Related
I did not see anything that really walked through what you should do in one place. This is the method I used to restore my device to factory condition. It can also be used to unbrick the device.
You should be comfortable with the command line before proceeding. You cannot downgrade at this tome, so download the version that was on your phone previously.
Files needed:
Verizon 5.5.959 or Verizon 5.6.890
moto-fastboot for linux, download the appropriate version for your arch
HowTo:
1. Extract the zip you downloaded and moto-fastboot.zip to the same working directory. You will get several .img files, moto-fastboot, and an .xml
2. Create a new file named "reset" in your working directory and fill it with the following code.
Code:
#!/bin/bash
./moto-fastboot flash mbm allow-mbmloader-flashing-mbm.bin
./moto-fastboot reboot-bootloader
sleep 30
./moto-fastboot flash mbmloader mbmloader.bin
./moto-fastboot flash mbm mbm.bin
./moto-fastboot reboot-bootloader
sleep 30
./moto-fastboot flash cdt.bin cdt.bin
./moto-fastboot erase userdata
./moto-fastboot erase cache
./moto-fastboot flash lbl lbl
./moto-fastboot flash logo.bin logo.bin
./moto-fastboot flash ebr ebr
./moto-fastboot flash mbr mbr
./moto-fastboot flash devtree device_tree.bin
./moto-fastboot flash system system.img
./moto-fastboot flash radio radio.img
./moto-fastboot flash boot boot.img
./moto-fastboot flash recovery recovery.img
./moto-fastboot flash cdrom cdrom
./moto-fastboot flash preinstall preinstall.img
./moto-fastboot reboot
3. Change directory to your working directory. Make moto-fastboot and the script executable.
Code:
chmod a+x moto-fastboot
chmod a+x reset
4. Execute the script you created in step 2 (with supercowpowers). It should read "< waiting for device >"
Code:
sudo ./reset
5. Make sure your phone is >%50 charged for good measure. Turn off your phone. Hold the 'M' key on the keyboard and turn your phone back on. Press Vol - to scroll down to "AP Fastboot". Press Vol + to select. Connect the USB cable.
6. Sit back and relax, the phone is now flashing back to factory. It will reset a few times. Eventually it will boot up like normal and you'll be all set!
Notes:
You can change sleep to 10 seconds to speed it up. I recommend 30 because I don't know how fast your system picks up usb devices.
The parameters I used to create the script are from the .xml file, in case you were wondering.
[Source for files]
http://rootzwiki.com/showthread.php?5103-SBF-Droid-3-Fastboot-files-(5.5.959-and-5.6.890)
If this helped you, press thanks so others know
If it didn't, please post why to help improve this guide
We have a easier method now, rsd.
Sent from my DROID3 using XDA App
ourtut said:
We have a easier method now, rsd.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
RSD doesn't run natively on Linux
I get it now. Good tut for ppl with linux.
Sent from my DROID3 using XDA App
Thanks for this! I hate having to drop to windows for this kind of stuff, especially considering that linux is under the android framework.
Sent from my DROID3 using XDA App
thank you now i never have to mess with rsd lite and windows .. and drivers you know. thanks
Sent from my DROID3 using Tapatalk
Why does the script need superuser (sudo)? I like the script and will for sure use it, thank you for sharing. I think it would work fine without sudo though
Sent from my DROID3 using XDA App
jweber228 said:
Why does the script need superuser (sudo)? I like the script and will for sure use it, thank you for sharing. I think it would work fine without sudo though
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I don't feel like trouble shooting peoples permissions issues. Running as superuser will eliminate those problems. Some systems\configurations do require those permissions.
Why is this thread no stickied? all other RSD lite threads are, and we cant use RSDlite in linux.
Darksurf said:
Why is this thread no stickied? all other RSD lite threads are, and we cant use RSDlite in linux.
Click to expand...
Click to collapse
because you have to msg the forum mod...cheif_tony and request it
thanks for this one!
a few questions,
is this possible with the new 906 zip?
http://forum.xda-developers.com/showthread.php?p=27315518#post27315518
can you please explain points 3 and 4 more detailed for newer linux/ubuntu users?
what do you mean "3. Change directory to your working directory. Make moto-fastboot and the script executable." and "Execute the script you created in step 2 (with supercowpowers)" how do i get supercowpowers?
The original post's "Verizon 5.6.890" link to the 890 install brings me to LNX.lu and requires a login. I've been waiting a while for their emailed account confirmation - is there another place to grab this file?
Also, you mention Arch - is this process the same in Ubuntu?
EDIT: Hah! Works like a charm. One last step - THANK YOU GamezR2EZ!
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.
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
downloaded all the goodies, gapps, rom, everything, went into CWM recovery (photon Q) followed steps exactly as followed, idk what the hell happened. Everything is wiped, tried rsd lite 5.7 with batakang stock and i get XML error every time. Ive flashed many roms since atrix 4g came out and so on, Can anyone please oblige me on this issue, im not a complete noobie.
asser failed: getprop("ro.product.device") == "xt925"
blah blah blah
E: error in /sdcard/Downloads/pac-mb886v22.zip
(status 7)
Installation aborted.
Any Help
BFRAPV42 said:
downloaded all the goodies, gapps, rom, everything, went into CWM recovery (photon Q) followed steps exactly as followed, idk what the hell happened. Everything is wiped, tried rsd lite 5.7 with batakang stock and i get XML error every time. Ive flashed many roms since atrix 4g came out and so on, Can anyone please oblige me on this issue, im not a complete noobie.
asser failed: getprop("ro.product.device") == "xt925"
blah blah blah
E: error in /sdcard/Downloads/pac-mb886v22.zip
(status 7)
Installation aborted.
Any Help
Click to expand...
Click to collapse
You must either A: install cwm (razr hd); or B: extract the zip, then go to Meta-inf > Com > Google > Android > Updater-Script, change "updater-script" to "updater-script.txt" then delete all the assert lines at the top, then save as "updater-script.file" then rename it to "updater-script" with no file extension again, and put it back in the same directory as the previous updater-script was, then repack the zip and install it. (I'm talking to you in detail because you apear to be new with one post, no offense if you know how to script it with note pad++ without detailed instructions. )
flashing error
Codex01 said:
You must either A: install cwm (razr hd); or B: extract the zip, then go to Meta-inf > Com > Google > Android > Updater-Script, change "updater-script" to "updater-script.txt" then delete all the assert lines at the top, then save as "updater-script.file" then rename it to "updater-script" with no file extension again, and put it back in the same directory as the previous updater-script was, then repack the zip and install it. (I'm talking to you in detail because you apear to be new with one post, no offense if you know how to script it with note pad++ without detailed instructions. )
Click to expand...
Click to collapse
i was on here prior but its been a while i appreciate the help. my issue theres no system on my AHD so how to get pacman rom redownloaded to my pc and no im not super BA at scripting. ya i can delete a few getvar lines to flash back to stock jb and start over again but syste.img wont even flash there while in AP Fastboot.
Thanks man
Trying to go to stock jb now, i had root and have unlocked bootloader, when usign rsd lite v5.7 i flash the xml after editing it and taking the 2 getvar lines out and now system wont flash, it says phone "Fail flashing process" "system.img" phone returned fail. flashing everything fine till it gets to the system.img file.
(Originaly Posted By: SkeevyDude)
Instructions Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Don't use RSD Lite, its too complicated.
Codex01 said:
(Originaly Posted By: SkeevyDude)
Instructions Install Stock Fastboots JB
Download the respective fastboot zip you want to use
Extract the zip
Open a terminal to the extracted zips directory
Reboot into fastboot
Type the following commands in this order
fastboot flash boot boot.img
fastboot flash devtree device_tree.bin
fastboot erase system -w !
fastboot flash system system.img
fastboot -w
fastboot erase cache !
fastboot reboot
Don't use RSD Lite, its too complicated.
Click to expand...
Click to collapse
And the erase commnds with ! don't work for us.
I installed CM10.1 by manually formatting /system and /data before flashing. Can't fail a build.prop check if there is no build.prop to check
stock jb
skeevydude said:
And the erase commnds with ! don't work for us.
I installed CM10.1 by manually formatting /system and /data before flashing. Can't fail a build.prop check if there is no build.prop to check
Click to expand...
Click to collapse
so i downloaded stock att jb rom from xda, went to the directory C:\user\costco\desktop and to the stock jb folder open command prompt and typed the code.(phone is in fast boot currently as well) Cmmnd prompt says is not recognized as an external or internal command,operable program or batch file. Maybe my head is just to busy to focus i must be messing up somewhere. You guys are so freaking awesome for being patient with me and helping me, ill buy the brews haha
Not an issue with bootloader already unlocked i assume cause once im back on stock im gonna be 1000 times more careful when rerooting again to get back where i was.
idk if its terminal for vista or if its the download i got, i got it from a link on here from, I leave the "getvar lines on the xml file when i do it through terminal right?
Check out my reply in this post. I had the same problem and got it figured out...
http://forum.xda-developers.com/showthread.php?t=2209660
Atrix HD - PACman ROM
RSD wouldn't flash system.img for some reason and wouldn't exit AP fastboot mode until I successfully flashed. So with the working fastboot files (check out skeevydudes posts, don't use the SDK fastboot) make a folder w fastboot.exe, fastboot api, the stock zip for rsd (remove the getvar and system.img lines of course), epinter's recovery (skeevydude made a recovery flash that contains this), and system.img (extracted from the stock RSD flash zip). Then open terminal or command prompt. cd to the folder you just made... fastboot flash system system.img then it will reboot when it flashes, reboot back to AP fastboot and then cd to fold again and then fastboot flash recovery recovery.img Then from epinter's CWM you can flash the ROM as instructed in the OP wo having to edit anything. Please excuse my mess doing all this from my phone
Droid4Drew said:
Check out my reply in this post. I had the same problem and got it figured out...
http://forum.xda-developers.com/showthread.php?t=2209660
Atrix HD - PACman ROM
RSD wouldn't flash system.img for some reason and wouldn't exit AP fastboot mode until I successfully flashed. So with the working fastboot files (check out skeevydudes posts, don't use the SDK fastboot) make a folder w fastboot.exe, fastboot api, the stock zip for rsd (remove the getvar and system.img lines of course), epinter's recovery (skeevydude made a recovery flash that contains this), and system.img (extracted from the stock RSD flash zip). Then open terminal or command prompt. cd to the folder you just made... fastboot flash system system.img then it will reboot when it flashes, reboot back to AP fastboot and then cd to fold again and then fastboot flash recovery recovery.img Then from epinter's CWM you can flash the ROM as instructed in the OP wo having to edit anything. Please excuse my mess doing all this from my phone
Click to expand...
Click to collapse
no man its all good i need all the tutorial help i can get, never have bricked a phone and worried i did so, i can make sense of most of it but my head is full of tht sdk stuff, trying to forget it and get this working, i feel like an idiot asking for step by step crap but how am i to get it quicker than asking for a little help. learning from this is major for me. Thanks man hopefully i get it ok.
still no bueno
BFRAPV42 said:
no man its all good i need all the tutorial help i can get, never have bricked a phone and worried i did so, i can make sense of most of it but my head is full of tht sdk stuff, trying to forget it and get this working, i feel like an idiot asking for step by step crap but how am i to get it quicker than asking for a little help. learning from this is major for me. Thanks man hopefully i get it ok.
Click to expand...
Click to collapse
still a no go, have the new folder with all 5 items needed, pulled up command prompt and its giving same issue. F WORDDDDDDDDDs
C:\Users\Costco>fastboot flash system system.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
same error.
You need these fastboot binaries in the folder also, sorry I couldn't think of the word binaries earlier when I was typing... This I what I ment by the exe and api, just put the two files from the windows folder of the zip into the folder you made and try again... http://www.batakang.com/ftp/devs/mattlgroff/snapdragon-fastboots.zip
Atrix HD - PACman ROM
Droid4Drew said:
You need these fastboot binaries in the folder also, sorry I couldn't think of the word binaries earlier when I was typing... This I what I ment by the exe and api, just put the two files from the windows folder of the zip into the folder you made and try again... http://www.batakang.com/ftp/devs/mattlgroff/snapdragon-fastboots.zip
Atrix HD - PACman ROM
Click to expand...
Click to collapse
i have the snapdragon fastboot .exe and .api in the folder already. along with the system.img , epinters recovery.img and MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA
i took a screen shot of the directions you gave with the command prompt open and the folder with the files in it but couldnt upload it unfortunately.
Make sure adb.exe and fast boot.exe are set to run as admin. Right click them and set them to be admin. Then try again.
Sent from my MB886 using xda app-developers app
TTLayland said:
Make sure adb.exe and fast boot.exe are set to run as admin. Right click them and set them to be admin. Then try again.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
fastboot.exe is admin api doesnt have an option in advanced for run as admin, i opened terminal and cd to where the file was on c: drive and typed [fastboot flash system system.img] hit entere and it worked but the phone never rebooted after it completed, when i typed [fastboot flash recovery recovery.img] with is epinters recovery it says ERROR cannot load recovery.img
Scratch that I'm actually replying to this from stock jb, thank all you guys for all the help.
Sent from my MB886 using xda app-developers app
So my advice worked?
Sent from my MB886 using xda app-developers app
Ya it work but It wouldn't with battery under 60% when I charged it up it flashed with ease. I'm on stock 4.1.1 gonna try epinters cwm to flash and then finally pacman
Sent from my MB886 using xda app-developers app
BFRAPV42 said:
Ya it work but It wouldn't with battery under 60% when I charged it up it flashed with ease. I'm on stock 4.1.1 gonna try epinters cwm to flash and then finally pacman
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
I found that the advice I gave you was the only thing that was not in the instructions. Good stuff that you got it working though.
Sent from my MB886 using xda app-developers app
Got a ? about Atrix HD flashed with Pac Man v22
I flashed Pac Man and everything looks great, and works well tiny lag issues but I love it so thank you to all the devs involved.
But...I have seemed to lose root access. I have tried to reinstall the root access with one click and it stops at Daemon started successfully *
any ideas thanks in advance!
Install a superuser zip through cwm.
Sent from my PACMAN MATRIX HD MAXX
Hey there everyone! Seeing as there's not a publicly released 9.0.6 Fastboot only ROM for the T-Mobile variant users, I've taken the liberty to package something up for you!
This tool includes the most recent fastboot for Windows, Linux, and Mac.
Please do not unzip the images.zip file, as it will be done by the tool automatically!
This tool can be used to correct a soft brick (as long as you can get into fastboot you can fix it!), as well as simply flash the International Variant to both the T-Mobile version, as well as the International model.
You must be in fastboot mode prior to running these scripts!
On Windows:
Simply unzip the zip and double click the windows-flash-all-partitions.bat file.
Wait for the images.zip file to finish extracting. (This requires powershell, if you don't have it, unzip the images.zip file to the images directory)
You will be prompted with the option to format your device. Type Y or y for Yes, N or n for No.
Fastboot will begin flashing the partitions for you!
Your device will reboot at the end.
On Linux:
Simply unzip the zip and then cd to the directory with your console.
Ensure you have the unzip command available. If you don't, for some reason, unzip the images.zip file to the images directory.
cd to the unzipped folder and run the following command: sudo ./linux-flash-all-partitions.sh
You will be prompted with the option to format your device. You can type the following: Y,y for Yes, N,n for no.
Fastboot will begin flashing the partitions for you!
Your device will reboot at the end!
For Mac Users: (Console/Terminal Use)
Simply unzip the zip and then cd to the directory with your console.
Ensure you have the unzip command available. If you don't, for some reason, unzip the images.zip file to the images directory.
Run the following command: sudo ./mac-flash-all-partitions.sh
You will be prompted with the option to format your device. You can type the following: Y,y for Yes, N,n for no.
Fastboot will begin flashing the partitions for you!
Your device will reboot at the end!
Upgrading from 9.0.5 should not require a data wipe, but your mileage may vary.
This does not touch any critical partitions, nor does it even try to.
While this should work for the International version as well, it does not flash any critical partitions.
Google Drive Link v1.1: https://drive.google.com/open?id=1oGMQ80He9ORD2yT7jEeOtvUPvRa4U9h_
Of course, let me know if you have any trouble!
Dameon87 said:
Hey there everyone! Seeing as there's not a publicly released 9.0.6 Fastboot only ROM for the T-Mobile variant users, I've taken the liberty to package something up for you!
This tool includes the most recent fastboot for both Windows and Linux.
Please do not unzip the images.zip file, as it will be done by the tool automatically!
On Windows:
* Simply unzip the zip and double click the windows-flash-all-partitions.bat file.
* Wait for the images.zip file to finish extracting. (This requires powershell, if you don't have it, unzip the images.zip file to the images directory)
* You will be prompted with the option to format your device. Type Y or y for Yes, N or n for No.
* Fastboot will begin flashing the partitions for you!
* Your device will reboot at the end.
On Linux:
* Simply unzip the zip and then cd to the directory with your console.
* Ensure you have the unzip command available. If you don't, for some reason, unzip the images.zip file to the images directory.
* run the following command: sudo ./linux-flash-all-partitions.sh
* You will be prompted with the option to format your device. You can type the following: Y,y for Yes, N,n for no.
* Fastboot will begin flashing the partitions for you!
* Your device will reboot at the end!
Upgrading from 9.0.5 should not require a data wipe, but your mileage may vary.
This does not touch any critical partitions, nor does it even try to.
While this should work for the International version as well, it does not flash any critical partitions.
Google Drive Link: https://drive.google.com/file/d/1ii59cmGVUcohZAiJB47fKoJQyikJVaLR/view?usp=sharing
Of course, let me know if you have any trouble!
Click to expand...
Click to collapse
Says TMO. Is this the t-mobile rom?
lollyjay said:
Says TMO. Is this the t-mobile rom?
Click to expand...
Click to collapse
No, it the international version! Sorry!
Dameon87 said:
No, it the international version! Sorry!
Click to expand...
Click to collapse
Thanks you might want to rename it to avoid any confusion
Sent from my crosshatch using XDA Labs
lollyjay said:
Thanks you might want to rename it to avoid any confusion
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
Already done!
So can I follow this to flash 9.0.6 on my TMobile 9.0 version? I just received the unlock bin.
Sent from my ONEPLUS A6013 using Tapatalk
Have tmobile purchased phone. unlocked of course and already running 9.0.5 international rom with no issues.
I am rooted with magisk.
when updating from 9.0.5 to 9.0.6 do I need to do any prep work? Uninstall magisk first?
OR just do what's in the OP and choose not to wipe?
raing said:
Have tmobile purchased phone. unlocked of course and already running 9.0.5 international rom with no issues.
I am rooted with magisk.
when updating from 9.0.5 to 9.0.6 do I need to do any prep work? Uninstall magisk first?
OR just do what's in the OP and choose not to wipe?
Click to expand...
Click to collapse
As long as you don't have any magisk modules that are known to bootloop when uninstalled (The Always on Display one will do this), you should be just fine! I was rooted with Magisk and upgraded to 9.0.6 without a wipe just fine.
Of course afterwards you will need to root again!
_nkay_ said:
So can I follow this to flash 9.0.6 on my TMobile 9.0 version? I just received the unlock bin.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Yes. After you unlock your bootloader you can use this to flash 9.0.6 to your device. You will -need- to wipe, though. So when the question is prompted to format your device, type Y.
@DaeMon87 your instructions say if you do not have power shell, I am on windows 7, so extract the image to the working adb folder?
Some strange reason didnt work for me. im on 9.0.5 right now..
phillymade said:
@DaeMon87 your instructions say if you do not have power shell, I am on windows 7, so extract the image to the working adb folder?
Click to expand...
Click to collapse
Windows 7 has powershell I believe. Try running the bat file. It's safe. It literally won't let you continue if the files don't exist.
djhotsauce said:
Some strange reason didnt work for me. im on 9.0.5 right now..
Click to expand...
Click to collapse
Gimme 5. When I made a find/replace I accidentally deleted a part of each command! Sorry about that! I'll upload an updated bat here in a min for you.
Updated Tools attached to post.
Dameon87 said:
Gimme 5. When I made a find/replace I accidentally deleted a part of each command! Sorry about that! I'll upload an updated bat here in a min for you.
Updated Tools attached to post.
Click to expand...
Click to collapse
fastboot: error: cannot load 'images/vbmeta.img': No such file or directory
fastboot: error: cannot load 'images/vbmeta.img': No such file or directory
fastboot: error: cannot load 'images/vendor.img': No such file or directory
fastboot: error: cannot load 'images/vendor.img': No such file or directory
still getting two errors
***nevermind i just got the file from the .zip.***
djhotsauce said:
fastboot: error: cannot load 'images/vbmeta.img': No such file or directory
fastboot: error: cannot load 'images/vbmeta.img': No such file or directory
fastboot: error: cannot load 'images/vendor.img': No such file or directory
fastboot: error: cannot load 'images/vendor.img': No such file or directory
still getting two errors
Click to expand...
Click to collapse
Likely those files were not properly unzipped. Try extracting them directly from images.zip and putting them into the images directory.
Dameon87 said:
Windows 7 has powershell I believe. Try running the bat file. It's safe. It literally won't let you continue if the files don't exist.
Click to expand...
Click to collapse
How do I force the .bat file to load in powershell rather than cmd. I am on Windows 10 so I know I have powershell just not familiar with it. Second question, since I used the OnePlus one rooter before to install magisk can I use that again or do I have to do it the old fashioned way ? Thank you for putting this together by the way!
OP updated with a new copy of the files including the mac version and the fixes for the flashing files.
feezler said:
How do I force the .bat file to load in powershell rather than cmd. I am on Windows 10 so I know I have powershell just not familiar with it. Second question, since I used the OnePlus one rooter before to install magisk can I use that again or do I have to do it the old fashioned way ? Thank you for putting this together by the way!
Click to expand...
Click to collapse
You don't need to! Just double click the .bat file. It simply runs the unzip command in powershell to avoid having to package anything else in the zip.
However, if you haven't grabbed the fixed bat file from the OP, please do so!
As for the OnePlus rooter, you can just use it again
Dameon87 said:
OP updated with a new copy of the files including the mac version and the fixes for the flashing files.
Click to expand...
Click to collapse
Does the google drive link have the updated tools? Or should users also download the updated tools?
Sent from my crosshatch using XDA Labs
Dameon87 said:
You don't need to! Just double click the .bat file. It simply runs the unzip command in powershell to avoid having to package anything else in the zip.
However, if you haven't grabbed the fixed bat file from the OP, please do so!
As for the OnePlus rooter, you can just use it again
Click to expand...
Click to collapse
Fantastic! I will give this a shot tonight ...fingers crossed!