Boootloop and/or Stuck at Logo - AT&T HTC One (M7)

Hi,
For no obvious reasons my phone went to bootloop yesterday night and I've been trying to fix it by different methods suggested in forums. But my phone does either of two things after changes/updates I make:
(1) Bootloop or (2) startup and stuck at HTC One beats audio screen
I have TWRP 2.8.0 installed. I can login to recovery.
Below is the phone getvar info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34SW906267
(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: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
It's an ATT HTC One M7.
Problems, at this moment:
(1) Get get adb to connect to device
(2) I have twrp backups on my computer but don't know how to transfer them onto phone so that I can try restore command - backup files are not in zip format but a folder with files in it.
(3) when I was able to sideload a rom, I did flash ARHD 82.0 but that didn;t help.
PLEASE HELP !!:crying:

st167 said:
Hi,
For no obvious reasons my phone went to bootloop yesterday night and I've been trying to fix it by different methods suggested in forums. But my phone does either of two things after changes/updates I make:
(1) Bootloop or (2) startup and stuck at HTC One beats audio screen
I have TWRP 2.8.0 installed. I can login to recovery.
Below is the phone getvar info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT
(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: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
It's an ATT HTC One M7.
Problems, at this moment:
(1) Get get adb to connect to device
(2) I have twrp backups on my computer but don't know how to transfer them onto phone so that I can try restore command - backup files are not in zip format but a folder with files in it.
(3) when I was able to sideload a rom, I did flash ARHD 82.0 but that didn;t help.
PLEASE HELP !!:crying:
Click to expand...
Click to collapse
To install ARHD you should use TWRP 2.6.3.3 :good:
Or if you want to use your backup you can push it to the phone storage with adb, while in TWRP recovery.
Put the backup folder inside your fastboot folder on your pc and rename it something easy to type "nandroid" for example. Boot the device to TWRP recovery Home Screen. Connect usb cable. Then in the command window type
Code:
adb push nandroid /sdcard/TWRP/BACKUPS/DEVICESERIALNO./nandroid
Replace "DEVICESERIALNO." with your phone's Serial number in capitals
Wait for the push to complete, the command window may appear unresponsive at first just be patient when it's done restore the nandroid with TWRP
P.s you should edit your post and delete your Serial number. You don't want it displayed on the forums. FYI that's the serial number you need to use in the push command.
If you found my posts helpful, no need to say thanks. There's a button for that

Thank you again (already pressed thanks button )...I'll give it a try once I get home.

st167 said:
Thank you again (already pressed thanks button )...I'll give it a try once I get home.
Click to expand...
Click to collapse
Your welcome let me know how it goes, or if you need more help :good:
If you found my posts helpful, no need to say thanks. There's a button for that

So I was able to push backup to TWRP and restore. Yay!
But now the problem is I don't have any cell services....phone identity section shows no imei, no baseband, etc. I can see all these info from fastboot getvar. Any idea?
Oh and I keep getting error saying com.htc.dialer is not responding.

st167 said:
So I was able to push backup to TWRP and restore. Yay!
But now the problem is I don't have any cell services....phone identity section shows no imei, no baseband, etc. I can see all these info from fastboot getvar. Any idea?
Oh and I keep getting error saying com.htc.dialer is not responding.
Click to expand...
Click to collapse
Sorry to tell you that doesn't sound good. Unknown imei and Baseband is normally a hardware failure.
You can try to flash a firmware package or even better if possible an ruu but it rarely solves the issue. It's most likely the Antenna pin connector.
Do you have warranty on the device if so the best option is to return to Stock and send it for repair. :good:
If you found my posts helpful, no need to say thanks. There's a button for that

Danny201281 said:
Sorry to tell you that doesn't sound good. Unknown imei and Baseband is normally a hardware failure.
You can try to flash a firmware package or even better if possible an ruu but it rarely solves the issue. It's most likely the Antenna pin connector.
Do you have warranty on the device if so the best option is to return to Stock and send it for repair. :good:
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
I flashed the att firmware and then flashed rom again. Everything worked fine Phone started normally and I was able to make calls.
But my happiness ended soon...I tried to restart the phone after it finished downloading and updating apps and it died
Now phone doesn't power on, no led indicator or nothing when I plug the charger in. I tried diff combinations of power and vol button but no luck. So now I have an expensive paper-weight :crying:
Phone is out of warranty as it has been more than 365 days since purchase.
But thanks for your help.

WHen my phone did similar behavior I held down power + vol up (It will eventually vibrate and show the white HTC splash screen) THen continued to keep the buttons held down for almost 10 seconds, it rebooted itself again and finally allowed me into HBOOT and from there I was able to choose "Recovery" and boot into TWRP
If that doenst work, try the same with Power + Vol down. Or maybe it was Power + Home + Vol up, or Power + home + Vol down. Sorry, I dont exactly remember but one of those 4 combinations will get you into HBOOT or into recovery so that you can flash a new Rom

st167 said:
I flashed the att firmware and then flashed rom again. Everything worked fine Phone started normally and I was able to make calls.
But my happiness ended soon...I tried to restart the phone after it finished downloading and updating apps and it died
Now phone doesn't power on, no led indicator or nothing when I plug the charger in. I tried diff combinations of power and vol button but no luck. So now I have an expensive paper-weight :crying:
Phone is out of warranty as it has been more than 365 days since purchase.
But thanks for your help.
Click to expand...
Click to collapse
It's also worth checking on your warranty most come with 2years

Related

Revert to 2.47 (Back to stock ROM)

Revert to 2.47
Hi
I have hboot 2.49 want to revert back to 2.47 and plus want to convert it to International version i want to use 407 roms
Details
CID-1111111
HBOOT-2.49.0000
Radio-4T.24.3218.09
OS-2.61.708.1
or can someone provide me latest 2.49 with OS 401
Thanks
Hi
I successfully flashed rom RUU.exe BrightstarUS WWE 1.23.1540.1 (flyhalf's)
and when i got the OTA for 4.4.2 it says my mobile software been modified and cannot update
I used manually to update through fastboot oem rebootRUU
OTA_T6_UL_K44_SENSE55_MR_BrightstarUS_WWE_2.61.1540.1-1.23.1540.1_release
please help me if I did something wrong
Try Change back go stock cid
Sent from my HTC One max using xda premium
I don't really know what is my original CID
HTC___116
something like this not sure
i have seen a list somewhere maybe i will recognize it
EDIT: Actually original software was HK region changed it to WWE US brightstar
I found the CID is HTC__622
i tried to flash it with Brightstar US CID BS_US001
is not working
with original CID HTC__622
is not working
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
I dont know whats wrong,
please help
The Don Jay said:
I found the CID is HTC__622
i tried to flash it with Brightstar US CID BS_US001
is not working
with original CID HTC__622
is not working
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
I dont know whats wrong,
please help
Click to expand...
Click to collapse
Can you check what is your MID ? is it 0P3P50000?
Also can you post the exact error message or a photo?
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.46.0000
(bootloader) version-baseband: 4T.21.3218.01
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.19.708.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA3ASWG05176
(bootloader) imei: 357311050403377
(bootloader) meid: 00000000000000
(bootloader) product: t6ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: 0P3P52000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 4153mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6cad6811
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.121s
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 20.643s
i have succeeded to flash
0P3PIMG_T6_UL_JB43_SENSE55_hTC_Asia_HK_1.19.708.2_Radio_4T.21.3218.01_10.15.1718.01_release_337043_signed_Hboot_2_4
my boot showing 1.19.708.2 but software version is 1.23.1540.1
what is missing what is the right thing to do ?
please help
Hi
I have HTC One max HK Asia Version HTC__622 i tried to flash this rom in CMW, TWP and stock recovery but not taking
with locked and unlocked bootloader
0P3PIMG_T6_UL_JB43_SENSE55_hTC_Asia_HK_1.19.708.2_ Radio_4T.21.3218.01_10.15.1718.01_release_337043_s igned_2_4.zip
tried wiping data, system and dalvik wipe but still giving me an error file is too large
is there anything i did wrong ?
please help im stuck
looking at the picture of you phone diplaying hboot, you cid is 111111111.
try changing back to a good 1
Hi
Problem solved thanks to Chinese website
changed the CID to the original which is HTC__622
Downloaded and copied and renamed the file
0P3PIMG_T6_UL_JB43_SENSE55_hTC_Asia_HK_1.19.708.2_ Radio_4T.21.3218.01_10.15.1718.01_release_337043_s igned_2_4.zip
to
0P3PIMG.zip and located to external SD card
Locked or Relocked the Bootloader .. better locked to get the fingerprint working (this can be done with scotty's method)
got to bootloader mode and press power button to enter bootloader mode then the file will update automatically without any command
Done
source chinese website which i cant post yet
your help
The Don Jay said:
Hi
Problem solved thanks to Chinese website
changed the CID to the original which is HTC__622
Downloaded and copied and renamed the file
0P3PIMG_T6_UL_JB43_SENSE55_hTC_Asia_HK_1.19.708.2_ Radio_4T.21.3218.01_10.15.1718.01_release_337043_s igned_2_4.zip
to
0P3PIMG.zip and located to external SD card
Locked or Relocked the Bootloader .. better locked to get the fingerprint working (this can be done with scotty's method)
got to bootloader mode and press power button to enter bootloader mode then the file will update automatically without any command
Done
source chinese website which i cant post yet
Click to expand...
Click to collapse
I need to revert back my hboot 2.49 to 2.47 . I would appreciate your help on how did your do it
solved too on me
The Don Jay said:
Hi
Problem solved...
Click to expand...
Click to collapse
Thanks!
BadrSaleh said:
I need to revert back my hboot 2.49 to 2.47 . I would appreciate your help on how did your do it
Click to expand...
Click to collapse
you need soff using firewater.
then you can flash any hboot. but be careful to use the correct one!

[RUU] Google Edition Conversion. 4.4.2- 1.16.1700.16 -RUU Zip Non-Rooted & Pre-Rooted

[RUU] Google Edition Conversion. 4.4.2- 1.16.1700.16 -RUU Zip Non-Rooted & Pre-Rooted
This will NOT work on a CDMA HTC One GSM ONLY!
[PSA: People have been reporting not being able to flash back to sense. When investigating this further I found that the system partition on the GPE is about half the size of the sense system partition. (just over a gig compared to like 2.8) This was not the case on the M7
So as of now once you convert, YOU CAN NOT GO BACK TO A SENSE BASED ROM UNTIL A RUU is RELEASED! Rest assured nothing is wrong with the RUU. If you did convert and want to go back you just have to wait for a RUU to be released then you can go back but flashing a sense rom in recovery wont work.
This thread is NOT to support changing your MID, Changing your CID, Rooting or Flashing a custom recovery. If you need to learn how to do any of those do NOT use this thread to post in. Post in the respective dedicated threads to complete these processes. This thread is ONLY to support flashing the RUU. Nothing more, nothing less.
This is NOT a general 4.4.2 discussion thread.
Furthermore, if you need any more detailed instructions than what's stated in this post then you really shouldn't be doing this to your device. If you need a "video" or ask for "step by step" instructions you will NOT get anything more than what's in this post (at least from me). There is no easier way to do this process, there is no easier way to explain it. If you read the post and still don't understand what to do then I advise you to leave your phone alone... Read and then read some more until you understand everything.. WE WILL NOT SPOON FEED YOU IN THIS THREAD!
This procedure is not easy and is not really noob friendly, well flashing the RUU is not really difficult but it's the prerequisites that are more complex/risky. If the instructions aren't clear enough for you or you require further hand holding then I'm sure most of us would advise you stay away from the process.
Also, please do not PM me for support. PM's will not be answered. Post it in the thread. It helps other's having the same issue find a solution. If it's over PM it only benefits you and not everyone else
Prerequisites
S-Off,
ADB knowledge
Fastboot knowledge
Instructions:
First you are going to have to have s-off on your device. Thread for S-off (and support for S-off) http://forum.xda-developers.com/showthread.php?t=2708464
Full Conversion 4.4.2 RUU ZIP containing System, Boot and all Firmware 1.16.1700.16
This will wipe EVERYTHING INCLUDING YOUR INTERNAL SD CARD!!!! PLEASE REMOVE YOUR EXTERNAL CARD IF YOU HAVE ONE so make sure you back up the contents before running this, but you'll end up with a factory-fresh GE. Of course, there's still no support, warranty or responsibility implied or otherwise.
The 4.4.2 RUU Zip supports the following MIDs and CIDs if your MID or CID is not in this list you will have to modify the android-info.txt file in the zip to match your MID/CID
modelid: 0P6B12000
modelid: 0P6B17000
modelid: 0P6B*****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
(please note.. If your model id or cid is not supported you can open up the android-info.txt file that's in the zip and replace one of the model ids or cids listed to match yours.)
Code:
adb reboot bootloader
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip/CODE]
you will the following message:
[CODE]FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Just run the same command again:
Code:
fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16.zip
Code:
fastboot reboot
Stock Non-Rooted 4.4.2-1.16.1700.16 RUU Zip: http://www.androidfilehost.com/?fid=23329332407584639
Mirror:
MD5: eb56e73af883aa2d175032c7dc527dc8
Stock Rooted + busy box pre-installed 4.4.2-1.16.1700.16 RUU Zip: http://www.androidfilehost.com/?fid=23329332407584640
Mirror:
MD5: b380f51a4a2b0e2a83c4d7bd92075ce5
If you want to flash a custom recovery you will have to flash back to stock recovery to get the OTA's
You can get the GPE Stock recovery here
Special thanks to @pasker17 for allowing me to walk him through pulling all the partitions!!
@beaups and crew for S-off
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, or flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. This process is not for the faint of heart so I am not responsible.... It was the other guy... I swear....
reserved
this one too
Worked like a charm the first time thanks! One thing to note is my dot view case works fine with calls the voice gesture down is missing though I'm not missing it. I mention this as some reviews say the gpe edition can't answer calls with the case.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Pre-rooted + busybox RUU added to op
ill probably hold off on fully converting for now but what is the advantage of doing so VS just flashing a GPE rom?
fix-this! said:
ill probably hold off on fully converting for now but what is the advantage of doing so VS just flashing a GPE rom?
Click to expand...
Click to collapse
OTA updates.
Sent from my HTC One_M8 using Tapatalk
BONED
had to change name
Thank you. Confirmed works on Rogers M8. Thank you again. Would be nice if HTC can release the photo edit app on play store in the future.... and maybe the burst mode for the camera
Questions
First off I wanted to say thanks!
But I'm having a few issues getting the IR blaster to work. The app detects it but when I put a camera up to the button I'm not seeing any flashing.
Also how to we use the HTC photo edit?
Thanks again!
lordpelvis said:
First off I wanted to say thanks!
But I'm having a few issues getting the IR blaster to work. The app detects it but when I put a camera up to the button I'm not seeing any flashing.
Also how to we use the HTC photo edit?
Thanks again!
Click to expand...
Click to collapse
What IR app are you using? I'm using Smart Remote and it is working perfectly. As for the camera, sorry, but we lost pretty much all functionality with the GPe camera.
I've tried power IR and a few others. Have a link to the remote you're using?
Sent from my HTC One_M8 using xda app-developers app
---------- Post added at 11:01 AM ---------- Previous post was at 10:54 AM ----------
I actually bought the app and nothing happens.
Sent from my HTC One_M8 using xda app-developers app
You can download the HTC TV app from the playstore.. Again.. To remind you guys.. That type of discussion is off topic and does not belong in the thread.
Sent from my HTC One_M8 using Tapatalk
I did want to mention that when trying to flash the RUU, I did get a second "error" after the listed first one. I've attached the code from ADB below.
Code:
Daniels-iMac:~ Daniel$ fastboot flash zip /Users/Daniel/Downloads/RUU-HTC_One_M8_GE-1.16.1700.16.zip
target reported max download size of 1830715392 bytes
sending 'zip' (510598 KB)...
OKAY [ 20.133s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=9
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,76
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) current_image_number=0
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,6
(bootloader) [RUU]UZ,adsp,13
(bootloader) [RUU]UZ,adsp,21
(bootloader) [RUU]UZ,adsp,27
(bootloader) [RUU]UZ,adsp,34
(bootloader) [RUU]UZ,adsp,41
(bootloader) [RUU]UZ,adsp,48
(bootloader) [RUU]UZ,adsp,54
(bootloader) [RUU]UZ,adsp,61
(bootloader) [RUU]UZ,adsp,68
(bootloader) [RUU]UZ,adsp,74
(bootloader) [RUU]UZ,adsp,81
(bootloader) [RUU]UZ,adsp,88
(bootloader) [RUU]UZ,adsp,94
(bootloader) [RUU]UZ,adsp,99
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,26
(bootloader) [RUU]WP,adsp,53
(bootloader) [RUU]WP,adsp,79
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) current_image_number=1
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,6
(bootloader) [RUU]UZ,boot,12
(bootloader) [RUU]UZ,boot,18
(bootloader) [RUU]UZ,boot,25
(bootloader) [RUU]UZ,boot,33
(bootloader) [RUU]UZ,boot,43
(bootloader) [RUU]UZ,boot,55
(bootloader) [RUU]UZ,boot,62
(bootloader) [RUU]UZ,boot,68
(bootloader) [RUU]UZ,boot,74
(bootloader) [RUU]UZ,boot,80
(bootloader) [RUU]UZ,boot,87
(bootloader) [RUU]UZ,boot,93
(bootloader) [RUU]UZ,boot,99
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) current_image_number=2
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,8
(bootloader) [RUU]UZ,recovery,16
(bootloader) [RUU]UZ,recovery,22
(bootloader) [RUU]UZ,recovery,29
(bootloader) [RUU]UZ,recovery,37
(bootloader) [RUU]UZ,recovery,45
(bootloader) [RUU]UZ,recovery,51
(bootloader) [RUU]UZ,recovery,60
(bootloader) [RUU]UZ,recovery,68
(bootloader) [RUU]UZ,recovery,76
(bootloader) [RUU]UZ,recovery,85
(bootloader) [RUU]UZ,recovery,93
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,66
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) current_image_number=3
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) current_image_number=4
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,20
(bootloader) [RUU]UZ,sp1,41
(bootloader) [RUU]UZ,sp1,77
(bootloader) [RUU]UZ,sp1,97
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
(bootloader) ...... Successful
(bootloader) current_image_number=5
(bootloader) start image[system] unzipping & flushing...
(bootloader) [RUU]UZ,system,0
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 40.913s
For those who may think something is wrong, it may not be the case. Although I received the error above, my phone continued to go through the process of flashing the RUU. I was patient and let it finish. The last step running the "fastboot reboot" command will not work as I was at a black screen that looked like fastboot except I had none of the usual fastboot options (hboot, etc.), just the listing of the hardware info (model, CID, etc.). I held the power button for several seconds until the phone shut off completely. Turned it back on and it booted up fine. Ran through the setup process and everything seems to be working fine. I will update if my phone explodes or anything else I notice is wrong, but otherwise it's been great so far. Thanks graffixnyc!
Thanks for this. I did this and want to know what app do you recommend for visual voicemail? The original app was great. Anyway I can download the one that came with the phone? Thanks
xoulu said:
Thanks for this. I did this and want to know what app do you recommend for visual voicemail? The original app was great. Anyway I can download the one that came with the phone? Thanks
Click to expand...
Click to collapse
Use Google voice for vvm. It will even text you a transcription of the phone message.
Sent from my HTC One_M8 using Tapatalk
Hey guys, I'm going to close this thread and ask you guys that you use the main thread in the m8 section (the RUU is the same) It's just easier for me to maintain one thread instead of 3 so head on over to the main thread: http://forum.xda-developers.com/showthread.php?t=2708589

HTC Rhyme s510b correct RUU

Hey guys,i hope someone can help me fix my fone..
I need to get RUU for my fone type.
I tried all RUU who are posted in htcdev.com - noone works.
***UNLOCKED***
BLISS PVT SHIP S-ON RL
HBOOT - 1.33.0000
RADIO - 3831.17.00.17_M
eMMC - boot
Apr 13 2012,10:10:20
Why don't you let us know what problems you are having, what region the Rhyme is from (Europe, Asia,...?), what RUUs you've tried exactly, and what part of the RUU is not working (error codes)?
The more info you give the better we can help.
es0tericcha0s said:
Why don't you let us know what problems you are having, what region the Rhyme is from (Europe, Asia,...?), what RUUs you've tried exactly, and what part of the RUU is not working (error codes)?
The more info you give the better we can help.
Click to expand...
Click to collapse
The problem is he stuck on switching on,
I have tryed the orginal RUU`s from htcdev.com ,but noone works.
I thing this rhyme is from Asia,becouse it have only 2 languages - Chaineese and English.
RUU ERROR - ERROR [155]: UNKNOWN ERROR
The ROM Update Utility cannot update your android phone.
Please get the corrent ROM Update Utility and try again.
Have you relocked the bootloader before running the RUU?
fastboot oem lock
I believe.
es0tericcha0s said:
Have you relocked the bootloader before running the RUU?
fastboot oem lock
I believe.
Click to expand...
Click to collapse
But to do this ,i need to enable USB Debugging ,but i cannt.
Is any automatic debugging for Rhyme?
That is not correct. You need to relock the bootloader while in the bootloader/fastboot mode so adb doesn't work there anyway.
es0tericcha0s said:
That is not correct. You need to relock the bootloader while in the bootloader/fastboot mode so adb doesn't work there anyway.
Click to expand...
Click to collapse
*** RELOCKED ***
BLISS PVT SHIP S-ON RL
HBOOT- 1.33.0000
RADIO- 3831.17.00.17_M
eMMC-boot
Apr 13 2012,10:10:20
I have RELOCKED it,but still cannt do anithing with RUU
Now is error 131
Error 131 should be because you are trying to use an HTC Rhyme RUU that is for a different region. If you don't have fastboot set up, you should (get it here: http://forum.xda-developers.com/showthread.php?t=2317790). Once you have that set up, open a CMD prompt and change directories to the folder where your fastboot files are then boot to the bootloader again and plug it in. Then do this:
fastboot devices
(this should pull up a string of letters+numbers, if it does not, you are either in the wrong folder or drivers are not correct)
if you get something with fastboot devices then do this:
fastboot getvar all
and post that here. This will give us ALL the details about what is on the phone and where it is from, etc.
Also, post up the version you are trying, for a reference point.
es0tericcha0s said:
Error 131 should be because you are trying to use an HTC Rhyme RUU that is for a different region. If you don't have fastboot set up, you should (get it here: http://forum.xda-developers.com/showthread.php?t=2317790). Once you have that set up, open a CMD prompt and change directories to the folder where your fastboot files are then boot to the bootloader again and plug it in. Then do this:
fastboot devices
(this should pull up a string of letters+numbers, if it does not, you are either in the wrong folder or drivers are not correct)
if you get something with fastboot devices then do this:
fastboot getvar all
and post that here. This will give us ALL the details about what is on the phone and where it is from, etc.
Also, post up the version you are trying, for a reference point.
Click to expand...
Click to collapse
This is what i got.
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.33.0000
(bootloader) version-baseband: 3831.17.00.17_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.708.3
(bootloader) serialno: SH34CVV00951
(bootloader) imei: 358071047342786
(bootloader) product: bliss
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PI4610000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 456a753a
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
How to know ,whatregion it is?
Mby u can now recommend some RUU?
Try this one:
http://dl4.htc.com/RomCode/Source_and_Binaries/bliss-ics-crc-3.0.16-5423ef1.zip

[Q] Soft Brick -- Help me fix this the easy way please!

S-Off
Unlocked bootloader
Had HD Rev 62 on it, but wiped EVERYTHING (data, cache, etc etc) in TWRP
Updated TWRP to 2.8.
Fastboot working, adb is not.
Fastboot sees and communicated with device just fine.
ADB does not list any devices, or errors. Just returns blank beneath List of connected Devices.
Cannot boot into anything since no OS is present. HD Rev latest version gets errors about "android-info.txt" and android-product.txt.
"error: update package has no android info.txt or android product.txt"
I don't care what OS is loaded on it because I am sending it to my mother. What is the fastest way to get it up and running again? I'm hoping to ignore fixing the ADB drivers on my Windows 8.1 machine (64-bit).
Can I just do a fastboot quick fix? If so, which RUU/Rom/Firmware/whatever. Anything that fastboot update update.zip will fix.
Thanks guys!
nik.the said:
S-Off
Unlocked bootloader
Had HD Rev 62 on it, but wiped EVERYTHING (data, cache, etc etc) in TWRP
Updated TWRP to 2.8.
Fastboot working, adb is not.
Fastboot sees and communicated with device just fine.
ADB does not list any devices, or errors. Just returns blank beneath List of connected Devices.
Cannot boot into anything since no OS is present. HD Rev latest version gets errors about "android-info.txt" and android-product.txt.
"error: update package has no android info.txt or android product.txt"
I don't care what OS is loaded on it because I am sending it to my mother. What is the fastest way to get it up and running again? I'm hoping to ignore fixing the ADB drivers on my Windows 8.1 machine (64-bit).
Can I just do a fastboot quick fix? If so, which RUU/Rom/Firmware/whatever. Anything that fastboot update update.zip will fix.
Thanks guys!
Click to expand...
Click to collapse
Post a fastboot getvar all (except for imei and serialno). If you are in bootloader/FASTBOOT USB and run the command adb devices it will not work. ADB works in OS if USB Debugging is enabled or in recovery.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34CW907053
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXX
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks @majmoz!
nik.the said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: removed
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXX
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: 11111111 change to T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks @majmoz!
Click to expand...
Click to collapse
This is the latest RUU 6.10.531.9 it will put you back at stock. Prior to running this, I would change the CID back to T-MOB010, I have had issues running TMO RUUs with SuperCID.
majmoz said:
This is the latest RUU 6.10.531.9 it will put you back at stock. Prior to running this, I would change the CID back to T-MOB010, I have had issues running TMO RUUs with SuperCID.
Click to expand...
Click to collapse
Which commands would I use to get this running? From bootloader/fastboot usb? Thanks again for the help @majmoz
nik.the said:
Which commands would I use to get this running? From bootloader/fastboot usb? Thanks again for the help @majmoz
Click to expand...
Click to collapse
Just follow the instructions in the Post. RUU.exe are run from Windows. Place the downloaded file in your fastboot/adb folder and double click it. Follow the on-screen instructions.
majmoz said:
Just follow the instructions in the Post. RUU.exe are run from Windows. Place the downloaded file in your fastboot/adb folder and double click it. Follow the on-screen instructions.
Click to expand...
Click to collapse
Nothing happens when I run the ruu. I get through to the agreement, accept, and then it disappears. Also, in the Sync manager, it's not showing my phone. I'm guessing this is a windows 8.1 problem?
nik.the said:
Nothing happens when I run the ruu. I get through to the agreement, accept, and then it disappears. Also, in the Sync manager, it's not showing my phone. I'm guessing this is a windows 8.1 problem?
Click to expand...
Click to collapse
Give this procedure a try!
Change USB ports (USB 2 is preferred) and cables if available
Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
Make sure you leave the adb and fastboot that you downloaded.
Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
A pop-up asking to install HTC Sync will appear, just ignore it or cancel it.
Make sure you set Fast Boot OFF in the Settings < Power on your phone, and USB Debugging enabled
Leave your phone ON and run the RUU set up.
I'm trying these things, but will it work on a phone that can't get to desktop? My phone isn't able to boot into android. It only can get into bootloader, recovery, and fastboot.
nik.the said:
I'm trying these things, but will it work on a phone that can't get to desktop? My phone isn't able to boot into android. It only can get into bootloader, recovery, and fastboot.
Click to expand...
Click to collapse
Put the phone in bootloader/FASTBOOT USB, then run the RUU.
majmoz said:
Give this procedure a try!
Change USB ports (USB 2 is preferred) and cables if available
Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
Make sure you leave the adb and fastboot that you downloaded.
Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
A pop-up asking to install HTC Sync will appear, just ignore it or cancel it.
Make sure you set Fast Boot OFF in the Settings < Power on your phone, and USB Debugging enabled
Leave your phone ON and run the RUU set up.
Click to expand...
Click to collapse
Hmm, frozen at 5% Checking header. RUU problem?
nik.the said:
Hmm, frozen at 5% Checking header. RUU problem?
Click to expand...
Click to collapse
Let's attack this differently. Let's flash the firmware 5.14.531.1 in fastboot. After it is finished, then run the RUU.
Download firmware, rename to fimware.zip and place in your fastboot folder.
Then put phone in bootloader/FASTBOOT USB then, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
majmoz said:
Let's attack this differently. Let's flash the firmware 5.14.531.1 in fastboot. After it is finished, then run the RUU.
Click to expand...
Click to collapse
It worked, then it restarted into QHSUSB_DLOAD. Hard bricked.
Any suggestions?
EDIT: Apparently Dexter's method can fix this, but I need the "appropriate" packages whatever those are :\.
nik.the said:
It worked, then it restarted into QHSUSB_DLOAD. Hard bricked.
Any suggestions?
EDIT: Apparently Dexter's method can fix this, but I need the "appropriate" packages whatever those are :\.
Click to expand...
Click to collapse
Here is his post and if you scroll down to Post #3 you will find the download.

[Q] Unable to install ROM

I have AT& T HTC One M7 (unlocked is displayed in HBOOT). It had crashed once before but I was able to get it back up and running using this thread: http://forum.xda-developers.com/htc-one/help/bricked-htc-one-m7-attempting-to-t2856447
But now it has crashed/bricked again and even after following the same steps, I am unable to get it up and running. Two new things I see is even if I select install recovery during installation, it goes back to twrp and looks like twrp is never able to install root access on this device. Specifics of my device are below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.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: 4130mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any thoughts what could be wrong. I even tried wiping out cache, delvik cache, data, system from twrp but no luck. Also, I have copy of HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip but not sure how I can restore this and if it will help.
cagashe said:
I have AT& T HTC One M7 (unlocked is displayed in HBOOT). It had crashed once before but I was able to get it back up and running using this thread: http://forum.xda-developers.com/htc-one/help/bricked-htc-one-m7-attempting-to-t2856447
But now it has crashed/bricked again and even after following the same steps, I am unable to get it up and running. Two new things I see is even if I select install recovery during installation, it goes back to twrp and looks like twrp is never able to install root access on this device. Specifics of my device are below:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.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: 4130mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any thoughts what could be wrong. I even tried wiping out cache, delvik cache, data, system from twrp but no luck. Also, I have copy of HTCOne-32GB-ATT-5.12.502.2-TWRP-stock-unrooted.zip but not sure how I can restore this and if it will help.
Click to expand...
Click to collapse
Download the stock 5.12.502.2 recovery and place in your adb/fastboot folder.
Boot into bootloader/FASTBOOT USB:
Code:
fastboot flash recovery 5.12.502.2.recovery.img
fastboot erase cache
fastboot reboot-bootloader
Boot into Recovery and perform a factory reset
Reboot back to bootloader
Flash TWRP 2.6.3.3
I would stick with the Guru Reset it can be done in TWRP. If the stock Recovery does not do the trick, then you could try the stock firmware. You will have to relock your bootloader before you can flash it.
Well.. I am clueless now
majmoz said:
Download the stock 5.12.502.2 recovery and place in your adb/fastboot folder.
Boot into bootloader/FASTBOOT USB:
Code:
fastboot flash recovery 5.12.502.2.recovery.img
fastboot erase cache
fastboot reboot-bootloader
Boot into Recovery and perform a factory reset
Reboot back to bootloader
Flash TWRP 2.6.3.3
I would stick with the Guru Reset it can be done in TWRP. If the stock Recovery does not do the trick, then you could try the stock firmware. You will have to relock your bootloader before you can flash it.
Click to expand...
Click to collapse
Well.. I am clueless now... I tried all the above steps you provided and and used Guru Reset along with firmware. Also, I tried ViperOne 6.2 with no luck.
To be precise the issue now I am running into is no matter what I tried all installations show up as successful but then on reboot phone gets in bootloop (it comes up fine until HTC beatsaudio screen and reboots again). Any thoughts/ideas?
cagashe said:
Well.. I am clueless now... I tried all the above steps you provided and and used Guru Reset along with firmware. Also, I tried ViperOne 6.2 with no luck.
To be precise the issue now I am running into is no matter what I tried all installations show up as successful but then on reboot phone gets in bootloop (it comes up fine until HTC beatsaudio screen and reboots again). Any thoughts/ideas?
Click to expand...
Click to collapse
After you ran the stock firmware or Guru Reset did you try to boot into system? If you didn't then you need to see if that fixed your issue. It might be ViperOne causing the issue with a bad boot.img. You can check the firmware to see if it has a boot.img in the zip. Just open the zip and look to see if there is a boot.img.
majmoz said:
After you ran the stock firmware or Guru Reset did you try to boot into system? If you didn't then you need to see if that fixed your issue. It might be ViperOne causing the issue with a bad boot.img. You can check the firmware to see if it has a boot.img in the zip. Just open the zip and look to see if there is a boot.img.
Click to expand...
Click to collapse
Yes.. I do see the boot. img in the Guru Reset; however, for some reason I am unable to open the firmware zip. I guess I am going to try flashing guru reset without firmware. Another question I had was about "You will have to relock your bootloader before you can flash it." I am trying to flash it leaving bootloader unlocked. Could that be the problem. If yes, can you please please give me the exact sequence I need to follow before flash and after copying Guru Reset to device. (I am using adb push for the same).
cagashe said:
Yes.. I do see the boot. img in the Guru Reset; however, for some reason I am unable to open the firmware zip. I guess I am going to try flashing guru reset without firmware. Another question I had was about "You will have to relock your bootloader before you can flash it." I am trying to flash it leaving bootloader unlocked. Could that be the problem. If yes, can you please please give me the exact sequence I need to follow before flash and after copying Guru Reset to device. (I am using adb push for the same).
Click to expand...
Click to collapse
If you are flashing the firmware, then you have to lock your bootloader since you are S-ON. Here is how you would flash the firmware.
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
fastboot oem lock
Then, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
You will have to unlock your bootloader before you push Guru Reset to your phone. If you have your old Unlock_code.bin you might try it first, if it fails use the whole procedure:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Still no luck
majmoz said:
If you are flashing the firmware, then you have to lock your bootloader since you are S-ON. Here is how you would flash the firmware.
You will have to unlock your bootloader before you push Guru Reset to your phone. If you have your old Unlock_code.bin you might try it first, if it fails use the whole procedure:
​
Click to expand...
Click to collapse
I tried all the steps and see a little progress.. now my phone keeps rebooting on HTC beatsaudio screen. The sequence I followed was as below:
1. Unlocked the device with unlock bin from HTCdev and rebooted in bootloader (Shows as unlocked and tampered).
2. Pushed TWRP and Guru_Reset_M7_5.12.502.2_clsA
3. Installed Guru_Reset_M7_5.12.502.2_clsA using install from TWRP.
4. Checked if the phone is up and running on reboot --> No luck (rebooting on HTC beatsaudio screen)
5. Rebooted phone again in bootloader.
6. Locked the device (fastboot oem lock) . At this step got an error on last line "too many links"
7. fastboot oem rebootRUU (got the silver screen)
8. fastboot flash zip firmware.zip (twice) waited for about a minute after getting confirmation in command prompt.
9. fastboot reboot
I believe I am not doing anything wrong. It is really frustrating now since everyone is sending me birthday wishes today on phone and I am unable to see any :crying:
cagashe said:
I tried all the steps and see a little progress.. now my phone keeps rebooting on HTC beatsaudio screen. The sequence I followed was as below:
1. Unlocked the device with unlock bin from HTCdev and rebooted in bootloader (Shows as unlocked and tampered).
2. Pushed TWRP and Guru_Reset_M7_5.12.502.2_clsA
3. Installed Guru_Reset_M7_5.12.502.2_clsA using install from TWRP.
4. Checked if the phone is up and running on reboot --> No luck (rebooting on HTC beatsaudio screen)
5. Rebooted phone again in bootloader.
6. Locked the device (fastboot oem lock) . At this step got an error on last line "too many links"
7. fastboot oem rebootRUU (got the silver screen)
8. fastboot flash zip firmware.zip (twice) waited for about a minute after getting confirmation in command prompt.
9. fastboot reboot
I believe I am not doing anything wrong. It is really frustrating now since everyone is sending me birthday wishes today on phone and I am unable to see any :crying:
Click to expand...
Click to collapse
Since the last thing you flashed was the stock firmware, boot into Stock Recovery and do a factory reset then reboot back to bootloader. Install TWRP and if the Guru Reset is still on your phone then flash it. If not, then push it to your phone like before. Hopefully, the factory reset in Recovery will clean out any outstanding issues.
Moved on to M8.. but still like to fix m7
Unfortunately none of the above steps worked hence I decided to move on with M8. However now that I have a working phone (M8) I am open to experiment with my M7.
Yesterday I tried restoring M7 nandroid backup from HTC guru and had some luck. But I guess I downloaded an older version of nandroid backup. So two questions:
1. Can anyone point me to correct version of nandroid backup that I can restore. (Phone is unlocked, S-On and not rooted. If I need to root it then I will need some guidance).
2. Any other method you guys can suggest to get the phone up and running again.
Below are getvar details.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.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: 4130mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
cagashe said:
Unfortunately none of the above steps worked hence I decided to move on with M8. However now that I have a working phone (M8) I am open to experiment with my M7.
Yesterday I tried restoring M7 nandroid backup from HTC guru and had some luck. But I guess I downloaded an older version of nandroid backup. So two questions:
1. Can anyone point me to correct version of nandroid backup that I can restore. (Phone is unlocked, S-On and not rooted. If I need to root it then I will need some guidance).
2. Any other method you guys can suggest to get the phone up and running again.
Below are getvar details.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.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: 4130mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
The nandroid backup is in the same post as the Guru Reset
http://forum.xda-developers.com/showthread.php?t=2775650
clsA said:
The nandroid backup is in the same post as the Guru Reset
http://forum.xda-developers.com/showthread.php?t=2775650
Click to expand...
Click to collapse
Thanks @clsA.. I have downloaded and copied the nandroid to device as mentioned in the post. Just one more question before I restore.. do I need to modify anything in the recovery. txt or I can simply restore it as-is
cagashe said:
Thanks @clsA.. I have downloaded and copied the nandroid to device as mentioned in the post. Just one more question before I restore.. do I need to modify anything in the recovery. txt or I can simply restore it as-is
Click to expand...
Click to collapse
it's fine as is
sometime a factory reset is needed after the restore is complete
clsA said:
it's fine as is
sometime a factory reset is needed after the restore is complete
Click to expand...
Click to collapse
@clsA.. I was able to restore the backup and saw the home screen. However after that it went to bootloop. I tried factory reset as you mentioned but no luck. Any thoughts? I am thinking of updating firmware?
cagashe said:
@clsA.. I was able to restore the backup and saw the home screen. However after that it went to bootloop. I tried factory reset as you mentioned but no luck. Any thoughts? I am thinking of updating firmware?
Click to expand...
Click to collapse
firmware is not going to help you have already done that
go into TWRP and wipe / format data ..type yes
push this rom to your phone and try it
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_81.0.zip
clsA said:
firmware is not going to help you have already done that
go into TWRP and wipe / format data ..type yes
push this rom to your phone and try it
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_81.0.zip
Click to expand...
Click to collapse
@clsA.. tried installing new rom you mentioned but no luck and it's back to bootloop from HTC screen. I am now thinking to restore your nandroid backup and look into build.prop. In one of the readings I came across this command which I believe is for getting usb debugging enabled.
write /sys/class/android_usb/android0/enable 1
start adbd
I am thinking to boot in twrp and run above command in adb shell. If successful then I think I can try rumrunner or firewater to s-off the phone... Totally frustrated now.. I have no idea why nothing is working on this phone.
USB Debugging ON now
clsA said:
firmware is not going to help you have already done that
go into TWRP and wipe / format data ..type yes
push this rom to your phone and try it
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_81.0.zip
Click to expand...
Click to collapse
@clsA... after some more research I found a way to enable USB debugging so steps I followed were:
1. Restored nandroid backup you mentioned in above post.
2. Modified build.prop and default.prop from PC and pushed them back in /system and / respectively.
3. I can now see usb debugging enabled in the home screen.
Only issue I am facing now is even after factory reset phone goes in bootloop from home screen (home screen always remains locked). Any thoughts?
If I somehow get S-Off by rumrunner or firewater would I have more options?

Categories

Resources