Database Users

Superuser Permissions has broken

When some Apps are requireing a root permission, a root request window used to poped up and I can choose "Allow" or “Deny".
But now it only poped with a blank window and there is no any bottons below! What happened?? I don't know how to reinstall Superuser Permissions, because I even can't uninstall it in the program manager.

I've got the same problem. I'm running 'TheOfficial DONUT AOSP' rom on a G1.
---
I finally decided to reinstall the rom and now it works again. But I still would like to know what broke it and/or how to fix it.

the Same
Me too :'(

resolved!
Hahaaa~~~ I resolved the problem!
Just use adb,first connect your phone to the PC, PC will install adb driver automatically(if not please search drivers on Google), open command prompt,type:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
adb push su /system/bin/
adb shell chmod 4755 /system/bin/su
adb shell reboot
All done! The su and adb file is in the attachment,enjoy~

nabor said:
Hahaaa~~~ I resolved the problem!
<snip>
All done! The su and adb file is in the attachment,enjoy~
Click to expand...
Click to collapse
Great work man, thanks!

When I run the "adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system" command I get "mount: Operation not permitted"
I've run the SuperOneClick and it always sticks on loading superuser.apk. If I unplug the USB reset the debug, it says my Droid is rooted, but it isn't.
UPDATE: Never mind... I just rooted the old fashion way and it worked...scary but it worked.

" 'adb' is not recognized as an internal or external comand "
please help me

su chmod 4755 /system/bin/sh doesn't work?

su chmod 4755 /system/bin/sh just won't work. When I first rooted yesterday I was able to pull and push a few files but when I've run adb today I'm getting the "operation not permitted" error, and when I try the chmod in Better Terminal I get a "read only" error.

UPDATE: I used the unroot feature on SuperOneClick then rerooted, I read somewhere that installing the PDANet client on the computer helped with the looping issues and it did, and now I'm able to use adb again.

Nope, back to mount: Operation not permitted. Any ideas?

Adding blur alarm to Fission ROM

For those of you that felt in love with the Blur Alarm and looking for a way to add it back. I have figured out the missing files beside the apk that goes in the system\app. This has been tested with sucess for Fission ROM v2.0.1.
Adding Blur alarm
system\app\BlurAlarmClock.apk
framework\blur-res.apk
framework\com.motorola.blur.library.utilities.jar
Hope it help.

nice,
I prefer the blur alarm over the normal one.
but here is my problem, the dock is DeskClock.apk, which is also the Clock and the alarms,
when I replace it with the Dock.apk, then the dock won't start up,
did you try to do that?
I'm getting the following exception, and have no clue on how to fix that Oo
Code:
11-04 00:39:22.031 2063 2063 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.motorola.dlauncher/com.motorola.dlauncher.DLauncher}: java.lang.SecurityException: Neither user 10048 nor current process has android.permission.DEVICE_POWER.

braway said:
nice,
I prefer the blur alarm over the normal one.
but here is my problem, the dock is DeskClock.apk, which is also the Clock and the alarms,
when I replace it with the Dock.apk, then the dock won't start up,
did you try to do that?
I'm getting the following exception, and have no clue on how to fix that Oo
Code:
11-04 00:39:22.031 2063 2063 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.motorola.dlauncher/com.motorola.dlauncher.DLauncher}: java.lang.SecurityException: Neither user 10048 nor current process has android.permission.DEVICE_POWER.
Click to expand...
Click to collapse
What ROM are you using? I renamed the original DeskClock.apk to DeskClock.bak since I don't have a docking station. May be it has something to do with the dlauncher. I also deleted the original launcher2 and replaced it with launcherpro.apk.

Fission 2.0.2
I basically did the same with the DeskClock.apk
but added the Dock.apk from the clean verizon rom (which is basically the "stock" droid2), I guess I'm simply missing something
btw, com.motorola.dlauncher is Dock.apk
I guess something is still missing which would set the missing permission oO

got it to work...
if someone cares:
I had to manually modify the /data/system/packages.xml
it should contain something like this:
Code:
<package name="com.motorola.dlauncher" codePath="/system/app/Dock.apk" flags="1" ts="1288859615000" version="8" userId="10057">
<sigs count="1">
<cert index="1" />
</sigs>
</package>
userId and ts are probably different
change the cert index to 0 !
reboot (right after it, for example with adb reboot)
after reboot, check that your change is still in this file (should be)
put your phone into the docking station, and the blur dock should start
yay

lol, this default blur alarm app is awesome and best I have seen. I was so surprised at what it wanted me to do when I first woke up to it , lol

I am not using fission and I am using Rubix 1.6.
I can only find the bluralarm.apk file and I can't find
framework\blur-res.apk
framework\com.motorola.blur.library.utilities.jar
Do i have to nandroid back to a blurry room to pick these up or are they available somewhere else?
Thanks

