yashsingh1/xdaforums huggingface dataset:
[HTC One S] romansvillage:
Oh wow... Even Ubuntu does that s**t now... Localizing standard folders. Well... good to know.
[HTC One S] ernestnwanu:
So I got a bit further. I'm stuck " waiting device /dev/sdc12........". I tried resetting (holding power until QDL disappears, it does and comes back) but nothing happens. What can I do? It's the part where you flash the hboot. Thanks
[HTC One S] romansvillage:
Oh... that's the same point I am at... QDL dissappears for about 5 to 10 seconds and comes back...

In that time i can't flash the hboot... I could flash backp4 though so my phone is usable, but no downgraded hboot :(

Hope anyone has an idea how to leave QDL mode at least as long as it takes to flash hboot....
[HTC One S] ernestnwanu:
How exactly did you flash it back? Just in case.. This sucks, I came so far.
[HTC One S] romansvillage:
I executed step 12 "sudo ./emmc_recover -f ./bakp4 -d /dev/sdc4 -c 24576" and went forward until it said waiting for device. Then I held the power button until QDL mode dissapeared, released the power button and bakp4 (make sure it's the one backuped from phone or the one from the ZIP but with modified IMEI) flashed in less than a second (before the phone went back into QDL mode...). Again hold down the power button and phone boots normally.
[HTC One S] ernestnwanu:
It's writing! I made an error, typed sdc instead of sdb. Didn't actually replace it while copying the command from OP

EDIT: nevermind. It doesn't give it the time to write :(... keeps switching mode all the time. Why is this?

---------- Post added at 11:53 PM ---------- Previous post was at 11:12 PM ----------

Thanks, please check your PM

EDIT: Nevermind, everything is restored. It's a shame though.
[HTC One S] hellforgedheart:
Did you get it to switch out of QDL somehow? or was it spamming QDL to watch -n 1 lsusb like mine?
[HTC One S] ernestnwanu:
It remained on qdl mode so I restored everything starting from step 10
[HTC One S] ZzB3B0zZ:
Video walkthrough will be flawless to do this, anyone?
[HTC One S] Sneakyghost:
Not first. I talked about it a lot a few pages back.

There's reasons not to go with 1.06.

sent from a phone
[HTC One S] jujusito:
With 1.09 cant flash radio
[HTC One S] Sneakyghost:
Are you sure? I was under the impression that radio still works on 1.09, but didn't test that though.

There also is a 1.08 hboot available. I can post that later if anyone wants to test that. It might be faster and more stable but still allow for radio flash...

sent from a phone
[HTC One S] jujusito:
Yes, i sure

Enviado desde mi HTC One S

---------- Post added at 10:23 AM ---------- Previous post was at 10:18 AM ----------

I have hboot 1.06 and dont have Any problems, also flash boot.img at same time that rom. I dont need to flash boot.img with fastboot.

1.06 recomended
[HTC One S] cat2115:
Idea of 1.09 hboot gotten from Sneakyghost and extract hboot guide from AKToronto

I flashed hboot 1.09 works fine. I pull it off t-mobile RUU 1.84 and then follow OP guide.

Odd for 1.09 was after step 12 completed

, charging never come back on. I had to re-do from step 5 to 9. Re-flashing hboot then charging light come on.

For experimental:

Last night I went to stock, oem lock and flash RUU 2.35 t-mobile then grab 1.06 from t-mobile RUU 1.53

Same result as 1.09 above

=============

I remember when flashing hboot the very first time and using hboot from OP ville folder, i did not encounter the above issue. I flashed 2 phones and everything work smoothly but when using hboot from extracted RUU, i start to have charging light as mentioned above.

Maybe hboot from OP is different from my extracted RUU? Only OP can answer but seem like OP might be very busy and haven't seem OP reply to any of this issues.
[HTC One S] fmedrano1977:
I originally had 2.35 ruu installed on my device. I went through the process and when it came to restoring bakp4 file, my phone would not connect. Had to reset UBUNTU and was able to continue. After restoring bakp4, I did not get the charging light either, so started again from step 3 and and I think it was after flashing hboot, the second time, that my charging light came back on.

Tmobile HTC One™ S
[HTC One S] ernestnwanu:
Any alternate ways of downgrading to hboot 1.06? It seems some of us are unable to write the hboot because the QDL mode thingy keeps switching no matter what. What can be done? I'm glad I could restore the bakp4 but I'd still like to try this again. Hboot 1.13 is terrible. Escpecially since I come from a phone with a live community, so I'm kind of a flashaholic lol.
[HTC One S] 2rz_taco_sr5:
dont be skeered

I just did my replacement from tmo with the newest ota 2.35 and hboot 1.14005 and everything went great. I used a fresh install of 12.04 on a spare laptop and entered every command exactly as it said. watch out for reading the wrong line or accidentally switching to a different line of code half way through entering! I almost did that and decided to move the entered code out of the page as I entered it by scrolling down to hide it and avoid mistakes. also enter everything exactly as seen so if one letter is caps and another isn't enter it that way. my phone went back to qdl mode constantly even when I was originally typing the enumerating code over and over. I did it a million times then noticed I was in qdl again but no problem I just held power 10+ seconds again until it went away on the first terminal and then the next time I typed the code in the second terminal it worked. had to hold power down about 10-15 times through the hboot flash process but ONLY whenever it hung up but that's OK. last suggestion is don't switch terminals until told to! keep using the same one until told to switch there is a reason for it and certain code goes in certain windows! all in all was very quick and easy hboot took 10-20 ish mins to flash.
[HTC One S] romansvillage:
Well... Now it works... I had to do a manual reset at the very first chunk... After in ran through just fine with 2 other manual resets... I don know what I was thinking yesterday... Sometimes a fresh day with a fresh mind works wonders ;)
[HTC One S] cat2115:
After step 12 completed, is your charger light come back on? For me no. I had to reflash hboot again then once it's flashed half way, it stop and charger light come back.
[HTC One S] ernestnwanu:
This did it for me. Hboot 1.06 at last. Thanks everyone, especially OP.
[HTC One S] fmedrano1977:
Nope, just this.

