Database Develop

HTC One Has Corrupt EMMC and Locked Out of Recovery

I have a Sprint HTC One running 4.2.2 (3.05.651.6) stock rom and TWRP recovery. It is unlocked and unrooted at the moment. It randomly took a nose dive the other day and has been stuck in either boot loop or bootloader/ fastboot usb. If I try to reboot, reboot-bootloader, factory reset, lock the bootloader, etc it boot loops on the white htc screen.
I have tried to flash the recovery again and erase cache with no luck. I've tried to flash a stock rooted rom using RUU and fastboot with no luck, it just boot loops.
I have had extensive help from @benny3 and we can't figure this out.
I found these links to be insightful and possibly a fix but to repair the EMMC if that is the issue, I first need to get my recovery up and running.
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
http://forum.xda-developers.com/showthread.php?p=49965919
Any ideas on how to do this since it seems that my recovery is corrupt because I can't get into despite flashing CWR and TWRP (I can't overwrite TWRP).
Any input is helpful as I has exhausted everything I can think of and nothing works.

Does your computer see the One when it's in fastboot mode?
And if I understand properly..
fastboot oem lock
won't 'Relocked' your phone? When it white screen bootloops does it go to bootloader mode, or back into fastboot mode?
Whenever I've mucked something up beyond repair (you'll lose data)
fastboot format userdata
fastboot format cache
fastboot format system
fastboot format sdcard
*fastboot format recovery* never tried this one, but if you have a botched recovery partition this could cause a problem
fastboot reboot-bootloader
fastboot oem lock
have been my failsafes for getting things back to order (ie: reRUUing).
Probably unrelated and unnecessary (but for info completeness sake) what hboot are you on? If you are on Windows 8/8.1, 1.44/1.54 hboots don't work (1.55 does) and you'll need Windows 7 (or linux) to be able to talk in fastboot.
If you happen to be s-off,
fastboot oem rebootRUU
will let you bypass everything and go straight into RUU reflash mode.
Haven't heard of any irrecoverable emmc errors with the One yet, but I may just not have looked hard enough. First time I legit hardbricked my Sprint GS2 I ebay'd a jtag debugger to get things back.

pbassjunk said:
Does your computer see the One when it's in fastboot mode?
And if I understand properly..
fastboot oem lock
won't 'Relocked' your phone? When it white screen bootloops does it go to bootloader mode, or back into fastboot mode?
Whenever I've mucked something up beyond repair (you'll lose data)
fastboot format userdata
fastboot format cache
fastboot format system
fastboot format sdcard
*fastboot format recovery* never tried this one, but if you have a botched recovery partition this could cause a problem
fastboot reboot-bootloader
fastboot oem lock
have been my failsafes for getting things back to order (ie: reRUUing).
Probably unrelated and unnecessary (but for info completeness sake) what hboot are you on? If you are on Windows 8/8.1, 1.44/1.54 hboots don't work (1.55 does) and you'll need Windows 7 (or linux) to be able to talk in fastboot.
If you happen to be s-off,
fastboot oem rebootRUU
will let you bypass everything and go straight into RUU reflash mode.
Haven't heard of any irrecoverable emmc errors with the One yet, but I may just not have looked hard enough. First time I legit hardbricked my Sprint GS2 I ebay'd a jtag debugger to get things back.
Click to expand...
Click to collapse
fastboot oem lock reboots my phone and goes into a boot loop. I have to manually get it back into bootloader. From there I can go back into fastboot
I'm running hboot 1.55. I have tried the above commands on Windows XP and Vista and MacOSX with the same results. Do you think Windows 7 will help? I can try my brother's computer.
And I'm s-on so i can't fastboot oem rebootRUU
And for the jtag debugger don't you have to tear the phone apart. HTC One can't be taken apart easily, it damages the casing

If you can get to bootloader you should be able to RUU

