[MOD][DIY] 4-way reboot menu - T-Mobile Samsung Galaxy Note 3

Hello everyone.
I figured I'd share this little gem with the community. I hope I am not offending eny devs out there. Most custom ROM's have this option built in, but if someone is using a stock ROM, they are out of luck.
So, first of all, I am not a developer or a programmer, but through the use of XDA forums I was able to acquire some knowledge, enough to get me in trouble, for sure )).
This is based on original work by Clark44 found here:
http://forum.xda-developers.com/showthread.php?t=1769661
The 4-way reboot menu is implemented in a file called android.policy.jar located in system/framework/. Certain custom ROM's have other things implemented inside this file, so I have 2 options for the 4-way reboot menu:
1. modified stock NF9 android.policy.jar in a flashable ZIP
2. smali files that can be inserted into any custom android.policy.jar in order to keep whatever else that's there; these files should be placed in com\android\internal\policy\impl
I will not be providing any explanations in this post regarding SMALI/BAKSMALI. There are plenty of tutorials out there for that. If you know what SMALI is, then you know how use the files in option 2.
Feel free to ask any questions.

I flashed the zip file but no 4 way reboot menu, any ideas why, T-Mobile note 3 5.0 lollipop

These are for KitKat ROMs only. I'm sure there's an update for LolliPop, but I haven't had the time to sort that out yet.

Related

[Q] Adding .apk to custom ROMs

I have been looking through different threads and have yet to be able to answer this question.
Is it possible to:
1) Download [custom rom].zip
2) Open the zip file
3) Remove the .apks that you don't use/want
4) Add personal .apks that you want in the rom
5) Sign it
6) Flash it
w/o causing any problems to the rom?
Yes...its called using dsixdas kitchen
Thank you for answering, I feel like a retard now, I came across this a couple of weeks ago and didn't even blink.
Just in case some one wants to know what dsixdas kitchen is:
[KITCHEN][SEPT. 16 '10] HTC Android Kitchen, v0.91 [Linux / Mac / Windows]
since I can not post links
utb said:
Yes...its called using dsixdas kitchen
Click to expand...
Click to collapse
or you could just use RA as your receovery and open the rom zip in any zip program and add/delete as you like.

Make themes for kitchen

I have trying to get themes to run in the Doc and Stefunel kitchen.
This is a pretty demanding task. Many (almost all) themes can not be used as is due to a non standard resources.arsc and 9.png errors.
There is some theme pro's here.
We like to find a some kind of way to enable any theme inserted in a rom.
Any ideas to make this in a easy way?
/Doc
No one here any ideas? I already proposed someone make a theme kitchen and integrate it with Doc's rom kitchen but apparently all the smart guys that got time and would know how to do that bought a Desire.
Which takes us back at doc's original question someone knows a fail-proof way to integrate themes into roms without having to flash a post-install zip?
Hi Doc,
i know this isnt way you want, but probably it can work:
What about make some script, witch will do:
1) after flashing ROM and start android - reboot android to recovery
2) (i dont know if it is possible) make script for CWM witch will automaticaly flash theme and reboot to system
If Im wrong .. ignore this
schiphol said:
Which takes us back at doc's original question someone knows a fail-proof way to integrate themes into roms without having to flash a post-install zip?
Click to expand...
Click to collapse
I've never need a post-install script to put a theme into a ROM.
Except for the JPY Gingerbread, but me and XGX got that hammered out in the thread in the Captivate forum and it works just fine without a second .zip.
MikeyMike01 said:
I've never need a post-install script to put a theme into a ROM.
Except for the JPY Gingerbread, but me and XGX got that hammered out in the thread in the Captivate forum and it works just fine without a second .zip.
Click to expand...
Click to collapse
Hi, any link to point in right direction is most welcome
I've merely dropped the framework-res.apk and twframework-res.apk into the /system/framework. And any other files like android.policy.jar that goes with it.
For JPY, I had to take a few extra steps:
http://forum.xda-developers.com/showpost.php?p=10258171&postcount=328

[Q] Odex or Deodex?

I am a little confused about the odex and deodex terminology. I am looking at various mods or hacks and I'm afraid I could mess something up because I don't know if I am deodexed or not.
I am on the stock ROM, I flashed chris41's stock kernel repacked with CWM and I rooted by installing zip of su and bb from the market. That is all I have done so far.
With that being said, am I deodexed or odexed?
Thanks in advance
P.S. I did search for the answer but did not find one.
Stolen from matlock and akazabam, rooting guide for dummies
Odexed - In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
DeOdexed - Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity."
this is an excerpt from the rooting guide for dummies. thanx to matlock and akazabam. its their words and not mine.
I think most stock roms are odexed...
Thanks for the info, that helps me not make a big mistake installing the hotspot hack and AIO mod.

[GUIDE] ROM Tweaking

