I have unlcoked bootloader and installed twrp
Im on global stable rom.
The global rom encrypted all the files.
Twrp cant mount encrypted, therefore i cant format or reflash rom from it.
I know how to decrypt the phone.
Its gonna take me some hours and alot of work.
Is there a twrp witch reads encrypted disk?
If i can extract the key would it be possible to use in twrp?
Or do you recommend to flash rom that lets you chose if you want encryption.
I´ve got the same problem. Did you enable encryption or it was enabled by default?
Yeah it was enabeled buy default.
!SOLUTION!
1) download "Xiaomi Mi 5 Latest Global Developer Version Fastboot File Download" from here http://en.miui.com/a-234.html
2) extract this files "system.img" and "boot.img" from downloaded zip
3) flash this files with ADB over CMD ("fastboot flash system system.img" and "fastboot flash boot boot.img")
4) now you have this developer ROM without encryption (i know, it´s a little hardcore solution, but it works )
5) now flash last TWRP and BOOT img for Mi5 from here https://www.androidfilehost.com/?fid=24499762636006354
(over the ADB)
6) boot TWRP, skip encryption screen (yes it is still displayed) but now you can wipe all partitions in advanced mode!
7) after the wipe, mount MTP storage in TWRP, copy the zip file you want to your device and inslall this zip over the TWRP
8) reboot, wait 10-15min and enjoy new ROM
I had same problem, in TWRP I was asked for encryption password, I didn't had it so I did "format data" and after few sec, i was able to see sdcard. But of course that will format sdcard and data partition.
You were lucky, I couldn't made format of sdcard, TWRP didn't able this function because of encryption. Actually TWRP couldn't mount it and therefore it couldn't be formatted.
Hi guys,
I have xperia sp, where I had a newest firmware installed. I decided to mod it to newest cyanogenmod (android 7.1).
Using night build, install boot.img and using adb install rest of system. Forgot to install gapps, but system ran smoothly.
So i decided to install cyanogen once again, following these steps:
1. fastboot - flash boot.img
2. system clean - wipe /system, /data, /cache (wipe all available from recovery menu)
3. Trying to upload system using adb, by selecting on recovery menu "sideload". ADB failed - mot recognise device
4. Upload system (cyanogenmod) to sd card and trying to update from recovery menu
5. SD card is fully visible, but when trying to update got an error: "E: unable to find /misc partition" (!!!)
6. 3,4,5 I tried many time, unsuccessful
7. Decided to downgrade to original firmware using flashtool.
8. All files *.sin uploaded successfully, except system.sin (size above 1GB)
9. Trying to upload system.sin manually using fastboot, but got the error "(file too large)
Now I have original boot, but phone is locked on "SONY" screen
I need any advice, how to upgrade phone to any system.
btw, I tried all available stock firmwares (254, 205, etc)
best regards
M.
Dunno and not sure but it doesn't cost nothing to try:
with fastboot flash kernel from 7.1 zip package and also flash twrp 3
then try to enter twrp recovery (VOL+ when lights up)
Don't use the latest version of flashtool and use version 0.9.18.6 instead to flash stock firmware
http://www.flashtool.net/downloads.php
Sent from my Xperia SP using Tapatalk
Thanks.,
it helps Previous version of flashtool did it correctly.
Now I have new question related to CM:
after sucessful installation of CM, I back to recovery
1. Copy OpenGAPPS to sdcard
2. Initiate aplly update from sdcard
3. Installation started but
4. Got an error "E: failed to map file"
tried different versions of OpenGAPPS (pino, nano, micro) with the same result.
Should I use recovery image from cyanogenmod?
And next, when I tried to execute:
fastboot flash recovery twrp.img
got an error:
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
I need to install open gapps.
best regards
M.M.
Ok, I fixed it
Installed TWRM recovery and install gapps finally.
Thanks for help
Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators
Screenshots of Havoc OS gsi running on my zte axon 10:
Android Q Gsi works too
you can also use the zte android 9 stock kernel and vendor
That all is great news.....bravooo
Any issues with the havoc gsi?
blcistheking said:
Any issues with the havoc gsi?
Click to expand...
Click to collapse
Only the Fingerprint is broken
noobstyle1337 said:
Only the Fingerprint is broken
Click to expand...
Click to collapse
its only broken if you have a a2020g, works fine if you have a a2020u, current los kernel is missing a2020g fingerprint firmware from what i can gather.
Bliss 12.7 Android 10 gsi on a2020u.
rafyvitto said:
Follow these easy steps
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
==
Click to expand...
Click to collapse
whenever i try this i just get
"fastboot: unknown option -- disable-verity"
Mr. DR. Professor Electro said:
whenever i try this i just get
"fastboot: unknown option -- disable-verity"
Click to expand...
Click to collapse
Skip that step not needed, just flahs the disable encryption zip file in twrp to disable encryption.
i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?
honestly i cant even flash any rom zip i have i just get error 1s , i even wipe data/format before flashing am i doing something wrong am i supposed to be on a or b while doing this or what
Futility's Forgotten Soldier said:
i have bootloader unlocked ive wiped everything even flashed disable encryption but whenever i try to install the zip for lineage 17 i get an "error installing zip file' am i doing something wrong?
Click to expand...
Click to collapse
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.
cant escape bootloop hell and error 255
rafyvitto said:
Follow these easy steps
Makes sure you have the GSI image on your sdcard before starting this, if your coming from lineage OS backup your data!
1.Unlock Bootloader
2. Boot into bootloader, check your slot if on B switch to A and vice versa.(fastboot set_active a/b) or you can stay in your current active slot up to you.
3.Download twrp and flash it (fastboot flash boot boot.img)
4.Boot back into boot loader and run "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img" link with b11 vbeta.img
5.Boot into twrp,Format data or in bootloader run this command "fastboot format userdata" to get rid if encryption else gsi wont boot then, go to "install" navigate to your sdcard where you place the gsi , look for 'select image" then flash your gsi.
6.To flash gapps(skip if the gsi includes them) if your using a aosp gsi go to twrp then go into /wipe/advanced wipe/ select system on the options then "repair or change file system" then press on "resize file system" this will resize your system partiton back to 3.X gigs and allow you to flash gapps.
7.Then reboot to system
8. Your gsi "should" boot
Downloads:
http://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
https://forum.xda-developers.com/pr...bled-device-development/gsi-havoc-os-t3930030 Havoc OS the gsi ive been using for some weeks.
Fixes and WorkArounds
Volte Fix for GSi
Install the volt-ims.apk as you would normally install an apk, download here http://www.mediafire.com/file/l0x88jx5zxyknhh/volte-ims.apk/file
For root( magisk) and twrp flash http://www.mediafire.com/file/de8tccz7gr93831/twrp-magisked-los-boot.img/file
To pass SafetyNet flash this http://www.mediafire.com/file/867xncq865vvtct/Universal-safetynet-fix-v3.zip/file
Also I created a template for what works on phhusson Treble experiments wiki:
https://github.com/phhusson/treble_experimentations/wiki/ZTE-Axon-10-Pro
CREDITS:
Unjustifieddev for his work on lineage, and the boot.img im using.
All the gsi creators
Click to expand...
Click to collapse
rafyvitto said:
Lineage 17 is very broken right now, i would suggest flashing bliss 2.7 gsi, check my telegram channel for more info.
Click to expand...
Click to collapse
having trouble
Steps I followed:
(bootloader been unlocked but double checked to be sure)
Started from LineageOS 16 clean flashed based
booted rom made sure Debug was enable in settings did nothing else
booted to bootloader
>fastboot set_active a
>fastboot boot "D:\Android\Flash\Recovery.img"
In Recovery:
Installed Twrp zip
install zip DisableForcedEncryption.zip
-reboot bootloader
>fastboot flash vbmeta "C:\Users\chris\Downloads\ZTE_Flash\vbmeta.img"
>fastboot format userdata
boot to recovery:
Installed GSI Image of Havoc OS to System image
Flashing system image......
simg2ing '/sdcard1/Havoc-OS-v2.9-20190914-phhgsi_arm64_ab-offical.img' 'dev/block/bootdevice/by-name/system_a'process
ended with ERROR: 255
got creative because nothing i was doing was fixing the problem so i went into fast boot and
>fastboot flash system "location/of/Havoc.img"
now no longer can acess the recovery not even but fastboot boot img command and back in a bootloop hell
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot "D:\Android\Flash\Recovery.img"
downloading 'boot.img'...
OKAY [ 0.605s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.640s
also i have no way to return to the original 10 pro rom whenever i flash it via the EDL tool with one of the US edl
Zips you provided i have boot loop but it gives me enough so i can have bootloader mode accessible but i have to rerun
the bootloader unlock. but flashing Lineage 16 seems to be the only thing to make my phone functional without giving it boot loop hell
ill try do it with bliss later but if there's anywhere i went wrong or how to solve the 255 let me know i really want to try out one of those GSIs
but im running on the US rom and using the TWRP for my pro from the fourms so i just really confused here idk if i could possibly give you anymore details
ok update i got it working
1. the 255 i fixed by
"
Reboot into recovery, TWRP
Go to the terminal in "Advanced"
Type cd /system to change the path to the system folder
Type rm addon.d to remove the addon file
Type exit to quit from the terminal
Now back to TWRP home, try backup/restore again, it should works.
Further adjustment: do check the use rm -f to format disk settings of TWRP, to make sure TWRP won't mess up the filesystem."
secondly what was ruining me was a big dumb mistake on my part you HAVE to do " --disable-verity --disable-verification flash vbmeta vbmeta.img" with the latest ADB tool kit I was using minimal adb and fastboot then got it to work
In step 5,i can not boot into TWRP and phone displays ZTE crashdump mode.
Please help.
Thanks.
Edit: I fixed it and can flashed this rom but it has some bugs.
This thread outlines the exact steps in installing a custom ROM on your Huawei Honor Note 10 device with either EMUI 8 or EMUI 9. You can install and run TWRP on both EMUI and or EMUI 9.
Make sure to follow this guide precisely, as order matters. At the end, I will post an explanation of why we need to execute these steps. I spent an entire weekend of trial and error on my Huawei Honor Note 10, and now I have figured out the ins and outs so you don't have to. You're welcome
Prerequisites
Huawei Honor Note 10 device, either on stock ROM or rooted (doesn't matter)
MicroSD card (formatted exFAT or FAT, doesn't matter)
Bootloader unlock code for Huawei Honor Note 10 (follows a format like my own HBP38K14DBK2RNB4)
Computer with admin privileges
Before You Flash Anything
Back up, back up, back up! I am not responsible if you lose valuable or sensitive data. Your Huawei Honor Note 10 will factory reset a number of times (probably more) before you can get back up and running again. Either use TWRP to do this, or use HiSuite (not recommended but will work on a locked bootloader).
Remove your SIM card! Your carrier may get charged ridiculous amounts of fees if you have a limited data plan, such as 256MB (Canada has notoriously expensive phone plans, so Canadians beware). When you reboot, expect Huawei's stock ROM to use copious amounts of data on retrieving the latest version of bloatware and spyware.
Ensure you have stock recovery installed. If you don't, download the stock recovery image, place it in your Minimal ADB and Fastboot folder, then boot to download mode by holding the VOLUME DOWN button and simultaneously plug in in your Huawei Honor Note 10 device, then open Minimal ADB and Fastboot on your computer and run this command:
Code:
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
Steps to Install Custom ROM on Huawei Honor Note 10
Download the EMUI 9 stock ROM and place the dload folder on your MicroSD card
Boot to (stock) recovery by holding down the VOLUME UP, VOLUME DOWN, and POWER buttons at the same time. The update should begin immediately. Wait patiently for your phone to reboot
Fill out the bloatware questionnaire by Huawei and download any and all updates under Settings. This will ensure you have the latest boot image. You will reboot at least once.
Once you have completed all the updates, reboot to download mode; press and hold the VOLUME DOWN button while you plug in your Huawei Honor Note 10 device to your computer
On your computer, download and open Minimal ADB and Fastboot
Run the following command:
Code:
fastboot oem unlock <code>
(where code corresponds to a format that looks like this: HBP38K14DBK2RNB4)
Confirm unlocking your bootloader by using the VOLUME keys, selecting yes, and pressing the POWER button. The Huawei Honor Note 10 device will now perform a factory reset
IMPORTANT step. DO NOT let the Huawei Honor Note 10 reboot. DO NOT. Impatiently wait for the low-level factory reset to complete and as soon as it does, enter download mode again by pressing the VOLUME DOWN key and plugging in the device again
Flash this TWRP recovery:
Code:
fastboot flash recovery_ramdisk HN10_Twrp.img
Reboot to recovery by holding the VOLUME UP and POWER buttons for over 5 seconds. You should see the TWRP logo, and it should boot up. It should boot up right away, so if TWRP hangs here on the TWRP logo, you need to skip back to step 2
IMPORTANT: wipe to factory reset. Wipe /system again via advanced wipe just to be safe
Install any custom ROM you wish via selecting a system image
IMPORTANT: disable_Dm-Verity_ForceEncrypt by installing this zip. If you don't do this, you won't be able to enter TWRP again
Optionally install magisk, titanium backup, and other magisk mods
Reboot system and profit
Update: 2021-04-06
Reboot to recovery by holding the VOLUME UP and POWER buttons for over 5 seconds. This should boot you to stock RECOVERY.
Wipe to factory reset. Confirm by typing "yes" (WARNING: this wipes your device)
Plug in your Huawei Honor Note 10 to your PC with ADB
Boot to DOWNLOAD mode by holding down the VOLUME DOWN button as soon as your Huawei Honor Note 10 reboots
Flash this TWRP recovery:
Code:
fastboot flash recovery_ramdisk HN10_Twrp.img
Reboot to recovery by holding the VOLUME UP and POWER buttons for over 5 seconds. You should see the TWRP logo, and it should boot up. It should boot up right away, so if TWRP hangs here on the TWRP logo, you need to skip back to step 2
Install any custom ROM you wish via selecting a system image (or zip file if you have EMUI 8)
Install magisk, titanium backup, and other magisk mods (note that you will NOT be able to boot to recovery after this; consider this you last chance to install any mods)
Reboot system and profit
Background and Explanation
When you first flash a ROM, even in EMUI 8, your Huawei Honor Note 10 encrypts /system to prevent third parties such as TWRP from mounting it. Hence, you may successfully boot to TWRP, but /system will be mounted as read-only. This is problematic, as it means you can't install any new ROMs (however, you can make a backup, which can be useful for backing up stock, encrypted /system partitions)
Because /system gets encrypted, it means you have to wipe /system completely. Doing a factory reset (low-level) does this, once you unlock your bootloader. However, if you were to let your Huawei Honor Note 10 boot, then the stock ROM would, by default, encrypt /system, forcing you to start this process all over again (as TWRP will, in most cases, not even boot with an encrypted /system). If your TWRP hangs on the TWRP logo, your /system partition is likely encrypted. You need to factory reset, install TWRP again, and then wipe /system, followed by installing the Disable_Dm-Verity_ForceEncrypt_01.15.2020.zip script.
ROMs I Tested That Work (well)
Resurrection Remix 7 (openKirin)
I hope this guide helps other fellow Huawei Honor Note 10 owners. If you have any questions, please also make sure to include your EMUI version and steps taken so that I can best help you. I hope that I have saved some of you trouble when updating to EMUI 9 and also helped to explain why updating can become so tedious.
Thank you for the instructions! I've got some questions...
ForgottenSolstace said:
IMPORTANT: wipe to factory reset. Wipe /system again via advanced wipe just to be safe
Install any custom ROM you wish via selecting a system image
Click to expand...
Click to collapse
During these steps, I saw the error messages like these:
Code:
Updater process ended with ERROR:7
Error installing zip file '/sdcard/RR-P-v7.0.2-20200202-ravel-Unoffical.zip'
and
Code:
Failed to mount '/cust' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Failed to mount '/product' (Invalid argument)
I tried getting into fastboot mode and flash the CUST.img, VENDOR.img, ODM.img and PRODUCT.img but failed with the error message "FAILED (remote: Command not allowed)", what should I do?
null00005 said:
Thank you for the instructions! I've got some questions...
During these steps, I saw the error messages like these:
Code:
Updater process ended with ERROR:7
Error installing zip file '/sdcard/RR-P-v7.0.2-20200202-ravel-Unoffical.zip'
and
Code:
Failed to mount '/cust' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Failed to mount '/product' (Invalid argument)
I tried getting into fastboot mode and flash the CUST.img, VENDOR.img, ODM.img and PRODUCT.img but failed with the error message "FAILED (remote: Command not allowed)", what should I do?
Click to expand...
Click to collapse
Yep, so it sounds like you have an encrypted /data.
Make sure you can safely wipe the entire device, then try the following in download mode:
Bash:
fastboot erase userdata
(Note: this will erase everything on /data)
Then boot to TWRP again. Check the logs and try again.
ForgottenSolstace said:
Yep, so it sounds like you have an encrypted /system.
Make sure you can safely wipe the entire device, then try the following in download mode:
Bash:
fastboot erase userdata
Then boot to TWRP again. Check the logs and try again.
Click to expand...
Click to collapse
How do I wipe the entire device? I have done step 8 properly (get into fastboot immediately after low-level factory reset completes) and wiped system in TWRP, but still get the error messages.
null00005 said:
How do I wipe the entire device? I have done step 8 properly (get into fastboot immediately after low-level factory reset completes) and wiped system in TWRP, but still get the error messages.
Click to expand...
Click to collapse
Bash:
fastboot erase userdata
That will wipe /data.
Since you can also boot to TWRP, then try wiping /system, cache, and dalvik (factory reset). If you can also wipe /data, then that might also work in TWRP, depending on which version you're using.
ForgottenSolstace said:
Bash:
fastboot erase userdata
That will wipe /data.
Since you can also boot to TWRP, then try wiping /system, cache, and dalvik (factory reset). If you can also wipe /data, then that might also work in TWRP, depending on which version you're using.
Click to expand...
Click to collapse
After reinstalling the stock ROM and unlock bootloader and flash TWRP again, I performed "fastboot erase system" and "fastboot erase userdata" in fastboot, then wiped Dalvik, cache, Cust, Data, system, Product and Version in TWRP. However, I am still getting the "Failed to mount '/odm' (Invalid argument)" error message
I can't wipe odm in TWRP since there is no such option, and I can't perform "fastboot erase odm" as it shows up an error message saying "FAILED (remote: Command not allowed)". What should I do now?
null00005 said:
After reinstalling the stock ROM and unlock bootloader and flash TWRP again, I performed "fastboot erase system" and "fastboot erase userdata" in fastboot, then wiped Dalvik, cache, Cust, Data, system, Product and Version in TWRP. However, I am still getting the "Failed to mount '/odm' (Invalid argument)" error message
I can't wipe odm in TWRP since there is no such option, and I can't perform "fastboot erase odm" as it shows up an error message saying "FAILED (remote: Command not allowed)". What should I do now?
Click to expand...
Click to collapse
If you roll back to stock and unlock your bootloader again, then you don't need to do fastboot erase userdata because "factory reset low-level" will perform that once you unlock your bootloader again. So you should be able to flash TWRP, boot fine (only that one time), install whatever ROM you want, flash magisk, and boot (note: on EMUI9, you must reboot to recovery, as boot_ramdisk only exists in EMUI8).
In the past, I have ignored the message "failed to mount '/odm'" and still had success; just pay attention to the status code at the end when you install /system. Don't bother wiping odm, as we really care about mounting /system. Perform a factory reset just to be safe, and feel free to wipe /data, but it won't matter if you already performed a factory-reset (low-level) from unlocking your bootloader again.
Try installing your ROM of choice from TWRP despite this error, flashing magisk, and confirm if that works.
ForgottenSolstace said:
This thread outlines the exact steps in installing a custom ROM on your Huawei Honor Note 10 device with either EMUI 8 or EMUI 9. You can install and run TWRP on both EMUI and or EMUI 9.
ROMs I Tested That Work (well)
Resurrection Remix 7 (openKirin)
Click to expand...
Click to collapse
Hi, how about root with magisk in this rom?!
TheFastGT said:
Hi, how about root with magisk in this rom?!
Click to expand...
Click to collapse
I second that. Magisk installed in boot.img but ROM doesn't recognize root, installing SuperSU says done but no result. Once I got SuperSU to get into stage where it said that boot might take longer and it was recognized but I can't replicate that anymore.
jazzzy said:
I second that. Magisk installed in boot.img but ROM doesn't recognize root, installing SuperSU says done but no result. Once I got SuperSU to get into stage where it said that boot might take longer and it was recognized but I can't replicate that anymore.
Click to expand...
Click to collapse
Just done....you need to install magisk in this:
RECOVERY_RAMDIS.img
then flash via fastboot and reboot...
TheFastGT said:
Just done....you need to install magisk in this:
RECOVERY_RAMDIS.img
then flash via fastboot and reboot...
Click to expand...
Click to collapse
so I open Magisk app and patch RECOVERY_RAMDIS.img, then flash RECOVERY_RAMDIS.img and after that flash TWRP ? TWRP won't overwrite RECOVERY_RAMDIS.img ?
jazzzy said:
so I open Magisk app and patch RECOVERY_RAMDIS.img, then flash RECOVERY_RAMDIS.img and after that flash TWRP ? TWRP won't overwrite RECOVERY_RAMDIS.img ?
Click to expand...
Click to collapse
I've a Honor Note 10 and i haven't TWRP installed, i use stock recovery and Openkirin rom...
How can I unlock my bootloader?
Darj said:
How can I unlock my bootloader?
Click to expand...
Click to collapse
HCU client
TheFastGT said:
HCU client
Click to expand...
Click to collapse
Thanks.. this is the only device I have so I wanted to ask what would happen if I mess it up
TheFastGT said:
HCU client
Click to expand...
Click to collapse
And once I unlock the bootloader using HCU client, do I have to follow the steps above or can I just install a custom recover how you'd do on any phone?
@Darj , did you manage to sort out rooting your Huawei Honor Note 10? I've updated the installation steps to reflect the shortened steps I last took to get Magisk running (downgraded to EMUI8 on my Huawei Honor Note 10 to try to preserve TWRP).
Hopefully, we'll see more ROMS from the OpenKirin project, as the latest security patch is almost a year old on EMUI8.
@ForgottenSolstace not yet. I want to make sure I have all the informations I need before spending money to unlock the bootloader
@Darj , it only costs 15USD to unlock your Huawei Honor Note 10. Why not go ahead and try?
I assure you that the effort is much worth it; Stock ROM is bloated with all kinds of spyware from the Chinese government. When you install AOSP, you can actually secure your phone following the updated instructions which encrypts /data.
Let me know if you have any questions. Happy to help
Hi ...got problem using twrp?
I'm having trouble installing GSI on the Galaxy Tab A8 2021.
1.Dedicated TWRP Recovery in XDA data was released as Odin after bootloader.
2.I entered the TWRP recovery and there was a unable mount twrps error.
3.To solve the problem, I entered the Format Data of the Wipe section of the TWRP Recovery, entered yes, and initialized it. The problem has been solved since then.
4.To install GSI, I went to the Wipe item in TWRP Recovery and tried Swipe to factory Reset, then pressed Advanced Wipe, selected Dalbik/ART Cache,Metadata,Cache,Data,Internal Storage, and tried Swipe to Wipe.
5.Select Fastboot from the Reboot item in TWRP Recovery and enter Fastboot mode.
6.I ran Google Platform-tools_r33.0.3-windows on my computer and typed the command you see in the picture.
7.I ran Fastboot -w after flashing GSI, but I got an error and reboot my Galaxy Tab will boot indefinitely.
*The GSI ROM file used the 9/12 UNOFFICICAL arm64 bgs.img file of Lineage os19.1.
*The firmware version of the Galaxy Tab is the most recent version.
Please check if there is a problem with my installation method.
I'm a person who doesn't know how to use English, so I used a translator. Thank you for your understanding.
In the step #7, instead of run "fastboot -w" try to flash the system file with "fastboot flash system nameofthe.img". After that, reboot in recovery again and format data like you usually do with TWRP, finally try to reboot the system.