Database Develop

[How-To] Unbrick HTC Tattoo(CLICK) after bad recovery

Hello all,
PROBLEM
I while ago I had flashed my tattoo with a ROM that came with ROMmanager (wich is able to flash a custom recovery within Android) and the result was that my recovery was corupted and I couldn't flash another rom anymore, since I have a locked SPL.
POSSIBLE SOLUTION
What you can try is to download the latest RUU for your device and try to update the tattoo. However, I know that alot of people will get the error code 170 or 171: USB not connected. Don't panic, I have found after so many days of searching the solution to this problem.
WHAT WILL YOU NEED ?
The correct RUU for your device forum.xda-developers.com/showthread.php?t=591746"]
Procmon, this is a Process Monitor. You will need this to extract the rom.zip file from the RUU. technet.microsoft.com/en-us/sysinternals/bb896645.aspx"]
The android SDK and ADB set up correctly ( just search it on Google, and you'll find it).
LETS GET STARTED
The first thing you'll need to do is to open your prefered RUU you just downloaded from the link above, and wait till it says "welcome to the htc update..."
Just click next once, and leave the RUU open.
NOTE: The RUU can't be minimalized, so I sugest to slide it down to the taskbar.
Next, open the Procmon application, it will show you all open tasks (don't start searching like a fool, there are too many processes running to find the file we're searching for!).
Still in the Procmon, search in the for a filter button (the sixth button, white with a bleu thing above it), and click on it, now there will popup a screen.
Change the first tab (Architecture) to Path, and the seccond one (is) to contains, then in the box type rom.zip, and leave the Include tab how it is.
Now press add, and then press apply and ok. And search to one of the path's that ends with rom.zip in the list.
Right-click on it, and select Jump To, now you will see the rom.zip file in a temporary windows folder. Copy the rom to whereever you want (e.g. on your desktop) and close the RUU and Process Monitor.
Now, we have found and extracted the original rom that comes with the tattoo, so we're ready to flash this rom manually to our tattoo:
Open up command prompt, and cd to adb (where you have installed the SDK).
Now connect the tattoo to your pc and make sure its recognized under ADB Devices in device manager in windows.
Go back to the command prompt, and type
Code:
adb devices
If ADB is setup how it should, then you'll see the tattoo there (a long number)
Now type:
Code:
adb shell
adb reboot oem-78
The tattoo is now going to reboot in RUU mode, so we can do fastboot commands. (You will see only HTC logo on the tattoo)
Copy the rom.zip you extracted from the RUU to the tools folder of your SDK.
Now type:
Code:
fastboot flash zip rom.zip
(rom.zip is the name of your extracted rom, if you renamed it, then use the name of your rom).
Wait for the flashing procedure to finish, you'll see some message of completed or done or something, and unplug your tattoo, it should be in the bootloader screen (with 3 skateboards) and in the middle you should see RUU in orange.
Reboot your device, and hold the HOME + END button till the tattoo screen comes up, and wait till you see a screen with an exlimation mark, now shortly press on the HOME+END butten and you should be able to see the recovery menu now!
OPTIONAL
Redoo the 'root the tattoo in one click', and you'll get a custom recovery and root acces. IF YOU DO SO, I STRONGLY RECOMMEND YOU TO FLASH ANOTHER CUSTOM RECOVERY TO THE TATTOO, JUST SEARCH ONE ON THE FORUM HERE AND YOU'LL ALSO FIND HOW TO DO SO TROUGH ADB COMMANDS.
Once you have a custom recovery, you can flash rom's again from the recovery.
Hope this tread was helpfull !

Very usefull tnx
Sent from my Tattoo using XDA App

Now I'm even less afraid of flashing my a.. of. :-D
Thanx man!
Sent from my Tattoo using Tapatalk

MOdel ID checl Failed
Hi ,
I am getting this error
C:\androidtools\tools>fastboot flash zip "C:\My Folder\Datas\Mobile\Tattoo\rom.z
ip"
sending 'zip' (88968 KB)... OKAY [ 12.422s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 40.079s
C:\androidtools\tools>

soulaiman said:
Hello all,
PROBLEM
I while ago I had flashed my tattoo with a ROM that came with ROMmanager (wich is able to flash a custom recovery within Android) and the result was that my recovery was corupted and I couldn't flash another rom anymore, since I have a locked SPL.
POSSIBLE SOLUTION
What you can try is to download the latest RUU for your device and try to update the tattoo. However, I know that alot of people will get the error code 170 or 171: USB not connected. Don't panic, I have found after so many days of searching the solution to this problem.
WHAT WILL YOU NEED ?
The correct RUU for your device forum.xda-developers.com/showthread.php?t=591746"]
Procmon, this is a Process Monitor. You will need this to extract the rom.zip file from the RUU. technet.microsoft.com/en-us/sysinternals/bb896645.aspx"]
The android SDK and ADB set up correctly ( just search it on Google, and you'll find it).
LETS GET STARTED
The first thing you'll need to do is to open your prefered RUU you just downloaded from the link above, and wait till it says "welcome to the htc update..."
Just click next once, and leave the RUU open.
NOTE: The RUU can't be minimalized, so I sugest to slide it down to the taskbar.
Next, open the Procmon application, it will show you all open tasks (don't start searching like a fool, there are too many processes running to find the file we're searching for!).
Still in the Procmon, search in the for a filter button (the sixth button, white with a bleu thing above it), and click on it, now there will popup a screen.
Change the first tab (Architecture) to Path, and the seccond one (is) to contains, then in the box type rom.zip, and leave the Include tab how it is.
Now press add, and then press apply and ok. And search to one of the path's that ends with rom.zip in the list.
Right-click on it, and select Jump To, now you will see the rom.zip file in a temporary windows folder. Copy the rom to whereever you want (e.g. on your desktop) and close the RUU and Process Monitor.
Now, we have found and extracted the original rom that comes with the tattoo, so we're ready to flash this rom manually to our tattoo:
Open up command prompt, and cd to adb (where you have installed the SDK).
Now connect the tattoo to your pc and make sure its recognized under ADB Devices in device manager in windows.
Go back to the command prompt, and type
Code:
adb devices
If ADB is setup how it should, then you'll see the tattoo there (a long number)
Now type:
Code:
adb shell
adb reboot oem-78
The tattoo is now going to reboot in RUU mode, so we can do fastboot commands. (You will see only HTC logo on the tattoo)
Copy the rom.zip you extracted from the RUU to the tools folder of your SDK.
Now type:
Code:
fastboot flash zip rom.zip
(rom.zip is the name of your extracted rom, if you renamed it, then use the name of your rom).
Wait for the flashing procedure to finish, you'll see some message of completed or done or something, and unplug your tattoo, it should be in the bootloader screen (with 3 skateboards) and in the middle you should see RUU in orange.
Reboot your device, and hold the HOME + END button till the tattoo screen comes up, and wait till you see a screen with an exlimation mark, now shortly press on the HOME+END butten and you should be able to see the recovery menu now!
OPTIONAL
Redoo the 'root the tattoo in one click', and you'll get a custom recovery and root acces. IF YOU DO SO, I STRONGLY RECOMMEND YOU TO FLASH ANOTHER CUSTOM RECOVERY TO THE TATTOO, JUST SEARCH ONE ON THE FORUM HERE AND YOU'LL ALSO FIND HOW TO DO SO TROUGH ADB COMMANDS.
Once you have a custom recovery, you can flash rom's again from the recovery.
Hope this tread was helpfull !
Click to expand...
Click to collapse
If this post does what it says it does, it should maybe be made a sticky so that everyone who bricks their device knows EXACTLY what to do to fix it.........

This metod work,excelent

nkaderfe said:
Hi ,
I am getting this error
C:\androidtools\tools>fastboot flash zip "C:\My Folder\Datas\Mobile\Tattoo\rom.z
ip"
sending 'zip' (88968 KB)... OKAY [ 12.422s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 40.079s
C:\androidtools\tools>
Click to expand...
Click to collapse
Hmm, seems like adb can't verify the model of your phone. Try a different ROM or Reinstall the sdk tools. If that doesn't make sense, then try to recreate your goldcard, but I don't think that that would make some difference at all.

soulaiman said:
WHAT WILL YOU NEED ?
The correct RUU for your device forum.xda-developers.com/showthread.php?t=591746"]
Procmon, this is a Process Monitor. You will need this to extract the rom.zip file from the RUU. technet.microsoft.com/en-us/sysinternals/bb896645.aspx"]
The android SDK and ADB set up correctly ( just search it on Google, and you'll find it).
Click to expand...
Click to collapse
Well, the rom.zip is always located in %tmp% (Start->run->%tmp% and then enter). Search the folders and somewhere you will find the rom.zip then...procmon is a little over-engineered
nkaderfe said:
Hi ,
I am getting this error
C:\androidtools\tools>fastboot flash zip "C:\My Folder\Datas\Mobile\Tattoo\rom.z
ip"
sending 'zip' (88968 KB)... OKAY [ 12.422s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 40.079s
C:\androidtools\tools>
Click to expand...
Click to collapse
Then you have a vendor specific build - Vodafone? Orange? You have to flash this in order to get the flashing started...
/EDIT: Did u create a goldcard?

Getting stuck.
When I type adb shell it responds with: -exec '/system/bin/sh' failed: No such file or directory <2> -
adb reboot oem-78
fastboot flash zip rom.zip
<waiting for device>
My phone is plugged in but doesn't want to boot past tattoo screen.
Plz help if you know the problem.

timlambo said:
Getting stuck.
When I type adb shell it responds with: -exec '/system/bin/sh' failed: No such file or directory <2> -
adb reboot oem-78
fastboot flash zip rom.zip
<waiting for device>
My phone is plugged in but doesn't want to boot past tattoo screen.
Plz help if you know the problem.
Click to expand...
Click to collapse
Hi,
You have to boot your phone first in bootloader mode, to do so you have to pull out battery, put it back in, hold in the down volume button while pressing power, it wil bring you in a white screen with at the bottom three androids on skeatboards.
Hope this helps you.

soulaiman said:
Hi,
You have to boot your phone first in bootloader mode, to do so you have to pull out battery, put it back in, hold in the down volume button while pressing power, it wil bring you in a white screen with at the bottom three androids on skeatboards.
Hope this helps you.
Click to expand...
Click to collapse
I know. That is where I were. I think the problem were with my rom, found old backup om pc and restored to that, but now it is working again.
Thanks for the help.

[Q] I may have bricked my One. Can someone help me?

So i have an AT&T HTC One M7, and i was trying to do all the necessary steps to convert it into a google edition, but in my attempt to get s-off, after unlocking and rooting my phone, i did a tutorial that told me to install the ARHD Rom, well after the installation my phone wouldnt load anything past the initial HTC splash screen. so i then i tried an ruu, when it failed it left me unable to even access recovery. so i tried all the ruu files i could find for att and none of them worked. does anyone know what i can do?
on my boot loader screen it says all this:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.57 0000
RADIO- 4M.27.3218.14
OpenDSP- v32.120.274.0909
OS- 5.12.502.2
eMMC- boot 2048MB
Apr 22 2014, 01:10:58.0

sigmaul said:
So i have an AT&T HTC One M7, and i was trying to do all the necessary steps to convert it into a google edition, but in my attempt to get s-off, after unlocking and rooting my phone, i did a tutorial that told me to install the ARHD Rom, well after the installation my phone wouldnt load anything past the initial HTC splash screen. so i then i tried an ruu, when it failed it left me unable to even access recovery. so i tried all the ruu files i could find for att and none of them worked. does anyone know what i can do?
on my boot loader screen it says all this:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.57 0000
RADIO- 4M.27.3218.14
OpenDSP- v32.120.274.0909
OS- 5.12.502.2
eMMC- boot 2048MB
Apr 22 2014, 01:10:58.0
Click to expand...
Click to collapse
There is no ruu you can flash to your phone with s-on because all of them are lower version and require s-off to be flashed. your issue with booting arhd is probably because you did not used the right recovery. you must use twrp 2.6.3.3 to flash it.
reflash twrp 2.6.3.3:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
bot in twrp recovery, flash arhd again and try to s-off, if you can't s-off restore your nandroid backup or if you don't have any backup, flash any custom rom you want to use.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\User>cd C:\fastboot
C:\Fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.122s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.013s
twrp isnt installing am i doing something wrong with that?

oh i got twrp on there, i had to re unlock my phone. now my dilemma is that the arhd rom is no longer there since the phone was wiped i guess. so my question now is, how do i get this arhd .zip back onto the phone? because i cant just drop it in like before

sigmaul said:
oh i got twrp on there, i had to re unlock my phone. now my dilemma is that the arhd rom is no longer there since the phone was wiped i guess. so my question now is, how do i get this arhd .zip back onto the phone? because i cant just drop it in like before
Click to expand...
Click to collapse
use adb push from twrp recovery, see below for detailed guide:
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer, either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-DATE\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery (2.6.3.3 or higher) on your device.
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
Here is a list of the HTC M7 roms
Connect your phone to computer using usb cable
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes and there is no progress bar. When the command prompt give you back the hand and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse

sigmaul said:
oh i got twrp on there, i had to re unlock my phone. now my dilemma is that the arhd rom is no longer there since the phone was wiped i guess. so my question now is, how do i get this arhd .zip back onto the phone? because i cant just drop it in like before
Click to expand...
Click to collapse
You can copy it from your PC to your phone via the USB cable using windows explorer or you can use the adb push method you used earlier.

thanks for the reply!!!
ive done as instructed but, nothings happening....
this what it looks like in my terminal
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
HT34WW914838 recovery
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push Android_Revolution_HD-O
ne_71.1.zip /sdcard/
_
after i try to push the zip file nothing happens, it doesnt say fail, or success or anything, just a blinking little line
any suggestions on that??
sorry about all questions btw, i jus didnt think so much would go wrong this time around (ive rooted this phone before no problem, im guessing the hboot 1.57 thing kinda screwed me this time) but thanks for the help so far =]

and no i cant use my usb my pc no longer recognizes my phone the same way, its recognized as a removable disk, and when clicked it says insert sdcard or something

sigmaul said:
thanks for the reply!!!
ive done as instructed but, nothings happening....
this what it looks like in my terminal
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
HT34WW914838 recovery
C:\Program Files (x86)\Minimal ADB and Fastboot>adb push Android_Revolution_HD-O
ne_71.1.zip /sdcard/
_
after i try to push the zip file nothing happens, it doesnt say fail, or success or anything, just a blinking little line
Click to expand...
Click to collapse
How long did you wait after doing adb push Android_Revolution_HD-One_71.1.zip /sdcard/ ?
---------- Post added at 01:43 AM ---------- Previous post was at 01:42 AM ----------
majmoz said:
You can copy it from your PC to your phone via the USB cable using windows explorer
Click to expand...
Click to collapse
Not when the phone is not booting in the OS

i actually never stopped it, haha jus letting it sit there just in case, but i dont think its going to do anything.....this is such a bummer

sigmaul said:
i actually never stopped it, haha jus letting it sit there just in case, but i dont think its going to do anything.....this is such a bummer
Click to expand...
Click to collapse
it should take between 5-10 min max to transfer the rom.

alray.....you a the ****ing man dude!! i got the rom on and working now!!! thanks so much dude. i guess ill try and continue converting this thing to a google edition, if its even possible to get s-off with hboot 1.57. but again thanks man youre a genius =]]

sigmaul said:
alray.....you a the ****ing man dude!! i got the rom on and working now!!! thanks so much dude. i guess ill try and continue converting this thing to a google edition, if its even possible to get s-off with hboot 1.57. but again thanks man youre a genius =]]
Click to expand...
Click to collapse
glad it worked :good:
The only pple i know here who have successfully s-off'ed on 1.57 used arhd 31.6. you might want to try it if it doesnt work on 71.1. good luck

alray said:
glad it worked :good:
The only pple i know here who have successfully s-off'ed on 1.57 used arhd 31.6. you might want to try it if it doesnt work on 71.1. good luck
Click to expand...
Click to collapse
Okay my phone is s-off on 1.57.. How can I go back to stock.. I need to send to warranty.. Do I have to do super cid ?

eshwar.sriram said:
Okay my phone is s-off on 1.57.. How can I go back to stock.. I need to send to warranty.. Do I have to do super cid ?
Click to expand...
Click to collapse
Follow nkk71's Guide to Stock. No, you should not do superCID.

[HOW TO] Really go back to HTC stock ROM and solve boot problems - noob guide

I managed to solve boot problems with broken Desire 500 HTC's (not booting, orange led blinking, vibrating 7 times etc.)
Just put your phone without battery in a ziplock bag in the freezer for 1 hour (not kidding). Let it sit for another 1/2 hour at room temperature, then insert battery and try booting into fastboot. If it doesn't work, remove battery and try again in half hour. Try until it boots, I tried about 15 times before I managed to boot into fastboot mode. So don't give up. After you manage to boot into fastboot mode, follow this guide to restore your phone functionality.
Works for:
HTC Desire 500 and maybe other HTC phones
If you are on Windows 7, skip this next step. To install ADB and Fastboot drivers on Windows 8 and 10, forum member @kmark23 posted the following solution:
1. Uninstall all drivers for HTC phone
2. Install latest HTC Sync Manager
3. Connect phone in normal mode
4. Connect phone in fastboot mode (system reports unrecognized device)
5. Run regedit as administrator
6. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags
7. Right-click on usbflags, click new > key, name it 0BB40FF00100
8. Select 0BB40FF00100 and in the right window right click > new > binary value
9. Rename created binary value to SkipBOSDescriptorQuery
10. Right click SkipBOSDescriptorQuery > modify binary data, type 01 00 00 00 , click ok
11. Unplug usb cable and plug again.
12. In fastboot cmd window type fastboot devices, press enter and see if your device is listed
Connect your phone directly to the PC and don't use a USB 3.0 port, only 2.0
Links for download are down the page
Your battery should be at least 40% charged before doing this. And of course, do everything at your own risk, I am not responsible for any bricked devices.
INSTRUCTIONS:
Z4U = single sim
Z4DUG = dual sim
Download 0P3ZIMG HTC Europe or Asia for your phone (single or dual sim) and region
If you want to use the RUU files instead, your bootloader must be locked. Instructions on how to relock the bootloader are below. After that, just run the RUU file as admin on your pc and follow on screen istructions, but your phone must have the correct CID (country ID) for the region the RUU is intended for, or else it won't install. If the RUU installer force closes click here for the solution.
You can also extract the ROM file from the RUU then flash it using fastboot, just like 0P3ZIMG files in this guide. To extract the ROM file, run the RUU as admin and after the install wizard don't click nothing, just let the window opened. Click windows Start and in the search box type %temp% and go to the folder. While in temp folder, in the search window in windows explorer type rom.zip and press enter. Copy the file rom.zip to your fastboot folder and use it like 0P3ZIMG files described next in this guide.
Uninstall old usb drivers for HTC, Samsung Kies, and other similar phone software or drivers.
Download and install Java Runtime Environment
Download and install android SDK Tools. After installation is complete, a window will pop-up. Check only platform tools and Google usb driver and download.
Download and install HTC Sync Manager
Download fastboot binaries and extract fastboot-win.zip in a folder on the desktop
Browse to Program Files (x86)\Android\android-sdk\platform-tools and copy files AdbWinApi.dll, AdbWinUsbApi.dll and adb.exe to fastboot-win folder you extracted on the desktop
Reboot your pc.
1. Copy the file 0P3ZIMG for HTC Europe or Asia to fastboot-win folder on the desktop. Rename copied file to Z4DUGIMG.img or Z4UIMG.img, depending on your phone.
2. Inside the fastboot-win folder on the desktop, holding down the shift key, right click on an empty space and then click open command window here
3. Boot your phone in fastboot mode (hold Power and vol – keys)
4. Connect phone to the pc with a good data cable. You should see Fastboot usb on your phone screen and a driver installing on your pc.
5. On the command window opened earlier, type fastboot devices. A device should be listed.
6. Next, on the command window, write the following commands:
fastboot oem lock – wait for the phone to restart, and on the phone screen you should see *Relocked*
type fastboot oem rebootRUU - your phone will go to a black screen with the HTC logo
type fastboot flash zip Z4DUGIMG.zip or fastboot flash zip Z4UIMG.img, depending on your phone
wait, the process is very long. DON’T DO ANYTHING UNTIL IT FINISHES COMPLETELY
After the process is totally completed, type fastboot reboot
Done.
After restoring the whole system, if you still want to root your phone, unlock your bootloader and install ONLY this recovery and latest SuperSU:
PhilZ Touch Recovery 6.59.0
SuperSU
Java Runtime Environment
Android SDK Tools- download and install windows.exe file
HTC Sync Manager
Fastboot binaries
ROM files

razvangrig said:
I managed to solve boot problems with broken Desire 500 HTC's (not booting, orange led blinking, vibrating 7 times etc.)
Just put your phone without battery in a ziplock bag in the freezer for 1 hour (not kidding). Let it sit for another 1/2 hour at room temperature, then insert battery and try booting into fastboot. If it doesn't work, remove battery and try again in half hour. Try until it boots, I tried about 15 times before I managed to boot into fastboot mode. So don't give up. After you manage to boot into fastboot mode, follow this guide to restore your phone functionality.
Works for:
HTC Desire 500
If you are on Windows 7, skip this next step. To install ADB and Fastboot drivers on Windows 8 and 10, forum member @kmark23 posted the following solution:
1. Uninstall all drivers for HTC phone
2. Install latest HTC Sync Manager
3. Connect phone in normal mode
4. Connect phone in fastboot mode (system reports unrecognized device)
5. Run regedit as administrator
6. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags
7. Right-click on usbflags, click new > key, name it 0BB40FF00100
8. Select 0BB40FF00100 and in the right window right click > new > binary value
9. Rename created binary value to SkipBOSDescriptorQuery
10. Right click SkipBOSDescriptorQuery > modify binary data, type 01 00 00 00 , click ok
11. Unplug usb cable and plug again.
12. In fastboot cmd window type fastboot devices, press enter and see if your device is listed
Links for download are down the page
Your battery should be at least 40% charged before doing this. And of course, do everything at your own risk, I am not responsible for any bricked devices.
INSTRUCTIONS:
Z4U = single sim
Z4DUG = dual sim
Download 0P3ZIMG HTC Europe or Asia for your phone (single or dual sim) and region
If you want to use the RUU files instead, your bootloader must be locked. Instructions on how to relock the bootloader are below. After that, just run the RUU file as admin on your pc and follow on screen istructions, but your phone must have the correct CID (country ID) for the region the RUU is intended for, or else it won't install. If the RUU installer force closes see http://forum.xda-developers.com/showpost.php?p=53081344&postcount=94 for solution.
You can also extract the ROM file from the RUU then flash it using fastboot, just like 0P3ZIMG files in this guide. To extract the ROM file, run the RUU as admin and after the install wizard don't click nothing, just let the window opened. Click windows Start and in the search box type %temp% and go to the folder. While in temp folder, in the search window in windows explorer type rom.zip and press enter. Copy the file rom.zip to your fastboot folder and use it like 0P3ZIMG files described next in this guide.
Uninstall old usb drivers for HTC, Samsung Kies, and other similar phone software or drivers.
Download and install Java Runtime Environment
Download and install android SDK Tools. After installation is complete, a window will pop-up. Check only platform tools and Google usb driver and download.
Download and install HTC Sync Manager
Download fastboot binaries and extract fastboot-win.zip in a folder on the desktop
Browse to Program Files (x86)\Android\android-sdk\platform-tools and copy files AdbWinApi.dll, AdbWinUsbApi.dll and adb.exe to fastboot-win folder you extracted on the desktop
Reboot your pc.
1. Copy the file 0P3ZIMG for HTC Europe or Asia to fastboot-win folder on the desktop. Rename copied file to Z4DUGIMG.img or Z4UIMG.img, depending on your phone.
2. Inside the fastboot-win folder on the desktop, holding down the shift key, right click on an empty space and then click open command window here
3. Boot your phone in fastboot mode (hold Power and vol – keys)
4. Connect phone to the pc with a good data cable. You should see Fastboot usb on your phone screen and a driver installing on your pc.
5. On the command window opened earlier, type fastboot devices. A device should be listed.
6. Next, on the command window, write the following commands:
fastboot oem lock – wait for the phone to restart, and on the phone screen you should see *Relocked*
type fastboot oem rebootRUU - your phone will go to a black screen with the HTC logo
type fastboot flash zip Z4DUGIMG.zip or fastboot flash zip Z4UIMG.img, depending on your phone
wait, the process is very long. DON’T DO ANYTHING UNTIL IT FINISHES COMPLETELY
After the process is totally completed, type fastboot reboot
Done.
Java Runtime Environment:
http://java.com/en/
Android SDK Tools - download and install file installer_r24.4.1-windows.exe
http://developer.android.com/sdk/index.html#Other
HTC Sync Manager
http://www.htc.com/us/software/htc-sync-manager/
Download fastboot binaries:
https://www.htcdev.com/process/legal_fastboot_win
ROM files
http://forum.gsmhosting.com/vbb/f485/htc-mtk-spd-qualcomm-cpu-flash-files-jamesjerss-updated-02-10-2015-a-1949859/#post11057152
Click to expand...
Click to collapse
Does this solve problem with vibrations from rumrunner proto 0.71 S-OFF or vibrations still stay?And can i use only disabled driver signature enforcement on windows 8.1 without modifying registry i run windows 8.1 on BIOS not UEFI and have legacy boot mode so i can on F8 select disable driver signature enforcement on number 7.

This should solve any software caused problems, since it rewrites the bootloader, radio, recovery, system partition and data partition. Your phone will be S-ON and unrooted, just like it came from the factory. I don't know about the driver signature enforcement on windows 8.1, I didn't try it. I only tested the above solution on windows 10, both Legacy and UEFI boot.
If you are S-OFF you can use any RUU .exe file if you do this:
Boot into fastboot mode, enter the command "fastboot oem readcid". Make a note of your original CID.
Enter the command "fastboot oem writecid 11111111
Enter the command "fastboot read cid" - it should confirm your CID is 11111111
Reboot the bootloader.
Don't forget, before you flash the RUU you have to relock the bootloader with fastboot oem lock command

It doesn't work. After I type fastboot flash zip Z4UIMG.img i get an error "FAILED (remote: 12 signature verify fail)".

sharleyP said:
It doesn't work. After I type fastboot flash zip Z4UIMG.img i get an error "FAILED (remote: 12 signature verify fail)".
Click to expand...
Click to collapse
Your bootloader must be locked before you flash
Your must flash the file matching your phone CID, otherwise it won't install. HTC signed encrypted files check the country id and firmware version before they install. So you can not downgrade the firmware, only upgrade it. Try the RUU_Z4_DUG_Asia file if the European does not work. Check your phone CID with fastboot oem readcid and see for wich country your phone is.

razvangrig said:
Your bootloader must be locked before you flash
Your must flash the file matching your phone CID, otherwise it won't install. HTC signed encrypted files check the country id and firmware version before they install. So you can not downgrade the firmware, only upgrade it. Try the RUU_Z4_DUG_Asia file if the European does not work. Check your phone CID with fastboot oem readcid and see for wich country your phone is.
Click to expand...
Click to collapse
Bootloader is locked. I performed all steps form your instruction. I tried Asian file but it also does not work - same error. My CID is HTC__032 - Eastern Europe.

sharleyP said:
Bootloader is locked. I performed all steps form your instruction. I tried Asian file but it also does not work - same error. My CID is HTC__032 - Eastern Europe.
Click to expand...
Click to collapse
When you connect your phone, don't use a USB3.0 port, only 2.0. I have the same CID as you and had no error flashing European HTC file. Try with the bootloader unlocked, try another data cable, remove phone battery and start the process again. You can copy Z4DUGIMG to your SD card and reboot the phone in fastboot. Hboot scans the SD card, and the update should automatically begin, but I haven't tried this. As a last solution, use Rumrunner s-off to get s-off (works with Desire 500). After S-OFF write your CID with command "fastboot oem writecid 11111111" (SuperCID) and you should be able to install any HTC firmware for this phone.

razvangrig said:
When you connect your phone, don't use a USB3.0 port, only 2.0. I have the same CID as you and had no error flashing European HTC file. Try with the bootloader unlocked, try another data cable, remove phone battery and start the process again. You can copy Z4DUGIMG to your SD card and reboot the phone in fastboot. Hboot scans the SD card, and the update should automatically begin, but I haven't tried this. As a last solution, use Rumrunner s-off to get s-off (works with Desire 500). After S-OFF write your CID with command "fastboot oem writecid 11111111" (SuperCID) and you should be able to install any HTC firmware for this phone.
Click to expand...
Click to collapse
I got the CID HTC__102 and i f*cked up my phone. I didn't done a Backup. I tried to Flash James Rom and the U.F.O Rom, but it failed with unlocked bootloader and S-ON... I have Radio-14.16.36Q4.22
I tried it with the Ruu Asian Version, but it doesn't sends/loads the 5 Files to my Phone... It just goes on and on, over 10 minutes... there are just the dots .. , ... , .... , .... , ..... , ...... , and so on.
I relocked it before trying the Ruu Thing. Bootloader Shows Relocked. I got TWCM installed an having the Single Sim Version from Germany
I hope you can help me! Thanks very much
I Forget to say, that i can see my device with fastboot devices, but i got a couple of Errors trying to install al the roms, i done also the Complete Wipes. And i got no OS installed!!

TheRealJoker31 said:
I got the CID HTC__102 and i f*cked up my phone. I didn't done a Backup. I tried to Flash James Rom and the U.F.O Rom, but it failed with unlocked bootloader and S-ON... I have Radio-14.16.36Q4.22
I tried it with the Ruu Asian Version, but it doesn't sends/loads the 5 Files to my Phone... It just goes on and on, over 10 minutes... there are just the dots .. , ... , .... , .... , ..... , ...... , and so on.
I relocked it before trying the Ruu Thing. Bootloader Shows Relocked. I got TWCM installed an having the Single Sim Version from Germany
I hope you can help me! Thanks very much
I Forget to say, that i can see my device with fastboot devices, but i got a couple of Errors trying to install al the roms, i done also the Complete Wipes. And i got no OS installed!!
Click to expand...
Click to collapse
Have you tried flashing the 0P3ZIMG Z4_U HTC Europe using fastboot commands and didn't work? Have you used a usb 2.0 port?
Check out this thread also and try the roms there for your hboot version

razvangrig said:
Have you tried flashing the 0P3ZIMG Z4_U HTC Europe using fastboot commands and didn't work? Have you used a usb 2.0 port?
Click to expand...
Click to collapse
Yes, Sir. Tried that already. I am using USb2.0 Ports, yeah.
The =P3ZIMG Z4_U HTC Europe is the first one from the Forum-site you send or? The one with ~689MB?
Trying it again now, adding a Screenshot
http://www.xup.in/dl,66261527/HTC_FLASH.PNG/

TheRealJoker31 said:
Yes, Sir. Tried that already. I am using USb2.0 Ports, yeah.
The =P3ZIMG Z4_U HTC Europe is the first one from the Forum-site you send or? The one with ~689MB?
Trying it again now, adding a Screenshot
http://www.xup.in/dl,66261527/HTC_FLASH.PNG/
Click to expand...
Click to collapse
Download the European RUU Z4_U (not the 0P3ZIMG). Run the RUU on your computer until the wizard comes up. While the RUU wizard is open, open Explorer in Windows and type %temp% in the navigation bar. There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC recovery and it is needed to run the RUU. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
Unlock your bootloader
Open a command prompt in ADB folder. Flash the stock recovery extracted in step 3 above using the following command:
fastboot flash recovery recovery.img or fastboot flash recovery recovery_signed.img
Relock the bootloader using the following command:
fastboot oem lock
Re-run the RUU on your PC

razvangrig said:
Download the European RUU Z4_U (not the 0P3ZIMG). Run the RUU on your computer until the wizard comes up. While the RUU wizard is open, open Explorer in Windows and type %temp% in the navigation bar. There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC recovery and it is needed to run the RUU. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
Unlock your bootloader
Open a command prompt in ADB folder. Flash the stock recovery extracted in step 3 above using the following command:
fastboot flash recovery recovery.img or fastboot flash recovery recovery_signed.img
Relock the bootloader using the following command:
fastboot oem lock
Re-run the RUU on your PC
Click to expand...
Click to collapse
For me ist not: recovery_signed, ist boot_signed, flashed it with the command: fastboot Flash recovery boot_signed.img , went fine, and then fastboot oem lock while in fastboot it restarted and showed above again Relocked, and then started RUU again and it's doing the same Thing, it just don't proceeds, it stays at 0/5 files.
EDIT: I didn't said that my phone Shows the black Background with silver/White HTC Logo during this try to send the 5 files, or whatever it tries to do...

TheRealJoker31 said:
For me ist not: recovery_signed, ist boot_signed, flashed it with the command: fastboot Flash recovery boot_signed.img , went fine, and then fastboot oem lock while in fastboot it restarted and showed above again Relocked, and then started RUU again and it's doing the same Thing, it just don't proceeds, it stays at 0/5 files.
I think there is a problem with your fastboot drivers or with the data cable you are using. I will try to get the recovery.img for your phone. What is your Hboot ver.?
Click to expand...
Click to collapse

razvangrig said:
TheRealJoker31 said:
For me ist not: recovery_signed, ist boot_signed, flashed it with the command: fastboot Flash recovery boot_signed.img , went fine, and then fastboot oem lock while in fastboot it restarted and showed above again Relocked, and then started RUU again and it's doing the same Thing, it just don't proceeds, it stays at 0/5 files.
I think there is a problem with your fastboot drivers or with the data cable you are using. I will try to get the recovery.img for your phone. What is your Hboot ver.?
Click to expand...
Click to collapse
Okay thank you. I got HBOOT-1.03.0001
Click to expand...
Click to collapse

TheRealJoker31 said:
razvangrig said:
Okay thank you. I got HBOOT-1.03.0001
Click to expand...
Click to collapse
Download ROM for hBoot 1.03 Build 1.34.401.1
Download firmware_1.34.401.1
Put ROM file on sd-card
Put firmware file in fastboot folder and rename to "firmware.zip"
Boot into CWM or TWRP recovery
Make full wipe (data, cache, system, dalvik cache)
Install the ROM zip file from SD-card
Reboot the phone in bootloader
Connect your device on PC
Enter next commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse

razvangrig said:
TheRealJoker31 said:
Download ROM for hBoot 1.03 Build 1.34.401.1
Download firmware_1.34.401.1
Put ROM file on sd-card
Put firmware file in fastboot folder and rename to "firmware.zip"
Boot into CWM or TWRP recovery
Make full wipe (data, cache, system, dalvik cache)
Install the ROM zip file from SD-card
Reboot the phone in bootloader
Connect your device on PC
Enter next commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
Should the Bootloader be locked or unlocked during that process?
I think Unlocked, else i can't install TWRP/CWM
Click to expand...
Click to collapse

TheRealJoker31 said:
razvangrig said:
Should the Bootloader be locked or unlocked during that process?
I think Unlocked, else i can't install TWRP/CWM
Click to expand...
Click to collapse
If you need CWM for your phone download it here PhilZTouch 6.59.0 (hboot-1.03.0001) One Sim by RealDob
Before you install the ROM from sd-card using CWM, your bootloader needs to be unlocked
Before flashing firmware.zip using fastboot, you need to relock the bootloader
Click to expand...
Click to collapse

razvangrig said:
TheRealJoker31 said:
Before you install the ROM from sd-card using CWM, your bootloader needs to be unlocked
Before flashing firmware.zip using fastboot, you need to relock the bootloader
Click to expand...
Click to collapse
Unlocked it, installed TWRP, Wiped but it failed, maybe cause there were no Folder like /data /System, started to install it from the zip.
Formatting User Data
Formatting Cache
Formatting System
Writting Data
Flashing System
EDIT:
Flashing Boot
Flashing Recovery
Setting Symlinks and permissions
Unmount System
Unmount Data
Unmount Cache
Install complete!
Please reboot your System.
updating Partition Details....
E: Unable to Mount /data ; /system ; /devlog
Okay, i rebooted, it started, works now. What is with the Firmware zip?
Should i Flash it? And i would like to Flash a ROM, i think every ROM is better than the Stock.
But which Rom should i use? did you tried one?
I just want WhatsApp and a Performance boost, while waiting 40days on the Nexus 6p, Sir!
Thank you very much!!!!
Click to expand...
Click to collapse

No problem, now relock bootloader and flash firmware.zip

TheRealJoker31 said:
razvangrig said:
Okay, i rebooted, it started, works now. What is with the Firmware zip?
Should i Flash it? And i would like to Flash a ROM, i think every ROM is better than the Stock.
But which Rom should i use? did you tried one?
I just want WhatsApp and a Performance boost, while waiting 40days on the Nexus 6p, Sir!
Thank you very much!!!!
Click to expand...
Click to collapse
firmware.zip rewrites all partitions (hboot, radio, recovery etc) and turns your phone back to stock, unrooted and s-off
Don't know about wich rom is better, I know only 2 roms for single sim, UFO and james Rom. My desire 500 is dual sim
Click to expand...
Click to collapse

How to Unlock Bootloader and Install TWRP

--------------------------------> DISCLAIMER: <------------------------------------​
Guide for pure educational purpose. If you are going to use it, you do it to *your risk and danger, I will not be held responsible if your phone will not work anymore.
Depending on the phone manufacturer, root and unlock the bootloader could invalidate the warranty of the phone​
-------------------------------> PRE-REQUIREMENTS <---------------------------------​
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here https://devsjournal.com/usb-drivers-for-all-android-devices.html or from attachment:
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here https://devsjournal.com/download-minimal-adb-fastboot-tool.html or from attachment:
Scrolling through the page you will have 2 options: Download or Portable
(choose the one that you prefer)
Pre-Requisite 3
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device (read all tutorial before do it, because it will be wiped all data from the phone)
Settings -> Applications -> Developer Options
Settings -> Applications -> Development
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'Build version' entry
A pop-up should appear, telling you 'now you are a developer'
In case of disaster follow this tutorial:​Restore Stock Image and Lock the Bootloader (for Warranty)​
-------------------------------> UNLOCK BOOTLOADER <---------------------------------​
IMPORTANT NOTE: Before doing this, know that this operation completely reset your device and after rebooting, you will find the phone as if he had just left out of the box. So you'll need to configure your phone again and reinstall all apps.
To unlock bootloader tap on:
Settings -> Applications -> Developer Options
(If you don't see the delevopers option you need to un-hide. To activate developer option click 7 times on ZUI version under settings -> system -> about. Once you did that you get developer options in settings -> system)
Now Click on it (Developers option) and activate the options OEM unlocking and USB debugging
If you have a Pin or Password, it will ask you to re-enter it.
You will see a popup where you will be asked to confirm this operation.
Now start the phone in boolader by doing this:
1) Connect the phone to the PC
2) Start the Minimal ADB & Fastboot program from the PC
3) On the PC screen, type: adb reboot bootloader​
(A request may appear on the phone screen with permission of USB debugging, accept it)
The phone will now restart in Booloader mode.
4) Now that you are in bootloader mode, from the PC, from the screen
Minimal ADB and Fastboot type:
fastboot -i 0x2b4c oem unlock-go​
The response will look like this:
...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\adb>​Type:
fastboot reboot​
Now, during the reboot phase, the phone will proceed with a factory reset and will restart normally (it could take a couple of minutes)​
Done, now your phone has the bootloader unlocked.
-------------------------------> HOW TO INSTALL TWRP <---------------------------------​
Download the TWRP from here or mirror
1) Open the folder where your TWRP Recovery .img file is saved.
2)Then open a CMD window inside that folder. To do that, Shift + Right click on any empty white space inside the folder and then select Open command window here.
3) Connect your Android device to the PC. Type the following into the command window to boot your device into bootloader/fastboot mode:
adb reboot bootloader​ If your asks for permission to “Allow USB debugging”, tap OK.
4) Once your device boots into bootloader mode, type this into the command line.
fastboot flash recovery recovery-TWRP-3.2.3-0110-LENOVO_Z5PRO-CN-wzsx150​
5) Once TWRP is successfully flashed on your device, type this final command to reboot your device.
fastboot reboot​
Well, now you have installed the TWRP Recovery.
If you are interested to know how to root your phone: Follow this TUTORIAL

