Database Develop

[Q] [HELP] FastBoot unroot.

Hey!
So I just got my HTC One yesterday and I'm currently stock on the HTC logo boot screen. I spent the last 2 days on the internet trying to figure out how to fix that issues. It seems that the phone doesn't have any Rom or firmware install on it. I kind don't know how everything work. I don't mind if my phone is root or unroot all I want is to make it work. I followed different method on Youtube none of the seem to work. From what I know it seems that the device is a Rogers device but when I try to unroot it I got a 12 signature fail. Every other thread have broken links and kinda don't fix my issues. Please help me I'm really desperate.
Thank you,

Can you access the boot loader?
Is it locked or unlocked?
Do you have a custom recovery?
What were you trying to do when you got stuck in the bootloop?
The more info you can give us the more we can help.
Sent from my HTC One using XDA Premium 4 mobile app

Hey Cory!
Thanks for answering to my post.
To answer your question,
Yes I do have access to bootloader, fastboot and recovery.
I can use command on my pc to run some fastboot command also.
When I try to use recovery I got stuck at the red triangle alert.
I do not have any backup of my device. Also I dont have Cwm on the device.
It looks like a completely emptu phone. i cant even manage to use it as a disk mode to put a file on it.
I was only trying to unroot it to put back the android stock that came with the HTC One when you purchase it.
Also at the moment I'm able to unlock or lock the device.
Thanks for your help. i have to be honest I'm noob with android.
Thanks,

vedgebill said:
Hey Cory!
Thanks for answering to my post.
To answer your question,
Yes I do have access to bootloader, fastboot and recovery.
I can use command on my pc to run some fastboot command also.
When I try to use recovery I got stuck at the red triangle alert.
I do not have any backup of my device. Also I dont have Cwm on the device.
It looks like a completely emptu phone. i cant even manage to use it as a disk mode to put a file on it.
I was only trying to unroot it to put back the android stock that came with the HTC One when you purchase it.
Also at the moment I'm able to unlock or lock the device.
Thanks for your help. i have to be honest I'm noob with android.
Thanks,
Click to expand...
Click to collapse
can you go to fastboot, and then run "fastboot getvar all", and post the results here to see the details of your device (remove the IMEI and serial number before posting)

nkk71 said:
can you go to fastboot, and then run "fastboot getvar all", and post the results here to see the details of your device (remove the IMEI and serial number before posting)
Click to expand...
Click to collapse
Here's what I got
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.631.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Any Idea what I can do to make it work?
Thanks,

There's a Nandroid backup you can use here:
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-roger001-1-29-631-17-2013-06-03-zip/

Can you help with a step by step how to restore?

There are guides on here already so just read them

EddyOS said:
There are guides on here already so just read them
Click to expand...
Click to collapse
Sorry I'm really bad with forums. Any guides in particular cuz I cant find the right one there too many.
Thanks I really appreciate

How about the nice, big, sticky thread in General?
http://forum.xda-developers.com/showthread.php?t=2358738
Search properly next time

So I manage to have clockworkmode on my HTC One.
I'm not stuck at the point of putting a firmware. I don't mind which one I just want my phone to work.
Bootloader is Unlocked.
When I plug the device to my computer I can't manage to put anything on it and dab doesn't seems to work properly.
I'm a noob so maybe I don't do it properly.
Thanks,

If you're a n00b why did you even attempt it in the first place? Surely you should know what you're doing before jumping in blind?

Actually the reason why I jump into it is cuz I got it from a friends for a couple of hundred dollar and it was like that.
I'm just trying to fix it and also try to understand and learn.
But thanks for the comment

If you manages to get cwm working you can adb push a ROM.
Download any stock ROM from the android development section of the One.
Android Revolution HD or InsertCoin are two favorites.
Put the .zip file in the same folder as your adb and fastboot files. I'm assuming you got adb and fastboot set up since you have cwm now, if not I can elaborate.
Rename the file rom.zip.
Open a command prompt in the folder that has adb and fastboot.
(Hold shift and right click, select open command prompt here)
Connect the phone while its booted into recovery.
Type "adb devices"
You should see your phones serial and the word recovery.
Now type "adb push rom.zip /sdcard/"
It will look like its frozen, leave it alone, it can take up to fifteen minutes or more.
Eventually it will tell you its done.
Unplug the phone and select full wipe or factory reset (inside cwm, not in the boot loader).
Also wipe both caches under advanced wipe.
Select flash or install from SD card, and pick ROM.zip.
Let it do its magic, or follow the prompts if it has an aroma installer. The more mods you choose, the farther from stock it will be, and the more likely it is to have bugs.
Good luck.
Sent from my HTC One using XDA Premium 4 mobile app

Help with Sim-Unlock

