Hello
so my brother bricked his htc one M7 so now im trying to get it back to work fine but i dunno how
i have rooted it from before but now when ever i try to power on his phone it goes to the bootloader menu and when i go to the recovery it says on top no OS installed
how can i re install the software ?
Post the output of 'fastboot getvar all' with the IMEI and serial number edited out. Depending on the result it could be as easy as flashing an RUU from bootloader.
AndroHero said:
Post the output of 'fastboot getvar all' with the IMEI and serial number edited out. Depending on the result it could be as easy as flashing an RUU from bootloader.
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3865mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
[If you can get into bootloader can you flash custom recovery TWRP 2.7.1.1?
If you can flash it via fastboot flash recovery <name of recovery.img>, then fastboot erase cache then try entering recovery.
If you can get into recovery sideload a custom rom through TWRP (suggest a CyanogenMod as relatively small just to get you operational
Related
I tried to reversed from Cyanogen back to stock using this setup: http://sakitechonline.com/restore-your-htc-one-to-sense-5-stock-or-factory-rom/
After locking my phone and flashing: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed It's crashing..
The only thing that's working now is fastboot..
But it's still S-On
Can someone help me.... :crying:
Or is it a brick?
c:\mini-sdk>fastboot getvar all
(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-ON
(bootloader) serialno: 0000000000000
(bootloader) imei: 000000000000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
Try to flash the RUU again, and be sure to have chosen the correct one.
Uxepro said:
Try to flash the RUU again, and be sure to have chosen the correct one.
Click to expand...
Click to collapse
Hi, I, think thats the good RUU, but maybe it's not possible flashing it with hboot 1.55
And can't flash it to hboot 1.44 because it's locked
Stupid me... just unlock again..
It's starting up now..
Ronnymes said:
Hi, I, think thats the good RUU, but maybe it's not possible flashing it with hboot 1.55
And can't flash it to hboot 1.44 because it's locked
Stupid me... just unlock again..
It's starting up now..
Click to expand...
Click to collapse
I guess you don't have to flash it to 1.44. My HTC also have the same detail as yours and also have the same problem.
This my HTC One detail:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA351W901363
imei: 355859050074707
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__044
battery-status: good
battery-voltage: 4048mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-ea0bccbd
hbootpreupdate: 11
gencheckpt: 0
My HTC One only can boot to Fastboot. And worst.. I don't have any ROM in my sdcard, so I use with TWRP Recovery and using USB OTG.
It works for me.
Try this link to download your stock ROM: http://forum.xda-developers.com/showthread.php?t=2428276
I Hope it can help.
netslider said:
I guess you don't have to flash it to 1.44. My HTC also have the same detail as yours and also have the same problem.
This my HTC One detail:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA351W901363
imei: 355859050074707
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__044
battery-status: good
battery-voltage: 4048mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-ea0bccbd
hbootpreupdate: 11
gencheckpt: 0
My HTC One only can boot to Fastboot. And worst.. I don't have any ROM in my sdcard, so I use with TWRP Recovery and using USB OTG.
It works for me.
Try this link to download your stock ROM: http://forum.xda-developers.com/showthread.php?t=2428276
I Hope it can help.
Click to expand...
Click to collapse
Gonna try it right now, thnx!!
Keep getting errors, tried this:
in bootloader/FASTBOOT USB, flash it:
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 above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
But it's not changing te hboot..
But I have installed a recovery (ClockworkMod 6.0.4.6 , is there a way to flash a new ROM via fastboot?
You won't be able to downgrade your hboot version as you are still S-ON.
If you use the guru reset ROM (flashed through custom recovery, if you can get to it?) then gain S-OFF, you will then be able to downgrade your hboot.
Sent from my HTC One using XDA Premium 4 mobile app
Ronnymes said:
Keep getting errors, tried this:
in bootloader/FASTBOOT USB, flash it:
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 above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
But it's not changing te hboot..
But I have installed a recovery (ClockworkMod 6.0.4.6 , is there a way to flash a new ROM via fastboot?
Click to expand...
Click to collapse
You don't have to change HBOOT.
Just take a suitable ROM for your device and flash it using recovery TWRP (suggested)
And to flash the ROM, I suggest using USB OTG. I connected my FlashDiskdrive to HTC One and using USB OTG I flashed the ROM.
And now, my HTC One is back to normal. Without changing HBOOT and still S-ON.
netslider said:
You don't have to change HBOOT.
Just take a suitable ROM for your device and flash it using recovery TWRP (suggested)
And to flash the ROM, I suggest using USB OTG. I connected my FlashDiskdrive to HTC One and using USB OTG I flashed the ROM.
And now, my HTC One is back to normal. Without changing HBOOT and still S-ON.
Click to expand...
Click to collapse
Oké, I have to buy the USB OTB cable first..
And put the RUU on a flashstick,
I hope it's possible because sideload is not working.
100% upload via sideload (Cyanogen ROM) but then a bootloop
So when I have the cable just flash te RUU ZIP to CWM recovery, and it's working again?
No need to use the OTB USB cable
Check this: http://android-revolution-hd.blogspot.nl/2013/10/fix-data-htc-one.html
Problem solved!!!
I'm freaking out a little bit. I was in the middle of trying to restore to stock. I got s-on back and locked the bootloader. Now I'm stuck on the bootloader. No matter what I press, it goes back to the bootloader. Adb no longer lists any devices connected to the pc. I can't get any of the RUU's I have downloaded to even open. Any ideas? Should the RUU be the next step?
I'm on xp
Bradlees said:
I'm freaking out a little bit. I was in the middle of trying to restore to stock. I got s-on back and locked the bootloader. Now I'm stuck on the bootloader. No matter what I press, it goes back to the bootloader. Adb no longer lists any devices connected to the pc. I can't get any of the RUU's I have downloaded to even open. Any ideas? Should the RUU be the next step?
I'm on xp
Click to expand...
Click to collapse
1- why did you s-on? Always keep s-off unless you send your phone for repair under warranty.
2- adb can't work from bootloader only fasboot, so ''fastboot devices'' should list your phone.
3- post the output of ''fastboot getvar all'' except IMEI so we can determine if you can use a ruu.
4- which ruu are you trying to flash?
alray said:
1- why did you s-on? Always keep s-off unless you send your phone for repair under warranty.
2- adb can't work from bootloader only fasboot, so ''fastboot devices'' should list your phone.
3- post the output of ''fastboot getvar all'' except IMEI so we can determine if you can use a ruu.
4- which ruu are you trying to flash?
Click to expand...
Click to collapse
If trying to turn my phone in for an upgrade, hence the return to factory.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(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: 3755mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm trying to download the tmobile us RUU I got off the link in here.
Bradlees said:
If trying to turn my phone in for an upgrade, hence the return to factory.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3*******
(bootloader) imei: xxxxxxxxxxxxxxxxx
(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: 3755mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm trying to download the tmobile us RUU I got off the link in here.
Click to expand...
Click to collapse
Edit out your serial no above ..
I posted this RUU for someone yesterday ..here's the link to the rom.zip
https://www.dropbox.com/s/mql8sas0udb1427/rom.zip
copy the file to your fastboot folder and flash it with fastboot
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip << yes two times
fastboot reboot
clsA said:
Edit out your serial no above ..
I posted this RUU for someone yesterday ..here's the link to the rom.zip
https://www.dropbox.com/s/mql8sas0udb1427/rom.zip
copy the file to your fastboot folder and flash it with fastboot
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip << yes two times
fastboot reboot
Click to expand...
Click to collapse
Success! You saved me.
If I could hit the thanks button more, I would.
Bradlees said:
Success! You saved me.
If I could hit the thanks button more, I would.
Click to expand...
Click to collapse
it's no problem .. like i said i just posted it for another guy yesterday so it was fresh on my mind
Hello,
After flashing Android Revolution HD 82.0, my phone got stuck at the 'HTC powered by android' splash screen.
Since I cannot boot, USB-debug mode is off and therefore I cannot use adb. I have TWRP 2.6.3.3-m7 installed as recovery, but this gets to the 'teamwin' splash screen and then goes to a black screen, followed by restarting and thus getting stuck on the 'HTC powered by android' splash screen again.
fastboot getvar all:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.29.3218.08
version-cpld: None
version-microp: None
version-main: 6.09.401.10
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 4198mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Thankyou in advance for your responses.
xsrust said:
Hello,
After flashing Android Revolution HD 82.0, my phone got stuck at the 'HTC powered by android' splash screen.
Since I cannot boot, USB-debug mode is off and therefore I cannot use adb. I have TWRP 2.6.3.3-m7 installed as recovery, but this gets to the 'teamwin' splash screen and then goes to a black screen, followed by restarting and thus getting stuck on the 'HTC powered by android' splash screen again.
fastboot getvar all:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.29.3218.08
version-cpld: None
version-microp: None
version-main: 6.09.401.10
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 4198mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Thankyou in advance for your responses.
Click to expand...
Click to collapse
have you checked MD5 value of twrp 2.6.3.3 and arhd before flashing?
TWRP 2.6.3.3: 72067aefb69541d40e8420d7aa46408d
ARHD 82.0: 813ED2AB219C6A7D7489E8090A5C8C45
reflash twrp 2.6.3.3
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then reflash the rom (check your MD5 before)
alray said:
have you checked MD5 value of twrp 2.6.3.3 and arhd before flashing?
TWRP 2.6.3.3: 72067aefb69541d40e8420d7aa46408d
ARHD 82.0: 813ED2AB219C6A7D7489E8090A5C8C45
reflash twrp 2.6.3.3[/URL]
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then reflash the rom (check your MD5 before)
Click to expand...
Click to collapse
Thanks a bunch. the MD5 for the rom was incorrect. re-downloading and re-flashing it worked.
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.
Hello Everyone,
I have a problem with my HTC One M7.
The Rom that is/was on the phone is on OS-6.14.111.2
But in the bootloader the displayed OS is 7.18.11.2 . For the moment it's relocked but can be unlocked again. It is also S-ON and it has no working recovery.
The problems are :
- The phone boots and after the first HTC (Powered by android) screen i get a black screen, and nothing is happening here.
- I can't seem to get any working recovery on the phone (TWRP or CWM), after i flash a recovery i get the message "Entering Recovery..." a brief flash and then the message again, and then nothing happends
any idea what i'm doing wrong ? What i can try ? or do i have a beautifull new paperweight ?
Here a fastboot getvar :
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.18.111.2
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: T-MOB101
battery-status: good
battery-voltage: 3899mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b30b07eb
hbootpreupdate: 11
gencheckpt: 0
Thank you all
Black-Panther666 said:
Hello Everyone,
I have a problem with my HTC One M7.
The Rom that is/was on the phone is on OS-6.14.111.2
But in the bootloader the displayed OS is 7.18.11.2 . For the moment it's relocked but can be unlocked again. It is also S-ON and it has no working recovery.
The problems are :
- The phone boots and after the first HTC (Powered by android) screen i get a black screen, and nothing is happening here.
- I can't seem to get any working recovery on the phone (TWRP or CWM), after i flash a recovery i get the message "Entering Recovery..." a brief flash and then the message again, and then nothing happends
any idea what i'm doing wrong ? What i can try ? or do i have a beautifull new paperweight ?
Here a fastboot getvar :
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.18.111.2
version-misc: PVT SHIP S-ON
serialno:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: T-MOB101
battery-status: good
battery-voltage: 3899mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b30b07eb
hbootpreupdate: 11
gencheckpt: 0
Thank you all
Click to expand...
Click to collapse
remove your serial no and IMEI from you post
try an older philz recovery or TWRP 2.6.3.3
Black-Panther666 said:
Hello Everyone,
I have a problem with my HTC One M7.
The Rom that is/was on the phone is on OS-6.14.111.2
But in the bootloader the displayed OS is 7.18.11.2 . For the moment it's
relocked but can be unlocked again. It is also S-ON and it has no working
recovery.
The problems are :
- The phone boots and after the first HTC (Powered by android) screen i get a
black screen, and nothing is happening here.
- I can't seem to get any working recovery on the phone (TWRP or CWM), after
i flash a recovery i get the message "Entering Recovery..." a brief flash and
then the message again, and then nothing happends
any idea what i'm doing wrong ? What i can try ? or do i have a beautifull
new paperweight ?
Here a fastboot getvar :
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4T.35.3218.16
version-cpld: None
version-microp: None
version-main: 7.18.111.2
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: T-MOB101
battery-status: good
battery-voltage: 3899mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b30b07eb
hbootpreupdate: 11
gencheckpt: 0
Thank you all
Click to expand...
Click to collapse
Go HERE
Download your RUU & flash it nothing more
Wanna save data flash TWRP 2.6.3.3 then 2.8.5.0 enable mtp mode connect to PC copy all data
Thank you for your quick response
It worked for the RUU part, but the recovery still isn't working.