Database Users

Unable to flash custom bootscreen

Hi I downloaded this android peeing on Apple logo bootscreen, it installed well so I got too excited and wanted to put tux hammering the Windows logo before android pee on the Apple, I made all 70 png's but did not touch anything either than creating the images. I then zipped them according to the original names but when I flash it I get ..... E: wrong digest, system/media/bootanimation.zip
I have tried several times but no luck, yet the original one would easy install. Help guys
Sent from my HTC Hero VillainRom 12, flykernel11 using XDA App

any idea someone

You probably need to sign the update zip, possibly change the install/flash location. Upload what you have in a zip and I'll make one for ya
Edit: and explain what I did

kyouko said:
You probably need to sign the update zip, possibly change the install/flash location. Upload what you have in a zip and I'll make one for ya
Edit: and explain what I did
Click to expand...
Click to collapse
Too bad everyone doesn't do that.

I have decided to change the part1 folder images with custom ones, I will upload the whole zip later so when you help me I won't have to re edit it again, thanx for your replies

Apologies as this is long overdue. Finally had some free time this weekend
Attached are both the working bootscreen AND the original for those who want to see what was changed between the two.
Edit: added the non-signed bootscreen.zip for reference as well. Never know who may want to look at it.
Setup
Extracted the zip (original_doesntflash.zip) into its own directory
Created the META-INF folder
Deleted the CERT.RSA, CERT.SF, and MANIFEST.MF files
Created the "com" folder inside META-INF
Inside the "com" folder I created another folder named "google"
Inside "google" create a folder named "android" <- forgot about this step
Inside there I placed the "update-script" (if you want to know how to make one of these by hand refer to my post HERE)
Added both folders (META-INF and system) to a zip - in this case named it "bootscreen.zip"
Signing The Zip
I'm running linux currently so I do it slightly different, but I'm assuming the majority of you guys and gals are windows users. If that's the case follow these directions:
Go HERE and download AvaboxV2
Extract the AvaboxV2.zip where you want it. Personally I'd made a separate AvaboxV2 folder in my AndroidSDK dir. But the desktop still will work
Copy the newly created zip (bootscreen.zip) into the "Auto-Sign" folder found in AvaboxV2
As per the README.txt:
Start a cmd prompt AS ADMINISTRATOR (not really needed if running Win7)
cd <to the directory of the Auto-Sign folder> [Example: cd C:\AndroidSDK\AvaboxV2\Auto-sign]
java -jar signapk.jar testkey.x509.pem testkey.pk8 bootscreen.zip bootscreen_signed.zip <- same command as used in linux, at least for me
Press enter...wait...wait...done
Congratulations you now have a working/flashable bootscreen zip

thanks mate I will download it today, thanks for the tutorial man its highly appreciative, thanks a lot

kyouko said:
Apologies as this is long overdue. Finally had some free time this weekend
Attached are both the working bootscreen AND the original for those who want to see what was changed between the two.
Edit: added the non-signed bootscreen.zip for reference as well. Never know who may want to look at it.
Setup
Extracted the zip (original_doesntflash.zip) into its own directory
Created the META-INF folder
Deleted the CERT.RSA, CERT.SF, and MANIFEST.MF files
Created the "com" folder inside META-INF
Inside the "com" folder I created another folder named "google"
Inside there I placed the "update-script" (if you want to know how to make one of these by hand refer to my post HERE)
Added both folders (META-INF and system) to a zip - in this case named it "bootscreen.zip"
Signing The Zip
I'm running linux currently so I do it slightly different, but I'm assuming the majority of you guys and gals are windows users. If that's the case follow these directions:
Go HERE and download AvaboxV2
Extract the AvaboxV2.zip where you want it. Personally I'd made a separate AvaboxV2 folder in my AndroidSDK dir. But the desktop still will work
Copy the newly created zip (bootscreen.zip) into the "Auto-Sign" folder found in AvaboxV2
As per the README.txt:
Start a cmd prompt AS ADMINISTRATOR (not really needed if running Win7)
cd <to the directory of the Auto-Sign folder> [Example: cd C:\AndroidSDK\AvaboxV2\Auto-sign]
java -jar signapk.jar testkey.x509.pem testkey.pk8 bootscreen.zip bootscreen_signed.zip <- same command as used in linux, at least for me
Press enter...wait...wait...done
Congratulations you now have a working/flashable bootscreen zip
Click to expand...
Click to collapse
I got an error when flashing the signed zip I got no update file found

