Database Develop

please help! htc one possible boot loop of death.

edit and tldr
ok so i recieved the phone from htc with a bootloop out of the box
instead of sending it back i was a numpty and decided to sort it myself and unlocked it to flash a rom
i accidentially deleted all the data
managed to get my winsows 8 laptop working today and got drivers working smoothly to the point i was able to sideload a rom so the phone finally had life from being a brick
my issue is no matter what rom i load it boots to splash screen, hangs at a black screen with the status bar at the top and battery and time then reboots and repeats.
i want help to get my phone back to life and stable with a workable rom and no bootlooping
i dont know what the issue is
i dont have s off
rumrunner wont work
i cannot boot into phone to allow debugging or disable fast boot
please help
device info
C:\Documents and Settings\fresh\Desktop\one\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(bootloader) imei: **********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.328s
i will offer a small sum for who ever gets me a working phone. small exchange for a paperweight !

Deleted. Op edited post to include cash reward. Dont want to look like im helping to receive money.

hi there, thank you for the reply, i have done steps 1, id already done that but ive done it again and installed the sdk into a folder in c drive for ease. the only problem is that when i click on fastboot in xp it comes up with a cmd windows a lot of writing comes down and then it just closes :/
ive already voided the warranty as ive somehow managed to unlock the bootloader and ive flashed cmw now what i need to do is somehow get s off and sideload a rom

another issue i have is that because i cant use fastboot the way youve said, ive downloaded an all in one tool from this forum, when i click a process it dosent do anything for me, but what it does so, is open a cmd window in which im able to type in fast boot commands i did the getvar all command and here is what you requested
'C:\Documents' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\fresh\Desktop\one\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(bootloader) imei: **********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.328s
C:\Documents and Settings\fresh\Desktop\one\data>

Deleted

garyfl said:
ok so i think this is going to be a little long winded
basically, i got a htc one given to me by htc,
Click to expand...
Click to collapse
Why don't you think they would give you a new working one?... :s (this is just a rhetorical question)

thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu

the ruu you have linked indicates i need s off, which i am having trouble doing, could you guide me ? i am thinking when i have fixed my windows 8 laptop tommorow this is going to be a smoother process. it also says i need hboot 1.44 and have to flash this

garyfl said:
thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu
Click to expand...
Click to collapse
If you don't solve it before I get a lil bit of time, I can try for tonight but can't promise it as it's still hectic here at work, I'll log in remotely and have a look at things if you want, and try to help you get it sorted.
In the meantime, you can take a picture of the hboot or fastboot screen that you get to with power + vol down and post it, and that will help you get the information from us for more information on the phone.
Also post a shot of the correspondence from HTC with your personal information removed/redacted/left out and that will also help us help you.
DO NOT ATTEMPT S - OFF with the knowledge and hardware that you're working with, you first need to use adb and fastboot some and be familiar with it before even going there. I'm not saying not ever, I'm saying not until you've resolved this and the phone's running good.

Deleted

when i run rumrunner with my version 2.24.401.1 it just says run again and read. so obviously failing. i did everything before i typed fastboot devices and got my device code, then getvar ver to get my number and downloaded appropriately but rum runner dosent work. so no s off. i give up.

sorry didnt read your reply, well it didnt initialise so no s off anyway

garyfl said:
sorry didnt read your reply, well it didnt initialise so no s off anyway
Click to expand...
Click to collapse
Take a picture of the hboot screen and post it for us

im sorry i cant take a pic atm no cameras, what i can do is write eveything out as it looks in detail for you
***tampered*** <--- in dark grey
***unlocked*** <--- in pink
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OPENdsp-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013, 00.54:00.14313
FASTBOOT USB <--- in red
then its just the vol up and down with selecable bootloader, reboot, reboot bootloader, power down at the bottom. i have rooted many phones in the past, desire hd, one x, galaxy note, galaxy s4, its just the trouble i am facing i think is using xp

can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.