Hi all,
I have the revolution HD Rom installed on my device and I got an unlock code online from a site I trust and bought from in the past (I say that to point out that I don't think that the problem is with the key itself)
When I tried to apply it though, it said that it is wrong...
I know it sounds weird, but my research shows that it might be related to me having a custom rom installed - something about changing the baseband?
Either way, I'd love for some community help on this - is this possible?
If so, what is the quickest/painless way to get back to stock? will that require a full factory reset?
will I lose the unlock again when I switch back to the rom?
Please help as I'm currently out of the country and have no phone
Thanks!!!

eladkatz said:
Hi all,
I have the revolution HD Rom installed on my device and I got an unlock code online from a site I trust and bought from in the past (I say that to point out that I don't think that the problem is with the key itself)
When I tried to apply it though, it said that it is wrong...
I know it sounds weird, but my research shows that it might be related to me having a custom rom installed - something about changing the baseband?
Either way, I'd love for some community help on this - is this possible?
If so, what is the quickest/painless way to get back to stock? will that require a full factory reset?
will I lose the unlock again when I switch back to the rom?
Please help as I'm currently out of the country and have no phone
Thanks!!!
Click to expand...
Click to collapse
You can either restore a nandroid of your stock ROM or flash an RUU. Try your code again after going to stock and it'll work.

eladkatz said:
Hi all,
I have the revolution HD Rom installed on my device and I got an unlock code online from a site I trust and bought from in the past (I say that to point out that I don't think that the problem is with the key itself)
When I tried to apply it though, it said that it is wrong...
I know it sounds weird, but my research shows that it might be related to me having a custom rom installed - something about changing the baseband?
Either way, I'd love for some community help on this - is this possible?
If so, what is the quickest/painless way to get back to stock? will that require a full factory reset?
will I lose the unlock again when I switch back to the rom?
Please help as I'm currently out of the country and have no phone
Thanks!!!
Click to expand...
Click to collapse
You posted in the wrong section. That's what Q&A is for.
Sent from my HTC One using XDA Premium 4 mobile app

gamer765 said:
You can either restore a nandroid of your stock ROM or flash an RUU. Try your code again after going to stock and it'll work.
Click to expand...
Click to collapse
Thanks for the reply man, I was going to follow the instructions on http://forum.xda-developers.com/showthread.php?t=2265618 but they link to more info on RUUs and the link is broken
How do I know which ruu do I need?
Thanks again!

eladkatz said:
Thanks for the reply man, I was going to follow the instructions on http://forum.xda-developers.com/showthread.php?t=2265618 but they link to more info on RUUs and the link is broken
How do I know which ruu do I need?
Thanks again!
Click to expand...
Click to collapse
What region is the phone from and what carrier? It's probably better if you can post your CID, which you can obtain by using the CID Getter app on the play store.

gamer765 said:
What region is the phone from and what carrier? It's probably better if you can post your CID, which you can obtain by using the CID Getter app on the play store.
Click to expand...
Click to collapse
I have a US AT&T phone, my CID is CWS_001
Thanks

eladkatz said:
I have a US AT&T phone, my CID is CWS_001
Thanks
Click to expand...
Click to collapse
You don't need to do all that, just use a Guru Reset ROM for your firmware, that will work (confirmed from several other users, with the same situation as yours). can you post a "fastboot getvar all" (remove IMEI and s/n) and I'll point you in the right direction

eladkatz said:
I have a US AT&T phone, my CID is CWS_001
Thanks
Click to expand...
Click to collapse
Just restore a stock AT&T nandroid and you should be good to go. Afterwards, you can install custom ROMs, your unlock will stick.
EDIT: You can restore this nandroid http://www.htc1guru.com/dld/htcone-32gb-att-1-26-502-10-twrp-stock-zip/
Make a nandroid of your current ROM first if you want to return to it afterwards. The above is a TWRP nandroid.

nkk71 said:
You don't need to do all that, just use a Guru Reset ROM for your firmware, that will work (confirmed from several other users, with the same situation as yours). can you post a "fastboot getvar all" (remove IMEI and s/n) and I'll point you in the right direction
Click to expand...
Click to collapse
Thanks, see below, not sure if it worked...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4082mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.041s

eladkatz said:
Thanks, see below, not sure if it worked...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4082mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.041s
Click to expand...
Click to collapse
Try this one: http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-12-zip/
It's slightly newer than your version but I think it should work, you can deselect "stock recovery" and "stock radio" during the install, as you won't need those.
BTW: why don't you S-Off? (just a question, I'm in no way implying you do anything you're not comfortable with!!)

gamer765 said:
Just restore a stock AT&T nandroid and you should be good to go. Afterwards, you can install custom ROMs, your unlock will stick.
EDIT: You can restore this nandroid http://www.htc1guru.com/dld/htcone-32gb-att-1-26-502-10-twrp-stock-zip/
Make a nandroid of your current ROM first if you want to return to it afterwards. The above is a TWRP nandroid.
Click to expand...
Click to collapse
I have clockwork mod recovery, can I use that to do the twrp nandroid recovery?
Also, in the url you are directing to, it says:
This Nandroid should not be needed. I have
a Stock ROM + Recovery Reset Installer which can
reset stock ROM and allow OTA updates. See Here:
http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-12-zip
Click to expand...
Click to collapse
Should I use that one instead?

eladkatz said:
I have clockwork mod recovery, can I use that to do the twrp nandroid recovery?
Also, in the url you are directing to, it says:
Should I use that one instead?
Click to expand...
Click to collapse
Sorry, I didn't get your question, and lots of different approaches to the same thing. If you want my opinion:
1- do a nandroid backup of your current setup
2- copy (or pull) everything to your PC, just in case
3- use the Guru Reset (http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-12-zip/), that's a flashable zip in custom recovery, do not select "stock recovery" (actually you have to uncheck it)
4- do not take any OTAs
5- use your SIM unlock code
6- restore your nandroid backup
if in step 5 the SIM unlock code doesn't work, then you can explore other options
That's my humble opinion.
Hit the Thanks button if I've helped

nkk71 said:
BTW: why don't you S-Off? (just a question, I'm in no way implying you do anything you're not comfortable with!!)
Click to expand...
Click to collapse
I guess because I'm not sure what that is, I've seen it mentioned as something that allowes to install custom RUUs but I'm not sure how that would help here...

eladkatz said:
I guess because I'm not sure what that is, I've seen it mentioned as something that allowes to install custom RUUs but I'm not sure how that would help here...
Click to expand...
Click to collapse
I guess the stock reset is fine, the main goal is to get you back to the stock carrier ROM for the unlock code to work.

nkk71 said:
Sorry, I didn't get your question, and lots of different approaches to the same thing. If you want my opinion:
1- do a nandroid backup of your current setup
2- copy (or pull) everything to your PC, just in case
3- use the Guru Reset (http://www.htc1guru.com/dld/guru_reset_m7_1-26-502-12-zip/), that's a flashable zip in custom recovery, do not select "stock recovery" (actually you have to uncheck it)
4- do not take any OTAs
5- use your SIM unlock code
6- restore your nandroid backup
if in step 5 the SIM unlock code doesn't work, then you can explore other options
That's my humble opinion.
Hit the Thanks button if I've helped
Click to expand...
Click to collapse
Thanks for the tip,
I followed the instructions to the letter and now it seems like I'm stuck on the HTC ONE boot screen...
I tried restarting once (after letting it idle for a good 10 minutes I think)
now I'm just staring at it, not really sure what my next step should be... could it just be that I need to wait?
On a positive note, I can still access fastboot/recovery so I guess worst case, I can do a factory reset - that oughta fix it, right?
Question about that - if I do that, will I still be able to do the nandroid restore and go back to my original state?
Thanks

eladkatz said:
Thanks for the tip,
I followed the instructions to the letter and now it seems like I'm stuck on the HTC ONE boot screen...
I tried restarting once (after letting it idle for a good 10 minutes I think)
now I'm just staring at it, not really sure what my next step should be... could it just be that I need to wait?
Click to expand...
Click to collapse
What's up with that, 2nd person today (out of 2) having problems with the Guru Resets
did you wipe in the Installer? did you make sure the download is not corrupt (MD5 sum)?
The way I usually know if the bootup is stuck or not, is: after a few minutes (something like 2 or 3 minutes, maybe less) the screen will change brightness, if it does I know it's not stuck, if the brightness doesn't change, I force a reboot and reflash.
I recommend you reboot to recovery, and restore your backup, just to have a functioning phone, then check the MD5 sum of your download to make sure it's OK.
I'm about to flash the Guru Reset that also got the other guy "stuck", to see if it works or not....

eladkatz said:
Thanks for the tip,
I followed the instructions to the letter and now it seems like I'm stuck on the HTC ONE boot screen...
I tried restarting once (after letting it idle for a good 10 minutes I think)
now I'm just staring at it, not really sure what my next step should be... could it just be that I need to wait?
On a positive note, I can still access fastboot/recovery so I guess worst case, I can do a factory reset - that oughta fix it, right?
Question about that - if I do that, will I still be able to do the nandroid restore and go back to my original state?
Thanks
Click to expand...
Click to collapse
FYI: http://forum.xda-developers.com/showpost.php?p=47085377&postcount=44
(it's a different Guru Reset, but same principle applies)

nkk71 said:
FYI: http://forum.xda-developers.com/showpost.php?p=47085377&postcount=44
(it's a different Guru Reset, but same principle applies)
Click to expand...
Click to collapse
I eventually just restored to factory defaults, proceeded to unlock and then went back to the nandroid backup, worked like a charm!
Thanks for all the help and support

[ON HOLD] Stuck in boot screen (not bootloader, rooted)

Hi, after searching through many posts and trying different things which didn't solve my problem for ours, I decided to just ask...
I have a rooted HTC (Switzerland / Europe version) and I tried to unroot it with different "europe" RUU's from this forum, none worked but I saw in the comments that some of those RUU's required S-OFF. So without any experience whatsoever my mastermind decided to just give it a try and turn S-OFF with the moonshine method. I guess I chose the wrong file (again?) and it didnt work, it always ran 10 restarts in the moonshine method at the end and then the error message "don't drink and shine" popped up. So I gave up and just started the phone.
After starting, I realised that the WIFI and the camera wasn't working anymore (tried all I could) and again I came to this forum and looked for solutions. I tried to wipe everything on the phone, including data wipe and all the wiped I found in twrp. After I did that, I chose the option reboot and well, the phone didnt shut off anymore and I was stuck in the starting screen ( HTC - quitly brilliant -- with the text below: this build is for development....) I tried all the shut down methods with sound button down and so on, also to keep a fleshlight on it (found: http://forum.xda-developers.com/showthread.php?t=2418404 )
I don't know what else to do and I'm pretty much lost. I shouldn't have tried all this without the knowledge damn -.-
please help!

Enion said:
Hi, after searching through many posts and trying different things which didn't solve my problem for ours, I decided to just ask...
I have a rooted HTC (Switzerland / Europe version) and I tried to unroot it with different "europe" RUU's from this forum, none worked but I saw in the comments that some of those RUU's required S-OFF. So without any experience whatsoever my mastermind decided to just give it a try and turn S-OFF with the moonshine method. I guess I chose the wrong file (again?) and it didnt work, it always ran 10 restarts in the moonshine method at the end and then the error message "don't drink and shine" popped up. So I gave up and just started the phone.
After starting, I realised that the WIFI and the camera wasn't working anymore (tried all I could) and again I came to this forum and looked for solutions. I tried to wipe everything on the phone, including data wipe and all the wiped I found in twrp. After I did that, I chose the option reboot and well, the phone didnt shut off anymore and I was stuck in the starting screen ( HTC - quitly brilliant -- with the text below: this build is for development....) I tried all the shut down methods with sound button down and so on, also to keep a fleshlight on it (found: http://forum.xda-developers.com/showthread.php?t=2418404 )
I don't know what else to do and I'm pretty much lost. I shouldn't have tried all this without the knowledge damn -.-
please help!
Click to expand...
Click to collapse
If you can restart and get into bootloader by holding power and vol. down, flash TWRP, put your RUU zip on your phone storage, and then flash it.

kibmikey1 said:
If you can restart and get into bootloader by holding power and vol. down, flash TWRP, put your RUU zip on your phone storage, and then flash it.
Click to expand...
Click to collapse
Hi, thanks for your advice. The problem is that, after recharging the phone again and trying several times, I just can't get into bootloader. When I hold the power button and vol. down the home and "arrow" touch-buttons at the bottom of the phone just start blinking. As long as I hold these two buttons the blinking doesn't stop, I did hold them for a full minute and nothing happend on the screen itself. After releasing the blinking stopped but the screen remained on it's state...

Enion said:
Hi, thanks for your advice. The problem is that, after recharging the phone again and trying several times, I just can't get into bootloader. When I hold the power button and vol. down the home and "arrow" touch-buttons at the bottom of the phone just start blinking. As long as I hold these two buttons the blinking doesn't stop, I did hold them for a full minute and nothing happend on the screen itself. After releasing the blinking stopped but the screen remained on it's state...
Click to expand...
Click to collapse
Blinking is good, just hold POWER + VOLDOWN with the phone sensors under a bright light (not kidding!!), it should reboot after 30sec to 2 minute. If it doesn't reboot, let go and try again; the bright light is important!!
Once it reboots, keep holding VOLDOWN so it reboots to bootloader.

Thank you guys, I tried it and it strangely worked (literally 2minutes with a light on it). I'm in the bootloader now and will try to
flash TWRP, put your RUU zip on your phone storage, and then flash it.
Click to expand...
Click to collapse
as kibmikey1 wrote. I hope I'll find the right files and manuals this time. Will report back

Enion said:
Thank you guys, I tried it and it strangely worked (literally 2minutes with a light on it). I'm in the bootloader now and will try to as kibmikey1 wrote. I hope I'll find the right files and manuals this time. Will report back
Click to expand...
Click to collapse
You can't flash a RUU zip through recovery.
Most important question: What's your final goal?? Where do you want to get with your phone??
also post a "fastboot getvar all" (remove IMEI and s/n), and date of bootloader.
PS: hit the thanks button if we helped

nkk71 said:
You can't flash a RUU zip through recovery.
Most important question: What's your final goal?? Where do you want to get with your phone??
also post a "fastboot getvar all" (remove IMEI and s/n), and date of bootloader.
PS: hit the thanks button if we helped
Click to expand...
Click to collapse
Didn't know about the thank you, my bad there.
My final goal is to have an up-to-date phone. I couldn't update my phone while it was rooted and therefore tried to unroot it and ran into all these complications.
I tried the command you wrote and the result was:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
thanks!

Enion said:
Didn't know about the thank you, my bad there.
My final goal is to have an up-to-date phone. I couldn't update my phone while it was rooted and therefore tried to unroot it and ran into all these complications.
I tried the command you wrote and the result was:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH35xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
thanks!
Click to expand...
Click to collapse
hey mate, edit your post and remove IMEI and s/n we don't need to see those.
can you confirm your hboot is dated before June 2013. I'll post your options after that

Hi, thanks for noticing, I removed it, please dit your post aswell
If you're talking about the date at the top of the bootloader, it says May 3

Enion said:
Hi, thanks for noticing, I removed it, please dit your post aswell
Click to expand...
Click to collapse
I already did when quoting you, changed them all to XXXXXXXXXXX, or is it showing up on your computer?
Enion said:
If you're talking about the date at the top of the bootloader, it says May 3
Click to expand...
Click to collapse
gimme a few minutes while I write down all the options
BTW: Easy on the thanks button, you only have 8 per day

nkk71 said:
I already did when quoting you, changed them all to XXXXXXXXXXX, or is it showing up on your computer?
gimme a few minutes while I write down all the options
BTW: Easy on the thanks button, you only have 8 per day
Click to expand...
Click to collapse
My bad again, it doesn't show up. I need to learn to read the forum rules first before posting stuff I guess.

Enion said:
My bad again, it doesn't show up. I need to learn to read the forum rules first before posting stuff I guess.
Click to expand...
Click to collapse
Code:
(bootloader) version-bootloader: 1.44.0000 (May 3)
(bootloader) version-main: 1.29.161.16
OK, so you have two primary choices:
A) Stay S-On
B) Get S-Off: with the above hboot and firmware, you can easily get s-off using revone
Now, with an unlocked bootloader but S-ON, you can
---- flash custom or stock ROM
---- flash different radios (ie baseband)
---- flash custom kernel
---- flash custom recovery
you cannot:
---- you cannot flash unsigned firmware
---- you cannot downgrade (firmware and hboot)
---- you cannot remove TAMPERED
---- you cannot LOCKED your phone, at best it will say RELOCKED
---- you cannot run a downgrade RUU
With S-Off, you can do ALL of these and more, e.g. you can reset your phone to 100% out-of-the box, and you can even change your phone from a Vodafone phone to ANY other variant (eg unbranded European, US Developer, 100% Google Play Edition, etc.)
I'm in no way encouraging you to go S-Off, unless YOU are comfortable with the thought and procedure.
If you're looking at always having the latest releases, then I personally would stick with custom ROMs, these get updated way quicker (even if sometimes based on a leak), than carrier dependent OTAs.
Should you stay S-On, the only way to upgrade the firmware, will be using an official Vodafone OTA, in one of two methods:
1- go back to stock rom & stock recovery, download and install, and then reinstall custom ROM
2- get your hands on the OTA file (either by downloading it yourself, or if you find it on the net), then extract "firmware.zip" and flash it in fasboot RUU mode (this will work cause the OTA contains a signed firmware specifically for your phone)
[and you cannot downgrade if for some reason you would want to]
On the other hand, if you are S-Off, you can use an unsigned firmware package found in various threads.
Ok, that's enough for now, even my head is spinning LOL.
Let me know what you think, and if you need more explanations. Then rethink your ultimate goal, and we can proceed from there.
(Now all this writing deserves a thanks )

nkk71 said:
Code:
(bootloader) version-bootloader: 1.44.0000 (May 3)
(bootloader) version-main: 1.29.161.16
OK, so you have two primary choices:
A) Stay S-On
B) Get S-Off: with the above hboot and firmware, you can easily get s-off using revone
Now, with an unlocked bootloader but S-ON, you can
---- flash custom or stock ROM
---- flash different radios (ie baseband)
---- flash custom kernel
---- flash custom recovery
you cannot:
---- you cannot flash unsigned firmware
---- you cannot downgrade (firmware and hboot)
---- you cannot remove TAMPERED
---- you cannot LOCKED your phone, at best it will say RELOCKED
---- you cannot run a downgrade RUU
With S-Off, you can do ALL of these and more, e.g. you can reset your phone to 100% out-of-the box, and you can even change your phone from a Vodafone phone to ANY other variant (eg unbranded European, US Developer, 100% Google Play Edition, etc.)
I'm in no way encouraging you to go S-Off, unless YOU are comfortable with the thought and procedure.
If you're looking at always having the latest releases, then I personally would stick with custom ROMs, these get updated way quicker (even if sometimes based on a leak), than carrier dependent OTAs.
Should you stay S-On, the only way to upgrade the firmware, will be using an official Vodafone OTA, in one of two methods:
1- go back to stock rom & stock recovery, download and install, and then reinstall custom ROM
2- get your hands on the OTA file (either by downloading it yourself, or if you find it on the net), then extract "firmware.zip" and flash it in fasboot RUU mode (this will work cause the OTA contains a signed firmware specifically for your phone)
[and you cannot downgrade if for some reason you would want to]
On the other hand, if you are S-Off, you can use an unsigned firmware package found in various threads.
Ok, that's enough for now, even my head is spinning LOL.
Let me know what you think, and if you need more explanations. Then rethink your ultimate goal, and we can proceed from there.
(Now all this writing deserves a thanks )
Click to expand...
Click to collapse
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward

Enion said:
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Click to expand...
Click to collapse
No problem mate, remember for revone to work your firmware is good ((bootloader) version-main: 1.29.161.16), but you will need a ROM based on 4.1.2 preferably (I have one - which worked for me and two others) in case you can't find one.
Also read here: http://forum.xda-developers.com/showthread.php?t=2431515
here: http://forum.xda-developers.com/showthread.php?t=2365506
and of course: http://forum.xda-developers.com/showthread.php?t=2314582
Let me know if you need any more help.
Once you are S-Off, you can easily upgrade/downgrade firmware in @vomer's guide (same as before, but down in the firmware section): http://forum.xda-developers.com/showthread.php?t=2365506

Enion said:
Thanks for the help. I will try to get S-Off then. I hope I can do it this time though. I'll report when I get it Off or need help again. Looking forward
Click to expand...
Click to collapse
Hey @Enion, you all good now?

nkk71 said:
Hey @Enion, you all good now?
Click to expand...
Click to collapse
Hi, sry for the late reply, didn't have much time today. I flashed the rom (4.2.1) that nkk71 gave me in a PM and the phone is working just fine now. I decided to just stay in this state for the moment and think about getting S-Off later. I want to thank everyone involved in this thread and especially nkk71, really quick & reliable message board.
//Enion

Enion said:
Hi, sry for the late reply, didn't have much time today. I flashed the rom (4.2.1) that nkk71 gave me in a PM and the phone is working just fine now. I decided to just stay in this state for the moment and think about getting S-Off later. I want to thank everyone involved in this thread and especially nkk71, really quick & reliable message board.
//Enion
Click to expand...
Click to collapse
I know what you mean, just got back from work myself, and didnt have a minute to scratch my head all day :silly:
Just for your info, it took me less than ten minutes to get S-Off using my setup (that ROM and firmware 1.28.61.7), worked like a charm from the first time.
Anyway, until you decide to do it, could you edit the main thread title to include something like [ON HOLD], I usually prefer [SOLVED], but [ON HOLD] should do for now, until you revive your thread

nkk71 said:
I know what you mean, just got back from work myself, and didnt have a minute to scratch my head all day :silly:
Just for your info, it took me less than ten minutes to get S-Off using my setup (that ROM and firmware 1.28.61.7), worked like a charm from the first time.
Anyway, until you decide to do it, could you edit the main thread title to include something like [ON HOLD], I usually prefer [SOLVED], but [ON HOLD] should do for now, until you revive your thread
Click to expand...
Click to collapse
I tried to set in "on hold" but I think I'm missing some rights in this forum, it just doesn't work. I tried http://forum.xda-developers.com/showthread.php?p=27117213 this method aswell.

Enion said:
I tried to set in "on hold" but I think I'm missing some rights in this forum, it just doesn't work. I tried http://forum.xda-developers.com/showthread.php?p=27117213 this method aswell.
Click to expand...
Click to collapse
didnt read the the link you sent, usually you just go to the first post, click EDIT then at the bottom of the edit window, click GO ADVANCED and it would show the main thread title.
anyway don't worry about, most people (unfortunately) never bother to [CLOSE] [SOLVED] etc. no wonder the forum is hard to navigate through
take care
---------- Post added at 07:29 PM ---------- Previous post was at 07:24 PM ----------
nkk71 said:
didnt read the the link you sent, usually you just go to the first post, click EDIT then at the bottom of the edit window, click GO ADVANCED and it would show the main thread title.
anyway don't worry about, most people (unfortunately) never bother to [CLOSE] [SOLVED] etc. no wonder the forum is hard to navigate through
take care
Click to expand...
Click to collapse
Thank you sir!

[Q] Active cmdline overflow, bootloop, can't access recovery/boot

Hello , My main goal before starting this whole process was to put the phone back to 100% stock, back to **LOCKED**, so that I could get my phone repaired under warranty.
My main problem came with that my HBOOT version was 1.57.0000 and "S-On".
I have now come to this error in the FASTBOOT screen that says "Active cmdline overflow!" after trying to install a stock rom on my phone after reading somewhere that a person had managed to obtain S-Off after putting a stock + bulletproof kernel and running Firewater.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.27.3263.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-660ef031
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have read countless threads about this error, attempted to flash countless recovery images to try and gain access back to recovery mode from FASTBOOT but I get the same error. Which is after attempting to access Recovery when having flashed a new recovery image, it tries to go in but loops back round to FASTBOOT screen with the same "Active cmdline overflow! (1025 Bytes)
If someone please, has any fix to this problem, I would be greatly appreciated.
If there is any information you need to know please ask!

Jimmyy9 said:
Hello , My main goal before starting this whole process was to put the phone back to 100% stock, back to **LOCKED**, so that I could get my phone repaired under warranty.
My main problem came with that my HBOOT version was 1.57.0000 and "S-On".
I have now come to this error in the FASTBOOT screen that says "Active cmdline overflow!" after trying to install a stock rom on my phone after reading somewhere that a person had managed to obtain S-Off after putting a stock + bulletproof kernel and running Firewater.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.27.3263.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4307mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-660ef031
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have read countless threads about this error, attempted to flash countless recovery images to try and gain access back to recovery mode from FASTBOOT but I get the same error. Which is after attempting to access Recovery when having flashed a new recovery image, it tries to go in but loops back round to FASTBOOT screen with the same "Active cmdline overflow! (1025 Bytes)
If someone please, has any fix to this problem, I would be greatly appreciated.
If there is any information you need to know please ask!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2739126

alray said:
http://forum.xda-developers.com/showthread.php?t=2739126
Click to expand...
Click to collapse
Hi thank you for your reply, unfortunately I have read this topic almost back to front and have tried every recovery image that was posted, but none have been successful in allowing me into recovery mode.

Jimmyy9 said:
Hi thank you for your reply, unfortunately I have read this topic almost back to front and have tried every recovery image that was posted, but none have been successful in allowing me into recovery mode.
Click to expand...
Click to collapse
then you'll probably need to send your phone for a motherboard replacement.

alray said:
then you'll probably need to send your phone for a motherboard replacement.
Click to expand...
Click to collapse
I was thinking this may come down to this. I know that my phone is still under warranty until April next year, however if I send this phone back to them in the state it is in surely they will throw it back at me saying it's been messed about with?
The current status of the phone is **Tampered** and **Unlocked**. I'm afraid I do not know the command to print the information from the top of FASTBOOT.

Jimmyy9 said:
I was thinking this may come down to this. I know that my phone is still under warranty until April next year, however if I send this phone back to them in the state it is in surely they will throw it back at me saying it's been messed about with?
The current status of the phone is **Tampered** and **Unlocked**. I'm afraid I do not know the command to print the information from the top of FASTBOOT.
Click to expand...
Click to collapse
If you already tried everything it the guide I have posted above then there is probably nothing more you can do. You can not remove TAMPERED and UNLOCKED flags from the bootloader screen with S-ON and this void your warranty. They will probably charge you to replace the main board.

alray said:
If you already tried everything it the guide I have posted above then there is probably nothing more you can do. You can not remove TAMPERED and UNLOCKED flags from the bootloader screen with S-ON and this void your warranty. They will probably charge you to replace the main board.
Click to expand...
Click to collapse
Thank you for your swift replies.
This further question goes beyond my knowledge of android development. Is there a way at all to make the device look like it is a hard brick to remove the evidence of Tampering and Unlocking? I can see this can be perceived as quite a bad thing to do morally, but I can see the coming quote from HTC for them to fix the motherboard as being quite high in price!

Jimmyy9 said:
Is there a way at all to make the device look like it is a hard brick to remove the evidence of Tampering and Unlocking?
Click to expand...
Click to collapse
With S-ON and not able to boot in recovery, I don't know how.

alray said:
With S-ON and not able to boot in recovery, I don't know how.
Click to expand...
Click to collapse
Thank you very much for your replies and help
I did see in this thread http://forum.xda-developers.com/showthread.php?t=2781953 that @nkk71 was able to fix what seems to be an exact copy of the problem I have here. However what nkk71 actually did is very vague since he assisted the person through PM/Teamviewer. It would be great to hear what fixed the problem!

Jimmyy9 said:
Thank you very much for your replies and help
I did see in this thread http://forum.xda-developers.com/showthread.php?t=2781953 that @nkk71 was able to fix what seems to be an exact copy of the problem I have here. However what nkk71 actually did is very vague since he assisted the person through PM/Teamviewer. It would be great to hear what fixed the problem!
Click to expand...
Click to collapse
Hi Jimmyy9,
unfortunately, it's a question of luck... i didnt post what we did, because it was (and still is) inclusive (otherwise i would have posted the solution).
in that particular instance, we were able to flash the noBCB recovery to the kernel partition and were able to access it.
i've tried the same (and a lot more) a couple of days ago, but without any success
it still eludes me what/when/why would allow a custom recovery to boot with S-ON on higher hboots, why it sometimes works, and most of the time it doesn't, so i really have very little to offer
unless you can get to a custom recovery (even a rooted ROM), i honestly can't help
just for info, i did a similar procedure on the HTC Butterfly S, but it also required an hboot downgrade to be able to get to recovery.
sorry, but unless you are able to get to any custom recovery or rooted ROM, i don't have any ideas

nkk71 said:
Hi Jimmyy9,
unfortunately, it's a question of luck... i didnt post what we did, because it was (and still is) inclusive (otherwise i would have posted the solution).
in that particular instance, we were able to flash the noBCB recovery to the kernel partition and were able to access it.
i've tried the same (and a lot more) a couple of days ago, but without any success
it still eludes me what/when/why would allow a custom recovery to boot with S-ON on higher hboots, why it sometimes works, and most of the time it doesn't, so i really have very little to offer
unless you can get to a custom recovery (even a rooted ROM), i honestly can't help
just for info, i did a similar procedure on the HTC Butterfly S, but it also required an hboot downgrade to be able to get to recovery.
sorry, but unless you are able to get to any custom recovery or rooted ROM, i don't have any ideas
Click to expand...
Click to collapse
Thank you for the detailed reply. I had been up for 30+ hours finding fixes and reading information regarding bricking phone and how to restore them. So my situation now is to either send it back to HTC repairs and confess to them I bricked my phone and cough up the costs for them to fix it,
Or
Attempt to fix the corrupt binary which I understand is the "misc" partition. I do however understand this may not be possible without s-off or recovery access. My only option would be if there existed a RUU h-boot 1.57 exploit? It might also be interesting to test the recovery img you used to fix the previous problem, obviously this is getting into desperation but I'm willing to try absolutely everything before I give in to sending HTC a bricked phone to fix.

Jimmyy9 said:
Thank you for the detailed reply. I had been up for 30+ hours finding fixes and reading information regarding bricking phone and how to restore them. So my situation now is to either send it back to HTC repairs and confess to them I bricked my phone and cough up the costs for them to fix it,
Or
Attempt to fix the corrupt binary which I understand is the "misc" partition. I do however understand this may not be possible without s-off or recovery access. My only option would be if there existed a hboot 1.57 exploit? It might also be interesting to test the recovery img you used to fix the previous problem, obviously this is getting into desperation but I'm willing to try absolutely everything before I give in to sending HTC a bricked phone to fix.
Click to expand...
Click to collapse
fixing the misc partition, doesn't actually require s-off, just "somewhere" where you have access to "dd" partitions.... the problem is that [adb commands with root and busybox], are only available in:
* a booted rooted ROM with USB debugging enabled
or
* a custom recovery
unfortunately, (at least to the best of my knowledge and efforts), fastboot is not able to flash to the misc partition... i tried a lot of different things, but could not get fastboot to flash to the misc.
as i mentioned, a couple of days ago, i spent a good 3 to 4 hours on teamviewer with another user in the same situation as yours (except he had an international unbranded edition, which has a lot more signed firmwares than your model), and we went through a lot of permutations to try to get somewhere but unfortunately with no success
maybe if i have some time over the weekend, i'll do a teamviewer session with you, but i fear it will also end up in failure
if there is somebody close to you who has a jtag (or other hardware), i guess this could be fixed easily, but with software only there are only so many things you can do.

nkk71 said:
fixing the misc partition, doesn't actually require s-off, just "somewhere" where you have access to "dd" partitions.... the problem is that [adb commands with root and busybox], are only available in:
* a booted rooted ROM with USB debugging enabled
or
* a custom recovery
unfortunately, (at least to the best of my knowledge and efforts), fastboot is not able to flash to the misc partition... i tried a lot of different things, but could not get fastboot to flash to the misc.
as i mentioned, a couple of days ago, i spent a good 3 to 4 hours on teamviewer with another user in the same situation as yours (except he had an international unbranded edition, which has a lot more signed firmwares than your model), and we went through a lot of permutations to try to get somewhere but unfortunately with no success
maybe if i have some time over the weekend, i'll do a teamviewer session with you, but i fear it will also end up in failure
if there is somebody close to you who has a jtag (or other hardware), i guess this could be fixed easily, but with software only there are only so many things you can do.
Click to expand...
Click to collapse
I appreciate you offering your free time to help with my problem but if you think it will produce the same results as your previous tests then I wouldn't want you to waste your time. I have heard about this JTag process and it looks very convincing @ www.funphoneshop.com.
I see 2 paths.
The first would be to go with the JTag process and hope that it works (since m7 is not listed on their model list)
or
Seeing as my phone is still under HTC warranty until 2016, I could attempt to further brick the phone (hard-brick not turning on at all) and go through the repair process to get a replacement phone. If I did do this I would need to do something that gives no proof that this phone was ever rooted/unlocked.
In your knowledge would a simple flash of a ROM from another model or device corrupt hboot/bootloader?

Hello again, I've done some more research about what other users did when they had unfortunately hard-bricked their phone and I came across this thread that you had also posted in a few weeks ago (http://forum.xda-developers.com/htc-one/help/htc-one-m7-hard-brick-t2876273).
According to your post flashing this recovery will corrupt one of the main partitions and therefore make the device unable to switch on and then cause it to appear as "QUALCOMM HS6USB QDLOADER 9008".
My question is that are HTC able to see any proof of tampering once the device is in Qualcomm mode?

Jimmyy9 said:
I appreciate you offering your free time to help with my problem but if you think it will produce the same results as your previous tests then I wouldn't want you to waste your time. I have heard about this JTag process and it looks very convincing @ www.funphoneshop.com.
I see 2 paths.
The first would be to go with the JTag process and hope that it works (since m7 is not listed on their model list)
Click to expand...
Click to collapse
you should give them a call, with the proper hardware they can S-OFF your device and a lot more, so since you know what the problem is it should be easy to fix for them.
even if they only s-off the phone, that would be enough to continue the software solution (downgrade hboot and use the noBCB recovery)

[Q&A] |TOOL| HTC One Toolkit [M7] • v3.2.0

Q&A for |TOOL| HTC One Toolkit [M7] • v3.2.0
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for |TOOL| HTC One Toolkit [M7] • v3.2.0. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Hi, I'm trying to use firewater + tempwater for S-Off. However, while the firewater push completes fine, when I try to push TempRoot, all I get is the following:
adb push temproot /data/local/tmp/
cannot stat 'temproot': No such file or directory

McCovican said:
Hi, I'm trying to use firewater + tempwater for S-Off. However, while the firewater push completes fine, when I try to push TempRoot, all I get is the following:
adb push temproot /data/local/tmp/
cannot stat 'temproot': No such file or directory
Click to expand...
Click to collapse
Were both files (firewater and temproot) in the same adb/fastboot folder?

4304
majmoz said:
Were both files (firewater and temproot) in the same adb/fastboot folder?
Click to expand...
Click to collapse
Honestly no idea. I'm just using the S-Off interface with the toolkit, so I'm not entirely sure where it's actually putting this stuff. Right enough, there's no "download temproot" option like there is for firewater/revone/etc, just a push option. I'm using firewater because Hboot is v1.57.
Frankly I'm just trying to root the thing. I was led to believe s-off was a prerequisite of that, but I'm beginning to believe that's not exactly the case.

McCovican said:
Honestly no idea. I'm just using the S-Off interface with the toolkit, so I'm not entirely sure where it's actually putting this stuff. Right enough, there's no "download temproot" option like there is for firewater/revone/etc, just a push option. I'm using firewater because Hboot is v1.57.
Frankly I'm just trying to root the thing. I was led to believe s-off was a prerequisite of that, but I'm beginning to believe that's not exactly the case.
Click to expand...
Click to collapse
You don't need S-OFF to root. You just need a unlocked bootloader, custom recovery and SuperSU. Here are the instructions.
Also, I would use the raw adb and fastboot commands without the toolkit. I would recommend the Minimal ADB & Fastboot Tool. Most Dev's and OPs will give the commands for how to do certain things so you could just copy and paste. It also gives you more control on what is happening to your phone.

McCovican said:
Honestly no idea. I'm just using the S-Off interface with the toolkit, so I'm not entirely sure where it's actually putting this stuff. Right enough, there's no "download temproot" option like there is for firewater/revone/etc, just a push option. I'm using firewater because Hboot is v1.57.
Frankly I'm just trying to root the thing. I was led to believe s-off was a prerequisite of that, but I'm beginning to believe that's not exactly the case.
Click to expand...
Click to collapse
You don't need s-off to root the phone. But with s-on you will be limited to flashing Roms, Recovery and Kernels. Firmware updates are possible but must be Signed firmware and can only be flashed with a 're-locked bootloader.
Just flash TWRP Recovery 2.6.3.3 boot to TWRP then reboot system from TWRP. You will be prompted to root the device Select yes. You may need to update binaries but that's it your done.
Better still just flash a prerooted Rom with TWRP. :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Bricked phone using tool
I was messing around with fastboot section using your tool and now my phone will not turn on. I was having issues getting my adc to connect and was messing around with options while my phone was connected in fastboot mode. I have TWRP installed and a custom rom.
Here are the getvar results I got prior to this:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901497
(bootloader) imei: 354439051467639
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.041s
While connected I pressed both the getvar all button, the red S-ON button and the HTC Drivers button. None of the seemed to be doing anything so I disconnected my phone. I went to remove it from fastboot mode, but it was stuck and none of my button presses did anything. I held the power button until it turn off, but now it refuses to come back on.
I reinstalled the drivers and connected the phone to my pc, but nothing gets picked up. I go into the fastboot sub-menu and click devices and get this message.
fastboot devices
???????????? fastboot
Something is connected, I ran getvar all and can see this
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4137mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.031s
I'm thinking I might be able to use the tool to flash something to fix my phone, but I dont what it should be. Or maybe someone with more experience can suggest something else. I already tried holding the power+volume buttons and shining a light from other bricked threads. Can someone help?

redlupine said:
I was messing around with fastboot section using your tool and now my phone will not turn on. I was having issues getting my adc to connect and was messing around with options while my phone was connected in fastboot mode. I have TWRP installed and a custom rom.
Here are the getvar results I got prior to this:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901497
(bootloader) imei: 354439051467639
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.041s
While connected I pressed both the getvar all button, the red S-ON button and the HTC Drivers button. None of the seemed to be doing anything so I disconnected my phone. I went to remove it from fastboot mode, but it was stuck and none of my button presses did anything. I held the power button until it turn off, but now it refuses to come back on.
I reinstalled the drivers and connected the phone to my pc, but nothing gets picked up. I go into the fastboot sub-menu and click devices and get this message.
fastboot devices
????????????fastboot
Something is connected, I ran getvar all and can see this
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4137mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.031s
I'm thinking I might be able to use the tool to flash something to fix my phone, but I dont what it should be. Or maybe someone with more experience can suggest something else. I already tried holding the power+volume buttons and shining a light from other bricked threads. Can someone help?
Click to expand...
Click to collapse
Wow that second getvar is pretty messed up. First thing I recommend is try is flashing an ruu. http://www.htc1guru.com/dld/ruu_m7_...20_10-40-1150-04_release_326691_signed_2-exe/
This one matches your original getvar. While the device is connected with fastboot this way. Run the ruu.exe on your pc.
If you found my posts helpful, no need to say thanks. There's a button for that

Danny201281 said:
Wow that second getvar is pretty messed up. First thing I recommend is try is flashing an ruu.
This one matches your original getvar. While the device is connected with fastboot this way. Run the ruu.exe on your pc.
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
I downloaded it and tried to run it, but it gets stuck at
"Verifying information on your Android phone. Please wait..."
I checked the program with Process Explorer and its trying to run this:
cmd /C htc_fastboot -s ????????????? getvar boot-mode
Unless there is a way to force it through I don't think this RUU way with work.

redlupine said:
I downloaded it and tried to run it, but it gets stuck at
"Verifying information on your Android phone. Please wait..."
I checked the program with Process Explorer and its trying to run this:
cmd /C htc_fastboot -s ????????????? getvar boot-mode
Unless there is a way to force it through I don't think this RUU way with work.
Click to expand...
Click to collapse
I kind of expected that due to the output from your second getvar but it was worth a try. To be honest this is probably off topic here so you may want to take it to a different thread.
I would however like to bring this to the attention of @nkk71 let's wait to see what he has to say on this subject
I've never seen a getvar so messed up so let's hope nkk71 has some idea :good:
If you found my posts helpful, no need to say thanks. There's a button for that

Danny201281 said:
I kind of expected that due to the output from your second getvar but it was worth a try. To be honest this is probably off topic here so you may want to take it to a different thread.
Click to expand...
Click to collapse
You are right, I'm posting this to the bricked help phone thread:
[Unbrick Service] Bricked Phone? Need Help? Look Here.

Lollipop
Hey,
I have a UK M7 (locked to H3G if that matters) currently running Android Revolution w/ Sense (rooted).
I have set my CID to 11111111 , I have S-OFF, HBOOT-1.56.0000 and I am looking load the OTA for the Google Play Edition (Lollipop 5.0.1) on to it using your tool. And then I will re-root.
Really I just wondered if anyone thinks that this is a bad idea for any reason.

htc one stock
I lost my stock back-up for warranty CID- VZW__001
OS- 1.10.605.10
I d like to return to full s-on stock for warranty make a new back-up
Then use tool kit to return to s-Off TWRP CAN you please help

help..
hello there OP , thankyou for the time you have put into this tool, im a noob with smartphones, and once tried 'windroid' one-click/aio type device from xda forums, it ended up with me unlocking the token thingy, but then it would not go frther, it actually put a cross X over the pic of a HDD or looked it, i quickly hit power off/one and it booted automatically into a factory install/reset kind of environment.. since then ive been to scared to even try rooting again... but your kit and hansoon one seem O.K , but my problem is, how do i find what version exactly of phone that i have, the thing lookes like the htc one x, i recall updating the rom couple of times now, so it is on kernel v3.* , but again, i need to somehow find this info and then try again using a app that actually works..i getting good reviews on your thread so i guess im hoping for some magic here, i know the questions ive asked are very nooby, but trust me i thought i had killed it, i remember unlocking the token id, i recall pasting this in and then it showed up as unlocked.. i have kept my .bin file handy if ever i re-needed it.. so i guess that part is done.. i would LOVE to run something wich doesnt kill the battery, as im experincing now is 1day lasting full charged..without many apps :S
i am sorry for the length of this question, its just i had a bad experience once, dont want that again.. but im hanging to try again... feel free to respond, or not respond, i know what im askingshould be here somewhere, although the model, if it is a one or one-x i guess is the only thing i am curious of..is how would i know because a couple of models looked very similar.. i THINK im running android 4.2.2 ,kernel 3.* , i beleive there is a couple.
i know there is a new exploit out for v3 kernel. would this not help make the tool 1000% proof.?? one wich i was told is now being used for android v5 wich apprently roots every device upto v5, so thats all v3/4 and 5 in one exploit...i have 'heard' that xda do have it and are using it for newer phones.. but what an oppurtunity,if this was added into your tool,it would be 100% proof on everything android.. just a thought but, you seem like a happpy go lucky cool op, so im just saying, if i was working on a tool, id work alot more on exploitation of the device/making sure there is no residual pains, and simply adding ballon like tips around the app kinda cool touch... i like your tools look, and i wish to use it.. but i dont want to endup being locked in phone..
i have htc one x , 32g, i believe :S it LOOKS exact same as the htc one-x,it was given to me as a one-x (sold to me),and at that stage,it was on ebay prettymuch on par with the other htc one-x,so it would be one-x im about 99% sure, i just now wonder about the updates i allowed the phone to perform,wich then changed android version/kernel.
I dont know if you have the answer i need, or answers if you wish to answer the entire post,because your going to get it,and really its you i want to ask anyhow, so its fine if it stays private, although since it is noobish, i guess you could go either way... i do raise some issues for some people to scared to get 'bricked' .. my phone uses vodaphones manager,wich i have uninstalled everytime it installs,now it has embedded itself though,and it only deletes down to un updated vodafone manager, i deleted every other voda app on there... so its basiocaallly a question of, do i go ahead with this version, or do i wait for something thats 100%.. im sure alot of people are like me, alittle hesitant to root..or had bad experiences.. ive rooted my samsung duo young fine, but the htc, well.. its got me sofar..i see all the one touch tools,i grabbed them, but wich one will actually work right.. remembeing i have used one wich was labelled windroid from xda ,it only made me paranoid as hell to use a working one, and then, i also think of exploitation, and i seriously wonder if your app can rooot an updated one-x on 4.2.2,and it does not go higher, it seems like two updates to get to this version,no updates now for about 6-12months,so i am looking here at a handful of exploits wich DO work and will root, ie; futex ; or asking you, if you think that would make your app even nicer,and erhaps a cleaner root process is achieved with something new, i know the one mentioned in UG came to xda,so,why is there no updated packs :?
i would hope that things got updated,maybe just me,but if theyre updating theyre firmware, then surely you must update your end to handle this... so is MY phone going to be o.k with this app, or do i wait and hope there is a newer expoloitation achieved ?
its a long post,, but i hope im getting through to some dev, theres alot to be done with these packs,specially with things like google play pad coming out, id like to buy one of those,but again,how do i trust apps wich have not been updated in ages...yet my phone has updated.. it just blurs the mind as to how you would get around kernel patches..i know android has many exploits,but not clean ones like the current one in use.. i will look in on this thread and hopefully someone will explain to me how to get the exact phone info, and alittle more info on how things getting rooted, ie; exploitation , and kernel images/links to GOOD working kernels already tested.. noobs like me dont want to test 5 types, we want one GOOD one
im sorry to write alot,but this is good topic ive been walking around for to long. i even have a spare iphone sitting here just for when i root the one-xx.i am confdent that if anyone will help me on this,its going to be xda forums, simple as that... i dont even bother reading many other blogs nomore,everything android is here..its a great little place,and i love it sofar.. exploring the roms,reading,wanting :[.. i will await some feedback. again, apologies for long post,but i trying to be thorough as i can on each issue. cheers.
dru
---------- Post added at 06:46 PM ---------- Previous post was at 06:37 PM ----------
apologies for the long post... ofc i dont expect it to go public BUT it does raise some issues..i dont see all of xda forum yet, but every search sofar has yielded results..only areas i find lacking is the rooting devices actually explaining wich root method is being used, its not a necessity,but some root methods leave memory leaks/other bugs wich can be phone specific, ome wich dont do anything atall because they bypass aprotections properly.
IF there is a thread on exploiting, i will join there..someone has to be sharing the exploits,and so they should, but alittle more info could be given to public,i guess not all people care,they just want one-click, well, i care about what i stick in my phone, so flashing a custom rom, kernel to me is a big deal i expect done right once..
i look forward to some feedback on my htc issues.

Sense Rom for S-off?
Do I have to install a sense-based rom before i go on s-off with Firewater?
Greez philipp

s-off htc one x
hi im new to all this but i have already unlocked the bootloader to my device and i want to try to root the device and s-off it...this is what is showing in boot screen
HBOOT--1.36
CPLD--NONE
RADIO--5.1204
eMMC-BOOTMODE:disabled
CPU-BOOTMODE:disabled
HW SECURE BOOT--ENABLED
MODEM PATHFF
will i be able to use the toolkit with this phone...any help and guidance most appreciated tnx

Griffmiester said:
hi im new to all this but i have already unlocked the bootloader to my device and i want to try to root the device and s-off it...this is what is showing in boot screen
HBOOT--1.36
CPLD--NONE
RADIO--5.1204
eMMC-BOOTMODE:disabled
CPU-BOOTMODE:disabled
HW SECURE BOOT--ENABLED
MODEM PATHFF
will i be able to use the toolkit with this phone...any help and guidance most appreciated tnx
Click to expand...
Click to collapse
You are not at the right place, this is the HTC One forum (M7) not the One X (Endeavor or Evita)
If you have an Endeavor One X (Tegra 3 cpu variant) , S-OFF is not possible
If you have an Evita One X (XL) (Qualcom cpu variant), head to this forum: http://forum.xda-developers.com/one-x-att
will i be able to use the toolkit with this phone...
Click to expand...
Click to collapse
No this is not for the One X, anyway better to learn how to use ADB and Fastboot .

Do this toolkit work with last android update?
I have a HTC One running 4.4.3 with brand (tim)(sense 6.0) and I wanted to know if this toolkit works with my device. I am not very good with modding so I could do disasters.
Thanks for replies.

LucaBalzano said:
I have a HTC One running 4.4.3 with brand (tim)(sense 6.0) and I wanted to know if this toolkit works with my device. I am not very good with modding so I could do disasters.
Thanks for replies.
Click to expand...
Click to collapse
Then I would suggest spend a few days to learn. Even if it does work and something goes wrong you won't know how to fix it. Do the proper research and learn to do things the right way instead of using a tool kit.

HTC ONE X+
***LOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.171.33
eMMC-bootmode: disabled
CPU-bootmode: disabled
MODEM PATH : OFF
Jun 21 2013, 17:36:36
HBOOT
SERIAL: FA2ASW105934
CANNOT GET OUT OF HBOOT SCREEN OR UE ADB FASTBOOT