So I s-offed my wifes evo 3d a little bit ago, Afterwards I put the 1.04 hboot and CM 10.1 on her sd and flash them, Of course wiping in recovery because of the hboot flash, And it bootloops, So i'm like wtf, And I re-wipe, and re-flash. Still a bootloop, So I throw the sd in the pc and realize it corrupted so I format it, And throw back on the 1.04 bootloader and reflashed the rom, Still a bootloop,
So I run the ruu, It goes through, And boots back up so I'm like, Okay, Got it all taken care of.
So I flash the 1.04 bootloader once again and as i'm rebooting for the first time, bootloop. So, This is now seeming like a problem to me, Anyhelp? Ramjet maybe?
This is the same copy same download as the 1.04 bootloader that's running on my phone with CM 10.1 doing just fine.
Can't_Live_Without_My_Evo said:
So I flash the 1.04 bootloader once again and as i'm rebooting for the first time, bootloop. So, This is now seeming like a problem to me, Anyhelp? Ramjet maybe?
This is the same copy same download as the 1.04 bootloader that's running on my phone with CM 10.1 doing just fine.
Click to expand...
Click to collapse
Try the JBear 1.50.5050 hboot.
ramjet73
ramjet73 said:
Try the JBear 1.50.5050 hboot.
ramjet73
Click to expand...
Click to collapse
I'm currently running the RUU again trying to get it to at least boot stabily a time or two.
It's so weird seeing the stock boot animation boot loop lol.
Got it to boot, I feel a little better lol.
Is there a chance somethings seriously wrong? I tried 1.40 and 1.04 and both bootlooped.
ramjet73 said:
Try the JBear 1.50.5050 hboot.
ramjet73
Click to expand...
Click to collapse
Isn't that one GB?
Edit: After a ruu and a run through set up, I unchecked fastboot and checked usb debugging and then flashed the 1.50.5050 and it also bootloops.
What. The. Hell.
The only thing that'll boot up is stock.
Edit 2: So after the RUU I flash the 1.50.5050 you suggested, Bootloop as above stated, So I take out the sd and put the 1.58 stock hboot on it and flash that and it boots back up just fine. Which makes sense, But doesn't... ya know.
Edit 3: So I went to go unlock the bootloader on 1.58 and I'm on the "Unlock Bootloader?" screen, But I can't select yes, I know the dang power button works, I've pressed it 20 times, held it, it wont recognize, I also tried the camera button, don't work
I just tried to select no, and guess what, it'll work for that
Anyone ever seen this?
I unlocked it successfully like, 2 hours ago, with no effort at all. What. The. Hell.
Edit 4: Alright even though it wouldn't go through and reboot when hitting yes, and I even hit no to reboot it, I pulled the battery and went into the bootloader and it's unlocked.
So I wrote a recovery, I'm gonna make a back up of the stock rooted rom and see what we can't figure out here.
Okay, So it'll boot a custom rom on the 1.58 hboot. And I've made a backup of the stock rooted rom, I'm gonna try and flash the 1.04 again, and if it bootloops i'm gonna try and restore the backup of the stock rooted rom from the 1.58 hboot (Will that be a problem)
OKAY! Flashed the 1.04 hboot over Common-Sense (Thanks Turtle) and it finally booted up, Time to flash some jb goodness and hope we've got success.
Can't_Live_Without_My_Evo said:
Isn't that one GB?
Edit: After a ruu and a run through set up, I unchecked fastboot and checked usb debugging and then flashed the 1.50.5050 and it also bootloops.
What. The. Hell.
The only thing that'll boot up is stock.
Edit 2: So after the RUU I flash the 1.50.5050 you suggested, Bootloop as above stated, So I take out the sd and put the 1.58 stock hboot on it and flash that and it boots back up just fine. Which makes sense, But doesn't... ya know.
Click to expand...
Click to collapse
Sorry, I didn't realize that you were still on the stock ROM. As you found out, the only hboots that will boot that is 1.58 and JBear 1.58.5858.
The JBear 1.50.5050 hboot is a customized version of the latest Sprint GB bootloader and should boot everything that the engineering (ENG) 1.04 hboot does. I prefer to use that over the ENG version for day-to-day stuff since it's partition configuration is closer to the stock 1.58 hboot.
ramjet73
ramjet73 said:
Sorry, I didn't realize that you were still on the stock ROM. As you found out, the only hboots that will boot that is 1.58 and JBear 1.58.5858.
The JBear 1.50.5050 hboot is a customized version of the latest Sprint GB bootloader and should boot everything that the engineering (ENG) 1.04 hboot does. I prefer to use that over the ENG version for day-to-day stuff since it's partition configuration is closer to the stock 1.58 hboot.
ramjet73
Click to expand...
Click to collapse
I've got it working now, But I still don't understand the problem.
Everything worked fine except changing hboots.
The first time I flashed the hboot and then the rom without booting into anything and it boot looped, And I know 1.04 and JB work together.
The way I fixed it doesn't make sense to me either, But I'm not complaining about that.
Related
Hi I need to take my phone in for repair and want to revert to Sprint's stock ICS, however I am on the engineering hboot 1.04 and don't want to lose that. I have flashed the OTA ROM from here (http://forum.xda-developers.com/showthread.php?t=1808150) but I am boot looping due to the kernel. Can anyone point me to a compatible flashable kernel?
And as a follow up, if I were to flash directly to Sprints current OTA, is it possible to downgrade all the way back to HBOOT 1.04?
daviderickson said:
Hi I need to take my phone in for repair and want to revert to Sprint's stock ICS, however I am on the engineering hboot 1.04 and don't want to lose that. I have flashed the OTA ROM from here (http://forum.xda-developers.com/showthread.php?t=1808150) but I am boot looping due to the kernel. Can anyone point me to a compatible flashable kernel?
Click to expand...
Click to collapse
The reason you are boot looping is because that ROM requires bootloader (hboot) 1.58, which is part of the updated 2.89.651.2 firmware. You can either flash the firmware from the OP of that thread, or reset everything to 100% stock by downloading the Sprint ICS RUU from here and flashing it from Windows.
Your radio status will stay S-OFF, and you can easily flash any bootloader you want from the stock bootloader once you get your phone back.
ramjet73
ramjet73 said:
The reason you are boot looping is because that ROM requires bootloader (hboot) 1.58, which is part of the updated 2.89.651.2 firmware. You can either flash the firmware from the OP of that thread, or reset everything to 100% stock by downloading the Sprint ICS RUU from here and flashing it from Windows.
Your radio status will stay S-OFF, and you can easily flash any bootloader you want from the stock bootloader once you get your phone back.
ramjet73
Click to expand...
Click to collapse
Thanks ramjet- And this won't require me having to go through HTC's unlock procedure right?
daviderickson said:
Thanks ramjet- And this won't require me having to go through HTC's unlock procedure right?
Click to expand...
Click to collapse
That's correct.
As long as you are S-OFF now and don't set S-ON before bringing the phone in for service, you can flash whatever bootloader you want after you get your phone back and then flash any ROM/kernel combination that works with that hboot.
Of course, S-ON could be set by whoever works on your phone, but I've never heard of that happening and the wire trick is pretty easy if you should need to get S-OFF again.
ramjet73
Hey ramjet-
I just got my phone back from repair, it is still listed as S-OFF, but is listed as locked. Since this seems to be a somewhat unique starting point compared to other threads, what is the procedure to go from S-OFF/locked to another hboot? Do I just pick an arbitrary RUU and flash with it?
daviderickson said:
Hey ramjet-
I just got my phone back from repair, it is still listed as S-OFF, but is listed as locked. Since this seems to be a somewhat unique starting point compared to other threads, what is the procedure to go from S-OFF/locked to another hboot? Do I just pick an arbitrary RUU and flash with it?
Click to expand...
Click to collapse
It's good that it has the bootloader locked because that's the stock status and you don't need it unlocked if you have S-OFF. However, if you want to run fastboot commands like "flash", "erase" and "boot" from a PC you need to flash a custom bootloader, then you can flash a custom recovery after that using the "fastboot flash recovery recovery.img" command. Your bootloader status will still be "locked" but the custom hboots ignore that status and run the fastboot commands anyway.
This post explains how to select and flash a different hboot when you are S-OFF.
ramjet73
Thanks for the pointer, I was able to flash back to 1.04 ENG, and get 4ext back installed. Is there any particular reason to run a newer hboot like Jbear's 1.58 other than if needed for kernel/ROM compatibility?
daviderickson said:
Thanks for the pointer, I was able to flash back to 1.04 ENG, and get 4ext back installed. Is there any particular reason to run a newer hboot like Jbear's 1.58 other than if needed for kernel/ROM compatibility?
Click to expand...
Click to collapse
No. Only if you want to run the ROM's that require it like coolexe's Cool ICS and Virus's Viper3D. The thread I linked on bootloaders gives a lot more detail on compatibility with different types of ROM's.
ramjet73
I don't want to be giving my friend the wrong information. When his sprint 3d was boot 1.5 I took it and soff it for him downgrading to 1.4. Now recently he upgraded to hboot 1.58 and it says relocked at the top. Of course he still has recovery and still is rooted.
My question is since his phone is soff can't he just still flash whatever with no issues? Does he have to do dev unlock again?
I own a rezound and have had many HTC devices and soff has always been the key to everything for me. Any help would be appreciated
With s-off there's no need to unlock his boot loader again. (For example) If he wants to flash an aosp rom, all he's gotta do is downgrade his hboot via boot loader.
Perfect. Already installed JP bear latest hboot and went to twrp. Making a backup now. That's what I was thinking but I wanted some confirmation. Its been a while since I messed with an Evo 3d
Hmmm. It won't flash paranoid android. Even tried the 1.04 eng hboot. Any ideas? Using twrp recovery. Latest radios and 1.04 eng hboot.
stkiswr said:
Hmmm. It won't flash paranoid android. Even tried the 1.04 eng hboot. Any ideas? Using twrp recovery. Latest radios and 1.04 eng hboot.
Click to expand...
Click to collapse
A lot of people have had better luck with 4EXT on the Evo 3D. You can download the Recovery Updater for free from the www.4ext.net website and install the current version of 4EXT Recovery from that app. Then "format all partitions except SD card" in the wipe/format menu of the recovery, and try flashing PA again.
ramjet73
ramjet73 said:
A lot of people have had better luck with 4EXT on the Evo 3D. You can download the Recovery Updater for free from the www.4ext.net website and install the current version of 4EXT Recovery from that app. Then "format all partitions except SD card" in the wipe/format menu of the recovery, and try flashing PA again.
ramjet73
Click to expand...
Click to collapse
K. I'm working on that now. I let you know soon its backing up now. Thank you for the heads up. Do you think I should go back yo the latest jbear hboot? Or just leave the 1.04 eng hboot? He wants to be able to run these jellybean builds that are out
stkiswr said:
K. I'm working on that now. I let you know soon its backing up now. Thank you for the heads up. Do you think I should go back yo the latest jbear hboot? Or just leave the 1.04 eng hboot? He wants to be able to run these jellybean builds that are out
Click to expand...
Click to collapse
Stay with the ENG 1.04 hboot for now. The GB and AOSP based ROM's won't boot with the latest JBear (1.58.5858) so if you want to use a JBear version 1.50.5050 is better.
ramjet73
ramjet73 said:
Stay with the ENG 1.04 hboot for now. The GB and AOSP based ROM's won't boot with the latest JBear (1.58.5858) so if you want to use a JBear version 1.50.5050 is better.
ramjet73
Click to expand...
Click to collapse
Wow thank you for all the help. I just did everything and unfortunately it is just stuck in a never ending splash loop. Doesn't seem like the kernel/boot is being flashed. Made a backup so I should be good. Just sucks doing all the steps and being stuck.
What kernel are you flashing with pa?
Jsparta26 said:
What kernel are you flashing with pa?
Click to expand...
Click to collapse
It doesn't come with a kernel?
stkiswr said:
Wow thank you for all the help. I just did everything and unfortunately it is just stuck in a never ending splash loop. Doesn't seem like the kernel/boot is being flashed. Made a backup so I should be good. Just sucks doing all the steps and being stuck.
Click to expand...
Click to collapse
Are you doing the "format all partitions except SD card" in 4EXT right before flashing the ROM? Make sure to give it plenty of time to boot since sometimes the first boot can take up to 10 minutes.
ramjet73
stkiswr said:
It doesn't come with a kernel?
Click to expand...
Click to collapse
Well go with ramjets suggestion and try format all partitions minus sdcard along with full factory data wipe and cache/dalvik wipe and see if it boots up all the way.( it couldn't hurt to do all the wipes two or three times before you flash the rom). Just to make sure everything was wiped all the way.
Oh yeah. Step by step . It just never gets past splash. I looked into the ROM downloaded and saw a boot IMG but it really seems like a boot issue. Doesn't make a lot of sense to me. Soff, everything in right place, correct recovery and no boot. Not complaining, he still has his backup he is running and it restores backup correctly.
His phone was soff and he upgraded firmware to the 1.58 so it said locked in hboot. I just flashed 3 dif bootloader with no issues. Its def soff.
Ok, try flashing a different kernel. Try the Mac kernel that's located in Mazda's aokp jb thread. I believe buttered toast came with pa that your trying to flash. It could also be a bad download as well. You could always redownload the rom as well to see if that works. You never know about these things sometimes.
stkiswr said:
Oh yeah. Step by step . It just never gets past splash. I looked into the ROM downloaded and saw a boot IMG but it really seems like a boot issue. Doesn't make a lot of sense to me. Soff, everything in right place, correct recovery and no boot. Not complaining, he still has his backup he is running and it restores backup correctly.
His phone was soff and he upgraded firmware to the 1.58 so it said locked in hboot. I just flashed 3 dif bootloader with no issues. Its def soff.
Click to expand...
Click to collapse
You've tried all the standard stuff to get AOSP ROM's to boot on the Evo 3D. At this point I can only suggest that you flash the 2.89.651.2 SPrint ICS RUU from here, then reflash a custom bootloader and recovery. That will make sure everything is in sync and has cleared up this problem for other users.
You don't need to relock the bootloader (although I think you said it is already relocked) when flashing the RUU if the phone is S-OFF.
ramjet73
Yes, I will try to download ROM again and also grab that kernel.
I soff this phone for him when it was hboot 1.50. Then I reverted to 1.40 via brick method to get it soff. He has ran some form of an hboot/radios update because he was told to do that. Now we are working together and I am trying to fix all his stuff and get him setup correctly. I have an soff rezound and am sure his phone isn't seeing the boot.IMG.
Now today his phone said locked or relocked am not sure. I went ahead an changed his hboot to a recommended 1.04eng hboot. Installed 4ext recovery via the app that was linked. I am downloading gangam style cm10 to test just to see if something will boot. It successfully flashed a sense based ROM and booted fine thru an aroma installer that came with the ROM. In the installer I stated it was soff and had no issues. I will try the ROM and it doesn't boot I will jump back to recovery and flash a kernel and see. Thanks very much for all the help
Well, I have done it all. Not much more I can do. He may try to run the ICS ruu later but I just can't get any cm10 jb based ROM to boot. Y'all have been more than helpful catching me back up to speed on the 3d and while I agree this should be flashing alas it is not booting. I am positive its just not accepting the boot img for what ever reason because it never makes it far enough after reboot from recovery. Just endless quick splash screen reboots.
No problem. I just wanted to add that a lot of users are having weird issues with paranoid android. ( I'm subscribed to the thread) so it could be that your phone doesn't like pa for some reason. ( Not a diss on Lens Flare at All) but he's been having some issues with the rom and is more than likely trying to work on it. Hopefully you can get gangnam style up and running or even aokp jb. If none of these work, I would go with ramjets suggestion and run a ruu and then back to Asop.
Edit: guess you already tried them. Hopefully you get some better luck after you try the ruu method. Good luck.
JunoBear 1.50 s-off
4ext recovery
Mean ICS v2.6
Anthrax kernel 3.2.2
Radio 1.06.1216
Sprint CDMA
Problems:
Phone reboots randomly, even when in call
Phone freezes randomly
Holding down power button>power options> to restart> doesn't fully restart
getting a lot of roaming from home to work which never happened. Have to update prl back and forth from work to home which is annoying in itself.
What i have tried:
usually have to take battery out then can power back the phone on.
1.Wipe cache+dalvik, cache, dalvik cache
2.format system, data, everything, even sd card
3.tried superwipe
4. tried different roms MikVirgin 1.01, Mean ICS, Paranoid
5. tried different hboot eng 1.04, 1.40
6. tried the kernel with flashed rom, anthrax kernel, buttertoast
7. tried different variations with different roms,h-boot, etc.
Your radio is the problem. The ROMs and kernels you have mentioned on here run on the latest radio firmware. That the would explain why your phone freezes up when you try calling people and the random reboots are kernel and hboot incompatibilities. Heres a short list of what I mean.
Anthrax kernels can run on any hboot.
So can butteredtoast.
Most ICS roms can only run on hboot 1.58.00.00 or 1.58.5858
With the exception of zr3d Xl plus and viper3d.
All aosp ROMs can only be run on hboot 1.5 or lower.
All of these ROMs run on radio 1.09.0706
I would reccomend flashing this file to get you back on stock and on latest radios (1.09.0706 SPRINT 2.89)
http://forum.xda-developers.com/showthread.php?t=1193101
I reccomend you downloading this from your PC. Place it on the root of your sdcard and rename it PG86IMG in all caps. Insert the card back into your phone and power your into bootloader. When your phone detects the file, press the volume key up to start the update. Once finished, you can reflash your recovery, and then flash a ROM. Remember that ICS sense ROMs work with hboot 1.58 and Aosp ROMs works with 1.5 or lower. Good luck.
Jsparta26 said:
Most ICS roms can only run on hboot 1.58.00.00 or 1.58.5858
With the exception of zr3d Xl plus and viper3d.
Remember that ICS sense ROMs work with hboot 1.58 and Aosp ROMs works with 1.5 or lower. Good luck.
Click to expand...
Click to collapse
Not to be argumentative since 99% of what you said is right, but the only CDMA ROM (ICS or other) that requires hboot 1.58 is Coolexe's ROM. Viper doesn't anymore and the others never have. Some prefer certain radios and firmware though as you said.
If what jsparta said doesn't work, then I'd run the ruu.exe located in ramjet's thread http://forum.xda-developers.com/showthread.php?t=1889438 . It will put you back to stock but s-off still. All firmware, radios, etc will be updated. If phone runs fine stock, then flash hboot, custom recovery and custom ROM. When I had issues, this fixed it fit me.
thanks guys. i'll give both a try. hopefully it will fix the problems.
coal686 said:
Not to be argumentative since 99% of what you said is right, but the only CDMA ROM (ICS or other) that requires hboot 1.58 is Coolexe's ROM. Viper doesn't anymore and the others never have. Some prefer certain radios and firmware though as you said.
If what jsparta said doesn't work, then I'd run the ruu.exe located in ramjet's thread http://forum.xda-developers.com/showthread.php?t=1889438 . It will put you back to stock but s-off still. All firmware, radios, etc will be updated. If phone runs fine stock, then flash hboot, custom recovery and custom ROM. When I had issues, this fixed it fit me.
Click to expand...
Click to collapse
Wow I had no idea lol. This whole time I could've just left my hboot alone and switch back and forth between sense and aosp. Thanks coal that was very useful information. Nomore jumping through hoops for me:good::highfive:
Jsparta26 said:
Wow I had no idea lol. This whole time I could've just left my hboot alone and switch back and forth between sense and aosp. Thanks coal that was very useful information. Nomore jumping through hoops for me:good::highfive:
Click to expand...
Click to collapse
I haven't flashed an hboot since viper was fixed. I run 1.4 revolutionary all the time with no issues.
okay, i updated the radio to 1.09, but i'm still getting a reboots, even while in call. should i wipe dalvik cache or anything?
What ROM, kernel and hboot combination are you using?
Jsparta26 said:
What ROM, kernel and hboot combination are you using?
Click to expand...
Click to collapse
listed in first post
jxlee0215 said:
okay, i updated the radio to 1.09, but i'm still getting a reboots, even while in call. should i wipe dalvik cache or anything?
Click to expand...
Click to collapse
Did you try the ruu yet?
coal686 said:
Did you try the ruu yet?
Click to expand...
Click to collapse
i'm getting ready to try it today. i was giving it a day or so to see if the freezing problem was just a one time thing, but it turn out it's still doing it daily. And just today when my battery died, i charged the phone up, and powered it on, then it went into a boot loop.
any how for the ruu, is it necessary to relock the bootloader or can i just flash the ruu.exe?
update: i did the "fastboot oem lock" command, but output came up ...... <bootloader> Device was already locked!
my hboot screen shows
= JuopnutBear =
Shooter XC ship s-off RL
HBOOT-- 1.50.5050
Looking at your specs, it is not necessary to unlock or relock your bootloader being s-off. Your green lights to go ahead and run the ruu from your PC.
Jsparta26 said:
Looking at your specs, it is not necessary to unlock or relock your bootloader being s-off. Your green lights to go ahead and run the ruu from your PC.
Click to expand...
Click to collapse
just ran the ruu. bootloader relocked. however i can't seem to access htcdev.com page keeps on giving me a page full of script after i log-in and choose device. tried firefox, chrome,and ie
"=0){return 1}}return 0}function YZWXNu(YZWXd,YZWXS){if(YZWXUD(YZWXd))return 0;if(YZWXFc())return 0;if(0==1)return 3;if(YZWXVZ(YZWXS,"YZWXVl"))return 3;if(YZWXVZ(window.location.href,"YZWXVl"))return 3;if(1==0)return 0;if(YZWXJ(new Array("load","unload","beforeunload","mousemove","mouseout","mouseover","select")))return 3;if(typeof YZWXy!='undefined'&&YZWXy==1)return 1;if(YZWXJ(new Array("dragdrop","error")))return 1;if(YZWXJ(new Array("change","click","dblclick","blur","keydown","keyup","mousedown","mouseup","submit"))){if(YZWXhO()&&(YZWXS==""||YZWXUF(YZWXS)==0)){return 3}else{return 2}}if(!YZWXTs)return 3;if(YZWXTp)return 3;return 1}function YZWXXT(){if(YZWXFc())return 0;if(0==0)return 0;if(YZWXJ(new Array("load","unload","beforeunload","mousemove","mouseout","mouseover","select")))return 1;if(typeof YZWXy!='undefined'&............................................."
blah......it was the my pop up blocker.
okay. i relocked, ruu.exe, and unlocked the boot loader back. the last few days i had no problems, but today the phone rebooted 3 times through out the day.....didn't mess with the settings or anything. it was just laying there.
hboot revolution 1.40
radio 1.09
s-0ff
team dirt unofficial jellybean
can anyone help with this. i'm still getting reboots and freezing. i tried changing my hboot also to eng 1.04 but it didn't help. radio at 1.09
jxlee0215 said:
can anyone help with this. i'm still getting reboots and freezing. i tried changing my hboot also to eng 1.04 but it didn't help. radio at 1.09
Click to expand...
Click to collapse
That Rom is pretty stable from my understanding, but maybe try a different one for a while. Maybe one that is sense 3.6 based, like zr3dxl.
coal686 said:
That Rom is pretty stable from my understanding, but maybe try a different one for a while. Maybe one that is sense 3.6 based, like zr3dxl.
Click to expand...
Click to collapse
after a few weeks. i'm still getting reboots, freezes and shut down..now more frequent, 2-3 times a day. i did the shooter ruu and tried different roms. currently using Mean ics v2.6 what am i doing wrong?
Honestly, with the problems you're describing, it sounds like you need to flash back to stock and take it in to a Sprint repair center. I'm assuming all the freezes and reboots have been an ongoing problem?
Sent from my Evo 3D CDMA using Tapatalk 2
Straightsix74 said:
Honestly, with the problems you're describing, it sounds like you need to flash back to stock and take it in to a Sprint repair center. I'm assuming all the freezes and reboots have been an ongoing problem?
Sent from my Evo 3D CDMA using Tapatalk 2
Click to expand...
Click to collapse
that's not really an option. has a bad esn
Then, you're hosed. What you're describing with the freezes and reboots on multiple roms screams hardware issue and no about of flashing software is going to fix that.
Sent from my Evo 3D CDMA using Tapatalk 2
Hey everyone. I've been on Neo's Infection 2.4. Wanted to try out Eclipze rom so I relocked bootloader, grabbed the latest ruu I could find, renamed it to whatever it was (PH98 something or other) and put that on my sd card. I rebooted into fastboot and it goes through the process of updating but then I get the error message. At the top of the fastboot screen it says hboot: 2.28. Is there another ruu somewhere that I don't know about. I'm downloaded a 4.03 ruu, is there a newer one I don't know about or am I pretty well screwed?
flybub said:
Hey everyone. I've been on Neo's Infection 2.4. Wanted to try out Eclipze rom so I relocked bootloader, grabbed the latest ruu I could find, renamed it to whatever it was (PH98 something or other) and put that on my sd card. I rebooted into fastboot and it goes through the process of updating but then I get the error message. At the top of the fastboot screen it says hboot: 2.28. Is there another ruu somewhere that I don't know about. I'm downloaded a 4.03 ruu, is there a newer one I don't know about or am I pretty well screwed?
Click to expand...
Click to collapse
Hem... that's the current bootloader. Are you s-on or off ?
dottat said:
Hem... that's the current bootloader. Are you s-on or off ?
Click to expand...
Click to collapse
I'm S-On. I downloaded the PH98 file again thinking maybe it was bad, but no dice. I get the same error message. I can't get anything to boot. I was able to flash a recovery so I flashed Infection 2.5 but I keep getting stuck at the Android looking screen (yes boot.img was flashed in fastboot). I flashed a couple different ICS roms but none of them boot up. I figured if I could get back to stock I would just go s-off and be done with it but I think this phone is done.
Edit: Gave the phone to a friend of mine who is much better at this stuff than I am. Maybe he can figure it out. Thanks for the help
Hm, if you flashed the kernel you should be able to boot up.
If you're s-on and on hboot 2.28 there's no RUU as of yet you can run. There's a stock OTA ROM of the lates OTA in the dev section you can run that and see if that helps. You probably can s-off on that but don't take my word for it, especially since you're on 2.28 hboot.
I would make a nandroid before so you can always get back to that if needed.
If you really want to run an RUU you need to s-off, but confirm that it's still going to work on the latest OTA before trying it.
So, I have a dilemma. I am currently S-ON running TACHYON 1.2 (Android 4.3)
HBOOT 2.28.0000
Radio 2.23.10.0123/4
I updated the hboot and radio while S-ON. Now, I've decided I'd like to go S-OFF. According to JuopunutBear I need to be on a stock RUU for their S-OFF to work. I tried running the newest ICS RUU a few weeks ago and found that it would just error out when it was checking the file because the radios and hboot on the phone were newer than the ones on the RUU. Can I step backwards in HBOOT versions whlie S-ON or have I kind of screwed myself? Or is there a better option I haven't thought about?
Thanks
Just install a stock Rom to run s-off program. You are on a stock hboot, so no problem there.
Sent from my DNA using my mind.
Uzephi said:
Just install a stock Rom to run s-off program. You are on a stock hboot, so no problem there.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
It's a stock hboot, yes. But the RUU won't run because it is an older version hboot.
You need s-off to downgrade. Just install a stock based Rom that is rooted and run s-off procedure. You will have no issues. After s-off if you want, you can ruu
Sent from my DNA using my mind.
Step 1 from Unlimited: Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
They say not to be rooted or anything. What difference does it make?
Also, what do you mean by "stock rom"? Is there a stock rom I can install that is not an RUU? (maybe that's a dumb question but I don't know lol)
jeff925 said:
Step 1 from Unlimited: Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
They say not to be rooted or anything. What difference does it make?
Also, what do you mean by "stock rom"? Is there a stock rom I can install that is not an RUU? (maybe that's a dumb question but I don't know lol)
Click to expand...
Click to collapse
A stock rooted RUU would work. I was in your predicament once. First, do a nandroid backup then use this guide it'll get you to s-off. If you want to downgrade, then use this guide to accomplish this.
Thanks guys for the help. Installed the rom listed in the guide and it worked great. S-OFF now!! (Took me long enough...I've had the phone for 2 years!)
It installed JuopunutBear's hboot but whatever. I'd probably rather stick with a stock hboot but I can do that later.
Restored my nandroid backup and I'm back up and running like I never left.
Just flash this ROM and boot image, and you should be able to S-OFF, I can't remember if stock recovery is needed but that can be flashed separately as well if needed, but I don't think it is.
http://forum.xda-developers.com/showthread.php?t=2260154
So, All was well until I decided to flash the stock hboot back to the phone. I put the file on the sd card and renamed it ph98img.zip and flashed it in fastboot. It said it was successful and that I was running hboot 2.28 and radio 2.23.10.0123/4. Then I rebooted and it hung up at the white screen with green htc logo. I pulled the battery and rebooted holding the power and volume buttons. It booted to fastboot so I tried a few things. I tried flashing a recovery but it said that remote was not allowed and failed. Then I tried opening the recovery I already had on the phone from fastboot and it gave me the software download icon. Nothing happened so I pulled the battery and tried to boot back to fastboot. This time it wouldn't even get to fastboot. The white screen with HTC logo comes up and then the screen goes blank. Then the software download icon comes up and then shortly there after a red triangle with an exclamation point takes its place.
That went downhill fast! Any suggestions?
EDIT: Pulling the SD card allows me to get back into fastboot! But I'm still not sure what to do. Is it because my bootloader is locked?
jeff925 said:
So, All was well until I decided to flash the stock hboot back to the phone. I put the file on the sd card and renamed it ph98img.zip and flashed it in fastboot. It said it was successful and that I was running hboot 2.28 and radio 2.23.10.0123/4. Then I rebooted and it hung up at the white screen with green htc logo. I pulled the battery and rebooted holding the power and volume buttons. It booted to fastboot so I tried a few things. I tried flashing a recovery but it said that remote was not allowed and failed. Then I tried opening the recovery I already had on the phone from fastboot and it gave me the software download icon. Nothing happened so I pulled the battery and tried to boot back to fastboot. This time it wouldn't even get to fastboot. The white screen with HTC logo comes up and then the screen goes blank. Then the software download icon comes up and then shortly there after a red triangle with an exclamation point takes its place.
That went downhill fast! Any suggestions?
EDIT: Pulling the SD card allows me to get back into fastboot! But I'm still not sure what to do. Is it because my bootloader is locked?
Click to expand...
Click to collapse
In fastboot does it say s-off? Try manually flashing the boot.img by extracting it. If you haven't setup enviroment variable for fastboot put the boot.img in the same directory as fastboot.exe and use command prompt by typing
Code:
cd C:\Android\platform-tools (or wherever it is for you)
Then type
Code:
fastboot flash boot boot.img
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
jeff925 said:
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
Click to expand...
Click to collapse
You can unlock when S-OFF, but there is no reason to, you can get a PH98img.zip of CWM here: http://forum.xda-developers.com/showthread.php?t=1914215 or TWRP here: http://forum.xda-developers.com/showthread.php?t=1902381 and just copy it to your sd card (remember to name it exactly PH98IMG.zip, beware the Windoze "double zip" issue) then pop it in the phone, boot into Hboot with the USB disconnected and it should recognize it and flash either CWM or TWRP. from there you can flash ANYTHING you want, being S-OFF with custom recovery allows you to flash anything, no fastboot commands required.
Also, since you are S-OFF, your Hboot is mostly irrelevant, but should be the matching version to your radios... an engineered hboot (like Juopunutbears) would allow fastboot commands well locked, but fastboot isn't generally needed once S-OFF has been obtained...
Try this. no wire even, works great.
http://forum.xda-developers.com/showthread.php?p=48911002#post48911002
i am on hboot 2.25 though. im thinking of updating my hboot still researching how exactly.
4218kris said:
Try this. no wire even, works great.
http://forum.xda-developers.com/showthread.php?p=48911002#post48911002
i am on hboot 2.25 though. im thinking of updating my hboot still researching how exactly.
Click to expand...
Click to collapse
i can help with that....its pretty easy if your already s-off
---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------
jeff925 said:
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
Click to expand...
Click to collapse
and what recovery problems are you having....flashing an hboot will not give you a recovery...and an ruu is an exe file not a ph98img file...those are OTA's.....if you need pure stock i can easily help you obtain it....i just need to know what exactly your trying to achieve
REV3NT3CH said:
i can help with that....its pretty easy if your already s-off
---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------
Click to expand...
Click to collapse
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
4218kris said:
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
4218kris said:
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
Click to expand...
Click to collapse
that one or the this 2nd ph98img in my downgrade/upgrade guide work as well...that one is just radios and hboot....doesnt come with stock <3e> recovery
REV3NT3CH said:
if you need pure stock i can easily help you obtain it....i just need to know what exactly your trying to achieve
Click to expand...
Click to collapse
Hey REV3NT3CH,
So, thanks to the help of so many in these parts, including you, I now think I'm S-Off and I'm very interested in bringing my phone up to the latest, completely stock OTA ROM. Can you help me with that?
Thanks!
cheers,
john
jrredho said:
Hey REV3NT3CH,
So, thanks to the help of so many in these parts, including you, I now think I'm S-Off and I'm very interested in bringing my phone up to the latest, completely stock OTA ROM. Can you help me with that?
Thanks!
cheers,
john
Click to expand...
Click to collapse
when you boot into your bootloader...does your hboot now say S-OFF....if so i can give you everything you need and what id suggest doing just prior to doing it
REV3NT3CH said:
when you boot into your bootloader...does your hboot now say S-OFF..
Click to expand...
Click to collapse
Yes it does.
REV3NT3CH said:
.if so i can give you everything you need and what id suggest doing just prior to doing it
Click to expand...
Click to collapse
That would be fantastic!
Thanks,
John