Database Develop

Help reflashing stock Android

Hello.
My Nexus 6 is out of warranty, so I'm doing my best to get it working myself because I can't get it replaced for free.
So, several months ago, my Nexus 6 (running Android 6.0.1 MOB30O) restarted on its own and showed a "Device is corrupt" message before booting (information at g.co/ABH; red error). I was concerned about the security of my device, so I performed a factory reset. Upon trying to set the phone up again, I found that after connecting to Wi-Fi, the phone would loop indefinitely while periodically saying that Google Play Services has crashed. I once tried leaving it overnight while it was "Checking connection" or whatever, and it still did not move to the next phase of setup. I have tried this on several different networks, and when I intentionally use a wrong password, the phone doesn't connect. So, I have no reason to believe the Wi-Fi connection is the problem. I have tried performing a factory reset from Android Recovery dozens of times, and it still doesn't work. So, I'm effectively limited to the boot menu to interact with my phone (so, I can't access Developer Options because I can't set up my phone). Also, most of the times I boot up my phone, I still get that red error during boot.
So, I've been trying to reflash stock Android. I tried using Nexus Root Toolkit to do that several times, and it never works (I get to a part in the process where it says to set up the phone and enable Developer Options, but I still can't set up the phone). I then decided I would try to do it myself since that tool wasn't fixing the problem. I am able to get ADB connected using the "Apply update from ADB" option within Android Recovery, but whenever I try to sideload one of the Shamu factory images, I get a C++ (I think) error:
Code:
loading: 'C:\Users\dpowell\Downloads\shamu-mob30o.zip'...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
I just updated all the ADB-related stuff from within Android Studio, so it all should be up-to-date.
So, I don't know what to try next. I've used Nexus Root Toolkit to root my Nexus 7 successfully, but I've never tried to modify my Nexus 6 before it stopped working. Regardless of what images I try to put onto the Nexus 6, it always shows MOB30O as the current image in the bootload menu.
Any thoughts or suggestions? I really would like to get this device working again, and Motorola would charge me $170 to replace it because it's not under warranty anymore.
Thank you for your help.

dpowell11 said:
Hello.
My Nexus 6 is out of warranty, so I'm doing my best to get it working myself because I can't get it replaced for free.
So, several months ago, my Nexus 6 (running Android 6.0.1 MOB30O) restarted on its own and showed a "Device is corrupt" message before booting (information at g.co/ABH; red error). I was concerned about the security of my device, so I performed a factory reset. Upon trying to set the phone up again, I found that after connecting to Wi-Fi, the phone would loop indefinitely while periodically saying that Google Play Services has crashed. I once tried leaving it overnight while it was "Checking connection" or whatever, and it still did not move to the next phase of setup. I have tried this on several different networks, and when I intentionally use a wrong password, the phone doesn't connect. So, I have no reason to believe the Wi-Fi connection is the problem. I have tried performing a factory reset from Android Recovery dozens of times, and it still doesn't work. So, I'm effectively limited to the boot menu to interact with my phone (so, I can't access Developer Options because I can't set up my phone). Also, most of the times I boot up my phone, I still get that red error during boot.
So, I've been trying to reflash stock Android. I tried using Nexus Root Toolkit to do that several times, and it never works (I get to a part in the process where it says to set up the phone and enable Developer Options, but I still can't set up the phone). I then decided I would try to do it myself since that tool wasn't fixing the problem. I am able to get ADB connected using the "Apply update from ADB" option within Android Recovery, but whenever I try to sideload one of the Shamu factory images, I get a C++ (I think) error:
I just updated all the ADB-related stuff from within Android Studio, so it all should be up-to-date.
So, I don't know what to try next. I've used Nexus Root Toolkit to root my Nexus 7 successfully, but I've never tried to modify my Nexus 6 before it stopped working. Regardless of what images I try to put onto the Nexus 6, it always shows MOB30O as the current image in the bootload menu.
Any thoughts or suggestions? I really would like to get this device working again, and Motorola would charge me $170 to replace it because it's not under warranty anymore.
Thank you for your help.
Click to expand...
Click to collapse
Hello,
The error you get from adb is coming from a problem with latest ADB Rev.25.0.4
Check this: https://issuetracker.google.com/issues/37139736
In Android studio are you able to revert to a previous version, no?
Rev.25.0.3 should work...
I assume your bootloader is locked?!
Good luck...

5.1 said:
Hello,
The error you get from adb is coming from a problem with latest ADB Rev.25.0.4
Check this: https://issuetracker.google.com/issues/37139736
In Android studio are you able to revert to a previous version, no?
Rev.25.0.3 should work...
I assume your bootloader is locked?!
Good luck...
Click to expand...
Click to collapse
Yes, my bootloader is locked.
Thank you, that fixed the ADB problem. I just saw that they actually have a Rev.25.0.5 now, so I am using that.
I tried sideloading first one of the Android 7 images, and that didn't work. So, I tried MOB30O again, and that also didn't work. Here's the error I'm getting:
Code:
E:footer is wrong
E:signature verification failed
Installation aborted.
The Shamu files I was trying to flash are the ones found at https://developers.google.com/android/images#shamu. Is this not what I'm supported to be using?
I don't know how relevant this is, but again, I'm using the "Apply update from ADB" option in Android Recovery, and all I did from my command line is "adb sideload [file]".
Thank you.

dpowell11 said:
Yes, my bootloader is locked.
Thank you, that fixed the ADB problem. I just saw that they actually have a Rev.25.0.5 now, so I am using that.
I tried sideloading first one of the Android 7 images, and that didn't work. So, I tried MOB30O again, and that also didn't work. Here's the error I'm getting:
The Shamu files I was trying to flash are the ones found at https://developers.google.com/android/images#shamu. Is this not what I'm supported to be using?
I don't know how relevant this is, but again, I'm using the "Apply update from ADB" option in Android Recovery, and all I did from my command line is "adb sideload [file]".
Thank you.
Click to expand...
Click to collapse
Hey,
WTF
You can't sideload a factory image
Download a proper OTA here: https://developers.google.com/android/ota#shamu
And try again.
Good luck...

5.1 said:
Hey,
WTF
You can't sideload a factory image
Download a proper OTA here: https://developers.google.com/android/ota#shamu
And try again.
Good luck...
Click to expand...
Click to collapse
Yeah, I understand about 40% of what I'm doing. Thanks for helping.
So, I sideloaded N6F26Y, which is 7.1.1. Here is the debug info I got:
Code:
Installing update...
Target: google/shamu/shamu:7.1.1/N6F26Y/3821691:user/release-keys
Patching system image unconditionally...
E:unknown command [log]
E:unknown command [log]
Writing bootloader...
Writing radio...
script succeeded: result was [1.000000]
Install from ADB complete.
So, it looks to me like that worked, but at the top of my screen, it still says 6.0.1/MOB30O. Also, it always makes me slightly nervous to see error messages. Do I need to reboot to bootloader in order for changes to take effect? Does it look like anything went wrong?
I know that manually messing with the operating system is potentially risky, so I didn't want to continue from here without knowing if there's anything else I needed to do.
Thank you so much for your help.

