I'm trying to root my Nexus S 2.3.4 and so far I have unlocked it but when trying to flash Recovery Clockwork in the Command Prompt I get the error mesage "signature verification failed".
Any help would be appreciated.
XCarBoneX said:
I'm trying to root my Nexus S 2.3.4 and so far I have unlocked it but when trying to load Recovery Clockwork I get the error mesage "signature verification failed".
Any help would be appreciated.
Click to expand...
Click to collapse
How are you trying to flash your recovery?
krohnjw said:
How are you trying to flash your recovery?
Click to expand...
Click to collapse
I'm using [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020/T only)
http://forum.xda-developers.com/showthread.php?t=895545
XCarBoneX said:
I'm using [GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020/T only)
http://forum.xda-developers.com/showthread.php?t=895545
Click to expand...
Click to collapse
You're getting Signature verification failed using fastboot flash recovery filename.img?
If so ensure a few things - 1.) you've got the correct file name and 2.) you have a good download of the img.
Filename is correct and img seems OK.
Boot Nexus S into Recovery Mode with USB debugging on
Command prompt:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
error: cannot load 'recovery-clockwork-3.0.2.4-crespo.img
Win 7 64-bit SP1
Android 2.3.4 GRJ22 unlocked
Device Manager:
ADB Interface
Android Original ADB Interface
fastboot devices in Command shows:
33332EFE0C9300EC
XCarBoneX said:
Filename is correct and img seems OK.
Boot Nexus S into Recovery Mode with USB debugging on
Command prompt:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
error: cannot load 'recovery-clockwork-3.0.2.4-crespo.img
Win 7 64-bit SP1
Android 2.3.4 GRJ22 unlocked
Device Manager:
ADB Interface
Android Original ADB Interface
fastboot devices in Command shows:
33332EFE0C9300EC
Click to expand...
Click to collapse
The error message did not say anything about signature verification failed. The problem is fastboot cannot find the file you specify in the command line.
SOLUTION: you have to go into the folder that you saved the "recovery-clockwork-3.0.2.4-crespo.img" (for example, if you saved the file in C:\android\) using the following commands:
Code:
c:
cd android
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
I have already set Path variables in Windows for the Andriod tools folder which contains Fastboot and the Recovery image file.
Could the problem be with the Android driver or Android 2.3.4 GRJ22?
XCarBoneX said:
I have already set Path variables in Windows for the Andriod tools folder which contains Fastboot and the Recovery image file.
Could the problem be with the Android driver or Android 2.3.4 GRJ22?
Click to expand...
Click to collapse
No - Fastboot can't find the file.
c:\Downloads>fastboot flash recovery fakefile.img
error: cannot load 'fakefile.img'
This takes place before checking if your device is connected, if you are unlocked to write the recovery, etc.
You're sure the cwd of the cmd prompt is the directory you downloaded the file to? Alternatively provide the full path to the recovery image.
Edit: Rereading your post above you have the recovery file in the directory as the tools. This won't resolve via the path. You either need to cd into that dir or provide the full path. Fastboot takes a local img file as the argument (local to your cwd unless you specify the full path).
Got it!!
Firmly rooted in Mother Earth.
You were absolutely correct with the cd\ command.
Running Cyanogen 7.02
Thanks so much!!
To fix hanging on cyanogen screen:
Factory data reset
wipe cache
advanced
wipe dalvik
All's good in Roots Reggae land.
XCarBoneX said:
Not quite done yet.
On reboot it hangs on the cyanogen screen.
Click to expand...
Click to collapse
You can either try reflashing or hook it up via adb and run a logcat - it will show you what it's hanging on or waiting on. Unless it's stuck *very* early on you should be able to adb shell and then run logcat.
Same problem here - Fastboot repeatedly returns "error: cannot load recovery.img" when trying to load CWM
Tried this solution:
suksit said:
SOLUTION: you have to go into the folder that you saved the "recovery-clockwork-3.0.2.4-crespo.img" (for example, if you saved the file in C:\android\) using the following commands:
Code:
c:
cd android
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
Click to expand...
Click to collapse
but I get "The system cannot find the path specificed." when "cd android" is entered.
- ";C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools" is the path
EDIT: Fixed.
1) Moved .img file to root in C:
2) c:
3) cd\
4) fastboot flash recovery recovery.img
Got it finally.
Related
Im trying to get my new XOOM from unlock to root and having a nightmare!
I have read and followed guides from the forum but still can't get the new recovery on?
I have done fastboot oem unlock and followed the instructions on the tab and at the end it says complete. Next once it reboots enabled usb debugging and rebooted into bootloader, all ok so far but when I try to run the command "fastboot flash recovery recovery-tiamat-r4c-100611-1150-cwm.img" it comes up with "cannot load"? I have tried with and without the. img at the end and also renamed the file "recovery" and "recovery.img" and still the same thing.
Has anyone had this same problem and can get me back on track please.
Sent from my MZ604 using xda premium
(this not applicable for steady hawkins recovery)
if you have adb installed.
copy files from platform tools folder to "tools" folder.
put tiamat recovery image in tools folder.
rename recovery..tiamat as recovery(not recovery.img)
commands:
adb reboot bootloader
fastboot flash recovery recovery.img
Ok, will give it a try when I get to my computer and will report back.
Thank you
Sent from my Desire HD using xda premium
Our Indian cricket team is in your country desperately need a win
rohit3192 said:
(this not applicable for steady hawkins recovery)
if you have adb installed.
copy files from platform tools folder to "tools" folder.
put tiamat recovery image in tools folder.
rename recovery..tiamat as recovery(not recovery.img)
commands:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
nope that didnt work, same thing error: cannot load 'recovery.img
ok now im getting someware
still not working but when i do adb devices it says list of devices attached but nothing?
Just a note usb debbuging is on
Sent from my MZ604 using xda premium
rohit3192 said:
(this not applicable for steady hawkins recovery)
if you have adb installed.
copy files from platform tools folder to "tools" folder.
put tiamat recovery image in tools folder.
rename recovery..tiamat as recovery(not recovery.img)
commands:
adb reboot bootloader
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
First of all, it really doesn't matter if all your files that you need are in Tools or Platform tools, as long as they are all in there and your command window is operating out of that folder.
Second, you are making a good point re: the img file extension...in Windows, it sometimes is set to hide file extensions, so it is possible that someone could already have the img file extension there and not see it and add it again, making recovery.img.img which of course wouldn't work.
I don't think this is the OP's problem, but you never know.
I went ahead and did the oem unlock but when I try and flash the recovery (or boot) image through fastboot using this:
C:\androidsdk\tools\fastboot flash recovery XXXXXXX.img
or
C:\androidsdk\tools\fastboot flash boot rootboot.img
I keep getting this error:
error: cannot load 'XXXXXXX.img'
I've trouble shooted all of the main things. ...my device is definitely attached. I have the recovery .img file in the same folder as fastboot (along with the 2 needed .dll files). I've also done stuff like re-install usb drivers, re-install sdk, I've oem unlocked 3 times.
I have a stock wifi xoom with 3.2
Here are the 2 main root guides I've been using
http://forum.xda-developers.com/showthread.php?t=1170760&highlight=how+to+root
http://forum.xda-developers.com/showthread.php?t=1242241&highlight=how+to+root
Thank you for your help
in cmd(assuming windows) type cd c:/•••••tools
your xoom should be in adb reboot bootloader
type fastboot flash recovery recovery.img
rename recovery file as recovery.img and place in tools/platformtools as the case may be.
sending this message from stock xoom.
awesome, thanks. What you told me was enough to show me what I was doing wrong.
In case someone else reads this later on I had to type
cd C:\androidsdk\tools ...hit enter
then it looked like this
C:\androidsdk\tools> ...and I then typed
fastboot flash recovery XXXX.img
earlier I also renamed the folder to androidSDK from android-sdk
Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago
4SHR4F said:
Help Ive erased recovery and im not really experienced with fastboot I was trying to install clockworkmod and ended up deleting recovery please help ive got the kernal image from ASus but it is tar.gz please help im so confused I cant update or flash custom rom now its a nightmare just got this 2 or 3 days ago
Click to expand...
Click to collapse
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557
how did you delete recovery?
cyanogen mod forum has a good wiki on fastboot.
buhohitr said:
So I assumed that your device is unlocked? I recommend to flash twrp, more easier and works wellstart with section 2).
http://forum.xda-developers.com/showthread.php?p=32825557
Click to expand...
Click to collapse
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP
4SHR4F said:
I followed this thread before it says Scott's TF700T Recovery Install tool V1.0
www.scottsroms.com
Congrats! You now have a custom Recovery installed on the official
JB release by Asus!
From here you can install a custom ROM or simply root the stock ROM.
The choice is yours!
Thank you for using my Recovery Install Tool!
Please visit www.scottsroms.com!
Donations Greatly Appreciated but Never Expected!
But when I boot into recovery I get Un recoverable bootloader error (0x00000000)
Also when I used the program it does the first reboot but not the second I dont know why? Please HELP
Click to expand...
Click to collapse
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob
buhohitr said:
I don't think you did it correctly, first boot you should see the 4 icons and you need to hit the volume down button on your device (within 10sec) to select USB icon then hit the volume up button to select this setting, now proceed with the instruction on your pc to flash. Make sure you copy the recovery twrp file named" openrecovery-twrp-2.3.1.0-tf700t.blob" from here http://goo.im/devs/OpenRecovery/tf700t to the "install Recovery" folder and RENAME this file to recovery.blob
Click to expand...
Click to collapse
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error
4SHR4F said:
OK last time im trying this wish me luck
Edit: Same problem grrrrrr it says its sent hasnt reboot my device as well so have to do it manually and still says same error
Click to expand...
Click to collapse
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.
buhohitr said:
Sounds like your pc is not communicate correctly with your device. When your device is on and you execute Scott's bat file, is your device reboot into recovery so that you can select fastboot mode? Basically, Scott bat file is using adb command to reboot your device into recovery mode, you manually select and enable fast boot mode on your device, then the script is using fastboot command to push the recovery.blob (located in the same directory as Scott bat file) to your device.
Click to expand...
Click to collapse
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~
4SHR4F said:
Yes it reboots the first time allowing me to go into recovery but then doesnt reboot second after it writes the recovery files dont know why fastboot works thats why I can delete recovery but writing is a problem :~
Click to expand...
Click to collapse
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.
buhohitr said:
And you did select the USB icon and the text displayed "fastboot" on your device? You also have the twrp renamed to recovery.blob in the same folder as the script? Let manually push this file using fastboot.exe and see what's happens.
Click to expand...
Click to collapse
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it
4SHR4F said:
With fastboot same problem when I load from command prompt it sends the file however if I do it without starting from that directory it says file not found but fastboot devices show the number should I make a video and send it
Click to expand...
Click to collapse
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.
buhohitr said:
don't trust the log from fastboot or any script. Just make sure the recovery.blog is in the same directory of the fastboot command and you must execute fastboot.exe from command prompt.
1. manually boot to fastboot mode from your device. (boot to recovery then select USB icon)
2. Open command prompt and run as admin and navigate to fastboot.exe directory (with recovery.blog in this directory also)
3. type;
fastboot.exe -i 0x0B05 flash recovery recovery.blob
4. Once done, type
fastboot -i 0x0B05 reboot
Let me know the status.
Click to expand...
Click to collapse
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
H:\Users\Install user>
Also I would also like to point out it does not let me reboot after I write the files (using holding shift key and opening command prompt) as it freezes I think??? BEcause I can reboot from fastboot before I input writing flash recovery but after it wont allow don't know why?
4SHR4F said:
This is what I get recovery.blob is in the folder and fastboot works as I can delete recovery just not write for some reason
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
H:\Users\Install user>cd C:\Fastboot
H:\Users\Install user>fastboot devices
015d262e99141416 fastboot
H:\Users\Install user>fastboot.exe -i 0x0B05 flash recovery recovery.blob
error: cannot load 'recovery.blob': No error
Click to expand...
Click to collapse
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?
_that said:
Did you even notice that you didn't change to drive C: before calling fastboot? Is your recovery.blob in C:\Fastboot or in "H:\Users\Install user"?
Click to expand...
Click to collapse
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why
4SHR4F said:
Yes I know but my command prompt is awkward either way ive tried using Android flasher but I find the problem is my device freezes while writing files dont know why
Click to expand...
Click to collapse
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob
buhohitr said:
Try this, copy the recovery.blob to this directory:
H:\Users\Install user\
Then type dir then hit enter, make sure your fastboot.exe and recovery.blob are there
H:\Users\Install user> dir then hit enter
Should show both fastboot.exe and recovery.blob
Now execute the fastboot command to push the recovery.blob
Click to expand...
Click to collapse
Same problem says its sent and that it is written but after if I try to reboot the tablet doesn't respond and cant go into recovery because of that error 0x00000000
All I want to do is get UBuntu and Clean ROM on my Tablet then no more modding
OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please
4SHR4F said:
OK I give up with command prompt can I use Odin or some other software to flash recovery or at least flash a custom rom from windows rather then twrp or cwm boatloaders or can I get ubuntu and do it through ubuntu any possibilities helpful please
Click to expand...
Click to collapse
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.
buhohitr said:
Nope, no Odin, but if your device is rooted, you could download goomanager from the market and install twrp using goomanager app.
Click to expand...
Click to collapse
What about install linux without root and from there send in the recovery that way will that work
4SHR4F said:
What about install linux without root and from there send in the recovery that way will that work
Click to expand...
Click to collapse
You can be the first one to try...it may or may not works, but the methods I provided proved by many that they worked.
Hey Guys! Im a newbie so cut me some slack. I attempted to root my phone using Nexus Root Toolkit. I successfully unlocked the bootloader
But the root process would fail like sometimess when it restarts my nexus s then says its booting up but it wont ! So i take the usb out let it boot then when i try to continue it finishes but its not rooted. I get the Unlocked Bootloader thing at the bottom. Help?!!?
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Device:Nexus S GT-I9020a
JellyBean 4.1.2
BootLoader State:Unlocked
Rooted:No not successfully
Download superuser to usb, flash with Clockworkmod Recovery.
Stable Superuser ver 3.2 for Nexus S.
Check other superuser versions here
Follow this guide If you do not have Clockworkmod Recovery or want to learn step-by-step method; or simply download recovery-clockwork-5.0.2.0-crespo, unzip and flash with fastboot.
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
P/S: Install Android SDK Tools if you do not already have fastboot. Add Android SDK Platform Tools package via SDK Manager, and fastboot.exe is found in the following directory.
Code:
C:\Program Files\Android\android-sdk\platform-tools\
_android_ said:
Download superuser to usb, flash with Clockworkmod Recovery.
Stable Superuser ver 3.2 for Nexus S.
Check other superuser versions here
Follow this guide If you do not have Clockworkmod Recovery or want to learn step-by-step method; or simply download recovery-clockwork-5.0.2.0-crespo, unzip and flash with fastboot.
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
P/S: Install Android SDK Tools if you do not already have fastboot. Add Android SDK Platform Tools package via SDK Manager, and fastboot.exe is found in the following directory.
Code:
C:\Program Files\Android\android-sdk\platform-tools\
Click to expand...
Click to collapse
I tried to follow but the Img was down from MediaFire and My carrier is AT&T But im using a Telus sim
I had the same problem. I booted up and tried root dim and said I'm boot rooted.
I downloaded super-user from play store tried again and worked.
Hope this helps
Sent from my Nexus S using xda app-developers app
The link that I provided is the official recovery clockwork download link.
Superuser zip and Clockworkmod Recovery image work on Nexus S regardless of carrier and SIM.
Flash clockworkmod recovery via fastboot.
Download superuser zip to /sdcard and flash via clockworkmod recovery.
Joebizzle said:
I tried to follow but the Img was down from MediaFire and My carrier is AT&T But im using a Telus sim
Click to expand...
Click to collapse
Ok So I Unzipped it and what folder do i flash?
Joebizzle said:
Ok So I Unzipped it and what folder do i flash?
Click to expand...
Click to collapse
And can u dumb it down a little bit because Im really bad at this stuff ? Thanks
_android_ said:
The link that I provided is the official recovery clockwork download link.
Superuser zip and Clockworkmod Recovery image work on Nexus S regardless of carrier and SIM.
Flash clockworkmod recovery via fastboot.
Download superuser zip to /sdcard and flash via clockworkmod recovery.
Click to expand...
Click to collapse
This is kinda confusing can u use teamviewer and help me so you
can see my screen?
What stage are you in? Have you got clockworkmod-recovery installed?
I assume you are referring to superuser zip file. DO NOT unzip it, copy the zip file into your Nexus S sdcard, any folder.
Copy clockworkmod-recovery image file to C:\Program Files\Android\android-sdk\platform-tools\
1. Reboot into recovery: Power off, hold Vol-Up and long-press Power button. This should get you in FASTBOOT MODE
2. Flash clockworkmod recovery via fastboot: Go into Windows command prompt
Code:
cd C:\Program Files\Android\android-sdk\platform-tools\
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
3. Once fastboot is finished, choose "RECOVERY" option on FASTBOOT menu. That should put you in Clockworkmod Recovery menu.
4. Select "install zip from sdcard"->"choose zip from sdcard" and select the superuser zip file that you copied earlier.
5. Reboot and you should be rooted.
Hope this helps.
_android_ said:
What stage are you in? Have you got clockworkmod-recovery installed?
I assume you are referring to superuser zip file. DO NOT unzip it, copy the zip file into your Nexus S sdcard, any folder.
Copy clockworkmod-recovery image file to C:\Program Files\Android\android-sdk\platform-tools\
1. Reboot into recovery: Power off, hold Vol-Up and long-press Power button. This should get you in FASTBOOT MODE
2. Flash clockworkmod recovery via fastboot: Go into Windows command prompt
Code:
cd C:\Program Files\Android\android-sdk\platform-tools\
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
3. Once fastboot is finished, choose "RECOVERY" option on FASTBOOT menu. That should put you in Clockworkmod Recovery menu.
4. Select "install zip from sdcard"->"choose zip from sdcard" and select the superuser zip file that you copied earlier.
5. Reboot and you should be rooted.
Hope this helps.
Click to expand...
Click to collapse
OK
So it says sending recovery. But its just stuck on saying that and is it supposed to take long?
If you are on stock rom, clockworkmod recovery may be replaced by stock recovery upon each boot.
You can re-flash clockworkmod recovery each time you need it, or disable the recovery restoration. Search this forum for instruction on how to make recovery stick.
---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------
Joebizzle said:
I tried the whole Command prompt thing but it says tgings ling fastboot is not a command so thats whats getting me stuck.
Thats why i was asking if you use teamviewer so u can control my pc from ur pc. Because im confused in install/ flashing via fastboot
Click to expand...
Click to collapse
Have you got Android SDK-tools installed? Did you install the "Platform Tools" package via SDK manager? fastboot.exe is not installed by default. You may want to install USB driver too. See attached picture.
Test if fastboot is available and working: plug nexus s to pc:
Code:
cd C:\Program Files\Android\android-sdk\platform-tools\
fastboot devices
If usb driver is working, you should see some device id being displayed.
Joebizzle said:
OK
So it says sending recovery. But its just stuck on saying that and is it supposed to take long?
Click to expand...
Click to collapse
Bump.
Joebizzle said:
Bump.
Click to expand...
Click to collapse
Please see previous post #11 to test if fastboot/usb driver is working. Nexus S must be in FASTBOOT MODE.
Install Google USB driver package from SDK manager if necessary.
_android_ said:
If you are on stock rom, clockworkmod recovery may be replaced by stock recovery upon each boot.
You can re-flash clockworkmod recovery each time you need it, or disable the recovery restoration. Search this forum for instruction on how to make recovery stick.
---------- Post added at 03:14 PM ---------- Previous post was at 03:10 PM ----------
Have you got Android SDK-tools installed? Did you install the "Platform Tools" package via SDK manager? fastboot.exe is not installed by default. You may want to install USB driver too. See attached picture.
Test if fastboot is available and working: plug nexus s to pc:
Code:
cd C:\Program Files\Android\android-sdk\platform-tools\
fastboot devices
If usb driver is working, you should see some device id being displayed.
Click to expand...
Click to collapse
Im just stuck on sending recovery
Joebizzle said:
Im just stuck on sending recovery
Click to expand...
Click to collapse
see post #13
_android_ said:
What stage are you in? Have you got clockworkmod-recovery installed?
I assume you are referring to superuser zip file. DO NOT unzip it, copy the zip file into your Nexus S sdcard, any folder.
Copy clockworkmod-recovery image file to C:\Program Files\Android\android-sdk\platform-tools\
1. Reboot into recovery: Power off, hold Vol-Up and long-press Power button. This should get you in FASTBOOT MODE
2. Flash clockworkmod recovery via fastboot: Go into Windows command prompt
Code:
cd C:\Program Files\Android\android-sdk\platform-tools\
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
3. Once fastboot is finished, choose "RECOVERY" option on FASTBOOT menu. That should put you in Clockworkmod Recovery menu.
4. Select "install zip from sdcard"->"choose zip from sdcard" and select the superuser zip file that you copied earlier.
5. Reboot and you should be rooted.
Hope this helps.
Click to expand...
Click to collapse
It says file not found?
Joebizzle said:
It says file not found?
Click to expand...
Click to collapse
Please be more specific.
To run fastboot and adb from any windows directory, you can copy the following from C:\Program Files\Android\android-sdk\platform-tools to c:\windows\system32
Code:
fastboot.exe
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
_android_ said:
Please be more specific.
To run fastboot and adb from any windows directory, you can copy the following from C:\Program Files\Android\android-sdk\platform-tools to c:\windows\system32
Code:
fastboot.exe
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
Click to expand...
Click to collapse
I think i got fastboot and bootloader mixed up...lol
Joebizzle said:
I think i got fastboot and bootloader mixed up...lol
Click to expand...
Click to collapse
All done?
_android_ said:
All done?
Click to expand...
Click to collapse
still stuck D:
Why is this soooooo hard.!?!?!
Hello!
I'm stuck trying to flash TWRP into my devices and hoping now to maybe get some help figuring this out.
My devices is
LG Nexus 5, D821, Android 6.0.1
OnePlus 3T, A3003, OxygenOS 5.0, Android 8.0.0
I wanting to flah them both with TWRP Recovery, I've followed the tutorials for each phone from the links below
LG Nexus 5
https://forum.xda-developers.com/go...ide-nexus-5-how-to-unlock-bootloader-t2507905
OnePlus 3T
http://www.teamandroid.com/2017/02/24/install-oneplus-3t-twrp-3-0-3-recovery-complete-guide/2/
I have installed the android studio for my PC and downloaded the neccesary tools to make this work as "Android SDK Platform-Tools", "Android SDK Tools", "Google USB Driver". I have unlocked the bootloader on both phones and downloaded the latest TWRP.img file for each phone from
LG Nexus 5
https://eu.dl.twrp.me/hammerhead/
OnePlus 3T
https://eu.dl.twrp.me/oneplus3t/
I've located each file in the same directory as adb and fastboot. The problem for me now is when I'm in command prompt and typing the following command
"cd Desktop/android-sdk-windows/platform-tools/fastboot flash recovery recovery.img"
I get the following text
"error: cannot load 'recovery.img': No such file or directory"
I have tried to download older twrp files and also from other pages but the issue remians. And when I'm in windows and trying to open the .img file I get a window that says
"It is not possible to mount the file"
"The Disc Image file is corrupted"
How can I solve this issue? Please Help
I've located each file in the same directory as adb and fastboot.
Click to expand...
Click to collapse
You mean your recovery.img is placed in your platforms-tools folder?
If so, try providing the full path to the recovery image in your command, for example:
Code:
cd Desktop/android-sdk-windows/platform-tools/fastboot flash recovery Desktop/android-sdk-windows/platform-tools//recovery.img
Also, I believe you need to reboot into bootloader before flashing the recovery, if you aren't aware already.
unignostik said:
You mean your recovery.img is placed in your platforms-tools folder?
If so, try providing the full path to the recovery image in your command, for example:
Code:
cd Desktop/android-sdk-windows/platform-tools/fastboot flash recovery Desktop/android-sdk-windows/platform-tools//recovery.img
Also, I believe you need to reboot into bootloader before flashing the recovery, if you aren't aware already.
Click to expand...
Click to collapse
Thank you! It worked now
EmmanouilEk said:
Thank you! It worked now
Click to expand...
Click to collapse
good stuff :good: