got a uk one s on orange. i couldnt find an orange ruu for it so ive made the cid 11111111.
Its s on but unlocked with htc dev
hboot version 1.13.0000
radio 0.16.3150s.17_2
I dont mind it been an unbranded one, but i just tried one and it failed at the point where it says its rebooting to bootloader, said incorrect device
Moved this thread to the correct section. Remember, questions always go in the Questions and Answers subforum
Now since your SuperCID you can flash whichever you'd like. I would however run an unbranded RUU.
Sent from my One S using Tapatalk 2
I thought as much but can't seem to boot into android after I OEM lock my boot loader.
But if I leave the boot loader unlocked then the ruu won't start.
Any reason I can't boot when I lock the boot loader? Do I need to flash stock recovery before I lock it?
The RUU should put a stock recovery.
First run an RUU, then lock it and run an RUU again imo
Sent from my One S using Tapatalk 2
Related
Hello Everyone,
I need to send my Sensation in for dust removal. I was running CM9, changed my CID back to BM___01 or something for bell mobility, where the phone came from. I then did the
Code:
fastboot oem writesecureflag 3
and got a brick. I unbricked successfully with the unbricking project. Kudos to the devs of that.
I now have a problem. My CID is for bell, so can't flash anything else, error in the ruu.
My hboot is 1.27 and my radio 11.22.3504.07_M, so I can't flash any of the bell ruu because of error 140 wrong bootloader. The only RUUs for bell are gingerbread with really old hboot.
I think I need to s-off and change CID to get a newer ICS RUU on here.
3 questions:
1. can I s-off without any firmware (no recovery, no rom) on the device, so no adb
2. Is there any other way to get a booting rom on here?
3. can I revert back to the gingerbread RUU using some sort of hboot downgrade, once I have something installed? (rom)
Thanks for your help.
jcarrz1
jcarrz1 said:
Hello Everyone,
I need to send my Sensation in for dust removal. I was running CM9, changed my CID back to BM___01 or something for bell mobility, where the phone came from. I then did the
Code:
fastboot oem writesecureflag 3
and got a brick. I unbricked successfully with the unbricking project. Kudos to the devs of that.
I now have a problem. My CID is for bell, so can't flash anything else, error in the ruu.
My hboot is 1.27 and my radio 11.22.3504.07_M, so I can't flash any of the bell ruu because of error 140 wrong bootloader. The only RUUs for bell are gingerbread with really old hboot.
I think I need to s-off and change CID to get a newer ICS RUU on here.
3 questions:
1. can I s-off without any firmware (no recovery, no rom) on the device, so no adb
2. Is there any other way to get a booting rom on here?
3. can I revert back to the gingerbread RUU using some sort of hboot downgrade, once I have something installed? (rom)
Thanks for your help.
jcarrz1
Click to expand...
Click to collapse
Hmm that's a rough situation you are in.. If you can't find the ruu that would be a problem..
First try contacting football.. For ics ruu of bell.. (football provides most of the ruu's.. He is the OP of pyramid shipped rom collections thread present in sensation development section)
Try changing Cid to a well know one
Like this.. What you do is
First reboot to bootloader
fastboot oem writecid HTC__001 (supercid won't work.. So stick with this for now)
Then remove battery..
Then reinsert it. Power on to bootloader
And check Cid
fastboot getvar cid
If this worked.. Great. Find a Europe ruu and flash it
Last .. Try htc-dev unlock.. If luckily you..got unlocked bootloader..
Flash custom rom..Then SOFF..Then change back Cid..Then flash the old ruu of your Cid..Then SON
To get a working rom
Sent from my pyramid.. Through blazing fast sonic waves
For future reference; S-ON is the last thing you do when sending the phone back. RUU needs to happen before that.
The situation you're in, you're going to have to HTC Dev unlock your bootloader, and fastboot flash system and boot, possibly install a firmware PG58IMG as well... hopefully that will be enough to get the phone booting. Then you'll want to S-OFF and flash the RUU (this will also set you back to ***LOCKED***), then you can S-ON.
You guys are so helpful. I will try this.
My utmost thanks,
jcarrz1
Is HTC dev unlock reversible, and does it void my warranty even if I reverse it? does it leave any trace/can they tell?
Getting S-OFF removes all trace of it.
Rusty! said:
Getting S-OFF removes all trace of it.
Click to expand...
Click to collapse
And then getting S-ON again will be like stock configuration?
No, going S-OFF changes ***UNLOCKED*** back to ***LOCKED***
jcarrz1 said:
And then getting S-ON again will be like stock configuration?
Click to expand...
Click to collapse
yep...
if you use juopunutbear soff after HTC-dev unlock ..you will get locked/juopunutbear bootloader (instead of relocked )
then RUU (to make everything stock..and to prevent wrong SON brick) and SON again ..will be complete stock
Again, I am amazed by your helpfulness.
Thanks guys! you run the general section
jcarrz1
I can't flash firmware because it says "parsing package" and then does nothing
I can't push a system.img because it says "too large"
I've tried ARHD, CM9, and stock zippified roms, and none of them boot. Probably firmware issue, but see first problem...
any tips?
jcarrz1 said:
I can't flash firmware because it says "parsing package" and then does nothing
I can't push a system.img because it says "too large"
I've tried ARHD, CM9, and stock zippified roms, and none of them boot. Probably firmware issue, but see first problem...
any tips?
Click to expand...
Click to collapse
ohk for firmware flash you can use this
copy the firmware zip (PG58IMG.zip) to the adb/fastboot folder
open command prompt from adb/fastboot
then these commands one by one
fastboot erase cache
fastboot oem rebootRUU (black screen with silver HTC)
fastboot flash zip PG58IMG.zip (if failed while flashing in the middle ..be careful)
fastboot reboot-bootloader
that would flash the firmware
i have supercid and i locked the bootloader to flash an ruu and restored the recovery to stock and i tried to flash a ruu and it failed and i got stuck in bootloader mode.
i need RUU:
1.84.461.11
and baseband 0.17.31501S.10_2
its israel carrier cellcom.
really need help thanks
more details--
never ran one, but assume you ran correct one
how did you "flash" it--what guide did you use--you don't actually flash it, you actually install/run it--just asking--
rugmankc said:
more details--
never ran one, but assume you ran correct one
how did you "flash" it--what guide did you use--you don't actually flash it, you actually install/run it--just asking--
Click to expand...
Click to collapse
i flashed the stock recovery through modacos website than relocked the bootloader with fastboot oem lock and than ran the exe file and i waited for like an half hour and than i saw some kind of error (don't remember the number) and than phone rebooted into bootloader and got stuck there.
i also wanted to ask if i have supercid does it mean i can install any ruu or it depends on my baseband version and other stuff?
casue i wanted to install the latest tmobile 2.35 ruu and my baseband doesn't match but i have supercid so i dont know what to do.
im new to all this stuff cause i had galaxy s2 and it was a lot easier to play with its system.
sounds like you did it all correctly
are you sure you got the stock recovery--last time i was on the site he listed two recoveries and i had to check them both out to see which one was stock
not sure on supercid as i have not ran one--maybe search, there are some threads and many posts on it--sorry
LSGio said:
i flashed the stock recovery through modacos website than relocked the bootloader with fastboot oem lock and than ran the exe file and i waited for like an half hour and than i saw some kind of error (don't remember the number) and than phone rebooted into bootloader and got stuck there.
i also wanted to ask if i have supercid does it mean i can install any ruu or it depends on my baseband version and other stuff?
casue i wanted to install the latest tmobile 2.35 ruu and my baseband doesn't match but i have supercid so i dont know what to do.
im new to all this stuff cause i had galaxy s2 and it was a lot easier to play with its system.
Click to expand...
Click to collapse
If you have SuperCID you can flash an RUU from any carrier as long as it has an HBOOT version equal or greater than your current one.
Sent from my HTC One S using Tapatalk 2
I cannot boot into ROM, but stuck at Bootloader. And I'm relocked.
The only thing I have is Fastboot USB.
I would like to RUU into a Stock ROM. How to do so?
Well ruu should be pretty self explanatory. If you are in the boot loader just run the ruu. Since you are relocked shouldn't take much work. Are you s-off? Why not just grab an AT&T ROM and flash it over. Sure it will be rooted, but delete the super user app
Sent from my Carbon-ize Evita using xda-developers app
Yeah, I just figured it. RUU was some executable file. I thought it was more complicated. No I'll just leave it like this and not S-Off, thanks. Apparently I'm not more than 30% battery though. But how do I see the battery from the Bootloader screen?
I dont believe you can. Only from recovery. Just let it charge for about 20-30 mins and you should be good
Sent from my Carbon-ize Evita using xda-developers app
If you have supercid and s-on running a ruu will brick your phone just a warning
Sent from my HTC One X using Tapatalk 2
How do I check if I have SuperCID or not?
And apparently the device name is GT-9100 which seems wrong...?
There is command in fastboot I think it is fastboot get cid but not sure do you have a att phone
Sent from my HTC One X using Tapatalk 2
Nope, I do not. I do not need to worry about that then.
No you should be ok att phones are the only ones that had to change there cids to unlock bootloader
Sent from my HTC One X using Tapatalk 2
Fastboot oem readcid
Sent from my One X using xda app-developers app
exad said:
Fastboot oem readcid
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Thanks couldn't remember what it was
Sent from my HTC One X using Tapatalk 2
Oh no! Can anyone please help me?
None of the RUUs work.
I'm Asian and I tried all:
1.88.707.2 ( Error 170, bad USB )
2.23.707.2 ( Error 170 )
This is the only one that I could select ROM and upgrade.
3.17.707.1 ( Less than 30% error is result of previous fail, so reboot. Actual Error 155 )
And I'm S-ON
hboot 1.09
radio 0.17a.32.09.16_2
OpenDSP - What's this and is it useful for my situation?
eMMC - boot
Apr 2 2012, 21:08:21
I think probably I can only install 3.17 RUU is because my last working ROM was CM10.1. After that I tried Sense ROMs but many failed hence I thought of doing Relock and RUU.
Is there any other thing I can do in my bootloader state? I tried Factory Reset.
Is it possible I attain S-OFF from here and flash recovery and flash OTA from there?
Or even better yet, can I try doing OTA from this state?
Aerodeath said:
And I'm S-ON
hboot 1.09
radio 0.17a.32.09.16_2
OpenDSP - What's this and is it useful for my situation?
eMMC - boot
Apr 2 2012, 21:08:21
I think probably I can only install 3.17 RUU is because my last working ROM was CM10.1. After that I tried Sense ROMs but many failed hence I thought of doing Relock and RUU.
Is there any other thing I can do in my bootloader state? I tried Factory Reset.
Is it possible I attain S-OFF from here and flash recovery and flash OTA from there?
Or even better yet, can I try doing OTA from this state?
Click to expand...
Click to collapse
I thought if you ran the ruu with s on you could brick...just obtain s off and then run the ruu
Sent from my Carbon-ize Evita using xda-developers app
I can't successfully S-OFF because I can't get into Android, stuck at bootloader.
And I'm not on AT&T, I don't need superCID and I can't change it to 11111111 either...
My CID is HTC__044
version-main is 1.88.707.2
Bootloader relocked
hBoot now 2.14?!
RUU_Evita_UL_hTC_Asia_WWE_1.88.707.2_R3_Radio_0.17a.32.09.16_2_10.88.32.17L_release_263455_signed should work but it didn't...
Never mind, everything seems to be working now.
It seemed that my hboot was too low to attempt RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed and Running as Administrator helped too.
Aerodeath said:
I can't successfully S-OFF because I can't get into Android, stuck at bootloader.
And I'm not on AT&T, I don't need superCID and I can't change it to 11111111 either...
My CID is HTC__044
version-main is 1.88.707.2
Bootloader relocked
hBoot now 2.14?!
RUU_Evita_UL_hTC_Asia_WWE_1.88.707.2_R3_Radio_0.17a.32.09.16_2_10.88.32.17L_release_263455_signed should work but it didn't...
Never mind, everything seems to be working now.
It seemed that my hboot was too low to attempt RUU_EVITA_UL_JB_45_S_hTC_Asia_WWE_3.17.707.1_Radio_0.23a.32.09.29_10.128.32.34a_release_298958_signed and Running as Administrator helped too.
Click to expand...
Click to collapse
I'm telling you this because I don't want you to go through what I did.
I'm on a telus one x, did not need super cid to unlock my bootloader. I relocked and flashed stock recovery, ran RUU. The RUU completed successfully but my phone was a full brick. Only JTAG would have saved it.
If you want to RUU, re-unlock your bootloader, flash recovery, flash stock rooted sense rom, hex edit your CID to 11111111 and S-OFF, then RUU. It's a lot safer now that you've unlocked your bootloader and rooted.
exad said:
I'm telling you this because I don't want you to go through what I did.
I'm on a telus one x, did not need super cid to unlock my bootloader. I relocked and flashed stock recovery, ran RUU. The RUU completed successfully but my phone was a full brick. Only JTAG would have saved it.
If you want to RUU, re-unlock your bootloader, flash recovery, flash stock rooted sense rom, hex edit your CID to 11111111 and S-OFF, then RUU. It's a lot safer now that you've unlocked your bootloader and rooted.
Click to expand...
Click to collapse
It's okay, I was running an international One XL, and luckily RUU was smooth, now the problem is solved and my phone has been sold and changed hands .
I have a One XL with o2 Germany Branding (CID: O2___102)
HBOOT 2.14
S-ON
ROM installed: CM 10.1
I want to relock it and flash a Stock ROM. Reason is that I want to send it to warranty.
As far as I know the HBOOT of the ROM must not be older than 2.14 and I can't find an appropriate ROM.
1. fastboot oem lock
2. launch RUU (I tried some, but it did't work)
Do I have to flash a Stock Recovery after that?
Running an RUU returns the phone to being completely stock, including recovery. I hope your don't have SuperCID or you're gonna brick. Click the link in my signature, you'll find RUU threads there.
Sent from my Evita
timmaaa said:
Running an RUU returns the phone to being completely stock, including recovery. I hope your don't have SuperCID or you're gonna brick. Click the link in my signature, you'll find RUU threads there.
Sent from my Evita
Click to expand...
Click to collapse
And what if none of these RUUs work?
O2:
OTA_EVITA_UL_JB_45_S_O2_DE_3.17.207.1_0.23a.32.09. 29_10.128.32.34a_release_2990766qakrzbj4mpslnsy.zi p
OTA_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1-1.92.207.3_release_272963z2vl7cdycjk01nm4.zip
fly23 said:
And what if none of these RUUs work?
O2:
OTA_EVITA_UL_JB_45_S_O2_DE_3.17.207.1_0.23a.32.09. 29_10.128.32.34a_release_2990766qakrzbj4mpslnsy.zi p
OTA_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1-1.92.207.3_release_272963z2vl7cdycjk01nm4.zip
Click to expand...
Click to collapse
Those are ota updates... A ruu is an exe file that is run from Windows
Sent from my HTC One XL using xda app-developers app
The available o2 RUUs are too old
Sent from my One X using Tapatalk 4
So you run an older RUU and then take OTAs, you can't just flash OTA files, it won't work. You need to return the phone to being completely stock first though, s-on, original CID, locked bootloader, original recovery.
Sent from my Evita
I tried this file: RUU_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1_Radio_0.19as.32.09.20_3_10.107.32.25L_release_272946_signed.exe, it didn't work (contentual: Error 170, USB Error)
The XL is S-ON (never was S-OFF), bootloader is relocked (fastboot oem lock), then I launched the RUU.exe.
What I read is, that I can't flash older ROMs (what ever that means). So, what can I do if the o2-RUUs are to old? Can I downgrade the HBOOT?
edit: Can I downgrade HBOOT with the JET (http://forum.xda-developers.com/showthread.php?t=1940512) and then ran a RUU?
i wanna flash RUU on my HTC One S and for that i need to know my version-main but when i go to fastboot and type "fastboot getvar version-main"
it shows blank!
also when i type "fastboot getvar all" i see everything but the version-main is blank! why?
is there any other way to determine which RUU i need?
What is your CID?
Sent from my Nexus 5 using Tapatalk
attelaut said:
What is your CID?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My CID is :
HTC__K18
i'm from israel!
can you help me find my ruu?
This RUU might work if your One S is S4 model.
What do you mean might work?
I have two questions:
If it doesn't work would my phone Get bricked?
How do I properly flash a RUU?
this is my current state:
Bootloader unlocked
Team win recovery
Cyanogenmod 10.2
Edit:yes,i have the snapdragon s4 (z520e)
Sent from my HTC One S using xda app-developers app
LSGio said:
What do you mean might work?
I have two questions:
If it doesn't work would my phone Get bricked?
How do I properly flash a RUU?
this is my current state:
Bootloader unlocked
Team win recovery
Cyanogenmod 10.2
Edit:yes,i have the snapdragon s4 (z520e)
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I'm not sure if there is RUU for your CID. I tried to Google that but I didn't find much. If you've bought your phone from carrier, then there is probably no RUU for your phone. If the CID doesn't match, then RUU won't run at all and it will throw an error. To run RUU you need to have locked bootloader and stock recovery.
attelaut said:
I'm not sure if there is RUU for your CID. I tried to Google that but I didn't find much. If you've bought your phone from carrier, then there is probably no RUU for your phone. If the CID doesn't match, then RUU won't run at all and it will throw an error. To run RUU you need to have locked bootloader and stock recovery.
Click to expand...
Click to collapse
if i relock the bootloader and flash stock recovery (please give me a link for it)
so can i flash the RUU mensioned erlier?
what if it fails?
Follow this guide to do it. You don't need to root since you have CyanogenMod. The links to XDA threads doesn't work, but all you need is RUU and all in one toolkit for One S which should be in Android Development section on this forum. Also you need to have the unlock token for your device.
If the RUU doesn't work, then you can try another RUU if you find correct one for your device. Some have went as far as changing CID to HTC__001 to run the European RUU, which I linked earlier, but to do it you need to unlock bootloader again.