I have a pixel 2 which is stuck in bootloader due to "Slot Unbootable: Load Error".
So far I tried to flash / wipe the device with https://flash.android.com/ but the process can't be started due to "Device Unlock Disabled".
Anyone got some hints for me?
Unfortunately your options are rather limited because the bootloader is locked, and because OEM Unlocking is off (get_unlock_ability=0), unlocking it is not possible. This is one of those shortcomings I think should be addressed in Pixel devices but that's another conversation for another time.
Are you able to boot into recovery or Download Mode?
I'll break out my old Pixel 2 when I get home and see if I can figure something out.
Trying to boot into Recovery Mode gives the same Load Error. Trying to boot into Download Mode gives: "ERROR: Operation Denied" .
50g said:
Trying to boot into Recovery Mode gives the same Load Error. Trying to boot into Download Mode gives: "ERROR: Operation Denied" .
Click to expand...
Click to collapse
Yeah, I had the same result on my Pixel 2.
Rescue Mode unfortunately wasn't introduced until the Pixel 3.
Unfortunately I don't think there is any way to fix your device beyond taking it to a repair center and having them replace the mainboard...unless you can find someone who has both the Qualcomm Product Support Tool as well as the necessary files. It's not possible to flash the device via bootloader when bootloader is locked; the prescribed method to update outside of system is via recovery (ADB sideload).
Sorry I couldn't be of more help.
I was concerned that might be the case. Appreciate your efforts.
Related
Hello Everyone,
My moto g phone suddenly started giving errors saying "unfortunately "xxxxx" not working. xxxx is like google play and many more system services. I cannot do anything as it gives the error continuously.
I was trying to factory reset the mobile and I got the error of "boot up failed". I searched for this and found out that I need to go for custom recovery(I'm new to this) to avoid this error and get my phone back to normal.
I found that I need to unlock boot loader to for custom recovery. After trying and searching a lot I managed to do that finally with the help of a thread in this forum.
From that time I tried with many img files like TWRP, CWM and philz. But, still I could not manage to get my phone back to work.
Last 3 days I was fully in to this searching and finding solution and finally thought to write here(I'm not feeling to give up on this). I can provide you with any information needed.
I read in some guidance of CWM recovery that I need to get CWM model to process further after the below command.
Code:
fastboot flash recovery recoveryimage.img
Instead my screen stays with the below content for whatever .img file I pass for the above command
"Android system recovery <3e>
LXB22. 46-28. 1"
Appreciate any help or support on this to get my phone back to work. Thanks in advance
Nazneen said:
Hello Everyone,
My moto g phone suddenly started giving errors saying "unfortunately "xxxxx" not working. xxxx is like google play and many more system services. I cannot do anything as it gives the error continuously.
I was trying to factory reset the mobile and I got the error of "boot up failed". I searched for this and found out that I need to go for custom recovery(I'm new to this) to avoid this error and get my phone back to normal.
I found that I need to unlock boot loader to for custom recovery. After trying and searching a lot I managed to do that finally with the help of a thread in this forum.
From that time I tried with many img files like TWRP, CWM and philz. But, still I could not manage to get my phone back to work.
Last 3 days I was fully in to this searching and finding solution and finally thought to write here(I'm not feeling to give up on this). I can provide you with any information needed.
I read in some guidance of CWM recovery that I need to get CWM model to process further after the below command.
Code:
fastboot flash recovery recoveryimage.img
Instead my screen stays with the below content for whatever .img file I pass for the above command
"Android system recovery
LXB22. 46-28. 1"
Appreciate any help or support on this to get my phone back to work. Thanks in advance
Click to expand...
Click to collapse
Rename the twrp or cwrecovery as recovery and copy to adb folder. Fastboot command is
fastboot flash recovery recovery.img, (not fastboot flash recovery recovery image .img)
pradeeppk said:
Rename the twrp or cwrecovery as recovery and copy to adb folder. Fastboot command is
fastboot flash recovery recovery.img, (not fastboot flash recovery recovery image .img)
Click to expand...
Click to collapse
it is not "recoveryimage". I just used it for this question. I tried with many files. So, I gave the name of the file and used the command and I got the success message also in CLI saying "Okay" and finished. But no file made any difference to device.
I had a pass code to unlock my screen. Two times I was able to get the screen (Other times it become dark after loading M) and it required the authentication code I gave to enter unlock screen. and I was filled with errors showing continuously "unfortunately not loaded 'system files' ". I suspect that whether the flash worked properly because it was asking for the screen unlock code.
Hello,
A few days ago I found my Motorola Moto G Turbo, model MERLIN XT1557 , turned off. When I switched it back on, it did not boot successfully but instead redirected to the bootloader with the message:
"Your device didn't start up successfully. Use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant."
"AP Fastboot Flash Mode (Secure)"
"failed to validate boot image"
"ERROR: Failed to pass validation, backup to fastboot"
"Fastboot Reason: Fall-through from normal boot mode"
"CID Read Failure"
"Invalid CID status 0x69"
I have not unlocked the bootloader or tried to install any custom firmware. As far as I can tell, this occurred spontaneously and without warning (my best guess would be an update that went wrong). For this reason, I have not enabled USB debugging either, so the phone doesn't even let me unlock the bootloader.
Recovery mode does not work, this merely gives the message "failed to validate recovery image". Nor do "Factory", "BP Tools" or "QCOM" do anything (barcodes works). Thus even if I wanted to perform a hard reset, I cannot seem to do it.
Strangely, I seem to be able to access two different types of bootloader interfaces, one with just text and another with a picture of an android. Neither seem to be of much help, however interestingly the one with the android picture states "Software Status: Official" while the pure text one sometimes (not always for some reason?) states "Software Status: Modified". Again, just to reiterate, I haven't performed any custom android modifications.
After all i tried to flash stock firmware, it installed successfully without even a single error and then again the same thing starting to happen, firmware installed but didn't solved the problem, same dual bootloaders menu start appearing.
ok, at last i am able to just boot into my phone,
used
fastboot oem config bootmode factory
Click to expand...
Click to collapse
and reboot. Phone opened in factory mode but still recovery is not accessible.
Working on figuring how can i get into recovery. Flashed twrp, didn't booted in recovery, flashed stock recovery, same result..
Hey yall,
so I finally managed to successfully brick my honor :laugh:
Everything was pretty much fine, I was messing with trying different ROMs. Then I used the "Change location" option in HWOTA8 (it probably flashed some extra files) and my systems "erecovery" or something likely essential "dissappeared".
Fastboot works, I tried flashing 'system' and recovery images with no success. It won't accept TWRP or any other image as I get "partition size get error"
When I try to boot into recovery or system, I get the error
Error Mode message: Func no 11 [recovery image], Error NO 2 [load failed]
I tried dload methods with (B132, B340 and some other versions, I get the Error Mode anyway)
What I think is the core of the problem could be one of following:
boot.img,
erecovery
frp
I get a boot loop no matter what I do.
The phone model is BLN-L22 indian (debranded from BLN-L21) and the last flashed ROM was Oreo
The FRP and Bootloader are unlocked.
I think it could work if I'd flash every partition, but it doesn't seem to work with images I got from "update.app"
Could you recommend me some repair/flashing tools/flashing files?
Any help in the investigation is greatly appreciated
Update: Just bought DC Phoneix
Now I managed able to boot into the "update via usb" screen. (with the help of DC Phoneix)
I can access adb, altho I cannot use adb shell, because it cannot access /bin/sh
Does having access to adb give me any advantage?
Solved using this <3. Now I'm at android 4
https://forum.xda-developers.com/honor-6x/how-to/guide-unbrick-honor6x-boot-fastboot-t3904381
Good morning!
While attempting to flash a stock MIUI 10 ROM into my Xiaomi Redmi Note 7, to downgrade back to Android 9.0 due to some app compatilibty issue, I messed up big time and my phone is now stuck in a loop where the screen turns on, nothing shows up, then it restarts, going off for a few seconds and turning on again.
Power Button + Volume UP successfully brings me to the stock recovery 3.0 from xiaomi.
Power Button + Volume DOWN fails to bring me to the fastboot mode.
If I select the Connect with MIAssistant in the recovery the phone will show up as "sideloaded" after using the command adb devices, but the MIPCSuite app does not see it and the command adb restart bootloader also fails to bring up the fastboot mode, it just gets stuck in the loop again.
More context on what went wrong and caused this: I followed an online tutorial to flash a rom using the MIFlash app, so I unlocked the bootloader and tried to flash the rom usin xiaomi's tool. I got a failed to check sparse crc error code and it went downhill from there when I tried to fix things reading multiple threads on the issue. I tried deleting some lines from the flash_all.bat file and tried to flash it again but then the flashing process went seemingly forever so I aborted the operation and now this loop happens. I tried a few more times but with no success.
The first time I tried to use the tool I used the clean all and lock option so I'm not certain if the miflash tool locked the bootloader regardless of the outcome of the flashing attempt.
Is there hope? Can I fix this phone if I only have access to stock recovery and nothing else (although it shows up in adb devices but can't get into fastbootmode) ?
Thanks a lot to anyone who took the time to read and possibly help.
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
jwoegerbauer said:
Both ADB and Fastboot are Android-side launched by device's bootloader. If you can't enter Fastboot mode then my guess is there is something is wrong with curently installed Android.
BTW: If you lock device's bootloader then bootloader attempts to load device's Stock ROM.
Click to expand...
Click to collapse
I see.
What can I do to try to fix this issue?
I finally managed to fix it through the Emergency Download Mode (EDL). It requires Xiaomi Authentication which I bypassed using this guide: https://www.droidwin.com/fix-mi-account-authorization-unbrick-xiaomi-edl-mode/
With that setup I flashed a stock rom using the MiFlash tool.
Hey guys, I need help flashing my Google pixel 2. It was off for a couple of months and now when I am trying to start it, its not booting without putting it on charge and even then it only shows the battery icon then the google icon and restarts (So a bootloop). But when I press and hold the power button and volume down key, it goes in the fastboot mode ( the one where all device information is shown with an Android Logo) (Pic att).
If I select Download mode, it just shows operation denied and if I select recovery mode then it goes to bootloop again. Also as far as I remember when I last used the phone, the usb debugging was turned off so please suggest what to do from here.
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Alekos said:
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Click to expand...
Click to collapse
Hey thanks for the update man. I know I should have kept atleast oem unlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
mayankggrwl said:
Hey thanks for the update man. I know I should have nlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
Click to expand...
Click to collapse
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Alekos said:
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Click to expand...
Click to collapse
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
mayankggrwl said:
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
Click to expand...
Click to collapse
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Alekos said:
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Click to expand...
Click to collapse
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
mayankggrwl said:
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
Click to expand...
Click to collapse
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how the op in that thread above fixed his Pixel 2 with Skipsoft tool. His Device state said Locked in his screenshot on his post.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
edit--try these commands
fastboot erase system
fastboot erase data
fastboot erase cache
Alekos said:
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how those users in the thread flashed the bootloader image since I didn't think you could if the device state is locked, but worth a try.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
Click to expand...
Click to collapse
Okay great !! Thanks for these. Ill go through that thread and will see if any of the listed methods work. Will also try that software. In a rush so will try these later on and then ill update you.