Related
Hi, I was wondering if someone could make a stock img file of ww 2.13.40.13. I seem to get system errors with the pre-rooted version and it stops me from flashing back to stock with the downloaded stock files (they come as a zip file).
Even if you could send me in the right direction to make one myself, that would be helpful.
Fixed it without the image file.
Just to let others know how,
Connected via ADB and erased system, boot.img and droid_boot.img then reflashed WW versions... All working fine now but was a few hours of frustration and hair pulling... Honestly, I look like Lex Luthor...
Same problem but didn't understand your procedure
Thank you for your solution but I didn't understand
I had the same problem : I rooted my phone by flashing pre-rooted system.img. It worked but now I want to be able to update OTA. So I need to replace pre-rooted system.img with stock one.
Can you please explain how you "erased system, boot.img and droid_boot.img then reflashed WW versions"?
I tried the following : fastboot erase system, fastboot erase cache, and then adb sideload UL-Z00A-WW-2.13.40.13-user.zip with official firmware downloaded from asus.com. But now my phone is blocked on black boot screen "ASUS in search of incredible, powered by android". I can only boot to recovery. Can you repair my phone without wiping data? Thank you.
Not even any clue
So after hours of searches, the only solution I found was to flash a pre-rooted system.img back. My phone boots again normally.
But I don't have any solution to my first problem.
When I try to flash official firmware, I do:
1. In phone recovery menu : apply adb update
2. In PC terminal : adb sideload UL-Z00A-WW-2.13.40.13-user.zip
3. At around 52% transfer, error displayed on phone :
Can't install this package (Wed Apr 1 00:14:20 CST 2015) over newer build (Fri May 29 00:14:18 CST 2015)
E:Error in sideload/package.zip
(Status 7)
Installation aborted.
Has anyone succeeded in getting back to a stock system after flashing a pre-rooted one? I searched in many thread and did not found any solution.
remidem said:
So after hours of searches, the only solution I found was to flash a pre-rooted system.img back. My phone boots again normally.
But I don't have any solution to my first problem.
When I try to flash official firmware, I do:
1. In phone recovery menu : apply adb update
2. In PC terminal : adb sideload UL-Z00A-WW-2.13.40.13-user.zip
3. At around 52% transfer, error displayed on phone :
Can't install this package (Wed Apr 1 00:14:20 CST 2015) over newer build (Fri May 29 00:14:18 CST 2015)
E:Error in sideload/package.zip
(Status 7)
Installation aborted.
Has anyone succeeded in getting back to a stock system after flashing a pre-rooted one? I searched in many thread and did not found any solution.
Click to expand...
Click to collapse
Apparently you can unroot through supersu. This should then allow OTA updates...
Already tried
ultramag69 said:
Apparently you can unroot through supersu. This should then allow OTA updates...
Click to expand...
Click to collapse
No I already tried to unroot via supersu, I have the same issue. As said in thread
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
"If you root via*METHOD 1*you can update SuperSu app as well as update binaries but*PLEASE DON'T apply any OTA updateas the phone*WILL GET STUCK IN A BOOTLOOP...Manually flash the firmware via adb..."
But it is not written how to revert METHOD 1 root.
remidem said:
No I already tried to unroot via supersu, I have the same issue. As said in thread
http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
"If you root via*METHOD 1*you can update SuperSu app as well as update binaries but*PLEASE DON'T apply any OTA updateas the phone*WILL GET STUCK IN A BOOTLOOP...Manually flash the firmware via adb..."
But it is not written how to revert METHOD 1 root.
Click to expand...
Click to collapse
From what I did, the pre-root.img was fine to OTA with as long as you don't update supersu... I flashed a pre-root.img on then applied the OTA through a 32gb or FAT32 formatted sd card and it worked fine, also took out root so you will need to put back in there if you want it....
Impossible to update with sdcard
ultramag69 said:
From what I did, the pre-root.img was fine to OTA with as long as you don't update supersu... I flashed a pre-root.img on then applied the OTA through a 32gb or FAT32 formatted sd card and it worked fine, also took out root so you will need to put back in there if you want it....
Click to expand...
Click to collapse
Thank you for your reply. I tried OTA update with sdcard:
1) In Settings/About/Software information, my current version is 2.13.40
2) I dowloaded, from http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999 update from 2.13 to 2.14
3) Copied to external sd, in root folder, and renamed zip to MOFD_SDCARD.zip
4) Rebooted in recovery
5) Update failed. Here is my log:
Finding update package...
I:Update location: /sdcard/MOFD_SDUPDATE.zip
Opening update package...
E:file path:/sdcard/MOFD_SDUPDATE.zip
Installing update...
script aborted: Package expects build fingerprint of asus/WW_Z00A/Z00A:5.0/LRX21V/2.13.40.13_20150401_8390_user:user/release-keys or asus/WW_Z00A/Z00A:5.0/LRX21V/2.14.40.19_20150415_9660_user:user/release-keys; this device has asus/WW_Z00A/Z00A:5.0/LRX21V/2.18.40.12_20150529_9543_user:user/release-keys.
Package expects build fingerprint of asus/WW_Z00A/Z00A:5.0/LRX21V/2.13.40.13_20150401_8390_user:user/release-keys or asus/WW_Z00A/Z00A:5.0/LRX21V/2.14.40.19_20150415_9660_user:user/release-keys; this device has asus/WW_Z00A/Z00A:5.0/LRX21V/2.18.40.12_2015
E:Error in /sdcard/MOFD_SDUPDATE.zip
(Status 7)
SD Installation aborted.
This is because the version of system.img is 2.18 and the fimware version is 2.13.
Indeed I have 2 choices:
- override system with a system.img in version 2.13, but I cannot find any.
- try to apply OTA update 2.17 to 2.18 or 2.18 to 2.19 but it seems risky.
Finally I found!!! I think that a version of the firmware is tagged in system partition and another version (classically the same) is tagged in data partition (this is the one you see in Parameters -> About -> Firmware version). When I wanted to flash a firmware the same version as the one written in parameters (2.13), my phone refused to downgrade because the version of system was higher (2.18). So I had to format the system partition, apply update with official 2.18 firmware. And it worked! My phone was unrooted and I could apply method 3 root.
My issue occurred because I made the following:
1) bought a phone with a 2.13 firware
2) used it for months, applied OTA updates until 2.18
3) flashed a 2.18 pre-rooted system.img
4) used it for weeks until a made an update of supersu
5) my phone couldn't boot any more, so I wiped data (I could avoid that, if I knew!). It made a factory reset, ie get back firmware to 2.13, but system was still in 2.18
Here is the procedure to revert a phone flashed with a pre-rooted system.img (to sell it, send back to warranty, or root with another method):
1) Download official firmware from asus website in the same or higher version of your pre-rooted system.img. Do not rely on version in Parameters -> About -> Firmware version. Or simply download the latest version.
2) In your phone bootloader, enter the following commands with your PC:
fastboot erase system (I'm not sure it is necessary)
fastboot format system
3) With your phone, go into recovery menu, then to "Update with adb"
4) With your PC, go to the directory where you downloaded the firmware as zip, and enter the following command: adb sideload nom_du_fichier_teléchargé.zip
5) It takes about an hour
6) You can reboot
After that I used method 3 to root again, so that I can now OTA update exactly the same way I used to do before rooting. Moreover, I think I can update supersu as well.
tried this method, and it fails with a /sideload/package.zip error using the .18 zip. Trying to unlock as i took the .22 update... root works fine though
wrecklesswun said:
tried this method, and it fails with a /sideload/package.zip error using the .18 zip. Trying to unlock as i took the .22 update... root works fine though
Click to expand...
Click to collapse
Someone said you need to use fastboot to flash droidboot.img, boot.img, system.img and recovery.img to go back to an older version. Not sure if this works as I unlocked bootloader when I had the chance.
If you can't then you might have to wait for the "Official" unlock tool but ASUS will know and you will be out of warranty.
ultramag69 said:
Hi, I was wondering if someone could make a stock img file of ww 2.13.40.13. I seem to get system errors with the pre-rooted version and it stops me from flashing back to stock with the downloaded stock files (they come as a zip file).
Even if you could send me in the right direction to make one myself, that would be helpful.
Fixed it without the image file.
Just to let others know how,
Connected via ADB and erased system, boot.img and droid_boot.img then reflashed WW versions... All working fine now but was a few hours of frustration and hair pulling... Honestly, I look like Lex Luthor...
Click to expand...
Click to collapse
Can you please post the complete steps for the fix! Stuck here for hours, you wouldn't want to look let Lex Luthor
kamranyusuf said:
Can you please post the complete steps for the fix! Stuck here for hours, you wouldn't want to look let Lex Luthor
Click to expand...
Click to collapse
VERY IMPORTANT - Make sure you have checked the MD5 checksum on the boot, droid_boot and recovery image files as these are definitely needed to boot phone. If these are corrupt then you can brick your phone... You have been warned...
Download firmware from here-http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
It is pre-rooted but the other files needed are included in the folder.
2. Put phone in fastboot mode and erased droid_boot.img, boot.img, recovery.img and system.img using command "fastboot erase (put choice here)"
3. Flash the files I just erased back on using fast boot - "
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
This got me the pre-rooted 2.13.40.13. As the supersu has been inserted it is fine to use OTA to update, just make sure you don't update supersu before the OTA flash.
Good luck....
And may you retain a strand or 3 of hair like Homer Simpson....
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"
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"
Hello, i have bricked my phone after an hurupdate, i dont know why but the phone have suddenly turn off during twrp hurupdater process and now i can't turn on the phone, i can plug in my pc & he recognize him as "fastboot devices" but when i try to flash something or unbrick via multi tool nothing happen (FAILED (remote: Command not allowed))
I can't do anything now.. Please help me !
Albanheraibi said:
Hello, i have bricked my phone after an hurupdate, i dont know why but the phone have suddenly turn off during twrp hurupdater process and now i can't turn on the phone, i can plug in my pc & he recognize him as "fastboot devices" but when i try to flash something or unbrick via multi tool nothing happen (FAILED (remote: Command not allowed))
I can't do anything now.. Please help me !
Click to expand...
Click to collapse
Erecovery has started working for some people. you can try that
mrmazak said:
Erecovery has started working for some people. you can try that
Click to expand...
Click to collapse
Nope .. nothing work ..
Anyone know how to unbrick ? ..
I think i have flashed the wrong update, i have bndl21 & i have flashed the bndl22 or bndal10, my phone is dead ?
Albanheraibi said:
I think i have flashed the wrong update, i have bndl21 & i have flashed the bndl22 or bndal10, my phone is dead ?
Click to expand...
Click to collapse
Shouldn't be, at least not from that, not completely.
Was this the first condition, or an added problem?
I think best thing to try is the service ROM.
This one is BND-L21C432..
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.. If this is not the correct version for your honor 7x
Now with dc phoenix i have restore the fastboot and the erecovery, i can flash all i want but nothing happens, just boot loop at "your phone is not trusted" screen.
I was on catuva's rom before brick and now i have the catuva splashboot screen even after full firmware retore by dc phoenix.
When i try to flash in twrp i see lot of errors related to partition table (invalid argument cust, odm, sytsem etc) it seems the partition table have a problem..
The DLOAD can restore this ?
When i try to restore via dload it stuck at 5% and it says "software install failed!" ..
Someone Help me ?..
Albanheraibi said:
When i try to restore via dload it stuck at 5% and it says "software install failed!" ..
Someone Help me ?..
Click to expand...
Click to collapse
You got failed using the "service-rom" dload?
This one is Oreo I believe. There is a nougat one also.
mrmazak said:
You got failed using the "service-rom" dload?
This one is Oreo I believe. There is a nougat one also.
Click to expand...
Click to collapse
Yes stuck at 5%..
i have try to flash the Honor 7X-Elemental V1(8.X-GPU) and i get an error at the end of process >
mount: failed to mount
/dev/block/platform/hi_mci.0/by-name/system at /system: invalid argument
What i am supposed to do with this error ?
Albanheraibi said:
Yes stuck at 5%..
i have try to flash the Honor 7X-Elemental V1(8.X-GPU) and i get an error at the end of process >
mount: failed to mount
/dev/block/platform/hi_mci.0/by-name/system at /system: invalid argument
What i am supposed to do with this error ?
Click to expand...
Click to collapse
Says in the install guide for it, you must be running at newest security patch in order to install elemental.
Please focus on one thing. Getting phone to boot full stock first before trying other rom. You are going to hard brck your phon if you keep doing flashes when the stock fails to install
mrmazak said:
Says in the install guide for it, you must be running at newest security patch in order to install elemental.
Please focus on one thing. Getting phone to boot full stock first before trying other rom. You are going to hard brck your phon if you keep doing flashes when the stock fails to install
Click to expand...
Click to collapse
When i try to rollback emui5 via twrp with your guide i have this error :
write radio image...
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update pakage from zip failed
E : unknown command [errno]
Updater process ended with ERROR : 9
Error installing zip file '/external_sd/HWOTA8/update.zip'
i remember that the phone has started to bootloop just after twrp flashed the wrong radio file..
This is the end ?
Albanheraibi said:
When i try to rollback emui5 via twrp with your guide i have this error :
write radio image...
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update pakage from zip failed
E : unknown command [errno]
Updater process ended with ERROR : 9
Error installing zip file '/external_sd/HWOTA8/update.zip'
i remember that the phone has started to bootloop just after twrp flashed the wrong radio file..
This is the end ?
Click to expand...
Click to collapse
I am not understanding how you say you follow my guide, then post the error.
This error shows you are trying to install ota update with TWRP.
My guide sets you to install ota update file with a modified stock recovery (no-check).
If you are having trouble because of bad translation, please do not assume what you need to do and wait for proper help and translation
mrmazak said:
I am not understanding how you say you follow my guide, then post the error.
This error shows you are trying to install ota update with TWRP.
My guide sets you to install ota update file with a modified stock recovery (no-check).
If you are having trouble because of bad translation, please do not assume what you need to do and wait for proper help and translation
Click to expand...
Click to collapse
Ok after update with hurupdater via twrp (he flashed the correct radio.img file) the phone have income from death !
Thank you for trying to help me !
Hello everyone!
My realme x chinese version is bricked and now im in (Your current image(boot/recovery)have been destroyed and cannot boot)
Please notice these-
I tried to flash twrp but didnt work.
I have stock recovery but ozip file installation fails.(I tried with otg)
I tried realme flash tool but my storage is not showing.
Even i tried to flash boot,vbmeta,vendor,dtbo,recovery,system and everything flashed properly except system.img.
But now when i try this cmd command (fastboot -w) it shows
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata.
now what can i do?
please help.
TIA
XyperOps said:
Hello everyone!
My realme x chinese version is bricked and now im in (Your current image(boot/recovery)have been destroyed and cannot boot)
Please notice these-
I tried to flash twrp but didnt work.
I have stock recovery but ozip file installation fails.(I tried with otg)
I tried realme flash tool but my storage is not showing.
Even i tried to flash boot,vbmeta,vendor,dtbo,recovery,system and everything flashed properly except system.img.
But now when i try this cmd command (fastboot -w) it shows
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata.
now what can i do?
please help.
TIA
Click to expand...
Click to collapse
Did you got the solution? Please help me!!!!!!!
XyperOps said:
Hello everyone!
My realme x chinese version is bricked and now im in (Your current image(boot/recovery)have been destroyed and cannot boot)
Please notice these-
I tried to flash twrp but didnt work.
I have stock recovery but ozip file installation fails.(I tried with otg)
I tried realme flash tool but my storage is not showing.
Even i tried to flash boot,vbmeta,vendor,dtbo,recovery,system and everything flashed properly except system.img.
But now when i try this cmd command (fastboot -w) it shows
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata.
now what can i do?
please help.
TIA
Click to expand...
Click to collapse
Hi,
I have the same problem.
Any chance you could share the method of how you managed to connect otg to transfer the ozip file? I also only have access to stock recovery and the fastboot mode.
I have the stock rom in zip file version which i am absolutely certain works because i have used it before but i can't install a custom recovery no matter what i try.
If possible could you also share the ozip file and the odp file?
Thank You!
I just wrote unbrick instruction here:
[GUIDE] [RMX1901] Unbrick & Install Android 13 Custom ROM
The guide is for a Chinese version of the phone. But might give you an idea for the global version. History: I was on the latest official ROM. But I was already unlocked the boot. Then I tried to install a custom ROM and failed. Because TWRP for...
forum.xda-developers.com
And you could find some information that I found from there.