• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Q] Cannot get to fastboot, dreaded 'brick' possible

Search This thread

Garoun

Member
Dec 30, 2011
23
4
I used mskip's method to root my VZW Galaxy Nexus LTE: http://forum.xda-developers.com/showthread.php?t=1392310

Everything was working fine all night, so I don't think it was the root that did it, but I had just downloaded an app to test my LED and the moment I hit 'open' from the market the phone showed the colored spiral booting image which then froze.

At that point no buttons would work, so pulled the battery and attempted to reboot the phone into recovery mode since I had made all the proper backups.

Prior to the hard crash the phone was unlocked, properly rooted, CWM installed and working.

I've tried pulling the battery and SIM but nothing seems to bring it back to life. I was able to get some odd beeps when plugging the USB into my pc while connecting it to the phone but nothing would happen from that point. ADB devices and fastboot devices show nothing.

Any help or the dreaded 'bricked' word would be appreciated for the sake of learning and 'closure'.
 

joshnichols189

Senior Member
Jun 5, 2010
7,012
1,038
Chicago
Try leaving the battery out for a little bit, and maybe even charging it for a good 15-20 minutes.. strange as that sounds, it could help. I doubt you're bricked if all it did was crash during normal use, but you never know.

I would try leaving the battery out then charging a little.. maybe even reinstall your samsung drivers on your computer to make sure that isn't an issue..
 
  • Like
Reactions: Garoun

Garoun

Member
Dec 30, 2011
23
4
Thanks for the info steps I've performed since leaving the post and reading yours, in order of execution:

*** Last night before making post (adding more detail now that I can think) ***
Prior to the root I had the issue a lot of people had reported in that the phone was somewhat temperamental at which cords it would charge on but 'most' of my micro's worked fine. Other than that I could get to adb and the sdcard without any issues.

The full sequence of events leading up to this is as such:
- Made sure I was fully charged
- Performed the root as mentioned in the OP
- Booted into CWM first thing and made a backup
- Used TiBu to restore some of my market apps (user only, no system apps) from my old rooted Incredible
- Finished setting up the rest of my phone
- Installed ROM Manager to update CWM to the newest version
- Installed the rest of my normal apps, then booted up TiBu and backed up all apps and their settings (user only, no system apps)
- Played with my phone for the next few hours with a reboot here and there if I installed an app and it's widget didn't show up
- About an hour after that I installed "market.android.com/details?id=com.rageconsulting.android.lightflowlite"
- After it had installed I clicked open and phone immediately jumped to the booting graphic and froze with no button response at all
- Pulled battery and rebooted, it showed the google logo (with the lock at the bottom), made it past the boot screen, got to the lock screen and no buttons or swipe action would take me to home screen
- Pulled battery and attempted to get into fastboot/recovery to no avail
- Attempted to get it talking to my pc and outside of the battery out OMAP4440 device manager message gave up for the night
- Uninstalled PDAnet, Samsung drivers, then used USBDeview to ensure I got them all, rebooted, reinstalled the Samsung drivers (Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe), rebooted, attempted to plug in phone and same OMAP4440 message
- Tried pulling the SIM and battery for a few minutes with same results
- Left it on the charger overnight so I could get some rest (same time when I left the OP)

*** Starting this morning at 10AM ***
- Let the phone sit on the charger overnight with the battery in
> No change

- Pulled battery for 10-15min then put battery back in and attempted to fastboot
> No change

- With battery in, tried plugging it back into my pc
> No change or response from Device Manager

- With battery out, tried plugging it back into my pc
> I attempts to installed drivers but always fails, I've attached a picture of the device manager during this situation
OMAP4440_Device_Manager.jpg

And an image from USBDeview:
(The instance ID that is chopped off: USB\VID_0451&PID_D010\6&1f916cd7&0&7)
OMAP4440_USBDeview.jpg

At this point I'm still dead in the water
 
Last edited:

Garoun

