{
"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"
}
Here is a SystemUI.apk that changes the Quick Panel icons to blue!
Prerequisites
Root
ADB
Something to mount /system/ as writable (I use ES File Explorer)
[NOTE: This is based on the STOCK Juggernaut 5.0 SystemUI.apk]
Instructions
1. Place the attached "SystemUI.apk" in the folder where you have ADB setup (usually either "tools" or "platform-tools" in your SDK folder)
2. Type "cmd" in Run Dialog
3. Type cd and then type the path to the folder where you have ADB setup
Example
Code:
cd c:/android/android-sdk/platform-tools/
4. On your phone, mount system as writable (IMPORTANT : Your system must be writable or you will get a read-only error in the command prompt)
5. Push the modified "SystemUI.apk" to the /system/app/ folder
Code:
adb push SystemUI.apk /system/app/
You may or may not get some Force Closes after doing this - IT'S OKAY!
6. Reboot your phone - the fastest way is just type "adb reboot" since you already have the command prompt up and are in the correct directory.
Congratulations! You changed your Quick Panel icons are blue!
Related
This is more of a dialer theme but has a few image updates for contacts as well.
Push to system/app folder after you rename the old Contacts.apk to something like Contacts.apk.bak
Step1: You need root and a file explorer that has root access. I use Root Explorer.
Step2: Copy the Contacts.apk file from your computer to your sdcard
Step3: Navigate to /system/App
Step4: Rename Contacts.apk to Contacts.apk.bak
Step5: Navigate Back to /sdcard
Step6: Copy or Move the new Contacts.apk
Step7: Navigate back to /system/app
Step8: Paste
Step9: Back out to home screen
Step10: Open App Drawer
Step11: Long Press Phone and Drag to home screen
Step12: Long Press Phone on Homescreen and drag to Launch Bar to put it back
Step13: For Contacts Repeat Steps 10-12 to put Contacts back on launch bar
-----------------------------------------------------------------------------
Images
{
"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"
}
Download
Very cool dialer
Sent from my SGH-T989 using Tapatalk 2
Removed stock toggles and clock from notification list and made notification row visible when bar is dropped.
Installation:
1. Make sure you have ROOT, ADB ENABLED, STOCK 4.3 (15.4.A.1.9), MADE A BACKUP OF ORIGINAL SystemUI.apk and SystemUI.odex from /system/app
-adb enabled is important because when somethings goes wrong you can put back original SytsemUI.apk and SytemUI.odex
2. Remove SystemUI.apk and SystemUI.odex from /system/app
-android will now reload UI it will display bootscreen for a while
-there will be no notification bar untill you put SystemUI.apk back don't worry it's ok
3. Paste file from bootm of this post to /system/app
-it's deodexed so no need of .odex file
4. Fix permissions a.k.a rwx (enable them all -chmod 777)
5. Reboot
If something goes wrong don't panic, when you boot and there is no notifaction bar or SytsemUI is force closing, just do:
1. Connect your phone via usb
2. Remove SystemUI.apk throught ADB
3. Push BOTH original backuped files
4. Everything is back :]
If someone want's to know how to edit things like that i can make tutorial for him/her.
{
"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"
}
APK:
"https://seacloud.cc/f/e9dd6cb2fe/"
Moderator please fix title spelling errors, was too excited :[
Hello!
I've trying to get root on nook. It gives just neverending 'registering' screen
It coonected with adb drivers and when i've launch root application I've got such screen:
{
"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"
}
How can I root this nook?
Thank you
Starting at the bottom screen:
I don't know which script (batch file) this "rootnook" is.
Apparently it is too picky about the version of adbd on your Glow2.
You can try to delete the line that causes it to stop.
The "find" and "findstr" appear to say "is not recognized as an internal or external command, operable program or batch file."
I don't know if your Windows doesn't have them or if they are named something else.
You can check by just typing:
Code:
C:\>find /?
C:\>findstr /?
The top screen we don't even know what command/script you tried.
It looks like you tried something and used the word "files" instead of an actual path.
The error looks like something out of the Glow2 shell
Code:
# busybox stat files
stat: can't stat 'files': No such file or directory
If instead of taking a graphic screen shot you should copy and paste the text and put it inside [code] & [/code]
so that those of us who don't speak Russian can more easily translate it.
How did I get that to work?
Code:
[b][code[b]][/b][/b] & [b][/code[b]][/b][/b]
This post explains how you can extract the logs of an app using the adb command line tool. Earlier, we could access the Android->data folder for each app but that is not possible now. But we can do it using the adb command line tool.
1. Step 1
a. Install and setup the adb command line tool for your computer. This article shows you how to do so.
2. Step 2
a. Now since your phone is connected to your computer via adb, open a command prompt and type in "adb shell". Now you can access your phone via the command line.
b. To access the data folder for a particular app, type in the following command "cd /sdcard/Android/data". Here you'll find the data folders for all the apps in your phone.
c. List all the apps using the "ls" command as shown below.
{
"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"
}
3.Step 3
a. Now get the complete name of your app and type in "cd <COMPLETE_APP_NAME>". Here you can access the logs/cache of your app.
b. Now to download this file to your pc, open another command prompt and type in command "adb pull /sdcard/Android/data/<APP_NAME>/<YOUR_PATH>"
c. This will fetch and download the files you need at the location where your command prompt is pointing to (D drive in this case)
Prerequisites:
• Root access
• ViPER4Android by repackagedhoch32
• Terminal Emulator of your choice
In terminal, run these commands:
- su
- cd /storage/emulated/0/Android/data
- ls -l | grep com.pittvandewitt.viperfx
It should say something as follows:
{
"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"
}
We are interested in 2 items: "u0_a336" and "ext_data_rw".
"u0_a336" is the owner of this file. This is installation-specific. The owner of your folder will probably be different!
"ext_data_rw" is the group this file belongs to. Yours may be different according to your ROM.
Write down all your permissions somewhere. You will need it later.
Now do this:
- cd com.pittvandewitt.viperfx
- chown u0_a336:ext_data_rw files
Remember to change the owner and group to your install.
Now do this:
- cd files
- chown u0_a336:ext_data_rw *
Should be 3 folders in "files": DDC; Kernel; Preset.
cd into DDC and Kernel then perform:
- chown u0_a336:ext_data_rw *
Done.
I just delete the folders, create new one, and move files into it and boom