yashsingh1/xdaforums huggingface dataset:
[HTC One S] jac10000:
You can always try, we not never know ... before send your phone to repair , try all solutions
[HTC One S] Tyler DeLarge:
are there other soluctions?
[HTC One S] cat2115:
Found this in eBay for HTC One S JTAG Brick Repair Service in USA. http://www.ebay.com/itm/HTC-One-S-J...411?pt=LH_DefaultDomain_0&hash=item25796e0553
[HTC One S] Tyler DeLarge:
no, at this point i prefer send it to HTC!
[HTC One S] Sneakyghost:
I did. I did not say i was messing with hboot. I was close to the truth though. Problem: they were not interested. They said only the Repair Centers determine if warranty yes or no. Not the support. And the Repair-Center will lock down any warranty claims as soon as they see an open bootloader.

(Which they ignore in case of a valid and recognized problem like the Home Button Bug, but do NOT ignore in case of a brick).

Clear?

Tyler, send the phone to some unbrick service. Doesnt need to be Tec's and mine. But send it in. Its not gonna come alive again. Trust me. No partitions visible to Linux on different USB Ports and Machines just means its dead. A fast switching QDL/no QDL means it's even more dead. Sorry.

And if the HTC Repair Center sees your open bootloader, they will charge you a return fee, it is 25 Euro in DE. If you have them NOT fix it and send it back to you, you still lose these 25 Euro. If they fix it, they will most likely charge you new Motherboard. Usually, they do no JTAG recoveries but rather replace the mainboard. Which is nearly as expensive as a new phone alltogether.

But try and report your Experience please...
[HTC One S] Tyler DeLarge:
on windows qhen i connect phone to pc, the pc sees the phone as: qhsusb_dload

i installed driver but i can t open it
[HTC One S] jac10000:
it shall have been good that you can boot on bootloader
[HTC One S] mycomputerisjunk:
Your phone is a brick. I had the same exact thing happen to my first One S. Send it in to HTC or get it someone to jtag it.
[HTC One S] :
As you've been told the past 3 pages.. this method will no longer help you. Either warranty it or find someone with a riff box to fix it
[HTC One S] Sneakyghost:
RIFF Box on order now. JTAG Unbrick Service here: http://goo.gl/7wJSA

Tecardo sent my mainboard off to Multi-com.pl today. They will produce the first JIG connector for the HTC One S on the market and for letting them have my mainboard as a mould they pay the shipping back and to them, give one free JIG to Tec and probably fix up my bootloader too :D

I can only say, this service is a unique deal for you guys. Tec will not charge you but just kindly ask for a small donation to unbrick the phones for you and you will most likely just have to pay the postage...

just sayin...
[HTC One S] jac10000:
It's un good news !

I I believed that One S was taken care by the riffbox but not because it did not exist Jig connector for it. Your are the first lol .
[HTC One S] Sneakyghost:
Yeah i am very curious how that all works out. Especially the JTAG Recovery. I am not totally sure this brick can be recovered but if it can, you guys know that brick downgrading has a secure and not-to-expensive way to get out of again.

Just lets pray and keep fingers crossed it all works out how we planned!

@Absolutelygrim:

How many reports of Post-JB bricks did you count for the One S?

Where there any reported at all?

Are you maybe confusing it with the SuperCID to JB OTA brick?

I was under the impression, on the HOS we can brick downgrade for sure even after the JB OTA? Still you have this big warning in Post #1?

Maybe Tecardo and I can test this when my mainboard is back, just do a couple of up- and downgrades and see how it goes?
[HTC One S] Darknites:
I think he was getting mixed up but there has been at least 2 people that bricked there phone trying to downgrade.
[HTC One S] ryanshew:
Geez, now I feel bad, as I was one of the ones telling you to go ahead with it.

Do you think it has something to do with the 2.15 bootloader?

