Related
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
hi xda community i just bout this thunderbolt yesterday from some guy for cheap cuz he said it only makes it to the white htc screen i thought i would be able to fix it by now but i guess its beyond me.
i dont know how it got to this point i do know it has s-on and i can access fastboot however when i select recovery or factory reset it goes directly to the htc white screen and bootloops until it dies. also charging is very difficult like this takes me about 30 mins just to get into fastboot cuz i have to keep messing with it.
any and all help would greatly be appreciated. thanks.
Sounds like there may still be an PG05IMG on the sdcard?
Since you have no clue what has been done, I would flash an RUU to get back to stock and move forward from there.
Take your SDcard out and format it. Download a recent RUU, a quick google search will find you the file. Rename the file exactly to PG05IMG.zip and place it on the root of the SDcard. Boot into Hboot and it should automatically detect the zip and go forward from there. In case you were not aware, you boot into Hboot by holding volume down and power to turn the phone on.
Make sure you get the battery charged up a bit before you try this.
I JUST TRYED DOING THAT RIGHT NOW BUT IT SAYS SOMETHING ABOUT THE VERSION IS OLDER PRESS POWER TO REBOOT SO I GUESS THE VERSION I WAS FLASHING IS OLDER THEN WHAT IT ALREADY HAS. IM DOWNLOADING WHAT I THINK IS THE NEWEST ONE RIGHTNOW BUT IT ENDS IN .EXE
NOT SURE WHAT TO DO WITH THAT. ITS THIS ONE...
RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.5_Radio_0.01.78.0906w_2__NV_8K_1.41_9K_1.64_release_219938_signed.exe
THE ONE THAT I TRIED TO FLASH IN HBOOT WAS THIS ONE...
PG05IMG_Mecha_VERIZON_WWE_1.10.605.3_Radio_1.15.00.0128w_3_NV_8K_1.39_9K_1.61_release_170484_signed.zip (THIS ONE GAVE ME THE ERROR ABOUT VERSION TOO OLD)
SORRY BOUT CAPS DONT KNOW WHAT I WAS THINKING.
Also forgot to mention it says LOCKED in the top of hboot
Update: update process started but hangs at step 7 mdm9k just says updating... So frustrating.
Help me please.
*** LOCKED ***
Mecha xd ship S-ON
HBOOT-1.05.0000
MICROP-/
RADIO-1.48.00.0817r
eMMC-boot
jul 19 2011, 14:51:08
Try flashing this. Rename PG05IMG.zip
http://www.androidpolice.com/2011/1...-fixes-several-issues-from-the-previous-leak/
I tryed that one last night too. Same results just hangs.
Do you guys think im bricked?
Not sure if this will work.....maybe try getting s-off and rooting it???use revolutionary.
i think i have to use adb for that and i cannot get into the rom at all just the white htc screen of death. so i cant enable usb debugging.
Try this rom. Its the latest stock gingerbread rom minus the mdm9k.img file and should bypass that during install in hboot. I cannot say this will work if the current mdm9k partition is messed up, but it is worth a shot. hope this helps.
-Crack
http://www.megaupload.com/?d=8D86PQBO
md5sum: 276b1f14827e463320aed38edc4e4e07
Just tried to flash with hboot got to checking.... But never asked me if I wanted to install the update.
I have one other idea. However I wont be able to get the new file uploaded till later tonight.
No prob thanks for your help ill be checking later then.
Ok, same file as last time. no mdm9k.img file so it should bypass (hypothetically). It should have the HTC security header included to allow the flash. Not sure if it will, since the method I used is experimental. It just wont pass security check and the update wont continue if it doesn't work.
http://www.megaupload.com/?d=2ZV4JHIG
md5sum: aa7fe560ea4d8cc188a7e685e8a4e1f6
-Crack
cool im downloading now...
update: nope. once again didn't ask me if i wanted to install update
Hmm, at the moment I am out of ideas. What have you tried via fastboot? Being s-on I know your options are limited, but it's worth asking or investigating.
i'v tried everything i can think of so far i haven't found many ruu that even ask me if i want to install the update and the ones that do ask me all hang during the the same step. at this point i am desperate ill try any file anyone throws at me so let me know what you have. S-on SUCKS.
So what happens when you do try and run an RUU.exe say the 2.11.605.5 stock RUU?
At a certain point the program will drop your phone into fastboot recovery where it does the flashing. This may sound like a dumb question, but has it been able to get to that point? If I am understanding you, you are able to get the phone to boot into bootloader and fastboot. Which I assume you can send commands via adb fastboot?
***LOCKED*** On Bootloader
Hello All,
First of all thanks for the awesome easy guide !!
This is the first time I am rooting my HTC Tbolt and have had an issue to start with.
Used the instructions in the link below:
http://forum.xda-developers.com/showthread.php?t=1401959
After I download the 2.11.605.5 downgrade zip, I rename it, put in on the SD Card and go to HBOOT and it installs the downgrade just fine.
But at the end of this process, when I try to get the MR4 Radio onto the SD Card and install it, it simply does not happen. HBoot checks for the file, finds it, but nothing happens. I have renamed in properly and followed instructions to the dot.
I also noticed a ***LOCKED*** right on top of the screen and I think this could be an issue.
Can I go ahead and proceed with the Revolutionary Root Technique ? Would this be possible at this point ?
Is there anyway I can get Flash the MR4 Radio before I actually root ?
Also, would I be able to flash the MR4 Radio onto my device after Rooting ?
Any help is much appreciated !
Thanks in advance !
Cheers !
So I decided I would finally S-Off my device today, having been too busy recently due to school and life. I got past the point where you do the wire trick and I thought all was going well, but then it said something along the lines of Error: Still Sober. I exited ControlBear and figured I would just try again. At first, it was stuck at the black Juopunutbear screen, and after trying to turn it off via the power button, I decided to pull the battery and turn it back on. When I did this, it just booted up into the bootloader. I searched the forum and found it was possible to attempt it from the bootloader, so I did. It appeared to be working fine, but then my phone rebooted, and ControlBear just said "Connecting to device..." for a while, then said "Connect device and install drivers." Now, my phone only boots into bootloader, my laptop doesn't recognize that it's plugged in (though it will say fastboot USB on the phone), and ControlBear just tells me to "Connect device and install drivers." I don't know where to go from here. Help? Has anyone else had this issue?
Never mind that problem! I rebooted my computer, then it detected my phone just fine. I got the wire trick this time, but now I'm stuck at a point where it keeps rebooting my phone into amonra and ControlBear doesn't detect it?
and again...nevermind! simply powered down, then powered back up, and all was well. What's weird, though, is that it didn't wipe my SD card....all the information is still on it. I would think something went wrong, but when I go to my bootloader, it says S-Off...oh well! Not about to complain about a functional SD card!
Sorry, just read your posts. I experienced each of the same problems along the way But with trying and trying, finally got it. Congrats and welcome to the s-off club!
pmterp said:
Sorry, just read your posts. I experienced each of the same problems along the way But with trying and trying, finally got it. Congrats and welcome to the s-off club!
Click to expand...
Click to collapse
Yeah, I was a little freaked out at first. But I figured, it still does something, so at least I'm not bricked! haha. Thanks! It's good to be part of the club!
i to am stuck in the bootloader. i f-ed my phone up so i decided to relock and run the ruu and that failed.now it says relocked security warning none of my computers see my rezound, adb wont see it ether. i have tried a lot of stuff but no go.
anyone have any advice?
neckbonest said:
i to am stuck in the bootloader. i f-ed my phone up so i decided to relock and run the ruu and that failed.now it says relocked security warning none of my computers see my rezound, adb wont see it ether. i have tried a lot of stuff but no go.
anyone have any advice?
Click to expand...
Click to collapse
When you say it failed. What was the nature of the failure? What did the screen say?
Did you rename the RUU to PH98IMG? Hopefully you have a card reader. Take the SD card out and make sure the RUU is renamed properly. Put it back into your phone and reboot. When the phone goes into HBOOT does it look for and find the card? It should find the PH98IMG file for you to flash. Its been said that you should flash this twice.
topgun1953 said:
When you say it failed. What was the nature of the failure? What did the screen say?
Did you rename the RUU to PH98IMG? Hopefully you have a card reader. Take the SD card out and make sure the RUU is renamed properly. Put it back into your phone and reboot. When the phone goes into HBOOT does it look for and find the card? It should find the PH98IMG file for you to flash. Its been said that you should flash this twice.
Click to expand...
Click to collapse
i did rename it to ph98img and it found it but said checking ph98img and then nothing. i got it up and going anyway. i used the all in one toolkit and started from the beginning and did everything and it worked
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.
Okay. So, I unlocked my bootloader, rooted my phone and then went to do the S-Off with the "wire trick." Well, during the Control Bear program it got to the 5th beer and rebooted my phone to the black screen with the phone and green arrows in a circle on it. It then couldn't find the device after 5 attempts of doing so. Yes, I had the drivers installed properly for the phone and ADB - so I don't believe that was the issue. Anyways, I closed Control Bear and unplugged my phone. Restarted my phone and Control Bear and it got stuck on the same screen, but now it can't find the device. I put the phone in fastboot, Control Bear detected it and then it booted up to the green arrow screen again.
At this point, I figure I just need to do a factory reset and everything should be fine. WRONG!
So far I have flashed 4EXT touch recovery so that I can attempt to flash a custom ROM. I tried flashing two different ROMs and after a successful installation it reboots and then gets to the same green arrow screen. I've also attempted to flash a stock RUU by putting it on the external SD card, renaming it PH85IMG.zip and it only gets through the blue status bar in the upper right corner and then goes back to the fast boot screen. Rebooting it afterward takes me to the same green arrow screen.
Suggestions on resurrecting my phone? I'd really like to not have to go through the unbricking BS in this thread: http://forum.xda-developers.com/showthread.php?t=1627882
Carrier
OS version
etc.
Info then problem solving after.
Most likely you can just restore a stock ruu, the one you used is probably older since you dug up a hard brick recovery thread though you have a softbrick, tells me you read a far way back than you needed to, so shoot some info, start solving from there.
TMOUS
Was running Stock ICS 4.0.3
HBOOT 1.93.0002
Dark Nightmare said:
Carrier
OS version
etc.
Info then problem solving after.
Most likely you can just restore a stock ruu, the one you used is probably older since you dug up a hard brick recovery thread though you have a softbrick, tells me you read a far way back than you needed to, so shoot some info, start solving from there.
Click to expand...
Click to collapse
Here: http://d-h.st/3VD
I don't know if that's the one you downloaded, but that's the latest image we have, you already know the process of renaming the file and placing it on your external sd card, also before you attempt to reload the stock RUU, don't forget to lock your bootloader, since you're s-on. It will say relocked, but that's fine, then put your sd card in and reboot into bootloader after relocking, watch the magic happen, hit volume up to update.
Ah! That's the step I was forgetting: relocking my bootloader! Thanks. I'm gonna get on that now. I'll let you know how it goes.
Dark Nightmare said:
Here: http://d-h.st/3VD
I don't know if that's the one you downloaded, but that's the latest image we have, you already know the process of renaming the file and placing it on your external sd card, also before you attempt to reload the stock RUU, don't forget to lock your bootloader, since you're s-on. It will say relocked, but that's fine, then put your sd card in and reboot into bootloader after relocking, watch the magic happen, hit volume up to update.
Click to expand...
Click to collapse
I figured, but I could've been wrong, yup let me know when you boot.
YEAH! That worked! Thanks so much! I think I'm gonna skip doing S-Off for now. LOL
DJ_Caibel said:
YEAH! That worked! Thanks so much! I think I'm gonna skip doing S-Off for now. LOL
Click to expand...
Click to collapse
:highfive:
Lol it's not exactly needed unless you wanna mess with things on an advanced level or go back to GB, which I doubt you do, so no worries.
I was looking to SuperCID, but I'm gonna leave that be and be happy with it as is. Thanks again for your help.
Dark Nightmare said:
:highfive:
Lol it's not exactly needed unless you wanna mess with things on an advanced level or go back to GB, which I doubt you do, so no worries.
Click to expand...
Click to collapse