Database Users

[UPDATE 22/08/12] ROM Cooking Guide (One Package)

This is how I made ROM, I'll try to write the steps as simple as I can. For advanced users only!
Update 22/08/11:
Revised packaging steps.
Update 13/08/11:
Removed unwanted method for ROM cooking.
Update 04/08/11:
Modified extract and repack ROM guide and added extracting system.rfs guide.
Things you need:
Base firmware
Archiver software (7zip recommended)
Any Linux environment to build ROM or Cygwin
APK Manager to optimize and decompile *.apk files
MagicISO (Optional) if you want to extract system.rfs
And the last thing is... You need enough experience in android world
So, here is the steps to cook a ROM:
Flash your phone with your desired base firmware
Make required modifications
Pull system.rfs from your phone by running this command on adb shell or Terminal Emulator:
Code:
dd if=/dev/stl12 of=/sdcard/system.rfs
Extract any *.tar.md5 files from your base firmware to your working folder with 7zip
Replace the current system.rfs with your modified one
EDIT: Pack your ROM by running this code via terminal or just pack it with 7zip/WinRAR as *.tar
Code:
tar -H ustar -c * >> ROMNAME.tar
change ROMNAME to your desired, well, ROM name.
Here is (yet) useful guide to modify your ROM.
Extract system files on system.rfs to make modding easier:
Extract PDA file (*.tar.md5) files with 7zip
Open system.rfs with MagicISO
To extract it, just drag and drop
NOTE: Never edit your ROM with MagicISO because the file permissions will be ignored, use MagicISO only for extracting files from system.rfs
Deodex, and Zipalign (optimize) your ROM apk files:
Ready to use deodex + root for KPN: http://forum.xda-developers.com/showthread.php?t=1196230
Ready to use deodex + root for KPH and other firmware: http://forum.xda-developers.com/showthread.php?t=1118048
Open APK Manager
To zipalign your apk files, in apk manager folder /place-apk-here-to-batch-optimize put your:
framework-res.apk, twframework-res.apk and all system apk
but not these:
AxT9IME, Calculator, Camera, Email, MMS, Phone, Screen Capture, Settings, Swype, Thinkdroid, Voice search
Choose Choose option 15
Then choose both (zp)
Let it run and done.
Now put back the apk files where they belong in the ROM.
How to put these apk files to my ROM? Copy these files to appropriate locations, such as /system/app to your ROM's /system/app, and etc.
Another handy modification guide:
Unpack and repack boot.img - http://forum.xda-developers.com/showthread.php?t=1173427
Convert firmware filesystem to ext4 - http://forum.xda-developers.com/showthread.php?t=1202049
Overscroll glow for any firmware - http://forum.xda-developers.com/showthread.php?t=1215933"
Give thanks to all dev who made that possible!
If you have more guides to put here, please PM me.

Am I pertamax?
hehe..just kidding.
Nice Info....great share.

I would want the Fla.sh Rom :'(

Thats a gr8 share...Thank you...)

saiftheboss7 said:
I would want the Fla.sh Rom :'(
Click to expand...
Click to collapse
sorry... once again, I'm sorry, I can't continue my ROM

Helpful thread man!
Thanks!

Great job taking your time to make this! Unfortunately, i dont even know the basics but now I know where to check when I do

fla.sh said:
sorry... once again, I'm sorry, I can't continue my ROM
Click to expand...
Click to collapse
Hey!
THX man, nice thread. Very useful!
Just PM to MOD, that they close you previous thread, a bout fla.sh.ROM. Or ppl just waiting it and asking.
CHEERS!

i think the most troublesome problem i encounter is to repack system.rfs. yes it can be mounted in magiciso, but howto repack/compile it back?

an0nym0us_ said:
i think the most troublesome problem i encounter is to repack system.rfs. yes it can be mounted in magiciso, but howto repack/compile it back?
Click to expand...
Click to collapse
Just save it.

didnt work when i just save it. my device got bootloop

an0nym0us_ said:
didnt work when i just save it. my device got bootloop
Click to expand...
Click to collapse
What modification you've added to your ROM? Maybe that modification causing the problem...

fla.sh said:
What modification you've added to your ROM? Maybe that modification causing the problem...
Click to expand...
Click to collapse
As Linux, MagicISO read RFS image as a FAT filesystem. File permissions can not be maintained. A better way but need linux:
1. Mount system.rfs as FAT and mount it to /tmp/rfs
2. Make ext4 image, and mount it to /tmp/system
3. Copy /tmp/rfs contents to /tmp/system
4. Make modification inside /tmp/system
5. Fix file permissions inside /tmp/system
6. Umount both image
7. Make ODIN flashable image, contains system.rfs (now in ext4 format) and CF-Root-S5830 boot and recovery image (for ext4 support)
8. Boot to Windows and flash your new firmware using ODIN.

ketut.kumajaya said:
As Linux, MagicISO read RFS image as a FAT filesystem. File permissions can not be maintained. A better way but need linux:
1. Mount system.rfs as FAT and mount it to /tmp/rfs
2. Make ext4 image, and mount it to /tmp/system
3. Copy /tmp/rfs contents to /tmp/system
4. Make modification inside /tmp/system
5. Fix file permissions inside /tmp/system
6. Umount both image
7. Make ODIN flashable image, contains system.rfs (now in ext4 format) and CF-Root-S5830 boot and recovery image (for ext4 support)
8. Boot to Windows and flash your new firmware using ODIN.
Click to expand...
Click to collapse
I use this command to mount rfs:
Code:
mount -o loop system.rfs /some_dir
Can you share us the command?

