Database Develop

[Recovery]5.0.1 Google Play Edition Stock Recovery + Bootloader + Firmware

Thanks to @pasker17 this wouldn't have been possible without him and his device!
Stock Recovery(Unlocked bootloader required. S-off not needed)
To flash boot into fastboot (either by adb reboot bootloader or holding down volume down and power when device is off) and run the command
fastboot flash recovery recoverygpe.img
GPE Bootloader & Splash Screen (to be flashed in RUU Mode S-off required)
To flash boot into fastboot (either by adb reboot bootloader or holding down volume down and power when device is off) and run the command
Once in bootloader type fastboot oem RebootRUU once at the HTC logo screen (RUU Mode) run
fastboot flash zip zipfilename.zip
All files can be downloaded from my website http://www.graffixnyc.com/m8.php
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, or flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. I am not responsible.... It was the other guy... I swear....

added bootloader and splash screen to OP

Is there a thread describing the installation process and pre-requisites?

I assume flashing this bootloader on normal m8 will result in GE dark bootloader?
Sent from my Viper One

@graffixnyc Would this be ok to flash on an Att m8

I'm sorry if this is a retarded question. But what is the difference between flashing this ROM --> http://forum.xda-developers.com/showthread.php?t=2706441 and using the recovery from this thread?

graffixnyc,sent you a general question via pm if you get a minute

Will this work on my M8?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.21331831.A05G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.22.980.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
----------------------------------------------------------------
Viper OneM8 + ElementX

If I change one of MID's to mine will it flash properly, without any adverse effects?
Sent from my HTC One_M8 using Tapatalk

Within the 'android-info.txt' file that is
Pushed from my Freed Viper OneM8

Will it have any adverse effect on Att devices?
Sent from my HTC One_M8 using xda app-developers app

graffixnyc said:
Thanks to @pasker17 this wouldn't have been possible without him and his device!
Stock Recovery(Unlocked bootloader required. S-off not needed)
To flash boot into fastboot (either by adb reboot bootloader or holding down volume down and power when device is off) and run the command
fastboot flash recovery recoverygpe.img
Link: http://www.androidfilehost.com/?fid=23329332407584495
Mirror: http://d-h.st/nMe
GPE Bootloader & Splash Screen (to be flashed in RUU Mode S-off required)
To flash boot into fastboot (either by adb reboot bootloader or holding down volume down and power when device is off) and run the command
Once in bootloader type fastboot oem RebootRUU once at the HTC logo screen (RUU Mode) run
fastboot flash zip zipfilename.zip
[/SIZE][/COLOR]
Click to expand...
Click to collapse
Installed the gpe recovery, adb said installed ok. If I boot into bootloader then recovery I get the dead android icon which stays on screen for 1 minute then the phone reboots
Secondly the command to fastboot oem RebootRUU gives
ERR command error?
Phone is unlocked, Rooted, S-off and Super CID

grentuu said:
Installed the gpe recovery although no recovery is showing after installing even though it said success.
Secondly the command to fastboot oem RebootRUU gives
ERR command error?
Phone is unlocked, Rooted, S-off and Super CID
Click to expand...
Click to collapse
the stock recovery requires a button press to show once the android is on ur screen, i think its vol up+pwr or vol dwn+pwr
also the command is fastboot oem rebootRUU it is case specific.

djkinetic said:
the stock recovery requires a button press to show once the android is on ur screen, i think its vol up+pwr or vol dwn+pwr
also the command is fastboot oem rebootRUU it is case specific.
Click to expand...
Click to collapse
Recovery sorted but the RebootRUU wont work and I have been case specific forget it... I see the error. Thank you. Will try now
---------- Post added at 06:04 PM ---------- Previous post was at 05:54 PM ----------
grentuu said:
Recovery sorted but the RebootRUU wont work and I have been case specific forget it... I see the error. Thank you. Will try now
Click to expand...
Click to collapse
I dumbly followed the instructions on page one which says RebootRUU lol. I should know better

If we flash this can we ever go back to sense? And do we need to wipe data after we flash?
Sent from my HTC One_M8 using xda app-developers app

bpdev said:
@graffixnyc Would this be ok to flash on an Att m8
Click to expand...
Click to collapse
I too would like to know this. I wouldn't mind the dark splash screen but want to make sure there are new ill effects.
Sent from my HTC One_M8

REDFOCZ said:
I too would like to know this. I wouldn't mind the dark splash screen but want to make sure there are new ill effects.
Sent from my HTC One_M8
Click to expand...
Click to collapse
I flashed then to my AT&T m8,but upon boot it sat at the splash screen. I booted into recovery and it said I didn't have an OS installed to /system. So I had to flash the GPE RUU to get back going.
Sent from my HTC One_M8 using xda app-developers app

