Develop Bugs

System messed up

Good morning,
I tried to revert back to stock as I had to send my 10 to service.
So, I took an old NAND (which was working fine when updating firmware) and restored it in TWRP. I'm S-On with unlocked bootloader.
NAND went through but then I was stuck on boot screen.....
Power + Vol down brought me back to "stock!!!recovery. From there to bootloader and then back to TWRP.
Getvar all showed me nothing, just lines without any values.
I finally flashed the MM Viper rom with a full wipe and it booted again.........with all apps and setting.
I have no clue what happened. I only want to get back to stock.

same problem as you, no idea why

Glad, I'm not the only one facing that issue. Sad we don't know what it caused.
Maybe the NAND backup does not harmonize with the newer firmware? No clue.
But now I can't handle that chaotic system.

nerodarknight said:
same problem as you, no idea why
Click to expand...
Click to collapse
Prinz069 said:
Glad, I'm not the only one facing that issue. Sad we don't know what it caused.
Maybe the NAND backup does not harmonize with the newer firmware? No clue.
But now I can't handle that chaotic system.
Click to expand...
Click to collapse
Are you on N firmware, or MM firmware?
Try find RUU for your firmware, flash that, it will clean reset your phone back to everything stock.
Btw the "stock recovery" you found by pressing power + vol down, is not recovery at all. It is download mode (same thing as fastboot mode.)
Newer HTC devices will have this enhanced Download mode from now on.
If you can find an RUU zip then just place it in SDcard and reboot to Download mode and you can easily flash the RUU without needing to run a program on your computer.
I prefer this because I use Linux at home, and RUU.exe won't work on linux.

MM firmware, but Im s-on

Prinz069 said:
MM firmware, but Im s-on
Click to expand...
Click to collapse
Perfect, it will be very straight forward then...
Find RUU for your firmware, make sure mid and cid match.
Once you flash that, relock your bootloader and send it back to HTC for service.
Your warranty won't be void.

Cant read out cid as getvar shows now values

Prinz069 said:
Cant read out cid as getvar shows now values
Click to expand...
Click to collapse
Then make an estimated guess.
You are from germany, so your phone would probably be an european variant right?
Could be a GSM unlocked variant, or a carrier unit.
Find what version your phone is, and find the RUU for that version and hope that the CID/MID matches.

What about the non working getvar command? Ill post a screenshot later.

Prinz069 said:
What about the non working getvar command? Ill post a screenshot later.
Click to expand...
Click to collapse
That i do not know, i just hope your phone is not hard-bricked.
Try to RUU until something happens.
Good luck haha

You can check your CID onscreen when in download mode.
To get there Start device with Power + Vol- pressed.
As far as I know you then could try a CID/MIP matching RUU, that has to be same or newer version then the one you're running to flash that with S-ON. But don't nail me on that.

When you say "stuck on boot screen", what, exactly, does that mean? For how long? First boot can take 20+ mins easy before hitting the "configuring app X of Y" screen.
Download mode tells you your CID, MID, firmware version, etc.
Since you're sending it back in for service, yes, RUU it (via SD card zip). It's easy and thorough.

Boot into download mode and read your firmware. If you are MM/Germany you probably have 1.95.401.X firmware (same as mine - MM/Ger/Unlocked).
Go to RUU thread and download RUU zip that is exactly or higher firmware as yours.
Rename as instructed in that thread (2PS6IMG.zip or something like that) and put it on your SDcard.
Reboot Download mode, it will detect the zip and ask if you want to flash it.
Confirm and let it reboot.

Thank you guys, you're all awesome...wish we could have a couple of drinks together:good:

Prinz069 said:
Thank you guys, you're all awesome...wish we could have a couple of drinks together:good:
Click to expand...
Click to collapse
Perfect, you have a ".401" phone.
It's an unlocked version, same as mine. (and most lol).
You could try running RUU.exe...if it doesn't work, use TWRP to mount the sdcard (internal, not the external one) and transfer the RUU.zip to your phone.
Go back into download mode and flash RUU there.

There's an RUU decrypter tool to extract the zip elsewhere in this forum.

