How to reset completely? (Boot Loop, TWRP-Backup not working) - Honor 8 Questions & Answers

Hey,
after my phone (L09 C636, EMUI 5, B380, rooted) began to do really crazy things yesterday (seemed like SuperSU was the problem) I decided to reset it completely because installation was a long and dirty path.
Here my steps (some missing, did to many things):
- don't know anymore how I started hours ago...
- tried several things with MultiTool and Huwei Update extractor
- wasn't able to enter something else than eRecovery and fastboot for hours
- got TWRP (3.1.1.0) run after several flashes of differtent versions
- no access to sdcard and not shown on PC (only ext SD)
- got Backup (EMUI 5, rooted) restored (without Vendor, Product, Version because with fails)
- bootloop
- sdcard accessable in TWRP and on PC
- tried dload way with different firmware versions (B130, B360, B380, failes (update.app inside dload, HuWoc (don't know name) folder deleted on sdcard)
So in summary I should have a colorfull shake of different parts of several firmwares, backups and internet guides.
Could anyone give me steps how I can get everything reseted and a clean phone? Don't need to detailed description, just steps that make the phone clean and runable so I can reinstall everything.
Thank you!

0mrwhatsupguy0 said:
Hey,
after my phone (L09 C636, EMUI 5, B380, rooted) began to do really crazy things yesterday (seemed like SuperSU was the problem) I decided to reset it completely because installation was a long and dirty path.
Here my steps (some missing, did to many things):
- don't know anymore how I started hours ago...
- tried several things with MultiTool and Huwei Update extractor
- wasn't able to enter something else than eRecovery and fastboot for hours
- got TWRP (3.1.1.0) run after several flashes of differtent versions
- no access to sdcard and not shown on PC (only ext SD)
- got Backup (EMUI 5, rooted) restored (without Vendor, Product, Version because with fails)
- bootloop
- sdcard accessable in TWRP and on PC
- tried dload way with different firmware versions (B130, B360, B380, failes (update.app inside dload, HuWoc (don't know name) folder deleted on sdcard)
So in summary I should have a colorfull shake of different parts of several firmwares, backups and internet guides.
Could anyone give me steps how I can get everything reseted and a clean phone? Don't need to detailed description, just steps that make the phone clean and runable so I can reinstall everything.
Thank you!
Click to expand...
Click to collapse
I had the same problem, first of all I used Huawei firmware extractor, so I flashed from fastboot recovery, recovery2 and boot(remember to use emui 5 firmware, with older version it will fail)
After that I used rollback package from dload and then I have installed a full marshmallow firmware from dload ...then updated to emui 5 and rooted again.

The Update.app hat to get directly in the dload folder on the external SD right? dload tells me the package doesn't exist...
Edit: getting tired. Copied the rollback as zip next try...
Edit: Rollback successful
Edit: THANK YOU! Got a runnig phone with Marshmellow that I can work with
Steps were just:
- Extracted recovery, recovery2 and boot out of B380 package
- flash them with fastboot
- install rollback package with dload
- install B130 (Marshmellow)

Related

Need stock recovery image: MHA-L29C185

My phone is dead in water.. I have TWRP that complains that the system partition is read only,
I have erecovery that cannot says "getting package info failed" (dies afer "getting package info from server"), and manual downloading of image 138 putting it in dload folder of SDCARD did not go -- it complained that it was not the right version I think..
What can I do now? I thought that I ought to restore the recovery partition, but I can't seem to find it anywhere..
I'm going nuts here
HELP!!
PS: I have been downloading the firmwares from http://hwmt.ru/oth/HWFF/info/view.php?find_model=mha , they have two sets: Do I need the OTA or the FULL version to be put into SDCARD's "dload" folder?
You need the FULL version. OTA means "over the air update", and is meant to be applied from a specific version to bring you to a newer version without having to download everything.
tkalfaoglu said:
My phone is dead in water.. I have TWRP that complains that the system partition is read only,
I have erecovery that cannot says "getting package info failed" (dies afer "getting package info from server"), and manual downloading of image 138 putting it in dload folder of SDCARD did not go -- it complained that it was not the right version I think..
What can I do now? I thought that I ought to restore the recovery partition, but I can't seem to find it anywhere..
I'm going nuts here
HELP!!
PS: I have been downloading the firmwares from http://hwmt.ru/oth/HWFF/info/view.php?find_model=mha , they have two sets: Do I need the OTA or the FULL version to be put into SDCARD's "dload" folder?
Click to expand...
Click to collapse
well this is a long shot,try to unlock ur BL again.after that try to boot into twrp.and for now only L29C636 n AL00C00 have offline update files that can be flash thru dload folder.
edit-if you need stock recovery actually u can downlaod the full fw of your build and extract update.app using huawei extractor and flash the recovery.img thru twrp or adb
If you can, try firmware finder. For that to work your phone must boot. Or you can go with FunkyHuawei, but that costs money to use.
Both requires stock recovery to install though. And as @eddmecha says, only 2 builds are offline installable.
The system being read only in TWRP is normal as its added as RO in fstab. And if you have dm-verity enabled its no point in installing anything to /system.
>well this is a long shot,try to unlock ur BL again.after that try to boot into twrp.and for now >only L29C636 n AL00C00 have offline update files that can be flash thru dload folder.
>edit-if you need stock recovery actually u can downlaod the full fw of your build and >extract update.app using huawei extractor and flash the recovery.img thru twrp or adb
Thank you very much; however, there is a problem with the huawei extractor: The extractor works and creates unknown_nn.img files, and there is another script, HuaweiFinder or something that renames them by guessing their contents. I have the "unknown" files, but that renaming script no longer works -- (it dies with FINDSTR errors).
So I can't find the recovery.. perhaps someone could do a "strings recovery.img" and tell me what I suppose to see in there, so I can do the same search amongs my unknown_nn.img files.. Many thanks! -t
eddmecha said:
well this is a long shot,try to unlock ur BL again.after that try to boot into twrp.and for now only L29C636 n AL00C00 have offline update files that can be flash thru dload folder.
edit-if you need stock recovery actually u can downlaod the full fw of your build and extract update.app using huawei extractor and flash the recovery.img thru twrp or adb
Click to expand...
Click to collapse
I am right now trying to do that -- to fix the recovery to stock, so that eRecovery will let me recover anything!
But can't find it amongst the extracted "unknown_file.nn" files ..
tkalfaoglu said:
I am right now trying to do that -- to fix the recovery to stock, so that eRecovery will let me recover anything!
But can't find it amongst the extracted "unknown_file.nn" files ..
Click to expand...
Click to collapse
from whr did u download the huawei extractor?
https://forum.xda-developers.com/showthread.php?t=2433454
is it this one?
eddmecha said:
from whr did u download the huawei extractor?
https://forum.xda-developers.com/showthread.php?t=2433454
is it this one?
Click to expand...
Click to collapse
I totally forgot about that one! I instead had used the one that required Perl..
I'm downloading and working on it now; many thanks!!
-t
UPDATE: After removing TWRP (with tears in my eyes) with:
sudo fastboot flash recovery RECOVERY.img
I was able to get my phone back.. It works now!

TWRP always says 'permission denied' & filenames are completely different

Hi,
I have a Mate 9 , Build No. MHA-L09C432B182
Baseband is 21.516.00.00.010
Kernel: 4.1.18-g0ad0fb3
I unlocked bootloader, it is defenetely unlocked. I am able to install TWRP.
I installed twrp-3.0.2 and also twrp-3.1.0 versions but have same problems in both versions:
filenames/folder names in /sdcard (internal storage) are broken, I mean their original names are gone, all files and folders are named like imbj9yf1fATc4Tvm5zt+ and so on instead of Screenshots for example.
So I cannot find my supersu.zip but however I think it would not install, because of this error:
Also I cannot run a TWRP backup, it shows:
Backup started
Backup Folder /data/media/0/TWRP/Backups/UGM2171100001069/2017-07-21-13-11-39_NRD90M...
Can not create '/data/media/0/TWRP' folder (Permission denied)
Failed to make backup folder
I tried to CHMOD 755 this folder/path, did not work/help
Can anybody help me here?
Thx and best!
/data is encrypted by default using file based encryption. That's why you see those files in /sdcard (/data/media/0/). You can remove encryption by using Wipe - 'Format Data' button.
This will remove everything in /data including your files in /sdcard.
To flash stuff you can use an external SD card or remove encryption or flash this twrp: https://mega.nz/#!xg9hWbpJ!dNOWJVUuD_4JL8N8PiDXYsj3SnvaOfKxBndvWc_4wgo
and adb push (adb push file.zip /cache/file.zip) to /cache and flash from there. /cache is added as storage with that twrp.
If you want to remove encryption, flash official SuperSU 2.82 SR1: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or Magisk 13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both require at least twrp 3.1.0.
If you chose to remove encryption you will also have to flash public and HW zips after Format Data, because files in /data/hw_init are removed which are needed for themes to work and 'System Update' and a few Huawei apps.
Public zip for L09C432B182:
http://update.hicloud.com:8180/TDS/...55/f1/full/public/update_data_full_public.zip
Hw zip for L09C432B182: http://update.hicloud.com:8180/TDS/...04/v84355/f1/full/hw/eu/update_full_hw_eu.zip
Flash public first then hw. Both will give errors but install fine.
If you don't want to remove encryption you won't be able to backup /data.
If so use this SuperSU: https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
Or magisk 13.3: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE
thanks for all your info.
Can you suggest what to do? Acutually I just want to install root to get titanium to work because I have older backups I want to look into to. After that I want to unroot again.
Not sure if i need encryption or if ishould decrypt now
Whats the best way for me now?
ante0 said:
/data is encrypted by default using file based encryption. That's why you see those files in /sdcard (/data/media/0/). You can remove encryption by using Wipe - 'Format Data' button.
This will remove everything in /data including your files in /sdcard.
To flash stuff you can use an external SD card or remove encryption or flash this twrp: https://mega.nz/#!xg9hWbpJ!dNOWJVUuD_4JL8N8PiDXYsj3SnvaOfKxBndvWc_4wgo
and adb push (adb push file.zip /cache/file.zip) to /cache and flash from there. /cache is added as storage with that twrp.
If you want to remove encryption, flash official SuperSU 2.82 SR1: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or Magisk 13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both require at least twrp 3.1.0.
If you chose to remove encryption you will also have to flash public and HW zips after Format Data, because files in /data/hw_init are removed which are needed for themes to work and 'System Update' and a few Huawei apps.
Public zip for L09C432B182:
http://update.hicloud.com:8180/TDS/...55/f1/full/public/update_data_full_public.zip
Hw zip for L09C432B182: http://update.hicloud.com:8180/TDS/...04/v84355/f1/full/hw/eu/update_full_hw_eu.zip
Flash public first then hw. Both will give errors but install fine.
If you don't want to remove encryption you won't be able to backup /data.
If so use this SuperSU: https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
Or magisk 13.3: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE
Click to expand...
Click to collapse
thanks for all your info.
Can you suggest what to do? Acutually I just want to install root to get titanium to work because I have older backups I want to look into to. After that I want to unroot again.
Not sure if i need encryption or if ishould decrypt now
Whats the best way for me now?
tobyffm said:
thanks for all your info.
Can you suggest what to do? Acutually I just want to install root to get titanium to work because I have older backups I want to look into to. After that I want to unroot again.
Not sure if i need encryption or if ishould decrypt now
Whats the best way for me now?
Click to expand...
Click to collapse
Then don't bother with decryption.
So you basically just have to place the root of your choice (of the mega ones I linked, because the official ones will remove encryption in your boot image and you will boot loop if you flash the official ones) on an external SD or transfer to /cache with adb after flashing the linked twrp. Then flash root and you're good to go.
I think you can sideload root zip, I haven't tried it. But that's another possibility if you don't have an external SD.
ante0 said:
Then don't bother with decryption.
So you basically just have to place the root of your choice (of the mega ones I linked, because the official ones will remove encryption in your boot image and you will boot loop if you flash the official ones) on an external SD or transfer to /cache with adb after flashing the linked twrp. Then flash root and you're good to go.
I think you can sideload root zip, I haven't tried it. But that's another possibility if you don't have an external SD.
Click to expand...
Click to collapse
Yes, it worked, i flashed supersu and got root acccess now, thx very much.
About unrooting later on, i understand I need to download the full stock rom, create a dload folder and copy update.app into it and reboot phone to download mode. It then will install stock rom and stock recovery, correct?
Will this erase internal storage again same like when unlocking bootloader?
thx!
tobyffm said:
Yes, it worked, i flashed supersu and got root acccess now, thx very much.
About unrooting later on, i understand I need to download the full stock rom, create a dload folder and copy update.app into it and reboot phone to download mode. It then will install stock rom and stock recovery, correct?
Will this erase internal storage again same like when unlocking bootloader?
thx!
Click to expand...
Click to collapse
No need (dload doesn't work anyway, except for AL00C00B115 and L29C636B136). You can uninstall using the SuperSU app or manually by removing /data/SuperSU.apk and restoring stock boot image. Boot image can be extracted from update.app for your model using Huawei Update extractor. Same goes for recovery. If you want to lock bootloader you have to install an update/same build number, you could use Firmware Finder for that or this tool: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
In my experience it will not remove apps, but data seems to go poof (as in app settings and data). Unlocking bootloader again will remove apps though as it does a factory reset.
ante0 said:
/data is encrypted by default using file based encryption. That's why you see those files in /sdcard (/data/media/0/). You can remove encryption by using Wipe - 'Format Data' button.
This will remove everything in /data including your files in /sdcard.
To flash stuff you can use an external SD card or remove encryption or flash this twrp: https://mega.nz/#!xg9hWbpJ!dNOWJVUuD_4JL8N8PiDXYsj3SnvaOfKxBndvWc_4wgo
and adb push (adb push file.zip /cache/file.zip) to /cache and flash from there. /cache is added as storage with that twrp.
If you want to remove encryption, flash official SuperSU 2.82 SR1: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or Magisk 13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both require at least twrp 3.1.0.
If you chose to remove encryption you will also have to flash public and HW zips after Format Data, because files in /data/hw_init are removed which are needed for themes to work and 'System Update' and a few Huawei apps.
Public zip for L09C432B182:
http://update.hicloud.com:8180/TDS/...55/f1/full/public/update_data_full_public.zip
Hw zip for L09C432B182: http://update.hicloud.com:8180/TDS/...04/v84355/f1/full/hw/eu/update_full_hw_eu.zip
Flash public first then hw. Both will give errors but install fine.
If you don't want to remove encryption you won't be able to backup /data.
If so use this SuperSU: https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
Or magisk 13.3: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE
Click to expand...
Click to collapse
hi,
thx for your last reply!
I am still on root status. I needed to decrypt now, thus I selected format data.
After that, files and folders are named correctly and I am able to create a backup.
I flashed public ziip, the other one was corrupt, mayve because of failed download, however as I understand it is not the reason why it always goes back to encryption, isn't it?
But: Once I reboot to Android and go back to recovery it is encrypted again?
My current problem is: I need to move a TWRP backup to internal storage and run TWRP restore feature from recovery, but it is encrypted. Once I format data it is decrypted but internal storage empty again. So I reboot to Android (because mounting from within TWRP does not work )and put TWRP backup folder to internsal storage, but then I go back to recovery and see it is encrypted again :S like driving in a circle ...
And I cannot put backup folder to external micro sd as it is too large for my small micro sd I have.
Do I need to flash a decrypted bootimage? If yes, which one?
Can you help me on this maybe?
tobyffm said:
hi,
thx for your last reply!
I am still on root status. I needed to decrypt now, thus I selected format data.
After that, files and folders are named correctly and I am able to create a backup.
I flashed public ziip, the other one was corrupt, mayve because of failed download, however as I understand it is not the reason why it always goes back to encryption, isn't it?
But: Once I reboot to Android and go back to recovery it is encrypted again?
My current problem is: I need to move a TWRP backup to internal storage and run TWRP restore feature from recovery, but it is encrypted. Once I format data it is decrypted but internal storage empty again. So I reboot to Android (because mounting from within TWRP does not work )and put TWRP backup folder to internsal storage, but then I go back to recovery and see it is encrypted again :S like driving in a circle ...
And I cannot put backup folder to external micro sd as it is too large for my small micro sd I have.
Do I need to flash a decrypted bootimage? If yes, which one?
Can you help me on this maybe?
Click to expand...
Click to collapse
'Format Data', flash official Magisk 13.3 or SuperSU 2.82 SR1 (mine from mega doesn't remove encryption), flash public zip, flash HW zip. It should now stay decrypted. You might have to go back to TWRP start screen after Format, then select 'Reboot' - 'Reboot Recovery' if it doesn't want to mount /data after Format.
Rebooting to system after formatting but not flashing magisk or supersu will encrypt again.
I can make a decrypted boot image if it doesn't want to stay decrypted.
ante0 said:
'Format Data', flash official Magisk 13.3 or SuperSU 2.82 SR1 (mine from mega doesn't remove encryption), flash public zip, flash HW zip. It should now stay decrypted. You might have to go back to TWRP start screen after Format, then select 'Reboot' - 'Reboot Recovery' if it doesn't want to mount /data after Format.
Rebooting to system after formatting but not flashing magisk or supersu will encrypt again.
I can make a decrypted boot image if it doesn't want to stay decrypted.
Click to expand...
Click to collapse
ok thx.
I redownloaded HW zip and checked md5 sum with the file from first attempt, same md5. However this is what i did:
Format data, tried to flash Magisk, but did not work, there was an error, this is why I flashed SuperSU 2.82 SR1 which worked with no errors. I flashed public zip right away, after that I flashed HW zip, but again, it did not work there were errors. However, encryption seems to be gone anyway. and yes, it keeps being decrypted.
I managed to get TWRP seeing an old TWRP Backup, which I pushed onto internal storage. I started restore of /data/ of that TWRP backup because I want to get the WhatsApp incl. data from data backup.
I booted up to Android and now I am faced with the next fuc*in problem: lock pattern of Dec 16. I cant remember and after few attemps devices is locked for 10 minutes, then for another 30 minutes ...
After google research it should be able to use Android device manager from a browser and to lock device and set a new pin/password to unlock the device. It is communicating as I can let the phone ring with no problem, but all how_tos show me this screen in android device manager interface
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Of course it is me, who dont get this mask to set a new pin/password ( (
I only can enter an optional phone no and message from browser
Any idea what to do?
Update: I extracted whatsapp from backup with nandroid manager app but it did not restore my data correctly, best way would be to get done the pattern problem when restopring the twrp backup
redaring locking bootloader again:
I went to your link https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
they say to download file for own device here: http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=
I only find:
DUK-L09C432B182
But mine is MHA-L09C432B182, can I go forward with DUK-L09C432B182 anyway? Actually I dont understand what to do, their description is curios.
tobyffm said:
ok thx.
I redownloaded HW zip and checked md5 sum with the file from first attempt, same md5. However this is what i did:
Format data, tried to flash Magisk, but did not work, there was an error, this is why I flashed SuperSU 2.82 SR1 which worked with no errors. I flashed public zip right away, after that I flashed HW zip, but again, it did not work there were errors. However, encryption seems to be gone anyway. and yes, it keeps being decrypted.
I managed to get TWRP seeing an old TWRP Backup, which I pushed onto internal storage. I started restore of /data/ of that TWRP backup because I want to get the WhatsApp incl. data from data backup.
I booted up to Android and now I am faced with the next fuc*in problem: lock pattern of Dec 16. I cant remember and after few attemps devices is locked for 10 minutes, then for another 30 minutes ...
After google research it should be able to use Android device manager from a browser and to lock device and set a new pin/password to unlock the device. It is communicating as I can let the phone ring with no problem, but all how_tos show me this screen in android device manager interface
Of course it is me, who dont get this mask to set a new pin/password ( (
I only can enter an optional phone no and message from browser
Any idea what to do?
Update: I extracted whatsapp from backup with nandroid manager app but it did not restore my data correctly, best way would be to get done the pattern problem when restopring the twrp backup
redaring locking bootloader again:
I went to your link https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
they say to download file for own device here: http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=
I only find:
DUK-L09C432B182
But mine is MHA-L09C432B182, can I go forward with DUK-L09C432B182 anyway? Actually I dont understand what to do, their description is curios.
Click to expand...
Click to collapse
L09C432B156 firmware: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v84355/f1/full/update.zip
L09C432B182 public data zip:
http://update.hicloud.com:8180/TDS/...55/f1/full/public/update_data_full_public.zip
L09C432B182 hw data zip:
http://update.hicloud.com:8180/TDS/...04/v84355/f1/full/hw/eu/update_full_hw_eu.zip
You might as well update to B190 while you're at it..
L09C432B190: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v89786/f1/full/update.zip
L09C432B190 public data zip:
http://update.hicloud.com:8180/TDS/...86/f1/full/public/update_data_full_public.zip
L09C432B190 hw data zip: http://update.hicloud.com:8180/TDS/...l/MHA-L09_hw_eu/update_full_MHA-L09_hw_eu.zip
Rename public data zip to update_data_public.zip.
Rename hw data zip to update_all_hw.zip
ok, to summarize:
1) I download these 3 files:
full update.zip:
L09C432B190: http://update.hicloud.com:8180/TDS/d...ull/update.zip
L09C432B190 public data zip:
http://update.hiclod.com:8180/TDS/d...ull_public.zip
L09C432B190 hw data zip:
http://update.hicloud.com:8180/TDS/d...-L09_hw_eu.zip
2) I extract recovery img file from update zip
3) I uninstall root from within super su app.
4) I rename zip files and flash public zip as well as hw zip from within twrp recovery
5) i put extraced recovery img to device by using "fastboot flash recovery "
Will it work like this? Or do I need to flash public and hw first and after that uninstall root from supersu?
and then in the end "fastboot oem lock" ? to get the bootloader locked and to switch off the boot message "your device cant be trusted" ?
and: I couldnt flash hw zip before as it ended up with errrors, is this why I dont have Search for updates in EMUI 5.0 anymore?
tobyffm said:
ok, to summarize:
1) I download these 3 files:
full update.zip:
L09C432B190: http://update.hicloud.com:8180/TDS/d...ull/update.zip
L09C432B190 public data zip:
http://update.hiclod.com:8180/TDS/d...ull_public.zip
L09C432B190 hw data zip:
http://update.hicloud.com:8180/TDS/d...-L09_hw_eu.zip
2) I extract recovery img file from update zip
3) I uninstall root from within super su app.
4) I rename zip files and flash public zip as well as hw zip from within twrp recovery
5) i put extraced recovery img to device by using "fastboot flash recovery "
Will it work like this? Or do I need to flash public and hw first and after that uninstall root from supersu?
and then in the end "fastboot oem lock" ? to get the bootloader locked and to switch off the boot message "your device cant be trusted" ?
and: I couldnt flash hw zip before as it ended up with errrors, is this why I dont have Search for updates in EMUI 5.0 anymore?
Click to expand...
Click to collapse
No. Follow the guide you linked, that's where you use those files.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
You could relock but it will say Bootloader Relocked instead of Bootloader Lock.
And if you don't plan on updating to B190 using the guide I suggest you download public and HW Data for B182 and flash those in twrp.
Can cause problems otherwise.
Flash public first. They will give errors because you're not supposed to flash them in twrp, they're official Huawei zips that are flashed using stock recovery.
ante0 said:
No. Follow the guide you linked, that's where you use those files.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
You could relock but it will say Bootloader Relocked instead of Bootloader Lock.
And if you don't plan on updating to B190 using the guide I suggest you download public and HW Data for B182 and flash those in twrp.
Can cause problems otherwise.
Flash public first. They will give errors because you're not supposed to flash them in twrp, they're official Huawei zips that are flashed using stock recovery.
Click to expand...
Click to collapse
OK and why i currently dont see menue point "search for updates" in EMUI 5.0 ? Maybe i will stay rooted as I see that xposed has now been released.
But I want to receive official OTAs anyway, but currently the full menue point for searching for updates is gone. Any idea?
tobyffm said:
OK and why i currently dont see menue point "search for updates" in EMUI 5.0 ? Maybe i will stay rooted as I see that xposed has now been released.
But I want to receive official OTAs anyway, but currently the full menue point for searching for updates is gone. Any idea?
Click to expand...
Click to collapse
Did you flash back public and HW Data for B182?
ante0 said:
Did you flash back public and HW Data for B182?
Click to expand...
Click to collapse
I was not sure which was the last I flashed during last days, B182 or B190.
However, just redownload B182 files and flashed, first public, then hw zip.
Rebooted device, "search for updates" is available again, thank you very much
But it says B182 is latest update, so OTA not available for me so far yet. How can I manually flash to latest version B190 without loosing 'Search for Update' section?
tobyffm said:
I was not sure which was the last I flashed during last days, B182 or B190.
However, just redownload B182 files and flashed, first public, then hw zip.
Rebooted device, "search for updates" is available again, thank you very much
But it says B182 is latest update, so OTA not available for me so far yet. How can I manually flash to latest version B190 without loosing 'Search for Update' section?
Click to expand...
Click to collapse
You can with that guide i linked a couple of posts back. You can't flash update.zip in twrp, you have to use that guide to flash it. It's pretty straightforward. Download HWOTA BASE, HWOTA WINDOWS and HWOTA MHA (Mate 9), extract all to the same folder (C:\hwota is a good location). Download the files for B190 i linked a couple of posts back. Rename public data zip to update_data_public.zip.
Rename hw data zip to update_all_hw.zip, place them and update.zip in the update folder, run bat (if windows) or sh (Linux) then do what the prompts say. When it asks pick same brand update, then script update folder. It will transfer files for you. Bootloader will be locked when you're done.
ante0 said:
You can with that guide i linked a couple of posts back. You can't flash update.zip in twrp, you have to use that guide to flash it. It's pretty straightforward. Download HWOTA BASE, HWOTA WINDOWS and HWOTA MHA (Mate 9), extract all to the same folder (C:\hwota is a good location). Download the files for B190 i linked a couple of posts back. Rename public data zip to update_data_public.zip.
Rename hw data zip to update_all_hw.zip, place them and update.zip in the update folder, run bat (if windows) or sh (Linux) then do what the prompts say. When it asks pick same brand update, then script update folder. It will transfer files for you. Bootloader will be locked when you're done.
Click to expand...
Click to collapse
Did like described, when it comes to "update should install automatically" it reboots into erecovery, but Software install failed!
The update package does not exists please download the package again
But all 3 files are within the script folder and named correctly i think, pls see my attached screenshot
tobyffm said:
Did like described, when it comes to "update should install automatically" it reboots into erecovery, but Software install failed!
The update package does not exists please download the package again
But all 3 files are within the script folder and named correctly i think, pls see my attached screenshot
Click to expand...
Click to collapse
Are they in the update folder? I think I see the update.bat file there.
Put them in the update folder (for example c:\hwota\update\)
ante0 said:
Are they in the update folder? I think I see the update.bat file there.
Put them in the update folder (for example c:\hwota\update\)
Click to expand...
Click to collapse
yes, that was my fault.
Put to update folder and run again, update was running and finished with 100%. phone rebooted loaded very long. Now android is broken. I see my background image, but cannot do anything it is like hanging hanging hanging, everyhting very slow, like it is loading much of information. rebooted phone and waited some more time. seems now it is working and I am on B190. Now, i have to unlock bootloader again and install supersu again =)
thx for your help so far.
btw: u dont have any solution for my previous posted problem with my twrp backup, dont you? restoring twrp backup ends up in lock screen with pattern which I cant remember. Android Device Manager from PC browser can communictae with the phone but it does not offer me to set a new pin. Do you have any other method in mind how I can go on?

[GUIDE] Manual Update P20 PRO with HuRUpdater and TWRP

If you have unlocked bootloader and TWRP, you can flash a newer firmware using HuRUpdater
This steps can be risky for your device if you don't know what you are doing, so try to read some guide about flashing first
before attempt these operations if you are a new to these things.
I don't take any responsability of catastrophic failures and loss of data.
-- I did a titanium backup before the upgrade, but in my case no restore was needed as all data were retained.
In this simple update no factory reset was triggered.
Please read the HUrupdater thread also for more informations.
- Install Unofficial TWRP by Pretoriano80
- Download HuRUpdater 0.3 and put it in a folder in your sdcard
-Search the firmware for your device with Firmware Finder
Make sure you download the correct firmware version for your device (type, region code)
wrong firmware can brick your device
I used updated firmware files APPROVED for my device checked with firmware finder app.
I don't know if flashing NOT APPROVED files will harm your device. You have been warned.
I successfully updated my device from CLT-L29C636B130 to CLT-L29C636B131
***Don't try to rebrand your phone with this method***
- Use FullOTA-MF images of the firmware and download the 3 files needed
in my case:
update.zip
update_data_full_public.zip
update_full_CLT-L29_hw_spcseas.zip
- rename the 3 files to:
update.zip
update_data_public.zip
update_all_hw.zip
and put the files in the same folder with HuRUpdater 0.3
(optional)
- The Update will overwrite your TWRP custom recovery so to retain it automatically rename the TWRP IMAGE
twrp_clt_0.1.img to recovery.img and put in the same folder with others files.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Remove all security locks from your phone before rebooting to TWRP.
Go to System- Developer Options
Disable Screen lock (third row)
this will suffice to remove the security locks of the phone (sequences, pin,fingerprints)
-Reboot to TWRP
If you are rooted, remove Magisk first with its uninstaller. I don't know if it's needed but better don't have things like that
messing around during the update. You can reroot later anyway.
-Go to the folder with the files and flash the system using the HuRUpdater_0.3.zip ONLY
That great tool will do all the job needed. After system, it will reflash the TWRP recovery IMG you previoulsly renamed
overwriting again the stock ramdisk_recovery that comes with the firmware.
It will take some minutes, don't panic and let the process end.
You will see some red errors but don't worry,it's fine
- Reboot in your TWRP to check (from inside TWRP , reboot - recovery, be sure not to have a usb cable plugged or it will trigger stock EMUI e-recovery)
- Wipe dalvik and cache
- Reroot new system with Magisk
-Reboot to system and restore the security lock in developer options
- Restore your fingerprints and pins
- Enjoy the update.
Thanks to @zxz0O0 for this great Tool, works good on P20 pro too.
And obviously @Pretoriano80 for his recovery.
Reserved
Working adb sideload?
If an update is already approved by Huawei, can we just download the firmware through HFF and place it in the appropriate folder, go to SYSTEM to check for updates, and then install it?
mangusZen said:
If you have unlocked bootloader and TWRP, you can flash a newer firmware using HuRUpdater
This steps can be risky for your device if you don't know what you are doing, so try to read some guide about flashing first
before attempt these operations if you are a new to these things.
I don't take any responsability of catastrophic failures and loss of data.
-- I did a titanium backup before the upgrade, but in my case no restore was needed as all data were retained.
In this simple update no factory reset was triggered.
Please read the HUrupdater thread also for more informations.
- Install Unofficial TWRP by Pretoriano80
- Download HuRUpdater 0.3 and put it in a folder in your sdcard
-Search the firmware for your device with Firmware Finder
Make sure you download the correct firmware version for your device (type, region code)
wrong firmware can brick your device
I used updated firmware files APPROVED for my device checked with firmware finder app.
I don't know if flashing NOT APPROVED files will harm your device. You have been warned.
I successfully updated my device from CLT-L29C636B130 to CLT-L29C636B131
***Don't try to rebrand your phone with this method***
- Use FullOTA-MF images of the firmware and download the 3 files needed
in my case:
update.zip
update_data_full_public.zip
update_full_CLT-L29_hw_spcseas.zip
- rename the 3 files to:
update.zip
update_data_public.zip
update_all_hw.zip
and put the files in the same folder with HuRUpdater 0.3
(optional)
- The Update will overwrite your TWRP custom recovery so to retain it automatically rename the TWRP IMAGE
twrp_clt_0.1.img to recovery.img and put in the same folder with others files.
- remove all security locks from your phone before rebooting to TWRP.
Go to System- Developer Options
Disable Screen lock (third row)
this will suffice to remove the security locks of the phone (sequences, pin,fingerprints)
-Reboot to TWRP
-If you are rooted, remove Magisk first with its uninstaller. I don't know if it's needed but better don't have things like that
messing around during the update. You can reroot later anyway.
-Go to the folder with the files and flash the system using the HuRUpdater_0.3.zip ONLY
That great tool will do all the job needed. After system, it will reflash the TWRP recovery IMG you previoulsly renamed
overwriting again the stock ramdisk_recovery that comes with the firmware.
- It will take some minutes, don't panic and let the process end.
You will see some red errors but don't worry,it's fine
- Reboot in your TWRP to check (from inside TWRP , reboot - recovery, be sure not to have a usb cable plugged or it will trigger stock EMUI e-recovery)
- Wipe dalvik and cache
- Reroot new system with Magisk 16.4
-Reboot to system and restore the security lock in developer options
- restore your fingerprints and pins
- enjoy the update.
Thanks to @zxz0O0 for this great Tool, works good on P20 pro too.
And obviously @Pretoriano80 for his recovery.
Click to expand...
Click to collapse
ekremxx said:
Working adb sideload?
Click to expand...
Click to collapse
I have not tried that, it depends on the TWRP recovery, let us know if you try
sarichter said:
If an update is already approved by Huawei, can we just download the firmware through HFF and place it in the appropriate folder, go to SYSTEM to check for updates, and then install it?
Click to expand...
Click to collapse
I really don't know, and I don't think it will work.
As far as I know this is the only manual update method for now.
I just updated to unapproved .150 for my c636 and all seems fine
If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.
sishafie said:
If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.
Click to expand...
Click to collapse
eRecovery is not replaced.
To enter there try other volume button or with a cable plugged
Not working adb sideload... How I can install I not know...not have my phone micro SD card slot...puff
sishafie said:
If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.
Click to expand...
Click to collapse
when booting there is a screen prompting to whether you want to go to eRecovery by pressing up or just boot into system and something ike that
---------- Post added at 04:23 PM ---------- Previous post was at 04:23 PM ----------
ekremxx said:
Not working adb sideload... How I can install I not know...not have my phone micro SD card slot...puff
Click to expand...
Click to collapse
why you want to do sideload ? guide clearly explained to install it using TWRP.
if you dont have TWRP, then install it first
I install twrp but how can I install whitour sd card I not have sd card slot my Huawei p20 pro one SIM card join no have sd card slot how I can install i not know.. when I try install abd sideload hrudader say cant find update.zip
update_data_public.zip
update_all_hw.zip
ekremxx said:
I install twrp but how can I install whitour sd card I not have sd card slot my Huawei p20 pro one SIM card join no have sd card slot how I can install i not know.. when I try install abd sideload hrudader say cant find update.zip
update_data_public.zip
update_all_hw.zip
Click to expand...
Click to collapse
The guide never said that you need sdcard
it said, that u need to put all those three files in same folder with the HuruUpdater.zip , and of course you can put it in your internal storage
i wont explain anything here. you better re-read the whole main post, as it already very clear
- put all files in one folder
- reboot to twrp
- flash huruupdater.zip
- boot to system
- reboot to twrp
- flash magisk to reroot
which step exactly that not understandable ? :silly:
I can install that's style orjinal filmware ty so much
Forgive me if this is not the appropriate forum, one question:
I have the Huawei P20, for this phone I only have 2 firmware files, the "Update .zip" and the "update_full_EML_L09_hw_eu.zip ".
Can't find the "update_data_public.zip"
Can I install the new firmware with Hurupdater anyway ? Thanks in advance.
Roberto
moghetto said:
Forgive me if this is not the appropriate forum, one question:
I have the Huawei P20, for this phone I only have 2 firmware files, the "Update .zip" and the "update_full_EML_L09_hw_eu.zip ".
Can't find the "update_data_public.zip"
Can I install the new firmware with Hurupdater anyway ? Thanks in advance.
Roberto
Click to expand...
Click to collapse
You should check and ask at P20 and HURupdater threads.
I don't know about P20.
Hello! Thank you very much for this tutorial .. A question.. I am in Chipset-boston 8.1.0. 001 (01DL) I have the bootloader open, just by installing the recovery that you say in the tutorial and then the other steps, I would not have a problem, right?
can I downgrade firmware safely with this method? im on 150 and want to go back to 130
Ferezesal19 said:
Hello! Thank you very much for this tutorial .. A question.. I am in Chipset-boston 8.1.0. 001 (01DL) I have the bootloader open, just by installing the recovery that you say in the tutorial and then the other steps, I would not have a problem, right?
Click to expand...
Click to collapse
You should not have problem, unless you are trying to rebrand.
Allesa said:
can I downgrade firmware safely with this method? im on 150 and want to go back to 130
Click to expand...
Click to collapse
I don't know about downgrading and I would not raccomend it
mangusZen said:
You should not have problem, unless you are trying to rebrand.
Click to expand...
Click to collapse
Thanks you. Only i want to Update... What firm you recommend That improves the duration of the battery?

Updating your P20 Pro (This can be used to restore a bricked P20 Pro)

My daily driver is AOSCP (CypherOS project) P20 pro ROM, but sometimes I flip back to stock every time there is a new Huawei P20 Pro update. Recently they released (9.0.0.213) so I removed the custom ROM and installed stock (9.0.0.213) without issues, just to see how it feels, whats new and such then jump back to custom. These steps helped me when I bricked my phone.
(Bootloader must be unlocked)
- Use at your own risk.
To jump to stock.
1) Go HERE and type in your phone model and click FIND MODEL button. Then click Filelist, copy and paste the first two links to your browser, this will download the main packages.
2) Extract the update.app file from the Update.zip file you just downloaded.
3) Use EMUI extractor application to extract the image files from the Update.app file.
4) Download Re-Flash, place all the images in the Re-Flash folder and flash as many images as you can. (This step simply puts your phone in enough working order for the update to complete)
Open the "cmd-here" file and start flashing:
Example:
fastboot flash recovery_ramdisk recovery_ramdis.img
fastboot flash cust cust.img
fastboot flash recovery_vbmeta.img recovery_vbmeta.img
fastboot flash kernel kernel.img
(Keep going - some will flash others won't)
5) type: Fastboot reboot, quickly unplug your phone and hold the volume up button, this will boot into EMUI recovery, now format data, format cache.
6) Now the two main packages you downloaded in step one, place those zip files in the folder called ZIPS-HERE, located in the Re-flash folder. Rename update_full_CLT-L29_hw_eu to update_all_hw
7) In the cmd-here window, type flash.bat
follow the steps.
Note:--------------------------------------------------------------------------------------------------------------
if the update fails you'll need a userdata.img, this image file isn't in most update.zip files. You can find it here.
Redo the steps again except this would be the last thing to do in step 4.
- fastboot flash userdata userdata.img
Okay, so I have CLT-L09C782, I updated it to 9.0.0.168 using the FunkyHuawei service. I opened Firmware Finder a while ago and I have seen some new versions of firmware there. Can I manually update from there?
aka.petteri said:
Okay, so I have CLT-L09C782, I updated it to 9.0.0.168 using the FunkyHuawei service. I opened Firmware Finder a while ago and I have seen some new versions of firmware there. Can I manually update from there?
Click to expand...
Click to collapse
I tried Firmware finder in the past, hadn't had any real luck with it whereas other have. So I really can't comment on it.

