I'm trying to get my father's phone ruu'ed to 3.14 tmo.
I rooted his phone and unlocked through htc dev a long time ago.
He is currently running cm10 w/ hboot 1.09 and radio 0.16.31501s.
S-on w/ tmo CID.
I used faceplam S-off on my phone and lost 3g/4g. I do not want this to happen to his phone.
So what I'am asking is what do i have to do to get his tmo HTC ONE S safely onto the JB 3.14 from htc/tmo?
When i try to ruu using the 3.14 i get ERROR [159]: IMAGE ERROR. It says i have the wrong image and to download the correct one. Its the same one i used on my phone repeatably.
Any help would be great. Really afraid of borking his phone.
after some googling. I found that the ruu has to match the hboot and be re-locked. Some one also suggested flashing a stock zip and stock recovery. However i cant find a stock rom zip for 1.53. So i just tried re-locking and ruu'ing, but now i get ERROR 155.
Any help would be great. Again i can't s-off for fear of being stuck on edge like my phone
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4132mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
billydroid said:
after some googling. I found that the ruu has to match the hboot and be re-locked. Some one also suggested flashing a stock zip and stock recovery. However i cant find a stock rom zip for 1.53. So i just tried re-locking and ruu'ing, but now i get ERROR 155.
Any help would be great. Again i can't s-off for fear of being stuck on edge like my phone
Click to expand...
Click to collapse
tmobile U.S.
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.exe
http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
to relock
while phone is in bootloader >fastboot USB
fastboot folder, shift right click open command window
from command window type
fastboot oem lock
(also heard but haven't tried because I'm S-Off that you can run RUU.exe from fastboot USB without relocking bootloader)
Edit: to answer the bootloader question. Yes you can ruu a different hboot as long as it is a higher hboot. (s-off no matter)
I got it. I had to re-lock and run ruu 1.84 rc2 first. Then it let me ruu 3.14.
Sent from my HTC VLE_U using Tapatalk
Related
Hi people i am stuck on splash screen with No bootloader, rom or recovery s-on locked bootloader hboot 1.18.0000
Any ideas???
ave you:
Pulled the battery, replaced it - pressed and help the powerbutton and volume down button, released the power button, got the screen with 3 androids?
If so you can then reflash the stock RUU and get back up in no time
I only get the splash screen inless i put in and unplug usb cable then i just get the hboot version ect.....
I can do a few fast boot commands but with the hboot 1.18.0000 i dont get advanced ones so screwed there. The ruu's have wrong bootloader error.
Im pretty screwed really!
what do you mean by "ruu's have wrong bootloader error"? If that stuff still works.. you should be able to fix it easily. I'm banking on the assumption that you're running the wrong RUU's and don't have SuperCID hence the "bootloader errors" (which I have no idea what that is!)
It comes up with error wrong bootloader error. I think its something to to do with the hboot version. I have tried every single ruu for the sensation.
any1 got any ideas as its still screwed x
What software version were you on before you tried to root/S-OFF?
i was on miui and had s-off unlocked and it was rooted. i am now s-on ***relocked*** and hboot 1.18.000 with no rom or recovery and with usb cable in its stuck on splash screen.
I mean what was your original ROM that was on it when you first got the phone? Without that it's hard to suggest an RUU to use
cant remember but i have ttied every ruu on shippedroms.com
i have supercid still by the way
You are not able to S-off thru revolutionary?
I have had this fone stuck like this since jan surely someone must know a way??
If hboot 1.18.000 supported advanced fastboot commands i could just put a recovery on it and then go from there. Sadly i cant and i cant find a way to send a hboot 1.17 while on 1.18 to the fone???
No it looks for adb devices. I only have fastboot.
Dunno if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.18.0000
(bootloader) version-baseband: 11.15.3504.16_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.401.1
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3989mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 9d24123f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.494s
So connecting in fastboot to the PC and running the RUU doesn't work? Have you tried the PG58IMG.zip method of flashing an RUU?
Yes mate i have ttried that as well :-( wen i unplug the usb cable i just get to the hboot screen and the only thing it says is ruu where the recovery option used to be.
:-( I think its dead and needs stamping on!
Someone must have an idea???
Im using a ****ty fone that only calls and sends txts plus onlu holds a few messages so i cnstntly have to clear my inbox :-(
Please help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
OK, lets see if i can help at all.
Lets get the basics sorted, what phone, what rom - original and before problem, what CID - original, which country / network, was it locked / branded...?
Then what steps did you do to end up messed up as you are? You say you had s-off and unlocked? Did you try to s-on, do a bad flash, update firmware, pee on the phone / give it to your dog...?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.18.0000
(bootloader) version-baseband: 11.15.3504.16_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.401.1
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3989mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 9d24123f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.494s
Standered htc sensation
I cant remember the original rom it came with but i have tried every shipped rom so far.
I used revolutionary to gain s-off and root it and was running miui and everything was fine for months then all of a sudden it restarted into bootloop :-( this was in december. Then i cant remember exactly wot i did but i lost recovery so was unable to flash new rom like that so i decided to flash a shipped rom.
The ruu failed so i put s-on and retried but it still failed. Then i noticed the new bootloader unlocker had just came out so unlocked it but soon relocked it.
This has now left me with a relocked bootloader s-on and no recovery at all.
I am on hboot 1.18.0000 so cant do advanced fastboot commands,
Cant use adb on it only fastboot so i think i maybe SCREWED!!!
Anymore info mate???
Thanks in advanced for trying mate
Hello,
While trying to install a RUU to send back my phone I got an error about my bootloader version.
Then I can't boot on my phone, I can't access recovery and the hboot and back to S-ON.
The only thing that is working is fastboot.
I tried to unlock the bootloader to be able to install a recovery again but I get a "Command Error" when I execute "fastboot oem get_identifier_token".
After trying a LOT of tutorials I have no clue what to do to get my phone back on.
Do you have any advices ?
Thanks a lot !!
masev said:
Hello,
While trying to install a RUU to send back my phone I got an error about my bootloader version.
Then I can't boot on my phone, I can't access recovery and the hboot and back to S-ON.
The only thing that is working is fastboot.
I tried to unlock the bootloader to be able to install a recovery again but I get a "Command Error" when I execute "fastboot oem get_identifier_token".
After trying a LOT of tutorials I have no clue what to do to get my phone back on.
Do you have any advices ?
Thanks a lot !!
Click to expand...
Click to collapse
Given that this has been covered many times, you would be better off listing EXACTLY what you have tried and the results you get so that people can have a better chance to help you. However, the answers are all out there and you simply need to read and make sure that you understand what you are doing and why.
I did read a lot of answers, with no success.
I exactly have the following symptoms :
When I boot my phone, I'm redirected to hboot with a security warning. If I go to recovery I get a sign from the phone that seems to say that no recovery is install.
I tried the following :
Try to install another RUU -> I still get error 140 about bootloader version
Tried a lot of different tutorials to install a rom / recovery but I understood that my bootloader is locked and thus need to unlock it. I tried HTCDev method to unlock it but I can't get my identifier_token, I guess this is because my phone is S-ON ?
Fastboot recognize my device (He give my the S/N) but I can't do other commands ...
I suppose that if I could get command from fastboot working again I could extract the recovery_signed.img from the RUU and installed the RUU again with success ...
Thank a lot for your help !
masev said:
I did read a lot of answers, with no success.
I exactly have the following symptoms :
When I boot my phone, I'm redirected to hboot with a security warning. If I go to recovery I get a sign from the phone that seems to say that no recovery is install.
I tried the following :
Try to install another RUU -> I still get error 140 about bootloader version
Tried a lot of different tutorials to install a rom / recovery but I understood that my bootloader is locked and thus need to unlock it. I tried HTCDev method to unlock it but I can't get my identifier_token, I guess this is because my phone is S-ON ?
Fastboot recognize my device (He give my the S/N) but I can't do other commands ...
I suppose that if I could get command from fastboot working again I could extract the recovery_signed.img from the RUU and installed the RUU again with success ...
Thank a lot for your help !
Click to expand...
Click to collapse
Have a look at these threads (found by searching for "Error 140" in the Desire S forums (and check out the stickies as well;-
http://forum.xda-developers.com/showthread.php?t=1870413&highlight=error+140
http://forum.xda-developers.com/showthread.php?t=1609169&highlight=error+140
SimonTS said:
Have a look at these threads (found by searching for "Error 140" in the Desire S forums (and check out the stickies as well;-
http://forum.xda-developers.com/showthread.php?t=1870413&highlight=error+140
http://forum.xda-developers.com/showthread.php?t=1609169&highlight=error+140
Click to expand...
Click to collapse
I already went through these ones, but it didn't help in my case : I found the RUU corresponding to my branding phone so I won't need a golden card and thus I can't install a different RUU.
For information are here my current variables :
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.16_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.49.1020.1
(bootloader) serialno: SH14RTJ05119
(bootloader) imei: 355067046626883
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: BOUYG201
(bootloader) battery-status: good
(bootloader) battery-voltage: 4147mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
And I am trying to install the RUU : RUU_Saga_Bouygues_FR_1.31.1020.1_Radio_20.28c.30.0805U_38.03.02.16_M_release_178948_signed.exe
Do you see any other path that I should follow ?
Thanks
masev said:
I already went through these ones, but it didn't help in my case : I found the RUU corresponding to my branding phone so I won't need a golden card and thus I can't install a different RUU.
For information are here my current variables :
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.16_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.49.1020.1
(bootloader) serialno: SH14RTJ05119
(bootloader) imei: 355067046626883
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: BOUYG201
(bootloader) battery-status: good
(bootloader) battery-voltage: 4147mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
And I am trying to install the RUU : RUU_Saga_Bouygues_FR_1.31.1020.1_Radio_20.28c.30.0805U_38.03.02.16_M_release_178948_signed.exe
Do you see any other path that I should follow ?
Thanks
Click to expand...
Click to collapse
RUU to a higher version.
Had the same problem with a branded phone. Problem is - you need a higher RUU. In my case there was no higher branded RUU.
I've made a gold card and flashed a unbranded higher RUU (latest ICS), and that makes the phone work again.
But without HTC-dev unlock we now can't get root! So if you can't find a higher RUU with your brand you may can't bring it to service with the new unbranded software on it.
Gesendet von meinem HTC Desire S mit Tapatalk 2
Hi everyone.
I'm trying to get back on stock (S4), but I can't find any RUU that matches my hboot and radio.
this is the result of fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4005mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I tried several S4 RUUs, european ones gave me error 131, Vodafone UK gave error 155 (the cellphone was bought in Italy).
What I did before executing the RUU exe(s) was just locking the bootloader. I think that probably installing ROMs in the time (the cellphone belongs to a friend of mine, so I don't know what was installed before) may have somewhat changed hboot (and/or radio) version, and now I can't find a RUU matching mine. Now i can only access the bootloader (I think the previous custom recovery is gone). I managed to access recovery by unlocking again the bootloader, but I can't mount any partition from the recovery (which is the main problem that lead me to decide to get back to stock.
What are my chances to return to HTC stock?
I have the same problem
Hi mate, I'm italian too. I suggest you to get S-Off (it's easy enough now with the brand new tools), change cid with fastboot command to HTC__001 and flash latest JB 4.1 european RUU. It's pretty easy
addsfsds said:
Hi mate, I'm italian too. I suggest you to get S-Off (it's easy enough now with the brand new tools), change cid with fastboot command to HTC__001 and flash latest JB 4.1 european RUU. It's pretty easy
Click to expand...
Click to collapse
I am very new to htc rooting and other stuff. kindly provide stepwise procedure with links to the tools and appropriate RUU
I have tried hit & trial but i am unable to get to stock
hasanalikhattak said:
I am very new to htc rooting and other stuff. kindly provide stepwise procedure with links to the tools and appropriate RUU
I have tried hit & trial but i am unable to get to stock
Click to expand...
Click to collapse
Dude give a quick look around, all the guides are here! or come to androidiani.com to get italian translated guides and support!
Dear all,
I tried to restore my phone to stock rom (for stability reasons)
however I tried RUU rom 3.18.502.6
Phone is Telstra Australia HTC one XL
now it goes into bootloop displaying HTC quietly brilliant logo then reboots and displays the same thing.
i can get into fastboot
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.14.0000
(bootloader) version-baseband: 0.24p.32.09.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.18.502.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8312000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3679mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97c9a06e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
Any help would be much appreciated!!
Thank you
First thing you need to do is edit the IMEI out of your post, never post that publicly. Is there a reason you're using an at&t RUU? If you really want to return the device to stock you should use a Telstra RUU. The at&t RUU will work because you have s-off, but it isn't technically stock (plus tethering won't work on an at&t ROM). Have you tried running the RUU a second time?
Transmitted via Bacon
Good idea. Thanks! I have tried ruu with that file multiple times. I used it before people have said it is compatible with super cid and S-off
Is if worth trying another ruu?
Would it be compatible?
I just want a stock HTC rom as this is now my backup phone. Will just use it to stream music.
Cheers!
Because you're s-off you can use any Evita RUU.
http://androidruu.com/?developer=Evita
Transmitted via Bacon
hmm. Tried updating to HTC_One_X_RUU_5.18.502.1.exe
still no dice.
STill boot looping
then tried flashing the latest TWRP via fastboot.
can't even get into recovery. just reboots.
Any other ideas?
Many thanks!!
tzuyang said:
hmm. Tried updating to HTC_One_X_RUU_5.18.502.1.exe
still no dice.
STill boot looping
then tried flashing the latest TWRP via fastboot.
can't even get into recovery. just reboots.
Any other ideas?
Many thanks!!
Click to expand...
Click to collapse
also tried clear storage and factory reset. these just result in system rebooting.......
Hi everyone,
I have a strange problem, My phone does not boot to recovery or bootloader, charging led does not turn on. This has happened after I flashed my phone with official rom.zip extracted from RUU (CID: HTC__J15; MID: PJ8311000); first time it flashed and showed error 90 (you have to reflash again), i waited fir htc logo to come back but it didn't and it is now stuck as I mentioned above.
My phone shows as fastboot device but rather weird s/n (??t fastboot) where ? is strange symbol.
Here is fastboot getvar all output: (screenshot attached)
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.14.0002
(bootloader) version-baseband:
(bootloader) version-cpld:
(bootloader) version-microp:
(bootloader) version-main: ��
(bootloader) version-misc: UNKNOWN
(bootloader) serialno: t
(bootloader) imei: 355195000000010
(bootloader) product: P
(bootloader) platform: HBOOT-8960
(bootloader) modelid: T��T� �� �$��$��/
(bootloader) cidnum: �*�
(bootloader) battery-status: good
(bootloader) battery-voltage: 3592mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: 1a7fdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
My phone was S-OFF, the problem now is I can't flash anything cuz my bootloader is locked and when I tried to unlock it from HTCDEV website it gives me error 150; wrong token or something like that.
Also when I try flashing anything like boot.img or rom.zip I get FAILED (remote: not allowed), attached screenshot
Does anyone know something about this? any help is appreciated.
Phone stuck in fastboot
The info in this reply is added to the main thread
Which RUU did you extract the ROM zip from? As far as I know there aren't any RUU's for your model (Evita_utl).
Transmitted via Bacon
timmaaa said:
Which RUU did you extract the ROM zip from? As far as I know there aren't any RUU's for your model (Evita_utl).
Transmitted via Bacon
Click to expand...
Click to collapse
I downloaded it from http://www.androidruu.com/?developer=Evita, the one starting with "RUU_EVITA_UL_ICS_40_S_HTC_ARA_2.40.415.1"
That RUU isn't for your device, it's not compatible. You've most likely borked your partitions. There isn't really anything you can do now apart from trying to find the stock firmware for your variant (the Evita_utl, not the Evita_ul) to fix your partitions, this will be difficult as I don't think your stock firmware is even available.
timmaaa said:
That RUU isn't for your device, it's not compatible. You've most likely borked your partitions. There isn't really anything you can do now apart from trying to find the stock firmware for your variant (the Evita_utl, not the Evita_ul) to fix your partitions, this will be difficult as I don't think your stock firmware is even available.
Click to expand...
Click to collapse
Thanks for replying. Does it have a different partition layout than the other One XL devices? isn't all of them supposed to have the same partitions? And I had S-OFF so it should not matter what version I flashed as far as I know -correct me if I'm wrong-