Database Develop

[Q] Unable to unlock, flash recovery or s-off or RUU

I have one hell of a problem.
Status of device:
-Google play edition kit kat htc one (converted from att version)
-No recovery, recovery is INACCESSABLE
-No root, and temp root does not work as well.
-Stock att RUU's not working (as of yet)
-I have tried firewatter, revone and rum runner to try and root so i can get s-off but unable.
-For whatever reason fastboot oem unlock does not as well as the unlock token.
Things i haven't tried because i cant find them:
-Google play edition RUU.exe file
-A standalone RUU for downgrading hboot 1.54 (which is my device currently)
-A modified RUU.exe that will allow me to restore to stock ANYTHING
-A RUU.zip that i can flash manually without s-off
Any suggestions?

j.sax.riley said:
I have one hell of a problem.
Status of device:
-Google play edition kit kat htc one (converted from att version)
-No recovery, recovery is INACCESSABLE
-No root, and temp root does not work as well.
-Stock att RUU's not working (as of yet)
-I have tried firewatter, revone and rum runner to try and root so i can get s-off but unable.
-For whatever reason fastboot oem unlock does not as well as the unlock token.
Things i haven't tried because i cant find them:
-Google play edition RUU.exe file
-A standalone RUU for downgrading hboot 1.54 (which is my device currently)
-A modified RUU.exe that will allow me to restore to stock ANYTHING
-A RUU.zip that i can flash manually without s-off
Any suggestions?
Click to expand...
Click to collapse
you probably have to redo the process at http://www.htcdev.com/bootloader/
redo the process and try to unlock your bootloader with the new unlock.bin
just follow the steps

OK.. Explain this. If you converted. You went SOFF. Then how do you end up with LOCKED Bootloader and SJON?
sent from my mobile device

I have had the same problem few weeks ago
First unlock your bootloader again with a new unlock.bin ...redo the hole process
http://www.htcdev.com/bootloader/
Second regain S-Off with rumrunner
Finaly you should be able to restore with a RUU

Dosent go
Boachti said:
I have had the same problem few weeks ago
First unlock your bootloader again with a new unlock.bin ...redo the hole process
Second regain S-Off with rumrunner
Finaly you should be able to restore with a RUU
Click to expand...
Click to collapse
It says on the prompt that it completed successfully with the unlock, however i do not receive a prompt on the device stating the developer options to accept or deny.
I will proceed as if i did and try my att ruu to try and update the device.
I tried with a google ruu and get signature verify fail, i think that i get the same issue with the att ruu.
IF you can suggest a RUU that will help me out of the situation i would really appreciate it.
Also if there is any reason why rum runner will not complete, i can swear adb is up everything should work but it just will not complete.

j.sax.riley said:
It says on the prompt that it completed successfully with the unlock, however i do not receive a prompt on the device stating the developer options to accept or deny.
I will proceed as if i did and try my att ruu to try and update the device.
I tried with a google ruu and get signature verify fail, i think that i get the same issue with the att ruu.
IF you can suggest a RUU that will help me out of the situation i would really appreciate it.
Also if there is any reason why rum runner will not complete, i can swear adb is up everything should work but it just will not complete.
Click to expand...
Click to collapse
Turning security back to ''on'' and relocking your bootloader on GPE was a bad decision, you probably bricked your device forever.
This is discussed in this thread: http://forum.xda-developers.com/showthread.php?t=2547894
With S-ON and Locked (Re-Locked) bootloader, your only hope is to flash a RUU of same or higher version than the version currently installed on your phone. You can't downgrade anything with s-on using a ruu.exe neither a ruu.zip. You are stuck until htc release a newer gpe ruu.
Post the output of ''fastboot getvar all'' minus your IMEI and SERIALNO

alray said:
Turning security back to ''on'' and relocking your bootloader on GPE was a bad decision, you probably bricked your device forever.
This is discussed in this thread:
With S-ON and Locked (Re-Locked) bootloader, your only hope is to flash a RUU of same or higher version than the version currently installed on your phone. You can't downgrade anything with s-on using a ruu.exe neither a ruu.zip. You are stuck until htc release a newer gpe ruu.
Post the output of ''fastboot getvar all'' minus your IMEI and SERIALNO
Click to expand...
Click to collapse
Is there any chance of spoofing the ruu.zip to make it look like a higher verison?
If not that can i just flash a recovery image even if its stock so i can have a recovery as i currently don't even have that which i think is the source of my problems.

