I recently bricked my Atrix 2, and since I don't have easy access to a Windows machine, I attempted to flash it back to stock using fastboot from the android dev tools. I noticed that the XML file in the FXZ looked like a set of fastboot commands, so that's what I tried to do. However, no matter which zip I started from, it always failed to flash system.img, saying that verification failed. After giving up on that approach, I used a friend's windows machine to flash the exact same zip using RSDLite, and it succeeded just fine. This leads me to conclude that RSDLite must be doing something special when flashing the system.img. Does anyone know what it is, and is there a way to do the same thing using the standard Android development tools (fastboot, etc)?
Thanks!
bemjb said:
I recently bricked my Atrix 2, and since I don't have easy access to a Windows machine, I attempted to flash it back to stock using fastboot from the android dev tools. I noticed that the XML file in the FXZ looked like a set of fastboot commands, so that's what I tried to do. However, no matter which zip I started from, it always failed to flash system.img, saying that verification failed. After giving up on that approach, I used a friend's windows machine to flash the exact same zip using RSDLite, and it succeeded just fine. This leads me to conclude that RSDLite must be doing something special when flashing the system.img. Does anyone know what it is, and is there a way to do the same thing using the standard Android development tools (fastboot, etc)?
Thanks!
Click to expand...
Click to collapse
Fastboot is basically doing what RSD Lite does manually. If you keep on getting a flash system.img error mkake sure that you have the proper drivers. You can download Android-SDK for your platform and then open the manager. There should be an option to install a drivers package.
I am pretty sure RSD Lite does nothing special. I have flashed just the system.img multiple times to quickly get my phone back up and running.
.
farshad525hou said:
Fastboot is basically doing what RSD Lite does manually. If you keep on getting a flash system.img error mkake sure that you have the proper drivers. You can download Android-SDK for your platform and then open the manager. There should be an option to install a drivers package.
I am pretty sure RSD Lite does nothing special. I have flashed just the system.img multiple times to quickly get my phone back up and running.
.
Click to expand...
Click to collapse
Thanks, but there are no USB drivers available for Mac OS X: the Android SDK says that they are unavailable for this platform. Maybe if I get the chance, I'll see if doing the flash with fastboot on Windows gives different results.
Are you using moto-fastboot?
Oh there's a Mac version here (from here)
There's a size limit on flash operations with normal fastboot.
moofree said:
Are you using moto-fastboot?
Oh there's a Mac version here (from here)
There's a size limit on flash operations with normal fastboot.
Click to expand...
Click to collapse
I've been using normal fastboot, I didn't realize there was a difference there. Thanks a ton, I'm sure that will solve my issue!
This needs to be added to to using the fastboot command that Farshad posted.
If you are doing this from OS X or linux, or well even windows, I posted a string of commands on how to flash these files using fastboot, there is a certain order, and there are files from the fxz you will need to skip.
Next time please do a search on this board for fastboot flash commands....
I will be nice and post this one last time, but this has been answered by me about 10 times now.... just saying....
run these commands from the OS X or linux terminal command line:
cd to the directory that contains the fxz files, and run the following (make sure that the adb and fastboot commands are in your path, I will not include that here, you should google how to add things to your path):
Code:
fastboot erase userdata
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
jimbridgman said:
This needs to be added to to using the fastboot command that Farshad posted.
If you are doing this from OS X or linux, or well even windows, I posted a string of commands on how to flash these files using fastboot, there is a certain order, and there are files from the fxz you will need to skip.
Next time please do a search on this board for fastboot flash commands....
I will be nice and post this one last time, but this has been answered by me about 10 times now.... just saying....
run these commands from the OS X or linux terminal command line:
cd to the directory that contains the fxz files, and run the following (make sure that the adb and fastboot commands are in your path, I will not include that here, you should google how to add things to your path):
Code:
fastboot erase userdata
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
do you really have to erase before flashing? I always try to avoid formatting system, but I have not done this manually, so you may have to.
lkrasner said:
do you really have to erase before flashing? I always try to avoid formatting system, but I have not done this manually, so you may have to.
Click to expand...
Click to collapse
Yes if you don't you will most likely get an error when you try to flash system.img, over a different system version.
jimbridgman said:
This needs to be added to to using the fastboot command that Farshad posted.
If you are doing this from OS X or linux, or well even windows, I posted a string of commands on how to flash these files using fastboot, there is a certain order, and there are files from the fxz you will need to skip.
Next time please do a search on this board for fastboot flash commands....
I will be nice and post this one last time, but this has been answered by me about 10 times now.... just saying....
run these commands from the OS X or linux terminal command line:
cd to the directory that contains the fxz files, and run the following (make sure that the adb and fastboot commands are in your path, I will not include that here, you should google how to add things to your path):
Code:
fastboot erase userdata
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot flash userdata data.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Sorry I missed your other explanations. I did see a lot of posts with random fastboot commands, but pretty much none with any sort of explanation or rationale. Most of them seemed to be on the order of "Use these commands because I said so" or "I used these and they seem to work, I don't know why".
Do you have a writeup where you explain why should I flash with fastboot in a different order than is given in the fxz? And can you explain why you are skipping flashing most of the partitions? None of the instructions for using RSD Lite suggested removing nearly that many of the entries in the xml file, so I would like to know why I wouldn't want to flash the same things that RSD Lite would be flashing.
If you do have a canonical post explaining what needs to be done and why, I can ask the maintainer of the newbie information post to add a link to that post, so that it is easy to find and hopefully make it so that you don't have to post about it again. If that post doesn't exist, if you would like to give me enough information to write it, I am more than happy to write it up (crediting you for the info, of course), and then see about getting it added to the newbie post.
bemjb said:
Sorry I missed your other explanations. I did see a lot of posts with random fastboot commands, but pretty much none with any sort of explanation or rationale. Most of them seemed to be on the order of "Use these commands because I said so" or "I used these and they seem to work, I don't know why".
Do you have a writeup where you explain why should I flash with fastboot in a different order than is given in the fxz? And can you explain why you are skipping flashing most of the partitions? None of the instructions for using RSD Lite suggested removing nearly that many of the entries in the xml file, so I would like to know why I wouldn't want to flash the same things that RSD Lite would be flashing.
If you do have a canonical post explaining what needs to be done and why, I can ask the maintainer of the newbie information post to add a link to that post, so that it is easy to find and hopefully make it so that you don't have to post about it again. If that post doesn't exist, if you would like to give me enough information to write it, I am more than happy to write it up (crediting you for the info, of course), and then see about getting it added to the newbie post.
Click to expand...
Click to collapse
The reason is there are other files, and some are binary files that run commands and make changes to the bootloader, and other things, you do not need any of that to have a working phone. Some of them also open the bootloader to allow flashing, which is not needed if you erase the boot partition first. Any of those files like mbmloader, and anything with .bin after it will not work correctly unless you use RSDlite, it sends the signatures and such to the files that require it.
For getting your phone back up in a quick and dirty fashion we don't care about the signatures, we are assuming you got the fxz from a known source, by doing it this way.
You should do other research besides this site, pull apart a few roms, the fxz, and figure out how they work. Do some android research as to the boot process, etc. That how this kind of information is learned. The why in this case is less important. I would have to explain android and linux and how they boot as well in more detail here, but those are best left to the google and linux explanation sites.
This is not a process for a beginner, that is why it is not in the beginner thread. It has the possibility of hard bricking your phone if a mistype happens.
I am going to be 100% honest here, if you don't know any of the information I am referring to in this post, just use RSDlite, it has checks and safeguards that this process does not.
If you really want to learn about this, and not just asking questions because you don't understand, then jump in with us devs and start to learn, pull apart some ROMs flash a few ROMs, build a few ROMs, those things will teach you more than you will ever need to know about what files are and are not needed for a working phone. Also google is a good resource.
Also your boot.img and your recovery.img could be left out, since they are never touched by you or a ROM flash. I leave them in for a slight safeguard that your phone will actually be wiped clean.
P.S. I am a linux and OS X user myself, hence why I learned all of this a long time ago... I have been using and working on android since the G1 firat came out.
I also use bootcamp with win7 just to use RSDlite, when the need arises... that is not often, if you follow my process. It skips all the checking, processing that RSDlite does with using fastboot.
jimbridgman said:
The reason is there are other files, and some are binary files that run commands and make changes to the bootloader, and other things, you do not need any of that to have a working phone. Some of them also open the bootloader to allow flashing, which is not needed if you erase the boot partition first. Any of those files like mbmloader, and anything with .bin after it will not work correctly unless you use RSDlite, it sends the signatures and such to the files that require it.
For getting your phone back up in a quick and dirty fashion we don't care about the signatures, we are assuming you got the fxz from a known source, by doing it this way.
You should do other research besides this site, pull apart a few roms, the fxz, and figure out how they work. Do some android research as to the boot process, etc. That how this kind of information is learned. The why in this case is less important. I would have to explain android and linux and how they boot as well in more detail here, but those are best left to the google and linux explanation sites.
This is not a process for a beginner, that is why it is not in the beginner thread. It has the possibility of hard bricking your phone if a mistype happens.
I am going to be 100% honest here, if you don't know any of the information I am referring to in this post, just use RSDlite, it has checks and safeguards that this process does not.
If you really want to learn about this, and not just asking questions because you don't understand, then jump in with us devs and start to learn, pull apart some ROMs flash a few ROMs, build a few ROMs, those things will teach you more than you will ever need to know about what files are and are not needed for a working phone. Also google is a good resource.
Also your boot.img and your recovery.img could be left out, since they are never touched by you or a ROM flash. I leave them in for a slight safeguard that your phone will actually be wiped clean.
P.S. I am a linux and OS X user myself, hence why I learned all of this a long time ago... I have been using and working on android since the G1 firat came out.
I also use bootcamp with win7 just to use RSDlite, when the need arises... that is not often, if you follow my process. It skips all the checking, processing that RSDlite does with using fastboot.
Click to expand...
Click to collapse
Thanks for the rather comprehensive reply. Sadly, I do not have the time or inclination to build ROMs, in fact, I may not have dug into this at all if I had a Windows license, but I do not. So it is true that I didn't know all of the information that you mentioned in the post, but I had guessed a lot of it given the format of the xml file in the fxz and the names of the partitions. I just like to verify that my guesses are not incorrect, thus the questions. I do have plans to spend some time reading Google's official Android documentation, I just hadn't gotten there yet.
Anyways, while I am not interested in building ROMs, given the format of the xml file, it looks like it would be a fairly easy task to build a Java application that would read the XML file, check the MD5 sums, and then do the flashing just like RSD Lite. If I was to do something to contribute to the development effort, I'd probably start there. Don't know if I'll have time, but that's much more of a problem to me than a custom ROM. You mention signature checking: does RSD Lite actually check cryptographic signatures on the images themselves, or is it only checking the MD5s? (Feel free to ignore that question if you think I should spend some time Googling, if you don't answer, I'll get around to looking it up eventually)
P.S. I am an experienced Linux and OS X user. I only happen to be new to the Android world. (I was using webOS before this)
bemjb said:
Thanks for the rather comprehensive reply. Sadly, I do not have the time or inclination to build ROMs, in fact, I may not have dug into this at all if I had a Windows license, but I do not. So it is true that I didn't know all of the information that you mentioned in the post, but I had guessed a lot of it given the format of the xml file in the fxz and the names of the partitions. I just like to verify that my guesses are not incorrect, thus the questions. I do have plans to spend some time reading Google's official Android documentation, I just hadn't gotten there yet.
Anyways, while I am not interested in building ROMs, given the format of the xml file, it looks like it would be a fairly easy task to build a Java application that would read the XML file, check the MD5 sums, and then do the flashing just like RSD Lite. If I was to do something to contribute to the development effort, I'd probably start there. Don't know if I'll have time, but that's much more of a problem to me than a custom ROM. You mention signature checking: does RSD Lite actually check cryptographic signatures on the images themselves, or is it only checking the MD5s? (Feel free to ignore that question if you think I should spend some time Googling, if you don't answer, I'll get around to looking it up eventually)
P.S. I am an experienced Linux and OS X user. I only happen to be new to the Android world. (I was using webOS before this)
Click to expand...
Click to collapse
No worries.... I am and have been a unix linux architect for 20 years (yes I got a job as a sysadmin at 17), been using macs since the 80s, I don't own a machine with a fulltime windows install. I only recently installed win 7 on my bootcamp partition on my macbook just for rdslite, only used it twice....
I have a shell script that will flash the phone using the commands I posted, if you would like I can upload it and post a link tomorrow. My shell script works on both os x and linux.
If you you try to do EXACTLY what rsdlite does line by line it will FAIL, even with a java app. The bin files and the mbm files can only be utilized with RSDlite. RSDlite has SEVERAL checks that only it can do after each step.... If you want to restore the fxz using the mac or linux the shell script is the easiest, no real need for all the fluff, of rsdlite or an app. I have done it about 20 times now without issue, so have others on here.
Again, just let me know if you want my script and I will post it here.
And no it does not check the cryptographic signature of the bootloader, but the mbm program that rdslite runs, does check the signature of the boot image and the bootloader.
I was not implying that you actually jump into rom dev work.... just that, by doing some pulling apart and attempting it will teach you more than reading the android docs.
If you are a linux guy then hopefully you know what sec linux is, and how it uses signatures with the bootloader. That is similar to what motorola has done with their bootloader on their android phones.
Jim
Sent from my MB865 using xda premium
jimbridgman said:
No worries.... I am and have been a unix linux architect for 20 years (yes I got a job as a sysadmin at 17), been using macs since the 80s, I don't own a machine with a fulltime windows install. I only recently installed win 7 on my bootcamp partition on my macbook just for rdslite, only used it twice....
I have a shell script that will flash the phone using the commands I posted, if you would like I can upload it and post a link tomorrow. My shell script works on both os x and linux.
If you you try to do EXACTLY what rsdlite does line by line it will FAIL, even with a java app. The bin files and the mbm files can only be utilized with RSDlite. RSDlite has SEVERAL checks that only it can do after each step.... If you want to restore the fxz using the mac or linux the shell script is the easiest, no real need for all the fluff, of rsdlite or an app. I have done it about 20 times now without issue, so have others on here.
Again, just let me know if you want my script and I will post it here.
And no it does not check the cryptographic signature of the bootloader, but the mbm program that rdslite runs, does check the signature of the boot image and the bootloader.
I was not implying that you actually jump into rom dev work.... just that, by doing some pulling apart and attempting it will teach you more than reading the android docs.
If you are a linux guy then hopefully you know what sec linux is, and how it uses signatures with the bootloader. That is similar to what motorola has done with their bootloader on their android phones.
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
You do have a couple of years on me on Linux use, and definitely lots more years of Mac use, I didn't use Macs until OS X. But I think we've established geek cred quite effectively at this point. ;-)
Thanks for offering the script, but if it literally just runs the commands that you gave earlier, it would be simple for me to just toss one together myself. (Now, if you want to elaborate on the secret sauce in RSDLite, I'd be all ears.
I do know what SELinux is. I haven't looked into the specifics of how they use signatures with the bootloader, but I have a pretty good idea of ways that it could be implemented. It does make a lot of sense that Moto would do something similar to SELinux. Actually, I'm a little bit surprised that they're doing something similar and not just doing the same thing, but perhaps the bootloaders are different enough that they needed to roll their own signing. (Or they just did what a lot of people do and fell into NIH syndrome.)
Thanks,
Bem
jimbridgman said:
This needs to be added to to using the fastboot command that Farshad posted.
If you are doing this from OS X or linux, or well even windows, I posted a string of commands on how to flash these files using fastboot, there is a certain order, and there are files from the fxz you will need to skip.
Next time please do a search on this board for fastboot flash commands....
I will be nice and post this one last time, but this has been answered by me about 10 times now.... just saying....
run these commands from the OS X or linux terminal command line:
cd to the directory that contains the fxz files, and run the following (make sure that the adb and fastboot commands are in your path, I will not include that here, you should google how to add things to your path):
Code:
fastboot erase userdata
fastboot erase boot
fastboot erase system
fastboot erase recovery
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
Hm. My bootloader and I are not on very good terms atm :\
-It tells me "command restricted" when erasing system, recovery, or boot with fastboot. RSD Lite just says "FAIL."
-Also, it tells me "preflash validation failure" when flashing boot or recovery. RSD Lite again just says "FAIL"
-It also gives me the "preflash validation failure" when flashing system with fastboot. Moto-fastboot and RSD Lite both work. Maybe fastboot would work if we could erase system?
-Finally, we don't have a userdata.img
cogeary said:
Hm. My bootloader and I are not on very good terms atm :\
-It tells me "command restricted" when erasing system, recovery, or boot with fastboot. RSD Lite just says "FAIL."
-Also, it tells me "preflash validation failure" when flashing boot or recovery. RSD Lite again just says "FAIL"
-It also gives me the "preflash validation failure" when flashing system with fastboot. Moto-fastboot and RSD Lite both work. Maybe fastboot would work if we could erase system?
-Finally, we don't have a userdata.img
Click to expand...
Click to collapse
In the first line the fastboot command I referenced and that Farshad mentioned and linked to is the moto-fastboot command. You are supposed to rename the binary to fastboot, there was a readme at one time that explained that and was included with the download of moto-fastboot.
Also, yes we don't have a Userdata.img, but I pulled this from my own personal script, that I have been using since the G1 days, that was my first android phone. My script is not customized for just our phone, so the userdata.img line will fail, but since we don't need it, it is no big deal.
Jim
jimbridgman said:
In the first line the fastboot command I referenced and that Farshad mentioned and linked to is the moto-fastboot command. You are supposed to rename the binary to fastboot, there was a readme at one time that explained that and was included with the download of moto-fastboot.
Also, yes we don't have a Userdata.img, but I pulled this from my own personal script, that I have been using since the G1 days, that was my first android phone. My script is not customized for just our phone, so the userdata.img line will fail, but since we don't need it, it is no big deal.
Jim
Click to expand...
Click to collapse
Oh I see now . I typically use moto-fastboot but I never renamed it. Thanks for the clarification.
cogeary said:
Oh I see now . I typically use moto-fastboot but I never renamed it. Thanks for the clarification.
Click to expand...
Click to collapse
Yeah the reason to rename the binary/exe, was for compatibility with other scripts and programs in old days, when there was no odin or RSDlite, etc. I still do it, so that if someone does come up with some bad-assed way to do something via a script or other means for another phone, then I don't have to edit their script to reference the "moto-fastboot" binary/exe. I just rename the fastboot to fastboot-orig, or fastboot-google. If I ever change phones, and I will, I can rename the binary/exe again real easy.
Just one of those things I have learned over the years with both android and linux and well even in the old DOS and windows NT 3.51 and 4.0 command line days.
Hey, and thank you all here on the forums for all the guides and helpful information.
I am completely new at android rooting, flashing and all that comes with this, though I've read up quite a bit.
Now, my tablet is running the 4.2.1 build "JOP40D.WW_epad-10.6.1.14.10-20130801" which i've found can not be rooted in certain ways, so I went for the fastboot.
I've made sure everything was as should be, far as I can tell from what I've read here:
Tablet prepared:unlocked, usb debugging checked
adb and fastboot ready
correct drivers
latest twrp blow(openrecovery-twrp-2.6.3.2-tf700t.blob)
Then, as I put in the final command "fastboot -i 0x0B05 flash recovery twrp.blob" I get the message "error: out of memory" and the fastboot.exe crashed.
What could be causing this? Don't really want to try over again since I have no idea what I might be doing wrong and I really don't want to end up with the hassle of a bricked tablet.
Could it be an issue with the twrp version, and its compatibility with the tablet?
There is no lack of available memory on my computer, and there shouldn't be problems with the tablet's ROM or RAM, as it runs fine except for the obvious problem this tablet has. Previous to unlocking it was wiped and reset to stock 4.2.1 Jelly Bean with the .10 build.
The CMD window looks like this:
"
C:\users\Hbryne.Hbryne-PC>fastboot devices
015d2d431f240415 fastboot
C:\users\Hbryne.Hbryne-PC>cd c:\android-adb
c:\android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
error: out of memory
"
Thanks in advance for any helpful reply!
HBMoe said:
Hey, and thank you all here on the forums for all the guides and helpful information.
I am completely new at android rooting, flashing and all that comes with this, though I've read up quite a bit.
Now, my tablet is running the 4.2.1 build "JOP40D.WW_epad-10.6.1.14.10-20130801" which i've found can not be rooted in certain ways, so I went for the fastboot.
I've made sure everything was as should be, far as I can tell from what I've read here:
Tablet prepared:unlocked, usb debugging checked
adb and fastboot ready
correct drivers
latest twrp blow(openrecovery-twrp-2.6.3.2-tf700t.blob)
Then, as I put in the final command "fastboot -i 0x0B05 flash recovery twrp.blob" I get the message "error: out of memory" and the fastboot.exe crashed.
What could be causing this? Don't really want to try over again since I have no idea what I might be doing wrong and I really don't want to end up with the hassle of a bricked tablet.
Could it be an issue with the twrp version, and its compatibility with the tablet?
There is no lack of available memory on my computer, and there shouldn't be problems with the tablet's ROM or RAM, as it runs fine except for the obvious problem this tablet has. Previous to unlocking it was wiped and reset to stock 4.2.1 Jelly Bean with the .10 build.
The CMD window looks like this:
"
C:\users\Hbryne.Hbryne-PC>fastboot devices
015d2d431f240415 fastboot
C:\users\Hbryne.Hbryne-PC>cd c:\android-adb
c:\android-adb>fastboot -i 0x0B05 flash recovery twrp.blob
error: out of memory
"
Thanks in advance for any helpful reply!
Click to expand...
Click to collapse
It looks as if you ran the 'fastboot devices' command from a different directory than 'fastboot -i 0x0B05....'
You cd'd into c:\android-adb
You have to run the fastboot cmd out of the same directory your fastboot.exe is in. And twrp.blob has to be in that directory (or folder) too.
berndblb said:
It looks as if you ran the 'fastboot devices' command from a different directory than 'fastboot -i 0x0B05....'
You cd'd into c:\android-adb
You have to run the fastboot cmd out of the same directory your fastboot.exe is in. And twrp.blob has to be in that directory (or folder) too.
Click to expand...
Click to collapse
Ah, could that have caused it? Figured the connection check could be done from anywhere - maybe that's what triggered the error. Tried again - although now without the check since I know it's connected and recognized - and it worked :laugh:
Thanks!
berndblb said:
You have to run the fastboot cmd out of the same directory your fastboot.exe is in. And twrp.blob has to be in that directory (or folder) too.
Click to expand...
Click to collapse
Not true if fastboot is properly installed in a directory that is in the PATH.
_that said:
Not true if fastboot is properly installed in a directory that is in the PATH.
Click to expand...
Click to collapse
True - but very few do...
Sent from my XT894 using Tapatalk
need help
hi im new here
i have alot of problems need help guys
first i was in build ww6.5.0 and was in root yesterday asus push new update in ota i download it and when my device restart to start setup it stop
and get erorr when it bootup gave me this (your device is recoverd to the original configuration) then i delete root (frome super user) and download the update again
same prob
sec idownload the raw image frome asus offcial site ww6.5.0 and my device freez after boot to setup the image and i force it to shutdown after that i can't make factory reset
saying to me E:unable to write /cashe/recovery/command file
and i have no root now
today i downoade the new image UL-K00E-WW-6.6.1.0-user.zip it start fine and copy fiels but got errors too
:Eunable to rename file /cashe/update.zip: cross-device linkE:unable to write file
E:unable to write file: /cashe/update.zip
E:update flash failed
flash failed
fail(flash_cmds error!)
Bear with me: Right now my nexus is stuck in a bootloop. My nexus had been partially rooted, everytime i went to download the OTA 5.0.1. update it would just take me to TWRP, and i didn't know what to do with that. So I finally tried to fully root the phone, and also use TWRP to install the OTA update. Now I'm stuck, I've tried wiping the cache/factory reset. How do I got about flashing it back to stock without losing all my data?
(apologies for the title, I thought originally that I had killed mtp and adb, but I figured out how to get them back just after posting)
Thanks!
As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits
Ben36 said:
As I saw your post before the edit.... Stop using toolkits and read about adb. If it's bootlooping then it's 95% not bricked so don't panic and read the guides
Just download system.img you want and fastboot it
Edit -
Don't see this as me being mean or a ****. This is stuff everyone needs to know, it's really not hard at all so don't worry. Once you've used it a few times you'll wonder why you ever used toolkits
Click to expand...
Click to collapse
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.
The reason I say read the guides is simply it saves me or anyone else typing out a massive guide that already exists in many places.
If you're looping then something is more than likely wrong with the system not the data. So flashing just the system will keep your data safe (as long as you flash the same android version as you previously had, lollipop or kitkat)
You need to be in the bootloader not recovery and use the command fastboot flash system system.img
Google img's are here - https://developers.google.com/android/nexus/images
(just keep unzipping until you find the individual img files)
photobumm said:
I don't think you're being a ****. I'm very grateful for your input. I used to be very into jailbreaking when I had an iPhone, but i haven't been able to put the same time towards getting the hang of rooting (which I think has a steeper learning curve to begin with|). I sort of understand adb but I obviously need to learn more. I've been using the toolkit because it was simpler. I remember from trying to use adb before that I need to place the files I want to transfer in the same folder as adb (i think?) but I could never get that to work.
I also don't understand system.img.'s relevance here. I'm not getting the "Error: Update package missing system.img" error.
Click to expand...
Click to collapse
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!
_MetalHead_ said:
He's saying to flash a system image to get you up and running again, and I agree that that is what you should do. As far as placing the files in the same folder as adb and fastboot is concerned (you'll use fastboot to flash the image), you need to do just that. I created a folder on my desktop called "ADB" and that's where both adb and fastboot are, as well as all the files that I flash with fastboot ie. system images, recoveries, etc... Here's a great guide to get you going with adb and fastboot- http://forum.xda-developers.com/showthread.php?t=2277112
Now when you go to flash it, if you decide to use the flash-all.bat to flash everything (the full factory image) and bring you back to stock, you'll have to open the .bat file with a text editor and remove the "-w" from the script and that way it won't wipe your phone. If you want to just reinstall the OS without everything else (worth a shot), just flash the system with the command
Code:
fastboot flash system system.img
and that should get you running again. If what I just said is confusing, read the guide I posted and it should become clear.
Here is where you'll download the factory image from- https://developers.google.com/android/nexus/images
Just unzip it, pull the system.img out and place it in the same folder that fastboot is in and flash away.
And one final thing- definitely avoid toolkits at all costs. You spent a good chunk of change on your phone, take the time to learn how to mod it the correct way.
Good luck!
Click to expand...
Click to collapse
So I have adb and fastboot running. And I changed the flash-all.bat file. However, I don't understand what I do now? I downloaded the Hammerhead zip and it has a bunch of things in it. Which files do I put into the adb/fastboot folder and how do I then flash them?
In the hammerhead file it lists the bootloader, flash-all, radio and then a zip file "image-hammerhead...". What files am I using and what is the code that I input? Is this the same sa flashing a rom?
I also tried placing the system.img in the adb folder, and then using the
Code:
fastboot flash system system.img
but it gives me an error "cannot load 'system.img'
So now my issue is I get a "error: could not load 'system.img'. after running
Code:
fastboot flash system system.img [code/] . I also tried with boot.img. Same error.
I ran the "flash all" script, by accident, a screenshot of the terminal is attached.. I'm still stuck in a the boot loop, however, and if try to enter recovery mode an android lying down with a red triangle is present. The above "error: could not load..." is still present.
Create a folder and put fastboot in it.
So you unzipped the stock image. You said you have some images in the folder and a zip image.
Unzip that second zip.
There you will find the rest of the images you need.
Now take the recovery, bootloader, system, userdata, cache, and radio images and move them into the folder which you created for fastboot.
Rename the bootloader image to bootloader. img
Now when looking at that open folder containing all the images and fastboot hold down shift and left click and select "open command promt from window"
Type
/fastboot erase bootloader
/fastboot flash bootloader bootloader.img
/fastboot reboot-bootloader
/fastboot erase recovery
/fastboot flash recovery recovery.img
/fastboot erase radio
/fastboot flash radio radio.img
Repeat for the rest of the image files
Finally type /fastboot reboot
Profit.
---------- Post added at 10:54 PM ---------- Previous post was at 10:51 PM ----------
P. S. Make sure your phone is booted in fastboot mode first.
Oh and that android is stock recovery
U fixed it?
So for some reason I still kept getting that error. I ended up restoring to stock using the nexus root toolkit. So it all worked out in the end.
Hi all.
I have searched the forum for solution to my problem but can't seem to find it.
When trying to flash 5.1 I get an error
After,I try to flash all .img files manually. All flash normal except system.img
I searched forums, used Wugs tool, tried on different PC's (Windows 8.1 & Windows 7) tried with different fastboot versions but no result.
Older versions flash normal(5.0.1, 4.4.4, etc..)
Any suggestions?
How much ram the PCs have?
One has 8gb ram installed,another one has 16gb
arsen4oo said:
One has 8gb ram installed,another one has 16gb
Click to expand...
Click to collapse
Strange...
Can you pack the adbs and fastboots to a zip or rar and upload it to somewhere or give me a link which adb and fastboot you use. I am going to try flash 5.1 in 30 minutes.
Here they are.
I am downloading ubuntu to try flashing from there.
*Update.
Succeed flashing on Ubuntu. Don't understand what's wrong with Windows.
arsen4oo said:
Here they are.
I am downloading ubuntu to try flashing from there.
*Update.
Succeed flashing on Ubuntu. Don't understand what's wrong with Windows.
Click to expand...
Click to collapse
Using your binaries it flashed fine, I got no errors.
My specs: Windows 8.1 Pro 8GB ram.
What is different with my setup about ram management is that since I have an SSD as drive C I moved the pagefile.sys to my HDD.
I also have Microsoft Visual C++ 2008, 2010, 2012 redistributables installed. I have no idea if that counts
I don't think problem is caused by pagefile.
But seems many people have this issue when flashing 5.1
Flashing from ubuntu is an alternative solution..
I have no idea what the issue is but here is how I got round exactly the same error message on my Windows 7 machine.
Create a new local user (with admin rights) and then reboot your machine. Log in with that user and close any applications that try to auto-start. Then try the batch file and it should now work.
I think it must be related to memory/open applications. I have loads of stuff open in the background, i.e. in the systray, with my standard login. This new user had nothing. Using this user after a reboot seems to do the trick!
Try to download the nexus image again. It might be corrupted or extract it again using 7zip. Just flashed mine a while ago using "minimal adb and fastboot" on windows 7 x64 with 2gb of RAM. Machines doesn't have anything to do with adb flashing. It's the file itself or the adb drivers.
Edit: I see you've already sorted this out via ubunta machine. Good for you.
I had the same issue last night too. I downloaded the latest nexus USB drivers and the flash completed successfully.
Had the same issue. Spent all night unbricking my phone. One of the partitions didn't flash right and i left my phone over night and it still didn't boot up. got 2 hours of sleep.
Kitkat flashed fine though.
So what i did. im using minimal adb fastboot
1) flash 4.4.4 images
2) extract ALL 5.1 image files (boot, system, etc) into the minimal adb fastboot folder C:\\program files etc etc
3) flash each item manuall
-fastboot flash bootloader bootloadername.img
-fastboot flash radio radioname.img
-then do the same with boot, radio, system, userdata, cache. (fastboot flash "partition" "name".img) so if youre flashing boot, then boot boot.img
this should boot up just fine. 2-5 minutes tops.
Manual flashing fixes it
Thanks a lot russian392! Your instructions resolved the issue for me on Windows 7 Home Premium laptop with only 4GB RAM.
So in addition to the standard flashing instructions I did the following:
1. Unzip image-hammerhead-lmy47d.zip
2. In flash-all.bat change the following line:
Code:
fastboot -w update image-hammerhead-lmy47d.zip
to:
Code:
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
BorgKing said:
Thanks a lot russian392! Your instructions resolved the issue for me on Windows 7 Home Premium laptop with only 4GB RAM.
So in addition to the standard flashing instructions I did the following:
1. Unzip image-hammerhead-lmy47d.zip
2. In flash-all.bat change the following line:
Code:
fastboot -w update image-hammerhead-lmy47d.zip
to:
Code:
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Click to expand...
Click to collapse
yep you got it right :good:
I'm sure your issue will be solved if you do exactly what said in this video
Those videos helped me to flash 5.1 successfully
Sanjay Varma said:
I'm sure your issue will be solved if you do exactly what said in this video
Those videos helped me to flash 5.1 successfully
Click to expand...
Click to collapse
lol i got the idea from the same vid. Just ive flashed partitions manually before.
russian392 said:
lol i got the idea from the same vid. Just ive flashed partitions manually before.
Click to expand...
Click to collapse
lolz - though he is explaining well, I did mistakes as the commands and file names identically followed by each other
Hello, i want to reactivate my old acer A701 by flashing a newer img or zip.I have the following problems.When I try to do the recovery with a zip file on an sdcard i get the prop error.When i try to flash it by an img i always get i haven set the ANDROID_PRODUCT_OUT even when I do an export ANDROID_PRODUCT_OUT=/home/leopold/platform-tools.
A printenv shows the ANDROID_Product_OUT and the img is in platform-tools.
What is going wrong, what can i do?
You either apply Flash zip from sd from within Android's Recovery menu or you use external ADB Sideload command to flash a properly signed ZIP-file what contains the ROM, or you use external Fastboot Flash command to flash an IMG-file what requires device's bootloader is unlocked.
Hello and thank you,
like i wrote above, i want to flash it.Now i found at another place i have to write:
sudo ANDROID_PRODUCT_OUT="./" fastboot flashall recovery Az.img
when i do that, the flash is starting but then i get the error android-info.txt is missing.
So i guess i have a wrong image.
Does anybody have an image for the A701 with a newer android version.Or can give me a link.
My 4.1.1 does not recognice newer apps.
leopold
Take note that
Code:
fastboot flashall <ROM.IMG>
is to be used to flash a complete ROM, whereas
Code:
fastboot flash recovery <RECOVERY.IMG>
is to be used to flash only a Recovery.
Ok, i understand but i m lost.
I have some imagees and some zip files what should work on my a701.
If I use fastboot with img, i get no android-txt found.
if I work with adb reboot recovery and the zip files I will allways get the partition error prop undefined.
Can I supress the search for the android -txt?
What else can I do?
one of the zip files is from here https://acer.shreps.fr/, it is the said stable kitkat.
If you have access to a Windows computer then make use of a Flash Tool what's suitable to the tablet.
Unfortunately i can not find a flashtool for the nividia tegra3.
I have some zip files what should work on the a701 but all have the error check partition size [-Prop_UNDEFINED-) then the installation will be aborted.
Is there a way to eliminate the partition check.
Or does somebody have a zip or an img with a working update or recovery for a recent Android working on the a701?