yashsingh1/xdaforums huggingface dataset:
[HTC One S] tylerjholmgren:
Help Please

Im not quite sure where I went wrong but when I try to flash hboot it wont reset and when I follow the steps to make it reset it still does the same thing everything is as it should be (qdl mode etc.) I also have all of these

/dev/sda /dev/sda2 /dev/sda5 /dev/sdb /dev/sdd /dev/sdd2

/dev/sda1 /dev/sda3 /dev/sda6 /dev/sdc /dev/sdd1 /dev/sde

when I did the commad "ls /dev/sd*" so which one do I choose for hboot and the for bakp4 when restoring?
[HTC One S] hicdub:
Cool. Thanks guys. I think I will try this later today.
[HTC One S] dc211:
None of those you didn't do it right yet. You need to see at least 36 of them.

Go to step 3

3. Now, hold power down on your phone for about 10 seconds*,OR until you see (QDL mode) disappear and let go, Then go to your second window and spam

So type in "ls /dev/sd* " and press enter. Then press up, then enter over and over while you are resetting the phone. Until your output changes. Look at the 2nd picture on the OP. He ran the command 7 times in a row before he got it. You need to do the same.
[HTC One S] tylerjholmgren:
Thank you so much you don't even know how grateful I am for your help you saved me from my own stupidity. Next time I need to read a little closer.
[HTC One S] dc211:
No problem, did you finish and get it all working?
[HTC One S] hicdub:
What do you mean by spam?
[HTC One S] dc211:
Do it repeatedly just like that quote says.
[HTC One S] hicdub:
Thanks for the quick reply. I just booted into Ubuntu from a live cd and I am doing this!

Wish me luck guys!

---------- Post added at 02:19 PM ---------- Previous post was at 01:46 PM ----------

I completed everything to step 12. It looks like it flashed successfully, but the charging light doesn't come on and the Qualcomm, Inc. Gobi Wireless Modem (QDL mode) is still listed. I'm not sure what do do next. Any ideas?
[HTC One S] dc211:
Step 13 :)
[HTC One S] hicdub:
This is pretty odd. I just flashed the hboot again and the light came on! I just rebooted to the bootloader... and it worked! Not sure how or why, but I'm stoked none the less!

Thanks again for the help guys. I'm off to test a rom flash without doing the fastboot method.
[HTC One S] encho:
It took me 3 times to flash hboot correctly, kept failing or freezing the usb port (computer restart helped). This is definitely not for the faint of heart. Finally got the phone back to life and hboot downgraded, thanks to everyone involved.
[HTC One S] mikeyinid:
Going into it blind and having a "brick" for 2 days was scary. Took one for the team though. Turned out to be a good thing.
[HTC One S] Olympus593:
Can it be done on a Mac (Mountain Lion) ?
[HTC One S] Darknites:
Have you tried rebooting the pc?
[HTC One S] LibertyMonger:
I am kind of confused, I have done this a few times already but this time I did a few things wrong or out of order.

First, I unlocked my phone and installed TWRP recovery then rooted it. After that, I went ahead and flashed Viper 2.0, I don't know what I was thinking when I did it but anyway, I have Viper 2.0 now and I am on hboot 1.13. So then I went to change my cid to supercid 11111111 and it was successful, now I want to downgrade. The part where I am a little confused is do I need to flash a 2.31 RUU before I downgrade or can I downgrade from Viper 2.0? I have a nandroid of my stock ROM, I am not sure what I need to do next before I downgrade. I am still on hboot 1.13, it never was upgraded. This might sound confusing but I hope someone can help.
[HTC One S] Darknites:
Don't think rom matters, so think you good to go without the RUU.
[HTC One S] LibertyMonger:
Thanks buddy, Man I was up all night trying to downgrade my sisters HTC One S, it took me about 10 times before it finally finished successfully. I think I was losing connection or something. It could have been the USB cable I was using. But I was getting some pretty scary errors, even saying "Fatal" lol. But you got to stick with it and keep trying and as long as you have prepared correctly and follow directions exactly you eventually get it! My first three times were a breeze! I am much relieved now I can go to sleep. Good Morning y'all! Lol. Thank you to everyone you all are great!
[HTC One S] Darknites:
Np dude an ya it was easy for me too but I'm in no rush to do it again just in case it goes wrong lol.
[HTC One S] ryanshew:
I had that issue with an older laptop, seemed like the usb wasnt fast enough to keep up with the constant restarting of the phone. When I switched to a new laptop, it went through first try.

