Develop Bugs

Moving Power Manager Pro to /system/app

Long post but, hopefully an easy answer that someone can walk me through. I have fully rooted my EVO along with the NAND. I'm trying to move/install (?) Power Manager Pro into the /system/app folder to get full rights so it can turn GPS on/off. The website for the app says that I need to do the following:
After root is obtained you need to install the application into the /system/app directory so that it has enough permission to change the location settings. Open a Terminal Emulator app and execute the following command to copy the application to the sdcard (for the full version the name of the application is /data/app/com.acme.android.powermanagerpro.apk):
su
cp /data/app/com.acme.android.powermanager.apk /sdcard/PowerManager.apk
If you can't find the application in /data/app try /data/apps-private/
Then, un-install Power Manager from the device
Execute the following commands in the terminal emulator to remount the /system directory as read/write and to install the application into the /system/app directory:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/PowerManager.apk /system/app
If you prefer to use adb from your computer, execute these commands:
adb remount
adb shell cp /sdcard/PowerManager.apk /system/app
Several users have utilized root explorer from the Google marketplace to simplify this process.
I have Root Explorer so I would like to do it through there is possible, but I can't seem to get it to work without it getting a FC when it opens after trying to move it.

hmmm, it might be force closing because the system is not mounted as read/write. Never used the app before so I dont know. But you can search the market for terminal emulator and then follow the steps the showed above. It looks like it should work.
...or you could do it through adb shell if you are connected to your 'puter

Trying it in Terminal Emulator with no luck... Wondering if the path is right or if i need to change that? It says:
xport PATH=/data/local/bin:$PATH
$su
cp /data/app.acme.android.powermanagerpro.apk /sdcard/PowerManager.apk
cp: not found

the path seems right (I assume you mean export and not xport). I dont think you need anything special on the rom to access cp through terminal emulator...
Have you tried hooking it up to a computer and entering it through adb shell to see if that works?

[Q] youtube app porting help!!! please!!!

can someone please post DETAILED isntructions to put froyo or gingerbread youtube app thing on samsung epic 4g. ive tried so many time and cant do it. and i delted the stock youtube app with titanium but cant install the other app and i dont wanna pay for root explorer cuz idk if its gonna help at all. i tried using the cmd promt but it says permission denied everytime and it also says adb is not recognized as an internal storage.. PLEASE SOMEONE HELP MEEE I DONT HAVE A YOUTUBE AP AT ALL NOW!!!!!