[RESTORE STARTED]
Restore folder: '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup'
Skipping MD5 check based on user setting.
Calculating restore details...
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.info' not found.
I:Restore file system is: 'emmc'.
I:InfoManager file '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.info' not found.
I:Restore file system is: 'emmc'.
Restoring 2 partitions...
Total restore size is 4784MB
I:Restore filename is: boot.emmc.win
I:Restore file system is: 'emmc'.
Restoring Boot...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/boot.emmc.win', writing '/dev/block/mmcblk0p59'
[Boot done (2 seconds)]
I:Restore filename is: system_image.emmc.win
I:Restore file system is: 'emmc'.
Restoring System Image...
I:Reading '/external_sd/TWRP/BACKUPS/FA65XBN06916/1.95 Backup/system_image.emmc.win', writing '/dev/block/mmcblk0p62'
Truncating string cache entries.
Truncating string cache entries.
I:Error writing destination fd (No space left on device)
This is the error I got for restoring the backup, can some explain the error for me?

nerodarknight said:
I:Error writing destination fd (No space left on device)
Click to expand...
Click to collapse
Could it be that?

dj_chapz said:
you probably have 1.95.401.X firmware
Click to expand...
Click to collapse
My Build is 1.95.401 when I check in Settings, But Downloade Mode says OS is 1.30.401.

Prinz069 said:
My Build is 1.95.401 when I check in Settings, But Downloade Mode says OS is 1.30.401.
Click to expand...
Click to collapse
Then you can flash pretty much any RUU zip to go back. Best bet would be the first newer RUU than 1.30.

HTC 10 Won't let me do anything. Possibly bricked.

Good afternoon all,
Hoping someone can help me here.
*Keeps boot-looping
*Some reason i have s-on and it may be the thing preventing me to do anything through bootloader or command prompt
*When i go into recovery mode, it goes back to boot-looping
*When i put firmware onto an SD card and put it into my phone, doesnt register anything is on there or fails to install.
Is there a way to get s-off from bootloader or download mode, even command prompt?

kranksta said:
Good afternoon all,
Hoping someone can help me here.
*Keeps boot-looping
*Some reason i have s-on and it may be the thing preventing me to do anything through bootloader or command prompt
*When i go into recovery mode, it goes back to boot-looping
*When i put firmware onto an SD card and put it into my phone, doesnt register anything is on there or fails to install.
Is there a way to get s-off from bootloader or download mode, even command prompt?
Click to expand...
Click to collapse
S-off will cost ya 25$ and will be a waste of money because it won't help. Do you even know what to flash ? Tell me what is written in download mode, OS number and such. Only thing you can try is the correct RUU and hope for the best

Mr Hofs said:
S-off will cost ya 25$ and will be a waste of money because it won't help. Do you even know what to flash ? Tell me what is written in download mode, OS number and such. Only thing you can try is the correct RUU and hope for the best
Click to expand...
Click to collapse
hTC download mode
*** UNLOCKED ***
htc_pmeuh1 PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.0.8996.00007_0809
OS-2.42.710.2
Tried flash recovery in CMD and in download mode on SD card, fail due to an error 225

kranksta said:
hTC download mode
*** UNLOCKED ***
htc_pmeuh1 PVT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v20.0.0.8996.00007_0809
OS-2.42.710.2
Tried flash recovery in CMD and in download mode on SD card, fail due to an error 225
Click to expand...
Click to collapse
Did you flash a firmware or a recovery image? I'm confused about your use of terms for stuff you flashed. Got a link on what you flashed?
Try this :
Download this file : https://androidfilehost.com/?fid=817550096634779605
Rename it to : 2PS6IMG.zip (NOT 2PS6IMG.zip.zip !!!)
Copy it to the sdcard and enter download mode and flash the full RUU (follow the instructions)

Mr Hofs said:
S-off will cost ya 25$ and will be a waste of money because it won't help. Do you even know what to flash ? Tell me what is written in download mode, OS number and such. Only thing you can try is the correct RUU and hope for the best
Click to expand...
Click to collapse
Mr Hofs said:
Did you flash a firmware or a recovery image? I'm confused about your use of terms for stuff you flashed. Got a link on what you flashed?
Click to expand...
Click to collapse
I just flashed TWRP, then from there I installed supersu. Phone was successfully rooted. Then i lent it to someone for a day and he said "errr i went into some weird twrp program and then it stopped working". I told him specifically to only use it for Facebook, Messages and Calling but nooooo. He must of deleted my firmware, is this possible from TWRP?

kranksta said:
I just flashed TWRP, then from there I installed supersu. Phone was successfully rooted. Then i lent it to someone for a day and he said "errr i went into some weird twrp program and then it stopped working". I told him specifically to only use it for Facebook, Messages and Calling but nooooo. He must of deleted my firmware, is this possible from TWRP?
Click to expand...
Click to collapse
No he can't delete your firmware from within TWRP, only the rom can be deleted. If you do as described above the phone will be flashed to 100% stock but beware, all of the info will be erased from the phone. As it came out of the box the very first time !