HOW TO INSTALL TWRP no.2
I can't find cmd.
I can only see the power shell

hohoim said:
HOW TO INSTALL TWRP no.2
I can't find cmd.
I can only see the power shell
Click to expand...
Click to collapse
because you are using win 10, inside the option there is "use powershell instead cmd" of something about that, uncheck it!

Can you push it with original rom like Xiaomi Mi flash?
BadCluster said:
because you are using win 10, inside the option there is "use powershell instead cmd" of something about that, uncheck it!
Click to expand...
Click to collapse
thank you

BadCluster said:
because you are using win 10, inside the option there is "use powershell instead cmd" of something about that, uncheck it!
Click to expand...
Click to collapse
i need help, i cant unlock bootloader a have 10.0.355 version firmware

nerak11111 said:
i need help, i cant unlock bootloader a have 10.0.355 version firmware
Click to expand...
Click to collapse
im on the same firmware, I'm able to input the adb reboot bootloader command and the phone loads in to the bootloader mode but after my pc doesnt recognise the phone, and when i input the fastboot -i 0x2b4c oem unlock-go, nothing happens and it displays waiting for any device,
i think the problem is that after the phone load in to the bootloader mode, the doesnt recognize it anymore so i cant send any commands to it,
can you help please,

i found a way to lock the bootloader after you installed the original rom!
this will solve the < waiting for devices > error when phone is connected to pc
follow this tutorial to install the propper driver if your PC does not recognize the phone in fastboot: tutorial
how do i know if i need this?
to know if the proper drivers are installed open adb and type "adb devices" to see if your device is connected
if your device is connected and seen by adb, proceed to type "fastboot devices". if your device is recognized, you are good to go, if not, please follow the youtube tutorial as it helped me solve this problem.
when your device is read as a adb fastboot device, reboot into bootloader using "adb reboot bootloader"
after this, type "fastboot flashing lock" to relock your device. you will get a message on the device to ask for permission.
BE AWARE! THIS WILL WIPE YOUR PHONE TO FACTORY RESET!
this steps will probably also help to unlock the bootloader in version355, but i have not tried that. please leave your findings below if you tried this!

