Database Users

[WIN][July 22] Droid Manager v8.0 [Buys once, or use for Free!]

--------------------------------------------------------------------------------------------------------------------
{
"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"
}
--------------------------------------------------------------------------------------------------------------------
Articles About Droid Manager:
1. Droid Manager – Uma interface de gestão gráfica para o ADB
2. Droid Manager: When Doing Only a Few Things is Not Enough (Xda)
3. Droid Manager: Comprehensive ADB Front End & Management Suite For Android
4. Droid Manager Review - Droid-Now.com
5. Droid Manager Given Major Overhaul and New Functionality (xda)
6. Droid Manager Android PC Software fuer Root User - CHIP.de
--------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------
Requirements - Download Links - Features​--------------------------------------------------------------------------------------------------------------------
Requirements:
Rooted Android Device.
.Net Framework 4. (Download Here)
Fastboot & ADB drivers installed. (Check Here)
Android 2.1+
Device USB Debugging turned on (Settings -> Developer Options -> USB Debugging).
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Additional Features for Droid Manager Pro Only:
Connect and use multiple devices with Droid Manager
Adb Wifi: Connect your device with Droid Manager over wifi
Ability to perform multiple tasks at once (lite version of Droid Manager can only perform one task at a time)
Speed improvements
More to come in the future
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Buy Droid Manager Pro for 1.99$ - Fastspring.com - Official Website
Droid Manager Pro Features:
Media Sync Manager: Sync media files with from within the app, or simply right click on your media folder on your computer and Droid Manager will handle the rest.
Adb Wifi: Connect to Droid Manager using your Wifi connection (requires configuration to be applied on the device)
Add "Rename" to file browser, now files and folders can be renamed the same way files on your computer are renamed.
Minor UI Changes.
Droid Sync Manager is now part of Droid Manager Pro.
Send files from your Android smartphone to your computer
Send files from your computer to your Android smartphone using your phone.
Introducing Programs and Features Center with the following features:
Install additional features to Droid Manager.
Allow Droid Manager, SMS Center & Droid Sync Manager through firewall.
Control start up for programs installed using Programs and Features Center.
Be sure to check Droid Manager folder in Windows Start Menu.
Introducing Message Center:
Receive notification on your desktop about incoming text messages.
Compose a new SMS Message.
Reply to received SMS Messages.
Sync contacts with your computer.
Click to expand...
Click to collapse
Pay once and get all future updates and goods for free :good:
--------------------------------------------------------------------------------------------------------------------
Download Link:
If you like my work and would like to donate to me ( Here ) I appreciate it
Download Droid Manager v6.3 Released: June 23
Droid Manager Beta Downloads Released: October 11
Droid Manager RC Released: July 22
Download Cygwin.zip
Download Android App (Google Play Link)
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Quick Start Videos:​--------------------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------------------------------
Features:​--------------------------------------------------------------------------------------------------------------------
Notes you MUST know about:
USB Debugging Bridge must be turned on in device settings, can be found at: Settings -> Developer Settings -> USB Debugging
If You Can't Copy Files To Your Device:
CM Users please enable root access for ADB in: Settings -> Developer Settings -> Root Access, change it to allow Adb & Apps.
If problem exists for non-CM users use adbd Insecure
For Dealing with Boot.img, Download Cygwin (No Instillation Required for Cygwin, Unzip the downloaded file to where ever you want, and in Droid Manager "Boot Image" tab, point the program on where you have extracted the contents of the zip file.)
System Sounds must be in .OGG extension if you want to add your own. Droid Manager doesn't convert to .OGG
Rom management section is meant for noobs in custom rom building who only care about changing default apps, some build.prop values, kernel and user apps before they install a custom ROM
Back Up is created on SD Card, make sure USB Mass Storage Is disabled.
If you are experiacing lags when Browsing phone files, Copy / Delete ..etc. Please update your Superuser app & binary. If problem is still there please use adbd Insecure and patch your Adbd (you will know what to do once you open the app)
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Features mentioned below are found in both Lite and Pro version
--------------------------------------------------------------------------------------------------------------------
File Manager
Navigate through phone files / folders + SD Card files (no need to mount it)
Show Properties of desired file / folder
View / Edit permissions.
Rename files / folders.
Delete files / folders.
Create new files / folders.
Search for files on phone.
Move files.
Copy files / folders to PC
Copy files / folders from PC
Get files / folders copied from Windows explorer (Windows default file manager) by using "Paste from Clipboard" option.
Send any desired file / app to another phone by connecting the other device through wifi (using Droid Manager android app)
Backup selected file / folder directly to pc, or in the form of tar file.
View / Extract and Create Tar / Tar.gz files.
Create Shortcut to any folder on your desktop.
View / Edit any file (Text files, RC files, Scripts ..etc) from your device (Permissions will be handled by Droid Manager if you are editing System files)
Generate and Compare MD5 Sum
Extract HexDump for files.
View Partition Info
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Apk Manager
Install User / System Apps
Backup All apk files installed on device (system & user apps)
Backup any desired app with it's data.
restore apps / data
Install Apps on Sd Card.
Find apk files in specific Directory on Pc & install.
Send any app to another device connected via Wi-Fi (connected using Droid Manager android app).
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Build.prop Editor
Load build.prop File.
Edit build.prop file.
Save Changes back to device.
Recommended values already included.
Ability To Add Your Own Build.prop Values To List of Recommended Values.
Ability To Edit Existing Build.prop Values.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Init.d Script Manager
Add support for init.d scripts for stock kernel.
Check if currently installed kernel supports init.d script.
Add / Edit / Remove init.d scripts
Recommended scripts already included.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Bootanimation and System Sounds Manager
Change Boot Animation file.
Load System sounds (Alarms / Notifications / UI Sounds / Ring Tones)
Remove / Add new sounds.
View currently selected system sound file.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Backup Manager
Backup manager is about preventing device from boot loops after flashing theme / mod.
To Do: Browse to your desired zip file (Theme / mod), Backup manager will pull effected files from the device and create a zip file that can be flashed via your recovery installed on device.
In case of bootloops after flashing theme or mod, use the zip file created by Droid Manager to get things back to normal and make the device boot up again.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Fastboot Center
Execute Fastboot commands.
Flash any .img file
Erase paritions.
Use with cautious, using the wrong Fastboot command might wipe your device or brick it.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Custom Rom Tools
Browse Rom Files
Edit Build.prop File
Add / Remove System & User apps
View Application Info Like: Package Code Name, Code Version, Version Name, SDK Version, Target SDK, and Permissions.
Add / Remove or change boot animation.
Add / remove init.d scripts.
Edit / Write updater script.
Include Themes / Kernel Modules / Mods into your project.
Write your change log and keep track with changes you make for your project.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Wifi Transfer & Boot Image Tools
Send / Receive Files via Wifi
Supports Multiple file sending.
Supports for sending folders via Wifi. (result: sending folder C:MyMusic, will lead to all files in the "MyMusic" folder will be on the device in: /sdcard/MyMusic)
[*]If no directory was provided in the Android app while receiving, files will be saved in /sdcard/Droid_Manager
while folders will be saved on /sdcard/Name_of_Folder_You_Sent.
Unpack, edit and repack boot.img file.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Extras (The following options can be found in the "Rom Management & Device" tabs on top)
Mount System As Read / Write or Read Only
View Installed Modules
Install Modules Located on Device SD Card or on PC (Needs reboot of device)
Execute Custom ADB Commands
Extract Kernel Log File, Logcat and Recovery Log
Up Time info for the device.
Wipe Cache / Dalvik Cache / Data Partition
Create Nandroid Backup Without The Need To Reboot Device
Install & update onAndroid
One Click Tweak will edit build.prop file, provide support for init.d scripts if current kernel doesn't support and add init.d scripts.
Undo changes made by "One Click Tweak"
Install & update Superuser app.
Install & update SU Binary.
Update Busybox
Snap screenshot (it will be automatically pulled to PC.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Some Additions (The following options can be found in the "Extras" Tab on top)
Added Link To Facebook Page
Added Link To Google+ Page
Added Link To Suggest Ideas
Added Link To Report Errors
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
-- Feedback's are much appreciated, it helps me evaluate my work
--------------------------------------------------------------------------------------------------------------------
-- Change Log & Screenshots In Second Post.
--------------------------------------------------------------------------------------------------------------------
-- Thanks To regaw_leinad for providing AndroidLib which helped me in creating the windows app.
-- Thanks To Jimbo77 For This Tool Which Droid Manager Interacts With For UnPacking & RePacking Boot.img
-- Thanks To Ryuinferno For This Script For Enabling Init.d Support on Stock Kernel.
-- Thanks To ameer1234567890 For Online Nandroid Backup.
-- Thanks To iconfinder Got My Icons From There.
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------
Always Remember:
Please Don't mirror my files, I like to keep track of download count.
Report Bugs in this thread and I will fix them as soon as possible.
If you want any new feature I will be happy to work on including it (if it's possible).
If you like my app please rate it
Click to expand...
Click to collapse
--------------------------------------------------------------------------------------------------------------------​​
XDA:DevDB Information
Droid Manager, Tool/Utility for the Android General
Contributors
DeepUnknown
Version Information
Status: Stable
Current Stable Version: 6.3
Stable Release Date: 2014-07-22
Created 2013-10-11
Last Updated 2014-12-01

Android Client Screenshots

Full Change Log on Google Docs: Droid Manager Change Log
-----------------------------------------------------------------------------------------------------------------------------------------------------
Droid Manager v6.1.2 Stable
-----------------------------------------------------------------------------------------------------------------------------------------------------
New Features:
More UI changes.
Ability to view bootanimation file before applying it to device.
Speed improvements.
Click to expand...
Click to collapse
-----------------------------------------------------------------------------------------------------------------------------------------------------
Bug Fixes:
Fix bug that was causing the app for some users to either crash or not work at all.
Fix bug prevented files to be sent to device when using "Send To Android" from windows menu.
Click to expand...
Click to collapse
Change Log:
------------------------------------------------------------------------------------------------------------
List of Commands That Droid Manager Accepts:
droidmanager -o path_to_directory_on_device
This will start Droid Manager and navigate to path passed in the command.
droidmanager -s destination_on_device file1_onPC file2_onPC ..etc
This will copy file(s) from PC to destination address passed in the command.
System will be automatically remounted as RW.
More to come in the future.
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------------------------
Additional Screenshots
------------------------------------------------------------------------------------------------------------
​

I respect your work.Thank

john9 said:
I respect your work.Thank
Click to expand...
Click to collapse
Thanks for your comment

53 downloads and yet no feedbacks

2.1+
Does the current download include 2.1+ android app? all my devices are <4.0
looks clean!

ciscogee said:
Does the current download include 2.1+ android app? all my devices are <4.0
looks clean!
Click to expand...
Click to collapse
Sorry I forgot to include the 2.1+ app, will upload it right a way and send you the link in a PM

Ran it last night. I like the gui for actually seeing folders. Anyway to make an .img without 4ext though. I'm trying to figure out how to flash a deodexed /system to my phone.
Sent from my SPH-M580BST using Tapatalk 2

ciscogee said:
Ran it last night. I like the gui for actually seeing folders. Anyway to make an .img without 4ext though. I'm trying to figure out how to flash a deodexed /system to my phone.
Sent from my SPH-M580BST using Tapatalk 2
Click to expand...
Click to collapse
Actually I haven't implemented creating IMG files or flashing zip files. I'm trying to find a way to make it possible to create img files and flash zip files

Great job !
It would be nice to add the possibility to edit files permission

plopingo said:
Great job !
It would be nice to add the possibility to edit files permission
Click to expand...
Click to collapse
Actually you can change permissions, right click on any file / folder click properties and from there you will be able to change the permissions

DeepUnknown said:
Actually you can change permissions, right click on any file / folder click properties and from there you will be able to change the permissions
Click to expand...
Click to collapse
my bad, thanks you !

DeepUnknown said:
Actually I haven't implemented creating IMG files or flashing zip files. I'm trying to find a way to make it possible to create img files and flash zip files
Click to expand...
Click to collapse
I have a couple of ideas for you on these, check your pm.
ciscogee said:
Ran it last night. I like the gui for actually seeing folders. Anyway to make an .img without 4ext though. I'm trying to figure out how to flash a deodexed /system to my phone.
Sent from my SPH-M580BST using Tapatalk 2
Click to expand...
Click to collapse
I have an idea for you as well, check your pm.

plopingo said:
my bad, thanks you !
Click to expand...
Click to collapse
your welcome
---------------------------------------------------------------------------------------------------
Волк said:
I have a couple of ideas for you on these, check your pm.
Click to expand...
Click to collapse
Thanks, waiting for your PM

--

Just sent, sorry, I wanted to do some research on my own as well.

I connect the phone to the computer run the program. But it is always waiting for the phone.
What should I do?
I connect in both MTP and USB Storage...

ardicli2000 said:
I connect the phone to the computer run the program. But it is always waiting for the phone.
What should I do?
I connect in both MTP and USB Storage...
Click to expand...
Click to collapse
I'm sorry I forgot to mention it, USB Debugging (Settings -> Developer Options -> USB Debugging (or Android Debugging)) must be turned on

DeepUnknown said:
I'm sorry I forgot to mention it, USB Debugging (Settings -> Developer Options -> USB Debugging (or Android Debugging)) must be turned on
Click to expand...
Click to collapse
I turned on the USB Debugging and install .NET Framework 4.
Phone connected to program.
However, I edited build.prop. Saved it to the device. It said pushed to device. Reboot now?
I said "Yes". But nothing happened. Reboot myself. Check the build.prop and saw that nothing has changed.
What am I doing wrong??

[GUIDE] Beginners/Ref Guide to Making Roms.

Hi guys! I see many people trying to learn how to make roms, Here i show the easiest and shortest way on how anyone can begin making roms for the Galaxy S3. ​
Requirements:
Prepared CWM Stock Package.
Apktool
7-zip
Notepad ++
Setting Up, and Introduction​
IF you have downloaded firmware from sammobile instead of zoot1's package, use this part for Setting up and introduction: http://forum.xda-developers.com/showpost.php?p=37812381&postcount=33
OR ELSE THE EASIER WAY
To start with, Download the prepared CWM Stock Rom by zoot1 here: http://forum.xda-developers.com/showthread.php?t=1868004
I personally use firmware from sammobile, because i like to do everything myself. Though this method would be easier for beginners.
Extract the zip file to folder called "ROM".
Now lets head towards the customizing.
Thanks to Prawesome alot for this part. I took some info from his guide.
So now, open up the system folder. You'll find loads of folders in it. Here is a brief introduction to each of those folders:
1. apps
When you open this folder. You will find apk's. An apk is an install-able app package for any Android Device.
You can delete specific apps incase you want to delete. But take extra precautions on what you're deleting. As some apps are useful. You can add apps here as well in formats of apk's. But note, adding Play Store apps to the system/app folder is not recommended. For example you don't want Google Talk in your rom, you just have to delete the Talk.apk.
2. bin
Nothing really to mod in this folder. Full of advanced techy stuff. xD
3. etc
Here is where most of the tweaks come in. There is a folder called init.d where mods like the V6 Supercharger or multi-tasking fixes can be applied. Note! Don't add more than 1 or 2 scripts. Most of them usually conflict with each other.
In the gps.conf file, you can edit your gps info to make the gps more accurate. Pretty good guides about this, search them out.
Next is the hosts file. Devs use this to block sites from generating ads, and keeping their roms ad-free. Take a look at my DroidS3 hosts file, there are over 20,000 hosts blocked. You can use the same hosts file for your rom too.
4. Fonts
Very easy folder to understand. All you need to do here is replace ttf files, and you'll change the fonts.
5. Framework
Here is where the big mods come in. I'll explain further on about this. It contains the android.policy.jar, a useful element to add many mods. Framework-res is used to change wallpapers and theme the rom. I'll explain later.
6. libs
Contains all the libs needed for specific system apps to work. Don't mess here unless you're adding a mod.
7. Folders like csc, hdic, sipdb, wakeupdata, vendor, excetra..
These are the folders, there isn't much to do. Csc folder contains the feature.xml where some mods can be added. Search the forums for that. The rest contain multi-languages and more stuff.
8. xbin folder
Used to add scripts like busybox, dexdump, openvpn support. More like the bin folder but smaller.
9. Build.prop
Ever wondered how some roms have android 5.0, when it hasn't even released? All you need to change is the ro.build.version.release to any number you like. Even Android 20! Go change it, and fool some noobs out there. More mods can be added to this file. e.g:
Code:
debug.sf.hw=1
video.accelerate.hw=1
debug.performance.tuning=1
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.config.nocheckin=1
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.telephony.call_ring.delay=0
ro.lge.proximity.delay=15
mot.proximity.delay=15
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
ro.config.nocheckin=1
The codes listed above are for improving jpeg quality, saving some battery life, reducing call delay and more. Search for build.prop mods, you'll find loads of them. ​Now, a small explanation of the Meta-inf folder.
In Meta-Inf you'll find the updater-script.
Since this is aimed at beginners, I'll just show you how to change what text is shown during install in CWM.
Just edit what's in the quotes of the ui_print code in the file, and enter your own text. e.g:
Code:
ui_print("Hi, This message in quotes is displayed in recovery");
Modding!​
It's time for the modding to begin.
Get apktool from: http://forum.xda-developers.com/showthread.php?t=1755243
Now, first copy your framework-res from the /system/framework directory to where you extracted apktool files. Let's call this folder "apktool"
Open the folder apktool, press shift and right click. Click on "Open command window here". Type:
Code:
apktool if framework-res.apk
Now you are ready to decompile apk's.
I'm going to show you how to mod different files. Copy over:
SystemUI.apk
android.policy.jar
framework-res.apk
1. SystemUI.apk
Just showing you basic modding here. Copy over SystemUI.apk to apktool folder. In the command prompt, type
Code:
apktool d SystemUI.apk
After it's done, you should see a SystemUI folder in the apktool directory.
I'm going to show you how to make the status bar transparent, thanks to raubkatze for this part.
Navigate to res/layout/tw_super_status_bar.xml and change android:background to match the red line.
Code:
<com.android.systemui.statusbar.phone.StatusBarWindowView [B][COLOR="Red"]android:background="#00000000[/COLOR][/B]" android:focusable="true" android:fitsSystemWindows="true" android:descendantFocusability="afterDescendants"
xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:systemui="http://schemas.android.com/apk/res/com.android.systemui">
Save and close.
Then navigate to /res/values/drawables.xml
Edit to match:
Code:
<item type="drawable" name="status_bar_background">[COLOR="red"][B]#00000000[/B][/COLOR]</item>
That's it. Save and close.
Go back to your command prompt and type
Code:
apktool b SystemUI SystemUI-new.apk
After it's done, probably will take around 5-10 minutes. You'll find SystemUI-new.apk in your apktool folder. Open both SystemUI.apk and SystemUI-new.apk with 7-zip. Delete AndroidManifest.xml from SystemUI-new.apk and copy AndroidManifest.xml and META-INF from SystemUI.apk to SystemUI-new.apk
That's it. Close the zip files.
If you have adb or android-sdk push SystemUI-new.apk to your phone using:
Code:
adb remount
adb push SystemUI-new.apk /system/app/SystemUI.apk
adb reboot
If you don't have adb, just copy over SystemUI-new.apk to your phone. Rename it to SystemUI.apk and copy to system/app with root explorer. Reboot.
There you have transparent statusbar now! ​
2. android.policy.jar
Decompile android.policy.jar with:
Code:
apktool d android.policy.jar
You will find android.policy.jar.out, open it and use Cristiano Matos guide to mod the files: http://forum.xda-developers.com/showthread.php?t=2018633
After that use:
Code:
apktool b android.policy.jar.out
Open the android.policy.jar.out folder, you will find a dist folder created and inside that is your modified android.policy.jar.
You can use adb again by:
Code:
adb push android.policy.jar /system/framework
or the normal root explorer method. ​
3. framework-res.apk
Here i'll show you small mods.
Decompile it using
Code:
apktool d framework-res.apk
Navigate to res/values/bools.xml. ​Here you can add these. Thanks to DSA for this! :
4 Way Rotation:
Code:
Code:
<bool name="config_allowAllRotations">false</bool>
Change to:
Code:
Code:
<bool name="config_allowAllRotations">true</bool>
Lock Screen Rotation:
Code:
Code:
<bool name="config_enableLockScreenRotation">false</bool>
Change to:
Code:
Code:
<bool name="config_enableLockScreenRotation">true</bool>
and
Code:
Code:
<bool name="lockscreen_isPortrait">true</bool>
change to
Code:
Code:
<bool name="lockscreen_isPortrait">false</bool>
Disable Keyboard Switch In StatusBar When Typing
Code:
Code:
<bool name="show_ongoing_ime_switcher">true</bool>
Change to:
Code:
Code:
<bool name="show_ongoing_ime_switcher">false</bool>
Unplugging From USB doesn't Turn Screen On
Code:
Code:
<bool name="config_unplugTurnsOnScreen">true</bool>
Change to:
Code:
Code:
<bool name="config_unplugTurnsOnScreen">false</bool>[/indent]
Now to change wallpaper. Change the default_wallpaper.jpg in drawable-xhdpi and to change lockscreen wallpaper change keyguard_default_wallpaper.jpg.
Now recompile using:
Code:
apktool b framework-res framework-new.apk
Delete AndroidManifest.xml from framework-new. Copy AndroidManifest.xml and META-INF from framework-res.apk to framework-new.apk
To test use adb:
Code:
adb push framework-new.apk /system/framework/framework-res.apk
Or rename to framework-res.apk and copy to system/framework using root explorer. Reboot.​
Once you've added everything, your modified apks. Ui_print mods, A custom kernel (just replace boot.img) it's time to compile. Now this is really easy. Just highlight all the folders/files like system, meta-inf and boot.img. Right click. Hover over 7-zip and click Add to Rom.zip. Wait for it to be done, and copy Rom.zip to your sd card and flash. Voila! You've made your rom!!​
You can get more mods to add from here: http://forum.xda-developers.com/showpost.php?p=26583654&postcount=4
I was a beginner once, everyone was a beginner once. People helped me, and now I want to help people.
Press the Thanks button, and/or rate this thread 5 stars to show your support. ​
FAQ
- How do i add a mod?
To add a mod, just download it. Open it and copy over all the folders from the zip file EXCEPT the META-INF.
- How can i set up apktool on windows?
To set up apktool on windows, you need aapt, apktool.jar and apktool.bat
- My modified apk is not working?
Do some testing and get to know what went wrong. I'm always here. I'll be glad to help.
- Are these the only apps i can modify?
Ofcourse not! Any apk can be modified. Just decompile it, and make your changes.
- I'm looking for a guide on something i want to learn. Can you add it here?
I'll try my best.​​​

Reserved

Reserved one more.

Any feedback guys? I hope this is useful.
Forget that i had to reserve one more.

R: [GUIDE] Beginners/Ref Guide to Making Roms.
Looks interesting...when i will finish my exam i will check with more attention
Sent from my GT-I9300 using xda app-developers app

Willy89 said:
Looks interesting...when i will finish my exam i will check with more attention
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks. Glad it's of help.
Sent from my GT-I9300 using xda premium

Thnx for making this thread.
It's always useful to read thread's like this.
Nice job.
Verzonden door mijn GT-I9300 met xda premium

Great guide, thanks, I will point Theshawty in this direction :thumbup::thumbup:

slaphead20 said:
Great guide, thanks, I will point Theshawty in this direction :thumbup::thumbup:
Click to expand...
Click to collapse
Too late old man. Not interested in building roms anymore.

Thanks guys.
If there's anything you'd like to have added.
Let me know.

AW: [GUIDE] Beginners/Ref Guide to Making Roms.
Thanks. That's it what i searched for to start. Great.

weli..this would be intersting..and will c hw thread moves...

I Need Help In Building the ROM
Hi,
I am steinert. i need your help in biulding the rom, actually i finished everything but getting the problem while flashing the rom. when i googled it. i came to know that the problem lies in updater-script. i used root explorer to find out the reason. it was like.
FINISHED EXECUTING SCRIPT FILE
EXIT VALUE:126
STDOUT:
NULL
STDERR:
SH:<STDIN>[1]:/CACHE/RECOVERY/LAST_LOG:CAN'T EXECUTEERMISSION DENIED.
I Hope that You help a NOOB like me....
Thank you in advance....

Jacqueline Steinert said:
Hi,
I am steinert. i need your help in biulding the rom, actually i finished everything but getting the problem while flashing the rom. when i googled it. i came to know that the problem lies in updater-script. i used root explorer to find out the reason. it was like.
FINISHED EXECUTING SCRIPT FILE
EXIT VALUE:126
STDOUT:
NULL
STDERR:
SH:<STDIN>[1]:/CACHE/RECOVERY/LAST_LOG:CAN'T EXECUTEERMISSION DENIED.
I Hope that You help a NOOB like me....
Thank you in advance....
Click to expand...
Click to collapse
After flashing the rom.
Check the error through Advanced > Show recovery log in recovery.
Post results here.

I : checking for entendedcommand..
I : skipping execution of extendedcommand, file not found...

Jacqueline Steinert said:
I : checking for entendedcommand..
I : skipping execution of extendedcommand, file not found...
Click to expand...
Click to collapse
Huh?
Get me a screenshot of your meta-inf/com/google/android directory.
What exactly did you modify? It should work if you left the meta-inf untouched.

masterex567 said:
Huh?
Get me a screenshot of your meta-inf/com/google/android directory.
What exactly did you modify? It should work if you left the meta-inf untouched.
Click to expand...
Click to collapse
I just removed all the apps and inserted new apps...!!
Should i send you my updater-script?

Jacqueline Steinert said:
I just removed all the apps and inserted new apps...!!
Should i send you my updater-script?
Click to expand...
Click to collapse
Removed all?
Some are core apps like SystemUI, etc.
Get me a screenshot of your rom.zip..

masterex567 said:
Removed all?
Some are core apps like SystemUI, etc.
Get me a screenshot of your rom.zip..
Click to expand...
Click to collapse
{
"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"
}
This is the screenshot of my rom..! and before also i got the same problem with out changing the system .apk's

Jacqueline Steinert said:
View attachment 1700664
This is the screenshot of my rom..! and before also i got the same problem with out changing the system .apk's
Click to expand...
Click to collapse
Highlight those 3 and in 7zip options click add to " ".zip
Sent from my GT-I9300 using xda premium

[ TOOL ][ SYSTEM | NORMAL ][ APP-MOD-MAKER ] Juno - 1.6 [divinemamgai]

{
"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"
}
New Version Out! - 1.6
Juno utilizes the features of a program called APK – Tool, and pushes it to another level, the level of ease! Now even if you are not aware of what is required to create fully functioning system apps for your Rom or Device, you can still make some pretty basic mods with this tool, OR you can go pro and create some pretty awesome mods! (Well for that you will need to know how to edit smali files and other xml files of system apps properly)
With this tool you easily Pull system apps from your phones /system/app directory and start editing them. Once done you can easily build the modified version of the system app and can instantly install them to your phone!
(Please refer to the section How to use? Before doing anything idiotic.)
Once done you can also get cleared of all the residual files too with just one single command.
At last I want to state this with all caution – You are using this tool on your own risk! Any damage done to your device is completely your fault and I’m not to be blamed for any kind of damage done to your device.
​
Step - 1 : Setting Up your PC!
Download The following resources first:
Android SDK [ Draw-Patch.9 Tool ]
Java SE Run-time Environment 7 [ Java Dependencies For APK - Tool ]
Now let's begin setting up your PC,
Install the above mentioned programs.
Go to Advanced System Properties.
It looks like this:
Go to Environment Variables, then create a new System Variable, having name JAVA_HOME and value as the path where you have installed the JRE.
It looks like this:
Now after creating the JAVA_HOME variable, search for Path system variable in the System Variables list. Now this is a bit tricky. Once found click on it and then on Edit. Move the cursor to the end of the string till you see ";" (without quotes), add the path to your JRE bin folder just after it.
It looks like this:
OK, so if everything went fine and just as what instructed then you are all good to proceed to Step - 2!
Step - 2 : Installing Juno!
First download the zip provided at the download section of this post, then extract it and execute the Juno.[Current-Ver].exe (eg. Juno.1.1.exe) setup file.
It looks like this:
Now click Next. In the next window if you want to change the directory of the Juno then just press Browse and choose your custom directory. If done click Next.
It looks like this:
In the next windows just press Next, and let the program to be installed on your PC!
It looks like this:
In the preceding window click on Run Juno if you want to execute the program now or just press Finish.
It looks like this:
Step - 3 : Setup the Program!
Open the program, Juno, from start menu or from the directory itself.
Please open the program in Administrator mode, by right clicking and selecting Run As Administrator. This is necessary for ADB and APK - Tool to work properly.
Note: If you have installed the program in a Drive which is not protected by Administrator Rights, then you can skip running it as Administrator.
It looks like this:
Now first enable USB - Debugging in your phone and connect it via a USB - Cable to your PC [ If you have any doubt on how to do that please refer to screens below. ]
Need help?:
In the Juno program console enter the command LOADRESOURCES and press Enter. Then enter PULL and press Enter and sit back and relax till the program loads all the necessary Resource files from your device.
It looks like this:
The Juno program usually only pulls and installs the Resource files of CM based roms automatically and also for the Xperia Stock roms. So if you are using any of those then just skip the preceding steps.
But for other Roms or Phones the developers will need to extract the required resource files from their devices or roms. For that follow the preceding steps:
Extract the required Resource files in to the main directory of the program. This can be done by using PULL command of the program or by manually retrieving required files.
Then while in the program, enter LOADRESOURCES, and then enter CUSTOM.
Enter the File-Name of the Resource file you just copied to the main directory. (Only the file-name no extensions!) And press Enter.
Now let the program complete the process, if you see no errors then everything has been completed just fine.
Now repeat the same with all the other Resource files.
Need help?:
If all the above mentioned steps have been completed successfully, then your program copy is ready to be used!
​
From Version 1.3, the How to use guide will be included with the program,i.e, in the form of Read Me.
Copy the apps you want to mod in the pulled directory of the program, if you want to do that manually, but you can even pull apps from your device using PULL command.
But for lower functions please refer to the section below.
The following section is going to cover all the functions supported by this program.
Legend - Function-Name [ Function-Code ]
Just enter the Function-Code given for each defined function below in the program to start that function.
Load Resources [ LOADRESOURCES ]
This function will allow you to load the necessary resource files which are needed by the APK – Tool to decompile the required system apps.
The sub-functions which this section includes are –
PULL – This function is for pulling the required resources straight from your device. [Note: It will only efficiently work for CM based or Stock Xperia roms and for other roms please use the sub-function CUSTOM]
INSTALL – This function will install the resource files automatically which you have copied in the res directory of the program. [Note: It will only efficiently work for CM based or Stock Xperia roms and for other roms please use the sub-function CUSTOM]
CUSTOM – This function is to be used when you require to install extra resource files of your rom. You have to provide the file-name of the custom resource file which you have to copy or pull from your device to the root directory of the program. And it will be automatically installed.
Mod [ MOD ]
This function allows you to mod your system apps. You have to enter the file-name of the system app which you have copied to or pulled to the root directory of the program. The program will automatically decompile or compile depending on the fact that what has already been done.
If the app is not compiled, then the program will first make a backup of the system app [Note: Please do not delete the backup folder under any circumstances as it may lead to false build, which will damage your device!]
Then the program will decompile the app and it will be available for the user to mod it in the working directory of the program.
If the app is already decompiled then the program will compile the edited app (irrespective of the fact that it has been edited or not.) and will generate a complete build in the build directory of the program, which will be ready to install to your device, keeping in mind that no error has occurred.
Delete [ DELETE ]
This function is used to get rid of the residual files after your entire project has been completed.
This function will delete the working folder and the backup folder without prompting, whereas the Main app file and the Build app file deletion will be prompted.
You just have to enter the file-name of the app you want to get rid of, and rest will be handled by the program itself.
Pull [ PULL ]
This function is used to pull or get the system apps from your device. But for that your device must be connected in USB – Debugging Mode.
You just have to enter the file-name of the app you want to pull or get from your devices /system/app/ directory. The app will be stored in the root directory of the program.
Install [ INSTALL ]
This function will let you install the build app to your device. But for that your device must be connected in USB – Debugging Mode.
You have to enter the file-name of the app you want to install. The app must have to be built to be installed.
Restart of the device is mandatory right after you have installed the app.
Exit [ EXIT ]
This function will exit the program.
​
Current Version - Juno.1.6
Download Juno -
Juno.1.1
Download
File Size: 5.99 MB (6283847 bytes)
Juno.1.2
Download
File Size: 6.09 MB (6387181 bytes)
Juno.1.3
Download
File Size: 6.10 MB (6397218 bytes)
Juno.1.4
Download
File Size: 6.10 MB (6397661 bytes)
Juno.1.5
Download
File Size: 6.34 MB (6643420 bytes)
Juno.1.6
Download
File Size: 6.32 MB (6629667 bytes)
​
Juno.1.6
Similar to that of 1.5.
Juno.1.5
Juno.1.4
Juno.1.3
Juno.1.2
​
​

Change - Log
Juno.1.1 - 28th Sept. 2013
Initial Release
Options for Pulling and Installing apps directly to phone are added.
Options to Pull required resources from the phone directly are added.
Use of independent installer.
Juno.1.2 - 5th October 2013
Bug - Fixes
User - Interface changes.
Some minor under-the-hood changes.
Directory structure re-defined i.e. APK - Tools files are moved to a folder named apktool and some other files are moved to res directory in order to make the programs main directory look clean.
Capability to mod framework files and other Google Play apps (some) made official. (Note: This can be also done in the previous version too.)
Juno.1.3 - 9th October 2013
Bug - Fixes
User - Interface changes.
Some minor under-the-hood changes.
Added new feature to Pull Resources from a defined directory in your devices system folder.
Juno.1.4 - 14th October 2013
Bug - Fixes
Added support to create compressed apps! With some compressed over 50% compression ratio.
Juno.1.5 - 18th October 2013
Added Option to create compressed or non-compressed builds.
Added notification sounds to keep you posted when program has completed it's procedures, or when it ask for compression of the builds.
Minor UI changes.
Juno.1.6 - 3rd November 2013
Minor UI fixes.
Last Version.
Build with different compiler.
​

Oh! Thanq so much! You made dat more easier..
Sent from my MT27i using xda app-developers app

cpkunki said:
Oh! Thanq so much! You made dat more easier..
Sent from my MT27i using xda app-developers app
Click to expand...
Click to collapse
Welcome buddy, I hope you will love the upcoming version! Well it has already been finished, I'm just waiting for the release date to come.

divinemamgai said:
Welcome buddy, I hope you will love the upcoming version! Well it has already been finished, I'm just waiting for the release date to come.
Click to expand...
Click to collapse
Oh! I tried it out! Thats great!
Even i am waiting for the next release.
Thanks again.
Sent from my MT27i using xda app-developers app

cpkunki said:
Oh! I tried it out! Thats great!
Even i am waiting for the next release.
Thanks again.
Sent from my MT27i using xda app-developers app
Click to expand...
Click to collapse
Next release is out there...!!! :laugh:

[BUG REPORT] oat2dex breaks OpenGL/Play Store SOLVED!

EDIT: The latest oat2dex solves this issue altogether.
WTF IS THE PROBLEM?
The OpenGL and Google Play Store refuse to work because baksmali inside the oat2dex tool misinterprets some fields in a single smali file and breaks "services.jar" when deodexing, and the main problem it causes is mistakenly setting your OpenGL version to 0 (instead of 3), basically disabling it.
oat2dex, for some reason, flips just a few specific fields (name and type) when deodexing, as if there is an ambiguity between 2 fields on the same offset.
When you flash the deodexed services.jar back to your phone and clear dalvik-cache, Android re-optimizes it (takes the "classes.dex" inside your new JAR file, does dex2oat on it, and saves it in /data/dalvik-cache/arm/). The deodexed file is broken, so that optimized file is broken too.
You take that broken odex file from dalvik-cache and deodex it again. Since it contains those flipped field names, this time it flips them again but to the correct fields.
The result DEX file you get by that second deodexing is a properly working DEX file, and if you rename it to "classes.dex" and replace "classes.dex" inside your broken "services.jar", you'll get a working "services.jar" and all your OpenGL and Google Play Store problems will disappear immediately.
HOW TO QUICKLY GET A WORKING DEX?
* Extract classes.dex from the JARs, rename them to framework.dex and services.dex.
* Copy them to your internal SD.
* Enable "USB debugging" in Developer options.
* Connect your device to your PC and open Command Prompt:
Code:
[B]adb shell[/B] (confirm ADB on your device)
[B]su[/B] (confirm SU on your device)
[B]dex2oat --dex-file=/sdcard/framework.dex --oat-file=/sdcard/framework.odex[/B]
[B]dex2oat --dex-file=/sdcard/services.dex --oat-file=/sdcard/services.odex[/B]
* Copy these odex files to your PC and deodex them again with oat2dex.
* Rename the new framework.dex and services.dex to classes.dex and add them to their JARs, replacing the broken classes.dex.
JARS AFFECTED BY THIS BUG
framework.jar/classes.dex --- only a single non-critical error in NumberPicker.smali (classes2.dex is fine)
http://forum.xda-developers.com/attachment.php?attachmentid=3338076&d=1432918042
services,jar/classes.dex --- Total of 8 errors, described below...
http://forum.xda-developers.com/attachment.php?attachmentid=3335118&d=1432772056
BUG REPRODUCTION
Requirements:
1) Java installed
2) oat2dex_bug.zip
ZIP contents:
* baksmali.jar
* oat2dex.jar
* boot.oat --- taken from /framework/arm/
* services.dex --- this is "classes.dex" from the deodexed "services.jar" (which breaks OpenGL)
* services-from-dcache.odex --- this is the odex file taken from "/data/dalvik-cache/arm/" that was created by Android after flashing the broken deodexed "services.jar" and clearing dalvik-cache
Reproduction steps:
1) Open "oat2dex_bug" folder, right-click inside it and then select "Open command window here".
2) Write the following lines exactly as follows:
java -jar oat2dex.jar boot boot.oat
java -jar oat2dex.jar services-from-dcache.odex odex
java -jar baksmali.jar -o services-from-dcache services-deodex.dex
java -jar baksmali.jar -o services services.dex
3) With WinMerge, compare folders "services" and "services-from-dcache".
You'll see that only one file has differences, and it's "ActivityManagerService.smali", that's the file you need to fix.
{
"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"
}
In the above images are the only affected areas you need to fix.

