Database Develop

[q] one m7 without o.s

Have HTC ONE M7 without Operative Sistem, try flash with many RUU exe example 3.22.1540.1 or 4.20.1020.12 but saysme error 155" error update image "
- Try change to super cid with fastboot but only allowme read the cid : HTC __044
- Try to change to S-OFF with rumruner, but the program ask me for phone in normal mode
- Already the phone status is :
TAMPERED
UNLOCKED
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO- 4A.17.3250.14
oPENdsp -V31.120.274.0617
os-2.24.707.1
CID HTC__044
Also when enter to Recovery show:
Team Win Recovery Project v2.6.01
No OS Installed
Somebody know how fix this? i can donate for the help, please not saysme : write in the right section and not helpme i am beginner with htc.
thanks

You are trying to flash the wrong ruu's
First you need to know how to use fastboot and adb, plenty of guides about for that.
Then you need to flash twrp recovery 2.6.3.3
Then you need to push the below zip to your internal sd card and flash it
http://www.htc1guru.com/dld/guru_reset_m7_2-24-707-1-zip/

You need adb sideload or USB otg cable
from HTC One

[Q] How to go from HBOOT 1.57 to HBOOT 1.44 in order to install Stock RUU

I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4M.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: XXXXXX
imei: XXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4333mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-1f512bb6
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!

consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified. Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2485651 here is a list of firmware
You can downgrade your hboot and then run the RUU. Make sure it's a stock hboot and NOT a modified one (it'll say either or). You can open the firmeware zips (not extract) and open and edit the android.info text file and add in your CID and model id as required if necessary
You can then flash the RUU as normal after. No need to step down hboots

consequense said:
I have an AT&T HTC One (m7). I would like to ultimately get this back to HTC's stock version with the ability to receive OTA updates and behave just like it would if it were never modified.
Several guides, post, and pages say that the only way I can successfully use an AT&T RUU file is accomplishing S-OFF since they will all contain older firmware (HBOOTS) than my current 1.57 version (I've seen some who LOCK the bootloader after achieve S-OFF and others who don't). If anyone can definitively tell me if it matters rather bootloader is still locked after achieve S-OFF, that would be appreciated.
XDA and HTC Guru indicate to successfully run an RUU I need to downgrade my HBOOT from 1.57 to HBOOT 1.44. While downgrading, can I go from 1.57 and directly install a 1.44 firmware or do I have to step down one at a time 1.57-->1.54-->1.x -> 1.44? Also, if anyone has a collection of firmware I can use to do this, that would be awesome too.
The RUU i'm trying to ultimately put on my phone is RUU_M7_UL_JB_50_Cingular_US_1.26.502.15_Radio_4A.17.3250.20_10.40.1150.04_release_326691_signed_2 from AndroidRUU (new , so can't embed the link)
After all my fiddling, this is the output of my getvar all:
If anyone has a suggestion on how to accomplish stock ROM back on my HTC m7 with my setup, I'd greatly appreciate it. Thank you!
Click to expand...
Click to collapse
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this 4.18.502.7 decrypted ROM. and the instructions are from clsA:
Copy your downloaded file to your fastboot / adb folder
Rename the file Rom.zip
open a command prompt in the same folder (shift + right click - command prompt here )
adb reboot-bootloader
fastboot commands:
fastboot oem rebootRUU
wait for the Silver HTC logo
fastboot flash zip Rom.zip
the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip Rom.zip
most times the green status bar does not reach the 100% mark. So when the output in the command window is complete, you can reboot:
fastboot reboot
Click to expand...
Click to collapse
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.

Decrypted ROM Failed
majmoz said:
Since you are S-OFF, you don't have to go all the way back to JB, you can flash this and the instructions are from clsA:
This should put you back at stock. You do not need to lock your bootloader since you are S-OFF.
Click to expand...
Click to collapse
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?

consequense said:
@majmoz I tried to flash the ROM you pointed me to, but it failed. It just said error updating <ROM Name> Updating partition details...
I am still on HBOOT 1.57, if I understood your previous comment, running this ROM would not require me to update the firmware first. Did I mis-understand that?
Click to expand...
Click to collapse
you can try it again but flash this firmware first and it should work.
http://d-h.st/a1w
You could also use the full RUU after flashing the above firmware. http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe

[Q] HTC One M7 BOOTLOADER SAYS LOCKED

