OK guys so I started a new thread because the situation has changed with my problems. OK so I originally posted a thread about the accelerometer, I thought maybe restoring to stock might fix it. So I flashed the zv7 on the irc with the lgnpst on the irc. And every time its the same problem, the phone hangs at the 4glte section of the stock boot animation. Also i cannot get into the boot loader. I can still get into download mode though. Any ideas?
Sent from my Galaxy Nexus using xda app-developers app
Look here. http://forum.xda-developers.com/showthread.php?p=38887359
It should get you set
Sent from my LG-LS970 using xda premium
Just factory reset in stock recovery.
What is Optimus Prime's full name?
Optimus G. Prime
I can't get into recovery either using adb or hardware keys
Sent from my Galaxy Nexus using xda app-developers app
nvm I got it thanks guys. its running but restoring to stock still didn't fix the problems back to a doner phone I guess.
Chyrio said:
OK guys so I started a new thread because the situation has changed with my problems. OK so I originally posted a thread about the accelerometer, I thought maybe restoring to stock might fix it. So I flashed the zv7 on the irc with the lgnpst on the irc. And every time its the same problem, the phone hangs at the 4glte section of the stock boot animation. Also i cannot get into the boot loader. I can still get into download mode though. Any ideas?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Not sure if it's the same issue or not, but it sounds fairly close. When I powered off the LG logo would show with screen grayed not black as a power out should be.
Try this. Unplug the phone and hit the power button until the phone goes black, not gray, black, hold the power button for say a count of 40 or longer. This should stop the LG logo cycling. leave the phone alone for about twenty minutes. Do not plug it in to a power sources as that will start the cycling again.
After about twenty minutes hit the power button once.
I'm not saying this will resolve your issue, but I had the issue you're describing, and tried everything I could think of to get into recovery. Like you I was able to get into download mode, which made me certain I should be able to get into recovery with the right set of button pushes. Tried it for hours before resigning myself to LGNPST, when I did the above though it booted right up with no problem.
Discovered completely by accident. I was in the process of starting the LGNPST process receiving some help on IRC when I I hit the power button after the delay off and it all worked out. Didn't have to go through the process. The help I got was the twenty minute delay. The folks over on IRC deserve a lot of credit for the help they give btw.
The problem started after I flashed the ZVB rooted rom zip. Since then If I try to power down while it's plugged in, or not, the same thing happens. Rebooting is not problematic, but powering down is. It's not a big deal now though since the fix is easy enough for me.
Give it a try can't hurt.
same issues...
I had same issues, I flashed back to original root back from which i started from, then flashed the stock rooted zip, then the radio update, even though ur told to do the opposite way, the reason i did was cause the radio update flashes the new bootloader, just make sure after u flash the radio update wipe the cache and dalvick casche also. I did that and it booted right away,
Related
Ok, so here is my story:
I rooted way back in July right after I got my Evo, so I started on Android 2.1. I flashed and used OMJ's ROM for quite a while until I discovered Cyanogen mod, which I switched to after trying OMJ's 2.2 ROM.
I used CM6 for a long time, eventually flashing some nightly builds, culminating in nightly build number 140. At some point in this process, I started having real trouble with bootlooping CONSTANTLY (and I couldn't even make a nandroid backup because it would reboot inside the backup process). I eventually got it to stop bootlooping after many many reboots and wipes (full wipe, cache wipe, dalvik wipe) and restarts and got CM to boot.
I just now flashed CM6.1 and started getting constant bootloops again. I assumed it was a problem with CM, so I decided eff it, I'm going with a different ROM and downloaded Calkulin's EViO 1.5 rom to try, but it can't boot either.
I can get to the android screen, which displays no signal, then it reboots. I can't get out of this cycle. When I was on CM, I had issues with starting up - I had to hold down the power button quickly and press airplane mode, then it would reboot again, but it would come all the way up. Then once it was fully booted I could disable airplane mode and it would stay online. After that point, I just decided never to reboot the phone, but this is a huge problem that I can't figure out how to fix.
I have tried wiping using Clockwork and Amon Ra, but neither makes a difference.
Any help would be GREATLY appreciated. Thanks!!!
it reboots while making nandroid? So even if you hold vol down + power and go to the recovery from there it is rebooting?
xHausx said:
it reboots while making nandroid? So even if you hold vol down + power and go to the recovery from there it is rebooting?
Click to expand...
Click to collapse
Correct, I hold volume down + power to get into recovery, then choose nandroid and backup, then while it is creating a nandroid backup, it reboots.
Does anyone have any ideas? At this point, I have no clue what to do, and I can't boot into any ROM.
If you Google it you'll see its an incredibly common problem not just with those of us who have modded our phones but those with stock roms who have never done so it happened to me when I originally flashed cm6 to my phone as well but it eventually fixed itself if you can get it to boot try factory reset it may help
Sent from my PC36100 using XDA App
hackulous said:
If you Google it you'll see its an incredibly common problem not just with those of us who have modded our phones but those with stock roms who have never done so it happened to me when I originally flashed cm6 to my phone as well but it eventually fixed itself if you can get it to boot try factory reset it may help
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Factory reset just wipes your data using your recovery doesn't it? Either way, I've tried that, and no dice.
I mean, I guess at the very least I could try to bring the phone into Sprint... is there a shipped RUU I can flash so they can look at it?
edit: found the latest RUU (http://forum.xda-developers.com/showthread.php?p=8474707)
I'm gonna try this and see what happens.
http://www.google.com/m/url?client=...IQFjAA&usg=AFQjCNHQ2016xLF_DLz7uVoilk8Hm1EsRg
Sent from my PC36100 using XDA App
same problem. no solution. i am now fully bricked, aka i reboot before i can pull down lockscreen (rom changes, unroot, nothing works) return before it gets so bad you cant unroot.
No good man I hope you got insurance
Sent from my PC36100 using XDA App
Ewe, thats no good. I would use the ruu but Do Not Use The Newest One. You will lose root and the new 3.30 people are having trouble rooting
Sent from my PC36100 using XDA App
same thing happening to me. Stuck in bootloop now, started out as just a random reboot that would boot than reboot than hold for a while. Right now im completely stuck in bootloop =(.
Is there a way to put a stock rom on my phone with just booting to recovery?
These sound like hardware issues but if your recovery is working fine then it may be something else. Did you try the RUU while in the recovery?
Just don't use the newest one
Sent from my PC36100 using XDA App
dkdude36 said:
same problem. no solution. i am now fully bricked, aka i reboot before i can pull down lockscreen (rom changes, unroot, nothing works) return before it gets so bad you cant unroot.
Click to expand...
Click to collapse
I was finally able to get to a point where I could get it to boot - here is what I did.
I wiped everything using amon ra's recovery, then flashed the latest cyanogen mod from here: http://mirror.teamdouche.net/get/supersonic/update-cm-6.1.0-RC1-Supersonic-signed.zip, then when it booted, it would get constant bootloops, but it would get to the home screen for a few seconds each time.
You have to click through the intro menus reaaaallly freakin fast so you see the desktop with the live wallpaper. DON'T sign into a google account. It will probably bootloop again, and if it doesn't, quickly hold down the power button and select airplane mode. If it reboots again, it will power up completely successfully in airplane mode. Then make sure you're in an area of good signal and disable airplane mode until you have 3G, and then sign into a google account. If it starts bootlooping again, quickly hold the power button and press airplane mode - you can always boot successfully in airplane mode for some reason...
xHausx said:
These sound like hardware issues but if your recovery is working fine then it may be something else. Did you try the RUU while in the recovery?
Just don't use the newest one
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
It could be hardware related, but I'm not 100% sure at this point...
The reboots seem to be correlated with signal strength. If I have 1 bar of signal (in CM, so not cell signal), it will reboot before it gets to 3G.
Also any flash on a website reboots the phone for some reason. I don't know if that's common or not.
So my S2 is stuck constantly rebooting before I can attempt to get the phone into download mode or back to CWM.
The best luck I've had so far is to rather consistently press the power button while the phone is trying to boot. This keeps the phone booting for the longest, and I've even made it into CWM and ODIN doing so. However anytime I stop tapping the power button, the phone will reboot.
At one point I did do a super wipe of the cache and OS, I just haven't been able to flash the phone back to stock. The same behavior occurs with a charged battery, a battery-less phone plugged into the wall, and a phone plugged into the wall with the battery in it.
I've opened up my phone to take a look at the power button placement. The plastic case is not pressing in the button, and when I press it in myself I hear a distinct click noise as normal. I've even pried away the case with no luck.
What next steps do I have? I do not have insurance with t-mobile or warranty of the phone. I do have the knowledge to solder if needed. Are there more options for me to try, to fix this issue?
EDIT: So this time I was able to get into ODIN, after letting the phone sit and do nothing for a week. No idea why it works now. I flashed back to stock. Will give it a day or two and then flash back to custom.
If you can get a computer to recognize the phone it can be fixed using adb or another method.
Sent from my SGH-T989 using Tapatalk
So now it's in ODIN and staying there! I don't know why, it never did before.
Should following this be all I need?
http://forum.xda-developers.com/showthread.php?t=1513359
My only confusion is, what is "This will restore to T-Mobile 2.3.6 ULKL1." ? I only know I have the T-Mobile T989 version.
ralewis said:
So now it's in ODIN and staying there! I don't know why, it never did before.
Should following this be all I need?
http://forum.xda-developers.com/showthread.php?t=1513359
My only confusion is, what is "This will restore to T-Mobile 2.3.6 ULKL1." ? I only know I have the T-Mobile T989 version.
Click to expand...
Click to collapse
what i know for sure is that it should be T-Mobile uvlh1 which im 98% sure is the standard base band when i got my phone
but other than that is your phone already rooted?
also when you go in CWM what does it say?
Does it just freeze?
So I did go through with the link and flashed back to stock. Everything seems to be working great now. I did nothing to the phone and it stopped acting up.
What used to happen is the device would act like I was holding the power button constantly. It would simply reboot, but never freeze. It felt Software independent, which worries me that it'll come back.
The problem started slowly, where my phone would reboot on its own here and there. Gradually getting worse. This happened after applying some OTA updates for CyanogenMod10. Though it didn't happen immediately after applying the updates.
Hi, guys!
This is nearly my first time here reporting a problem, but I'm really stuck and I'm pretty sure that you'll be able to help me.
I have a GSM Galaxy Nexus i9250 which was on Stock Rom without Root (even though it was rooted and back to normal afterwards). Last night I left my phone plugged to the wall, charging. Let me tell you that the phone was on, too. The following day (I mean, this morning) when I went to pick up the cellphone, I found that it was in an infinite bootloop. Google logo, X logo, Google logo, X logo... And so on.
The first thing I thought about, was changing the battery, considering the fact that I had been using the extended one. Despite from that, It didn't work.
After that, my second idea was to flash the factory image again, but the issue wasn't solved. At first, I was able to actually see my phone working on (I was ver close to choose the language!) but the reboot came up again.
Last but not least, my last chance was to try to solve the problem via Recovery Mode. When I tried to go down that road, a tiny Android appeared on my screen, with its chest opened and a red triangle over him.
I ran out of ideas, but surely you'll have come great tips or another magic trick regarding this problem.
Thanks a lot in advance!
When you see android with triangle, press power and volume + to see recovery menu, wipe data and cache
Sent from my Galaxy Nexus using xda premium
samersh72 said:
When you see android with triangle, press power and volume + to see recovery menu, wipe data and cache
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Hey, thanks for your help!
Unfortunately, that didn't do the trick... =/
Whenever I try to wipe cache, the process begins and the phone resets again... And again... And again.
Could it be a HW issue?
Thanks!
Hello, I have the same problem, which appeared about week ago. I was going sleep when my phone froze. I plugged charger then (I was too tired to wait) and next morning my phone was in infinite loop. After reflashing stock firmware all was good but only for a while... When I replaced all the content I had, bootloops appeared sometimes ending infinite and sometimes just only 1 or 2. By now I don't know what to do. Firstly I thought that it was maybe because of root access for some crappy app, but even without root it still happens. I even tried not to restore backup from Play Store, but with no luck.
Is there any way to see some log and discover what is causing trouble?
Any help is really needed!
Sideload .zip if youre unlocked or do a factory reset
Sent from my Transformer Infinity
mr.gonzoo said:
Is there any way to see some log and discover what is causing trouble?
Any help is really needed!
Click to expand...
Click to collapse
Hi
If you turn on usb debugging in the developer options, you can then do adb logcat while it's bootlooping.
That will at least show you what's failing. Also adb shell dmesg gives you the kernel messages.
Logcat is pretty easy to follow once you get over the information overload you will see it looping after a short while
Edit: obviously if it's bootlooping you can't get into developer option. You can access adb via recovery. You should be able to "adb shell cat /proc/last_kmesg" . Doing that after failed boot attempt will give you the kernel output from the last boot. Theres ways to enable debugging for booting from recovery I'll double check it when I get in
Hope that helps a little
Sent from my HTC Sensation Z710e using xda premium from my HTC Sensation Z710e using xda premium
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.
Ok so, I have been running Hyperdrive RLS16 for quite sometime now with no issues, going on approx 6 months now. Love the rom. Just today out of nowhere my phone started timing out. By timing out I mean, screen started going black as if I was closing it when I was in the middle of using it. This proceeded to happen for at least 15 minutes meanwhile it was constantly rebooting itself as well. After about 15 mins of reboots and screen timeouts, it got to where the phone would not stay on. it would boot up, then when i started using it it would reboot again. So after a battery pull, sd card pull and sim card pull I restarted it and since it seems to be doing ok for the moment. I immediately backed up my rom in clockword mod recovery through rom manager, backed up all my apps and created an update.zip in titanium backup. I downloaded the stockmod slim rom t999 4.3 v3 and the uvuemj4 modem that it requires for data and was gunna try and flash it and everytime i boot into recovery and try to select an option to pick, it randomly starts selecting things and jumping all over the place and then reboots. wont let me wipe data factory reset, or wipe dalvick or cache. wont even let me choose the rom or modem to flash. I tried to update my version of clockwork mod, and nothing. Tried to download goo manager and try twrp but it wont go into twrp it stays in clockwork mod and does the same. Im so confused on what to do to fix this and would like to flash a new rom to see if it will fix my screen timeouts and reboots but I cant get recovery to cooperate in order to do that. Can anyone help me? PLEASE!!!! I thought maybe if i try clockwork mod touch that it may fix the problem, but even if i download it how can i flash it if recovery isint cooperating?:crying::crying::crying:
kbeezy2686 said:
Ok so, I have been running Hyperdrive RLS16 for quite sometime now with no issues, going on approx 6 months now. Love the rom. Just today out of nowhere my phone started timing out. By timing out I mean, screen started going black as if I was closing it when I was in the middle of using it. This proceeded to happen for at least 15 minutes meanwhile it was constantly rebooting itself as well. After about 15 mins of reboots and screen timeouts, it got to where the phone would not stay on. it would boot up, then when i started using it it would reboot again. So after a battery pull, sd card pull and sim card pull I restarted it and since it seems to be doing ok for the moment. I immediately backed up my rom in clockword mod recovery through rom manager, backed up all my apps and created an update.zip in titanium backup. I downloaded the stockmod slim rom t999 4.3 v3 and the uvuemj4 modem that it requires for data and was gunna try and flash it and everytime i boot into recovery and try to select an option to pick, it randomly starts selecting things and jumping all over the place and then reboots. wont let me wipe data factory reset, or wipe dalvick or cache. wont even let me choose the rom or modem to flash. I tried to update my version of clockwork mod, and nothing. Tried to download goo manager and try twrp but it wont go into twrp it stays in clockwork mod and does the same. Im so confused on what to do to fix this and would like to flash a new rom to see if it will fix my screen timeouts and reboots but I cant get recovery to cooperate in order to do that. Can anyone help me? PLEASE!!!! I thought maybe if i try clockwork mod touch that it may fix the problem, but even if i download it how can i flash it if recovery isint cooperating?:crying::crying::crying:
Click to expand...
Click to collapse
It sounds like there would be a problem with your digitizer. Or motherboard. Either way it sounds expensive to fix.
Sent from my Galaxy NexusL using Tapatalk
The touch response is working fine though, and the buttons work fine. But it randomly scrolls all over the place in recovery and selects things on its own even when Im just holding it in my hand pressing nothing. I have the regular clockwork mod recovery not the touch installed. I have to scroll with the volume buttons and select with the power button. But even when im not pressing either it just goes in ghost mode and starts selecting stuff. Its crazy!! Is there a problem with my version of recovery? 6.0.4.3
jmcoffey said:
It sounds like there would be a problem with your digitizer. Or motherboard. Either way it sounds expensive to fix.
Sent from my Galaxy NexusL using Tapatalk
Click to expand...
Click to collapse
kbeezy2686 said:
The touch response is working fine though, and the buttons work fine. But it randomly scrolls all over the place in recovery and selects things on its own even when Im just holding it in my hand pressing nothing. I have the regular clockwork mod recovery not the touch installed. I have to scroll with the volume buttons and select with the power button. But even when im not pressing either it just goes in ghost mode and starts selecting stuff. Its crazy!! Is there a problem with my version of recovery? 6.0.4.3
Click to expand...
Click to collapse
I don't use cwm so I wouldn't know. But your didgitizer could still act like its working fully and still be broken. Idk man.
Sent from my Galaxy Nexus using Tapatalk
ok well thanks man for your help. Would the digitizer be causing the random reboots as well?
jmcoffey said:
I don't use cwm so I wouldn't know. But your didgitizer could still act like its working fully and still be broken. Idk man.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
kbeezy2686 said:
ok well thanks man for your help. Would the digitizer be causing the random reboots as well?
Click to expand...
Click to collapse
If it's malfunctioning is possible. But there's no telling.
Sent from my Galaxy Nexus using Tapatalk
Can you boot download mode? Odin flash stock firmware. If it continues then it may be a hardware problem.
i havent tried to do that. But i did do a factory reset from my settings instead of through recovery. I did lose quite a bit of stuff because it deleted my backups in titanium and etc but my recovery is working now. No more ghost mode selecting everything. But my phone is still doing the random reboots
DocHoliday77 said:
Can you boot download mode? Odin flash stock firmware. If it continues then it may be a hardware problem.
Click to expand...
Click to collapse
kbeezy2686 said:
i havent tried to do that. But i did do a factory reset from my settings instead of through recovery. I did lose quite a bit of stuff because it deleted my backups in titanium and etc but my recovery is working now. No more ghost mode selecting everything. But my phone is still doing the random reboots
Click to expand...
Click to collapse
Did you flash another ROM and its still rebooting?
Sent from my SGH-T999 using Tapatalk
kbeezy2686 said:
The touch response is working fine though, and the buttons work fine. But it randomly scrolls all over the place in recovery and selects things on its own even when Im just holding it in my hand pressing nothing. I have the regular clockwork mod recovery not the touch installed. I have to scroll with the volume buttons and select with the power button. But even when im not pressing either it just goes in ghost mode and starts selecting stuff. Its crazy!! Is there a problem with my version of recovery? 6.0.4.3
Click to expand...
Click to collapse
Earlier I too felt this type of auto touch in my other device and I figured out that this was happening due to some radio interference at some particular time and particular place which was near a radio station
Whenever I go away or that station time was over it will be working correctly
May be something like this happening just for your information to make sure
Sent from my SGH-T999 using Tapatalk