Related
When I try to reboot to the ClockworkMod Recovery using both in-system methods (ROM Manager, etc.), or using the volume buttons, it only boots to the Acer screen with Entering recovery image kernel or Entering boot menu mode. After that, the screen hangs there, doing nothing. I'm sure the solution is out there somewhere, but I haven't found it. Also, I cannot get adb or fastboot to work from a Windows 7 64-bit command line. I did install a few things from the Android SDK, but I'm not sure if I installed everything I need.
Any help? I'm looking to upgrade my CyanogenMod 10.1 to the latest stable build, but I'm unable to do that until this problem is solved.
Thanks!
OMIGHTY1 said:
When I try to reboot to the ClockworkMod Recovery using both in-system methods (ROM Manager, etc.), or using the volume buttons, it only boots to the Acer screen with Entering recovery image kernel or Entering boot menu mode. After that, the screen hangs there, doing nothing. I'm sure the solution is out there somewhere, but I haven't found it. Also, I cannot get adb or fastboot to work from a Windows 7 64-bit command line. I did install a few things from the Android SDK, but I'm not sure if I installed everything I need.
Any help? I'm looking to upgrade my CyanogenMod 10.1 to the latest stable build, but I'm unable to do that until this problem is solved.
Thanks!
Click to expand...
Click to collapse
is it possible you try the connection on a linux maschine? (ubunty/mint) you should be able to issue "fastboot devices".
Sometimes Win7 is sluggish.
Also have you tried the resetbutton and then boot to fastboot?
gl
-Buster
I don't have any Linux machines to boot to, although I suppose I could try a Live CD. I've tried getting to fastboot using every method available, but I still haven't had any luck.
OMIGHTY1 said:
I don't have any Linux machines to boot to, although I suppose I could try a Live CD. I've tried getting to fastboot using every method available, but I still haven't had any luck.
Click to expand...
Click to collapse
keep in mind then that you need to install adb and fastboot from the packetmanager. but i for one do my adb/fastboot from my linux mint since i dont need to hassle with the drivers for my devices anymore
I'll try it from Linux, then. I'll report back with my findings.
OMIGHTY1 said:
I'll try it from Linux, then. I'll report back with my findings.
Click to expand...
Click to collapse
you'll need:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
sudo apt-get install android-tools-fsutils
Hey man . have u solved the issue. I have the same problem
nandox310 said:
Hey man . have u solved the issue. I have the same problem
Click to expand...
Click to collapse
Which version of CWM are you using?
Latest versions don't work (stuck on the boot screen page).
You should use version 6.0.2.3 or previuos versions.
Sorry, I haven't been to the thread in awhile, I've been busy with stuff. XD
I haven't tried what was suggested yet, and 6.0.2.3 doesn't work for me either.
Fantastic!
After installing the packages (I had to find the .deb packages myself, as the Terminal wasn't finding them), I was able to detect the device in Ubuntu 13.04 i386. Furthermore, I was able to reinstall the CWM Recovery from the CyanogenMod Wiki for this device. I fastboot'd into the Bootloader, flashed the recovery, then "adb reboot recovery", and there's the recovery menu! Thanks for your help everyone! :laugh:
OMIGHTY1 said:
After installing the packages (I had to find the .deb packages myself, as the Terminal wasn't finding them), I was able to detect the device in Ubuntu 13.04 i386. Furthermore, I was able to reinstall the CWM Recovery from the CyanogenMod Wiki for this device. I fastboot'd into the Bootloader, flashed the recovery, then "adb reboot recovery", and there's the recovery menu! Thanks for your help everyone! :laugh:
Click to expand...
Click to collapse
you're welcome :highfive:
whoops wrong thread
''
Hi XDA,
I am a complete noob, and this is my first time posting, so bear with me.
Some time ago I rooted and unlocked my TF300 with SuperSu. Recently I wanted to upgrade to 4.4 kitkat. However, my Tablet was stuck at Andriod 4.1 because of the the unlock.
I went to manually update my TF via the Asus website. I installed the 10.6.1.8 using my TWRP 2.5, and Oem 4.1 OS. Installation worked just fine. After install, I booted up and I had 4.2 with everything working correctly.
Next step was to install TWRP 2.7.0.1. I reset my TF and went into RCK to see something went wrong when updating.
My TWRP will not load, and I get the Android on his back with the red triangle when I try to enter RCK.
Thanks in advance!!
I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.
TallMilk said:
I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.
Click to expand...
Click to collapse
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.
cmendonc2 said:
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.
Click to expand...
Click to collapse
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks
TallMilk said:
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks
Click to expand...
Click to collapse
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.
You are amazing. I will give it a try tonight and report back!
cmendonc2 said:
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.
Click to expand...
Click to collapse
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.
TallMilk said:
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.
Click to expand...
Click to collapse
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.
cmendonc2 said:
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.
Click to expand...
Click to collapse
Awesome! Worked like a charm. twrp 2.7.0.1 installed perfectly.
Then I tried to flash the cyanogenmod. Said it installed fine, but it just gets stuck on the loading screen...
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.
TallMilk said:
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.
Click to expand...
Click to collapse
Damn, so I'm screwed. Why does Asus have to such so much...? You can no longer unlock afaik.
SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?
cmendonc2 said:
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?
Click to expand...
Click to collapse
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:
SilentSpartan said:
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:
Click to expand...
Click to collapse
Did you ever get your tablet fixed? I am having some problems myself after a miserable m9 update.
Been a while so i tried read up a bit. Thank you for taking the time to read this and/or dropping a little knowledge on me.
I Install Weaksauce. Run.
Install SuperSu.
Run firewater
can someone tell me where to get adb tools? have never really messed around with adb.
Install CWM or TWRP (which is more stable?)
nandroid
install custom rom
Correct order? and some help with the adb would be appreciated. Thanks again
If nobody else helps with adb stuff, I'll link in a little when I get on the computer. Try firewater first. If it fails and says it will never work with your device in the error, you will need to DL and use sunshine. It will cost you 25 dollars but worth it if you ever want to have control of your device.
After you use firewater or sunshine, whatever you have to use. reboot, uninstall weak sauce and SuperSU.
Then back into fastboot.
Definitely use twrp
After installing twrp with fastboot,
After you have twrp, flash SuperSU zip found here on xda in chainfires thread. This will give you your permanent root.
Then you can nandroid, and rom all you want.
silver04v said:
If nobody else helps with adb stuff, I'll link in a little when I get on the computer. Try firewater first. If it fails and says it will never work with your device in the error, you will need to DL and use sunshine. It will cost you 25 dollars but worth it if you ever want to have control of your device.
After you use firewater or sunshine, whatever you have to use. reboot, uninstall weak sauce and SuperSU.
Then back into fastboot.
Definitely use twrp
After installing twrp with fastboot,
After you have twrp, flash SuperSU zip found here on xda in chainfires thread. This will give you your permanent root.
Then you can nandroid, and rom all you want.
Click to expand...
Click to collapse
where do i put twrp.img
camf3xu said:
where do i put twrp.img
Click to expand...
Click to collapse
Youbplace the image in your adb folder in.....sdk/platform-tools.
camf3xu said:
where do i put twrp.img
Click to expand...
Click to collapse
Into the same folder where your adb.exe and fastboot.exe are.
To get adb/fastboot try this great little tool: http://forum.xda-developers.com/showthread.php?t=2317790
Make sure USB debugging is enabled in Developer Options.
Then open Device Manager on your PC, connect your phone booted to Android via USB cable and note any changes. You should see an entry for adb interface. If it doesn't have a yellow exclamation mark next to it, you probably have the correct driver installed. If it does, right click the entry and update the driver.
Check the connection with the command:
Code:
adb devices
from a command prompt opened from the adb folder.
If it returns a string of letters and numbers: Congrats, your adb is working.
Next boot the phone to hboot.
Connect it via USB and you should see a new entry for the fastboot interface.
Proceed as above.
To test the connection issue
Code:
fastboot devices
If you get the connection, the command to flash TWRP is
Code:
fastboot flash recovery twrp.img
Check out the 2 other posts many get firewater to work using superuser with weaksauce app instead of supersu. Check out the two other posts below first is the main one.
http://forum.xda-developers.com/showthread.php?t=2787587
http://forum.xda-developers.com/ver...firewater-s-off-fail-bottle-chugging-t2821691
Hello guys, I had root when I had androd 4.4.4 but uprading it to 5.0.1 made my root ineffective. When I open my app list I can still see there is SuperSU but when I try to open, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upraded to android 5.0 you need to manually re-roo - consult the relevant forums for your device."
Well thats why I'm here. I googled the "how to root android 5.0.1 on linux" term but there wasnt any way to do it.
I hope you guys can help me.
Conixcit said:
Hello guys, I had root when I had androd 4.4.4 but uprading it to 5.0.1 made my root ineffective. When I open my app list I can still see there is SuperSU but when I try to open, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upraded to android 5.0 you need to manually re-roo - consult the relevant forums for your device."
Well thats why I'm here. I googled the "how to root android 5.0.1 on linux" term but there wasnt any way to do it.
I hope you guys can help me.
Click to expand...
Click to collapse
Download the SuperSU zip file (google for it) an then install it from recovery. I assume you have a custom recovery and the android sdk(adb + fastboot) on your linux desktop.
Other option is to install a custom ROM with the SuperSU already installed. I am running Cataclysm rom.
Hope it helped!
nunojsa said:
Download the SuperSU zip file (google for it) an then install it from recovery. I assume you have a custom recovery and the android sdk(adb + fastboot) on your linux desktop.
Other option is to install a custom ROM with the SuperSU already installed. I am running Cataclysm rom.
Hope it helped!
Click to expand...
Click to collapse
A small correction:
nunojsa said:
I assume you have a custom recovery and the android platform-tools (adb + fastboot) on your linux desktop.
Click to expand...
Click to collapse
(To get adb/fastboot, most Linux distros have them packaged outside the android-sdk - android-sdk is mostly used by app devs. Most people will only use adb or fastboot, thus have no need for the sdk, which brings heavy java deps)
@Conixcit , http://forum.xda-developers.com/google-nexus-5/#root - easy enough.
At least for Ubuntu based distros you can
1. Install adb and fastboot by going the terminal and entering:
sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
(Edit: that is supposed to be a colon followed by a p)
sudo apt-get install android-tools-adb android-tools-fastboot
2. Enable debugging in developer options
3. Type in the terminal:
sudo adb start-server
adb reboot-bootloader
fastboot oem unlock
4. Download the latest version of twrp and the supersu.zip for the nexus 5 (hammerhead)
5. Rename the twrp file "recovery.img" and move it into your home folder
6. Type into the terminal:
fastboot flash recovery recovery.img
7. Let it do its thing and then turn it on. Drag your supersu.zip into a folder on your phone (somewhere where you find it)
8. Type into the terminal:
adb reboot-bootloader
9. Use the volume buttons to scroll down to recovery then short press the power button. Once booted into recovery, choose install, find SuperSU and swipe to install
9. Power on the phone and go into SuperSU and check if the binaries need to be updated and if they do say yes and when it asks you to reboot, do so.
Hope that helps
awsumatt said:
At least for Ubuntu based distros you can
1. Install adb and fastboot by going the terminal and entering:
sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
(Edit: that is supposed to be a colon followed by a p)
sudo apt-get install android-tools-adb android-tools-fastboot
2. Enable debugging in developer options
3. Type in the terminal:
sudo adb start-server
adb reboot-bootloader
fastboot oem unlock
4. Download the latest version of twrp and the supersu.zip for the nexus 5 (hammerhead)
5. Rename the twrp file "recovery.img" and move it into your home folder
6. Type into the terminal:
fastboot flash recovery recovery.img
7. Let it do its thing and then turn it on. Drag your supersu.zip into a folder on your phone (somewhere where you find it)
8. Type into the terminal:
adb reboot-bootloader
9. Use the volume buttons to scroll down to recovery then short press the power button. Once booted into recovery, choose install, find SuperSU and swipe to install
9. Power on the phone and go into SuperSU and check if the binaries need to be updated and if they do say yes and when it asks you to reboot, do so.
Hope that helps
Click to expand...
Click to collapse
Any debian based distro .... their, fixed that for you .... ubuntu is based and built from debian.
Sent from my rooted RCT6203W46 using xda-dev app
awsumatt said:
At least for Ubuntu based distros you can
1. Install adb and fastboot by going the terminal and entering:
sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
(Edit: that is supposed to be a colon followed by a p)
sudo apt-get install android-tools-adb android-tools-fastboot
2. Enable debugging in developer options
3. Type in the terminal:
sudo adb start-server
adb reboot-bootloader
fastboot oem unlock
4. Download the latest version of twrp and the supersu.zip for the nexus 5 (hammerhead)
5. Rename the twrp file "recovery.img" and move it into your home folder
6. Type into the terminal:
fastboot flash recovery recovery.img
7. Let it do its thing and then turn it on. Drag your supersu.zip into a folder on your phone (somewhere where you find it)
8. Type into the terminal:
adb reboot-bootloader
9. Use the volume buttons to scroll down to recovery then short press the power button. Once booted into recovery, choose install, find SuperSU and swipe to install
9. Power on the phone and go into SuperSU and check if the binaries need to be updated and if they do say yes and when it asks you to reboot, do so.
Hope that helps
Click to expand...
Click to collapse
Here is the question, will I lose my data after step 6 ?
Second ;
Can I install SuperSU. zip directly command line without twrp. I don't like recovery things.
My meaning is ; can I install the SuperSU.zip with "fastboot flash recovery SuperSU. Zip " or something like that. I've installed Android L manually, so first 5 step is already done.
Conixcit said:
Here is the question, will I lose my data after step 6 ?
Second ;
Can I install SuperSU. zip directly command line without twrp. I don't like recovery things.
My meaning is ; can I install the SuperSU.zip with "fastboot flash recovery SuperSU. Zip " or something like that. I've installed Android L manually, so first 5 step is already done.
Click to expand...
Click to collapse
"fastboot oem unlock" is what wipes the /data partition. Flashing a recovery only replaces the recovery.
You can't flash a zip in fastboot, and sideloading the zip probably won't work if you're on the stock recovery. It's best to flash a custom recovery anyways since it lets you do backups (important if you have root access) and flash other things that you may want to.
Elluel said:
"fastboot oem unlock" is what wipes the /data partition. Flashing a recovery only replaces the recovery.
You can't flash a zip in fastboot, and sideloading the zip probably won't work if you're on the stock recovery. It's best to flash a custom recovery anyways since it lets you do backups (important if you have root access) and flash other things that you may want to.
Click to expand...
Click to collapse
Well we have a problem here: I wanna root my phone but as you say I need to install custom recovery first. But as you said again I need rooted phone.
So : how I'm gonna do that ?
As I said before ' I've already did "fast OEM unlock" step.
So my question is :
will I lose any data while installing custom recovery via adb (terminal)
I'm saying that again : fast OEM thing is already done.
Conixcit said:
Well we have a problem here: I wanna root my phone but as you say I need to install custom recovery first. But as you said again I need rooted phone.
So : how I'm gonna do that ?
As I said before ' I've already did "fast OEM unlock" step.
So my question is :
will I lose any data while installing custom recovery via adb (terminal)
I'm saying that again : fast OEM thing is already done.
Click to expand...
Click to collapse
Huh?
- You need an unlocked bootloader to flash a custom recovery (which you do, fastboot oem unlock)
- You need a custom recovery to flash SuperSU for root access
I already answered your question in my previous post. Again: fastboot oem unlock is what wipes the /data partition, flashing a recovery using fastboot does not.
I rooted my phone on 5.0.1 without problems. Maybe try a different version of CF-Autoroot or do it on a computer running Windows.
Sent from my Nexus 5 using XDA Free mobile app
KodRoute said:
I rooted my phone on 5.0.1 without problems. Maybe try a different version of CF-Autoroot or do it on a computer running Windows.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Windows is not necessary since adb and fast boot are available on all platforms.....
#stayparanoid
Elluel said:
Huh?
- You need an unlocked bootloader to flash a custom recovery (which you do, fastboot oem unlock)
- You need a custom recovery to flash SuperSU for root access
I already answered your question in my previous post. Again: fastboot oem unlock is what wipes the /data partition, flashing a recovery using fastboot does not.
Click to expand...
Click to collapse
Use this app won't wipe data and can also reset tamper flag
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Sent from my Nexus 5 using XDA Free mobile app
31ken31 said:
Use this app won't wipe data and can also reset tamper flag
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Except you need root access to use that in the first place.
His bootloader is already unlocked.
That app is for those that already have root access, but want to relock and unlock the bootloader from within Android for possible security reasons.
Elluel said:
Except you need root access to use that in the first place.
His bootloader is already unlocked.
That app is for those that already have root access, but want to relock and unlock the bootloader from within Android for possible security reasons.
Click to expand...
Click to collapse
I used two apps to unlock and flash recovery. I'm trying to remember what the other was. My kid broke my laptop and I unlocked n rooted without a PC.
Sent from my Nexus 5 using XDA Free mobile app
31ken31 said:
I used two apps to unlock and flash recovery. I'm trying to remember what the other was. My kid broke my laptop and I unlocked n rooted without a PC.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Towelroot was used to gain root access via a kernel exploit. It has long since been patched and is now irrelevant. The only methods now require you unlock the bootloader.
Damn it, Elluel already told the OP what he needs to do.
Everybody else stop. You're causing more confusion by saying **** like "towelroot" or "cf auto root".
There's nothing simpler than flashing a custom recovery, and then the supersu flashable zip.
If OP needs to help to learn how to push a file to the device... that's has been answered in other threads a thousand times in this forum.
Hello Again,
Almost 3 months has passed and now my device on android 5.1
And again I have to root my device I found guide exatchly for me but somehow It didn't gone fine.
Guide : http://www.androidpit.com/how-to-root-nexus-5-on-android-lollipop
Well I even done CWM step, I was in CWM I did install SuperSU 2.46.zip and I did fix the root question.
But Root Checker says My Device isn't rooted. What is I'm doing wrong ?
@beekay201
@Elluel
Conixcit said:
Hello Again,
Almost 3 months has passed and now my device on android 5.1
And again I have to root my device I found guide exatchly for me but somehow It didn't gone fine.
Guide : http://www.androidpit.com/how-to-root-nexus-5-on-android-lollipop
Well I even done CWM step, I was in CWM I did install SuperSU 2.46.zip and I did fix the root question.
But Root Checker says My Device isn't rooted. What is I'm doing wrong ?
@beekay201
@Elluel
Click to expand...
Click to collapse
Tell you what, my hammerhead is still at 5.1 stock, non-rooted yet. In like 2 or 3 hrs I'll be home, and I'll write down the steps I'll use to root.
My question is: Is there any way that i can install any custom recovery now, when I am locked out of my phone, so I can try Method 7 from this post . I have enabled USB debugging, but for some reason, my device is unauthorized from executing adb commands.
I have Xiaomi Redmi Note 3, and have forgotten its password. I have tried Method 2, 5 and 6 from this post, but to no avail.
I tried method 2 and 5 which requires ADB to be installed, but I was not able to access my phone. I have USB debugging enabled and my phone is not rooted. When I tried to run the following code:
Code:
adb devices
adb shell
it showed that my phone is unauthorized and error: device unauthorized This adb server's $ADB_VENDOR_KEYS is not set
Here's the screenshot:
When trying method 6, I had to change the path of ADB driver because the file I downloaded from the post, had its own ADB driver which clashed with my already installed ADB driver, but even after that, it again showed the above error. Here' the screenshot:
Finally I want to try method 7 from the above post, which requires custom recovery to be installed on the phone, is there any way now?
Though it seems now that the I have only one option left and that is to factory reset my phone, but if , there is any other way by which I can bypass my lock screen, please please please inform me.
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
joe2k01 said:
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Didn't know that such package existed... I'd still do it my way if your phone was laggy/corrupted,... Else do the package flash. Keep me updated!
Sent from Lenovo a6000 1GB version.
Thanks! a lot, could you please guide me a little bit, how should I proceed?
MGlolenstine said:
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
dost25 said:
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
Click to expand...
Click to collapse
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Ok i will try
MGlolenstine said:
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Can unlocking my bootloader somehow brick my phone?
Everything can brick your phone. Updating my lenovo phone with official update hardbricked mine... But yeah, it can.