Hello i search the Orginal Rom from the Samsung Galaxy S5mini SM-G800F but in deodex.
Can someone help me because.
CM11/12/13 I do not like it
whazza83 said:
Hello i search the Orginal Rom from the Samsung Galaxy S5mini SM-G800F but in deodex.
Can someone help me because.
CM11/12/13 I do not like it
Click to expand...
Click to collapse
+1
Deodex your own rom by yourself
pull from system via ADB (usb debugging enabled) -> app, framework and priv-app, put them in a folder named system.
(can also extracted from flashfile, system.img with other tools like ext4_unpacker.exe)
deodexing -> app, framework and priv-app with SVAdeodexer (build.prop needed in systemfolder)
if deodexing finished then copy the three folders on your internal or external storage on device.
now start in to twrp recovery (mount system first), delete in the system folder on phone -> app, framework and priv-app
copy the deodex folder (app, framework and priv-app) to system and set chmod 755.
finger crossed, first time boot after replacing the folders takes several minutes
http://forum.xda-developers.com/galaxy-s5/general/tool-deodex-tool-android-l-t2972025
thanks to svadev
Whit SVAdeodexer odex to deodexing ---- work
twrp recovery mount system and copy ---- work
chmod 755 ---- work ---- but system starting working not
Even after an hour it starts still from new and does not go into the system
Sorry for my bad englisch
try to deodex with lordroid, this java based tool can creating a flashable zip file for twrp
http://forum.xda-developers.com/android/software-hacking/tool-batch-deodex-rom-t3313150
thanks to lord-ralf-adolf
Related
I want to deodex stock firmware (2.36 - XWKTH) and i made the zip file with system folder include 'app' and 'framework' folders.
I can't create update-script for this.
any bady can make me a list of commands For the following? (of course with mount system and what is needed for this)
Code:
deleting .odex files forom app and framework.
copying system folder (in the zip file) to /system
Many thanks!
I'm looking for a deodexed version of the stock Telus/Koodo (Canada) rom for Galaxy Ace. I have the odexed version, but I'm not sure how to deodex. If anyone knows where I can get the deodexed version, or can help me with deodexing, it would be greatly appreciated.
Quietly, THIS IS DEVELOPMENT SECTION and not Q&A or GENERAL, POST IT THERE, here will be posted roms! READ THE XDA RULES BEFORE POSTING -.-
I only know how to deodex on Windows.
First have/download your SG Ace firmware (Canada)
Extract your firmware contents using MagicISO to: firmware_name\system
Download AutoDEOTool1.0.4 (Just a modified version of the tool, including updated binaries)
Unzip it to a directory without spaces e.g: C:\
Move/Copy your firmware's apps and framework files to: _app & _framework
Run AutoDEOToolMain.bat
Hit 2 to be specific.
To find your bootclasspath, just download Terminal Emulator on your Android phone
Run the command: echo $BOOTCLASSPATH
To save it in your sdcard, run: echo $BOOTCLASSPATH>>/sdcard/bootclasspath.txt
Open the bootclasspath.txt, remove any "/system/framework/" codes (without the quotes) then save it
Now copy everything in bootclasspath.txt
Then in the AutoDEOToolMain windows, paste your bootclasspath & hit enter
This will deodex all files in _app & _framework
NOTE: If there are still some odexed files left, then use dsixda's kitchen to deodex the remaining files.
Now copy/move all files in _app to your firmware's /system/app folder
Copy/move all files in _framework to your firmware's /system/framework folder
Now you have a deodexed Canada firmware!
Download these rom_tools and extract it to the root of the extracted firmware (firmware_name)
Now add the boot.img
Zip it and to flash it!
Thanks, I'll try that tonight. What exactly do the rom tools do? I looked at the archive, and I'm pretty sure busybox means root, but what about the rest?
sauron82 said:
Thanks, I'll try that tonight. What exactly do the rom tools do? I looked at the archive, and I'm pretty sure busybox means root, but what about the rest?
Click to expand...
Click to collapse
data folder is optional to include
META-INF folder is to flash the ROM
format.sh formats your Ace/Gio
installbusybox.sh installs busybox
mkfs.ext4 is the tool that format.sh uses
Hello guys,
I tried to port different ROMs to my beloved s plus but none of them booted.
I can install them successfully but when I reboot system it stuck at the boot animation and then doesn't boot.....
What's the problem.
Here is the procedure I'm using to port ROM:
Copy any other file or folder present in the root of the ROM except system,META-INF, and boot.img from port to base
Delete :
Apps
Framework
Fonts
Media
Priv-app folders from base ROM and then copy:
Apps
Framework
Fonts
Media
Priv-apps from port to base ROM.
I go to ../Base ROM/system/etc/permissions/ and delete all files except handled_******** and platform then copy all other files except handled_******** and platform from ../Port ROM/system/etc/permissions to base's permissions folder.
I go to /Base ROM/system/etc/init.d and delete all files except 00banner or 99banner don't know for sure the name of the banner file.
Change the name of the ROM in build.prop with notepad++.
Make archive of the ROM (.zip)
Copy the ROM in the internal storage of s plus.
And then flash it on to my s plus.
I tried to port 4.4.4 and 4.4.2 ROMs from s2 and s4 but without success
I'm using TWRP 2.7.1.0 .
Is there anything I'm forgetting to do?
Please help!!!
Need help!!
Developers please help me out!!
Need help!
Are you having the same issue @shin_no40 ?
sent from my GT-I9001 using Tapatalk app and my fingers
Ask here forum.xda-developers.com/galaxy-s-i9000/i9001-development
Here are some tools I put together to deopt/deodex a system.img
It's been partially tested and works for me, but needs some more testing
I'll continue working on it to fine tune/clean scripts.
Linux Only For Now!
What does this do exactly?
This de-odexes the app, priv-app and framework folders, adds .dex files and lib folders to the appropriate apks/jars and folders, removes odex files and organizes everything into structured folders ready to flash. This does all the work so you don't have to.
Why would I want to do this?
Doing this helps with customization of apks. You can theme the launcher or even replace the lockscreen photos with your own if you choose
This also shrinks the stock system.img to 700+MB
Warning: contains the command 'sudo' for linux root permissions in unpack/repack scripts. Just an easy workaround for now
Instructions:
extract the zip
chmod 755 -R the extracted folder
Add a stock system.img to the extracted folder
run ./unpack.sh to mount the system.img
copy app, priv-app and framework from the 'fugu' folder to the 'system' folder
run ./oat2dex.sh to deodex the 3 folders
remove the 3 folders from the 'fugu' folder
add the 3 folders from the 'system' folder to the 'fugu' folder
run ./repack.sh to build the system.img
Download - auto-oat2dex-fugu_v1.zip
Um I'm familiar with deodex but what's de-opt?
Sent from my Nexus 6
trvbone said:
Um I'm familiar with deodex but what's de-opt?
Sent from my Nexus 6
Click to expand...
Click to collapse
It's de-optimization, which is a method to undo the oat optimized dex. It's similar to deodexing.
awesome thanks, ill test this out tomorrow.
thanks for sharing,
dfl
negamann303 said:
Here are some tools I put together to deopt/deodex a system.img
It's been partially tested and works for me, but needs some more testing
I'll continue working on it to fine tune/clean scripts.
Linux Only For Now!
What does this do exactly?
This de-odexes the app, priv-app and framework folders, adds .dex files and lib folders to the appropriate apks/jars and folders, removes odex files and organizes everything into structured folders ready to flash. This does all the work so you don't have to.
Why would I want to do this?
Doing this helps with customization of apks. You can theme the launcher or even replace the lockscreen photos with your own if you choose
This also shrinks the stock system.img to 700+MB
Warning: contains the command 'sudo' for linux root permissions in unpack/repack scripts. Just an easy workaround for now
Instructions:
extract the zip
chmod 755 -R the extracted folder
Add a stock system.img to the extracted folder
run ./unpack.sh to mount the system.img
copy app, priv-app and framework from the 'fugu' folder to the 'system' folder
run ./oat2dex.sh to deodex the 3 folders
remove the 3 folders from the 'fugu' folder
add the 3 folders from the 'system' folder to the 'fugu' folder
run ./repack.sh to build the system.img
Download - auto-oat2dex-fugu_v1.zip
Click to expand...
Click to collapse
Can you please deodex Marshmallow stock rom for Nexus Player ?
Thanks a lot
Can u provide deodexed all system apps links.
Dear all, I need help im modifying system.img from Stockrom. I can delete apks (de-bloating) but I do not know how to add new apks!
So far I have done the following steps:
1. Untar AP*.tar.md5
2. Extract with LZ4 system.img.lz4
3. simg2img system.img system-new.raw
4. sudo mount -t ext4 -o loop system-new.raw mnt/
5. delete bloatware apps from system/app and system/priv-app
6. add additional apks to system/app and system/priv-app????
7. umount, img2simg, lz4, tar and flash (e.g. Odin)
I have real issues with step 6, everything I tried so far did not work.
a) add apks to system/app and system/priv-app with user root and 644
b) create directories in system/app and system/priv-app
c) replace apks in system/app and system/priv-app
While the de-bloating works, step 6 is broken! The new apps are not usable. They show up with the generic android "robot icon" and their canonical name (e.g. org.fdroid.fdroid...) and are immediately stopped.
What is the correct approach to add additional apks to an existing stock rom image? Please help.