Tmobile HTC One™ S
[HTC One S] :
HTC Warranty

I just called today about replacing my phone, they were very quick to tell me that by flashing any roms to my phone voids the warranty. Which is fine, I vented about S-OFF and how that would have made what I did unnecessary, but they don't care one bit. I found mobiletechvideos.com they seem to have a JTAG service for the ONE S, it seems like my only option at this point. In hind sight I think I should of just gotten the Nexus 4. I swore to myself after I got the Nexus S that I would never get a non Nexus device. HTC just isn't really supporting its development community like you see with any Nexus device. But I have to say that even without that support from HTC, the developers have done some amazing work.
[HTC One S] smokin901:
that is why some people call it Hell Telephone Company.
[HTC One S] muayyadf1:
Dude, it is your fault not HTC's. They sell production products for all customers not only developers. Plus, it is clearly stated by unlocking the bootloader you warranty gets an automatic void. At that point, you are responsible of anything happens. Not even a single developer gives warranty for his/her rom/hack/recovery/etc, they all say use on your own risk.
[HTC One S] :
I never said it was HTC's fault, its exactly the opposite. I also didn't say I was asking for any warranty support from any developers or anyone else. Actually I'm pretty sure I mentioned that I was going to send in my phone somewhere else to pay to have it fixed anyway.
[HTC One S] 2rz_taco_sr5:
Yes came right on when it was supposed to. Maybe a piece of code didn't flash half way through but everything else kept going so until the second time around when you flashed that spot again it probably wouldn't work. I'm no expert just an idea though. All sorts of little things can come up that you would never think of lol I just wanted to post up mine went fine though since I've got a new phone with the newest software (for tmo us atleast) and the process still works fine.
[HTC One S] cat2115:
I reinstall ubuntu 12.1 and updated. So i use notepad to copy all the code in here and rename to my sd* so i don't need to change when copy&paste to terminal. I use t-mobile 1.09 hboot.img and rename to hboot109.nb0 and place in ville folder. When I start doing the flash, everything went perfectly. Charging light went on right after step 12 completed.

Just to be organized and prepared, i think those who want to flash perfectly should copy all the code in notepad then find out what's their phone /dev/sd* are, edited in notepad and I also change hboot.nb0 to hboot109.nbo just so i know i'm flashing 1.09. Then start your flashing. Just some idea.
[HTC One S] adolfo778:
just downgraded very easy steps to follow at first look this looked almost impossible lol but as I did it the process became simpler

glad to have working wifi :D
[HTC One S] District:
Running Linux Mint 14 on my desktop. HTC ONE S connected via a HTC OEM micro-usb cable directly to the desktop (no hub).

Successfully downgraded from Hboot 1.14.0004 to 1.09.

Big thanks to Absolutelygrim and Yarrimapirate for the instructions, Sneakyghost for the HBOOT archive, and all the commentors in this thread.

Process took about 30 minutes total. The majority of that time was spent in step 9.