Holy @#%. Well done! This issue was a real pain. Thanks

What about fixing framework.jar ? Play store compatibility ?
Sent from my C6903 using XDA Free mobile app

dstrikersZ1 said:
What about fixing framework.jar ? Play store compatibility ?
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
framework.jar has only 1 error in NumberPicker.smali, and it's not very critical. Has nothing to do with the Play Store bug. After you've fixed services.jar by deodexing it twice, Play Store is fixed.

IaguCool said:
WTF IS THE PROBLEM?
The OpenGL and Google Play Store refuse to work because baksmali inside the oat2dex tool misinterprets some smali files and breaks "services.jar" when deodexing, and the main problem it causes is mistakenly setting your OpenGL version to 0 (instead of 3), basically disabling it.
oat2dex, for some reason, flips just a few specific fields (name and type) when deodexing, as if there is an ambiguity between 2 fields on the same spot.
When you flash the deodexed services.jar back to your phone and clear dalvik-cache, Android re-optimizes it (takes the "classes.dex" inside your new JAR file, does dex2oat on it, and saves it in /data/dalvik-cache/arm/). The deodexed file is broken, so that optimized file is broken too.
You take that broken odex file from dalvik-cache and deodex it again. Since it contains those flipped field names, this time it flips them again but to the correct fields.
The result DEX file you get by that second deodexing is a properly working DEX file, and if you rename it to "classes.dex" and replace "classes.dex" inside your broken "services.jar", you'll get a working "services.jar" and all your OpenGL and Google Play Store problems will disappear immediately.
JARS AFFECTED BY THIS BUG
framework.jar/classes.dex --- only a single non-critical error (classes2.dex is fine)
services,jar/classes.dex --- described below
BUG REPRODUCTION
Requirements:
1) Java installed
2) oat2dex_bug.zip
ZIP contents:
* baksmali.jar
* oat2dex.jar
* boot.oat --- taken from /framework/arm/
* services.dex --- this is "classes.dex" from the deodexed "services.jar" (which breaks OpenGL)
* services-from-dcache.odex --- this is the odex file taken from "/data/dalvik-cache/arm/" that was created by Android after flashing the broken deodexed "services.jar" and clearing dalvik-cache
Reproduction steps:
1) Open "oat2dex_bug" folder, right-click inside it and then select "Open command window here".
2) Write the following lines exactly as follows:
java -jar oat2dex.jar boot boot.oat
java -jar oat2dex.jar services-from-dcache.odex odex
java -jar baksmali.jar -o services-from-dcache services-from-dcache.dex
java -jar baksmali.jar -o services services.dex
3) With WinMerge, compare folders "services" and "services-from-dcache".
You'll see that only one file has differences, and it's "ActivityManagerService.smali", that's the file you need to fix.
And here are the only differences you find in the file (notice especially the first one and the last one):
Click to expand...
Click to collapse
java -jar baksmali.jar -o services-from-dcache services-from-dcache.dex
Click to expand...
Click to collapse
Error: "Can´t find the file services-from-dcache.dex"
There is no such file in the zip either - only services-from-dcache.odex, but with this file it did not work

