Hello everybody
It seems I'm quite late with this issue so I wasn't sure whether to post in an old thread or open a new one...
A few days ago my 12-year-old nephew, for 3 month a really proud owner of a Nexus S I9023 came to me desperately sad: He had tried to update to ICS (the manual "update.zip method") and ended up with a totally unresponsive phone like many others back in December.
I do not own an Android device myself and this stuff is all new to me (so sorry for any dumb questions or thoughts ;-) ), but after some googling and finding this great forum and especially AdamOutler's tool (and reading about other people's success with it) I was confident to be able to bring the Nexus back to life. But I'm still stuck at a certain point...
What I've done so far:
-I installed Ubuntu 10.04.3 LTS natively on a PC (I failed with using a virtual installation on my Mac).
-Installed JavaSDK and the UnBrickable Resurrector.
-Downloaded the Android SDK from here and installed it following this advice (I didn't download fastboot separately as it was included in the SDK).
-Downloaded a full ROM from here , extracted the bootloader.img and boot.img from the .zip, downloaded recovery-clockwork-5.0.2.0-crespo.img and put all that stuff in the fastboot directory.
Ok, ready to go now (I think):
I start the Resurrector (R40), select "Nexus S", remove the battery, plug in USB, replace the battery (now the Resurrector recognizes the Nexus) and click "Perform Resurrection" (without holding any button on the Nexus). After a few seconds the Resurrector reports success, showing the "Android with speech bubble" and saying "Fastboot mode" below. On the Nexus the Search- and Homebutton (the both on the right side) are now lit-up, but the display is still black.
At this point I'm wondering if everything went ok, shouldn't the Nexus now already show its bootloader screen like on Adam's image or the battery charging screen ? Anyway, according to the Resurrector everything is fine, so let's continue.
I start Terminal and cd to the fastboot directory. Just to be sure the Nexus is recognized:
Code:
lsusb
Bus 002 Device 023: ID 18d1:4e20
Code:
fastboot devices
34329EB4B3F800EC fastboot
Now I'm not exactly sure what to do next. As far as I've understood some have now flashed the bootloader, boot & recovery images first, others have "booted from the recovery.img (?)", in both cases I end up with this:
Code:
fastboot flash bootloader bootloader.img
sending 'bootloader' (1536 KB)...
OKAY [ 1.629s]
writing 'bootloader'...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 1.631s
Code:
fastboot boot recovery-clockwork-5.0.2.0-crespo.img
downloading 'boot.img'...
OKAY [ 4.374s]
booting...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 4.376s
But when I try to unlock, I only see this:
Code:
fastboot oem unlock
...
I wait several minutes but nothing happens. I stop this by unplugging the phone and an error appears:
Code:
FAILED (status read failed (No such device))
finished. total time: 561.710s
(I assume waiting nearly 10min is enough?)
I also tried to run fastboot as root with sudo, but that doesn't change anything. I'm really stranded at this point. :-(
This is my first contact with Android and I'm also not very familiar with Linux, but in my humble understanding I should be just one little step away from success, shouldn't I?
For me everything seems to work properly, the Resurrector reports success, saying the Nexus is in fastboot mode now, fastboot is running and recognizing it and also my attempts to "fastboot flash" or "fastboot boot" obviously work until the "Bootloader Locked" error pops up.
So the two big questions are:
1. Is it ok that after successful resurrection only Search and Home are lit-up, but the display remains black or should I see the bootloader or battery charging screen?
2. Why is fastboot stuck while unlocking?
I'm also wondering if it's worth it to set up a Linux/Windows dualboot installation to run fastboot or even Odin in Windows, I can't imagine that I have a better chance that way, this should work with Linux alone, shouldn't it?!
So, I hope I haven't bored you too much ;-)
I would really appreciate some help to make my nephew happy again...
Have a nice weekend!
If the bootloader is locked then you need to OEM unlock then on the screen it should say unlock bootloader? I need to press up with the volume keys and press ok power button.. Then it should be unlocked try that then white everything yo the phone
Sent from my Nexus S 4G using xda premium
In order to unlock oem, you first need to fastboot unlock which you did.
Then, confirm it on your phone which you didn't b/c you can't see/don't have fastboot screen.
And i think you didn't have fastboot screen b/c you didn't hold the buttons like you supposed to.
That's what everyone has to do to enter fastboot.
I think you should follow this thread.
And download and use the ROM package he has linked.
And instead of ODIN which requires Windows, you can use Heimdall which can run on Linux/Mac.
And search how to use Heimdall before flashing.
And if you don't have a backup, download some ROM (stock one preferred) to flash instead of restoring backup.
Also, search how to flash a ROM and clean/full wipe in CWM before flashing.
Same situation here, please help me.
Hello Cicofz and everybody,
I am stuck in about the same situation. Only a little later, my phone bricked on a 4.0.4 upgrade.
I used resurrection and on my phone the same Search and Home lit-up, the display remains black! but resurrection tells me it is in download or Fastboot mode. My fastboot on Mac doesn't get stuck, it tells me everything is Oke. However there is no possibility to get the screen on and really start fastboot on my phone...
So i think I'm stuck on the same thing you got stuck on some weeks ago.
Did you solve the problems in the meanwhile? If so can you please let me know how you did this.
If anybody els can help me please Do...
regards KnoefKnoef
Hello KnoefKnoef,
yes, I was able to bring the Nexus back to life (and a big grin back on my nephew's face) ;-) Afterwards it turned out pretty easy, just fastboot with Ubuntu, no need for any Windows stuff.
It's getting late here in Germany, so I'll try to recall and post what I've done tomorrow. I'm not sure, but I think I've even copied the whole terminal session so I can tell you step by step. I must have a look at the PC I used for it tomorrow...
Good Night
It is running... and yes it is on ICS 4.0.4.
thanks for your Quick reply, butt help is not needed anymore.
After using UnBrickable Resurrector in Linux I got the phone in download mode. with the home and search light glowing.
Then I Switched to Windows using this tread: *OFFICIAL* Android 4.0.4 IMM76D ROM for Nexus S 4G http://forum.xda-developers.com/showthread.php?t=1575502
It ended in a message Failed. Butt the phone was reboot-able. And best of all it is running on ICS 4.0.4.
So I'm very happy now.
It was quite a procedure doing all this on a MAC using Windows and Linux. Butt I eventually managed to do it....
Thanks for your input...
knoefknoef said:
thanks for your Quick reply, butt help is not needed anymore.
Click to expand...
Click to collapse
Pleased to hear that
Hello guys, I have looked for days and days for a solution... Could only find a solution if the tablet was a Nexus 7 or a Samsung device. I looked into the system files for anything remotely similar but unfortunately could not.
So do the great minds that are here able to help me ? So that the tablet will boot on a power input? Booting down is achieved by using an app so all I need is to boot the tablet. The tablet is a 2014 shield, rooted with cwm on 5.1.1
I am not a developer so will need a little hand holding but can usually achieve things, I would of thought somebody would have tryed this before considering the price of the tablet...
Can this be achieved by modifying a system file or does it have to be done on the bootloader ? If so can you please help.
I use the tablet mainly for in car diagnostics, and also media so want it to auto boot on power. All wiring is done just need a final little help. Regards BT
I doubt you will get your tablet to boot on charge, as it would require modifying the bootloader (wich is, AFAIK, not open-source).
But you can try some alternative, for example, don't shut it down, just let it sleep instead of powering it off. With the right settings you can get almost 0% discharge (Wifi off when screen off, turn bluetooth off, disable syncing, airplane mode, ...)
By default, the tablet screen turn on when on charge.
Cheers I will give that a try, I will see if I can get it working as you described above, what would you advise using tasker?
To anybody else;
I have tried running the : fastboot oem off-mode-charge 0 command through Minimal ADB. But unfortunately it comes back saying;
(bootloader) Unknown Command!
OKAY [ 0.029s]
finished. total time: 0.033s
When I test some other commands such as 'fastboot devices' it comes back with the correct serial so I am communicating with the device, and when I do 'fastboot oem unlock' It comes back saying unlocked too. But running 'fastboot oem device-info' again returns an unknown command... So is this a problem with what I am doing or the shield tablet not being compatible?
I was using the camera on my pixel and it just shut off. It wouldn't turn back on. I had to hold the power button down for almost a minute before it booted back up. Now I'm stuck on the bootloader screen with no way to get into recovery. Clicking on recovery brings me to a failed to load recovery message.
I'm rooted on 7.1.1 December update, unlocked bootloader, stock rom and recovery.
I've tried reading the forum's before posting but im stumped. I've tried flashing the factory image via flash-all bat, but I get stuck at writing 'bootloader'... I've tried flashing twrp with basically the same amount of success, it just saying 'booting' after I run the fastboot boot recovery command. I've tried basically every option in the skipsoft tool kit. Many of the different things I've tried seem to end up getting stuck at the bootloader portion of whatever it is I'm trying to do.
Slot b is the current slot, I feel like that has something to do with it, bl is listed as N/A on the bootloader screen. I successfully ran the fastboot active_slot command to switch to slot a, but when I rebooted slot b is still active. I can't relock the bootloader either, tried that, it says successfully locked, then it reboots and it's still unlocked.
I'm not in front of my PC right now and can give more specific details if anyone has any suggestions.
llong31 said:
I was using the camera on my pixel and it just shut off. It wouldn't turn back on. I had to hold the power button down for almost a minute before it booted back up. Now I'm stuck on the bootloader screen with no way to get into recovery. Clicking on recovery brings me to a failed to load recovery message.
I'm rooted on 7.1.1 December update, unlocked bootloader, stock rom and recovery.
I've tried reading the forum's before posting but im stumped. I've tried flashing the factory image via flash-all bat, but I get stuck at writing 'bootloader'... I've tried flashing twrp with basically the same amount of success, it just saying 'booting' after I run the fastboot boot recovery command. I've tried basically every option in the skipsoft tool kit. Many of the different things I've tried seem to end up getting stuck at the bootloader portion of whatever it is I'm trying to do.
Slot b is the current slot, I feel like that has something to do with it, bl is listed as N/A on the bootloader screen. I successfully ran the fastboot active_slot command to switch to slot a, but when I rebooted slot b is still active. I can't relock the bootloader either, tried that, it says successfully locked, then it reboots and it's still unlocked.
I'm not in front of my PC right now and can give more specific details if anyone has any suggestions.
Click to expand...
Click to collapse
If you can access bootloader, you're still OK. Take a breath, grab a recent adb/fastboot download. The Minimal ADB 1.41 copy isn't the latest but it'll work for this purpose. Redo your flash-all.bat. Be patient. May need to flash boota and bootb if you receive errors about boot slots. Search for CZ Eddie's flash-all instructions if unsure.
llong31 said:
I was using the camera on my pixel and it just shut off. It wouldn't turn back on. I had to hold the power button down for almost a minute before it booted back up. Now I'm stuck on the bootloader screen with no way to get into recovery. Clicking on recovery brings me to a failed to load recovery message.
I'm rooted on 7.1.1 December update, unlocked bootloader, stock rom and recovery.
I've tried reading the forum's before posting but im stumped. I've tried flashing the factory image via flash-all bat, but I get stuck at writing 'bootloader'... I've tried flashing twrp with basically the same amount of success, it just saying 'booting' after I run the fastboot boot recovery command. I've tried basically every option in the skipsoft tool kit. Many of the different things I've tried seem to end up getting stuck at the bootloader portion of whatever it is I'm trying to do.
Slot b is the current slot, I feel like that has something to do with it, bl is listed as N/A on the bootloader screen. I successfully ran the fastboot active_slot command to switch to slot a, but when I rebooted slot b is still active. I can't relock the bootloader either, tried that, it says successfully locked, then it reboots and it's still unlocked.
I'm not in front of my PC right now and can give more specific details if anyone has any suggestions.
Click to expand...
Click to collapse
Download the toolkit and choose option to download and install the latest factory build and when it asks if you want to erase data type n (no) so you will not lose anything. Just make sure you are on the slot that was active which i believe u said was b
quangtran1 said:
If you can access bootloader, you're still OK. Take a breath, grab a recent adb/fastboot download. The Minimal ADB 1.41 copy isn't the latest but it'll work for this purpose. Redo your flash-all.bat. Be patient. May need to flash boota and bootb if you receive errors about boot slots. Search for CZ Eddie's flash-all instructions if unsure.
Click to expand...
Click to collapse
Thanks for the quick response, but the suggestion did not work. I had previsouly tried a version of what CZ Eddie said ( my adb drivers werent updated and I didnt palce the factory image in the same folder as minimal adb). I followed the guide to a T this time with the same result. The below is the same for boot_a and boot_b
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.643s]
writing 'boot_a'...
FAILED (remote: flash write failure)
finished. total time: 1.212s
and this is what I get when trying to run the actual bat file
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.876s]
writing 'bootloader_b'...
It just sits there until I cancel the job, I let it run for about 15 min, which is prob 15 min longer than it should take for that particular portion of the batch. My bootloader is ****ed...
llong31 said:
Thanks for the quick response, but the suggestion did not work. I had previsouly tried a version of what CZ Eddie said ( my adb drivers werent updated and I didnt palce the factory image in the same folder as minimal adb). I followed the guide to a T this time with the same result.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.643s]
writing 'boot_a'...
FAILED (remote: flash write failure)
finished. total time: 1.212s
and this is what I get when trying to run the actual bat file
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.876s]
writing 'bootloader_b'...
It just sits there until I cancel the job, I let it run for about 15 min, which is prob 15 min longer than it should take for that particular portion of the batch. My bootloader is ****ed...
Click to expand...
Click to collapse
Well, you're always welcome to send it to me. I'll fix it at no charge one time, plus shipping. I have a team of testers whose only tasks are to break phones, tablets, laptops just so we can put them back together.
llong31 said:
C:\Program Files (x86)\Minimal ADB and Fastboot
Click to expand...
Click to collapse
Get off of minimal and on to Google's fastboot. May not help but there have been a far number of problems with this phone and minimal to not try.
Sounds like when I lost a recovery in one slot doing a sideload in TWRP. I did the temp TWRP load and then added TWRP properly from there. No issues after.
llong31 said:
Thanks for the quick response, but the suggestion did not work. I had previsouly tried a version of what CZ Eddie said ( my adb drivers werent updated and I didnt palce the factory image in the same folder as minimal adb). I followed the guide to a T this time with the same result. The below is the same for boot_a and boot_b
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a boot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (24821 KB)...
OKAY [ 0.643s]
writing 'boot_a'...
FAILED (remote: flash write failure)
finished. total time: 1.212s
and this is what I get when trying to run the actual bat file
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32728 KB)...
OKAY [ 0.876s]
writing 'bootloader_b'...
It just sits there until I cancel the job, I let it run for about 15 min, which is prob 15 min longer than it should take for that particular portion of the batch. My bootloader is ****ed...
Click to expand...
Click to collapse
I had to do the flash all once because I wiped the whole OS. I just ran it without specifying _a or _b and it worked like a charm. I think where to flash it is in the bat file so it puts it in the right place on its on. I didn't take out the -w to save my data.
TonikJDK said:
Get off of minimal and on to Google's fastboot. May not help but there have been a far number of problems with this phone and minimal to not try.
Click to expand...
Click to collapse
This was going to be my suggestion. It's all I ever use when flashing through fastboot.
Also, as I believe the above poster stated, I don't specify_a or_b when flashing stuff. It usually just works for me.
Hope you get it all working again. If you can access the bootloader, I believe you will be able to.
GeekMcLeod said:
This was going to be my suggestion. It's all I ever use when flashing through fastboot.
Also, as I believe the above poster stated, I don't specify_a or_b when flashing stuff. It usually just works for me.
Hope you get it all working again. If you can access the bootloader, I believe you will be able to.
Click to expand...
Click to collapse
I am not so sure minimal even supports dual partitions. It's latest version is from April. Long before all of this. Might be why people are getting in trouble. It works if you don't specify partition sometimes it seems....We might be on to something here.
quangtran1 said:
Well, you're always welcome to send it to me. I'll fix it at no charge one time, plus shipping. I have a team of testers whose only tasks are to break phones, tablets, laptops just so we can put them back together.
Click to expand...
Click to collapse
Interest to know what you do? Can I have a job
aholeinthewor1d said:
Interest to know what you do? Can I have a job
Click to expand...
Click to collapse
We're a mobile app developer for vertical markets (doctors, lawyers, engineers, warehousing). We put ourselves in customers' position to test our apps. We find ways to break mobile devices, from OS to drivers to incompatibilities to external environment (temperature, sand, rain, etc) in order to error-trap potential issues that users may encounter. We haven't bricked a phone by accident in a long while. If we brick something, we know what we did. That's why I'm speechless that average Pixel users in these forums can brick their phones.
quangtran1 said:
We're a mobile app developer for vertical markets (doctors, lawyers, engineers, warehousing). We put ourselves in customers' position to test our apps. We find ways to break mobile devices, from OS to external environment (temperature, sand, rain, etc) in order to error-trap potential issues that users may encounter. We haven't bricked a phone by accident in a long while. If we brick something, we know what we did. That's why I'm speechless that average Pixel users in these forums can brick their phones.
Click to expand...
Click to collapse
That sounds awesome. Here I am doing tech support from home talking to miserable people all day. But yea it's crazy how quiet it is here. I don't really mean the development side of things either I just mean on general any time I've had new phones at release the forums were filled with people. Hoping after the holidays and as back orders are shipping we get some more people here that can figure this out.
I know I won't have an issue rooting and installing TWRP but I'm a little nervous to flash Roms before this is figured out. Especially because I don't stay on any single ROM that long I like to experiment.
aholeinthewor1d said:
That sounds awesome. Here I am doing tech support from home talking to miserable people all day. But yea it's crazy how quiet it is here. I don't really mean the development side of things either I just mean on general any time I've had new phones at release the forums were filled with people. Hoping after the holidays and as back orders are shipping we get some more people here that can figure this out.
I know I won't have an issue rooting and installing TWRP but I'm a little nervous to flash Roms before this is figured out. Especially because I don't stay on any single ROM that long I like to experiment.
Click to expand...
Click to collapse
Understandable.
quangtran1 said:
We're a mobile app developer for vertical markets (doctors, lawyers, engineers, warehousing). We put ourselves in customers' position to test our apps. We find ways to break mobile devices, from OS to drivers to incompatibilities to external environment (temperature, sand, rain, etc) in order to error-trap potential issues that users may encounter. We haven't bricked a phone by accident in a long while. If we brick something, we know what we did. That's why I'm speechless that average Pixel users in these forums can brick their phones.
Click to expand...
Click to collapse
Im sure you didnt mean it this way, but I didnt do anything to brick the phone, I wasnt flashing twrp or a rom or tinkering in any way. I was just using the camera. The more I'm reading, the more I'm thinking its an issue with 7.1.1 with pixels and nexus 6p's. I RMA'd this, we'll see what happens.
Also, I tried google fastboot, didnt change anything. I let it sit for about an hour and a half running the flash-all.bat, just sits at writing 'bootloader'... One thing I noticed is that with google fastboot is says writing 'bootloader' whereas with minimal adb is gave a specific slot it was writing.
llong31 said:
Im sure you didnt mean it this way, but I didnt do anything to brick the phone, I wasnt flashing twrp or a rom or tinkering in any way. I was just using the camera. The more I'm reading, the more I'm thinking its an issue with 7.1.1 with pixels and nexus 6p's. I RMA'd this, we'll see what happens.
Also, I tried google fastboot, didnt change anything. I let it sit for about an hour and a half running the flash-all.bat, just sits at writing 'bootloader'... One thing I noticed is that with google fastboot is says writing 'bootloader' whereas with minimal adb is gave a specific slot it was writing.
Click to expand...
Click to collapse
There was absolutely no negative connotation in my comment. I stand by my experience that it is improbable to brick a smart phone. I'm just flabbergasted that it happens at all to anyone these days.
llong31 said:
Also, I tried google fastboot, didnt change anything. I let it sit for about an hour and a half running the flash-all.bat, just sits at writing 'bootloader'... One thing I noticed is that with google fastboot is says writing 'bootloader' whereas with minimal adb is gave a specific slot it was writing.
Click to expand...
Click to collapse
Thank you for trying, and letting us know how it went. We are all still gathering info, and it's much appreciated. And glad they rma'd it.
TonikJDK said:
Thank you for trying, and letting us know how it went. We are all still gathering info, and it's much appreciated. And glad they rma'd it.
Click to expand...
Click to collapse
Thought I'd add a little more info...
I cant charge the phone with the phone being turned off. It shows a picture of a battery being charged, screen goes black and flashes a a blue horizontal line across it (kinda like its glitching out). It does this about 3 times and then it automatically turns on without me pushing the power button. Not sure whats causing this, but its strange to say the least.
I made sure I had the latest SDK on my pc, been trying a bunch of different fastboot commands to try and wipe the thing and start over. Every command I run results in- FAILED (remote: failed to erase partition).
I tried searching this error, and its not looking good, most people just RMA'd their devices with many believing the internal sd is corrupted. I hope they accept it back, I checked the tamper flag, and its not on, unlocked is showing as on though (obviously).
llong31 said:
Thought I'd add a little more info...
I cant charge the phone with the phone being turned off. It shows a picture of a battery being charged, screen goes black and flashes a a blue horizontal line across it (kinda like its glitching out). It does this about 3 times and then it automatically turns on without me pushing the power button. Not sure whats causing this, but its strange to say the least.
I made sure I had the latest SDK on my pc, been trying a bunch of different fastboot commands to try and wipe the thing and start over. Every command I run results in- FAILED (remote: failed to erase partition).
I tried searching this error, and its not looking good, most people just RMA'd their devices with many believing the internal sd is corrupted. I hope they accept it back, I checked the tamper flag, and its not on, unlocked is showing as on though (obviously).
Click to expand...
Click to collapse
Sure, a corrupt system would certainly cause the battery replenishment logic to misbehave. It won't know when to fast charge, when to maintain, when to trickle, etc.
llong31 said:
Thought I'd add a little more info...
I cant charge the phone with the phone being turned off. It shows a picture of a battery being charged, screen goes black and flashes a a blue horizontal line across it (kinda like its glitching out). It does this about 3 times and then it automatically turns on without me pushing the power button. Not sure whats causing this, but its strange to say the least.
I made sure I had the latest SDK on my pc, been trying a bunch of different fastboot commands to try and wipe the thing and start over. Every command I run results in- FAILED (remote: failed to erase partition).
I tried searching this error, and its not looking good, most people just RMA'd their devices with many believing the internal sd is corrupted. I hope they accept it back, I checked the tamper flag, and its not on, unlocked is showing as on though (obviously).
Click to expand...
Click to collapse
Did you have an outdated fastboot binary? If you can still get in bootloader, I'd try with the good fastboot from the Android SDK.
This is a standard US Google Pixel 128GB that I picked up in January from Swappa. I have not ever modified it in any way. Never been dropped or abused either.
Since early April, the phone would randomly freeze and reboot itself. Sometimes it would be days between reboots, sometimes it would reboot multiple times even before it finishes booting. It's usually random, but I noticed it would always reboot if I am recording a really long video (5-10 minutes). Audio also failed once (no sound could be heard from speaker or earpiece) even after rebooting multiple times. Three days ago, while recording a long video of my kid at Disneyland, it froze. This time, the reboot failed to. The screen flashes some garbled stuff on the screen. Only difference this time is that I know the internal flash memory was almost full before I even started recording the video.
I can't get the phone to boot at all. If I press the vol-down button (doesn't even need the power button), I can get to the bootloader menu. In the bootloader menu, if I choose "Start," Restart bootloader," or "Recovery mode," the screen will flash again forever (I've waited hours). If I choose "Barcodes," then I will see all the proper IME/SKU/Serial numbers and barcodes. Choosing "Power off" works too, if it's not plugged in -- if it's plugged into power, the screen will flash a "static" screen endlessly. I took a video of this happening at Disneyland.
https://youtu.be/VlQ_PpZQ9SY
https://youtu.be/5m8_u0nQ4hE (the flashing screen)
After I got back from vacation, I plugged it into a Windows PC. No ADB access, but I can get fastboot to see it. Trying to reflash the lastest stock image (https://forum.xda-developers.com/showpost.php?p=70972735&postcount=3) fails with this:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32380 KB)...
OKAY [ 0.810s]
writing 'bootloader_b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.919s
rebooting into bootloader...
OKAY [ 0.052s]
finished. total time: 0.055s
< waiting for any device >
Click to expand...
Click to collapse
The screen would flash the same garbage as it tried to reboot into bootloader. I hold down the volume-down button to get back in and it continues:
target reported max download size of 536870912 bytes
sending 'radio_b' (57240 KB)...
OKAY [ 1.430s]
writing 'radio_b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.542s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
< waiting for any device >
Click to expand...
Click to collapse
Once again the screen would flash the same garbage as it tried to reboot into bootloader. I hold down the volume-down button to get back in and it continues:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
Bootloader Version...: N/A
Baseband Version.....: N/A
Serial Number........: FA6C70300873
checking product...
OKAY [ 0.052s]
checking version-bootloader...
FAILED
Device version-bootloader is 'N/A'.
Update requires '8996-012001-1703151359'.
finished. total time: 0.367s
Press any key to exit...
Click to expand...
Click to collapse
That's it. The bootloader screen does show BL and Baseband versions as "N/A", but can't these be overwritten? And is it normal for the device to say LOCKED? This is everything on my bootloader screen:
BL: N/A
Baseband: N/A
Product/Variant: sailfish-US-PVT
Serial Number: FAxxxxxxxx
CPU: MSM8996SG-AB 0x10001
UFS: 128GB Toshiba
DRAM: 4096MB Hynix LPDDR4
Boot-slot: b
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Click to expand...
Click to collapse
If it'll help, I can get better photos/videos of the phone. The screen flashes some random distorted Google/Android logos and some "static"-looking pixels.
Any clue about what I should do? I would like to be able to get my photos/videos from the phone. I would also like to be able to recover the phone. Doing both would be awesome. I'm not sure if there is a hardware issue or software issue, but this phone has been horrible since April.
I think either your phone is bricked or your hardware has failed. Fastboot error shows that it cannot identify your bootloader so you have to get a replacement through Google. Check Google photos to see if there are backups of the videos.
Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.
Tulsadiver said:
Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.
Click to expand...
Click to collapse
But wouldn't stock recovery support adb commands? I never checked but if it does he could adb pull files off of sdcard
UPDATE: Someone suggested I try draining the battery and try rebooting. Didn't think it would help, but was desperate, so I left the phone on. A few hours later, it shutoff. I put it back on a charger overnight. Now I can't even start it again. This thing is a brick. So disappointed in Google.
justinxfan said:
I think either your phone is bricked or your hardware has failed. Fastboot error shows that it cannot identify your bootloader so you have to get a replacement through Google. Check Google photos to see if there are backups of the videos.
Click to expand...
Click to collapse
I make sure to backup every night while charging and on WiFi, but this happened at Disneyland and I had the entire day's videos not yet backed up. :crying:
Tulsadiver said:
Try to boot to twrp. Maybe the pc will see your phone and you can get your video off.
Oops. Sorry, didn't see you are locked.
Click to expand...
Click to collapse
danielt021 said:
But wouldn't stock recovery support adb commands? I never checked but if it does he could adb pull files off of sdcard
Click to expand...
Click to collapse
adb didn't see the device. Just fastboot.
ken830 said:
UPDATE: Someone suggested I try draining the battery and try rebooting. Didn't think it would help, but was desperate, so I left the phone on. A few hours later, it shutoff. I put it back on a charger overnight. Now I can't even start it again. This thing is a brick. So disappointed in Google.
I make sure to backup every night while charging and on WiFi, but this happened at Disneyland and I had the entire day's videos not yet backed up. :crying:
adb didn't see the device. Just fastboot.
Click to expand...
Click to collapse
Yep sounds like the boot loader is screwed. Phone is a brick. She thing happened to my Nexus 7. I had to replace the motherboard.
did anyone got any leads on this... the same issue with my pixel 128gb... unfortunately it is out of warranty. a working solution would be a great help.
AlphaOrion said:
did anyone got any leads on this... the same issue with my pixel 128gb... unfortunately it is out of warranty. a working solution would be a great help.
Click to expand...
Click to collapse
Sorry to hear this, but I didn't have any solution except for replacing the entire phone. You should contact Google anyhow.
this is so disappointing...I wonder how many people this has happed to already, I was using the phone and it just randomly shut off and wont turn back on..almost exactly what the OP is experiencing...obviously phone is now out of warranty and apparently motherboard needs to be replaced (which is ridiculous!!)….I've never had a phone brick on me ever, never thought it would actually happen, especially on stock everything.
---------- Post added at 08:02 AM ---------- Previous post was at 07:57 AM ----------
Maybe its me....but it seems like more and more people are having this issue...looks like as the hardware gets older the more prone to partition being corrupted....this is not acceptable for a 2 year old phone
I have had numerous pixel replacements. One of them was a hard brick like yours. Even took it to iFixit and they confirmed it was dead. So it may not be uncommon.
I just don't get if photos and videos were so important if no one ever does a weekly backup? Use Google drive, use Google photos, use your USB cable to PC if you don't trust Google.
Phones break, get over it. You want a fast phone? Expect it to die even faster. 2 years for a phone is normal, if you don't think it is get then budget phones are there, with the long life low hardware aspect
I had TWRP and Magisk flashed. Now I wanted to go back, flashed factory, locked the bootloader and now I can only boot into fastboot. Everything elsa ends in a bootloop with a short flashing Google logo.