samsung galaxy nexus wont unlock - Samsung Galaxy Nexus

Hi I have this problem my samsung galaxy nexus wont unlock. The phone worked fine 10 minuts ago then clicked the power bottom to unlock but it just stays black screen
and i have to pull out the battery and turn it on aging and there is 75% battery left so that's not the problem

after a hard reboot with pulling out the battery, you still can't unlock your phone?

fine
after a battery pullout i will unlock fine but it's just thet some times theres is no response when i click the power bottum to get to the unlock screen and the only option is to pull out the battery

is your phone rooted? if so, go to cwm, backup, and flash a clean rom. Then if it works, try restoring from ur backup

Not rooted
The phone is not rooted and totaly like origina. I tried to root the phone but it dient worked beacuse the fastboot driver wuldent install so no change at the phone it think but culd it be that, that is causing the problem

same here
I had the same problem once three weeks ago. The Gal N would just not respond to the power button. I had to pull the battery AND the SIM card. It has never happened again since then.
All stock phone, no root, no unlocked bootloader

Sounds like 'sleep of death', there's a thread on it - eta here:
http://forum.xda-developers.com/showthread.php?t=1360880
It seemed to be some app stopping the phone waking up, for some ? lightflow, others ? juice defender. I stopped following the thread so I don't know if a definitive fix was found.
You could try a factory reset and see if that fixes it...

Related

Is it bricked? UnSolved AGAIN!