garyfl said:
can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.
Click to expand...
Click to collapse
flash twrp/cwm recovery to your one
open the sideload feature of the customer recovery on your phone and connect to your computer usb
download this and put the downloaded file together with your adb and fastboot folder
then adb sideload or adb push the dowloaded guru reset to your One
once it is done, you can install the guru reset zip using the custom recovery install option

right just to update i have some semi good news and fell im getting somewhere
got my windows 8 laptop up and running today and installed all drivers and adp corrdctly, this accounts for the intel usb 3 mod too. adb and fastboot were recognising the device.
ive succesfully got out of brick mode and managed to get a rom to sideload to the deviice, the rom being viper rom in question, installed successfully, only issue is i have a wierd bootlooping issue where it does actually boot to lockscreen but when i pull lockscreen up with my finger it shows htc splash screen.
having ago with android revolution now.
wondering if i have to flash a boot.img or something
can anyone advise ?
ive spent countless days on this

regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,

garyfl said:
regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,
Click to expand...
Click to collapse
the guru ruu.zip for 2.24.401.1 is sideloading now

guys, the guru stock installed but now im back to the very beginning of the way i recoieved my phone. bootloops to the black screen with bar at top with date and battery, then after a while restarts, please someone help me

[Q] Bootloop - Green HTC logo, sometimes Android