HELP NEEDED
My HTC one m7 is stuck at locked bootloader...no matter what I do it remains locked....the rom is the stock 4.1 jb...it is s-ON...so far I have tried this:
Tried unlocking from HTC DEV
Tried Towelroot
when I unlock using htc dev the splash screen appears...after pressing yes, it reboots and resets everything but no unlocked bootloader....towelroot also doesn't work....
adb also not working...
previously it was s-OFF and I had installed viperONE....

Faisal0000 said:
HELP NEEDED
My HTC one m7 is stuck at locked bootloader...no matter what I do it remains locked....the rom is the stock 4.1 jb...it is s-ON...so far I have tried this:
Tried unlocking from HTC DEV
Tried Towelroot
when I unlock using htc dev the splash screen appears...after pressing yes, it reboots and resets everything but no unlocked bootloader....towelroot also doesn't work....
adb also not working...
previously it was s-OFF and I had installed viperONE....
Click to expand...
Click to collapse
Is USB Debugging enabled?
Is Fast boot in Power disabled?

Faisal0000 said:
HELP NEEDED
My HTC one m7 is stuck at locked bootloader...no matter what I do it remains locked....the rom is the stock 4.1 jb...it is s-ON...so far I have tried this:
Tried unlocking from HTC DEV
Tried Towelroot
when I unlock using htc dev the splash screen appears...after pressing yes, it reboots and resets everything but no unlocked bootloader....towelroot also doesn't work....
adb also not working...
previously it was s-OFF and I had installed viperONE....
Click to expand...
Click to collapse
was the device converted to GPE at any point when it was s-off. Or is it GPE originally?
Have you tried
Code:
fastboot oem unlock
Also the output from
Code:
fastboot getvar all
would be helpful, please edit out your serial and imei before posting :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

majmoz said:
Is USB Debugging enabled?
Is Fast boot in Power disabled?
Click to expand...
Click to collapse
yes usb debugging is enabled...and fastboot is disabled...

Danny201281 said:
was the device converted to GPE at any point when it was s-off. Or is it GPE originally?
Have you tried
Code:
fastboot oem unlock
Also the output from
Code:
fastboot getvar all
would be helpful, please edit out your serial and imei before posting :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
the device was originally sense...it wasn't converted to gpe...
fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3773mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

fastboot oem unlock doesnt work...

Faisal0000 said:
fastboot oem unlock doesnt work...
Click to expand...
Click to collapse
Ok I notice you have a very new radio compared to you hboot version. This unlocking problem normally happens when an s-off device is set back to s-on while something is still customized in the firmware. Could be anything even as little as a custom boot splash. Normally happens after botched gpe conversion. That's why I asked about that
What reason did you go back to s-on. Is it possible you had custom firmware at the time?
I only know of one case where the bootloader was ever unlocked again and they had to use Sunshine app. Which unlocked the bootloader and returned s-off. Obviously this is a good option If the phone is booting.
Although normally the device has been on the latest firmware with no ruu available. Not the case for your device, you could try flashing the 3.62.401.1.zip firmware from here.
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/ with below instructions.
Rename the 3.62.401.1.zip to firmware.zip and put it in your fastboot folder.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
Code:
fastboot oem lock
you can skip this if already locked
Code:
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
< --- case sensitive.
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Make sure fastboot usb is connected and run the ruu.exe on your pc
http://www.htc1guru.com/2014/03/android-ruu-europe/ This will return you to complete stock 4.19.401.9. After which you should get a new unlock code from HTC dev and try unlock again.
Good luck :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Ok I notice you have a very new radio compared to you hboot version. This unlocking problem normally happens when an s-off device is set back to s-on while something is still customized in the firmware. Could be anything even as little as a custom boot splash. Normally happens after botched gpe conversion. That's why I asked about that
What reason did you go back to s-on. Is it possible you had custom firmware at the time?
I only know of one case where the bootloader was ever unlocked again and they had to use Sunshine app. Which unlocked the bootloader and returned s-off. Obviously this is a good option If the phone is booting.
Although normally the device has been on the latest firmware with no ruu available. Not the case for your device, you could try flashing the 3.62.401.1.zip firmware from here.
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
Then flash this ruu. http://www.htc1guru.com/2014/03/android-ruu-europe/ This will return you to complete stock 4.19.401.9. After which you should get a new unlock code from HTC dev and try unlock again.
Good luck :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
First of all thanks...
P.S the bootloader is locked and I cant flash the RUU...
neither do I have a custom recovery and root...so i cant install a guru reset...
the phone is booting and working fine but no root...
if I get root by towelroot I could use flashify to flash recovery without unlocking the bootloader and then restore it to stock...but the problem is that tr is not working...tried all versions...it worked before...
I did it s-ON to return it to stock so I could sale it...I was using viperone with elemental X kernel...I foolishly cleared everything also the system and... didnt notice...after that I flashed the stock recovery and gave the command for s-ON and then locked the bootloader...but the phone didnt boot...I didint knew what happened so I sent it for repair in a local shop...I dont know what they did but when I got it back it was LOCKED not RELOCKED....I dont what RUU did they flash because whenever I insert a sim card it says network locked...it happens with every sim card and whatever code I insert it says succesfully unlocked from network and rebooting...but still remains network locked...I was trying to unlock bootloader to flash the correct RUU to get the phone back in order but to no avail...now I've checked every local shop but they're out of options....so XDA is my only hope now....