A strange thing happened and now I can't escape the bootloader screen. I lost my phone for a two days and when I found it it wouldn't come on. I connected it to a power cable and it immediately brought up the bootloader. The charge light won't come on but now the phone will power on without the power cable. Problem is it just brings up the bottloader and tries to install the rom image on the sd card. I put a new image on the card reinserted it and then allowed it to reflash. But it still just brings up the bootloader. Any advice?
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
orb3000 said:
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
Click to expand...
Click to collapse
Go into bootloader. Plug in usb and flash from your pc. Try if it helps.
Flash with Task 29 first, it may be that corrupted info is still on the rom when you reflash screwing up the loading of the new rom.
orb3000 said:
Try to flash another ROM but not from SD, remove SD and SIM and flash from your PC
Hope it helps,
Click to expand...
Click to collapse
Lennyz1988 said:
Go into bootloader. Plug in usb and flash from your pc. Try if it helps.
Click to expand...
Click to collapse
Reflashed from PC, reboot to bootloader behavior does not change.
ultramag69 said:
Flash with Task 29 first, it may be that corrupted info is still on the rom when you reflash screwing up the loading of the new rom.
Click to expand...
Click to collapse
Flashed Task 29, then reflashed Energy ROM 23569 MaxManila. ROM booted and began setup procedure. Completed setup procedure and there was joy in the land. Installed the SD card and copilot loaded. Turned off phone to reinstall SIM. Turned phone on and bootloader loaded. every attempt to reboot brought bootloader up. Removed SD card and soft reset bootloader came up with error message but all I could read was "RUUUBH" at the top and "...error code" at the end of one line and "...se try again" at the end of the next, the rest was overwritten over the bootloader text.
Removing the SD card, I reflashed the stock SPL, rebooted to bootloader, then reflashed Task 29 and attempted to flash stock ROM, but the computer would not recognize the phone anymore.
Rebooted the phone and replugged into PC computer recognized, reflashed Hard-SPL and then attempted to flash Core EVO ROM (which is when all the trouble started by the way) The ROM flashed and the phone commenced the setup routine.
Was able to setup email and apps and customization and everything was good, left phone in cradle overnight and phone was fully charged this am. Rebooted the phone just as a check and bootloader returned, subsequent reboots always return into bootloader.
What now?
cyberscribe said:
Reflashed from PC, reboot to bootloader behavior does not change.
Flashed Task 29, then reflashed Energy ROM 23569 MaxManila. ROM booted and began setup procedure. Completed setup procedure and there was joy in the land. Installed the SD card and copilot loaded. Turned off phone to reinstall SIM. Turned phone on and bootloader loaded. every attempt to reboot brought bootloader up. Removed SD card and soft reset bootloader came up with error message but all I could read was "RUUUBH" at the top and "...error code" at the end of one line and "...se try again" at the end of the next, the rest was overwritten over the bootloader text.
Removing the SD card, I reflashed the stock SPL, rebooted to bootloader, then reflashed Task 29 and attempted to flash stock ROM, but the computer would not recognize the phone anymore.
Rebooted the phone and replugged into PC computer recognized, reflashed Hard-SPL and then attempted to flash Core EVO ROM (which is when all the trouble started by the way) The ROM flashed and the phone commenced the setup routine.
Was able to setup email and apps and customization and everything was good, left phone in cradle overnight and phone was fully charged this am. Rebooted the phone just as a check and bootloader returned, subsequent reboots always return into bootloader.
What now?
Click to expand...
Click to collapse
reflashed task 29, then reflashed stock ROM, still enters bootloader. note that it says serial on the bottom and that changes to USB most of the time when I plug it in. Also please note that when I remove the battery to power down and replace it and then plug it in it powers up all by itself (without me pushing the power button). This has been the method of rebooting that has been going on, this last time however, after removing the battery and plugging it in the charge light came on (seems to be a good sign). Pressing the power button caused the phone to boot to ROM image, but I'm afraid that rebooting it will result in the bootloader loop. I'll update after it finishes loading Winmo 6.1
this is certainly strange, could it be something with the SPL, i would look into that next if this doesnt help
cyberscribe said:
reflashed task 29, then reflashed stock ROM, still enters bootloader. note that it says serial on the bottom and that changes to USB most of the time when I plug it in. Also please note that when I remove the battery to power down and replace it and then plug it in it powers up all by itself (without me pushing the power button). This has been the method of rebooting that has been going on, this last time however, after removing the battery and plugging it in the charge light came on (seems to be a good sign). Pressing the power button caused the phone to boot to ROM image, but I'm afraid that rebooting it will result in the bootloader loop. I'll update after it finishes loading Winmo 6.1
Click to expand...
Click to collapse
I think you either have a bad battery or a bad TP 2. Try replacing the battery first. You can get a cheap external charger off ebay if you phone doesn't charge.
stevedebi said:
I think you either have a bad battery or a bad TP 2. Try replacing the battery first. You can get a cheap external charger off ebay if you phone doesn't charge.
Click to expand...
Click to collapse
Yeah, leaning heavily on the battery theory myself (although that could be wishful thinking), so I ordered a new OEM one this AM. OK here is the update. WinMo6.1 completed setup, activesync synced up my contacts, did not load copilot (since 4 out of 6 times the crash happened after I reinstalled copilot). Rebooted using the power button, rebooted to winmo.
Rebooted 4 times manually, each time it rebooted to winmo just fine.
Executed hard reset and aborted setup then reflashed task 29
Flashed Energy Rom MaxManila, allowed setup to complete, loaded copilot, and synced with activesync. Everything has been fine for 8 hours. No forced reboots, no lockups. Please note I have maintained battery charge above 50%.
Thanks for the suggestions and keep your fingers crossed.
cyberscribe said:
Yeah, leaning heavily on the battery theory myself (although that could be wishful thinking), so I ordered a new OEM one this AM. OK here is the update. WinMo6.1 completed setup, activesync synced up my contacts, did not load copilot (since 4 out of 6 times the crash happened after I reinstalled copilot). Rebooted using the power button, rebooted to winmo.
Rebooted 4 times manually, each time it rebooted to winmo just fine.
Executed hard reset and aborted setup then reflashed task 29
Flashed Energy Rom MaxManila, allowed setup to complete, loaded copilot, and synced with activesync. Everything has been fine for 8 hours. No forced reboots, no lockups. Please note I have maintained battery charge above 50%.
Thanks for the suggestions and keep your fingers crossed.
Click to expand...
Click to collapse
Fixed! Stable as a rock
cyberscribe said:
Fixed! Stable as a rock
Click to expand...
Click to collapse
Premature, OK I've been rocking just fine and bamm out of the blue the problem reemerged. OK I say to self no biggie MUST be the battery and the new just came in the mail today so I say self change battery, no help. Bootloader loop here again. Help someone please!
cyberscribe said:
Premature, OK I've been rocking just fine and bamm out of the blue the problem reemerged. OK I say to self no biggie MUST be the battery and the new just came in the mail today so I say self change battery, no help. Bootloader loop here again. Help someone please!
Click to expand...
Click to collapse
task 29 got me to the rom splash screen
cyberscribe said:
task 29 got me to the rom splash screen
Click to expand...
Click to collapse
reflash ROM from PC not SD. Reflashing after that from SD works. Hope I don't have to do this every time I change a battery!
I think I may be having the same or a similar issue as you cyberscribe. All of a sudden, I am getting restarted into the bootloader too.
I was using an older NRG 2.1 ROM (April-ish) and had to pull the battery after it froze up. Nothing new, it happens. The new part is that it would only restart into the bootloader screen. I thought it might be the older ROM, so I Task 29'ed and flashed NRG's newest 2.1 June 2nd ROM.
Successful boot and ROM setup while connected to USB. Unplugged USB, restarted phone, BOOTLOADER.
Plugged in USB, successful boot.
Unplugged USB, BOOTLOADER.
Plugged in wall outlet, successful boot.
Unplugged wall outlet, BOOTLOADER.
Obviously, I can conclude that there is an issue with trying to boot on battery power, or at least while not connected to a power source.
Anyone ever have this happen? Or have any ideas why this would be happening? I really don't want to have to find a power source every time I need to restart my phone, haha. I am still trying to troubleshoot further and will update if I find anything else worthwhile.
Also last night I tried restarting while plugged into car adapter, which as expected booted fine every time.
However, this morning I just restarted on battery power and it booted fine also. Nothing changed from last night to this posting. Honestly, I am completely at a loss as to why I am getting restarted into the boot loader seemingly at random. I thought I had it nailed down with the power source, but now that apparently is not the issue.
cyberscribe, are you still having issues? Anyone else ever have this problem? Any thoughts on a cause or solution? Or anything to help troubleshoot?
After the bootloader first pops up, there is a very quick screen that flashes, "Loading.... No image file", then goes back to the bootloader screen.
I have to discount my earlier theory that it will always boot when connected to any power source. Now it will only boot when connected via USB to the PC.
Looks like I am going to have to re-flash the stock ROM and then stock SPL and see if this solves the issue. Then, if not, I guess a warranty claim is in my near future.
I really wish we could have gotten some replies from smarter people than myself in this thread. haha
Finally flashed back everything to stock (SPL, radio, ROM) and still having the bootloader issue, looks like it is going to be a warranty claim after all.
Sounds more like a memory issue if it can't find the image file. If you both got your Rhodiums from the same carrier it could be a bad batch of phones...
Same issue on my tilt 2 just cropped up today. If I am reading the above correctly it sounds like 2 tilts and a t-mob rhodium having the issue, so different carriers. =/
Soft reset the handset and set it down, picked it back up and it was in bootloader. All attempts to get it out of bootloader (reflashing from sd, pc etc.) seem to complete just fine, but upon reboot dump into bootloader. May be a different problem than OP as I havent had any success in getting a boot after reflash.
Not sure if I am having the same problem, when I try to turn on it just comes up with the Touch pro 2 screen with the red text in the bottom left hand corner, I am using an energy Rom again from about April, I have tried re flashing but pc wont recognise/find phone, Wha acn be done?

