yashsingh1/xdaforums huggingface dataset:
[HTC One S] jac10000:
it's because

$ sudo ./emmc_recover -f ./bakp4 -d /dev/sdc4 -c 24576

don't work

(step 9 work ? )

And if the computer don't se your phone even if you hold your phone's power button for about 10 seconds , you must restart your computer.

and

5. Make sure Linux sees the phone
Code:
$ sudo dmesg | grep "qcserial"
You should see "Qualcomm USB modem converter detected" as the last line of the output. If not, you can unplug and replug the USB cable or run...

Code:
$ sudo modprobe qcserial
to reload the driver

6. Reset the driver
Code:
$ sudo modprobe -r qcserial
7. create the block device
Code:
$ sudo mknod /dev/ttyUSB0 c 188 0
8. Open a third Terminal window and navigate to where you stored the ville folder. I saved it to my desktop, so my code is
Code:
$ cd Desktop/ville
$ chmod +x emmc_recover

Then

12. Now we restore the original mmcblk0p4 that you should have saved as "bakp4"
Code:
$ sudo ./emmc_recover -f ./bakp4 -d /dev/sdc4 -c 24576
[HTC One S] ratelutz:
ok did this and i was able to flash bakp4

but afterward nothing happens. still not able to boot phone
[HTC One S] jac10000:
When you flashed hboot on step 9,

9. Now we restore the hboot.. replace /sdc12 with your device location that we discovered in step 3 and 4
Code:
$ sudo ./emmc_recover -f ./hboot.nb0 -d /dev/sdc12 -c 24576

it will take several minutes ? No "waiting for device" only on terminal ?
[HTC One S] ratelutz:
yep on step 9 and it worked

should i reflash hboot again?
[HTC One S] jac10000:
if the two flash worked you must have your charging light turns back on. If not you must restart since step 5 and all reflash.

If your charging light turns on , you could reboot your phone. long press on power pehaps to reboot
[HTC One S] ratelutz:
ok i start over from step 5

i will report the result

thanks

---------- Post added at 12:15 AM ---------- Previous post was at 12:05 AM ----------

does not help here what happens

1. sudo modprobe -r qcserial

2. sudo mknod /dev/ttyUSB0 c 188 0

3. pushed power butto 10sec. lsusb changes from Qalcom, In. Gobi Wireless Modem to Qualcom Inc. and devices are in /dev/

4. run sudo ./emmc_recover -f ./hboot.nb0 -d /dev/sdc12 -c 24576

output:================= emmc_recover 0.3 alpha 2 ==========================

Using chunksize 24576

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

CTRL+C if not, ENTER to continue

Please connected device

this@this:~/ville$

and thats it /device removed and lsmod switches back to ... Gobi Wireless Modem...
[HTC One S] jac10000:
I see in your signature you have a htc hd2, you don't do that on a hd2 ? Really a One S ? Reassure I lol
[HTC One S] ratelutz:
its because i'm working on my wifes phone.

and she will XXXX me if i can not fix it :(
[HTC One S] :
Restart the computer and do it again.. don't do emmc_recover -r, use your power button

Sent from my One X
[HTC One S] ratelutz:
did that allready two times
[HTC One S] jac10000:
Do that he say, absolutelygrim help you better than me

Edit: it's really sdc4 and sdc12 for you ? no sdb4 and sdb12 ?
[HTC One S] ratelutz:
puuhhhh finaly i booted.

thanks guys for your help
[HTC One S] jac10000:
:) your wife will not XXXX you ;)
[HTC One S] Sneakyghost:
You guys scare me a lot :D

I've got a triple boot laptop now with win 7, 8 and Ubuntu. Will also dive into it over Christmas as my wife's not here and I've got some precious time then to chill and do this properly.

Installing Ubuntu already gave me some first impressions and I'm confident I can manage, especially since seeing Grim supporting people so much here.

That's the sole reason of my post here now: I wanted to express that I'm very grateful for your doings here mate. I and most others value your frequent and fast responses highly.

Thank you, Sir!

sent from a phone
[HTC One S] ryanshew:
Yes thank you very much grim, my phone is much more enjoyable thanks to you.

