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!
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
I know how to fastboot flash .img files and understand it includes the radio and kernel components. I'm rooted and have TWRP recovery. But which .img file contains the radio and which the kernel? I ask because I'll be going from the latest T-Mo rom (LYZ28J) to Project Fi having just received my sim. If I flash just the system.img from LYV48E (Fi rom) will I have the correct kernel and radio or will I have to flash boot.img also or something else? Since kernels and radios can be flashed separately I'm just not sure where everything comes from. I would appreciate some clarity.
Groid said:
I know how to fastboot flash .img files and understand it includes the radio and kernel components. I'm rooted and have TWRP recovery. But which .img file contains the radio and which the kernel? I ask because I'll be going from the latest T-Mo rom (LYZ28J) to Project Fi having just received my sim. If I flash just the system.img from LYV48E (Fi rom) will I have the correct kernel and radio or will I have to flash boot.img also or something else? Since kernels and radios can be flashed separately I'm just not sure where everything comes from. I would appreciate some clarity.
Click to expand...
Click to collapse
have you ever unzipped a factory.img .tar file to see what files it contains?
Groid said:
I know how to fastboot flash .img files and understand it includes the radio and kernel components. I'm rooted and have TWRP recovery. But which .img file contains the radio and which the kernel? I ask because I'll be going from the latest T-Mo rom (LYZ28J) to Project Fi having just received my sim. If I flash just the system.img from LYV48E (Fi rom) will I have the correct kernel and radio or will I have to flash boot.img also or something else? Since kernels and radios can be flashed separately I'm just not sure where everything comes from. I would appreciate some clarity.
Click to expand...
Click to collapse
simms22 said:
have you ever unzipped a factory.img .tar file to see what files it contains?
Click to expand...
Click to collapse
If I were a betting man, I'd be backing the horse called "Wish I'd done that before posting"
Tiptonian said:
If I were a betting man, I'd be backing the horse called "Wish I'd done that before posting"
Click to expand...
Click to collapse
Hahaa. Unzip and you shall receive. LMAO
simms22 said:
have you ever unzipped a factory.img .tar file to see what files it contains?
Click to expand...
Click to collapse
Not sure what you mean by this. I have the system, boot, recovery, and userdata .img files. I don't know which one has the kernel or which one has the radio. You imply I can unzip, for example, system.img to see what files are there, but I cannot unzip it or any of the .img files. My main question still is unanswered which is which .img files do I need to (m)fastboot flash to insure I have the correct (stock) kernel and radio for the Project Fi rom? I may just flash them all, flash TWRP, re-root and start clean, but I wanted to consider the option of keeping data. Any helpful answers?
Tiptonian said:
If I were a betting man, I'd be backing the horse called "Wish I'd done that before posting"
Click to expand...
Click to collapse
prdog1 said:
Hahaa. Unzip and you shall receive. LMAO
Click to expand...
Click to collapse
So glad my post was such a source of amusement for you. Sorry I didn't make it clear I know how download factory images, unzip the .tgz file to get the .tar file. Unzip the .tar file to get to the .zip file. Unzip the .zip file to get the boot, recovery, system, and userdata .img files. But no one actually tried to answer my question.
Groid said:
So glad my post was such a source of amusement for you. Sorry I didn't make it clear I know how download factory images, unzip the .tgz file to get the .tar file. Unzip the .tar file to get to the .zip file. Unzip the .zip file to get the boot, recovery, system, and userdata .img files. But no one actually tried to answer my question.
Click to expand...
Click to collapse
kernel is boot.img, radio is radio.img
Thank you for your reply. I suspected boot.img is the kernel but wanted to make sure. I notice that the radio-shamu-. . .02.78.02.img and boot-shamu. . .71.10.img are in the shamu-lvy48e folder in the .tar file with the flash batch files. The enclosed .zip file has the system, boot, userdata, recovery, and cache .img files along with the text file specifying the bootloader (kernel) and baseband (radio). I now understand that the boot.img is the kernel which is the same version my current one in LYZ28J, so I need not flash it. The radio is different based on the android-info.txt file. So, the last piece of the puzzle for me is will I get the updated radio by flashing the system.img or must I separately flash the radio-shamu -. . .-02.78.02.img?
Groid said:
Thank you for your reply. I suspected boot.img is the kernel but wanted to make sure. I notice that the radio-shamu-. . .02.78.02.img and boot-shamu. . .71.10.img are in the shamu-lvy42e folder in the .tar file with the flash batch files. The enclosed .zip file has the system, boot, userdata, recovery, and cache .img files along with the text file specifying the bootloader (kernel) and baseband (radio). I now understand that the boot.img is the kernel which is the same version my current one in LYZ28J, so I need not flash it. The radio is different based on the android-info.txt file. So, the last piece of the puzzle for me is will I get the updated radio by flashing the system.img or must I separately flash the radio-shamu -. . .-02.78.02.img?
Click to expand...
Click to collapse
youll get the updated radio in the factory.img, but you can always flash the radio itsrlf via fastboot(fastboot flash radio radioname.img).
Groid said:
Thank you for your reply. I suspected boot.img is the kernel but wanted to make sure. I notice that the radio-shamu-. . .02.78.02.img and boot-shamu. . .71.10.img are in the shamu-lvy48e folder in the .tar file with the flash batch files. The enclosed .zip file has the system, boot, userdata, recovery, and cache .img files along with the text file specifying the bootloader (kernel) and baseband (radio). I now understand that the boot.img is the kernel which is the same version my current one in LYZ28J, so I need not flash it. The radio is different based on the android-info.txt file. So, the last piece of the puzzle for me is will I get the updated radio by flashing the system.img or must I separately flash the radio-shamu -. . .-02.78.02.img?
Click to expand...
Click to collapse
If have updated SDK will get everything in flash-all.bat. If not and have to do all separate they are all separate. Bootloader, radio, boot, system, cache, userdata. There is no radio in system.img. It is the radio. img. On first unzip get bootloader, radio, flash-all and the folder for the rest of the images. If want radio fastboot flash radio (radio.img).
Thank you for answering my question about whether or not the radio gets updated by flashing system.img. Unfortunately, I cannot get ADB to work properly. I initially seem to have it working with the ADB devices statement from the command prompt, it returns the serial #, but when I try to execute the batch file ADB seems to be disconnected. At least I have experience with (m)fastboot and will just flash the radio and system .imgs since the bootloader is the same. I'll keep TWRP recovery, format cache, update supersu for root and I should be good to go.
Groid said:
Thank you for answering my question about whether or not the radio gets updated by flashing system.img. Unfortunately, I cannot get ADB to work properly. I initially seem to have it working with the ADB devices statement from the command prompt, it returns the serial #, but when I try to execute the batch file ADB seems to be disconnected. At least I have experience with (m)fastboot and will just flash the radio and system .imgs since the bootloader is the same. I'll keep TWRP recovery, format cache, update supersu for root and I should be good to go.
Click to expand...
Click to collapse
well, adb doesnt work in the bootloader, and its only fastboot that can flash those files..
Thanks, I was responding to using adb to sideload with the flash(all).bat. Fastboot works fine for me so I don't really miss using adb commands.
Hey guys. So I've been trying to manually update with no success so far. I was going to sideload, but I got the November security update ota and there is no ota file for LMY48X to Marshmallow (as far as I know). So I bit the bullet and unlocked the bootloader yesterday, and got the adb and fastboot set up and tried to run the ./flash-all.sh command. (I'm on a Mac) Everything was going fine until I came across an error. So I basically gave up and restored all my user data.
Today I figured I'd try again since I have already unlocked my bootloader and have nothing to lose. mra58k didn't work, so I figured I'd try the mra58n image and removed the -w command from the flash-all.sh and tried again. This is what I got:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(69137) malloc: *** mmap(size=2094391296) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 2092296104 bytes
error: update package missing system.img
Can anyone help me out? I have a feeling I won't be getting the ota through my phone anytime soon.
I may be wrong as this is a pure guess, but did you check the download to confirm it met the checksum? You might just try deleting your download and redownloading the latest version.
haibane said:
I may be wrong as this is a pure guess, but did you check the download to confirm it met the checksum? You might just try deleting your download and redownloading the latest version.
Click to expand...
Click to collapse
No it is Google. Same here. Flashall.bat stops after flashing m-bootloader and m-radio.
After that it is needed to extract all the images and fastboot flash every image.
Don't use the flash-all.sh file to flash, flash the files manually. Plenty of guides outline the commands to use. Plus, make sure that you're Android SDK Tools is updated to the latest version.
RMarkwald said:
Don't use the flash-all.sh file to flash, flash the files manually. Plenty of guides outline the commands to use. Plus, make sure that you're Android SDK Tools is updated to the latest version.
Click to expand...
Click to collapse
Thanks for the reply. So I went ahead and followed your advice and tried to do it manually. I checked everything was up to date. I flashed the bootloader, radio, recovery and boot images and rebooted the bootloader between every flash with no incident. Then I tried to flash the system.img and it first everything seemed to be ok but the terminal is stuck at "sending sparse 'system' " and hasn't done anything in 20 minutes. I'm afraid to do anything right now. Is it ok to close terminal, reopen it and try flashing the system.img again?
ICStevenC. said:
Thanks for the reply. So I went ahead and followed your advice and tried to do it manually. I checked everything was up to date. I flashed the bootloader, radio, recovery and boot images and rebooted the bootloader between every flash with no incident. Then I tried to flash the system.img and it first everything seemed to be ok but the terminal is stuck at "sending sparse 'system' " and hasn't done anything in 20 minutes. I'm afraid to do anything right now. Is it ok to close terminal, reopen it and try flashing the system.img again?
Click to expand...
Click to collapse
Hmmm...the system.img does take time but shouldn't take 20 minutes. Did you flash all the .img files separately, or did you use the command:
Code:
fastboot -w update image-shamu-mra58n.zip
?
I've never done any of this from a Mac, only Linux and Windows, but here's what I do when flashing manually. I extract the contents of the factory image zip, AND the image-shamu-mra58n.zip into my SDK directory (see image attached).
Once everything is extracted, after backing up things I wanna save on my device, I boot to the bootloader and go to town:
Code:
fastboot erase boot
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot erase system
Code:
fastboot erase userdata
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img
Code:
fastboot reboot-bootloader
Code:
fastboot flash radio radio-shamu-d4.01-9625-05.27+fsg-9625-02.104.img
Code:
fastboot reboot-bootloader
Code:
fastboot flash system system.img
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash cache cache.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot reboot
RMarkwald said:
Hmmm...the system.img does take time but shouldn't take 20 minutes. Did you flash all the .img files separately, or did you use the command:
Code:
fastboot -w update image-shamu-mra58n.zip
?
Click to expand...
Click to collapse
No, I decompressed that zip and flashed them all separately using the
Code:
./fastboot flash
command and dragging the files directly to the terminal and then using
Code:
./fastboot reboot-bootloader
in between every flash.
ICStevenC. said:
No, I decompressed that zip and flashed them all separately using the
Code:
./fastboot flash
command and dragging the files directly to the terminal and then using
Code:
./fastboot reboot-bootloader
in between every flash.
Click to expand...
Click to collapse
Okay, seems like you're on the right path. See my post above. You'll erase everything first, then flash everything back one by one, kinda like what you are already doing. I've never had issues doing it this way ever, it may be overkill and it will wipe your phone completely, but if you've backed things up (pictures, docs, music, etc) beforehand, no biggie. The only times I reload the bootloader is after flashing the bootloader, and then the radio.
The system.img will take the longest, and userdata will take a little time too, but the others should be almost instant.
RMarkwald said:
Okay, seems like you're on the right path. See my post above. You'll erase everything first, then flash everything back one by one, kinda like what you are already doing. I've never had issues doing it this way ever, it may be overkill and it will wipe your phone completely, but if you've backed things up (pictures, docs, music, etc) beforehand, no biggie. The only times I reload the bootloader is after flashing the bootloader, and then the radio.
The system.img will take the longest, and userdata will take a little time too, but the others should be almost instant.
Click to expand...
Click to collapse
The terminal doesn't appear to be responding to any command now. I tried erasing boot and after pressing enter, nothing happened. Closing it and reopening it doesn't help. Should I try restarting my computer?
ICStevenC. said:
The terminal doesn't appear to be responding to any command now. I tried erasing boot and after pressing enter, nothing happened. Closing it and reopening it doesn't help. Should I try restarting my computer?
Click to expand...
Click to collapse
Yeah, give that a shot. As long as you have bootloader access you will be okay.
RMarkwald said:
Yeah, give that a shot. As long as you have bootloader access you will be okay.
Click to expand...
Click to collapse
I am now on 6.0 and everything appears to be functional. Thank you so much for all your help! I really appreciate it.
Awesome man! Glad I could help.
I accidentally flashed the radio image over the modem partition, and now my Turbo won't boot. I can't find the img after a quick google. Can someone with more time to look please give me a link?
BTW I tried using a full stock image that I downloaded when I unlocked, and it doesn't seem to have included the modem image.
http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327
schwinn8 said:
http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327
Click to expand...
Click to collapse
That package has the radio.img, not the modem.img. What I need is the modem, because I accidentally overwrote it with the radio. now my damn phone won't boot.
immadeofpixels27 said:
That package has the radio.img, not the modem.img. What I need is the modem, because I accidentally overwrote it with the radio. now my damn phone won't boot.
Click to expand...
Click to collapse
radio = modem
immadeofpixels27 said:
That package has the radio.img, not the modem.img. What I need is the modem, because I accidentally overwrote it with the radio. now my damn phone won't boot.
Click to expand...
Click to collapse
Those packages do have the modem.img...
And as @ChazzMatt stated modem <=> radio
Do you have a TWRP backup where you can restore EVERYTHING?
This is not our Quark TWRP below, it's just an example to show there are several categories you probably backed up and could restore. Actually many more categories than shown here.
In our TWRP, we have:
System
Data
Cache
Modem
Logo
Boot
Recovery
You can restore the modem partition through TWRP as well as the boot partition, if you need that.
immadeofpixels27 said:
That package has the radio.img, not the modem.img. What I need is the modem, because I accidentally overwrote it with the radio. now my damn phone won't boot.
Click to expand...
Click to collapse
Well that's a bummer Pixel, I can upload a (hidden) TWRP backup of everything (no data, you can't have my data partition, lol) if that'll help you out.
iiWoodstocK said:
Those packages do have the modem.img...
And as @ChazzMatt stated modem <=> radio
Click to expand...
Click to collapse
ChazzMatt said:
Do you have a TWRP backup where you can restore EVERYTHING?
This is not our Quark TWRP below, it's just an example to show there are several categories you probably backed up and could restore. Actually many more categories than shown here.
In our TWRP, we have:
System
Data
Cache
Modem
Logo
Boot
Recovery
You can restore the modem partition through TWRP as well as the boot partition, if you need that.
Click to expand...
Click to collapse
NepoRood said:
Well that's a bummer Pixel, I can upload a (hidden) TWRP backup of everything (no data, you can't have my data partition, lol) if that'll help you out.
Click to expand...
Click to collapse
I also thought that modem == radio until I tried the fastboot command
Code:
fastboot flash modem radio.img
As it turns out, Modem and Radio are, in fact, separate partitions on the device. And if you flash the radio.img to the modem partition, ResRemix gets stuck in the boot animation and stock su4tl-44 only boots to recovery. Additionally, I can't mount /data or /cache in TWRP anymore... I even tried re-flashing gpt.bin.
If anyone could somehow pull all the contents of their modem partition and package it in something flashable via fastboot, that would be most helpful.
immadeofpixels27 said:
I also thought that modem == radio until I tried the fastboot command
Code:
fastboot flash modem radio.img
As it turns out, Modem and Radio are, in fact, separate partitions on the device. And if you flash the radio.img to the modem partition, ResRemix gets stuck in the boot animation and stock su4tl-44 only boots to recovery. Additionally, I can't mount /data or /cache in TWRP anymore... I even tried re-flashing gpt.bin.
Click to expand...
Click to collapse
The command is
fastboot flash radio radio.img
http://forums.androidcentral.com/sp...astboot-flash-radio-modem-using-fastboot.html
There is a separate modem partition you can flash -- but not an ".img" file for the "flash modem" command. According to all the recovery commands I can find, it's a .bin file you should be flashing for the fastboot flash modem ____.bin.
as in
mfastboot flash modem NON-HLOS.bin
How to Manually Flash Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
[GUIDE] Moto G - Restore stock firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Moto X - Return to Stock
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
How to Fix your Bricked Moto E and give it a New Life!
http://techylab.com/1576/fix-bricked-moto-e/
All three of those Motorola-based guides for Motorola phones show
mfastboot flash modem NON-HLOS.bin
ChazzMatt said:
The command is
fastboot flash radio radio.img
http://forums.androidcentral.com/sp...astboot-flash-radio-modem-using-fastboot.html
There is a separate modem partition you can flash -- but not an ".img" file for the "flash modem" command. According to all the recovery commands I can find, it's a .bin file you should be flashing for the fastboot flash modem ____.bin.
as in
mfastboot flash modem NON-HLOS.bin
[GUIDE] Moto G - Restore stock firmware
http://forum.xda-developers.com/showthread.php?t=2542219
Moto X - Return to Stock
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
How to Fix your Bricked Moto E and give it a New Life!
http://techylab.com/1576/fix-bricked-moto-e/
All three of those Motorola-based guides for Motorola phones show
mfastboot flash modem NON-HLOS.bin
Click to expand...
Click to collapse
Yes, I know that now. The problem is that I thought modem and radio were synonymous when I flashed the radio.img onto the modem partition. I already know I screwed up, I just need that file that actually belongs in the modem partition. It's not in any stock firmware .zip I can find, including BHB27's AFH account and RootJunky website
immadeofpixels27 said:
I just need that file that actually belongs in the modem partition. It's not in any stock firmware .zip I can find, including BHB27's AFH account and RootJunky website
Click to expand...
Click to collapse
Sounds like it's the "NON-HLOS.bin"
______
If you can fastboot, you've tried this?
[ROM] SU4TL-49 100% Stock
http://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
Obviously the full non-TWRP version...
TheSt33v said:
SU4TL-49 Stock Image for XT1254: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
Flash with TWRP.
This package will flash every image in the SU4TL-49 firmware package except for recovery. It should bring your phone to almost 100% stock. The only image that is not included is the recovery image, because that would overwrite TWRP. If you need the stock recovery, download this: https://mega.nz/#!LwhxyCaZ!NZVi3pA77t7Qlxm1gFQr340SHurOAJEhDQsiR8QFbMc. Install it using the Install Image option in TWRP.
Yes, it does include modems.
No, it will not re-lock your bootloader.
No, it won't erase your data, but you should do a factory reset in TWRP after flashing this. You might be able to get away without it if you're coming from a modified stock rom, but if you leave out the factory reset after coming from a CM-based rom, you're gonna have a bad time.
Deodexed version here for those who may want it: https://mega.nz/#!zxAEHJjS!hqNDjOGJoE3eI3rwL48h45Lovj764quxFsWP9IsN_Z4
If you need the full, non-TWRP version, here it is: https://mega.nz/#!ao4zmQQB!T2VClxKcTb-ePAhHotvlSR3NCxG0tRY1YEhMtti_H3k
Click to expand...
Click to collapse
i have a .49 modem
https://www.androidfilehost.com/?fid=24732830915362860
---------- Post added at 04:36 PM ---------- Previous post was at 04:30 PM ----------
oh, found .44
https://www.androidfilehost.com/?fid=24732872338309178
quantum tao said:
i have a .49 modem
https://www.androidfilehost.com/?fid=24732830915362860
---------- Post added at 04:36 PM ---------- Previous post was at 04:30 PM ----------
oh, found .44
https://www.androidfilehost.com/?fid=24732872338309178
Click to expand...
Click to collapse
Those are TWRP backups, right? If that's the case, they're for the radio partition, despite being labelled modem... I already tried restoring a modem backup in TWRP...
Just want to chime in that radio contains the modem, and also contains fsg and modem storage 1 & 2.
You can use laginimaineb's unpack_motoboot.py script, found here:
https://github.com/laginimaineb/unpack_motoboot
to extract the individual partitions of both bootloader and radio images from fastboot packages.
Fyi, the modem partition has to be unsparsed with simg2img before it will flash properly in recovery.
Also noticed that at least with lra and vzw builds, the specific radio for the corresponding build is required for everything to function properly.
Note:
mdm1m9kefs1 = modem storage 1
mdm1m9kefs2 = modem storage 2
mdm1m9kefs3 = fsg
I have made flashable zips of all vzw and lra radios for my personal use; if there is any interest, I'll post them up
Q9Nap said:
Just want to chime in that radio contains the modem, and also contains fsg and modem storage 1 & 2.
You can use laginimaineb's unpack_motoboot.py script, found here:
https://github.com/laginimaineb/unpack_motoboot
to extract the individual partitions of both bootloader and radio images from fastboot packages.
Fyi, the modem partition has to be unsparsed with simg2img before it will flash properly in recovery.
Also noticed that at least with lra and vzw builds, the specific radio for the corresponding build is required for everything to function properly.
Note:
mdm1m9kefs1 = modem storage 1
mdm1m9kefs2 = modem storage 2
mdm1m9kefs3 = fsg
I have made flashable zips of all vzw and lra radios for my personal use; if there is any interest, I'll post them up
Click to expand...
Click to collapse
How is that script used? I have Python 3.5 installed, but dragging and dropping the file to be unpacked onto the .py didn't do anything.
Also, your premade zips would be very helpful
immadeofpixels27 said:
How is that script used? I have Python 3.5 installed, but dragging and dropping the file to be unpacked onto the .py didn't do anything.
Also, your premade zips would be very helpful
Click to expand...
Click to collapse
I'm using python 2.7, but it may work with 3.5.
If you enter "unpack_motoboot.py" in a terminal, it will list usage instructions:
unpack_motoboot.py <MOTOBOOT_IMAGE> <UNPACK_DIR>
Example:
Code:
unpack_motoboot.py radio.img .
simg2img modem modem.raw
I'll try to get around to making a thread of flashable radio zips soon...
Q9Nap said:
I'm using python 2.7, but it may work with 3.5.
If you enter "unpack_motoboot.py" in a terminal, it will list usage instructions:
unpack_motoboot.py <MOTOBOOT_IMAGE> <UNPACK_DIR>
Example:
Code:
unpack_motoboot.py radio.img .
simg2img modem modem.raw
I'll try to get around to making a thread of flashable radio zips soon...
Click to expand...
Click to collapse
Okay, I installed python 2.7, but didn't add the path variables because I already have 3.5 and don't want two things trying to run the same file. How do I run the script without the path variables? It's not playing nice...
Q9Nap said:
I'm using python 2.7, but it may work with 3.5.
If you enter "unpack_motoboot.py" in a terminal, it will list usage instructions:
unpack_motoboot.py <MOTOBOOT_IMAGE> <UNPACK_DIR>
Example:
Code:
unpack_motoboot.py radio.img .
simg2img modem modem.raw
I'll try to get around to making a thread of flashable radio zips soon...
Click to expand...
Click to collapse
Alright, I have the unpacked modem file, but simg2img doesn't work in Command prompt or Python 2.7 shell... is it a Linux command?
EDIT: also, isn't the file I need supposed to be a .bin, not a .raw?
immadeofpixels27 said:
Alright, I have the unpacked modem file, but simg2img doesn't work in Command prompt or Python 2.7 shell... is it a Linux command?
EDIT: also, isn't the file I need supposed to be a .bin, not a .raw?
Click to expand...
Click to collapse
Simg2img is available as an exe, but the Linux one is what I usually use as the windows one doesn't always work.
I recommend downloading superr's kitchen, which has a nice collection of tools for working with image files.
As for the extension type, it is arbitrary what you name the file, as long as your updater-script matches.