Related
Hi,
Could someone please dump a system image for the 10.1? It's reeeealy easy
There are a few soft-bricks already due to people flashing the wrong image or to the wrong partition ( you know who you are, people! ) and you would be doing them a massive favour if you did.
If you already have busybox, all you have to do is run this:
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Then you can pick it up the system.img from /sdcard
Code:
adb pull /sdcard/system.img
ZIP it and upload it somewhere ( Dropbox ) and you're done!
TIA
BC
Http://droidbasement.com/galaxy/sys-backup
The system_extra backup contains extra stuff (from the 'tools' compilation).
Thanks. There are a couple of people who will really appreciate that
OT: I just repacked your su/busybox update with the boot.img from the Voda 10.1 and it works fine. Link to the Voda boot.img is here
Would it be possible to get the original system image without the extra tools? I am trying to flash this image however I keep getting a remote error when I do so. Could it have something to do with the fact that this image is 600MB compared to other system images that are around 200 MB like for the gt 10.1v? Thanks again for posting it.
the extra stuff is not making it 600mb (maybe 10-20). It is quite big on the IO.
In order to fastboot flash it you must have an unlocked bootloader to do so (which in unlocked by default on the IO).
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
nadewad said:
Ok so my bootloader is unlock however every time I try flashing this image i get the following:
sending 'system' (591872 KB)...
FAILED (remote: (00000006))
finished. total time: 0.002s
I am able to flash other system images no problem however, this one seems to be giving me some issues. Any other ideas to flash this image successfully? Thanks.
Click to expand...
Click to collapse
ill retake the dump and upload it. ill do it tonight. maybe some corruption ocurred, etc.
It might be the same trick where you have to create a sparse ext4 image instead of ripping the image straight, because fastboot transfers the entire image in RAM before flashing it...
Try
Code:
make_ext4fs -l 512m -s /sdcard/system.img /system
If anyone has created a system image but isn't quite sure if it is the correct one, I'll be glad to try it out as I am one of those people who soft bricked their device. Just PM me and I'll be more than happy to flash my device and verify the stability of the system image. Thanks.
Nader
bump? Did anyone end up getting a system image? Thanks.
Nader
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
nadewad said:
Ok so I was able to get a hold of another system image however, it still failed with the same error.
ydaraishy mentioned something about using make_ext4fs to make a sparse image? How is this done exactly? Is this through the adb shell or is this a separate tool that can be used on a linux machine. Any help on bringing my device back to life would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Run it on the device instead of using dd on the device.
ydaraishy said:
Run it on the device instead of using dd on the device.
Click to expand...
Click to collapse
He has a soft-bricked device so that's not an option unfortunately.
You can do a MD5 checksum of the file and get pershoot to check it against the original.
Otherwise, in the mean time, you can try this tool:
http://www.diskinternals.com/download/
You want the tool called "Linux Reader 2.0". It says it can only read ext2 and ext3, but I just tried it on my 10.1v system image which I created using the same method as pershoot, and it works fine.
...and see if you can mount it in Windows. If you can, the image is (probably) OK.
bcmobile said:
He has a soft-bricked device so that's not an option unfortunately.
Click to expand...
Click to collapse
Well, obviously, someone _else_ has to provide that image from a working device.
Same error here, while trying to flash the system.img. Any alternatives?
Thanks,
Eduardo.
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
nadewad said:
I just received another system image from a friend of mine who created it using make_ext4fs. It does flash successfully however, it still leaves my device in a boot loop. Whats the button combination to get the device into recovery mode?
I find it funny that the boot, recovery and system images for the galaxy tab 10.1v actually work and the device runs. Although the accelerometer, camera and usb don't work though.
Eduardo if you would like, you can PM me and I can share with you the dropbox folder of the system image that actually flashed to see if it would work on your device.
I think at this point I may just throw in the towel and send my device back to Samsung to get repaired :/
Thanks to everyone on the xda forums who tried helping me out. You guys are truly awesome
Click to expand...
Click to collapse
Samsung may charge you for the repair
Before you send it back, just have one more go at flashing the boot.img which smaskell provided from here. Just do a:
Code:
fastboot flash boot boot.img
The boot loop may be due to a different (incompatible) kernel if you still have the boot partition from the 10.1v
Failing that, if you're still up for it, do a:
Code:
adb logcat > %userprofile%\desktop\logcat-out.txt
...then open the locgat-out.txt file on your desktop and post the contents here or just zip and attach the file. That might give us something to work with
I am also not able to flash this system.img file. I get the same error.
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
nadewad said:
I did remember to flash the boot image of the 10.1 over the 10.1v. However, even when the device is booting up I still can't get access to the adb shell. Any ideas as to why I cannot access the adb shell?
I did notice though that when I had typed in:
fastboot getvar product
It had returned GT-P7100 which is the product number for the Galaxy Tab 10.1v, however the Galaxy Tab 10.1 has the product number GT-P7510.
Could this be because I had accidentally flashed the 10.1v rom or that these devices both use the same version of fastboot etc?
Click to expand...
Click to collapse
My tablet is showing P7100 as well. I tested with my employee's GT LE, and it shows the same. So, this is not the problem...
adb is not accessible to me as well.
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.
Hey guys. So I've been trying to manually update with no success so far. I was going to sideload, but I got the November security update ota and there is no ota file for LMY48X to Marshmallow (as far as I know). So I bit the bullet and unlocked the bootloader yesterday, and got the adb and fastboot set up and tried to run the ./flash-all.sh command. (I'm on a Mac) Everything was going fine until I came across an error. So I basically gave up and restored all my user data.
Today I figured I'd try again since I have already unlocked my bootloader and have nothing to lose. mra58k didn't work, so I figured I'd try the mra58n image and removed the -w command from the flash-all.sh and tried again. This is what I got:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(69137) malloc: *** mmap(size=2094391296) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 2092296104 bytes
error: update package missing system.img
Can anyone help me out? I have a feeling I won't be getting the ota through my phone anytime soon.
I may be wrong as this is a pure guess, but did you check the download to confirm it met the checksum? You might just try deleting your download and redownloading the latest version.
haibane said:
I may be wrong as this is a pure guess, but did you check the download to confirm it met the checksum? You might just try deleting your download and redownloading the latest version.
Click to expand...
Click to collapse
No it is Google. Same here. Flashall.bat stops after flashing m-bootloader and m-radio.
After that it is needed to extract all the images and fastboot flash every image.
Don't use the flash-all.sh file to flash, flash the files manually. Plenty of guides outline the commands to use. Plus, make sure that you're Android SDK Tools is updated to the latest version.
RMarkwald said:
Don't use the flash-all.sh file to flash, flash the files manually. Plenty of guides outline the commands to use. Plus, make sure that you're Android SDK Tools is updated to the latest version.
Click to expand...
Click to collapse
Thanks for the reply. So I went ahead and followed your advice and tried to do it manually. I checked everything was up to date. I flashed the bootloader, radio, recovery and boot images and rebooted the bootloader between every flash with no incident. Then I tried to flash the system.img and it first everything seemed to be ok but the terminal is stuck at "sending sparse 'system' " and hasn't done anything in 20 minutes. I'm afraid to do anything right now. Is it ok to close terminal, reopen it and try flashing the system.img again?
ICStevenC. said:
Thanks for the reply. So I went ahead and followed your advice and tried to do it manually. I checked everything was up to date. I flashed the bootloader, radio, recovery and boot images and rebooted the bootloader between every flash with no incident. Then I tried to flash the system.img and it first everything seemed to be ok but the terminal is stuck at "sending sparse 'system' " and hasn't done anything in 20 minutes. I'm afraid to do anything right now. Is it ok to close terminal, reopen it and try flashing the system.img again?
Click to expand...
Click to collapse
Hmmm...the system.img does take time but shouldn't take 20 minutes. Did you flash all the .img files separately, or did you use the command:
Code:
fastboot -w update image-shamu-mra58n.zip
?
I've never done any of this from a Mac, only Linux and Windows, but here's what I do when flashing manually. I extract the contents of the factory image zip, AND the image-shamu-mra58n.zip into my SDK directory (see image attached).
Once everything is extracted, after backing up things I wanna save on my device, I boot to the bootloader and go to town:
Code:
fastboot erase boot
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot erase system
Code:
fastboot erase userdata
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
Code:
fastboot reboot-bootloader
Code:
fastboot flash radio radio-shamu-d4.01-9625-05.27+fsg-9625-02.104.img
Code:
fastboot reboot-bootloader
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash cache cache.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot reboot
RMarkwald said:
Hmmm...the system.img does take time but shouldn't take 20 minutes. Did you flash all the .img files separately, or did you use the command:
Code:
fastboot -w update image-shamu-mra58n.zip
?
Click to expand...
Click to collapse
No, I decompressed that zip and flashed them all separately using the
Code:
./fastboot flash
command and dragging the files directly to the terminal and then using
Code:
./fastboot reboot-bootloader
in between every flash.
ICStevenC. said:
No, I decompressed that zip and flashed them all separately using the
Code:
./fastboot flash
command and dragging the files directly to the terminal and then using
Code:
./fastboot reboot-bootloader
in between every flash.
Click to expand...
Click to collapse
Okay, seems like you're on the right path. See my post above. You'll erase everything first, then flash everything back one by one, kinda like what you are already doing. I've never had issues doing it this way ever, it may be overkill and it will wipe your phone completely, but if you've backed things up (pictures, docs, music, etc) beforehand, no biggie. The only times I reload the bootloader is after flashing the bootloader, and then the radio.
The system.img will take the longest, and userdata will take a little time too, but the others should be almost instant.
RMarkwald said:
Okay, seems like you're on the right path. See my post above. You'll erase everything first, then flash everything back one by one, kinda like what you are already doing. I've never had issues doing it this way ever, it may be overkill and it will wipe your phone completely, but if you've backed things up (pictures, docs, music, etc) beforehand, no biggie. The only times I reload the bootloader is after flashing the bootloader, and then the radio.
The system.img will take the longest, and userdata will take a little time too, but the others should be almost instant.
Click to expand...
Click to collapse
The terminal doesn't appear to be responding to any command now. I tried erasing boot and after pressing enter, nothing happened. Closing it and reopening it doesn't help. Should I try restarting my computer?
ICStevenC. said:
The terminal doesn't appear to be responding to any command now. I tried erasing boot and after pressing enter, nothing happened. Closing it and reopening it doesn't help. Should I try restarting my computer?
Click to expand...
Click to collapse
Yeah, give that a shot. As long as you have bootloader access you will be okay.
RMarkwald said:
Yeah, give that a shot. As long as you have bootloader access you will be okay.
Click to expand...
Click to collapse
I am now on 6.0 and everything appears to be functional. Thank you so much for all your help! I really appreciate it.
Awesome man! Glad I could help.
This is my Situation:
I was using a ROM Based in Android 5.1.1 in specific ([5.1.1_r29] Team Razor), everything was good but I read that I had to update bootloader and radio but never saw a link, looking for internet for help found this GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml.zip version to install via RSD Lite, everything was good, but when I tried to flash the recovery I get that I couldnt flash it 'cuz is not compatible:
Code:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 6.193s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.660s
My device start normally, but I want too install the Recovery and root it, I couldnt find any information about my problem or a real solution.
I've read about flash a system.img but what "system.img"?, I'm looking for some help, if anyone pass thru this and have the answer would be awesome if you share it.
Thank you in advance.
[SOLVED]
Unzip mfastboot.exe into \platform-tools\
flashing: mfastboot flash recovery recovery.img
done!
The info in your post is kind of confusing. What does ghost_retail*.xml.zip have to do with looking for a custom recovery which is what I am guessing you want on your "working" device? All you could get out of the .xml.zip file would be something like stock_recovery.img which wouldn't allow you do recoveries. Sounds like you want to download TWRP (or Philz) from somewhere and boot into fastboot mode, then use "fastboot flash recovery {whatever_recovery.img}" to flash the custom recovery.
If that's not your intent then post back and try to explain better. It seems like you had things "working well" on TR511 but still decided to update BL & Rad anyway. There's no need to update anything if it's all working OK and there's no new features (like a working speakerphone or something) in there for you.
Also: the 'reported output' in your
Code:
section is pretty inconclusive for troubleshooting. It almost sounds as if you tried to flash (or RSDLite) something huge like the entire image (805,306,368 bytes?). I've built lots of recoveries and they average more like 5-10MB. , not 800MB. Also it says something about "battery low" in there. I'm lost on that output ;;)
And another note: System.img has little or nothing to do with getting recovery back together. It's just the packed up version of /system/.... in the "SYSTEM" partition.
Maybe for starters: tell us once again what ROM is working right now including version. Then tell us what recovery you want to flash. Someone can likely help out if we know those things. You appear to have unlocked BL since you're flashing ROMs so there's hope.
Anyway, good luck.
[QUOTE="Mexickano, post: 64350799, member: 4488447"]This is my Situation:
I was using a ROM Based in Android 5.1.1 in specific ([5.1.1_r29] Team Razor), everything was good but I read that I had to update bootloader and radio but never saw a link, looking for internet for help found this[B] GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml.zip[/B] version to install via RSD Lite, everything was good, but when I tried to flash the recovery I get that I couldnt flash it 'cuz is not compatible:
[code](bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 6.193s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.660s
My device start normally, but I want too install the Recovery and root it, I couldnt find any information about my problem or a real solution.
I've read about flash a system.img but what "system.img"?, I'm looking for some help, if anyone pass thru this and have the answer would be awesome if you share it.
Thank you in advance.[/QUOTE]
I was on 5.1.1 and downgraded to 5.1 stock, everything ok till now?
when I'm trying to flash TWRP this appears
Code:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 6.193s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.660s
Mexickano said:
I was on 5.1.1 and downgraded to 5.1 stock, everything ok till now?
when I'm trying to flash TWRP this appears
Code:
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (8498 KB)...
OKAY [ 6.193s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 7.660s
Click to expand...
Click to collapse
Thanks. I'm assuming the battery low message is just a confused response and not really true? Also, I see that the recovery.img (whatever you are calling TWRP) is ~8.5MB which seems fine. It looks like fastboot on the PC (whatever) isn't happy talking to the xt1053 booted into fastboot/bootloader. Could you try doing a "fastboot devices" and show the output back here? If it's anything other than an OK ID number for the device, then it might be interesting.
I'll attach a version of fastboot I just recently used to flash a recovery in case you want to try it.
Another thing: I've never had this happen myself, but have heard about it a few times: When booted, use some explorer to look in your /system folder for a file with a name like this "recovery-from-boot.p". If it's there, supposedly it will keep forcing the default non-custom recovery to be written regardless of what you do. I'm sure there's a work-a-round for that like ..
What about using the "Fastboot boot "your-custom-recovery.img" if you have that "recovery-from-boot.p" problem? It should take you into the recovery you're trying to write without bothering to write it to the recovery partition. From there, you would be root if you can open the TWRP console, and get rid of the recovery-from-boot.p file, install root, etc, then finally, flash recovery with whatever combination of stuff ^^ it takes.
hachamacha said:
Thanks. I'm assuming the battery low message is just a confused response and not really true? Also, I see that the recovery.img (whatever you are calling TWRP) is ~8.5MB which seems fine. It looks like fastboot on the PC (whatever) isn't happy talking to the xt1053 booted into fastboot/bootloader. Could you try doing a "fastboot devices" and show the output back here? If it's anything other than an OK ID number for the device, then it might be interesting.
The battery message is because the Battery is low, that's it, no big deal.
I can boot into fastboot w/o issues and I will post back the result of "fastboot devices".
I'll attach a version of fastboot I just recently used to flash a recovery in case you want to try it.
how can I use it, excuse my ignorance, but I see a .exe inside a .zip
Another thing: I've never had this happen myself, but have heard about it a few times: When booted, use some explorer to look in your /system folder for a file with a name like this "recovery-from-boot.p". If it's there, supposedly it will keep forcing the default non-custom recovery to be written regardless of what you do. I'm sure there's a work-a-round for that like ..
What about using the "Fastboot boot "your-custom-recovery.img" if you have that "recovery-from-boot.p" problem? It should take you into the recovery you're trying to write without bothering to write it to the recovery partition. From there, you would be root if you can open the TWRP console, and get rid of the recovery-from-boot.p file, install root, etc, then finally, flash recovery with whatever combination of stuff ^^ it takes.
Click to expand...
Click to collapse
There's a "recovery-from-boot.p" but I cant delete it or change the name because I'm not root, can I be root without installing Recovery?
Mexickano said:
There's a "recovery-from-boot.p" but I cant delete it or change the name because I'm not root, can I be root without installing Recovery?
Click to expand...
Click to collapse
Should be able to work around that, but the workaround is to find a way to become root, so I was mentioning this in the last post of mine:
What about using the "Fastboot boot "your-custom-recovery.img" if you have that "recovery-from-boot.p" problem? It should take you into the recovery you're trying to write without bothering to write it to the recovery partition. From there, you would be root if you can open the TWRP console, and get rid of the recovery-from-boot.p file, install root, etc, then finally, flash recovery with whatever combination of stuff ^^ it takes.
Click to expand...
Click to collapse
I'm trying to think of ways to do this above and I think that is actually one of them and there should be another way as well.
Way one: There's a fastboot command "fastboot boot "{name-of-your-recovery-img-for-twrp}". That command causes it to boot (well, if all goes well) into recovery without writing recovery. If it works, you're a root user because that's how recovery is. In TWRP, I'm sure there's a console command as well as a file explorer or some kind. You'll have to remount as read-write /system partition. From a console it'd look like this "sudo mount -o remount,rw /system" (I'm pretty sure that's it). You can look it up or try it with a w where the rw is right now. Also you can just do a plain "mount" command and look at the output to see what it's mounted as in case you need it.
If you get into whatever file explorer twrp has available, then navigate to that file 'recovery_from_boot.p' and see if the file system is in read-write mode by trying to rename it (like to recovery_from_boot.p.orig). If that doesn't work, then go to the special commands or advanced (sorry, not recalling twrp that well) and mount /system as read-write whatever that takes, like an unmount & a mount. Then go back to file explorer and do the rename. I hate deleting files I'm not 100% sure about, but you can do what you like there.
Way two: If you can boot into the version of twrp.img on your PC, then I'm not seeing why you can't install root from it too. Worth a try. You might have some other remaining problem between whatever fastboot you've got on the pc and the bootloader, but it's worth a shot. There's a number of write-ups on how to do this if you google it. Anyway, once you've rooted you can reboot and you should only lose recovery, not root. Once booted, install supersu, etc. usual stuff, then if it all checks out, flash the recovery and it should stay once you've dumped that file.
Way two and a half: If I understand how the normal boot works on androids, then you should be able to avoid having recovery erased at least one time by using the buttons either to go directly to recovery (volume_up + power) or (volume_down+volume_up + power) RIGHT after you flash recovery. I'm just thinking that /system isn't going to execute if you pick the right combo of buttons to get into recovery but it'll be a pita because you have to burn recovery then hit it on the first boot after or it's gone.
Cheers.
hachamacha said:
Way one: There's a fastboot command "fastboot boot "{name-of-your-recovery-img-for-twrp}". That command causes it to boot (well, if all goes well) into recovery without writing recovery. If it works, you're a root user because that's how recovery is. In TWRP, I'm sure there's a console command as well as a file explorer or some kind. You'll have to remount as read-write /system partition. From a console it'd look like this "sudo mount -o remount,rw /system" (I'm pretty sure that's it). You can look it up or try it with a w where the rw is right now. Also you can just do a plain "mount" command and look at the output to see what it's mounted as in case you need it.
there is a "recovery-from-bot.p", I cant delete it, rename it or anything else since I aint get root privileges.
I can get into fastboot and when I type fastboot devices I get:
TA0000143X fastboot
If you get into whatever file explorer twrp has available, then navigate to that file 'recovery_from_boot.p' and see if the file system is in read-write mode by trying to rename it (like to recovery_from_boot.p.orig). If that doesn't work, then go to the special commands or advanced (sorry, not recalling twrp that well) and mount /system as read-write whatever that takes, like an unmount & a mount. Then go back to file explorer and do the rename. I hate deleting files I'm not 100% sure about, but you can do what you like there.
Way two: If you can boot into the version of twrp.img on your PC, then I'm not seeing why you can't install root from it too. Worth a try. You might have some other remaining problem between whatever fastboot you've got on the pc and the bootloader, but it's worth a shot. There's a number of write-ups on how to do this if you google it. Anyway, once you've rooted you can reboot and you should only lose recovery, not root. Once booted, install supersu, etc. usual stuff, then if it all checks out, flash the recovery and it should stay once you've dumped that file.
I cant boot into recovery because I can't flash the Recovery, that's the reason why I created this topic because I CANT flash recovery.
Way two and a half: If I understand how the normal boot works on androids, then you should be able to avoid having recovery erased at least one time by using the buttons either to go directly to recovery (volume_up + power) or (volume_down+volume_up + power) RIGHT after you flash recovery. I'm just thinking that /system isn't going to execute if you pick the right combo of buttons to get into recovery but it'll be a pita because you have to burn recovery then hit it on the first boot after or it's gone.
I cant get into Recovery because there is no Recovery flashed.
What about that fastboot.zip, how I flash it or install it because I see a fastboot.exe inside the zip.
Cheers.
Click to expand...
Click to collapse
I need to know if there's a way to flash another bootloader or anything else?
If I try to delete the "recovery-from-boot.im" in fastboot this message appear:
X:\Android\sdk\platform-tools>fastboot erase /system/recovery-from-boot.img
(bootloader) Variable not supported!
erasing '/system/recovery-from-boot.img'...
(bootloader) Invalid partition name /system/recovery-from-boot.img
FAILED (remote failure)
finished. total time: 0.094s
FINALLY!!
I solved putting mfastboot.exe into /platform-tools/ and typing
mfastboot flash recovery [recovery].img
Thank you for your effort and time.
Mexickano said:
I need to know if there's a way to flash another bootloader or anything else?
If I try to delete the "recovery-from-boot.im" in fastboot this message appear:
X:\Android\sdk\platform-tools>fastboot erase /system/recovery-from-boot.img
(bootloader) Variable not supported!
erasing '/system/recovery-from-boot.img'...
(bootloader) Invalid partition name /system/recovery-from-boot.img
FAILED (remote failure)
finished. total time: 0.094s
FINALLY!!
I solved putting mfastboot.exe into /platform-tools/ and typing
mfastboot flash recovery [recovery].img
Thank you for your effort and time.
Click to expand...
Click to collapse
Cool! I think I also was trying to say "try other versions of fastboot" (like mfastboot). Good deal.
I have been away from Android for a little while - but I'm coming to sell my Nexus 6, and so I'm attempting to flash the latest OS from google.
I downloaded 6.0.1 from google, and then worked through these steps:
fastboot flash bootloader C:/image-shamu-XXXXXX/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-shamu-XXXXXX/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-shamu-XXXXXX/system.img
Yes, there are more steps, but I just can't get to them! Once I flash system I get the following...
target reported max download size of 536870912 bytes
sending sparse 'system' (517178 KB)...
OKAY [ 25.080s]
writing 'system'...
OKAY [ 7.142s]
sending sparse 'system' (515137 KB)...
OKAY [ 25.155s]
writing 'system'...
OKAY [ 7.346s]
sending sparse 'system' (515644 KB)...
Thats it, thats as far as it ever goes, then I just sit there waiting, waiting, and nothing happens.
Any suggestions?
Updated Android SDK Tools to make sure you have the latest fastboot? If you haven't updated, update these.
Here's the commands I run, keep in mind this will completely wipe all data/apps/files from the device, so backup anything you want saved to a computer before doing this. Is it overkill? Sure, but I've never had an issues across multiple devices, so since, for me at least, if it isn't broke I'll keep doing this:
Erase:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Flash bootloader:
Code:
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
Flash radio:
Code:
fastboot flash radio "name of radio"
fastboot reboot-bootloader
Flash img files:
NOTE: The system.img is large, so if your Android SDK tools isn't updated, you could get an error. This part does take a few minutes to do, so be patient and give it time to complete.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Reboot device:
Code:
fastboot reboot
Just a thought, prompted by the commands in the original post referring to the C: drive. I didn't even know you could do this, though I suppose it makes sense. The easier method IMO is to copy or move all the image files to the ADB/Fastboot folder, rename them if necessary for simpler typing, then just "fastboot flash system system.img", etc., as RMarkwald says.
I doubt that it will make any difference, but since you appear to be stuck it might be worth trying - worst case, it fails again...
And just for curiosity, did you try flash-all.bat? I know that people have trouble with it and fall back on the separate flashing steps - just wondering if that's why you're doing it this way.
dahawthorne said:
Just a thought, prompted by the commands in the original post referring to the C: drive. I didn't even know you could do this, though I suppose it makes sense. The easier method IMO is to copy or move all the image files to the ADB/Fastboot folder, rename them if necessary for simpler typing, then just "fastboot flash system system.img", etc., as RMarkwald says.
I doubt that it will make any difference, but since you appear to be stuck it might be worth trying - worst case, it fails again...
And just for curiosity, did you try flash-all.bat? I know that people have trouble with it and fall back on the separate flashing steps - just wondering if that's why you're doing it this way.
Click to expand...
Click to collapse
Good call on the movement of files to the adb/fastboot folder, as that is what I do when flashing these files, and the flash-all.bat potentially causing his issues.
RMarkwald said:
Updated Android SDK Tools to make sure you have the latest fastboot? If you haven't updated, update these.
Here's the commands I run, keep in mind this will completely wipe all data/apps/files from the device, so backup anything you want saved to a computer before doing this. Is it overkill? Sure, but I've never had an issues across multiple devices, so since, for me at least, if it isn't broke I'll keep doing this:
Erase:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Flash bootloader:
Code:
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
Flash radio:
Code:
fastboot flash radio "name of radio"
fastboot reboot-bootloader
Flash img files:
NOTE: The system.img is large, so if your Android SDK tools isn't updated, you could get an error. This part does take a few minutes to do, so be patient and give it time to complete.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Reboot device:
Code:
fastboot reboot
Click to expand...
Click to collapse
Having all kinds of trouble rerooting my 6. Will this relock the bootloader? Wanted to keep user data but if a fresh start is what I need then OK. TIA
Mongo23ny said:
Having all kinds of trouble rerooting my 6. Will this relock the bootloader? Wanted to keep user data but if a fresh start is what I need then OK. TIA
Click to expand...
Click to collapse
No, you have to run "fastboot oem lock" to lock the bootloader, not recommended.
You perform above steps, boot device and go through setup, enable USB debugging, boot to bootloader and flash TWRP, boot to TWRP. You will need to clean up some space to flash SuperSU (you'll have to remove apps from /system/app or /system/priv-app), as there will not be any space on /system to install/flash anything that needs to live there, it either won't work or error out. Once you have removed system apps and create space on /system, you can flash your SuperSU zip, then reboot the phone.
RMarkwald said:
No, you have to run "fastboot oem lock" to lock the bootloader, not recommended.
You perform above steps, boot device and go through setup, enable USB debugging, boot to bootloader and flash TWRP, boot to TWRP. You will need to clean up some space to flash SuperSU (you'll have to remove apps from /system/app or /system/priv-app), as there will not be any space on /system to install/flash anything that needs to live there, it either won't work or error out. Once you have removed system apps and create space on /system, you can flash your SuperSU zip, then reboot the phone.
Click to expand...
Click to collapse
I don't wanna relock the bootloader. Not sure what to remove from system apps, etc. This was not this difficult the first time I rooted. Thanks for any and all help.
This is off-topic from the original question, but let's go with it...
Personally I've never had to remove anything from system. Clean install, flash TWRP (or just temporarily boot into it), flash SuperSU v2.67. Job done. Since it (probably) doesn't try to install into system, there shouldn't be any problem.
@dannstarr - you haven't answered my question.
dahawthorne said:
This is off-topic from the original question, but let's go with it...
Personally I've never had to remove anything from system. Clean install, flash TWRP (or just temporarily boot into it), flash SuperSU v2.67. Job done. Since it (probably) doesn't try to install into system, there shouldn't be any problem.
@dannstarr - you haven't answered my question.
Click to expand...
Click to collapse
Do I keep system read only in twrp 3.0.0.0?
Disregard, did everything suggested by rmarkwald and dahawthorne. Worked well, took some security update that happened to get rid of the corrupt phone boot message. Flashed twrp 3.0.0.0 and installed SuperSU 2.67 with no problems. Thanks all.