One S | ICS Blue XDA Premium | MIUI Sense | Bricked Beastmode
[HTC One S] pottyvick:
So something weird happened with my one S... Went through the whole process... After the last step the charging light didnt turn on. So i started back at step 5. During the flashing of the hboot (again) it rebooted the phone into recovery... i selected reboot and pow! Hboot 1.06 and my rom is working great... Not sure why that happened, but seems to be working
[HTC One S] ratelutz:
this is nearly the same, like happend to me
[HTC One S] mikennite:
Do I need to create the brick for this to work?
[HTC One S] jac10000:
Yes, without brick it can't work
[HTC One S] LibertyMonger:
Hi guys thanks for the great support in this thread. I am ready downgrade my hboot from 1.13 to 1.06 but I think I have one question before i start. I am getting mixed answers and not sure which is best. I changed my cid to HTC__001 and was told to do so then flash a 2.31 RUU. Well that didn't work so I am on the Venom ROM. Can I just go ahead with this or do I need to run an unbranded RUU first? My phone is showing it is unbranded after changing my cid to HTC__001.

Thanks for your help!
[HTC One S] Darknites:
If you still got that RUU then do SuperCID and the RUU will work and I think its a good idea to do it but not needed but I think you should do what I say :p:laugh: because its been working great for me.
[HTC One S] LibertyMonger:
Yeah I know Buddy, I am just wondering if i have to run the unbranded RUU or can I just start the downgrade. Guess I will try tonight. Thanks
[HTC One S] Darknites:
Has far I know you don't have to so its up to you on that.
[HTC One S] dharvey4651:
Forgive me if this has been asked before but the thread is a whopping 36 pages long and being Christmas eve I don't have the time to read through everything(I did read the whole first page).

Has anyone come up with an automated version of this yet? Or semi-automated? I think if it was possible to run a tool that does all of the scripts for you and simply tells you when to hold down the power button and unplug-plug in the USB would be absolutely invaluable. It would save hours of work and dramatically reduce the amount of bricks as a result of not properly following instructions among other things.

Again please understand that I did not read the whole thread, only the first page and only because I don't have time to read the whole thing. An answer would be appreciated and please accept my apology if this has been asked and answered before
[HTC One S] Darknites:
Can't think who did it but there is scripts for some parts.
[HTC One S] :
I'll add it to the op if I find it.. the only true automated version is for Evita/jewel which the scripts were designed for. Luckily most, if not all, msm8960 devices (dual core s4) are set up the same way. Which is why the manual method works.
[HTC One S] v3n3:
Im a bit panic-ing right now, so please excuse me :-x

Im from Germany, we just got the 4.1 Update yesterday, I relocked my Bootloader today blablabla, flashed the RUU and installed the Officiall Update.

Well, my phone shows up as "QHSUSB_DLOAD" now in Device Manager. Nothing else I can do >.<

To my questions:

This Thread is named "Unbrick Ville S4" but the first few steps require you to do something while your phone is not bricked.

Is there any way to recover the phone without the backup of "mmcblk0p4" ?

Thanks ( and maybe that should be mentioned in OP :-x )

EDIT:

Like I said, I paniked, did just read a little further, and it looks like its going to work for me ...

Going to give feedback when it worked out :-3
[HTC One S] inetdua:
I'm from Russia and we have the same.

If you strictly follow the instructions, but on step # 3 nothing happens. The phone does not see the sections. What to do - is unknown.
[HTC One S] hellgod:
Same here with the 4.1 OTA, don't know what to do...
[HTC One S] jujusito:
Hi

Updating to JB ota mi one s brick, corrupted hboot. I follow This tutorial but i can't unbrick it.

I have relocked bootloader and stock recovery, ¿This method works with this configuration?, tanks a lot.
[HTC One S] KeroG:
+1....
[HTC One S] rootrider:
Ok, had this problem as well tonight when I started downgrading.

After I entered the list command a couple of times and nothing happened, I pressed the power button for about 12 seconds (modem reset) and continued entering the list command afterwards. The additional driveletters appeared in a glance when the connection was automatically reestablished.

I downgraded from 2.15 to 1.06.
[HTC One S] Sneakyghost:
I was already believing the jb hboot would disable the brick downgrade... Thanks for your answer buddy!

sent from a phone
[HTC One S] inetdua:
We did not downgrade. And brick with us for another reason. We are talking about different things. In our case the phone is not working after update
[HTC One S] hellgod:
In my case I think the brick comme from the fact that my phone was in "SUPER_CID" not in onriginal one.