dpowell11 said:
Yeah, I understand about 40% of what I'm doing. Thanks for helping.
So, I sideloaded N6F26Y, which is 7.1.1. Here is the debug info I got:
So, it looks to me like that worked, but at the top of my screen, it still says 6.0.1/MOB30O. Also, it always makes me slightly nervous to see error messages. Do I need to reboot to bootloader in order for changes to take effect? Does it look like anything went wrong?
I know that manually messing with the operating system is potentially risky, so I didn't want to continue from here without knowing if there's anything else I needed to do.
Thank you so much for your help.
Click to expand...
Click to collapse
Hey,
You know everyone has to start somewhere. 40% is not that bad. :good:
Factory reset once again, just in case. And reboot.
Should be good now (hopefully). Let me know...
Cheers...

5.1 said:
Hey,
You know everyone has to start somewhere. 40% is not that bad. :good:
Factory reset once again, just in case. And reboot.
Should be good now (hopefully). Let me know...
Cheers...
Click to expand...
Click to collapse
Dude. It works.
Man, this phone had been out of commission for months. I am so happy to have it working again.
Thank you very much for your help. I really appreciate it a bunch.

dpowell11 said:
Dude. It works.
Man, this phone had been out of commission for months. I am so happy to have it working again.
Thank you very much for your help. I really appreciate it a bunch.
Click to expand...
Click to collapse
Hey,
Great! I'm glad for you...
Keep reading on this site. There's plenty of usefully threads, infos, etc...
Enjoy your phone...
Cheers...

[SOLVED!] ULTRA Brick - Oreo Firmware OB16 Over Nougat ROM/kernel/TWRP DESTRUCTION?

