Related
Droid 3 Flash Failure
I assume it is possible to fix this problem but I can not find a solution despite extensive research. I have a Droid 3, XT862 experiencing:
AP Fastboot Flash Mode (S)(Flash Failure)
Every time I start the phone I get this message. I can get around it by using Power+M, going into Boot Mode Selection Menu and using Normal Powerup. I have Safestrap v1.08 installed and am able to run 5.6.890 as my safe ROM and Hash’s Cyanogen ICS and both ROM’s work great.
Having to go through these procedures is a pain. I have tried to SBF. I have attempted to flash using RSD Lite. All attempts fail. I would appreciate any help or even an explanation of what the problem may be. Thanks.
Hello
dowlnoad moto-fastboot
download swu.zip file
( moto-fastboot file and downloaded swu.zip file must be extracted to that same folder )
turn on phone by using power + vol down
and in CMD use a command
moto-fastboot flash preinstall preinstall.img
( you know, how to use a CMD in windows right ? )
after that reboot your phone all should be ok
You Give Me Too Much Credit
Thank you so very much for your help. I have moto-fastboot but have no idea where to obtain the swu.zip file. Any help would be appreciated. CMD in windows, what? Sorry, I am 62 years old, have no experience with this stuff. I thought I was doing well by rooting, strapping, and loading two ROMs. So if you could give me just a little more help here, I will kiss your avatar on the screen (which actually looks pretty hot!). Thanks.
Weird! Could you detail at which step RSD Lite failed to flash the ROM onto your phone? Normally, RSD Lite is the first to call when it comes to flash or unbrick Motorola phones. It's never failed me once since using on my Milestone.
Anyway, I don't know if you've read this instruction. This is pretty much foolproof. The link for the file is dead, you could try this to obtain it.
Good luck!
1. Download full system files from that link
http://www.multiupload.nl/PLYL79UDCC or from link what you got from blackbuddha
1a. make directory on C: and name it 1
2. extract this file to folder c:/1/
3. download moto-fastboot files
http://forum.xda-developers.com/attachment.php?attachmentid=635568&d=1308927194
end extract to C:/1/ where you have system droid3 system files
you must have moto-fastboot file and preinstall.img file in that same folder
( so you must check and if this both file is in diffrent folders please copy all to c:/1/)
4. click on start and in type CMD (and push enter)
5. in this black window ( CMD ) input cd/ (and push enter)
6. now type cd 1 (and push enter) you will go to folder 1
7.and now type moto-fastboot flash preinstall preinstall.img (and hit enter)
*** update ***
You must turn on phone with hold POWER + VOL DOWN buttons i forgot
niko99 said:
1. Download full system files from that link
http://www.multiupload.nl/PLYL79UDCC or from link what you got from blackbuddha
1a. make directory on C: and name it 1
2. extract this file to folder c:/1/
3. download moto-fastboot files
http://forum.xda-developers.com/attachment.php?attachmentid=635568&d=1308927194
end extract to C:/1/ where you have system droid3 system files
you must have moto-fastboot file and preinstall.img file in that same folder
( so you must check and if this both file is in diffrent folders please copy all to c:/1/)
4. click on start and in type CMD (and push enter)
5. in this black window ( CMD ) input cd/ (and push enter)
6. now type cd 1 (and push enter) you will go to folder 1
7.and now type moto-fastboot flash preinstall preinstall.img (and hit enter)
*** update ***
You must turn on phone with hold POWER + VOL DOWN buttons i forgot
Click to expand...
Click to collapse
I tried this but nothing happens after, phone stays in AP Fastboot Flash mode(S)
cmd did sending preinstall and writing okay twice.
Is the phone supposed to restart itself?
What next?
so no problem flash all files
with using a CMD and FAST-BOOT
moto-fastboot flash recovery recovery.img
moto-fastboot flash boot boot.img
moto-fastboot flash devtree device_tree.bin
moto-fastboot flash logo.bin logo.bin
moto-fastboot flash preinstall preinstall.img
moto-fastboot flash cdrom cdrom
moto-fastboot flash radio radio.img
moto-fastboot flash system system.img
and this should help for 100% to you
Still working on this
I, original poster, still working on this to solve problem. Have two Droid3s so I have time to work on it. Will try later today. Thanks.
Does Not work!! Lint in the blowhole?
OK, I have tried this cure multiple ways and it just does not work. I downloaded multiple copies of the files to be installed. I have used CMD as described above but it just does not "flash". When I add the command line in CMD my hard drive cranks and spins, loading the files to be flashed. Then I get <waiting for device>. I put the phone into AP Flashboot Phone battery is OK, and plug in the USB cable. I get Erasing "userdata"...OKAY [0.047s] and Erasing 'cache" ...OKAY [0.156s] CMD says Sending "recovery" <9216 KB>... and nothing. I have waited, and waited. There is just something that prevents the files from being flashed in. Any possible ideas? It is obviously connecting if it can erase, but it will not send.
When using RSD Lite, the phone is detected as Fastboot CDMA_Solana S. When I attempt to flash the SBF file it says: Failed flashing process. Unable to retrieve interface handle. [0x7027]; phone connected.
You also try to flash mbm.bin and mbmloader.bin finally or not ?
MBM.BIN
MBMLOADER.BIN
this two files must work
moto-fastboot flash mbm mbm.bin
moto-fastboot flash mbmloader mbmloader.bin
must work ! look if you have this both files in that same folder where is fast-boot.exe
if you dont have download from here
http://speedy.sh/gURdE/mbmloader.bin
http://speedy.sh/UHGVd/mbm.bin
Thanks again but no luck
Tried to flash just these two files and no luck. The same process as described above occurred, then it did not flash the files. I am about ready to give up and just put up with having to use two steps to start the phone.
Are you on one of the leaked OTA ROMs (.902, .905, or .906)?
I am on .905 and also have this same issue. Cannot flash anything with RSD Lite and I get the AP-FastBoot Flash Failed message everytime I reboot.
I think we need a new version of RSD Lite.
Sent from my DROID3 using xda premium
Maybe Tha's The Problem
Perhaps you have put your finger on the problem. I have .906 currently installed. I am using RSD Lite 5.6 which I assume, but do not know, is the latest version available. My only reservation in agreeing that this may be the problem is that I believe I had 5.6.890 installed when I bricked and tried to unbrick using Pete's unbricking script. Flash would not work. Later I recovered by installing .906 from recovery (I think) and then continued to be unable to flash. So it could be a .906 problem but maybe not.
Hi Guys
when using fastboot to flash /system you need the latest Moto fastboot, the previous one will not work and the standard fastboot also will not work.
HD and M Compatible FASTBOOT
Enjoy
Hi guys,
it's possible to have an osx/linux version for the fastboot...???? Please !!??
Thanks a lot
FrAsErTaG said:
Hi Guys
when using fastboot to flash /system you need the latest Moto fastboot, the previous one will not work and the standard fastboot also will not work.
HD and M Compatible FASTBOOT
Enjoy
Click to expand...
Click to collapse
I don't have razr phone, but I think the attached fastboot has a chance to work on it. The archive contains Darwin, Linux and Windows versions. I've run a strings on the binary and they are very similar, the size it's not so different too... It's from Atrix.
Hope this helps
epinter said:
I don't have razr phone, but I think the attached fastboot has a chance to work on it. The archive contains Darwin, Linux and Windows versions. I've run a strings on the binary and they are very similar, the size it's not so different too... It's from Atrix.
Hope this helps
Click to expand...
Click to collapse
how to install this fastboot??? (como instalar este fastboot???)
Thanks for this, guys.
If you're having issues flashing in RSD Lite, and you get the "getvar" error message, unzip the .xml files and inside should be an .xml in there (only .xml file there is) open it up in Notepad++ and delete the two lines that reference "getvar" save and close, open up RSD lite and then just load the already uncompressed folder (no need to rezip what you just did). Should work.
I ha e some trouble on rsd after downgrading from jb to ics... I cant use rsd lite anymore...
Enviado desde mi XT925 usando Tapatalk 2
Code:
mbp:motofastboot-olympus alexus$ cd Darwin/
mbp:Darwin alexus$ ls
fastboot
mbp:Darwin alexus$ ./fastboot
-bash: ./fastboot: cannot execute binary file
mbp:Darwin alexus$ file fastboot
fastboot: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped
mbp:Darwin alexus$
Where did you get it from Motorola site?
Hello everyone,
This is a AP.bin extractor
rewritten in plain C based on xonar_'s work and support both linux and win32
navossoc@xda introduced the "LGExtract.exe". the encrypyted/compressed kdz can be extracted/decrypted to AP.bin/CP.fls by LGExtract.exe
xonar_ made BIN/FLS extractor
http://forum.xda-developers.com/showthread.php?t=1879915
and release source(win32)
•http://forum.xda-developers.com/showpost.php?p=31432471&postcount=11 (original Java version by xonar_)
•http://forum.xda-developers.com/showpost.php?p=33426102&postcount=37 (win32 C port by navossoc)
•http://forum.xda-developers.com/showpost.php?p=34022349&postcount=141
Basically, the AP.bin file is plain raw file, the bootable images can be extracted by searching specific pattern "ANDROID!".
based on this work, I can figure out the AP.bin header information without searching specific pattern to extract boot.img/ext4 partitions/bootloader etc.
Usage
Download attached file. It include both win32 and linux binary and it's source(GPL).
• show AP.bin information
Code:
extract P990_AP.bin
• extract specific section
Code:
extract P990_AP.bin 3
• or extract all images
Code:
extract P990_AP.bin -1
TODO
• show filenames or partitions
References
mman-win32 is used to port win32 binary
• mman-win32 (GPLv2) by kutuzov - http://code.google.com/p/mman-win32/
• http://forum.xda-developers.com/showpost.php?p=34078601&postcount=148
ChangeLog
•*oops! no source change. just replace with working extract.exe (reported by spyrosk and Kostja_V)
Credits
• navossoc - the Author of LGExtract.exe and win32 C port of extractor.
• xonar_ - BIN/FLS extractor and it's java source.
This is a cool tool, wkpark, but I don't understand the difference to the already available tool here:
(it already does extract AP.bin files of the latest ICS leaks, dumping all the available partitions.
But I guess your tool does dump more things like header and bootloader? Could you please write the differences of those two tools?
Also it would be cool to get a tool which is capable of re-merging changed partitions (system.img, boot.img, recovery.img, cracked bootloader) again to a AP.bin --- would that possible? We could create Smartflah-Custom-ROMs then!)
Stefan Gündhör said:
This is a cool tool, wkpark, but I don't understand the difference to the already available tool here:
(it already does extract AP.bin files of the latest ICS leaks, dumping all the available partitions.
But I guess your tool does dump more things like header and bootloader? Could you please write the differences of those two tools?
Also it would be cool to get a tool which is capable of re-merging changed partitions (system.img, boot.img, recovery.img, cracked bootloader) again to a AP.bin --- would that possible? We could create Smartflah-Custom-ROMs then!)
Click to expand...
Click to collapse
as I already mentioned, just rewritten in plain C to make it more portable to support both linux and win32
and make it more unix friendly
and this tool print the exact address and size of images to make it possible to use "dd" to fix AP.bin without any specific tools
e.g.)
Code:
$ extract SU660_AP.bin
filesize: 939524096
[01] address=0x00100000 size=0x00300000
[02] address=0x00400000 size=0x00080000
[03] address=0x00480000 size=0x00180000
[04] address=0x00600000 size=0x20000000
[05] address=0x20600000 size=0x00800000
[06] address=0x20e00000 size=0x01400000
[07] address=0x22200000 size=0x15e00000
$ extract SU660_AP.bin 6 # 6 is recovery.img
...
$ dd if=cwm.img of=SU660_AP.bin bs=1024 seek=$(printf "%d" $((0x20e00000 / 1024))) conv=notrunc
now we got CWM injected AP.bin!
But currently you cant use this method for ICS firmwares
wkpark said:
as I already mentioned, just rewritten in plain C to make it more portable to support both linux and win32
and it is more unix friendly
Click to expand...
Click to collapse
Aaaah okay cool
What about the re-merging thing, do you think you could maybe look into that?
Edit: Ah I see you updated your post, thanks!
Simply awesome. Thanks wkpark!
Very good utility, bravo!
I have been able to decipher everything except partitions 1 and 2, in total there are 7 partitions
1. 01.img
2. 02.img
3. bootloader.img
4. boot.img
5. recovery.img
6. data.img
7. ext3_system.img
I have created a shell for Linux
Use
Copy the file P990_AP.bin into the AP_Toolkit folder /
Run menuen.sh or menues.sh
Look very useful! Tnx dude!
Homero2 said:
Very good utility, bravo!
I have been able to decipher everything except partitions 1 and 2, in total there are 7 partitions
1. 01.img
2. 02.img
3. bootloader.img
4. boot.img
5. recovery.img
6. data.img
7. ext3_system.img
I have created a shell for Linux
Use
Copy the file P990_AP.bin into the AP_Toolkit folder /
Run menuen.sh
Click to expand...
Click to collapse
I guess the order of images are not always the same,
the V30C of SU660 is somewhat different, so this script is not compatible with SU660
some images like as bootable images can be detected by the following method
the bootable images easily checked by dd
Code:
[ $(dd if=boot.img bs=1 count=8 2>/dev/null) = 'ANDROID!' ] && echo "this a is bootable image"
OK, actually the structure varies between models, I have checked that there are differences between P990 and SU660.
And within the same model varies structure?, I've tried several versions of P990 and it seems that the structure is maintained.
Homero2 said:
Very good utility, bravo!
I have been able to decipher everything except partitions 1 and 2, in total there are 7 partitions
1. 01.img
2. 02.img
3. bootloader.img
4. boot.img
5. recovery.img
6. data.img
7. ext3_system.img
I have created a shell for Linux
Use
Copy the file P990_AP.bin into the AP_Toolkit folder /
Run menuen.sh or menues.sh
Click to expand...
Click to collapse
If I remember well partition 1 is the bct file. I suppose that partition 2 has something to do with partition layout .
Sent from my LG-P990 using xda app-developers app
This is a new version, it is more complex than the previous version, also includes the BAT version for Window.
Forgive if there is any error in the Windows version, long time that I do not write anything serious for Windows.
In the menu you can choose the model (P990 or SU660)
Researching a bit I have seen that the 01.img portion is the star.bct, but...
The original file weighs in at 4.0kb, which is obtained with AP_Tool weighs 3.0 MB
With a hex editor I saw that the heading is:
Code:
32 DB 10 C0 A8 A2 5 C 3F 1B 17 34 84 15 57 C6
Looking for I found 7 headers, I extracted them and got 7 files which then I expose in the order found within the 01.img file
star_0.bct - 4.0Kb - this is good (exactly of 000 to FFF)
star_1.bct - 508.0Kb
star_2.bct to star_6.bct - 512.0Kb
Guys,
the extract exe in first post does not work properly. I think it doesn't extract the partitions at the right headers.
I extracted the V28g bin file and the system and data partitions when mounted are unreadable.
Using the extract2 (attached) the partitions are readable perfectly.
The sizes also, differ between the two set of partitions.
I felt I had to let you know.
spyrosk said:
Guys,
the extract exe in first post does not work properly. I think it doesn't extract the partitions at the right headers.
I extracted the V28g bin file and the system and data partitions when mounted are unreadable.
Using the extract2 (attached) the partitions are readable perfectly.
The sizes also, differ between the two set of partitions.
I felt I had to let you know.
Click to expand...
Click to collapse
Did you use the LG extract.exe or other tool to get the ap.bin?
It works perfectly with the lgextract.exe that's why I wrote this post
And why don't you attach your source code?
Isn't it modified extract.c?
Or just binary hacked executable
found at the navossoc's post?
The license of this source code is GPL but you didn't include modified source code in it.
Sent from my LG-P990 using xda app-developers app
wkpark said:
Did you use the LG extract.exe or other tool to get the ap.bin?
It works perfectly with the lgextract.exe that's why I wrote this post
And why don't you attach your source code?
Isn't it modified extract.c?
Or just binary hacked executable
found at the navossoc's post?
The license of this source code is GPL but you didn't include modified source code in it.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
I did use LGExtract.exe to get the bin.
I just downloaded the binary in the first post of this thread. I didn't touch the source code.
The tool from OP doesn't work for me too. The extracted system.img size is 515mb, but should be 512, so it is not flashable via nvflash.
On the screenshot you can see, that files extracted using extract-v0.1 from the OP and extract2 from the http://forum.xda-developers.com/showpost.php?p=34100186&postcount=2 have different sizes.
spyrosk said:
Guys,
the extract exe in first post does not work properly. I think it doesn't extract the partitions at the right headers.
I extracted the V28g bin file and the system and data partitions when mounted are unreadable.
Using the extract2 (attached) the partitions are readable perfectly.
The sizes also, differ between the two set of partitions.
I felt I had to let you know.
Click to expand...
Click to collapse
Kostja_V said:
The tool from OP doesn't work for me too. The extracted system.img size is 515mb, but should be 512, so it is not flashable via nvflash.
On the screenshot you can see, that files extracted using extract-v0.1 from the OP and extract2 from the http://forum.xda-developers.com/showpost.php?p=34100186&postcount=2 have different sizes.
Click to expand...
Click to collapse
thankyou for your testing!!
confirmed !
my bad.. I uploaded not correctly patched win32 executable by mistake.
I just replace the old one with a working win32 binary.
Homero2 said:
Researching a bit I have seen that the 01.img portion is the star.bct, but...
The original file weighs in at 4.0kb, which is obtained with AP_Tool weighs 3.0 MB
With a hex editor I saw that the heading is:
Code:
32 DB 10 C0 A8 A2 5 C 3F 1B 17 34 84 15 57 C6
Looking for I found 7 headers, I extracted them and got 7 files which then I expose in the order found within the 01.img file
star_0.bct - 4.0Kb - this is good (exactly of 000 to FFF)
star_1.bct - 508.0Kb
star_2.bct to star_6.bct - 512.0Kb
Click to expand...
Click to collapse
the image 01(BCT) and 02(PT. Partition Table) are updated by the Smartflash or NVFlash automagically.
you can't even simply download(flash) the BCT/PT image at all
like as MBR and PT, the BCT also duplicated itself
@wkpark hi,
I bumped into the following issue, when I first had an idea making an option in AIO-Toolkit to switch between locked and yours unlocked new bootloader.
I extracted stock bootloader image with your bin extractor.
I also checked its md5 with a backed-up (by nvflash) one's (which was smartflashed) and are the same.
So far so good and your bin extractor works perfectly.
When I try to flash it, nvflash always stops here | 1507328/1572864 bytes sent
Do you have any idea why this happens?
Since the unlocked one is much smaller than the total size of the partition, I suppose stock one has about the same actual size.
Could you please make an image of the stock one for me (with its data only)? get the original from here
cause I don't know how to do it myself and actually I am on a leave and I don't have any linux pc available.
I'd like to give a try because now I am curious, why the cracked one can be flashed and the stock not.
Thank you in advance for your help
Cheers
spyrosk said:
@wkpark hi,
I bumped into the following issue, when I first had an idea making an option in AIO-Toolkit to switch between locked and yours unlocked new bootloader.
I extracted stock bootloader image with your bin extractor.
I also checked its md5 with a backed-up (by nvflash) one's (which was smartflashed) and are the same.
So far so good and your bin extractor works perfectly.
When I try to flash it, nvflash always stops here | 1507328/1572864 bytes sent
Do you have any idea why this happens?
Since the unlocked one is much smaller than the total size of the partition, I suppose stock one has about the same actual size.
Could you please make an image of the stock one for me (with its data only)? get the original from here
cause I don't know how to do it myself and actually I am on a leave and I don't have any linux pc available.
I'd like to give a try because now I am curious, why the cracked one can be flashed and the stock not.
Thank you in advance for your help
Cheers
Click to expand...
Click to collapse
Hi! I was facing the same problem like you. Open the bootloader.bin in a hex editor (WinHEX or any other hexeditor) and delet all the FF hex values from the end of the file. I hope it will work for you
Edit: I deleted the FF a valuses frrom the the backed up bootloader
Hy everybody,
I need a small help. I'd like to extract stock system apks placed in /system/app but I don't succed.
On the normal RAZR XT910 I use RSD or a zip extractor (winrar, winzip, etc.) to divide a stock firmware in system_signed, mbr_signed, motoboot, cdrom_signed, boot_signed and other files, then i can extract system_signed using Ext2explore to have a copy of the stock system folders,
On the RAZRi XT890 firmwares 4.1.2 this procedure doesn't work, when i try to extract system_signed,Ext2explore sometimes doesn't read the archive without any response or other times it stops working.
Thanks for helping.
bobby3 said:
Hy everybody,
I need a small help. I'd like to extract stock system apks placed in /system/app but I don't succed.
On the normal RAZR XT910 I use RSD or a zip extractor (winrar, winzip, etc.) to divide a stock firmware in system_signed, mbr_signed, motoboot, cdrom_signed, boot_signed and other files, then i can extract system_signed using Ext2explore to have a copy of the stock system folders,
On the RAZRi XT890 firmwares 4.1.2 this procedure doesn't work, when i try to extract system_signed,Ext2explore sometimes doesn't read the archive without any response or other times it stops working.
Thanks for helping.
Click to expand...
Click to collapse
Hey,
try unyaffs tool
First, wrong section. This belongs in the q&a.
Back to topic. The system.IMG has an ext4 file system. Mount it in Ubuntu with a mount loop methode. Don't know the exact words for it, sry.
Sent from my XT890 using xda app-developers app
Doesn't work
Thanks (and thanks to moderator) but these methods doesn't work.
Using system_signed of RAZRi unyaffs tool gives me an error response, "mount" on linux does nothing.
Using system_signed of RAZR XT910 instead works fine with ext2explore, with unyaffs tool and mounting in ubuntu but i need to extract RAZRi system_signed.
bobby3 said:
Thanks (and thanks to moderator) but these methods doesn't work.
Using system_signed of RAZRi unyaffs tool gives me an error response, "mount" on linux does nothing.
Using system_signed of RAZR XT910 instead works fine with ext2explore, with unyaffs tool and mounting in ubuntu but i need to extract RAZRi system_signed.
Click to expand...
Click to collapse
Than u still didnt look good enough. But ok, i have done it now for you
Download the script in the attachment. The simg2img.py.zip and extract it.
Uncompress the system.img file into a normal ext4 disk image:
‘python simg2img.py system_signed tmp.img’
This will create an uncompressed ext4 volume ‘tmp.img’ in the same directory
Mount this disk image:
‘sudo mount -t ext4 -o loop tmp.img somedir/’
profit. The mounted file/partition (then) is in read only mode, for the record
Hazou
Thanks a lot!
Hazou said:
Than u still didnt look good enough. But ok, i have done it now for you
Download the script in the attachment. The simg2img.py.zip and extract it.
Uncompress the system.img file into a normal ext4 disk image:
‘python simg2img.py system_signed tmp.img’
This will create an uncompressed ext4 volume ‘tmp.img’ in the same directory
Mount this disk image:
‘sudo mount -t ext4 -o loop tmp.img somedir/’
profit. The mounted file/partition (then) is in read only mode, for the record
Hazou
Click to expand...
Click to collapse
Fantastic! It works!
You are great! :highfive:
Thank you! Thank you! Thank you!
Hello! I've recently just snagged a fully functioning Tegra X1-Powered Nvidia Shield Portable 2 that's rooted. I'm trying to extract the partitions so that I can make backups of the bootloader (to flash with nvflash), system, boot, recovery, etc images for other X1-Powered Shield 2 owners for unbricking purposes, as there aren't any recovery images posted online.
Does anyone know which fastboot/adb commands could achieve this? Here is what the partition scheme looks like but I have no clue which partition is which. Any help with this would be greatly appreciated. Thank you so much!
so i just made an interesting find as to which partition is which
i ran
ls -l /dev/block/platform/sdhci-tegra.3/by-name/
and then ran
cat fstab.loki_e_lte
and now i think i know which partition needs to be extracted for each image. refer to screenshot for context
so it seems
mmcblk0p19 > system.img
mmcblk0p20 > cache.img
mmcblk0p18 > boot.img
mmcblk0p22 > misc.img
mmcblk0p23 > staging.img
mmcblk0p16 > recovery.img
i have extracted the images for recovery but i have not tested these. also currently working on figuring out how to extract the bootloader so i can have a *complete* system recovery for those even without a bootloader; if anyone knows how, i'm all ears.
i do not recommend flashing these on a non-bricked shield but someone with a bricked X1 powered shield feel free to test and let me know how it goes <3 flashing instructions are included in the folder too.
loki_e_lte - Google Drive
drive.google.com