now thats really informative. thanks

ROM unpacking and repacking gude has been corrected. Tested by me. If you have any problems, just ask here.
Thanks.

I think you should add the date of update in the title, so that everyone can know about the update...
BTW thanks for this amazing guide...
Love it!!!

After making changes to system.rfs, how to save it as .rfs again?

adiles said:
After making changes to system.rfs, how to save it as .rfs again?
Click to expand...
Click to collapse
Please take look at the first page, it's updated, you know?

After I created md5 file and selected it in odin, it says "invalid image type" and "invalid model binary". How to solve that? After that I continued, skipped these errors and flashed, my phone stopped at boot screen with text "Galaxy ACE....". Plz help me

[ROM]MYGICA ATV580 [TAZPOWN]ROOTED+CLEANED MYGICA FIRMWARE (Geniatech)

Download or cook the PRE-ROOTED firmware for ATV580 (Mygica/Geniatech) Rockchip RK3188 ARM Cortex A9 x 4 CPU.
DOWNLOAD ROM - [ROOTED & CLEAN]
Mygica ATV580 Tazpown Firmware (Build 20131213.20140309):
- Download: ATV580.Tazpown.Firmware.Build-20131213.20140309.zip -
Build Information:
Android 4.2.2 Quad Core Enjoy TV Box
Build Number: 20131213.20140309
Release Date: 2014-03-09
Based Mygica Official Build 20131213.102000
Click to expand...
Click to collapse
Change log:
1.) Based on Mygica Official Build 20131213 Android 4.2.2 (Quad Core Enjoy TV Box)
2.) Removed most Chinese and unnecessary or obsolete applications.
3.) Added su (SuperSU v1.93 06.02.2014) and busybox (Busybox defconfig build for 1.21.1 armv71) Android Rooting Utilities.
4.) Switched External SDCard (up to 32GB) with Internal Flash (only 2GB) Memory. Tested: moving apps to SDCard OK!. You should have an micro SD card inserted on your device.
5.) Fixed Black Screen when playing video with Youtube App.
Click to expand...
Click to collapse
Installation Tips:
For a complete information about how install this rom image, scroll down to the bottom of the post.
COOK YOUR OWN CUSTOM FIRMWARE FOR MYGICA ATV580 - DIY!
You can watch the full tutorial process on this video (this video is a little help, the complete steps its only here in this post).
https://www.dropbox.com/s/88330vv1q3p1pzu/Mygica580-custom-firmware.mov
Original Non-Rooted Mygica Latest ATV580 Stock Firmware (official):
http://www.mygicausa.com/boards/search?searchterms=atv580
Based Mygica Official Build 20131012 Android 4.2.2: https://www.dropbox.com/s/kopamtzdr7gv63d/update20131012.img
Based Mygica Official Build 20131213 Android 4.2.2: https://www.dropbox.com/s/36rkjlf98k47uyc/update20131213.img
1. [ON WINDOWS] Extract Rocket Firmware with imgRePackerRK 1.04
imgRePackerRK RockChip's firmware images (*.img) unpacker/packer. Version 1.04 Windows & Linux
http://forum.xda-developers.com/showthread.php?t=2257331&page=2.
How to unpack a firmware IMG (Windows):
1. Obtain firmware IMG [update.img] and imgRePackerRk [above]
2. Extract imgRePackerRk
3. Open command prompt in directory containing imgRePackerRk.exe [hold shift, right click > "open command window here"]
4. Type "imgRePackerRk.exe {IMG_name}.img" [e.g. "imgRePackerRk.exe update.img"]
5. A new directory called "{IMG_name}.img.dump" [e.g. "update.img.dump"] will be created, containing individual IMGs (system.img)
2. [ON UBUNTU] Mount system.img on Ubuntu and mofify!
Code:
sudo mount -t ext4 system.img system-folder -o loop
2.1. [ON UBUNTU] Rooted Android Firmware.
We use SuperSU. You can get SU and BUSYBOX commands from another Android Distribution compatible with RK3188 devices.
In this case we obtained root commands bin/su bin/busybox and xbin/su Rocket 3188 firmware root tools:
RK3066/RK3188 Development Kitchen/Tool by Rockchipfirmware.com/TNT/FMA
You can also get su and busy box commands from:
Minix Neo X7 Custom Firmware
Code:
[email protected]:~/atv/rk3XXX_mod_tool/ref/bin# cp su ~/atv/system-folder/bin/
[email protected]:~/atv/rk3XXX_mod_tool/ref/bin# cp busybox ~/atv/system-folder/bin/
[email protected]:~/atv/rk3XXX_mod_tool/ref/xbin# cp su ~/atv/system-folder/xbin
Code:
#!/bin/bash
#add needed files
sudo cp -fap ~/atv/rk3XXX_mod_tool/ref/bin/su system-folder/bin/su
sudo cp -fap ~/atv/rk3XXX_mod_tool/ref/xbin/su system-folder/xbin/su
sudo cp -fap ~/atv/rk3XXX_mod_tool/ref/bin/busybox system-folder/bin/busybox
#set permissions
sudo chown root:root bin/su
sudo chmod 6755 bin/su
sudo chown root:root bin/busybox
sudo chmod 6755 bin/busybox
sudo chown root:root xbin/su
sudo chmod 6755 xbin/su
This is everything you need for rooting the system. Later you can download SuperSu from Android Play Store Official.
2.2.- [ON UBUNTU] Removed most Chinese and unnecessary or obsolete applications.]
Code:
system-folder/app/
Code:
rm -rf com.waxrain.airplayer-1.apk
rm -rf eHomeMediaCenter_box.apk
rm -rf Facebook_299369.apk
rm -rf flashplayer
rm -rf Music.apk
rm -rf QuickSearchBox.apk
rm -rf RkApkinstaller.apk
rm -rf RkExplorer.apk
rm -rf RKGameControlSettingV1.0.1.apk
rm -rf RkVideoPlayer.apk
rm -rf WifiDisplay.apk
rm -rf youtube_5.0.21.apk
If you really need some of these apps, I packet them into a zip file so you can install them easily as you need:
Download: Official Mygica Firmware Deleted Apps
2.3. [ON UBUNTU] Modify vold.fstab to mount external_sd to REAL sdcard, so you can get more space for your Apps.
VERY CAREFUL WITH THIS!! Just locate duplicate, comments old lines (for security) and modify:
Code:
/etc# vi /etc/vold.fstab
Code:
#dev_mount flash /mnt/sdcard auto /dev/block/mtd/by-name/user
#dev_mount sdcard /mnt/external_sd auto /devices/platform/rk29_sdmmc.0/mmc_host/mmc0
dev_mount flash /mnt/sdcard auto /devices/platform/rk29_sdmmc.0/mmc_host/mmc0
dev_mount sdcard /mnt/external_sd auto /devices/virtual/mtd/mtd9/mtdblock9
To make the externalised writable, you must edit "platform.xml", from "/etc/permissions" adding in "android.permission.WRITE_EXTERNAL_STORAGE" this: <group gid="media_rw" /> Like this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
2.4. [ON UBUNTU] FIX Youtube black screen (only audio) on build update.img (UPDATE 20131213)
Edit build.prop file, in order to fix Youtube black screen when playing videos:
Code:
sys.browser.use.overlay = 1
2.5. [ON UBUNTU] Umount Custom System folder (system.img) and copy again to Windows.
Umount system image (system.img) and copy back to windows machine, to repack with imgRePackerPk utility:
Code:
umount system-folder/
3. [ON WINDOWS] Build again the new custom firmware
How to repack a firmware IMG (Windows) [Assuming you have followed above to unpack]
1. Open command window in directory containing imgRePackerRk.exe and *.dump directory
2. Type "imgRePackerRk.exe {dump_name}.dump" [e.g. "imgRePackerRk.exe update.img.dump"]
3. New firmware IMG will be created [name will be name of .dump directory without .dump extension]
4. INSTALL ROM ON DEVICE (update.img)
Put the cooked update.img on USB or SDCard, and insert it on Mygica ATV580, then you can apply the update automatically. Your device will reboot and the firmware update will start. The Mygica Bootloader will search for a file called update.img automatically on external_sd micro sdcard. So you should have an micro sdcard inserted on the device.
IMPORTANT: If the Mygica Bootloader show an error like update.img not found when it try to start update process. Probably is because of switched external_sd with internal flash sdcard, probably the updater bootloader won't find the update.img firmware when reboot. This has a simple solution, just manually copy update.img to both, external_sd and sdcard directory. You should need an good tool like Solid Explorer (available en Android Play Store).
IMPORTANT: If the previous method doesn't help you to install the update.img. You can use an editor to switch back to the original mount external_sd and flash sdcard points in /etc/vold.fstab. You should revert the changes on this file. You should need an good tool like Solid Explorer (available en Android Play Store).
IMPORTANT: Before Install this Rooted Original Firmware, remember it is better to RESET DEVICE, so you can make a brand new install cleaning all data files from the previous firmware.
IN CASE OF EMERGENCY (ALTERNATIVES TO SAVE A BRICKED ATV580)!
In case of you brick your ATV580, there is a way to recover it from the dead... Using Android Recovery System. I don't have the full firmware ready for this, but I made some research about how create FLASEABLE ZIP IMAGES for Android Recovery System. So the trick is create a Flashable Zip with our native update.img firmware inside.
To start Android Recovery System, boot ATV580 use a simple clip putting it on a small hole button located an the bottom of the device and connect power supply at the same time during about 5 seconds. Then you can get into this mode, you can use your remote to navigate the menu. In this mode you can load Flasheable Zip loading this files from Computer to SDCARD reader and then to your device.
- Tools and Samples to Build a Flasheable Zip for Android Recovery System (Save your ATV580) rksigner_tazpown-20140324.zip -
This packet include a sample of flasheable zip for Mygica ATV580 that restore build.prop file from a damaged one, which causes the system boot loop and bricked.Just copy the signed Flasheable Zip and use System Recovery System to load it. This flasheable zip fix the system. If you know the problem or you have enough experience to put a right copy of update.img on Flasheable Zip, you can save any bricked or boot loop device, with this tools. You have more docs and information inside of this package.
Screenshots during the flashing process for the sample flashing included in the tools:
- Android Recovery System
- Android Recovery System Flashing my own Flasheable ZIP
Thanks! Dont Forget To PRESS THANKS Button :good:
If you like my work, please consider to invite me a cup of coffee here! ​
​

