Develop Bugs

[Q] Updated to OTA 2.3.3 and now, can't root

I recently updated to 2.3.3 using the OTA method. I was rooted prior to this with unrevoked3 but unrooted before I updated to 2.3.3. I wish to root again but now the bootloader will not activate using the normal Vol Dwn + Power.
Is there another way to open my bootloader or do I live the rest of my EVO's life unrooted?
Some guidance pls and thanks in advance,
R

OK, the OTA has been out for weeks, you've been a member here long enough to post a few hundred times an you didn't notice the multiple threads saying that there is no root for the the update yet??
Sorry if I have no pity for you....

HipKat said:
OK, the OTA has been out for weeks, you've been a member here long enough to post a few hundred times an you didn't notice the multiple threads saying that there is no root for the the update yet??
Sorry if I have no pity for you....
Click to expand...
Click to collapse
@ HipKat,
Thanks for the responce buddy. I didn't ask for pity, but I do apologize that I haven't used this forum as I probably should have. I also apologize if I disrupted your day by you having to type your responce. I just wiped the blood off the corner of my mouth btw. Glad to see that in your own way, you've answered my question. Thanks, hope we clash again sometime Buddy.....
Regards and hope your day improves...

Rooters should never take OTA's, that should now be programmed in your head......

dirkyd3rk said:
Rooters should never take OTA's, that should now be programmed in your head......
Click to expand...
Click to collapse
Oh, believe me, it is and thanks *as he wipes yet another drop of blood from the corner of his mouth*
Thanks again Mate....

However...
If you didn't flash the s-on zip, then you should remain s-off. The new update has an option called "fastboot" enabled by default. Either turn it off in settings or pull the battery, then boot into the bootloader. If you remain s-off you can just flash recovery and then flash a rom.
(from... Evo/MIUI/Tapatalk)

plainjane said:
However...
If you didn't flash the s-on zip, then you should remain s-off. The new update has an option called "fastboot" enabled by default. Either turn it off in settings or pull the battery, then boot into the bootloader. If you remain s-off you can just flash recovery and then flash a rom.
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
I'll give it a try and thanks for a possible fix to my Stupidity. Appreicated my friend. Live and Learn as they say.....
Regards,
R

Like several others on this forum, I updated after being previously rooted. Will it be possible to root my phone in the near future? I really want to flash the phillyfinest kingdom rom
Sent from my PC36100 using XDA Premium App

It's like the Tootsie Roll pop, the world may never know........

plainjane said:
However...
If you didn't flash the s-on zip, then you should remain s-off. The new update has an option called "fastboot" enabled by default. Either turn it off in settings or pull the battery, then boot into the bootloader. If you remain s-off you can just flash recovery and then flash a rom.
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
WOW, it worked, I am now able to access my Bootloader and YES, the S is OFF.
Thanks plainjane for the help.....

That is the one good thing. As long as you stayed S-Off, then you'd be good to go.
Sorry for the curt reply, but it's just been beaten to death on here for weeks now...

rdisanza said:
WOW, it worked, I am now able to access my Bootloader and YES, the S is OFF.
Thanks plainjane for the help.....
Click to expand...
Click to collapse
No problem.
You can flash recovery through the bootloader in PC36IMG form. Download the zip, place it on the root of your SD card, then boot into the bootloader. It'll scan and find the file, accept the "update", then decline to reboot. You can then go into recovery to restore a nandroid backup or flash the rooted stock rom (or another if you prefer).
Amon Ra: http://db.tt/WP0beNa
ClockworkMod: http://db.tt/9sksyTK
Both are from my Dropbox and properly named, so don't rename the file.
(from... Evo/MIUI/Tapatalk)

@HipKat,
Nah, don't give it a second though, I didn't. You have helped me in the past and I know everyone has a bad day or sore subject. I do appreicate this forum and ppl like you who help the helpless like me. I have much to learn and I learn by asking, sometimes, stupid questions. Thanks again man.
@plainjane,
Once again, thank you for all your help. I may have more questions for you but for now, Im going to stay stock with the S-OFF. I will review everything, take a deep breath and possible root again next weekend. All of this makes my head spin. Also, I presume those are both rooted 2.3.3 ROMS?
Again, My Thanks....
Regards,
R

