Related
I installed the new zen2.2 rom today and had a working clockwork recovery. Here is where I went stupid, I downloaded the kernel update but rather than running it via update.zip I flashed it using flash_image recovery via adb shell.
Now my phone comes up to fastboot usb and never goes any further, been waiting hours! I have tried booting into fastboot/hboot and it does nothing. I have booted to hboot before successfully but now nothing.
If I run adb devices it shows no devices. If I run fastboot devices it does show my device.
Whats next?
If you cant get into fastboot and you cant get into recovery then you m ight have bricked your phone. Did you try a hard reset?
How do you do a hard reset?
Here is a little more info. I believe it does actually get to fastboot usb as it says so on the top left of the screen and I can run fastboot commands but most commands say error. If I do fastboot devices it shows the device connected.
Little more info - when I try doing a back to basics RUU update it connects, shows the rom version, starts the update and then at about 88% every time, it goes right to a error [171] usb connection error. So its communicating but never finishes. Tried with the sprint RUU stock rom, another that was built by one of the devs in the Hero community and still both do the same.
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
ASimmons said:
I'm pretty sure you can flash a custom recovery from fastboot. Using something like fastboot flash xxx dont quote me on this but it sounds like you have a soft brick and you just need to get a recovery back on the phone. From there you can then flash and rom back on the phone. Do some research on flash a recovery from fastboot.
Click to expand...
Click to collapse
Right, I also believe that if I could get a recovery back on the phone I would be good as gold! Here is the problem though. I have tried running "fastboot flash recovery [recovery.img]" but it gives me the below error. I have tried multiple key combination's to get into hboot but nothing works. If anyone has any other key combination's I could try please let me know!
Code:
D:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (3720 KB)... FAILED (remote: not allow)
finished. total time: 0.001s
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
Yeah I think he knows now not to flash kernels... atleast I hope so. +1 for your post.
unCoRrUpTeD said:
1st:The ONLY time you use flash_image recovery is when you are installing a recovery console, NOT a kernel
If you notice the kernel is in a signed .zip folder. When you use flash_image command it needs to be .img file
2nd: Put the recovery image on your sdcard
Put it in the tools folder of AndroidSDK and do
Code:
adb push recovery.img /sdcard
Click to expand...
Click to collapse
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
Now type in
Code:
$ adb shell
$ su
# flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
casualonejp said:
I am fully aware of how the how-to's and what not to do's. Like I said, it was a mistake, call it a bit of anxiety due to the new 2.2 rom that I was trying to get installed. I did it too quick and without much common sense .
For the second part, I am unable to do anything with adb as my computer does not see the phone. When running adb devices it is not listed. Only command that sees my phone is fastboot devices, but again I am unable to run anything aside from that due to previous error.
Click to expand...
Click to collapse
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
edit: sorry i dont think fastboot will see the sdcard but try anyways.
ASimmons said:
First do you have the eng spl, does your hoot say s (on)
Have you tried that command but point it to the sdcard? Also do you have any files on your sdcard like say a recovery.img or an update zip. If you don't you might need to manually move the file to it and try some of these commands
fastboot update /sdcard/<imagepackage>.zip [-w] -w will wipe the cache and the user/data
or your previous flash recovery but with the file pointing to the file on the sdcard
Click to expand...
Click to collapse
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
casualonejp said:
I will try the fastboot command right now. I am unable to get to hboot with any of the key combination I have tried, before I was able to. Only thing that always comes up is the HTC white screen with fastboot usb at the top left. Can't see what hboot version or anything else I have due to that limitation.
Click to expand...
Click to collapse
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.img
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
ASimmons said:
After reading a bit you should be able to do something like i described
- copy amon_ra image to yor sd
- flash_image recovery /sdcard/name-of-recovery.img
hopefully you have a way to copy the files to your sd card like say a microsd card converter and stick it in your comp. Or I have had to use a freaking camera once for my g1 after being in a similar situation.
edit: ok so maybe you wont be able to if you spl is in s-off mode.
if you can access your card and see if you have nadroids you could also try this
fastboot flash system /path/to/nandroid/system.fimg
fastboot flash boot /path/to/nandroid/boot.img
fastboot flash userdata /path/to/nandroid/userdata.img
fastboot reboot
hopefully you have these backed up on your puter to.
Click to expand...
Click to collapse
Negative on the fastboot commands. Also did have a nandroid but on old sdcard which died. I read that I could use anothers nandroid backup but I am currently trying to find one to test.
Tried doing the RUU method with stock/custom roms and it gets as far as seeing the image but when I click on "ok" to start the recovery, it goes to "waiting on bootloader" and then at 88% it errors to a 171 error stating usb connection error.
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
ASimmons said:
I would do some research its my understanding that you can't be bricked since you can get into spl. You should be able to put an .img file on your sd card and flash it. Sorry I can give you any more input.
Click to expand...
Click to collapse
Ya I have been researching non stop all yesterday evening and today so far all day. I just cant get it to do anything. I will keep researching though. Thanks
Did you fix this yet?
Anyone figure this out yet...I have the same issue and haven't been able to resolve it yet. Still with a brick at this point!
Hey guys,if your stuck at fastboot(As I just was tonight), try in your CMD(if running Windows) fastboot reboot-bootloader or fastboot reboot to reboot as normal,I'll try to keep you updated to get through all this. I am at a loss right now but searching for answers first before i go about asking.
Answer to MY problem(maybe not yours): OK,I have come to the conclusion here tonight that I had a soft brick. What I did was remove the battery,put the battery back in,restarted the phone normally,then I ran the HTC Sprint Hero MR 2.27.651.6 on my computer(essentially restoring back to unrooted factory settings). This worked for me. I am totally refreshed and happy that my phone is ok and all. Yes I may have to go back and re-root but this only take me bout 20 minutes most to root and re-flash a CyanMod7 Nightly Rom. Hope my info can help out somebody!
We are trying to solve how to make our own fastboot system.img files from dd the system partition on a phone. If we can get a stock, 5.5.959, system.img that has never been mounted read/write, then we should be able to compare it to a fastboot system.img and figure out the exact difference. We already have a start of an idea, but it has to be perfect.
By virgin, no OTA patches, and no mounting read/write. You do have to root the phone, but on the temporary root. Put busybox in /data/tmp or somewhere. Next chmod 755 /data/tmp/busybox . Then do something like /data/tmp/busybox dd if=/dev/block/system of=/data/tmp/system.img . Finally copy /data/tmp/system.img off the phone and post it in this thread, please.
Busybox
We already have this file.
You have had it for days, in fact. You converted it to system.tar.gz for me.
Source: erismaster
Satisfies all of your requirements -- 5.5.959 (not OTA!), Verizon, temp ADB root, never mounting /system, dd with those arguments.
psouza4 said:
We already have this file.
You have had it for days, in fact. You converted it to system.tar.gz for me.
Source: erismaster
Satisfies all of your requirements -- 5.5.959 (not OTA!), Verizon, temp ADB root, never mounting /system, dd with those arguments.
Click to expand...
Click to collapse
Is there anyways to get my hands on this? My phone is purely in fastboot mode only and have no other real options to me, so if i could somehow flash this via fastboot, it may actually solve my issue.
(I cant even get into recovery)
edru said:
Is there anyways to get my hands on this? My phone is purely in fastboot mode only and have no other real options to me, so if i could somehow flash this via fastboot, it may actually solve my issue.
(I cant even get into recovery)
Click to expand...
Click to collapse
http://www.megaupload.com/?d=N2FPWHE6
I tried a fastboot flash of this system.img and it gave me a crc check failure.
You can't flash it, it's not signed. It's only useful for development.
Sent from my DROID3 using XDA App
Thanks very much!
No worries about finding a system.img that hasn't ever been mounted . . . we now have "Like a Virgin" images for repeated re-mounting and her pleasure.
Location please?
Wolfhere said:
Location please?
Click to expand...
Click to collapse
the thread is on the main page . . . . http://www.necrotania.com/Download/swu.zip
Hi I have an LG Optimus 2x SU660 and I am having a problem on upgrading it.
It don't have a adb boot-loader so I can flash IMG files to it.
Is there a guide so I can flash IMG files using nvflash? Or some one who know how to do it.
Thanks.
It is possible to use fastboot, but it's more awkward than other phones.
The thing with NVFlash is you need to be sure of your partition layout, NVFlash uses a number to identify which partition to write the .img too, if you don't know what the numbers are, you'll have some difficulty.
Thank you. I am also unable to access the fastboot.
I think its because I used LG-P993 rom that is compatible with SU660.
Never heard of the P993 before, but looked it up and it appears to be another variant of the Optimus 2X. Great, that'll confuse people.
To use fastboot you have to wipe your boot partition, if you have to ask, then I don't recommend it.
What might be best is if you can get someone to make a NAND backup of a stock SU660 and then you restore it.
Can you still get into (custom) recovery? If so then I don't see why you couldn't DD the image files, you can get the partition layout from /etc/recovery.fstab
I am now stuck again on fastboot. any fix can you recommend?
Oh bloody hell, what have you gone and done?
If (as I'm assuming) you've got into fastboot, then the best thing you can do is get a recovery.img and use: fastboot boot recovery.img, at which point you can flash something.
Did fastboot flash recovery c:/recovery.img but still it won't boot.
Don't worry because I can return it to its original state by flashing the old nvflash rom.
Of course it wont boot, you've wiped your boot partition remember
You will now have to tell it to boot from something, so as above, try: fastboot boot c:\recovery.img and you should be in recovery. Now from there you can flash a .zip (which will replace your missing boot partition) or restore a backup.
OR
If you have the right bootimage handy, you can use fastboot boot c:\boot.img and the phone will fire up, after that you need to use DD to permantly install the boot image you booted.
That you do from ADB shell or the terminal: dd if=/sdcard/boot.img of=/dev/block/mmcblk0pX (where X is the boot partition)
what is dd?
---------- Post added at 06:43 PM ---------- Previous post was at 06:42 PM ----------
Sir may i requrest for your YM id?
If I knew what a YM ID was I'd tell you lol
dd is basically a *nix copy command, did you not use it to wipe the boot partition?
Yahoo Messenger Id.
No sir.
Oooh there's something I've not used in a while!
[email protected]
Can I just erase from settings to restore to default?
Sent from my XT1058 using XDA Premium 4 mobile app
our best bet is probably to follow this guide here...
http://forum.xda-developers.com/showthread.php?t=2446515
Or maybe easier would be just to...
fastboot flash system <nameofsystemfilehere>.img
I would have to double check my last bit of advice though.
Newbie help
is there anyway to do this without deleting my stuff. Sorry im a newbie at this. i orginialy installed the first root moto app and it had a unroot option. the new one doesnt and i really need to get back to stock without doing anything complicated
MarcusSi1516 said:
is there anyway to do this without deleting my stuff. Sorry im a newbie at this. i orginialy installed the first root moto app and it had a unroot option. the new one doesnt and i really need to get back to stock without doing anything complicated
Click to expand...
Click to collapse
Well...
fastbooting the system should not delete your user data. and its not really complicated.
Do you have ADB set up on your computer?
i think so
thepolishguy said:
Well...
fastbooting the system should not delete your user data. and its not really complicated.
Do you have ADB set up on your computer?
Click to expand...
Click to collapse
yah i do. but i origginaly downloaded root app as apk
MarcusSi1516 said:
yah i do. but i origginaly downloaded root app as apk
Click to expand...
Click to collapse
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
####EDIT####
If fastboot will not flash the system.img use a different fastboot.exe created to flash the larger .img
arigi said:
The solution is to use the mfastboot.exe linked from here:
http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
Click to expand...
Click to collapse
And if you leave it named "mfastboot" then you must issue the commands with the "m"...
"mfastboot flash system system.img"
without the parenthesis of course
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes it should. Just got to make sure you grab the correct images for your carrier.
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
should.
But I have a VZW MotoX and I dont want to jack anyone up.
As long as you are using the proper system and recovery. If you flash the ATT system to a VZW device you are going to have problems.
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Worked perfect on my ATT Moto x
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
This man deserves some props. Thanks for posting that.
Sent from my HTC One mini
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Thanks for this! It cleared up a whole bunch of things about rooting and locked/unlocked bootloaders for me that just hadn't "clicked" before.
Sent from my Moto X
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Thanks! This was very helpful. I got stuck in a bootloop from a rooted MotoX 4.2.2 whilst trying to accept the OTA to 4.4. I was able to erase the cache to stop the bootloop problem, but I wanted to accept the OTA. I followed this guide and it seemed to work.
For posterity, anyone on Win7 x64 might have had similar problems to me:
Code:
MX-17-57-X-1_CFC_1FF.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
sending sparse 'system' (777329 KB)...
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
OKAY [ 49.985s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
The solution is to use the mfastboot.exe linked from here: http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
arigi said:
Thanks! This was very helpful. I got stuck in a bootloop from a rooted MotoX 4.2.2 whilst trying to accept the OTA to 4.4. I was able to erase the cache to stop the bootloop problem, but I wanted to accept the OTA. I followed this guide and it seemed to work.
For posterity, anyone on Win7 x64 might have had similar problems to me:
Code:
MX-17-57-X-1_CFC_1FF.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
sending sparse 'system' (777329 KB)...
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
OKAY [ 49.985s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
The solution is to use the mfastboot.exe linked from here: http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
Click to expand...
Click to collapse
^^^^THIS^^^^
Thanks @arigi I added this to my original instructions.
Hey guys I'm mostly a lurker not too much of a poster I would respond to "BHUNDVEN"'s thread ([TOOL] Moto X FXZ Flashing Script (100% back to stock) [10/03/2013]) over on the OG Android development sections but alas my "Post count" is too low.
I keep getting this when trying to run the final command "moto-x-flash [insert .xml file]"
Any help? Thanks!
Last login: Thu Nov 7 00:31:17 on ttys001
jeffreys-mbp:~ jeffreymarshall$ cd desktop/moto-x-tools-0.2.0
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$ sudo python setup.py install
running install
running build
running build_py
running build_scripts
running install_lib
running install_scripts
changing mode of /usr/local/bin/moto-x-flash to 755
running install_egg_info
Removing /Library/Python/2.7/site-packages/moto_x_tools-0.2.0-py2.7.egg-info
Writing /Library/Python/2.7/site-packages/moto_x_tools-0.2.0-py2.7.egg-info
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$ moto-x-flash VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml
Traceback (most recent call last):
File "/usr/local/bin/moto-x-flash", line 24, in <module>
tree = ET.parse(firmware_xml)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1182, in parse
tree.parse(source, parser)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 656, in parse
parser.feed(data)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1642, in feed
self._raiseerror(v)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
raise err
xml.etree.ElementTree.ParseError: not well-formed (invalid token): line 1, column 2
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$
I'm not to sure I have the python pkg installed correctly. Had to use the "sudo" command to get it to take.
AceBoonKoon said:
I'm not to sure I have the python pkg installed correctly. Had to use the "sudo" command to get it to take.
Click to expand...
Click to collapse
i cant help you with that toolkit as i don't use it. But if you are merely trying to flash your phone to stock then find the rsd back to 100% stock thread and do that. Just as simple as any other tool you can find.
But honestly, if you spent say 4 hours reading and installing things for adb/fastboot stuff, you won't ever need one of those tools and you won't ever again spend countless hours trying to figure out how to get some tool someone created to work correctly for your phone. The simple sometimes becomes the most time consuming.
Once you figure out a few commands and realize whats going on, you will understand how simple all of that stuff is, and then will be confused as to why anyone ever created a tool for that simple task. Not bashing on the people that created the toolkit, that helps hundreds of people out I'm sure that dont feel like reading a little bit.
memapp can
I would but this [TOOL] is for mac.
No windows machine ala no rsdlite. I did however see that I needed to rename the .xml file to a .zip file ... Then extract the contents and move them over to the moto-x-tools folder and tried flashing it that way but got a "Command not found" error.
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$ moto-x-flash VZW_XT1060_4.2.2-13.9.0Q2.X-116-MX-17-53_CFC_1FF.xml
Running: fastboot oem fb_mode_set
/bin/sh: fastboot: command not found
Running: fastboot flash partition gpt.bin
/bin/sh: fastboot: command not found
Running: fastboot flash motoboot motoboot.img
/bin/sh: fastboot: command not found
Running: fastboot flash logo logo.bin
/bin/sh: fastboot: command not found
Running: fastboot flash boot boot.img
/bin/sh: fastboot: command not found
Running: fastboot flash recovery recovery.img
/bin/sh: fastboot: command not found
Running: fastboot flash system system.img
/bin/sh: fastboot: command not found
Running: fastboot flash modem NON-HLOS.bin
/bin/sh: fastboot: command not found
Running: fastboot erase modemst1
/bin/sh: fastboot: command not found
Running: fastboot erase modemst2
/bin/sh: fastboot: command not found
Running: fastboot flash fsg fsg.mbn
/bin/sh: fastboot: command not found
Running: fastboot erase cache
/bin/sh: fastboot: command not found
Running: fastboot erase userdata
/bin/sh: fastboot: command not found
Running: fastboot erase customize
/bin/sh: fastboot: command not found
Running: fastboot erase clogo
/bin/sh: fastboot: command not found
Running: fastboot oem config carrier vzw
/bin/sh: fastboot: command not found
Running: fastboot oem fb_mode_clear
/bin/sh: fastboot: command not found
Flashing was successful!
Running: fastboot reboot
/bin/sh: fastboot: command not found
jeffreys-mbp:moto-x-tools-0.2.0 jeffreymarshall$
jayboyyyy said:
i cant help you with that toolkit as i don't use it. But if you are merely trying to flash your phone to stock then find the rsd back to 100% stock thread and do that. Just as simple as any other tool you can find.
But honestly, if you spent say 4 hours reading and installing things for adb/fastboot stuff, you won't ever need one of those tools and you won't ever again spend countless hours trying to figure out how to get some tool someone created to work correctly for your phone. The simple sometimes becomes the most time consuming.
Once you figure out a few commands and realize whats going on, you will understand how simple all of that stuff is, and then will be confused as to why anyone ever created a tool for that simple task. Not bashing on the people that created the toolkit, that helps hundreds of people out I'm sure that dont feel like reading a little bit.
Click to expand...
Click to collapse
In response to the fastboot commands suggestion - I have already tried using the adb/fastboot methods didn't work. Did a search for people with similar issues and found that it has something about it being on a mac or some other nonsense. That's the reason for the [TOOL] I think. It's a workaround.
AceBoonKoon said:
In response to the fastboot commands suggestion - I have already tried using the adb/fastboot methods didn't work. Did a search for people with similar issues and found that it has something about it being on a mac or some other nonsense. That's the reason for the [TOOL] I think. It's a workaround.
Click to expand...
Click to collapse
don't know where you fastboot is but i believe its trying to call it and its not in the directory that the cmd is pointed to.
Ok I've went down the list and manually flashed each command.
When I get to ./fastboot flash system system.img
I keep getting this error
"Mismatched PIV partition name for system
Invalid PIV image: system"
I can successfully flash all other commands except this one. I went into the .xml file and deleted the "getvar" portion already. Any help?
AceBoonKoon said:
Ok I've went down the list and manually flashed each command.
When I get to ./fastboot flash system system.img
I keep getting this error
"Mismatched PIV partition name for system
Invalid PIV image: system"
I can successfully flash all other commands except this one. I went into the .xml file and deleted the "getvar" portion already. Any help?
Click to expand...
Click to collapse
not sure about the error sorry. also you might want to click on the reply button so it appears as a notification for me or i might not ever look at the thread again if i forget, jsut fyi.
are you sure you are using the right fxz for your phone? also when you run manual commands in fastboot, the xml file doesn't matter. that file is just there for rsd and other programs to use (it is basically just a script of commands that gets called on by programs to run). i don't know if you are typing "./fastboot" instead of just "fastboot" in cmd prompt but you only need to type "fastboot flash system system.img"
jayboyyyy said:
not sure about the error sorry. also you might want to click on the reply button so it appears as a notification for me or i might not ever look at the thread again if i forget, jsut fyi.
are you sure you are using the right fxz for your phone? also when you run manual commands in fastboot, the xml file doesn't matter. that file is just there for rsd and other programs to use (it is basically just a script of commands that gets called on by programs to run). i don't know if you are typing "./fastboot" instead of just "fastboot" in cmd prompt but you only need to type "fastboot flash system system.img"
Click to expand...
Click to collapse
Thanks for the fyi didn't know. I've tried flashing both fxz's for my phone and nothing both keep saying the same error Mismatched PIV. Thanks for the schooling on the xml file didn't know that. Going to keep searching.
AceBoonKoon said:
Thanks for the fyi didn't know. I've tried flashing both fxz's for my phone and nothing both keep saying the same error Mismatched PIV. Thanks for the schooling on the xml file didn't know that. Going to keep searching.
Click to expand...
Click to collapse
both? you can't just flash both like that. are you sure you are doing all of this right? one for your phone is a different FW version than the other one. This could be why you are getting this mismatch. Also, you would need to unzip and move all of the files to the directory that your fastboot is in. Then if you were trying to flash a different fxz, you would need to remove the old files from that directory and replace them with the new fxz files.
Finally, the commands to run manually will be found at this link. http://forum.xda-developers.com/showthread.php?p=46712761&highlight=flash+stock#post46712761
jayboyyyy said:
both? you can't just flash both like that. are you sure you are doing all of this right? one for your phone is a different FW version than the other one. This could be why you are getting this mismatch. Also, you would need to unzip and move all of the files to the directory that your fastboot is in. Then if you were trying to flash a different fxz, you would need to remove the old files from that directory and replace them with the new fxz files.
Finally, the commands to run manually will be found at this link. http://forum.xda-developers.com/showthread.php?p=46712761&highlight=flash+stock#post46712761
Click to expand...
Click to collapse
Now it's saying that can't downgrade when trying to flash the bootloader and it still won't flash the system.img same error.
I think I messed up when I tried to flash the "newer" FXZ. To see if I could get it to go through.
AceBoonKoon said:
I think I messed up when I tried to flash the "newer" FXZ. To see if I could get it to go through.
Click to expand...
Click to collapse
ya you can't flash the old one anymore. it will fail. you should be able to flash the new system img though. just make sure you are using the right one for your device. couldn't find anything on the internet for that particular error. So not many people run into it. It has to be something you are doing. try redownloading the fxz (the correct new fxz for your phone) and then start over from the beginning of the code and flash all the new stuff.
jayboyyyy said:
ya you can't flash the old one anymore. it will fail. you should be able to flash the new system img though. just make sure you are using the right one for your device. couldn't find anything on the internet for that particular error. So not many people run into it. It has to be something you are doing. try redownloading the fxz (the correct new fxz for your phone) and then start over from the beginning of the code and flash all the new stuff.
Click to expand...
Click to collapse
The fastboot flashes through every command flawlessly all EXCEPT the system.img. Keeps saying the bootloader preauthorization failed. I've flashed it every which way, straight through, at random, only the recovery, bootloader, and system.img. Can't get it to play nice.
I did read somewhere that mac fastboot had an issue with how large the system file was for VZW's moto x and couldn't flash it. Someone said that rsd lite breaks it up into smaller pieces in order to get it to flash. I wonder if there is a manual way to do this?
AceBoonKoon said:
The fastboot flashes through every command flawlessly all EXCEPT the system.img. Keeps saying the bootloader preauthorization failed. I've flashed it every which way, straight through, at random, only the recovery, bootloader, and system.img. Can't get it to play nice.
I did read somewhere that mac fastboot had an issue with how large the system file was for VZW's moto x and couldn't flash it. Someone said that rsd lite breaks it up into smaller pieces in order to get it to flash. I wonder if there is a manual way to do this?
Click to expand...
Click to collapse
forgot you were using a mac. just throw that thing away and get a big boy computer. lol. jk. don't need to start hearing a bunch of people chime in but here is a link to a fastboot file that splits it up for you. don't know if it will help or not.
http://forum.xda-developers.com/showthread.php?t=2489249
jayboyyyy said:
forgot you were using a mac. just throw that thing away and get a big boy computer. lol. jk. don't need to start hearing a bunch of people chime in but here is a link to a fastboot file that splits it up for you. don't know if it will help or not.
http://forum.xda-developers.com/showthread.php?t=2489249
Click to expand...
Click to collapse
I went and downloaded the "motofastboot-olympus" file and extracted the Linux fastboot file and placed in my folder replacing the current fastboot and now when I try to run a fastboot command I get "./fastboot: cannot execute binary file" I've tried the "Darwin" fastboot as well same thing.
AceBoonKoon said:
I went and downloaded the "motofastboot-olympus" file and extracted the Linux fastboot file and placed in my folder replacing the current fastboot and now when I try to run a fastboot command I get "./fastboot: cannot execute binary file" I've tried the "Darwin" fastboot as well same thing.
Click to expand...
Click to collapse
i see that you actually searched for this answer because i went to that mac thread i remembered seeing to see if there was a solution there. so you can just factory reset the device right? you don't need the system.img there to factory reset i don't think. just try a factory reset.
just found this. try downloading the nexus for stuff. pull the fastboot-mac file or whatever it is out of it. run all your commands with the "./fastboot-mac" and see if it works now.
jayboyyyy said:
i see that you actually searched for this answer because i went to that mac thread i remembered seeing to see if there was a solution there. so you can just factory reset the device right? you don't need the system.img there to factory reset i don't think. just try a factory reset.
Click to expand...
Click to collapse
I've been searching all day for all of these answers. Just thought it would help to ask as well.
I found the solution to my problem. For any of those who are having trouble flashing back to stock ON A MAC It will not flash because the system.img file is TOO BIG you need the CORRECT version of Moto-Fastboot. Here's the link that you can download and place it in your "Fastboot" folder. http://forum.xda-developers.com/showthread.php?t=1138092
I suggest you hold on to that fastboot for future flashes/return to stock. Thank you for your help jayboyyyy!
AceBoonKoon said:
I've been searching all day for all of these answers. Just thought it would help to ask as well.
I found the solution to my problem. For any of those who are having trouble flashing back to stock ON A MAC It will not flash because the system.img file is TOO BIG you need the CORRECT version of Moto-Fastboot. Here's the link that you can download and place it in your "Fastboot" folder. http://forum.xda-developers.com/showthread.php?t=1138092
I suggest you hold on to that fastboot for future flashes/return to stock. Thank you for your help jayboyyyy!
Click to expand...
Click to collapse
nice find. im going to update that thread i made with this link instead of the link i had because it seems to have fastboot for everyone.