pbassjunk said:
Does your computer see the One when it's in fastboot mode?
And if I understand properly..
fastboot oem lock
won't 'Relocked' your phone? When it white screen bootloops does it go to bootloader mode, or back into fastboot mode?
Whenever I've mucked something up beyond repair (you'll lose data)
fastboot format userdata
fastboot format cache
fastboot format system
fastboot format sdcard
*fastboot format recovery* never tried this one, but if you have a botched recovery partition this could cause a problem
fastboot reboot-bootloader
fastboot oem lock
have been my failsafes for getting things back to order (ie: reRUUing).
Probably unrelated and unnecessary (but for info completeness sake) what hboot are you on? If you are on Windows 8/8.1, 1.44/1.54 hboots don't work (1.55 does) and you'll need Windows 7 (or linux) to be able to talk in fastboot.
If you happen to be s-off,
fastboot oem rebootRUU
will let you bypass everything and go straight into RUU reflash mode.
Haven't heard of any irrecoverable emmc errors with the One yet, but I may just not have looked hard enough. First time I legit hardbricked my Sprint GS2 I ebay'd a jtag debugger to get things back.
Click to expand...
Click to collapse
BD619 said:
If you can get to bootloader you should be able to RUU
Click to expand...
Click to collapse
when you say RUU do you mean using fastboot, cuz I actually tried that last night and it failed and went into a boot loop. I also tried using RUU on my computer with my phone initially in fastboot usb. When it rebooted into bootloader it went into a boot loop as well. I had to manually go into bootloader again and then the program failed

BD619 said:
If you can get to bootloader you should be able to RUU
Click to expand...
Click to collapse
I tried these commands and also tried to unlock the bootloader but they all failed when running

I have the same problem just with verizon htc one
can boot only to hboot
any other mode (recovery, factury reset, check crc, reboot RUU) unavailable. Phone just bootloops on white htc logo
can not unlock boot, verizon phones restricted on htc-dev site

I have this problem in ONE M7 S-ON
no solution to restore; ;
thanks

jondon156 said:
I have a Sprint HTC One running 4.2.2 (3.05.651.6) stock rom and TWRP recovery. It is unlocked and unrooted at the moment. It randomly took a nose dive the other day and has been stuck in either boot loop or bootloader/ fastboot usb. If I try to reboot, reboot-bootloader, factory reset, lock the bootloader, etc it boot loops on the white htc screen.
I have tried to flash the recovery again and erase cache with no luck. I've tried to flash a stock rooted rom using RUU and fastboot with no luck, it just boot loops.
I have had extensive help from @benny3 and we can't figure this out.
I found these links to be insightful and possibly a fix but to repair the EMMC if that is the issue, I first need to get my recovery up and running.
http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
http://forum.xda-developers.com/showthread.php?p=49965919
Any ideas on how to do this since it seems that my recovery is corrupt because I can't get into despite flashing CWR and TWRP (I can't overwrite TWRP).
Any input is helpful as I has exhausted everything I can think of and nothing works.
Click to expand...
Click to collapse
try fastboot boot recovery.img

Same issue
I have the same problem on my Verizon HTC One M8. I was wondering if you were able to get your phone up and running again. If so, what/how did you do it?
I actually can get into recovery - adb sideload will not work any wiping or formatting I does NOT in fact wipe anything. I've tried recovering nandroid(s) and installing ROMs but same boot loop.

No fix??
Has anyone been able to fix their phone.

I'm also having same issue .. Tried everything nothing works ..
http://forum.xda-developers.com/htc-one/help/htc-one-m7-802d-booting-cleaner-killed-t3438530

Hello everyone, I'm also having the same problem with my HTC mini. I'm pretty sure the emmc got corrupted.
I have tried everything that was out there.
Can't unlock, at least it doesn't show unlocked, but send code successfully that I got from htcdev.
Can't twrp, since I'm locked. Can't flash Rom.zip that I extracted from the ruu.
On Windows I get 171 error. I have the correct drivers and fasboot works . I'm s-on , so I tried higher version from stock image.
Has anyone fixed their emmc ? If so, how'd u do it?
Thanks guys and good luck to all

davipaulo9 said:
On Windows I get 171 error. I have the correct drivers and fasboot works . I'm s-on , so I tried higher version from stock image.
Click to expand...
Click to collapse
Have you tried what's in this thread?
Suggestions I came across while researching error 171 with an RUU:
1. You are using a USB 3 port. Switch to USB 2.
2. Install HTC sync and then uninstall it leaving the drivers
3. Try a different USB cable.
4. You're using the wrong RUU.

