Won't root. Help please - Nexus S Q&A, Help & Troubleshooting

Hey. Got nexus s on rogers in Canada. Achieved unlock but that's as far as I get. I transfered the files to root but I think it was not the correct image. My about screen says build i54. If anyone can help I would really appreciate it. Thanks
Sent from my Nexus S using XDA App

check this thread >>>[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020/T only)
All credits go to AllGamer

rikardo1979 said:
check this thread >>>[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020/T only)
All credits go to AllGamer
Click to expand...
Click to collapse
Actually, that is wrong. The Nexus S he has is with Rogers, so it's a I9020a
This would be the proper guide:
http://forum.xda-developers.com/showthread.php?t=1007782

he didnt mentioned what model he has and Rogers mean nothing to me
Thanks for that m8
Matridom said:
Actually, that is wrong. The Nexus S he has is with Rogers, so it's a I9020a
This would be the proper guide:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse

Matridom said:
Actually, that is wrong. The Nexus S he has is with Rogers, so it's a I9020a
This would be the proper guide:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
ive followed all instructions and cannot get recovery to flash...i get error cannot load recovery.img. ive been searching the forum for hours looking for the answer and cannot find it..any help would be much appreciated.
thank you kindly

can u post steb by step what u do and how u do it ?
Cwest1 said:
ive followed all instructions and cannot get recovery to flash...i get error cannot load recovery.img. ive been searching the forum for hours looking for the answer and cannot find it..any help would be much appreciated.
thank you kindly
Click to expand...
Click to collapse

Cwest1 said:
ive followed all instructions and cannot get recovery to flash...i get error cannot load recovery.img. ive been searching the forum for hours looking for the answer and cannot find it..any help would be much appreciated.
thank you kindly
Click to expand...
Click to collapse
What is the exact command you typed?
Sent from my Nexus S using XDA App

Cwest1 said:
ive followed all instructions and cannot get recovery to flash...i get error cannot load recovery.img. ive been searching the forum for hours looking for the answer and cannot find it..any help would be much appreciated.
thank you kindly
Click to expand...
Click to collapse
The most common mistake is that you were in the wrong directory when you typed the command.
Let's assume you haven't edit the PATH environment variable, the easiest way is to copy the recovery image into the same directory as fastboot.exe. For example, in my laptop fastboot.exe is located in C:\android-sdk-windows\tools and my recovery image is named recovery.img, both files are in the same directory (C:\android-sdk-windows\tools).
Plug the phone in, reboot into bootloader mode, open the Command Prompt and issue the following command:
Code:
cd C:\android-sdk-windows\tools
fastboot flash recovery recovery.img
Please remember to change the directory in the cd command and recovery.img file name to the correct ones.

Related

Stuck on Mac root, please help

Ive unlocked the phone but when I try and boot recovery I keep getting this error message, cannot load 'recovery-clockwork-3.0.0.5-crespo.img'.
Any advice would be welcome. Sorry and thanks for being a noob. Rooted phones before but seem to be struggling with this one.
I just flashed the recovery instead of booting it, it gets overwritten if you don't change the relevant .sh file anyway.
Fastboot flash recovery <recovery.img>
Sent from my Nexus S using XDA App
did you try using this guide? http://forum.xda-developers.com/showthread.php?t=878446 if you did, try to flash the recovey.img again.
if you download the SDK from the guide, upgrade the recovery.img to the last one...
cuz i thing the code is 3.0.0.0 not 3.0.0.5
chikilin1389 said:
cuz i thing the code is 3.0.0.0 not 3.0.0.5
Click to expand...
Click to collapse
The code is the proper name for the file he's using. So if he's trying to flash 3.0.0.5, that's what he'd type...
OP - more details on what you're doing, step by step, might be helpful in solving your problem.

[Q] Sprint Nexus S 4g running 2.3.5 (can or can it not be rooted)?