I tried and here is a photo of the error
https://www.dropbox.com/s/npi8bgntwud6n8n/IMAG0981.jpg?dl=0

kranksta said:
I tried and here is a photo of the error
https://www.dropbox.com/s/npi8bgntwud6n8n/IMAG0981.jpg?dl=0
Click to expand...
Click to collapse
Strange!
Can you try to reflash TWRP and enter it again. If that works you can flash any custom rom

I tried still a no go. Here is a video.
https://www.dropbox.com/s/ti45qpjq2suw7ow/VIDEO0052.mp4?dl=0

kranksta said:
I tried still a no go. Here is a video.
https://www.dropbox.com/s/ti45qpjq2suw7ow/VIDEO0052.mp4?dl=0
Click to expand...
Click to collapse
There is a thing that might work but to be honest it's a shot in the dark. You could try to flash the TWRP image to the boot partition. When the phone starts it won't try to start the boot.img but the twrp.img
Once you can reach the recovery you must flash a custom rom, that will reflash the boot.img to the boot partition.

Are you sure the 2PS6IMG.zip wasn't a corrupt download?

roirraW "edor" ehT said:
Are you sure the 2PS6IMG.zip wasn't a corrupt download?
Click to expand...
Click to collapse
I got the files from XDA and I'm positive that they wouldn't be/

Mr Hofs said:
There is a thing that might work but to be honest it's a shot in the dark. You could try to flash the TWRP image to the boot partition. When the phone starts it won't try to start the boot.img but the twrp.img
Once you can reach the recovery you must flash a custom rom, that will reflash the boot.img to the boot partition.
Click to expand...
Click to collapse
I gave it a shot and unfortunately that didn't work either. If i can just somehow get to S-OFF state, I will be able to install any rom through the bootloader. Any ways of getting S-OFF on bricked device?

kranksta said:
I got the files from XDA and I'm positive that they wouldn't be/
Click to expand...
Click to collapse
It doesn't matter where you got them from. Downloads can get corrupted coming from anywhere. I'm not saying the files supplied are corrupted, I'm saying it's possible that your download of the file(s) may be corrupted.
If a MD5 or other kind of hash is provided for the download, use a program on the PC or app on the phone to see if the hash if the file you downloaded matches the hash that's provided for the download. If they don't match, then your file is corrupted.
This is a very common thing and should be the first thing you should check, when a hash is provided, if you have problems with flashing anything on the phone.
I don't necessarily check the hash of every single file I download for my phone, but I do of the ones that are the largest and/or most critical. Checking the hash can save a lot of trouble of trying to figure out what's wrong when there's no possibility of getting something working because the download is corrupted.
I check the hash right on the phone because even if you download something on the PC and verify it's correct, when you transfer it to the phone it can be corrupted that way, too. I use @scary alien 's Android File Verifier (AFV) https://forum.xda-developers.com/showthread.php?t=826001. It's also in the Play Store. There are also Android file managers that have built-in hash generating/checking capability.

Ok, here is a link to an image with all the files i have https://www.dropbox.com/s/9zlju4izi19a75a/IMAG0982.jpg?dl=0
Where should i start? I can do .img files and a few others, just not .zip files. I can't do a single thing in bootloader due to S-ON. what should I extract? What file in the extraction should I use and also where should I flash it to?
System?
Data?
Boot?
Recovery?
Cache?
Misc?
Thanks again, as soon as this is fixed, there is a donation coming to XDA Developers as a token of my appreciation.

kranksta said:
Ok, here is a link to an image with all the files i have https://www.dropbox.com/s/9zlju4izi19a75a/IMAG0982.jpg?dl=0
Where should i start? I can do .img files and a few others, just not .zip files. I can't do a single thing in bootloader due to S-ON. what should I extract? What file in the extraction should I use and also where should I flash it to?
System?
Data?
Boot?
Recovery?
Cache?
Misc?
Thanks again, as soon as this is fixed, there is a donation coming to XDA Developers as a token of my appreciation.
Click to expand...
Click to collapse
I'm out of the blue here. If the 710 RUU doesn't work i don't know what would work. Usually the full RUU is the last resort to completely flash the device.

Bummer..... Thanks anyway.

kranksta said:
Bummer..... Thanks anyway.
Click to expand...
Click to collapse
Last thing i can think of is to relock the bootloader and run the full 2.42.710 ruu again. That's all from my end. Sorry......

