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!

[Q] Stuck in a boot loop, cannot access recovery

Alright I am stuck. I've spent three days searching all the forums I can find, trying everything I find, and none of it has worked.
I was running the Decrap ROM on my phone no problem up until the OTA update started coming through. It failed the couple of times it tried to install. Then the Revolt ROM 1.0 came out. Made a backup, and flashed that one over the Decrap ROM, no problems. Revolt 1.1 is released, I flashed back to stock, then flashed 1.1 over it. It was running fine for a few days, except for two FC on the phone. Then I got a call from my girlfriend, tried to answer it, and the phone FC but was still ringing. I tried opening the dialer to call back, and it kept force closing. I rebooted the phone, and my real problems started.
The phone now goes through this process...Vibrate > LG splash screen > blank screen > Vibrate > LG splash screen > blank > repeat.
The only way to make it stop is taking the battery out. Every time I plug it into the wall or computer (with or without a battery) the process starts automatically. I cannot get into any sort of recovery no matter how long I hold the volume and power keys. I tried taking the battery out, SIM card, and SD card. I plugged it into the wall with and without a battery, let it charge overnight, no luck. I tried the SDK method with fast boot but I cannot get my computer to recognize the device because it keeps trying to restart itself.
The only thing I have not tried is the LGNPST method because I read of problems people were having even after recovering their phone, and I figured that if the SDK method would not work because my computer did not recognize the device neither would this.
Does anyone have any other suggestions? Or am I going to have to bite the bullet and pay for a replacement?
Thanks!

Sent you a pm
Sent from my VS910 4G using XDA Premium App

I have not had the exact problem you do, I can get the phone to charge. But I have also 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 after boot in the morning.
It seems a number of non-root users have this problem. You might be able to go in for a replacement, see:
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.
Have you tried plugging it in without the SIM and SD card?

Charging without Battery
http://forum.xda-developers.com/showthread.php?t=1211935&highlight=can't+boot+to+clockwork
Well, this morning, I ended up in exactly your positions, despite having a full battery.
I tried the suggestion of plugging the phone in without the battery and letting the bottom lights flash on and off about five times. Then I put the battery back in and it booted to the charger.
still can't get to Clockwork though, if you find a solution, please post.
Update: I ended up getting back to Clockwork. Can't say exactly what did it, but what seemed to work was:
1. Charging the battery fully overnight
2. Removing the battery and holding the power button down for 30 seconds
3. Leaving the battery out for some time, about an hour I guess
4. With the battery still removed, plugging the phone in and allowing the bottom lights to flash about 10 times
5. Replacing the battery, holding down the power button and volume down.
After a full day of not being able to get into Clockwork, I was able to get in and do a factory reset.

Returning Revolution to Verizon
FYI, I took my rooted, non bootable phone into a Verizon store, and they ordered a replacement. Didn't try anything special and they didn't ask about or look for rooting on the phone.

I am having a similar but not identical problem. After trying to downgrade with LGNPST, my phone just sits at the initial LG logo. Well, it comes up, then blinks and vibrates and then comes back. It will sit there forever. I have been unable to get the hard reset menu to come up.
The phone is detected under Windows, but it tries to install a new device driver "LGE CDMA USB MODEM" for which I do not have drivers for. It does not show up as a device in LGNPST.
Any ideas?

nesterbation said:
I am having a similar but not identical problem. After trying to downgrade with LGNPST, my phone just sits at the initial LG logo. Well, it comes up, then blinks and vibrates and then comes back. It will sit there forever. I have been unable to get the hard reset menu to come up.
The phone is detected under Windows, but it tries to install a new device driver "LGE CDMA USB MODEM" for which I do not have drivers for. It does not show up as a device in LGNPST.
Any ideas?
Click to expand...
Click to collapse
Try pulling battery, put battery back in, press and hold volume up, press and hold power button, hold both thru the lg screen. Hopefully it will boot into a download mode that is recognized in lgnpst.
Sent from my VS910 4G using xda premium

Didn't seem to do anything different. Still prompting for those USB modem drivers.

nesterbation said:
Didn't seem to do anything different. Still prompting for those USB modem drivers.
Click to expand...
Click to collapse
You are downgrading correct? If so the drivers you downloaded from the downgrade instructions delete those. Go to LGs website download those drivers and then retry again. That's what I did yesterday when it wouldn't recognize my phone in the program. Let me know if it works.
I've Revolted have you?

