I am running a cm7 nightly on my Aria which still has a 0.57 hboot (i rooted long ago with unrevoked, and unrevoked3 is not working for me now). I am trying to get cwm recovery 2.5.0.7 to stick, but every time I boot, it reverts back to 2.5.0.1. Some thread said to try with s-off, but my hboot is version 0.57. So now, how do I get my hboot to a newer version?
thanks in advance
The only way to install a different version of Clockwork in your phone's current state is to run Unrevoked again on the device, but select a custom recovery img for it use. To do that, you need to have the USB cable disconnected when you run Unrevoked and go to File > Custom Recovery.
Unfortunately Unrevoked assumes you are using the default Aria ROM when you use it, so what you may need to do is actually restore the device to factory condition by using the 2.1 RUU (NOT the 2.2.2 RUU!), then run Unrevoked again, being careful to select the new Clockworkmod image before plugging the phone in.
If you don't care about off-mode charging, then I suggest that you just stick with the recovery version you have. There is virtually no difference between them and you'd be putting yourself through much trouble for little reason. If you do want to go to the trouble, you might as well go the S-OFF route.
If you want to S-OFF, which makes the process of replacing the version of Clockworkmod trivial, then you would need to use the 2.2.2 RUU on your phone first. This would update your HBOOT to version 1.02, then you can use Revolutionary to S-OFF the phone. As long as you take a Nandroid backup before all of this, you can even restore your ROM afterward if you want.
drumist said:
The only way to install a different version of Clockwork in your phone's current state is to run Unrevoked again on the device, but select a custom recovery img for it use. To do that, you need to have the USB cable disconnected when you run Unrevoked and go to File > Custom Recovery.
Unfortunately Unrevoked assumes you are using the default Aria ROM when you use it, so what you may need to do is actually restore the device to factory condition by using the 2.1 RUU (NOT the 2.2.2 RUU!), then run Unrevoked again, being careful to select the new Clockworkmod image before plugging the phone in.
If you don't care about off-mode charging, then I suggest that you just stick with the recovery version you have. There is virtually no difference between them and you'd be putting yourself through much trouble for little reason. If you do want to go to the trouble, you might as well go the S-OFF route.
If you want to S-OFF, which makes the process of replacing the version of Clockworkmod trivial, then you would need to use the 2.2.2 RUU on your phone first. This would update your HBOOT to version 1.02, then you can use Revolutionary to S-OFF the phone. As long as you take a Nandroid backup before all of this, you can even restore your ROM afterward if you want.
Click to expand...
Click to collapse
Thanks much drumist... maybe when I have some time to kill, i'll try this out. Basically my main reason for wanting to get off 2.5.0.1 was the offmode charging. But it does not bother me so much that I cannot wait a few more days/weeks
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
Related
Im no pro at this stuff by any means, but I have modded the heck out of 5 personal phones and numerous other devices for friends and co workers.
I see a lot of talk of radio's and RUU, are these the same thing? The names are so confusing to me at the moment. Im used to 4 digit Radio names that tend to work on every rom. It seems as if some of the roms are coming with their own modified radios ( RUU's? ) Just wondering if anyone could clarify some basic information on this whole deal.
Secondly it seems as if these RUU/Radio 's are flashed via stock recovery. How does one boot their TB into stock recovery and what are the controls once in stock recovery ( stock recovery and bootloader are the same thing, correct? )
How do I boot into CWR from a dead phone? If I should happen to soft brick my phone or something in the future, how do I get into CWR without being able to boot?
And lastly, can someone give me a brief explanation of what S-on and S-off are? I assume anyone thats rooted is running s-off, correct?
So far I'm rooted running the battery sipper Kernel and I don't really know what direction to take, just trying to do my research. Might wait for CM7 support to start flashing, as this phone really isn't that bad..
Thanks in advance!
I'm still pretty new to all of this, but this is what I've learned so far.
RUU and the radio are different. RUU has everything, the apps the firmware and radio in it. Basically what you need when you wipe your phone and go back to completely stock. Where as radio just updates your radio or baseband.
It's kind of confusing the terms that are thrown around. Some people call it Hboot some call it bootloader. To get into it, turn off your phone, hold Vol down and then the power button. Let go and you should boot into bootloader.
Having S-Off just means your phone is unlock. You're able to access files and folders that are normally locked from you. Which lets you flash roms etc.. S-on, those files/folders are locked.
RUU is short for ROM Upgrade Utility - it's an historical name, based on a utility used to upgrade older HTC phones. For HTC Android phones, the HUU files contain images which get flashed to the phone.
Bootloader is a generic term on Android phones - the HTC one is call Hboot.
Recovery is a separate app/partition, it can be started from Hboot. If you root, you'll probably install Clockworkmod Recovery, which lets you backup/restore the partitions. It should also prevent an OTA update from being installed.
S-On/S-Off refer to a security feature which prevents unsigned images from being flashed. Rooting should set S-Off, which lets you make changes.
Every time I boot into hboot it wants me to confirm an update after it performs an operation it did during the root process. Should I remove that file from my sd?
Sent from my ADR6400L using XDA App
If you have an PG05IMG.zip on your sdcard, remove it. You don't want to leave it laying around after it's been flashed.
mike.s said:
RUU is short for ROM Upgrade Utility - it's an historical name, based on a utility used to upgrade older HTC phones. For HTC Android phones, the HUU files contain images which get flashed to the phone.
Bootloader is a generic term on Android phones - the HTC one is call Hboot.
Recovery is a separate app/partition, it can be started from Hboot. If you root, you'll probably install Clockworkmod Recovery, which lets you backup/restore the partitions. It should also prevent an OTA update from being installed.
S-On/S-Off refer to a security feature which prevents unsigned images from being flashed. Rooting should set S-Off, which lets you make changes.
Click to expand...
Click to collapse
I had a pretty good idea what these were, but great explanations. Thank You
mike.s said:
RUU is short for ROM Upgrade Utility - it's an historical name, based on a utility used to upgrade older HTC phones. For HTC Android phones, the HUU files contain images which get flashed to the phone.
Bootloader is a generic term on Android phones - the HTC one is call Hboot.
Recovery is a separate app/partition, it can be started from Hboot. If you root, you'll probably install Clockworkmod Recovery, which lets you backup/restore the partitions. It should also prevent an OTA update from being installed.
S-On/S-Off refer to a security feature which prevents unsigned images from being flashed. Rooting should set S-Off, which lets you make changes.
Click to expand...
Click to collapse
Nice, Simple explanations. Very clear and helpful. Thanks.
I've just received my HTC EVO 3D GSM, and i want to root it, S-OFF, CWMR and that..
I've had a HTC Desire before, rooted and CWMR but not S-OFF, and i was running CyanogenMod 7 on it.
I've decided (so far) to keep my EVO 3D running stock ROM.
But i do want root, to be able to do nandroid backups, titantium backup, underclock/overclock it, etc etc.
Can i simply use Revoluntionary to S-OFF and install CWMR, and then flash "su-2.3.6.3-efgh-fixed-unsigned.zip" to achieve root (aka SU) ?
And then i'll have root, without wiping or resetting anything on my phone?
I'm semi new to this, and i really don't want anything to go wrong
On my CDMA Evo, I skipped the backups and stuff and it never wiped or asked me to wipe. I still ended up with S-OFF, twrp, root, etc. without having to wipe.
I'm the exact same as you, just came from a HTC Desire with CM7 to an EVO 3D.
Id really like to know what the best process is, from what i can tell the HTC method isn't the one to us.
The other thing I'd like to know is exactly what is the problem with phone that have been updated to 2.3.4, people have said not to update if you want to root??
Check the gsm dev section...gsm doesnt have much to play with right now but im sure it will soon
Hey, a little update and maybe some help to others in the same situation as mine.
I've now successfully rooted & S-OFF'd my HTC EVO 3D GSM, though still using stock ROM.
I followed this lovely guide, which was very nice, and worked like a treat.
http://www.youtube.com/watch?v=Smp6cT4UEKE&feature=related
The only thing i did different was that i used another SU.zip file, since from reading on these forums, the one he linked (in the video) had some errors, so i used the file others recommended.
Recommended SU.zip file:
http://forum.xda-developers.com/showpost.php?p=16651725&postcount=17
ronin201085 said:
I'm the exact same as you, just came from a HTC Desire with CM7 to an EVO 3D.
Id really like to know what the best process is, from what i can tell the HTC method isn't the one to us.
The other thing I'd like to know is exactly what is the problem with phone that have been updated to 2.3.4, people have said not to update if you want to root??
Click to expand...
Click to collapse
The HTC Method isn't optimal, since it will not S-OFF your phone, and there are far better ways to unlock your phone properly.
My EVO came preinstalled with 2.3.4, so i'm fairly sure the android version doesn't change anything.
There are different hboot versions floating around, and mine came with 1.49.0007, which can easily be rooted & S-OFF'd with the proper tools (as i linked in my last post).
The 1.49.0008 version is not working properly at the moment i believe (correct me if i'm wrong?)
And if you update your phone to the newest version, you'll get hboot version 1.50, which is not rootable yet (not stable atleast, think i saw some experimental roots at some point?)
And as for more info, i did not loose any data or apps or anything when rooting & S-OFF, so it worked perfectly
Hey thanks for the help, thought I'd just put everything i have down for anyone else. This will S-OFF and Permanent Root an EVO 3D.
Model: HTC EVO 3D GSM (shooter_U)
Android: Gingerbread 2.3.4
Hboot: 1.49.0007
1. Enable USB Debugging on your Phone.
2. Connect Phone to Computers USB.
3. Download "revolutionary-0.4pre4" from http://revolutionary.io/
4. Get Beta Key from http://revolutionary.io/
5. Download & Install "HTCDriver3.0.0.007" from http://unrevoked.com/rootwiki/doku.php/public/revolutionary
6. Run "revolutionary.exe" from "revolutionary-0.4pre4"
7. Phone should reboot 4 times
8. Type Yes to install Clockwork Recovery Mod.
9. Download "su-2.3.6.3-efgh-fixed-unsigned" from http://forum.xda-developers.com/showpost.php?p=16651725&postcount=17
10. Copy "su-2.3.6.3-efgh-fixed-unsigned" zip file to the root of your SD Card
11. Boot into Recovery by Powering off the Phone, then powering thge phone on by holding the "Power Button and Volume Down Button"
12. Press the Volume Down button to select "Recovery" and press "Power Button" to Select. Then Choose "Install ZIP from SD", and install "su-2.3.6.3-efgh-fixed-unsigned".
13. Done (now check you have SuperUser App, maybe go get Titanium Backup & ROM Manager).
Thanks to Moonbloom, Revolutionary and http://www.youtube.com/watch?v=Smp6cT4UEKE for help.
No problem mate, glad i can help
From what i've seen (personally, on my own phone) and heard on these forums, ROMManager doesn't work properly with HTC EVO 3D GSM.
When i installed the free version of ROMManager, it didn't recognize that i had ClockWorkMod Recovery, but when i rebooted into recovery, it clearly showed that i had CWMR installed.
A lot of people have had this issue, and when you go into ROMManager, it will ask you to flash CWMR to the latest version. If you do this after having used Revolutionary (including the entire process) it will completely **** up your S-OFF, root, CWMR and everything, so don't try and flash CWMR from within ROMManager.
All the things you can do in ROMManager are also doable if you reboot your phone into recovery (just without the fancy ROMManager GUI)
I am a rooted htc rezound user and am in desperate need for help. My rezound is rooted and the bootloader is unlocked. I just recently tried the new ICS (sense 3.5) rom that was released yesterday. Before i used the rom i did a nandroid backup and then a factory reset. Once i was finished with the rom (because of the bugs it carried), i went to restore my phone using the nandroid backup. When the phone booted back up, after it hit the HTC splash screen, it freezes. The phone is still on, but stuck on a black screen.
I have tried everything. Restoring the nandroid backup multiple times. Flashing a stock rom of the htc rezound in the recovery and also (changing the name to PH98IMG) and the tried flashing it through bootloader/hboot. I also took the stock kernel and did the same exact thing. Ive also downloaded the automatic (.exe) RUU update of the stock rom, from Scott's Roms, but that just kept giving me an "Update Fail" message.
Please help me!
.
Thread moved. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
No offense, but this is what you get for flashing a leak without understanding the repercussions. Fortunately, you can be helped but in the future it may not be possible to restore to an earlier version if you flash a leak via a PH98IMG.zip.
Several things you and others must understand now that you have flashed your phone via the PH98IMG.zip leak. If you flashed scott's rom of the leak, you are fine and this DOESN'T apply to you.
1) Your mainver was updated. It is possible you WILL NOT be able to EVER use an RUU to restore in the future. The RUU checks for the mainver and if yours is newer, it will error. A new RUU of the official ICS update will probably work, but that could be a ways off and you could be screwed if you need to RUU in the mean time.
2) Since your mainver was updated, the current ways to install kernels that involve PH98IMG.zips won't work unless you modify them yourself. So you will have to install them via fastboot. Some of them are distributed as zImages so you can't flash those anymore without devs updating their tools. It is unlikely that they will, because in order for them to work with your phones, it will update everyone elses mainver when they run the kernel installation and doing that for everyone would be irresponsible.
DO NOT FLASH THIS IF YOU DIDN'T UPDATE TO THE LEAK VIA A PH98IMG.ZIP IF YOU FLASHED THE BOOT IMAGE WITH FASTBOOT OR CLEANFLASH YOU ARE FINE. IF YOU MODIFIED THE android-info.txt YOURSELF BEFORE FLASHING BECAUSE YOU ARE SMART, DON'T FLASH THIS EITHER.
Anyway, to use:
1) Wipe in recovery
2) Format /system in recovery
3) Run your nandroid restore or install a rom of your choice.
4) Flash the PH98IMG.zip from the bootloader.
Restart and you should be OK
con247 said:
No offense, but this is what you get for flashing a leak without understanding the repercussions. Fortunately, you can be helped but in the future it may not be possible to restore to an earlier version if you flash a leak via a PH98IMG.zip.
Several things you and others must understand now that you have flashed your phone via the PH98IMG.zip leak. If you flashed scott's rom of the leak, you are fine and this DOESN'T apply to you.
1) Your mainver was updated. It is possible you WILL NOT be able to EVER use an RUU to restore in the future. The RUU checks for the mainver and if yours is newer, it will error. A new RUU of the official ICS update will probably work, but that could be a ways off and you could be screwed if you need to RUU in the mean time.
2) Since your mainver was updated, the current ways to install kernels that involve PH98IMG.zips won't work unless you modify them yourself. So you will have to install them via fastboot. Some of them are distributed as zImages so you can't flash those anymore without devs updating their tools. It is unlikely that they will, because in order for them to work with your phones, it will update everyone elses mainver when they run the kernel installation and doing that for everyone would be irresponsible.
Anyway. To restore the stock kernel, I am building a special PH98IMG.zip right now. DO NOT FLASH THIS IF YOU DIDN'T UPDATE TO THE LEAK VIA A PH98IMG.ZIP IF YOU FLASHED THE BOOT IMAGE WITH FASTBOOT OR CLEANFLASH YOU ARE FINE. IF YOU MODIFIED THE android-info.txt YOURSELF BEFORE FLASHING BECAUSE YOU ARE SMART, DON'T FLASH THIS EITHER.
Anyway, to use:
1) Wipe in recovery
2) Format /system in recovery
3) Run your nandroid restore
4) Flash the PH98IMG.zip from the bootloader.
Restart and you should be OK
Click to expand...
Click to collapse
Omg, thank you sooooooooo much. It worked beautifully! Thank you times a million!
con247 said:
No offense, but this is what you get for flashing a leak without understanding the repercussions. Fortunately, you can be helped but in the future it may not be possible to restore to an earlier version if you flash a leak via a PH98IMG.zip.
Several things you and others must understand now that you have flashed your phone via the PH98IMG.zip leak. If you flashed scott's rom of the leak, you are fine and this DOESN'T apply to you.
1) Your mainver was updated. It is possible you WILL NOT be able to EVER use an RUU to restore in the future. The RUU checks for the mainver and if yours is newer, it will error. A new RUU of the official ICS update will probably work, but that could be a ways off and you could be screwed if you need to RUU in the mean time.
2) Since your mainver was updated, the current ways to install kernels that involve PH98IMG.zips won't work unless you modify them yourself. So you will have to install them via fastboot. Some of them are distributed as zImages so you can't flash those anymore without devs updating their tools. It is unlikely that they will, because in order for them to work with your phones, it will update everyone elses mainver when they run the kernel installation and doing that for everyone would be irresponsible.
Anyway. To restore the stock kernel, I am building a special PH98IMG.zip right now. DO NOT FLASH THIS IF YOU DIDN'T UPDATE TO THE LEAK VIA A PH98IMG.ZIP IF YOU FLASHED THE BOOT IMAGE WITH FASTBOOT OR CLEANFLASH YOU ARE FINE. IF YOU MODIFIED THE android-info.txt YOURSELF BEFORE FLASHING BECAUSE YOU ARE SMART, DON'T FLASH THIS EITHER.
Anyway, to use:
1) Wipe in recovery
2) Format /system in recovery
3) Run your nandroid restore
4) Flash the PH98IMG.zip from the bootloader.
Restart and you should be OK
Click to expand...
Click to collapse
As stupid as it was that I installed that PH98IMG.zip without looking further into it, or if I had just used fast boot, or cleanFLASH I wouldn't be in this mess. I mainly blame it on having the Eris, INC1, and INC2 all S-OFF, esp my latest phone before the Rezound inc2, was perma S-OFF thanks to the XTC clip so I could flash just about anything without repercussion. But you live and you learn. The Eris had crazy 2.1 leaks and people got stuck on some bad builds, and not only that they were unable to root when root finally came out, because they flashed the 2.1 leak.. I thought I learned my lesson then but with this I didn't know any better. Learn something new everyday. but I disagree with this part. "It is possible you WILL NOT be able to EVER use an RUU to restore in the future."
Jcase has assured me this is not true.
Ignore This and the next post plz
I need ten post in order to post on development forums. I am just going to use my thread so plz ignore this.thnks
I need ten post in order to post on development forums. I am just going to use my thread so plz ignore this.thnks
ggggggggggggggg
hhhhhhhhhhh
Don't give up now! You're almost there...
Lol.. i had to do same to be able to post to the appropriate threads and forums ...
Careful about that. If a mod's having a bad day your posts could be deleted.
Just sayin'.
Sent from my Unlocked/Rooted Rezound running CleanROM 2.0/AmonRa
Sounds like you haven't gotten a hang of flashing a ROM with this device. Try the following.
1 - Download Cleanflash to computer
2 - Download ROM you want to install.
3 - Using a ZIP program, look in the ROM and copy the boot.img file and put in the Cleanflash folder.
4 - Open the back cover, pull battery, wait 10 seconds, put back battery and cover.
5 - Press and hold Vol-, then power for 2 seconds, release power, wait for hboot screen, then release vol-
6 - Connect phone to computer
7 - Make sure HTC Sync is not running on computer
8 - Run CleanFlash and use option 2 to flash boot.img to phone
9 - On the phone, use vol keys to go to recovery (I assume you have Amon Ra recovery already installed)
10 - Follow the menu to mount your sd card
11 - From the computer, your phone's sd card should now show up as a drive
12 - Copy ROM (entire zip file) to sd card, while your at it make sure there is no other ZIP file on the card. You should also mount the internal card and make sure there are no zip files there either.
13 - Unmount the card and disconnect from computer
14 - Now flash the new ROM
15 - reboot phone
feralicious said:
Don't give up now! You're almost there...
Click to expand...
Click to collapse
LOL (I hope an LOL is not cause for banishment)
Sent from my ADR6425LVW using XDA App
Considering I can't post in the development forum yet, I'll try asking here first. I've been reading up for the past few days on flashing recovery and ROMs for my new Rezound, mostly on ADB today to get a feel for the very basics. Right now I'm trying to get Amon Ra onto my device, only to run into the command prompt telling me, "error: cannot load 'recovery-ra-vigor-3.12b-gnm'. The recovery.img is in the root directory where the fastboot and adb executables are located. What am I missing? It's likely a simple fix, but as of yet my searches aren't finding the results I'm after.
Also, when I tried using fastboot to reboot the device to the bootloader (fastboot reboot-bootloader) I got a < waiting for device > message. I ended up just doing a battery pull to get into the fastboot menu on the phone. And as I've seen it asked previously, I did install the drivers when I was going through the unlock process last night. Any suggestions?
canned karma said:
Considering I can't post in the development forum yet, I'll try asking here first. I've been reading up for the past few days on flashing recovery and ROMs for my new Rezound, mostly on ADB today to get a feel for the very basics. Right now I'm trying to get Amon Ra onto my device, only to run into the command prompt telling me, "error: cannot load 'recovery-ra-vigor-3.12b-gnm'. The recovery.img is in the root directory where the fastboot and adb executables are located. What am I missing? It's likely a simple fix, but as of yet my searches aren't finding the results I'm after.
Also, when I tried using fastboot to reboot the device to the bootloader (fastboot reboot-bootloader) I got a < waiting for device > message. I ended up just doing a battery pull to get into the fastboot menu on the phone. And as I've seen it asked previously, I did install the drivers when I was going through the unlock process last night. Any suggestions?
Click to expand...
Click to collapse
Recovery img has to be in the same folder as the fast boot file. Second...you must make sure too add the file ext for that file. Should be .img for a recovery file.
Sent from my ADR6425LVW using XDA App
I hadn't added in the file extension, that did the trick nicely. Thanks!
i love
lamp and rezound
Can i use the PH8 zip to return my Rezound to stock? I am on Scotts leaked ICS rom. It works and all but i want to restore my phone to stock. Im on a Mac so i can't use a RUU. Is there a zip of the latest RUU i can flash in Hboot?
There is a stickied post with the stock vigor RUU's that the phone's came with . Shouldn't have an issue since you used Scott's version he altered the mainver to avoid issues with going back to stock.
Need to relock then run RUU though FYI.. just in case you weren't clear about that.
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
I had much the same problem with my cdma, hboot 1.5, S-On shooter. When I was S-On none of the ICS roms would work. The all bootlooped on me. If you follow the rooting method found here on xda, it will get you back to a stock Rooted GB Rom.
go into hboot -> fastboot USB-> run command dos -> fastboot cwm-4.0.1.4-shooter.IMG -> flash the 2.17 firmware-> enjoy.
I had to S-off with Juopunutbear, then re-run that root/flash to get past the bootloops.
Sent from my Shooter using xda app-developers app
Unfortunately I have tried that and it still is not working.
My only suggestion would be to try it a few times, other then that, its above my head.
Sent from my shooter using xda app-developers app
rookiemistake said:
I am an unfortunate rookie, and have made mistakes, hence the name. I want to return my phone to stock from htcdev unlock, s-on, hboot 1.5. with a boot loop on meanom ICS for the evo 3d. I have tried to use older ruu shooters. Relock with fastbot oem lock, and then pg86img. However with the bootloop I can not access anything unless I unlock again, and then go into recovery. This is all that I can think of at the moment that might help.
Kill the rookie!!! PLEASE HELP!!
Click to expand...
Click to collapse
Have you tried one of the ruu exe files that you run from your computer? If you are trying to go stock, you should be able to relock the bootloader and run the ruu and that's it.
Sent from my ICS 3VO with Tapatalk 2
First of all I want to thank everyone that has been attempting to assist me with my problem. I have tried to relock since I am on htcdev unlock and then run an ruu force via my computer. I get an installation aborted error when trying to flash pg86img via recovery. I don't know what else to say.
You can't flash a bootloader zip from recovery. You have to flash it from hboot. Also make sure the zip is named correctly "PG86IMG.zip" without the quotes. Also make sure the zip is on the root of your sd as in not in any folders. Once you've named the zip correctly and placed it correctly then power off the phone. Hold down the volume down button and tap the power button. You should boot into the bootloader wait until the phone recognizes the zip and follow the on screen instructions. Hopefully this helps.
#Root-Hack_Mod*Always\=LTE
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
rookiemistake said:
Thank you again. I tried your directions, it did recognize the pg86img. However it did not give me any instructions to follow. It did however allow me to be able to a partial stock state. My software version is still on the teamgenesis sense v2.9 cdma. Although I do like some of the features on this rom, I would still like to be able to get the OTA of ICS when it is released. Any suggestions?
Click to expand...
Click to collapse
To get the ota release (if it ever comes ) I do believe you will need to be locked and running the existing gingerbread rom. While I am not positive, I think the system uses the props file to determine if an update is applicable, and it will likely not recognize the teamgenesis rom version as being upgradeable.
Now I will likely get flames for saying this, but if you want to put the meanrom v2.4 of ICS on the phone, it can be done with s-on, you just need to follow the correct process. I ran that rom for a while, and it is very stock like, stable, and has a few enhancements that you will not find on a non-rooted stock rom. I never found anything wrong or not working with that rom.
To get it to load, first I downloaded flashimagegui from market, put the meanrom zip file on the sd card and made sure I had a recovery that I could get into. I am using TWRP v2.1.1, lots of folks talk about others like ext4, and I am only going to say use whichever you like, after all it is your phone.
Then with the phone unlocked via the htc method, I started the flashimage app, and browsed to the meanrom file. It extracted the kernel and flashed it. Once that was done, with clear cache buttons selected, rebooted to recovery, and used the install menu selection of TWRP to again flash the same rom file. Once it flashed the file, selected clear cache and dalvik just to be safe, selected reboot system, and it worked great.
Have a great weekend.
So, apparently I am still doing something wrong. I have put the pg86img on the root, relocked to the bootloader, and let it run it's course. However, it will get through with reading it and stops and does not finish anything with loading the system information. I have also tried to run the ruu via usb connection. I keep running into a c++ issue saying runtime error. I have wiped everything and thankfully I did make a backup of the rom and other information that I was runing so I can currently fall back on that.
I am on hboot 1.5, 2.17, and teamgenesis ICS rom for evo 3d.
Apparently there have been rumors that Sprint has finally released the ICS OTA, not that it really matters anymore, but I have run into a few interesting glitches, such as WIFI not staying connected while asleep or disconnecting.
If I have to I am willing to pay to do a netmeeing with someone in order to be able to fix this.
Sorry if it sounds like I am getting frustrated, but I have tried every walkthrough that I have found and have not had any luck with any of them.
Please help.
I forgot to say I am s-on
First, a big big thanks to Virus!! My phone info:
Sprint EVO3D CDMA
SHOOTER XC SHIP S-OFF RL
HBOOT-1.40.0000
RADIO-1.06.00.1216
eMMC-boot
Jun 8 2011, 17:20:22
TWRP v1.1.1
I previously flashed Freeza's v2.17.651.5 firmware and then the Stock ROM + root Shooter_S_Sprint_WWE_2.17.651.5_odex.zip which I'm currently running.
I've read this entire post OTA_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2-2.17.651.5 along with mpgrimm2's post Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 8-20-12 and just want to ask before I "leap"! My steps as far as I see it:
1. Run my backups (Titanium, etc) and create a TWRP nandroid.
2. Flash the Stock 2.89.651.2-2.17.651.5 firmware
3. Install the superwipe zip (presumably install zip via TWRP recovery?)
4. Flash the Stock Rooted 2.89.651.2-2.17.651.5 ROM
5. If necessary, flash the BT fix.
At this point I should be up and running the DEODEX'd version of the Stock ICS ROM as if I'd done the ICS OTA. Question here is whether I'll hit compatibility problems with any apps I have installed? I know hard to say w/o knowing what all I've got installed, but if problems I figure just uninstall the app and find something compatible... Any other problems I could expect or should look for?
If for some reason I wanted to go back to my current GB ROM nandroid before the ICS update, I can just reflash hboot 1.40 and restore the nandroid made in my step 1? Do I need to worry about reflashing any other 2.17 firmware? It sounds like I can just restore my nandroid on hboot 1.58 but thinking I'd rather be back at hboot 1.40.
I too have run into the "remote: not allowed" error when using fastboot to flash images. From mpgrimm2's post, it's looks to be because my radio is s-off while my stock hboot 1.40 is technically not s-off? To have a fully functional fastboot via pc, I'd need to flash JBear hboot 1.40 (for GB) or JBear hboot 1.58.5858 (for ICS) from Ramjet's Pick your bootloader!, right? Seeing that I'm ok with flashing by booting into recovery, is there any other advantages (or disadvantages) to using the JBear hboots?
Sorry for the long post, but wanted to be complete... All help is greatly appreciated!
It looks like you have it right. To clarify one point, you don't need to downgrade firmware to run GB (I don't think that's even possible). Just the hboot.
Read, Search, Read again, ... Then Ask with Tapatalk 2
coal686 said:
It looks like you have it right. To clarify one point, you don't need to downgrade firmware to run GB (I don't think that's even possible). Just the hboot.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
Thanks for the confirmation on my steps and being able to revert if I want to...I figured I would want to keep some of the updated firmware but wasn't sure what all could/should keep.
Although like the idea of being able to use fastboot fully, thinking best to just stick with the stock hboot for now...
Again thanks and if anyone has any other thoughts, they're always welcome!
I delayed doing the ICS update using the steps above, have read through the new pages/posts on the http://forum.xda-developers.com/showthread.php?t=1808150 post, and now have a few last questions before I jump in! Sorry if seem obvious, but have done the reading but now a bit confused or need clarification. I could just do it and recover if necessary, but rather ask up front.
If reading right, doing the Superwipe in step 2 will format both my phone and sdcard, cleaning out and recreating the partitions. Does this mean I'll have to use my TB Pro backups to restore all my personal apps & data? And if so, will I encounter any issues restoring such thing as my call log (or just restore the data and I'll be ok)? Reading up on Superwipe gets me thinking it deletes everything when I thought flashing this would be like an OTA update and keep my current apps, etc. Sorry again it's been awhile since flashing the stock 2.18.651.5 rooted ROM and just not remembering!
Also part way through the threads, there's mention of needing to first flash a ROM that will boot on 1.58 hboot or will get boot looping. I figure if my 2.18.651.5 GB rooted ROM won't boot after step 1, I'd just have to remove the firmware P86IMG file from the sdcard to proceed to step 2. The OP doesn't mention this - or is this a different situation than mine?
Lastly, on P.59, mpgrimm2 recommends flashing the full stock RUU to clean out all bits & pieces that might be left (I'm figuring it's the RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe) and reinstalling a custom recovery to have the stock rooted ICS. Is this a special case for one person or an alternative to the 3 step method? And it would mean I'd be reinstalling all apps and restoring all my data afterwards, right? Should I even consider this route if the three steps do an upgrade and keep my apps/data?
Thanks and sorry again for so many questions - just getting a headache keeping all straight and sorting through what's special case scenarios...oh and one last, is this Sense 3.5 or 3.6 - the OTA on HTC's site is listed as 3.6, right?
That's correct sir. It is 3.6