Hi! You really cool! Thanks a lot!
One question - do you fix it for supporting native 1080p resolution?

jalcot said:
Hi,
finally you can download or cook the PRE-ROOTED firmware for ATV580 (Mygica/Geniatech) Rockchip RK3188 ARM Cortex A9 x 4 CPU.
Thanks!
Click to expand...
Click to collapse
Many thanks for all the work!

I need rooted IMG file.. Somebody help me.. I don't have a PC to cook rom..thanks a lottt
Sent from my rk31sdk using Tapatalk

timothypham said:
I need rooted IMG file.. Somebody help me.. I don't have a PC to cook rom..thanks a lottt
Sent from my rk31sdk using Tapatalk
Click to expand...
Click to collapse
Be parient. I fixed the problem when swap sdcard and flash make it writable. but now I have another problem. When I move apps to SDcard these apps dissapear. I am working arround the solution.
I will get the ROM perfect very very soon.

jalcot said:
Be parient. I fixed the problem when swap sdcard and flash make it writable. but now I have another problem. When I move apps to SDcard these apps dissapear. I am working arround the solution.
I will get the ROM perfect very very soon.
Click to expand...
Click to collapse
Thanks for hard working jalcot. I'm waiting your room with root. I buy ATV580 3 months ago, and can't root it...wait your room.. Thanks again.
Sent from my rk31sdk using Tapatalk

