Related
This guide is for MS Windows users!
For a long time, I have struggled to find a solution to a very basic question. How do I extract the files/apps from my Nandroid Backups directly on my PC?
If you have been wondering about this too and haven't found a solution yet, this guide is for you!
Tool (See Attachment) : Unyaffs: Unyaffs is a program/binary to extract files from a yaffs file system image. Now it can only extract images created by mkyaffs2image. To know more head here (Do not download anything from there)
Steps:
1. Copy your Nandroid backup image file/s(Eg system.img or data.img etc) to a suitable folder on your PC. (Keep the original copy intact, just duplicate any/all image files that you want to extract)
2. Download the attachment and extract its contents (unyaffs.exe and cywin1.dll) to the same folder as your Nandroid image file/s.
3. Open a command window in that folder (Shift + Right Click -->> open command window here)
4. Now type the following command to extract the desired image file.
Code:
unyaffs xxxx.img
Note: xxxx is any .img file you want to extract eg system.img, data.img etc etc
5. Wait. The tool will display "end of image" when it is done.
Done.
6. The extracted data should be in the same directory as the tool is.
Eg. If you want to restore/extract your contacts:
Extract the data.img
Code:
unyaffs data.img
Your contacts will be in:
Code:
\data\data\com.android.providers.contacts\databases
nice find buddy...i was looking for a method to extract img files and fetch my backup data...thanks...:good:
Great One buddy. Now I can extract these from my backup as well.
@Niks: buddy, mistakenly pressed thanks button for you. I m thinking, if you will it to be back..??
kataria.vikesh said:
Great One buddy. Now I can extract these from my backup as well.
@Niks: buddy, mistakenly pressed thanks button for you. I m thinking, if you will it to be back..??
Click to expand...
Click to collapse
lol:laugh:...it happens sometimes...i am thanking you for thanking me by mistake.. :good:
this is a very very useful tool... once my room mate forgot to manually backup some data and had only taken a cwm, then i searched and searched online and finally found this somewhere.. mounted the data on pc and then totally forgot about it.. thanks so much for posting it here buddy..
I had done this about a year back... had really forgotten about sharing it with you all.. i was very new to xda then..
vbz89 said:
this is a very very useful tool... once my room mate forgot to manually backup some data and had only taken a cwm, then i searched and searched online and finally found this somewhere.. mounted the data on pc and then totally forgot about it.. thanks so much for posting it here buddy..
I had done this about a year back... had really forgotten about sharing it with you all.. i was very new to xda then..
Click to expand...
Click to collapse
The files in my backup are:
- boot.img - - - - - - - - - - (8,192 KB)
- chache.ext4.tar - - - - - (0 KB)
- chache.ext4.tar.a - - - - (108 KB)
- data.ext4.tar - - - - - - - (0 KB)
- data.ext4.tar.a - - - - - (820,985 KB)
- nandroid.md5 - - - - - - (1 KB)
- recovery.img - - - - - - - (8,192 KB)
- system.ext4.tar - - - - (0 KB)
- system.ext4.tar.a - - - ( 361,039 KB)
I can't open either of them with unyaffs. For the:
- ".img" and ".md5" files I get the message: broken image file
- ".tar" files I get: end of image, but no files in the folder (because the archives have 0KB, I guess)
- ".a" files I get the following:
Exception: STATUS_ACCESS_VIOLATION at eip=004010B0
eax=E3130040 ebx=00000000 ecx=00000000 edx=00DD1662 esi=0028CD34 edi=61179FC3
ebp=0028CCD8 esp=0028CCA0 program=C:\Users\Administrator\Desktop\2013-01-29.12.43.40\New
folder\unyaffs.exe, pid 1436, thread main
cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B
Stack trace:
Frame Function Args
0028CCD8 004010B0 (0028CD39, 00000000, 612058E8, 00401333)
0028CD08 004013AF (00000002, 00D98400, 00D982B0, 00000001)
0028CD68 61006CD3 (00000000, 0028CDA4, 61006570, 7EFDE000)
End of stack trace
My backup was made with CWM-Based Touch Recovery v6.0.1.2 (from SyiahKernel S2-v4.1.5).
Does anyone know if there is a way so I can extract a single file from this backup?
Thank you.
dmarcelro said:
The files in my backup are:
- boot.img - - - - - - - - - - (8,192 KB)
- chache.ext4.tar - - - - - (0 KB)
- chache.ext4.tar.a - - - - (108 KB)
- data.ext4.tar - - - - - - - (0 KB)
- data.ext4.tar.a - - - - - (820,985 KB)
- nandroid.md5 - - - - - - (1 KB)
- recovery.img - - - - - - - (8,192 KB)
- system.ext4.tar - - - - (0 KB)
- system.ext4.tar.a - - - ( 361,039 KB)
I can't open either of them with unyaffs. For the:
- ".img" and ".md5" files I get the message: broken image file
- ".tar" files I get: end of image, but no files in the folder (because the archives have 0KB, I guess)
- ".a" files I get the following:
My backup was made with CWM-Based Touch Recovery v6.0.1.2 (from SyiahKernel S2-v4.1.5).
Does anyone know if there is a way so I can extract a single file from this backup?
Thank you.
Click to expand...
Click to collapse
This will not work with newer recoveries because they use the newer ext4 filesystem for packaging/compressing instead of the older yaffs filesystem used by CWMv4. This will only work with yaffs filesystem recoveries. Only .android_secure.img, system.img, data.img, cache.img and hidden.img are supported. It cannot extract boot.img and recovery.img because these are not packaged/compressed by CWM. CWM just pulls these images from /dev/block and generates an md5 for them along with other packages. In short recovery and boot are not created by CWM, these are pre-compiled images and hence cannot be extracted using this tool.
You can try these options: (Not tested).
EXT4 imagefile unpacker
OR
If you have access to linux, try this.
OR
I assume Dsixda's Kitchen on XDA can help you. I can't remember but, I think it can handle ext4.tar files, give it a go. Search Dsixda's Kitchen on XDA.
The-Droidster said:
You can try these options: (Not tested).
["...sourceforge.net/projects/androidicsjbext/"]EXT4 imagefile unpacker
Click to expand...
Click to collapse
Doesn't work.
The-Droidster said:
OR
If you have access to linux, try ["...ubuntuforums.org/showthread.php?t=2103602"].
Click to expand...
Click to collapse
No more linux on my PC.... ufffffffff
The-Droidster said:
OR
I assume Dsixda's Kitchen on XDA can help you. I can't remember but, I think it can handle ext4.tar files, give it a go. Search Dsixda's Kitchen on XDA.
Click to expand...
Click to collapse
I'll check this, but it requires a lot of searching. Could not find what I want with few clicks.
Thank you.
No more linux on my PC.... ufffffffff
Click to expand...
Click to collapse
You can use cygwin in windows if you don't have linux.
I'll check this, but it requires a lot of searching. Could not find what I want with few clicks.
Thank you.
Click to expand...
Click to collapse
Dsixda's Kitchen
The-Droidster said:
You can use cygwin in windows if you don't have linux.
Dsixda's Kitchen
Click to expand...
Click to collapse
Ok, you convinced me. I'll learn to cook my own ROM. Thanks once more. :good:
Hi guys, I get this error message when tryin' this (Windows 7 - 64 bit, Clockworkmod backup)
Code:
unyaffs data.ext4.tar
1 [main] unyaffs 1044 exception::handle: Exception: STATUS_ACCESS_VIOLATION
1242 [main] unyaffs 1044 open_stackdumpfile: Dumping stack trace to unyaffs.e
xe.stackdump
The same with system.ext4.tar.
Did you read thrpugh the thread at least once? It's just one page, really not that hard.
Sent from my LG-P880
Ok, unyaffs won't work with newer versions of backup but I found out Titanium Backup can do that job.
finding photos
I have a few backups and have looked through the files after running the command prompt. Is it possible to find any photos that may have been there and where would i look
jomara1611 said:
I have a few backups and have looked through the files after running the command prompt. Is it possible to find any photos that may have been there and where would i look
Click to expand...
Click to collapse
which one?
Sent from my XT1033 using Tapatalk
Open image file failed
The-Droidster said:
This guide is for MS Windows users!
For a long time, I have struggled to find a solution to a very basic question. How do I extract the files/apps from my Nandroid Backups directly on my PC?
If you have been wondering about this too and haven't found a solution yet, this guide is for you!
Tool (See Attachment) : Unyaffs: Unyaffs is a program/binary to extract files from a yaffs file system image. Now it can only extract images created by mkyaffs2image. To know more head here (Do not download anything from there)
Steps:
1. Copy your Nandroid backup image file/s(Eg system.img or data.img etc) to a suitable folder on your PC. (Keep the original copy intact, just duplicate any/all image files that you want to extract)
2. Download the attachment and extract its contents (unyaffs.exe and cywin1.dll) to the same folder as your Nandroid image file/s.
3. Open a command window in that folder (Shift + Right Click -->> open command window here)
4. Now type the following command to extract the desired image file.
Code:
unyaffs xxxx.img
Note: xxxx is any .img file you want to extract eg system.img, data.img etc etc
5. Wait. The tool will display "end of image" when it is done.
Done.
6. The extracted data should be in the same directory as the tool is.
Eg. If you want to restore/extract your contacts:
Extract the data.img
Code:
unyaffs data.img
Your contacts will be in:
Code:
\data\data\com.android.providers.contacts\databases
Click to expand...
Click to collapse
ERROR : Open image file failed..........is dat also work for cache.yaffs2 files ??
Error
when running the command unyaffs boot.img through command prompt, it tells me "broken img" is this corrupted data?
Introduction
You probably know already that starting from Android 5.x (Lollipop) compiled roms (aosp,cm,stock) are not compressed anymore the way they used to be on previous android versions. On previous versions all content inside /system folder that has to be extracted within our device was either uncompressed (simple /system folder inside our flashable zip) or compressed in a system.img file, which it is a ext4 compressed file; both of these, anyway, were readable and we could see all system files (app,framework, etc).
The problem comes in >=5.0 versions, this method is not used anymore. Why? Because roms started to be always larger, so it is necessary to compress them even more.
What does new Android zips (full roms, but also otas) contain?
New Android flashable zips are made this way:
boot.img (kernel)
file_contexts (selinux related)
META-INF (folder containing scripts)
system.new.dat (compressed /system partition)
system.patch.dat (for OTAs)
system.transfer.list (see explanation below)
What does updater-script contains then?
The updater-script uses a brand new function: block_image_update(), this method basically decompresses necessary files inside the device. Let's study it.
From google git source code, if we go inside the new file /bootable/recovery/updater/blockimg.c, we find at the end of it the registration of the function block_image_update() as the method BlockImageUpdateFn() which starts at line 254. Here finally we find all information we need to know about the decompression of the .dat file(s). First file we analyze is system.transfer.list which Google tells us:
The transfer list is a text file containing commands to transfer data from one place to another on the target partition.
Click to expand...
Click to collapse
But what each line means?:
First line is the version number of the transfer list; 1 for android 5.0.x, 2 for android 5.1.x, 3 for android 6.0.x, 4 for android 7.x/8.x
Second line is the total number of blocks being written
Third line is how many stash entries are needed simultaneously (only on versions >= 2)
Fourth line is the maximum number of blocks that will be stashed simultaneously (only on versions >= 2)
Fifth line and subsequent lines are all individual transfer commands.
Click to expand...
Click to collapse
Ok, but how to decompress the system.new.dat file?
All instructions are below. sdat2img, rimg2sdat and img2sdat binaries are involved. Please read carefully step by step.
NOTE for OTAs
If you are looking on decompressing system.patch.dat file or .p files, therefore reproduce the patching system on your PC, check imgpatchtools out by @erfanoabdi.
You can use/modify these files and/or include them in your work as long as proper credits and a link to this thread are given.
If you have questions or problems write here
Are you building from source and want to revert to the old flashing method without DAT files?
Do this (thx @Elluel):
1 - Delete this line
2 - Make sure you have this commit
Thanks
- howellzhu & luxi78 - for initial source codes
- all contributors from github
Ubuntu
Ubuntu 64-bit - Guide
Step 1 - Decompressing = DAT (sparse data) -> EXT4 (raw image)
We're now using sdat2img binary, the usage is very simple (make sure you have python 2.7+ installed):
./sdat2img.py <transfer_list> <system_new_file> [system_img]- <transfer_list> = input, system.transfer.list from rom zip
- <system_new_file> = input, system.new.dat from rom zip
- [system_img] = output ext4 raw image file
and a quick example:
./sdat2img.py system.transfer.list system.new.dat system.imgby running this command you will get as output the file my_new_system.img which is the raw ext4 image.
Step 2 - Decompress EXT4 (raw image) -> OUTPUT folder -> Compress EXT4 (raw image)
Now we need to mount or ext4 raw image into an output folder so we can see apks/jars etc.
To do this we need to type this command:
sudo mount -t ext4 -o loop system.img output/As you can see there is a new folder called output which we can edit/modify/delete your files (not able to? see here)
Now we need to compress it back to a raw ext4 image, to do this we need the make_ext4fs binary. Make sure you have the file_contexts file (taken from the Rom zip) inside the make_ext4fs path. Then type this (got issues? see here)
./make_ext4fs -T 0 -S file_contexts -l 1073741824 -a system system_new.img output/You will get the new raw ext4 image called 'system_new.img' ready for the next step.
Step 3 - Converting = EXT4 (raw image) -> IMG (sparse image)
Now we need to convert the ext4 raw image into a sparse image. For this you need img2simg binary you can find here (thx to @A.S._id).
The usage is simple:
img2simg <raw_image_file> <sparse_image_file>Pretty self-explanatory, the output will be a new sparse image (.img).
Step 4 - Converting = IMG (sparse image) -> DAT (sparse data)
Now we need the img2sdat binary, the usage is very simple (make sure you have python 2.7+ installed):
./img2sdat.py <system_img>- <system_img> = name of input sparse image file (from step 3)
As you can see the output is composed by system.transfer.list, (system.patch.dat) & system.new.dat, ready to be replaced inside your Rom zip.
DOWNLOADs
sdat2img.py
- github.com
make_ext4fs
- mega.co.nz
img2sdat.py
- github.com
Source - Changelog
sdat2img
Repo: https://github.com/xpirt/sdat2img
Changelog: https://github.com/xpirt/sdat2img/commits/master
Source: https://github.com/xpirt/sdat2img/blob/master/sdat2img.py
img2sdat
Repo: https://github.com/xpirt/img2sdat
Changelog: https://github.com/xpirt/img2sdat/commits/master
Source: https://github.com/xpirt/img2sdat/blob/master/img2sdat.py
Windows
Windows 32/64 bit - Guide
Step 1 - Decompressing = DAT (sparse data) -> EXT4 (raw image)
We're now using sdat2img.py binary, the usage is very simple (make sure you have python 3.x installed):
sdat2img.py <transfer_list> <system_new_file> <system_ext4>- <transfer_list> = input, system.transfer.list from rom zip
- <system_new_file> = input, system.new.dat from rom zip
- <system_ext4> = output ext4 raw image file
and a quick example:
sdat2img.py system.transfer.list system.new.dat system.imgby running this command you will get as output the file my_new_system.img which is the raw ext4 image.
Step 2 - Decompress EXT4 (raw image) -> OUTPUT folder -> Compress EXT4 (raw image)
Now you should either move to Ubuntu x64/x86 or follow the 2nd step from the Ubuntu guide on cygwin 32 bit.
Step 3 - Converting = EXT4 (raw image) -> IMG (sparse image)
Now we need to convert the ext4 raw image into a sparse image. For this you need img2simg binary you can find here (thx to @A.S._id).
The usage is simple:
img2simg.exe <raw_image_file> <sparse_image_file>Pretty self-explanatory, the output will be a new sparse image (.img).
Step 4 - Converting = IMG (sparse image) -> DAT (sparse data)
Now we need the img2sdat binary, the usage is very simple (make sure you have python 2.7+ installed):
img2sdat.py <system_img>- <system_img> = name of input sparse image file (from step 3)
As you can see the output is composed by system.transfer.list, (system.patch.dat) & system.new.dat, ready to be replaced inside your Rom zip.
DOWNLOADs
sdat2img.py
- github.com
make_ext4fs
- mega.co.nz
img2sdat.py
- github.com
Is there any tool to browse (and/or manipulate) these .dat files in Windows?
01 Vlatce said:
Is there any tool to browse (and/or manipulate) these .dat files in Windows?
Click to expand...
Click to collapse
i don't think so, though you can install ubuntu in a virtual machine as 64-bit and decompress there without problems.
edit: windows binaries added to OP.
xpirt said:
i don't think so, though you can install ubuntu in a virtual machine as 64-bit and decompress there without problems.
Click to expand...
Click to collapse
I found one, Ext2Explore, it can browse and extract lollipop .dat files
01 Vlatce said:
I found one, Ext2Explore, it can browse and extract lollipop .dat files
Click to expand...
Click to collapse
Can you explain how to work in more detail ? Thanks.
chihliouma said:
Can you explain how to work in more detail ? Thanks.
Click to expand...
Click to collapse
With that application you can open the system.new.dat file like a zip archive
Sent from my Nexus 5
xpirt said:
i don't think so, though you can install ubuntu in a virtual machine as 64-bit and decompress there without problems.
Click to expand...
Click to collapse
01 Vlatce said:
I found one, Ext2Explore, it can browse and extract lollipop .dat files
Click to expand...
Click to collapse
Confirmed.
Works perfectly..
Thanks a lot! This will save a lot of time theming.. (pulling the system, settings, framework without having to flash the rom first)
Oh, just for s&g's i extracted ("decompiled") the system.new file, the files (app, prive-app, framework, media, etc) all got placed on my desktop -- i deleted the system.new file from the rom -- i then placed the folders and files that got extracted and placed them in the rom -- i flashed it -- it booted! lol.. didnt think it would... but anyways, there's that.
For those who want to try:
--- > its basically self explanatory.
- once downloaded (the link above) extract the contents from the zip (i just went ahead and extracted to my desktop)
- right click the linux penguin
- run as administrator - the window will pop up
- go to file > open image > find your system.new image (should already be extracted from the rom and placed on your desktop)
- click open
- you should now see your image (or path) in the windows -- double click them (i doubled clicked both the right and left side)
- now you should be able to see all the folders
---> if you want to extract those folders
- just go up to the top
- click save and choose an extraction (i chose Desktop)
Hoped i helped -- any questions or confusion, dont be shy to ask -- i probably went too fast, idk lol
Enjoy!
Incredible_Culp said:
Confirmed.
Works perfectly..
Thanks a lot! This will save a lot of time theming.. (pulling the system, settings, framework without having to flash the rom first)
Oh, just for s&g's i extracted ("decompiled") the system.new file, the files (app, prive-app, framework, media, etc) all got placed on my desktop -- i deleted the system.new file from the rom -- i then placed the folders and files that got extracted and placed them in the rom -- i flashed it -- it booted! lol.. didnt think it would... but anyways, there's that.
For those who want to try:
--- > its basically self explanatory.
- once downloaded (the link above) extract the contents from the zip (i just went ahead and extracted to my desktop)
- right click the linux penguin
- run as administrator - the window will pop up
- go to file > open image > find your system.new image (should already be extracted from the rom and placed on your desktop)
- click open
- you should now see your image (or path) in the windows -- double click them (i doubled clicked both the right and left side)
- now you should be able to see all the folders
---> if you want to extract those folders
- just go up to the top
- click save and choose an extraction (i chose Desktop)
Hoped i helped -- any questions or confusion, dont be shy to ask -- i probably went too fast, idk lol
Enjoy!
Click to expand...
Click to collapse
I can't get this to work at all. I'm using Win 7 Pro and I've actually used this app before with stock Nexus 7 factory images and it worked fine.. What file did you actually download? I d/l 2 different versions, one was beta 2.0 and the other was a zip that said 2.2.71 but the about on the exe says 2.1, which is the version I've been using for quite a while.
With the beta 2.0, there's not even an option to open a file and with the 2.1, it errors out every time. After opening system.new.dat image and double clicking, it just hangs and the program stops responding. If I try clicking on it and selecting save, it allows me to select a folder to save it in but I just get a dialog box that says saving files and then hangs at 24% every time, finally crashing with a Microsoft C++ runtime error.
Oh btw, you didn't go too fast LOL, this is really a simple app to use but it's just not working for me with these block image files. Maybe I'm missing something but it's got me scratching my head. :laugh: If you have any ideas, I'm all ears.
Thanks,
Mike T
webdroidmt said:
I can't get this to work at all. I'm using Win 7 Pro and I've actually used this app before with stock Nexus 7 factory images and it worked fine.. What file did you actually download? I d/l 2 different versions, one was beta 2.0 and the other was a zip that said 2.2.71 but the about on the exe says 2.1, which is the version I've been using for quite a while.
With the beta 2.0, there's not even an option to open a file and with the 2.1, it errors out every time. After opening system.new.dat image and double clicking, it just hangs and the program stops responding. If I try clicking on it and selecting save, it allows me to select a folder to save it in but I just get a dialog box that says saving files and then hangs at 24% every time, finally crashing with a Microsoft C++ runtime error.
Oh btw, you didn't go too fast LOL, this is really a simple app to use but it's just not working for me with these block image files. Maybe I'm missing something but it's got me scratching my head. :laugh: If you have any ideas, I'm all ears.
Thanks,
Mike T
Click to expand...
Click to collapse
hmm interesting..
im using windows 8.1
idk how much help i can be because i just downloded the first option (provided by the link above) and went from there.
like you said, theres two.. the .exe and the .zip.. i downloaded the .exe
Incredible_Culp said:
hmm interesting..
im using windows 8.1
idk how much help i can be because i just downloded the first option (provided by the link above) and went from there.
like you said, theres two.. the .exe and the .zip.. i downloaded the .exe
Click to expand...
Click to collapse
So, did you d/l the zip that was modified 2006-8-26, which is version 2.0 beta, or did you click the link which said download latest release?
Mike T
webdroidmt said:
So, did you d/l the zip that was modified 2006-8-26, which is version 2.0 beta, or did you click the link which said download latest release?
Mike T
Click to expand...
Click to collapse
ha! didnt even see there was a latest release..
i downloaded the 2006-8-26 apparently -- didnt even look at that date either LOL
i dont want to try the latest now -- this one works fine for me lmao -- dont want to ruin it.. ah, screw it, im downloading the latest now
EDIT: Ok, i lied.. i just checked my trash.. i did download the lastest release .zip .. the 2271..
@webdroidmt @Incredible_Culp Download from here lol: http://sourceforge.net/projects/ext2read/
Maybe something with my PC setup or Win 7 because the 2006-8-26 version doesn't even give me an option for opening a file image. It actually loads up looking like an incomplete application, it's also a very small filesize. Did you just d/l the ext2explore exe, or did you also d/l ext2read2 beta zip?
Mike T
webdroidmt said:
Maybe something with my PC setup or Win 7 because the 2006-8-26 version doesn't even give me an option for opening a file image. It actually loads up looking like an incomplete application, it's also a very small filesize. Did you just d/l the ext2explore exe, or did you also d/l ext2read2 beta zip?
Mike T
Click to expand...
Click to collapse
Use the download link in the above post and click the green download button, and it should be the correct version, from 2012 rather than 2006.
Lethargy said:
@webdroidmt @Incredible_Culp Download from here lol: http://sourceforge.net/projects/ext2read/
Click to expand...
Click to collapse
That's the one I've been using for quite some time. As mentioned in my previous post, the system.new.dat file just "appears" to be saving but hangs at 24%, then eventually crashes. I'm stumped, should be so easy but it doesn't want to cooperate. LOL
Thanks anyway,
Mike T
webdroidmt said:
That's the one I've been using for quite some time. As mentioned in my previous post, the system.new.dat files just "appear" to be saving but hangs at 24%, then eventually crashes. I'm stumped, should be so easy but it doesn't want to cooperate. LOL
Thanks anyway,
Mike T
Click to expand...
Click to collapse
Weird. Try redownloading the ROM you're trying to extract?
Lethargy said:
Use the download link in the above post and click the green download button, and it should be the correct version, from 2012 rather than 2006.
Click to expand...
Click to collapse
Thanks for trying guys, that is exactly the one I've been using. I downloaded it again a few seconds ago and still getting the same result. :laugh:
Thanks.
Mike T
---------- Post added at 01:09 AM ---------- Previous post was at 01:08 AM ----------
Lethargy said:
Weird. Try redownloading the ROM you're trying to extract?
Click to expand...
Click to collapse
I've actually tried with images from 3 different roms and they all give me the same result. It's cool, I just won't be able to play around as much as I used to porting stuff.
Mike T
---------- Post added at 01:15 AM ---------- Previous post was at 01:09 AM ----------
Lethargy said:
Weird. Try redownloading the ROM you're trying to extract?
Click to expand...
Click to collapse
Just curious, you guys aren't changing the file extension to something other than .dat, right?
Mike T
I ran into this today after wiping my "internal storage" in TWRP (oops).
This guide assumes you have bricked the Nexus 5 with an unlocked bootloader and root'd device
**Download before starting**
- Latest TWRP: http://teamw.in/project/twrp2/205
- Latest Hammerhead stock images: https://developers.google.com/android/nexus/images#hammerhead
- One Click TWRP Recovery Toolkit: http://www.androidrootz.com/2013/11/nexus-5-one-click-toolkit-for-mac.html
- Latest SuperSU (GA or beta): http://forum.xda-developers.com/showthread.php?t=1538053
**Recover Stock OS**
- Extract the Hammerhead stock images .tgz archive contents on your mac
- Ensure you have copies of "fastboot" and "adb" and place them in the same folder (optional but easier)
- Edit "flash-all.sh" script with complete path to "fastboot", or simply "./fastboot". An example:
/Users/james/Downloads/hammerhead-lrx22c/fastboot
- Boot the device in Fastboot Mode (volume up + down and power)
- Use the USB Cable to connect the Nexus 5 to your PC.
- Open "Terminal" > change directory to correct folder > Execute "flash-all.sh"
- Wait for the installation process to complete
- Reboot once you can, and go back into fastboot
**Reflash recovery (stock images rewrite recovery)**
- Extract "TWRP.RecoveryNexus5.zip" into a folder
- Place downloaded TWRP .img into the same folder (i.e "openrecovery-twrp-2.8.3.0-hammerhead.img")
- Edit "TWRP.Recovery.Nexus5" file > line 36 > change to above .img. An example:
./fastboot flash recovery openrecovery-twrp-2.8.3.0-hammerhead.img
- Open "Terminal" > change directory to the correct folder > Execute "TWRP.Recovery.Nexus5", or just open it in finder (like any app)
- Follow instructions in cmd window
Once completed you can let your phone boot normally (i.e, reboot into system).
Now you can mount the file system and place ROM files via USB again.... then boot into recovery and flash whatever you need... Remember to flash SuperSU!
Good Resources:
- http://forum.xda-developers.com/goo...olkit-root-twrp-recovery-unroot-11-6-t2515640
- http://www.android.gs/how-to-unbrick-google-nexus-5/
Thanks to @techfanatic9 for creating the toolkits!
(Sorry for english !!)
!! Some problems with Android 5.1.x installed on External.
[Dual-Boot] I9305 [SCRIPT]
Hi. Because i dont find any kernel/script for I9305 with Dual-Boot, i try to make this script for test roms (but can be use day by day without problem).
This script help to patch .zip rom/kernel/gapps (and other i think) for install him on SDCARD. (without touch your internal rom).
How can you do this? Need to repartition your sdcard in 3 parts
1. With your sdcard data (files/music..etc)
2. external System (for system rom)
3. external Data (for data rom)
What you need to know !!!!
- Thanks on @Nicene Nerd for this App. I'm inspired from him.
- I'm not a developer.
- I don't now so much about linux (so, script not have a best optimization)
- This script is better good for people who test roms (like Lollipop).
- If you dont try this script, don't say anything. (only if you have some problem/stucks)
- Install on Internal roms like: Amcha / N4 / ..etc (big roms)..because i try to install on external rom and dosen't work
- Rom like Nameless / RR / ..etc can be install on external
- Anyone who want help me to make this script better, say here where need to edit (with what) and who can code help
- Say here what rom/kernel/script work or dosen't work to install on external. For modify script
What you need.
MiniTool Partition Wizard (or other program to repartition sdcard)
USB Cable (for repartition)
A phone (i9305 of course)
SDCARD 16gb (or more) Class 10 (if you have class 4 or other..your external rom run slow)
Backup your sdcard data (for safe)
Backup your phone (for safe)
ROM with root permision.
Water (because is good for your health)
First time you need to repartition sdcard
First partition: FAT32 (split memory from this..is good option)
Second: 1600 mb (1,6 gb) for system
Third: 2500 mb (2,5 gb) minimum memory for data
How can do this:
On MiniTool show your sdcard (like this)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1. Right click on him > Split
2. On New Partition Size you need to have minimum (system + data) 1600 + 2500 = 3600 mb (3,6 gb)..If you want more memory on data, you can type more than 3600 mb (i need more so i split 7000 mb)
After write your value, press ok
Now look like this
3. Right click on new partition (H on me) > Delete
Now you have unallocated partition
4. Right click on unallocated partiton > Create > Ok (on warning)
5. On box you need to edit:
Create As: Primary
File System: Ext4
Partition Size: 1600 (because is system partition)
After this. Press Ok
6. Right click on unallocated partition > Create > Ok (on warning)
Create As: Primary
File System: Ext4
Partition Size: dont modify
After this. Press Ok
7. Before press Apply, check if look like this
Now you can press Apply and wait
Good
After sdcard was partitioned, go to next step
Put my script on your SDCARD
(Why in sdcard? because internal/external rom view the sdcard everytime)
(internal/external rom have separated 'internal memory')
1. Unrar on desktop (right click on archive > extract here)
2. Copy 'db' folder to your sdcard
3. Check if 'db' folder is on your sdcard
4. With file explorer (i use Root Browser), go to db folder and install 'terminal.apk'
5. After install run him
On terminal:
Type: su (for superuser permision)
Type: cd /mnt/extSdCard/db (or anywhere is db folder location..on LolliPop is: cd extSdCard/db)
Type: sh db.sh
Now you are in script menu
Option: 1 -> Save Internal BOOT.IMG
Option: 2 -> Flash Internal BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 3 -> Mount Internal partitions on root direcotry (/.dbSystem & /.dbData)
Option: 4 -> Clean Internal partitions (use this if you are in External rom)
Option: 5 -> Save External BOOT.IMG
Option: 6 -> Flash External BOOT.IMG and Reboot phone (if not reboot, try to reboot manualy)
Option: 7 -> Mount External partitions on root direcotry (/.dbSystem & /.dbData)
Option: 8 -> Clean External partitions (use this if you are in Internal rom)
Option: 9 -> Patch file for External rom (file like rom/gapps/pa-gapps/kernel..etc)
Option: 0 -> uMount /.dbSystem & /.dbData
Option: fb -> Flash manualy BOOT.IMG file
Option: ie/ei (hidden command) -> I'm work on this.. Is a experimental function. Don't use it
Patch files for external rom:
1. Copy on 'db' folder rom who want to patch, gapps archive and kernel your need
2. Run script on terminal
3. Need to save your Internal boot.img (Option 1 on menu)
4. Option 8 to clean your external partitions (if was used before with other rom).
5. Option 9 to patch
6. Type rom/gapps/kernel..etc archive name like: my_rom.zip > And press enter
7. Wait to patch (all patched files have pre name ext-
NOTE: If you patch rom/kernel (with boot files), you need to watch if script modify any fstab file. If no, external rom not work!
8. After you patch all you archive need..go to recovery (i use TWRP 2.8.5.0) and flash him but need to kep order:
- First ROM zip
- Second GAPPS (or PA-GAPPS) (or without this)
- Third KERNEL (if is need)
- .. other patched scripts
9. After flashing, reboot and wait to new external rom start up
(if you have any error (boot loop/other) you can flash internal boot stored in "sdcard/db/.db/.imgs/boot-int.zip")
10. After your external rom is ON, install 'terminal.apk' from sdcard
11. Run script on terminal
12. Save your External BOOT.IMG (Option 5)
13. Enjoy with your external rom.
(To switch rom you have option 2 and 6 or flash manualy .zip stored in "sdcard/db/.db/.imgs/boot-*.zip")
I forgot something?
Another explain: http://forum.xda-developers.com/showpost.php?p=59570171&postcount=11
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
Version 1.0:
+ It's alive !
thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?
LeoDeos said:
thanks fro this script, but i have a question:
if I understand how it works, every time I have to save the rom I'm using...it creates a backup of rom in flashable zip format.
to switch from one to another rom I have to flash the zip saved...so what is the difference with a nand backup/restore?
and what are the performance and the lag of a rom thst run on sd card?
Click to expand...
Click to collapse
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion
il3gal said:
Script was patched a .zip file for install on External partitions (system/data).
And modify boot.img (mounts).
Difference on nand backup/restore and this is time and to swich internal to external is much faster. (only flash boot.img for swich)
I make a Benchmark and score is 30k with Nameless (0303 version).. When you copy some file in sdcard (with usb) or you install a apk file (depend so much what sdcard you have).. have some lags..but if i use day by day i dont have lag.
I dont now if i explain so good how script works because i dont now so much english..
Look at uploaded image. How much time need to change rom from ..3 minutes..all i need is to flash boot.img (for internal/external) and reboot..
This is a good option in my opinion
Click to expand...
Click to collapse
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?
LeoDeos said:
ok understand...
but i'm not still sure of utility of the external boot.
foe example: i can flash stock rom on internal and save boot.img...
after i flash aosp rom always on internal and save boot.img with another name.
in this case the time to switch one to another rom is the same 3 minutes.
i wrong?
Click to expand...
Click to collapse
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?
il3gal said:
hmm..but system files and data files where is? same in internal? You cant..
You need other partitions for system / data if you want another rom
For internal partition mount points is mmcblk0p13 (system) and mmcblk0p16 (data)
For external is mmcblk1p2 (system) and mmcblk1p3 (data)
Hm..understand?
Click to expand...
Click to collapse
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?
LeoDeos said:
maybe i explain wrong.
so i try to repeat well.
1) flash stock rom on internal.
2) backup stock rom (option 1 of your script)
3) full wipe and flash aosp rom always on internal.
4) backup aosp rom (always with option 1 of your script)
(if i'm not wrong we will have 2 backup zip file)
5) switch rom (option 2 of your script)
its possible?
Click to expand...
Click to collapse
aaaaaa...no..
il3gal said:
aaaaaa...no..
Click to expand...
Click to collapse
ok thanks
LeoDeos said:
ok thanks
Click to expand...
Click to collapse
I make now how i use this script ..with images..
Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.
Explain 2
I made a tutorial how i use this script. Skip the repartition step because is easy (repartition need to make one time..not everytime want you install external rom)
On my rom (N4 Elite Lite v5).
1. Copy what files need to patch in db directory (where is script). In my case (pa_gapps-modular-pico-5.0.1-20150221-signed.zip & nameless-5.0.2-20150318-i9305.zip)
2. Run script.
3. First time need to save your internal boot.img (kernel). (for swich roms)
(because script modify kernel (mount point on kernel) and when you swich rom, all who make script is to flash kernel for internal/external rom)
4. After you save internal kernel, go back to menu and type option 9 to patch zip rom/gapps/kernel..etc
(if rom have a included kernel, watch if script find a fstab.* file and if can be edited. If not edited, external rom not work)
(all rom/kernel/gapps..other script need to modify updater-script or update-binary (pa-gapps use this)..if not edited, you cannot install rom on external partitions
5. After i patch rom file, i need and gapps because i use Google Play Store, so, i patch and gapps (go in menu, option 9 and type gapps file name)
(Now my db directory look like this)
6. All good. Now i want to be sure about my external partitions is clean, and i go to option 8 to clean him
7. After clean, reboot in recovery and flash ROM (ext-nameless-5.0.2-20150318-i9305.zip) and after GAPPS (ext-pa_gapps-modular-pico-5.0.1-20150221-signed.zip)
8. Reboot phone and wait to rom boot complete..(first boot may during a time)
(At Total Memory, is total memory allocated on 'data' partition (from repartition) (third partition))
9. After boot is complete..install 'terminal.apk' from db folder (script folder)
10. Run script from terminal.
11. Option 5 (for save this external boot.img)
12. Voila..now i have 2 separated roms..installed in 2 separate partitions (internal system/data and external system/data)
To swich i have 2 option. From terminal (script). (example) If i'm in internal rom and i want to swich, open script an type option 6..For flash external kernel and reboot phone to boot in external rom.
From recovery: flash manualy .zip files stored in sdcard/db/.db/.imgs/boot-*.zip
Now is good explication?
djb77 said:
Not meaning to rain on the parade here but it basically seems to be similar to just backing up and restoring like nand. It may not be exactly the same but it seems to be a similar thing.
Unfortunately it looks like it can't perform a proper dual boot.
Click to expand...
Click to collapse
Is not same. Do you know dual windows on pc?
Partiton C have Windows 7 (example)
and partition D have Windows 8.1 (for example)
If you boot pc, have a question "Who windows want to boot" 7 or 8.1..and you choose.
My script is same, but for 'choose', need to flash a kernel (external/internal..depend what you want to boot)
hmm.
This script is same with http://forum.xda-developers.com/showthread.php?t=2639112 ...but is not app..and dont have some options like "backup"..
Tested with:
ROM
- AICP 8.0
- Resurrection Remix® LP
- NamelessROM
- Cyanogenmod 12
- SlimLP
KERNEL
- Boeffla 3.0-alpha9
Changelog
Version 1.1:
+ Some bug fixes
+ Mkdir folder check after create
I see some people was download script. Can give me feedback? (db_1.0.rar - [Click for QR Code] (1.11 MB, 32 views))
What rom is work and what not? (i dont have time to test all roms)
Abandoned.
il3gal said:
Abandoned.
Click to expand...
Click to collapse
why?
LeoDeos said:
why?
Click to expand...
Click to collapse
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this
il3gal said:
Because i dont have feedback..
I continue use this but i dont post update..
32 downloads / 0 feedback..
I think people don't understand how it works ..hm
I'm bad to explain this
Click to expand...
Click to collapse
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method
LeoDeos said:
i think you should leave the download link.
it could help for someone.
when i'll time and an sd card bigger i want try your method
Click to expand...
Click to collapse
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.
il3gal said:
ok. i remove and [abandoned] .
just wait. now i try to add some things on script.
Click to expand...
Click to collapse
thanks
+Tested with:
ROM
- AICP 9.0 (test version)
Changelog
Version 1.2:
+ Some bug fixes (major bug fixes)
+ Add rsync for Duplicate Partition (ie/ei command. hidden command because not work now
+ Patch init. files from kernel (work with pureSTOCK / pureCM kernel) (i'm not tested, but you can flash now a big rom (like Amcha/N4 Lite) in external rom)
+Tested with:
ROM
- N4 Elite Lite v7 (but i don't now how much fast is) (when i have time, i will tested)
Changelog
Version 1.3:
+ Removed experimental (duplicate partitions)
+ Removed rsync
+ Add check "Where i am now" for check what system mounted (internal/external) for optimized script
+ On start, check if rom/kernel changed and you can save new rom much easy
+ Disabled some options from menu (depend where are you (internal/external) rom)
+ On mount/ckeab internal/external partitions, now check if is mounted property
+ Terminal updated at last version
Who know a universal reboot command for any rom? Because reboot not work on N4 Elite Lite rom
This tool has been heavily modified for the zte max pro, it was originally posted as the axon 7 tool. Not all features have been included as not all work as of yet for the pro.
ZTE Zmax Pro EDL Tool
BAT-program for Flash / Backup / Restore / Unlock the phone in EDL mode
Qualcomm HS-USB QDLoader 9008 (COM ...)
!!! Whatever you do, you do at your own risk !!!"
!!! If you are not sure of yourself do not use this program !!!
Special requirements (read first) !!!
1. The program must be unpacked
2. Before using the program, make sure that:
- It is desirable to copy the program to the root of the disc, for example: C:\ZTE_Zmax_Pro_edl\ or D:\ZTE_Zmax_Pro_edl
- You launched this program as administrator
- You have drivers installed, preferably original for ZTE Zmax Pro
3. Read carefully what the program displays on the screen (I specially wrote the tips, the information is very useful, many questions disappear)
Features of the program:
1. Automatically reboot the phone into EDL mode
2. Finds the connected phone and forces the COM-port speed to 115200
3. Can flash , backup, restore
4. Analyzes folders for missing required files
5. and others ...)))
Structure of program folders:
1. Folder flash - in this folder you need to copy the files you want to flash
Subfolders:
folder full - if you want to flash full firmware (official, adapted for EDL mode), then in this folder you need to put all the files from the firmware for EDL mode:
its name usually looks like this: A2017 _......._ FULL_EDL
folder boot - if you want to flash your kernel file, you need to put a file named: boot.img in this folder (the file name must be exactly that!)
folder recovery - if you want to flash your recovery file, you need to put a file named: recovery.img in this folder (the file name must be exactly that!)
folder modem - if you want to flash your modem file, you need to put a file named: NON-HLOS.bin in this folder (the file name must be exactly that!)
folder splash - if you want to flash your splash file, you need to put a file named: splash.img in this folder (the file name must be exactly that!)
2. Folder backup - the folder contains backup copies of the phone partitions created by the program
Subfolders:
folder all - this folder contains backups of all partitions, except userdata
folder full - this folder contains backup of all partitions included in the FULL EDL firmware
folder boot - this folder contains a backup of the boot partition
folder recovery - this folder contains a backup of the recovery partition
folder modem - this folder contains a backup of the modem partition
folder splash - this folder contains a backup of the splash partition
folder efs - this folder contains backup of the efs partition
3. Folder unlock - contains all the necessary files to unlock (do not touch it!)
4. Folder logs - contains all the logs of the program
5. Folder tools - contains all the necessary files for the program (do not touch it!)
For those who still do not understand how to flash (FAQ):
Question: I want to flash a patched or original boot, how to do this ???
Answer: Download the boot you need, rename it to boot.img and place it in the folder ZTE_Zmax_Pro_edl\flash\boot\. Run the program ZTE_Zmax_Pro_edl.bat and select Flash -> Flash Boot
Question: I want to flash TWRP, how to do this ??? !!! Only for those who unlocked the bootloader !!!
Answer: Download official TWRP or TWRP by @NFound, rename it to recovery.img and place it in the folder ZTE_Zmax_Pro_edl\flash\recovery\. Run the program ZTE_Zmax_Pro_edl.bat and select Flash -> Flash Recovery
Question: I want to flash the modem, how to do this ???
Answer: Download or take the NON-HLOS.bin file from firmware and put it in the folder ZTE_Zmax_Pro_edl\flash\modem\. Run the program ZTE_Zmax_Pro_edl.bat and select Flash -> Flash Modem
Question: I want to flash the splash, how to do this ???
Answer: Download or take the splash.img file from firmware and put it in the folder ZTE_Zmax_Pro_edl\flash\splash\. Run the program ZTE_Zmax_Pro_edl.bat and select Flash -> Flash Splash
!!! Download !!!
View attachment ZTE_Zmax_Pro_edl.zip
Hi loonycgb2. I have a question. I want flash a full firmware but there in not the optionin the app. Can you help me?
How do you unlock the bootloader on z981?
How do you unlock the bootloader on z981?
fastboot oem unlock command does not work.
the efs backup feature throws an error where it cannot find persist.bin. it also cant restore the backup for the same reason. all done according to instructions