rkrasny said:
I am not using fission and I am using Rubix 1.6.
I can only find the bluralarm.apk file and I can't find
framework\blur-res.apk
framework\com.motorola.blur.library.utilities.jar
Do i have to nandroid back to a blurry room to pick these up or are they available somewhere else?
Thanks
Click to expand...
Click to collapse
get the vzw clean rom (or so) from droid2files.com (http://droid2files.com/roms/VZW_2.4.5_Clean_ROM.zip)
everything should be in it...

braway said:
get the vzw clean rom (or so) from droid2files.com (http://droid2files.com/roms/VZW_2.4.5_Clean_ROM.zip)
everything should be in it...
Click to expand...
Click to collapse
Perfect; thanks much.

Question?
How do I add this to my phone and make it work? Do I need to use ADB and move it to the phone or what? I really liked the blur alarm a lot and would like to get that back if I can. Thanks for any help in advance.

You just need a method to transfer the files to the phone to the correct spot
ADB or root explorer can move the files
I will show the adb method below, you can substitute the adb shell, mount, cp (copy), chmod (change permissions), and rm (delete) steps with Root Explorer
ADB
Open a command prompt
cd to the directory where you have the files on your computer
Code:
adb push BlurAlarmClock.apk /sdcard/BlurAlarmClock.apk
adb push blur-res.apk /sdcard/BlurAlarmClock.apk
adb push com.motorola.blur.library.utilities.jar /sdcard/com.motorola.blur.library.utilities.jar
Then adb shell to the phone, mount system as r/w, copy the files to the system
Code:
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/BlurAlarmClock.apk /system/app/BlurAlarmClock.apk
cp /sdcard/blur-res.apk /system/framework/blur-res.apk
cp /sdcard/com.motorola.blur.library.utilities.jar /system/framework/com.motorola.blur.library.utilities.jar
Then set the permissions on these files so they will work
Code:
chmod 644 /system/app/BlurAlarmClock.apk
chmod 644 /system/framework/blur-res.apk
chmod 644 /system/framework/com.motorola.blur.library.utilities.jar
You can then remove the files from the sdcard if you wish
Code:
rm /sdcard/BlurAlarmClock.apk
rm /sdcard/blur-res.apk
rm /sdcard/com.motorola.blur.library.utilities.jar
Now mount the system as read-only again
Code:
sync
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
As for the Blur dock
Use the same steps above to copy the file and move it to the system
Code:
adb push Dock.apk /sdcard/Dock.apk
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/Dock.apk /system/app/Dock.apk
chmod 644 /system/app/Dock.apk
sync
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
rm /sdcard/Dock.apk
Next pull the packages.xml file
Code:
adb pull /data/system/packages.xml
Edit packages.xml as shown in the above post
Then push back
Code:
adb push packages.xml /data/system/packages.xml
When you "install" the blur dock, you might want to remove the standard android dock
Code:
adb shell
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
mv /system/app/DeskClock.apk /system/app/DeskClock.bak
sync
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
Notice I just used mv (rename/move)
This is just in case I want it back later
You may need to reboot the phone when you are finished for this to work.
I never tried without rebooting so I don't know if they will work otherwise.

Fix WiFi Channel 12-13

You can fix wifi channel 12-13 support by setting the wifi_country_code to EU.
You need a rooted device and sqlite3 to fix (attached).
Unpack the attached zip and run fix_wifichannel_EU.bat (Windows only)
or with linux:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p3 /system
exit
adb push bin\sqlite3 /system/bin
adb shell
su
chmod 6755 /system/bin/sqlite3
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
reboot

Ohhhh it's good to see you here in the Iconia section!
I used to be a user of your great Desire Kernels/roms.
Hope to see some work from you soon.

richardtrip said:
You can fix wifi channel 12-13 support by setting the wifi_country_code to EU.
You need a rooted device and sqlite3 to fix (attached).
Unpack the attached zip and run fix_wifichannel_EU.bat (Windows only)
or with linux:
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
adb push bin\sqlite3 /system/bin
adb shell chmod 6755 /system/bin/sqlite3
adb shell sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO secure (name, value) VALUES ('wifi_country_code', 'EU');"
adb shell reboot
Click to expand...
Click to collapse
Thank you very much and great to see you here
OT: can you help us with the recovery issues ??

Thanks in advanced. I will try sometime in the near future.
Enviado desde mi GT-I9000B usando XDA Premium App

so you got this tablet, richard =P Wonder when we will be able to start playing with custom rom =)
Btw, I notice that a huge amount of RAM is consumed and the maximum amount of RAM freed I have ever got is 440MB. Do you know what happened to the rest?

lpachuong said:
so you got this tablet, richard =P Wonder when we will be able to start playing with custom rom =)
Btw, I notice that a huge amount of RAM is consumed and the maximum amount of RAM freed I have ever got is 440MB. Do you know what happened to the rest?
Click to expand...
Click to collapse
The rest of the ram is reserved for video on boot.