When this happened to me I contacted Verizon about the issue. Apparently I was not the first person this had happened to. I found on a couple of other forums that non root users had the same problem. Sounds like it may be an issue with the phone in general.
Sent from my VS910 4G using xda premium

BP failure, BP bypass?

Whoa! My droid 3 just did something weird! I started getting screen artifacts that looked like a black terminal and it said something about a BP failure and BP bypass. This a pop up showed up asking if I want to switch to global mode since no cdma tower was available ( I switched to cdma only and it save crazy amounts of battery now). Then my phone rebooted without me making a selection! This has never happened before. I got to see this stuff, but I'm wondering if its cause I installed Log This that I was able to notice anything. What is (a) BP ?
If this is all software related, could the bypass get us escalated priviledges?

Darksurf said:
Whoa! My droid 3 just did something weird! I started getting screen artifacts that looked like a black terminal and it said something about a BP failure and BP bypass. This a pop up showed up asking if I want to switch to global mode since no cdma tower was available ( I switched to cdma only and it save crazy amounts of battery now). Then my phone rebooted without me making a selection! This has never happened before. I got to see this stuff, but I'm wondering if its cause I installed Log This that I was able to notice anything. What is (a) BP ?
If this is all software related, could the bypass get us escalated priviledges?
Click to expand...
Click to collapse
That's a bootloader protection (BP) Bypass. That may be the way in! Any way to replicate that? We need *FULL* disclosure on what was going on. A logcat output would be great!
Open ADB and type:
Code:
adb shell logcat > /sdcard/logcat.txt
adb pull /sdcard/logcat.txt C:\
Then upload that file (C:\logcat.txt) to a sharing site and let us rip it apart.

Some people over at phandroid had similar BP issues. There was no bypass message though. Maybe they are somehow related?
http://androidforums.com/motorola-droid-3/387878-my-d3-crashed-bp-panicked-error.html

forum.xda-developers.com/showthread.php?t=1188279

Yes, but we need the output of dmesg from before the panic. logcat will provide that.

BP=Baseband Processor=Radio
Something caused the radio to go into panic mode and it rebooted the phone.
This is not a way to get root unfortunately. The radio is setup such that in order to access it you need to bypass the AP (Applications Processor) layer where the OS and kernel etc. reside. That is what BP Bypass or Passthrough mode is for.
When you flash an SBF file the last stage of the flash re initializes the device for BP Passthrough to flash the radio partition.
The radio is literally a separate chipset on the board from the OMAP SoC and there are various access modes and device interfaces for all of those components.

Well bummer, I was hoping for something useful. At least we know that this has already been covered instead of wasting our time on it. Thanx for the info, knowledge is the key to everything.

either way, it'd still be nice to know what caused it.

Mine did the same thing shortly before it went to complete ****. After that happened it started rebooting itself all the time, rebooting itself coming back up with the welcome to android screen, even though there was no factory reset, it would reboot during calls, it would tell me i had missed calls from tomorrow. Browser barely functioned, apps would constantly force close. I brought it in to verizon after 3 days of it. Got a new one and traded my wife for her X. And now root comes. Ohh well i guess ill have to get by with a bionic.

pplude said:
either way, it'd still be nice to know what caused it.
Click to expand...
Click to collapse
I think it has something to do with not having CDMA signal. Just a guess. I have my phone set to CDMA only to save lots of battery, and sometimes all signal drops and then I get signal again (it happens when bouncing between 2 towers where I live) and then I guess the radio freaks.
I've only had it happen once, but I have notice that I had pretty good signal then bounced over to another tower and when I bounced back (all in a short time frame) is when it happened.
Just a guess.

Can't reconnect to 4G after disabling it on my Bionic with ICS

I have a Bionic that i just put ICS on. 4G was killing my battery so i used *#*#4346#*#* to put it in CDMA auto. Now it won't let me revert back to LTE/cdma/evdo. I choose that setting and it automatically changes it back to CDMD auto. I haven't seen 4G since i did this. Please help! My wifes phone gets 4g service, so i know the service isn't down.

sweetchuck08 said:
I have a Bionic that i just put ICS on. 4G was killing my battery so i used *#*#4346#*#* to put it in CDMA auto. Now it won't let me revert back to LTE/cdma/evdo. I choose that setting and it automatically changes it back to CDMD auto. I haven't seen 4G since i did this. Please help! My wifes phone gets 4g service, so i know the service isn't down.
Click to expand...
Click to collapse
Mine did the same thing. I got mine back somehow. If I recall, I set it to the original setting again. After that I turned off data, and turned off the radio all together. Rebooted and it worked. I made a thread about this in the general section but 200 views later no response.

