Related
Calling all the Huawei Experts to help me out on this!!
Short Summary of problem
On my Ascend Mate 7 MT7-TL10 (running Android 5.1.1 version B326) -The bootloader shows as unlocked but I still can't flash a custom recovery - It gives error 'FAILED (remote: image verification error)'. I am using the lastest version of ADB/Fastboot, I have USB drivers installed and I also have the Bootloader Unlock code from Huawei, which works and shows 'Done'
Please read the details below first and kindly see all attachments
Click to expand...
Click to collapse
Little bit more information
- On the Bootloader screen of my MT7-TL10 (Gold 32 GB, 3 GB RAM version), I see "Phone Unlocked" in red, which means that my bootloader is unlocked. (refer to attachment)
- When I run the command 'Fastboot OEM get-bootinfo', it returns 'UNLOCKED'.
- However, whenever I try to flash a custom recovery, it gives me an error 'FAILED: (remote: image verification error).
- At the same time, if I flash stock recovery, it is successful.
Detailed Information
- When I run the command 'fastboot oem get-bootinfo' it returns 'UNLOCKED'.
- However, when I run the command 'fastboot oem get-lockstate', it returns 'Locked'
- I rolled back to KitKat 4.4.2 - But the process of roll-back to KitKat 4.4.2 was not as simple as it was described in many forums and I first ended up soft-bricking the device
- I followed the restore process described on Huawei's website and ended up flashing a chinese ROM (JAZZ) on my MT7-TL10 and there were plethora of chinese apps
- Then, I unlocked the bootloader using (fastboot oem unlock <unlock code>) and on KitKat, both commands 'fastboot oem get-bootinfo' and 'fastboot oem get-lockstate' returned 'UNLOCKED' (Hurray!, That's what I thought but...)
- Realizing that the bootloader was finally unlocked, with the help of @acbka, I was finally able to restore Lollipop (version 5.1.1 - B326) and to my utter disgust, after upgrading, I found out that I was again not able to flash a custom ROM - On Lollipop, the command 'fastboot oem get-lockstate' again returned 'LOCKED' and the command 'fastboot oem get-bootinfo' returned 'UNLOCKED'
- As you can see, I was back to square 1 and I still can't unlock the bootloader and therefore, I cannot root my phone
Final statement
- When I rolled back to KitKat, the Bootloader showed as Unlocked and I was able to flash custom recovery TWRP
- After upgrading to Lollipop (5.1.1 B324 and B326), I am unable to flash custom recovery (somehow, the bootloader shows as 'Locked' when I run 'fastboot oem get-lockstate')
- If I flash stock recovery, it is successful
- The error 'FAILED (remote: image verification error)' implies that the bootloader is locked and that's why it forbids flashing of custom recovery BUT it allows flashing stock recovery
Please see the attached pictures, which will show what I mean.
I will really appreciate any help to enable me to flash a custom recovery!! Please help!
i also face the same problem any one can help us ?
try another bat file to flash recovery,
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984
Thanks for replying. However, this won't help because I am directly running the fastboot command (not using a .bat file). The link that you posted is dead...
Please read this: I have explained in my post with scrrenshots that the fastboot command 'fastboot oem unlock CODE' works and shows 'Done', which means that it has unlocked the bootloader. If you repeat the command, it shows 'user already unlocked', which is a proof that the Fastboot command is working.
However, the problem is that flashing a custom Recovery shows a 'remote' error, which means that it is the bootloader, which is preventing the flashing of the custom recovery.
The problem is that on Android 5.1.1, the bootloader is appearing as locked even though the fastboot procedure shows that the bootloader was unlocked.
I have tried different fastboot binaries and also tried different procedures (including BAT files) but not able to beat this problem.
Sent from my HUAWEI MT7-TL10 using Tapatalk
prahastaabenk said:
try another bat file to flash recovery,
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984
Click to expand...
Click to collapse
kingrk said:
Thanks for replying. However, this won't help because I am directly running the fastboot command (not using a .bat file). The link that you posted is dead...
Please read this: I have explained in my post with scrrenshots that the fastboot command 'fastboot oem unlock CODE' works and shows 'Done', which means that it has unlocked the bootloader. If you repeat the command, it shows 'user already unlocked', which is a proof that the Fastboot command is working.
However, the problem is that flashing a custom Recovery shows a 'remote' error, which means that it is the bootloader, which is preventing the flashing of the custom recovery.
The problem is that on Android 5.1.1, the bootloader is appearing as locked even though the fastboot procedure shows that the bootloader was unlocked.
I have tried different fastboot binaries and also tried different procedures (including BAT files) but not able to beat this problem.
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
Edit: The link that you posted is not dead - it didn't open on my smartphone. The author of that post ACBKA helped me and we both tried it but could not beat the bootloader. While it shows that it is unlocked, it is still restrictive and doesn't allow flashing of custom recovery.
awzx_77 said:
i also face the same problem any one can help us ?
Click to expand...
Click to collapse
I have an idea!
I remember that when I was troubleshooting the problem (my smartphone was soft-bricked when I tried to rollback to KitKat and I ended up flashing Chinese 'Jazz' version on my TL10), I had realized that the bootloader was FULLY UNLOCKED on the chinese Jazz ROM and I could actually install a custom recovery. So, here is the idea:
a) First roll back to KitKat 4.4.2 --> I believe that there is a procedure on XDA to roll-back to KitKat
b) Change the phone's location to China
c) Install custom recovery and root phone by flashing superuser
d) Upgrade to Lollipop 5.1.1 (Chinese version)
e) Upgrade to Marshmallow beta (Chinese version)
f) Install custom recovery and root phone
same problem
just unlock the bootloader again using unlock code!
it worked for me
+1 for @xAghilx. Same here.
Hi friends
Please give me suggestion or guide how to solve problem about handset booting after mistakenly handset OEM locked through fastboot
It enter to fastboot mode but not going to recovery mode or restart in system mode
Is there any solution
If yes then please help me
fastboot oem unlock ?
Actually ive unlocked OEM and install twrp recovery and installed freedom os
Then while checking OEM status ive enter command fastboot OEM lock
It ask me I've pressed yes after that the massage is came after restart as your device is corrupt it can't be trusted and will not boot
After that it enter to fastboot but not going to recovery mode or system
While type command in fastboot OEM unlock massege come failed
This happens because your bootloader has been unlocked at one time. There is no going back, even if you use "fastboot oem lock" later.
Edit: Just noticed the part about your device will not boot. You need to find the system image and flash it. I read somewhere today that OnePlus just released the system image for 4.7.4.
Can you unlock again?
@op, IMHO the best possible solution will be to flash stock rom image and stock recovery if required but I think when you flash stock image it will also flash stock recovery.
When you turn off the phone and boot it with VOLUME UP plus POWER, this should send you straight away to Fastboot. Try if you can unlock again, otherwise... bad luck - you'll need a restore session with 1+.
the Doctor said:
This happens because your bootloader has been unlocked at one time. There is no going back, even if you use "fastboot oem lock" later.
Click to expand...
Click to collapse
Not to be unrespectful, but you're wrong, it is absolutely possible to relock bootloader without problems.
IMHO, trouble happened because he had a custom rom onboard... and a locked bootloader does exactly its purpose... to not boot insecure firmware!
jonsat said:
Not to be unrespectful, but you're wrong, it is absolutely possible to relock bootloader without problems.
IMHO, trouble happened because he had a custom rom onboard... and a locked bootloader does exactly its purpose... to not boot insecure firmware!
Click to expand...
Click to collapse
After looking into it further, I agree with you. That's what I get for having a bootloader-locked Samsung device for two years. I must be getting rusty!
Yes, the bootloader can be re-locked. There may still be a tamper flag as with previous OnePlus devices. But having a locked bootloader with non-OEM software would likely cause the problem he is describing. So, he needs to flash the factory image from bootloader.
I've requested to 1+support for restore remote session
Support send me file link and l2 will assist me in within 2 days
DO NOT RELOCK BOOTLOADER UNLESS U READ UP FIRST!!!!!, its worth just waiting the few seconds after reboot, then to go and try to relock the bootloader
I've restored oneplus 5t through remote session
it become as company new mobile
After that OEM also unlock
Thanks oneplus supports.
kaihansen2001 said:
Can you unlock again?
Click to expand...
Click to collapse
Yes ive unlock Bootloader
Rdxsammm said:
I've restored oneplus 5t through remote session
it become as company new mobile
After that OEM also unlock
Thanks oneplus supports.
Click to expand...
Click to collapse
How did you do it? can you guide me too?
sam razzy said:
How did you do it? can you guide me too?
Click to expand...
Click to collapse
Have you dumpling files and MSM download tools for oneplus 5t
If you have then restore op5t after success it work as new mobile.
But you can get basic dumpling file from oneplus support remote session.
You have to create ticket and chat with oneplus support
oneplus 5 device corrupt and it cant be trusted and will not bootr
hrushi0130 said:
oneplus 5 device corrupt and it cant be trusted and will not bootr
Click to expand...
Click to collapse
Did you by any chance re-lock the bootloader with a custom recovery and custom ROM flashed?
It's because of custom recovery.
Just flash stock recovery image before locking the bootloader.
This fixed for me.
Rdxsammm said:
Actually ive unlocked OEM and install twrp recovery and installed freedom os
Then while checking OEM status ive enter command fastboot OEM lock
It ask me I've pressed yes after that the massage is came after restart as your device is corrupt it can't be trusted and will not boot
After that it enter to fastboot but not going to recovery mode or system
While type command in fastboot OEM unlock massege come failed
Click to expand...
Click to collapse
You unlocked bootloader, flashed rom (custom) and relocked bootloader? Never lock your bootloader on a custom rom! Just enter fastboot again flash twrp (manual/force reboot recovery), copy internal storage to pc then wipe/format everything. Format data. Factory reset then flash latest official rom and reboot
Hi all,
I am new to this forum, but have some experience with rooting and custom roms(oneplus one and samsung)
Now with the Mi Max 3, which was unlocked, i have flashed the recovery twrp-3.2.3-0-nitrogen.img, but I did not realize that
i had to reboot into this recovery from the fastboot mode.
so I endet up with a locked bootloader and bottloop and am not able to unlock the bootloader again.
I think my only solution is the test-point method and a EDL authorized account.
Some help would be greatly appreciated.
thanks
Henry
You don't have to boot into the bootloader from fastboot mode, you can press the power button and volume up button like on almost all other Android phones to boot into TWRP recovery. Sometimes it takes a few attempts to get right, but you should learn how to do it eventually.
Unfortunately it sounds like you had one of the dodgy re-sold Chinese models that had been re-flashed with Global firmware and it's locked your bootloader again on reboot.
Your only option is to use the official Miui Flash tool to boot into fastboot mode, flash the latest Global Developer ROM, and then sign in with your account and apply to unlock the bootloader again using the Miui unlock program. It may be instant but, they'll probably make you wait 720 hours, as the entire point of the program was to stop phones like yours being re-sold outside China.
At least you'll have a usable, non-bricked device though.
Thanks for your answer.
now I have opened the backcover (yes was much work ( I succeded without destroying something) and could apply the test point method to get into the lde mode.
Win10 shows it as qualcomxx at com 3
what is the best way now to awake it to life again? even without unlocking.
hi,
with the test point method I could flash the chinese rom, and the mi max 3 is awaken to life again!
The bootloader is still locked.
I have applied for unlocking, but have to wait some 15 days.
One tip: if the case is open, one can apply a little bit of silicon grease to the small pins on the side of the plastic frame
before closing it. Opening it again is much easier then.
One question: if I replace the recovery.img of the chinese rom with a TWRP image (renamed to recovery.img)
and flash that modified rom with the test point method, could this probaly work?
With a working TWRP one could install other roms without unlocking bootloader.
If yes, which TWRP would you apply?
Thanks
freedoc said:
Hi all,
I am new to this forum, but have some experience with rooting and custom roms(oneplus one and samsung)
Now with the Mi Max 3, which was unlocked, i have flashed the recovery twrp-3.2.3-0-nitrogen.img, but I did not realize that
i had to reboot into this recovery from the fastboot mode.
so I endet up with a locked bootloader and bottloop and am not able to unlock the bootloader again.
I think my only solution is the test-point method and a EDL authorized account.
Some help would be greatly appreciated.
thanks
Henry
Click to expand...
Click to collapse
Flashing a recovery should not lock your bootloader, so I don't know how you did it. Note, that if you are using Xiaomi's firmware tool, you should not forget about unticking the box to lock the bootloader. But I would suggest to stay away from that tool and go command line instead with fastboot.
If you can access fastboot, I'd recommend to flash an official fastboot tgz ROM of your choice. Official ROM should boot even with an unlocked bootloader and you may start all over again more carefully.
So I think you might be able to avoid using EDL mode at this stage.
probally I forgot to untick that box. The bootloader is locked and I have to wait 319 hours.
I have got to love the test point EDL method which is simple and effective, and gave me control over the device again.
If I flash again the chinese fastboot rom (in which I have changed the original recovery.img into TWRP.img, named recovery.img) via the EDL
will that give me an installt TWRP (still with locked bootloader, but possible to install custom roms) or will i have a brick again?
thanks
freedoc said:
probally I forgot to untick that box. The bootloader is locked and I have to wait 319 hours.
I have got to love the test point EDL method which is simple and effective, and gave me control over the device again.
If I flash again the chinese fastboot rom (in which I have changed the original recovery.img into TWRP.img, named recovery.img) via the EDL
will that give me an installt TWRP (still with locked bootloader, but possible to install custom roms) or will i have a brick again?
thanks
Click to expand...
Click to collapse
Only you can answer that question by trying it out. Are you sure you have to wait for the unlocking again? Double check that! As I know you also need a priviliged xiaomi account to be able to resurrect a device in EDL mode.
Is there any way to unlock the non european variants of G8s? G810EA, not EAW.
Tried on LG dev page it refuses saying not supported but my fastboot shows option to write a BL unlock key and says it can be unlocked.
Any possibility of getting unlocked BL another way? Im open to unofficial methods.
Many thanks
corpsegrinder62 said:
Is there any way to unlock the non european variants of G8s? G810EA, not EAW.
Tried on LG dev page it refuses saying not supported but my fastboot shows option to write a BL unlock key and says it can be unlocked.
Any possibility of getting unlocked BL another way? Im open to unofficial methods.
Many thanks
Click to expand...
Click to collapse
Well I think the bl unlock method for a while for v40 and g7 was crossflashing to a firmware with fastboot and fastboot booting (not flashing) a magisk patched boot IMG, then using the root to dd flash the engineering abl which allows unlocking. I don't know if that would work for g8s without a brick or if your fastboot even allows fastboot booting
antintin said:
Well I think the bl unlock method for a while for v40 and g7 was crossflashing to a firmware with fastboot and fastboot booting (not flashing) a magisk patched boot IMG, then using the root to dd flash the engineering abl which allows unlocking. I don't know if that would work for g8s without a brick or if your fastboot even allows fastboot booting
Click to expand...
Click to collapse
Thanks alot for the response, that's very hopeful! any place you could point me to the process of flashing the engineering abl? not even sure were to start looking for it on the G8s. P.S im not a noob just a noob to LG
I think my fastboot would allow booting as it does respond to basic commands i've tried so far, only issue is the boot.img's out there are all for the EAW version, anyway to decompile a boot img from a kdz?
Thanks in advance!
corpsegrinder62 said:
Thanks alot for the response, that's very hopeful! any place you could point me to the process of flashing the engineering abl? not even sure were to start looking for it on the G8s. P.S im not a noob just a noob to LG
I think my fastboot would allow booting as it does respond to basic commands i've tried so far, only issue is the boot.img's out there are all for the EAW version, anyway to decompile a boot img from a kdz?
Thanks in advance!
Click to expand...
Click to collapse
Yeah, download the kdz for the exact software version you're on, look up kdztools steadfasterx, go on the GitHub, extract the boot IMG, and patch it in the magisk app. Then try fastboot booting it; flashing it without bl unlock would make it not let you boot, but since fastboot booting worked on g7 and v40, I'd assume it would be ok. You might want to join the telegram group and find someone who knows for certain though
antintin said:
Yeah, download the kdz for the exact software version you're on, look up kdztools steadfasterx, go on the GitHub, extract the boot IMG, and patch it in the magisk app. Then try fastboot booting it; flashing it without bl unlock would make it not let you boot, but since fastboot booting worked on g7 and v40, I'd assume it would be ok. You might want to join the telegram group and find someone who knows for certain though
Click to expand...
Click to collapse
Thanks, im going to try this really appreciate your help here. and the abl any idea how i go about flashing that to unlock? Patching the main boot img from magisk while still locked even if the boot img boots with fastboot obviously still won't work to write boot partition with locked BL would it?
thanks i am in that group and asked several times but got ignored, thats why i thought i would ask here, there are 8 countries on this variant so i figured it would help all if it could be figured out since LG Dev only supports the euro model and this variant can actually be unlocked
corpsegrinder62 said:
Thanks, im going to try this really appreciate your help here. and the abl any idea how i go about flashing that to unlock? Patching the main boot img from magisk while still locked even if the boot img boots with fastboot obviously still won't work to write boot partition with locked BL would it?
thanks i am in that group and asked several times but got ignored, thats why i thought i would ask here, there are 8 countries on this variant so i figured it would help all if it could be figured out since LG Dev only supports the euro model and this variant can actually be unlocked
Click to expand...
Click to collapse
Worry about that later, first figure out if you can fastboot boot a boot IMG. Fastboot flashing it will 100% brick you
antintin said:
Worry about that later, first figure out if you can fastboot boot a boot IMG. Fastboot flashing it will 100% brick you
Click to expand...
Click to collapse
Thanks again, so here is the result.
I am struggling with both kdz tools and kdz firmware extractor, im able to get the DZ and dll files out, but on kdz tools using undz i end up with a bunch of .chunk files, and firmware extractor gives a zlib deflate error and gives a 0 byte file,
Taking this one side, i tried to rename the .chunk to a .img file, fastboot proceeded to download and attempt to boot, but stuck at logo, im guessing because the extraction of the boot img wasn't successful. but fastboot command worked and downloading to the phone worked, and it did attempt to boot, i have no idea now though how to get this kdz extracted. so needless to say without a working boot img i can't confirm 100% all i can confirm is fastboot boot command works.
any ideas?
[EDIT] i changed the unkdz to -c command, it extracted a boot img, i did as you said, patched boot img with magisk, and tried to fastboot boot it, sure enough! booted with dev warning error popups, but went into magisk, root access granted! so the patched boot img works by fastboot booting.
How would i go about the rest though with abl? as far as im aware we still waiting for firehose for G8/s?
corpsegrinder62 said:
Thanks again, so here is the result.
I am struggling with both kdz tools and kdz firmware extractor, im able to get the DZ and dll files out, but on kdz tools using undz i end up with a bunch of .chunk files, and firmware extractor gives a zlib deflate error and gives a 0 byte file,
Taking this one side, i tried to rename the .chunk to a .img file, fastboot proceeded to download and attempt to boot, but stuck at logo, im guessing because the extraction of the boot img wasn't successful. but fastboot command worked and downloading to the phone worked, and it did attempt to boot, i have no idea now though how to get this kdz extracted. so needless to say without a working boot img i can't confirm 100% all i can confirm is fastboot boot command works.
any ideas?
[EDIT] i changed the unkdz to -c command, it extracted a boot img, i did as you said, patched boot img with magisk, and tried to fastboot boot it, sure enough! booted with dev warning error popups, but went into magisk, root access granted! so the patched boot img works by fastboot booting.
How would i go about the rest though with abl? as far as im aware we still waiting for firehose for G8/s?
Click to expand...
Click to collapse
Nice, now you basically have to do the same thing as the other bl unlock guides. You flash the engineering abl to slot b (while on slot a) which needs to have working pie on it. Then you switch to it, go to fastboot, and do fastboot oem unlock.
antintin said:
Nice, now you basically have to do the same thing as the other bl unlock guides. You flash the engineering abl to slot b (while on slot a) which needs to have working pie on it. Then you switch to it, go to fastboot, and do fastboot oem unlock.
Click to expand...
Click to collapse
Thats great! When you say flash though. You mean dd flash with terminal with su to flash boot_b using said root access right? Then using fastboot to switch to boot_b and use that to unlock, correct?
But no abl yet for G8s as far as im aware, so i take it we need to wait on firehose for it or would cross flashing abl from another device work? Also android 10 update is around the corner, im still on pie 10i for now.
Thanks alot for your patience to help
I’ve unlocked my bootloader and rooted previously on the stock A10 ATT rom. I’ve then cross flashed to the A11 CAN version. Bootloader is still obviously unlocked but root is gone. I understand how to root again but I can’t get into bootloader mode to see if I have an active boot_a or boot_b. Does anyone know how to do this or any other way to see which is active? I’ve tried button combinations and ADB reboot bootloader command with no luck. It was working fine previously but I can no longer get into it after crossflashing.
BWA_Dallas said:
I’ve unlocked my bootloader and rooted previously on the stock A10 ATT rom. I’ve then cross flashed to the A11 CAN version. Bootloader is still obviously unlocked but root is gone. I understand how to root again but I can’t get into bootloader mode to see if I have an active boot_a or boot_b. Does anyone know how to do this or any other way to see which is active? I’ve tried button combinations and ADB reboot bootloader command with no luck. It was working fine previously but I can no longer get into it after crossflashing.
Click to expand...
Click to collapse
You probably don't have the engineering abl flashed to the appropriate abl slot. Using that abl is what gives you fastboot. But once you've used it, you have to flash the original back, so that the phone will boot. The engineering abl is based on an earlier version of android.
This is exactly what I needed. Thank you!