Database Develop

[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] Stuck..No OS, bootloader unlocked (tampered) Not Rooted

Hi all
I have a mates HTC One (M7) he had installed a custom rom and then i dont know how wiped the lot.
So at the moment I have a Unlocked but Tampered bootloader
HB 1.56.000
S-ON
No Root
and NO OS
I have managed to install TWRP and have ADB installed (windows 8.1 x64)
In fastboot i get fastboot usb although adb commands do not appear to work although fastboot commands do.
I have tried to sideload using TWRP but no luck.
I have tried to use Fastboot flash zip recovery.zip to flash the GURU Reset from HTCGuru but that doesn't work
Tried to get s-off but with the adb issues I am having no luck.
Any help would be great....i have spent nearly 20 hours straight on this and have now lost the will to live

fastboot getvar all
Windows 7
We need these
from HTC One

yatindroid said:
fastboot getvar all
Windows 7
We need these
from HTC One
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH36LW904423
(bootloader) imei: 357864056120981
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

remove imei and serial from your output above, its dangerous to post them.
you need TWRP 2.6.3.3 on your phone.
enter recovery on your phone then place the guru reset file you downloaded in the same folder as adb and fastboot on your computer, (windows 8.1 is fine) and rename it to rom.zip for ease.
make sure your phone is plugged into your PC, open a command window in your adb/fastboot folder and type adb push rom.zip /sdcard/
takes a while so sit back and wait, it will tell you on the CMD window when its done.
make sure your battery is 50% or more, unplug your phone, and then flash it from within recovery, select install and find rom.zip in the list, swipe to confirm flash.

Cheers will try and report back
Sent from my LG-D802 using XDA Free mobile app

lspec230 said:
Cheers will try and report back
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
remove your serial number and IMEI number from you above post.
---------- Post added at 08:07 PM ---------- Previous post was at 08:05 PM ----------
during the installer, select wipe data, flash stock recovery but don't flash stock radio.

Ok got TWRP 2.6.3.3 on there
When I try the adb push command I get Error: Device not Connected
I wish I knew why he didn't S-Off in the first place.
I am guessing the only way to do this now is to get an OTG cable and try and move the .zip that way.
Is there a way to use a the fastboot commands to push the file across rather adb as i seem to be able to use fastboot ok

do you have the latest drivers installed ?
do you have the latest adb and fastboot ?
strange that fastboot works but adb doesn't, you are in recovery main screen when you issue the push command ?

Seanie280672 said:
do you have the latest drivers installed ?
do you have the latest adb and fastboot ?
strange that fastboot works but adb doesn't, you are in recovery main screen when you issue the push command ?
Click to expand...
Click to collapse
Yeah latest drivers reinstalled ADB/SDK tools yesterday adb version 1.0.31
Went through the windows 8.1 pain of ensuring my USB Drivers were intel rather than the default windows one as well.
I have tried the adb push in Recovery and Fastboot USB and also tried using adb sideload utility in TWRP
If I use fastboot to relock the bootloader and with s-on will I be able to use a stock RUU.exe??

yup you can do that, or if that fails then pull the rom.zip from the RUU and flash through fastboot rebootRUU mode.

Will try pulling the rom first will I have to look the bootloader first.?
Tried last night with the ruu.exe but kept getting 155 error
Sent from my LG-D802 using XDA Free mobile app

lspec230 said:
Will try pulling the rom first will I have to look the bootloader first.?
Tried last night with the ruu.exe but kept getting 155 error
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
155 error = relock your bootloader first, use the command fastboot oem lock
when you run the RUU it first unpacks itself, leave the installer open but don't do anything else with it.
you need to show hidden files and folders on your PC
then goto c:\users\username\AppData\Local\TEmp then one of those folders you see at the top of the list with lots of letters and numbers will have rom.zip in it, copy and paste it to your adb and fastboot folder, it should be pretty much the same file size as the whole RUU itself, once that's done you can close the RUU installer.

Thanks for all the help everyone... Relocked bootloader and used the 4.4 ruu.exe
Think someone owes me beer for soft bricking his phone then throwing at me to fix
Sent from my LG-D802 using XDA Free mobile app

Weird black screen problem

