Related
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.
So i kind of got a situation here , i originally wanted to be rooted and have my nexus 6 non encrypted so i had unlocked and rooted my phone. After i ran the "./fastboot erase userdata" command i flashed the custom recovery again and booted into it. From there i thought i would be able to "./adb sideload" a stock custom rom non encrypted but for some reason i was having difficulty running that command. My laptop was not seeing the phone, so after about 30 min of playing around with it trying to get it to work i figured id just start over fresh. From this point i dont have an OS installed so i knew i would have to download the appropriate files for the nexus 6 so i did. I tried both methods, the "./flash-all.sh" command and flashing everything one by one rebooting the bootloader in between flashes and still kept getting this same error
fastboot(1561,0xa04aa1d4) malloc: *** mach_vm_map(size=1681293312) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679613116 bytes
error: update package missing system.img
and now im stuck in fastboot mode at least, but cannot revert back to stock unless im missing something here. Can someone help please
AnthonyAldrete said:
So i kind of got a situation here , i originally wanted to be rooted and have my nexus 6 non encrypted so i had unlocked and rooted my phone. After i ran the "./fastboot erase userdata" command i flashed the custom recovery again and booted into it. From there i thought i would be able to "./adb sideload" a stock custom rom non encrypted but for some reason i was having difficulty running that command. My laptop was not seeing the phone, so after about 30 min of playing around with it trying to get it to work i figured id just start over fresh. From this point i dont have an OS installed so i knew i would have to download the appropriate files for the nexus 6 so i did. I tried both methods, the "./flash-all.sh" command and flashing everything one by one rebooting the bootloader in between flashes and still kept getting this same error
fastboot(1561,0xa04aa1d4) malloc: *** mach_vm_map(size=1681293312) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1679613116 bytes
error: update package missing system.img
and now im stuck in fastboot mode at least, but cannot revert back to stock unless im missing something here. Can someone help please
Click to expand...
Click to collapse
it looks like the script is looking for a file that is not in the proper directory
the flash all script has never worked for me I have always had to manually flash the images.
looks like you are on a mac since you are using the ./with the command
follow the directions below and you should get back to stock
since you are already in bootloader mode
Download the required factory image files to your computer and extract them
Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu or MAC just cd to the directory.
Type in the commands into the command prompt
Make sure your computer recognizes your device by typing: fastboot devices
Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the radio: fastboot flash radio radio-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the system partition: fastboot flash system system.img
Flash the data partition: fastboot flash userdata userdata.img
Flash the kernel/ramdisk: fastboot flash boot boot.img
Flash the recovery partition: fastboot flash recovery recovery.img
Erase the cache partition: fastboot format cache
Reboot: fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
funny i just did this exact same thing like you instructed and was about to reply to this post saying i resolved it hahah. Thanks anyways though =), i dont understand why i was getting that though because i had every file in the same place
No worries glad you got it working
qnc said:
No worries glad you got it working
Click to expand...
Click to collapse
Also found out that you Dont do the ./fastboot erase userdate command because it puts 0s in and leaves the phone unbootable which was my root cause for my phone being stuck. Instead, after flashing the boot.IMG you do the ./fastboot partition userdata instead and it will do a factory reset and when booting it will not encrypt the phone.
qnc said:
it looks like the script is looking for a file that is not in the proper directory
the flash all script has never worked for me I have always had to manually flash the images.
looks like you are on a mac since you are using the ./with the command
follow the directions below and you should get back to stock
since you are already in bootloader mode
Download the required factory image files to your computer and extract them
Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu or MAC just cd to the directory.
Type in the commands into the command prompt
Make sure your computer recognizes your device by typing: fastboot devices
Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the radio: fastboot flash radio radio-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the system partition: fastboot flash system system.img
Flash the data partition: fastboot flash userdata userdata.img
Flash the kernel/ramdisk: fastboot flash boot boot.img
Flash the recovery partition: fastboot flash recovery recovery.img
Erase the cache partition: fastboot format cache
Reboot: fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
Click to expand...
Click to collapse
And I was having the same issues executing the flash all command too until I opened the command in a text editor and for every command put the "./" in front and was able to execute it but this is the first time I've gotten an error. My nexus5 worked with this command no problem
worked for me but still could not decrypt
qnc said:
it looks like the script is looking for a file that is not in the proper directory
the flash all script has never worked for me I have always had to manually flash the images.
looks like you are on a mac since you are using the ./with the command
follow the directions below and you should get back to stock
since you are already in bootloader mode
Download the required factory image files to your computer and extract them
Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu or MAC just cd to the directory.
Type in the commands into the command prompt
Make sure your computer recognizes your device by typing: fastboot devices
Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the radio: fastboot flash radio radio-some-description-number.img
Reboot: fastboot reboot-bootloader
Flash the system partition: fastboot flash system system.img
Flash the data partition: fastboot flash userdata userdata.img
Flash the kernel/ramdisk: fastboot flash boot boot.img
Flash the recovery partition: fastboot flash recovery recovery.img
Erase the cache partition: fastboot format cache
Reboot: fastboot reboot
Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
Click to expand...
Click to collapse
so all of this worked for me and its back up and running, but my phone still says that its encrypted
My HTC One M7 (UK O2) was prompting me to update to the latest operating system.
Eventually I succumbed and installed the update. The phone is stock although I had unlocked the bootloader in preparation for experimenting with new operating systems (I'm a noob but curious about experimenting).
After installing, the phone rebooted and wound up on a screen with a red exclamation mark in a picture of a phone.
Sometimes it boots into the white Android startup screen, then shuts down and goes throught the whole startup cycle in a loop
I can get it into bootloader mode but none of the options presented there such as factory reset seem to do anything.
I don't think it's a hardwear problem as it seems to be a direct result of trying to install the update.
I would send it in for a warranty repair but I think that as I have unlocked then relocked the bootloader and it shows a 'relocked' flag then that voids the warranty, is that right?
Any help to sort this mess out would be appreciated.
Thanks
jimbobly
During unlocking bootloader some files deleted and during update ota checks file integrity so file found missing and update stops
So basically you have to restore that files
Or RUU update can be found here
But it will delete your all data photo songs contact apps so backup them
http://forum.xda-developers.com/showthread.php?t=3053944
Thanks Yatindroid,
I don't think I can restore the files so I need to use the RUU. Can you tell me how to identify the correct file?
Thanks
jimbobly said:
Thanks Yatindroid,
I don't think I can restore the files so I need to use the RUU. Can you tell me how to identify the correct file?
Thanks
Click to expand...
Click to collapse
this file: https://www.androidfilehost.com/?fid=95916177934541097
instructions on how to flash it are at the top of the page in Yatindroid's link.
RUU
Seanie280672 said:
this file androidfilehost.com/?fid=95916177934541097
instructions on how to flash it are at the top of the page in Yatindroid's link.
Click to expand...
Click to collapse
This file seems to be corrupt/ can't be opened, downloaded it 3 times, can you link an alternative or explain the things that I need to consider in order to be able to choose an RUU myself.
Thanks
jimbobly said:
This file seems to be corrupt/ can't be opened, downloaded it 3 times, can you link an alternative or explain the things that I need to consider in order to be able to choose an RUU myself.
Thanks
Click to expand...
Click to collapse
This file is not corrupted, its encrypted, you can't open it. Want to know if its corrupted? MD5 value is what you want to check.
If the MD5 is ok then flash the zip.
md5: 399fa4bc8e841cc993a358e7c09fc4ca
alray said:
This file is not corrupted, its encrypted, you can't open it. Want to know if its corrupted? MD5 value is what you want to check.
If the MD5 is ok then flash the zip.
md5: 399fa4bc8e841cc993a358e7c09fc4ca
Click to expand...
Click to collapse
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
jimbobly said:
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
Click to expand...
Click to collapse
First is the Md5 good?
RUU
jimbobly said:
Can you explain what is happening when I try to flash it over to the phone.
I go through all the steps and when I execute the flash command for this zip file it says 'Preprocess_file : Cannot open file RUU.zip' This lead me to believe it was defective in some way. What am I missing?
Click to expand...
Click to collapse
Also, when I try to unpack the zip file I get the message that the compressed file is empty!
jimbobly said:
Also, when I try to unpack the zip file I get the message that the compressed file is empty!
Click to expand...
Click to collapse
To eliminate any doubt about corrupted file, the only thing you have to do is to check the md5 value. ANd like we already said, the file is encrypted you can't open an encrypted zip. Just check the md5 to confirm the file is good.
alray said:
To eliminate any doubt about corrupted file, the only thing you have to do is to check the md5 value. ANd like we already said, the file is encrypted you can't open an encrypted zip. Just check the md5 to confirm the file is good.
Click to expand...
Click to collapse
Unfortunately, this is a bit advanced for me. How can I do this?
jimbobly said:
Unfortunately, this is a bit advanced for me. How can I do this?
Click to expand...
Click to collapse
http://www.winmd5.com/
alray said:
http://www.winmd5.com/
Click to expand...
Click to collapse
OK, I checked the md5 with the tool and they match. But I still get the message 'preprocess file cannot open zip'.
How should I be handling the file, with the fastboot commands?
jimbobly said:
OK, I checked the md5 with the tool and they match. But I still get the message 'preprocess file cannot open zip'.
How should I be handling the file, with the fastboot commands?
Click to expand...
Click to collapse
you need learn flashing RUU zip
reboot your phone to fastboot mode (same as you posted pic )
setup adb folder find miniSDK HERE and Here
Download htc fastboot HERE copy it adb folder rename it fastboot.exe (rename old fastboot to other name)
open adb folder put your RUU zip there rename it RUU.zip
connect your phone with PC
your phone should be locked/relocked
at adb folder open CMD (shift + right click)
type command below
Code:
fastboot devices
(will show attached phone to PC match serial no)
Code:
fastboot oem rebootRUU
(reboot phone to flashing ruu mode)
Code:
fastboot flash zip RUU.zip
(wait it will take time 8-10 minutes it will show successfully at last if not repeat same command immediately)
Code:
fastboot reboot-bootloader
( it is last and important step of flashing)
now see new version showing at phone details
reboot to system
RUU
Thanks for taking the time to look at this Yatindroid.
I followed your instructions but there seems to be a problem with the RUU file.
When I execute the 'flash zip' command I get an 'unable to read zip message!
The file I have has been recommended by several people.
Am I handling this file incorrectly?
This is the file I am using. https://www.androidfilehost.com/?fid=95916177934541097
All I did was rename the file RUU.zip and move it to the ADB folder.
Thanks for the help.
jimbobly said:
Thanks for taking the time to look at this Yatindroid.
I followed your instructions but there seems to be a problem with the RUU file.
When I execute the 'flash zip' command I get an 'unable to read zip message!
The file I have has been recommended by several people.
Am I handling this file incorrectly?
This is the file I am using. https://www.androidfilehost.com/?fid=95916177934541097
All I did was rename the file RUU.zip and move it to the ADB folder.
Thanks for the help.
Click to expand...
Click to collapse
put RUU.zip in fastboot/adb folder
name should be RUU.zip not RUU.zip.zip
use htc fastboot rename that to fastboot
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
yatindroid said:
put RUU.zip in fastboot/adb folder
name should be RUU.zip not RUU.zip.zip
use htc fastboot rename that to fastboot
Click to expand...
Click to collapse
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
jimbobly said:
RUU
I changed the name to just RUU, I thought the filename had to include the .zip term.
Now it tells me that it cannot open RUU.zip.
Click to expand...
Click to collapse
check md5
fastboot flash zip ( pressing tab will show files in fastboot folder press tab until you got ruu.zip )
Already checked the md5 and it's ok.
What is the best thing to do? Just try a new RUU?
What am I doing wrong (fixing flash bootloader to fix "device is corrupted")
Hi,
I extract these files from shamu-mra58x: (with that version i can smoothly root without thse force "device is corrupted"?)
1. android-info
2. boot
3. cache
4. recovery.img
5. system
6. userdata
*** Is any file missing? What about Radio.img ? ***
Copied them to Platform-tools folder.
Booted into bootloader and started the following commands: (ARE THEY ALL RIGHT?)
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radion.img
fastboot reboot-bootloader
fastboot flash system system.img
In: fastboot flash bootloader bootloader.img ->
I got this responce in the cmd.
Why?
Thank you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the command you need is "fastboot flash bootloader bootloader.img"
also, i don't see the bootloader.img file IN your ADB folder, which is certainly going to fail that command as well
**EDIT**
Also, PLEASE make sure you downloaded the files for "shamu" not for another nexus device. I don't know if there is anything that would check that, but flashing a bootloader for another device would *probably* hard brick you.
shabydog said:
Hi,
I extract these files from shamu-mra58x: (with that version i can smoothly root without thse force "device is corrupted"?)
1. android-info
2. boot
3. cache
4. recovery.img
5. system
6. userdata
*** Is any file missing? What about Radio.img ? ***
Copied them to Platform-tools folder.
Booted into bootloader and started the following commands: (ARE THEY ALL RIGHT?)
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radion.img
fastboot reboot-bootloader
fastboot flash system system.img
In: fastboot flash bootloader bootloader.img ->
I got this responce in the cmd.
Why?
Thank you!
Click to expand...
Click to collapse
its fastboot flash bootloader bootloader.img you forgot to put where you want it to be flashed to.
Thank you for the quick responce
@PWn3R
You mean that you dont see the bootloader.img in Platform-tools forlder, right?
I double checked in Google Dev site and downloaded the 6.0.0 (MRA58X) version which was under "Nexus 6" section.
@simms22
When i type:
fastboot flash bootloader bootloader.img --- I get this response:
target responed max download size of 536870912 bytes
error: cannot load "bootloader.img": No erro
What about the rest of the commands? Are they right?
And why there is NO radio.img when i take the img's from shamu-mra58x?
I dont need chainfire's modified boot.img?
Thanks again!
shabydog said:
Thank you for the quick responce
@PWn3R
You mean that you dont see the bootloader.img in Platform-tools forlder, right?
I double checked in Google Dev site and downloaded the 6.0.0 (MRA58X) version which was under "Nexus 6" section.
@simms22
When i type:
fastboot flash bootloader bootloader.img --- I get this response:
target responed max download size of 536870912 bytes
error: cannot load "bootloader.img": No erro
What about the rest of the commands? Are they right?
And why there is NO radio.img when i take the img's from shamu-mra58x?
Thanks again!
Click to expand...
Click to collapse
The files you are missing are in the folders above where you got the system.img and boot.img. The command we gave you fails because the bootloader.img file from the zip you extracted isn't in the folder you are trying to flash from. So, yes, to the question you posed.
What do you mean "the files you are missing..."?
It's only the radio, no?
And regarding this sentece -> I did not got you :
The command we gave you fails because the bootloader.img file from the zip you extracted isn't in the folder you are trying to flash from
Click to expand...
Click to collapse
From MRA58X i get these img's:
boot
cache
recovery
system
userdata
(and txt file called android-info)
I copied all of the 6 files into Platform-tools folder.
shabydog said:
What do you mean "the files you are missing..."?
It's only the radio, no?
And regarding this sentece -> I did not got you :
From MRA58X i get these img's:
boot
cache
recovery
system
userdata
(and txt file called android-info)
I copied all of the 6 files into Platform-tools folder.
Click to expand...
Click to collapse
The other files are in another folder. You extracted a zip from that folder to get the boot, cache, recovery, system and userdata files. Find the folder that you extracted that zip from, and the files you are looking for (bootloader and radio) are inside the same folder that you extracted the update.zip file to get the other img files.
OK
Found them.
I dont know why, BUT the Radio+Bootloader wasnt within the zip of shamu-mra58x TAR file...they came in the same zip.
See attached imgae.
So just too them and copied to Platform-tools! Is it ok?
Also attached: The "updated" folder -> all the files are there?
Thank you.
shabydog said:
OK
Found them.
I dont know why, BUT the Radio+Bootloader wasnt within the zip of shamu-mra58x TAR file...they came in the same zip.
See attached imgae.
So just to take these 2 and copy to Platform-tools.
I also add the "updated" folder -> all the files are there?
Thank you.
Click to expand...
Click to collapse
Yup, all files present.
I always flash them in this order: bootloader, radio, system, userdata, boot, recovery and cache.
Why do I get this error for any command?
target respond max download size of 536870912 bytes
error: cannot load 'system' : No error
Read that i should run CMD as admin...(I am the only user on this pc...guess i have admin privileges, right?)
Also to close softwares running on backgroud - Will try that too now.
shabydog said:
Why do I get this error for any command?
target respond max download size of 536870912 bytes
error: cannot load 'system' : No error
Click to expand...
Click to collapse
Have you updated the SDK tools?
Hi,
I will try updating that.
By the way - These are the packages that installed:
Do you see anything missing? (Exept of the 2 updates)
Thank you!
PWn3R said:
The command we gave you fails because the bootloader.img file from the zip you extracted isn't in the folder you are trying to flash from. So, yes, to the question you posed.
Click to expand...
Click to collapse
Hi!
Really need your help. please...
I really dont understand what is the issu with bootloader.img file is not in the folder that i flashing from?
@PWn3R and @simms22
Here is the platform-tools with all the images...
What is wrong?
Thank you!
P.S:
1) Is it o.k that a Bootloader file for the N6 named "bootloader-shamu-moto-apq8084-71.15"
??? (Double checking after googled for that)
2) If anyone can loot at the above (last replay) screenshot of the SDK and tell me if anything is missing there?
Looking at the last screen print, it looks like you have all the IMG files in the same folder.
If so, open a command prompt (after connecting your phone in bootloader mode to PC), and type in "fastboot devices" (without quotes). If you get back the serial #, then proceed. (if you get any error message, stop - get fastboot working first).
If fastboot devices worked, run the fastboot commands to flash individual IMG files (reboot bootloader command after flashing bootloader and radio IMG files).
Edit: the bootloader IMG file can be named anything (as long as you flash the exact file name). For ease, I usually rename the file as bootloader.img and then, "fastboot flash bootloader bootloader.img" - but if your bootloader file is named something else, you can use that filename in the command
Edit2: remember that if you flash userdata (that you have highlighted in your screen print), that will wipe your data.
Edit3: (yeah, a lot of edits, I know - need my coffee). If you are getting "file not found", try this - in the command prompt, type in "dir *.img" (without quotes) and verify that all the IMG files are present
@jj14
The wierd thing is that:
--> If i do fastboot devices from platform-tools the phone do recognize!
--> If i do it from "update6" folder ( that how the author told in the tut: http://www.ibtimes.co.uk/android-6-...-not-enough-space-error-nexus-devices-1522624 )
I get "'fastboot' is not recognized as an internal or external command,operable program or batch file".
shabydog said:
Why do I get this error for any command?
target respond max download size of 536870912 bytes
error: cannot load 'system' : No error
Read that i should run CMD as admin...(I am the only user on this pc...guess i have admin privileges, right?)
Also to close softwares running on backgroud - Will try that too now.
Click to expand...
Click to collapse
Did you place the system.img file in the same folder as where fastboot.exe is located? The command is: fastboot flash system system.img. Do you see a serialnumber if you type: fastboot devices?
shabydog said:
@jj14
The wierd thing is that:
--> If i do fastboot devices from platform-tools the phone do recognize!
--> If i do it from "update6" folder ( that how the author told in the tut: http://www.ibtimes.co.uk/android-6-...-not-enough-space-error-nexus-devices-1522624 )
I get "'fastboot' is not recognized as an internal or external command,operable program or batch file".
Click to expand...
Click to collapse
That seems to indicate that fastboot.exe is not in the PATH variable in windows. To get around that, extract all the IMG files and place them in the same folder as where fastboot.exe is, and then, open a command prompt to that folder and run the commands from there.
If you want to make fastboot.exe available anywhere (regardless of which folder your command prompt is at), you can update your path variable - see instructions on how to do this http://www.howtogeek.com/118594/how-to-edit-your-system-path-for-easy-command-line-access/
Oh well.... for the XX time i will try to help (although i wouldn't anymore.
Delete that whole SDK. Download attached fastboot/adb (very latest version). Extract to a folder and put the images you want to flash in the same folder as fastboot. open command prompt AS ADMIN and use the CORRECT commands.
there is no 'fix' for the 'device is corrupted' message. with corrupted they mean that you have a custom recovery flashed or that you are rooted. Again: flash twrp with fastboot and flash a custom rom and kernel.
Please have a look at the added screenshot - everything is in there.
Droidphilev
Thank you for trying helping anyway - appreciate!!!
"Delete whole SDK" = completly Uninstall from add/remove programs?
Thanks !
In your screen print, I can't see the path, so assuming this screen print is showing your actual folder (not a zip archive), and that all the IMG files are in the same folder:
Open a command prompt window, and CD to the platform-tools folder, and type in "dir *.img" without quotes. Share that screen print (you should see all the IMG files there).
Then, try the fastboot commands (start with fastboot devices), and see how it goes. In case you get an error, share the error message
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
Click to expand...
Click to collapse
Go to https://developers.google.com/android/images and flash manually it's work with me
Sent from my BASIC using Tapatalk
When you run the flash all in fastboot, what messages/errors does it show?
I once ran into a similar problem, the fact that you have unlocked the bootloader is good as you can flash the factory image and boot it up.
Usually once in fastboot I check the devices with "fastboot devices", if it shows up, I close the adb window, copy the factory image files to the adb folder, and doublec click the flash all bat. It should do everything by itself and reboot now.
TENN3R said:
When you run the flash all in fastboot, what messages/errors does it show?
I once ran into a similar problem, the fact that you have unlocked the bootloader is good as you can flash the factory image and boot it up.
Usually once in fastboot I check the devices with "fastboot devices", if it shows up, I close the adb window, copy the factory image files to the adb folder, and doublec click the flash all bat. It should do everything by itself and reboot now.
Click to expand...
Click to collapse
Just to add to this, make sure you left the image-coral-[buildnumber].[builddate].zip ZIPPED. Your folder should look something like this one, although you might also have your platform-tools in that same directory, which is perfectly fine, but not necessary if you have them added to your path.
Just try redoing the flash-all.bat again. This time, though, do it from powershell. Here's what to do. Right click in the folder, not on any item, just in the folder, and you should see "open powershell" (or command prompt, if this is the case, then just type powershell into the cmd window), click that. Then, type or copy and paste into the powershell prompt while in that directory:
.\flash-all.bat | Tee xda-flash-attempt.log
and if it still doesn't work and you're stuck in fastboot, just upload that .log file, so we can see what happened. If you're curious, what Tee does is it simultaneously takes standard input (i.e. what you see on the screen, the output of programs) and shows it to you, as well as sends it to a file, in this case, the xda-flash-attempt.log If you really don't want to use powershell, you can accomplish what's needed by typing flash-all.bat > xda-flash-attempt.log, but you will not see any of the output, as it will all be piped into that file. The | key is the one directly below backspace, which is the same key as \, but with shift held down.
Also, if it's not working, it might be worth checking that the checksum of the zip file you downloaded is correct, possibly redownloading it, and also checking what the flash-all.bat contents are. There are two files named flash-all in the folder, one a .sh for *nix systems, and a .bat for windows. While it should automatically assume you meant the .bat, it's best to be explicit. The .sh really wouldn't do anything different, if it worked, so it's a minor issue that really wouldn't make a difference, but still.
Edit: when you do type flash-all, the cmd prompt was in the directory with the flash-all.bat file as well as all of the other necessary files, yes? Seems obvious, perhaps, but just based on the "cd\pp\p" command you ran, which doesn't do anything, you should be changing directory to the directory that holds the flash-all.bat as well as the firmware.
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today ...
Click to expand...
Click to collapse
Like others have said, you need to extract the Google image which has a nested zip file (which you leave alone unless you need something in there). Since you apparently are stuck and cannot boot, I suggest you extract the boot.img from that nested zip file into your tools folder and fastboot flash the boot.img to be able to boot the phone to system. You may need to do the vol-down button press to enter fastboot mode. Once you have your phone back and running, boot into fastboot mode and run the flash-all again. If you extracted the Google image completely, now the script can finish. Not sure if you want to wipe the phone while doing this, so you can also "dirty flash" . If you would like to retain all your apps and app data, edit the flash-all script with notepad and remove the wipe flag (-w) from the script and SAVE it before running. Best of luck. :good:
blackbomb1991 said:
Hi everyone ,
I tried flashing android 11 on my pixel 4xl today and I did the exact same procedures when I used to flash my pixel 2 but I don't know what went wrong and I am stuck on Fastbood Mode where it says :
Boot slot: b
enter reason: no valid slot to boot.
What I did was , I downloaded platformtols and pixel 4xl factory image. Then , I unzipped all contents into one folder. I ran cmd command and execute the following commands :
Before running the commands I enabled OEM Unlock and USB debugging .
In the command Prompt I executed :
cd\pp\p
adb
adb devices
then it showed the list of devices attached
adb reboot bootloader
fastboot flashing unlock
and then
flash-all
And now I am stuck on fastboot mode and my phone is not rooted if you are concerned . I contact google support and he thought its a hardware issue which I am damn sure it's not . He told me to send my phone to the repair center but I can not because I am not in US anymore and where I am living there is no Google Service Center. Can someone please help me I just want to run my phone again. Please !
Thanks.
Click to expand...
Click to collapse
Put the unzipped factory image files (should be 6 of them) in your platform tools folder and then open up the command prompt in the platform tools folder and execute the flash-all command. Make sure all remnants of previous factory images, etc. are removed from the platform tools folder beforehand as well so you just have the platform tools default files in there as well as the 6 files from the factory image.
The latest version of platform tools is 30.0.4 I believe so make sure you have that version.
I just switched from a Pixel 2 xl and ran into the exact same problem with the no valid slot to boot error yesterday. It turned out I was not using the latest platform tools when flashing the factory image. I upgraded my platform tools to 30.04 and everything flashed and booted as expected.
Make sure you're using an A to C and not the C to C that comes with the phone when flashing. Yes, it matters.
Hi everyone,
Thank you so much guys for your quick responses . Well , I finally resolved my issue by the following commands so I'm just gonna post it for whomever may run into the same problem as I did .
First thing I did, was to download the latest Platform tools as well as USB Drivers and then I executed the following commands :
fastboot --slot=all flash bootloader ( Drag bootloader image ) By dragging I mean , you should unzip the flash factory image into a folder and then drag bootloader image into command prompt .
fastboot reboot bootloader
fastboot --slot=all flash radio ( Drag radio image )
fastboot reboot bootloader
fastboot --skip-reboot --slot=all update ( Drag Image file )
Boommmmm, my phone back on running again with no issue.
blackbomb1991 said:
Hi everyone,
Thank you so much guys for your quick responses . Well , I finally resolved my issue by the following commands so I'm just gonna post it for whomever may run into the same problem as I did .
First thing I did, was to download the latest Platform tools as well as USB Drivers and then I executed the following commands :
fastboot --slot=all flash bootloader ( Drag bootloader image ) By dragging I mean , you should unzip the flash factory image into a folder and then drag bootloader image into command prompt .
fastboot reboot bootloader
fastboot --slot=all flash radio ( Drag radio image )
fastboot reboot bootloader
fastboot --skip-reboot --slot=all update ( Drag Image file )
Boommmmm, my phone back on running again with no issue.
Click to expand...
Click to collapse
Woohoo! This worked perfectly. Thanks for following up with the instructions.