Okay so here's my situation. I had to re-activate my device, and sprint told me I couldn't do it while on a custom ROM (I was on AOKP). So I flashed the Stock Deodexed rom that I still had on my SD for ICS thinking it would work. After flashing, my device wouldn't boot. So I put my phone in fastboot and used RSD to flash the 4.1.2 FXZ. After flashing, I got a FAIL error. Under status it says "Failed flashing process. Unknown fastboot command"
I searched everywhere and I'm coming up with blanks... yes my phone's bootloader is unlocked. Anyone know what I'm doing wrong?
xLoveHateLegend said:
Okay so here's my situation. I had to re-activate my device, and sprint told me I couldn't do it while on a custom ROM (I was on AOKP). So I flashed the Stock Deodexed rom that I still had on my SD for ICS thinking it would work. After flashing, my device wouldn't boot. So I put my phone in fastboot and used RSD to flash the 4.1.2 FXZ. After flashing, I got a FAIL error. Under status it says "Failed flashing process. Unknown fastboot command"
I searched everywhere and I'm coming up with blanks... yes my phone's bootloader is unlocked. Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
You need to delete the two getvar commands in the xml file.
<step operation="getvar" var="max-download-size" />
KitsunePaws said:
You need to delete the two getvar commands in the xml file.
Click to expand...
Click to collapse
I did that, then when trying to flash that, I got an error that said
"Error!!!!!!
Failed to create
Please check if the file path is too long to create or if there is enough free disk space."
xLoveHateLegend said:
I did that, then when trying to flash that, I got an error that said
"Error!!!!!!
Failed to create
Please check if the file path is too long to create or if there is enough free disk space."
Click to expand...
Click to collapse
Haven't seen that one, what did you use to edit the file with? What version of RSD?
Here's the one I used a few days ago for 4.1.2
http://www.sendspace.com/file/0nhnof
Replace your xml, reload RSD and try again.
KitsunePaws said:
Haven't seen that one, what did you use to edit the file with? What version of RSD?
Click to expand...
Click to collapse
I used notepad. Deleted the whole line (spaces infront of the command aswell) for both commands.
I'm using RSD Lite 6.1.5.
xLoveHateLegend said:
I used notepad. Deleted the whole line (spaces infront of the command aswell) for both commands.
I'm using RSD Lite 6.1.5.
Click to expand...
Click to collapse
We're using the same RSD, try the xml I posted.
Thanks, I'm giving that a try right now.
KitsunePaws said:
We're using the same RSD, try the xml I posted.
Click to expand...
Click to collapse
You might've just saved my ass, it's getting further than I was getting with the xml I edited myself. It's at the flash system.img part right now.
EDIT: My phone's booting up and Hands Free Activation is running. Thanks a ton!
So im having issues returning back to stock its failing at step 18/23 flash system img any ideas?
scuzzy19 said:
So im having issues returning back to stock its failing at step 18/23 flash system img any ideas?
Click to expand...
Click to collapse
Which version of RSD Lite are you using? I think 6.0 or even 6.1+ is required...
How long did you let it sit? Do you ever get an error?
arrrghhh said:
Which version of RSD Lite are you using? I think 6.0 or even 6.1+ is required...
How long did you let it sit? Do you ever get an error?
Click to expand...
Click to collapse
i grabbed one from a different source but dont remember where. i ended up getting it working through a different method using twrp. but i was up for awhile lol
you won't get this error with rsd 6.1.6
Related
Hey guys,
I'm brand new to the Nexus S but I'm not new to flashing/rooting etc. However I am having an issue here.
I successfully unlocked my bootloader today, and flashed CWM Recovery, rooted, and finally flashed CM7. I wanted to try Netarchy's kernel, so I installed Kernel Manager from the market and tried that way (been wanting to try out that app anyways). Well, I got an error, something about insufficient memory. The error message said I should reboot and try again.
So I rebooted.
Well now I am stuck in fastboot menu with "NO BOOT OR RECOVERY IMG" at the top of the screen.
So, I copied CWM recovery back into my AndroidSDK\Tools folder, and did
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
but I just keep getting
Code:
error: cannot load "recovery-clockwork-3.0.2.4-crespo.img"
I reinstalled drivers and tried again. Same error.
I double checked file name, tried renaming the recovery image file name, made sure it was in the same directory as fastboot.exe. If I do
Code:
fastboot devices
it DOES see my phone. I just can't get the recovery image to flash!
Can someone please help me???
Does your computer show the extensions of the files?
E.G. does fastboot appear as "fastboot" or "fastboot.exe" ?
And I'd recommend using 3.0.2.5 rather than 3.0.2.4. 3.0.2.4 is known to have bugs with it working. Your phone needs to be in bootloader mode in order for this command to work. http://forum.xda-developers.com/showthread.php?t=988686
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
matt2053 said:
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
Click to expand...
Click to collapse
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
zephiK said:
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
Click to expand...
Click to collapse
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Trying your link now.
matt2053 said:
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Click to expand...
Click to collapse
I personally flash kernels manually. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
zephiK said:
I personally flash kernels by myself. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
Click to expand...
Click to collapse
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
matt2053 said:
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
Click to expand...
Click to collapse
I just found it awkward that your phone said:
"NO BOOT OR RECOVERY IMG"
Click to expand...
Click to collapse
Let me know the results.
my bootloader appears as:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKB3
CARRIER INFO - TMB
SERIAL NUMBER - <removed>
LOCK STATE - UNLOCKED
and the navigational stuff
Click to expand...
Click to collapse
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
matt2053 said:
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
Click to expand...
Click to collapse
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
zephiK said:
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
Click to expand...
Click to collapse
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
matt2053 said:
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
Click to expand...
Click to collapse
if anything... if you have another system, you could try it on that system. you could also try it in another USB socket.
i mean, i dont think its your drivers but it doesnt hurt to see if it thats the problem.. your device was detected.
so your phone is unable to start up (get past google) and not able to get into recovery?
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
matt2053 said:
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
Click to expand...
Click to collapse
... WOW! i thought you knew that.
if you want the first command to work you have to do:
cd C:\android\tools\
fastboot flash recovery recovery.. blah blah blah
Click to expand...
Click to collapse
but congrats it was all you!
Yeah I must have had a brain fart. I obviously did it correctly earlier in the day when I flashed Clockwork originally. I was thinking the environment variable editing I did handled the need for the directory but I guess that's only for the command not the file.
Well, all is good now anyway!
Sent from my Nexus S using XDA App
How do i get back to a stock rom on this ? I got it rooted and Flashed to a rom, that could not connect via wifi or anything . when i got it. im looking for a some how way to get back to stock.
Ianonymous said:
How do i get back to a stock rom on this ? I got it rooted and Flashed to a rom, that could not connect via wifi or anything . when i got it. im looking for a some how way to get back to stock.
Click to expand...
Click to collapse
Well all the aftermarket ROM's usually state you should take a backup of your current state.
Since I'm guessing you didn't do that, FXZ back to stock. This will wipe EVERYTHING, including your internal SD card.
Ok so i downloaded the Sprint 4.1.2 Got the RSD LITE 6.0 Updated my Moto Drivers. And still it gives on status Failed Flashing process Unknown fastboot Command ( GetVar ) ...
Ianonymous said:
Ok so i downloaded the Sprint 4.1.2 Got the RSD LITE 6.0 Updated my Moto Drivers. And still it gives on status Failed Flashing process Unknown fastboot Command ( GetVar ) ...
Click to expand...
Click to collapse
Please see the 'NOTES' section of the OP in the FXZ thread...
Skrilax_CZ said:
you may have to open the zip and edit the xml, and delete the 2 lines "<step operation="getvar" var="max-download-size" />" if you get unknown command fastboot getvar max-download-size
Click to expand...
Click to collapse
OMFG Thank you so much . I defo owe you a beer or a coffee
Hey I have seriously screwed up my phone. I was having a random call issue and CSpire suggested doing a factory reset and reprogram. I was have TWRP on my photon so I decided to use it for the wipe. I chose to wipe system, thinking it would do a better job then just a factory reset. Well now I have no rom. Using twrp or cwmrecovery and neither will flash my backup or custom rom. Using rsd lite and trying to go back to stock and it fails at different points. First it failed to flash at step one giving an error about unknown fastboot command {getvar} so I did a search and found suggestions to delete those lines. I did then it failed top flash at {oem} so I did another search and found suggestions to delete those lines. So I did and now I am stuck at step 17/22 and I get a message flashing failed at 17/22 flashing system "system.img". I have been trying since yesterday with no luck. My battery is 100% at the moment. Can someone please point me in the right direction. The closest I have found to a solution was in the Atrix forum and it gave a manual step by step instruction but being new to this I do not understand it. It is found here http://forum.xda-developers.com/showthread.php?t=2110626
Any help would be greatly appreciated.
Are you trying to downgrade, or are you flashing the 4.1 JB FXZ?
arrrghhh said:
Are you trying to downgrade, or are you flashing the 4.1 JB FXZ?
Click to expand...
Click to collapse
I am flashing the 4.1 JB that I got from sbf.droid-developers. I got the one specifically for CSpire and not the one for Sprint.
lsufan72 said:
I am flashing the 4.1 JB that I got from sbf.droid-developers. I got the one specifically for CSpire and not the one for Sprint.
Click to expand...
Click to collapse
So if you let RSD sit, it eventually errors out on flashing the system.img?
arrrghhh said:
So if you let RSD sit, it eventually errors out on flashing the system.img?
Click to expand...
Click to collapse
Yes that is correct. Also, in RSD under device properties, it shows n/a by everything. Not sure if that is helpful or not.
Been content and happy with my Photon Q since tweaking it a little after getting it. Was still running the stock ROM, just with a few add ons. Also running one of the early TWRP releases.
Been battling a sd card corruption issue over the last few days, and after hours of testing and trial and error my next theory was that something on the ROM was corrupting my sd card (that's a completely different story/issue).
In any case, I rebooted the phone into recovery, made a full backup (system + data), wiped, then tried to restore a backup I had from about 3 months ago. The restore operation for system completes very quickly, but doesn't give any errors, and then when I go to reboot the device, TWRP warns there is no OS. Sure enough, there isn't. Using TWRP's file manager I can see there's nothing there. Rebooting just brings you to a boot logo screen, no further. I can get into fastboot and back into recovery. Thinking maybe something was wrong with my backups, I downloaded a clean stock TWRP image from a thread on here, same thing when I restore it. Thought maybe my recovery was jacked up, so I booted into fastboot and updated to the most current recovery, no change.
I'm pretty much DEAD at this point. Any thoughts, ideas, or suggestions?
Any help is greatly appreciated.
RSD Lite?
Otherwise restore one of the TWRP backups in the forums.
arrrghhh said:
RSD Lite?
Click to expand...
Click to collapse
Not totally familiar with it, but coming from a Samsung background, it's somewhat like Odin I believe. I'll look into it.
arrrghhh said:
Otherwise restore one of the TWRP backups in the forums.
Click to expand...
Click to collapse
Already tried two different ones, same result no matter what I try to restore. Doesn't work for some reason.
Ok, trying to flash using RSD Lite...
Using the "asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip" file downloaded from here: http://sbf.droid-developers.org/asanti_c/list.php
Edited the XML file to remove the two lines that say <step operation="getvar" var="max-download-size" />
When I try to flash, there are 23 steps, it keeps failing at step 18 (flashing the system.img). The exact error I get in RSD Lite is "Failed flashing process. 18/23 flash system "system.img" -> Phone returned FAIL."
Any thoughts?
Coucher said:
Ok, trying to flash using RSD Lite...
Using the "asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip" file downloaded from here: http://sbf.droid-developers.org/asanti_c/list.php
Edited the XML file to remove the two lines that say <step operation="getvar" var="max-download-size" />
When I try to flash, there are 23 steps, it keeps failing at step 18 (flashing the system.img). The exact error I get in RSD Lite is "Failed flashing process. 18/23 flash system "system.img" -> Phone returned FAIL."
Any thoughts?
Click to expand...
Click to collapse
There's another fellow with this same issue.
Not sure if they solved it yet, but does 'fastboot devices' work in a command prompt? Should show your device serial number in the terminal.
Just got it to work. I was using an older RSD Lite version (5.7). That image requires v6.1.5 in order to sucessfully flash the system.img
Worked fine with the newer RSD Lite version. Now to restore as much stuff as I can, but at least I'm back functional.
Thanks again for the heads up on RSD Lite.:good:
Coucher said:
Just got it to work. I was using an older RSD Lite version (5.7). That image requires v6.1.5 in order to sucessfully flash the system.img
Worked fine with the newer RSD Lite version. Now to restore as much stuff as I can, but at least I'm back functional.
Thanks again for the heads up on RSD Lite.:good:
Click to expand...
Click to collapse
Cool, I will mention this. Thanks.
I'm new to rooting and android in general. I'm currently running 4.4 rooted with stock I believe. Says ponury kernal in my settings.
I'm trying to flash the update for 4.4.2 via the TWRP install. I get a failed error: error executing updater binary in zip.
I've made sure my zip is the 4.4 to 4.4.2 but still no luck. Any ideas what I can do? Do I need to wipe something before I can put it on there?
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
tom1807 said:
On a first thought, you need to get back to the original kernel.
Update from 4.4.1 to .4.4.2. has no problems with different kernels installed, however this won't work from 4.4. to 4.4.2.
The exact error message would be also helpful
Click to expand...
Click to collapse
The error was : error executing updater binary in zip. I will look into getting back to stock.
matthewordie said:
The error was : error executing updater binary in zip. I will look into getting back to stock.
Click to expand...
Click to collapse
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
jd1639 said:
You need to fastboot flash the system and boot image from 4.4 if you have a custom kernel. Then flash the update
Click to expand...
Click to collapse
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
matthewordie said:
How do I fastboot flash the system and boot image? Can I do that from TWRP or do I need to use the command line with the fastboot? I have fastboot installed on my mac already. I was playing with that as well.
Click to expand...
Click to collapse
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
jd1639 said:
You'll need to get the factory image and extract the files. Inside there is another zip file which you'll need to extract. That's where you'll find the images. Use fastboot flash system system.img The Mac command is slightly different, I don't remember exactly what it is. To fastboot boot its the similar format
Click to expand...
Click to collapse
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
matthewordie said:
Is there a method of rooting or a specific kernal that will make it easier to update next time? I'd really hate to have to wipe everything every time there's an OTA update.
Click to expand...
Click to collapse
Flashing the system image won't wipe anything
http://forum.xda-developers.com/showthread.php?p=14
Sent from my Nexus 5 using Tapatalk
Zepius said:
then stop modding your phone if you want OTAs.
its really that simple.
just flash the 4.4.2 factory images.
Click to expand...
Click to collapse
Well I really don't know the exact steps involved in "flashing the image". That's what I'm asking.
jd1639 said:
Flashing the system image won't wipe anything
Click to expand...
Click to collapse
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
matthewordie said:
Then I guess I had the wrong impression of what flashing the image is. Is there a guide available?
Click to expand...
Click to collapse
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
jd1639 said:
Follow method#2. But only flash the system.img and boot.img. http://forum.xda-developers.com/showthread.php?p=47156064
Edit, your bootloader is unlocked, right? If not then you will lose all you data unlocking it
Click to expand...
Click to collapse
Ah, I was close I actually did method 1. Yeah I did leave it unlocked since i'm going to root again right away. Thanks