Hi!
I have a Moto X 2013 from Verizon. I am planning on sending it in for a replacement via Motorola. Since they give you a brand new phone, you lose all your data from it.
I have tried for ages trying to find ways on the internet.
Before I do this, I want to know for 100% fact that there is no way to backup my phone.
Key "fact thingies"
-Cannot enable ADB Debugging (There is a password on my phone)
-CAN ACCESS FASTBOOT (Verified by checking fastboot terminal)
-Buttons work fine.
Any help will be highly appreciated, and, if you can help me get my data backed up, I will reward you with the Steam game of your choice (Up to $15)
HardBoiledGregg said:
Hi!
I have a Moto X 2013 from Verizon. I am planning on sending it in for a replacement via Motorola. Since they give you a brand new phone, you lose all your data from it.
I have tried for ages trying to find ways on the internet.
Before I do this, I want to know for 100% fact that there is no way to backup my phone.
Key "fact thingies"
-Cannot enable ADB Debugging (There is a password on my phone)
-CAN ACCESS FASTBOOT (Verified by checking fastboot terminal)
-Buttons work fine.
Any help will be highly appreciated, and, if you can help me get my data backed up, I will reward you with the Steam game of your choice (Up to $15)
Click to expand...
Click to collapse
Give a bit more info, is your bootloader locked/unlocked.
Which data your want to backup, Photos, other files, app data?
What version of Android you run?
The password your have, is it a password, pattern, pin?
liveroy said:
Give a bit more info, is your bootloader locked/unlocked.
Which data your want to backup, Photos, other files, app data?
What version of Android you run?
The password your have, is it a password, pattern, pin?
Click to expand...
Click to collapse
Okay, here goes.
My bootloader is locked (unfortunantely), I'd like to back up user created files, so music, pictures, videos, and the folders containing them, It has 4.4.4 rooted, and the password is, well, a regular password.
HardBoiledGregg said:
Okay, here goes.
My bootloader is locked (unfortunantely), I'd like to back up user created files, so music, pictures, videos, and the folders containing them, It has 4.4.4 rooted, and the password is, well, a regular password.
Click to expand...
Click to collapse
You can give it a try with a OTG adapter and USB keyboard attached, this way you can probably unlock the device, but you`ll need some blind navigation with the keyboard after that so you can reach the settings
Today or tomorrow when I got the time I`ll play a bit with that and I`ll see if I can help you.
liveroy said:
You can give it a try with a OTG adapter and USB keyboard attached, this way you can probably unlock the device, but you`ll need some blind navigation with the keyboard after that so you can reach the settings
Today or tomorrow when I got the time I`ll play a bit with that and I`ll see if I can help you.
Click to expand...
Click to collapse
Okay, will do
HardBoiledGregg said:
Okay, will do
Click to expand...
Click to collapse
I've played a while today with a keyboard and I can do everything, except to unlock the phone, the unlock ring itself cannot be operated with keyboard. Password input is okay, so it's navigation to Developer Options and enabling USB debugging is also doable..
There is an option to plug mouse first, try to jiggle with it and unlock the ring, since this is the only of few things you can do when your have password, then connect the keyboard, input your password and proceed.
After that there will be one more obstacle, which is to authorize you pc to access debugging, but this can be done with keyboard too, since it's a pop-up.
hm, not the easiest task, since your BL is locked,you cant install CWM, otherwise you could remove the pw with the aroma file manager out of CWM: http://forum.xda-developers.com/showthread.php?t=2225695
Have you tried this?: http://trendblog.net/how-to-bypass-android-phone-lock-screen-pattern-pin-password/
And have you looked into this?: http://android.stackexchange.com/qu...ce-as-have-no-internet-connection/35848#35848
Another way would be removing the lock via cerberus, but this would require installing cerberus 1st on your phone and if your phone is locked but rooted but you cant access the phone directly or via adb then there isn't much you can do cause you have to access the phone somehow, either directly or via terminal / PC
UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.
Can we get a video of how to do this?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?
trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.
AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks
#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.
Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project
So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader
MOD EDIT:
This is the latest version
这是最新版本
#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
any luck with that? can I backup my firmware before doing it?
darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.
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.