relocking rezound - HTC Rezound

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!

Related

Juopunutbear S-OFF need help ASAP Please

I used HTC unlocker to unlock my phone and installed cleanrom by scott. I need to send my phone back for repair so I HAVE to restore it to stock before I can send it back. I used Juopunutbear and it failed several times. Now my phone seems to be bricked. ControlBEAR.exe is reporting
Cowardly refusing to S-OFF this phone
Error code is: 4E D7 B9 21
Quit....
Press ENTER to exit.....
all I can get to is the fastboot/hboot menu and it says at the top
***LOCKED***
S-OFF
However I cant install anything or get to recovery or anything else. if I reboot the phone it just takes me back to the fastboot menu
I need by phone back up can someone please help me....
scampbell70 said:
I used HTC unlocker to unlock my phone and installed cleanrom by scott. I need to send my phone back for repair so I HAVE to restore it to stock before I can send it back. I used Juopunutbear and it failed several times. Now my phone seems to be bricked. ControlBEAR.exe is reporting
Cowardly refusing to S-OFF this phone
Error code is: 4E D7 B9 21
Quit....
Press ENTER to exit.....
all I can get to is the fastboot/hboot menu and it says at the top
***LOCKED***
S-OFF
However I cant install anything or get to recovery or anything else. if I reboot the phone it just takes me back to the fastboot menu
I need by phone back up can someone please help me....
Click to expand...
Click to collapse
Looks like you may be S-off. Try downloading a stock GB Ruu, renaming to ph98img and put it on the root of your sd card. Reboot and hboot should install it. It will take a while and a reboot once before finishing.
topgun1953 said:
Looks like you may be S-off. Try downloading a stock GB Ruu, renaming to ph98img and put it on the root of your sd card. Reboot and hboot should install it. It will take a while and a reboot once before finishing.
Click to expand...
Click to collapse
I dont have a card reader or extra sdcard so how do I get a stock GB Ruu onto the sdcard?
scampbell70 said:
I dont have a card reader or extra sdcard so how do I get a stock GB Ruu onto the sdcard?
Click to expand...
Click to collapse
You should be able to do a fastboot push.
What would work better would be to fastboot flash Amon-Ra, then you can mount the SD as mass storage.
Sent from my Business ICS Rezound.
scampbell70 said:
I dont have a card reader or extra sdcard so how do I get a stock GB Ruu onto the sdcard?
Click to expand...
Click to collapse
I'm not big on ADB or Fastboot so I can't tell you how using those tools. However, when I needed to recover after several failed s-off attempts, I used this all in one tool and just selected Flash AmonRa recovery.
Then I would boot into recovery, AmonRa has an option to toggle USB to SD card, so then you could copy whatever from your computer to the SD card.
http://forum.xda-developers.com/showthread.php?t=1504824&highlight=all+in+one
Thank you everyone that helped
You can also do the PH98IMG.zip thing this way:
1) Put PH98IMG.zip in fastboot folder
2) fastboot oem rebootRUU
3) fastboot flash zip PH98IMG.zip
4) Wait a long time, when the prompt returns control to you it is done
5) fastboot reboot
6) Let it fire up and all that jazz
7) Then do "fastboot writesecureflag 3" and you will be 100% stock
con247 said:
You can also do the PH98IMG.zip thing this way:
1) Put PH98IMG.zip in fastboot folder
2) fastboot oem rebootRUU
3) fastboot flash zip PH98IMG.zip
4) Wait a long time, when the prompt returns control to you it is done
5) fastboot reboot
6) Let it fire up and all that jazz
7) Then do "fastboot writesecureflag 3" and you will be 100% stock
Click to expand...
Click to collapse
Note that, if I recall correctly, this:
Code:
7) Then do "fastboot writesecureflag 3" and you will be 100% stock
Will return you to S-On
LunaticSerenade said:
Note that, if I recall correctly, this:
Code:
7) Then do "fastboot writesecureflag 3" and you will be 100% stock
Will return you to S-On
Click to expand...
Click to collapse
I believe you're correct. Pretty sure that's in the Dev board about getting S-On, and that's the command to run.
LunaticSerenade said:
Note that, if I recall correctly, this:
Code:
7) Then do "fastboot writesecureflag 3" and you will be 100% stock
Will return you to S-On
Click to expand...
Click to collapse
He is trying to return it so I assume that is the goal.
con247 said:
7) Then do "fastboot writesecureflag 3" and you will be 100% stock
Click to expand...
Click to collapse
Okay I downloaded a stock signed RUU renamed it and put it on the root of my sdcard, when I rebooted the phone the phone recognized and I applied the update. It booted up perfectly and the phone is back on stock GB, I dont see where to writesecureflag though, did I have to do that before I let the phone boot all the way into the OS for the first time? Under the fastboot menu I see no option to writesecureflag, do I need to reflash the stock RUU and start again?
scampbell70 said:
Okay I downloaded a stock signed RUU renamed it and put it on the root of my sdcard, when I rebooted the phone the phone recognized and I applied the update. It booted up perfectly and the phone is back on stock GB, I dont see where to writesecureflag though, did I have to do that before I let the phone boot all the way into the OS for the first time? Under the fastboot menu I see no option to writesecureflag, do I need to reflash the stock RUU and start again?
Click to expand...
Click to collapse
you will need to fastboot oem writesecureflag 3 in a cmd window with the phone in fastboot:
directoins: http://forum.xda-developers.com/showthread.php?t=1612937
scotty1223 said:
you will need to fastboot oem writesecureflag 3 in a cmd window with the phone in fastboot:
directoins: http://forum.xda-developers.com/showthread.php?t=1612937
Click to expand...
Click to collapse
I tried writing S-On but I keep getting the error device offline. I used
There are 4 ways to do it:
Unplug the usb and plug it back again.
Go to the Settings -> Applications -> Development of your device and uncheck the USB debugging mode and then check it again back!
Restart the adb on your PC. adb kill-server and then adb start-server
Restart your device and try again.
Click to expand...
Click to collapse
to try and fix it but no luck it still says offline, any ideas??
scampbell70 said:
I tried writing S-On but I keep getting the error device offline. I used
to try and fix it but no luck it still says offline, any ideas??
Click to expand...
Click to collapse
You will need to be in fastboot. Pull the battery, then reboot holding volume down.
*Note: make sure there is no PH98IMG.zip on your SD card
Once in hboot, select fastboot. Then connect to your PC.
In your command prompt/adb window, type 'fastboot devices' to make sure your PC reads the phone.
Then type 'fastboot oem writesecureflag 3' and you'll be S-On.
Sent from my Business ICS Rezound.
Phone is all back to stock and shipped back for repairs thank you all very much for your help

