Help with screwed up HBoot. Can't flash a bunch of roms - HTC EVO 3D

I'm still a noob when it comes to Android. My 3D had a 1.30 hboot, and I rooted it with Revolutionary the day it was released back last summer.
So I had been using the ICS CM9 rom that was first released several months ago (actually my phone was sitting in my drawer as I was waiting on an official ICS update)
Anyway I flashed PG86IMG.zip from Virus
http://forum.xda-developers.com/showthread.php?p=29613228#post29613228
and followed all the steps. Everything went smoothly.
Now I wanted to return to CM9 or any other non-sense rom so I could use a bluetooth wiimote since I heard HTC sense roms don't support the proper BTstack.
Every time I flash any of those roms, they end in endless boot loops. CM9 Devil Toast, CM10, none of them work. I do superwipe and everything. The only roms that work are sense based. How do I fix this?
My Hboot is now 1.58. It says ***LOCKED*** with "SHOOTER XC SHIP S-OFF RL". I heard this doesn't mean anything because I'm still rooted with S-Off, but why can't I flash those roms anymore? I want to play some GBA with the WiiMote.
I can't seem to find exact info on my problem. I know I should ask in Virus' thread, but his roms are working fine.
Thanks.

I'd say just run a 2.17 firmware zip through fastboot
Sent from my PG86100 using xda premium

Datguy_n_Disguy said:
I'd say just run a 2.17 firmware zip through fastboot
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
You should be able to just flash a different Hboot. There is a thread in the Dev section with the 1.40 and the Eng 1.04 Hboots. Just flash and you can go back.
From what I understand you cannot run AOSP or older Sense builds on the newer Hboot currently.

Related

Boot loop on all ics roms

I keeping getting a bootloop on all ics roms and I tried a kernal that someone recommend but it kills my 3d and i get random reboots . Is there any way to fix this problem and install the ROM with everything working. I'm on hb 1.50 . S- on . Or is there a way to downgrade to hb 1.40 but i don't have a Linux . What's the easiest way ?
Sent from my PG86100 using XDA
I also get the same results!
You can always try 4EXT Recovery with smartflash on. It works for both S-On and S-Off
ccr515 said:
I keeping getting a bootloop on all ics roms and I tried a kernal that someone recommend but it kills my 3d and i get random reboots . Is there any way to fix this problem and install the ROM with everything working. I'm on hb 1.50 . S- on . Or is there a way to downgrade to hb 1.40 but i don't have a Linux . What's the easiest way ?
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
try a superwipe. that fixed mine. Look in the dev forum for it (i think you can find it in the mean rom thread)
You could also downgrade using the instructions in the development thread. Ir doesnt require Linux, it includes a downloadable bootable CD. ITA damn near an automated process minus the brick part. And +1 for 4ext recovery it has features built just for S-on.
My other shooter is an FNAR .308
I already tired a super wipe and my netboot doesn't have a cd drive .
Sent from my PG86100 using XDA
Try using any of Chad.Goodman's ICS Kernel after flashing an ICS ROM
1) DO THIS AT YOUR OWN RISK
2) USE THE RIGHT KERNEL
*credit to chad.goodman* http://forum.xda-developers.com/showthread.php?t=1623646
That the kernal that I already use . It breaks my 3d and i get random reboots
Sent from my PG86100 using XDA
ccr515 said:
That the kernal that I already use . It breaks my 3d and i get random reboots
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Well what kernel did you use, you could be flashing the wrong one. The other option is to downgrade HBOOT ,, no linux required
http://forum.xda-developers.com/showthread.php?t=1563342
---------- Post added at 08:10 PM ---------- Previous post was at 07:49 PM ----------
I got my ICS ROM to work by flashing RLS1
I doubt downgrading HBOOT will help, he's getting it to work with Chad's kernel. I'm exhibiting the exact same issue with bootloops with the stock kernel(in my case I used the shooter ice kernel to get it to boot) and I'm S-OFF/GSM so I'm pretty sure the issue isn't HBOOT related.
Same here
I have the same issue. I use 4ext with smartflash for recovery. I'm able to flash any GB rom I want, but when I try an ICS rom with a stock kernel I get the boot looping. Is there any other way to make this work? I don't want to dig into the brick/unbrick business if I can help it. I have also tried using Flash Img GUI and fastboot/adb to flash the kernel with the exact same results. Any information on this would help, but a solution would be fantastic!
._. I see what's going on... It's GSM users trying to flash CDMA kernels once again.
Sent from my PG86100 using XDA
What I did was use the new s off for 1.50 and once I got that done I was able to flash any ics Rom I want . Look for it in the development section.
Sent from my PG86100 using XDA
ccr515 said:
What I did was use the new s off for 1.50 and once I got that done I was able to flash any ics Rom I want . Look for it in the development section.
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
+1 to this. The stock Ics kernel does not do well with 1.5 s-on. Since you cannot downgrade to 1.4 s-off, you should try the new 1.5 s-off method. Otherwise you have to use a custom kernel which is not 100% yet.
Sent from my PG86100
coal686 said:
+1 to this. The stock Ics kernel does not do well with 1.5 s-on. Since you cannot downgrade to 1.4 s-off, you should try the new 1.5 s-off method. Otherwise you have to use a custom kernel which is not 100% yet.
Sent from my PG86100
Click to expand...
Click to collapse
Seems like no stock ics kernels like 1.4 hboot period with or without s-off. None would work for me until i updated my hboot to 1.5 and had s-off.
smokin1337 said:
Seems like no stock ics kernels like 1.4 hboot period with or without s-off. None would work for me until i updated my hboot to 1.5 and had s-off.
Click to expand...
Click to collapse
I've been running 1.4 s-off since the downgrade method came available and have never had an issue with any ics ROMs.
Sent from my PG86100
Can someone post a link to the new S-Off method for hboot 1.5?
MakeMeFibonacci said:
Can someone post a link to the new S-Off method for hboot 1.5?
Click to expand...
Click to collapse
Here it is: http://forum.xda-developers.com/showthread.php?t=1585846
I recommend you read all about it first as you have to connect two contact points on your phone using insulated wire, which sounds kind of dangerous.
coal686 said:
Here it is: http://forum.xda-developers.com/showthread.php?t=1585846
I recommend you read all about it first as you have to connect two contact points on your phone using insulated wire, which sounds kind of dangerous.
Click to expand...
Click to collapse
The hboot downgrade seems a lot less scary for sure. In all honesty it was ez and took me less than 30 mins but to each his own

