Related
Guys, I need some help. I rooted with Androot and flashed PSGroove with ROM Manager. Now I need to flash the stock recovery back.
I followed a guide (cant post link) but I get "error: cannot load recovery.img", I don't want to touch the ROM because it's stock.
Anyway, where can I find stock FRF91 recovery.img?
Also, there is no install-recovery.sh in system/etc/ and I didn't delete it, where can I get it too?
Thanks.
Download a stock FRF91 image, extract the ZIP, you'll see recovery.img.
I downloaded around 3 stock FRF91's and none included recovery.img
I need it too...Where can I find this stock recovery.img ?
thx for help
i have massive problems restoring stock recovery.img on frf91 nothing works ...
i re enabled install-recovery.sh started it ... did not work ---
downloaded the stock recovery.img
/mnt/sdcard $ md5sum recovery.img
md5sum recovery.img
336f05884ade218f2a0932df9bd770a2 recovery.img
flash_image it .. did not worked ... any help ?
Restore the two files you deleted when you rooted:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
Sent from my Nexus One using XDA App
did this already ... invoked the install-recovery.sh manualy ... will post output later ... STILL NO OTA updates :/
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.
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.
hi guys, all custom roms are flashable. how can i fastboot flash the system partition of any custom rom, lile aicp or others? is that possible someway? tia!
I believe unpacking the system.new.dat from a ROM zip gives you a system.img, which I can only assume is fastboot flashable with fastboot command
can't open the .dat file as archive here with 7zip how could I unpack it?
EDIT: I see now you said "unpack" not uncompress... googling for that now!
FcukBloat said:
can't open the .dat file as archive here with 7zip how could I unpack it?
EDIT: I see now you said "unpack" not uncompress... googling for that now!
Click to expand...
Click to collapse
you can extract your system.new.dat by following this guide
thanks both! I suceeded in installing aicp's system image via fastboot after unpacking system.new.dat with a tool found on xda similar to the one you linked
thanks again!
Hi all, I want to clean install stock rom via fastboot. I used to do this on my oneplus one a while back. I think that I need to install img files to five partitions (boot.img, recovery.img, system.img, userdata.img and cache.img). Are there any other files that need to installed (eg bin or mbn files)?
I think I should be able to get the img files by unzipping the stock rom files. Has anyone tried to get the img files from unzipped stock rom and install via fastboot?
Any help is greatly appreciated.
Thanks
Don't know exactly, but also interested to learn about this!
OnePlus does not provide fastboot flashable roms, the only way to get them would be to update uusing the recovery first and extracting the .img files afterwards, but then you don't need them anymore since you are already upgraded.
Jo_Jo_2000 said:
OnePlus does not provide fastboot flashable roms, the only way to get them would be to update uusing the recovery first and extracting the .img files afterwards, but then you don't need them anymore since you are already upgraded.
Click to expand...
Click to collapse
The system.new.dat format is not unique to oneplus, but the standard for flashable android zips since version 6 (aka marshmellow). The system.new.dat, system.patch.dat and system.transfare.list are build from system.img while building a rom (aka compile rom from source). This process is NOT unidirectional; you can easily revert it. I'm on linux, so you have to google, how this is accomblished on win or darwin. For linux users:
https://github.com/xpirt/sdat2img