So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
-Still sitting staring at this white htc screen. I literally am out of ideas. I did everything perfect and this happened, I'm so sad. I specifically remember doing something regarding MainVer's awhile back so I would never have this problem and now I am here with a broken phone. This blows ... Suggestions?!
SHIDOOBY said:
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
-Still sitting staring at this white htc screen. I literally am out of ideas. I did everything perfect and this happened, I'm so sad. I specifically remember doing something regarding MainVer's awhile back so I would never have this problem and now I am here with a broken phone. This blows ... Suggestions?!
Click to expand...
Click to collapse
If you are s-on, it is nearly impossible to be "done for". Probably user error (no offense) but you probably had a file named incorrectly or it didn't flash properly. I just got to work and can't really help you right now, but i know someone can. Just don't worry, you'll be fine. Like i said, it's far from "done for".
tCizler said:
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
Click to expand...
Click to collapse
Easy fix.
If you don't have the ROM on your computer anymore, download it again. Extract it and copy the boot.img to your ADB directory (if you don't have ADB, you need to get it lol.) Plug your phone into your computer, then just boot your phone into your bootloader, go into recovery, wipe everything 3X to be safe. Install the ROM, reboot into bootloader (make sure you're in fastboot USB mode.) Open up command prompt, CD to your ADB directory and type in fastboot flash boot boot.img. Reboot, and enjoy. If you have any issues, let me know.
In addition to Chyrux's useful post, I'd recommend keeping backups of your phone's storage on PC and possibly cloud storage.
If you got the time, or a spare SD card to get phone running in the meantime, might want to try a recovery program to get those nandroid backups and files off the SD card. I'd suggest Piriform Recuva for Windows, use the Deep Scan option.
I used to have ADB but don't anymore and downloaded the "noob proof" thing that allows you to do everything. Although you can't really use it without your phone turning on. When I press the volume down button it tries to install a kernel and said "Main Version Old" and makes me press the power button to reboot. I do have Amon Ra installed. I haven't really messed with the whole phone thing in awhile and have tried to educate myself by reading and reading and am a bit of a perfectionist. I don't know where I went wrong.
-I do know that I am on the new firmware w/ ICS
-I do know that Amon Ra is installed.
-I don't have a backup because everything seems to have been deleted.
-I suppose something went wrong during the installation process with RezRom S4 2.5
-I currently have no idea what I am doing. I am not stupid, nor do I expect handouts. I am fully capable of reading threads and usually fixing all my problems on my own. But, without a backup and me not being completely familiar with adb and my phone stuck on a white htc screen it makes me a bit timid to do anything else without some direction.
SHIDOOBY said:
I used to have ADB but don't anymore and downloaded the "noob proof" thing that allows you to do everything. Although you can't really use it without your phone turning on. When I press the volume down button it tries to install a kernel and said "Main Version Old" and makes me press the power button to reboot. I do have Amon Ra installed. I haven't really messed with the whole phone thing in awhile and have tried to educate myself by reading and reading and am a bit of a perfectionist. I don't know where I went wrong.
-I do know that I am on the new firmware w/ ICS
-I do know that Amon Ra is installed.
-I don't have a backup because everything seems to have been deleted.
-I suppose something went wrong during the installation process with RezRom S4 2.5
-I currently have no idea what I am doing. I am not stupid, nor do I expect handouts. I am fully capable of reading threads and usually fixing all my problems on my own. But, without a backup and me not being completely familiar with adb and my phone stuck on a white htc screen it makes me a bit timid to do anything else without some direction.
Click to expand...
Click to collapse
Lol I feel your pain. I don't have an SD card reader, so situations like this usually blew. But, there's a bright side: you have an internal storage unit. Let's try something basic. Take out your SD card and plug your phone into your computer. Reboot into your recovery and mount your USB storage. Tell me if you can see your internal and can access it.
So this is where I get stuck at; I appreciate that idea and will try it shortly (at work at the moment). I basically have no access with my computer and phone via usb because i am unable to get past hboot.
2 things happen as of right now:
-I press the power button and it sits at the HTC white screen forever
-I hold volume down and the power button and it tries to flash a kernel and says my Main Version is old. (When in fact, I know I did the MainVer fix while back; frustrating)
So with those 2 things only happening, is your suggestion still to yank out the external? I wish I had a microSD reader to wipe it and put a new rom on there and then figure out how to access amon ra and get passed this mess.
I took 2 min off work to yank the card out(the external, that is) -- I was able to reach recovery. I went into the mounting section of Amon Ra where I was able to see /sd-ext and /sdcard, both of which I got the message. "E: Can't mount /dev/block/mmcblk1p1) (No such file or directory)
Chyrux said:
Lol I feel your pain. I don't have an SD card reader, so situations like this usually blew. But, there's a bright side: you have an internal storage unit. Let's try something basic. Take out your SD card and plug your phone into your computer. Reboot into your recovery and mount your USB storage. Tell me if you can see your internal and can access it.
Click to expand...
Click to collapse
And for that matter, I have gotten in the habit of lifting my battery out at an angle, pressed into the contacts still to remove and insert my SD card on the fly for when I get these lingering PH98IMG.zip files. Pop out, go to recovery with a ninja grip on phone, and pop SD in lol.
I know Amon Ra Revamped 3.15 recovery has an option to delete those zips.
http://forum.xda-developers.com/showthread.php?p=23169557
Need to try reflashing that zip again in recovery perhaps, maybe RUU undid your Misc partition Mainver fix.
In any case... What your white bootloader screen says would help troubleshoot.
(Sorry for constant edits)
When you flash a new kernel the mainver is changed to what that kernel's is. I'd it's a newer number then when you try to flash something with a older number it won't flash. So every time you flash a kernel it is a good idea to go ahead and redo the main version fix
Sent from my ADR6425LVW using Tapatalk 2
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT 2.21. 0000
RADIO-1.2.22.10. 0310r/1.22.10.0308r
OpenDSP-v13.6.0.7611.00.0104
eMMC-Boot
Mar 11 2012,22:16:16
HBOOT
<VOL UP> to previous menu
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
- How would I flash the Mainver fix when I can't even communicate with my computer through usb?
- Would adb help(I haven't used in a LONG time)
- I'm sitting at the screen I just took about 20 min to type out up above.
The white screen text I showed you was without the external sd card in. I feel like the only solution right now is to buy another external SD card.. put a rom on it, and then flash it... maybe that's the solution since I can't access this SD card and it seems to be ****ed with a mainver problem? Although, even with a new SD card I don't know how I would flash the mainver fix?
SHIDOOBY said:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT 2.21. 0000
RADIO-1.2.22.10. 0310r/1.22.10.0308r
OpenDSP-v13.6.0.7611.00.0104
eMMC-Boot
Mar 11 2012,22:16:16
HBOOT
<VOL UP> to previous menu
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
- How would I flash the Mainver fix when I can't even communicate with my computer through usb?
- Would adb help(I haven't used in a LONG time)
- I'm sitting at the screen I just took about 20 min to type out up above.
Click to expand...
Click to collapse
Okay, you are following the guide of the RezROM to a tee I take it. Have to ask which AmonRa version did you install? I got the same mounting errors once and had to re-flash the recovery to AmonRa 3.14 to detect the mount points properly.
And yes, should be able to use fastboot commands with ADB to push the recovery, the Mainver fix, etc. That is the key communication tool you have barring any other access in your situation.
I'm am not anywhere remotely close to a PC and a bit rusty too, will try and find the ADB commands for that.
PhantasmRezound said:
Okay, you are following the guide of the RezROM to a tee I take it. Have to ask which AmonRa version did you install? I got the same mounting errors once and had to re-flash the recovery to AmonRa 3.14 to detect the mount points properly.
And yes, should be able to use fastboot commands with ADB to push the recovery, the Mainver fix, etc. That is the key communication tool you have barring any other access in your situation.
I'm am not anywhere remotely close to a PC and a bit rusty too, will try and find the ADB commands for that.
Click to expand...
Click to collapse
Those lines I typed were without the SD card in the actual phone. I did install the newer version of AmonRa (3.15 for ICS and GB) In the actual recovery with the External SDcard out I did some scoping around where you're able to delete the kernel install, but that would leave me still with a broken phone. I need to be able to access my SD card and put a new rom on it i'm guessing? I don't even know what the **** I'm doing anymore.
wow.
put THIS file on your sd card. then do the update in HBOOT. once your are back up and running flash the main version fix. then get s-off
*EDIT* just saw where you can go into recovery. Okay. Here comes the fun part. I'm not well-versed in the mainver issue and this method can brick your phone, so be careful. Just what I have for now.
Start by having your SD card out (but on your desk, just make sure you have it lol.) Boot up your phone into the bootloader and go to where you can access your recovery, but don't. Here's where you can brick your phone. Pop out your battery and leave the cable plugged in (you'll have power still going to your phone.) Now, put your SD card back in and put your battery back in as well. Boot into your recovery and mount USB storage. From there, delete the update file using My Computer.
SHIDOOBY said:
So I decided I needed to update my phone. I installed the new firmware and everything went perfect. I decided on this rom (I am S-ON). After installing the rom I ran the other zip for S-On users. It then told me my Main Version was too old. I remember doing a fix for this months ago and saying I won't have this issue again. Now I am sitting at a white HTC screen thinking my phone is completely done for. With the firmware leak and all that all my backups seem to have been deleted. Any suggestions?... I am in dire need.
-Still sitting staring at this white htc screen. I literally am out of ideas. I did everything perfect and this happened, I'm so sad. I specifically remember doing something regarding MainVer's awhile back so I would never have this problem and now I am here with a broken phone. This blows ... Suggestions?!
Click to expand...
Click to collapse
Delete the PH98IMG.zip off your sdcard, download and flash THIS and then try flashing the rom and kernel again. should work. Worked for me.
try this link: http://forum.xda-developers.com/show...57&postcount=4
tmettler5 said:
Delete the PH98IMG.zip off your sdcard, download and flash THIS and then try flashing the rom and kernel again. should work. Worked for me.
try this link: http://forum.xda-developers.com/show...57&postcount=4
Click to expand...
Click to collapse
I think his issue is that he can't access his SD card because he doesn't have a reader/other device to use.
Ah... That makes sense. Maybe another sdcard, then? I'll put the set mainver low file in the dropbox later today and send a link. If you can use a second sd card and put it on that he can fix it. I think.
Sent from my ADR6425LVW using XDA
tmettler5 said:
Ah... That makes sense. Maybe another sdcard, then? I'll put the set mainver low file in the dropbox later today and send a link. If you can use a second sd card and put it on that he can fix it. I think.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Nah, he won't have to. Granted, my method is a bit...unsafe lol, but it worked fine for me. he just has to be careful and he'll be able to take the file off. Glad you have the fix cause I don't, though. So hopefully my trick will work and then he can use the fix.
If you get to the point where you can get into recovery, flash this: http://dl.dropbox.com/u/79523435/SetMainVersionLOW.zip
Then flash your rom and kernel as per normal.
Related
---------------------------------------------------------------
First a huge thank you to all who have spent countless hours creating ROMs and posting all the help here on this site. I knew nothing about working with alternate ROMs or Rooting before starting on this journey and would have never been able to get this done without the communiities help. Thank you all.
---------------------------------------------------------------
History:
I installed Amon RA Recovery using this method this method and then flashed a couple of different ROMs.
Problem:
Recently my screen started continually scrolling to the left even when I'm not touching it. Sucks. So, I'm returning the phone.
I followed the process in this post and everything seemed to work fine to get it back to stock.... I think.
Thinking that Amon RA also needed to be removed I looked at HBoot. I had never seen HBoot before I started messing around with the phone so I'm not sure what I'm supposted to see to verify that it is back to stock. Now when I go into Hboot, I see "Recovery" still which was what I used to flash ROMs backup etc. I'm pretty sure (but I must confess I'm not 100% sure) that was Amon RA Recovery. Now when I select "Recovery" I get a black screen with an picture of my phone and a red alert symbol over it. It never goes anywere from there and I have to reboot. Phone always comes back up OK and I've been using it for two weeks now.
I suspect that is not this "Recovery" behavior is not factory behavior and I'd like to get it corrected before I return it to Verizon.
I've done and TON of searching and poking around, but, I just can't seem to find a difinitive answer with the little knowledge I have. Many of the posts I've found assume more knowledge than I have so I'm a bit lost at this point.
Here are my two questions:
1. How do I get HBoot back to stock and correct the "Recovery" issue (assuming this is an issue)?
2. How do I verify that there is no evidence that I've Rooted and/or how do I verify that I'm correctly "unRooted?"
Thanks in advance for any help you can offer.
That Recovery that you describe is stock recovery, not Amon's. That part is all set.
The only other thing that you may want to do, if you are paranoid about this (I am not sure that Verizon checks returned phones all that carefully), is to check the first line when you restart in the Bootloader (Hold Vol-Dn while powering up, but I think you already know that.) If the first line ends "S-ON", you have a stock, locked Bootloader. If it says "S-OFF", you have the unlocked bootloader and Verizon could determine that the phone was rooted.
Ok, thanks! It HBoot reads S-On. So, is there any further cleanup I need to do the SD card to prep it to return other than reomove any of the ROMs I have sitting on the root?
I just reverted my eris to OTA 2.1 and hboot reads s-off. Any ideas on how to fix this?
bernadou said:
Ok, thanks! It HBoot reads S-On. So, is there any further cleanup I need to do the SD card to prep it to return other than reomove any of the ROMs I have sitting on the root?
Click to expand...
Click to collapse
I think that they make you keep your SD card, so that should be all set. Otherwise, if you truly are paranoid, just copy the SD contents to your computer and format the SD card. That should hide anything. Otherwise, you'd want to get rid of the /Nandroid folder, and I'd use something like Astro to look at all other folders. I believe that there is a setting to check for hidden files and folders (essentially, files and folders whose names start with a period). As I recall, when you flash ROMs, Amon's Recovery creates some sort of hidden folder with the same name as the root file, so you'd want to delete those, probably.
All this said, check out this post:
Well, it still didn't work this morning, so I called back the tech line, and talked to a 'level 2' tech. I told them it was rooted, and the problem I was having, so he said to take it to the local store and have them reflash it to the oem software. Took it by there, and I talked to a guy that works there that rooted a droid and was having problems, told me that I can't go back to the oem sofware after rooting, so they issued me a replacement eris on the spot. Maybe this will take care of the problem, they said if it didn't They could probably swap me for an incredible.
Click to expand...
Click to collapse
I doubt that this is official policy, but you may not have to worry too much about it.
primopax said:
I just reverted my eris to OTA 2.1 and hboot reads s-off. Any ideas on how to fix this?
Click to expand...
Click to collapse
When there is a S-OFF bootloader on the phone, you can use fastboot to flash a different bootloader in place. This works because the existing bootloader has been copied to (and is running out of) RAM memory.
e.g.
Code:
fastboot flash hboot hboot_7501a_1.47.0000_091023.nb0
You ought to be damn sure you know what you are doing, have fully charged your phone, and have verified the MD5 signature of the replacement bootloader, as this operation is the single most dangerous thing you can do to your Eris.
The stock bootloader image files can be found by unpacking the "rom.zip" files from either of the MR1 or MR2 HTC RUUs (v1.47.0000), or any of the HTC Leak ROMs V1, V2, V3 (v1.49.0000)
bftb0
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
glitch666 said:
I just acquired a Droid Eris from my buddy of mine, when you turn it on it just stays at the screen with the 3 androids on skateboard(if I turn it on with it plugged into usb It makes the connection noise though). I can Also get into hboot and recovery but no matter what I do it will not install anything, everything just fails. Also its say its S-ON. Any help would be great, thanks.
Click to expand...
Click to collapse
Well, you didn't really say what "everything just fails" means. How about giving us an error message?
While you are at it, what version of recovery is on the phone - Amon_RA v1.6.2, or some version of Clockwork?.
Same deal for the bootloader - how about an exact version number - 1.49.0000, 1.47.0000, or other?
Because your phone is already "soft-bricked", and you got it for free, and because your recovery boots up, you can try flashing "ErisMTDNuke_v0.9.zip". You can find it at this post:
http://forum.xda-developers.com/showpost.php?p=11651122&postcount=21
It has an an assert() in it that tries to block it from running on ClockworkMod, but depending on what version of recovery you have, that may not matter. Let me know if you get any errors running it. If it runs, you should be back in business; it leaves the /system, /data, and "boot" partitions of the ROM blank, so you will need to flash a ROM afterwards. Also, if you have ClockworkMod recovery on the phone, you should consider getting it off of there, and putting one of the two Amon_RA recovery variants on there.
You might find the entire thread that contains the above post very useful, as it describes a method for installing the S-OFF bootloader using the "SoSickWiTiT" rooting method, as well as other tricks such as using fastboot to soft-load recoveries without writing them to flash; that full thread is here:
http://forum.xda-developers.com/showthread.php?p=11652502
Please provide full details on what works / doesn't work, particularly with "ErisMTDNuke_v0.9.zip" - it has only been used on 3 phones so far (worked on all three, though).
cheers
bftb0
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
glitch666 said:
I dont think the phones been rooted(my friend has no idea what that even is). It has hboot 1.49.0000, and the recovery is not a custom one, its Android recovery 2e. If I try to Install an update through recovery its says installation aborted. Also if I use pb00img.zip it loads in hboot but says previous version is older and to reboot.
Click to expand...
Click to collapse
OK, that is completely different. It is impossible to load a dev ROM using the stock recovery <2e>
Did you try the "wipe data/factory reset procedure" of the recovery menu, or have you already done that and then the phone hangs at the three droids?
bftb0
If the stock ( <2e> ) recovery factory reset does not work, then the method of last resort is going to be to try and get the S-OFF bootloader onto the phone using the "SoSickWiTiT" rooting method.
Generally what happens - if you have corrupted flash memory partitions - is that parts of this install will fail, but getting the engineering bootloader (1.49.2000 S-OFF) onto the phone will succeed - and from there you can leverage the behaviors of the S-OFF bootloader to get a custom recovery running (by using fastboot). Once that happens, you can run the ErisMTDNuke_v0.9.zip flash to erase the /system, /data, and "boot" partitions, so that a subsequent ROM flashing operation will succeed (probably, no guarantees).
The way the "SoSicWiTiT" rooting method works, you run the "Official 2.1 RUU" Utility on the PC - but just before it is ready to start writing to the phone (after it has unpacked all it's temporary files and installed drivers for you), you take the "Root PB00IMG.ZIP" file, rename it to "rom.zip", and replace the "rom.zip" file unpacked in the temporary file area of the RUU. This gets the S-OFF bootloader installed (at a minimum, possibly the whole rom if your problem is not flash memory page corruption).
The thread I mentioned above has more details; ask questions if you don't understand something.
bftb0
PS You should be doing all of these operations with a well charged battery - 100% is a good place to start. Don't let the phone sit in HBOOT or FASTBOOT mode for extended periods of time - the battery will discharge rapidly, even if the phone is plugged in to the charger.
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
glitch666 said:
Thank you for the quick and to the point replies, I will try this later tonight and will post and let you know if it works out. I have tried the factory reset and it doesn't work, but hey it was free if I screw it up Its no big issue lol. Im not new to rooting its just I have no experience with this particular phone, so thank you =].
Click to expand...
Click to collapse
OK. Good luck.
The Root PB00IMG.ZIP and the "Official 2.1 RUU" can be found here:
Consolidated HTC RUU, Leak, and OTA Downloads
Amon_RA's original (v1.6.2) recovery is located here
If you don't have a version of fastboot on your PC/workstation already, you can find different platform versions of it a short distance down the HTC's developer page for the ADP.
If you can get the S-OFF bootloader onto the phone, then you can flash Amon_RA's recovery from the PC with a single command:
Code:
fastboot flash recovery recovery-RA-eris-v1.6.2.img
If you don't already have USB drivers installed on your PC, the RUU utility should be able to do it for you automatically (although ymmv depending on your Xp/Vista/Win7/x32/x64 variety).
Let me know how things go.
bftb0
PS It is worth repeating - make sure your phone is well charged when you are doing any flashing.
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
glitch666 said:
Yeah I know fastboot like the back of my hand(g1 and other phones that I love dearly but no longer have), im giving this a shot right now, thank bud.
Click to expand...
Click to collapse
Standing by.
No matter what the official 2.1 RUU gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things. Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
PS -
I might have mentioned it in that other thread, but anyway: the RUU utility will get the phone to cooperate if the phone is put into fastboot mode (or RUU mode). Normally it is expected that the phone will be booted normally when you start up the RUU... but that (obviously) isn't an option for a soft-bricked phone.
cheers
glitch666 said:
No matter what the official 2.1 ruu gives me a bootloader mismatch error 140 with either the actual rom.zip or the root rom renamed to rom.zip and placed in the temp folder, let me try some more things.
Click to expand...
Click to collapse
Rats. Does that happen immediately after the RUU starts up, or only when you tell it to begin the flashing operation?
Here's another wild straw to grasp at.
If you plug the phone into your PC, and then cold-start it (normal boot), do you hear 2 USB sequences at about 5 and 9 seconds, respectively? If the kernel is alive, but looping on something.... and the prior user had USB debugging enabled, and it's a 2.1 ROM, we can probably still root it by hand across ADB.
does "adb devices" give you anything 15 or more seconds after boot-up, or does your (Windows) device manager indicate a "Composite Interface"?
bftb0
Edit RUU says Im going from 2.37.605.4 to 2.36.605.1. Ok so this leads me to believe it has the 4th OTA on it right?
Click to expand...
Click to collapse
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
No it goes all the way to the flashing processes after the phone goes into bootloader mode. then stops and gives me the error, now with adb when I turn the phone on I hear one chime and then get a device not recognized and no output from adb. Did you see my last post on the other page I edited it about the bootloaders, its says its going from 2.37.605.4 to 2.36.605.1. Sorry you posted before me so ignore this last tid bit.
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
I would think that you are starting the process with the phone in FASTBOOT mode, right?
bftb0 said:
Sure sounds that way. Normally that info (the "Main Version") is stored in the misc partition, and it rather surprises me that an OTA install would cause that to happen; but I can't argue with what you are seeing.
That might mean that neither RUU nor PB00IMG.ZIP installs will work without being able to modify the RUU program to ignore version checks.
How about the adb angle - does anything come up on the USB when the 3 skating droids are showing?
Click to expand...
Click to collapse
I am not getting anything from adb.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
Click to expand...
Click to collapse
Yup it stayed the same.
bftb0 said:
Long shot, but check your HBOOT screen again - is it still S-ON (1.49.0000) ?
BTW, when you say "bootloader mode" - do you mean FASTBOOT or RUU mode? (The RUU mode is just a graphic with the HTC logo in the middle of the screen, sometimes with small arrows in each of the 4 corners of the screen. FASTBOOT mode says either "FASTBOOT" or "FASTBOOT USB" right on the screen).
Click to expand...
Click to collapse
First I put the phone into fastboot mode, then fire up RUU and it kicks the phone to a black screen with an htc logo in the middle and trys to flash it(the RUU says its putting the phone into bootloader mode so I guess thats what its in when it restarts to the htc logo).
Don't Quote me but I know the Eris is Almost like my Hero, and with the Hero there's a way to Get it into the Fastboot I Think by Holding Volume Up and Powering on the Phone! Then you Should be Able to Run the Latest RUU for the Eris... Hopefully that will get you back Right!!
Good Luck!
Sent from my Hero using XDA App
Alright, so I've got an S-On rooted Rezound and I'm stuck in the boot loop. YES I've read all the posts about logging in and dialing *#etc and also to go into Mobile Network and switch to LTE/CDMA, but I can't dial anything because the phone cuts off before I get a chance, and the LTE switch does nothing. I've tried flashing several different kernels, using the adb method and the PH98IMG methods, I've tried installing several different ROMS, I've done at least 10 different wipes/factory resets, I boot my phone without the cover, SIM card and without the SD card..and I'm still stuck in this boot loop. Someone please help a noob
---- EDIT WITH SOLUTION ----
Here's my "solution" to this issue. I'm sure it's located somewhere in these forums, but I couldn't find it so I imagine others can't either. Essentially, you're going to have to S-Off. Here's the solution:
I believe my recovery started acting funny after I failed to S-Off properly the first time. Amon Ra was all gimmicky and said stuff like "E: can't find cache" and reinstalling the recovery/wiping everything (and I mean everything: external SD, internal SD, cache, partioning SD card etc..) wasn't working. I tried re-installing Amon Ra through command prompt with the adb, I tried reinstalling my ROMS but my phone wasn't having it.
It got to the point all I could boot into was a white HTC screen, so I then tried out Twrp's 2.1 Touchscreen (I wasn't S-Off yet) recovery (I don't have enough posts to post a link yet ) which INITIALLY reported the same "E: can't find cache" errors as Amon Ra, BUT when I wiped my files in Twrp it seemed to actually fix them...I'm not sure exactly what I wiped or formatted that fixed the "E: can't find mount/cache" issues, so try everything.
So my ROM installed but I was still stuck on the white HTC logo. This is where I INSTALLED A NEW KERNEL THROUGH ADB. I wish I knew which kernel I installed, but I have like 10 and I just picked a random one. The point is if you're still stuck at a white HTC screen, install a new kernel.
So I got a recovery on the phone, and then I tried to S-Off again but I didn't have a good ROM installation so that was hanging at the HTC white screen. I then installed CleanROM DE 1.4 and I was able to boot into it, but ran into my initial problem of it crashing after dialing a number and entering infinite reboot. However, it would stay on just long enough for me to run ControlBear's program to S-Off.
So I S-Offed, I downloaded the Gingerbread RUU (the .exe version for Windows), I installed it, and now I can dial numbers and I'm all goodie again. Unfortunately, I honestly think the only way I was escaping my trouble was doing an S-Off, unless they leak a Ice Cream Sanwhich executable for Windows.
TL;DR Install Twerp 2.1 through adb, wipe everything, install CleanROM DE 1.4, install kernel S-Off, run Gingerbread RUU .exe
autotuneuser said:
Alright, so I've got an S-On rooted Rezound and I'm stuck in the boot loop. YES I've read all the posts about logging in and dialing *#etc and also to go into Mobile Network and switch to LTE/CDMA, but I can't dial anything because the phone cuts off before I get a chance, and the LTE switch does nothing. I've tried flashing several different kernels, using the adb method and the P87etc methods, I've tried installing several different ROMS, I've done at least 10 different wipes/factory resets, I boot my phone without the cover, SIM card and without the SD card..and I'm still stuck in this boot loop. Someone please help a noob
Click to expand...
Click to collapse
Have you tried running a RUU to put it back to factory like you just bought it?
I can't tell you how many times I've had to do that to fix stuff.
Magestic12 said:
Have you tried running a RUU to put it back to factory like you just bought it?
I can't tell you how many times I've had to do that to fix stuff.
Click to expand...
Click to collapse
I think I have downloaded the stock RUU..but just to be sure could you possibly link me to the correct one to run? Also I thought it was impossible to go back down from Ice Cream Sandwhich to Gingerbread?
autotuneuser said:
I think I have downloaded the stock RUU..but just to be sure could you possibly link me to the correct one to run? Also I thought it was impossible to go back down from Ice Cream Sandwhich to Gingerbread?
Click to expand...
Click to collapse
It is if you're s-on. Also, what did you mean by "P87etc," are you flashing the files properly?
autotuneuser said:
I think I have downloaded the stock RUU..but just to be sure could you possibly link me to the correct one to run? Also I thought it was impossible to go back down from Ice Cream Sandwhich to Gingerbread?
Click to expand...
Click to collapse
People say a lot of things are impossible, most have the virtue of never being tried.
This is the one I used to fix mine when I screwed up the partitions on my phone. I will warn you, the link in the thread takes you to another site & you have to sign up to download it. Its completely free & legit, but it won't let you download unless you register which is STUPID!
http://forum.xda-developers.com/showthread.php?p=25664508
Let me know if that helps
Oh & BTW I was & still am on the ICS leaks when I did this, so you'll be fine. You will lose everything on your phone though, because it wipes everything. But if you can't use it, that's not really an issue I guess.
tekhna said:
It is if you're s-on. Also, what did you mean by "P87etc," are you flashing the files properly?
Click to expand...
Click to collapse
The PH98IMG file. And I believe I'm flashing the properly..I do it twice; flashboot in adb, it tells me success, I then flash again right there, and then I reboot back to the bootloader and flash again so I do it 3 times in total.
I'm downloading the Vigor executable now. It's going to take a while but I'll report back with my results.
autotuneuser said:
The PH98IMG file. And I believe I'm flashing the properly..I do it twice; flashboot in adb, it tells me success, I then flash again right there, and then I reboot back to the bootloader and flash again so I do it 3 times in total.
I'm downloading the Vigor executable now. It's going to take a while but I'll report back with my results.
Click to expand...
Click to collapse
PH98IMG is not going to help you in this situation. You are going to have to download & run the RUU that I linked in the previous post. Trust me on this, not only have I already tried that before, I've blown my phone up enough times to know.
Magestic12 said:
PH98IMG is not going to help you in this situation. You are going to have to download & run the RUU that I linked in the previous post. Trust me on this, not only have I already tried that before, I've blown my phone up enough times to know.
Click to expand...
Click to collapse
Ok, I went to use the RUU and at first I got error 150, so I read somewhere I should lock my bootloader, so I relocked and now I get error 140, whcih is bootloader verision error. I think that's because I'm on ICS with S-On right? Is there any ICS RUU I can use to restore my phone? I downloaded Vigor_Stock_Doedexed_3.14.605.5 before but it still wasn't working for me.
autotuneuser said:
Ok, I went to use the RUU and at first I got error 150, so I read somewhere I should lock my bootloader, so I relocked and now I get error 140, whcih is bootloader verision error. I think that's because I'm on ICS with S-On right? Is there any ICS RUU I can use to restore my phone? I downloaded Vigor_Stock_Doedexed_3.14.605.5 before but it still wasn't working for me.
Click to expand...
Click to collapse
And as far as this goes yeah you can't use the .exe if your on ICS firmware with s-on and there are no available .exe's for ICS
Sent from my ADR6425LVW using Tapatalk 2
Unless you are already on the gingerbread build, and it sounds like your not, if you are s-on, it simply will not work. My suggestion is to download the latest leak and that should get you going. If it were me, and I aleady did it, download the latest leak here: http://android.thesmallprint.org/ICS.LEAK.3.14.605.5_PH98IMG.zip. Rename it PH98IMG.zip and put it on your external sd card. Should take less than 10 mins to download. Reboot into bootloader and let hboot install it. Make sure you are locked or relocked. After that is installed either delete or change the name of that file. Reboot into bootloader, unlock, and install either amon ra or tpwr and you can reinstall that rooted rom.
what he said
mikey's comments just previous are totally right, but after install, i would recommend
a factory reset, maybe even twice.
your bootloop problem should be cured then...
I was on the latest ICS firmware running an ICS ROM when I had to run the RUU I gave the link for & it worked fine for me.
Here's my suggestion & you can take it for what its worth.
I would download the latest HBoot & Radios & flash them.
Then if you can get into recovery, wipe everything, manually wipe the system, boot, etc. Then after that try running the RUU.
I just did this earlier in the week & it worked fine & my phone was all screwed up because the partitions were mounting to the wrong places & just all messed up.
I am by no means a dev or an expert, I'm just telling you what I did.
WHATEVER YOU CHOSE, YOU DO AT YOUR OWN RISK, but I don't see where you really have a choice.
Let me know if I can be of anymore help as I know what its like to have a phone that's freaking out on you. You can PM me or post here which ever you prefer. If after that we still can't get it fixed, we'll go find a dev to help us.
mikeyk101 said:
Unless you are already on the gingerbread build, and it sounds like your not, if you are s-on, it simply will not work. My suggestion is to download the latest leak and that should get you going. If it were me, and I aleady did it, download the latest leak here: . Rename it PH98IMG.zip and put it on your external sd card. Should take less than 10 mins to download. Reboot into bootloader and let hboot install it. Make sure you are locked or relocked. After that is installed either delete or change the name of that file. Reboot into bootloader, unlock, and install either amon ra or tpwr and you can reinstall that rooted rom.
Click to expand...
Click to collapse
Well now my recovery is saying it can't mount various things like "E: can't mount b dev/block/ blah blah"
And I tried flashing my ROM through Amon recovery but it's saying it can't open the file because it's (bad). I formatted the SD card and I'm still getting the issue. Any ideas?
Did you download the one from the link? You don't flash that PH98IMG.zip in recovery, you boot up into bootloader and let hboot find it. If when you get to your bootloader and it is fastboot, use your volume key and select on bootloader option. Then hboot will find it and ask you if you want to install it. Install it. After that, you will then need to reinstall either amon ra or the other but stay away from clockworkmod. But to reinstall the recovery, you will have to unlock again.
mikeyk101 said:
Did you download the one from the link? You don't flash that PH98IMG.zip in recovery, you boot up into bootloader and let hboot find it. If when you get to your bootloader and it is fastboot, use your volume key and select on bootloader option. Then hboot will find it and ask you if you want to install it. Install it. After that, you will then need to reinstall either amon ra or the other but stay away from clockworkmod. But to reinstall the recovery, you will have to unlock again.
Click to expand...
Click to collapse
I did install in hboot. I then installed Amon so I could flash the ROM and that's what's giving me all those errors.
If all you are after is stock and rooted, try looking at this one: http://forum.xda-developers.com/showthread.php?t=1642217
Since you ran the PH98IMG that I directed you to, you are now on ICS. So follow the directions in that thread for "S-On and ICS".
Installation for S-ON Devices on ICS firmware
•Copy ROM to SD Card AND PH98IMG.zip to ROOT of SD Card
•Reboot to recovery
•wipe data / Factory Reset
•Flash ROM
•Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
•Reboot
•Profit!
Edit: The only change I would recommend is to hold off putting that PH98IMG file from that thread on the sd card right away. You will have a hard time getting to recovery if you have that on the card. I would suggest following all the instructions up to and including "Flash ROM". Then I would "return" back to the main Amon Ra screen, make sure you have the data cable connecting your phone to the computer, select "USB-MS Toggle", then select the SD Card, and that will allow you to copy the PH98IMG file to the SD card. Then continue with the rest of the directions. If you do this right, you should be ok.
mikeyk101 said:
If all you are after is stock and rooted, try looking at this one: http://forum.xda-developers.com/showthread.php?t=1642217
Since you ran the PH98IMG that I directed you to, you are now on ICS. So follow the directions in that thread for "S-On and ICS".
Installation for S-ON Devices on ICS firmware
•Copy ROM to SD Card AND PH98IMG.zip to ROOT of SD Card
•Reboot to recovery
•wipe data / Factory Reset
•Flash ROM
•Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
•Reboot
•Profit!
Edit: The only change I would recommend is to hold off putting that PH98IMG file from that thread on the sd card right away. You will have a hard time getting to recovery if you have that on the card. I would suggest following all the instructions up to and including "Flash ROM". Then I would "return" back to the main Amon Ra screen, make sure you have the data cable connecting your phone to the computer, select "USB-MS Toggle", then select the Internal_sd, and that will allow you to copy the PH98IMG file to the SD card. Then continue with the rest of the directions. If you do this right, you should be ok.
Click to expand...
Click to collapse
It's the actual recover I believe to be giving me the errors, but I'll try what you said in about 2 days (I need to study for finals). It might be because I tried to S-Off and I installed all of that guys software and it might be making the phone act funny. I'll be much more descriptive about my errors when I post back in 2 days.
I fixed it!!
Ok, so I finally got it working, I'll try to detail my steps for anyone else who ran into similar issues:
I believe my recovery started acting funny after I failed to S-Off properly the first time. Amon Ra was all gimmicky and said stuff like "E: can't find cache" and reinstalling the recovery/wiping everything (and I mean everything: external SD, internal SD, cache, partioning SD card etc..) wasn't working. I tried re-installing Amon Ra through command prompt with the adb, I tried reinstalling my ROMS but my phone wasn't having it.
It got to the point all I could boot into was a white HTC screen, so I then tried out Twrp's 2.1 Touchscreen (I wasn't S-Off yet) recovery (I don't have enough posts to post a link yet ) which INITIALLY reported the same "E: can't find cache" errors as Amon Ra, BUT when I wiped my files in Twrp it seemed to actually fix them...I'm not sure exactly what I wiped or formatted that fixed the "E: can't find mount/cache" issues, so try everything.
So my ROM installed but I was still stuck on the white HTC logo. This is where I INSTALLED A NEW KERNEL THROUGH ADB. I wish I knew which kernel I installed, but I have like 10 and I just picked a random one. The point is if you're still stuck at a white HTC screen, install a new kernel.
So I got a recovery on the phone, and then I tried to S-Off again but I didn't have a good ROM installation so that was hanging at the HTC white screen. I then installed CleanROM DE 1.4 and I was able to boot into it, but ran into my initial problem of it crashing after dialing a number and entering infinite reboot. However, it would stay on just long enough for me to run ControlBear's program to S-Off.
So I S-Offed, I downloaded the Gingerbread RUU (the .exe version for Windows), I installed it, and now I can dial numbers and I'm all goodie again. Unfortunately, I honestly think the only way I was escaping my trouble was doing an S-Off, unless they leak a Ice Cream Sanwhich executable for Windows.
TL;DR Install Twerp 2.1 through adb, wipe everything, install CleanROM DE 1.4, install kernel S-Off, run Gingerbread RUU .exe
Flashed OJM's rom in TWRP, and now my phone won't boot at all. I can't find my NANDROID backup I made, and I cannot mount internal storage and when I plug it into my computer, it says that the internal storage needs to be formatted. Am I just screwed or what?
you have access to bootloader or recovery? Also, RUU is likely an option (last resort, of course)
sent from a shining jewel 4g LTE
wow
internale storage corrupted
try formatting it thru hboot if its possible. i think there is something of the sort
try it
---------- Post added at 04:34 AM ---------- Previous post was at 04:32 AM ----------
or try ruu
does it mount the external storage in TWRP? if so why not just put a rom on that and flash it there?
scottspa74 said:
you have access to bootloader or recovery? Also, RUU is likely an option (last resort, of course)
sent from a shining jewel 4g LTE
Click to expand...
Click to collapse
Yes, I do. Currently downloading RUU atm
flex360 said:
wow
internale storage corrupted
try formatting it thru hboot if its possible. i think there is something of the sort
try it
did that, then it booted into recovery, says unable to mount /data
---------- Post added at 04:34 AM ---------- Previous post was at 04:32 AM ----------
or try ruu
Click to expand...
Click to collapse
thoughtlesskyle said:
does it mount the external storage in TWRP? if so why not just put a rom on that and flash it there?
Click to expand...
Click to collapse
Yes it does, and I put one on and it just won't flash it. Keeps rebooting TWRP
Anyone else have 36c492e612ded94745c1dcb28382395c for their md5?
shook187 said:
Stay away from that garbage ROM bro. I will never bash a developer even if I don't like the ROM, but that ROM is half ass.
Sent from my EVO using XDA
Click to expand...
Click to collapse
why do you say that? some other people have flashed it and no problems...far as i read there.
jordan.nave said:
Flashed OJM's rom in TWRP, and now my phone won't boot at all. I can't find my NANDROID backup I made, and I cannot mount internal storage and when I plug it into my computer, it says that the internal storage needs to be formatted. Am I just screwed or what?
Click to expand...
Click to collapse
Did you happen to be playing around with the kernel as well? and how was it flashed?
I hope your Blocks aren't bad nor un-writable, for the message given to you will not be able to fix.
Very easy fix
jordan.nave said:
Flashed OJM's rom in TWRP, and now my phone won't boot at all. I can't find my NANDROID backup I made, and I cannot mount internal storage and when I plug it into my computer, it says that the internal storage needs to be formatted. Am I just screwed or what?
Click to expand...
Click to collapse
I screwed up the same way the very first day I got the phone. The eMMC on this phone tends to get easily corrupted. The fix is extremely easy. Just click Format. Then Flash ROM. Done.
If you do not have custom recovery installed please google how to do it using Android SDK through fastboot.
The good thing about Android phones (and particularly HTC) is that short of dropping an actual brick on the phone it is really hard to "brick"it. I am yet to see one hopelessly dead.
This is in detail:
1. Boot-up into recovery
2. Mount internal storage
3. Connect to a USB port on a computer
4. Right click on the Removable Disk (X where X could be any letter depending on your computer. Format. Done. Disconnect from PC.
5. From within TWRP recovery install the ROM you have downloaded and put on your External microSD card. Do not forget to select "Using External SDCard" before flashing.
I think I'm in trouble. PLEASE HELP!
My phone:
Evo 4G LTE
LazyPanda
JEWEL PUT SHIP S-OFF RL
HBOOT – 1.12.1111
Radio – 1.02.12.0427
Recovery – TWRP 2.2.2
ROM – CyanogenMod 10
I tried to upgrade to TWRP 2.3.1:
Download - Bootloader Method:
http://techerrata.com/file/twrp2/jew....1.0-jewel.zip
Download the file above and rename to PJ75IMG.zip and place it on the root of the sdcard. Boot into bootloader and accept the update. Boot back to the ROM and rename/remove the file
Everything went well and the update was successful. However, my phone is stuck in a boot loop – clocking on the Cyanogen boot animation (the word “CyanogenMod” in the middle of a circle going clockwise on the outside and counter-clockwise on the inside). I let it run as long as 30 minutes - - no luck.
I am able to long-hold the power button to bring me back to the Upgrade screen. If I hit yes <VOL UP>, it updates successfully and asks to hit power to re-boot. If I hit no <VOL DOWN>, the upgrade is aborted and I am asked to hit power to re-boot.
I‘m thinking my options are:
1. Try the “RegawMOD EVO 4G LTE Rooter” to get back to where I was
2. Try the 1.13.165.1 RUU to get back to factory and then re-root.
3. ???
Any thoughts or suggestions?
Thanks,
Gary
Did you put it on the internal or external? If you put it on the external card remove it and reboot to bootloader. This is why I tell people to flash recovery manually
I think I would try and return back to 2.2 since it was working great there and "restore", and find out for sure if my DL source was actually from TeamWin or if any compatible issue may occur with installing or upgrading to the new recovery.
Since you 1.12.1111(modified), just remember that you have to be stock 1.12.000 and s-on "if" you are thinking to go the RUU route.
GaryJohnSr said:
My phone:
Evo 4G LTE
LazyPanda
JEWEL PUT SHIP S-OFF RL
HBOOT – 1.12.1111
Radio – 1.02.12.0427
Recovery – TWRP 2.2.2
ROM – CyanogenMod 10
I tried to upgrade to TWRP 2.3.1:
Download - Bootloader Method:
http://techerrata.com/file/twrp2/jew....1.0-jewel.zip
Download the file above and rename to PJ75IMG.zip and place it on the root of the sdcard. Boot into bootloader and accept the update. Boot back to the ROM and rename/remove the file
Everything went well and the update was successful. However, my phone is stuck in a boot loop – clocking on the Cyanogen boot animation (the word “CyanogenMod” in the middle of a circle going clockwise on the outside and counter-clockwise on the inside). I let it run as long as 30 minutes - - no luck.
I am able to long-hold the power button to bring me back to the Upgrade screen. If I hit yes <VOL UP>, it updates successfully and asks to hit power to re-boot. If I hit no <VOL DOWN>, the upgrade is aborted and I am asked to hit power to re-boot.
I‘m thinking my options are:
1. Try the “RegawMOD EVO 4G LTE Rooter” to get back to where I was
2. Try the 1.13.165.1 RUU to get back to factory and then re-root.
3. ???
Any thoughts or suggestions?
Thanks,
Gary
Click to expand...
Click to collapse
Tekn010933 said:
I think I would try and return back to 2.2 since it was working great there and "restore", and find out for sure if my DL source was actually from TeamWin or if any compatible issue may occur with installing or upgrading to the new recovery.
Since you 1.12.1111(modified), just remember that you have to be stock 1.12.000 and s-on "if" you are thinking to go the RUU route.
Click to expand...
Click to collapse
As long as the update is on the card the bootloader will be stuck trying to install it and reboot or reboot if install is canceled so trying to downgrade is pointless and I don't know if ruu will even recognize the phone in the middle of an update
Try a full wipe and reflash your rom
If the user has an update on the internal the bootloader will be stuck trying to update, no access to recovery
Not bricked.
Great diagnosis bud, any ideas? Even with bootloader attempting to install, is fastboot accessible?
I FIXED IT. Thanks to Tekn010933, {ParanoiA} and om4. Since the new "PJ75IMG.zip" was on the card, it would continue to loop. I figured I would remove the sdcard. I knew there was a chance of corruption, but I removed it and got into TWRP. It was 2.3.1, but I reloaded 2.2.2., updated it to 2.3.1, clean full wipe, NAND restore and back in business.
This was the most scared I've been since I started rooting (my Hero, my OG Evo and my Evo 4G LTE).
WHEW!!!
Here I was thinking you pushed it to internal, well I asked but didn't get an answer so I assumed lol
bricked htc evo 4g sprint
phone will not turn on and when i hold the power button for more than thirty seconds the orange lcd flashes five times then to off again cant even reachthe bootloader screen any help please!!!! i have two years of warranty so worst case senario is i bring it back it and get a new one but if any could help me soon would be greatly appreciated
Hello all,
So I am having an interesting issue with my Rezound which has served me well for the past two years. Last night while I was browsing the internet I got the warning that my battery was going to go dead. Ignored it and kept browsing, eventually causing the phone to auto shutdown, fine, I have a spare battery (love removable batteries), threw that in and it started to boot but gets stuck at the white "HTC" loading screen. I am able to get into HBOOT and get the following.
*** LOCKED ***
VIGOR PVT SHIP S_ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-Boot
Sep 20 2012,17:40:22
When I try to do a factory reset it will act like it is going to start, showing a phone with a green circle and an arrow, and a loading bar. Then before the loading bar begins to get filled in at all (it is just gray with diagonal lines) the green circle changes to a red triangle and an exclamation point.
If I try to boot into recovery I get the same phone with a red triangle image.
This phone is 100% stock unrooted and untouched in any way save for disabling the stock bloatware (I didnt even root it to uninstall that!). AFAIK there was no OTA update done to it yesterday, and I have been using it every day up until now with no real issues.
Simply just the battery died, and now it wont boot. Any ideas?
I am having the same issue on my wife's Rezound. It died last night and went into the same bootloop. Tried a factory reset to no avail. Phone is stock with the same info as previous poster in HBOOT.
I'm familiar with some android development, but know nothing about HTC phones. If somebody could point me in the right direction it would be greatly appreciated.
So I have tried running the stock RUU, no dice, I was already at the latest version.
I then unlocked my bootloader through HTC dev and tried to flash AmonRA so I can do custom ROMs.
Now when I go into my bootloader and select "Recovery" the white HTC screen pops up with a brown progress bar in the top right which fills up quickly, then the phone turns off and that is it until I remove the battery (wont respond to power again after it turns itself off).
So it would appear flashing AmonRA did not work either. Next I will be trying CWM.
Thanks for the update. Keep us posted if anything works. I just don't have the time to learn and try everything right now.
So I got CWM Recovery flashed successfully, but when I boot into recovery and try to wipe I get format failed and mounting errors.
Could my eMMC have been corrupt? How can I fix it?
EDIT: I also get cant mount and cant open on /cache, /system, /sdcard from inside the CWM recovery
Have you attempted to s-off and ruu down to an official exe?
Sent from my DNA using my mind.
I have not done s-off yet, would that fix my mount issues? I am now running TWRP recovery, that also is unable to mount anything. I appear to be having issues with the /dev/block/mmcblk0p35 and /dev/block/mmcblk0p36 and /dev/block/mmcblk0p29 etc areas. At this point any help would be greatly appreciated.
I have put a good 12 hours into trying to get this thing to boot. I feel like I am close and if I could just get it to somehow re-format the whole /block directory then flash a new rom it would would. Pushing an RUU from fastboot did not work, nor did running it from TWRP. TWRP gave me issues in the aforementioned mmcblk areas, and fastboot just says failed, I would guess for the same reason though.
Yes, if all else fails. RUU exe is the last resort
Sent from my DNA using my mind.
I found another phone for the wife to use for now. I'll try to s-off and ruu when i have some time.
Uzephi said:
Yes, if all else fails. RUU exe is the last resort
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Where can I find the instructions and files to get S-Off without access to a ROM and running windows? The JPBear instructions state Linux only and says I need to have a stock ROM.
OK, so from my research I will need to use Linux. Do I need the HTC USB drivers or anything or can I just take a fresh install of Ubuntu and run JPBear? Also, since I have unlocked my bootloader and (tried) to flash a rooted stock rom, do I now need to re-lock and try to run the RUU again? I did try that tonight (re-locking then running the stock RUU) but it still gave me the error that HBOOT was older on the version I was trying to flash.
You won't be able to run any RUU with being s on as their isn't one available for the latest OTA. Try wiping and formatting cache data and system with the latest CWM (Touch). Then follow flash instructions of a ROM for s on.
Sent from my Rezound using Tapatalk 4
I have personally used the windows version of jpbear on a custom ROM to s-off my Rezound. It is somewhere in this forum. I was in a similar pickle and needed s-off to ruu. Albeit, my phone didn't have mount issues, so I don't know if ruu will fix your specific issue, but if anything will, ruu will fix it.
Sent from my Rezound using xda app-developers app
Uzephi said:
I have personally used the windows version of jpbear on a custom ROM to s-off my Rezound. It is somewhere in this forum. I was in a similar pickle and needed s-off to ruu. Albeit, my phone didn't have mount issues, so I don't know if ruu will fix your specific issue, but if anything will, ruu will fix it.
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
I believe an RUU would fix it if I can manage to get S-Off. I found an old version of ControlBear 0.2.2 for windows, when I run it it tells me to connect my phone and install drivers if I run from recovery. If I run from fastboot USB it trys to reboot my device into the ROM. So I dont know if JPBear will even work for me if I don't have access to my ROM.
Jensen567 said:
I believe an RUU would fix it if I can manage to get S-Off. I found an old version of ControlBear 0.2.2 for windows, when I run it it tells me to connect my phone and install drivers if I run from recovery. If I run from fastboot USB it trys to reboot my device into the ROM. So I dont know if JPBear will even work for me if I don't have access to my ROM.
Click to expand...
Click to collapse
i have a guide for obtaining s-off in linux....very well explained and thorough....
REV3NT3CH said:
i have a guide for obtaining s-off in linux....very well explained and thorough....
Click to expand...
Click to collapse
First off let me say a big THANK YOU for taking the time to respond and help me out. I did some searching, this is the guide you are referring to?
http://forum.xda-developers.com/showthread.php?t=2502814&highlight=s-off
I have no qualms with using linux and have some experience with ubuntu I just do not have an install up and running now so I wanted to avoid that if possible, but no big deal. In this thread
http://forum.xda-developers.com/showthread.php?t=1612035&page=202
you suggest I use fastboot usb to reinstall everything, is there a guide for this also? I am able to get to the white HBOOT screen to do fastboot USB, and I am also able to get into TWRP recovery. Version 2.6.3.3. However if I try to wipe anything from inside recovery I get "Unable to mount '/emmc'" or '/cache' '/data' or '/system'.
Sorry for my noobness with flashing, last time I did any of this was when I unlocked/s-off my DINC which was very easy at the time.
EDIT: I notice also in that guide you suggest to start from inside the ROM, I am unable to do this. Will it work from HBOOT, fastboot usb, or recovery?
Jensen567 said:
First off let me say a big THANK YOU for taking the time to respond and help me out. I did some searching, this is the guide you are referring to?
http://forum.xda-developers.com/showthread.php?t=2502814&highlight=s-off
I have no qualms with using linux and have some experience with ubuntu I just do not have an install up and running now so I wanted to avoid that if possible, but no big deal. In this thread
http://forum.xda-developers.com/showthread.php?t=1612035&page=202
you suggest I use fastboot usb to reinstall everything, is there a guide for this also? I am able to get to the white HBOOT screen to do fastboot USB, and I am also able to get into TWRP recovery. Version 2.6.3.3. However if I try to wipe anything from inside recovery I get "Unable to mount '/emmc'" or '/cache' '/data' or '/system'.
Sorry for my noobness with flashing, last time I did any of this was when I unlocked/s-off my DINC which was very easy at the time.
EDIT: I notice also in that guide you suggest to start from inside the ROM, I am unable to do this. Will it work from HBOOT, fastboot usb, or recovery?
Click to expand...
Click to collapse
1.) yes that is the guide im referring to...2.) AHA 2.6.3.3 HAS MOUNT ISSUES AND IS POSTED....go to an earlier version like 2.6.3.0...2.6.3.3 is only meant for FLASHING KITKAT ONLY and nothing else.....also why did you even trey to wipe internal sd anyway its not required...if you want the rezounds proper wipe method i can tell you...keep in mind the dinc is a whole different phone using a whole different motherboard....hence the differences....3.) once you have the proper version ill tell you how to get rid of mount issues
REV3NT3CH said:
1.) yes that is the guide im referring to...2.) AHA 2.6.3.3 HAS MOUNT ISSUES AND IS POSTED....go to an earlier version like 2.6.3.0...2.6.3.3 is only meant for FLASHING KITKAT ONLY and nothing else.....also why did you even trey to wipe internal sd anyway its not required...if you want the rezounds proper wipe method i can tell you...keep in mind the dinc is a whole different phone using a whole different motherboard....hence the differences....3.) once you have the proper version ill tell you how to get rid of mount issues
Click to expand...
Click to collapse
OK, I installed 2.6.3.0 and that is running. Still have mount issues but I am guessing that is normal at this point? I didn't try to wipe the internal SD per say, I was trying to wipe the cache and system to do a reinstall after the battery died and I was stuck at the white HTC boot screen.
Basically I am a noob and was just trying anything/everything to get it booting again. I found my old DINC now and am running that for now so I have some more time to work on it. On a side note, CM7.2 GB is still awesome.
Jensen567 said:
OK, I installed 2.6.3.0 and that is running. Still have mount issues but I am guessing that is normal at this point? I didn't try to wipe the internal SD per say, I was trying to wipe the cache and system to do a reinstall after the battery died and I was stuck at the white HTC boot screen.
Basically I am a noob and was just trying anything/everything to get it booting again. I found my old DINC now and am running that for now so I have some more time to work on it. On a side note, CM7.2 GB is still awesome.
Click to expand...
Click to collapse
so wait you are staying on ice cream sandwhich or lower? ok steps on 2.6.3.0 to get internal back is first go to wipe>advinced wipe and tick internal sd only...then swipe to wipe...youll get an error and thats ok....do the same method again except this time you'll notice it says emmc instead of internal sd....now go to mount option from main screen..then make sure only internal sd is checked and right below all options make sure it says Storage: Internal SDcard (size in mb) if it still says micro sd just tap on that area to change it....tap mount usb and plug into pc...reformat in windows using administrative tools in control panel or if it shows in my computer do it that way.....if you are staying on ICS or lower STAY WITH AMON RA ONLY...twrp and cwm is meant for jb and higher on the rezound....if the above method doesnt work...install amon ra and moun usb that way....you will have to fastboot install the recoveries obviously
REV3NT3CH said:
so wait you are staying on ice cream sandwhich or lower? ok steps on 2.6.3.0 to get internal back is first go to wipe>advinced wipe and tick internal sd only...then swipe to wipe...youll get an error and thats ok....do the same method again except this time you'll notice it says emmc instead of internal sd....now go to mount option from main screen..then make sure only internal sd is checked and right below all options make sure it says Storage: Internal SDcard (size in mb) if it still says micro sd just tap on that area to change it....tap mount usb and plug into pc...reformat in windows using administrative tools in control panel or if it shows in my computer do it that way.....if you are staying on ICS or lower STAY WITH AMON RA ONLY...twrp and cwm is meant for jb and higher on the rezound....if the above method doesnt work...install amon ra and moun usb that way....you will have to fastboot install the recoveries obviously
Click to expand...
Click to collapse
I have not decided what ROM I want to run, for now just getting it booting on the rooted OEM rom is fine.
I tried that method and it did not work. It does say unable to mount /emmc, but it also comes up with unable to mount just about everything else. Nothing shows as mounted under mount from the main menu (I have my SD card removed for now) and when I tap Internal SDcard to mount it I get unable to mount /emmc in the console.
I tried AmonRA first, flashing through fastboot usb, and it did not work for me. When I would select recovery from HBOOT the phone would go to the white HTC screen then the screen shuts off but recovery never comes up. The phone just got hot and would not respond to power button so I pulled the battery.