Block box over "Bootloader Unlocked" screen. No bootloop. - G 2014 Q&A, Help & Troubleshooting

Okay, so I bought this phone a year ago, I unlocked the bootloader, rooted it, did the whole nine yards. Learned some. F2ucked my phone up. The usual. I dont know what happened. My best guess is that I installed a VERY wrong rom on my phone. I don't know what rom, and I don't know how to find out. The phone turns on. It reaches the "Bootloader Unlocked" Warning. It stops here. It does nothing else. There is a black box on the screen, it covers almost the entire "Bootloader Unlocked" warning. If I boot the phone into Flashboot, recovery takes me to a blank puke green screen (The aforementioned black box is visible here too, however it looks like Missingn0 (from pokemon)). Selecting factory reset simply reboots the phone and puts it back at the "Bootloader Unlocked" warning. What is my problem, and is there any way to fix it?

FrustratedPhoneUser said:
Okay, so I bought this phone a year ago, I unlocked the bootloader, rooted it, did the whole nine yards. Learned some. F2ucked my phone up. The usual. I dont know what happened. My best guess is that I installed a VERY wrong rom on my phone. I don't know what rom, and I don't know how to find out. The phone turns on. It reaches the "Bootloader Unlocked" Warning. It stops here. It does nothing else. There is a black box on the screen, it covers almost the entire "Bootloader Unlocked" warning. If I boot the phone into Flashboot, recovery takes me to a blank puke green screen (The aforementioned black box is visible here too, however it looks like Missingn0 (from pokemon)). Selecting factory reset simply reboots the phone and puts it back at the "Bootloader Unlocked" warning. What is my problem, and is there any way to fix it?
Click to expand...
Click to collapse
You'll probably have to restore to stock, or you could clear data, system, cache, and dalvik and flash another ROM. It would be easier to help if you knew which ROM you flashed. You should really pay attention to what ROM you flash. It's pretty important.

Ragarianok said:
You'll probably have to restore to stock, or you could clear data, system, cache, and dalvik and flash another ROM. It would be easier to help if you knew which ROM you flashed. You should really pay attention to what ROM you flash. It's pretty important.
Click to expand...
Click to collapse
try my easy installer in signature pick correct one for your phone model i.e xt106x

Ragarianok said:
You'll probably have to restore to stock, or you could clear data, system, cache, and dalvik and flash another ROM. It would be easier to help if you knew which ROM you flashed. You should really pay attention to what ROM you flash. It's pretty important.
Click to expand...
Click to collapse
reefuge said:
try my easy installer in signature pick correct one for your phone model i.e xt106x
Click to expand...
Click to collapse
This was few months ago. I may have found the name of the Rom, But I am unsure if this is the Rom that caused the problem, or another Rom that I simply had on my PC. Also, I have just encountered another problem. The battery will not charge, It won't allow me to flash anything to the phone while its at low battery.

Okay, In reference to my last reply, After opening the Bat file and allowing the CMD to open, I had to run option 3 before running option 1. This seems to have fixed hatever the problem was, both with the charging and the device not working.

FrustratedPhoneUser said:
Okay, In reference to my last reply, After opening the Bat file and allowing the CMD to open, I had to run option 3 before running option 1. This seems to have fixed hatever the problem was, both with the charging and the device not working.
Click to expand...
Click to collapse
:good:

Related

[Q] Android 4.4.2 disaster & Downgrade to 4.3