jalcot said:
Be parient. I fixed the problem when swap sdcard and flash make it writable. but now I have another problem. When I move apps to SDcard these apps dissapear. I am working arround the solution.
I will get the ROM perfect very very soon.
Click to expand...
Click to collapse
Thanks for keeping working on it!

Jalcot...where are you... I still waiting you...
Sent from my rk31sdk using Tapatalk

timothypham said:
Jalcot...where are you... I still waiting you...
Sent from my rk31sdk using Tapatalk
Click to expand...
Click to collapse
Yes, thank you for your patient... I've worked hard to cook a perfect clean ROM...

pokatusher said:
Hi! You really cool! Thanks a lot!
One question - do you fix it for supporting native 1080p resolution?
Click to expand...
Click to collapse
Yes! With the new XBMC Gotham Beta I was watching MKV 1080p Movies on my home streaming.

Jalcot...love you so much..you save my Atv... i hate Android no root... i will download rom tonight... thanks your hard work...thank Jalcot again....
Sent from my HTC Sensation using Tapatalk

Great rom Jalcot...thanks so muchhhhhh
Sent from my rk31sdk using Tapatalk
---------- Post added at 12:23 PM ---------- Previous post was at 12:04 PM ----------
I can't use Phone Remote Control Service .. Are you remove it, Jalcot
Sent from my rk31sdk using Tapatalk

timothypham said:
Great rom Jalcot...thanks so muchhhhhh
Sent from my rk31sdk using Tapatalk
---------- Post added at 12:23 PM ---------- Previous post was at 12:04 PM ----------
I can't use Phone Remote Control Service .. Are you remove it, Jalcot
Sent from my rk31sdk using Tapatalk
Click to expand...
Click to collapse
I think so... It is RKGameControlSettingV1.0.1.apk or maybe eHomeMediaCenter_box.apk?
Don't worry, I packed all deleted official apps from the Original Firmware so you can install them easily as you need... You can download them.

Thank so much.. Jalcot..
Sent from my rk31sdk using Tapatalk

I need CWM to install some MOD... Where got it, Jaclcot
Sent from my rk31sdk using Tapatalk

jalcot said:
Yes! With the new XBMC Gotham Beta I was watching MKV 1080p Movies on my home streaming.
Click to expand...
Click to collapse
Launch Antutu and see in System Information real resolution of output, please.Or install small ultility like this and send screenshot

Help me..
Jalcot... can you help me.. plz reup stock firmware for me..
I install PurePerfomes and big bug.. No wifi, no Ethernet detected.. I rollback to your rom but it still bug.. no wifi, no Ethernet... i can't do anything... i hope instal stock firmware will save me...

I can't reinstall your ROM.. I restore factory but it nothing fix.. WiFi and Ethernet is gone... With with me hixhix
Sent from my HTC Sensation using Tapatalk

Everything I have... Not file browser... My ATV is die...
Sent from my HTC Sensation using Tapatalk

Love the clean rooted Rom, many thanks!
Also great job on the internal/external card swap
Gotham latest nightly is still choppy with 1080p content I have but Beyond xbmc 3.3 works great
Thanks Jalcot!

Anyone Please compile LP for T530NU

as the title states please someone i perfer a smart dev here on xda to compile or get the lollipop offical update to work on the TAB4 10.1 SM-T530NU JUST A REQUEST NOT A DEMAND.

LGMONO said:
as the title states please someone i perfer a smart dev here on xda to compile or get the lollipop offical update to work on the TAB4 10.1 SM-T530NU JUST A REQUEST NOT A DEMAND.
Click to expand...
Click to collapse
There are three different cyanogenmod 12 (lollipop) ROMs listed in the development section compatible with the t530nu which are all better than stock anyway. I have the exact same model as you and have been on lollipop for months now and loving it

i understand that, i love and encourage CM and AOSP roms i have used them quite offen however i prefer stock because stock roms utilize the devices features and because there are so many devices the devs dont have time to port stock based apps in there modifications so there for i use stock roms for a daily driver. but i would always support custom roms to anyone as did you. thanks for the reply, would really like to get a stock based lp on the device.
Thanks

LGMONO said:
i understand that, i love and encourage CM and AOSP roms i have used them quite offen however i prefer stock because stock roms utilize the devices features and because there are so many devices the devs dont have time to port stock based apps in there modifications so there for i use stock roms for a daily driver. but i would always support custom roms to anyone as did you. thanks for the reply, would really like to get a stock based lp on the device.
Thanks
Click to expand...
Click to collapse
^^what he said.
I've been checking the forums throughout the day since the LP update came out hoping that someone ported it to the T530NU. Who knows when the official one will come out since the LP update for the T530 has only been released in Spain so far. I doubt it will be released for the T530NU until the update for the T530 is released in more regions.