[Q] Wont load past white HTC screen.

Just flashed the latest MIUI Rom and now I can't get passed the White screen with the green "HTC"
Do I have to have S-off?
I've had my rezound unlocked since the day I got it 8 months ago but just now decided to flash it, I used to have a INC and rooted and flashed that years ago but i'm a little rusty now,
Burnz92 said:
Just flashed the latest MIUI Rom and now I can't get passed the White screen with the green "HTC"
Does I have to have S-off?
I've had my rezound unlocked since the day I got it 8 months ago but just now decided to flash it, I used to have a INC and rooted and flashed that years ago but i'm a little rusty now,
Click to expand...
Click to collapse
If you are s-on, you have to flash the kernel separately. I'm not familiar with the MIUI rom, but go back and read the installation instructions but it certainly sounds like that is your problem.
topgun1953 said:
If you are s-on, you have to flash the kernel separately. I'm not familiar with the MIUI rom, but go back and read the installation instructions but it certainly sounds like that is your problem.
Click to expand...
Click to collapse
This. If you're S-ON, you have to extract the boot.img from the .zip and flash it manually.
shrike1978 said:
This. If you're S-ON, you have to extract the boot.img from the .zip and flash it manually.
Click to expand...
Click to collapse
How do I manually flash it?
Burnz92 said:
How do I manually flash it?
Click to expand...
Click to collapse
fastboot flash boot boot.img
Sent from my ADR6425LVW using Tapatalk 2
shrike1978 said:
fastboot flash boot boot.img
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
whenever I go to fastboot on my phone(it says "FASTBOOT USB" in highlighted red) and type 'adb devices" it doesn't return anything.
What ive done leading up to the point.
1. Booted in to rec from my phone and flash the rom
2. Rebooted phone with down vol pressed
3. Went to fastboot
4. Pulled up CMD and did cd:...etc
5. Typed adb devices and it doesnt retun anything.
Im about to turn s-off unless im missing something here.
Btw WAR EAGLE
shrike1978 said:
This. If you're S-ON, you have to extract the boot.img from the .zip and flash it manually.
Click to expand...
Click to collapse
How does one manually flash the boot.img?
Sorry I did not see the previous post. I assume you must use a PC for this action and have the fastboot.exe from the SDK toolkit.
Burnz92 said:
whenever I go to fastboot on my phone(it says "FASTBOOT USB" in highlighted red) and type 'adb devices" it doesn't return anything.
What ive done leading up to the point.
1. Booted in to rec from my phone and flash the rom
2. Rebooted phone with down vol pressed
3. Went to fastboot
4. Pulled up CMD and did cd:...etc
5. Typed adb devices and it doesnt retun anything.
Im about to turn s-off unless im missing something here.
Btw WAR EAGLE
Click to expand...
Click to collapse
Fastboot and adb are two different things.
Burnz92 said:
whenever I go to fastboot on my phone(it says "FASTBOOT USB" in highlighted red) and type 'adb devices" it doesn't return anything.
What ive done leading up to the point.
1. Booted in to rec from my phone and flash the rom
2. Rebooted phone with down vol pressed
3. Went to fastboot
4. Pulled up CMD and did cd:...etc
5. Typed adb devices and it doesnt retun anything.
Click to expand...
Click to collapse
What version of Windows are u running? I was having similar problems on Windows 8 and I think it was a driver issue. I never resolved the problem, just switched to a laptop running something other than Win8. Worked like a charm then! Are you using Hasoon All In One tool? That may help if ur a little n00bish like me!
Sent from my Rezound using xda app-developers app
stankopp said:
How does one manually flash the boot.img?
Sorry I did not see the previous post. I assume you must use a PC for this action and have the fastboot.exe from the SDK toolkit.
Click to expand...
Click to collapse
yes you need a pc. have fastboot as well as adb installed and working. if you do not have fastboot downloaded and installed, it will NOT work. if you dont have it just google it and it shouldnt be hard to find. Also, you must have the correct drivers installed for the rezound
1. Open the rom.zip file (that you download) and extract the boot.img file to the same directory that fastboot is installed.
2. Put the rom.zip file on the root of your sd card.
the rest is done from the command line
3. In command prompt, run "adb devices" and confirm that your phone shows up. (if yes, proceed) (if not, go back and confirm you have the correct drivers installed)
4. run "adb reboot recovery", wipe, and flash your rom in recovery (self explanitory) if you need help with this part, im sorry.
5. after the rom finishes its flashing process, run "adb reboot bootloader"
6. when the bootloader comes up, run "fastboot flash boot boot.img"
7. after that flashes, you should be good to go. just run "fastboot reboot" and youre done

Stuck at 4G LTE screen after zip update

I was on 4.0.3 and I flashed the zip through AromRa recovery.
Now, when booting up, its stuck at the 4G screen.
The update was the OTA update released to update radios to Global. THIS
It didn't gave any error at all, it said "Reboot to complete installation or update". But when I clicked the reboot option, I saw a line saying something like "Can't write....." then the screen went off and it rebooted. This line was not there, or atleast not visible before I clicked the reboot option.
I am new to rezound and android, so please let me know what I can do. I wasn't able to get a nandroid backup before doing this, had no ext. SD card.
All I did before flashing the zip was flashing the custom recovery. Nothing else. No SU or anything else.
Can I RUU 4.0.3 to fix this problem?
Yes you need to ruu to get it back. I'm assuming your s on. You need to be s off in order to flash radios by themselves.
Sent from my ADR6425LVW using xda app-developers app
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
lamborg said:
Yes, I am s-on and not rooted.
Is there any specific RUU that I should go to? I was thinking of using 4.03.605.2
Thanks
Click to expand...
Click to collapse
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
feralicious said:
Yes, that's the latest global RUU.
You need to relock to run it:
fastboot oem lock
Put it on your sd card and it should do it's thing when you reboot. Run it a couple times and make sure it's finished so it will get all the system files. I believe it reboots you once it's done.
Then you can unlock again, flash recovery and root. If you have trouble rooting again search this forum for "super su" and you'll find a version you can flash to gain root.
Click to expand...
Click to collapse
I relocked but then tried flashing the zip twice.
Here's what comes in cmd:
sending....
OKAY
writing
<bootloader>adopting sig ....
<bootloader>checking sig
failed <remote: not allowed>
finished
After rebooting, it gets stuck on the white HTC screen.
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
mike7728 said:
sounds like a bad download, go back to android police and try to get the mirror from Illinois, it worked for me a couple of weeks ago after having the same issue as you.
sent from my rooted SAMSUNG GALAXY NOTE 2...
Click to expand...
Click to collapse
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You have to fastboot oem rebootRUU first
then fastboot flash zip PH98IMG.zip
you may have to flash the zip twice.
Code:
androidforums.com/incredible-all-things-root/487280-easier-way-flash-pb31img-files.html
(I can't link yet)
lamborg said:
Thanks mike.
I downloaded the same RUU from a different source and flashed it. But the same failed remote not allowed error.
1 question.
In adb, do I need to type the command fastboot flash zip PH98IMG.zip in the hboot (with otions fastboot, recovery, clear storage, simlock, image crc) or after selecting the fastboot option at the hboot screen?
I am asking because nothing happens when I put the command while on the hboot screen and I get the remote error when commanded from the fastboot screen.
Click to expand...
Click to collapse
You don't flash this in fastboot since it's a zip file.
EDIT: Looks like you can flash in fastboot as mentioned in the above post. Cool, I like that. I would flash it twice as I've read several times that you need to to make sure it gets all the system files.
If htat doesn't work for whatever reason, just put it on the sd card of your phone, detach your phone from your pc and reboot. hboot should find it (it looks for the PH98IMG.zip file) and flash it. Flash it twice to be sure it gets all the system files.
When it's done and you're rebooted use a file explorer and delete the PH98IMG file so it doesn't flash again on the next reboot.

[Q] cant get into recovery after relocking EVOLTE

Ok So....
I was S-On cause i have 64bit Win7. I was going to return LTE for Upgrade to ONE. So i used this to get back to stock. $250 is too much for me right now to upgrade so i'll be keeping my LTE for a couple more months. At least to see whats up with the Mega. Anyways I went back to reroot but im havent been able to get to recovery. I have all my root files (HTC Dev Unlock token) I can Unlock and relock Boot loader. This is where I'm at... See photo 1.
*** UNLOCKED *** ( I Noticed it no longer says "Tampered" across the top. Does that make a diference?)
S-On
HBoot 2.09
Radio 1.12.11.1119
I used the JB OTA firmware from unlimited.io/jewel.htm
I have tried to reflash TWRP 2.4.1.0 But I can't access Recovery. Second photo shows error icon when rebooting to recovery from Boot Loader. I tried re flashing SU, even stock_EVO4gLTE_recovery.img though i dont think that last one would work cause im now on updated firmware.
Am i just SOL and can no longer access recovery?
Will Dirty Racoon help me get recovery back?. Im just now getting familiar to fastboot. Linux is a bit intimidating.
HBoot Pic - https://lh3.googleusercontent.com/-...AAFm0/_gjzRfxXTcA/w815-h611-no/Picture+26.jpg
Recovery Error Pic - https://lh6.googleusercontent.com/-...AAFnE/wyW4K6OEM3o/w816-h612-no/Picture+27.jpg
Put the phone back n bootloader like the 1st pic.
Then select Fastboot
Then connect phone to Pc
Then the Bootloader should show Fastboot USB.
Now open up the folder on your Pc that has Fastboot then open a command Window and type fastboot flash recovery what ever the recovery image name is.
Sent from my EVO using xda premium
Follow this guide made by bigdaddy619 and you should be s-on/unlocked and Rooted then flash your Preferred ROM
http://forum.xda-developers.com/showthread.php?t=2026938
scoot0073 said:
Put the phone back n bootloader like the 1st pic.
Then select Fastboot
Then connect phone to Pc
Then the Bootloader should show Fastboot USB.
Now open up the folder on your Pc that has Fastboot then open a command Window and type fastboot flash recovery what ever the recovery image name is.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I tried flashing recovery 3 times no go.
wait in the OG root zip there are 2 images that say recovery. A "stock_EVO4GLTE_recovery.img" and I also have
"openrecovery-twrp-2.4.1.0-jewel.img"
Im gona try Bgdaddys' guide...
will report back tomorrow.
Thanx for the replies.
Artanis said:
I tried flashing recovery 3 times no go.
wait in the OG root zip there are 2 images that say recovery. A "stock_EVO4GLTE_recovery.img" and I also have
"openrecovery-twrp-2.4.1.0-jewel.img"
Im gona try Bgdaddys' guide...
will report back tomorrow.
Thanx for the replies.
Click to expand...
Click to collapse
Put your phone in fastboot usb then type in terminal/cmd
fastboot flash recovery openrecovery-twrp-2.4.1.0-jewel.img
Then hit enter and it should transfer/flash/install
Then do fastboot reboot-bootloader
Then go into recovery and you should have twrp installed...
Sent from my EVO using xda app-developers app
jocarog said:
Put your phone in fastboot usb then type in terminal/cmd
fastboot flash recovery openrecovery-twrp-2.4.1.0-jewel.img
Then hit enter and it should transfer/flash/install
Then do fastboot reboot-bootloader
Then go into recovery and you should have twrp installed...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You guys rock IDK why it didn't work before. but I just flashed TWRP 2.5 and it worked like a ice cold Boones on a 15 year old cheerleader.
Thanks again.

[Q] Fastboot HELP!!!!

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

Categories

Resources