Database Info

Need little help with root

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

[Q] Stuck on Google logo. Unable to push image file to phone... Please help.

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

[Q] Fastboot and locking problems

hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?

Are you in the bootloader? (Phone off -> Vol. Up + Power -> fastboot oem lock).
Also, does the command "fastboot devices" show your device?

The USB connector socket at the phone might not make a proper contact with the USB plug. Make sure they connect properly. You may try another cable, or have a look at your USB socket and compare it to another. Check out particularly the little horizontal part in the USB socket.
Make sure you're in bootloader/fastboot mode before attempting to connect in fastboot. Fastboot cannot detect your phone, make sure your udev related settings are appropriate. Check on a Linux PC: https://source.android.com/source/initializing.html Configuring USB Access section.
If after this your phone will not be recognized by fastboot, please post the output of the following command (as root), after seconds after connecting the phone in fastboot mode:
Code:
tail /var/log/messages

Harbb said:
Are you in the bootloader? (Phone off -> Vol. Up + Power -> fastboot oem lock).
Also, does the command "fastboot devices" show your device?
Click to expand...
Click to collapse
fastboot does not show my device. I go into bootloader using adb reboot bootloader because my stupid power button wont work, thats why i want to sent it in to get fixed.

If drivers are properly installed this might not be working because the power button is stuck in or something. Not sure what to try to sort it out if that's the case.

mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
1 - Boot your phone into fastboot mode.
2 - open cmd in your pc.
3 - write: cd \"name of the file where your fastboot is in your pc", and then press enter.
4 - write: fastboot oem lock
5 - press enter and it's done!

bjuderas said:
1 - Boot your phone into fastboot mode.
2 - open cmd in your pc.
3 - write: cd \"name of the file where your fastboot is in your pc", and then press enter.
4 - write: fastboot oem lock
5 - press enter and it's done!
Click to expand...
Click to collapse
if you read the first post it says that fastboot doesnt work

mikeydubbs said:
if you read the first post it says that fastboot doesnt work
Click to expand...
Click to collapse
Sorry, didn't read it right!
And I'm sorry, but I don't know the solution for your problem!

have you tried using a different usb port on your pc?
sent from my dark iced, skanky, t11 infused ns4g

p1gp3n said:
have you tried using a different usb port on your pc?
sent from my dark iced, skanky, t11 infused ns4g
Click to expand...
Click to collapse
yeah i have and i tried using my laptop, and ubuntu 11.10
this sucks so much

i sent my phone in for a broken power button as well. I couldn't even get into the bootloader to relock it so i sent it with an unlocked bootloader. they still fixed it.

shahravi94 said:
i sent my phone in for a broken power button as well. I couldn't even get into the bootloader to relock it so i sent it with an unlocked bootloader. they still fixed it.
Click to expand...
Click to collapse
so do you think as long as its not rooted they wont care?

yup! i flashed a stock image so it was unrooted and sent it in. they fixed it up for me

If you are using Linux you might need su permissions!
Try:
sudo fastboot oem lock

mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Hi, I know this thread is old but I was having the same problem relocking my nexus 4 after installing stock Android 4.4.3 KitKat.
I'm using Nexus Root Toolkit, I don't know what tools you're using to lock your nexus S boblem ut this very easy to use it downloads the drivers and what ever you need to lock, unlock or flash stock and custom roms for any Nexus device.
So my problem was that I would launch OEM Lock on Nexus Root Toolkit and it would detect the device, reboot in Fastboot mode and it would proceed just fine but after saying "Launching TWRP.... something" it would reboot the phone and say to me "Waiting for device" untill it would time out.
I found out that when the program(NEXUS ROOT TOOLKIT) asked me to download a TWRP IMG files, I said no everytime because I didn't think I'd need it. So after trying 5 times, I allowed it to download it and i retryed to OEM Lock it and MAGIC!
Somewhere in the process of Locking the rom it is going to need the TWRP File so allowing the program to download it solved it for me.
I don't know if this will help you or if you still have the same phone, but if you do have use Nexus Root Toolkit and download all it asks and you'll be fine.
Good Luck.

"waiting for device" forever when "fastboot oem unlock:
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
I have the same exact problem.
ADB works fine when the phone is up & running, so I am suspecting a driver compatibility problem when the phone is in "FASTBOOT MODE".
I tried to install the "Universal Naked Driver 0.73 (Compatible with Nexus 5, 4, 7, 10 and S)" but Windows 7 64-bit refuses to pick it up. I use the Device Manager method which shows (when the phone is in "FASTBOOT MODE"):
Code:
"Other Devices
> Android 1.0"
When the phone is up & running, Device Manager shows it as:
Code:
"Android USB Devices
> SAMSUNG Android Composite ADB Interface"
Any idea how to proceed from here?
-----
Update: After a day went by, I searched Google some more and found a thread that describes exactly my problem:
http://forum.xda-developers.com/nexus-s/help/nexus-s-root-windows-requests-android-1-t878579
Which led me to:
http://forum.xda-developers.com/nex...oader-nexus-s-t875580/post9861928#post9861928
Which led me to:
http://pdanet.co/a/
I am rushing to try this now...
-------
Success!
~> fastboot oem unlock
...
OKAY [ 18.734s]
finished. total time: 18.734s
Click to expand...
Click to collapse