Dudash said:
^^what he said.
I've been checking the forums throughout the day since the LP update came out hoping that someone ported it to the T530NU. Who knows when the official one will come out since the LP update for the T530 has only been released in Spain so far. I doubt it will be released for the T530NU until the update for the T530 is released in more regions.
Click to expand...
Click to collapse
and @LGMONO
I imagine it's possible to port the official update, here are my thoughts. Take the LP Odin file (the tar file) and open the tar.md5 file in winrar or 7zip. Extract all the files inside (system.img, boot.img, the modem.bin and everything) and make it into an update zip, (with updater-script and everything) but tailor it to be flashable with FlashFire. No idea if it'll work but that's what I'd try if I preferred touchwiz over cyanogenmod.
Edit: On the files you want to pull, I don't think you want to use cache.img or hidden.img, but yeah everything else.

thisisapoorusernamechoice said:
and @LGMONO
I imagine it's possible to port the official update, here are my thoughts. Take the LP Odin file (the tar file) and open the tar.md5 file in winrar or 7zip. Extract all the files inside (system.img, boot.img, the modem.bin and everything) and make it into an update zip, (with updater-script and everything) but tailor it to be flashable with FlashFire. No idea if it'll work but that's what I'd try if I preferred touchwiz over cyanogenmod.
Edit: On the files you want to pull, I don't think you want to use cache.img or hidden.img, but yeah everything else.
Click to expand...
Click to collapse
T, hey hey, you only want the system.img and the boot.img, the issue though is the kernel, my attempts at getting the firmware running "as-is"
fail, [kernel] while i can access through adb i couldn't get a read on logcat even when invoking with full/absolute path
/system/bin/logcat
the sepolicy is covering adb and as i'm learning , sometimes permission denied actually means no such file or directory
and/or the opposite :silly: gotta love android.
m

moonbutt74 said:
T, hey hey, you only want the system.img and the boot.img, the issue though is the kernel, my attempts at getting the firmware running "as-is"
fail, [kernel] while i can access through adb i couldn't get a read on logcat even when invoking with full/absolute path
/system/bin/logcat
the sepolicy is covering adb and as i'm learning , sometimes permission denied actually means no such file or directory
and/or the opposite :silly: gotta love android.
m
Click to expand...
Click to collapse
I know they got a custom kit Kat kernel going for cm11 NU, did anything come of getting that working for cm12 and would that be of use in this instance? (Yeah I haven't checked the thread in a little while because I'm lazy and inattentive)

thisisapoorusernamechoice said:
I know they got a custom kit Kat kernel going for cm11 NU, did anything come of getting that working for cm12 and would that be of use in this instance? (Yeah I haven't checked the thread in a little while because I'm lazy and inattentive)
Click to expand...
Click to collapse
T
hey, you forgot irrepressibly polysyllabic ! xD
okay seriously though, i'm momentarily stumped as to what's going on with my t330nu but later later tonight i'll run a kernel compile and try the t530 rom again.
m

thisisapoorusernamechoice said:
and @LGMONO
I imagine it's possible to port the official update, here are my thoughts. Take the LP Odin file (the tar file) and open the tar.md5 file in winrar or 7zip. Extract all the files inside (system.img, boot.img, the modem.bin and everything) and make it into an update zip, (with updater-script and everything) but tailor it to be flashable with FlashFire. No idea if it'll work but that's what I'd try if I preferred touchwiz over cyanogenmod.
Edit: On the files you want to pull, I don't think you want to use cache.img or hidden.img, but yeah everything else.
Click to expand...
Click to collapse
i tried that lol it didnt work im a .net dev not an android dev i assure you the android devs are much smarter however i did try that method already i purchased ODIN mobile and the device is not supported, when i did try with odin pc version the erro is the aboot and fails im very sure the system will work on t530nu

LGMONO said:
i tried that lol it didnt work im a .net dev not an android dev i assure you the android devs are much smarter however i did try that method already i purchased ODIN mobile and the device is not supported, when i did try with odin pc version the erro is the aboot and fails im very sure the system will work on t530nu
Click to expand...
Click to collapse
Nah you don't want to try this with Odin it verifies what device you have. I say try flashfire instead (chainfire even said FF is intended to replace mobile Odin as well as safestrap) but we have to figure something out for the kernel (boot.img).
@moonbutt74 I was able to flash t530/1 ROMs before anyone started developing NU specific custom kernels, is it not working here because it's an official build or something? Sorry for my frustratingly persistent dearth of knowledge.
moonbutt74 said:
T
hey, you forgot irrepressibly polysyllabic ! xD
okay seriously though, i'm momentarily stumped as to what's going on with my t330nu but later later tonight i'll run a kernel compile and try the t530 rom again.
m
Click to expand...
Click to collapse
Finally another individual understands my irresistible urge to layer on excess syllables with each successive increment of agitation I am provoked to. Also my father is a lawyer (lmao). I'll try some things for this tonight, I don't really expect success (or really anything other than a soft brick) but my curiosity is officially piqued, I'll make this my project for tonight