does it work with lenovo z5 pro gt?

Thanks man i will try this as soon as they deliver my phone still waiting on it.

[/COLOR]
anonOmattie said:
i found a way to lock the bootloader after you installed the original rom!
this will solve the < waiting for devices > error when phone is connected to pc
follow this tutorial to install the propper driver if your PC does not recognize the phone in fastboot:
how do i know if i need this?
to know if the proper drivers are installed open adb and type "adb devices" to see if your device is connected
if your device is connected and seen by adb, proceed to type "fastboot devices". if your device is recognized, you are good to go, if not, please follow the youtube tutorial as it helped me solve this problem.
when your device is read as a adb fastboot device, reboot into bootloader using "adb reboot bootloader"
after this, type "fastboot flashing lock" to relock your device. you will get a message on the device to ask for permission.
BE AWARE! THIS WILL WIPE YOUR PHONE TO FACTORY RESET!
this steps will probably also help to unlock the bootloader in version355, but i have not tried that. please leave your findings below if you tried this!
Click to expand...
Click to collapse
I tried, But I can't.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ver: 355
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
c4aec27a device
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing lock
...
FAILED (remote: Device already : locked!)
finished. total time: 0.012s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing lock
...
FAILED (remote: Device already : locked!)
finished. total time: 0.059s

