Related
Here's my story.
Rooted my phone about a month ago (used the PBI one, you know what I mean?) and when I did I loaded it in the root folder, rebooted, held END+VOL DWN, hit action, and away it went. Since then I've tried a few times to update to Evil Eris 4.0 using the same methods (I'm 100% newb when it comes to all the terminology) and long story short I followed all the instructions and it just sat there like a brick with the "Green Droid and big triangle with a ! in it" screen (which I interpret as death) but found that if I just plugged it into a computer (Mac or PC) it'd load back up into whatever rom I was using fine. This morning I got jazzed about KaosFroyo V. 34 and tried to install that the same way (END+ VOL DWN) and again got the "!" screen making me run to school to plug it in ASAP.
With all that said, what am I doing wrong? I'm such a crazy newb about all this its ridiculous so please don't reply with a lot of jargon, step by steps would be greatly appreciated. I don't HATE my current rom (the maps crash a lot but they do work) but I just wanna be one of the cool kids
Would a bought Rom Manager app help? I've heard lots of negative stuff about the clockwork mode and that it can ruin your phone.
GreenLanternBatman said:
Here's my story.
Rooted my phone about a month ago (used the PBI one, you know what I mean?) and when I did I loaded it in the root folder, rebooted, held END+VOL DWN, hit action, and away it went. Since then I've tried a few times to update to Evil Eris 4.0 using the same methods (I'm 100% newb when it comes to all the terminology) and long story short I followed all the instructions and it just sat there like a brick with the "Green Droid and big triangle with a ! in it" screen (which I interpret as death) but found that if I just plugged it into a computer (Mac or PC) it'd load back up into whatever rom I was using fine. This morning I got jazzed about KaosFroyo V. 34 and tried to install that the same way (END+ VOL DWN) and again got the "!" screen making me run to school to plug it in ASAP.
With all that said, what am I doing wrong? I'm such a crazy newb about all this its ridiculous so please don't reply with a lot of jargon, step by steps would be greatly appreciated. I don't HATE my current rom (the maps crash a lot but they do work) but I just wanna be one of the cool kids
Would a bought Rom Manager app help? I've heard lots of negative stuff about the clockwork mode and that it can ruin your phone.
Click to expand...
Click to collapse
It sounds like you don't have Amon's recovery flashed yet.
This is probably the easiest thing you can do.
http://forum.xda-developers.com/wiki/index.php?title=How_to_flash_Recovery_Image
or this
http://forum.xda-developers.com/showthread.php?t=742228
In either case, you need to read, and educate yourself.
Precursor - If you run a back up program like Titanium Back Up or MyBackUp Pro, now would be a good time to do that.
I think your main problem is that to get into Recovery mode, you need to hit Volume Up + Power (End). Once there, I'd suggest going to Back Up/Restore and doing a Nandroid Back Up. This will save the entire state of your phone just as it is before you went into Recovery. Exactly as is. Next, go to Wipe, and select options 1 - Factory/Data Reset and 2 - Dalvik Cache. If you don't already have the KaosFroyo-v34.zip file on the root (meaning NOT in a folder) of your card, you can go back to the main Recovery screen and select 2 - USB MS Toggle which will mount your SD card to the computer and you can drag and drop the file from there. Once you've followed these steps, now you are ready to choose option Flash Zip from SD card. Select the zip you need and let it do its thing. You didn't mention if you had apps2sd set up not. If you don't, ignore this next part, if you do, pay attention. IF and only IF you were using apps2sd then you will need to reformat your card to work with Froyo roms. Froyo already has the benefit baked into it but it utlilizes it in a different way. To reformat, you will want to copy everything from your SD card to your computer, then in Recovery, go to Partition card. For Ext and Swap sizes select "0" and then hit ok for partition the rest of the card in FAT32 format. Done. You can add back on contents from the SD card in Recovery through the USB Toggle mode or after you boot everything up, it does not matter (the only difference being that your computer will ask if you want to copy and merge folders if you do it after you boot because it will remake some of the folders for you on booting) . With that being said, now it's time to try out KaosFroyo! The first boot WILL take awhile and the phone will be very slow once it does boot as it has to Sync all of your info and applications back from the Market. Once that gets finished, then you can restore your data if you saved it through Titanium or MyBackUp. I usually like to give it a reboot after all this fun stuff, just to give it a chance to gather itself, if you will. After that, you should be good to go with learning the ins and outs of Froyo Hope this helps!
Did you make a amon backup before you first rooted you phone? I had that same problem when I flashed Kaosfroyo v34. I would boot up in recovery (Vol up+end) and I would have the android with the ! above him. I started freaking out. What I did was restore my nand backup back to 2.1. Then I re-rooted back to KaosFroyo v34. Then went into recovery and everything was good. My advice, unroot then root again. Maybe its not the best/easiest way, but it did the trick for me. And as always, search the forums, there is a post for almost anything. Hope that helps.
EDIT : I am now offering a $100 reward via PayPal to anyone that can offer me a solution to this problem. If you do not have a PayPal account, I will mail you a check for $100. Those are my only methods for payment. I am 100% serious about this by the way. From what I'm told, Nandroid backups are stored on the internal SD card, so even once the replacement phone arrives, I could not restore the nandroid backups on the (currently) broken phone over to the new one. I absolutely HAVE to get to those backups, and it is well worth $100 to me. NOTE : to be eligible for the reward, you MUST read the entire thread. I have already exhausted many common solutions to problems like this one, and am getting tired of getting offered the same advice over and over. If you fail to read the thread and offer me a solution that I have already attempted, I will not give you the $100 reward, even if you later are the one that comes up with the solution to my problem.
Please delete my other threads, I can't edit the title on them and they are outdated now.
This is my situation in a nutshell.
Downloaded Obsidian v2, wiped and flashed it. (this is my girlfriend's phone) - she did not like 2.2, so I wiped data/cache and attempted to restore the nandroid backup I had made. After hanging on 'restoring data' for 30 minutes I rebooted the phone, and now I'm here. The phone boots to the Vibrant logo only, I can get absolutely no other logos to show up no matter what I do. I realize now that I needed to flash a 2.1 kernel prior to restoring the Nandroid backup, but on my Droid, when I restore a nandroid backup that includes the kernel, so I did not know this step was necessary.
I have downloaded Odin but I have NEVER used it, so I am completely lost there as well. As far as I know, I simply need to download Odin, and then follow one of the many methods to access download mode. I have tried about 15 different methods of holding the buttons on the phone, plugging in the USB cable at the right time, etc. etc. etc. None of the methods work. The phone boots up to the Vibrant logo each and every time, no matter what. I downloaded and installed the Kies software so the drivers should be installed.
What do I do now? The phone is not hardware locked because I've used the buttons to access recovery many times. Is there a step I'm missing when it comes to Odin or do I just download it and open it? PLEASE give me instructions as if I am a child, because obviously whatever I'm doing is not working. PLEASE no vague instructions. I do not know how to use adb, odin, or basically how to do anything at all with this phone. I am a Droid user, and after I get her phone back to the way it was I will never attempt to hack it again. Thank you.
edit : also, yes I have pulled the SD card/SIM card.
I'm ready to give up on this.. is it possible to return this phone to T Mobile for a replacement, and if so, will her nandroid backups and titanium backup info be stored on her SD card? Then I could just root her new phone and restore the nandroid backup and be done with it. I promise, once I find some kind of solution, I am never hacking a Vibrant again. Far too complicated to hack non-stock google phones.
use Odin 1.3 or maybe higher
velocity92c said:
I'm ready to give up on this.. is it possible to return this phone to T Mobile for a replacement, and if so, will her nandroid backups and titanium backup info be stored on her SD card? Then I could just root her new phone and restore the nandroid backup and be done with it. I promise, once I find some kind of solution, I am never hacking a Vibrant again. Far too complicated to hack non-stock google phones.
Click to expand...
Click to collapse
I'm at work but do a search for odin 1.3 which worked for me. There is a thread that had all the files you need to get the phone back to stock kernel and all. If you haven't resolved the problem by tomorrow I'll try to find the thread for you or post the files if I can from my computer.
I'm already using 1.3 and I've already downloaded the all in one pack of files I need. Still can't get past the Vibrant screen to use Odin. I'm guessing since nobody has responded back with a way to fix this that I'm hosed, so can I take the phone to a TMO store and get a new one?
Download Mode
velocity92c said:
I'm already using 1.3 and I've already downloaded the all in one pack of files I need. Still can't get past the Vibrant screen to use Odin. I'm guessing since nobody has responded back with a way to fix this that I'm hosed, so can I take the phone to a TMO store and get a new one?
Click to expand...
Click to collapse
Have you tried turning the phone off then while holding the volume down button only, have odin running and plug in the usb cable to the phone? It should power on into download mode like that.
Email me [email protected]
The best phone in the world
I have literally tried every possible combination of holding down buttons, powering up, usb cable in, out, etc. etc. I searched the forum and tried at least 30n different "surefire" methods. Odin always sits there and does nothing, and the phone just goes to the vibrant screen.
jaliscojorge said:
Have you tried turning the phone off then while holding the volume down button only, have odin running and plug in the usb cable to the phone? It should power on into download mode like that.
Click to expand...
Click to collapse
I had to build an extremely ghetto Jig, which is just a 301kohm resistor going across pins 4 and 5 of a microusb plug. It sounds hard but its really not that bad, and unfortunately its the only way to get your phone into downloader mode if its hardware locked, like mine is.
As mentioned previously the phone is not hardware locked. I've accesssed recovery several times with the standard methods. Just got back from Tmobile and it will be a week before the new phone gets here. There has to be a way to fix this. Someone please help?
This is pretty weird because if the phone is not hardware locked, there's no reason that you can't get into download mode.
Just to be clear, so are you saying when you hold vol up + vol down ONLY, you will get vibrant screen?
Or when you hold volup + vol down THEN plug in the usb, it goes to Vibrant screen?
You need to be in download mode to use Odin, not recovery mode. Have you ever gotten into download mode via hardware? Was 'usb debugging' enabled? If so, go into download mode and follow Eugene's Froyo that doesn't brick.
I don't know how I can be anymore clear that the phone is not HWL and I cannot access download mode. I'm not trying to be an ass, it's just a very frustrating situation. I know you need to be in download mode to use Odin. I cannot get to download mode or this would be a cinch.
And to the poster before ^ this one, the phone goes to the Vibrant screen regardless of what button combination I press, or whether or not I hit any buttons at all. I've literally tried every combination possible, many many times.
I'm ready to throw this phone out the window. I have a hard time believing I am the only one to ever have this issue. It seems as though the answer to most problems is download mode + Odin but that does me no good.
Is there literally nothing else I can try?
From what I understand email thegreat520 he is supposed to be the guy to talk to I've heard it from a few posts
Still flashing
I know it can be frustrating, but excuse me for starting with the basics...
have you followed this youtube guide? I put it in the sticky because it was very helpful in my opinion.
http://www.youtube.com/watch?v=AnY7P14JSWQ
Here is another way I have not seen before:
http://www.youtube.com/watch?v=E9LYLoK1Qog
and why not post another
http://www.youtube.com/watch?v=rqxearzXrVY
I had the same issue search my post I used a froyo Rom when the phone 1st came out I download then something went wrong will flashing a new Rom I tried and tried odin did not work bc NO download mode I had got my phone the day it came out I just sent it back to tmobile pm ill explain how
Sent from my SGH-T959 using XDA App
Same issue
Used download mode many times, then did the same exact thing you did with the obsidian ROM. Now i cant get into download mode at all.
The method that worked 100% of the time previously (holding both volume buttons and then plugging the phone in while odin is runing) does not work. Tried a bunch of different methods and nothing.
There has to be a way to get around this.
OP, please try the method in the general sticky. It seems to fix the HWL issue.
WOW!
Without even plugging anything in, I:
1) Turned phone off
2) Held Vol. Down + Home button + Power
And that got me into download mode. I will proceed to try flashing back to stock now.
I have tried all the methods in the videos, and the issue is not related to the phone being HWL. It is not HWL. I have used the buttons to access the modes before. So please give me something unique to try besides a button combination, because none of them work. Am I literally the only one in the world that has ever had this problem before? I will paypal someone 50 bucks if they can help me fix this and that's not a lie. Her new phone won't be here for weeks and she is currently without a phone. Maybe I'm doing SOMETHING wrong but it is definitely not a button combination. I have literally tried them all, including with the USB cable in and out, and plugging it in at certain times during the process. Don't you normally get a charging icon when you plug the phone into the computer? All I get is the vibrant screen. Even if the phone is off, if I plug it into a computer without hitting any buttons, it turns on and goes to the vibrant screen. 50 dollars via paypal. You can't beat that. If you don't have paypal I will mail you a check, and no this is not a joke.
So I'm pretty much screwed huh? Can someone tell me if nandroid backups are stored on the SD card on the Vibrant? I will just wait til the new phone gets here and put the old SD card in the new phone and restore it if so.
OK well I have trying my best as a noob to research for 2 days not in and out on how to fix my issue
My friend tried rooting my phone and to install a different rom. I am on 2.1 and unfortunately I got the phone used with 2.1 already on it so I don't know if it was a leaked or legit 2.1 rom, and I am learning as I go here to fix this issue as I have never new how to do this stuff nor have I ever done it.
Where I am at now:
only thing that happens when I hit power is the phone "vibrates then stays on the 3 skateboard screen" or press "volume down + power" and it goes to the Hboot screen. I go into recovery and it goes to clockworkmod and from there after trying to install any roms from the sd card it says on the last 3 lines
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
and every time I go back or power up to the Hboot screen it does not have any "update bar" (I guess if this was done right as I read on other threads there should be some type of update bar) on the right corner or any other options "for me to select" accept:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
and then with some other info above the Hboot highlighted in blue
I have tried formatting the sd card a bunch of times, I did the clearing of the "wipe data, wipe cache partition, wipe dalvikcache" as I read to do over my reading, but I see that if I go under any restore options under clockwork, no files are found for me to back up too so I am seeing he did not back up any of my info, I also have tried using 2 different ds cards.
So more less it looks like my options are to get this fixed from the only place my phone will boot to with options and thats when I press volume + and power so I guess loading whatever I need to my sd card>>if thats an option or am I screwed, I have seen many tutorials but none of them start where my particular position is stuck at in Hboot. this is my only phone and I had to buy a prepaid which is just about out of minutes, I put an add on craigslist trying to get someone I will pay to fix my issue but no luck, please I need help and I will pay u somehow to guide me through this of my exact issue, I was trying to get to rom 2.3 but if it's easier to get back to 2.1 rom then so be it.
PLEASE!~~
Please HELP!
Cheeva316 said:
Please HELP!
Click to expand...
Click to collapse
Got a solution in the making for you, just give me about 30 minutes.
Edit: Maybe 45 minutes lol, sorry i'm testing this before I have you do it to see if it works.
Ok download the following files:
http://www.mediafire.com/?njwqa7axwzyaqgb
http://www.mediafire.com/?f69cl8dc747h0l9
http://www.mediafire.com/?xg8nnqs177xggx4
http://www.mediafire.com/?qxpi5wsx5lzbhbo
http://www.mediafire.com/?4tg67hck7vh1xxs
Edit: Flash the "rootme.zip" first then follow the rest.
Now what you need to do first is extract the "nandroid" file to somewhere you can easily find it.
Now take the folder called "nandroid" along with all the other zip files you downloaded and place them on your sd card. Put your sd card in your phone and power on with volume down+end. Press volume up. Use the trackball to select "Backup/Restore". Use the trackball again to select "Nand Restore". Use it again to select "HT9BGHG01402". Use it again to select "BDS-20110125-0901". Let the restore run, then power off your phone. Turn your phone back on with just the power button, let it run (might even take up to 10 minutes for the phone to start up). Let me know if the phone boots up or not after about 10-15 minutes. This should work and if it does then we can go from there, even to getting you 2.3 if you want.
You might be asking, what the hell is he having me do ? Here's what i'm doing. I made a nandroid backup a few months ago of when I had kaosfroyov39 which is a 2.2 rom. I am going to have you flash MY backup to YOUR phone which when done right, CAN work. Anyway, let me know what happens and remember to give the phone about 10-15 minutes to boot all the way.
Cheeva316 said:
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
Click to expand...
Click to collapse
( Another phone on the precipice of being ruined by someone's cobbled-together "clockwork" recovery. )
If the /system flash memory partition got corrupted in a way that left a lot of pages marked as bad pages, then the /system partition will be "short", and only small ROMs will successfully load into it, if at all. That might be the cause of the above error messages.
But - because you are using Clockwork, there is really no way to know if that is the case, or if you simply have a whole bunch of corrupted ROM files on your SD card. That's because Clockwork does not verify ROM files before it starts flashing them - which allows total garbage to be flashed to the phone. (That's why Clockwork should never be used by newbs).
Here's what I would suggest you do.
- Make sure you are keeping the phone well charged. (Leaving the phone in HBOOT mode will discharge the battery quickly, even if it is plugged in to the charger, BTW).
- Report the exact bootloader version you have - probably 1.47.0000 or 1.49.0000, but it could be something other. Please be precise.
- With the power off, eject the SD card out of the slot and see if you can boot into the normal HBOOT menu with no SD card in the slot. Report your result.
- Boot into the recovery menu and tell us what version # of the recovery you have. If you can determine the details of how your friend attempted to root the phone, that might be pertinent. Again - precise details are valuable; vague hand-waving not so much.
- The Amon_RA recovery has a mode ("USB-MS toggle") which allows you to mount the SD card to the PC. Does your "Clockwork" recovery have this feature, or are you able to put files onto the micro-SD card using a media slot on a PC?
- Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
What I would suggest you do at the moment is to find the SMALLEST Eris** ROM you can find, get it onto your SD card, verify that you didn't corrupt it, and then perform a "wipe data/factory reset" in your recovery and attempt to install it. If you get the same errors as above, then you should definitely NOT try to do a PB00IMG.ZIP or RUU installation. (The current gingerbread ROMs (e.g. GSB v1.4) are pretty small - they only use about 65% of the /system partition.)
I have a flashable "repair" file which might be applicable. It is not a "ROM" per se - it uses some low-level MTD (flash memory) repair techniques, and also flashes into place the original Amon_RA (v1.6.2) recovery, instead of whatever p.o.s. "Clockwork" recovery you currently have on the phone; but I regard it as something which should only be used as a last resort. But - without some more details and testing on your part, I don't feel comfortable about posting it up.
Let me know.
**PS I wanted to ask one more question - this is an Eris we are talking about, right? (I note you were posting in the Hero CDMA forum not so long ago).
Well I want to thank you for replying with such info but it seems that the recovery image file that I reinstalled on the phone was bad cause when it was updating the bar was going up but as it was going through each item it was updating.. I noticed "bootloader in red letters" with I believe saying "error" next to it and then same on another item it tried updating then the phone powered off and now it's dead, tried everything, no charging light comes on, computer (2 different computers) wont reconize it, it's doing nothing at all, I will try to get my hands on another battery but I am broke, but I doubt it's the battery cause I heard with a bootloader error (or damaged) then the phone won't boot up or do anything so I guess the phone is scrap for parts which sucks cause now my friend who started this deal killed my only phone me n my family had, another lesson learned...time to try n sell some stuff on craigslist..damn
Yes it's a Droid Eris...or was! damnnnn...
Again thank you for your help very much appreciated...
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Cheeva316 said:
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Click to expand...
Click to collapse
Well, I am very sorry that this happened to you and my advice to you didn't reach you in time. From the details that you added, I am pretty sure that you indeed have a hard brick.
BUT - the death of your Eris can still help others avoid the same fate. If you can reconstruct the rooting process you went through,
[SIZE=+2]PLEASE LET US KNOW EXACTLY WHAT ROOTING METHOD YOU USED[/SIZE] - and then we can wave people away from it.
When I say exactly, I mean extremely specific: do you still have the download file that you used? If so, push it up to an uploader site and give a link to it. (I think you mentioned unrevoked or something). Do you still have the exact link you used to download that rooting software? Was it Unrevoked? Z4root?
bftb0
I will tomorrow as I saved all the files on my laptop n I am on my pc now, but will do try my best as I am a newb to this phone stuff
Did you try what I suggested or is it too late ?
phone wont do anything so cant do nothing...
Did you find out any more details about the rooting method you used?
might be a couple more days till I can get to it, my laptop is messing up now...all the saved info was on it
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.
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: