Related
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!
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
Flashed TWRP 2.6.3.0 on my tf201 and now I cant boot to my OS. Unlocked jb bootloader using the Asus method. After booting to recovery TWRP kept asking for a PW. If I press cancel im able to bypass the screen but I cant mount any partitions to flash a rom. I booted back to my OS tried to flash the rom using goomanager but when the tablet restarted it entered a recovery loop. I cant access my OS, cant mount partitions, and ADB sideload keeps failing to start. any help?
http://forum.xda-developers.com/showthread.php?t=1514088 checked out this link but solutions require ADB. none talk about twrp or passwords
lun7200 said:
Flashed TWRP 2.6.3.0 on my tf201 and now I cant boot to my OS. Unlocked jb bootloader using the Asus method. After booting to recovery TWRP kept asking for a PW. If I press cancel im able to bypass the screen but I cant mount any partitions to flash a rom. I booted back to my OS tried to flash the rom using goomanager but when the tablet restarted it entered a recovery loop. I cant access my OS, cant mount partitions, and ADB sideload keeps failing to start. any help?
http://forum.xda-developers.com/showthread.php?t=1514088 checked out this link but solutions require ADB. none talk about twrp or passwords
Click to expand...
Click to collapse
You have flashed the wrong TWRP for the bootloader you are on.
Try the following.
http://forum.xda-developers.com/showthread.php?t=2409602
I know you are bootlooping to TWRP so type adb reboot bootloader to get into the bootloader menu.
flumpster said:
You have flashed the wrong TWRP for the bootloader you are on.
Try the following.
http://forum.xda-developers.com/showthread.php?t=2409602
I know you are bootlooping to TWRP so type adb reboot bootloader to get into the bootloader menu.
Click to expand...
Click to collapse
Hi, thanks for the response. I tried to run adb reboot bootloader but all I get back is error: insufficient permissions for device and in the link you sent they get the device into fastboot mode using the paperclip reset button. His was on the TF300, is it any different for the TF201? How can I get it into fastboot mode since it keeps looping to TWRP with no access to the rest of the system. Im running this on Ubuntu so its definetly not a drivers issue.
lun7200 said:
Hi, thanks for the response. I tried to run adb reboot bootloader but all I get back is error: insufficient permissions for device and in the link you sent they get the device into fastboot mode using the paperclip reset button. His was on the TF300, is it any different for the TF201? How can I get it into fastboot mode since it keeps looping to TWRP with no access to the rest of the system. Im running this on Ubuntu so its definetly not a drivers issue.
Click to expand...
Click to collapse
Where are you trying to run that command from?
You do not go into adb sideload while in twrp. You are already in full adb mode as soon as you load into twrp and you just type the command while there.
flumpster said:
Where are you trying to run that command from?
You do not go into adb sideload while in twrp. You are already in full adb mode as soon as you load into twrp and you just type the command while there.
Click to expand...
Click to collapse
Initially tried to run from ADB sideload but it didnt work obviously. When I run it at the "TWRP Password" screen is when I get the error: insufficient permission for device message. I run the commands after pressing cancel on the password prompt and i get the same message.
*****@******:~$ adb reboot bootloader
error: insufficient permissions for device
[email protected]*******:/home/***# adb reboot bootloader
error: insufficient permissions for device
lun7200 said:
Initially tried to run from ADB sideload but it didnt work obviously. When I run it at the "TWRP Password" screen is when I get the error: insufficient permission for device message. I run the commands after pressing cancel on the password prompt and i get the same message.
Click to expand...
Click to collapse
Hmm, I have never failed to get that command to work but I also have never tried it from linux.
flumpster said:
Hmm, I have never failed to get that command to work but I also have never tried it from linux.
Click to expand...
Click to collapse
will try with a windows machine and report back findings
Please help. i'm trying to root my A52s. I passed the bootloader unlock and go on for rooting but I cannot boot into bootloader to run the command. What should I do?
@trai_th do you really mean bootloader?
That's equivalent to downlode mode on samsungs.
It should work with adb if turned on in dev options.
Command: adb reboot bootloader.
bmwdroid said:
@trai_th do you really mean bootloader?
That's equivalent to downlode mode on samsungs.
It should work with adb if turned on in dev options.
Command: adb reboot bootloader.
Click to expand...
Click to collapse
i tried adb reboot bootloader, it's back to the samsung screen. But i manage to use fastboot mode when we try to unlock bootloader page instead. but still can't root it. don't know how, it's quite complicated...
Arobase40 said:
So do you gain access to your bootloader now ?
Click to expand...
Click to collapse
yep
Hi,
has anybody tried to relock the bootloader?!
i was a little over hasty and unlocked a device. I thought (yeah, i didnt checked it ...) if asus is offering a unlocker, it should be no big deal to lock it again.
But everything i found is for the ZF8, and all i found does not work on the ZF9.
It starts that there is no adb/sideload option in recovery nor have i found a custom recovery.
And every relock command in fastboot is not known by the fastboot environement of the ZF9...
So has anybody found a way?
thx in advance.
Matt
Has anyone found a method to close the bootloader again? I'm thinking of opening it but I'm worried that I won't find a method to close it if necessary.
zero5liters said:
Hi,
has anybody tried to relock the bootloader?!
i was a little over hasty and unlocked a device. I thought (yeah, i didnt checked it ...) if asus is offering a unlocker, it should be no big deal to lock it again.
But everything i found is for the ZF8, and all i found does not work on the ZF9.
It starts that there is no adb/sideload option in recovery nor have i found a custom recovery.
And every relock command in fastboot is not known by the fastboot environement of the ZF9...
So has anybody found a way?
thx in advance.
Matt
Click to expand...
Click to collapse
try "fastboot oem asus-csc_lk". After wipe data.
sakun-ice said:
try "fastboot oem asus-csc_lk". After wipe data.
Click to expand...
Click to collapse
i tried it but without wipe before. And that did not work.
I try it later with wipe. But i do not have hope. because most of the fastboot commands do not work on the ZF9.
I tried to read the commands out of the bootloader but with no luck ...
zero5liters said:
i tried it but without wipe before. And that did not work.
I try it later with wipe. But i do not have hope. because most of the fastboot commands do not work on the ZF9.
I tried to read the commands out of the bootloader but with no luck ...
Click to expand...
Click to collapse
If you haven't tried it, you can try it with:
-fastboot oem asus-back
-fastboot oem asus-csc_lk
-fastboot flashing lock
-fastboot flashing lock_critical
-fastboot oem lock
-fastboot oem lock_critical
-fastboot flash !frp-partition! default_key.bin
-fastboot oem asus-lock
No. Didnt work. 'Command not supported in default implemantation' All of these commands.
I did not try the *critical commands and the "frp partition". I had not time to read me in on that. And i dont want to brick the phone complete.
For what it's worth, fastboot oem asus-csc_lk worked for me. It also wiped the phone itself, I didn't have to do it manually.
schizophaser said:
For what it's worth, fastboot oem asus-csc_lk worked for me. It also wiped the phone itself, I didn't have to do it manually.
Click to expand...
Click to collapse
No,
i tried it but fastboot doesnt recognize the command.
But thanks. I now startet the "Repair" @ asus.
schizophaser said:
For what it's worth, fastboot oem asus-csc_lk worked for me. It also wiped the phone itself, I didn't have to do it manually.
Click to expand...
Click to collapse
Yeah ! works for me too
OTA update working ?
rafik25 said:
OTA update working ?
Click to expand...
Click to collapse
Doesn't seem so. 2050 was released two weeks ago and didn't show up in the updater, so I had to install it manually today.
schizophaser said:
Doesn't seem so. 2050 was released two weeks ago and didn't show up in the updater, so I had to install it manually today.
Click to expand...
Click to collapse
Same, though I expected that since I rooted.
For any one wondering how to update, just take the firmware file from ASUS's site, place it in your phone's internal storage, then either wait a few seconds for the update notification to pop up or restart your phone (you should see it then). Follow the prompts from there.
schizophaser said:
For what it's worth, fastboot oem asus-csc_lk worked for me. It also wiped the phone itself, I didn't have to do it manually.
Click to expand...
Click to collapse
This command works? Can someone give me a quick guide to close the bootloader? Right now I have twrp and magisk.
sakun-ice said:
This command works? Can someone give me a quick guide to close the bootloader? Right now I have twrp and magisk.
Click to expand...
Click to collapse
1. You can only re-lock the bootloader by going back to the stock firmware/recovery, losing twrp and magisk.
2. Re-locking the bootloader does not re-enable the OTA updates, but might help with Google Pay/SafetyNet attestation if that's broken for some reason.
3. This command works. Just flash the stock firmware and recovery, then do adb reboot bootloader and fastboot oem asus-csc_lk.
schizophaser said:
1. You can only re-lock the bootloader by going back to the stock firmware/recovery, losing twrp and magisk.
2. Re-locking the bootloader does not re-enable the OTA updates, but might help with Google Pay/SafetyNet attestation if that's broken for some reason.
3. This command works. Just flash the stock firmware and recovery, then do adb reboot bootloader and fastboot oem asus-csc_lk.
Click to expand...
Click to collapse
To flash the stock recovery is it enough to install the full zip of the stock ROM from twrp and reboot?
sakun-ice said:
To flash the stock recovery is it enough to install the full zip of the stock ROM from twrp and reboot?
Click to expand...
Click to collapse
Yes, that should be enough.
schizophaser said:
Yes, that should be enough.
Click to expand...
Click to collapse
ok, just one last question. If I have the latest version (2060.113) with TWRP, to leave everything stock what I have to flash is the zip downloaded from ASUS (also 2060.113: https://dlcdnets.asus.com/pub/ASUS/ZenFone/AI2202/ASUS_AI2202-33.0804.2060.113-kernel-src.tar.gz?model=Zenfone%209 ). I have seen that there are other ROMs called RAW, but I don't know exactly which one to install. I'm afraid that when installing the zip from that link something "non-stock" will remain installed and when closing the bootloader the smartphone won't boot.
sakun-ice said:
ok, just one last question. If I have the latest version (2060.113) with TWRP, to leave everything stock what I have to flash is the zip downloaded from ASUS (also 2060.113: https://dlcdnets.asus.com/pub/ASUS/ZenFone/AI2202/ASUS_AI2202-33.0804.2060.113-kernel-src.tar.gz?model=Zenfone%209 ). I have seen that there are other ROMs called RAW, but I don't know exactly which one to install. I'm afraid that when installing the zip from that link something "non-stock" will remain installed and when closing the bootloader the smartphone won't boot.
Click to expand...
Click to collapse
I can't say much about this. I don't think it's going to be a problem, but of course you're doing it at your own risk.