Hi,sorry for my english
I have a cooked rom gingerbread jvo the name is real .
This rom haven't samsung keyboard and i need it in 3x4 mode...can you help me?
Sent from my GT-I9000 using Tapatalk
Uppp
Sent from my GT-I9000 using Tapatalk
Ginger Samsung Keyboard: http://www.addictivetips.com/wp-content/uploads/android/signedkey.apk (Right click - Save as)
There ya go. Google is your friend!
If it won't install u need to run these commands in adb:
adb shell
su
busybox mount -o rw,remount /dev/block/mtdblock3 /system
cp /system/app/LatinIME* /sdcard/
rm /system/app/LatinIME*
pm uninstall com.android.inputmethod.latin
exit
exit
Hope it works for ya.
Hi,
I've been having problems with my root and superuser. I tried to install supersu also but was crashing every time. The superuser could not get the new su version and generally my A100 acted as not rooted. I tried to do the rooting process again and again with no luck. I downloaded the latest su version and tried the commands again.
Then it crossed my mind to remove the old su from xbin (since I got the new version) and give the commands. So I rm it but then I gave it a closer look and saw that the command did not copy the new su to xbin but was using the cat command. The commands I gave are
(The su version is supposed to be the latest one)
$ export PATH=/data/local/bin:$PATH
$ pwd
/
$ cd sdcard
$ /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
$ /system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
$ /system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
$ ls /system/xbin/su
/system/xbin/su
$ su --version
0.83:SUPERSU
$ /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
$ /system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
$ /system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
$ ls /system/xbin/su
/system/xbin/su
$ su --version
0.83:SUPERSU
$ rm /system/xbin/su
rm failed for /system/xbin/su, Permission denied
$ ls -al /system/xbin/su
-rwsr-sr-x root root 91980 2012-03-24 01:40 su
$ /system/bin/cmdclient ec_micswitch '`chmod 6777 /system/xbin/su`'
$ ls -al /system/xbin/su
-rwsrwsrwx root root 91980 2012-03-24 01:40 su
$ rm /system/xbin/su
rm failed for /system/xbin/su, Permission denied
$ mv /system/xbin/su /mnt/sdcard/temp
failed on '/system/xbin/su' - Cross-device link
$ /system/bin/cmdclient ec_micswitch '`rm /system/xbin/su`'
$ /system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
$ /system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
$ /system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
$ ls /system/xbin/su
/system/xbin/su: No such file or directory
Now I have no su file... how can I restore it? Can anyone send me the su from their A100 (I guess it would be the same)
I can't understand why the rooting stopped. It use to work ok...maybe the interference of superuser and supersu caused this..
It happened after a restart...
Anyhow... how do I get my root back...? Any ideas...?
Sent from my A100 using Tapatalk
SuperSu and Superuser both use different su binaries. Which one are you going to use (it's not wise to have both or else they are going to interfere with each other).
The superuser stopped responding but I couldn't uninstall it. The posts I've for the supersu said that it dike not matter whether you have superuser isntalled,so I installed it.
I would prefer supersu I guess... but at the moment anything would be just fine....
Sent from my A100 using Tapatalk
dkaratasos said:
The superuser stopped responding but I couldn't uninstall it. The posts I've for the supersu said that it dike not matter whether you have superuser isntalled,so I installed it.
I would prefer supersu I guess... but at the moment anything would be just fine....
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
Are you running honeycomb or ICS?
Theonew said:
Are you running honeycomb or ICS?
Click to expand...
Click to collapse
Honeycomb
Sent from my A100 using Tapatalk
dkaratasos said:
Honeycomb
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
Try re-rooting using this method: http://forum.xda-developers.com/showthread.php?t=1472521.
Theonew said:
Try re-rooting using this method: http://forum.xda-developers.com/showthread.php?t=1472521.
Click to expand...
Click to collapse
I did but did not work
$ sh root.sh
Copying root file & changing permissions (making your tab super!) Please wait...
-rwsr-sr-x root root 22148 2012-04-01 01:45 su
If su is listed above with out errors and is bigger than 0 bytes... That's all folks!!
Now you need to install superuser and open it, then go to the wrench icon and tap it
Find the update area and tap it, tap update now to update the super user file that this script copied over earlier
Once its updated, install busybox from the market and your all set!
$
Both superuser and supersu could not gain root shell...
If you check the size of the su file in xbin now and initially you will see a big difference ...
Can someone upload their su file...? Isn't it the same...?
Sent from my A100 using Tapatalk
I opened the root.sh ...
It has the same commands as a script... it would not do anything different...
Root.sh:
echo "Copying root file & changing permissions (making your tab super!) Please wait..."
sleep 2
/system/bin/cmdclient ec_micswitch '`mount -o remount,rw /system`'
sleep 2
/system/bin/cmdclient ec_micswitch '`cat /mnt/sdcard/su >/system/xbin/su`'
sleep 2
/system/bin/cmdclient ec_micswitch '`chmod 6755 /system/xbin/su`'
sleep 1
rm /mnt/sdcard/su
echo " "
ls -l /system/xbin/su
echo " "
echo "If su is listed above with out errors and is bigger than 0 bytes... That's all folks!!"
echo " "
echo "Now you need to install superuser and open it, then go to the wrench icon and tap it"
echo "Find the update area and tap it, tap update now to update the super user file that this script copied over earlier"
echo "Once its updated, install busybox from the market and your all set!"
Sent from my A100 using Tapatalk
The only thing left to try is a factory reset (or update to ICS if you want to keep all your data) then re-root (that will work). In these cases, one would just flash superuser via recovery, but since you are on HC and have no custom recovery, that simple fix is not possible.
How about taking the su file from an other A100...? Even a non rooted A100.. won't that work...?
Sent from my A100 using Tapatalk
dkaratasos said:
How about taking the su file from an other A100...? Even a non rooted A100.. won't that work...?
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
A non-rooted device does not have a su binary. The su binary of a rooted one would be the same as the one here: http://goo-inside.me/superuser/su-bin-3.0.3.2-efghi-signed.zip (until there's an update at least ).
Theonew said:
A non-rooted device does not have a su binary. The su binary of a rooted one would be the same as the one here: http://goo-inside.me/superuser/su-bin-3.0.3.2-efghi-signed.zip (until there's an update at least ).
Click to expand...
Click to collapse
That confuses me.... but then why the rerooting process did not work,if there was not already a su file there...? And why the scripts use cat instead of the simple cp ...? Even more... why the size of the su I had before is different than the new one..? Are you sure there is no su file on a non rooted A100..?
Sent from my A100 using Tapatalk
I did it... I tried a few different su versions I had downloaded in the past and one worked... with superuser ... the supersu crashes....
I got rid of supersu and through superuser I updated the su file..it worked like a charm...
Thanx for your help...
Sent from my A100 using Tapatalk
dkaratasos said:
That confuses me.... but then why the rerooting process did not work,if there was not already a su file there...? And why the scripts use cat instead of the simple cp ...? Even more... why the size of the su I had before is different than the new one..? Are you sure there is no su file on a non rooted A100..?
Sent from my A100 using Tapatalk
Click to expand...
Click to collapse
1. Corruption.
2. That's the chosen "exploit".
3. SuperSu's su binary will be a different size than Superuser's su binary.
4. No non-rooted device has a su binary. The su binary allows root access (which a non-rooted device does not have). The rooting process places the su binary in a device.
dkaratasos said:
I did it... I tried a few different su versions I had downloaded in the past and one worked... with superuser ... the supersu crashes....
I got rid of supersu and through superuser I updated the su file..it worked like a charm...
Click to expand...
Click to collapse
Great.
P.S. - You should have said you still had SuperSu installed.
And u should recheck next time on supersu's description I'm pretty sure it says u can't b running both
Sent from my A100 using Tapatalk 2 Beta-4
raphsabb said:
And u should recheck next time on supersu's description I'm pretty sure it says u can't b running both
Sent from my A100 using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
Well according to chainfire here
http://forum.xda-developers.com/showpost.php?p=23442897&postcount=43
Both can be installed and whichever you update the su file grants you the superuser ....
It crashes thought having both...
Sent from my A100 using Tapatalk
They can both be installed but not used together, I added a screenshot of the description in play store, hopefully u can see it from my screenshot
{
"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"
}
Sent from my A100 using tapatalk
Hi,
I'm facing a similar but slightly different problem and looking for some help. Here's the situation:
- I have a rooted galaxy s2 running CM7
- I recently deleted the su binary (why I did that is another story)
- I don't have SuperSU
How can I get root back?
Thanks!
aharol said:
Hi,
I'm facing a similar but slightly different problem and looking for some help. Here's the situation:
- I have a rooted galaxy s2 running CM7
- I recently deleted the su binary (why I did that is another story)
- I don't have SuperSU
How can I get root back?
Thanks!
Click to expand...
Click to collapse
Try doing an advanced restore of system assuming you have a nandroid of that rom that's decently recent. Would also work for the a100 on ICS, but is dependant on having a nandroid of the current rom and is somewhat up to date. This will restore your busy box and super user and root. Don't restore system from another rom. Wipe cache and dalvik after restore. Other option, flash the rom directly over the current install, though I wouldn't suggest it.
Tapatalked from my Galaxy S II.
pio_masaki said:
Try doing an advanced restore of system assuming you have a nandroid of that rom that's decently recent. Would also work for the a100 on ICS, but is dependant on having a nandroid of the current rom and is somewhat up to date. This will restore your busy box and super user and root. Don't restore system from another rom. Wipe cache and dalvik after restore. Other option, flash the rom directly over the current install, though I wouldn't suggest it.
Click to expand...
Click to collapse
I'm a relative noob so let me restate to make sure I understand.
- do a reboot in recovery mode
- go to the .zip file of the current rom (CM7 --- the file I have is the latest) and run it
- AFTER that is done (and not before?), wipe the cache and dalvik cache
Is this correct. Any critical step that I'm missing?
Thanks
I have create a script file that will flash a recovery from the terminal in the Galaxy Nexus.
I got the command from xda but I could not remember it when I wanted to flash a recovery,
so I wrote a script to do it.
AS WITH ANY FLASHING OR MODDING OF "YOUR" PHONE, I AM NOT RESPONSIBLE FOR ANY DAMAGES YOU MAY CAUSE!
I have tested this on my:
Unlocked Galaxy Nexus 4.1.1 takju (flashed from yakju)
Sprint Galaxy Nexus 4.0.4
Thanks to -viperboy- for help.
Code:
Created by Smurph82 2012_0512 (c) v1.0
flashr [-h] [-r] [-m] [-s s] -- Flash a recovery
to the Galaxy Nexus.
where:
-h show this help text
-r will reboot after flashing is complete.
-m image is in the root of the sdcard
-s source of the recovery image (/sdcard/recovery.img).
To use the script:
Download and Flash the script file from your current recovery
Or download the zip file and move the flashr file in the /system/bin folder to /system/bin with RootExplorer
or other root level file manager.
If you manually add the file you must
Code:
chmod 0755 /system/bin/flashr
or change the permissions from RootExplorer
Then open Terminal and type
Code:
su
first, yes you have to be rooted to do this!
Next type
Code:
flashr
or
Code:
flashr -h
to get the help
If you want to flash a recovery you must have the recovery.img
somewhere on your device that you can remember. Like the root of the sdcard.
To flash a recovery type
Code:
flashr -s /sdcard/recovery.img
or if the recovery is in the root of the sdcard type
Code:
flashr -ms recovery.img
If you want to reboot after the flashing is complete next use
Code:
flashr -mrs recovery.img
In the code examples above I used recovery.img as an example.
This should be "what ever you named the recovery".img it does not have to be recovery.
Reserved
Change Log:
v1 - Initial Release
i know you might think that im trolling, but im really not. what id like to know is what makes that better than just flashing the recovery, via the terminal, the old-fashioned way..
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter, if you want to go to the recovery)
providing ithe file is on the main fs in the sd storage.
flash_image does not work with ics, that I have found. So I wrote my own. If there is a new flash_image that works with the galaxy nexus then I could not find it. Maybe it is because I'm still using the stock rom and kernel. I took the flash_image out of cm9 but it didn't work for me.
Sent from my Galaxy Nexus using XDA Premium HD app
Would you be willing to share the sources for this? It would be interesting to know how this works, since it may be useful also for other purposes than flashing recovery images. Or not?
I will post the source later today. It really is not much.
Sent from my Transformer Prime TF201 using XDA Premium HD app
E:V:A said:
Would you be willing to share the sources for this? It would be interesting to know how this works, since it may be useful also for other purposes than flashing recovery images. Or not?
Click to expand...
Click to collapse
Hope that this is helpful to someone.
Code:
#!/system/bin/sh
usage="Created by Smurph82 2012_0512 (c) v1.0
flashr [-h] [-r] [-m] [-s s] -- Flash a recovery
to the Galaxy Nexus.
where:
-h show this help text
-r will reboot after flashing is complete.
-m image is in the root of the sdcard
-s source of the recovery image (/sdcard/recovery.img)."
# Read in the options turn off verbose and require -s to have input
while getopts :hrms: opt; do
case $opt in
h) echo "$usage"
echo
exit;;
m) sdroot="/sdcard/";;
s) sourcedir=$OPTARG;;
r) reboot="t";;
*) echo
echo
echo "Invalid option: -$OPTARG" >&2
echo "$usage"
echo
exit;;
esac
done
shift $(($OPTIND - 1))
# This was for testing
#echo
#echo "Vars: m $sdroot: s $sourcedir: r $reboot: dir $sdroot$sourcedir"
#echo
# Check to make sure somthing was typed if not show help
if [ "$sourcedir" == "" ]; then
echo "$usage"
echo
exit
else
# Check that something is in that location if not dont flash
if [ -s $sdroot$sourcedir ]; then
echo "Flashing image from: $sdroot$sourcedir"
cat $sdroot$sourcedir > /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
else
echo "File not found at $sdroot$sourcedir"
exit
fi
fi
# Early in the morning I was getting cute
if [ "$reboot" == "t" ]; then
echo "Rebooting in 5.."
sleep 1
echo "Rebooting in 4.."
sleep 1
echo "Rebooting in 3.."
sleep 1
echo "Rebooting in 2.."
sleep 1
echo "Rebooting in 1.."
sleep 1
reboot recovery
fi
thank u very much for this! so easy now!!
It is just as easily done in a terminal by the following (assuming you downloaded the recovery you want to /sdcard and named it recovery.img):
su
dd if=/sdcard/recovery.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
efrant said:
It is just as easily done in a terminal by the following (assuming you downloaded the recovery you want to /sdcard and named it recovery.img):
su
dd if=/sdcard/recovery.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
Click to expand...
Click to collapse
Yes I know that but who wants to type all of that out. I just made it shorter more
or else. If you want to type the whole command then by all means have at it. I just
think that "flashr -mrs twrp.img" is a whole lot easier. Just my thoughts.
Hi
Nice enough script.
Although I feel I should warn people that it looks like this script will write anything you tell it. making no effort to verify that the file is a valid or correct for your phone. so be careful not to specify the wrong file.
fastboot flash recovery $file is much safer.
That is true if you are connected to a computer but this script is run on the phone from the terminal. If someone knows a way to check a file from the terminal running on the phone please tell me and I will update the script. I understand that there is currently no verification of the file that is being written so please make sure that you are writing the right file.
Sent from my Galaxy Nexus using XDA Premium HD app
i need to know if there is a comand to see the current formatting of system,data and cache
thanks
sorry for bad english
Not sure if this is what your looking for but using terminal emulator on phone type, Su then enter then type busybox df -h then enter, making sure you space after df
UTID
founded
it s "mount" with adb shell
thanks
Hi
I received my new Oneplus 5T and installed everything on it. So far so good, the only problem I have is to re-use my tasker scripts.
Some of those scripts use shell command to send a sqlite3 request on various databases located in /data/data/...
The problem is that those scripts doesn't work anymore, seems unable to access /data/data/...
Using a terminal emulator, the same command works very well.
I don't understand what's happen now.
Found the solution.
I added the su command before the sqlite3 command:
su
sqlite3 ....
Instead of using the root tickmark.
The proposed solution only works with SuperSU. It doesn't work under magisk.
pantale said:
The proposed solution only works with SuperSU. It doesn't work under magisk.
Click to expand...
Click to collapse
Have you tried adding -c to the su command? The shell command would then be:
Code:
su -c sqlite3...
Didgeridoohan said:
Have you tried adding -c to the su command? The shell command would then be:
Click to expand...
Click to collapse
Doesn't work, even with quotes.
Work well using SuperSU but not with Magisk
Here is the error message:
09.29.16/E Lancer un Shell: %folder -> %folder
09.29.16/E Lancer un Shell: ->
09.29.16/E Lancer un Shell: ->
09.29.16/Shell runBackground su -c 'sqlite3 /data/data/me.bluemail.mail/databases/2513211d-9c12-4de3-ba85-67b5a78cc0c3.db "SELECT id FROM folders WHERE name=\"INBOX\";" ' root: false timeout: -1
09.29.16/Shell start process-thread ID 391
09.29.16/E add wait type Shell1 time 2147483647
09.29.16/E add wait type Shell1 done
09.29.16/E add wait task
09.29.16/Variables doreplresult: |%folder| -> |%folder|
09.29.16/E Erreur: 134
Using SuperSU the Tasker sqlite3 plugging doesn't work also.
Seems unable to access /data/data/...
Even with root authorization.
Can this be related to encrypted data partition ?
Finally, I found the solution...
Had to find a 64bits version of sqlite3, and now it works normaly.