In step 9 and step 12, I stalled at "Waiting for /dev/sd*" at the initial execution, and never again.

After downgrading HBOOT, I successfully flashed the Wifi Partitions and on the following reboot Trickdroid 9.1.0 (Jelly Bean 4.1, Sense4+) connected to Wifi immediately :)
[HTC One S] Hachi_Roku:
Just wanted to say that I downgraded a Telus HTC One S with this method from 1.13 to 1.06. At the end of the procedure the charging light did not come on at all. As soon as I pressed the power button the phone booted up without a hitch! I also managed to change my CID :).

I had the problem where QDL mode kept switching back on automatically, all I had to do was constantly press and release power until Hboot flashed. Hopefully, flashing a new radio will fix this crappy reception.

Thank you OP for a great tutorial
[HTC One S] jac10000:
Thank's for the trick, but brings to what hboot1.09 rather than 1.06 ? More compatibility ?
[HTC One S] cat2115:
1.09 can flash any ROMs as 1.06. The reason I pick 1.09 over 1.06 because my experience w/1.06 wasn't as good as 1.09. But you can use 1.06 or 1.09 and decide it yourself.
[HTC One S] jac10000:
ok thank's
[HTC One S] :
last step gives me error

Resetting Device

Cannot Reset device

---------- Post added at 04:07 PM ---------- Previous post was at 03:48 PM ----------