One S | Xparent ICS Tapatalk 2 | Viper 1.2.1 | Bricked Beastmode
[HTC One S] theguitarman94:
I'm definitely one of them. My phone was completely perfect, nothing wrong with it and I bricked it with the downgrade method. Waiting for mine to come back from repair. I bricked it over 3 weeks ago and I've sent it in for the second time (this time it better get fixed!)
[HTC One S] Darknites:
Ok make that 3 people lol.
[HTC One S] LibertyMonger:
It's really odd there have been bricks, it all seemed very easy to me I've downgraded all 4 of my family's HOS phones with no issues. Were people fooling around trying it back and forth more than once or what? I know after one downgrade that's it for me I wouldn't want to upgrade and back again for nothing, I am not sure of the whole situations it just seems this is something you wouldn't want to push your luck with lol. I hope you all have great success with the jtag
[HTC One S] theguitarman94:
Did you downgrade any of them from Jellybean? I'm very comfortable with linux and this sort of thing (never bricked any of my phones before) my phone just didn't want to comply lol! I just got my 8x through the post so I thought why not try and downgrade! Can't wait to get it back though
[HTC One S] bstylz911:
is there a VIDEO TUT for this?
[HTC One S] :
No I didn't mix anything up, one s and one x users have bricked from CID ota, and a few one x people have bricked from trying to downgrade from the JB firmware. I just put up the warning anyway.. not that people read, they still blame me for bricking or not able to help them fix it
[HTC One S] Sneakyghost:
Ok cool then mate. It does appear to be a bit more risky than originally thought then.

Sorry out of thanks again for the day already.

Keep up the good work!

Cheers
[HTC One S] LibertyMonger:
No I only downgraded from 1.13 to 1.06 and will never want to upgrade. It seems people who downgrade are so worried about being able to get OTA's after but I don't see the point. That's why we are here in XDA to get better than stock! Lol. It seems to me once you downgrade, leave it be I wouldn't want to take any chances
[HTC One S] 2rz_taco_sr5:
Call quality problem.

has anyone been having problems with horrible call quality? i did this to my replacement phone a few weeks ago then noticed my sound making a call was HORRIBLE no big deal i thought so i got ANOTHER replacement... mad some calls on it to check it and everything is fine. so then i do this again and BAM instantly after i had to make a call and problem is right back... only thing i did was downgrade hboot and restore nandroid so i thought it could be the rom but going back to ICS rom the problem is still there.... im very confused... can the hboot effect call quality? will upgrading my hboot back fix the problem possibly? it is a night and day difference before the downgrade crystal clear and now i cant turn my volume up more than half way even on my stock nandroid restored.... i can compare to my girlfriends stock htc one s and call the same number and my phone is almost unusable where as hers is fine.

any help is really appreciated.
[HTC One S] adolfo778:
Try flashing a different radio
[HTC One S] 2rz_taco_sr5:
thanks thats a good idea. ill give it a try. the phone i got replaced and both the replacements were all on 1.11t but maybe reflashing will reset something? ill be back...
[HTC One S] 2rz_taco_sr5:
Flashed the radio and no improvement. Better yet I ran the ruu on the phone I have to return and it works fine again so its definitely software based...
[HTC One S] ryanshew:
Downgrade again, then flash a ruu containing the 1.09 hboot. It has all the same capabilities as 1.06. Maybe that will work.

HTC_One_S | 1.06_Bootloader_Downgrade | Xparent_ICS_Tapatalk_2.4.1 | MIUI_Sense_Based| Beastmode_BRICKED_rc5
[HTC One S] 2rz_taco_sr5:
Yeah maybe... Can I just do main version fix then run an older hboot? I'm still on 1.06 but you would think others would have the same problem if it was hboot 1.06... My original one s came with 1.06 and was rooted from day one and never had an issue. I might flash the recent ruu on this second replacement which should fix this one too then root and only do the downgrade again and see where the sound issue starts...
[HTC One S] ryanshew:
Have you tried just flashing a fresh ROM after a full wipe, rather than a nandroid?

HTC_One_S | 1.06_Bootloader_Downgrade | Xparent_ICS_Tapatalk_2.4.1 | Paranoid_Android | Blackout_AOZP_RC3_Kernel
[HTC One S] 2rz_taco_sr5:
Ill try that soon thanks for the ideas guys had a family emergency come up yesterday so been busy but ill let you know if I figure it out.
[HTC One S] ryanshew:
btw, which radio did you try to flash and which did you have previous?