I thought so, but don't you think that is too much out of 1GB ram? I found the device is laggy if ram goes under 350MB. Hope modded kernel can help optimize ram.

sweet
Nicely done! It works. Yea it is good to see you here' meaning we have somebody who knows a thing or two about android development.
W

Fix worked!
For some strange reason adb remount command didn't worked and adb wasn't able to push sqlite3 file to /system/bin even after remounting /system rw from the device itself. I had to push it to sdcard and then move it to /system/bin.
By the way, channel 13 is working fine now.
Thx

Hi Richard,
It's good to see such a great dev interested in the A500 (I have a Desire). <vbg>
EDIT: I can confirm that this works!
I cannot remount /system, either via ADB nor via a shell (on the device itself). In both cases, I get...
Code:
mount -o rw,remount /dev/block/mmcblk0p3 /system
mount: Operation not permitted
[Edit: worked with a terminal, but forgot to SU first, and I was typing mmcblkop3, not mmcblk0p3 !!]
I tried to be clever (NB: I don't have a SD card installed):
Code:
adb shell mount -rw /dev/block/mmcblk0p3 /mnt/external_sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
That's the extent of my *nix skills...
Any ideas?
-Dave

zxdavb said:
Hi Richard,
It's good to see such a great dev interested in the A500 (I have a Desire).
I cannot remount /system, either via ADB nor via a shell (on the device itself). In both cases, I get...
Code:
mount: Operation not permitted
I tried to be clever (NB: I don't have a SD card installed):
Code:
adb shell mount -rw /dev/block/mmcblk0p3 /mnt/external_sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
That's the extent of my *nix skills...
Any ideas?
-Dave
Click to expand...
Click to collapse
Try su before the mount command.
Edited the procedure in the first post so try that (should work now).
Sent from my A500 using XDA Premium App

zxdavb said:
Hi Richard,
It's good to see such a great dev interested in the A500 (I have a Desire). <vbg>
I cannot remount /system, either via ADB nor via a shell (on the device itself). In both cases, I get...
Code:
adb shell mount -o rw,remount /dev/block/mmcblk0p3 /system
mount: Operation not permitted
I tried to be clever (NB: I don't have a SD card installed):
Code:
adb shell mount -rw /dev/block/mmcblk0p3 /mnt/external_sd
Usage: mount [-r] [-w] [-o options] [-t type] device directory
That's the extent of my *nix skills...
Any ideas?
-Dave
Click to expand...
Click to collapse
Just do
Code:
su
mount -o remount,rw /system

daveba said:
Just do
Code:
su
mount -o remount,rw /system
Click to expand...
Click to collapse
Thanks!
For the beginners (like me): I noticed that /system was set back to read-only on reboot...

Works brilliantly. Thanks.

thx - but I trust editing the build.prop in Root Explorer should also do the job for those who don't want to mess with adb and commands.

hi
can anyone tell me whats this fix for?
is it going to make wifi receiver even better?
thx..

he_stheone64 said:
thx - but I trust editing the build.prop in Root Explorer should also do the job for those who don't want to mess with adb and commands.
Click to expand...
Click to collapse
yes,
add this line
ro.wifi.country=EU
and reboot.

i have this message:
'Unable to detect a device over adb'
I've connected my nexus S via usb cable, i've tryed with the usb usb storage on an off, and i get the same message.
I'm using windows / x64.

Dexter_nlb said:
yes,
add this line
ro.wifi.country=EU
and reboot.
Click to expand...
Click to collapse
i've done that but i canot save the file i get the message that it's a read only file system.
how can i gain write access to that file??

Thanks the fix_wifichannel_EU.bat in the zip worked like a charm. Channel 13 now works on my Asus Eeepad Transformer purchased from the US as well.

"wi fi is turning on" issue after wpa supplicant

hello, i tried searching the forum for anything related to my problem but didnt find anything useful that's why starting new thread!!
please help me on this one!!
i have samsung galaxy tab2 10.1 through which i wanted to connect to my laptop's ad hoc network!! for that i rooted n installed busy box on my tablet, then did this through command prompt!!
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp /system/bin/wpa_supplicant /sdcard/wpa_supplicant.original
cp /sdcard/wpa_supplicant /system/bin/.
chmod 755 /system/bin/wpa_supplicant
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
exit
and when i rebooted my tablet after that, it's showing "wi fi is turning on" and is stuck like that!! i
so i did factory reset but still its showing the same thing!!
thanks in advance!!