Database Develop

[Q] Bricked after flashing Insertcoin 4.4 ROM (ADB can't find device)

I flashed the ROM in recovery. I thought I was S-OFF but am S-ON. It gave me error code 7 and the installation failed. Now I can't even boot into recovery (it just cycles between the HTC splash screen and then tries booting into recovery for a second. I see the recovery logo and then it reboots).
Holding down the volume down and power buttons I can get into HBOOT, but can't do a factory reset or recovery from there. I can get into the FASTBOOT menu, but my computer just tells me that the device connected has malfunctioned and can't recognize it. running "ADB Devices" returns with no devices found.
I downloaded and ran the RUU, but it can't find the phone. I'm out of ideas. I appreciate any help you guys can offer.

Caboose127 said:
I flashed the ROM in recovery. I thought I was S-OFF but am S-ON. It gave me error code 7 and the installation failed. Now I can't even boot into recovery (it just cycles between the HTC splash screen and then tries booting into recovery for a second. I see the recovery logo and then it reboots).
Holding down the volume down and power buttons I can get into HBOOT, but can't do a factory reset or recovery from there. I can get into the FASTBOOT menu, but my computer just tells me that the device connected has malfunctioned and can't recognize it. running "ADB Devices" returns with no devices found.
I downloaded and ran the RUU, but it can't find the phone. I'm out of ideas. I appreciate any help you guys can offer.
Click to expand...
Click to collapse
I'm willing to help.. but I am very busy.. can I have a look into this a bit later? Maybe someone else is going to be able to help you.. but if there isn't... I'm going to help you.
To calm down: As long as you can get into your hboot, everything is fine! You are not hardbricked!
Let me know if that's ok for you.

LibertyMarine said:
I'm willing to help.. but I am very busy.. can I have a look into this a bit later? Maybe someone else is going to be able to help you.. but if there isn't... I'm going to help you.
To calm down: As long as you can get into your hboot, everything is fine! You are not hardbricked!
Let me know if that's ok for you.
Click to expand...
Click to collapse
Hey, as long as you're willing to help, I can wait. I'm at work for the next 6 hours and don't really NEED my phone until I get off. So I've got time to wait.
Thanks.

Caboose127 said:
Hey, as long as you're willing to help, I can wait. I'm at work for the next 6 hours and don't really NEED my phone until I get off. So I've got time to wait.
Thanks.
Click to expand...
Click to collapse
Hmm.. in 3 hours I'm going to sleep.. (Switzerland time zone) And so I write some basic thing that you can test and try out.. so that we can determine what the best steps will be.
First: Give me the output from that command(while in fastboot-ubs):
fastboot getvar all
Click to expand...
Click to collapse
Second:
What hboot version do you have? 1.44/1.54/1.55
What's the stock ROM you recieved with the factory fresh phone? z.zz.XXX.z now.. what was the XXX number exactly? The international edition for example is: 1.24.401.7 I only need the 3-digit number.
Third:
Unlocked or Locked/Relocked?

LibertyMarine said:
Hmm.. in 3 hours I'm going to sleep.. (Switzerland time zone) And so I write some basic thing that you can test and try out.. so that we can determine what the best steps will be.
First: Give me the output from that command(while in fastboot-ubs):
Second:
What hboot version do you have? 1.44/1.54/1.55
What's the stock ROM you recieved with the factory fresh phone? z.zz.XXX.z now.. what was the XXX number exactly? The international edition for example is: 1.24.401.7 I only need the 3-digit number.
Third:
Unlocked or Locked/Relocked?
Click to expand...
Click to collapse
The phone is unlocked, HBOOT version is 1.44
running fastboot getvar all yields "waiting for device" Windows doesn't recognize the phone when it's plugged in. I know I have the correct drivers installed. When it tries to boot into recovery, I briefly see the device show up in Device Manager, but it disappears again. I don't know what the stock ROM was that came with the phone. I want to say it was 1.27.531.8, but I don't know for sure.

Caboose127 said:
The phone is unlocked, HBOOT version is 1.44
running fastboot getvar all yields "waiting for device" Windows doesn't recognize the phone when it's plugged in. I know I have the correct drivers installed. When it tries to boot into recovery, I briefly see the device show up in Device Manager, but it disappears again. I don't know what the stock ROM was that came with the phone. I want to say it was 1.27.531.8, but I don't know for sure.
Click to expand...
Click to collapse
Are you in the fastboot mode? I mean you booted your phone into the bootloader.. then you chose "fastboot" and after this there's written "FASTBOOT USB"? and then you got this waiting for device? because simply being in hboot doesn't allow you to use fastboot commands. Sorry if this is a noob question.. but if your device wasn't recognized.. this would be f***ing difficult to get anything running again. This bug with the recovery.. hmmm... don't boot into recovery again.. recovery is connected to adb not fastboot... and to calm down.. here we have a RUU to get back stock(don't use it right now):
http://www.androidruu.com/getdownlo...50.20_10.40.1150.04_release_324846_signed.exe

have you tried re flashing a new recovery via fastboot?

LibertyMarine said:
Are you in the fastboot mode? I mean you booted your phone into the bootloader.. then you chose "fastboot" and after this there's written "FASTBOOT USB"? and then you got this waiting for device? because simply being in hboot doesn't allow you to use fastboot commands. Sorry if this is a noob question.. but if your device wasn't recognized.. this would be f***ing difficult to get anything running again. This bug with the recovery.. hmmm... don't boot into recovery again.. recovery is connected to adb not fastboot... and to calm down.. here we have a RUU to get back stock(don't use it right now):
Click to expand...
Click to collapse
Nope, the phone is currently displaying "FASTBOOT USB" in red and I have the following selectable options on the screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN

khhhhris said:
have you tried re flashing a new recovery via fastboot?
Click to expand...
Click to collapse
I would flash a new recovery, but my computer doesn't seem to be recognizing my device. It does for a second during boot into recovery, but once the recovery crashes and the phone resets, the phone disappears from device manager. It doesn't show backup when I'm in FASTBOOT USB.
I'm going to try it on a coworkers computer.

Caboose127 said:
Nope, the phone is currently displaying "FASTBOOT USB" in red and I have the following selectable options on the screen:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Click to expand...
Click to collapse
this is weird... try another computer. Try different drivers from here:
http://forum.xda-developers.com/showthread.php?t=2191279
TRY EVERYTHING GO GET THE COMPUTER RECOGNIZING YOUR HTC ONE
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
khhhhris said:
have you tried re flashing a new recovery via fastboot?
Click to expand...
Click to collapse
...lol this would be funny.. maybe his recovery partition is corrupt.. hmmm then we'd have to use different error handling strategies...

Progress! I was able to get fastboot working on my coworkers computer: Here's the gitvar results:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****************
(bootloader) imei: *****************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4267mV
(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.047s
Click to expand...
Click to collapse
The phone shows up in Device Manager when I'm in FASTBOOT USB, but not when I'm in HBOOT. I still can't do anything with ADB.
I was able to flash a new recovery with FASTBOOT, but that recovery crashed as well.

If you are still trying for your computer to recognize the adb device and still hasn't then just buy an USB OTG then put an USB to flash a rom from there.
http://www.androidapps4u.com/temp/screenshot_3-usb-otg-cable.jpg

Define crashed? TWRP 2.6.3.0 ? or CWM ? What happens in recovery mode?

Caboose127 said:
Progress! I was able to get fastboot working on my coworkers computer: Here's the gitvar results:
The phone shows up in Device Manager when I'm in FASTBOOT USB, but not when I'm in HBOOT. I still can't do anything with ADB.
I was able to flash a new recovery with FASTBOOT, but that recovery crashed as well.
Click to expand...
Click to collapse
adb commands won't work while in fastboot mode/bootloader. fastboot needs to be used while in fastboot mode. While your in fastboot, try
fastboot erase cache
Then fastboot flash your recovery again (fastboot flash recovery nameofrecovery.img), and try to access recovery

Thanks for all of your help guys. I finally got it working.

For everyone else reference, mark your thread [SOLVED] and post a brief description how you fixed it..

Thanks guys for helping me out!

Can not write anything via Fastboot and Phone is in Bootloop :( kindly Help!

I am unable to write any thing via bootloaders (i.e. recovery, zip, ruu etc) i have also tried to restore my phone via RUU...setup is shutting down the device but do not boot it up again in bootloader so the setup could proceed with flashing the RUU (as it suppose to)... i m uploading the cmd screen shot for your kind perusal, kindly help me out as well please...
these steps i have tried as yet:
tried (fastboot flash recovery twrp.img)
Tried Flashing OTA firmware (fastboot update firmware.zip)
Tried RUU.exe setup
i can not even flash recovery... whenever i attempt to do so it gives an error as attached!
seems like some sort of security has been activated but can be a hardware issue as well... Please HELP!
Please advise what should i do or what can be done in this matter

Have you tried fastboot erase cache
Sent from my HTC One using XDA Premium 4 mobile app

Try going s off
Sent from my GT-I9305 using xda app-developers app

bored_stupid said:
Have you tried fastboot erase cache
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did... command is not implementing... giving out same error as on recovery flsah!
Thanks... will appreciate more help...

nateboi81 said:
Try going s off
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
i have tried that...
my set is only responding to informational commands like getvar info, device info etc but its not implementing the commands which will write something on internal memory...
s-off = Security off right?
i believe some sort of security has been triggered!

?
Any One please....

Just a couple of shots in the dark.. disable any antivirus also check you have latest fastboot maybe download latest android sdk which will have it and try again.
Try another pc or cable.
Sent from my HTC One using Tapatalk

Mortal Eternity said:
Any One please....
Click to expand...
Click to collapse
are you using USB 3 port/hub, check Device Manager connections... if the "main" (internal) port-structure is USB 3 based, then that could be the problem.
PS: and what version does adb devices give?

nkk71 said:
are you using USB 3 port/hub, check Device Manager connections... if the "main" (internal) port-structure is USB 3 based, then that could be the problem.
PS: and what version does adb devices give?
Click to expand...
Click to collapse
I can offer 20$ for who ever can help me fix my set please...(i know its too low but its all i have for now and i need my cellphone fixed to sale it)
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35FW902658
(bootloader) imei: 355972054420881
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4157mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 1.342s
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>

Mortal Eternity said:
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 1.342s
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>
Click to expand...
Click to collapse
what was the last thing the phone had on it ? I see the bootloader is unlocked so did it already have a custom recovery ? custom rom ? Rooted ?
have you turned the phone completely OFF holding the powerbutton and volume up and down for 2 min ?
did you try a factory reset with stock recovery ?
when you tried the RUU.exe what was the error and what file did you try ?

clsA said:
what was the last thing the phone had on it ? I see the bootloader is unlocked so did it already have a custom recovery ? custom rom ? Rooted ?
have you turned the phone completely OFF holding the powerbutton and volume up and down for 2 min ?
did you try a factory reset with stock recovery ?
when you tried the RUU.exe what was the error and what file did you try ?
Click to expand...
Click to collapse
thats how i messed my set up: i was on TWRP 2.6.3.3 which was working perfectly fine then i thought it would be better if i'd flash a latest recovery so flashed 2.7.0.4 then i tried to flash latest build of insertcoin with that messed up recovery which got me stuck on 7% while flashing the rom, so i restarted by set after waiting for 5 minutes or so... then i tried going in to recovery again and tried to do a factory data reset to reflash the rom... recovery stuck on factory data rest n made me reboot my set... since then the situation is same for me
i did the 2 minutes trick, since my phone is not hard bricked so its just making the set booting again and again in fastboot mode thats it!
yes i did factory reset but with twrp then i got stuck at where i m now... plus i m unable to flash anything on emmc since then...
when i tried RUU.exe the setup shut my phone down but do not restart it in fastboot mode (how it should) i tried to boot my phone manually but didnt help...
Please advice any thing else

2.7.0.4 is for Sprint
Can you force the phone into fastboot oem rebootRUU and try and flash from their?
you can extract the signed Rom.zip from the RUU and flash it that way
the Rom.zip will be in c:\users\yourusername\appdata\local\temp\somerandomfolderthatwasjustcreated (sort by date)(also you have to view hidden folders to see appdata in the user folder)
mine was here "C:\Users\Cliff\AppData\Local\Temp\{A3096E6D-C55A-4EA1-B6B1-1E95174B190C}"

clsA said:
2.7.0.4 is for Sprint
Can you force the phone into fastboot oem rebootRUU and try and flash from their?
you can extract the signed Rom.zip from the RUU and flash it that way
the Rom.zip will be in c:\users\yourusername\appdata\local\temp\somerandomfolderthatwasjustcreated (sort by date)(also you have to view hidden folders to see appdata in the user folder)
mine was here "C:\Users\Cliff\AppData\Local\Temp\{A3096E6D-C55A-4EA1-B6B1-1E95174B190C}"
Click to expand...
Click to collapse
i flashed the recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2708134 (its not for sprint only - at least its not written in this thread)
No i can't bro... it says this when i tried to run the command:
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.060s]
finished. total time: 1.061s
Thank you for helping me...

Mortal Eternity said:
i flashed the recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2708134 (its not for sprint only - at least its not written in this thread)
No i can't bro... it says this when i tried to run the command:
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.060s]
finished. total time: 1.061s
Thank you for helping me...
Click to expand...
Click to collapse
I think your emmc has bad sectors. Whats wrong with htc one? So many bricks because of bad dmmc chip. Jesus

Mortal Eternity said:
i flashed the recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2708134 (its not for sprint only - at least its not written in this thread)
No i can't bro... it says this when i tried to run the command:
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.060s]
finished. total time: 1.061s
Thank you for helping me...
Click to expand...
Click to collapse
Have you at least tried a different PC and/or OS? I remember one guy having tonnes of problems (and we spent hours on teamviewer too), not being able to get anything to work, until we found out that even his USB2 port is based on an internal USB3 connection... he then used a different PC and was up and running again!

Mortal Eternity said:
i flashed the recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2708134 (its not for sprint only - at least its not written in this thread)
...
Click to expand...
Click to collapse
Thanks for posting the link .. i was not aware of that file.
I think I would still try and flashback to 2.6.3.3 ... if you can get back in TWRP
try this file >> https://www.dropbox.com/s/n49t43thctnl02a/TWRP_2.6.3.3_m7.zip

clsA said:
Thanks for posting the link .. i was not aware of that file.
I think I would still try and flashback to 2.6.3.3 ... if you can get back in TWRP
try this file >> https://www.dropbox.com/s/n49t43thctnl02a/TWRP_2.6.3.3_m7.zip
Click to expand...
Click to collapse
recovery is not accessible... when ever i select the recovery option the set gets unresponsive
can't even factory data reset my phone... sent an email to htc saying if they can replace my set i will pay 100$ t has been 2 days, still waiting for their reply...
lets hope for best :fingers-crossed:

nkk71 said:
Have you at least tried a different PC and/or OS? I remember one guy having tonnes of problems (and we spent hours on teamviewer too), not being able to get anything to work, until we found out that even his USB2 port is based on an internal USB3 connection... he then used a different PC and was up and running again!
Click to expand...
Click to collapse
thanks for your suggestion but its not the cable or port issue i have tried 5 different pcs... i have even visited local market for solution... no one has any solutions for this as yet... but there are many phones with same case... it seems like a hardware flaw at htc's end.
p.s. i m really very thankfull to people who are trying to help me!

darksnoopy said:
I think your emmc has bad sectors. Whats wrong with htc one? So many bricks because of bad dmmc chip. Jesus
Click to expand...
Click to collapse
yes it seems like a common issue to me now... lets hope htc will take some precaution while making such expensive phones...

Mortal Eternity said:
yes it seems like a common issue to me now... lets hope htc will take some precaution while making such expensive phones...
Click to expand...
Click to collapse
Tell me about it! I got an new m7 again (i hate m8 design) but this time i am not going to unlock boot loader not going to s-off and not going to install custom recovery!
This is the thread with the problem i had with my first m7. I haven't quit, still trying to fix it and give it away. Maybe we should make a sticky thread with all those people with problem like this!
http://forum.xda-developers.com/showthread.php?t=2685024&page=3

[Q] MODs Please close this thread!!!!! Thank you

MODs please delete this thread
Hi all,
I've been wrecking my brains out, can anyone help.
My M7ul is stuck in recovery loop, doesn't matter what rom I push using adb and flash it keeps on going booting into recovery. I cannot change the recovery from TWRP even tho using adb it says I have tried to flash new recovery twrp and cwm it still reverts back to twrp 2.6.3.3.
I have also used the method http://android-revolution-hd.blogspot.nl/2013/10/fix-data-htc-one.html to wipe the data partition, it shows that it has wiped it but as it reboots all the files that were suppose to be wiped is still there.
I have tried to load stock rom but as soon as it restarts to load the bootloader the phone boots into recovery and the pc doesn't pick up the phone and the process stops. I have tried to relock the bootloader and it doesn't lock.
Any ideas and help would be appreciated.

touchplus said:
Hi all,
I've been wrecking my brains out, can anyone help.
My M7ul is stuck in recovery loop, doesn't matter what rom I push using adb and flash it keeps on going booting into recovery. I cannot change the recovery from TWRP even tho using adb it says I have tried to flash new recovery twrp and cwm it still reverts back to twrp 2.6.3.3.
I have also used the method http://android-revolution-hd.blogspot.nl/2013/10/fix-data-htc-one.html to wipe the data partition, it shows that it has wiped it but as it reboots all the files that were suppose to be wiped is still there.
I have tried to load stock rom but as soon as it restarts to load the bootloader the phone boots into recovery and the pc doesn't pick up the phone and the process stops. I have tried to relock the bootloader and it doesn't lock.
Any ideas and help would be appreciated.
Click to expand...
Click to collapse
Try to flash a boot.img from you rom. You might have wiped it out.

Thank you, I'll try that and let you know.
Update;
no luck, it still reverts into the recovery loop.

touchplus said:
Thank you, I'll try that and let you know.
Update;
no luck, it still reverts into the recovery loop.
Click to expand...
Click to collapse
When you flashed the new recovery did you use the following commands:
In bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
If you don't erase the cache after you flash the recovery it does take properly.
You might give this new version of TWRP a try.

Hi Majmoz
I am grateful for your time in helping me, but I am not having any luck.
I have followed your instruction but to no avail, for some reason it will not flash a new recovery, the adb process shows its writing but it defaults back to the twrp 2.6.3.3. I have tried flashing the new one you linked and CWM but keeps on reverting back. The phone goes into the htc logo for about 10 sec and restarts again into old recovery.

touchplus said:
Hi Majmoz
I am grateful for your time in helping me, but I am not having any luck.
I have followed your instruction but to no avail, for some reason it will not flash a new recovery, the adb process shows its writing but it defaults back to the twrp 2.6.3.3. I have tried flashing the new one you linked and CWM but keeps on reverting back. The phone goes into the htc logo for about 10 sec and restarts again into old recovery.
Click to expand...
Click to collapse
@alray or @nkk71 Can you help with this.
touchplus: Can you post a fastboot getvar all with the imei and serialno removed? I think you will need a RUU to put all the pieces back together.

touchplus said:
Hi all,
I've been wrecking my brains out, can anyone help.
My M7ul is stuck in recovery loop, doesn't matter what rom I push using adb and flash it keeps on going booting into recovery. I cannot change the recovery from TWRP even tho using adb it says I have tried to flash new recovery twrp and cwm it still reverts back to twrp 2.6.3.3.
I have also used the method http://android-revolution-hd.blogspot.nl/2013/10/fix-data-htc-one.html to wipe the data partition, it shows that it has wiped it but as it reboots all the files that were suppose to be wiped is still there.
I have tried to load stock rom but as soon as it restarts to load the bootloader the phone boots into recovery and the pc doesn't pick up the phone and the process stops. I have tried to relock the bootloader and it doesn't lock.
Any ideas and help would be appreciated.
Click to expand...
Click to collapse
I hate to be the bearer of bad news, but this sounds like a hardware problem. I've seen one or two other people whose phones were "stuck in time", the ROM would boot up fine, but upon every reboot it would revert back to a previous state, even files (eg pictures) that were added or deleted would revert back.
TWRP 2.6.3.3 should be good for any ROM.
So first make sure you bootloader is UNLOCKED, then copy/paste command prompt output of everything you do, please check the Frequently Asked Question sticky page 3
and do all the steps mentioned there, in particular step D which will truly format everything (like the fix-data-htc-one article).
copy/paste your output back here, maybe we can spot something
best of luck

details
majmoz said:
@alray or @nkk71 Can you help with this.
touchplus: Can you post a fastboot getvar all with the imei and serialno removed? I think you will need a RUU to put all the pieces back together.
Click to expand...
Click to collapse
Hi Majmoz,
Here are the details, thanks again
c:\mini>fastboot getvar all
< waiting for device >
(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.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH38**********
(bootloader) imei: 357****************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3717mV
(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!
I have downloaded the RUU from htcguru for HTC_001 but can't seem to load it on the phone, the ruu process goes to the first stage and reboots the phone and says waiting for bootloader but the phone boots up and goes straight into the htc logo and then restarts again and enters into recovery. I have tried to force the phone into bootloader mode after restart but it won't recognise the phone and installation process timeouts
Thank you again

nkk71 said:
I hate to be the bearer of bad news, but this sounds like a hardware problem. I've seen one or two other people whose phones were "stuck in time", the ROM would boot up fine, but upon every reboot it would revert back to a previous state, even files (eg pictures) that were added or deleted would revert back.
TWRP 2.6.3.3 should be good for any ROM.
So first make sure you bootloader is UNLOCKED, then copy/paste command prompt output of everything you do, please check the Frequently Asked Question sticky page 3
and do all the steps mentioned there, in particular step D which will truly format everything (like the fix-data-htc-one article).
copy/paste your output back here, maybe we can spot something
best of luck
Click to expand...
Click to collapse
Hi nkk71,
Thank you for getting involved in helping me, I have followed all steps from A -G
A- Please see attached image
B- I am able to get to into the bootloader- the bootloader is unlocked and has the word tampered written on top
C-
c:\mini>adb version
Android Debug Bridge version 1.0.31
c:\mini>fastboot devices
SH38XXXXXXXX fastboot
c:\mini>fastboot flash recovery twrp-2.7.1.2-m7.img (the recovery didn't update to 2.7.1.2 as you can see in the picture it reverted back)
sending 'recovery' (9940 KB)... OKAY
writing 'recovery'... OKAY
c:\mini>fastboot erase cache
erasing 'cache'... OKAY
c:\mini>fastboot reboot-bootloader
rebooting into bootloader... OKAY
D- See attached pictures
E- I have pushed the rom into the phone and installed it, it goes through the installation process without errors and reboots into htc logo for about 10 sec and then reboots again and goes back into recovery
F- Windows recognizes the phone
G- doesn't go through the bootup cycle instead phone starts and hangs at HTC logo for about 10 sec and restarts into recovery.
H- I have added an additional picture as I did a imgcrc in the bootloader menu just incase there is information that may help.
Thank you again.

found an error
Hi Guys,
I did another check using this command /sbin/e2fsck -n -f /dev/block/mmcblk0p37 listed on http://android-revolution-hd.blogspot.co.uk/2013/10/fix-data-htc-one.html. There is an error that showed up could this be the problem and if so how can I fix this, I have already tried the process from the link about 3 times but that error isn't fixed.
c:\mini>adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (1914292, counted=976600).
Fix? no
Free inodes count wrong (1677448, counted=1677418).
Fix? no
/dev/block/mmcblk0p37: ********** WARNING: Filesystem still has errors *********
*
/dev/block/mmcblk0p37: 26488/1703936 files (3.4% non-contiguous), 4901452/681574
4 blocks

touchplus said:
Hi nkk71,
Thank you for getting involved in helping me, I have followed all steps from A -G
H- I have added an additional picture as I did a imgcrc in the bootloader menu just incase there is information that may help.
Thank you again.
Click to expand...
Click to collapse
I think it's a hardware problem
the part where the rpm crc checksum is only 7 characters is not a good sign, and if you're flashing 2.1.7.2 properly, but it's still stuck with 2.6.3.3 would lead me to say it's a hardware issue.
you can still try running the 4.19.401.9 ruu: http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
you'll need to relock bootloader since you are S-ON, using "fastboot oem lock" for the RUU to be able to install
Best of luck
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
touchplus said:
Hi Guys,
I did another check using this command /sbin/e2fsck -n -f /dev/block/mmcblk0p37 listed on http://android-revolution-hd.blogspot.co.uk/2013/10/fix-data-htc-one.html. There is an error that showed up could this be the problem and if so how can I fix this, I have already tried the process from the link about 3 times but that error isn't fixed.
c:\mini>adb shell /sbin/e2fsck -n -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (1914292, counted=976600).
Fix? no
Free inodes count wrong (1677448, counted=1677418).
Fix? no
/dev/block/mmcblk0p37: ********** WARNING: Filesystem still has errors *********
*
/dev/block/mmcblk0p37: 26488/1703936 files (3.4% non-contiguous), 4901452/681574
4 blocks
Click to expand...
Click to collapse
yep, looks bad, you've already done two full formats (one using the original mk2fs and one using twrp), and the error comes back -> bad chip, needs a motherboard replacement
sorry

nkk71 said:
I think it's a hardware problem
the part where the rpm crc checksum is only 7 characters is not a good sign, and if you're flashing 2.1.7.2 properly, but it's still stuck with 2.6.3.3 would lead me to say it's a hardware issue.
you can still try running the 4.19.401.9 ruu: http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
you'll need to relock bootloader since you are S-ON, using "fastboot oem lock" for the RUU to be able to install
Best of luck
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
yep, looks bad, you've already done two full formats (one using the original mk2fs and one using twrp), and the error comes back -> bad chip, needs a motherboard replacement
sorry
Click to expand...
Click to collapse
Hi nkk71 and Majmoz,
Thank you very much for all your help. I guess its a dead end then :crying:,
I just wanted to try one last thing before I give up, but having a slight problem, I want force it load an RUU but I can't lock the bootloader, the phone restarts after the adb command but doesn't lock the bootloader, if I could somehow lock the bootloader then maybe I can try and load the RUU. If you have any ideas on how else I can lock the bootloader that would be a great.
this what I get from adb
c:\mini>fastboot oem lock
... (bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
When I attempt to put the phone in ruu mode using adb command the phone restarts and goes back into recovery- so this options doesn't work any other options you may have would be great
c:\mini>fastboot oem rebootRUU
< waiting for device >
... (bootloader) Start Verify: 3
OKAY

Htc desire 510 64 bit uk ( revert back to stock )

REVERT BACK TO FULL STOCK HTC DESIRE 510 64 BIT UK EE/ORANGE (SOLVED)​
UNLOCKED BOOTLOADER IS NEEDED FOR THIS SO IF YOU DO NOT HAVE A UNLOCKED BOOTLOADER UNLOCK IT FIRST AT HTCDEV. I AM WRITING THE GUIDE TO HELP THOSE WHO HAVE THE HTC DESIRE 510 64 BIT UK VERSION ON EE/ORANGE AND ARE TRYING TO REVERT BACK TO FULL STOCK. IT MAY HELP THOSE ON OTHER NETWORKS BUT TRY AT YOUR OWN RISK. I HAVE NOTICED THAT THERE ARE NOT MANY ROMS ABOUT FOR THIS PHONE STOCK OR CUSTOM. MY 510 WAS GREAT UP UNTILL I STARTED TO CUSTOMISE IT. CUSTOM RECOVERY ROOT ECT. IT ALL WENT WELL UNTILL I NOTICED I HAD SOME NASTY RED WRITING EVERY TIME I TURNED MY PHONE ON. SOMETHING ABOUT HTC DEVELOPMENT. I ALSO NOTICED THAT OTA UPDATES WERE NOT INSTALLING. F**k THIS I THOUGHT TIME TO REVERT BACK TO FULL UNROOTED STOCK BUT THIS WAS NOT AS SIMPLE AS I THOUGHT IT WOULD BE AS I COULD NOT FIND ANY DESIRE 510 64 BIT UK STOCK ROMS ANYWHERE ON THE NET. I HAVE MANAGED TO GET A STOCK ROM AND REMOVED THE ROOT. I HAVE ALSO MANAGED TO GET A STOCK RECOVER.img. THE WHOLE PROCESS WILL TAKE LESS THAN 1 HOUR IF YOU KNOW WHAT YOU ARE DOING. DO THIS PROCESS AT YOUR OWN RISK. YOU WILL NEED TO HAVE A UNLOCKED BOOTLOADER. NO S-OFF IS NEEDED. OK LETS GET STARTED
DOWNLOAD FILES HERE https://onedrive.live.com/download?...!362&authkey=!AJe2kEJ0umuLUT0&ithint=file,zip
ENTER FASTBOOT MODE ON PHONE (hold volume down button and power button at the same time)
START FAST BOOT PROGRAMME ON PC (open adb folder and place mouse pointer on a blank space within the folder and hold tab key while pressing right mouse key then select open command window here)
WE WILL BE DOING THE PROCESS IN THIS ORDER
1 FLASH CWM RECOVERY.IMG ( WITH FASTBOOT )
2 INSTALL STOCK ROM.ZIP FROM SD CARD ( FROM CWM MENU )
3 INSTALL STOCK RECOVERY.IMG ( WITH FASTBOOT )
4 RE LOCK BOOTLOADER ( WITH FASTBOOT )
1ST PUT THE PHONE IN FASTBOOT MODE AND CONNECT TO THE PC. START FASTBOOT PROGRAMME AND ENTER THIS FASTBOOT COMMAND AND PRESS ENTER. fastboot flash recovery recoverycwm.img WHEN THIS HAS FINISHED POWER OFF THE PHONE BY REMOVING THE BATTERY THEN PUT IT BACK IN.
2ND PUT THE STOCK ROM ON SD CARD AND PUT IT IN THE PHONE. ENTER CWM RECOVERY ON THE PHONE BY GOING INTO FASTBOOT MODE AND SCROLLING DOWN TO RECOVERY AND PRESS POWER BUTTON. ONCE IN RECOVERY MODE CLEAR ALL THE CATCHES ( i formatted everything apart from the sd card ). NOW INSTALL THE ROM ZIP. RESTART THE PHONE AND ENABLE USB DEBUGING MODE THEN POWER OFF THE PHONE AND REMOVE THE BATTERY THEN PUT IT BACK IN.
3. NOW POWER THE PHONE BACK ON INTO FASTBOOT MODE AND CONNECT IT TO THE PC. START THE FASTBOOT PROGRAMME AND TYPE THE FOLLOWING COMMAND fastboot flash recovery recovery-update.img THEN PRESS ENTER. ONCE COMPLETE TURN OFF THE PHONE BY REMOVING THE BATTERY AND PUTTING IT BACK IN.
4. NOW POWER ON THE PHONE INTO FASTBOOT MODE AND CONNECT TO THE PC. START THE FASTBOOT PROGRAMME AND ENTER THE FOLLOWING COMMAND fastboot oem lock AND PRESS ENTER. YOUR PHONE WILL RESTART. JOB DONE
YOU WILL NOW BE BACK ON STOCK FIRMWARE WITH A STOCK UNROOTED KERNEL AND A STOCK RECOVER MENU AND LOCKED BOOTLOADER. THE RED WRITING ON THE HTC SPLASH SCREEN WILL BE GONE AND OTA UPDATES WILL NOW WORK. :good:

where do i find the link?
Where is the link you said to get the required files?
Thanks in advance for this post, i hope it works

frodoor said:
Where is the link you said to get the required files?
Thanks in advance for this post, i hope it works
Click to expand...
Click to collapse
I cant upload the files as i am new to xda but if you want to give me your email address i can forward a a download link.

ANDROIDGEEK072 said:
I cant upload the files as i am new to xda but if you want to give me your email address i can forward a a download link.
Click to expand...
Click to collapse
Yes please i sent a PM with my email,
Thank you :good:
Email: [email protected]

Hey .. Mine is from boost mobile, hope this work on here too. Send me the links too on [email protected]
Thanks in advance

frodoor said:
Yes please i sent a PM with my email,
Thank you :good:
Email: [email protected]
Click to expand...
Click to collapse
Glad it worked for you my friend. Can you leave a comment in the post to let others know that it worked for you. Nice one :good:

ANDROIDGEEK072 said:
Glad it worked for you my friend. Can you leave a comment in the post to let others know that it worked for you. Nice one :good:
Click to expand...
Click to collapse
Download link now added good luck

kudokunnn said:
Hey .. Mine is from boost mobile, hope this work on here too. Send me the links too on [email protected]
Thanks in advance
Click to expand...
Click to collapse
Download link added

ANDROIDGEEK072 said:
Download link added
Click to expand...
Click to collapse
Hi, thank you for rom, but not working for me... Last part.
C:\Users\Nerijus\Desktop\HTC DESIRE 510 64 BIT UK\adb> fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: -4
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.132s
When i rebooted device htc sreen freeze (without red letters ), waited for 30 minutes and nothing... sry for my english

Can u send me the links....my email adrress is [email protected]

Nerijus87 said:
Hi, thank you for rom, but not working for me... Last part.
C:\Users\Nerijus\Desktop\HTC DESIRE 510 64 BIT UK\adb> fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: -4
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.132s
When i rebooted device htc sreen freeze (without red letters ), waited for 30 minutes and nothing... sry for my english
Click to expand...
Click to collapse
Are you sure that your phone is a 64 bit version also this method requires a unlocked bootloader. This rom is for EE network

ANDROIDGEEK072 said:
Are you sure that your phone is a 64 bit version also this method requires a unlocked bootloader. This rom is for EE network
Click to expand...
Click to collapse
Forgot to say that it will say failed but it should still lock your bootloader. Sounds like you may have a 32 bit phone this is why it is stuck on htc screen or you did not flash the recovery.

Ummm:
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: -4
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.149s
C:\adb>
And it just keeps rebooting....

maksimkooo98 said:
Ummm:
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: -4
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.149s
C:\adb>
And it just keeps rebooting....
Click to expand...
Click to collapse
Let me ask you this question because I'm looking at the info you put on here from your phone so... WHAT kind of phone is that? I need the name, the MODEL number and everything... EVEN your HBoot screen info too... Type it ALL in here!!!

Please send me to [email protected]. thank you in advance

MrMike2182 said:
Let me ask you this question because I'm looking at the info you put on here from your phone so... WHAT kind of phone is that? I need the name, the MODEL number and everything... EVEN your HBoot screen info too... Type it ALL in here!!!
Click to expand...
Click to collapse
***RELOCKED***
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-01.02.012_U10251_39.O8.40922
OS-
eMMC-boot 1024MB
Aug 10 2015, 17:43:35.0
HTC Desire 510 model number: 0PCV200

Mine is a boost mobile....can u suggest me a link where reverting back to stock for boost mobile is given...
Im asking this particularly bcoz u said that it is for ee network....

ANDROIDGEEK072 said:
REVERT BACK TO FULL STOCK HTC DESIRE 510 64 BIT UK EE/ORANGE (SOLVED)​
UNLOCKED BOOTLOADER IS NEEDED FOR THIS SO IF YOU DO NOT HAVE A UNLOCKED BOOTLOADER UNLOCK IT FIRST AT HTCDEV. I AM WRITING THE GUIDE TO HELP THOSE WHO HAVE THE HTC DESIRE 510 64 BIT UK VERSION ON EE/ORANGE AND ARE TRYING TO REVERT BACK TO FULL STOCK. IT MAY HELP THOSE ON OTHER NETWORKS BUT TRY AT YOUR OWN RISK. I HAVE NOTICED THAT THERE ARE NOT MANY ROMS ABOUT FOR THIS PHONE STOCK OR CUSTOM. MY 510 WAS GREAT UP UNTILL I STARTED TO CUSTOMISE IT. CUSTOM RECOVERY ROOT ECT. IT ALL WENT WELL UNTILL I NOTICED I HAD SOME NASTY RED WRITING EVERY TIME I TURNED MY PHONE ON. SOMETHING ABOUT HTC DEVELOPMENT. I ALSO NOTICED THAT OTA UPDATES WERE NOT INSTALLING. F**k THIS I THOUGHT TIME TO REVERT BACK TO FULL UNROOTED STOCK BUT THIS WAS NOT AS SIMPLE AS I THOUGHT IT WOULD BE AS I COULD NOT FIND ANY DESIRE 510 64 BIT UK STOCK ROMS ANYWHERE ON THE NET. I HAVE MANAGED TO GET A STOCK ROM AND REMOVED THE ROOT. I HAVE ALSO MANAGED TO GET A STOCK RECOVER.img. THE WHOLE PROCESS WILL TAKE LESS THAN 1 HOUR IF YOU KNOW WHAT YOU ARE DOING. DO THIS PROCESS AT YOUR OWN RISK. YOU WILL NEED TO HAVE A UNLOCKED BOOTLOADER. NO S-OFF IS NEEDED. OK LETS GET STARTED
DOWNLOAD FILES HERE https://onedrive.live.com/download?...!362&authkey=!AJe2kEJ0umuLUT0&ithint=file,zip
ENTER FASTBOOT MODE ON PHONE (hold volume down button and power button at the same time)
START FAST BOOT PROGRAMME ON PC (open adb folder and place mouse pointer on a blank space within the folder and hold tab key while pressing right mouse key then select open command window here)
WE WILL BE DOING THE PROCESS IN THIS ORDER
1 FLASH CWM RECOVERY.IMG ( WITH FASTBOOT )
2 INSTALL STOCK ROM.ZIP FROM SD CARD ( FROM CWM MENU )
3 INSTALL STOCK RECOVERY.IMG ( WITH FASTBOOT )
4 RE LOCK BOOTLOADER ( WITH FASTBOOT )
1ST PUT THE PHONE IN FASTBOOT MODE AND CONNECT TO THE PC. START FASTBOOT PROGRAMME AND ENTER THIS FASTBOOT COMMAND AND PRESS ENTER. fastboot flash recovery recoverycwm.img WHEN THIS HAS FINISHED POWER OFF THE PHONE BY REMOVING THE BATTERY THEN PUT IT BACK IN.
2ND PUT THE STOCK ROM ON SD CARD AND PUT IT IN THE PHONE. ENTER CWM RECOVERY ON THE PHONE BY GOING INTO FASTBOOT MODE AND SCROLLING DOWN TO RECOVERY AND PRESS POWER BUTTON. ONCE IN RECOVERY MODE CLEAR ALL THE CATCHES ( i formatted everything apart from the sd card ). NOW INSTALL THE ROM ZIP. RESTART THE PHONE AND ENABLE USB DEBUGING MODE THEN POWER OFF THE PHONE AND REMOVE THE BATTERY THEN PUT IT BACK IN.
3. NOW POWER THE PHONE BACK ON INTO FASTBOOT MODE AND CONNECT IT TO THE PC. START THE FASTBOOT PROGRAMME AND TYPE THE FOLLOWING COMMAND fastboot flash recovery recovery-update.img THEN PRESS ENTER. ONCE COMPLETE TURN OFF THE PHONE BY REMOVING THE BATTERY AND PUTTING IT BACK IN.
4. NOW POWER ON THE PHONE INTO FASTBOOT MODE AND CONNECT TO THE PC. START THE FASTBOOT PROGRAMME AND ENTER THE FOLLOWING COMMAND fastboot oem lock AND PRESS ENTER. YOUR PHONE WILL RESTART. JOB DONE
YOU WILL NOW BE BACK ON STOCK FIRMWARE WITH A STOCK UNROOTED KERNEL AND A STOCK RECOVER MENU AND LOCKED BOOTLOADER. THE RED WRITING ON THE HTC SPLASH SCREEN WILL BE GONE AND OTA UPDATES WILL NOW WORK. :good:
Click to expand...
Click to collapse
hey, thank you for this tutorial, i need download link to the rest of the files....

Thanks
ANDROIDGEEK072 said:
REVERT BACK TO FULL STOCK HTC DESIRE 510 64 BIT UK EE/ORANGE (SOLVED)​
UNLOCKED BOOTLOADER IS NEEDED FOR THIS SO IF YOU DO NOT HAVE A UNLOCKED BOOTLOADER UNLOCK IT FIRST AT HTCDEV. I AM WRITING THE GUIDE TO HELP THOSE WHO HAVE THE HTC DESIRE 510 64 BIT UK VERSION ON EE/ORANGE AND ARE TRYING TO REVERT BACK TO FULL STOCK. IT MAY HELP THOSE ON OTHER NETWORKS BUT TRY AT YOUR OWN RISK. I HAVE NOTICED THAT THERE ARE NOT MANY ROMS ABOUT FOR THIS PHONE STOCK OR CUSTOM. MY 510 WAS GREAT UP UNTILL I STARTED TO CUSTOMISE IT. CUSTOM RECOVERY ROOT ECT. IT ALL WENT WELL UNTILL I NOTICED I HAD SOME NASTY RED WRITING EVERY TIME I TURNED MY PHONE ON. SOMETHING ABOUT HTC DEVELOPMENT. I ALSO NOTICED THAT OTA UPDATES WERE NOT INSTALLING. F**k THIS I THOUGHT TIME TO REVERT BACK TO FULL UNROOTED STOCK BUT THIS WAS NOT AS SIMPLE AS I THOUGHT IT WOULD BE AS I COULD NOT FIND ANY DESIRE 510 64 BIT UK STOCK ROMS ANYWHERE ON THE NET. I HAVE MANAGED TO GET A STOCK ROM AND REMOVED THE ROOT. I HAVE ALSO MANAGED TO GET A STOCK RECOVER.img. THE WHOLE PROCESS WILL TAKE LESS THAN 1 HOUR IF YOU KNOW WHAT YOU ARE DOING. DO THIS PROCESS AT YOUR OWN RISK. YOU WILL NEED TO HAVE A UNLOCKED BOOTLOADER. NO S-OFF IS NEEDED. OK LETS GET STARTED
ENTER FASTBOOT MODE ON PHONE (hold volume down button and power button at the same time)
START FAST BOOT PROGRAMME ON PC (open adb folder and place mouse pointer on a blank space within the folder and hold tab key while pressing right mouse key then select open command window here)
WE WILL BE DOING THE PROCESS IN THIS ORDER
1 FLASH CWM RECOVERY.IMG ( WITH FASTBOOT )
2 INSTALL STOCK ROM.ZIP FROM SD CARD ( FROM CWM MENU )
3 INSTALL STOCK RECOVERY.IMG ( WITH FASTBOOT )
4 RE LOCK BOOTLOADER ( WITH FASTBOOT )
1ST PUT THE PHONE IN FASTBOOT MODE AND CONNECT TO THE PC. START FASTBOOT PROGRAMME AND ENTER THIS FASTBOOT COMMAND AND PRESS ENTER. fastboot flash recovery recoverycwm.img WHEN THIS HAS FINISHED POWER OFF THE PHONE BY REMOVING THE BATTERY THEN PUT IT BACK IN.
2ND PUT THE STOCK ROM ON SD CARD AND PUT IT IN THE PHONE. ENTER CWM RECOVERY ON THE PHONE BY GOING INTO FASTBOOT MODE AND SCROLLING DOWN TO RECOVERY AND PRESS POWER BUTTON. ONCE IN RECOVERY MODE CLEAR ALL THE CATCHES ( i formatted everything apart from the sd card ). NOW INSTALL THE ROM ZIP. RESTART THE PHONE AND ENABLE USB DEBUGING MODE THEN POWER OFF THE PHONE AND REMOVE THE BATTERY THEN PUT IT BACK IN.
3. NOW POWER THE PHONE BACK ON INTO FASTBOOT MODE AND CONNECT IT TO THE PC. START THE FASTBOOT PROGRAMME AND TYPE THE FOLLOWING COMMAND fastboot flash recovery recovery-update.img THEN PRESS ENTER. ONCE COMPLETE TURN OFF THE PHONE BY REMOVING THE BATTERY AND PUTTING IT BACK IN.
4. NOW POWER ON THE PHONE INTO FASTBOOT MODE AND CONNECT TO THE PC. START THE FASTBOOT PROGRAMME AND ENTER THE FOLLOWING COMMAND fastboot oem lock AND PRESS ENTER. YOUR PHONE WILL RESTART. JOB DONE
YOU WILL NOW BE BACK ON STOCK FIRMWARE WITH A STOCK UNROOTED KERNEL AND A STOCK RECOVER MENU AND LOCKED BOOTLOADER. THE RED WRITING ON THE HTC SPLASH SCREEN WILL BE GONE AND OTA UPDATES WILL NOW WORK. :good:
Click to expand...
Click to collapse
Thanks for the useful tutorial I flashed my Telstra brand 64 bit phone with this tutorial and it was successful.
the only issue I encountered was when I locked the bootloader in the end than the phone kept rebooring into bootloader. I realised that the Rooted bootloader is causing this So I flashed the supplied boot.img to the phone and voila it worked.
In my opinion we have to unroot the phone before locking the bootloader.
I still can see "software status : modified" and "Relocked" in the bootloader screen. I hope someone someday will find a way to clean this thing as well.

solution
maksimkooo98 said:
Ummm:
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [ERR] Failed to disable wdog debug: -4
(bootloader) [INFO] Calling SCM to disable SPMI PMIC arbiter
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.149s
C:\adb>
And it just keeps rebooting....
Click to expand...
Click to collapse
flash boot_signed.img to your phone which is inside the rom.zip. Same problem was with me and it did the trick.

Stuck in fastboot - No running ROM, recovery , ADB

Dear Community,
I reached a state with my mobile phone where I really do not know anymore how to proceed to get back to any running ROM on my HTC Mini 2. :angel:
I read the other threads on this topic, but they did not help my situation.
Maybe someone see's what I am missing, or what I can do about it. In the end, I would like to go back to a CM 11 / CM 13 ROM, but as I understood, I should first go back to stock to enable S-off, using a nandroid recovery backup. Then flash a new custom rom. However I am stuck without any recovery running properly. Only the hboot/fastboot menu is working, and the phone will always boot there again.
Some more info:
- ADB does not work currently. I tried Win and OSX , so I believe its the phone rejecting it.
- With stock recovery, reading in the 0P8BIMG.zip RUU file containing a 2.19.401.2 or 2.18.401.3 system fails.
- Flashing recovery TWRP 2.8.5.0 / 2.8.1.0 works, but the phone will not start it.
Code:
C:\Users\USER>fastboot flash recovery "Z:\Installs\HTC Mini 2\recovery-twrp-2.8.5.0.img"
sending 'recovery' (11796 KB)...
OKAY [ 1.393s]
writing 'recovery'...
OKAY [ 0.394s]
finished. total time: 1.790s
- My bootloader is ***Unlocked*** according to the fastboot screen. However, I cannot lock it :
Code:
C:\Users\USER>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) Start Verify: 3
(bootloader) WARM RESET: 8
(bootloader) [INFO] Reset reason in IMEM is 0x77665501
(bootloader) [INFO] Rebooting device
FAILED (status read failed (No such file or directory))
finished. total time: 1.056s
- Output of getvar all :
Code:
C:\Users\USER>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1102.19.1017
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: mem_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P8B20000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: be7179e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please let me know if I missed to provide important information.
Is there any way for me to start over on a lower level ? Or is a mobile shop / HTC my only solution left?
Thanks a lot for any feedback!
Greetings,
faiv

faiv said:
Dear Community,
I reached a state with my mobile phone where I really do not know anymore how to proceed to get back to any running ROM on my HTC Mini 2. :angel:
I read the other threads on this topic, but they did not help my situation.
Maybe someone see's what I am missing, or what I can do about it. In the end, I would like to go back to a CM 11 / CM 13 ROM, but as I understood, I should first go back to stock to enable S-off, using a nandroid recovery backup. Then flash a new custom rom. However I am stuck without any recovery running properly. Only the hboot/fastboot menu is working, and the phone will always boot there again.
Click to expand...
Click to collapse
you dont need S-OFF to install ROM just Bootloader unlocked.
Just because you can flash the recovery doesn't mean its the correct one, try the one in here
You need HTC drivers for ADB to work. (see link above)
After flashing recovery you can flash the rom using your preferred method.

kativiti said:
you dont need S-OFF to install ROM just Bootloader unlocked.
Just because you can flash the recovery doesn't mean its the correct one, try the one in here
You need HTC drivers for ADB to work. (see link above)
After flashing recovery you can flash the rom using your preferred method.
Click to expand...
Click to collapse
Thanks for your reply!
Unfortunately, it does not help. I flashed the recovery you suggested, and I still cannot boot into recovery.
Code:
C:\Users\oo>fastboot flash recovery C:\Users\USER\Downloads\twrp-2.8.1.0-20142812-memul.img
sending 'recovery' (10896 KB)...
OKAY [ 1.312s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.696s
I have the HTC Sync manager installed. Last time ,this was enough to get the drivers as well.
Just tested the other adb.exe plus the api as well. Does not work.

faiv said:
Thanks for your reply!
Unfortunately, it does not help. I flashed the recovery you suggested, and I still cannot boot into recovery.
Code:
C:\Users\oo>fastboot flash recovery C:\Users\USER\Downloads\twrp-2.8.1.0-20142812-memul.img
sending 'recovery' (10896 KB)...
OKAY [ 1.312s]
writing 'recovery'...
OKAY [ 0.378s]
finished. total time: 1.696s
I have the HTC Sync manager installed. Last time ,this was enough to get the drivers as well.
Just tested the other adb.exe plus the api as well. Does not work.
Click to expand...
Click to collapse
try to unlock bootloader again(just last step) , i remember having same kind of problem before, with the hboot.
and of course you are using original HTC cable?

kativiti said:
try to unlock bootloader again(just last step) , i remember having same kind of problem before, with the hboot.
and of course you are using original HTC cable?
Click to expand...
Click to collapse
I tried unlocking again already, but I must admit that you got me with the last one. I'm using other cables.....(there are many...how do I recognize the right one ? )
Will report back with the proper one, but I seriously believe that mine are fine.
Besides this, what would be your next guess ?

faiv said:
I tried unlocking again already, but I must admit that you got me with the last one. I'm using other cables.....(there are many...how do I recognize the right one ? )
Will report back with the proper one, but I seriously believe that mine are fine.
Besides this, what would be your next guess ?
Click to expand...
Click to collapse
ok we need to go step by step.
Check the shape of the cable maybe you'll get lucky. EBAY if not buy one. they are very cheap.
2nd in hboot try to enter recovery, if still error i need to know what it does, ei: black screen, red letters, etc.

kativiti said:
ok we need to go step by step.
Check the shape of the cable maybe you'll get lucky. EBAY if not buy one. they are very cheap.
2nd in hboot try to enter recovery, if still error i need to know what it does, ei: black screen, red letters, etc.
Click to expand...
Click to collapse
I'll tell you what it does, It stucks on red mark page and then black screen. So what is the problem ? If you don't answer my topic I write from another one !

blu3sm4n said:
I'll tell you what it does, It stucks on red mark page and then black screen. So what is the problem ? If you don't answer my topic I write from another one !
Click to expand...
Click to collapse
ok. so you dont have a recovery installed or its corrupted.
please be patience as every case its different and it takes trial and error until we figure out.
1-type command fastboot erase cache
2- flash stock recovery
3-relock oem. fastboot oem lock
in HBOOT enter recovery and erase phone. (NOTE: to enter recovery you need to press power+vol- after the red triangular)
4- get new token to unlock BOOTLOADER
5 -flash TWRP
all this because you need stock recovery to properly unlock bootloader.

kativiti said:
ok. so you dont have a recovery installed or its corrupted.
please be patience as every case its different and it takes trial and error until we figure out.
1-type command fastboot erase cache
2- flash stock recovery
3-relock oem. fastboot oem lock
in HBOOT enter recovery and erase phone. (NOTE: to enter recovery you need to press power+vol- after the red triangular)
4- get new token to unlock BOOTLOADER
5 -flash TWRP
all this because you need stock recovery to properly unlock bootloader.
Click to expand...
Click to collapse
Thanks for your help, first of all I can not unlock with Htcdev my bootloader. It is still locked. When I try to unlock and type unlock_code.bin, it asks me yes or no and I choose yes, it reboots and stucks on the logo screen again. I reboot again with volume down + power and see it is still "locked" .
When I try to flash stock recovery I type the flash recovery code and I get this message "writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)".. So Don't know what to do. I can not unlock, I can not flash recovery and I can not flash any stock rom because my main is : 2.19.401.2. So if I want to flash 2.18.401.3 RUU it says me your os is older. I am desperate I hope you can help dude. Thanks

blu3sm4n said:
Thanks for your help, first of all I can not unlock with Htcdev my bootloader. It is still locked. When I try to unlock and type unlock_code.bin, it asks me yes or no and I choose yes, it reboots and stucks on the logo screen again. I reboot again with volume down + power and see it is still "locked" .
When I try to flash stock recovery I type the flash recovery code and I get this message "writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)".. So Don't know what to do. I can not unlock, I can not flash recovery and I can not flash any stock rom because my main is : 2.19.401.2. So if I want to flash 2.18.401.3 RUU it says me your os is older. I am desperate I hope you can help dude. Thanks
Click to expand...
Click to collapse
ok so now you saying its LOCKED?
can yo send a hboot pic?
before trying next step..do you have an sdcard inserted in phone? if so remove and restart phone(corrupted sdcard will freeze phone logo)
if still stuck in logo try next step, if LOCKED
download RUU
- RENAME THE RUU FILE TO 0P8BIMG.zip AND PLACE IN THE ROOT OF SD CARD
- SWITCH OFF DEVICE
- HOLD VOL DOWN AND POWER KEY
- SOON AS DEVICE ENTER BOOT LOADERS IT WILL START READING THE PLACED FILE AND FLASHING SHOULD START SOON.

kativiti said:
ok so now you saying its LOCKED?
can yo send a hboot pic?
before trying next step..do you have an sdcard inserted in phone? if so remove and restart phone(corrupted sdcard will freeze phone logo)
if still stuck in logo try next step, if LOCKED
download RUU
- RENAME THE RUU FILE TO 0P8BIMG.zip AND PLACE IN THE ROOT OF SD CARD
- SWITCH OFF DEVICE
- HOLD VOL DOWN AND POWER KEY
- SOON AS DEVICE ENTER BOOT LOADERS IT WILL START READING THE PLACED FILE AND FLASHING SHOULD START SOON.
Click to expand...
Click to collapse
Yes it is LOCKED. I add HBOOT pic as atached, I tried to flash RUU but it says me "your main version is older " so i can not flash 2.18.401.3 RUU. I found this one (2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip )and tried to flash but it didn't work (on boot menu it says no image found)

blu3sm4n said:
Yes it is LOCKED. I add HBOOT pic as atached, I tried to flash RUU but it says me "your main version is older " so i can not flash 2.18.401.3 RUU. I found this one (2.19.401.2_boot_system_2015-09-21--20-48-04_KOT49H.zip )and tried to flash but it didn't work (on boot menu it says no image found)
Click to expand...
Click to collapse
thx for the picture.
you hboot shows that nothing has been done to the phone. so it was NEVER unlocked as stated in original post.
At this point im gonna suggest get your self an original usb cable because the one you using its no good. its giving you wrong info and it seems some get to the phone but corrupted and thats why unlock fails.
im trying to create a new updated RUU but might take some time.
please get OTA cable and try to unlock

You are right, it is never unlocked as I told you before. My cable is original itselfs cable. My phone is never unlocked, never rooted and never made s-off. So what do you suggest now ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi

blu3sm4n said:
You are right, it is never unlocked as I told you before. My cable is original itselfs cable. My phone is never unlocked, never rooted and never made s-off. So what do you suggest now ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi
Click to expand...
Click to collapse
while i try to compile an ruu, try to unlock it.
Start over from scratch. get new token, this time choose "all other devices" in Dev HTC.
after clicking "yes" Wait at least 10 minutes before stress out.
let me know

Ok I'll try and let you know
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi

kativiti said:
while i try to compile an ruu, try to unlock it.
Start over from scratch. get new token, this time choose "all other devices" in Dev HTC.
after clicking "yes" Wait at least 10 minutes before stress out.
let me know
Click to expand...
Click to collapse
I did exactly what you did. I got new token and choose "all supported other devices" in HTCdev. I took pictures of every step. It didn't work again after 3rd picture If I press volume up + power, it says "Device CW install : can't mount /data" and goes black screen and charging. If i don't press anything it goes black screen again and then chargin again as you can see on the 5th picture. So I can not unlock
By the way, If I choose recovery or factory reset on bootloader menu, I get the same result. (2nd, 3rd, 4th and 5th pictures).

blu3sm4n said:
I did exactly what you did. I got new token and choose "all supported other devices" in HTCdev. I took pictures of every step. It didn't work again after 3rd picture If I press volume up + power, it says "Device CW install : can't mount /data" and goes black screen and charging. If i don't press anything it goes black screen again and then chargin again as you can see on the 5th picture. So I can not unlock
By the way, If I choose recovery or factory reset on bootloader menu, I get the same result. (2nd, 3rd, 4th and 5th pictures).
Click to expand...
Click to collapse
1- in hboot enter recovery
when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
if recovery fails flash it
2-put this file in sdcard and update.
in hboot enter recovery, when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.

kativiti said:
1- in hboot enter recovery
when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
if recovery fails flash it
2-put this file in sdcard and update.
in hboot enter recovery, when red warning shows, press power+vol up to enter recovery.
wipe data and reboot.
Click to expand...
Click to collapse
in hboot when I try to enter recovery, red warning comes and pressing power+vol up, it says "device cw install:cant mount/data" and then black screen.
I tried second step and added your file into sdcard and update. it says press power button. After that white htc screen is coming. It is waiting since 15 minutes but still nothing and still white screen [emoji21]
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi

Sorry but it seems I'm unable to help you.
The picture shows green letters behind the red ones. It means the flashing fail, maybe it rejected the recovery or because its locked.
Either way your problem is, your system and recovery are corrupted.
My advice is contact HTC and send for repair. They usually don't charge you.

Ok dude thanks a lot. I'll contact HTC, i hope they can help ?
HTC One_M8 cihazımdan Tapatalk kullanılarak gönderildi