Database Develop

Strange Problem

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!

Boot Trouble - Rooted After Phone Downloaded OTA, Not Installed

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.

Phone won't turn on

Hey Everyone,
Just seeing if anyone might have a solution to my problem that I'm facing. I had rooted my phone when the root originally came out, and everything seemed to be working fine. I had been texting on my phone when it suddenly froze, I waited to see if it would come back, but it never did so I pulled the battery.
The phone originally booted to the M logo, but froze, after another battery pull the phone now won't turn on at all. As in it's not responding to the power button press at all. It's not being recognized by a computer, and there doesn't seem like much I can do.
Any suggestions out there? If my phone is bricked and can't even turn on, will a Verizon store know this? How could they?
thanks.

If u froze something like a system app that may have bricked it. Theres something u can flash which was a cracked version of an ota update that should fix it but u may not be able to receive official updates if u do that. Other option is to wait for an official sbf file
Sent from my DROID3 using XDA App

How can I flash something? There doesn't appear to be a way for me to access my phone. I can't get into restore or the bootloader.

What happens when you plug the phone into your charger(using the stock charger and cable)?

Nothing, no light, no anything

I actually haven't tried it in a situation like that so I can't give instructions :/
Sent from my DROID3 using XDA

Just take the phone into Verizon and tell them it has stopped working. You don't have to go into any detail at all.

g3m1n1 said:
Just take the phone into Verizon and tell them it has stopped working. You don't have to go into any detail at all.
Click to expand...
Click to collapse
I think that might be what I do, I can't imagine they would have a way of knowing it's rooted if the phone won't even turn on, charge, or anything.
Thank you, btw.

Try taking out the battery and plugging it in to the wall without it in it. If it starts to boot, let it. Then replace the batter and plug it into the wall again and let it charge up. Happened to my Droid X before and I was able to get it working by doing this.

Tried this, but couldn't get it to work.
Took it to a Verizon store and they said they would send me a new one tomorrow, and then all I do is send mine in afterwards.
Is there a chance that after I send them my phone they could find out I rooted it? I'm worried they would charge me full price for the phone they sent me if they discover it.

Niviac said:
Tried this, but couldn't get it to work.
Took it to a Verizon store and they said they would send me a new one tomorrow, and then all I do is send mine in afterwards.
Is there a chance that after I send them my phone they could find out I rooted it? I'm worried they would charge me full price for the phone they sent me if they discover it.
Click to expand...
Click to collapse
Honestly the Magnuson-Moss act protects you in that VZW has to prove that rooting caused the phone to fail. However in practice you end up having to take them to court which is too costly and time consuming. But to answer your question yes they could pretty easily figure it out.
But to put it differently no one else that I've read about has had a failure like yours. People have bootlooped and such, but no one has just had nothing happen on power-up. It doesn't sound like you did anything other than root, which couldn't possible cause this. Freezing apps and deleting system apps only causes force closes and bootlooping, you had neither.

5.9.905 made my 4g connection worse

I was on 5.9.904 with Eclipse 2.2 and flashed back to 5.9.902 and upgraded to 5.9.905 then installed Eclipse 3 for 5.9.905 and now my 4G sucks.
Keep in mind I'm in a solid 4G area where it never switches to 3G.
Sometimes the icon is blue and it works but most of the time its white and doesn't work.
I have to set my phone to airplane mode and back for it to work again and sometimes that doesn't work.
If I go back to 5.9.902 and upgrade to 5.9.904 will that change the radio back to the old version or not? If nothing works I'm just going to get a replacement of hopefully a new phone from Verizon.
Thanks

If you had better connection with .902 then just FXZ back to that and don't install the official update when it ask you to. That is why there are different FXZ files so that you have the option to use what is best for you.

I had better connection on 5.9.904.
I just don't know if radio updates are permanent or not.
Will going back to 904 fix it?
Wow I dropped data while typing this message.

I haven't upgraded to 905 yet, but I've been having all sorts of problems with 4g for the past 2 days. I'm on 904 and eclipse
Sent from my DROID BIONIC using Tapatalk 2

scottocs said:
I had better connection on 5.9.904.
I just don't know if radio updates are permanent or not.
Will going back to 904 fix it?
Wow I dropped data while typing this message.
Click to expand...
Click to collapse
Radio updates are not always permanent. If you are on 5.9.905 you can FXZ back to 5.9.902 (which will put in the 5.9.902 radios) and then go find the 5.9.904 update.zip, and flash that in stock recovery to get back on the 5.9.904 radios.

Im starting to think it is something wrong with Eclipse 3 because the connection on stock 5.9.905 is working fine.

Me too - I ran the OTA - didn't lose root (am running SafeStrap w/.902 Pathsaver). I first noted the problem while in Beverly Hills - normally a full 4G area with few problems save the occasional network problem.
My network weather settings would not refresh though 4G icon appeared in blue - Also email was silent for too long.
The problem again appeared when accessing The Market (Play). The phone responded with No Connection/Retry. The connection would not return despite going to A/P mode or switching between CDMA/LTE. Finally, I restarted and 4G returned for long enough to download an app and listen to a podcast on BeyondPod.
This weekend, while listening to BeyondPod - the stream just stops and will not restart until the phone is fully restarted (ON BUTTON with -+ volume pressed).
I will revert to 902 and try flashing 905 from the SD card tomorrow.
Will report results -
This seems to be fairly uncommon as such, I'm hoping that the above will restore.
From all I've read - 4G is supposed to be ENHANCED with .905.
C'est la vie.