HTC_One_S | Xparent_ICS_Blue_Tapatalk_2 1.06_Hboot_Downgrade | unofficial_4.2.1_AOKP_Feb7 | Komodo_Kernel
[HTC One S] LibertyMonger:
Yeah for sure bro, it went terribly wrong last night I stayed up til 7am to get it done I couldn't go to sleep til I figured it out! I kept getting errors but kept trying and finally got it. The USB cable I was using might have been the culprit, my cat nibbled on it a bit but not enough to ruin it, it still works just fine but this program might be very particular, I would make sure you're using the best USB cable you have. Just a theory, like I said I didn't think it was nibbled enough to compromise it but that could have been the issue. Man was I relieved when that tiny light came back on! Lmao!

So words for encouragement DO NOT GIVE UP! Just because things seem to be going terribly wrong it does not mean you effed up! Lol

---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------

Yeah I have done 3 other phones and didn't have a single issue, I think that was before my cat nibbled on this cable. It is a short cable, about 10 inches and I left it hanging off my PC and she got a hold of it lol.
[HTC One S] ryanshew:
That cable was probably the issue then.

HTC_One_S | Xparent_ICS_Blue_Tapatalk_2 1.06_Hboot_Downgrade | unofficial_4.2.1_AOKP_Feb7 | Komodo_Kernel
[HTC One S] Sneakyghost:
It says somewhere around the development of emmc_recover, that the connection between linux and phone in QDL mode is very fragile and tears apart often. This will very most likely get worse with a bad cable since this is all about current flow. Also, up until now, this connection cannot be established on a windows machine, apparently because the connection cannot be made stable. Whatever the reason is, it tells us we should set it up as good as we can.

If i where you guys i'd make sure to have a cable which is good, properly shielded, has magnets on either side, then not have some cellphone or bluetooth equipment sit right beside it (interference!). That'll increase your chances of a successful brick downgrade.
[HTC One S] samstheman42:
Maybe this is a dumb question so I'll apologize in advance if it is...