Faisal0000 said:
First of all thanks...
P.S the bootloader is locked and I cant flash the RUU...
neither do I have a custom recovery and root...so i cant install a guru reset...
the phone is booting and working fine but no root...
if I get root by towelroot I could use flashify to flash recovery without unlocking the bootloader and then restore it to stock...but the problem is that tr is not working...tried all versions...it worked before...
I did it s-ON to return it to stock so I could sale it...I was using viperone with elemental X kernel...I foolishly cleared everything also the system and... didnt notice...after that I flashed the stock recovery and gave the command for s-ON and then locked the bootloader...but the phone didnt boot...I didint knew what happened so I sent it for repair in a local shop...I dont know what they did but when I got it back it was LOCKED not RELOCKED....I dont what RUU did they flash because whenever I insert a sim card it says network locked...it happens with every sim card and whatever code I insert it says succesfully unlocked from network and rebooting...but still remains network locked...I was trying to unlock bootloader to flash the correct RUU to get the phone back in order but to no avail...now I've checked every local shop but they're out of options....so XDA is my only hope now....
Click to expand...
Click to collapse
If the phone is s-on the bootloader must be LOCKED or RELOCKED to run an ruu or flash firmware
you can only flash Unlocked while s-off. So it should work. If it fails post the error :good:
I've edited my previous post to include instructions for flashing
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
If the phone is s-on the bootloader must be LOCKED or RELOCKED to run an ruu or flash firmware
you can only flash Unlocked while s-off. So it should work. If it fails post the error :good:
I've edited my previous post to include instructions for flashing
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Thanks a lot man....but it was showing some error and so I got a new htc one, this thread is useless now so if anyone can delete it plz delete it...
Sent from my HTC One using XDA Free mobile app

[Q] Htc M7 Soft Bricked Need Advice

Hi guys,
I have gone through the the forum and have read up on the issure, I have made some progress, I need some expert advice on the last few stages.
The Htc one M7 is soft bricked, i have unlocked the bootloder via the htc site, i know how to use ADB and fastboot command line. I have installed TWRP on the phone, now i can see my phone as a drive on my computer. the phone is still S-ON
What i want to achieve:
Put a stock firmware on the phone and thats that.
Not too keen on putting customs firmwares, if there is a Google Edition firmware, that will be a plus if not then the firmware with sense 5 or 6 etc.
The CID is 332 ( could this be an issue)
I just need the phone to work as normal with stock or google play edition stock.
Do i need to get s-on to S-off? whats the easiest way. what firmware would work for this cid-332, do i need to change my CID to get best firmware, these are the stages i need advice.
Thanks a lot guys.
Phone details below
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.13.599.101
version-misc: PVT SHIP S-ON
serialno: HT386xxxxxxxx
imei: 354xxxxxxxxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332