I am looking for some input as if the Sprint Nexus S 4g running 2.3.5 can be rooted. I have rooted an EVO before (running an older version of android) but I am having tons of trouble rooting this phone. Any input would be greatly appreciated.
My Nexus S 4G is running stock 2.3.5, and is rooted. After the GRJ90 OTA, I had to re-install clockworkmod and reflash the su.zip, but with the bootloader unlocked, that's a pretty trivial task.
If you're starting with a brand-new NS4G, like, just bought it this morning and all that's happened is the 2.3.4 -> 2.3.5 OTA, then you'll need to start by unlocking the bootloader. Search is your friend; there are definitely full unlock/root guides here on XDA. If you're looking for an executive overview, the command is "fastboot oem unlock". Then it's just a matter of flashing clockworkmod or another appropriate recovery for this device (crespo4g, not plain crespo), followed by flashing a zip with the su binary and Superuser.apk. Don't forget to disable /etc/install-recovery.sh
assuming the phone is new the bootloader is probably locked? Either way would you be able to point me in the right direction?
Check the General section. You'll find a step by step guide.
Sent from my Nexus S 4G
I have tried this- http://forum.xda-developers.com/showthread.php?t=895545
When I get to step 2 the files are not in the directory, I then copied everything from "Platform tools" (I could be wrong in regards to the exact name of file) and placed into the android-sdk-windows\tools it does not find it and I can not proceed. Am I using the right process?
jgreene1014 said:
I am looking for some input as if the Sprint Nexus S 4g running 2.3.5 can be rooted. I have rooted an EVO before (running an older version of android) but I am having tons of trouble rooting this phone. Any input would be greatly appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1071500
everything you need.
you may need to rename install.recovery.sh in /etc to something else to prevent the stock recovery from being installed.
edit: if you need drivers and such, you can find them here...
http://forum.xda-developers.com/showthread.php?t=1088494
I was gunna ask the exact same question.. about to pick up my NS4G in an hour or so
jgreene1014 said:
I have tried this- http://forum.xda-developers.com/showthread.php?t=895545
When I get to step 2 the files are not in the directory, I then copied everything from "Platform tools" (I could be wrong in regards to the exact name of file) and placed into the android-sdk-windows\tools it does not find it and I can not proceed. Am I using the right process?
Click to expand...
Click to collapse
So you've downloaded the sdk and installed all the drivers for windows?
Sent from my Nexus S 4G
I chose this method http://forum.xda-developers.com/showthread.php?t=935819 Phone is now unlocked but when I get to step 2 number 19 it does not boot into clockwork a green droid with a caution sign in a triangle appears! I need help!!!
Thanks
I just rooted mine with the 1 click method found on the NS4G section. Didnt mattered it was running 2.3.5
jgreene1014 said:
I chose this method http://forum.xda-developers.com/showthread.php?t=935819 Phone is now unlocked but when I get to step 2 number 19 it does not boot into clockwork a green droid with a caution sign in a triangle appears! I need help!!!
Thanks
Click to expand...
Click to collapse
Prolly gotta unlock it, boot up, drag su zip to USB storage then boot into bootloader and flash clockwork. Immediately select the recovery option and flash su from cw. Reboot. Using root explorer or the like, rename install.recovery.sh to something else. Add a .bak to it. Reboot into bootloader and flash cw. Then it should stick. Easier and faster to do than typing this on my nexus.
I renamed the install.recovery.sh to recovery.img the first time around. Should I change to recovery.bak? I can now start my phone and I am showing the lock but when ever I go into recovery mode i get the droid with the caution sign in the triangle
jgreene1014 said:
I renamed the install.recovery.sh to recovery.img the first time around. Should I change to recovery.bak? I can now start my phone and I am showing the lock but when ever I go into recovery mode i get the droid with the caution sign in the triangle
Click to expand...
Click to collapse
If you follow my instructions directly, your recovery will stick.
Sent from my Nexus S 4G using XDA Premium App
Thanks A bunch!!!!! That did it all set with root!
jgreene1014 said:
Thanks A bunch!!!!! That did it all set with root!
Click to expand...
Click to collapse
No problem.
Sent from my Nexus S 4G via XDA Premium

Help for Root on VZWS3