If all I want to do is downgrade my hboot (I'm on a jb ROM and NEED wifi working), do I need to go through all of the above steps? Logic would dictate yes, but I figured I would ask since I haven't bricked my phone (yet) lol

Sent from my Tricked Out Droid
[HTC One S] LibertyMonger:
Yeah you articulated it much better than me, I was guessing that was the issue, my cable has bite marks on it but it isn't pierced through, although I did have a bluetooth adapter on and may have been using my bluetooth headset as well. Very good information to consider before attempting this!
[HTC One S] 2rz_taco_sr5:
I could be wrong but I don't personally know how down grading will fix your WiFi? I downgraded and flashed jelly bean and like the two phones I had replaced before I still had no WiFi. But every time I just flash WiFi partitions and that fixes it so even if you downgrade you wont have wifi. Have you tried flashing that? Its in the dev section.
[HTC One S] ryanshew:
Well, the thing is you have to downgrade to flash those.

HTC_One_S | Xparent_ICS_Blue_Tapatalk_2 1.06_Hboot_Downgrade | unofficial_4.2.1_AOKP_Feb7 | Komodo_Kernel
[HTC One S] bluebenno:
worked for me - thanks

This worked without drama on my 2nd linux rig (debian), it would not work on my fedora laptop - I got into a fight with the qcserial module. Just to document my experiance.

I wanted to run the ViperOneS ROM, but the wifi wouldn't work. Due to my higher hboot version; Performing the FAQ suggestion "Flash WiFi Partitions from the developement forum!" was ineffective. Ref here. After performing this procedure to downgrade the hboot it then worked perfectly, and so did the wifi.

I've since found out that the ViperROM can use the firmware on the partitions and from the filesystem. It seems when I tried it the filesystem takes precidence. I would try this first http://xdaforums.com/showthread.php?p=34271913 - before attemping this procedure. You can also use adb to push the firmware files directly into /etc/firmware.

=> The point I'm trying to make is don't risk your phone unless you have or want to. Just out of principle I want to, it's my phone and I want rw access to all my partitions!

Thanks to mirGantrophy (OP). He in turn thanks - and so do I - beaups, 18th.abn, yarrimapirate. Thanks to others hard work and time, I now own my phone!
[HTC One S] Sneakyghost:
AW: [TUT] Downgrade/Unbrick Ville S4

Interesting.

I was just asking Tecardo if he had tried to inject the Wi-Fi partitions into the file system to see if the system accepts them.

I thank you for two pieces of info:

First, finding out that the file system based firmware is prioritized, secondly that you found out about the Wi-Fi partitions also working that way (that's what I gathered from your post).

However, I wish to note that it isn't just the viper ROM exhibiting this behavior. It seems like this has generally changed from ICS to JellyBean.

sent from viper 2.1 One S
[HTC One S] samstheman42:
The reason I've been considering moving to a lower hboot is because the one I have breaks my ability to connect to wifi (t-mo 1.14) and I actually really need the connectivity. Are you saying I can bypass the need to downgrade with this alternative solution? I read through the op and didn't see anything that seemed useful... Would love some direction if you would indulge me :)

Sent from my Tricked Out Droid
[HTC One S] bluebenno:
I have a proof of concept and will post details soon. I made a small change to Viper's boot.img to link(s) to /etc/firmware rather than to the firmware partitions - so you can use whatever firmwares you want abit easier.

The great thing about open systems is if you don't like something you can just change it. Sorry to stray OT and I certainly don't want to detract from the great and gutsy work of this thread. Just saying in case someone is scared of bricking their phone.
[HTC One S] resadent:
How many minutes do you have to wait actually? This has been running for more than an hour in my case and it finally stopped so I started from the beginning... this is frustrating lol
[HTC One S] Darknites:
It didn't take an hour, think 20-30 minutes.
[HTC One S] bluebenno:
There is some counter in the OS, each time the reset occurs it increments - it has a lowish limit - check th eouput of 'dmesg' on your linux rig, you'll see the error. Replugging into another USB will help. For sure It just felt like it took 20-30 days ;)

I've published a *untested* *hack* to make a Viper ROM ignore the firmware partitions (for WIFI and Radio) and use /etc/firmware. You can then change firmwares by coping in anything you like or via an install tool. http://xdaforums.com/showthread.php?t=2151709
[HTC One S] resadent:
Finally managed to get it, now in hboot 1.06. Thank you very much :)

NOTE: what happened to me, was that my phone didn't reset properly, and happened the second time too. I just held the power for another 10 seconds until QSD disapeared from the terminal and released, then started working again.
[HTC One S] Evil-Monkey:
Main reason I used this method was to be able to flash radios at will. The working wifi partions where just a bonus :)

echo en Android
[HTC One S] bluebenno:
full SOFF now available

A full S-OFF is here http://xdaforums.com/showthread.php?t=2155135

lets not forget to thanks mirGantrophy (OP), yarrimapirate (his tools), beaups, 18th.abn
[HTC One S] Sneakyghost:
AW: [TUT] Downgrade/Unbrick Ville S4

That'll be an interesting bit of info to share on Tecardo's radio thread don't you think?

