Related
Hi. I was trying to install cm13 on my honor 8. I unlocked the bootloader, but while trying to install twrp recovery I think I deleted everything off the phone. The huawei erecovery doesn't work, and I tried sooooo many fastboot commands. I can't do adb commands. I can only get into fastboot mode. Is there anyway for me to get out of this? I tried flashing the system.img and boot.img from fastboot but it fails.
LuneTech said:
Hi. I was trying to install cm13 on my honor 8. I unlocked the bootloader, but while trying to install twrp recovery I think I deleted everything off the phone. The huawei erecovery doesn't work, and I tried sooooo many fastboot commands. I can't do adb commands. I can only get into fastboot mode. Is there anyway for me to get out of this? I tried flashing the system.img and boot.img from fastboot but it fails.
Click to expand...
Click to collapse
Was ur bootloader and frp in unlocked state ?
Sent from my KIW-L22 using Tapatalk
gopinaidu77 said:
Was ur bootloader and frp in unlocked state ?
Click to expand...
Click to collapse
Yes. And it still is
LuneTech said:
Yes. And it still is
Click to expand...
Click to collapse
So u can still recovery your phone
Sent from my KIW-L22 using Tapatalk
LuneTech said:
Hi. I was trying to install cm13 on my honor 8. I unlocked the bootloader, but while trying to install twrp recovery I think I deleted everything off the phone. The huawei erecovery doesn't work, and I tried sooooo many fastboot commands. I can't do adb commands. I can only get into fastboot mode. Is there anyway for me to get out of this? I tried flashing the system.img and boot.img from fastboot but it fails.
Click to expand...
Click to collapse
Hi, i have the exact same problem...
Have you figgerd it out?
Lucas Napik said:
Hi, i have the exact same problem...
Have you figgerd it out?
Click to expand...
Click to collapse
Yes. I installed a roll back update (something like that) by getting into the force update mode. After it finished, I had to then apply the full stock firmware. The problem was that I somehow put the firmware of another phone, because my model number was from a different Huawei phone.
trying to get back to stock
gopinaidu77 said:
So u can still recovery your phone
Sent from my KIW-L22 using Tapatalk
Click to expand...
Click to collapse
Hi. I got tired of CM13, so I tried to go back to stock. I checked a guide online which told me to flash 2 files using TWRP. after that, I lost twrp and now my bootloader is locked. What do I do? I manually did an update with the update.app file, and it says update success, but when it reboots it stays on the honor 8 screen, I waited for 25 minutes and it's still there.
LuneTech said:
Hi. I got tired of CM13, so I tried to go back to stock. I checked a guide online which told me to flash 2 files using TWRP. after that, I lost twrp and now my bootloader is locked. What do I do? I manually did an update with the update.app file, and it says update success, but when it reboots it stays on the honor 8 screen, I waited for 25 minutes and it's still there.
Click to expand...
Click to collapse
Try going into stock recovery and doing a factory reset after you use the update.app. You'll have to unlock the bootloader again and flash twrp if you want root.
Restoring to MM using a full image will typically lock the bootloader.
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
eksasol said:
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
Click to expand...
Click to collapse
2 things, 1 is that there are 2 recovery files in the UPDATE.APP, and 2 is that I can't do a factory reset from the recovery, because it brings me to the erecovery and it doesn't give me the option to factory reset.
LuneTech said:
2 things, 1 is that there are 2 recovery files in the UPDATE.APP, and 2 is that I can't do a factory reset from the recovery, because it brings me to the erecovery and it doesn't give me the option to factory reset.
Click to expand...
Click to collapse
You need to hold VOLUME UP and POWER button with the phone off to get into the recovery to do a factory reset. Once the honor logo pops up, you can release the power and volume up buttons.
Recovery.img = Stock recovery
Recovery2.img = eRecovery
eksasol said:
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
Click to expand...
Click to collapse
I just did everything exactly the way you said. But it still stays at the honor boot logo. I don't mind waiting over night for it to boot up if I have to, but I've never had a phone take this long to boot up, even on first boot.
For a "brick" thread, it seems odd that the model is never mentioned so that someone can really point you to the right spot. If you keep going to erecovery, then it has to do with whether or not your cable is plugged in (likely you've been keeping it plugged in for your fastboot attempts, or that's a guess). I only go to erecovery with both up/down & power if the cable is plugged in. If I want to get to stock recovery (regardless of what the hell is in the "recovery" partition, TWRP, or who knows?) then I unplug it before trying any key combo from power off to get there.
Lastly, if you use this sort of thing as a template (I'm just going to use one for the frd-l09 as an example, but stick the right model in there for you) ::
Example to plug into Google to find your rollback with instructions:: site:consumer.huawei.com honor 8 frd-l09 rollback
Click to expand...
Click to collapse
So if you've got an frd-l04 then plug that in where frd-l09 is. It'll just look on the site consumer.huawei.com just above where the various country/variant breakdowns are, like US/ZH/HU/Etc. are.
Pick the one out that is closest to what it seems you want. All the pages are in the local languages so I'm guessing the .pdf that explains what to do is in the language you'll want as well.
Good luck:: Let us know what model phone you have.
More: Contents of first "intermediate" update.app is 8 image files. I'm sure the 2nd one that is specifically your own phone's version of b162 has a lot more files in it. I've not looked for awhile but I think it's 21 or 22 files. This is a two step process, first is all the crap that comes in update.app from the rollback page (just a 100K file which sets you up in intermediate state for rollback) and 2nd you find your exactly right b162 for your model phone, and pretty much repeat the process.
Yet More: One odd thing about the Honor 8: I've not seen it on other phones is the partition layout is not really "trustworthy" unless you really have gotten to understand it. There appears to be at least 3 or 4 places you can get to that I used to think would all have to be in the recovery partition, but apparently the Honor 8 works differently, so no matter how bleak your odds seem, .. maybe not. I got to both erecovery and stock recovery and rollback while TWRP was installed and it worked just following the directions from their website.
Agreed on this thing.
eksasol said:
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
Click to expand...
Click to collapse
Thank you very much, you saved me and my phone !!!
I made a mistake: my phone was under android m and I flashed by mistake the rollback update (to go m from n), then my honor was bricked on bootloop, no recovery, no update by dload....nothing worked....
Your solution was the right one !! again thank you very much
Interesting observation with the eRecovery (recovery2 partition). So I have TWRP installed, the system partition modified and user storage not encrypted. I was still able to to use eRecovery to connect to WiFi and download the factory image and it automatically repaired the phone to factory state. I noticed it doesn't re-lock the bootloader afterward. This seems to be the easiest method to unbrick.
Getting into eRecovery.
hi! Or extract the files? sorry for my english
eksasol said:
It happened to me too, it is possible you still didn't use the right image.
This is how I recovered mine:
1. Go here to download the latest firmware for your model: https://www.androidfilehost.com/?w=files&flid=129406
2. Use the Huawei Update Extractor to extract files from the "Update.app". (Ignore the 'profile' drop down list in the app.)
3. Unlock your phone's bootloader.
4. Flash these four images (extracted using the tool from step 2):
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
5. Boot into recovery and do a factory reset. This is needed to reformat the internal storage (and make it encrypted I think). (Power+Vol Up)
6. Put the Update.app file inside the "dload" folder in your SDcard.
7. Boot into flash mode to let the phone flash the Update.app (Power+Vol Up+Vol Down).
Click to expand...
Click to collapse
Ok after the factory reset (which is peppered with mounting errors)...
failed to mount /data (invalid arguments)
unable to mount storage
When I try to flash cust.img and system.img they both fail.
I cannot check what firmware I was on before I started all this, but I believe it was the latest one. This is a FRD-04. I flashed TWRP 3.1.0.1 erecovery and I can access it and fastboot.
I have tried various different things and nothing I do can unbrick the phone. Any help would be appreciated.
menriquez said:
Ok after the factory reset (which is peppered with mounting errors)...
failed to mount /data (invalid arguments)
unable to mount storage
When I try to flash cust.img and system.img they both fail.
I cannot check what firmware I was on before I started all this, but I believe it was the latest one. This is a FRD-04. I flashed TWRP 3.1.0.1 erecovery and I can access it and fastboot.
I have tried various different things and nothing I do can unbrick the phone. Any help would be appreciated.
Click to expand...
Click to collapse
have the same problem as you on my FRD-09.
I don't have this phone anymore, but the easiest way I find to restore it is using eRecovery.
Hello guys,
I had some problems with my Honor 6x L21 so I tried to flash new custom ROM that I didn't like in the end. I tried to revert back and found update.app method. I somehow relocked my bootloader and now tried to install update.app which fails at 5 % and says it is not compatible.
Now, I have erecovery with me that can get nothing after connecting to wifi. No update from SD Card option available.
When I try to unlock bootloader again, it fails.
Also, when I run command 'fastboot oem get-bootinfo' the following lines do come in result:
<bootloader> unlocked
OKAY [0.009s]
Finished.
However, my phone shows Phone Relocked and FRP lock.
Any help guys?
@amannan: I have a US BLN-L24, I was able to use the dload method to roll back to Marshmallow from Nougat. I'm not sure why it sometimes fails at 5%, I think Huawei recently implemented something to cause the update to fail if you haven't passed an online verification check. So basically, no upgrading offline for some of the newer firmwares, someone correct me if I'm wrong. I think it has something to do with Nougat too.
In your case, all hope isnt lost as long as you can access eRecovery and fastboot. What you need to do is find the stock MM packages for your device. This will most likely consist of a small rollback file and a much larger firmware file. Go search Huawei's downloads section on their website until you find what you need, use your model as a reference point. There should also be a PDF file with instructions in it, read it.
For each of the 2 files you get, extract the zips, make a folder called dload on your MicroSD (not internal phone storage). In my case I had to first place the update.app file from the rollback zip into the dload folder, boot to eRecovery (hold volume up and volume down, then hold Power, let let of Power when logo appears but continue to hold the other keys). From there the file will automatically flash. Then I had to extract update.app from the large firmware zip and put in dload, repeat same process again. You should be back on MM.
If either file wont flash then go download Huawei Firmware Extractor. Use it to extract boot.img and recovery.img from the rollback zip's update.app, then boot to fastboot mode while phone is powered off. Plug in a MicroUSB charger into phone then plug other end into PC.
Then:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Make sure to install drivers for the phone first, just install HiSuite on Windows is easiest way. For ADB and fastboot, install '15 seconds adb fastboot" (Google it). If the terminal on your PC says something like "file not found", then either use the cd command (change directory) to move working directory to boot.img/recovery.img location, or move the files to C:\adb.
Once you're back up and booting you can then proceed to bootloader unlock, root, ROM flashing, etc.
Hope this helped!
AnonVendetta said:
@amannan: I have a US BLN-L24, I was able to use the dload method to roll back to Marshmallow from Nougat. I'm not sure why it sometimes fails at 5%, I think Huawei recently implemented something to cause the update to fail if you haven't passed an online verification check. So basically, no upgrading offline for some of the newer firmwares, someone correct me if I'm wrong. I think it has something to do with Nougat too.
In your case, all hope isnt lost as long as you can access eRecovery and fastboot. What you need to do is find the stock MM packages for your device. This will most likely consist of a small rollback file and a much larger firmware file. Go search Huawei's downloads section on their website until you find what you need, use your model as a reference point. There should also be a PDF file with instructions in it, read it.
For each of the 2 files you get, extract the zips, make a folder called dload on your MicroSD (not internal phone storage). In my case I had to first place the update.app file from the rollback zip into the dload folder, boot to eRecovery (hold volume up and volume down, then hold Power, let let of Power when logo appears but continue to hold the other keys). From there the file will automatically flash. Then I had to extract update.app from the large firmware zip and put in dload, repeat same process again. You should be back on MM.
If either file wont flash then go download Huawei Firmware Extractor. Use it to extract boot.img and recovery.img from the rollback zip's update.app, then boot to fastboot mode while phone is powered off. Plug in a MicroUSB charger into phone then plug other end into PC.
Then:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Make sure to install drivers for the phone first, just install HiSuite on Windows is easiest way. For ADB and fastboot, install '15 seconds adb fastboot" (Google it). If the terminal on your PC says something like "file not found", then either use the cd command (change directory) to move working directory to boot.img/recovery.img location, or move the files to C:\adb.
Once you're back up and booting you can then proceed to bootloader unlock, root, ROM flashing, etc.
Hope this helped!
Click to expand...
Click to collapse
Dear AnonVendetta, Thank you so much for the help. I was able to use the dload method. I read somewhere that the last firmware version needs to be updated using dload method. I had B361 before it got all messed up so tried that update and it started working.
Also, the fastboot won't flash any img file since the FRP was locked somehow.
Thank you for the help
@amannan: Glad it worked out, you must have already made progress before I posted, your response was too quick.
I do believe you cant flash anything via fastboot if the bootloader is still locked.
I've only owned my Honor 6X for about 2 weeks, I've had to do an emergency recovery several times due to various issues. This is my first Huawei but I've owned many Android devices before, and rooted/custom ROMmed most of them, so I'm just a newbie to Huawei but not Android in general. I'm getting the hang of things.
Good luck!
amannan said:
Dear AnonVendetta, Thank you so much for the help. I was able to use the dload method. I read somewhere that the last firmware version needs to be updated using dload method. I had B361 before it got all messed up so tried that update and it started working.
Also, the fastboot won't flash any img file since the FRP was locked somehow.
Thank you for the help
Click to expand...
Click to collapse
Yes, dload method is the only way to restore the device in such scenario. If frp is locked then condition is worse as you can not flash anything but only dload will help you. Correct package should be flashed and will succeed.
So I have and Unlocked bootloader, TWRP for Android Oreo, and Root. I did a backup of the existing system but like an idiot when I was clearing the DAVLIK and User space I also formated the MicroSD and subsequently my backup.
I tried following the different guides to reload the base system but I'm not having any luck I must have done something royally wrong but at this point I don't even care if I revert back to stock I just want something other then the endless boot loop that is currently my reality.
I've tried downloading the update.zip files from http://pro-teammt.ru/firmware-database/ but the images are not posting properly when I try from TWRP or Fastboot. I tried reverting the recovery back to stock and trying to use OpenKirin and again no luck. Can someone point to the proper firmware with what ever recovery.img, kernal ramdisk.img, and or system.img I need to extract.
I'm missing something or am I using old guides with newer software release.
Thanks in Advance
Okay so I finally figured out why I was receiving errors when I tried to extract the kernel.img, system.img, and recovery.img from the update.app files in Huawei Update Extractor. Apparently Huawei turned off CRC checks on the newer files and once they are disabled in the settings they images open up fine. Going to try and flash a build with fastboot.
Process I'm going to undertake to try and restore the system.img for my MHA-L29C567 device. Currently my Bootloader is Unlocked, and I am able to access Fastboot&Rescue Mode so I intend on manually updating the MHA-L29C567B367 (8.0.0.367) Update using Fastboot.
1) Go to http://pro-teammt.ru/firmware-database/?firmware_model=MHA-L29C567&firmware_page=0 and Download MHA-L29C567B367 (8.0.0.367) Update.zip
2) Unzip/decompress update.zip and use HuaweiUpdateExtractor_0.9.9.5 with CRC checks turned off in setting to avoid error opening Update.app.
3) Extract System.img and Kernel.img and apply to phone using following commands in windows command terminal with Phone in Fastboot&Rescue Mode (Hold Power and Volume Down)
fastboot flash system SYSTEM.img
fastboot flash kernel Kernel.img
4) Reboot phone with command fastboot reboot
5) Wipe DAVLIK User Space and cross my fingers it boots.
smtelegadis said:
Process I'm going to undertake to try and restore the system.img for my MHA-L29C567 device. Currently my Bootloader is Unlocked, and I am able to access Fastboot&Rescue Mode so I intend on manually updating the MHA-L29C567B367 (8.0.0.367) Update using Fastboot.
1) Go to http://pro-teammt.ru/firmware-database/?firmware_model=MHA-L29C567&firmware_page=0 and Download MHA-L29C567B367 (8.0.0.367) Update.zip
2) Unzip/decompress update.zip and use HuaweiUpdateExtractor_0.9.9.5 with CRC checks turned off in setting to avoid error opening Update.app.
3) Extract System.img and Kernel.img and apply to phone using following commands in windows command terminal with Phone in Fastboot&Rescue Mode (Hold Power and Volume Down)
fastboot flash system SYSTEM.img
fastboot flash kernel Kernel.img
4) Reboot phone with command fastboot reboot
5) Wipe DAVLIK User Space and cross my fingers it boots.
Click to expand...
Click to collapse
That didn't work so I reapplied TWRP and tried to apply the update.zip file and that did not work either. Having a hard time of things at this point just need to take a break for tonight.
So I'm getting an error message with the following when I try to update using the MHA-L29C636B368 (8.0.0.368) rom:
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update package from zip failed. Screenshot attached or link below:
https://photos.app.goo.gl/VGbh86ddthsU8kdt8
From what I've read in other forum post is that repairing the system partition can fix this. I used the Wipe>Advance Wipe [toggled "System"]>Repair or Change File System>Repair File System. I also tried to format the partition and again no change. I know the partition is not toggled read only and I even did that and reverted just to see if it was not presenting properly. Can't figure out what is going on here. Would really appreciate some advice. I rebooted into recovery after each attempt.
Thanks in Advance
So I followed the thread in this forum for how to downgrade back to nougat and now I have my phone running again. In the process of resetting the system and updating back to EMUI 8 now.
Hi,
First of all, yes, I have checked the other threads that talk about reverting to stock and I am still stuck.
So I installed Kang OS which is Android 11, and now I want to revert to stock. I have tried downloading multiple different versions of the fastboot ROM from the page https://androidfilehost.com/?w=files&flid=294300 and run the flash all batch file and every time I am either getting stuck in a boot loop or getting the Verity Crash Dump Screen. I have managed to reach the fastboot screen, and I am waiting on the fastboot screen, for someone to show me some way.
Thanks in Advance.
If you used a pin then your storage is encrypted and the rom you are trying to flash can't use it, that's why you're most likely stuck at boot.
I ran into the same issue and posted about it in the same thread. I think we will need a new version of TWRP as 3.4.0-0 would not accept my pin which had not changed.
To fix your issue, sadly, you'll need to wipe your storage:
Boot the phone into fastboot mode
Attach your USB cable to the phone/PC
Download and unzip the file I've attached (ADB/Fastboot)
Launch an elevated command window in the folder you extracted the attached zip to
Try the command fastboot devices and ensure that it reports the device correctly, if not then you need to install the latest OnePlus drivers
Type the following in the command window : fastboot -w (This will wipe the storage)
Try your rom again (TWRP should remain as the recovery if you had flashed it already, if not then copy the latest TWRP img file to the same folder as the ADB/Fastboot tools, use fastboot and type boot twrpfilename.img this will make the phone boot into TWRP recovery, you can then copy over the TWRP zip and flash it to recovery using the booted version of TWRP)
Once you've done the above you shouldn't really need to use the fastboot scripts as the latest rom should just flash from TWRP.
Get msm download tool for guacamole which is the codename of the op7p. I know the shorts with the global version I am unsure if this works with T-Mobile or others?
MSM is a bit of a severe fix when they've already confirmed they can still get fastboot, MSM is for completely bricked phones that can't access anything. Wiping the storage and going to fastboot will allow them to just flash recovery then flash the stock rom. Way easier.
Boot into twrp. Then format data. Phone will boot then.
I have not one, but two bricks. I bought one to unbrick the other, but the reverse happened. Using the EDL tool from this forum, I made a full and then an all backup and tried to use it to unbrick the other. No success. Now I cannot enter fastboot on either device, but both will enter EDL. I think at least one will fastboot if I can switch the active a/b slot.
Can the active a/b slot be switched via a command in the edl mode? Or is there another way to switch the active slot on a brick without fastboot access? Thank you
I already had that you have to put in the edl tool Then unlock bootloader and then you can go back to fastboot mode, it is because the files abl.elf have to be flashed to have fastboot
but to avoid the brick you have to flash all then boot the mobile phone and best an official Rom flash then back ...in edl Tool .... if you have an A2020G the 1.6 edl firmware helps you continue flashing and then you can lineage OS and then everything else flash what you want
Here ist the Link of 1.6 A2020Gpro Firmware: yadi.sk/d/0d8uKQ1nEd8ZVA
noobstyle1337 said:
I already had that you have to put in the edl tool Then unlock bootloader and then you can go back to fastboot mode, it is because the files abl.elf have to be flashed to have fastboot
but to avoid the brick you have to flash all then boot the mobile phone and best an official Rom flash then back ...in edl Tool .... if you have an A2020G the 1.6 edl firmware helps you continue flashing and then you can lineage OS and then everything else flash what you want
Here ist the Link of 1.6 A2020Gpro Firmware: yadi.sk/d/0d8uKQ1nEd8ZVA
Click to expand...
Click to collapse
Thank you for your answer.
I have tried flashing both phones with the following:
1) Full edl from newly purshased phone with v1.1
2) All edl from newly purchased phone with v1.1
3) A2020G v1.6 pro firmware
4) Several other firmwares which the edl would not accept as valid.
None of these worked. Actually, they made things worse. I cannot not even get to fastboot anymore. They both used to give a splash screen that quickly looped. Even that is now gone. Pressing any combination of buttons results in absolutely nothing or edl mode.
The only conclusion that I can make is one of two things:
1) Bricked both all hope
2) edl flashes that I am using are set up for A slot, when the phone is trying to use B slot. I thought when one slot was unbootable it would automatically switch to the other but that doesn't seem to be happening.
Does anyone know of a way to force the phone to boot to the other slot from edl mode? OR some flag that I can edit to switch the slots? OR some command that I can issue to switch slots using fh_loader.exe or emmcdl.exe or another edl tool?
There's no command to switch active slots that I know of and I've gone into the source on fh_loader.
What phone version do you have? Is there some reason you didn't download the EDL tools I uploaded recently instead? The original EDL tool has a few bugs. Read the newer EDL tool thread for some helpful information related to unbricking.
The fact that you aren't getting a ZTE logo at all indicates that you do not have a mixed up slot a/b situation anyway. It probably means you need to fix your AOP files. Of course the original EDL tool doesn't really let you do that. If you have the US version you can use the tools I uploaded to target just the AOP files and try restoring them from your original backup... either the a or b slot one should work.
Make sure you keep your original ALL/FULL backups (both) from the EDL tool, they're probably 99% good and you'll be doing yourself a favor not to delete or modify them.
groundslug said:
Thank you for your answer.
I have tried flashing both phones with the following:
1) Full edl from newly purshased phone with v1.1
2) All edl from newly purchased phone with v1.1
3) A2020G v1.6 pro firmware
4) Several other firmwares which the edl would not accept as valid.
None of these worked. Actually, they made things worse. I cannot not even get to fastboot anymore. They both used to give a splash screen that quickly looped. Even that is now gone. Pressing any combination of buttons results in absolutely nothing or edl mode.
The only conclusion that I can make is one of two things:
1) Bricked both all hope
2) edl flashes that I am using are set up for A slot, when the phone is trying to use B slot. I thought when one slot was unbootable it would automatically switch to the other but that doesn't seem to be happening.
Does anyone know of a way to force the phone to boot to the other slot from edl mode? OR some flag that I can edit to switch the slots? OR some command that I can issue to switch slots using fh_loader.exe or emmcdl.exe or another edl tool?
Click to expand...
Click to collapse
You can only change the slots if you are in Fastboot. You have doing it wrong ... if you have an A2020G you can flash the firmware ... if you have the A2020u version then you should ... flash the correct one
so in itself quite simple .... flash edl firmware and then unlock .. then you boot into the fastboot mode and then you have to use these lines
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Then
fastboot --set-active=a
in any case you have to unlock to access the fastboot menu
then you should be able to boot
---------- Post added at 04:39 PM ---------- Previous post was at 04:36 PM ----------
remember to flash Android 9 edl firmware because otherwise the unlock won't work
---------- Post added at 04:47 PM ---------- Previous post was at 04:39 PM ----------
also remember that some firmwares have to be in the flash folder or in the backup folder if it doesn't work
bobthenormal said:
What phone version do you have? Is there some reason you didn't download the EDL tools I uploaded recently instead? The original EDL tool has a few bugs. Read the newer EDL tool thread for some helpful information related to unbricking.
Click to expand...
Click to collapse
A2020U on both.
Many thanks for your edl tools! The problem was at least very close to what I thought. Active slot a. Fix bootable partition on your edl tools brought both back to their previous state. (This a/b slot scheme is intentionally over complicated and for modders makes bricks instead of preventing them.) The newly purchased phone is now unlocked and bootable into v1.1. I will proceed with lineage next. The old phone is still a brick with a locked bootloader, but it has fastboot now. I keep you posted. Other life duties call at the moment. Thanks!
groundslug said:
A2020U on both.
Many thanks for your edl tools! The problem was at least very close to what I thought. Active slot a. Fix bootable partition on your edl tools brought both back to their previous state. (This a/b slot scheme is intentionally over complicated and for modders makes bricks instead of preventing them.) The newly purchased phone is now unlocked and bootable into v1.1. I will proceed with lineage next. The old phone is still a brick with a locked bootloader, but it has fastboot now. I keep you posted. Other life duties call at the moment. Thanks!
Click to expand...
Click to collapse
It's great to hear I was able to help save from that terrible bricked feeling!
For the 2nd phone - you can try this to unlock it manually without getting it to boot... First do a full backup using my EDL tool. Then use the "FRP" tool I included to write an "unlocked" version of the FRP partition. Then go into fastboot and do the unlock manually - I think it's "fastboot flashing unlock".. but just search to make sure that's right.
Otherwise.. I'm slow but I'll eventually upload the locked stock ROMs.
bobthenormal said:
It's great to hear I was able to help save from that terrible bricked feeling!
For the 2nd phone - you can try this to unlock it manually without getting it to boot... First do a full backup using my EDL tool. Then use the "FRP" tool I included to write an "unlocked" version of the FRP partition. Then go into fastboot and do the unlock manually - I think it's "fastboot flashing unlock".. but just search to make sure that's right.
Otherwise.. I'm slow but I'll eventually upload the locked stock ROMs.
Click to expand...
Click to collapse
Both are unlocked now, thank you!
I am still having trouble getting lineage OS to go though. Here's the steps I follow:
1) Fashboot flash twrp from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot flash vbmeta from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
3) Boot to twrp.
4) Twrp flash lineage 16 OS. Tried both from here. http://samson.nwwn.net/~unjust/Axon 10 Pro/LineageOS/
5) Twrp flash lineage 16 OS root addon arm64 from here. https://download.lineageos.org/extras
6) Wipe data and cache.
This results in the previous state in which only edl, no fastboot is available. So I flash my all backup using the edl tools and I am back to the beginning. I must be missing a step???
EDIT: I also tried restoring aop and uefisecapp files via edl after above steps as suggested in your readme. Same with vbmeta. Again, edl only, no fastboot.
groundslug said:
Both are unlocked now, thank you!
I am still having trouble getting lineage OS to go though. Here's the steps I follow:
1) Fashboot flash twrp from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot flash vbmeta from here. https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
3) Boot to twrp.
4) Twrp flash lineage 16 OS. Tried both from here. http://samson.nwwn.net/~unjust/Axon 10 Pro/LineageOS/
5) Twrp flash lineage 16 OS root addon arm64 from here. https://download.lineageos.org/extras
6) Wipe data and cache.
This results in the previous state in which only edl, no fastboot is available. So I flash my all backup using the edl tools and I am back to the beginning. I must be missing a step???
EDIT: I also tried restoring aop and uefisecapp files via edl after above steps as suggested in your readme. Same with vbmeta. Again, edl only, no fastboot.
Click to expand...
Click to collapse
Just replying real quick since I have a min and I saw a few things you can try... 1. make sure you're installing twrp itself with the zip after you boot into it with fastboot, 2. use the two flags when you write vbmeta just in case (I forget them but one is dm verify and the other is no verity, should be in the original LOS16 thread) and 3. try the fix bootable partition tool from my tools after you install. the LOS16 image has a similar problem as all other images that it has a specific slot it works on (B I think) so if you end up installing and trying to boot it from the other slot it locks into a fast bootloop. Don't bother installing the addons until LOS is booting, so just do a reboot to system after you flash it, fix bootable. If it doesn't boot then it has to be something I'm not thinking of. Goodluck!
It's been a while, but I wanted to follow up.
I did finally get lineage working. The two things that I was missing:
1) Fastboot to flash boot partition with los-twrp-magisked-boot.img
There is another file named twrp-magisked-los-boot.img that did NOT work for.
A third file named Magisk20.3-twrp.img would appear to be yet a third option for flashing boot. I did not try it because I had a working boot.
All three files can be found at link already given: https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot to flash system partition with system.img
I used python and a python module called payload dumper (use google to find tutorial) to extract the .img files from the lineage 16 zip file.
This gave me 5 files.
boot.img - Did not use. See #1
dtbo.img - Flashing it led to a brick, if I remember right. Do not use.
system.img - Yes!
vendor.img - I flashed it too, but I do not think it is necessary.
vbmeta.img - Did not use. Use vbmeta disabled as noted above.
I use the lineage 16 dated 20191029 that used to be available at the following link. It appears to be dead as of today. Maybe will return.
http://samson.nwwn.net/~unjust/Axon%2010%20Pro/
Other versions of lineage will probably work with this method, but I can not say for sure.
In summary, use fashboot to flash los-twrp-magisked-boot.img and system.img. Obtain boot from link above. Obtain system from python module payload dumper from lineage 16 zip file. See other threads on this forum for details regarding unlocking bootloader with EDL tools and how to make vbmeta disabled. Hope this helps someone avoid the headaches I had!
groundslug said:
It's been a while, but I wanted to follow up.
I did finally get lineage working. The two things that I was missing:
1) Fastboot to flash boot partition with los-twrp-magisked-boot.img
There is another file named twrp-magisked-los-boot.img that did NOT work for.
A third file named Magisk20.3-twrp.img would appear to be yet a third option for flashing boot. I did not try it because I had a working boot.
All three files can be found at link already given: https://www.mediafire.com/folder/ha8j5crsdmbmx/ZTE_Axon_10_pro_stuff
2) Fastboot to flash system partition with system.img
I used python and a python module called payload dumper (use google to find tutorial) to extract the .img files from the lineage 16 zip file.
This gave me 5 files.
boot.img - Did not use. See #1
dtbo.img - Flashing it led to a brick, if I remember right. Do not use.
system.img - Yes!
vendor.img - I flashed it too, but I do not think it is necessary.
vbmeta.img - Did not use. Use vbmeta disabled as noted above.
I use the lineage 16 dated 20191029 that used to be available at the following link. It appears to be dead as of today. Maybe will return.
http://samson.nwwn.net/~unjust/Axon%2010%20Pro/
Other versions of lineage will probably work with this method, but I can not say for sure.
In summary, use fashboot to flash los-twrp-magisked-boot.img and system.img. Obtain boot from link above. Obtain system from python module payload dumper from lineage 16 zip file. See other threads on this forum for details regarding unlocking bootloader with EDL tools and how to make vbmeta disabled. Hope this helps someone avoid the headaches I had!
Click to expand...
Click to collapse
Thanks a lot! I'm stuck in the same spot, I have the solutions but I can't connect fully with sahara or qpst? Is this why you went with the payload dumper? Sorry I'm unfamiliar but I'm up to use it.
Rise55Chrom said:
Thanks a lot! I'm stuck in the same spot, I have the solutions but I can't connect fully with sahara or qpst? Is this why you went with the payload dumper? Sorry I'm unfamiliar but I'm up to use it.
Click to expand...
Click to collapse
By sahara, you mean the EDL protocol, yes? (I am not familar with qpst.) Are you using the EDL tools published by unjustified and bobthenormal on this forum? I had problems with the sahara protocol too when adding the firehose. I initially fixed it by opening the back case and disconnecting and reconnecting the battery connector. That's a big headache, especially if you don't already have the back case open. (I had it open because I had previously replaced the screen.) I found that to be unnecessary. If you press all three buttons to enter EDL mode, just press them again and again until the sahara works and the firehose goes in.
Regarding payload dumper, I used it simply because nothing else gave me a bootable phone. I did use the EDL tools to unlock the bootloader and to set the active slot (only bobthenormal's EDL tools will set the active slot).
Here's the payload dumper tutorial that worked for me.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Don't forget to flash los-twrp-magisked-boot.img and vbmeta disabled as noted above. Also, if you use this method, let me know if it was necessary for you to flash vendor.img. Above all, do a complete backup via the EDL tools before making any other changes!
groundslug said:
By sahara, you mean the EDL protocol, yes? (I am not familar with qpst.) Are you using the EDL tools published by unjustified and bobthenormal on this forum? I had problems with the sahara protocol too when adding the firehose. I initially fixed it by opening the back case and disconnecting and reconnecting the battery connector. That's a big headache, especially if you don't already have the back case open. (I had it open because I had previously replaced the screen.) I found that to be unnecessary. If you press all three buttons to enter EDL mode, just press them again and again until the sahara works and the firehose goes in.
Regarding payload dumper, I used it simply because nothing else gave me a bootable phone. I did use the EDL tools to unlock the bootloader and to set the active slot (only bobthenormal's EDL tools will set the active slot).
Here's the payload dumper tutorial that worked for me.
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Don't forget to flash los-twrp-magisked-boot.img and vbmeta disabled as noted above. Also, if you use this method, let me know if it was necessary for you to flash vendor.img. Above all, do a complete backup via the EDL tools before making any other changes!
Click to expand...
Click to collapse
Phenomenal! Best advice, I have received... Thank you so very much. You hit it right on the head. I'll be sure to fill ya in asap when I have the time to get after it. Appreciate you.
bobthenormal said:
EDL tool
Click to expand...
Click to collapse
Hello, where can I find this program? EDL tool