Member
Dec 30, 2011
23
4
Ok, as a freak of nature I got to fastboot! I was doing a combination of trying to get the the OMAP driver to installed using samsung/pdanet drivers. A lot of plugging and unplugging with the battery out. Put the battery in one last time with the usb plugged in and finally got the oh so lovely 'vibrate' and fastboot loaded.

In the process of recovering to the original backup I made before the crash. Will let you know what happens from there.

I can get into the phone and restored my CWM backup from just before root, going to try flashing it back to stock and starting over after I give it time to charge fully.

Edit 11:53: Flashing the stock image back onto the phone and relocking the bootloader to see if the LED is still broken.

Edit 1:26: Phone is now locked and stock, trying to debug the LED since it use to come on while charging or if I was in a call. All it does now is one short blink and then nothing.

Edit 1:40: Looks like things are behaving again so back to root.
 
Last edited:

Garoun

Member
Dec 30, 2011
23
4
And back to the original spot I started at :(

When I tried to root, it got past unlocking, during the root I completed the steps to let it keep loading but then it went into a boot loop and kept jumping between the animation, vibrate, black google screen. After it did that a few times in went completely black and now back to no load at all (fastboot or recovery).

I've tried the battery pull and wait, but seems I'm back where I started :(. Ah the joys we put ourselves through out of the quest for knowledge :).
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,067
Norfolk
And back to the original spot I started at :(

When I tried to root, it got past unlocking, during the root I completed the steps to let it keep loading but then it went into a boot loop and kept jumping between the animation, vibrate, black google screen. After it did that a few times in went completely black and now back to no load at all (fastboot or recovery).

I've tried the battery pull and wait, but seems I'm back where I started :(. Ah the joys we put ourselves through out of the quest for knowledge :).
Did you use my ToolKit for the second root or another root method?

What model and build are you on?

I dont see how the root method could make your phone not load into fastboot or adb as it only boots (not flashes) an insecure boot image to then push the 2 files needed.

Are you back running again or still nothing? If you get the phone running again then flash back to stock and exchange the phone. Just tell them the phone goes dead now and again.

Mark.
 

Garoun

Member
Dec 30, 2011
23
4
Did you use my ToolKit for the second root or another root method?

What model and build are you on?

I dont see how the root method could make your phone not load into fastboot or adb as it only boots (not flashes) an insecure boot image to then push the 2 files needed.

Are you back running again or still nothing? If you get the phone running again then flash back to stock and exchange the phone. Just tell them the phone goes dead now and again.

Mark.

Method: Yep, I used the Toolkit for the second try after using it to return to stock and locked phone. All drivers were working correctly but the main difference between the 1st time and second I did the root before trying to flash the CWM onto the device.

Version: (this is a snapshot from system info before the first root but it was 4.0.2 LTE/CDMA)
Screenshot_2011-12-29-20-05-36.jpg

I honestly don't think it was the root that did it, since the phone was running stable for hours after the original root(including multiple reboots and charging). It wasn't until my LED Notification light started acting up that things went pear shaped, which started with Trillian then once I ran the led app that put the nail in the coffin. It was also having issues with recognizing most of my USB cables, only really had success with my included cord.

As from prior posts I somehow made it come back to life but could not achieve the same success with the 2nd SOD. Both times had the same case of seeing Device manager pop up the OMAP4440 pop up momentarily if no battery was installed, but not USB response at all by the PC if battery was in. The one time it worked I was in the middle of reinstalling PDAnet and the Device manager repeatedly tryed to reinstall the OMAP driver even though it failed every time but inserting the battery (while still connected) made the phone wake up.

I ended up biting the bullet and taking it back for warranty replacement. At least it was pretty much wiped clean (no titanium backups) at that point since I had just unlocked it. Lady up front said, "you broke it already", I responded with, "Well it was having issues charging on any cable other than what it came with so I didn't bother bring it in since I could get a charge, but after getting the rest of my apps installed I tried to open one and it went to that rainbow colored screen when you turn it on and froze. Tried pulling the battery but still wouldn't work". I simply answered the questions asked. Unfortunately, I'm going to hold off on rooting for now until I know my phone is completely stable since first one was having occasional oddities before I even touched the boot loader.

Considering I was only rooting and not doing any other customizations, only wanted to be able to backup/restore my apps and their data, my research made me think the SOD wasn't normal.

Am I correct in thinking that none of the actions made in ":applyroot" from the runme.bat should cause fastboot and/or ODIN to be unreachable if it fails at any point? Hell I don't even think a corrupt recovery should prevent it from at least making it to ODIN? I hadn't even gotten to the ":deleterecoveryrestore" step.
 

NPuter

Senior Member
Oct 28, 2010
288
22
wow - I'm definitely curious as to what happend here. Could it have been defective hardware?
 

Garoun

Member
Dec 30, 2011
23
4
I'm leaning heavily towards defective hardware. The way my led and usb port started acting seemed like I had a short or something. The fact that it tried to connect to my pc with the battery out has me beyond perplexed.

Had done a lot of reading and researching to try to understand all the possible pitfalls, but this one had me dumbfounded.

I'm curious to see the reply to the questions on my previous post. I'll gladly answer any questions I can if it'll help someone else in the future. :)

Sent from my Galaxy Nexus using XDA App
 
  • Like
Reactions: adesos

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,067
Norfolk
Am I correct in thinking that none of the actions made in ":applyroot" from the runme.bat should cause fastboot and/or ODIN to be unreachable if it fails at any point? Hell I don't even think a corrupt recovery should prevent it from at least making it to ODIN? I hadn't even gotten to the ":deleterecoveryrestore" step.
Nothing in the rooting procedure in my ToolKit would harm the system. First it boots (not flashes) an insecure boot image to gain temporary adb root access. 2 files are then pushed to the phone and permissions are set. After a reboot the only thing left on the phone is the 2 files (su and superuser.apk). These files have been used thousands of times to grant root for phones so there is nothing wrong with the way they work.

The Galaxy Nexus is pretty much unbrickable in that it should always be able to boot into fastboot mode as it it is totally outside the operating system and cannot be overwritten by flashing.

Dont be put off by your bad experience as im sure it was a very rare thing to happen :)

Mark.
 
  • Like
Reactions: lehoule and Garoun

adesos

Member
Mar 4, 2011
14
0
my god ....i have the same problem as you ...but now i can't find any omap4400 driver....and i don't what the timing to put battery back to the phone ...
 

Garoun

Member
Dec 30, 2011
23
4
I'm just letting the phone rest for a while to make sure it's fully stable. I'm sure it'll eventually get rooted again (incredible has been ripped for a while now), for three time being I'll just have to use adb to push/pull my important app data.

Ade, I don't believe there is an omap driver we have access to, since my research has turned up that it's essentially the chipset trying to initialize. I am probably wrong, but for now I believe only a provider/manufacturer has that access.

Sent from my Galaxy Nexus using XDA App
 

Firerouge

Senior Member
Jan 1, 2012
66
7
Literally the same thing happened to me to.


Phone was rooted 4.0.2 with CWM recovery installed.

Turned off my phone this morning after charging all night.

Came back an hour later and saw the white full battery icon on the screen. Tried to turn it on and would not turn on.

Tried going into fastboot to no avail.

When plugged into PC all I got was the OMAP thing under device manager.

Took the phone to Verizon, they got it to boot up to the boot logo after removing the battery and then putting the battery in while holding the power button. The phone crashed after booting past the boot logo, had it replaced.
 
Last edited:

Garoun

Member
Dec 30, 2011
23
4
Literally the same thing happened to me to.


Phone was rooted 4.0.2 with CWM recovery installed.

Turned off my phone this morning after charging all night.

Came back an hour later and saw the white full battery icon on the screen. Tried to turn it on and would not turn on.

Tried going into fastboot to no avail.

When plugged into PC all I got was the OMAP thing under device manager.

Took the phone to Verizon, they got it to boot up to the boot logo after removing the battery and then putting the battery in while holding the power button. The phone crashed after booting past the boot logo, had it replaced.

So based on 3 quick accounts of this issue I'm wondering if there is a critical flaw that only pops up after the bootloader is unlocked.

Adesos and Fire, did you two use mskip's toolkit or another method?

In my case, the only common factors between my two roots was unlocking the boot loader and getting through the initial root. On the 2nd root it hardlocked before I had renamed the recovery reset file or installed CWM.

Trying to figure out some common ground.

So mship knows exactly what got completed before the hardlock, these are the parts that got completed from the batch before the bootloop.

fastboot-windows.exe oem unlock
fastboot-windows.exe boot root\boot_LTE_ICL53F_insecure.img

(had an issue with needing to restart the program at this point since I had to reboot into Android and enable usb debugging, did not have this problem the first time)
adb-windows.exe root
adb-windows.exe remount
adb-windows.exe push root\su /system/bin
adb-windows.exe push root\Superuser.apk /system/app
adb-windows.exe shell chmod 06755 /system/bin/su
adb-windows.exe shell chmod 06755 /system/app/Superuser.apk

echo Completed. Now booting back to FastBoot Mode:
echo.
pause
(The moment I hit Enter after this to kick off the reboot is when I got stuck in a boot loop, and it finally hard locked after about 6 reboots since I didn't want to battery pull unless it never stopped)
adb-windows.exe reboot bootloader

Again, the first root worked fine until I tried to test the LED notification light that had started acting up.

Hunh, now I wish I had a backup battery so I could see if something got screwed up with the battery since the phone acted like it was shorted or something when the battery was installed. (fact that device manager popped up the omap only when battery pulled)
 

Firerouge

Senior Member
Jan 1, 2012
66
7
I did indeed use the toolkit.

The first time I did it I unlocked bootloader. Phone rebooted tweaked it a bit.

About an hour later launched the tool before rebooting the phone into fastboot, tried to run the root exploit, all steps failed though since the phone hadn't been in fastboot first. So I rebooted into fastboot and then ran the tool again successfully.

Root was applied, then deleted the recovery restore file, then put CWM recovery on it.

I never once booted to CWM recovery. The next day the phone stopped working.
 

adesos

Member
Mar 4, 2011
14
0
hi, did you get any idea to restore the dead phone???
13 days past away, and i'm only waiting to jtag flash a bootloader to my phone.....
1: i unlocked my bootlloader
2: i rooted my phone
3: fastboot flash recovery
and i'm very likely to know, how to get in the fastboot mode?
(1,with the battery in or out?
2, should i press any button when i plug the usb cable to phone?
3,or what esle i should do?)

thank you.....plz give me some answers....i hate to wait jtag info to flash my phone....it will be 1 month later or more....
 

Garoun

Member
Dec 30, 2011
23
4
hi, did you get any idea to restore the dead phone???
13 days past away, and i'm only waiting to jtag flash a bootloader to my phone.....
1: i unlocked my bootlloader
2: i rooted my phone
3: fastboot flash recovery
and i'm very likely to know, how to get in the fastboot mode?
(1,with the battery in or out?
2, should i press any button when i plug the usb cable to phone?
3,or what esle i should do?)

thank you.....plz give me some answers....i hate to wait jtag info to flash my phone....it will be 1 month later or more....

If the normal tests and attempts to get the phone at least booting, there had been mixed results of holding the power button only while putting the battery in, but the issue is honestly a toss up since I haven't heard of any other people with this problem.

I've been so busy at work I haven't bothered trying to root my phone again or track down more people with the same problem.

Your best bet may honestly be sending it in and take your chances.
 
Last edited:
  • Like
Reactions: adesos

adesos

Member
Mar 4, 2011
14
0
yeah i'm busy in my work too, so my reply is late........

thanks for your reply

you mean that....

you just put battery in ...... and hold the power button......and plug usb cable to computer so you get in the fastboot mode???
 

mskip

Retired Senior Moderator
Mar 20, 2008
12,328
16,067
Norfolk
yeah i'm busy in my work too, so my reply is late........

thanks for your reply

you mean that....

you just put battery in ...... and hold the power button......and plug usb cable to computer so you get in the fastboot mode???
You need to HOLD the volume up and down buttons then press the power button to get into fastboot mode.

MArk.
 

xenspidey

Senior Member
Aug 21, 2008
104
24
HELP!!

I have the exact same problem as stated before, however I don’t think it has anything to do with the rooting process. I unlocked and rooted the old fashion way weeks ago and have been running very stable since. However, yesterday I received my extended battery which has worked well and today I got a couple extra cables. I was charging both of my batteries with my new cable for 4-5 hours this morning at work. I was going to lunch and powered off my phone to switch out the batteries. Now my phone won’t turn on at all, with either battery. I have tried both batteries, with the OEM cable… nothing. If I have the battery out and attempt to plug into my PC I get the “looking for OMAP4400” pop up. I’ve tried every combination listed previously… has anyone got any new light to shed?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Am I correct in thinking that none of the actions made in ":applyroot" from the runme.bat should cause fastboot and/or ODIN to be unreachable if it fails at any point? Hell I don't even think a corrupt recovery should prevent it from at least making it to ODIN? I hadn't even gotten to the ":deleterecoveryrestore" step.
    Nothing in the rooting procedure in my ToolKit would harm the system. First it boots (not flashes) an insecure boot image to gain temporary adb root access. 2 files are then pushed to the phone and permissions are set. After a reboot the only thing left on the phone is the 2 files (su and superuser.apk). These files have been used thousands of times to grant root for phones so there is nothing wrong with the way they work.

    The Galaxy Nexus is pretty much unbrickable in that it should always be able to boot into fastboot mode as it it is totally outside the operating system and cannot be overwritten by flashing.

    Dont be put off by your bad experience as im sure it was a very rare thing to happen :)

    Mark.
    1
    Try leaving the battery out for a little bit, and maybe even charging it for a good 15-20 minutes.. strange as that sounds, it could help. I doubt you're bricked if all it did was crash during normal use, but you never know.

    I would try leaving the battery out then charging a little.. maybe even reinstall your samsung drivers on your computer to make sure that isn't an issue..
    1
    I'm leaning heavily towards defective hardware. The way my led and usb port started acting seemed like I had a short or something. The fact that it tried to connect to my pc with the battery out has me beyond perplexed.

    Had done a lot of reading and researching to try to understand all the possible pitfalls, but this one had me dumbfounded.

    I'm curious to see the reply to the questions on my previous post. I'll gladly answer any questions I can if it'll help someone else in the future. :)

    Sent from my Galaxy Nexus using XDA App
    1
    hi, did you get any idea to restore the dead phone???
    13 days past away, and i'm only waiting to jtag flash a bootloader to my phone.....
    1: i unlocked my bootlloader
    2: i rooted my phone
    3: fastboot flash recovery
    and i'm very likely to know, how to get in the fastboot mode?
    (1,with the battery in or out?
    2, should i press any button when i plug the usb cable to phone?
    3,or what esle i should do?)

    thank you.....plz give me some answers....i hate to wait jtag info to flash my phone....it will be 1 month later or more....

    If the normal tests and attempts to get the phone at least booting, there had been mixed results of holding the power button only while putting the battery in, but the issue is honestly a toss up since I haven't heard of any other people with this problem.

    I've been so busy at work I haven't bothered trying to root my phone again or track down more people with the same problem.

    Your best bet may honestly be sending it in and take your chances.