moonryder said:
Error: "Can´t find the file services-from-dcache.dex"
There is no such file in the zip either - only services-from-dcache.odex, but with this file it did not work
Click to expand...
Click to collapse
Then you made a mistake somewhere.

IaguCool said:
Then you made a mistake somewhere.
Click to expand...
Click to collapse
tried it again, step 1 and 2 without problems, but step3 the same error as mentioned before
there is a new file in the folder called "services-deodex.dex"

moonryder said:
tried it again, step 1 and 2 without problems, but step3 the same error as mentioned before
there is a new file in the folder called "services-deodex.dex"
Click to expand...
Click to collapse
Ahh I see that oat2dex renames the file for some reason. I fixed line 3 to
java -jar baksmali.jar -o services-from-dcache services-deodex.dex
You could figure that out yourself, you know... by looking inside the folder, I don't see why you repeat every step like a robot uncritically.

IaguCool said:
...I don't see why you repeat every step like a robot uncritically....
Click to expand...
Click to collapse
cause i am not a programmer and a noob in this field contrary to you (maybe you are a genius and i am a little user :angel: )

moonryder said:
cause i am not a programmer and a noob in this field contrary to you (maybe you are a genius and i am a little user :angel: )
Click to expand...
Click to collapse
So basically it's like pushing a screwdriver into a wall socket without knowing what electricity is... I don't get why people that don't develop even try to deodex themselves in the first place. Deodexing is meant for developers, not "little users"...

