Related
I'm hoping someone might be able to help me recover my Nexus 7 which appears to be bricked currently. It is the 2013 version, and it was never rooted initially and was running stock firmware. (By the way, I'm not the most proficient with messing with my Android devices or even with the terminology, so I apologize in advance if I might require clarification on some of the responses).
A few days ago, I woke up to discover that somehow my home screen had reverted back to the way it was upon initially getting the device. This wasn't a big deal since I didn't lose any data or apps, but I figured something might be wrong and even posted about it on Google's product forums. Then, last night, I attempted to update to 4.4.3 because it had been prompting me to do so for a week or two. It downloaded and attempted the update, but it failed. It then eventually restarted, but upon loading up Android I got an error message that stated:
System UID's Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable
with a button to click that says "I'm Feeling Lucky" - I clicked the button figuring I could at least get back in to back up my data, but after about 30 seconds the device just rebooted again (all I managed to do was accidentally click the Chrome icon) and now it is just stuck at the initial boot-up screen displaying the Google text logo.
I have tried to hold down the volume button and hit power, and I get to a screen with 4 options I can cycle through: Recovery mode (which will just put me back the Google text logo), Power off (which turns off the device), Start (which puts me back to the Google text logo), and Restart bootloader (which brings me right back to this menu options page). I'm attaching a screenshot of this page.
I spent about an hour on the phone with Google support, but they were basically useless. I then did some research and downloaded Skipsoft Unified Android Toolkit and was able to get the device to be recognized when it was in that 4-option mode by the Skipsoft Toolkit. However, all fastboot options I tried didn't seem to succeed because the Bootloader was locked. I figured I would try to unlock it, and it told me that in doing so it would wipe my device (so be it I figured since I had already pretty much kissed my data on there goodbye at this point). However, it seems to try and wipe it (even giving me a prompt on the actual Nexus 7), but then just sits and does nothing that I can see (see attached screenshots).
Anyone have any ideas/suggestions? Thanks so much!
To be safe, with a stock device that was not rooted... I would go ahead and use the Skipsoft program to flash the stock image back on the device. This should alleviate any future issues with the OS on your device.
I believe it to be Option #9 on Skipsoft.
xbi0s said:
To be safe, with a stock device that was not rooted... I would go ahead and use the Skipsoft program to flash the stock image back on the device. This should alleviate any future issues with the OS on your device.
I believe it to be Option #9 on Skipsoft.
Click to expand...
Click to collapse
Thanks for the reply - I attempted your suggestion, but it didn't work because the Bootloader is still locked; and attempting to unlock the Bootloader seems to stall on erasing userdata.
Any other thoughts? Thanks!
Anyone else have any suggestions/ideas? Thanks!
mbressman said:
Anyone else have any suggestions/ideas? Thanks!
Click to expand...
Click to collapse
Download ADB from my signature.
Put the device in bootloader mode (power+vol down), open fastboot.exe and type fastboot oem unlock.
Aerowinder said:
Download ADB from my signature.
Put the device in bootloader mode (power+vol down), open fastboot.exe and type fastboot oem unlock.
Click to expand...
Click to collapse
When I try that, I get:
Code:
C:\Users\User\Desktop\ADB & Fastboot API 19 (19.0.1)>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
And it just hangs there....
The Nexus 7 did prompt me whether I want to unlock the bootloader and I selected yes (with the volume and power keys), but then it just hangs at that selection screen as well...
Any ideas??
Thanks!
mbressman said:
When I try that, I get:
Code:
C:\Users\User\Desktop\ADB & Fastboot API 19 (19.0.1)>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
And it just hangs there....
The Nexus 7 did prompt me whether I want to unlock the bootloader and I selected yes (with the volume and power keys), but then it just hangs at that selection screen as well...
Any ideas??
Thanks!
Click to expand...
Click to collapse
I changed the wrong link in my signature. The ADB link correctly points to version 19.0.2 now. Try that one. Try a different cable if you have one, try a different USB port if you can.
Aerowinder said:
I changed the wrong link in my signature. The ADB link correctly points to version 19.0.2 now. Try that one. Try a different cable if you have one, try a different USB port if you can.
Click to expand...
Click to collapse
Tried two different cables on two different USB ports with the new 19.0.2 downloads you posted - still having the same thing happen. Could it be the computer I'm using, or the drivers I installed (I used the Skipsoft Unified Android Toolkit drivers)? Or is my device just totally bricked and unrecoverable?
Thanks!
mbressman said:
Tried two different cables on two different USB ports with the new 19.0.2 downloads you posted - still having the same thing happen. Could it be the computer I'm using, or the drivers I installed (I used the Skipsoft Unified Android Toolkit drivers)? Or is my device just totally bricked and unrecoverable?
Thanks!
Click to expand...
Click to collapse
You can try different drivers. Uninstall current ones, and install the ones from my signature.
Aerowinder said:
You can try different drivers. Uninstall current ones, and install the ones from my signature.
Click to expand...
Click to collapse
Ok, so I removed the Clockworkmod ADB drivers from add/remove programs (or uninstall programs - whatever it is called now on Win7), then I went into device manager and deleted the driver for Google Nexus BootLoader Interface, and then I rebooted. After the reboot, plugging the Nexus 7 in showed no driver detected, so I downloaded your Koush Universal ADB drivers, extracted them, and used them to install the Google Nexus Bootloader Interface drivers again (that's what it detected for my Android when I pointed the device listed in device manager to the extracted folder).
I then ran "fastboot oem unlock" but it's still getting stuck at the same place: (bootloader) erasing userdata...
Anything else I can try?
Thanks!
Hi,
I have the same issue since yesterday. When I pulled my nexus from my backpack (charged 12 hours earlier) its battery was drained. After charging it nexus stucked on google screen during normal or recovery boot. Oem unlock also hangs on erasing userdata. I'm looking forward for any solution to this.
Maybe some ****ty update? I've got the LTE version.
Anyone have anything else I can try?
I'm currently working on getting ASUS to replace the device under warranty - but they want me to send it in first, and I'm concerned that while I can't access any of my data on it, the data might still be there and potentially accessible to others (and I'd prefer to not have all of my confidential data that I stored on there accessible to anyone else). Unfortunately, ASUS won't replace/repair it unless I send it in, so I'm between a rock and a hard place...
Any help or advice is greatly appreciated!
Thanks.
mbressman said:
Anyone have anything else I can try?
I'm currently working on getting ASUS to replace the device under warranty - but they want me to send it in first, and I'm concerned that while I can't access any of my data on it, the data might still be there and potentially accessible to others (and I'd prefer to not have all of my confidential data that I stored on there accessible to anyone else). Unfortunately, ASUS won't replace/repair it unless I send it in, so I'm between a rock and a hard place...
Any help or advice is greatly appreciated!
Thanks.
Click to expand...
Click to collapse
I've tried every single way to unbrick my nexus. After 2 days of searching send it for repair. Without any questions they replaced mainboard. Problem solved hard way.
Gawson said:
I've tried every single way to unbrick my nexus. After 2 days of searching send it for repair. Without any questions they replaced mainboard. Problem solved hard way.
Click to expand...
Click to collapse
Gawson - when you got it back did it still have your data on it, or was it wiped?
mbressman said:
Gawson - when you got it back did it still have your data on it, or was it wiped?
Click to expand...
Click to collapse
When I got it was wiped. Flash is on the mainboard so there was no way they could save my data. They do not migrate your personal stuff.
Now its working like new. In fact it has all new guts except battery and screen.
Only problem is that now auto brightness sensor is giving crap instead of useful data. I don't know if its hardware related or just 4.4.3 issue.
OK,
So a friend of mine asked me to help him fix his Nexus 7 2013 FLO (WiFi only).
According to him he hasn't even unlocked the bootloader (and the info displayed while in fastboot mode confirms this). Apparently what happened, a few months ago, he downloaded an OFFICIAL KitKat OTA, clicked OK to upgrade, and since then, the tablet will not get past the screen that says Google. I can get it into fastboot mode but cannot flash anything, and when I attempted to use The Nexus Root Toolkit by WugFresh to unlock the bootloader at the very least, I can get it to display the screen that says "please use the arrow key to navigate Yes or No. Unlocking your bootloader allows you to load a custom OS, but may void your warranty, etc. etc. etc."
I tried using CMD to erase the cache and userdata and after giving it upwards of 20 minutes, during which the window (in CMD) simply said "erasing cache" and never actually made any progress whatsoever...
Any idea what (if anything) can be done?
Sound off in the comments!
Thanks a million!
Stephen Spigelman
I can't help... but am in the same boat as of last night with the 5.0 update.
Were you able to unlock the bootloader? You did say that you were able to get to the screen to unlock it. If not, i dont think much of anything can be done.
Bricked
Virgin N7 2013... No hacking... Bootloader locked... started acting weird and I attempted a system restore. It now gets stuck at the Google screen. Fastboot gets stuck at erasing userdata. I have tried multiple USB cables on Win7, OSX, and Ubuntu. Help!!!
im wondering how this happens?, I already unlocked my bootloader just cause of this.. maybe the chip just dies?
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
ariesgodofwar said:
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
Click to expand...
Click to collapse
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
tigerdim said:
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
Click to expand...
Click to collapse
Mine did not occur after flashing any firmware, but the symptom was the same in that I could get into the bootloader, attempt to flash new system images, appear as if all would be well, and then on reboot would stick at the Google screen. Not sure if folks are seeing the same thing here, but when I tried to get into Recovery from the Bootloader menu, it would reboot as if going there, but still never make it past the Google screen. It happened within 18 hours of unboxing a remanufactured N7 G2. Asus advised on the packing slip that is was a LED (Indicator) Error (whatever that is), and they they subsequently had to replace the board to fix it.
I hope it is a software issue, but not sure to tell you how to go about correcting it if you cannot flash new images via ADB or the bootloader and get it to boot successfully.
When i boot to recovery i get the TWRP startup screen but stays stuck.
Bump
bump.. any ideas?
i have the same :/
kobi_shalom said:
i have the same :/
Click to expand...
Click to collapse
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
tigerdim said:
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
Click to expand...
Click to collapse
So you success?
NO success because I cannot unlock the bootloader.
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Dielahn said:
I have no experience with your issue but it sounds like a soft brick. Im sure if you follow this guide ypu can fix it. https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418 hopefully this helps until someone who really knows can help you.
Click to expand...
Click to collapse
That simple thread actually gave me an idea. I grabbed the latest SDK tools. Presto!
Note to anyone else with this issue...
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
By the way, the dead Droid is recovery, from that screen, hold power and press up for recovery menu, in case you ever get stuck again
And just for future reference for others who may be in a similar issue and stumble across this thread...
As long as you've successfully unlocked your bootloader and "fastboot devices" successfully pulls up your device, you'll be just fine. You just gotta take a step back, breath and then make sure your SDK tools are updated before moving forward.
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
Make sure you try a different cable to connect your phone to your PC.. I had the same issue, and I try two different cable before my device accepted the flash-all
Okay, so somehow fortunately I was able to get back into my TWRP 1 last time and able to push my files I needed to boot it back up...
Raistline said:
If you cannot get the Bootloader to load, then you are seriously SOL. You have a hard bricked device.
Only thing you can do now is raise a support case with Google and hope that allow you to get a replacement with the only explanation being, "The phone restarted on it's own and never came back up." Or something similar and vague without expressly telling them what you did.
Click to expand...
Click to collapse
The funny thing is I was able to and was in bootloader but I couldn't use any commands from my computer (as far as I know) which is why I was freaking out.
I should've but I didn't actually try using other cables. I did try other usb ports but that didn't do anything.
I still kind of believe that my phone (somehow) got messed up from loading TWRP. I don't know if it's because it is still beta or what but I am like 99% sure it was from that as I can't see anything else being the problem.
warlord1352 said:
i know this is probably going to sound really stupid but somehow i bricked my phone as well....not exactly sure what happened but it had to do with something after installing/booting TWRP. anyway, i am stuck with nothing on my phone and can't seem to do anyting....derek, how did you use sdk to fix???
*edit I can't even have fastboot devices pull my phone....am i really f'ed?
Click to expand...
Click to collapse
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
derekr44 said:
Just got the XL on Friday. Loved it.
Unlocked the bootloader about 45 minutes ago. Wiped upon reboot (as normal). Google logo displayed with progress bar but the animation never stopped.
Downloaded the factory image from Nov. Ran the flash-all.bat from bootloader. No errors. Rebooted. Got a "Your device is corrupt" error. Phone stuck on the Google boot screen. Going into recovery just gives me a dead droid.
Attempting to flash the 8.1 developer preview results in the same issue. As of right now, nothing seems to boot at all. I've changed USB-C cables, since I've read about those causing issues, but still the same.
Click to expand...
Click to collapse
Something similar for me but with different reason for starting all this. When I did sideload of 8.1 all went well but my camera wasn't working (I saw the same thing in 8.1 DP) so I needed to go back to 8.0 but you can't sideload downgrade. I went to Google to get replacement sent and figure I might try to sort things out with this one in the meantime. I had to unlock to be able to just flash the factory 8.0 image so did that with both the unlock commands, then after that and after update I just got hung on the white screen with google logo. I was able to get back to bootloader with the power button + volume from off and from there I would get to the screen with the android and the exclamation point - I think you hold volume up and then power to go to sideload. Once there I just sideloaded 8.0 and all was good. I do still get the warning about corrupt whatever and have to hit power on reboot or fresh power up but I could redo the locks and whatnot and all seems fine now with camera working.
At the least I got camera back while waiting for replacement.
b4db0ys said:
just install the lastest fastboot and adb drivers from google and flash the factory image using commands or use any script .
after that everytime my phone got stuck on google logo .
how i fixed - Temporary boot twrp beta2 recovery using cmd (fastboot boot abc.img) "here abc refers to the correct name of the img file" and once booted into recovery go to advanced and select Partition A and reboot.
It will boot up just fine
Here is the link for a script that will flash both partitions with stock image
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
This cleaned things up for me - still no camera in 8.1 but I got the replacement coming.
So I'm in the same boat as the OP but my bootloader is locked. Am I totally screwed? Is there a way to do any of this when the device won't show up in ADB?
Deuces said:
if the flash tool isn't working, use my script:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
can you just develop some scripts that working on locked bootloader ?
i have a bricked Pixel xl with locked bootloader and oem locked
If you can boot twrp but can't connect to a pc, a type c flash drive comes in handy. Load it with the needed ota, twrp installer zip and Just mount it and you're good to go.
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
If it still boots into the boot loader you're fine and fixable.
Phalanx7621 said:
If it still boots into the boot loader you're fine and fixable.
Click to expand...
Click to collapse
Well that's good news at least!
What can I do?
Prosis said:
Well that's good news at least!
What can I do?
Click to expand...
Click to collapse
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Phalanx7621 said:
This will wipe your device. If it won't boot up, there are a ton of other things you COULD try, but without knowing what caused it to be this way it'd be fishing in the dark.
Go to this website https://developers.google.com/android/images
download Android 8.1 Oreo Factory Image (make sure Factory Images is selected in the upper left portion of the screen at the top, not OTA).
After downloading, extract the files to a folder, go into that folder and select all the items in it and copy them to wherever you have fastboot / adb installed. Make sure phone is in bootloader, then open a command prompt (or Windows Powershell in Windows 10)use Fastboot command:
fastboot flash-all.bat
If in Windows Powershell, use command:
.\fastboot flash-all.bat
If you need platform-tools (adb/fastboot) they're here
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Prosis said:
But don't I need to have an unlocked bootloader for that? It's currently locked and OEM Unlock was not enabled in Android before it crashed.
Click to expand...
Click to collapse
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Phalanx7621 said:
Ohh....well then you'd need to enter recovery mode, but you're saying that doesn't work?
Have you powered down the device completely, plugged it into a power source, then tried booting into bootloader mode, choosing Recovery Mode, and then once the dead android appears on the screen from recovery mode, hold down the power button and while holding that down click the Volume Up button once, then release the Power button. This should allow access to the stock recovery where you can do a factory reset.
Click to expand...
Click to collapse
Yeah I tried that but the dead android never appears. It reacts the same way it does when I try to boot into the system, which is just a white flicker that appears and disappears on the top of the screen. It's like it's trying to load the white screen with the Google logo but it can't.
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Phalanx7621 said:
Had you modified the system at all? Was this bare bones stock? As far as I know, nothing can touch system files without root, so recovery (boot.img) should be fine. What about overheating, that was my next question. Was it getting super hot before this happened?
edit: I found this website, with this gentleman claiming that the Nexus Root Toolkit also works for our devices in a "bricked" situation. I know nothing about it, nor have I tried it, was just looking to see if I could find anyone else with your situation and ran across this website .
https://forums.androidcentral.com/google-pixel-pixel-xl/804286-help-bricked-my-pixel-xl.html
http://www.wugfresh.com/nrt/
Again, I have never used this, so use at your own risk. Hopefully someone else will help out here who may have this similar situation.
Click to expand...
Click to collapse
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Prosis said:
Thank you! No it was not modified in any way. The only thing that happened was that I tried the P Beta (through OTA) during the weekend and flashed (through fastboot) the factory Oreo ROM then relocked the bootloader. So everything was back to factory state. Everything worked fine all week. It wasn't hot when it shut down at all.
I'll try this while I wait for Google's response to whether it's under warranty or not and keep you updated.
In the meantime, if you or anyone else has a way to just try to flash the ROM or recovery again even with the locked bootloader I'm all ears!
Thanks
Click to expand...
Click to collapse
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Phalanx7621 said:
Ohhh ok I see. Yes, never ever relock the bootloader. In case of situations like this, it's always a good idea to leave it unlocked. Just out of curiosity, have you tried plugging it into a power source, powr it up to the boot loader screen, choose Recovery, then hold in Volume Down + Power for about 30 seconds? It should reboot it back to bootloader menu again. This sometimes works for me when nothing else does, but I have no idea why.
Click to expand...
Click to collapse
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Prosis said:
Oh getting into bootloader menu is no issue at all. I just can't go anywhere else (recovery, system, etc.).
It's not even able to show me the charging animation when the device is off.
Click to expand...
Click to collapse
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Phalanx7621 said:
Unforunately, if recovery mode isn't booting and you don't have the bootloader unlocked, I'm out of ideas. Have you tried, just for ****s and giggles, to unlock the bootloader again via fastboot just to see what it says?
Click to expand...
Click to collapse
Yeah I did. I even tried several tools that are supposed to be able to help but without having Allow OEM Unlock enabled nothing works :/
After maybe 2 hours left alone charging now it's not even booting into the booloader anymore...
Are you going to be able to RMA it? Is it still under warranty?
Phalanx7621 said:
Are you going to be able to RMA it? Is it still under warranty?
Click to expand...
Click to collapse
I'm waiting for my seller to give me the original order number (which seems like forever right now given the situation). Then Google will be able to tell me if it's still under warranty. If not then, according to the authorized repair center, it's either the battery, the port or the motherboard which means it's probably the end for this phone as prices range from less than $100 to nearly $400. :crying:
Prosis said:
I bought my Pixel XL (2016) used last week. Everything was perfect. Tried Android P Beta and then went back to official Oreo. The phone worked perfectly all week.
Then tonight I'm watching a YouTube video and the thing shuts off to never turn back on. I can't access recovery but the bootloader is there. The thing is it's locked and I can't allow OEM unlock cause I can't boot into Android.
When I try to boot normally or go into recovery mode there's a white flicker on top. Like it's trying to load it but can't.
It's possible that it's no longer under warranty...
Can anyone help?
Thanks :crying:
Click to expand...
Click to collapse
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Homeboy76 said:
Post this information on this thread: Need Pixel XL 128GB complete eMMC image file by noriharsha
Click to expand...
Click to collapse
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Prosis said:
Thanks but the phone isn't even powering on at this point so it's probably a physical problem.
Click to expand...
Click to collapse
Good news! I got an RMA!!
Thanks for your help everyone!
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Deleted
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
lil_michelle said:
Did you flash disable dm verity first after unlocking the bootloader before flashing a patched system image?
Click to expand...
Click to collapse
mac796 said:
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
Click to expand...
Click to collapse
thank you! Using the Android Flash Tool resolved my issue.
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
Hard to say, for those of us who haven't had any problems...yet. I've flashed the full factory image at least twice so far.
Normally, the USB cable and to a lesser extent, the USB port used on the computer, would be my first suspects as to the problem, but since you said it finished successfully, I have no clue.
Do I need to disable dm verity at least once, or is that just completely obsolete now.
summitfox said:
Do I need to disable dm verity at least once, or is that just completely obsolete now.
Click to expand...
Click to collapse
When using Magisk 23016 for rooting it is not necessary at all.
summitfox said:
Do I need to disable dm verity at least once, or is that just completely obsolete now.
Click to expand...
Click to collapse
The *only* time you *might* still need to disable verity and verification are for some custom kernels - until those kernels are updated the same way Magisk Canary 23016 was, and then they won't need it. If you're not planning on using custom kernels, and just rooting the stock kernel instead, then there's no reason to disable them anymore.
tuffCookie said:
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Click to expand...
Click to collapse
summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
Did either of you verify the hash of the download before flashing?
Before flashing any image, the hash should always be verified as it ensures the file is secure and not corrupted.
JW09I4 said:
Before flashing any image, the hash should always be verified as it ensures the file is secure and not corrupted.
Click to expand...
Click to collapse
^ This. For years now, I've just gotten used to verifying the hash of every important thing that I download that has the hash value made available. Saves a lot of hassle later on since if the downloaded file is corrupted just slightly, everything will go wrong down the road in the process.
I also check for new Platform Tools and Google's USB driver each and every time I flash a new update. It's just habit and again, saves a lot of trouble.
To add on the previously said:
Windows has a built-in hash checker, you just need to open CMD and type
Get-FileHash <Drag'n'Drop'le'File'here>
Click to expand...
Click to collapse
Then just copy the hash (strg+c) into your browser search window where you downloaded the OTA/firmware (strg f to open search, strg v to paste) and if you get a match (1/1), the hash checks out.
It's easy, it's fast, it's reliable. It will only cost you a few seconds. No hassle involved.
Morgrain said:
Windows has a built-in hash checker, you just need to open CMD and type
Click to expand...
Click to collapse
For anyone who doesn't know, this is referencing Windows' built-in PowerShell. It may be the default these days as Microsoft pushes it and it's more capable than Command Prompt, but you can still open CMD and the "Get-FileHash" won't be available there.
Morgrain said:
To add on the previously said:
Windows has a built-in hash checker, you just need to open CMD... Then just copy the hash (strg+c) into your browser search window where you downloaded the OTA/firmware (strg f to open search, strg v to paste) and if you get a match (1/1), the hash checks out.
Click to expand...
Click to collapse
roirraW edor ehT said:
For anyone who doesn't know, this is referencing Windows' built-in PowerShell. It may be the default these days as Microsoft pushes it and it's more capable than Command Prompt, but you can still open CMD and the "Get-FileHash" won't be available there.
Click to expand...
Click to collapse
It's often better to use a program that will compare the hashes, else a SHA256 or SHA512 hash becomes tedious to manually compare - I'm partial to QuickHash [GitHub] due to its broad functionality (drag and drop file for it to auto-compute hash and you can paste what the hash should be either before or after)
For quick one or two-file comparisons, I prefer Implebits' HashTab, which adds a new configurable tab to the file properties dialog in Windows. I originally got turned onto the program when it was Beeblebrox.org, which being a Douglas Adams fan definitely got my attention back then but I stuck with it after they sold it.
Edit: I see Implebits is going out of business and HashTab will go to GitHub and be open source, so exciting times!
Implbits Software, LLC is going out of business
We will soon release Hashtab as an Open Source project on Github. Until we do... you can download the last build of Hashtab that we made using the link below:
Click to expand...
Click to collapse
Actually the same situation here. What's the version of your adb tool. Do I have to use the web tool to flash in the future? Could I use adb with flash.bat as always？
mac796 said:
You're going to have to use the Android flash tool now. Just follow the link in the Google factory image site. You'll be able to get back to December at the very end. It'll tell you to relock your bootloader Don't do it if you don't want to.
Click to expand...
Click to collapse
That's what I had to do and agree to relock bootloader
Joynaruto said:
Actually the same situation here. What's the version of your adb tool. Do I have to use the web tool to flash in the future? Could I use adb with flash.bat as always？
Click to expand...
Click to collapse
Tried that with no joy as future idk. My situation was different after flashing Los the recovery was overwritten and flashing stock said something about timestamp error
summitfox said:
I did this exact same thing, unlocked device, and flash-all.bat the December update, except my device was a hard brick. I could get zero response from the device, no matter how long I would hold in the power button. Connecting to computer would chime connected, then disconnect a second later. After the flash-all.bat command, it finished successfully, the phone rebooted to a screen that said software was corrupt and would not boot. Pressed power to move passed it and phone went black forever. Had 98% battery too. Had to send back to google for replacement. Did I miss something, or was it just the super buggy December update that did it. I am now scared to death to root this phone again fearing that I did something wrong, and that it will do this again. Is fastboot flashing the factory image a bad thing now, did I miss something, or was it just some weird glitch?
Click to expand...
Click to collapse
I think you should of used the full image not the update with flashall.bat
tuffCookie said:
I got impatient and decided to flash the Dec 2021 US Carrier factory image on my unlocked Pixel 6 Pro.
I set my device to OEM unlocking, grabbed the latest ABD/Fastboot files from Google, went into the bootloader and unlocked it w/ "fastboot flashing unlock", and then proceeded to flash my device. However, I now get a "Your device is corrupt. It can't be trusted and may not work properly" error w/ a red triangle exclamation mark upon boot. I can click the power button to get past it and the device will appear to boot, but it stays stuck on the Google screen w/ white background.
I'm able to manually restart into fastboot and fastboot devices recognizes the device.
I've flashed all my previous Pixel's many times before and never came across this error. Any ideas?
Click to expand...
Click to collapse
I had this before as well after manually flashing the November update. Got the device cannot be trusted. Rebooted, flashed again, and device completely fried. Wouldn't turn on, not recognized by computer, nothing. Complete brick. Suspect system board fried. I'll never try to manually flash an update with a Google device again. Hopefully it ends better for you.