When doing
Su wm size 1080x1920 it brings the error that I can't change while system is running is there a work around? How do I send a script if the system is turning off?
Root - init.d
raul4916 said:
When doing
Su wm size 1080x1920 it brings the error that I can't change while system is running is there a work around? How do I send a script if the system is turning off?
Click to expand...
Click to collapse
Was actually able to by just as soon as it boots go to adb shell with pc and running wm will be fine
Related
I'm having problems with the SuperUser Permissions included on the DamageLess 2.8 ROM. I've never been able to use it correctly, and now I really need to in order to utilize the DCUpdater. Can someone tell me how to work this app??
BTW, i've already tried to run the adb shell in my android sdk folder, but that doesn't work. It keeps telling me that the path syntax is not correct, or something along those lines.
dereklane said:
I'm having problems with the SuperUser Permissions included on the DamageLess 2.8 ROM. I've never been able to use it correctly, and now I really need to in order to utilize the DCUpdater. Can someone tell me how to work this app??
BTW, i've already tried to run the adb shell in my android sdk folder, but that doesn't work. It keeps telling me that the path syntax is not correct, or something along those lines.
Click to expand...
Click to collapse
Do you have debugging enabled?
Yeah, I enabled it after I plugged in my phone
Thread Moved. Not related to Development.
dereklane said:
I'm having problems with the SuperUser Permissions included on the DamageLess 2.8 ROM. I've never been able to use it correctly, and now I really need to in order to utilize the DCUpdater. Can someone tell me how to work this app??
BTW, i've already tried to run the adb shell in my android sdk folder, but that doesn't work. It keeps telling me that the path syntax is not correct, or something along those lines.
Click to expand...
Click to collapse
if you have debugging enabled, make sure you aren't connected to your computer, that will cause it to crash. other than that i don't know
As long as you have USB debugging enabled, when a program asks for superuser permission, it will prompt you.
-------------------------------------
Sent via the XDA Tapatalk App
I had the same problem but enabled usb debugging and disconected the phone from the computer and SU is working fine again.
I have USB debugging enabled, disconnected from the PC, but I can't get Superuser to prompt (for any apps) when trying to run Autokiller. I just flashed Fresh 2.1.2 coming from FreshToast. Any help?
what version should i use on my Xperia X10a?
hi
i rooted my X10a & have the Superuser Permission install lately. when i click on the icon, it shows a blank screen. i click the menu button > preferences , it shows Action Yap & Notification. there's no apps or anything else. could someone guide me how i get it work?
thanks
For anyone having issues with SU (no matter which ROM) check the permissions on the following two binaries:
/system/bin/su
/system/xbin/su
If they're not 755, connect to the shell via ADB and change them - that's worked for several users on Fresh, my guess is that it would probably work on other ROMs as well.
ok i have some issues...
I have a Moto Blur...
and when i checked the
/system/bin/su --- it only had -r-
/system/xbin/su -- didnt have this file
do you have an idea what's wrong?
thanks
mat
I have replaced some fonts on the nook and everytime at some point, i get issue with it.. it does not boot anymore... and every time i need to do a factory reset, re-root. Is there steps/precautions i need to be aware when replacing fonts on the nook or adding apps in system/app??
I have an htc desire rooted and i have never had issues like that on it; i have replaced fonts, edited files like build.prop or key mapping, added/deleted/renamed apps in system/app and i never had a single issue... maybe the nook is different i don't know
To answer your question, no, it's not dangerous.
Linux doesn't care at all about fonts.
So if you have a problem with fonts, use ADB and logcat and actually figure out what the problem is.
Even with flashing dots, ADB and logcat (and dmesg) work.
Renate NST said:
To answer your question, no, it's not dangerous.
Linux doesn't care at all about fonts.
So if you have a problem with fonts, use ADB and logcat and actually figure out what the problem is.
Even with flashing dots, ADB and logcat (and dmesg) work.
Click to expand...
Click to collapse
adb does not detect the nook while it is booting... it only detects when it's booted or when i use cwm
Well, apparently you are bashing some non-font thing.
How are you copying over the font?
Are you using some wonderful "Insta-Mega-File-Masher-Omatic"?
Which font are you replacing?
Stick to basics.
Get your Nook working with 1.2.1 since that is where you should be.
Get ADB working.
Remount /system r/w, adb reboot, still working? Yup.
Remount /system r/w, adb push your font to /system/fonts/temp.ttf, adb reboot, still working? Yup.
Remount /system r/w, then:
Code:
stop
mv whatever.ttf old.ttf
mv temp.ttf whatever.ttf
reboot
Renate NST said:
Well, apparently you are bashing some non-font thing.
How are you copying over the font?
Are you using some wonderful "Insta-Mega-File-Masher-Omatic"?
Which font are you replacing?
Stick to basics.
Get your Nook working with 1.2.1 since that is where you should be.
Get ADB working.
Remount /system r/w, adb reboot, still working? Yup.
Remount /system r/w, adb push your font to /system/fonts/temp.ttf, adb reboot, still working? Yup.
Remount /system r/w, then:
Code:
stop
mv whatever.ttf old.ttf
mv temp.ttf whatever.ttf
reboot
Click to expand...
Click to collapse
I am replacing Caecilia, HelveticaNeue and Trebuchet.... i using adb push to replace the fonts .. i use these commands
adb shell
#su
#mount -o rw,remount /dev/block/mmcblk0p5 /system
adb push myfont.tff /system/fonts
adb reboot
sometimes, every fonts is replaced properly... and everything is alright.. sometimes, replacing the 3rd font and i reboot .. i gets locked.. sometimes it's the 2nd font, it's random.. or sometimes i push an app to system/app.. everything is alright... then i push the same app, it does not boot.. it's all random
how do you activate adb while booting... adb does not detect my nook while booting...
A comment; I have done some playing around with fonts over a year ago and if I recall correctly, the system needs fonts files with names Caecilia, HelveticaNeue and Trebuchet. You can rename other font files to have those names, but those names must exist.
Next, a question; Is it possible that the font files you are attempting to use are so big that they are filling up the file system?
Filling up the partition was one thing I thought of, but since /system is normally ro that didn't seem like it could affect anything.
Do a df and see what space you have left.
How big are the files?
If you are trying to make this do Chinese, just replace one file.
Linux doesn't use fonts.
Android only uses the Droid fonts.
Opera Mobile will use DroidSansFallback.ttf
ReaderRMSDK.apk uses the rest of the fonts.
I was messing around with Rom Toolbox pro and changed my dpi values from 480 to 800, restarted the phone and it loaded with huge resolution and touchwiz keeps saying it fails. I can not access my app drawer but yet i can still send and receive txt messages.
I have safestrap on alliance rom build 2[N9E], will i be able to get a stock build.prof file, place it on my sd card. then book into recoverymode and apply an update from the sdcard?
Any help would be greatly appericated
shrimpy88 said:
I was messing around with Rom Toolbox pro and changed my dpi values from 480 to 800, restarted the phone and it loaded with huge resolution and touchwiz keeps saying it fails. I can not access my app drawer but yet i can still send and receive txt messages.
I have safestrap on alliance rom build 2[N9E], will i be able to get a stock build.prof file, place it on my sd card. then book into recoverymode and apply an update from the sdcard?
Any help would be greatly appericated
Click to expand...
Click to collapse
Not sure if it will work, but flashing the rom again should overwrite the system folder where the build.prop is stored, so a new one would be installed.
aef
well, lucky me i don't back up enough like i should. ..
I ended up with this:
adb push build.prop /data/local/tmp/build.prop
adb shell "su -c busybox mount -o remount,rw /system"
adb shell "su -c cat /data/local/tmp/build.prop > /system/build.prop"
Then it would not boot the RomOS...just reflashed it to a previous state lost a lot of stuff but oh well.
I really like AllianceRom but having verzion is frustrating
I had to put stock back onto my phone because snapchat wasn't happy with the root and i needed my snapchat but I HAD to scale my dpi. Stock dpi was just to big. I changed the dpi in stock by using CMD lines "adb devices" and " adb shell wm density 400&& adb reboot" Which changed most the of phones dpi. The only thing it didn't hit were the notification bar/draw and the capacitive buttons.
Anyone know what i can do to scale these in stock?
jvongsana said:
I had to put stock back onto my phone because snapchat wasn't happy with the root and i needed my snapchat but I HAD to scale my dpi. Stock dpi was just to big. I changed the dpi in stock by using CMD lines "adb devices" and " adb shell wm density 400&& adb reboot" Which changed most the of phones dpi. The only thing it didn't hit were the notification bar/draw and the capacitive buttons.
Anyone know what i can do to scale these in stock?
Click to expand...
Click to collapse
well goto display and change the display size to small... after that goto to dev. options and change the smallest width to 515 dp.... and boom...
I have already made my display size as small as it will go via the phone's Settings, but I want it smaller. I have tried the advice command (adb shell wm density 560 && adb reboot) and it doesn't work. Has anyone else tried this?
You need root , and its impossible to root it right now
lyall29 said:
I have already made my display size as small as it will go via the phone's Settings, but I want it smaller. I have tried the advice command (adb shell wm density 560 && adb reboot) and it doesn't work. Has anyone else tried this?
Click to expand...
Click to collapse
Just from your laptop or pc you can do it , just first install drivers and then om cmd and write:
adb shell wm density *** and hit enter put what ever dpi you want instead of the stars