elliotn said:
I got an error when flashing the signed zip I got no update file found
Click to expand...
Click to collapse
LOL uhh, I'll take a look at it and test it out... and edit my previous post with w/e I did wrong
Forgot to add the ''android'' folder in the zip. Fixed and should work now

[GUIDE] Extract files from Nandroid backups

I have seen this asked a few times recently so I figured I would try to put together a quick and easy guide to extracting files from Nandroid backups. This guide only covers Windows, I assume if you are running Linux you can download unyaffs and compile/run it without my assistance. If you are adventurous you can install cygwin and compile unyaffs on your own (or download it at any number of sites across the internet), however I have included all the files needed to extract the files from the img files.
1. Download unyaffs along with the cygwin1.dll
2. Extract the files to a new folder.
3. Copy the system.img file from the ROM or your Nandroid backup to the folder you extracted unyaffs.exe and cygwin1.dll to.
4. Open a command prompt and cd to the folder containing the three files. If you are on Windows 7 you can just navigate there with Windows Explorer and in the URL bar type cmd to open a comman prompt in that location.
5. Type unyaffs system.img
You have now extracted all the files from the system partition of your Nandroid backup. The APKs are in the /app folder and some apps require library files that can be found in the /lib folder. For example: Swype.apk requires that libSwypeCore.so be in the lib folder for it to work properly.

I get an "end of image" message and no folder is created with the extracted files.
I am trying to recover some photos from my Gallery, which I presume is in data.img - but no matter what I try to extract, I get "end of image"
any ideas?

Is the system.img the only thing you can open with this or can you open the data.img or the wimax.img also?

Lock-N-Load said:
I get an "end of image" message and no folder is created with the extracted files.
I am trying to recover some photos from my Gallery, which I presume is in data.img - but no matter what I try to extract, I get "end of image"
any ideas?
Click to expand...
Click to collapse
Your photos should be on your MicroSD card, not on one of the system partitions. Look in SDCARD:\DCIM\100ANDRO, your photos should be there.

cruise350 said:
Is the system.img the only thing you can open with this or can you open the data.img or the wimax.img also?
Click to expand...
Click to collapse
I want to know this also

Seems to work ok for me for data.img and system.img, but not wimax.img or boot.img.

Yep, I tried that too...worked.

Is there a command to repack the system or data image after you have unpacked and played around with them???
I am pretty sure that my issue is within the data file...I removed what I think caused the problem but how do I repack it all to put it on the sd card and try it out?
thanks

Does anyone know a command to repack the files???

Worked for me.
Pretty much my whole family has Evo's. theyre all rooted too thanks to me but in my experimenting, i lost the 4G keys to mines. so i troubleshooted. i put Amen Ra's recovery on my brothers phone, and nandroid'ed only the wimax. put the entire folder for that backup on my sdcard on the spot where u would find ur backups, ran Amen Ra on my Evo. and bam. working 4G. u just cant use them at the sametime cuz it interfears.

Oh ok cool.
Is there anyway to pack the files on windows
I want to see if my phone will boot now that I got rid of some programs I believe to be causing it to bootloop

Stupid question. Don't mind me.

Awesome this works Thanks allot

how can I extract /data/system to then package back as either
* SBF
or
* update.zip
to write to another identical phone?
re
http://forum.xda-developers.com/showthread.php?p=17217163#post17217163
ubuntu fyi

I've extracted *.smg files from a SBF Rom File. I'm willing to extract Stock Apk's from it.
Now, my Unyaffs is in the same folder of the SMG files such as cygwin1.dll, however when i try to execute "unyaffs cg39.smg" I receive the following:
8 [main] unyaffs 5960 handle_exceptions: Exception: STATUS_ACCESS_VIOLATIO
N
2790 [main] unyaffs 5960 open_stackdumpfile: Dumping stack trace to unyaffs.e
xe.stackdump
the log says:
Exception: STATUS_ACCESS_VIOLATION at eip=004010B0
eax=444E1A20 ebx=0000001A ecx=FFFFFFE4 edx=00801322 esi=0040130E edi=610E21A0
ebp=0022EE88 esp=0022EE50 program=C:\Motorola\unaffys\teste-extracted\unyaffs.exe, pid 4708, thread main
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame Function Args
0022EE88 004010B0 (0022EEE9, 00000000, 00000000, 00401333)
0022EEB8 004013AF (00000002, 00800180, 00800090, 610A5E22)
0022EFA8 61004DD2 (0022EFC0, FFFFFFFF, 77A651CE, 00000000)
0022FF58 6100594F (00000000, 00000000, 00000000, 00000000)
End of stack trace
I've tried to regsrv32 the DLL and also receveid error as a invalid Dll. Does anyone have an idea?
I'm looking for stock Phone, Contacts and the keyboard apk, by the way, anyone knows the keyboard apk file?
thanks