One S | Xparent ICS Tapatalk 2 | Viper 1.2.1 | Bricked Beastmode
[HTC One S] pnut22r:
How many people did this with livecd, and how many people did a full install of Linux? Also is there a preferred Rom to be on when starting this procedure? I'm prepping now. Don't want to mess around.

Any tips?
[HTC One S] ryanshew:
Dual boot with Windows. Ubuntu 12.04 rather than 12.1 seemed to work better for me.

Rom doesn't matter, just make sure you haven't taken the jb ota. Or if your on hboot 2.15, don't do it.

HTC_One_S | 1.06_Hboot_Downgrade | Tapatalk_HD_Beta | unofficial_AOKP_Oct11_[Tablet_UI] | Blackout_AOZP_Revised_Oct11_Kernel
[HTC One S] pnut22r:
Excellent. I have

**Tampered**

**Unlocked**

Hboot 1.14.0005

Does this actually make the device s-off? Or does it just hack it so we can flash stuff without having to flash boot.img?

Also, I read the first few pages... What's the consensus on returning to complete stock of need be?
[HTC One S] Qs5:
No we don't get s-off. But with Hboot 1.06 and 1.09 you can flash boot.img, recoveries, radios/basebands, splash screens.
[HTC One S] Darknites:
I used web install to do it that way you can easily uninstall it after.
[HTC One S] pnut22r:
And this means I can flash a Rom straight up. No having to flash the boot.img after, correct?

Oh, and how long did the process take?
[HTC One S] Darknites:
Yep and about half hour.
[HTC One S] ryanshew:
Yup, it's one of the best upgrades...err...downgrades available for this phone.

HTC_One_S | 1.06_Hboot_Downgrade | Tapatalk_HD_Beta | unofficial_AOKP_Oct11_[Tablet_UI] | Blackout_AOZP_Revised_Oct11_Kernel
[HTC One S] Darknites:
Yep best downgrade upgrade ever.

Edit, so reminds me of fonejacker.
[HTC One S] pnut22r:
I'm having trouble with the last step. I finish everything with no errors, and everything writes correctly, but the charge light doesn't come on and the Qualcomm label doesn't go away. Thoughts?

Edit: weird, right after I wrote this post, I went back and ran the step with the hboot, half way through, it stopped, my light came on, Qualcomm went away. I rebooted my phone and all is well. Weird
[HTC One S] Sneakyghost:
AW: [TUT] Downgrade/Unbrick Ville S4

I'd recommend to flash the 1.53 ruu after downgrade to stabilize the hboot as your flash seems to have been interrupted.

Mine went like that, then showed graphical glitches in bootloader and odd behavior upon restarts. 2 weeks later, the reboots had deteriorated to a point where I often needed two attempts to boot the device. Then it died and never came back. Now Tecardo will unbrick it but we are still waiting for equipment.

Sent from my Oldschool HD2
[HTC One S] pnut22r:
Really. Yeah it was really weird. I thought I would just go back a few steps, give it a shot. As mentioned it came out right during the second attempt to flash the hboot. As mentioned, I had already made it to the last step and nothing had happened. So everything was already loaded.

So, you suggest I flash the 1.53 ruu? What will this do? Will I have to re-root? Will I have to do this downgrade again?

Just want to avoid problems later.
[HTC One S] pnut22r:
So get the ruu, and run it from a Windows pc?

This thread has the ruu, and there is only 1.53 for tmous, I assume that's the one you mean

http://xdaforums.com/showthread.php?p=36586654

Or would it be more beneficial to run the entire downgrade again? Try and get the hboot to write again?
[HTC One S] pnut22r:
Okay. So I was having trouble flashing some roms after doing this downgrade. As suggested by sneakyghost, I did an OEM lock and flashed the 1.53 ruu.

Now, should I re-root and be good? Or upgrade then re-root and do this downgrade again? Suggestions?