sent from viper beta 2.1
[HTC One S] eddiemurphy:
Uh while it was flashing the hboot, it suddenly said this "Failed to detect device in dload-mode" what does this mean? what do i do now, do i just continue to the next step?

---------- Post added at 06:17 PM ---------- Previous post was at 06:15 PM ----------

the exact thing just happened to me and I don't know what to do.

Anyone help please?

I looked at some of the previous posts and someone had the same problem as me and i followed the steps that he did and now i am downgraded from hboot 1.13 to 1.06. :)
[HTC One S] pyro43284:
with s-off and super cid we can downgrade our hboot with ruu.. i just updated with ruu 2.35 hboot 1.14 after i relocked my hboot and now im running ruu 1.53 which gives me hboot 1.06 had to share this so we can down grade much easier now i have done this on two one s devices both are s4
[HTC One S] :
With s-off there is no reason to downgrade
[HTC One S] Sneakyghost:
Yes there is. Boot.img flashing is still a bit fussy on the higher hboots even though it shouldn't. Something odd still there. But this thread is now obsolete. What a pity. Loved the messing about here :D

Thanks to the guys involved in this, Grim for bringing it here, Fusion for writing emmc_recover... who else and whatnot... been a good thing!
[HTC One S] eddiemurphy:
Hehe I downgraded then I went to do s-off for an adventure
[HTC One S] jac10000:
Be strong Sneakyghost :p

What of souvenir and adventures :crying: Your first brick, so magnificent :crying:

Please remove the S-Off just for Sneakyghost !!! :p
[HTC One S] Sneakyghost:
AW: [TUT] Downgrade/Unbrick Ville S4

Now, it's not that bad mate :D

sent from viper 2.1
[HTC One S] tominozh:
I think that before anybody want to downgrade should try to get soff first. Its much safer imo. I got soff on hboot 2.15 and there is no more limitations compare to lower hboots (1.06 or 1.09). I can now flash between roms without need to fastboot flash boot.img. I swaped between few roms with different base (like CM10.0, pacman 20.0, viper 2.1) all booted without needs to flash boot.img.

Take this as a friendly advice before you'll try to brick your phone.

:D
[HTC One S] alexskin:
I've made a mistake when hex editing the last file and know I can't unlock the bootloader, I've run a few ruu's but still can't unlock. The phone works fine I'm on JB write know, so I was wondering if there is a way to repair this file. Thanks in advance
[HTC One S] ryanshew:
Ok, that made no sense. What mistake hex editing what?

HTC_One_S | 1.06_Hboot_Downgrade | Tapatalk_HD_Beta | Root_Box | Bubba_Kernel_2.8b | S-OFF
[HTC One S] Evil-Monkey:
To each their own, I knew nothing of linux and still tried this. It's as safe as you want it to be assuming you can read directions. :D my device is still S-Off and in my opinion, super cid and s-off isn't really necessary for me until a dev comes up with a method of adding some memory to our internal sdcard. Because of this method and work these devs put in I've been happily flashing radios before most kids lol

echo en Android
[HTC One S] alexskin:
this one '' This is why it is easier on evita.. http://db.tt/kCeCpDAE

I made a version for you guys.. http://db.tt/ar4sbw6V

Place on your sdcard

open terminal emulator

Code:

$ su

# dd if=/sdcard/mmcblk0p23 of=/dev/block/mmcblk0p23

reboot to fastboot and lock your bootloader. And then run the RUU

You can download the edited version. USE WITH CAUTION ''

because when the tutorial was first posted there was no edited file, and i got confused with the lines that i had to edit, every thing went well, the bootloader downgraded without errors. than i relocked the phone to run a RUU, that went well to, but when i wanted to unlock it again i get error 150 on htcdev.com when confirming the token
[HTC One S] eddiemurphy:
Me too, I knew nothing about Linux except than it was an operating system until a few days ago when I downgraded my hboot and got s-off. It did take me my entire Saturday tho.:p:D
[HTC One S] donverse:
Hmmm I tried to unbrick my One S but it gets "stuck" at step 4 I guess. I can enumerate the partitions but after that my 1S always goes back to that QDL mode and it seems that none of the commands are reaching it. Any help? :/
[HTC One S] bluebenno:
With my linux rig and phone the 'working time' was very short, only a few seconds before it goes back to QDL. If you can see the partitions it should work - try continuing on.
[HTC One S] donverse:
Thanks, but doesn't help :/