SrCDA said:
does it work with lenovo z5 pro gt?
Click to expand...
Click to collapse
i am not sure, but except for cpu the phones are similar. you can try the steps i provided and see if it will lock. no chance of bricking your phone if following shown commands.
please reply if this work!
vinashiny said:
[/COLOR]
I tried, But I can't.
ver: 355
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
c4aec27a device
[B]------------phone is seen by adb as device[/B]
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
[B]-------------phone is not seen as fastboot device, so follow tutorial provided[/B]
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flashing lock
...
[B]FAILED (remote: Device already : locked!)[/B]
[B]------------why try to lock a already locked phone??[/B]
finished. total time: 0.012s
[/QUOTE]
Click to expand...
Click to collapse

How do I update the OS once i've unlocked the bootloader and rooted?
Do i just simply install the zip update via TWRP? Or do i need to flash it with the qualcomm flashing tool?

I have activate the oem , but in th bootloader it still show that the oem is failed ,it means it haven't turn on the button i don't know why i can't unlock the oem

maxihinz said:
How do I update the OS once i've unlocked the bootloader and rooted?
Do i just simply install the zip update via TWRP? Or do i need to flash it with the qualcomm flashing tool?
Click to expand...
Click to collapse
you should wait for the rom to be updated, and flash it with qfil flasher. there are currently nop twrp roms available...
Blade_zheng said:
I have activate the oem , but in th bootloader it still show that the oem is failed ,it means it haven't turn on the button i don't know why i can't unlock the oem
Click to expand...
Click to collapse
so you want to open or close bootloader?

