I dumped the boot.img using:
Code:
cat /dev/mtd/mtd1 > /sdcard/cat-boot.img
and
Code:
dump_image boot /sdcard/dump-boot.img
Using dump_image it says:
Code:
mtd: read all-zero block at 0x00240000; skipping
mtd: read all-zero block at 0x002a0000; skipping
mtd: read all-zero block at 0x002c0000; skipping
And the sizes differ:
cat-boot.img: 4096K
dump-boot.img: 3712K
Then I ran unpackbootimg to unpack them. Neither worked, invalid gz files. So I took a look at the image files and instead of 2K header, it had a 4K header that had an extra 2K of 0's. Any idea why that might be?
I deleted the extra 2K of 0's and ran unpackbootimg again, both boot images provided identical gz's that worked.
I am able to test the gz's and extract the cpio, but how can I check if the kernel is good?
Since it seems to be malformed, it might have different spacing or something?
If I try to boot off of it using fastboot it just gives an error:
Code:
C:\android-sdk\tools>fastboot boot pulled\extracted\dump-boot.img-zImage
creating boot image...
creating boot image - 2263040 bytes
downloading 'boot.img'... OKAY [ 2.687s]
booting... FAILED (remote: invalid boot image)
finished. total time: 2.687s
Could someone with some experience take a look and help? I'm doing my best
The attached file has the extra 2K of 0's in the header I mentioned already removed.
Edit: I did the dump while the phone was booted up normally. It doesn't have any recovery mode where I could otherwise do it. If I use "adb reboot recovery" it just formats the phone and reboots.
Edit 2:
After doing a bunch of searching I tried this:
Code:
fastboot -b 400000 -n 4096 boot pulled\extracted\dump-boot.img-zImage pulled\extracted\dump-b
oot.img-ramdisk.gz
And it worked!!
Now I can try to port Clockwork Recovery
Edit 3: removed attachment, extracted version is attached to next post.
I attached the extracted kernel and ram disk here so anyone can use them without having to bother taking them apart themselves.
To fix a broken boot image, get the Andriod SDK installed, plug in the phone, reboot holding both green and red buttons to get to fastboot screen. Then use fastboot.exe to load image. Try to boot off it before flashing it. In order to flash it the "flash:raw boot" fastboot option will need to be used. I haven't tried this, but I've booted off of my extracted version and that worked.
The base address is "400000" and the page size is "4096" those need to be specified in the fastboot options.
Also just for reference, the extracted file "boot.img-cmdline" had this in it:
mem=215M console=ttyMSM2,115200n8 androidboot.hardware=qcom
Click to expand...
Click to collapse
Not sure where or when that's needed yet, not for flashing, but maybe for compiling.
Sanyo zio m6000
I have locked myself out of my phone. I was wondering if you could upload/send me the boot image you used. I have tried all the ones you have for download, but none work.
Any updates on this? I think this is suspect as to why nandroid restore borks the kyocera boot splash screen.
Sent from my Zio using XDA App
I know this is off topic so excuse me but myprepaiddroid.com has some rom's that have been converted to the zio on cricket but they have not been tested yet.
So is the kernel in the boot image?
http://db.tt/zisPRYH boot.img after 2.2.1 update.
Sent from my Zio using XDA Premium App
That extra 2k of 0s in the header is the kyocera logo (or the instruction that points to the actual image).
Would you mind unpacking the 2.2 boot.img zImage and Ramdisk and posting them phazei?
Is phazei around anymore?
Sent from my Zio using XDA Premium App
Mattix724 said:
Is phazei around anymore?
Click to expand...
Click to collapse
Haha, yeah, I'm here. Just been busy, life's been getting me down. Foreclosure, and other misc stuff.
I browse the forum a couple times a week or so.
Sweet. Do you know if there was any change to the boot.img after 2.2?
Sent from my Zio using XDA Premium App
Related
I have already successfully removed the boot and shutdown animations (incl. sound) via "adb shell" commands:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
mv /system/media/bootani.qmg /system/media/_bootani.qmg
mv /system/media/samsungani.qmg /system/media/_samsungani.qmg
mv /system/media/video/shutdown/shutdown.qmg /system/media/video/shutdown/_shutdown.qmg
mv /system/media/audio/ui/PowerOff.wav /system/media/audio/ui/_PowerOff.wav
mv /system/etc/PowerOn.snd /system/etc/_PowerOn.snd
mv /system/etc/PowerOn.wav /system/etc/_PowerOn.wav
mount -o remount,ro /dev/mtdblock3 /system
exit
or just download the attached shell script and execute it as su:
adb push nobootani.sh /data/local/nobootani.sh
adb shell
Code:
su
cd /data/local
chmod 777 nobootani.sh
./nobootani.sh
exit
Btw the tablet now boots much faster.
But the boot splash screen from Samsung is still there.
EDIT:
I found out that the boot logo is actually a JPEG image located in the Secondary Bootloader (sbl.bin) on partitions bml4 and bml5 (both are identical on my Tab).
The partion layout seems to be the same as for the Galaxy S series:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S#Modifications
(here you can also find the secret codes to check firmware etc.)
This command gives the partition info:
cat /proc/LinuStoreIII/bmlinfo
To dump any partition (e.g. SBL) to SD card:
dd if=/dev/block/bml4 of=/sdcard/bml4_dump bs=1
I attached the extracted boot logo.
Thanks xdadevel,
Followed your instructions above and it worked like a charm - my Tab boots up MUCH faster now.
I think to remove the Samsung boot logo you would have to edit something like init.rc in the bootimg, repackage it, and then copy it across.
Im trying to do this and get
Can not mount permission denied.
Failed for bootani.qmg, Read-only system file.
Any ideas?
xdadevel said:
I have already successfully removed the boot and shutdown animations (incl. sound) via "adb shell" commands:
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
cd /system/media
rm bootani.qmg
rm samsungani.qmg
cd /system/media/video/shutdown
rm shutdown.qmg
cd /system/media/audio/ui
rm PowerOff.wav
cd /system/etc
rm PowerOn.snd
rm PowerOn.wav
mount -o remount,ro /dev/mtdblock3 /system
exit
Btw the tablet now boots much faster.
But the boot splash screen from Samsung is still there.
I've been reading about the methods for other Samsung devices, such as:
flashing a PDA tar with Odin
fastboot flash splash1
packing the logo png as an update.zip
None of these worked.
Instead I bricked my tablet and flashed "P1_20100909.pit" and "GT-P1000_P1000XXJK1.rar" (from samfirmware.com) to make it work again.
Click to expand...
Click to collapse
Very easy, thanks for the idea! I copied the files to my external SDcard just in case though... Maybe it would be nice for you to remind people of that. Cheers!
mklass said:
Im trying to do this and get
Can not mount permission denied.
Failed for bootani.qmg, Read-only system file.
Any ideas?
Click to expand...
Click to collapse
Have you rooted your phone?
smithdc said:
Have you rooted your phone?
Click to expand...
Click to collapse
Yes it is
Cheers
I hope this work on the US TMobile verison?
Sent from my Samsung Galaxy Tab
It does work on the U.S. TMobile tab, I tried it. to me it boots faster, but seems to shut down slower.
Thanks! I follow your instruction but instead of deleting, I just rename them with .old extension (maybe one day will need them.. who knows.. )
Now it boot much faster!!
Hi,
is there any way to replace the boot logo?
deafjam said:
It does work on the U.S. TMobile tab, I tried it. to me it boots faster, but seems to shut down slower.
Click to expand...
Click to collapse
Thanks in might give it a shot.
Sent from my Samsung Galaxy Tab
So again is there a way to replace the boot logo?
Sent from my GT-P1000 using XDA App
saintxseiya said:
So again is there a way to replace the boot logo?
Click to expand...
Click to collapse
As I pointed out in the first post the boot logo is located in the secondary bootloader partition which an ARM binary. The logo is not accessible via the file system. You would have to dump this binary, modify it and flash it again (e.g. with Odin).
The risk is that if something goes wrong (corrupted binary, signature check failed etc.) your device will not boot anymore. Not even into the flashing mode because it is also part of the secondary bootloader.
Such perma brick can maybe reverted with professional tools like JTAG if you are willing to disassemble your device.
http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/1
Noone so far seemed to replace the boot logo successfully.
One way could be to overwrite the original jpeg (see first post) with a black jpeg of exactly the same size (=20701 bytes). If there's no signature check and the jpeg format is valid this should work.
xdadevel said:
As I pointed out in the first post the boot logo is located in the secondary bootloader partition which an ARM binary. The logo is not accessible via the file system. You would have to dump this binary, modify it and flash it again (e.g. with Odin).
The risk is that if something goes wrong (corrupted binary, signature check failed etc.) your device will not boot anymore. Not even into the flashing mode because it is also part of the secondary bootloader.
Such perma brick can maybe reverted with professional tools like JTAG if you are willing to disassemble your device.
http://www.ifixit.com/Teardown/Samsung-Galaxy-Tab-Teardown/4103/1
Noone so far seemed to replace the boot logo successfully.
One way could be to overwrite the original jpeg (see first post) with a black jpeg of exactly the same size (=20701 bytes). If there's no signature check and the jpeg format is valid this should work.
Click to expand...
Click to collapse
Thanks for the answer!
I searched the net also about these mysterious qmg Files, i do not understand why is Samsung using that kind of files, it just makes us unhappy not to customize the tabs
thanks worked very well, however, I have the t-mobile tab and the t-mobile splash screen stills shows up on boot is there any way to get rid of that one or is it similar to the samsung one that your having trouble removing?
Just flash an unbranded firmware, they will be gone then
Sent from my GT-P1000 using XDA App
xdadevel said:
Noone so far seemed to replace the boot logo successfully.
One way could be to overwrite the original jpeg (see first post) with a black jpeg of exactly the same size (=20701 bytes). If there's no signature check and the jpeg format is valid this should work.
Click to expand...
Click to collapse
Actually it works to overwrite the boot logo in sbl.bin with a custom jpeg file. The size must be less or equal 20701 bytes. I filled the remaining bytes of the original jpeg data with 0x00 but be careful NOT to overwrite the bytecode after the jpeg!!
When booting the device I can see the custom logo for 2-3 seconds.
After that, however, the Samsung boot logo shows up again!
Must be located in another place as well.
This sounds great! Could you make a quick tut how to do that exactly please?
Is there a virtual testlab for the tab or an emulator?
Sent from my GT-P1000 using XDA App
saintxseiya said:
This sounds great! Could you make a quick tut how to do that exactly please?
Is there a virtual testlab for the tab or an emulator?
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
No, unfortunately not. Just flash the european firmware
kg4mxz said:
No, unfortunately not. Just flash the european firmware
Click to expand...
Click to collapse
I am already on jk5 i want to customize my tab.
Sent from my GT-P1000 using XDA App
http://dl.dropbox.com/u/11197643/Spla****/1296674240-gen.png
The above graphic was made with the release version of Spla****!
Hello there, this is my first post in this bit of the forums as I don't regularly dive into this sort of project. I recently created a splash screen for HCDRJacob based upon the htc quietly brilliant screen and it gave me an idea, make a generator!
You can choose the resolution, the text and the colors.. The next version will have a hex input for the text color. The resulting .img file it spits out can be flashed through fastboot but that is not really related to this itself. The resulting files will be hosted for an unspecified amount of time (Ostebaronen is hosting it so I really don't know) so don't link directly to them.
Here are some examples of splashes made with the generator.
http://dl.dropbox.com/u/11197643/Spla****/1296674618-gen.png
http://dl.dropbox.com/u/11197643/Spla****/1296674633-gen.png
http://dl.dropbox.com/u/11197643/Spla****/1296674652-gen.png
http://dl.dropbox.com/u/11197643/Spla****/1296674665-gen.png
Please, comments below, thankyou.
Thanks to Ostebaronen for hosting this and anyone who tested the earlier results.
Hey, I've been looking for something like that, is there a link???
Thankk u
Sent from my T-Mobile G2 using XDA App
I really forgot that!?
URL is http://spla****.dokyou.eu/
Please post your results
Sent from my HTC Wildfire using XDA App
Lol yeah I double checked to see if I missed it.
Sure thing, thanks bro
Sent from my T-Mobile G2 using XDA App
That's ok, I feel a little stupid now
Sent from my HTC Wildfire using XDA App
N00bish question here- when i flash it whatt exact data (and from where) does it replace. eg.bootloader/radio/bootimg
It will replace the very first splash screen you see . Take note also that you need fastboot in hboot of your phone.
You will need to have S-off, right?
hahha nice tool man
you can create very funny things with it
thanks!
Sweet Nice applications like this is always welcome to the scene.
"C:\SDK\tools>fastboot flash splash1 1296755019-flash.img
sending 'splash1' (750 KB)... OKAY [ 0.121s]
writing 'splash1'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.289s"
this is what i'm getting.... i think it may be because i have a nexus one...read that somewhrere...but yeah some insight?
Excellent thanks i make one to test, but...
sorry for noob question how can i put it on mi evo?
I see a how-to but with zip file, but this method launch img file.
roar109: This is a different splash, this is splash1, wheras the zip is the bootanimation.
IceNova: follow this link to root your nexus one, this should enable fastboot, http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
diegov600: Yeah you need S-OFF for the fastboot flash splash1 command
Just wanted to say it worked great!!
Thanks for the awesome splash creator!
Now time to attempt some troubleshooting...
IceNova said:
"C:\SDK\tools>fastboot flash splash1 1296755019-flash.img
sending 'splash1' (750 KB)... OKAY [ 0.121s]
writing 'splash1'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.289s"
this is what i'm getting.... i think it may be because i have a nexus one...read that somewhrere...but yeah some insight?
Click to expand...
Click to collapse
Now assuming you have root and all that, is your 1296755019-flash.img file in the same directory? Try renaming it to something a little smaller like splash.img, then once in the tools directory, just do "fastboot flash splash1 splash.img" That's exactly what I did and it worked first try for me. Hope you get it resolved.
roar109 said:
Excellent thanks i make one to test, but...
sorry for noob question how can i put it on mi evo?
I see a how-to but with zip file, but this method launch img file.
Click to expand...
Click to collapse
Use fastboot method as explained aboved. Boot your phone into hboot mode (The screen that tells you your radio and that junk) then on your pc, navigate to your android sdk's tool folder using command line and follow the previously stated steps to fastboot flash the img file.
is there a way of flashing this using like root explorer, or using terminal emulator on the phone. im only asking because i dont always carry my usb cable with me and 90% of the time im using dropbox to transfer files to my phone and no need to always have the usb.
Not that I know of no, sorry.
Good job!
Trying this now and just downloaded my boot screen...super easy and kinda fun lol...now when i have more time gunna put it on the phone!
update: have more time now so putting it on the phone but...
having troubles : (...i have the .img file in the platform-tools folder with all the correct filepath etc...but the type "fastboot flash splash1 my#-flash.img" and get the following error:
"fastboot is not recognized as an internal or external command, operable program or batch file."
sorry im new to all this hacking/software stuff...more of hardware fan myself lol
Lol thanks .
@ above: Fastboot is at C:\android-sdk-windows\tools by default.
http://dl.dropbox.com/u/11197643/Spla****/1296762749-gen.png
The newest version...waiting on it to be updated.
Pretty sweet. Would be cool if you could do it without the quietly brilliant part.
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.
Can I just erase from settings to restore to default?
Sent from my XT1058 using XDA Premium 4 mobile app
our best bet is probably to follow this guide here...
http://forum.xda-developers.com/showthread.php?t=2446515
Or maybe easier would be just to...
fastboot flash system <nameofsystemfilehere>.img
I would have to double check my last bit of advice though.
Newbie help
is there anyway to do this without deleting my stuff. Sorry im a newbie at this. i orginialy installed the first root moto app and it had a unroot option. the new one doesnt and i really need to get back to stock without doing anything complicated
MarcusSi1516 said:
is there anyway to do this without deleting my stuff. Sorry im a newbie at this. i orginialy installed the first root moto app and it had a unroot option. the new one doesnt and i really need to get back to stock without doing anything complicated
Click to expand...
Click to collapse
Well...
fastbooting the system should not delete your user data. and its not really complicated.
Do you have ADB set up on your computer?
i think so
thepolishguy said:
Well...
fastbooting the system should not delete your user data. and its not really complicated.
Do you have ADB set up on your computer?
Click to expand...
Click to collapse
yah i do. but i origginaly downloaded root app as apk
MarcusSi1516 said:
yah i do. but i origginaly downloaded root app as apk
Click to expand...
Click to collapse
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
####EDIT####
If fastboot will not flash the system.img use a different fastboot.exe created to flash the larger .img
arigi said:
The solution is to use the mfastboot.exe linked from here:
http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
Click to expand...
Click to collapse
And if you leave it named "mfastboot" then you must issue the commands with the "m"...
"mfastboot flash system system.img"
without the parenthesis of course
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes it should. Just got to make sure you grab the correct images for your carrier.
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
should.
But I have a VZW MotoX and I dont want to jack anyone up.
As long as you are using the proper system and recovery. If you flash the ATT system to a VZW device you are going to have problems.
Aarongauntt said:
Just basic knowledge over here, but shouldn't that work for any carrier?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Worked perfect on my ATT Moto x
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
This man deserves some props. Thanks for posting that.
Sent from my HTC One mini
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Thanks for this! It cleared up a whole bunch of things about rooting and locked/unlocked bootloaders for me that just hadn't "clicked" before.
Sent from my Moto X
thepolishguy said:
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
THIS IS FOR VERIZON WIRELESS
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
IF YOU BREAK IT IS NOT MY FAULT
Okay - this is probably going to sound complicated but it is not that complicated...
First let's go over the easy version...
reboot into bootloader and...
fastboot flash system system.img
fastboot flash recovery recovery.img
So that's the easy and short version. Do that and you have restored your phone to stock without losing your app data.
Now the complicated part is whether not you know what to do with that information? In fastboot if you type...
fastboot devices
...it should return you serial number. If it does not then you do not have the proper drivers installed. Install Motorola Device Manager and this should solve the problem http://goo.gl/DiRvpE
Then of course you need the system.img and the recovery.img http://sbf.droid-developers.org/ghost_rcica/list.php
MAKE SURE YOU DOWNLAOD THE FILES FOR THE RIGHT PHONE OR YOU ARE HOSED
Once you download that file you will have to unzip it with something like 7zip or Winrar and when you do you will find those files. Then the files have to be copied to the "platform-tools" folder of your android sdk (or the folder where your fastboot.exe is).
Then you can open a command prompt from that folder with your device attached and...
adb devices
...should return a serial number
adb reboot bootloader
...should reboot into bootloader
fastboot devices
...should return a serial number
fastboot flash system system.img
...should flash the system...
fastboot flash recovery recovery.img
...should flash the recovery...
fastboot reboot
...should reboot the device and you will enter set up but your user data will be preserved.
I am always nervous about helping people because if they break something they like to blame someone. I work a full time job and had a little time to do this write up. This is no guarantee that if you need help in the future that I will be able to help or even know how to help. Please make sure you understand that and are prepared to resolve your issue on your own.
Click to expand...
Click to collapse
Thanks! This was very helpful. I got stuck in a bootloop from a rooted MotoX 4.2.2 whilst trying to accept the OTA to 4.4. I was able to erase the cache to stop the bootloop problem, but I wanted to accept the OTA. I followed this guide and it seemed to work.
For posterity, anyone on Win7 x64 might have had similar problems to me:
Code:
MX-17-57-X-1_CFC_1FF.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
sending sparse 'system' (777329 KB)...
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
OKAY [ 49.985s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
The solution is to use the mfastboot.exe linked from here: http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
arigi said:
Thanks! This was very helpful. I got stuck in a bootloop from a rooted MotoX 4.2.2 whilst trying to accept the OTA to 4.4. I was able to erase the cache to stop the bootloop problem, but I wanted to accept the OTA. I followed this guide and it seemed to work.
For posterity, anyone on Win7 x64 might have had similar problems to me:
Code:
MX-17-57-X-1_CFC_1FF.xml>fastboot flash system system.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
sending sparse 'system' (777329 KB)...
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 46961884 is not a multiple of the block size 4096
OKAY [ 49.985s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
The solution is to use the mfastboot.exe linked from here: http://forum.xda-developers.com/showthread.php?t=2489249
Hope that helps someone trying to do this same thing.
Click to expand...
Click to collapse
^^^^THIS^^^^
Thanks @arigi I added this to my original instructions.
I just took my good ol' Streak 7 to update it as I see some nice JB action here. But as I understand any manipulation to be made needs TWRP to be present on device. As GooManager wasn't instaling recovery the simple way, I decided to download image and flash it via Fastboot. Yet every single time it failed to do so.
Code:
fastboot flash recovery twrps.img
sending 'recovery' (4822 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I was flashing the latest (2.6.x) version. Also my device is empty atm (had 3.2, now has nothing). Custom Recovery is CWR 5.
Need help to flash the TWRP and begin using JB roms.
YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot.
The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.
giveen said:
YOu need to use the NVflash pack, which write the recovery.img to the correct partition at a lower level than fastboot.
The error you are seeing is due to Dell screwing things up and resulting in fastboot being able to read the partitions name value.
Click to expand...
Click to collapse
Seems that all download links for nvflash pack for DS7 are now dead both on xda and google.