The OTA shoud have write the new hboot and then the hboot check the device CID but it don't match cause of the supercid then il lock the phone...
[HTC One S] inetdua:
It is important for us to understand only one thing: how to see the partitions on the phone? Because anything more than that, we can't get
[HTC One S] Darknites:
Its not SuperCID because rootrider has that and it worked fine for him, there is more to it then just SuperCID.
[HTC One S] v3n3:
Tried this for nearly an Hour now, the Device does disapear from the lsusb List but the Partitions dont show up :-/

Im rushing out the "ls /dev/sd*" command like its the last day, but nothing shows up.

That makes me sad ... really dont want to send my phone to Service
[HTC One S] rootrider:
Did you unplug/replug your device already at this point? Give it a try.
[HTC One S] inetdua:
new threat here to collect all info about this issue. (BRICK AFTER UPDATE OTA)
[HTC One S] PeQuEsan:
I'm about to test this, as I don't want to apply JB OTA, and do it manually, flashing new radio, and after that some cooked ROM based on that JB release... I'm currently downloading ubuntu (I'm on very low bandwidth connection), as advised in the OP.

Just one question... If I understand right, you backup your own p4, to restore it after flashing 1.06 HBOOT included in ville.zip package... Then... why I can see a backp4 file inside that ville.zip package... ¿?

Thanks a lot.
[HTC One S] mycomputerisjunk:
Followed the instructions and everything when fine until the end. The last step says that the charge light will turn on and the QDL Mode will be removed out of the lsusb window. Ran the last command and it finished. However, noting happened. So, I started over again. Now it wont go past waiting device /dev/..

I have tried restarting the computer and sudo ./emmc_recover -r. Nothing.. Sad

Any insight would be great.
[HTC One S] dc211:
the backp4 is in there incase you forgot to copy your original one fromthe phone. if you wanted to use that one you need to edit the file and input your imei.
[HTC One S] :
It says if you get stuck at waiting for device, you may need to do "sudo modprobe -r qcserial" if that doesn't work, restart your computer

Did you take the ota update and brick?

My guess is.. that for some reason, it is writing over p4 which is what the CPU uses to boot into the OS, as well as a write protected hboot. However, if you did not brick and have the new hboot. This method should still work to downgrade

$ su

#
[HTC One S] mycomputerisjunk:
As for the OTA, no clue. I just got the phone from someone. They said they just got it replaced under warranty, so it was likely the latest. I am running a live CD and I have restarted a couple times and used the sudo modprobe -r qcserial. As of now, the phone is black and does nothing. I can however see Qualcomm, Inc. Gobi Wireless Modem (QDL mode) listed in lsusb.
[HTC One S] :
When it goes into QDL mode try doing "ls /dev sd*" until you see

/sdc1-36, it may be sdb or sdd, most likely sdc though
[HTC One S] mycomputerisjunk:
Nop. I saw all the extra partitions the first time I did it, but now it only shows whats on the computer. I spammed the hell out of it, no changes.
[HTC One S] v3n3:
Yes, I did.

Tried another USB-Port, Machine ( from Laptop to Desktop ) and another USB-Cable ( both offficial HTC ) ... nothing :-/

Atleast I tried ;)

Thank you for your support.
[HTC One S] PeQuEsan:
Done! Thanks to you I've been able to downgrade to 1.06 HBOOT, and thus, flash new JB radio and wifi partitions from recovery. :)

Just a little correction: command for first of the three linux terminal windows is incorrect... You don't have to insert the dot, so correct command is:

watch -n 1 lsusb

...quite easy to figure out, but maybe someone can be a little bit nervous if first command doesn't work exactly as expected...

From there, all is absolutely correct. More than 10 minutes flashing chunks of 1.06 HBOOT!!! It was a neverending experience... :P

bye!
[HTC One S] :
If using Ubuntu like the op states, "watch -n.1 lsusb" should work without error. Some other distributions and shells don't like the "." However
[HTC One S] :
No, that's why I asked for your p23.. For the One X it holds the RUU information, yours didn't. If you can get me the partition table list I may be able to find out which partition it is in.

Or can you plug your phone in to a computer, enable USB debugging and get me another copy of p23?

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

Here's a copy of One X p23 if it helps you find what you are looking for

https://www.dropbox.com/s/t5am01ur1fketpq/p23