I do currently have 1.06 hboot after the ruu
[HTC One S] jac10000:
yes you can re-root, it's good. Not need of other upgrade and downgrade because you are on 1.06 hboot.
[HTC One S] pnut22r:
Thanks. Question for everyone...

When I ran the ruu, does that actually rewrite the hboot? If I'm on hboot 1.6, and I run the ruu, does it redo the hboot? Sneakyghost suggested flashing the ruu to make the hboot more stable. Just thinking that means it will redo the hboot part. That should make things more stable
[HTC One S] jac10000:
If you install a more recent ruu you also install a more recent hboot. And if the new hboot is above 1.13 You will again have to downgrade it
[HTC One S] pnut22r:
Okay, I'm having a hard time with this. Downgraded, had some trouble with some roms. Flashed the ruu, rerooted, had more trouble with certain roms (viper ics), then couldn't boot back into recovery. Reflashed the ruu. Took two ota updates, and now I'm on 1.09

I was having a hard time with 1.06, should I try again with 1.09? The trouble I'm having with viper is that it won't boot. I can flash other roms without having to flash the boot.img afterward, but viper won't boot. Is there something with that rom that causes trouble ?

Also, I should be okay worth 1.09 correct?

Also, the goal of this is to be able to flash roms, without having to separately flash the boot, correct? Seemingly, it's similar to having soff, correct?
[HTC One S] Darknites:
Do you say no to custom kernel?
[HTC One S] ryanshew:
Ya, I had the same trouble with viper, I think what it is, is that they use an aroma script to customize the install and since that rom came out at the time inbetween 1.13 and this downgrade, I don't think the installer even attempts to flash the boot image.

All you have to do is fastboot the boot.img, they even have a script for that, you put on your pc and double click it, then it does the rest.

HTC_One_S | 1.06_Hboot_Downgrade | Tapatalk_HD_Beta | unofficial_AOKP_Oct11_[Tablet_UI] | Blackout_AOZP_s2w_Revised_Oct11_Kernel
[HTC One S] Darknites:
Or flash Elemental-S right after.
[HTC One S] ryanshew:
Ya that too for JB, but he's talking about ICS Viper. I don't think either viper flashes the boot.img in the aroma script anyhow.