Thanks
Sent from my PC36100 using Tapatalk 2

hi guys,exist a new link for this tool or another tool for open .img files?
thanks in advance

Efs backup -- important !!!!

For those of you that don't think you need to read this - you are wrong! I have flashed 100's of ROM's with no issue until the end of last week.
MODERATORS PLEASE STICKY THIS IN A PLACE WHERE EVERYDAY USERS THAT FLASH ROMS WILL SEE IT
I uneventfully flashed a ROM (not important which one because I don't think it has anything to do with particular ROM) and all went well. I went to bed with a working phone and the somehow a reboot happened and awoke with a phone with no signal. The error was saying that there was no SIM card and / or No Network Available.
I finally used HC-kTool app on the Market (used latest version) to Restore an efs.tar file and my phone started working but I had a generic / fake IMEI number -- 004999010640000
If you have backed up your /EFS folder on the root of your phone then all is well. The easiest way is to use Hellcat's HC-kTool to back up your EFS and save a copy on your sdcard and your PC and that way you will not have to go through my misery.
However if you have not BACKED UP your EFS files then you will have issues like I did
Ok so here is what I can tell based on my experience:
Look for any files or folders on your sdcard that have EFS in the name. You might get lucky and look in the /EFS folder on your phone. If the nv_data.bin file has been corrupted the .nv_data.bin.bak might still be OK. If that is the case you may be able to follow this guide: http://forum.gsmhosting.com/vbb/f606/samsung-android-repair-efs-imei-repair-without-box-1348192/
What won't work is any sort of simple copying nv_data.bin from the sdcard to the /EFS folder using Root Explorer - I spent almost an entire weekend trying this.
If your /EFS folder .bak file has been corrupted then in my case I found a folder on my sdcard named EFS_BACKUP that I assume that Clockworkmod has created during some of my ROM flashes (somebody correct me if I'm wrong because otherwise I have no idea how it got there).
In the EFS_BACKUP folder I have a number of files form different dates (I assume of flashes) labelled efs_xxdate.tar.gz
btw you can use these or any .gz file when using HC_kTool tool simply by renaming the file (long press with Root Explorer) to just a .tar file (delete the .gz). HC_kTool uses a file named efs.tar on the root of the sdcard to restore.
In my case I had to extract one of these files by long pressing in Root Explorer and choicing extract. I then went to the extracted folder on the sdcard (using Root Explorer) and found a folder named efs_xxdate and within that a folder named EFS
... again don't get mislead -- simply copying and pasting that file or any other to the root /EFS folder will not work!!
I noticed that there were multiple files in the extracted/efs_xxdate/efs folder but the dates were different. The nv_data.bin and the nv_dat.bin.md5 files were dated the same as the date of the folder BUT the .nv_data.bak file was dated Dec31, 2010
Here's how I restored that file:
1) I extracted the .tar.gz file as above
2) Went to sdcard\extracted\efsxxdate\efs folder and copied the older dated .nv_data.bak to the root of the sdcard using Root Explorer (long press, copy, then paste)
3) Then renamed the .nv_data.bak file to nv_data.bin on the root of the sdcard
3) Then followed these instructions from line 14 on in this post .. http://forum.gsmhosting.com/vbb/f606/samsung-android-repair-efs-imei-repair-without-box-1348192/
14 = at command prompt [ C:\adbtools\ ], type adb shell
15 = type su
16 = type cp /sdcard/nv_data.bin
17 = type rm -rf /efs/nv_data.bin.md5
18 = type exit & exit
19 = REBOOT YOUR PHONE
I'm not sure why this works but EVERY combination of copying and pasting nv_data.bin , .bak, or entire EFS folders suing Root Explorer does NOT work but this above technique did work for me ! Somehow having the .md5 file recreated is the key ??
I hope this helps someone.
BACKUP YOUR EFS -- Hellcat's HC_kTool seems to work great
Thank the DEVELOPERS