As you can see, the RUU information is at 0xA0, right after "ClearAutoImage" I have it edited to 1.00.000.0 which enables us to run any RUU
[HTC One S] mikeyinid:
I'll dump you a new one, or look for the one that matches yours

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

youre right, its blank. any other ideas which it might be?
[HTC One S] mbh87:
I think it's only not blank if you super cid, but since the One S has access to the bootloader unlock that isn't necessary.
[HTC One S] :
His bakp4 had superCID already applied to it. I don't know if that's the determining factor on p23
[HTC One S] alltubetone:
Worked Perfectly! Had to hold the power button down a couple times while writing the hboot, but otherwise went very smoothly!
[HTC One S] mikeyinid:
Yea the p4 that guy gave me was already supercid. I just want to be able to run the old ruu so I can get wifi back on all the roms.
[HTC One S] dc211:
You can use the all in one tool kit and hit the Main Version Error Fix and it will write the 1.00.000.0 for you. If the only thing stopping you from using a RUU is the main version that's you're fix.

Here it is after it's applied if you still want it.

https://dl.dropbox.com/s/5asrhpnrpnbpzdy/mmcblk0p23?dl=1
[HTC One S] topnomi:
I Just successfully downgraded from 1.13 to 1.06 :highfive:

I first tried in my brother's archlinux. It would't wait for the device when i ran emmc_recover (it just errored out saying not connected). After banging my head against the wall for about 10 min, I decided to try a usb linux mint 13. It worked like a charm!

So I'd like to reinforce that you should use a debian based linux distribution when proforming this process.

Thanks for helping us downgrade to functional :)
[HTC One S] plocri:
does the downgrade tip with the terminal emulator can be done only itself or is something to do only after the unbrick procedure?
[HTC One S] :
You can do it at any time.. just hex edit p23 and dd it back to the phone
[HTC One S] plocri:
so let me understand: I've debranded my vodafone one s, installed 2.31 european ruu, now with custom recovery and root I can edit the hex file, restore vodafone cid, relock bootloader and install vodafone ruu, right?

