Related
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
Can someone skilled please explain in detail how to create a non-wipe version of a given stock rom?
I know that the data.img has to be removed from the according .tar.md5 file (see picture), in order to do that you have to open the file with a zip program (remove the .md5 or open it with "open with").
The problem is, after removing the data.img the .tar.md5 file want flash proper with odin. I guess this is due to a wrong md5 sum which was not changed during this process, and therefore is no longer valid!
I remember that I read once that you have to use a specific packer for that (winrar for example is not able to do this), but I cant find this source again!
Can someone please illuminate us in regard to that?
Thank you very much in advance!
ps.:
I posted this in development section because I think this is more development related as Q/A! If this violates the forum rules any mod should feel free to move this thread into Q/A...
You don't have to keep the .md5 extension to flash via odin, and thus skip the md5 checksum check.
But I don't know if it will flash properly after you removed the data.img
I have never tried that. Maybe you still have to modify a script or something...
I thought of using Mobile Odin and not selecting the Code.tar.md5 through the open file dialog, but rather selecting every part to flash individually and NOT selecting anything for data.
Too scared to try...
thanks latoc!
can someone with experience confirm that is it enough to remove the data file from the tar, repack it and don't add .md5?
I tried the mobile odin method and it wiped my phone even though nothing was selected in the data part.
There must be a script somewhere that tells the phone to wipe...
I made a backup before so no problem for me
Sent from my GT-N7000 using XDA App
Use peazip, it can create working tar images that can be flashed. Winrar corrupts tar. Some say 7z also does a good job. I haven't tried it as I was happy with peazip. You can even use gzip. Hope it helps.
You can even extract all the contents, remove add files, then use paezip or gzip to make a tar. Works perfectly. MD5 is not a necessity. If you want, you can create a MD5 hash for the new tar that you have created. Google it. Its easy.
ragin said:
Use peazip, it can create working tar images that can be flashed. Winrar corrupts tar. Some say 7z also does a good job. I haven't tried it as I was happy with peazip. You can even use gzip. Hope it helps.
You can even extract all the contents, remove add files, then use paezip or gzip to make a tar. Works perfectly. MD5 is not a necessity. If you want, you can create a MD5 hash for the new tar that you have created. Google it. Its easy.
Click to expand...
Click to collapse
thanks for the answer!
peazip uses 7zip via console, so its the same!
anyway, the tar from peazip wont flash! odin (1.83 and 1.85) stops with an error (could not write) with the boot.bin (from my modified tar), after that the phone wont boot and give the message: firmware update failed, use kies recovery mode blabla
only way to get it back to life without kies is to flash a proper boot.bin (sbl.tar), which is the software boot loader.
did you experience anything like that before?
No one with an idea?
There must be enough people with this knowledge around here...
Sent from my GT-N7000 using xda premium
I didn't try it myself but someone else post this link to this thread in the SGSII forums about what you're asking about, I want to try when I get home and get the latest LA3 firmware but here it is:
http://forum.xda-developers.com/showthread.php?t=1132724
matius44 said:
I didn't try it myself but someone else post this link to this thread in the SGSII forums about what you're asking about, I want to try when I get home and get the latest LA3 firmware but here it is:
http://forum.xda-developers.com/showthread.php?t=1132724
Click to expand...
Click to collapse
And this supercomplicated procedure achieves what exactly?
A non-wiping rom update?
I think he just wanted to delete the data image, repack and flash with odin.
Just needed the correct packer. Right?
legion1911 said:
And this supercomplicated procedure achieves what exactly?
A non-wiping rom update?
I think he just wanted to delete the data image, repack and flash with odin.
Just needed the correct packer. Right?
Click to expand...
Click to collapse
right, it should be enough to delete the data.img!
it looks like the problem is the packer, although i'm in contact with intratech (who is a xda-mod who did this a few times @sgs2 forums, besides he's really great in what he is doing!) and he meant that there could also be a wipe instruction inside the cache.img!
when i know more i will post it here!
TML1504 said:
right, it should be enough to delete the data.img!
it looks like the problem is the packer, although i'm in contact with intratech (who is a xda-mod who did this a few times @sgs2 forums, besides he's really great in what he is doing!) and he meant that there could also be a wipe instruction inside the cache.img!
when i know more i will post it here!
Click to expand...
Click to collapse
Great! Will be waiting for you're simpler procedure as I found that way hard myself!
Sent from my GT-N7000
TML1504 said:
thanks for the answer!
peazip uses 7zip via console, so its the same!
anyway, the tar from peazip wont flash! odin (1.83 and 1.85) stops with an error (could not write) with the boot.bin (from my modified tar), after that the phone wont boot and give the message: firmware update failed, use kies recovery mode blabla
only way to get it back to life without kies is to flash a proper boot.bin (sbl.tar), which is the software boot loader.
did you experience anything like that before?
Click to expand...
Click to collapse
I think you can safely remove boot.bin from the tar file. You should verify this before trying.
PS : If the bootloaders havent changed, why do you want to flash them? They are already there.
That packer could be used to easily install anything.
So if you find that packer, please let us know.
ragin said:
I think you can safely remove boot.bin from the tar file. You should verify this before trying.
PS : If the bootloaders havent changed, why do you want to flash them? They are already there.
Click to expand...
Click to collapse
it would be ok to remove the boot.bin as well, but then the flash would fail on the next (first) file odin tries to flash!
in case of not deleting boot.bin, this would be the first and therefore damage the boot partition, a reboot is not possible. that's the reason i hat to reflash sbl.bin!
the reason for this is again the packer, if the .tar would be ok, so would be the flash procedure!
intratech suggests to use linux and the following command to create a odin flashable tar:
Code:
tar -c boot.bin cache.img factoryfs.img hidden.img modem.bin param.lfs Sbl.bin zImage >> [Name of the desired file].tar
i will look far a tar executable for win32 and report!
done!!!
found a working packer: tar for win32
this was a little bit tricky, because the download from http://gnuwin32.sourceforge.net/packages/gtar.htm did not work, i always get the error message "The procedure entry point libiconv_close could not ..."
searching in google about that i discovered the following:
in the download from sourceforge is an old dll, the "libiconv-2.dll" which causes this error! you have to download a newer version from diffutils 2.8.7-1, which can be found here!
then, simple rename the inside libiconv2.dll to libiconv-2.dll and overwrite the one in the \bin dir from the C:\Program Files\GnuWin32\bin!
then add "C:\Program Files\GnuWin32\bin" to the path variables of your system, then you can use the tar command from the whole shell!
lol, until now this was all to get the tar program running! all people running linux won't need this steps, as tar should be fully functional for them!
then simple extract the rom files with whatever packer you like, you should see a file named "CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5" or whatever your original rom is. remove the .md5 and extract again, then you should end up with some more files:
boot.bin
cache.img
data.img
factoryfs.img
hidden.img
param.lfs
sbl.bin
zimage
now, tar the files you want to flash into one file with the shell command from intratech, for example:
tar -c boot.bin factoryfs.img hidden.img param.lfs sbl.bin >> filename.tar
you can also add whatever kernel you wish, add a zimage then!
DO NOT ADD CACHE.IMG, AS IT CONTAINS THE WIPE COMMAND!!!
now flash this file (and perhaps the proper modem.tar.md5) with odin as PDA (modem as phone) and you are done!
upgraded with this method from KL7 to LA3 without wipe and without any problems. once you have tar for win32 up and running it's really simple!
big thanks to intratech for aiding me about the cache.img and the tar syntax!!
ps.: i don't care about the yellow triangle nor the flash counter, as it is very easy to reset: use the sbl.bin from the sgs2, flash it, remove battery, use usb-jig, remove battery, flash sbl.bin from note, remove battery, done! no triangle, counter at 0
TML1504 said:
done!!!
found a working packer: tar for win32
this was a little bit tricky, because the download from http://gnuwin32.sourceforge.net/packages/gtar.htm did not work, i always get the error message "The procedure entry point libiconv_close could not ..."
searching in google about that i discovered the following:
in the download from sourceforge is an old dll, the "libiconv-2.dll" which causes this error! you have to download a newer version from diffutils 2.8.7-1, which can be found here!
then, simple rename the inside libiconv2.dll to libiconv-2.dll and overwrite the one in the \bin dir from the C:\Program Files\GnuWin32\bin!
then add "C:\Program Files\GnuWin32\bin" to the path variables of your system, then you can use the tar command from the whole shell!
lol, until now this was all to get the tar program running! all people running linux won't need this steps, as tar should be fully functional for them!
then simple extract the rom files with whatever packer you like, you should see a file named "CODE_N7000XXLA3_CL880036_REV02_user_low_ship.tar.md5" or whatever your original rom is. remove the .md5 and extract again, then you should end up with some more files:
boot.bin
cache.img
data.img
factoryfs.img
hidden.img
param.lfs
sbl.bin
zimage
now, tar the files you want to flash into one file with the shell command from intratech, for example:
tar -c boot.bin factoryfs.img hidden.img param.lfs sbl.bin >> filename.tar
you can also add whatever kernel you wish, add a zimage then!
DO NOT ADD CACHE.IMG, AS IT CONTAINS THE WIPE COMMAND!!!
now flash this file (and perhaps the proper modem.tar.md5) with odin as PDA (modem as phone) and you are done!
upgraded with this method from KL7 to LA3 without wipe and without any problems. once you have tar for win32 up and running it's really simple!
big thanks to intratech for aiding me about the cache.img and the tar syntax!!
ps.: i don't care about the yellow triangle nor the flash counter, as it is very easy to reset: use the sbl.bin from the sgs2, flash it, remove battery, use usb-jig, remove battery, flash sbl.bin from note, remove battery, done! no triangle, counter at 0
Click to expand...
Click to collapse
Bravo, Wiener, Bravo!
Btw I found another way and just did it.
I used dsixda kitchen to deodex, root, zipalign and make a non-wipe version and it was easy!
Thought I might share it with you guys
Sent from my GT-N7000
thx for the info, but i personally dislike most deodexed roms!
besides it could cause unknown troubles (remember tha smali baksmali issue) it generally runs less smooth! the reason? simply speaking odexed is optimized (the o in odex), deodex trades this optimizations for the advantage of being simpler to skin, modify etc.
this means deodexed may be acceptable for people who want to skin and modify a lot, therefore almost all custom roms are deodexed. it makes it simpler for the cook!
you as an enduser would almost always prefer odexed roms. also lots of quality mods are available for odexed too...
just my opinion, and i used to use custom roms a lot!
Sent from my GT-N7000 using xda premium
Ok I just upgraded from KKA to LA3 without wiping using nothing but the stock files and mobile odin:
Launch mobile odin, and fill each line one by one, selecting the correct firmware file, except data and cache.
Select ever root if you didn't select a rooted kernel, and flash that baby! !!
Sent from my GT-N7000 using XDA App
Latoc said:
Ok I just upgraded from KKA to LA3 without wiping using nothing but the stock files and mobile odin:
Launch mobile odin, and fill each line one by one, selecting the correct firmware file, except data and cache.
Select ever root if you didn't select a rooted kernel, and flash that baby! !!
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
also thx, for me this didn't work from KL7 to LA1, got bootloops! but generally fine if this was only my fault, and the odin method works fine!
This is the latest firmware (T700XXU1ANF7) as of June 29, 2014 for the Galaxy Tab S 8.4 (Wifi) model (SM-T700).
"No-Wipe" means your app data and storage will all stay 100% in tact. Only system mods, custom kernels, and root will be removed as you are flashing stock firmware.
Please feel free to use as you see fit.
Download: http://www.androidfilehost.com/?fid=23501681358556680
open1your1eyes0 said:
This is the latest firmware (T700XXU1ANF7) as of June 29, 2014 for the Galaxy Tab S 8.4 (Wifi) model.
"No-Wipe" means your app data and storage will all stay 100% in tact. Only system mods, custom kernels, and root will be removed as you are flashing stock firmware.
Please feel free to use as you see fit.
Download: http://www.androidfilehost.com/?fid=23501681358554636
Click to expand...
Click to collapse
No 10.5 love?
mitchellvii said:
No 10.5 love?
Click to expand...
Click to collapse
+1, can't forget us 10.5 owners
mitchellvii said:
No 10.5 love?
Click to expand...
Click to collapse
Stock Firmware SM-T800 (Wi-FI)
Stock Firmware SM-T805 (LTE)
Now all I need is a rom to screw my rig up with so I'll need this
Is there any tool to extract system.img?
UPDATE:
I found a way how to do it.
I used sgs4ext4fs by Chainfire to modify system.img and after that Ext2explore to extract files from modified system.img .
Also if anyone is interested how to extract hidden.img, first you need to modify it with sgs4ext4fs and after that use sgs2toext4. Then you can open modified hidden.img with ext4_unpacker and extract files from it.
Dabolx said:
Is there any tool to extract system.img?
UPDATE:
I found a way how to do it.
I used sgs4ext4fs by Chainfire to modify system.img and after that Ext2explore to extract files from modified system.img .
Also if anyone is interested how to extract hidden.img, first you need to modify it with sgs4ext4fs and after that use sgs2toext4. Then you can open modified hidden.img with ext4_unpacker and extract files from it.
Click to expand...
Click to collapse
u did it on Windows or Linux? cause I want the system file extracted. can u send it to me please?
Dabolx said:
Is there any tool to extract system.img?
UPDATE:
I found a way how to do it.
I used sgs4ext4fs by Chainfire to modify system.img and after that Ext2explore to extract files from modified system.img .
Also if anyone is interested how to extract hidden.img, first you need to modify it with sgs4ext4fs and after that use sgs2toext4. Then you can open modified hidden.img with ext4_unpacker and extract files from it.
Click to expand...
Click to collapse
Maybe you could repack it with root files to get root. There is a how to video on you tube. I would do it, but my linux machine is down.
suzook said:
Maybe you could repack it with root files to get root. There is a how to video on you tube. I would do it, but my linux machine is down.
Click to expand...
Click to collapse
Please don't coming from the one that said root is okay from the note 10.1 2014 edition. Root and profit. Sound familiar. You mean root and brick.
mitchellvii said:
No 10.5 love?
Click to expand...
Click to collapse
ewells38 said:
+1, can't forget us 10.5 owners
Click to expand...
Click to collapse
Apologies for the delay folks. It's now uploaded.
http://forum.xda-developers.com/showthread.php?t=2800372
Dabolx said:
Is there any tool to extract system.img?
UPDATE:
I found a way how to do it.
I used sgs4ext4fs by Chainfire to modify system.img and after that Ext2explore to extract files from modified system.img .
Also if anyone is interested how to extract hidden.img, first you need to modify it with sgs4ext4fs and after that use sgs2toext4. Then you can open modified hidden.img with ext4_unpacker and extract files from it.
Click to expand...
Click to collapse
well, we need some step by step instruction here
anyone able to extract system files??
Dabolx said:
Is there any tool to extract system.img?
UPDATE:
I found a way how to do it.
I used sgs4ext4fs by Chainfire to modify system.img and after that Ext2explore to extract files from modified system.img .
Also if anyone is interested how to extract hidden.img, first you need to modify it with sgs4ext4fs and after that use sgs2toext4. Then you can open modified hidden.img with ext4_unpacker and extract files from it.
Click to expand...
Click to collapse
Chainfire needs recovery.img to make cf autoroot for us. Are u able to extract the recovery.img for the q0.5 as well as 8.4 so I can post it in the cf auto root thread so we can get root?
FYI for those of you who have PMed me I have fixed the corrupt download and updated the OP link.
Zip
Dabolx said:
Is there any tool to extract system.img?
UPDATE:
I found a way how to do it.
I used sgs4ext4fs by Chainfire to modify system.img and after that Ext2explore to extract files from modified system.img .
Also if anyone is interested how to extract hidden.img, first you need to modify it with sgs4ext4fs and after that use sgs2toext4. Then you can open modified hidden.img with ext4_unpacker and extract files from it.
Click to expand...
Click to collapse
Can you please zip extracted and provide a link!!
Thanks
No
jazzespresso said:
well, we need some step by step instruction here
anyone able to extract system files??
Click to expand...
Click to collapse
No I am unable to extract and have done many in the past. It appears no one here has been successful either!!!
EMSpilot said:
No I am unable to extract and have done many in the past. It appears no one here has been successful either!!!
Click to expand...
Click to collapse
bare with me on that one since I tried too many different options, following worked for me - required files attached here (I ziped, so hopefully XDA did not blocked it)
This is for Windows PC:
1. Download sgs4ext4fs.exe, and download firmware, unzip firmware up until you see system.img.
2. Open command prompt (on windows, click start, type cmd) where system.img, and type
sgs4ext4fs --trim system.img systemt.img
........ > you will see bunch of ............., but wait until it finishes.
3. Once it finishes it creates systemt.img, get sgs2toext4.jar (save it to the same folder), and open sgs2toext4.jar, and drag and drop newly created systemt.img to the window (sgs2toext4.jar's window), wait until it finishes, when it finishes it will create systemt.ext4.img
4. Now last step, download ext2explore.exe, and open it, and go to file --> open image and pick systemt.ext4.img, it will show the img file there (on both side of window), on the left side, select the systemt.ext4.img (should be showing full path), right click your mouse, and select save to your desktop or any other folder location you pick.
Obviously, next step will be odexing everything:laugh:
Yorgo1982 said:
u did it on Windows or Linux? cause I want the system file extracted. can u send it to me please?
Click to expand...
Click to collapse
Here you go:
System img from Galaxy Tab 10.5
How about a custom recovery .the build your own recovery with stock recovery.IMG leads to a http// 404 error online after it builds it.any of you smarter than me individuals know how to build a custom CWM/TWRP img ?
Nexus 5 via Tapatalk
open1your1eyes0 said:
This is the latest firmware (T700XXU1ANF7) as of June 29, 2014 for the Galaxy Tab S 8.4 (Wifi) model (SM-T700).
"No-Wipe" means your app data and storage will all stay 100% in tact. Only system mods, custom kernels, and root will be removed as you are flashing stock firmware.
Please feel free to use as you see fit.
Download: http://www.androidfilehost.com/?fid=23501681358556680
Click to expand...
Click to collapse
I actually needed this this morning and feel indebted to you cause the online so called Stock Firmwares lead to mad amount of bloat to my computer.
Thank you
restore
jball said:
I actually needed this this morning and feel indebted to you cause the online so called Stock Firmwares lead to mad amount of bloat to my computer.
Thank you
Click to expand...
Click to collapse
Thanks this worked like a charm!!! Great work!!!
Hey all, long story short I need to find to the Nougat vendor.img. The link to it from the debloated ROM page appears to be down, so if anyone else has a link to the .IMG file that would be helpful. In the WETA ROM thread, the dev said you go extract it from the .zip but I have no idea where it is/how to flash it in fastboot if it's not a .IMG file. Thanks.
Sent from my Nexus 6P using XDA-Developers mobile app
If the file icon looks like a page with a cd/dvd on it, that is an .img file. Or just right click and look at the properties.
Eric214 said:
If the file icon looks like a page with a cd/dvd on it, that is an .img file. Or just right click and look at the properties.
Click to expand...
Click to collapse
In the zip, the vendor file has a .new.dat extension. Would I change that to .img and flash it in fastboot? Or would that be a mistake?
if the dev says the vendor.img file is included it should be in there, your have to dig through the compressed folder to find it, its usually named vendor.img you might have extensions hidden, or if you have a known .img file elsewhere it will likely have the same icon next to it in the file tree.
you can just extract it and rename the file with a straight ".IMG" prefix and flash that from your ADB folder or using your chosen tool
hutzdani said:
if the dev says the vendor.img file is included it should be in there, your have to dig through the compressed folder to find it, its usually named vendor.img you might have extensions hidden, or if you have a known .img file elsewhere it will likely have the same icon next to it in the file tree.
you can just extract it and rename the file with a straight ".IMG" prefix and flash that from your ADB folder or using your chosen tool
Click to expand...
Click to collapse
So that didn't work (phone wouldn't boot past splash screen) but I did flash this .img file https://www.androidfilehost.com/?fid=24651430732236715 and it worked
RollTribe said:
So that didn't work (phone wouldn't boot past splash screen) but I did flash this .img file https://www.androidfilehost.com/?fid=24651430732236715 and it worked
Click to expand...
Click to collapse
What issue were you having that you needed the vendor image, if you mind me asking?
Was your phone stuck in the splash screen loop?
defcondev said:
What issue were you having that you needed the vendor image, if you mind me asking?
Was your phone stuck in the splash screen loop?
Click to expand...
Click to collapse
I had an old version of TWRP (wasn't aware that there was one that worked with Nougat) and needed to flash an old vendor to get it to work, then a newer one to get my phone to boot. I flash the DP5 vendor and the phone booted just fine, but there was a warning message and I figured it would be better to get the updated vendor.
I obtained the firmware for this model and to my surprise, the odin files do not have the ext4 extension. However, in spite of that, they cannot be opened by my normal tools 7zip or WinZip. I do not understand the encoding for these files, has anyone successfully opened them?
Teracotta said:
I obtained the firmware for this model and to my surprise, the odin files do not have the ext4 extension. However, in spite of that, they cannot be opened by my normal tools 7zip or WinZip. I do not understand the encoding for these files, has anyone successfully opened them?
Click to expand...
Click to collapse
It depends on the image, boot, recovery, system etc and what you want to do with it?
ashyx said:
It depends on the image, boot, recovery, system etc and what you want to do with it?
Click to expand...
Click to collapse
I figured out the issue.
The earlier firmwares list the files as .img, but they are in fact .img.ext4 files. I renamed them, then converted them to proper .imgs and it worked.
Thanks you for giving a response.