Hello guys,
I have a weird problem that happened not to my phone but a friend of mine... I'll try to make the details as good as possible but it may be different since I did not own the phone, but as I said, a friend did.
She says it was Sense6.0 4.4.2 and that one day the phone booted, showed the HTC logo like 3 times (between bootloop) and it went down (power off), so she charged it for like 1 days but it didn't turn the display on... Now, it had pattern lock so getting adb to work was a complete PITA but we figured that the phone wasn't dead when we tried to call her and she swept the screen to answer and she did, so, after a lot of pain, we managed to unlock it blindly and accept the recogniztion so we could have adb...
Now, we rebooted into fastboot, unlocked bootloader (which wiped the system to factory reset) and installed a custom kernel/recovery (via fastboot)
The phone has 1.57 HBOOT and I understand firewater works, but here is the major problem: I don't have access to Wireless because I cant see a damn thing so were screwed there... 3G connection doesn't work at all and I go and ping and it says failed...
ALTHOUGH I tried rumrunner (before I knew HBOOT was 1.57) and somehow it rebooted and the screen turned on so I figured the screen wasnt dead, but as soon as it finished booting, the screen went off again forever...
The phone has CID: HTC__332 (Latin American variant) so I cant find a suitable RUU so I can flash without S-OFF
I am really screwed but maybe anyone here with some experience can shed a light here and save an M7
PD: I have working adb and fastboot but just through command line