so its must to be writen GL_ES_VERSION:I
its i/1/L ?

Alvian_P said:
so its must to be writen GL_ES_VERSION:I
its i/1/L ?
Click to expand...
Click to collapse
It's "I" for Integer. Seriously what are you people doing here? It's for *developers*, normal users have nothing to gain from this process.

That's how I have fixed it too, well done
Take care that mWentToSleep must also be fixed.
Both lines are inverted.
Edit: nevermind, your method is inverting both... I did it manually.

Please tell what command compiles the folder "services" into file "services.dex" back?

Bazooka Joe said:
Please tell what command compiles the folder "services" into file "services.dex" back?
Click to expand...
Click to collapse
Google for "smali-2.0.5.jar" for that. baksmali only decompiles.

IaguCool said:
It's "I" for Integer. Seriously what are you people doing here? It's for *developers*, normal users have nothing to gain from this process.
Click to expand...
Click to collapse
@laguCool
1. thx for discovering that problem and its solution
2. all devs began once upon a time, so i think threads like this one are very helpful for users who want to learn and become a dev in future too. So
3. please be soft with all of them who asks questions here.
Thx again for your excellent work and knowledge.
m.

moonryder said:
@laguCool
1. thx for discovering that problem and its solution
2. all devs began once upon a time, so i think threads like this one are very helpful for users who want to learn and become a dev in future too. So
3. please be soft with all of them who asks questions here.
Thx again for your excellent work and knowledge.
m.
Click to expand...
Click to collapse
Well, being soft isn't my thing, it's against my nature...
Anyways, if a person doesn't know what "I" means in Dalvik opcode, they are doing the learning process wrong. They need to be familiar with Dalvik datatypes beforehand.