Or as bricked as these Qualcomm devices CAN be?
Hey all,
The TL;DR is basically where the list starts
I was running Blu's TWRP v45, the latest PureFusion, Blu's latest Custom kernel, had OB15 firmware underneath. I had been SO USED to simply downloading the newest firmware from kamilmirza's AFH page and just flashing it + it being totally fine that I did it without thinking for OB16. I wasn't too worried because about a week ago I had flashed the unofficial Oreo Lineage and it worked just fine! Plus, I just assumed if it died I could just restore a backup or re-flash the older OB. But as soon as I flashed the new firmware/modem by itself this time on an otherwise perfectly running device, I only saw the OnePlus splash screen. No booting, no access to recovery, no NOTHIN.
I tried flashing the beta TWRP version afterward via fastboot but no dice. Also tried temporary booting via fastboot to it, flashing Blu's again, booting to that. Everything the same result. Splash screen & nothing more. I then went to the extent of trying to format all the partitions and flash a boot.img or do a "-w update" or "flashall" command via fastboot. Because everything out in the universe is a recovery-flashable-zip, it seems like there's no way I can flash the necessary OTA stuff to bring it back to life!
My only remaining idea is getting this damn unbrick tool to work (duhh). I can see the Qualcomm HS-USB QDLoader 9008 in device manager after doing the Vol Up (only) and plugging the cable in. BUT the MSMDownloadTool just cannot see the device. Not in bootloader, not in the weird Vol-Up/cable state. [This is with Qualcomm drivers QUD.WIN.1.1 Installer-10037.3 Setup.exe, the official OnePlus drivers, ADB & Fastboot installed.]
Sorry for long explanation. In the end, what I'm left with is:
Blank formatted partitions (I hope... I'm not even positive they wound up formatted from the fastboot commands)
Fastboot is detected, but no ADB devices are found
Can get to bootloader, but nothing else
No recovery access - Flashing beta akhilnarang Oreo recovery does nothing. Flashing stock recovery does nothing. Flashing Blu_Spark recovery does nothing. (The fastboot commands succeed though each time somehow)
So far the only suggestion I've received is trying the MSMDownloadTool/unbrick process on another computer.
Does anyone have ANY ideas? From my experience, it seems like what might help me would be if a folder with the specific partition images existed for the OTAs, like how Google offers. (boot.img, recovery.img, user-data.img, system and so on). Am I wrong in thinking that? OnePlus has told me this simply does not exist and cannot give me anything like that (don't know why, when they already offer all the OTA flashables...)
PS - OnePlus support just absolutely refuses to even let me communicate to a "level 2" representative to ask a couple of the more technical questions about it. I can't understand why. They are insisting I start an RMA and send it for repair. They even initially scheduled a time for me to talk to higher level rep and then thought up a reason to cancel it via email an hour or so later...
Edit: Just in case the thread gets large and people don't read further posts, this is using:
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. Have the watermark bottom right of desktop
It's with the stock DASH cable
Tried multiple ports
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times
Tried starting the tool BEFORE the device is plugged in, as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
HOW IT GOT SOLVED:
At the end of the day, I had to fight and convince OnePlus support to grant me a remote session with Level 2 Support.
(Attached final image) These two password protected RAR files had almost identical tools as the Unbrick tutorial on XDA.
The major difference was that MSMDownloadTool was version 3.0.8 ***does anyone have this version??*** I can't get into these RARs. The 3.0 tool circulating did not work for me. We might need the newer version as time goes on?? Otherwise, the process was identical.
Unfortunately, the image they used was for 7.1.1. I had to unlock the bootloader and after doing that and getting OB15 & the RR build I wanted, etc, I then realized my phone was force-encrypted as well.
The only toolkit that worked for force decrypting once everything else worked was:
OnePlus_3_3T_5_64bit_TOOLKIT_by_Neisor
Finally, something like 3 clean flashes later, we Gucci.
Thanks for the attempted help to those that did! Hopefully this can help someone else.

Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
As long as you can turn your phone off and on, it's doable. But you need to do that USB plugging + volume up thing while phone is totally off (you can hear Windows making bling when you connect it while pressing volume up, but phone itself stays screen off). And there shouldn't be anything on the screen before/while MSMtool do its job.
You can try different USB ports too.

Eremitus said:
Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
Click to expand...
Click to collapse
Hahaha yes...... That's why I made this post though! It SEEMS like it should be possible to recover from this since fastboot commands + bootloader work! It SEEMED like it would be easy to recover from if anything went wrong... But, here I am.
Oh yeah forgot to mention ~
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. That part of the process went totally fine with BIOS and installing stuff, etc.
Also, shot in the dark but might @Funk Wizard have any ideas? Sorry to call out for this

Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
btw, I messed up my phone in nearly similar case, flashing wrong firmware when using leaked H2OS ROM.

Eremitus said:
Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
Click to expand...
Click to collapse
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others

purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
Hmm, ok.
Stock dash cable works, so that part is ok. Also usb3.0 ports should work too, atleast for me. So everything else seems to be ok except the MSMtool itself

Try different cable, bin there done that!!

purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
I hope you find a solution, since my experience sounds similar to yours Ill share it and maybe you can find something to help out.
I was exactly where you are for about 3 hours last night.
Boot would always get stuck at the splash screen. Could boot into Fastboot, tried using the Skipsoft tool to fastboot flash a stock image but it kept failing.
As far as the Unbrick Tutorial goes, I know the first thing I kept messing up was thinking I needed to press the power button while holding the volume up and connecting to the PC
Also when I tried to manually update the driver on "Qualcomm 9088" it said it was already up to date.
Then I just ran the MSMTool it flashed 6.0.1 back on my phone and I was back in business.
Im sure this is the guide you followed: Here
I found another on the oneplus forums that is essentially the same but goes into a little more detail in the steps: Here
Since I was back completely Stock including Recovery I went ahead and sideloaded OB16 to get the firmware and modem then went about rooting, unencrypting etc...
Lost a few days worth of files but I'm back running LunuxOS Oreo right now.
Good luck I know how you feel. :good:

I've got it revived! I'll update OP. Sadly, it required OnePlus's intervention.

Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful

guilhermeferrari said:
Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful
Click to expand...
Click to collapse
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!

purplepenguin said:
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!
Click to expand...
Click to collapse
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.

namefaisal said:
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.
Click to expand...
Click to collapse
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??

Yeah, I got it open
purplepenguin said:
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??
Click to expand...
Click to collapse
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.

New Files without Password
namefaisal said:
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.
Click to expand...
Click to collapse
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing

@Sam Nakamura

namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,

cdorrell12000 said:
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,
Click to expand...
Click to collapse
You are most welcome.
Sadly everyone gets unbricked with these files but My device didn't. I have to send the device to the service center now. It seems my case is a hardware issue. Tough luck

namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
thanks a lot saved my day !!

purplepenguin said:
@Sam Nakamura
Click to expand...
Click to collapse
Sorry, I just saw your mentioning somehow I missed it, happy you got your phone back already, unfortunately not independent for big OP, did you guys already share this new 3.08 MSM-download-tool to the well established threads or did you I missed this too? This information and according files should be shared with the community and easy to find for those poor souls who unintentionally killed their beloved device...
---------
Edit: further sharing isn't necessarily needed, you did already a pretty good job by naming the thread and describing the situation thoroughly, only suggestion could be to link the updated MSM-download-tool download to the first post with some hint, just an idea though...
Cheers
Sent from my OnePlus 3T using XDA Labs

HELP Recover files: Moto G 2014 16GB XT1033 low battery, bootloop, now hard bricked

Hello guys, I'll try to explain what happened giving just a few context that may help give me some right direction to recover the user data that were in the phone.
As this thread got longer than I expected, summarising:
Moto G XT1033 drained battery, got into bootloop, only fastboot was working, couldn't get into recovery mode ("boot up failed"). When I tried to replace battery, after power on it's now bricked (as "qhsusb_bulk" in PC). My main goal, save user data (whatsapp folder mainly), to flash and restore Android.​
Whole situation detailed, what happened:
I have a Motorola Moto G 16GB Music Edition Dual SIM XT1033 (Music edition) 2014, sold in Brazil. It was working for all these years fine, avoided upgrading Android KitKat from 4.4 because it just worked fine. In past months I noticed the battery holding less and less charge, but as I intended to buy a new phone soon I didn't care.
Unfortunately, couple days ago I heard the sound of notification "low battery... powering off". Then I plugged the charger cable and waited some time, after that, I thought it would just boot up normally, it showed "M" loading screen, with the animation etc, but it went to black screen and loop to loading screen again and again.
I tried to hold power and volume down, it went to fastboot, and when I tried start "recovery mode" but it would just say "boot up failed".
I searched for threads and people who had issue like mine and in fact, I found someone who described exactly the same problem I had, user named @ravibhat here: https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
While he didn't say he was able to fully flash his smartphone and get it back working, he said he was able to recover all his user data. I was really trying to follow his steps to at least, recover all user data, BUT, before that, my Moto G got hard bricked.
As I have another Moto G XT 1033, the exact same model as this one, but with a working battery, I thought it would be plausible to replace the battery so I could have more safety when fixing the phone, but it didn't work as that. Instead, after I disconnect and reconnect the battery, the Moto G is now hard bricked, as it doesn't boot up anymore, not even holding power + volume buttons, holding for 60s or 120s, none, nada. Rarely, the LED light blink once, nothing more. I connected to PC and it recognized as "qhsusb_bulk", after disconnecting and connecting the phone back to Windows 7, it automatically tried to install drivers and now it would just show "Qualcomm HS-USB QDLoader...." in device manager .​
Now I have two issues, first, make it come back to state where I could open fastboot. Second, try to dump/save all user data, to then make a total flash/factory reset to see if I can get it working again.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) and this (https://forum.xda-developers.com/moto-g/general/guidy-to-unbrick-hard-bricked-moto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
I don't want to just go and try a bunch of (possible danger) commands and guides without having some experienced people giving advices on how to perform actions, or even if it's possible to "make some backup" of current situation, "copying whole partition", etc, before installing and flashing anything.
Device INFO:
Android version was 4.4. No Root. Bootloader is LOCKED. No customizations.
ADB Debugging state is unknown, probably it was just the default value.
What I want:
I want to get a copy of all my internal storage data, eg: WhatsApp folder, etc. Better if I could get whole storage image and just flash OS and boot loader to get back as it was...
Trying to flash it in any way that causes data loss would be my last option, but @ravibhat who had same issue few years ago couldn't even get it back working again.
What @ravibhat found out:
He thought bootloader UNLOCK would wipe all internal memory user data, but he did it and still could get all files using TWRP 2.8.x.x.
"To root the phone, I’ll have to UNLOCK the Bootloader."
"ADB can be used to backup using PUSH, PULL (may or may not require Android USB Debugging enabled)": he couldn't get it to work using adb push/pull.
Please, I would really appreciate any help from anybody, also from following users @ravibhat , @lost101 , @Teddy Lo , @Kamin4ri , @oversleeper , @jdawc7 , @sd_shadow , @SahilTech , @liveroy , @bouba148 , @bejunk , @Wolfcity, @skad00sh, @FabioSan.

After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/mot...oto-g-t2833798) and this (https://forum.xda-developers.com/mot...oto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
Click to expand...
Click to collapse
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.

oversleeper said:
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
Click to expand...
Click to collapse
Thanks @oversleeper, I was a bit afraid because of the "blank-flash.bat" name.. but as I don't know of any other method of beginning this recovery other than unbricking using this qboot bat script, I will end up giving it a chance.
As I said before, Windows 7 auto installed the "Qualcomm HS-USB QLoader 9008" driver as soon as it recognized the "qhsusb_bulk". Do you think I should try to uninstall it and start from step 1 on this guide (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) installing the "Riff BOX JTAG drivers + Driver Signature Enforcement Overrider"?

Yes, I suggest that you install the driver's as advised in that old thread. Also, you will need to use the right qboot utility, for the right model and version of the bootloader that you have or it won't work. Unfortunately I can't help with that, you will need to search the internet and may luck be with you.

Flicking Lock Screen after update to latest Android 11 OTA update

I just saw an update notification that Android 11 had been released. Since my phone was running Android 10, I proceeded the update without hesitation (and without backup). The phone is running stock rom without root (I guess I did unlock the bootloader but couldn't confirm since this new rom version cannot boot into fastboot mode). After update, the lock screen keeps flicking and I cannot unlock the phone. I tried booting into safe mode but got the same flicking lock screen.
The rollback pack has flagged 'ota-downgrade=yes' so data will always be wiped.
Code:
... "ota-downgrade=yes" will be set in the package metadata file. A data wipe will always be enforced when using this flag...
I guess my last hope is that
Option 1) Wish I really did unlock the boot loader and some gurus found a way to boot into fastboot mode and flash the customer recovery/android 10 so I can pull my photos/videos by adb.
Option 2) Tried booting into recovery but no new OTA update available. Wait for new OTA update
Option 3) Some found a way to
a) boot into EDL/Download mode and
b) flash TWRP/Android 10 using QPST/QFIL (Not possible currently since Qualcomm QPST/QFIL tools did not work and official realme flash (MSMDownloadTool) ALWAYS wipe your data!)
Option 4) Someone got the private key so we can sign our customized-made update_pack and copy photos/videos to OTG USB Drive under Recovery.
Option 5) Someone share a rollback pack with 'override_timestamp=yes' instead of "ota-downgrade=yes" so data will NOT be wiped
Any comments are welcome
Spoiler: Button Combos for Booting into Other Mode
Vol Up + Power (hold for 10s)= Force Shut Down
Vol Down + USB Charging = Recovery
Vol Down when booting = Safe mode
depth testing.apk = Fast Boot (https://c.realme.com/in/post-details/1244859266402091008)
? = EDL/Download Mode
Latest Official Roms
软件升级
软件升级
www.realme.com
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1340_all_2QCxQYdkxpql.ozip
Bootloader Unlock Guide
realme Community
Welcome to realme Community, your virtual playground to learn the latest tech news, win exclusive prizes, or simply chat about realme!
c.realme.com
Spoiler: OTA Update Pack
https://download.c.realme.com/osupdate/RMX1931_11_OTA_0150_all_oDfL8HoMZ5HW.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1220_all_Dx2plLOdGTD4.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1280_all_4zs7Gcdyxm3V.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1250_all_H8peW44p7GS0.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1300_all_QzFVhQQieINQ.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1330_all_sgVacScUYMkf.ozip
https://download.c.realme.com/osupdate/RMX1931_11_OTA_1340_all_2QCxQYdkxpql.ozip
Spoiler: OTA Rollback Pack
RMX1931_11_OTA_0170_all_VEio9eM857gn.ozip
RMX1931_11_OTA_1330_all_19781_downgrade.ozip

Did you have any luck getting your phone back to normal?

aiben16 said:
Did you have any luck getting your phone back to normal?
Click to expand...
Click to collapse
No.
I want my data back and waiting for next update seems to be the only hope. Reported to realme but get no response.
If you have similar issue and don't care your data, you can do factory reset.

Am on the same boat here, Bluetooth devices still get automatically connected, USB works (mouse and keyboard) but still haven't found a way past the flicking login screen.
Happened overnight and last backup was quite a few months ago, definitively need to get the data back.
- Edit: Booting to safe-mode doesn't help either.
- Edit2: Can't attempt any update because the device is not accepting my lockscreen password either.

Mywk said:
Am on the same boat here, Bluetooth devices still get automatically connected, USB works (mouse and keyboard) but still haven't found a way past the flicking login screen.
Happened overnight and last backup was quite a few months ago, definitively need to get the data back.
- Edit: Booting to safe-mode doesn't help either.
- Edit2: Can't attempt any update because the device is not accepting my lockscreen password either.
Click to expand...
Click to collapse
If you disabled or uninstalled the coloros calendar package via ADB, enable or reinstall it again via ADB, the new System UI in the Android 11 update relies on it

This really sucks.
Any solution yet? Would be happy if I could just get access to my photos...
BTW for future reference, I'm on a Realme X Lite. I actually was positively surprised with this phone (up and running perfectly for over 2 years), but this policy is quite shocking...

Phil_123 said:
If you disabled or uninstalled the coloros calendar package via ADB, enable or reinstall it again via ADB, the new System UI in the Android 11 update relies on it
Click to expand...
Click to collapse
Just wonder if there is any way to sideload apk via adb since I can't even go to the home screen and accept adb connection.

Almost one year passed but no progress. No firmware update either.

damonxd said:
Just wonder if there is any way to sideload apk via adb since I can't even go to the home screen and accept adb connection.
Click to expand...
Click to collapse
I forgot what I exactly did to get out of the situation. From what I very vaguely remember, it might have involved tapping where the Allow button would be very quickly before the whole UI crashes. Then, depending on whether you disabled or uninstalled the weather package, you either enable or "install-existing" the package name.
How to install / get back uninstalled Apps (APKs) with ADB.
A lot of people searched for a way to uninstall bloat or APKs using ADB because a lot of OEMs don't allow uninstalling many of preinstalled apps. Tested on Pie and Oreo. BUT most of the articles if not all of them ( couldn't find any article...
forum.xda-developers.com

Phil_123 said:
I forgot what I exactly did to get out of the situation. From what I very vaguely remember, it might have involved tapping where the Allow button would be very quickly before the whole UI crashes. Then, depending on whether you disabled or uninstalled the weather package, you either enable or "install-existing" the package name.
How to install / get back uninstalled Apps (APKs) with ADB.
A lot of people searched for a way to uninstall bloat or APKs using ADB because a lot of OEMs don't allow uninstalling many of preinstalled apps. Tested on Pie and Oreo. BUT most of the articles if not all of them ( couldn't find any article...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the tips. It seems my situation is a bit difference. I can't even see the unlock pattern screen to let me unlock the phone before I can tap "allow" for USB connection and entering ADB commands. Maybe yours have the screen lock disabled before updating.

Question Phone bricked, stuck in fastboot mode

Hi.
Updated my Pixel5a to latest android 13.
After unlocking bootloader and rooting the the phone with magisk the phone worked ok for a few days.
When suddenly after reboot it got to fastboot mode with failed to load/verify boot images error.
Tried to flash new image but every command I try now I get the "FAILED (remote: 'error getting device locked state Not Ready')" error
To make things worse i cannot switch the phone to recovery or rescue mode it always reboots to fastboot.
{
"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"
}
Please help

Nobody encountered something similar?
First time since for me since I use smartphones(10+ years), a phone gets bricked so easily without a chance to revive it.

Here is your answer brother

Sorry I missed this.
Unfortunately, it looks like your bootloader is corrupted or malfunctioning, and the only way to fix this is by replacing the mainboard. There are special software tools that can perform a low level reflash, but they are not publicly available.

I have the same issue. After a broken screen replacement, my 5a would often freeze and turn off when these two conditions were met: Not connected to power + screen turned on.
I'm not 100% sure if it was connected to the screen replacement, given the problems only started occurring ~2 weeks later.
The phone would only turn on again when connected to power, even when the battery was already at 100%.
Unfortunately, I thought it was a software issue and didn't get it fixed immediately, so after one of the crashes I was greeted by the fastboot screen from the original poster above. Mine looks exactly the same (except for serial numbers etc.).
Current status:
Locked, unrooted, vanilla Android 13. Assume it's the January OTA, but could be December.
Recovery/Rescue modes don't work, I can only get into Fastboot. Selecting recovery will reboot into Fastboot.
Questions:
Is there a way to restore Android and how? Would it require a mainboard replacement like @V0latyle suggested?
Is the user data on the phone lost, or could it be saved in the process (no recent backups)?
What's the best way to back up an unrooted+locked+vanilla Pixel phone (without Google Cloud backup, given that's not E2E encrypted, afaik)?
Thank you!