[Q] HELP!! New stock nexus ui crashed, stuck at boot animation

Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
This is the hspa version.
svntsvn said:
Stock galaxy nexus, ui force closed. Powered off. Can get into recovery mode to attempt to reinstall stock rom. It shows a droid with an opened chest, with a red triangle above it when I try to go to recovery mode from the odin screen.
Anyone else have this issue? Is there a way to flash using a mac? I have limited access to a pc.
Thanks all.
Click to expand...
Click to collapse
The android icon you're referring to sounds like the stock recovery. In order to flash a ROM (even stock) from recovery mode, you'll need to load a custom recovery. This requires the device to be unlocked.
Not very often a stock setup needs to be restored. Generally, with the stock setup, only the /data partition is wiped (revert to factory default) and the issues are cleared. Not sure why a stock setup would need to be restore.
If you're still going to pursue reloading the system, without access to the normal android mode, the best route will be using fastboot. This can be done on a mac and the fastboot commands should be the same.
Hope that helps get a start!
This happened me earlier. I was able to factory reset it, which, unfortunately really annoyed me because I hadn't saved a backup..
Before the "Google" logo shows up, press and hold the power button and the volume up and down buttons.
Then go into recovery mode using the volume buttons.
When it reboots, you get that Droid with the hazard sign (which I know you're at, but just for the sake of others who need help) all you have to do is hold down the power button and WHILE it's held, press the volume up or down button and move to "Factory Reset". When you hold down the power button and press the volume rocker, a little menu will appear. It should only take a few minutes then.
Hope this helps. Apparently this is a WiFi issue. I'll definitely be keeping backups as of now..
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
svntsvn said:
I left it off, plugged it back in for a couple of hours and it booted right up. Strange.
I'm wondering if it had anything to do with juice defender and its settings that take effect at a lower battery level? Its the only thing I can come up with. Never had a stock phone's ui force quit and not reboot. The battery was definitely up to 25% given the time it was initially charging, but maybe it was still interfering.
Well, now that she's running, time to get root, recovery, rom and rejoice.
Thanks for the replies, very much appreciated.
Click to expand...
Click to collapse
I had the exact same problem happen last night with UI crashing and then the getting stuck at the boot animation. I was desperately searching online, looking to find a solution that didn't involve rebooting to factory setting and came across this post and did exactly what you did and it WORKED, very strange, I really wanna know what caused that!!!!
I've had the same problem with my Galaxy Nexus. I received it on December 21st, with stock 4.0.1 build. No root or unlock attempt at any time. On January 2nd I experienced this problems (UI process crash, screen not responding, reboot and stuck in boot animation).
The only solution was to do a factory reset and start over.
On January 10th same problem, same solution. Second factory reset.
I got the 4.0.2 OTA just two days after that. I thought that would resolve the problem. The phone seemed more stable, with less FC's and no trace of the UI crash. Indeed it lasted long...
Exactly until January 24th when I picked up the phone and seemed in the sleep of dead. Removed the battery, restarted the phone... and stuck in the boot animation.
Do you have any advice? Should I return the phone? Aside from those specific problems I am quite happy with the SGN and Android 4 in general. And I use it quite a lot (I have a very long train commute) without other problems.
Again...
It happened again!!
I don't know what to do anymore, this is not a usable phone when I have to reinstall and reconfigure every 3 weeks.
I may have found the problem
Well, not me exactly, but this bug report seems to fit the problem and the charging workaround. Seems to be a problem the file used to store the battery stats and draw the charge graph.
It also fits my usage (I try not to charge it up until 100%).
I can't post links to the forum, the issue is id number 24518 which you can find in code.google.com/p/android/

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!

[Q]Rogers Galaxy S3 constantly restarting even in recovery/download mode

So tonight out of the blue, my Rogers Galaxy S3 restarted itself. This isn't totally unusual, as sometimes this will happen once or twice a day, but never has it been too bad.
First off, I've been running Cyanogenmod 10.0, and again, has been relatively problem free. The first major issue I had was a week or so ago when I woke up to my phone having seemingly restored it's default settings on its own. Apps and all my other data were intact, but widgets, app settings, etc, were all cleared.
Now tonight, my phone can rarely boot into CM, and when it does, the power menu will appear shortly thereafter before restarting itself once again. If the phone is plugged in, I can't get anything other than the charge indicator to come on the screen for more than a second. The phone also does this when trying to boot into recovery mode or download mode.
I'm at a total loss as to what to do here, so I'm going to be leaving the phone off with the battery out over night. Appreciate any feedback in the meantime.
Also having a similar problem: phone boots up, will barely enter the bootloader/TWRP/boot animation for hyperdrive ROM. Also with rogers. I believe it might be SDS but I need to re install the stock firmware and can barely boot into the bootloader without the phone dying (battery is charged though). Any help greatly appreciated!
EDIT: managed to boot up for long enough to install "eMMC check" and apparently I have a 'sane chip'.
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
There have been issues with the power button getting stuck. Maybe you have that issue?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Well, after pulling most of my hair out, that does seem to be the issue. Would explain why the power menu would come up the few times it did manage to boot. I managed to get it working for a while, but the button seems to be really delicate since picking my phone up and barely touching it reset it again.
I guess now I need a solution to the power button sticking, but at least it doesn't seem to be SDS.
Okay, that makes sense. When I leave the phone completely stable it's fine.
However, I have tried unrooting and reinstalling stock firmware. However, my system status in bootloader is still custom, when I boot up the rom I still have superuser installed. I tried installing two different stock firmwares for Rogers and the same problem. Any help would be great, I really want to send this in for warranty ASAP.
EDIT: After using ODIN to install stock rom, I still had Superuser. I installed SuperSU and then preformed it'sfull unroot. After that i cleared data and cache from stock recovery and the phone is now at original status and seems to not be randomly rebooting/dying. Weird.

[Q] Gnex stuck in bootloader after using gnex toolkit to unlock

Hi guys, i have a problem with my gnex D:. what has happened is i have downloaded the gnex root toolkit and tried to unlock my phone, then my gnex turned off while the program said it was restarting the phone into bootloader and then poof my phone has a black screen and nothing happens. then after this my phone is now in a state where if i turn it on it will vibrate and show the google logo like normal but after that it has a black screen and well.... nothing and the only way to turn the phone back on is to pull out the battery make sure the charger isn't plugged in and then put the battery back in the phone and either boot up the phone so it'll do the soft brick thing with the google screen or boot into bootloader where to my knowledge nothing can be done to fix the problem. someone please help cause i just got it back from waiting 3 weeks for repairs then coming home and capoot it's dead :'(
EDIT: Sorry forgot to mention it is a samsung galaxy nexus running jellybean 4.3 JWR66Y GSM
EDIT 2: problem resolved, turns out it was just a simple corrupted boot.img file

Categories

Resources