Poesini said:
Hello guys,
I have a weird problem that happened not to my phone but a friend of mine... I'll try to make the details as good as possible but it may be different since I did not own the phone, but as I said, a friend did.
She says it was Sense6.0 4.4.2 and that one day the phone booted, showed the HTC logo like 3 times (between bootloop) and it went down (power off), so she charged it for like 1 days but it didn't turn the display on... Now, it had pattern lock so getting adb to work was a complete PITA but we figured that the phone wasn't dead when we tried to call her and she swept the screen to answer and she did, so, after a lot of pain, we managed to unlock it blindly and accept the recogniztion so we could have adb...
Now, we rebooted into fastboot, unlocked bootloader (which wiped the system to factory reset) and installed a custom kernel/recovery (via fastboot)
The phone has 1.57 HBOOT and I understand firewater works, but here is the major problem: I don't have access to Wireless because I cant see a damn thing so were screwed there... 3G connection doesn't work at all and I go and ping and it says failed...
ALTHOUGH I tried rumrunner (before I knew HBOOT was 1.57) and somehow it rebooted and the screen turned on so I figured the screen wasnt dead, but as soon as it finished booting, the screen went off again forever...
The phone has CID: HTC__332 (Latin American variant) so I cant find a suitable RUU so I can flash without S-OFF
I am really screwed but maybe anyone here with some experience can shed a light here and save an M7
PD: I have working adb and fastboot but just through command line
Click to expand...
Click to collapse
So does the screen come on when the phone is booted to the bootloader and recovery?
Can you post fastboot getvar all?
Code:
fastboot getvar all
Post the output here but remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
So does the screen come on when the phone is booted to the bootloader and recovery?
Can you post fastboot getvar all?
Code:
fastboot getvar all
Post the output here but remove imei and serial numbers before posting.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
No, the screen never turn on... It did only when trying the first time rumrunner but not anymore (But so, I know the screen isn't dead)
Here is the getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.599.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(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
all: Done!
finished. total time: 0.047s

Poesini said:
No, the screen never turn on... It did only when trying the first time rumrunner but not anymore (But so, I know the screen isn't dead)
Here is the getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.15.599.101
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3854mV
(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
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
It does sound like a dead LCD to me. Weird how it came on once while running rumrunner though. Try powering off the device then hold a it under a bright light hold power on + volume down for 90+ seconds. Maybe a fault with proximity sensor.
There is no ruu you can use while s-on and I can't even find a firmware you can try to flash. So if that doesn't work I don't know what else to try
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
It does sound like a dead LCD to me. Weird how it came on once while running rumrunner though. Try powering off the device then hold a it under a bright light hold power on + volume down for 90+ seconds. Maybe a fault with proximity sensor.
There is no ruu you can use while s-on and I can't even find a firmware you can try to flash. So if that doesn't work I don't know what else to try
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Holding the device under a bright light seems to power on the device SOMETIMES with the HTC logo visible and then it gets past that (with a little backlight movement meanwhile -dimmer- or -brighter-) and then back to desktop with no light
Is there any way to disable the proximity sensor or maybe flash a custom ROM via adb commands to flash it into recovery inside OS (TWRP 2.8.1.0 right now) or something?

Poesini said:
Holding the device under a bright light seems to power on the device SOMETIMES with the HTC logo visible and then it gets past that (with a little backlight movement meanwhile -dimmer- or -brighter-) and then back to desktop with no light
Is there any way to disable the proximity sensor or maybe flash a custom ROM via adb commands to flash it into recovery inside OS (TWRP 2.8.1.0 right now) or something?
Click to expand...
Click to collapse
Well that's promising. You can push a Rom with adb but you need the recovery menu to install it which may prove difficult if you can't see it.
To push the Rom put it in your fastboot folder and rename it rom.zip. connect the usb with the phone for adb and type in the command window
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes.
You may be better to use TWRP 2.6.3.3 to avoid install problems. Remember to
Code:
fastboot erase cache
when you flash a new recovery.
And keep using the bright light power on trick. May be give the sensors a clean (top left of the phone).
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Well that's promising. You can push a Rom with adb but you need the recovery menu to install it which may prove difficult if you can't see it.
To push the Rom put it in your fastboot folder and rename it rom.zip. connect the usb with the phone for adb and type in the command window
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes.
You may be better to use TWRP 2.6.3.3 to avoid install problems. Remember to
Code:
fastboot erase cache
when you flash a new recovery.
And keep using the bright light power on trick. May be give the sensors a clean (top left of the phone).
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I know my ways to push files via ADB, but I am saying like SuperSU does when it asks if you want to update it via TWRP option where it reboots directly to recovery and flashes a zip without you doing anything
I could push many files via ADB, but I couldn't flash them correctly (and I don't want to screw this phone) without seeing the screen

Poesini said:
I know my ways to push files via ADB, but I am saying like SuperSU does when it asks if you want to update it via TWRP option where it reboots directly to recovery and flashes a zip without you doing anything
I could push many files via ADB, but I couldn't flash them correctly (and I don't want to screw this phone) without seeing the screen
Click to expand...
Click to collapse
Flash twrp 2.6.3.3 newer versions of twrp can be temperamental and probably why your having trouble flashing roms
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 07:26 PM ---------- Previous post was at 07:07 PM ----------
Try the bright light trick again but this time power off the device. Hold the sensors close to the light
Hold volume up and down +power for 60 secs the phone will bootloop while your holding the buttons. Hopefully that will be enough to reset the sensor. :fingers-crossed:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

bootloader refuses to unlock

I've tried to unlock the boot loader of my HTC one m7 to no avail.
I tried unlocking it via htcdev but after wiping my phone, my boot loader still remained locked.
is there any alternative way of unlocking the boot loader without htcdev?
I saw one that involved typing some commands in fastboot but I'm afraid that might wreck the phone.
PS, I'm a newbie so please make any suggestions as plain as possible

gravity02 said:
I've tried to unlock the boot loader of my HTC one m7 to no avail.
I tried unlocking it via htcdev but after wiping my phone, my boot loader still remained locked.
is there any alternative way of unlocking the boot loader without htcdev?
I saw one that involved typing some commands in fastboot but I'm afraid that might wreck the phone.
PS, I'm a newbie so please make any suggestions as plain as possible
Click to expand...
Click to collapse
So is your device ***LOCKED*** or ***RELOCKED*** by which I mean has it ever been unlocked before or this is the first time?
Normally the course of action for bootloader unlocking issues is to flash a matching firmware package and request a new Unlock_code.bin. But let's see what variant of M7 you have first not all M7s can be unlocked via HTCdev.
Could you post the out put of
Code:
fastboot getvar all
Please remove your IMEI and Serial numbers before posting for security purposes
If you can't use HTCdev and your device is s-on then the only option is Sunshine App but it costs $25 so let's see what you've got and go from there :good:

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3721mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))

