Related
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
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
andason said:
Hello.
I have an htc one xl (evita) which will not boot certain roms. I can boot some roms such as miui v5 and magiRom but I can not figure out why it will not boot roms such as CyanogenMod, ChameleonOS or TeamBaked BB9 as examples. These that will not boot will only boot loop and I'm going froot loop.
I am S-off, HBoot 1.09. Using TWRPv2.3.1.0.
I have tried TWRPv2.5, Hboot >1.09 and flashing boot.bin separately.
I have also tried some suggestions from these posts with no success so far ..
http://www.smartphonejam.com/2013/0...-on-HTC-Screen-Logo-Bootloop-after-Flash.html
http://forum.xda-developers.com/showthread.php?t=2159863
Any suggestions on how to boot other roms?
Thanks in advance for your help.
ps. I'm on mac - so if you have any suggestions and tools, please keep the mac in mind.
Click to expand...
Click to collapse
3.18 ruu.
Sent from my One X using xda premium
jacobas92 said:
3.18 ruu.
Sent from my One X using xda premium
Click to expand...
Click to collapse
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
andason said:
man i've looked at a lot of stuff regarding how to get to 3.18 but i keep finding a bunch of conflicting info that my brain is busted. If anyone can reply to some answers with my further info I would appreciate it...
My CID is 11111111
I'm S-off
hboot 1.09
What steps do I need to take to get to 3.18?
I can't seem to find a stock evita recovery image. My understanding is I need to relock boot loader, install stock recovery, upgrade to 3.18 and then restart the process of unlocking. Is this correct? Is the stock recovery located in an original at&t update?
Click to expand...
Click to collapse
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
RollTribe said:
As long as you're s-off, just go ahead and run this http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/ I know you wrote s-off, I'm just being double sure because if you're s-on it'll brick you. S-off you'll be fine. You won't have to relock or anything like that. With s-off you can just do whatever you want :good:
Click to expand...
Click to collapse
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
andason said:
Thanks. I'll find me a windows pc tomorrow and go for it. After I flash this in windows, do i then just flash any custom rom I want to go to which has the 3.4 kernel and will I be limited only to those now?
Click to expand...
Click to collapse
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
RollTribe said:
Yeah any 3.4 ROM, but you can also use non-3.4 if you so choose.
Click to expand...
Click to collapse
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Yeah, man, Wine doesn't work, I tried back when I used Mac for my Android needs. Everything is SO much easier with a windows PC
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
claudiuslu2011 said:
after flashing the 3.18 ruu, i can still flash any custom roms i want? aosp, sense base. what about ics version roms?
Click to expand...
Click to collapse
Yup all Roms
is there any advantage on the 3.18ruu?
Yeah, you need it to run AOSP 3.4 kernel roms
andason said:
Thanks again. Much easier then what I thought I was understanding in my reads. I did see other people mention that as long as you were s off then everything else just about doesn't matter and then other contradicting that. Got to the point that I thought it made be easier to start all over in combination I was trying to install wine and it failed after about 45 minutes of downloading.
arrrggh.
Click to expand...
Click to collapse
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link: http://bugsylawson.com/index.php/fi...radio-024p320906-101303234-release-signedexe/
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
exad said:
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
Click to expand...
Click to collapse
Thanks again for the help.
andason said:
Thanks. Everything seems to work fine now.
A couple of things to note for others who make look at this thread - After flashing the rom in your link:
1. Hboot will be at 2.14 - So if you wish, downgrade back to 1.09, otherwise you will need to flash the boot.img and then the rom when trying new roms.
2. The after market recovery (will now be oem recovery) will be gone so be sure to reinstall your preferred recovery (TWRP or CW)
3. The touchscreen may not respond in some roms, so you may have to downgrade your touchscreen panels firmware http://forum.xda-developers.com/showthread.php?t=2159863
Thanks again for the help.
Click to expand...
Click to collapse
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
odd that rom would not boot with 2.14..but with 1.09 no problems?
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
There was probably some other factor causing the issue. I boot all roms with 2.14 no problem.
andason said:
odd that rom would not boot with 2.14..but with 1.09 no problems?
Click to expand...
Click to collapse
Which ROM? After s-off?
Sent from my Evita
timmaaa said:
You actually don't need to downgrade your hboot, if you're s-off you don't need to manually flash boot.img no matter what your hboot version is.
Sent from my Evita
Click to expand...
Click to collapse
do i need to downgrade my touch firmware?
claudiuslu2011 said:
do i need to downgrade my touch firmware?
Click to expand...
Click to collapse
You only need to downgrade touchscreen firmware if:
You're on 2.14 hboot + You are flashing an AOSP ROM not yet on 3.4 Kernel.
timmaaa said:
Which ROM? After s-off?
Sent from my Evita
Click to expand...
Click to collapse
It may be I am mistaken. I thought it was baked but i was also trying a rom I was trying to port. During the time i was flashing from 1.09 to 2.14 and also seen that baked required 2.14. So with all that going on i was just trying boot.img and then the rom to ensure no errors.
*** WHAT MY PROBLEM IS***
PLEASE can someone confirm any AOSP ROM that works with 2.15 HBOOT?
***WHAT I KNOW***
( i know the CM 10.2 thread says that RUU 3.18 which will make the hboot 2.14 but since 2.15 is latest i assume it should support)
(i also know that [HBOOT 2.15 is essential for SENSE 5 4.2.2 to run,i believe that's the only reason people go for 2.15)
***WHAT I HAVE TRIED***
NOW from what i have tried is that the 1st stable cm 10 release doesn't work with 2.15 (obviously too old build) my screen also became responsive(i believe that because of touch panel firmware) then with the latest stable release of cm 10.1 it specified that it needs hboot 2.14 and hence couldn't flash.
with PAC 4.3 it does gets installed but screen is unresponsive and infinite bootloops!:silly:
***WILL THIS WORK***
so now if i RUU 3.18 i will have to unlock boot loader and root it (M SOFF SUPER CID) which i m not really ready to do!
now there are methods that can help u downgrade/upgrade your firmware , can i do that?
also will using torched kernel help in me in any way?
***WHY DO I WANT AOSP***
Viper XL 4.2.2 best ROM ever hats off but the thing is i dont know why but i have Signal issues i tried flashing the recommended RADIO version.
since the vendor had already RUUd my device that was meant from some ASIAN region and already came with SENSE 5 and i dint mess up with it in any way still i had signal issues (which are unpredictable) i found by GSAM BATTERY monitor that around 30 to 40% of my battery is consumed by RADIO.
also the best signal is around -81db
i also had some issues with camera!
and then there is the numerous options i can have with AOSP.
****LASTLY CAN ANYONE HELP****
:angel:
Just RUU. Your bootloader will remain unlocked and your S-OFF will remain
After the RUU you can flash recovery and flash a rom. You can technically just flash the 2.14 firmware.zip by extracting it from an OTA or an RUU, but easier to just ruu. and you get a nice clean wipe too.
I misread the m soff part sorry. You could have just run the ruu and twrp and been done in the time it took you to write that post.
Sent from my HTC One XL
954wrecker said:
He makes it hard to understand but he is S-ON so he is screwed at this point
Sent from my HTC One XL
Click to expand...
Click to collapse
no no no i am SOFF i know for sure!!!
exad said:
Just RUU. Your bootloader will remain unlocked and your S-OFF will remain
After the RUU you can flash recovery and flash a rom. You can technically just flash the 2.14 firmware.zip by extracting it from an OTA or an RUU, but easier to just ruu. and you get a nice clean wipe too.
Click to expand...
Click to collapse
jus for the sake for reassurance:
after RUU:
will Bootloader remain Unlocked?
will it still be SOFF?
and SUPERCID?
so these things will survive the RUU?
954wrecker said:
I misread the m soff part sorry. You could have just run the ruu and twrp and been done in the time it took you to write that post.
Sent from my HTC One XL
Click to expand...
Click to collapse
LOL u are right thanks!
its just that m kinda paranoid cause every day in the Help and Troubleshooting section there is some thread dats says BRICKED so always to be on the safer side!
Sonone said:
jus for the sake for reassurance:
after RUU:
will Bootloader remain Unlocked?
will it still be SOFF?
and SUPERCID?
so these things will survive the RUU?
Click to expand...
Click to collapse
yes
exad said:
yes
Click to expand...
Click to collapse
thanks a lot EXAD!!!:good::good:
btw earlier you mentione its possible to extract the firmware file?
how can it be done?
Sonone said:
thanks a lot EXAD!!!:good::good:
btw earlier you mentione its possible to extract the firmware file?
how can it be done?
Click to expand...
Click to collapse
the easiest way is to extract firmware.zip from a 3.17/3.18 ota file for your carrier.
exad said:
the easiest way is to extract firmware.zip from a 3.17/3.18 ota file for your carrier.
Click to expand...
Click to collapse
I wouldn't mess with extracting the firmware files from the OTAs manually. If one of the hboot modules is missing, a brick can result. The OP is probably OK, since he has already manually updated to hboot 2.15. But RUU is still seems the safest way.
redpoint73 said:
I wouldn't mess with extracting the firmware files from the OTAs manually. If one of the hboot modules is missing, a brick can result. The OP is probably OK, since he has already manually updated to hboot 2.15. But RUU is still seems the safest way.
Click to expand...
Click to collapse
as always thank you...
since u recoomend thats the safest way i will try out that.
have to download the RUU 3.18!!!
*waiting*
Hey guys,
Where can I find the RUU for HBOOT 2.15.0000, RADIO 1.13.50.05.31 ?
I've looked all over and cannot find it.
Any help appreciated.
Seconded. I've looked for a RUU on and off for the last several months.
808phone said:
Hey guys,
Where can I find the RUU for HBOOT 2.15.0000, RADIO 1.13.50.05.31 ?
I've looked all over and cannot find it.
Any help appreciated.
Click to expand...
Click to collapse
What is your CID?
92lucio92 said:
what is your cid?
Click to expand...
Click to collapse
my cid:
TMOBO010
thanks!
808phone said:
my cid:
TMOBO010
thanks!
Click to expand...
Click to collapse
Why you need this specific ruu?
It may be this one: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
92Lucio92 said:
Why you need this specific ruu?
It may be this one: http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
Click to expand...
Click to collapse
Thanks! I was told that I needed the same RUU as what I had on the phone or else I could not restore if I didn't have S-OFF.
Are you saying that I can install a _newer_ RUU at any time than what I have?
Thanks,
Aron
Yes, you can always install the same or newer version. To install older you need to be S-off.
Skickat från min One S via Tapatalk
WOW! OK, well that opens things up.
Here's my plan, please tell me if it makes sense.
1: I will try firewater s-off. Let's see if that works. Right now I am back to RELOCKED so we will see if the temporary root method works for firewater s-off.
2: Assuming the above works, I will them put in TWRP recovery (fastboot flash recovery xxxxx)
I would think that this would give me s-off, and finally a custom recovery software.
I am not sure at this point if I need SuperSU if I have s-off and TWRP installed and an unlocked boot loader.
Thanks!!!!
BTW: I had previously unlocked boot loader, installed TWRP, superSU. Tried to install CM11 and when I flashed the boot.img it screwed up my phone. Now I am back to RELOCKED and stock Jellybean.
808phone said:
WOW! OK, well that opens things up.
Here's my plan, please tell me if it makes sense.
1: I will try firewater s-off. Let's see if that works. Right now I am back to RELOCKED so we will see if the temporary root method works for firewater s-off.
2: Assuming the above works, I will them put in TWRP recovery (fastboot flash recovery xxxxx)
I would think that this would give me s-off, and finally a custom recovery software.
I am not sure at this point if I need SuperSU if I have s-off and TWRP installed and an unlocked boot loader.
Thanks!!!!
BTW: I had previously unlocked boot loader, installed TWRP, superSU. Tried to install CM11 and when I flashed the boot.img it screwed up my phone. Now I am back to RELOCKED and stock Jellybean.
Click to expand...
Click to collapse
I would look into moonshine s-off first. I've read of some people having problems with firewater.
Moonshine S-Off
You have to be patient with it, but it's completely foolproof. I've used it on two HTC One S models without fail.
OK, but with moonshine I need to go to HTC dev an unlock the boot loader again. Also I'm worried that it will change HBOOT. Seems spooky.
808phone said:
OK, but with moonshine I need to go to HTC dev an unlock the boot loader again. Also I'm worried that it will change HBOOT. Seems spooky.
Click to expand...
Click to collapse
It's not spooky at all. Even though it changes the hboot, the hboot is technically still listed as 2.15 and is compatible with any ROM in the dev section (except the ones that require 2.16, of course).
Thanks. I noticed another thing. With moonshine I have to update my ROM to :3.14.531.11
808phone said:
Thanks. I noticed another thing. With moonshine I have to update my ROM to :3.14.531.11
Click to expand...
Click to collapse
Yep. It has to be on the stock version of Jelly Bean 4.1 to work. Although I've read that it's also okay if you've upgraded to 3.14.531.17. It will work with that firmware upgrade too if you just use the same process as if it were on 3.14.531.11.
Brushstroke said:
Yep. It has to be on the stock version of Jelly Bean 4.1 to work. Although I've read that it's also okay if you've upgraded to 3.14.531.17. It will work with that firmware upgrade too if you just use the same process as if it were on 3.14.531.11.
Click to expand...
Click to collapse
OK I know my software number is 3.14.531.17
But when you look at something like HBOOT 2.15.0000, RADIO 1.13.50.05.31 how does that correlate to the software number? Is there a way to find out? Very confused by this.
Thanks!
808phone said:
OK I know my software number is 3.14.531.17
But when you look at something like HBOOT 2.15.0000, RADIO 1.13.50.05.31 how does that correlate to the software number? Is there a way to find out? Very confused by this.
Thanks!
Click to expand...
Click to collapse
Hboot version is the version of the bootloader. Radio is the version of the firmware for the equipment in the phone that controls your mobile data/WiFi connection. These usually are upgraded along with a major software update like 3.14.531.11.
Sent from my One S using xda app-developers app
Thanks! I was just wondering why the software version is not listed in the RUU number.
Something like:
HBOOT 2.15.0000, RADIO 1.13.50.05.31 Version 3.14.531.17 RUU
OK, never mind. I can't believe it was so easy to find the RUU. Right on HTC's site!
And HTC DOES list the software number:
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.17_Radio_1.13.50.05.31_10.30.50.08L_release_320836_ICS_2_JB.exe
OK, I am ready to try S-OFF.
Thanks for the help.
808phone said:
Thanks! I was just wondering why the software version is not listed in the RUU number.
Something like:
HBOOT 2.15.0000, RADIO 1.13.50.05.31 Version 3.14.531.17 RUU
Click to expand...
Click to collapse
The software version usually is in the RUU number, actually. The one for yours is:
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2
It notes that it's for the Ville and not VilleC2, and that it is JB (Jelly Bean), that its for T-Mobile US, then the software number, then the radio version. They're all named pretty much in this order.
Sent from my Nexus 7 using xda app-developers app
Thanks for the help guys but moonshine and firewater s-off didn't work for me.
Moonshine gets stuck with a ton of .............. over and over.
Firewater crashes out of adb shell.
Another user has the same ROM etc... he tried all of the options (except all in one toolkit) and none work.
I thought I saw a manual way of getting s-off but I can't find the link now.
Hey guys!!
I've had PAC-ROM on my M4 for quite a long time now, decided to go back to stock because of reasons today.. Everything's fine, used TWRP to recover my stock ROM - I've made a backup
Now, I got the message for the Sense 6 update and I was so happy, it downloaded successfully, everything's well at this point. I click on Install Now and it boots to TWRP and nothing else happens.. I can't find a way to update. Can someone please help? ;/
Thanks in advance!
P.S. Sorry if I haven't posted any helpful information, I don't know what to post So tell me if you need to know anything, I'll share it right away
Peshyy said:
Hey guys!!
I've had PAC-ROM on my M4 for quite a long time now, decided to go back to stock because of reasons today.. Everything's fine, used TWRP to recover my stock ROM - I've made a backup
Now, I got the message for the Sense 6 update and I was so happy, it downloaded successfully, everything's well at this point. I click on Install Now and it boots to TWRP and nothing else happens.. I can't find a way to update. Can someone please help? ;/
)
Click to expand...
Click to collapse
just flash stock recovery instead of custom TWRP
iourikil said:
just flash stock recovery instead of custom TWRP
Click to expand...
Click to collapse
Ok, thanks.. http://forum.xda-developers.com/showpost.php?p=45905821&postcount=2 Is the first mentioned 'here' gonna work? the 1.31.401.1 one?
Thanks again :3
Edit:
I've flashed the 1.31.401.1 and it worked! Currently installing the update ;3
Peshyy said:
Ok, thanks.. http://forum.xda-developers.com/showpost.php?p=45905821&postcount=2 Is the first mentioned 'here' gonna work? the 1.31.401.1 one?
Thanks again :3
Click to expand...
Click to collapse
use recovery.img from this
firmware m4 OTA 3.10.401.4
https://mega.co.nz/#!eBIRwYIR!vGks0Gloq7VpgAD5POrlbBh1HWPfpRIFAxpMahG7Nk4
iourikil said:
use recovery.img from this
firmware m4 OTA 3.10.401.4
URL HIDDEN
Click to expand...
Click to collapse
Ok, thanks! I'll download it right away.. But here's an issue I got while installing the update with the previous recovery.. I get a phone with a red exclamation mark inside a triangle in the middle of updating.. any help ? ;s
Also, can you tell me is there a specific way of installing this recovery? Because there are multiple files and I don't know what to do with all of them ;/
Third edit:
I've just remembered fastboot flashed multiple partitions, so that's what they must be.. so I tried but I get errors on them except boot.img and recovery.img. The radio.img showed an error that the bootloader isn't the correct version or something..
Peshyy said:
Ok, thanks! I'll download it right away.. But here's an issue I got while installing the update with the previous recovery.. I get a phone with a red exclamation mark inside a triangle in the middle of updating.. any help ? ;s
Also, can you tell me is there a specific way of installing this recovery? Because there are multiple files and I don't know what to do with all of them ;/
Third edit:
I've just remembered fastboot flashed multiple partitions, so that's what they must be.. so I tried but I get errors on them except boot.img and recovery.img. The radio.img showed an error that the bootloader isn't the correct version or something..
Click to expand...
Click to collapse
extract file recovery.img from zip archive
and flash it as usual
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
iourikil said:
extract file recovery.img from zip archive
and flash it as usual
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I get the same error... the Phone with a red exclamation mark with a triangle around it.. Is it because I'm rooted. I just searched and it might be it..
Should I follow the guide on theunlockr.com / 2014 / 03 / 18 / unroot-htc-one-mini /
So.. Should I only lock the bootloader or completely unroot it?
I'll try with only locking the bootloader in a sec..
Ok, here's what happens when I use fastboot oem lock : snag.gy / CnD59.jpg .. The bootloader shows as "RELOCKED", which is good.. but I still fail to install the update.. But regarding the un-rooting process, on theunlockr what is posted the .exe is US.. I'm from Bulgaria, which is Europe.. and if I download a UK version of the .exe will it still work ?
Edit.. will a tool like Revolutionary work? I saw it just sets the phone to S-OFF
Peshyy said:
Ok, here's what happens when I use fastboot oem lock : snag.gy / CnD59.jpg .. The bootloader shows as "RELOCKED", which is good.. but I still fail to install the update.. But regarding the un-rooting process, on theunlockr what is posted the .exe is US.. I'm from Bulgaria, which is Europe.. and if I download a UK version of the .exe will it still work ?
Edit.. will a tool like Revolutionary work? I saw it just sets the phone to S-OFF
Click to expand...
Click to collapse
I know that you can't get OTA with unlocked bootloader and rooted, and I don't think you can do it with a re-locked bootloader either.
OTA also failed for me with a "locked" bootloader, where i used revone to set the bootloader to Locked rather than Relocked.
The only way i've gotten OTA to install was to run the Att Ruu.exe to restore to stock. If i run update immediately after that, it works. If i do other things, like unlock, root, etc, the oTA fails, just the same as yours is failing.
If you want sense 6, the easiest way, from where you are now, would be to flash twrp 2.7.1.1 recovery, then install the stock sense 6 rom in the development section. If you're not on the latest firmware (hboot 2.22) then the path is a little longer, as you will have to s-off, then update firmware, then flash sense 6 rom.
jollywhitefoot said:
I know that you can't get OTA with unlocked bootloader and rooted, and I don't think you can do it with a re-locked bootloader either.
OTA also failed for me with a "locked" bootloader, where i used revone to set the bootloader to Locked rather than Relocked.
The only way i've gotten OTA to install was to run the Att Ruu.exe to restore to stock. If i run update immediately after that, it works. If i do other things, like unlock, root, etc, the oTA fails, just the same as yours is failing.
If you want sense 6, the easiest way, from where you are now, would be to flash twrp 2.7.1.1 recovery, then install the stock sense 6 rom in the development section. If you're not on the latest firmware (2.22) then the path is a little longer, as you will have to s-off, then update firmware, then flash sense 6 rom.
Click to expand...
Click to collapse
Ok, thanks for the info.. I don't know how to find my firmware.. It doesn't show up on the About phone menu.. I've gone to the bootloader and it isn't there as well.. if it's the hboot, my hboot is 2.21.0000, meaning it isn't 2.22.. ;/
Also.. can you tell me what *** TAMPERED *** means in the bootloader? Right above *** RELOCKED ***.
And what is the 'Att Ruu.exe'? I don't mind having no root, no unlocked bootloader, etc.. I want the pure HTC experience again..
Edit: I saw that 'Att Ruu.exe' stands for the AT&T model.. the thing is that mine isn't AT&T.. mine is international, I think.. doesn't have any other branding or whatsoever..
Peshyy said:
Ok, thanks for the info.. I don't know how to find my firmware.. It doesn't show up on the About phone menu.. I've gone to the bootloader and it isn't there as well.. if it's the hboot, my hboot is 2.21.0000, meaning it isn't 2.22.. ;/
Also.. can you tell me what *** TAMPERED *** means in the bootloader? Right above *** RELOCKED ***.
And what is the 'Att Ruu.exe'? I don't mind having no root, no unlocked bootloader, etc.. I want the pure HTC experience again..
Edit: I saw that 'Att Ruu.exe' stands for the AT&T model.. the thing is that mine isn't AT&T.. mine is international, I think.. doesn't have any other branding or whatsoever..
Click to expand...
Click to collapse
Hboot was what i was referring to when i said firmware. Sorry, but i don't have any experience with 2.21 so i don't know what ROMs you can flash with it. If i had to guess, i would think one of the older sense 5.5 roms in the dev section would work on it, but i've never been on 2.21, so i can't tell you which ones with any confidence. I don't think any of the sense 6 Roms will work for you, but, again, i don't know for sure as i've never been on 2.21.
Tampered i think comes up when you use custom recovery. I don't know exactly what triggers it, but i don't think just flashing custom recovery does. I think it might happen when you use custom recovery to flash a ROM. It's just a flag and nothing to worry about. It doesn't prevent you from doing anything.
RUUs are executable files that can restore your device to stock. They are carrier and location specific, so you need to make sure you use the one for your carrier and location, if it is available. I said ATT RUU becuase I'm on ATT in the US. RUU files aren't available for every carrier in every country. If you are in the US on Att, i can help you with this. If you are somewhere else or on a different carrier, i can't.
jollywhitefoot said:
Hboot was what i was referring to when i said firmware. Sorry, but i don't have any experience with 2.21 so i don't know what ROMs you can flash with it. If i had to guess, i would think one of the older sense 5.5 roms in the dev section would work on it, but i've never been on 2.21, so i can't tell you which ones with any confidence. I don't think any of the sense 6 Roms will work for you, but, again, i don't know for sure as i've never been on 2.21.
Tampered i think comes up when you use custom recovery. I don't know exactly what triggers it, but i don't think just flashing custom recovery does. I think it might happen when you use custom recovery to flash a ROM. It's just a flag and nothing to worry about. It doesn't prevent you from doing anything.
RUUs are executable files that can restore your device to stock. They are carrier and location specific, so you need to make sure you use the one for your carrier and location, if it is available. I said ATT RUU becuase I'm on ATT in the US. RUU files aren't available for every carrier in every country. If you are in the US on Att, i can help you with this. If you are somewhere else or on a different carrier, i can't.
Click to expand...
Click to collapse
Oh, that's a shame ;//
First - is there a way I can update to 2.22 ? ;/
Second - I mentioned earlier I'm from Bulgaria, which is in Europe. Isn't there an international RUU ? ;(
I've unlocked my bootloader again as I think found a way to make the phone S-OFF.. I just have to root my phone again as it's not rooted -__- I don't want a custom ROM download, I want the stock one with no modifications or anything else.. ;/
Peshyy said:
Oh, that's a shame ;//
First - is there a way I can update to 2.22 ? ;/
Second - I mentioned earlier I'm from Bulgaria, which is in Europe. Isn't there an international RUU ? ;(
I've unlocked my bootloader again as I think found a way to make the phone S-OFF.. I just have to root my phone again as it's not rooted -__- I don't want a custom ROM download, I want the stock one with no modifications or anything else.. ;/
Click to expand...
Click to collapse
Sorry. I missed where you said your location.
To upgrade your firmware, you have to s-off. There's a post somewhere around here that walks you through using revone, which I've done and had success with. I think I linked to it yesterday, so look through my old posts. If you can't find it, I'll send the link later.
But, yes, you have to be rooted to s-off.
I don't know about ruu for Bulgaria. Try looking on the HTC website, or your carrier's website.
The stock roms in the dev section seem to be pretty much 100% stock. I'm not a developer, so I don't know that they are for sure, but I think they are created directly from stock, just modified so you can flash then in recovery.
jollywhitefoot said:
Sorry. I missed where you said your location.
To upgrade your firmware, you have to s-off. There's a post somewhere around here that walks you through using revone, which I've done and had success with. I think I linked to it yesterday, so look through my old posts. If you can't find it, I'll send the link later.
But, yes, you have to be rooted to s-off.
I don't know about ruu for Bulgaria. Try looking on the HTC website, or your carrier's website.
The stock roms in the dev section seem to be pretty much 100% stock. I'm not a developer, so I don't know that they are for sure, but I think they are created directly from stock, just modified so you can flash then in recovery.
Click to expand...
Click to collapse
I tried revone about a hundred times with no success.. I just can't get it to work. I get an error 'Segmentation fault (core dumped)' and that's it -__- I tried googling but with no success.. I'm now trying rumrunner but as I look at the command prompt, it most likely won't succeed as well ;/ Yep.. it failed, said ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
I'm rooted and with unlocked bootloader, installed CWM as well
Edit:
So I found http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921 .. I'm gonna try it out now, it's the same as my update, so yeah..
Peshyy said:
I tried revone about a hundred times with no success.. I just can't get it to work. I get an error 'Segmentation fault (core dumped)' and that's it -__- I tried googling but with no success.. I'm now trying rumrunner but as I look at the command prompt, it most likely won't succeed as well ;/ Yep.. it failed, said ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
I'm rooted and with unlocked bootloader, installed CWM as well
Edit:
So I found http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921 .. I'm gonna try it out now, it's the same as my update, so yeah..
Click to expand...
Click to collapse
I got both of those errors and they were because i really wasn't rooted even though i thought i was.
jollywhitefoot said:
I got both of those errors and they were because i really wasn't rooted even though i thought i was.
Click to expand...
Click to collapse
Yeah, I understood that the hard way.. Tried so many things, nothing worked.. just threw my phone (on a soft place, but still) and won't deal with anything 'til tomorrow.. I'm just so pissed at the moment. The root that should work and has worked before doesn't work now.. I really don't know what's wrong -__- gonna do everything all over again and try to get S-OFF and attempt to fix OTA updates.. ;/
Peshyy said:
Yeah, I understood that the hard way.. Tried so many things, nothing worked.. just threw my phone (on a soft place, but still) and won't deal with anything 'til tomorrow.. I'm just so pissed at the moment. The root that should work and has worked before doesn't work now.. I really don't know what's wrong -__- gonna do everything all over again and try to get S-OFF and attempt to fix OTA updates.. ;/
Click to expand...
Click to collapse
Sorry. I've been there before. If i have time, i'll re-set my phone back to factory, s-on and see if i can remember what i did to fix that error. One possibility was that i didn't have a ROM installed, but i don't remember for sure. I'll see if I made any notes let you know if I remember what i did to fix.
jollywhitefoot said:
Sorry. I've been there before. If i have time, i'll re-set my phone back to factory, s-on and see if i can remember what i did to fix that error. One possibility was that i didn't have a ROM installed, but i don't remember for sure. I'll see if I made any notes let you know if I remember what i did to fix.
Click to expand...
Click to collapse
Whoah, thanks so much! You shouldn't be so kind.. That's so much work to do.. Damn ;/ THANKS!
Peshyy said:
Whoah, thanks so much! You shouldn't be so kind.. That's so much work to do.. Damn ;/ THANKS!
Click to expand...
Click to collapse
What's your exact status:
Unlocked or Relocked?
Tampered?
Which recovery?
Version?
Is there an OS installed or did you wipe?
jollywhitefoot said:
What's your exact status:
Unlocked or Relocked?
Tampered?
Which recovery?
Version?
Is there an OS installed or did you wipe?
Click to expand...
Click to collapse
It's Tampered and Unlocked. I totally formatted everything, put CWM and using stock software.. It's the Sense 5.5 with Android 4.4.2. ClockworkMod Recovery Touch 6.0.3.6