[Q] Nexus S I9020A: Has Anyone Successfully Rooted Device? - Nexus S Q&A, Help & Troubleshooting

I am at my wits end.
I have tried for the better part of a day to root my i9020A (Android 2.3.4, KD1, GRj22).
Has anyone successfully gained root?
If so, could you point me in the right direction.
PS. I will appreciate help from someone who has actually done this (I9020A).
Thanks.

Is your bootloader unlocked, if so then you have to flash clockwork recovery, by using fastboot mode through sdk android software, through your computure. You can get the recovery file and root file in general forum. In the general forum, there is a guide there as well and you can also go to youtube as well.

It's fairly simple - this applies to all of the versions of the Nexus S:
Boot into bootloader - fastboot oem unlock (this wipes)
Flash custom recovers
Mount /system
flash SU binary through recovery
On reboot the recovery will be overwritten with stock. To prevent this rename / delete /etc/install-recovery.sh

pterry30 said:
Is your bootloader unlocked, if so then you have to flash clockwork recovery, by using fastboot mode through sdk android software, through your computure. You can get the recovery file and root file in general forum. In the general forum, there is a guide there as well and you can also go to youtube as well.
Click to expand...
Click to collapse
My bootloader is locked.
I cannot get my device to recognize the USB drivers.
I tried both Android SDK & Samsung USB Mobile drivers

I had to use the junefabrics driver. Shabby has a one click that does most of it and provides the adb driver
Sent from my Nexus S 4G using XDA App

pterry30 said:
Is your bootloader unlocked, if so then you have to flash clockwork recovery, by using fastboot mode through sdk android software, through your computure. You can get the recovery file and root file in general forum. In the general forum, there is a guide there as well and you can also go to youtube as well.
Click to expand...
Click to collapse
aritafari said:
My bootloader is locked.
I cannot get my device to recognize the USB drivers.
I tried both Android SDK & Samsung USB Mobile drivers
Click to expand...
Click to collapse
Phew! Finally
I was able to unlock my bootloader (used pdanet).
If at first you don't succeed, try and try again.

pterry30 said:
Is your bootloader unlocked, if so then you have to flash clockwork recovery, by using fastboot mode through sdk android software, through your computure. You can get the recovery file and root file in general forum. In the general forum, there is a guide there as well and you can also go to youtube as well.
Click to expand...
Click to collapse
agree with pterry30

aritafari said:
Phew! Finally
I was able to unlock my bootloader (used pdanet).
If at first you don't succeed, try and try again.
Click to expand...
Click to collapse
Can you explain please...

Related

Problem with the ROM"Official OTA JB 4.1.1 for GSM Nexus S (CWM Flashable) + Extras"

