Related
I had my wife's EVO 3D working fine on VipeRom2.1 I think and when i tried to update it to 2.5 it went into a reboot loop. I cleared everything by formatting the system and clearing the cache and data and nothing. I tried a different rom, MeanRom and same thing. Right before it seems like it is going to get me to the unlock screen, reboot. I can get into the bootloader and the recovery just fine but no matter what i install, reboot, reboot, reboot.
Evo 3D
twrp 1.03
Recovery 2e
HBOOT 1.5
Any assistance would be greatly appreciated.
jschauf said:
I had my wife's EVO 3D working fine on VipeRom2.1 I think and when i tried to update it to 2.5 it went into a reboot loop. I cleared everything by formatting the system and clearing the cache and data and nothing. I tried a different rom, MeanRom and same thing. Right before it seems like it is going to get me to the unlock screen, reboot. I can get into the bootloader and the recovery just fine but no matter what i install, reboot, reboot, reboot.
Evo 3D
twrp 1.03
Recovery 2e
HBOOT 1.5
Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
What software is your phone on ? The 2.08 or 2.17?
jschauf said:
I had my wife's EVO 3D working fine on VipeRom2.1 I think and when i tried to update it to 2.5 it went into a reboot loop. I cleared everything by formatting the system and clearing the cache and data and nothing. I tried a different rom, MeanRom and same thing. Right before it seems like it is going to get me to the unlock screen, reboot. I can get into the bootloader and the recovery just fine but no matter what i install, reboot, reboot, reboot.
Evo 3D
twrp 1.03
Recovery 2e
HBOOT 1.5
Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Did you change/update your radios at all?
I am not sure of the software version. I tried going back to unrooted stock with RUU_Shooter_U_HTC_ARA_1.24.415.2_Radio_10.55.9020.00_10.13.9020.29_M_release_208706_signed and it gave me a version error.
I am running radio 0.97.10.0808 according to the relocked screen that I am getting while trying to restore to unlocked sprint stock.
And now I see the difference in radio and the version in the restore file.
Thanks for the assistance, my Epic Touch 4g has been so simple to tinker with, this thing is a pain in the rear.
The RUU you installed was for the GSM version of the phone, re-run the CDMA version. The GSM version is called Shooter_U whereas the sprint version is just called Shooter.
I'm guessing this would be a good place to start?
http://www.scottsroms.com/downloads.php?do=cat&id=4
I will try this one when I get home today. Hopefully I can get it back stock and then start over and get a functional custom ROM working.
The wife was not to happy I blew up her phone yesterday trying to update it, I am guessing she is not going to let me "fix" it again.
Yupp, install one of them, not sure which one will allow you to do the HTC unlock though.
I think I figured out what I did wrong in the first place. Someone please correct me if I am wrong. I forgot that 1.5 S-ON can't just install the ROM from the standard recovery method like I can with my Epic Touch 4G. I think I need follow the "How to Flash Any ROM or Kernel You Want" instructions from http://forum.xda-developers.com/showthread.php?t=1239821. I just booted to recovery and tried to install the ROM. Does this sound about right?
jschauf said:
I think I figured out what I did wrong in the first place. Someone please correct me if I am wrong. I forgot that 1.5 S-ON can't just install the ROM from the standard recovery method like I can with my Epic Touch 4G. I think I need follow the "How to Flash Any ROM or Kernel You Want" instructions from http://forum.xda-developers.com/showthread.php?t=1239821. I just booted to recovery and tried to install the ROM. Does this sound about right?
Click to expand...
Click to collapse
I didn't look at the link you posted. But with hboot 1.5 you can not write to the boot partition from recovery. In order to do this you need to extract the boot img from the ROM your gonna flash and fastboot flash boot boot.img then fastboot boot recovery.img will take you to recovery and flash ROM from there
Sent from my PG86100 using XDA App
mteezey said:
I didn't look at the link you posted. But with hboot 1.5 you can not write to the boot partition from recovery. In order to do this you need to extract the boot img from the ROM your gonna flash and fastboot flash boot boot.img then fastboot boot recovery.img will take you to recovery and flash ROM from there
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
You actually dont need to do both. If you just do a fastboot boot recovery.img it will give you complete access, including flashing the kernal. So after you type that command, it will load a the custom recovery and when you flash the rom, it will flash the kernel included with the rom as well. FYI you need to do a fastboot boot recovery.img each time you want to flash a kernel. If you arent changing kernals then you can just go into recovery as you normally would and flash a rom. If you want to flash a kernal without hooking up to a computer, then read into Flash Image GUI.
JayDaKissEP said:
You actually dont need to do both. If you just do a fastboot boot recovery.img it will give you complete access, including flashing the kernal. So after you type that command, it will load a the custom recovery and when you flash the rom, it will flash the kernel included with the rom as well. FYI you need to do a fastboot boot recovery.img each time you want to flash a kernel. If you arent changing kernals then you can just go into recovery as you normally would and flash a rom. If you want to flash a kernal without hooking up to a computer, then read into Flash Image GUI.
Click to expand...
Click to collapse
This is what I thought, The first one I tried was the newest version of ViperRom. I first tried to just flash over top of the existing rom with the hope I would not have to reset everything and make her start over with how she had it setup, I guess the newest version had a newer kernel. Hopefully I am able to get it back to a functional state this afternoon.
jschauf said:
This is what I thought, The first one I tried was the newest version of ViperRom. I first tried to just flash over top of the existing rom with the hope I would not have to reset everything and make her start over with how she had it setup, I guess the newest version had a newer kernel. Hopefully I am able to get it back to a functional state this afternoon.
Click to expand...
Click to collapse
I believe that does have the anthrax kernel havent downloadedthe new version. However i know some people have been having problems with roms that are based off the new OTA if their phones still have the old firmware. Definatly flash teh kernel/boot via fastboot recovery that should take care of the problem.
Correction not anthrax.
I got everything back working yesterday, I guess doing it correct the first time will save me some headache. I just need to remeber to start recovery from windows instead of from the bootloader screen. Thanks for the assistance.
Ok,
A little back story is that I very recently downgraded my Hboot from 1.50 to 1.40 using the new downgrad methods that have come out. Before that I used the HTC Dev unlock with S-on, and now I am S-off by way of the Revolutionary unlock method.
I have always used clockwork recovery for flashing since it was the only one that was compatible with phones that were on Hboot 1.50 when I first rooted. I have never had any issues flashing any roms previously, and I have done so many many times before.
I noticed a few days ago when trying to flash the newest version of Viper rom, which I have had on my phone before on 1.50, that it would not flash. It gave me an error saying that the file was bad, and it would abort. I re-downloaded the file thinking it was corrupted and kept getting the same results.
I went on and found yet another new rom that I was intersting in trying that was an AOSP rom. This time it would get the majority of the way through flashing the rom and then fail with a status 1 error message when it got to the step of writing permissions.
Unlike the error with Viper rom this left my phone in a state where it could only boot to recovery since the rom that was on the phone was only partially installed.
The only instances I have seen on here where others have had this issue is when people are trying to flash roms that aren't for their phone, or they have a gsm evo 3D trying to flash a cdma rom. This is not the case for me as I am certain that the roms I am trying to flash are for the cdma 3D, and I am also sure that I have the cdma version.
For some reason Mean Rom is the only rom that will allow me to flash successfully at this point, and even that fails sometimes with the status 1 error message if I try to install it immediately after another rom has failed even if I wipe data/cache before attempting it. I have to reboot the phone into recovery again in order to get it to work.
I am very frustrated at this point considering the only reason I downgraded my Hboot was to have more freedom to flash roms without the extra wear and tear of having to use the computer or HTC Dumblock to get past Fastboot and into recovery.
Anyone have any ideas on this one? Any suggestions are greatly appreciated.
I mean no insult by this question, but have you tried a Modified Superwipe before flashing the ROMs? I usually clear Dalvik/Cache, install Modified superwipe, then clear D/C, then install the ROM, then clear D/C one more time for good measure.
I've also heard the people have trouble with CWM not flashing ROMs properly on the Evo3d. I was using TWRP 2.0 and switched to 4ext (see my sig) and have not had trouble with either. Have you tried switching recoveries?
The old CWM 4.0 something works well for the CDMA when it comes to wipe and flashing..
TWRP 2.0 even the later newer one had funky issues after a few days of using no full wipes to roms flashing funky to themes and icons showin up missing.
Always do a full wipe ..
So... I flashed scrosler's Stock Rooted RUU 3.14, and once that was cleanly on and working I got into amonra and cleared data, flashed Venasaur 3.1, and then in Hboot ran the 3.14 kernel again.
How did I go wrong and what's the simple fix that will get me with the pokemon? ~thanks <3
(I'm getting bootlooped that is)
You flashed an incompatible kernel. Are you s-on or s-off? If s-off just flash the Rom again in amon ra and reboot phone. No need to install a kernel it will do it for you. If s-on you need the kernel for venasaur Rom which may need to be flashed in fastboot unless someone has made it into a flammable zip. If s-on might as well take the plunge and s-off. It's a very easy process.
sent from my Clean Rezound
I am S-on, as soon as I find something condutable and more reliable than a paperclip i'll probably do S-off haha
I don't think anyway has, I just time getting the image boot file off of the rom and running it in H-boot, I still get a bootloop (I'm genuinely surprised that it didn't work), that's a pretty sticky situation, i'm stuck without a phone until that's solved =(
I repeal that statement, taking the boot.img out and flashing it in hboot worked, wonderful! thanks =)
Question for you?..
Now that that you have your Venusaur 3.1 running..are you having any issues with Wifi?
I did the re-lock, android police ruu, unlock, install recovery, clean wipe x10, install venusaur 3.1, and then installed sense4 boot image for the venusaur rom. However I keep getting Wi-fi Errors, I'm guessing my wifi modules are wrong but I'm just trying to figure out where I may have messed up. I tried flashing the wifi modules provided by http://forum.xda-developers.com/showthread.php?t=1642217 but no go...any ideas?
well i'm fairly curious how you were able to get the sense4 boot image, it gave me a mainver error, I took the boot image out of the rom and ran that.
Which got me in, and wifi isn't giving me a problem surprisingly, but I'm now curious to how your supposed to go 3g with the new setting setup.
My Sd card also can't mount I'm not sure if that's related to 3.14 and pokemon rom or just my terrible flashing
Watercycle, are you still having problems? If you flashed Scott's Rom that is not an ruu. I believe you are still o n the old firmware. You will need to go to nilsp business Rom in the development section and download the old firmware patch (i think it's in the 4th post) then flash in amon ra. You should be set after that.
sent from my Clean Rezound
actually I flashed scott's 3.14 deodex and old firmware patch + boot img before flashing the pokemon and pokemon boot img
I'm currently only struggling with the issue of sd card mount now
Watercycle said:
actually I flashed scott's 3.14 deodex and old firmware patch + boot img before flashing the pokemon and pokemon boot img
I'm currently only struggling with the issue of sd card mount now
Click to expand...
Click to collapse
The patch may still be on your sd card from Scott then and if not go to the thread I suggested. Just boot to recovery and flash the patch again. You will need that patch for any ics Rom you run because you are still on gb firmware. Don't panic your almost there.
sent from my Clean Rezound
how can you tell if your on old gb firmware? =( since it still boots up and works
darnit I thought i was on ics after that full ruu =o
so after having flashed the pokemon in Hboot i flash the old firmware again? (i'm scared it will bootloop me because i finally got it working haha)
ZombieCodeMonkey said:
Question for you?..
Now that that you have your Venusaur 3.1 running..are you having any issues with Wifi?
I did the re-lock, android police ruu, unlock, install recovery, clean wipe x10, install venusaur 3.1, and then installed sense4 boot image for the venusaur rom. However I keep getting Wi-fi Errors, I'm guessing my wifi modules are wrong but I'm just trying to figure out where I may have messed up. I tried flashing the wifi modules provided by http://forum.xda-developers.com/showthread.php?t=1642217 but no go...any ideas?
Click to expand...
Click to collapse
I briefly searched the venasaur thread (which you can do to) and found most people having WiFi issues either had the wrong kernel or just reset their router and bam, WiFi works. I can't help you anymore then that so you may want to ask in that thread.
Edit: did you unzip the Rom and get the boot.IMG there or did you download seperate? If you didn't unzip and take it out of the Rom then try that. You should be good.
sent from my Clean Rezound
What ruu did you use?
sent from my Clean Rezound
Give me like 20 minutes to get back to you...heading home....motorcycle can't multitask at night more obvious to others haha
Sent from my ADR6425LVW using Tapatalk 2
snow, since I sucsessfully was on
This
will flashing the old gingerbread fix my sd mounting or break everything?
sorry I have to be more direct, gotta get some sleep now =)
Watercycle said:
snow, since I sucsessfully was on
This
will flashing the old gingerbread fix my sd mounting or break everything?
sorry I have to be more direct, gotta get some sleep now =)
Click to expand...
Click to collapse
I think so
Watercycle said:
snow, since I sucsessfully was on
This
will flashing the old gingerbread fix my sd mounting or break everything?
sorry I have to be more direct, gotta get some sleep now =)
Click to expand...
Click to collapse
It will fix your sd card. You never ran the ruu if all you flashed was Scott's rooted, deodexd Rom. If you get with me tomorrow I can walk you through the ruu but I think at that point you might as well s-off. Time to find that wire
sent from my Clean Rezound
If you could see your sd card on Scott's Rom it was because of the patch. Make sure you report back. I need some sleep.
sent from my Clean Rezound
Okay...
I re-locked my bootloader using the usual, fastboot oem lock.
then I download the full leaked RUU from Android Police, androidpolice.com/2012/05/07/exclusive-download-htc-rezound-ice-cream-sandwich-build-3-14-605-5-brings-a-handful-of-fixes-and-newer-radios/"
Booted to Hboot with that file on the SD card in the proper name, completely flashed the phone with the Leaked RUU
Once OS loaded, rebooted back to fastboot and used hTcdev.com to unlocked my bootloader again. (I do not have S-Off yet).
Then I downloaded and flashed through fastboot commands the TWRP 2.1.1. Touchscreen recovery.
Once this was done, I downloaded and installed Venusaur 3.1.0 through recovery after performing scot's superwipe x10,
Then fastboot flashed the boot.img for the sense 4.0 roms.
Wi-Fi does not turn on at all...It will state Turning on...but not to long after will give error.
So after all of that I tried grabbing the wifi module.zip from one of the stock rom de-odexed rooted 3.14.605.5 roms, and tried flashing that through recovery and manually adding the file through root explorer..nothing.
Hope that helps clarify.
Also i would through an inquiry to there thread but I don't have enought posts yet to post in development.
ZombieCodeMonkey said:
Okay...
I re-locked my bootloader using the usual, fastboot oem lock.
then I download the full leaked RUU from Android Police, androidpolice.com/2012/05/07/exclusive-download-htc-rezound-ice-cream-sandwich-build-3-14-605-5-brings-a-handful-of-fixes-and-newer-radios/"
Booted to Hboot with that file on the SD card in the proper name, completely flashed the phone with the Leaked RUU
Once OS loaded, rebooted back to fastboot and used hTcdev.com to unlocked my bootloader again. (I do not have S-Off yet).
Then I downloaded and flashed through fastboot commands the TWRP 2.1.1. Touchscreen recovery.
Once this was done, I downloaded and installed Venusaur 3.1.0 through recovery after performing scot's superwipe x10,
Then fastboot flashed the boot.img for the sense 4.0 roms.
Wi-Fi does not turn on at all...It will state Turning on...but not to long after will give error.
So after all of that I tried grabbing the wifi module.zip from one of the stock rom de-odexed rooted 3.14.605.5 roms, and tried flashing that through recovery and manually adding the file through root explorer..nothing.
Hope that helps clarify.
Also i would through an inquiry to there thread but I don't have enought posts yet to post in development.
Click to expand...
Click to collapse
Why are you not s-off? Makes life much easier. What I have concluded is that you need to start over. You have the wrong kernel. Wipe everything then flash the Rom in recovery. You will have had to unzip the Rom on your pc then take the boot.IMG out and flash this in fastboot to the phone. I don't think there is a ph.zip file for this. There are very good directions if you search that thread.
sent from my Clean Rezound
Sorry guys but it's bed time. If you both follow those directions you should be fine. If not get with me in the morning.
sent from my Clean Rezound
Hello all,
I am brand new to the android community, and have come accross a problem that I can't seem to get fixed. I previously rooted/rom'd my EVO lte with mean rom a while back. I started to have wireless issues so I decided to spend some time learning/fixing the problems that I'm sure my noobness created.
I relocked my phone and unrooted it back to factory 2.13.651.1. After doing that I updated my phone via Sprints OTA updater. I recieved an update that took me to 3.16.561.3. After that was completed I preceeded to unlock my bootloader again and installed TWRP 2.4.1.0. When I try to install any ROM it appears to go well in TWRP, but it reboots right after it says "updating kernel, this may take a while". When it reboots it sits at the HTC white startup screen, it doesnt even flash the red developer letters under the HTC logo like it normally does when continuing to boot into recovery or the old ROM.
I did some search and have found that others had issues with TWRP 2.4.1.0 (http://forum.xda-developers.com/showthread.php?t=2048229&page=573). They rolled back to 2.4.0.0. The problem is that with the OTA update the touch sence in TWRP is broken unless you run 2.4.1.0.
Anyone else run across ths issue?
The solution is probably staring me in the face but my noob aura is blocking it. :silly:
TWRP 2.4.1.0 broke something with flashing so you might have to relock and ruu to get back to normal. The problem is there is no ruu out for 3.16 and running the ruu for 3.15 may mess up your phone. I would try to flash the kernel separately by flashing with fastboot or flashgui and see if that allows it to boot into the rom. You may be able to run dirty racun and gain s-off since the hboot didn't change with the latest update.
Waterheeter said:
Hello all,
I am brand new to the android community, and have come accross a problem that I can't seem to get fixed. I previously rooted/rom'd my EVO lte with mean rom a while back. I started to have wireless issues so I decided to spend some time learning/fixing the problems that I'm sure my noobness created.
I relocked my phone and unrooted it back to factory 2.13.651.1. After doing that I updated my phone via Sprints OTA updater. I recieved an update that took me to 3.16.561.3. After that was completed I preceeded to unlock my bootloader again and installed TWRP 2.4.1.0. When I try to install any ROM it appears to go well in TWRP, but it reboots right after it says "updating kernel, this may take a while". When it reboots it sits at the HTC white startup screen, it doesnt even flash the red developer letters under the HTC logo like it normally does when continuing to boot into recovery or the old ROM.
I did some search and have found that others had issues with TWRP 2.4.1.0 (http://forum.xda-developers.com/showthread.php?t=2048229&page=573). They rolled back to 2.4.0.0. The problem is that with the OTA update the touch sence in TWRP is broken unless you run 2.4.1.0.
Anyone else run across ths issue?
The solution is probably staring me in the face but my noob aura is blocking it. :silly:
Click to expand...
Click to collapse
So u was on 3.16 and unlocked it? Did u use dirty racun? Did it work? Sorry I accepted ota and want s-off rooted if possible.
Sent from my EVO using xda app-developers app
polar2792 said:
So u was on 3.16 and unlocked it? Did u use dirty racun? Did it work? Sorry I accepted ota and want s-off rooted if possible.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I didnt use dirty racun to unlock, I used the fastboot method. I'm not developed enough in my knowledge to be s-off atm.
cruise350 said:
TWRP 2.4.1.0 broke something with flashing so you might have to relock and ruu to get back to normal. The problem is there is no ruu out for 3.16 and running the ruu for 3.15 may mess up your phone. I would try to flash the kernel separately by flashing with fastboot or flashgui and see if that allows it to boot into the rom. You may be able to run dirty racun and gain s-off since the hboot didn't change with the latest update.
Click to expand...
Click to collapse
On your notes I did some searching to learn what you were saying. First I tried to use the fastboot update 'meanbean-rom.zip' file but it produced errors:
archive does not contain 'android-info.txt
archive does not contain 'android-product.txt
error: update package has no android-info.txt or android-product.txt
I tried fastboot flash boot boot.img after extracting the boot.img from the .zip. After rebooting the phone stays on the white HTC logo screen but now populates the red dev notice. Looks like I'm going in the right direction
Thanks for your help so far.
I believe I have it figured out. I searched for an unofficial version of CWM recovery (all the XDA links for the evo lte have been removed for now due to bugs). I'll deal with those bugs as I was stuck without a phone until I got it figured out
Installed CWM 5.8.3.5 and flashed Meanbean Rom. Problem fixed
I'll put TWRP back on when they release a patch.
*Edit* spoke too soon. The touch interface doesnt work with meanbean due to the driver update (I'm guessing). Atlease I can see any missed calls now. lol
*Edit* Thanks to the D3rps I was able to get my phone up and going again. They had posted the stock 3.16 rom here: http://forum.xda-developers.com/showthread.php?t=2127947, with *Removed* recovery I was able to flash that rom. Now I just have to keep an eye out for the Meanbean update that will make it work with 3.16 touch.
**Edit** I removed the reference to the recovery I was using due to problems my noob self was not aware of. Thanks to Bigdaddy619 for his guidance, I now realize why no one is using it on the evo lte.
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
simonsgray said:
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
Click to expand...
Click to collapse
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Thanks man. sig is a little out of date, i havent' needed xda as much since jumping to nexus. TWRP and i didn't do the s-off stuff. it says it needs a stock rom and i just havea spinning cyanogen mod. i will try install the 4ext and see if that changes the results.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
simonsgray said:
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
Click to expand...
Click to collapse
If you want to flash back to the stock ICS image you need to first relock your bootloader. When you relock it will say relocked when in hboot. The procedure is to place the image in the root of your external SD card and select from hboot. It should recognize and flash back to stock, however everything other than your external SD gets wiped in the process. So you need to make sure you have a good recent backup. Also, you remember when you first HTC dev unlocked they sent you an image to push to unlock? Well, I hope you saved it, because you'll need it again to re-unlock the bootloader after flashing the firmware image, but before attaining s-off.
However, if you were already on your carrier's latest ICS firmware before you started flashing different ROMs, you probably already have their latest radio. If you install the latest 4ext and enable smart flash, you'll probably succeed in installing any of the source built ROMs (ASOP, CM, PACman, evervolv) without s-off, because ROMs built from the source don't have the CID flag in their binaries.
If you still decide to go back and attain s-off the procedure is as follows: 1) relock your bootloader 2) flash the latest stock firmware for the carrier that sold your device. 3) Unlock your bootloader again using the image and commands you previously did to HTC dev unlock the first time, 4) get s-off using the wire-trick 5) flash the hacked hboot (and another radio if you desire, but not required for most ROMs) 6) super CID to remove all carrier locked file / partition limitations and protections 7) Flash your preferred recovery. Because you're now s-off you can use TWRP, CWM, or 4ext since the protected partitions are no longer an issue. 8) Flash any ROM you want provided it's based on ICS or later (below won't work because the radio is incompatible).
Edit: One other thing to note before starting any of this make sure your battery is fully charged. Also, the first time you boot after installing CM or any ASOP based ROM it can take quite some time to go through the process before you get to the login screen. For me it usually takes a little under 10 mins. It may at first appear to be a little sluggish until the rom settles, usually about 10-15 mins.
I hope this helps