niscy said:
I have the same issue. After a broken screen replacement, my 5a would often freeze and turn off when these two conditions were met: Not connected to power + screen turned on.
I'm not 100% sure if it was connected to the screen replacement, given the problems only started occurring ~2 weeks later.
The phone would only turn on again when connected to power, even when the battery was already at 100%.
Unfortunately, I thought it was a software issue and didn't get it fixed immediately, so after one of the crashes I was greeted by the fastboot screen from the original poster above. Mine looks exactly the same (except for serial numbers etc.).
Current status:
Locked, unrooted, vanilla Android 13. Assume it's the January OTA, but could be December.
Recovery/Rescue modes don't work, I can only get into Fastboot. Selecting recovery will reboot into Fastboot.
Questions:
Is there a way to restore Android and how? Would it require a mainboard replacement like @V0latyle suggested?
Is the user data on the phone lost, or could it be saved in the process (no recent backups)?
What's the best way to back up an unrooted+locked+vanilla Pixel phone (without Google Cloud backup, given that's not E2E encrypted, afaik)?
Thank you!
Click to expand...
Click to collapse
1. If I was current when the OP happened, I would've suggested powering on with the button combo to try and get into recovery -- Hold the Power and Volume Down; make sure to try and hold it down for as long as more than a minute. If that doesn't work, I might try Android Flash Tool as Noexcusses once suggested, but that usually requires an unlocked bootloader. Still...since it's officially from Google (the phone's maker), it might have some special "magic" that it can pull of, but don't get your hopes up on that...
3. The currently accepted best method is the Swift Backup app, My Backup Pro is an old and good staple, but without root, there's not much it will be able to save. I believe Swift (can) locks it to your Google account and/or you can password protect the backups, but I'm not totally sure if they encrypt it as well as locking it in such manner; I don't believe My Backup Pro does anything like this. There's always adb commands that might be able to save a little bit more, but again, not by much without root access. And I don't think any unrooted backup method bothers to back up the non-system internal storage.
Sorry for your troubles and hopefully you get it all back up and running! And not to be to "scoldy", but it's always a good idea to back things up (I usually do when I manually update the firmware & security updates each month); I know it's a bit harder to remember when it's an update OTA because it's a lot less involved, but it can be a good trigger to remind to...