Ok, so I have admittedly really screwed up and I'm hoping someone here (or multiple someones) can help me out.
My major screwups:
No nandroid backup.
No s-off
I have Sprint
Current State:
I can get to fastboot, recovery and adb works fine. But no matter which recovery/rom combination I try, I get the same end result. My phone will boot to the "HTC One" screen, then go the green HTC logo/white background screen then reboot. Sometimes it stays active long enough to begin the "Welcome to Android" stuff (pick your language, wifi connection, etc...), but not nearly long enough to get through all the screens.
What I've tried so far:
Multiple recovery options including CWM and TWRP. CWM versions 6.0.4.3, 6.0.4.5 touch. TWRP versions 2.6.3.3, 2.6.3.4, 2.7.0.0.
ROMS: ARHD 31.6 and 62.0 (I know this doesn't work with Sprint), Viper 6.1 and some "stock" rom I found somewhere (filename One_4.19.401.11_odexed.zip).
I don't remember exactly the order, but I know I did TWRP 2.6.3.4 and ARHD 62.0 first. Then did Viper 6.1, then ARHD 31.6. Since then, I've tried every combination of recovery and ROM that I can think of.
Here's getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4205mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
I'm willing to try anything at this point. So suggestions are welcome. You're also welcome to berate me for the above mentioned screwups, but it won't be very helpful.
TIA

Goto_End said:
Ok, so I have admittedly really screwed up and I'm hoping someone here (or multiple someones) can help me out.
Multiple recovery options including CWM and TWRP. CWM versions 6.0.4.3, 6.0.4.5 touch. TWRP versions 2.6.3.3, 2.6.3.4, 2.7.0.0.
TIA
Click to expand...
Click to collapse
Those sound like version numbers for m7_u/ul models, flash proper TWRP for Sprint from here: http://techerrata.com/browse/twrp2/m7wls
(make sure to check MD5 on the download)

nkk71 said:
Those sound like version numbers for m7_u/ul models, flash proper TWRP for Sprint from here: (can't post links yet)
(make sure to check MD5 on the download)
Click to expand...
Click to collapse
Downloaded the 2.6.3.0 from the link you provided (checked md5), flashed recovery. Did an adb push to get the Viper ROM (also checked the md5) back to /sdcard and flashed the ROM. Same results as before.
Additional info:
Sometimes I will get "com.htc.htcdialer is not responding", sometimes not.
The screen will timeout on the green HTC logo screen. If I hit Power to bring it back to life, I have to "pull to unlock" and either the logo screen is still there or it's made it to "Welcome to Android".
I actually got to the Welcome screen this time. Picked the language, wifi network and started with my Google login before it rebooted.
Maybe an incompatible ROM issue? If so, I'm out of ideas as to what to try next.
I've downloaded what I believe to be the RUU for this model phone, but since I can't see the phone in Windows, I haven't even tried the RUU.

Goto_End said:
Sometimes I will get "com.htc.htcdialer is not responding", sometimes not.
...before it rebooted.
Click to expand...
Click to collapse
That's usually caused by the modem not initializing properly, and you could have some corrupt partitions due to using an m7_u/ul and it's time for ruu i guess.
Better head over to the HTC One Sprint forum: http://forum.xda-developers.com/sprint-htc-one should be plenty of help there.
Most of us here are on m7_u/ul so can offer only limited assistance... could be as simple flashing a radio for Sprint... but like I said, I'm not too familiar with Sprint unbrick.
Sorry & Good Luck

There's an awesome Rescue Tutorial over in the Sprint HTC One forum for people like me who flashed a GSM ROM on a CDMA phone. I can't post links yet, or I'd link to it just for posterity.
In essence, the GSM ROMs screw up the partition table. The fix was really easy. Most of the time was spend downloading the correct ROM and waiting for the adb push.

[Q] RUU stuck at "checking headers"

I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.

XDA Dev said:
I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.
Click to expand...
Click to collapse
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!

SaHiLzZ said:
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!
Click to expand...
Click to collapse
Haha, thanks, I guess nearly 3 years of lurking on these forums taught me something about posting.
I was using a Windows Vista SP2 PC to try this. I've just tried it on my Mac running Windows 7 SP1 with bootcamp, the RUU file (which still checks out with the correct MD5 hash) starts the installshield wizard normally, but as soon as I accept the terms and conditions, the program closes and nothing opens again. I checked on task manager, the process closes shortly after accepting the terms. I tried restarting and looking up for a solution but I couldn't find anything that worked.
Is Vista really the only reason it's stuck at checking headers? I know Vista is rather despised by a lot of people, but by 2014 it did get better. I'd rather use that machine because on my Mac running Windows 7 the RUU could not start up because I've made the Windows partition too small. (It has around 3gb free now whereas the vista machine has more than 150).

Sorry for the double post, but it's probably my last one on this thread.
Even if my boot loader was re-locked, I tried running the firewater program to get s-off, and it worked. (As a bonus it re-unlocked my boot loader without wiping the phone, but I re-locked it again to get the ruu working).
Then I tried downgrading to hboot 1.44, but for some reason it kept giving an error like "failed: remote 42 custom id check fail." I decided to try the sense 5.0 ruu anyway (on my vista PC), and it worked! The phone now says "relocked" but tampered is gone of course, and I have hboot 1.44, android 4.1 and htc sense 5.0, but still s-off.
The first update popped up (and it's not android 4.4 with sense 6, it's something in between) so I'm going to update until no more updates are available. Then I'm going to re-unlock the boot loader because I want to root my phone, and then set up all my stuff. When a new update comes out, I can just flash the original recovery, apply the update and then re-flash twrp to root again.
Thank you for the suggestion to install the older ruu. I'm still stumped on why the newer one didn't work (it would have caused much less hassle), but whatever. At least my phone is much cleaner now. It feels good to have it like this again, I'm not against custom roms but I like the stock software too.
I'm using my iPhone to write this, but trust me, my htc is in full working order now.
Until next problem I can't solve myself
Sent from my iPhone using Tapatalk

Thanks for updating back. Don't S-ON.

SaHiLzZ said:
Thanks for updating back. Don't S-ON.
Click to expand...
Click to collapse
Yeah, I'm not going to. I've updated to android 4.3 now and I'm still downloading updates--it updated hboot to 1.55 but I still have s-off, so I believe it stays s-off if I don't run the command to (I guess irreversibly) go back to s-on, which I don't even know. (I didn't do s-off before because I didn't care about the extra privileges and was afraid of bricking my phone, but now that I have it I don't mind so I'm keeping it).
Sent from my iPhone using Tapatalk

[Q] Cannot install any ROM's at all, but can access bootloader.

Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.

Loafmanuk said:
Hi guys, my first post on here, sorry it has to be a request for help.. I've read through a mountain of threads about M7 issues, but none seem to match my issue, so I figure I can only ask.
Oh, by the way, I am very much a novice at this, so I may need things to be explained in a little more detail than some. I'm not a total noob as I have modded a few other phones in the past.
I have an HTC One M7 and decided I wanted to flash a different ROM. I went to HTCDEV and went through the process to unlock the bootloader. This went flawlessly.
I then installed TWRP 2.6.3.3 in fastboot. Again no problems.
I have an OTG cable (with external power).
I made a backup with TWRP which went ahead without error.
I then did a test flash of ViperOne 6.2.0 which went without issue, but ultimately I wanted to flash ARHD 91.1 (Lollipop 5.0.2).
My problem is that after ViperOne 6.2.0 I can no longer install ANY ROM at all. It says installing but then TWRP returns to the main menu with no error mentioned. I'm sure it's something I've done, just don't know what. After a few failed flashes I did format various partitions, and I suspect I flumped something at this point!?!
It's like the all the partitions on the phone are locked. And everytime I exit TWRP it says you have no OS installed and also says I'm not rooted and do I want to install SuperSU. I say yes everytime, but it will ask the next time still.
It's got to the point that I've ran out of ideas, so I hope there is someone that may have an idea.
So to summarise,
I have an unlocked bootloader.
I am still S-ON as I have HBOOT 1.57 and Rumrunner wont work.
I have no ROM installed, so cannot boot the phone into anything but fastboot and recovery (I can still flash different recovery environments from fastboot)
Hopefully someone may have an idea. Thanks very much in advance.
Click to expand...
Click to collapse
ok first of all, you need to use TWRP latest for Lollipop custom roms, 2.6.3.3 is too old, use 2.8.6.0, also, expect problems with Lollipop roms whilst your still on KitKat firmware (hboot 1.57), you really need to be on Lollipop firmware to use Lollipop custom roms.
People using the latest Lollipop custom roms on KK firmware are reporting no wifi, Bluetooth issues etc.
can you post your fastboot getvar all please without imei and serial number please.

Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(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: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.

BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.

Loafmanuk said:
Hi, thanks for the quick response.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(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: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I hope this shows something up.
I really appreciate your help.
Click to expand...
Click to collapse
yup shows me a lot of info: 6.16.61.8 this shows me your on Orange UK network, although its now T-Mo & Orange together as EE, sorry but they've not released the Lollipop update yet for the 61's which is the 3rd set of numbers pulled from that long number above, this also confirms your on orange UK ORANG001 and so does this: PN0710000 kind of......... long story
m7_ul this tells me you have the LTE version of the M7
4275mV battery info = good
4T.28.3218.04 radio version
1.57.0000 hboot version
(bootloader) security: on (bootloader) build-mode: SHIP PVT SHIP S-ON basically your s-on
it would show your imei number and serial number too, but you want to keep those 2 numbers to yourself.
---------- Post added at 06:40 PM ---------- Previous post was at 06:36 PM ----------
Loafmanuk said:
BTW, I tried TWRP 2.8.6.0, but it wont read from the external USB stick like 2.6.3.3 does!?! Plus I can't install CM11 or 12 either, so it,s not just newer ROM's.
Click to expand...
Click to collapse
plug your phone into the computer whilst its booted into recovery main screen only, the internal storage of your phone should open on your computer, copy the rom.zip to your internal storge, unplug and flash it.
I'm pretty sure 2.8.6.0 supports usb otg, you may have to select it as a storage option first as it defaults to internal storage, cant quite remember as I'm on an M8 now.
edit: yes it does, select install and then at the top change from internal storage to usb otg.

I've re installed TWRP 2.8.6.0 and finally got it to see the USB stick (reformatted it). But when I try and install it seems to be going ahead, but after a minute or to I get the TeamWin splash screen flash up as though recovery is booting and it returns to the main menu. Oddly, the LED on the memory stick is still flashing!?!
I'll try installing from the phones internal memory like you suggested and hopefully that will work. Thank you so much for this, I'll update in a while.

Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.

Loafmanuk said:
Okay, I've got the ROM on the internal storage and am currently trying to install it. It has gone through to suggest it has installed so I am rebooting...
It has got further than I have with the OTG all day, so I have my fingers crossed...
Waiting...
Waiting...
And we have lift off, wow! It installed fine that time, thank bacon for that! I really didn't need the expense of getting another phone at the moment, what with car insurance, van insurance, van tax, and all the other bits I've just forked out for.. I would have been phoneless (and possibly homeless!) for the next several weeks!
So it was perhaps a dodgy flash drive or OTG cable maybe? Strange that it worked before.
I can not thank you enough! Strangely I did try to put the ROM on the internal storage earlier, but it said the ROM file was too large to transfer to internal storage!? Not sure why it suddenly let me, but very happy it has! Thank you again, without your suggestion I probably wouldn't have bothered trying that method again. :victory:
You're awesome.
Click to expand...
Click to collapse
you are very welcome, I just use my USB OTG for backup's and restores, never tried flashing a rom from it.

Used phone from Africa, EFS partition likely formatted, no backup, what can i do?

*I will try to provide as much information as I can, so this will probably be a long post. Sorry!*
Hi,
I've bought a used HTC One M7 from Ghana because I needed a replacement phone while I was working there. I noticed it didn't have a factory ROM on it, but I figured I would change that anyway. So I bought it.
First problem with it was a well documented issue with HTCs and their conflict with Google Play Services which resulted in the malfunctioning of voice calling. Since it wasn't a stock ROM, i was unable to get the OTA updates that eventually fixed this bug.
So I decided to flash a custom ROM on it.
The phone had SuperCID and was S-off. It turns out it was a US Sprint version, although its back cover had an ATT logo. Who knows what was done to this phone. Anyway, since I am far from being an expert at flashing custom ROMs and custom recoveries, I asked a friend to help.
He managed to install TWRP and a Cyanogen 12 nightly ROM (12-20151108-NIGHTLY-m7spr) but in the process something must have happened because now, even though the phone works fine and boots fine, it doesn't recognise my sim card and there is no network signal.
When I realised that the baseband, IMEI, MEID, ICCID and a few others said "unknown" instead of their values, i dug through this forum and concluded that the EFS partition must have been erased or damaged in the process. (is there a way to confirm that?) There was no backup, obviously.
I have read bits and pieces of information about this problem, but nothing that seemed helpful in my particular case.
I can't flash any other ROM on it because it says the MD-5 file is missing or something like this.
So I am stuck with an almost working phone, and no solution to my problem. I even called HTC service and they said they will not fix a phone sold in the US, since I live in Romania.
So this is basically my only hope of getting this phone to work again. If even possible. So, please, in layman terms, what can I do?
Thank you!

tudorv said:
*I will try to provide as much information as I can, so this will probably be a long post. Sorry!*
Hi,
I've bought a used HTC One M7 from Ghana because I needed a replacement phone while I was working there. I noticed it didn't have a factory ROM on it, but I figured I would change that anyway. So I bought it.
First problem with it was a well documented issue with HTCs and their conflict with Google Play Services which resulted in the malfunctioning of voice calling. Since it wasn't a stock ROM, i was unable to get the OTA updates that eventually fixed this bug.
So I decided to flash a custom ROM on it.
The phone had SuperCID and was S-off. It turns out it was a US Sprint version, although its back cover had an ATT logo. Who knows what was done to this phone. Anyway, since I am far from being an expert at flashing custom ROMs and custom recoveries, I asked a friend to help.
He managed to install TWRP and a Cyanogen 12 nightly ROM (12-20151108-NIGHTLY-m7spr) but in the process something must have happened because now, even though the phone works fine and boots fine, it doesn't recognise my sim card and there is no network signal.
When I realised that the baseband, IMEI, MEID, ICCID and a few others said "unknown" instead of their values, i dug through this forum and concluded that the EFS partition must have been erased or damaged in the process. (is there a way to confirm that?) There was no backup, obviously.
I have read bits and pieces of information about this problem, but nothing that seemed helpful in my particular case.
I can't flash any other ROM on it because it says the MD-5 file is missing or something like this.
So I am stuck with an almost working phone, and no solution to my problem. I even called HTC service and they said they will not fix a phone sold in the US, since I live in Romania.
So this is basically my only hope of getting this phone to work again. If even possible. So, please, in layman terms, what can I do?
Thank you!
Click to expand...
Click to collapse
First of all, sprint phones are CDMA phone. Once the sim is unlocked, it will work on GSM but you'll not get full connectivity i.e probably no LTE.
Is the IMEI MEID and Baseband correctly displayed when using "fastboot getvar all"? Also post the output of "fastboot getvar all" (don't shate your imei and meid). Sometimes, flashing a RUU can fix this problem, in some other cases its caused by an hardware defect.
And btw, HTC phone does not have an EFS partition.

alray said:
First of all, sprint phones are CDMA phone. Once the sim is unlocked, it will work on GSM but you'll not get full connectivity i.e probably no LTE.
Is the IMEI MEID and Baseband correctly displayed when using "fastboot getvar all"? Also post the output of "fastboot getvar all" (don't shate your imei and meid). Sometimes, flashing a RUU can fix this problem, in some other cases its caused by an hardware defect.
And btw, HTC phone does not have an EFS partition.
Click to expand...
Click to collapse
Thank you for your reply. I will get the information you mentioned and I will reply again as soon as I have it. If the HTCs don't have that partition, then this gives me a bit of hope, since I am sure that the baseband, IMEI and all the others were there before I flashed the CyanogenMod. So it might not be a hardware issue.
Thanks!

alray said:
First of all, sprint phones are CDMA phone. Once the sim is unlocked, it will work on GSM but you'll not get full connectivity i.e probably no LTE.
Is the IMEI MEID and Baseband correctly displayed when using "fastboot getvar all"? Also post the output of "fastboot getvar all" (don't shate your imei and meid). Sometimes, flashing a RUU can fix this problem, in some other cases its caused by an hardware defect.
And btw, HTC phone does not have an EFS partition.
Click to expand...
Click to collapse
Sorry for the delay. Overworking and having to do everything on a Mac makes these things a bit harder. Basically I have to read tutorials for every step I do. So..
I finally was able to get the fastboot command a try. You were right. The IMEI and MEID are there, but the baseband is not. What does that mean? Flashing a RUU will fix this? Can you point me to the right RUU to flash so I don't brick this troublesome phone?
Thank you again for your help. If anybody else has any suggestions, I'd love to hear them. Thanks!
Here's the fastboot result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34KS901953
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4107mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

tudorv said:
Sorry for the delay. Overworking and having to do everything on a Mac makes these things a bit harder. Basically I have to read tutorials for every step I do. So..
I finally was able to get the fastboot command a try. You were right. The IMEI and MEID are there, but the baseband is not. What does that mean? Flashing a RUU will fix this? Can you point me to the right RUU to flash so I don't brick this troublesome phone?
Thank you again for your help. If anybody else has any suggestions, I'd love to hear them. Thanks!
Here's the fastboot result:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA34KS901953
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: XXXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4107mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Try to flash the latest sprint RUU:
http://dl3.htc.com/application/RUU_...1.10.exe?_ga=1.245824013.849696128.1459511845

alray said:
Try to flash the latest sprint RUU:
http://dl3.htc.com/application/RUU_...1.10.exe?_ga=1.245824013.849696128.1459511845
Click to expand...
Click to collapse
Just wanted to let everyone know that it worked. I was able to flash a Sprint RUU (not the one from their website, because the exe utility crashed at some point. don't ask me why) I flashed a zip RUU using fastboot. Just like that. In two minutes I had my phone back.
So, again, thank you very much for your help.
T.