Update HBOOT 1.15 to 1.19?

It appears that HBOOT 1.15 will not get s-off any time soon...Is it O.K. to upgrade to HBOOT 1.19 and wait then for s-off capabilities, or is 1.19 taboo also.
I am rooted, can I stall HBOOT 1.19 with abd, or would I have to root the phone again, and install a recovery...
There are 2 ways, ruu or revert to stock for ota. You must relock bootloader before ruu or ota. For the ota you need stock recovery as well. There's a few misconceptions floating around. First is that you need to update to run the latest base, this is simply not true, I'm running mikeys latest without issue. The second is basically the same but involving the aroma installer, flashes fine but sometimes kernel will not flash and you boot to bootloader. This does not mean you need to update only that the kernel did not like the new base, fastboot kernel and you'll be fine. Some people still have WiFi issues and others have LTE issues, both should have been addressed in the last 2 updates and people with the latest firmware are still having problems. To me this does not warrant relocking upgrading and going through the unlock again.
A lot of people including myself don't consider 1.19 an upgrade and like om said you don't nerf to update
Sent from my EVO using xda app-developers app
Always best waiting
In my experiences, it is almost ALWAYS best to wait. If for some reason 1.19 gets s-off before 1.15 then u can update. But for now, just wait. I got lucky and I'm 1.12 s-off either way warranty is gone so always get s-off whenever possible.
I keep seeing threads about s-off. I'll like people to be more specific as to what they're trying to achieve that they can't while being s-on?
Sent from my EVO using xda premium
Just the ability to directly flash software to partitions normally inaccessible, Firmware basically. Those of us s-on would have to flash back to stock, lock hboot, and accept an ota or relock and run the ruu
Also, don't know the details of any of it, but in the s-off bounty thread guy is donating a 1.15 hboot. U can flip a coin better than I can say what they will do with it then. Either update it to 1.19 or try and find the exploit on 1.15.
Personally, if I was a badass at finding exploits in HTC coding then I'd crack both like yesterday. But if I was that badass I'd have better stuff to do as well... Hoping for 1.19 s-off just for future development.
Anthonicia said:
Also, don't know the details of any of it, but in the s-off bounty thread guy is donating a 1.15 hboot. U can flip a coin better than I can say what they will do with it then. Either update it to 1.19 or try and find the exploit on 1.15.
Personally, if I was a badass at finding exploits in HTC coding then I'd crack both like yesterday. But if I was that badass I'd have better stuff to do as well... Hoping for 1.19 s-off just for future development.
Click to expand...
Click to collapse
there is a guy in the s-off thread saying he will give up his phone and i saw fuses sent him a PM reply about it hang in there guys
om4 said:
There are 2 ways, ruu or revert to stock for ota. You must relock bootloader before ruu or ota. For the ota you need stock recovery as well. There's a few misconceptions floating around. First is that you need to update to run the latest base, this is simply not true, I'm running mikeys latest without issue.
Click to expand...
Click to collapse
Quick question: Are you saying that if I wanted to run Mean ROM that I do not need to be in the latest OTA? I'm confused because I was under the understanding that we needed to be on 2.13. Please clarify for me.
Sent from my EVO LTE using xda app
No you don't, I ran meanrom a few days ago and today I switched to viper 2.02. Meanroms kernel installer worked fine, viper required fastboot but both run fine
Thanks for the quick response. Wow, I feel like a dumb *ss now. I've been holding out trying any new roms because I didn't want to come off of hboot 1.15.
Which rom do you like better so far between viper and mikey's?
Sent from my EVO LTE using xda app
The level of customization on viper is crazy, meanrom runs great with evilz kernel and is closer to stock. I'm still sifting through the different mods for viper and I've yet to check out any themes but so far but I'm still digging through it all

