Guys badly need help here, my One has been unoperational for a week now. I converted it to GPE and updated to 4.4. 2 days ago I want to restore it to its factory ROM, restoring its warranty as well through this tutorial: http://htc-one.wonderhowto.com/how-to/return-your-rooted-unlocked-htc-one-back-factory-settings-for-warranty-repairs-0149204/. Unfortunately after performing step 3, my phone rebooted and is stuck in bootloader with these details:
*** TAMPERED ***
*** RELOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS- 3.58.1700.5
eMMC-boot 2048MB
I can't boot to recovery, when I connect it to PC only fastboot commands are working. It's not detected by ADB. Everytime I flash a new recovery like cwm or twrp it returns with this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Everytime I flash the RUU file it returns with this:
I tried the factory reset but it just reboots the phone..I can't even to its installed ROM.
Pls help me to fix my phone.. :'(
ClydeWinux said:
Guys badly need help here, my One has been unoperational for a week now. I converted it to GPE and updated to 4.4. 2 days ago I want to restore it to its factory ROM, restoring its warranty as well through this tutorial: http://htc-one.wonderhowto.com/how-to/return-your-rooted-unlocked-htc-one-back-factory-settings-for-warranty-repairs-0149204/. Unfortunately after performing step 3, my phone rebooted and is stuck in bootloader with these details:
*** TAMPERED ***
*** RELOCKED ***
M7_UK PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS- 3.58.1700.5
eMMC-boot 2048MB
I can't boot to recovery, when I connect it to PC only fastboot commands are working. It's not detected by ADB. Everytime I flash a new recovery like cwm or twrp it returns with this:
Everytime I flash the RUU file it returns with this:
I tried the factory reset but it just reboots the phone..I can't even to its installed ROM.
Pls help me to fix my phone.. :'(
Click to expand...
Click to collapse
Can you unlock your boot loader via
fastboot oem unlock
Or
via HTCDev bootloader unlocker?
I will get there said:
Can you unlock your boot loader via
fastboot oem unlock
Or
via HTCDev bootloader unlocker?
Click to expand...
Click to collapse
This is the response when I try the command "fastboot oem unlock"
And the HTCDev Unlock, with no response on my phone. No unlock confirmation, it stays in bootloader.
I am afraid my phone is already dead locked.
You can't flash RUU zips with S-On, you need the RUU.exe for your region/carrier.
If you can get into fastboot then its very unlikely that it is dead.
Sent from my HTC One using Tapatalk
swag1981 said:
You can't flash RUU zips with S-On, you need the RUU.exe for your region/carrier.
If you can get into fastboot then its very unlikely that it is dead.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
If it's for his MID & CID, he can flash a ruu.zip. IMHO
ClydeWinux said:
This is the response when I try the command "fastboot oem unlock"
And the HTCDev Unlock, with no response on my phone. No unlock confirmation, it stays in bootloader.
I am afraid my phone is already dead locked.
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n)
nkk71 said:
If it's for his MID & CID, he can flash a ruu.zip. IMHO
can you post a "fastboot getvar all" (remove IMEI and s/n)
Click to expand...
Click to collapse
Thanks for your reply @nkk71, here's the details I got:
(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.58.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4252mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Since your bootloader is RELOCKED its normal that you cannot flash a custom recovery. Perform a factory reset from the Bootloader and try again with the HTCDev unlock.
Ivanovic said:
Since your bootloader is RELOCKED its normal that you cannot flash a custom recovery. Perform a factory reset from the Bootloader and try again with the HTCDev unlock.
Click to expand...
Click to collapse
Hi @Ivanovic, I have tried selecting factory reset from bootloader but it just reboots the phone to bootloader.
ClydeWinux said:
Hi @Ivanovic, I have tried selecting factory reset from bootloader but it just reboots the phone to bootloader.
Click to expand...
Click to collapse
Why did you relock the bootloader? Before relocking did you have custom or stock recovery?
Ivanovic said:
Why did you relock the bootloader? Before relocking did you have custom or stock recovery?
Click to expand...
Click to collapse
It was unlocked when it was still running on GPE 4.4. When I tried to return to factory ROM, I accidentally "RELOCKED" it instead of achieving "LOCKED" status, as it is instructed here: http://htc-one.wonderhowto.com/how-to/return-your-rooted-unlocked-htc-one-back-factory-settings-for-warranty-repairs-0149204/
Re-unlocking with HTCDev does not work at all. @Ivanovic
Yes I installed TWRP before relocking, but I can't boot on recovery now..
-wrong post, sorry-
ClydeWinux said:
It was locked when it was still running on GPE 4.4. When I tried to return to factory ROM, I accidentally "RELOCKED" it instead of achieving "LOCKED" status, as it is instructed here: http://htc-one.wonderhowto.com/how-to/return-your-rooted-unlocked-htc-one-back-factory-settings-for-warranty-repairs-0149204/
Re-unlocking with HTCDev does not work at all. @Ivanovic
Click to expand...
Click to collapse
So you were S-OFF and then after relocking the bootloader you turned to S-ON?
almost same situtation here;.
http://forum.xda-developers.com/showthread.php?t=2554284
Click to expand...
Click to collapse
and here
http://forum.xda-developers.com/showthread.php?p=48079963
Click to expand...
Click to collapse
and here
http://forum.xda-developers.com/showthread.php?t=2551491
Click to expand...
Click to collapse
i hate that "Loading custom splash failed" error.
Ivanovic said:
So you were S-OFF and then after relocking the bootloader you turned to S-ON?
Click to expand...
Click to collapse
Yes I was at S-OFF and turned to S-ON as instructed. I have no idea that would change everything..
I bought it yesterday in a repair shop, but they said its already "DEADBOOT" which I believe not true as I can still send commands and communicate with the phone through FASTBOOT, but not with ADB.. @Ivanovic
ClydeWinux said:
Yes I was at S-OFF and turned to S-ON as instructed. I have no idea that would change everything..
I bought it yesterday in a repair shop, but they said its already "DEADBOOT" which I believe not true as I can still send commands and communicate with the phone through FASTBOOT, but not with ADB.. @Ivanovic
Click to expand...
Click to collapse
ADB works only withing Recovery or when the phone has booted to normal state. Either way ADB wasnt gonna help you. You need to unlock the bootloader somehow and flash a custom recovery. For unlocking did you try fastboot oem unlock or the unlock token command?
Although it says you need s-off please try the following:
1.Download stock zip RUU for 4.4 http://d-h.st/Kmq
2.Boot into bootloader and choose fastboot
3.Make sure fastboot works by typing fastboot devices
4.type fastboot oem rebootRUU
5.type fastboot flash zip RUU-HTC_One_GE-4.4-3.58.1700.5.zip
6.it will fail so type again fastboot flash zip RUU-HTC_One_GE-4.4-3.58.1700.5.zip
Ivanovic said:
ADB works only withing Recovery or when the phone has booted to normal state. Either way ADB wasnt gonna help you. You need to unlock the bootloader somehow and flash a custom recovery. For unlocking did you try fastboot oem unlock or the unlock token command?
Although it says you need s-off please try the following:
1.Download stock zip RUU for 4.4 http://d-h.st/Kmq
2.Boot into bootloader and choose fastboot
3.Make sure fastboot works by typing fastboot devices
4.type fastboot oem rebootRUU
5.type fastboot flash zip RUU-HTC_One_GE-4.4-3.58.1700.5.zip
6.it will fail so type again fastboot flash zip RUU-HTC_One_GE-4.4-3.58.1700.5.zip
Click to expand...
Click to collapse
I have tried all of this but nothing seems to work.
Response with "fastboot oem unlock" command:
Response with HTCDev Unlock:
but this doesn't do anything to my phone, no unlock confirmation.
Response when flashing the RUU zip:
@Ivanovic
ClydeWinux said:
I have tried all of this but nothing seems to work.
Response with "fastboot oem unlock" command:
Response with HTCDev Unlock:
but this doesn't do anything to my phone, no unlock confirmation.
Response when flashing the RUU zip:
@Ivanovic
Click to expand...
Click to collapse
Hey, since you are able to get to fastboot, your phone is not dead
So dont panic
Do you hav the htc Unlock_code.bin which you got from your email adress when you first unlocked your bootloader using htcDev?
prunzzz said:
Hey, since you are able to get to fastboot, your phone is not dead
So dont panic
Do you hav the htc Unlock_code.bin which you got from your email adress when you first unlocked your bootloader using htcDev?
Click to expand...
Click to collapse
@prunzzz Yes I still have the .bin file..I've tried unlocking using it but same result, no response from the phone..
Can you give a bit more history? Correct me if I'm off...
HBOOT: M7_UK PVT SHIP S-ON RH
MID: (PN0714000) is Australia/Hong Kong/Singapore
CID: (GOOGL001) is Google
Firmware: (3.58.1700.5) is Google
My primary question is UK hboot and MID. Phone is from Australia/Hong Kong/Singapore region, you S-OFF, you changed CID, you flashed google firmware+rom, and you flashed UK hboot?
Thoughts: wrong MID and hboot could be causing RUU and unlock to fail verification?
I am in the same boat i have tried everything i can think of and i cannot seem to get my phone to work. I have tried multiple RUU's with no luck i cant flash them and before i relocked my bootloader i tried different recoveries with no luck. Now when i try to flash a boot_signed.img it says signature failed. Hopefully someone will have a solution.
Related
Hello,
i'm reading here for some weeks and this forum helped me much so far. Now I made a bad mistake while flashing the latest firmware on my One and it seems that I have bricked it.
What have I done?
I used ARHD 5.1 GE on my One with an older firmware. Before that I was using ARHD 4.1. Data of my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4260mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I changed to SuperCID, before that I had VODAP102. Bootloader is relocked.
After flashing latest firmware, my sdcard got wiped. So I have no backups or any other data on my phone. The phone stops booting after the white screen with the "HTC" logo and shows a turquoise color with little stripes and nothing happens.
I tried to flash another firmware, as you can see in the phone's details. That worked, but changed nothing. I can't install a rom, because adb doesn't find my device, but fastboot does. I tried several HTC-drivers and cables and USB-slots. Nothing.
I read several How-To's but I got stuck with this. Even tried to install the 1.28.401.7 RUU, but that stops with Error 155. After first time that error occured I relocked my bootloader, but that didn't help. I can't push files to the phone, because adb doesn't work.
Now only one thing left: Asking you for help. I'm somewhat frustrated.
Peko
pekomane said:
Hello,
i'm reading here for some weeks and this forum helped me much so far. Now I made a bad mistake while flashing the latest firmware on my One and it seems that I have bricked it.
What have I done?
I used ARHD 5.1 GE on my One with an older firmware. Before that I was using ARHD 4.1. Data of my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
I changed to SuperCID, before that I had VODAP102. Bootloader is relocked.
After flashing latest firmware, my sdcard got wiped. So I have no backups or any other data on my phone. The phone stops booting after the white screen with the "HTC" logo and shows a turquoise color with little stripes and nothing happens.
I tried to flash another firmware, as you can see in the phone's details. That worked, but changed nothing. I can't install a rom, because adb doesn't find my device, but fastboot does. I tried several HTC-drivers and cables and USB-slots. Nothing.
I read several How-To's but I got stuck with this. Even tried to install the 1.28.401.7 RUU, but that stops with Error 155. After first time that error occured I relocked my bootloader, but that didn't help. I can't push files to the phone, because adb doesn't work.
Now only one thing left: Asking you for help. I'm somewhat frustrated.
Peko
Click to expand...
Click to collapse
1- remove IMEI and s/n
2- install latest TWRP 2.6.3.3 (needed for 4.4 roms)
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
3- confirm adb working in TWRP now, and unlock using: http://forum.xda-developers.com/showthread.php?t=2475914 or "revone -u"
(you don't need to relock if you're s-off)
4- push, sideload, or OTG a ROM and install
5- error 155 occurs due to hboot 1.55+, you'll need to downgrade to 1.44 to run RUU
nkk71 said:
1- remove IMEI and s/n
2- install latest TWRP 2.6.3.3 (needed for 4.4 roms)
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
3- confirm adb working in TWRP now, and unlock using: http://forum.xda-developers.com/showthread.php?t=2475914 or "revone -u"
(you don't need to relock if you're s-off)
4- push, sideload, or OTG a ROM and install
5- error 155 occurs due to hboot 1.55+, you'll need to downgrade to 1.44 to run RUU
Click to expand...
Click to collapse
Step 1 already edited, right after posting...
Thanks for now, I have to try that when I am at home. I will post here, if it worked or not.
pekomane said:
Step 1 already edited, right after posting...
Thanks for now, I have to try that when I am at home. I will post here, if it worked or not.
Click to expand...
Click to collapse
no problem, IF you're gonna end up using RUU, you need to downgrade to this hboot: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <- just in case the first one says "failed flush again"
fastboot reboot-bootloader
and run the RUU, should work fine.
nkk71 said:
no problem, IF you're gonna end up using RUU, you need to downgrade to this hboot: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <- just in case the first one says "failed flush again"
fastboot reboot-bootloader
and run the RUU, should work fine.
Click to expand...
Click to collapse
Thanks for that, but using RUU was only one way I thought of to get my phone working again, because adb push and sideload don't work. If the way you mentioned in your first post works, then I will be absolutely fine without using RUU. Otherwise I will try the RUU option.
It worked! Thanks for your help! :good:
pekomane said:
It worked! Thanks for your help! :good:
Click to expand...
Click to collapse
Cool, if everything OK now, could you edit main thread title to include [SOLVED], Danke
Done.
By the way, it was the first option you posted that did the trick.
pekomane said:
Done.
By the way, it was the first option you posted that did the trick.
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk
Hello nkk7
S-OFF by rumrunners
bootloader 1.55
Version main 3.62.401.1
Cid HTC001
Mid pn0710000
I have tu use ruu to go back to stock can u please give me step by step guide in sequence pls
Pls
And there is no ruu for 3.62.401.1
Thus I will have downgrade that's why I am confused
Pls give me step by step info
shurahbil said:
Hello nkk7
S-OFF by rumrunners
bootloader 1.55
Version main 3.62.401.1
Cid HTC001
Mid pn0710000
I have tu use ruu to go back to stock can u please give me step by step guide in sequence pls
Pls
And there is no ruu for 3.62.401.1
Thus I will have downgrade that's why I am confused
Pls give me step by step info
Click to expand...
Click to collapse
follow my guide in my signature, there is a RUU.EXE available for CID: HTC__001 and MID: PN0710000 (so you can follow the RUU.EXE procedure)
in my opinion do NOT GO S-ON!!
nkk71 said:
follow my guide in my signature, there is a RUU.EXE available for CID: HTC__001 and MID: PN0710000 (so you can follow the RUU.EXE procedure)
in my opinion do NOT GO S-ON!!
Click to expand...
Click to collapse
Done ok ty
Why do not go s-on
Because you will close an avenue of troubleshooting if you are S-ON..
Hey guys
I've got a few questions here:
I want to ask if it is possible to convert my device into a Developer edition.
I want to set my device back to Stock so I have to use a RUU...Right?
I've already tried it but something had gone wrong.
I used this tutorial....but afterward I wasn't able to install the Ota-Update (4.4.2) (from 4.4 to 4.4.2)
My device is running on ARHD 52.0
Hboot 1.56
SuperCid
S-Off
Thanks in advance for your answers
Boachti said:
Hey guys
I've got a few questions here:
I want to ask if it is possible to convert my device into a Developer edition.
I want to set my device back to Stock so I have to use a RUU...Right?
I've already tried it but something had gone wrong.
I used this tutorial....but afterward I wasn't able to install the Ota-Update (4.4.2) (from 4.4 to 4.4.2)
My device is running on ARHD 52.0
Hboot 1.56
SuperCid
S-Off
Thanks in advance for your answers
Click to expand...
Click to collapse
can you please post you fastboot getvar all minus IMEI/Sn. I converted my phone several time so I can assist you with this.
Boachti said:
Hey guys
I've got a few questions here:
I want to ask if it is possible to convert my device into a Developer edition.
I want to set my device back to Stock so I have to use a RUU...Right?
I've already tried it but something had gone wrong.
I used this tutorial....but afterward I wasn't able to install the Ota-Update (4.4.2) (from 4.4 to 4.4.2)
My device is running on ARHD 52.0
Hboot 1.56
SuperCid
S-Off
Thanks in advance for your answers
Click to expand...
Click to collapse
Look, if your intention is to convert ur HTC One to a Dev. Edition, then you simply have to follow this guide:
http://forum.xda-developers.com/showthread.php?t=2541082
The RUU which you need to flash is:
http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
S-OFF is required, which you have already. However, you will keep a few things in mind:
1) Windows 7 must only be used. 8.1 is NOT supported
2) Depending on your phone, you may have to alter model and carrier id. Post your getvar all, for more assistance
3) Your HBOOT version will need a downgrade to 1.44. The method is mentioned in the guide
4) You cannot OTA update with a custom recovery. The guru reset rom and stock recovery are required for OTAs
raghav kapur said:
The guru reset rom and stock recovery are required for OTAs
Click to expand...
Click to collapse
What? That doesn't make any sense, if he flash a ruu his phone will be stock, no needs to flash a guru reset rom after....
+ he doesn't need to downgrade hboot to 1.44 if he use a ruu.zip instead of a ruu.exe like this one
so he will only need to change CID and MID (if required) before flashing the ruu.zip... simple as that.
To change CID:
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
TO change MID to PN0712000 use this tool with custom recovery:http://forum.xda-developers.com/showthread.php?t=2535365
then flash the ruu
Code:
fastboot oem rebootRUU
fastboot flash zip <name_of_ruu>.zip
fastboot flash zip <name_of_ruu>.zip
fastboot reboot
alray said:
What? That doesn't make any sense, if he flash a ruu his phone will be stock, no needs to flash a guru reset rom after....
+ he doesn't need to downgrade hboot to 1.44 if he use a ruu.zip instead of a ruu.exe like this one then windows 8.1 is supported (for the zip method) as said in the guide you linked
so he will only need to change CID and MID (if required) before flashing the ruu.zip... simple as that.
To change CID:
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
TO change MID to PN0712000 use this tool with custom recovery:http://forum.xda-developers.com/showthread.php?t=2535365
then flash the ruu
Code:
fastboot oem rebootRUU
fastboot flash zip <name_of_ruu>.zip
fastboot flash zip <name_of_ruu>.zip
fastboot reboot
Click to expand...
Click to collapse
What I meant was that the OTA cannot be installed on ARHD
And, ok, I wasn't aware that the HBOOT doesn't need to be downgraded through zip method
raghav kapur said:
What I meant was that the OTA cannot be installed on ARHD
Click to expand...
Click to collapse
ok
raghav kapur said:
And, ok, I wasn't aware that the HBOOT doesn't need to be downgraded through zip method
Click to expand...
Click to collapse
I wasn't aware of this too, nkk71 told me last week.
from nkk71's guide, look at the s-off column:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2) RUU.ZIP (Windows7, Mac, Linux): http://www.htc1guru.com/downloads/ruu-zip-downloads/ <- this is now the preferred method instead of RUU.EXE
Click to expand...
Click to collapse
no hboot downgrade require for the zip method as per his guide:
http://forum.xda-developers.com/showpost.php?p=47794203&postcount=3
Thank you very much
I will post getvar ass soon as I'm back home
Thanks
alray said:
can you please post you fastboot getvar all minus IMEI/Sn. I converted my phone several time so I can assist you with this.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.22.3263.14
version-cpld: None
version-microp: None
version-main: 4.06.1540.3
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 3823mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bee46337
hbootpreupdate: 11
gencheckpt: 0
Boachti said:
version: 0.5
version-bootloader: 1.56.0000
version-baseband: 4A.22.3263.14
version-cpld: None
version-microp: None
version-main: 4.06.1540.3
version-misc: PVT SHIP S-OFF
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 3823mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bee46337
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Change your CID to BS_US001:
boot your phone in bootloader, select fastboot and connect usb cable to computer. From your adb/fastboot folder, open a cmd prompt.
Code:
fastboot oem writecid BS_US001
fastboot reboot-bootloader
confirm your cid is now BS_US001:
Code:
fastboot oem readcid
the output should be BS_US001
Install latest TWRP recovery (you can skip this if your version is 2.6.3.0 and above)
download and save latest twrp to your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
boot phone in twrp recovery (main menu)
download this MID change tool and save it to you adb/fastboot folder push it to your sdcard
Code:
adb push MID_Change_1.01.zip /sdcard/
then in twrp menu select ''install'' and chose the MID_Change_1.01.zip
Follow graphical interface instruction and change MID to PN0712000
reboot phone in bootloader/fastboot usb mode
download this ruu.zip and save it to your adb/fasboot folder
flash the ruu
Code:
fastboot oem rebootRUU
fastboot flash zip <name_of_ruu_file>.zip
fastboot flash zip <name_of_ruu_file>.zip <------ do it again
fastboot reboot
boot phone normally, download and install ota.
Currently S-OFF and UNLOCKED.
Just ran a 4.4.2 RUU via zip, rom is back to stock, but recovery isn't working, red triangle.
When I try to flash the firmware.zip, it returns
E:\Tools\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot flash zi
p firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (42459 KB)...
OKAY [ 2.955s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.990s
Click to expand...
Click to collapse
I also tried extracting the boot.img and recovery.img and flashing them separately, but I still get the red triangle when trying to enter recovery.
Need to return my HTC One to 100% stock to fix the purple camera issue, tried everything I could find, please help!
(Warranty expires in a week)
An RUU.zip has to be run as follows, not from recovery
Make sure the RUU.zip is in your adb folder.
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. *You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. *When the output in the command window is complete, you can reboot:
fastboot reboot
PS the red triangle is stock recovery
(Power button + volume up to enter recovery ).
Sent from my GT-I9505 using XDA Premium 4 mobile app
PLZ HELP
bored_stupid said:
An RUU.zip has to be run as follows, not from recovery
Make sure the RUU.zip is in your adb folder.
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. *You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. *When the output in the command window is complete, you can reboot:
fastboot reboot
PS the red triangle is stock recovery
(Power button + volume up to enter recovery ).
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just tried running both the firmware.zip and ruu.zip flash commands twice, same result!
Still can't return to stock recovery(the really simple one).
Current specs:
*** LOCKED ***
M7_U PUT SHIP S-OFF RH
CID-HTC__621
HBOOT-1.56.0000
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-4.20.709.14
eMMC-boot 2048MB
Click to expand...
Click to collapse
Names of the files I used
firmware.zip [MD5：19c0fd52eb90d6e60ff2a6e9c1ee035a]
RUU_M7_U_K44_SENSE55_MR_hTC_Asia_TW_4.20.709.14.zip [MD5：04110c3e9152faf91ba661e68b34ec42]
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's
Why was you trying to flash a firmware.zip.
Also if your trying to return to full stock for warranty purpose, your phone needs to be locked not relocked and you must also remove tampered.
Follow this guide to achieve this
http://forum.xda-developers.com/showthread.php?t=2541082
And also look here for stock rom
http://www.htc1guru.com/guides/return-stock-guide/
Sent from my GT-I9505 using XDA Premium 4 mobile app
bored_stupid said:
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's
Why was you trying to flash a firmware.zip.
Also if your trying to return to full stock for warranty purpose, your phone needs to be locked not relocked and you must also remove tampered.
Follow this guide to achieve this
http://forum.xda-developers.com/showthread.php?t=2541082
And also look here for stock rom
http://www.htc1guru.com/guides/return-stock-guide/
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm trying to flash a firmware.zip because I failed at flashing the stock recovery individually.
Commands... I used just the usual ones, but tried them all at different states: LOCKED, RELOCKED, UNLOCKED...
fastboot flash recovery recovery.img
fastboot erase cache
LOCK/UNLOCK from this thread: http://forum.xda-developers.com/showthread.php?t=2475914
Also this corrupted data partition thing by Mike of ARHD: http://android-revolution-hd.blogspot.tw/2013/10/fix-data-htc-one.html
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.709.14
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 4106mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I can successfully flash TWRP recovery, but no luck with any other stock recovery...
(flashed the extracted boot.img from the same firmware.zip before flashing the recovery.img)
theplaypig said:
Just ran a 4.4.2 RUU via zip, rom is back to stock, but recovery isn't working, red triangle.
Click to expand...
Click to collapse
That is the stock recovery!!
nkk71 said:
That is the stock recovery!!
Click to expand...
Click to collapse
Isn't it supposed to be a very simple menu?
If it is stock recovery, how do I use it? I tried pressing POWER+VOL_UP as mentioned above but it just kept rebooting!
theplaypig said:
Isn't it supposed to be a very simple menu?
If it is stock recovery, how do I use it? I tried pressing POWER+VOL_UP as mentioned above but it just kept rebooting!
Click to expand...
Click to collapse
stock recovery:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
to get to this menu:
you need to briefly press POWER + VOLUP (or POWER+UP+DOWN), you may need to try a few times to get the timing correct.
nkk71 said:
stock recovery:
to get to this menu:
you need to briefly press POWER + VOLUP (or POWER+UP+DOWN), you may need to try a few times to get the timing correct.
Click to expand...
Click to collapse
Thanks I just looked it up and it's working. It was correct the whole time, I went full retard.
theplaypig said:
Thanks I just looked it up and it's working. It was correct the whole time, I went full retard.
Click to expand...
Click to collapse
no problem
nkk71 said:
no problem
Click to expand...
Click to collapse
When I reboot, I get a black background with red HTC and white text, and then I get the usual boot animation(with sound).
Is the first part stock or custom? Can't remember if I modded it...
theplaypig said:
When I reboot, I get a black background with red HTC and white text, and then I get the usual boot animation(with sound).
Is the first part stock or custom? Can't remember if I modded it...
Click to expand...
Click to collapse
Can you post a pic of the screen.
Did you follow nkk71's guide for returning to full stock?
Sent from my GT-I9505 using XDA Premium 4 mobile app
bored_stupid said:
Can you post a pic of the screen.
Did you follow nkk71's guide for returning to full stock?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Here's a video: http://youtu.be/jUMIhA_mKE4
I had to downgrade my hboot from 1.56 to 1.44 to get S-ON, I suppose I should upgrade it to the latest version so it matches everything else?
Edit:
I followed this guide: http://www.htc1guru.com/guides/return-stock-guide/
theplaypig said:
Here's a video: http://youtu.be/jUMIhA_mKE4
I had to downgrade my hboot from 1.56 to 1.44 to get S-ON, I suppose I should upgrade it to the latest version so it matches everything else?
Edit:
I followed this guide: http://www.htc1guru.com/guides/return-stock-guide/
Click to expand...
Click to collapse
that video show's correct (stock) bootup and powerdown animations, but a (possibly) modded bootsplash.... that would be partition mmcblk0p13 and can't be flashed without S-Off
though an RUU should have taken care of that!!
PS: I say possibly, because maybe your version (HTC__621) is supposed to be like that.
nkk71 said:
that video show's correct (stock) bootup and powerdown animations, but a (possibly) modded bootsplash.... that would be partition mmcblk0p13 and can't be flashed without S-Off
though an RUU should have taken care of that!!
PS: I say possibly, because maybe your version (HTC__621) is supposed to be like that.
Click to expand...
Click to collapse
I ran the RUU via zip not exe, maybe that's the issue? I think I'll have to S-OFF again to fix it...
And the hboot part? Should I upgrade it to a matching version for a valid warranty?
theplaypig said:
I ran the RUU via zip not exe, maybe that's the issue? I think I'll have to S-OFF again to fix it...
And the hboot part? Should I upgrade it to a matching version for a valid warranty?
Click to expand...
Click to collapse
doesn't matter if it was a ruu.zip or ruu.exe both would/should change the bootsplash... can you check the zip if it has "splash1.nb0" that would be the bootsplash.
ruu (zip or exe) contain everything so hboot and bootsplash should already by stock.
maybe it's just supposed to be that way for you??
nkk71 said:
doesn't matter if it was a ruu.zip or ruu.exe both would/should change the bootsplash... can you check the zip if it has "splash1.nb0" that would be the bootsplash.
ruu (zip or exe) contain everything so hboot and bootsplash should already by stock.
maybe it's just supposed to be that way for you??
Click to expand...
Click to collapse
Checked the RUU zip and it doesn't have the bootsplash, a simplified version of RUU I guess...
So I decided to run a RUU exe, which should be more complete and thorough, 100% back to stock.
But since I couldn't S-ON yesterday, I downgraded my hboot from 1.56 to 1.44 (I thought upgrading it back to 1.56 would be simple).
Now I can't get S-OFF to run the RUU exe(can't use revone because it doesn't work with my version of something),
and some things don't match when I try to run it with S-ON.
I can't find any newer version of RUU or the latest hboot for download.
Overall, I ****ed up pretty bad and I think I'm about to send it back regardless of warranty...
Returning to stock is a lot harder than I thought, all this time put in to fix the purple camera thing...
playpig, i have the exact same fone as you and i also want to unroot my fone. can you please tell me where you found the stock recovery and how u unrooted your fone? thanks in advance
Hi, i've bought an htc one m7 stuck in bootloader, trying to fix it.. this is what I see in bootloader
** TAMPERED **
** UNLOCK **
** Security Warning **
M7_U PVT SHIP S-ON RH
HBOOT-1.57.000
RADIO-4T.28.3218.04
OpenDSP-V32.120.274.0909
eMMC-boot 2048MB
i've tried to unlock bootloader, succesfully and after the reboot it access directly in twrp 2710 recovery (maybe the previous owner flashed it)..
so, i go in advanced, then in adb sideload to transfert a custom rom (eg. revolution) but my phone switch off the screen and my pc try to install qhsusb_dload driver, without success.. so, I press the power button for 20sec (circa) and switch off completly.. and back again in bootloader, that relock automatically every reboot...
how can i fix it? :crying:
Thanks!
Angel2k6 said:
Hi, i've bought an htc one m7 stuck in bootloader, trying to fix it.. this is what I see in bootloader
** TAMPERED **
** UNLOCK **
** Security Warning **
M7_U PVT SHIP S-ON RH
HBOOT-1.57.000
RADIO-4T.28.3218.04
OpenDSP-V32.120.274.0909
OS- (THIS ROW IS BLANK AFTER "OS-"!)
eMMC-boot 2048MB
i've tried to unlock bootloader, succesfully and after the reboot it access directly in twrp 2710 recovery (maybe the previous owner flashed it)..
so, i go in advanced, then in adb sideload to transfert a custom rom (eg. revolution) but my phone switch off the screen and my pc try to install qhsusb_dload driver, without success.. so, I press the power button for 20sec (circa) and switch off completly.. and back again in bootloader, that relock automatically every reboot...
how can i fix it? :crying:
Thanks!
Click to expand...
Click to collapse
Unlock bootloader
flash TWRP 2.6.3.3
Enter TWRP / Wipe / Format Data / Type yes
Reboot to Recovery and push the rom to the phone
adb push rom.zip /sdcard/
Install / rom.zip
clsA said:
Unlock bootloader
flash TWRP 2.6.3.3
Enter TWRP / Wipe / Format Data / Type yes
Reboot to Recovery and push the rom to the phone
adb push rom.zip /sdcard/
Install / rom.zip
Click to expand...
Click to collapse
the problem is that a cannot flash twrp .. how can i do it?
When i unlock the bootloader through the unlock_code.bin (taken from htcdev) the phone reboots automatically in recovery twrp 2.7.1.1 .. and if i reboot the phone again in bootloader it's again in RELOCKED mode..
Angel2k6 said:
the problem is that a cannot flash twrp .. how can i do it?
When i unlock the bootloader through the unlock_code.bin (taken from htcdev) the phone reboots automatically in recovery twrp 2.7.1.1 .. and if i reboot the phone again in bootloader it's again in RELOCKED mode..
Click to expand...
Click to collapse
when it boots to TWRP just follow the rest of the steps
clsA said:
when it boots to TWRP just follow the rest of the steps
Click to expand...
Click to collapse
If i do a wipe from twrp it says "unable to mount /cache" and "unable to mount /system".. Anyway.. After this wipes have I to reboot again in the same recovery? And then? When have I to type adb commands?
Angel2k6 said:
If i do a wipe from twrp it says "unable to mount /cache" and "unable to mount /system".. Anyway.. After this wipes have I to reboot again in the same recovery? And then? When have I to type adb commands?
Click to expand...
Click to collapse
tried it .. but "unable to mount /system /data /cache" .. and when i do reboot>recovery .. the phone doesn't reboot.. it switch down and i have to press for 10-15 seconds to switch completly off.. and than again in relocked bootloader..
Angel2k6 said:
tried it .. but "unable to mount /system /data /cache" .. and when i do reboot>recovery .. the phone doesn't reboot.. it switch down and i have to press for 10-15 seconds to switch completly off.. and than again in relocked bootloader..
Click to expand...
Click to collapse
post your fastboot getvar all
maybe you can flash stock recovery and factory reset
Í
clsA said:
post your fastboot getvar all
maybe you can flash stock recovery and factory reset
Click to expand...
Click to collapse
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***********
(bootloader) imei: ****************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: TIM__401
(bootloader) battery-status: good
(bootloader) battery-voltage: 4311mV
(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.201s
Thank you!
Ah.. Another thing that I have noticed is that in twrp the driver isn't installed by windows.. In "device management" I see a "one" device with a yellow exclamation (I've installed htc sync) .. Windows can't find any compatible driver in my PC.. if i look into hardware details, this is the id:
USB\VID_18D1&PID_D001&REV_0228
EDIT: about the driver i've installed it modifying android_winusb.inf adding this lines:
;HTC ONE(MOD)
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0228
Click to expand...
Click to collapse
in x64 section .. i don't know if i done it well but now when i'm in twrp windows recognize phone, seen as "Android Phone - Android Composite ADB inteface" without the exclamation mark and if I do "adb devices" in prompt it sees my device (seen as it's serial number) and near it "recovery"..
P.S. Why every time the phone is rebooted it relock the bootloader automatically and I have to unlock again to access the recovery?
Angel2k6 said:
Í
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***********
(bootloader) imei: ****************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: TIM__401
(bootloader) battery-status: good
(bootloader) battery-voltage: 4311mV
(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.201s
Thank you!
Ah.. Another thing that I have noticed is that in twrp the driver isn't installed by windows.. In "device management" I see a "one" device with a yellow exclamation (I've installed htc sync) .. Windows can't find any compatible driver in my PC.. if i look into hardware details, this is the id:
USB\VID_18D1&PID_D001&REV_0228
EDIT: about the driver i've installed it modifying android_winusb.inf adding this lines:
in x64 section .. i don't know if i done it well but now when i'm in twrp windows recognize phone, seen as "Android Phone - Android Composite ADB inteface" without the exclamation mark and if I do "adb devices" in prompt it sees my device (seen as it's serial number) and near it "recovery"..
P.S. Why every time the phone is rebooted it relock the bootloader automatically and I have to unlock again to access the recovery?
Click to expand...
Click to collapse
Do you remember your Version Main only its not present in the getvar?
Danny201281 said:
Do you remember your Version Main only its not present in the getvar?
Click to expand...
Click to collapse
Nope.. I've bought this phone as it is.. :/
Angel2k6 said:
Nope.. I've bought this phone as it is.. :/
Click to expand...
Click to collapse
Well I'm thinking flashing a firmware package may help, But i just can't find anything. What is country of Origin, Italy?
Danny201281 said:
Well I'm thinking flashing a firmware package may help, But i just can't find anything. What is country of Origin, Italy?
Click to expand...
Click to collapse
Yes, Italy.. But reading around, in Italian forums it seems that there isn't any ruu for cid tim__401 ..
EDIT :
I don't know if this one could help but here http://www.androidiani.com/forum/modding-htc-one/405113-ritorno-stock-tim.html
there is a TIM backup (he says already rooted) android version 4.4.2..
up
if i try to do this from recovery (using a cm11 rom)
adb devices
List of devices attached
************ recovery
adb push rom1.zip /sdcard/
protocol failure
Click to expand...
Click to collapse
screen switch off and windows tries to install qhsusb_dload drivers..
any ideas? :crying:
Could i try with an otg cable?
Angel2k6 said:
up
if i try to do this from recovery (using a cm11 rom)
screen switch off and windows tries to install qhsusb_dload drivers..
any ideas? :crying:
Could i try with an otg cable?
Click to expand...
Click to collapse
You need to flash a firmware package, or at very least a stock recovery. I have searched all over the net but I can't find any thing not even an OTA.zip
I think your version main would be 5.12.901.3 since that appears to be the latest version with hboot 1.57. But there simply aren't any files for that.
Best suggestion I have for now is, as your able to unlock. Unlock the bootloader
Code:
fastboot flash unlocktoken Unlock_code.bin
fastboot erase cache
fastboot reboot-bootloader
and flash an unbranded stock recovery this one maybe https://www.androidfilehost.com/?fid=95864024717070745
Then use that to do a factory reset. Reboot and see if its locked. If it is unlock again with
Code:
fastboot flash unlocktoken Unlock_code.bin
fastboot erase cache
fastboot reboot-bootloader
Check to see if problem is resolved.
Danny201281 said:
You need to flash a firmware package, or at very least a stock recovery. I have searched all over the net but I can't find any thing not even an OTA.zip
I think your version main would be 5.12.901.3 since that appears to be the latest version with hboot 1.57. But there simply aren't any files for that.
Best suggestion I have for now is, as your able to unlock. Unlock the bootloader
Code:
fastboot flash unlocktoken Unlock_code.bin
fastboot erase cache
fastboot reboot-bootloader
and flash an unbranded stock recovery this one maybe https://www.androidfilehost.com/?fid=95864024717070745
Then use that to do a factory reset. Reboot and see if its locked. If it is unlock again with
Code:
fastboot flash unlocktoken Unlock_code.bin
fastboot erase cache
fastboot reboot-bootloader
Check to see if problem is resolved.
Click to expand...
Click to collapse
I'll try later..
But, every time that I unlock bootloader the phone automatically goes in recovery, so I can't type the second command "fastboot erase cache", because if I reboot again in bootloader is again relocked.. :/
Angel2k6 said:
I'll try later..
But, every time that I unlock bootloader the phone automatically goes in recovery, so I can't type the second command "fastboot erase cache", because if I reboot again in bootloader is again relocked.. :/
Click to expand...
Click to collapse
Ok I see, only option is to flash firmware then since that can be done while it's relocked. First we need to find it
Danny201281 said:
Ok I see, only option is to flash firmware then since that can be done while it's relocked. First we need to find it
Click to expand...
Click to collapse
And then it's the only way? If i try using an otg cable flashing a cm11? Could I do more damage?
Angel2k6 said:
And then it's the only way? If i try using an otg cable flashing a cm11? Could I do more damage?
Click to expand...
Click to collapse
But how can you boot a custom rom with a relocked bootloader? Are you able to unlock flash a rom then boot to Android? Or does it relock when you reboot after flashing the rom?
Danny201281 said:
But how can you boot a custom rom with a relocked bootloader? Are you able to unlock flash a rom then boot to Android? Or does it relock when you reboot after flashing the rom?
Click to expand...
Click to collapse
But when I unlock bootloader and the phone reboots directly in recovery, in that session, while I'm in recovery, they bootloader isn't unlocked?
I've never tried to flash a rom because adb sideload or adb push seems that don't work..
Angel2k6 said:
But when I unlock bootloader and the phone reboots directly in recovery, in that session, while I'm in recovery, they bootloader isn't unlocked?
I've never tried to flash a rom because adb sideload or adb push seems that don't work..
Click to expand...
Click to collapse
It must be unlocked otherwise the custom recovery wouldn't load. So you could push and install a rom, but after its installed the rom you will need to reboot. If the bootloader locks it won't boot the custom rom.
You could also try to dd (direct dump) a stock recovery while your in custom recovery. Maybe that would help?
Hi
I'm running XENON HD and tried to do an OTA upgrade. When I came back to my phone, it was in the bootloader screen. After every reboot, it goes there.
This wouldn't normally be a problem except that my volume keys are damaged and I can't select any option from the bootloader screen.
I tried a #fastboot boot twrp.img but it doesn't reboot the phone.
Is there any way I can access recovery another way? I did a backup (on the sd card ) so I really just need to get into recovery.
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
Any help/ideas is appreciated.
Thanks!
Perf_engineer said:
Hi
I'm running XENON HD and tried to do an OTA upgrade. When I came back to my phone, it was in the bootloader screen. After every reboot, it goes there.
This wouldn't normally be a problem except that my volume keys are damaged and I can't select any option from the bootloader screen.
I tried a #fastboot boot twrp.img but it doesn't reboot the phone.
Is there any way I can access recovery another way? I did a backup (on the sd card ) so I really just need to get into recovery.
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
Any help/ideas is appreciated.
Thanks!
Click to expand...
Click to collapse
fastboot boot twrp.img was only working on hboot 1.44 back in 2013, this command was disabled with 1.54 and all newer hboot.
There is no command to make your phone reboot in recovery from the bootloader so i'm afraid you will not be able to go back in recovery. If at least your phone is in bootloader mode with "fastboot usb" in red you can relock your BL and restore using a RUU. Once the ruu is flashed the phone will reboot to the OS by itself.
alray said:
fastboot boot twrp.img was only working on hboot 1.44 back in 2013, this command was disabled with 1.54 and all newer hboot.
There is no command to make your phone reboot in recovery from the bootloader so i'm afraid you will not be able to go back in recovery. If at least your phone is in bootloader mode with "fastboot usb" in red you can relock your BL and restore using a RUU. Once the ruu is flashed the phone will reboot to the OS by itself.
Click to expand...
Click to collapse
Crap.. At least it isn't dead. Thanks for your help
alray said:
fastboot boot twrp.img was only working on hboot 1.44 back in 2013, this command was disabled with 1.54 and all newer hboot.
There is no command to make your phone reboot in recovery from the bootloader so i'm afraid you will not be able to go back in recovery. If at least your phone is in bootloader mode with "fastboot usb" in red you can relock your BL and restore using a RUU. Once the ruu is flashed the phone will reboot to the OS by itself.
Click to expand...
Click to collapse
Hi alray.
I downloaded what i thought was the right RUU but I am getting an error message saying it can't verify the signature.
How can I tell which RUU I should use? I don't care what goes on it as I will be unlocking the bootloader again and putting back on a custom rom.
Thanks
./fastboot flash zip RUU.zip
sending 'zip' (1463809 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
Perf_engineer said:
Hi alray.
I downloaded what i thought was the right RUU but I am getting an error message saying it can't verify the signature.
How can I tell which RUU I should use? I don't care what goes on it as I will be unlocking the bootloader again and putting back on a custom rom.
Thanks
./fastboot flash zip RUU.zip
sending 'zip' (1463809 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
Nevermind. I found the CID and MID of my phone. Downloading now. hopefully it will work
Perf_engineer said:
Nevermind. I found the CID and MID of my phone. Downloading now. hopefully it will work
Click to expand...
Click to collapse
Nope
Any thoughts?
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3AHW902491
(bootloader) imei: 359405051005401
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4204mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
No version main.
I can't find an exe for my model. Apparently zip files won't work when you are missing the verison
Fastboot reboot
Fastboot flash recovery
Fastboot reboot
Fastboot reboot recovery
If you have a kik. Feel free to contact me under the same name for quick assistance
Tony the noob :D said:
Fastboot reboot
Fastboot flash recovery
Fastboot reboot
Fastboot reboot recovery
If you have a kik. Feel free to contact me under the same name for quick assistance
Click to expand...
Click to collapse
Thanks for the offer. Don't have kik unfortunately.
Current state I'm in is that I have relocked my phone, but the version_main is blank.
flashing from zip doesn't work in RUU.
I tried to flash the recovery again but keep getting the signature failed message
Perf_engineer said:
Thanks for the offer. Don't have kik unfortunately.
Current state I'm in is that I have relocked my phone, but the version_main is blank.
flashing from zip doesn't work in RUU.
I tried to flash the recovery again but keep getting the signature failed message
Click to expand...
Click to collapse
Your trying to do a HTC OTA Update?
pardon me for stealing the thread. In a related issue.
https://forum.xda-developers.com/htc-one-tmobile/development/recent-zip-ruu-t-mo-t3662241
which RUU or rom to install?
Perf_engineer said:
I can't find an exe for my model. Apparently zip files won't work when you are missing the verison
Click to expand...
Click to collapse
Yes zip version will work even if your version-main is blank, since you don't know your version-main, use the latest ruu for your cid/mid. If the latest version ruu isn't available in the ruu collection thread, you'll probably have to download it from easy-firmware.com or a similar website.
---------- Post added at 06:48 AM ---------- Previous post was at 06:46 AM ----------
Perf_engineer said:
Thanks for the offer. Don't have kik unfortunately.
Current state I'm in is that I have relocked my phone, but the version_main is blank.
flashing from zip doesn't work in RUU.
I tried to flash the recovery again but keep getting the signature failed message
Click to expand...
Click to collapse
you can't flash the recovery partition when the BL is locked. The BL must be locked to flash the ruu.
Tony the noob :D said:
Your trying to do a HTC OTA Update?
Click to expand...
Click to collapse
Is that possible? I can't load any rom at the moment.
Tony the noob :D said:
Fastboot reboot
Fastboot flash recovery
Fastboot reboot
Fastboot reboot recovery
If you have a kik. Feel free to contact me under the same name for quick assistance
Click to expand...
Click to collapse
I thought you can't fastboot into recovery?
At least I never could. If I can I could have solved this ages ago
alray said:
Yes zip version will work even if your version-main is blank, since you don't know your version-main, use the latest ruu for your cid/mid. If the latest version ruu isn't available in the ruu collection thread, you'll probably have to download it from easy-firmware.com or a similar website.
---------- Post added at 06:48 AM ---------- Previous post was at 06:46 AM ----------
you can't flash the recovery partition when the BL is locked. The BL must be locked to flash the ruu.
Click to expand...
Click to collapse
crap crap crap.
I just tried to unlock the bootloader again. Remember when I said the volume keys were damaged? I should have been more specific.. The phone fell and damaged the volume up key and it is pressed in. This doesn't allow me to use the power button to select. So I can't unlock the bootloader now :\ (unless I can give it a default acceptance?)
So I think my only options are to put on the stock and leave it as is
Or open the phone up so the case isn't pressing on the volume key.
This was the RUU I tried. It seems to be the latest and the right version.
PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_423416_combined_signed.zip
can anyone confirm?
Thanks
Perf_engineer said:
I thought you can't fastboot into recovery?
At least I never could. If I can I could have solved this ages ago
Click to expand...
Click to collapse
no you can't
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
Perf_engineer said:
crap crap crap.
I just tried to unlock the bootloader again. Remember when I said the volume keys were damaged? I should have been more specific.. The phone fell and damaged the volume up key and it is pressed in. This doesn't allow me to use the power button to select. So I can't unlock the bootloader now :\ (unless I can give it a default acceptance?)
So I think my only options are to put on the stock and leave it as is
Or open the phone up so the case isn't pressing on the volume key.
This was the RUU I tried. It seems to be the latest and the right version.
PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_423416_combined_signed.zip
can anyone confirm?
Thanks
Click to expand...
Click to collapse
use the 7.18.206.51 ruu, it's the latest one for o2
alray said:
no you can't
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
use the 7.18.206.51 ruu, it's the latest one for o2
Click to expand...
Click to collapse
FAILED (remote: 02 data length is too large)
Update:
The data too large message was when I used the latest HTC fastboot Linux version.
I switched to Windows and it worked. Back at stock.
Thanks to everyone for their help, especially alray
Ok...so I'm never happy.. Anyway to unlock the bootloader again without the power button?
Perf_engineer said:
Ok...so I'm never happy.. Anyway to unlock the bootloader again without the power button?
Click to expand...
Click to collapse
sunshine
alray said:
sunshine
Click to expand...
Click to collapse
Thanks for the tip but it didn't work.
It was unable to get temporary root access.
I tried iRoot and towelroot but they also failed.
Guess I'm stuck