unrooting help

I need to send my phone in for warranty work. I followed the guide on the unlockr.com but the PC10img.zip they supply for you says the main version is too old update fail. I believe all I need is the right PC10img file but my phone is S-on atm not sure if that matters. if I could get some help that would be much appreciated!

I dont know about the website you mention but why not use the Vision Wiki?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
which points to here: http://forum.xda-developers.com/showthread.php?t=999796

Aresmar said:
I dont know about the website you mention but why not use the Vision Wiki?
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
which points to here: http://forum.xda-developers.com/showthread.php?t=999796
Click to expand...
Click to collapse
Got it fixed! Thank you!

Drike19 said:
Got it fixed! Thank you!
Click to expand...
Click to collapse
Good to hear!
PS: if you can use the 'thanks button' I would be glad too

that warning is for people flashing it when they are already getting bootloops/are semibricked. It will install the hboot, radio, and recovery (now you are probably s-on and definitely don't have cwm recovery anymore) and then it will stop updating. Then you are mostly screwed. If your rom is still booting fine, you shoud be ok just make sure your phone is running the right unrooted factory rom (if you unroot it manually, be sure to remove superuser first! Lol) and you should be fine.
However...can someone verify that what i'm saying is right before potential disaster strikes?
Edit: how did i miss the fact that this was already solved?oooops! Lol

[Q] Trouble achieving S-Off

Howdy! Lemme preface all of this by saying that I'm less than a noob here....really inexperienced. Here's the background......
I rooted my DInc and I can't even remember which unrevoked tool I used. I was just reading along and punching commands and when the process was done I was rooted. I installed CWM successfully and flashed to CM7.2 which I've been running for quite some time. Lately I got an itch to try a JB ROM like infected, so when I looked into it, it clearly says I need S-off to accomplish that flash so I checked and realized I was S-on still.
At this point, I added the unrevoked-forever.zip to my sdcard root and tried to flash that ZIP by way CWM and i get these error messages:
E: unsupported radio version
E: update failed. Check/sdcard/soff.log
E: error in /sdcard/unrevoked-forever.zip (Status 42)
I am running Android version 2.3.7 and radio baseband version 2.15.10.12.20
Is this one of those things that I shouldn't be trying from CM7.2 and I should've dealt with before my initial flash to CM7.2?? Basically I'm totally freakin lost and in WAAAAY over my element, so any guidance would be duly appreciated. Thanks in advance!
Scott

Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.

PonsAsinorem said:
Just going to leave this right here...
http://unrevoked.com/rootwiki/doku.php/public/forever
Read the page, tell me what your issue is, and we'll go from there.
Click to expand...
Click to collapse
Sorry....i guess it pays to be extra thorough in the description of the problem. The link you left me is the one that I followed. I researched achieving S-Off on the DInc first and found this same page in my research. I followed the process and all went smooth right up until i started to flash the unrevoked-forever.zip from my sdcard via CWM. The aforementioned error messages came up on my phone and it said the process failed.
I thought it might be because the radio baseband versions that are list as "supported" do not match mine

smvogel73 said:
I thought it might be because the radio baseband versions that are list as "supported" do not match mine
Click to expand...
Click to collapse
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.

PonsAsinorem said:
Sounds good to me. With the way HTC handles S-OFF, you don't really need it. I'd go the legit way and unlock your bootloader with HTCdev.
http://www.htcdev.com/bootloader/
Edit: and for the record, you're lucky you didn't brick your device. Reading the supported requirements and ignoring them is a good way to do it.
Click to expand...
Click to collapse
Yes thx....I'm gathering that! So this is where terminology gets so dang confusing for me. I didn't think unlocking my bootloader meant the same thing as achieving S-Off?? I already thought my bootloader was unlcoked, as I was able to flash CM7.2, which I didnt think I would be able to do if I had a locked bootloader. So wicked confused!!! And try as I miught to educate myself in these forums, I haven't located a sticky or guide that really thoroughly explains all the vernacular regarding android dev/modding/rooting/flashing/etc
So this other method will work with any radio baseband version then?? Or is it important to check compatibility there too??

What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON

PonsAsinorem said:
What's the very top of your HBOOT say, UNLOCKED? Some more reading:
S-Off vs Unlocked, and flashing firmware
About Unlock and S-ON
Click to expand...
Click to collapse
It says "UNLOCKED" and below that it says "S-ON
Thank u for the materials too!

So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run. I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.
The ROM I'm looking to flash is Infection JB 4.2.2. The instructions say that if you're coming from. A non-AOSP ROM and are S-On that you've gotta extract boot.img and fastboot it after the ROM flash......whatever the heck that means???

smvogel73 said:
So after looking at those two links, it sure seems like not only is S-Off a potentially dangerous thing to do, it might also not even be necessary on the long-run.???
Click to expand...
Click to collapse
Correct. Staying S-ON minimizes the danger. It locks your radio, and HBOOT, which are the main dangers.
smvogel73 said:
I say that carefully tho, as u just got thru telling me that flashing a new ROM against spec is a very dangerous thing to do and could potentially brick mu phone.???
Click to expand...
Click to collapse
Not really ROM flashing, but radio and HBOOT flashing, which is what unrevoked-forever tweaks.
I'd try to flash it one more time. When you do, what, if anything, are you wiping? You should be doing a factory reset, system, and boot wipe/format, then flash the ROM.
If that doesn't work (it might not, it's been awhile since I've worked with S-ON devices), then we'll move on to S-OFF (if you want).

Oh no.....I didn't even attempt to flash the Infection JB ROM specifically because I was not able to achieve S-Off. Whether it was intended or not, yea.....u sufficiently scared me about bricking the phone if I'm not to spec per the developer.
Are u saying I should wipe and then try to flash this ROM despite still being S-On?

Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.

PonsAsinorem said:
Up to you. Personally, if it were me, I would try flashing the ROM with S-ON. The inc is a very friendly device, as long as you don't try to break the HBOOT and/or radios. It is next to impossible to break those with S-ON.
If you want to go S-OFF instead, grab the latest supported radio from http://dinc.does-it.net/ and then do the unrevoked-forever.
Click to expand...
Click to collapse
Well there you have it....I will trust your wisdom (as it is far supperior to my own) and I shall flash this ROM tonight!! I already have a nandroid backup of CM7.2 that Im running, as well as a Titanium backup of all my user apps/files.
Sincerest thanks for all your help!!

Hello. Im no expert but i think Cyanogenmod is aosp so you should be good.
I was where you were 2 yrs ago when I rooted my 1st phone: a friends froyo Dinc (ahhh...froyo). A few months ago I aquired my own and went to research how to root GB and everything has changed and is now vastly more complicated. Also I think every phone has a locked bootloader but not encrypted and I think Soff is extra security since I've only encountered it on htc phones. Anyway I've managed to get my inc to Soff but its still locked, idk how lol
Sent from my ADR6300 using Tapatalk 2

ReRoot after Sense 6.0 OTA

Anybody having any luck re-rooting after the Sense 6 OTA today?

brent372 said:
Anybody having any luck re-rooting after the Sense 6 OTA today?
Click to expand...
Click to collapse
im guessing they patched the exploit and will have to wait for a new one if you went back to locked, or s-on status.

synisterwolf said:
im guessing they patched the exploit and will have to wait for a new one if you went back to locked, or s-on status.
Click to expand...
Click to collapse
Never S-OFF'd or unlocked it.
Never perm-rooted it. Didn't even have custom recovery.
It was 100%, just rooted. It is a work-only phone so I am not overly concerned with it. But it would still be nice to be able to.

brent372 said:
Never S-OFF'd or unlocked it.
Never perm-rooted it. Didn't even have custom recovery.
It was 100%, just rooted. It is a work-only phone so I am not overly concerned with it. But it would still be nice to be able to.
Click to expand...
Click to collapse
Ah, im sure someone will find a way. they always do.

synisterwolf said:
Ah, im sure someone will find a way. they always do.
Click to expand...
Click to collapse
Tell that to the folks in the VZW s5 forums. lol

eman7131 said:
Tell that to the folks in the VZW s5 forums. lol
Click to expand...
Click to collapse
ZING
i guess i should say that HTC phones seem to be easier to root, well from the outside looking in that is. i have no clue how hard it really is to find an exploit.

newest RUU today
FLASH: Just now, I can confirm that after taking the 5-28-2014 update (4.10.605.3) Weaksauce 1.01 can't any longer attain root.

michaelbsheldon said:
FLASH: Just now, I can confirm that after taking the 5-28-2014 update (4.10.605.3) Weaksauce 1.01 can't any longer attain root.
Click to expand...
Click to collapse
And this is why I always tell people that if they want to stay rooted or unlock in the future that they shouldn't take any OTAs.

Wasnt a deal breaker for me on this phone
Sent from my HTC6525LVW using Tapatalk

not a tragedy
GrayTheWolf said:
And this is why I always tell people that if they want to stay rooted or unlock in the future that they shouldn't take any OTAs.
Click to expand...
Click to collapse
Nah, just a learning exercise!!
Was locked and S-0ff and took the 0TA to check it out. Including Weaksauce.
Easily flashed an unencrypted older RUU, then unlocked the bootloader with Scotty's recipe posted earlier.
Made firmware newest with SantoD's no-boot firmware and we're back at the races!

michaelbsheldon said:
Nah, just a learning exercise!!
Was locked and S-0ff and took the 0TA to check it out. Including Weaksauce.
Easily flashed an unencrypted older RUU, then unlocked the bootloader with Scotty's recipe posted earlier.
Made firmware newest with SantoD's no-boot firmware and we're back at the races!
Click to expand...
Click to collapse
If s-off there's no need to lock to get an OTA.
Also, keep this so you don't need to flash back to an older RUU.
http://forum.xda-developers.com/showthread.php?t=2765784

[Q] Fix for "Test device" in HTC Tell? Relocking bootloader?

Hi folks,
I have a HTC One M8 that is registered with HTCDev and also S-Off (courtesy of the awesome sunshine tool). In the settings app, I have a red text telling me this is now a test device and all my data are belong to HTC. (As someone posted here months ago.)
I am not sure if I want to cripple the Udove.apk because I'm concerned about the next OTA update. Is there a way to "unregister" with HTC or more technically, relock the bootloader without loosing S-Off? Is there a way to determine I have a stock hboot if I'm not sure if I messed with it in the process?
Thanks for reading

This really is just a follow-on of your other thread, so I don't know why you started a new one.
The phone will come up as a test device since its s-off. Relocking the bootloader won't change that, nor will it effect s-off.
Try to freeze the app with Titanium. Or remove it now, and revert to the stock ROM when its OTA time.

redpoint73 said:
This really is just a follow-on of your other thread, so I don't know why you started a new one.
Click to expand...
Click to collapse
I did not mean to offend anyone, I was just thinking my question in this thread differed from the previous one and might not be found by the right people under the other title.
redpoint73 said:
The phone will come up as a test device since its s-off. Relocking the bootloader won't change that, nor will it effect s-off.
Click to expand...
Click to collapse
Thanks for clearing that up. I had so far been unable to figure out if this test device thing was connected to s-off, bootloader or both of them.
redpoint73 said:
Try to freeze the app with Titanium. Or remove it now, and revert to the stock ROM when its OTA time.
Click to expand...
Click to collapse
I could try Titanium, yes. Since my motivation to go all over several app setups is decreasing, I will avoid flashing as best as I can.

jndvid said:
I did not mean to offend anyone, I was just thinking my question in this thread differed from the previous one and might not be found by the right people under the other title.
Click to expand...
Click to collapse
No worries, I was not offended. But you posed similar or related questions in your other thread, so IMO its redundant to start a new thread and ask them again.
Its pretty typical for additional questions to pop up during your thread as the issue evolves and the discussion progresses. But IMO no need to create new threads as that happens.

I have HTC M8 and I want to run custom rom but have this red text.. now I am s-off and rooted, so I can delete system apps.. which apps no I need to remove so it won't sent anything to the HTC?
Thank you very much for answers...