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.
Related
Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks
How about you
a) Flash an official rom via stock recovery and try it then
b) Ask this question in the Questions and Answers section instead of the Development section because I don't see any development relevant information in this post...
gevenerof said:
Hello
I did accidentally have a power failure on my computer when flashing version 4.0.4 to my Galaxy Nexus and the phone keeps booting on recovery menu automatically.
I have tried to flash different version using fastboot and Odin but always get an error saying my bootloader is locked use "fastboot oem unlock"
When try to unlock using the command the phone displays a selection screen asking to unlock the bootloader YES/NO, If I select YES the fastboot line returns the following error FAILED (remote: Unknown Partition) and the bootloader keep locked.
I have tried a thousand times without success and I am not able to utilize any firmware because is not permitted until I manage to get the bootloader finally Unlocked.
Pls help
Thanks
Click to expand...
Click to collapse
Try using the Gnex Toolkit posted on the development page as a sticky.
since u can't use fastboot (and the toolkit is useless in this case), i think u should try odin
THIS IS NOT DEVELOPMENT
Do not post question threads here
Read forum rules before posting threads
Thread moved
FNM
First of all, use ANY toolkit (Mine's in the description ^^)
Then unlock your bootloader (Open cmdthe type:
Code:
fastboot oem unlock
You'll need ADB/fastboot drivers installed, though...)
There's no point using a toolkit, how it sounds to me is you somehow messed up a partition when flashing the update.
As someone already said try flashing an ota update through the stock recovery (if you have stock recovery)
It was probably the bootloader that got messed up when your power went.
Try flash a new bootloader too, see how that goes.
Fastboot flash bootloader filename.img
I am having the exact same issue. Trying to flash, format or dare i even say erase won't do anything to the bootloader, trying to access recovery on mine it says failed, trying to unlock the bootloader through oem unlock, prompts the failed : remote unknown error code. :S
use the galaxy nexus toolkit to unlock bootloader, root
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Thats true, every tool kit i have tried has failed, even fastboot commands, at least the latter tell you that it fails. Where can i download the bootunlocker app? Does my Nexus 7 have to boot into the rom to do this? Because mine can't. :S
Petrovski80 said:
Apparently the power outage messed up your partitions, causing the unlock command to fail. And since your bootloader is still locked, both fastboot and Odin cannot be used to flash anything. If you have root, you can try unlocking the bootloader with the bootunlocker app.
PS: advice that says 'use toolkit X' is pointless by the way. Toolkits are just GUIs around fastboot and adb, if the raw fastboot commands don't work, Toolkits won't work either.
Click to expand...
Click to collapse
Incorrect.
Signed images will flash correctly with a locked bootloader.
Jubakuba said:
Incorrect.
Signed images will flash correctly with a locked bootloader.
Click to expand...
Click to collapse
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it
AndiS21 said:
Would you be kind to help me with the instructions and the signed image for nexus 7 needed to be flashed over a locked bootloader? I would greatly appreciate it
Click to expand...
Click to collapse
Ask Google or Samsung, they have the keys to sign it. Also, this is the galaxy nexus forums.
Sent from my i9250
OP, OMAP flash?
Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?
I used Nexus Root Toolkit when I got semi-bricked.
Use erase Command on flashboot for data and system then do flash_all again
As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?
hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.
d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.
hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.
Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.
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
Hey guys, Is IT possible to unlock bootloader without approval trom xiaomi? I used mi unlock app on my Pc before approval, and It seems that my phone Is succesfully unlocked. Even in console on Pc it days that the device Is unlocked.
However, I can't flash twrp (It still boots into factory recovery), so I cannot root.
Any help on this case? Do I still need approval and do unlock process again after that?
zoniqon said:
Hey guys, Is IT possible to unlock bootloader without approval trom xiaomi? I used mi unlock app on my Pc before approval, and It seems that my phone Is succesfully unlocked. Even in console on Pc it days that the device Is unlocked.
However, I can't flash twrp (It still boots into factory recovery), so I cannot root.
Any help on this case? Do I still need approval and do unlock process again after that?
Click to expand...
Click to collapse
What happens when you flash twrp?I mean it says failed or successful.
You can run this fastboot command to get bootloader status: fastboot oem device-info
Ww222 said:
What happens when you flash twrp?I mean it says failed or successful.
You can run this fastboot command to get bootloader status: fastboot oem device-info
Click to expand...
Click to collapse
Actually..I got it to work. But when it booted into twrp, I doesn't have magisk copied on phone storage.
Then I tried to reboot phone normally, but I got bootloop. Then I flashed fastboot rom and then it booted into system, but my phone is locked again.
Currently, I'm running MSM Xtended. Unfortunately, I'm unable to root my device. I have tried following the instructions in the MSM thread on how to obtain root, but the command isn't recognized in fastboot. I assume it's because I flashed the latest version of the global rom before flashing MSM. I'm guessing the latest global version upgraded my BL to a version that doesn't support "fastboot boot". Is there another way to go about this without having to wipe my phone and flashing a different global version? Any help is appreciated!
Dont mean to treat you noobish here, but is the bootloader unlocked? I have never heard of fastboot "boot" not being available.. Are you in the bootloader when trying to run this? Does fastboot devices show anything. I'm still newish to the whole fastbootd thing (fastboot reboot fastboot) but when I am running fastboot boot I do it from the bootloader, not fastbootd.
Apologies for the late response, so I'm a dummy that likes to skim. I figured it out after work. Fastbootd does not support "fastboot boot", but regular fastboot does.
@jerryhou85 Sorry to bother, but please close this thread as the issue was resolved.