Already been highlighted a few times
http://forum.xda-developers.com/showthread.php?t=1068193&highlight=efs

Can you please clarify....I always keep a weekly copy of clock work mod backed up. Is this not enough? A lille confused about the need for efs backup...
Sent from my SGS2

Thx for this post. Anyway, i got stuck at 17, it says "-rf: not found". What does that mean? Am i unable to mount efs?

Nice post. Not happened to me *yet* but you never know.
Here is the direct link to Hellcats K-tool
Backing mine up now

jcrompton said:
However if you have not BACKED UP your EFS files then you will have issues like I did
Click to expand...
Click to collapse
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..

s2d4 said:
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
Click to expand...
Click to collapse
Actually i don't understand how he made it: ktool doesn't use a tar file like posted, but an img file, and you can only find tar.gz files in the backup folder. How do you get an img file out of those?

s2d4 said:
someone move it to general please..
Click to expand...
Click to collapse
Sorted
Used K-Tool since the method mentioned via terminal never worked..

stylez said:
Sorted
Used K-Tool since the method mentioned via terminal never worked..
Click to expand...
Click to collapse
Good for you
But what did you do exactly? How did you obtain the img file for ktool to flash it? I only have the tar backups from the Efs_ backup folder...

s2d4 said:
You had the EFS image file already, all you had to do was rename the file then use ktool and you were done within seconds..
You probably could've done it via pm as I don't think it was a good idea to try any suggestion that was thrown at you in public forum...
btw, this is original development section.. someone move it to general please..
Click to expand...
Click to collapse
I did not have a new efs image file
All the files I had had been corrupted
I spent four days PMing all the big wigs re this. It's not as simple as you think unless you familiarize yourself with EFS backup BEFORE you need it!
Clockwork mod and nandroid backups do not alter the efs folder when a backup is restored! It must be backed up separately
Sent from my GT-I9100 using xda premium

vnvman said:
Good for you
But what did you do exactly? How did you obtain the img file for ktool to flash it? I only have the tar backups from the Efs_ backup folder...
Click to expand...
Click to collapse
I did not have an image file either. Look above at my post where I describe how to do it from step number 1 forward
I didn't use the tool to fix it
I just suggested getting the tool and learning how to use it
Sent from my GT-I9100 using xda premium

jcrompton said:
I didn't use the tool to fix it
Click to expand...
Click to collapse
Just to make the whole thread clear, is your IMEI now the original IMEI or the default U1 IMEI of 0049...?

Hmm..in the end i fixed this by flashing the efs from the official kh3 firmware through odin (clear efs checked). Now my imei changed to a generic one but i don't really care: i have my baseband back and the phone works. I just hope the FBI or something isn't after me now.

vnvman said:
Hmm..in the end i fixed this by flashing the efs from the official kh3 firmware through odin (clear efs checked). Now my imei changed to a generic one but i don't really care: i have my baseband back and the phone works. I just hope the FBI or something isn't after me now.
Click to expand...
Click to collapse
Do you have an EFS_BACKUP folder on your sdcard? And if so do you have any compressed files with older (mine was dated Dec31 2010) .nv_data.bak files?
If you do then that's what I ultimately used to restore my IMEI (not the generic one)

jcrompton said:
Do you have an EFS_BACKUP folder on your sdcard? And if so do you have any compressed files with older (mine was dated Dec31 2010) .nv_data.bak files?
If you do then that's what I ultimately used to restore my IMEI (not the generic one)
Click to expand...
Click to collapse
Thanks, i'll try that right away.

vnvman said:
Actually i don't understand how he made it: ktool doesn't use a tar file like posted, but an img file, and you can only find tar.gz files in the backup folder. How do you get an img file out of those?
Click to expand...
Click to collapse
kTool does both, raw .IMG dump and filebased .tar.gz backup.

Does K-Tool work with CF-Root kernel?

HellcatDroid said:
kTool does both, raw .IMG dump and filebased .tar.gz backup.
Click to expand...
Click to collapse
Wtf, i got answered by Hellcat himself!
Thanks, i didn't notice that option, i would have gone much less nuts if i knew it, stupid me