LGMONO said:
i tried that lol it didnt work im a .net dev not an android dev i assure you the android devs are much smarter however i did try that method already i purchased ODIN mobile and the device is not supported, when i did try with odin pc version the erro is the aboot and fails im very sure the system will work on t530nu
Click to expand...
Click to collapse
L,
hi, this step carries risk, make a backup !!
what you need, from the full firmware img extract system.img and boot.img
pack system.img for odin flash, this is the tricky part, it's one of the following
A- rename system.img.ext4 to system.img
--- then in linux/cygwin cd to the directory where system.img is located
--- run tar as follows
--- tar -H ustar -c system.img > system.img.tar
--- md5sum -t system.img.tar >> system.img.tar
--- mv system.img.tar system.img.tar.md5
or
B- don't rename system.img.ext4 and run again in linux/cygwin
--- tar -H ustar -c system.img.ext4 > system.img.ext4.tar
--- md5sum -t system.img.ext4.tar >> system.img.ext4.tar
--- mv system.img.ext4.tar system.img.ext4.tar.md5
then attempt attempt odin flash, NOT MOBILE ODIN
do the same for boot.img
m

thisisapoorusernamechoice said:
Nah you don't want to try this with Odin it verifies what device you have. I say try flashfire instead (chainfire even said FF is intended to replace mobile Odin as well as safestrap) but we have to figure something out for the kernel (boot.img).
@moonbutt74 I was able to flash t530/1 ROMs before anyone started developing NU specific custom kernels, is it not working here because it's an official build or something? Sorry for my frustratingly persistent dearth of knowledge.
Finally another individual understands my irresistible urge to layer on excess syllables with each successive increment of agitation I am provoked to. Also my father is a lawyer (lmao). I'll try some things for this tonight, I don't really expect success (or really anything other than a soft brick) but my curiosity is officially piqued, I'll make this my project for tonight
Click to expand...
Click to collapse
can you give me a download link to flashfire please i tried searching for this i cant find it ? please thanks

moonbutt74 said:
L,
hi, this step carries risk, make a backup !!
what you need, from the full firmware img extract system.img and boot.img
pack system.img for odin flash, this is the tricky part, it's one of the following
A- rename system.img.ext4 to system.img
--- then in linux/cygwin cd to the directory where system.img is located
--- run tar as follows
--- tar -H ustar -c system.img > system.img.tar
--- md5sum -t system.img.tar >> system.img.tar
--- mv system.img.tar system.img.tar.md5
or
B- don't rename system.img.ext4 and run again in linux/cygwin
--- tar -H ustar -c system.img.ext4 > system.img.ext4.tar
--- md5sum -t system.img.ext4.tar >> system.img.ext4.tar
--- mv system.img.ext4.tar system.img.ext4.tar.md5
then attempt attempt odin flash, NOT MOBILE ODIN
do the same for boot.img
m
Click to expand...
Click to collapse
Thank you i will try this and thanks to all that is participating in this thread.. i have a lg g3 i just updated to lollipop and i like it, but remember for you guys out there newbees so to say at least try and give support for AOSP and Cyan roms i am a huge fan. Give them devs the credit they work hard for

LGMONO said:
can you give me a download link to flashfire please i tried searching for this i cant find it ? please thanks
Click to expand...
Click to collapse
Chainfire said:
- Join the G+ community using the same Google account as you're using for Play on your phone/tablet here: https://plus.google.com/communities/116661625291346007584
- Sign up to receive the BETA versions from Play here: https://play.google.com/apps/testing/eu.chainfire.flash
- Use the link provided after sign-up to download the app. Note that it may take minutes to even hours before the provided link actually works.
Click to expand...
Click to collapse
Link to Chainfire's FlashFire thread: http://forum.xda-developers.com/showpost.php?p=59959596&postcount=1

LGMONO said:
can you give me a download link to flashfire please i tried searching for this i cant find it ? please thanks
Click to expand...
Click to collapse
Here
But try what moonbutt74 is saying first, he's smarter than I. I'm just thinking aloud about all the (probably almost certainly stupid) stuff I'm going to try to get this working

T,
i have a though about incorrect firmware linking in boot.img and /system/etc scripts in the release
to mount and explore the system.img goto directory where extracted image is located and run
simg2img system.img.ext4 system.img
when thats done
mkdir system
mount -o rw -t ext4 system.img system
for the boot img goto @osm0sis 's AIK thread and get the linux package
use that toolkit to unpack the boot.img and check it out, you'll generate two directories after img unpacking,
ramdisk and split-image in split-image directory you will find the kernel and dtb imgs
m

yeah the link on google play is dead lol

nevermind i got it thanks

moonbutt74 said:
T,
i have a though about incorrect firmware linking in boot.img and /system/etc scripts in the release
to mount and explore the system.img goto directory where extracted image is located and run
simg2img system.img.ext4 system.img
when thats done
mkdir system
mount -o rw -t ext4 system.img system
for the boot img goto @osm0sis 's AIK thread and get the linux package
use that toolkit to unpack the boot.img and check it out, you'll generate two directories after img unpacking,
ramdisk and split-image in split-image directory you will find the kernel and dtb imgs
m
Click to expand...
Click to collapse
^^This guy is very smart ^^ i will try that as well i really wanna get these guys the lp for t530nu here in America we are being neglected with the official lollipop update samsung is slacking here i say less talk and more work for them people lol. we would probably all have our lollipop by now. jk

moonbutt74 said:
T,
i have a though about incorrect firmware linking in boot.img and /system/etc scripts in the release
to mount and explore the system.img goto directory where extracted image is located and run
simg2img system.img.ext4 system.img
when thats done
mkdir system
mount -o rw -t ext4 system.img system
for the boot img goto @osm0sis 's AIK thread and get the linux package
use that toolkit to unpack the boot.img and check it out, you'll generate two directories after img unpacking,
ramdisk and split-image in split-image directory you will find the kernel and dtb imgs
m
Click to expand...
Click to collapse
Thanks M I'll get started once I get back from my daily run (I refuse to be a fat American stereotype :silly: )