Problem with the ROM"Official OTA JB 4.1.1 for GSM Nexus S (CWM Flashable) + Extras"
Hello, this is the first topic i write on XDA. I have a huge problem with the ROM called "Official OTA JB 4.1.1 for GSM Nexus S (CWM Flashable) + Extras" uploaded by kibmcz
I have made a mistake, i forgot to install the file for root and now i do not have root, i can not connect my nexus s with the computer and i can not get on my Clockworkmod recovery to change ROM. I don't know what to do. Please help me to change this ROM!
You should still be able to boot into the bootloader (vol up + pwr). You can then flash CWM again via fastboot.
chronophase1 said:
You should still be able to boot into the bootloader (vol up + pwr). You can then flash CWM again via fastboot.
Click to expand...
Click to collapse
How can i flash CWM via fastboot? Can you give me directions please?
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
You'll learn a lot more by reading up on it. It's worth your time. Seeing as you've unlocked your bootloader, this should be a cakewalk for you.
You'll learn a lot more by reading up on it. It's worth your time. Seeing as you've unlocked your bootloader, this should be a cakewalk for you.[/QUOTE]
Thanks a lot my friend, i hope that i won't have any problem to connect my nexus s with the PC because now i have due to this ROM..
Its not the roms fault. The point of a stock unmodified ROM is simple. To be a stock ROM unmodified ROM
You'll learn a lot more by reading up on it. It's worth your time. Seeing as you've unlocked your bootloader, this should be a cakewalk for you.[/QUOTE]
My friend i still can not connect my phone with the computer. So i can't follow these directions.
albundy2010 said:
Its not the roms fault. The point of a stock unmodified ROM is simple. To be a stock ROM unmodified ROM
Click to expand...
Click to collapse
But now unfortunately i can not connect my phone with the computer and flash recovery
error?
ironia. said:
error?
Click to expand...
Click to collapse
Yes..
christoscy said:
Yes..
Click to expand...
Click to collapse
And what error? That would be handy to know... if it's the lack of drivers just install PDAnet and follow the instructions, it will install the drivers for the Nexus S.
DeuXGod said:
And what error? That would be handy to know... if it's the lack of drivers just install PDAnet and follow the instructions, it will install the drivers for the Nexus S.
Click to expand...
Click to collapse
I have installed them but it still does not recognise my Nexus S. And it doesn't show me Android ADB Interface in device manager.
christoscy said:
I have installed them but it still does not recognise my Nexus S. And it doesn't show me Android ADB Interface in device manager.
Click to expand...
Click to collapse
With your phone up and running normally and android debugging on, go to cmd. type adb devices does it show? Just wondering.
jayjay3333 said:
With your phone up and running normally and android debugging on, go to cmd. type adb devices does it show? Just wondering.
Click to expand...
Click to collapse
No it doesn't show..

[Q] HTC One & Mini not recognized on pc in fastboot

Hi All
Now a proud owner of HTC One mini (uk) but am having issues trying to unlock bootloader, root and install custom rom.
for some reason my PC will not recognize my mini in fastboot mode . i have re installed the usb drivers and even tried to connect my wifes HTC one which i have previously rooted ...but it will not connect to either of the two.
I would be grateful if the community could offer a solution or advice, Thanks
oh forgot to say pc running windows 8.1
Edit: I found this http://forum.xda-developers.com/showthread.php?t=2588979 on the portal. it has ADB,FASTBOOT and DRIVERS needed . Not tried it myself as reverted to windows 7 however, many users confirming that it works on win 8 & 8.1.
I hope this helps, any thanks is given to the developer "Snoop05" as i am just posting the link.
cheers
Braddison said:
Hi All
Now a proud owner of HTC One mini (uk) but am having issues trying to unlock bootloader, root and install custom rom.
for some reason my PC will not recognize my mini in fastboot mode . i have re installed the usb drivers and even tried to connect my wifes HTC one which i have previously rooted ...but it will not connect to either of the two.
I would be grateful if the community could offer a solution or advice, Thanks
oh forgot to say pc running windows 8.1
Click to expand...
Click to collapse
same problem,change system to windows 7
thinkinbunny said:
same problem,change system to windows 7
Click to expand...
Click to collapse
Hi and thanks for the reply.
yeah ive had to used an old laptop running windows 7 and eventually unlocked bootloader. Now have an issue that adb is out of date! so still unable to root and install magioRom R3 :crying:
Braddison said:
Hi and thanks for the reply.
yeah ive had to used an old laptop running windows 7 and eventually unlocked bootloader. Now have an issue that adb is out of date! so still unable to root and install magioRom R3 :crying:
Click to expand...
Click to collapse
Search around to see if you can find a updated version? Let me explain to you how I did it. First, I unlocked my bootloader. Second, I downloaded the twrp and magiorom r3. Third hold shift and right click on the flashboot folder that you downloaded from htcdev and click on the open command window here. Rename you twrp to recovery. If your twrp file says img on it then try recovery.img, if not then type recovery. And on the cmd type flashboot flash recovery.img. Then you go back to bootloader and go to recovery and follow all the steps on the magiorom link. Don't forget to thank me. And btw, I didn't have to download any of those adb files. You root your phone when you have twrp. It'll ask you if you want to root. Say yes!!!!
abzboi said:
Search around to see if you can find a updated version? Let me explain to you how I did it. First, I unlocked my bootloader. Second, I downloaded the twrp and magiorom r3. Third hold shift and right click on the flashboot folder that you downloaded from htcdev and click on the open command window here. Rename you twrp to recovery. If your twrp file says img on it then try recovery.img, if not then type recovery. And on the cmd type flashboot flash recovery.img. Then you go back to bootloader and go to recovery and follow all the steps on the magiorom link. Don't forget to thank me. And btw, I didn't have to download any of those adb files. You root your phone when you have twrp. It'll ask you if you want to root. Say yes!!!!
Click to expand...
Click to collapse
should be:
fastboot flash recovery recovery.img
theodorius123 said:
should be:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thanks for that. I forgot about that. And I hope that it'll work for him.
abzboi said:
Search around to see if you can find a updated version? Let me explain to you how I did it. First, I unlocked my bootloader. Second, I downloaded the twrp and magiorom r3. Third hold shift and right click on the flashboot folder that you downloaded from htcdev and click on the open command window here. Rename you twrp to recovery. If your twrp file says img on it then try recovery.img, if not then type recovery. And on the cmd type flashboot flash recovery.img. Then you go back to bootloader and go to recovery and follow all the steps on the magiorom link. Don't forget to thank me. And btw, I didn't have to download any of those adb files. You root your phone when you have twrp. It'll ask you if you want to root. Say yes!!!!
Click to expand...
Click to collapse
Many thanks for your advice. I will try this later on.
btw the adb file is in the flashboot file downloaded from htcdec but have found a workaround that i will try
Braddison said:
Many thanks for your advice. I will try this later on.
btw the adb file is in the flashboot file downloaded from htcdec but have found a workaround that i will try
Click to expand...
Click to collapse
cool

