Related
Im going to lose my mind! I've searched and read and found no real answer..... Is there anyway that I can get my phone out of the boot screen?
Ive downloaded and rooted before and never had a prblm! I download this certain Rom Lastnight and all of a sudden my phone is stuck on the boot screen! I've tried everything i can with it and no luck. Does anyone have some type of info on what i can do or is there no hope for my poor lil droid?
Please let me know!
Thanx in advance!
Have you tried a battery pull? Pop that out and back in, reboot into recovery and restore your nandroid back up. Should be fine from there...
What I do when this happens to me is pull the battery, wipe my phone, re-apply the rom, then reboot.
-If that does not work, then revert back to your nand backup.
Thanks for the ideas but I tried both of those actions first and got nothing in return. This sukks! I even tried to go back and load the PB00img zip tha i had and no go. I'm guessing that i Bricked this dam Phone!
Back to the Blackberry! Damn!
Do you think its possible that i can load a new Rom and try to boot the phone into recovery and flash that zip? The problem seems to be my boot screen! I've seen post with people with similar "situations" <--------lol (not From Jersey shore) and tried those methods and once again nothing.
Sucks that you are still having this issue. The next step I can think of would be if you have SDK set up then once it is stuck on the boot screen, run a logcat and post it here so someone that is smarter than I can figure out where you are running into problems at. You'll need to navigate to your SDK/tools folder (in the Command window of course...) and then once there just type in: adb logcat .
This will result in a myriad of crazy computer language stuff. Should be able to tell us something at least.
First, take a deep breath; your phone is not bricked. Far from it in fact.
Second, prove to yourself that it isn't bricked by booting it into the custom recovery:
Power it off, and then hold down Vol-Up (first) and the End (second); keep pressing both buttons until the three skating droids have appeared. The custom recovery menu should pop up about 10-12 seconds after that.
Third, download "some other certain ROM" (I get to be as vague as you are, right?) to your PC, and get it to the root folder of your SD card somehow. Look up "USB-MS toggle Amon_RA" if you don't already know what that is.
Fourth, flash that "some other certain ROM" and prove to yourself that your phone is not bricked, making sure that you perform a "Wipe data/factory reset" first before you flash the ROM.
Then, after you've shown yourself how it is possible to do these steps, go back and try to figure out why the other "certain ROM" doesn't work on it's first boot. Try popping out the SD card before you boot it to see if that is the trouble.
bftb0
@es0tericcha0s, Thanks for the response but instead of doing more harm to the phone i just took it to VZW, (Kinda) Explained what happen and they switched it out no prob.
@bftb0 lol Be as Vague as possible.... I didn't want to say any particular Rom for the simple fact that who ever did the Rom i'm sure worked hard at it, And evevn tho i'm not new at this, it could very possibly be my mistake somewhere in installing it! SO I choose to respect the XDA and The Dev But thanks for your awesome response! (no Sarcasm intended) lol
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.
My wife and I recently traveled to Chicago and on the bus ride there, she turned off her eris to conserve battery. When we arrived in Chicago, she turned her phone back on and it gets stuck on the screen with the droids on skateboards. We let it sit for an hour plus with no results. I have searched for resolutions on this site, but all I could find were issues with already rooted phones.
When I go into the system recovery, I get a message E: can't open /cache/recovery/command. I wiped cache partition and wipe data/factory reset and rebooted and it still gets stuck.
I also downloaded the latest OTA update and renamed it to update.zip and pasted it on the sd card and tried to apply sdcard:update.zip but I get a message E:signature verification failed.
Is there anything I can do to resolve this problem and get the phone to boot? Is there a way that I can root the phone even though it wont boot up? We went to a verizon store and that was pretty much a waste of time.
Thanks for the help.!!
thats crazy man. you have no nand backup? i got in a bootloop once but i was rooted. i downloaded a random rom and booted to recovery then mounted usb and transfered rom to sdcard then flashed it and it booted right up. i would think if you got the click root program for eris and flashed it in recovery and then flashed a rom it would work but im not sure im no excerpt. hope you figure it out
kd,
The procedure you used (wipe data/factory reset using the stock recovery) should have worked with a non-rooted phone... assuming that all the hardware was still OK.
You should not have experienced a verification failure applying a valid OTA file as an update.zip, but it is not obvious to me that you should be trying to fix the problem that way in any event.
If the phone is under warranty, I think that the right thing to do is contact VZW or whomever sold you the phone about warranty return. Only if there is NOT a warranty available would I consider further "repair" experimentation on your part.
Let me ask a single question before I give any other advise: what bootloader version is on your phone? (You should see this in the HBOOT or FASTBOOT screen); probably it will be one of these three:
1.47.0000 S-ON
1.49.0000 S-ON
1.49.2000 S-OFF
I would advise you to avoid trying PB00IMG.zip or "RUU" rom reflashes at the moment. I can provide "cautious" instructions about how to proceed; but first- what bootloader do you have?
bftb0
I have contacted VZW and the phone is not under warranty so she is pretty much stuck with this phone.
Here is what I see on the bootloader screen:
PB00100 XC SHIP S-ON
HBOOT-1.46.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-MELFAS_45_17
RADIO-2.42.01.04.27
Oct 5 2009, 19:21:56
Any instructions would be GREATLY GREATLY appreciated!!
Thanks
kdcroswell
kdcroswell said:
PB00100 XC SHIP S-ON
HBOOT-1.46.0000 (PB0010000)
Click to expand...
Click to collapse
This is hopeful.
What I am going to suggest is that you proceed carefully by flashing as little as possible to the phone; the first step is to get the engineering bootloader onto the phone. (In principle, this could allow recovery of 100% of your wife's current configuration and data.) The top-level "outline" of the plan I have in mind looks like this:
- flash ONLY the 1.49.2000 S-OFF bootloader to the phone using the Root PB00IMG.zip file and the "toastcfh" battery pull trick using HBOOT.
- soft-boot a custom recovery to the phone without flashing it (this uses the PC utility "fastboot")
- Immediately make a Nandroid backup of the current contents of the phone.
- Perform a diagnostic "flash" that will report on the state of the MTD partitions.
- Make a decision on how to proceed from that information.
Before we begin, though, we should get a couple of preliminaries out of the way.
(A) You need to have a method to be 100% sure that the files you download to your SD card are in "perfect" condition. If you don't know what a "MD5" signature is, you should review what that means and then download a utility (either from Microsoft, or even better, an opensource GUI tool) to your PC that will allow you to compute "MD5" signatures of files that you download from the Internet.
Simple mistakes in transferring large files to an SD card can cause them to be truncated or corrupted, and this can have disastrous consequences if you flash a corrupted file to your phone. Making sure that you check the "MD5" checksum of the files you download - after you have transferred them to the SD card will prevent this kind of trouble. (This type of error might be what caused your trouble with the "update.zip" you used which failed a verification/signature step)
(B) The method I am going to suggest requires you to work at the command line of your PC, and also get some USB drivers installed. The easiest way to install the drivers is probably to run the "Official 2.1 RUU" Utility right up to the point where you would attempt to flash the phone - but DO NOT actually begin the flashing procedure. You can get that RUU Utility from this page:
Consolidated HTC RUU, Leak, and OTA Downloads
The RUU Utility you are looking for is listed on that page as "[ 2.36.605.1 ] a.k.a. "Leak-V3" (or MR3/"Official" RUU) - (Eclair/2.1)" -
RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe
Note that the file size and MD5 checksums are given on the above-mentioned page; use this download to familiarize yourself with computing MD5 checksums with whatever tool you decided to use.
Here's some other downloads that you should pull down to your PC in preparations for all of this:
1) The Amon_RA custom recovery (v1.6.2) - file name: recovery-RA-eris-v1.6.2.img
2) The ROOT PB00IMG.zip file - [ 2.19.605.1 ] Find this in the above URL "Consolidated HTC RUU..." - file name: Eris_RootROM_v2.19.605.1_PB00IMG.zip
3) The fastboot utility for your PC/Mac/Linux machine; you can get this from HTC about midway down this page. (Note that this page also provides you a MD5 checksum.)
I would suggest that you get your PC set up with drivers, and verify that you can communicate with your phone with the fastboot (command-line) utility, before you start doing anything to the phone. This could go smoothly, but probably depends on what O/S version you have on your PC. As I said, the easiest way to get drivers installed onto your PC is to run the RUU Utility right up to the point where you would begin flashing stuff to your phone (but then you exit that utility without actually starting the flashing operation.).
In both cases - the "dry run" of the RUU to install the USB drivers, and the communications check with the "fastboot" tool, you will need to put the phone into fastboot mode; this is done by powering the phone off completely, and then turning it on by holding the Send key and End/Power key together (make sure to press the Send key first). If you do this (and the phone and PC are connected with the USB cable), you can verify communication between the PC and the phone with the fastboot command with:
Code:
fastboot devices
If the USB drivers on your PC have been installed correctly and you are communicating with the phone, the above command will print your "device ID number" on the screen.
Once you get to this point, come back here and give a status update, and I'll provide some further instructions. (Also, since I don't know what your skills are - you might mention whether you are familiar with using the command line or other rooting/phone manipulation methods - reading between the lines, I see that you are more skilled than most of the newbs that come here looking for help)
If you get this all set up, you can also review the following descriptive article (with pictures) on how to do the PB00IMG.ZIP install - including the "battery pull trick".
You can also review a description of how to make a Nandroid backup.
bftb0
PS - One more thing to remember. While the phone is in an unusual state, it is a good idea to keep it fully charged. Don't let it sit in either HBOOT or FASTBOOT modes for extended periods of time - the phone will discharge even if it is plugged in to the charger. You can leave it in that mode for 5-10 minutes, but don't let it sit in either of those modes unattended.
Don't want to threadjack, but for easy MD5 checking on Windows or Mac, you can use HashTab (which is awesome). I can't direct link yet, but: www [dot] implbits [dot] com/Products/HashTab.aspx
I have downloaded the RUU utility and ran it to install all of the needed drivers. I have also downloaded the fastboot utility and verified that the phone and PC are talking by using the code you provided.
I have also downloaded the Amon_RA custom revovery and the ROOT PB00IMG.zip file and verified the MD5 signature for both files.
I read the link on how to do the PB00IMG.zip install including the battery pull trick and the link to how to make a nandroid backup.
I didnt do anything else but verify that the phone and PC are talking and downloaded the files that I will be needing.
I am not real familiar with rooting phones but the instructions you have given me so far are easy to follow.
Now that we verified that the phone and PC are talking, what should I do next?
Thanks again for all your help!!
kdcroswell said:
I have downloaded the RUU utility and ran it to install all of the needed drivers. I have also downloaded the fastboot utility and verified that the phone and PC are talking by using the code you provided.
I have also downloaded the Amon_RA custom revovery and the ROOT PB00IMG.zip file and verified the MD5 signature for both files.
I read the link on how to do the PB00IMG.zip install including the battery pull trick and the link to how to make a nandroid backup.
I didnt do anything else but verify that the phone and PC are talking and downloaded the files that I will be needing.
I am not real familiar with rooting phones but the instructions you have given me so far are easy to follow.
Now that we verified that the phone and PC are talking, what should I do next?
Thanks again for all your help!!
Click to expand...
Click to collapse
OK.
(1)
The first step is to charge the phone fully, and attempt the HBOOT+PB00IMG.zip install, using the "battery pull trick":
- charge the phone completely.
- move the "PB*.zip" file to the SD card top-level folder, making sure it is renamed to "PB00IMG.zip".
- Make sure to verify the MD5 of the PB00IMG.zip file on the SD card - not the copy on your computer.
- Turn your phone off.
- Take the back cover of the phone off.
- With the phone off, pull the battery a couple of times and re-insert it to get familiar with how long it takes to pull the battery. You should try to do this within one second of the screen going dark (please re-review the instruction post on AF). The timing is not super-critical, but when you press the button to start the flashing, the "bootloader" flashes very rapidly - something like 1/4 of a second, and then the screen goes dark. Practicing the battery pull will get you used to it.
- Re-review the instructions in that "Visual Example" post over on Android Forums
- Start the phone in HBOOT mode (Hold Vol-Down+End key).
Hopefully, you will not get a "Main Version is Older!" message after HBOOT unpacks and inspects the PB00IMG.zip file. If you do, proceed no further and report that result.
- Accept the flash (start it), and then pull the battery as soon as the screen goes dark. Do NOT pull the battery before the screen goes black - do it as soon as possible after it goes black.
If this all goes well, you should be able to re-start the phone to see if the bootloader flashing occurred.
DO NOT start the phone in HBOOT mode, because the PB00IMG.zip will repeat again., Instead, after you re-insert the battery, start the phone in FASTBOOT mode: Send+End.
You should see "S-OFF" and "1.49.2000" if the flash succeeded.
(Note: some people have reported that occasionally, the "flashing" process will continue after powering up the phone, even though this is not the desired outcome. I have done the "battery pull" trick with the HBOOT+(Root) PB00IMG.zip install perhaps 50 times, and I think it happened to me twice. If this occurs, don't panic - just let it go to completion.)
(2)
If the flash succeeded, put the phone into FASTBOOT mode (Send+End), and perform a soft-boot of the Amon_RA image:
Code:
fastboot boot recovery-RA-eris-v1.6.2.img
The easiest way to make this work is to have the "recovery-RA-eris-v1.6.2.img" file in the same folder that you have the "fastboot.exe" program in (unless you have changed your PATH environment variable to include that location; in that case you can run the program from any "current directory").
This is one of the features of the S-OFF bootloader: using the "fastboot" program, you can shove a bootable image across the USB connection, and tell the phone to boot it up; doing this does not alter any of the flash memory on the phone. You should be able to use Amon_RA to make an initial Nandroid backup at this point.
I'll add another post to this in a couple minutes.
bftb0
OK.
Now, normally - if the phone in question had not been acting up when it was "stock", we would be proceeding much more rapidly. But, in the past, we have observed cases where just "flashing" a ROM, especially using the RUU utility or HBOOT+PB00IMG.zip method can cause the phone to become a hard brick if there are problems with the flash memory partitions.
So, download the attached "flashable .zip" file: MTD_Inspect_v0.9.zip
File: MTD_Inspect_v0.9.zip
Size: 2,786,881 bytes
MD5: 17a39da9d554bef76930ea0499fc8851
You can transfer files to your SD card when it is in Amon_RA recovery - that is the menu item "MS-USB" toggle. Use that mode to transfer this file ("MTD_Inspect_v0.9.zip") to the root folder of your SD card.
(BTW, since you are using the "MS-USB" toggle feature, now is a good time to rename or delete the PB00IMG.zip file on the SD card - you don't wan't the install to re-start automatically should you accidentally start the phone in HBOOT mode)
(BTW #2, I should mention that your phone will charge when it is running Amon_RA - so it is safe to leave the phone in Amon_RA recovery for extended periods of time - so long as you eventually plug it in either via USB, or on a charger)
You can "flash" this above package after you have transferred it to your phone. It actually doesn't "flash" anything - it runs a diagnostic program to look at the health of your phone's flash memory.
When it finishes, it will create a report file on the SD card named "MTD_Inspect.txt". It will have some lines of text at the top of the file which look like this. Post the top of that report (as shown below).
(I just ran this on my phone - this shows you what the first several lines of that file look like)
Code:
Eris MTD Partition Status Report Generated on Wed Mar 16 05:20:45 UTC 2011
PARTITION DEVICE_NAME SIZE(Bytes) BAD_BLOCKS #_E-BLKS ECC_FAIL ECC_CORR BBT_BLOCKS
misc /dev/mtd/mtd0 655360 0 5 0 0 0
recovery /dev/mtd/mtd1 5242880 0 40 0 0 0
boot /dev/mtd/mtd2 2621440 0 20 0 0 0
system /dev/mtd/mtd3 178257920 1 1360 0 0 0
cache /dev/mtd/mtd4 136314880 1 1040 0 0 0
userdata /dev/mtd/mtd5 167247872 0 1276 0 0 0
What I am most interested to look at are the "bad block" counts. Some phones have none; as you can see my phone has 1 bad block in each of the system and cache partitions. (Zero or low numbers are OK - we are just checking here to see if there is anything horribly wrong).
Also, BTW - please report if you saw any errors reported when you make the Nandroid backup. You will see an "E:" and a message on-screen if an error occurs.
bftb0
Hi kd,
It occurred to me that - because you had already performed a "factory reset" procedure using the stock recovery boot - that there is little value in performing a Nandroid backup. (Although, if errors occur during the backup, that information could be useful for diagnostic purposes).
I had been thinking something along the lines of "wouldn't it be great to get hand the phone back to the wife just as she had last used it" - but that is clearly impossible if the /data partition got cleaned up.
So... what you probably want to do is download a ROM file to load onto the phone after we review the results of the "MTD_Inspect.txt" report.
The one that will be most familiar to your wife, and 100% stock, is this one:
[ROM] HTC Eris March 2011 OTA Stock ROM - v2.41.605.6
It's not even rooted - it literally is identical to the most recent "stock" HTC/VZW code for the Eris. Putting a rooted ROM on the phone is also possible, and there are versions that are extremely close to stock, such as "xtrSense 5.0", if you want to put that on the phone as an alternative. (The phone will be a little snappier in it's behavior.)
Anyway, you might want to download a ROM file, transfer it to the root folder of your SD card, and verify it's "MD5" signature (the copy on the SD card, not the one on the computer).
Assuming that no problems occurred with the Nandroid backup and the "MTD_Inspect.txt" report doesn't indicate huge problems with any of the "boot", "system", "userdata", or "cache" partitions, the next step you will be taking is to flash the ROM file using the Amon_RA menu.
bftb0
Hey bftb0,
I have followed the steps you listed and successfully flashed the bootloader to 1.492000 and performed a soft-boot of the Amon_RA image. I created a nandroid backup without any errors.
I downloaded the attached MTD_Inspect_v0.9.zip file and transfered it to the sd card using Amon_RA custom recovery tool and flashed it. I attached the report it left on the sd card.
bftb0 said:
I had been thinking something along the lines of "wouldn't it be great to get hand the phone back to the wife just as she had last used it" - but that is clearly impossible if the /data partition got cleaned up.
So... what you probably want to do is download a ROM file to load onto the phone after we review the results of the "MTD_Inspect.txt" report.
The one that will be most familiar to your wife, and 100% stock, is this one:
[ROM] HTC Eris March 2011 OTA Stock ROM - v2.41.605.6
It's not even rooted - it literally is identical to the most recent "stock" HTC/VZW code for the Eris. Putting a rooted ROM on the phone is also possible, and there are versions that are extremely close to stock, such as "xtrSense 5.0", if you want to put that on the phone as an alternative. (The phone will be a little snappier in it's behavior.)
Click to expand...
Click to collapse
I think the wife will be happy with a working android phone. She is currently using an old windows phone (HTC ozone). I think she would be very happy with xtr sense.50 rom if it makes the phone a little snappier. She had complaints about the stock rom lagging between making calls and what not.
After you take a look at the inspect report and don't see anything out of the ordinary, I can give it a shot.
I will wait for your reply.
OK, everything looks normal. (1 bad block in /cache, but I don't know why that would cause a problem)
Go ahead and flash a ROM file after performing a
wipe -> wipe data/factory reset
in Amon_RA.
Watch the screen carefully for any errors (indicated with an "E:")
If flashing of the ROM succeeds, power the phone off with the menu, start it up in fastboot mode (Send+End), and then perform a flashing operation of the recovery partition:
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
Then, after waiting for all visible activity to cease on the screen, pull the battery, re-insert it, and power the phone up normally. It will take quite a bit longer to get to the initial screen than normal, but that is typical for a first boot.
Let me know if you see any errors anywhere - watch the phone closely through all these steps.
bftb0
kd
I just remembered that - because you did a factory reset with the stock recovery on your phone - you will need to "activate" the phone.
The phone may request to do activation during the initial start up of the phone. I think that any other phone which is registered on that line needs to be switched off for this to work correctly (but am not completely sure, since I don't flop back and forth between phones). I guess that means that the Ozone should be off when you start up the phone.
If you've already gone past that point and need to do it manually, dial *228, and then enter option 1.
Whether this works or not depends on what Verizon did for you when you visited them. (It won't work if they removed the phone from the account) If it doesn't activate, give Verizon a call on another line and tell them "your phone came back from the dead".
bftb0
No errors!!!!
She now has xtrSense 5.0 running on her phone and it booted up!!!!!!
Thank you for all the help you provided!!
We activated the ozone when we got home from Chicago by dialing *228 opt 1.
So after I got the new rom loaded on her eris, I followed the prompts and activated the phone again.
Everything seems to be working normal again!!
I can't thank you enough for all the help you gave me!!
So far, running the xtrSense rom, the only thing that she has noticed different was the internet icon in the apps list. I got her facebook set up without any issues. (thats all she really cares about)
Thanks again for everything!!!
OK, you're welcome.
Sorry we went through a lot of extra effort (I was afraid of a scenario that didn't exist on your phone), but it sounds like your wife had a phone to use in the meantime.
Make sure to get rid of the PB00IMG.zip file (either delete it or rename it or move it out of the top-level folder) so it doesn't cause any disruption should the phone get booted into HBOOT mode.
A couple of other points are worthwhile to make, too.
1) You are an Eris rooter now, whether you wanted it or not
2) If you flashed the recovery ("fastboot flash recovery recov..."), you can now boot directly in to it (the custom recovery) by holding the Vol-Up and End/Power buttons when the phone is turned off.
3) You have means to make complete backups on your wife's phone with Nandroid. Once she has her phone fully configured, you might want to do that once as a insurance policy against further disasters.
Cheers and safe travels,
bftb0
PS It didn't escape me that you had absolutely no troubles with any of this stuff, including the command line, which usually eludes younger windows users. Compute much?
That was no big deal going through the extra effort! I am just relieved that we dont have to puchurse a different eris thru craiglist or ebay.
I deleted the PB00IMG.zip file when you mentioned it in a previous step.
I am going to have to look into rooting my phone now!! It was kind of fun!
I wouldn't say that I compute much. When I was a child and first introduced to computers, there was no such thing as windows. It was all dos. My father is a software engineer so I picked up alot from him back in the dos days.
My wife can't thank you enough for all the information you provided!
Cheers to you!!
kdcroswell
Hello,
I want to send out a Heavy thanks for this thread. I too was able to restore my wife's phone and flashed xtrsense 5.0. All other forums I visited for this topic ended with a verizon exchange and that wasn't possible for me. But right on! this was a tremendous help. Thanks again!
bftb0, I am having the same issue but it seems the process may be a little different for me do to my boot loader.
Mine shows 1.49.0000 S-ON
I did all of the same steps up to the point that I received the error as follows.
"Main Version is Older!" message after HBOOT unpacks and inspects the PB00IMG.zip file.
You advised to Stop and ask for further guidance so I am doing that now.
In advance I appreciate the help. This thread has been more helpful than any other resource I have found so far.
Update: Hallelujah, we have seen the birds!
Just for future reference to those of you who may be stuck in an "APX loop", where NVFlashing and even repartioning do not work for you. I tried many things, and only one thing worked.
Didn't work:
1) NVFlashing to anything
2) Repartioning or wiping
3) Wiping out all storage on the SD card
After doing many, many rinse and repeats on the above, the only thing that did work were these instructions:
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Click to expand...
Click to collapse
Now, I don't know of too many cases like mine where APX was the only thing that was working and that no amount of CWM or NVFlashing could bring back whatever was wrong with the bootloader, but this method forced a recovery image restore and got me back to the point where I can now power down and reboot. And for that, I thank this fine community!
I think we need a better guide somewhere on... Stages of recovery. If this doesn't work, here's the next deeper level. (Example: Level 1, wipe data/cache and reflash the rom. Level 2: Repartition and fix permissions. Level 3: NVFlash for 1.1 or 1.2 back to stock. Level 4: run the steps I have listed above. Level 5: fixing the bootloader. Level 6: Remove the case cover and short the back.)
Anyways, thanks again guys. Hopefully someone else will search with the same issue I had and get fixed as I have.
try this (not a developer here) when it boots up use your computer to delete all the files on the sd card so it looks blank- not sure if it will fix your issue but if there is a file on there messing your reboot into cwm that should will get rid of it. let me know how it goes. (standard at your own risk disclaimer) i have done this before just to see what would happen and nvflash brought it back up.
Hey, thanks for the reply. The sdcard was already blanked out through my various steps, so that doesn't appear to be the problem. Same things happen.
Now, that's just the app data and such on the sdcard, so I am guessing if I was able to see/delete all the system files instead via USB and delete it that way, I'd see something else.
just to bee clear i would delete everything on there not just the system files- so when you go to the drive from your computer it shows nothing at all.
here are the steps i would take start to finish.
1 nvflash rom
2 connect to computer, mount usb, then highlight and delete all files on gtab.
3 nv flash again (preferably with a stock rom with cmw pre loaded
4 reboot and pray that this fixed it.
OP - What size is the nvflash file you are using? I have run into a similar issue before with the larger nvflash.exe (like 152kb). It should be 140KB.
Just something else to check.
So to clarify, when you nvflash the 3588 stock image, it will automatically reboot at the end of the nvflash_gtablet.bat batch file?
pugsby said:
Hey all. Little frustrated since I've tried most of the tricks and still have a soft-bricked device. Not sure how it happened originally, but one way or another, I have a bad bootloader and no access to CWM.
APX works. I can NVFlash 1.1 or 1.2-based Stock or otherwise roms, and they boot (once, and only once...) . I can get USB mount. I've tried them with and without CWM pre-installed and see no differences.
But as soon as I reboot or power off, it just returns to APX mode. It is only a black screen, however. No birds, no logo, no nothing. The only way to make it boot again is to NVFlash it again.
All the instructions say to enter CWM to re-partition or to wipe data. That's great, but I have no access to CWM. Pressing the buttons during bootup does nothing because the device never makes it that far through bootup. And the format utility doesn't wipe enough data to return this back to a truly blank device, because when I nvflash, my apps still show to be there and I want it back to a blank slate.
I've tried pressing the buttons directly after a NVFlash to enter CWM that way, but it just goes straight into the rom.
Others have suggested popping off the back of the case and grounding out things to reset that way, but I thought that was just if APX didn't work, but APX is the only thing that DOES work, so not sure if it applies. (Let me know if I'm wrong there)
More things to try?
Click to expand...
Click to collapse
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
After you repartition, wipe data, clear cache, etc. it might still loop into APX. If it does you'll need to force it to install a new bootloader. I'll dig up a link to the procedure if you need it.
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
K J Rad said:
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
Click to expand...
Click to collapse
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Acidburn find out a solution for this problem
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
K J Rad said:
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
Click to expand...
Click to collapse
This got me into CWM (Yay!). This, however, did not fix the APX looping (boo).
I repartitioned, wiped, nvflashed, wiped, repeat. Even though I have more options now with CWM, the end outcome is still the same that after the initial boot, it won't boot again.
BUT, I did find a working method. See the original post.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I was hoping you'd respond, goodintentions, as I used your NVFlash files and instructions this last time around from your very handy site.
I'm not sure exactly what happened. I do know that Rom manager was involved somehow, trying to use that integration with recovery. (I know, not recommended, but at first it acted like it would work).
Also, I think a 1.2 Rom was mistakenly flashed on top of a 1.1 bootloader somehow.
The details are fuzzy. It's been so many things since then that who knows..
goodintentions said:
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Click to expand...
Click to collapse
I am a tech. Been working with/on/in electronics and computers for roughly 35 years. I had a hard time believing the problem was real until I had one in my hands that was doing it. I've tried doing it to my own tablet but a simple nvflash always got me going again.
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
Click to expand...
Click to collapse
This is successful in some cases but not all. In some cases the bootloader has to be updated using factory stock recovery. ClockworkMod and nvflash don't update the bootloader (and I suspect some other system related partitions/information) properly. For those cases the fix is a little more complex. This process...
http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
has worked on all but one of the tablets I've recovered. The odd one out required an extra reboot (though I was doing the steps from memory and on an unfamiliar computer so I could be mistaken). However... as noted above... a subsequent nvflash of even the same image resulted in another APX loop. The end result was I had to craft a custom nvflash for each of those machines to avoid the problem in the future. That may or may not be necessary for all cases but since it's relatively easy I just do it out of habit now.
Keep in mind that serious APX looping issues are very rare in the grand scheme of things. Many times folks get confused and fail to follow directions properly and think they have a bigger problem than they really do. The overwhelming majority of times a simple nvflash and repartitioning will fix these things right up.
Added: BTW, the best way I've found to avoid the APX loop issue entirely... do a data wipe before you flash a new ROM and then again immediately after and before you boot it for the first time. I know... one should be enough... but if you make it a habit to do two... then you'll probably remember to do at least one of them ;-)
Great info. I shall try not to enter another painful APX loop. I was shocked how many things I had to try and places I had to go before I found a working method. I guess I really did a number on this thing somehow. But I'm happy that it's back.
I didn't have to do the more painful one you mentioned, but honestly I was ready to try about anything short of slaying a dragon.
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.