j.sax.riley said:
Is there any chance of spoofing the ruu.zip to make it look like a higher verison?
If not that can i just flash a recovery image even if its stock so i can have a recovery as i currently don't even have that which i think is the source of my problems.
Click to expand...
Click to collapse
Unfortunately no. ''spoofing'' the ruu will require to decrypt it. With s-on you can't flash a decrypted ruu, you can only flash a ruu that is signed with HTC private key (decrypted ruu can't be signed back with HTC private key). S-OFF would have saved your phone in this case.
The only way to flash the stock recovery in your case is to flash a signed firmware.zip of the same of higher version.
Still waiting your ''fastboot getvar all'' output

alray said:
Unfortunately no. ''spoofing'' the ruu will require to decrypt it. With s-on you can't flash a decrypted ruu, you can only flash a ruu that is signed with HTC private key (decrypted ruu can't be signed back with HTC private key). S-OFF would have saved your phone in this case.
The only way to flash the stock recovery in your case is to flash a signed firmware.zip of the same of higher version.
Still waiting your ''fastboot getvar all'' output
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(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: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

j.sax.riley said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(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: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Afaik, there is no ruu you can flash. Your version is 3.62.1700.1 and the latest ruu I can find is 3.58.1700.5 which is a downgrade (require S-OFF) You'll need to find or wait for a ruu higher or equal to 3.62.1700.1

alray said:
Afaik, there is no ruu you can flash. Your version is 3.62.1700.1 and the latest ruu I can find is 3.58.1700.5 which is a downgrade (require S-OFF) You'll need to find or wait for a ruu higher or equal to 3.62.1700.1
Click to expand...
Click to collapse
That sux.
Are you sure there is no other way?
The htc regular version stock is version 4 something and so i was hopping that would override any bull**** i have going on.
i tired temp roots to see if i can s-off in os with firewater but i was unsuccesffully at gaining temp root.
Its funny to me because i swear reading somewhere that "andoid 4.4 is great" dont even have to root because of app ops or something but its obvious now thats a load of b.s and i should have just always run rooted as that has never done me wrong.
Do you know where i would find a ruu when one comes out? as one probably will with 4.4.3 coming out soon.

j.sax.riley said:
That sux.
Are you sure there is no other way?
Click to expand...
Click to collapse
If you can't s-off using rumrunner or firewater then no, idt there is other options.
j.sax.riley said:
The htc regular version stock is version 4 something and so i was hopping that would override any bull**** i have going on.
Click to expand...
Click to collapse
The international version ruu is a .401 base (not .1700) and require to change CID and probably MID. Changing those values require S-OFF!
j.sax.riley said:
Do you know where i would find a ruu when one comes out? as one probably will with 4.4.3 coming out soon.
Click to expand...
Click to collapse
htcdev.com under the ''kernel source code'' section, http://htc1guru.com and http://androidruu.com/?developer=M7

[*] Attempting to acquire root. This will take 5-10 minutes, be patient
error in setsockopt().
Failed to get prepare_kernel_cred address.
Failed to get commit_creds address.
Failed to get ptmx_fops address.
Failed to setup variables.
This is my output from trying temp root with firewater method.
I am not sure what the issue is that is happening but i assume with the first failure the whole system collapses.
Thank you for the help btw, and i will keep my eyes open for a new ruu.
What do i need to be looking for in the ruu to make sure it will work with my phone?
Specific cid and mid?

j.sax.riley said:
What do i need to be looking for in the ruu to make sure it will work with my phone?
Specific cid and mid?
Click to expand...
Click to collapse
must be signed and same or higher version than 3.62.1700.1.
any .1700 version will match your CID and MID (GOOGL01 and PN0712000)

Last question,
Flashing a newer hboot or the "modified gpe bootloader"
Is it possible since im s-off, and will it change anything?
And why wont this zip work?
RUU Zip M7 Google Edition 4.4 3.58.1700.5
Because its version 3.58 and i am 3.62?

I like Htc phones and especially their commitment to bring timely updates.
But.....i do miss being able to use odin and never have to worry if your device gets f-ed up you can always reformat it to stock without trying to get a warranty replacement (which i cant because i'm rocking my google play edition) which is great and totally beats cyanogen mod for stability.
Although....i miss blink feed lol

j.sax.riley said:
Last question,
Flashing a newer hboot or the "modified gpe bootloader"
Is it possible since im s-off, and will it change anything?
Click to expand...
Click to collapse
Fomr the output of your fastboot getvar all, you are S-ON not S-OFF so you won't be able to flash a modifed hboot. Btw, if you flash a modified hboot in the future with s-off, you will brick your device if you s-on again (with a modified hboot)
j.sax.riley said:
And why wont this zip work?
RUU Zip M7 Google Edition 4.4 3.58.1700.5
Because its version 3.58 and i am 3.62?
Click to expand...
Click to collapse
Yes, 3.58 is a downgrade of version from what you have currently on your phone. Downgrading require S-OFF

[Q] HTC One relocked, can't flash (signature error)

Hey All,
I hope you guys can help me, I'm completely lost in all these threads and posts. I've spent hours on this, literally hours...
I have a HTC One M7 (bought in Belgium) which I wanted to return to stock because of a faulty speaker (I just rooted the standard image). So I relocked the bootloader to flash an RUU. I tried flashing several European RUUs from the xda collection, but nothing worked. I also tried a zipped firmware, and it also fails. I always get this error:
FAILED remote: 12 signature verify fail
I'm stuck in fastboot, it doesn't boot into the OS anymore, only fastboot.
Getvar output:
C:\ADT\sdk\platform-tools>fastboot getvar all
(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.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4024mV
(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.051s
I try to flash the RUU Zip M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4_decrypted.zip
Strange thing is, when I check the zip's android-info:
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__E11
...
So I don't get anymore why it would fail a signature check...
I also tried flashing a newer version, this didn't work either. What makes matters worse, the battery keeps uncharging as I continue to struggle...
Tell it to me straight, doctor... Is my HTC doomed to be a paperweight?

What do you mean "flash a RUU" ? Is it you try to fastboot flash the RUU ? It won't work that way.
Checking this : http://www.androidruu.com/?developer=M7
I see there is only one RUU that may work for you : RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
What you need to do:
1- in fastboot mode - relock the bootloader : run command fastboot oem lock (you did this already)
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish

ckpv5 said:
What do you mean "flash a RUU" ? Is it you try to fastboot flash the RUU ? It won't work that way.
Checking this :
I see there is only one RUU that may work for you : RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
What you need to do:
1- in fastboot mode - relock the bootloader : run command fastboot oem lock (you did this already)
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
Click to expand...
Click to collapse
First of all, thanks a bunch for taking the time to respond.
I'm currently downloading the proposed RUU and will try flashing it.
I don't understand, however, why my downloaded RUUs wouldn't work since the CID and model corresponded?
I tried both methods: using the RUU to flash and using the fastboot oem rebootRUU > flash zip.

dwarfstrider said:
First of all, thanks a bunch for taking the time to respond.
I'm currently downloading the proposed RUU and will try flashing it.
I don't understand, however, why my downloaded RUUs wouldn't work since the CID and model corresponded?
I tried both methods: using the RUU to flash and using the fastboot oem rebootRUU > flash zip.
Click to expand...
Click to collapse
When your device is S-ON, you need a correct version RUU i.e 1.29.401.16 (which is not available, I believe), so you should go for a higher version not lower version.
I'm new to HTC One too so not so sure about fastboot oem rebootRUU, but I believe it needs a S-OFF device to work but yours is S-ON.
More info : http://forum.xda-developers.com/showthread.php?t=2358738

ckpv5 said:
When your device is S-ON, you need a correct version RUU i.e 1.29.401.16 (which is not available, I believe), so you should go for a higher version not lower version.
I'm new to HTC One too so not so sure about fastboot oem rebootRUU, but I believe it needs a S-OFF device to work but yours is S-ON.
[/url]
Click to expand...
Click to collapse
That RUU doesn't work, after checking the signature I get: ERROR [158]: IMAGE ERROR...

dwarfstrider said:
That RUU doesn't work, after checking the signature I get: ERROR [158]: IMAGE ERROR...
Click to expand...
Click to collapse
Search for ERROR 158 may help you.
What I understand ERROR 158 maybe because the bootloader is not relocked, not using USB2.0, maybe also a modified hboot (usually the one that remove the red text warning) is installed prior to running the RUU, not running the RUU in Admin Privilege mode.
Maybe someone else have better idea, have to wait for that.

What I understand ERROR 158 maybe because the bootloader is not relocked, not using USB2.0
- No, I locked using fastboot oem lock with USB cable.
maybe also a modified hboot (usually the one that remove the red text warning) is installed prior to running the RUU
- Afaik, I never installed a custom hboot myself. I get the red text warning at the white HTC screen.
not running the RUU in Admin Privilege mode.
- Nope, the RUU runs with admin privileges in Win 7
Maybe someone else have better idea, have to wait for that.
- Let's hope so :laugh:

This is what my phone looks like atm:
i.imgur.com/ bX9MFM3.jpg
(can't post pics/links yet, sorry)
Please guys, help a fella out... I will be forever grateful

Update: I unlocked my phone again with the unlock bin from HTCDev and now it boots again...
I suppose I need to do S-OFF with revone since I'm at 1.44, but unsure. Damn this stuff is confusing.

You will need to flash new firmware I saw a hierarchy of htc one's Ruu firmware list on android revolution site.
Just check in the name of the correct ruu you downloaded and try to match the numbers of your Ruu with the list given there. I hope it may help you or if you get confused Pm me.
Sent from my HTC One using XDA Premium 4 mobile app

OK, I solved it.
So I did an S-OFF with revone, then locked and removed tampered (also revone).
Then I flashed a good RUU. It took ages to find a good one, followed another thread (2325010) on the forum which I can't link because of the restrictions .
Then I used thread 1672425 to put S-ON again and now my One it back to full stock!

[Q] HTC ONE (m7) 64GB Developer Edition

Hello everybody, I´m a little newbie here so need some URGEN HELP.
1.- I bought an HTC ONE (m7) 64GB Developer Edition from SWAPPA with ClockworkMod Recovery and CyanogenMod 11 on it.
2.- While looking into XDA-Developer was following a thread to get it back to stock recovery using nandroid so I can flash an RUU from HTCDEV
While doing that seems that I erase everything from the phone and now it´s giving me an error mounting e:/ drive and It doesn´t recognize the phone in ADB mode.
I´m stuck with the CWM without the ability to get files into /sdcard/0/clockworkmode/backups
Can someone help me or point me in the right direction to get back to the stock android that the HTC Developer Edition (m7) comes in factory default.

ulises.boom said:
2.- While looking into XDA-Developer was following a thread to get it back to stock recovery using nandroid so I can flash an RUU from HTCDEV
Click to expand...
Click to collapse
you don't need stock recovery to use a ruu. Recovery is overwritten by the ruu.
ulises.boom said:
While doing that seems that I erase everything from the phone and now it´s giving me an error mounting e:/ drive and It doesn´t recognize the phone in ADB mode.
I´m stuck with the CWM without the ability to get files into /sdcard/0/clockworkmode/backups
Can someone help me or point me in the right direction to get back to the stock android that the HTC Developer Edition (m7) comes in factory default.
Click to expand...
Click to collapse
Just flash the latest dev edition ruu http://www.htc1guru.com/2014/03/android-dev-ruu/

@alray Thanks for the prompt response.
I will download and try that later today after work.
But some questions so I don´t do something stupid:
I have to restart the phone on Fastboot mode or Recovery Mode for the RUU to work, as the phone is starting with the Gray and red triangle and an admiration mark.?
Thanks

ulises.boom said:
@alray Thanks for the prompt response.
I will download and try that later today after work.
But some questions so I don´t do something stupid:
I have to restart the phone on Fastboot mode or Recovery Mode for the RUU to work, as the phone is starting with the Gray and red triangle and an admiration mark.?
Thanks
Click to expand...
Click to collapse
you can run the ruu.exe in bootloader mode if you want, it will then switch to ruu mode by itself. If the phone were booted in the OS the ruu.exe will make it reboot in ruu mode.

@arlay Sorry to tell you that it didn´t work.
Let me explain a little of what I have here:
It seems that I erase everythin in the Phone except by the Fastboot and Recovery.
I´m having the following errors:
E:Can´t mount /cache/recovery/
E: unknown volume "/sdcard/.android_secure
Running the RUU I got Error 155.
And another thing, it can find /system/xbin/su
Do I hava a recobrable one or a brick?
I have it on s-on and could not made it s-off with revone
alray said:
you can run the ruu.exe in bootloader mode if you want, it will then switch to ruu mode by itself. If the phone were booted in the OS the ruu.exe will make it reboot in ruu mode.
Click to expand...
Click to collapse

ulises.boom said:
@arlay Sorry to tell you that it didn´t work.
Let me explain a little of what I have here:
It seems that I erase everythin in the Phone except by the Fastboot and Recovery.
I´m having the following errors:
E:Can´t mount /cache/recovery/
E: unknown volume "/sdcard/.android_secure
Running the RUU I got Error 155.
And another thing, it can find /system/xbin/su
Do I hava a recobrable one or a brick?
I have it on s-on and could not made it s-off with revone
Click to expand...
Click to collapse
1- can you post a "fastboot getvar all" (excluding IMEI and s/n)
2- with S-On you need to relock bootloader for RUU (same or higher version) to work
3- for S-Off, you should also try rumrunner and firewater

@nkk71 Here is the results of the getvar
List of devices attached
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.16
(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: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4281mV
(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
nkk71 said:
1- can you post a "fastboot getvar all" (excluding IMEI and s/n)
2- with S-On you need to relock bootloader for RUU (same or higher version) to work
3- for S-Off, you should also try rumrunner and firewater
Click to expand...
Click to collapse

ulises.boom said:
@nkk71 Here is the results of the getvar
List of devices attached
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-main: 1.29.1540.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
finished. total time: 0.062s
Click to expand...
Click to collapse
Personally, I would use this ruu.exe : http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
it's the same version as your current one, which would give you a chance to S-Off, if you wish.... a higher version, could make that more difficult.
the RUU will work but you need to lock your bootloader using fastboot oem lock
I know it's ironic that the Dev Edition is bootloader unlocked be default, but RUU's wont work with that.

@arlay & @nkk71 Thanks a million for helping me solve my problem.
I have a functional HTC ONE m7ul Developer Edition back in business.
Now to wait for a KitKat Update to put it on the Mobile.
nkk71 said:
Personally, I would use this ruu.exe : http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
it's the same version as your current one, which would give you a chance to S-Off, if you wish.... a higher version, could make that more difficult.
the RUU will work but you need to lock your bootloader using fastboot oem lock
I know it's ironic that the Dev Edition is bootloader unlocked be default, but RUU's wont work with that.
Click to expand...
Click to collapse

I´m a very happy man again.
Have been receving and updating the phone with already three OTA Updates without any issues so far.
Many thanks to the guys/girls on XDA-Developers for this very helpful site.
ulises.boom said:
@arlay & @nkk71 Thanks a million for helping me solve my problem.
I have a functional HTC ONE m7ul Developer Edition back in business.
Now to wait for a KitKat Update to put it on the Mobile.
Click to expand...
Click to collapse

ulises.boom said:
Hello everybody, I´m a little newbie here so need some URGEN HELP.
1.- I bought an HTC ONE (m7) 64GB Developer Edition from SWAPPA with ClockworkMod Recovery and CyanogenMod 11 on it.
2.- While looking into XDA-Developer was following a thread to get it back to stock recovery using nandroid so I can flash an RUU from HTCDEV
While doing that seems that I erase everything from the phone and now it´s giving me an error mounting e:/ drive and It doesn´t recognize the phone in ADB mode.
I´m stuck with the CWM without the ability to get files into /sdcard/0/clockworkmode/backups
Can someone help me or point me in the right direction to get back to the stock android that the HTC Developer Edition (m7) comes in factory default.
Click to expand...
Click to collapse
Is this the link you talking about?
http://www.youtube.com/watch?v=rpA71FXddyU

[Q] HTC One not booting and not going into recovery. Plz help.

My htc one At&t turned Developer edition was working perfect. No root , No custom rot or whatsoever. I was running latest update 4.4 with Sense 6. It just rebooted and then it just got stuck at the HTC one logo screen. Wont just pass that.
I hard reset with power + down. It rebooted. But then again stuck at the HTC logo screen.
I went to fastboot and tried going to recovery . It just reboots and then comes with a Red Triangle exclamation mark. I was hoping to go in recover and the clean the cache might fix the stuck on boot screen issue. It seems i am not able to go in recovery also. I don't know why.
I tried selecting the factory reset , it took its time. Then it shut down. I again booted it , again stuck at HTC logo screen. It wont load the android. It takes charging fine.
Any idea why going to recovery shows the red exclamation mark ? i have not played with the recovery.. have been getting the HTC update as normal.
Also any way i can boot it now ?? its just stuck at the boot screen.
Was my primary phone.
Thanks,

anirudhgargi said:
My htc one At&t turned Developer edition was working perfect. No root , No custom rot or whatsoever. I was running latest update 4.4 with Sense 6. It just rebooted and then it just got stuck at the HTC one logo screen. Wont just pass that.
I hard reset with power + down. It rebooted. But then again stuck at the HTC logo screen.
I went to fastboot and tried going to recovery . It just reboots and then comes with a Red Triangle exclamation mark. I was hoping to go in recover and the clean the cache might fix the stuck on boot screen issue. It seems i am not able to go in recovery also. I don't know why.
I tried selecting the factory reset , it took its time. Then it shut down. I again booted it , again stuck at HTC logo screen. It wont load the android. It takes charging fine.
Any idea why going to recovery shows the red exclamation mark ? i have not played with the recovery.. have been getting the HTC update as normal.
Also any way i can boot it now ?? its just stuck at the boot screen.
Was my primary phone.
Thanks,
Click to expand...
Click to collapse
the red exclamation mark is normal, the stock recovery is working fine. When you access the recovery and get to this point, hold volume up button and press power to access recovery options. You can factory reset from here and clear cache

stovie_steve said:
the red exclamation mark is normal, the stock recovery is working fine. When you access the recovery and get to this point, hold volume up button and press power to access recovery options. You can factory reset from here and clear cache
Click to expand...
Click to collapse
Great ! Many thanks.
I got to the Recovery menu. I cleared the cache and the selected the factory/reset. And rebooted the device.
But Its till stuck at the boot screen

anirudhgargi said:
Great ! Many thanks.
I got to the Recovery menu. I cleared the cache and the selected the factory/reset. And rebooted the device.
But Its till stuck at the boot screen
Click to expand...
Click to collapse
Can you post a fastboot getvar all and post the results, removing your IMEI and Serial number please?
Are you completely stock, S-on and locked bootloader?

S-on , Bootloader locked. Complete Stock.
stovie_steve said:
Can you post a fastboot getvar all and post the results, removing your IMEI and Serial number please?
Are you completely stock, S-on and locked bootloader?
Click to expand...
Click to collapse
Yes i am Completely on stock with S-on and locked bootloader. I switched my phone from At&t to Dev edition some months back . I installed a Brightstar RUU and did a series of OTA time to time. So it was S-on , bootloader locked and no custom recovery etc All perfect with no playing around. Was my 1st device.
Thanks

anirudhgargi said:
Yes i am Completely on stock with S-on and locked bootloader. I switched my phone from At&t to Dev edition some months back . I installed a Brightstar RUU and did a series of OTA time to time. So it was S-on , bootloader locked and no custom recovery etc All perfect with no playing around. Was my 1st device.
Thanks
Click to expand...
Click to collapse
Please post a fastboot getvar all. To do this, connect your phone to the computer and make sure you have adb/fastboot files. At the bootloader screen it shoulder say FASTBOOT USB
Open a command prompt from the folder where your ADB files are and type the command fastboot getvar all. Post the results here, and remember to remove your serial no and IMEI

GetVar All Output.
stovie_steve said:
Please post a fastboot getvar all. To do this, connect your phone to the computer and make sure you have adb/fastboot files. At the bootloader screen it shoulder say FASTBOOT USB
Open a command prompt from the folder where your ADB files are and type the command fastboot getvar all. Post the results here, and remember to remove your serial no and IMEI
Click to expand...
Click to collapse
Anirudh-Gargis-MacBook:~ anirudhgargi$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(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: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3790mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s

anirudhgargi said:
Anirudh-Gargis-MacBook:~ anirudhgargi$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(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: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3790mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
Your CID is cidnum: 11111111 which means this phone has been rooted before. Did you run any fastboot commands e.g. fastboot writesecureflag 3 and go back to S-ON? Did you install any updates recently?

Rooted when it was 4.1 on At&t. But never then.
stovie_steve said:
Your CID is cidnum: 11111111 which means this phone has been rooted before. Did you run any fastboot commands e.g. fastboot writesecureflag 3 and go back to S-ON? Did you install any updates recently?
Click to expand...
Click to collapse
Yes it was rooted when it was 4.1 and then i installed a 4.2 via RUU.exe to get to Dev Edition. I changed to SuperCid as that time the RUU was not working for some reason. I left it 1111111 as i was able to get the OTA updates normally. Since that 4.3 no rooting and no S-off. Had been like this since then.
I did not install any update recently. Last update was back in Aug for the sense 6.0. Have been using since then without any issue , except for couple of OS crashes.
What you doubt ? Has the OS partition corrupted ? Do i need to reflash ?

anirudhgargi said:
Yes it was rooted when it was 4.1 and then i installed a 4.2 via RUU.exe to get to Dev Edition. I changed to SuperCid as that time the RUU was not working for some reason. I left it 1111111 as i was able to get the OTA updates normally. Since that 4.3 no rooting and no S-off. Had been like this since then.
I did not install any update recently. Last update was back in Aug for the sense 6.0. Have been using since then without any issue , except for couple of OS crashes.
What you doubt ? Has the OS partition corrupted ? Do i need to reflash ?
Click to expand...
Click to collapse
I checked for an RUU for your current version but cannot find one. And because you are S-ON you cannot downgrade or run an earlier RUU
Your option at present may be only to unlock the bootloader via HTC.dev, install custom ROM/Recovery and then obtain S-OFF via firewater or Sunshine to remove the TAMPERED and re-lock the bootloader

Ohh ! i don't have a Window machine also handy
stovie_steve said:
I checked for an RUU for your current version but cannot find one. And because you are S-ON you cannot downgrade or run an earlier RUU
Your option at present may be only to unlock the bootloader via HTC.dev, install custom ROM/Recovery and then obtain S-OFF via firewater or Sunshine to remove the TAMPERED and re-lock the bootloader
Click to expand...
Click to collapse
I was also checking the RUU if theres is one of 4.4 wirh sense6 released by htc.
As i am S-On i cannot download a previous version of RUU and flash that ? Why is that ?
Can a OTA update ( MR ) will do ? i can try searching for the latest OTA file
i can just place the OTA of the latest Sense 6 and then place in storage and choose update via phone storage.

anirudhgargi said:
I was also checking the RUU if theres is one of 4.4 wirh sense6 released by htc.
As i am S-On i cannot download a previous version of RUU and flash that ? Why is that ?
Can a OTA update ( MR ) will do ? i can try searching for the latest OTA file
i can just place the OTA of the latest Sense 6 and then place in storage and choose update via phone storage.
Click to expand...
Click to collapse
S-ON does not permit you to downgrade to another RUU, only upgrade. If you try and flash an RUU.zip via fastboot you will have a beautiful aluminium ornament as the phone will not work.
I don't think there is an OTA either

Many thanks, i will update after doing all those steps.
stovie_steve said:
S-ON does not permit you to downgrade to another RUU, only upgrade. If you try and flash an RUU.zip via fastboot you will have a beautiful aluminium ornament as the phone will not work.
I don't think there is an OTA either
Click to expand...
Click to collapse
I was able to find the Sense 6 4.4 OTA. Just that i am scared now.
I guess i will have to get a window pc to do that what you told.
Many thanks @stovie_steve.
Regards,
ANirudh

anirudhgargi said:
I was able to find the Sense 6 4.4 OTA. Just that i am scared now.
I guess i will have to get a window pc to do that what you told.
Many thanks @stovie_steve.
Regards,
Anirudh
Click to expand...
Click to collapse
1 more question , which file can i download after unlocking the bootloader ?
I mean can i install another binary with S-On and unlocked bootloader ? Which one shall i download
To do S-off i need to have working android (adbshell).
And just to understand the process I need that to install a custom recovery so that i can do a S-off. Once S-off i can run the 4.3 RUU exe. Right ? Of course re-lock the bootloader later as i will be doing a updates from HTC (signed) only.
After that OTA can bring me to latest OS ?

Which Custom rom to flash for next step.
anirudhgargi said:
1 more question , which file can i download after unlocking the bootloader ?
I mean can i install another binary with S-On and unlocked bootloader ? Which one shall i download
To do S-off i need to have working android (adbshell).
And just to understand the process I need that to install a custom recovery so that i can do a S-off. Once S-off i can run the 4.3 RUU exe. Right ? Of course re-lock the bootloader later as i will be doing a updates from HTC (signed) only.
After that OTA can bring me to latest OS ?
Click to expand...
Click to collapse
I have unlocked the bootloader and got a custom recovery (twrp) . I am still s-on. To do S-off
i need to have a working android , for that i need a custom rom. Can anybody tell which rom can be good , i have already the latest Stock 4.4 with "S-ON" and unlocked bootloader.
I cannot flash a htc rom directly as i am S-on and have latest update. To download a version lower (RUU avail) i need to do s-off.
My final aim to get back to Stock 4.4 Sense 6 . This way i approached my HTC one hit a boot loop and not coming out after all methods.

[Q] Is this phone bricked?

Afternoon peeps.
A friend at work has just dropped a HTC One (m7) onto my desk asking if i can bring it back to life. Allegedly whilst flashing the ROM the USB cable detached.
Any who, the phone is stuck on the bootloader. It's TAMPERED, RELOCKED, HBOOT-1.55
I cannot unlock the phone with the HTC unlock token or fastboot oem unlock
The former recycles power but still says RELOCKED, the latter gives me (ERR Command error !!!)
If I run fastboot oem rebootRUU the phone cycles power then returns to the bootloader.
I've tried running "RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe". This states I'm on image 3.63.61.1 so i'm guessing it can communicate in some ways but sadly it fails to push the image after rebooting the phone back into Bootloader (I assume it's going for the oem recovery here?)
Any suggestions or is it dead in the water?

elmuziko said:
Afternoon peeps.
A friend at work has just dropped a HTC One (m7) onto my desk asking if i can bring it back to life. Allegedly whilst flashing the ROM the USB cable detached.
Any who, the phone is stuck on the bootloader. It's TAMPERED, RELOCKED, HBOOT-1.55
I cannot unlock the phone with the HTC unlock token or fastboot oem unlock
The former recycles power but still says RELOCKED, the latter gives me (ERR Command error !!!)
If I run fastboot oem rebootRUU the phone cycles power then returns to the bootloader.
I've tried running "RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe". This states I'm on image 3.63.61.1 so i'm guessing it can communicate in some ways but sadly it fails to push the image after rebooting the phone back into Bootloader (I assume it's going for the oem recovery here?)
Any suggestions or is it dead in the water?
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" make sure to remove imei and serialno before posting it.

alray said:
Post the output of "fastboot getvar all" make sure to remove imei and serialno before posting it.
Click to expand...
Click to collapse
Thanks for responding so quickly. Find the results below :
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.63.61.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: ORANG001
battery-status: good
battery-voltage: 4163mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b0a25cb2
hbootpreupdate: 11
gencheckpt: 0

elmuziko said:
Thanks for responding so quickly. Find the results below :
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.63.61.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: ORANG001
battery-status: good
battery-voltage: 4163mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b0a25cb2
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
elmuziko said:
Afternoon peeps.
(...)
Allegedly whilst flashing the ROM the USB cable detached.
(...)
It's TAMPERED, RELOCKED, HBOOT-1.55
Click to expand...
Click to collapse
Interesting. How could he flash a rom if the bootloader was relocked? Did he relocked the bootloader after the failed rom flash?
I cannot unlock the phone with the HTC unlock token or fastboot oem unlock
The former recycles power but still says RELOCKED, the latter gives me (ERR Command error !!!)
Click to expand...
Click to collapse
fastboot oem unlock method only works for GPE variant of the M7. All other variants must use htcdev.com method.
You said that the phone is rebooting and still locked when flashing the unlock token. Does it hang at "entering recovery" screen after selecting "yes" to unlock then it reboot or it reboot right after selecting "yes" to unlock (not hanging at "entering recovery" screen)?
If I run fastboot oem rebootRUU the phone cycles power then returns to the bootloader.
Click to expand...
Click to collapse
not good. Phone should reboot to a black screen with silver "HTC" logo when running fastboot oem rebootRUU. Its might confirm a bootloader issue....
I've tried running "RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.exe". This states I'm on image 3.63.61.1 so i'm guessing it can communicate in some ways but sadly it fails to push the image after rebooting the phone back into Bootloader (I assume it's going for the oem recovery here?)
Click to expand...
Click to collapse
Your phone is on .61 firmware CID is ORANG001 (orange UK) and MID is PN0710000. The .401 ruu versions are for CID HTC__001 (carrier unlocked/international), will not work on this phone. You need a .61 ruu and because the phone is s-on, it must the same version or higher (can't downgrade). So you need 3.63.31.1 or above (e.g 4.xx.61.x or 7.xx.61.x). Unfortunately, I can not find any ruu for this version.
The issue with the bootloader stuck at relocked might be the result of relocking the phone with a custom recovery still installed. Stock recovery is needed to unlock the bootloader. Normally this issue can be solved by flashing the same version firmware.zip (3.63.61.1) in ruu mode which will rewrite stock recovery and then enable the phone to be unlocked again. Problem: 1: you need to access ruu mode (which doesn't work) 2: You need the 3.63.31.1 stock firmware.zip (which i can't find on the usual hosting websites).
Make sure you have the latest sdk tools 1.0.32. the command "adb version" will tell you that.
Also make sure you have the latest HTC drivers installed.
Then try to unlock the bootloader again using htcdev.com method. Try to get a new unlock_code.bin by submitting to unlock token again.
Try other usb ports, usb cable.
If you really can't unlock the bootloader or access ruu mode, im afraid there is nothing to do except to send to phone to HTC for repair.

alray said:
Interesting. How could he flash a rom if the bootloader was relocked? Did he relocked the bootloader after the failed rom flash?
Click to expand...
Click to collapse
Yeah so I'm told. When it failed to flash he went through a heap of options including locking the loader for some reason; I have no idea why.
alray said:
fastboot oem unlock method only works for GPE variant of the M7. All other variants must use htcdev.com method.
You said that the phone is rebooting and still locked when flashing the unlock token. Does it hang at "entering recovery" screen after selecting "yes" to unlock then it reboot or it reboot right after selecting "yes" to unlock (not hanging at "entering recovery" screen)?
Click to expand...
Click to collapse
I get the prompt for unlocking, hit yes then the screen goes blank for a few seconds, a white HTC screen then the bootloader with RELOCKED still as the status.
alray said:
The issue with the bootloader stuck at relocked might be the result of relocking the phone with a custom recovery still installed. Stock recovery is needed to unlock the bootloader. Normally this issue can be solved by flashing the same version firmware.zip (3.63.61.1) in ruu mode which will rewrite stock recovery and then enable the phone to be unlocked again. Problem: 1: you need to access ruu mode (which doesn't work) 2: You need the 3.63.31.1 stock firmware.zip (which i can't find on the usual hosting websites).
Click to expand...
Click to collapse
Thanks for looking, I appreciate it. What sites do you use so I can keep an eye on it in the future? I handed it back to him yesterday as a write off and he doesn't seem to care having bought a Nexus 6 recently; with that in mind I might buy it off him with the look to fixing it at a later point.
Thanks again, appreciate your help and advice.