Currently any chance to root 4.4.2?

Sorry if this is the wrong section. Please move if required.
I recieved my phone from the 9th. december batch, with 4.4.2. pre installed. I tried the root toolkit and the google sdk tool to root the device. I could unlock the phone, but thats it.
Unlock bootloader (which will wipe the phone). Then flash or fastboot into custom recovery, and flash the latest SuperSU (1.80 at the time of this post) zip file. There, now you are rooted.
rajendra82 said:
Unlock bootloader (which will wipe the phone). Then flash or fastboot into custom recovery, and flash the latest SuperSU (1.80 at the time of this post) zip file. There, now you are rooted.
Click to expand...
Click to collapse
First thing I did. SSU says there is no file and there is no way to install it. Please read the forum.
Don't use toolkits. Follow one of the guides like the one here: http://forum.xda-developers.com/showthread.php?t=2507905
I'm assuming you unlocked the phone with ADB/fastboot so you should be able to push and install custom recovery and flash SuperSU. You can't just download the SuperSU market app and expect it to install. You must flash it from recovery. After that it can be updated from the market but not installed from the market.
worked
usern ameisval idandnot said:
I get daemon started succesfully. error device not found
Click to expand...
Click to collapse
Check your drivers then. If the drivers are installed correctly and you have USB debugging on in the developer settings you will have access through adb.
Sent from my Nexus 5 using XDA Premium 4 mobile app
usern ameisval idandnot said:
I get daemon started succesfully. error device not found
Click to expand...
Click to collapse
Could be your drivers (but since you unlocked you should have the right drivers). Look up one of the driver troubleshooting threads. Make sure you don't see Android Device with a yellow (!) in your device manager. If you do, your drivers are missing. If you connect it and don't see anything at all in device manager see if you can uninstall whatever drivers you had and install the universal driver. There's lots of people who have had driver issues so search the forum.

[Q] Corrupt Recovery

Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
the exclamation point is the stock recovery. once you take in an ota, it removes both root and your custom recovery. to get your custom recovery back so that you can flash a bootloader(and the supersu root binaries). you can flash a custom recovery while youre in your bootloader via fastboot on your desktop.
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Yeah just realised that. Sorry its my first post
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
why don't you try twrp maybe you can flash twrp then remove the file then go back to cwm
Sent from my Nexus 5 using Tapatalk
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
luppas said:
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
Click to expand...
Click to collapse
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
simms22 said:
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
luppas said:
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
Click to expand...
Click to collapse
adb version and fastboot devices is different. adb is not fastboot and you can not use adb as fastboot. fastboot is fastboot.
simms22 said:
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
Click to expand...
Click to collapse
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
luppas said:
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
Click to expand...
Click to collapse
glad you got it

