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
Related
Please use this new guide to flash a new radio
http://forum.xda-developers.com/showthread.php?t=1684477
We are glad we have our unlocked devices and can happily flash Custom ROM`s, backup and restore nandroids or flash mods. Nevertheless there are still some restrictions, since we still have no S-Off. This week the latest 1.78 OTA update arrived and devs are working hard to upgrade their ROM`s to the new One S ROM base.
BUT...
assuming you already use a Custom ROM and you want to flash latest stuff, in any of these ROM`s built on latest base you will still use your old Radio, which was shipped initially. Since 1.78 OTA brought a new Radio (baseband), with S-Off it would be painless to flash it via fastboot or recovery, but we still aren`t there.
BUT...
there is a way to use latest ROM base with latest Radio. You just need to be willing to go that extra route.
What`s the benefit of upgrading a Radio?
The baseband is responsible for:
Signal quality
WiFi and Bluetooth connectivity
GPS / aGPS
Can improve battery due to improved signal quality
Can even improve camera
and more...
Who needs this?
Everyone who flashed first Custom Rom BEFORE OTA 1.78 arrived and wants to enjoy latest Baseband. Please check first, whether OTA for your region / provider is already available.
This is how you can upgrade your RADIO without S-Off
Step 1:
Make an nandroid in recovery
Step 2:
Download my stock 1.53 nandroid (maybe someone can upload to a faster mirror), unzip it and copy the folder in sdcard/clockworkmod/backup folder
http://minus.com/mquC9WDG6/4
Dropbox mirror - thx @ angelsanges
https://www.dropbox.com/s/av1w0aip9a...3_original.rar
Step 3:
Restore my Stock153Clean.zip nandroid in recovery
Step 4:
Download my fastboot folder (in case you haven`t installed SDK) and copy stock recovery image and clockwork recovery image in the unpacked fastboot folder
Fastboot folder: http://minus.com/mIA3OFkYq/3
Stock recovery: http://minus.com/mIA3OFkYq/18
Clockwork Recovery (or use another CWM version, whatever you prefer): http://minus.com/mIA3OFkYq/4
Step 5:
Boot in Bootloader (with adb reboot bootloader or Power and Vol. down) and connect your device. Navigate in cmd to your fastboot folder and flash stock recovery with:
fastboot flash recovery recovery_signed.img
Step 6:
Reboot and check for system updates in settings info (that can last a while, sometimes you need to try several times), download and install when prompted. Wait a few minutes for your device to install the update and reboot.
Step 7:
Boot in Bootloader and connect your device. Navigate in cmd to your fastboot folder and flash Clockwork recovery with:
fastboot flash recovery r2-modaco-recovery-clockwork-touch-ville.img
Step 8:
Restore your own nandroid (which does not backup and restore radio images) and now you have upgraded your Radio
Screenshot from my device running Virtuous ROM with latest Radio from 1.78 OTA Update
{
"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"
}
???????
tks, but if i have s-off ,i don't need to this way....
And Sorry, but you have the old Rom 1.70.666.1...
cosmic76 said:
tks, but if i have s-off ,i don't need to this way....
And Sorry, but you have the old Rom 1.70.666.1...
Click to expand...
Click to collapse
There's no s-off yet for One S.
Sent from my HTC One S using xda premium
cosmic76 said:
tks, but if i have s-off ,i don't need to this way....
And Sorry, but you have the old Rom 1.70.666.1...
Click to expand...
Click to collapse
I lol'd.
Some people had luck and got a device with S-OFF..
Just to let you know
yup !!! lucky b**tards!
Theres a couple people on these forums with the One S developer phone too !! Ive seen pics as proof !
Retracts Statement in Shame. Hangs head. Sorry, My bad bro. Lolz @ Self.
Thx!! Exactly what I needed But your stock ROM has such a slow download
he_stheone64 said:
Step 8:
Restore your own nandroid (which does not backup and restore radio images) and now you have upgraded your Radio
Click to expand...
Click to collapse
Sorry for the noob question,
But if I don't want to restore mi old nandroid, but i want install new ROM..I can do that by simply putting the zip in sd?
Thanks
Ivan
he_stheone64, I guess I am out of luck again and this won't work with CID T-MOB101?
any one got a mirror for the 1.53 nandroid ? got a estimated time of 5 hours left !!, also, couldnt i just use a 1.53 rom ?? its clean, untouched stock, from RUU, no root or nothing...
will i also get this update with vodafone UK CID ? VODAP100 i think it is
EDIT, The update isnt even available !! yet according to my provider it is !
i have stock ROM and stock recovery ! still no bloody update
nice, probably this will fix the umts<>hspa toggling problem i am experiencing ...
since the download of the nandroid backup takes hours i tried restoring my own backup of stock 1.53. only difference is root. the update was detected immediately after i rebooted from cwr. sadly the update process did not succeed. the progress bar stopped after ~25% and then i just got a red triangle with an exclamation mark in it. after 1-2 minutes the phone rebooted and it's still stock 1.53 with old radio. any ideas what could be missing?
i did revert to stock recovery and there was ~2gb of space left on /sdcard/
probably root?!
//edit: found the problem. i changed 3 lines in build.prop which gets patched in the update process ... removed changes (and unrooted) and now the update works.
link for the stock rom is very very slow
ZeppeMan said:
Thx!! Exactly what I needed But your stock ROM has such a slow download
Click to expand...
Click to collapse
That`s why I asked for a mirror in OP
ivyn87 said:
sorry for the noob question,
but if i don't want to restore mi old nandroid, but i want install new rom..i can do that by simply putting the zip in sd?
Thanks
ivan
Click to expand...
Click to collapse
yes you can...
AndrewSM said:
he_stheone64, I guess I am out of luck again and this won't work with CID T-MOB101?
Click to expand...
Click to collapse
As fas a I now, T-Mobile hasn`t released an update yet, so in that case you still need to be patient.
azzledazzle said:
any one got a mirror for the 1.53 nandroid ? got a estimated time of 5 hours left !!, also, couldnt i just use a 1.53 rom ?? its clean, untouched stock, from RUU, no root or nothing...
will i also get this update with vodafone UK CID ? VODAP100 i think it is
EDIT, The update isnt even available !! yet according to my provider it is !
i have stock ROM and stock recovery ! still no bloody update
Click to expand...
Click to collapse
As mentioned in the OP, check FIRST whether your provider already delivers an update. If you have a matching RUU for your device, you can flash back also with the RUU. This certainly requires some extra steps, but does the job.
he_stheone64 said:
As mentioned in the OP, check FIRST whether your provider already delivers an update. If you have a matching RUU for your device, you can flash back also with the RUU. This certainly requires some extra steps, but does the job.
Click to expand...
Click to collapse
according to my provider, its already out, but i cannot find the update.. i went back to stock rom, stock recovery, still couldnt find it...
i have downloaded the OTA update.. someone extracted it and uploaded it, but as for how to flash it.....ive no idea lol
ZeppeMan said:
Thx!! Exactly what I needed But your stock ROM has such a slow download
Click to expand...
Click to collapse
Any improvement with this new radio?
he_stheone64 said:
As fas a I now, T-Mobile hasn`t released an update yet, so in that case you still need to be patient.
Click to expand...
Click to collapse
Thanks. Well I flashed the genuine ROM 1.53 over the stock Tmobile bloatware ROM. The OTA will work anyways when Tmo releases it? Because I've read that OTA doesn't work if the system partition has been modified...
azzledazzle said:
according to my provider, its already out, but i cannot find the update.. i went back to stock rom, stock recovery, still couldnt find it...
i have downloaded the OTA update.. someone extracted it and uploaded it, but as for how to flash it.....ive no idea lol
Click to expand...
Click to collapse
This is info I got from the guy who posted the OTA zip:
Need stock recovery to install. And you may loose root.
Root Keeper from market is said to work for keeping root. The "one click-tool" here in the development section can easily flash stock recovery for you. You can always re-flash CWM after update is installed.
And this is how you would install OTA zip file for sensation, guess it works the same way. You can give it a try, I can't since I don't have matching CID (the list of supported CIDs is in the OTA zip file in firmware.zip): http://forum.xda-developers.com/showpost.php?p=16862231&postcount=1
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"
}
this is happening since i rooted my htc with the supersu zip method .
so here is the problem:
when the htc's battery dies and i connect it to the wall charger or usb so it boots into recovery and then when i press reboot system now it reboots normally. (running clockworkmod touch recovery)
how do i make it boot straight into the rom without booting into recovery?
Install TWRP- 2.3.0.0 , and stay away wrom clockwork. And install custom rom, they all are properly rooted, and busybox installed.
Still have the problem
Your phone isn't properly rooted, as this zip method fails some time.
Simply grab Su_Bbox* from here and flash it in recovery. If CWM recovery fails to flash that, download TWRP recovery from the same linked folder and 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' in fastboot mode of your phone.
SU and Busybox need to be properly installed for working root. It's not only (any) SU making it!
rootrider said:
Your phone isn't properly rooted, as this zip method fails some time.
Simply grab Su_Bbox* from here and flash it in recovery. If CWM recovery fails to flash that, download TWRP recovery from the same linked folder and 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' in fastboot mode of your phone.
SU and Busybox need to be properly installed for working root. It's not only (any) SU making it!
Click to expand...
Click to collapse
i saw you have a file called ville recovery signed is it the stock recovery?
LSGio said:
i saw you have a file called ville recovery signed is it the stock recovery?
Click to expand...
Click to collapse
Yes!
rootrider said:
Yes!
Click to expand...
Click to collapse
is it compatible with the s4 or s3 htc one s?
S4
--- edit ---
Whatever device you have, SU_Bbox will work on any phone, as it is device unindependant!!!
rootrider said:
S4
Click to expand...
Click to collapse
now im flashing the bbox file and gonna see how it goes
didn't fix my problem
did this happened to you and then after flashing bbox its gone?
LSGio said:
did this happened to you and then after flashing bbox its gone?
Click to expand...
Click to collapse
I had that reboot into recovery problem some time ago... But I'm not shure about the solution now...
Well, I'd need to know a few things now.
Device? S3 S4?
Rom? Stock or custom, if custom, which rom?
Recovery? TWRP or CWM and which version?
Kernel? Custom or stock?
Bootloader version and CID?
rootrider said:
I had that reboot into recovery problem some time ago... But I'm not shure about the solution now...
Well, I'd need to know a few things now.
Device? S3 S4?
Rom? Stock or custom, if custom, which rom?
Recovery? TWRP or CWM and which version?
Kernel? Custom or stock?
Bootloader version and CID?
Click to expand...
Click to collapse
device S4
Stock Rom
CWM recovey version 5.8.3.1
stock kernel
don't know how to check the BL and cid version
and one more important thing:
i fully unrooted the device (an option is available through the superSU app) and it still shows tampered and still booting into recovery
LSGio said:
device S4
Stock Rom
CWM recovey version 5.8.3.1
stock kernel
don't know how to check the BL and cid version
and one more important thing:
i fully unrooted the device (an option is available through the superSU app) and it still shows tampered and still booting into recovery
Click to expand...
Click to collapse
if you have skype it would be easier mine is:
lior_shvartz2
LSGio said:
device S4
Stock Rom
CWM recovey version 5.8.3.1
stock kernel
don't know how to check the BL and cid version
and one more important thing:
i fully unrooted the device (an option is available through the superSU app) and it still shows tampered and still booting into recovery
Click to expand...
Click to collapse
Ok, stock JB would mean that there is a write protection, invented with HTCs JB update (as long as you're using the stock kernel...).
To solve this, you'd need to flash any sense custom kernel (bricked, bulletproof, ElementalX). I'd recommend bulletproof (close to stock so).
BL and CID can be checked by starting bootloader mode. You'll see it below the tampered flag.
As Fanagoreca already mentioned, you should flash TWRP recovery (the one from my link above is 2.3.3.0, working good and for S4) by booting into fastboot mode and entering 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' from terminal/command window.
After that you should flash a custom kernel to remove write protection, either in recovery or fastboot mode ('fastboot flash boot boot.img'). But through recovery should work.
Then flash SU_Bbox again from TWRP. The point is, I don't know if your version of CWM works as it should. Since the time this phone came out, CWM always had bugs and wasn't working in some ways. TWRP was pretty good to go with up to 2.3.3.0, after that version it started to become buggy for some things.
So just give it a try. I think it's not a big problem.
--- edit ---
Sorry, don't have skype.
---------- Post added at 09:50 AM ---------- Previous post was at 09:38 AM ----------
...
BL version comes into game, if you're s-on. Versions > 1.09 make it necessary to flash the kernel separately from your rom in fastboot mode. Else your system won't start, as there is no kernel...
Usually you'd unzip the kernel (aka boot.img) from your rom.zip and flash it with: 'fastboot flash boot boot.img' in fastboot mode.
CID will be relevant for receiving OTA updates or gaining s-off. So it's not that important this time.
rootrider said:
Ok, stock JB would mean that there is a write protection, invented with HTCs JB update (as long as you're using the stock kernel...).
To solve this, you'd need to flash any sense custom kernel (bricked, bulletproof, ElementalX). I'd recommend bulletproof (close to stock so).
BL and CID can be checked by starting bootloader mode. You'll see it below the tampered flag.
As Fanagoreca already mentioned, you should flash TWRP recovery (the one from my link above is 2.3.3.0, working good and for S4) by booting into fastboot mode and entering 'fastboot flash recovery openrecovery-twrp-2.3.3.0-ville.img' from terminal/command window.
After that you should flash a custom kernel to remove write protection, either in recovery or fastboot mode ('fastboot flash boot boot.img'). But through recovery should work.
Then flash SU_Bbox again from TWRP. The point is, I don't know if your version of CWM works as it should. Since the time this phone came out, CWM always had bugs and wasn't working in some ways. TWRP was pretty good to go with up to 2.3.3.0, after that version it started to become buggy for some things.
So just give it a try. I think it's not a big problem.
--- edit ---
Sorry, don't have skype.
---------- Post added at 09:50 AM ---------- Previous post was at 09:38 AM ----------
...
BL version comes into game, if you're s-on. Versions > 1.09 make it necessary to flash the kernel separately from your rom in fastboot mode. Else your system won't start, as there is no kernel...
Usually you'd unzip the kernel (aka boot.img) from your rom.zip and flash it with: 'fastboot flash boot boot.img' in fastboot mode.
CID will be relevant for receiving OTA updates or gaining s-off. So it's not that important this time.
Click to expand...
Click to collapse
im using ics right now (4.0.3) so i want to unroot and relock BL to update but firsst i want so solve this problem.
if i'll update will it fix my problem?
one more question:
the bootloader version is the HBOOT version? if it does so mine is 1.13
LSGio said:
im using ics right now (4.0.3) so i want to unroot and relock BL to update but firsst i want so solve this problem.
if i'll update will it fix my problem?
one more question:
the bootloader version is the HBOOT version? if it does so mine is 1.13
Click to expand...
Click to collapse
The update won't fix your problem. I think it's recovery related. So changing the recovery might solve it. You still should try that first. For running RUUs or OTA update you will need to flash custom recovery and relock bootloader. The tampered flag can only be removed when you s-off your device.
HBOOT version is bootloader version, here 1.13.
Which country you are living in? Be warned, that when you flash the latest OTA update (JB) from TMO US your partition for writing CID will be locked. And if you can't superCID your phone anymore, you will not be able to get s-off!
You should consider superCID'ing and getting s-off first. Once being s-off you can do anything with your phone.
rootrider said:
The update won't fix your problem. I think it's recovery related. So changing the recovery might solve it. You still should try that first. For running RUUs or OTA update you will need to flash custom recovery and relock bootloader. The tampered flag can only be removed when you s-off your device.
HBOOT version is bootloader version, here 1.13.
Which country you are living in? Be warned, that when you flash the latest OTA update (JB) from TMO US your partition for writing CID will be locked. And if you can't superCID your phone anymore, you will not be able to get s-off!
You should consider superCID'ing and getting s-off first. Once being s-off you can do anything with your phone.
Click to expand...
Click to collapse
i fixed my problem by updating trough OTA to JB (im from israel)
and btw you said that i should install custom recovery and relock to update but it failed so i flashed the stock recovery and than relocked and i achieved success.
do you have an idea when sense 5 is coming out to our device ?
LSGio said:
i fixed my problem by updating trough OTA to JB (im from israel)
and btw you said that i should install custom recovery and relock to update but it failed so i flashed the stock recovery and than relocked and i achieved success.
Click to expand...
Click to collapse
oops, sorry, you're right. I meant stock recovery but wrote custom.
LSGio said:
do you have an idea when sense 5 is coming out to our device ?
Click to expand...
Click to collapse
The first thing going on will be 4.2.2 and sense 5 for the m7 (one) in may or june. The One X will get updated to that as well around one month later, including blinkfeed and zoe. The One S will also be updated to Sense 5 but if there will be blinkfeed and zoe might be doubted. I personally think that this will be 4.2.2 as well.
I can't find the sources for that anymore, but I was reading about that yesterday or the day before.
rootrider said:
oops, sorry, you're right. I meant stock recovery but wrote custom.
The first thing going on will be 4.2.2 and sense 5 for the m7 (one) in may or june. The One X will get updated to that as well around one month later, including blinkfeed and zoe. The One S will also be updated to Sense 5 but if there will be blinkfeed and zoe might be doubted. I personally think that this will be 4.2.2 as well.
I can't find the sources for that anymore, but I was reading about that yesterday or the day before.
Click to expand...
Click to collapse
ok thank you for all this info now what is the proccess to S-OFF'ing my device
these are my device's stats:
{
"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"
}
And Hboot version is 2.15
CPU: S4
And i'm also using the latest hasoon2000's toolkit which looks like this:
UP!!
Go Here for instructions to S-Off
Hello,
I have been running the Milestone1 rom for AOKP for a while now. Everything is running dandy. I wanted to try out the nightly builds, specifically the aokp_evita_ unofficial_2013-07-08.zip
I have the bootloader unlocked as well as s-off
When i try to install that rom, it always ends up failed.
This what I see in TWRP 2.6.0.0
Updating partitions details...
running boot script..
Finished running boot script.
installing '/sdcard/aokp_evita_unofficial_2013-0708.zip'...
checking for MD5 file...
skipping MD5 check: no MD5 file found
assert failed: getprop("ro.bootloader") == "2.14.00"
E:Error executing updater binary in zip '/sdcard/aokp_evita_unofficial_2
Error flashing zip '/sdcard/aokp_evita_unofficial_2013-07-08.zip'
Updating partition details
Click to expand...
Click to collapse
I have h-boot 1.11.0000
I'm completely lost.
any help would be greatly appreciated.
Thanks
You need to upgrade to the 3.18 ruu. Since you're S-Off you should be good to go, just run it and flash AOKP.
RollTribe said:
You need to upgrade to the 3.18 ruu. Since you're S-Off you should be good to go, just run it and flash AOKP.
Click to expand...
Click to collapse
Im on a rogers one x. How and where can i get 3.18 RUU?
buhbuh said:
Im on a rogers one x. How and where can i get 3.18 RUU?
Click to expand...
Click to collapse
Download and run this RUU: (Do not relock bootloader, it is not needed with S-OFF)
http://bugsylawson.com/files/file/2...s320928l-101033224l-release-268972-signedexe/
Then you can either check for updates within your stock rom right after or download and install This OTA through the stock recovery which you can download here:
http://fotadl.htc.com/OTA_EVITA_UL_...128.32.34a_release_299850qstr7rxdbfuofl6j.zip
I would imagine you know how to check for the OTA on your phone.
But if you plan to download the OTA and flash it manually, you will want to copy The OTA zip file to your SD card.
Boot to your bootloader then select recovery.
When you get an image on your screen press and hold volume up and then press power. You will see a message that SD card could not be mounted. This is normal.
Then you will be in Stock recovery.
Select install update from Phone storage could also be called internal storage (do not select from SD card as it will be looking for an external card and not the internal memory and it will say it could not be mounted.)
Select the OTA zip file and it will start doing stuff.
Then when done, select reboot phone and it will install the rest of the OTA and voila you will be on 2.14 hboot.
Then you can reflash twrp 2.6 and then flash your rom and smile, maybe even frolic in the streets as a result of your accomplishments.
STOP THE PRESSES! milestone1 isn't even using the 3.4 kernel......... why would op need 2.14 hboot?
*edit* Nevermind I'm an idiot. Unofficial. Follow my directions or Flash the OFFICIAL rom if you don't want to go through all that hassle.
@exad he WAS running MS and is trying to flash nightly. That's the error he got in the OP.
RollTribe said:
@exad he WAS running MS and is trying to flash nightly. That's the error he got in the OP.
Click to expand...
Click to collapse
Yeah I see it now -_- Sorry!!!
My bad everyone! My bad! As you were! Carry on and all that.
OP... You can also run this http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe ruu, this is the AT&T one. Options are good .
buhbuh said:
Im on a rogers one x. How and where can i get 3.18 RUU?
Click to expand...
Click to collapse
exad said:
Download and run this RUU: (Do not relock bootloader, it is not needed with S-OFF)
http://bugsylawson.com/files/file/2...s320928l-101033224l-release-268972-signedexe/
[/COLOR]
Click to expand...
Click to collapse
so should just download and run this RUU and then install try to install the nightly rom?
sorry for the many questions. This area is completely new to to me.
buhbuh said:
so should just download and run this RUU and then install try to install the nightly rom?
sorry for the many questions. This area is completely new to to me.
Click to expand...
Click to collapse
Yes you should follow my directions above. Sorry for confusing you
After the RUU you have to do the OTA portion too or you won't update to 3.18 or 3.17 or whatever it is for rogers.
RollTribe said:
OP... You can also run this http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe ruu, this is the AT&T one. Options are good .
Click to expand...
Click to collapse
exad said:
Yes you should follow my directions above. Sorry for confusing you
After the RUU you have to do the OTA portion too or you won't update to 3.18 or 3.17 or whatever it is for rogers.
Click to expand...
Click to collapse
thank you for all your help guys. Im going to try it and report back. thanks!
RollTribe said:
OP... You can also run this http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe ruu, this is the AT&T one. Options are good .
Click to expand...
Click to collapse
It is not recommended to run an RUU for a different carrier even if the hardware is almost exactly the same.
The device drivers may be slightly modified and I don't think canadian carrier and american carrier one x use the same radio bands. Whenever I use an AT&T radio, my phone gets crazy hot fast while using radio
Im getting error[170]: USB Connection error
I have USB debugging enabled.
Device manager sees the device.
i can adb
exad said:
It is not recommended to run an RUU for a different carrier even if the hardware is almost exactly the same.
The device drivers may be slightly modified and I don't think canadian carrier and american carrier one x use the same radio bands. Whenever I use an AT&T radio, my phone gets crazy hot fast while using radio
Click to expand...
Click to collapse
Oh I didn't know, my bad. I've always read that it's fine, but I guess it's better to be safe. H8 said it was fine, but OP can choose from what he thinks. I, personally, never had any problems but YMMV I guess.
buhbuh said:
Im getting error[170]: USB Connection error
I have USB debugging enabled.
Device manager sees the device.
i can adb
Click to expand...
Click to collapse
Try running the RUU while in fastboot.
buhbuh said:
Im getting error[170]: USB Connection error
I have USB debugging enabled.
Device manager sees the device.
i can adb
Click to expand...
Click to collapse
Also, try running it via a USB 2.0 port, not 3.0. I have all kinds of problems with 3.0.
Edit: nvm you got it working.
exad said:
Try running the RUU while in fastboot.
Click to expand...
Click to collapse
That worked.
It showing that my current image version is 1.94.631.3
Should I continue?
again sorry for asking soo many questions.
RollTribe said:
Oh I didn't know, my bad. I've always read that it's fine, but I guess it's better to be safe. H8 said it was fine, but OP can choose from what he thinks. I, personally, never had any problems but YMMV I guess.
Click to expand...
Click to collapse
You're probably right, it would probably be fine. I'm paranoid myself, and usually will go overboard with the old better safe than sorry frame of mind
---------- Post added at 09:09 PM ---------- Previous post was at 09:08 PM ----------
buhbuh said:
That worked.
It showing that my current image version is 1.94.631.3
Should I continue?
again sorry for asking soo many questions.
Click to expand...
Click to collapse
Yes, go through and let it do it's thing.
buhbuh said:
That worked.
It showing that my current image version is 1.94.631.3
Should I continue?
again sorry for asking soo many questions.
Click to expand...
Click to collapse
That should be fine, it's just your firmware version.
Edit: ah ya beat me to it.
RollTribe said:
That should be fine, it's just your firmware version.
Edit: ah ya beat me to it.
Click to expand...
Click to collapse
IM AN XDA POST NINJA BRO!!!
{
"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"
}
exad said:
IM AN XDA POST NINJA BRO!!!
Click to expand...
Click to collapse
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