Database Develop

[Q] HTC One Bootlooping after Google Edition ARHD 6.0 installation

At this time I am pretty much hopeless... Seriously, nothing works, but if a miracle happens and I get my HTC One back to life it will be thanks to you guys.
So... This is my story:
Today I was using my HTC One M7_UL like any other day, I had Android OneDroid BETA 15 (a CyanogenMod with a few tweaks) installed and I got bored of it, so I decided to flash a Google Edition ROM. Came to the forum and looked for the thread with most replies on "Custom Android HTC One ROMs" and found the winner of the Google Edition ones, the ARHD 6.0 Google Edition. Fine, I thought, let's flash this [email protected]%#. So I started by downloading the latest version (roughly 550 MB) and connecting my HTC One to my Windows 8.1 Pro computer. The HTC drivers don't work with my 8.1 Pro Windows but since I only needed it to send the .zip file to my Internal Storage I gave it a shot. Copied everything, disconnected and proceeded to my recovery (TWRP) where I Wiped it up and flashed ARHD 6.0 GE. After installing, still on the recovery, restored the phone to factory presets and rebooted it. A Google logo appeared and some Nexus-like balls started to spin, some weird sh%t. Until there, everything absolutely fine, but it stood there with the balls spinning for 3~4 minutes and I thought it was normal because it was the first boot after flashing the new ROM. Got to Language Settings on the Android Welcome screen but then it quickly turned black and reeboted. HTC Logo appeared for roughly 1 second and it got black and rebooted again, this time starting back up but when I got to the Language setup it would do the same thing, over and over again.
So I started looking into it and didn't find many answers, then I decided to try and flash another Google Edition ROM, SkyDragon, but as I am a COMPLETE NOOB in this rooting and wobbly wobbly thingies I had no idea how I would get the .zip file to the Internal Storage, since the HTC One HAS NO SD CARD!!! I researched a bit and found sth called ADB Sideloading, which I am certain you know what it is, but the thing is, since my computer doesn't quite work with HTC Drivers I had to use my sister's PC, with Windows 7 and HTC One All-in-One kit. I could access my bootloader and recovery despite of the bootloop, which I think is a good thing, so I put it to fastboot mode, connected the cable to her computer and on the phone it changed from "fastboot" in red to "fastboot usb" in red also, so I thought, oh ok, it will work now. But when I tried ADB commands or tried any of the commands on the All-in-One thing it would just say "NO DEVICES FOUND" or something among those lines.
Anyway, if someone got this far I already thank you for trying to help but I am pretty certain I got a bricked device. I don't even now what to do, should I try to ADB Sideload this other ROM or should I try a Sense ROM, cuz I read somewhere that Google Edition ROMs only work when migrating from Sense ROMs, and if I am supposed to flash a Sense ROM how would I do so? Please try to be as simple as possible, I don't know much and I am pretty noob, anyways, thank you so much, and I hope you can help me!
(Also, before this bootloop it was S-OFF and now it shows as S-ON)
Waiting for a response,
John B.

You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.

