Database Info

No bootloader, rom or recovery s-on locked bootloader hboot 1.18.0000

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

[Q] Desire S crashed. Unable to recover - Pls help

Hi,
I had made my Desire S , S-off and rooted. I have cyanogenmod 7.1 running on my device. There was a slight problem with GPS to thought of making it to HTC rom. So used RUU to update it. But device crashed, when I try to start it gets stuck in white screen of htc. I came across this situation before, but I used RUU again then everything went fine, this time device is not at all detecting by RUU or adb. I tried most of the methods mentioned in XDA, but nothing help. Please guide me regarding this.
Here is the output of fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.1
(bootloader) serialno: <<>>
(bootloader) imei: <<>>
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4210mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.018s
My Hboot details:
-----AlphaRev-----
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.11_M
eMMC-boot
Mar 10 2011, 14:58:38
This is the thing which I able to get by any commands. Please help me regarding this issue.
Thanks,
Bhaswanth Gattineni.

II suggest that you edit your last post and remove both your imei code and the serial number
Swyped firm ym Desire S unsig XAD Permuim

Thanks ben_pyett ! I edited it.

I had the same issue. I think the problem lies within the version of hboot set to 6.xxxx. You should have installed the eng hboot right after the s-off, as they recommend here on xda.
I had the chance that a friend of mine works in a cell phone repair company, where they put my DS back to default.
You can still fastboot, so try to flash CM again, or locate the rom.zip file of the RUU. You can find it somewhere on your hard drive when running the RUU.
In the zip you will see boot.img, system.img and some other img files, flash them all.
fastboot flash system system.img, flashboot boot boot.img, and so on.
Good luck

@bhaswanth88
You sir need a goldcard I think (that cid isn't in the Europe RUU's) not sure about WWE ones.

If you have recovery.img back up, just find the Android Flasher program some where in xda, and flash your recovery by Flasher.
I've same problem before, I want to install a RUU files, but I don't check CID between my phone & ruu files.
Sent from my HTC Desire S using XDA