I have to do this because wifi cannot connect with stock and custom roms :(
[HTC One S] htcsensation:
watch -n.1 lsusb is showing me :

High Tech Computer corp.

and sudo dmesg | grep "qcserial"

nothing. this is just a test before killing the phone

this is normal?
[HTC One S] :
Its not bricked... it'll show as

Qualcomm, Inc. Gobi wireless modem (QDL mode) if its bricked
[HTC One S] :
Yes. Just make sure you have supercid or vodafone
[HTC One S] plocri:
i'm using vodap001 cid and supercid too, but both 1.53 and 1.78 ruu give me error 155...

help please :(
[HTC One S] sherry478:
can someone help me please in step nine i replaced sdc12 with sdb12 and now the first window i dont see the phone anymore and i cant resore my p4 it keeps saying "please connected device" i starting to panic becuase i cant do anything.
[HTC One S] dc211:
Don't panic you're on the right track. Restoring your p4 isn't until step 12. Have you flashed hboot yet (step 9)?

Did you see "Qualcomm USB modem converter detected" after you did? $ sudo dmesg | grep "qcserial"

What was the last command you ran?
[HTC One S] sherry478:
i did flash the hboot it shows this

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!
Writing 24576 bytes to offset 0x00024000
Waiting mode-switch
Device changed mode
Failed to detect device in dload-mode

---------- Post added at 04:54 PM ---------- Previous post was at 04:51 PM ----------

i dont see "Qualcomm USB modem converter detected" ater i do $ sudo dmesg | grep "qcserial"
[HTC One S] :
Did you relock your boot loader?
[HTC One S] dc211:
I can't tell if your hboot finished or not it doesn't look like it to me. I didn't expect your problem to be there. You're gonna have to wait for Grim to pop in. He's online so sit tight and don't worry.
[HTC One S] PeQuEsan:
I used a new ubuntu 12.10 installation... And it didn't like the dot... :confused:

Desde el móvil...
[HTC One S] mycomputerisjunk:
So in QDL mode, is the phone actually on in some way? Reason I ask is because my phone is still black and I am waiting for the battery to die.
[HTC One S] :
Yes the phone is on in qdl mode
[HTC One S] LibertyMonger:
BEMYOW!!!

I DID IT!!! I DOWNGRADED MY HBOOT YEEHAW!!! Lol

Ps...Now I need to figure out which radio will be best for me.

Thanks a bunch absolutelygrim very much appreciated Bud!
[HTC One S] Darknites:
Woohoo finally lol.
[HTC One S] jac10000:
Ruu downgrade

If I want to ruu downgrade, I have to edit mmcblk0p23, ok , but also have I to downgrade the hboot if it's 1.13 or 1.14 ?
[HTC One S] mycomputerisjunk:
So, for those of us where to phone is black after the last command... Any ideas?
[HTC One S] Sneakyghost:
As discussed with some folks, it isn't as plain on ubuntu. Finally I got to know that the dot needs to be a comma in German. Here, "watch lsusb -n.1" would become "watch lsusb -n,1"

So, after all, keyboard layout or general usage of special characters also differs from language to language and needs to be taken into consideration.

This problem was the initial cause of me suggesting some sort of FAQ in the first place.

I have found out though that the internet is full of quite comprehensive explanations (often easy to understand even) of Linux stuff. So, I've now reverted to learning and practicing terminal stuff before actually doing anything serious.

After all, I'm still very scared...

:D

sent from a phone
[HTC One S] Darknites:
Lol one day dude one day you be enjoying the life of a low Hboot.
[HTC One S] neptuno92:
Help needed

Hi everyone, I need some help. I have a bricked One S and when I'm in step 2 I can't find a way to make QDL mode go away. I just press power button for about 10 sec. then all the info about my phone disappears and 5 sec. later I can see the same QDL mode activated than before.

What should I do?

Thanks :)
[HTC One S] ryanshew:
That's what it's supposed to do.

One S | Xparent Red Tapatalk 2 | Viper 1.2.1 | Bricked Beastmode
[HTC One S] neptuno92:
I don't undestrand that in the tuto... QDL should disapear after pressing the power button and I'm still seeing Qualcomm, Inc. Gobi Wireless Modem (QDL mode).

Edit: Anyway, even if that was correct I'm unable to list the partitions of the phone... so I'm at the same point :S
[HTC One S] ryanshew:
As soon as it disappears, start spamming the command, over and over and over.

One S | Xparent Red Tapatalk 2 | Viper 1.2.1 | Bricked Beastmode
[HTC One S] neptuno92:
Yes, I've been trying this for hours and it doesn't work. I see Qualcomm, Inc. Gobi Wireless Modem (QDL mode), it disappears and I start spamming, 5 sec. later I have Qualcomm, Inc. Gobi Wireless Modem (QDL mode) again, not Qualcomm, Inc. as it should be.
[HTC One S] LibertyMonger:
I think you need to unplug usb and plug it back in, I had this issue at first too. Read the tuto carefully it tells you this I think, It helped me get by this.
[HTC One S] :
If you bricked by taking the ota this won't fix it
[HTC One S] neptuno92:
I was installing a zip for upgrading to Jelly Bean. I thought that the problem is a not completed installation of a new hboot but I'm not sure. Is there any other way for unbricking my phone?
[HTC One S] LibertyMonger:
Just finished successfully downgrading for my 2nd HTC One S, my nieces hboot! She's very happy. Thanks again for making this possible and for the great tutorial, makes it nice and easy.
[HTC One S] :
Do you guys happen to have the proper hex for your phone? We just figured out how to unbrick the one x with our hex files, but they are missing what is called a "cookie" so we can't use them for s-off yet

Edit: false alarm. Lol
[HTC One S] rijon99:
Can someone help me with this? Are there any YouTube videos or anything? I'm a complete noob at linux, but I really want to downgrade my hboot :/
[HTC One S] Sneakyghost:
Do what i do. Grab Ubuntu Distro off their page (free download), then google Live Ubuntu USB Creator or something like that, then find yourself a tool like e.g. LiLi to make a bootable live usb, then start learning all the sh!t...

best thing is launch firefox once you found your way around the ubuntu desktop and every question that comes up goes right into google search :D

I have figured out a few things around the usage of terminal already and i am confident that one fine day when i am quite sure that i can recover my device because i know enough i will proceed with the brick.

I believe its probably asked too much of the guys here to educate you if one has no linux knowledge (like me, i saw my first ever booted linux desktop about two weeks ago lol).

PS:

Oh and i don't think YouTube is a good way of learning... most stuff you learn goes through the hands, not the eyes. Read stuff, then type it to try it out (like commands or search terms and stuff....). It will stick in memory much better.