Develop Bugs

Dena Theme v1.1 for I9000XXJPK

So i have modified The Dena theme from JPH for JPK
1.You need a rooted JPK
2.download root explorer and install
3.download Dena Themev1.1 and unpack it
4. Copy the unpacked files to your Galaxy s
5:Open root explorer and copy framework-res.apk and twframework-res.apk
from sdcard to system/framework directory
6.copy settings.apk from sdcard to system/app directory
7.Restart your Phone and it work perfectly
Link:
rapidshare.com/files/420925248/Dena_Theme_V1.1_For_I9000XXJPK.zip.html
No Pass

Any pics possible?

here some pics
yfrog.com/1233401109p
yfrog.com/ng74387340p
open this links and there are two pics i cant post it here i am new!!! sorry

{
"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"
}

Thank you very much pharaohdk!!!!!

nice theme..got other link..RS server seems to be busy atm..^_^

nice theme
thanks

hello,
auto rotation in notification bar removed ?
in stock jpk i have wlan bluetooth gps vibration autorotation

Problems with the file copy. I get a no space for copy error.

Yes, idem for me :x

Alexzander said:
Problems with the file copy. I get a no space for copy error.
Click to expand...
Click to collapse
i got the same error also..you will need to remount first..
mount -o remount, rw /system
thats should be okay then..^_^

doesn't work, cause the phone not able to boot after cping the 3 files.

it didn`t work for me either ...
I get a no space for copy error too ...
is it possibile that the one click lag fix could be causing it ?
anyway my phone booted with normal skin ... but got few odd vibrations on startup
EDIT:
Managed to get it working using Android SDK tools. ROOT needed
Connected my phone via usb with the computer ... USB debuging needs to be enabled before connecting the phone.
copy the files included in Dena Themev1.1 to your internal SD card.
1. adb shell
2. su (grant su rights on your phone when asked)
3. mount -o rw,remount /dev/block/mtdblock3 /system
3. rm system/framework/twframework-res.apk
4. rm system/framework/framework-res.apk
5. rm system/app/settings.apk (if no file is found try Settings.apk ... no ide if it matters tho)
6. cp sdcard/twframework-res.apk system/framework
7. cp sdcard/framework-res.apk system/framework
8. cp sdcard/Settings.apk system/app
Then reboot your phone manually.
Worked for me with a few minor bugs tho.
So i suggest you bacup the original *.apk`s

cp: no found
help me

Install busybox.
And a please would not have been too much
Sent from my GT-I9000 using XDA App

that is those buttons and wallpapers wearing? thanks

Universal (All Firmware) One Click Root (Including 2.6.1!)

I have not tryed it yet cause I'm still at work. Once I get home I will give it a try and post my findings. But it looks like people have and its does work. Below are the 2 links to the fix, hope this helps.
Link 1
Link 2

Looks great!
Sent from my Nexus S

It works and this tip might help so people
When you open cmd go to the folder you download the files to or it will not work or did not for me at first,
cd c:\users\<yourcomputername here mine is troy>\downloads\superuser
Then as link said
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install com.noshufou.android.su-1.apk
adb reboot

It works
It works!
Note that if you still have superuser installed from the previous roots before update to 6.2.1, it gives you a failed message for last step before reboot.
I presume this is because that step is just to install superuser again?
Mine is working now anyway despite this...im going to try installing recovery now and get cm7 on here before Amazon push another update^^

Of course it works, I wrote it while drunk.
{
"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"
}

Hopefully they will integrate your root into the KF utility now

In my Will.I.Am voice > Oh myyyyyyyyy God! lol it works thanks alot man! now to install TWRP

I must be missing something , there is no drivers package in any of the files i downloaded ,just the su / superuser.apk , maybe im still drunk!

Vintage144 said:
I must be missing something , there is no drivers package in any of the files i downloaded ,just the su / superuser.apk , maybe im still drunk!
Click to expand...
Click to collapse
Didn't include any, I don't use windows, and have no clue how to setup adb on it. Im sure you can find directions somewhere.

ahh ok , i see

Vintage144 said:
ahh ok , i see
Click to expand...
Click to collapse
You get the drivers with sdk manager in the sdk starter package from google.
Sent from my Kindle Fire using Tapatalk

hi my mother got the kindle fire and im trying to root it. but im having problems.
when i get to the cmd part where i type in
cd c:\KindleADB
then type
adb devices
nothing appears. restarted comptuer. still no go. uninstalled the android phone in device manager but once i put the kindle back it appeared again then tried to just update the driver but i do think it did anything cause i re-ran the script and still nothing. should i ignore and move on? or is the something less involed then this.
im running im just trying to get this thing rooted so i can use ad hoc mode but im having issues.

[Q] Setting kernel parameters on startup (without using any app)?

I'm using LeanKernel 4.5 and i'd like to change governor, scheduler and some other minor parameters using sysfs. My linux understanding is quite basic.
I can easly check current values using adb (a list of sysfs options is here):
Code:
adb shell
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
I get "interactivex". However, why I can't change it using adb (first question)? This it's not working:
Code:
adb shell
echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
And the governor remains "interactivex".
Second question is, how can I make them permanent? Should I modify init.rc script?

You need to be root to change those values. 'su' after 'adb shell'.
Second, your rom needs to support /system/etc/init.d/ scripts.
Sent from my i9250