foX2delta said:
@bhaswanth88
You sir need a goldcard I think (that cid isn't in the Europe RUU's) not sure about WWE ones.
Click to expand...
Click to collapse
Too late for a gold card.
- flash a suitable HBOOT
- look for a suitable Stock recovery (there's one in the RUU)
- zip it along with the android-info.txt (using normal compression)
- rename it to PG88IMG.zip
- put it in the root of your card & boot into fastboot mode
- flash the file when the phone makes the request
- try the RUU again
- if it fails, create a PG88IMG.zip from either CWM or EXT4
- flash it the same way
- then flash a custom ROM
- from the custom ROM, you can create a gold card, use ADB commands, etc.

I think I should mention for future reference, the answer to all your problems is not a RUU. There is already a GPS fix in the development section
Sent from my Desire S using Tapatalk 2 Beta-4

[Q] Help Ruu'ing

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

how to fix this

Hi sorry for new post but i tried to search some info but it didint helped me. So at first i installed viper s rome (old one 4.1.X ) then i tried to install cyogen 11, but i think i accidentaly pushed out usb cable when i was transfering rom.zip file.
So i tried to flash cyogen rom but it failed. Then i tried to restore from recovery. It was successful, but then i stucked in boot loop (recovery mode).
So how can i go back to stock?

ErnestasC13c said:
Hi sorry for new post but i tried to search some info but it didint helped me. So at first i installed viper s rome (old one 4.1.X ) then i tried to install cyogen 11, but i think i accidentaly pushed out usb cable when i was transfering rom.zip file.
So i tried to flash cyogen rom but it failed. Then i tried to restore from recovery. It was successful, but then i stucked in boot loop (recovery mode).
So how can i go back to stock?
Click to expand...
Click to collapse
Some of this may help:
http://xda-university.com/as-a-user/how-to-recover-from-a-bootloop
http://forum.xda-developers.com/showthread.php?t=2678700

how to know which ruu is good for me? i bought my fone in england it was unlocked my radio is 1.11.50.05.28

ErnestasC13c said:
how to know which ruu is good for me? i bought my fone in england it was unlocked my radio is 1.11.50.05.28
Click to expand...
Click to collapse
You need your CID (Country ID), you can get it from the the boot screen:
Press and hold the VOLUME DOWN button, and then press and hold the POWER button.
Wait for the screen with the three Android images to appear, and then release the POWER and VOLUME DOWN buttons.
The CID is the 2nd line.
Write down the HBOOT and Radio versions too.

VLE PTV SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
all info i could get

So no CID on the screen above this?
What is the carrier? You can use an RUU that is equal or newer than what you have.
http://androidruu.com/?developer=Ville

so wich one should i pick?

ErnestasC13c said:
so wich one should i pick?
Click to expand...
Click to collapse
Try this to get your info:
http://forum.gsmhosting.com/vbb/f485/guide-how-get-cid-main-ver-bootloader-etc-1638931/

(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: SH23MW404445
(bootloader) imei: 359901045063217
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(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

OK so it seems that HTC__001 is HTC Europe. So you need any RUU that is same or newer with "HTC_Europe" in the RUU name.
So if you look here:
http://www.androidruu.com/?developer=Ville
This one has the exact same radio.... hopefully this is it!
http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe

808phone said:
OK so it seems that HTC__001 is HTC Europe. So you need any RUU that is same or newer with "HTC_Europe" in the RUU name.
So if you look here:
http://www.androidruu.com/?developer=Ville
This one has the exact same radio.... hopefully this is it!
http://www.androidruu.com/getdownlo...28_10.27.50.08L_release_301814_signed_2_4.exe
Click to expand...
Click to collapse
tried this one no luck

ErnestasC13c said:
tried this one no luck
Click to expand...
Click to collapse
What happened? Did it give an error? Did you relock the bootloader first?

Phone won't boot up

HI Guys
So my mate's phone won't boot up and I'd really appreciate some assistance. The last thing I did was unlock the phone via htcdev. But that's all I could do. Now I can't flash a recovery (I've tried a few) because I get an IMAGE UPDATE ERROR. I've also received a "SIGNATURE VERIFY FAIL" error.
Also, adb won't recognise my device but fastboot does.
What I'm trying to do is install a custom rom because my mate was complaining that his phone was slow and a bit laggy. I sold the phone to him in the first place so I've taken it upon myself to fix it.
Thanks guys, let me know if you need any further info.
CJ

First of all, we need some information about your phone.
I need : what kind(k2u, k2ul and so on)
Then what you have already done.
Then the other things (best of all you copy all information from your boot loader)
Edit: okay skript point 2 xD
Kreumadragon

Thanks for getting back to me.
Here's the information you've requested.
UNLOCKED
K2_ul PVT SHIP S-ON RL
HBOOT-2.21.0000
Radio-1.18.40a.00.05
openDSP-v13.2.0268.0620
OS-3.12.980.10
eMMC-boot 1024MB
Jul 2014
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.12.980.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT2BWTP01724
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8015000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.100s
Let me know if you need any further information.

With regards to what I have already done, I tried to flash TWRP recovery but I got an image update error.

Mhh do you flash the right TWRP?
And use fastboot flash recovery *recovery name*?
Do you have any data's to loose?
Kreumadragon

yeah I flashed a few different TWRPs and none of them worked.. if there is a specific one and if you have a link, I could try again?
nope i don't need any data to lose. I have removed the sd card. Thanks again.

Anyone? Still having no luck with this phone.

Please test (if you want) the cwm recovery. Link:
http://forum.xda-developers.com/showthread.php?p=37075457
If this doesn't work flash a ruu and try again
Kreumadragon

There is no RUU out which will work and also the cwm is outdated.
How did you flash recovery?
Use the one i recommended in my index thread. This should work on your hboot.

An other option is to get s off and flash it via pl**img.zip isn't it?
Kreumadragon

You need a working OS for S-off. Not sure if that is working here.

@Old
You have s off, haven't you?
And I get s off with hboot 2.21
Kreumadragon

I don't have One SV anymore.
Rumrunner works on hboot 2.21.

He says that he didn't have data's to loose
theoretically you can create an ........IMG.zip file with all files a ruu use, only the recovery is changed? Think I can make one but first want to read what you think(old)
Kreumadragon

As long as he is S-on you don't need to make anything.
Right now he can only flash signed firmware by HTC this way.

Okay, thx I don't know
Actually no ruu for any kind of k2ul?
Kreumadragon

Only one. And you must be S-off or on ICS to use that.

@CJ_
Do you have test old.s method?
If this doesn't work, you probably need SOff.
Kreumadragon

Hi old.splatterhand, to answer your question, I flashed the latest TWRP recovery (2.8. something) but I got the following IMAGE UPDATE ERROR. Will try the ones in your index and report back.
Thanks for your help guys.

Will try it now... If that doesn't work, how do I get S-Off when I can't do anything with the phone?