HTC_One_S | 1.06_Hboot_Downgrade | Tapatalk_HD_Beta | unofficial_AOKP_Oct11_[Tablet_UI] | Blackout_AOZP_s2w_Revised_Oct11_Kernel
[HTC One S] Darknites:
Dam it I even told him to try the ICS one too, I should of known:(.
[HTC One S] 2rz_taco_sr5:
The phone I had replaced had 1.11t that I flashed to it then both the replacements came with 1.11t... my original phone came with 1.06 hboot and had no problems both the replacement phones came with 1.14 and when I downgraded the first one I then installed a fresh viper rom. When I noticed the horrible call quality I got the replacement replaced thinking it was the phone. I tested the new one and it was fine so I thought I was good and downgraded it. Well right after that its now horrible too and the first replacement was fixed as soon as I flashed the ruu... I think the older hboot just doesn't agree with the newer replacement phones. I may run the ruu to get the higher hboot back the just flash a rom and see what happens... Very weird.
[HTC One S] Darknites:
Does it go bad with just the downgrade?
[HTC One S] ryanshew:
Oh, well try a different radio, that's what was suggested before, not to reflash the one you already had. I've seen people complaining about call quality with that one, try the regular 1.11 or 1.09ts.

Here's links to them in my Dropbox. These are flashable .zips, just flash then in recovery;

1.09ts:

http://db.tt/JNStrv3a

1.11:

http://db.tt/TCjI30Im

HTC_One_S | 1.06_Hboot_Downgrade | Tapatalk_HD_Beta | unofficial_AOKP_Oct11_[Tablet_UI] | Blackout_AOZP_s2w_Revised_Oct11_Kernel
[HTC One S] Phantom Pt. II:
Hi. Ignore this. Here's a free hug:

[hug]
[HTC One S] pnut22r:
Thank you, thank you, thank you. I thought I was crazy. Then I started to think, it can't even be flashing the boot.img. of course all of us are smart enough to go check the updater script to see, but of course I didn't. Well I'm not crazy, and I feel so much better now.

For good measure, even though I have 1.09, I'm still going to use flash image gui, but at least I don't HAVE to all the time, in case something blows up and I need to quick flash something.

Thanks everyone for your help.
[HTC One S] 2rz_taco_sr5:
Sure ill give it a try I have several other radios i can try just weird cause that's the radio that i had flashed on my original phone that came with 1.06 and it was already on both the replacement phones too and worked fine before the downgrade so idk why only after the downgrade it would now cause a problem but ill try a new radio and a fresh wipe and flash and ill get back with everyone I would have by now but had an emergency come up and went out of state the day I posted so its been tough but I appreciate the help.
[HTC One S] pnut22r:
i dont know if this is the place to post it or not, but i am currently downgraded to 1.09 and most of the time things work (aside from flashing any TeamVenom roms)

I can NEVER get a rom to restore. I wipe, restore, but it always bootloops when i reboot. What am i doing wrong. I have never had this much trouble with other phones (stupid s-on)

If you guys are going to restore a backup, what steps do you take? Also, i am using TWRP 2.4.1 (the latest)

I would think with hboot 1.09 things should be good.
[HTC One S] Darknites:
When I restore I do factory reset and then restore and then reboot.
[HTC One S] 2rz_taco_sr5:
did you run the boot.img script? You still have to do that. Having 1.09 means you can use the script if you were higher you would have to use the flash image GUI...
[HTC One S] pnut22r:
I'm so confused. Can I just flash anything straight up? Without having too flash the boot.img separately?

1.09
[HTC One S] Darknites:
Ya you can but maybe Viper is picky and don't flash the boot.img but any other rom has flashed without using an app or fastboot.
[HTC One S] pnut22r:
Yeah. That's my experience. However, when making a backup of Virtuous Jb, then trying to restore, it doesn't restore. Unless I reflash the Rom after restoring. Then it works. Weird
[HTC One S] Darknites:
I use 2.3.3.0 so maybe try that one.
[HTC One S] pnut22r:
Yes. That worked, thank you.
[HTC One S] Darknites:
Oh dear so never updating ever again and I'm only 2.3 because I was lazy after test a newer build of CWM.
[HTC One S] fegato:
Do this hboot downgrade gives back the good old mass storage usb and remove the stupid MTP ?

I would do this just for this reason

thanks
[HTC One S] :
If you use a ROM that doesn't use MTP.
[HTC One S] Lacuna666:
Last step fails for me

Hi, I tried searching for the answer, but didn't find it:

All went well except the last step: 12.

The phone wont reboot, i tried holding down the power-knob, and the Qualcomm does dissapear, but it still wont continue after letting go

The Qualcomm re-appears then

I should mention, that i wasnt 100% sure about this part:

The step where you have to look "where your device is located", im assuming that its sdk in my case ?

ls /dev/sd*

/dev/sda /dev/sdf /dev/sdk1 /dev/sdk17 /dev/sdk24 /dev/sdk31 /dev/sdk6

/dev/sda1 /dev/sdg /dev/sdk10 /dev/sdk18 /dev/sdk25 /dev/sdk32 /dev/sdk7

/dev/sda2 /dev/sdg1 /dev/sdk11 /dev/sdk19 /dev/sdk26 /dev/sdk33 /dev/sdk8

/dev/sda3 /dev/sdg2 /dev/sdk12 /dev/sdk2 /dev/sdk27 /dev/sdk34 /dev/sdk9

/dev/sdb /dev/sdh /dev/sdk13 /dev/sdk20 /dev/sdk28 /dev/sdk35

/dev/sdc /dev/sdi /dev/sdk14 /dev/sdk21 /dev/sdk29 /dev/sdk36

/dev/sdd /dev/sdj /dev/sdk15 /dev/sdk22 /dev/sdk3 /dev/sdk4

/dev/sde /dev/sdk /dev/sdk16 /dev/sdk23 /dev/sdk30 /dev/sdk5

So when i applied the command: in step 9, i used

sudo ./emmc_recover -f ./hboot.nb0 -d /dev/sdk 12 -c 24576

Any ideas ?

Thanks

Step 12:

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] Darknites:
Could try rebooting the pc.
[HTC One S] Phonebricker:
I dont get this part

