Related
I am trying to return my phone to stock to send it in for replacement (microphone stopped working). I tried to run the Tmo RUU file a couple of times before I found the tutorial on how to properly do it and I am not sure if that may situation worse.
Somehow I wiped the phone and now and am S-On and its locked (showing as tampered). I cannot get the phone to go into any mode that adb can see, although I can access the phone via fastboot commands. What are my options at this point? Is there a way to load a ROM via fastboot? Is there a way to get S-Off and unlock it so I can try the steps to go back to to 100% stock again or am I screwed?
The phone on Tmobile is currently running Hboot 1.44 if that makes a difference.
PLEASE HELP!!!
Can you get to boatloader?
yes, I am in bootloader mode right now. I just successfully unlocked the bootloader from HTCDev. So now I am unlocked with S-On. I also have TWRP 2.6.3.0 and can access recovery. I also was able to set my CID back to T-MOB010.
It seems like I can do anything i want with fastboot commands, but none in adbd. Is there a way to load a rom from fastboot?
an0ther said:
Can you get to boatloader?
Click to expand...
Click to collapse
Your ruu must match your firmware on your phone. If your firmware is higher than your ruu it won't work. What firmware is the stock tmobile and what is your phone os and cid? You can always soff, change cid to stock, rebootRUU and flash stock ruu then s-on and relock.
I am running 3.17 fw and I am not sure what the RUU fw was, most likely 2.17 or something. I did not realize it would be an issue. So what are my options to get it back to stock?
This is what Getvar all says...
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.20.3218.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4255mV
(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: 1.930s
an0ther said:
Your ruu must match your firmware on your phone. If your firmware is higher than your ruu it won't work. What firmware is the stock tmobile and what is your phone os and cid? You can always soff, change cid to stock, rebootRUU and flash stock ruu then s-on and relock.
Click to expand...
Click to collapse
You will have to soff to downgrade firmware on phone. Soff, get stock ruu that matches your cid, rebootRUU and flash stock ruu, s-on, and relock
Can I get S-Off through fastboot? I try and run Revone via HTC One Toolkit and it outputs with error: device not found. I am assuming it is because I cant see it in adb.
an0ther said:
You will have to soff to downgrade firmware on phone. Soff, get stock ruu that matches your cid, rebootRUU and flash stock ruu, s-on, and relock
Click to expand...
Click to collapse
Adb devices , you get nothing? Might need newer adb or try another usb port. Reboot phone and computer. Need adb.
Is adb accessible via the bootloader or recovery? I thought adb only worked when you were booted into a rom. I am completely removing the HTC drivers and installing version 3.0.0.007 to see if it helps with adb.
an0ther said:
Adb devices , you get nothing? Might need newer adb or try another usb port. Reboot phone and computer. Need adb.
Click to expand...
Click to collapse
WiKDMoNKY said:
Is adb accessible via the bootloader or recovery? I thought adb only worked when you were booted into a rom. I am completely removing the HTC drivers and installing version 3.0.0.007 to see if it helps with adb.
Click to expand...
Click to collapse
Adb is accessible from recovery. Try updating HTC drivers and your adb. Sometimes using an USB 3 port causes issues.
Ok, I tried a different computer and now the toolkit is detecting the phone in adb and fastboot, but when I try to push revone it says this adb push revone /data/local/tmp/
failed to copy 'revone' to '/data/local/tmp/': Is a directory
WTF?
I have same problem please help......!!!!
HELLO EVERYONE PLEASE HELP..............
My HTC ONE IS
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
x.xx.666.x - Bell (Canada)
modelid: PN0712000
cidnum: BM___001
I was trying to unroot my device, and i have followed commands as below, i have installed file given at below link
http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One/666/
1) fastboot oem lock
2) fastboot oem rebootRUU
3) fastboot flash zip (firmware).zip
green bar stopped at round about 90% , after waiting 2 minutes i entered
4) fastboot reboot
now phone rebooted but nothing happens only blank screen appears.
i have again unlocked it, i can access bootloader, somehow i have also managed to install recovery,
I HAVE SYSTEM BACKUP IN MY LAPTOP
but i cannot transfer my backup file from laptop to htc one
---------------------------------------
C:\HTCONE>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.666.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34PW904746
(bootloader) imei: 354439053702181
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
--------------------------------------------------
WHAT SHOULD I DO ?? PLEASE HELP
MY PREFRENCE IS TO RESOTRE IT WITH SOTCK FIRMWARE UNROOTED.
Your issue is different than mine, go start your own thread please.
vasa_pratik said:
HELLO EVERYONE PLEASE HELP..............
My HTC ONE IS
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
x.xx.666.x - Bell (Canada)
modelid: PN0712000
cidnum: BM___001
I was trying to unroot my device, and i have followed commands as below, i have installed file given at below link
http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One/666/
1) fastboot oem lock
2) fastboot oem rebootRUU
3) fastboot flash zip (firmware).zip
green bar stopped at round about 90% , after waiting 2 minutes i entered
4) fastboot reboot
now phone rebooted but nothing happens only blank screen appears.
i have again unlocked it, i can access bootloader, somehow i have also managed to install recovery,
I HAVE SYSTEM BACKUP IN MY LAPTOP
but i cannot transfer my backup file from laptop to htc one
---------------------------------------
C:\HTCONE>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.666.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34PW904746
(bootloader) imei: 354439053702181
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
--------------------------------------------------
WHAT SHOULD I DO ?? PLEASE HELP
MY PREFRENCE IS TO RESOTRE IT WITH SOTCK FIRMWARE UNROOTED.
Click to expand...
Click to collapse
you have a tmobile htc one? Me too. I had the same error but was able to get S-OFF by following this guide: http://rootzwiki.com/topic/96098-s-offdowngrade-12753111-to-1275318
If that doesn't work I would
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
boot in to recovery
Wipe -> format all data -> Yes
go back to the main menu and go to advanced then ADB sideload. Swipe to start adb sideload
on pc type adb sideload romname.zip I'd use a stock rom since they don't normally use aroma
adb sideload will automatically install the rom and reboot
now that your phone is functioning normally gain s-off using revone like usual.
try downgrading again.
I followed your steps, but I get a failed on installation of the sideload on the phone.
blu9987 said:
I would
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
boot in to recovery
Wipe -> format all data -> Yes
go back to the main menu and go to advanced then ADB sideload. Swipe to start adb sideload
on pc type adb sideload romname.zip I'd use a stock rom since they don't normally use aroma
adb sideload will automatically install the rom and reboot
now that your phone is functioning normally gain s-off using revone like usual.
try downgrading again.
p.s. you have a tmobile htc one? Me too. I had the same error but was able to get S-OFF by following this guide, which would probably let you skip everything I posted above: http://rootzwiki.com/topic/96098-s-offdowngrade-12753111-to-1275318
Click to expand...
Click to collapse
If you reboot recovery the zip will still be there labeled sideload.zip if you want to try to install it again manually.
or you could try the modified ruu in the link. It worked for me but be advised in general RUUs can be dangerous.
edit: that guide says to be on the android homescreen, i've been able to run RUUs from the locked bootloader screen just fine.
Downloading...
blu9987 said:
If you reboot recovery the zip will still be there labeled sideload.zip if you want to try to install it again manually.
or you could try the modified ruu in the link. It worked for me but be advised in general RUUs can be dangerous.
edit: that guide says to be on the android homescreen, i've been able to run RUUs from the locked bootloader screen just fine.
Click to expand...
Click to collapse
I got ARHD 22 to load via sideload (had to boot back into recovery and install form the sideload.zip). The rom boots and works as it should. Now when I try and relock the bootloader to run the RUU downgrader you linked me to revone is giving me revone failed (error code = 1).
adb push revone /data/local/tmp/
3279 KB/s (648208 bytes in 0.193s)
adb shell chmod 755 /data/local/tmp/revone
adb shell /data/local/tmp/./revone -P
revone v0.2.1
revone failed (error code = 1)
Any ideas?
blu9987 said:
If you reboot recovery the zip will still be there labeled sideload.zip if you want to try to install it again manually.
or you could try the modified ruu in the link. It worked for me but be advised in general RUUs can be dangerous.
edit: that guide says to be on the android homescreen, i've been able to run RUUs from the locked bootloader screen just fine.
Click to expand...
Click to collapse
to relock the bootloader you do fastboot oem lock from the bootloader screen, then you run the ruu i linked if you still want to use revone to get s-off.
When I run fastboot OEM lock it shows as re-locked and something about security at the top of the bootloader screen. Will flashing the ruu fix all that?
blu9987 said:
to relock the bootloader you do fastboot oem lock from the bootloader screen, then you run the ruu i linked if you still want to use revone to get s-off.
Click to expand...
Click to collapse
Sent from my Nexus 7 using Tapatalk 4
Hello,
I've made a mistake. While trying to convert my HTC One to Google Edition, I've mistakenly turned S-ON.
The OS was running fine before it was S-ON. Now it boots up to Homescreen and reboots immediately.
The CID is the one from Google Edition. So I can't flash any RUU's.
I can lock and unlock the Bootloader, or flash another Recovery etc.
But since the OS keep rebooting I cant use ADB and turn S OFF.
missgestalt said:
Hello,
I've made a mistake. While trying to convert my HTC One to Google Edition, I've mistakenly turned S-ON.
The OS was running fine before it was S-ON. Now it boots up to Homescreen and reboots immediately.
The CID is the one from Google Edition. So I can't flash any RUU's.
I can lock and unlock the Bootloader, or flash another Recovery etc.
But since the OS keep rebooting I cant use ADB and turn S OFF.
Click to expand...
Click to collapse
" I've mistakenly turned S-ON." -> why, oh why?? dont you realize that's a one way ticket??
Anyway, are you saying you are able to UNLOCK bootloader, if so there may be hope: Unlock bootloader and use rumrunner to get s-off (AND STAY S-OFF)
missgestalt said:
Hello,
I've made a mistake. While trying to convert my HTC One to Google Edition, I've mistakenly turned S-ON.
The OS was running fine before it was S-ON. Now it boots up to Homescreen and reboots immediately.
The CID is the one from Google Edition. So I can't flash any RUU's.
I can lock and unlock the Bootloader, or flash another Recovery etc.
But since the OS keep rebooting I cant use ADB and turn S OFF.
Click to expand...
Click to collapse
Try sideloading another rom via recovery and flashing it..
Sent from my One using Tapatalk
@nkk71
Any way to use rumrunner without a working OS? As I stated above, I don't access to ADB.
@n1234d
I'll try sideloading via custom recovery. Any ROM suggestions?
missgestalt said:
@nkk71
Any way to use rumrunner without a working OS? As I stated above, I don't access to ADB.
@n1234d
I'll try sideloading via custom recovery. Any ROM suggestions?
Click to expand...
Click to collapse
post your "fastboot getvar all" (excluding IMEI and s/n)
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.62.1700.1
version-misc: PVT SHIP S-ON
serialno: ____
imei: _____
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: GOOGL001
battery-status: good
battery-voltage: 4307mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e82187e
hbootpreupdate: 11
gencheckpt: 0
missgestalt said:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.62.1700.1
version-misc: PVT SHIP S-ON
serialno: ____
imei: _____
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: GOOGL001
battery-status: good
battery-voltage: 4307mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e82187e
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
try installing a custom ROM for 3.62, such as ARHD 31.6 (rooted & unsecured kernel) and get S-Off using rumrunner.
(you may have to try different ROMs as you're on GPE hboot & firmware.)
Runs fine with the mentioned ROM. I'll keep it at S-OFF this time. Thank you very much :good:
missgestalt said:
Runs fine with the mentioned ROM. I'll keep it at S-OFF this time. Thank you very much :good:
Click to expand...
Click to collapse
Happy flashing
And keep S-Off, you are lucky you were able to unlock again, lots of people got stuck with unable to unlock again!!
S-Off = "get out of jail"
So my friend bought and HTC One M7 on Amazon and it was working fine for a few days but it ended up getting stuck on the boot screen. It has TWRP 2.6.0.1 on it but no backup available. I've been working on it for a few days so here are more details.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.07.1540.1
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3717mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
issues i'm having
adb won't recognize it - adb devices - but fastboot and my PC do
I'm not sure if because there is no OS will USB debugging still be disabled?
I'm assuming it is disabled because i can't access it with adb - but ive read you should still be able to push a recovery image regardless.
im unable to fastboot a recovery or boot.img even though they are in the same folder as fastboot.exe and adb.exe
i have the updated HTC Sync Manager and Device Manager sees the phone so i think i have the newest drivers.
my OS says it is 6.07.1540.1 in red and i cant figure out how to even get an OS on there without an OTG stick and it doesnt have a slot for an SD card unless im going crazy.
It says "Tampered" which its said the whole time
and "relocked" after i relocked it with hamsoon's app to try and install the sense 55 RUU and 50 RUU
i cant get it to fastboot anything besides "devices" and rebooting the bootloader.
Any help would be greatly appreciated before I BLOW THIS PHONE UP WITH WILLPOWER ALONE!
Tpuck said:
So my friend bought and HTC One M7 on Amazon and it was working fine for a few days but it ended up getting stuck on the boot screen. It has TWRP 2.6.0.1 on it but no backup available. I've been working on it for a few days so here are more details.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.07.1540.1
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3717mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
issues i'm having
adb won't recognize it - adb devices - but fastboot and my PC do
I'm not sure if because there is no OS will USB debugging still be disabled?
I'm assuming it is disabled because i can't access it with adb - but ive read you should still be able to push a recovery image regardless.
im unable to fastboot a recovery or boot.img even though they are in the same folder as fastboot.exe and adb.exe
i have the updated HTC Sync Manager and Device Manager sees the phone so i think i have the newest drivers.
my OS says it is 6.07.1540.1 in red and i cant figure out how to even get an OS on there without an OTG stick and it doesnt have a slot for an SD card unless im going crazy.
It says "Tampered" which its said the whole time
and "relocked" after i relocked it with hamsoon's app to try and install the sense 55 RUU and 50 RUU
i cant get it to fastboot anything besides "devices" and rebooting the bootloader.
Any help would be greatly appreciated before I BLOW THIS PHONE UP WITH WILLPOWER ALONE!
Click to expand...
Click to collapse
adb wont work in the bootloader, stop trying, only fastboot.
stop worrying about USB debugging, it only applies when you are booted into a working rom and has nothing to do with the bootloader or recovery.
in this order:
unlock the bootloader at http://www.htcdev.com/bootloader register and follow all instructions until unlocked, "TAMPERED" is normal for a previously unlocked bootloader
Change your CID to BS_US001
With your phone showing fastbootUSB on the screen and plugged into the computer, run these commands in a CMD window from within your adb and fastboot folder, phone must be plugged into the computer:
fastboot devices (make sure your serial number shows up)
then:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
when you phone restarts back to the bootloader, do fastboot getvar all again to make sure your cidnum has changed to BS_US001 from CWS__001
and then run this RUU: http://dl3.htc.com/application/RUU_...6_10.33Q.1718.01L_release_420191_signed_2.exe
Tpuck said:
So my friend bought and HTC One M7 on Amazon and it was working fine for a few days but it ended up getting stuck on the boot screen. It has TWRP 2.6.0.1 on it but no backup available. I've been working on it for a few days so here are more details.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.07.1540.1
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 3717mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
issues i'm having
adb won't recognize it - adb devices - but fastboot and my PC do
I'm not sure if because there is no OS will USB debugging still be disabled?
I'm assuming it is disabled because i can't access it with adb - but ive read you should still be able to push a recovery image regardless.
im unable to fastboot a recovery or boot.img even though they are in the same folder as fastboot.exe and adb.exe
i have the updated HTC Sync Manager and Device Manager sees the phone so i think i have the newest drivers.
my OS says it is 6.07.1540.1 in red and i cant figure out how to even get an OS on there without an OTG stick and it doesnt have a slot for an SD card unless im going crazy.
It says "Tampered" which its said the whole time
and "relocked" after i relocked it with hamsoon's app to try and install the sense 55 RUU and 50 RUU
i cant get it to fastboot anything besides "devices" and rebooting the bootloader.
Any help would be greatly appreciated before I BLOW THIS PHONE UP WITH WILLPOWER ALONE!
Click to expand...
Click to collapse
First, unlock the bootloader again. Locking the bootloader to use a ruu in not required when the phone is s-off.
change your cid to BS_US001:
Code:
fastboot oem writecid BS_US001
flash the 7.17.1540.7 ruu.exe posted in my thread (link in my siganture)
@Seanie280672 faster than me this time
Thanks alot guys
I actually just finished unlocking the bootloader and i was able to reinstall 6.07 without the red warning - which is the most ive been able to do in 3 days.
IT still not booting up but hopefully the newest update will let me.
THANK YOU
Tpuck said:
Thanks alot guys
I actually just finished unlocking the bootloader and i was able to reinstall 6.07 without the red warning - which is the most ive been able to do in 3 days.
IT still not booting up but hopefully the newest update will let me.
THANK YOU
Click to expand...
Click to collapse
you need to change your cid, you have a conflict going on, Dev edition firmware 1540 out of your version main, and an AT&T cid number CWS__001. You are also s-off, which is a good thing, never go s-on.
if you follow mine or alray's instructions, your phone will boot fine.
@alray lol
Hey,
So ive changed the CID to BS_US001 and tried to run the .exe like you both suggested (Twice) and i got the 155 error once and it froze at 1/6 sending the second time (i let it run for an hour), ive also tried flashing one of the .zip files alray had and i get 24 parsing android-info fail. Now it says OS-6.07.1540.1 (7.17.1540.7) where i had gotten it to just say 6.07.1540.1 in black. Im gonna try the ruu.exe again is there something else i need to change? - here is what getvar all has now
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.07.1540.1
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: BS_US001
battery-status: good
battery-voltage: 3773mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-eff4f609
hbootpreupdate: 11
gencheckpt: 0
Tpuck said:
Hey,
So ive changed the CID to BS_US001 and tried to run the .exe like you both suggested (Twice) and i got the 155 error once and it froze at 1/6 sending the second time (i let it run for an hour), ive also tried flashing one of the .zip files alray had and i get 24 parsing android-info fail. Now it says OS-6.07.1540.1 (7.17.1540.7) where i had gotten it to just say 6.07.1540.1 in black. Im gonna try the ruu.exe again is there something else i need to change? - here is what getvar all has now
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.07.1540.1
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: BS_US001
battery-status: good
battery-voltage: 3773mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-eff4f609
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
try to flash the 6.07.1540.2 full firmware from my thread
Code:
fastboot oem rebootRUU
fastboot flash zip Firmware_6.07.1540.2.zip
fastboot flash zip Firmware_6.07.1540.2.zip
fastboot reboot-bootloader
and then launch the ruu again. Should work.
3rd time was the charm. Got it up and running, thank you so much for your help. Now i'm totally interested in this stuff so i guess it was worth 3 days of headaches to find that out.
Hi all,
I apologise for this as it seems there are a few soft brick posts to do with the M7 here. I've tried following them but I'm not having much success.
Last night I decided to root my phone in an effort to find a good ROM that looked good but also didn't have the same battery drain as the stock HTC Lollipop update.
Everything was ok to start with. Got the unlock code, followed a process on HTConeroot.com. Other than TWRP probably not being the latest version, all seemed ok. After SuperSU wouldn't start due to the incorrect binaries, I tried to update it through twrp and the trouble started. It would not start the OS and, being the noob, I pressed 'wipe' on twrp and i have no arrived at the following:
I am currently in a boot loop. It will not start the OS. I cannot gain access to recovery mode in TWRP either as the screen flashes up team winning and then just restarts. I can gain access to the Hboot screen and from there can do a USB fastboot link. However, I can't do anything with ADB as it doesn't recognise any device as being connected. Fastboot prompt works fine though.
In a nutshell, I'm looking to get the phone working again. I don't really need to go back to a stock rom - I was looking at google play edition or cyanogen (though I'm told the latter isn't *that* stable). Is someone able to help me?
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Phone is stating *unlocked* and *tampered* with S-ON.
Honest989 said:
Hi all,
I apologise for this as it seems there are a few soft brick posts to do with the M7 here. I've tried following them but I'm not having much success.
Last night I decided to root my phone in an effort to find a good ROM that looked good but also didn't have the same battery drain as the stock HTC Lollipop update.
Everything was ok to start with. Got the unlock code, followed a process on HTConeroot.com. Other than TWRP probably not being the latest version, all seemed ok. After SuperSU wouldn't start due to the incorrect binaries, I tried to update it through twrp and the trouble started. It would not start the OS and, being the noob, I pressed 'wipe' on twrp and i have no arrived at the following:
I am currently in a boot loop. It will not start the OS. I cannot gain access to recovery mode in TWRP either as the screen flashes up team winning and then just restarts. I can gain access to the Hboot screen and from there can do a USB fastboot link. However, I can't do anything with ADB as it doesn't recognise any device as being connected. Fastboot prompt works fine though.
In a nutshell, I'm looking to get the phone working again. I don't really need to go back to a stock rom - I was looking at google play edition or cyanogen (though I'm told the latter isn't *that* stable). Is someone able to help me?
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Phone is stating *unlocked* and *tampered* with S-ON.
Click to expand...
Click to collapse
Edit your post above and remove your IMEI and Serialno, keep these numbers private.
ADB doesn't work from bootloader, only fastboot will. ADB is only available from a custom recovery or from a booted OS with USB debug enabled.
You'll first need a working recovery so reflash twrp recovery:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Thanks - I think I have it... I part way followed this thread - which means i've relocked the bootloader :/
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
however, I need to find an RUU of 7.19.401.30 - thought I'd found the right version only to get blocked at model number. I'd got the .22 instead.....
To date, I've not been able to...
Honest989 said:
Thanks - I think I have it... I part way followed this thread - which means i've relocked the bootloader :/
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
however, I need to find an RUU of 7.19.401.30 - thought I'd found the right version only to get blocked at model number. I'd got the .22 instead.....
To date, I've not been able to...
Click to expand...
Click to collapse
There is no 7.19.401.30 ruu, the latest one is 7.19.401.22 and can't be flashed on your phone since its a downgrae in version (requires s-off)
Unlock your bootloader and flash your custom rom.
Thanks - I'm now in a stable TWRP env. I now need to figure out how to push a rom across to the phone.
Next question. Does s-mode have to be off. If so, how is this achieved via fastboot? (or is it a case of more tools and tinkering). As I've already made a hash of things once, I'm loath to do this........
Honest989 said:
Thanks - I'm now in a stable TWRP env. I now need to figure out how to push a rom across to the phone.
Next question. Does s-mode have to be off. If so, how is this achieved via fastboot? (or is it a case of more tools and tinkering). As I've already made a hash of things once, I'm loath to do this........
Click to expand...
Click to collapse
You don't need s-off to flash a rom, if you want s-off for going back to stock using the ruu (downgrade) you'll first need a working rom. S-OFF can only be achieved from a working rom using Sunshine S-OFF
To push a rom to your phone, if you have a recent twrp version (2.8+) just boot your phone in recovery mode connected to your pc using the usb cable and you should be able to see your phone storage (like if it was a usb stick). just drag and drop your rom.zip to your phone and then in twrp select "install" and flash the rom. If you are one an older version of twrp, use adb to push the rom to your phone:
Code:
adb push name_of_rom.zip /sdcard
Thanks guys what solved it was:
Up to date version of TWRP
Latest version of Android revolution.
The reson it wasn't booting or providing some sort of DR was because I had somehow wiped everything from the phone. By way of complete fluke, I now have a rooted phone running on a completely clean install directory. Remind me to back up later on.
I post as a final measure, as after two days of being unable to use my AT&T HTC One M7, I am in need of help. Badly. I have tried everything I could find, it either errors, fails, or crashes, nothing is working for me. I am without an OS, and have an unlocked bootloader, TWRP, and sleep deprivation. This all started when attempting to update to the newest Android available, and has left me stranded with a soft brick. If anyone has any ideas for me, PLEASE speak up. My phone was working fine until yesterday, and I am NOT interested in going back to my Iphone.
ErrorSuccess said:
I post as a final measure, as after two days of being unable to use my AT&T HTC One M7, I am in need of help. Badly. I have tried everything I could find, it either errors, fails, or crashes, nothing is working for me. I am without an OS, and have an unlocked bootloader, TWRP, and sleep deprivation. This all started when attempting to update to the newest Android available, and has left me stranded with a soft brick.
Click to expand...
Click to collapse
What issue the update caused exactly? The phone is stick at the HTC splash screen?
Post the output of "fastboot getvar all" (remove you irmei/sn before posting)
Is you bootloader locked/unlocked?
alray said:
What issue the update caused exactly? The phone is stick at the HTC splash screen?
Post the output of "fastboot getvar all" (remove you irmei/sn before posting)
Is you bootloader locked/unlocked?
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4M.32.3218.06
version-cpld: None
version-microp: None
version-main: 7.23.502.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4207mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
The phone will freeze at the htc splash, and then reboot into TWRP.
Unlocked
1st install any lollipop recovery, latest would be good
2nd search for latest RUU.ZIP (Lollipop) and install with "htc_fastboot.exe" (google for these 2 terms!, follow the htc_fastboot.exe commands instructions which should be explained on that site of the file)
3rd be happy.
ErrorSuccess said:
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4M.32.3218.06
version-cpld: None
version-microp: None
version-main: 7.23.502.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4207mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
The phone will freeze at the htc splash, and then reboot into TWRP.
Unlocked
Click to expand...
Click to collapse
This is the typical problem of updating a lollipop rooted rom. Relock your bootloader and flash the latest at&t ruu, then install all updates (if any) before unlocking and rootimg
alray said:
This is the typical problem of updating a lollipop rooted rom. Relock your bootloader and flash the latest at&t ruu, then install all updates (if any) before unlocking and rootimg
Click to expand...
Click to collapse
Thank you so much! This finally fixed it. I tried flashing the ruu, but I didnt realize my bootloader had to be relocked.
ErrorSuccess said:
Thank you so much! This finally fixed it. I tried flashing the ruu, but I didnt realize my bootloader had to be relocked.
Click to expand...
Click to collapse
yep when s-on you must re-lock the bootloader to flash a RUU