[Q] Problem with flash a working ROM - Sprint HTC One (M7)

I did extensive search on multiple forums but did not get answer. Hope someone can help here.
The timeline and issue look like this:
* unlocked phone and installed TWRP 2.5 for m7wls. This part was good.
* HTC released 4.3 OTA. I was unable to take it because of TWRP.
* In the middle, probably a wrong zip (Android_Revolution_HD-One_4.0_GE.zip) was loaded by twrp. Now, twrp cannot mount USB at all.
* Tried CWM recovery, works but cannot mount USB either.
* Flashed back stock boot and stock recovery: http://forum.xda-developers.com/showthread.php?t=2236418
* Tried to do fastboot oem rebootRUU then fastboot flash zip. But none of the zip I found can pass. Failed with 24 parsing android-info fail
To summarize, no USB mount, no OTG yet (ordered a cable yesterday), fastboot seems working, twrp/cwm recovery looks good. Can anyone please help? Thank you!
Device: Sprint HTC One unlocked, S-ON, HBoot 1.44.0000
Desktop: Windows 8 64-bit
C:\temp> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4291mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.043s

xmmmm said:
* In the middle, probably a wrong zip (Android_Revolution_HD-One_4.0_GE.zip)
Click to expand...
Click to collapse
This isn't for our phone. Where did you get this? I haven't seen this in our forum.
Sent from my HTCONE using Tapatalk 2

hcyplr29 said:
This isn't for our phone. Where did you get this? I haven't seen this in our forum.
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse
Most likely, it is for GSM version.

xmmmm said:
Most likely, it is for GSM version.
Click to expand...
Click to collapse
Try this. http://forum.xda-developers.com/showthread.php?p=45988642
Sent from my HTCONE using Tapatalk 2

I will give a try. But why this rom could prevent twrp/cwm from mounting USB?
Thank you.
hcyplr29 said:
Try this. http://forum.xda-developers.com/showthread.php?p=45988642
Sent from my HTCONE using Tapatalk 2
Click to expand...
Click to collapse

xmmmm said:
I will give a try. But why this rom could prevent twrp/cwm from mounting USB?
Thank you.
Click to expand...
Click to collapse
you flashed a GSM rom on a CDMA phone and messed up your partitions, at this point you can only try to sideload a rom (for your phone m7wls) or RUU, to run ruu you will need to get s-off.

Aldo101t said:
you flashed a GSM rom on a CDMA phone and messed up your partitions, at this point you can only try to sideload a rom (for your phone m7wls) or RUU, to run ruu you will need to get s-off.
Click to expand...
Click to collapse
Thanks, I will try this as well. Moving to a Windows 7 PC to do all this. May I ask which ROM I should load? Thank you.

xmmmm said:
Thanks, I will try this as well. Moving to a Windows 7 PC to do all this. May I ask which ROM I should load? Thank you.
Click to expand...
Click to collapse
any rom in the sprint forum which ever one appeals to ya

The problem is resolved.
Some factors to consider if someone else run into the same issue. Most of these are mentioned in other threads as well.
1. Windows 7 x64 OK. (Previous was Windows 8 x64)
2. HTC Driver 3.0.0.007 (Previous was 4.1.0.001)
3. Installed UniversalAdbDriverSetup6.msi. Without this, adb always gave device not found error.
4. Rollback to 1.29.651.10 by doing below and then run RUU from Windows. Ignore the lseek64 error.
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
fastboot oem lock
The device is still S-ON and relocked with stock recovery after above steps. There is no more tampered alert in hboot.
By the way, when adb started working, I tried to use "adb push rom.zip /sdcard" and install the stock 1.31.651.2 zip from twrp. But it seems the system constantly freeze up with this approach. RUU is definitely the best and easiest way to do.
Many thanks to all who contributed the ideas.

xmmmm said:
The problem is resolved.
Some factors to consider if someone else run into the same issue. Most of these are mentioned in other threads as well.
1. Windows 7 x64 OK. (Previous was Windows 8 x64)
2. HTC Driver 3.0.0.007 (Previous was 4.1.0.001)
3. Installed UniversalAdbDriverSetup6.msi. Without this, adb always gave device not found error.
4. Rollback to 1.29.651.10 by doing below and then run RUU from Windows. Ignore the lseek64 error.
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
fastboot oem lock
The device is still S-ON and relocked with stock recovery after above steps. There is no more tampered alert in hboot.
Many thanks to all who contributed the ideas.
Click to expand...
Click to collapse
Best Driver is Universal Naked Driver
And if you dont need full blown SDK Minimal ADB and Fastboot

Konfuzion said:
Best Driver is Universal Naked Driver
And if you dont need full blown SDK Minimal ADB and Fastboot
Click to expand...
Click to collapse
Good to know. Thank you!

Related

HTC One Looks Dead/Bricked - What to do next

