Develop Bugs

Device strange issue will not stop giving problems!

This is a list of events that I have gone through today. I received a new charger because the old one I had became defective & was charging my phone up & then it would go back down to 0% & then shut off & it would end up in a problem where the phone would not turn on unless I pulled out the battery while the AC was in & then it was able to charge but still it would turn on, on its own to drain the battery when off & this was very frustrating. The charger I have now works but the device acts strange over the last few months doing a task29 & flashing the first ROM after would make that ROM not work & then I had to flash a totally different ROM to make it work. I was using Android & it had died a few times & also I experienced the same thing I did when it would charge up & go back down to 0%. please read below:
I got my new charger today & at 62% of charge I decided to flash to a custom ROM via mem card again well the ROM was a success but when pulling battery out to restart it didnt want to work. So I went to flash again in bootloader by memory card it shut off on me in the middle & restarted into bootloader again & shut off again right away. I did a task29 it worked got it out of bootloader & now the orange led flashes off & on when its off & now ive gotten that to stop. What exactly is wrong with this device?
it was @ 73% and finally setup a ROM NRGY however it ended up shutting off on its self & going into a power boot loop constantly restarting until that ROM can no longer start & now its stuck on the boot screen w/ its info.
I flashed the stock SPL on USB now im going to try to flash the carriers ROM back.
Stock SPL = Successful!
2nd Touch Pro 2 ROM Version Flash = Successful!
Its working for now. Battery is @ 80%
AHH! After charging to 100% idk what it did but when I went into the other room to check out its all possessed.
I have a black screen w/ white text that says:
The device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source.
Press Volume Up to reset your device or press any other button to cancel.
This operation will delete all your personal data and restore the device to its factory default settings.
IDK how this happened.
When I hit any key it didnt do anything it was stuck until I did a battery pull. Then I restarted the device it was stuck at the boot screen w/ its red info. It erased the entire ROM. Then I tried to do recover mode & it did nothing. I tried to flash the stock ROM again & no results & then again & still no results. I think its now not accepting the ROM at all since from: in the ROM update utility is blank.
Now it decides to get past the boot screen but then it malfunctions again & restarts itself & it tries to setup a 2nd time then after it does & its on sense home for a couple of mins it reboots twice & now its stuck on the boot screen again.

Things that I can think of.
- Isn't your batterie just broken? You will break your batteries when you deplete them completely. Maybe try a new batterie, because you said that you let it die for a few times. It could be that this is causing your problems.
- Did you flash true usb when you were in the bootloader? Give that a try, because I believe that the customruu performs some sort of checks. Maybe this is nonsens, but you can try it.

The battery was fully charged & it was working better than before.
I reflashed the Stock SPL to flash the carriers ROM back & that worked but at anytime it just rebooted for whatever reason to make it so the ROM was unusable at any time I would reboot it would decide to actually go past it seldom. I experienced that at one point oddly it went into setup n it did it again after a while its just acting strange.

If you're back to stock SPL and stock ROM, can't you just send it back for a warranty replacement ?

IDK how old it is. I bought it brand new from ebay.

Viper Matrix Wireless said:
IDK how old it is. I bought it brand new from ebay.
Click to expand...
Click to collapse
No warranty bro...
You can try but no warranty 9/10 times.
What ROM are you using? I used to have that issue with my betas.
It wld destroy itself after softreset and I would have to reflash.
Try to flash, turn off right after it boots, turn on and see how that works for ya.

Rep had told me I could get it replaced & they know I bought from ebay. But I havent called them on this yet.
It doesnt work. It usually doesnt go past the boot screen. Flashing does nothing to help it. Whenever it feels like it it may have to stay on for a few mins to go into setup but most of the time it will stay there & reboot, reboot, reboot, reboot each time its a different # of times & it will reset itself at anytime. Ive even had bootloader shut off on me & restart itself during flashing its a pain. I had another issue I didnt mention my device on any custom ROM when I had 0.85 olinex SPL the device would just freeze & not respond every time. Now this is a different situation. I am back of SPL 0.87 which is the default. I flashed the entire carrier ROM which 0.79 was rewritten w/ 0.87 & that was successful but its still rebooting & causing fatal problems including the black screen w/ white text.
UPDATE: I just walked into the kitchen. Somehow the device turned on by itself & now its sitting on the sense home screen. I know its not fixed but idk why it would turn itself on.

