I have a couple questions.
I am on the 1.16 hboot with cid111111 and s-off unlocked tampered. twrp and maximus rom.
I finally did super cid and s-off on my one-s. Shortly after I recieved a notification that ota update 3.16.401.8 (612.27 mb) was available.
I was wondering if it would even work if i attempted to update. or would i have to update manually. Or would it brick it.
The main reason i would want to update is because the JB Sense roms just dont seem to run smoothly on my phone.
I was thinking this would update everything so the custom roms run smoother.
And Should i even update my hboot. does it make a difference.
I would usually be against it(ive had to downgrade other phones before).
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
impostle said:
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
Click to expand...
Click to collapse
Ok. ill look into that. sounds easy enough. last time i tried to update, i couldnt because of my cid. now i guess since there is an official t-mob i can do it?
You cant flash an ruu with super cid?
Oh and also, Once i update my hboot am i able to install the older ICS roms like maximus. thats just the most stable one i have found for my particular phone.
One more. Will i be able to restore my cid with s-off
ruu update
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
myphonesbetter said:
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
Click to expand...
Click to collapse
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
impostle said:
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
Click to expand...
Click to collapse
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
real187 said:
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
Click to expand...
Click to collapse
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
EDIT: Thats what I get for watching too many threads, I miss stuff.
impostle said:
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
Click to expand...
Click to collapse
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
real187 said:
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
Click to expand...
Click to collapse
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
impostle said:
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
Click to expand...
Click to collapse
I have seen the tread. But im scepitical, because if it really was only because of the s-off more people should have it. Might be hardware related.
Eh you do not have tot change back your Cid to original (if its a branded Cid the ruu still wont run), just a valid HTC Cid.
Verstuurd van mijn One S met Tapatalk
He could flash from recovery or fastboot flash any hboot he wants with s-off. No RUU needed for downgrade or upgrade. That's only needed to go back to stock for warranty purposes.
@myphonesbetter
If you want the red warning text overlay to be gone as well choose any of the files here and flash it within recovery. S-Off needed to do so!
To remove ***Tampered*** as well download hboot 1.140004. You will need to come from a lower hboot version so if you're already on >1.140004 flash one <1.140004 first.
--- edit ---
You can lock/unlock your phone as well by flashing. Read more in [how to] reset your lock status flag. Also it's in the Droid DNA forums it's valid for One S. Remember: You need s-off for this to work.
--- and one more ---
You can change your CID pretty simple on rootet devices. Just enter fastboot mode and type:
'fastboot oem writecid HTC__001'
Reboot bootloader then. You can find a collection of HTC ONE S CID's here
^^^^^Very helpful post. thank you. I wouldve never found that.
When you run the ruu .exe, do you have to be in fastboot or in android? The install app told me just to turn the phone on so i figured it would automatically go into bootloader. but it did nothing at all to my phone and gave me an error 115.
When i tried the ota it tells me that I am runnning an altrered OS and i will have to install it a different way.
Sorry for the easy questions. but i just cant seem to find any threads that say how to. I found the ruu and a zip of the ruu. but not how to install it.
The best sense rom has instructions on flashing a newer hboot. .but i want to install a completely stock rom.
myphonesbetter said:
^^^^^Very helpful post. thank you. I wouldve never found that.
.
Click to expand...
Click to collapse
guess you run out of thanks, no?
Never even noticed the thanks meter. I have more of a direct thank you approach.
I tried to flash the ruu .exe in fastboot. and it actually rebooted into the black htc screen, so i figure thats the way to do it.
Unfortunately I got another error. image error (159) use the correct rom and flash again.
I am attempting to flash 3.16.401.8 onto hboot 1.16 (relocked) i am s-off and i changed my cid to HTC__001 via fastboot.
Is there another way. or can i flash the zip in twrp or cwm? Again i just want an oem jelly bean with the proper hboot and radio and everything that the OTA would change. so i can be up to date before i move on to the JB roms.
Ive tried all of the custom ones, and the wifi cuts in and out. i used the wifi partition fix. and i flashed the latest radio. nothing helped for more than a few hours.
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
ultimul said:
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
Click to expand...
Click to collapse
Yah thats usually how it works for me. if it works for 99% of people with one step. ill have to do it manually with 20 steps. I guess its made me learn alot about adb and fastboot. I could never get adb to work untill i upgraded to windows 7 recently. until then i had to exract everything to my sdcard via terminal emulator and then drag it to my computer form the card and modify things. but ive been forced to learn quite a bit.
Its weird. I bought my phone off of craigslist from someone who had no idea how to root. But when i opened it into hboot it said Tampered and locked. with no signs of ever being unlocked. completely stock rom and no red warning text on the splash screen.
The reason i want to be stock it so i know all the correct partitions and everything are set up right. (that part i dont understand yet).
I know that a normal system wipe in twrp or cwm doesnt wipe everything. If i wipe and install the same rom i am using(just to clear it up and start over) it doesnt even wipe the app data. (at least on my phone)
Im thinking that its because i am installing a euro rom with a HTC__001 cid and mine was originally TMUS T-MOB010 .
one thing i noticed also is that windows could not verify either of the ruus i downloaded from shppied roms
How do i flash the ruu.zip that i downloaded? Do i need to rename it update.zip like the older phones? Its been a while.
Ok so i know im pretty much helping myself here but i hate when i come across threads with no conclusion.
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Any help would be appreciated.
Ahh, things go on here! Nice! :laugh:
It's not quite clear if the RUU is the right one on this phone as many people report problems... So let's go OTA.
To flash the 3.16 OTA update your hboot needs to be < 2.15, your recovery needs to be the HTC stock one , your device needs to be relocked (not totally shure as mine wasn't at that time and it worked, but please remember that) and you need to have HTC stock system/ and stock data/ (ICS) files on your phone (you'll have to unroot as well, if rootet), as the OTA seems to check if certain files are present before working.
All that is quite a pain in the ass, isn't it?! So do one the following:
- Just make shure your bootloader version is lower 2.15, else flash a lower one.
- Click here and you'll have access to one of my google drive folders.
- Download the 2.31 zip. Unpack and copy these nandroid backup files into the appropriate TWRP folder on your phone, reboot into recovery and restore. Once done, you'll be able to flash the 3.16 OTA update after reboot. Remember to change CID before if you're on 11111111.
- Or download the 3.16 zip, unpack and restore. You'll have stock htc sense JB without the OTA. You don't even need to downgrade your bootloader in case. CID doesn't matter here.
- To root simply download SU_Bbox file and flash in recovery.
Important: With the JB update HTC invented disk write protection by default. This simply means that files deleted within stock sense JB will be back after rebooting the phone, also root was granted and working (still grats to htc for this one!!!). Check out for elemental x kernel at this point, as flar2 is the one offering additional modules for the stock kernel working around this. So you can be on stock JB as close as possible with write protection disabled.
--- edit ---
I nearly forgot: If you're experiencing WiFi troubles afterwards search for flashing wifi partitions.
--- and one more ---
myphonesbetter said:
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Click to expand...
Click to collapse
Cause you're on 2.35 US. You need to be on 2.31 EU before, because 3.16 is EU and there is still no JB update to 2.35 US. 3.16 OTA will work with htc__001 (htc worldwide).
The OTA determined my OS was modified.
I could not restore the folder i took directly out of the zip.
There was a folder inside the folder that contained the same files. I was able to flash this.
My hboot is still at 1.14 my cid is not htc--001 relocked. the update was 650 mb of which i could not use wifi for becauese it just said error.
so 650 mb through tmobile. only took a few minutes but used almoast half of my months dl limit.
IDK. i found instructions on how to update the hboot in best sense roms thread. i will try that.
Edit: the restore for 3.16 worked in twrp. shouldve tried that first.
I may still update my hboot. I cant really find any instructions. Apparently the search just finds every thread and lists it.
If you are on the latest TWRP 2.4.3.0 go back to 2.4.1.0 (the latest one seems to have restore problems).
The folder contained in the zip needs to be copied to /TWRP/BACKUPS/HT23whatever/
You should be able to restore then.
--- edit
hehe, ok then.
You can flash any of these hboots from within TWRP. Up or down, it doesn't matter - you're s-off.
---------- Post added at 10:43 AM ---------- Previous post was at 10:32 AM ----------
CID should be HTC__001 not htc--001. Maybe a typo.
Related
I've just successfully gone through the process of S-OFF, CWM, etc, to change my CID from UK Vodafone to generic EU HTC__001. No problems at all.
I'm wondering though when you download the RUU executable, run it to get at the extracted rom.zip and then cancel the HTC RUU to do the rest manually, what would actually happen if you ran the RUU , would it not do the upgrade for you anyway?
Second question - Now I have the CID of HTC__001, and have flashed the 1.35.401.1 latest version, when the next version is out, will it be an easy update via the OTA utility on the phone, or do you need to keep doing the long winded flashing method forever now?
chrisw99 said:
I've just successfully gone through the process of S-OFF, CWM, etc, to change my CID from UK Vodafone to generic EU HTC__001. No problems at all.
I'm wondering though when you download the RUU executable, run it to get at the extracted rom.zip and then cancel the HTC RUU to do the rest manually, what would actually happen if you ran the RUU , would it not do the upgrade for you anyway?
Click to expand...
Click to collapse
Yeah it would flash for you, or at least it did for me! I re-ran my stock RUU just to be on the safe side after S-Off and it redoes everything but kept my S-Off... so I just reflashed CWM (PD58IMG.zip method), and then rooted the stock ROM.
chrisw99 said:
Second question - Now I have the CID of HTC__001, and have flashed the 1.35.401.1 latest version, when the next version is out, will it be an easy update via the OTA utility on the phone, or do you need to keep doing the long winded flashing method forever now?
Click to expand...
Click to collapse
From my understanding OTA's won't flash through a third-party recovery (CWM) so if you keep the stock recovery then I think it would work... But from this point on there will probably be pre-rooted version of most every release packaged in a nice .zip for you to flash with ROM Manager/CWM... or who knows maybe you'll find a nice ROM you like and then the chef would keep you updated!
I hope that helps!
Yes, very useful thanks.
Is there any difference between renaming rom.zip to PD58IMG.zip and letting it happen , or putting rom.zip on and doing "update from zip file" from recovery?
Bonjour everyone, here's a little guide on how to unbrand your phone in order to get the OTA updates notifications directly and be able to install them.
If you want to get S-OFF one day on your One SV, read this first. You need to change CID to SuperCID to do so, and it's not possible (for the moment) if you upgrade to JB
Basically this works as long as your phone model is sold unbranded somewhere in the world and that the people having such a phone got an OTA update.
For now, ther's no way to change CID if you're running JB and are S-ON. That means that this only work for One SV's running ICS who want to get the OTA updates.
As far as I know, it works on K2_U and K2_UL, since they both got an OTA update to JB.
The trick is simple, I didn't invent it and haven't been able to find its original founder, but thanks a lot to her or him !
I'm basically just a messenger here since I only tried out some stuff that worked with other phones, so thanks a lot to bkcokota, old.splatterhand and jmztaylor
Don't try it if you're worried, bricks happen, you'd be the only one responsible !
Here we go :
1. First you need to root your phone, here's how.
2. Change you CID using the same method than for the One S.
Personnaly, I changed it to "HTC__203", which is the CID unbranded HTC phones have in France (HTC-FRA).
For example, "HTC__001" is HTC-WWE, which stands for World Wide English.
You can change it to whatever CID you like : choose it well. I can only recommend to use HTC__203 since it's the only one I tried and that it worked, but do as you please !
3. Flash stock recovery back. You'll find it here or here. Flash it like you flashed CWM recovery (into fastboot, using fastboot flash recovery xxxxxx.img).
4. Relock your bootloader. It's possible that it's not necessary, but it can't hurt ("fastboot oem lock", when in fastboot usb)
5. Run a RUU that matches you unbranded CID to get an "unbranded" rom.
You'll find them here, for example. The "RUU_K2_UL_ICS_40_HTC_Europe_1.17.401.5_R....exe" one will work with HTC__203 and HTC__001 CIDs.
6. Go ask your phone if he can find any updates
WARNING : for the moment there's no way to change CID if you upgrade to JB since the newer HBOOT (v2.00) don't let you do it. That means that for now you won't be able to S-OFF if you upgrate to JB using this method. For now...
Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).
old.splatterhand said:
Nice one!
Only thing i would add for people to know:
if somebody want to get S-Off, they should change the CID to SuperCID 11111111 (or if you want 22222222,...).
Click to expand...
Click to collapse
Done, sir.
It was only said at the bottom of the message at first, but now I put it at the beginning as well.
There's one thing that I'm trying to get though : according to a lot of people and forums, you don't get OTA when you have SuperCID... but some poeple say they do.
It probably changes depending on the type of HTC phone, but also depending on the OTA (some got the first ones, but not the latest...).
I got the ota notification with SuperCID, i think it depends on more things.
But there i'm not far enough into it.
I have had no success at all. My story:
Updated a branded phone to JB, rooted. Then I did a moonshine S-off and changed CID to HTC__001 (even tried 11111111).
I have downloaded a ICS RUU (couldn't find stock K2_UL so I thought that I would download ICS first and then do OTA to JB) but I am getting error 158. I have checked md5 sum and it matches (http://androidfiles.org/ruu/getdown...0.14_2_10.49.40.11L_release_301902_signed.exe). Any ideas?
If you're on jb and hboot 2.00, that's normal... and written in the first post.
There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Is there any chance to make this for the k2cl ( boost mobile ) version?
idr666 said:
Is there any chance to make this for the k2cl ( boost mobile ) version?
Click to expand...
Click to collapse
Can you be more specific, what you mean with "this".
old.splatterhand said:
Can you be more specific, what you mean with "this".
Click to expand...
Click to collapse
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB
idr666 said:
Sorry, I was wondering if there is a way to update this phone ( the k2cl ) to JB
Click to expand...
Click to collapse
Boost has no official jb, but i know that there is work for an custom jb rom for boost.
Oh, thank you for the info. Is there any link about this work in progress?
idr666 said:
Oh, thank you for the info. Is there any link about this work in progress?
Click to expand...
Click to collapse
Look here
szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot, but I guess that I have had success in changing to superCID (at least this is what I can read in bootloader and using fastboot oem readcid command.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?
szympro said:
There is information that it is impossible to change CID while on JB and with 2.0 hboot,...
Click to expand...
Click to collapse
This was before moonshine was available. With S-Off i think it should be possible.
So, as far as I understand newer hboot won't let me use older RUU as well, right?
Click to expand...
Click to collapse
I think so.
szympro said:
old.splatterhand, you seem to know this and that about One SV. No chance for older RUU, right? I can't seem to find a clean WWE JB OTA update. I just want a clean, stock, not modified ROM from HTC and I thought RUU is the only way to go :crying: Any advices?
Click to expand...
Click to collapse
To get it a bit clearer.
At this point i'm not very up to date, thats why i didn't answer til now.
I think (but i'm not sure) you can flash the ruu, if you are on hboot 1.0.
And as you are S-Off you should be able to downgrade hboot. But this is a very risky point, you can easily brick your device. Here is, how you have to do:
rollon76 said:
To change hboot you will need a PL80IMG.zip on sdcard with android-info.txt and hboot.img inside it.
reboot to bootloader and flash.
Click to expand...
Click to collapse
The thing what makes it difficult, is to get the hboot.img (its inside ics ruu), cause the htc ruu's encrypted and i only have heard about tools for linux which can decrypt it.
Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!
szympro said:
Thanks to your reply I did some research and I have managed to do what I wanted. I have downgraded hboot first (by extracting and encrypting ICS RUU using linux), then I could run RUU and now I am stock ICS with S-off and superCID
Should I post some files from RUU? 1.0 hboot or stock recovery? You guys need something?
Thanks for your helping hand old.splatterhand!
Click to expand...
Click to collapse
Glad, it worked for you.
Yes, of course, everything is appreciated! You can use this thread, please post ruu name too. You can look at my posts there. Hboot, boot.img, recovery, radio, would be fine.
HERE have other ruu
https://www.dropbox.com/sh/1t2zswod7tc97az/5hbzEgTv80
szympro said:
I have downgraded hboot first (by extracting and encrypting ICS RUU using linux)
Click to expand...
Click to collapse
Wow, that's cool !
Did you use rollon's method and flashed PL80IMG.zip in bootloader mode ?
If yes, which android-info.txt did you use ?
If not, how did you do it ?
szympro said:
then I could run RUU and now I am stock ICS with S-off and superCID
Click to expand...
Click to collapse
Even cooler for you.
Did you get the ota update notification for JB then ?
Did you manage to apply it ?
Thanks and congratulations !
Hi everyone.
Just a quick message to confirm that rollon's method works.
To downgrade you need to be S-OFF, extract and decrypt (with ruuveal, using linux or a linux virtualbox runned in windows) hboot and androidinfo from ICS RUU, put them in a zip named PL80IMG.zip, put it on your sd card and boot into bootloader. Then you can run the ICS RUU normally and you'll be back to stock ICS, with a "*** LOCKED ***" bootloader (not relocked !), will be able to go back to S-ON using "fastboot oem writesecureflag 3" (thanks to JMZ)...
You'll then have a locked S-ON out of box phone running 100% stock ICS with original boot, recovery and all that... who'll get the 2 JB OTA's...
In case anyone's interested
Didn't find to much related to specifically to what I want to do.
I was tinkering with my software and messed something up and won't boot.
I can seem to find a strict stock rooted rom from t-mobile
Can I do the following without messing up my phone?
I already have s-off and twrp and a none working rom.
I want to relock bootloader, flash ruu
unlock again and flash recovery and root file.
I think this should work without messing up the phone and I should still have s-off right?
M9x3mos said:
Didn't find to much related to specifically to what I want to do.
I was tinkering with my software and messed something up and won't boot.
I can seem to find a strict stock rooted rom from t-mobile
Can I do the following without messing up my phone?
I already have s-off and twrp and a none working rom.
I want to relock bootloader, flash ruu
unlock again and flash recovery and root file.
I think this should work without messing up the phone and I should still have s-off right?
Click to expand...
Click to collapse
I've ran an RUU a couple times and still had S-off when it was done. It should not impact that at all.
Or you can skip all that and just flash the t mobile ROM in the dev section.
But, yeah, you will keep soff through the ruu
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me
No need to relock bootloader if s-off. You should flash stock recovery so and use a CID according to your RUU file.
Stock recovery not needed.
Just ruu away
Verstuurd van mijn HTC One S met Tapatalk
Oooh
I also thought too you needed to re lock to flash a ruu.
I guess that is only if not s off then.
Just need to match cid though still.
SCID will work with any RUU. But you shouldn't use it if you insist to upgrade by OTA... Some people reported a brick this way.
Updating EU RUU from 2.31.401.5 to 3.16.401.8 (going from a CM10.1 version)
Well here is what I've done if it can help some. No warranty that it'll work for everyone, but let's go:
First thing : I've started with CM10.1, S-OFF, SuperCID (11111111) and TWRP 2.5.0.0
I DID NOT relock the bootloader and NOT put back the original Recovery
1) I've put back my original CID (EU Bouygues eg. HTC__203. You should put your original one). Fortunately, I had the original mmcblk0p4 file backup (just copy back the original file to /dev/block. See here : http://forum.xda-developers.com/showthread.php?p=26516911#post26516911).
2) once my original CID has been put back (still S-OFF and TWRP and not relock), I've started in bootloader mode the RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5 and let things run
3) after the installation and reboot, I went to Parameters/Update/Check to force the JB update 3.16.401.8 download.
4) I've let the JB update to be performed (several reboot): all went fine. Going into fastboot, I'm still Unlocked / S-OFF / HTC__203 (original) / Radio 1.11.50 and HBOOT 2.15.000. Sounds good !
5) I went back into fastboot to re-flash the TWRP 2.5.0.0 (fastboot flash recovery openrecovery-twrp-2.5.0.0-ville.img)
6) I then reboot into Recovery : now TWRP is back ! In TWRP, try to reboot into bootloader. TWRP will warn you that you're not ROOT and suggest to install root on your phone. Hit YES.
7) Reboot normally your phone : you should have now a Super SU Installer icon in your apps. Open it, choose install via TWRP, and you're good to go! You've now the latest HTC JB sense version with root.
Optional :
-You can perform a full TWRP backup (with Sense/original CID) in case of further HTC update (?)
-You can put back your SuperCID if wanted
Now if you want to test the CM10.1-3.4 kernel here http://forum.xda-developers.com/showthread.php?t=2302248, it's booting fine (after full wipe)
Voilà !
Hope this helps
yeah
with the tmo model I can get the JB ruu right from HTC
I have just been having issues that I want to get stock and maybe root.
Will double check CID and just flash then.
I think hboot and radio on jb equivlent already but will try that.
Thank you
I wanted to post a little warning here, and relate what happened with my RUU update. First, I'm unlocked, s-off, Hboot 1.13.0000, superCID (11111111), running TWRP 2.5.0.0.
So I read somewhere that the latest RUU may not install correctly if on an older Hboot so I fastboot flashed the latest 2.15, no problems. Then I found a decrypted ROM that Hasoon2000 had posted thinking that this would give me the firmware I wanted, I believe this was based off of RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release. I then Fastboot flashed: (I didn't relocking bootloader or changing CID but I did first flash stock recovery because I wasn't sure it I needed to or not)
1. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip "name of ROM".zip
The script ran and everything flashed successfully, so I reflashed TWRP 2.3.3.0 and the phone booted just like stock ROM. At this point I checked the Hboot and it was 2.04 something! with a 1.11?? radio. (So this told me I likely wouldn't have needed to first flash the 2.15 Hboot not sure about this tho) I then tried to restore my backed up SDcard and here is where I ran into problems. My SDcard/internal storage only had 48.6MB of space! Nothing I did would change it I worked with this for several hours last night before giving up and this morning I thought to try running a different Tmobile RUU. Found this thread http://forum.xda-developers.com/showthread.php?t=2250573 and downloaded this Firmware package: http://www.filedropper.com/firmware_1 and ran the same fastboot commands (changed recovery back to stock which I probably wouldn't have needed to do...??) and everything flashed perfectly (I needed to run the "fastboot flash zip firmware.zip" the second time, which is normal). I now have my SDcard back with Hboot 2.15, radio 1.13, superCID and s-off yet, "hopefully" am ready to flash the new 3.4 updated stuff!
I suspect the reason for my problems lay in my flashing a euro ROM/RUU, but I really don't know that for sure. This is just what happened to me. Hope this helps a bit!
i believe i have an issue that is too challenging for me. i flashed the lates trickdroid and for some reason i couldnt get my radio to show. my baseband version was unknown. i tried to flash a new radio tto no avail. finally i flashed the jb ruu and now the rom will work for a couple of minutes and then reboot still with unknow baseband radio version. im s off with super cid. any thing to help woul be appreciated.
Did you run the ruu exe or how did you flash it?
Sent from my HTC VLE_U using xda premium
Clom801 said:
i believe i have an issue that is too challenging for me. i flashed the lates trickdroid and for some reason i couldnt get my radio to show. my baseband version was unknown. i tried to flash a new radio tto no avail. finally i flashed the jb ruu and now the rom will work for a couple of minutes and then reboot still with unknow baseband radio version. im s off with super cid. any thing to help woul be appreciated.
Click to expand...
Click to collapse
Have you tried the fastboot flash zip firmware.zip method? It's working great at updating firmware for all the AOSP ROMs.
TheArtiszan said:
Did you run the ruu exe or how did you flash it?
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
i ran the RUU. i tried the TMOUS ICS and EU JB
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
el_smurfo said:
Have you tried the fastboot flash zip firmware.zip method? It's working great at updating firmware for all the AOSP ROMs.
Click to expand...
Click to collapse
is that the new method posten in the development section? i will try
ok, tried it and it didnt work. still shows no signal with an x ans reboots after a couple minutes
You can try the tmous jb one.
That might be better as not a downgrade.
Not sure about the eu one but that could be why the ics one is not working.
Sent from my HTC VLE_U using xda premium
Clom801 said:
i ran the RUU. i tried the TMOUS ICS and EU JB
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
is that the new method posten in the development section? i will try
ok, tried it and it didnt work. still shows no signal with an x ans reboots after a couple minutes
Click to expand...
Click to collapse
Interesting thought... Try a cm based ROM. They use a radio in a different system folder. If it still doesn't work, sounds more like a hardware failure.
Background story:
I was trying to unlock and s-off 1.73 at&t one x phone with 1.09 hboot so that i could install a custom rom... Having experience with some other phones I prepared myself, software, drivers and everything else and plunged into action... I successfully unlocked the phone using a compilation of tutorials since it's so old bootloader and all, as for root i'm not sure I actually managed to get it work, it complained most of the time of missing bin files although I flashed su through recovery again and it settled down. I couldn't s-off it in any of the way tutorials were suggesting, gathering that i would have to update with some newer RUU, so I quit and phone is still s-on. And then I did an incredibly stupid thing, i didn't do nandroid backup, i just wiped system and tried to flash a new rom to no avail... None of the roms won't get flashed, i tryed sense and cm based ones, i'm getting some partition error, something about 2,14 and 2,15, not sure since error reporting is not consistent... Now I'm stuck within recovery and bootloader, i'm unlocked but s-on, i can't flash system img through fastboot nor a custom rom through adb sideload it says that partition is too small.
So question is what am I to do? What is my safest way out? Should i try flashing RUU (the one that should be the original one 1.73.502) or could I run some newer RUU and which would be preferable? If I'm to run RUU 1.73, should I run it as an exe or should I try to flash it as a zip file? Does it matter that the phone is unlocked and s-on? Why won't the smaller cm roms flash, how small could the partition be and does it have something to do with android version (4.1, 4.2 etc)?
To get a working ROM on your phone you can download an old build of cm and flash that. The new builds require updated firmware but the older builds don't. Go here and download the bottom build (stable cm10), and you'll need to get the 4.1 gapps package from here.
Sent from my Evita
What recovery and version number? I have a feeling this is recovery related, more than anything.
Also, newer builds of CM10.2 require hboot 2.14 or 2.15, so that is probably what the error message you mentioned is about.
We should be able to get you back up in and running on the custom ROM of your choice. But if you do decide to go the RUU route, in order to run an RUU, you must relock the bootloader in fastboot. Then you should be able to run the RUU. 1.73 RUU is fine. DO NOT run the 3.18, as there is a bug where with SuperCID and S-on (and you now have both) will BRICK THE PHONE. But the 1.73 or 1.85 RUUs will be fine.
Run the RUU as an .exe. I don't see the point in extracting and running the ROM.zip. You would just be making the process harder than it should be, and also removing some of the safeguards, if I remember properly.
S-off should work on any hboot version. I believe I got s-off while on hboot 1.09.
I'm running twrp 2.5.0.0 recovery, is there newer version? It never crossed my mind that it could something to do with recovery, so I never looked it up... Perhaps I could change it, it's not like that's gonna ruin chance of restoring any previous backups i didn't make...But i'd rather update the phone's firmware just to get those hboot glitches off the way because it, i'm quite sure, obstructed the s-off process (i was getting few 9x errors during s-offing, mostly 99).
So I'd be safe running 1.85 RUU. Is there some other RUU you would recommend, preferably some which will make the whole process of rooting, SuperCIDing and s-offing easier?
Thank you for helping me out!
edit> I tried flashing oldest CM and it worked! Then, feeling safe and all, I flashed newest twrp recovery and then, to my utter amazement, it flashed other rom I was aiming for... So thanks, for that recovery tip, it saved me a lot of pain! Now all is left for me is to figure out that s-off thing...
Hi, i had a S4 which got a broken screen and costs too much to fix a the moment so i brought a Telstra HTC ONE XL off a friend for $100.
I do like the phone but was over the 4.2.1 software as used to the 4.3 on the S4 which i rooted and put on CM10.
I tried with this phone to put on the nightly cm 10.3 but i hit a problem ,when install the nightlies it boot loops and when i try install the stable 10.1 it fails with an error which i do belive is to do with my V2 hboot.
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial
I have unlocked through htcdev and rooted it ok.
Im stuck now though as i pressed backup current original rom which turns out its not.
The phone details are
CID TELST001
Model: HTC ONE XL TELSTRA
If someone can tell where to either find the newest telstra rru for my phone or how to update my hboot so i can use cm10?
My phone is pretty useless at the moment
stueee said:
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
Click to expand...
Click to collapse
Where are you getting CM from (link it) and what is the file named? CM will typically have the phone's code name (EVITA) in the file name. If the code name ENDEAVORU is in the file name, it is in fact for the wrong device, as the ENDEAVORU is for the quad core Tegra3 (non-LTE) version, which is completely different hardware.
Also, I don't know if 10.3 is even released yet for our device, or for the ENDEAVORU for that matter. I think you might be confused about what you are flashing. So again, link what you are trying to install.
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have. Getting s-off disables the security check which would let you run any Evita RUU but you need to get a ROM to boot first before you try that. You also need SuperCID.
Your best bet is probably to flash an older Sense ROM (4.0 or 4.1), then you can at least boot, and get SuperCID and s-off so you can run the 3.18 RUU to meet the requirements for the latest cm ROMs.
Sent from my Evita
timmaaa said:
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have.
Click to expand...
Click to collapse
For some reason, I got confused and thought the OP was saying that the ROM install was failing. But it clearly says the RUU (or "rru" anyway) failed.
But yes, you can only run an RUU for your carrier version. So you will need s-off to run the AT&T RUU (the RUU referenced in the OP).
But still confused about the mention of CM10.3. From what I can see, it doesn't exist for either our EVITA, or the ENDEAVORU.
Maybe he meant cm10.2 and it was a typo?
Sent from my Evita
timmaaa said:
Maybe he meant cm10.2 and it was a typo?
Click to expand...
Click to collapse
Could be. Although if so, its a type that appears twice.
It seems fairly common for folks to try to install the wrong CM (wrong device). So I want to make sure the OP isn't doing that.
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
stueee said:
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
Click to expand...
Click to collapse
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Hi Red,
Sorry i typed out that post at almost 1am after pulling my hair out over a few hours and got a little confused.
My hboot is 2.15 and twrp is 2.6.3.0 which I believe is the latest.
What sense rom would work on mine as i really need this working now as i cant find a rom to suit anywhere with my lesser expertees.
I tried changing the cid using the super cid Telstra bat file but it won't recognize the phone as its not loaded, i tried in off state, bootloader, fastboot and twrp but is just keeps saying cant find phone.
I also tried the hex editor method but it didnt seem to update the CID after i completed it without errors.
thanks for you help.
redpoint73 said:
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Click to expand...
Click to collapse
With 2.15 hboot, you cannot modify the files required for supercid.
You can try the ever so risky jet tool. But this tool deliberately bricks to downgrade your hboot.
Sent from my HTC One XL using xda app-developers app
Any recent Sense ROM will suit your current setup, have a look here and you'll find a whole bunch. Unfortunately for you the 2.15 hboot has write protection enabled so there's no way you can get SuperCID (abd therefore can't get s-off), at least not until an exploit is released.
When you tried to flash CM did you also flash the boot.img via fastboot afterwards? You're s-on so that's necessary to get it to boot. Phones on a higher hboot like yours are unable to flash the boot.img through recovery so it must be done manually.
All you do is retrieve the boot.img from the root of the ROM zip, put it in your fastboot folder on your PC, and after you've flashed the ROM in recovery you reboot to bootloader, connect the phone to the PC, open a command prompt from within your fastboot folder (shift + right click anywhere in the folder then select open command prompt here), then give the following command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the ROM.
Sent from my Evita
stueee said:
My hboot is 2.15
Click to expand...
Click to collapse
That's pretty important. This is the reason why the older CM10.1 failed to install. CM was having issues with older hboots, so a script was added to require hboot 2.14.
Once hboot 2.15 came along, folks found that CM failed to install since the install script explicitly requires 2.14. Later versions include hboot 2.15 in the install script.
As exad and timmaaa mention, SuperCID (and therefore s-off) are not possible on hboot 2.15. So you are stuck with s-on (assuming that is what you are on now). It also means you can't currently run any RUU. Reason being, with s-on you can't run older RUUs, RUUs from another carrier, and there are no RUUs based on hboot 2.15. No "current" RUU exists (for your hboot), you can't run "previous" RUUs with the S-on restriction. So therefore you can't currently run any RUU.
But hboot 2.15 will work with newer versions of CM (and other AOSP ROMs which have been recently updated) as well as any Sense ROMs. But with s-on, you need to extract boot.img and flash manually with fastboot every time you install a ROM (as timmaaa points out). If you did not do this, this is why flashing the recent CM10.2 nightly resulted in a bootloop. Failure to falsh boot.img is the most common reason for bootloop after flashing a ROM.
stuck in bootloop
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
martin-m7 said:
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
Click to expand...
Click to collapse
You're in the wrong forum, buddy. This is the HTC One XL forum.