*** SOLVED - Problem was my own stupidity ***
Got the HTC One a couple of days ago. Came back to Android after a few months on iPhone. Figured I'd jump right back into rooting and flashing custom ROMs.
Anyway, unlocked the phone, wanted to install Android Revolution 51, tried to upgrade firmware, and that's when things went sideways. Now, I can't do anything. Can Fastboot, but can't ADB. Have tried to load every driver in the book, but to no avail. CID is CWS_001 if that helps. Have been at this for a day and a half now. I need ideas.
thoughts?
Does it get detected on your window device manager when you plug it in?
sent from my mobile device
SaHiLzZ said:
Does it get detected on your window device manager when you plug it in?
sent from my mobile device
Click to expand...
Click to collapse
Yes. It shows up under Android USB Devices and says "My HTC"
diceman725 said:
Yes. It shows up under Android USB Devices and says "My HTC"
Click to expand...
Click to collapse
Then you should be able to restore it with ADB... No idea how yet, but as far as I know your not completely dead here.... I may however be completely out to lunch here...
Iz3man said:
Then you should be able to restore it with ADB... No idea how yet, but as far as I know your not completely dead here.... I may however be completely out to lunch here...
Click to expand...
Click to collapse
Would be very grateful. I agree, it would seem logical that I could ADB my way out, but at the moment, ADB doesn't recognize the device.
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Zedrox said:
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
I don't have a ROM loaded in the Virtual SD. And unless I'm mistaken, I can really only use ADB sideload at this point to load one up
Can you get into basic HTC recovery on the phone? I'm assuming you can if you can get fastboot working.
If so can't you just reflash a actual recovery from there, and then a rom from that? Apologies if this is completely irrelevant, I base all my android knowledge off my Desire.
Sent from my HTC Desire using Tapatalk 2
Adb reboot
sent from my mobile device
Zedrox said:
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Yeah now it does. I know if windows can see it you should be OK.
Try adb reboot recovery or adb reboot bootloader
Right be able to get into something there.
Iz3man said:
Yeah now it does. I know if windows can see it you should be OK.
Try adb reboot recovery or adb reboot bootloader
Right be able to get into something there.
Click to expand...
Click to collapse
Problem is I can't get into ADB. It doesn't recognize the device. Going to try to flash a recovery and see if that works.
diceman725 said:
Problem is I can't get into ADB. It doesn't recognize the device. Going to try to flash a recovery and see if that works.
Click to expand...
Click to collapse
OK I'm lost here Can you boot into recovery? Or do you have a blank screen from the start?
Either way I hope you get it, its a pain when they do that!
Iz3man said:
OK I'm lost here Can you boot into recovery? Or do you have a blank screen from the start?
Either way I hope you get it, its a pain when they do that!
Click to expand...
Click to collapse
I can get into recovery, yes...
If you can boot to recovery, are you not able to boot to OS? How does it look dead??
sent from my mobile device
SaHiLzZ said:
If you can boot to recovery, are you not able to boot to OS? How does it look dead??
sent from my mobile device
Click to expand...
Click to collapse
There is no OS. Somehow I blew it away. When I get home I am going to try to flash a zipped RUU. Hopefully that works.
diceman725 said:
There is no OS. Somehow I blew it away. When I get home I am going to try to flash a zipped RUU. Hopefully that works.
Click to expand...
Click to collapse
No luck on flashing the RUU file. It sends successfully, but fails on the write.
You need to post an output of fastboot getvar all (imei /sn removed)
sent from my mobile device
also nearly bricked
..
Please make a new thread.
sent from my mobile device
SaHiLzZ said:
You need to post an output of fastboot getvar all (imei /sn removed)
sent from my mobile device
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Accidentally erased operating system on HTC One M7

