Related
Now that the bootloader is unlocked, everyone is asking "WTF do I do now?". Well, here's a bit of help to get you started. I'm assuming you already have adb and fastboot setup and working -- if not, quit reading and get that taken care of. Also, I only run Linux...so I'll try to be transparent and only list the fastboot commands.
I assume that you're not a complete moron and can Google what you don't understand.
Don't use the stock\SDK fastboot binary for flashing /system.
An updated fastboot binary for Lin\Win\Mac can be found here on the Batakang FTP from our local, neighborhood Mattlgroff.
Linux -- Rename the file to moto-fastboot and add it to a directory in your $PATH -- Ubuntu\Debian users can just add it to ~/bin (enabled by default)
Windows -- Rename the file to moto-fastboot and put it somewhere handy...that's on you to decide.
ROOT\ADMINISTRATOR INFO
On Linux, you might have to run as root in order to run some of the fastboot commands. If your system uses sudo for root commands, typing "sudo -i" will bring up an interactive sudo shell so you don't have to type sudo over and over again. If your system uses su for root, well, you already know the command.
On Windows, you have to enable Administrator Privileges to be able to run some of the fastboot commands.
Linux Terminal Hints
~/ means your home directory -- example -- "gedit ~/Documents/file.txt" would open file.txt in gedit easier than /home/yourusername/Documents/file.txt
You can add a * to file names and directories to not type as much -- example -- "gedit ~/Doc*/file.txt" is the same as the command above, only shortened. If two files have similar names, like Documents and Downloads, then you have to type the name up until the firs different character then add *.
Use the command "../" to go up\back one directory. The command is stackable so "../../" would go back 2 directories and so forth and so on.
Use "cd" to change directories. Is an example really needed for this...
Proper Apps to Use
For zip file editing, use 7-zip on Windows and Archive Manager (file-roller) on Linux
For editing text files on Windows use Notepad++ or any text editor that has unix line breaks -- do not use default Notepad or Wordpad -- you've been warned. Use what ever you prefer on Linux. I prefer Gedit myself.
Basic Fastboot Command Syntax
fastboot flash "partition" "image" -- flashes partition image where partition is where to write to and image is the path to the image being written.
example -- fastboot flash system /path/to/system.img
fastboot -w -- does a factory reset; to expedite things, "-w" can be added to "fastboot flash system system.img -w"
fastboot continue -- continue with the boot process
fastboot devices -- list devices fastboot recoginzes
fastboot -s "device model number" -- set the device fastboot will write commands to; use "fastboot devices" to find model number
fastboot reboot bootloader -- reboot phone into fastboot mode (or restart fastboot mode while in fastboot); same as "adb reboot bootloader"
fastboot help -- list all of this & more
Command Info
Not all the fastboot commands work for us. Specifically, the "erase" commands. If a wipe command doesn't work, skip it. I'll mark them with a ! at the end if it might fail.
Install CWM Recovery by Epinter
Read Epinter's RAZR HD CWM Thread
Download the recovery image
On stock rom, navigate to /system/etc and rename install-recovery.sh to install-recovery.sh.bak
Reboot into fastboot -- use "adb reboot bootloader" from Terminal\Command Prompt
Wipe the existing recovery -- "fastboot erase recovery" !
Flash the recovery with "fastboot flash recovery cwmrecovery6028-xt925_20130219-epinter.img"
That's it, CWM is installed.
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
Install Stock Fastboots ICS
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.ext4
fastboot erase cache !
fastboot -w
fastboot reboot
Install Alternate Radio
Reboot into fastboot
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
NON-HLOS.bin is found inside a fastboot zip.
Easy Kernel Install
Download kernel-flash.zip in the attachments[/URL]
Open the zip
Replace the zips current boot.img and device_tree.bin from the fastboot of your choice
Install the zip with CWM
By default, kernel-flash.zip comes with Mex Retail kernel and devtree
Easy CWM Install
Download recovery-flash.zip in the attachments[/URL]
Install the zip with CWM
Not sure if its SS compatible, but it is CWM compatible (for the lazy Photon Q users).
Obtain root after installing a Stock Firmware
There are two choices for obtaining root after a stock flash. the closed source SuperSu by Chainfire & and the open source Superuser by Koush.
Download SuperSu zip from Chainfire (Closed Source)
Download Superuser from Koush (Open Source)
Download the one of the root zips above.
Reboot into CWM/TWRP -- adb reboot recovery
Locate and flash the zip (see below for an alternative way)
Reboot, that's it. Nice not having to run exploits\hacks\Linux just for root
Install Rom/Zip file with ADB + CWM
CWM has the awesome ability to install zip files without having to manually copy them to the phone first. All's necessary is a PC with working adb.
Reboot into recovery
Select "install zip from sideload"
On PC, type "adb sideload /path/to/zip" and press enter
The zip will now be copied to the phone's cache & install
Once installed, do any requirements you'd normally do like wipe caches, etc
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Unless you're not rooted with an unlocked BL, there's really no reason why it shouldn't work?
Sent from my N4'd Atrix HD
I was rooted before unlocking... shouldn't it still be rooted?
Sent from my MB886 using Tapatalk 2
miketravis said:
I have done this numerous times and it still will not boot into recovery. I have read and followed epinter, yours, official cwm, and other various Google found instructions (none of them functionally different) and still the same result. It recognizes the phone, writes, completes, then if I reboot and select recovery it goes to the android with the open chest cover with the exclamation point....
Any ideas how I could be screwing this up?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Did you uninstall safestrap?
Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.
miketravis said:
Yep. Should I reinstall it and try again?
Sent from my MB886 using Tapatalk 2
---------- Post added at 01:40 PM ---------- Previous post was at 01:30 PM ----------
reinstalled safestrap and tried again, success!!
Not sure why that made a difference but I got it so thank you very much.
Click to expand...
Click to collapse
Still did not work for me
Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2
miketravis said:
Did you install recovery inside safestrap? Then fastboot cwm?
Sent from my MB886 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.
tvd0405 said:
Yes, I did. After fastboot, I followed the OP instructions to uninstalling the SS recovery and SS app. Boot into recovery and got the open android.
Click to expand...
Click to collapse
same here.
I have the same problem. I was able to flash cwm, uninstall the SS recovery, and uninstall the app. The first time I got the dead android symbol. I restored SS via Titanium Backup, reinstalled the SS recovery, and flashed cwm again. I tried rebooting into recovery and was able to get cwm working. As soon I uninstalled SS and rebooted, I got another dead android.
probably because were all on the XT926 if we were to revert back to XT925 then the recovery should work otherwise we will have to tweak the recovery to get it to work properly witht the XT926 software awesome thing is we can now free up the space that SS used for a rom slot however for noobs you might wana stick with SS once you hardbrick without anything to go back too it will be game over for your phone and then you have to con ATT for another
i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx
htchd2fix said:
i got it.....
i was on ICS 404 bootloader unlcoked and rooted
how the hek you go on bootloader menu (power vol.down???????)
right now im accessing evything with boot widget from play market....
everything works i backed up my stock rom.....
can i try a jellybean rom????? and go back to ICS as many times i want???? from cwm recovery???
thanx
Click to expand...
Click to collapse
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.
skeevy420 said:
From Phone Off, Hold Power and Both Volumes.
If the phone is on, do the above and when the screen goes black, press them all again...I've been doing that for an hour now
I installed MR via fastboot and just now got it booting. I made the mistake of using the SDK fastboot to flash /system.
Click to expand...
Click to collapse
What's MR?
yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?
Markyzz said:
What's MR?
Click to expand...
Click to collapse
Mexican Retail
Install instructions in OP
htchd2fix said:
yes it works.....thanx
i was used to powr vol.down with atrix4g
ok..now can i install any rom and if dont like it go back to may backup????
still a little scared.....
i mean i wont loose root right?
Click to expand...
Click to collapse
You won't lose root
And with an unlocked bootloader, all you gotta do is flash an updater zip with the su binary and app for Stock roms that don't have root
I'll link to a root zip in the op once I find one (or just make it; depends on how quick I find it in a search)
thanx again..
ahahahha...what a beautifullll day....
skeevy420 said:
Mexican Retail
Install instructions in OP
Click to expand...
Click to collapse
is there a point to flash a different firmware? is it required by any means?
I had SS and was backed up, I booted up the "stock ROM" and was successful in unlocking the BL and flashing CWM. I made a new backup of the stock ROM and restored it with success in CWM. In the video it show he has MR , but im confused as to why.
Also, I cant seem to get rid of safestrap....how in the hell do you uninstall it???
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
Note:I'm going to assume you have the Fastboot and ADB Drivers installed and the boot loader is unlocked!
Why is this here?
This thread is made to help new users install the developers preview through what I think is the fastest way and safest way too through the command prompt on Windows.
Responsibility!
If your device becomes bricked, makes toast for you, and anything else I did not mention its simply not my fault since you took it upon your self to do this method.
Credits!Thanks Google for this lovely Operating System. Thank you Chain Fire for providing this method to root Android Lollipop and for your app and boot.img too! Thanks to LG for manufacturing this great device to use and enjoy stock Android. Finally, big thanks to TWRP for providing us with this recovery!
The Steps!Step 1: Download the Lollipop preview HERE, extract it and open the folder with all the image files along with the radio and bootloader image too.
Step 2: Drop all the images to your folder that contains the ADB and Fastboot files
Step 3: Open the folder that contains the ADB and Fastboot files
Step 4: Hold the shift key and right click and click "Open command window here"
Caution! Make sure you back up everything before you begin the process if not its not my fault you forgot to back up.
Step 5: Make sure your device is in fastboot and connected. We are going to replace the boot loader for a newer one. Please make sure the boot loader image name first before we began because i'm just going to use boot loader as a example the real file name will be different. Type the command shown below.
Code:
fastboot flash bootloader bootloader.img
Step 6: Now we are going to flash the Radio as also stated above be sure to check the image name before we flash.
Code:
fastboot flash radio radio.img
Step 7: Now we are going to flash userdata. This part you don't have to worry about the file name you can just copy and paste the command but, I would double check.
Code:
fastboot flash userdata userdata.img
Step 8: Now going to flash boot or the kernel just as step 8 and here from out I will let you know when you have to worry about the file name again.
Code:
fastboot flash boot boot.img
Step 9: Now were flashing the system files.
Code:
fastboot flash system system.img
Step 10: Now were flashing the a custom recovery (twrp for this example) so we can install the SuperSU files later. You can get the recovery image HERE and rename it "Trecovery" and place it to the same folder. After flashing it go to the recovery and from there reboot it.
Code:
fastboot flash recovery Trecovey.img
Yay! We got Android Lollipop now we have to root it.Step 1: Let Andriod Lollipop boot up and go download SuperSu on your device by going to Chainfire SuperSU thread and click on his installable zip link and download SuperSU 2.14 or above. On your computer download his modified boot image HERE and rename it Rboot.img and move it your folder where the ADB and Fastboot files are.
Step 2: On your computer go to fastboot again on your phone and type the code in below.
Code:
fastboot flash boot Rboot.img
Step 3: Go to recovery and install the SuperSU zip as usual, reboot, and that's it. Enjoy!
reserved
Trecovery.img
Thanks for your work. Unfortunately, we already have a sticky thread on flashing images and rooting: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
The method to flash and root lollipop is no different than any other version.
Because we don't want multiple threads with the some information I will close this thread
Thanks.
All,
I need some help. I received the OTA from Motorola but can't load it yet because I'm rooted and using TWRP recovery. I did the following steps so I could download the OTA but am not able to get the stock recovery to load. Here are my steps:
1) Downloaded factory image file TMO_LXE22.46-11_22.21.11.victara_tmo.tmo.en.US.tgz
2) Verified I'm on the same system and build version. On my phone I see Build # LXE22.46-11 and System Version 22.21.11.victara_tmo.tmo.en.US
3) I opened Super SU and did an unroot which removed the app and I assume removed the root
4) Next I booted into fastboot mode and opened a command line on my windows PC
5) I placed the recovery.img file from the downloaded image into the folder
6) I opened a command line and typed "fastboot recovery recovery.img
7) It looks like the file loads correctly, yet when I try to reboot into recovery, I'm getting the android icon with the exclamation point and message command not recognized
Does anyone have any tips on what I may be doing incorrectly?
Thanks,
Rick
Not an expert with fastboot but shouldn't #6 be fastboot flash recovery recovery.img
ContractorDude said:
Not an expert with fastboot but shouldn't #6 be fastboot flash recovery recovery.img
Click to expand...
Click to collapse
You are correct.
Sent from my XT1095 using Tapatalk
Yes, sorry that was a typo. I ended up having to load a fresh copy of 5.0 and then the update.
My steps were correct and the issue was not recovery related.
FYI, that's what the stock recovery is supposed to do when you try to boot to it.
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.