Hi Guys,
I updated my Vodafone Ireland HTC One to Android 4.4.2 OTA version (4.19.161.10) a couple of weeks ago. I have serious problems with the phone since then, it's not much of use anymore. I get the following error messages on homepage when the phone starts: "shoebox engine has stopped", "com.android.phone has stopped" , and I constantly get "google play services has stopped" error message. Worst thing is that the phone restarts itself a few times a day and when it restarts, it goes back to the state it was on the day I updated it. Anything I saved on my phone since the update gets removed (contacts, pics, sms, whatsapp messages, progress in games).
I tried a factory reset, but it doesn't work. Phone restarts to do the reset and shows me a triangle with an exclamation mark in it for a minute or so, and then just restarts normally, no reset done. HTC phone support couldn't offer any solution.
So, I would like to wipe all the data off my phone and go back to official Android 4.3. I never rooted the phone and it's still "Locked" with S-On. I'm not really interested in rooting, I just want to have the device working properly. Do I still have to relock the bootloader and turn S-Off before I flash official 4.3 version, or should I just skip those steps? HBoot version is 1.56, would it cause any problems?
Any additional feedback is welcome, appreciate your help! Thanks
I never rooted the phone and it's still "Locked" with S-On.
Click to expand...
Click to collapse
Do I still have to relock the bootloader and turn S-Off before I flash official 4.3 version, or should I just skip those steps?
Click to expand...
Click to collapse
Is the bootloader unlocked or not? my guess is you meant to say unlock?
You should be able to flash RUU without doing anything else
JPS7 said:
Hi Guys,
I updated my Vodafone Ireland HTC One to Android 4.4.2 OTA version (4.19.161.10) a couple of weeks ago. I have serious problems with the phone since then, it's not much of use anymore. I get the following error messages on homepage when the phone starts: "shoebox engine has stopped", "com.android.phone has stopped" , and I constantly get "google play services has stopped" error message. Worst thing is that the phone restarts itself a few times a day and when it restarts, it goes back to the state it was on the day I updated it. Anything I saved on my phone since the update gets removed (contacts, pics, sms, whatsapp messages, progress in games).
I tried a factory reset, but it doesn't work. Phone restarts to do the reset and shows me a triangle with an exclamation mark in it for a minute or so, and then just restarts normally, no reset done. HTC phone support couldn't offer any solution.
So, I would like to wipe all the data off my phone and go back to official Android 4.3. I never rooted the phone and it's still "Locked" with S-On. I'm not really interested in rooting, I just want to have the device working properly. Do I still have to relock the bootloader and turn S-Off before I flash official 4.3 version, or should I just skip those steps? HBoot version is 1.56, would it cause any problems?
Any additional feedback is welcome, appreciate your help! Thanks
Click to expand...
Click to collapse
I don't think you will be able to downgrade to 4.3 without s-off, You sure you don't have an app that kitkat doesn't like. Since you want to wipe all data, why not backup all apps and then uninstall everything you downloaded and installed, reset the phone gain and see what happens.
Or perhaps try a custom rom
Backup the SD card/any data you want and factory reset the phone and set up 4.4.2 again from scratch. Sometimes and OTA doesn't 'take' properly the first time from my experience
I think a factory reset would solve a lot of problems, but the phone doesn't want to do it. When I try to factory reset, it first shows Red triangle with exclamation mark and then just restarts with nothing removed. Tried both through the menu and with hardware buttons.
I read on several guides that "Fastboot" needs to be switched off before a factory reset. Maybe that's the problem. Because if I disable "Fastboot" in "Settings -> Power", the phone will not have this setting saved when it restarts. As I wrote in the original post, when the phone restarts, all of the settings and data in the phone go back to the state they were on the day I updated it to 4.4.2. My e-mails, messages, pictures, songs, app settings, even the temperature on the weather app :silly:
Bootloader is currently "Locked" and it was never unlocked before. I upgraded only OTA versions so far. Thanks for the opinions. I just don't want to do anything wrong while trying to make it better. Still don't know if I should skip s-off or not. Would it harm the phone if I just try with s-on?
JPS7 said:
I think a factory reset would solve a lot of problems, but the phone doesn't want to do it. When I try to factory reset, it first shows Red triangle with exclamation mark and then just restarts with nothing removed. Tried both through the menu and with hardware buttons.
I read on several guides that "Fastboot" needs to be switched off before a factory reset. Maybe that's the problem. Because if I disable "Fastboot" in "Settings -> Power", the phone will not have this setting saved when it restarts. As I wrote in the original post, when the phone restarts, all of the settings and data in the phone go back to the state they were on the day I updated it to 4.4.2. My e-mails, messages, pictures, songs, app settings, even the temperature on the weather app :silly:
Bootloader is currently "Locked" and it was never unlocked before. I upgraded only OTA versions so far. Thanks for the opinions. I just don't want to do anything wrong while trying to make it better. Still don't know if I should skip s-off or not. Would it harm the phone if I just try with s-on?
Click to expand...
Click to collapse
Wow!!!! UNLOCK BOOTLOADER!!!!!!! Install twrp. In recovery wipe data only that's a factory reset. If you read the s-off threads fully you will have no problems,so go forth and profit. The fastboot setting in power settings is for a quick power on only. It has nothing to do with anything else.
[email protected] said:
Wow!!!! UNLOCK BOOTLOADER!!!!!!! Install twrp. In recovery wipe data only that's a factory reset. If you read the s-off threads fully you will have no problems,so go forth and profit. The fastboot setting in power settings is for a quick power on only. It has nothing to do with anything else.
Click to expand...
Click to collapse
It's a pain. I can't even unlock the bootloader. I followed the steps correctly and got to the screen on my phone where it gives all the information about warranty and asks "Unlock the bootloader?". I volume up and pick "Yes". Device restarts and nothing happened. Again back to the day I installed 4.4.2 and the bootloader is still locked
You will somehow have to unlock. Have you tried from command line to use the unlock.bin file, or have you tried it via AIO to see if there are different results when it asks? To downgrade you will need to get that done, S-Off, downgrade HBoot, and run the RUU if there is one for your device. If not, grab one of the stock 4.3's from the forums, and do it manually. Personally I would change CID if needed and RUU the dev edition, but that's just me.