bk201doesntexist said:
You need to be root to change those values. 'su' after 'adb shell'.
Second, your rom needs to support /system/etc/init.d/ scripts.
Sent from my i9250
Click to expand...
Click to collapse
Thank you for your help. I did :angel: but it doesn't work:
{
"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"
}
Also, I'm using the stock factory images. So you're saying that I will not able to set this values at boot? If yes, how the app SetCPU can?

Gremo said:
Thank you for your help. I did :angel: but it doesn't work:
Also, I'm using the stock factory images. So you're saying that I will not able to set this values at boot? If yes, how the app SetCPU can?
Click to expand...
Click to collapse
Add a file at /system/etc/init.d/<filename.extension>. Chmod it to 755 and add the contents below into it(the steps can be done via adb or file manager, its easier via file manager for newbies)
Code:
#!/system/bin/sh
echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
After that, reboot your phone and check whether the changes has been done or not
To enable init.d, at minimum you need to be rooted though and busybox needs to be installed
Here's a link on how to enable it(you can try whether it works or not first, if it doesn't then only try this one): http://forum.xda-developers.com/showthread.php?t=1933849

[Q] Why cmd show # instead of $ after I typed "adb shell" then "su"

[Q] Why cmd show # instead of $ after I typed "adb shell" then "su"
Hi, I am not good at command writing, but recently I would like to use "androidscreencast.jnlp" which I need to use cmd in desktop windows to configure for keyboard and mouse control over the android phone.
When I type adb shell, it doesn't show "$", it shows "[email protected]:/ #".
What does that mean??
I probably need the "$" sign to do the configuration...
{
"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"
}
Can anyone help??
Thank you very much!!

# is the symbol for you having root access.

Indeed.
Sent from my Galaxy Nexus using xda app-developers app

Op, use google
Sent from my i9250

Zepius said:
# is the symbol for you having root access.
Click to expand...
Click to collapse
Thanks Zepius,
but I have been trying the following codes in cmd for several times in order to allow using desktop keyboard and mouse to control my nexus through AndroidScreenCast.jnlp. It seems unsuccessful. It's supposed that the code is fine. Just wondering does that "[email protected]:/ #" the obstacle ...
{
su
chmod 777 /data/dalvik-cache
cd /data/dalvik-cache
exit
exit
}

francis1212 said:
Thanks Zepius,
but I have been trying the following codes in cmd for several times in order to allow using desktop keyboard and mouse to control my nexus through AndroidScreenCast.jnlp. It seems unsuccessful. It's supposed that the code is fine. Just wondering does that "[email protected]:/ #" the obstacle ...
{
su
chmod 777 /data/dalvik-cache
cd /data/dalvik-cache
exit
exit
}
Click to expand...
Click to collapse
Not sure what those commands have to do with getting a keyboard to work, but you certainly would no be able to execute them without the # prompt...
Sent from my Galaxy Nexus using Tapatalk 2

francis1212 said:
Thanks Zepius,
but I have been trying the following codes in cmd for several times in order to allow using desktop keyboard and mouse to control my nexus through AndroidScreenCast.jnlp. It seems unsuccessful. It's supposed that the code is fine. Just wondering does that "[email protected]:/ #" the obstacle ...
{
su
chmod 777 /data/dalvik-cache
cd /data/dalvik-cache
exit
exit
}
Click to expand...
Click to collapse
What does the cache have to do with the keyboard?
Beamed from my Maguro.

[SOLVED] ADB Devices Unauthorized

I am trying to get rid of this extremely buggy and heavy, Asus Zen software, on my ZE551ML, and replace it with something else, but I'm running into walls, everywhere I go. First, in ADB, I get
Code:
List of devices attached
F6AZFG14H361 unauthorized
I have tried clicking Revoke USB debugging authorizations, but that didn't help anything. I tried restarting ADB, didn't work. I know those are supposed to be the steps, but they aren't working, for me.
I am on ROM ww_2.20.40.174. Has anyone else had this problem?

Your device should prompt you to authorize the PC you're connecting with. You need to watch for it to pop up.
{
"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"
}

Kid_Ding said:
Your device should prompt you to authorize the PC you're connecting with. You need to watch for it to pop up.
Click to expand...
Click to collapse
It never gives me this popup. It "sees" the device, but never asks to add the fingerprint.
All of this assumes your Zenfone 2 is being recognized by the computer, running the command:
Code:
lsusb
Bus 003 Device 015: ID 0b05:5601 ASUSTek Computer, Inc.
If it is not, you have another problem. If it is being recognized, continue.
[SOLUTION BELOW]
Ubuntu 14:
Kill the ADB server.
Code:
adb kill-server
In the user's profile, look for a folder called .android. The folder may be hidden or owned by root. If the folder is owned by root, run these commands with the sudo prefix or sudo -s to promote to the root user.
Code:
ls -la
drwxr-x--- 2 root root 4096 Mar 21 10:24 [COLOR="Blue"].android[/COLOR]
Rename the folder to .android.old.
Code:
mv .android .android.old
Remove the USB debugging authorizations, on your phone, in developer options.
Restart the ADB server
Code:
adb start-server
If your usb is still plugged in, it should pop up the dialog to add the RSA fingerprint. Do so.
Check to see if the phone is recognized.
Code:
adb devices
List of devices attached
F6AZFG14H361 device
Thanks for the help.

help
excuse me, i am in the same situation, but my phone is stuck on recovery screen , i need a code to authorize it through adb only (( , any help???