I tried to pull the system files from the stock system.img thru Dsixda kitchen....it said no system files found. Sgs2 popped up, but there was no files.
I did this to pull system files from tmobile stock firmware. So im not too sure of why it didnt pull the files.
I did use 7zip to "unzip" the tar file. Selected system.img and put it in the kitchen....selected "set up working folder"...then I got no system files found.
Am I missing something?
Sent from a Insane S4
alloycowboy said:
I tried to pull the system files from the stock system.img thru Dsixda kitchen....it said no system files found. Sgs2 popped up, but there was no files.
I did this to pull system files from tmobile stock firmware. So im not too sure of why it didnt pull the files.
I did use 7zip to "unzip" the tar file. Selected system.img and put it in the kitchen....selected "set up working folder"...then I got no system files found.
Am I missing something?
Sent from a Insane S4
Click to expand...
Click to collapse
try updated kitchen
regards
Solved
Im on current version
Sent from a Insane S4
Why don't you connect your phone in debug mode and shift right click in your working folder and : adb pull /system/
Or are you working from files only? If so you can run your Linux commands from kitchen?
Sent from my GT-I9505G using Tapatalk 2
Make it an ext4 then add a boot.img and a cache or data partition. Then try to set up the working folder
Sent from my cm_tenderloin using xda app-developers app
Related
hi...
i want to change standard notification bar from my htc desire running sense froyo rom with mod battery percentage, animation icons for data, signal, etc.
what i did is :
1. pull framework-res.apk from /system/framework folder
2. extract framework-res.apk using apktool
3. extract & overwrite with icons colour pack v4 downloaded from http://forum.xda-developers.com/showthread.php?t=722993 into drawable & drawable-hdpi folder from extracted framework apk folder.
4. bundled modified framework-res.apk using apktool
5. sign framework-res.apk
6. in recovery mode, adb push framework-res.apk to /system/framework. before doing that, i mount /system first..
7. reboot
what i found, everytime i choose network setting or wireless setting it crashed with error message process.com.android.settings has stopped unexpectedly.
why this error occured ? any other step that i did is wrong ?
I just pull from adb, my PC has 7zip installed so can see drill into the compressed file, drag replace the altered images, back out of the compressed file to commit, push via adb, reboot.
Sent from my Nexus One using XDA App
Why not use the UOT kitchen?
Sent from my HTC Desire using XDA App
HTCinToronto said:
I just pull from adb, my PC has 7zip installed so can see drill into the compressed file, drag replace the altered images, back out of the compressed file to commit, push via adb, reboot.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
This is what I do, basically. I make the battery mod with UOT, and when the flashable zip is ready I extract the framework-res to some folder and just replace couple of images, then I'll put the modified framework-res back to the UOT-file and flash it. Works every time.
EDIT: I don't extract the files within framework-res.zip, only the .zip itself so I can open it via WinRar and replace the files. It isn't probably even needed, you could probably replace the needed files when browsing the UOT file with winrar/whatever etc etc. Haven't tried.
Can this same method be applied to anything that can be found in the framework ?
I've compiled and installed a modded kernel. I'm trying to figure out how to load AOSP compiled binaries. I've tried using adb flash_image system /sdcard/system.img, but I get "failed with error: 6." Does anyone know what this means or how to load system.img on a Galaxy Tab from VZW? I'm working on reactivating the phone dialer...
the galaxy tab has nothing like fastboot, so its pretty hard to flash it! but u can try to overwrite a stock factory.rfs with the files from ur system.img and flash via odin!
That sounds like a great idea. However, I'm trying to figure out how to put the vendor specific drivers in the system.img, which is mountable and editable. If I could get my hands on an original stock system.img, that'd be awesome.
Sent from my SCH-I800 using XDA App
As far as I know, the Tab doesn't use mtd file system, so I don't think it uses .img extensions.
Not positive though. Somebody correct me if I'm wrong.
I know for a fact that img files are created as the output of an Android system build. This img can be broken apart with standard Linux tools. I've already done this. I've also mounted factoryfs.rfs to a local directory, which allows me to move apps to and from the file system.
Sent from my SCH-I800 using XDA App
If you have a md5 of it too, you should be able to flash it via an advanced restore in CWM recovery. That is if it is only the data that is flashed to /system. otherwise I would suggest converting it to a .fs or .tar and flash via heimdall or Odin (respectively).
What PC tools can I use to open .img files in a nandroid/CWM backup set?
Must I set up an Android ROM cooking kitchen using Virtual Box + Ubuntu, or is there another way?
zyborg said:
What PC tools can I use to open .img files in a nandroid/CWM backup set?
Must I set up an Android ROM cooking kitchen using Virtual Box + Ubuntu, or is there another way?
Click to expand...
Click to collapse
use the attached unyaffs.exe to extract a system.img! simply drag the created system.img onto unyaffs.exe and it will extract alle the files in the same directory!
to rebuild, i think it might be able to create a image file in magic disk maker but im not sure
zyborg said:
What PC tools can I use to open .img files in a nandroid/CWM backup set?
Must I set up an Android ROM cooking kitchen using Virtual Box + Ubuntu, or is there another way?
Click to expand...
Click to collapse
http://android-dls.com/wiki/index.p...cking.2C_Editing.2C_and_Re-Packing_the_images
Landroid said:
use the attached unyaffs.exe to extract a system.img! simply drag the created system.img onto unyaffs.exe and it will extract alle the files in the same directory!
to rebuild, i think it might be able to create a image file in magic disk maker but im not sure
Click to expand...
Click to collapse
thanks! this was very easy to use
Ok so i was trying to root my SGS and got stuck in the first step.
It says after u download the zip u unzip and there is supposed to be a .tar file.
But after i unzipped mine was another zip so i unzipped that and there was some weird file called : zImage
Its not a tar file so says my computer. Is it supposed to be like that? Any help will be thanked.
So i tried rooting my phone and it didn't work, i am on gingerbread and have no experience about SGS but have some experience about android.
So after i failed my root i tried turning on the phone but this weird picture of a phone/yellow triangle/computer
And it won't let me turn on the phone fully, i can only go to download mode and nothing else. i have tried hard reset but not working.
Please help!
Simliar problem as this http://forum.xda-developers.com/showthread.php?t=805923.
just unzip it first one and its tar file just put it in pda in odin and flash it. don't
Sent from my GT-I9100 using Tapatalk 2
yahyoh said:
just unzip it first one and its tar file just put it in pda in odin and flash it. don't
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
From properties it said that the zImage file is a tar file so should i flash using that?
Edited description
cuz u have to flash the kernel and the phone will boot. as i said before just unzip the downloaded file the put the unziped file in pda in odin
don't extract the zimage file from the tar file
Sent from my GT-I9100 using Tapatalk 2
androidboss7 said:
From properties it said that the zImage file is a tar file so should i flash using that?
Click to expand...
Click to collapse
the zimage is inside the tar file don't extract it just flash the tar file
Sent from my GT-I9100 using Tapatalk 2
You have to flash a complete stock rom to get the phone to work
Gesendet von meinem GT-I9000 mit Tapatalk
Start with settings in Windows file manager = show file extensions (like .tar .zip .txt .exe)
Depending on what program used to unzip, .zip and .tar might have same icons. Show file extension to see difference.
Sent from my GT-I9000
yahyoh said:
the zimage is inside the tar file don't extract it just flash the tar file
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
thats what i did and this is what happened.
do i have to flash to stock rom again or can i just root again and it will
boot?
The zimage file is contained in the .tar, but still you need to flash the .tar file...
.Tar files seem like zip files and can be extracted, so to solve the windows showing the file as zipped do as O-T said:
O-T said:
Start with settings in Windows file manager = show file extensions (like .tar .zip .txt .exe)
Depending on what program used to unzip, .zip and .tar might have same icons. Show file extension to see difference.
Sent from my GT-I9000
Click to expand...
Click to collapse
Then start ODIN with administrator privileges and use the .tar file (ONLY TAR FILES) as PHONE, do not choose any other file and certainly dont tick re-partition, after all are ready (and your phone is in download mode and recognized by ODIN) press start.
If you failed and see the screen with "Phone/YellowTriangle/Computer" do not worry, just pull out the phone battery, leave it with battery off for 30 secs, put the battery back in, get your phone to download mode (guess you are putting your phone to download mode before flashing, right?) and try again using the instructions that you have read in all those posts!
Coolgreek said:
The zimage file is contained in the .tar, but still you need to flash the .tar file...
.Tar files seem like zip files and can be extracted, so to solve the windows showing the file as zipped do as O-T said:
Then start ODIN with administrator privileges and use the .tar file (ONLY TAR FILES) as PHONE, do not choose any other file and certainly dont tick re-partition, after all are ready (and your phone is in download mode and recognized by ODIN) press start.
If you failed and see the screen with "Phone/YellowTriangle/Computer" do not worry, just pull out the phone battery, leave it with battery off for 30 secs, put the battery back in, get your phone to download mode (guess you are putting your phone to download mode before flashing, right?) and try again using the instructions that you have read in all those posts!
Click to expand...
Click to collapse
Thanks mate!
After i read ur post i flashed again and it works again with root!
So final question. if i want to unroot do i just flash stock kernel and i am unrooted?
androidboss7 said:
Thanks mate!
After i read ur post i flashed again and it works again with root!
So final question. if i want to unroot do i just flash stock kernel and i am unrooted?
Click to expand...
Click to collapse
Glad to be of help!
About your question: Exactly. Flashing original kernel will remove root!
Coolgreek said:
Glad to be of help!
About your question: Exactly. Flashing original kernel will remove root!
Click to expand...
Click to collapse
thanks for ur help dude
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
So I have all the files I think I need in the platform-tools folder and adb recognizes the device but when I type adb sideload update.zip, it says *cannot read 'update.zip' *. The problem isn't that it doesn't read sideload, but it doesn't read the file. Any thoughts?
I hope I'm able to help I had the same prob...when I renamed the file to update.zip. The thing was the file was really update.zip.zip, so try that as file name and see what happens....
Make sure the file you want to sideload is in the same folder as your adb folder, or type out the full path to the file you want to install.
Sent from my HTC One using XDA Premium HD app
I only named the file update so its full title would be update.zip so I don't think its the name that's causing the trouble. The file is already stored in the same folder as adb and fastboot. Thanks though, it really means a lot to have help on this
I had this issue as well. I only renamed it to update....after trying again and renaming it to update.zip it work fine. It'll show the file to be sideloaded as update.zip.zip
Sent from my Nexus 4 using xda premium
1. The update.zip.zip would have worked, it finally started sending, but I didn't want to lose any data so I did the framework service hack instead. Thanks guys!