If i use DD to dump factoryfs, can i use this in a Rom as it is?
Ok so i found out how:
ADB shell
su
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
Is this any different to adb pull ?
that could be used to make a full backup of your phone for future recovery directly with ADB?
You sure it's possible? I'm intrigued
Bubble-be said:
Is this any different to adb pull ?
Click to expand...
Click to collapse
Way different.
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO
Once you have have the factoryfs.rfs file how do you use this to flash the phone back?
I used this method to take a copy of the factory firmware before flashing a ROM. I can see in the TAR file used in the ROM I flashed has other RFS files as well.
flash it
stubborn_d0nkey said:
flash it
Click to expand...
Click to collapse
Hi Stubborn_d0nkey,
Thanks but I'm a bit of a noob at this. How exactly do you setup odin to do it as odin wants tar files and when using "one package" that tar combines lots of rfs files.
Can you explain step by step
thanks
astrae said:
Hi Stubborn_d0nkey,
Thanks but I'm a bit of a noob at this. How exactly do you setup odin to do it as odin wants tar files and when using "one package" that tar combines lots of rfs files.
Can you explain step by step
thanks
Click to expand...
Click to collapse
Download Total Commander and add it to a .tar file.
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO
This is becoming interesting. So one could dd all the mount points and flash it back, or dd it back in download mode.
Which block devices should you backup ? To what rfs files do they correspond ?
Another question I have : where are the mount points defined ? I couldn't locate an fstab.
Bubble-be said:
This is becoming interesting. So one could dd all the mount points and flash it back, or dd it back in download mode.
Which block devices should you backup ? To what rfs files do they correspond ?
Another question I have : where are the mount points defined ? I couldn't locate an fstab.
Click to expand...
Click to collapse
No. You dd back in normal mode.
stl6: system
stl7: data
stl8: cache
Sent from my ACID Lestatious 2.0 BUILD 1.7 Galaxy 3 FROYO
Looks like deskjeti is one step further :
[Need Help] Galaxy 3 Backup Tool
I have a firmware for NEC A9 Tablet which contains an android-fs.tar.gz file.
It basically contains the android file system with the usual directories. su is already located in /system/xbin
I am able to flash the firmware and root the firmware using z4root. I was wondering on how to create pre-rooted firmware?
I am comfortable with linux command and permission settings. Can anyone help to point me to the right direction?
Hello to all,
I upgraded my i9000 (Galaxy S) from the rom JVP in [ROM][4.1.2] Slim Bean - I9000 [2.7].
I lost imei and found the standard imei samsung 004 ....
I have a total backup of efs folder. But the problem is that every time you restart the folder is deleted entirely. I tried to copy files from the backup-fs via ADB, root explorer,setting permission of file manually too, trying on different rom as jvs, jvu, ic.
When you flash the rom with odin, it tells me "unable to mount efs". Everything works except the modem and now the imei is empty.
I do not know what to do. I think the problem is mounting the efs folder, but I'm not an expert on linux. Is there a way to delete all the mount point? you can do a real hard reset?
Can you help?
giovanar said:
Can you help?
Click to expand...
Click to collapse
run through efs problems and solutions in My Android Solutions
to solve it
First of all: Tool to be used in this guide was developed by user And_pda from Russian 4pda.ru forum. So all credits must go to And_pda
The original thread (in Russian) is here. Actually the original thread is about several tools to works with different images for different phones. But we will talk only about Moto X.
The guide will describe how to extract all files from system partition from stock firmware. The tools works under Windows (I personally tested it on Win 7).
If you unzip any stock firmware you will find one file, which represents system partition: system.img.
To extract all files from system.img please do:
1. Download ImgExtractor_1_3_4.rar and extract it.
2. Create directory System in the folder where system.img is located;
3. Copy ImgExtractor.exe into the folder where system.img is located;
4. Run CMD and "cd" to the folder where system.img is located
5. In CMD run the following: ImgExtractor system.img System
After ImgExtractor finished you will have all system files and folders in System directory.
That's all
PS. ImgExtractor also can extract modem firmware (NON-HLOS.bin)
Anyway to extract system image on 4.4, inject su binary re-image, and msfastboot flash?
Sent from my XT1080 using Tapatalk
djnikko said:
Anyway to extract system image on 4.4, inject su binary re-image, and msfastboot flash?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Maybe. But to get the locked recovery to flash it must be signed by moto thousand bit code.
extract for something like my signature?
Hey this will mos def save some time. Thanks my dude
Sent from my XT1095
Can you get this to work with motoboot.img? It'll make it possible to downgrade to bootloaders such as 4-21, 3-15, etc.
mr_verystock said:
Can you get this to work with motoboot.img? It'll make it possible to downgrade to bootloaders such as 4-21, 3-15, etc.
Click to expand...
Click to collapse
Phone's cid partition changes with every firmware update so bootloader downgrade will not work. The phone just won't boot up. I know the man who tried all this tricks - he flashed dumps from phones with unlocked bootloaders.
Pretty cool tool... I just wished it would keep the original timestamps for the directories and files....
Is there any way to assemble extracted files and build original system files?
Sent from my SM-N910C using Tapatalk
Latest version if any need it
It can't handle large img files though.
works on Samsung Galaxy S6 , Note 4 , cache.img , hidden.img , files which ext4 unpacker couldn't handle.
How big were the img files? It can't handle the 4GB LG G4 .img files but works fine with the smaller Motorola RAZR HD Maxx .img files.
i used it only for cache and hidden, so <250MB. I didn't tried on larger files.
That's why it works.... the Motorola img files were 1 GB or less... it can't handle the LG G4 files.
it would be great if the author patched/forked the original ext4 unpacker, so it can open newer img's like this (sparse with moded header) , so we would've had a GUI, because imgextractor is only text.
imgextractor is the only one that works on Motorola img files.
yes, even with Samsung Galaxy Note 4 / S6 and newer devices, on the IMG file - the ext4 sparse header is not standard, but i said, since this program (imgextractor) is based on ext4 unpacker sources, it could've keeped that GUI and only mod a little.
Anyway, you could also open IMG with the original ext4 unpacker if you fix it first with IMGEXTRACTOR. to fix: convert IMG file from MODED SPARSE EXT4 to normal EXT4 (> imgextractor.exe original.img temp.ext4 -conv) and then back to FIXED SPARSE EXT4 (> imgextractor.exe temp.ext4 fixed.img -conv). Now open fixed.img in ext4 unpacker program and it will work.
l.e. I found what the problem was, on Samsung Exynos devices, and the newer ones, the IMG files headers are 32 bytes, instead of the normal 28, Chainfire explains it here. So that's why ext4 unpacker gives error on opening. For alternative fix (instead of the conversion i explain upper in this post using imgextractor) you can use Chainfire's sgs4ext4fs tool , works on Windows/Linux, builds and other useful tool here.
Also there is a tool for Motorola IMG files there, see the Usage section.
gracias
tanks bro work in motorola razr hd stock kitkat system.img
BenjaminW8 said:
can you maybe make a more detailed guide how you did this
i cant seem to make sytem.img to extract for the s7 Edge
Click to expand...
Click to collapse
I believe you want be able to utilize Imgextractor as the S7 system.img exceeds the supported size of the Imgextractor
Hello, fellow users, I am new at posting on XDA and as you can see the title "Stock Partitions" I would like to have the Stock Partitions of SM-T350, you may be wondering why I need it, I am fixing the sensors on my tab a ( sm-t350 ) and I think it's going to be fixed by flashing those stock Partitions if anyone has better knowledge I would love to be taught thank you!.
I have tried pulling the stock firmware files ( tar.md5/Odin flashable) but I don't know what partitions I needed to pull regarding on sensors ( i.e. everything excluding wifi e.g. proximity, accelerometer, gyroscope ), I also tried reflashing ( Odin ) the stock firmware but no luck, I only remember that it once work sometime before but after so many modifications on the system I guess I have altered and modified or even remove the partitions where sensors are stored.
Here are some forums for Android Partitions and tips for extracting.
Android Partitions:
https://forum.xda-developers.com/android/general/info-android-device-partitions-basic-t3586565/amp/
Print the Code for the partition table ( stock )
ls -l /dev/block/bootdevice/by-name/
Code for pulling a partition
dd if=/dev/block/mmcblk0pxx of =/sdcard/xxxxxx.img
If anyone can pull every parition on the partition table without the system and Data and upload that here that would be great for me and for everyone.
Thank you so much guys.
Really need that stock efs, persist, and modem patitions thank you guys