simplepinoi177 said:
And not to be to "scoldy", but it's always a good idea to back things up
Click to expand...
Click to collapse
I agree... I had it on my todo list forever, but I just couldn't find a good way to back it up without root. And I didn't want root, because in the past that has prevented certain apps from working (e.g., some banking apps would see it as a security issue and refuse to start) and it has created trouble with OTAs.
Will look into this "Swift" app then. It's a shame, this is so trivial with iPhones (fully encrypted iTunes backups).
simplepinoi177 said:
Hold the Power and Volume Down
Click to expand...
Click to collapse
That combo takes me to Fastboot, but when I select "Recovery" from there, the phone just reboots into Fastboot again with the same errors. I can see the phone in "fastboot devices", though.
simplepinoi177 said:
Android Flash Tool as Noexcusses once suggested
Click to expand...
Click to collapse
Android Flash Tool = the thing that you run in the browser, by clicking the "Flash" link on the Google website? Is that better than adb/fastboot?
Also, do you mean for side-loading the OTA (see https://developers.google.com/android/ota)? I thought that required access to recovery?
Or are you talking about flashing the factory image (https://developers.google.com/android/images#barbet)? I haven't tried that, yet, but I assumed it would wipe my user data?
EDIT: I see the device in the Android Flash Tool, says "connected". It's in Fastboot mode and showing OP's screen. Let's see what I can do from here.
EDIT2: OUCH.

niscy said:
I have the same issue. After a broken screen replacement, my 5a would often freeze and turn off when these two conditions were met: Not connected to power + screen turned on.
I'm not 100% sure if it was connected to the screen replacement, given the problems only started occurring ~2 weeks later.
The phone would only turn on again when connected to power, even when the battery was already at 100%.
Unfortunately, I thought it was a software issue and didn't get it fixed immediately, so after one of the crashes I was greeted by the fastboot screen from the original poster above. Mine looks exactly the same (except for serial numbers etc.).
Current status:
Locked, unrooted, vanilla Android 13. Assume it's the January OTA, but could be December.
Recovery/Rescue modes don't work, I can only get into Fastboot. Selecting recovery will reboot into Fastboot.
Questions:
Is there a way to restore Android and how? Would it require a mainboard replacement like @V0latyle suggested?
Click to expand...
Click to collapse
With a locked bootloader, the only thing you can try to do is sideload an OTA, but if you can't get into recovery mode, I'm not sure there's anything you can do - a locked bootloader will reject commands such as boot, which would be useful in this case to live boot a good image...but if the bootloader was unlocked, you'd just be able to reflash /boot anyway
niscy said:
Is the user data on the phone lost, or could it be saved in the process (no recent backups)?
Click to expand...
Click to collapse
Unfortunately I believe nothing can be done to save it or back it up. If you could get into recovery and sideload an OTA, user data would be preserved, but since you can't get into recovery, that point is moot, because it looks like your only option to get the device working again is to have it repaired, which would most likely involve mainboard replacement and complete loss of all user data (except what was already backed up into the Google cloud)
niscy said:
What's the best way to back up an unrooted+locked+vanilla Pixel phone (without Google Cloud backup, given that's not E2E encrypted, afaik)?
Click to expand...
Click to collapse
There is none. Google cloud backup is the best way, but even this can't back up app data, and there is no way to back up app data without root, because of Scoped Storage - no app can access any other app's "private" data without root permissions.
simplepinoi177 said:
1. If I was current when the OP happened, I would've suggested powering on with the button combo to try and get into recovery -- Hold the Power and Volume Down; make sure to try and hold it down for as long as more than a minute. If that doesn't work, I might try Android Flash Tool as Noexcusses once suggested, but that usually requires an unlocked bootloader. Still...since it's officially from Google (the phone's maker), it might have some special "magic" that it can pull of, but don't get your hopes up on that...
Click to expand...
Click to collapse
Actually the only thing that is required is that OEM Unlocking be enabled in developer options. If it is not, the Flash Tool won't work.
simplepinoi177 said:
3. The currently accepted best method is the Swift Backup app, My Backup Pro is an old and good staple, but without root, there's not much it will be able to save. I believe Swift (can) locks it to your Google account and/or you can password protect the backups, but I'm not totally sure if they encrypt it as well as locking it in such manner; I don't believe My Backup Pro does anything like this. There's always adb commands that might be able to save a little bit more, but again, not by much without root access. And I don't think any unrooted backup method bothers to back up the non-system internal storage.
Click to expand...
Click to collapse
Again, due to scoped storage, root permissions would be required to access any other app's private data to effect a "full" backup.
niscy said:
Will look into this "Swift" app then. It's a shame, this is so trivial with iPhones (fully encrypted iTunes backups).
Click to expand...
Click to collapse
If you can boot into system, you'd be better off using Google Cloud Storage because at least that would back up device settings. Swift Backup won't do this, and is otherwise only able to access "generic" data - phone logs, texts, external storage, etc.
niscy said:
That combo takes me to Fastboot, but when I select "Recovery" from there, the phone just reboots into Fastboot again with the same errors. I can see the phone in "fastboot devices", though.
Click to expand...
Click to collapse
I think you're toast, bud.
niscy said:
Android Flash Tool = the thing that you run in the browser, by clicking the "Flash" link on the Google website? Is that better than adb/fastboot?
Click to expand...
Click to collapse
No, it's just a GUI alternative that only flashes official images. As I mentioned above this only works if OEM unlocking is enabled, or the bootloader is unlocked. A locked bootloader rejects commands like flash, boot, and update, so the flash tool unlocks the bootloader first (if not already unlocked) before proceeding with the flash.
niscy said:
Also, do you mean for side-loading the OTA (see https://developers.google.com/android/ota)? I thought that required access to recovery?
Click to expand...
Click to collapse
Yes, it does.
niscy said:
Or are you talking about flashing the factory image (https://developers.google.com/android/images#barbet)? I haven't tried that, yet, but I assumed it would wipe my user data?
Click to expand...
Click to collapse
You can only do this with an unlocked bootloader. Even though it's the factory image, as I mentioned a couple times already, the commands necessary to flash the image are rejected by a locked bootloader.
As for wiping data, this only happens if you use the included script without editing out the -w. Some people with unlocked bootloaders prefer to update using the script, they just change it so it doesn't wipe data. I personally prefer updating using the factory image but I do everything manually through fastboot and ADB because I'm stubbornly old fashioned.

niscy said:
I agree... I had it on my todo list forever, but I just couldn't find a good way to back it up without root. And I didn't want root, because in the past that has prevented certain apps from working (e.g., some banking apps would see it as a security issue and refuse to start) and it has created trouble with OTAs.
Click to expand...
Click to collapse
Just so you know, there are ways & methods to keep apps from detecting root; I would say (as far as Pixel 2XL, Pixel 5, and Pixel 7's are concerned) about 95% of apps could be made to hide root from; I get Wallet, 3 banking apps, Netflix, Xfinity apps, & certain games which all shouldn't work with a rooted device to work. And, usually, if for some reason hidden detection stops working, it usually is worked on and works again within a short amount of time.
niscy said:
Android Flash Tool = the thing that you run in the browser, by clicking the "Flash" link on the Google website? Is that better than adb/fastboot?
Click to expand...
Click to collapse
Surprisingly, it is a thing you run from the browser...! It surprised the heck out of me too! I would've thought it was a tool you actually download and run... Be aware you most likely need like 3-4GB+ free on your system (usually C drive...
niscy said:
Also, do you mean for side-loading the OTA (see https://developers.google.com/android/ota)? I thought that required access to recovery?
Or are you talking about flashing the factory image (https://developers.google.com/android/images#barbet)? I haven't tried that, yet, but I assumed it would wipe my user data?
Click to expand...
Click to collapse
I am talking about neither of those as they require you to have access to recovery mode and/or require an unlocked bootloader...
niscy said:
EDIT: I see the device in the Android Flash Tool, says "connected". It's in Fastboot mode and showing OP's screen. Let's see what I can do from here.
EDIT2: OUCH.
View attachment 5813733
Click to expand...
Click to collapse
Hey! At least that's something! And hopefully, at least it's not a total loss...could be worse; you might've/could've had to wait while a repair shop completely replaced the motherboard.
If you end up having to wipe the device to recover, consider the worst case scenario where they replace the motherboard...it would mean a wiped device anyway....

Okay guys, thank you for the help so far @V0latyle @simplepinoi177
This is where I'm now:
It only gives me the "wipe" warning when I select the "Lock Bootloader" box, otherwise it directly proceeds to download the image without giving the warning.
How come I'm getting this far while I'm in Fastboot? Am I on the right path?

The image download failed a few times due to supposedly insufficient disk space (a lie). Turns out the problem was Incognito mode, seems that has restrictions that break the flash tool.
But now I'm getting the below instead after the image downloaded. Does that mean that the tool won't work, because my device is locked?
Flash Failed
Fastboot command (flash:bootloader_b) failed: 'error getting device locked state Not Ready'

niscy said:
Okay guys, thank you for the help so far @V0latyle @simplepinoi177
This is where I'm now:
View attachment 5813743
It only gives me the "wipe" warning when I select the "Lock Bootloader" box, otherwise it directly proceeds to download the image without giving the warning.
How come I'm getting this far while I'm in Fastboot? Am I on the right path?
Click to expand...
Click to collapse
See if you can get away with not checking "wipe device" or "lock[ing] bootloader"...
It automatically downloads the factory image -- that's why I said you have to have 3-4GB free on your hard drive...
You get that far because the AFT works in fastboot, and you luckily are still able to see fastboot in your device manager & be in fastboot mode...
I'd say you are on the right path....at least a lot more hopeful than replacing your mobo. But if all doesn't work, you may be required to wipe the device and/or lock the bootloader as well...

Seems the next thing I would have to try is re-running the Flash Tool with the "Wipe device" and "Lock bootloader" boxes checked?
Just to confirm, would the motherboard replacement require a user data wipe? If yes, then I guess I have nothing to lose at this point.

niscy said:
The image download failed a few times due to supposedly insufficient disk space (a lie). Turns out the problem was Incognito mode, seems that has restrictions that break the flash tool.
But now I'm getting the below instead after the image downloaded. Does that mean that the tool won't work, because my device is locked?
Flash Failed
Fastboot command (flash:bootloader_b) failed: 'error getting device locked state Not Ready'
View attachment 5813745
Click to expand...
Click to collapse
Yes, unfortunately this is bad news...
Most likely, I imagine and maybe @V0latyle can concur and/or elaborate, but it is most likely due to you not having OEM unlock ticked in the Developer Mode and an unlocked bootloader -- I stated before, but wasn't exactly sure as I've never tried it not on an unlocked bootloader, but that tool most likely doesn't work without having an unlocked bootloader (& thus also having OEM unlocked ticked as well)...I was just holding out hope that, since it was an official Google tool, it might've been able to do something for you (especially considering you could still see it as a fastboot device in your device manager)....
niscy said:
Seems the next thing I would have to try is re-running the Flash Tool with the "Wipe device" and "Lock bootloader" boxes checked?
Just to confirm, would the motherboard replacement require a user data wipe? If yes, then I guess I have nothing to lose at this point.
Click to expand...
Click to collapse
Yes, motherboard replacement requires a user data wipe. I'm unsure if the technician either does this just as policy/practice, or if after installing the new mobo, the Android OS requires it...but I imagine it is the latter...
It might be worth a try to check those boxes, but most likely will not work. Your bootloader is already locked, so "lock[ing] bootloader" is kinda redundant and wouldn't be necessary for it to work...

Okay guys, I think I'm officially ****ed. No matter what boxes I check, I get the error mentioned above ("Fastboot command (flash:bootloader_b) failed: 'error getting device locked state Not Ready'").
But even worse, I checked with some repair shop and they told me they won't even do motherboard replacements for out-of-warranty devices (because thieves would often use this service to "refurbish" stolen phones).
So I can't even get the motherboard replaced, unless I do it myself? **** my life.

niscy said:
Okay guys, I think I'm officially ****ed. No matter what boxes I check, I get the error mentioned above ("Fastboot command (flash:bootloader_b) failed: 'error getting device locked state Not Ready'").
But even worse, I checked with some repair shop and they told me they won't even do motherboard replacements for out-of-warranty devices (because thieves would often use this service to "refurbish" stolen phones).
So I can't even get the motherboard replaced, unless I do it myself? **** my life.
Click to expand...
Click to collapse
Sorry to hear that it didn't work out...was a long shot...
Is there a uBreakiFix anywhere near you (they are the official repair company for Google)? If not, would it be possible to ship them the unit? Talk to Google versus talking to "some repair shop" (unless that repair shop you talked to was uBreakiFix, then that might be the policy; but I doubt it. Doesn't sound reasonable. I might try another store; even if you have to ship it to a distant one)...
Or course this all means you will have to spend $$$ to get it repaired, so be prepared for that...

niscy said:
Seems the next thing I would have to try is re-running the Flash Tool with the "Wipe device" and "Lock bootloader" boxes checked?
Click to expand...
Click to collapse
That would have no effect on whether the tool works
niscy said:
Just to confirm, would the motherboard replacement require a user data wipe? If yes, then I guess I have nothing to lose at this point.
Click to expand...
Click to collapse
All the storage lives in the flash devices, which live on the mainboard. A new mainboard would be preloaded with firmware, and would have to be programmed with your IMEI, but it would be like getting a brand new phone - no user data whatsoever.
simplepinoi177 said:
Yes, unfortunately this is bad news...
Click to expand...
Click to collapse
Well, hold on. We've got a lot of people all responding at once. @niscy if you could, hold off for a bit until we can get to the bottom of what your device state is and what you can and can't do.
simplepinoi177 said:
Most likely, I imagine and maybe @V0latyle can concur and/or elaborate, but it is most likely due to you not having OEM unlock ticked in the Developer Mode and an unlocked bootloader
Click to expand...
Click to collapse
Yes, one of these is required to use the Android Flash Tool (although if the bootloader is unlocked, OEM Unlocking is default "on"
simplepinoi177 said:
-- I stated before, but wasn't exactly sure as I've never tried it not on an unlocked bootloader, but that tool most likely doesn't work without having an unlocked bootloader (& thus also having OEM unlocked ticked as well)...
Click to expand...
Click to collapse
The bootloader doesn't have to start unlocked; as long as OEM Unlocking is enabled, the Flash Tool will automatically unlock the bootloader and perform the flash. I'm pretty sure this results in a data wipe.
simplepinoi177 said:
I was just holding out hope that, since it was an official Google tool, it might've been able to do something for you (especially considering you could still see it as a fastboot device in your device manager)....
Click to expand...
Click to collapse
Negative, the Flash Tool is simply a GUI interface for ADB Platform Tools and uses the same commands. Since, as I have explained multiple times, a locked bootloader rejects several commands required to flash the device, OEM Unlocking would have to be enabled at the very least to use the tool, which would then unlock the bootloader so that the commands will work.
The only "Google approved" way to update ALL devices regardless of OEM lock or bootloader lock is via OTA, because either update_engine in Android system, or the recovery kernel, is able to verify the update package. The bootloader is not capable of verifying packages applied externally; it can only compare certain partitions (such as /boot) against reference hashes (vbmeta images), which is why it's designed to reject all flashing and booting commands while locked
To be able to perform a complete factory reflash on a locked bootloader, the bootloader would have to have the ability to analyze and verify the entire update package, and it simply does not have the resources to do this. Bootloader only has three jobs:
Verify boot images
Load boot images
Provide USB interface (and must be unlocked to flash anything)
simplepinoi177 said:
Yes, motherboard replacement requires a user data wipe. I'm unsure if the technician either does this just as policy/practice, or if after installing the new mobo, the Android OS requires it...but I imagine it is the latter...
It might be worth a try to check those boxes, but most likely will not work. Your bootloader is already locked, so "lock[ing] bootloader" is kinda redundant and wouldn't be necessary for it to work...
Click to expand...
Click to collapse
As I explained, it's because you'd essentially be getting a brand new phone that has never had user data on it. Wiping data on the old mainboard is unnecessary, but most repair centers don't have a way to transfer user data.
@niscy Before you go any further, let's establish where exactly "Square One" is. Please answer these questions:
Are you able to boot into Android system? Is recovery the only thing not working?
What have you tried to get into recovery mode?
When you attempt to boot into recovery, do you see an error message at the bottom of the bootloader screen?
Do you have any particular issue with backing up your data to Google Cloud if that option is possible?

V0latyle said:
1) Are you able to boot into Android system? Is recovery the only thing not working?
2) What have you tried to get into recovery mode?
3) When you attempt to boot into recovery, do you see an error message at the bottom of the bootloader screen?
4) Do you have any particular issue with backing up your data to Google Cloud if that option is possible?
Click to expand...
Click to collapse
1) Can't get into Android system, just Fastboot.
2) Select recovery from Fastboot mode with the volume keys. I also tried "fastboot reboot recovery" (doesn't seem to work on the 5a). It doesn't make a difference how I get into fastboot (just turning it on vs. voldown + power key combo).
3) Screen just goes black and stays black for 30-60 seconds or so. Then it goes back to the fastboot screen.
4) While setting it up, the explanations in Android suggested that it was not fully end-to-end encrypted. However, I found some articles online that say the opposite. So maybe I just got confused by ambiguous language.
EDIT: flashing without the Android Flash Tool fails too, obviously...
barbet-tq1a.230105.001 % ./flash-all.sh
Sending 'bootloader_b' (8762 KB) OKAY [ 0.350s]
Writing 'bootloader_b' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.080s]
Finished. Total time: 0.080s
EDIT2: Seems there's enough E2E encryption in Google backups ... see https://blog.elcomsoft.com/2021/01/...n-apple-icloud-google-and-microsoft-accounts/