[GSI][Android 10] Install AOSP 10 on Huawei Honor 6X.

POST - v14
(This number will increase every time the post is updated.)​What's new in v14?
Corrected some simple mistakes in procedure.​Modified overall post for better UX.​
​
Spoiler: Version Changelog
What's new in v13?
Modified Gapps part in requirements to make it more clear.​Added useful information section. for Pro Noobs and Ultra Noobs like me.​​What's new in v12?
Added User Contributions and feedback section.​Added Miscellaneous recommendations section.​Modified some steps in installation procedure to make it even more noob friendly.​Linked @lmaohelp's thread.​Decreased size of text in procedure.​​​
​
This ROM is based on Android 10 GSI builds of @phhusson (Thanks a ton to him).
Thanks to @Hami_Do for his hi6250 patches.
Thanks to Huawei for making their phones nearly unbrickable .
Thanks to @Djiban for his ideas on improving the thread.
Follow this thread only if you know what you're doing. I'm not responsibe for any damage or thermonuclear wars .
Read the post completely and understand it before doing anything ATLEAST FOR THE SAKE OF MANKIND .
This thread is best viewed in PC and is Noob Friendly.
Note that I was using flux substratum theme in the screenshots. Hence, icons and colors may vary on your device.​
Spoiler: Requirements
Requirements:
Huawei Honor 6X (Unlocked Bootloader. If not, follow this post (using PotatoNV) or YouTube video.
EMUI 8 (If not, you could follow this guide, direct file : link).
GSI from link (download system-quack-arm64-aonly-vanilla.img.xz, you could try others but arm64, a-only is must).
TWRP from attchments or link or any other TWRP recovery compatible with Honor 6X EMUI 8.
Gapps(Optional, I used nano OpenGapps, NikGapps gave an error during installing, You can also try others. You can directly try the img with gapps instead of vanilla but i prefer nano gapps over vanilla).
stock recovery.
Time.
PC.
ADB and Fastboot.
Patience.
Human Brain.
ALL IN ONE GUIDE : Check it out here. It contains every thing in detail all the way from bricked device -> EMUI 2 -> EMUI 5 -> EMUI 8 -> AOSP 10 (mentioned in this post). Thanks to @lmaohelp for his effort and describing everything in detail.
Useful Information :
What on the Earth is meant by Vanilla android? -> it is the stock / pure version of android without Google apps and services.​
What is OpenGapps? Check it out at OpenGapps.org!​
What is Nano (not the mathematical 10^-9) Gapps? It is a version of Gapps with Minimal installation which means only the core part of gapps is installed with very little major apps. They can be installed later.​
What is ARM64? it is a 64 bit operating system/platform.
What on the moon is AOSP? It stands for android open source project which is the purest form of android.
NOTE : My device bootlooped whenever I tried installing Magisk. So, better stick with the PHH-SuperUser that you get out-of-the-box with the system image.
NOTE : Skip every step with gapps if you are already using img with gapps.
What isn't working :
VoLTE (can't be fixed as per my knowledge), Camera (FIXED NOW | trying to find a fix, replacing libcamxxx could help), Flashlight (FIXED NOW | also trying to find a fix, fixing camera may fix this too).
CAMERA AND TORCH HAVE BEEN FIXED. Thanks to @Hami_Do (flash the attched patch file whenever you are bored, LOL)
What's Working :
Everything except the ones mentioned above VoLTE.
*Tell me if something else isn't working.
***If you have a bricked device/messed up somewhere during the process and unable to figure out what to do, follow this guide by @lmaohelp .***​Procedure :
Make sure your device is running EMUI 8.​
Extract downloaded image using some xz extractor(7zip can also do this), copy it to pc.​
Reboot your device to TWRP recovery.​
Format the data partition {Wipe > Format data > type "yes"}​
(Optional) In TWRP, choose wipe > advanced wipe > select system, data, cache and DALVIK and format them.​
Check if your device is detected by adb using
Code:
adb devices
.​
Move the img file using adb to device
Code:
adb push -p *img-name*.img /sdcard/
(the img file must be in adb directory).​
(Optional, only if you want nano gapps over vanilla) Move Gapps in the same manner
Code:
adb push -p *gapps-name*.zip /sdcard/
(the zip file must be in adb directory).​
Install img as system image {Install > Install Image > Select > Choose system image > Swipe➡}.​
(Optional, only if you want nano gapps over vanilla) Unmount and Remount system partition. Go to wipe > advanced wipe > Choose system > resize. Flash gapps.​
Flash stock recovery(also available in attachments) with twrp in the same way. push it with adb using
Code:
adb push -p STOCK_RECOVERY_RAMDISK.img /sdcard/
and flash it with twrp as "Recovery" after choosing install image.​
Disconnect your device from PC and reboot to recovery(stock one).​
Clear cache partition and perform a factory reset(You'll get an error during factory reset but you have to do it) (your device will bootloop if wiped with twrp itself).​
Reboot, Cross your fingers and wait.​
>If you flashed gapps over vanilla, the first boot would take about 5 mins. else, it would be very fast. Subsequent boots on both are quite fast.
>Sometimes, I observed that flashing gapps from internal storage caused bootloop(this is because of corrupt zip), in such case get back to EMUI 8, repeat the process by flashing gapps from micro sd.
*you'll get a warning that something wrong with your device every time you boot it. IGNORE IT.
Spoiler: Additionals
Additionals:
> If you messed up somewhere during installation, you can always recover your device by following this guide.
> If you have the update.zip file from the above mentioned EMUI 8 folder directly, you could just directly flash it after wiping data, system and cache(use adb push or microsd to transfer update.zip to device).
>Its better to charge your device to atleast 70% before doing anything as you'll have ample of time to recover it if you messed up something. If not, you can still charge your device in eRecovery mode and twrp but i found some issues like heating up and slow charging.
>Don't forget to set ringtone, notification and other sounds from settings after booting.
Spoiler: Updates
Updates :
I was able to install magisk by flashing unSU zip from @Hami_Do 's thread on hi6250 manual fixes and then flashing phh's magisk after deleting phh-su from /system/bin/ but sadly, I wasn't able to use quickswitch for other launchers as it needs magisk version of 20.4 (min.) but phh's magisk is 19.3 and substratum theme engine is not working (due to some error). So, I'm sticking with the root that comes out of the box and I recommend you to do the same. EXTRAS : The Phone and Messaging apps that came out of the box with the GSI stopped working after installing magisk. So, you are installing magisk, just replace these system apps from LineageOS ones or delete them and install the google phone and messaging from play store.
During multiple tests (installing, modifying and testing the GSI for its stability in multiple ways), I found that you need not always go back to stock EMUI 8 if you messed up something. This works without error but if you have some time, getting back to stock EMUI 8 is still recommended before installing some other ROM/GSI.
Try not to touch the finger print sensor when you are at the setup after first boot. This is making the finger print sensor not recognisable until next reboot.
User Feedback and Contributions :
Thanks to @OrionThyHunter for his feedback and some fixes :
Using the Greenify app will stop the finger print sensor from working. FIX : Disable "Alternative Screen Off Mode".
Thanks to @[email protected] for finding out he following issues :
Adaptive Brightness Doesn't work. Flash the attachment in this post to fix it.
To pass SafetyNet, follow this post.
Miscellaneous Recommendations :
Use Google Camera Go app for photos. Its much better than the GSI's stock one.
​
Happy Flashing !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........
[email protected] said:
thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........
Click to expand...
Click to collapse
I think VoLTE can't be fixed.
For camera, you have to replace each file in /system/lib/ starting with libcam(libcamxyz...) from stock emui 8 and check each possible combination with subsequent reboots. I'm a little bit busy right now as I'm working on AOSP 11(as I believe it'll run without much problems because it has been tested on other hi6250 devices) with @Djiban. You could just do this on your own. If you find any working combination, please post it in this thread.
[email protected] said:
thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........
Click to expand...
Click to collapse
Finally, Fixed it dude(camera and torch) by replacing libraries! Found a patch that does the same thing. Updated the Original post.
Tried a lot to fix VoLTE but didn't work... will try again later.
CHECK IT OUT!
#endyourwait LOL!
Hi again, I got this installed using TWRP, and I still have TWRP installed because I don't have the stock recovery. The system boots but it is giving me an error saying encryption unsuccessful, with a button saying "erase all data" which does nothing, and I am unable to do anything.
I was having this error when I first installed EMUI 8 from EMUI 5 as well, but at least the button took me to eRecovery, where the factory reset would fail at 5-6%. Currently if I go into eRecovery and click factory reset, it just reboots and takes me to TWRP again. Also, when I go into eRecovery it asks me to reformat the partition because it is "corrupted", which somehow changes the file system for /data to f2fs, and causes the phone to be stuck on the android boot animation. When I change /data back to ext4 I am able to boot back to the screen of encryption unsuccessful.
How do I fix this issue and be able to use the phone? Attached is a screenshot of the error message the OS is giving me.
lmaohelp said:
Hi again, I got this installed using TWRP, and I still have TWRP installed because I don't have the stock recovery. The system boots but it is giving me an error saying encryption unsuccessful, with a button saying "erase all data" which does nothing, and I am unable to do anything.
I was having this error when I first installed EMUI 8 from EMUI 5 as well, but at least the button took me to eRecovery, where the factory reset would fail at 5-6%. Currently if I go into eRecovery and click factory reset, it just reboots and takes me to TWRP again. Also, when I go into eRecovery it asks me to reformat the partition because it is "corrupted", which somehow changes the file system for /data to f2fs, and causes the phone to be stuck on the android boot animation. When I change /data back to ext4 I am able to boot back to the screen of encryption unsuccessful.
How do I fix this issue and be able to use the phone? Attached is a screenshot of the error message the OS is giving me.
Click to expand...
Click to collapse
Did you flash stock recovery after flashing system image?
Get back to emui 8(if you have update.zip, you could directly flash it with twrp). Repeat the process. Flash stock recovery. Perform a factory reset. And boot it to the system for the first time. You could then flash twrp with fastboot.
***Do not do a factory reset with twrp! Its causing errors.***
Apparently it could be a faulty EMMC chip according to this website, which makes sense since TWRP is not able to mount the internal storage partition or the Dalvik / ART cache, and eRecovery is not able to reset the phone, which is a characteristic of EMMC failure, according to this website. I had to unplug the battery countless times when I was tinkering with the phone, because my power button is broken, and it definitely would've contributed to this failure according to what I have read. Well, guess I'm done with this phone lol
EDIT: Well I'm starting from scratch again but everything is installing fine so I guess nothing is wrong currently? Huawei factory reset even worked
Venkata Lochan Nune said:
Did you flash stock recovery after flashing system image?
Get back to emui 8(if you have update.zip, you could directly flash it with twrp). Repeat the process. Flash stock recovery. Perform a factory reset. And boot it to the system for the first time. You could then flash twrp with fastboot.
***Do not do a factory reset with twrp! Its causing errors.***
Click to expand...
Click to collapse
No, I don't know where to find the stock recovery file, where can I find it?
I managed to boot into EMUI 8 just fine since I did not have a password on the EMUI 5 OS before installing lol. Now I just need the stock recovery you are talking about so I can follow your steps.
do you mean, you testing ASOP 11 on honor 6x ? if yes wow......
[email protected] said:
do you mean, you testing ASOP 11 on honor 6x ? if yes wow......
Click to expand...
Click to collapse
Nope, not now. @Djiban is quite busy and for me to work, I'm not having a spare device. He'll do it when he's got free time.
I didn't find much noticeable differences between AOSP 10 and 11 execpt some ui improvements and under-the-hood improvements. So, I'll skip AOSP 11 and directly will work with AOSP 12 on future. I liked the new things introduced in android 12. So, I'll definitely work on it.
lmaohelp said:
No, I don't know where to find the stock recovery file, where can I find it?
I managed to boot into EMUI 8 just fine since I did not have a password on the EMUI 5 OS before installing lol. Now I just need the stock recovery you are talking about so I can follow your steps.
Click to expand...
Click to collapse
Do you have the update.zip file?
Or wait I'll attach one in few hours...
lmaohelp said:
Apparently it could be a faulty EMMC chip according to this website, which makes sense since TWRP is not able to mount the internal storage partition or the Dalvik / ART cache, and eRecovery is not able to reset the phone, which is a characteristic of EMMC failure, according to this website. I had to unplug the battery countless times when I was tinkering with the phone, because my power button is broken, and it definitely would've contributed to this failure according to what I have read. Well, guess I'm done with this phone lol
EDIT: Well I'm starting from scratch again but everything is installing fine so I guess nothing is wrong currently? Huawei factory reset even worked
Click to expand...
Click to collapse
This is because twrp on our phone doesn't support encryption-decryption things. So, they can only mount internal storage when you perform a complete data format by typing "yes".
Venkata Lochan Nune said:
Do you have the update.zip file?
Or wait I'll attach one in few hours...
Click to expand...
Click to collapse
I do, but I'm unfamiliar with how to get the recovery.img from the zip file. If you can tell me how to extract it or attach one that would be great!
lmaohelp said:
I do, but I'm unfamiliar with how to get the recovery.img from the zip file. If you can tell me how to extract it or attach one that would be great!
Click to expand...
Click to collapse
Actually, flashing it should replace twrp with stock one didn't it?
You can extract it with 7zip. It worked for me.
Venkata Lochan Nune said:
Actuall, flashing it should replace twrp with stock one didn't it?
You can extract it with 7zip. It worked for me
Click to expand...
Click to collapse
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.
lmaohelp said:
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.
Click to expand...
Click to collapse
Well you could directly flash update.zip with twrp.
Wail I'll attach it in a while. Just turned on my PC to search for it and this bloody "working on updates" came up.
lmaohelp said:
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.
Click to expand...
Click to collapse
Yeah I've faced the same problem with flashify and ofcourse other similar apps. The problem I usually get is that system partition isn't writable. After changing it to r/w, I get an error that boot image not found. (This doesn't happen in flashify, it just freezes). Not sure what the problem is maybe, huawei's anti modding measures...
This might be the stock recovery(its in between some 10 other recoveries so, not sure). Try it and inform me
EDIT : THIS IS NOT THE RIGHT ONE. STOCK RECOVERY WAS ATTACHED IN POST #1.
Venkata Lochan Nune said:
This might be the stock recovery(its in between some 10 other recoveries so, not sure). Try it and inform me.
Click to expand...
Click to collapse
I don't think that is the correct file, as I flashed it and "adb reboot recovery" just causes it to be stuck on the "your phone is unlocked" screen, and so does clicking the factory reset option in eRecovery. I tried extracting the RECOVERY_RAMDIS(K).img file and flashing it, which worked, and successfully failed (lol) to reset the phone.
EDIT: I got into the OS successfully. It is unexpectedly smooth, good job!
lmaohelp said:
I don't think that is the correct file, as I flashed it and "adb reboot recovery" just causes it to be stuck on the "your phone is unlocked" screen, and so does clicking the factory reset option in eRecovery. I tried extracting the RECOVERY_RAMDIS(K).img file and flashing it, which worked, and successfully failed (lol) to reset the phone.
EDIT: I got into the OS successfully. It is unexpectedly smooth, good job!
Click to expand...
Click to collapse
So you liked it?
And hey, attach the stock recovery for future reference if someone needs it.
Use the camera patch to fix cam and flashlight issues. It just replaces the libraries. Flash any emui 8 compatible twrp with fastboot. Take a migrate backup in case.
Google Camera GO app works like a charm and is better than the stock one so I recommended using it.
Enjoy your phone!

Categories

Resources