wera750 said:
I flashed then to my AT&T m8,but upon boot it sat at the splash screen. I booted into recovery and it said I didn't have an OS installed to /system. So I had to flash the GPE RUU to get back going.
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Oh wow, thanks for the heads up. I'm not sure if I'm ready to convert to a Gpe device just yet. I'll stick with what I have.
Sent from my HTC One_M8

WreckTangle said:
I assume flashing this bootloader on normal m8 will result in GE dark bootloader?
Sent from my Viper One
Click to expand...
Click to collapse
I thought it would, but I believe the system partition is smaller. I flashed it thinking I could have dark boot loader with my sense ROM, but it wiped my phone and I couldn't install venom back on my device, and it wouldn't boot. Finally thought it might be boot loader related so when I flashed back it worked again. But even with hboot back to the Dev hboot it says version 3.16 or whatever the gpe boot loader version is.
Sent from my HTC One_M8 using Tapatalk

Is 3.16 the hboot version on all HTC m8s? I may have been mistaken in my previous post
Sent from my HTC One_M8 using Tapatalk

[Q] HTC One Stuck in Bootloader! (HELP)

So my htc one is stuck in what i think you call the boot loader. I powered it off the other day and now it is stuck in the boot loader. Every button I click on the boot loader always brings me back to the boot loader. I have rooted my phone and it is unlocked with s on and running a custom rom. I don't know what to do because it won't load into the rom and all it does is keep going back to the boot loader any help would be greatly appreciated.

aidanbern said:
So my htc one is stuck in what i think you call the boot loader. I powered it off the other day and now it is stuck in the boot loader. Every button I click on the boot loader always brings me back to the boot loader. I have rooted my phone and it is unlocked with s on and running a custom rom. I don't know what to do because it won't load into the rom and all it does is keep going back to the boot loader any help would be greatly appreciated.
Click to expand...
Click to collapse
What rom?
Clear cache and dalvik cache from recovery and try to boot

aidanbern said:
So my htc one is stuck in what i think you call the boot loader. I powered it off the other day and now it is stuck in the boot loader. Every button I click on the boot loader always brings me back to the boot loader. I have rooted my phone and it is unlocked with s on and running a custom rom. I don't know what to do because it won't load into the rom and all it does is keep going back to the boot loader any help would be greatly appreciated.
Click to expand...
Click to collapse
Relock and flash back to stock if the above suggestion dies not help.

You should be more specific on your problem and what you've been doing with it in the past week. Then we'll be glad to help you.
Sent from my HTCONE using xda app-developers app

aarongillion63 said:
You should be more specific on your problem and what you've been doing with it in the past week. Then we'll be glad to help you.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Hard to say what your issue is as you are vague on the rom and what you mean as in boot loader as people use it interchangeable with the boot screen and or the actually boot loader (Hboot) menu. Either way, Try to enter recovery (Power and volume down buttons at the same time and or hold volume down button as phone is restarting until you enter recovery). You should also enter fastboot and erase cache and restart and see if that works. Make sure the rom you have is Correct for your phone as well.