[Guide] Flashing Firmware on Linux/Ubuntu using Heimdall

Flashing Bootloader/Modem/Recovery etc with Heimdall on Linux
Tested on G930F / G935F
Code:
* I am not responsible for bricked devices
* You are choosing to make these modifications.
Guide for flashing Bootloader & Modem on G935F :
1. Install Heimdall
Ubuntu users can execute the following command in terminal :
sudo apt-get install heimdall-flash heimdall-flash-frontend
Click to expand...
Click to collapse
2. Download the Bootloader & Modem you wish to flash.
3. Remove the .md5 extension (erase .md5 from the name)
4. Decompress the renamed tar files and you will get cm.bin, param.bin,modem.bin & sboot.bin.
5. Place the files in a folder and cd to that folder from terminal . e.g cd Downloads
6. Launch Heimall using :
sudo heimdall-frontend
Click to expand...
Click to collapse
4. Detect device & download device pit
5. Open pit file in heimdall and select partitions CM, Radio, Param and Bootloader specifying location of each file respectively
6. Flash

How do you flash a firmware that's in zip file. .. the same way?? Trying to root sprint s7 with heimdall....

oct01 said:
How do you flash a firmware that's in zip file. .. the same way?? Trying to root sprint s7 with heimdall....
Click to expand...
Click to collapse
Don't do it. Your device has a locked bootloader. This guide is only for G935F.

Thank you

Can I install TWRP this way?

yes, you can install twrp , but its more easy if you use the terminal
Code:
heidmall flash --RECOVERY recovery.img
and it should take less than a minute , all done

Wasted the last 8(!) hours of my life with this crap. Do yourself a favour and just grab a Window$ computer, install Samsung drivers and use the latest Odin -- it took less than 5 min in total.

smoneck said:
Wasted the last 8(!) hours of my life with this crap. Do yourself a favour and just grab a Window$ computer, install Samsung drivers and use the latest Odin -- it took less than 5 min in total.
Click to expand...
Click to collapse
I use Linux for years heimdall v frustratingly hit & miss _ sometimes works sometimes no.pit file printed dodgy USB cables / ports et al one day device recognised next day nothing sadly I have to concur flashing is much easier using Doze and Odin . . .

Just purchaced a Note 3 verizon, Pls suggest best practices to Root & unlock

Hello good peoples of Xda ,
I just purchased a Note 3 verizon I believe 900v on swappa It will arive in the next few day's and I want to get all my ducks in a row by that I mean aquire all the root and unlocking tools nessary for a best practices root and if nessary unlocking of my boot loader.
Goals for root are mostly to debloat the phone and hotspot mod's for no hassle teathering.
I may dip my toes into custom rom for this phone but mostly I am just looking for a clean lean experiance for my note 3. I have been pouring over the many many pages of the various rooting guids and I am just not sure witch method to use is the safest / most reliable .
thank you for your time and helpful suggestions.
This is what I have found so far.
ArabicToolApp : Root for lolipop
Odin3 v3.12.3 : flash tool is this latest ? best to use ?
Samsung usb drivers v1.5.45.0 : are these the proper drivers to install ?