IaguCool said:
It's "I" for Integer. Seriously what are you people doing here? It's for *developers*, normal users have nothing to gain from this process.
Click to expand...
Click to collapse
just look around , anyways my college is IT
ah sorry if this thread not open for normal users

IaguCool, Big, big Thanks!!! OpenGL worked now! :good:
There is a more simple way for obtain dirty odex from dirty dex file. Just copy deodexed services.dex to sdcard and type in terminal
dex2oat --dex-file=/sdcard/services.dex --oat-file=/sdcard/services.odex
Then copy created /sdcard/services.odex to PC and deodex them again to obtain correct services.dex.

_SIL_ said:
IaguCool, Big, big Thanks!!! OpenGL worked now! :good:
There is a more simple way for obtain dirty odex from dirty dex file. Just copy deodexed services.dex to sdcard and type in terminal
dex2oat --dex-file=/sdcard/services.dex --oat-file=/sdcard/services.odex
Then copy created /sdcard/services.odex to PC and deodex them again to obtain correct services.dex.
Click to expand...
Click to collapse
Thank you I rarely use the terminal so I missed that. I actually copied all /framework/ odex files from dalvik-cache to see if there are more JARs affected by this bug, will add them to the list if I find any.

[Guide] [ROOT Required] Installing Viper4Android on Lollipop