Moved as not ROM Development.

Try flashing task 29 1st... Might be because when you flash remnants of the older OS are still there causing trouble. Remember though, you need to have Hard SPLed it 1st....

I got so frustrated I just got done calling T-Mobile Tech Support & they are going to ship me a replacement.

ultramag69 said:
Try flashing task 29 1st... Might be because when you flash remnants of the older OS are still there causing trouble. Remember though, you need to have Hard SPLed it 1st....
Click to expand...
Click to collapse
I thought I would reply to you.
This is what started my problems is when I did a task 29 my device was acting funny afterwards. I did it again about a month later cuz I flashed way too much & it kept getting worse. But Task29 didnt help this time its what caused me to have to flash 2 different ROMs cuz the first one I flash after doesnt work.

I received the battery & it didnt do anything.
I'm still waiting on the replacement to come.

[Q] Please help!! My Pro 2 keeps rebooting ..!

Dear all,
I flashed the ROM for my HTC Touch Pro 2 and installed a new one. the new ROM worked well for 2 days, until the night I charged my HTC on the laptop. It keeps rebooting and cannot load the system.
It can enter the color screen by pressing VOL - and Power, and I can still flash new ROM via both microSD card and ActiveSync under the color screen.
However, it still reboots as it enters the "Windows Mobile" screen.
I have tried hard reset and Task29 to wipe it before flashing ROM but both of them did not work.
I have tried different ROMs and I even successfully made a gold card in order to repair it, but it still reboots when loading the system when entering the screen "Windows Mobile" .
Does anyone know what's wrong with my phone ? I am so confused and thinking it is a problem with the hardware.
THX..!

I believe this is what is called a "Boot loop". I ran into this problem once and it was because the phone wasn't fully charged. Turn the phone off and plug it into the wall charger and charge it fully. Then try again. This worked for me, but I can't say for sure if it will work for you.

doublen1 said:
I believe this is what is called a "Boot loop". I ran into this problem once and it was because the phone wasn't fully charged. Turn the phone off and plug it into the wall charger and charge it fully. Then try again. This worked for me, but I can't say for sure if it will work for you.
Click to expand...
Click to collapse
Thank you doublen1, I plugged it on the wall socket and see whether it works or not tomorrow...

It does not work for me, but thank you anyway, haha！

Sorry, I tried. Maybe someone else will know.

[Q] Defy bricked in weird fashion, help!

I'll be as brief as I can! Been using a app from the Market called Friendcaster on my rooted Defy running a pays ROM(I cannot remember which one, but it was a early Froyo, been using it for months). Noticed phone running hot after Friendcaster updated, and got a memory warning, turned out Friendcaster was constantly syncing and filled phones memory. Went to delete app, saw a fix, so installed that. Restarted phone, soon started syncing constantly then, and when ever I went into contacts phone locked up. Deleted app, rebooted, and phone went into a boot loop. Went to recovery, cleared phone storage. Phone refused to boot. Tried flashing SKTJRD-3.4.2.74.sbf flash it got to 100%, but never went to complete, even after leaving a few hours.
Phone now won't respond, won't go into recovery, only gets white LED when you connect USB, RSD lite does not see phone. Not sure if the McGuyver hack will help, the battery gets hot if you put phone on charge, and tried a fully charged battery from a visitors phone and still with no response, I understand you only need to do this if battery is flat and you cannot charge phone.
I've had a good search around on here, and on Google but can't find anything that seems to help, frustrated, I might be a new n00b, but this is the first time I haven't been able to solve a problem with a bit of Googling ARGH! Plus my phone doesn't work.
Hope you guys can help, if not what's the chance of Moto/Voda UK swapping out/repairing phone if I send it in?