You should start by figuring out which firmware release it has on it.
If it has PL1 (the newest security release, circa 2017/01/15), there will be no rooting for you... unless you manage to create a new exploit.
OB6 and OF1 - (one of) the yemen tool(s)**
NK1 - no root available ( and can't be rolled backwards w/ Odin, only NK1 or higher )
NJ6 - no root available? ( Try towelroot, or you can downgrade to NC4 using Odin )
MI9/MJ7/MJE/NC2(leak)/NC4 - Towelroot v3
For which bootloader unlock binary to use, see here.
Can't help you out with USB drivers, I don't remember what I used. afaik, they will either work 100% or not work at all, so you just need to get something working.
I've never used anything but Odin 3.0.9. Can't tell you if the version you mention is "better".
good luck
** i've never rooted OB6 or OF1, so can't give you any advice about which to use. Feel free to read the related threads. In my (casual) reading of those threads, it is nearly impossible to intuit out why some people have problems and others do not. Mostly because the reporting is not sufficiently detailed.

bftb0 said:
You should start by figuring out which firmware release it has on it.
Click to expand...
Click to collapse
Your right, after thinking about my post I realized there were 2 many variables that I need to know before I ask for help. So once I recieve the phone and if it's fully functional I will find out what firmware it has and what the cid it has and will post a follow up if I need help.
P.S thank you for the concise jist of what is and is not possible with the various firmware's.

Recieved my phone.
I got my note 3 and boy is it just a wonderful device. SM-900v running OF1 firmware, and My Cid is 15 so is all good.
procedurs completed.
I got root from useing the yemem tool.
and have tryed some debloating removed the NFL apk as a test with Tit.backup.
dissabled ota updates, I made a copy of the update.zip (that was downloaded with out me asking it too. I assume that this update.zip is the new PL4 firmware )and deleted it. renamed the fota.apk's with a .bak
not really sure if I should unlock the the bootloader I would love to have twerp.
Could anyone point me at a good debloating script ?
LOVE LOVE LOVE my note 3.
I also have a zero lemon battery/case combo on the way.

PL1 not PL4
See here. Might be dated - stuff tends to move around from release to release.
You should probably also freeze SDM.* and SysScope.* (in addition to LocalFOTA)**
There is a small permanent downside to unlocking - the blowing of the Knox Warranty Flag means that you will never be able to use Knox Secure containers, even if you did a full stock flash with Odin. Not sure how important this is to folks using the phone as a personal device (as opposed to a corporate device).
Operating with a rooted-stock device with a locked bootloader usually progresses through a customary arc - especially with new rooters, but also with experienced folks - where the user one day does some incremental mod that boot-loops the Android UI. At that point there is no means to reverse the small change. (You can't get in via "adb" as it's daemon isn't started yet, and even if it were, the fact that it is in secure mode means that you would have to have a stable UI in order to confirm the connection.) As there is no rooted secondary boot available (i.e., a custom recovery), there is no way to perform repairs, and a trip back to Odin is in store for the owner. Worse yet, a backup has never been made... so all customizations are all lost and must be re-created completely from scratch.
** this is a good idea if you unlock and install a custom recovery: (although TWRP may detect it and emasculate it automatically)
Code:
su
chmod 0000 /system/bin/install-recovery.sh

bftb0 said:
PL1 not PL4
Click to expand...
Click to collapse
Right PL1 ok.
Well I decided in for a penney in for a pound and have sucessfully unlocked my boot loader, had no issues.
my question now is how do I install twerp I have downloaded
twerp-3.0.2-0-hltevzw-4.4
and twerp 3.0.2-1-hlte.img.tar
I think I need to install the tar file.
but I don't know how. I have odin but not sure if that is the right program to use. I think I read where somone installed twerp with flashify or somthing like that.
What should I do ?

Truck'nfool said:
Right PL1 ok.
Well I decided in for a penney in for a pound and have sucessfully unlocked my boot loader, had no issues.
my question now is how do I install twerp I have downloaded
twerp-3.0.2-0-hltevzw-4.4
and twerp 3.0.2-1-hlte.img.tar
I think I need to install the tar file.
but I don't know how. I have odin but not sure if that is the right program to use. I think I read where somone installed twerp with flashify or somthing like that.
What should I do ?
Click to expand...
Click to collapse
man up and use a root prompt command line. It's a single command.
Code:
dd of=/dev/block/mmcblk0p15 if=/sdcard/twrp-3.0.2-0-hltevzw-4.4.img bs=2048
( assuming that you put the twrp .img file in the /sdcard folder. If it was in the download folder, then if=/sdcard/Download/twrp-3.0.2-0-hltevzw-4.4.img )
Note there are absolutely, positively no spaces anywhere in "mmcblk0p15". Critically important.
The above command writes a raw binary data (the .img file) to the 15th partition of the mmcblk0 device - the flash memory chip. You can do this with boot images (such as custom recoveries) or a few other binary images, but typically not with ext4 or other filesystems.
Note this command could be extremely dangerous if you made a mistake. If you were to write data someplace else it could be a permanent disaster. So cut-n-paste to be safest (without a new-line), and then double- and triple- check the command for typos before you hit the enter key.
FYI, you can see what the partition mapping is by doing a folder listing
Code:
ls -ld /dev/block/platform/*1/by-name/*
The partitioning scheme varies from android device to android device; but on the SM-N900V the recovery partition is the 15th partition. (On other devices it might be something different).

bftb0 said:
man up and use a root prompt command line. It's a single command.
dd of=/dev/block/mmcblk0p15 if=/sdcard/twrp-3.0.2-0-hltevzw-4.4.img bs=2048
Click to expand...
Click to collapse
are you talking about adb ?
So somthing like
adb shell
su
dd of=/dev/block/mmcblk0p15 if=/sdcard/twrp-3.0.2-0-hltevzw-4.4.img bs=2048
???

Truck'nfool said:
are you talking about adb ?
So somthing like
adb shell
su
dd of=/dev/block/mmcblk0p15 if=/sdcard/twrp-3.0.2-0-hltevzw-4.4.img bs=2048
???
Click to expand...
Click to collapse
That works.
Or a terminal emulator.
All you need is to put the file on your (internal, pseudo-) /sdcard, "su", and "dd".
For extra credit, make sure to compute a file checksum (e.g. "md5sum") every time you copy the original .img file to a new location and especially prior to flashing. That safeguards against a bad copy operation, crappy flash memory, etc.
Stock ROMs might not have a "md5sum" binary in /system/bin, but since you are rooted you could install a private busybox in someplace like /data/local/bin. I prefer to use a busybox which is SELinux-cognizant, e.g. v1.23.1 here as busybox_full_selinux_1.23.1.zip Note that I don't "install" this .zip so that stuff in /system/bin or /system/xbin get overwritten, but instead just keep it in a private area all on it's own.
Steps.
0) extract the "busybox" binary from the .zip file and get a copy to your SD card. Then
Code:
su
mkdir -p /data/local/bin
chmod 755 /data/local/bin
cp /sdcard/busybox /data/local/bin/
chmod 755 /data/local/bin/busybox
cd /data/local/bin
./busybox --install -s /data/local/bin
This allows it to be used as needed in a terminal/console shell.
e.g. using ls
1) Explicitly: /data/local/bin/ls -lZ *
2) Implicitly "as a last resort":
export PATH="${PATH}"':/data/local/bin'
ls -lZ *
3) Implicitly "as preferred":
export PATH='/data/local/bin:'"${PATH}"
ls -lZ *

I am now have root, unlocked bootloader and twrp Whoot!!
Well I now have twrp installed thank you vary much for all your help and direction I sincerly appreciate your assistance.
I installed termux and after updating the packages sucessfully used dd to install twrp.
1st thing I am going to do a full system backup.

No developer love for N900V not good