Database Info

Have I bricked my Desire S? [SOLVED]

I believe I may have bricked my Desire S also.
I rooted my Desire S through the official HTC method. (I have since relocked)
I then attempted to flash a custom ROM.
The custom ROM (Reaper 2.2) got stuck in (what I believe to be a boot loop) so I attempted to revert to the backup I made - that failed.
I did manage to get CyanogenMod 7 working but with missing functionality
Now I could not get beyond the white HTC screen (or the Black screen with the circle/number pattern on Reaper)
My desire S originally was on Vodafone (Ireland)
Whem I try to load the error is:
SD Checking
Loading...[PG88DIAG.zip]
No image!
Loading...[PG88DIAG.nbh]
No image or wrong image!
Loding...[PG88IMG.zip]
No image!
Loading...[PG88IMG.nbh]
No image or wrong image!
My phone was on 2.3.5 and Sense 3.0
Other details I obtained:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.161.3
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei:xxxxxxxxxxxxxxx
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4195mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
I have spent hours upon hours trawling through forums, posts and guides but nothing has worked.
I have tried RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release_177977_signed.exe and got error [170]:device not detected and I have tried from the command line via fastboot....
I really need help here please.
OR is my Desire S totally bricked beyond repair

If you unlock with htcdev, you need to extract the boot.img from your desired ROM and flash manually through adb after flashing the ROM. I'm 99% sure this will solve your problem. And you'll have to do this each time you flash a new ROM, or backup.
if you s-off your phone rather than using htcdev, you would not suffer from this procedure.
Don't be afraid, there is no brick
Sent by my fingers to your head.

eyahl said:
If you unlock with htcdev, you need to extract the boot.img from your desired ROM and flash manually through adb after flashing the ROM. I'm 99% sure this will solve your problem. And you'll have to do this each time you flash a new ROM, or backup.
if you s-off your phone rather than using htcdev, you would not suffer from this procedure.
Don't be afraid, there is no brick
Sent by my fingers to your head.
Click to expand...
Click to collapse
this and bootloader need to be ****unlocked**** in order to boot custom rom, and ***re-locked*** when installing RUU