BenPope said:
You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.
Click to expand...
Click to collapse
Yeah I am unlocked and untempered.
Here is my fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(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: 4309mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.077s
And I am ABSOLUTELY SURE that before all of this it was S-OFF, ABSOLUTELY!

BenPope said:
You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.
Click to expand...
Click to collapse
Also my TWRP is 2.6.3.3 so I should be good about that right?

Jvov said:
Also my TWRP is 2.6.3.3 so I should be good about that right?
Click to expand...
Click to collapse
Yes, but as far as I know, you need to be S-Off for GPE KitKat ROMs.
Do you really have no version-main?
If your hboot is 1.44 and dated prior to June, you should be able to use revone to S-Off, but you'll need a booting ROM of Android 4.2.2.

BenPope said:
Yes, but as far as I know, you need to be S-Off for GPE KitKat ROMs.
Do you really have no version-main?
If your hboot is 1.44 and dated prior to June, you should be able to use revone to S-Off, but you'll need a booting ROM of Android 4.2.2.
Click to expand...
Click to collapse
Can you explain exactly how can I do that?

Just flash back to another ROM for the moment that has root then use rumrunner to get S-OFF then flash ARHD GPE again. You'll be fine then.
Sent from my One using XDA Premium 4 mobile app

Also don't do a reset after flashing the rom. It will boot loop every time.
Bat cave One

zelendel said:
Also don't do a reset after flashing the rom. It will boot loop every time.
Bat cave One
Click to expand...
Click to collapse
Solved, thanks to all!

[Q] HTC One relocked, can't flash (signature error)

Hey All,
I hope you guys can help me, I'm completely lost in all these threads and posts. I've spent hours on this, literally hours...
I have a HTC One M7 (bought in Belgium) which I wanted to return to stock because of a faulty speaker (I just rooted the standard image). So I relocked the bootloader to flash an RUU. I tried flashing several European RUUs from the xda collection, but nothing worked. I also tried a zipped firmware, and it also fails. I always get this error:
FAILED remote: 12 signature verify fail
I'm stuck in fastboot, it doesn't boot into the OS anymore, only fastboot.
Getvar output:
C:\ADT\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4024mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.051s
I try to flash the RUU Zip M7_UL_JB_50_HTC_Europe_1.29.401.16_R_Radio_4A.14.3250.13_10.33.1150.01_release_318486_signed_2_4_decrypted.zip
Strange thing is, when I check the zip's android-info:
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__E11
...
So I don't get anymore why it would fail a signature check...
I also tried flashing a newer version, this didn't work either. What makes matters worse, the battery keeps uncharging as I continue to struggle...
Tell it to me straight, doctor... Is my HTC doomed to be a paperweight?

What do you mean "flash a RUU" ? Is it you try to fastboot flash the RUU ? It won't work that way.
Checking this : http://www.androidruu.com/?developer=M7
I see there is only one RUU that may work for you : RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
What you need to do:
1- in fastboot mode - relock the bootloader : run command fastboot oem lock (you did this already)
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish

ckpv5 said:
What do you mean "flash a RUU" ? Is it you try to fastboot flash the RUU ? It won't work that way.
Checking this :
I see there is only one RUU that may work for you : RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
What you need to do:
1- in fastboot mode - relock the bootloader : run command fastboot oem lock (you did this already)
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
Click to expand...
Click to collapse
First of all, thanks a bunch for taking the time to respond.
I'm currently downloading the proposed RUU and will try flashing it.
I don't understand, however, why my downloaded RUUs wouldn't work since the CID and model corresponded?
I tried both methods: using the RUU to flash and using the fastboot oem rebootRUU > flash zip.

dwarfstrider said:
First of all, thanks a bunch for taking the time to respond.
I'm currently downloading the proposed RUU and will try flashing it.
I don't understand, however, why my downloaded RUUs wouldn't work since the CID and model corresponded?
I tried both methods: using the RUU to flash and using the fastboot oem rebootRUU > flash zip.
Click to expand...
Click to collapse
When your device is S-ON, you need a correct version RUU i.e 1.29.401.16 (which is not available, I believe), so you should go for a higher version not lower version.
I'm new to HTC One too so not so sure about fastboot oem rebootRUU, but I believe it needs a S-OFF device to work but yours is S-ON.
More info : http://forum.xda-developers.com/showthread.php?t=2358738

ckpv5 said:
When your device is S-ON, you need a correct version RUU i.e 1.29.401.16 (which is not available, I believe), so you should go for a higher version not lower version.
I'm new to HTC One too so not so sure about fastboot oem rebootRUU, but I believe it needs a S-OFF device to work but yours is S-ON.
[/url]
Click to expand...
Click to collapse
That RUU doesn't work, after checking the signature I get: ERROR [158]: IMAGE ERROR...

dwarfstrider said:
That RUU doesn't work, after checking the signature I get: ERROR [158]: IMAGE ERROR...
Click to expand...
Click to collapse
Search for ERROR 158 may help you.
What I understand ERROR 158 maybe because the bootloader is not relocked, not using USB2.0, maybe also a modified hboot (usually the one that remove the red text warning) is installed prior to running the RUU, not running the RUU in Admin Privilege mode.
Maybe someone else have better idea, have to wait for that.

What I understand ERROR 158 maybe because the bootloader is not relocked, not using USB2.0
- No, I locked using fastboot oem lock with USB cable.
maybe also a modified hboot (usually the one that remove the red text warning) is installed prior to running the RUU
- Afaik, I never installed a custom hboot myself. I get the red text warning at the white HTC screen.
not running the RUU in Admin Privilege mode.
- Nope, the RUU runs with admin privileges in Win 7
Maybe someone else have better idea, have to wait for that.
- Let's hope so :laugh:

This is what my phone looks like atm:
i.imgur.com/ bX9MFM3.jpg
(can't post pics/links yet, sorry)
Please guys, help a fella out... I will be forever grateful

Update: I unlocked my phone again with the unlock bin from HTCDev and now it boots again...
I suppose I need to do S-OFF with revone since I'm at 1.44, but unsure. Damn this stuff is confusing.

You will need to flash new firmware I saw a hierarchy of htc one's Ruu firmware list on android revolution site.
Just check in the name of the correct ruu you downloaded and try to match the numbers of your Ruu with the list given there. I hope it may help you or if you get confused Pm me.
Sent from my HTC One using XDA Premium 4 mobile app

OK, I solved it.
So I did an S-OFF with revone, then locked and removed tampered (also revone).
Then I flashed a good RUU. It took ages to find a good one, followed another thread (2325010) on the forum which I can't link because of the restrictions .
Then I used thread 1672425 to put S-ON again and now my One it back to full stock!

[Q] My HTC One is bricked!!!! please HELP

Hello everyone. It is my first time on this forum, so please be patient.
On Saturday I received my new HTC One 802d dual sim. Following in the steps of this and other forums I could root it and unlock the bootloader.
Then I wanted to get S-Off for putting on a new ROM but while the Moonshine was running, in one of the many resets, the phone can't start the OS (obviously cmd window showed an error).
From there on I tried a myriad of things but with no success. I could not find the original RUU to flash it either.
I am truly desperate!!!! can anyone help ???
I leave data from my HTC One:
l
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.27.0000
(bootloader) version-baseband: 1.01.32.0917
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.35.707.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: A********************66
(bootloader) product: m7cdwg
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0751000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-8076a49a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Android 4.2.2
HTC Sence 5.0
Soft Number 2.35.707.2
HTC SDK API level 5.34
PRI Version 4.20_09A
PRL Version 10014
Kernel 3.4.10-g8914e14
Baseband Version 1.01.32.0917-1237.25.32.0717
Biuld Number 2.35.707.2 CL257405
Browser version WebKit/534.30
THANKS YOU!!!!!

pdelmazo said:
Hello everyone. It is my first time on this forum, so please be patient.
On Saturday I received my new HTC One 802d dual sim. Following in the steps of this and other forums I could root it and unlock the bootloader.
Then I wanted to get S-Off for putting on a new ROM but while the Moonshine was running, in one of the many resets, the phone can't start the OS (obviously cmd window showed an error).
From there on I tried a myriad of things but with no success. I could not find the original RUU to flash it either.
I am truly desperate!!!! can anyone help ???
I leave data from my HTC One:
l
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.27.0000
(bootloader) version-baseband: 1.01.32.0917
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.35.707.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: Remove
(bootloader) product: m7cdwg
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0751000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-8076a49a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Android 4.2.2
HTC Sence 5.0
Soft Number 2.35.707.2
HTC SDK API level 5.34
PRI Version 4.20_09A
PRL Version 10014
Kernel 3.4.10-g8914e14
Baseband Version 1.01.32.0917-1237.25.32.0717
Biuld Number 2.35.707.2 CL257405
Browser version WebKit/534.30
THANKS YOU!!!!!
Click to expand...
Click to collapse
You might want to remove your meid from your first post.
Assuming you have a custom recovery installed, you might try to install Maximus HD for dual sim. I found these instructions in his other thread for the single sim rom. Why don't you think you have a rom installed? Are you stuck in bootloader? You can follow these instructions by alray but you must use a custom recovery for your variant and the Maximus HD rom for your variant.
If you get the rom installed and working, I would try rumrunner S-OFF, since you have a lower hboot. Since you have such a unique phone, I would make nandroid backups to I could recover from issues easier. I hope it helps.

majmoz said:
You might want to remove your meid from your first post.
Assuming you have a custom recovery installed, you might try to install Maximus HD for dual sim. I found these instructions in his other thread for the single sim rom. Why don't you think you have a rom installed? Are you stuck in bootloader? You can follow these instructions by alray but you must use a custom recovery for your variant and the Maximus HD rom for your variant.
If you get the rom installed and working, I would try rumrunner S-OFF, since you have a lower hboot. Since you have such a unique phone, I would make nandroid backups to I could recover from issues easier. I hope it helps.
Click to expand...
Click to collapse
Thank you very much!!!! I'll try to flash Maximus HD, but I have a few questions:
The phone has to be unlocked?
What would be the details to consider the rom to choose?
Thanks!!!!

pdelmazo said:
Thank you very much!!!! I'll try to flash Maximus HD, but I have a few questions:
The phone has to be unlocked? Yes, the phone has to be unlocked!
What would be the details to consider the rom to choose? The rom must be for your variant, if you flash a rom that is not designed for your variant you can brick your phone. There are not a lot of choices for your variant!
Thanks!!!!
Click to expand...
Click to collapse
See answers in Magenta. You should check out the Mega-Guide All about HTC One Dual Sim and the Collection of HTC One Dual Sim RUU, OTA, Firmware, etc..

majmoz said:
See answers in Magenta. You should check out the Mega-Guide All about HTC One Dual Sim and the Collection of HTC One Dual Sim RUU, OTA, Firmware, etc..
Click to expand...
Click to collapse
hello again.
Yesterday I could finally install the maximushd 1.0 as the 3.0 but in both cases when phone restarted, it made a boot loop again. Might be corrupt the hboot? There is way to fix it? another idea? Thank you

majmoz said:
See answers in Magenta. You should check out the Mega-Guide All about HTC One Dual Sim and the Collection of HTC One Dual Sim RUU, OTA, Firmware, etc..
Click to expand...
Click to collapse
pdelmazo said:
hello again.
Yesterday I could finally install the maximushd 1.0 as the 3.0 but in both cases when phone restarted, it made a boot loop again. Might be corrupt the hboot? There is way to fix it? another idea? Thank you
Click to expand...
Click to collapse
Hi...
Finally I flash the boot.img boot with a RUU for my HTC.
Now the phone starts, passes the first HTC screen and tries to show the desktop but goes black .... can only see the top bar with the time and the GSM signal ... then it reboots again.
I dont know what else to do....
Plaese Help Me!!!!
Thanks

pdelmazo said:
Hi...
Finally I flash the boot.img boot with a RUU for my HTC.
Now the phone starts, passes the first HTC screen and tries to show the desktop but goes black .... can only see the top bar with the time and the GSM signal ... then it reboots again.
I dont know what else to do....
Plaese Help Me!!!!
Thanks
Click to expand...
Click to collapse
This is a long shot but first I would try to flash the stock firmware 4.22.707.3. You will need to lock your bootloader first. This firmware will wipe your personnal data from the phone.
First, download the firmware file and rename it firmware.zip and place in your adb/fastboot folder.
Second, relock you phone using this command:
Code:
fastboot oem lock
Third, use the following procedure to flash the stock firmware to your phone:
Code:
fastboot reboot-bootloader
After that, type:
Code:
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:
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:
fastboot reboot

majmoz said:
This is a long shot but first I would try to flash the********* You will need to lock your bootloader first. This firmware will wipe your personnal data from the phone.
First, download the firmware file and rename it firmware.zip and place in your adb/fastboot folder.
Second, relock you phone using this command:
Code:
fastboot oem lock
Third, use the following procedure to flash the stock firmware to your phone:
Code:
fastboot reboot-bootloader
After that, type:
Code:
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:
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:
fastboot reboot
Click to expand...
Click to collapse
that was amazing !!!!!
It really works !!! I only doubt is .... I can not seem to turn on the wifi .... how do I fix it? or you install the MaximusHD now ....?
Can I pay you for your help? I would like to do
I will waiting

pdelmazo said:
that was amazing !!!!!
It really works !!! I only doubt is .... I can not seem to turn on the wifi .... how do I fix it? or you install the MaximusHD now ....?
Can I pay you for your help? I would like to do
I will waiting
Click to expand...
Click to collapse
Thanks is enough for helping you out.
Wifi might be a software issue, with the new firmware you got the latest radio for your phone. If you still have the stock rom installed you could try the OTA update? If the rom is stock and the recovery is stock you could rename (to shorten it) and move the OTA to your sdcard. When it is on your sdcard, follow these steps for installing the OTA manually. It may or may not run, but if it fails it will tell you why it failed and maybe we can fix it.

majmoz said:
Thanks is enough for helping you out.
Wifi might be a software issue, with the new firmware you got the latest radio for your phone. If you still have the stock rom installed you could try the OTA update? If the rom is stock and the recovery is stock you could rename (to shorten it) and move the OTA to your sdcard. When it is on your sdcard, follow these steps for installing the OTA manually. It may or may not run, but if it fails it will tell you why it failed and maybe we can fix it.
Click to expand...
Click to collapse
Hi....
The phone has installed Android 4.4.2, HTC Sence 6.0 from MaximusHD 3.0
Should I also install this OTA?

pdelmazo said:
Hi....
The phone has installed Android 4.4.2, HTC Sence 6.0 from MaximusHD 3.0
Should I also install this OTA?
Click to expand...
Click to collapse
No, there is no stock rom for your phone! So, you can not go back to stock to get the OTA. Make a nandroid backup while in recovery and save it to your computer should something go amiss in the future. Glad to see you are back up and running.
Go to your first post and edit the title with "[Solved]".

majmoz said:
No, there is no stock rom for your phone! So, you can not go back to stock to get the OTA. Make a nandroid backup while in recovery and save it to your computer should something go amiss in the future. Glad to see you are back up and running.
Go to your first post and edit the title with "[Solved]".
Click to expand...
Click to collapse
Ok I'll do it ... thank you very much for everything.
So I can not do anything to solve the problem wifi?

pdelmazo said:
Ok I'll do it ... thank you very much for everything.
So I can not do anything to solve the problem wifi?
Click to expand...
Click to collapse
What specifically is wrong with wifi?
Are you getting data?
Does SMS/MMS work?
No issues with calls?
Have you tried rebooting the phone?

majmoz said:
What specifically is wrong with wifi?
Are you getting data?
Does SMS/MMS work?
No issues with calls?
Have you tried rebooting the phone?
Click to expand...
Click to collapse
Yes, I have restarted the phone twice but no Wifi on when I touch the button. Nor have 3G / H + data.
Calls and SMS work fine.
Should I reinstall ROM?

pdelmazo said:
Yes, I have restarted the phone twice but no Wifi on when I touch the button. Nor have 3G / H + data.
Calls and SMS work fine.
Should I reinstall ROM?
Click to expand...
Click to collapse
Yes, re-install the ROM and while in recovery wipe cache/dalvik. And check your APN settings against the APN settings for your carrier.

majmoz said:
Yes, re-install the ROM and while in recovery wipe cache/dalvik. And check your APN settings against the APN settings for your carrier.
Click to expand...
Click to collapse
Hi friend, i'm here again.
I had to reflash my phone with help from llabtoofer.com
We were able to fix the Wifi but the phone does not work on 3G network... only on EDGE.
Could be a problem with the Firmware or with the Radio?
I just called the telephone's company and they said that APN configuration was ok. If you want, I can send you a copy.
I'm in Argentina, Latin America.... perhaps the ROM installed is from Europe or perhaps is not compatible with my M7C_DWG.
Can you help me one more time?
Thanks.... I will waiting.

pdelmazo said:
Hi friend, i'm here again.
I had to reflash my phone with help from llabtoofer.com
We were able to fix the Wifi but the phone does not work on 3G network... only on EDGE.
Could be a problem with the Firmware or with the Radio?
I just called the telephone's company and they said that APN configuration was ok. If you want, I can send you a copy.
I'm in Argentina, Latin America.... perhaps the ROM installed is from Europe or perhaps is not compatible with my M7C_DWG.
Can you help me one more time?
Thanks.... I will waiting.
Click to expand...
Click to collapse
An earlier post stated that you had MaximusHD 3.0 installed. According to the website it doesn't support your phone! However, your software information has just the stock rom not MaximusHD 3.0. I don't thing there is an RUU for your phone so if you can find someone with a nandroid backup that you could use it would help. If you could get the stock firmware and flash it. Sorry, I'm not much help.

majmoz said:
An earlier post stated that you had MaximusHD 3.0 installed. According to the website it doesn't support your phone! However, your software information has just the stock rom not MaximusHD 3.0. I don't thing there is an RUU for your phone so if you can find someone with a nandroid backup that you could use it would help. If you could get the stock firmware and flash it. Sorry, I'm not much help.
Click to expand...
Click to collapse
Ok, thank you very much.
I will keep looking for a solution.... When I have it, I'll let you know.
Thaks.

[Q] stuck in boot loop

General Details:
HTC One M7 Verizon, rooted, S-Off, TWRP 2.8.6.0
I had been running stock rom but rooted and got S-Off. Recently updated to TWRP 2.8.6.0. Still worked at this point.
Downloaded Android Revolution HD 91.1 and attempted install. Everything said it was successful, rebooted into a boot loop.
When it starts it vibrates (one short buzz) , then comes up to the initial HTC logo with the text at the bottom about it being a dev build, 31 seconds later, screen goes black, 4 seconds later this process starts over. I am able to use volume down + power buttons to get to the bootloader, then go into fastboot mode, load twrp recovery, etc.
Here's what I've tried so far:
Variations on wiping partitions, dalvik cache, everything, formating everything, etc.
Tried reinstalling the AR HD 91.1 zip, installed AR HD 84.0, installed AR HD 6.1 Google Edition, Installed Stock ROM from AR.
All to no avail. I'm downloading and installing android sdk now. Starting to think the issue is a firmware difference between what's on the phone and what ROM needs.
Here's what bootloader shows me:
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.57.0000
RADIO-1.13.41.0421
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Apr 22 2014, 18:03:29.22981
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
fastboot getvar all returns:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: 000000000000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
google search has been little help.
So...any thoughts?

Try reverting to an older version of TWRP. I had the same thing happen this morning and I just reverted now everything works fine.

muguly said:
Try reverting to an older version of TWRP. I had the same thing happen this morning and I just reverted now everything works fine.
Click to expand...
Click to collapse
Which version did you revert to? So far I've tried 2.7.1.1 and 2.7.0.1 to no avail.

archanoid said:
Which version did you revert to? So far I've tried 2.7.1.1 and 2.7.0.1 to no avail.
Click to expand...
Click to collapse
2.7.1.2

muguly said:
2.7.1.2
Click to expand...
Click to collapse
I installed 2.7.1.2 via fastboot flash recovery
then I tried re-installing the ARHD 91.1 ROM (which it said it did successfully) but the same problem continues.

archanoid said:
I installed 2.7.1.2 via fastboot flash recovery
then I tried re-installing the ARHD 91.1 ROM (which it said it did successfully) but the same problem continues.
Click to expand...
Click to collapse
Does ARHD supports the Verizon variant? And is your phone running the latest firmware?

alray said:
Does ARHD supports the Verizon variant? And is your phone running the latest firmware?
Click to expand...
Click to collapse
It's a specific ROM for the verizon variant so I'd say yes to the first question.
Now, I'm not 100% sure on this but I wasn't sure how to check the firmware version. I searched (googled) for how to tell and found a line saying the "version-main" line from a "fastboot getvar all" tells you the firmware version. When I issue a "fastboot getvar all" the version-main line is blank. Might that indicate I have no firmware on my phone?

archanoid said:
It's a specific ROM for the verizon variant so I'd say yes to the first question.
Now, I'm not 100% sure on this but I wasn't sure how to check the firmware version. I searched (googled) for how to tell and found a line saying the "version-main" line from a "fastboot getvar all" tells you the firmware version. When I issue a "fastboot getvar all" the version-main line is blank. Might that indicate I have no firmware on my phone?
Click to expand...
Click to collapse
version-main is sometime blank because of twrp, that doesn't mean you don't have a firmware.

alray said:
version-main is sometime blank because of twrp, that doesn't mean you don't have a firmware.
Click to expand...
Click to collapse
Okay so I just read a bunch about flashing firmwares. So I changed my CID to 11111111 and grabbed a custom 7.19.401.22 firmware from another thread here on xda, ran a fastboot oem rebootRUU (got the black screen with silver htc logo) then tried the fastboot flash zip firmware.zip and it gives me this every time:
FAILED (remote: 41 model id check fail)
Any pointers on figuring out what firmware I should be running for my phone?

archanoid said:
It's a specific ROM for the verizon variant so I'd say yes to the first question.
Click to expand...
Click to collapse
Can you give a link, not saying youre wrong, but I can't find this information, just to be sure. I thought ARHD was for M7_UL and M7_U only...
archanoid said:
Okay so I just read a bunch about flashing firmwares. So I changed my CID to 11111111 and grabbed a custom 7.19.401.22 firmware from another thread here on xda, ran a fastboot oem rebootRUU (got the black screen with silver htc logo) then tried the fastboot flash zip firmware.zip and it gives me this every time:
FAILED (remote: 41 model id check fail)
Click to expand...
Click to collapse
7.19.401.22 is WWE version for PN0712000 MID
Any pointers on figuring out what firmware I should be running for my phone?
Click to expand...
Click to collapse
If a specific firmware is required, it should be mentioned in the rom thread. My guess is that if your phone is Verizon and the rom is for Verizon then update to the latest verizon firmware. Meanwhile you could try to wipe everything from twrp + formate data. Reboot the recovery and push the rom to your phone and try to flash it again. Also worth trying another rom.

alray said:
Can you give a link, not saying youre wrong, but I can't find this information, just to be sure. I thought ARHD was for M7_UL and M7_U only...
Click to expand...
Click to collapse
I got it from here: http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
I thought I saw something that said it would work on verizon phone but I could be wrong about that. May have to pick a different ROM.
alray said:
...then update to the latest verizon firmware
Click to expand...
Click to collapse
I'm trying to do that now but having a hell of a time figuring out what firmware that is and where to get it.
(Thanks again for your help, btw)

archanoid said:
I got it from here: http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
I thought I saw something that said it would work on verizon phone but I could be wrong about that. May have to pick a different ROM.
I'm trying to do that now but having a hell of a time figuring out what firmware that is and where to get it.
(Thanks again for your help, btw)
Click to expand...
Click to collapse
You should try flashing a verizon rom from the verizon section

alray said:
You should try flashing a verizon rom from the verizon section
Click to expand...
Click to collapse
I just downloaded NuSenSeveN and am going to try it and see if it works. I'll let you know.

Lo and Behold!
Installing NuSenSeveN ROM worked. Guess ARHD doesn't like VZW phones. Sorry to have wasted anyone's time.

archanoid said:
Installing NuSenSeveN ROM worked. Guess ARHD doesn't like VZW phones. Sorry to have wasted anyone's time.
Click to expand...
Click to collapse
learning is not wasted time

True. Plus hopefully if anyone else makes the same mistake as me they'll find this thread and save themselves a lot of time/heartache figuring out what's up.
Thanks again for all help. This place is great.

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