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
Related
This is in reguards to putting on a recovery.
I but the phone in fastboot then go into SDK tools and click on Fastboot and it opens then closes in under one second. I have the recovery image fill in the same folder as well.
This is driving me crazy and I can't figure it out!
Thanks for the info in advance!
Happy New Years!
Sent from my ADR6425LVW using XDA App
Any ideas? This is driving me crazy.....
Thanks!
Sent from my ADR6425LVW using XDA App
Fastboot needs command line parameters. You can't just click it open. Run cmd then CD to your sdk directory and run fastboot flash recovery (image_file)
Is there anyway this can be explained more. Still new to it all and learning!
I really appreciate all the input!
Sent from my ADR6425LVW using XDA App
Sorry for the ignorance as I'm still learning this whole HTC thing. I came from the Droid X. Ugh, what a change!
Sent from my ADR6425LVW using XDA App
Theres a good walkthrough in the development section. Here's the short version.
First off its very similar to unlocking(same tools needed)
1) copy your recovery image to wherever you have fastboot on your PC(for this example say c:\android
2) reboot your phone into hboot(power down, then power up holding power + volume down)
3) choose fastboot on the phone
4) plug the phone into your PC
5) open a command prompt on your PC
6) change directory to c:\android(or where you have fastboot)
7) run "fastboot flash recovery recovery.img " (where recovery.img = your recovery file
8) reboot
Done
Sent with Resounding success via tapatalk
Verizon Resound Unleashed - rooted and Senseless
MrSmith317 said:
Theres a good walkthrough in the development section. Here's the short version.
First off its very similar to unlocking(same tools needed)
1) copy your recovery image to wherever you have fastboot on your PC(for this example say c:\android
2) reboot your phone into hboot(power down, then power up holding power + volume down)
3) choose fastboot on the phone
4) plug the phone into your PC
5) open a command prompt on your PC
6) change directory to c:\android(or where you have fastboot)
7) run "fastboot flash recovery recovery.img " (where recovery.img = your recovery file
8) reboot
Done
Sent with Resounding success via tapatalk
Verizon Resound Unleashed - rooted and Senseless
Click to expand...
Click to collapse
I'm going to thank you for this, too. I don't know if it's because I know how to do this now after doing it so much over the past week or so, but that was the easiest explanation I've seen of flashing a recovery. Nice job
This is a great explanation but this is what it says:
C:\Program Files\Android\android-sdk\platform-tools>fastboot flash recovery reco
very.img
error: cannot load 'recovery.img'
Now when you say put it in the same directory does that mean the same folder?
Thanks!
MrSmith317 said:
Theres a good walkthrough in the development section. Here's the short version.
First off its very similar to unlocking(same tools needed)
1) copy your recovery image to wherever you have fastboot on your PC(for this example say c:\android
2) reboot your phone into hboot(power down, then power up holding power + volume down)
3) choose fastboot on the phone
4) plug the phone into your PC
5) open a command prompt on your PC
6) change directory to c:\android(or where you have fastboot)
7) run "fastboot flash recovery recovery.img " (where recovery.img = your recovery file
8) reboot
Done
Sent with Resounding success via tapatalk
Verizon Resound Unleashed - rooted and Senseless
Click to expand...
Click to collapse
I finally got it.
Thanks for all your input!
MrSmith317 said:
Theres a good walkthrough in the development section. Here's the short version.
First off its very similar to unlocking(same tools needed)
1) copy your recovery image to wherever you have fastboot on your PC(for this example say c:\android
2) reboot your phone into hboot(power down, then power up holding power + volume down)
3) choose fastboot on the phone
4) plug the phone into your PC
5) open a command prompt on your PC
6) change directory to c:\android(or where you have fastboot)
7) run "fastboot flash recovery recovery.img " (where recovery.img = your recovery file
8) reboot
Done
Sent with Resounding success via tapatalk
Verizon Resound Unleashed - rooted and Senseless
Click to expand...
Click to collapse
Thanks I just needed this too!
I fixed it with this https://forum.xda-developers.com/attachments/howto_driver-zip.2480396/
I have 4.5.141 unlocked, rooted and I have GooManager installed, I try to have it flash the TWRP version 2.1.1 recovery for me automatically so I can try to download and flash a custom ROM and it downloads and it flashes the custom recovery and the phone reboots and I get an error that reads "Failed to Boot 2 Starting RSD Mode" and when I pull the battery, the phone reboots and the "Failed to boot 2" message does not show up. Can anyone help me in trying to successfully flash a custom recovery onto my Atrix 4G?
ksweeley said:
I have 4.5.141 unlocked, rooted and I have GooManager installed, I try to have it flash the TWRP version 2.1.1 recovery for me automatically so I can try to download and flash a custom ROM and it downloads and it flashes the custom recovery and the phone reboots and I get an error that reads "Failed to Boot 2 Starting RSD Mode" and when I pull the battery, the phone reboots and the "Failed to boot 2" message does not show up. Can anyone help me in trying to successfully flash a custom recovery onto my Atrix 4G?
Click to expand...
Click to collapse
Download TWRP recovery from this thread
Download moto-fastboot-win32.zip from this thread
Unzip them both to the same folder on your computer (eg.: c:\fastboot).
Make sure all files are in the same folder: moto-fastboot, the ADB DLL files and recovery.img
Open a command prompt window pointing to that folder (tip: hold shift on the keyboard, right click on the folder and select "open command window here")
Connect yout atrix to your pc via USB and boot your atrix into fastboot mode (when the phone is off, keep the VOL - button pressed and press the power button. When Fastboot appears, press VOL +)
Now issue type these commands into the command prompt:
moto-fastboot erase recovery
moto-fastboot flash recovery recovery.img
after it's done, type
moto-fastboot reboot
After that you should be able to boot into TWRP recovery. Cheers!
vladeco said:
Download TWRP recovery from this thread
Download moto-fastboot-win32.zip from this thread
Unzip them both to the same folder on your computer (eg.: c:\fastboot).
Make sure all files are in the same folder: moto-fastboot, the ADB DLL files and recovery.img
Open a command prompt window pointing to that folder (tip: hold shift on the keyboard, right click on the folder and select "open command window here")
Connect yout atrix to your pc via USB and boot your atrix into fastboot mode (when the phone is off, keep the VOL - button pressed and press the power button. When Fastboot appears, press VOL +)
Now issue type these commands into the command prompt:
moto-fastboot erase recovery
moto-fastboot flash recovery recovery.img
after it's done, type
moto-fastboot reboot
After that you should be able to boot into TWRP recovery. Cheers!
Click to expand...
Click to collapse
I'm having a problem, I typed in moto-fastboot erase recovery and it says
"erasing 'recovery' ... FAILED <remote: <00180001>>"
and on the phone itself it reads in red text:
"Failed to process command erase:recovery error(0x180001)"
Is there a way to fix this error?
I fixed this, re-flashed the pudding.zip file I found, and I got the recovery to flash.
ksweeley said:
I'm having a problem, I typed in moto-fastboot erase recovery and it says
"erasing 'recovery' ... FAILED <remote: <00180001>>"
and on the phone itself it reads in red text:
"Failed to process command erase:recovery error(0x180001)"
Is there a way to fix this error?
I fixed this, re-flashed the pudding.zip file I found, and I got the recovery to flash.
Click to expand...
Click to collapse
Hi, Could you please share the steps for the resolution? I have read about pudding, also i tried but can not achive. Thanks
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!?
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
Hi guys. I have an HTC OX+... I tried to flash a rom but something went wrong and I erased everything... Now I managed to switch my phone on in fastboot and in recovery mode. How can I sort the problem out?
My recovery is TWRP 2.7.1.0
lorenk93 said:
Hi guys. I have an HTC OX+... I tried to flash a rom but something went wrong and I erased everything... Now I managed to switch my phone on in fastboot and in recovery mode. How can I sort the problem out?
My recovery is TWRP 2.7.1.0
Click to expand...
Click to collapse
I assume your PC has all drivers installed so go to command prompt, there go to your folder where adb and fastboot are.
It should be like this, cd C:\folder_where_adb_is
Now go to recovery mode on the phone and search for Sideload, it can be in install zip from your recovery, click it when you found it.
Go to your Pc and put the ROM to the folder where adb and fastboot are.
Then make sure your phone says it's in adb sideload mode,
On the PC write
Code:
adb sideload file_name.zip
And wait until it's finished
Let's say that's done, but you can't boot, it keeps restarting forever.
In this case, go to your rom.zip open it on the PC and there will be a file called boot.img
Extract boot.img to your folder where fastboot and adb are.
Now on your phone, force it to close by holding power, open fastboot
Again open cmd on the PC and point it to your folder where fastboot and adb are.
Then write
Code:
fastboot flash boot boot.img
oziboy said:
I assume your PC has all drivers installed so go to command prompt, there go to your folder where adb and fastboot are.
It should be like this, cd C:\folder_where_adb_is
Now go to recovery mode on the phone and search for Sideload, it can be in install zip from your recovery, click it when you found it.
Go to your Pc and put the ROM to the folder where adb and fastboot are.
Then make sure your phone says it's in adb sideload mode,
On the PC write
Code:
adb sideload file_name.zip
And wait until it's finished
Let's say that's done, but you can't boot, it keeps restarting forever.
In this case, go to your rom.zip open it on the PC and there will be a file called boot.img
Extract boot.img to your folder where fastboot and adb are.
Now on your phone, force it to close by holding power, open fastboot
Again open cmd on the PC and point it to your folder where fastboot and adb are.
Then write
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
When I write adb sideload file_name.zip, it
returns "error: closed". why?
lorenk93 said:
When I write adb sideload file_name.zip, it
returns "error: closed". why?
Click to expand...
Click to collapse
file_name.zip is your ROM name, for example if you have arhd it can be ARHD_V8.zip or something, just see what name the zip file of your rom has
if this is not the case try
ADB usb before trying adb sideload
oziboy said:
file_name.zip is your ROM name, for example if you have arhd it can be ARHD_V8.zip or something, just see what name the zip file of your rom has
if this is not the case try
ADB usb before trying adb sideload
Click to expand...
Click to collapse
so... I have to write "ADB usb file_name.zip". tath's right?
lorenk93 said:
so... I have to write "ADB usb file_name.zip". tath's right?
Click to expand...
Click to collapse
No, you have to write only "adb usb".
Then try "adb sideload yourrom.zip" again.
if that didn't work, then reboot into recovery and go to command prompt, and write
Code:
adb kill-server
adb usb
adb push yourromname.zip /sdcard
that should work if nothing else works. im having kinda the same issue right now :/
oziboy said:
No, you have to write only "adb usb".
Then try "adb sideload yourrom.zip" again.
if that didn't work, then reboot into recovery and go to command prompt, and write
Code:
adb kill-server
adb usb
adb push yourromname.zip /sdcard
that should work if nothing else works. im having kinda the same issue right now :/
Click to expand...
Click to collapse
I don't know why, but when I write adb usb it returns "error: device not found"
lorenk93 said:
I don't know why, but when I write adb usb it returns "error: device not found"
Click to expand...
Click to collapse
I just fixed this on my phone, now to to control panel - uninstall a program and delete htc sync manager (only sync manager, not the drivers)
Then try again, if nothing, go to here and install that.
If installed, go to fastboot mode, plug in your phone and in that program, when you open it, it says install drivers, flash rom and such...
Now on the right there is flash TWRP recovery, flash that, if your device is an LTE variant (ATT, Telus) install the ones for that and international for international version, make sure you got the correct one.
Then go to recovery, on the lower-right side there is an "advanced" button, hit that and there should be adb sideload somewhere, click that and swipe left to right to enable.
Go to your PC and repeat the sideloading steps as I said before.
oziboy said:
I just fixed this on my phone, now to to control panel - uninstall a program and delete htc sync manager (only sync manager, not the drivers)
Then try again, if nothing, go to here and install that.
If installed, go to fastboot mode, plug in your phone and in that program, when you open it, it says install drivers, flash rom and such...
Now on the right there is flash TWRP recovery, flash that, if your device is an LTE variant (ATT, Telus) install the ones for that and international for international version, make sure you got the correct one.
Then go to recovery, on the lower-right side there is an "advanced" button, hit that and there should be adb sideload somewhere, click that and swipe left to right to enable.
Go to your PC and repeat the sideloading steps as I said before.
Click to expand...
Click to collapse
I did it... Thanks to you... So thank you so much...
lorenk93 said:
I did it... Thanks to you... So thank you so much...
Click to expand...
Click to collapse
No problem, I had almost the same problem and just told what I did xD