1.57 H-Boot?

I have the Evo V 1.57 H-Boot S-Off that's rooted and with 4Ext recovery. My question is, what ROMS are compatible with this setup. I know CM10 isn't which is fairly disappointing. I wanna flash something different so I can WIFI Tether. Thank you.
Sent from my HTCEVOV4G using xda premium
CM10 does work with the Evo V
If you are refering to MMS not working you can find a fix Here. And it seems your on hboot 1.57 if you had read the CM10 OP you noticed you need to downgrade your hboot to 1.50 or lower. (eng boot recommended)
Im also sure any CDMA Rom will work with your device you might just have to change the APN
Okay. I understand that and thank you for the help. But my other question was are there any compatible ROMs with my H-Boot?
YourWorstPoison said:
Okay. I understand that and thank you for the help. But my other question was are there any compatible ROMs with my H-Boot?
Click to expand...
Click to collapse
Most ICS Sense based ROM's should work fine with hboot 1.57. There are many in the Evo 3D development forum on XDA and some specifically designed for the Evo V in that device forum on androidforums.com.
You will need to downgrade your hboot if you want to run GB and/or AOSP based ROM's and there are instructions to do that here. My favorite hboot is JBear 1.50.5050 since it is the newest version that boots most ROM's.
ramjet73
I'll check them out. Everytime I tried running an ASOP Rom, it just wanted to bootloop. Drives me crazy. Thank you. Appreciate it.
Sent from my HTCEVOV4G using xda premium

CM v10.1 "Wild for the Night" - HBOOT Issues