feeldennis said:
Hi guys,
I have gone through the the forum and have read up on the issure, I have made some progress, I need some expert advice on the last few stages.
The Htc one M7 is soft bricked, i have unlocked the bootloder via the htc site, i know how to use ADB and fastboot command line. I have installed TWRP on the phone, now i can see my phone as a drive on my computer. the phone is still S-ON
What i want to achieve:
Put a stock firmware on the phone and thats that.
Not too keen on putting customs firmwares, if there is a Google Edition firmware, that will be a plus if not then the firmware with sense 5 or 6 etc.
The CID is 332 ( could this be an issue)
I just need the phone to work as normal with stock or google play edition stock.
Do i need to get s-on to S-off? whats the easiest way. what firmware would work for this cid-332, do i need to change my CID to get best firmware, these are the stages i need advice.
Thanks a lot guys.
Phone details below
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.13.599.101
version-misc: PVT SHIP S-ON
serialno: HT386xxxxxxxx
imei: 354xxxxxxxxxx
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
Click to expand...
Click to collapse
you seem to have a carrier that has never released a RUU or any useful files really. Did you make a Nandroid backup of you stock software ?
If you have no backup the best you can do is just flash an international Rom that matches you firmware version like this one
https://www.androidfilehost.com/?fid=23501681358543706
During install choose No to stock recovery and No to installing the Radio

clsA said:
you seem to have a carrier that has never released a RUU or any useful files really. Did you make a Nandroid backup of you stock software ?
If you have no backup the best you can do is just flash an international Rom that matches you firmware version like this one
https://www.androidfilehost.com/?fid=23501681358543706
During install choose No to stock recovery and No to installing the Radio
Click to expand...
Click to collapse
Hi there,
I had no back up. So it is like bad luck with this cid 332.
Will this rom "Guru_Reset_M7_5.11.401.10-TeHashX.zip" work?
Thanks for reply.
thanks

feeldennis said:
Hi there,
I had no back up. So it is like bad luck with this cid 332.
Will this rom "Guru_Reset_M7_5.11.401.10-TeHashX.zip" work?
Thanks for reply.
thanks
Click to expand...
Click to collapse
you'll be able to flash it but you will never get ota uptades using this version because of your cid and mismatch between software version and firmware version.
Its not possible to return it to stock .599 so you should either s-off it and do a conversion to another version or use custom roms.

alray said:
you'll be able to flash it but you will never get ota uptades using this version because of your cid and mismatch between software version and firmware version.
Its not possible to return it to stock .599 so you should either s-off it and do a conversion to another version or use custom roms.
Click to expand...
Click to collapse
Cool, best way to S-off?
please advice or put a link, keep in mind it is soft bricked, i can get into the bootmenu and TWRP MENU.
THANKS

feeldennis said:
Cool, best way to S-off?
please advice or put a link, keep in mind it is soft bricked, i can get into the bootmenu and TWRP MENU.
THANKS
Click to expand...
Click to collapse
SunShine S-Off
http://theroot.ninja/
but you still have to flash the rom i listed first and get ROOT

feeldennis said:
Cool, best way to S-off?
please advice or put a link, keep in mind it is soft bricked, i can get into the bootmenu and TWRP MENU.
THANKS
Click to expand...
Click to collapse
flash a close to stock rom and s-off using sunshine
once s-off, change you cid
Code:
fastboot oem writecid HTC__001
then change your MID to PN0710000 using this tool
and finally, flash a x.xx.401.x RUU.
or if you prefer the dev edition version:
change cid to BS_US001
MID to PN0712000
and use the latest ruu 6.07.1540.2

alray said:
flash a close to stock rom and s-off using sunshine
once s-off, change you cid
Code:
fastboot oem writecid HTC__001
then change your MID to PN0710000 using this tool
and finally, flash a x.xx.401.x RUU.
or if you prefer the dev edition version:
change cid to BS_US001
MID to PN0712000
and use a the latest ruu 6.07.1540.2
Click to expand...
Click to collapse
Let me get this clear,
1st i need to flash the above firmware,
2nd S-off with sunshine, is sunshine free?
3rd chand cid and Mid.
then i can use latest RUU.
Can i s-off with out installing any rom first?
Thanks

feeldennis said:
Let me get this clear,
1st i need to flash the above firmware,
2nd S-off with sunshine, is sunshine free?
3rd chand cid and Mid.
then i can use latest RUU.
Can i s-off with out installing any rom first?
Thanks
Click to expand...
Click to collapse
SunShine = $25
Getting s-off and converting to Developers Edition Worth = $1,000,000

Update, functioning M7
clsA said:
SunShine = $25
Getting s-off and converting to Developers Edition Worth = $1,000,000
Click to expand...
Click to collapse
Hi guys, thanks so much for your help and advice,
I decided to go the easy route, and just droped in the cyanogen mod rom and flashed.
Maybe i will do the S-off at a later date.
The phone works super.
Thanks guys.

htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0

Please help me revive this sick m7

