Database Info

[ROM][KERNEL] Hyperion Project - Hyperion 7.x | Pre GM now available!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HYPERION 7​
The fastest and smoothest ROM for Samsung Galaxy Young GT-S5360 yet​
With its easy-to-use interface, amazing features, and rock-solid stability, Hyperion leaves others behind.
And even as others try to catch up, the features built into Hyperion keeps your device years ahead.​
Before you download, please read THIS​
​
Elegant and intuitive interface.​
The simple, beautiful Home screen is the easiest place to start.
From the home screen to every built-in apps in the system, navigation is fast, fluid and effortless.​
Everything you touch is easy, intuitive, and fun.​
​
Amazing features and built-in apps.​
An ever-expanding collection of features and built-in apps make Hyperion even more powerful, innovative, and fun to use.
Here are just a few.​
Would you like to donate?​
Save your money for more important matter! ​
I accept "Thanks" donation!​
Fast, simple and easy ​
If you love Hyperion and wants to support the project
Rate the thread 5 stars​

Features and screenshots
NOTE:
... and we are back! If you read on 1st post, you probably not reading this. If you don't get me, click HERE ​
HYPERION 7 HIGHLIGHTS
PERFORMANCE TUNING
Full GPU (Graphic Processing Unit) rendering for faster, smoother and more responsive system performance
Disabled Journalism (File caching) for faster file read/write
Advanced radio controls for maximum battery saving
ADDITIONAL PERFORMANCE TUNING
IPv4 and TCP Stacks tweak
Secure WiFi Profiling
ISP Restriction tweaks
VPN Support
NOTE:
All above performance tuning are certified real by Hyperion Private Testers and not just written there just to say we updated something.
PERFORMANCE TUNING HIGHLIGHTS
Hyperion Core now fused with Adrenaline Engine for blazing fast performance - Tweak developed by ImbaWind- LINK
NetForks tweak for turbo charged internet browsing experience - Tweak developed by DroidFolks- LINK
FEATURES
UNIQUE FEATURES
No SMS Bug
No false Android version
No copy-pasted app from other ROMS
No paid apps edited to look like a new tweak or mod
No useless features
BASIC FEATURES
De-Odexed
Zipaligned
Recompressed APKS
Optimized APK Images
Rooted
BusyBox and BusyBox run-parts support
Apps2SD enabled
ADVANCED FEATURES
EXT4 File System Support
CIFS
Swap Support
BaCeM Tweak
UnderVolt Support
Firewall Support (DroidWall Open-Source Project)
ENHANCEMENTS
Mobile BRAVIA® Engine
xLOUD™ Sound Enhancement Technology
SRS Wow™ HD Sound Enhancement
Beats™ Audio Enhancement
OTHER ENHANCEMENTS WORTH MENTIONING
Modified PlayStore app
No market restrictions
No auto-update
No useless features
Mother of all HOSTS - more than 27,000 servers blocked
Blocks ADs
Blocks banners
Blocks 3rd party cookies
Blocks 3rd party page counters
Blocks web bugs
Blocks hi-jackers
Blocks phising sites
Blocks Malwares
Blocks Spywares
Blocks Trackers
Blocks un-authorized application connection
WHAT MAKES HYPERION UNIQUE
Savie's special kernel for Hyperion (Savie for Hyperion Project)
UNIQUE FEATURE
No false frequency reading
BASIC AND ADVANCED FEATURES
System-App replacer - I love you savie for this!
All-In-One modules
22 Powerful Governors
5 I/O Schedulers
Supports EXT 2/3/4 File System
Supports UnderVolting and UnderClocking
Supports CIFS (Remote Server-Client file access via Internet)
Hyperion Home - Xperia S Launcher originally modified for Gingerbread by ra3al - LINK
UNIQUE FEATURE
Not a paid app - We know how to code so we don't rely on paid apps.
BASIC AND SUPER LAME FEATURES :laugh:
Desktop layouts: Dock only, 4 Corners, Dock + 2 Corners and Dock + 4 Corners
Iconpack Support: Launcher Pro (Plus) icon packs, ADW Launcher icon packs and Go launcher icon packs
Custom desktop and App drawer row and column grid sized
Desktop folder support
App drawer sort methods: Own icon sort, Alphabetical, Most used and Recently Installed
Settings backup and restore function
Network Unlocker - Modified Galaxy Toolbox v1.0 by Doky73 - LINK
Modified for Hyperion
Remove carrier lock (Unlock)
Restore carrier lock (Re-lock)
Remove bin count (kernel flash count via odin)
NOTE:
The purpose of editing is to keep the sdcard structure tidy and to make sure there is no oddity in Core > Tools for menu items. Launcher and bml15 backups are stored in Hyperion folder in sdcard.​

Installation and downloads
DOWNLOAD
Hyperion 7 Golden Master Final
Filename: HYPERION.7-GM.FINAL.zip
Size: 119.31 MB (125109981 bytes)
Uploaded By: CarlDeanCatabay
Uploaded On: 2012-11-13 12:29:45
MD5 Sum: c8a0b092b53165db700943ba72b885d3
File Desc: Hyperion 7 Golden Master Final Public Build
Virus Status: OK (Clean)
To all Hyperion users,
I got a message from our moderator regarding reports that Hyperion 7's zip package contains root explorer which is a paid app. During testing I added RootExplorer to make debugging init.d scripts easier. Due to excitement and demand for the new build, I forgot to remove RootExplorer and accidentally uploaded a zip package that contains this paid app. Starting today, link to Hyperion will be disabled until a new build is ready. Sorry for the inconvenience and my apologies to Speed Software Developers.
Thanks and Regards,
Carl
​INSTALLATIONFlash Hyperion using STOCK RECOVERY
Go to recovery by pressing the HOME button + VOLUME UP key and the POWER BUTTON
Select WIPE DATA/FACTORY RESET
Select WIPE DATA/FACTORY RESET
Select APPLY UPDATE FROM SDCARD
After installing, reboot your phone
Flash Hyperion using CWM (ClockWorkMod) RECOVERY (UPDATED: 10/24/2012 11:13 AM Arabian Standard Time)
Go to recovery by pressing the HOME button + VOLUME UP key and the POWER BUTTON
Select MOUNTS AND STORAGE
Mount /system
Mount /data
Mount /sdcard
Select WIPE DALVIK-CACHE from Advance and Debugging
Select WIPE BATTERY STATS from Advance and Debugging
Select WIPE DATA/FACTORY RESET
Select WIPE CACHE PARTITION
Select INSTALL ZIP FROM SD CARD
Select SELECT ZIP FROM SD CARD
After installing, press the power button to go back and select REBOOT SYSTEM NOW
NOTES
First boot may take from 1-2 minutes or longer
The first screen you will see is the setup wizard.
The blue circle on the right corner of the status bar indicates that the system is busy (performing media scan, staring services etc etc).
In some cases (if flashed via CWM), the status bar might remain in "busy mode" until you restart your device.
HOW DO YOU KNOW YOU'RE STUCK IN BOOT LOGO? -IF IT STAYS THERE FOR MORE THAN 10 MINUTES. IF THAT'S THE CASE, TRY RE-FLASHING THE ROM OR FLASH STOCK ROM FIRST VIA ODIN BEFORE HYPERION :highfive:​

Installation Troubleshooting Guide
​INSTALLATION TROUBLESHOOTING GUIDE
​In the past days, as we have observed, there had been installation issues for new and existing users. We know how annoying it is to get a bootloop, installation aborted and many installation related problem, so here you go, I will put every single scenario that had been reported and the best solution to install the best (according to users) rom when it comes to performance and style :victory:
Whenever I flash a new build, I have this "one-shot-install" method I am keeping. This one works whether you are jumping from one kernel to another. The one-shot-install step is:
Flash stock via Odin (Recommended)
Format SD Card to remove any unwanted files, orphaned data from previous ROM and of course, junk files.
Copy Hyperion zip package to sd card
Reboot to CWM using TempCWM if you are on stock ROM, or the built in CWM from savie's kernel if you are a previous Hyperion user and skipped flashing stock via Odin
Go to Mounts and Storage and mount /system, /data, /cache and sdcard
After mounting, Go back to main menu using the power button
Navigate to Advance (Advanced and Debugging)
Select Wipe dalvik-cache -this helps you avoid bootloops
Select Wipe batterystats -this ensures your battery gauge gets re-calibrated on first boot
After doing wiping dalvik and battstats, Go back to main menu using the power button
Select Wipe data/reset
Select Wipe cache
After doing data and cache wipe, select install update from sdcard
Select zip from sd card
Select Hyperion zip pacakage and install
Wait for the system to complete installation, it will take 2-5 minutes (maximum) to complete installation
Reboot your device
BELOW ARE THE REPORTED SCENARIOS AND POSSIBLE CAUSES WHY INSTALLATION FAILS​ COMMON FAILED INSTALLATION SCENARIO(S)
SCENARIO 1:
"I flashed Hyperion after flashing stock rom via Odin but every time I use Temp CWM and try to flash Hyperion, it goes back to stock recovery. No error is shown on recovery"
CAUSE OF ISSUE:
Incomplete download.
HOW TO AVOID:
Use a MD5 Sum checker. You can ask our dear friend Google for any md5 sum checker, it's free and it is usually less than 1 MB to download. Always make sure your zip package is intact and complete.
QUICK GUIDE TO CHECKING MD5 SUM:
Open your MD5 checker
Select the Hyperion package you downloaded
Paste the MD5 sum value from the download page in DevHost (MD5 Sum: c8a0b092b53165db700943ba72b885d3)
If it matches, then that means the zip package you have is intact and complete​SCENARIO 2:
"I can't flash Hyperion via stock or CWM, it shows installation aborted"
CAUSE OF ISSUE:
Bad or damaged zip package
HOW TO AVOID:
Check the md5 sum and make sure your zip package is not damaged. If it is damaged, md5 checker will show you MD5 Hash Sum mismatch.​SCENARIO 3:
I flashed Hyperion but nothing happened, I still have stock rom or previous custom rom
CAUSE OF ISSUE:
/system, /data, /cache partitions were not mounted in CWM prior to installation
HOW TO AVOID:
Super duper hyper mega easy; Go to Mounts and Storage and make sure they are all mounted​BOOT LOOP SCENARIO(S)
SCENARIO 1:
"I am using a custom rom and I flashed Hyperion on top of it without flashing stock via Odin. After flashing, my device goes to endless boot loop. My previous custom rom includes a custom kernel"
CAUSE OF ISSUE:
Custom kernel (boot.img) from previous ROM
HOW TO AVOID:
The safest way to install a custom rom (in this scenario, Hyperion) on a device running a different custom rom with custom kernel is to revert back to stock rom first because jumpring from one kernel to another will surely cause boot loops. That is why we always recommend flashing stock rom first before flashing Hyperion.​STUCK AT BOOT LOGO SCENARIO(S)
SCENARIO 1:
"I am using a custom rom with repencis kernel or merruk kernel prior to flashing Hyperion. After flashing Hyperion, I am stuck on boot logo (the samsung galaxy y blah blah screen)."
+
Same scenario above but; "I flashed stock rom via odin, but every time I do wipe data/factory reset and wipe cache, it shows me error mounting rfs blah blah"
CAUSE OF ISSUE:
Both repencis and merruk are known to convert your device's File System (FS) to EXT4. If your device's file system is EXT4 and not RFS (Robust File System), flashing Hyperion will fail, but boot.img (kernel) will be flashed.
SYMPTOMS OF EMMC FORMATTED TO EXT4:
CWM cannot mount /system but all partitions can be mounted
Stock recovery cannot do data and cache wipe
HOW TO AVOID/FIX:
Given your phone is already formatted to EXT4, there is nothing you can do but to repartition your device's EMMC (the chip where we install the device's OS) using Odin.
But remember I have written "but boot.img (kernel) will be flashed"? This will help you in solving this kind of issue.
Please keep in mind that this issue is not a problem with Hyperion rom, if CWM and Stock recovery cannot mount your /system partition, no custom rom can be successfully installed on your device.
Now this is the work around . . .
Since boot.img will always be flashed, that means if the kernel on the rom you are installing have CWM installed, then you will have CWM as recovery.
Now that's a good news because your default recovery now is CWM, and you can use it to format partitions back to its default file system. Follow the steps below:
Remove the battery of your device
Press the recovery key combination to boot into recovery
If you are lucky, you will be able to reboot to CWM (given you flashed Hyperion)
Once you are in recovery, Go to mounts and storage and format /system, /data and /cache
Once format is successful, reboot recovery using the "Reboot recovery" option
After rebooting recovery, mount the partitions and try flashing Hyperion again.

Wireless and Networking Troubleshooting Guide
WIRELESS AND NETWORK TROUBLESHOOTING GUIDE​WIFI ISSUE(S)
WIFI ISSUE 1:
WiFi gets disconnected once phone is locked or the display turns off​
CAUSE OF ISSUE:
Okay, don't panic. This is not a bug. This behavior is the one responsible why you save battery even if you don't turn off your WiFi radio and this is called WiFi Sleep Policy.
HOW TO AVOID:
Currently Hyperion have 3 WiFi policies available in Settings Tab > Wireless and Network > WiFi Settings > Advanced > WiFi sleep policy.​
WiFi Sleep Policies:
When screen turns off - if selected, wifi will turn off automatically when the screen turns off (obviously)
Never when plugged in - if selected, wifi will not turn off automatically when connected via AC or USB port and is getting power from either AC or USB.
Never - if selected, wifi will never turn off automatically - default setting in stock roms
WIFI ISSUE 2:
WiFI cannot connect to any wireless hot spot and/or wireless networks
CAUSE OF ISSUE:
Still UNKNOWN. The dev team are thinking that only production specific GT-S5360 devices are affected with this issue.
Based on user feedback, we are in conclusion that the following might be causing the problem:
Savie's special built kernel for Hyperion
Netforks Tweak
Mother of Host
HOW TO AVOID:
Currently, we have the following fix but not all or even none of the below suggestion may fix the problem depending on your SGY.
A simple reboot will fix the WiFi connection problem
Flashing your device's radio image (baseband) via Odin will fix the problem
Removing NetForks tweak will fix the problem
Removing Mother of Host may fix the problem
QUICK GUIDE TO FLASHING BASEBAND
Open Odin and locate the firmware files for your device
Connect your device to computer using USB Data Cable (USB Cable)
On the PHONE field, locate the MODEM file for your device
Click start to start flashing BASEBAND
NOTE:
You will only flash the PHONE file​
QUICK GUIDE TO REMOVING NETFORKS TWEAK
Using root explorer, navigate to system/etc/init.d
Delete 04netforks_tweak
Using root explorer, navigate to data/
Delete droidfolks folder
Reboot your device
INTERNET ISSUE(S)​INTERNET ISSUE 1:
Cannot open websites and or cannot surf the web​
CAUSE OF ISSUE:
Mother of all Hosts​
For some reason, most of the website that can't load on any browser are website like mediafire, 4shared and other file hosting sites which what they have in common are ADs, Popups, Counters and Surveys. Since MOH is blocking these type of web activities, some webpages may not load. Specially those sites that are configured not to load when their advertisements are disabled by either the browser or internet connection.​
HOW TO AVOID: Thanks to Dr.oidbio for pointing this out​
OPTION 1​
Using root explorer, navigate to system/etc​
Replace hosts file with any hosts file from stock or other custom roms​
Reboot your device​
OPTION 2:
Using root explorer, navigate to system/etc
Open hosts file with text editor and edit the content
Delete everything except​
Code:
[LEFT]#
127.0.0.1 localhost
127.0.0.1 localhost.localdomain
255.255.255.255 broadcasthost
::1 localhost
127.0.0.1 local[/LEFT]
Reboot your device​​CONFIRMED WORKING FIX​​REPORTED BY: AlvaroOrduna
Therefore, I set to work and I solved the Wifi issue (obviously with your helpful guides). So that I wanted to share with you the procedure to solve the problem. Here are the steps I took:​1. Delete 04netforks_tweak from system/etc/init.d
2. Delete droidfolks folder from data/
3. Edit the hosts file in system/etc deleting all except:#
127.0.0.1 localhost
127.0.0.1 localhost.localdomain
255.255.255.255 broadcasthost
::1 localhost
127.0.0.1 local​4. Reflash baseband via Odin
It should be mentioned that I do these steps on flashing zip. I mean, I edit the ROM in the computer and then I install it following the steps in INSTALLATION TROUBLESHOOTING GUIDE. Everything else works fine, but in the future I will continue to watch to see how the phone behaves. If something goes wrong and you do not mind, I will report it.​​

Attribution-NonCommercial-NoDerivs 3.0 Unported (CC BY-NC-ND 3.0)
​Disclaimer
The Commons Deed is not a license. It is simply a handy reference for understanding the Legal Code (the full license) — it is a human-readable expression of some of its key terms. Think of it as the user-friendly interface to the Legal Code beneath. This Deed itself has no legal value, and its contents do not appear in the actual license.​
Creative Commons is not a law firm and does not provide legal services. Distributing of, displaying of, or linking to this Commons Deed does not create an attorney-client relationship.​
This is a human-readable summary of the Legal Code (the full license). Disclaimer​
You are free:
to Share — to copy, distribute and transmit the work
Under the following conditions:
Attribution — You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work).
Noncommercial — You may not use this work for commercial purposes.
No Derivative Works — You may not alter, transform, or build upon this work.
With the understanding that:
Waiver — Any of the above conditions can be waived if you get permission from the copyright holder.
Public Domain — Where the work or any of its elements is in the public domain under applicable law, that status is in no way affected by the license.
Other Rights — In no way are any of the following rights affected by the license:
Your fair dealing or fair use rights, or other applicable copyright exceptions and limitations;
The author's moral rights;
Rights other persons may have either in the work itself or in how the work is used, such as publicity or privacy rights.
Notice — For any reuse or distribution, you must make clear to others the license terms of this work. The best way to do this is with a link to this web page.
Developer Conditions:
Any ported version of this rom for any device must be released under the name "Hyperion" or any name as long as "Hyperion" is present.
Ported version must have the same logo in Settings > System.
A link to this thread is required.
Hyperion Project in HTC Mania​