What you will need:
To be on Lollipop WITH root (go here if you need to flash the rooted ROM)
BusyBox to be installed (it should already be installed on the rooted ROM, if not then search the Play Store or use your favorite one)
A copy of Viper4Android v2.3.4.0 (Download from here)
A file browser that can access the /system partition and change permissions (I prefer ES File Explorer but you can use whatever you like)
Titanium Backup (or you can use the application manager in the Settings app)
Firstly, what you will need to do is use your file browser and create a folder called "Viper4Android" in your /system/priv-app/ folder. Set the permission for this folder to rwxr-xr-x or 0755, then paste your Viper4Android APK into the folder you created and set the permission for the APK to rwxrwxrwx or 0777, with root being owner and group for both folder and APK.
Secondly, what you will need to do is browse to /system/etc/ with your file browser and open the file init.qcom.post_boot.sh and at the very bottom of the file paste this:
Code:
/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
It is imperative that you make sure you are using Unix line endings instead of anything else.
Thirdly, use Titanium Backup or the Application Manager to freeze SoundAlive, as all music apps will attempt to default to it. Also you may want to freeze the Adapt Sound app, as if you enable it will then be used over V4A.
Lastly, reboot your phone and then install the drivers and reboot one last time. I can confirm that it works on Play Music, and that it doesn't work on the stock Music player (however I believe there is a way to get it to work somewhere on the internet).
Problems:
Viper4Android fails at installing!
Click to expand...
Click to collapse
You are to create it as a system app, so follow the first step.
Viper4Android doesn't appear!
Click to expand...
Click to collapse
Make sure you followed the first step correctly and set the proper permissions.
Viper4Android still says Abnormal and Unsupported in the status!
Click to expand...
Click to collapse
Make sure you pasted the command into the init.qcom.post_boot.sh file and that you used Unix line endings, as using DOS or Mac line endings add extra characters that Android will try to parse as actual text.
Viper4Android says that BusyBox isn't installed!
Click to expand...
Click to collapse
This bug happens sometimes, I found the best way to beat it is to open your BusyBox app and just put it in the background and try the driver installation again.
I enabled everything and my music still sounds the same!
Click to expand...
Click to collapse
Make sure you freeze SoundAlive and Adapt Sound, as they will be used before Viper4Android, also you may need to put V4A into Compatibility mode to use with certain music players. Also you can't use the stock Music player (but I think there is a way somewhere on the internet).
My phone broke and won't boot!
Click to expand...
Click to collapse
Then you may want to wait until a recovery flashable zip is made, but at no point are the steps going to brick your phone, you can just boot to Safestrap or flash back.
Notes:
This process can probably be done very easily with a init.d script and a recovery flashable zip, but I currently don't have the time and don't want to risk screwing up someone's phone.
You can use any other Viper4Android mod, as long as it is v2.3.4.0, I prefer this version which looks very nice. You can extract the file from the zip attachment and just follow the steps here.
You do not need to have SELinux set to permissive, as even with using MultiSystem to set it to permissive, it still didn't work until the above command is used.
I haven't tested whether effects like convolver or DDC work, but they should.
Thanks to:
@ihancioglu for the code that allows it to work
@nappent for most of the steps needed to get it running
EXTRA:
Here is an init.d script that will do the bypass for you, however, you must have init.d support. As it stands right now, Walter.White's Lollipop ROM does not have init.d, if you want to enable init.d, you have to add
Code:
/system/etc/init.d/*
to the end of init.qcom.post_boot.sh and create an init.d folder in /system/etc.
Script: https://mega.nz/#!ZpIUCbrb!QONi8bWb1afE47_JnwxgpBcXoKFuPG3mpnyFX4r83G0

What process did you use to be able to write to the root. I can not gain root access even though i have su, busybox, and several other apps with root access. I have tried using ES File explorer with no success. It will not access the root of the device.
---------- Post added at 09:31 PM ---------- Previous post was at 08:35 PM ----------
100% verified and working. Big thanks!!!

Works perfectly. Thanks for this work around OP!
Any thoughts on using NuPlayer vs. AwesomePlayer in dev. options?
{
"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"
}
joshuaburnsjr said:
What process did you use to be able to write to the root. I can not gain root access even though i have su, busybox, and several other apps with root access. I have tried using ES File explorer with no success. It will not access the root of the device.
---------- Post added at 09:31 PM ---------- Previous post was at 08:35 PM ----------
100% verified and working. Big thanks!!!
Click to expand...
Click to collapse
Root Browser worked for me.

KTownGT said:
Any thoughts on using NuPlayer vs. AwesomePlayer in dev. options?.
Click to expand...
Click to collapse
I use NuPlayer, but to be honest I haven't seen or heard of any difference. Some guides say that disabling NuPlayer will allow V4A to work, but V4A has worked just perfectly fine with NuPlayer enabled.
Among other things, creating a recovery flashable zip has fallen through. I have come across a problem where I can't modify init.qcom.post_boot.sh from a recovery, be it SafeStrap or FlashFire. I have also discovered something else, init.d support was supposed to be included with Walter.White's Lollipop ROM, but his script encountered the same problem as me, it couldn't append to init.qcom.post_boot.sh. So right now anyone using his ROM does not have init.d setup, luckily, it can be very easily enabled. All you have to do is add
Code:
/system/etc/init.d/*
to the end of init.qcom.post_boot.sh and create an init.d folder in /system/etc and you are good to go. I have attached an init.d script to the main post that can make use of init.d and do the bypass.

Namelesswonder said:
I use NuPlayer, but to be honest I haven't seen or heard of any difference. Some guides say that disabling NuPlayer will allow V4A to work, but V4A has worked just perfectly fine with NuPlayer enabled.
Click to expand...
Click to collapse
Exactly why I asked... lol
Looks like it is only required when setting SELinux to permissive; which doesn't appear to be required. You literally saved me from going back to 4.4.2, just for V4A btw:good:
Namelesswonder said:
Among other things, creating a recovery flashable zip has fallen through. I have come across a problem where I can't modify init.qcom.post_boot.sh from a recovery, be it SafeStrap or FlashFire. I have also discovered something else, init.d support was supposed to be included with Walter.White's Lollipop ROM, but his script encountered the same problem as me, it couldn't append to init.qcom.post_boot.sh. So right now anyone using his ROM does not have init.d setup, luckily, it can be very easily enabled. All you have to do is add
Code:
/system/etc/init.d*
to the end of init.qcom.post_boot.sh and create an init.d folder in /system/etc and you are good to go. I have attached an init.d script to the main post that can make use of init.d and do the bypass.
Click to expand...
Click to collapse
Answers my second question about init.d. :good:
Have been debating whether to stay on Alliance or go back to OTA, seeing as how I don't use the customization settings & need NFC

KTownGT said:
Exactly why I asked... lol
Looks like it is only required when setting SELinux to permissive; which doesn't appear to be required. You literally saved me from going back to 4.4.2, just for V4A btw:good:
Answers my second question about init.d. :good:
Have been debating whether to stay on Alliance or go back to OTA, seeing as how I don't use the customization settings & need NFC
Click to expand...
Click to collapse
I originally stayed off of Lollipop for a month because I couldn't get V4A to work, but I tried to find a solution after people got it working on the Galaxy S6.
I made this guide because using MultiSystem to set SELinux to permissive did not fix the issue. It was like the policies for SELinux were still being enforced. Also, I made a mistake for the init.d code, it should be
Code:
/system/etc/init.d/*
. Currently stock rooted Lollipop is ok, with Xposed now working and Wanam just recently updated you can make stock usable now.

Namelesswonder said:
I originally stayed off of Lollipop for a month because I couldn't get V4A to work, but I tried to find a solution after people got it working on the Galaxy S6.
I made this guide because using MultiSystem to set SELinux to permissive did not fix the issue. It was like the policies for SELinux were still being enforced. Also, I made a mistake for the init.d code, it should be
Code:
/system/etc/init.d/*
. Currently stock rooted Lollipop is ok, with Xposed now working and Wanam just recently updated you can make stock usable now.
Click to expand...
Click to collapse
Same pretty much. It's painful going from using V4A & a USBDAC to straight LP.

working perfectly.. thanks

Works amazing jus one question the download from mediafire has two different apps both the same version which should I have installed

Works for me! Thanks.
Sent from my SAMSUNG-SM-N900A using Tapatalk

Orion.Lamas said:
Works amazing jus one question the download from mediafire has two different apps both the same version which should I have installed
Click to expand...
Click to collapse
On V4A's website?
There should be an APK for before JB, and one for KK/LP. You should use the one that's like"V4A_FX_4.x.apk"
Sent from my iPad using Tapatalk

Thanks OP! Got it all working and the sound quality has definitely improved. Question though, in past versions I loved adjusting the IRSamples. Is that no longer a thing in this latest version?

Viper4android worked again!
Namelesswonder said:
What you will need:
To be on Lollipop WITH root (go here if you need to flash the rooted ROM)
BusyBox to be installed (it should already be installed on the rooted ROM, if not then search the Play Store or use your favorite one)
A copy of Viper4Android v2.3.4.0 (Download from here)
A file browser that can access the /system partition and change permissions (I prefer ES File Explorer but you can use whatever you like)
Titanium Backup (or you can use the application manager in the Settings app)
Firstly, what you will need to do is use your file browser and create a folder called "Viper4Android" in your /system/priv-app/ folder. Set the permission for this folder to rwxr-xr-x or 0755, then paste your Viper4Android APK into the folder you created and set the permission for the APK to rwxrwxrwx or 0777, with root being owner and group for both folder and APK.
Secondly, what you will need to do is browse to /system/etc/ with your file browser and open the file init.qcom.post_boot.sh and at the very bottom of the file paste this:
Code:
/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
It is imperative that you make sure you are using Unix line endings instead of anything else.
Thirdly, use Titanium Backup or the Application Manager to freeze SoundAlive, as all music apps will attempt to default to it. Also you may want to freeze the Adapt Sound app, as if you enable it will then be used over V4A.
Lastly, reboot your phone and then install the drivers and reboot one last time. I can confirm that it works on Play Music, and that it doesn't work on the stock Music player (however I believe there is a way to get it to work somewhere on the internet).
Problems:
You are to create it as a system app, so follow the first step.
Make sure you followed the first step correctly and set the proper permissions.
Make sure you pasted the command into the init.qcom.post_boot.sh file and that you used Unix line endings, as using DOS or Mac line endings add extra characters that Android will try to parse as actual text.
This bug happens sometimes, I found the best way to beat it is to open your BusyBox app and just put it in the background and try the driver installation again.
Make sure you freeze SoundAlive and Adapt Sound, as they will be used before Viper4Android, also you may need to put V4A into Compatibility mode to use with certain music players. Also you can't use the stock Music player (but I think there is a way somewhere on the internet).
Then you may want to wait until a recovery flashable zip is made, but at no point are the steps going to brick your phone, you can just boot to Safestrap or flash back.
Notes:
This process can probably be done very easily with a init.d script and a recovery flashable zip, but I currently don't have the time and don't want to risk screwing up someone's phone.
You can use any other Viper4Android mod, as long as it is v2.3.4.0, I prefer this version which looks very nice. You can extract the file from the zip attachment and just follow the steps here.
You do not need to have SELinux set to permissive, as even with using MultiSystem to set it to permissive, it still didn't work until the above command is used.
I haven't tested whether effects like convolver or DDC work, but they should.
Thanks to:
@ihancioglu for the code that allows it to work
@nappent for most of the steps needed to get it running
EXTRA:
Here is an init.d script that will do the bypass for you, however, you must have init.d support. As it stands right now, Walter.White's Lollipop ROM does not have init.d, if you want to enable init.d, you have to add
Code:
/system/etc/init.d/*
to the end of init.qcom.post_boot.sh and create an init.d folder in /system/etc.
Script: https://mega.nz/#!ZpIUCbrb!QONi8bWb1afE47_JnwxgpBcXoKFuPG3mpnyFX4r83G0
Click to expand...
Click to collapse
I used link2sd to covert music & video players from system to user apps & viper4android worked greatly!

SilverStone641 said:
Thanks OP! Got it all working and the sound quality has definitely improved. Question though, in past versions I loved adjusting the IRSamples. Is that no longer a thing in this latest version?
Click to expand...
Click to collapse
Working here. Did you change the UI setting?
Sent from my SAMSUNG-SM-N900A using Tapatalk

hllah66 said:
I used link2sd to covert music & video players from system to user apps & viper4android worked greatly!
Click to expand...
Click to collapse
Good to know that is what you have to do to get V4A working on stock Music and Video Player. I don't know if that would bring up any issue, but nice find.

Works like a charm on AllianceROM Lollipop v9.1 Extreme Customisation 05.24.2015 :victory:

KTownGT said:
Working here. Did you change the UI setting?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Interesting. I don't have that option at all in my interface. I haven't adjusted any UI settings either. Is there another component that needs installing?

SilverStone641 said:
Interesting. I don't have that option at all in my interface. I haven't adjusted any UI settings either. Is there another component that needs installing?
Click to expand...
Click to collapse
Open V4A --> tap settings --> tap "UI Settings" --> Tap "Expert". Should have it after that

KTownGT said:
Open V4A --> tap settings --> tap "UI Settings" --> Tap "Expert". Should have it after that
Click to expand...
Click to collapse
MY HERO!! Thank you so much!! I've got all my favorite settings options back plus it sounds even better! Thank you!!

Namelesswonder said:
Good to know that is what you have to do to get V4A working on stock Music and Video Player. I don't know if that would bring up any issue, but nice find.
Click to expand...
Click to collapse
Hello...
How is that accomplished?
They can be detailed the activities necessary to achieve this?
Thanks!!!