Related
Ok, so, yesterday my phone just randomly froze. I rebooted the phone and it randomly popped up with this "Decrypt Storage" message where I have to put in a password which I never set to unlock my phone. So, I rebooted into clockworkmod. Well, it shows the CWM logo for a second then reboots into the normal boot. I tried going into the bootloader to do a factory reset. The same thing happens. I don't know what to do! My One is a paperweight! Can anyone help me?
Thanks so much in advance.
HotFieryTech said:
Ok, so, yesterday my phone just randomly froze. I rebooted the phone and it randomly popped up with this "Decrypt Storage" message where I have to put in a password which I never set to unlock my phone. So, I rebooted into clockworkmod. Well, it shows the CWM logo for a second then reboots into the normal boot. I tried going into the bootloader to do a factory reset. The same thing happens. I don't know what to do! My One is a paperweight! Can anyone help me?
Thanks so much in advance.
Click to expand...
Click to collapse
Do you have S-Off and or SuperCID? Can you restore a stored CWM backup? Tried flashing a RUU?
i dont know how ppl expect someone to help them if they dont provide details about their devices..sigh
Ok. I have S-On and I don't have SuperCID. My One is an unlocked One, not Dev version. I cannot restore to a CWM backup because CWM doesn't load. I cannot flash an RUU because when I try to relock my bootloader with fastboot, I get an error saying "FAILED (status read failed (Too many links))." I've also tried deleting userdata through fastboot and I get the error "FAILED (remote: not allowed)." I hope that this I can fix this, cause right now my One is a $600 paperweight.
Thanks so much for your help.
I also just read that this may help you.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: .........................
(bootloader) imei: ..........................
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4027mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.066s
Thanks again for your help
"FAILED (status read failed (Too many links))." is normal I think, mine says that every time but the operation is actually successful.
RuleOfSines said:
"FAILED (status read failed (Too many links))." is normal I think, mine says that every time but the operation is actually successful.
Click to expand...
Click to collapse
That may be true, but my bootloader still says unlocked.
Anyone have any idea what I should do?
fastboot erase cache
skinsfanbdh said:
fastboot erase cache
Click to expand...
Click to collapse
Ok. I did that. No detectable changes. Every other command still fails.
Oh, also I forgot to say that one change I noticed when it first stopped working was that the boot animation changed from the Renovate Rom one to "ANDROID" with light sweeping from left to right.
phone needs to be connected to the computer and booted to bootloader for the command to work
skinsfanbdh said:
phone needs to be connected to the computer and booted to bootloader for the command to work
Click to expand...
Click to collapse
I wasn't born yesterday.
the command to lock bootloader you are using is fastboot oem lock right?
Have you tried installing a new recovery from fastboot? Maybe try TWRP, to install fastboot oem flash recovery yourrecovery.img
nugzo said:
the command to lock bootloader you are using is fastboot oem lock right?
Have you tried installing a new recovery from fastboot? Maybe try TWRP, to install fastboot oem flash recovery yourrecovery.img
Click to expand...
Click to collapse
I'm starting to think this is a hardware issue. I used the fastboot oem lock command and it gets an error. I tried flashing the stock recovery, CWM, and TWRP. For all three, it says it is successful, but when I boot into recovery, it's the same CWM version I've had that loads the hat logo for a second and then crashes and boots normally. Do you know what the errors I get on almost everything mean?
Anyone?
HotFieryTech said:
I wasn't born yesterday.
Click to expand...
Click to collapse
LMAO.. this was so funny.
Please, anyone know how to fix my broken phone? I can't go to HTC because my phone's bootloader says "TAMPERED" and "UNLOCKED." Someone please help me
Thanks
bump
Anyone? I have a dead device here.
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
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
Dear XDA-Developers Forum,
I require your help fixing my HTC One M7.
When I tried to use an RUU to set it back to stock firmware the RUU.exe returned error 155. Maybe I did something wrong. I have some experience flashing different phones but I'm not a pro like most people here..
Anyway, the phone hung at the black screen with the HTC logo. At some point I managed to reconnect to the bootloader and Fastboot commands were still available. I tried using Fastboot to verify I had the correct RUU which to all appearance was the case. After trying to reboot to system the phone is stuck in a loop. It displays the CM logo from the ROM it had previously installed.
From here, I'm stuck. Power button does not work, combinations to go into bootloader don't work. The only thing that does work is holding power and vol+ and vol- at the same time. This makes the phone reboot (showing white HTC screen with green logo). After a few seconds I am however stuck with the CM logo.
Is there a way to fix this?
Some additional info on my device:
HBoot 1.55
Bootloader unlocked
S-ON (although that's strange cause I had it turned off before)
CM 10.2 installed
TWRP 2.8.5.0
I hope someone has a solution. Of course all drivers and software are up to date and I have backup of my relevent data. I fear that I will need to get a replacement since extensive Google-Search would not yield a solution so far. It could be I'm just not educated enough to understand.
Best regards
Nick
Little Update
Without any chance of turning the device off and re-entering bootloader or recovery I waited until the battery finally died.
I plugged it into the wall charger. I was then finally able to start to the bootloader. It looked very usual. The security alert had disappeared and it was in HBoot mode.
I went on and selected factory reset guessing this to be the easiest and quite likely solution to the bootloop. TWRP started but showed a number of mounting errors and did not finish the operation. After auto-restart I'm back at the bootloop from the start.
Waiting for the battery to die again...
Any suggestions what I should do next?
DNK83 said:
Without any chance of turning the device off and re-entering bootloader or recovery I waited until the battery finally died.
I plugged it into the wall charger. I was then finally able to start to the bootloader. It looked very usual. The security alert had disappeared and it was in HBoot mode.
I went on and selected factory reset guessing this to be the easiest and quite likely solution to the bootloop. TWRP started but showed a number of mounting errors and did not finish the operation. After auto-restart I'm back at the bootloop from the start.
Waiting for the battery to die again...
Any suggestions what I should do next?
Click to expand...
Click to collapse
Error 155 means your using the wrong RUU
You don't need to keep waiting for the battery to die, hold down the volume down button and the power button together, keep them held down, the captive lights on the bottom will flash about 15 times, when the phone goes off, let go of the power button only, the phone should now boot to the bootloader.
post your fastboot getvar all without imei and serial number please, anyone here needs more info about your phone before we can help and this will tell us all everything we need to know.
Hello,
thanks for your reply.
I have tried holding the power button and vol- together. Even after more than 30 seconds the phone does not react and keeps on showing the CM logo.
Sorry, for not providing more information. I would've posted the getvar info before but was not able to connect through fastboot.
Will do once the battery is charged enough for the next try.
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
DNK83 said:
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
Click to expand...
Click to collapse
take the brackets off the all () the command is fastboot getvar all
DNK83 said:
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
Click to expand...
Click to collapse
Why the brackets () in "fastboot getvar (all)" ? The command is "fastboot getvar all" without the quotes.
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3684mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
alray said:
Why the brackets () in "fastboot getvar (all)" ? The command is "fastboot getvar all" without the quotes.
Click to expand...
Click to collapse
The brackets are added because I'm tired and kinda angry.
DNK83 said:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3684mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
first of all I recommend you flash twrp 2.8.6.0 from here, it will make life easier for you: https://dl.twrp.me/m7/twrp-2.8.6.0-m7.img.html
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
then enter twrp, and create a very simple backup, just something like boot or cache.
now plug your phone into the computer, it should open on your computer as this version of twrp supports MTP, navigate to the TWRP backup folder on your phone and delete the backup file from the folder (just the backup file itself, none of the folders) it will be in TWRP/BACKUP/PHONE SERIAL NUMBER/DATE AND OTHER DIGITS/ delete the file in here and replace with the files in this zip (make sure you extract the zip first): https://www.androidfilehost.com/?fid=95897840722646676
now unplug your phone and restore the backup.
The installation of TWRP worked fine. Trying to make the simple backup yields a bunch of failed attempts to mount.
DNK83 said:
The installation of TWRP worked fine. Trying to make the simple backup yields a bunch of failed attempts to mount.
Click to expand...
Click to collapse
in that case, select wipe, and then format data button, type yes to confirm, when done, select reboot to recovery for change to take effect, it will say no OS installed, just ignore it, it will also ask you if you would like to install super SU, select do not install, when the phone boots back to recovery, try backup again.
Okay.
I formatted the card and was able to do the backup. I was neither notified of a missing OS nor asked if I wanted to Install Super SU. Reboot to Recovery worked normal.
Plugging the phone into my computer does not yield a connection that I could use to copy files.
DNK83 said:
Okay.
I formatted the card and was able to do the backup. I was neither notified of a missing OS nor asked if I wanted to Install Super SU. Reboot to Recovery worked normal.
Plugging the phone into my computer does not yield a connection that I could use to copy files.
Click to expand...
Click to collapse
make sure you are on the recovery main screen when you plug the phone into your computer, no sub menu's.
If it still doesn't appear on your computer, double check your device manager to make sure its showing in there correctly.
A "Google Nexus ADB Interface" is listed. Is that what we're looking for?
Btw: many thanks for the help so far. It's becoming quite exciting right now.
DNK83 said:
A "Google Nexus ADB Interface" is listed. Is that what we're looking for?
Btw: many thanks for the help so far. It's becoming quite exciting right now.
Click to expand...
Click to collapse
Strange, it should look like this pict below, I'm using a HTC One M8, with the latest TWRP, but its the same thing as yours, as I previously had the M7.
try uninstall, that driver and then manually install the correct driver.
check Question 2 here on how to manually force the driver: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
I have tried re-installing the HTC driver. So far no results. Did you want me to remove this ADB thing from the device manager? I am rebooting quickly to see if Win7 is the problem.
DNK83 said:
I have tried re-installing the HTC driver. So far no results. Did you want me to remove this ADB thing from the device manager? I am rebooting quickly to see if Win7 is the problem.
Click to expand...
Click to collapse
yes, just right click that other driver and uninstall it, then reboot.
I just download HTC sync manager and install that for my drivers, then just uninstall HTC sync, you will see the driver package which comes with sync manager just above it, leave that one alone, never had a problem with it.
The hardware detection ran when I plugged the phone in. The device is again listed as "Google Nexus ADB Device"
I have a package installed named "Minimal ADB and Fastboot Version 1.2". This is probably the reason why my phone is listed this way right now...uninstall?
DNK83 said:
The hardware detection ran when I plugged the phone in. The device is again listed as "Google Nexus ADB Device"
I have a package installed named "Minimal ADB and Fastboot Version 1.2". This is probably the reason why my phone is listed this way right now...uninstall?
Click to expand...
Click to collapse
strange, ive never seen it appear like that.
ive attached my adb and fastboot files below if you want to use those, maybe yours came with the google nexus driver.
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