Are there any mac detailed step by step guides of how to unlock and root the Nexus 5??
I've seen the 2 main threads here but they are step by step for windows and some of the coding has already been pointed out as wrong for the mac so I'm having a very hard time just unlocking and rooting my nexus 5 which is sitting here.
If anyone could please link me to a detailed MAC guide, I would very much appreciate it.
Thanks.
Willz said:
Are there any mac detailed step by step guides of how to unlock and root the Nexus 5??
I've seen the 2 main threads here but they are step by step for windows and some of the coding has already been pointed out as wrong for the mac so I'm having a very hard time just unlocking and rooting my nexus 5 which is sitting here.
If anyone could please link me to a detailed MAC guide, I would very much appreciate it.
Thanks.
Click to expand...
Click to collapse
I can help you out.
Download and install Android File Transfer, which will install the necessary drivers for your phone to connect to your computer. http://www.android.com/filetransfer/
Enable developer options on your phone by going to Settings > about phone and tapping the build number 7 or so times. Then go to the developer settings and enable USB debugging.
Once this is done, in your folder entitled your "username" in your Mac (the same folder that has Desktop, Documents, Downloads, etc.), create a folder titled Android.
Inside that Android folder, put these two files: http://cl.ly/SMwW and http://cl.ly/SMiC These are adb and fastboot.
Once that's done, open Terminal, type:
Code:
cd /Users/yourusername/Android
and hit enter.
Then type:
Code:
./adb devices
hit enter, and you should see your phone's serial number so long as you enabled USB debugging as described above.
Then type:
Code:
./adb reboot bootloader
hit enter, your phone will reboot to the bootloader
Download this file and place it inside the Android folder we created earlier: http://cl.ly/SMw9 This is the latest TWRP for our phones.
Into the same Terminal window, type:
Code:
./fastboot oem unlock
hit enter, WARNING: your phone will be returned to stock and your storage erased, once that's done, type
Code:
./fastboot reboot-bootloader
and hit enter to reboot back into the bootloader that is now unlocked.
Then to install TWRP, type:
Code:
./fastboot flash recovery openrecovery-twrp-2.6.3.2-hammerhead.img
and then reboot the bootloader again. I would then suggest hitting your down arrow a couple of times and booting into recovery, where TWRP will prompt you to root your device with SuperSU. Alternatively, here is the SuperSU zip that you can put onto your phone's storage and flash in TWRP. http://cl.ly/SMlk
Not sure if you missed it, but alternatively there's a Mac toolkit that's recently been posted.
http://forum.xda-developers.com/showthread.php?t=2515640
I do not want to root using a toolkit on my mac and I am trying to root on my macbook using this thread.
I keep on getting:
-bash: ./fastboot: Permission denied
after I type localhost: ./fastboot oem unlock in terminal
What's going on?
stelv said:
I do not want to root using a toolkit on my mac and I am trying to root on my macbook using this thread.
I keep on getting:
-bash: ./fastboot: Permission denied
after I type localhost: ./fastboot oem unlock in terminal
What's going on?
Click to expand...
Click to collapse
Are you cd'd into the directory where the fastboot binary is?
Also, here is a really good tutorial, Google ftw...
http://forum.xda-developers.com/showthread.php?t=1917237
0dBu said:
Are you cd'd into the directory where the fastboot binary is?
Also, here is a really good tutorial, Google ftw...
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Yes I am cd'd into directory and it recognizes my device until a reboot to bootloader. Then while in bootloader mode on my phone, terminal on my computer will no longer recognize my device.
I will take a look at the link though. Thank you. I dont have sdk setup on my computer, maybe thats it.
stelv said:
Yes I am cd'd into directory and it recognizes my device until a reboot to bootloader. Then while in bootloader mode on my phone, terminal on my computer will no longer recognize my device.
I will take a look at the link though. Thank you. I dont have sdk setup on my computer, maybe thats it.
Click to expand...
Click to collapse
When you're in bootloader and you type: fastboot devices what does it return?
0dBu said:
When you're in bootloader and you type: fastboot devices what does it return?
Click to expand...
Click to collapse
Its just blank after I type devices. Before I boot into bootloader though ./adb devices shows me my phones serial number
stelv said:
Its just blank after I type devices. Before I boot into bootloader though ./adb devices shows me my phones serial number
Click to expand...
Click to collapse
If adb devices shows your device you're in recovery, not bootloader
It doesn't show my device in boot loader though. Terminal says permission denied though. Maybe I'll try a different directory when I get back to my computer.
Sent from my Nexus 5
stelv said:
It doesn't show my device in boot loader though. Terminal says permission denied though. Maybe I'll try a different directory when I get back to my computer.
Sent from my Nexus 5
Click to expand...
Click to collapse
Use fastboot devices if you're in bootloader
Anyhow, the link I posted is a good tutorial, it should get you sorted. Although, even though I have ADB and Fastboot in my Path (ADB works fine), I still have to cd into the platform-tools directory to get fastboot to work. If anyone has some insight into that's I'd be all ears, but I still make it work.
Sent from my Nexus 5 using Tapatalk
Thanks guys. I got fastboot working, boot loader unlocked and twrp installed but I had to use the fastboot file from the other thread. The fastboot file in the second post this thread doesn't work correctly.
Now my next problem is I have twrp installed but it is asking me for a password and it will not backup my system. When I try to reboot I get bootloops. I can get back into fast boot though. Do I need to push a ROM file or superuser via fast boot? What is the command for that?
Sent from my Nexus 7
stelv said:
Thanks guys. I got fastboot working, boot loader unlocked and twrp installed but I had to use the fastboot file from the other thread. The fastboot file in the second post this thread doesn't work correctly.
Now my next problem is I have twrp installed but it is asking me for a password and it will not backup my system. When I try to reboot I get bootloops. I can get back into fast boot though. Do I need to push a ROM file or superuser via fast boot? What is the command for that?
Sent from my Nexus 7
Click to expand...
Click to collapse
That has happened to me also. I went ahead and flashed the factory image, and then re-flashed recovery after that and it worked fine.
Sent from my Nexus 5 using Tapatalk
0dBu said:
That has happened to me also. I went ahead and flashed the factory image, and then re-flashed recovery after that and it worked fine.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks. I saw a fix in the twrp thread as follows, so i did this. Twrp is working as normal now and no bootloops. I have the factory image downloaded too just in case. Thanks again! Everything seems to be working now.
Dees_Troy said:
If you have just used fastboot oem unlock, you should let the device boot up normally first before trying to install TWRP. If you boot TWRP first before booting normally, you will be prompted for a password. Hit cancel and got to Wipe -> Format Data. Type yes at the prompt and hit the "enter" key. Hit the home button at the bottom and Reboot -> Recovery. Unlocking the device will cause you to lose all userdata, apps, pictures, downloads, etc.
To root, when you select to reboot from the GUI in TWRP, you will be asked if you want to install SuperSU. Swiping to confirm will root your device.
Click to expand...
Click to collapse
Related
im using this method to root my nexus which i just bought today -- http://forum.xda-developers.com/showthread.php?t=1078213 --
and i download the files needed and i downloaded the terminal emulator from the market ( which is what i thought i needed to download) and typed in
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery recovery-clockwork-3.1.0.1-crespo4g.img
Click to expand...
Click to collapse
but it keeps saying adb: permission denied.
once i get passed the emulator im pretty good and can take care of the recovery stuff. i understand how to flash things and get booted up. just need a little help to get through the first step
fastboot oem unlock works?
try
fastboot boot recovery recovery.img
Joey_UFC said:
once i get passed the emulator...
Click to expand...
Click to collapse
No idea what you mean here, but the error above sounds like you forgot to enable USB debugging in the settings.
man, i guess you are doing it wrong... you should type these commands CMD (if you are in windows), not on the phone. Of course, it will give you "permission denied" because you don't have root yet...
rgds
http://forum.xda-developers.com/showthread.php?t=1096384
thanks for the replys guys, i'll show you what i have done so far ( seriously nothing lmao)
The link i posted in the OP is what i hope is to get rooted.
First i downloaded the grj stock rom and put it in the root of my sd card.
then i downloaded the Clockwork Recovery and put that in my sd card as well ( just in case)
and the 3rd step asks to open up the terminal, this is where i had trouble. I tried my cmd on my laptop while my phone is plugged in ( with usb debugging on) and pasted this command..
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery recovery-clockwork-3.1.0.1-crespo4g.img
Click to expand...
Click to collapse
and it says it does not recognize that command. so after a while of trying i realized the OP might of ment the terminal EMULATOR that you get from the market. and i tryed that and typed in the command again
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery recovery-clockwork-3.1.0.1-crespo4g.img
Click to expand...
Click to collapse
and the emulator says adb denied.
so that's where im at now. Its either the thread i posted is for people who are ALREADY rooted or that theres a different command for me to try.
i think i know whats wrong. my android sdk isn't installed correctly
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
Disclaimer: I am not responsible in any way if using anything I've made causes hard bricks,bootloops,alien abductions or any other problems.
Hey guys!
It's been some time that I've been seeing people having problems flashing the 2nd Bootloader and a custom recovery to the 2012 Kindle Fire HD 7". So,I decided to create this tool. May I present to you,
Flasher
By SafinWasi
This is a batch file which can flash the 2nd Bootloader and a custom recovery to the 2012 Kindle Fire HD 7",complete with ADB and Fast boot executables,stack override,disable auto-recovery update script as well as the 7.2.3 Bootloader downgrade to prevent red screens.
Working features:
Device verification through fastboot.
Flashing Freedom boot and TWRP/CWM Touch/CWM Stock (thanks r3pwn)
Downgrading the Bootloader to 7.2.3
Stack override
Disabling auto-update recovery script
Reboot into TWRP(optional)
Backing up boot,recovery and system partitions.
Restoring previously made backup
Click to expand...
Click to collapse
Steps to use:
Download the zip and extract it.
Read the ReadMe.txt carefully.
Install the Kindle Fire ADB drivers(if needed)
Run Flasher.bat as Administrator.
Follow the on-screen instructions.
Click to expand...
Click to collapse
Changelog:
[01/02/2014]Initial Release
[19/02/2014]Fixed a bug in the backup script
[17/03/2014]Added restore backup option
[24/06/2014]Added support for CWM Touch Advanced Edition and Stock CWM;updated TWRP to 2.7.0.0
Click to expand...
Click to collapse
Download link:
Link 1:flasher-v2-20140624-tate.rar - 31.23 MB
Link 2:flasher-v2-20140624-tate.rar
MD5 Checksum:84313f4b18008f63346853a8666523d5
Click to expand...
Click to collapse
Notes:
This tool is designed to work for Amazon OS version 7.4.6. So,using it on any other software might get you into a bootloop,but the recovery and Freedom-boot will work.Because of this,it is recommended to do the following things before using this tool:
Rooting the device.
Backing up any important data.
Placing the ROM and GApps zips on the sdcard in case you get a bootloop,so that you can just flash those in recovery after doing a complete wipe.
Preparing to lose the Amazon OS
Click to expand...
Click to collapse
Source:
https://github.com/SafinWasi/Flasher.git
Click to expand...
Click to collapse
Credits go to Hashcode,seokhun,BuQQzz,fattire,very green,r3pwn and anyone else whose work helped me.
Please hit the Thanks button if this tool helped you. Feel free to comment below to suggest any modifications,report any issues or for any help.
Thanks.
XDA:DevDB Information
Flasher, Tool/Utility for the Amazon 7" Kindle Fire HD
Contributors
Anonymous.123, SafinWasi
Version Information
Status: Beta
Beta Release Date: 2014-06-24
Created 2014-03-18
Last Updated 2014-07-01
Reserved
bump
Works as expected. Successfully flashed CyanogenMod and installed everything while being on Amazon's latest firmware.
One problem though, it doesn't get into fastboot when I connect the Kindle to the USB, I have to set it to fastboot mode manually via normal ADB method. Might be because I don't have a fastboot cable. Anyways, good work, really useful!
GMattZ said:
Works as expected. Successfully flashed CyanogenMod and installed everything while being on Amazon's latest firmware.
One problem though, it doesn't get into fastboot when I connect the Kindle to the USB, I have to set it to fastboot mode manually via normal ADB method. Might be because I don't have a fastboot cable. Anyways, good work, really useful!
Click to expand...
Click to collapse
Did you turn off the Kindle before connecting? Also,do you have the ADB drivers installed?
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Anonymous.123 said:
Did you turn off the Kindle before connecting? Also,do you have the ADB drivers installed?
Click to expand...
Click to collapse
I do have all the Fastboot and ADB drivers installed.
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
You might want to use this Bin4ry's Root Toolkit to root your Kindle. I've attached the link for you to download.
Root_with_Restore_by_Bin4ry_v33
As for fastboot, adb reboot-bootloader will not work. You'll need to issue this command:
adb shell
su
reboot bootloader
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
Well,you could use the Root with Restore by Bin4ry to root the device. But since you have OS version 7.4.8,you should keep the ROM and GApps zips on the sdcard since using my tool on any OS other than 7.4.6 might get into a bootloop.
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct.
The command you are looking for is (must be rooted to use this command with a USB cord otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
To root use Root Many Android. I recommend using v31 http://forum.xda-developers.com/showthread.php?t=1886460
LinearEquation said:
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct.
The command you are looking for is (must be rooted to use this command with a USB cord otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
To root use Root Many Android. I recommend using v31 http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
Thanks, I have no problem with the SDK and adb/fastboot environment, all that is working as should. It's just root that I need first which clearly I missed somewhere. Once I gain root I should be good to go. I'll try that root exploityou mentioned, (thanks for providing the version number) as the one found in this thread wasn't working. Then I'll fastboot flash back to 4.2 before attempting to install the 2nd bootloader. SHould be good to good. Thanks for your help.
FillTheVoid said:
Thanks, I have no problem with the SDK and adb/fastboot environment, all that is working as should. It's just root that I need first which clearly I missed somewhere. Once I gain root I should be good to go. I'll try that root exploityou mentioned, (thanks for providing the version number) as the one found in this thread wasn't working. Then I'll fastboot flash back to 4.2 before attempting to install the 2nd bootloader. SHould be good to good. Thanks for your help.
Click to expand...
Click to collapse
Well that was a nightmare. Because plugging my kindle in after the "fastboot -i 0x1949 getvar product" wouldn't boot into fastboot I had to issue the "adb shell su -c reboot bootloader" command myself. I then opened up the batch file for OP's flasher tool (thanks again) and entered the commands manually. I now have the second boot loader and TWRP and am Installing CM11. Thanks members of the Fire community for your help and patience and making this Fire usable.
FillTheVoid said:
Well that was a nightmare. Because plugging my kindle in after the "fastboot -i 0x1949 getvar product" wouldn't boot into fastboot I had to issue the "adb shell su -c reboot bootloader" command myself. I then opened up the batch file for OP's flasher tool (thanks again) and entered the commands manually. I now have the second boot loader and TWRP and am Installing CM11. Thanks members of the Fire community for your help and patience and making this Fire usable.
Click to expand...
Click to collapse
No problem bro.
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Bump
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
vampir4997 said:
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It should because it looks like it flashes the same files you would flash were you to do it manually complete with bootloader downgrade. You still want to rot first. Root Many Android v31 for that http://forum.xda-developers.com/showthread.php?t=1886460
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
vampir4997 said:
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Most probably it will work,but you can never be too careful. Be sure to make a backup by option 2.
Bump
Do i need to be in fastboot for this? Also what is the preffered root method for 7.4.8? Sorry kind of a noob with the kindle
Sent from my Nexus 5 using XDA Premium 4 mobile app
vampir4997 said:
Do i need to be in fastboot for this? Also what is the preffered root method for 7.4.8? Sorry kind of a noob with the kindle
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My tool will boot you into Fastboot. And the preferred (and probably only) root method for 7.4.8 is the Root with restore by Bin4ry v31. LinearEquation answered this question a while ago.
Ty,sorry guess i didnt read back far enough
Sent from my Nexus 5 using XDA Premium 4 mobile app
work in progress any help would be great. anything you do is at your own risk and possible may brick your phone or OS.
Ok this is a start of rooting this phone just like other carriers phone cricket z987 grand x max plus you need to install king root4.5 worked for me to get temp root. now this is not permenent and will cause phone to get buggy forcing a restart. what has worked with zte max, zte grand x max plus worked was after getting temp root you could install twrp 2.8.6.0 and installing superuser.zip from there gave gave perm root access but not full w/r access. now that does not work with this phone. phone boots into factory bootloader when trying to install twrp.
im looking into more option but as of right now I on a slow stand still till i can figure something out or someone else. feal free to help.
cgrimm9 said:
work in progress any help would be great. anything you do is at your own risk and possible may brick your phone or OS.
Ok this is a start of rooting this phone just like other carriers phone cricket z987 grand x max plus you need to install king root4.5 worked for me to get temp root. now this is not permenent and will cause phone to get buggy forcing a restart. what has worked with zte max, zte grand x max plus worked was after getting temp root you could install twrp 2.8.6.0 and installing superuser.zip from there gave gave perm root access but not full w/r access. now that does not work with this phone. phone boots into factory bootloader when trying to install twrp.
im looking into more option but as of right now I on a slow stand still till i can figure something out or someone else. feal free to help.
Click to expand...
Click to collapse
Please do I have people asking me if it's possible to root this phone and I said it could happen so fingers crossed
I tried and pretty much gave up. I can only gain temp root but its would be useful in small things like installing a recovery but there is non that works that I know of. I got titanium backup to back up my system but don't know if it will write if I format. Again any help from would be appreciated
Has any progress been made? I've been tinkering with this for days. Been pulling my hair out trying to dump the rom. If I can get the rom dumped I can attempt to port cwm over.
jimbog92 said:
Has any progress been made? I've been tinkering with this for days. Been pulling my hair out trying to dump the rom. If I can get the rom dumped I can attempt to port cwm over.
Click to expand...
Click to collapse
try this
stock system.img, boot.img, & recovery.img from someone who has not yet installed TWRP or supersu. To do this, install kingroot 4.5 and terminal emulator and run kingroot to get temp root. Then open terminal emulator and enter the following commands without the ""
"su"
"cd /dev/block/platform/7824900.sdhci/by-name"
"dd if=boot of=/sdcard/boot.img"
"dd if=recovery of=/sdcard/recovery.img"
"dd if=system of=/sdcard/system.img"
You will need to make sure you have at least 3GB of internal storage space before doing this just to be safe. The system.img will probably be about 1.5GB I did this and I got all three files saved to the root of my sd card. it would be easier for you do do this your self I am over my data cap so I cant upload the file
Last edited by cgrimm9; Today at 02:06 AM.
cgrimm9 said:
try this
stock system.img, boot.img, & recovery.img from someone who has not yet installed TWRP or supersu. To do this, install kingroot 4.5 and terminal emulator and run kingroot to get temp root. Then open terminal emulator and enter the following commands without the ""
"su"
"cd /dev/block/platform/7824900.sdhci/by-name"
"dd if=boot of=/sdcard/boot.img"
"dd if=recovery of=/sdcard/recovery.img"
"dd if=system of=/sdcard/system.img"
You will need to make sure you have at least 3GB of internal storage space before doing this just to be safe. The system.img will probably be about 1.5GB I did this and I got all three files saved to the root of my sd card. it would be easier for you do do this your self I am over my data cap so I cant upload the file
Last edited by cgrimm9; Today at 02:06 AM.
Click to expand...
Click to collapse
Ok, i got the first 2 to dump, now im guessing the system dump takes a while. where do they dump to exactly? and thanks for the help.
Ok, got all 3 to dump and found the files.. Now, have you made any progress in attempting to port a custom rom?
I'm to scared to brick my phone gf will kill me if I spend more money on a new phone. There is possibly a way to gain perm root but its risky you can look here
You do this at your own risk you brick your phone I will not beable to help restore.
jimbog92 said:
Ok, i got the first 2 to dump, now im guessing the system dump takes a while. where do they dump to exactly? and thanks for the help.
Ok, got all 3 to dump and found the files.. Now, have you made any progress in attempting to port a custom rom?
Click to expand...
Click to collapse
I may attempt that this weekend. But honestly, I am more worried about getting custom recovery and a custom rom installed.
Had there many any follow up on this phone? I would love to get cm12 or cm13 up and running.
I know its possible I don't think its gonna happen it only needs twrp to be tweaked to install in a different location but I don't see no support for this phone
dude, this phone is so easy to root. you dont need kingroot or any of that crap. you just need to know what your doing with adb. which you should know before you ever get into rooting. email zte support and request your boot loader unlock code. be sure to include you will need to provide them your phones serial number and imei. you willrecieve it in less than 24 hrs. open adb in comand terminal and type "adb devices". adb should return showing your devices serial number and device name. if it does you are good, if not make sure you have usb debugging enabled on your device. if your device does show up then type "adb reboot bootloader". your phone should reboot to the bootloader screen. to make sure this worked type "fastboot devices". Again your devices serial number and device should populate. Then type "fastboot oem unlock and the code you recieved from zte". adb will say "daemon started... time elapsed... write successful. i would download twrp 2.8.7.0. once you have that downloded move it to the same folder your adb is installed at and in adb type "fastboot flash recovery (recoveryname.img)".here again adb will say daemon started... time elapsed... write successful. now move supersu.apk (your super user app) to the root of your sd card. in adb type "fastboot reboot recovery" and your device will reboot into recovery. unplug your phone. on your phone in recovery select install zip. select your sd card. select your superuser apk. the swipe to install. once its done select reboot. bam your device is rooted with super user installed. a lot of times when you unlock your bootloader your device will factory reset so dont be surprised. do this all at your own risk
Hello
I would like to help out with this if ppl are still trying. I have experience with kernel building and etc etc but I need to know how to root my phone otherwise I can't dump boot imgs. To port over twrp or cwm. Also the source does not seem to be available so I would have to write a ton of code to do so. And also I noticed this post dates back to when the phone ran 4.4.4. I'm running 5.1.1 and that's another issue once rooted I can do it but we need more support.
Have any of you uploaded your boot, recovery and system image. Also have any of you managed root yet. I will be attempting to do so this weekend.
niisan518 said:
Have any of you uploaded your boot, recovery and system image. Also have any of you managed root yet. I will be attempting to do so this weekend.
Click to expand...
Click to collapse
Hello, I was wondering if you had any luck rooting. I also have the ZTE Lever running kit kat 4.4
kxhan15 said:
dude, this phone is so easy to root. you dont need kingroot or any of that crap. you just need to know what your doing with adb. which you should know before you ever get into rooting. email zte support and request your boot loader unlock code. be sure to include you will need to provide them your phones serial number and imei. you willrecieve it in less than 24 hrs. open adb in comand terminal and type "adb devices". adb should return showing your devices serial number and device name. if it does you are good, if not make sure you have usb debugging enabled on your device. if your device does show up then type "adb reboot bootloader". your phone should reboot to the bootloader screen. to make sure this worked type "fastboot devices". Again your devices serial number and device should populate. Then type "fastboot oem unlock and the code you recieved from zte". adb will say "daemon started... time elapsed... write successful. i would download twrp 2.8.7.0. once you have that downloded move it to the same folder your adb is installed at and in adb type "fastboot flash recovery (recoveryname.img)".here again adb will say daemon started... time elapsed... write successful. now move supersu.apk (your super user app) to the root of your sd card. in adb type "fastboot reboot recovery" and your device will reboot into recovery. unplug your phone. on your phone in recovery select install zip. select your sd card. select your superuser apk. the swipe to install. once its done select reboot. bam your device is rooted with super user installed. a lot of times when you unlock your bootloader your device will factory reset so dont be surprised. do this all at your own risk
Click to expand...
Click to collapse
Hello, I tried booting into bootloader but it didn't work, just does a normal reboot. It does recognize my phone though when I type adb devices. I contacted zte through email and by phone and they said they don't give those codes. Is the bootloader suppose to be unlocked already? Thank you.
Have you tried just typing "fastboot oem unlock" , or "fastboot oem bootloader unlock" without the unlock code? A lot of devices don't even need a code. Or if your bootloader is already factory unlocked, you could just skip to "fastboot flash recovery".
kxhan15 said:
Have you tried just typing "fastboot oem unlock" , or "fastboot oem bootloader unlock" without the unlock code? A lot of devices don't even need a code. Or if your bootloader is already factory unlocked, you could just skip to "fastboot flash recovery".
Click to expand...
Click to collapse
Hello again. Well I tried everything you mentioned. When I type adb devices it shows my device but when I type reboot bootloader it just does a normal reboot. Also when I type fastboot flash recovery with my img. file it just says waiting for device. Any suggestions. I really appreciate the help and your time.
dhplap said:
Hello again. Well I tried everything you mentioned. When I type adb devices it shows my device but when I type reboot bootloader it just does a normal reboot. Also when I type fastboot flash recovery with my img. file it just says waiting for device. Any suggestions. I really appreciate the help and your time.
Click to expand...
Click to collapse
Plug your device in and type adb devices once that is done type ADB reboot fastboot
kxhan15 said:
Plug your device in and type adb devices once that is done type ADB reboot fastboot
Click to expand...
Click to collapse
Thanks again. I tried that and it still just does a normal reboot.
dhplap said:
Thanks again. I tried that and it still just does a normal reboot.
Click to expand...
Click to collapse
from what I've researched the bootloader is locked and it's impossible to enter fastboot mode. Thank you very much for your help though.
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.