betterment66 said:
can someone please post DETAILED isntructions to put froyo or gingerbread youtube app thing on samsung epic 4g. ive tried so many time and cant do it. and i delted the stock youtube app with titanium but cant install the other app and i dont wanna pay for root explorer cuz idk if its gonna help at all. i tried using the cmd promt but it says permission denied everytime and it also says adb is not recognized as an internal storage.. PLEASE SOMEONE HELP MEEE I DONT HAVE A YOUTUBE AP AT ALL NOW!!!!!
Click to expand...
Click to collapse
The new YouTube.apk just needs to be placed in '/system/app'. What I did was remove the original YouTube.apk and put the new one in its place and voila. Here is the method adapted for Windows (I think it's all right for Windows). This is also assuming you rooted with a one click root that included the remount script and that you have adb on your computer (the one click rooter should have adb included with it).
1. in the cmd prompt, go to the folder where you have adb and type:
Code:
adb.exe shell
2. inside shell:
Code:
$ su
# remount rw
# mkdir /sdcard/backup
# cp /system/app/YouTube.apk /sdcard/backup
# rm /system/app/YouTube.apk
# exit
$ exit
3. now in the cmd prompt again:
Code:
adb.exe push \path\to\YouTube.apk /system/app
4. Reboot the phone.

gremlyn1 said:
The new YouTube.apk just needs to be placed in '/system/app'. What I did was remove the original YouTube.apk and put the new one in its place and voila. Here is the method adapted for Windows (I think it's all right for Windows). This is also assuming you rooted with a one click root that included the remount script and that you have adb on your computer (the one click rooter should have adb included with it).
1. in the cmd prompt, go to the folder where you have adb and type:
Code:
adb.exe shell
2. inside shell:
Code:
$ su
# remount rw
# mkdir /sdcard/backup
# cp /system/app/YouTube.apk /sdcard/backup
# rm /system/app/YouTube.apk
# exit
$ exit
3. now in the cmd prompt again:
Code:
adb.exe push \path\to\YouTube.apk /system/app
4. Reboot the phone.
Click to expand...
Click to collapse
ok i get to remount rw but the when i type in the nect code it says
mkdir falied for /sdcard/backup read-only filesystem

I install it using terminal emulator.
All I do is type
Su
#rm /system/app/YouTube.apk
#cp /sdcard/DirectoryWithTheYoutubeApp/YouTube.apk /
system/app
Or after you rm, just use the "My Files" app and go on your sdcard and click YouTube.apk and it'll install and work fine. But remember to sign out of youtube before you close it by going to your page and clicking sign out or else it'll keep force closing after you start it up.
I hope I helped...
Sent from my SPH-D700 using XDA App

you guys are gonna freaking kill me. ALL THE TROUBLE I WAS HAVING WAS BECAUSE I HAD MY SDCARD MOUNTED THE WHOLE TIME I WAS TRYING TO DO THIS THE MINUTE I TRIED IT WITHOUT IT BEING MOUNTED IT WORKED...IM SO DUMB!!!!! LOL BUT THANKS FOR THE HELP ALL OF U!!!!!! U GUYS ROCK!!!! N SO DOES THE NEW UTUBE APP .....BTW I UNDERSTAND UR NOT SUPPOSED TO SIGN IN TO IT RIGHT???

I just uninstalled the original, put the modded youtube.apk in the SDX backup folder and installed (restored) it with SDX stock app remover. Simple, fast and no typing required.
Glad you got it worked out though.

me 2!!! this app rocks

Glad it's working! Having the SD card mounted while trying to adb is a common mistake and always a good first troubleshooting check.

Google Wallet Help (ADB Shell related)

I'm going through these instructions but they are pretty complicated for me.
lukegb said:
Instructions for getting rid of ZIP version only <4.0.3:
Open ClockworkMod Recovery
Download the correct files from http://googlewallet.lukegb.com/stock/system/ that match your Android build and system - ICL53F is Android 4.0.2, yakju is GSM and mysid is LTE.
You'll need:
NfcGoogle.apk
com.android.nfc_extras.jar
Open an adb shell from your computer to your device from the directory you've just downloaded those files to
Run (on device via adb shell):
Code:
mount /system
mount /data
rm /system/app/Wallet.*
rm /system/app/NfcGoogle.*
rm /system/framework/com.android.nfc_extras.*
exit
Run (on computer):
Code:
adb pull /data/system/packages.xml packages.xml
Make a backup of the newly-created packages.xml file which is on your computer
Open packages.xml in a text editor (which isn't notepad)
Copy ALL the content
Open http://googlewallet.lukegb.com/gn_packages_xml_fixer.html in a web browser
Paste the content into the left-hand "Input" box
Click "Fix it"
Copy ALL the content from the right-hand "Output" box
Delete all the content in the text editor with packages.xml open
Paste the content
Save packages.xml
Close your text editor
Run (on computer):
Code:
adb push NfcGoogle.apk /system/app/NfcGoogle.apk
adb push com.android.nfc_extras.jar /system/framework/com.android.nfc_extras.jar
adb push packages.xml /data/system/packages.xml
adb shell chmod 644 /system/app/NfcGoogle.apk
adb shell chmod 644 /system/framework/com.android.nfc_extras.jar
You're done.
EDIT (28/12/11)
Important notice for all those who have already attempted to remove the ZIP version to replace with the APK version
Read this if NFC has disappeared from your more menu, you get crashes in the More menu, Wallet now forcecloses where it didn't before after removing the ZIP
I have just (idiotically) noticed a blindingly obvious flaw with the files I had previously uploaded to the stock folder on http://googlewallet.lukegb.com - they were the odexed versions of the files, crucially WITHOUT the .odex files. I've replaced them with pseudo-stock (same signatures) versions of the apks and if you replace the NfcGoogle.apk, Android should correctly take this into account.
Don't forget to chmod 644 the NfcGoogle apk and the com.android.nfc_extras.jar files!
Click to expand...
Click to collapse
I'm stumped here: Open an adb shell from your computer to your device from the directory you've just downloaded those files to
I can open cmd and open adb shell but i don't understand how to open adb from the directory where i donwloaded said files.

Are you trying to install Google Wallet thru ADB? Why don't you just install it from Google Play?

babymatteo said:
Are you trying to install Google Wallet thru ADB? Why don't you just install it from Google Play?
Click to expand...
Click to collapse
I'm trying to fix google wallet because it is giving me an error. The post I quoted shows me the directions to fix that error.

Best thing to do is put the file(apk) in the tools directory of the android-sdk directory and use the exact same command
Same thing for the jar file...

haitu said:
[snip]
I can open cmd and open adb shell but i don't understand how to open adb from the directory where i donwloaded said files.
Click to expand...
Click to collapse
Open a command prompt and navigate to where the directory is. For example, let's say you downloaded the files to C:\users\n00b\desktop\junk, and you open a command prompt and it opens in C:\users\n00b\, then all you have to do is type:
cd /users/n00b/desktop/junk
Make sure you have your adb files in that directory.

haitu said:
I'm trying to fix google wallet because it is giving me an error. The post I quoted shows me the directions to fix that error.
Click to expand...
Click to collapse
Just out of curiosity, what error are you getting?

[Q] HELP!!! Lcd Density Problem !!

Hi everybody,
Sorry for my bad english, i'm italian,
I've a problem with my a100 with stock ics. yesterday i've rooted it and i've installed lcd density modder. now, i've do a mistake and saved the dpi instead of temp apply. after the reboot the home won't start cause it freeze. i can only have access to settings i can't access the lcd density app. i've tried to reset to factory but it's still the same. Can anyone help me ?
thanks

Use adb to pull build.prop from /system use some text editor to open it and find this line ro.sf.lcd_density= and change it to ro.sf.lcd_density=160 then reboot.
The exact commands are :
Code:
adb pull /system/build.prop build.prop
adb push build.prop /system/build.prop
adb shell reboot

thank you so much, resolved

can you explain how to pull it up into the text editor i'm afraid i have the same problem and found this thread i enter the pull command and recieve this in cmd prompt:
C:\Users\Owner>adb pull /system/build.prop build.prop
224 KB/s (1841 bytes in 0.008s)
and now i'm lost.....

ilovemywife269 said:
can you explain how to pull it up into the text editor i'm afraid i have the same problem and found this thread i enter the pull command and recieve this in cmd prompt:
C:\Users\Owner>adb pull /system/build.prop build.prop
224 KB/s (1841 bytes in 0.008s)
and now i'm lost.....
Click to expand...
Click to collapse
Open your editor and then open build.prop in it.
Or name it build.txt then edit it then save as build.prop.
Tapatalked from my Galaxy S II.

pio_masaki said:
Open your editor and then open build.prop in it.
Or name it build.txt then edit it then save as build.prop.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
i'm a noob here i need more details on how exactly i should go about getting it opened

ilovemywife269 said:
i'm a noob here i need more details on how exactly i should go about getting it opened
Click to expand...
Click to collapse
Open whatever editor you want, then click on help for how to open documents in that program.
Otherwise, file>open>whereveryousavedit/build.prop
Then file>save.
Edit: for windows I suggest notepad++
Tapatalked from my Galaxy S II.

pio_masaki said:
Open whatever editor you want, then click on help for how to open documents in that program.
Otherwise, file>open>whereveryousavedit/build.prop
Then file>save.
Edit: for windows I suggest notepad++
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
ok i didn't save it anywhere how do i save it?

ilovemywife269 said:
ok i didn't save it anywhere how do i save it?
Click to expand...
Click to collapse
C:\Users\owner\build.prop from what you posted before.
Tapatalked from my Galaxy S II.

pio_masaki said:
C:\Users\owner\build.prop from what you posted before.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
ok now i get:
C:Users\Owner>adb push build.prop /system/build.prop
failed to copy 'build.prop' to '/system/build.prop' : Read-only file system

what am i doing wrong shouldn't it be in a Read-Write system?

ilovemywife269 said:
what am i doing wrong shouldn't it be in a Read-Write system?
Click to expand...
Click to collapse
adb remount
adb push build.prop /system/build.prop
Edit: if that fails try this:
adb shell mount -o remount,rw -t ext4 /dev/block/mmcblk0p3 /system

mount: permission denied (are you root?)
i was rooted before i factory reset i went through the adb root method which is basicaly how i achieved root to begin with except i used a cmd prompt terminal app and did it all on my tablet and now i'm not sure i never had a "full" root idk how to explain that but it told me i was rooted and could run root apps and such but it still limited me on a few things if this helps i have
"bootloader 0.03.06-ics (unlocked)"
it came stock with gb or honeycomb i had to find a .zip file to get ics
now i've tried to adb root again and failed i'm not sure why...

ilovemywife269 said:
mount: permission denied (are you root?)
i was rooted before i factory reset i went through the adb root method which is basicaly how i achieved root to begin with except i used a cmd prompt terminal app and did it all on my tablet and now i'm not sure i never had a "full" root idk how to explain that but it told me i was rooted and could run root apps and such but it still limited me on a few things if this helps i have
"bootloader 0.03.06-ics (unlocked)"
it came stock with gb or honeycomb i had to find a .zip file to get ics
now i've tried to adb root again and failed i'm not sure why...
Click to expand...
Click to collapse
OK time for info then. What ROM are you on? What recovery? Why did you use a method other then one intended for the a100? Being rooted but limited is probably due to missing or bad busy box installation.
Tapatalked from my A100 - Kuroikaze B3

i used an update zip for what i believed to be a stock ics rom and i rooted with a method that was intended for the a100:
Download the su binary from here.
Hook your device to the computer via USB cable.
Copy the su binary file to /mnt/sdcard/ on your tablet.
Open a command prompt on your Windows computer.
Change directory to where ADB is located. (This is usually the /tools or /platform-tools directory inside the Android SDK installation directory.)
Type in the following commands at the terminal (press Enter after each command):
adb shell /system/bin/cmdclient ec_micswitch ‘`mount -o remount,rw /system`’
adb shell /system/bin/cmdclient ec_micswitch ‘`cat /mnt/sdcard/su >/system/xbin/su`’
adb shell /system/bin/cmdclient ec_micswitch ‘`chmod 6755 /system/xbin/su`’
Install the Superuser app from the Android Market.
i used this method but i used terminal emulator on my tablet i didn't use adb
here is the update zip i used for ics- this is the error i get trying to attach the zip file:
The connection was reset
The connection to the server was reset while the page was loading.
The site could be temporarily unavailable or too busy. Try again in a few
moments.
If you are unable to load any pages, check your computer's network
connection.
If your computer or network is protected by a firewall or proxy, make sure
that Firefox is permitted to access the Web.

Use the script as intended. From the PC. If you go running them on the tab itself you may have missed one somewhere.
You can't attach a file that large to a post.
Tapatalked from my Galaxy S II.

when i enter the first shell command it denies me and asks me if i am root......

ilovemywife269 said:
when i enter the first shell command it denies me and asks me if i am root......
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=23285307
Use this method.
Tapatalked from my Galaxy S II.

i tried both ics rooting methods both of which told me they achieved root however i am still denied permission to remount

with my moto phones i've always been able to flash back to stock.....or flash back to life anyways is there a way to flash this tablet?

[UNIVERSAL GUIDE] Root Any Android Device Manually !

THIS GUIDE NO LONGER WORKS BECAUSE ANDROID ISN'T WHAT IT USED TO BE BACK IN 2013-14.
PLEASE STOP WASTING TIME TO FOLLOW THIS OBSOLETE METHOD 1. PLEASE REFER ONLY TO METHOD 3​
The Ultimate Guide to Rooting any Android Device Manually !!!!​
Wanting to ROOT Your Phone but can't do Because Of No rooting Guides or want to learn to root any device ? Then , This Guide Is For YOU
OK So lets start....
**What You Need**
1.Your Unrooted Android Device.
2.ADB Drivers Installed On Your PC. If you Don't Have Download From Here :
Code:
adbdriver.com/‎
3. The Most Inportant Root Kit Made By Me (N'ayam Amarsh'e) - Download From The Attachment.
4.Strength And Courage 'Coz Rooting Voids Your Warranty... If You have a samsung device then Don't Worry Your warranty is gone forever... But if you own any other, maybe you can void it or maybe......
I've Written Android Device as ADV to make it more easy....
**Steps**
So you have the adb drivers installed let's go....
1. Open The root kit by Extracting The Rootkit with WinRAR....
2.Turn 'USB DEBUGGING' 'ON' in your ADV...
3. Connect your ADV to Your PC...
4.In the root kit Open Cmd.exe File ... [ IF YOU CAN'T OPEN CMD, GOTO C:/WINDOWS/SYSTEM32/ COPY CMD .EXE TO YOUR ROOTKIT FOLDER]
5. In CMD window Type the following command...
Code:
->adb devices *Your device will get listed in the window if it doesn't check your adb drivers or if you have followed the steps properly...
->adb push busybox /data/local/tmp
->adb push su /data/local/tmp
->adb push Superuser.apk /data/local/tmp
If you Succeed Move On ...
6.Then You need Root Shell Type :
Code:
adb shell
Note that you see a "$" sign in the command prompt. That means you are not in 'su' shell.
7.Next run the following commands in the shell to change permissions and get some limited privileges for the Superuser files:
Code:
->chmod 6755 /data/local/tmp/su
->chmod 755 /data/local/tmp/busybox
->chmod 644 /data/local/tmp/Superuser.apk
{Note}The names of the files are case sensitive!
8.Done ? Now You need to open a copy of linux which has nautilus... So enter your linux (I recommend using ubuntu 11.4) and type in the terminal (ctrl+alt+T)
Code:
->sudo nautilus
this will open nautilus with root privileges...
You can just boot it from USB so no hassle of installing it... http://www.cyberciti.biz/tips/download-ubuntu-linux-11-04-iso-cd-dvd-images-natty-narwhal.html
Having your ADV connected with USB to PC switch it off and put it in download/recovery mode...
superlouro said:
DEVICE OFFLINE?
! SOLUTION ! (click me)
Click to expand...
Click to collapse
9.In The Exploring Window navigate to
Code:
/data/local/tmp
and move/cut 'su' and 'busybox' to
Code:
/system/bin
...
10.From the tmp Folder you went earlier Move/cut 'Superuser.apk' to
Code:
/system/app
11.Now Reboot You ADV ... Congrats ! You're now ROOTED !
Many Users Are Having Problem with This Method, If you can't do the method 1. Try Method 2.
METHOD 2
PLEASE DON'T ASK ME ABOUT THIS METHOD, THIS IS JUST FOR A TRY, MY BROTHER FOUND THIS METHOD TO BE WORKING, I HAVEN'T TRIED IT YET!
This is linux based method, It's quite easy if you follow every step correctly...
You need to download psneuter, https://github.com/tmzt/g2root-kmod/tree/master/scotty2/psneuter
When you have it execute the following...
Code:
adb devices
Code:
adb push psneuter /data/local/tmp
This will copy the file to your device and now we'll execute it..
Code:
adb shell
cd /data/local/tmp
chmod 777 psneuter
./psneuter
Now You'll see
Code:
adb kill-server
adb devices
adb shell
now # will appear in place of $, or after typing $su.
Code:
# mount -o remount,rw -t rfs /dev/block/st19/system
# exit
$ adb push busybox /system/bin
$ adb push su /system/bin
$ adb install Superuser.apk
$ adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/st19/system
# exit
$ adb reboot
Now your device will reboot and you can see SuperUser App in your app drawer...
----------------------------------------------------------------------
METHOD 3
There is no chance of the phone not getting rooted with my method but If you don't want to do the above methods, Try these, I'm pretty sure they will root your device with ease...
1. Framroot App [Not On Google Play]-http://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
2.KingoRoot App - www.kingoapp.com
3.One Click Root Free/Pro (My Favorite app, roots many devices with No-Brick Guarantee) - www.oneclickroot.com
4.Root Master App - forum.xda-developers.com/showthread.php?t=2672150
5.z4root App - http://forum.xda-developers.com/showthread.php?t=833953
6.Easy rooting toolkit App-http://forum.xda-developers.com/showthread.php?t=1321582
7.Vroot Software - http://vrootdownload.info/ or http://www.mgyun.com/en/getvroot
8.SRSRoot Software - http://www.srsroot.com
9.Unlock Root Software - http://www.unlockroot.com/download.html
10.Universal Androot App - forum.xda-developers.com/attachment.php?attachmentid=391774
ONLY FOR MTK DEVICES- MTK DROID TOOLS- http://forum.gsmhosting.com/vbb/f60...3-2014-imei-repair-rooting-tool-more-1780568/
HOPE THESE WILL DO....
Press Thanks To appreciate me to Work On Other Guides And Roms....
Your Appreciation Is Needed...
And This GUIDE IS Originally By N'ayam Amarsh'e

I have any error. Device is offline.
---------- Post added at 09:13 AM ---------- Previous post was at 09:02 AM ----------
uukasz92 said:
I have any error. Device is offline.
Click to expand...
Click to collapse
Problem solved i download another adb drivers and work fine

In /UserData/local/tmp i only have one file "directory" and nothing else. It's look like something block the data folder.

uukasz92 said:
In /UserData/local/tmp i only have one file "directory" and nothing else. It's look like something block the data folder.
Click to expand...
Click to collapse
that means you have not properly pushed the files into the directory.... Try installing adb drivers again and do the same steps...Good luck
When you open cmd just type ' adb devices' if your device gets listed then you can start if it doesn't check your drivers...

After uinstall all adb drivers and phone drivers comand prompt shows me a device code and status ofline. At the begining i install atached to therad package of adb drivers. But lately some where in Internet I find some update package of adb drivers. And there was the same sort of files like in your package. I put them there and replace and after that adb shows the device is working and status is online but your guide still does not work. Question is where is real problem ? I checked and Debug Mod is on, drivers are installed.

Try this , download android commander and try to copy the busybox , su and superuser to data/local/tmp

N'ayam Amarsh'e said:
Try this , download android commander and try to copy the busybox , su and superuser to data/local/tmp
Sent from my Mi-492 using xda app-developers app
Click to expand...
Click to collapse
I used the same files in android commander because program can't finde my device to.

Which phone you have.... Try to download its original drivers this might help...

I using Samsung Galaxy Grand Neo (GT-I9060) Jelly Bean 4.2.2
Now is working. But how to move "su" and busybox into system/bin ? Android commander says " You need root to do this." when i try to copy does files into system/bin. Folders are protected and I dont have premission to do anything with them.

uukasz92 said:
I using Samsung Galaxy Grand Neo (GT-I9060) Jelly Bean 4.2.2
Now is working. But how to move "su" and busybox into system/bin ? Android commander says " You need root to do this." when i try to copy does files into system/bin. Folders are protected and I dont have premission to do anything with them.
Click to expand...
Click to collapse
Sorry I forgot that Android Commander works only for rooted phones... Silly Me...
OK you will need to do it with Droid Explorer
OR
linux and in the linux you'll have to type 'sudo nautilus' it'll open it with root privilages...

N'ayam Amarsh'e said:
Sorry I forgot that Android Commander works only for rooted phones... Silly Me...
OK you will need to do it with Droid Explorer
OR
linux and in the linux you'll have to type 'sudo nautilus' it'll open it with root privilages...
Click to expand...
Click to collapse
And in your guide need little correct. In step 9 should be /data/local/tmp not /UserData/local/tmp. Does are two diffrent folders. And before I think I do something wrong when all files be already on right place

Droid Explorer cant change folders premission too. Command prompt says : Read-only drirectory. I don't know what to do now.

uukasz92 said:
And in your guide need little correct. In step 9 should be /data/local/tmp not /UserData/local/tmp. Does are two diffrent folders. And before I think I do something wrong when all files be already on right place
Click to expand...
Click to collapse
thanks.... Guide is updated now

Good 1 helped alot

harmeet singh said:
Good 1 helped alot
Click to expand...
Click to collapse
I am happy that I helped....

Hi! First thank you for that guide. I rooted several devices but with a noname(10.1" A10 dual core) china tablet I have some problems so I hope your solution works.
I have some problems/questions:
1. Step 5: Are you sure it's:
Code:
adb push su /data/local/tmp
instead of
adb push su /data/local/tmp[B][SIZE="5"]/[/SIZE][/B]
I'm currently not able to look at the data folder but if I change the directions e.g to /test/local/tmp it just creates a "tmp" file and overwrites the file with every push command.
2. Step 6: If it's a $ it's not rootet, what should be there if it's rooted? I have a # there. Rootchecker says it's rooted since the beginning, but I cant access with superuser/supersu etc.
3. Step 8 doesn't work. I use a virtual box with ubuntu 13.10(Stinson: new is always better?) for the first time. With "sudo nautilus" I get the message that root access is not granted(failed to register client). I used "gksudo nautilus" instead... does that matter?
4. I can't connect my device to the virtual box. I tried to add the usb device but didn't work. USB Developer Android[0223] is in virtual box connected. However, I dont know where to find it in ubuntu. I'm a ubuntu noob sorry :/
5. Is there another way to get rw permissions?
Thanks in advance :good:

thankyou for information i think is hard for me

Very nice, ty

Humbel said:
Hi! First thank you for that guide. I rooted several devices but with a noname(10.1" A10 dual core) china tablet I have some problems so I hope your solution works.
I have some problems/questions:
1. Step 5: Are you sure it's:
Code:
adb push su /data/local/tmp
instead of
adb push su /data/local/tmp[B][SIZE="5"]/[/SIZE][/B]
I'm currently not able to look at the data folder but if I change the directions e.g to /test/local/tmp it just creates a "tmp" file and overwrites the file with every push command.
2. Step 6: If it's a $ it's not rootet, what should be there if it's rooted? I have a # there. Rootchecker says it's rooted since the beginning, but I cant access with superuser/supersu etc.
3. Step 8 doesn't work. I use a virtual box with ubuntu 13.10(Stinson: new is always better?) for the first time. With "sudo nautilus" I get the message that root access is not granted(failed to register client). I used "gksudo nautilus" instead... does that matter?
4. I can't connect my device to the virtual box. I tried to add the usb device but didn't work. USB Developer Android[0223] is in virtual box connected. However, I dont know where to find it in ubuntu. I'm a ubuntu noob sorry :/
5. Is there another way to get rw permissions?
Thanks in advance :good:
Click to expand...
Click to collapse
For Your First Answer You Need not to worry /tmp and /tmp/ are the same...
2.Have you tried typing 'adb shell' then ' su ' if yes there's your solution.... If not then you have problem with su binary or busybox....
3.You have an Ubuntu 11.4 .iso file so burn it to a blank disk and boot your live disk .... It should be all right then...
4.Answer in 3....
5.Answer in 3....
6.Press Thanks if I helped...

bro im confused wt to do exactly in that sudo ... step pls give a brief explaination