Hi Guys,
Bought an m7 cheap on ebay. I don't know anything about the history, except to say it's been fiddled with...
It powers up but it won't boot up; it hangs on the HTC logo.
Bootloader's unlocked, it's been rooted... S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ** edited out **
(bootloader) imei: ** edited out **
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm thinking I should try and take it back to stock, but I don't know where I should go from here and I'm worried I might screw it up.
Any help would be greatly appreciated
Thanks in advance!

Go to RUU mode and flash an RUU. There's a lot of threads explaining how to go to back to stock on this forum. If it still doesn't work, it might be an internal issue like the motherboard.

Can someone please recommend an RUU to go to... I'm just worried if I use the wrong one it will cause more issues. I thought RUUs were dependent on the CID num and as that's been changed to allow custom roms... I'd be happy taking it back to a plain old vanilla HTC / Google - just something to get it back alive.
Thanks

Should also add I can't get s-off... adb devices doesn't show anything... I'm guessing usb debugging wasn't set up

mdb said:
Can someone please recommend an RUU to go to... I'm just worried if I use the wrong one it will cause more issues. I thought RUUs were dependent on the CID num and as that's been changed to allow custom roms... I'd be happy taking it back to a plain old vanilla HTC / Google - just something to get it back alive.
Click to expand...
Click to collapse
There is no ruu we can recommend because your version-main is blank the fact that you also have superCID doesn't help identifying which ruu you'll need to use.
mdb said:
Should also add I can't get s-off... adb devices doesn't show anything... I'm guessing usb debugging wasn't set up
Click to expand...
Click to collapse
You'll have to unlock the bootloader, flash a custom recovery (twrp preferred), flash a rom and use your phone like that or, if you want, from there you will be able to achieve s-off again and convert your phone to wherever you want (Stock Sense or stock GPE) by flashing a RUU.

alray said:
There is no ruu we can recommend because your version-main is blank the fact that you also have superCID doesn't help identifying which ruu you'll need to use.
You'll have to unlock the bootloader, flash a custom recovery (twrp preferred), flash a rom and use your phone like that or, if you want, from there you will be able to achieve s-off again and convert your phone to wherever you want (Stock Sense or stock GPE) by flashing a RUU.
Click to expand...
Click to collapse
Thanks so much for this... I've been learning more all day (traditionally an iOS guy)...
Am I right in thinking I would need to sideload a custom rom through twrp and then install it? If so, I'm having an issue getting my laptop to talk to the phone - "adb devices" is pretty flakey to say the least, sometimes it works sometimes it doesn't... I've read various things about Windows 8 and that adb works best on Windows 7, can you please confirm I'm on the right track here. I'd like to put the Viper rom on it.
Thanks again

In order to flash custom recovery you need to be booted to bootloader menu, and use fastboot commands. If you flash TWRP 2.8.6.0 or later, there's no need to sideload a ROM because newer TWRP recoveries have MTP option, so you use that. Try to go to bootloader, connect your phone to your laptop or PC, and issue a command fastboot devices. If it shows your phone, you're good to go

Thanks donkeyking1...
I got it working eventually, I needed to install new drivers for Windows 8 then adb started behaving properly. I ended up pushing the Viper ROM to the phone... The phone's alive now but currently it has no IMEI, baseband or OS - they're all blank. I'm wondering if it's because I've installed Viper 9 without upgrading the firmware first? My next goals are to try and S-OFF the device so I can install a stock rom, at which point hopefully I'll get OTA updates and then go back to Viper 9 - it looks great, I just can't use it! - no phone signal!
Does that sound like the right approach? I'm trying to flash different custom roms to hopefully find one that works with rumrunner. I've read that some folks have managed to S-OFF on hboot 1.57 with rumrunner, but it's picky on the rom that's installed. It doesn't work on Viper 9...
If anyone can add any help it would be much appreciated!
Thanks in advance

