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.
Related
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"
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
I was trying to go from stock at&t 4.4.2 to GPE and made it through the bootloader and root process but had problems trying to use firewater for s-off. Gave me an error about my kernel I attempted to flash to elementalx-m7-15.1-gpe and now I cannot get to my OS and I cant transfer a different kernel to my HTC one. I can only boot to fastboot and TWRP v2.8.1.0. I've been trying to sideload roms but cant get my HTC one to appear under adb devices when using sideload in TWRP. How can I fix this? HBOOT 1.57 OS-5.12.502.2
Edit 1 : I've been trying to use RUU_M7_UL_K44_SENSE55_MR_Cingular but after turning my screen to the htc logo and making it 5 percent through I get a USB Connection Error Error [171]
Edit 2: output of fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.12.502.2
version-misc: PVT SHIP S-ON
serialno: HT359W912793
imei: 354439052834159
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4019mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
DimsumThe said:
I was trying to go from stock at&t 4.4.2 to GPE and made it through the bootloader and root process but had problems trying to use firewater for s-off. Gave me an error about my kernel I attempted to flash to elementalx-m7-15.1-gpe and now I cannot get to my OS and I cant transfer a different kernel to my HTC one. I can only boot to fastboot and TWRP v2.8.1.0. I've been trying to sideload roms but cant get my HTC one to appear under adb devices when using sideload in TWRP. How can I fix this? HBOOT 1.57 OS-5.12.502.2
Edit 1 : I've been trying to use RUU_M7_UL_K44_SENSE55_MR_Cingular but after turning my screen to the htc logo and making it 5 percent through I get a USB Connection Error Error [171]
Edit 2: output of fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.12.502.2
version-misc: PVT SHIP S-ON
serialno: HT359W912793
imei: 354439052834159
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4019mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Ok so you flashed a GPE kernel on your sense phone. You need s-off and to complete the conversion before you can use that kernel. On 4.4.2 Sense you should use
Sense 6 Android 4.4.2
ElementalX-m7-14.12-Sense http://elementalx.org/htc-one-m7#downloads
Check your drivers are installed correctly. In the device manager on your pc your phone should be listed as "MY HTC" if your drivers are ok, try downgrading to TWRP 2.6.3.3. Some newer versions of twrp have problems with adb. I also recommend doing a "Format Data" in twrp before you push and install a new rom.
Also you should try adb push instead of sideload. With the phone on the twrp home screen.
Code:
adb push "naneofrom".zip /sdcard
The command window will appear unresponsive until the push completes (several minutes) when it's done install the Rom with twrp recovery.
If you found my posts helpful, no need to say thanks. There's a button for that
I havent been able to get adb to work it either says its offline or is not listed when I use the adb devices command at twrp homescreen. Also can I do s-off before or after this? Thanks for helping.
edit1: I was able to get adb to work with2.6.3.3
edit2: I got an older rom to work through adb now to start over again thank you so much!
DimsumThe said:
I havent been able to get adb to work it either says its offline or is not listed when I use the adb devices command at twrp homescreen. Also can I do s-off before or after this? Thanks for helping.
edit1: I was able to get adb to work with2.6.3.3
edit2: I got an older rom to work through adb now to start over again thank you so much!
Click to expand...
Click to collapse
Your welcome, glad you solved your problem :good:
If you found my posts helpful, no need to say thanks. There's a button for that
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
So ive been trying to unroot my HTC ONE M7 before sending it back to the carrier as im getting it replaced, then will sell that other phone as I already have a new phone with me. Im on Rogers Canada, ive tried the RUU.exe and it just goes on for hours and does nothing.
Ive tried flashing different custom roms to the device, my fastboot and ADB works perfectly its just nothing is working. The last error I got was "FAILED (data transfer failure (Unknown error))" but I get so many errors with every way Ive tried, im beginning to give up.
I was wondering if I can get the same help I got here two years ago, where I was having issues rooting and someone helped me. He was a high rep member and I trusted him with using teamviewer on my comp. Im totally open to skype screensharing or using teamviewer.
Info:
HTC ONE M7 (ROGERS,CANADA)
Rooted w/ cyanogen mod
I have no idea if its S-off or S-on as I did this like 3 years ago
Thanks
DoctorClanScriptr said:
So ive been trying to unroot my HTC ONE M7 before sending it back to the carrier as im getting it replaced, then will sell that other phone as I already have a new phone with me. Im on Rogers Canada, ive tried the RUU.exe and it just goes on for hours and does nothing.
Ive tried flashing different custom roms to the device, my fastboot and ADB works perfectly its just nothing is working. The last error I got was "FAILED (data transfer failure (Unknown error))" but I get so many errors with every way Ive tried, im beginning to give up.
I was wondering if I can get the same help I got here two years ago, where I was having issues rooting and someone helped me. He was a high rep member and I trusted him with using teamviewer on my comp. Im totally open to skype screensharing or using teamviewer.
Info:
HTC ONE M7 (ROGERS,CANADA)
Rooted w/ cyanogen mod
I have no idea if its S-off or S-on as I did this like 3 years ago
Thanks
Click to expand...
Click to collapse
Can you post the output of "fastboot getvar all" please (hide your imei) ?
What was the RUU version you were trying to flash?
Also I only have Fastboot no ADB anymore for some oddreason. I think its because I accidentally deleted the OS and have no recovery because it isnt letting me install it. So im ****ed
alray said:
Can you post the output of "fastboot getvar all" please (hide your imei) ?
What was the RUU version you were trying to flash?
Click to expand...
Click to collapse
Not sure, was trying so many haha. Heres the GetVar. Oh and by the way I ****ed up my phone completely, I cant even install a recovery and I think I deleted the OS on accident. So all I have to work with is fastboot
ootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
serialno: HT36WW904197
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 4274mV
partition-layout: Generic
security: on
build-mode: SHIP
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
DoctorClanScriptr said:
Not sure, was trying so many haha. Heres the GetVar. Oh and by the way I ****ed up my phone completely, I cant even install a recovery and I think I deleted the OS on accident. So all I have to work with is fastboot
ootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
serialno: HT36WW904197
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 4274mV
partition-layout: Generic
security: on
build-mode: SHIP
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Try the 7.17.631.7 RUU from this thread. This ruu is in the ZIP format, not EXE so you'll have to flash it using fastboot. You'll also need to use htc's version of fastboot.exe to flash this ruu as the regular fastboot version you can find from Google (from the android sdk tool) won't work.
https://www.androidfilehost.com/?fid=24341993505161791
alray said:
Can you post the output of "fastboot getvar all" please (hide your imei) ?
What was the RUU version you were trying to flash?
Click to expand...
Click to collapse
alray said:
Try the 7.17.631.7 RUU from this thread. This ruu is in the ZIP format, not EXE so you'll have to flash it using fastboot. You'll also need to use htc's version of fastboot.exe to flash this ruu as the regular fastboot version you can find from Google (from the android sdk tool) won't work.
https://www.androidfilehost.com/?fid=24341993505161791
Click to expand...
Click to collapse
got htcs fastboot binaries, and flashed using fasboot. I get this error FAILED (remote: 02 data length is too large)
alray said:
Try the 7.17.631.7 RUU from this thread. This ruu is in the ZIP format, not EXE so you'll have to flash it using fastboot. You'll also need to use htc's version of fastboot.exe to flash this ruu as the regular fastboot version you can find from Google (from the android sdk tool) won't work.
https://www.androidfilehost.com/?fid=24341993505161791
Click to expand...
Click to collapse
Okay I tried it again. Got this
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device HT36WW904197...
edit: tried it again ,its doing something, Now I will wait
alray said:
Try the 7.17.631.7 RUU from this thread. This ruu is in the ZIP format, not EXE so you'll have to flash it using fastboot. You'll also need to use htc's version of fastboot.exe to flash this ruu as the regular fastboot version you can find from Google (from the android sdk tool) won't work.
https://www.androidfilehost.com/?fid=24341993505161791
Click to expand...
Click to collapse
DoctorClanScriptr said:
got htcs fastboot binaries, and flashed using fasboot. I get this error FAILED (remote: 02 data length is too large)
Click to expand...
Click to collapse
Holy **** I love you, it ****ing worked. amazing
alray said:
Try the 7.17.631.7 RUU from this thread. This ruu is in the ZIP format, not EXE so you'll have to flash it using fastboot. You'll also need to use htc's version of fastboot.exe to flash this ruu as the regular fastboot version you can find from Google (from the android sdk tool) won't work.
https://www.androidfilehost.com/?fid=24341993505161791
Click to expand...
Click to collapse
Hi
If you don't mind could you help me find the RUU for the following getVAR as I couldn't find it:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.16.61.8
version-misc: PVT SHIP S-ON
serialno: FA35TW906311
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: ORANG001
battery-status: good
battery-voltage: 4152mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Thanks
---------- Post added at 10:37 PM ---------- Previous post was at 09:39 PM ----------
mrsid2201 said:
Hi
If you don't mind could you help me find the RUU for the following getVAR as I couldn't find it:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.16.61.8
version-misc: PVT SHIP S-ON
serialno: FA35TW906311
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: ORANG001
battery-status: good
battery-voltage: 4152mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Thanks
Click to expand...
Click to collapse
I think i found the RUU from your thread - 7.19.61.10 but the problem is after downloading it, I can't seem to extract it as it shows the "Compressed folder is invalid".
mrsid2201 said:
Hi
If you don't mind could you help me find the RUU for the following getVAR as I couldn't find it:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.16.61.8
version-misc: PVT SHIP S-ON
serialno: FA35TW906311
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: ORANG001
battery-status: good
battery-voltage: 4152mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Thanks
---------- Post added at 10:37 PM ---------- Previous post was at 09:39 PM ----------
I think i found the RUU from your thread - 7.19.61.10 but the problem is after downloading it, I can't seem to extract it as it shows the "Compressed folder is invalid".
Click to expand...
Click to collapse
Please read this https://forum.xda-developers.com/showpost.php?p=64082118&postcount=416 espacialy that part " there is no mention of opening the zip file"
saturday_night said:
Please read this https://forum.xda-developers.com/showpost.php?p=64082118&postcount=416 espacialy that part " there is no mention of opening the zip file"
Click to expand...
Click to collapse
Thanks!
When I tried to flash the RUU I get an error saying "Could not allocate [random number] bytes".
Is it because the image is too big to handle?
mrsid2201 said:
Thanks!
When I tried to flash the RUU I get an error saying "Could not allocate [random number] bytes".
Is it because the image is too big to handle?
Click to expand...
Click to collapse
Are you using htc_fastboot.exe? https://www.androidfilehost.com/?fid=24341993505161791
If so, try command
Fastboot erase cache
saturday_night said:
Are you using htc_fastboot.exe? https://www.androidfilehost.com/?fid=24341993505161791
If so, try command
Fastboot erase cache
Click to expand...
Click to collapse
I erased the cache but the error remains and yes, I used htc fastboot.
mrsid2201 said:
I erased the cache but the error remains and yes, I used htc fastboot.
Click to expand...
Click to collapse
If you use the htc_fastboot.exe you need to put it in the adb folder and rename it to fastboot.exe otherwise the commands are not working with it and your pc uses the usual fastboot.exe. For an easier usage you should also rename the ruuxxxx.zip to just ruu.zip. (also make sure you see the file extentions and dint rename it to ruu.zip.zip)