I'm having some issues with this device connecting to ADB and I need to flash a different HBOOT so I dont get the error message on boot up. Because of said issue I cant flash a newer HBOOT version to my device via ADB. Is there another way that you can flash other than ADB? I know on previous HTC devices you were able to flash it from the bootloader itself if I remember correctly. Any ideas? Thanks.
Place the hboot in a zip with the android-info.txt file, in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
Code:
fastboot oem rebootRUU
(this puts the device in RUU mode)
Code:
fastboot flash zip hboot.zip
(this flashes the hboot zip file)
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
Code:
fastboot reboot-bootloader
(this reboots the device to bootloader)
santod040 said:
Place the hboot in a zip with the android-info.txt file, in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
Code:
fastboot oem rebootRUU
(this puts the device in RUU mode)
Code:
fastboot flash zip hboot.zip
(this flashes the hboot zip file)
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
Code:
fastboot reboot-bootloader
(this reboots the device to bootloader)
Click to expand...
Click to collapse
Thank you for the response, maybe I wasn't clear enough. I cannot use ADB from my computer AT ALL with this device. It recognizes other devices and shows them when I do adb devices but on the DNA it shows as offline and commands do not work because of that.
spincredible said:
Thank you for the response, maybe I wasn't clear enough. I cannot use ADB from my computer AT ALL with this device. It recognizes other devices and shows them when I do adb devices but on the DNA it shows as offline and commands do not work because of that.
Click to expand...
Click to collapse
what devices does it show?
thayl0 said:
what devices does it show?
Click to expand...
Click to collapse
This is what it shows in ADB:
List of devices attached
FA34GSXXXXXX offline (shows full device but was told by somebody in the past leave most of that info out.)
I know that its DNA related as ADB works just fine on my Gnex without issue.
Are you using Windows 8? There is no HTC drivers for windows 8 that will work. You must use a different windows version or dual boot with Linux.
If you are on a compatible version of windows, try reinstalling the drivers.
Sent from my DNA using my mind.
I'm using Windows 7
Sent from my VS980 4G using Tapatalk
Related
Hey guys sooooooo,
This is what happened will try to be as detailed as possible.
Prime started acting up so decided to flash new rom.
Switched from CWM to TWRP some time ago placed new
rom on ext sd booted in TWRP and like second nature wiped
device like I do on my phone.
Here is the problem I then realized i had TWRP 2.1 which does
not read ext sd cards
Now I am stuck not being able to do anything so being the good
XDA'er i spend hours searching and attempted to flash CWM now
I have NOOOOOOO recovery my Prime hangs at boot screen I believe
I can access Fast boot but not familiar with ADB so before I move forward
And F*%^ things up more HELP
pdotc said:
Hey guys sooooooo,
This is what happened will try to be as detailed as possible.
Prime started acting up so decided to flash new rom.
Switched from CWM to TWRP some time ago placed new
rom on ext sd booted in TWRP and like second nature wiped
device like I do on my phone.
Here is the problem I then realized i had TWRP 2.1 which does
not read ext sd cards
Now I am stuck not being able to do anything so being the good
XDA'er i spend hours searching and attempted to flash CWM now
I have NOOOOOOO recovery my Prime hangs at boot screen I believe
I can access Fast boot but not familiar with ADB so before I move forward
And F*%^ things up more HELP
Click to expand...
Click to collapse
If you have your twrp 2.1 on pc, do fastboot install (see the twrp page for details) then adb push a rom to the prime and install it... you should be okay then....
Gage_Hero said:
If you have your twrp 2.1 on pc, do fastboot install (see the twrp page for details) then adb push a rom to the prime and install it... you should be okay then....
Click to expand...
Click to collapse
my device is not showing up in ADB i tried naked drivers anything else I can do?
pdotc said:
my device is not showing up in ADB i tried naked drivers anything else I can do?
Click to expand...
Click to collapse
When you plug the device into the pc, is it recovery or fastboot mode? Not sure it will show up if it is in a bootloop. Also if you are in recovery, you should be running adb from within the folder the exe file is in... basically open the folder, press and hold shift then rightclick and select open command prompt here then type adb devices and see what you get.
Gage_Hero said:
When you plug the device into the pc, is it recovery or fastboot mode? Not sure it will show up if it is in a bootloop. Also if you are in recovery, you should be running adb from within the folder the exe file is in... basically open the folder, press and hold shift then rightclick and select open command prompt here then type adb devices and see what you get.
Click to expand...
Click to collapse
I cannot access recovery, I can access the fastboot menu i hear the windows sound. When I check my devices in Win7 it shows fastboot there but when I ADB it says no device.
pdotc said:
I cannot access recovery, I can access the fastboot menu i hear the windows sound. When I check my devices in Win7 it shows fastboot there but when I ADB it says no device.
Click to expand...
Click to collapse
The adb commands won't work in fastboot... you need to use the fastboot commands.
From: http://www.teamw.in/project/twrp2/93
Put the attached file in your nvflashpack folder where you see the fastboot.exe, this way you don't need to type paths. In the same window press and hold shift, rightclick in the window and select open command prompt here. Make sure the prime is already in fastboot mode.... now, copy the command below and rightclick in the command window and select paste (avoids typing mistakes) press enter and with any luck you should be able to boot to twrp recovery...
You will need adb and fastboot for this method. Download the above file, check the md5, rename to twrp.img and put the file in the same directory as your fastboot binary (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
fastboot -i 0x0b05 flash recovery twrp.img
If you use the attached file you don't need the modified bootloader, you will have an older version of twrp but the whole point is to get you running first...
After you do this, boot into recovery, connect the prime to the PC and with the rom in the same folder as adb.exe, open a command window like before. Type adb devices, you should see the prime... then do adb push /the name of your rom.zip/ sdcard/
For the name of the rom, I usually right click the file, go to properties and copy the name.. (no spelling mistakes) again, right click in command window and paste and be sure to put .zip at the end. This should take about 5 minutes to complete. Then in recovery, go to install and you should be able to flash the rom....
Gage_Hero said:
The adb commands won't work in fastboot... you need to use the fastboot commands.
From: http://www.teamw.in/project/twrp2/93
Put the attached file in your nvflashpack folder where you see the fastboot.exe, this way you don't need to type paths. In the same window press and hold shift, rightclick in the window and select open command prompt here. Make sure the prime is already in fastboot mode.... now, copy the command below and rightclick in the command window and select paste (avoids typing mistakes) press enter and with any luck you should be able to boot to twrp recovery...
You will need adb and fastboot for this method. Download the above file, check the md5, rename to twrp.img and put the file in the same directory as your fastboot binary (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
fastboot -i 0x0b05 flash recovery twrp.img
If you use the attached file you don't need the modified bootloader, you will have an older version of twrp but the whole point is to get you running first...
After you do this, boot into recovery, connect the prime to the PC and with the rom in the same folder as adb.exe, open a command window like before. Type adb devices, you should see the prime... then do adb push /the name of your rom.zip/ sdcard/
For the name of the rom, I usually right click the file, go to properties and copy the name.. (no spelling mistakes) again, right click in command window and paste and be sure to put .zip at the end. This should take about 5 minutes to complete. Then in recovery, go to install and you should be able to flash the rom....
Click to expand...
Click to collapse
Ok 1st I want to thank you for your help.
sorry to be a noob at this ADB thing can you tell me a step by step on how get to that fastboot cus i get no where when I type it in?
pdotc said:
Ok 1st I want to thank you for your help.
sorry to be a noob at this ADB thing can you tell me a step by step on how get to that fastboot cus i get no where when I type it in?
Click to expand...
Click to collapse
C:\android-sdk\platform-tools> fastboot -i 0x0b05 flash recovery twrp.img
error: cannot load 'twrp.img'
C:\android-sdk\platform-tools>
C:\android-sdk\platform-tools> fastboot devices
00000 fastboot
C:\android-sdk\platform-tools>
pdotc said:
C:\android-sdk\platform-tools> fastboot devices
00000 fastboot
C:\android-sdk\platform-tools>
Click to expand...
Click to collapse
You will need adb and fastboot for this method. Download the above file, check the md5, rename to twrp.img and put the file in the same directory as your fastboot binary (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
fastboot -i 0x0b05 flash recovery twrp.img
You need to rename the file see the red text above. I would download nvflash from here.... http://androidroot.mobi/t3_nvflash/ the windows zip file.... unzip it and from within the window get your command prompt.... make sure you have the twrp file I attached earlier in the same folder... then copy fastboot -i 0x0b05 flash recovery twrp.img and rightclick and paste into the command filed press enter..... it should install twrp....
now if I have misunderstood and you don't know how to get the prime into fastboot hold volume down and power, when you see the white text in the top left corner, press volume up then volume up to select fastboot of course the prime will be connected to the pc before this...
btw we were all noobs at one point... this is our school....
Gage_Hero said:
You will need adb and fastboot for this method. Download the above file, check the md5, rename to twrp.img and put the file in the same directory as your fastboot binary (unless you have /platform-tools in PATH then you can flash from anywhere). Turn off your device and boot to fastboot (power on while holding volume down, then select the usb icon and hit volume up to confirm). The device will now be in fastboot mode. Plug the device into your computer. Run the following command via the command line:
fastboot -i 0x0b05 flash recovery twrp.img
You need to rename the file see the red text above. I would download nvflash from here.... http://androidroot.mobi/t3_nvflash/ the windows zip file.... unzip it and from within the window get your command prompt.... make sure you have the twrp file I attached earlier in the same folder... then copy fastboot -i 0x0b05 flash recovery twrp.img and rightclick and paste into the command filed press enter..... it should install twrp....
now if I have misunderstood and you don't know how to get the prime into fastboot hold volume down and power, when you see the white text in the top left corner, press volume up then volume up to select fastboot of course the prime will be connected to the pc before this...
btw we were all noobs at one point... this is our school....
Click to expand...
Click to collapse
sent to Asus they want $220 to fix smh now trying to decide on paying or calling it a loss and buying the infinty.
If you can get to fastboot, then it's not a loss and it's recoverable.
Did you already send to Asus?
Sent from my vivow using Tapatalk 2
I am about to root my brothers evo but he has updated and all that stuff. How would i root his phone? Can I follow the root method from Zedomax?
Go to HTC dev and follow the steps to unlock. Once unlocked flash twrp recovery either thru fasboot or goomanager. After that the rooted Rom of your choice
Don't forget about fastboot flashing the boot IMG if needed
Sent from my EVO using xda premium
Let me save you some frustration lol
HTC Dev Unlock
Requirements
HTC Drivers
ADB Tools Mini SDK
Setup
Install HTC Drivers if necessary
Extract ADB Tools anywhere, doesnt matter
Open ADB Tools and hold shift+right click, select open command window here
In phone settings, enable usb debugging and disable fasboot
Connect the phone to pc
Steps
In the command window type adb start-server
Next type adb reboot bootloader
Type fastboot devices to make sure you are connected
Type fastboot oem get_identifier_token
Right click and select mark, click and drag from the top arrows > to the bottom arrows and make sure not to highlight any empty spaces as this will confuse the website, right click and it will be saved to clipboard
Now go to HTC Dev and if you don't already have an account, sign uo for it
Go to unlock bootloader and select other device and accept the agreements
Skip the steps until you get the to token submit window and paste the token you copied earlier and submit.
Go to your email and download the unlock_bin code
Put the code in the ADB Tools folder
Type fastboot flash unlocktoken Unlock_code.bin
When the phone prompt comes up to unlock bootloader hit yes, now you are unlocked, re-enable usb debugging and disable fastboot
Type adb reboot bootloader
Type fastboot devices to make sure phone connected
Type fastboot flash recovery openrecovery-twrp-2.2.2.0-jewel.img
Type erase cache
Reboot phone and you will have unlock and recovery, all thats missing is to restart phone in bootloader and select recovery to flash a rom. Both meanrom and viper have built in kernel installers, should the phone get stuck booting just extract the boot.img from the rom and put it in adb, with phone in fastboot type fastboot flash boot boot.img
What he said
Sent from my EVO using xda premium
Sorry if this has been covered before but I can´t get it to work. I desperatly need help because my One X+ does not boot into recovery. It started with me having CM 10.1 working and all was good. Then when I was using the cam it froze and rebooted but didnt start. I tried to get into recovery but after having chosen the recovery option the phone shows the HTC boot screen, blinks to Another HTC bootscreen and then goes black. I assume it shuts off because I cannot Contact it from fastboot or adb. I have tried flashing a number of different recovery and kernel combinations but the same problem remains. I have even tried the RUU to get it back to stock but even that gives me the same problem afterwards.
I have tried to erase cache and Everything I have found in this wonderful forum but now I dont know what to do. Pls help me
My Hboot is 1.35.0000 and it´s the international version.
Hi darkwing66,
You said...
darkwing66 said:
...I assume it shuts off because I cannot Contact it from fastboot or adb...
Click to expand...
Click to collapse
How did you managed to flash a different boot or another recovery if this device is not recognized by the SDK tool?
Lucky Thirteen said:
Hi darkwing66,
You said...
How did you managed to flash a different boot or another recovery if this device is not recognized by the SDK tool?
Click to expand...
Click to collapse
Sorry, it was after the boot that I cannot access it. If I boot into fastboot its possible to flash recovery and kernel. I´m new at this so I try my best
I have tried flashing openrecovery-twrp-2.4.4.0-enrc2b.img, ViperX+ 1.06 with venomkernelflasher etc. Everythings seems to go well until reboot, or trying to get into recovery. Could it be HW fault or is it just my incompetence to get it right?
And you said you tried to flash the appropriate boot.img for your ROM?
Bootlooping is usually caused by an inpropriate boot.img... Can you described how you do it please? There is something missing.
Are you using any sort of tool or you're doing all this via a command window?
Also are you sure you picked the right Recovery? Don't take the CWM, you must install the TWRP for the ENRC2B version since you have an International phone.
---------- Post added at 01:43 PM ---------- Previous post was at 01:19 PM ----------
Oops! Sorry I didn't saw you had edited your previous post.
It's hard to tell what you have done, you need to precise what you are doing....
At first you were at this :
...CM 10.1 working and all was good. Then when I was using the cam it froze and rebooted but didnt start...
Click to expand...
Click to collapse
then now you are at :
...ViperX+ 1.06 with venomkernelflasher...
Click to expand...
Click to collapse
First, if you have CM 10.1 installed on your phone you CAN NOT use VenomKernelFlasher, the latter is only usable with the Viper ROM. You need to flash the boot.img of CM 10.1 if this is the ROM actually installed on your phone.
You should try to flash the correspondent CM 10.1 boot.img located HERE
As I said i´m new at this
When it all happened I was using the CM 10.1. I flashed and rooted with Hasoon2000 v2.3 toolkit.
From the toolkit I flashed the CWM recovery which was working fine until this very moment..
I used the same toolkit to flash the blade boot img you so kindly linked to but same problem did occur after that.
Panicing as I was then I tried Another rom with it´s recovery and kernel but the problems remained the same. (viperX)
Is there anyway I can start over and get a fresh start so to speak? I thought the RUU would solve it but it didn´t. I relocked the phone Before trying the ruu...
update:
Just tried flashing the openrecovery-twrp-2.4.4.0-enrc2b.img with the "BLADE" boot.img but nothing Changes.
It says ok when flashing..
I know this may sound stupid but make sure when flashing a new boot.img you also have flashed the matching rom. I'd take a deep breath and reflash a whole new set. Use normal commands from a "CMD" box so you can track any problems.
Start here with recovery, http://forum.xda-developers.com/showthread.php?t=1995002
Then flash this rom and kernel http://forum.xda-developers.com/showthread.php?t=2010104
edit - just realized if you are not able to boot into android you will need to sideload your rom via recovery
edit - just realized if you are not able to boot into android you will need to sideload your rom via recovery[/QUOTE]
The problem is that I can´t boot into recovery.. can I do it some other way?
i trust you can get to the bootloader screen? if so, is it from there where you try and flash the recovery? Hmm without recovery you cannot flash any rom.
however if you have not been able to boot into recovery i trust you didnt wipe the system (other than when you relocked and then unlocked the bootloader) if so try just flashing the cm10.1 kernel again to see if you can return to a booting phone again.
edit - what error did you get when trying to flash the ruu?
ratcom said:
i trust you can get to the bootloader screen? if so, is it from there where you try and flash the recovery? Hmm without recovery you cannot flash any rom.
however if you have not been able to boot into recovery i trust you didnt wipe the system (other than when you relocked and then unlocked the bootloader) if so try just flashing the cm10.1 kernel again to see if you can return to a booting phone again.
edit - what error did you get when trying to flash the ruu?
Click to expand...
Click to collapse
I didn´t get any errors at all, it just installs then when it boots it shuts off after the HTC bootscreen. It feels like my main concern must be to get a working recovery again? But how??
darkwing66 said:
I didn´t get any errors at all, it just installs then when it boots it shuts off after the HTC bootscreen. It feels like my main concern must be to get a working recovery again? But how??
Click to expand...
Click to collapse
ok so if you boot into bootloader using the vol down and power I trust you are able to select recovery? if so does it then reboot show 2 htc screens then black screen?
ratcom said:
ok so if you boot into bootloader using the vol down and power I trust you are able to select recovery? if so does it then reboot show 2 htc screens then black screen?
Click to expand...
Click to collapse
Yes I can select recovery and then it shows the "HTC quietly brilliant" two times then goes black, or if it shuts off.
darkwing66 said:
Yes I can select recovery and then it shows the "HTC quietly brilliant" two times then goes black, or if it shuts off.
Click to expand...
Click to collapse
if you are using the correct recovery version (International) then I'm out of ideas Sorry I couldnt help
Make sure you downloaded the good RUU for your CID
Boot your phone in BOOTLOADER (Volume down + Power)
Make sure your phone is responding to adb command line with the following : fastboot devices (Enter)
Relock your BOOTLOADER : fastboot oem lock (Enter)
Rebooting
Boot the phone into FASTBOOT and then connect to the PC
Again make sure your phone is responding to adb command line with the following : fastboot devices (Enter)
If you have a your serial number in return you can run the RUU
Good luck!
Lucky Thirteen said:
Make sure you downloaded the good RUU for your CID
Boot your phone in BOOTLOADER (Volume down + Power)
Make sure your phone is responding to adb command line with the following : fastboot devices (Enter)
Relock your BOOTLOADER : fastboot oem lock (Enter)
Rebooting
Boot the phone into FASTBOOT and then connect to the PC
Again make sure your phone is responding to adb command line with the following : fastboot devices (Enter)
If you have a your serial number in return you can run the RUU
Good luck!
Click to expand...
Click to collapse
Thank you for not giving up on me
Did all the steps you said and everything went well except for the problem still remaining. Would it make any difference if I try to extract the recovery and boot from the RUU as I have seen mentioned somwhere in the forum?
You can give it a shot, but how are you gonna transfer the Rom.zip on your phone then?
Usually it's something like
Run the installer of the RUU with your phone unplugged.
Stop on the automated installer and put it aside on your Desktop
Follow this path in your computer : C:\Users\your_account_name\AppData\Local\Temp\{ABC1234D-56E7-8910-F11G-123AB4C56DE7}\{ABC1234D-56E7-8910-F11G-123AB4C56DE7}\Rom.zip (Your string will be different but the Rom.zip will still be there)
Extract from this Rom.zip : boot_signed.img & recovery_signed.img
Boot to fastboot, flash boot_signed.img and recovery.img .
Boot to recovery and flash the Rom.zip
Lucky Thirteen said:
You can give it a shot, but how are you gonna transfer the Rom.zip on your phone then?
Usually it's something like
Run the installer of the RUU with your phone unplugged.
Stop on the automated installer and put it aside on your Desktop
Follow this path in your computer : C:\Users\your_account_name\AppData\Local\Temp\{ABC1234D-56E7-8910-F11G-123AB4C56DE7}\{ABC1234D-56E7-8910-F11G-123AB4C56DE7}\Rom.zip (Your string will be different but the Rom.zip will still be there)
Extract from this Rom.zip : boot_signed.img & recovery_signed.img
Boot to fastboot, flash boot_signed.img and recovery.img .
Boot to recovery and flash the Rom.zip
Click to expand...
Click to collapse
I figured if I manage to extract those files from the rom.zip then I could flash them with fastboot? But at the moment I´m even struggling with extracting the darn files...
Do you Think it will make any difference doing the flashing this way or just running the RUU.exe (wich in my case doesn´t work)?
darkwing66 said:
I figured if I manage to extract those files from the rom.zip then I could flash them with fastboot? But at the moment I´m even struggling with extracting the darn files...
Do you Think it will make any difference doing the flashing this way or just running the RUU.exe (wich in my case doesn´t work)?
Click to expand...
Click to collapse
Hold on I will upload the International version of both of them for you...
Give me ~5 minutes
Edit (sorry if it took longer) :
Here it is :
ENRC2B_recovery_signed
ENRC2Bbootsigned
Hoping you will be able to do something with those. I'll catch later.
Lucky Thirteen said:
Hold on I will upload the International version of both of them for you...
Give me ~5 minutes
Click to expand...
Click to collapse
The recovery file can´t be dl, it says "This file, folder or group is private or does not exist."
edit:
Found one but still the same black screen and no recovery...
darkwing66 said:
The recovery file can´t be dl, it says "This file, folder or group is private or does not exist."
Click to expand...
Click to collapse
Links fixed, Sorry!
First I just want the conformation that you are doing all this manually via a command window and not throught any sort of flashing tool, right?
Lets try those...
Test 1 :
Put this FILE in your platform-tool folder of SDK and do not rename it.
Plug your phone on your computer USB cable
Open a SDK/ADB command window
Type at the prompt> adb devices (Enter) (Serial conformation)
Type at the prompt> adb reboot-bootloader (Enter)
Rebooting in BOOTLOADER
Unplug your phone while rebooting
Once in FASTBOOT plug in your phone and make sure FASTBOOT USB is highlighted
Type at the prompt>fastboot devices (Enter) (Serial conformation)
Type at the prompt>fastboot erase recovery (Enter)
Type at the prompt>fastboot flash recovery TWRPrecovENRC2B.img (Enter)
Type at the prompt>fastboot erase cache (Enter)
Unplug your USB cable and hit Power once.
Select via your Volume rocker -> Recovery
Again hit Power button again
Results?
Test 2 :
Put this FILE in your platform-tool folder of SDK and do not rename it.
Plug your phone on your computer USB cable
Open a SDK/ADB command window
Type at the prompt> adb devices (Enter) (Serial conformation)
Type at the prompt> adb reboot-bootloader (Enter)
Rebooting in BOOTLOADER
Unplug your phone while rebooting
Once in FASTBOOT plug in your phone and make sure FASTBOOT USB is highlighted
Type at the prompt>fastboot devices (Enter) (Serial conformation)
Type at the prompt>fastboot erase recovery (Enter)
Type at the prompt>fastboot flash recovery ENRC2BstockRecovery.img (Enter)
Type at the prompt>fastboot erase cache (Enter)
Unplug your USB cable and hit Power once.
Select via your Volume rocker -> FACTORY RESET
Hit your Power button once to confirm.
The phone should enter Stock Recovery mode and wipe EVERYTHING including "SD card" but also should fix all corrupted DATA (ROM, Directory, Etc)
Once done reboot your phone by holding volume down +power to enter manually the BOOTLOADER
Plug back your USB cable
Open a SDK/ADB command window
Type at the prompt> fastboot devices (Enter) (Serial conformation)
Make sure FASTBOOT USB is highlighted
Type at the prompt>fastboot flash recovery TWRPrecovENRC2B.img (Enter)
Type at the prompt>fastboot erase cache (Enter)
Unplug your USB cable and hit Power once.
Select via your Volume rocker -> Recovery
Again hit Power button again
Can you access Recovery now?
Lucky Thirteen said:
Links fixed, Sorry!
First I just want the conformation that you are doing all this manually via a command window and not throught any sort of flashing tool, right?
Lets try those...
Test 1 :
Put this FILE in your platform-tool folder of SDK and do not rename it.
Plug your phone on your computer USB cable
Open a SDK/ADB command window
Type at the prompt> adb devices (Enter) (Serial conformation)
Type at the prompt> adb reboot-bootloader (Enter)
Rebooting in BOOTLOADER
Unplug your phone while rebooting
Once in FASTBOOT plug in your phone and make sure FASTBOOT USB is highlighted
Type at the prompt>fastboot devices (Enter) (Serial conformation)
Type at the prompt>fastboot erase recovery (Enter)
Type at the prompt>fastboot flash recovery TWRPrecovENRC2B.img (Enter)
Type at the prompt>fastboot erase cache (Enter)
Unplug your USB cable and hit Power once.
Select via your Volume rocker -> Recovery
Again hit Power button again
Results?
Test 2 :
Put this FILE in your platform-tool folder of SDK and do not rename it.
Plug your phone on your computer USB cable
Open a SDK/ADB command window
Type at the prompt> adb devices (Enter) (Serial conformation)
Type at the prompt> adb reboot-bootloader (Enter)
Rebooting in BOOTLOADER
Unplug your phone while rebooting
Once in FASTBOOT plug in your phone and make sure FASTBOOT USB is highlighted
Type at the prompt>fastboot devices (Enter) (Serial conformation)
Type at the prompt>fastboot erase recovery (Enter)
Type at the prompt>fastboot flash recovery ENRC2BstockRecovery.img (Enter)
Type at the prompt>fastboot erase cache (Enter)
Unplug your USB cable and hit Power once.
Select via your Volume rocker -> FACTORY RESET
Hit your Power button once to confirm.
The phone should enter Stock Recovery mode and wipe EVERYTHING including "SD card" but also should fix all corrupted DATA (ROM, Directory, Etc)
Once done reboot your phone by holding volume down +power to enter manually the BOOTLOADER
Plug back your USB cable
Open a SDK/ADB command window
Type at the prompt> fastboot devices (Enter) (Serial conformation)
Make sure FASTBOOT USB is highlighted
Type at the prompt>fastboot flash recovery TWRPrecovENRC2B.img (Enter)
Type at the prompt>fastboot erase cache (Enter)
Unplug your USB cable and hit Power once.
Select via your Volume rocker -> Recovery
Again hit Power button again
Can you access Recovery now?
Click to expand...
Click to collapse
I have used both toolkit and cmd, another problem is that I cant get "adb devices" to return my device. I have tried in win 8, win 7, and now ubuntu but no serial nr returned. If I try fastboot devices it works fine. Is it important to get the adb to work or could I use fastboot instead? I dont know how I can make it work, maybe its my phone thats the problem? I will try now to flash the file you sent me in your latest post. I very very much appreciate you helping me
edit:
Test 1:
The fastboot erase recovery returns - erasing 'recovery'... FAILED (remote: not allowed)
Fastboot flash.. returns -
C:\sdk\platform-tools>fastboot flash recovery TWRPrecovENRC2B.img
sending 'recovery' (7370 KB)... OKAY
writing 'recovery'... INFOFormat partition SOS done
OKAY
Erase cache - OKAY
After reboot - same problem
Test 2:
The same result as test 1...
Must be something is broken in my ***** phone!?
So I have a Telus version of the HTC One X+ 64GB. I have been pretty familiar with flashing roms on samsungs. Wasn't the case so much with the HTC. So I decided to unlock boot loader, root, and flash a custom recovery. Decided to flash this rom from this thread. http://forum.xda-developers.com/showthread.php?t=2219520 not understanding how the boot.img works well guess what I didn't flash that. Now I'm stuck on the Panandriod 3+ boot logo. The phone from my understanding don't seem to wanna charge. Just gets a slow blinking red notification light. When I was able to get into recovery when the battery had charge I was unable to get the ad card to mount so I could add the boot.img to the phone to get fast boot to flash it. I have all the drivers installed on the PC but unsure if maybe the reason that recovery is unable to mount is because of HTC Sync is installed on the PC as well?
The whole reason for trying to flash a rom on this HTC is because I have the HTC One Developer Edition on the way and I wanted to learn as much about flashing HTC as I could so I wouldn't mess up and brick my HTC One when it came. Nowwwww I'm not so confident.
Two days research I have a little more knowledge but still unable to find a good thread or resource to fix this problem. I was able to get some charge thru to the phone when I selected recovery and it went to a black screen with the notification light pulsing red. It seems like its not fully bricked. I tried to use Cmd in windows to try and communicate and see if he phone would respond to the fast boot commands but to no lunch Cmd cannot find the phone. Do anyone know where I could start? Is there a tool kit that can send me back to stock? It was running 4.1.1 any help in the right direction would be great. Thank you guys.
You HAVE to flash the boot.img! Flash it in fastboot
fastboot flash boot boot.img
Without the new boot.img (which is the kernel) your Rom will not run.
Download the pizza boot.img
sixcarnage said:
You HAVE to flash the boot.img! Flash it in fastboot
fastboot flash boot boot.img
Without the new boot.img (which is the kernel) your Rom will not run.
Download the pizza boot.img
Click to expand...
Click to collapse
Hey thanks for replying
I downloaded the pizza boot.img but the issue I'm facing is charging it seems either very very slow on black screen or maybe it's not charging? But main issue is that PC cannot find the One X+ I will try this command but where do I place the pizza boot.img on windows?
The only thing is getting me is I'm getting the sound from windows when you connect a device when I plug the phone in USB but the cmd so far that I have tried even the All in one toolkit don't seem to see that the phone is connect USB in fast boot or boot loader mode. Think this is due to not enough charge? Plus should I just leave it in custom recovery to charge which is a black screen due to it says not enough charge to flash to charge my device?
sixcarnage said:
You HAVE to flash the boot.img! Flash it in fastboot
fastboot flash boot boot.img
fastboot erase cache
Without the new boot.img (which is the kernel) your Rom will not run.
Download the pizza boot.img
Click to expand...
Click to collapse
Corrected.
Gene1985 said:
Two days research I have a little more knowledge but still unable to find a good thread or resource to fix this problem.
Click to expand...
Click to collapse
I can hardly believe you didn't find anything that help you with this issue on this forum.
First is your SDK/ADB tool install on your computer?
It's not that complicated to flash the boot.img. Take the pizza boot.img and put it in your platform-folder of your SDk tool. Reboot your phone by holding Volume down and pressing Power button. In bootloader plug in your USB cable and at the prompt confirm that your computer is seen by typing this >fastboot devices if you have your serial confirmation then simply proceed with this at the prompt>fastboot flash boot insert_pizza_name_boot.img (enter) again at the prompt>fastboot erase cache (enter) the for rebooting >fastboot reboot (enter)
If you need more infos, you have everything required in my signature to help you.
Do you have the latest TWRP
Lucky Thirteen said:
Corrected.
I can hardly believe you didn't find anything that help you with this issue on this forum.
First is your SDK/ADB tool install on your computer?
It's not that complicated to flash the boot.img. Take the pizza boot.img and put it in your platform-folder of your SDk tool. Reboot your phone by holding Volume down and pressing Power button. In bootloader plug in your USB cable and at the prompt confirm that your computer is seen by typing this >fastboot devices if you have your serial confirmation then simply proceed with this at the prompt>fastboot flash boot insert_pizza_name_boot.img (enter) again at the prompt>fastboot erase cache (enter) the for rebooting >fastboot reboot (enter)
If you need more infos, you have everything required in my signature to help you.
Click to expand...
Click to collapse
Thanks Lucky, I noticed tonight I went thru everything in issues and I noticed that I didn't correctly have SDK set up right on my windows. Hopefully that this is the issue and that when I set it up right that I can fix this problem. This has been far different then Samsung to fix hahaha thanks again and kinda my bad for posting the question. But hopefully that works.
sixcarnage said:
Do you have the latest TWRP
Click to expand...
Click to collapse
No I don't have TWRP I have the recover that came in the noob tool kit. The none touch screen one lol. But I understand a fair bit on what I should have done. I'm gonna try and follow luckies link for the SDK set up and see if I can send the zip file to the phone then flash it in recovery. Just I hope the thing can charge. I had it on the charger for 4 hours today and it still said that there was not enough charge to flash I tried charging it in the boot loop and in recovery.
So I guess the issue is worse. The phone won't charge at all the red notification light blinks red but it don't seem to be charging at all I have looked for fixes and it says flash latest compatible recovery but it won't even discover the phone connected to windows with proper HTC drivers installed
Is your phone capable of booting in bootloader mode?
Lucky Thirteen said:
Is your phone capable of booting in bootloader mode?
Click to expand...
Click to collapse
Yea I am able Lucky. But what I tried today was to get RUU to recognize the phone to do that but no go. So tomorrow I'm gonna do a fresh reinstall on a new laptop of windows and install drivers again and all that. But as for boot loader mode it boots. I click recovery and I get a black screen. I can fast boot USB but I'm not quite sure about USB debugging is still turned on. If it where I'm sure I wouldn't have an issue with the PC not seeing the phone connected.
OK try this in bootloader mode with the USB plug
fasboot devices
Do you have a confirmation serial number?
Will do Lucky. Thanks for your time and patience. I will try this over the night. I really like to try and get this fixed and to understand how the htc works with installing roms and tweaks. I really don't wanna mess up my Develeper Edition of the HTC One that's on the way.
If you have your serial confirmation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Phone should charge in recovery even if the red light doesn't lit.
Just tried this on my phone with less than 10% and it worked flawlessly, after ~10 minutes my phone was at 13%+
Otherwise you will have to create a batch file and run it while your phone is in FASTBOOT USB mode :
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
That should allow your phone to charge to the minimal required to flash or to re-unlock your bootloader.
Lucky Thirteen said:
If you have your serial confirmation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Phone should charge in recovery even if the red light doesn't lit.
Just tried this on my phone with less than 10% and it worked flawlessly, after ~10 minutes my phone was at 13%+
Otherwise you will have to create a batch file and run it while your phone is in FASTBOOT USB mode :
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
That should allow your phone to charge to the minimal required to flash or to re-unlock your bootloader.
Click to expand...
Click to collapse
Thanks Lucky. I will try this first thing in the A.M I hope that works.
Lucky Thirteen said:
If you have your serial confirmation.
Download this recovery HERE
Move this file in your platform-tools folder
Press and hold the Shift key and right click on a empty space of that folder and select Open Command Window Here
In the command window with your phone in FASTBOOT USB mode
Type>fastboot flash recovery TWRP2500.img
(Success)
Type again>fastboot erase cache
(Success)
Unplug your USB cable
Hit one time Power
Select Recovery (Volume down)
Hit Power to Reboot in Recovery
Phone should charge in recovery even if the red light doesn't lit.
Just tried this on my phone with less than 10% and it worked flawlessly, after ~10 minutes my phone was at 13%+
Otherwise you will have to create a batch file and run it while your phone is in FASTBOOT USB mode :
Code:
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
That should allow your phone to charge to the minimal required to flash or to re-unlock your bootloader.
Click to expand...
Click to collapse
worked like a charm Lucky. thanks i followed all the steps now im up and running. thanks again.
Great! This is a good news!
Please take the time to edit your OP and change your title to this : [SOLVED] BAD FLASH!!!! NOOB. Possible Brick HELP THANK YOU.
Happy flashing now!
I just waited 360 hours and unlocked a new Mi8 dipper as I have done with 5 Xiaomi phones previously. Everything looks normal. MiUI v10 says it is unlocked. With USB debugging activated the device code shows up with the 'adb devices' command. However when it comes to actually modifying the bootloader in Fastboot mode things look very locked in place. In the terminal console 'abd devices' command shows no devices. Similarly when trying to load TWRP with 'fastboot flash recovery TWRP. img' command it searches to find no device and ends with a fault. I have tried with 3 different USB-C cables on three different PC's. Two with Windows 10 with ADB tools and another on current ArchLinux with 4.20 kernel and ADB tools.
Incidentally, my wife has an untouched and therefore unlocked Pocophone F1. It does the same thing as above.
Has anyone heard of such a tbing? Is it possible that Xiaomi thinks this phone has been unlocked when in fact the bootloader is still locked?
As far as a fix goes,the unlock tool says its locked and won't try again to unlock it. This would be utterly painful were it not for Lawnchair launcher coming to the user experience rescue.
It is your computer, try to reinstall adn, driver, etc,..
If bootloader is locked, you still can type fastboot devices, but cannot flash anything with the error that you dont have permission to edit partiton.
khanhdx said:
It is your computer, try to reinstall adn, driver, etc,..
If bootloader is locked, you still can type fastboot devices, but cannot flash anything with the error that you dont have permission to edit partiton.
Click to expand...
Click to collapse
Thanks. Will try again in different variations. A few questions:
1. Is it advisable or not advisable to use a USBv3 or 3.1 port instead of USBv2 ?
2. I have tried a few different Windows 10 drivers from various sources. Can you recommend any specific driver for Xiaomi?
Thanks for helping. I will be very disappointed if I can't mod this phone.
p-we said:
Thanks. Will try again in different variations. A few questions:
1. Is it advisable or not advisable to use a USBv3 or 3.1 port instead of USBv2 ?
2. I have tried a few different Windows 10 drivers from various sources. Can you recommend any specific driver for Xiaomi?
Thanks for helping. I will be very disappointed if I can't mod this phone.
Click to expand...
Click to collapse
I think no different between USB2 and USB3 in this case.
Try uninstall all driver and app related to xiaomi.
Then Disable Signed Driver Enforcement.
Then install latest Miflash: http://en.miui.com/a-234.html (file at step 1)
Then open Mi Unlock folder (the one u found MiUnlock.exe), hold Shift + right click, select open PowerShell here.
Type cmd, enter.
Reboot phone to fastboot, connect to pc.
Type fastboot devices, enter.
khanhdx said:
I think no different between USB2 and USB3 in this case.
Try uninstall all driver and app related to xiaomi.
Then Disable Signed Driver Enforcement.
Then install latest Miflash: http://en.miui.com/a-234.html (file at step 1)
Then open Mi Unlock folder (the one u found MiUnlock.exe), hold Shift + right click, select open PowerShell here.
Type cmd, enter.
Reboot phone to fastboot, connect to pc.
Type fastboot devices, enter.
Click to expand...
Click to collapse
I think I'm close. I installed MIFlash and installed drivers. I now see the device ID in Windows PowerShell in fastboot mode which I did not have before:
C:\Users\wdirk\Downloads\miflash_unlock-en-3.3.827.31\miflash_unlock_en_3.3.827.31>fastboot devices
46265bfe fastboot
But when I enter 'fastboot flash recovery twrp.img' (the twrp.img file is in the same directory), the phone immediately goes to another mode (no fastboot logo with very small text on top left of screen) and nothing happens. So fastboot sees the device but will not write twrp recovery. Ideas?
So I tried Minimal ADB and Fastboot again. Positive that the device shows up:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
46265bfe fastboot
But goes into blank screen with very small text on top left with more inforation this time:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (41796 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
p-we said:
I think I'm close. I installed MIFlash and installed drivers. I now see the device ID in Windows PowerShell in fastboot mode which I did not have before:
C:\Users\wdirk\Downloads\miflash_unlock-en-3.3.827.31\miflash_unlock_en_3.3.827.31>fastboot devices
46265bfe fastboot
But when I enter 'fastboot flash recovery twrp.img' (the twrp.img file is in the same directory), the phone immediately goes to another mode (no fastboot logo with very small text on top left of screen) and nothing happens. So fastboot sees the device but will not write twrp recovery. Ideas?
So I tried Minimal ADB and Fastboot again. Positive that the device shows up:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
46265bfe fastboot
But goes into blank screen with very small text on top left with more inforation this time:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (41796 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
Click to expand...
Click to collapse
I never face any case like this. So maybe i can help you.
Try install different version of TWRP maybe can help..
ShafiX94 said:
Try install different version of TWRP maybe can help..
Click to expand...
Click to collapse
Very strange but I followed your steps on another PC in exactly the same way and now it has flashed TWRP successfully. It did require using blue USB3 port
Thank-you! :good:
Glade to hear you solved it.
For the record: I had the exact same problem as yours. If I recall correctly, the only thing I had to do was to rename the recovery file to: recovery.img then wait a minute or so. Which is strange, but worked.
First tried to boot Pitchblack recovery when it succeeded then tried it with TWRP (recovery.img).
If anyone finds themselves here. Go to https://forum.xda-developers.com/mi-8/how-to/guide-to-issues-flashing-unlocked-mi8-t3911389
p-we said:
If anyone finds themselves here. Go to https://forum.xda-developers.com/mi-8/how-to/guide-to-issues-flashing-unlocked-mi8-t3911389
Click to expand...
Click to collapse
I am glad that you sorted your issue.
But I can assure you that the issue was strictly caused by your PC. It truly should not matter which USB port you use. We have 3 Mi8 in our house and I have unlocked 2 of them using an older laptop with a broken usb 3.0 port.
For the benefit of others who may experience this issue.
Always. remove peripheral devices from the PC such as an external hard drive, when perform tasks such as unlocking the bootloader or unbricking a phone.
Windows should be up to date and I can tell you that professionally, we absolutely require that people temporarily disable windows defender and antivirus when attempting to resolve these kinds of issues, as you are indeed affecting the bootloader of the device.
Windows antivirus will often remove files that it miscategorises as a virus. In example, if you attempt to download and install the All In One Tool, windows defender will neuter the software 90% of the time.