Good morning all. I must say, THANK YOU very much for all the hard work done here to make rooting my VZW LG Revo so painless.
This morning my newly rooted phone wouldn't boot. It did download the OTA yesterday before I rooted it but I delayed that OTA for 24hrs. The phone was off all night on the charger. I took it off the charge, held the power button to boot and felt the one haptic vibration and thought all was good, booting. Not. It stayed black and failed to respond to subsequent power on tries. Battery out then back in didn't work to revive it. On charger didn't bring up the charging screen either.
Shot in the dark, I tried the charger with the battery removed and saw the bottom control buttons light and turn off. After maybe 10 seconds, about five flashes, I took it back off the charger and put the battery back in. This time it started right up, no drama.
This is a newly rooted phone, but after it downloaded but did NOT install the Verizon OTA.
Yesterday, after seeing my phone asking to update to the latest Verizon OTA and having not yet rooted but planned to in order to prevent such an update, I selected to delay the OTA by 24 hours. Later I successfully performed the SingleOneClick procedure, rebooted, verified Superuser, installed RevoToolkit the latest ClockworkMod. Then came Titanium Backup with which I did a full system and app backup. Barnacle Tether was next on order. That's all I did with it yesterday, in case that matters.
My question is, is this related to the OTA and is there something I should/can set to prevent this from happening. Especially concerning to me is what happens in a few hours when the 24 hour timer is supposed to OTA. At the moment, all is well and my Revo is working.
Bait-Fish
Not sure about ur first question about the boot but concerning what will happen in 24 hours... if you have clockwork mod recovery installed then when it tries to do the ota your phone will reboot in clockwork unable to take the update. It will keep trying to update like once a day and keep rebooting you into clockwork. To fix this flash the revolt rom in the dev section which includes the new update from Verizon minus losing root.
Sent from my VS910 4G using XDA App
Thanks for the guidance. I will look into it right away.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Posting a follow-up to say thanks again for the tip. I went with the Revolt ROM. Goodbye OTA!
Awesome man. Not a problem. Glad it worked out for you bud.
Bait-Fish said:
Posting a follow-up to say thanks again for the tip. I went with the Revolt ROM. Goodbye OTA!
Click to expand...
Click to collapse
Sent from my VS910 4G using XDA App
I've had repeated problems with not being able to boot my Revolution. This has happened consistently no matter which ROM I've used. I've factory reset and tried Decrap and Revolt both. I can reboot my phone fine, but if I ever turn it off overnight, I go back to a blank screen in the morning.
It seems a number of non-root users have this problem.
https://www.youtube.com/watch?v=IOGM__SQB6Y
I'm not sure if having a low battery contributes to the problem, but I do know that Clockwork works better with a full battery.
Interesting. It's reassuring to know it's not just me. Hopefully it gets resolved quickly.
I am forgetting if mine had the buttons lit like his in the video or not. I was definitely still on the original stock ROM. Luckily it hasn't happened to me since.
Related
I have put Froyo on my phone early as many others have and there are a few bugs on it, so what I am wondering is when it officially comes out will there be "some" additional updates since it is already on my phone or will I have to reinstall it with the official version from the market? What I am wondering is just update any further updates from the market with the Froyo I have? or with the public release in the next couple weeks install that? does it matter? if this makes any sense what I am saying LOL
I have the exact same question in my mind. Remember the 2.1-update?
-------------------------------------
Sent via the XDA Tapatalk App
My wife and I both have the Nexus One. I decided to stay on CM 5.0.7 Test 3 until he gets the chance to work on his 2.2 rom, I'm in no hurry.
My wife wanted it on hers because she wouldn't allow me to root her phone.
After putting 2.2 on hers there is some pretty bad stability issues. Her phone has straight up frozen at least 8 times since yesterday requiring a battery pull.
When he phone isn't being a temperamental babby its great but when it starts to chug the whole house of cards comes crashing down.
Since I rooted mine I just make nandroid backups and restore from that so life is simple for me but with hers how do I restore back to total stock?
Do I reboot into the bootloader and at the screen where I would typically apply the update.zip just use the restore option or would the restore option in the phones settings work? I.e Factory Default.
While she is semi tech savvy I just don't have the time or patients to deal with her phone issues right now so I guess she'll just need to be on 2.1 until the official release.
[Update] Froyo May Have Been Launched Prematurely
http://phandroid.com/2010/05/24/froyo-may-have-been-launched-prematurely/
rensky said:
I have the exact same question in my mind. Remember the 2.1-update?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
sorry I am a newbie 2.2 is my first update that's why I am posting this to see if I didn't f*** up my phone or something. other than that it seems to be working fine with a few bugs here and there and 2 things updated today from the market, so am wondering leave it be or get rid of it and reinstall the official one? thnx for responses
Enndr said:
My wife and I both have the Nexus One. I decided to stay on CM 5.0.7 Test 3 until he gets the chance to work on his 2.2 rom, I'm in no hurry.
My wife wanted it on hers because she wouldn't allow me to root her phone.
After putting 2.2 on hers there is some pretty bad stability issues. Her phone has straight up frozen at least 8 times since yesterday requiring a battery pull.
When he phone isn't being a temperamental babby its great but when it starts to chug the whole house of cards comes crashing down.
Since I rooted mine I just make nandroid backups and restore from that so life is simple for me but with hers how do I restore back to total stock?
Do I reboot into the bootloader and at the screen where I would typically apply the update.zip just use the restore option or would the restore option in the phones settings work? I.e Factory Default.
While she is semi tech savvy I just don't have the time or patients to deal with her phone issues right now so I guess she'll just need to be on 2.1 until the official release.
Click to expand...
Click to collapse
From what I understand, if you want to go back to ERE27/EPB54, you would need to either restore a Nandroid image that has those ROM's or download an unsigned original ERE27/EPB54 image.
When you say battery pull, are you actually physically pulling the battery whe the phone freezes? I've read a couple of posts/articles where that might be harmful to the phone and so what's recommended instead is to perform a soft-reboot.
You can do so by holding down the power button + volume down key + trackball at the same time. If done so correctly, the phone will automatically reboot in a few seconds.
Enndr said:
but with hers how do I restore back to total stock?
Click to expand...
Click to collapse
No can do. No unlocked bootloader = no regression. You either unlock the bootloader or live with Froyo.
I would consider a factory reset though, as I have no stability problems what so ever.
Hey guys, I've got an odd problem and am hoping somebody out there can help me out.
I bought a nexus one a while ago and promptly rooted it and installed cyanogen's 5.0.6 mod. I followed the guide on XDA to the letter and had no problems at all. Cyanogen's mod was great and the trackball alert pro was amazing.
My brother saw my phone and after his jailbroken iPhone called it quits he bought one offline from www.google.com/phone. He asked me to unlock it and put cyanogen's mod on there.
I used the same files, that I did for my phone, and followed the same steps listed on the guide to the letter, just as I did for my own phone. I didn't change one thing in the process.
However, after booting past that lovely cyan colored x and getting into the phone, it would randomly reboot, and then get stuck at the solid X logo, forcing me to take out the battery. I would take it out, wait 30 seconds, put it back in, only to have it happen again.
I thought it was a wiping issue, so I redid everything to no avail. I even put everything back to stock, and tried once again doing everything I had done for my phone to no avail. I can't figure it out and it's frustrating me. All the files are the same that I used on my phone, nothing is different except the phone, yet whenever I install the Rom, it randomly reboots and gets stuck on the solid X logo.
So, as you can see I'm at a loss. I'm not sure why my phone works and his doesn't. FWIW his phone DOES NOT reboot when on stock everything, only when a custom ROM is on it. Also, I set my phone back to stock everything and re-rooted/flashed and have had no problem, yet when I do the same steps on his phone, random reboot/frozen.
Can anyone out there help?
Nobody?
SphericalPuma said:
Hey guys, I've got an odd problem and am hoping somebody out there can help me out.
I bought a nexus one a while ago and promptly rooted it and installed cyanogen's 5.0.6 mod. I followed the guide on XDA to the letter and had no problems at all. Cyanogen's mod was great and the trackball alert pro was amazing.
My brother saw my phone and after his jailbroken iPhone called it quits he bought one offline from www.google.com/phone. He asked me to unlock it and put cyanogen's mod on there.
I used the same files, that I did for my phone, and followed the same steps listed on the guide to the letter, just as I did for my own phone. I didn't change one thing in the process.
However, after booting past that lovely cyan colored x and getting into the phone, it would randomly reboot, and then get stuck at the solid X logo, forcing me to take out the battery. I would take it out, wait 30 seconds, put it back in, only to have it happen again.
I thought it was a wiping issue, so I redid everything to no avail. I even put everything back to stock, and tried once again doing everything I had done for my phone to no avail. I can't figure it out and it's frustrating me. All the files are the same that I used on my phone, nothing is different except the phone, yet whenever I install the Rom, it randomly reboots and gets stuck on the solid X logo.
So, as you can see I'm at a loss. I'm not sure why my phone works and his doesn't. FWIW his phone DOES NOT reboot when on stock everything, only when a custom ROM is on it. Also, I set my phone back to stock everything and re-rooted/flashed and have had no problem, yet when I do the same steps on his phone, random reboot/frozen.
Can anyone out there help?
Click to expand...
Click to collapse
I had the same issue with mine and a buddys N1... not sure exactly what to do but I wiped right before I put cyan on and the again right after and if started fine after that... wipe it was much as you do when you poo! lol worked for me! GOOOOD LUCK!
Thanks for the tip. When My brother gets off work i'll try it on his phone and let everybody know the results
-------------------------------------
Sent via the XDA Tapatalk App
zippa71385 said:
I had the same issue with mine and a buddys N1... not sure exactly what to do but I wiped right before I put cyan on and the again right after and if started fine after that... wipe it was much as you do when you poo! lol worked for me! GOOOOD LUCK!
Click to expand...
Click to collapse
Well I tried your suggestion with no luck. It rebotos and gets stuck at the X after about a minute inside the homescreen
Not sure if this discussion has already happened.
I have noticed twice since rooting my nook (with 2.12.25) that it has randomly restores back to 1.0.0 (or seemingly).
The first time it was just sitting beside me and it did one of its un-commanded restarts. I noticed that it was reloading the original 1.0.0 version. I lost everything and the nook was unresponsive after finishing. I followed all the hard reset rules and then upgraded to 1.0.1. I then autorooted again and reinstalled all apps.
Last night it did it again while I was using it. I was reading a book and then went to check email. I got an error message something like "invalid authorization" and that it was reloading the base software. I let it do its thing and go through its reboots. I also let it automatically update to 1.0.1 before I touched it. I re-registered it. Now when it loads it doesn't show the normal rooted nook boot screens. When I go into extras I see only the stock apps plus the additional ones that the auto-nooter loads (everything else gone). I tries to get me to log into LogicPD Zoom (Google) but it fails to load.
Has anyone else seems this?
Is there a way to re-load or fix the nook color install without having to go through the complete wipe process?
Once I fix is there some setting we can change to prevent it from happening again?
Thanks
After nootering the nook, I proceeded to load clockwork mod and made a backup of the OS. Now when it auto restores, I can reinstall the backup from clockwork mod by holding both Power and the Nook Key for five seconds when powering on.
Still don't seem to know how to stop the auto restoring though
Mine restarts too, has since I rooted it. Thankfully, there is no data loss, just an inconvenience. If there were a log being kept (like in other OSs), I could at least go there to find out what is crashing it.
Acts like a low memory restart, but that isn't what it is.
TJD
Wanted to add that mine does this also. It has happened 3 times in 4 weeks. Thank god for ClockWork it is not to big a deal now to restore. I wish someone could figure this out tho.
Mine actually randomly boots up (I'll have it off, then hear it start up a few hours later). Not sure it's related, but thought I'd mention it in case it turns out to be.
Sent from my PC36100 using XDA App
Mine used to restart everytime it went to sleep. Happens to alot of people. SetCPU and On Demand usually fixes it. There is like 2 or 3 of these threads in Q&A
straby187 said:
Mine used to restart everytime it went to sleep. Happens to alot of people. SetCPU and On Demand usually fixes it. There is like 2 or 3 of these threads in Q&A
Click to expand...
Click to collapse
Except they're talking about the system restoring itself, not rebooting.
It has to reboot to restore. Thought if you fix the reboot problem it would help maybe not... My bad
I'm autonooted on 1.0.0 and have never had an ota restore or update.
Sent from my Nook Color
Have you guys made sure to rename the otacerts file after rooting?
There are several active threads on this. In my case it was a faulty power button. I went ahead and exchanged the unit. Replacement is 1.01 and feels like the case is sturdier. Might be imagining that. Check my other posts on the subject. Good luck.
Sent from my NC using XDA app
This morning I woke up and my phone was working fine. I had 2 updates in the market and I hit update all. After that my phone rebooted and it does the Verizon LTE animation and the LG splash screen but it goes into a black screen. While it's in the black screen the phone vibrates and the battery heats up. I tried going into recovery but it did nothing.
Pull the battery fo a few and wait before a reboot?
http://www.youtube.com/watch?v=TGjBRAVZKW4&feature=youtube_gdata_player this is the issue that's happening.
Sent from my MB860 using XDA App
so you said you went in to recovery and it did nothing? So you couldn't even get recovery to load? and are you stock or rooted with clockworkmod recovery?
I can't even get it into recovery. I hold the volume keys and power buttons and it just does the boot up then black screens.
Sent from my MB860 using XDA App
Just hold down the volume down button, then hold down the power button also. Continue to hold both through the lg splash, then it should be into recovery.
Sent from my VS910 4G using XDA Premium App
isoutsider said:
This morning I woke up and my phone was working fine. I had 2 updates in the market and I hit update all. After that my phone rebooted and it does the Verizon LTE animation and the LG splash screen but it goes into a black screen. While it's in the black screen the phone vibrates and the battery heats up. I tried going into recovery but it did nothing.
Click to expand...
Click to collapse
I had the same thing happen to mine 20 days after I got it. I had to have it replaced under the warranty, which means they had to ship it next day air.
I've heard of a few other people with the same problem.
Finally able to get into recovery and wipe data but now phone starts up and its black screen with the status bar across the top. It's acting like it has no home launcher.
Unfortunately you are going to have to get a replacement from VZW. If you are within the 14 day period you can just swap it at the store. otherwise you have to go through the Warranty folks and make sure you have them ship it to you overnight.
isoutsider said:
Finally able to get into recovery and wipe data but now phone starts up and its black screen with the status bar across the top. It's acting like it has no home launcher.
Click to expand...
Click to collapse
Do you have Clockwork installed?
If so, this is an easy fix.
If not, well, it's a little tougher.
The gist of what's happening is easy to find by connecting your phone while it's booting to USB and running "adb logcat" on your desktop.
That will give you the boot logs and the exact reason for what's happening.
If you're running my decrapified ROM, you may want to switch back to the stock ROM. Go to my stock NANDROID thread, download that, put it in the right folder on your SD card, then boot into clockwork and follow the instructions in the stock nandroid thread.
Make sure you clear data also!
No need to call verizon
I tried connecting the phone to the pc and got nothing. computer couldn't even detect it. I called verizon and got the phone swapped under the warranty. First thing I'm doing when I get the phone is putting the recovery on it. Would have made this process much easier.
Sent from my DROIDX using XDA App
isoutsider said:
I tried connecting the phone to the pc and got nothing. computer couldn't even detect it. I called verizon and got the phone swapped under the warranty. First thing I'm doing when I get the phone is putting the recovery on it. Would have made this process much easier.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Yep, having ADB access is a surefire way to get your phone up and running again.
But, just for future reference, LG has a failsafe firmware updater that will always work, no matter what state the phone is in.
It's not super easy to set up, but it will fix a phone no matter how broken the software may be.
There's a thread in the Dev subforum with the files and instructions, but the gist is that it's accessed by holding VOLUP+POWER with usb plugged in, then plugging in the battery.
It's successfully recovered 3 phones so far.
It may not be the easiest way to get the phone back, but it has a 100% success rate
I'm having no luck with my new replacement I got from vzw. I've tried rooting it with S1C using both exploits, I've tried rootwiki's manual method and none of them work for me. Anyone got any tips?
isoutsider said:
I'm having no luck with my new replacement I got from vzw. I've tried rooting it with S1C using both exploits, I've tried rootwiki's manual method and none of them work for me. Anyone got any tips?
Click to expand...
Click to collapse
Well... you could always try my "toggle ADB" trick.
Turn usb debugging on, then back off, then on again.
Then follow the rest of the rooting instructions, but skip the whole exploit section.
(Basically, remount /system as rw, push su, chmod su, and push superuser, and install busybox)
Ironically, the phone doesn't actually NEED any exploits at all-- it's pretty unlocked to begin with!
Hey everyone I'm new to this forum. After I updated my bionic to ICS last week I have had nothing but problems. The phone constantly reboots itself. It might stay on for 5 seconds or 3 hours. I was wondering if there is anyway to go back to Gingerbread or a way to install a rom that will work. Any help would be greatly appreciated.
There's no going back to GB. Have you done a Factory Reset since getting ICS? If not, do that first thing.
Sir_Eagle said:
There's no going back to GB. Have you done a Factory Reset since getting ICS? If not, do that first thing.
Click to expand...
Click to collapse
I have reset it 3 times. Still reboots all the time. I tried taking out the microSD card doesn't help either.
I worked in an environment with nearly 20 Bionics, and I've seen it twice. Believe it or not, it was the battery. No idea why, but in both cases I replaced the batteries and the issue was completely resolved. The issue only came up after the ICS update. And, in both cases they were extended batteries, tho I'm not sure if that matters.
stevendbrady said:
I worked in an environment with nearly 20 Bionics, and I've seen it twice. Believe it or not, it was the battery. No idea why, but in both cases I replaced the batteries and the issue was completely resolved. The issue only came up after the ICS update. And, in both cases they were extended batteries, tho I'm not sure if that matters.
Click to expand...
Click to collapse
I should be getting a new battery in the mail tomorrow. I will let you know what happens. Thanks for the help.
Ha, it's been a month, but did it work? Or did you get it working otherwise?
I experience the same issue.
I RSD Lite and FZX my phone back to stock and it seems to work for another 5 days or so. I've tried to nandroid a backup when it's good then restore it when it goes nutty but that doesn't help. I've flashed the FZX image, then used Safestrap to flash a CM-based ROM in Slot1, but when the stock goes TU, so does the other.... and vice versa.
I haven't tried batteries.
I just got this phone in the mail yesterday off of e**y and it has been rebooting all the time too. Not consistently though but enough to make it aggravating. I just got it rooted and somehow was able to get safestrap3 on it. Went into the twrp recovery and wiped cache and dalvik and rebooted from there. So far ok but it has only been about 10 minutes since I did that. I have already done 3 factory resets and even wiped cache in stock recovery. I used my X2 to record the craziness of this phone doing it's own thing but with the guy above talking about the battery maybe being faulty I might have to try that because the phone has at 0% when I got it and I don't know how long it was dead for. Does not being charged for a long time ruin a battery?