nunojpg said:
If you are using Linux you might need su permissions!
Try:
sudo fastboot oem lock
Click to expand...
Click to collapse
It helped. Thanks!

mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Well before trying to Relock the device see whether its connected or not. Type this command fastboot devices and hit enter see whether it shows some no. As in a reply if not that means the deivce isnt connected. If the device is connected type this command to relock your device fastboot oem lock and hit enter. Check on your device screen The Lock status will be changed to LOCKED.
If Helped Click Thanks
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
mikeydubbs said:
hey so i need to send my nexus s in for repair and i have stock rom and recovery, but every time i try fastboot oem lock it just sits at "waiting for device"
ADB works fine.
I tried alternative drivers
What can i do to re lock my phone?
Click to expand...
Click to collapse
Well before trying to Relock the device see whether its connected or not. Type this command fastboot devices and hit enter see whether it shows some no. As in a reply if not that means the deivce isnt connected. If the device is connected type this command to relock your device fastboot oem lock and hit enter. Check on your device screen The Lock status will be changed to LOCKED.
If Helped Click Thanks

help my phone is not recognized by adb

question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please

lileddy305 said:
question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please
Click to expand...
Click to collapse
you can go to bootloader right ...then no worries ..you are NOT BRICKED ...
i presume you got GB rom running ..so thats why after flashing the latest firmware ..your device is bootlooping ...
no worries
if you can go to bootloader ...connect the device to pc from there (phone reads fastboot usb after this)
and in adb folder ...open command window there and ..type this "fastboot devices" without quotes.it should show your device
(remember adb wont work ..when in bootloader only fastboot does)
now type this "fastboot getvar all"
and post the complete output here ...except IMEI and SERIALNO
I'll guide you further

Have you tried starting your phone and trying to get into your bootloader so you can run fastboot? or even make it into recovery to restore a back up or different rom? Make sure you have the most updated driver for your phone. You can also put your SD card in another phone or in your computer and put the firmware version on the root of your card, put it in your phone, run your hboot and let it update by itself. Between these two options you should be able to resolve your problem.
Or because I posted like 5 seconds after the guy above... Do what he ^ said

ganeshp said:
you can go to bootloader right ...then no worries ..you are NOT BRICKED ...
i presume you got GB rom running ..so thats why after flashing the latest firmware ..your device is bootlooping ...
no worries
if you can go to bootloader ...connect the device to pc from there (phone reads fastboot usb after this)
and in adb folder ...open command window there and ..type this "fastboot devices" without quotes.it should show your device
(remember adb wont work ..when in bootloader only fastboot does)
now type this "fastboot getvar all"
and post the complete output here ...except IMEI and SERIALNO
I'll guide you further
Click to expand...
Click to collapse
hi, i did as you said but when i type adb devices it just goes blank. i get no device recognized but yea i am able to get to the bootloader

lileddy305 said:
hi, i did as you said but when i type adb devices it just goes blank. i get no device recognized but yea i am able to get to the bootloader
Click to expand...
Click to collapse
read my post again ..did i said adb devices ??? NO i said fastboot devices ..that too this needs to be done with phone in bootloader connected to pc

ganeshp said:
read my post again ..did i said adb devices ??? NO i said fastboot devices ..that too this needs to be done with phone in bootloader connected to pc
Click to expand...
Click to collapse
oh ok sorry i read wrong, ima do that right now.
btw when this works you better have a donate button lol
thank you so much for your help

ganeshp said:
you can go to bootloader right ...then no worries ..you are NOT BRICKED ...
i presume you got GB rom running ..so thats why after flashing the latest firmware ..your device is bootlooping ...
no worries
if you can go to bootloader ...connect the device to pc from there (phone reads fastboot usb after this)
and in adb folder ...open command window there and ..type this "fastboot devices" without quotes.it should show your device
(remember adb wont work ..when in bootloader only fastboot does)
now type this "fastboot getvar all"
and post the complete output here ...except IMEI and SERIALNO
I'll guide you further
Click to expand...
Click to collapse
ok so here are the results that i got

ok i understand your situation completely
you need to flash the 3.32 unlocked firmware
then you need to flash 4EXT recovery
then you need to go to recovery and then flahs the ROM
in order to do that ...this is the perfect guide
FLASH 3.32 FW and ROM
follow the post#1 and post #2 to the letter
then at the end you will come out fine
if you got any problems ..you can post back here ..I'll help you (or simply click the IRC HELP CHANNEL present in my signature and join that ..I'll be online there )
Also donation is not really required a simple thanks to my posts are enough ..but if you do feel like donating ..its much appreciated

[Q] Nexus 5 power button doesn't work anymore

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!