anonOmattie said:
you should wait for the rom to be updated, and flash it with qfil flasher. there are currently nop twrp roms available...
so you want to open or close bootloader?
Click to expand...
Click to collapse
I will be wait.i want to open the bootloader

doesnt work for me, it only shows :
< waiting for any device >
Click to expand...
Click to collapse
and nothing happens, did i miss a step ? should i do something on the bootloader menu ?

anonOmattie said:
i found a way to lock the bootloader after you installed the original rom!
this will solve the < waiting for devices > error when phone is connected to pc
follow this tutorial to install the propper driver if your PC does not recognize the phone in fastboot:
Click to expand...
Click to collapse
i did this
still gives me the dreadful waiting for any device message

Does NOT work on Win 10!!
It can Reboot to the Bootloader but cant Unlock it always is Say < waiting for any device > and nothing happen....

I have a Lenovo Z5 Pro, firmware 10.0.355, bootloader unlocked and TWRP (no root).
Can I flash the OTA update (I received the 10.5.153 - Android 9.0 OTA update) with the TWRP or I must flash again the original recovery?
If I need the original recovery, anyone knows where I can download the original one (10.0.355).
Thank you.

what about TWRP for Z5 Pro GT 855 version ??

Help me recover my motorola g5s plus Android phone

Hi All,
I need help from you experts to recover my phone moto g5s plus
Type : M271C Model : XT1806
The phone was working without any issues but suddenly got restarted and now i's stuck in the "Fast Boot Flash" Mode.
It cannot boot and the "Boot Loader Log" screen says below.
"Start Up Failed:
Your Device did not startup successfully.
Use the software repair assistant on computer to repair your device.
Connect your device to your computer to get the software repair assistant.
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason : Fall Through from normal boot mode
USB Connected"
1. I installed the "Rescue and Smart Assistant" software and tried to recover from there but unfortunately it does not recognize my phone model.
2. Tried to install Install TWRP Custom Recovery tool. But I cannot do it because the "USB debugging " is not enabled on the phone.
3. 'USB debugging"and "OEM Unlock" on my Android device is not enabled so I cannot Unlock Bootloader
Is there any way that I can boot into recovery or install a custom ROM without having the "USB Debugging" and "OEM Unlock" Enabled in my phone?
Thanks