coal686 said:
Have you tried what's in this thread?
Suggestions I came across while researching error 171 with an RUU:
1. You are using a USB 3 port. Switch to USB 2.
2. Install HTC sync and then uninstall it leaving the drivers
3. Try a different USB cable.
4. You're using the wrong RUU.
Click to expand...
Click to collapse
I tried that before, fasboot sees the phone but adb does not .
I think the emmc might be bad. I got the right ruu. Took from HTC website . Can't unlock either
---------- Post added at 10:13 AM ---------- Previous post was at 10:10 AM ----------
coal686 said:
Have you tried what's in this thread?
Suggestions I came across while researching error 171 with an RUU:
1. You are using a USB 3 port. Switch to USB 2.
2. Install HTC sync and then uninstall it leaving the drivers
3. Try a different USB cable.
4. You're using the wrong RUU.
Click to expand...
Click to collapse
I,tried all that, I got correct ruu from HTC site.
Using usb 2.0 fastboot sees the phone but adb does not .
I might have corrupted emmc
---------- Post added at 10:13 AM ---------- Previous post was at 10:13 AM ----------
coal686 said:
Have you tried what's in this thread?
Suggestions I came across while researching error 171 with an RUU:
1. You are using a USB 3 port. Switch to USB 2.
2. Install HTC sync and then uninstall it leaving the drivers
3. Try a different USB cable.
4. You're using the wrong RUU.
Click to expand...
Click to collapse
I,tried all that, I got correct ruu from HTC site.
Using usb 2.0 fastboot sees the phone but adb does not .
I might have corrupted emmc

davipaulo9 said:
I,tried all that, I got correct ruu from HTC site.
Using usb 2.0 fastboot sees the phone but adb does not .
I might have corrupted emmc
Click to expand...
Click to collapse
Maybe, but I've had that issue (where fastboot sees the phone and adb doesn't) and nothing was corrupt on the phone. It was a driver issue. But the ruu still worked for me.

coal686 said:
Maybe, but I've had that issue (where fastboot sees the phone and adb doesn't) and nothing was corrupt on the phone. It was a driver issue. But the ruu still worked for me.
Click to expand...
Click to collapse
I don't think it's a driver issue, but I'm not sure.
Fastboot sees the devices and in Windows also it's recognized on device manager . How can I check the emmc for errors and is it possible to repair?
---------- Post added at 01:45 PM ---------- Previous post was at 12:47 PM ----------
coal686 said:
Maybe, but I've had that issue (where fastboot sees the phone and adb doesn't) and nothing was corrupt on the phone. It was a driver issue. But the ruu still worked for me.
Click to expand...
Click to collapse
This is what I get running fastboot oem rebootruu
cmd18 polling stattus times out , MCI _status: 0x4C2000

davipaulo9 said:
I don't think it's a driver issue, but I'm not sure.
Fastboot sees the devices and in Windows also it's recognized on device manager . How can I check the emmc for errors and is it possible to repair?
---------- Post added at 01:45 PM ---------- Previous post was at 12:47 PM ----------
This is what I get running fastboot oem rebootruu
cmd18 polling stattus times out , MCI _status: 0x4C2000
Click to expand...
Click to collapse
From what I'm reading, the partitions might be shot. What does "fastboot getvar all" say?

coal686 said:
From what I'm reading, the partitions might be shot. What does "fastboot getvar all" say?
Click to expand...
Click to collapse
It spits out this message

coal686 said:
Have you tried what's in this thread?
Suggestions I came across while researching error 171 with an RUU:
1. You are using a USB 3 port. Switch to USB 2.
2. Install HTC sync and then uninstall it leaving the drivers
3. Try a different USB cable.
4. You're using the wrong RUU.
Click to expand...
Click to collapse
Tried that, didn't work.
I'm using usb 2.0 uninstall HTC sync , got right ruu. Any other thoughts?

PLEASE HELP! Soft-bricked

So I bought this HTC One M7, the guy claims its soft bricked and hes not able to fix it because hes technically challenged. So I take it home boot it up, its stuck in a boot loop so I boot it into fastboot the bootloader is locked so I try to connect it to adb, no luck, there is no driver on this internet that I have found that will connect to adb. So I resort to fastboot, I "fastboot devices" and sure enough it connects (wicked), first I try to flash recovery, I try to boot recovery, I tried to update zip, no luck in flashing anything because I either get a signature fail or a "remote: not allowed" then I realize my bootloader is locked, I try to unlock it "fastboot oem unlock" and of course I get a "INFO [ERR] command error". I also tried to change my cid to 11111111 and no luck. I have actually tried everything I can think of I cant get s-off to work my recovery is stock as well so theres no possibility of OTG cable plus a usb. My fastboot will not flash anything in fastboot, I cant push any files to the phone, I cant connect to adb, I cant use my recovery. So what in the actual can I do? I think i'm f**ked.
Thank you in advance for anything you can help me with.