Truth6199 said:
Hard to say what your issue is as you are vague on the rom and what you mean as in boot loader as people use it interchangeable with the boot screen and or the actually boot loader (Hboot) menu. Either way, Try to enter recovery (Power and volume down buttons at the same time and or hold volume down button as phone is restarting until you enter recovery). You should also enter fastboot and erase cache and restart and see if that works. Make sure the rom you have is Correct for your phone as well.
Click to expand...
Click to collapse
Ok sorry I will try to be more specific this time. So the screen I'm in is the htc hot boot menu with the three android dude on the bottom and unlocked at the top of the screen. My phone has been rooted for a month or so and it's been fine running cyanogen mod (don't know what version). So my problem is I can not go anywhere but this menu every option I click always brings me back I the same menu with boot loader reboot reboot boo loader and power down. I can't get Into recovery or power up in my rom. And when I plug it in to charge it sows a charging symbol for a minute then it goes away and back to the menu. Help would be greatly appreciated thanks

aidanbern said:
Ok sorry I will try to be more specific this time. So the screen I'm in is the htc hot boot menu with the three android dude on the bottom and unlocked at the top of the screen. My phone has been rooted for a month or so and it's been fine running cyanogen mod (don't know what version). So my problem is I can not go anywhere but this menu every option I click always brings me back I the same menu with boot loader reboot reboot boo loader and power down. I can't get Into recovery or power up in my rom. And when I plug it in to charge it sows a charging symbol for a minute then it goes away and back to the menu. Help would be greatly appreciated thanks
Click to expand...
Click to collapse
so have you tried to clear cache and reboot? Or flash the rom again?

Inves
alray said:
so have you tried to clear cache and reboot? Or flash the rom again?
Click to expand...
Click to collapse
I can't get I the place to flash a new Rom idk how to clear cache though but I can't flash because I can't leave the menu

aidanbern said:
I can't get I the place to flash a new Rom idk how to clear cache though but I can't flash because I can't leave the menu
Click to expand...
Click to collapse
Code:
fastboot erase cache
fastboot reboot
then try to boot the phone, if its not booting to the OS try to boot in recovery. If not you'll have to flash the recovery
---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------
aidanbern said:
I can't get I the place to flash a new Rom idk how to clear cache though but I can't flash because I can't leave the menu
Click to expand...
Click to collapse
also post the output of
Code:
fastboot getvar all
except IMEI and SERIALNO

alray said:
Code:
fastboot erase cache
fastboot reboot
then try to boot the phone, if its not booting to the OS try to boot in recovery. If not you'll have to flash the recovery
Click to expand...
Click to collapse
It says command not found and I'm on Mac forgive me I'm not that good with this stuff used to iPhones and stuff

aidanbern said:
It says command not found and I'm on Mac forgive me I'm not that good with this stuff used to iPhones and stuff
Click to expand...
Click to collapse
then if you are on a mac, open a terminal windows, change directory to the folder where you have adb and fastboot.
Code:
./fastboot erase cache
./fastboot reboot
or
Code:
./fastboot-mac erase cache
./fastboot-mac reboot
depending if your fastboot is named ''fastboot'' or ''fastboot-mac''
anyway I don't understand why you don't know how to do these commands. You said in your 1st post you have unlocked your bootloader, rooted and flashed a custom rom... so you should know how to use fastboot and adb commands right?
---------- Post added at 04:54 PM ---------- Previous post was at 04:48 PM ----------
Here is a tutorial on how to install and use ADB/FASTBOOT for mac http://forum.xda-developers.com/showthread.php?t=1917237

alray said:
then if you are on a mac, open a terminal windows, change directory to the folder where you have adb and fastboot.
Code:
./fastboot erase cache
./fastboot reboot
or
Code:
./fastboot-mac erase cache
./fastboot-mac reboot
depending if your fastboot is named ''fastboot'' or ''fastboot-mac''
anyway I don't understand why you don't know how to do these commands. You said in your 1st post you have unlocked your bootloader, rooted and flashed a custom rom... so you should know how to use fastboot and adb commands right?
Click to expand...
Click to collapse
Umm my dab files are not on my computer is there any way to get them to my computer.

http://forum.xda-developers.com/showthread.php?t=1917237

alray said:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Thanks south for the help so far tonight I am going to try all the suggestions and I will tell you if the work thanks alot

aidanbern said:
It says command not found and I'm on Mac forgive me I'm not that good with this stuff used to iPhones and stuff
Click to expand...
Click to collapse
Now i do not think my computer recognizes that my phone is plugged in because i can not get my device to show up when i put in ./adb devices
? maybe it does not think my phone is actually plugged in?

alray said:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
So when i enter the ./adb devices my phone does not show up i think maybe my computer doesn't recognize that my phone is connected to the computer?

alray said:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 0.027s
did not work… and the reboot just boots me back to the same menu.

alray said:
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.19.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.32.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5822000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3969mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5cc83deb4d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

aidanbern said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.19.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.32.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid:
(bootloader) product: m4_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PO5822000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3969mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5cc83deb4d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
you have a htc one mini .. the files here will brick your phone
find the correct recovery and rom for your phone here
http://forum.xda-developers.com/htc-one-mini
your should be able to RUU your phone back to working here's the files
http://www.androidruu.com/index.php?developer=M4
Get the RUU not the OTA updates

clsA said:
you have a htc one mini .. the files here will brick your phone
find the correct recovery and rom for your phone here
http://forum.xda-developers.com/htc-one-mini
your should be able to RUU your phone back to working here's the files
http://www.androidruu.com/index.php?developer=M4
Get the RUU not the OTA updates
Click to expand...
Click to collapse
Ok so is there a tutorial for doing an ruu I have never done It that way? And is a recovery different from the rom if so what's the difference and what are the files I need for the ruu I'm sort of confused hhaha forgive me not to experinced in this

[Q] Trying to put stock recovery back for OTA 5.11.1540.9

Hi Guys,
Hope that anyone can help me with the following:
I normally have Openrecovery-twrp-2.6.3.3-m7 running on my M7.
However, with the new software update of 5.11.1540.9 pushed out, I normally go back to original recover, then update my software by downloading it an installing on the phone.
A couple of months ago I changed my version, originally an ATT phone, to I think a European or WWE version. I am not sure anymore.
Anyway, when I try to flash the original recovery ecovery_Cingular_US_3.17.502.3.img back and reboot in to recovery I get a black screen and eventually a phone icon with exclamation mark.
After holding the power button for a while, I can reboot and get back in the phone or restore TWRP.
My question is, does anyone know how to get the original recovery working again so that I can run the update.
This is the info of the bootloader:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1540.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 111111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(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
I rather do not wipe the whole device if I don't have to. Before I changed the firmware to European or WWE I was able to restore the original bootloader at leisure. So I think it would be best to go back to the correct country firmware, or find a recovery file that does work with my current firmware.
If I can install the latest Developer Edition ROM with TWRP, and have to wipe, that is fine. I don't want to risk bricking my phone with doing all kind of updates. Have done so many and it is still working, would hope to keep it that way
Any help appreciated.

I thought all you needed to do was re-lock the bootloader, then run the correct RUU file for your phone.
I do not remember having to flash back to stock recovery when I ran RUU for the latest update - I just relocked the bootloader. After the RUU is run, you will be back on stock recovery

mike-y said:
I thought all you needed to do was re-lock the bootloader, then run the correct RUU file for your phone.
I do not remember having to flash back to stock recovery when I ran RUU for the latest update - I just relocked the bootloader. After the RUU is run, you will be back on stock recovery
Click to expand...
Click to collapse
Well, last time it worked for me when I had the Dev edition. My phone was unlocked with S-On, and I had TWRP for recovery.
I remember receiving the OTA, installing it and then seeing the message in TWRP that it couldn't install.
I then set the Recovery_Cingular_US_3.17.502.3.img for recovery and I was able to install the OTA.
After that I went back to TWRP.
Couple of months ago I set my CID to 11111111 and S-off and I installed, I believe a european version or a WWE version (not sure anymore what i did ) to get a radio that might unlock 4G here in Australia (which failed cause of hardware restrictions of bands).
Anyway, my phone works fine and I received the OTA but I can't repeat the back to stock recovery trick cause after flashing the Recovery_Cingular_US_3.17.502.3.img it doesnt enter recovery. Probably something to do with my WWE or Euro firmware?
What does relock mean in this case.
I also am at loss at what the correct RUU is. Is RUU firmware, or a whole complete ROM?
Can you see from my bootloader info what version I have and should consider?
I am just a bit confused with all the terms and was quite into it a couple of months ago, but now its a blur.

You don't need relock boot loader
When you boot in recovery got exclamation mark press volume up for4-5 sec then press power upto home back light blinks leave power button you got recovery with blue options
from HTC One

yatindroid said:
You don't need relock boot loader
When you boot in recovery got exclamation mark press volume up for4-5 sec then press power upto home back light blinks leave power button you got recovery with blue options
from HTC One
Click to expand...
Click to collapse
Well I tried your suggestion but it doesnt work. After I hold the power button when seeing the exclamation mark, the phone finally reboots. It tried to install the OTA this way, but it doesnt work.
I think the current recovery:Recovery_Cingular_US_3.17.502.3.img doesnt match my current firmware of something like that.
Any other suggestions?
Can I just install a fresh ROM with the latest version, not sure where to get it from.

Not really sure what to do, I tried another recovery but after choosing to install the OTA, and reboot, I see progress bar which ends up in red triangle.
Tried to lock bootloader but then of course I can go back to standard recovery using TWRP.
I just tried to install again and when progress bar appeared I hit volume up and then power button. Now I see status updates of the installation.
If fails while verifying the current system:
"/system/lib/libcryptox.so" has unexpected contents
Installation aborted.

mattileblanc said:
Not really sure what to do, I tried another recovery but after choosing to install the OTA, and reboot, I see progress bar which ends up in red triangle.
Tried to lock bootloader but then of course I can go back to standard recovery using TWRP.
I just tried to install again and when progress bar appeared I hit volume up and then power button. Now I see status updates of the installation.
If fails while verifying the current system:
"/system/lib/libcryptox.so" has unexpected contents
Installation aborted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2791123
from HTC One

[Q] HTC ONE (M7UL) imei problems + rebooting + s-on

Hi you all,
So to start things off i might say i tried alot of things to revive my htc one.
What happenend?
I wanted to give my htc one some new life so I thought lets factory reset it. All worked well but then the horror just began. My One began rebooting and rebooting itself over and over. So what i did next was enabled flight mode throught the power button and restarted the phone. So from then on it was running for about 30 seconds untill it starts rebooting again.
So what I did is unlock the phone and tried several Custom Roms. The only ones working are old cm11 roms, but I can not get S-Off to reflash the firmware because I am stuck with an eMMC 9001xxxxx... chip, so I guess bad luck for me.
So now my phone will not detect ANY SIM Card and will not show any imei number or baseband in the os. In the bootloader however they are still there, both of them.
RUU's will not work for me as I am S-ON and stuck on hboot 1.57
SunShine is not working either as my phone shuts down after aprox. 30 seconds on sense rom.
Firewater is not working either as it has an 9001.... eMMC chip.
my getvar stats:
PHP:
(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: 6.09.401.10
(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__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3972mV
(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
So my question is are there still any suggestions for me, that I didn't do or just overlooked?
So I would appreciate anything, before tearing it apart..
Cheers

shieldeverything said:
Hi you all,
So to start things off i might say i tried alot of things to revive my htc one.
What happenend?
I wanted to give my htc one some new life so I thought lets factory reset it. All worked well but then the horror just began. My One began rebooting and rebooting itself over and over. So what i did next was enabled flight mode throught the power button and restarted the phone. So from then on it was running for about 30 seconds untill it starts rebooting again.
So what I did is unlock the phone and tried several Custom Roms. The only ones working are old cm11 roms, but I can not get S-Off to reflash the firmware because I am stuck with an eMMC 9001xxxxx... chip, so I guess bad luck for me.
So now my phone will not detect ANY SIM Card and will not show any imei number or baseband in the os. In the bootloader however they are still there, both of them.
RUU's will not work for me as I am S-ON and stuck on hboot 1.57
SunShine is not working either as my phone shuts down after aprox. 30 seconds on sense rom.
Firewater is not working either as it has an 9001.... eMMC chip.
my getvar stats:
PHP:
(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: 6.09.401.10(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__102(bootloader) battery-status: good(bootloader) battery-voltage: 3972mV(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
So my question is are there still any suggestions for me, that I didn't do or just overlooked?
So I would appreciate anything, before tearing it apart..
Cheers
Click to expand...
Click to collapse
You don't need s-off to flash firmware. You only need s-off to downgrade or to use custom firmware. You will however need to relock your bootloader. Although I should tell you Unknown imei & Baseband often turns out to be a hardware problem.
You can flash this firmware with a relocked bootloader. You will need to 're flash custom recovery and Rom to boot the phone afterwards. Unless you flash a stock Rom first, Stock Rom can be downloaded here http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
Firmware download
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.10.zip
Download it and put it in your fastboot folder and rename it firmware.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
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
If you found my posts helpful, no need to say thanks. There's a button for that

Danny201281 said:
You don't need s-off to flash firmware. You only need s-off to downgrade or to use custom firmware. You will however need to relock your bootloader. Although I should tell you Unknown imei & Baseband often turns out to be a hardware problem.
You can flash this firmware with a relocked bootloader. You will need to 're flash custom recovery and Rom to boot the phone afterwards. Unless you flash a stock Rom first, Stock Rom can be downloaded here http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
Firmware download
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/6.09.401.10.zip
Download it and put it in your fastboot folder and rename it firmware.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
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
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
Ok cheers m8!
I am gonna try it right now. Yeah I heard about the hardware problem, but I was thinking mine might be not because it happened after a factory reset (done in the os itself). I once was able to bring back baseband and imei but I just can't remember what exactely I did.
So I am going to report back as soon as I tried. I am wondering.
Btw you know what hardware defect actually would cause it (just wondering)
Thx!

shieldeverything said:
Ok cheers m8!
I am gonna try it right now. Yeah I heard about the hardware problem, but I was thinking mine might be not because it happened after a factory reset (done in the os itself). I once was able to bring back baseband and imei but I just can't remember what exactely I did.
So I am going to report back as soon as I tried. I am wondering.
Btw you know what hardware defect actually would cause it (just wondering)
Thx!
Click to expand...
Click to collapse
With your phone s-on and on the latest firmware there's not much else you can do but flash the firmware package I linked. If you can get s-off you can try an ruu.
From a hardware perspective It's the antenna connector pin that causes the issue as far as I'm aware. I only know of one that was repaired without returning to HTC and the antenna connector pin was the cause. Replacing it solved the problem.
If you found my posts helpful, no need to say thanks. There's a button for that

Danny201281 said:
With your phone s-on and on the latest firmware there's not much else you can do but flash the firmware package I linked. If you can get s-off you can try an ruu.
From a hardware perspective It's the antenna connector pin that causes the issue as far as I'm aware. I only know of one that was repaired without returning to HTC and the antenna connector pin was the cause. Replacing it solved the problem.
If you found my posts helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
So I did everything and it worked. But only for 5-10 minutes and then it startet rebooting again and again. So I guess this is a hardware problem too and as I don't have any warranty or something there my m7ul goes...
Thx for your help anyways!

Help please. Phone started boot looping

Hi guys,
A few days ago my phone started crashing after bout 10 seconds of getting to the android home screen. It literally didn't stop so i thought it might be smart to do a factory restore. That wiped everything but the boot/crashes still occurred. Now i'm stuck and don't know what to do. All the videos i've watched don't seem to match up with my issue and the fixes don't work. I've uploaded a video to show you what is happening.
I would be extremely grateful for any help or advice
With thanks
James

The flashing lights are normal when it comes to doing a hard reboot. You can unlock your bootloader as long as it isn't a Verizon model over on HTC's Dev website, it will tell you everything you need and the instructions. That will allow you to flash a custom recovery, such as TWRP. To flash that recovery after unlocking your bootloader, make sure you are in Fastboot and in the fastboot prompt on your PC/Mac type fastboot flash recovery recovery-name.img. From there, you can look around at the custom roms on this forum and see if anything suits you. If you prefer stock android then there are Lollipop and a few Marshmallow builds, if you prefer Sense 6/7 there's some builds for that as well. I'm going to be leaving and busy here for about 2-3 hours but when I get back if you need more assistance feel free to let me know on here.

jamesdf5 said:
Hi guys,
A few days ago my phone started crashing after bout 10 seconds of getting to the android home screen. It literally didn't stop so i thought it might be smart to do a factory restore. That wiped everything but the boot/crashes still occurred. Now i'm stuck and don't know what to do. All the videos i've watched don't seem to match up with my issue and the fixes don't work. I've uploaded a video to show you what is happening.
I would be extremely grateful for any help or advice
With thanks
James
Click to expand...
Click to collapse
It looks like a recovery issue. Can you get it to bootloader menu? Hold power + vol down till it enters bootloader
dey tuuk ur juurbs

fireball0093 said:
The flashing lights are normal when it comes to doing a hard reboot. You can unlock your bootloader as long as it isn't a Verizon model over on HTC's Dev website, it will tell you everything you need and the instructions. That will allow you to flash a custom recovery, such as TWRP. To flash that recovery after unlocking your bootloader, make sure you are in Fastboot and in the fastboot prompt on your PC/Mac type fastboot flash recovery recovery-name.img. From there, you can look around at the custom roms on this forum and see if anything suits you. If you prefer stock android then there are Lollipop and a few Marshmallow builds, if you prefer Sense 6/7 there's some builds for that as well. I'm going to be leaving and busy here for about 2-3 hours but when I get back if you need more assistance feel free to let me know on here.
Click to expand...
Click to collapse
Hi,
Thanks for the reply
The first thing i tried was unlocking the bootloader but my PC couldnt see the phone. I'll have to try again later and let you know

donkeykong1 said:
It looks like a recovery issue. Can you get it to bootloader menu? Hold power + vol down till it enters bootloader
dey tuuk ur juurbs
Click to expand...
Click to collapse
Thanks for replying. Yes i can get into bootloader

jamesdf5 said:
Thanks for replying. Yes i can get into bootloader
Click to expand...
Click to collapse
When you're in bootloader and you connect your phone to your PC, does it say fastboot usb on the phone?
dey tuuk ur juurbs

fireball0093 said:
The flashing lights are normal when it comes to doing a hard reboot. You can unlock your bootloader as long as it isn't a Verizon model over on HTC's Dev website, it will tell you everything you need and the instructions.
Click to expand...
Click to collapse
His bootloader his already unlocked see video @ 3:00, and that unlocked bootloader most likely caused the ota update to fail an so the bootloop (see video @ 0:49) (unlocking the bootloader = wipes /data/preload = ota will fail).
donkeykong1 said:
When you're in bootloader and you connect your phone to your PC, does it say fastboot usb on the phone?
Click to expand...
Click to collapse
Yep see video @ 3:00. So its the 1.44 + Win 8/10 incompatibility issue.
jamesdf5 said:
Hi,
The first thing i tried was unlocking the bootloader but my PC couldnt see the phone. I'll have to try again later and let you know
Click to expand...
Click to collapse
Its already unlocked as you can see from your bootloader screen ***UNLOCKED***
I guess you are using a Windows 8 or 10 PC? This is the reason why your PC doesn't detect your phone. It still running the old 1.44 Hboot version which isn't compatible with Win 8/10 for fastboot commands. Btw USB debugging on/off doesn't matters for using fastboot commands in bootloader or for using adb commands when in a custom recovery, its only needed to use adb commands from a booted rom. The simplest solution would be to get your hands on a Win 7 PC, install adb/fastboot and the drivers, and post the output of "fastboot getvar all" (don't post your imei / sn). Your phone is running a pretty old version, I'm sure we'll be able to find a RUU or a Guru reset rom to restore your phone back to stock.

alray said:
His bootloader his already unlocked see video @ 3:00, and that unlocked bootloader most likely caused the ota update to fail an so the bootloop (see video @ 0:49) (unlocking the bootloader = wipes /data/preload = ota will fail).
Yep see video @ 3:00. So its the 1.44 + Win 8/10 incompatibility issue.
Its already unlocked as you can see from your bootloader screen ***UNLOCKED***
I guess you are using a Windows 8 or 10 PC? This is the reason why your PC doesn't detect your phone. It still running the old 1.44 Hboot version which isn't compatible with Win 8/10 for fastboot commands. Btw USB debugging on/off doesn't matters for using fastboot commands in bootloader or for using adb commands when in a custom recovery, its only needed to use adb commands from a booted rom. The simplest solution would be to get your hands on a Win 7 PC, install adb/fastboot and the drivers, and post the output of "fastboot getvar all" (don't post your imei / sn). Your phone is running a pretty old version, I'm sure we'll be able to find a RUU or a Guru reset rom to restore your phone back to stock.
Click to expand...
Click to collapse
Thanks for your reply. Really helpful. I am using windows 10 but thankfully I have a windows 7 laptop that is stuck in an update loop . So i'm now using the laptop and have unlocked the bootloader. (I didnt have an unlocked bootloader, the image on the video i uploaded was just a screenshot of an example).
So now i'm at the unlocked bootloader stage. I now need to know what order to do things next. The phone is still bootlooping.
Using the laptop the bootloop screen now shows USB
Thanks again

donkeykong1 said:
When you're in bootloader and you connect your phone to your PC, does it say fastboot usb on the phone?
dey tuuk ur juurbs
Click to expand...
Click to collapse
It does now i've unlocked it. yes

jamesdf5 said:
It does now i've unlocked it. yes
Click to expand...
Click to collapse
Post a fastboot getvar all so we can tell you which RUU is for your phone. Be sure to delete your IMEI and serial no from the output before you post it
dey tuuk ur juurbs

donkeykong1 said:
Post a fastboot getvar all so we can tell you which RUU is for your phone. Be sure to delete your IMEI and serial no from the output before you post it
dey tuuk ur juurbs
Click to expand...
Click to collapse
Okie dokie thanks
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Chicken Korma
(bootloader) imei: Chocolate
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

jamesdf5 said:
Okie dokie thanks
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Chicken Korma
(bootloader) imei: Chocolate
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Latest firmware and s-on... Not good... There is no signed firmware for your phone, but there is a way to trick your phone to think it's on older firmware. @alray knows everything about that, so we'll have to wait for him to see this
dey tuuk ur juurbs

donkeykong1 said:
Latest firmware and s-on... Not good... There is no signed firmware for your phone, but there is a way to trick your phone to think it's on older firmware. @alray knows everything about that, so we'll have to wait for him to see this
dey tuuk ur juurbs
Click to expand...
Click to collapse
ok thank you :good:

jamesdf5 said:
Thanks for your reply. Really helpful. I am using windows 10 but thankfully I have a windows 7 laptop that is stuck in an update loop . So i'm now using the laptop and have unlocked the bootloader. (I didnt have an unlocked bootloader, the image on the video i uploaded was just a screenshot of an example).
So now i'm at the unlocked bootloader stage. I now need to know what order to do things next. The phone is still bootlooping.
Using the laptop the bootloop screen now shows USB
Thanks again
Click to expand...
Click to collapse
Sorry I thought the video was from you. So as I can see your phone isn't on hboot 1.44 so it should have worked fine with windows 10....
jamesdf5 said:
Okie dokie thanks
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.61.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Chicken Korma
(bootloader) imei: Chocolate
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Flash twrp recovery
Code:
fastboot flash recovery twrp-3.0.0-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot your phone in twrp main menu so you can use adb commands. You'll need to change your version-main number from 7.19.61.51 to 7.19.61.10 so you can flash the 7.19.61.10 RUU which is the latest one for this phone:
Code:
adb shell
echo -ne "7.19.61.10\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
**** Better to copy/paste the command starting with "echo -ne". A typo in this command could be really dangerous for your phone so make sure you do not make any mistake.
Once back in bootloader mode, do a "fastboot getvar all" again and confirm your version-main is now 7.19.61.10, If yes, relock your bootloader using "fastboot oem lock" and flash the 7.19.61.10 RUU. Dont forget you need to use the fastboot version linked in that thread to flash the RUU, it won't work with the standard fastboot version. Then when the ruu is flashed, your phone should boot normally, go through the initial setup screen and then download and install all the ota updates so you're back to 7.19.61.51.

alray said:
Sorry I thought the video was from you. So as I can see your phone isn't on hboot 1.44 so it should have worked fine with windows 10....
Click to expand...
Click to collapse
Yes it was my video but the bootloader image was a screenshot i found on Google cos my phone wasn't getting me to bootloader so I wanted to refer to it.
alray said:
Flash twrp recovery
Code:
fastboot flash recovery twrp-3.0.0-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot your phone in twrp main menu so you can use adb commands. You'll need to change your version-main number from 7.19.61.51 to 7.19.61.10 so you can flash the 7.19.61.10 RUU which is the latest one for this phone:
Code:
adb shell
echo -ne "7.19.61.10\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
**** Better to copy/paste the command starting with "echo -ne". A typo in this command could be really dangerous for your phone so make sure you do not make any mistake.
Once back in bootloader mode, do a "fastboot getvar all" again and confirm your version-main is now 7.19.61.10, If yes, relock your bootloader using "fastboot oem lock" and flash the 7.19.61.10 RUU. Dont forget you need to use the fastboot version linked in that thread to flash the RUU, it won't work with the standard fastboot version. Then when the ruu is flashed, your phone should boot normally, go through the initial setup screen and then download and install all the ota updates so you're back to 7.19.61.51.
Click to expand...
Click to collapse
Fab thanks i'll give this a go tomorrow. I'll let you know how i get on
Thanks
James

jamesdf5 said:
Yes it was my video but the bootloader image was a screenshot i found on Google cos my phone wasn't getting me to bootloader so I wanted to refer to it.
Fab thanks i'll give this a go tomorrow. I'll let you know how i get on
Thanks
James
Click to expand...
Click to collapse
PS definitely not recognised on my Windows 10. Won't see it at all.

jamesdf5 said:
PS definitely not recognised on my Windows 10. Won't see it at all.
Click to expand...
Click to collapse
Strange, keep using your w7 pc for now. Maybe a driver problem, or maybe you are using an usb 3.0 port instead of a 2.0?

alray said:
Sorry I thought the video was from you. So as I can see your phone isn't on hboot 1.44 so it should have worked fine with windows 10....
Flash twrp recovery
Code:
fastboot flash recovery twrp-3.0.0-0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Then boot your phone in twrp main menu so you can use adb commands. You'll need to change your version-main number from 7.19.61.51 to 7.19.61.10 so you can flash the 7.19.61.10 RUU which is the latest one for this phone:
Code:
adb shell
echo -ne "7.19.61.10\x00\x00" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
exit
adb reboot bootloader
**** Better to copy/paste the command starting with "echo -ne". A typo in this command could be really dangerous for your phone so make sure you do not make any mistake.
Once back in bootloader mode, do a "fastboot getvar all" again and confirm your version-main is now 7.19.61.10, If yes, relock your bootloader using "fastboot oem lock" and flash the 7.19.61.10 RUU. Dont forget you need to use the fastboot version linked in that thread to flash the RUU, it won't work with the standard fastboot version. Then when the ruu is flashed, your phone should boot normally, go through the initial setup screen and then download and install all the ota updates so you're back to 7.19.61.51.
Click to expand...
Click to collapse
Ok i got it working on my Windows 10.
I've just managed to flash the recovery image, cleared cache and rest. Thank you for the amazingly easy instructions.
However it won't go into the recovery it just keeps boot looping to the HTC logo.
When i select recovery i see the HTC logo and words that say entering recovery but then it restarts and continues boot looping.
Interestingly my bootloader now says **Tampered**. I'm guessing that is normal.
I appreciate all your time and effort trying to help me.
Regards
James

jamesdf5 said:
Ok i got it working on my Windows 10.
I've just managed to flash the recovery image, cleared cache and rest. Thank you for the amazingly easy instructions.
However it won't go into the recovery it just keeps boot looping to the HTC logo.
When i select recovery i see the HTC logo and words that say entering recovery but then it restarts and continues boot looping.
Interestingly my bootloader now says **Tampered**. I'm guessing that is normal.
I appreciate all your time and effort trying to help me.
Regards
James
Click to expand...
Click to collapse
Yes tampered is normal after flashing custom software. Try the old twrp 2.6.3.3, it sometime doing miracles. Mdmower's versions of TWRP are also known to boot when some other official twrp versions can't.
https://dl.twrp.me/m7/
http://android.cmphys.com/twrp-m7/
Btw did you erased the cache and rebooted the bootloader before attempting to boot in recovery ("fastboot erase cache" then "fastboot reboot-bootloader"? Its the main cause of non-booting recovery, just to be sure.

alray said:
Yes tampered is normal after flashing custom software. Try the old twrp 2.6.3.3, it sometime doing miracles. Mdmower's versions of TWRP are also known to boot when some other official twrp versions can't.
https://dl.twrp.me/m7/
http://android.cmphys.com/twrp-m7/
Btw did you erased the cache and rebooted the bootloader before attempting to boot in recovery ("fastboot erase cache" then "fastboot reboot-bootloader"? Its the main cause of non-booting recovery, just to be sure.
Click to expand...
Click to collapse
Oh dear. I have to confess i accidentally restarted the phone after i flashed it without erasing cache. :crying::crying: I then went back and flashed again and erased as you said in the instructions.
I have have tried the older version on twrp. No luck. I'm guessing i ballsed it up first time! Sorry