Been trying to get root on a VZW S3
I have done the entire ODIN process, installed CWM and when I start the phone it has a unlock on the Samsung boot up screen. When I try to flash the rooted img zip file from CWM it just says failed, I tried several root zip files and can't seem to get it to work.
Can anyone point to what I'm doing wrong??
Thanks in advance!
Go to section two of droidstyle's guide and follow it to a T.
http://forum.xda-developers.com/showthread.php?t=1762709
Brian Gove said:
Go to section two of droidstyle's guide and follow it to a T.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
thank you brian, unfortunately i keep getting "adb is not a recognized internal or external command" in the setup
i have no idea where to go from here...any ideas
ptm88 said:
thank you brian, unfortunately i keep getting "adb is not a recognized internal or external command" in the setup
i have no idea where to go from here...any ideas
Click to expand...
Click to collapse
Try this then. Go to section 6 of his guide and follow those instructions using the "Rooted Stock VRALF2(Root66)" download. That's pretty much how you'd recover from a soft brick so it should work for you also.

Well, I'm a little stuck. Help?

Okay, so I decided to do something stupid and forget to backup my HTC One S while rooting. I installed CM10, and it got stuck in a bootloop, so stupid me decided to also do a factory reset and basically delete everything I needed to get out of it. I've tried numerous things, including ADB sideloading a ROM, but whenever I do that, it also gets stuck in a boot loop. I have no idea how to use RUU's, and if anybody could help me to fix my phone, that'd be really really helpful. I'm also kindof a n00b towards this stuff, so step-by-step instructions would be much appriciated Thanks.
~MuZiiX
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
CuzCrostyPwns said:
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
Click to expand...
Click to collapse
I think my device is s-off...i used the HTC One S all in one toolkit, and I have no idea what supercid is :s I've tried a couple RUU's before (don't know if i used them correctly, but i did relock the bootloader when i did it) but none of them helped. It just stayed at a black screen with "htc" in the middle. No error triangles or anything.
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
CuzCrostyPwns said:
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
Click to expand...
Click to collapse
Yeah, the RUU's were .exe's with my phone connected through USB. I can get into recovery, I have CWM installed.
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
CuzCrostyPwns said:
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
Click to expand...
Click to collapse
Well thats what I've been trying to do with the ADB sideloading, because it wont let me mount my sd card. It just says 'ERROR MOUNTING SD CARD" and when I've tryed flashing a new ROM from ADB sideloading, it just gets stuck in a bootloop again.
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
CuzCrostyPwns said:
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
Click to expand...
Click to collapse
I've tried running multiple RUU files, and I have no idea what one to use. The phone when I got it was unlocked, and the android version was ICS I'm pretty sure.
I dunno how to find my stock settings because I cant get past the loading screen.
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
did you flash boot.img? most of roms will bootloop without it
Roundtableprez said:
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
the boot.img is located in the zip you downloaded from get.cm
NQNH said:
the boot.img is located in the zip you downloaded from get.cm
Click to expand...
Click to collapse
So what command would I use while flashing the boot.IMG file? (again sorry for not getting this, I just wanna get my phone working again)
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Download or build from source
Download gapps
wipe unless you're upgrading from an earlier CM10 ROM
flash rom in recovery
flash gapps in recovery
unless you have s-off fastboot flash boot boot.img
Click to expand...
Click to collapse
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
dc211 said:
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
Click to expand...
Click to collapse
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
MuZiiX said:
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
Click to expand...
Click to collapse
It not really a big deal. Your problem is the most common one we see in Q&A. Also, once you finish flashing the boot.img keep in mind that CM10 can take a few minutes to boot the first time.
Also, just a heads up while the toolkits are helpful learning the command yourself actually lets do you a lot more things a lot faster.
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
CuzCrostyPwns said:
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
MuZiiX said:
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
Click to expand...
Click to collapse
Nope, just gotta do it one of the three ways mentioned. If debugging isn't enabled use option 1.
This can either be done via
1 powering off and keeping volume up & the power-button pressed
2 the extended power-menu (If your ROM has it, just select "reboot" & then "bootloader")
3 via adb, connect your phone with the pc, make sure it says "USB debugging connected", go to Android/platform-tools/ & then press shift while you perform a right click with the mouse, then choose "open prompt here", type
Click to expand...
Click to collapse

[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