Related
I just wanted to try the latest CM9 after locking bootloader for a return. It unlocked, flashed fine, rebooted a few times. I was going to relock it so I used "reboot to bootloader". It was charging, it shut down and never turned back on. Removing the battery didn't help either. When I connect it to the PC, it recognizes OMAP4400 but doesn't install any drivers. I don't see how it can be bricked as I just rebooted to bootloader. It's been charging for a few hours and I haven't touched it since. I'm going to try the USB Jig soon, any additional help would be greatly appreciated..
If you're unlucky, you've hard-bricked it, somehow...
Try pressing (Just) Volume down + power...
That also gets you into Oding mode...
If that don't work, then sorry... I wouldn't know any other solution. Try the jig, if you want, but it's not put, that it'll work.
Well, best of uck!!
Hope you fix it!
LG familyguy59
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
The phone will work plugged in without the battery in under normal conditions, and that it's showing up at all is a good sign.
Have you used fastboot before successfully? You may need to load drivers manually. This thread links a few different options you can try:
http://rootzwiki.com/topic/12013-welcome-to-rootzwiki-editionstep-by-step-oem-unlock-and-root/
freemini said:
Jig doesn't work, volume down+power doesn't, fastboot doesn't. Anything I do to it, it still shows as OMAP4440 in device manager. Even without the battery in. It must be in some kind of special recovery mode, but how the hell does it work with no battery. I'll leave it without battery over night, it's charged for sure so that can't be the problem.
Click to expand...
Click to collapse
My guess is that if it is showing as OMAP, it is a sign that bootloader is not working at all, I've seen some topics of panda boards (that use the same processor) with the same symptons when bootloader was lost...
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
freemini said:
Yes I did use fast boot successfully before. I just don't see how it could corrupt the bootloader by simply restarting in it.. It doesn't make sense to me at all.
Click to expand...
Click to collapse
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
familyguy59 said:
Well, I have this thought: You last used fastboot (With success), you maybe flashed a ROM, opr something.
You then restartet the phone, whilst it was still updating some internal files.
Maybe, if you did do that (willingly or not), you buggered the bootloader, like that...
Click to expand...
Click to collapse
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
freemini said:
It was not syncing or downloading anything, I've been using CM9 for about an hour before choosing reboot to bootloader. The only thing the phone was doing was charging.. I just don't understand how a simple command to reboot in bootloader can screw it up, it just doesn't make sense to me. It seems it's in a loop, Device Manager shows OMAP4440 refreshing about every second. It eventually disappears but if I plug it back in it does it again. I'm guessing the bootloader is gone
Click to expand...
Click to collapse
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
familyguy59 said:
Well, it may be gone, but OMAP normally means, that there is no firmware present...
This happened to me, whilst flashing a new firmware, onto the Wave, of my Dad...
I'll have a look, inside my Devman, and see, what I can find ^^
Click to expand...
Click to collapse
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
freemini said:
Thanks but I sent it back now. I hope they take it, there's a chance they won't obviously.. Let me know if you find anything, but it seemed hopeless to me.
Click to expand...
Click to collapse
Well, I wish best of luck, in that matter!
I still think, it's an unwanted brick, though...
I've looked, but can't find anything, whilst the phone is booted in Android, so, I'll restart it in a minute, and then have a look ^^
Hello guys,
I've read more or less all threads I could find on the EMMC brickbug, /data partitions locked, phone doesn't boot et cetara but I've got a problem that seems to match all of those problems fairly well, but not really 100%.
I've got a GSM Galaxy Nexus and after the upgrade to 4.1.2 my telephone suddenly started to bootloop (stock, but I did a factory reset). Eventually I pulled the battery and in desperation I decided to download the original Google Factory Image and flash it using ./flash-all.sh and that was when all hell broke lose. I got the fastboot usb_read error and got screen tearing. After that, I couldn't even boot the phone anymore, it was completely dead, so I started to research all over Google.
After a good while of searching and installing Windows on a separate partition I eventually used the GT-9250 OMAPFlash and behold, the phone booted again (well, just to the bootloader, but still, it at least turned on). I decided to do flash-all again and got the very same problem again. Phone locked up, had to do OMAPFlash and next time I started the phone was warning that recovery et cetara is missing, but I still got to the bootloader.
I started to get creative and instead of trying to flash again I fastboot-booted into a temporary Clockwork Recovery (fastboot boot recovery-clockwork.img) as to gain ADB access, which also worked fine. I tried to wipe everything and that worked evenly well (well, except /data which is inaccessible according to clockwork).
So I tried to flash yet again, failed, and did the entire procedure again to get to Clockwork. I started to research on flash memory problems and found something about the EMMC brickbug after which I ran all the tests (dd if=/dev/block/mmcblk0 of=/dev/null and the scripts that are kindly provided here on the forum). Result: No brick found but I didn't quite trust the findings despite running all tests several times. I decided to move the system, cache and data partitions using parted a little further back on the flash. That worked well, no lockup or anything. But the second I try to flash (both using the shell with flash_image or fastboot) the phone will immediately lock up the second the first bytes are written.
What is weird with this is that writing change to the partition table isn't causing locks, formatting /system or /cache doesn't cause locks, only the writing to the partitions will cause an instant lock.
So, my question is: Do you guys recognize this problem (i.e. no brickbug evident during testing, no problems writing partitions or wiping but instant lock when doing either flash_image or fastboot flash)?
Any tips are greatly appreciated!
Can you relock bootloader?
Sent from my i9250
bk201doesntexist said:
Can you relock bootloader?
Sent from my i9250
Click to expand...
Click to collapse
fastboot oem lock and fastboot oem unlock work fine.
there's a possibility that the device is still under warranty, relock/return it.
sent from my i9250
bk201doesntexist said:
there's a possibility that the device is still under warranty, relock/return it.
sent from my i9250
Click to expand...
Click to collapse
Hehe, alright. Was kind of expecting that answer when you asked whether or not I can lock it, but yes. I have 3 weeks left on the warranty.
That aside I am really curious on whether this IS the EMMC brick, a variation of it, or if I am just unlucky that I ran into a regular hardware defect a day after the 4.1.2 update.
Danie1 said:
Hehe, alright. Was kind of expecting that answer when you asked whether or not I can lock it, but yes. I have 3 weeks left on the warranty.
That aside I am really curious on whether this IS the EMMC brick, a variation of it, or if I am just unlucky that I ran into a regular hardware defect a day after the 4.1.2 update.
Click to expand...
Click to collapse
actually, i asked because i'm almost 99% sure you're not facing emmc corruption.
A couple of ideas: tried other computer/usb port/usb cable? Checked usb port on the phone for dust, damage?
Thing is, omapflash doesnt detect corrupt emmc.
sent from my i9250
bk201doesntexist said:
actually, i asked because i'm almost 99% sure you're not facing emmc corruption.
A couple of ideas: tried other computer/usb port/usb cable? Checked usb port on the phone for dust, damage?
Thing is, omapflash doesnt detect corrupt emmc.
sent from my i9250
Click to expand...
Click to collapse
Yeah, I did test if there was something wrong with the USB connection. Even tried with a different computer and different cables. Same thing. Anyway, I packed it up and will return it to the store, let's see what they will find.
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link
Okay, first of all, I would like to mention that I'm new at all of this.
I brought this phone 2 years ago and 2 months ago I decided I was going to root it. So I switched to CyanogenMod 11 M4 and did everything that was required i.e., unlocking bootloader and flashing a recovery and all that.
Just 2 days ago my phone showed an update available to CyanogenMod 11 M5. So I downloaded it and then the phone took me to my recovery. There I made a backup and flashed the M5.zip file that was downloaded. But when I rebooted my system a popup came saying com.process.phone has stopped unexpectedly. I pressed OK but it was persistent. I had no idea what to do so I booted into recovery and wiped data and then performed a restore of my previous backup that I had taken. Half-way through the backup the phone just switched off and then restarted with the traditional HTC logo and then it switched off again and restarted again and this process kept looping.
I loaded my bootloader and connected the phone via fastboot to my computer and erased the cache and flashed the recovery again. Then wehn I restored it started working normally as it did before.
But the battery was around 20% at that time so I left it to charge overnight. When I woke up the next day it was insanely hot and the LED was constantly red but it wouldnt wake up. So I loaded into recovery to restore it again but it kept on saying "Error mounting /system!"
And then after a few tries it switched off. Now it won't wake up again. Even the LED seems dead.
Has anyone of you ever encountered a similar issue? Any help would be appreciated. I've tried all the button combinations that are recognized by the device but nothing seems to work.
dead battery
i guess its because of corrupt or dead battery
try giving external power or replace battery and try
further you could even try other options like booting cwm
flashing last kernel image found
jhakjhuk1853 said:
i guess its because of corrupt or dead battery
try giving external power or replace battery and try
further you could even try other options like booting cwm
flashing last kernel image found
Click to expand...
Click to collapse
Booting CWM or flashing the last kernel image aren't an option because the device doesn't switch on at all. I cannot access the bootloader.
try changing battery
try changing battery by buying new battery and connecting
or remove battery and charge it with external source i guess u must have heard of jump starting battery
kartikeym309 said:
Booting CWM or flashing the last kernel image aren't an option because the device doesn't switch on at all. I cannot access the bootloader.
Click to expand...
Click to collapse
kartikeym309 said:
Okay, first of all, I would like to mention that I'm new at all of this.
I brought this phone 2 years ago and 2 months ago I decided I was going to root it. So I switched to CyanogenMod 11 M4 and did everything that was required i.e., unlocking bootloader and flashing a recovery and all that.
Just 2 days ago my phone showed an update available to CyanogenMod 11 M5. So I downloaded it and then the phone took me to my recovery. There I made a backup and flashed the M5.zip file that was downloaded. But when I rebooted my system a popup came saying com.process.phone has stopped unexpectedly. I pressed OK but it was persistent. I had no idea what to do so I booted into recovery and wiped data and then performed a restore of my previous backup that I had taken. Half-way through the backup the phone just switched off and then restarted with the traditional HTC logo and then it switched off again and restarted again and this process kept looping.
I loaded my bootloader and connected the phone via fastboot to my computer and erased the cache and flashed the recovery again. Then wehn I restored it started working normally as it did before.
But the battery was around 20% at that time so I left it to charge overnight. When I woke up the next day it was insanely hot and the LED was constantly red but it wouldnt wake up. So I loaded into recovery to restore it again but it kept on saying "Error mounting /system!"
And then after a few tries it switched off. Now it won't wake up again. Even the LED seems dead.
Has anyone of you ever encountered a similar issue? Any help would be appreciated. I've tried all the button combinations that are recognized by the device but nothing seems to work.
Click to expand...
Click to collapse
After the phone updated did u extract and flash boot.img from M5.zip?
convict_moody said:
After the phone updated did u extract and flash boot.img from M5.zip?
Click to expand...
Click to collapse
No, I didn't do that because when I switched over from a CM11 Nightly to CM11 Snapshot M4 I didn't extract and flash the boot image even then and everything was working perfectly. So, I didn't think I would need to.
kartikeym309 said:
No, I didn't do that because when I switched over from a CM11 Nightly to CM11 Snapshot M4 I didn't extract and flash the boot image even then and everything was working perfectly. So, I didn't think I would need to.
Click to expand...
Click to collapse
U should give it a try, since some CM updates triggers the kernel itself so boot.img should be flashed again.
convict_moody said:
U should give it a try, since some CM updates triggers the kernel itself so boot.img should be flashed again.
Click to expand...
Click to collapse
That is the problem. I can't. When I connect it to the PC it just never shoes up and I have no luck getting into the bootloader. Do you know of any reliable unbricking guides? I'm guessing my phone is possibly bricked.
kartikeym309 said:
That is the problem. I can't. When I connect it to the PC it just never shoes up and I have no luck getting into the bootloader. Do you know of any reliable unbricking guides? I'm guessing my phone is possibly bricked.
Click to expand...
Click to collapse
Check the guides in here:
HTC One X Reference
convict_moody said:
Check the guides in here:
HTC One X Reference
Click to expand...
Click to collapse
Nah, nothing is suitable. There are guides on how not to brick your device but nothing to unbrick it. :|
Thanks anyways. It's appreciated.
Another bricked HOX apparently. There seem to be loads of these on the internet. In my case, it can't have to do with custom roms or rooting since I never messed around with stuff like that. I even opened the HOX and checked all cables etc. There is no part that looks damaged or otherwise suspicious.
What can we do? How can we at least get access to the data in the internal memory?
Don't know if this will help, but it might be that it hasn't actually charged properly over night and has drained itself to death.
Try plugging into PC and get to fast boot.
Fastboot = Volume Down + Power Button
Then make a batch file out of this:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
Click to expand...
Click to collapse
Then run the Batch File
Credit to Floepie for writing the .bat
Wilks3y said:
Don't know if this will help, but it might be that it hasn't actually charged properly over night and has drained itself to death.
Try plugging into PC and get to fast boot.
Fastboot = Volume Down + Power Button
Then make a batch file out of this:
Then run the Batch File
Credit to Floepie for writing the .bat
Click to expand...
Click to collapse
Unfortunately, there's no way this could help. because the HOX is literally dead. There is not even a charging indication when plugged into a PC or the wall charger. And thus it's not recognised by the PC and fastboot won't find it.
I'm something of a noob here, so I appreciate your patience and help.
My wife's Nexus 5x applied the latest update for 7.1.1 and her phone then fell victim to the dreaded bootloop. I was able to get through this guide to apply a rescue OTA: https://drive.google.com/file/d/0Bz6x7k-VkpUJam5Mc1hKa09PVGc/view (sorry, I can't post the hyperlink to an external site since I'm so new here, lol).
All of the steps completed down to step 21, when I tried reboot after the update - it rebooted then went right back into the boot loop.
The OTA I used was for Bullhead N4F26O (which is the one I should use based on the guide). I also tried N4F26I, but the OTA failed and it went straight to the bootloop.
I ran out the battery, charged it a bit, and tried again, but ran into the same problem (update completes, reboot, bootloop starts again).
Does anyone else have any more ideas on what I can try? At this point all I really care to do is recover any photos I can from the device (my wife forgot to setup image backup on her phone and USB debugging was never turned on). Google Fi already offered to send out a replacement, so I'm not worried about getting the device fully functional again.
Thanks for your help.
Not sure exactly what happened, but the phone was plugged into my PC stuck in the bootloop. I unplugged the phone and it booted...it didn't have much of a charge, so I quickly turned on developer mode, USB debugging, and some other option I noticed about allowing unlocking of the OEM bootloader. Also, I checked the backup settings for her photos and they were set to backup automatically, but just on a secondary Google account.
If anyone has any ideas for resurrecting the phone, I'd appreciate it (for the sake of learning if nothing else). Thanks
LeChuck5000 said:
Not sure exactly what happened, but the phone was plugged into my PC stuck in the bootloop. I unplugged the phone and it booted...it didn't have much of a charge, so I quickly turned on developer mode, USB debugging, and some other option I noticed about allowing unlocking of the OEM bootloader. Also, I checked the backup settings for her photos and they were set to backup automatically, but just on a secondary Google account.
If anyone has any ideas for resurrecting the phone, I'd appreciate it (for the sake of learning if nothing else). Thanks
Click to expand...
Click to collapse
Exactly how did you apply the update? Over the phone or fastboot? Can you get to fastboot mode (bootloader)? Unlocking the bootloader will erase everything.
Tulsadiver said:
Exactly how did you apply the update? Over the phone or fastboot? Can you get to fastboot mode (bootloader)? Unlocking the bootloader will erase everything.
Click to expand...
Click to collapse
I can get it into fastboot, and can sometimes get it into recovery (but not consistently...it often just goes into the bootloop when I try to launch recovery).
To apply the update I just followed the guide I linked to in my OP. First, installed the adb, fastboot, & usb drivers on my computer. I then put the phone into recovery, and wiped the partition cache. I then connected the phone to my PC, picked Apply update from ADB on the phone, and ran adb sideload c:\MyNexus\bullhead-ota-n4f26i-06953aec.zip from the command line on my PC.
Heat the EMMC Chip. I tried every type of flashing to fix it, nothing did. Then I did what a lot of people said and tried to heat the emmc chip and it worked perfectly. It's been working fine for the past 3 days and I hope it stays that way.
Arrivale said:
Heat the EMMC Chip. I tried every type of flashing to fix it, nothing did. Then I did what a lot of people said and tried to heat the emmc chip and it worked perfectly. It's been working fine for the past 3 days and I hope it stays that way.
Click to expand...
Click to collapse
You stick it in the oven? Use a heat gun? How hot/long?
tallgrasshawk said:
You stick it in the oven? Use a heat gun? How hot/long?
Click to expand...
Click to collapse
Heat gun, I put aluminum foil at the end of the gun to make it narrow and easy to target just the emmc. Keep it on for around 30sec x 3
How else?
Arrivale said:
Heat gun, I put aluminum foil at the end of the gun to make it narrow and easy to target just the emmc. Keep it on for around 30sec x 3
Click to expand...
Click to collapse
I don't have a heat gun, how else can I heat it? Also, excuse my ignorance, I'm new to phone thing since my Nexus 5x went into bootloop last week I've learned a lot, fast. Where exactly is the EMMC? How else can I heat it? I'm desperate to get this phone working as I just went overseas and Nexus won't send a replacement here
My attempt at the Rescue OTA fails in step 19, I can't get the device state to be "unlocked" does anyone know how to unlock it when the phone is in bootloop? (So all I really have access to is command prompt, which says I can't unlock the oem) HELP!?!