Related
Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
George Kayogre said:
Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
George Kayogre said:
Hello,
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592
clsA said:
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592
Click to expand...
Click to collapse
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".
George Kayogre said:
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".
Click to expand...
Click to collapse
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful
alray said:
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful
Click to expand...
Click to collapse
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something
George Kayogre said:
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something
Click to expand...
Click to collapse
uninstall htc sync and try again
alray said:
uninstall htc sync and try again
Click to expand...
Click to collapse
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.
George Kayogre said:
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.
Click to expand...
Click to collapse
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.
alray said:
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.
Click to expand...
Click to collapse
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
This is what "fastboot getvar all" returned:
(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.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
clsA said:
Unzip this to your desktop and open a command window from it's folder (right click - command prompt here)
plug in your phone to the pc boot to the bootloader with power + volume down
type fastboot devices
your phone serial number should be listed
now type fastboot erase cache
it should say something about formatting cache
now fastboot reboot
hopefully your phone will boot back up
Click to expand...
Click to collapse
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen
George Kayogre said:
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
This is what "fastboot getvar all" returned:
(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.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen
Click to expand...
Click to collapse
have you tried to perform a factory reset from the bootloader?
alray said:
have you tried to perform a factory reset from the bootloader?
Click to expand...
Click to collapse
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.
George Kayogre said:
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.
Click to expand...
Click to collapse
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms
alray said:
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms
Click to expand...
Click to collapse
Here's something new: after unlocking my phone, and having confirmed that i wanted all my "personal data erased", it just booted up normally and it worked, but then, while using it, t=it simply crashed...and got stuck in the bootloop again, which kinda points in the arrow of hardware issue again. I'm gonna try installing a rom (after i figure out how) and see where that leads me.
Update: Flashed CM11, phone still on boot loop, sending to repair soon.
Everyone, thanks for the help anyway, I really appreciate it.
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:
Hello
I'm struggling since some days with my One M7 and since I'm not an expert I'm asking for some help..
I have unlocked the phone, installed twrp and by mistake wiped the os, so the phone doesn^t boot anymore. I would like to restore the original settings before trying again to root and install a custom rom.
The problem is that my phone is currently recognized only by fastboot and not by adb, tried several times with different usb cables and os (Win and mac) without success.
my understanding is that the only way to restore the os is via an official RRU.exe (as the device is s-on),am i correct?
Here the details
hboot 1.57.0000
radio 4t.28.3218.04
Opendsp v32.120.274.0909
I downloaded a RUU.exe but getting a security fail message in bootloader, again my understanding is that the image signature is wrong ? which ruu.exe can I use to successfully restore my device ?
many thanks in advance and best regards
Michele
zzmike76 said:
Hello
I'm struggling since some days with my One M7 and since I'm not an expert I'm asking for some help..
I have unlocked the phone, installed twrp and by mistake wiped the os, so the phone doesn^t boot anymore. I would like to restore the original settings before trying again to root and install a custom rom.
The problem is that my phone is currently recognized only by fastboot and not by adb, tried several times with different usb cables and os (Win and mac) without success.
my understanding is that the only way to restore the os is via an official RRU.exe (as the device is s-on),am i correct?
Here the details
hboot 1.57.0000
radio 4t.28.3218.04
Opendsp v32.120.274.0909
I downloaded a RUU.exe but getting a security fail message in bootloader, again my understanding is that the image signature is wrong ? which ruu.exe can I use to successfully restore my device ?
many thanks in advance and best regards
Michele
Click to expand...
Click to collapse
Right first of all adb commands wont work in the bootloader so stop trying different cables etc as your wasting your time, adb is only for when your in a booted rom or in recovery, fastboot commands are for the bootloader.
Next please post your fastboot getvar all without imei and serial number.
also, if you intend on going to a custom rom, there is no point flashing an RUU, you are already halfway there to flashing a custom rom, so which rom do you want to flash ?
hello
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(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!
thanks and regards
michele
zzmike76 said:
hello
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(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!
thanks and regards
michele
Click to expand...
Click to collapse
I can tell you now with a CID of VODAP110 there is no RUU for your phone, I used to have a TWRP backup for vodaphone, that was a long time ago before I got s-off, i'll have a look through and see if I can find it, which custom rom do you want to flash ?
Seanie280672 said:
I can tell you now with a CID of VODAP110 there is no RUU for your phone, I used to have a TWRP backup for vodaphone, that was a long time ago before I got s-off, i'll have a look through and see if I can find it, which custom rom do you want to flash ?
Click to expand...
Click to collapse
well, actually I would be happy to have my mobile booting again
as I'm not an expert I would kindly ask you for any suggestion for custom roms
thanks a lot!
Michele
zzmike76 said:
well, actually I would be happy to have my mobile booting again
as I'm not an expert I would kindly ask you for any suggestion for custom roms
thanks a lot!
Michele
Click to expand...
Click to collapse
Rom suggestions are not allowed.
Put TWRP 2.6.3.3 on your phone if you don't already have that version, it must be that version, I know its a bit old but its still the best for sense based rom's, you can get it from here: http://techerrata.com/browse/twrp2/m7
place the img file in the same folder as your adb and fastboot files on your computer then open a command windows from there and with your phone plugged in and fastbootUSB showing on your phone, issue the following commands
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
then download this file, this is stock unbranded rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.12_odexed.zip re-name it to rom.zip and place it in the same folder as adb and fastboot on your computer, then enter recovery on your phone, just the main screen no sub menu's, and then open a cmd window on your computer from the adb/fastboot folder and with your phone plugged into the computer type this command:
Code:
adb push rom.zip /sdcard/
it will appear unresponsive for quite a while, just leave it alone, takes about 5 mins to push the file but it will let you know when its done.
unplug your phone and flash the rom, when its finished reboot your phone and set it all up.
when everything is done that you want done to it, boot back into recovery and select reboot - system, it will say your rom is not currently rooted, do you want to install SuperSU now, select yes if you want root, your phone will then boot back up, follow the instructions on your phone screen when it boots back up, simple as that to root.
thanks for the information, i downgraded twrp to the suggested version but when entering recovery mode i cannot see the phone with the command adb devices...i noticed that when i plug the phone in windows for few seconds show the phone in device manager with name My HTC under android usb devices but then it disappears
i installed the latest htc drivers but still no phone detection
zzmike76 said:
thanks for the information, i downgraded twrp to the suggested version but when entering recovery mode i cannot see the phone with the command adb devices...i noticed that when i plug the phone in windows for few seconds show the phone in device manager with name My HTC under android usb devices but then it disappears
i installed the latest htc drivers but still no phone detection
Click to expand...
Click to collapse
that's strange that it pops up and then disappears, are you using the original HTC cable, or try a different one, also make sure HTC Sync is uninstalled, just leave the drivers on your computer, you will need to restart after uninstalling HTC Sync.
Sounds more like a computer issue to me than the phone.
Do you have a USB OTG cable you can use ?
original cable (tried also with another one), htc synch uninstalled 8and rebooted), driver version is 2.0.7.23
strang ething it appens on mac as well
i have no otg cable, if i buy one could it solve the issue ?
zzmike76 said:
original cable (tried also with another one), htc synch uninstalled 8and rebooted), driver version is 2.0.7.23
strang ething it appens on mac as well
i have no otg cable, if i buy one could it solve the issue ?
Click to expand...
Click to collapse
yes, you just copy the rom.zip to a memory stick, plug it into one end of the otg cable and the other end into your phone, does away with the use for a computer.
my driver is 2.0.7.28
could be your adb and fastboot, you could always try mine, link below
just find it very strange that it see's it, and then it disappears, ive never experienced anything like this happening to me, yet fastboot works fine, its got to be your drivers, you may have to force your driver in device manager whilst in recovery on your phone, are you using windows 8 ?
Seanie280672 said:
yes, you just copy the rom.zip to a memory stick, plug it into one end of the otg cable and the other end into your phone, does away with the use for a computer.
my driver is 2.0.7.28
could be your adb and fastboot, you could always try mine, link below
just find it very strange that it see's it, and then it disappears, ive never experienced anything like this happening to me, yet fastboot works fine, its got to be your drivers, you may have to force your driver in device manager whilst in recovery on your phone, are you using windows 8 ?
Click to expand...
Click to collapse
no windows 7 , this evening will try with an old xp laptop..but on the mac as well i can only see the device in fastboot
is there away to reformat the sdcard from twrp ? maybe it is damaged
zzmike76 said:
no windows 7 , this evening will try with an old xp laptop..but on the mac as well i can only see the device in fastboot
is there away to reformat the sdcard from twrp ? maybe it is damaged
Click to expand...
Click to collapse
inside twrp you can select wipe and then format data, that will wipe everything all partitions etc, you shouldn't be having any problems with windows 7 though.
update..bought an otg cable and was able to restore the image you sent me...MANY THANKS !!
still the device does not show on windows (there must be some driver issue), but now adb commands work on my mac (yesterday they didn't) so i have a working environment
need to understand how to s-off on mac , is it possible or windows is required ?
thanks again for your support!
zzmike76 said:
update..bought an otg cable and was able to restore the image you sent me...MANY THANKS !!
still the device does not show on windows (there must be some driver issue), but now adb commands work on my mac (yesterday they didn't) so i have a working environment
need to understand how to s-off on mac , is it possible or windows is required ?
thanks again for your support!
Click to expand...
Click to collapse
the only way to s-off on your current HBOOT is to use sunshine, your best off connecting your phone to wifi and download it straight to your phone as its an apk file actually for your phone, not to be run from the computer, it will check your phone first to see if it can be s-off'd and if it can then you'll have to pay $25 though paypal etc, it will then proceed, its well worth it, you can get rid of that vodaphone branded rubbish straight away and flash any RUU should you come stuck again, I paid to have mine done in a shop in Sheffield before sunshine came about and firewater didn't work.
http://theroot.ninja/
Seanie280672 said:
the only way to s-off on your current HBOOT is to use sunshine, your best off connecting your phone to wifi and download it straight to your phone as its an apk file actually for your phone, not to be run from the computer, it will check your phone first to see if it can be s-off'd and if it can then you'll have to pay $25 though paypal etc, it will then proceed, its well worth it, you can get rid of that vodaphone branded rubbish straight away and flash any RUU should you come stuck again, I paid to have mine done in a shop in Sheffield before sunshine came about and firewater didn't work.
http://theroot.ninja/
Click to expand...
Click to collapse
another update....it seems that after a while the phone is entering the usb host adapter mode and refuses to charge/being detected by mac/pc..at least i now can see the warning within the phone..now reading this thread http://forum.xda-developers.com/showthread.php?t=2481211
will try again to wipe everything and reinstall to see whether windows can detect it just for s-offing the phone
Hi guys,
I really need help with my phone, i have an HTC One M7 802w dual sim and i soft bricked by trying to install an stock ruu which i though was the correct one for my phone.
I ended up being stuck in this screen an HTC Grey screen with exclamation marks in all four corners. I tried entering bootloader mode holding the phone in bright light by pressing the power button + vol down, but i had no success.
My computer can still see the device when try the fastboot devices command and can still flash a stock ruu i think but i can't find the correct one for my phone.
Can you guys please help! It almost brand new i only had it for 3 weeks now and i can't do anything but look at it
Here is my phones info:
(bootloader) version: 0.5
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-main: 2.39.1402.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) battery-status: good
(bootloader) battery-voltage: 3675mV
(bootloader) partition-layout: Generic
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 44.035s
Thank you in advance! I really hope that you guys can help me!
mrrrdude said:
Hi guys,
I really need help with my phone, i have an HTC One M7 802w dual sim and i soft bricked by trying to install an stock ruu which i though was the correct one for my phone.
I ended up being stuck in this screen an HTC Grey screen with exclamation marks in all four corners. I tried entering bootloader mode holding the phone in bright light by pressing the power button + vol down, but i had no success.
My computer can still see the device when try the fastboot devices command and can still flash a stock ruu i think but i can't find the correct one for my phone.
Can you guys please help! It almost brand new i only had it for 3 weeks now and i can't do anything but look at it
Here is my phones info:
(bootloader) version: 0.5
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-main: 2.39.1402.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) battery-status: good
(bootloader) battery-voltage: 3675mV
(bootloader) partition-layout: Generic
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 44.035s
Thank you in advance! I really hope that you guys can help me!
Click to expand...
Click to collapse
This is your RUU according to your version main http://d-h.st/7GA
flash it like this:
1. Download the file and rename the file to RUU.zip
2. Place it in adb/fastboot folder
3. Reboot phone to fastbootUSB mode
4. as you are S-On you need to relock bootloader
fastboot oem lock
fastboot erase cache
fastboot reboot-bootloader
5. fastboot oem rebootRUU
6. fastboot flash zip RUU.zip (pre HBOOT update, please flush again)
7. fastboot flash zip RUU.zip (yes twice)
now make sure at the end it says successful and OKAY
8. fastboot reboot-bootloader
9. fastboot reboot.
Seanie280672 said:
This is your RUU according to your version main http://d-h.st/7GA
flash it like this:
1. Download the file and rename the file to RUU.zip
2. Place it in adb/fastboot folder
3. Reboot phone to fastbootUSB mode
4. as you are S-On you need to relock bootloader
fastboot oem lock
fastboot erase cache
fastboot reboot-bootloader
5. fastboot oem rebootRUU
6. fastboot flash zip RUU.zip (pre HBOOT update, please flush again)
7. fastboot flash zip RUU.zip (yes twice)
now make sure at the end it says successful and OKAY
8. fastboot reboot-bootloader
9. fastboot reboot.
Click to expand...
Click to collapse
Thank you very much! i'll download the file and try! be back with a reply! hope it workes! thank you again!!!!!!
mrrrdude said:
Thank you very much! i'll download the file and try! be back with a reply! hope it workes! thank you again!!!!!!
Click to expand...
Click to collapse
IT WORKES!!!! My PHone is back to normal!! THANK YOU VERY MUCH!
I'm curious about something, can you please tell me what do you look for to see which is the proper RUU for any HTC?
mrrrdude said:
IT WORKES!!!! My PHone is back to normal!! THANK YOU VERY MUCH!
I'm curious about something, can you please tell me what do you look for to see which is the proper RUU for any HTC?
Click to expand...
Click to collapse
THIS: (bootloader) version-main: 2.39.1402.1
bit more tricky though if this isn't present, I then base it on CID, MID, Baseband version, HBOOT version etc, whatever I can.
it helps that you have a dual sim kind of, everything for your phone is here: http://forum.xda-developers.com/showthread.php?t=2617159
scroll down the page till you see 3. HTC One 802w (x.xx.1402.x) in blue, and then from there look up your full version main, if your VM is an OTA, then you have a big problem trying to recovery your phone, if theres an RUU then its easy.
Now your back up and running, make yourself a nandroid backup before messing with your phone, then copy the nandroid to somewhere safe on your computer, ive seen so many people wipe there entire phone by accident, including the nandroid and then being stuck, or get s-off for it, s-off is the difference between fixing your phone in the future if it ever goes down again, or having a nice new paper weight.
Seanie280672 said:
THIS: (bootloader) version-main: 2.39.1402.1
bit more tricky though if this isn't present, I then base it on CID, MID, Baseband version, HBOOT version etc, whatever I can.
it helps that you have a dual sim kind of, everything for your phone is here: http://forum.xda-developers.com/showthread.php?t=2617159
scroll down the page till you see 3. HTC One 802w (x.xx.1402.x) in blue, and then from there look up your full version main, if your VM is an OTA, then you have a big problem trying to recovery your phone, if theres an RUU then its easy.
Now your back up and running, make yourself a nandroid backup before messing with your phone, then copy the nandroid to somewhere safe on your computer, ive seen so many people wipe there entire phone by accident, including the nandroid and then being stuck, or get s-off for it, s-off is the difference between fixing your phone in the future if it ever goes down again, or having a nice new paper weight.
Click to expand...
Click to collapse
Thank you very much for your help! I'll do that from now one! i have allot to learn about flashing.
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