Mr Hofs said:
Last thing i can think of is to relock the bootloader and run the full 2.42.710 ruu again. That's all from my end. Sorry......
Click to expand...
Click to collapse
I seem to be (what i think) 1 step closer.
https://www.dropbox.com/s/tw4t53ykxmzjh4z/IMAG1003.jpg?dl=0
This was after Trying TWRP again, When i boot the phone normally, i dont get the Developers message under my htc (still doesnt boot though) and I noticed that adb can't find my device which tells me USB degging must have been turned off before he ruined my phone. Any other possible way to enable USB debugging Through CMD/PowerShell?
If this helps even:
(bootloader) kernel: lk
(bootloader) product: htc_pmeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: *********784
(bootloader) current-slot:
(bootloader) imei: ************644
(bootloader) version-main: 2.42.710.2
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS620000
(bootloader) cid: OPTUS001

I'm on twrp, not exact sure how but i'm here! ?

Could somebody help me?downgrade emui5

:crying:Last night, I installed the Android 8 update package on the forum.
Halfway through, an error is displayed and then exit.
I tried eRecovery and Hisuite, but all failed.
I tried it and found that the original recovery partition became recovery_ramdisk. It looks like the partition has changed.
What can I do to be able to return to emui5?
I have imagined "fastboot flashall", but I do not know how? Forgive my lame English

zzkeier said:
:crying:Last night, I installed the Android 8 update package on the forum.
Halfway through, an error is displayed and then exit.
I tried eRecovery and Hisuite, but all failed.
I tried it and found that the original recovery partition became recovery_ramdisk. It looks like the partition has changed.
What can I do to be able to return to emui5?
I have imagined "fastboot flashall", but I do not know how? Forgive my lame English
Click to expand...
Click to collapse
recovery_ramdisk. is the new name of recovery partition. EMUI8/Oreo flashing has started means the partitions etc have changed already so right now you can't go back to EMUI 5 as rollback images are not available yet. You can try to flash again properly with proper download for your specific model. I guess you are missing some echo commands.

thank you very much
SVR said:
recovery_ramdisk. is the new name of recovery partition. EMUI8/Oreo flashing has started means the partitions etc have changed already so right now you can't go back to EMUI 5 as rollback images are not available yet. You can try to flash again properly with proper download for your specific model. I guess you are missing some echo commands.
Click to expand...
Click to collapse
I extract the update.app(oreo) file and then i flash the system.img. Now it works..Thank you

hey how did you did that?
zzkeier said:
I extract the update.app(oreo) file and then i flash the system.img. Now it works..Thank you
Click to expand...
Click to collapse
I also have similar problem I installed different model rom using firmware finder and now I can only use my phone when I unlock bootloader when I lock it it will not open directly go into the erecovery and nothing is working I tried everything twrp,erecovery,force updating nothing worked all failed.please help

shrey2204 said:
I also have similar problem I installed different model rom using firmware finder and now I can only use my phone when I unlock bootloader when I lock it it will not open directly go into the erecovery and nothing is working I tried everything twrp,erecovery,force updating nothing worked all failed.please help
Click to expand...
Click to collapse
well,I flash the system.img by fastboot,and then make a factory reset.Bootloader unlock needed.

i have the same problem
I tried to upgrade phone to Oreo after unlock, in update progress it got error and restart phone! Now it shows:
Code:
Error Mode
Attention!
Please update system again
Error!
Func No : 11 (recovery image)
Error No : 2 ( load failed )
I just have access to fastboot
i did flash system.img and tried install twrp on ramdisk recovery. but always same
:crying::crying::crying::crying:

Bricked my phone, please help

I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l

jetzecazemier said:
I upgraded my phone to android EMUI8 and tried to install the RR 8.1 ROM but my device wouldn't boot up. Then I tried to reflash the stock system.img but it won't let me. I don't have TWRP on my phone but I can acces fastboot. Does anyone know what to do? Thanks in advance :^l
Click to expand...
Click to collapse
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?

mrmazak said:
What is it you mean , it won't let you. Does it give a message. Failed?
Are you at frp locked?
Click to expand...
Click to collapse
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error) I am frp unlocked by the way.

jetzecazemier said:
Well when I try to flash the stock 8.0 system.img it gives me a "Invalid sparse file format at header magi" and when I try to flash TWRP it gives me a "FAILED (remote: partition length get error)
Click to expand...
Click to collapse
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447

