Found a copy of HBOOT 1.44 that can still be hit by revone lying around online. Figured this would be useful to anyone who was super paranoid about their phone randomly S-ON'ing.
Download the zip Here and reboot to RUU (fastboot oem rebootRUU)
Flash the zip (fastboot flash zip zipname.zip)
Done.
Edit: You're going to have to edit the android-info.txt to match your device info.
So, basically this gives us s-off people a plan-B if we accidentally do something wrong?
HECK YES!!!!!
I will flash this, then go S-On to protect my sweet sweet phone from bad flashes.
Edit:
Have you actually tried this?
GrayTheWolf said:
So, basically this gives us s-off people a plan-B if we accidentally do something wrong?
F*** YES!!!!!
I will flash this, then go S-On to protect my sweet sweet phone from bad flashes.
Edit:
Have you actually tried this?
Click to expand...
Click to collapse
It flashed no problem. I couldn't get revone to kick to me to S-ON. However whatever it uses to lock/unlock the bootloader works and the hboot version is just 1.44.0000 so I'm assuming its revone'able. Fastboot wouldn't do it either due to hboot signature checks. Do you know another way to get S-ON?
Sonic2756 said:
It flashed no problem. I couldn't get revone to kick to me to S-ON. Fastboot wouldn't do it either due to hboot signature checks. Do you know another way to get S-ON?
Click to expand...
Click to collapse
Oh, that's a problem isn't it?
How would we go about getting back on 1.44 then?
GrayTheWolf said:
Oh, that's a problem isn't it?
How would we go about getting back on 1.44 then?
Click to expand...
Click to collapse
fastboot oem writesecureflag 1 works.
fastboot oem writesecureflag 3 fails due to hboot check.
I'm not sure if revone offers the ability to turn S-ON actually, I'll keep looking into it after my homework is done.
Sonic2756 said:
fastboot oem writesecureflag 1 works.
fastboot oem writesecureflag 3 fails due to hboot check.
I'm not sure if revone offers the ability to turn S-ON actually, I'll keep looking into it after my homework is done.
Click to expand...
Click to collapse
After your homework, go s-on, and then try to s-off again with revone to humor me and make sure it works.
What is the date on that 1.44 iirc anything after july can not be revone'd
GrayTheWolf said:
After your homework, go s-on, and then try to s-off again with revone to humor me and make sure it works.
Click to expand...
Click to collapse
Probably due to my GPE RUU. Gonna flash back to stock and try again.
Kraizk said:
What is the date on that 1.44 iirc anything after july can not be revone'd
Click to expand...
Click to collapse
1.44 as a whole can't be S-Off short of a java card I am pretty sure.
GrayTheWolf said:
1.44 as a whole can't be S-Off short of a java card I am pretty sure.
Click to expand...
Click to collapse
No if it's the one before the newest hboot you need to run revone as su in shell otherwise revone works
Sent from my HTC6500LVW using xda app-developers app
123421342 said:
No if it's the one before the newest hboot you need to run revone as su in shell otherwise revone works
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Sorry, I had myself confused.
GrayTheWolf said:
1.44 as a whole can't be S-Off short of a java card I am pretty sure.
Click to expand...
Click to collapse
I'm pretty sure 1.45 is the on that was patched.
Sent from my HTC One
123421342 said:
No if it's the one before the newest hboot you need to run revone as su in shell otherwise revone works
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
This one says May 3, 2013. Also even after flashing back to stock, trying to S-ON with 1.44 flashed, fastboot gives me the hboot verification error.
Eh. Apparently you can't S-ON with even a older stock bootloader. Which is probably good because apparently the phone would have refused to boot with S-ON and 1.44 flashed. Either way I would leave 1.44 flashed as a just in case. Especially since it's not an easy fix if something S-OFF related goes wrong.
Sonic2756 said:
Eh. Apparently you can't S-ON with even a older stock bootloader. Which is probably good because apparently the phone would have refused to boot with S-ON and 1.44 flashed. Either way I would leave 1.44 flashed as a just in case. Especially since it's not an easy fix if something S-OFF related goes wrong.
Click to expand...
Click to collapse
Very nice bro, this will help keep many people feel safer that don't know entirely the full risks involved with S-OFF
Sonic2756 said:
This one says May 3, 2013. Also even after flashing back to stock, trying to S-ON with 1.44 flashed, fastboot gives me the hboot verification error.
Click to expand...
Click to collapse
So, when I get my phone back with S-Off I should flash this file to downgrade bootloader to 1.44? Do I keep it 1.44 and flash roms as usual? Sorry for the dumb questions... Just don't want to mess up my phone.
lluke04 said:
So, when I get my phone back with S-Off I should flash this file to downgrade bootloader to 1.44? Do I keep it 1.44 and flash roms as usual? Sorry for the dumb questions... Just don't want to mess up my phone.
Click to expand...
Click to collapse
messing with hboot is a perfect way to do just that actually.
wrong hboot file.,
hboot file not downloaded fully (corrupted)
it is (Was) back on the inc4 you'd have a bricked phone with no way to fix it, except maybe jtag
but if Sonic confirms it safe, I'd trust him and just double check that md5
andybones said:
messing with hboot is a perfect way to do just that actually.
wrong hboot file.,
hboot file not downloaded fully (corrupted)
it is (Was) back on the inc4 you'd have a bricked phone with no way to fix it, except maybe jtag
but if Sonic confirms it safe, I'd trust him and just double check that md5
Click to expand...
Click to collapse
Please bare with me... I don't understand what you are say. Is the file Sonic posted HBOOT 1.44 good or bad and should I should I not flash it? I don't want to mess with anything I don't have to. I must have misread his post earlier. I thought he said to be on the safe side flash 1.44.
EDIT:
Originally Posted by Sonic2756 View Post
Eh. Apparently you can't S-ON with even a older stock bootloader. Which is probably good because apparently the phone would have refused to boot with S-ON and 1.44 flashed. Either way I would leave 1.44 flashed as a just in case. Especially since it's not an easy fix if something S-OFF related goes wrong.
lluke04 said:
Please bare with me... I don't understand what you are say. Is the file Sonic posted HBOOT 1.44 good or bad and should I should I not flash it? I don't want to mess with anything I don't have to. I must have misread his post earlier. I thought he said to be on the safe side flash 1.44.
Click to expand...
Click to collapse
I flashed it and everything's fine for me. I never post things without testing them first.
Sent from my M7 using XDA Premium 4 mobile app
Sonic2756 said:
I flashed it and everything's fine for me. I never post things without testing them first.
Sent from my M7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply. I figured you wouldn't. I am just new and don't want to mess up my phone.
Related
Hey all.
I am not ready to turn s-off yet. But I want to upgrade my radio.
The problem is when I try and use the same pg3img file I used to go to stock when I first went to 2.05 it tells me "main is older. Update failed"
And then I have to reboot.
So does anyone know what I am doing wrong. Do I need another pg3img file (can they only be used once?)
Or did I just mess something up?
Any help appreciated.
Sent from my ADR6300 using XDA App
Mean Sixteen said:
Hey all.
I am not ready to turn s-off yet. But I want to upgrade my radio.
The problem is when I try and use the same pg3img file I used to go to stock when I first went to 2.05 it tells me "main is older. Update failed"
And then I have to reboot.
So does anyone know what I am doing wrong. Do I need another pg3img file (can they only be used once?)
Or did I just mess something up?
Any help appreciated.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
from what i understand you need to have s-off to flash to 2.15
wowthatisrandom said:
from what i understand you need to have s-off to flash to 2.15
Click to expand...
Click to collapse
Correct. The whole process of flashing the 2.15 radio depends on the signature checking system within the bootloader to be disabled.
Thanks to both of you.
I didn't know this was the case.
Guess I will have to seriously consider turning s-off.
Sent from my ADR6300 using XDA App
It's easy as pie. If your inc has clockwork mod it can seriously be done in less than five minutes, along with that you can flash a stock recovery in case you have to return the phone.
Sent from my ADR6300 using XDA App
s-off, 2.15 radio, skyrider 2.2 = all within 15mins or less i think.
I may have to exchange my phone is why I am hesitating on the s-off.
I understand once that is done I can never truly go back to stock. At least not s-on anyway.
Sent from my ADR6300 using XDA App
Mean Sixteen said:
I may have to exchange my phone is why I am hesitating on the s-off.
I understand once that is done I can never truly go back to stock. At least not s-on anyway.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
You think the verizon guys are gonna find out if the flag is s-off or s-on?.. NO WAY!!..
As long as it boots and there is no water damage/screen damage.. you could be on Froyo for all they care!
The pbing file wont work because it consists of an older radio and hboot. The phone wont let you downgrade your radio unless you have NAND unlocked and S-off. The only way to get the 2.15 radio i think is to have S-off. Hope this helps
mikeacela said:
The pbing file wont work because it consists of an older radio and hboot. The phone wont let you downgrade your radio unless you have NAND unlocked and S-off. The only way to get the 2.15 radio i think is to have S-off. Hope this helps
Click to expand...
Click to collapse
It actually doesn't work because the zip isn't signed with the correct signatures, so HBOOT won't flash it.
I tried to root my husbands htc evo phone but it was interrupted and was not able to try again. He was able to update the software when sprint sent it out but somehow when I went into his bootloader it has S-OFF. I need to return the phone to sprint. Is there any way I can turn S-ON again?
How were u trying to root? Which process?
Taking my experience into account:
Ive been rooted with unrEVOked...and unrooted using the Stock RUU zip. BUT....prior to that...S-on needs to be recovered. The process in which Ive used was following the enclosed link.
Hope it helps...good luck.
http://forum.xda-developers.com/showthread.php?t=780141
tgeigel said:
I tried to root my husbands htc evo phone but it was interrupted and was not able to try again. He was able to update the software when sprint sent it out but somehow when I went into his bootloader it has S-OFF. I need to return the phone to sprint. Is there any way I can turn S-ON again?
Click to expand...
Click to collapse
If it is S-OFF, just run a stock RUU EXE file... 3.70 seems to work just fine. it will return the device to complete stock, including the bootloader for 3.70 release/ship.
The only way to get s-off to s-on is to flash the unrevoked s-on tool. You can run the RUU all you want and return the partitions to stock, s will still remain off. Well it should anyhow, strange things happen sometimes...
That link in the second post gives you both. Flash s-on then flash the RUU, dont go the other way around...
I was rooting using unrevoked but somehow it got interrupted and didn't finish the process. This was before he update his phone
Even though the phone has the updated software?
Sent from my PC36100 using XDA App
tgeigel said:
I was rooting using unrevoked but somehow it got interrupted and didn't finish the process. This was before he update his phone
Even though the phone has the updated software?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Is the phone stock currently? If so just flash the s-on tool, it should work (though I havent heard anyone attempting this yet). If you need to return partitions to stock or an older version of android then run the RUU.
also PM a Mod and ask them to move this to Q please, only post developed work in the DEVELOPMENT section...
tgeigel said:
I was rooting using unrevoked but somehow it got interrupted and didn't finish the process. This was before he update his phone
Even though the phone has the updated software?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Did the update change the Hboot version from 2.10 to 2.16?
Power off the phone, hold Vol Down and Power and wait for Bootloader to run to see which version is on the device.
evomattnc said:
The only way to get s-off to s-on is to flash the unrevoked s-on tool. You can run the RUU all you want and return the partitions to stock, s will still remain off. Well it should anyhow, strange things happen sometimes...
That link in the second post gives you both. Flash s-on then flash the RUU, dont go the other way around...
Click to expand...
Click to collapse
This is wrong. I was S-OFF since June of 2010 when I bought it and rooted, I just recently had to return my device and get it swapped. I simply ran the RUU Exe, I then made sure to check because I didn't want to return it with S-OFF, and it was S-ON. I didn't run any S-ON Tool or anything else other than the RUU Exe.
Unknownforce said:
This is wrong. I was S-OFF since June of 2010 when I bought it and rooted, I just recently had to return my device and get it swapped. I simply ran the RUU Exe, I then made sure to check because I didn't want to return it with S-OFF, and it was S-ON. I didn't run any S-ON Tool or anything else other than the RUU Exe.
Click to expand...
Click to collapse
Thanks. Plz move this thread to QA sorry I posted in the wrong thread.
Sent from my PC36100 using XDA App
I tried to run the s-on tool but it says unsupported radio and it aborts
Sent from my PG86100 using XDA Premium App
Had the same problem so i just downgraded the radio but i need help because i turned s-on before installing stock rom and now i dont have a rom at all installed and i need to get it back to stock by today :0
BLiizz said:
Had the same problem so i just downgraded the radio but i need help because i turned s-on before installing stock rom and now i dont have a rom at all installed and i need to get it back to stock by today :0
Click to expand...
Click to collapse
You tried just resetting the phone? Like a data factory reset.
Sent from my PC36100 using XDA App
Run the ruu now...
BLiizz said:
Had the same problem so i just downgraded the radio but i need help because i turned s-on before installing stock rom and now i dont have a rom at all installed and i need to get it back to stock by today :0
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
You get yours fixed t geigel?
tgeigel said:
You tried just resetting the phone? Like a data factory reset.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Youre wrong...unless you upgraded your hboot with the ruu. We usually use the ruu for your hboot...I need you to talk less now...
Unknownforce said:
This is wrong. I was S-OFF since June of 2010 when I bought it and rooted, I just recently had to return my device and get it swapped. I simply ran the RUU Exe, I then made sure to check because I didn't want to return it with S-OFF, and it was S-ON. I didn't run any S-ON Tool or anything else other than the RUU Exe.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
evomattnc said:
You get yours fixed t geigel?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
No my computer was not reading my phone properly and it wasn't downloading the driver either. So I just decided to send the phone back to sprint with the s-off. I ran the ruu and it didn't connect to my phone
Sent from my PC36100 using XDA App
ok so i have my s-on and i ran the pc36img and my phone is still rooted am i doing something wrong i need to take it back to the store so i can get my 3d today
I have run the stock ruu on my phone and it unrooted and was back to S-on with no problem.
evomattnc said:
Youre wrong...unless you upgraded your hboot with the ruu. We usually use the ruu for your hboot...I need you to talk less now...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
"Hell I don't know anymore"
Unknownforce said:
This is wrong. I was S-OFF since June of 2010 when I bought it and rooted, I just recently had to return my device and get it swapped. I simply ran the RUU Exe, I then made sure to check because I didn't want to return it with S-OFF, and it was S-ON. I didn't run any S-ON Tool or anything else other than the RUU Exe.
Click to expand...
Click to collapse
The reason yours switched to s-on is because the root method you used included the ENG bootloader. If the root method included unrevoked forever then the only way to achieve s-on is with the s-on tool. So no, he wasn't wrong he could have been more thorough in his explination that's all.
Sent from my PC36100 using XDA Premium App
Is there a way to root in bootloader? Thanks.
Fairly certain i told you this before, but for gingerbread, go to revolutionary.io, install the driver, boot into the bootloader, connect as fastboot, follow the instructions.
teh roxxorz said:
Fairly certain i told you this before, but for gingerbread, go to revolutionary.io, install the driver, boot into the bootloader, connect as fastboot, follow the instructions.
Click to expand...
Click to collapse
It's not working says waiting for device. I'm stuck in bootloop and i flashed s on to try to go back to stok that didn't work either so I wanna s off again and try something else is there a root PC36IMG file I can use I searched and didn't find anything? Thanks.
jcthelight said:
It's not working says waiting for device. I'm stuck in bootloop and i flashed s on to try to go back to stok that didn't work either so I wanna s off again and try something else is there a root PC36IMG file I can use I searched and didn't find anything? Thanks.
Click to expand...
Click to collapse
No that type of PC36IMG won't work. Are you sure you have the revoultionary.io drivers installed?
Pretty sure you need Usb debugging on when you have it plugged in for revolutionary to read it
Sent from my PC36100 using XDA App
evo4gnoob said:
Pretty sure you need Usb debugging on when you have it plugged in for revolutionary to read it
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yup! I used it to root then PC36IMG to unroot when the white screen of death came upon me.
evo4gnoob said:
Pretty sure you need Usb debugging on when you have it plugged in for revolutionary to read it
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That's correct, though he can't get into the os because he bootloops. I'd say flash a new boot.img via fastboot, but he's having trouble getting the device to read.
teh roxxorz said:
That's correct, though he can't get into the os because he bootloops. I'd say flash a new boot.img via fastboot, but he's having trouble getting the device to read.
Click to expand...
Click to collapse
Yup and I tried to flash boot.img but says something about signature failed my hboot ver. is 0.79.0000 radio 1.39.00.04.26 if that helps at all.
jcthelight said:
Yup and I tried to flash boot.img but says something about signature failed my hboot ver. is 0.79.0000 radio 1.39.00.04.26 if that helps at all.
Click to expand...
Click to collapse
Did you root with unrevoked?
Sent from my PC36100 using XDA App
evo4gnoob said:
Did you root with unrevoked?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Revolutionary but then urooted with a PC36IMG file.
jcthelight said:
Yup and I tried to flash boot.img but says something about signature failed my hboot ver. is 0.79.0000 radio 1.39.00.04.26 if that helps at all.
Click to expand...
Click to collapse
I still think its a driver issue. Double check you have the revolutionary drivers installed.
teh roxxorz said:
I still think its a driver issue. Double check you have the revolutionary drivers installed.
Click to expand...
Click to collapse
I'm pretty sure I have them installed cause when i click the revolutionary box it opens and says waiting for device.
jcthelight said:
I'm pretty sure I have them installed cause when i click the revolutionary box it opens and says waiting for device.
Click to expand...
Click to collapse
He's talking about the HTC drivers
Sent from my PC36100 using XDA App
evo4gnoob said:
He's talking about the HTC drivers
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes I looked in device manager when the phone is plugged in and HTC is there.
Try this PC36IMG file on your SD card
http://goo-inside.me/supersonic/ruu...15.00.11.19_NV_1.90_release_161482_signed.zip
It won't root your phone, but might get rid of the bootloop.
shortydoggg said:
Try this PC36IMG file on your SD card
http://goo-inside.me/supersonic/ruu...15.00.11.19_NV_1.90_release_161482_signed.zip
It won't root your phone, but might get rid of the bootloop.
Click to expand...
Click to collapse
Ok hboot update.
it is a ruu file that you run from your pc to go back to stock "just out of the box". it may get rid of your issues. Thats the first thing I would try. dont worry about s-on or s-off and all that...just run it.
jcthelight said:
Ok hboot update.
Click to expand...
Click to collapse
So what would you recomend doing now? Thanks.
{ParanoiA} said:
it is a ruu file that you run from your pc to go back to stock "just out of the box". it may get rid of your issues. Thats the first thing I would try. dont worry about s-on or s-off and all that...just run it.
Click to expand...
Click to collapse
I renamed it to PC36IMG and flashed it from my sd card it updated the hboot and still bootlooping and it wasn't an rru file it was a zip file.
Did u flash any voltage lowering scripts like vipermod? Also are u now s-on or s-off? Since you are back to stock now and are still getting reboots, I would say u may be sol. Get it replaced
Sent From My Pocket
Can somebody help me locate a guide for gaining S-OFF after doing the HTC dev unlock? Seems a bit scattered. I have downloaded the RUU for gingerbread and know that I need to relock but I'm also reading that I need to remove CWM? Any help would be appreciated.
Kayak83 said:
Can somebody help me locate a guide for gaining S-OFF after doing the HTC dev unlock? Seems a bit scattered. I have downloaded the RUU for gingerbread and know that I need to relock but I'm also reading that I need to remove CWM? Any help would be appreciated.
Click to expand...
Click to collapse
I'm in the same boat, there's plenty of information out there but it seems scattered.
I read through the Comprehensive S-Off/Root Methods thread and I think it goes like this:
Flash the RUU that's posted in that thread.
Re-lock bootloader (fastboot oem lock).
At this point it's like you're back to stock, correct?
Downgrade hboot if needed using the scripts shown (or does the RUU do this?)
S-off with revolutionary and get clockworkmod flashed.
Flash superuser / a ROM.
My question is: what will be the state of my phone after I flash the RUU listed in that thread? Will I be back to stock recovery? Will I need to downgrade hboot?
roswell_nightlife said:
I'm in the same boat, there's plenty of information out there but it seems scattered.
I read through the Comprehensive S-Off/Root Methods thread and I think it goes like this:
Flash the RUU that's posted in that thread.
Re-lock bootloader (fastboot oem lock).
At this point it's like you're back to stock, correct?
Downgrade hboot if needed using the scripts shown (or does the RUU do this?)
S-off with revolutionary and get clockworkmod flashed.
Flash superuser / a ROM.
My question is: what will be the state of my phone after I flash the RUU listed in that thread? Will I be back to stock recovery? Will I need to downgrade hboot?
Click to expand...
Click to collapse
I think you have to flash the stock recovery first, before the RUU.
Flash the 2.3.3 ruu, make sure you have stock recovery, relock it then use revolutionary to get S-OFF.
Sent from my Incredible 2 using Tapatalk 2
prototype7 said:
Flash the 2.3.3 ruu, make sure you have stock recovery, then use revolutionary to get S-OFF.
Sent from my Incredible 2 using Tapatalk 2
Click to expand...
Click to collapse
Need to downgrade HBOOT before that, right?
Kayak83 said:
Need to downgrade HBOOT before that, right?
Click to expand...
Click to collapse
Just flashing the RUU should be fine, that's all the downgrade tool does.
prototype7 said:
Just flashing the RUU should be fine, that's all the downgrade tool does.
Click to expand...
Click to collapse
I didn't realize that flashing that RUU would leave me with hboot .97, that's pretty cool.
I'm now S-Off, thanks for the help!
roswell_nightlife said:
I didn't realize that flashing that RUU would leave me with hboot .97, that's pretty cool.
I'm now S-Off, thanks for the help!
Click to expand...
Click to collapse
Neither did I lol, just checked the code and saw that's all the downgrade tool really does.
Sent from my Incredible 2 using Tapatalk 2
I was just about to post this thread... glad i searched first.
Guys, how do I flash the RUU?
I've tried renaming it to PG32IMG.zip, but it throws an error stating "wrong zipped image" or something of that sort.
I've tried flashing it through flashboot:
C:\Android>fastboot flash recover recovery_signed.img
sending 'recover' (3746 KB)... OKAY [ 1.144s]
writing 'recover'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.613s
Click to expand...
Click to collapse
Both don't work for me, and I'm out of ideas here.
pco052 said:
Guys, how do I flash the RUU?
I've tried renaming it to PG32IMG.zip, but it throws an error stating "wrong zipped image" or something of that sort.
I've tried flashing it through flashboot:
Both don't work for me, and I'm out of ideas here.
Click to expand...
Click to collapse
What exactly did you do to get there? Are you unlocked? Need more info for us to help you.
Sent from my SCH-I535 using Tapatalk 2
I Am still looking for info on this subject if anyone is still following this thread.
pprice520 said:
I Am still looking for info on this subject if anyone is still following this thread.
Click to expand...
Click to collapse
On what subject? I did just notice the previous poster's issue, they missed the y in recovery... Not sure what you're asking for though.
Sent from my SCH-I535 using Tapatalk 2
prototype7 said:
On what subject? I did just notice the previous poster's issue, they missed the y in recovery... Not sure what you're asking for though.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
thanks for the fast response, but after staying up all night i figured out how to fix my own problem lol I needed help gettin the heck off htcdev unlock so i could run rev like usual to s-off and flash regular roms. another thing you may be able to help with tho. im looking for a "stableish" ICS or JB for my dinc2.
pprice520 said:
thanks for the fast response, but after staying up all night i figured out how to fix my own problem lol I needed help gettin the heck off htcdev unlock so i could run rev like usual to s-off and flash regular roms. another thing you may be able to help with tho. im looking for a "stableish" ICS or JB for my dinc2.
Click to expand...
Click to collapse
Evervolv is good, maybe PAC, idk about sense
Don't have the phone anymore, so can't really say.
Sent from my SCH-I535 using Tapatalk 2
prototype7 said:
Evervolv is good, maybe PAC, idk about sense
Don't have the phone anymore, so can't really say.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
ill look around thanks for trying to help tho
I flashed the tazzpatriot ICS sense ROM with the new 3.0 kernal. Everything runs smoothly & it will only get better when oc is added in.
Sent from my HTC Incredible 2 using xda app-developers app
I updated to Kit Kat this morning. What are the necessary steps for me to gain root? I haven't rooted a phone since my Droid X, so I might be out of the loop on some things. Thanks for any help!!!
So why would you take the update before asking this
Sent from my HTC One VZW using Tapatalk 4
You can still root it. If you go into RUU mode, flash one of the older system RUU's, then get s-off before updating. You pretty much gave yourself a **** ton more steps to do it, but yes, you can.
This link has the info to flash back to an older version - http://forum.xda-developers.com/showthread.php?t=2475216&highlight=s-on
You won't need the s-on / lock part of that, but you will probably need to flash one of those old system images, then use rumrunner to get s-off and unlocked, then you can update to 4.4, then flash a recovery.
Use firewater-soff.com. Use the temp root method.
Sent from my HTC6500LVW using Tapatalk
ccarr313 said:
You can still root it. If you go into RUU mode, flash one of the older system RUU's, then get s-off before updating. You pretty much gave yourself a **** ton more steps to do it, but yes, you can.
This link has the info to flash back to an older version - http://forum.xda-developers.com/showthread.php?t=2475216&highlight=s-on
You won't need the s-on / lock part of that, but you will probably need to flash one of those old system images, then use rumrunner to get s-off and unlocked, then you can update to 4.4, then flash a recovery.
Click to expand...
Click to collapse
If you are s-on hboot will not allow you to flash an older ruu version than you are currently on (downgrade). So that wont work. But as stated in the post above firewater will get you bootloader unlocked and s-off.
cmlusco said:
If you are s-on hboot will not allow you to flash an older ruu version than you are currently on (downgrade). So that wont work. But as stated in the post above firewater will get you bootloader unlocked and s-off.
Click to expand...
Click to collapse
You are totally right, forgot about that feature. Goodluck with firewater. lol
Glad i s-offed and unlocked on original 4.3 lol
I rooted my One yesterday and installed some custom roms...
It was updated to the newest version, so it is possible to root it... easy ^^
disconnecktie said:
Use firewater-soff.com. Use the temp root method.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So Firewater can achieve S-off with completely stock kit kat? I ask because I just sent my One to be repaired (4.3 S-off) but I have this feeling HTC will update me and possibly return me to S-on.
lancasterv3 said:
So Firewater can achieve S-off with completely stock kit kat? I ask because I just sent my One to be repaired (4.3 S-off) but I have this feeling HTC will update me and possibly return me to S-on.
Click to expand...
Click to collapse
It is supposed to work for the newer versions. The worst case scenario is that it won't work.
Sent from my HTC6500LVW using Tapatalk
disconnecktie said:
It is supposed to work for the newer versions. The worst case scenario is that it won't work.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Thanks, from what I have read in the S-Off thread the temp. root has in fact been blocked so I do not think this will work unless I am reading it wrong.
lancasterv3 said:
Thanks, from what I have read in the S-Off thread the temp. root has in fact been blocked so I do not think this will work unless I am reading it wrong.
Click to expand...
Click to collapse
Yeah I must have missed that. Lots of off topic stuff in there right now. That sucks. Hopefully I don't have to ever send my phone off for repair.
Sent from my HTC6500LVW using Tapatalk