I think that I am not in a hurry to get the .905 OTA.

with all the issues with the last couple of radio updates im sure they will push out another one soon to fix those issues lol. it's best just to stick to a stable radio version until confirmed issues are solved.

Amendment to original post
Lemmy Caution said:
Me too - I ran the OTA - didn't lose root (am running SafeStrap w/.902 Pathsaver). I first noted the problem while in Beverly Hills - normally a full 4G area with few problems save the occasional network problem.
My network weather settings would not refresh though 4G icon appeared in blue - Also email was silent for too long.
The problem again appeared when accessing The Market (Play). The phone responded with No Connection/Retry. The connection would not return despite going to A/P mode or switching between CDMA/LTE. Finally, I restarted and 4G returned for long enough to download an app and listen to a podcast on BeyondPod.
This weekend, while listening to BeyondPod - the stream just stops and will not restart until the phone is fully restarted (ON BUTTON with -+ volume pressed).
I will revert to 902 and try flashing 905 from the SD card tomorrow.
Will report results -
This seems to be fairly uncommon as such, I'm hoping that the above will restore.
From all I've read - 4G is supposed to be ENHANCED with .905.
C'est la vie.
Click to expand...
Click to collapse
On further troubleshooting - assumed that root was not broken. It seemed that all of my apps were working as they should but when I attempted a SafeStrap restart and restore my UnSafe installation, The SafeStrap prompts would not appear. So, I checked root -found that it was in fact broken so, I ran Voodoo, restored root, ReInstalled Safestrap Recovery from the app and, restored my unsafe system to .905.
Since it was the weekend, I haven't had much of a chance to test 4G but while I was at the gym, I did listen to some podcasts. Email seems to be pushing. Today (weekday) should give me ample opportunity to test the update.
Hopefully, the restore fixed the problem.

This entire thread Sounds like bad hardware our user error
Sent from my Xclipsed Bionic

I am in the same boat here. I took the .905 update last weekend and my 4g has been terrible since. It stays 'white' most of the time and when it is blue and I open an application it instantly turns back to white and I get no connectivity...does anyone have a suggestion? Also, I was rooted and had safestrap. After the update...I guess I am not sure if I have root anymore? a root check app says I do not but I was still able to reinstall safestrap apk and then boot into eclipse.
Thanks in advance

I think this is a network issue. With last couple of days, my LTE has been showing white and wont connect to network. I still have 5..9.902.
Sent From Droid-Bionic
Using Xparent Blue Tapatalk

My phone is 5.9.904. Does that mean I can't get the 905 update?

So is it the update or a network issue?

ronaldheld said:
So is it the update or a network issue?
Click to expand...
Click to collapse
On my personal use, I was trying to see if the MAX batt saver option had something to do with the data connecting. Since setting it on nighttime save, I havent had too much of an issue.

these are from the eclipse forum
I take no credit, but used them both (despite not having any data issues at all) and others claim these work:
A:
1. Power down
2. Remove the back cover, battery, SD card and SIM card.
3. Power back up, let the phone come all the way back up and tell you that you can only do "emergency calls only"
4. Power down
5. Reinstall SIM card, SD card, battery and back cover.
6. Power back on and let the phone boot normally.
B. in settings, Battery, Battery Mode, do not use "maximum battery saver". use nightime saver. (I use custom battery saver, which just slightly adjusts the nighttime hours).
no harm in trying these.

Link to 905
Anyone have a solid link to 905? The one DROIDMODDERX posted here (http://www.sendspace.com/file/xo8f4g) won't download to my phone. Not sure if it is my phone or the link. I can pull stuff off of Google Play all day long though.

Juroid said:
I think this is a network issue. With last couple of days, my LTE has been showing white and wont connect to network. I still have 5..9.902.
Sent From Droid-Bionic
Using Xparent Blue Tapatalk
Click to expand...
Click to collapse
x2 on network issue. I've noticed 4g issues many times lately on my phone and also on stock .902

Not network issues....the leaked .905 is flawed.
My wife and I did a test. I did t his because for the 3 days I used the leak I noticed white data drops happening a helluva lot.
We were in the same room standing less than a foot apart in the same house.
We hit the same app/icons on our bionics at the same time even.
I had the .905 leak....it went white 5 times for roughly 15-120 seconds each time in a 15 minute window.....my wife's stock .902? NEVER.
Nuff said...or not. lol

Bionic reboot problem

I have had my replacement Bionic for about a week. Have been on ICS .232 leak aince unboxing. Today the problem started. The phone will boot, but never connects to the network (no phone, no data. The phone settles, then it reboots. Tried battery pull, pulled sim card, tried different battery, tried both charging and not charging. was hoping it was something I can fix without data wipe. Tired of setting everything up over and over again! lol

Did a data wipe, no help. Also found that if I turn on airplane mode, it stops the reboot. Soon as airplane mode is turned back off (I lose the power button quick toggle, it's grayed out and I have to go into settings to change it) automatic reboot. Guess flashing back to .905 and hopefully not be sending yet another one back! !

SamuriHL s House of Bionic works miracles for 232+ bionics!
Sent from my DROID BIONIC using xda premium