jonrogers61 said:
So I bought this HTC One M7, the guy claims its soft bricked and hes not able to fix it because hes technically challenged. So I take it home boot it up, its stuck in a boot loop so I boot it into fastboot the bootloader is locked so I try to connect it to adb, no luck, there is no driver on this internet that I have found that will connect to adb. So I resort to fastboot, I "fastboot devices" and sure enough it connects (wicked), first I try to flash recovery, I try to boot recovery, I tried to update zip, no luck in flashing anything because I either get a signature fail or a "remote: not allowed" then I realize my bootloader is locked, I try to unlock it "fastboot oem unlock" and of course I get a "INFO [ERR] command error". I also tried to change my cid to 11111111 and no luck. I have actually tried everything I can think of I cant get s-off to work my recovery is stock as well so theres no possibility of OTG cable plus a usb. My fastboot will not flash anything in fastboot, I cant push any files to the phone, I cant connect to adb, I cant use my recovery. So what in the actual can I do? I think i'm f**ked.
Thank you in advance for anything you can help me with.
Click to expand...
Click to collapse
You can't use adb unless you're booted to OS or custom recovery. Also you can't unlock bootloader with "fastboot oem unlock" unless your phone is GPE version. For Sense you need unlock token from htcdev. In order to flash anything, you need custom recovery, and you can flash it only if your bootloader is unlocked

donkeykong1 said:
You can't use adb unless you're booted to OS or custom recovery. Also you can't unlock bootloader with "fastboot oem unlock" unless your phone is GPE version. For Sense you need unlock token from htcdev. In order to flash anything, you need custom recovery, and you can flash it only if your bootloader is unlocked
Click to expand...
Click to collapse
I unlocked my htc with the unlocktoken from htc dev but it still says locked in bootloader. I can flash the unlock_code.bin but it does not restart nor does it come up with a message that says I would like to unlock bootloader etc.

jonrogers61 said:
I unlocked my htc with the unlocktoken from htc dev but it still says locked in bootloader. I can flash the unlock_code.bin but it does not restart nor does it come up with a message that says I would like to unlock bootloader etc.
Click to expand...
Click to collapse
can you post the output of "fastboot getvar all" (remove your imei and serialno). Sometimes, reflashing the stock firmware can solve some bootloader unlock problem but I need to know you getvar all before I can tell you which one you should flash.

M7 Cant get into RUU mode

I have a verizon htc one m7 that will boot to the verizon logo then restart. i can access the bootload/fastboot and recovery. when i issue the fastboot command of fastboot oem rebootRUU the command completes and phone goes black then the green htc logo appears and continues to try and boot normally. does anybody have any suggestions on how to get to the RUU mode? bootloader is locked and s-on is active. this is a completly stock phone.

I think you need unlocked bootloader (but I'm not sure). So try unlocking it (keep in mind that you'll loose the guarantee)

suchauser said:
I think you need unlocked bootloader (but I'm not sure). So try unlocking it (keep in mind that you'll loose the guarantee)
Click to expand...
Click to collapse
1- no need for an unlocked bootloader
2- he's on Verizon so he can't use HTCdev to unlock, and sunshine won't work without a booted phone
idragoncell said:
I have a verizon htc one m7 that will boot to the verizon logo then restart. i can access the bootload/fastboot and recovery. when i issue the fastboot command of fastboot oem rebootRUU the command completes and phone goes black then the green htc logo appears and continues to try and boot normally. does anybody have any suggestions on how to get to the RUU mode? bootloader is locked and s-on is active. this is a completly stock phone.
Click to expand...
Click to collapse
how about some background info, how you ended in this situation... if it's a complete stock phone (so you weren't messing around with flashing things), then it could very well be a hardware problem... but the above info isnt enough, you need to provide more details of how this came to be
it's also good practice to copy/paste the entire command prompt output, so we can take a look of what was typed and what the output generated

Customer bought the phone too me in a boot loop state.. he claims he was using it and it just went black then came back on but never fully booted kept restarting at the verizon logo. htc told him to try and factory reset the phone but that was a no go as well. i have tried a RUU utility and when the program says rebooting to bootloader it doesnt go into bootloader just trys to boot up normally. the same thing happens when i attempt to put it in RUU mode it just reboots and trys to boot normally.

idragoncell said:
Customer bought the phone too me in a boot loop state.. he claims he was using it and it just went black then came back on but never fully booted kept restarting at the verizon logo. htc told him to try and factory reset the phone but that was a no go as well. i have tried a RUU utility and when the program says rebooting to bootloader it doesnt go into bootloader just trys to boot up normally. the same thing happens when i attempt to put it in RUU mode it just reboots and trys to boot normally.
Click to expand...
Click to collapse
sorry, dont get me wrong, but since i've been back (for a few hours), people are ... let's just say, not very forthcoming
what would help:
a screenshot of bootloader
a "fastboot getvar all" (excluding the last 6 digits of IMEI, MEID, and serial number... those need not be shared)
possibly a fastboot oem last_dmesg
though if the phone is completely stock, never been tampered with, then you have a high chance it's a hardware problem

