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
Related
Hey all,
I'm currently running Innefabilis Deus Alpha Preview and I like it, but will wait for another update that's more stable. Anyway, I tried reverting back to Ineffabilis v1.0 (GB) but when I installed a Kernel by dsb, it says something about "Main version is older!" in fastboot. I read that if you've already flashed the latest leak (ICS), it's not easy to revert back to GB.
I'm wondering if I'm able to use CleanTool to flash dsb's Kernel instead after flashing a GB Rom. Can anyone help me? I've already tried flashing other Kernels via fastboot on my phone and have failed.
This is a common problem right now and you can do a few things...fastest and easiest way is you can flash boot.img via fastboot for short term fix. Just pull the boot.img from the ROM you are flashing. This will get you up and running...but you will run into this again.
For a long term solution...I just came across this...which should help you...
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.
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
Click to expand...
Click to collapse
get the PH98IMG from his post here...
http://forum.xda-developers.com/showpost.php?p=21442702&postcount=3
this works well. Myself I just cleaned everything up installed my GB rom, let it fail then pulled the battery and used the trusty droid to mount the sd card from the rezound and put this file on it. booted in to recovery let it do its thing and it worked perfect.
However I'm not sure if pulling the battery after the the file fails is safe, just a risk I took.
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.
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?
ive read every thread and nothing seems to work...
ive done the internal and sd memory fixes but im still having a major issue, i was running clean rom de1.2 perfectly before i went and started the s-off procedure...now once i achieved s-off and i went to upgrade my rom to cleanrom de 1.3 i was getting the memory errors and reboots...went through the steps to fix the memory as i mentioned earlier and im still getting reboots when i receive txts or emails...normally id think this were a rom issue but ive tried some different roms...i thought i had the issues taken care of but now when i go to play some music it reboots plus im still getting reboots with sms and gmail...i froze gmail and have bought enough time to charge my phone to a decent ammount (have been working on this all morning), everything is current and have tried everything from wiping several times and re-installing the roms several times, all the fastboot and adb commands from the storage issues...flashed different kernels and even recoveries...i cant even stream music from my laptop and play it on the phone with out there being a reboot...i can send sms fine, it just appears to be receiving them is the issue...dont know if this is one problem or several...what information of my phone would you guys need to diagnose a problem...
im on:
Cleanrom DE 1.3 w/ 3.0.13 kernel
baseband v. 1.22.10.0310r 1.22.10.0308r
build 3.13.605.7 cl363816 release keys
hboot 2.21.2121
not sure what else to try...is there a method to getting back to bone stock so i can retry this whole thing again...im talking relocking the device and redoing all the htcdev crap/root/s-off/rom again
thank you very much in advance for any help
Sounds like youre on old firmware. Flash the old firmware patch. If it doesn't help Flash the ruu. If you're s-off no need to relock at all. You'll need to have a Ph file for recovery unless you want to unlock
Sent from my ADR6425LVW using Tapatalk 2
ive flashed those several times...is there difference between them? the ones i flashed were from the clean rom folder after installing the rom
Best thing to do is run a ruu then it wipes your phone clean.
Sent from my ADR6425LVW using Tapatalk 2
rezin said:
ive flashed those several times...is there difference between them? the ones i flashed were from the clean rom folder after installing the rom
Click to expand...
Click to collapse
I had the sd issues after s-off and I never did the editing to fix the issues all I did to fix them was reflash amon ra then reflashed my backup of cleanrom and reflashed the kernel and rebooted then let it startup and then pulled battery and then restarted the phone and everything was back to normal sd card issue fixed. Try that it might work. Oh and I took the jhboot when it asked when it asked if I wanted to install it.
Sent from my ICS Rezound
ok the old firmware patch seems to have worked...i really hope so cuz ive just about exhausted my AD&B keys...
ok so now that that has been taken care of, will it be smooth sailing from here on out? thanks for everything, especially the devs and hackers that made my headache even possible...
came from a droid x and that couldve been a hell of a device, wish there were an s-off equivalent to its ridiculous bootloader...but yeah loving the rezound dont even wanna return it even its mangled battery terminal...
ok spoke too soon...the sms reboots are gone...i can make calls but now the memory is back to being a problem...both internal and sd are showing as non existent...so do i now run those memory fixes again? or just wipe and install the rom completely from scratch again?
rezin said:
ok spoke too soon...the sms reboots are gone...i can make calls but now the memory is back to being a problem...both internal and sd are showing as non existent...so do i now run those memory fixes again? or just wipe and install the rom completely from scratch again?
Click to expand...
Click to collapse
youre prolly on an incompatible hboot(cant mix GB and ICS)
heres what id do:
-run the 3.13.605.07 RUU
-clear storage in hboot
-install the ics jpbear hboot,if desired
-install recovery
-fresh start cleanrom 1.3
i just did the above to go from 3.11/1.2 to 3.13/1.3 and i have absolutely no issues. its smooth,fluid,sd card is there,never rebooted.
im not supposed to relock for this am i? do i just flash in recovery like 605.1 ruu?
rezin said:
im not supposed to relock for this am i? do i just flash in recovery like 605.1 ruu?
Click to expand...
Click to collapse
If you're s-off no need to relock
Sent from my ADR6425LVW using Tapatalk 2
ok flashed ruu and ran the kernel...now im getting the reboots again...wth
rezin said:
ok flashed ruu and ran the kernel...now im getting the reboots again...wth
Click to expand...
Click to collapse
what did you do (in detail)?
installed ph98img.zip
wiped data cache dalvik
installed ruu twice before leaving recovery
rebooted...
reinstalled amon ra
everything seemed fine but now im back to not having any accessible memory on phone
im about to re-do the memory fixes and upgrade the hboot
if that doesnt work then i dunno
rezin said:
installed ph98img.zip
wiped data cache dalvik
installed ruu twice before leaving recovery
rebooted...
reinstalled amon ra
everything seemed fine but now im back to not having any accessible memory on phone
im about to re-do the memory fixes and upgrade the hboot
if that doesnt work then i dunno
Click to expand...
Click to collapse
ive got no clue what youre talking about. ruus are flashed i hboot,not recovery. what ph98img did you install?
again,heres what id do:
-run the 3.13.605.07 RUU (not flash a rom)
-clear storage in hboot
-install the ics jpbear hboot,if desired
-install recovery
-fresh start cleanrom 1.3 (wipe cache,dalvic,data/factory reset,system,boot) do not install old firmware patch.
follow those directions exactly,and you wont have prollems. if you dont know what something means,ask.
http://forum.xda-developers.com/showthread.php?t=1631830
thats not an ruu? i also followed the directions from team bamf website...
i just flashed rezrom s4 1.2...lets see how that goes
rezin said:
http://forum.xda-developers.com/showthread.php?t=1631830
thats not an ruu? i also followed the directions from team bamf website...
i just flashed rezrom s4 1.2...lets see how that goes
Click to expand...
Click to collapse
That's a Rom. A ruu installs everything. Radios, boot and everything else.
Sent from my ADR6425LVW using Tapatalk 2
despite many here misusing the term ruu, a ruu is an executable file run on a PC which does quite a bit more than a rom flash. Run one of the Ruu, out wit until Verizon releases a real ruu for ics, which hopefully will be Wednesday.
Sent from my ADR6425LVW using xda premium
jdmba said:
despite many here misusing the term ruu, a ruu is an executable file run on a PC which does quite a bit more than a rom flash. Run one of the Ruu, out wit until Verizon releases a real ruu for ics, which hopefully will be Wednesday.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Despite however exceedingly helpful once again pointing out how many people "misuse" the term RUU may be.. This did not help him solve his problem in the slightest.
OP:
In the above instructions where he says "Run RUU":
-You will need to download the full ICS leak from android police or I believe there's a link here: http://forum.xda-developers.com/showthread.php?t=1631630
--There are instructions on that site on how to install the RUU.
Then follow the previous poster's instructions about installing a new hboot (if you want to, it is not required)
**EDIT: You do not NEED to do this, please only do it if you know what you're doing. I have had absolutely no reason to replace my hboot and I haven't had any issues.**
Then you will need to reinstall a custom recovery.
Then you can proceed with your wiping/flashing. I remember a previous poster saying to do a factory reset after updating to the new RUU. Not sure if it's required, but I did it and I'm not having any issues.
Hope this helps!
yeah thanks again and i found that original RUU im installing now...i wouldve updated my status earlier but the download took an hour or so...everything seems fine at the moment...its currently updating /system, but i did notice it relocked my device, and i still have s-off though...so my question is, do i need to worry about being locked if ive still got s-off?
UPDATE:
ive got a fully functioning phone now...thanks everyone for the assistance and patience...this has been the most critical mod ive done to any phone...dont know where it screwed up along the way but im gonna enjoy this for a while before i tamper with it again
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