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
Related
And now I'm boot looping won't go past n color startup animation wth
Sent from my Cyanogen Mod EVO using Tapatalk
I had that problem on my NC when it was rooted. Luckily I had another problem that let me get out by the 8 times reset manual method. Mine would occasionally update itself back to version 1.0.0. When it did that I managed to reset it & now a new NC is on its way to replace this one.
This probably won't help solve the issue but at least it lets you know you're not alone.
Mine boot looped and I did the full 8X reboot thing and then the 3 button data reset. All of that puts you back to "out-of-the-box" stock. You can then redo the autonooter rooting procedure.
Can't get out
I am stuck in a boot loop and cant get out.
First it was stuck on the droid boot animation from the auto config. After I put the autonooter card back in it started looping the rooted boot animation.
Did the 3 button thing and that forced an update but went back to bootlooping the rooted animation.
Then did the 8X reboots manually and that also forced the down arrow update, but then it still bootloops.
I tried getting in from PuTTy (as admin) but it never connects. Do I just use port 22? (to 192.168.2.2 with Data and username as root?)
adb doesn't work... going to bed now and will try again tomorrow after work.
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Bigger Issues.... First Brick?
Nate731 said:
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
So ... I left my Nook in what I thought was an "OFF" state last night, only to bring it to work and find it says "Battery too low to Power on" "Please wait 15 minutes and try again"
I think... no worries... plug it in and let 'er sit for an hour.... an hour passes and I'm still getting the same screen.
Is this better or worse? let me see...
1) if it stays like this, I can return/exchange it at B&N and they won't be able to verify that it was rooted due to non-bootiness
2) If it eventually boots, I will have to try to get it out of bootloop.
3) If it comes to life and I can't get it out of bootloop, I will drain the battery again and go back to #1.
Any thoughts besides this current train?
sort of working?
OK....
so after charging on USB port (all I have at work today as I forgot the base to the charger), it will bootloop again... yay!
problem is... the bootloops take too much juice and won't allow me to fail 8 reboots. I can't even charge it up enough since I'm on USB charging and it keeps trying to turn itself on.
2 Options i see:
1) Go home and charge it on the wall and see if that helps
2) Discharge it to death and return within my 30 days (X-mas gift)
Doubt this will work, but have you tried putting in an autonooter sdcard and then plug it into the usb? If it tries to boot maybe it will boot from that sdcard?
Boot from the Froyo SD card, then fix /rom/devconf/BootCnt from ADB.
Cal you never mentioned if you cleared the user data... Did you?
Nate731 said:
Cal you never mentioned if you cleared the user data... Did you?
Click to expand...
Click to collapse
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
cal3thousand said:
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
Click to expand...
Click to collapse
Try Geezer's tip but do this:
Do three button reset WITH the autonooter card in there.
Got it working
Finally got it working after creating a Nookie Froyo card and booting off of that.
Then I reinstalled ADB on my work computer and reset the BootCnt file to 8...
that successfully restored /system and then the 3 finger trick actually gave an option to wipe.
Now to start over.
New Question: How likely is this hardware related and should I be looking to replace it before my 30 days is up>?
I ran into the same problem, trying the same solution - any luck the second time?
JasonBunting said:
I ran into the same problem, trying the same solution - any luck the second time?
Click to expand...
Click to collapse
My Nook has been great since the fix. But I also needed to use a program to turn off Wifi when I turn the display off.
I did it all from my Nookie...
confused?!
I was wondering how you fixed this..i have read everywhere, but nothing...im stuck in the nook co screen. This happened right after i plugged my nook to charge after my battery was drained...thnks
Think i may have bricked my tab... FAIL.
Verizon Tab. Running stock OS. Was rooted
Bought the Bootstrap recovery so i could do a nandroid backup. I kept failing the VZW update, so i figured do a backup, then remove bootstrap and reflash things to get it right. However...It doesn't work like the Droid X or 2 bootstrap. So that i wasn't prepared for. It automatically ran the backup fine, but on the reboot it just went nowhere and was stuck in a boot loop.
I tried vol up + power, did nothing. Did Vol down + power and got to Downloading screeen. :O Didn't have time to **** with it then, i was getting an oil change and honestly thought it would have just given me the option to run a backup...not run a backup and flash and all the other stuff it did.
Finally get time today to tweak it. It won't even turn on to downloading screen. Can't even get it to bootloop. I plugged it it in the wall and the battery symbol shows, but...it has the spinning "thinking" logo showing, though it never spins and i cannot see how much charge is on it.
I downloaded Hemidall or however you spell it, and the stock verizon tab files. It won't even see the device when i plug it into the laptop. Yes i have the drivers installed. I have hooked up my tab to my laptop MANY times. Running Windows 7 64 bit. Also have Ubuntu if needed. Also downloaded and installed that Visual C++ thing that needed to be downloaded with it.
Any ideas of what to do other then use it as a paper weight? I know i can send it back to Samsung, but i don't think the wife would appreciate me bricking my tablet like that. LOL Somehow i cannot see her taking that as a good thing.
Should i just leave it plugged in for a few hours and hope it starts showing a status update? Been 45 min now, showing nothing.
Any help would be greatly appreciated. Thanks.
edit: OK been a bit longer, took it off, can get it to get stuck at Samsung loading screen again. XD Just didn't try download screen yet cause i want to make sure it is FULLY charged. Only crappy thing is that it still won't show battery status while it is charging, just the thinking symbol. Hope i don't fry the battery then
edit again: Still can't be recognized by Heimdall. CRAP. Anyone know the Vendor ID, Product ID and Interface ID to use to install the proper drivers through zdag??
edit again: hooked up while in download mode, was able to install drivers. Did clean install and rebooted. All fine now. WOOT
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!
I have been running Slim ICS on my Captivate for a month or two now. I have been on version 3.6 for awhile now and have had no issues.
Today however, My phone was acting a little odd, and I decided that it had been awhile since my last reboot, so I held the power button, clicked reboot, (not into recovery) put the phone back in my pocket once I was sure it was rebooting and went on my way.
30 minutes later I took my phone out of my pocket and looked at the screen. It was still on the Slim ICS screen and I thought maybe it was looping, but it never rebooted itself or went back to the AT&T screen. It just stayed on the Slim ICS screen until I pulled the battery.
It has done the same thing every time I try to turn it on.
Download mode wont work (my cappy doesn't have the 3-button combo, so I have to use a jig.) I can get it in download mode but my computers wont read it. I tried uninstalling/reinstalling drivers, I tried different chords (on each computer.) and nothing works.
I'm kind of at my witts end, as it is my alarm in the mornings and I rely heavily on my phone. any suggestions on what to do? or is it time to check if I can upgrade...?
(P.S. I apologize for the sloppy formatting, it's 2:30 am and I've been trying to make this work for 2 hours...)
EDIT: I kept trying and eventually got my phone to read as gadget serial instead of unknown, flashed back to stock and am now getting back to ICS. To anyone in a similar situation, just keep trying and hopefully it'll pay off.
Do you have recovery mode?
Swyped from my ICS Samsung Captivate
korockinout13 said:
Do you have recovery mode?
Swyped from my ICS Samsung Captivate
Click to expand...
Click to collapse
None of the button combos work on my device (none of them ever have) and I cant get my computer to read my phone, so I can't use ADB to reboot in recovery. All I can really do right now is get into download mode with my jig, but none of the computers in my house will read it with any of my chords.
Have u tried "Mobile Odin" by Chainfire ?? Find it in the Market...uuugghh...the Play Store. :/
Sent from my SAMSUNG-SGH-I777 using xda premium
alright, it was a huge headache... but I got back to gingerbread stock.
I'll tell how I did it:
Deleted all installed samsung drivers (and rebooted computer).
Go to download mode (I used the jig, if you have button combos, it's probably easier)
Plug the device into the computer and hope to god it reads as Gadget serial
I then used this to restore to stock (it failed 3 times before it worked... everytime it got just a little bit further, until it finished.)
So ultimately, after a nightmare of a time and a lot of headache, I'm thankfully back at stock, and working on getting back to ICS.
although the process is difficult, as odin still won't find my phone (heimdall does though)
Hi there!
I'm wondering if you guys can help me brainstorm, or at least get to the root of the problem. Alright, so to preface... I'm using an ATT Galaxy S Captivate [i897]
I was updating my version of MIUI from the miui.us version 2.3 to version 4.0 [ICS.] This worked fine, and I had backed up my data with TitaniumBackup. However, I made a mistake: I chose one of the backup all options, where it backed up all my system data and app data. Little did I know, restoring the system data would completely own my phone. So I did a restore, rebooted, and my Captivate sits at the boot animation indefinitely. It won't get past it.
Somewhere along the line, my download mode and recovery mode 3-button combo got borked. They no longer work [trust me, I've tried every one.] When I try to enter recovery by pressing and holding a number of volume and power button combinations, it goes straight to the boot animation after the AT&T screen. When I try to enter download mode by pressing and holding volume/power, battery in, cable in, and every other possible combination [including switching the cable to different ports on my computer,] I simply get a "stuck" circular loading icon which flickers every few seconds. When I let go, it shows me a grey battery icon with that stuck loading circle overlaid.
So, moving on, I decided to disassemble my phone and try to reset it by shorting the TP contact in the back against the SD card slot. I wish I could find the thread; it's supposed to reset the device. It definitely causes my captivate to reboot [while it was stuck in the boot animation] but it didn't fix the problem. So I decided to make my own jig.
I built it out of three 100k ohm resistors, was super careful not to contact the metal parts of them while I plugged it into my phone. I tried plugging the micro B cable in first, then touching the resistor leads to pins 4 and 5 on the back end of the USB jig, but to no avail. I tried slightly different resistances, but no go. I tried connecting every pin to every other pin just for the hell of it, and no luck there either.
I don't have a soldering gun, so J-tagging is not an option [before I just buy a new phone, anyway,] and I'd rather not buy a USB jig because I'm not convinced it'll work. I know there are a lot of factors, and everyone says to try it 400 times, but I tried it more than I have patience for already. There's got to be something else wrong.
I'm wondering if TitaniumBackup has the capability to mess up the boot loader? If I accidentally overwrote system files with older ones, why would that cause it to get stuck in a bootloop? And where did my download mode go?
If anyone has any ideas, please let me know! I've done a massive amount of research on this. And I found some pretty brilliant ideas along the way, but none of them seemed to work for me. I'm to the point where I literally can't find any more references to problems similar to mine, so I figured I'd ask you guys!
TL;DR: I think by [accidentally] restoring system files with TitaniumBackup from MIUI 2.3 to 4.0, I may have completely owned the boot loader. Can this happen? And is there any fix? I can't get into download or recovery with button combination, jigs, or short-circuiting my phone in fun new ways.
Thanks
The phone by itself is not capable of writing to the bootloader. I am at a loss for why it doesn't work. All I can say is keep trying.
Sent from a jelly bean
korockinout13 said:
The phone by itself is not capable of writing to the bootloader. I am at a loss for why it doesn't work. All I can say is keep trying.
Sent from a jelly bean
Click to expand...
Click to collapse
Well. It might just be the way you wrote it, but you said "I try to enter download mode by pressing and holding volume/power, battery in, cable in...".
The correct method is exactly this.
1. Pull your battery.
2. Hold down volume button.
3. Insert battery.
4. Plug in USB.
5. You should be in DL mode.
Give it a try even if you think you have done it before....