If you have a new full battery, Can you put Defy into Bootloader mode?
If it cant, it should be realy brick

You should try this thread...
http://forum.xda-developers.com/showthread.php?t=1206708

Try to :
Uninstall RDS and the drivers;
Reboot PC;
Reinstall newer dirvers and rds (the 4.9 version);
Reboot PC;
Connect Defy with USB, wait 1 minute, if not recognized try to press power button and wait 1 min. If not recognized yet, try click on Config-->DeviceID and try both options.
If not recognized yet... try another pc, try another full battery... if this doesn't work there's nothing left to do.
The McGyver trick is dangerous! Don't charge your battery with this method more than 15 minutes!

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

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'.

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..

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
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And an image from USBDeview:
(The instance ID that is chopped off: USB\VID_0451&PID_D010\6&1f916cd7&0&7)
At this point I'm still dead in the water

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.

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 .

Garoun said:
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 .
Click to expand...
Click to collapse
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.

mskip said:
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.
Click to expand...
Click to collapse
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)
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.

wow - I'm definitely curious as to what happend here. Could it have been defective hardware?

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

Garoun said:
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.
Click to expand...
Click to collapse
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.

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 ...

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

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.

Firerouge said:
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.
Click to expand...
Click to collapse
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)

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.

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....

adesos said:
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....
Click to expand...
Click to collapse
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.

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???

adesos said:
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???
Click to expand...
Click to collapse
You need to HOLD the volume up and down buttons then press the power button to get into fastboot mode.
MArk.

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?

Galaxy nexus keeps rebooting

I have a stock GN, not rooted yet. Today my phone automatically shut off and now it starts back up, google logo shows up and all those colors come on for couple of seconds and then the phone reboots itself.
I can press both volume up+volume down + power button and get into a menu which gives me the options of Start, Restart bootloader, recovery mode, and power off. I choose recovery mode but then it goes on to an android sign with exclamation mark. After that I can't seem to get anywhere. I have tried volume up +power, volume down+power, and volume up+down+power but nothing seems to work. It just keeps on rebooting it self.
Any solutions to this problem??

There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)

....

FredFS456 said:
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
Click to expand...
Click to collapse
So, I did the above method and after flashing the factory stock rom it won't start up anymore. It doesn't respond to anything at all. It seems I've bricked it
Is there any way to unrbick it now? I'm assuming I can't send it in for warranty either now if it's semi bricked. Unless it's been completely bricked which means there is still a chance of getting a replacement phone.

I have the same prob on rooted SGN
This morning I switched off the airplane mode to be available, system crashed and restarted. And then still the same again - booting / android logo / restart again.. /./. I am using Android Revolution HD 2.1.5, for last month with no problems.
I tried to boot into recovery, then wipe the cache and reflash rom and radio from sd, it is still the same. I can see all the files on my int. sd with no probs.
Please help.

I'm thinking it might be a hardware issue, but I'll wait for another member's opinion before confirming.

Solved!!!
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.

630263 said:
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
Click to expand...
Click to collapse
Was your phone rooted or bootloader unlocked before the problem occurred?
Anyways I've sent in my phone for warranty, hopefully samsung will fix it.

So my phone company called me today and apparently Samsung told them that it's corrosion(?) problem. When I asked exactly what does that mean they said it's moisture damage or physical damage that probably caused it. But I'm confused how could my phone possibly get moisture damage inside an otter box. I know how delegate these devices are and I know how to take care of them.
Anyhow it'll be $90 to fix it. I had no other option so I asked them to go ahead with the repairs. So frustrated with Samsung to be honest. I never dropped my phone once, never had any water damage, phone was always inside the defender case. And I still have to pay them for fixing my phone even though it's not my fault.