Anyone else? I get to step 3 and can enumerate the partitions but after that nothing seems to happen... Especially in step 9 nothing happens and even more important my charging light is still off so for now my 1S is pretty much a very expensive, yet solid, brick, ready to get thrown wherever it may take it..
[HTC One S] ryanshew:
That's not enough info to help...need to know exactly whats happening. Ie...I do this, then this is what happens...include screenshots even a video, so we can see if your doing it right.

Your saying nothing happens after step 4, but then you say you get to step 9, so your leaving out all the important details.

HTC_One_S[-OFF] | Xparent_ICS_Blue_Tapatalk | Root_Box | Bubba_Kernel_3.5
[HTC One S] Leoleg:
Dear friends. I've got brick after OTA updating my One S S4 by WI-FI and off course I have not the mmcblk0p4. Could some one from you take this one from your One S to give me for tying unbrick my.
[HTC One S] Darknites:
Don't work, look here to fix it.
[HTC One S] Evil-Monkey:
What OTA?

echó en Android
[HTC One S] Leoleg:
I've mean FOTA it's updating which sends HTC.
[HTC One S] emdzej:
I've successfully s-offed 2.15 bootloader, but still have one question.

Let's say that for some reason I want to downgrade to 1.06 - can I use the attached hboot.nb0 file with fastboot flash hboot? Is it in the right format?

(the reason for that is that after s-off when the phone is powered off and connected to the charger it can't be turned on - so I assume that this has something in common with the bootloader version. It can be turned on by detaching the charger and holding power for about 30 sec... it will turn on after some time. I guess it get's stuck in qualcomm dload mode for some weird reason).
[HTC One S] tominozh:
What recovery are you using?
[HTC One S] emdzej:
latest cwm touch
[HTC One S] tominozh:
That's the problem of that recovery. Nothing to do with s-off. So you can either live with it or use twrp. There is + and - for both. I'm with cwm at the moment as well.
[HTC One S] emdzej:
Oh, thank you so much for that tip. I'll use the other one then.
[HTC One S] :
This thread is no longer necessary as s-off has been achieved, no need to downgrade with this method. You can just simply flash the hboot without creating the brick, as such, this method is deprecated and unsafe and I will close the thread. I thank all of you for taking your time and helping each other. I hope everyone that had a successful downgrade enjoys their phone, and everyone that didn't downgrade enjoy the s-off (thus removing the need for this) and everyone that bricked, I wish you well. If you choose the JTAG method, good luck to you!
[HTC One S] :
I don't suggest it
[HTC One S] Darknites:
Well I just done it now and thanks for the help. Next step learn how to do a rom lol.
[HTC One S] vietlong3:
When step 9 Waiting for /dev/sdc12... i can not next step.

I save mmcblk0p4 on computer and not save bakp4 on conputer.

can I reset the phone or get rid of this regime?or relock Bootloader?

in here my picture.
[HTC One S] hicdub:
You're an animal. We are all glad you have more balls than the rest of us combined. I'm really enjoying the bootloader!
[HTC One S] mikeyinid:
I knew it would work. Just messed up trying jet first.
[HTC One S] lonoguge:
Hey guys liking this thread but i have one question. Will this downgrade solve all the data problems like switching from g to 3g, loss of 4g, and loss of Wi-Fi on most ROMs other than trickdroid 7? This started when i did a manual upgrade from the official Tmobile - sense stock to android 4.0.4 and sense 4.1. This is the only reason I'm considering this downgrade.
[HTC One S] mikeyinid:
No. But if you downgrade using this process and then ruu 1.53 those issues will mostly be gone..
[HTC One S] lonoguge:
Thanks for the quick reply, so if I were to do the downgrade using the ruu you just mentioned, I would have no problems using ROMs like viper ROM 1.2.0( which is based on 4.0.4 and sense 4.1) without worrying about the same problems of data and Wi-Fi loss happening correct?
[HTC One S] mikeyinid:
Right
[HTC One S] :
$ sudo ./emmc_recover -f ./hboot.nb0 -d /dev/sdb12 -c 24576

