Hi,
I'm trying to get a One S back to stock for a friend but failing...
The phone is unlocked, S-ON, hboot 1.14, 02_01 CID, has CWM recovery and rooted Cyanogenmod 10.1 installed, battery 100% and runs fine as is...
So, first of all I re-lock ready to run this RUU:
RUU_Ville_U_O2_UK_1.78.206.4_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258707_signed
but every time half way through it fails with the following errors in the attached screen shots...
A point to add is as soon as I re-lock the phone, it then will not boot but goes straight into hboot every time which I thought was strange..?
Anyway, some guidance would be very welcome to get this One S back to stock,
EDIT: Just flashed S4 Stock Recovery and the RUU still fails half way through, any ideas..?
Can anyone give me links to O2__01 HTC One S RUU files, can't find any live one anywhere..??
Thanks
Getting a RUU to run correctly is very hit and miss. The page below is a useful guide to double check the basics:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Post 9 details that with s-on you can't flash a RUU with a radio version older than the one you are on already. This may be your problem as I think your radio version will be 1.06 and the one in the RUU you are trying to run is 0.16. The problem with s-on is you can't flash radio's to do anything about that.
The RUU that should work is the one listed below, but I can't find any decent download links for it, like you said. Just try googling it and see if anything turns up.
RUU_Ville_U_ICS_40_S_O2_UK_2.38.206.2_Radio_1.08es.50.02.16_10.09b.50.04L_release_278818_signed.exe
rosswhite said:
Getting a RUU to run correctly is very hit and miss. The page below is a useful guide to double check the basics:
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Post 9 details that with s-on you can't flash a RUU with a radio version older than the one you are on already. This may be your problem as I think your radio version will be 1.06 and the one in the RUU you are trying to run is 0.16. The problem with s-on is you can't flash radio's to do anything about that.
The RUU that should work is the one listed below, but I can't find any decent download links for it, like you said. Just try googling it and see if anything turns up.
RUU_Ville_U_ICS_40_S_O2_UK_2.38.206.2_Radio_1.08es.50.02.16_10.09b.50.04L_release_278818_signed.exe
Click to expand...
Click to collapse
Thanks rosswhite, I think you are right about the radio and no I can't find any download links that work either...
Another thought, does anyone have or know where to get a nandroid backup of O2_01..?
topcat888 said:
Thanks rosswhite, I think you are right about the radio and no I can't find any download links that work either...
Another thought, does anyone have or know where to get a nandroid backup of O2_01..?
Click to expand...
Click to collapse
Your other option of course is to S-OFF the device. You can then flash any radio or RUU you want.
Related
I've made S-off with Revolutionary method to upgrade my Radio, after I've made the upgrade I'm still having issues with my signal, so I'm thinking to send the phone in warranty, but I can't manage to do the S-off.
Do you have any solutions?
Alternate way to restore your phone to S-ON and stock
Hi,
I've spent the last few days digging through the internet, looking for ways to get my Desire S back to S-ON after AlphaReveX S-OFF. The reason? I need to send it in for repair due to a birth defect.
I thought I'd share the path which turned out to be successful. Remember that there's always a risk that your phone will end up bricked as a result of procedures like this. I take no resonsibility for bricked devices, this is just a statment saying what worked for me. Good luck.
My initial setup was AlphaReveX S-OFF with Clockworkmod Recovery and LBC Mod. As the ARX HBOOT can't be overwritten by the HTC update program, it has to be replaced by a HBOOT that can. Luckily I found this thread in which Igl0 provides a pretty much tailor made HBOOT for this purpose:
http://forum.xda-developers.com/showpost.php?p=15493125&postcount=1.
The only problem: It couldn't be flashed in the bootloader (it would just return the message "parsed .."). After this I tried flashing through ADB, but for some reason it didn't work either. My third attempt was more fruitful - I successfully flashed engHBOOToverARX.img through fastboot (HTC drivers required which you probably already have).
Just to keep things simple I've made a zip which contains the files needed (except HTC drivers) to perform this flash. This guide assumes that you have already tried other methods and are familiar with related terms.
1. Connect phone to PC and navigate to fastboot
2. Download and extract the compressed folder attached to this post
3. I've composed a simple .bat (called "Click This") that will open a cmd prompt
and execute the command: fastboot flash hboot engHBOOToverARX.img.
4. Restart and enter HBOOT.
Click to expand...
Click to collapse
If the file was transferred and flashed correctly, the header text in HBOOT should now read "ENG HBOOT ...".
Now you can go ahead and flash a HTC stock RUU. It will overwrite other customisations such as a custom recovery. The HTC Update failed on my first attempt (file: RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release), but luckily I found another RUU that worked (RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed). You can browse this great collection to find one that suits you: http://forum.xda-developers.com/showthread.php?t=1002506.
As my first RUU installation failed partially, I was left with only the stock HBOOT and a non working recovery. Though, I found out that I could perform the next HTC Update attempt while in fastboot, and it was successful this time.
Cheers
Maarten
Thank you very much for the answer, I'll try this way. but before this can you tell me please if this will be a problem the fact that now I have a stock branded Orange ROM? When I did the S-off I didn't changed the ROM, I only changed my radio.
Thanks !!!
More questions....I'm afraid
sebysebu said:
Thank you very much for the answer, I'll try this way. but before this can you tell me please if this will be a problem the fact that now I have a stock branded Orange ROM? When I did the S-off I didn't changed the ROM, I only changed my radio.
Thanks !!!
Click to expand...
Click to collapse
You need to provide more information and details like Settings->About Phone-> Software info Radio (Baseband),Build Number,Kernel etc
If you know what radio version you had on your phone when you got it and what you have now that would be useful.
As I believe what you're saying is that you still have the same ROM version (ORANGE) as your phone came with, but you've simply changed radio and S-OFF'd!?
Do you have a custom recovery installed ie CWM (clock work mod)?
Having a branded ROM shouldn't effect your signal reception...
sebysebu said:
Thank you very much for the answer, I'll try this way. but before this can you tell me please if this will be a problem the fact that now I have a stock branded Orange ROM? When I did the S-off I didn't changed the ROM, I only changed my radio.
Thanks !!!
Click to expand...
Click to collapse
Okay. I'm afraid I don't have the competence to answer that!
ben_pyett said:
You need to provide more information and details like Settings->About Phone-> Software info Radio (Baseband),Build Number,Kernel etc
If you know what radio version you had on your phone when you got it and what you have now that would be useful.
As I believe what you're saying is that you still have the same ROM version (ORANGE) as your phone came with, but you've simply changed radio and S-OFF'd!?
Do you have a custom recovery installed ie CWM (clock work mod)?
Having a branded ROM shouldn't effect your signal reception...
Click to expand...
Click to collapse
Now I have: Radio : 3805.06.02.03_M
Build number : 1.47.401.4
Kernel : 2.6.35.10
Before I don't know what radio I had.
Yes, I have the same ROM version (ORANGE) that camed with the phone, and I'd simply changed the radio after S-off by Revolutionary
I don't have any custom recovery installed.
Regards,
Thanks!!!
I have a Desire S currently running ICS. I've been following this guide robotcantalk.blogspot.co.uk/2013/03/i-desires-jellybean.html in an attempt to upgrade to JB using CM10.1 Build 22.
I've followed it to the letter. In short everything works fine until I go to install the older RUU. The RUU still detects my version as 14.* so my guess is the misc_version command isn't working. I've been chasing my tail on this for nearly 24 hours now so posting here is my last ditch attempt before accepting I can't do it and possibly going out to buy a new phone.
Because misc_version didn't seem to be working, I tried substituting that part of the guide with flashing SetMainVersionLOW.zip via 4EXT recovery but again, when I went to install the older RUU it still sees my version as 14.* and the RUU tells me to get the correct update.
Any ideas what might be causing this?
I just need to get HBOOT 0.98 then I can follow the rest of the guide and use revolutionary. I feel so close but left banging my head against the wall here.
Did u try the downgrade guide here on xda?
http://forum.xda-developers.com/showthread.php?t=1318919
I followed this and it worked first time, have a read at it, maybe u missed something from the other guide.
Thanks, I'll give it a go. I went to a lot of sites/links, but not sure I've seen this one.
The guide needs updating like many others. All goldcard makers point to revskills.de and this site appears broken.
Is the goldcard essential or just a precaution? If it's essential, my next question is how to create one without using the revskills link? I tried flashgc, and this didn't work.
Is ur phone branded?
If ur phone is unlocked/unbranded like mine (my cid is HTC_001) then i used the htc_europe_1.47xxxxxxx ruu and worked perfect. so i coulda used a WWE ruu aswell.
If ur phone is branded, o2 lets say then u would have to use the correct ruu.
If u cant find/get the correct ruu for ur phone then yes u would need a goldcard so that u could use one of the WWE or europe ruu's instead. So basically the goldcard bypasses the cid check of the ruu.
Yes, my phone is unlocked/unbranded. I was trying to downgrade using the RUU from the guide in my OP (RUU_Saga_HTC_Europe_1.28.401.1). I'll try skipping the goldcard and running the same RUU as you...
martinistripes said:
Yes, my phone is unlocked/unbranded. I was trying to downgrade using the RUU from the guide in my OP (RUU_Saga_HTC_Europe_1.28.401.1). I'll try skipping the goldcard and running the same RUU as you...
Click to expand...
Click to collapse
Ul be fine so, just follow that guide step by step, and when u do the part with misc version just make sure u type in the exact number of the ruu ur going to use. Then relock ur bootloader and run ruu. Good luck
jmcclue said:
Ul be fine so, just follow that guide step by step, and when u do the part with misc version just make sure u type in the exact number of the ruu ur going to use. Then relock ur bootloader and run ruu. Good luck
Click to expand...
Click to collapse
This worked great. No requirement for the goldcard. In the guide I was following previously, the misc_version entry was NOT the same as that of the the RUU suggested. Either this is why it wasn't working, or it's because I used a different RUU (the one you used).
Very happy I posted here now. :good:
Could you mark the thread as solved, it may help someone else out
“Paying alimony is like feeding hay to a dead horse.”*―*Groucho Marx
Had my HTC ONE S for a while now
When i first got it i followed all the guides to unlocking the bootload and rooting etc and ended up running viper rom, and various others along the way. You know how it is!
Anyhow i was fiddling once and some how managed to delete the sd card and it wouldnt mount.
I fixed that and im not sure if its a coincidence but i now have random call drops even with a good signal. radio randomly coming on and music apps closing...........mainly when using head phones....................
The following is what was suggested to me.................
Sneakyghost said:
Not easy. I'd say do S-OFF as the very first thing (well relatively, of course do the unlock, do the SuperCID, then...). S-OFF ensures you can just flash any RUU and no matter if locked or unlocked or on custom ROM or not.
You can also only do SuperCID and flash any RUU.
Once done, pick the 3.16 WWE RUU. Please do NOT do the OTA which is offered on that RUU if you do not have S-OFF yet as that OTA disables any chance to get S-OFF currently.
If you happen to sit in the US and are on Tmobile, check HERE for latest tmob RUU because you might want Wifi calling and such. Else, just select any you like. I recommend WWE though.
Not really hard then once you got S-OFF. The hard part is understanding S-OFF procedure. If you get that done everything else is pretty easy. There is a thread for S-OFF with a good guide.
Regarding GPS Fix from Crypted: http://forum.xda-developers.com/showthread.php?t=1563226 (have that open in my browser always cause its a magic little fix)
Click to expand...
Click to collapse
Apparently my htc one s is a international one?
Your CID "HTC__001" Suggests you have an international one X and not a carrier locked one xl. You will need to post in the international one x forums.
Click to expand...
Click to collapse
Any ideas on what i do now as i cant find a htc one s international forum?
EDIT: regarding the above, no one seemed sure and i couldnt seem to find a definitive answer so rather than messing around changing the cid and risking a brick. Some one suggested RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
as my radio is 1.06es 50.02.31 and the 2.31 works with hboot of 1.14 which mine also is....................
after all this im even more confused lol!
So currently ive relocked the bootloader using fastboot and run the above RUU and im back to stock i believe?
What would one suggest?
im on hboot 1.14.0002 and radio is 1.06es i believe.
Ideally id like to get back to viper rom
Might test for a few days if i can resist a custom rom just to check
thanks
Even I'm on hboot 1.14.. Get an S-OFF, flash a latest radio ie., 1.15. That should work.
so ifi flash s off i can run any run any ruu without risk of bricking? by changing the cid thing thanks?
Gavin01 said:
so ifi flash s off i can run any run any ruu without risk of bricking? by changing the cid thing thanks?
Click to expand...
Click to collapse
Risk of bricking came from.SUPER-CID and OTA update, also downgrading h-boot.
first get supercid, then get S-off, then change cid back to original or desired one. if you have a international S4 device original cid wil do fine.
then ruu what you want, s-off simplifies flashing of ruus and roms and more things.
if you might update the device with latest jb without S-off you cant get S-off no more (as of now), you now have the option.
you can always revert back.
Right guys im still not reallty understanding all this sorry.
My phones now coming up with OTA update which i understand i shouldnt run as this then blocks all chance of getting S-Off in the future?
As i understand it my HTC one is a international one so i dont need to change the cid?
So i need to do is get S-Off and run another RUU?
Ill try and follow the guide to S-Off but even that im struggling with Can anyone tell me what RUU i should be running when i manage to get S-Off. My details are above in the first post i think>?
Thanks for your patience.
You need supercid to get soff (face palm)
Then change cid back to original HTC one. To do any otas you want.
Advice:
Before you start. look at your current software version Google the ruu from that info, save the file. When need to ever change back in the future, and then ota back to latest version.
Verstuurd van mijn One S met Tapatalk
im still scared of this super cid thing as ive read a few people have bricked their phones
Although i keep getting the annoying message that a system update is available so i must try and do something soon.
Unless i just go straight to viper
Gavin01 said:
im still scared of this super cid thing as ive read a few people have bricked their phones
Although i keep getting the annoying message that a system update is available so i must try and do something soon.
Unless i just go straight to viper
Click to expand...
Click to collapse
If it's just the message you want to get rid of, just turn off automatic update checks.
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me
Hello
Ok .. since i see some nice gentlemen here responding to queries with patience .. I'd like to post one myself.
I obtained S-Off the very next day i got my One S .. things were running smooth on stock. Looked out for some ROMS and finally installed one. Now I want to revert to my stock ROM while maintaining S-off/root. My problem is only that i don't find this ROM stable or the kernel .. just want to revert to stock.
Will flashing 3.16 WWE RUU take me back to stock firmware and kernel?
Would really appreciate the help
Evening, gents.
I'm trying to update my hboot so I can begin flashing newer roms. I'm stuck on hboot 1.14 and as many others have been posting about, it's giving me issues.
Anyway, here are my details:
S-Off
CID 22222222
hboot 1.14.0002
getvar version-main returns: 2.20.502.7
I've been messing around with my phone for a couple of weeks, trying this and that to update it, but nothing seems to be working. I even tried using a new RUU, but it doesn't seem to recognize my phone (it runs, and Windows says the software didn't install properly, but doesn't give me details).
Sorry for the vagueness - I'm not really sure what else would be pertinent at this point.
Any help would be greatly appreciated!
The only way you're meant to update is via the 3.18 RUU, this is because it isn't just the hboot you're meant to update, it's the firmware as a whole. So any other method you've attempted is wrong. Are your drivers up to date? Do you have HTC Sync Manager installed? If so you should uninstall that (leave drivers installed) because it can get in the way.
Sent from my Evita
timmaaa said:
The only way you're meant to update is via the 3.18 RUU, this is because it isn't just the hboot you're meant to update, it's the firmware as a whole. So any other method you've attempted is wrong. Are your drivers up to date? Do you have HTC Sync Manager installed? If so you should uninstall that (leave drivers installed) because it can get in the way.
Sent from my Evita
Click to expand...
Click to collapse
I saw where you recommended that to someone else, and tried it earlier this evening. It didn't work for me earlier, but I tried it again anyway. It worked this time! I think this was more the fault of Windows being unclear than anything...
I got the same error, but I told Windows to proceed "with default settings" (it didn't really say what those were), but either way, it fixed it. I now have hboot 2.14. Thanks a bunch for your help!
Now, off to re-install a custom recovery. Away!
Flashing firmware.zip from OTA's in rebootRUU mode in the order OTA's would flash them is also a valid way to update firmwares.
firmware.zip from first release 3.17 or 3.18 is always a "full" firmware.zip, then just follow the OTA chain to the latest.
Or if you are s-off you can make use of one of the modified firmware.zip's by Turge, Carl and others. Depending on the one you chose you will get a fair chunk of the firmware files. Some only include the radio in particular and lack sbl's etc. I personally prefer to do everything rather than just some of the key pieces(like radio and hboot).
Eg Turges is fairly well complete.
Hi, could you please help me http://forum.xda-developers.com/showthread.php?p=48178634#post48178634
Okay....so I need to twiddle around with my trusty old HOX in order to solve the constant rebooting issues. (I also want to jump ship off of the memory-heavy Viper Venom that's on it to just straight CM or something similarly light weight)
To do that I've got to update the firmware.
And to do that... first I have to identify what bloody firmware I have so that I use the correct updating method and don't brick my one and only device.
I'm not a total noob... I've been working on a beginner/moderate level with Android for 3 years now... I can get around ADB (typos not withstanding) reasonably well, push commands, get to hboot, know fastboot and such... but I am just not finding the specific answers I need right this moment to get this work done. So if Someone can point me in the proper direction, I would be muchly appreciative.
Right Now my bootloader screen says the following
Tampered
Unlocked
Evita PVT Ship S-ON RLHboot 1.09.0000
Radio 0.20os.32.09.10_2
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
So, who can tell me which firmware version contains Hboot1.09? Once I know that, I can start the process of SuperCID and S-OFF to make these updates. Barring that, anyone who can point me to a one-click unlock tool would be great too... the ones I find on the first few pages of the forum all recommend firmware newer than what I know is installed on here according to the above into, and I am leery to use them for risk of bricking my one and only phone.
Your current firmware is actually irrelevant, you need not worry about that at all. All you need to do is get s-off, which should be a sinch. Because you don't have SuperCID (I'm assuming from your last paragraph) you really only have one option, which is the Rumrunner method. It should work with Viper installed, if not it has a good success rate with the Kickdroid ROM.
Rumrunner S-off
Sent from my Evita
So I did have SuperCID... a readCID command demonstrated that.
and thanks to your assuaging my fears, timmaaaa, I was able to flash to 2.15 without a problem.
the problem now... is even after pushing TWRP every way I know how, I can't get into recovery, even with fastboot erase cache. ugh I feel like yanking my hair out.
but at least the phone hasn't randomly slowed down or rebooted since flashing the new firmware. (and the pesky double-reboot that made flashing it such a core in the first place is fixed too)
::edit:: gonna spend the next hour redownloading the venom ro so I can push the boot.img file, maybe that will fix things.
Did you check the md5 of the recovery download?
Sent from my Evita
timmaaa said:
Did you check the md5 of the recovery download?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did. I also tried to install it via a few onboard solutions like goo.im. no go. it says it's been installed, fastboot insists the phone is unlocked and s-off; but it boots to the flash screen, tries to load recovery, fails, and reboots to the rom.
I am going to assume that the unlock is fubar somehow and start from scratch by installing 2.20 and using the HTC unlock, and go from there.
now if only damned downloads didn't take 5 hours on my slow rural connections... thank you isp conglomeracy.