That's quite worrying, I just started having boot loop problems today. I've had the phone since Feb 29th and not had a problem with it yet, but today it started boot looping. I went into recovery and did a factory reset, was alright for a couple of hours then it crashed, started bootlooping again. Running stock 4.0.2 unrooted, I'm wondering if flashing 4.0.4 might help.

I'm in the same boat.... unrooting stock 4.0.1 firmware - canadian version from Negri.
April 23rd my phone crashed and started boot looping. Google logo - reboot - Google logo - reboot
Factory reset worked. I installed less apps than I had before figuring perhaps an app was corrupting something.
Yesterday - it happened again. Phone crashed. Boot loop. Factory Reset worked. Installed even fewer apps.
We'll see what happens this time around. I am hoping it is just a software thing. Hoping 4.0.4 gets pushed soon too.....

I've been having the same issue, plus sometimes my home screen it would lock up and wouldn't let me do anything, so I did a battery pull and it would boot loop for a half hour.
After the 3rd time I just took it to my Verizon wireless store, and showed them the situation and they couldn't figure it out, so their sending me a replacement, which I'm not looking forward too, don't want a semi-used phone....
Via Galaxy Nexus [LTE]

Rebooting Issue Solved.
I was also a troubled Samsung Galaxy Nexus user and my phone kept restarting more than half a dozen times everyday. Most of the times when I switched between two or more applications, or when it was simply idle on my desk.
However, I found a solution (at least in my case). All I did was root my phone, install cwm recovery, and flash a custom rom after wiping cache and factory resetting the phone, It's been about 5 to 6 hours now since I flashed the custom rom and I haven't had a single reboot or hang since.
Others who face this problem, please give it a shot, who knows? You might save your Galaxy Nexus instead of sending it back to get a replacement or spend some money on it for repairs which aren't even required in the first place.

I also had this problem unrooted. I had to give it to Samsung for the warranty
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz

I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.

2stardiver said:
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
Click to expand...
Click to collapse
I could be wrong, but have you tried to clean the pin on the battery? Seems like battery and the phone isn't contracting too well
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

Little update, phone did continue rebooting with original 1750mAh battery also.
I did also reset with recovery mode, and after that it did also reboot one time.
like it uses all memory/cpu and when nothing to do reboot (like windows )
I also did flash stock rom with toolkit but no help.
I will test rooting phone and flash another rom, or is it useless ?

after using couple days, not yet rooted.
Phone works and wont reboot even in heavy stress. but sometimes it just reboots by own not a single program in task list.
might reboot right after previous reboot or take hours to reboot.
stupid phone

I have been done some research.
I did one more time reflash google stock with rootkit, and forgot lock phone, it was almost 3 hours by own in wifi, no reboots at all.
when I noticed that I forgot to lock it I rooted whole phone and installed paranoid android 2.13 with CWM.
Now Ive been using 2 hours without any reboot, installing software, setting things up and using apps.
I dont understand at all:silly:
edit: noup, yesterday evening one almost reboot, paranoid android did reset itself but didnt even reset uptime. so I didnt count that normal reboot.
but after wake up this morning, it did reboot once when I put in my pocket, another just lying on table, once activating bluetooth in my car.
going to send it back to seller.

I have a similar issue, although not quite the same. Last night my phone started boot looping - it managed to boot up to the lock screen, and I can use it for about a minute before it dies and then reboots. This continues again and again (I have to pull the battery to quit it).
I have stock JB on my GSM GN, but rooted with an unlocked bootloader / CWM. I restored my old CWM backup, and had the same issue. I also wiped the cache and the dalvik just to see if that helped, but I had the same issue. I then tried to do a factory reset in CWM, but after I did that the boot loop just got to the nexus logo and died, entering a new (slightly shorter) boot loop. I went back into recovery and reflashed my CWM backup, and that at least got me back to booting into android.
I can't understand what's going on - could it be a hardware issue if it will happily stay alive in recovery, but dies after 1-2mins of android?
Thanks for your help. If it is hardware then I hope I can reflash the stock recovery / bootloader and unroot through recovery... the phone doesn't stay on long enough to do it when it's booted into full android!