nfribeiro said:
Does K-Tool work with CF-Root kernel?
Click to expand...
Click to collapse
Yes, should work fine.
Should you find any missbehavings or issues though, please let me know and they shall be fixed
vnvman said:
Wtf, i got answered by Hellcat himself!
Thanks, i didn't notice that option, i would have gone much less nuts if i knew it, stupid me
Click to expand...
Click to collapse
lol xD
Well, but not necessarily stupid, the first few versions indeed only made the raw .IMG dump and the button still only says "backup to /sdcard/efs.img" (yeah, I should really change that text )
But since some 1.2x build it makes the .tar as well and when you hit the restore button it asks if you want to restore the .IMG or the .tar

Haha yeah right, i never hit restore because i didn't have an img dumped to the sd so i thought i had nothing to restore there

[HELP] Retrieving TWRP data [SOLVED]

Hello, I would like to know how I could extract backed up TWRP data on my computer? maybe because the data was large TWRP split it into two files : data.ext4.win000 and data.ext4.win001 (sizes 1.5 and 1.2 GB)
How I got there:
I've been using XenonHD rom for quite a while, and this rom uses koush's superuser app.
I noticed there was a newer version on the market so I installed it; however it appears the one used by the rom developer was modified and therefore had a different package name: I ended up with two superuser apps, one of them asking to update the binaries, which I did.
After that the phone got stuck and rebooted two or three times before being stuck indefinitely at 'updating app' message right after the bootanimation. I tried:
- to wipe dalvik cache but it was still stuck;
- I reflashed the rom + gapps but it was still stuck;
- then I went to the /data/app/ folder (via TWRP) and deleted the superuser app i installed from market, as well as the corresponding data in /data/data, wiped cache and dalvik again: still the same...
-the I decided to make a backup via TWRP : one of the whole system, and one of Data partition only;
- then I realised I couldn't transfer it to my computer in TWRP, so I finally made a factory reset, re-flashed the rom+gapps, and then (it worked) copied my backup to the computer
now; how can I retrieve the data of my apps only, as I guess it is the system data that is messed up?
Of course I tried to restore the Data backup in twrp and it got stuck again the same way....
any help greatly appreciated!

You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app

forvrknight said:
You could try appextractor on the play store
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again

asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voilà
I could then retrieve my sms mms messages by retrieving the file smsmms.db (and eventually smsmms.db-journal) located in /data/data/com.android.providers.telephony/databases, and putting them on the phone in the same folder
I could also retrieve my phone call logs by retrieving the files contacts2.db (and eventually contacts2.db-journal) located in /data/data/com.android.providers.contacts/databases, and putting them on the phone in the same folder
Hope it helps someone someday
For some reason replacing the data folder of a particular app does not always work, I have to investigate a bit or maybe start fresh with a new rom and try again
Click to expand...
Click to collapse
It actually helped me, thanks a lot!

Two Questions
asim0 said:
On this file I used AccessData FTK Imager,
Click to expand...
Click to collapse
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
asim0 said:
All you have to do now is to merge the two data folders and voilà
Click to expand...
Click to collapse
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.

pi_yush said:
This is a 4.6 Gigs professional software. If TWRP can read this type of file there must be a smaller tool available for this.
Can you please let me know of any other toll which would do the same?
For the 2nd file do we need to follow the same procedure like 'evidence' and stuff?
Thanks, I am desperate to read some information from TWRP backup and cannot wait 6 days while the 4.6 Gigs of ISO will download.
Click to expand...
Click to collapse
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001

number_thirty_two said:
These files (at least the ones produced by TWRP2 on my phone) are just standard gzipped tar archives. The tar command has supported this format for at least 20 years. You can extract with a command like this:
Code:
tar xvfz data.ext4.win000
tar xvfz data.ext4.win001
Click to expand...
Click to collapse
Thanks number_thirty_two, I copyed thes to a folder I named untar in my home folder of CYGWIN, and extracted my system files perfectly
C:\cygwin\home\carl\untar\
system.ext4.win000
system.ext4.win001
tar xvfz system.ext4.win000
tar xvfz system.ext4.win001

Apologies for resurrecting this, but does anyone know how to extract them if they were compressed as .comp files?

