Hello, I have been doing some firmware updates and just wanted to check if HTC posted any AT&T RUU's for backup purposes - good news 1.58.502.1 full RUU is posted here -- http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe
At least now some of us will have easier and less time consuming rollback to AT&T stock! ))
Dottcent said:
Hello, I have been doing some firmware updates and just wanted to check if HTC posted any AT&T RUU's for backup purposes - good news 1.58.502.1 full RUU is posted here -- http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe
At least now some of us will have easier and less time consuming rollback to AT&T stock! ))
Click to expand...
Click to collapse
Sweet this is nice to have!
thanks for posting, that will be nice to have.
Dottcent said:
Hello, I have been doing some firmware updates and just wanted to check if HTC posted any AT&T RUU's for backup purposes - good news 1.58.502.1 full RUU is posted here -- http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe
At least now some of us will have easier and less time consuming rollback to AT&T stock! ))
Click to expand...
Click to collapse
Wow. Not sure how you found this. When I'm looking on the HTCdev site, I can't get this to pull up...but I'm extremely grateful...
Thanks you!!
Mark
Finally! Thanks for posting.
I can confirm this works. Used it to return to stock, used the guides here http://forum.xda-developers.com/showthread.php?t=2751011 to remove the tampered flag and relock the bootloader with out tripping the relocked flag, then ran this RUU, everything is 100% back to stock, except for S-Off.
zacharyt86 said:
I can confirm this works. Used it to return to stock, used the guides here http://forum.xda-developers.com/showthread.php?t=2751011 to remove the tampered flag and relock the bootloader with out tripping the relocked flag, then ran this RUU, everything is 100% back to stock, except for S-Off.
Click to expand...
Click to collapse
Glad it worked I haven't had a chance to try it. I'm still running GPE ruu but glad to see there is a easier way to return to stock.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
issue
RUU wont run for me no matter what I do. I have tried locking, CWS__001, wiping everything and putting in RUU mode and the .exe wont run past the EULA acceptance
orvon.freeman said:
RUU wont run for me no matter what I do. I have tried locking, CWS__001, wiping everything and putting in RUU mode and the .exe wont run past the EULA acceptance
Click to expand...
Click to collapse
same here. pissing me off lol. i think its actually corrupted. because by pulling the rom.zip file if you open it . it doesnt even look like all the files are there
daddioj said:
same here. pissing me off lol. i think its actually corrupted. because by pulling the rom.zip file if you open it . it doesnt even look like all the files are there
Click to expand...
Click to collapse
If you feel the file is corrupt, you can download the RUU from the HTC's website, you will find it under device support (ATT HTC ONE M8). I think your bootloader has to be locked to be able to install the RUU.
wurldfamuz said:
If you feel the file is corrupt, you can download the RUU from the HTC's website, you will find it under device support (ATT HTC ONE M8). I think your bootloader has to be locked to be able to install the RUU.
Click to expand...
Click to collapse
i know i been doin HTC for years . ok bad choice of words lol. isnt that what the original link is? i never checked
downloaded from the source and still wont run
---------- Post added at 04:11 PM ---------- Previous post was at 04:10 PM ----------
as a not I did do the google edition con
wurldfamuz said:
If you feel the file is corrupt, you can download the RUU from the HTC's website, you will find it under device support (ATT HTC ONE M8).
Click to expand...
Click to collapse
The link in the OP is the HTC link. Same link as given on AT&T's support page: http://www.htc.com/us/support/htc-one-m8-att/news/
---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------
For folks having trouble running RUU, do you have HTC drivers installed, and is adb/fastboot able to see the phone?
Bootloader typically needs to be locked or relocked to run RUU on past HTC devices. But S-off bypasses this requirement.
---------- Post added at 04:29 PM ---------- Previous post was at 04:27 PM ----------
redpoint73 said:
Finally! Thanks for posting.
Click to expand...
Click to collapse
Actually, when I said "Finally" it was more in regard to the fact we haven't had any official RUU for this device yet.
Its actually quite fast for HTC to have the RUU so fast (1 week) after rolling out the OTA.
zacharyt86 said:
I can confirm this works. Used it to return to stock, used the guides here http://forum.xda-developers.com/showthread.php?t=2751011 to remove the tampered flag and relock the bootloader with out tripping the relocked flag, then ran this RUU, everything is 100% back to stock, except for S-Off.
Click to expand...
Click to collapse
... hummmm? i thought relocking the bootloader and then flashing with a RUU will clear the Tampered/Locked flag. Thoughts?
cortez.i said:
... hummmm? i thought relocking the bootloader and then flashing with a RUU will clear the Tampered/Locked flag. Thoughts?
Click to expand...
Click to collapse
No I tried that the first time and it flashed the ruu fine but the flag stayed at relocked and tampered, then I re-unlocked the bootloader and folled the links in that post to remove them, then flashed the ruu, now it all shows as normal, except for s-off, which isn't that obvious.
cortez.i said:
... hummmm? i thought relocking the bootloader and then flashing with a RUU will clear the Tampered/Locked flag. Thoughts?
Click to expand...
Click to collapse
Tampered yes, Relocked no
Tampered just appears when you install a custom recovery. So since the RUU re-installs stock recovery, the Tampered flag is removed.
The bootloader lock flag is intended to always say either Unlocked or Relocked, once its been initially unlocked. Its intended to never be returned to Locked (once unlocked). But hboot can be hacked to make it so. An official RUU will never do this.
Success! I was s-off rooted and had twrp, all I did was followed the directions. I also took out my sim card and SD card.
{
"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 Nexus 7 using Tapatalk
redpoint73 said:
Finally! Thanks for posting.
Click to expand...
Click to collapse
Exactly my thought, finally! ?
Those who ran RUU - thanks for your success confirmation! ?
Sent from my HTC One_M8 using Tapatalk
zacharyt86 said:
No I tried that the first time and it flashed the ruu fine but the flag stayed at relocked and tampered, then I re-unlocked the bootloader and folled the links in that post to remove them, then flashed the ruu, now it all shows as normal, except for s-off, which isn't that obvious.
Click to expand...
Click to collapse
appreciate you reconfirming steps to return to "stock".:good:
redpoint73 said:
Tampered yes, Relocked no
Tampered just appears when you install a custom recovery. So since the RUU re-installs stock recovery, the Tampered flag is removed.
The bootloader lock flag is intended to always say either Unlocked or Relocked, once its been initially unlocked. Its intended to never be returned to Locked (once unlocked). But hboot can be hacked to make it so. An official RUU will never do this.
Click to expand...
Click to collapse
thank you for the clarification... i feel "slightly safer" experimenting with M8. :good:
does anyone know how to make this a flashable zip to use with rebootRUU?
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.
was bored while trying to fix my kernel issue, so I copied the jpbear style for unlocked hboots. This will work just like the jpbear hboots, meaning fastboot flash is re-enabled without unlocking on HTCDev. I think it also enables fastboot extended commands but I'm not sure. Thanks to JuopunutBear for the original unlocked hboot. Note: when they put up their official one, I will take this down. I have tested it and it should not brick your phone, but the standard disclaimer applies as you are modifying your bootloader.
https://dl.dropbox.com/u/15902163/PH98IMG_hboot_2.27_unlocked.zip
MD5: 1109A13D4F33628BD1B53160FE42450E
Good work!
con247 said:
Do not download this until an md5 is posted!
Click to expand...
Click to collapse
Good call, save a few unnecessary bricks from being made
Sent from my ADR6425LVW using xda app-developers app
posted MD5.
Also, posted as a PH98IMG. I realized... its kinda pointless fastboot flashing something when fastboot flash is unlocked
delete
Downloaded, I'll try later......
Downloaded, I'll try later......About to go to sleep. Thanks for this!!
Screenshots after flash....
Well...couldn't go to sleep...flashed it.
{
"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"
}
As you can see......says vinylfreak89 at top....
Thanks
=========
wow...Tapatalk uploads big pictures....lol
Sent from my HTC Rezound / ADR6425LVW using Tapatalk v2.2.7
i was thinking of tagging it with the usual jpbear tag but that would get way too confusing if/when they finally release one.
Notice it doesn't say "Locked" anywhere....
vinylfreak89 said:
i was thinking of tagging it with the usual jpbear tag but that would get way too confusing if/when they finally release one.
Click to expand...
Click to collapse
============
Notice it doesn't say "Locked" anywhere....did you edit that out?
actually it would say *** UNLOCKED *** if I didn't edit it. Apparently the changes this makes makes the phone think it was unlocked. I just edited the *** UNLOCKED *** text to **vinylfreak89**. Jpbear just edits it to =Juopuntbear=
Yep...just did a couple of quick flashbacks....
Yep...just did a couple of quick flashbacks....jBear2.25 and Stock2.27 and looked. Back on yours now...lol It's amazing...the flashing, etc. was pretty scary a few months back. Can do it all pretty quick now. I already had put the flashable zip for the stock 2.27 together a few days back. I do have a pretty quick learning curve...I have been modding phones since the Moto Razor flip phones, WM5,WM6,WM6.5 and now the Androids.
---------- Post added at 03:01 AM ---------- Previous post was at 02:53 AM ----------
What did you used to edit the nbo file? I have opened up copies with wordpad...just to see what was in it. Parts are readable....lol.
So, I suspect the primary advantage of this hboot, is that should one brick his phone and try and return it to Verizon, then Verizon will not suspect a thing because it will not show UNLOCKED or TAMPERED?
Instead Verizon will see "vinylfreaq89" and be convinced the phone has not been tampered with?
I suppose this might work with some Verizon employees who are high school dropouts.
Hihi lol
Great work, appreciate it.
regards
HowardZ said:
So, I suspect the primary advantage of this hboot, is that should one brick his phone and try and return it to Verizon, then Verizon will not suspect a thing because it will not show UNLOCKED or TAMPERED?
Instead Verizon will see "vinylfreaq89" and be convinced the phone has not been tampered with?
I suppose this might work with some Verizon employees who are high school dropouts.
Hihi lol
Great work, appreciate it.
regards
Click to expand...
Click to collapse
It would be really neat if you could make it say "locked" as if it never had been unlocked or tampered. That would help anyone needing Verizon service.
motenak said:
It would be really neat if you could make it say "locked" as if it never had been unlocked or tampered. That would help anyone needing Verizon service.
Click to expand...
Click to collapse
S-off on gingerbread came with an engineering hboot, which did exactly that. it would display "LOCKED" and act as if it was unlocked. There was an "ENG" indicator on another line that it was an engineering hboot. This hboot was leaked. and thus was signed by HTC. This hboot also was capable of additional fastboot commands, but no developers are making use of them to my knowledge.
It seems the sole purpose of these replacement hboots is to fool Verizon. I don't think they accomplish this mission very well.
Except for the GB ENG hboot, the other replacement hboots are not signed by HTC. This carries the risk that if the phone is given the command to becomr S-ON, then the phone becomes an unrecoverable brick. Perhaps some new verizon ota or ruu will try to turn s-on back on, and phones will become bricks.
Anyway, I am using the stock version if this hboot. and am wondering what advantages there might be to using this modified hboot?
I think sometimes smart talented developers rush into doing modifications before considering if it is really a good idea?
so... is this a patched hboot,or is it just a copy and hex edit of your unlocked hboot?
if its the latter... have yall that have flashed it,have you flashed back to the stock 2.27 hboot to make sure you are locked still?
id hate to see this hboot change the lock status flag on those devices that folks care.
the ICS JPbear hboots do work just fine in place of 2.25 and 2.27,so if this is messing with the lock status flag one can easily just use one of them to retain locked status.
im not criticizing,just curious. if it is a copied unlocked stock hboot,yall that flashed it have some big cast iron balls id have been afraid an unlocked stock hboot would have had some phone specific info that could have ended badly
if one can really flash between locked and unlocked by simply flashing an unlocked hboot,thats pretty interesting... i wouldn t have thot it would work out that way
Flashed back to Stock 2.27.........
Flashed back to Stock 2.27.........again. Still "LOCKED". Did this right after the screenshots I posted. Since I tried this "Modded hBoot have flashed Stock2.27,then Jbear2.25, then This2.27again. When Stock says "LOCKED". With others says "Jbear or vinyl"......Have had no problems.
manbat said:
Flashed back to Stock 2.27.........again. Still "LOCKED". Did this right after the screenshots I posted. Since I tried this "Modded hBoot have flashed Stock2.27,then Jbear2.25, then This2.27again. When Stock says "LOCKED". With others says "Jbear or vinyl"......Have had no problems.
Click to expand...
Click to collapse
thanks for the info. if youd said that earlier in the thread,my apologies,i hadnt seen it.
No problem...
No problem...I thought about most of your points before I flashed this one the first time...lol. Took a deep breath and did it... .
Hmmm...can I make a request for custom verbiage?
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Hate to be a thorn, but noticed form the pick on page 1, there is not recovery option listed. Or are my glasses foggy?
Hello everyone,
I have a SIM unlocked AT&T HTC One (M7) that I am using on T-Mobile.
I am not rooted (I do not wish to be rooted at this time), and I have managed to get up to version 4.3 by use of the HTC RUU, but when I try to get to android version 4.4, the RUU shows error 155. How would I fix this?
Help Please
-TR3Y
TR3Y said:
Hello everyone,
I have an unlocked AT&T HTC One (M7) that I am using on T-Mobile.
I am not rooted (I do not wish to be rooted at this time), and I have managed to get up to version 4.3 by use of the HTC RUU, but when I try to get to android version 4.4, the RUU shows error 155. How would I fix this?
Help Please
-TR3Y
Click to expand...
Click to collapse
try this one
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
clsA said:
try this one
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
Thank you for replying. I have tried that one already, as well as the one from HTC1Guru. Both of them read the build number as 4.20.502.1 instead of 4.18.502.7 . I believe the error keeps happening because the build number does not match and pretty much my laptop won't allow it to upgrade as long as the build numbers don't match. I will try it again though.
Thanks,
-TR3Y
P.S. has this happened with anyone else?
Update: I have re-tried the update now. At 5% and checking header. I will give it over night to update.
clsA said:
try this one
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
clsA, is this an official RUU from HTC? Every time I try do it, it hangs at 5% (checking header...). I just want to make sure there is no virus/malware here. and androidruu.com is blocked at the location I am at. It says that there was malware found on AndroidRUU. Can you confirm any of this?
-Malware on AndroidRUU and
-official RUU from HTC
-TR3Y
Well I'm going to say the files work for smorgasbord and not others
Malware no I've never seen any infections RUU
Sent from my HTC One_M8 using Tapatalk
clsA said:
Well I'm going to say the files work for smorgasbord and not others
Malware no I've never seen any infections RUU
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
So, are the RUU files are official from HTC? Also HTC1GURU was not blocked at the location I was at. I got the RUU from there. I am guessing both of the RUU files from both websites are the same?
Yeah their the same file
And no their not on the HTC site
I'm not really sure where they originated from
Sent from my HTC One_M8 using Tapatalk
clsA said:
Yeah their the same file
And no their not on the HTC site
I'm not really sure where they originated from
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Oh ok... Well, now I have a new error when I try from a last resort computer. When I try and run the RUU an error box comes up that says "htc_fastboot.exe has stopped" and then everything crashes. This is an error I have not had anywhere else. Any suggestions?
clsA said:
Yeah their the same file
And no their not on the HTC site
I'm not really sure where they originated from
Click to expand...
Click to collapse
I'm pretty sure the 4.18.502.7 RUU on androidRUU was leaked from some member of the HTC elevate program, that's why it changes the build version to 4.20.502.1, so that it's clear its not the GA release (and possibly to prevent downgrading once its installed.) Also, several reports of that RUU failing to install, possibly it has different signature-- I don't really know.
cschmitt said:
I'm pretty sure the 4.18.502.7 RUU on androidRUU was leaked from some member of the HTC elevate program, that's why it changes the build version to 4.20.502.1, so that it's clear it not the GA release (and possibly to prevent user's from downgrading once they've installed it.) Also, several reports of that RUU failing to install, possibly it has different signature-- I don't really know.
Click to expand...
Click to collapse
Are you recommending that people not install that RUU and just wait for HTC to release it?
TR3Y said:
Are you recommending that people not install that RUU and just wait for HTC to release it?
Click to expand...
Click to collapse
Just sharing my observations. If you're trying to stay 100% stock and are currently on 3.17.502.3 then download the 4.18.502.7 OTA and flash it in stock recovery.
@clsA posted it here.
cschmitt said:
I'm pretty sure the 4.18.502.7 RUU on androidRUU was leaked from some member of the HTC elevate program, that's why it changes the build version to 4.20.502.1, so that it's clear it not the GA release (and possibly to prevent downgrading once its installed.) Also, several reports of that RUU failing to install, possibly it has different signature-- I don't really know.
Click to expand...
Click to collapse
Thanks for the info ... I know I downloaded the RUU when it first come out and had @nkk71 decrypt the rom zip for me ... he mentioned that it had errors during the decrypting but nothing specific, just that he fixed it. Flashing the rom.zip alone fails on all attempts. I was s-off when i flashed the RUU.exe so i don't really know if it's a signature problem or not. The Decrypted version i uploaded worked fine on my 2nd One (s-off of coarse). But I have had reports of it not flashing also ...so I'm really not sure what to think.
cschmitt said:
Just sharing my observations. If you're trying to stay 100% stock and are currently on 3.17.502.3 then download the 4.18.502.7 OTA and flash it in stock recovery.
@clsA posted it here.
Click to expand...
Click to collapse
I have tried going into the current recovery already. The OTA is on the root of internal storage. I went into the recovery and went install from phone storage, and it had an error and just restarted my One. If you have a few minutes. I will do it again and say what the error was.
clsA said:
Thanks for the info ... I know I downloaded the RUU when it first come out and had @nkk71 decrypt the rom zip for me ... he mentioned that it had errors during the decrypting but nothing specific, just that he fixed it. Flashing the rom.zip alone fails on all attempts. I was s-off when i flashed the RUU.exe so i don't really know if it's a signature problem or not. The Decrypted version i uploaded worked fine on my 2nd One (s-off of coarse). But I have had reports of it not flashing also ...so I'm really not sure what to think.
Click to expand...
Click to collapse
I've decrypted the RUUs as well and the format has changed in KK RUUs (due to the size) so now the encrypted rom.zip contains 5 zip files: firmware.zip, system1.zip, system2.zip, system3.zip, and userdata.zip. That's why we see messages like "checking 1/5" when it's flashing, it's verifying each of the 5 zips.
I haven't attempted to flash that RUU (or any RUU for that matter), been on CM builds for the last year.
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
TR3Y said:
I have tried going into the current recovery already. The OTA is on the root of internal storage. I went into the recovery and went install from phone storage, and it had an error and just restarted my One. If you have a few minutes. I will do it again and say what the error was.
Click to expand...
Click to collapse
Give it a try, let's see what happens. There's also a means to flash the OTA in TWRP that worked for at least a couple of people: here
cschmitt said:
I've decrypted the RUUs as well and the format has changed in KK RUUs (due to the size) so now the encrypted rom.zip contains 5 zip files: firmware.zip, system1.zip, system2.zip, system3.zip, and userdata.zip. That's why we see messages like "checking 1/5" when it's flashing, it's verifying each of the 5 zips.
I haven't attempted to flash that RUU (or any RUU for that matter), been on CM builds for the last year.
Click to expand...
Click to collapse
@clsA ... @cschmitt ...
can either of you tell me how to fix this error? http://ow.ly/w0iCY
TR3Y said:
@clsA ... @cschmitt ...
can either of you tell me how to fix this error? http://ow.ly/w0iCY
Click to expand...
Click to collapse
it says check cid failed .. have you changed your cid to something else ?
change it back
fastboot oem writecid CWS__001
TR3Y said:
can either of you tell me how to fix this error?
Click to expand...
Click to collapse
Other's have reported that, it's seems to be an issue with the update script checking the CID.
Does your fastboot screen show CID CWS__001 and OS 3.17.502.3 ?
clsA said:
it says check cid failed .. have you changed your cid to something else ?
change it back
fastboot oem writecid CWS__001
Click to expand...
Click to collapse
I don't remember changing the CID, unless unlocking it did that. That won't wipe my phone if I do that, right?
cschmitt said:
Other's have reported that, it's seems to be an issue with the update script checking the CID.
Does your fastboot screen show CID CWS__001 and OS 3.17.502.3 ?
Click to expand...
Click to collapse
it doesn't appear to.
{
"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"
}
cschmitt said:
Other's have reported that, it's seems to be an issue with the update script checking the CID.
Does your fastboot screen show CID CWS__001 and OS 3.17.502.3 ?
Click to expand...
Click to collapse
TR3Y said:
I don't remember changing the CID, unless unlocking it did that. That won't wipe my phone if I do that, right?
Click to expand...
Click to collapse
sorry for the confusion, you seem to be in really good hands try the fix @cschmitt posted above
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.