Hi,
Tablet version:
Galaxy Tab 4 SM-T530
I am searching for the fastest way to batch flash a group of tablets.
I've wrote an android app, and this app needs to be in the rom.
So i need to modify a rom, and add my app to it.
What i've tried:
http://forum.xda-developers.com/tab-4/development/rom-slimrom-5-0-1-alpha-0-7-t2963906
Downloaded the rom above
Unzipped it to a folder
Downloaded the tool below:
http://forum.xda-developers.com/and...tool-tool-unpack-repack-dat-img-v2-0-t3284806
Extracted the system.new.DAT and added my app to it
Repacked the rom, to system.img
Extracted boot.img from the cyanogenmodrom
Extracted the kernel : boot_matisselte.img
Created .TAR's from those .img's using:
http://forum.xda-developers.com/showthread.php?t=2446269
Flash with odin.
Odin does accept all of the .TAR files, but when i turn on my tablet, it is stuck on the 'Samsung screen'.
Who can help me out, or point my in a good direction?
Related
Hi, I have download a rom which include a tar.md5 file. I know odin could install it easily, but how can I do this from my phone (I haven't got windows at work).
I have take a look in the tar.md5 and it contain :
factoryfs.img
zImage
So, I have seens this kind of file in ClockMod backup dir.
May I create a directory in clockmod, push this file in it, and do a restore ?
Does it work ?
is they another way ?
Hey Guys,
I'm in need of some really n00b friendly advice.
When you flash a new ROM (i.e. CM9) in CWM the tutorials tell you to flash the file named Update.zip. My problem is that I can't seem to find one in the zip file I downloaded for my xperia mini.
I downloaded FXP131, and found the zip file to contain a boot.img, which will be the kernel. And 2 other folders named META-INF and System.
I know how to flash the kernel and expect it was just left in there for easy transportation.
But where in the world is 'update.zip'?
Am I meant to unpackage the kernel then re-zip the META-INF and System folder and then call that 'Update.zip'?
I've flashed roms for some of my other devices before, but they've always used flashtool or samsungs flashtool.
Please help me guys, I don't like sounding this inexperienced
update.zip
I'm wondering if the ROM I am trying to flash needs to be renamed as update.zip in order to work. It is krook's v.6 of JB for the Lenovo K1 tablet. Since the download site has to distinguish between wifi and 3G versions, as well as nvflash versions there are a number of different filenames, however does it need to be renamed after putting it on my SD card?
Generally speaking "update.zip" is used as a generic name. For example the update.zip I just flashed is actually named "rascarlo_maguro_ota_2012-11-01.zip". When you flash a custom ROM in a custom recovery you should be able to browse & flash whichever file you need.
The FXP131.zip file that contains the boot.img and 2 other folders named META-INF and System is the "update.zip"
solved
My problem was an incomplete download. I compared file sizes, and checked md5sums and determined the correct ROM and it is now in the middle of finishing the upgrade/optimization process.
Thx
The tools that I've tried are for earlier versions of Android does anyone know of a working tool? My goal is to downgrade the kernel 1 versoin on my Note 5 AT&T with a locked bootloader.
N920AUCS3CPK1 but running the N920AUCS3CPJ1 kernel.
Update on useful tools:
Assayyed Kitchen for Windows https://forum.xda-developers.com/ch...-android-roms-editor-assayyedkitchen-t3410545
Assayyed takes the system.img you retrieve from decompressing your firmwares AP file. (typically 1 of 4 files known as combination files used to flash to Odin). This tool debloats, deodex, deknox and remove apps from system. In addition it allows you to unpack the kernel (boot.img) and recovery.img files! You can manipulate some settings in Assayyed (see the thread) or even directly as the image is extracted inside of your work folder for both kernel and recovery. You can replace init, change settings in english and etc. Then Assayyed allows you to repack the tool and I can confirm on sm-n920a nov 1 2016 firmware you can flash the repacked image, booting I need to test on a less expensive device first.
(I don't know if it correctly adjusts file permissions in Windows honestly I didn't boot with the final image I only tested that I could flash it, which I could with heimdall for Ubuntu directly from github using .pit file from current firmware csc file).. I have a thread
Carliv Image Kitchen
https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658
This tools is strictly for unpacking/repacking the boot.img and recovery.img files, may have other features I been focused on kernel/recovery. It has some really cool features which I am just learning but the great news is it's available in Ubuntu (also Windows I believe.)
Heimdall for Linux and mac - this is a program that is used on Linux that's similar to Odin for windows. It is capable of flashing extracted tar firmware AP,CP,CSC,and BL using download mode for Samsung devices.
This is not my program.
Also I am limited to Linux for heimdall so testing Mac I can not do but Instructions to install will also be posted using a link
I am testing how to flash the s7 for others limited to Linux or mac.
Linux install of Heimdall on Linux:
Go to the official website here: http://goo.gl/PQC1RN
Scroll down and click on Download(for Linux)
Click to download the Heimdall version for your Linux version (EX. ubuntu13.04-heimdall_1.4.0-0_amd64.deb will work with 14.04 & 13.04 64bit)
Click and download the frontend if you don't like to work inside the terminal
Open your Downloads folder and click to install the files you downloaded
Remember to open Heimdall as Admin(sudo) so it works correctly
Mac install:
http://rootmygalaxy.net/install-odin...3-for-mac-osx/
Steps to flashing frimware on linux:
1. open terminal and type sudo heimdall-frontend
2. look for flash tab
3. extract firmware zip to a folder then create 4 more folders named AP,BL,CP,and CSC
4. Rename AP,BL,CP,CSC by removing the .md5 part of the file name leaving only the .tar at the end
5. Extract each tar to its specific folder
6. Under the flash tab look for pit file and click browse, goto CSC folder and click the pit file
7. Now look for add and from the list under partition details choose which file to add then click browse under it should have the file name you are looking for under partition details if unsure what to put, go through each folder you made and keep adding each file
8. then click start
This is capable of flashing the firmware , as in the pictures it shows it works and fails, i am thinking because i am flashing all at once instead of each folder separate, or in the wrong order
there are forums on xda on how to use heimdall more extensivly but im just doing this for the s7 so productive comments are welcomed
Also this is being tested on a sprint version of the s7 g930p that has been flashed to g930u firmware, in the pictures im flashing a firmware i already have installed just incase i mess up
Worked like a charm for me, this post needs more attention.
XCnathan32 said:
Worked like a charm for me, this post needs more attention.
Click to expand...
Click to collapse
U were able to get all firmware files flashed and able to use phone
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Downunder35m said:
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Click to expand...
Click to collapse
Thank you for this explanation, but the explanation of the video to better understand everyone
Will see if I can at least add some pics while working on Nougat.
Hello,
Thanks for you tutorial.
I have a h96 Pro+ and the last firmware was a .img file... (Link of the firmware : https://mega.nz/#F!d1tHVZgA!Qc0mAom7FBHT9HDv3rGtGQ )
Is there a good guy who can convert this .img to a .zip file please ?
A lot of users are asking for this, me too and if you can help me to do this it will be really cool and appreciate
Thank you,
Carmin.
Thanks for your explanation im trting to port 7.1.1 to my tv box and i have found one funcional the only troble is the wi fi drivers not working ill give it a try latter today
Sent from my SM-N9300 using Tapatalk