asim0 said:
It didn't work for me...
I finally got my data back by this tricky procedure (there might be an easier way but google+xda was not my friend on this one, I tried ext2explore and ext4explore, linux_reader, Andoird_ICS_JB_ext4_unpacker and maybe some more without success)
I renamed the two files:
data.ext4.win000 renamed as data.ext4.tar.001
data.ext4.win001 renamed as data.ext4.tar.002
Unzipping the first one with 7zip recreates a .tar archive named data.ext4.tar, which is not really a tar archive (extracting it will only give a very few files, for me it only included the image files of my custom bootanimation)
On this file I used AccessData FTK Imager, which would recognise the 'evidence' as a tar file and would allow you to export the data, however this is only the data contained originally in the first file (data.ext4.win000) (although the reconstructed archive was the right size, for me 2.7GB, the part extracted by this software was only 1.5GB)
To recover the second part, simply rename the second file (initially data.ext4.win001) into data.7z and then extract. (this does not work with the first file, all you would get is again a very few files, for me it looked like the content of a single apk file)
All you have to do now is to merge the two data folders and voil
Click to expand...
Click to collapse

[Q] Needed secsettings.apk and secsettings.odex for NH1, quickly!

Hey guys!
So I was just installing S5 Settings from balliboxer
and now I am an idiot to backup the secsettings apk and odex.
After I installed it, it gone FC.
Please somebody have an stock 4.4.2 SecSettings.apk and odex file please?
I'm running on 4.4.2 G7102 NH1.

sorry i don't have nh1 so i can't help you but what about four threads for the same thing , it's not realy serious man if you need help just post one time
if you have a pc :
domload your rom from Sam
http://www.sammobile.com/firmwares/download/36186/G7102XWUBNI2_G7102OLBBNI2_XSE.zip/
--extract it yoy will have G7102XWUBNI2_G7102OLBBNI2_XSE.tar.md5 use 7zip and extract it
--When you have completed extracting all of them, you'll find many files including many .img files. For Apps you need to extract system.img. Unlike normal nandroid backup's system.img file which in yaffs, this stock one in different. So, unyaffs tool can't unpack the system.img
--To extract the system.img, download this tool: sgs2toext4 (created by drphrozen). On extracting it you'll have sgs2toext4.jar file.
--Open a command window and set the directory where you have .jar file.
--Now type sgs2toext4.jar and press enter.
--The .jar will run in a new window & will ask you to drag & drop the system.img file there. Do the same and wait till the process completes.
--When the process completes, you'll find a file named system.ext4.img in the same folder where you had the system.img file.
--Now download ext2reader and install it. Then open the program open your system.img.ext4
--Now navigate in to find the apk you need and extract it copy to your phone

maxx35000 said:
sorry i don't have nh1 so i can't help you but what about four threads for the same thing , it's not realy serious man if you need help just post one time
if you have a pc :
domload your rom from Sam
http://www.sammobile.com/firmwares/download/36186/G7102XWUBNI2_G7102OLBBNI2_XSE.zip/
--extract it yoy will have G7102XWUBNI2_G7102OLBBNI2_XSE.tar.md5 use 7zip and extract it
--When you have completed extracting all of them, you'll find many files including many .img files. For Apps you need to extract system.img. Unlike normal nandroid backup's system.img file which in yaffs, this stock one in different. So, unyaffs tool can't unpack the system.img
--To extract the system.img, download this tool: sgs2toext4 (created by drphrozen). On extracting it you'll have sgs2toext4.jar file.
--Open a command window and set the directory where you have .jar file.
--Now type sgs2toext4.jar and press enter.
--The .jar will run in a new window & will ask you to drag & drop the system.img file there. Do the same and wait till the process completes.
--When the process completes, you'll find a file named system.ext4.img in the same folder where you had the system.img file.
--Now download ext2reader and install it. Then open the program open your system.img.ext4
--Now navigate in to find the apk you need and extract it copy to your phone
Click to expand...
Click to collapse
Thanks dude! And sorry for those 4 threads. Gonna download it!
This will take soooooo long! My Internet connection is slow and can complete in 9-10 hours!

Just be patient and people will see your thread and help you! But making FOUR posts...?