V0latyle said:
As I explained, it's because you'd essentially be getting a brand new phone that has never had user data on it. Wiping data on the old mainboard is unnecessary, but most repair centers don't have a way to transfer user data.
Click to expand...
Click to collapse
Interesting...I am aware that, for computers, replacing the motherboard doesn't necessarily touch data because that's usually stored on the hard drive. I figure the internal storage on a smartphone might be set up similarly and have it separated in something the same way (i.e. I imagine it's something similar to a microsd internal circuitry), and thus might not be touched simply by replacing the mobo. I wasn't insinuating that the repair centers would wipe old data that they were going to toss anyway; thought it was separate from the mobo and could possibly survive the exchange.
Thanks for clarifying! Also, I posted this here instead of PMing it because it is somewhat useful information that might help someone else understand things better (like me)...but I do apologize for the off-topic...

I just went back and read your first post. Failure to load/verify boot images means there's a dm-verity issue - as I mentioned previously, the bootloader verifies the integrity of the boot image as it's loaded; this prevents things like persistent rootkits. In this case, it's coming up against an error - the hash of the boot image does not match the verification hash in /vbmeta, probably because it somehow got corrupted during the update. With an unlocked bootloader this would be a fairly simple fix - just reflash /boot - but with a locked bootloader, this is pretty much impossible to fix.
niscy said:
1) Can't get into Android system, just Fastboot.
Click to expand...
Click to collapse
Yeah, because as described above, the boot image is corrupted, and unfortunately, the boot image also contains recovery.
niscy said:
2) Select recovery from Fastboot mode with the volume keys. I also tried "fastboot reboot recovery" (doesn't seem to work on the 5a). It doesn't make a difference how I get into fastboot (just turning it on vs. voldown + power key combo).
3) Screen just goes black and stays black for 30-60 seconds or so. Then it goes back to the fastboot screen.
Click to expand...
Click to collapse
Not sure why the screen goes black for a while, it should just recycle back to the bootloader screen immediately
niscy said:
4) While setting it up, the explanations in Android suggested that it was not fully end-to-end encrypted. However, I found some articles online that say the opposite. So maybe I just got confused by ambiguous language.
Click to expand...
Click to collapse
Yeah. I won't be one of those people who advocates for using a product you don't believe in, but you also have to consider benefit vs risk - in this case, you really don't want to use your data, but you didn't implement an alternative for backups.
niscy said:
EDIT: flashing without the Android Flash Tool fails too, obviously...
barbet-tq1a.230105.001 % ./flash-all.sh
Sending 'bootloader_b' (8762 KB) OKAY [ 0.350s]
Writing 'bootloader_b' FAILED (remote: 'error getting device locked state Not Ready')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.080s]
Finished. Total time: 0.080s
EDIT2: Seems there's enough E2E encryption in Google backups ... see https://blog.elcomsoft.com/2021/01/...n-apple-icloud-google-and-microsoft-accounts/
Click to expand...
Click to collapse
Yeah. At this point, I think you're pretty much limited to two options:
Pay for a repair (expensive)
Buy a new device (even more expensive)
I'm sorry there's no better answer. If OEMs like Google (or in this case, Foxconn as the manufacturer) made a point of providing low level flash tools and training to repair stations, then it might be possible to reflash the boot image. But, they don't do this for a litany of reasons, ranging from "it's cheaper to replace than to fix" to "tools like this could be used for major exploits in the wrong hands".
simplepinoi177 said:
Interesting...I am aware that, for computers, replacing the motherboard doesn't necessarily touch data because that's usually stored on the hard drive. I figure the internal storage on a smartphone might be set up similarly and have it separated in something the same way (i.e. I imagine it's something similar to a microsd internal circuitry), and thus might not be touched simply by replacing the mobo. I wasn't insinuating that the repair centers would wipe old data that they were going to toss anyway; thought it was separate from the mobo and could possibly survive the exchange.
Thanks for clarifying! Also, I posted this here instead of PMing it because it is somewhat useful information that might help someone else understand things better (like me)...but I do apologize for the off-topic...
Click to expand...
Click to collapse
Yeah, mobile mainboards are generally "all in one", with the SoC, modem, and storage all located on the same board. There are sometimes small daughterboards for things like camera modules and microSD/SIM card slots but for the most part everything is on the same board. All flashable storage is located on the same memory devices - this includes the most basic things such as the bootloader itself and the baseband image, as well as the system partitions, and of course the "userspace" data. Imagine if your hard drive was built into your motherboard, and also hosted your BIOS/UEFI.
There is only one more thing I can advise trying, and it will most likely not work: Try to switch back to the A slot. You can do this through fastboot: fastboot --set-active=a
Again, this is not likely to work because I believe the bootloader will reject this command as well.
An interesting note that isn't of much help right now: The whole point of A/B slots (and seamless system updates) is not just being able to update "on the fly" without booting into recovery and waiting 5-10 minutes for an update to finish, but also a "fail safe" so that if an update fails for whatever reason, the system should recycle back to the last working configuration.
Spoiler: It works like this:
Let's assume for the sake of argument you're on slot A, running the January update.
When the February update becomes available, update_engine downloads the update package, extracts it, and writes it to the inactive slot - in this case, slot B.
The bootloader is then commanded to boot slot B on the next reboot
When user reboots device, bootloader marks slot B as active and attempts to boot from that slot. There are a couple of markers here - a slot can be marked active, bootable, and successful.
Once boot proceeds past a certain point, the slot is now marked bootable. Once loaded into Android system, the boot is marked successful.
If for any reason slot B fails to boot, or crashes at a certain point, the device should automatically reboot back to slot A, and upon successful boot of Android, notify the user that the update failed.
I don't know why it failed to do that in this case. Apparently it thought slot B was both bootable and successful, and the failure didn't occur early enough to recycle back to slot A.