I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:
Related
I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!
Hey all,
I’ve heard that the Rezound is impossible to brick, but all I can guess is that I managed to do the impossible.
I bought a used Rezound a month or so ago. The previous owner had already rooted it and upgraded it to ICS – I honestly wasn’t happy he did this and didn’t mention it in his listing; I just wanted a stock phone and didn’t want to mess with rooting. I didn’t know exactly what he had done to it, so my idea was to reflash it myself, so I knew exactly what was on the phone. Battery life and overheating had been a real problem with the phone, so I was suspecting he might have done something to cause it, so I wanted to rule that out before concluding it was a hardware issue.
ANYWAY – I used cwm, backed everything up, wiped the phone’s memory, then booted back into recovery mode to flash the new ROM. I was able to pick the new ROM and get the process started. It worked its way through the process, rebooted, then sat on the intro screen for-ever. No matter how long I let it sit, it would not complete the install. At that time, I was able to boot back into recovery mode, at which point I cleaned out all the data caches, wiped it as clean as I could, and then tried to repeat the install. Eventually, I used every option in recovery mode and nothing made a difference – I never managed to get the phone working again.
In my last effort, I left the phone on overnight, figuring I’d give it all the time I could to sort itself out, settle into the new ROM, etc. NOW, the battery is dead and the phone won’t charge it. If I remove the battery, put it back in, and plug it in, the charge light goes on for about 5 seconds and then turns back off. At this point, the phone is completely dead.
Do I have any options at this point? Or am I just pretty much SOL?
And no, I don’t know WTF I’m doing, clearly the main issue is probably typing on the keyboard right now. Any help is appreciated.
phermes1 said:
Hey all,
I’ve heard that the Rezound is impossible to brick, but all I can guess is that I managed to do the impossible.
I bought a used Rezound a month or so ago. The previous owner had already rooted it and upgraded it to ICS – I honestly wasn’t happy he did this and didn’t mention it in his listing; I just wanted a stock phone and didn’t want to mess with rooting. I didn’t know exactly what he had done to it, so my idea was to reflash it myself, so I knew exactly what was on the phone. Battery life and overheating had been a real problem with the phone, so I was suspecting he might have done something to cause it, so I wanted to rule that out before concluding it was a hardware issue.
ANYWAY – I used cwm, backed everything up, wiped the phone’s memory, then booted back into recovery mode to flash the new ROM. I was able to pick the new ROM and get the process started. It worked its way through the process, rebooted, then sat on the intro screen for-ever. No matter how long I let it sit, it would not complete the install. At that time, I was able to boot back into recovery mode, at which point I cleaned out all the data caches, wiped it as clean as I could, and then tried to repeat the install. Eventually, I used every option in recovery mode and nothing made a difference – I never managed to get the phone working again.
In my last effort, I left the phone on overnight, figuring I’d give it all the time I could to sort itself out, settle into the new ROM, etc. NOW, the battery is dead and the phone won’t charge it. If I remove the battery, put it back in, and plug it in, the charge light goes on for about 5 seconds and then turns back off. At this point, the phone is completely dead.
Do I have any options at this point? Or am I just pretty much SOL?
And no, I don’t know WTF I’m doing, clearly the main issue is probably typing on the keyboard right now. Any help is appreciated.
Click to expand...
Click to collapse
Well, not sure about the installation issues...but the reason the phone died is because you have CM recovery. Known issue .. probably a hundred threads just not recently because people have either switched or don't let their phone run down. Phone can't charge from CM recovery and you need to switch back to Amon Ra recovery. http://forum.xda-developers.com/showthread.php?t=1434532
Basically, pull battery and then replace and hold volume down and power at the same time to boot into bootloader. Plug phone into computer . Put Amon recovery img into the same folder containing fastboot. Then make sure phone is in fastbootUSB . http://forum.xda-developers.com/showthread.php?t=1339679&highlight=amon+ra
Latest is 3.15 .. so once it is placed in the right folder type fastboot flash recovery recovery-ra-vigor-3.15-gnm.img ... this will flash amon ra recovery.. then you can charge. Once charged then you can attempt to recover your rom.
Sounds like you need an external charger to get the battery a little juice. I never thought that it was possible for a battery to not be able to charge because it was super dead unit I saw it happen on a Thunderbolt. You could take the battery to Verizon and have them give it a quick charge, just to get you back on your feet or got to an electronics store and buy a charger (can always take it back). Get it to boot again then work it from there maybe flash the Stock or Leaked PH98IMG just to get back to working so you can breath again..
Getting yourself out of a jam is part of the learning curve in flashing phones.
Yep, known problem with CWM. Plug it in powered off for a long time. It might not seem like it is charging, but it is, very little.
What ROM did you flash?
Also need to know the firmware version.
Once you get into hboot, tell us what radios you have and what version of hboot. You have three options, 2.11, 2.21, and 2.25. Also tell us if it has S-On or S-Off.
All of this is crucial for us to help you get back to stock.
Great, thank you for the good info! I was about ready to toss the thing in the trash, but it sounds like there may be hope yet!
EmerikL said:
Yep, known problem with CWM. Plug it in powered off for a long time. It might not seem like it is charging, but it is, very little.
What ROM did you flash?
Also need to know the firmware version.
Once you get into hboot, tell us what radios you have and what version of hboot. You have three options, 2.11, 2.21, and 2.25. Also tell us if it has S-On or S-Off.
All of this is crucial for us to help you get back to stock.
Click to expand...
Click to collapse
I'll have to get back to you on all of that - I'm not entirely sure right now, and everything is at home. Pretty sure it was a Venasaur ROM.
I wish the mods would delete any and all links to CWM. These threads keep cropping up.
its possible you need to flash the ICS firmware patch as well and thats why its not booting
Sorry to hassle you guys with what has probably already been answered a few times. I did some searching – yes, I should have done a little more - and the results I found were all folks that had phones that would still power on to some degree. I didn’t find many where the phone was completely dead, and if I did the responses were generally, “You’re screwed, throw it out.” Issues with cwm really didn’t cross my mind, so I didn’t think to search on that.
Anyway, I appreciate the help. I’ll sit down tonight and see if I can’t figure this thing out.
It is likely that he is S-ON and if he had a sense 4 rom installed, the new rom won't boot.
To the OP, can you please tell us the hboot version # (2.xx) it is either 2.10, 2.11,2.21, or 2.25. Also tell us if it says S-ON or S-OFF and unlocked, locked, or relocked, or juponutbear in purple at the top.
Easiest way to brick it is to take out battery while flashing a hboot haha.
No worries about the question, we're glad to help (since you didn't post this in the Development section lol)
Anyway, as long as you are S-ON, it shouldn't be too bad of a process, just lengthy. First, you'll need the Android SDK so you can get Fastboot, etc, as well as all the HTC device drivers installed, and you'll need to flash Amon RA recovery over.
Amon RA can be found here:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
**Make sure the Recovery file is in .img format, not .zip or anything, and place in the same folder as Fastboot (which is located in the Android SDK folder).**
You'll need to pull the battery, plug the USB cable into the computer, plug into the phone, replace battery, and hold down 'Power' + 'Volume Down' until the screen flashes the HTC screen. (Not sure if that's the only order, but it works). This will take you into Fastboot.
Next, you'll need to open a command prompt and 'cd' to your folder with Fastboot in it. Type:
Code:
fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
into the command prompt and hit enter. It should show on the command prompt a couple lines of time it took, etc. and when done you will have Amon RA recovery.
Now you will at least be able to charge your phone!! From the phone, you can select 'Bootloader' then 'Recovery' and you will boot into recovery, which will allow you to charge your battery. You can check the charge status of the battery while in recovery in one of the menus, can't remember which one. (Fun tip: you can use 'Home'/'Menu' to scroll up/down, 'Back' to go back and 'Search' to select, since the hardware buttons are so difficult to press)
Once you get the phone charged, you have a couple of options. Since you stated you wanted to go to stock, I'll explain the steps to get back to the state the phone shipped with.
Once you get a good charge, you will also need to re-lock the bootloader to go back to stock, which is also done in fastboot by typing:
Code:
fastboot oem lock
(Get to fastboot by Battery Pull>Battery Put Back>Power + Volume Down, all while connected to a computer, just like when doing the Recovery flash)
BACK TO STOCK::
You can do this one of two ways, either run the revert using a .zip, or as a .exe connected to your computer. Personally, (and I know I'll probably lose credibility here lol) I prefer the .zip method, although many swear by the 'True RUU' .exe method.
**Here's a little aside to get you so you can get all of these files onto your phone. There's an option in Amon RA that mounts as removable storage to your computer so you can transfer files. Select 'USB-MS toggle' and then select 'USB-MS Toggle SDCard'. Then you can transfer all the files you need before continuing.
First, download the stock "ruu" zip from here:
http://goo.im/stock/vigor/ruu/RUU_V..._1.12_9k_1.83_V_APT_release_221502_signed.zip
and you will need to rename it to PH98IMG.zip and it will need to be placed on the root of your SDCard, not in any folder. Then download the MainVer.zip from here:
http://forum.xda-developers.com/showpost.php?p=23169557&postcount=4\
which can be placed anywhere on the SDCard, but I would place it in the same place as the PH98IMG file for ease.
Once you have the PH98IMG file on the root of the SDCard, and have the MainVerLow zip there also, continue on.
To flash, go to the 'Flash zip' menu in recovery, and locate the setMainVerLow.zip. All this does is set the Main Version low, so hboot (or whatever) doesn't kick it back saying you can't downgrade. This flash will only take a second, and when complete, go back to the main Recovery menu.
It probably doesn't matter, but I would wipe data/factory reset again just to be safe. Do this by selecting 'Wipe' then 'Wipe ALL data/factory reset'. Once done, go back to the main Recovery screen.
Now you will want to reboot into bootloader, which I believe is under either 'Other' or 'Developer Options'
The phone will reboot, and book back into a screen similar to what you saw in fastboot. Some purple text will scroll saying stuff about looking for some file, and will find the one you just put on there and ask if you want to update now. Click the power button to confirm the update. It will show a progress bar on the side, as well as list the parts it has updated for you. It will get around halfway done or so and reboot itself, but DON'T TOUCH ANYTHING OR REMOVE THE BATTERY!!! lol it will reboot and finish the second half of the install. Once it's done, I think you need to hit 'Power' one more time to reboot, but once it does you will be rebooted and load up the completely stock ROM that originally shipped with the Rezound. Of course, from here you can go to the system update menu and update to the latest released OTA.
EDIT:: Just wanted to add, none of what I have written was developed/discovered/first-posted by me, it is the work of other, MUCH more intelligent people other than myself. So don't thank me for anything other than putting them all here lol
con247 said:
It is likely that he is S-ON and if he had a sense 4 rom installed, the new rom won't boot.
To the OP, can you please tell us the hboot version # (2.xx) it is either 2.10, 2.11,2.21, or 2.25. Also tell us if it says S-ON or S-OFF and unlocked, locked, or relocked, or juponutbear in purple at the top.
Click to expand...
Click to collapse
Will try to do that tonight.
I need to get it to power up first. I've had it plugged in at my desk all day and no luck so far. Let me get that taken care of and I'll go from there.
See if you can borrow a friends battery. A thunderbolt or my touch 4g slide battery will work too. You can also manually charge your battery by wiring a USB cable directly to it. Then you can get rid of the broken recovery and charge the battery fully.
good luck.. if you figure all this out you might like being rooted. i had several issues coming from an htc incredible to rezound the cwm was one.
Definitely get Amon Ra.
Sent from my ADR6425LVW
con247 said:
You can also manually charge your battery by wiring a USB cable directly to it. Then you can get rid of the broken recovery and charge the battery fully.
Click to expand...
Click to collapse
OK, that looks interesting. How do I do that?
EDIT - NEVER MIND - just found it.
phermes1 said:
OK, that looks interesting. How do I do that?
EDIT - NEVER MIND - just found it.
Click to expand...
Click to collapse
might be worth your while:
http://www.amazon.com/HTC-Thunderbo...ords=htc+thunderbolt+external+battery+charger
It doesn't charge very fast, but nice to have around.
Hopefully im not too late, but click my name and look at the threads that i have started. I used a ghetto IMO method to charge a dead droid x battery. You njeed a useless usb cable and a little time. Basically you strip the red and black wires and respectively touch them to the + and - leads on your battery. This will charge it relatively fast, you only need to hold it on the battery for a minute or so, just long enough.
But use this as a last plan method, i dont know how safe this is because the voltages may go in wrong or damage the battery, but to this day my droid x still works and i got it on the release week so its relatively old.
If you can, you should get a legit charger instead but if you want it done fast, give this a try or find another way. hope i helped but just make sure that if the battery heats up if you try this, you stop immediately. That could mean that the battery is about to explode or its breaking.
hope i helped, but if you want more help there is bound to be youtube videos on how to do this.
If you try this and something goes wrong its not my problem, but i have done this before and it should work.
Here is the link to the forum i made:
http://forum.xda-developers.com/showthread.php?t=1656547
Yakuzagang5 said:
No worries about the question, we're glad to help (since you didn't post this in the Development section lol)
Anyway, as long as you are S-ON, it shouldn't be too bad of a process, just lengthy. First, you'll need the Android SDK so you can get Fastboot, etc, as well as all the HTC device drivers installed, and you'll need to flash Amon RA recovery over.
Amon RA can be found here:
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
**Make sure the Recovery file is in .img format, not .zip or anything, and place in the same folder as Fastboot (which is located in the Android SDK folder).**
You'll need to pull the battery, plug the USB cable into the computer, plug into the phone, replace battery, and hold down 'Power' + 'Volume Down' until the screen flashes the HTC screen. (Not sure if that's the only order, but it works). This will take you into Fastboot.
Next, you'll need to open a command prompt and 'cd' to your folder with Fastboot in it. Type:
Code:
fastboot flash recovery recovery-ra-vigor-3.15-gnm.img
into the command prompt and hit enter. It should show on the command prompt a couple lines of time it took, etc. and when done you will have Amon RA recovery.
Click to expand...
Click to collapse
Update on my efforts. The steps above are where I'm currently at - so I haven't gotten far.
I got the $5 charger as suggested, so my phone will power on and I can at least get to the bootloader screen.
For whatever reason, it will NOT power on if I follow the steps above. It won't power up when I have it plugged into the PC. I can only power it on with it unplugged. So, when I run through the command prompt to install Amon Ra, it seems to be unable to connect to the phone. It displays 'Waiting for device' and nothing ever happens. At this point, it looks like I have everything I need on the PC side, but the phone is too boogered up to communicate with it.
I'm trying the options to clear out the memory right now. The problem there is that it goes to the screen with the top hat and orange circular arrow, and just sits there forever. It never acknowledges that it's done clearing memory.
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
anticlotto_ said:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
Click to expand...
Click to collapse
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
CROSSFREEZE said:
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
Click to expand...
Click to collapse
Thank you for your reply! I have tried hard resetting multiple times, but I had removed some bloatware apps (I will quarantine them next time instead because I don't wanna go through this ever again) and I have tried the kdz method to only be stuck at 15% every time when I followed instructions to the pixel. I have tried to do it on windows 7 and windows 8. I have also tried the fastboot method by lelus, and that manages to "work" but I am still stuck at the tmobile boot screen afterwards. I have gotten the hang of the process of getting into the fastboot, but what do I do from there? I chose to flash ics xloader and uboot, but the process goes by so fast, I'm not even sure it is doing anything. The LG Tool has really gotten me nowhere, it just gives me a lovely error and then cannot continue the upgrade recovery process.
It said somewhere that after I flash through the fastboot I then have to try the kdz method, so I am going to do that now and see if it works. I don't know if there would be a difference between flashing a jb kdz or an ics kdz, but I will just do ics to be on the safe side.
I am quite happy to say that flashing the ics kdz was successful, and my phone is now up and running.
My p769BK is stuck on the LG screen. /: months
Sent from my LG-MS770 using xda app-developers app
im terrible with fastboot, i used the unlock the bootloader for noobs with an offline flash.
heres what i did to get out of bootloops....
alright, this is all from memory but the offline flash didnt work as well for me when stuck in weird bootloops.
Step one-going back to online flash---->
A---
the easiest way i found was to go to C:/windows/system32/drivers/ect/hosts
right click>open with notepad
there should be two lines at the bottom
"127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com"
i would cut them out and paste them in a text doc in the same folder for reference later...
but either way you should remove them from the hosts file and save
B----
Make sure your small server is closed! once you minimize it it should go down to your status bar (shttps)
Step two-LGMS---->
make sure you have LG mobile support installed or install it.
open lg mobile support
install needed drivers for your phone
power your phone off/remove the battery
put battery back in
connect it to your computer holding down the volume up button
S/W UPDATE mode should pop up, if it doesn't preform and hardreset and try again til it works (it will)
then in the top right corner there should be a button or two click them both until you see
"restore update" or Update restore or something to that effect
select that
and let it ride man
i got my phone ****ed many times and just had to keep redoing this until it worked. if your bootloader is truely unlocked you can probably go through all that again and get CM10 working, i did but im still working through kinks.....
GOOD LUCK feel free to ask any more Q's about this process if you run into any problems
This started when my phone was acting out on Viper 4.0 rom and I figured I'd wipe it and start fresh, wiped the phone & ROM no longer booted, went to the forum to see if there is anything new to tryout & found dirty unicorn so I thought hey that's different (for me) let's give it a shot. Long story short the phone never came back until I relocked & used a factory RUU and it worked but phone was now locked & back to stock. Phone is S-Off by the way.
Today was a new day and I was determined to either get a new rom on my phone or go back to Viper 4.0, unlocked hboot & rooted the phone, installed the newest TWRP 2.8.01 and decided ok everything looks good let's see what happens, Dirty Unicorn requires that you copy ROM to internal storage then flash and this is where the first problem occurred; I couldn't mount internal storage so I thought meh I'll just boot the factory rom & connect as USB storage so I did that, back into recovery and somehow internal storage is not in either file manager or could I get to it from the install screen. I gave up & decided to go ahead & flash from Micro-SD which didn't work, tried to wipe & fail, tried to fix permissions and fail, every time I reboot it asked to reinstall supersu so I tried to flash the most recent zip I had and sure enough fail finally one of my zips worked and I hit reboot, that was the end of my phone.....
Right now - phone is completely blank, power does nothing, power+vol down does nothing, power+vol down+vol up does nothing. When I plug the phone into PC it shows up as QHSUSB_DLOAD RUU doesn't work and fastboot commands return nothing.
ummm what do I do?
oh & the second phone was a friend's phone that he gave up on gave to me to fix for him, of course that's bricked too but I have a feeling it'll come back maybe after the battery dies, haven't tried yet. But I need to get my own phone working so I can be back in business.
Whatever recommendations are welcome
Can't wait to go to Samsung lol this or something similar happens every time I try to switch or upgrade rom.
oceanisbleu said:
This started when my phone was acting out on Viper 4.0 rom and I figured I'd wipe it and start fresh, wiped the phone & ROM no longer booted, went to the forum to see if there is anything new to tryout & found dirty unicorn so I thought hey that's different (for me) let's give it a shot. Long story short the phone never came back until I relocked & used a factory RUU and it worked but phone was now locked & back to stock. Phone is S-Off by the way.
Today was a new day and I was determined to either get a new rom on my phone or go back to Viper 4.0, unlocked hboot & rooted the phone, installed the newest TWRP 2.8.01 and decided ok everything looks good let's see what happens, Dirty Unicorn requires that you copy ROM to internal storage then flash and this is where the first problem occurred; I couldn't mount internal storage so I thought meh I'll just boot the factory rom & connect as USB storage so I did that, back into recovery and somehow internal storage is not in either file manager or could I get to it from the install screen. I gave up & decided to go ahead & flash from Micro-SD which didn't work, tried to wipe & fail, tried to fix permissions and fail, every time I reboot it asked to reinstall supersu so I tried to flash the most recent zip I had and sure enough fail finally one of my zips worked and I hit reboot, that was the end of my phone.....
Right now - phone is completely blank, power does nothing, power+vol down does nothing, power+vol down+vol up does nothing. When I plug the phone into PC it shows up as QHSUSB_DLOAD RUU doesn't work and fastboot commands return nothing.
ummm what do I do?
oh & the second phone was a friend's phone that he gave up on gave to me to fix for him, of course that's bricked too but I have a feeling it'll come back maybe after the battery dies, haven't tried yet. But I need to get my own phone working so I can be back in business.
Whatever recommendations are welcome
Can't wait to go to Samsung lol this or something similar happens every time I try to switch or upgrade rom.
Click to expand...
Click to collapse
All of the things you mentioned are user error and have nothing to do with HTC or the phone itself. Now as far as an answer goes to try to get your phone working again, have you tried holding power for 60 seconds? MOD Edit: Unnecessary.
goliath714 said:
All of the things you mentioned are user error and have nothing to do with HTC or the phone itself. Now as far as an answer goes to try to get your phone working again, have you tried holding power for 60 seconds? MOD Edit: Unnecessary.
Click to expand...
Click to collapse
Yes of course I tried, the phone has been absolutely unresponsive. No amount of button holding is going to fix QHSUSB_DLOAD
Correct me if I'm wrong but http://forum.xda-developers.com/showthread.php?t=1948485 is the only known solution for QHSUSB_DLOAD due to firmware issue (I'm pretty sure this is what happened) or Jtag.
Here's the kicker, the files in that thread are no longer there so as it stands phone's just a Brick.
So for now I'm giving up on it and going samsung.
When I have the energy I may try working on the second one I have which turns out wasn't bricked instead the power button is unusable 90% of the time, but for now that's going to be left out of commission. Ultimately I need a backup because sprint techs seem to only operate on a 3 day basis when it comes to physical repairs therefore I plan to revive the second phone just to keep it as plan-b.
May all be user error but frankly what takes me minutes with a samsung seems to take days on the past couple of HTC phones I've had, so the ranting aspect of my post is merely in these regards and that only and out of frustration, this sucks because I'd take HTC build quality over samsung any day. I've been an HTC faithful since their first windows phone (5 years ago or so).
I know I have to fix the power button on the second phone but have any idea why it fails halfway through a factory RUU?
that's where I left off with it, it's S-On Unlocked running TWRP 2.8.0.1 I was trying to return it to full stock so I can have a go with facepalm S-Off procedure.
Did you relock the bootloader prior to attempting to run the RUU?
Magnum_Enforcer said:
Did you relock the bootloader prior to attempting to run the RUU?
Click to expand...
Click to collapse
out of 3 different RUUs I donwloaded only one worked, bootloader was relocked, ran RUU, Error 132 "Signature Error"
the one that did work the installer said finished, phone reboots but goes right back to bootloader where it says "Relocked" & "Security Warning" won't do anything else.
Hello all, got a bit of a strange issue here. So I was using the 30b release from runningnak3d, https://forum.xda-developers.com/tmobile-lg-v10/development/h901-t-mobile-nougat-v30b-twrp-t3639203
I was selling my v10, so I did a reset, skipped or hit next to everything, and verified that all was working. I sold the phone and a couple days after the buyer got it, he told me it was bootlooping. I asked what he did and of course the first time he said nothing, just turned it on. After more conversation, he said when he got it it booted and after a while told him an upgrade was available. He said he accepted the upgrade, and afterwards got the bootloop.
I got the phone back today to try to fix it and give it back to him. Here's what I have found. Definitely bootlooping, stops at T-Mobile logo and reboots. It does still have the unlocked bootloader, still shows the warning right at boot. TWRP is gone! I booted to recovery, answered Yes to those 2 questions, and it did a reset instead of loading TWRP.
I really have no idea what he did, whether is was an OTA update or maybe he tried to load something on his own.
So, is there any hope of getting this thing going again? So far I was able to boot it into download mode, but it won't respond to any fastboot commands. My computer detects it, but in computer management it says LGE USB modem or something like that. When I try to regular boot, the computer does detect the phone, but it doesn't get far enough along to issue ADB commands. I'm thinking it's a paperweight at this point, so I'm game to try whatever.