I had to do a factory reset to get mine back.
Been too scared to turn off 4g since.

I've heard of people having similar issues and were able to solve it by turning off the phone, removing the SIM card and powering it back on, then turning it off again re-inserting the SIM and then turning it back on. Not sure if it will help in your situation, but it's worth a try before a FDR.

Same here. Been too afraid to change it again.
Sent from my DROID BIONIC using xda app-developers app

Weird. I'm on leak 6.7.230 and it happily toggles between 3G and 3G+4G through that menu.

possible solution
I know I'm late to the party here, but i wanted to add my 2 cents, as i just got a Bionic and had this problem.
I used the LTE on/off app to turn the 4g off to save battery. When i wanted 4G back, it would not come back. I tried restarting, pulling the battery with the phone on, booting with no sim, etc. Nothing worked. Setting the phone to 4g would cause it to lose all data connections. The 3G would always stay on for about 20 secs, before dropping.
Finally, after a restart with, i went to the *#*#4346#*#* screen, set it to 4G, and pulled the battery before the data dropped (i already had the phone case open so a battery pull could be performed quickly. I then let the phone sit for a good 5+ minutes without a battery in it, and when i finally booted back up the 4G was there.
Now i don't know if this was a coincidence or not (i'm not going to try to replicate it, i'm leaving well-enough alone), but i wanted to share my experience b/c this thread was one of the top hits on Google for this specific problem. So hopefully this will help someone out.

Phone starts with moving halo and "wissen"... "Is it wiping my phone?"

Phone starts with moving halo and "wissen"... "Is it wiping my phone?"
Just now I took my Nexus 6 out of my pocket because it was very warm.
The screen was all black with in the middle a big Halo moving with the disturbing message "wissen" beneath it.
"wissen" is Dutch for wiping, deleting or removing...
Turning the phone off is possible by holding down the power button for 6 seconds, but then it turns on again after 3 seconds showing that same screen again.
After some fiddling I was able to find a method to turn it off.
I can start the phone by holding down the power button and the volume button (down) which will start the recovery program.
There I can turn it off.
Although I have unlocked the phone and ran modded firmwares I switched to standard factory Nexus 2 years ago and haven't had a rooted phone for all that time.
Recently I installed the 7.1 OTA updated.
I'm afraid this is something like a remote wipe.
It also doesn't ask me to give my PIN which is normal for it to do.
What is happening?
Some more info: Yesterday I bought the "AIO All-in-one Toolbox " after using the free one for 3 weeks. Could that be involved?

It may be formatting and encrypting your data partition.

Yes, but why?
It just went into my pocket this morning....
I came one step further.
As I was still able to get it into fastboot loader I exited with "volume up"
Then it went into an almost normal boot. This didn't require the pin it normally needed.
The device went into a full factory reset.
I thought I would be up and running fast, but after entering my new gmail account/password I got the message that I needed to wait another 24 hours because I did a password reset.
I did this password reset of my Google account out of safety. Now I'm being punished for this....
Luckily I have a spare Motorola G3 with its own SIM, so I can at least use my phone.
I can't even use my Nexus as a phone nor can I go to settings. Maybe if use another Google-account.

Did some more research...
The last Exchange sync was while cycling to work.
Didn't use the phone then nor later.
Because my Google-account is locked I can't do anything with my Phone (not even phone), so I decided to flash an alternate rom on it.
I flashed lineagos and also rooted the device again.
Although I did root my Nexus 6 in the beginning this is the first custom ROM I have on it. I still need to install gapps.
Now I can start using my Titaniumbackup again that I bought several years ago.
I still have no idea how it could have gone into wiping. I put the phone in my pocket while it was screenlocked. The device needs a pincode to unlock.....
I am still unable to use Google Apps. I can run the app, but it doesn't let me install apps.
On the stock rom I was just stuck (stuck rom, haha)..... at the installation screen unable to even make a phone call....
Does someone have any idea???

frater said:
...
Does someone have any idea???
Click to expand...
Click to collapse
My idea is that you have the N6 unprotected in your pocket. Moving or cycling caused activation of a factory reset.