First and foremost, I sincerely apologize if there is some information out there that I have missed or failed to read. I am a noob to this forum as far as posting goes but I've been reading posts here for some time and thus far I have been unable to find a solution to my problem.
This is the third time that I'm flashing my EVO 3D, however it is the first time I've actually used S-OFF. This particular iteration of my phone was completely vanilla ICS on hboot 1.58. I followed the dummy-proof guide stickied to this forum all the way through getting S-OFF through the "wire trick" method. At this point I wound up with a "jbear" version of hboot 1.58. Sweet deal.
Problem is I decided I wanted to try CM v10.1 so I had to change hboot to something below 1.57... No biggie. Except for I messed with the thing for hours and had absolutely no luck getting it to boot. The only thing that worked was returning to the jbear 1.58 hboot and restoring an earlier backup from 4EXT with the stock ROM.
Long story short after multiple flashes, going from jbear 1.58 to jbear 1.50 and back several times I finally got the phone running on CM v10.1 "Wild for the Night" with hboot ENG 1.04.
So... my question is as follows. Have I hosed something up in my tinkering by going back and forth between hboots multiple times? I'm concerned that doing the v1.58 "wire trick" S-OFF and then jumping from one hboot to the other only to wind up with ENG 1.04 might cause issues in the future.
I apologize for any incoherence on the above. It is now 6am and I've been at this for hours...
kriz225 said:
First and foremost, I sincerely apologize if there is some information out there that I have missed or failed to read. I am a noob to this forum as far as posting goes but I've been reading posts here for some time and thus far I have been unable to find a solution to my problem.
This is the third time that I'm flashing my EVO 3D, however it is the first time I've actually used S-OFF. This particular iteration of my phone was completely vanilla ICS on hboot 1.58. I followed the dummy-proof guide stickied to this forum all the way through getting S-OFF through the "wire trick" method. At this point I wound up with a "jbear" version of hboot 1.58. Sweet deal.
Problem is I decided I wanted to try CM v10.1 so I had to change hboot to something below 1.57... No biggie. Except for I messed with the thing for hours and had absolutely no luck getting it to boot. The only thing that worked was returning to the jbear 1.58 hboot and restoring an earlier backup from 4EXT with the stock ROM.
Long story short after multiple flashes, going from jbear 1.58 to jbear 1.50 and back several times I finally got the phone running on CM v10.1 "Wild for the Night" with hboot ENG 1.04.
So... my question is as follows. Have I hosed something up in my tinkering by going back and forth between hboots multiple times? I'm concerned that doing the v1.58 "wire trick" S-OFF and then jumping from one hboot to the other only to wind up with ENG 1.04 might cause issues in the future.
I apologize for any incoherence on the above. It is now 6am and I've been at this for hours...
Click to expand...
Click to collapse
no, switching your hboots won't cause any issues with your phone. I will tell you however, always make sure you're on a compatible hboot for any ROM you flash
You can change hboots 10 times a day until you change your phone, nothing will break because of that. The problem is that some hboots are incompatible with some roms and some android versions. For most Jelly Bean you need the x hboot, while for Ice Scream Sandwitch you need the y hboot. You get the point l. Nothing breaks as long as you properly change hboots and don't get errors in the process of doing so.
Relax and flash away whatever you want
When flashing a new HBOOT you need to boot into recovery and wipe your cache partition then reboot again to recovery using the reboot to recovery option within recovery. Then flash ROM and GAPPS. Also make sure to be using the VERY latest 4ext recovery. The test version
私のEVO 4G LTEから送信される。
Thanks!
Thanks for the responses, that's reassuring.
dastin1015 said:
When flashing a new HBOOT you need to boot into recovery and wipe your cache partition then reboot again to recovery using the reboot to recovery option within recovery. Then flash ROM and GAPPS. Also make sure to be using the VERY latest 4ext recovery. The test version
私のEVO 4G LTEから送信される。
Click to expand...
Click to collapse
I saw these suggestions on your development thread and followed them. This is how I finally got it to work with the ENG 1.04 and so far the ROM is working great.
Not to take my own thread off topic but is there a list of supported kernels for this ROM? I'm interested in under clocking, etc. and not sure if that's possible on stock.
kriz225 said:
Thanks for the responses, that's reassuring.
I saw these suggestions on your development thread and followed them. This is how I finally got it to work with the ENG 1.04 and so far the ROM is working great.
Not to take my own thread off topic but is there a list of supported kernels for this ROM? I'm interested in under clocking, etc. and not sure if that's possible on stock.
Click to expand...
Click to collapse
Stock kernel has what you need.
私のEVO 4G LTEから送信される。
Thanks!
dastin1015 said:
Stock kernel has what you need.
私のEVO 4G LTEから送信される。
Click to expand...
Click to collapse
Thanks. I found the option, I apologize for the noobishness.
you're fine. i swapped a few hboots a few months ago so I could run CM10.1 roms. i think im on 1.50 with no problems
A sense stock kernel? Can I get the link to a underclocked kernel for cm10.1? Because I think this might solve my problem of 3g not toggling off.
Sent from my HTCEVOV4G using xda app-developers app
SkinnyBiggs said:
A sense stock kernel? Can I get the link to a underclocked kernel for cm10.1? Because I think this might solve my problem of 3g not toggling off.
Sent from my HTCEVOV4G using xda app-developers app
Click to expand...
Click to collapse
Not sense. AOSP stock with max cpu 1128.
Sent from my Evo 3D CDMA using xda premium
SkinnyBiggs said:
A sense stock kernel? Can I get the link to a underclocked kernel for cm10.1? Because I think this might solve my problem of 3g not toggling off.
Sent from my HTCEVOV4G using xda app-developers app
Click to expand...
Click to collapse
Seems like we can no longer flash different kernels on cm10. What I suggest you do is try out dirty unicorns with dirty Mac kernel. Or kernel of your choice.
Sent from my Evo 3D CDMA
Astrikz said:
Seems like we can no longer flash different kernels on cm10. What I suggest you do is try out dirty unicorns with dirty Mac kernel. Or kernel of your choice.
Sent from my Evo 3D CDMA
Click to expand...
Click to collapse
If you want your favorite kernel to work on CM bug the developer and get them to update their code. There's no reason to be running legacy code when we're all about having the latest and greatest
私のEVO 4G LTEから送信される。
I went through about 5 versions of HBoot also before ending up on 104 eng... everything seems to be fine!