Please help me guys ... :( :'(
[HTC One S] plocri:
yes I did, and flashed stock recovery too! I was able to install 2.31 ruu and wifi still doesn't work, now I've paid filefactory and i'm downloading the 2.38 vodafone ruu, hope it helps!
[HTC One S] sherry478:
does that mean i am bricked more than i already am? :/
[HTC One S] :
Your hboot didn't finish flashing. You need to start over from step 1. Follow it precisely.
[HTC One S] sherry478:
i cant see my device in qdl mode and when i try ls /dev/sd* i see /dev/sda /dev/sda1 /dev/sda2

does that mean there is someway i can restore my device?
[HTC One S] :
Do you see QDL mode or Qualcomm inc when you type lsusb ? Try to run

sudo ./emmc_recover -r

If it doesnt change from QDL mode to Qualcomm inc or Qualcomm inc to QDL mode, reboot your computer
[HTC One S] sherry478:
restarted my computer i found QDL mode. Redid all the steps BUT this time different error flashing the hboot:

ubuntu@ubuntu:~$ cd Desktop/ville
ubuntu@ubuntu:~/Desktop/ville$ chmod +x emmc_recover
ubuntu@ubuntu:~/Desktop/ville$ sudo ./emmc_recover -f ./hboot.nb0 -d /dev/sdb12 -c 24576
================= emmc_recover 0.3 alpha 2 ==========================

Using chunksize 24576
Messing up with device /dev/sdb12, ARE YOU SURE?
CTRL+C if not, ENTER to continue

Ok, ready to flash
Filesize:	1047808
Chunksize is:	24576
Cycle count is: 43.135417
Press ENTER if everything is correct, CTRL+C if not

Ready to write 24576 bytes
Resetting device
Cannot reset device
Reset command sent
Waiting device /dev/sdb12.......
Found device!
Writing 24576 bytes to offset 0x00000000
Waiting mode-switch
Device changed mode
Detected mode-switch
Ready to write 24576 bytes
Resetting device
Reset command sent
Waiting device /dev/sdb12.......
Found device!
Writing 24576 bytes to offset 0x00006000
Waiting mode-switch
Device changed mode
Detected mode-switch
Ready to write 24576 bytes
Resetting device
Reset command sent
Waiting device /dev/sdb12.......
Found device!
Writing 24576 bytes to offset 0x0000C000
Waiting mode-switch
Device changed mode
Detected mode-switch
Ready to write 24576 bytes
Resetting device
Reset command sent
Waiting device /dev/sdb12.......
Found device!
Writing 24576 bytes to offset 0x00012000
Waiting mode-switch
Device changed mode
Detected mode-switch
Ready to write 24576 bytes
Resetting device
Reset command sent
Waiting device /dev/sdb12.......
Found device!
Writing 24576 bytes to offset 0x00018000
Waiting mode-switch
Device changed mode
Detected mode-switch
Ready to write 24576 bytes
Resetting device
Reset command sent
Waiting device /dev/sdb12.......
Found device!
Writing 24576 bytes to offset 0x0001E000
Waiting mode-switch
Device changed mode
Detected mode-switch
Ready to write 24576 bytes
Resetting device
Reset command sent
Waiting device /dev/sdb12.......
Found device!
FATAL: Failed to open /dev/sdb12

---------- Post added at 05:57 PM ---------- Previous post was at 05:29 PM ----------

thank you finaly after 3 attempts my hboot finally flashes and my phone is downgraded and working!!!!!!
[HTC One S] leezer3:
I'd be far more interested in the relative kernel versions and distro applied patches TBQH.

From a quick repos glance, it looks like Arch is on 3.6 wheras Mint is still on 3.2.

There's also always the possibility that Arch has decided to drop the QDL driver from a default kernel compile, but I'm not commenting on that possibility.

IMHO if you roll a fresh copy of mainline on Arch with the QDL driver enabled in the config, it'll probably work just fine. This is too low-level for anything other than disabled driver in the config, or a bug of some description to be affecting it :)
[HTC One S] :
please, tell me I am wrong for downgrade hboot, mi htc one s is s-on, has hboot 1.14.002 and I would like downgrade hboot, follow your steps,

and flash RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L with error 155, mmcblk0p23 Okay so....

or is so
[HTC One S] plocri:
it's the first one, I did it, ruu recognizes 1.00 version but I failed to downgrade, always 155 error with right cid and supercid
[HTC One S] mikeyinid:
So, the downside to this is that you won't be able to run any RUU, I've tried all 3 tmo versions and all fail at certificate. Not good.
[HTC One S] :
Have you tried changing your CID back to normal in p4?

For AT&T we have a CID stored in p23 and p4.. P4 has superCID and p23 has CWS__001 (AT&T CID)
[HTC One S] mikeyinid:
anyone happen to know what the tmo cid is?

---------- Post added at 06:46 PM ---------- Previous post was at 06:19 PM ----------

nevermind, ruu ran fine. usually helps if you lock your bootloader first :cool:
[HTC One S] dc211:
T-MOB010 in case you need it in the future.
[HTC One S] mikeyinid:
tmo 1.53 ran fine with scid, but thank you
[HTC One S] vietlong3:
5. Reboot your phone. The charging light will no longer be on, and you should be stuck on a black screen.

Enumerating your partitions

my phone can not open, can you help me.

---------- Post added at 10:37 AM ---------- Previous post was at 10:23 AM ----------

hello

after I finished this step,

5. Reboot your phone. The charging light will no longer be on, and you should be stuck on a black screen.

my phone started off, not charging lights as a guide, but do more the next step is not possible, my phone is currently disabled and can not boot up.
[HTC One S] :
I told you what to do already.

Plug your phone in, open a terminal window and type lsusb

Tell me if you see Qualcomm, Inc. or Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
[HTC One S] vietlong3:
now have a way that look up Phone the me no?

Phone of the toi la T-MobileUS, or have a way that again fastboot non?

and on the PC 1 driver cannot installed.
[HTC One S] :
You have to install linux
[HTC One S] vietlong3:
On the PC 1 driver cannot installed.
[HTC One S] :
You have to be using Linux.
[HTC One S] fmedrano1977:
If using ubuntu, reboot it and try the last step again.

Tmobile HTC One™ S
[HTC One S] :
I repeated the whole process it worked In the second try .
[HTC One S] Sneakyghost:
Ok now its official. I killed my Device.

I downgraded a week or two ago and ever since, the 1.06 hboot had a graphic glitch where the line "fastboot usb" shows - it was only showing a diagonal half of the line once a cable got plugged in.

It had problems with waking up via power button and sometimes didn't wake up from a restart unless i used the power button.

I assume the hboot was defective.

this morning, after flashing Viper 2.0 JB final build for testing, it couldn't mount cache partition but then recovered. Then i was messing with /system rw permissions and remounting stuff. Then i rebooted and all i got was an orange LED and a black screen.

I then managed with a lot of patience and trying to get it into fastboot.

I then locked it and flashed the 1.53 RUU to restore a healthy hboot. All went well. No errors where shown.

Then the phone rebooted at the end of the process and didn't wake up anymore. Now, no LED and no screenbacklight. Just plain dead.

I hooked it up to Ubuntu and saw the Qualcom Gobi Wireless modem was still there and the power button also still triggered a reset.

however, the partitions cannot be listed anymore.

I took a guess and chose the partition i knew it was having last time. But no way. EMMC_Recover just sits there waiting for the device as the flash chip obviously doesn't allow any access anymore.

Anyone got an idea? I guess i will have to send it in, right? Or is there another way i can force a new hboot down the throat of this picky beast?
[HTC One S] jac10000:
Can you restart on bootloader ? If yes, have you try to flash a more recent ruu ?
[HTC One S] theguitarman94:
Hey sneakyghost that's not good to hear. Unfortunately this happened to me very early on in the process. I only got my partitions to list once and then they never showed up again. I knew what I was doing I'm not a noob and people need to realise that it's not the safest method of doing things even if you know what you are doing. I think what's happened is that the partitions have become corrupt and we can no longer write to them therefore rendering the phone a complete brick. It sucks and HTC won't repair mine because of water damage! Even though it was bricked lol

---------- Post added at 07:15 PM ---------- Previous post was at 07:13 PM ----------

I've tried the Jewel evita kit many times and I've re tried this tutorial about 50 times (no exaggeration) No matter what people suggest you won't be able to recover it. It's dead
[HTC One S] Sneakyghost:
Yeah mate i am through with testing everything emmc_recover has on offer. Unfortunately it appears that Fusions is not really pushing development of this tool any further - if there is anything he can develop.

All i know by now is that the connection in QDL Mode is unstable and tears away easily. So there is plenty of room for corruption of the hboot and i bet this is gonna happen to quite a few, so i changed my mind and decided its not a good thing to do unless you know a cheap way to jtag the thing.

HTC is currently trying to avoid responsibility for the repair but argue with an unlocked bootloader, whereas my main concern still is the Helicoptering Issue and i want them to fix that first and maybe see if they can revive the brick alongside that repair. If thats not an option for them i found a dude in way up south who does this the jtag way. Cost 22 bucks which is not bad. Postage needs to be added though.

I found one very useful hint in the HTC Sensation World, where emmc_recover stemms from: One TUT writer said its vital to run the RUU with the hboot you just flashed to your device after you did, simply because - here its getting interesting - the device will become unstable more and more over time with a forcefully downgraded hboot and (i add this) eventually brick.

I believe that it is quite likely that exactly this happened. Although i noticed many of the instability symptoms already before i downgraded. My sample is jus flawed from factory. Its never been good. Never seen a worse Helicoptering/Home Button Issue either. Its a POS and i want a replacement because i got sold a bad piece. But its hard to convince a large company like HTC that they have screwed up.

Its easier for them to convince me that i have screwed up. This world is truly unfair...

[EDIT]

Absolutelygrim, I'd recommend to put a suggestion into your TUT on #1 to flash the hboot-corresponding RUU (1.53 EU in this case) after the downgrade as it appears on the Sensation this was strongly recommended too and might make it a safer thing. Before you do so, it would be good to collect some user experiences on this matter.
[HTC One S] theguitarman94:
I agree with everything you said and a J-tag seems to be the only option if HTC don't come round. They should repair the phone though because I'm pretty sure they have no way of telling if you've unlocked your bootloader because everything on the phone is dead.
[HTC One S] cat2115:
Knowing this I would not dare to do it again. I'm kewl w/1.09 now.. but sorry to hear u brick ur phone.
[HTC One S] :
I don't know about the one s, and I can't vouch for what I've heard in the one x forums, but apparently trying to downgrade the 2.14 hboot from JB ota perma pricks the phone.

I have also seen 2 cases where accepting an OTA with superCID permanently bricks the phone (one x as well)
[HTC One S] LibertyMonger:
Sneakyghost's experience sounds terrifying and really bad news, sorry to hear. I am sure it will petrify anyone who see's this thread and considers it. So, sneakyghost, did you downgrade from the 2.14 hboot? Or do the downgrade multiple times? Everything is great with both my 1.06 hboot I sure hope it remains this way. Thanks for all your work sneakyghost and thanks for sharing your experience bud.
[HTC One S] Darknites:
People have already downgraded from the JB Hboot with no issues. Also mine been working great too and I did it 2 months ago and downgraded from 1.14.
[HTC One S] danirebollo:
I made this tutorial for windows+linux (Ubuntu LiveUSB) from you source adding some info (related at bibliography). Please feel free to add to your tutorial if find something interesting: http://danirebollo.blogspot.com/2013/01/htc-one-s-unbrick-downgrade-hboot_17.html
[HTC One S] :
Unfortunately I'm not fluent in Spanish
[HTC One S] danirebollo:
oh :(

I think it may be well to add to this tutorial the idea of ​​a LiveUSB of Ubuntu and also the copy of nandroid inside Windows as well, I've had a problem with this because in the last step Ubuntu recognized the phone as "HTC" and could not copy the file, but from windows with adb i do.