gravity02 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3721mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Ok your s-off That's good you have a couple of options here. You can flash a firmware package and request a new Unlock_code.bin as I mentioned above. :good: I'll see if I can find a firmware zip for you and post the link here
EDIT: -You can download a matching firmware here http://d-h.st/NPJ. Do you know how to flash firmware.zips with fastboot?
Or you can boot a custom recovery and unlock it yourself using "adb shell"
With the recovery image file in your fastboot folder. Connect fastboot usb and in the command window type
Code:
[B]fastboot boot recovery "name-of-recovery".img[/B]
[B]adb shell[/B]
[B]su[/B] (if needed to get a*#*prompt)
[B]echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796[/B]
(i would very strongly recomend you copy/paste this)
[B]exit[/B]
(exit a second time if you need to to get back to a normal > prompt)
[B]adb reboot bootloader[/B]
verify you are now unlocked
The above method is taken from this thread http://forum.xda-developers.com/showthread.php?t=2475914 Thanks should go to the OP :good:

thanks for the quick replies. I already have twrp installed. should I now run the command?
will it erase my files?

gravity02 said:
thanks for the quick replies. I already have twrp installed. should I now run the command?
will it erase my files?
Click to expand...
Click to collapse
HTCdev method will wipe your DATA and SDCARD
Recovery command method will not wipe anything :good:
Quoted from the Main Thread in above link
piterk said:
Could you tell me if this method to lock/unlock bootloader wipes phone data like the method via htcdev?
Click to expand...
Click to collapse
scotty1223 said:
no,it does not erase data.
the flashing of unlock code,and relock command initiate hboot to factory reset. this is only changing the flag that hboot checks.
Click to expand...
Click to collapse

tried this but it didn't work. the boot loader remained locked.
the phone was once bricked and I had it fixed via a JTAG. could this be a reason for this?

gravity02 said:
tried this but it didn't work. the boot loader remained locked.
the phone was once bricked and I had it fixed via a JTAG. could this be a reason for this?
Click to expand...
Click to collapse
Mmmm that's strange try again but this time use CWM https://www.dropbox.com/s/82kt3edku0j2sup/cwm.img?dl=0 you don't need to flash it just boot it with
Code:
fastboot boot cwm.img
Failing that did you try the firmware method?

I haven't tried the firmware method. can you walk me through it?

gravity02 said:
I haven't tried the firmware method. can you walk me through it?
Click to expand...
Click to collapse
Download the firmware package linked in my previous post. Put the zip in your fastboot folder and rename it "firmware.zip"
Boot your phone to the bootloader and connect fastbootusb, Now in the fastboot command line type
Code:
fastboot erase cache
fastboot oem rebootRUU
--- case sensitive ---^^^
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now go to htcdev and complete the Unlock my bootloader procedure to get a new Unlock_code.bin :fingers-crossed:
FYI :- Flashing the firmware will restore the Stock Recovery so after the Unlock you will need to flash your Custom recovery again

I followed the steps but my phone is now stuck in the htc logo. I can't even switch it off

done this and now the phone is stuck in the htc logo. i've been trying to switch off the phone and try to boot into bootloader but holding down the power button only makes the capacitive buttons flash on and off. i'm in a fix. any help?:crying:

gravity02 said:
done this and now the phone is stuck in the htc logo. i've been trying to switch off the phone and try to boot into bootloader but holding down the power button only makes the capacitive buttons flash on and off. i'm in a fix. any help?:crying:
Click to expand...
Click to collapse
Hold down the power button and the volume down together, the capacitive buttons will flash, don't worry just let them flash and just keep holding down those 2 buttons, when they stop flashing which is about 12 to 15 times, release the power button, but continue to hold down the volume down the phone should now boot to the bootloader.

Seanie280672 said:
Hold down the power button and the volume down together, the capacitive buttons will flash, don't worry just let them flash and just keep holding down those 2 buttons, when they stop flashing which is about 12 to 15 times, release the power button, but continue to hold down the volume down the phone should now boot to the bootloader.
Click to expand...
Click to collapse
Don't forget it needs to be in a bright lighted room (really!)

gravity02 said:
done this and now the phone is stuck in the htc logo. i've been trying to switch off the phone and try to boot into bootloader but holding down the power button only makes the capacitive buttons flash on and off. i'm in a fix. any help?:crying:
Click to expand...
Click to collapse
Your Stuck on the HTC logo because you flashed the firmware and you have a custom rom. The Firmware restored your Stock Recovery and boot.img. Were you able to unlock the bootloader? You need to do that before you try flash anything. It was the Custom recovery and boot.img that caused the problem with unlocking the bootloader.
To make your phone boot to your rom again open the zip file of the rom installed on the phone and extract the boot.img to your fastboot folder. Then flash it with fastboot
Code:
fastboot flash boot boot.img
or just flash your rom again or any compatible rom :good:
P.S for the record when you post you should be quoting my last post or mention me like this @Danny201281 Then I will get a notification and you will get a faster response :good:

i'm currently in fastboot and there doesn't seem to be any change even after flashing the firmware.
i'm still s-off.
tried unlocking the bootloader again and it still remains locked. should i retry flashing the firmware?

gravity02 said:
i'm currently in fastboot and there doesn't seem to be any change even after flashing the firmware.
i'm still s-off.
tried unlocking the bootloader again and it still remains locked. should i retry flashing the firmware?
Click to expand...
Click to collapse
That is weird, are there any files on the device you need to keep? I'm running out of ideas here but you could try factory reset from the stock recovery but i'm not sure it will help. After that the only other thing I can suggest is flashing a full RUU.
Stock recovery factory reset instructions
Select recovery from the bootloader menu. The screen will turn black for a while and then display an image of a phone with red exclamation. Don't worry that's normal. Hold Volume up and press the power button to reveal the stock recovery menu. You will also see some errors about failed to mount sdcard that's also normal in Stock Recovery.
Select Factory Reset from the recovery menu. :good:
In the mean time i'll check out your options for RUU
---------- Post added at 10:44 AM ---------- Previous post was at 10:30 AM ----------
Danny201281 said:
That is weird, are there any files on the device you need to keep? I'm running out of ideas here but you could try factory reset from the stock recovery but i'm not sure it will help. After that the only other thing I can suggest is flashing a full RUU.
Stock recovery factory reset instructions
Select recovery from the bootloader menu. The screen will turn black for a while and then display an image of a phone with red exclamation. Don't worry that's normal. Hold Volume up and press the power button to reveal the stock recovery menu. You will also see some errors about failed to mount sdcard that's also normal in Stock Recovery.
Select Factory Reset from the recovery menu. :good:
In the mean time i'll check out your options for RUU
Click to expand...
Click to collapse
Ok it seems your in luck. There's plenty of RUU's for your T-Mobile device. Look here http://forum.xda-developers.com/showthread.php?t=2375223 and download this T-Mobile HTC One RUU 1.27.531.11
Simple to use just connect fastboot usb in the bootloader and launch the ruu on your pc. This will also wipe your device and return you to Stock.

@Danny201281, i'll download the RUU but will it be possible to flash twrp recovery and restore a backup of the ROM I made so?
won't that bring the phone back to life?

gravity02 said:
@Danny201281, i'll download the RUU but will it be possible to flash twrp recovery and restore a backup of the ROM I made so?
won't that bring the phone back to life?
Click to expand...
Click to collapse
You can't flash recovery while the bootloader is locked not even with s-off.
You could open the firmware zip you flashed and replace the recovery and boot.img with twrp and the boot.img of your Rom. Then flash the firmware zip. The phone should then boot up no problem. And you'll have the custom recovery back. If you want you can send me the boot.img or a link to the Rom on your phone and I can make the zip for you
Can I ask why you locked it in the first place? There's really no need to lock or relock when the device is s-off.
It's starting to look more like a hardware problem though. As I say normally it's some customization in the firmware that causes the problem. But with non of the methods working even with stock firmware it seems like the bootloader is not excepting any unlock instruction.

@ Danny201281, I replaced the stock recovery in the firmware.zip with twrp and flashed the firmware and was able to boot into twrp. I then copied a nandroid backup I made previously into the phone and restored it and the phone booted up properly.
how do I extract the boot.IMG from the nandroid?
thanks for your help so far

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