Are you using adb for recovery?

andres_vacal said:
Are you using adb for recovery?
Click to expand...
Click to collapse
No. ADB cannot be used since my device is not enabled "USB Debugging"

USB debugging should not be required to unlock the bootloader as you are using fastboot commands to unlock the bootloader rather than ADB commands.
Try "fastboot reboot recovery"

andres_vacal said:
USB debugging should not be required to unlock the bootloader as you are using fastboot commands to unlock the bootloader rather than ADB commands.
Try "fastboot reboot recovery"
Click to expand...
Click to collapse
I get following error when I run that command.
Rebooting into recovery FAILED (remote: 'Unknown command')
fastboot: error: Command failed

dharshana1 said:
I get following error when I run that command.
Rebooting into recovery FAILED (remote: 'Unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
Okay, I think I untherstand whats happening. Its probable that any way or another you deleted your recovery or directly your ROM.
So i´ll recommend you to download and run TWRP(You can look out on the internet for your specific device)
If it runs correctly, go to reboot and check out if in the top part says "No OS installed", if it says that, then you will have to lock out for a compatible ROM and instal it.
If you have any thoughts let me know how it goes..

andres_vacal said:
Okay, I think I untherstand whats happening. Its probable that any way or another you deleted your recovery or directly your ROM.
So i´ll recommend you to download and run TWRP(You can look out on the internet for your specific device)
If it runs correctly, go to reboot and check out if in the top part says "No OS installed", if it says that, then you will have to lock out for a compatible ROM and instal it.
If you have any thoughts let me know how it goes..
Click to expand...
Click to collapse
Hello,
Thanks for the reply, I tried to install the TWRP tool that is for my specific device, but it won't allow me to install since "USB debugging" is not enabled in my device.
Is there any other way to install that without USB debugging enabled?
Thanks

Okay, so i´ll try to explain in detail how to install TWRP via Fastboot commands (No usb debugging needed since you are using fastboot)
1. Make sure you have all the specific drivers for using fastboot.
2. Type "fastboot devices" and make sure your device appears on the command prompt
(it should apper something like "5f684fe2").
3. Type "fastboot erase recovery" to make sure the old recovery is no longer avaiable in your device.
4. Send the TWRP.img file that you already have to the adb folder you are using on the command prompt
5. Type "fastboot flash recovery TWRP.img" ("TWRP" is the recovery´s name you have saved)
6. Tyoe "fastboot reboot recovery" and see if TWRP is now installed.
Important note: Make sure you have saved all the important files from your phone.
If this doesn´t fuction, after you make step 2 succesfully:
Type these 3 commands:
"fastboot erase system"
"fastboot erase data"
"fastboot erase cache"
and "fastboot reboot"
Then repeat the instalation process.

andres_vacal said:
Okay, so i´ll try to explain in detail how to install TWRP via Fastboot commands (No usb debugging needed since you are using fastboot)
1. Make sure you have all the specific drivers for using fastboot.
2. Type "fastboot devices" and make sure your device appears on the command prompt
(it should apper something like "5f684fe2").
3. Type "fastboot erase recovery" to make sure the old recovery is no longer avaiable in your device.
4. Send the TWRP.img file that you already have to the adb folder you are using on the command prompt
5. Type "fastboot flash recovery TWRP.img" ("TWRP" is the recovery´s name you have saved)
6. Tyoe "fastboot reboot recovery" and see if TWRP is now installed.
Important note: Make sure you have saved all the important files from your phone.
If this doesn´t fuction, after you make step 2 succesfully:
Type these 3 commands:
"fastboot erase system"
"fastboot erase data"
"fastboot erase cache"
and "fastboot reboot"
Then repeat the instalation process.
Click to expand...
Click to collapse
Hi,
Thank you so much for the reply. I can see a device when I run the "fastboot devices" command. But when I tried above other commands (fastboot erase ...) they failed with below error.
Erasing 'recovery' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'system' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'data' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
when I run the fastboot erase cache command below error throws
Erasing 'cache' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
Thank you for your time helping me resolve this issue, anything else that I can try out?

Okay so I think your phone´s bootloader is locked.
So try this out: https://forum.xda-developers.com/t/...der-root-and-recovery-for-the-moto-g.3418432/ (Unloock bootloader section)
Hopefully it will get your bootloader unlocked and then you will be ready to do the process I posted before.
This is going harder than I thought.

dharshana1 said:
Hi All,
I need help from you experts to recover my phone moto g5s plus
Type : M271C Model : XT1806
The phone was working without any issues but suddenly got restarted and now i's stuck in the "Fast Boot Flash" Mode.
It cannot boot and the "Boot Loader Log" screen says below.
"Start Up Failed:
Your Device did not startup successfully.
Use the software repair assistant on computer to repair your device.
Connect your device to your computer to get the software repair assistant.
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason : Fall Through from normal boot mode
USB Connected"
1. I installed the "Rescue and Smart Assistant" software and tried to recover from there but unfortunately it does not recognize my phone model.
2. Tried to install Install TWRP Custom Recovery tool. But I cannot do it because the "USB debugging " is not enabled on the phone.
3. 'USB debugging"and "OEM Unlock" on my Android device is not enabled so I cannot Unlock Bootloader
Is there any way that I can boot into recovery or install a custom ROM without having the "USB Debugging" and "OEM Unlock" Enabled in my phone?
Thanks
Click to expand...
Click to collapse
Just got the same issue..
Did you get it resolved?

andres_vacal said:
Okay so I think your phone´s bootloader is locked.
So try this out: https://forum.xda-developers.com/t/...der-root-and-recovery-for-the-moto-g.3418432/ (Unloock bootloader section)
Hopefully it will get your bootloader unlocked and then you will be ready to do the process I posted before.
This is going harder than I thought.
Click to expand...
Click to collapse
Well this guy has given same steps , but while unlocking bootloader
fastboot oem get_unlock_data
is not working at all, its giving same error which @dharshana1 has mentioned before.
I'm using this cell last three years, it started acting slow all of a sudden and then this thing has happened.

smandar said:
Well this guy has given same steps , but while unlocking bootloader
fastboot oem get_unlock_data
is not working at all, its giving same error which @dharshana1 has mentioned before.
I'm using this cell last three years, it started acting slow all of a sudden and then this thing has happened.
Click to expand...
Click to collapse
I worked with this model 3 weeks ago, and the thing is that in order to unlock bootloader you will need to go to motorola´s web page for getting a password. in this thread you will find how it goes. I untherstand that amazon's versions are unable to unlock bootloader so if you are into that version, bad luck.