Related
Dear Esteemed XDA members,
I have spent literally days of testing and researching to try and unbrick my phone. Friends and family have seen my obsession with trying to fix this, some even offering to buy me a new phone!!!! But this ain't about money - this is about having control of my damn device!!! I'm usually pretty good with trying to solve this kind of stuff, but this time I'm truly stumped (and desperate, and obsessed!). I have come to the conclusion that it's directly related to ARM Trusted Firmware. Here are the details of my "journey" to date... please read it, and if you know how to fix it, please share!!! then I can get my life back!!!! Before I go any further, I am certain that my problem was initially triggered by doing an official update on a rooted phone. So to avoid experiencing the same problem I'm about to describe, it's best to unroot and relock your device before loading new official firmware.
I have a Huawei Honor 4x (Che2-UL00, with Kirin 620 chipset) with an unlocked bootloader. Recently, I tried to manually upgrade from Kitkat (emui3.0) to Lollipop (emui3.1), using the official update.app from huawei's website (image was good - I checked the hash). To load the update.app, I used the official huawei recovery. The progress bar went to roughly 90% and then hung. Upon restarting my phone, it went into rescue mode with the following error: Func NO : 15 (bl31 image) Error NO : 1 (security verify failed).
Interestingly, I looked closely at the fastboot.img files for kitkat Vs lollipop (I got the image files by using HuaweiUpdateExtractor). I noticed that only the lollipop fastboot image contains this error message text. Also, bl31 is related to ARM trusted firmware, for more info search for BL31 (Secure Monitor) on google, or see bl31_main.c in the Trusted Firmware source code. So it seems that the lollipop image is using the full ARM trusted firmware, an extra layer of security which is preventing the (unlocked) bootloader from allowing me to load into recovery. I think this is the core problem, and I think there is a way to solve it but I just don't have a deep enough understanding to get there. Below I'll explain each step I went though and provide some additional diagnostic info:
1. First step was to access recovery mode (Vol UP + power). This failed and resulted in same bl31 error message.
2. Second step was to try and update again using the three-button force update (Vol Up + Vol Down + Power). It vibrates once after a few seconds, and freezes with the logo screen with the red light flashing. As an experiment, I tried this without the SDCARD and noticed it vibrated almost instantly, which suggests that it does try to load something from the SDCARD when inserted. I didn't get any further in this mode.
3. Final step I tried was to load into fastboot (Vol Down + Power). This worked and I got into a special "Rescue&Fastboot" mode. First thing I tried was to manually downgrade to kitkat by flashing the kitkat images using the fastboot flash command. The images boot.img, system.img, recovery.img flashed successfully. cust.img simply failed. I desperately wanted to flash the kitkat fastboot.img which doesn't contain the trusted firmware bl31 image stuff, but fastboot replied: FAILED (remote: Command not allowed). In fact, many of the fastboot commands fail with this same error message, even though there is the "PHONE unlocked" writing in red on my phone screen. With the limited command set available (even fastboot oem device-info is not allowed!), here is the diagnostic info I was able to get:
a) fastboot oem check-rootinfo
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1452356543
I think this change from RISK to SAFE is the core of my problem. the change_time is from several days ago when I attempted to update. I think it reflects the trusted firmware state (I'm guessing here, as I can't find documentation for these commands).
b) fastboot oem backdoor info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
I think that FB LockState: LOCKED means that fastboot is locked (guessing again, can't find documentation!), which explains why many of the commands fail.
c) fastboot oem check-image
(bootloader) secure image verify successfully
I think this checks the recovery image, because when I flash a different recovery, this signature check fails
d) fastboot getvar rescue_phoneinfo
rescue_phoneinfo: Che2-UL00 V100R001CHNC00B365
This appears to be the ROM version at the time of purchase.
e) fastboot oem get-build-number
(bootloader): Che2-UL00 V100R001CHNC00B384
This actually corresponds to the build number of kitkat I was using just before the failed upgrade to lollipop.
f) fastboot oem relock mycode
FAILED (remote: root type not allowed).
I tried this just to see if it wold relock. I'm not sure what the error means, but I do not that this command failed with signature verify fail if i change the recovery image.
Here are the questions I want to ask:
1. Can I force the device to flash a new image? I can't get into recovery or have full access to fastboot commands due to the trusted firmware stuff. And as I mentioned earlier the three button trick fails with a freeze at the logo screen. It appears that I need to do this using a means other than fastboot. The only interface I have is Android Sooner ADB Interface. adb devices renders nothing. Only fastboot finds a device.
2. Can I somehow make the "security verify check" pass so that I don't get that bl31 error? I'm not sure exactly which images this bl31 thing is trying to verify! Perhaps some combination of images from the new lollipop stuff I tried to flash and the kitkat build I had running previously?
3. Can somehow disable all this Trusted Firmware stuff??
4. Any other suggestions???
This is driving me to the brink on insanity!!! Gotta figure it out!! Thanks for reading and trying to help!
Hi,
Did anyone solve this problem?
I'm facing the exact same situation.
Che2-UL00 too.
Thanks in advance!
prezident36 said:
Hi,
Did anyone solve this problem?
I'm facing the exact same situation.
Che2-UL00 too.
Thanks in advance!
Click to expand...
Click to collapse
I still find it hard to believe this problem absolutely cannot be solved. However, I took it to a Huawei service center and they weren't able to unbrick it either. They had to replace the mainboard, which seems like a complete waste. Cost around $50, so not the end of the world but still annoying.
Anyway, screw this whole "trusted firmware" rubbish. I'm the owner of the device, yet I'm not "trusted".
hello, i have exactly the same problem!
---------- Post added at 10:58 PM ---------- Previous post was at 10:41 PM ----------
Where do i get the replacement mainboard from?
Me too, upgrading kitkat to lollipop. Now facing that rescue error.
My Honor 4X is unlock bootloader and root before upgrading lollipop,
Hi all,
As a result of some attempts to restore stock rom for KIWI-UL00. I ended up in a pretty bad state :
1. The phone reboots perpetually.
2. Putting a 64gb sd card with stock rom gets the recovery to 5% and then phone gets into the reboots cycle. I actually do not know if the dload/UPDATE.APP is being picked up or the wrong boot flashed in is kicking in.
3. The phone is unlocked, but as a result of the flashing I got FRP lock??? Here is what I see in fastboot mode on the phone screen:
PHONE is Unlocked
FRP Lock
4. Any attempt to flash in a new BOOT, SYSTEM or RECOVERY with fastboot ends up with error:
./fastboot flash recovery ~/Downloads/split_updata.pl/kiw_ul00_B239_Unicom/RECOVERY.img
target reported max download size of 266338304 bytes
sending 'recovery' (55968 KB)...
OKAY [ 1.768s]
writing 'recovery'...
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (Undefined error: 0))
finished. total time: 1.769s
My thinking is that FRP lock is causing denying fastboot, but have no idea how to remove it. Without being able to flash in the correct stock recovery, I don't think I will be able to install the stock rom ever.
There are a lot of stuff written about FRP lock out there, but they assume working phone. In my case, I only have access to fastboot, not even adb!
Any ideas appreciated,
Thanks.
But u still can get it into fastboot right? Isnt it possible to use adb then to root it and put twrp on it and after that put custom firmware on it to get it booted up properly again. And after that installing a stock image again?
Dafriss said:
But u still can get it into fastboot right? Isnt it possible to use adb then to root it and put twrp on it and after that put custom firmware on it to get it booted up properly again. And after that installing a stock image again?
Click to expand...
Click to collapse
fastboot has very limited capabilities (I guess because of the FRP lock?) Some commands work, like this:
./fastboot oem get-bootinfo
...
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) Root State: ROOT
(bootloader) Bootloader WidevineKey: WidevineKey_VALID
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.011s]
finished. total time: 0.011s
but other like erase or flash fail with the same error.
Do you know how to use ADB when the device is in fastboot mode? I currently get this:
./adb devices
List of devices attached
My thinking is that in order for DB to work the device need to be put in recovery mode, something I cannot achieve.
The only other mode i can put the phone in is by holding the UP and POWER it gets into something that has "eRecovery", but the rest is all in Chinese . There are 3 menus you can select with the volume and power (no screen touch). The first one leads to wifi discovery and but nothing after that. The other two top level menus lead to restart - again they are in Chinese, not sure what they do.
hrstoyanov said:
fastboot has very limited capabilities (I guess because of the FRP lock?) Some commands work, like this:
./fastboot oem get-bootinfo
...
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) Root State: ROOT
(bootloader) Bootloader WidevineKey: WidevineKey_VALID
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.011s]
finished. total time: 0.011s
but other like erase or flash fail with the same error.
Do you know how to use ADB when the device is in fastboot mode? I currently get this:
./adb devices
List of devices attached
My thinking is that in order for DB to work the device need to be put in recovery mode, something I cannot achieve.
The only other mode i can put the phone in is by holding the UP and POWER it gets into something that has "eRecovery", but the rest is all in Chinese . There are 3 menus you can select with the volume and power (no screen touch). The first one leads to wifi discovery and but nothing after that. The other two top level menus lead to restart - again they are in Chinese, not sure what they do.
Click to expand...
Click to collapse
Isnt eRcovery from EMUI itself to save bricked phones? Like booting in new software or something? Maybe there are some video's about it on youtube???
I had some sort of the same issue but never had problems with frp lock before, i actually used a video from xda to get my honor 5x working again. I'll look for the link so you can see if the same steps work for you!
---------- Post added at 01:01 AM ---------- Previous post was at 12:59 AM ----------
Maybe thid will work when you make a walk around the rebooting parts
Dafriss said:
Isnt eRcovery from EMUI itself to save bricked phones? Like booting in new software or something? Maybe there are some video's about it on youtube???
I had some sort of the same issue but never had problems with frp lock before, i actually used a video from xda to get my honor 5x working again. I'll look for the link so you can see if the same steps work for you!
---------- Post added at 01:01 AM ---------- Previous post was at 12:59 AM ----------
Maybe thid will work when you make a walk around the rebooting parts
Click to expand...
Click to collapse
I saw the video, thanks. However, as you noticed in the video, not only phones boot ok, but when in fastboot mode, his phone reads:
Phone Unlocked
FRP Unlocked
When FRP is unlocked you can do all sorts of things with fastboot. I am not that lucky :crying:
hrstoyanov said:
I saw the video, thanks. However, as you noticed in the video, not only phones boot ok, but when in fastboot mode, his phone reads:
Phone Unlocked
FRP Unlocked
When FRP is unlocked you can do all sorts of things with fastboot. I am not that lucky :crying:
Click to expand...
Click to collapse
relax buddy, try dload method with any other version of stock firmware,
and if it doesnt help,
first find a rollback update.app package for your particular variant, first flash it
then , go back to lollipop firmware with the same dload method,.
you should be booted to lollipop firmware,
than, go on to developer options and enable oem unlock option
start from there..
thilak devraj said:
relax buddy, try dload method with any other version of stock firmware,
and if it doesnt help,
first find a rollback update.app package for your particular variant, first flash it
then , go back to lollipop firmware with the same dload method,.
you should be booted to lollipop firmware,
than, go on to developer options and enable oem unlock option
start from there..
Click to expand...
Click to collapse
The problem is that the "dload/update.app on sdcard" method only works if the phone has stock recovery and I blew that one off.
In order to flash in the stock recovery, i need the FRP lock removed, otherwise fastboot gives me the above errors . See my problem?
the eRecovery seems more hopeful. But is all in Chinese. I got to the first step where it finds my wireless network. I put the password for the WIFI
and it starts doing omething, but fails with big red exclamation mark and tones of thing written in chinese...
hrstoyanov said:
The problem is that the "dload/update.app on sdcard" method only works if the phone has stock recovery and I blew that one off.
In order to flash in the stock recovery, i need the FRP lock removed, otherwise fastboot gives me the above errors . See my problem?
the eRecovery seems more hopeful. But is all in Chinese. I got to the first step where it finds my wireless network. I put the password for the WIFI
and it starts doing omething, but fails with big red exclamation mark and tones of thing written in chinese...
Click to expand...
Click to collapse
how could you actually blow up recovery dude??
thilak devraj said:
how could you actually blow up recovery dude??
Click to expand...
Click to collapse
I think I flashed in the wrong HUAWEI recovery image - I used the latest stock rom for KIWI-L24, but my phone is KIWI-UL00.
I would love to be able to put the right one in, but the FRP Lock issue is preventing me. I don't understand how can the phone be unlocked but have a FRP lock??? See the FASTBOOT commands I used in earlier in this thread.
hrstoyanov said:
I think I flashed in the wrong HUAWEI recovery image - I used the latest stock rom for KIWI-L24, but my phone is KIWI-UL00.
I would love to be able to put the right one in, but the FRP Lock issue is preventing me. I don't understand how can the phone be unlocked but have a FRP lock??? See the FASTBOOT commands I used in earlier in this thread.
Click to expand...
Click to collapse
I'm having the same problem since 4months ago. Fed up of trying myself anymore so I Brought it to many phone shops but no one can repair. Might want to consider replacing the Mother board. anyone with solution pls help! Stupid FRP locked
hrstoyanov said:
I think I flashed in the wrong HUAWEI recovery image - I used the latest stock rom for KIWI-L24, but my phone is KIWI-UL00.
I would love to be able to put the right one in, but the FRP Lock issue is preventing me. I don't understand how can the phone be unlocked but have a FRP lock??? See the FASTBOOT commands I used in earlier in this thread.
Click to expand...
Click to collapse
rexaze said:
I'm having the same problem since 4months ago. Fed up of trying myself anymore so I Brought it to many phone shops but no one can repair. Might want to consider replacing the Mother board. anyone with solution pls help! Stupid FRP locked
Click to expand...
Click to collapse
FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options
Have you tried booting up TWRP from download mode and see if that works?
Fastboot boot TWRP.img
Sent from my KIW-L24 using Tapatalk
From aboot.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
fastboot oem frp-unlock
or
fastboot oem frp-erase
try if it works
2. Putting a 64gb sd card with stock rom gets the recovery to 5% and then phone gets into the reboots cycle. I actually do not know if the dload/UPDATE.APP is being picked up or the wrong boot flashed in is kicking in.
.[/QUOTE]
This part of your post makes it sound like at least one part of recovery is still functioning. (I think there are 2 recoveries on the 5x, but I don't know the details).
I also had the "stuck at 5%" problem when trying to use the "dload" method. Here was my experience:
1) Using 64gb SD card (Class 10 or something fancy)
I was never able to do a stock recovery. Despite many tries after reformatting the card, recovery process always terminated at approximately 5% ending in a reboot without applying the update (which in your case would probably be a bootloop since the existing system is bad).
2) Using 8gb SD card (An old card, class 2)
This worked the first time. I was literally about ready to throw this phone away and send an angry message to Honor, and only tried this out of desperation. I've used it multiple times since, and dload recovery always works with this card.
My conclusion was that this phone cannot seem to read all SD cards properly. I'm not sure if the problem is capacity (over 32gb??), speed class, or brand. Try another card and it may save you. To be safe, it's probably best to be a smaller size, lower speed class card.
dpredster said:
Have you tried booting up TWRP from download mode and see if that works?
Fastboot boot TWRP.img
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
Thank you so much, this worked for me
lukedunk said:
2. Putting a 64gb sd card with stock rom gets the recovery to 5% and then phone gets into the reboots cycle. I actually do not know if the dload/UPDATE.APP is being picked up or the wrong boot flashed in is kicking in.
.
Click to expand...
Click to collapse
This part of your post makes it sound like at least one part of recovery is still functioning. (I think there are 2 recoveries on the 5x, but I don't know the details).
I also had the "stuck at 5%" problem when trying to use the "dload" method. Here was my experience:
1) Using 64gb SD card (Class 10 or something fancy)
I was never able to do a stock recovery. Despite many tries after reformatting the card, recovery process always terminated at approximately 5% ending in a reboot without applying the update (which in your case would probably be a bootloop since the existing system is bad).
2) Using 8gb SD card (An old card, class 2)
This worked the first time. I was literally about ready to throw this phone away and send an angry message to Honor, and only tried this out of desperation. I've used it multiple times since, and dload recovery always works with this card.
My conclusion was that this phone cannot seem to read all SD cards properly. I'm not sure if the problem is capacity (over 32gb??), speed class, or brand. Try another card and it may save you. To be safe, it's probably best to be a smaller size, lower speed class card.[/QUOTE]
this might be one of my chances.. i trieda 32gig card.. so ill try a 8gig.. if this works im gonna kiss all of you guys.. looking for a solution sincetwo days.. with a hour sleepbreak... thnks for the tip for themoment.
Sent from my HUAWEI HUAWEI GRA-L09 using XDA Labs
maxprzemo said:
From aboot.img
Code:
fastboot oem frp-unlock
or
fastboot oem frp-erase
try if it works
Click to expand...
Click to collapse
can u explain a bit more
---------- Post added at 03:37 PM ---------- Previous post was at 03:35 PM ----------
dpredster said:
Have you tried booting up TWRP from download mode and see if that works?
Fastboot boot TWRP.img
Sent from my KIW-L24 using Tapatalk
Click to expand...
Click to collapse
how ?
Hello!! sorry for the bump, but I have exactly the same problem. Bootloader unlock, but FRP LOCK
Phone is bricked.
Updateapp fails to install at 5%
Any solution? Totally stuck.
---------- Post added at 08:57 PM ---------- Previous post was at 08:55 PM ----------
maxprzemo said:
From aboot.img
Code:
fastboot oem frp-unlock
or
fastboot oem frp-erase
try if it works
Click to expand...
Click to collapse
what's this about? aboot?
maxprzemo said:
From aboot.img
Code:
fastboot oem frp-unlock
or
fastboot oem frp-erase
try if it works
Click to expand...
Click to collapse
I am having the same problem (boot = unlocked, frp = lock) and here's what I get from those commands:
-----------------------
D:\_TEMP\Portables\ADB Tools>fastboot oem frp-unlock
...
FAILED (remote: oem_frp_check_password failed! Error = -1)
finished. total time: 0.013s
-----------------------
Whatever the FRP-Check Password is, I don't have it. I tried the OEM unlocker Code as well as the (former) google password (ok, just a stupid try).
donschmidto said:
From aboot.img
I am having the same problem (boot = unlocked, frp = lock) and here's what I get from those commands:
-----------------------
D:\_TEMP\Portables\ADB Tools>fastboot oem frp-unlock
...
FAILED (remote: oem_frp_check_password failed! Error = -1)
finished. total time: 0.013s
-----------------------
Whatever the FRP-Check Password is, I don't have it. I tried the OEM unlocker Code as well as the (former) google password (ok, just a stupid try).
Click to expand...
Click to collapse
Relock bootloader and unlock again. This way u can unlock frp
hello guys, yesterday i just thought lets reflash a .kdz, because my phone was having problems with the MAC adress on Lineage.
i flashed v20d, phone worked, MAC was still 00:00:00:00:00, but i thought tf, i dont care, lets unlock and flash lineage again.
then i suddently realised that my unlock.bin didnt work.
if i check imei it says:
fastboot getvar imei
imei:
finished. total time: 0.016s
empty? the system recognizes the IMEI... maybe wrong bootloader/modem? i cant flash any bootloaders nor modems, because of my bootloader beeing locked/unlockable.
have a nice day
EDIT: thanks to my dumbness searching a whole night everywhere and trying to dump nv/reset imei and other (maybe even illegal) things i found a thread that describes the same situation:
flash .kdz in UPGRADE mode, then immediatly (without reboot) boot into stock recovery (which means data wipe). after this fastboot found my real IMEI.
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
marceloariel said:
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
Click to expand...
Click to collapse
Thanks for the reply. I actually tried this as well but it did not work. MiFlash just appears to be running the flash_all_lock.bat script on Windows and it failed because the bootloader was not already unlocked according to its debug logs when I ran it. I should have mentioned that above.
Not sure if it will help but did you try a factory reset?
Press and hold the Power+Volume Down buttons untill you see the android with the no command. Press and hold the Power button. Press and release the Volume Up button once then release the Power button. Then you should see some recovery options.
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
sensig said:
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
Click to expand...
Click to collapse
The issue is caused by fastboot rom containing dummy system_b image and flashing script "forgetting" to force partition A as active. If a phone has B as an active partition and someone uses flash_all_lock.bat script, the phone's screwed. No idea what brought Xiaomi to this "brilliant" idea, not only there is a higher chance to brick the phone, but the zip file is also unnecessarily larger.
With locked bootloader it isn't possible to switch active partition anymore, so the phone is a (semi)brick. EDL mode is usually used to reflash locked bootloaders.
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
There are two commands for setting active partition, depending on the fastboot version. It's either old
fastboot set_active a
or newer
fastboot --set-active=a
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
if you open flashing script file (.bat or .sh) in a text editor, you will see that fastboot is flashing system.img to system_a partition and system_other.img to system_b partition. That system_other.img is a dummy image and is not bootable. You either:
Option 1: Set active partition to A before running any stock flashing script.
Option 2: Replace system_other.img to system.img in the script.
Option 3: Force partition A after flashing userdata.img and before any lock or reboot command.
dephekt said:
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
Click to expand...
Click to collapse
I am in the same exact position with my Mi A3... did you ever resolve this and if so how?
mewcatchew said:
I am in the same exact position with my Mi A3...
Click to expand...
Click to collapse
What causes led to this behavior ?
htn711 said:
What causes led to this behavior ?
Click to expand...
Click to collapse
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
Click to expand...
Click to collapse
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting).
Click to expand...
Click to collapse
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
garylawwd said:
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
Click to expand...
Click to collapse
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
---------- Post added at 02:40 PM ---------- Previous post was at 02:30 PM ----------
htn711 said:
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
Click to expand...
Click to collapse
Did you read my posts? I get "locked state error" with fastboot commands. I can reboot bootlader in fastboot, and it tjust reboots into fastboot - thats just about all i can do. It wont let me change anything, can only get info and reboot...
mewcatchew said:
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
Click to expand...
Click to collapse
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
garylawwd said:
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
Click to expand...
Click to collapse
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
Ya I wouldn't go trusting some random Russian site either. I don't think there is anything you can do without either
A) going into edl and using a verified mi account
B) bringing it to a service centre (which nobody wants to do)
In fastboot you can't get any commands to work now right? Your device is fully locked again?
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
That Russian site is run by the XDA guy from what I understood. There are other paid services which have Xiaomi service accounts, I only pointed you to the cheapest "verified" eshop. Just Google another one if you don't trust Russians. All of them will need to connect to your PC over Teamviewer and do the flashing, you will just follow the instructions (connect the phone, reboot it etc.).
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11. Many guides online seem to gloss over needing the bootloader unlocked before root. TMALSS; I'm not sure if the non-international version can be bootloader unlocked and/or if I can root without needing this. Long version of what I've tried is below:
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Thus to unlock the bootloader, I am following a guide from TWRPupdate:
It says to perform 'adb reboot bootloader' and then 'fastboot oem device-id':
Code:
C:\adb-platform-tools>fastboot device-id
fastboot: usage: unknown command device-id
My phone only reboots into normal mode whenever running reboot bootloader command within ADB.
I can run fastboot commands when I run 'adb reboot fastmode' but I don't believe this is true fastmode. As I have tried everything mentioned here, such as cables or different computers. Essentially most fastboot commands I've tried do not work except for showing my device as listed / connected.
I have also tried the drivers from LG / Google / ADB separately. And on 2 computers.
Is it possible that I don't have rescue mode or a bootloader still? As I get a black screen when entering recovery mode (but my computer recognizes A device), but adb nor fastboot does. I used to see the recovery screen logo, but I stopped seeing this screen either after updating to Android V11 or reading/backing-up the partitions in QFIL.
In last resort, I have tried rooting via patching the boot image using Magisk v23. I downloaded the firmware for my carrier, converted the KDZ to DZ via Python, and extracted the boot.img_117638 file. Given the file is 0 bytes with nothing in text edit, I still converted it to an img file. But in the kdztools android app, when I select this image file and run, I get:
Code:
!Invalid input file
!Installation failed
I'm guessing the boot.img file should have some data in it. But I'm not sure this method would even work due to the fastboot issues, especially with 'download to device' errors.
-------
I'm just at a standstill on what to even try next. I don't see many people having this much trouble unlocking/rooting their v60. Did the OTA Android v.11 break the root-ability?!
PS: Debugging and OEM unlock are both set in developer options. I can also list drivers used if need.
Thanks for the help in advance!
While digging I also found a post by alexenferman whom managed to use QFIL to root many older ZTE smartphones. They state it may but likely won't work on newer flagship phones. It's a great tutorial I'll have to try soon, but is there a reason it likely won't work here?
kyij said:
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11.
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
NGOwner said:
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
Click to expand...
Click to collapse
Haha, I remember reading that and still continued
I am on Verizon myself using this TM model. I know the phone was unlocked to the point where I could use it with Verizon. I even got 5g using my old 4g sim card.
Anyhow.. I have tried using that command already, and get the same 'command not supported issue'.
Code:
C:\adb-platform-tools>fastboot devices
LMV600TMc40cxxxx fastboot
C:\adb-platform-tools>fastboot oem unlock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Again have tried different computers and cables as I've read fastboot can be pretty picky too.
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
NGOwner said:
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
Click to expand...
Click to collapse
Yes I do, I have turned it off and back on as well.
Well then at this point, I'm tapped out. Smarter folks than me will need to step in and take up the mantle.
[NG]Owner
I ended up posting a form to reddit where about 10 people insisted I did something wrong, and with little surprise -- I did.
I did not flash the engineering bootloader after saving a copy.
Makes a lot more sense since it seemed like a lot of steps to backup without actually doing anything
Thanks NG for the help too!
are you success to unlock bootloader yet. if no i will show you
adb reboot fastboot> select reboot bootloader on your phone> fastboot oem unlock