2. Download adb and enable USB debugging (adb is in the android SDK, or search Google for a download)

if we're running a Linux live cd, what to we do with the adb we downloaded?
[HTC One S] Darknites:
Not sure for LiveCD but if you try to use adb it will then ask if you want to install it.
[HTC One S] Lacuna666:
Yes I did, no effect, still the same result
[HTC One S] Lacuna666:
Could somebody please confirm that I chose the right letter : k , I only see people talking about c and d, i would just like to rule that part out.

sudo ./emmc_recover -f ./hboot.nb0 -d /dev/sdk 12 -c 24576
[HTC One S] jac10000:
Yes , for you it's sdk12 and after sdk4 for the other command line
[HTC One S] Lacuna666:
Thanks
[HTC One S] Lacuna666:
ok thanks guys, got it working now!
[HTC One S] Phonebricker:
Can someone please explain to me how to install adb from the android sdk tools if i am running Ubuntu from a LIVE cd?
[HTC One S] ryanshew:
You don't really need adb, you could just drag and drop the file.

I never once used adb for this procedure.

HTC_One_S | 1.06_Hboot_Downgrade | Modified_4.2.1_AOKP_Jellybam.zip | Komodo_Kernel
[HTC One S] Phonebricker:
On the very first command "$ adb shell" it's asking me for adb when I press enter. Should I just skip that command and start with "su"

Crap, to top it off, when i SU, its asking for a password. what is the password. Damn I must be doing this the hard way.
[HTC One S] Darknites:
First part is done on phone and the password when asked is your user password.
[HTC One S] Phonebricker:
Well, Hell... that explains alot! Damn, sometimes I feel like an idiot. Im guessing I only begin to use Linux at the part where the instructions call for me to open 3 terminal windows.
[HTC One S] ryanshew:
Correct, in terminal emulator. Once the bakp4 it's extracted, hook phone to pc, mount, and drag and drop file to a safe place on pc.

HTC_One_S | 1.06_Hboot_Downgrade | Modified_4.2.1_AOKP_Jellybam.zip | Komodo_Kernel
[HTC One S] Bloodbreed:
Hello people,

Does this work on the one x too ?

My trouble is that i messed my partition permission when i flashed a kernel and can t really copy something to sdcard.

I suppose that i need to enter apx mode with killp4 but that won t work because of those permissions.

Is there an other way to enter apx mode ?
[HTC One S] Phonebricker:
Ok, I get all the way to the last step and it tells me "please blacklist qcserial module" what happened?

Edit: nevermind I got it. I had to repeat

$ sudo modprobe -r qcserial

$ sudo mknod /dev/ttyUSB0 c 188 0

then try the last step again.
[HTC One S] xDC23:
followed all steps correctly, now its hanging at waiting device /dev/sdc12......

i tried holding the power button and it won't do anything.

edit: nevermind saw my mistake

ok corrected my mistake and it still hangs at waiting device
[HTC One S] k1llacanon:
I'm on jb 1.12 hboot I think that's what it's called does this mean I can't do this?
[HTC One S] mikeyinid:
Bahaha. Love it
[HTC One S] vietlong3:
yes, i install Ubuntu 12.04 64 bit
[HTC One S] dc211:
:eek: Are you sure? That screen shoot sure as hell looks like windows device manager.
[HTC One S] hicdub:
After this step, do you HAVE to run an ruu? I am on T-Mobile USA.

What did you do after this step Mikey? Aren't you tmous as well?
[HTC One S] GrimTG:
No RUU needed. I'm T-mobile. Just restart the phone normally

Sent from the shadows
[HTC One S] mikeyinid:
My phone stayed at a black screen. Hold down the power button until the screen flickers then hold volume down to boot to bootloader. Then hit reboot there and you'll be in business
[HTC One S] usaff22:
It definitely is