maxx35000 said:
sorry i don't have nh1 so i can't help you but what about four threads for the same thing , it's not realy serious man if you need help just post one time
if you have a pc :
domload your rom from Sam
http://www.sammobile.com/firmwares/download/36186/G7102XWUBNI2_G7102OLBBNI2_XSE.zip/
--extract it yoy will have G7102XWUBNI2_G7102OLBBNI2_XSE.tar.md5 use 7zip and extract it
--When you have completed extracting all of them, you'll find many files including many .img files. For Apps you need to extract system.img. Unlike normal nandroid backup's system.img file which in yaffs, this stock one in different. So, unyaffs tool can't unpack the system.img
--To extract the system.img, download this tool: sgs2toext4 (created by drphrozen). On extracting it you'll have sgs2toext4.jar file.
--Open a command window and set the directory where you have .jar file.
--Now type sgs2toext4.jar and press enter.
--The .jar will run in a new window & will ask you to drag & drop the system.img file there. Do the same and wait till the process completes.
--When the process completes, you'll find a file named system.ext4.img in the same folder where you had the system.img file.
--Now download ext2reader and install it. Then open the program open your system.img.ext4
--Now navigate in to find the apk you need and extract it copy to your phone
Click to expand...
Click to collapse
Unfortunately this doesn't work. When you drop the system.img.ext4 file onto the sgs2ext4 tool, no file is produced. The tool just keeps endlessly repeating:
"system.img.ext4 32 B 0 B/s"
I think that tool is too old (2.5 years old) and doesn't support the newest Samsung firmwares.

siraltus said:
Unfortunately this doesn't work. When you drop the system.img.ext4 file onto the sgs2ext4 tool, no file is produced. The tool just keeps endlessly repeating:
"system.img.ext4 32 B 0 B/s"
I think that tool is too old (2.5 years old) and doesn't support the newest Samsung firmwares.
Click to expand...
Click to collapse
witch firmware do you want to extract ?and whitch file you want ?
i 've extract my latest firmware 09/2014 so it work fine for me

maxx35000 said:
witch firmware do you want to extract ?and whitch file you want ?
i 've extract my latest firmware 09/2014 so it work fine for me
Click to expand...
Click to collapse
The T-Mobile Galaxy Note 4 (SM-N910T) NK4 firmware. I can't find any instructions online on extracting Samsung firmwares other than these, which were originally written up by rwilco12 a long time ago and reposted endlessly.

siraltus said:
The T-Mobile Galaxy Note 4 (SM-N910T) NK4 firmware. I can't find any instructions online on extracting Samsung firmwares other than these, which were originally written up by rwilco12 a long time ago and reposted endlessly.
Click to expand...
Click to collapse
you have one solution try to extract md5 file
and direct mount system.img in ubunt it work for me then copy the file you want

maxx35000 said:
you have one solution try to extract md5 file
and direct mount system.img in ubunt it work for me then copy the file you want
Click to expand...
Click to collapse
I'll try doing that in a Linux VM. I'm on Windows and the Diskinternals Linux Reader keeps saying the filesystem is invalid.

siraltus said:
I'll try doing that in a Linux VM. I'm on Windows and the Diskinternals Linux Reader keeps saying the filesystem is invalid.
Click to expand...
Click to collapse
give me a link to download the system.img i try to extract it

maxx35000 said:
give me a link to download the system.img i try to extract it
Click to expand...
Click to collapse
Thank you for your help. It's this firmware: http://www.sammobile.com/firmwares/download/39224/N910TUVU1ANK4_N910TTMB1ANK4_TMB.zip/

Anything? Is this a no-go?

siraltus said:
Thank you for your help. It's this firmware: http://www.sammobile.com/firmwares/download/39224/N910TUVU1ANK4_N910TTMB1ANK4_TMB.zip/
Click to expand...
Click to collapse
sorry i have forget to do it i download the file now
but what the files needed in ?

maxx35000 said:
sorry i have forget to do it i download the file now
but what the files needed in ?
Click to expand...
Click to collapse
I just want to find a method that works for extracting the Note 4 firmware because none I found online work.

siraltus said:
I just want to find a method that works for extracting the Note 4 firmware because none I found online work.
Click to expand...
Click to collapse
I found that the Linux method works on my Mac. Took a ton of tinkering and restarting the emulator on my machine.
sgs2ext4.jar did not work for me in Windows. It just hangs.

sbrownla said:
I found that the Linux method works on my Mac. Took a ton of tinkering and restarting the emulator on my machine.
sgs2ext4.jar did not work for me in Windows. It just hangs.
Click to expand...
Click to collapse
yes sgs2ext4.jar work with some of system.img but not all but you can mount in linux i have extracted note 4 img :good:

maxx35000 said:
give me a link to download the system.img i try to extract it
Click to expand...
Click to collapse
The SAMMOBILE firmware or the system.img? I'm not yet downloading it. Let's see if I can resume the download.