[Q] Newbee trying to install a custom room, have s-off

I followed some videos on youtube and have the following:
Radio S-Off
4Ext latest
Rooted phone.
I am now venturing into custom ROMs, one thing I realized that I have not taken ANY OTAs in a at least a year and a half on my sprint EVO 3D. So, my System Info is as follows:
Android Version: 2.3.3
HTC Sense: 3.0
Software number: 1.13.651.7
HBoot 1.40
I was looking into Cool ICS Rom, but it says I need to have a newer firmware and HBoot 1.58
I am not sure how to upgrade my firmware?
Can someone please point me in the right direction?
Thanks,
RoSahas.
rosahas said:
I followed some videos on youtube and have the following:
Radio S-Off
4Ext latest
Rooted phone.
I am now venturing into custom ROMs, one thing I realized that I have not taken ANY OTAs in a at least a year and a half on my sprint EVO 3D. So, my System Info is as follows:
Android Version: 2.3.3
HTC Sense: 3.0
Software number: 1.13.651.7
HBoot 1.40
I was looking into Cool ICS Rom, but it says I need to have a newer firmware and HBoot 1.58
I am not sure how to upgrade my firmware?
Can someone please point me in the right direction?
Thanks,
RoSahas.
Click to expand...
Click to collapse
This is what I am going to try and then install an ICS HBoot after the RUU:
http://forum.xda-developers.com/showpost.php?p=32174176&postcount=52
Try installing the firmware only zip of the latest ruu that should work 1.40 hboot shouldn't stop you from installing a ROM in fact I don't think any hboot can don't quote me on that
Sent from my Evo 3D CDMA using xda app-developers app
luigirocks said:
Try installing the firmware only zip of the latest ruu that should work 1.40 hboot shouldn't stop you from installing a ROM in fact I don't think any hboot can don't quote me on that
Sent from my Evo 3D CDMA using xda app-developers app
Click to expand...
Click to collapse
Okay hboot versions can be incompatible with different roms. Here is a general rule of thumb for cdma (sprint) 3d's. Latest firmware seems to work with every rom. Older firmware will not work with htc's ics roms.
Hboot 1.58 - works on htc's ics roms
Hboots 1.04-1.50 - works with htc's gingerbread roms and source built roms gb, ics, jb.
Now some of the custom htc ics roms will work with any hboot.
Always read the OP and check for requirements. FYI of you are s-off than you can change Hboots without much hassle. I will do a write up on hboot flashing.
Also if a rom wont boot or bootloops after installation it is most likely wrong hboot or you are using old firmware.
Sent from my PC36100 using xda app-developers app

Categories

Resources