http://imgur.com/73JGfka
https://goo.gl/photos/hkdxnmNtB7ctd2XA9
http://imgur.com/El0SNkj

idragoncell said:
http://imgur.com/73JGfka
https://goo.gl/photos/hkdxnmNtB7ctd2XA9
http://imgur.com/El0SNkj
Click to expand...
Click to collapse
thanks for the details, nothing "looks" wrong from those, but the "fastboot oem last_dmesg" has to be done after attempting to flash something, after a (non flashing reboot) it will just be empty.
couldn't find much, but have you tried this RUU:
http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442
EDIT:
1- RUU.EXE will leave a log (before you close the .exe), in c:\ruu_log\.......txt
2- command prompt copy/paste is preferred to a screenshot, since it's much easier to read
good luck

HTC Desire 510 can't do anything with it. Stuck

So here's the story... this is an HTC Desire 510 purchased from Telus here in Canada. I've been messing around with different kernels, ROMs, etc. None of them really worked well for me, so I decided to go back to stock, unlock and try to sell it. Now I'm stuck at the bootloader and I can't figure out what to do. I tried to re-lock the bootloader so I could flash the stock ROM (those were the instructions I read)...
Whenever it boots, it gets to the recovery screen. ("Fastboot USB" / HBOOT) it says *Tampered* and *Relocked* at the top.
Then, when I try to unlock it with Unlock_code.bin (I have tried every method available), and say "Yes", I get the Fastboot USB screen with an overlay that says - at the top: Entering Recovery...
at the bottom it says: This build is for development purposes only, etc.
Then it just stays there until I remove the USB cable and the battery.
I reboot and I get the same thing every time.
Is there any way to fix this? I've tried many an adb command with no avail. I'm ready to throw this thing into the river.

cjmitchell said:
So here's the story... this is an HTC Desire 510 purchased from Telus here in Canada. I've been messing around with different kernels, ROMs, etc. None of them really worked well for me, so I decided to go back to stock, unlock and try to sell it. Now I'm stuck at the bootloader and I can't figure out what to do. I tried to re-lock the bootloader so I could flash the stock ROM (those were the instructions I read)...
Whenever it boots, it gets to the recovery screen. ("Fastboot USB" / HBOOT) it says *Tampered* and *Relocked* at the top.
Then, when I try to unlock it with Unlock_code.bin (I have tried every method available), and say "Yes", I get the Fastboot USB screen with an overlay that says - at the top: Entering Recovery...
at the bottom it says: This build is for development purposes only, etc.
Then it just stays there until I remove the USB cable and the battery.
I reboot and I get the same thing every time.
Is there any way to fix this? I've tried many an adb command with no avail. I'm ready to throw this thing into the river.
Click to expand...
Click to collapse
Is it 64 bit or 32 bit? And what type of recovery did you have on it before?

MrMike2182 said:
Is it 64 bit or 32 bit? And what type of recovery did you have on it before?
Click to expand...
Click to collapse
It's 32 bit and it had TWRP.

cjmitchell said:
It's 32 bit and it had TWRP.
Click to expand...
Click to collapse
What you need to do first of all is find an RUU for your device and then find the original recovery, not the twrp recovery but the actual recovery that was on the phone when you first got it. If you don't flash the original recovery then the RUU will refuse to continue and that's basically HTC's way of trying to prevent us from breaking the phone.. The unlock code you got from HTC you should have kept and whenever you sell the phone pass it along to the new owner.. So to help you understand everything I said first unlock your bootloader again and then flash the original recovery and then lock the bootloader again then run the RUU on the PC.. Some times you have to run the RUU a few times to finally get it to finish completely cause some times it'll hang and just sit there so just end the process and restart it but before ending it be sure you gave it enough time to try before thinking it's stuck because it may not be... After the RUU finishes, the phone will totally be stock again the same way it was the day you bought it..