Possible intruder on my N6

I have recently purchased a used Nexus 6 and I have just noticed that my phone may be compromised. It took a while to set up the phone as i wasn't getting the original account info to complete the setup, but now that I have run the setup, and set up a 'group' on the home screen that I labelled 'Entertainment' which holds a couple games. I see now, that the label has been changed to 'D's Sacs Was DQ'. Why would this happen and or what can be done to secure my phone? Please help!
Thank you
FK
fkoulbot said:
I have recently purchased a used Nexus 6 and I have just noticed that my phone may be compromised. It took a while to set up the phone as i wasn't getting the original account info to complete the setup, but now that I have run the setup, and set up a 'group' on the home screen that I labelled 'Entertainment' which holds a couple games. I see now, that the label has been changed to 'D's Sacs Was DQ'. Why would this happen and or what can be done to secure my phone? Please help!
Thank you
FK
Click to expand...
Click to collapse
LMAO! Really?! Did you factory wipe it? Is it stock or boot loader unlocked? Is it rooted?
fkoulbot said:
I have recently purchased a used Nexus 6 and I have just noticed that my phone may be compromised. It took a while to set up the phone as i wasn't getting the original account info to complete the setup, but now that I have run the setup, and set up a 'group' on the home screen that I labelled 'Entertainment' which holds a couple games. I see now, that the label has been changed to 'D's Sacs Was DQ'. Why would this happen and or what can be done to secure my phone? Please help!
Thank you
FK
Click to expand...
Click to collapse
Flash userdata.img and erase and flash cache.img in fastboot (if you have a unlocked bootloader) and after that data factory reset in recovery and reboot. That all you can you do.
Flashing it to ensure it was wiped of anything on it prior to use, since it was used, should have been the first thing done to it (ensuring ti wasn't locked to an account or you would have issues afterwards).
gee2012 said:
Flash userdata.img and erase and flash cache.img in fastboot (if you have a unlocked bootloader) and after that data factory reset in recovery and reboot. That all you can you do.
Click to expand...
Click to collapse
How do i know if I have an unlocked bootloader? I'm worried if i do a factory reset I'd be locked out if their account is still considered the original.
fkoulbot said:
How do i know if I have an unlocked bootloader? I'm worried if i do a factory reset I'd be locked out if their account is still considered the original.
Click to expand...
Click to collapse
To get in booltoader/fastboot mode:
1. with adb, type in cmd: adb reboot bootloader
2. Manualy: power down the phone and press both volume up and down + power.
RW-1 said:
Flashing it to ensure it was wiped of anything on it prior to use, since it was used, should have been the first thing done to it (ensuring ti wasn't locked to an account or you would have issues afterwards).
Click to expand...
Click to collapse
That was an issue when I began. I needed their account info to log in during setup but then was able to add my info.
fkoulbot said:
That was an issue when I began. I needed their account info to log in during setup but then was able to add my info.
Click to expand...
Click to collapse
Try logging in and boot the phone with the original account, delete the account and then perform a data factory reset in recovery. Then boot up with your account and that should do it usualy.
fkoulbot said:
How do i know if I have an unlocked bootloader? I'm worried if i do a factory reset I'd be locked out if their account is still considered the original.
Click to expand...
Click to collapse
Or even easier... do you see a little icon of an unlocked lock at the bottom of the screen when you boot your phone?
Or, something much less nefarious...
I would think that it could be possible you may have placed the phone in a pocket with the home screen showing (or some similar action) and the folder got renamed with random presses that also triggered random words through autocomplete. Been there, done that.
It was me.. I hacked you.. But once I was in, I couldn't think of anything to do, so I renamed a folder. Was gonna key log your bank details but this was way better
I hack phones and change events in the calendar app. Because I like confusion and making people late.

[Q] I think I hard bricked my N6

Hi there,
So I just bought a brand new N6.
Did nothing to it, did not unklock the bootloader, di not flash anything.
Just ran it a first time, set my account, donwloaded the 5.1 OTA when proposed to and then it was over.
After the OTA installation my phone displayed a dead android and "Error".
When rebooting my phone, the apps are "optimizing" undefinitely and then the phone will restart.
I tried factory reset from recovery, that did nothing, I mean, the phone will still bootloop endlessly.
My bootloader is not unlocked so I cannot flash my phone..
Is there anything I can do ?
Thank you in advance
Aanze said:
Hi there,
So I just bought a brand new N6.
Did nothing to it, did not unklock the bootloader, di not flash anything.
Just ran it a first time, set my account, donwloaded the 5.1 OTA when proposed to and then it was over.
After the OTA installation my phone displayed a dead android and "Error".
When rebooting my phone, the apps are "optimizing" undefinitely and then the phone will restart.
I tried factory reset from recovery, that did nothing, I mean, the phone will still bootloop endlessly.
My bootloader is not unlocked so I cannot flash my phone..
Is there anything I can do ?
Thank you in advance
Click to expand...
Click to collapse
try fastboot formatting userdata and fastboot formatting cache
simms22 said:
try fastboot formatting userdata and fastboot formatting cache
Click to expand...
Click to collapse
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Aanze said:
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Click to expand...
Click to collapse
Well, since you haven't enabled OEM unlock, there's not much you can do besides RMA at this point.
Aanze said:
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Click to expand...
Click to collapse
unfortunately, that might have been your only option. as you need to boot up first, to enable unlocking of your bootloader, to reflash the factory image. and you cant boot up
Evolution_Tech said:
Well, since you haven't enabled OEM unlock, there's not much you can do besides RMA at this point.
Click to expand...
Click to collapse
That's what I thought.
I thought I could use the fix described here http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518 but my device does not appear as "qhusb_bulk" like specified so I guess its over.
id get the phone refurbished, from google or from motorola, since it wasnt anything that you did, but was the updates fault. btw, that happens, very rarely, but it does happen that updates can cause issues.
simms22 said:
id get the phone refurbished, from google or from motorola, since it wasnt anything that you did, but was the updates fault. btw, that happens, very rarely, but it does happen that updates can cause issues.
Click to expand...
Click to collapse
Well thank you anyway, looks like I have no other choice than send the device back.
One last question, since my phone won't stop rebooting endlessly is there any way to turn it off ? Long press on power does not do anythng, it will stil restart...
Edit: I found how to turn it off through bootloader.
Aanze said:
Well thank you anyway, looks like I have no other choice than send the device back.
One last question, since my phone won't stop rebooting endlessly is there any way to turn it off ? Long press on power does not do anythng, it will stil restart...
Edit: I found how to turn it off through bootloader.
Click to expand...
Click to collapse
exactly. i was just gonna write how to do that.
simms22 said:
exactly. i was just gonna write how to do that.
Click to expand...
Click to collapse
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Aanze said:
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Click to expand...
Click to collapse
If getting that it should unlock. Got nothing to lose and if does unlock it is recoverable.
Aanze said:
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Click to expand...
Click to collapse
yes! if you can unlock the bootloader, then you can flash the factory image via fastboot while youre in your bootloader. which would fix you not booting
prdog1 said:
If getting that it should unlock. Got nothing to lose and if does unlock it is recoverable.
Click to expand...
Click to collapse
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Aanze said:
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Click to expand...
Click to collapse
Your good to go. Just need to fastboot the stock images.
just return it, if you find that you cant recover it after unlocking the bootloader then they wont take it back
Aanze said:
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Click to expand...
Click to collapse
grab a factory image, and read directions for flashing a factory image. you want to flash each individual file inside separately, instead of using the flash-all script.
simms22 said:
grab a factory image, and read directions for flashing a factory image. you want to flash each individual file inside separately, instead of using the flash-all script.
Click to expand...
Click to collapse
Yep, doing it right now.. flashing system currently.. crossing fingers;.
crossing my fingers for you over here as well
It worked !! IT WORKED !
I love you xda ! really do love you.
Thanks a million.
(Although it's a bit strange that I was able to unlock bootloader without usb debbugging mode enabled no ?)
This is very interesting indeed. To the OP, where did you purchase the device? I find it very peculiar that you were able to issue the OEM unlock command without using the toggle in settings.

Help! Phone stuck at boot screen, power button only restarts phone!!

UPDATE:
OK I'M BACK INTO RECOVERY.
Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?
When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?
I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
so I received a new Nexus 6 device from T-Mobile for my girlfriend.
In our area unfortunately Wi-Fi calling is a must, so she went ahead and did both of the OTA updates. After doing the second update the phone was stuck optimizing apps, and then the screen wouldn't work...
So I then hooked the phone up to the PC and through ADB did the following commands
fastboot erase userdata
fastboot erase cache
That was supposedly the commands I had found on the internet to go ahead and factory reset the phone.
Now the phone is stuck at the balls swirling and it won't stop. Try and hold the power button down and the phone just restarts itself, won't shut down so I can't even get back into the recovery.
I tried to first load up a factory image before doing something silly like that but when I tried to run the command "fasboot oem unlock" it says I need to enable developer options in Android... which I couldn't get to anyways...
Can someone please help with this issue. Her old phone got stolen and now she has this one which is completely messed up.
Thank you for anyone who can help me!
none
You have to hold power and down on the bottom button, or since you have adb, you can do "adb reboot recovery". Push volume down first then power. After that you can enable MTP and toss a rom on the phone. Do a complete wipe with the exception of the internal storage ( I did storage one time accidentally, yuk) flash a ROM and you should be good
I can't even turn off the device at this point.... It is just stuck at the balls spinning and won't go any further.
When trying to shut the phone off the power button just restarts the phone, doesn't shut it down. Not sure what is going on.....
jwleonhart said:
I can't even turn off the device at this point.... It is just stuck at the balls spinning and won't go any further.
When trying to shut the phone off the power button just restarts the phone, doesn't shut it down. Not sure what is going on.....
Click to expand...
Click to collapse
It should shut down if hold the power button long enough. Takes like 20 seconds or so.
OK I'M BACK INTO RECOVERY.
Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?
When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?
I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.
jwleonhart said:
OK I'M BACK INTO RECOVERY.
Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?
When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?
I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.
Click to expand...
Click to collapse
As far as I know with stock recovery about all you can do is try to format cache and try to factory reset again. Otherwise will have to take back to T-Mobile and RMA. Make them update it. Lot of OTA updates have been failing.
I'm just curious to know if there is someway. Maybe I can force TWRP recovery or something like that on the phone by at least getting in the bootloader... There is a fix for bricking if it is like that.
Why the bootloader just doesn't come unlocked I will not understand. It would prevent motorola from having a heap of useless devices, as i'm sure probably even motorola themselves cannot fix the device.
Seems like a whole pile of sh*t if you ask me.
Anyone have any ideas? Worst part is T-Mobile won't ship a phone over the weekend either, so thats just 3 more days without a phone which is just wonderful.
jwleonhart said:
I'm just curious to know if there is someway. Maybe I can force TWRP recovery or something like that on the phone by at least getting in the bootloader... There is a fix for bricking if it is like that.
Why the bootloader just doesn't come unlocked I will not understand. It would prevent motorola from having a heap of useless devices, as i'm sure probably even motorola themselves cannot fix the device.
Seems like a whole pile of sh*t if you ask me.
Anyone have any ideas? Worst part is T-Mobile won't ship a phone over the weekend either, so thats just 3 more days without a phone which is just wonderful.
Click to expand...
Click to collapse
There is no way to flash a recovery without the bootloader unlocked. On these devices it is best to unlock bootloader first thing before trying to update so have some control if things go bad. Moto has the ability to reflash them like J-Tag. TMobile store may replace it.
Messed up part about T-Mobile is the fact this was an exchange for a stolen phone. They actually waived the insurance fee of $175 and the tax on the phone... which was extremely nice of them since I still owed about $350 on the LG G3 my girlfriend had.
So since the exchange was done over the phone or I should say since the new handset would bought over the phone the store won't replace it... it's weird they operate that way because the store should be able to replace anything that is sold via phone or internet and vice versa.
jwleonhart said:
Messed up part about T-Mobile is the fact this was an exchange for a stolen phone. They actually waived the insurance fee of $175 and the tax on the phone... which was extremely nice of them since I still owed about $350 on the LG G3 my girlfriend had.
So since the exchange was done over the phone or I should say since the new handset would bought over the phone the store won't replace it... it's weird they operate that way because the store should be able to replace anything that is sold via phone or internet and vice versa.
Click to expand...
Click to collapse
Yea. It a bad situation. We have seen a lot of them choke on the OTA flash. Best to unlock upfront and fastboot the updated factory image. You are always safe once it is unlocked.
Still begs the question as to why they don't just unlock the bootloader from the factory to avoid all this crap. I mean imagine how much money and time they would save if they just did it? I completely forgot about unlocking the bootloader even because I figured hey just OTA it and be done.... remember it's my girlfriend so I wasn't going to put some ROM on there that might have something broken or whatever... can't believe this **** though.
jwleonhart said:
Still begs the question as to why they don't just unlock the bootloader from the factory to avoid all this crap. I mean imagine how much money and time they would save if they just did it? I completely forgot about unlocking the bootloader even because I figured hey just OTA it and be done.... remember it's my girlfriend so I wasn't going to put some ROM on there that might have something broken or whatever... can't believe this **** though.
Click to expand...
Click to collapse
I understand. They look at unlocked bootloader as a security problem. It even tells you it disabled security when you flip the unlock switch. From the many OTAs we have seen brick it is best to just unlock even if running stock. Once it is up and running can always relock. Do not relock if have custom recovery or kernel tho. It will more than likely bootloop. I tried it for grins but made sure the unlock option was enabled and was able to unlock and reflash. Many have flashed new software and relocked before first boot to find out it bootloops and can't unlock again. Best to have TWRP so that if is locked have a adb/MTP option. We pretty much discourage OTA. I haven't tried but have seen a post that says must be locked to OTA. If that is the case you always have the chance of a bad OTA flash and end up same place you are now. With TWRP there are also OTA files that have been converted to flashable zip and can be flashed in recovery.

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.

Categories

Resources