I was slow around flashing to the latest baseband but finally took the dive today and the program locked up at 5% for like 2 hours before I yanked it. Now it just gets to the "S/W Updater" screen regardless of what I do (NVFlash recoveries, roms, kernels, format, hard reset, etc). When I try to update it again, it just immediately says it's already the latest version. Why won't it just flash over it like most flashing programs.
Tmobile is pinging me $20 for a replacement but I have a really good G2x. Is there anything I can do to revive mine or is it toast? ADB commands or something? I have clockworkmod on there now, but I'm not really getting anywhere.
[Update]
Use this NVFlash method to completely format your phone, re-setup your partition tables, and flash the stock GB rom:
http://forum.xda-developers.com/showthread.php?p=17258229
Dead
It's dead. Same thing happened to me and to many many others. Turn it back to TMo and take the hit--it's not worth the time playing around with it any more.
Call TMo and ask to be forgiven the $20. If you've been a long and loyal customer they might even do it.
Your new phone should come with 2.3.3 installed. Mine did and I've had no trouble with it--it's finally settled down into a very usable and fast phone. Stock ROM. But I won't buy another LG phone again for a very long time--not until they hire a few software engineers who know what they're doing.
No my friend. I got revived!
http://forum.xda-developers.com/showthread.php?p=17258229
It totally erased everything, formatted everything, reset all the partitions, and flashed the GB Stock rom.
Booted up, NVFlashed CWM, Restored my Nandroid backup, viola!
Thought it would be a good thing to make more available. It was in the Android development thread but the title is tricky as its listed as a rom (which I guess it kinda is).
Sent from my LG-P999 using xda premium
i dont understand why people get stuck on this. ok
when i did it. the LG Tool stop responding on half the period % and my phone had the S/W updater screen so what i did i click on closed unpluged my device then open the LG Tool again plug my device and the LG TOOL said that there was a problem if i wish to continue with my update i click yes and it kept doing till it was done and my phone was fine with 2.3.3
The mistake you made was just stopping the update. Mine did the same thing. Instead of listening to the stupid message about removing the battery, etc. I just removed the usb cable, waited for the beep, put the cable back in, waited for the beep and then pressed "restart" on the update. It completed perfectly after that.
Well I've gone through all of those scenerios and it would attempt to reflash it, but the last time it got stuck on 5% for about 2 hours... no error message or anything. After 2 hours at 5% I pulled the plug. When it is in the middle of "flashing" and gets locked up, there is no Cancel button or Restart button like when it errors out.
I had no errors, just a locked up program. Regardless the posted link really fixed me up and got it working again.
I changed the title and updated the OP with the solution.
Related
Hello All,
I promise I've done 2 days of research before and while doing this.
I have a Samsung Galaxy S on ATT using ATT network. I tried to put Cognition on it 2.3b7 and something was wrong with the battery life, so I decided to start over and flash it again. In the meantime DG released 2.3b8.
I rooted it Mac (i'm on a mac), got superuser permission, did the whole clockwork thing. Then I decided to flash it using Odin3 1 click downloader back to ATT software. Well then I got phone...!...computer error. I couldn't do the 3 button combo to get it download mode. I made the 301k Jig, that worked and got me in to download mode. I used Odin3 again, got it back to ATT software but I think it was still custom.
The whole ODIN process was actually way more indepth because it wouldn't work, or the USB software wasn't installed correctly, my phone kept being a *****. But I got it to work eventually.
My phone would also say Samsung I9000 (it's a i897, idk if its the same) instead of just the ATT start up. I went through the rooting process a few times on the Mac and no super user app would show up. So I did it on a PC and it worked. Then I went through the standard process of installing Cognition. I backed it up using clockwork, then clicked install rom and selected the .zip file in the SD card.
It started working. Then after about 30 minutes, it just wouldn't turn on anymore. I've taken out the battery, it's fully charged and all that. It still just won't turn on. It's all black...
What happen, has it happen to anyone and how do I fix it?
It's seriously a paper wieght right now.
dnguyen527 said:
What happen, has it happen to anyone and how do I fix it?
Click to expand...
Click to collapse
Exact same thing happened to me - except I have a genuine i9000.
ROM Flasher - selected ROM - booted into clockworkmod, which started flashing the ROM, it proceeded for about 10 minutes, displayed lots of activity on the screen, then the screen went black... and has remained black ever since.
The phone won't turn on, won't go into download mode, won't go into reset mode. I have a jog on order, but I don't think that will do much. I thought that maybe the battery had drained (it didn't - tried it in a different phone).
The phone is just dead, and an equal paperweight.
Are there any options left, or do I just need to send it back to Samsung?
My wife and I both have non-rooted TBs which started experiencing random reboots after the OTA. We went to the store and they ordered us two new ones. They'll be here Tuesday.
Yesterday my wife's TB rebooted, and got stuck at the HTC logo. She was unable to turn it off. I did a battery pull, and again, stuck at the HTC logo. I swapped my battery since hers was low, nothing. It's dead, Jim.
We called the store and they wouldn't swap it since one is already on order. My wife is a doctor, and being without a phone until Tuesday is not an option. So I loaned her mine. (Sigh).
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
ZBoater said:
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
Click to expand...
Click to collapse
Unfortunately, the only thing I would've suggested would be flashing the signed ruu.
You could try reverting to the pre-OTA firmware, but I'm not sure you'll be able to use ADB if you're stuck bootlooping. Check out the "NOT FOR ROOT USERS" section.
ZBoater said:
My wife and I both have non-rooted TBs which started experiencing random reboots after the OTA. We went to the store and they ordered us two new ones. They'll be here Tuesday.
Yesterday my wife's TB rebooted, and got stuck at the HTC logo. She was unable to turn it off. I did a battery pull, and again, stuck at the HTC logo. I swapped my battery since hers was low, nothing. It's dead, Jim.
We called the store and they wouldn't swap it since one is already on order. My wife is a doctor, and being without a phone until Tuesday is not an option. So I loaned her mine. (Sigh).
I tried reflashing the latest signed ruu I got from another thread. I downloaded it onto my SD card, swapped cards, and I was able to hboot and the install seemed to go fine. However, it had no effect. It still gets stuck in the same spot.
Tried factory reset, recovery, nothing. Every time I reboot I get stuck at the logo and I need to pull the battery.
Out of curiosity more than anything else, any other things I can try?
Thanks.
Click to expand...
Click to collapse
RIP poor TB
How long did you wait for the screen to clear?
Just curious because I know usually when I do any type of update or rom change, etc, since you normally wipe the data and cache, the boot up can take quite a long time on the initial boot up.
I know some people report as long as 10 minutes or so to get past the screen. I don't think mine ever took that long, but there have been times I think it's stuck and then a minute or so later, it gets past it.
Just my two cents.
This has happened to a few people already after the update. I don't know what is in this update but HTC screwed up majorly.
Sounds a lot like what happend to mine, but mine was rooted.
See here...http://forum.xda-developers.com/showthread.php?t=1090531
LOL, I welcome the breaks when I can't find my phone for the day.
you should just leave it on the htc logo until the battery dies or until it get wayy to hot.. just to see
will9512 said:
you should just leave it on the htc logo until the battery dies or until it get wayy to hot.. just to see
Click to expand...
Click to collapse
What would that accomplish?
Yeah your lucky you got a guy to order your phone because I wouldn't have because even the new ones are rebooting, when you get it I would suggest postponing the update if it comes without the Mr1 update, as far as your wives phone yeah I would check out the forum uptop on going back to old software other than I have had a few people come into the store with same problem and couldn't do anything( mainly because I have no access to anything), but ship a replacement, oh and one suggestion is if you don't want your wife to borrow your phone your local store does have emergency stock Android loaners that you use until you get your replacement in, and then you just send your phone and the loaner back in the FedEx box so if you really need a phone you can do that.
Sent from my ADR6400L using Tapatalk
I believe your random reboots are due to the new radio which is tied into the OTA. If you apply the OTA again your still going to have random reboots. I ever used the newer radios and have never had a random reboot.
I have an Evo 4G revolutionary rooted. Had sinister rom. Flashed the new King Runny and it worked fine starting out. I tried to get into the navigation and it said I needed to download the updates. Then it said I did not have enough memory space and I needed to delete to make space. I then deleted all the pictures off the phone, and that didn't help. So next I went to factory data reset and I believe I pressed on the SD card to be erased too, which may have been an oops on my part. So when it rebooted I got stuck at the boot screen where it is the blue android symbol and it flashes repetitively. I tried multiple things, I have read multiple threads. I tried to flash back the stock ruu. I have been working at it for a couple of days now and I am at a loss. I am on the verge of taking it back to Sprint and eating my $100. Funny thing is, I cannot get into recovery, I can only get into bootloader. Last time I was in recovery, it was saying I could not mount the SD card and I could not mount through usb either. When I try to go to recovery now I get the white evo screen, it goes black, vibrates 5 times and I get a blinking green led. So far the majority of the threads I have read say I have to eat the $100. Others say the battery overheating caused a hardware problem. Just want to see what anyone else thinks. Thanks to all the developers and all the people that can make this stuff happen. I appreciate all the support even if it is to tell me I have to eat the $100.
Hello all, I have an HTC Arrive running LEAD's 7.8 8858 ROM. I've been running this rom since January with very little issues. However, within the last couple of weeks I have been noticing strange things going on with my phone. Some mornings I have woken up and left for work and notice my phone is almost dead, even though I remember plugging it in the night before. Also, as of this week, after a reboot of my phone, the Call button shows Home Service instead of Sprint, but eventually changes over to Sprint. At times I will go to use my phone and see it has put itself in Airplane mode or has a locked sim card logo displayed instead of signal bars. In this case I have to reconnect to the network to regain functionality.
Now as of last night my phone is constantly rebooting while charging. I plugged it in last night and kept hearing a buzz (I keep it on vibrate), looked at the phone and it would be booting up. It fully boots to the Start screen and I can go ahead and begin doing something, but no matter what I'm doing it just shuts completely off without even saying Goodbye (literally). It continues to do this until I unplug it, and it ONLY reboots when plugged in. I've tried a battery pull a couple of times but to no avail. Its getting very annoying because it takes much longer to actually charge, and I also don't imagine this is very good for the phone itself.
I was planning on flashing LEAD's latest release to see if it fixes it, but I'm not sure if the phone will react this way plugged into the PC as well. I haven't plugged in to the computer yet to find out, hopefully it won't do this, else I won't be able to flash it.
Any ideas or suggestions? Has anyone else had this issue?
well i plugged into the pc and it still reboots however, when in the tricolor bootloader it does not reboot! so with this discovery i now know that its a bug in the OS causing the reboots. also, because its not rebooting in the bootloader, i should be able to reflash without issues, correct?
as a side note, the phone got VERY hot last night while left in to charge, so i will just charge my wifes phone and swap the batteries so that i wont damage my phone.
no one else has reported this issue with this ROM as far as i can see, only random reboots.
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
leadpoizon said:
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
Click to expand...
Click to collapse
thanks for the reply lead! i am going to flash you latest release now. i am going to look for an alternative way to backup pictures outside of Zune and the PC, but i dont think any exist.
i will post back when its up and running.
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
x_orange90_x said:
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
Click to expand...
Click to collapse
No problem. Glad your issue is fixed now.
Ok so I am no longer having the charging or battery issues anymore, but now my Marketplace is basically broken. When I can manage to begin a download it immediately goes to Attention Required, and upon clicking i get error code 8000ffff. So no apps will install/download from Marketplace. Also, on almost every game and app, it says this app is not available for your device, even ones i used to use on 8858. Some i have even manually installed and they work fine. Also when trying to even view many of the games in the Marketplace, I get error 805a0194. So far I haven't managed to install anything from the Marketplace aside from the Bank of America app.
I have tried resyncing with Live, rebooting the phone, tried changing Marketplaces and settings with the Marketplace Config app. Nothing fixes it
Any suggestions?
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
x_orange90_x said:
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
Click to expand...
Click to collapse
Sorry, I've moved on from this device, so I can't test anything now. I never had any issues like this on my device and I used it extensively for a long time after flashing that ROM.
Out of nowhere my phone started to restart randomly to the point when it looks like a boot loop. Also I have noticed that those boot loops occurs when my battery is below 50% and when I'm charged to 100% I can boot but after 3-4 minutes it goes to restart anyway. Also when I have turned off WiFi, GPS and BT there are no more reboots so far but I'm not able to turn on back WiFi, GPS or BT unless I will pull battery out and put back and turn on them back quickly but then I'm getting back those random restarts.
I'm on a stock but rooted Lollipop with TWRP.
I saw some threads with similar issues and were related to a battery but in those cases phones stay up when were charged or a battery pack and mine has still if is connected to the wall or a battery pack.
Any clue what is going on?
Thanks
OK now I'm not able to get to the Factory Reset screen (Power + Vol Down). Any clue on that?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
Also when I try to flash stock it goes for about 6% and stops saying something like can't change to download mode.
Is this phone dead?
So now I have issues to get started that phone. Mostly goes into boot loop mode (LG logo, LED flashes few times and reboots). Sometimes it goes beyond LG logo - to AT&T logo and reboots there. When I pass that I have a luck and I can get phone to work but I need to disable WiFi, BT and NFC.
Also I have got into MiniOS and run that ATT testing tool which came all passed except one - OTG or something like that failed.
Any help?
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Wish I could help. I'm having a similar problem on CM13. After a few dozen posts asking for help with 0 replies, I've decided you now modify your software entirely at your own risk and if something goes to hell you either have to install a different ROM or buy a new phone.
Click to expand...
Click to collapse
try a new battery @TheNetwork @Scyzor
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
TheNetwork said:
I think android modification is dead man. There's a bunch of junk devs that release crap that isn't even worthy of being flushed down a toilet, then provide no help to users with problems. At best they tell you that it's your fault then ignore you.
Click to expand...
Click to collapse
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
harffmut said:
try a new battery @TheNetwork @Scyzor
Click to expand...
Click to collapse
Zahr said:
I ran into those constant bootloops on every ROM I tried, including when I factory restored to KitKat unless the phone was plugged in. I got a new battery (then recently replacing that one with a newer & good 6,800mAh for under $20 because it drains way too fast) & bootloops stopped.
Sent from my LG-D850 using XDA-Developers mobile app
Click to expand...
Click to collapse
I have got two batteries week ago. One original replacement (3000 mAh) and some OEM (3500 mAh) - both were failing into boot loop until I will get to be lucky enough after full charge over the night and boot to the system and leave it as is but last Tuesday my screen started to fade away instead of turning off and after that it went again into boot loop.
But I don't have any problems booting into recovery (TWRP) or DL mode. Strange...
Scyzor said:
I think this is sad but true :\ All PROs are gone to different phones or newest releases and only LG G3 fanboys left with bunch of "supporters" from Asia. Anyway I'm going to dump LG and will wait for new Google Nexus.
Click to expand...
Click to collapse
This happens with all phones as devs are like anyone else. They upgrade their devices and focus on the new device. Some sell their old device to offset the cost of the new one. Development takes time and many of these individuals have lives outside of development. They have jobs and/or families. What they do is for the fun of it and so they can get more of what they want out of Android. If they share it, then that is up to them and does not mean they owe support to those who choose to use their ROM(s). The fact that a development site lets non developers use ROMs that are uploaded is a privilege and I'm thankful for it. I'm not a developer but have been able to use info from here to get more of whst I want from my phones.
Strange problem. Battery full, no problems there. After getting mad about sdcard not being recognized, even with cm 12.1 , I decided to install cm 6.01 rom(marshmallow) nightly. Installed, changed launcher to nova prime, right gapps, and installed kernel auditor. Downloaded xposed for marshmallow, rebooted, everything was fine(or so I thought). Two days later, coming back from store, looked at my phone and hit power, to get it out of sleep. That's when everything went wrong. It didn't come back, and no pressing of the power button did anything, I had to battery pull. I rebooted to twrp, and over the next week tried to get it right. Uninstalled cm 6.01 nightly, and put xneon rom on it. Same problem persisted, no boot to the os, or partial boot to the lockscreen. I knew the phone wasn't hard bricked, since twrp was still working, and phone wasn't shutting down to no response. Whenever I tried to boot into the os' , it would still get stuck on startup, though. I read all of the advice to return to stock, using flashtool, or lgup, going into download mode, everthing that I could read up on, and implement. I ran to best buy, and ordered a huawei 5x, and said to myself, I can't fix it. Well, today, I said why don't I short the battery pins, and repeatedly press the power buttons, at the same time( because when i put the battery in, even after 10~15 seconds, it would boot to the lg logo, then fade to non-responsive again). Viola! it booted into the os' , and didn't shut down to unresponsive condition(no power button action, and ultimately, battery pull). It seems everthing was fine, until I used the browser, then condition came back. Battery pull again, and it's working now, haven't shut it down since, so I adjusted the display off time to 30 min. , and turned off power saving modes. I don't know if it's truly fixed, but I thought my phone was going to my archives history drawer(all my other phones still work, but they're underpowered, old os' phones). It may still go there, once I pick up my huawei, but I'm glad to see it still living. Is there some type of time out I'm not aware of? or a shutdown by internal fuse, or reset that's built into the firmware? I've heard of bad screens with this, but didn't think that was the problem, since, when in twrp, it never shut down to being unresponsive, and when twrp shut off screen, it would come back, even after hrs of it on. I want to know if the bootloader has anything to do with this, and by shorting it, cleared the emmc.
I have made a video how it looks on my LG G3:
PS.
Is there flashable CWM for D850? I have heard that TWRP is creating those issues from the video.
Well, based on some articles it looks like a hardware issue mostly related to the overheating and "cold soldering joints". Based on that article most of LG phones may experience that issue:
http://www.androidauthority.com/lg-v10-bootloop-problem-711334/