What you will need:
Basic tools
- Notepad++
- ZIP manager tool like 7zip
Advanced tools
- Cygwin
- smali (assembler/disassembler)
- APKTool/APK Multi-tool
Lets Begin:
Download a ROM (we use CM in this guide) of your choice (don’t forget to get the permissions for it modding from the developer) and extract it. When you extract it, you will see at least two folders and one file
Folders
- system
- META-INF
Files
- boot.img [this is not present in defy/defy+ ROMs so don't worry about it ]
NOTE THAT I AM ONLY GIVING DETAILS ABOUT THOSE FOLDER WHICH YOU CAN REMOVE/EDIT
THE \system\bootmenu\2nd-boot\ FOLDER
In this folder you'll find the kernel [zImage] file of the ROM here you can change it with the one you compiled or by others.
The Tts folder
The ‘TTS folder’ is all about Text-To-Speech. It contains all the files needed by the Android system to get Text-To-Speech working. If you are removing the TTS feature from your ROM, make sure you remove this entire folder and the TTS related apps from the ‘system folder’, as this will save a lot of space.
The WiFi and Usr folders
The WiFi folder contains the drivers required by the WiFi module to function. So i strongly recommend NOT to touch this folder. If you delete any file from this folder, you will mess up the WiFi functionality.
The usr folder contains some miscellaneous but very important stuff. It may contain anything and everything needed by the Android operating system. For instance, this folder contains all the key-mapping. If such files are messed with, your device will be non-functional although it will boot.
The Build.prop
The build.prop file is pretty self-explanatory. Here, you can change the most basic things, like the android version that setting shows. Wondered how people are making 2.3.4 look like 4.0.3 in settings? Its build.prop. Also,you can change what ‘About phone’ shows here.
Other things,you can change things like,how long your wifi scans,how much battery your phone saves while in sleep, Dalvik VM heapsize and default ringtones. If you are wondering what # stands for, it signifies that, the particular line is commented out, and the system does not read it. You can use it add comments to the build.prop. This helps others understand, what is the function of a particular tweak.
A guide for some basic build.prop tweaks can be found here.
Please be aware that, these build.prop modifications are not universal. So, you will have to experiment with the tweaks and their values.
The META-INF folder
This folder contains instructions for the Android Recovery about how to work with the files present in the zip. This folder contains many folders, but the only one we need to edit is the update-script file.
Making Flashable ZIP
In order to create a flashable zip, first zip the ‘system, META-INF’ folder and the ‘boot.img’. Let’s name this zip as ‘update.zip’. Next we need to sign the zip. Get a signer here. Put your update zip in the same folder as the signer. Then run the ‘signer.bat’ file. This will sign your zip file. After the signing process is complete, you can change the name of the zip to your liking.
confused
hi,,,i'm new here,,,,
after reading ur post, actually i can't do this,,,
and i installed miui v5 rom and always find crashing about "android process stopped."
and i can't edit the rom or make update of it because of no jnderstanding it, but i like miui so far.
so, can u give me the link of miui v5 rom that not crash, in order to me just to instal it without editting.
thx so much.
gwesal said:
hi,,,i'm new here,,,,
after reading ur post, actually i can't do this,,,
and i installed miui v5 rom and always find crashing about "android process stopped."
and i can't edit the rom or make update of it because of no jnderstanding it, but i like miui so far.
so, can u give me the link of miui v5 rom that not crash, in order to me just to instal it without editting.
thx so much.
Click to expand...
Click to collapse
Checkout my miui thread I have already posted the original link there
D5+/cm11/1.2GHz.
Sent from Tapatalk app
coolshahabaz said:
Checkout my miui thread I have already posted the original link there
D5+/cm11/1.2GHz.
Sent from Tapatalk app
Click to expand...
Click to collapse
which one???
is it the official rom from miui site or edited rom you created??
actually its take too long doenloading from official site. but rom i doawnloaded is always crashing android.process.stopped.
gwesal said:
which one???
is it the official rom from miui site or edited rom you created??
actually its take too long doenloading from official site. but rom i doawnloaded is always crashing android.process.stopped.
Click to expand...
Click to collapse
The one I edited had that prob of crashing, n the one on official site is about 240mb ty its taking time
D5+/cm11/1.2GHz.
Sent from Tapatalk app

[Q] [REQ][HOW TO?] How to theme a system app?

I just recently switched my stock rom to be deodexed and I'm now looking at the possibility of theming and mods for my rom.
I already have a little experience modding the signal icons on a different Android device, and I've already downloaded a mod from this forum that turns part of the stock dialer to a holo dark/material theme, but I want to do more with it.
So far I can't seem to find a good tutorial on how to properly mod system files, especially knowing that the stock rom on the Moto G is a Motorola variant of Android KitKat, and not AOSP or similar, although it's close enough that I figure some mods might work since many Xposed modules for AOSP work fine on my stock rom.
Would it be safe to look for a tutorial based on AOSP 4.4.4, or does anyone know a good place to learn the proper way to modify and theme a Motorola stock rom?
chuman72486 said:
I just recently switched my stock rom to be deodexed and I'm now looking at the possibility of theming and mods for my rom.
I already have a little experience modding the signal icons on a different Android device, and I've already downloaded a mod from this forum that turns part of the stock dialer to a holo dark/material theme, but I want to do more with it.
So far I can't seem to find a good tutorial on how to properly mod system files, especially knowing that the stock rom on the Moto G is a Motorola variant of Android KitKat, and not AOSP or similar, although it's close enough that I figure some mods might work since many Xposed modules for AOSP work fine on my stock rom.
Would it be safe to look for a tutorial based on AOSP 4.4.4, or does anyone know a good place to learn the proper way to modify and theme a Motorola stock rom?
Click to expand...
Click to collapse
get apktool
with this decompile your apks you want to theme/mod
hapy theming! (there plenty of tutorials of how to edit images or the .9 patch files. with gimp etc.. just search )
after that recompile, if you just have edited some images (ressources) pull them afterwards from the new COMPILED apk out in a folder.
take the original apk & open with 7zip & pull the edited stuff into the right directions.
if you have done some advanced modification such as in values folder, you need after the new apk is compiled, open it with 7zip & pull from the original app the meta-inf folder into the new compiled one (singing) after tthat replace it on that phone

Categories

Resources