---------------------------------------------------------------
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
Related
[07oct2010] resolved
I have searched extensively through the forums and have attempted dozens of different solutions and permutations of my own. My Eris will not advance past the splash screen, I can access recovery and bootloader. I've tried many different versions of update.zip through recovery, fails for various reasons, usually signature. Every attempt for PB00IMG.zip in HBOOT yields Main Version is Older. Fast boot gives me (remote: not allow). I've created a gold card, and it's not done me any good, the phone doesn't even acknowledge it, I used the Kingston 2gb and tried GoldCardTool.exe 0.5 and hex editor separately, it appears to have been successful. Ruu doesn't recognize my phone in any of the modes I can access, splash, HBOOT, FastBoot, recovery triangle, recovery.
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-SYN0104
RADIO-2.32.40.11.09
Feb 8 2010,00:08:56
Thanks
USSENTERNCC1701E said:
I have searched extensively through the forums and have attempted dozens of different solutions and permutations of my own. My Eris will not advance past the splash screen, I can access recovery and bootloader. I've tried many different versions of update.zip through recovery, fails for various reasons, usually signature. Every attempt for PB00IMG.zip in HBOOT yields Main Version is Older. Fast boot gives me (remote: not allow). I've created a gold card, and it's not done me any good, the phone doesn't even acknowledge it, I used the Kingston 2gb and tried GoldCardTool.exe 0.5 and hex editor separately, it appears to have been successful. Ruu doesn't recognize my phone in any of the modes I can access, splash, HBOOT, FastBoot, recovery triangle, recovery.
PB00100 XC SHIP S-ON
HBOOT-1.49.0000 (PB0010000)
MICROP-0111
TOUCH PANEL-SYN0104
RADIO-2.32.40.11.09
Feb 8 2010,00:08:56
Thanks
Click to expand...
Click to collapse
I am assuming that this is a completely stock phone with the July 2010 OTA on it?
(I assume this because you mentioned "recovery triangle" - which seems to indicate that you have the stock recovery on the phone.)
I think you are "almost" SOL - but there are a few remote possibilities. I hope you don't mind answering a few questions. But first, some assertions:
- fastboot will not do anything useful for you with an S-ON bootloader; that is the way it works. S-ON means (among other things) that "fastboot is crippled".
- the only "update.zip" files which will work with the stock recovery are signed with HTC's key; furthermore, they are locked to specific versions of the recovery boot. These are the "OTA" zip files. Moreover, they perform binary patching, so they are extremely tightly bound to the exact version of software which pre-exists on the phone.
So, here's my questions:
1) Completely stock phone or not? (Please Elaborate, esp. if you have any root tools on the phone.)
2) Did you try the HBOOT+PB00IMG.zip method with the "Leak-V3" HTC ROM, and also get a "Main Version is Older" error?
3) Before your phone got into this state, did you have USB debugging turned on?
4) Does "adb devices" indicate that adbd is running on the phone when it is in the "Stuck at boot splash screen" state?
5) If it is a stock phone, did you try cold-booting into "Safe Mode" (press and hold trackball down and then press and hold End/Power, and continue to hold down the trackball until the verizon splash screen shows up - about 40 seconds, iirc). If that works - do a factory reset.
Finally - if the phone is (in fact) completely stock - why not take it back to Big Red and ask them to exchange it? (Or upgrade it; lately it seems from reports as if all the Eris refurbs that are left all have problems).
bftb0
bftb0 said:
1) Completely stock phone or not? (Please Elaborate, esp. if you have any root tools on the phone.)
Click to expand...
Click to collapse
Not stock. I rooted my phone with Easy Root, then used 1-Click root and got Amon's Recovery Image. I think I was running Cyanogen. I was trying to get back to stock and no method was working, I was unable to flash with using adb or fastboot, I was able to flash using the recovery image and the way I got the recovery image led me to believe I was able to flash from within the phone, so I got a terminal emulator on the phone and flashed the recovery and boot partitions to an images I extracted from an update.zip that I found, I can't remember where it came from though.
bftb0 said:
2) Did you try the HBOOT+PB00IMG.zip method with the "Leak-V3" HTC ROM, and also get a "Main Version is Older" error?
Click to expand...
Click to collapse
Yes I tried an image i found on androidforums, same error.
bftb0 said:
3) Before your phone got into this state, did you have USB debugging turned on?
Click to expand...
Click to collapse
I believe I did, but it's been a while, it may have been off, I know I was attempting to use adb before hand, and that it did register the device, I don't think I would have disable it, but I can't be sure.
bftb0 said:
4) Does "adb devices" indicate that adbd is running on the phone when it is in the "Stuck at boot splash screen" state?
Click to expand...
Click to collapse
No, adb devices says "List of attached devices" and lists nothing.
bftb0 said:
5) If it is a stock phone, did you try cold-booting into "Safe Mode" (press and hold trackball down and then press and hold End/Power, and continue to hold down the trackball until the verizon splash screen shows up - about 40 seconds, iirc). If that works - do a factory reset.
bftb0
Click to expand...
Click to collapse
I tried, and after a couple minutes it was still on the skateboarding androids. I suppose I should have specified, I don't ever get to the verizon screen.
Thank you
Well, you might just be SOL.
But, I have to say, I still notice a fair bit of ambiguity in the way you describe certain things. For instance, I asked about the "Leak-V3" PB00IMG.zip file, and you replied "an image from Androidforums". (There have been 6 different PB00IMG.zip files from HTC for the Eris.)
Also, you said,
"flashed the recovery and boot partitions to an images I extracted from an update.zip that I found, I can't remember where it came from though"
Click to expand...
Click to collapse
.
As you have discovered, sloppiness gets you into trouble. Almost all of the methods that you are attempting are highly sensitive to versions of software already on the phone, and also past history.
To summarize, it sounds like the current state of your phone is:
(1) 1.49.0000 S-ON Bootloader ( = Leak-V3 )
(2) recovery boot from "an update.zip", origin and version unknown.[SIZE=+1]**[/SIZE]
(3) boot partition from "an update.zip", origin and version unknown.[SIZE=+1]**[/SIZE]
(4) /system, /data, and /cache partitions from a version of "I think I was running Cyanogen."
That's pretty much a disaster - you don't have an engineering bootloader, you don't have a custom recovery, your boot image is mis-matched to the loaded OS, and your OS (obviously) will not boot far enough to gain any access from adb.
As near as I can tell, you really have only one chance at recovery; the RUU method certainly will not work as it requires the OS to be booted at the very beginning so that the phone can be restarted in OEM-78 (aka "RUU") mode, and you can't do that correctly without an HTC-derived 2.1 ROM anyway. (Or manually installing the correct "reboot" binary and supporting shared libs).
Here is what I recommend you try: go back and find the Leak-V3 PB00IMG.zip; it has a MD5 checksum of 1c0b0182356242a9d673a661e7458587. Try to apply it to your phone with the HBOOT method. If you get a "Main Version is Older" message, you are screwed - that is your only hope at the moment.
bftb0
[SIZE=+1]**[/SIZE]If you are able to locate the "update.zip" file that you used (on your PC, I suppose), you might be able to identify the HTC version from the MD5 checksums of the "boot.img" and "recovery.img" files in that "update.zip" file. This listing of checksums for HTC ROMs provides those values. (Note the same post can be used to identify PB00IMG.zip files as well - just compute their "MD5" checksums and look up the value)
PS I don't know when you started on your journey of trying to restore back to factory, but there is this method which uses the normal (Amon_RA) flashing method. It works.
Sorry for all my impercison, I entered into all this without an understanding of how specific everything is, this was my first endeavor into tinkering with any sort of EEPROM OS, I didn't recognize by necessity everything is distinct.
The link listed in the same one I downloaded the PB00IMG.zip from.
Thanks for your time, I guess I'll just find one on eBay with a broken screen and a good ESN.
USSENTERNCC1701E said:
Sorry for all my impercison, I entered into all this without an understanding of how specific everything is, this was my first endeavor into tinkering with any sort of EEPROM OS, I didn't recognize by necessity everything is distinct.
The link listed in the same one I downloaded the PB00IMG.zip from.
Thanks for your time, I guess I'll just find one on eBay with a broken screen and a good ESN.
Click to expand...
Click to collapse
Ouch. Sorry that your phone ended up that way. Sort of a "live brick".
I have flashed, rooted, unrooted, installed Eris ROMs via adb, fastboot, manually with unyaffs, rolled back bootloaders (8 ways to Sunday) - and I don't think there is anything more I could do with your phone even if I had it in my hands.
It's not very ethical, because it is (in fact) your fault that the phone ended up that way it did - but have you considered having VZW replace it?
bftb0
bftb0 said:
It's not very ethical, because it is (in fact) your fault that the phone ended up that way it did - but have you considered having VZW replace it?
bftb0
Click to expand...
Click to collapse
I've thought about it, I can justify the morality to myself by asserting that their is really nothing wrong with the hardware and assuming they have some means of reprogramming it that I don't have access to. The other side to that is, they may have some way of seeing what's been done to it that I don't know about, and then do I get charged?
Well, I took it in store and they just swapped it out, hoping they don't come back at me if they find anything when it gets back to factory. Thanks again for your help.
USSENTERNCC1701E said:
Well, I took it in store and they just swapped it out, hoping they don't come back at me if they find anything when it gets back to factory. Thanks again for your help.
Click to expand...
Click to collapse
Good luck with the new phone. If you plan on rooting, take your time and read as much as you can in the dev forum.
bftb0
if you are rooted and have a recovery and need to return to stock OTA do this:
http://forum.xda-developers.com/showthread.php?t=792026&highlight=cupcake
edit, I see you resolved it already, thats what I get for not reading the thread.
The flash down to cupcake method works in all cases because it overwrites everything on the phone when the 2.1 OTA comes. The only safe stuff is on your SD Card
Hi Everybody,
I have seen the recent posts and guides regarding unrooting especially the guide from Twolazyg. Only problem is, I am already running the stock Sprint 651.3 rom. I always backed up my stock rom and would switch back to update it and I did just that this time to get 651.5 without the pesky CIQ software. I am aware of how to relock the bootloader as per htc instructions but then again I'm not sure of what to do. When I rooted I installed cwm 4.0.1.4 through the method at htcevohacks.com then TWRP came out and I flashed twrp 2.0.0RC0 over cwm. Never had a problem with TWRP so I know it isn't the recovery. I didn't get Flashimage GUI so I was always using fastboot to install roms. Also, I never used the android sdk (at least I think I didn't because its not on my computer) so not too sure when someone says use adb in the instructions. Oh yea, I'm also a noob so take it easy if you can lol.
Initially, I installed a custom rom after rooting and unlocking my bootloader via htc method. Then I wasn't too happy with the roms and just decided to stay rooted but keep my stock rom. I installed app quarantine to freeze some of the unused system apps like friendstream, peep, stocks, etc.. Before I did the update I brought all the apps out of quarantine incase anything screwy happened with app updates.
Fast forward to today, and now after 651.5 update my phone is literally restarting. It keeps booting up to my lock screen and it holds for 1 minute then it just restarts. It's sitting in front of me right now and as I type it has restarted at least 10 times as I have been watching it. It actually started acting up after I let out all the apps from app quarantine yesterday so 651.3 was already screwy with system apps unquarantined.
So I'm trying to unroot and relock so I can send this baby back to Sprint and get a replacement. Already did a master a reset three times and nothing works in terms of stopping the constant rebooting.
I'm just wondering where do I start with any of the steps. Should I just follow the guide exactly or do I have to take different steps???
Thanks
Hiya Buddy said:
Hi Everybody,
I have seen the recent posts and guides regarding unrooting especially the guide from Twolazyg. Only problem is, I am already running the stock Sprint 651.3 rom. I always backed up my stock rom and would switch back to update it and I did just that this time to get 651.5 without the pesky CIQ software. I am aware of how to relock the bootloader as per htc instructions but then again I'm not sure of what to do. When I rooted I installed cwm 4.0.1.4 through the method at htcevohacks.com then TWRP came out and I flashed twrp 2.0.0RC0 over cwm. Never had a problem with TWRP so I know it isn't the recovery. I didn't get Flashimage GUI so I was always using fastboot to install roms. Also, I never used the android sdk (at least I think I didn't because its not on my computer) so not too sure when someone says use adb in the instructions. Oh yea, I'm also a noob so take it easy if you can lol.
Initially, I installed a custom rom after rooting and unlocking my bootloader via htc method. Then I wasn't too happy with the roms and just decided to stay rooted but keep my stock rom. I installed app quarantine to freeze some of the unused system apps like friendstream, peep, stocks, etc.. Before I did the update I brought all the apps out of quarantine incase anything screwy happened with app updates.
Fast forward to today, and now after 651.5 update my phone is literally restarting. It keeps booting up to my lock screen and it holds for 1 minute then it just restarts. It's sitting in front of me right now and as I type it has restarted at least 10 times as I have been watching it. It actually started acting up after I let out all the apps from app quarantine yesterday so 651.3 was already screwy with system apps unquarantined.
So I'm trying to unroot and relock so I can send this baby back to Sprint and get a replacement. Already did a master a reset three times and nothing works in terms of stopping the constant rebooting.
I'm just wondering where do I start with any of the steps. Should I just follow the guide exactly or do I have to take different steps???
Thanks
Click to expand...
Click to collapse
Well first off, Flash Image GUI is a great program, so I want to provided my biased opinion as the author!
Off the top of my head, I am really temped to say your currently rebooting issue could very well be software related and not hardware related.
Moving around system applications, "freezing" and "unfreezing", I personally don't view as the most reliable method.
I view returning the device as the last ditch effort and giving up because everything else has failed and the issue is most likely hardware related.
If you're interested in troubleshooting the issue further, running the RUU, should return the system partition and the kernel back to a completely stock state at which point the rebooting should stop.
If the rebooting stops, then you'll know the issue was trigger by something software related and not hardware related.
Many of the RUU files for the EVO 3D are located at http://www.goo-inside.me/shooter/ruu . The directions/guides are posted all over the place on how to properly process an RUU but they are really fairly simple and bring the device back to 100% stock state.
Hope that helps and good luck!
Thanks for your input joey but weird thing is, when I have my evo 3d plugged in to my pc it does not continuously reboot. For the hour or so I've had it plugged in, it hasn't rebooted at all. It is completely usable. After unplugging it, the reboot cycle begins and it is unusable.
I wanted ask for some help because I never installed android sdk or did anything through adb at all. So if someone says "do it via ADB" I will have no clue as to what to do to fix my phone. I have installed sdk and platform tools to try and relock my bootloader but I'm not sure what to do. I mean, I went back to htc dev step 14, which is to relock I just have to type in fastboot oem lock but because I never did it via sdk method. So I guess I should follow the same method in my TWRP 2.0 folder then? Because I see a file called adb.exe
So, based on Twolazyg's instructions, would I have to put my phone in recovery via fastboot. Then type in the command prompt adb reboot bootloader. Then go to Hboot to flash the RUU and finally type in fastboot oem lock. Is this right???
I tried the instructions provided by Twolazyg but I can't get the first step to work...
So, I hold power + volume down and select fastboot.
Connect to pc with usb cable.
Open up cmd.exe and type in:
cd Desktop\Evo3DTwrp
Then follow instructions.
I type in adb reboot bootloader and then nothing happens.
I get this message on my computer:
* daemon not running. starting it now *
* daemon started sucessfully *
error: device not found
What am I doing wrong???
All I wanna do is unroot so I can return this phone for a new one...
Nevermind people, figured it out lol
Was about to Rage Quit but it works.
Got the RUU working and no longer have superuser and bootloader says relocked
Will now try the update to 651.5 then contemplate a return...
You da man joeykrim! My problem has been resolved
Hiya Buddy said:
Thanks for your input joey but weird thing is, when I have my evo 3d plugged in to my pc it does not continuously reboot. For the hour or so I've had it plugged in, it hasn't rebooted at all. It is completely usable. After unplugging it, the reboot cycle begins and it is unusable.
I wanted ask for some help because I never installed android sdk or did anything through adb at all. So if someone says "do it via ADB" I will have no clue as to what to do to fix my phone. I have installed sdk and platform tools to try and relock my bootloader but I'm not sure what to do. I mean, I went back to htc dev step 14, which is to relock I just have to type in fastboot oem lock but because I never did it via sdk method. So I guess I should follow the same method in my TWRP 2.0 folder then? Because I see a file called adb.exe
So, based on Twolazyg's instructions, would I have to put my phone in recovery via fastboot. Then type in the command prompt adb reboot bootloader. Then go to Hboot to flash the RUU and finally type in fastboot oem lock. Is this right???
Click to expand...
Click to collapse
regarding "adb", this binary is kept inside the android-sdk directory and under the subdirectory platform-tools.
many times ppl extract the adb.exe and the accompanying .dll file, package these two up into their "one click" tools and distribute.
personally, i prefer to grab the official android-sdk from google and their associate adb.exe instead of using copies distributed by other users.
hopefully that helps clarify some of the details around adb!
Hiya Buddy said:
You da man joeykrim! My problem has been resolved
Click to expand...
Click to collapse
always good to hear. another evo 3d saved!
glad it worked out. if any guides/posts were specifically helpful to you, feel free to post back your solution in case anybody else comes across this thread with the same issue.
never stops amazing me how many ppl end up with the exact same issue and these posts can be helpful!
glad to hear the issue was resolved!
@joeykrim
Everything works, but back to rooting for me until Sprint gets their **** together with 651.5 update. I took my phone in for service today after unrooting and relocking the bootloader. I was curious as to why my 3g speeds hover around 100kbps when they're usually at 800-1000kbps. According to the tech, who was running a custom rom on his Epic 4G Touch, he told me the update contained a prl that was screwy and it caused speed issues. I can confirm this with the other two evo 3ds on my account that have never been rooted/modded because they're just as slow with loading up web pages and working with apps. It was prl 21083 that is just not working out with data speed.
On Speed Test, I would put up a screen shot but I'm currently working on rooting lol, the latency would always be around 800ms and the fastest speed I got was 121kbps. There are no outages in my area because I called CS yesterday to set up my appointment and they said the towers are working normally. So it seems the 651.5 update is adds a snappyness to the UI but instead of speeding up the internet, it makes for a rather unpleasant internet experience and makes one question their "truly unlimited data and premium data fee."
So I'm gonna put TWRP back on my phone and pick a new rom based on 651.3 because of the screwed up prl unless I can keep my 651.5 and change the prl.
@Hiya buddy
I have a Sprint evo 3d flashed to reliance (carrier in india). I was on a sense 3.5 rom. I heard about this update and i restored my nandroid of stock ROM. Then i relocked it and flashed RUU (2.08.651.3). And accepted the OTA. Everything is working fine for me. No PRL's / Settings changed. My phone still works on reliance........
I did the same thing, restoring my nandroid backup of OTA 651.3 and did the update. After update 3g speeds are atrocious on Sprint, as for the software the phone is a bit snappier and more fluid than before.
hboot 1.5 s-off. Is this a true s-off or whats the deal
This past weekend I rooted my 3D evo and my girlfriends 3D evo. I had a bunch of problems during the process with mine. receiving 4g on the blackened rom, had to go into the msl settings a couple times, ect.... then when all was said and done, at the boot menu it said s-off.
On the other hand, when i rooted my girlfriends evo 3D, I had no issues at all went through really easily then at the end her's said s-on! I was baffled, I had used the same process, and both of our phones have hboot 1.5?
Does this mean I can install roms from recovery? I have a the full (I think it's revolutionary) recovery on it. Options to install from zip and all.
However I did try and install a custom kernal from kernal manager and had to reinstall the blackened rom (Which is awsome btw) because I couldn't get 4G or wifi. (RCMIX Kernal). When i tried to flash a new kernal over the rcmix, it went through the process rebooted...then nothing still had the RCMIX kernal? So I reinstalled blackened. Totally fine, everything working 100%.
Any explainations, I haven't been able to find anyone with 1.5 hboot s-off doing a google search, only people who say it's coming soon. I also figured this would be the best place to post this considering there is no hboot 1.5 general section. if there is please move this there.
Thanks in advance
sag04463 said:
This past weekend I rooted my 3D evo and my girlfriends 3D evo. I had a bunch of problems during the process with mine. receiving 4g on the blackened rom, had to go into the msl settings a couple times, ect.... then when all was said and done, at the boot menu it said s-off.
On the other hand, when i rooted my girlfriends evo 3D, I had no issues at all went through really easily then at the end her's said s-on! I was baffled, I had used the same process, and both of our phones have hboot 1.5?
Does this mean I can install roms from recovery? I have a the full (I think it's revolutionary) recovery on it. Options to install from zip and all.
However I did try and install a custom kernal from kernal manager and had to reinstall the blackened rom (Which is awsome btw) because I couldn't get 4G or wifi. (RCMIX Kernal). When i tried to flash a new kernal over the rcmix, it went through the process rebooted...then nothing still had the RCMIX kernal? So I reinstalled blackened. Totally fine, everything working 100%.
Any explainations, I haven't been able to find anyone with 1.5 hboot s-off doing a google search, only people who say it's coming soon. I also figured this would be the best place to post this considering there is no hboot 1.5 general section. if there is please move this there.
Thanks in advance
Click to expand...
Click to collapse
Hboot 1.5 s-off is not possible at the moment. Probably wouldn't be worth it to the devs at this point in time with ICS around the corner. That OTA update will most likely change the bootloader.
sent from America....F__k yeah!
@sag04463 Jabawockee is right, that doesn't seem possible. And your issue is a common problem with Hboot 1.5. You gotta get the Flashimage GUI from joeykrim or you could do it via fastboot and remember a few simple commands. That 4G/Wifi issue seems to only be problematic with Hboot 1.5 because HTC didn't fully unlock the bootloader or something (Experts, take it easy on me I'm not sure about this) and it doesn't allow for the installation of custom kernels.
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.
Alright. 3 days and countless hours researching to avoid getting flamed - i've reached my last resort.
I've got an unrooted Thunderbolt on my hands that is stuck in a bootloop. The HTC splash screen is all I can get aside of getting into HBOOT. Factory reset and recovery from the bootloader puts me right back into the boot loop. Ive tried flashing CWM via PG05IMG and it recognizes it but does not prompt me to go through with the install. I can't get ADB to recognize the device because USB debugging is apparently disabled. I have HTC SYNC process/application disabled (tried it enabled as well) and I have revolutionary's HTC driver installed (After it not working prior to its installation -- im getting desperate at this point). I am getting the click noise through my computers audio when I plug in the device to the computer, so I know its at least partially getting recognized - however, I cannot find it in my device manager. Im on WIN7. I have removed SIM and SD. Tried different of each cards. Verified MD5's of all files including the the latest OTA non-root RUU I tried to flash via bootloader (for the record this was my first step to troubleshoot the issue). When I attemped to flash the non-root OTA RUU it checked the file with the little side bar escalating and then brought me right back to the hboot screen with options
Here is the info I have. I was given this phone by someone who didn't want to mess around with trying to get it work, so as far as I know, its not rooted. In fact, im almost positive its all stock, or was. I really hope im missing something silly here. I just can't figure this one out.
MECHA XD SHIP S-ON
HBOOT-1.04.0000
MICROP-/
RADIO-1.48.00.0906w_1
eMMC-boot
Thanks.
-Andrew
EMMC?
I've tried re-balling that EMMC chip also, forgot to mention that. I may need a new one entirely according to some other posts...
Have you tried clearing caches ?
Sent from my ADR6400 using Tapatalk 2
So...you've spent three days trying to flash something to a phone with S-ON?
have you tried...getting S-OFF (root) first?
just sayin'
gcodori said:
So...you've spent three days trying to flash something to a phone with S-ON?
have you tried...getting S-OFF (root) first?
just sayin'
Click to expand...
Click to collapse
can't w/o booting, can htc unlock though but it wont help
trter10 said:
can't w/o booting, can htc unlock though but it wont help
Click to expand...
Click to collapse
Everything you say you are trying to do will not work without root. Can't change the bootloader without it...can't install custom recovery without unlocked bootloader. I might have that backwards, but in any case the only thing that might get you out of looping is to flash a .ruu file in bootloader. If you search the forums, you should find a link to one. A .ruu is a full system image file for the stock vzw t bolt ROM. You will loose all info on your phone (not sd card) but that might do it for you.
remove sd card from phone. back it up and format completely. install into phone.
use the HTC thunderbolt all in one program and see if the phone is recognized. if it is...use it to gain root and s-off. from there you can flash a recovery or go completely back to stock and s-on if you need.
I have an Evo3d through Sprint and about a month ago they started sending me notifications to upgrade to Ice cream sandwich. I did such and immediately my touchscreen started going crazy. If I used the keypad in either position it would just randomly add letters all over the place, the home row would just stop working, and the phone would occasionally appear to lock up. I took the phone into the Sprint repair center and they told me they would not do anything with it because there is a incredibly small dent along the bezel that happened when I dropped the phone over 1 year ago. It has worked for at least a year on Gingerbread with 0 issues. I was then left to my own devices and after looking at several guides finally decided on a guide video to use for flashing to a custom rom, which I was hoping would fix the problem.
I unlocked the phone, simple enough, and from what I could find came to the conclusion that the guide which was for HBOOT-1.50 S-ON was the same image and process for my phone which is HBOOT-1.58 S-ON. I then used the cwm-4.0.1.4-shooter image to load into a "revolution" menu which allowed me to select the ROM which I had previously loaded onto the phone in the sdcard root directory. I selected MeanROM-v45 as per the video's recommendation and it told me it installed. I then rebooted the phone and saw the fancy new loading animation, then I saw the phone background, then I saw the unlock ring, then the phone rebooted in a never ending cycle. After reading the countless threads on what could be wrong, I tired MeanRom-v4.1, and the stock rom which I was led to believe was "Kingdom_Sprint_WWE-0.81.651.0_Radio_1.05.00.0429_NV-SPCS_2.25_0429_PRL21078_test_188785" and it gave me an error when trying to install. I then did more reading and found a new boot image which is "recovery-clockwork-5.0.2.0-shooter" and another rom which claimed to be stock which was "Shooter_S_Sprint_WWE_2.17651.5_odex". This rom reset the boot animation to the stock Sprint one, but alas all my phone does is constantly reboot, except I did notice it says "Safe Mode" in the lower right hand corner of the background before it reboots. I then tried to use the "RUU_Shooter_ICS_35_S_Sprint_WWE_2.89...." application which I was linked to from one forum post or another, and it gives me an error 155, then gives me another error when it tries to recover. Does anyone know how to correct what I apparently messed up? Sometimes some of the instructions are filled with lingo that i don't quite understand, but i can follow directions if they are sufficiently given.
joebandli said:
I have an Evo3d through Sprint and about a month ago they started sending me notifications to upgrade to Ice cream sandwich. I did such and immediately my touchscreen started going crazy. If I used the keypad in either position it would just randomly add letters all over the place, the home row would just stop working, and the phone would occasionally appear to lock up. I took the phone into the Sprint repair center and they told me they would not do anything with it because there is a incredibly small dent along the bezel that happened when I dropped the phone over 1 year ago. It has worked for at least a year on Gingerbread with 0 issues. I was then left to my own devices and after looking at several guides finally decided on a guide video to use for flashing to a custom rom, which I was hoping would fix the problem.
I unlocked the phone, simple enough, and from what I could find came to the conclusion that the guide which was for HBOOT-1.50 S-ON was the same image and process for my phone which is HBOOT-1.58 S-ON. I then used the cwm-4.0.1.4-shooter image to load into a "revolution" menu which allowed me to select the ROM which I had previously loaded onto the phone in the sdcard root directory. I selected MeanROM-v45 as per the video's recommendation and it told me it installed. I then rebooted the phone and saw the fancy new loading animation, then I saw the phone background, then I saw the unlock ring, then the phone rebooted in a never ending cycle. After reading the countless threads on what could be wrong, I tired MeanRom-v4.1, and the stock rom which I was led to believe was "Kingdom_Sprint_WWE-0.81.651.0_Radio_1.05.00.0429_NV-SPCS_2.25_0429_PRL21078_test_188785" and it gave me an error when trying to install. I then did more reading and found a new boot image which is "recovery-clockwork-5.0.2.0-shooter" and another rom which claimed to be stock which was "Shooter_S_Sprint_WWE_2.17651.5_odex". This rom reset the boot animation to the stock Sprint one, but alas all my phone does is constantly reboot, except I did notice it says "Safe Mode" in the lower right hand corner of the background before it reboots. I then tried to use the "RUU_Shooter_ICS_35_S_Sprint_WWE_2.89...." application which I was linked to from one forum post or another, and it gives me an error 155, then gives me another error when it tries to recover. Does anyone know how to correct what I apparently messed up? Sometimes some of the instructions are filled with lingo that i don't quite understand, but i can follow directions if they are sufficiently given.
Click to expand...
Click to collapse
Well since you are S-on and unlocked you have to relock your bootloader to run ruu files. Fastboot oem lock is the command you run in fastboot. Also with older ruu files they only work with older roms and such. as for newer ones like the ics ruu, ics roms such as meanrom ics v2.6 works with only hboot 1.58 and newer firmware. I understand that sometimes these guides and tutorials are not clear enough. That's why you got to ask questions. We are here to help so you can get the best out of your experience with your evo 3d. I would not rely on sprint techs too much because sometimes they will just tell you to do a factory reset. Your phone should be fine. Just relock your bootloader and run the file from the bootloader screen and everything should be peachy. If you want to flash a custom rom after you do the update just unlock your bootloader again. Flash 4ext recovery for your device and do some research on what roms and kernels are compatible with S-on unlocked bootloaders. Fyi 4ext recovery has this thing called the smart flash option that allows you to flash kernels through their recovery without having to do through fastboot. Or try Joeykrims Flash Gui Image. All in all, gaining s-off is the best route to solve most of your problems and makes it easier to flash roms and kernels. There is a method for gaining s-off with the ics ota and hboot 1.58. Just do your research. Best of luck to you.
Oh yeah don't forget to hit the thanks button if I helped you out at all.
Jsparta26 said:
Your phone should be fine. Just relock your bootloader and run the file from the bootloader screen and everything should be peachy.
Click to expand...
Click to collapse
Which file are you reffering to from the bootloader screen?
When I Vol Down + Power On this is what I see
***RELOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012,15:06:44
HBOOT
Now that I have relocked the phone it tries to load PG86DIAG.zip (No Image!), PG86DIAG.nbh (No Image!), PG86DIAG.zip (No Image or wrong image!), PG86IMG.zip, and then it does "Checking..[PG86IMG.zip]" and returns Main Version is Older! Update Fail! Press <Power> to reboot.
I know several of the tutorials and even the "How to Fix" guides I was trying to use to restore the phone has me copy PG86IMG.zip to the sdcard root, so I am guessing I need a different image. Now the only problem is that I have to re unlock the phone so I can "fastboot boot cwm-4.0.1.4-shooter.img" so that I can mount the phone and transfer files to and from it (unless there is another method I can use other than adb, because it does not see it as an attached device)
So what I should do is:
1, Unlock the phone again
2, fastboot boot cwm-4.0.1.4-shooter.img
3, Mount the phone, and copy a file named "PG86IMG.zip" (Which I need to obtain the correct one)
4, Unmount the phone and then relock it?
What would the next step be and do you know where I can get the correct file?
I appreciate the response, I am at my wits end and was about to go waste some cash buying a new phone.
joebandli said:
What would the next step be and do you know where I can get the correct file?
I appreciate the response, I am at my wits end and was about to go waste some cash buying a new phone.
Click to expand...
Click to collapse
Forget about PG86IMG.zip files. Since you are S-ON they have to be signed by HTC and there are very few of those around.
You need the 2.89 RUU.exe from one of the links in this post. Flash that from Windows, then HTC unlock again and follow the guides to flash a custom recovery and then root the stock ROM or a rooted custom ROM.
ramjet73
ramjet73 said:
Forget about PG86IMG.zip files. Since you are S-ON they have to be signed by HTC and there are very few of those around.
You need the 2.89 RUU.exe from one of the links in this post. Flash that from Windows, then HTC unlock again and follow the guides to flash a custom recovery and then root the stock ROM or a rooted custom ROM.
ramjet73
Click to expand...
Click to collapse
Thank a ton, that worked to put my phone back to "working" icecream sandwich.