I have a question about going S-Off with Flashmaniac and Revolutionary. I unlocked my phone via HTC Dev way a before a few months but now finnaly i want to go s-off. I'm on a JB rom and have 4ext recovery, HBOOT 1.49.0018. In the thread it says that it can be done with my hboot and only with a Gingerbread ROM. Now my question is can i use a GB rom like LeeDroid or do i need to use my first orginal rom that i backed up and can i do it with 4ext recovery or what? If some could help me please
I did s-off using this tool quite a while back but i remember i was on a custom ics rom. Just make sure your rom is rooted and usb debugging is turned on. Do all 3 steps and you should be good to go.
EM|NEM said:
I did s-off using this tool quite a while back but i remember i was on a custom ics rom. Just make sure your rom is rooted and usb debugging is turned on. Do all 3 steps and you should be good to go.
Click to expand...
Click to collapse
Thanks on the answer ..I'll try it
I think that easiest method is by "wire trick" Here you go http://forum.xda-developers.com/showthread.php?t=1743466 yust follow method C
I tried the Flasmaniac way and it didnt work. Im stuck on the 3rd step when it needs to relock my device.
Relock your phone, install officiall GB rom and since u have hboot version .0018 u must to downgrade to .0007 or 0008 , then u are ready to go with revolutionary. Othervise u cant gain s-off using revolutionary method with some ics or jb custom rom.
For flasmaniac metod i think u need gb based rom
Sent from my HTC EVO 3D X515m using xda app-developers app
I had a custom GB rom and people said that it works with it. But my problem is that i can't relock the bootloader. When i try with fastboot oem lock it gives me an error and the phone reboots and the flahsmaniac way gets stuck when it needs to relock it. So i feel lost,and i don't like to try the wire trick, don't know if it's safe or not.
Related
Hello folx,
My device is unlocked, rooted, hboot version 1.53.0007 and s-on. I try to flash rom via 4ext recovery touch. for every rom the boot image show up than restart with an infinite loop. How do i fix it ? The problem caused by hboot version or being s-on ? I don't want to mess up with s-off. I don't want to push my phone that far with wired stuff.
Thanks.
S-on is your issue, the only way you might be able to flash a rom without resulting in a boot loop is with 4ext with smart flash enabled but there's also the hboot which could cause issue too depending in which rom you flashed and also the firmware could also cause issues, so to sum up, go s-off already and do us all a favorite, makes life so much easier
(Don't ask me for help as I couldn't care if your phone explodes, eh!
Best way to fix this is to get s-off using the wire trick then downgrade your hboot to 1.4 (I had the same issue and this fixed it). As flash said, use 4ext recovery. The wire trick isn't that bad, it's actually really easy.
Is there any proper tutorial that i can apply s-off to my phone ? Does the hboot version differ this process?
Sent from my HTC EVO 3D X515m using xda app-developers app
By the way i wanted to install latest miui jb rom with 4ext recovery by enabling smartflash. Even with that option it doesn't work. And also first i try to flash boot img and than installed the rom still same.
Sent from my HTC EVO 3D X515m using xda app-developers app
you wont be able to boot jb roms with your hboot. get s-off using this guide and downgrade hboot
http://forum.xda-developers.com/showthread.php?t=1743466
Do method D (wire trick)
salihk. said:
By the way i wanted to install latest miui jb rom with 4ext recovery by enabling smartflash. Even with that option it doesn't work. And also first i try to flash boot img and than installed the rom still same.
Sent from my HTC EVO 3D X515m using xda app-developers app
Click to expand...
Click to collapse
You need to downgrade your Hboot to install jb roms, and the only way to do it is with S-OFF, I did a few phones using the wire trick method and have not had any problems yet. S-OFF is well worth it if you want try different roms...
mcerk02 said:
You need to downgrade your Hboot to install jb roms, and the only way to do it is with S-OFF, I did a few phones using the wire trick method and have not had any problems yet. S-OFF is well worth it if you want try different roms...
Click to expand...
Click to collapse
This guy is unbelievable. You have been posting redundant solutions that have already been suggested. If there's something different and more insightful that you can add please do so. Otherwise don't post. I know your trying to help but just wait until somebody hasn't had their issue resolved and do what I suggested.
Now I must lay down. My headache is killing me:crying:
salihk. said:
Is there any proper tutorial that i can apply s-off to my phone ? Does the hboot version differ this process?
Sent from my HTC EVO 3D X515m using xda app-developers app
Click to expand...
Click to collapse
This video. is what I used. And for the wire. I just used a piece of small copper wire with rubber on it. But it's the most informative video I've seen.
I had this problem as well.
Ultimately, the solution was to downgrade to hboot 1.49.0007 (from 1.57.xxxx).
Hello
My Evo 3d is S-ON with 1.490018 Hboot, i was running Mwakious V10 with anryl Kernel. Everything went well but after playing with rom toolbox i crashed my phone.
My problem is that i can only flash a GB Rom lik LeeDroid and cant go back to an ICS one.
My phone keeps boot looping even if I flash boot.img from the rom i want to instal after the flash... Bootloops too when trying to flash with for ext ant smartflash on...
Is there something i forget after all this goot time on mwakious rom without touch anything ???
i tryed new makious rom and ioda ics rom and issue is the same...
I have an extra question : I i want to install RUU RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe in order to restard from scratch with a clean official ics rom, do i need to relock the bootloader ?
thank 4 help :cyclops:
Did you at any point update your firmware to the new ics one? if not then do it and try an ics rom. most of the newer ics roms require the new firmware.
http://d-h.st/Mf1
and as for RUU, yes you need to relock before running it. I would recommend you get s-off as its quite easy with your hboot. saves you trouble down the road
EM|NEM said:
Did you at any point update your firmware to the new ics one? if not then do it and try an ics rom. most of the newer ics roms require the new firmware.
http://d-h.st/Mf1
and as for RUU, yes you need to relock before running it. I would recommend you get s-off as its quite easy with your hboot. saves you trouble down the road
Click to expand...
Click to collapse
Hello,
you confirmed my thoughts about firmware as i can only run old releases of ics roms, for example i was used to have the mwakious one V11 with boot.omg from V7, but for now i deleted my backups and files are not avaliable on mwakious thread :crying:
i cannot update firmware as i am s-on, right ? is see this seems to work on recent hboot : http://forum.xda-developers.com/showthread.php?t=1796625 but don't know if it will work with 1.49.0018 (I must read the full thread before asking .
I tryed to do the wire trick from http://forum.xda-developers.com/showthread.php?t=1743466 but did not work even with help of another member...
that's why i wanted to flash an ics ruu to begin update all and begin from scratch... but after relocked the bootloader phone won't boot to android so ruu doesn't work
as the wire trick did not work i want to try to downgrade with Free3Vo tool (sorry i don't remeber the thread) or this method http://forum.xda-developers.com/showthread.php?t=1471246 ....
tarassor said:
Hello,
you confirmed my thoughts about firmware as i can only run old releases of ics roms, for example i was used to have the mwakious one V11 with boot.omg from V7, but for now i deleted my backups and files are not avaliable on mwakious thread :crying:
i cannot update firmware as i am s-on, right ? is see this seems to work on recent hboot : http://forum.xda-developers.com/showthread.php?t=1796625 but don't know if it will work with 1.49.0018 (I must read the full thread before asking .
I tryed to do the wire trick from http://forum.xda-developers.com/showthread.php?t=1743466 but did not work even with help of another member...
that's why i wanted to flash an ics ruu to begin update all and begin from scratch... but after relocked the bootloader phone won't boot to android so ruu doesn't work
as the wire trick did not work i want to try to downgrade with Free3Vo tool (sorry i don't remeber the thread) or this method http://forum.xda-developers.com/showthread.php?t=1471246 ....
Click to expand...
Click to collapse
If nothing works for you then Relock the bootloader -> again boot into bootloader -> select fastboot -> connect to PC (phone should show "fastboot USB") -> then RUN RUU.exe.
RUU works even when phone is in "fastboot USB" mode. Make sure you use the RUU made for your phone/region and the battery is charged enough.
If you would like to attempt the downgrade method then try this
http://forum.xda-developers.com/showthread.php?t=1495657
Worked flawlessly for me. Just make sure you have a valid cid
mnomaanw said:
If nothing is working for you then Relock the bootloader -> again boot into bootloader -> select fastboot -> connect to PC (phone should show "fastboot USB") -> then RUN RUU.exe.
RUU works even when phone is in "fastboot USB" mode. Make sure you use the RUU made for your phone/region and the battery is charged enough.
Click to expand...
Click to collapse
i choose this one, RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
My evo 3d is an unbranded european (CID 203), i will try into fastboot when i have some time to do.. thank for the tips, i will report as soon i try !
EM|NEM said:
If you would like to attempt the downgrade method then try this
http://forum.xda-developers.com/showthread.php?t=1495657
Worked flawlessly for me. Just make sure you have a valid cid
Click to expand...
Click to collapse
i downloded it will see, my CID is 203, have not time today... btw thank you and happy new year
I bought Evo which was already upgraded to ICS (OTA I assume), and it was branded I think. I've unlocked it via HTCDev, flashed '4ext touch recovery' and then rooted. Then I flashed MIUI ICS ROM, and everything is OK for now.
I want to use BootManager to flash multiple ROMs. It requires s-off. I tried it already with s-on, because I've read that SmartFlash (from 4ext recovery) makes my phone like s-off, so ROM on SD card installed, but won't boot. I had many problems going back to my Phone ROM, I restored my backup, wiped many times, installed fresh ROM and still had a bootloop. Finally I got it working again by flashing boot.img via fastboot (glad I did nandroid backup before). I didn't try again with different ROM, because after 2 hours of trying to recover my base ROM I've had enough. So I'm pretty sure BootManager will work better if my phone will be s-off.
So my question is - what to do next? We have so many guides and different comments here, sometimes the same method works for one, and doesn't work for another one, and I'm really confused.
I assume I should follow the instructions here http://forum.xda-developers.com/showthread.php?t=1743466 but I don't understand few things:
friend.evil said:
flash an ICS ROM from recovery(Method B from 10 to 14)
open ICS ROM.zip and extract boot.img to a folder which contains adb, fastboot and AdbWinApi.dll
go to fastboot and type:
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Do I have to do this if I'm already have MIUI with root privileges? Do I still need that boot.img from MIUI, and put it together with fastboot.exe?
Or should I restore stock ICS? I'm pretty sure I did nandroid backup before flashing MIUI.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
Do I need to fix hboot after s-off? What hboot version I have after doing steps 1 to 4 from section E? There's a big zip file (PG86IMG.zip), is it another ROM or what?
And most important question - if method D doesn't work, method F is recommended, but:
elias17 said:
Hboot s on will only flash roms that are based on ics 3.28xx and sense 4 roms using a special boot.img ! U can never flash GB roms until u go s off like i did its a tricky process but it works and now i can flash any rom in the gsm section
Click to expand...
Click to collapse
friend.evil said:
2_flash Leedroid GB ROM from recovery http://leedroid.ftp.rshost.eu/Shoote....zip(Don't forget to wipe data/factory reset and wipe cache + dalvik)
Click to expand...
Click to collapse
I don't get it - can I flash GB ROM or not if I have hboot 1.53.0007 s-on? Can I use method F if method D fail?
Sorry for my english, I'm from Poland.
Thanks in advance for any tip.
You're confusing yourself, What you need to do my friend is.
1. Download RUU, Run RUU
2. HTC Unlock bootloader again
3. Do the Juopunutbear Wiretrick to get s-off
4. Download the 1.04 ENG hboot (There is one of those for the GSM I think... not sure though)
5. Flash a badass Android 4.2.1 rom. They work.
There's much more detailed guides on what to do, BUT This is a summary of what you want.
Be sure to hit thanks [= I'm almost to 100
Which RUU should I search for? GB or ICS?
But isn't the 1+2 the same as restoring my ICS Stock ROM from backup?
I think hboot 1.49.0007 would be enough, I've read that BootManager works well with that version.
1. Yes you can just restore your stock ics backup BUT you will have to root it using the file provided in method B.
2. Yes the 1.49.0007 hboot is best for gsm
3. You can flash a GB rom with your hboot no problem. It just dont think it will boot. so technically you should be able to do the wire trick with a GB rom flashed(not booted into). You'll be in fastboot mode for the wiretrick. There are different files for GB and ICS when doing the wiretrick
Your best bet is to run an ICS RUU, unlock bootloader, root rom, do the wire trick, change hboot to 1.49.0007 and then flash any rom you want
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
mars28 said:
Backup was made right after I made root, is it enough? I just don't want to go through the entire process from the beginning (unlocking, rooting etc).
Click to expand...
Click to collapse
That should work But unlocking again is really easy
You should still have you unlock token in the same place,
You just plug up to the computer hop into fastboot usb and type
Fastboot flash unlocktoken Unlock_Code.bin
to unlock and then
fastboot flash recovery recovery.img
for a recovery,
Then move SU to your sd card and flash it in recovery.
Then your all ready for the wire trick, The more you do these things the more experience you get at them and the better you get with fastboot. I suggest you go through the process opposed to just restoring (First off it's much much safer) and you'll know the ropes if you (or anyone else) has this problem.
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
The token and the unlock code are specific to the phone, And doesn't change until you get a new phone.
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
mars28 said:
Maybe you're right. I'll try with RUU. But I see it's hard to find the correct one these days, some old links died. I have a file called "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed" which I have downloaded right before I started unlocking my Evo, could it be the correct one?
I didn't know I can use old "unlock_code.bin", I saw that everytime I read the token from the device, it was different. So I assumed that I have to flash bin that match the token.
Click to expand...
Click to collapse
you can easily get a new token from htc dev web site
Sent from my HTC EVO 3D X515m using xda app-developers app
Can't_Live_Without_My_Evo said:
And that seems to be the right one, Do you live in Europe? lol Shooter u means GSM and ICS means it's the latest RUU.
Click to expand...
Click to collapse
I know I use shooter_u, I asked because I've found another RUU which have "Rogers_WWE" in name of the file, and the rest of the file name is identical, and I remember that I had to choose "rogers" when I was unlocking via htcdev. That's why I wasn't 100% sure if I had to choose "HTC_Europe" or "Rogers_WWE".
Another thing which confuses me:
http://forum.xda-developers.com/showthread.php?t=1495358
mpgrimm2 said:
Note 3: If you previously did the HTC Unlock, you'd have to "RELOCK" BEFORE running the RUU.
To do this from fastboot type: fastboot oem lock
Click to expand...
Click to collapse
Should I do this or start directly with RUU.exe? My phone is currently "UNLOCKED, hboot 1.53.0007, s-on".
And what about CID? I've read somewhere that I have to change to supercid or something, to be able to flash zips via fastboot. How to check my current CID?
Search for cid getter on play store to get your cid
You certainly need to relock you hboot before running RUU. For the correct ruu you should check the box that your phone came in. It should have the details (atleast i think so)
P.S. you probably don't need to change cid. Infact i'd recommend you not to do that just yet
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
friend.evil said:
12_Notice when you s-off the phone the hboot is corrupted i advice after s-off to follow the methods In E_(from 1 to 4)
Click to expand...
Click to collapse
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
mars28 said:
Got the CID, it's HTC__032. I want to be prepared, who knows what might come up during the whole process.
What means "corrupted"? Phone won't boot or what?
Eeh, if I knew that hboot 1.53.x is so problematic, I would buy Evo with GB on-board.
Click to expand...
Click to collapse
I think yours might be an european model. i had the exact same cid as yours.
when you get to that step of corrupted hboot just follow the steps on this thread and flash hboot 1.49.0007
http://forum.xda-developers.com/showthread.php?t=1906172
Cant kive without my evis comments about the wire trick are bang on. It will fix everything. Having s-off is just much easier so do the wire trick. It will work. My wife and I both have an evo. I had to do the wire trick twice on hers for it to work and four times on mine for it to work. Be patient if it fails the first few times. And if the screen gets stuck on the jounuo whatever screen you can fix that.
If you are stuck at Juopunutbear screen and if you can go to bootloader you need to connect the phone to pc, go to fastboot ( should say fastboot usb)*Go to controlbear folder (from where you ran controlbear to begin withon you pc then open command window in it (hold shift and right click, that willopen command window rigjt there and then*when you get into it you need to enter:
"ControlBear.exe -f" no quotes or "ControlBear f" notice the space after the exe !
Lots of peopke forget to put it in and say it didnt work.
I presume this will fix the problem
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
My phone is now s-off. I didn't flash RUU, just restored stock rooted ROM from backup, did the wire trick (just one time, surprisingly) and everything went nice and smooth. Then I flashed hboot 1.49.0007 with no problems at all. Thanks guys for the tips.
One more thing - my phone state is now "LOCKED" - should I bother?
So I got what I wanted - I've installed ROM in BootManager (the one which doesn't boot before, while phone was 's-on') and this time it booted from SD. Today I'll try more ROMs in BootManager.
Locked doesn't matter as long as you are s-off. It only creates problems if you ever plan on using fastboot commands. Trust me, you dont need to bother with it
But if you really want to know heres a quote from ramjet where he explains it a bit.
ramjet73 said:
Once the RUU.exe is run and the stock bootloader is installed, the phone will be bootloader S-ON regardless of the radio S-OFF status. To run fastboot commands like "flash" and "erase" the stock bootloader needs to be unlocked by the htcdev method or a custom bootloader modified to support those commands needs to be flashed, which requires radio S-OFF.
Click to expand...
Click to collapse
I could not load what i believe is newer (ICS) roms. My phone would restart after the loading screen. so i did the s-off thing and i could now run ics roms.
now. i need to access the # codes. only one of them works. If i try older roms, including the backup from when i first rooted the phone, it gets to sense, then resets after a second or two.
is this because of S-OFF?
how can i undo the S-OFF so i can put my stock rom back on and access the # codes.
thanks for the help
No its not because of s-off.
What is your current hboot version?
What rom are you using now?
And your backup was ICS or Gingerbread?
If you want to boot a Gingerbread ROM you need to be on older hboot.
What is the code that you want to try?
I guess almost all Gingerbread dialer codes should work on sense based ICS rom.
mnomaanw said:
No its not because of s-off.
What is your current hboot version?
What rom are you using now?
And your backup was ICS or Gingerbread?
If you want to boot a Gingerbread ROM you need to be on older hboot.
What is the code that you want to try?
I guess almost all Gingerbread dialer codes should work on sense based ICS rom.
Click to expand...
Click to collapse
hboot is 1.58
iv tried several roms including my original backup.
i believe backup was gingerbread. what the phone came with 2 years ago.
only one of hte codes worked. i dont know which ones specificialy i need
for soem reason they jsut dont work on ics roms
i assumed it was s-off because s-on was what kept me from running ics
What are you trying to do?
birddseedd said:
hboot is 1.58
iv tried several roms including my original backup.
i believe backup was gingerbread. what the phone came with 2 years ago.
only one of hte codes worked. i dont know which ones specificialy i need
for soem reason they jsut dont work on ics roms
i assumed it was s-off because s-on was what kept me from running ics
Click to expand...
Click to collapse
You have hboot 1.58, so you have a Sprint evo 3d.. so you need hboot 1.4 or 1.5 or eng hboot or revolutionary hboot or jb 1.50.5050 to boot you gingerbread backup. Just download and try few of these by renaming them to PG86IMG.zip and installing through bootloader. If the backup is almost 2 year old try revolutionary or 1.40 hboot.
And what recovery are you using now? Back then there was no touch recoveries. Only non touch cwm. So the backup is most likely made from that recovery. I don't know whether your current recovery restores it correctly or not.
And what exactly are you trying to do? Most codes work on Sense based ICS roms.
mnomaanw said:
You have hboot 1.58, so you have a Sprint evo 3d.. so you need hboot 1.4 or 1.5 or eng hboot or revolutionary hboot or jb 1.50.5050 to boot you gingerbread backup. Just download and try few of these by renaming them to PG86IMG.zip and installing through bootloader. If the backup is almost 2 year old try revolutionary or 1.40 hboot.
And what recovery are you using now? Back then there was no touch recoveries. Only non touch cwm. So the backup is most likely made from that recovery. I don't know whether your current recovery restores it correctly or not.
And what exactly are you trying to do? Most codes work on Sense based ICS roms.
Click to expand...
Click to collapse
I dont know exactly which codes. but i know that only one of them worked.
basically i want to downgrade hboot and turn S-ON. i THINK this is what i need to do to run a gingerbread rom and have access to the # codes i need that wouldnt work on multiple ics roms
If you turn back to s-on you won't be able to downgrade.
But with s-off you can upgeade/downgrade anytime.
Your gingerbread rom will boot on s-off. There are many cases of bricked devices while turning s-off to s-on which can be fixed but there's no reason for you to turn it s-on, is there?
i dont know. s-off is what i had to do when i coudl boot gignerbread and not ics, so im under the assumption that to run gingerbread and not ics i need s-on. if this is not the case then all i need to do is go back to hboot 1.4? can you point me in the direction of downgrading please?
birddseedd said:
i dont know. s-off is what i had to do when i coudl boot gignerbread and not ics, so im under the assumption that to run gingerbread and not ics i need s-on. if this is not the case then all i need to do is go back to hboot 1.4? can you point me in the direction of downgrading please?
Click to expand...
Click to collapse
There's a difference between assumption and fact...
When you first did s-off you had a Gingerbread ROM and not ics and it was able to boot.
Currently I am dual booting with one ICS rom and one gingerbread rom and I'm s-off and they both boot perfectly. ON S-OFF GINGERBREAD BOOTS WITHOUT ISSUES.
Download the hboot 1.40.zip from somewhere (cannot attach using phone right now and I'm too lazy to search ramjet73 post ) and rename it to PG86IMG.zip and put it on root of sdcard then reboot into bootloader, let it scan and it will ask to update.. Hit volume up key then power key and it will reboot but before it boots, remove battery as your current ROM is not going to boot on that hboot unless it uses vm kernel. Now remove memory card and delete/rename/move that file from your sdcard using a card reader. Then boot into recovery and restore your backup. Make sure you use the same recovery that you used to make the backup. Only use the HBOOT 1.40 if you have evo 3d from sprint.
.
.
.
If you dont want to do all these download RUU. Exe file made for your phone from shipped-roms.com and run it and follow the instructions, it will get you to stock rom and will unroot your phone. Your phone will be like new with stock recovery but still s-off. You can still flash custom recoveries and ROMs and hboots later.
that site seems to not have an ruu for me
mnomaanw said:
There's a difference between assumption and fact...
When you first did s-off you had a Gingerbread ROM and not ics and it was able to boot.
Currently I am dual booting with one ICS rom and one gingerbread rom and I'm s-off and they both boot perfectly. ON S-OFF GINGERBREAD BOOTS WITHOUT ISSUES.
Download the hboot 1.40.zip from somewhere (cannot attach using phone right now and I'm too lazy to search ramjet73 post ) and rename it to PG86IMG.zip and put it on root of sdcard then reboot into bootloader, let it scan and it will ask to update.. Hit volume up key then power key and it will reboot but before it boots, remove battery as your current ROM is not going to boot on that hboot unless it uses vm kernel. Now remove memory card and delete/rename/move that file from your sdcard using a card reader. Then boot into recovery and restore your backup. Make sure you use the same recovery that you used to make the backup. Only use the HBOOT 1.40 if you have evo 3d from sprint.
.
.
.
If you dont want to do all these download RUU. Exe file made for your phone from shipped-roms.com and run it and follow the instructions, it will get you to stock rom and will unroot your phone. Your phone will be like new with stock recovery but still s-off. You can still flash custom recoveries and ROMs and hboots later.
Click to expand...
Click to collapse
i cannot seem to find an attached zip
birddseedd said:
that site seems to not have an ruu for me
Click to expand...
Click to collapse
Are you sure that you have HTC SHOOTER AKA EVO 3D?
These are RUUs from sprint from 1st to last
1. Gingerbread http://shipped-roms.com/download.ph...0.0518_NV_SPCS_1.15_release_193503_signed.exe
2. Gingerbread http://shipped-roms.com/download.ph...530_NV_NV_SPCS_1.16_release_198109_signed.exe
3. Gingerbread http://shipped-roms.com/download.ph...08_NV_SPCS_1.31_003_release_208230_signed.exe
4. Gingerbread http://shipped-roms.com/download.ph...08_NV_SPCS_1.31_003_release_219445_signed.exe
5. Gingerbread http://shipped-roms.com/download.ph...216_NV_NV_spcs_1.42_release_233304_signed.exe
6. ICS http://shipped-roms.com/download.ph...06__NV_NV_SPCS_1.43_release_271101_signed.exe
These are for sprint evo 3d......And not gsm or virgin.
EDIT : I see you edited it yourself.
yep. that is my phone
ok im confused. i thought that sense and apex were just ui options? i chose sense with a ics rom and now ##3424#. im confsued.
birddseedd said:
ok im confused. i thought that sense and apex were just ui options? i chose sense with a ics rom and now ##3424#. im confsued.
Click to expand...
Click to collapse
yes
raptoro07 said:
yes
Click to expand...
Click to collapse
grr. that doesnt help. lol. so sense vs apex is more than the ui? it is actualy involved in the core of the os? or do each simply have different dialers?
Now, before you start giving me tutorials and links and things of that sort, let me explain my problem. No matter what rom and kernel combo I try, it starts booting and then just bootloops. I already have an idea of what the problem is though. I have 4EXT recovery installed and I unlocked my phone with HTCDev. The thing is tho, when you do it with HTCDev, it stays S-OFF but unlocked. So whenever I install a rom, it fails after the kernel gets installed (And I tried SmartFlash and all of that) I'm on HBOOT 1.57, so I need a way to make it S-OFF so I can install all the jellybean and ICS roms I want. I'm also confused about firmware. Where is that stored and what exactly is it for? (For example, to install the ICS rom, it says I need some file [sprint 2.89 something...]) So I need a step by step guide to how to get it from my point to S-OFF running MIUI or AOKP. Right now I have no ROM (All partitions are wiped)
Shawn9221 said:
Now, before you start giving me tutorials and links and things of that sort, let me explain my problem. No matter what rom and kernel combo I try, it starts booting and then just bootloops. I already have an idea of what the problem is though. I have 4EXT recovery installed and I unlocked my phone with HTCDev. The thing is tho, when you do it with HTCDev, it stays S-OFF but unlocked. So whenever I install a rom, it fails after the kernel gets installed (And I tried SmartFlash and all of that) I'm on HBOOT 1.57, so I need a way to make it S-OFF so I can install all the jellybean and ICS roms I want. I'm also confused about firmware. Where is that stored and what exactly is it for? (For example, to install the ICS rom, it says I need some file [sprint 2.89 something...]) So I need a step by step guide to how to get it from my point to S-OFF running MIUI or AOKP. Right now I have no ROM (All partitions are wiped)
Click to expand...
Click to collapse
You can install all ICS roms with smart flash. Even if you are S-ON and hboot 1.57. For example MIUI v4 forks like a charm on this configuration. I've gained s-off via htcevohacks.com... There are couple of video tutorials and explanations about hacking gsm and cdma evos.. It's simple step by step tutorial, just watch it couple of times so you will know what to expect and need and just follow the guy
freaky deaky said:
You can install all ICS roms with smart flash. Even if you are S-ON and hboot 1.57. For example MIUI v4 forks like a charm on this configuration. I've gained s-off via htcevohacks.com... There are couple of video tutorials and explanations about hacking gsm and cdma evos.. It's simple step by step tutorial, just watch it couple of times so you will know what to expect and need and just follow the guy
Click to expand...
Click to collapse
Well update, I'm now on JuopunutBear's HBoot 1.50 with S-OFF. Still tho, no matter what rom I try to install (I tried MIUI, AOKP Dirty Unicorns, and Cool Rom) The only one I've had success with is Negalite Blurom. I'm still confused
Shawn9221 said:
Well update, I'm now on JuopunutBear's HBoot 1.50 with S-OFF. Still tho, no matter what rom I try to install (I tried MIUI, AOKP Dirty Unicorns, and Cool Rom) The only one I've had success with is Negalite Blurom. I'm still confused
Click to expand...
Click to collapse
With s-off you're fine.. Just copy the pg86img on the sd card and boot into bootloader and hit yes.. It should give you the hboot 1.49.0007...
here is the link to tutorial... http://forum.xda-developers.com/showthread.php?t=1906172
I'm not sure if you have cdma or gsm version. And also I'm not sure if it will work on cdma devices.. Better check it out..
freaky deaky said:
With s-off you're fine.. Just copy the pg86img on the sd card and boot into bootloader and hit yes.. It should give you the hboot 1.49.0007...
here is the link to tutorial... http://forum.xda-developers.com/showthread.php?t=1906172
I'm not sure if you have cdma or gsm version. And also I'm not sure if it will work on cdma devices.. Better check it out..
Click to expand...
Click to collapse
Thanks so much! :laugh: That was only for GSM but I searched for 1.40 HBoot for CDMA. I flashed it and now no more bootloops
Thanks for all of you help.
Shawn9221 said:
Thanks so much! :laugh: That was only for GSM but I searched for 1.40 HBoot for CDMA. I flashed it and now no more bootloops
Thanks for all of you help.
Click to expand...
Click to collapse
I'm glad you managed it.. happy flashing..