mrmazak said:
Ok, that does not seem too bad, yet.
I suppose you are using system.img downloaded from web.
That image has given many that same error.
Best to use your system.img.
And the error flashing twrp, is common when using the nougat command or nougat recovery on Oreo.
Solutions.
Find your firmware on pro-teammt
http://pro-teammt.ru/firmware-database/?firmware_model=Bnd-&firmware_page=0
Then download update.zip
Extract files.
Get hauwei update extractor.
https://www.google.com/url?sa=t&sou...FjAAegQIARAB&usg=AOvVaw0xkKEyI85nY9x4Fjr1AWJl
Extract the system.img
Then fastboot flash it.
Recovery:
Oreo command== fastboot flash recovery_ramdisk twrp_ramdisk
Twrp name depends on version used. I use build 4 from here
https://forum.xda-developers.com/p10-lite/development/recovery-twrp-3-2-1-0-t3783447
Click to expand...
Click to collapse
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917

jetzecazemier said:
Okay so I've downloaded the latest firmware for my model but when I try to extract the update.app inside of the update.zip file the huawei zip extractor gives me "RECOVERY_RAMDIS.img: Invalid header crc - Expected: 15200 Got: 44917
Click to expand...
Click to collapse
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.

mrmazak said:
yes there is a bug either in the extractor or the update files. they all do it. Go to the settings tab and take check mark off verify header.
Click to expand...
Click to collapse
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?

jetzecazemier said:
I flashed the system.img but now the phone bootloops. It could be possible I got the wrong system.img because I don't know exactly what firmware my phone was on before I messed up. I only know it was EMUI8. Is there a way to completely reflash everything?
Click to expand...
Click to collapse
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.

mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
Alright, I'll try that before I have a look at that thread

mrmazak said:
Yes. I have guide thread here for that.
https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
But also wipe in factory reset from stock recovery may solve the bootloop.
Click to expand...
Click to collapse
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?

jetzecazemier said:
I tried rebooting to stock recovery in order to factory reset but it only shows me the update, power off and reboot options so no factory reset possibility. I read through the entire thread you linked here but I'm very confused as to what to do with the full OTA file. I'm on a broken EMUI8 that bootloops and I'd like to clean flash EMUI8 again so I can flash an AOSP Oreo rom after that. What do I do?
Click to expand...
Click to collapse
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip

mrmazak said:
Just made updates to guide last night. I think it is worded simple now.
Download my update "package" from step E
Extract it to a folder on your PC.
You are on emui8, so copy the HWOTA folder from the extracted zip to your sdcard
Also put hwota-update-7-8-auto.zip on sdcard.
Put the three (3) update files from pro-teammt.ru in the HWOTA8 folder on your sdcard
Put card into phone
Boot into twrp
Select install
Choose sdcard as source
Install hwota-update-7-8-auto.zip
Click to expand...
Click to collapse
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?

jetzecazemier said:
So far so good but the FULLOTA update file I got from that website only has one file (update.zip) Do I need to extract that? And if so, what 3 files do I put on my sdcard?
Click to expand...
Click to collapse
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder

mrmazak said:
No do not extract it.
On that site, next to link for update file, is "file list"
Click this. It gives links for all three files.
Put those three zip files into hwota folder
Click to expand...
Click to collapse
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.

jetzecazemier said:
Alright, I got it! Now I need to flash TWRP but the executable to install TWRP says my adb drivers are outdated. I have the minimal fastboot and adb installation from XDA.
Click to expand...
Click to collapse
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer

mrmazak said:
That should be fine.
Usually means you have other adb also , probably from other tool.
If you have twrp , not need to use the terp recovery installer
Click to expand...
Click to collapse
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.

jetzecazemier said:
Well the problem is I don't have TWRP and none of the versions i've tried to install work. The installer doesn't work either, it says closing adb daemon and stays on that.
Click to expand...
Click to collapse
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar

mrmazak said:
Each step of the tool I put pause.
So it stopped on command and not closed.
Press spacebar
Click to expand...
Click to collapse
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?

jetzecazemier said:
Dude, you're the man! I got my device up and running again. I'll probably stay on EMUI8 since it's more stable than the current AOSP rom. I wanna root it tho so can I just use the lazy recovery tool to install twrp and simply install magisk?
Click to expand...
Click to collapse
Yes.
The lazy tool has recovery with encryption working

I got it working on EMUI8 but I decided to flash the aosp rom cuz i prefer stock android. Can't seem to get twrp to install tho. I keep getting "1 was unexpected at this time"

ERROR MODE Attention! Please update system again.

Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system

mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore

Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.

Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..

mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (

Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595

mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.

Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)

mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:

Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are

Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.

mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse

Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?

IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)

mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.

mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising

IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"