I am trying to install twrp on my device, but i never had adb or fastboot installed. I tried to follow the guide in another thread, and when i enter the command line it has an error like it not recognizing my prime.
since my bootloader is unlocked, i wouldnt be able to get the ota, so i downloaded the zip from asus support site. is twrp the only way to install the update?
Related
I have a UK-bought SGT10.1, which I rooted shortly after purchase and installed CWM Recovery using Odin. I've been running In Paris for a while, and was about to update to v5. Last time I downloaded pershoot's kernel from droidbasement, I saw an updated version of CWM Recovery here: http://droidbasement.com/db-blog/?p=2370.
Being a security-type, running the latest versions is always the best option to me - and seeing I know my way around the console I figured I'll install adb/fastboot and use that this time instead of Odin. So I downloaded the SDK, installed the Tab 10.1 drivers (I've reinstalled Windows since I rooted), and grabbed the fastboot .exe from the previous revision and placed it inside android-sdk\platform-tools next to adb.
Now I'm trying to follow the instructions to install the extracted .img - but having some issues getting into fastboot mode in order to execute the commands. Running adb devices results in expected output, as does adb reboot recovery. However running adb reboot bootloader causes the device to reboot all the way back through to the lockscreen. I see some advice stating that to manually enter fastboot you reboot the device holding power+vol down, then pressing down to switch to the second option that isn't download mode. However that to me is the option to manually enter CWM Recovery, so now I'm confused. Running fastbooot reboot-bootloader cause
I don't want to brick my device, so I figured I'd ask for some advice here for getting into fastboot mode, and ask whether I can just flash the .zip inside CWM Recovery or if that is a very risky move?
Thanks in advance
I currently have S-Off 1.5 Hboot on my Sprint Evo 3D with 2.17.651.5 HTC Software Release. I am having problems rooting the phone using the Revolutionary rooting method. When I run Revolutionary.exe, I get an error message that says my "Shooter" is not supported at this time. Also, when I try and follow your instructions via cmd command propt, I can't seem to access the "rootevo3dnew" zip file I downloaded from "HTCEVOHACKS website. Please help!!!
jshawjr said:
I currently have S-Off 1.5 Hboot on my Sprint Evo 3D. I am having problems rooting the phone using the Revolutionary rooting method. When I run Revolutionary.exe, I get an error message that says my "Shooter" is not supported at this time. Also, when I try and follow your instructions via cmd command propt, I can't seem to access the "rootevo3dnew" zip file I downloaded from "HTCEVOHACKS website. Please help!!!
Click to expand...
Click to collapse
There is a difference between unlocking the bootloader and gaining root access. If you're device is already s-off, as stated above, there is no need to run revolutionary again to unlock the device as the device has already been unlocked.
The next step after unlocking the device is seting up root access in the respectively loaded ROM, generally the stock ROM.
A common approach: you can either flash a custom recovery, which can then load the superuser .zip file and setup root access in the currently loaded stock ROM, or you can flash a custom ROM through the custom recovery which contains root access already setup.
Hope that helps clarify some of the possible confusion!
This does help. How do I flash a Custom Recovery? When I go into Fastboot and choose Recovery, the phone just locks up and I can't go any further...can you please send instructions?
jshawjr said:
This does help. How do I flash a Custom Recovery? When I go into Fastboot and choose Recovery, the phone just locks up and I can't go any further...can you please send instructions?
Click to expand...
Click to collapse
Directions are posted all over the forum in many different guides and threads.
There are multiple ways of accomplishing the same end goal. If you're interested in finding the easiest method for you, might need to do some research.
The method I would personally use would be the command: fastboot flash recovery c:\recovery.img .
The advantage to this route is the fastboot flash command will permanently load the custom recovery in the recovery partition so when you follow the steps you outlined, boot into the bootloader and select recovery, the recovery will load.
Hope that helps!
I will try this and see if I can get it to work. It appears I'm doing something wrong on my computers 'cmd' command prompt...I keep geeting an error.
I was able to finally get into cmd command prompt using Revolutionary.exe and it tells me that my Hboot 1.5 is not supported. Is there another way to flash custome recovery image?
Problem: Was trying to install AOKP 4.0 onto my fully updated TF201.
Wiped data/cache/davlik
installed ROM
installed Google Apps
Device stuck on splash screen.
Figured out the problem was an older version on CWM. I believe it was 5.5.0.4.
Tried to go install latest version of CWM: 5.8.3.4 by using the Fastboot method.
Accidentally selected Wipe Data Option instead of USB.
Lost CWM, all data on internal memory and my entire OS.
Device cannot boot (stays on splash screen). I also try to get back into CWM and it fails. I get bounced back to the Fastboot screen.
What can I do to get this thing back up and running? I will even take stock at this moment just to get the ball rolling again.
Thanks!
kevinb77 said:
Problem: Was trying to install AOKP 4.0 onto my fully updated TF201.
Wiped data/cache/davlik
installed ROM
installed Google Apps
Device stuck on splash screen.
Figured out the problem was an older version on CWM. I believe it was 5.5.0.4.
Tried to go install latest version of CWM: 5.8.3.4 by using the Fastboot method.
Accidentally selected Wipe Data Option instead of USB.
Lost CWM, all data on internal memory and my entire OS.
Device cannot boot (stays on splash screen). I also try to get back into CWM and it fails. I get bounced back to the Fastboot screen.
What can I do to get this thing back up and running? I will even take stock at this moment just to get the ball rolling again.
Thanks!
Click to expand...
Click to collapse
Go here, http://forum.xda-developers.com/showthread.php?t=1615990 read the OP, then go here to download http://teamw.in/project/twrp2/93
Follow the instructions under
Download - Recovery Image / Fastboot Method:
You will back up and running in no time, unfortunately you will need to reinstall the rom....
PS you will need to adb push the rom after you reboot to recovery....
Gage_Hero said:
Go here, http://forum.xda-developers.com/showthread.php?t=1615990 read the OP, then go here to download http://teamw.in/project/twrp2/93
Follow the instructions under
Download - Recovery Image / Fastboot Method:
You will back up and running in no time, unfortunately you will need to reinstall the rom....
PS you will need to adb push the rom after you reboot to recovery....
Click to expand...
Click to collapse
Thanks for the quick response!
OK, I was able to get the stock TF201 drivers onto my Windows 7 PC (since an alternate method had me change them) I am following every step explained in the directions from TeamW.in and am getting this error: "The program can't start because AdbWinAPI.dll is missing from your computer. Try reinstalling the program to fix this problem"
(UPDATE) I was able to find a ADBWinAPI.dll file and I dropped it into the same folder as the twrp.blob and fastboot.exe files. I am not able to access the cmd line, but it does not start the flash, it only lists a bunch of optional cmds to pick from. None of which look useful.
kevinb77 said:
Thanks for the quick response!
OK, I was able to get the stock TF201 drivers onto my Windows 7 PC (since an alternate method had me change them) I am following every step explained in the directions from TeamW.in and am getting this error: "The program can't start because AdbWinAPI.dll is missing from your computer. Try reinstalling the program to fix this problem"
(UPDATE) I was able to find a ADBWinAPI.dll file and I dropped it into the same folder as the twrp.blob and fastboot.exe files. I am not able to access the cmd line, but it does not start the flash, it only lists a bunch of optional cmds to pick from. None of which look useful.
Click to expand...
Click to collapse
Did you ever have any luck with this? I had a JB ROM soft brick my 201 about a year ago. I lost TWRP recovery, OS, pretty much everything. It stays on the splash screen and allows me to get to the fastboot option. I can't get my computer(windows 8) to recognize it at all. Just states it can not recognize USB device. I installed the universal naked driver package along with trying the stock ASUS driver package with no luck.
I put the tablet down and purchased a 701 but now would like to fix the 201 and sell it. If you have any advice I would be very thankful
I have been trying to update SuperSU with the app and its always failing. Also I am trying to use Titanium backup and it keeps telling me I am not rooted. Can anyone please help me fix this issue?
I am also trying to update TWRP, I have it downloaded already just not sure how to do it.
Download the file I sent you & flash it in recovery. As far as updating TWRP, you'll need to download the img file from the TWRP site, place it in your ADB-fastboot folder, connect via fastboot USB and run the command "fastboot flash recovery nameofrecovery.img". If you're S-off you can download the TWRP zip and install it through the bootloader just like a firmware update.
If you don't have ADB on your computer, take a look at the top link in my sig. There's a link on how to install ADB included in that guide:thumbup:
Sent from my HTC EVO 4G LTE
So I am a first time rooter, so I'll try my best to use the proper terms and whatnot.
Anyways, I have an unlocked HTC One X+ that I am trying to root. I was using the AIO kit by Hasoon2000. I had my bootloader successfully unlocked, and so I proceeded to continue with rooting. I thought I pushed the SuperSU.zip to the device, because the cmd line said it was successful. So I booted into recovery mode, made a backup, and then when to flash the SuperSU.zip file. However, I could not find it in the file explorer in recovery mode.. so I went to push the file to the phone again, but now it says device not found. The only thing I can think that's happened is my USB debugging got turned off... which is bad. So is SuperSU.zip in my phone somewhere, or am I stuck with a phone that can only go into recovery mode?
Thanks for any help!
I have now similar problem too...
actually I had rooted successfully, but after many failed CM11 installation attempts, I decided to relock the bootloader, in order to update the Firmware. But it didn't work too and I came the way back again, in which I unlocked the bootloader with Unlock Token etc. again. Now the bootloader is unlocked but apparently not rooted!?! I can't push superuser via adb because **Device is not found** and I can only go to TWRP Recovery and bootloader...
COULD SOMEONE HELP??!
PS: when i press the reboot in TWRP, it says that "the phone seems not to be rooted, do you want to install the SuperUser? and when I accept it... it reboots only and nothing does change!
well... im not sure what I did differently but it finally recignized the device!! And now I managed to get everything installed... weird!