This tool will allow you remove the Tampered flag from your bootloader. It will also allow you to easily Lock and Unlock your Bootloader directly from recovery.
No root required since it is run in recovery, however you still must be S-OFF.
Before using this tool you need to be sure you are using the latest version of recovery as the M7 U/UL TWRP requires at least version 2.6.3.3 for this package to work. The current downloads for both CWM and TWRP can found below:
The latest M7 U/UL TWRP can be downloaded HERE.
The latest M7 U/UL CWM can be downloaded HERE.
***[UPDATE] - It seems that the latest TWRP 2.6.3.3 has been pulled due to some minor issues. If your TWRP version doesn't work please use CWM for now until a updated TWRP release is made.
This will work for Verizon and Sprint as well, however they have different versions of these recoveries, so please make sure you are using the correct recovery for your device.
Saying this again in case you missed it: YOU MUST BE S-OFF!
To use the tool simply copy the zip file to your phone and then boot to your custom recovery and choose install. Then browse to where you copied the file and select it. The aroma installer will begin. Follow the steps outlined in the pictures below and choose the options you want to run.
{
"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"
}
Now you can just keep this file on your phone and Lock and Unlock at anytime without a PC and without losing data.
***Credits***
S-trace for originally discovering the location of the lock status flag. See this thread.
scotty1223 for his ADB shell commands. Threads HERE and HERE. Scotty was also very helpful to me in understanding some of the default values.
Just to be clear I did not just copy and paste scotty1223's commands into a aroma installer. The echo command can be problematic in aroma, so I developed original code for all four commands. The end result is the same in that the data in the partitions is changed as needed.
***Download***
Guru Bootloader Reset Tool
md5: fdb8264a8f4741bae22939cd7734f7c2
Enjoy!
If this helped you out please consider a small donation or just a thanks would be great.
Demo and Troubleshooting
Demo Video:
***Troubleshooting***
If the installer stays on this screen fore more than a few seconds, then it means you need to delete/format cache. This can be done within both recoveries. You may need to reboot recovery after clearing cache and begin the installer again. This seems to happen more on CWM than TWRP.
If the installer runs but your bootloader doesn't change, it is proably one of these things:
You are not S-Off
You do not have the latest version of recovery (I recommend TWRP)
+ 1
+1
Worked on int. m7 with hboot version 1.55.
Now have removed my tampered flag :victory:
thx
pOpY
Oh yeah..thanks..a handy tool..
Sent from my HTC One using XDA Premium 4 mobile app
Nice Thanks @crushalot
Quick question (if you have time): why do we need latest recovery? what would happen on an older recovery?
Will this work on Rumrunners custom HBOOT or is a stock HBOOT only recommended?
Sent from my HTC One using Tapatalk
nkk71 said:
Nice Thanks @crushalot
Quick question (if you have time): why do we need latest recovery? what would happen on an older recovery?
Click to expand...
Click to collapse
On older recoveries, the worst that could happen is that it may not work. It won't hurt to try.
The reason you need an updated recovery is because on TWRP before version 2.6.3.3 the partition wasn't writable so the actions didn't work. Older CWM should be ok but I only tested the latest.
Evil-Dragon said:
Will this work on Rumrunners custom HBOOT or is a stock HBOOT only recommended?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
It will work on any firmware. Hboot is not touched. This only modifies partitions mmcblk0p3 and mmcblk0p7.
crushalot said:
On older recoveries, the worst that could happen is that it may not work. It won't hurt to try.
The reason you need an updated recovery is because on TWRP before version 2.6.3.3 the partition wasn't writable so the actions didn't work. Older CWM should be ok but I only tested the latest.
Click to expand...
Click to collapse
Noted. Thanks
Sent from my HTC One using Tapatalk
Awesome!
I was looking for this... it worked great! Thanks man!
crushalot said:
On older recoveries, the worst that could happen is that it may not work. It won't hurt to try.
The reason you need an updated recovery is because on TWRP before version 2.6.3.3 the partition wasn't writable so the actions didn't work. Older CWM should be ok but I only tested the latest.
Click to expand...
Click to collapse
Hi crushalot, I just noticed TWRP version 2.6.3.3 was pulled and back to 2.6.3.0, just FYI
Awesome that this can be done fron recovery, let alone in an Aroma install! Looks good! :good:
But I am having trouble seeing the use for me personally? Is this so that Ican lock my botloader and download Official OTAs (if thats required)? Or is this just something in case I have to send it off for service?
Or am I missing something here?
DaringDomino3s said:
Awesome that this can be done fron recovery, let alone in an Aroma install! Looks good! :good:
But I am having trouble seeing the use for me personally? Is this so that Ican lock my botloader and download Official OTAs (if thats required)? Or is this just something in case I have to send it off for service?
Or am I missing something here?
Click to expand...
Click to collapse
. Warranty purposes. Or for example in my case if I decided to upgrade my phone with jump, I can make everything look like never even happened. It's quite useful.
Sent from my HTC One using XDA Premium 4 mobile app
nkk71 said:
Hi crushalot, I just noticed TWRP version 2.6.3.3 was pulled and back to 2.6.3.0, just FYI
Click to expand...
Click to collapse
Yeah, seems like it was pulled because the charging while in recovery doesn't work correctly.
It still works for everything else. Not sure if they will just re-release 2.6.3.3 when fixed or make a new version.
I will update the link and info in the OP.
Thanks
DaringDomino3s said:
Awesome that this can be done fron recovery, let alone in an Aroma install! Looks good! :good:
But I am having trouble seeing the use for me personally? Is this so that Ican lock my botloader and download Official OTAs (if thats required)? Or is this just something in case I have to send it off for service?
Or am I missing something here?
Click to expand...
Click to collapse
Also sometimes a locked bootloader is needed for promotions like the 25 GB of Google Drive space.
There can be a variety of reasons one might need to toggle it.
Looking and unlocking won't wipe data? Like a typical htcdev unlock does?
Sent from my HTC One using xda app-developers app
crushalot said:
Yeah, seems like it was pulled because the charging while in recovery doesn't work correctly.
It still works for everything else. Not sure if they will just re-release 2.6.3.3 when fixed or make a new version.
I will update the link and info in the OP.
Thanks
Click to expand...
Click to collapse
I'm still on CWM 6.....2 (the old one, but with updated ts drivers) gonna test ur tool on friday.
Will let u know.
Btw, thanks for all your guru site, I refer to it a lot; PayPal doesn't work in my country so can't contribute. But thanks !!
Love ur work.
Sent from my HTC One using Tapatalk
joho5 said:
Looking and unlocking won't wipe data? Like a typical htcdev unlock does?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No, my tool doesn't wipe data during a lock or unlock.
It directly modifies the partitions that conatin the bootloader status, without touching /data or /system
Related
For Archive Purposes.
Flashable via TWRP
{
"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"
}
IMPORTANT
THIS ROM IS MENT TO BE USED WITH BOOTLOADER v1.11 AS THE PARTITION OFFSETS ARE DIFFERENT FROM 1.09 and 1.14
IF YOU ARE USING ONE OF THE OTHER BOOTLOADER'S THE ROM WILL FREEZE ON LOAD WHILE TRYING TO PREPARE THE /SDCARD PARTITION. IF ON 1.11, YOU MUST FLASH CORRESPONDING RADIO OR WIFI WILL BE BROKEN - SIMPLY CHANGING RIL'S ALONE WILL NOT FIX THE ISSUE.
FOR FILE REFERENCE ONLY.
They both have Busybox run parts, and Su binary & App included.
Evita_UL_Rogers_WWE_1.94.631.3_release Odexed
MD5 Sum: 92AB3DF4F68C9EC570FCF8533BD99B06
Size: 540.36 MB (566,607,262 bytes)
Evita_UL_Rogers_WWE_1.94.631.3_release Deodexed
MD5: 5AD39E62E396BFBDEA4C097F182A1A13
Size: 540.15 MB (566,383,813 bytes)
Original OTA
OTA_Evita_UL_Rogers_WWE_1.94.631.3-1.73.631.1_release_268994d5lde1latibkco05.zip
MD5 Sum: f768179558ff329beaaf06eddaf7fc63
JSL, always quick on the draw
Sent from my HTC One X
Very nice. Thanks!
anyway to flash this with a locked bootloader?
hey sry to be a noob but is that the link posted on the second post? thanks for the work btw!
Berserk87 said:
anyway to flash this with a locked bootloader?
Click to expand...
Click to collapse
Nope. I doubt it, because the zip is not signed by HTC
The ota is signed by HTC (specifically the firmware.zip inside it)
I'm working on fixing an issue with the complete dump of clean 1.94 off my device I pulled when I made the thread. Since this is an archive purposes only thread I've been slacking a bit. I have a flashable zip made, but it causes an fc upon the initial boot when calling setup and then the device will lock up.
JSLEnterprises said:
The ota is signed by HTC (specifically the firmware.zip inside it)
I'm working on fixing an issue with the complete dump of clean 1.94 off my device I pulled when I made the thread. Since this is an archive purposes only thread I've been slacking a bit. I have a flashable zip made, but it causes an fc upon the initial boot when calling setup and then the device will lock up.
Click to expand...
Click to collapse
so when will you post the link? i'd like to use this rom to test some lte related work.
Thanks!
seanwuk said:
so when will you post the link? i'd like to use this rom to test some lte related work.
Thanks!
Click to expand...
Click to collapse
I'll have it up in a couple hours, I'm currently headed out. In the meantime, use Sirius... its geared around Canadian customizations anyways.
Links Added.
Please Read Notice.
Nice work packaging it up.
What's the baseband and RIL versions if you have it flashed?
Edit: NVM, Niceppl already packaged this Badboy up for me.
Hey, Trying to flash rogers odexed, I have hboot 1.11 and it keeps erroring out During flash.
Formatting...
E:Error in /sdcard/filename.zip
(status 1)
Error flashing zip 'sdcard/filename.zip'
Updating Partition details...
Am I not supposed to flash from recovery?
um, yes. its not a ruu. so you have to flash it in recovery.
DvineLord said:
um, yes. its not a ruu. so you have to flash it in recovery.
Click to expand...
Click to collapse
I AM flashing in recovery.... It's erroring out... So messed up.
You might have a corrupted download, it happens, try downloading it again. I had issues with it on that mirror, especially if I downloaded directly to my phone.
Sent from my HTC One XL using xda premium
sixty_oz said:
You might have a corrupted download, it happens, try downloading it again. I had issues with it on that mirror, especially if I downloaded directly to my phone.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I checked the md5, was good. Turned out that TWRP 2.3.0 was the issue. Managed to update to 2.3.1 and all is working now. Oddly enough, Goo manager just would not update it so I had to do it manually.
At least all is working now. I've used a bunch of custom roms but in the end nothing is as fast and stable as Stock.
exad said:
I checked the md5, was good. Turned out that TWRP 2.3.0 was the issue. Managed to update to 2.3.1 and all is working now. Oddly enough, Goo manager just would not update it so I had to do it manually.
At least all is working now. I've used a bunch of custom roms but in the end nothing is as fast and stable as Stock.
Click to expand...
Click to collapse
I had to go through fastboot to update it on mine too!, that's funny, it worked before i unrooted and rerooted. good to know, does this rom have the menu button option?
sixty_oz said:
I had to go through fastboot to update it on mine too!, that's funny, it worked before i unrooted and rerooted. good to know, does this rom have the menu button option?
Click to expand...
Click to collapse
Nope, this is an all stock, with rogers crap removed, root and i think busybox, I cant remember if I had added it or not, if it does then it's probably 1.20.1.
JSLEnterprises said:
Links Added.
No possible way you could work on a 1.14hb configuration, I had your er3busxl on the inspire/DesireHD, and it would be nice to check this Rom out.. [/B]
Click to expand...
Click to collapse
Sent from my Venomized Elemental Evita
hello, hope you guys can help me out:
everytime i try to flash trickdroid, viperones or zenROMplus i get the same similar error in TWRP which looks like this:
Updating parition details...
Formatting Cache using mke2fs...
Done.
Formatting Data using mke2fs...
Wiping Internall SDcard
Updating parition details...
Installing '/sdcard/TrickDroid_9.0.0.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
=======================
|Welcome to TrickDroid!|
|by torxx |
=======================
Formatting paritions...
E:Error executing updater binary in zip '/sdcard/Trick
Error flashing zip '/sdcard/TrickDroid_9.0.0.zip'
Updating partition details...
i have no problems flashing CM10 or CM10.1 nightly.
whats wrong with that?
Ville (s4) (o2 branding)
unlocked
s-off
hboot 2.13.0000
radio 1.11.50.05.28
TWRP v2.5.0.0
Flashing the Sense ROMs like TrickDroid or zenROM+ doesn't work in TWRP versions above 2.3.3.0.
Don't ask me why, but it doesn't work. You can temporarily flash it in an older recovery
fastboot boot recoveryname.img
Aah ok thanks! Didnt know that this was a well known problem with twrp v2.5+, because i didnt find such an error on google. Could u tell which recovery i should use? CWM or better lower twrp version? Is a twrp version lower than 2.3 buggy or fine?
turnschuh said:
Aah ok thanks! Didnt know that this was a well known problem with twrp v2.5+, because i didnt find such an error on google. Could u tell which recovery i should use? CWM or better lower twrp version? Is a twrp version lower than 2.3 buggy or fine?
Click to expand...
Click to collapse
TWRP 2.3.3.0 is the beat IMO. It works fine for me and is very stable.
Sent from my One S using Tapatalk 2
Ah, that explains the issue I've been having recently. Thanks for the help! I reverted to 2.3.3 and was able to get viper to flash again. I haven't noticed any difference between 2.3.3 and 2.5 on this device. Are there any downsides to keeping 2.3.3 for the foreseeable future?
HOSer_hut said:
Ah, that explains the issue I've been having recently. Thanks for the help! I reverted to 2.3.3 and was able to get viper to flash again. I haven't noticed any difference between 2.3.3 and 2.5 on this device. Are there any downsides to keeping 2.3.3 for the foreseeable future?
Click to expand...
Click to collapse
It's quicker to wipe on the newer one, but other than that it's the same. (Save for a few UI elements)
Sent from my One S using Tapatalk 2
The major change is the addition of otg in versions above 2.4
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2
Thank you guys. i was able to flash it with CWM Now i want twrp 2.3.3.0 but didnt find any download link on the official site nor on trusted sites like this forum. Can someone help me out again? (last question from me in this thread^^) thanks in advance!
turnschuh said:
Thank you guys. i was able to flash it with CWM Now i want twrp 2.3.3.0 but didnt find any download link on the official site nor on trusted sites like this forum. Can someone help me out again? (last question from me in this thread^^) thanks in advance!
Click to expand...
Click to collapse
On the TWRP website, search for Ville and you'll find all the previous versions (not the goo.im app link)
oh lol yea found it thanks, think im blind sometimes..
Yes!! Back in action
Awesome! So glad I stumbled onto this thread. The Google searches were all coming up with nothing until this one. I was using 2.6.1.0 when I initially had this issue then upgraded to 2.6.3.0 hoping that would resolve but nothing. Rolled back to 2.3.3.0 and now I'm good to go :good:
Just FYI, to anyone else that comes after me this fix worked for me and I'm using a T-Mo Galaxy S2 so this fix is not device-specific.
The issue I'm running into is that I can't figure out how to revert to 2.3.3.0. I'm using 2.6.0.0 and in the cmd prompt I type "fastboot erase cache" and then "fastboot flash recovery xxxxxx.zip". But when I do that I'm forever stuck in fastboot until I flash 2.6.0.0 again. It's like my HOX+ is married to that version and can't use anything else. Any help would be greatly appreciated.
aaron79att said:
The issue I'm running into is that I can't figure out how to revert to 2.3.3.0. I'm using 2.6.0.0 and in the cmd prompt I type "fastboot erase cache" and then "fastboot flash recovery xxxxxx.zip". But when I do that I'm forever stuck in fastboot until I flash 2.6.0.0 again. It's like my HOX+ is married to that version and can't use anything else. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Fasboot flashing needs to be .img not .zip
extract your 2.33 zip so that you can flash the .img
fastboot flash recovery recovery.img (typing the name of recovery.img)
or download the img file from twrp website
http://teamw.in/project/twrp2
click on the "get twrp for your device" on the right and follow the links to the version you want for your particular brand of phone.
tivofool said:
Fasboot flashing needs to be .img not .zip
extract your 2.33 zip so that you can flash the .img
fastboot flash recovery recovery.img (typing the name of recovery.img)
or download the img file from twrp website
click on the "get twrp for your device" on the right and follow the links to the version you want for your particular brand of phone.
Click to expand...
Click to collapse
Thanks for the reply, tivo. My mistake on the .zip. I meant .img. I made sure to download the correct version, but still have the same issue. I just get stuck on the white HTC development screen. So, I can get into bootloader and TWRP (2.6.0.0 only), but can't flash ROMs. I'm just stuck with no OS and can't seem to find a work-around. My bootloader says Tampered and Unlocked/S-On. I did, however, use an unlock guide for the One X by accident, instead of the X+. That is the only thing I can think that would cause my troubles...
charliearthur said:
Awesome! So glad I stumbled onto this thread. The Google searches were all coming up with nothing until this one. I was using 2.6.1.0 when I initially had this issue then upgraded to 2.6.3.0 hoping that would resolve but nothing. Rolled back to 2.3.3.0 and now I'm good to go :good:
Just FYI, to anyone else that comes after me this fix worked for me and I'm using a T-Mo Galaxy S2 so this fix is not device-specific.
Click to expand...
Click to collapse
sorry how to revert back? I have TWRP 2.5.0.0
Edit:Nevermind I found out, but that wasn't the case for me I'm trying to flash liquid jb v2.37 and after I downgraded twrp ,I've still got an error (error 7)...
How do i get 2.3.3 when the goo.im page only goes back to 2.5 for my device? Also is this solution still relevant for flashing an AOKP 4.4 kit kat nightly rom on the Sprint HTC One (m7wls/m7spr)
usaff22 said:
TWRP 2.3.3.0 is the beat IMO. It works fine for me and is very stable.
Sent from my One S using Tapatalk 2
Click to expand...
Click to collapse
tried to find this on the link for a T-Mobile phone, but it only has nexus 7. So I googled it and every carrier seems to have the previous versions on techerrata EXCEPT T-Mobile.
Any help would be appreciated
Learnerspermit said:
tried to find this on the link for a T-Mobile phone, but it only has nexus 7. So I googled it and every carrier seems to have the previous versions on techerrata EXCEPT T-Mobile.
Any help would be appreciated
Click to expand...
Click to collapse
If you just search [ville] on the TWRP website, it should have the One S recovery you need. It doesn't matter if you have the T-Mobile of the International version.
usaff22 said:
If you just search [ville] on the TWRP website, it should have the One S recovery you need. It doesn't matter if you have the T-Mobile of the International version.
Click to expand...
Click to collapse
Sorry for not mentioning that part as well.
Went to the TWRP site and see NO SEARCH ENGINE, nor anything there that says Ville. Nor Googling TWRP ville.
Learnerspermit said:
Sorry for not mentioning that part as well.
Went to the TWRP site and see NO SEARCH ENGINE, nor anything there that says Ville. Nor Googling TWRP ville.
Click to expand...
Click to collapse
On the TWRP site, look for the "Get TWRP for your device" button in the upper right hand corner. Then that should bring up the search function:
{
"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"
}
Hello everyone,
I had installed CM10.1 some time ago, everything was good except some Wi-Fi problems which I somehow fixed with Bubba kernel. I decided to update my build after staying for a long time on the same one. So I downloaded the latest CM10.1 nightly, went on to install it, only to get surprised by a red sign on the recovery screen saying that the kernels don't match or is not compatible (or something similar). So I searched around to find a way to update my kernel but I was very confused with the guides I found, and as a result, I turned to TrickDroid with Sense 5, which I'm currently on.
It's time now to update again but I'm still confused about the whole thing. I have no idea where to start and that's the reason you're reading this thread right now.
My hboot is 1.13 and my baseband 0.16 (Europe). Also, I'm S-On and not SuperCID-ed.
Chris95X8 said:
Hello everyone,
I had installed CM10.1 some time ago, everything was good except some Wi-Fi problems which I somehow fixed with Bubba kernel. I decided to update my build after staying for a long time on the same one. So I downloaded the latest CM10.1 nightly, went on to install it, only to get surprised by a red sign on the recovery screen saying that the kernels don't match or is not compatible (or something similar). So I searched around to find a way to update my kernel but I was very confused with the guides I found, and as a result, I turned to TrickDroid with Sense 5, which I'm currently on.
It's time now to update again but I'm still confused about the whole thing. I have no idea where to start and that's the reason you're reading this thread right now.
My hboot is 1.13 and my baseband 0.16 (Europe). Also, I'm S-On and not SuperCID-ed.
Click to expand...
Click to collapse
Why not flash the boot.img from the New Build.zip as you are S-ON?
khan.orak said:
Why not flash the boot.img from the New Build.zip as you are S-ON?
Click to expand...
Click to collapse
Obviously I tried that with no luck.
But here's the thing. The CM thread says "you need to update your firmware to use the 3.4x kernel click me". I followed the tutorial provided and the update did not work. That's where I'm stuck.
Chris95X8 said:
Obviously I tried that with no luck.
But here's the thing. The CM thread says "you need to update your firmware to use the 3.4x kernel click me". I followed the tutorial provided and the update did not work. That's where I'm stuck.
Click to expand...
Click to collapse
Aahhh yess
Can you just run an RUU from your carrier? That's a one-stop solution: will upgrade your firmware and HBOOT and you should be good to go.
Sent from my HTC One S using Tapatalk 4 Beta
Can you guide me please?
I found a page with a bunch of RUUs but I don't know which one to run. Also, my One S was carrier locked but I unlocked it by following a tutorial I found in the forum. Does that mean I should run a carrier RUU?
Sent from my HTC One S using Tapatalk 4
Chris95X8 said:
Can you guide me please?
I found a page with a bunch of RUUs but I don't know which one to run. Also, my One S was carrier locked but I unlocked it by following a tutorial I found in the forum. Does that mean I should run a carrier RUU?
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Okay. Sure.
First, You will have to tell me your CID. You can find that out by getting CID GETTER from play store. It should tell you your CID in RED color.
Also, you run the RUU, it will upgrade you plus get you on stock, afterwards, IF it is locked again, you can unlock it and flash CM latest nightlies again. So no biggie there.
Hey thank you very much for your time.
The app says my CID is H3G_001
Sent from my HTC One S using Tapatalk 4
Chris95X8 said:
Hey thank you very much for your time.
The app says my CID is H3G_001
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
I suppose that is Three (3) UK .
Okay, I found that there is no JellyBean RUU for your carrier. Same as they did with HTC One X.
But here's the deal, after relocking your bootloader, you can use This RUU which is an ICS RUU.
It will bring you to Stock ICS without changing your HBOOT and firmware. Afterwards, you should check for System Updates and receive JellyBean OTA. So that will take you to JellyBean + 2.15.0000 HBOOT + Newer Firmware.
OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4
Chris95X8 said:
OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Yeah, that's right.
Yes, udpdate through WiFi as it is a big update to JB OTA. works everywhere.
---------- Post added at 05:12 PM ---------- Previous post was at 05:10 PM ----------
Chris95X8 said:
OK so if I get it right... I lock my bootloader, run that RUU which will bring me back to ICS, update through OTA (does that work everywhere?) and then just do the rooting and recovery stuff again and install the latest CM build. Alright, I'll give it a shot!
Sent from my HTC One S using Tapatalk 4
Click to expand...
Click to collapse
Also, I'll advise that you do a complete backup after you update to JellyBean, as I can see no JellyBean RUU/OTA for your carrier. So in case of any problems, you can restore NANDroid backups.
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.
khan.orak said:
Also, I'll advise that you do a complete backup after you update to JellyBean, as I can see no JellyBean RUU/OTA for your carrier. So in case of any problems, you can restore NANDroid backups.
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.
Click to expand...
Click to collapse
You see, I got this One S from the UK locked to Three but I live elsewhere, so I unlocked with a method I found on the forums. Does the process change at all?
Chris95X8 said:
You see, I got this One S from the UK locked to Three but I live elsewhere, so I unlocked with a method I found on the forums. Does the process change at all?
Click to expand...
Click to collapse
nope. I think you should be able to unlock it using This method IF it locks after the update.
But before doing any stuff (unlocking, rooting etc), make nandroid backups of the new JB ROM. People have to strive really hard in absence of RUU, OTA.zip and NANDroids.
khan.orak said:
nope. I think you should be able to unlock it using This method IF it locks after the update.
But before doing any stuff, make nandroid backups. People have to strive really hard in absence of RUU, OTA.zip and NANDroids.
Click to expand...
Click to collapse
That's how I did it :laugh:
Chris95X8 said:
That's how I did it :laugh:
Click to expand...
Click to collapse
Great. shouldn't be a problem then.
khan.orak said:
So, after JB update, flash a custom recovery (TWRP 2.3.3.0 preferable), before rooting and any other stuff, do a complete backup of BOOT+SYSTEM.
Click to expand...
Click to collapse
From what I see, TWRP needs root to install now (with the GooManager app). When I first installed it, I did it with a fastboot command since the recover was an image file.
Chris95X8 said:
From what I see, TWRP needs root to install now (with the GooManager app). When I first installed it, I did it with a fastboot command since the recover was an image file.
Click to expand...
Click to collapse
what recovery do you have right now?
khan.orak said:
what recovery do you have right now?
Click to expand...
Click to collapse
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Why do you suggest 2.3.0.0 though? Can't I update to the latest one (2.6)?
Chris95X8 said:
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Click to expand...
Click to collapse
If you want to root your device, just flash a flashable SuperSU.zip from recovery. Instant root.
---------- Post added at 03:44 PM ---------- Previous post was at 03:39 PM ----------
Chris95X8 said:
TWRP actually. But it's ok, I found this. I thought the RUU would restore the HTC recovery.
Why do you suggest 2.3.0.0 though? Can't I update to the latest one (2.6)?
Click to expand...
Click to collapse
actually, I have been having issues with 2.6.0.0 flashing Carbon ROM. PACman worked fine. Can't say anything. Both worked okay with 2.3.3.0. You may give the latest a try.
Ughhh what the hell is this now. The RUU can't run.
I locked the bootloader, went on to run the RUU and this happened...
{
"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"
}
Chris95X8 said:
Ughhh what the hell is this now. The RUU can't run.
I locked the bootloader, went on to run the RUU and this happened...
Click to expand...
Click to collapse
Oh. Just yesterday, some folks reported unsuccessful and corrupt RUU downloads from androidruu site.
You may use this one Here
Disclaimer:
By flashing this tool you take full responsibility to whatever happens on your device. The developer will NOT be held responsible to whatever happens on your device. Of course, this tool has been tested but whatever happens on your device will not be held against the developer.
*NOTE*
If you Want Want To See A Recovery That not in Here Just Ask
Be Sure You Have A HTC One S
Now HBOOT 2.16 & 2.15 Compatible
FOR NOW ALL RECOVERYS ARE 2.16 HBOOT ONLY I WILL UPDATE IT AFTER I GET MOST OF 2.15
About:One day while on xda I saw a recovery switcher made by another xda user so I Said to my self "hay i want that"
so After Messing With Stuff I Was Done With my Own Recovery Switcher Enough taking go a head and flash and have fun IF you like my development please follow my project from desktop , by going on the first page of this thread and pressing from the top black corner the button telling you "FOLLOW PROJECT" .
THANK YOU
Recovery In Here/BuildNumber For Hboot 2.16:
TWRP 2.6.1.0
PhilZ Touch 6.09.6
Magio TWRP Recovery 2.6.1.0
Recovery In Here For Hboot 2.15:
PhilZ Touch 6.12.8
TWRP 2.7.0.0
Recovery In Here For Both Hboots:
Stock Recovery
Unofficial TWRP 2.7.1.2
Features:
[*]Switch Pre Built Recovery Made For Your Device On The Fly
[*]No More Flashing recovery's In Fastboot
Changelog:v6 - 7/19/14:
Code clean ups
Updated Unofficial TWRP to 2.7.1.2 Recovery For AOSP For Both Hboot 2.15/2.16
v5.1 - 5/14/14:
Code clean ups
v5.0 - 5/7/14:
Added Unofficial TWRP 2.7.0.8 Built By @mdmower
v4.0 - 4/16/14:
Added Unofficial TWRP 2.7.0.5 Built By @mdmower
v3.0 - 3/12/14:
Added Stock recovery For RUUs
Added TWRP 2.7
v2.0 - 3/9/14:
Now Hboot 2.15 Compatible
ClockworkMod
New Splash Screen
Code Clean Ups
v1.0 - 2/23/14:
Initial Release
Downloads: Recovery Switcher_v6
MD5 44236e1ec56c5371f34bc754cc24310e
Recovery Switcher_v5.1
MD5 e63bc2792dcaad961b8d2994abb72c4f
Recovery Switcher_v5
MD5 f0c0105a785b1bfc019b89e9f533c672
Recovery Switcher_v4
MD5 0e3eb7459a1d5db5b0934735a2266d37
Recovery Switcher_v3
MD5 6d69c269575d6956ecc6590280f913bf
Recovery Switcher_v2
MD5 bc79cf15486fbe270e596b98bcbe7ae3
Recovery Switcher_v1
MD5 bf922be9d30667e420e8787b0aedb43b
Don't forget to hit the thanks button, I have worked very hard on this
Instructions:
Download the zip
Boot into recovery
Install It like you would with a Mod Or Rom
Then Set The Check Box At the end With Reboot In To System
Then Boot Back In to recovery and See your new recovery
Thanks To/Credits:
amarullz - For Aroma Installer
@CNexus - For The Idea
Phil3759 - For Philz Recovery
LlabTooFeR - For Twrp Recovery
@wapvirus - For The Splash Screen
@rc420head - Thanks For Testing
@mdmower - For Unofficial TWRP 2.7.0.5 @Venomtester - For The Op Pictures
@glencoco
XDA:DevDB Information
[AROMA]Recovery Switcher[2014-02-23], a Tool/Utility for the HTC One S
Contributors
Flashalot, rc420head
Version Information
Status: Stable
Stable Release Date: 2014-03-09
Created 2014-02-23
Last Updated 2014-03-12[/CENTER]
This looks like a great tool, many thanks.
I am currently on TWRP 2.6.1 that was bundled with Maximus10HD during the hboot 2.16 upgrade.
My main gripe about this recovery is that you are no longer able to transfer files to the internal memory whilst in recovery mode, which is a real pain for obvious reasons if your phone won't boot. However I'm unaware if this is an hboot 2.16 limitation or just the recovery I am using.
Do either of the other two recoveries you have included allow file transfer with ADB sideloading, ie as per hboot 2.15?
RichardW1992 said:
This looks like a great tool, many thanks.
I am currently on TWRP 2.6.1 that was bundled with Maximus10HD during the hboot 2.16 upgrade.
My main gripe about this recovery is that you are no longer able to transfer files to the internal memory whilst in recovery mode, which is a real pain for obvious reasons if your phone won't boot. However I'm unaware if this is an hboot 2.16 limitation or just the recovery I am using.
Do either of the other two recoveries you have included allow file transfer with ADB sideloading, ie as per hboot 2.15?
Click to expand...
Click to collapse
Unfortunately no none of the recovers for 2.16 are able to mount in recovery but they all can have Rom pushed by adb
Also I would highly recommend a usb otg cable works great no matter the recovery
Sent from a potato running Android
I was using, actually tried, recovery switchers called a b and c, with three recoveries in each, but have never succeeded to change recovery from recovery. I had a same tought - great tool. But in vain. Now i have it. Thanksalot @Flashalot
Востани Сербие, востани царице
Noob question. I've been putting off upgrading my ROM because of the mount USB storage issue with the new firmwares. How do I go about accessing my USB storage with an OTG cable?
ThR1LL said:
Noob question. I've been putting off upgrading my ROM because of the mount USB storage issue with the new firmwares. How do I go about accessing my USB storage with an OTG cable?
Click to expand...
Click to collapse
Well if your talking about recovery then if in twrp go to mounts and mount it same as philz but if it's your ROM then I think you should take it up to the developer who made it may I ask what ROM you are on
Sent from my SPH-L710 using Tapatalk
{
"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"
}
New build I will release it in a few hr
Sent from my SPH-L710 using Tapatalk
Update as been released check op for change log
Also thank @wapvirus for the new splash screen
Flashalot said:
Update as been released check op for change log
Also thank @wapvirus for the new splash screen
Click to expand...
Click to collapse
Sorry Flahalot but the downloadname is wrong ( it's 1 instead 2 ).
Please correct it.
Thanks again for your useful works.
Paolo
Update as been released check op for change log
Update Released Check op for changelog
Sent from my Nexus 7 using Tapatalk
Flashalot said:
Update Released Check op for changelog
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
do you know what is different in twrp 2.7.0.5?
dd98 said:
do you know what is different in twrp 2.7.0.5?
Click to expand...
Click to collapse
Unofficial 2.7.0.5: Important changes since official 2.7.0.0
Charging LED indicator while in recovery
Better handling of .android_secure (for non-data/media)
Fix backup of /data could fail in some rare cases (for data/media)
Fix only one CPU core enabled
Unofficial 2.7.0.5: Known issues and limitations
Off-mode charging does not display charging images; the LED works though.
http://mdmower.cmphys.com/twrp-ville/
Due To cm changing stuff flashing any of the twrps and then flashing a cm based ROM will end an a error I will have to update it once I get some time
Sent from my One S using Tapatalk
Minor Update Released Check op for change log ?
Sent from my Nexus 7 using Tapatalk
Flashalot said:
Minor Update Released Check op for change log ?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
First try --> softbrick sdacard Could be easily solved without data loss. Great work, thx a lot
-> Aroma crashed at 90% while installing latest TWRP 2.15 .. and sorry I have no log for you.
LS.xD said:
First try --> softbrick sdacard Could be easily solved without data loss. Great work, thx a lot
-> Aroma crashed at 90% while installing latest TWRP 2.15 .. and sorry I have no log for you.
Click to expand...
Click to collapse
OK I'll take a look at it and if you could pull a log with adb while your running it or save the log really helps me out
Sent from my One S using Tapatalk
Found out what happened switched the 2.16 with 2.15 vice versa so that's why there's errors will fix and reupload
Sent from my One S using Tapatalk
Flashalot said:
Found out what happened switched the 2.16 with 2.15 vice versa so that's why there's errors will fix and reupload
Sent from my One S using Tapatalk
Click to expand...
Click to collapse
Any news on the new version?
My windows 7 machine crashed so I don't have working fastboot now.
Would be great to be able to flash twrp 2.7.0.8 without fastboot
Sent from my One S using XDA Free mobile app
mmarkvoort said:
Any news on the new version?
My windows 7 machine crashed so I don't have working fastboot now.
Would be great to be able to flash twrp 2.7.0.8 without fastboot
Sent from my One S using XDA Free mobile app
Click to expand...
Click to collapse
Ya sorry I'm busy with aosp and recovery switcher on my m8 but I fix it in a bit
Sent from my One S using Tapatalk
I made advanced stock kernel and TWRP for Xperia X Compact.
I don't have X Compact, so there will be no further update.
Please don't ask for update.
Advanced stock kernel
-For 34.1.A.1.198
-ric, dm-verity disabled
-DRM patch from tobias.waldvogel
-SELinux Permissive
-Load recovery from recovery (FOTAKernel) partition
Download:
https://drive.google.com/open?id=0B0j3VJ1Xp5N8bl9xbEFxN1N1Vkk
TWRP 3.0.2
-Fully supports decryption
Download:
https://drive.google.com/open?id=0B0j3VJ1Xp5N8M1ZGbzBBMTdyRnM
1. Reboot into recovery or bootloader
2. Extract boot.img from zip and run this command in fastboot mode:
fastboot flash boot boot.img
If you have no recovery, you also need to flash recovery by this command:
fastboot flash recovery TWRP-3.0.2-2-F5321.img
3. Reboot
4. Done!
* Press volume up or down key when LED is orange to enter into recovery
Kernel source:
https://github.com/AndroPlus-org/android_kernel_sony_msm8956/tree/34.1.A.1.198
Device tree for TWRP:
https://github.com/AndroPlus-org/android_device_sony_kugo
PayPal:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=S2LALLRARKTKC
Credit:
tobias.waldvogel for awasome DRM patch,
nilezon for boot script
Snow_Basinger for testing
and big thanks to other people involved including Sony and TeamWin
AndroPlus said:
I made advanced stock kernel and TWRP for Xperia X Compact.
I don't have X Compact, so there will be no further update.
Please don't ask for update.
Advanced stock kernel
-For 34.1.A.1.198
-ric, dm-verity disabled
-DRM patch from tobias.waldvogel
-SELinux Permissive
-Load recovery from recovery (FOTAKernel) partition
Download:
https://drive.google.com/open?id=0B0j3VJ1Xp5N8bl9xbEFxN1N1Vkk
TWRP 3.0.2
-Fully supports decryption
Download:
https://drive.google.com/open?id=0B0j3VJ1Xp5N8YWJsVGZTc0ZhZUE
1. Reboot into recovery or bootloader
2. Extract boot.img from zip and run this command in fastboot mode:
fastboot flash boot boot.img
If you have no recovery, you also need to flash recovery by this command:
fastboot flash recovery TWRP-3.0.2-2-F5321.img
3. Reboot
4. Done!
* Press volume up or down key when LED is orange to enter into recovery
Kernel source:
https://github.com/AndroPlus-org/android_kernel_sony_msm8956/tree/34.1.A.1.198
Device tree for TWRP:
https://github.com/AndroPlus-org/android_device_sony_kugo
PayPal:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=S2LALLRARKTKC
Credit:
tobias.waldvogel for awasome DRM patch,
nilezon for boot script
Snow_Basinger for testing
and big thanks to other people involved including Sony and TeamWin
Click to expand...
Click to collapse
this is only for unlocked bootloader?
x10isrooted said:
this is only for unlocked bootloader?
Click to expand...
Click to collapse
yes.
I've unlocked the bootloader and have access to recovery. Am I able to root this thing then?
mesajoejoe said:
I've unlocked the bootloader and have access to recovery. Am I able to root this thing then?
Click to expand...
Click to collapse
To root, just install SuperSu zip in TWRP (search it)
mesajoejoe said:
I've unlocked the bootloader and have access to recovery. Am I able to root this thing then?
Click to expand...
Click to collapse
So I think you unlocked the boot loader using the service delivered by Sony, correct? Okay...
But how did you deal with the DRM security keys (TA partitions)? If I get that right within the TA partition there might be some key information which could affect advanced camera functionality? Did you get a backup of the TA partition before unlocking the bootloader?
Thank you for support!
fl3xx said:
So I think you unlocked the boot loader using the service delivered by Sony, correct? Okay...
But how did you deal with the DRM security keys (TA partitions)? If I get that right within the TA partition there might be some key information which could affect advanced camera functionality? Did you get a backup of the TA partition before unlocking the bootloader?
Thank you for support!
Click to expand...
Click to collapse
You don't need to backup TA (at least when you are using) since DRM patch solves camera functionality problem.
has anyone tested this? It basically means we can:
1. unlock the bootloader
2. flash twrp recovery
3. flash this kernel
4. flash superuser
and we have a rooted x compact with working drm (at least some of it).
Is that correct?
charliebigpot said:
has anyone tested this? It basically means we can:
1. unlock the bootloader
2. flash twrp recovery
3. flash this kernel
4. flash superuser
and we have a rooted x compact with working drm (at least some of it).
Is that correct?
Click to expand...
Click to collapse
In theory yes. Though I cannot flash the superuser zip, nor can I mount anything in TWRP at the moment. Before unlocking boot loader and flashing this, I flashed UK for fingerprint sensor so that may be the reason. Tomorrow I plan on testing more.
Sent from my HTC 10
mesajoejoe said:
In theory yes. Though I cannot flash the superuser zip, nor can I mount anything in TWRP at the moment. Before unlocking boot loader and flashing this, I flashed UK for fingerprint sensor so that may be the reason. Tomorrow I plan on testing more.
Sent from my HTC 10
Click to expand...
Click to collapse
Good luck and keep us posted!
charliebigpot said:
Good luck and keep us posted!
Click to expand...
Click to collapse
No luck. It won't install the superuser.zip. In TWRP everything is red, can't mount anything. Can't see internal SD from TWRP, can't format anything. I went back to Customized US from xperifirm and re-flashed kernel and TWRP. Not sure what to do.
{
"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"
}
mesajoejoe said:
No luck. It won't install the superuser.zip. In TWRP everything is red, can't mount anything. Can't see internal SD from TWRP, can't format anything. I went back to Customized US from xperifirm and re-flashed kernel and TWRP. Not sure what to do.
Click to expand...
Click to collapse
hmm, can you upload full log (tmp/recovery.log)?
I confirmed this works on F5321 but maybe there's some difference in US.
AndroPlus said:
hmm, can you upload full log (tmp/recovery.log)?
I confirmed this works on F5321 but maybe there's some difference in US.
Click to expand...
Click to collapse
Here ya go.
mesajoejoe said:
Here ya go.
Click to expand...
Click to collapse
Can you check if there is /dev/block/platform/soc/7824900.sdhci ?
e.g.
Code:
ls -l /dev/block/platform/soc/7824900.sdhc
AndroPlus said:
Can you check if there is /dev/block/platform/soc/7824900.sdhci ?
e.g.
Code:
ls -l /dev/block/platform/soc/7824900.sdhc
Click to expand...
Click to collapse
Two things exist there. 7824900.sdhci and 7864900.sdhci Thank you BTW for looking into this. Root access is the only thing holding me back from using this device.
Sent from my HTC 10
mesajoejoe said:
Two things exist there. 7824900.sdhci and 7864900.sdhci Thank you BTW for looking into this. Root access is the only thing holding me back from using this device.
Sent from my HTC 10
Click to expand...
Click to collapse
Thank you, I'll rebuild TWRP later with "7864900.sdhci".
I don't know why there are two path, but 7864900.sdhci should be right path for your device.
oops it was for sdcard...
AndroPlus said:
Thank you, I'll rebuild TWRP later with "7864900.sdhci".
I don't know why there are two path, but 7864900.sdhci should be right path for your device.
oops it was for sdcard...
Click to expand...
Click to collapse
Let me know if there's anything I can assist with.
mesajoejoe said:
Let me know if there's anything I can assist with.
Click to expand...
Click to collapse
Can you try this version?
https://drive.google.com/open?id=0B0j3VJ1Xp5N8M1ZGbzBBMTdyRnM
AndroPlus said:
Can you try this version?
https://drive.google.com/open?id=0B0j3VJ1Xp5N8M1ZGbzBBMTdyRnM
Click to expand...
Click to collapse
Appears to be working. I have mounting access in TWRP, flashed superuser.zip without issue. Thanks!
Well it was kind of working. On US firmware root was functioning but when switching over to UK it stopped. Since then I have not been able to regain root access on US or UK. After flashing the superuser.zip it just hangs on the Sony logo. I've gone back and forth between US and UK, but no luck. TWRP is having issues unmounting /system... not sure if that gives anyone any insight. I'm probably just going to leave it without root access for now. Appreciate your help!
Does it work on CE version
Hey everyone
Can anyone confirm that it works on CE software Version.
Unlock BL is allowed.
Thanks in advance.