Preview - Work In Progress
"Do you even know how to theme apk?"
Hyperion 7.x with Hyperion Home 2.x
​

The Dev Team
The Hyperion Project 2012​Devs I thank the most on this project:
b16h22 - Father of EVO-X; the grand daddy of Hyperion
savie - the guy behind Hyperion's Core Power - Savie For Hyperion (SFH) Kernel​Other Devs and their contributions:
ra3al for his amazing work on XPERIA S Home Launcher with Settings | 0.9.2c
DroidFolks for Netforks Tweaks for all Android 2.3.6 - 4.1.2 devices​

Hyperion 7.x Pre GM ​
NOTHING NEW, JUST THIS:
More smoother UI - Project Butter Hyperion style | Speed and stability will always be a priority and not eye candy :angel:
Tamed Mother of all Host - not sure though if it's Grandma Host on this package, but who cares? Host file is less agressive now and this will solve problems with sites (specially file sharing sites) not loading.
UPDATED
Graphics driver for smoother gaming experience.
Some libs and *I think some modules as well.
ADDED
Sound Theme - Linda Sounds Mod (the most complete set).
FIXED
WiFi Issues - caused by Multi-CSC mod that affects WiFi banding depending on the market where your device was officially released. In future I might include CSC + WiFi CSC editing so you can take control of WiFi banding (device <-> router connectivity).
Tick/Untick bug in some checkbox item(s) in settings - might also be region related problem.
Most black text over dark background (some are still present because they don't depend on framework/SystemUI)
BACK FROM THE DEAD
I know you missed the good old TouchWhiz Launcher, so here it is, old guy new look
WHAT'S IN IT:
Holo style dock, home and app drawer buttons
9-12 home screens
5-icon dock support
Grid and List view in App drawer
Support AppShare in app drawer
Random icon background support (currently list view only)
Opacity tweaked to match the overall transparency of UI
DEFAULT CONFIG:
3 Home screens
1 Widget: Google search + voice
4 shortcuts on default home screen
5 icons in dock
App drawer icons arranged alphabetically
App drawer in grid view
DOWNLOAD
Filename: HYPERION-7.x.zip
Size:114.63 MB (120203331 bytes)
Uploaded By:CarlDeanCatabay
Uploaded On:2012-11-30 02:34:16 MD5
Sum:5f37a325cffc4c5f409eaba2e5825d76
File Desc:Hyperion 7.x Pre GM Build
Virus Status:OK (Clean)
Note: Use virus status as a reference, rescan with your own Anti-Virus.​

TRANSLATING HYPERION​TOOLS YOU NEED:
Any apk tool for decompiling and recompiling like APK Tools, APK Manager and APK Changer Alpha 11 - APK Manager and APK Changer Alpha 11 are the one I'm using. Take note, it's alpha 11, not the latest version of APK Changer.
Notepad++ - a GNU editor you can download from HERE
WHERE TO GET THEM:
APK Multitool - http://apkmultitool.com
APK Changer - http://forum.xda-developers.com/showthread.php?t=1189971
APK Tools - I don't know where to get it. Ask dear Google.​HOW TO SETUP YOUR TOOLS:
I advice you use APK Changer as it has an automated setup where you can configure this tool as you install it.
Follow the installation/setup steps for the tool of you choice
After that look for C:\Users\<User>\apktool\framework folder. Ex: C:\Users\Carl\apktool\framework
Take framework-res.apk and rename it to 1.apk
Take twframework-res.apk and rename it to 2.apk
Copy 1.apk and 2.apk to C:\Users\<User>\apktool\framework
HOW TO TRANSLATEPREPARE APKS
In this example, we will modify Settings.apk and translate it to Spanish language.
Take Settings.apk from stock ROM that supports Spanish and rename it to Settings-ES. If your language is not Spanish, then of course you need to take Settings.apk from stock rom for you region which support your language.
Take Settings.apk from Hyperion. You don't need to rename it. Leave it as it is.
DECOMPILE APKS
Once you have all the needed APKS for modding, place it inside the folder designated by the tool you're using for decompiling. In this example I am using APK Changer, so I will put Settings.apk and Settings-ES.apk to C:\Apk-Changer_alpha11\place-files-here-for-modding folder
Open your tool, in this case it is APK Changer. If you installed this already prior to preparing APKS, then you should have the main menu where you have the option to decompile/compile.
Decompile both Settings-ES.apk and Settings.apk
TRANSLATE/ADD ADDITIONAL LANGUAGE TO APK
After decompiling apk, look for the "values" folder inside the decompiled APK. In this case I use APK Changer so I will navigate to C:\Apk-Changer_alpha11\out\Settings\res
You should to the same for Settings-ES and open it in another folder so you can view both folders side-by-side
You can simply take "values-es" folder from Settings.apk and copy it to Settings\res
After copying folder, open Settings\res\strings and add the values present in Settings.apk's res\values\strings.xml to "values-es" folder.
After that, compile your APK and now you have a translated version of APK.
Do this for every app you want to be translated.
OF COURSE MOST OF US ARE LAZY AND ONLY KIND ENOUGH TO TRANSLATE, SO I'LL POST HERE THE FILES YOU NEED TO EDIT AND TRANSLATE AND IF I HAVE TIME AND I AM NOT FEELING LIKE A LAZY MONKEY, I WILL BE THE ONE TO COMPILE THE APK FOR YOU.​NOTE:
Only strings.xml and arrays.xml values needs translation. You only need to translate values inside
Code:
<string name="[COLOR=Red][B]alert_mesage_recipients[/B][/COLOR]">[COLOR=SeaGreen][B]Alert message recipients[/B][/COLOR]</string>
<string name="[COLOR=Red][B]text_you_should_not_translate[/B][/COLOR]">[COLOR=SeaGreen][B]Text you should translate[/B][/COLOR]</string>
Example:
<string name="alert_mesage_recipients">Alert message recipients</string>
You will translate "Alert message recipients"
You should NOT translate "alert_mesage_recipients"
Translated example:
<string name="alert_mesage_recipients">Alerta destinatarios del mensaje</string>​GET FILES HERE
SETTINGS.APK​

CarlDeanCatabay said:
Yes. To check that, navigate to:
/sd-ext/ using root explorer, you will see there:
app
app-private
dalvik-cache
lost+found
To check if deep sleep is working, navigate to:
Settings > Core > CPU States
NOTE:
Deep Sleep starts when phone is idle, if your phone is running for 2-4 minutes from boot, in some cases you will not see deep sleep state in cpu states info. That is normal.
Click to expand...
Click to collapse
i dont know anything abt a2sd plz can u tell me after making the partition what should i do so all the apps and dalvik cache is installed in the partition thanks quick reply will be appreciated
btw i am loving this rom
and is there any way the to change the status bar toggles order

CarlDeanCatabay said:
Yes. To check that, navigate to:
/sd-ext/ using root explorer, you will see there:
app
app-private
dalvik-cache
lost+found
To check if deep sleep is working, navigate to:
Settings > Core > CPU States
NOTE:
Deep Sleep starts when phone is idle, if your phone is running for 2-4 minutes from boot, in some cases you will not see deep sleep state in cpu states info. That is normal.
Click to expand...
Click to collapse
alright.thanks

@CarlDean : No Statusbar tweaks and Widget button, so how do we edit stat bar and add or remove some toggles on 14 toggles?

Solehria said:
i dont know anything abt a2sd plz can u tell me after making the partition what should i do so all the apps and dalvik cache is installed in the partition thanks quick reply will be appreciated
btw i am loving this rom
and is there any way the to change the status bar toggles order
Click to expand...
Click to collapse
Ooops! Seems like I forgot to put QuickToggle in Settings > Parts. I'll create a patch and will attach it here later. Sorry about that, I was too excited to release the ROM

CarlDeanCatabay said:
Based on yowskee's test, RAM usage is about 130-140 MB and he can play Zenonia 4 at 170MB used at most. But i need others to test that.
Click to expand...
Click to collapse
You made my day downloading & flashing

CarlDeanCatabay said:
Ooops! Seems like I forgot to put QuickToggle in Settings > Parts. I'll create a patch and will attach it here later. Sorry about that, I was too excited to release the ROM
Click to expand...
Click to collapse
plz can u tell what i have to do about a2sd after making a partition

if possible add stat bar tweaks...i dont want to see AM and PM on clock

plz people help me what should i do after making the partition

Please, have present the Kernel Savie #73 not run in all model S5360. In variant S5360X not worked.

Solehria said:
plz people help me what should i do after making the partition
Click to expand...
Click to collapse
Please follow the instructions in my Link2SD for dummies on how to partition your SD Card.

🔥 READ ME FIRST [FAQ][HTC][PICO/EXPLORER][a310e]🔥

"Those, who fail to read history are bound to repeat its mistakes"
People here have and did and will fail to read the things here and many did and many probably will have to lose their devices. You don't have to lose a device to get knowledge inbetween your ears.You don't have to be stupid. You surely can learn from your mistakes. But There's a better way. You can learn from others mistakes. This thread is a compilation of such mistakes ,that I personally have done and many others ,who did and their solutions aka The easy ways.
So, officially I congratulate you for finding this thread and reading Upto here. So, even if you don't read the whole thread, these are the main stuff you must know is
1. Rooting is a dangerous process -done by developers only. If you did root your device, you assume full responsibility for your device. So, if you can't think like one of the developers at least partly, I suggest you don't root your device ,coz when you mess up, the one who deviced the procedure or Rom will not help you. And everything you find here is in "AS IS " tag.
2.If you have rooted, next thing you must do is backup-
Go to recovery,
go to backup and restore
click backup.
I find it strange that this is not included in the root procedure. This surely would've helped a lot of Picos out there.
3.NEVER DO A RUU
-It unanimously holds the number ONE title for the major causes of bricking of Picos.
Trust me -Surely you can save your device, without the ruu. And with ruu, you're bound to fail without proper knowledge and research.
The only time you are suggested by experts to do a ruu is when you have already done a ruu "and" bricked it.
4. Overclocking here may cause burnt nand. -know what Rom you're using-it may have built in-overclock .
However, overclocking doesn't necessarily produce burnt-nand for all devices.
5.Finally, Not all answers you receive in the question and answer thread are good. Some answers will kill your device. So please judge the credibility of the answerer before you follow the answers. Generally, you could track back their previous answers and their working. Thanks meter is a good source of credibility -but not always -Not all who have big thanks record are helpful neither are they knowledgeable-There are spammers, who trick people into giving thanks.Do your home work before you trust a stranger. Recognized developer title is a good source of credibility.
The above five should save you a lot of trouble.
Ever in trouble? Drop by and read.
Do your googling,if you don't understand anything here.Have a great time !

Re: [faq][newbies only][mini edition]
��To start, this thread is only for newBies,who have rooted thier Rom and have a custom recovery. If you haven't, click here
Alright, this thread aims to answer all the frequently asked questions by newBies. The section this thread aims to answer will consist mostly of custom Roms especially cyanogen.
To start, we'll start with basics
Our phone consists of the following five partitions
1.Boot/kernel
2.Recovery
3. System/Rom
3.1What's not working
3.2 Latest links
4. /cache- error /last log
5.Data
5.1Scripts
6.Common issues after flashing Rom, scripts/GAPPS/PLAY STORE /
Ram
7. USB and CPU ,screen and power button-2/7/13
8. About developers and members
9. ��Burnt nand*recovrecovery 25/6/13 *��
10. STILL CAN'T FIND THE ANSWER ��
10.1LOGCAT
10.2ADB
11.MINI TIPS AND TRICKS
11.1CM9/10 themes
11.2.FONT CHANGING AND language तदधा ಥಮು support adding
11.3.DID YOU KNOW?
12. Recommended apps
13. BATTERY LIFE AND PERFORMANCE
14 .http://forum.xda-developers.com/showthread.php?p=38098604
BUILD. PROP TWEAKS
We'll discuss the faq in each.
All links are here
Index:
http://forum.xda-developers.com/showthread.php?t=1754876
This is the best link you'll ever have
Thanks hrkh83
Guides
http://forum.xda-developers.com/showthread.php?p=36057579
Guides for everything
Thanks hpsgill
Make yourself useful by akshat
Seen it before,
Just read this now
http://forum.xda-developers.com/showthread.php?p=37805872
Stock Roms instead of bricking ruu
tk immortal yash
http://forum.xda-developers.com/showthread.php?p=39101954

Re: [faq][newbies only][mini edition]
/BOOT(4 MB Max )
1.what does this partition contain?
It contains your kernel
2.what is kernel?
It's a in betweener between ROM (/system ) and your hardware.
Basically, a software, which connects the main software (your Rom gui) and the hardware
3 .what is the stock kernel version?
2.6
4. Is there a update available?
Yes. You can update it to 3
3.4 is currently being worked on
5.what are advantages of kernel 3 ?
Nothing much that you can feel
Basically related to stability, security, and future Android Os updates can easily be done for a310e
5.where are the links to kernel 3 ?
Look down
6.what's not working in kernel 3 ?
1.Ext4+kernel 3+mount2SD/s2e/link2SD doesn't work.
2. CPU states file reading ~fixed in overclocked kernel ~fixes yet to be fully implemented across RomS [overclock may cause burnt nand/recovery ]
With cm9
1.Firewall
2.USB tethering
3. Wi-Fi hotspots
4.Vpn
Anything related to iptables
With cm10
Known issues
Ext4 cannot be mounted?
Temple run 2 and subway surfers reboots*fixed in overclocked kernel *burnt nand *
7. What's not working in kernel 2 ?
garuda v5
Data usage option in settings in jelly bean.
8.what's not working in kernel 2.6 sakindias cranium kernel?
Build #2
Lag
Build #3
No support for Android native a2SD
Build #4
Same as build #3,but advertised as faster
9. I wanna make my own kernel?
Special thanks to bhargz16
http://forum.xda-developers.com/showthread.php?t=2114594
10.Is there a overclocked kernel?
Yes
http://forum.xda-developers.com/showthread.php?p=38098604
11. How to Flash kernel? Do I need to clean install?
No need to clean install
Copy zip to root of /SD card
Go to recovery
Install zip from SDcard
Choose the correct zip
Install
Reboot
Go back to main ^|^

Re: [faq][newbies only][mini edition]
/Recovery(5 MB Max )
First thing to do after root is to make a nandroid backup.
Go to backup and restore and select backup
1.what is this partition?
It contains your recovery
2.what is recovery?
It's a specialized partition for Android, which is used when something goes wrong.
We use it to change (flash) Roms, change kernels and mostly everything in xda. Make nandroid before you mess up
3. What are the recoveries available for a310e ?
1 .yannou90 (cwm5) recovery
2.Twrp 2 .3 by cute prince
3. twrp 2.2 by oblikas
4.cwm6 by sakindia
5.*OFFICIAL *The latest TWRP by bhargz16( http://forum.xda-developers.com/showthread.php?t=2123503 )
6.cwm6 by nihar.g
Links .check index link in top post
4. Are all of them stable?
The 1 and 5 are pretty stable.
What's not working:
cwm6 by sak let me down big time .
http://forum.xda-developers.com/showthread.php?p=38734554
Except 1,all other recoveries will not show charging animation, when you are charging your phone after switching it off ~instead of charging animation ~you'll be going to recovery
twrp official - some problems with ext4 partition has been reported and also reported to have been fixed. -I never had the problem before and after and I recommend this one 2.5 present here in xda.
twrp cute prince has issues restoring backups (problem with symlink )
5.what's the difference between them?
cwm5 - complete backups of all partitions
twrp - support compressed backups /file manager and other great things
cwm6 - your SD ext partitions will not be fully backed up during subsequent backups,but only the changed files greatly reducing the size of subsequent backups
6. Can you explain more about cwm ?
http://forum.xda-developers.com/showthread.php?p=38100620
7. Recommended apps.?
Recovery file manager aroma 1.8
8. How to flash a recovery?
Two methods described in detail in link above by bhargz16 ~ fast boot
Flash from phone:
Required:
Flash_image binary
You can flash any recovery
From terminal using
Code:
su
flash_image recovery /sdcard/recovery.img
You need recovery.img (renamed like that ) present in /sdcard itself
9. Error while restoring .Androidsecure /sdext ?
http://forum.xda-developers.com/showthread.php?p=39874898
10. Cannot go to recovery /burnt recovery /unable to flash recovery?
Use
Code:
fastboot boot recovery /sdcard/twrp5.img
or
Code:
fastboot boot recovery.img
or
Code:
fastboot boot /sdcard/twrp5.img
You need twrp5.img or recovery.img present in /SDcard and renamed like that itself.
After booting into recovery, you can do everything you please. ~flash erase format and install new Rom and boot the device
After booting up the device, flash erase mtd1 through terminal emulator.and then flash a suitable small recovery. And then pledge here that you'll never overclock ever again.
Go back to main ^|^

Re: [faq][newbies only][mini edition]
/SYSTEM (235 MB Max )
1.what is it?
Here's where your Rom resides
Any cyanogen /ever/miui roms all go here
2. What are system apps
Any app in /system /app is system app and they have special permissions
2.1 how to make a app system app?
Uninstall the app with titanium backup and copy it's apk to system/app(normal delete apk will not delete. Dex and lib files ) ~reboot ~
Some apkS need it's library file also in /system /Lib (copy from /data /Lib to /system /lib )
3.what is binary?
These are executable ~very important files in /system /bin. (or /xbin in recovery)
Your root su is here
4. What are the roms available?
Many roms are available in xda
Main line ones are
CYANOGEN 7
CYANOGEN 9
CYANOGEN 10
Cyanogen 10.1
Miui
5.What is cyanogen 7 ?
It's a cyanogen version of gingerbread
9 is ics
10 is jelly 4.1
10.1 is jelly 4.2
5.1 what's the development going on?
cm7 *camera was unable to be fixed *development stopped
cm 10*active development now *
cm 10.1 *thread closed *
6. How to install a new Rom? Cyanogen for example?
Download the latest build. Zip and put in the root of /sdcard.
Go to recovery
Factory reset data
Wipe cache
Wipe dalvik
Wipe SD ext
Choose install zip from /sdcard and choose the build. Zip
Wait
Reboot
Go back to main ^|^

The nothing really bugs list
Welcome to THE "NOTHING REALLY" BUGS™
This is the official nothing really bugs Pico web post at xda. Its name implies that the bugs present are really nothing to some people. But to the rest, it may bother a lot. So, this post.
Here you'll find most of the nothing really bugs. All statements having "Nothing really " in bugs list directs here. This is to inform new flashers of what they'll get and what they won't. To make the facts clear,so that you won't have to flash every Rom to find out all the nothing really™ bugs. After all, this is a newbie friendly thread.
Please note that though every effort has been taken to ensure an exhaustive list of all the bugs .Some may not have been stated here .If you do find a bug, which isn't stated here, please feel free to mention it here and I'll add it after being personally confirmation by me or two to three renowned senior member witnesses. Further more, some bugs here may have been fixed. You can take a look at the last edited day of this post to make sure this post is up to date. And you can mention it here,if any of the information found here is wrong.
1.What doesn't work in cm10 4.1 Jelly beans ?:
1video (video recording with some third party apps~Skype video messaging, zoom camera ,camera magix and a lot more)(S. ucam works fully)
2Bluetooth headphones can't be used during call(try using sound about )✘
2.1 Bluetooth stereo headphones ✘
3vsync
4.stock camera force close often and unstable (S. Camera 360/ucam)
5.Wi-Fi unable to turn on ~from settings /notification bar. (s:Flash kernel 2.6)
6.burnt nand
7. Wi-Fi direct (native )causes reboot. (S. 3Rd party app ~fast file transfer)
8.some VOIP~{ex:gtalk(even after normal gapps),and many more}
9.Most streaming video{not flash, but those, which open in mx} doesn't work. Most TV apps don't work (not flash using tv apps)
10. mobile data may fluctuate for some(timedo app to turn on and off airplane mode for every hour)
11. calls robotic call for some
http://forum.xda-developers.com/showthread.php?p=32997468
12. Unofficial adobe flash is flickering too too much. (Only Firefox actually works with flash..which flickers unbearably ~the rest don't even work )
13. Headphones volume control during in call✘
14.USB tethering (native)✘
15. Wi-Fi hotspots work only as open source ✘
16.Bluetooth A2dp streaming ✘
17.Firewall rules don't stick, when put in init.d. Somehow the Rom process overtakes the firewall rules during boot and during some process. My intuition directs the blame at bandwidth controller| throttle service~|Data usage settings|which wasn't implemented properly, but using dirty hacks
18. USB mtp and ptp not working at all. USB mass storage not working for certain devices ~double mounting. (s.flash kernel 2.6 with USb mass storage fix here. )
19. Multi mount SD app doesn't work [s.flash kernel 2.6]
OTHERS
1. Battery drain
2.Phone heating
3.WiFi toggle
Total :22[Because, I used this Rom for a long time,so the large number]
✘- Unconfirmed by me .The rest are personally tested and confirmed "not working " and again confirmed to be a problem of Rom itself.
2.What doesn't work in cm9 ?
forum.xda-developers.com/showthread.php?p=35756952#post35756952
2VIDEO PLAYBACK doesn't work as well as stock
3 Wi-Fi toggle in latest RomS
4 Bluetooth stereo headphones ✘
Experienced by some:
A. Encryption doesn't work (crypt)✘
B.robot call http://forum.xda-developers.com/showthread.php?p=32997468
C.mobile data flickering
Note: video playback is much better in cm10.
Language rendering is also much better in cm10.
3.what doesn't work in Original HTC STOCK ROM?
A. if you ever click "reset to default" in the Camcorder settings..,all future video recordings will overwrite already taken videos and all previous videos will be lost(use ucam)
B. sending a more than 150MB file on Bluetooth file manager app through Bluetooth will reboot your device.
(use stock transfer)
3.1 what's not working in a rooted stock Rom?
(make a nandroid backup first to protect you)
Optimize storage in storage settings
Factory reset will put you in bootstruck.
4.What doesn't work in cm10.1 ?
Camera and lot more minor/major
Too long list
Will update when usable
5.what doesn't work in cm7 ?
Camera
6.what's not working in kernel 3 ?
1.Ext4+kernel 3+mount2SD/s2e/link2SD doesn't work.
2. CPU states file reading ~fixed in overclocked kernel ~fixes yet to be fully implemented across RomS [overclock may cause burnt nand/recovery ]
3.Wi-Fi toggle from notification bar /from settings
4. USB mtp and ptp not working at all. USB mass storage not working for certain devices ~double mounting.
5. Multi mount SD app not working.
With cm9
1.Firewall
2.USB tethering ✘
3. Wi-Fi hotspots ✘
4.Vpn ✘
Anything related to iptables
With cm10
Known issues
Some partitions [?Ext4] cannot be mounted
*burnt nand *
With latest cute prince kernel [power management fix ]:
Mounting of SDcard on some devices
Multimount SD app
7. What's not working in kernel 2 ?
garuda v5
Data usage option in settings in jelly bean.
8.what's not working in kernel 2.6 sakindias cranium kernel?
Build #2
Lag
Build #3
No support for Android native a2SD
Build #4
Same as build #3,but advertised as faster
9. Sense4 Roms
1.Burnt nand ~most common ✘
2.Random reboots ✘
3. WiFi direct. ✘
4.Bluetooth headphones ✘
Go back to main ^|^
✘- Unconfirmed by me .The rest are personally tested and confirmed "not working " and again confirmed to be a problem of Rom itself.
S - probable third party solutions
Solutions for burnt nand -Please go to burnt nand section.

[COLOR="RED"]Welcome to [b]▶LâTêS†↭ⓛⓘⓝⓚⓢ™◀[/B][/COLOR]
Welcome to ▶LâTêS†↭ⓛⓘⓝⓚⓢ™◀
Not sure whether it'll be updated,but galaxyfreak released a app on latest Roms ~ http://forum.xda-developers.com/showthread.php?p=38913186
Why this post ?
Because index has only thread links and sakindia123 never updates op
If he does, then this post will not be updated anymore. Other than that, here are some kernel links as well. Other than the main line ones, the others are not updated. Sense4 links are already present in op and here as well http://forum.xda-developers.com/showthread.php?p=40111838 . Any link that's not present in op will only be updated.
1.what's the latest build on cyanogen 9?
Build 13
http://forum.xda-developers.com/showthread.php?p=36626369
#14*beware of burnt nand *
http://forum.xda-developers.com/showthread.php?p=38770875
2.what's the latest build on cyanogen 10 ?
Build 3.2.2.use with kernel 2.6
http://forum.xda-developers.com/showthread.php?p=38183817
Liverpool fan latest 3.2
http://forum.xda-developers.com/showthread.php?p=38447868
Beta 5~beware of burnt nand ~
Video fix by bhargz*liverpl 4 beta5*
http://forum.xda-developers.com/showthread.php?p=39124906
http://forum.xda-developers.com/showthread.php?p=39090779
Beta6~beware of burnt nand ~
http://forum.xda-developers.com/showthread.php?p=39166124
+
http://forum.xda-developers.com/showthread.php?p=39804373
(Flash this to prevent overclock)
Lock screen fix for both beta 5 and 6 .
http://forum.xda-developers.com/showthread.php?p=39043840
2.1 Aokp build link
http://forum.xda-developers.com/showthread.php?t=2208242
3.what is the latest build on cyanogen 10.1 ?
Alpha 3
http://forum.xda-developers.com/showthread.php?p=38094629
Alpha 4
http://forum.xda-developers.com/showthread.php?p=38325531
4.what's the latest build on kernel?
Old Kernel 3
http://forum.xda-developers.com/showthread.php?p=36572115
Kernel 3 v2 only for sense
http://forum.xda-developers.com/showthread.php?p=38466559
http://forum.xda-developers.com/showthread.php?p=39730163
Kernel 3 v2 for cm10
http://forum.xda-developers.com/showthread.php?p=39737920
http://forum.xda-developers.com/showthread.php?p=39804373
5. Is there a overclocked kernel?
http://forum.xda-developers.com/showthread.php?p=38098604
kernel 2.6=garudav5kernel
6. Kernel 2.6 for JB ?
http://forum.xda-developers.com/showthread.php?p=37649737
http://forum.xda-developers.com/showthread.php?p=36303556
7. Kernel 2.6 for ics?
http://forum.xda-developers.com/showthread.php?p=35797210
http://forum.xda-developers.com/showthread.php?p=36526379
http://forum.xda-developers.com/showthread.php?p=37550173
8. Side effects and solution of using kernel 2.6 on a kernel 3 based Rom:
http://forum.xda-developers.com/showthread.php?p=39452607
Basically, USB storage may not work.
To, make it work, Flash the fix attached with this post(don't remove battery @ any stage:sly-tested on my twrp 2.4.4 with cm10beta5.May not work with ics.
Alternatively, you can use multi mount SD app /root tool box lite app.
Attached zip md5: 8216eaf4a357b9cddc5cfd29b8d05a50
Attached zip sha-1: 408a075479745fe1713f8c55a968801f7f6160dd
Some more links :
http://forum.xda-developers.com/showthread.php?p=40964578
Super wipe zip
http://forum.xda-developers.com/showthread.php?p=38338418
Nand recovery procedure:
http://forum.xda-developers.com/showthread.php?p=38098622
tk to akshatshenoy.
Flashing an older ruu:
Not recommended @ any stage
http://forum.xda-developers.com/showthread.php?p=38694608
Even if it works,you might have problems data, battery drain etc.. if you Flash a wrong radio
KERNEL RAMDISK exchange on Android itself:wip
AUTORAMDISK™ EXCHANGE PROJECT alpha™
http://forum.xda-developers.com/showthread.php?p=40035607
How to install kernel? Clean?
http://forum.xda-developers.com/showthread.php?p=38098513
QUESTION NUMBER 11 ABOVE
Go back to main ^|^

Re: [faq][newbies only][mini edition]
/DATA (150 MB )
1.WHat's this?
It is the internal memory
2.Why is it important?
Because this is the place where all the apps go
No /data = no more apps
3.what's our available internal memory?
150 MB
User available 90 MB
4. Any way to increase internal memory?
By scripts
5 .Recommended apps to diagnose application not installed
Diskusage app
Log cat
6. What does a app contain?
App when installed splits into apk dex,and data(lib+data) files
Go back to main ^|^

Re: [faq][newbies only][mini edition]
SCRIPTS
Before we start, a app when installed takes space as three parts.
They are apk,dex and data (lib+app data)
All scripts work by symlinking
1. What are the scripts available for our explorer?
Partial scripts
A.Link2SD app
Moves apk,dex,lib~doesn't move app data
B.Root data2SD app
Need ext partitions
Moves application data2 ext
Full scripts--Need init.d support able to move fully /partially as per requirements
Links available in index
1.Mount2SD
Download from play store or from here check index
Famous for it's stability and frequent updates
Issues +
2. Int2ext
As per script, moves partially /fully .
Has a large user base
issues ++
3.s2e
Moves fully.
Issues +++
NO official version for jelly beans.
4.a2sd darktremor
Issues ++++
However works pretty well with stock Rom and jaggy Rom
Discontinued
5.ungaze script
Issues +++++
I don't recommend it.
Why not?
Because
http://forum.xda-developers.com/showthread.php?p=33750812
http://forum.xda-developers.com/showthread.php?p=31915607
1.1 mount2SD doesn't work? Script not executed fully @ boot?
Flash kernel 2.6 from above and you should be good to go.
2. How do I increase internal memory (literally ) from 150 MB to 2GB(for example SD ext )?
Use mount2SD reverse mount
Use int2ext
Side effects:
As per Android rules, 10% of internal memory will be unavailable
So, 200 MB out of 2GB SD ext will be unavailable
Mount2SD also has normal moving methods ,which will make Android think you'll have 150MB but you can fill up 2GB inside of 150 MB (Here 10% would mean 15 MB)
3. I installed d2ext/similar ,I'm not able to install more apps ,even though I have more SD ext space?.
A. First make sure you don't hit 10% data limit described above
B. Use diskusage app to determine,which partitions are full
For example- some scripts don't move dalvik and so dalvik will fully accumulate in /data creating no space.
C. Fix permissions from recovery, wipe cache and dalvik and reboot.
4. My Rom doesn't have init.d support /I'm using stock Rom?
Check index
You can add init.d support by
Flashing custom kernel (cranium)
Flashing scripts to make init.d support (or pimp my Rom app[not tested])
5. Where to add scripts before flashing Rom?
Add it in /system/etc/init.d (permissions are rwx rwx rwx ,if you're adding this in recovery after flashing )
For mount2SD add configurations folder in /data/m2sd.
6. How to migrate from link2SD to mount2SD?
http://forum.xda-developers.com/showthread.php?p=38840247
7. Is there a full script so that I can use both my internal memory and SD ext?
A bit complicated, but this what I use...
Configure mount2SD
To move both apk and dalvik
Don't move data.
Then open titanium backup to move app data
@First move one app data to create data2SD directory.. then you can batch move whatever apps you think fit.
But please make sure you have at least 10 to 30 MB in /data and in/SD ext (SD ext not necessarily ) before a nandroid backup. Otherwise restoreS will not work.
Go back to main ^|^

Re: [faq][newbies only][mini edition]
Common issues with scripts:
0. Device stuck @ HTC logo with 4 error icons on all four corners
Since you flashed an ruu and failed user data fail etc.
Unlock bootloader if possible
Flash twrp recovery again
Code:
fastboot flash recovery.img
Then go to recovery with this command
Code:
fastboot boot recovery
Now that you're in recovery wipe everything, format everything .
If flashing failed /you can't enter recovery, do this keeping twrp recovery.img in /SDcard
Code:
fastboot boot /sdcard/recovery.img
Do cute prince recovery procedure shown in burnt nand section
Flash erase mtd3 as well
Now Flash your Rom and boot
If it doesn't boot, repeat the whole procedure above and now
Do ruu.
If all the above failed,
http://forum.xda-developers.com/showthread.php?p=39181288
Read the above thread fully. That's the last resort.
Moral : Don't ever Flash an RUU (if you haven't already )
You can Flash stock Rom ~safer
1. Device struck in HTC logo
Wait for 15 minutes
Try pulling out battery and reboot
Update busybox and try installing scripts again
Convert your partition to ext3
Change your kernel to 2.6
2. Mount2SD ~apps update after every boot?
Turn cache off in app
Turn safe mode off
Clear cache and dalvik ~fix permissions ~reboot
Common issues after flashing:
1. I get status 7 error?
Open archive with Bluetooth file manager and check archive integrity
Try different compression method(thanks hpsgill)
Delete system apps
2. I get status 0 error?
Update binary used is different
Exchanged update binary from a working zip to this one
Other errors can be cured by changing recovery .
http://forum.xda-developers.com/showthread.php?p=38469360
Common issues after flashing Rom:
1. Always do a clean install
To wipe everything except /sdcard.
Even in /sdcard delete Android /data after backup
2. No I won't listen. I want to do you a dirty install. Show me how?
Your choice
http://forum.xda-developers.com/showthread.php?p=35903694
3. I get force closes of all apps?
Dalvik problem.
Clear cache and dalvik cache and reboot
4.I get force close of a specific app?
If it's a paid app, then you need to change your Android id to your original Id with Android id changer /titanium backup
Not a paid app?
Clear cache and data of that app and reboot
Fix permissions
5.reboot after reboot?
Thanks bhargz16
Kernel problem. Change kernel
GAPPS:
1. This gapp always force closes?
A. If it's a gapp found on play, just uninstall that gapp from system using titanium backup and then reboot and install from play store.
B.if not found on play, then try flashing a different gapps version from goo.im .
Make sure you have enough space on /system and on /cache before flashing and then flash. If not delete unused apps like stock keyboard ,etc
2. RPS5~AEC0/927/any other error while downloading apps from play?
A. Clear data cache of play store app
Reboot
B. Clear data of google services framework
Reboot
C. Remove your google account and re add it. Reboot.- this worked for me.
3. All my apps are missing from installed apps in play?
Wait for some time,if you've flashed a new Rom
Clear data and cache of play store
Reboot
Download app eric market fix *use @ your own risk *
Repeat the solution of questions 2.
Go back to main ^|^
Part 2 on next page :thumbup:

Re: [faq][newbies only][mini edition]
CPU:
1.Can you overclock?
IMO,
All overclocking burns nand.
It's just a matter of sooner /later.
Read this post before attempting anything
http://forum.xda-developers.com/showthread.php?p=38445346
Burnt nand recovery procedures here ~~the third post below this post
http://forum.xda-developers.com/showthread.php?p=38098622
The links below are old. All latest Roms come with overclocked burning kernels.
cm10:
http://forum.xda-developers.com/showthread.php?p=38189883
cm10.1:
http://forum.xda-developers.com/showthread.php?p=38336080
gpu oc
http://forum.xda-developers.com/showthread.php?p=38331698
cpu oc
2. Governors ~what are they?
As the name says they govern when the cpu should go to higher speed and when they should sleep
Performance governor always keep your phone at Max
Powersave keeps your cpu always at low
USB :
1. Flashed kernel 3 and USB doesn't work.?
Flash kernel 2 back.
2. I want to know how to fix USB +kernel 3?
Don't know
3. Can I have usb otg ?
No, not yet.
SCREEN AND POWER BUTTON and soft keys:
1.SCREEN turns on after turning off ?
A. Some apps are trying to make screen on. After screen turns on, go to settings immediately and open running applications, you may be able to find the culprit. It's probably the app, which is restarting. Some apps like lock any app screen etc. Logs could be helpful.
B. Some users reported it could be a hardware problem -look below for power button issues.
C. Some users reported it could be a script problem (rare )
2. My home screen button and /or search buttons doesn't work?
A. Did you do a dirty install of new Rom
Clear cache and dalvik and fix permissions and reboot
B. Copy com.Android.providers.settings /databases from your previous nandroid backups(use yaffs file manager /nandroid manager)and paste it in it's respective location now (paste it using file manager in recovery )
C. If that doesn't work, clean install again
Tech savvy? ~search for device provisioned 1 in cyanogen forums
http://forum.xda-developers.com/showthread.php?p=38633404
3. Power button doesn't work properly ?
A. If it's not a software problem(try the above solution first),then you broke it.
If you broke it, avoid using the power button anymore-use attached scripts indeed.
There are apps in market to simulate power keys.
Or
http://forum.xda-developers.com/showthread.php?p=38633404
Go back to main ^|^

Re: [faq][newbies only][mini edition]
Miscellaneous topics:
Subject to change without prior notification
Developers:
1. Who are the developers that make these roms?
1. Cute_prince
2.sakîndia123
3.derefas
4.lirokoa
5.liverpool fan
6.bhargz16
7.nihar.g
8.ngolralph
And many others. The above are the developers of the roms that I used and present in no order.
2. Why doesn't sakindia123 update the OP ?
Disclaimer: Since it is one of the most faq by newbie,I'm forced to discuss here. I personally do not know sakîndia. If you still want more info, contact senior member hpsgill
You see.. He does nothing without reason. If he doesn't, then the last build present in op will be more /less equal to the latest build. There are other reasons ,which if I had to speak of them all, time wouldn't let me and I would have to deal with flaming members and mods and deleted posts and locked threads . Furthermore that question is well out of the scope of this thread. You are instructed not to ask this question any where.
YOU HAVE BEEN WARNED.
3. How can I contact these developers?
You can by studying Android development and codes, bccms,404s,tr2s and then talking to them. You'll have better luck talking with non recognized developers than the rds.
And try discussion threads .
4. Why doesn't a developer answer my question? (I'm being polite here)
Because the developer doesn't know the answer
w.r.f to http://forum.xda-developers.com/showthread.php?p=38095857
Or your question has already been answered. Try searching for your question at the least 10 pages back.
or your question is too silly to answer
Or your question is not seen ,because they don't have time .
5. Why do they do this ?
For passion of development, addicted, and for learning purposes.
So, that means they don't work for you. They don't help you. They do what they want.
6. I feel a emptiness around forum members. Was there a developer who worked here, yet left without goodbye?
Well not sure about goodbye, but yes his name is jaggyjags.
sakIndia123 came only late and his first work his cranium kernel, which he abandoned like it was nothing.. buried it along with jags. Cruel things did happen before you were here.
Go back to main ^|^
Members:
1. Why won't members answer my question?
Again, thanks to bhargz16
http://forum.xda-developers.com/showthread.php?p=38095857
Or question has already been answered over and over again. Try searching for your question and read at the least 10 pages back.
Or they don't want to help you
Or may be you aren't polite
Or they want thanks
2. Why do they want thanks?
You see.. you should hit thanks for them in order for them to reply
3. Why hit thanks?
Because they are thankaholics .
This addiction
Some call it want,
For some it's need
Some call it greed
And some call it hunger
And some childish foolishness
Never hit thanks, unless you mean it. Never sell yourself short. Mean it, then hit it.
http://forum.xda-developers.com/showthread.php?p=32867800
My first thread closed by mods
:crying:
Having said that, please do be grateful for what you receive. Hitting thanks is like giving a eternal reputation mark on them rather than just saying it. Saying just makes a temporary mark. Get it. 
4.what is spam?
Spam is going out of topic . It never should be done in dev threads unless thread is dead.
Some do the work of mods pretending to be mods.
5.who are mods?
They are moderators who have power to ban anyone at will (in short )
And they are losing patience
http://forum.xda-developers.com/showthread.php?p=37950595
6.Can I spam here?
Feel free to speak what you want..
7. If I feel something wrong is going on /flaming /threatening, who should I report to?
You can use the report system~that (!) mark over every post. Click it and your issue will be resolved within a hour(probably ).
Go back to main ^|^

[color="red"] [b]
0110…380“30…4010¨¨1WELCOME TO NAND/recovery BURNT ZONE 0110…380“30…4010¨¨1
0„30†2Moved by touch0160†640„30†3Inc.
0110…380“30…4010¨¨1DON'T FLASH AN RUU AT ANY STAGE 0110…380“30…4010¨¨1
0. What's burnt nand?
It's condition caused by overclocking(oc)[CPU oc ,to be specific. For gpu oc,go to the last part of this post question 10 ] resulting in bad blocks all over your system, data, cache and recovery.
Important: Use diskusage app to determine size. Don't go by phone's inbuilt settings
A case of burned /system partition in cm10 beta6 running overnight:
Uploaded with ImageShack.us
A late case of burnt nand of /data :
Uploaded with ImageShack.us
1 &2:Not applicable anymore. Peace!
3. No one has burnt thier nand*it's just some people think that thier nand is burnt * is this true?
Well, I'm sure, going through the forums and q &a ,I know that people have indeed burnt thier nands and some just by using the overclocked kernel without even overclocking.
Sources:
http://forum.xda-developers.com/showthread.php?t=1847002&page=400
http://forum.xda-developers.com/showthread.php?t=2243719
http://forum.xda-developers.com/showthread.php?p=39985385
http://forum.xda-developers.com/showthread.php?p=39799173
http://forum.xda-developers.com/showthread.php?p=39439861
http://forum.xda-developers.com/showthread.php?p=39428922
http://forum.xda-developers.com/showthread.php?p=39402187
http://forum.xda-developers.com/showthread.php?p=38941663
http://forum.xda-developers.com/showthread.php?p=39216556
http://forum.xda-developers.com/showthread.php?p=38945489
http://forum.xda-developers.com/showthread.php?p=39197918
http://forum.xda-developers.com/showthread.php?p=39169697
http://forum.xda-developers.com/showthread.php?p=38657723
http://forum.xda-developers.com/showthread.php?p=40616272
http://forum.xda-developers.com/showthread.php?p=39331139
But below is a strong correlation with bad block proof between overclocking and burnt recovery. Yes it burns recovery too.
http://forum.xda-developers.com/showthread.php?p=39196574
THE ABOVE LINKED POSTS ARE MOSTLY SOLVED BY ME OR SENIOR MEMBER S, BUT SOME HAVE LOST THEIR DEVICES. IF YOU CAN'T FIND THE ANSWER HERE, I SUGGEST YOU READ ALL THE LINKED POSTS-VARIOUS DIFFERENT METHODS HAVE BEEN EMPLOYED.,WHICH ARE TOO LONG TO EXPLAIN HERE. READ AND READ-YOU'LL FIND.
4. What are the symptoms of burnt nand?
Early symptoms:
You'll notice a strong drop in your free space in /data
Late symptoms:
/data free space is Nil /below 50%of what you saw before
Error in /cache /recovery/log.
Error in /cache/recovery/last log.Not readable.
No apps can be installed
Rom lags like hell
No Rom can be flashed /boots
Previous nandroids ,which are successfully restored before fails to restore now.
Really abrupt and fast restores with twrp
RUU cannot be done ~user data(mtd5) fail. System fail (mtd3)
5. How can I diagnose burnt nand early?
If you suspect burnt nand ,
1.Watch out for free space in /data and watch out for sharp reduction.
2.Download this app Disk Usage and watch out for increase in system data in /data
http://forum.xda-developers.com/showthread.php?p=39464989
3.Make a dmesg and look for these errors
http://forum.xda-developers.com/showthread.php?p=36834988
4.Definitive method is this :
shahrooz_ra said:
hello
is there any linux terminal command for check badblock on nand memory?
Click to expand...
Click to collapse
1.DOWNLOAD THE TERMINAL.ZIP ATTACHED BELOW
2.EXTRACT TERMINAL.ZIP INTO /SDCARD/lol [create a folder named lol[small letters ]in SDcard, if there already isn't one ]
3.Open terminal emulator on your phone
4.type or copy and paste this code and press enter
Code:
su
cp /sdcard/lol/runme.sh /r.sh
chmod 0755 /r.sh
/r.sh
5.if it doesn't work first time, paste twice.
6.If pasting twice doesn't work, type each code one by one -you'll surely get it. Come on-its just 4 lines -type it lazy!
And Now you'll see the number of bad blocks you've got.
You can also Flash the zip below[for which you have to go to recovery ]or execute the attached script badblocks.sh as root.
6. What are the parts affected by burning?
Proved to affect
/Data
/system
/cache
/recovery
Rest is unknown
7. Ok I managed to burn my nand What are the recovery procedures available?
I SIMPLIFIED THINGS HERE BY MAKING A FLASHABLE FLASH_ERASE. ZIP[Code named FLASH_ERASEmadeflashablebyBANNED.zip ] it works with twrp2.5 to flash_erase needed partitions. However not tested fully. Problem? Post here.
Other long procedures:
Cute prince recovery procedure:
http://forum.xda-developers.com/showthread.php?p=36868966
I think Cute prince missed this .Just add this at the end
Code:
./flash_erase -N /dev/mtd/mtd3 0 0
7.1 I GET FLASH ERASE NOT FOUND?
Flash the flash_erasemadeflashablebyBANNED.zip
Derefas recovery procedure:
derefas was the one who actually gave the idea of recovering nand
http://forum.xda-developers.com/showthread.php?p=36867557
Sachin Thomas recovery procedure
Developed lately *can be done on phone itself */if it didn't involve recovery /*
http://forum.xda-developers.com/showthread.php?p=38941897
Recovery recoveriNG procedure (bhargz16)
http://forum.xda-developers.com/showthread.php?p=39198068
8. I can't find my answer here?
Go to official burnt nand discussion thread
http://forum.xda-developers.com/showthread.php?t=2183130
Or you can ask your questions here.
9.can I Flash any other kernel to prevent overclocking?
You can Flash garuda2.6
Link in latest links post page 1.
http://forum.xda-developers.com/showthread.php?p=38098567
Side effects:
http://forum.xda-developers.com/showthread.php?p=39452607
10. Some more links:
Unknown recovery procedure
http://forum.xda-developers.com/showthread.php?p=36836090
MTD status report:
http://forum.xda-developers.com/showthread.php?p=36837173
11. Cannot go to recovery /burnt recovery /unable to flash recovery?
Not sure of the exact command,but will work.
Use
Code:
fastboot boot recovery /sdcard/twrp5.img
or
Code:
fastboot boot recovery.img
or
Code:
fastboot boot /sdcard/twrp5.img
You need twrp5.img or recovery.img present in /SDcard and renamed like that itself.
After booting into recovery, you can do everything you please. ~flash erase format and install new Rom and boot the device [do ruu here, if you haven't been able to enter hboot before]
After booting up the device, flash erase mtd1 through terminal emulator.and then flash a suitable small recovery. And then pledge here that you'll never overclock ever again.
12. GPU OC ?
gpu oc has been reverted along with CPU oc by sak for burnt nand. But may be added later. but not present in cm released on or two months before 9 may13.
12.1 is it safe?
I don't know. CPU oc did provide burnt nand and bad blocks. Gpu oc may also do some things, which may not be seen as of now. I've seen one case complaining that, after using Cyanogen and going back to stock - games started lagging, which did not lag, when he was in stock before. The reliability is doubtful. But not much people go back to stock either -so not much can be said.
12.2 do you recommend it?
"If any provider of any oc removes the "AS IS" tag and take responsibility,if something happens, then I'll probably may use that oc,otherwise count me out".
12.3 How to remove gpu oc ?
Its present in kernel. Flash another kernel. Or modify source and compile yourself.
Present at arch/arm/mach-msm/msm7x27a.c- kernel source.
Try here
Normal [bus, Gpu] is [0,133330000],[160000000,192000000],[200000000,245760000] I think.
13. Was there anyone unable to recover and lost thier device for ever?
AFAIK,
"The lost thier device for ever list RIP "
Ghostking
Hawk378
And May be many more
Legend *:
Attachment list:
***********************************************************VERY IMPORTANT : UNDER CLOCK BELOW 300MHZ ,IF YOU ARE USING ZIPS WHILE SYSTEM IS RUNNING.AFTER THE TESTS, YOU MAY OVER CLOCK AS YOU WISH. ********************************************************************************************
Provided "AS IS"
1- script to detect badblocks by banned.
2-flashable zip to detect badblocks by btfb0
3-Terminal method to detect bad blocks by banned .
4-flashable zip to detect bad blocks by banned.
5- Recovery procedure to delete bad blocks- Made flashable by BANNED.
All zips posted here has readme.txt files inside it-which are self explanatory to that particular zip.
*USE AT YOUR OWN RISK*

Re: [faq][newbies only][mini edition]
I have a question not answered here?
Post your question in the q&a section after making sure that your question hasn't already been asked.
Please use search button on the top right to make sure that your question hasn't already been asked. And it'll help you to find more answers.
Follow detailed instructions here
http://forum.xda-developers.com/showthread.php?p=33608527
And post with logcat increases your chances of resolving the problem
ADB
What is logcat and ADB?
Special thanks to akshat.shenoy
http://forum.xda-developers.com/showthread.php?p=37805872
He'll explain things better
Basics of ADB:
http://forum.xda-developers.com/showthread.php?p=9936674
Partition and wipe SD ext with ADB:
http://forum.xda-developers.com/showthread.php?p=38706881

Re: [faq][newbies only][mini edition]
reserved

Re: [faq][newbies only][mini edition]
MINI Tips and tricks:▶?
1.How can I apply cm9/10 themes?
http://forum.xda-developers.com/showthread.php?p=35530897
Download the zip from here, read instructions there and flash it in recovery
Now you can use any HDPI themes on your Pico
Thanks ngoloralph
2. How do I change fonts?
Download Rom toolbox lite and go to font installer;
A. If you're on stock, the rest is automatic
B.if you're on cyanogen 9/10/11,if you change the droid sans /others as recommended by app, you'll end up in boot loop (possibly because of symlinking of robot sans & droid sans )
In such a case go to preferences and click to overwrite only roboto regular font and everything will be fine.
Take a look
Uploaded with ImageShack.us
3. How do I add a new language support to my device?
Note: no new language gui can be added by this method. This only adds support. Instead of seeing boxes, you may see your language. If you want full language support, you can go to this abandoned thread.?? http://forum.xda-developers.com/showthread.php?p=40890599 ??
Language support can simply be added by adding a Android supported language font file in /system /fonts and give it permissions rw r. r.(font files can be found all over xda )
Step 2. Open system /etc /fallbackfonts.xml...
There should be a lot of font file names there.. just delete a font name that you don't want and add your font file name (the name of the file which you put in /system /fonts)
In there.
Practice makes perfect.
This method however doesn't work /only partly works for complex languages /script like Hindi Arabic etc.
DID YOU KNOW?
1. Long pressing reboot button (in the menu after pressing power key) will get you into safe mode
2. Long pressing power keys and volume keys + and- for more than 30 seconds will reboot your device (tk to hrkh83)
3. Repeatedly pressing certain options(like Android version) in the about menu in settings(on cyanogen ) will take you into different settings (tk liverpoolfan)
Go back to main ^|^

Battery drain
BATTERY DRAIN
Of course, we're gonna talk about drain.
Before we start, I want to disprove some prevalent concepts
1. Battery calibration
It is supposed to increase Battery capacity and increase Battery life and it makes your phone to show the correct Battery on the notification bar.
FALSE
It doesn't do any of those. Calibration is just deleting Batterystats.bin file. That file holds info about how many seconds each apps were running for.typically it's blameometer. It shows the information you see in the battery chart in your settings. Nothing more.
Source: article
2. Cycling your battery life from 0 to 100 and 100 to 0 will typically increase Battery life. Further more you should make sure it comes to zero by turning on the phone,every time it got switched off on it's own.
FALSE AGAIN
Nothing could destroy your Li-On Battery than extreme low voltage. You can be sure that this will destroy your battery life more than anything. During storage it's recommended to keep the battery in cool place with 40%Battery.
So, don't use any battery draining app from market.
Ok, since we took out the false foundation, it's time to put some true working tips to save your battery during usage and it's overall life
1. It's recommended to charge as often as possible ~every time you get a socket. Though not to keep @100 all the time. Overcharging theoretically may damage your battery, but your phone comes with various safety mechanisms to prevent charging after that.
2. Limit the number of apps. Definitely would produce good Battery.
3. Limit the number of apps, that run in background all the time.
Typical example would be facebook.
PERFORMANCE:
4.Disable autostarts for all apps, that you don't use much~using autostart manager.
Disabling autostarts for the clock app will make you get up late. Use common sense.
This alone should drastically improve your performance
5.Use lightweight launchers ~Nova.
Go (any go products) is not advisable
6.Post ICS, Disable media scanner receiver.
You can use elixir app to disable media scanner receiver. This will scan your SDcard over and over again resulting in Battery drain,which is significant, if you use a bigger SD. Use media scanner root to enable and disable.
As far as the usual ones,
7. Disable autobrightness
8. Keep screen @ minimum brightness
9. Disable autorotation
10. Disable location services.
GAPPS:
11. Disable GSF (google services framework ) receivers ~the ones with gtalk on it.
12. Disable auto sync
You can use timedo /timer Android to turn on sync twice /thrice daily.
13. Reduce number of accounts. Better to keep single than three accounts.
14. Good internet connection. Amount of energy taken to re connect is supposed to be far more than amount needed to keep a connection.
15. Undervolt/with underclock
RECOMMENDED APPS:
1.BETTER BATTERY STATS ~free for xda.
2. Onepower guard
I haven't found satisfying results with this app, but still try it out
3.greenIFY
I haven't used this @ all.
4. Any app, that is used to reduce /increase heartbeat sent to google servers.
Well, that's all I've learnt as of now.

Re: [faq][newbies only][mini edition]
Recommended apps section (only free)
Top apps
0. Superuser by koush (Clockworkmod)
1. Titanium backup
2. Efficient backup
3. Floating logcat ~logcat extreme
4. Catlog
5. Aroma file manager (recovery use only)
6 .Es file explorer
6.1 es file explorer v2
7. Yaffs file manager
8. App extractor
8.1 nandroid manager
9. Loaderdroid
10. Xda app
11. Elixir (much useful to disable app components than it's actual use)
12. Android pro widgets(similar to HTC friendstream)
13. Nova launcher
14. Timedo
15. Live logcat lite
16. Rom toolbox lite
17. Screen stand by root(turn off screen without making phone to sleep)
18. Disk Usage
Launcher:
1. Nova
2. Apex
Downloaders:
Loaderdroid
Multimedia players:
Video
mx
bs
qq
Audio
Ttpod
Equalizers
NOOZOXIDE REWIRE PRO
Walkman sound enhancements
Awesome beats
Cyanogen Dsp(better than stock )
Equalizer from market.
Cam/corDer /video recorder:
Camera:
Camera 360
ucam
spycam
Video recorder
ucam
Zoom camera
Camera magix
Browsers:
Fast and server based
Uc browser mini
Opera mini
Opera mobile
uc browser
Puffin browser
Full fledged browsers
Firefox
Dolphin
Google chrome beta
Chrome
KEYBOARDS ?
Touchpal keyboard
mĺ has internet permisn wid emoji
Office apps:
Kingsoft office(better than paid apps)
Zip extractors:
Zarchiver(ant-one)
Screen off(w/wake lock):
Screen stand-by
File managers:
ES explorer
Fx file explorer
Call recorders:
No known call recorders are working.
Stocks:
Personal finance
Superuser:
Superuser by koush ~open source&free
Super su ~made pro free after the release of prior~closed source ~
⇧Go back to main ♠
THE END.
© All rights reserved 2013?

Autoramdisk exchange alpha
MINI ADVANCED SECTION:
KERNEL RAMDISK exchange on Android itself:wip
AUTORAMDISK™ EXCHANGE PROJECT alpha™
『Moved by touch™』Inc.
In association with
Google Nose beta™
Presents
AUTORAMDISK™ EXCHANGE PROJECT alpha™
Current version: 0.0.0.0.071 Alpha
Created with Es explorer 1.6
Created on HTC explorer Pico a310e
Update:
I have got it to work and complete
http://forum.xda-developers.com/showthread.php?p=40035607
Old post: too lazy to delete
Present condition:
Hi. I cannot get it to work on HTC Pico yet .It may work on other phones. If someone can, please feel free to complete it provided you give proper credits And you do not make money out of this.
What's this?
It's a procedure (wip) to Flash any kernel without the need to change ramdisk.
As new kernel gets released, you don't need to change ramdisk to suit your Rom.
Automated procedure:
Open any kernel.zip with any zip extractor on your phone
Copy the script below and paste it in updater-script present in meta~inf/com/google/Android
(delete any other things written there. )
Code:
package_extract_dir("bin","/tmp");
set_perm(0, 0, 0755, "/tmp/busybox");
set_perm(0, 0, 0755, "/tmp/unpack-bootimg");
set_perm(0, 0, 0755, "/tmp/mkbootimg");
set_perm(0, 0, 0755, "/tmp/dump_image");
run_program("/sbin/dump_image","boot","/tmp/oldboot.img");
run_program("/tmp/unpack-bootimg", "-i","/tmp/oldboot.img","-o","/tmp");
package_extract_file("boot.img", "/tmp/boot.img");
run_program("/tmp/busybox", "mkdir","/tmp/boot");
run_program("/tmp/unpack-bootimg", "-i","/tmp/boot.img","-o","/tmp/boot");
run_program("/tmp/busybox", "rm","-r","/tmp/kernel");
run_program("/tmp/busybox", "mv","/tmp/boot/kernel","/tmp/kernel");
run_program("/tmp/mkbootimg", "--ramdisk","/tmp/ramdisk.cpio.gz","--kernel","/tmp/kernel","-o","/tmp/newboot.img");
write_raw_image("/tmp/newboot.img", "boot");
delete_recursive("/tmp/newboot.img", "/tmp/boot", "/tmp/oldboot.img", "/tmp/kernel", "/tmp/ramdisk.cpio.gz","/tmp/boot.img", "/tmp/busybox", "/tmp/unpack-bootimg", "/tmp/mkbootimg");
mount("yaffs2", "MTD", "system", "/system");
package_extract_dir("system", "/system");
Download zip files from the source link below
Extract it and copy the bin folder from there to your kernel folder directly.
There should be 3 folders in your kernel folder ~bin folder, meta inf folder, system folder and boot.img
Now compress it and Flash
Note that this is only applicable to change ramdisk. If the boot. Img needs more work than that, it won't work. Essentially, it won't work on sense4 compiled kernels and vice versa
Manual terminal emulator method:
Alright guys, one last tutorial from me making my last mark here .This tutorial is not tested fully and probably never will be due to lack of time. And it will work for sure ~but May have syntax errors.
Credits:
1.trevd for arm executable binaries.
2.Xda university.
Requirements:
1.Any Android 2.3+ rooted
2.Android terminal emulator
3.arm executable unpack-bootimg binary and mkbootimg binaries (find it below )
History:
I wanted to change ramdisk for kernels for a long time on phone itself ~probably for a year or more . But anyone who tried to unpack using normal unzip apps would've noticed that other data.img and even system.img in clockworkmod could be unpacked easily, but not the boot.img and recovery.img. When I searched to unpack, it was easy with computers using the unpackbootimg binary for Linux. Problem was it wasn't cross compatible with our phones . So, I was searching for quite a while,until I found trev on xda university and he had made arm executable binaries for unpacking, repacking. Actually the main reason these binaries were created was for far greater and more advanced purposes i.e. to use apply patch functions in update binary and update script to Flash ramdisk on phone without flashing the kernel itself or vice versa (AFAIK)[ The apply patch functions are used in normal ota updates for any Android phone ]. Anyway I took those binaries to unpack kernels on our phone to change ramdisk. I write this for those, who want to change ramdisk on thier phone, but had no experience in PC whatsoever. And also by doing this, I share the unpack boot image binaries by trevd for Android phone ,so that any advanced member May use it for kernel updater scripts~think about it ~one zip for all cm9/10/10.1. Ofcourse the rest is up to you. Thanks for reading
Procedure:
1.Download the zip given in source below
2.Unpack it
3.Find these two binaries in /system/bin
Unpack-bootimg and mkbootimg
4.Copy them to /system/bin and give them full execute permissions in es explorer and read/write permission for user.
5.For easy remembrance,say, b1.img is your original boot image for your Rom(and Android,say cm10 ) and b2.img is the new kernel released for cm10.1
6.You want to change the ramdisk ofb2 cm10.1 to cm10 ,so that you can Flash the new kernelb2 for your cm10
7.Create new folder in SDcard named boot and put both b1.img and b2.img there
8.Open terminal.
9.type the following code one by one
Code:
su
cd /sdcard/boot
mkdir /sdcard/boot/b1
mkdir /sdcard/boot/b2
unpack-bootimg -i /sdcard/boot/b1.img -o /sdcard/boot/b1
unpack-bootimg -i /sdcard/boot/b2.img -o /sdcard/boot/b2
rm /sdcard/boot/b2/ramdisk.cpio.gz
mv /sdcard/boot/b1/ramdisk.cpio.gz /sdcard/boot/b2/ramdisk.cpio.gz
mkbootimg --kernel /sdcard/boot/b2/kernel.img --ramdisk /sdcard/boot/b2/ramdisk.cpio.gz --base 12C00000 -o /sdcard/b2new.img
rm -r /sdcard/boot
Note: the last rm command will delete all your old kernels ~don't execute it, if you don't want to have it deleted.
10.Now you have new kernel boot image with your ramdisk in /sdcard/b2new.img
11.Put it back in the zip with it's modules and
12. Flash
13.Hoping it'll work.
14.That's the end.
Source and binaries here:
http://forum.xda-developers.com/showthread.php?p=36931024
For dream and Sapphire models, you can use the binaries created by koush ~ which is found in his github ~any kernel project.
I'll probably be leaving soon
Kind of feel like working for xda. I guess sak and others would probably feel like it later. It's been great while it lasted. So this is probably my last project. If I did have some extra hardware during this period, things May have been different. It's good, while it lasted.
"The fantasy of a dream is that, it's still a dream, when it becomes reality, then it's no more a dream and the fantasy is lost. "
「Good bye xda」
So long:angel:

Re: [faq][newbies only][mini edition]
one more
The Infamous BUILD.PROP Tweaks :
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/
from
http://www.droidforums.net/forum/droid-4-roms/234899-examining-build-prop-tweaks.html
Guess that'll end this hoax for good.
One thing that was useful for me was this
http://www.modaco.com/topic/347274-guide-making-cm-utilise-both-cache-and-data-for-dalvik-cache/

[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]

osm0sis' Odds and Ends -- Misc./Batch Tools, Flashable Zips, Scripts, etc.
General Information
In a nutshell, I just wanted a single thread to gather links to some of my other, larger projects, but also serve as a spot I could put some smaller scripts and zips I've created that I don't think merit their own separate threads. This is partially for my own sanity and will hopefully make it easier for others to find some things as well. A lot of the stuff here was developed with the GN, N4, N5, N7s or N5X, OP5/T, OP6/T, OP7Pro/T, OP8Pro/T or OP9Pro (my devices) and Windows in mind, but could generally be applicable to most devices either out-of-the-box or with some slight modification. If you see something that inspires you, go ahead and mod it, just let me know and give me some credit somewhere. If anyone would like to know the specifics of what's in a particular script that I haven't already linked to more information on, just let me know and I'll post that in here as well.
Note: Older zips with a "cwm-" prefix are NOT only for the now-defunct ClockworkMod Recovery, the prefix was used to denote a flashable zip before I adopted Chainfire's "UPDATE-" prefix. Please use a currently maintained recovery, like TWRP, for all zips to ensure the best compatibility/results.
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Misc./Batch Tools
AnyKernel3 (many devices) - link
AnyKernel was a simple template for an update.zip that could apply any kernel to any ROM, regardless of ramdisk to reduce the chance of any issues arising from the custom kernel pairing. The drawback to this is that some kernels require modifications to the ramdisk to enable/set up kernel features, and in the old AnyKernel format there was no way to do this. AnyKernel3 pushes the format even further by allowing kernel developers to modify the underlying ramdisk for kernel feature support easily using a number of included command methods along with properties and variables to customize the install experience.
APK-Patcher (many devices) - link
A proof-of-concept, simplifies APK modification to make it easier for modification creators to keep creating. Using JesusFreke's brilliant bak/smali and iBotPeaches' excellent apktool, modified to run on-device along with the various binaries required, allows on-the-fly APK modifications to be applied via recovery, to whatever ROM APK is present, taking the constant update burden off of the modification creator. The zip is smart and automated, using the APK name to run all the various parts involved for complicated patches and is extensible to any number of APKs in a single zip.
Android Image Kitchen (many devices) - link
A collection of Windows/Android ports of the necessary Linux utilities for Android image (kernel+recovery) mod work, and my own automation script to unpack, edit and repack the ramdisk. Other guides/scripts exist but none of them are universal for target device, compression and/or developed for Windows/Android. Now also Linux builds to bring my improved featureset back to where it came from, recently extended to macOS as well. Has been extremely useful for me in my messing around with kernel ramdisks.
ADB Screenshot (many devices) - attached
Take screenshots while in recovery. Useful for development of recovery apps or error reporting. Original method had lots of different threads around with the general method for various devices but I figured out a couple tricks required for getting it working on the Galaxy Nexus and then automated the process. Tested and confirmed working with both pixel formats of CWM and TWRP. More information in this GN Q&A FFmpeg thread. New method uses fb2png and should work on all ARM devices.
ADBsync sdcard Backup (many devices) - attached
Backs up the entire sdcard so that you can have a complete snapshot of your device when you make periodic backups, and be able to restore things exactly as they were. Automates the sync process of Renate NST's great adbsync utility which makes only newer files get pulled, significantly decreasing backup time for the sdcard compared to "adb pull". Original version posted in the old adbsync thread. Defaults for devices with /data/media/ internal sdcards (Nexus devices, etc.), but is easily customizable to backup other mountpoints or backup via ADB over WiFI.
Flashable Script Zips
TWRP A/B Retention Module script (many devices) - link
We need an interoperable root ecosystem again. A/B and system-as-root were a big setback to the root community in this respect. To help alleviate this issue, this atypical Magisk script zip "module" will keep TWRP installed to both slots when flashed from Magisk Manager after an A/B OTA has installed in the background, but before you use Manager to install Magisk to inactive slot.
Nexus BootUnlocker script (GN, N4, N5, N7 '13, N10) - attached
I don't know about everyone else but sometimes I find I've rebooted into the bootloader only to realize I've forgotten to unlock it in segv11's excellent BootUnlocker App beforehand. Well, I decided to make a BootUnlocker Script for my Galaxy Nexus so I could just boot to recovery quickly, unlock, then adb reboot-bootloader (or use my Reboot To Bootloader script below) to get back without having to fully boot the OS to make the change. Also extremely useful in the case you aren't able to boot. As with the app there is no data loss like there would be with fastboot, allowing you to relock for safety. Originally posted in the GN EDIFY Scripting thread. Modified for the newer Nexus devices and combined into a single Nexus BootUnlocker zip with tamperbit reset support added using information from the BootUnlocker App Dev thread. For newer devices using Factory Reset Protection (N6 and later), the BootUnlocker Script can't directly toggle the lockstate due to new security tokens, but it does now toggle the ability to use "fastboot oem unlock" without needing a booted device.
N7 BootUnlocker script (N7 '12) [creation guide] - link
The Nexus 7 2012 is a special case. Per-device encryption of an entire partition makes it impossible to support the N7 '12 in a simple root app, or flashable zip as above, however using my guide and included script you can now create a working BootUnlocker Script Zip for your specific device. As with the above scripts there is no data loss like there would be with fastboot, allowing you to relock for safety.
sdcard Fix Permissions script (many devices) - attached
A little flashable zip script to fix ownership and permissions of files and directories on the sdcard to what they would be if Android OS had put them there itself, since some apps can't access pushed files that have root.root as owner/group. This is useful when restoring to your sdcard backup, as with my ADBsync sdcard Backup batch script above, since generally, pushed files get root.root from adb shell and higher permissions than usual. Also a solution for a bug where sdcard files get lower permissions somehow, resulting in similar access problems. Currently written for devices with /data/media/ internal sdcards (Nexus devices, etc.), but could easily be modified for other mountpoints. No longer required on Oreo since it fixes these itself at boot.
Recovery SLAM script (many devices) - link
Recovery "Simple Legacy Auto-Mount" (SLAM!) is for devices that have been updated to SAR, but there are older zips that break in TWRP because they rely on the mounts occuring a certain way, especially during a ROM OTA. Recovery SLAM mounts them more as the zips would expect, generally allowing them to proceed. Most useful for premounting /system before a legacy zip with my FlashAfterUpdate addon.d script.
SUmount script (many devices) - attached
Another tool for the toolkit of anyone using Chainfire's SuperSU or topjohnwu's Magisk systemless root, this simple flashable zip script toggles the mounting of the su.img, magisk.img and magisk_merge.img while in recovery to allow easier access to the /su, /magisk and /magisk_merge filesystems, simplifying manipulating it via ADB shell, AROMA Filemanager or TWRP's terminal/file manager. Especially useful to anyone who uses su.d/post-fs-data.d scripts or can't boot due to some issue with a user addition in /su/su.d, /su/bin or a Magisk module.
unSU script (many devices) - link
While experimenting with Chainfire's brilliant SuperSU systemless root, I discovered that uninstalling the older style system-modifying root through his app (<2.60) didn't restore all of the modified system files correctly, so I wrote this script to do so and aid in people wanting to unroot from recovery. Expanded to support uninstallation of Koush's SuperUser, phh's Superuser, SuperSU Systemless (su.img and BINDSBIN), Magisk, LineageOS addonsu and custom ROM su binaries.
Adreno Systemless Installer script (N5, N6, N7 '13) - link
For use with Qualcomm's official updated preview GPU drivers packages for Adreno 3xx/4xx-powered Nexus stock images. This is a different frontend to take whatever device zip from Qualcomm is in the same directory as it (also searching /sdcard), then unpack and install it as a Magisk module or into the SuperSU systemless root /su filesystem, instead of the usual /system.
Kernel MultiROM Injector script (many devices) - attached
Intended for use in Chainfire's excellent FlashFire app to automate re-injecting the current boot image ramdisk with Tasssadar's brilliant MultiROM's trampoline bootmenu; this avoids having to do this as an extra step in MR-TWRP following an OTA, ROM Delta or SuperSU update. Should work for all EMMC devices with MultiROM installed.
GN PIT Editor script (GN) - link
Dumps and alters the Galaxy Nexus' Partition Information Table (PIT) to reclaim unneeded space from the /cache partition and add it to /system to allow for larger ROMs and GApps packages to make continued support for Lollipop+ easier. The resulting file is byte-for-byte identical to those created by external tools like PIT Magic, so that it may be flashed back to the device in Odin Mode to complete the repartitioning.
Kernel Emergency Reset script (many devices) - link
Basically a go-to cure-all for custom kernel users experiencing issues after an upgrade due to old settings left over in a kernel control app (eg. franco.Kernel updater, Trickster, etc.), or problematic init.d/userinit.d scripts. It's also useful if you just want to make sure you're running clean defaults without conflicts.
Reboot To Bootloader script (all devices) - attached
Those who preferred using CWM may have noticed a couple of things missing that the other popular custom recovery, TWRP, has built-in. One of these is a file explorer/manager, which is answered by amarullz' brilliant AROMA Filemanager. Another thing I found myself wanting was a way to reboot back to the bootloader once I'm in recovery, so I created this very very simple flashable zip script. (No longer required on CWM >=6.0.3.5). Note: Once in the bootloader, "Start" will boot you back to recovery. Not sure why, but it's not a big deal, just reboot normally from recovery at that point.
Flashable Installer Zips
Flashlt Installer (many devices) - attached
Installs my Flashlt script to allow easy flash and dump of boot, recovery and radio/modem (possibly others) EMMC or MTD partitions while booted, and trimming of null characters from files. Also installs a script zip that makes flashing boot.img (kernel), recovery.img, and radio.img/modem.img (baseband) files via recovery simple. It aims to save the average user the hassle of repacking their own image zip, or using the command-line or fastboot to flash it. Place an appropriately named file in the same directory as the zip and flash away! Should work on all devices with normal partition naming ("boot", "recovery" and "radio" or "modem") which accept Android standards-compliant images (including a/b slot devices like Pixel). Extremely handy when used with amarullz' brilliant AROMA Filemanager, and/or my Android Image Kitchen: Mobile Edition (linked above).
Busybox Installer (all devices) - attached
A byproduct of building my own static busybox compiles in all Android architectures for my AIK-mobile package, I figured I might as well offer them up separately as well since there weren't any providers making Android x64 builds when I was researching. Detects device (ARM/64, x86/_64, MIPS/64) to install the busybox binary, cleans up symlinks from any previous install and generates new ones. Detects and supports SuperSU/Magisk systemless installs. Please read the release post about applet inclusion and special features.
nano Terminal Editor Installer (many devices) - attached
An installer to push my own static Android ARM build of the nano editor and required files to /system/xbin and /system/etc/terminfo, with a wrapper adding a --term option to try terminfo profiles more easily. Detects and supports SuperSU/Magisk systemless installs. Can then be used from Terminal while booted. When flashed in recovery also allows temporary recovery use by pushing a script to /sbin/nano with the required setup, so you can trigger it from adb shell or TWRP Terminal. Makes it extremely easy and worry-free to tweak and mod on the go, knowing you can edit the faulty build.prop or startup script if something goes wrong.
adb + fastboot Installer (many devices) - attached
Marshmallow removed adb from the /system/bin directory. For those wanting this functionality back, here's an installer to push static compiles of adb and fastboot to /system/xbin, with a wrapper to point adb to the correct HOME directory and set TMPDIR for compatibility. Detects and supports SuperSU/Magisk systemless installs. Can then be used from Terminal while booted.
Nexus Media Installer (many devices) - attached
Custom ROMs usually don't include Google ringtones/notifications/system sounds and bootanimation, instead including numerous terrible sounds and often less-than-desirable visuals. This installs the media from old Nexus devices systemlessly (SuperSU and Magisk supported), or to system with an addon.d script to survive a ROM update or dirty flash, and using the zip name (also reading from /data/.nexusmedia) to allow user choice.
mtd-utils Installer (many devices) - attached
mtd-utils (flash_erase, nanddump, nandwrite) are necessary for mod work on a number of Android devices using mtd/char devices instead of the more standard emmc/block devices, and where the busybox versions have been less reliable in the past (especially where it doesn't include flash_erase), using the official suite is preferable. The older ARM builds available on XDA were about a decade old, so I worked out how to configure and cross-compile from the latest source. Detects and supports SuperSU/Magisk systemless installs. Can then be used from Terminal while booted
ZipSigner + Zip Installer (many devices) - attached
Signing zips and APKs on-device has always been a tricky proposition due to memory requirements of the old SignApk.jar, running a jar on an Android device, and other complications for script-based zips. Android has always been missing a zip binary (for unzip see my Busybox Installer). ZipAlign is also handy if you do APK work. To remedy this once and for all, here's an installer to push my dexed version of topjohnwu's brilliant zipsigner.jar and static ARM compiles of zip and zipalign to /system/xbin, with a wrapper to run zipsigner with Android's dalvikvm. Detects and supports SuperSU/Magisk systemless installs. Can then be used from Terminal while booted.
odex Script Installer (all devices) - attached
Based on the great work and binaries from this thread, a simple installer to push my odex script along with the required dexopt-wrapper and zip binaries to /system/xbin and set the appropriate permissions. Automates the procedure to odex any apk or jar from the commandline to potentially improve performance. Dalvik runtime (KitKat and below) only. Also uses cut from busybox.
N5X/6P BLOD Workaround Injector (N5X, N6P) - link
When, unfortunately, my Nexus 5X was recently stricken with the abominable Bootloop of Death, I looked into the well-publicized workaround and turns out it was all contained in the ramdisk and cmdline of a Android image. This is the perfect application of AnyKernel2, so I made an AK2 add-on zip to patch both the current boot and recovery partitions with all the current workarounds to help others afflicted by this issue to hopefully regain their data/device as easily as possible. Linked is the Nexus 5X thread, the Nexus 6P thread may be found here.
N7'13 TWRP flo2flox Injector (N7 '13) - link
The Nexus 7 2013 (flo) has seen a bit of a resurgence with official Lineage 18.1 support repartitioned as "flox". Since official TWRP is still automatically being built only for flo and this isn't compatible with flox, and the minor changes required for flox support were a great application of AnyKernel3, this zip automates the patching process so making official TWRP from flo2flox is easy for all going forward.
GN Synapse Support Injector (GN) - link
This AK2 kernel add-on for the Galaxy Nexus injects support for the Synapse tweaking app into the current boot partition ramdisk, including all the Synapse interfaces for the GN I've maintained since the Franco Kernel and DirtyV Kernel days.
GN Recovery Color Correction Injector (GN) - link
The aging screen on the Galaxy Nexus was looking pretty rough in recovery until I discovered the recently added new OMAP kernel color correction was also present in the most recent TWRP recovery versions. So this add-on zip uses AK2 to patch the current recovery partition ramdisk to add the command to reduce that green/yellow SAMOLED nastiness.
Kernel init.d Support Injector (many devices) - attached
An experimental proof-of-concept. Following from great ideas by Captain_Throwback in my AnyKernel2 thread and using script from my Flashlt script above, this AK2 zip will inject basic init.d bootscript support into any kernel ramdisk on any emmc device with normal partition naming and using the Android bootable image standard, without having to bloat a ramdisk using a busybox binary. This zip is also signed, so could potentially be used with non-Nexus stock recovery on a locked bootloader.
CMSetup Fix for GApps Installer (many devices) - attached
Installs a su.d script fix to work around the CyanogenMod/LineageOS 13 ROM issue of a broken Quick Settings pull-down when CMSetupWizard is removed as part of a GApps installation. Removing CMSetupWizard is useful because it allows Google's SetupWizard to grant apps default permissions, so the workaround automatically executes the only required command at the appropriate time following first boot. Requires a SuperSU/Magisk installation (for su.d/post-fs-data.d support). Flash after the SuperSU/Magisk zip and your GApps.
Dev Team init.d Pack Installer (all devices) [see "950iosettings, etc." below] - link
A simple installer I wrote to create the /system/etc/init.d/ directory, extract the latest init.d scripts as published by the "Franco's Dev Team" tuning collective (of which I was a member), then set correct owner, group and permissions to the entire init.d directory. If you are a developer and would like to include these tunables/scripts in your kernel or ROM please provide credit. A lot of time and effort has gone into this project and that's all we ask.

Scripts
950iosettings + 875mntsettings + 925vmsettings + 975experimental init.d scripts (all devices) [with Franco's Dev Team] - links
Also available bundled in an installer. The scheduler tunables have already gained a bit of attention/adoption on various devices and kernels, but this is the init.d script I wrote to set the new custom scheduler tunables values as "default" by an independent loop, sleeping in the background and detecting each time the scheduler is changed. There is no effect on idle drain or deep sleep. The settings included are the complete work of the "Franco's Dev Team" (or "Team Franco") tuning collective, of which I was a member. We strove to perfect the scheduler, vm and various other settings for the smoothest and fastest experience available. The collective was: malaroth, osm0sis, joaquinf, The Gingerbread Man, pkgnex, Khrushy, shreddintyres. If you are a developer and would like to include these tunables/scripts in your kernel or ROM please provide credit. A lot of time and effort has gone into this project and that's all we ask. Lollipop(+) updated versions now also available through the continued excellent work of pkgnex.
999-flashafterupdate.sh addon.d+addon.d-v2 script (many devices) - attached
For ROMs that don't have "Flash After Update" support built into their delta/update process. During an upgrade, this script will flash zips from an sdcard directory, with several options (listed in the script header) for displayed output, after all other addon.d backup/restore actions have completed. This can be used to flash SuperSU and then an AnyKernel2 kernel on LineageOS, for example. Only zips that specifically support addon.d-v2 can be supported on A/B devices. See this how to for instructions for use with A/B devices. Unzip once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
98-twrp_ab.sh addon.d-v2 script (many devices) - attached
Allows you to keep TWRP installed in a boot partition through A/B OTAs with Magisk installed by copying the TWRP ramdisk from the current slot to the updated one, before Magisk's addon.d-v2 script patches it. Requires a current Magisk installation since we need the tools and Magisk's the only way to ensure a working addon.d-v2 environment across ROMs at the moment. Unzip once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
97-dumpimages.sh addon.d+addon.d-v2 script (many devices) - attached
For ROMs with boot.img, etc. inside an OTA payload.bin or otherwise inaccessible, it dumps the updated chosen partitions before further modifications (TWRP, Magisk, etc.), saving it to /sdcard/Download/boot.img or to/from other customizable locations at the top of the script. Unzip once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
00-omnirootfix.sh addon.d-v2 scipt (many devices) - attached
OmniROM appears to include 69-gapps.sh automatically in its /system/addon.d directory despite not shipping with any GApps; when not rooted this doesn't appear to present a problem, but really this is only because the script doesn't have enough permissions to run how it's supposed to since Omni's sepolicy doesn't let addon.d-v2 work correctly. Once Magisk is installed, providing more privileges to the addon.d-v2 update_engine, Omni's 69-gapps.sh would remove important system files during an A/B OTA when no GApps were installed, so this script will simply prevent that for those wanting to run Omni minimally and with root. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
00-resizesystem.sh addon.d script (many devices) - attached
One common solution for aging devices is to resize the /system partition so that it can hold newer, larger ROMs and, of course, GApps packages. On devices where the /system partition has been resized to hold larger GApps packages, but the ROM in use has system.dat format zips with no resizing functionality, the extra space would get lost in a ROM delta flash, breaking things when GApps attempted to restore. This script will resize the system partition to its maximum before the GApps restore occurs on EMMC-based devices with standard partition naming. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
10-extract-lineage-kernel.sh addon.d script (many devices) - attached
Nowadays with systemless root and other boot.img mods out there, it's good to have a backup of your ROM's unmodified boot.img handy in case you want to do a clean flash of your boot partition. Since LineageOS moved their update zips to a /data/data subdirectory that made this harder to get to, I automated the procedure as an addon.d script so that the newest gets extracted on each update. The output directory may be changed by editing the script. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
999-customkernel.sh addon.d script (many devices) - attached
Addon.d is awesome at restoring your GApps, root app, and other things after a ROM Delta, update, or dirty flash, but of course this can leave a lot of stuff out that you'd also have to re-flash (see below for a personal addon.d script you can modify to cover anything else you want to save). This script aims to help remedy the issue for custom kernel users on EMMC-based devices with standard partition naming by dumping the current kernel as part of the addon.d backup process, and then restoring it after the ROM has flashed its included kernel. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions. This is deprecated by my FlashAfterUpdate addon.d script, above.
logohack.sh (GN) - link
Galaxy Nexus bootloader image replacement hack script. Inspired by bitdomo's brilliant imgdata tool and replicating the functionality of Ezekeel's abandoned, broken paid Logo Me app, this script improves upon the app version by working on all Galaxy Nexus bootloaders and on-the-fly, to allow replacement of the Google logo and lock images within the sbl partition. Remove the .txt extension once downloaded and place in /system/bin/ or /su/bin/ with rwxr-xr-x (755) permissions. It can then be run from the Terminal.
flash_image (many devices) - attached
MTD devices require a little extra finesse when flashing partitions from the command prompt and multiple commands, versus MMC devices, for which we can just use the dd command both ways. I wrote this little script to simplify the process for myself in my MX Box tinkering. It parses /proc/mtd so you only need to enter the partition name. It requires _n0p_'s excellent MTD-Utils compiled for Android, and uses grep and cut from busybox. Remove the .txt extension once downloaded and place in /system/xbin/ with rwxr-xr-x (755) permissions. It can then be run from the Terminal.
getprio (all devices) - attached
Android doesn't allow you to check the priority (or "niceness") of a process with the getpriority command as you would with normal Linux, and busybox doesn't provide this functionality either, so I wrote this reasonably simple script to allow you to check the niceness of a process. Some kernels have been experimenting with increasing the priority of com.android.systemui for smoothness, so this command can be used for testing different levels and whether the renice command set it correctly. Remove the .txt extension once downloaded and place in /system/xbin/ with rwxr-xr-x (755) permissions. It can then be run from Terminal with either the pid (default), class or a class name search string. Uses pidof and pgrep from busybox.
gappsintegrator init.d script (many devices) - link
ROM GApps Auto-Integration of /data/app GApps into /system, complete with libs (unlike Titanium Backup), for Jelly Bean through Marshmallow. It should process things early enough in the boot that afterwards Dalvik will immediately do the cleanup ("Android is upgrading..."), much like following an OTA. An initial GApps installation is one requirement and there are some important notes for support of Lollipop and above. Intended for ROMs with a busybox installation. Can also remove libs from and zipalign the integrated APKs if those binaries are present in the ROM.
lmkwhitelist init.d script (all devices) - link
Users running ROMs or kernels with extremely aggressive custom lowmemorykiller (lmk) driver settings may notice their launcher redrawing frequently. Some kernels/ROMs also include an exclusion for this by making stock (or the included) launcher unkillable, however that still leaves all the 3rd party launchers out there that people use. I wrote this init.d script with a community created list of the most common launchers to make whichever one is installed unkillable. This also has instructions for how to set up init.d scripts. If your launcher isn't included in the list, you can modifiy it by adding the application class name (from the Play Store URL) to the list within quotes, separated by spaces. Also part of the 975experimental Franco's Dev Team init.d script, linked above.
dalvik2cache init.d script (all devices) - link
Bind mounts the dalvik-cache directory to the cache partition. Useful on devices where the cache is sizable and unlikely to be used for OTAs (custom ROM, etc.), and the data partition is not. Every little bit counts!
settingsdump.sh (all devices) - attached
In comparing vm settings from various kernels and ROMs to see what's out there, I wrote this script to generate a list of the values of all the relevant sysfs files and directories. Now expanded to cover cpu and governor as well. Remove the .txt extension once downloaded. To run it, assuming you just put it in /sdcard/, open Terminal Emulator and type: "sh /sdcard/settingsdump.sh" (without quotes). It will output the file to /sdcard/r*-output.txt where * is the revision of the kernel you're running. This makes it easier to compare what's changed between different nightlies, for example.
Other
BootUnlocker app (many devices) [with segv11] - link
With a number of users researching and contributing the bootloader lockbit and tamperbit offsets in threads around xda and to the development thread for seg11's excellent BootUnlocker app, I have begun making beta builds with these new devices added. With hopes of adding any/all that can be, it now supports all the older Nexus devices, OnePlus devices and several others. We are accepting Pull Requests and collaborators for further device/design updates. Check my original revival post for more details.
G-Box Midnight MX2 g18ref ROM, recovery and kernel osmods (MX Box) [with BenniBenassi & relol] - link
I bought one of these unbranded Android TV boxes and was immediately determined to tweak it as much as possible following my work on the Galaxy Nexus. Flashing the official Matricom stock ROM over the generic included one I also discovered the recovery didn't have any A/V output to my old CRT TV. I set out to dump the kernel and recovery images, fix the recovery images and tweak the kernel defaults for the most performance.
Holo Stock Notification Icons for Notification Toggle (many devices) - link
This was likely my first post ever on xda. It is a "Notificon" pack for j4velin's fantastic Notification Toggle App, bringing a seamless stock look to this indespensibly useful app. Also a great way to get back to Settings easily from the notification shade since Android 4.2, and add shutdown/reboot menu functionality to stock/vanilla ROMs.
My GN Kernel Settings + 900colorsettings init.d script (GN) - link
I was being asked a fair amount for my kernel settings over in the GN f.K thread where I helped out, so I posted them up. I also put up an init.d script for setting color values on boot, which can drastically change the outcome on older panels, and at least makes custom values seamless. Instructions for how to set up init.d scripts are included.
Galaxy Nexus Baseband Collection: maguro - i9250 / M420 / SC-04D Radios (GN) [with josteink] - link
Original thread author josteink moved on to other devices and asked me to take over the thread. Lots of great information on the GN radios, posted alphabetically by region and chronologically by the build string date I found embedded in the images. Huge respect and massive thanks to josteink for seeing the need for a baseband thread almost as soon as the Galaxy Nexus was launched, way back in December 2011, and maintaining it diligently.
TK GApps (many devices) [with TKruzze] - link
After helping TKruzze with some of the concept and script work for his famous Paranoid Android Google Apps packages (PA GApps 2.0), we decided to collaborate again for his return to XDA after a much-needed hiatus, with me doing the thread setup and management with DevDB, and a Q&A section so things don't get overwhelming for those trying to follow along. The main thread remains locked and can be subscribed-to for those wanting notification only when there's a new GApps release, and the Q&A functioned as the main discussion thread where people can help each other. Much of the script is the same from PA GApps but TKruzze has added some impressive new features, made many fixes and revamped a large portion of the documentation. I also continued as an adviser and submitted script when needed.
Nexus Louder Audio Improvement Patch (GN, N4, N5, N7 '12, N7 '13) [with Misledz] - link
One of my earliest forays into EDIFY scripting, I wrote the flashable zip install/revert scheme for this great volume boost mod by Misledz. The scripts check to see if the mod is already installed and if so recommends you flash the version-specific revert that goes with it. More on that in the Intelligent EDIFY thread. During install the script also backs up the ROM files it replaces so that you don't need to reflash your whole ROM if something goes wrong, just use the revert to restore the backups. I eventually rewrote this completely in shell script with a Universal install/revert, that detects which files to backup and leaves a list for itself to revert. I also wrote automation batch scripts for Misledz as the "Louder Build Farm" to simplify his work for all the versions of the mod he maintains for various devices, linked in the knowledge base below. GN/Dev thread linked; Other links can be found there.
Payload-Dumper-Go for Android Magisk Module (many devices) [with ssssut] - link
payload-dumper-go arm compile and wrapper for use extracting from payload.bin on-device.
Git for Android Magisk Module (many devices) [with Termux] - link
Hacked arm64 git commands for use on booted Android.
Google Experience XML Magisk Module (many devices) [with Google] - link
Hacked Google Nexus/Pixel/Android One sysconfig feature xml entries for use on non-Google devices.
Digital Wellbeing Add-on Magisk Module (many devices) [with Google & Open GApps] - link
Digital Wellbeing for Android 12L and 13 GApps that don't properly support it (like MindTheGapps).
Model Mod Magisk Module (many devices) - link
Experiment to append _SN to the existing device model to get CTS passing again after the September 2021 server-side SafetyNet changes, (superceded by kdrag0n's excellent Universal SafetyNet Fix module).
Xposed Framework Installer Zip (many devices) [with rovo89 & Tungstwenty] - link
When JB4.3 broke all previous root methods I made this simple frontend script to install rovo89's brilliant Xposed Framework for modding ROMs until they could release a new version themselves. Xposed Framework files and the install.sh used are the work of rovo89 and Tungstwenty; I have only created a recovery flashable zip and shell script to function as an alternative frontend for the framework installation process. Then updated to mimic the APK installation and allow devices with /system write protection like HTC's S-ON to install the framework. (Deprecated as of Xposed 2.5).
BBCode for my xda Signature (n/a) - link
Last and definitely least. A number of people have asked me about the formatting of my signature, so here are some simple BBCode tricks and workarounds I thought others might like too. Keep in mind that my signature can be significantly larger because of my RC status.
Enjoy!
Questions, comments and feedback welcome.
Credits & Thanks: All authors of any included binaries and libraries for their amazing work. Anyone who's helped me with these projects along the way.
Disclaimer: Naturally, you take all the responsibility for what happens to your device when you start messing around with things.

Knowledge Base
Links to information/research posts I've made and other experiments.
----
avbtool-arm (zip package) - link
AOSP's BootSignature.jar for AVB v1 was relatively simple to run on-device for boot.img modifying flashable zips like SuperSU and AnyKernel2 but avbtool for AVB v2 is written in Python, so that makes things a bit trickier. For experimentation I whipped up a little wrapper script to run avbtool on-device with an actual Python interpreter.
Omni SoundPacks (and Nexus Stock pack) - link
My suggested expansion to the Omni SoundPacks feature to allow it to cover all SystemUI sounds.
OnePlus FingerPrint Material Icons (Information) - link
My preferred fingerprint icon for the in-screen OP6T sensor using Zacharee1's excellent OPFPControl app.
----
Complete Shell Script Flashable Zip Replacement + Signing Documentation (Reference) - link
Using a shell script instead of an update-binary in flashable zips can make them universal for architecture and put a lot more power in the hands of the developer. This reference documents all of the analogous functions myself and others have written to make this easy.
Booted Zip Flashing Shell Setup Script (Reference/How-To) - link
My implementation of booted zip flashing, originally for AnyKernel2 in Franco Kernel Updater (now Franco Kernel Manager) and since expanded to support AK3's ability to be flashed from anywhere and support most other flashable zips on devices that allow remounting /.
Unified ext4/f2fs ramdisk + ROM installer (Reference) - link
Supporting multiple filesystems like ext4 and f2fs in a custom kernel boot.img ramdisk required some work before custom ROMs were updated to do this themselves and use fallback fstabs. This is the roll-up post gathering all the changes necessary for someone to add this pre-official support to their ramdisk, kernel and ROM installers.
FlashFire Recipe Book (Reference/How-To) - link
Just a quick reference of common tasks (OTA flashing, etc.) for people figuring out how to use Chainfire's brilliant flashing app.
personal addon.d (How-To/Template) - link
I was tired of having to redo a number of tasks (remove files, backup Nexus sounds and replace the AOSP ones, etc.) to get my device back to where I wanted it after flashing a newer nightly, so I wrote an addon.d script to do it all for me. Provided if anyone wants to modify it for their own personal setups.
KBox2: Set Up A Build Environment On Android (How-To) - link
Very cool Linux-like command prompt environment on Android. I originally had it set up as a native build environment with rudimentary git support. You can follow my steps to do the same.
Keeping SafetyNet Passing With Incremental Google OTA on Virtual A/B Devices (How-To) - link
Post-reboot checks added to the incremental OTA process for Virtual A/B devices using Google's servers made it impossible to remain rooted throughout the OTA process, but following these instructions you can complete the OTA then re-root without SafetyNet catching you.
Cygwin-Linux Cross-Compiler (How-To) - link
Compiling from Cygwin with a Linux target required some fixes to the toolchain, so I detailed them for future reference.
N4/N5/N7 '13 Qualcomm Optimized Bionic/Dalvik Patch Comparisons (updated zips) - link
Using Qualcomm optimized files on Snapdragon devices improves performance greatly on KitKat. Especially good on Nexus devices or AOSP ROMs. I took the time to dissect the required files and see what worked best.
AIK Build Farm (desktop shell script) - link
The Cygwin shell script "build farm" I wrote for my Android Image Kitchen project to perform all of the cross-compiles required for the mobile and Linux versions. Allows someone to setup the repos from scratch and build.
Louder Farm (zip packages) - link
The Nexus Louder project was a pretty massive system file modifcation undertaking. This details my work to make building the patch zips easy for co-dev Misledz, and includes the farm packages at various stages.
----
N7 '13 Bootloader cracking (Information) - link
Sat down with my parents' Nexus 7 2013 (before I got my own) over Christmas and cracked the bootloader for unlock support via my Nexus BootUnlocker Script zip and later the official BootUnlocker App.
N7 '13 Unbricking (Information) - link
Instructions I put together for recovering from a hard brick (bad bootloader flash usually), via the exposed Qualcomm/Marshall London "HS-USB Diagnostics 9006" mode.
Default System Alarm Setting Script (Information) - link
A script snippet function to allow easily changing the default alarm sound on ROMs that hide this ability, like OnePlus' OxygenOS.
SELinux Audit2Allow Script (Information) - link
A script snippet for turning SELinux audits in a logcat into allow statements ready for supolicy or magiskpolicy.
Partition Dumping Script (Information) - link
A script snippet for dumping all non-userland partitions from any eMMC device, useful for bootloader lockstate hacking.
GN Partition Information Table (PIT) Research (Information) - link
Wanting to push the GN as far as possible, several remaining users came together to discuss how it could be repartitioned to add more space to /system to better support Lollipop+ and I contributed a large amount of R&D over several posts throughout the thread which resulted in the PIT Editor script zip (posted above). Could be useful for other devices using PITs as well.
GN/N7 '12 tunables post (deprecated) (Reference) - link
The list of supported basic tunables on franco.Kernel for the Galaxy Nexus and Nexus 7 2012 back when those were my primary supported devices.
GN scheduler tunables HZ scale (Information) - link
The Galaxy Nexus scheduler (and other) tunables opperate on an odd scale due to the the device's HZ value in the source being weird. This post experiments with that and finding the method/equation behind it.
LMK boot timing (Information) - link
The Android lowmemorykiller module default tunables go through a bizarre sequence during boot, so I experimented and came up with a script to allow setting alternates as soon as possible.
LMK Launcher Whitelist/Niceness settings reversion (Information) - link
Setting oom_adj values and changing the niceness on launchers and systemui improved responsiveness and helped avoid these important processes being killed by LMK. Then I noticed sometimes they spontaneously reset; experimentation followed.
MTD partition flashing (Reference) - link
My MTD-based MX Box set-top device gave me a few hours of headaches until I figured out how to dump and flash the boot (kernel) partition correctly. This details my experiments and the correct procedure I discovered.
nano Android static build instructions (Reference) - link
A little documentation of all the dirty tricks I used to get the nano terminal editor utility to build for Android from the official git repo source.
mtd-utils Android static build instructions (Reference) - link
A little documentation of all the dirty tricks I used to get mtd-utils to build for Android from the official git repo source.
Pixel Launcher bind mount instructions (Reference) - link
I was annoyed that on stock Nexus 5X and 6P Pixel Launcher wasn't available and when sideloaded lost the Google Feed pane, so I replaced Google Now Launcher with Pixel Launcher using bind mounts.
Netflix broken DRM workaround instructions (Reference) - link
Custom Nexus 7 2013 ROMs Nougat+ have all had issues with Netflix due to some peculiarities of the DRM libraries the ROMs use, but some found that intentionally semi-breaking DRM using files from other devices allows Netflix to work again, but this broke Google Play Movies. I did some more testing, resolved the Play Movies issue and wrote up how to install the single needed replacement library either to system or with a systemless bind mount.
----
Thanks for the interest! More to come, I'm sure!

What can I say...
SUBSCRIBED
Sent from my Galaxy Nexus

Far superior

thanks
Franco Team always made a great work .... Keep it up.
Thanks for these great useful infos!

Bookmarked, subscribed and rated a well deserved 5 stars :good:

Thanks for sharing. Very useful.

Nice...
Envoyé depuis mon Galaxy Nexus avec Tapatalk

Nice collection osmosis

Many thanks osm0sis, to you and all the team for all your contributions Almost feel as though I know you since I've been hanging round GNex and N7 franco.Kernel threads for so long and if you pop up on the N4 thread it's like seeing an old friend I'm mostly quiet, but really appreciate all you do :thumbup:
Sent from my Nexus 4 using Tapatalk 2

Subscribed... Thanks dude...
-3StarsAndaSun

Subscribed. Thanks

Thanks back to you, everyone! I've learned a hell of a lot about Linux and Android in the year since I got my GN, and I mostly have xda to thank for that, even though I've always been the type to tinker and Google things. Still lots more to learn though! But, at the very least I guess nobody can say I haven't been busy since becoming a RC, huh?

Nice to see all these settings are adopted by others, also the interactive tuneables are used in ak kernel now.
Verstuurd van mijn Nexus 7 met Tapatalk

Subscribed :good: !

New version of testvalue.sh up. I added the input value to the output.txt file to make it easier to read since it starts at 0. Right now we're trying to work out the equation for the scale of certain cfq and deadline tunables on the GN, which is a bizarre one:
7, 15, 23, 31, 39, 46, 54, 62
Increases by 8s but occasionally (on the 5th jump, though sometimes 6th) it increases by 7.
Edit: Every 3rd increase of 7 occurs on the 6th instead of the 5th.
Edit 2: Stats genius of the group, @pkgnex worked out what the trick was; dropping the decimals once calculated.
So in Excel: y=TRUNC(x*7.8125,0)
:good:
The "why" of the GN tunables working this way, with a value of 125/16 is a very good question. No ideas there, personally. Something to do with the GN having a HZ value of 128 (where on others it's 100 or even 200) I'd assume, but I don't see the direct connection.
This was very handy to know though, because the cfq+deadline source requires the number of jumps (x) to hardcode the values, not the actual desired numbers like you'd expect.

Perfect!!!

Very interesting

Created a getprio script last night for use in /system/xbin as a runnable script to check the niceness of a process. It's up in the 2nd post now. It attempts to make up for Android not having "getpriority", and not displaying the niceness in "top" or "ps" like it would on mainstream Linux.
Code:
usage: getprio [-p] <pid> | -c <class> | -s <search string>
note - class name search will only use the top result
So you can either -p the numeric pid of a process if you know it (this is the default so the -p argument is optional), -c the class name of the process (eg. com.android.systemui), or -s a search string using part of the class name (eg. systemui). If there is more than one result for the search only the top result will be returned so if you are trying something like "-s mms", you'll only see the system mms process and not com.android.mms until you get more specific with "android.mms" or something. It's likely you've got a lower level process if you get the response "Warning: empty class name!" so that's your tip your search was too broad. Naturally, processes must be running in order to return info as well. :good:
Edit: ps -p will display niceness on Android, but it's not ideal if you want it only for a specific process like with getpriority. Thanks boype.

[SCRIPT/TOOL] kn0x0ut Toolbox - Install custom roms, mods + more and KEEP WARRANTY!!!

Ladies and Gentlemen I present to you the
kn0x0ut Toolbox v2.30!
(complete, with knox 0x0 reference! hehe)​
This script/toolbox allows you to install custom roms, and mods that you would normally have to flash with custom recovery.
(aroma installer and other magic like that gets ignored, but the aroma mods can usually be installed manually on a second run)
On top of that it allows you to create and restore backups of your system and data partition. (for "online" restore without needing custom recovery).
As we (hopefully) all know, if you want to keep knox warranty void at 0x0 you cannot use a custom recovery or kernel....
But let me start with a few words of warning:
Dont do anything obviously stupid...there are no safe-wheels for most commands.
(for example: dont "clean-base" or use "rom-install" without actually installing a new rom or you will most likely end up without system apps and device not booting correctly - like you wouldnt wipe system in a custom recovery without installing a rom...).
It can be used over adb or terminal, but if you install a rom the system ui gets stopped, so better do it over adb!
kn0x0ut toolbox is 100% safe for your device - no hardbrick or efs clear possible by using it!
The worst thing that can happen when using the kn0x0ut toolbox is that you have to factory reset or flash again with odin, so keep the odin file close. (at best this is a custom made RDLV odin.tar.md5 you used to upgrade your rom version with - or for people who have to use other methods because of the new bootloader - keep the last odin file close you used to upgrade also.. and the root method that worked for you)
This whole thing "programmed" on/for a N9005 but in theory it should work for all samsung devices - including the other knox enabled devices and even on many other devices. (but it might need some adjustments, so be careful and have a way to restore your stock rom before you try anything fancy with other devices)
If your knox warranty is already void aka 0x1 then you can still use the toolbox and its mods (some could actually be useful to anyone..) but it won't bring back the warranty.
I didn't really create this thing for me actually - I already did the all steps the toolbox can do by hand with adb terminal on my device (and perfected my method with lots of trial and error..), but I wanted you guys to also be able to enjoy custom roms while keeping your knox warranty intact and show samsung a big FU for putting us through this BS in the first place...
If you like the toolbox and appreciate the work I put into this please consider buying me a beer or hitting the thanks button at least.
---
This kn0x0ut toolbox itself requires root access (if you want to be able to install mods and files you need to be able to mount system writable)!
You will have to use "Root de la vega" or some other method to get rooted while keeping your warranty intact.
IF YOU GET "PERMISSIONS DENIED" ERRORS, PLEASE TRY THE FOLLOWING COMMANDS TO REMOUNT YOUR SYSTEM WRITABLE:
(please try them all, and report back in the thread which one works, and which fail or get permission denied)
Code:
mount -o rw,remount /system
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
mount -o rw,remount /dev/block/mmcblk0p23 /system
---
How to use:
Extract the download from below to the root of your internal or external sd card.
The script will try to detect the folder first on the external and then on the internal sd.
(/mnt/extSdCard/kn0x0ut or /sdcard/kn0x0ut)
Then browse into that directory with terminal or adb shell and type:
Code:
sh kn0x0ut.sh
and you will get all the commands supported currently.
---
You can then use the command
Code:
sh kn0x0ut.sh kn0x0ut
to install the script to your system's xbin folder and create a symlink to "/system/xbin/knoxout" as well.
(if you want to upgrade kn0x0ut from an older version, make sure you delete all the duplicate old files from the kn0x0ut folder - basically everything but the "processed" and the backup folders if you have them, and replace them with the files from the latest versions download. Then re-run the "sh kn0x0ut.sh kn0x0ut" command to update the kn0x0ut script in your system/xbin folder as well)
From then on you can just type
Code:
kn0x0ut <command>
or even easier:
Code:
knoxout <commands>
The script will automatically detect the kn0x0ut folder on the external or internal sd. (external has higher priority if both present)
To install a zip file meant to be flashed in CWM, you put in into the "put_files_folder". You can put zip, tar, tar.gz or already extracted files and folders into there.
---
To actually work, the files/folders must be in a certain stucture. The script expects already extracted files which get placed into the put_files_here folder to be in the structure like they would appear on the device.
Think of the "put_files_here" folder as the root folder - files get placed on the system in the same structure as if the put_files_folder was the rootfs "/". So if you got a subfolder system/app inside the put_files_here folder, the files inside it will get pushed to /system/app... Hope this makes any sense, else someone else pls try to explain it better.
(NOTE: The script will only install files, it wont do additional magic if there is any contained inside the zip like aroma installer - its mainly meant to speed up the process of installing mods and/roms that require system files to be replaced. (and some things might need to be done by hand, if you want enhanced functionalities from aroma installer)
If you have a zip that does not fully install, check out if there are any scripts inside etc. - and also check the "not_installed" folder which gets created after each installation.
If you want to install a rom, make sure you are on the same base version as the rom you are trying to install. So if you want to flash rom "xyz" based on MK2 then you gotta have stock, but rooted MK2 installed (with odin and RDLV for example). If you want to mix versions, you can try - but I can't tell if that actually works or causes problems - I just would skip the BS and make sure you got the right base rom installed with odin before tying to install a custom rom with kn0x0ut...
---
See 2nd post for current command list.
See 3rd post for current list of available mods.
See 4th post for more detailed command explanation.
See 5th post for download.

Code:
>>> commands <<<
Help:
-----
help - Display help
listmods - Display a list of all available mods
Backup:
-------
backup-base - Backup system app and framework files
backup-efs - Backup efs partition
backup-system - Backup system partition
backup-data - Backup data partition
backup-full - Backup system and data partition
Installation / Restore:
-----------------------
install - Install contents of "put_files_here"
(place backup tar's there for restore)
For System Restore use "rom-install"!
For Data Restore run "clean-data" then "install"!
rom-install - As above but clean system apps, framework
and dalvik-cache before
Mod Installation:
-----------------
mod=[mods] - Install specified mods (for multiple seperate with ',')
Special:
--------
supersu - Install supersu v1.80 to xbin (incl. init.d support for all kernels)
busybox - Install busybox v1.21.1 to xbin (incl. symlink-redirect)
kn0x0ut - Install kn0x0ut v2.30 to xbin
fix_perm - Install fix_permissions v2.10 to xbin
backup_perm - Install backup_permissions v2.00 to xbin
Cleaning:
-----------------------
clean-dalvik - Clean dalvik-cache
clean-base - Clean system apps and framework (MAKE SURE YOU INSTALL NEW BEFORE REBOOT!)
clean-data - Clean data partition to restore from backup (leaves sdcard content alone)
Bloatware Removal:
------------------
removebloat-cooolboy - Remove most bloatware (based on CoOoL_BoY's bloatware remove script)
removebloat-zroice - Remove bloatware hardcore mode (beware - most google stuff gone except playstore)
>>> commands END <<<

Code:
>>> available mods <<<
Mod: acid
Description: ACID Audio Engine v5 (optimised for samsung)
Mod: acid_awesomebeats
Description: ACID Audio Engine AddOn - Awesome Beats
Mod: acid_noozxoide
Description: ACID Audio Engine AddOn - Noozxoide
Mod: aosp_browser
Description: AOSP Browser (with Google, Startpage & Startpage Mobile)
Mod: aosp_clock
Description: AOSP Clock (deinstall ClockPackage.apk if you want to use this)
Mod: bash
Description: BASH Shell
Mod: busybox
Description: busybox v1.21.1 (busybox.net) + special default symlink fixes
Mod: chronus
Description: Chronus Clock Widget
Mod: forcelte
Description: Init.d script to force lte on
Mod: onandroid
Description: onandroid script v9.20 + necessary binaries (mkyaffs2image, dedupe)
Mod: onandroid_n9005
Description: onandroid partition layout for N9005
Mod: openvpn
Description: openvpn binary v2.1.1 (statically linked, no libs necessary)
Mod: sqlite3
Description: sqlite3 binary + libs and init.d script to optimise db's at boot
Mod: zipalign
Description: zipalign binary + init.d script to run at boot (fixed to make it work!)
>>> available mods END <<<

Add ons and commands explained in detail:
1.) Fix permissions script is running after all the commands to ensure permissions are correct. You can also install the fix_permissions script as standalone command. (see command list)
2.) To install a rom or other cwm zip file put it into the "put_files_here" folder and run "install" or "rom-install" depending on what you want to do. You can also use this to restore system and data partition backups made by kn0x0ut or onandroid (those have to be in tar or tar.gz format).
3.) The busybox which gets installed is directly from busybox.net and has more commands than the "normal" busybox floating around from stericson.
Additionally if you use the "busybox" command some symlinks will get redirected from toolbox to busybox and give enhanced functions.
(for exampe: mv, cp, rmdir, rm, ...)
4.) "sqlite3" and "zipalign" will also install an init.d script so that they are running on system boot to optimize the dbs and/or zipalign the apks.
--- more to come ---

Current Version: v2.30
### Downloads ###
Please do link to this thread if you want to use the kn0x0ut toolbox for other projects.
(do not distribute kn0x0ut download links but instead link to this thread, not only for credits, but so people can report bugs etc in one place)
READ THE INSTRUCTIONS AND TRY TO REMOUNT YOUR SYSTEM WRITABLE BEFORE YOU TRY TO INSTALL A ROM! AND ONLY DO THAT OVER ADB SHELL!!!
>>> YOU HAVE TO RUN KN0X0UT AND ALL ITS COMMANDS AS ROOT USER IN TERMINAL OR OVER ADB SHELL. TO MAKE THE SHELL ROOT YOU HAVE TO TYPE "SU" AND THEN ENTER BEFORE USING ANY OF THE OTHER COMMANDS! <<<
kn0x0ut_2.31.zip - 14.84 MB
Do not run rom-install if any of the other commands fails, and please try them first. (at least busybox and supersu installation)

reserved

reserved

So if I already have Knox at 0x1 am I screwed?
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2

harosxcomp170 said:
So if I already have Knox at 0x1 am I screwed?
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
Click to expand...
Click to collapse
well then this thing has no use to you, other than the addons and installing stuff on a running system instead of using custom recovery.
But it wont fix the knox warranty no. It just KEEPS it from getting tripped by allowing installs without custom recovery.

Now say if I odined back to completely stock with no root. Will that bring my Knox back to 0x0? Or has the damage already been done?
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2

harosxcomp170 said:
Now say if I odined back to completely stock with no root. Will that bring my Knox back to 0x0? Or has the damage already been done?
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
Click to expand...
Click to collapse
sorry to say, but gtfo with these questions inside this thread! knox 0x1 stays knox 0x1 - so far nothing gonna bring it back - ssheeesh this you should really know man. one lil google search gives you 100 threads about just that! (completely offtopic to this tool also... sorry but is this xda or android central?!)

Yea sorry about that I didn't know if there was a break through or something I bought my phone off swappa with knox already voided.
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2

harosxcomp170 said:
Yea sorry about that I didn't know if there was a break through or something I bought my phone off swappa with knox already voided.
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
Click to expand...
Click to collapse
well tbh, I wouldn't worry so much about it, I'm strongly considering to trip my flag to have custom kernel and recovery. This toolbox here can't fully replace it. But maybe we find a way to make our own signed kernels and/or recovieries or some other way around this knox warranty void bs.
My phone is still new and for such an expensive piece I rather don't risk anything before it's clear there are no bugs out or smth people dont yet know about (I mean with the hardware, not with my toolbox or smth). Plus its fun to try out whats possible.. (i learned so much about android and the shell by doin all this... good exercise hehe)
So until then I'll keep my warranty intact - and beside overclocking and some kernel tweaks and maybe easy nandroid backups/restore we can do quite alot.
---
@ the others with their flags still intact: Why so shy? Any success stories so far? This would get more attention if someone would confirm it working other than me hehe =). You all pushed me to make a script now use it! (try X-note for the start or smth .. thats what I'm using and it worked fine)

Cf root will trip the KnoX.
But samsung accepts one time warranty even if u tripped it.
This is my 3rd note, in 3 executive years. Ive never needed warranty. The golden rule with Samsung phones is if it works (hardware), it will stay to work for years. Just like German Mercedes from the '80s and '90 s.
Greetsz
Sent from my SM-N9005 using Tapatalk

but it's impossible to use your program without root? it's right. my phone it's already in rom MJ7, so, no soluce now to root without tripping the knox to 0x1..

Will i need to run scrtips once?
or before install more rom.

Will this wipe my phone? Dont wanna loose my data
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app

no it wont wipe data partition.
If you just use the "install" command it wont wipe anything, just copy over and overwrite the files that exist.
If you use the "new_rom" command it will wipe the system apps and the framework before installing.
If you come from odexed and want to install deodexed version you must use the "new_rom" command or else you will have odex files and some incompatible system apps left.
---
I'm also working on a way to backup and restore system as well as data.
What I really would like to know is what happens if you create an odin image from your system partition and flash that back with odin or mobileodin. It would just "restore" the system to the state where you created the image, but the question is if that would trip knox or not.
To be honest I doubt it would, since we only install a system image back that was already "ok" for knox - you already got the custom system partition flag when one uses RDLV or somehow else attains root access because the system is not unmodified, so this wouldnt change anything.
The only problem with my thinking would be if odin / mobileodin implements a special check thats only triggered when you flash through it and which will then trigger the knox flag if it finds a custom image.
If you find any stories of people who just flashed a (custom) system image through odin or mobileodin please point me there. So this question can finally be answered fully.
If we could just flash system images with odin while leaving out kernel and recovery and keeping knox, this would make custom recovery obsolete kind of. The only thing we still couldnt do then would be to use custom kernel features. So please help me to find out!

Yeah
So will new rom erase
game saves
Sms
Installed apps
Settings?
Okay if i find such thread ill post or pm it to you
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app

It shouldnt, although you might end up with other problems.. not 100% sure to be honest. (I only installed on freshly wiped device so far, or wiped afterwards etc, just to make sure)
Best thing to do is backup everything with titanium and then give it a try - but make sure you backup stuff to your external SD or copy it over to the pc, because the internal sd will get wiped if you have to factory reset. (just do a backup of everything with titanium and then copy the contents of your internal SD card (everything - to include game saves etc) to your pc.
If end up having to factory reset because of bugs from the old data you can just restore the apps with titanium and have your internal sd contents backed up.
---
If you give it a try (if you have the titanium backup and the internal sd contents you can always restore the old state at least) please report if you had to wipe data or if everything runs fine?
When I tested things around I did this already and the data stayed - but i did not test all the apps to really make sure.. so theres a small chance for problems - but I actually doubt it.

Performance tweaks for Redmi 3s and other devices - Flashable zips

Here are a few scripts I wrote for my device to boost up its performance. Few of them are written without being specific to any device or version of OS. For these general scripts (not specific to any device), download links are given at this first OP. For scripts which are specific to Redmi 3s, links are given at second post. These redmi 3s specific scripts install certain modified files such as service.jar and framework-res.apk.
All possible care has been taken to make general scripts work on all devices. Since I could check only on a few devices I could have access to, there could be a remote chance of not working on some devices. As devices vary on many accounts like OS version, customisation, configuration and file structure, for any eventuality, I recommend to take back up before proceeding with flashing of these zips.
Since the scripts are zipped in flashable zips, custom recovery (preferably TWRP) is must on your devices.
Here are general scripts with brief explanations.
1. Busybox installer zip: For various tweaks and init.d scripts to work properly, busybox is inevitable. This script installs Stericsons Busybox v1.24.2. If you have already busybox installed, no need of flashing this. Further flashing on the installed busybox may not harm.
Download Link: http://www.mediafire.com/file/s45tpufcy42h107/BusyBox-v1.24.2-Stericson.zip
2. Boot_patcher zip: This zip adds mount flags such as noatime, nodiratime, commit=60, nobarrier, noaudot_da_alloc, etc in fstab in boot.img and removes DM-verity. These flags have proved to increase IO on file systems. Many tweaks, I have noticed, put init.d script to remount partitions with these flags. But this zip does it directly at mount points at boot level obviating the need of init.d scripts.
Note: This zip is observed to break root enabled by Magisk. No need to worry. Just flash once again Magisk zip after flashing this zip. However, there is no problem of broken root if same is enabled by supersu.zip by chainfire.
Download Link:
http://www.mediafire.com/file/wshva78c456z1ub/boot_patcher.zip
3. Universal_journal_disabler zip: This zip makes journaling off on ext4 for system, data and cache partitions provided the partitions have been mounted on ext4 fs (if mounted on f2fs, it won’t touch those partitions). Journaling is a special control measure introduced from ext3 onwards. Journaling keeps track of changes made before writing on fs. This is useful in the scenarios of sudden power off or closure/crash due to any reasons for later restoration of changes made. This is not necessary on devices like mobile. But by default it is on. Since Journaling involves overhead on cpu, disabling the same is observed to improve performance considerably.
Note: Please flash this zip placing it on external memory, not on internal memory. Flashing from internal memory will not switch off journaling on data partition. So to ensure disabling journaling on data (which is essential for noticeable improvement), flash this zip placing it on external memory (external SD card) only.
Download Link:
http://www.mediafire.com/file/fmij6tnt8aebtyj/Universal_journal_disabler.zip
4. Permissive_selinux zip: In nougat custom roms, especially for Redmi 3s, selinux is enforcing. Enforcing selinux is seen to come in the way of many root apps though root enabled. One important issue I noticed that scripts at init.d folder were not running at boot due to enforcing selinux. Thus, I have made a small script to make selinux permissive on every boot by default. It takes care of file/folders created by supersu and magisk zip and accordingly puts the ‘setenforce 0’ in the appropriate folder.
Note: zip found not compatible with Magisk version 14
Download Link:
http://www.mediafire.com/file/qkimoscmfpu8x8a/permissive_selinux.zip
5. Ad_blocker zip: Nothing special about it. It just replaces hosts file in /etc folder for ad blocking. Important thing is about permissions assigned (rw_ r__ ___) for reducing impact of reading the big hosts file.
Download Link: http://www.mediafire.com/file/i50pr16umzp7h9q/ad_blocker.zip
6. Build_prop_patcher zip: This one has taken hell out of my time and patience. Not that it does any special thing, it simply inserts some build properties to build.prop file. But I wanted to make it such that it would search the intended build properties in build.prop file and changes the values thereof. If properties not found, inserts them at the end of file.
It is customisable zip. You can unzip and modify buildprop file according to your requirements. Special feature is it won’t add properties if present already with intended values. So, it is useful particularly to those who frequently flash roms with the result of losing added build.prop on every flash. Just flash this after flashing rom and have all your desired build.prop instantly.
Download Link: http://www.mediafire.com/file/c208fq98mixu9vx/build_prop_patcher.zip
7. Init.d script installer zip: I have collected some init.d scripts which I felt very essential and to implement on every device I have. Like build_prop_patcher zip mentioned above, herein also you can unzip the file and add your scripts to init.d folder therein, and make a permanent zip to flash every time you change your roms.
Note: For the scripts to work placed in init.d folder, you device should have been rooted and init.d enabled.
Download Link: http://www.mediafire.com/file/ot51sid37sfr0m8/initd_script_installer.zip
Credits:
@jcadduono for having heavily relied on his kernel flasher zip
@skynet28 for the method of journal disabling

Redmi 3s specifc
Here are Redmi 3s specific zips
1. Mm_rr_service_frmwrk_patch zip: This is meant for marshmallow resurrection remix rom as the modified service.jar and framework-res.apk used here for installation are from marshmallow resurrection remix rom. However, I think these modified files work on any marshmallow los based custom rom for redmi 3s.
In service.jar file, oom (out of memory) values for different categories of apps have been modified as below. As mentioned here, these oom values have resulted in turnaround of functioning of apps.
App category - old values - new values
Home ---------- 6 ---------- 0
Visible ---------- 1 ---------- 3
Previous ---------- 7 ---------- 5
Heavy ---------- 4 --------- 4
Service --------- 5 ---------- 6
Backup ---------- 3 ---------- 7
In all the custom roms, adaptive brightness is problematic, screen brightness is erratic on slight change in ambient light. So, I decompiled framework-res.apk, and changed autobrightness array values and found adaptive brightness afterwards comfortable.
Download Link:
http://www.mediafire.com/file/7y40j1x8dxp0bla/mm_rr_service_frmwrk_patch.zip
2. nougat_aex_frmwork_patch zips: Here also, I have modified services.jar and framework-res.apk files of nougat AEX roms. In services.jar, oom values have been modified as stated above, and in framework-res.apk also, autobrightness array values have been changed for smooth adaptation of screen brightness to ambient light. Since the services.jar and framework-res.apks used here are from AEX roms, zips are for AEX roms only. For each version of AEX rom (so far two versions, 4.5 and 4.6) for Redmi 3s, there is a separate zip which is to be flashed depending upon the version of AEX rom installed on your device.
For AEX v4.5
Download Link: http://www.mediafire.com/file/lxgd42fmfljxavv/nougat_aex45_svc_frmwork_patch.zip
For AEX v4.6
Download Link: http://www.mediafire.com/file/5bhawu1o226qdh3/nougat_aex46_svc_frmwork_patch.zip
3. nougat_rr_frmwork-res_patcher: This is for nougat resurrection remix roms. It also does the same thing of patching resources.arsc file in framework-res.apk for smooth adjustment of screen light to the ambient light.
Download Link: http://www.mediafire.com/file/luf4kslvttxss2d/nougat_rr_framework-res_patcher.zip
4. nougat_rr_svc_patch: This zip is for nougat resurrection remix roms. This installs patched services.jar with modified oom values as mentioned above (for the first zip in this post) for smooth functioning of apps.
Download Link: http://www.mediafire.com/file/61h9dz77zpxxuj9/nougat_rr_svc_patch.zip
5. adaptive_brightness_for_Oreo.zip: This is for overlaying the correct values of adaptive brightness in framework_res.apk for Oreo roms. Here, overlay feature of Oreo rom is being used instead of replacing modified framework_res.apk as done in the cases of zips for marshmallow and nougat roms above.
Download Link:http://www.mediafire.com/file/n77hsdvg9jx6pkp/adaptive_brightness_overlay.zip/file
6. persist_patch zip: This is for those who have corrupted persist files causing light, proximate and magnetic sensors not working.
Download Link:
http://www.mediafire.com/file/rrshneruhkdn8on/persist_patch.zip

Good work bro
Will it affect battery backup?

basiljose007 said:
Good work bro
Will it affect battery backup?
Click to expand...
Click to collapse
Definitely

shankar_vl said:
Definately
Click to expand...
Click to collapse
I mean positively or negatively? I prefer battery backup over higher performance, so asking

basiljose007 said:
I mean positively or negatively? I prefer battery backup over higher performance, so asking
Click to expand...
Click to collapse
both positively

Don't know if i will ever use these. But your hard work definitely deservers a vote of thanks.