I have an AT&T HOX+, and I recently unsuccessfully tried to root it.
After failing, I relocked it without enabling USB Debugging. Now I can't connect it to my PC and it's just stuck in fastboot.
I also can't boot into recovery. The only options are hboot, reboot, reboot bootloader, and power down.
Is there anyway to fix it without going into an at&t store?
thanks in advance
cortem said:
I have an AT&T HOX+, and I recently unsuccessfully tried to root it.
After failing, I relocked it without enabling USB Debugging. Now I can't connect it to my PC and it's just stuck in fastboot.
I also can't boot into recovery. The only options are hboot, reboot, reboot bootloader, and power down.
Is there anyway to fix it without going into an at&t store?
thanks in advance
Click to expand...
Click to collapse
There are Tutorials in the HTC One X+ General forum, where everything you need to know is written down, so i won't try to explain it all in here...
These should not be that hard to find and after reading you should know how to get your device working again.
cortem said:
I have an AT&T HOX+, and I recently unsuccessfully tried to root it.
After failing, I relocked it without enabling USB Debugging. Now I can't connect it to my PC and it's just stuck in fastboot.
I also can't boot into recovery. The only options are hboot, reboot, reboot bootloader, and power down.
Is there anyway to fix it without going into an at&t store?
thanks in advance
Click to expand...
Click to collapse
Unlock the boot loader again.
Flash TWRP
use adb sideload to copy ROM
use TWRP to flash the ROM.
Addicted2xda said:
Unlock the boot loader again.
Flash TWRP
use adb sideload to copy ROM
use TWRP to flash the ROM.
Click to expand...
Click to collapse
how do I unlock the boot loader without usb debugging?
everytime I try, the command prompt says either "device not found" or "could not connect"
cortem said:
how do I unlock the boot loader without usb debugging?
everytime I try, the command prompt says either "device not found" or "could not connect"
Click to expand...
Click to collapse
Try booting in fastboot mode and see - I guess it will connect,
Although I am not an expert, but I think USB Debugging comes into play after ROM is booted...
Also, as per your signature, your kernel is:
Kernel: hXORe v3.4
Click to expand...
Click to collapse
Are you sure you have the correct kernel - just for a check install the kernel that came with the ROM. AFAIK the ATT kernel is experimental...
Addicted2xda said:
Try booting in fastboot mode and see - I guess it will connect,
Although I am not an expert, but I think USB Debugging comes into play after ROM is booted...
Also, as per your signature, your kernel is:
Are you sure you have the correct kernel - just for a check install the kernel that came with the ROM. AFAIK the ATT kernel is experimental...
Click to expand...
Click to collapse
sorry for asking, but how do I boot from here?
whatever I do just brings me back to the fastboot usb screen with the message "relocked security warning" at the top.
I can't get to recovery mode or unlock it
EDIT: i'm on hboot 1.40 so apparently there is no ruu available at the moment
cortem said:
sorry for asking, but how do I boot from here?
whatever I do just brings me back to the fastboot usb screen with the message "relocked security warning" at the top.
I can't get to recovery mode or unlock it
EDIT: i'm on hboot 1.40 so apparently there is no ruu available at the moment
Click to expand...
Click to collapse
No as of now there is no RUU available at the moment.
If you just check a thread I have started I had the same problem. Here is what I did:
While on Fastboot - used hasoon's tool kit to re unlock the boot loader. It failed a few times but then it ultimately succeeded. You need to be on either hboot or fastboot to unlock the bootloader not in recovery....
BTW have you actually tried the toolkit?
Hope you have the unlock_code.bin in root of the toolkit...
Addicted2xda said:
No as of now there is no RUU available at the moment.
If you just check a thread I have started I had the same problem. Here is what I did:
While on Fastboot - used hasoon's tool kit to re unlock the boot loader. It failed a few times but then it ultimately succeeded. You need to be on either hboot or fastboot to unlock the bootloader not in recovery....
BTW have you actually tried the toolkit?
Hope you have the unlock_code.bin in root of the toolkit...
Click to expand...
Click to collapse
I've been using the toolkit, so I did as you recommended.
However, the command prompt says "Error: cannot load C:/phone" whenever I try to unlock the bootloader
cortem said:
I've been using the toolkit, so I did as you recommended.
However, the command prompt says "Error: cannot load C:/phone" whenever I try to unlock the bootloader
Click to expand...
Click to collapse
I am assuming you have installed the hTC drivers. Using hTC Sync or other method?
Is it showing in device manager?
What is your OS?
If it is showing as unknown device then you may try Koush's universal ADB driver.
Another thing does "fastboot devices" shows you anything?
It is really weird, because I did these steps and it just worked for me....
Addicted2xda said:
I am assuming you have installed the hTC drivers. Using hTC Sync or other method?
Is it showing in device manager?
What is your OS?
If it is showing as unknown device then you may try Koush's universal ADB driver.
Another thing does "fastboot devices" shows you anything?
It is really weird, because I did these steps and it just worked for me....
Click to expand...
Click to collapse
thanks for your concern.
I'll look into all of those and get back to you tomorrow about my results
Don't use toolkits they cause more issues than they solve.... Connect your device to your PC, open a command prompt, navigate to your fastboot folder and type in "fastboot devices" If it gives you back your devices S/N, your good to go. If not reinstall HTC Sync manager.... I don't see why you can't enable usb debugging on a bootloader locked device though....They have nothing to do with each other afaik....
Sent from my HTC One X+ using Tapatalk 4 Beta
AndroHero said:
Don't use toolkits they cause more issues than they solve.... Connect your device to your PC, open a command prompt, navigate to your fastboot folder and type in "fastboot devices" If it gives you back your devices S/N, your good to go. If not reinstall HTC Sync manager.... I don't see why you can't enable usb debugging on a bootloader locked device though....They have nothing to do with each other afaik....
Sent from my HTC One X+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
thank you so much
it worked!
edit: nevermind I'm retarded
Related
Hello, I rooted and used this method to root and install recovery:
http://forum.xda-developers.com/showthread.php?t=1690919
Then I installed Mean ROM and everything went smoothly.
I tried installing a kernel:
First, I tried this:
http://forum.xda-developers.com/showthread.php?t=1814037
and then I tried this:
http://forum.xda-developers.com/showthread.php?t=1800399
Both of them say they installed, but when I open Antutu CPU Master, I cannot overclock, I even went on the settings and about phone and it looked like the kernel was still the same.
Is there a specific method in which to flash the kernel?
Can someone help?
Thanks
I believe that you have to be S-OFF (preferred) or HTC Dev Unlocked to flash kernels successfully.
Also, if you took the latest OTA, you're now on a version of hboot, which doesn't allow flashing kernels.
Sent from my r00ted, unlocked, 100% tricked-out LTEVO
If you are on the new H-boot, you cannot flash kernels from recovery. Simple as that.
You can fastboot flash them. Theres a thread about it in the general section. I'd suggest reading up on it
Rxpert said:
If you are on the new H-boot, you cannot flash kernels from recovery. Simple as that.
You can fastboot flash them. Theres a thread about it in the general section. I'd suggest reading up on it
Click to expand...
Click to collapse
Can someone please provide me the link or a walkthrough on what to do?
I dont have anything installed on my computer at all and am completely new to this.
If your using TWRP 2.2.1 then maybe you can use the HTC Dumlock to flash kernels? I'm S-off so I don't have to use it.
Try this:
http://forum.xda-developers.com/showthread.php?t=1693205
Sent from my r00ted, unlocked, 100% tricked-out LTEVO
Here are the instructions for flashing a kernel on the latest hboot:
http://forum.xda-developers.com/showthread.php?t=1794867
You basically just need to flash the entire boot image instead of just the kernel. I know there is an an Enoch boot image available in the official thread, not sure about Evilz.
To do a fastboot flash you'll need the sdk installed. There is a good how to video here if you've never done it before:
http://www.youtube.com/watch?v=oaNM-lt_aHw
Sent from my EVO LTE
Another good source of info:
http://wiki.cyanogenmod.com/wiki/Fastboot
Sent from my r00ted, unlocked, 100% tricked-out LTEVO
Might be able to flash using Flash Imgae GUI.
Edit: Nvm. premo15's first link talks about using it.
I tried Flash Image GUI, but it messed up my rom, now I keep getting a Reboot Loop on the HTC Screen with the Developer Warning.
I then tried to clear all data and install the Mean Rom again, and when I do, it says that the ROM is installed in the Recovery, but When it boots, it goes back to the Reboot Loop.
Can someone Please Help me!
gokuman56 said:
I tried Flash Image GUI, but it messed up my rom, now I keep getting a Reboot Loop on the HTC Screen with the Developer Warning.
I then tried to clear all data and install the Mean Rom again, and when I do, it says that the ROM is installed in the Recovery, but When it boots, it goes back to the Reboot Loop.
Can someone Please Help me!
Click to expand...
Click to collapse
You have to extract the boot.img from mean rom and use fastboot to install it. premo15's first link also talked about using fastboot to install. If you want to install a custom kernel then just take the boot.img out of the fashable zip and use fastboot.
Okay,
I got ADB to Work, but whenever I do an ADB Command, such as adb reboot bootloader. It says Device Not Found, I installed the appropriate drivers and it also makes a device connected sound when I plug in the phone. When I open device manager, it shows all drivers installed.
Can someone help me with this issue, lol, I've been having so many issues with modding this phone....
gokuman56 said:
Okay,
I got ADB to Work, but whenever I do an ADB Command, such as adb reboot bootloader. It says Device Not Found, I installed the appropriate drivers and it also makes a device connected sound when I plug in the phone. When I open device manager, it shows all drivers installed.
Can someone help me with this issue, lol, I've been having so many issues with modding this phone....
Click to expand...
Click to collapse
You can type in adb devices to show connected devices. Make sure Android debugging is on in Settings -> Developer Options.
My Phone will not Boot at all. I cannot Enable ADB Debugging, I can go to the Bootloader Menu or the Recovery Menu.
I pressed fastboot and enabled fastboot-usb, and it made a connecting noise, but with adb, it will say phone not found
gokuman56 said:
My Phone will not Boot at all. I cannot Enable ADB Debugging, I can go to the Bootloader Menu or the Recovery Menu.
I pressed fastboot and enabled fastboot-usb, and it made a connecting noise, but with adb, it will say phone not found
Click to expand...
Click to collapse
Try going into recovery from the bootloader and then try the "adb devices" command. I've noticed that I can't issue adb commands while in fastboot also...not sure why. If you can get it to display your device while in recovery, then you know your communication is good. Go back into fastboot and you should be able to do the "fastboot flash boot" command, but rebooting with the adb command will not work for some reason. After you flash the boot image, there should be an option to reboot on your phone that you can select with the volume keys.
Sent from my EVO LTE
Thanks! Got it!
when you flash a boot img, what folder does it go in? i have the same problem but i have a mac.
Trying to re-lock my Rezound using fastboot. When I dbl click fastboot on PC, a black cmd window briefly flashes then disappears. help?
fastboot is a command line app. Open a command window and type "fastboot oem lock"
that's what i tried first, then got a "waiting for device" message. I figured i didn't have my phone set right? here was my process...
1. rebooted phone to hboot
2. connected to computer
3. opened command window
4. cd to the correct directory
5. typed the "fastboot oem lock" command
6. received "waiting for device" message
???
novakrj said:
that's what i tried first, then got a "waiting for device" message. I figured i didn't have my phone set right? here was my process...
1. rebooted phone to hboot
2. connected to computer
3. opened command window
4. cd to the correct directory
5. typed the "fastboot oem lock" command
6. received "waiting for device" message
???
Click to expand...
Click to collapse
Make sure you go into fastboot once you're in the HBoot menu or it won't be able to communicate with the device
Make sure you have HTC Sync or some other Rezound-compatible drivers installed. It needs that for fastboot and adb to communicate with your phone.
dplane said:
Make sure you go into fastboot once you're in the HBoot menu or it won't be able to communicate with the device
Click to expand...
Click to collapse
You have to be I fast boot, hboot
sent from my s-on reZound rockin viperRez Rom on latest ICS firmware
Same thing happened to me. Make sure when you plug in the usb cable, the phone connects as a disk drive, not charge only.
Are you trying to re lock or go S-on? I thought that flashing the command fastboot OEM lock would put S-on rather than relock.
Sent from my ADR6425LVW using Tapatalk 2
ended up i needed both bits of advice.
I hadn't reinstalled htc sync files since a pc reformat a month ago, and i needed to enter fastboot once in hboot.
thanks guys
Mr. Boom said:
Are you trying to re lock or go S-on? I thought that flashing the command fastboot OEM lock would put S-on rather than relock.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
no.
fastboot oem lock is changing hboot to relocked
s-on command is something like fastboot write secureflag3 or something- look it up don't use what i just posted. if you do go s-on make sure you just ran a RUU
Mr. Boom said:
Are you trying to re lock or go S-on? I thought that flashing the command fastboot OEM lock would put S-on rather than relock.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
"Fastboot OEM lock" is to lock the bootloader.
"Fastboot OEM writesecureflag3" is to go back to s-on
Sent from my Galaxy Nexus
1. Reboot to fastboot.
This can be done in 3 ways:
A. from the power menu (assuming the rom has it
B. Shut down completely. Battery pull to make sure. Then hold press amd hold Vol Down, then press and hold Power and keep holding down both.
C. Use the command:
adb reboot bootloader
2. Use fastboot to relock bootloader.
Sent from my Rezound
since last we spoke...
was able to relock
flashed the ruu to get back to stock
updated OTA to ICS
unlocked again
flashed aman ra in fastboot
rebooted
the plot thickens...
when i reboot to recovery, it reboots to android stock, not aman ra, hence, no root?
thoughts?
novakrj said:
since last we spoke...
was able to relock
flashed the ruu to get back to stock
updated OTA to ICS
unlocked again
flashed aman ra in fastboot
rebooted
the plot thickens...
when i reboot to recovery, it reboots to android stock, not aman ra, hence, no root?
thoughts?
Click to expand...
Click to collapse
just try flashing Amon Ra again
should i wipe anything first?
novakrj said:
should i wipe anything first?
Click to expand...
Click to collapse
No, just fastboot flash.
Sent from my Rezound
still no go on second flash attempt. still showing android system recovery, not aman ra. tried to install su superuser in the developer menu in android system recovery to achieve root but didn't take.
thanks if anybody has any ideas. I'll just keep searching threads...i usually miss something pretty obvious.
edit: just in case this helps...
when i boot into recovery the top of the screen reads "Android system recovery"
at the bottom of the screen it says:
RA Revamped
Build: RA VIGOR-v3.15-getitnowmarketing
novakrj said:
still no go on second flash attempt. still showing android system recovery, not aman ra. tried to install su superuser in the developer menu in android system recovery to achieve root but didn't take.
thanks if anybody has any ideas. I'll just keep searching threads...i usually miss something pretty obvious.
edit: just in case this helps...
when i boot into recovery the top of the screen reads "Android system recovery"
at the bottom of the screen it says:
RA Revamped
Build: RA VIGOR-v3.15-getitnowmarketing
Click to expand...
Click to collapse
Yeah that's amon ra.
Now flash the SuperSu zip file.
(the install su doesnt work last time I checked.)
You can get the SuperSu zip in Ashton's ICS thread.
Sent from my Rezound
beautiful....Thank you!
I have no idea where to go from here, I locked the bootloader, but the phone won't boot and if I insert a USB plug it won't stay in fastboot, it just says HTC and drivers fail, no device detected. Any ideas? Thanks in advance. Problem solved in pm.
define "it won't stay in fastboot"... what does happen? you tried to boot to bootloader (vol- & power) right?
what did u do which resultat in a softbrick?
cheers
doorgoo said:
I have no idea where to go from here, I locked the bootloader, but the phone won't boot and if I insert a USB plug it won't stay in fastboot, it just says HTC and drivers fail, no device detected. Any ideas? Thanks in advance. Problem solved in pm.
Click to expand...
Click to collapse
Next time you should share the solution, just in case it happens to anyone else.
Same problem
SysAdmNj said:
Next time you should share the solution, just in case it happens to anyone else.
Click to expand...
Click to collapse
This happened to me as well I think. I have an AT&T version of the HTC One X+
I can't seem to install a rom. Loading hboot gives a failed to open usb master mode error. Using adb push D:\rom.zip /data/ succeeds, but the rom.zip is nowhere to be found in /data/. Using Hasoon's all in one toolkit abd sideloader function, or booting into recovery and typing adb sideloader D:\rom.zip fails, as it gives the adb instructions list.
This happened when I used Hasoon's all in one toolkit to unlock my bootloader, flash twrp, flash the blade boot.img and wipe my phone according to the instructions found in this tread (http://forum.xda-developers.com/showthread.php?t=2027304).
Please help. Can't use my phone at all.
Thanks much!
davismj said:
This happened to me as well I think. I have an AT&T version of the HTC One X+
I can't seem to install a rom. Loading hboot gives a failed to open usb master mode error. Using adb push D:\rom.zip /data/ succeeds, but the rom.zip is nowhere to be found in /data/. Using Hasoon's all in one toolkit abd sideloader function, or booting into recovery and typing adb sideloader D:\rom.zip fails, as it gives the adb instructions list.
This happened when I used Hasoon's all in one toolkit to unlock my bootloader, flash twrp, flash the blade boot.img and wipe my phone according to the instructions found in this tread (http://forum.xda-developers.com/showthread.php?t=2027304).
Please help. Can't use my phone at all.
Thanks much!
Click to expand...
Click to collapse
I get that usb master mode error too, after that it goes on to allow me to select fastboot, etc.. You?
davismj said:
This happened to me as well I think. I have an AT&T version of the HTC One X+
I can't seem to install a rom. Loading hboot gives a failed to open usb master mode error. Using adb push D:\rom.zip /data/ succeeds, but the rom.zip is nowhere to be found in /data/. Using Hasoon's all in one toolkit abd sideloader function, or booting into recovery and typing adb sideloader D:\rom.zip fails, as it gives the adb instructions list.
This happened when I used Hasoon's all in one toolkit to unlock my bootloader, flash twrp, flash the blade boot.img and wipe my phone according to the instructions found in this tread (http://forum.xda-developers.com/showthread.php?t=2027304).
Please help. Can't use my phone at all.
Thanks much!
Click to expand...
Click to collapse
This has happened to me and several people. Search my posts under stats as I wrote the steps I took to get my phone up and working again. Some other people have written instructions too.
Let me know how it goes.
Sent from my HTC One X+ using xda premium
I recently went from being HTC Dev unlocked 1.58 to JuopunutBear S-Off. Before I was able to do fastboot commands but coundn't flash a recovery. I figured that maybe doing Jbear might do something for the issue since I wanted to S-Off anyway. Due to some ignorance I did the Jbear process and wiretrick to achieve S-off. But, Instead of using a Jbear Bootloader I though I could downgrade also by flashing a 1.13 RUU. I did it and my phone worked. When I went to the bootloader it read: S-Off 1.40 ect. (with no Locked/Unlocked bar at top). I wanted to flash a ROM and it didn't work so I thought i should try to unlock the phone bootloader. This did not work.
I then found out I had to use a Jbear bootloader and I am now on: Hboot 1.50.5050 with S-Off and (Joupunutbear) at top. Now whenever I try to use fastboot or adb commands I get the error *device not found* or -waiting for device-. I want to flash a recovery and then a rom but neither is possible now.
Things I have researched and checked:
1. htc sync drivers work/are up to date(i used them before this issue occurred and have tried others)
2. usb debugging is on.
3. I can not do a logcat. I get the same error.
4. I tried to install the recovery through the rom manager app but it got the same error.
Any help in advance would be appreciated.
(I apologize if there is already a solution on the site. I have searched to the best of my ability.)
If your phone boots up, go to developer options and make sure android debugging is enabled
Otherwise, it sounds like you are in boot loader. You need to navigate to fast boot
Then when your USB is connected it should read fast boot USB
Flash recovery
Make a backup
Wipe all partition except SD
Flash ROM/gapps whatever
Reboot
Sent from my Evo V 4G using xda app-developers app
hossman said:
If your phone boots up, go to developer options and make sure android debugging is enabled
Otherwise, it sounds like you are in boot loader. You need to navigate to fast boot
Then when your USB is connected it should read fast boot USB
Flash recovery
Make a backup
Wipe all partition except SD
Flash ROM/gapps whatever
Reboot
Sent from my Evo V 4G using xda app-developers app
Click to expand...
Click to collapse
I have rooted my two previous phones, one of them being HTC android so I have some experience. What I'm saying is that I have usb debugging on and I boot to bootloader, then fastboot and get fastboot-usb.
Despite doing everything correctly it still gives errors with the device. For example, i tried again this morning and waited until it said -waiting for device- to go into fastboot and it did something different:
* attached an image of my commands since I coundn't link them. (new user)
the second command is what happens when i start in fastboot usb.
All commands dealing with fastboot result in *Device not found*
Thanks for the response, I understand those common issues get posted a lot.
I'm working on rooting my very first android phone for the very first time, and I've run across a snag. I've been following Luckythirteen's guide to rooting found here, but so far I've been unable to flash the TWRP recovery. Here's what I posted in the original thread:
Help! I've followed the steps to the T, but I'm struggling with installing the recovery. I've unlocked my bootloader, downloaded the TWRPrecovery.img, put it in the right folder. As soon as I boot into the bootloader, my phone seems to disconnect from the computer. I still have fastboot usb selected, but my device no longer shows up under adb devices. When I try to >fastboot flash recovery TWRPrecovery.img, I get an error "error: cannot load 'TWRPrecovery.img' : Unknown error"
I've got the international HOX+ and a computer running Win7. Any assistance in the matter would be super appreciated.
I hope I've provided enough information for someone to help me out here. I'm a complete Android beginner so this is all a little overwhelming. Thanks.
It is normal that your device does not show using "under adb devices" when in fastboot. You have to use "fastboot devices" instead. Try and see if your dive shows up there.
Also did you try redownloading the recovery.img and/or reinstallung HTC Drivers?
reaper90 said:
It is normal that your device does not show using "under adb devices" when in fastboot. You have to use "fastboot devices" instead. Try and see if your dive shows up there.
Also did you try redownloading the recovery.img and/or reinstallung HTC Drivers?
Click to expand...
Click to collapse
Hey, thanks for the reply. You're right, I did end up finding it under fastboot devices, but it still wouldn't work. Since then I've tried flashing a recovery using the all in one kit found in this, and adb shows that the flash was successful, however when I select recovery under the HBOOT menu, it just shuts off my phone, and when I power up again it reboots normally. Any idea what's up now?
christmas_time said:
Hey, thanks for the reply. You're right, I did end up finding it under fastboot devices, but it still wouldn't work. Since then I've tried flashing a recovery using the all in one kit found in this, and adb shows that the flash was successful, however when I select recovery under the HBOOT menu, it just shuts off my phone, and when I power up again it reboots normally. Any idea what's up now?
Click to expand...
Click to collapse
Where exactly did you see that flashing process was successful? What about your HTC drivers? Are they up to date? What version of TWRP did you try to install?
reaper90 said:
Where exactly did you see that flashing process was successful? What about your HTC drivers? Are they up to date? What version of TWRP did you try to install?
Click to expand...
Click to collapse
The adb command window shows the flashing process just like the images in the initial tutorial. I've tried reinstalling the drivers a few times now, would it show me the device under fastboot devices if my drivers weren't working? I tried the latest TWRP, 2.5.0.0. Sorry for double-posting, I wasn't aware you were the same guy from the other thread!
christmas_time said:
The adb command window shows the flashing process just like the images in the initial tutorial. I've tried reinstalling the drivers a few times now, would it show me the device under fastboot devices if my drivers weren't working? I tried the latest TWRP, 2.5.0.0. Sorry for double-posting, I wasn't aware you were the same guy from the other thread!
Click to expand...
Click to collapse
did you see the following two things in the command window? "sending recovery.img" an then "done"?
and just to be sure: you picked the right recovery version for the One X+?
reaper90 said:
did you see the following two things in the command window? "sending recovery.img" an then "done"?
and just to be sure: you picked the right recovery version for the One X+?
Click to expand...
Click to collapse
I must admit to my embarrassment that yes, it turns out I was trying to flash the wrong recovery (HOX instead of HOX+) and now I feel like an idiot, but I've finally gotten it to work, and I'm finally rooted! Thanks so much!