Thanks for the reply's guys.
I managed to get the RUU working this evening but the phone was still ***unlocked***... I got some error (didn't make note of it)
I will re-read both posts when I am not so tired and try the suggestions
Thanks again
(I will post my results)

Ok, now I think I really have messed it up
I tried to flash RUU to the phone and now I cant get recovery to mount the sd card.
Can anyone suggest which RUU I should be using as the RUU app told me I was using the wrong image
I am totally at my wits end....I cannot even go back to the CyanogenMod rom

GSR-James said:
Ok, now I think I really have messed it up
I tried to flash RUU to the phone and now I cant get recovery to mount the sd card.
Can anyone suggest which RUU I should be using as the RUU app told me I was using the wrong image
I am totally at my wits end....I cannot even go back to the CyanogenMod rom
Click to expand...
Click to collapse
Did you read what I wrote?? Do what I said or search forum about that if you need more information. It is definitely necessary, you won't succeed without flashing boot.img separately.
Sent by my fingers to your head.

I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?

GSR-James said:
I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?
Click to expand...
Click to collapse
Yes, that's what I meant
Sent by my fingers to your head.

GSR-James said:
I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?
Click to expand...
Click to collapse
YEs that sounds about right, although the full command is
Code:
fastboot flash boot boot.img

Thank you both for the reply's.
I will try this when I sober up in the morning

Now that I am sober I want to thank eyahl, nenad_l and ben_pyett for your input.
I managed to get the rom working last night (drunk and all as I was )
I am now running a MIUI rom
Baseband version: 20.4801.30.0822U_3822.10.08.04_M
I need to ask a couple more questions if I may?
The interface is not what I am used to and don't particularly like it. It reminds me of the UI I had on my old Galaxy I9000. Is this as a result of my kernel version?
Kernel version: [email protected]#1 Thur Oct 6 14:48:57 BST 2011
My understanding of what I have done by flashing the boot.img is that my kernel is that of the rom from where the boot.img was taken and the MIUI rom sits atop - is this correct?
So if I extract a boot.img from a different rom and then flash I will have a different kernel version and subsequently return my UI to (SENSE) that I'm more familiar to?
Sorry for the n00b questions but I am only learning about this at the moment
Thanks guys

No problem, and your understanding is not really correct, the UI is determined by the ROM not the boot image (which is ultimately the kernel), so to get sense back you need to flash a sense ROM like Endy
Every time you flash a new ROM simply flash the associated boot
You shouldn't flash a boot from one ROM under another, it's not mix and match, well that's not completely true.
Swyped form ym Dersie S unsig XAD Permuim

Thanks Ben.
I will look for the 'Endy' rom you suggested.
Ok, so I dl the zip, extract the boot.img, write it from cmd and then flash the rom like normal?
I find it very frustrating to find roms.....almost every time I select a rom to dl I'm redirected to a bad link or to a referral to another referral etc....
If anyone has a source for roms please post it!

Best source for roms is the development section here at desire s xda. Just look through the threads, you will find good quality and stable roms. Endy=endymion ROM
You can look to the index thread, additionally zac made a torrent thread where you can find torrents for the most used roms
Sent by my fingers to your head.

Thanks eyahl
I have dl Endy and will try it now.
I'll have a look where you suggested
Thanks

You must wipe your device (all partitions except sd) prior to each ROM flash
Swyped form ym Dersie S unsig XAD Permuim

Just want to thank everyone for helping me resolve my issue.
I now have an Endy rom sunning stable for the most part.
Can this thread be marked resolved?
Thanks again

GSR-James said:
Just want to thank everyone for helping me resolve my issue.
I now have an Endy rom sunning stable for the most part.
Can this thread be marked resolved?
Thanks again
Click to expand...
Click to collapse
You're welcome
Yes, you can mark the thread solved
Sent by my fingers to your head.

Is there a 'button' or a tool that I can use to mark as solved or does it have to be done by a mod...
or can I just do this:
SOLVED!!!

GSR-James said:
Is there a 'button' or a tool that I can use to mark as solved or does it have to be done by a mod...
or can I just do this:
SOLVED!!!
Click to expand...
Click to collapse
Go to your first post, click EDIT, then on the edit panel, click on ADVANCED and then modify the topic of your thread by adding [SOLVED] in front of it.
You're done.

Updated TWRP 2.7.0.0 for Ville

It worked great for me. I just tested it with a back up and restore from internal as well as an OTG cable.
http://teamw.in/project/twrp2

What rom you have?
I know that for some 4.2.2 rom is better to keep the modified twrp 2.6.1.0

Here you can find a modified version of the latest TWRP that works correctly on hboot 2.16, which have the data/media storage partition in the same system partition.

Yep, thank you! Works just fine for me.

I've installed Liberty ROM 6b and hboot is 2.16. which one is proper for my device?

mosi-comp said:
I've installed Liberty ROM 6b and hboot is 2.16. which one is proper for my device?
Click to expand...
Click to collapse
The version for hboot 2.16:
/data/media storage partition (HBOOT 2.16.0000 only)
twrp-2.7.0.5-ville-dm.img (9 MB)

pandolf84 said:
Here you can find a modified version of the latest TWRP that works correctly on hboot 2.16, which have the data/media storage partition in the same system partition.
Click to expand...
Click to collapse
There are a lot of issue with this recovery because since /sdcard is on /data/media and there is no symlink to /sdcard, than a lot of installer and aroma installer will fail during zip flashing...
also it would be nice if backup is done like 2.6.1.0 (accessible from sdcard/TWRP/backups)
and also it would be nice if the default directory points to /sdcard and not /

I'm having issues with mounting to usb with this version of twrp. It wont connect via ADB or as a storage device =/

Naiks20 said:
I'm having issues with mounting to usb with this version of twrp. It wont connect via ADB or as a storage device =/
Click to expand...
Click to collapse
Did you flash the correct version for your boot? Also note that no recovery for 2.16 will be able to mount as usb due to new partition layout which is not fat32 anymore. You can mount a usb otg or otherwise use adb sideload feature (google it). This is not the fault of the dev.
Sent from my KFAPWI using Tapatalk
---------- Post added at 10:14 PM ---------- Previous post was at 10:11 PM ----------
pandolf84 said:
Here you can find a modified version of the latest TWRP that works correctly on hboot 2.16, which have the data/media storage partition in the same system partition.
Click to expand...
Click to collapse
Your latest unofficial twrp is working great for me on the 2.16 hboot. Stable so far and when I reboot to system there are no multiple reboots or other issues.
Have you thought about posting the link in the htc one s development forum? A lot of folks who may be interested tend to view that subforum more than this one. Also I had a bit of trouble downloading the link. I had to tell my browser to download the target and had to rename to .img as it was originally trying to download and open as a webpage.
Sent from my KFAPWI using Tapatalk

This recovery works great also for me, but i'm not the developer of this mod.
I don't remember who have posted on xda forum the link of MDMower website.
Bye

T-Mobile HTC One S won't enter recovery
I flashed openrecovery-twrp-2.7.1.0-ville.img onto my t-mobile htc one s (i wish i knew the model number i think it may be the pj40100 or the z520e or both, the z520e pj40100 and i'm running hboot 2.15.0 with bootloader unlocked s-on After flashing i rebooted the bootloader and then tried to go into recovery but the phone just goes into a loop of failed system boot attemps and the white htc quietly brilliant screen just goes on and off over and over until i hold down the power button long enough to power down the phone Phone has a brand new battery that I used another phone to fully charge What could be the problem?

Maybe you have to delete twrp-folder from SD card and retry...

I flashed this to my One S T-Mobile but phone can't enter recovery
I flashed this to my One S T-Mobile but phone can't enter recovery and returns to white htc quietly brilliant screen going on and off

What's your flash command and steps....?

Unable to boot or enter recovery
fastboot flash recovery openrecovery-twrp-2.7.0.0-ville
foeti said:
What's your flash command and steps....?
Click to expand...
Click to collapse
---------- Post added at 07:52 PM ---------- Previous post was at 07:45 PM ----------
There's no sd card present and I tried clear storage from bootloader didn't help the phone doesn't boot to system or recovery i'm running mainver 3.14 installed via ruu hboot 2.15 I'm thinking i need to flash boot.img maybe i dunno
foeti said:
Maybe you have to delete twrp-folder from SD card and retry...
Click to expand...
Click to collapse

I've got exactly the same problem with my HTC ONE S ville. Cannot get TWRP 2.7.1.2 or any newer version to work, only bootloop. Just wanted to install cm11 on H-Boot 2.15 unlocked, S-OFF :crying::crying:

rifek4 said:
Use unofficial TWRP v2.8.5.5, -> LOOK HERE <-. From me recommend CyanogenMod 12 or other ROM's on this base (Candy5, Resurrection Remix, PAC-MAN)
Click to expand...
Click to collapse
Unfortunately no luck at all. The only Recovery I got to work is "openrecovery-twrp-2.6.3.0-ville-selinux.img" but this one is to old to flash new roms. I can flash CM10 with it, but it is also not booting. Here are the details of my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.17_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.77.111.5
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3870mV
(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
I send it to a specialist (someone with a Riff Box xD), because I bricked the bootloader (QHUSB_DLOAD). I got the phone back with unlocked super cid hboot 2.15. That are very good prerequisites, but as I said no Recovery works for me. No Philz, no offical or inoffical twrp. This device is the first one in my "carrier" that is really frustrating me...

First: Please delete your serial number and your imei. Just for your own safety.
And second: As your "fastboot getvar all" output states your phone is on hboot 1.09 and not 2.15. So that's the culprit for your problems.
Just flash a RUU that corresponds to your CID and update your phone to the latest firmware version using the OTA function of the stock rom. If you can't find a suitable RUU get S-OFF by flashing a Sense based rom and using either rumrunner or facepalm. After that you will be able to use every RUU you want. If you use facepalm just be careful not to install OTAs before you undo SuperCID or you will brick your phone.
P.S.: Maybe there's a faster method to solve your problems but that's actually what I would do.

Thank you for the advice, normally I delete those data but it was to late for thinking clearly xD
The vars I posted were the ones before I bricked the phone. I got it back with the values I described after that. But I was not able to update TWRP and in general not able to boot any ROM flashed with old TWRP. But after one week of pain I found this awesome Thread http://forum.xda-developers.com/showthread.php?t=2751518 the RUU updated the whole phone to Hboot 2.16 and suddenly I was able to install TWRP 2.8.5.5-ville and flash the special Hboot 2.16 version of cm11. I had to flash boot.img manually, because S-OFF was gone after RUU update, no big deal. I'm happy now =)

[q] not booting

My HTC One SV (LTE europe version ) stuck while booting, it displays white logo screen only,
now i unlocked bootloader and tried to flash rom, but failed,
How i can flash a custom rom or original oerating systedm in my phone,
please help me.

anpayy said:
My HTC One SV (LTE europe version ) stuck while booting, it displays white logo screen only,
now i unlocked bootloader and tried to flash rom, but failed,
How i can flash a custom rom or original oerating systedm in my phone,
please help me.
Click to expand...
Click to collapse
Can you get into the bootloader? If you can, you can flash TWRP recovery via fastboot and flash a custom Rom with the recovery.

Yes
thearif said:
Can you get into the bootloader? If you can, you can flash TWRP recovery via fastboot and flash a custom Rom with the recovery.
Click to expand...
Click to collapse
i can get into bootloder, but where can i get TWRP recovery and custom rom file ?

anpayy said:
i can get into bootloder, but where can i get TWRP recovery and custom rom file ?
Click to expand...
Click to collapse
Go to http://forum.xda-developers.com/showthread.php?t=2292432 . Read through and find the recovery there. It is pretty well explained there. I am on my mobile so I am not sure of the link will take you to the first page. It is on the first page. Make sure you get the correct recovery for your phone model.

Original rom
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???

anpayy said:
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
Click to expand...
Click to collapse
That I do not know, but if my memory serves me right, there was a thread either in android development or general sections with the latest OTAs. You might wanna search for that...

anpayy said:
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
Click to expand...
Click to collapse
You've already got the link to my index thread, but it seems you are to lazy to have a look at it. You even only need to watch for the software number and you will easily find what you are searching for.

Os intallation failed
i tried to install OTA update through TWRP recovery , but it failed

You can't flash this in recovery. Use TWRP recovery and flash the rom (not the Ota). Links are in my index thread.

Installed rom
Sucessfully instaled Viper SV rom,
but still phone did not booting,

Did you also flash boot.img of the rom in fastboot?

no
I missed to boot boot.img,
Now phone is working perfectly...........
Thanks all........specially old.splatterhand & thearif

Nice

anpayy said:
I missed to boot boot.img,
Now phone is working perfectly...........
Thanks all........specially old.splatterhand & thearif
Click to expand...
Click to collapse
Good to hear that...

Hi all,
I'm new in this forum so I post there.
My problems starts after try to updete htc one sv k2_ul. After update I get red triangle and then my phone freezed on white screen with logo.
Try to do factory reset from bootloader, but nothing happen. After few days looking information I unlock bootloader and try flash new boot, but after that I get Tampered. I found if I must s-off, but how I can get it? My pc found phone only on fastboot mode. Any ideas?

miegas said:
Hi all,
I'm new in this forum so I post there.
My problems starts after try to updete htc one sv k2_ul. After update I get red triangle and then my phone freezed on white screen with logo.
Try to do factory reset from bootloader, but nothing happen. After few days looking information I unlock bootloader and try flash new boot, but after that I get Tampered. I found if I must s-off, but how I can get it? My pc found phone only on fastboot mode. Any ideas?
Click to expand...
Click to collapse
You can't get S-off, without working OS.
You don't have an OS anymore on your phone?
Are you running a custom recovery like TWRP?
Run this fastboot cmd and copy the output here (remove your imei & serial number):
Code:
fastboot getvar all

old.splatterhand said:
You can't get S-off, without working OS.
You don't have an OS anymore on your phone?
Are you running a custom recovery like TWRP?
Run this fastboot cmd and copy the output here (remove your imei & serial number):
Code:
fastboot getvar all
Click to expand...
Click to collapse
My os just stop working.
I don't try TWRP, today will look more about that.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.15.40a.00.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4143mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.075s
edit
I flashed TWRP and I make restore, but phone won't start anyway. Maybe need to flash new os?

Flash the stock rom in TWRP, and don't forget to flash boot.img of the rom in fastboot.
Links are in my index thread.
Make a backup in recovery (just in case) and a wipe (advanced -> everything except int & ext sdcard) before.

old.splatterhand said:
Flash the stock rom in TWRP, and don't forget to flash boot.img of the rom in fastboot.
Links are in my index thread.
Make a backup in recovery (just in case) and a wipe (advanced -> everything except int & ext sdcard) before.
Click to expand...
Click to collapse
Something I make wrong. I flashed TWRP, then installed ViperSV, phone restarted and booted TWRP. Then I found boot.img in yours index thead.
Then in fastboot flashed new boot, but phone still booting in TWRP. What I make wrong?

You need to flash the boot.img thats inside the ViperSV.zip, not any from my index thread.

[Q] Bell HTC One S - S_ON, no nand, BL-Ulck, cm flashed, brick?

Hello All,
I have a Bell HTC One S that seems to be soft bricked and I would appreciate any help as I am either missing a key, or I am irreparably soft bricked (if that's a thing).
The story:
Unlocked the bootloader via htc-dev, flashed twrp-2.6.3.0-ville via fastboot, reboot to recovery, installed CM Rom. Now I cannot boot a rom.
This is because I didn't S-OFF, root or modify CID prior to attempting to flash custom rom. So, I tried re-lock and restore to factory but am getting nowhere.:
- "fastbootflash zip OTA_Ville_U_JB_45_S_BM_3.16.666.9_1.11.50.05.28_10.27.50.08L_release_308167.zip", results in the error "FAILED (remote: signature verify fail)".
- I cannot find an RUU.exe that's current enough for my version (3.16.666.10).
- Attempted to load "OTA_Ville_U_JB_45_S_BM_3.16.666.9_1.11.50.05.28_10.27.50.08L_release_308167.zip" via adb sideload from twrp and the get the error "assert failed: check_cid(getprop("ro.cid"). "00000000", "22222222", .... , 'BM___001" =='t'.
- Get same error "(... 'BM___001" =='t'...)" if attempt to install the zip from TWRP too.
#HBOOT Info.
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.20
OpenDSP-c31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
#Fastboot getvar all
version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.11.50.05.28
version-cpld: None
version-microp: None
version-main: 3.16.666.10
version-misc: PVT SHIP S-ON
serialno: ************
imei: ****************
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: BM___001
battery-status: good
battery-voltage: 4139mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
If anybody could guide me in the right direction, it would be greatly appreciated. Hopefully that direction isn't junking this phone.

... bump ...
There has to be an expert out there who can give me a hand with this phone...
anyone?
Am I not being descriptive enough?

Can you still boot to recovery or bootloader?

Fiabeschi said:
Can you still boot to recovery or bootloader?
Click to expand...
Click to collapse
Yes,
I can boot into both recovery and bootloader. I can load recoveries and can also access adb shell via TWRP. I just can't seem to load a factory rom back onto the device with adb or fastboot. If I could get the thing back to stock I would be happy so I could take another crack at it it, while rooting and using superCID prior to trying to flash a custom rom...
If I could somehow obtain s-off without needing the ability to boot up to a rom I would be alright too.
Thanks for the reply!

sockky said:
Yes,
I can boot into both recovery and bootloader. I can load recoveries and can also access adb shell via TWRP. I just can't seem to load a factory rom back onto the device with adb or fastboot. If I could get the thing back to stock I would be happy so I could take another crack at it it, while rooting and using superCID prior to trying to flash a custom rom...
If I could somehow obtain s-off without needing the ability to boot up to a rom I would be alright too.
Thanks for the reply!
Click to expand...
Click to collapse
That's a start, I suppose that you can recover things back. Still. I'm quite a noob, so I have difficulties in understanding what you've done after installing the ROM. I think the problem was that, since you're S-on (as me, and no superCID too), you should have installed via fastboot the kernel after flashing the ROM on TWRP. I did the same error the first time, having the phone stuck on the first HTC logo. Then I installed the kernel, and it was ok.
So, if the phone is still unlocked and everything, I'd give a try to wipe system,cache and dalvik, flash back the rom, reboot to fastboot, install the kernel and cross your finger... Only problem, I don't know if it will work and worse, if it can worsen your condition. (I don't think so.).

Well, as Fiabeschi already said, you should have flashed kernel (boot.img) after flashing the rom, that's why it won't boot. On the contrary, if you're s-off you don't need to flash kernel separately

Solved: flash boot.img
ZioRò and Fiabeschi,
Your responses were exactly what I was looking for.
- Even though S-ON and flashed a non-signed rom, all I just flashed boot.img from the zip of the rom (cm11 in this case) via fastboot -enabling access to working, rooted, rom.
- Needed S-OFF because Radio wouldn't work and "Rumrunner" did the trick.
- Flashed latest radio
- SIM Unlocked
Pretty dynamic paperweight now! Thank you both very much -I can't say I'm in love with HTC at this point though.
Sockky

sockky said:
ZioRò and Fiabeschi,
Your responses were exactly what I was looking for.
- Even though S-ON and flashed a non-signed rom, all I just flashed boot.img from the zip of the rom (cm11 in this case) via fastboot -enabling access to working, rooted, rom.
- Needed S-OFF because Radio wouldn't work and "Rumrunner" did the trick.
- Flashed latest radio
- SIM Unlocked
Pretty dynamic paperweight now! Thank you both very much -I can't say I'm in love with HTC at this point though.
Sockky
Click to expand...
Click to collapse
I'm glad to hear good news from you! Now enjoy your (reborn) HTC One S

Problem with Custom Roms

Hi there i tested these ROMS on mine HTC One S Ville S4 (International).
Here the Results:
Maximus 10.0.0 - http://forum.xda-developers.com/showthread.php?t=2445392
I´ve followed all steps but no luck, the phone reach splash screen and all i get is all 3 lights on the bottom and a green on the top illuminated.
LIBERTY ROM - The Sixth Element 4.4.2/4.4.3
Almost the same situation with Maximus Rom but with Black splash screen this time on the 2 versions of this Rom
At the moment i have the ViperOneS 3.2.0 but i would like test other Roms.
Here my specs:
----> Start <----
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.16.31501S.17_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: SH24PW******
(bootloader) imei: ***************
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3873mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.071s
----> End <----

you need a specific hboot to try the rom. i think is 2.15 and you have 1.13.. so..... i think that is the problem.

first of all you'd update all that is possible to lates ver. (hboot, recovery), may be you should try hboot 2.16 and roms for it...

grorg said:
first of all you'd update all that is possible to lates ver. (hboot, recovery), may be you should try hboot 2.16 and roms for it...
Click to expand...
Click to collapse
No luck with RUUs

vic_111 said:
No luck with RUUs
Click to expand...
Click to collapse
You will need to update HBOOT to version 2.15 or 2.16 depending on which rom you want to install. HTC__304 is Europe/Spain so the Europe RUU should be fine for you. Its pretty easy:
Download FIRMWARE HBOOT 2.15
Extract the included recovery and flash it using fastboot:
fastboot flash recovery recovery.img
Relock your bootloader (in case it's actually locked)
fastboot oem lock
Then flash the firmware215.zip:
fastboot oem rebootRUU
fastboot flash zip firmware215.zip
fastboot flash zip firmware215.zip (First time you probably get an error, so just retype the command!!!)
fastboot reboot-bootloader (to get back into bootloader mode)

LS.xD said:
You will need to update HBOOT to version 2.15 or 2.16 depending on which rom you want to install. HTC__304 is Europe/Spain so the Europe RUU should be fine for you. Its pretty easy:
Download FIRMWARE HBOOT 2.15
Extract the included recovery and flash it using fastboot:
fastboot flash recovery recovery.img
Relock your bootloader (in case it's actually locked)
fastboot oem lock
Then flash the firmware215.zip:
fastboot oem rebootRUU
fastboot flash zip firmware215.zip
fastboot flash zip firmware215.zip (First time you probably get an error, so just retype the command!!!)
fastboot reboot-bootloader (to get back into bootloader mode)
Click to expand...
Click to collapse
He's S-On, are you sure it'll work like this? Flashing firmware is not possible unless you're S-Off. He should first try to achieve S-Off via rumrunner or other method (since he's already using Viper or a close-to-stock ROM). Then he might try flashing 2.15/2.16 firmware

Rapier said:
He's S-On, are you sure it'll work like this? Flashing firmware is not possible unless you're S-Off. He should first try to achieve S-Off via rumrunner or other method (since he's already using Viper or a close-to-stock ROM). Then he might try flashing 2.15/2.16 firmware
Click to expand...
Click to collapse
I'm sure. Flashing "SIGNED" zips will totally work with S-ON.

LS.xD said:
I'm sure. Flashing "SIGNED" zips will totally work with S-ON.
Click to expand...
Click to collapse
I will give it a try , hope I don't get a brick
But I have two questions:
1What you mean "locked" I have my boot loader unlocked!
When I finish the flash process I can unlock again?
Sent from my HTC One S

vic_111 said:
I will give it a try , hope I don't get a brick
But I have two questions:
1What you mean "locked" I have my boot loader unlocked!
When I finish the flash process I can unlock again?
Sent from my HTC One S
Click to expand...
Click to collapse
You can unlock it at any time, but you will have to lock it before upgrade the firmware.

LS.xD said:
You can unlock it at any time, but you will have to lock it before upgrade the firmware.
Click to expand...
Click to collapse
No luck, upgraded sucessfully but now i have a blank screen blinking
Update: Should i update to 2.16? If yes where i can get it?
Update URGENT: I cant install any rom now help please
Update 2: I tried install 2.16 but unsucessfull
Update 3:Anyone can find a RUU for me , because i cant :crying:
Update 4: Well i am on ViperOneS again , somehow (flashed boot.img before aroma-installer),but i would like test Liberty one you think you can send me hboot 2.16 signed , i tried find but only for s-off
Update 5 [LAST ONE]: Finally i get it Liberty Rom works 100% thanks for all the help guys , REALLY!!!

vic_111 said:
No luck, upgraded sucessfully but now i have a blank screen blinking
Update: Should i update to 2.16? If yes where i can get it?
Update URGENT: I cant install any rom now help please
Update 2: I tried install 2.16 but unsucessfull
Update 3:Anyone can find a RUU for me , because i cant :crying:
Update 4: Well i am on ViperOneS again , somehow (flashed boot.img before aroma-installer),but i would like test Liberty one you think you can send me hboot 2.16 signed , i tried find but only for s-off
Click to expand...
Click to collapse
Update 5 [LAST ONE]: Finally i get it Liberty Rom works 100% thanks for all the help guys , REALLY!!!

vic_111 said:
No luck, upgraded sucessfully but now i have a blank screen blinking
Update: Should i update to 2.16? If yes where i can get it?
Update URGENT: I cant install any rom now help please
Update 2: I tried install 2.16 but unsucessfull
Update 3:Anyone can find a RUU for me , because i cant :crying:
Update 4: Well i am on ViperOneS again , somehow (flashed boot.img before aroma-installer),but i would like test Liberty one you think you can send me hboot 2.16 signed , i tried find but only for s-off
Update 5 [LAST ONE]: Finally i get it Liberty Rom works 100% thanks for all the help guys , REALLY!!!
Click to expand...
Click to collapse
I'm glad you finally made it. HBOOT 2.16 works with S-OFF only, thats why I uploaded 2.15. As @Rapier mentioned earlier, you can use rumrunner.us for easily getting S-OFF

Mind you that hboot 2.16 gives you shared internal storage. E.g. all free space is available to all partitions. This may come tot be necessary for you if flashing lollipop roms since the "foot print" of installed aps on lollipop becomes much larger. This has to do with runtime environment... Kitkat runs with Dalvik Cache whereas Lollipop runs with the Android Runtime aka ART.
So, staying on hboot 2.15 give you the old partition layout with approx. 1 GByte(??) free for apps and 7 as internal SD.
While hboot 2.16 serves all your free internal storage to all partitions. This saves you headache of internal space for apps running out.
(Someone may deel to fill in the technical gaps i left in)
Cheers , happy hboot 2.16 user.
Verstuurd vanaf mijn One S met Tapatalk