Hi, i run an HTC One M7 that was originally from AT&T. I unlocked it and use it in my country. Few days ago i wanted to install the stock Android and try it. I did everything as was said - unlocked the bootloader, s-off, recovery etc. after a few hours of the stock Android experience i wanted to change it to ARHD. As i changed it a question popped out asking if i want to root my device. I answered "yes", not knowing what it means. My phone was bricked and stuck on the HTC welcome screen since yesterday. I tried a lot of differend ways of fixing it and still no results. I locked and unlocked the bootloader again, tried to install the official RUU, but it doesn't want to. I get MTP driver error when connecting to my computer.
I have "can't mount SD card" on my phone. I'm pretty desperate, but i want to fix this issue and get back my phone. This will be a lesson for me.
Skyrocker94 said:
Hi, i run an HTC One M7 that was originally from AT&T. I unlocked it and use it in my country. Few days ago i wanted to install the stock Android and try it. I did everything as was said - unlocked the bootloader, s-off, recovery etc. after a few hours of the stock Android experience i wanted to change it to ARHD. As i changed it a question popped out asking if i want to root my device. I answered "yes", not knowing what it means. My phone was bricked and stuck on the HTC welcome screen since yesterday. I tried a lot of differend ways of fixing it and still no results. I locked and unlocked the bootloader again, tried to install the official RUU, but it doesn't want to. I get MTP driver error when connecting to my computer.
I have "can't mount SD card" on my phone. I'm pretty desperate, but i want to fix this issue and get back my phone. This will be a lesson for me.
Click to expand...
Click to collapse
post your fastboot getvar all minus the serial no and IMEI so we can find the files you'll need to restore you phone
clsA said:
post your fastboot getvar all minus the serial no and IMEI so we can find the files you'll need to restore you phone
Click to expand...
Click to collapse
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: --------------------
(bootloader) imei: -------------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.120s
Here we go! thanks a lot!!
Skyrocker94 said:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: --------------------
(bootloader) imei: -------------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.120s
Here we go! thanks a lot!!
Click to expand...
Click to collapse
download this ruu and run it, its the same version you already have / had on your phone, if you bootloader is unlocked then you will need to re-lock it first.
http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
with regards to your drivers problem, see FAQ 2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Thanks a ton!!! i hope it works!!!
Skyrocker94 said:
Thanks a ton!!! i hope it works!!!
Click to expand...
Click to collapse
fastboot oem lock
relocks the bootloader to run the RUU
if you have problems with the RUU
try this / unlocking the bootloader / flashing TWRP 2.6.3.3 and sideload this Guru Reset >> http://www.androidfilehost.com/?fid=23501681358545274
It worked. Thank you very much!
"Ask and it shall be given to you"
same issue here, no more SO and stuck in HTC log
Hello, help me please, i've search the RUU for restore my HTC but not are sure where's the right.
Here Original "fastboot getvar all" when device was working also w/o SO.
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.27.3218.14
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: H3G__402
INFObattery-status: good
INFObattery-voltage: 4102mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-1f512bb6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Thanks a lot for help, sorry for my English.
vanito said:
Hello, help me please, i've search the RUU for restore my HTC but not are sure where's the right.
Here Original "fastboot getvar all" when device was working also w/o SO.
Thanks a lot for help, sorry for my English.
Click to expand...
Click to collapse
another H3G__402 you need help from @Danny201281
he has the same phone
vanito said:
Hello, help me please, i've search the RUU for restore my HTC but not are sure where's the right.
Here Original "fastboot getvar all" when device was working also w/o SO.
Thanks a lot for help, sorry for my English.
Click to expand...
Click to collapse
Well I'm H3G__001 UK. H3G__402 is Italy right? Not that it makes a difference the software is all the same.
Unfortunately there is no ruu for H3G. What exactly happened with your phone it can hopefully be fixed without the need for an ruu.
Bad flash, wiped your os? Can you access bootloader or recovery?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Danny201281 said:
Well I'm H3G__001 UK. H3G__402 is Italy right? Not that it makes a difference the software is all the same.
Unfortunately there is no ruu for H3G. What exactly happened with your phone it can hopefully be fixed without the need for an ruu.
Bad flash, wiped your os? Can you access bootloader or recovery?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
this phone was w/o SO since i've buyed of 2 handle. was installed only a Custom Rom. i want make it S-OFF for installl anythingh for error from TWRP have done advanced wipe and have erase also this Rom whith all partition and BKP.
Phone enter in Recovery, hboot, fastboot and can flash RUU signed, (have tried with an BOX to flash Guru reset but Error becouse No signature), or if you have other Rom or other for fix this issue and after i want make S-OFF for change this Bad cid, if can help me please
vanito said:
this phone was w/o SO since i've buyed of 2 handle. was installed only a Custom Rom. i want make it S-OFF for installl anythingh for error from TWRP have done advanced wipe and have erase also this Rom whith all partition and BKP.
Phone enter in Recovery, hboot, fastboot and can flash RUU signed, (have tried with an BOX to flash Guru reset but Error becouse No signature), or if you have other Rom or other for fix this issue and after i want make S-OFF for change this Bad cid, if can help me please
Click to expand...
Click to collapse
Hi and sorry for the delayed reply, as I say there is no ruu for h3g, but it sounds as if you just need to push a compatible Rom to the phone, what is you current version of TWRP.
I do have some h3g stock nandroids, one for jb 4.3 and one for kk 4.4.2. I'll need to upload them for you and I can't do that until later this evening as I'm in work now. If you want to go s-off the jb 4.3 nandroid has worked for me everytime so would be worth a try. I'll upload it tonight and send you a link as soon as it's available.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
You're such a nice and friendly forum mate, @Danny201281
tetakpatalked from Nexus 7 flo
Danny201281 said:
Hi and sorry for the delayed reply, as I say there is no ruu for h3g, but it sounds as if you just need to push a compatible Rom to the phone, what is you current version of TWRP.
I do have some h3g stock nandroids, one for jb 4.3 and one for kk 4.4.2. I'll need to upload them for you and I can't do that until later this evening as I'm in work now. If you want to go s-off the jb 4.3 nandroid has worked for me everytime so would be worth a try. I'll upload it tonight and send you a link as soon as it's available.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Not worry, important i can fix with you help this problem.
My version of TWRP installed now is "twrp-2.7.1.0a-m7" this device first of i Erase all had installed an VENOM Rom, not remember wich ViperOnes version, my Getvar All you have seen, i want listen to you becouse not understand good about these HTC w/o sd card.
If you can send to me this nandroid jb 4.3 and if please write also if i can flash how normal rom/Ruu or how do.... you help is very good for me :good:
wait for you link to download, please if cannot use Mega.co is good becouse here is blocked and impossible open this, Ciao:good:
vanito said:
Not worry, important i can fix with you help this problem.
My version of TWRP installed now is "twrp-2.7.1.0a-m7" this device first of i Erase all had installed an VENOM Rom, not remember wich ViperOnes version, my Getvar All you have seen, i want listen to you becouse not understand good about these HTC w/o sd card.
If you can send to me this nandroid jb 4.3 and if please write also if i can flash how normal rom/Ruu or how do.... you help is very good for me :good:
wait for you link to download, please if cannot use Mega.co is good becouse here is blocked and impossible open this, Ciao:good:
Click to expand...
Click to collapse
Ok sorry I was very busy last night. I am on this for you now, I'll post link as soon as it's ready but my upload seed is very poor
I created this nandroid using TWRP 2.6.3.3 but it should restore fine using other versions of TWRP.
Do you have adb working when in recovery mode? You will need it to push the nandroid to the device.
Danny201281 said:
Ok sorry I was very busy last night. I am on this for you now, I'll post link as soon as it's ready but my upload seed is very poor
I created this nandroid using TWRP 2.6.3.3 but it should restore fine using other versions of TWRP.
Do you have adb working when in recovery mode? You will need it to push the nandroid to the device.
Click to expand...
Click to collapse
Hello, can leave this version of TWRP: "twrp-2.7.1.0a-m7", that i've or you can suggest another version?
System not Mount, i've tryed to push in fastbootRUU but fail anythinghs i want push.
I've tryed putting phone in Recovery mode and i can see from "device manager" that have "adb android" or similar then if open can see "My Htc", if i put in normal mode, (is w/o Boot.img), i can see MTP that install/uninstall and phone how "Cd Unit external", (cannot open).
Not warry where upload it, important not use Mega.co becouse in Italy is Blocked, any other site is ok.
Please can send to me also Command for Push this Nandroid 4.3 in Recovery mode?, (i've also one dongle + sw but for Flash anythinghs requiere fastboot RUU mode), anyway i'm looking forward this Nandroid Bkp and how push in phone hooping that i can fix the phone
@vanito backup done with TWRP 2.6.3.3 is compatible with 2.7.1.0
He is asking you about ADB and using command line of your PC to push the files. Do you know how to do it? Do you have SDK installed on your PC?
tetakpatalked from N7100
vanito said:
Hello, can leave this version of TWRP: "twrp-2.7.1.0a-m7", that i've or you can suggest another version?
System not Mount, i've tryed to push in fastbootRUU but fail anythinghs i want push.
I've tryed putting phone in Recovery mode and i can see from "device manager" that have "adb android" or similar then if open can see "My Htc", if i put in normal mode, (is w/o Boot.img), i can see MTP that install/uninstall and phone how "Cd Unit external", (cannot open).
Not warry where upload it, important not use Mega.co becouse in Italy is Blocked, any other site is ok.
Please can send to me also Command for Push this Nandroid 4.3 in Recovery mode?, (i've also one dongle + sw but for Flash anythinghs requiere fastboot RUU mode), anyway i'm looking forward this Nandroid Bkp and how push in phone hooping that i can fix the phone
Click to expand...
Click to collapse
twrp 2.7.1.0 should work fine :good:
adb will only work in recovery mode. Put phone in recovery and connect usb. Then in the adb/fastboot command line type
Code:
adb devices
You should see an output of your phone's serial no. If you did it's working. You can test adb push with a Rom if you have one. Rename the Rom file to "rom.zip" and put it in your adb/fastboot folder. Then in the command line type
Code:
adb push rom.zip /sdcard
The push will take several minutes the command window will be unresponsive until it's done. When it's finished the push you should be able to Install the Rom using TWRP.
P.S. The stock nandroid is uploading to dropbox. This is ok for use in Italy?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
@vanito you have got a real little guide for Windows by @Danny201281
In the case that you are a Linux user, it works just slightly different: in such case check my little thread about running fastboot & ADB in Ubuntu. It is posted in the Nexus 7 section but ADB works for Samsung just the same way.
tetakpatalked from Nexus 7 flo
Danny201281 said:
twrp 2.7.1.0 should work fine :good:
adb will only work in recovery mode. Put phone in recovery and connect usb. Then in the adb/fastboot command line type
Code:
adb devices
You should see an output of your phone's serial no. If you did it's working. You can test adb push with a Rom if you have one. Rename the Rom file to "rom.zip" and put it in your adb/fastboot folder. Then in the command line type
Code:
adb push rom.zip /sdcard
The push will take several minutes the command window will be unresponsive until it's done. When it's finished the push you should be able to Install the Rom using TWRP.
P.S. The stock nandroid is uploading to dropbox. This is ok for use in Italy?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
@Danny201281, ok i have this twrp 2.7.1.0 also and can install replace the other one i've installed:good:
Yes i've installed adb&fastboot in C: (principal directory), i use Win7 32 bit and can use also win Xp in the 2 pcs i've adb&fastboot installed.:good:
Yes, i know a little about use of these adb or fastboot, specific command for this case i can copy from this you good guide:good:
I've tested pushing "guru reset..." from fastboot yesterday but have get one Error 24, not have tested pushing via Adb command, but now i see you command above and can test this.
Sorry, i not know which Rom can push and if you can advise me about wich push is big help, (if you can post only link to Rom) for me, if possible any Rom for to make S-Off after that i fix this phone.
Yes, Dropbox i can use here if you give me access for download the Nandroid Bkp 4.3.
Last question, if push of Rom goes all ok, after i open phone in recovery and find this Rom in Sd Card, right?...then from "Install>Sd Card>Rom" swipe and will be installed right?
Ok, after i install this Rom always from recovery can install you nondroid bkp 4.3, ok?, :good:
I'm ready if can send to me link for this Rom and Link of dropbox i want try to ceck anythinghs.

[Q] Need information about current state of this phone I bought.

Hi,
I purchased an HTC One M7 over the internet. It arrived with CyanogenMod on it, but to use my SIM with it, I had to flash AT&T's stock ROM onto the phone. I know little about actually dealing with Phone ROMs & other software things, so I'm unsure what I currently have on this phone.
If I do a factory reset, SuperSU Installer is always an app pre-installed. If I update it and try to root the device, after it reboots, a red triangle with exclamation point comes up with a phone under it. Then after some time, or if I manually do it, it reboots and enters a reboot loop until I go to the boot loader and Factory Reset it again. I read somewhere that this comes up to show that the Recovery is write-protected or something similar.
When booting to the bootloader, this is the information that appears:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
<date>
HBOOT
<commands>
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
SHOW BARCODE
I don't have a warranty to begin with, so I don't particularly care if the TAMPERED message comes up.
If I try and flash CyanogenMod onto the phone using CM's desktop & phone program/app, when the phone reboots, it goes to the bootloader which causes the program on my desktop computer to lose track of the phone.
So, now to my question: What state is this phone in? i.e. Is it rooted? If it is, what is installed on it aside from HBOOT & AT&T's stock ROM, if anything? If it's not, is it because I used AT&T's stock ROM?
My ultimate goal is to get CyanogenMod back on this phone correctly, but everything I've tried with that has hit some roadblock (their desktop program/phone app combo failing, installing TWRP failing, etc.) Any help is appreciated.
Thanks,
Tremor.
Your phone is still S-ON. To be free to do what you want you need to get to S-OFF, methinks.
cichlidiot said:
Your phone is still S-ON. To be free to do what you want you need to get to S-OFF, methinks.
Click to expand...
Click to collapse
Thanks.
That's one thing I was curious about though. If I require S-OFF to install CM, then did my installing of AT&T's ROM cause it to switch to S-ON since it had CM on it before? Just curious.
TremorPV said:
Hi,
I purchased an HTC One M7 over the internet. It arrived with CyanogenMod on it, but to use my SIM with it, I had to flash AT&T's stock ROM onto the phone. I know little about actually dealing with Phone ROMs & other software things, so I'm unsure what I currently have on this phone.
If I do a factory reset, SuperSU Installer is always an app pre-installed. If I update it and try to root the device, after it reboots, a red triangle with exclamation point comes up with a phone under it. Then after some time, or if I manually do it, it reboots and enters a reboot loop until I go to the boot loader and Factory Reset it again. I read somewhere that this comes up to show that the Recovery is write-protected or something similar.
When booting to the bootloader, this is the information that appears:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
<date>
HBOOT
<commands>
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
SHOW BARCODE
I don't have a warranty to begin with, so I don't particularly care if the TAMPERED message comes up.
If I try and flash CyanogenMod onto the phone using CM's desktop & phone program/app, when the phone reboots, it goes to the bootloader which causes the program on my desktop computer to lose track of the phone.
So, now to my question: What state is this phone in? i.e. Is it rooted? If it is, what is installed on it aside from HBOOT & AT&T's stock ROM, if anything? If it's not, is it because I used AT&T's stock ROM?
My ultimate goal is to get CyanogenMod back on this phone correctly, but everything I've tried with that has hit some roadblock (their desktop program/phone app combo failing, installing TWRP failing, etc.) Any help is appreciated.
Thanks,
Tremor.
Click to expand...
Click to collapse
Ok can you boot the phone to the bootloader connect fastboot usb, then in the fastboot command line type
Code:
fastboot getvar all
This will give an output of all the version information for the device. Post it here after removing your IMEI and Serial numbers. You don't want to advertise those
And no you don't need s-off to flash roms, and flashing stock at&t did not and cannot set s-on again.
Let's start with the getvar and take it from there :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
If it goes to boot loader then it sounds like your missing a good recovery image. Flash the recovery and then flash a rom.
Stay away from PC installers and ROM manager.
Danny201281 said:
Ok can you boot the phone to the bootloader connect fastboot usb, then in the fastboot command line type
Code:
fastboot getvar all
This will give an output of all the version information for the device. Post it here after removing your IMEI and Serial numbers. You don't want to advertise those
And no you don't need s-off to flash roms, and flashing stock at&t did not and cannot set s-on again.
Let's start with the getvar and take it from there :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Yes, I entered the bootloader, then I switched to Fastboot which gave me a screen like this:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
<date>
FASTBOOT
<commands>
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I move the selection down to REBOOT or any other command, FASTBOOT changes to FASTBOOT USB and stays that way.
However, my PC says the USB device malfunctioned, and running the "fastboot getvar all" command does this:
Code:
< waiting for device >
When the HTC One is on and plugged in, it shows up just fine as "My HTC One" under Android USB Devices in Device Manager, so the drivers work.
zelendel said:
If it goes to boot loader then it sounds like your missing a good recovery image. Flash the recovery and then flash a rom.
Stay away from PC installers and ROM manager.
Click to expand...
Click to collapse
It only goes to bootloader when I hold down the Volume Down button.
Not sure how to do that. Still learning.
TremorPV said:
Yes, I entered the bootloader, then I switched to Fastboot which gave me a screen like this:
Code:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
FASTBOOT
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
If I move the selection down to REBOOT or any other command, FASTBOOT changes to FASTBOOT USB and stays that way.
However, my PC says the USB device malfunctioned, and running the "fastboot getvar all" command does this:
Code:
< waiting for device >
When the HTC One is on and plugged in, it shows up just fine as "My HTC One" under Android USB Devices in Device Manager, so the drivers work.
It only goes to bootloader when I hold down the Volume Down button.
Not sure how to do that. Still learning.
Click to expand...
Click to collapse
Sounds like a driver problem on the pc side. Check your drivers are installed correctly. Your phone should appear in device manager as "My HTC" Edit :- I see the drivers are working when the phone is on and then fail see this FAQ post Q (2) to fix your drivers after the malfunction message http://forum.xda-developers.com/showthread.php?p=52135024
What operating system do you have on your pc Windows 7, 8 or 8.1. / Mac OSX?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Sounds like a driver problem on the pc side. Check your drivers are installed correctly. Your phone should appear in device manager as "My HTC" Edit :- I see the drivers are working when the phone is on and then fail see this FAQ post Q (2) to fix your drivers after the malfunction message http://forum.xda-developers.com/showthread.php?p=52135024
What operating system do you have on your pc Windows 7, 8 or 8.1. / Mac OSX?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Will do. (at work atm)
Windows 8.1 64 bit, using WIndows 7 64 bit drivers.
TremorPV said:
Will do. (at work atm)
Windows 8.1 64 bit, using WIndows 7 64 bit drivers.
Click to expand...
Click to collapse
That's what I was afraid of, I can't speak from personal experience as I use Windows very little and if I do it's Windows 7. But to the best of my knowledge Windows 8 and 8.1 are a bit finicky when it comes to adb/fastboot especially if your on hboot 1.44.
There's a thread here you may find helpful there are a few solutions discussed here http://forum.xda-developers.com/showthread.php?t=2347317
Personally I prefer Linux. When all else fails Linux doesn't see my guide here it contains everything you need to know to use Linux without installing it on your pc. Just boot from a usb stick, no drivers require. Just Linux and adb/fastboot http://forum.xda-developers.com/showthread.php?p=54272479
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
That's what I was afraid of, I can't speak from personal experience as I use Windows very little and if I do it's Windows 7. But to the best of my knowledge Windows 8 and 8.1 are a bit finicky when it comes to adb/fastboot especially if your on hboot 1.44.
There's a thread here you may find helpful there are a few solutions discussed here http://forum.xda-developers.com/showthread.php?t=2347317
Personally I prefer Linux. When all else fails Linux doesn't see my guide here it contains everything you need to know to use Linux without installing it on your pc. Just boot from a usb stick, no drivers require. Just Linux and adb/fastboot http://forum.xda-developers.com/showthread.php?p=54272479
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Figured. I had heard they worked with 8, but I guess not.
Awesome.
Me too. If only all of my games worked on Linux. Will try this and get back to you.
TremorPV said:
Figured. I had heard they worked with 8, but I guess not.
Awesome.
Me too. If only all of my games worked on Linux. Will try this and get back to you.
Click to expand...
Click to collapse
I hear you about the gaming on Linux. They seem to be making progress though. At least we have Steam now :good:
But yeah my pc dual boots with Windows 7 for gaming.
Danny201281 said:
I hear you about the gaming on Linux. They seem to be making progress though. At least we have Steam now :good:
But yeah my pc dual boots with Windows 7 for gaming.
Click to expand...
Click to collapse
So it worked. Boo ya. Well... kinda. Here is my output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: >number<
(bootloader) imei: >number<
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3892mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.043s
Useful.
I tried it again to see if I could get it past that FAILED message and this is what I get:
Code:
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 1.002s
wat
TremorPV said:
So it worked. Boo ya. Well... kinda. Here is my output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: >number<
(bootloader) imei: >number<
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3892mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.043s
Useful.
I tried it again to see if I could get it past that FAILED message and this is what I get:
Code:
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 1.002s
wat
Click to expand...
Click to collapse
The failed message is normal with Hboot 1.44 you will always get that until you update hboot.
Danny201281 said:
The failed message is normal with Hboot 1.44 you will always get that until you update hboot.
Click to expand...
Click to collapse
Ah. Good to know.
So in my journey to learn, I decided I wanted to try updatig HBOOT. Which, from what I've read, requires S-OFF, so I went to Firewater. Unfortunately, I didn't realize I needed S-OFF & Firewater, and did the following with S-ON:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip hboot_firewater>version<.zip
Which failed. My phone still works and can get to the fastboot/HBOOT screen, so from what I can tell, no harm was done.
Running firewater based on the instructions on their webpage doesn't really do anything. It pushes the firewater file to the /tmp on the device, but won't run it. Not sure why. Specifically, this happens:
Code:
adb reboot
adb wait-for-device push firewater /data/local/tmp
adb shell
That goes fine. This is where the strange things start:
Code:
[email protected]:/ $ su
1|[email protected]:/ $ chmod 755 /data/local/tmp/firewater
[email protected]:/ $ /data/local/tmp/firewater
error, run firewater as root. su or FU!!!!!!
1|[email protected]:/ $ su /data/local/tmp/firewater
That's exactly as it appears in the Terminal. While it's doing this, I get lots of pop ups on Linux about how it's unable to mount the Android Phone. I check my phone after doing the above commands, and it's on the stock AT&T ROM I installed.
There's nothing mentioned about Firewater and nothing has happened AFAIK. Firewater's page says there should be a prompt or something, but there's not.
TremorPV said:
So it worked. Boo ya. Well... kinda. Here is my output:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: >number<
(bootloader) imei: >number<
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3892mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.043s
Useful.
I tried it again to see if I could get it past that FAILED message and this is what I get:
Code:
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 1.002s
wat
Click to expand...
Click to collapse
Ok so let's get you phone booting again.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Download this and place it in your fastboot folder. Rename it recovery.img
Flash your recovery with fastboot
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Now select recovery from the bootloader menu. Now we can push the Rom.
Download this stock Rom drop it in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/did/guru_reset_m7_1-26-502-12-zip/
And push to the phone with
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes several minutes when it's done install the Rom with twrp recovery.
---------- Post added at 07:37 PM ---------- Previous post was at 07:27 PM ----------
Oh so you have a Rom booting? Ok I'm a little busy for the next hour. If you want to go s-off don't update anything just yet.
Getting s-off will be harder after you update
Use this toolkit to get s-off with revone as your on hboot 1.44 http://forum.xda-developers.com/showthread.php?t=2364445
Danny201281 said:
Ok so let's get you phone booting again.
http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Download this and place it in your fastboot folder. Rename it recovery.img
Flash your recovery with fastboot
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Now select recovery from the bootloader menu. Now we can push the Rom.
Download this stock Rom drop it in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/did/guru_reset_m7_1-26-502-12-zip/
And push to the phone with
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes several minutes when it's done install the Rom with twrp recovery.
---------- Post added at 07:37 PM ---------- Previous post was at 07:27 PM ----------
Oh so you have a Rom booting? Ok I'm a little busy for the next hour. If you want to go s-off don't update anything just yet.
Getting s-off will be harder after you update
Use this toolkit to get s-off with revone as your on hboot 1.44 http://forum.xda-developers.com/showthread.php?t=2364445
Click to expand...
Click to collapse
ARGH. Didn't read the whole post before doing anything. Finished flashing the recovery.img to the recovery before I finished your post. I needed a different recovery anyway as I don't like the current one, so yay at least. I didn't boot into recovery though, so hopefully I'm fine.
It's fine. Take your time. I've got all day.
Yes, I would like S-OFF just so I can update HBOOT so that if I want to tinker with my phone in the future it will be easier to do. I may not like CyanogenMod, so trying out Kit Kat and other things will be easier (I imagine) without whatever is making it hard to deal with this phone.
Danny201281 said:
I hear you about the gaming on Linux. They seem to be making progress though. At least we have Steam now :good:
But yeah my pc dual boots with Windows 7 for gaming.
Click to expand...
Click to collapse
Same here. Give me my games and a few apps and good bye Windows lol
TremorPV said:
ARGH. Didn't read the whole post before doing anything. Finished flashing the recovery.img to the recovery before I finished your post. I needed a different recovery anyway as I don't like the current one, so yay at least. I didn't boot into recovery though, so hopefully I'm fine.
It's fine. Take your time. I've got all day.
Yes, I would like S-OFF just so I can update HBOOT so that if I want to tinker with my phone in the future it will be easier to do. I may not like CyanogenMod, so trying out Kit Kat and other things will be easier (I imagine) without whatever is making it hard to deal with this phone.
Click to expand...
Click to collapse
Ok so cool, flashing recovery won't cause any issues with s-off later on, so you can flash what ever recovery you preffer.
Hboot can be updated without s-off but once you do it gets much harder to s-off as HTC have implemented patches into the newer firmware to try and prevent it. unless you wanna pay $25 for Sunshine app which should work regardless.
Getting s-off with revone is by far the easiest way to do it for free if your on hboot 1.44 Personally I've never used revone all devices I s-offed were already on higher hboot versions so had to use other methods. So you should read through the link I posted to get that done but it sounds fairly simple using that toolkit. Once your s-off the sky's the limit pretty much.
Danny201281 said:
Ok so cool, flashing recovery won't cause any issues with s-off later on, so you can flash what ever recovery you preffer.
Hboot can be updated without s-off but once you do it gets much harder to s-off as HTC have implemented patches into the newer firmware to try and prevent it. unless you wanna pay $25 for Sunshine app which should work regardless.
Getting s-off with revone is by far the easiest way to do it for free if your on hboot 1.44 Personally I've never used revone all devices I s-offed were already on higher hboot versions so had to use other methods. So you should read through the link I posted to get that done but it sounds fairly simple using that toolkit. Once your s-off the sky's the limit pretty much.
Click to expand...
Click to collapse
Sweet.
Figured. Sounds just like when I jailbroke my old PSP-2000.
I tried that tool, but this is what happened:
Code:
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb reboot
error: more than one device and emulator
Revone & Firewater both say this. This tool does not have a Linux version unfortunately.
TremorPV said:
Sweet.
Figured. Sounds just like when I jailbroke my old PSP-2000.
I tried that tool, but this is what happened:
Code:
adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
adb reboot
error: more than one device and emulator
Revone & Firewater both say this. This tool does not have a Linux version unfortunately.
Click to expand...
Click to collapse
What output do you get from adb devices?

[Q] No SO, Drivers Problems, PLEASE HELP

Hi I'm going crazy right now, I really need some help, here's the history:
Today I bought a htc one m7 from a girl and when she was restoring it I saw that it was with a custom recovery, I didnt care about it becouse anyway I was going to install it some day. After that I went home and started searching some lollipop rom.
Well I downloaded it and copied it to the internal storage, I was ready to flash so I did it.
After flashing the rom it begins to bootloop, so I thougt "ok, it maybe need just a wipe" so I wiped it, as it didnt solved the problem I wiped again but this time with all boxes checked, after that y realized that I was wiping EVERYTHING (It happened before in a nexus 5 and 4).
Ok, I thought f**k it, I'll push the files with adb and problem solved, but when I conected the phone to the pc it has now driver problems, I cant get adb to work, neither fasboot, I installed and uninstalled al drivers I found on the internet, I really dont know what else to do.
If I conect the phone with the pc in fastboot mode in devices manager it says that the usb device ist recognized and something like that there is an error with the number.
And when I conect it in recovery mode it says "one" with the exclamation symbol, I red a lot of posts about how to solve it, but when I force install the drivers nothing happens.
Help me please, I dont know what more to do. And sorry about my english
If you need some information/pictures, just ask for it
Im new with this phone and I have no idea what to do
nachoy9 said:
Hi I'm going crazy right now, I really need some help, here's the history:
Today I bought a htc one m7 from a girl and when she was restoring it I saw that it was with a custom recovery, I didnt care about it becouse anyway I was going to install it some day. After that I went home and started searching some lollipop rom.
Well I downloaded it and copied it to the internal storage, I was ready to flash so I did it.
After flashing the rom it begins to bootloop, so I thougt "ok, it maybe need just a wipe" so I wiped it, as it didnt solved the problem I wiped again but this time with all boxes checked, after that y realized that I was wiping EVERYTHING (It happened before in a nexus 5 and 4).
Ok, I thought f**k it, I'll push the files with adb and problem solved, but when I conected the phone to the pc it has now driver problems, I cant get adb to work, neither fasboot, I installed and uninstalled al drivers I found on the internet, I really dont know what else to do.
If I conect the phone with the pc in fastboot mode in devices manager it says that the usb device ist recognized and something like that there is an error with the number.
And when I conect it in recovery mode it says "one" with the exclamation symbol, I red a lot of posts about how to solve it, but when I force install the drivers nothing happens.
Help me please, I dont know what more to do. And sorry about my english
If you need some information/pictures, just ask for it
Im new with this phone and I have no idea what to do
Click to expand...
Click to collapse
go here and read post 2 FAQ 2
http://forum.xda-developers.com/showthread.php?t=2541082
That should get your drivers working
post your fastboot getvar all (minus your serial no and IMEI) and I can try and help you find the correct files for your phone
clsA said:
go here and read post 2 FAQ 2
http://forum.xda-developers.com/showthread.php?t=2541082
That should get your drivers working
post your fastboot getvar all (minus your serial no and IMEI) and I can try and help you find the correct files for your phone
Click to expand...
Click to collapse
Wow THANKS A LOT, I was doing something like that when installing drivers but not that, now I have adb working.
I dont want to do anything more wrong, can you tell me wich file to flash over TWR to get it working? my fastboot shows:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-CWS_001
HBOOT-1.44.0000
RADIO-A1.14.3250.13
OpenDPS-v26.120.274.0202
eMMC-boot
May 3 2013,19:16:59:-1
I cant post the getvar becouse I have windows 8.1 and as I saw, fastboot comands doesnt works with windows 8.1 if I have HBOOT-1.44
clsA said:
go here and read post 2 FAQ 2
http://forum.xda-developers.com/showthread.php?t=2541082
That should get your drivers working
post your fastboot getvar all (minus your serial no and IMEI) and I can try and help you find the correct files for your phone
Click to expand...
Click to collapse
I used my grandmas PC
C:\Users\Miriam\Desktop\androidññ\platform-tools>fastboot devices
HT36KW908410 fastboot
C:\Users\Miriam\Desktop\androidññ\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------
(bootloader) imei: ------
(bootloader) meid: ------
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.068s
nachoy9 said:
I used my grandmas PC
C:\Users\Miriam\Desktop\androidññ\platform-tools>fastboot devices
HT36KW908410 fastboot
C:\Users\Miriam\Desktop\androidññ\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------
(bootloader) imei: ------
(bootloader) meid: ------
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.068s
Click to expand...
Click to collapse
I would use this first
http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
clsA said:
I would use this first
http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
Click to expand...
Click to collapse
how does it work? I have to put the phone on fastboot mode or in a custom recovery for adb comands?
nachoy9 said:
how does it work? I have to put the phone on fastboot mode or in a custom recovery for adb comands?
Click to expand...
Click to collapse
just leave the phone plugged into the PC and in Fastboot USB mode on the bootloader screen
then run the RUU
clsA said:
just leave the phone plugged into the PC and in Fastboot USB mode on the bootloader screen
then run the RUU
Click to expand...
Click to collapse
Just made it, thanks a lot, do you know how to install updates now? becouse it doesnt find any OTA
nachoy9 said:
Just made it, thanks a lot, do you know how to install updates now? becouse it doesnt find any OTA
Click to expand...
Click to collapse
are you on the AT&T network ?
clsA said:
are you on the AT&T network ?
Click to expand...
Click to collapse
No, Im from Uruguay (South America)
nachoy9 said:
No, Im from Uruguay (South America)
Click to expand...
Click to collapse
I recommend you convert your phone to Developer edition
I posted instructions here for another guy >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
clsA said:
I recommend you convert your phone to Developer edition
I posted instructions here for another guy >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
Click to expand...
Click to collapse
Ill do it, THANKS A LOT
clsA said:
I recommend you convert your phone to Developer edition
I posted instructions here for another guy >> http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
Click to expand...
Click to collapse
Sorry Im bothering you again, but I tryed to install that RUU and it says that there is an error with the image version or something like that
nachoy9 said:
Sorry Im bothering you again, but I tryed to install that RUU and it says that there is an error with the image version or something like that
Click to expand...
Click to collapse
Did you change your CID?
clsA said:
Did you change your CID?
Click to expand...
Click to collapse
Yes
nachoy9 said:
Yes
Click to expand...
Click to collapse
your on 3.x 502 AT&T
try the 4.X.1540 DE RUU here >> http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353887_signed_3.exe
If it gives you an error flash this firmware then the RUU
https://www.androidfilehost.com/?fid=95887005526790121
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
clsA said:
your on 3.x 502 AT&T
try the 4.X.1540 DE RUU here >> http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353887_signed_3.exe
If it gives you an error flash this firmware then the RUU
https://www.androidfilehost.com/?fid=95887005526790121
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
Ok, ill try and tomorrow I tell you if it worked, thanks

[Fixed] Bricked Hboot 1.44 with RUU 1.31 (Explanation on how solved in OP)

[Fixed][Solution]
This should work for anyone who soft bricked there device but still has the 1.44 HBoot to allow them to still flash a recovery. I did not come up with any of this but was helped by nkk71 who showed me the way. I dealt with this problem for over 2 days now non-stop trying to fix it only missing 1 step that made all the difference.
This method is for a HTC One (M7) Sprint Variant:
-Be sure to use HTCDev to unlock your phone and flash a custom recovery. (I used TWRP)
-Be sure to have all the adb and fastboot exe files needed. If you bricked your phone you most likely already do but if not there are tons of links on the forums to help you get all the information you need from them.
-Check to make sure what RUU your phone is at by going into fastboot and using a cmd window type: fasboot getvar all. This will display your phones information. If you happen to be at 1.31 like my phone was you will need to do the next step, if not then find your recovery.
- Fix your version main to say 1.29.651.10 by editing the misc partition
Boot into recovery
In the recovery mount your device. I mounted all parts in TWRP.
Open a cmd window and doucle check that your device is connected by typing: adb devices
(If it shows a set up numbers and letters and then says recovery then that is your device.)
Now type: adb shell
type: echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
type: adb reboot bootloader
Once it loads back into the bootloader click on fastboot and check to see if your device is connected by typing: fastboot devices
If you see you device type: fastboot oem lock (This will relock your device)
- Now you are ready to run the RUU. (After it runs your phone is back to stock)
If any of this is confusing, there are links below that were used to get me through this. If you need to do this I wish you luck.
Original Post:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.
toxicfumes22 said:
So basically I erased everything. Not sure how but phone Bricked. Luckily i have a 1.44Hboot and I simply just burned the recovery back.
Unforunately I've stopped messing with phones for about 2 years so it took me forever to get everything set back up properly. Now my biggest issue is I can't manage to get a ROM to boot anymore. The closest one is ViperOne 8, I've tried Android Revolution HD91.1 (which started all my troubles), NUSenSeven which is having issues for more people as well, and tried a very basic Stock M7 one.
Any information you give please act like I'm stupid. I can do adb and fastboot, but if you just say flash it, please dont expect me to know how. I've forgotten tons.
Anyways, currently my phone shows the:
*Tampered*
*Unlocked*
S-On
I have been trying to get it to S-off and then remove the Tampered but I can't get s-off with Revone.
Gives me Error = 1 and I'm just totally lost. But not I can't even seem to get a ROM to load and when it does I have no Service on this phone anymore and I have to remove the HTCsetupwizard.apk. Unfortunately sometimes this does not show up in system/app and under system might not show anything at all.
If that is standard to happen right after a fresh install without loading then that kind of makes sense. Also, I only wait about 10minutes on booting for the roms. Only Rom I wait longer on is the ViperOne 8 as it shows upgrading.
Please advise, I'm will to try anything. I'm having a huge headache with this and throwing the phone into a wall is becoming a reality.
Click to expand...
Click to collapse
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output
nkk71 said:
1- please post a "fastboot getvar all" (excluding IMEI, MEID and s/n)
2- looks like you're on Sprint, which is different that the GSM version of the M7, and has a different partition table
3- you may need to use an RUU to get your partitions back to normal
4- revone wont work on such new ROMs, even if hboot is 1.44 the ROM still plays a factor
let's start with the "fastboot getvar all" output
Click to expand...
Click to collapse
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4117mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.059s
2) Yes on Sprint, but with no activation on this phone now.
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
BTW, Thank you for the response.
toxicfumes22 said:
BTW, Thank you for the response.
Click to expand...
Click to collapse
Sure, no problem.
toxicfumes22 said:
1) C:\adb\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
2) Yes on Sprint, but with no activation on this phone now.
Click to expand...
Click to collapse
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
toxicfumes22 said:
3) RUU would be 1.31, I relocked phone and went to use the RUU but don't know how to flash it.
Click to expand...
Click to collapse
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
toxicfumes22 said:
4) I figured that with Revone thats why I attempted the RUU but got stuck there. I'll have to refind the RUU again though as I downloaded about 40GB yesterday and my SSD doesn't have that much room anymore. Waiting for windows 10 which is far away.
Click to expand...
Click to collapse
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction
nkk71 said:
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
Click to expand...
Click to collapse
Nice trick, still learning a lot from you
alray said:
Nice trick, still learning a lot from you
Click to expand...
Click to collapse
it's an "old trick", i take no credit at all for it ... as long as hboot version is the same, fixing the version-main (using adb or even the "misctool" <- it's somewhere on xda, dont have a link handy atm) should work fine
extract:
Code:
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version... [I]<- this is where it would fail, without that fix[/I]
(bootloader) checking hboot version... [I]<- this is where it would fail if hboot is higher[/I]
(bootloader) start image[boot] unzipping & flushing...
nkk71 said:
Sure, no problem.
okay, so it's a Sprint M7 with a messed up partition table, so yes, best course of action is probably RUUing
There is no 1.31.651.2 RUU (signed and encrypted) as far as I looked (which isnt very far, but I think it would have show up)
revone will need hboot 1.44 (dated pre June 2013) and a compatible ROM to work.
So course(s) of action:
A) fix your version main to say 1.29.651.10 by editing the misc partition; example here
then run full 1.29.651.10 RUU.EXE
then you can use revone
or
B) flash newer version RUU.EXE
use sunshine (paid app $25) to get S-OFF
note: you will likely need to update firmware first for the ruu to work properly
hope that points you in the right direction
Click to expand...
Click to collapse
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.
toxicfumes22 said:
I'd like to do option A but unfortunately I do not know how to use adb in recovery. I only know how to use it when android is running. The rest I should be able to do.
Click to expand...
Click to collapse
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.
New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.
toxicfumes22 said:
New Getvar all after I guessed that mounting the phone would allow an adb connection
C:\adb\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.651.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4329mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.062s
So do this mean that I am ready to run the .exe while in fastboot?
Of course after relocking the device. just want to confirm as I tried this earlier but missed the first step which was most likely crucial.
Click to expand...
Click to collapse
yes should work fine now, give it a try.
alray said:
yes should work fine now, give it a try.
Click to expand...
Click to collapse
nkk71 said:
you use adb shell same in recovery (actually better) as you use it in a booted & rooted rom, unfortunately, i can't do that right now, so either @alray will have to help you
or it'll have to wait till tomorrow.
Click to expand...
Click to collapse
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.
toxicfumes22 said:
I have a phone again. Thank you so much.
Imagine someone frustrated for over 2days spending 10+ hours a day readying, flashing and trying everything to get their phone to work with limited knowledge.
Now imagine that same person jumping up and down with joy. (That's me now)
Thank you so much for your help. Your links did the trick, they were what I couldn't find.
Now that I know how to do this, I'm going to try RevOne, flash a new Firmware and then flash one of the new roms I wanted. If any of this fails then I'm done with this stuff for some time, haha.
Click to expand...
Click to collapse
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
All thanks for you
My only contribution here was to say "give it a try" :laugh:
alray said:
All thanks for you
My only contribution here was to say "give it a try" [emoji23]
Click to expand...
Click to collapse
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk
nkk71 said:
Glad everything worked out
And for once, thank you for updating the title and first post (you may wanna check that echo command though)
And many thanks to @alray
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
I copied and pasted, its exactly what I used. If it's wrong let me know and I'll fix though.
Another update though is I am now Unlocked with S-Off w/o Tampered. Basically what I wanted.
Now should be my last questions, but it's a good idea to update to the newest firmware correct?
Firmware will never be able to stop me from achieve what I just did to fix the phone correct?
nkk71 said:
Sometimes, that is all what is needed
I think the OP agrees.
Sent from my SM-P905 using Tapatalk
Click to expand...
Click to collapse
Yup, I was going to not do a thing until I had a response. I was just worried I'd somehow mess it up. Just one confirmation that it looked good was enough to give me confidence.

Categories

Resources