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
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"
}
--->**Discontinued** HTC One S USA T-Mobile JellyBean Update * Sense 4+* Rooted * Deodexed * Aroma Installer * APM <---
* Awesome battery life
* This Rom is based off the TMOUS_3.14.531.17.70rd RUU
* Root, BusyBox, Zipalign, Unsecure boot.img, APM, Deodexed,
* Busybox, Busybox-run-parts supported, /data/app-enabled, and Bash-shell support
* Added a few startup scripts
* Added WWE Languages
* HTC ONE Sounds
* Please Read Change Log For Further Fixes, Changes, Additions.
-> I am not responsible for any phone that may become bricked. <-
** This ROM is not to be used for a base ROM **
{
"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"
}
Wallpaper Download
---------------------------------------------------------------------------
Installation Instructions
----------------------------------
Working Folders
SkyDrive
Google Drive
Android File Host Dev Account
-----------------------------------
* Download your ROM
* Put on the sdcard / Internal storage
* Fastboot flash boot boot.img (only if you are S-ON)
* Flash in recovery and use the Aroma Installer
* Done!
* If your WiFi isn't working and you are S-OFF Flash WiFi Fix S-OFF. If you are S-ON try Htc_on_s_wifi_fix-S-ON
--------------------------------------------------------
* How to backup your WiFi Partition
Code:
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Next type "dd if=/dev/block/mmcblk0p19 of=/sdcard/mmcblk0p19" and hit enter. This will dump the partition to your sdcard.
4. Next type "dd if=/dev/block/mmcblk0p18 of=/sdcard/mmcblk0p18" and hit enter. This will dump the partition to your sdcard.
5. Next type "exit", hit enter, type "exit", and hit enter again. This should take you back to a command prompt for your computer.
Now the partition's are backed up, to restore them do the following.
1. Fire up your command prompt and go to the directory that you have ADB installed to. Type "adb shell" and hit enter.
2. Type "su" and hit enter. You now have root privileges.
3. Type "dd if=/sdcard/mmcblk0p19 of=/dev/block/mmcblk0p19"
4. Type "dd if=/sdcard/mmcblk0p18 of=/dev/block/mmcblk0p18"
Now they are restored.
Please click thanks if this helped you.
--------------------------------------------------------------------------------------
* How To Root, Update Firmware, & Flash A Custom ROM
By: Mkinney88 (UnKnown_ROMS)
--> Unlock your device
Step1. download and use this program to unlock your bootloader http://forum.xda-developers.com/showthread.php?t=1604677
Step2. SuperCID your phone so you can S-OFF and so you can also write the T-MOB010 CID if you are on a different carrier and want to run this ROM. You will need to be CID T-MOB010 if you want to run the firmware.zip Follow this to SuperCID http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Step3. After you have sucessfully unlocked your bootloader and SuperCID you can either S-OFF your phone or Not, it is up to you. I would recommend you achieve S-OFF so you can flash radios, kernels, and boot.img's. Follow this to achieve S-OFF http://forum.xda-developers.com/showthread.php?t=2155135
If everything went well you should be able to reboot into bootloader using the All In One Tool and in the top left your bootloader should say Unlocked, S-OFF, CID-1111111
--> Writing T-MOB010 CID
If you did everything right then your all set. Next you will want to run the fastboot command " fastboot oem writecid T-MOB010 " and reboot into bootloader again. Now in the top left it should say CID-T-MOB010. If you have made it this far you are doing great. Now we are going to run the firmware.zip package to ensure everything works without a problem.
--> Flashing the firmware.zip
Now if you are coming from STOCK OEM LOCKED T-MOBILE PHONE that already has Andorid 4.1.1 Jelly Bean on it then you do not need to do this step. You must be CID T-MOB010 to flash this or S-OFF CID 11111111
1. fastboot oem lock
2. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip firmware.zip, and you might get an error
5. fastboot flash zip firmware.zip again and it should pass and install a bunch of files should take about 2 minutes.
6. the phone does NOT reboot on its own so #7
7. fastboot reboot or fastboot reboot-bootloader
--> UNLOCKING BOOTLOADER AGAIN
Now we need to unlock the bootloader again so just do step 1 again but you will already have the Unlock_code.bin from the first time you unlocked you phone so no need to get another one from HTC but if for some funny reason it doesn't work you will need to just resubmit for a new one.
--> CUSTOM RECOVERY
After doing all the above steps you will need to install the custom recover. You will need to use TWRP 2.3.3 to insure no problems. Here is the link to download it http://techerrata.com/file/twrp2/ville/openrecovery-twrp-2.3.3.0-ville.img after you download it go to the DIR where you have the HTC One S All-In-One Toolkit v3.5 extracted. example: C:\Users\yourusername\Downloads\One_S_All-In-One_Kit_v3.5\One_S_All-In-One_Kit_v3.5\Data\Recoveries and in the Recoveries folder rename the downloaded twrp2.3.3.img to TWRPS4.img and replace the one that is in the folder and then proceed to install the recovery.
--> Intermission
Your current phone status
Bootloader = Unlocked
S-OFF
HBOOT = 2.15
CID = T-MOB010
Custom Recovery = TWRP 2.3.3
You are now ready to flash any Jelly bean ROM / OR my ROM
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Add-On / Mods
SkyDrive // Google Drive
Advanced Power Menu (Thanks Behold_this)
Open APN
Open APN With UnKnown_AutoBrightness MOD
Removed Carrier from Default Lockscreen
Autobrightness Mod
Lower Autobrightness Mod
Ridiculosly Low Autobrightness Mod
Stock Green Battery
1% Blue Battery Mod (Thanks he_stheone64)
Volume Wake With Advanced Power Menu
Volume Long Press To Skip Tracks
Long Press Back To Kill 3rd Party Apps
Modified Roise With Menu
Transparent Rosie with Clear NavBar
Better WiFI Calling Icons
Green Power Saver Leaf LOL
Blue Power Saver Leaf LOL
Transparent Rosie (Thanks Flashalot for the Tutorial)
Transparent Notification Pull Down (Thanks Flashalot for the Tutorial)
--------------------------------------------------------------------------
--------------------------------------------------------------------------
Custom Recovery
TWRP 2.3.3 Recovery.img (Must be Unlocked)
--------------------------------------------------------------------------
---> Change Log <---
HTML:
V2.0 ***CURRENT***
* Aroma interactive installer
* App removal
* Added Open VPN support
* Added SQL3lite support
* Added memory enhancer script
* EXT4 write back
* Sense 5 icons by default
* Updated all mods with the Sense 5 icons
________________________________________
V1.9
* Re-based from 3.14.531.17.70rd RUU
* Uploaded a complete firmware.zip ( S-OFF & CID 11111111, S-ON TRY AT YOUR OWN RISK )
* Added Languages from WWE
* Added HTC ONE sounds
__________________________________
V1.8.1 FULL ROM
*Fixed Missing Permissions
*Fixed ADB
*Updated SU
*Updated WP_MOD.KO for Updated Kernel
(( MUST INSTALL AS A FULL ROM TO FIX MISSING PERMISSIONS ))
(( THERE IS A NO WIPE FULL ROM SO YOU WONT LOSE ANYTHING ))
____________________________________
V1.8 FULL ROM *******REMOVED**********
*Re-based from 3.14.531.17.70rd OTA
* (( Please also Flash the v1.8 firmware.zip ))
V1.8 Update Only *****REMOVED******
Update includes
* New Boot.img from OTA
* Patched files from 3.14.531.17.70rd OTA To Fix Battery Drain
* (( Please also Flash the v1.8 firmware.zip ))
_________________________________________
V1.7.1 FULL ROM
* Added A few Power Saving tweaks to build.prop
* Added WWE Languages
// For best battery life - change WiFi sleep policy to NEVER - Make sure Best WiFi Performance is UN-Checked.
V1.7.1 Update
* Added A few Power Saving tweaks to build.prop
// For best battery life - change WiFi sleep policy to NEVER - Make sure Best WiFi Performance is UN-Checked.
____________________________________
V1.7
* Updated to fix WiFI Calling Battery Drain :)
* Also added some AGPS stuff in as well
* Some Kernel Tweaks
* Stopped debugger icon from showing up every time you plug in your phone to your computer.
--> Go to --> WiFi --> advanced settings and change [B]keep Wi-Fi on during sleep[/B] to [B]Never [/B]or [B]Only when plugged in[/B].
[COLOR="Red"]// I DO NOT GIVE PERMISSION TO USE THIS ON ANY OTHER ROM // I WILL FIND OUT [/COLOR]
____________________________________
V1.6A
REMOVED
____________________________________
V 1.6
* Migrated over updates from EU 3.16.401.9
* Modified Rosie with transparent dock and landscape mode
* Updated boot.img (kernel) 3.16.401.9 based
* 1% Battery Mod by default
____________________________________
V1.5A
* Removed the /DATA/ wipe from the Updater-Script
-------------------------------------------------------
V1.5
* Added WiFi setup in system setup
-------------------------------------------------------
--> V1.4
* Added Start Up Scripts
* Fixed sys/read_write issue (thanks [URL="http://forum.xda-developers.com/showthread.php?t=2059411"]flar2[/URL])
* Updated to latest SuperSU
* Added Secure Box and Block Box to message app
* Cleaned up a few things
--------------------------------------------------------
--> V1.3
* Removed T-Mobile Bloat
--------------------------------------------------------
--> V1.2 Initial release
mkinney88 said:
I have received the jelly bean update from t-mobile this morning. This is only the OTA.zip pulled from my phone. I know it is Android 4.1.1 I am currently working on this as a flash-able rooted room but i figured i would upload the OTA.zip for everyone else. I am currently uploading now so it might be a few minutes before you can download it. I am uploading as of 1:40pm EST.
Dropbox
Roughly 20 Minutes
Click to expand...
Click to collapse
Thanks for working on this! This is exactly what I was hoping someone would do. I really don't want the hassle of re-locking, flashing stock recovery, etc. just to get the OTA.
I'm currently running CM 10.1 but I've always had some weird GPS issues with CM on my One S and miss the Sense camera quality.
I'm backing up everything now and happen to be free most of the evening tonight so if you get it assembled as a flash-able rooted ROM let me know and I'd be happy to try it and/or help test it.
DigitalMonk said:
Thanks for working on this! This is exactly what I was hoping someone would do. I really don't want the hassle of re-locking, flashing stock recovery, etc. just to get the OTA.
I'm currently running CM 10.1 but I've always had some weird GPS issues with CM on my One S and miss the Sense camera quality.
I'm backing up everything now and happen to be free most of the evening tonight so if you get it assembled as a flash-able rooted ROM let me know and I'd be happy to try it and/or help test it.
Click to expand...
Click to collapse
I didn't have to re-lock my bootloader. I just changed my CID back to tmobile and ran a RUU. After the RUU and also the OTA update im still S-off and unlocked, it just flashed the stock android recovery back. FYI
mkinney88 said:
I didn't have to re-lock my bootloader. I just changed my CID back to tmobile and ran a RUU. After the RUU and also the OTA update im still S-off and unlocked, it just flashed the stock android recovery back. FYI
Click to expand...
Click to collapse
Good to know in case I get impatient. Haven't taken the time to get S-off but I've been unlocked, rooted and custom recovery since about day 5 of owning my One S.
I'm at work for a few more hours so I figured I can be patient and hold off and be available to test flashing a ROM if you end up doing one because if that's an option I'm guessing a lot of people will go that route rather then doing the CID change, RUU and wait for the OTA to download and install.
I've got a fresh titanium backup and nandroid done so I'll wait patiently to see where you go with this.
DigitalMonk said:
Good to know in case I get impatient. Haven't taken the time to get S-off but I've been unlocked, rooted and custom recovery since about day 5 of owning my One S.
I'm at work for a few more hours so I figured I can be patient and hold off and be available to test flashing a ROM if you end up doing one because if that's an option I'm guessing a lot of people will go that route rather then doing the CID change, RUU and wait for the OTA to download and install.
I've got a fresh titanium backup and nandroid done so I'll wait patiently to see where you go with this.
Click to expand...
Click to collapse
I will hopefully have a rooted deodexed and odexed version of this tonight unless i run into a problem. If I don't run into any problems expect a ROM around 10:30pm EST. It will only be rooted and stock I wont have anytime tonight to do modifications.
I am s-on, locked bootloader and on the ics version of the pacman rom....what steps do i need to take to flash the update?
lightninbug said:
I am s-on, locked bootloader and on the ics version of the pacman rom....what steps do i need to take to flash the update?
Click to expand...
Click to collapse
It's not flash-able yet. He was just posting the actual OTA.zip for other developers who may want to pull files from it.
DigitalMonk said:
It's not flash-able yet. He was just posting the actual OTA.zip for other developers who may want to pull files from it.
Click to expand...
Click to collapse
I know...let me rephrase.. How can I go about getting the official ota? With my setup listed above
Sent from my Nexus 4 using xda premium
mkinney88 said:
I will hopefully have a rooted deodexed and odexed version of this tonight unless i run into a problem. If I don't run into any problems expect a ROM around 10:30pm EST. It will only be rooted and stock I wont have anytime tonight to do modifications.
Click to expand...
Click to collapse
Perfect. Exactly what I'm looking for. I'd like to try the stock experience again with JB just to see what it's like if nothing else. My usage habits have changed recently and JB stock may well be good enough for me. I really want the really good camera back just with buttery goodnewss and Google Now.
lightninbug said:
I am s-on, locked bootloader and on the ics version of the pacman rom....what steps do i need to take to flash the update?
Click to expand...
Click to collapse
--> Download the T-Mobile RUU tmobile htc one s ics RUU
--> Run the RUU and it will return you to stock. Then go to setting->software->Update and get the first OTA then after you install that update go back and check for update again. ** You can also try running the ruu and then put the jellybean OTA on your internal storage and reboot into the stock recovery and apply update from internal storage. (i have not tried this yet) ** Should work though
mkinney88 said:
--> Download the T-Mobile RUU tmobile htc one s ics RUU
--> Run the RUU and it will return you to stock. Then go to setting->software->Update and get the first OTA then after you install that update go back and check for update again. you can also try running the ruu and then put the jellybean OTA on your internal storage and reboot into the stock recovery and apply update from internal storage.
Click to expand...
Click to collapse
No need to relock boot loader? Or flash stock recovery?
Sent from my Nexus 4 using xda premium
lightninbug said:
No need to relock boot loader? Or flash stock recovery?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I am S-OFF and i didn't re-lock my boot-loader or flash recovery. I only use to re-locked my boot-loader when i was s-on but i don't know if it makes a difference. You should be S-OFF by now why are you not.
mkinney88 said:
I have received the jelly bean update from t-mobile this morning. This is only the OTA.zip pulled from my phone. I know it is Android 4.1.1 I am currently working on this as a flash-able rooted ROM but i figured i would upload the OTA.zip for everyone else.
//// I also uploaded the firmware.zip for this update. \\\\
Dropbox
--> If you download this please give me a thanks <--
**UPLOADED**
Edit: I can confirm if you are s-off this will not affect you at all. I did change my CID back to T-MOB010. I did NOT re-lock my bootloader, I ran the TMOUS_2.35.531.7 RUU to get back to stock and downloaded the OTA for JellyBean.
This does include GOOGLE NOW
HBOOT-2.15.0000
Radio-1.13.50.05.31
Click to expand...
Click to collapse
i didnt change my CID....and locked the bootloader...flashed stock recovery and ran the ota...
aegentirony said:
i didnt change my CID....and locked the bootloader...flashed stock recovery and ran the ota...
Click to expand...
Click to collapse
Thanks for the feed back
aegentirony said:
i didnt change my CID....and locked the bootloader...flashed stock recovery and ran the ota...
Click to expand...
Click to collapse
What ROM were you on? Curious as I would like to have stock jellybean (not rooted) on my One S.
I'm s-off and supercid. Just wondering what the steps would be if I wanted to try this.
Sent from my Galaxy Nexus using xda app-developers app
npiper05 said:
What ROM were you on? Curious as I would like to have stock jellybean (not rooted) on my One S.
I'm s-off and supercid. Just wondering what the steps would be if I wanted to try this.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
This is a full update just flash stock recovery and then flash ota I think that should work. Please leave feedback and let us know.
So I'm guessing the are the steps.
1. Save update.zip to my sd
2. Flash stock recovery (I need to find this)
3. Boot into recovery (the stock recovery should
4. Stock recovery should flash the update
Do I need to change my CID back to T mobile? I've heard of bricks when flashing OTA with super cid.
Sent from my Galaxy Nexus using xda app-developers app
npiper05 said:
So I'm guessing the are the steps.
1. Save update.zip to my sd
2. Flash stock recovery (I need to find this)
3. Boot into recovery (the stock recovery should
4. Stock recovery should flash the update
Do I need to change my CID back to T mobile? I've heard of bricks when flashing OTA with super cid.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I changed back to the tmob010. I have uploaded the firmware to my dropbox on the link in the first post. You will find the stock recovery image there. Then just fastboot flash img and try from there.
npiper05 said:
What ROM were you on? Curious as I would like to have stock jellybean (not rooted) on my One S.
I'm s-off and supercid. Just wondering what the steps would be if I wanted to try this.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
i was on the latest T-Mobile US Rom , rooted, supercid, s-off
npiper05 said:
So I'm guessing the are the steps.
1. Save update.zip to my sd
2. Flash stock recovery (I need to find this)
3. Boot into recovery (the stock recovery should
4. Stock recovery should flash the update
Do I need to change my CID back to T mobile? I've heard of bricks when flashing OTA with super cid.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Are you rooted now ? ...You should just flash stock recovery in fastboot, relock your bootloader, flash the latest RUU...then let the phone OTA ...Stock JB not rooted will be the result.
aegentirony said:
i didnt change my CID....and locked the bootloader...flashed stock recovery and ran the ota...
Click to expand...
Click to collapse
aegentirony said:
i was on the latest T-Mobile US Rom , rooted, supercid, s-off
Are you rooted now ? ...You should just flash stock recovery in fastboot, relock your bootloader, flash the latest RUU...then let the phone OTA ...Stock JB not rooted will be the result.
Click to expand...
Click to collapse
Yes - rooted now. I have Trickdroid 9.0. Would love stock JB for work. Using stock Galaxy Nexus now, as I need stock setup, no root for work.
I tried going to the dropbox link, but had the "too much traffic" message.
If I want, could I flash stock recovery, flash RUU, then do a system update to try to get the JB update?
Only thing that makes me nervous is the SuperCID. I'll look for a link to change back to TMOB CID. I'm guessing it's not too difficult.
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
Sorry if this question does not belong here, I'm a noob. A few days ago I was trying some things with the sunshine free apk and after a few minutes I got a message that said "congratulations now you have temp root", then I installed TWRP through google play, rebooted into recovery and it worked. At that time I did not try to install a Custom Rom through this method because I wasn't sure about it, my question is Can I install a custom rom doing with this method? (like the google play edition sensified rom)
coderch123 said:
Sorry if this question does not belong here, I'm a noob. A few days ago I was trying some things with the sunshine free apk and after a few minutes I got a message that said "congratulations now you have temp root", then I installed TWRP through google play, rebooted into recovery and it worked. At that time I did not try to install a Custom Rom through this method because I wasn't sure about it, my question is Can I install a custom rom doing with this method? (like the google play edition sensified rom)
Click to expand...
Click to collapse
I'm not really sure what to tell you. If you managed to install TWRP without getting S-Off and an unlocked bootloader (never heard of this) I would think you could flash a rom. However, I don't know if it would work for you or not. If the rom comes with a boot.img file, it would almost certainly fail to flash that part of the rom. You would need an unlocked bootloader for that to work. If the system part of the rom did flash, it might be nothing but headaches if it relied on the boot.img. I'm not even sure if the system would flash without an unlocked bootloader. My guess is probably but I think you might be in for a world of headaches if you do it. I would recommend just running sunshine and paying the piper . Maybe somebody else more knowledgeable than me can answer and tell you for sure. I'd tread lightly on this one if I were you. I just don't know for sure. All I know is that boot.img isn't going to succeed.
robocuff said:
I'm not really sure what to tell you. If you managed to install TWRP without getting S-Off and an unlocked bootloader (never heard of this) I would think you could flash a rom. However, I don't know if it would work for you or not. If the rom comes with a boot.img file, it would almost certainly fail to flash that part of the rom. You would need an unlocked bootloader for that to work. If the system part of the rom did flash, it might be nothing but headaches if it relied on the boot.img. I'm not even sure if the system would flash without an unlocked bootloader. My guess is probably but I think you might be in for a world of headaches if you do it. I would recommend just running sunshine and paying the piper . Maybe somebody else more knowledgeable than me can answer and tell you for sure. I'd tread lightly on this one if I were you. I just don't know for sure. All I know is that boot.img isn't going to succeed.
Click to expand...
Click to collapse
Thank you, then I'll have to buy the full version of app
coderch123 said:
Sorry if this question does not belong here, I'm a noob. A few days ago I was trying some things with the sunshine free apk and after a few minutes I got a message that said "congratulations now you have temp root", then I installed TWRP through google play, rebooted into recovery and it worked. At that time I did not try to install a Custom Rom through this method because I wasn't sure about it, my question is Can I install a custom rom doing with this method? (like the google play edition sensified rom)
Click to expand...
Click to collapse
I suspect you haven't accomplished as much as it sounds. I don't believe you can flash a custom recovery with s-on and a locked bootloader. When you ran sunshine, did you go all the way and pay for it or did you stop after gaining temp root? Temp root may allow something like the TWRP app (different from the actual TWRP recovery) to think it's done it's thing without the flash actually completing. When you say "it worked" do you mean you booted all the way into TWRP recovery?
cntryby429 said:
I suspect you haven't accomplished as much as it sounds. I don't believe you can flash a custom recovery with s-on and a locked bootloader. When you ran sunshine, did you go all the way and pay for it or did you stop after gaining temp root? Temp root may allow something like the TWRP app (different from the actual TWRP recovery) to think it's done it's thing without the flash actually completing. When you say "it worked" do you mean you booted all the way into TWRP recovery?
Click to expand...
Click to collapse
Yep, I installed the app from google play and then it asked me if I wanted to reboot into recovery so I did it. I was able to use TWRP but I didn't try anything because I wasn't sure.
coderch123 said:
Yep, I installed the app from google play and then it asked me if I wanted to reboot into recovery so I did it. I was able to use TWRP but I didn't try anything because I wasn't sure.
Click to expand...
Click to collapse
But you're sure that you still have s-on and a locked bootloader? What happens if you turn off the phone and then enter the bootloader (volume up + power) and enter recovery from there? Does it take you to TWRP or stock recovery.
cntryby429 said:
But you're sure that you still have s-on and a locked bootloader? What happens if you turn off the phone and then enter the bootloader (volume up + power) and enter recovery from there? Does it take you to TWRP or stock recovery.
Click to expand...
Click to collapse
Here's a picture
{
"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"
}
Ok, but if you enter recovery from hboot as in your picture do you actually go into twrp? I wonder if either the TWRP app (with temp root) was somehow able to boot twrp instead of flashing it to the recovery partition and booting to recovery or perhaps some previous owner flashed a spoofed hboot and you actually do have an unlocked bootloader but don't know it. Did you buy the phone new with this being the first time you've tinkered with it?
cntryby429 said:
Ok, but if you enter recovery from hboot as in your picture do you actually go into twrp? I wonder if either the TWRP app (with temp root) was somehow able to boot twrp instead of flashing it to the recovery partition and booting to recovery or perhaps some previous owner flashed a spoofed hboot and you actually do have an unlocked bootloader but don't know it. Did you buy the phone new with this being the first time you've tinkered with it?
Click to expand...
Click to collapse
I went to the States a month ago and I bought it pre-owned in Gamestop, so maybe as you said it is modified. And answering about the TWRP I tried to boot into recovery yesterday but I had no success (I got to the default android recovery).
Summing up I'll just buy the full version of the sunshine app and do this thing in the proper way, thank you for your help and time.
coderch123 said:
I went to the States a month ago and I bought it pre-owned in Gamestop, so maybe as you said it is modified. And answering about the TWRP I tried to boot into recovery yesterday but I had no success (I got to the default android recovery).
Summing up I'll just buy the full version of the sunshine app and do this thing in the proper way, thank you for your help and time.
Click to expand...
Click to collapse
Why not verify first you are truly s-on with a fastboot getvar all
That way we can make sure someone didn't flash a faux hboot.
Sent from my SM-T810 using Tapatalk
dottat said:
Why not verify first you are truly s-on with a fastboot getvar all
That way we can make sure someone didn't flash a faux hboot.
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
Sorry for the delay. I checked it with fastboot getvar all and it is stock, there's nothing wrong with it. S-ON and locked bootloader.