[Q] Root nexus 5 help!

OK in am new to this if I root my phone with one root brand or what ever it's called can I unroot with the same kind or something different
UnderstandFones said:
OK in am new to this if I root my phone with one root brand or what ever it's called can I unroot with the same kind or something different
Click to expand...
Click to collapse
Okay, to first learn what is root and what it entails, read this http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
Once you have understanding of what it is, there are other guides to help you with the different aspects of it and possibilities of what you can do with your phone. Refer to this http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
Sounds like someone who doesn't know what "root" actually is :/
Also wrong section, and read the stickies.
Google search is your friend.
Google " fastboot "&" adb " along with the word and # " Nexus 5 ".
If you read and understand than it is harder to brick your device
Nexus 5 rastakat 4.4.3 via Tapatalk app
fxdil said:
Okay, to first learn what is root and what it entails, read this http://forum.xda-developers.com/google-nexus-5/help/faq-to-android-read-post-root-t2508292
Once you have understanding of what it is, there are other guides to help you with the different aspects of it and possibilities of what you can do with your phone. Refer to this http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
Click to expand...
Click to collapse
I understand root sorry I didn't make that clear. However I have three question. #1 Do I root before I get a recovery?#2 Do need a computer to root?
UnderstandFones said:
I understand root sorry I didn't make that clear. However I have three question. #1 Do I root before I get a recovery?#2 Do need a computer to root?
Click to expand...
Click to collapse
You only posed two..
1. No. You need to unlock the bootloader first, from there you can install a custom recovery.
2. Highly recommended. There are tools nowadays that simplifies the process, but nothing works as best as doing it manually. You'll get to learn more, understand how your phone works, and it's much easier overall for the people at this forum to help you if you encounter a problem, if you understand the terms we use and how things are done.
Sent using Etch-a-Sketch.
fxdil said:
You only posed two..
1. No. You need to unlock the bootloader first, from there you can install a custom recovery.
2. Highly recommended. There are tools nowadays that simplifies the process, but nothing works as best as doing it manually. You'll get to learn more, understand how your phone works, and it's much easier overall for the people at this forum to help you if you encounter a problem, if you understand the terms we use and how things are done.
Sent using Etch-a-Sketch.
Click to expand...
Click to collapse
Sorry I also didn't mention I unlocked the bootloader yesterday
UnderstandFones said:
Sorry I also didn't mention I unlocked the bootloader yesterday
Click to expand...
Click to collapse
Did you unlock using adb?
Then you should be on your way to rooting. Remember to flash a custom recovery first, that's very important.
Sent using Etch-a-Sketch.
@UnderstandFones Read all the threads which I've linked in my signature. Please read them thoroughly as it seems that your basics are not yet cleared.
fxdil said:
Did you unlock using adb?
Then you should be on your way to rooting. Remember to flash a custom recovery first, that's very important.
Sent using Etch-a-Sketch.
Click to expand...
Click to collapse
I followed these directions I don't know if it used adb but I think I remember seeing it.
fxdil said:
Did you unlock using adb?
.
Click to expand...
Click to collapse
You can't unlock the bootloader using adb. It needs to be unlocked when the phone is in fastboot mode using a fastboot command.
UnderstandFones said:
I followed these directions I don't know if it used adb but I think I remember seeing it.
Click to expand...
Click to collapse
If you have already unlocked the bootloader, then download a recovery, extract the recovery.img file and then flash it via fastboot. All these steps can be accessed by following the thread linked in my signature.
vin4yak said:
You can't unlock the bootloader using adb. It needs to be unlocked when the phone is in fastboot mode using a fastboot command.
If you have already unlocked the bootloader, then download a recovery, extract the recovery.img file and then flash it via fastboot. All these steps can be accessed by following the thread linked in my signature.[/QUOTE
Where I am confused is when I download the recovery in this case twrp 2.7.1.1 and the superSU and put them in the android platform folder, do I then turn my phone off and fastboot mode and unzip the superSU in the platform folder?
Click to expand...
Click to collapse
vin4yak said:
You can't unlock the bootloader using adb. It needs to be unlocked when the phone is in fastboot mode using a fastboot command.
If you have already unlocked the bootloader, then download a recovery, extract the recovery.img file and then flash it via fastboot. All these steps can be accessed by following the thread linked in my signature.
Click to expand...
Click to collapse
I didn't tell him to unlock using adb did I? Merely pointing out to do it manually, he must have had to download adb to his computer, given that he's not even sure how he unlocked his bootloader.
UnderstandFones said:
Where I am confused is when I download the recovery in this case twrp 2.7.1.1 and the superSU and put them in the android platform folder, do I then turn my phone off and fastboot mode and unzip the superSU in the platform folder?
Click to expand...
Click to collapse
Will you please read the thread named "[GUIDE] Nexus 5 - How to Unlock Bootloader, Install Custom Recovery and Root" which is linked in my signature. Read it thoroughly and then post questions. Please get your basics cleared first.
Put the twrp img file in platform tools folder and then open a cmd window from there to run fastboot commands. Yes, you need to go into fastboot mode to run fastboot commands.
fxdil said:
I didn't tell him to unlock using adb did I? Merely pointing out to do it manually, he must have had to download adb to his computer, given that he's not even sure how he unlocked his bootloader.
Click to expand...
Click to collapse
Just for the sake of accuracy and to be pedantic, fastboot and adb are completely different. fastboot.exe and adb.exe do completely different things. All thats needed unlock the bootloader is fastboot.exe and USB drivers. This can all be done without downloading adb.exe
Sent from my Nexus 5 using Tapatalk
Where I am confused is when I download the recovery in this case twrp 2.7.1.1 and the superSU and put them in the android platform folder, do I then turn my phone off and fastboot mode and unzip the superSU in the platform folder?
Click to expand...
Click to collapse
Turn your phone off, boot into bootloader, then fastboot the recovery image.
Once done, reboot into your new custom recovery, use adb to push the superSU zip to your phone (do not unzip it, leave it as it is), use your custom recovery to locate to the zip, then install it.
fxdil said:
I didn't tell him to unlock using adb did I? Merely pointing out to do it manually, he must have had to download adb to his computer, given that he's not even sure how he unlocked his bootloader.
Click to expand...
Click to collapse
You said, "Did you unlock using adb? Then you should be on your way to rooting."
Anyone would interpret this as if your accepting that the bootloader is unlocked with adb. Which isn't correct. In any case, if that's not what you meant, my bad!
vin4yak said:
Will you please read the thread named "[GUIDE] Nexus 5 - How to Unlock Bootloader, Install Custom Recovery and Root" which is linked in my signature. Read it thoroughly and then post questions. Please get your basics cleared first.
Put the twrp img file in platform tools folder and then open a cmd window from there to run fastboot commands. Yes, you need to go into fastboot mode to run fastboot commands.
Click to expand...
Click to collapse
I am doing what you are telling me in your thread. when I open the command window and input the first code it say "the system cannot find the path specified" that the problem / what has been done fore this to say that?
UnderstandFones said:
I am doing what you are telling me in your thread. when I open the command window and input the first code it say "the system cannot find the path specified" that the problem / what has been done fore this to say that?
Click to expand...
Click to collapse
Post a screenshot please
Sent from my Nexus 5 using Tapatalk
UnderstandFones said:
I am doing what you are telling me in your thread. when I open the command window and input the first code it say "the system cannot find the path specified" that the problem / what has been done fore this to say that?
Click to expand...
Click to collapse
You get that error because the twrp file which you're trying to flash isn't in the platform tools folder.
Here are some things you need to check:
1. Have you navigated correctly to the twrp file path in fastboot?
2. Is the twrp file named correctly? if it's recovery.img then the command would be fastboot flash recovery recovery.img
3. Make sure you have file extensions seen in windows explorer so that you can confirm the file extension.

Categories

Resources