Related
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
Hi,
I need to make an unROOT and I cannot find original stock ROM for my 9023i Nexus S. I went through a lot of threads but there is no original ROM. I need to send it to servis and use warranty - so I probably need 2.3.3. I tried look for in out of xda and downloaded something that has 4MB - it does not work.
Please, if you have it, send me a link. Thank you!
forum.xda-developers.com/showthread.php?t=1063664
for unrot use youtube and google..
once you flash stock rom for your device with link from post above this one it will unroot and give you stock recovery
sean1984 said:
once you flash stock rom for your device with link from post above this one it will unroot and give you stock recovery
Click to expand...
Click to collapse
I read this. But what happend was, that I flashed it and the lock was opened at start - and when I got into the system, there were a lot of canceled processes and I couldnt continue Now I probably need to root it again (I hope it will work) but I dont know what to flash
EDIT: Great. I cannot get into system so I cannot enable debugging, - so I cannot root it again and eve get into system AND there is no recovery Only thing I can do is to connect USB cable and open disk in PC
Is there any way to push from bootloader recovery through adb???
Why would you flash 2.3.3 ? leting your device "officially" update to 2.3.6 or even ICS (if you're I9020T) isn't a guilt lol ..... Anything official and a locked bootloader , unrooted would be fine for warranty purposes ...
mahanddeem said:
Why would you flash 2.3.3 ? leting your device "officially" update to 2.3.6 or even ICS (if you're I9020T) isn't a guilt lol ..... Anything official and a locked bootloader , unrooted would be fine for warranty purposes ...
Click to expand...
Click to collapse
Never mind. I managed to get there 2.3.4. When the device comes back I root it again so no need to update right now.... anyway, I cannot relock it it does not have to be locked?
EDIT: I'd rather had it locked, just in case.... but I cannot relock it. I tried to use sdk, write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English)
devcager said:
Never mind. I managed to get there 2.3.4. When the device comes back I root it again so no need to update right now.... anyway, I cannot relock it it does not have to be locked?
EDIT: I'd rather had it locked, just in case.... but I cannot relock it. I tried to use sdk, write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English)
Click to expand...
Click to collapse
While you're in fastboot mode and connected to your PC , run "fastboot oem lock" .... This should lock it unless you're having another issue ...
mahanddeem said:
While you're in fastboot mode and connected to your PC , run "fastboot oem lock" .... This should lock it unless you're having another issue ...
Click to expand...
Click to collapse
"run fastboot oem lock" means to put it in a command line? Because it does not work. Or it is a program??
devcager said:
"run fastboot oem lock" means to put it in a command line? Because it does not work. Or it is a program??
Click to expand...
Click to collapse
it means you go into your command prompt , guide your way to where you put your sdk tools with the fastboot command, and then run the command from there.
so basicly start > run > cmd , and from there find go to your directory where you placed your android sdk tools.
kwaidan said:
it means you go into your command prompt , guide your way to where you put your sdk tools with the fastboot command, and then run the command from there.
so basicly start > run > cmd , and from there find go to your directory where you placed your android sdk tools.
Click to expand...
Click to collapse
I do exactly this... It does not work. when in command prompt I put "cd android-sdk-windows" and get there. then I put "fastboot oem lock" and it tells what I wrote in previous posts :/
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
Hi everybody,
So, there is my problem, I bought the nexus 5 in November. I rooted it.
And the last wednesday, while using my phone, the power button decided to not respond anymore.
The phone still worked but two days ago the batery became empty and now I can just go in the "bootloader menu" and the "download mode".
Google accepted to replace my phone, but I really want to save my files. And like you certainly know we can't save our files with the phone Off.
But my phone is detected in this two modes.
I installed the nexus driver but I still can't open my files.
I pretty sure there is a way to save my files, I searching and trying but nothing work, I would open my phone if I can activate the power button manually but I don't know how.
If you have any solution, I'll take it.
Per-haps the ADB can help me ? But I don't know how to use it.
Thanks a lot for reading.
Have a good day !
Ps : I'm new here please be gentle if I don't understand directly
And sorry for my poor english.
PeauMorte said:
Hi everybody,
So, there is my problem, I bought the nexus 5 in November. I rooted it.
And the last wednesday, while using my phone, the power button decided to not respond anymore.
The phone still worked but two days ago the batery became empty and now I can just go in the "bootloader menu" and the "download mode".
Google accepted to replace my phone, but I really want to save my files. And like you certainly know we can't save our files with the phone Off.
But my phone is detected in this two modes.
I installed the nexus driver but I still can't open my files.
I pretty sure there is a way to save my files, I searching and trying but nothing work, I would open my phone if I can activate the power button manually but I don't know how.
If you have any solution, I'll take it.
Per-haps the ADB can help me ? But I don't know how to use it.
Thanks a lot for reading.
Have a good day !
Ps : I'm new here please be gentle if I don't understand directly
And sorry for my poor english.
Click to expand...
Click to collapse
Hoping you have enabled the usb debugging you can indeed backup through adb: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
Can you enter into recovery mode from the bootloader menu?
Primokorn said:
Hopping you have enabled the usb debugging you can indeed backup through adb: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
Can you enter into recovery mode from the bootloader menu?
Click to expand...
Click to collapse
The usb debugging is enabled I hope too, I'll try it immediatly, thanks you.
But I can't enter in any thing in that menu.
PeauMorte said:
The usb debugging is enabled I hope too, I'll try it immediatly, thanks you.
But I can't enter in any thing in that menu.
Click to expand...
Click to collapse
You can use a fastboot command to boot into recovery: fastboot boot path/to/TWRP.img if you have TWRP Recovery.
Then you will be able use to use adb commands to backup your data.
Primokorn said:
You can use a fastboot command to boot into recovery: fastboot boot path/to/TWRP.img if you have TWRP Recovery.
Then you will be able use to use adb commands to backup your data.
Click to expand...
Click to collapse
Hmm, Have I to start eclipse ? Where can I find the "sdk platform" ?
I found a folder who have that name but nothing happens when I run the exe files.
And in eclipse nothing had that name.
Edit : Sorry I did'nt understand before. I'm trying your command in this folder, but it say me that there is no such files in this directory. Could you explain me ?
Edit 2 : Okay I have to read better i guess, I don't have TWRP, I'm downloading it, could you just explain me a little how does it work ?
Edit 3 : With the command "adb devices" I can't see my phone :/ Have I to surrender ?
PeauMorte said:
Hmm, Have I to start eclipse ? Where can I find the "sdk platform" ?
I found a folder who have that name but nothing happens when I run the exe files.
And in eclipse nothing had that name.
Edit : Sorry I did'nt understand before. I'm trying your command in this folder, but it say me that there is no such files in this directory. Could you explain me ?
Edit 2 : Okay I have to read better i guess, I don't have TWRP, I'm downloading it, could you just explain me a little how does it work ?
Edit 3 : With the command "adb devices" I can't see my phone :/ Have I to surrender ?
Click to expand...
Click to collapse
1. First off, you have to install and set up adb & fastboot on your PC. Here is a great tutorial: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
However you can use this tool instead: http://forum.xda-developers.com/showthread.php?t=2588979
2. To boot into recovery mode from bootloader, connect your phone to PC then enter this command into cmd:
fastboot devices (check if your N5 is connected otherwise)
fastboot boot path/to/TWRP.img (you can download the latest TWRP img from this website)
Primokorn said:
1. First off, you have to install and set up adb & fastboot on your PC. Here is a great tutorial: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
However you can use this tool instead: http://forum.xda-developers.com/showthread.php?t=2588979
2. To boot into recovery mode from bootloader, connect your phone to PC then enter this command into cmd:
fastboot devices (check if your N5 is connected otherwise)
fastboot boot path/to/TWRP.img (you can download the latest TWRP img from this website)
Click to expand...
Click to collapse
With the two methods, no devices are found. But when I try with an other phone, nothing is dected too (debug mod enabled).
I tried to remove driver and update with all sources but nothing apparently work per-haps my debug mode is disabled ? ...
Edit :
Okay fastboot device detected my phone !
The guaranty will stop if I use the second command ?
And last thing, where I need to put the img ?
Thanks a lot I looking at the end of that problem *o*
PeauMorte said:
With the two methods, no devices are found. But when I try with an other phone, nothing is dected too (debug mod enabled).
I tried to remove driver and update with all sources but nothing apparently work per-haps my debug mode is disabled ? ...
Edit :
Okay fastboot device detected my phone !
The guaranty will stop if I use the second command ?
Click to expand...
Click to collapse
Nope because you only BOOT and not FLASH TWRP.img. Actually I say TWRP because I have this recovery but I think you can use this command with the stock recovery. You just have to use recovery.img file from the factory images instead of TWRP.img.
---------- Post added at 02:30 PM ---------- Previous post was at 02:30 PM ----------
PeauMorte said:
And last thing, where I need to put the img ?
Thanks a lot I looking at the end of that problem *o*
Click to expand...
Click to collapse
Put the file into your platform-tools folder (where you have fastboot.exe file)
Primokorn said:
Nope because you only BOOT and not FLASH TWRP.img. Actually I say TWRP because I have this recovery but I think you can use this command with the stock recovery. You just have to use recovery.img file from the factory images instead of TWRP.img.
---------- Post added at 02:30 PM ---------- Previous post was at 02:30 PM ----------
Put the file into your platform-tools folder (where you have fastboot.exe file)
Click to expand...
Click to collapse
Okay, nice !
But I put the twrp.img in the adb folder, but it doeasn't found the file, where i need to put it ?
path/to means what ?
PeauMorte said:
Okay, nice !
But I put the twrp.img in the adb folder, but it doeasn't found the file, where i need to put it ?
path/to means what ?
Click to expand...
Click to collapse
Did you rename the downloaded file to "TWRP.img"? The file name must be the same into your command prompt.
Copy TWRP.img into your platform-tools folder then open a command prompt from this folder and enter: fastboot boot TWRP.img
The path is the directory of your file you want to use. If you open the command prompt from the folder you have TWRP.img (platform-tools) then you don't need to mention the path.
I think the bootloader needs to be unlocked first for "fastboot boot twrp.img" to work? Isn't it? If unlocking wasn't necessary, everyone would've just booted recoveries to root their phones. (so that the sdcard doesn't get erased).
I sincerely doubt that the OP has an unlocked bootloader.
vin4yak said:
I think the bootloader needs to be unlocked first for "fastboot boot twrp.img" to work? Isn't it? If unlocking wasn't necessary, everyone would've just booted recoveries to root their phones. (so that the sdcard doesn't get erased).
I sincerely doubt that the OP has an unlocked bootloader.
Click to expand...
Click to collapse
Actually I never tried fastboot boot command on a locked bootloader. If it requires an unlocked bootloader and OP has a locked one I have no idea to recover his data.
Primokorn said:
Actually I never tried fastboot boot command on a locked bootloader. If it requires an unlocked bootloader and OP has a locked one I have no idea to recover his data.
Click to expand...
Click to collapse
Please guy ! You're a genius !
I love you !
I just used the reboot comand and my phone goes On !
Now I can back up my files
(Ps : For the people who'll have the same problem, you have to use your charger with you're computer and keep pressing the volume down while putting the charger in the phone to go in boot menu, but be carfully, you can't shutdown after that only solution, remove batery !)
:fingers-crossed:
PeauMorte said:
Please guy ! You're a genius !
I love you !
I just used the reboot comand and my phone goes On !
Now I can back up my files
(Ps : For the people who'll have the same problem, you have to use your charger with you're computer and keep pressing the volume down while putting the charger in the phone to go in boot menu, but be carfully, you can't shutdown after that only solution, remove batery !)
:fingers-crossed:
Click to expand...
Click to collapse
Happy for you... and your data
Primokorn said:
Happy for you... and your data
Click to expand...
Click to collapse
I'll just ask a last question because you're a super user of twrp, the back up fonctionality could work if I use it on this phone and the put it in my new nexus sent by google ?
Thanks a lot again and have a good day, you made mine.
PeauMorte said:
I'll just ask a last question because you're a super user of twrp, the back up fonctionality could work if I use it on this phone and the put it in my new nexus sent by google ?
Thanks a lot again and have a good day, you made mine.
Click to expand...
Click to collapse
Yes, you can! Just make sure you don't restore the /efs partition which contains the imei and other files which are unique to every device!
- Sent from an IceCold Hammerhead!
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.