Related
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.
So i think i am getting lost and I really want to be careful before i re-start my crack flashing habits again.
I flashed senseless ics, loved it, but wanted to go back to gb. So i went back to senseless 1.1, extracted boot.img, and adb pushed and flashed then did a nandroid back up and every thing is A-ok .
Here is my confusion.
What problems are ppl refering to with Mainver? ( what is that even )
Why do ppl have to RUU ( again what is it)
is my method right ? Which is : if the rom came with an auto script to flash from hboot then hurray, if not, then flash boot.img from adb via fast boot and flash to my liking ?
the only roms i gave been on so far : cleanrom 1.5.5, inefebellis, senesless 1.1, senseless ecs, then back to senseless 1.1 via nandroid like mentioned.
jmichaels1982 said:
So i think i am getting lost and I really want to be careful before i re-start my crack flashing habits again.
I flashed senseless ics, loved it, but wanted to go back to gb. So i went back to senseless 1.1, extracted boot.img, and adb pushed and flashed then did a nandroid back up and every thing is A-ok .
Here is my confusion.
What problems are ppl refering to with Mainver? ( what is that even )
Why do ppl have to RUU ( again what is it)
is my method right ? Which is : if the rom came with an auto script to flash from hboot then hurray, if not, then flash boot.img from adb via fast boot and flash to my liking ?
the only roms i gave been on so far : cleanrom 1.5.5, inefebellis, senesless 1.1, senseless ecs, then back to senseless 1.1 via nandroid like mentioned.
Click to expand...
Click to collapse
ruu is flashing stock. method is right with the boot.img which is also the kernel but without other kernel files found in the flashable zip. If the rom doesnt have the boot.img u can also use cleanflash tool to flash the kernel/boot into your current rom,restart,then wipe/flash rom
sent from my rezound using tapatalk
RUU files are the official software releases from HTC.
RUU files are signed. (They give proper "official" codes to hboot to get past the s=on security)
This means that they can flash all parts of the device, even the bootloader and radio firmware, which we can not normally flash because it is write locked. (do to s=on we can't flash them even with root)
Sometimes people have issues and need to get the phone back to pure stock so they use the RUU.
Mainver is data on the software version number of the kernel (I believe... it may be for some other part, either way it is version info)
Think V1... V1.2... V1.5... V1.5.5
Because of s=on we are not allowed to "downgrade/revert" to older software versions.
The leaked ICS build has a newer Mainver, some people flashed the leak unmodified, and that changed the Mainver info. Now they need to use a special trick to trick the s=on security to allow flashing of older kernels. The ICS ROMs we have now, have been modified so they do not change the Mainver. This makes it easier to go back to GB or switch to other ROMs.
Marine6680 said:
RUU files are the official software releases from HTC.
RUU files are signed. (They give proper "official" codes to hboot to get past the s=on security)
This means that they can flash all parts of the device, even the bootloader and radio firmware, which we can not normally flash because it is write locked. (do to s=on we can't flash them even with root)
Sometimes people have issues and need to get the phone back to pure stock so they use the RUU.
Mainver is data on the software version number of the kernel (I believe... it may be for some other part, either way it is version info)
Think V1... V1.2... V1.5... V1.5.5
Because of s=on we are not allowed to "downgrade/revert" to older software versions.
The leaked ICS build has a newer Mainver, some people flashed the leak unmodified, and that changed the Mainver info. Now they need to use a special trick to trick the s=on security to allow flashing of older kernels. The ICS ROMs we have now, have been modified so they do not change the Mainver. This makes it easier to go back to GB or switch to other ROMs.
Click to expand...
Click to collapse
Good write up !
waw
Thank you Thank you Thank you ! best crash course ever ...
Im currently trying to go back to the stock RUU from Scotts Cleanrom 4.0 however im having issue after issue.
My first issue is In this current version of cleanrom i can not access phone storage / sd storage to transfer the RUU to my phone.
The .exe verion of the RUU keeps failing and saying "unknown error, which im guessing is because my bootloader is unlocked. If I lock my bootloader, it doesnt allow my phone to boot into cleanrom, it just keeps saying under relocked "Security Warning".
Im literally lost, as scotts cleanrom 4.0 keeps rebooting and is unusable for me, and I can not use amen ra to flash a new rom because i can not copy a new rom to my phone/sd card. Furthermore, there are no nandroid backups for me to access.
My current state is this: i am "Relocked" But under it im getting "Security Warning"
I have the RUU on the SD Card but when i go into hboot, the loading bar on the top right completes then nothing happens...
You can mount your sdcard within amonRA. It's the "USB-MS toggle" and mount sdcard option.
You can also use a usb sdcard reader and pop in your sdcard.
The "USB-MS toggle" worked for me in the past.
Droidel said:
You can mount your sdcard within amonRA. It's the "USB-MS toggle" and mount sdcard option.
You can also use a usb sdcard reader and pop in your sdcard.
The "USB-MS toggle" worked for me in the past.
Click to expand...
Click to collapse
Ran to walmart to grab an adapter and i was able to get a different rom on my sd card using a reader. Currently waiting for it to boot up Ineffabilis v1.3, we'll see if this can clear up my issues since putting the RUU PH98IMG on the sd card and jumping into the bootloader didnt seem to install. Its taking its sweet time though :-/
Having bad luck with my Rezound so far, partially because i was rushing but partially because it seems like it just doesnt WANT to work, lol
Edit:
Wouldnt boot into that rom... going to try scott's stock rooted rom... if that doesnt work im gonna be back at step one
Ok so the short of it is, you can't run an older RUU. The hboot was updated with the leaked RUU, so any older RUU will fail. That is the bad news.
The good news is that you can still go back to stock, somewhat. Grab a stock rom from www.scottsroms.com, and install that.
What you need to do first is reunlock your phone.
Code:
fastboot flash unlocktoken Unlock_code.bin
This is if you still have your unlock token from htcdev.com. If not you need to rerun the process.
Secondly, reflash Amon Ra for recovery.
Code:
fastboot flash recovery nameofrecoveryfile.img
Flash the stock rom from Scott's site.
Lastly flash this zip in recovery, and you should be good to go.
EmerikL said:
Ok so the short of it is, you can't run an older RUU. The hboot was updated with the leaked RUU, so any older RUU will fail. That is the bad news.
The good news is that you can still go back to stock, somewhat. Grab a stock rom from www.scottsroms.com, and install that.
What you need to do first is reunlock your phone.
Code:
fastboot flash unlocktoken Unlock_code.bin
This is if you still have your unlock token from htcdev.com. If not you need to rerun the process.
Secondly, reflash Amon Ra for recovery.
Code:
fastboot flash recovery nameofrecoveryfile.img
Flash the stock rom from Scott's site.
Lastly flash this zip in recovery, and you should be good to go.
Click to expand...
Click to collapse
Second time you helped me out of a hole today, you ARE the man. Thank you so much
And in fact, I would much rather be on one of Scott's stable stock like roms with that vzw bloat removed.
Edit:
Got scotts stock rom working nicely except i still cant access my sd card or internal storage. i flashed The Zip you linked and it still is not working. Any ideas?
question:
once somebody is rooted and flashed with a ROM from xda, is there anyway to go back to the original stock (not Scott's) so the Rezound can get the official OTA update to ICS on its own?
cpham817 said:
question:
once somebody is rooted and flashed with a ROM from xda, is there anyway to go back to the original stock (not Scott's) so the Rezound can get the official OTA update to ICS on its own?
Click to expand...
Click to collapse
Depends on the rom, if you updated to one of the newer ICS roms that require updating the firmware, no. The current roms will be updated with the goods from the latest OTA once it's available though so you just install the latest version of the rom of your choice.
Now if there's any more radio/hboot/baseband type updates, we'd have to manually go through the process of installing the latest RUU to update those also.
i haven't updated the firmware yet, i was actually thinking of doing so tonight. I'm not trying to unroot, i would rather just get the ota update. the rom I've been using has started being buggy and there doesn't seem to be a fix (random restarting several times a day, lost connection issues, etc). what would i have to do?
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
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