MrMike2182 said:
What you need to do first of all is find an RUU for your device and then find the original recovery, not the twrp recovery but the actual recovery that was on the phone when you first got it. If you don't flash the original recovery then the RUU will refuse to continue and that's basically HTC's way of trying to prevent us from breaking the phone.. The unlock code you got from HTC you should have kept and whenever you sell the phone pass it along to the new owner.. So to help you understand everything I said first unlock your bootloader again and then flash the original recovery and then lock the bootloader again then run the RUU on the PC.. Some times you have to run the RUU a few times to finally get it to finish completely cause some times it'll hang and just sit there so just end the process and restart it but before ending it be sure you gave it enough time to try before thinking it's stuck because it may not be... After the RUU finishes, the phone will totally be stock again the same way it was the day you bought it..
Click to expand...
Click to collapse
HTC or Telus don't provide a RUU for the Telus version of the phone so I've been trying the Cricket version, doesn't work. It gives me the message: ERROR [131]: CUSTOMER ID ERROR.
There is some russian website that seems to have it for Telus, but you have to pay to access it, and I don't even know if it's what I need. ir-file.com (I can't post links)
So I'm not going down that rabbit hole.
I can't flash any recovery I find...
"fastboot getvar platform" gives me hTCBmsm2886
"fastboot flash recovery (*.img)" gives me a message saying FAILED (remote: signature verify fail) for every single recovery image I can find. Nothing works.

cjmitchell said:
HTC or Telus don't provide a RUU for the Telus version of the phone so I've been trying the Cricket version, doesn't work. It gives me the message: ERROR [131]: CUSTOMER ID ERROR.
There is some russian website that seems to have it for Telus, but you have to pay to access it, and I don't even know if it's what I need. ir-file.com (I can't post links)
So I'm not going down that rabbit hole.
I can't flash any recovery I find...
"fastboot getvar platform" gives me hTCBmsm2886
"fastboot flash recovery (*.img)" gives me a message saying FAILED (remote: signature verify fail) for every single recovery image I can find. Nothing works.
Click to expand...
Click to collapse
Did you try to reflash twrp? If I was in your predicament I'd flash twrp and then there is a rom that I configured to work great on the 32 bit phones it's the Modded CM11 and I'm pretty sure it'll work on yours albeit the cameras aren't working yet at least it's a start and you can find the CM11 I configured here ----> Modded CM11

MrMike2182 said:
Did you try to reflash twrp? If I was in your predicament I'd flash twrp and then there is a rom that I configured to work great on the 32 bit phones it's the Modded CM11 and I'm pretty sure it'll work on yours albeit the cameras aren't working yet at least it's a start and you can find the CM11 I configured here ----> Modded CM11
Click to expand...
Click to collapse
Yeah, I tried to reflash TWRP, I get that message "FAILED: (remote: signature verify fail)"
That is after I type in the C:\adb\ folder "fastboot flash recovery twrp-2.8.7.0-a11.img"
and every other recovery image I can find, including older versions of TWRP.
This is why I'm frustrated, nothing works. If I could flash a ROM that'd be cool, but I can't get out of the bootloader, I can't even get into recovery.

cjmitchell said:
Yeah, I tried to reflash TWRP, I get that message "FAILED: (remote: signature verify fail)"
That is after I type in the C:\adb\ folder "fastboot flash recovery twrp-2.8.7.0-a11.img"
and every other recovery image I can find, including older versions of TWRP.
This is why I'm frustrated, nothing works. If I could flash a ROM that'd be cool, but I can't get out of the bootloader, I can't even get into recovery.
Click to expand...
Click to collapse
I need you to type everything you see on your HBoot screen when you pull the battery and put it back in and then hold the volume down button and then press the power button at the same time and when the screen comes up type everything you see in here so I can see it... I think the reason you're getting the remote signature failure is because the bootloader is still locked and you have to make sure it really is unlocked.. Try that then get back to me.

Yeah, the bootloader is still locked. here's what it says:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 19 2015,21:13:29.0
Then the regular menu.
I can't seem to unlock the bootloader.

cjmitchell said:
Yeah, the bootloader is still locked. here's what it says:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
A11_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.101.1372.19.1121
OpenDSP-v28.2.2.00546.0331
OS-
eMMC-boot 1024MB
Aug 19 2015,21:13:29.0
Then the regular menu.
I can't seem to unlock the bootloader.
Click to expand...
Click to collapse
Well if you had the boot unlocked before, why can't you send the unlock_code.bin to it and have it unlock again? Or did you lose the key? Because you're supposed to keep that key.. Did you use some sort of program to try and root the phone? Like them 1 click root apps...
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Go download this to a computer/laptop whatever and connect the phone to it and try to run this RUU on the PC while the phone is connected to it and turned on in HBoot/fastboot... Do this before trying to unlock the boot again and if it hangs try it again because some times it can take 3 or 4 tries to get it to work... Download Cricket RUU - http://dl3.htc.com/application/RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Aio_Wireless_US_1.11.506.8.exe
Edit: I know you said your carrier is Telus and I know that's a Cricket RUU that I listed, but they are both the same so run it!!
Edit again: Never mind don't bother running the RUU because you're not s-off and you can't change your CID so I suggest you find a way to unlock your bootloader again somehow and then flash the CM11 to test out.

MrMike2182 said:
Well if you had the boot unlocked before, why can't you send the unlock_code.bin to it and have it unlock again? Or did you lose the key? Because you're supposed to keep that key.. Did you use some sort of program to try and root the phone? Like them 1 click root apps...
---------- Post added at 06:44 PM ---------- Previous post was at 06:40 PM ----------
Go download this to a computer/laptop whatever and connect the phone to it and try to run this RUU on the PC while the phone is connected to it and turned on in HBoot/fastboot... Do this before trying to unlock the boot again and if it hangs try it again because some times it can take 3 or 4 tries to get it to work... Download Cricket RUU - http://dl3.htc.com/application/RUU_A11_UL_K44_DESIRE_SENSE60_AIO_Aio_Wireless_US_1.11.506.8.exe
Edit: I know you said your carrier is Telus and I know that's a Cricket RUU that I listed, but they are both the same so run it!!
Edit again: Never mind don't bother running the RUU because you're not s-off and you can't change your CID so I suggest you find a way to unlock your bootloader again somehow and then flash the CM11 to test out.
Click to expand...
Click to collapse
I have the unlock_code.bin, I've been trying to send it to the phone but it doesn't work. I've tried the WinDroid app and the command line "fastboot flash unlocktoken unlock_code.bin" and I get to the screen that asks if I want to unlock the bootloader, but when I select "Yes" it hangs and sticks on that screen, but at the top it says: "Entering Recovery..." and at the bottom it says "This build is for development purposes only", etc.
If I can't flash anything then I'm guessing it's perma-bricked... :/

cjmitchell said:
I have the unlock_code.bin, I've been trying to send it to the phone but it doesn't work. I've tried the WinDroid app and the command line "fastboot flash unlocktoken unlock_code.bin" and I get to the screen that asks if I want to unlock the bootloader, but when I select "Yes" it hangs and sticks on that screen, but at the top it says: "Entering Recovery..." and at the bottom it says "This build is for development purposes only", etc.
If I can't flash anything then I'm guessing it's perma-bricked... :/
Click to expand...
Click to collapse
Right it hung there because there was no recovery flashed so right after you unlock that no matter what just flash twrp to it the second after you tap yes to unlock the bootloader send the recovery to it.

MrMike2182 said:
Right it hung there because there was no recovery flashed so right after you unlock that no matter what just flash twrp to it the second after you tap yes to unlock the bootloader send the recovery to it.
Click to expand...
Click to collapse
as soon as I hit the "Yes" option on the "Unlock bootloader?" screen, it tries to go into recovery. And it's instant. There is no window where I can flash the recovery - I've tried it multiple times.
So I can't unlock it and I can't flash a recovery.
I'm afraid this thing is done for...

cjmitchell said:
as soon as I hit the "Yes" option on the "Unlock bootloader?" screen, it tries to go into recovery. And it's instant. There is no window where I can flash the recovery - I've tried it multiple times.
So I can't unlock it and I can't flash a recovery.
I'm afraid this thing is done for...
Click to expand...
Click to collapse
You are supposed to be unlocking it from a PC and flashing the recovery from the PC also not trying to flash the recovery from the phone you cant do that unless the phones working.. Don't you have minimal ADB and Fastboot installed on a Windows PC?

Bootloader not unlocking (Asus Zenfone Go ZB452KG)

Hey people, first time in this section so I'm gonna go straight to the chase...
I've been having some troubles unlocking this phone's bootloader
http://www.gsmarena.com/asus_zenfone_go_zb452kg-8097.php
Here's the thing
I've already enabled "Enable OEM unlock" in Developer Options
I've already unlocked many devices and this is the first time i got this problem
When going in bootloader and doing
Code:
fastboot oem unlock
It's stuck in
Code:
...
waited for 5 mins... NONE, still stuck
Reboot and did nothing, bootloader still locked
So I'm gonna need some help in this freakin phone :fingers-crossed:

How were you able to "Enable OEM Unlock"?
My ZB452KG has the developer mode activated, but there's no option to Enable OEM Unlock...

BallisticSmith said:
How were you able to "Enable OEM Unlock"?
My ZB452KG has the developer mode activated, but there's no option to Enable OEM Unlock...
Click to expand...
Click to collapse
Downgrade to the very first firmware version

veez21 said:
Downgrade to the very first firmware version
Click to expand...
Click to collapse
Yeah, i tried doing that through adb, but the phone don't let me install an older ROM version on top of this one

BallisticSmith said:
Yeah, i tried doing that through adb, but the phone don't let me install an older ROM version on top of this one
Click to expand...
Click to collapse
flash the very first stock recovery(find it in facebook groups) through flashify and then flash the very first firmware

veez21 said:
flash the very first stock recovery(find it in facebook groups) through flashify and then flash the very first firmware
Click to expand...
Click to collapse
if I can download the very first firmware Asus Zenfone Go ZB452KG from the website ASUSTek?
Sorry for my bad english

Str1kman said:
if I can download the very first firmware Asus Zenfone Go ZB452KG from the website ASUSTek?
Sorry for my bad english
Click to expand...
Click to collapse
You can download it, then flash(needs root) the very first stock recovery and then you can flash the firmware?

this thread has continued to be unaswered for several years now.
only tested 2 phones... and it seems they both have bootloader status is unknown. i can do fastboot and recovery mode on the 2 phones but on fastboot mode.. only shows blank screen... idk why it's like that. i downgraded both phones to 12.2.0 version. and bootloader status is still unknown. it can be recognized by the computer in fastboot mode using fastboot devices command but you can't do anything to it. fastboot oem device-info does not work only shows .......... , fastboot oem unlock ....., only one working is fastboot adb_enable .. kinda useless. .. i gave up on unlocking the bootloader for this phone.. im too noob for this.

yankee77 said:
this thread has continued to be unaswered for several years now.
only tested 2 phones... and it seems they both have bootloader status is unknown. i can do fastboot and recovery mode on the 2 phones but on fastboot mode.. only shows blank screen... idk why it's like that. i downgraded both phones to 12.2.0 version. and bootloader status is still unknown. it can be recognized by the computer in fastboot mode using fastboot devices command but you can't do anything to it. fastboot oem device-info does not work only shows .......... , fastboot oem unlock ....., only one working is fastboot adb_enable .. kinda useless. .. i gave up on unlocking the bootloader for this phone.. im too noob for this.
Click to expand...
Click to collapse
I opened this thread when I was still "noob-ish". The device's bootloader can't be unlocked. Unless someone hacks into it's bootloader (like LG L Fino), it might be possible.

Mr.haikal

veez21 said:
I opened this thread when I was still "noob-ish". The device's bootloader can't be unlocked. Unless someone hacks into it's bootloader (like LG L Fino), it might be possible.
Click to expand...
Click to collapse
I found a way to unlock bootloader on this device. Just run this commands:
Code:
fastboot oem adb_enable 1
fastboot reboot-bootloader
fastboot oem unlock
Also compiled a TWRP recovery:
TWRP: https://github.com/Displax/android_.../download/3.2.3-0/twrp-3.2.3-0-ASUS_X014D.img
Sources: https://github.com/Displax/android_device_asus_ASUS_X014D

Displax said:
I found a way to unlock bootloader on this device. Just run this commands:
Also compiled a TWRP recovery:
TWRP: https://github.com/Displax/android_...s/download/master/twrp-3.2.1-0-ASUS_X014D.img
Source: https://github.com/Displax/android_device_asus_ASUS_X014D
Click to expand...
Click to collapse
Cool, I'll try it when I get the device on my hands. I don't have it anymore.
EDIT: It works wew ?

Displax said:
I found a way to unlock bootloader on this device. Just run this commands:
Code:
fastboot oem adb_enable 1
fastboot reboot-bootloader
fastboot oem unlock
Also compiled a TWRP recovery:
TWRP: https://github.com/Displax/android_.../download/3.2.3-0/twrp-3.2.3-0-ASUS_X014D.img
Sources: https://github.com/Displax/android_device_asus_ASUS_X014D
Click to expand...
Click to collapse
+1 worked after i installed the drivers from Asus PCLink. Anyone has a custom kernel or ...

BallisticSmith said:
Yeah, i tried doing that through adb, but the phone don't let me install an older ROM version on top of this one
Click to expand...
Click to collapse
I got root access with KingRoot and then flashed TWRP with Flashify.
Somehow that gave me access to bootloader without the necessity to downgrade the firmware.