First off, my question is whether im stuck with hboot 2.09 until they release a RUU, or is there a magical way to downgrade?
Sorry, I've got quite the situation to explain.
I was running 2.13.651.1 rooted stock rom + TWRP 2.3, (had hboot 1.12) but I wanted to bust out the new jellybean update. So, I unrooted and attempted to install but it kept booting into twrp and if I used twrp, it gave me an error of assert failed status 7(couldnt find a cid or something) So i flashed over the stock recovery and attempted to upgrade but it failed with a red triangle(!). I then figured it was because it was upset about the build, so I RUU'd down to 1.13.651.1 and the updates worked great. I stopped at 2.13.651.1 and was going to dirtyracun to s-off but i first decided to test the jellybean update. Well I soon realized that i had really screwed up because now Im stuck with hboot 2.09, and there doesnt appear to be anyway to flash an older version. Am i mistaken ?
Its pretty messed up right now. bootloops into the bootloader when its relocked, and carries a security warning. But if i unlock it, it boots up to the os fine.
Also, I noticed that if I try and use the 1.13 RUU , while its unlocked ( i know it doesnt work) , it detects that the firmware version is 2.13. However, if i start the ruu from the bootloader, it detects the firmware as 3.15.. interesting. I wasnt sure if the hboot was skewing the version detection or not.
If any of you geniuses can provide any shed of light, please do.
-Thanks.
P.S , I have a android backup from twrp, but it cant seem to boot after and it fails to mount the sdcard ? When it did complete successfully(once), it wouldnt boot, the screen went black. Even a factory reset didnt seem to fix it, but for some reason it works now if unlocked.
Jessman123 said:
First off, my question is whether im stuck with hboot 2.09 until they release a RUU, or is there a magical way to downgrade?
Sorry, I've got quite the situation to explain.
I was running 2.13.651.1 rooted stock rom + TWRP 2.3, (had hboot 1.12) but I wanted to bust out the new jellybean update. So, I unrooted and attempted to install but it kept booting into twrp and if I used twrp, it gave me an error of assert failed status 7(couldnt find a cid or something) So i flashed over the stock recovery and attempted to upgrade but it failed with a red triangle(!). I then figured it was because it was upset about the build, so I RUU'd down to 1.13.651.1 and the updates worked great. I stopped at 2.13.651.1 and was going to dirtyracun to s-off but i first decided to test the jellybean update. Well I soon realized that i had really screwed up because now Im stuck with hboot 2.09, and there doesnt appear to be anyway to flash an older version. Am i mistaken ?
Its pretty messed up right now. bootloops into the bootloader when its relocked, and carries a security warning. But if i unlock it, it boots up to the os fine.
Also, I noticed that if I try and use the 1.13 RUU , while its unlocked ( i know it doesnt work) , it detects that the firmware version is 2.13. However, if i start the ruu from the bootloader, it detects the firmware as 3.15.. interesting. I wasnt sure if the hboot was skewing the version detection or not.
If any of you geniuses can provide any shed of light, please do.
-Thanks.
P.S , I have a android backup from twrp, but it cant seem to boot after and it fails to mount the sdcard ? When it did complete successfully(once), it wouldnt boot, the screen went black. Even a factory reset didnt seem to fix it, but for some reason it works now if unlocked.
Click to expand...
Click to collapse
yes, i am sorry to say that you are stuck with hboot 2.09.
tekno4ever said:
yes, i am sorry to say that you are stuck with hboot 2.09.
Click to expand...
Click to collapse
Dang. Well , thanks. Nice to know. Does it take them very long to make a RUU ?
Jessman123 said:
Dang. Well , thanks. Nice to know. Does it take them very long to make a RUU ?
Click to expand...
Click to collapse
not sure, but i know its coming down the pipe.
Same here
***Tampered***
***Relocked***
Jewel PVT Ship S-Off Rl
CID-SPCS_001
HBoot-2.09.0000
Radio-1.12.11.1119
OpebDSP-V31.1.0.45.0815
eMMC-boot
Oct 18 2012
So far after having the dirty racun take the tamper away when i was @ HBoot 1.12. But being stupid i downloaded the full zip PJ with recovery etc.
I was also panicking.
So here is the deal
The phone is now relocked and has stock recovery which is useless.
What i did was the following.
download the latest recovery file. Open the cmnd window and follow the instructions of how to unlock the bootloader. after you have unlocked the bootloader, restart, and go back into bootloader, it should say unlocked. now in fastboot usb run the (flash) the recovery. Reboot. Then install the rom...
if you need help let me know... but as of now we are stuck with the ***TAMPERED*** ***UNLOCKED**** until someone does a RUU
Jessman123 said:
Dang. Well , thanks. Nice to know. Does it take them very long to make a RUU ?
Click to expand...
Click to collapse
Are you familiar with linux os? A few of us on here a couple months ago worked on a way to downgrade from 1.15 and 1.19 to 1.12. If you're up for it, I believe I have something that may help you. But it can get very in depth if you don't do it correctly.
Sent from my Jelly Bean'd EVO LTE
Look at your bootloader. Its s-off. Flash your favorite recovery and then your favorite Rom. Or wait for the newest ruu
You should still be s-off so your hboot shouldn't matter too much
Sent from my EVO using xda premium
Well, I was able to get it to re-install my backup successfully. So I am now back where I started before my tampering, just with hboot 2.09. Its fully functional now, I was just eager to get Jellybean .
There is something I've never understood. I *thought* I had unlocked my bootloader when I first got my phone by using HTC's instructions. When I used theirs, it shows Unlocked, however, right below it states S-ON still. I am able to flash whatever I want when it says unlocked, so I assumed it had done its job. But I wasn't sure, so this is why I was going to do the Dirty Racun in the first place.
My goal was simply to achieve the update but keep my precious root, and with all my things left untouched like the typical OTA.
@EVOMIKE025 - I haven't had much time to play directly with Linux, but I have dealt with other Linux devices, so I'm sure I might be competent enough to handle your secrets, but there is only one way to find out! However, I'm kinda nervous of messing with the phone without a RUU available right now. I just couldn't get the OTA to function, and I think it was because of TWRP getting in the way of its reboot. If I have to bite the bullet and re-install everything and my root access, I may do it. I haven't had much time though, this all happened on a sunny day with spare time. Unfortunately a simple upgrade turned into this.
EVOMIKE025 said:
Are you familiar with linux os? A few of us on here a couple months ago worked on a way to downgrade from 1.15 and 1.19 to 1.12. If you're up for it, I believe I have something that may help you. But it can get very in depth if you don't do it correctly.
Sent from my Jelly Bean'd EVO LTE
Click to expand...
Click to collapse
how did you unlock 2.09 hboot with s-off? I accidently hit the install and couldnt stop it from rebooting and installing persistently. Didnt want to brick the phone so i let it go. Now im "dev rooted" and i cant do ****. Can you help me out?
how did you unlock 2.09 hboot with s-off? I accidently hit the install and couldnt stop it from rebooting and installing persistently. Didnt want to brick the phone so i let it go. Now im "dev rooted" and i cant do ****. Can you help me out?
Click to expand...
Click to collapse
Personally, when I wanted to re-lock it, I used "fastboot flash oem-lock" and when I wanted to unlock it again, I flashed the "Unlock_Code.bin" back over that I got from the HTC Dev. That's how i was able to flop around on the locking and re-locking. Don't know if that helps? :fingers-crossed:
guess I'm stuck!
Ok. First time to post so go easy! I got mine unlocked, 2.09. But unable to root. I guess that's the deal till someone comes out with an ruu??
My phone says unlocked, S-on.
It will not load the twrp recovery. IDK if it is me or just not available. The phone is working fine. So I will roll with it but would love some insight!
bradhary said:
Ok. First time to post so go easy! I got mine unlocked, 2.09. But unable to root. I guess that's the deal till someone comes out with an ruu??
My phone says unlocked, S-on.
It will not load the twrp recovery. IDK if it is me or just not available. The phone is working fine. So I will roll with it but would love some insight!
Click to expand...
Click to collapse
Unless I've misunderstood android the last 3yrs, RUU has nothing to do with root. (Unless I'm misinterpreting your meaning in 1st paragraph. where it seems you're associating the 2). RUU will not help with root.
Once you're unlocked thru HTC dev, you can fastboot flash custom recovery (TWRP). With custom recovery installed, you can flash superuser (root) binaries and install superuser or superSU.
Check the thread in development by regaw_lienad for more info and file links. Or you can Google chainsDD superuser for his website with the binaries zip (while I'm at it, wow, all us android users have a lot of thanking to do to chainsDD).
Sent from my EVO using xda premium
bradhary said:
Ok. First time to post so go easy! I got mine unlocked, 2.09. But unable to root. I guess that's the deal till someone comes out with an ruu??
My phone says unlocked, S-on.
It will not load the twrp recovery. IDK if it is me or just not available. The phone is working fine. So I will roll with it but would love some insight!
Click to expand...
Click to collapse
Everything you need to flash recovery and SU is here
Thank you
bigdaddy619 said:
Everything you need to flash recovery and SU is here
Click to expand...
Click to collapse
Got it done! Thanks to all! Especially you my friend, hope I don't leave anyone out! Should I update the superSu? I clicked on it to see if it would open and it did, just asked iff I wanted to update..I really don't want to mess it up allready!
Thanks again, Brad.
PS, It was the new 2.3.3.0 that did it!
SU binary needs to be updated. continue?
bradhary said:
Got it done! Thanks to all! Especially you my friend, hope I don't leave anyone out! Should I update the superSu? I clicked on it to see if it would open and it did, just asked iff I wanted to update..I really don't want to mess it up allready!
Thanks again, Brad.
PS, It was the new 2.3.3.0 that did it!
Click to expand...
Click to collapse
when I hit continue, my phone just does a reboot... Any one..
I think I got it???
Sorry to be a pain! And sorry to the OP for hijacking! Got the wifi to work, phone says it's rooted but the supersu is still out of date and will reboot if I try to update. If anyone has any ideas as to what I could try next, thank you in advance! I will roll like it is as it seems to be working. :good:
bradhary said:
when I hit continue, my phone just does a reboot... Any one..
Click to expand...
Click to collapse
The reboot when updating super user binaries is a known issue introduced in hboot 2.09.....its basically HTC messing with the developers' capabilities of customizing etc....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.pocketables.com/2012/12/...rs.html?utm_source=dlvr.it&utm_medium=twitter
Sent from my EVO using xda app-developers app
EVOMIKE025 said:
Are you familiar with linux os? A few of us on here a couple months ago worked on a way to downgrade from 1.15 and 1.19 to 1.12. If you're up for it, I believe I have something that may help you. But it can get very in depth if you don't do it correctly.
Sent from my Jelly Bean'd EVO LTE
Click to expand...
Click to collapse
Downgrading the bootloader is one of the few ways to make your phone completely, unusably bricked right? If anyone has a way to downgrade 2.09 to 1.19 SAFELY AND WITHOUT MAKING THE PHONE A PERMANENT PAPERWEIGHT or and preferably, not to mention unlikely, s-off 2.0.9, please share and I will be more pleased than a person who won a million bucks.
got it done!
Thanks to everyone I figured it out! I reflashed with the newer superSu, 3.2. all is good, shows good root, backed up and ready to start geeking!
Related
Be warned, if you unlock with HTC's method and you don't have s-off already, you will be able to load roms but NOT KERNELS at all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my PG86100 using Tapatalk
What kernels have you tried? Maybe it just won't work all custom ones are currently based on the old kernel (ie not downgrade). Have you tried flashing freeza's 2.3.4 kernel with ciq removed?
novanosis85 said:
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
LMAO too funny.
mwalt2 said:
What kernels have you tried? Maybe it just won't work all custom ones are currently based on the old kernel (ie not downgrade). Have you tried flashing freeza's 2.3.4 kernel with ciq removed?
Click to expand...
Click to collapse
I tried freeza's kernel on a phone that was unlocked via HTC unlock. Doesnt take.. And you know how when you flash kernels it usually takes like 10 seconds to flash? It takes a couple of minutes to flash. Even if you install a rom when it gets to install the boot.img it hangs longer than it takes to install /system
Same thing that is happening with the recoveries(except that one older version on cwm) they appear to flash fine but the changes do not really take
graffixnyc said:
I tried freeza's kernel on a phone that was unlocked via HTC unlock. Doesnt take.. And you know how when you flash kernels it usually takes like 10 seconds to flash? It takes a couple of minutes to flash. Even if you install a rom when it gets to install the boot.img it hangs longer than it takes to install /system
Click to expand...
Click to collapse
Who in their right mind would choose HTC's unlock method, over Revolutionary? If they did choose HTC's unlocking method, then their pretty stupid and they shouldn't be flashing roms in the first place.
I mean, come-on. Revolutionary gave us an exploit to get s-off and root with the users in mind. HTC gave us the unlocking method with HTC in mind. So if you chose HTC, when we have Revolutionary, you deserve whatever you get. IMHO
Sent from my PG86100 using XDA Premium App
sniperkill said:
Who in their right mind would choose HTC's unlock method, over Revolutionary? If they did choose HTC's unlocking method, then their pretty stupid and they shouldn't be flashing roms in the first place.
I mean, come-on. Revolutionary gave us an exploit to get s-off and root with the users in mind. HTC gave us the unlocking method with HTC in mind. So if you chose HTC, when we have Revolutionary, you deserve whatever you get. IMHO
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
I did the HTC unlock on my buddy's phone Just to be the guinea pig Plus he doesnt have a clue about flashing or anything like that (that's why he gave his phone to me to set up for) My phone thank god was s-offed using revolutionary.
I'm going to try to hold on to his phone for as long as I can because me and Haus_ have been trying to figure out what we can do to unlock it. We've also been bouncing ideas around with IEF..
sniperkill said:
Who in their right mind would choose HTC's unlock method, over Revolutionary? If they did choose HTC's unlocking method, then their pretty stupid and they shouldn't be flashing roms in the first place.
I mean, come-on. Revolutionary gave us an exploit to get s-off and root with the users in mind. HTC gave us the unlocking method with HTC in mind. So if you chose HTC, when we have Revolutionary, you deserve whatever you get. IMHO
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Class A **** response there.
There many reasons to go through it. One being if you didn't have the choice and ur phone had the OTA already applied. The other being for dev purposes and to see what all it actually does so we can get a idea about it.
sgt. slaughter said:
Class A **** response there.
There many reasons to go through it. One being if you didn't have the choice and ur phone had the OTA already applied. The other being for dev purposes and to see what all it actually does so we can get a idea about it.
Click to expand...
Click to collapse
Well said
Sent from my PC36100 using XDA Premium App
Someone please delete this thread as what is stated in the original post is totally false. The stock kernal with CIQ removed does indeed work, no other custom 2.3.3 Kernals will work with 2.3.4 because the framework is different.
Edit: Not to mention once an unofficial exploit is available, I am positive it can be ran on top of the HTC Unlock to give you S-OFF.
My EVO 3D is HTC Unlocked.
novanosis85 said:
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Rem3Dy said:
Well said
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Correcto mundo on the **** answer.
And yes, I'm new here, but it doesn't mean I did my search. Read many guides how to use HTC unlock here, and all of there where "so revolutionary isn't needed anymore" "you can install roms with htc method" bla bla bla, but none of them say you can't install kernels. So I just posted this as a warning for other newbies.
And yes, as the other guy, I did try the stock modified new kernel, and nope, doesn't take it. Appears HTC has put some kind of lock to the kernel.
Yup... I can confirm this too. I updated my phone via ota, then proceeded to the htc unlock page. (should have read xda first) Bootloader unlock was very easy, and cwm installed fine. after cwm installed I noticed wifi reads error after you try to turn on. Nothing besides the initial cwm flashed via bootloader, and kernels do not flash in cwm. Now im pissed, n feel like a dumbass. Thanks HTC. Well... Im gonna try to get the phone covered under an insurance claim. With a new phone, I cant say I will make the same mistake twice...
Cant you just relock the phone via the HTC method and use a revolutionary method once its relocked?
ssconceptz said:
Someone please delete this thread as what is stated in the original post is totally false. The stock kernal with CIQ removed does indeed work, no other custom 2.3.3 Kernals will work with 2.3.4 because the framework is different.
Edit: Not to mention once an unofficial exploit is available, I am positive it can be ran on top of the HTC Unlock to give you S-OFF.
My EVO 3D is HTC Unlocked.
Click to expand...
Click to collapse
Can you post screen shots of you settings kernel version before and after you flashed the kernel? Or are you just saying it worked because you flashed it and nothing broke? I flashed freeza's kernel and my kernel version didn't change at all. Not even the date SMP PREEMPT Fri Aug 5
Plus some of the things it claimed to do at boot didn't happen
I still had data in these after I flashed and booted:
Removes files from /data/system/dropbox ()
-Removes files from /data/system/appusagestats
-Removes files from /data/system/usagestats
These were still all read write:
-Modifies permissions on /data/system/dropbox to read-only
-Modifies permissions on /data/system/appusagestats to read-only
-Modifies permissions on /data/system/usagestats to read-only
All Still had full permissions:
-Removes permissions on /data/system/userbehavior.db
-Removes permissions on /data/system/userbehavior.db
-Removes permissions on /data/system/userbehavior.db-shm
-Removes permissions on /data/system/userbehavior.db-wal
-Removes permissions on /data/system/userbehavior.xml
Plus the fact the kernel takes a few minutes to flash when it should only take the most a few seconds tells you something isnt right. Have you guys tried flashing a kernel by it self? Do you notice it takes a long time to flash? Or when you're flashing a rom watch the progress. Does it hang and take longer to flash the boot image than the system image? that shouldnt be. Something is for sure not taking. I flashed his kernel and nothing broke, but none of his changes he made to it stuck
SPreston2001 said:
Cant you just relock the phone via the HTC method and use a revolutionary method once its relocked?
Click to expand...
Click to collapse
No, you cannot. Revolutionary doesnt support the 1.50 bootloader. In the past we could solve this by downgrading the bootloader. But now HTC built in a bootloader version check. It wont allow you to flash a bootloader with an older version of the current bootloader. We tried changing the mainver in the misc partition and that's how we found that out. Then we tried to flash the RUU with the older 1.40 bootloader we got a "bootloader is older version" IEF from alpharev/revolutionary said "That's a new one" Him and I were on irc the other night trying to figure it out. At first we couldnt even get a RUU to run. That's when I discovered to get a RUU to run you first have to relock the phone(which you could unlock again after)
graffixnyc said:
No, you cannot. Revolutionary doesnt support the 1.50 bootloader. In the past we could solve this by downgrading the bootloader. But now HTC built in a bootloader version check. It wont allow you to flash a bootloader with an older version of the current bootloader. We tried changing the mainver in the misc partition and that's how we found that out. Then we tried to flash the RUU with the older 1.40 bootloader we got a "bootloader is older version" IEF from alpharev/revolutionary said "That's a new one" Him and I were on irc the other night trying to figure it out. At first we couldnt even get a RUU to run. That's when I discovered to get a RUU to run you first have to relock the phone(which you could unlock again after)
Click to expand...
Click to collapse
Ok so would it be best if anyone who used the HTC unlock method to relock the phone via HTC and wait for you guys to come up with a exploit for the 1.50 hboot?
SPreston2001 said:
Ok so would it be best if anyone who used the HTC unlock method to relock the phone via HTC and wait for you guys to come up with a exploit for the 1.50 hboot?
Click to expand...
Click to collapse
you dont have to relock. Just the best bet is to hold off until revolutionary get's it working with the hboot 1.50. Hopefully soon they will figure it out. Or HTC gives us another update that fully unlocks us. I called HTC and started a case about this not fully unlocked nonsense. I told them if I void my warranty I should be able to flash whatever I want on my phone. the rep even did say "well even if you dont, it's your phone you should be able to do what you want with it" He logged my complaint and said they are actually looking for feedback on the bootloader unlock and said he will log the call and escalate it to them. I did ask if this was just a first step and if there would be a further update later and he said it was possible. Since this is the first time they are doing this they will most likely gather the feedback from the users and make the process better. How good my call did? probably not good at all. But I just kept telling the guy.. If I void my warranty I should be able to try to flash whatever I want to my phone, even if melted it and blew it into pieces. The rep for sure agreed with me.
graffixnyc said:
you dont have to relock. Just the best bet is to hold off until revolutionary get's it working with the hboot 1.50. Hopefully soon they will figure it out. Or HTC gives us another update that fully unlocks us. I called HTC and started a case about this not fully unlocked nonsense. I told them if I void my warranty I should be able to flash whatever I want on my phone. the rep even did say "well even if you dont, it's your phone you should be able to do what you want with it" He logged my complaint and said they are actually looking for feedback on the bootloader unlock and said he will log the call and escalate it to them. I did ask if this was just a first step and if there would be a further update later and he said it was possible. Since this is the first time they are doing this they will most likely gather the feedback from the users and make the process better. How good my call did? probably not good at all. But I just kept telling the guy.. If I void my warranty I should be able to try to flash whatever I want to my phone, even if melted it and blew it into pieces. The rep for sure agreed with me.
Click to expand...
Click to collapse
Ok thanks!! I helped my cousin unlock his phone via the HTC method because he didnt feel comfortable doing it alone. We were both surprised to learn that after unlocking the bootloader the phone still had S-On! Now can he still flash a custom rom and become rooted with S-On? Everytime we go into the bootloader and try to go into recovery we get a red triangle with a exclamation point in the middle. Im not sure if something went wrong in the unlocking process but now he just has a unlocked phone thats still not rooted.
SPreston2001 said:
Ok thanks!! I helped my cousin unlock his phone via the HTC method because he didnt feel comfortable doing it alone. We were both surprised to learn that after unlocking the bootloader the phone still had S-On! Now can he still flash a custom rom and become rooted with S-On? Everytime we go into the bootloader and try to go into recovery we get a red triangle with a exclamation point in the middle. Im not sure if something went wrong in the unlocking process but now he just has a unlocked phone thats still not rooted.
Click to expand...
Click to collapse
After you unlock you have to flash recovery. Then you'll be able to flash roms/root. But you can only flash 2.3.4 roms because of the kernel issue
graffixnyc said:
After you unlock you have to flash recovery. Then you'll be able to flash roms/root. But you can only flash 2.3.4 roms because of the kernel issue
Click to expand...
Click to collapse
From what I saw if you use there bootloader unlock you can then use an older RUU image to move back to an old hboot version then you can revolutionary it and get true s-off alot of hoops but you get there
Sent from my PG86100 using XDA App
Unlock Boatloader is officially launched
This is not S-OFF
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://www.htcdev.com/bootloader/unlock-instructions
can anyone confirm this actually gives you S-OFF?
This unlocks my evo 3D but I still have S-ON.
No mention of S-OFF/S-ON. Only unlocking the bootloader (which it does successfully).
If I remember correctly HTC had said this was to be a 2 part process. Could part 2 be here?
Sent from my PG86100 using xda premium
cordell12 said:
If I remember correctly HTC had said this was to be a 2 part process. Could part 2 be here?
Click to expand...
Click to collapse
I'm not sure what the OP was referring to since the bootloader unlocker was open a few days ago. I unlocked my bootloader then and when I followed the link today it sent me to the exact same page.
Like I said, there is no mention of S-ON or S-OFF anywhere. Perhaps the OP can clarify or correct.
Also, I went ahead and went through the process again and it was identical with no S-OFF.
That is Lame, HTC knew exactly what we were talking about back when this all started. To "unlock" the bootloader and keep boot.img locked and S on is a major Fail on HTC!
Unless they come through with part 2...
Sent from my PG86100 using xda premium
I believe part one was the software update that allowed the unlock to be done, part two would be the unlock process they currently do on their website.
foss said:
I'm not sure what the OP was referring to since the bootloader unlocker was open a few days ago. I unlocked my bootloader then and when I followed the link today it sent me to the exact same page.
Like I said, there is no mention of S-ON or S-OFF anywhere. Perhaps the OP can clarify or correct.
Also, I went ahead and went through the process again and it was identical with no S-OFF.
Click to expand...
Click to collapse
I thought S-OFF/S-ON didn't matter with an "unlocked" bootloader. Doesn't unlocking the bootloader essentially remove the signature check, which without a signature check in place it doesnt matter if S is ON of OFF.
I can flash ROMs fine but I thought I couldn't flash a new radio because all of the tutorials state that I need S-OFF to flash radios. No?
No S off no Kernels
mlin said:
I thought S-OFF/S-ON didn't matter with an "unlocked" bootloader. Doesn't unlocking the bootloader essentially remove the signature check, which without a signature check in place it doesnt matter if S is ON of OFF.
Click to expand...
Click to collapse
They unlocked the Sytem and Data partition only with there unlock method. There unlock method does not in any way touch the S-Flag... So if you have s-off you will keep it, if you have s-on you are screwed and will NEVER get s-off unless revolutionary (or the like) do this for us again. I do understand that they may be looking at reverting the 1.5hboo to 1.4 then in turn allow you to use the there tool to obtain S-OFF.
If they would just unlock the boot partition all would be well regardless of S-Flag. Those bastards. So in essence you can flash a custom ROM or even install SU (whatever mods you want) but you wont be flashing a new kernel.
Luckily I had S-OFF and decided to experiment with this and my S-OFF remained and I can flash as I choose.
Steve0007 said:
Unlock Boatloader is officially launched
Click to expand...
Click to collapse
excuse me if im wrong, but isnt this the same thing thats been posted all around here for the past 2 weeks now?
bk718 said:
excuse me if im wrong, but isnt this the same thing thats been posted all around here for the past 2 weeks now?
Click to expand...
Click to collapse
Yep! Seems to be to me.
bk718 said:
excuse me if im wrong, but isnt this the same thing thats been posted all around here for the past 2 weeks now?
Click to expand...
Click to collapse
Sure is!
I wanna add that kernels CAN be flashed with this HTC method. They MUST be flashed with Fastboot though.
So by unlocking the bootloader can you us one of this phones with any service provider? For example I want the EVO 3D but I have Verizon
Sent from my ADR6300 using XDA App
People have been flashing 2.3.4 kernels with a modified ramdisk using fastboot (not recovery) from what I've read. I think people are too quick to judge HTC. They did what they said they would do. I don't think half of the people here even really know the intricacies of unlocked bootloaders and s-off (I certainly don't ). Does s-off even mean anything on non-HTC phones?
I remember people saying how easy it would be to get 'root' since we had an ENG bootloader. They acted like it was a done deal. It certainly took longer than they made it sound like it would and I don't know if alpharev even used the ENG bootloader to get s-off.
cordell12 said:
Sure is!
I wanna add that kernels CAN be flashed with this HTC method. They MUST be flashed with Fastboot though.
Click to expand...
Click to collapse
Are you sure is not Soff before the HTC Method?
mwalt2 said:
People have been flashing 2.3.4 kernels with a modified ramdisk using fastboot (not recovery) from what I've read. I think people are too quick to judge HTC. They did what they said they would do. I don't think half of the people here even really know the intricacies of unlocked bootloaders and s-off (I certainly don't ). Does s-off even mean anything on non-HTC phones?
Click to expand...
Click to collapse
Are you sure they are not S-OFF?
Can you please provide the fastboot command to do this? As well, The people that are flashing the modified kernels like on my ROM using freeza kernel are currently S-OFF if you are S-OFF you can flash modded kernel with hboot 1.5. If you are S-On you cannot. But since you two both say its possible can you please provide a citation or some other sort of proof. I would love to investigate this further! This means a whole new ball game.
EDIT: And yes, I do understand the intricacies of kernels, ROMS, eMMC partitions, etc. I am no expert like the guys at revolutionary or anything even close but I do understand.
And to answer your question about S-OFF on other devices. No such thing. I believe this is just an HTC thing. Im sure other manufactures have there own version of this but I only play with HTC.
I did do some ROM and kernel work on some LG stuff and they did not have any real protection at all. Apply ROOT and flash recovery, that was it. So simple, so easy.
scrosler said:
Are you sure is not Soff before the HTC Method?
Are you sure they are not S-OFF?
Can you please provide the fastboot command to do this? As well, The people that are flashing the modified kernels like on my ROM using freeza kernel are currently S-OFF if you are S-OFF you can flash modded kernel with hboot 1.5. If you are S-On you cannot. But since you two both say its possible can you please provide a citation or some other sort of proof. I would love to investigate this further! This means a whole new ball game.
EDIT: And yes, I do understand the intricacies of kernels, ROMS, eMMC partitions, etc. I am no expert like the guys at revolutionary or anything even close but I do understand.
And to answer your question about S-OFF on other devices. No such thing. I believe this is just an HTC thing. Im sure other manufactures have there own version of this but I only play with HTC.
I did do some ROM and kernel work on some LG stuff and they did not have any real protection at all. Apply ROOT and flash recovery, that was it. So simple, so easy.
Click to expand...
Click to collapse
I think it's fastboot as in using the pg86img.zip. I've just read about it in the general forum and can't test anything since I am s-off.
http://forum.xda-developers.com/showpost.php?p=17101607&postcount=264
mwalt2 said:
I think it's fastboot as in using the pg86img.zip. I've just read about it in the general forum and can't test anything since I am s-off.
http://forum.xda-developers.com/showpost.php?p=17101607&postcount=264
Click to expand...
Click to collapse
I am currently s-on htc unlock method. I have been pulling the boot.img out of the room zip then booting phone into fastboot. With boot.img in same dir as fastboot I use the command fastboot flash boot boot.img. After successful I use the volume buttons to get into recovery and flash the rom. Using md5sum I have tested the kernel partition is changed.
Sent from my PG86100 using Tapatalk
Azrael.arach said:
I am currently s-on htc unlock method. I have been pulling the boot.img out of the room zip then booting phone into fastboot. With boot.img in same dir as fastboot I use the command fastboot flash boot boot.img. After successful I use the volume buttons to get into recovery and flash the rom. Using md5sum I have tested the kernel partition is changed.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
NO ****????
Try this then.... FLash a ROM based on 2.3.3 then flash silverneedle 1.0, overclock and tell me if that works? If you can... If not its cool.
So I had some "help" from a well meaning visiting nephew who was playing with my phone and noticed that I had an update available and decided that I should really have the latest software on my phone...so now I am on 2.17 with hboot 1.5, locked bootloader and all with no custom recovery BUT I am still s-off. I have a NAND backup that is not to old that I did with CWM, but how do I get to that to install it?
I have been looking for several hours and cant seem to find a solution...maybe I'm just searching under the wrong keywords...nevertheless HELP!!!!!!!
I am in the process of downloading a 1.13 stock ruu. Will that work or is there a quicker way to get this done?
I would prefer to avoid HTC unlock if I can, and my understanding is that with s-off, I should be able to.
Thanks for helping bail my ass out guys and girls!
(I thought about it, but no, I didnt beat the kid...his intentions were good...at least they better have been...)
Have you tried flashing a cwm recovery? I think I read someone had the same problem.seens your s-off you should still be able to flash a recovery, and after that's done then you can be able to wipe and flash anything you want, and you well even be able to downgrade your hboot.
Nope, it wont let me flash a recovery through fastboot...access denied (phone shows locked). I cant install it with "flash image gui" because i dont have root.
I know it should be an easy fix because I have the all important s-off...I just cant find how to do it.
taminrob said:
So I had some "help" from a well meaning visiting nephew who was playing with my phone and noticed that I had an update available and decided that I should really have the latest software on my phone...so now I am on 2.17 with hboot 1.5, locked bootloader and all with no custom recovery BUT I am still s-off. I have a NAND backup that is not to old that I did with CWM, but how do I get to that to install it?
I have been looking for several hours and cant seem to find a solution...maybe I'm just searching under the wrong keywords...nevertheless HELP!!!!!!!
I am in the process of downloading a 1.13 stock ruu. Will that work or is there a quicker way to get this done?
I would prefer to avoid HTC unlock if I can, and my understanding is that with s-off, I should be able to.
Thanks for helping bail my ass out guys and girls!
(I thought about it, but no, I didnt beat the kid...his intentions were good...at least they better have been...)
Click to expand...
Click to collapse
S-Off just means that the security is off, and you're able to write onto the boot partition of the phone when flashing a ROM, in one shot. If your Hboot = 1.50, you may have to unlock your bootloader via HTCDEV method, your phone gets wiped. Try HTC SuperTool, maybe it will work, since you're S-Off.
http://forum.xda-developers.com/showthread.php?p=21538250
Follow my post and the links in there should get you back to 1.4
Sent from my HTC Evo 3D using Tapatalk
Thank you, that got me back in where I needed to be! Was able to load CWM again and restored from my back up...now all I need to do is make since of all the conflicting instructions to do this update so the icon goes away...found some that are fairly clear, but the links are broken now that the upload sites are blacklisted.
Either way, just glad to have my hboot back where it belongs.
So like most users, I was very excited to hear about the ICS leak by Football since I've been waiting MONTHS for some sort of development on that.
Getting impatient on waiting for CM9 and Evervolv builds for the Amaze, I really wanted to try this new leak for T-Mobile. So I figured that in order to do that, I must get S-Off.
It seemed like a tedious process so I've been holding it off for a while. Now that I've got a copper wire and everything, I wanted to do the deed once and for all.
So I accidentally flashed a stock rom (which I thought was a good thing since the instructions said I needed a stock rom), but I seem to have lost root access. Superuser runs, but battery calibration says I need to have root first and Titanium Backup doesn't work. However, my phone still says unlocked and I can still run ClockworkMod Recovery. The S-Off program tells me that there's an error. Is there anyone that can help?
bri.kwong94 said:
So like most users, I was very excited to hear about the ICS leak by Football since I've been waiting MONTHS for some sort of development on that.
Getting impatient on waiting for CM9 and Evervolv builds for the Amaze, I really wanted to try this new leak for T-Mobile. So I figured that in order to do that, I must get S-Off.
It seemed like a tedious process so I've been holding it off for a while. Now that I've got a copper wire and everything, I wanted to do the deed once and for all.
So I accidentally flashed a stock rom (which I thought was a good thing since the instructions said I needed a stock rom), but I seem to have lost root access. Superuser runs, but battery calibration says I need to have root first and Titanium Backup doesn't work. However, my phone still says unlocked and I can still run ClockworkMod Recovery. The S-Off program tells me that there's an error. Is there anyone that can help?
Click to expand...
Click to collapse
Well you are on T-mobile so you have two choices here. you can S-off if you want to have total freedom or you can revert your phone to stock and relock your bootloader and flash it and then re-unlock again. but remember flashign this without s-off may prevent you from getting s-off later on.
Ray196 said:
Well you are on T-mobile so you have to choices here. you can S-off if you want to have total freedom or you can revert your phone to stock and relock your bootloader and flash it and then reunlock again.
Click to expand...
Click to collapse
Well, I can't flash the PH85IMG without S-Off, right? Because on the HBoot screen, it would load the file but i wouldn't be asked if I wanted to install it. So I had no idea what to do. I thought I had to have S-Off to install it. Does this really mean I've lost root even though my phone says unlocked and I can run Clockworkmod?
bri.kwong94 said:
Well, I can't flash the PH85IMG without S-Off, right? Because on the HBoot screen, it would load the file but i wouldn't be asked if I wanted to install it. So I had no idea what to do. I thought I had to have S-Off to install it. Does this really mean I've lost root even though my phone says unlocked and I can run Clockworkmod?
Click to expand...
Click to collapse
you can if you lock your boot loader and revert the phone to stock.
Ray196 said:
you can if you lock your boot loader and revert the phone to stock.
Click to expand...
Click to collapse
Well, how do i revert it to stock and reroot it exactly?
bri.kwong94 said:
Well, how do i revert it to stock and reroot it exactly?
Click to expand...
Click to collapse
i think you can use this. http://forum.xda-developers.com/showthread.php?t=1493905
bri.kwong94 said:
Well, how do i revert it to stock and reroot it exactly?
Click to expand...
Click to collapse
Pretty sure you just use fastboot to lock, open a command prompt with your phone attached in debugging mode, type in fastboot oem lock, then install the stock rom listed in the development section. (If I am wrong on this, someone please feel free to correct me.)
Just tried and I got a temp root with Weaksauce from the M8 forums, which allowed me to run firewater for S-Off on the 4.4.2 ota.
1.) Install the necessary drivers
2.) Install and gain temp root with weaksauce, from this thread: http://forum.xda-developers.com/showthread.php?t=2699089
3.) After obtaining Temp root (TuneInRadio will appear in your notification bar if its running) Run Firewater (normal, rooted device method) and your golden: http://firewater-soff.com/instructions/
Make sure to follow all the instructions for Weaksauce and Firewater.
sum182 said:
Just tried and I got a temp root with Weaksauce from the M8 forums, which allowed me to run firewater for S-Off on the 4.4.2 ota.
1.) Install the necessary drivers
2.) Install and gain temp root with weaksauce, from this thread: http://forum.xda-developers.com/showthread.php?t=2699089
3.) After obtaining Temp root (TuneInRadio will appear in your notification bar if its running) Run Firewater (normal, rooted device method) and your golden: http://firewater-soff.com/instructions/
Make sure to follow all the instructions for Weaksauce and Firewater.
Click to expand...
Click to collapse
kewl... @JustinCase
Works great. Returned to full stock 3.06 S-On, took OTA, and ran weaksauce + firewater no problem. Much easier than the original facepalm & htcdev.
pyroguysf said:
Works great. Returned to full stock 3.06 S-On, took OTA, and ran weaksauce + firewater no problem. Much easier than the original facepalm & htcdev.
Click to expand...
Click to collapse
Thanks for the additional confirmation. Yea, this was actually one of the easier unlocks/s-offs I've had in a while. Thanks to the devs of those wonderful programs.
sum182 said:
Thanks for the additional confirmation. Yea, this was actually one of the easier unlocks/s-offs I've had in a while. Thanks to the devs of those wonderful programs.
Click to expand...
Click to collapse
Can confirm this worked for me as well. Anyone figure out a working wifi hotspot solution for us very rare rooted, unlimited, kit kat users? Wireless tether apk seems to fail for me.
Worked fantastic for me! Easiest way to root and s-off yet! Custom romantic now up and running. I used flashify to install TWRP.
HOLY, GOD, THANK YOU. I just did this with my old DNA, worked flawlessly. Even checked for OTA updates right beforehand and it said it was up to date. So this even worked on the newest update. THANK YOU SO MUCH
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry guys, I've been away forever and ever.
Does this mean I can once again gain root access for the DNA?!
Edit: Rooted, unlocked.
So happy I found this thread haha.
tried this today with my DNA but can't get my mac to see the device via adb, can anyone help me troubleshoot this? Thanks!!!
dbstudios said:
tried this today with my DNA but can't get my mac to see the device via adb, can anyone help me troubleshoot this? Thanks!!!
Click to expand...
Click to collapse
Debugging enabled?
xxfallacyxx said:
Debugging enabled?
Click to expand...
Click to collapse
Yea it is, I've even tried switching it off and on again and reconnecting the phone and still nothing. ADB does perform the action but comes up with nothing in the list.
dbstudios said:
tried this today with my DNA but can't get my mac to see the device via adb, can anyone help me troubleshoot this? Thanks!!!
Click to expand...
Click to collapse
Same problem here but on a Windows 7 machine. USB debugging enable, most recent windows drivers installed, uninstalled and re-installed. No matter what I do, ADB does not see my phone. Really frustrating because it has worked on this same computer previously before the Kit Kat update.
I can't get this to work. I am S-OFF from old OTA soff method, took the latest OTA now I am relocked and SOFF, but not able to flash any recovery due to relocked status. I can't unlock.
I tired weaksauce method and it says already rooted, but its not. I reset the phone to try again with no luck.
I tried to change the CID and that didnt work.
Tried to run earlier RUU and won't let me. Is there a PH98IMG of the latest OTA?
Thanks.
edit: http://forum.xda-developers.com/droid-dna/help/solved-flash-recovery-relocked-s-off-t2804435
4.42 weaksauce wont work Please help
I can not gain root access S-off on my replacement phone Verizon sent me. Any help would be greatly appreciated. If i have not included enough information my apologies as I normally figure these things out and have not had to post before. If this is not an appropriate thread to post in please redirect me. Also my boot loader is throwing tampered flag but is still locked S-on.
Sweet....Worked here too. Two things for anyone having issues....When you install SuperSU, you don't need to run it. It'll say installation failed if you do, but that's nothing to worry about. Second, after you do the adb reboot, wait 1-2 minutes after the reboot completes before you run the next command. You need to give time for temp root to be regranted.
Time to unlock the bootloader...
---------- Post added at 05:36 PM ---------- Previous post was at 05:02 PM ----------
Ok, so something else. After doing the above, if you run SuperSu it will tell you that you need to update your su binary and recommends you use TWRP to do it. So I cancelled out and installed Rom Installer from the play store and used it to flash TWRP 2.7.1. Then rebooted (not sure if necessary), then reran SuperSU. This time when it prompted me I told it to go ahead and update itself using TWRP. It did just that and all is good now.
Works Like Greased Lightning!!
Thanks SOOOOOO Much for providing this guide for S-Off for all of us who (stupidly) Allowed VZW to push the 4.4 Update to our Droid DNA's!!
This worked So easily, the Very First time! Follow both the weaksauce Guide and the firewater Guide EXPLICITLY and you will have no problems at all! Thanks to all of the devs who made this possible!
Droidel said:
I can't get this to work. I am S-OFF from old OTA soff method, took the latest OTA now I am relocked and SOFF, but not able to flash any recovery due to relocked status. I can't unlock.
I tired weaksauce method and it says already rooted, but its not. I reset the phone to try again with no luck.
I tried to change the CID and that didnt work.
Tried to run earlier RUU and won't let me. Is there a PH98IMG of the latest OTA?
Thanks.
edit: http://forum.xda-developers.com/droid-dna/help/solved-flash-recovery-relocked-s-off-t2804435
Click to expand...
Click to collapse
you dont need to be unlocked to install a recovery.
pack up your recovery image with an android info text document.
use fastboot/ruu mode to install the recovery zip file.
if you really want to use htcdev,you can also change your cid. if 11111111 or 22222222 dont work,try 33333333 or HTC__001(just remember to change it back when youre done)
Ok well i figured out my problem
solomonerwin said:
I can not gain root access S-off on my replacement phone Verizon sent me. Any help would be greatly appreciated. If i have not included enough information my apologies as I normally figure these things out and have not had to post before. If this is not an appropriate thread to post in please redirect me. Also my boot loader is throwing tampered flag but is still locked S-on.
View attachment 2873959
View attachment 2873960
View attachment 2873961
View attachment 2873962
Click to expand...
Click to collapse
I hope this helps. I had to uninstall all updates for tunein radio after that i still could not get supersu to down load the binaries so i installed superuser instead and it worked just fine. By no means am i saying this is the correct way to do it i am just telling you what worked for me.
s off firmware 3.06.605.4
can the above said firmware device be s offed??
ps: im new to xda
thanks for sharing this info. Now im s-off on Android 4.4.2, however... is it possible to flash custom ROMs wiha locked bootloader? that's all i want, otherwise ill just sell the phone and buy a Nexus 5.