If it doesn't write, hold your phone power button until you see Qualcomm, Inc. Gobi Wireless Modem (QDL mode) disappear from your screen
[HTC One S] vietlong3:
I have tried many times still error:

ubuntu@ubuntu:~/Desktop/ville$ sudo ./emmc_recover -f ./bakp4 -d /dev/sdc4 -c 24576
================= emmc_recover 0.3 alpha 2 ==========================

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

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

Ready to write 1024 bytes
Resetting device
Cannot reset device
Reset command sent
Waiting device /dev/sdc4.......
[HTC One S] htcsensation:
run just lines below:

[replace sdb4 to your device]

root@bt:~/Desktop/ville# sudo modprobe -r qcserial

root@bt:~/Desktop/ville# sudo mknod /dev/ttyUSB0 c 188 0

root@bt:~/Desktop/ville# sudo ./emmc_recover -f ./bakp4 -d /dev/sdb4 -c 24576

================= emmc_recover 0.3 alpha 2 ==========================

Using chunksize 24576

Messing up with device /dev/sdb4, ARE YOU SURE?

CTRL+C if not, ENTER to continue

Ok, ready to flash

Filesize:	1024

Chunksize is:	24576

Cycle count is: 0.541667

Press ENTER if everything is correct, CTRL+C if not

Ready to write 1024 bytes

Resetting device

Cannot reset device

Reset command sent

Waiting device /dev/sdb4.......

Found device!

Writing 1024 bytes to offset 0x00000000

Waiting mode-switch

Device changed mode

Detected mode-switch

root@bt:~/Desktop/ville#

if it doesnt start , pres pover button for 10 sec. until it started
[HTC One S] :
Reboot your computer..

Use the power button to reset it
[HTC One S] encho:
Where to get other hboot versions? Downgrading to 06 reintroduced 'crazy buttons' syndrome :eek:

I guess it is still worth it - flashing kernels and stuff. I will use 3G only mode in meantime.
[HTC One S] Darknites:
You need a RUU for that and what crazy buttons? mine is working fine.
[HTC One S] mikeyinid:
Hboot has nothing to do with what your talking about
[HTC One S] alltubetone:
Hold down the power button on the phone for ~13 seconds and then release and it should start writing. When I did this is hung up a few times during the writing process.

EDIT: Quote from First Post:
[HTC One S] encho:
Thx. Didn't have the soft button problem since my last ruu update 4 months ago. Downgraded hboot and it started happening the very next day. Freakish coincidence?
[HTC One S] rootrider:
Glad to be back on 1.06.

Had to press the power button many many times but successfully finished. And oh, one more thing: Use Ubuntu as mentioned by the OP. Tried Linux Mint Debian before, but got stuck when writing the 'new' h-boot.

And last not least, I hit thanks-button already. So thank you for this useful post and your help.
[HTC One S] alexskin:
i-ve got a problem, i-ve put the killp4 file on my phone made the backup and kild the phone but it does not boot in the qdl mode, i-m holding the power button but it doesn-t do nothing, one more thing what recovery are u talcking about? custom or the original? becouse i have a custom one

---------- Post added at 05:53 PM ---------- Previous post was at 05:25 PM ----------

how do i know witch sd* is my phone?

---------- Post added at 06:43 PM ---------- Previous post was at 05:53 PM ----------

in step 12 i'm geting error ./emmc_recover: command not found