mdb said:
Thanks donkeyking1...
I got it working eventually, I needed to install new drivers for Windows 8 then adb started behaving properly. I ended up pushing the Viper ROM to the phone... The phone's alive now but currently it has no IMEI, baseband or OS - they're all blank. I'm wondering if it's because I've installed Viper 9 without upgrading the firmware first? My next goals are to try and S-OFF the device so I can install a stock rom, at which point hopefully I'll get OTA updates and then go back to Viper 9 - it looks great, I just can't use it! - no phone signal!
Does that sound like the right approach? I'm trying to flash different custom roms to hopefully find one that works with rumrunner. I've read that some folks have managed to S-OFF on hboot 1.57 with rumrunner, but it's picky on the rom that's installed. It doesn't work on Viper 9...
If anyone can add any help it would be much appreciated!
Thanks in advance
Click to expand...
Click to collapse
flash the 7.19.401.2 firmware and then the 7.19.401.2 RUU. If you still have imei problem after that, its most likely an hardware defect.
relock your bootloader if not already locked or re-locked:
Code:
fastboot oem lock
Code:
fastboot orm rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastbppt flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
fastboot reboot
*** use htc_fastboot.exe for flashing the ruu (linked below). Save all files in the same folder where you already have fastboot.exe and adb.exe on your computer.
M7_UL_Firmware_7.19.401.2.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
htc_fastboot.exe

Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!

mdb said:
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
Click to expand...
Click to collapse
To flash a ruu on a s-on phone there are many prerequisites:
The RUU must match your MID: 7.19.401.2 is for PN0710000
The RUU must match your CID: You have superCID so its not a problem.
The RUU must be the same version or an upgrade from your actual version, we don't know your actual version because of your blank versio-main but you have 1.57 hboot which suggest a 6.xx.xxx.x version. So 7.19.401.2 should be an upgrade.
The bootloader must be locked or re-locked.
There is no risk trying it, the worst that can happen is that the phone won't accept the ruu and nothing will be flashed.

mdb said:
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
Click to expand...
Click to collapse
Super CID + your MID. WWE firmware should work just fine. Right @alray?

donkeykong1 said:
Super CID + your MID. WWE firmware should work just fine. Right @alray?
Click to expand...
Click to collapse
:good:

Well, thanks so much for your help guys, but alas it seems the phone is k-put... Flashed the firmware and the rom no problem.... but it still shows no IMEI / IMEI SV / IMSI and it can't recognise the phone number - I'm guessing it can't read the sim. It does show the OS and IMEI in the bootloader, but once booted it's a no go.

mdb said:
Well, thanks so much for your help guys, but alas it seems the phone is k-put... Flashed the firmware and the rom no problem.... but it still shows no IMEI / IMEI SV / IMSI and it can't recognise the phone number - I'm guessing it can't read the sim. It does show the OS and IMEI in the bootloader, but once booted it's a no go.
Click to expand...
Click to collapse
Try to bend your sim tray just a little bit. Maybe your sim card is not reaching the contacts inside the phone. Or put a piece of paper under the sim and see what happens

Thanks donkeykong1, I've tried but it's not working... The fact the IMEI / IMEI SV and baseband are unknown though... they're not sim related...
It does show the baseband and IMEI in fastboot getvar all though?...

There were a lot of people with that same issue, and their phones worked fine, so I doubt it has anything to do with your sim. Your sim works in another phone?

Yeah, the sim's fine. @alray said it's likely a hardware issue if the firmware / rom didn't repair the IMEI issue, and the other threads I've looked at with the same issue are all saying the motherboard's faulty.

Although I am baffled as to why it is showing the IMEI / baseband in the bootloader, in fastboot etc. but not once the phone has booted up?...
I read on another thread (http://forum.xda-developers.com/showthread.php?t=2253514) that maybe flashing a kernal and/or radio might solve it?
Just wondering whether I should try flashing an official HTC rom? I've been in touch with the guy I got it off and he said it was originally on Orange, UK:
http://www.htcdev.com/devcenter/downloads > One M7 / v5.0.2 > Find Files : Page 6
One M7 / Orange / UK / CRC / 3.4.10 / v5.0.2 / 539.0 MB / 7.19.61.10
Was also thinking of...
http://www.htcdev.com/devcenter/downloads > One M7 / v5.0.2 > Find Files : Page 1
One M7 / HTC / EU / MR 3 / 3.4.10 / v5.0.2 / 486.0 MB / 7.19.401.22
If I did that would I need to update the firmware first like you advised originally @alray?
If I know I can revive the IMEI etc. I'll be happy to go ahead and pay to S-OFF
Thanks in advance

You need a kernel to match your firmware. If you're on 7.19.401.2, then you need 7.19.401.2 kernel. I can give you boot.img, but I don't have the whole zip, with modules. Then again, if your phone boots fine, maybe boot.img will help. I'd [email protected] to confirm my thoughts though. He's much more into this than I am