Hello,
I have created a ROM, but it does not have root access - how do I add root access to this ROM?
Thanks,
Isaac
From what I remember you need to go to Terminal, and type in:
Code:
telnetd
After that...
# Download an Android "Telnet" application from the Market and connect to localhost.
# If you connect successfully, you will have a root prompt "#".
# Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Click to expand...
Click to collapse
That's only for RC29 though, and in RC29 it executed anything you typed in, so you are supposed to type it into the home screen. More info here:
http://forum.xda-developers.com/showthread.php?t=442480
Hopefully it will work on the ROM you worked on as well.
Good luck!
Big fan of your app, btw.
i want a SiriusXM player, and got mad you didn't have one,
isaacwaller said:
Hello,
I have created a ROM, but it does not have root access - how do I add root access to this ROM?
Thanks,
Isaac
Click to expand...
Click to collapse
Boot into the recovery console (power + home) and then drop into the shell (alt+x).
Then do this:
Code:
# mount system
# cd /system/bin
# cat sh > su
# chmod 4755 su
# reboot
Thanks! That worked perfectly!
can someone give me a tutorial on how to update the user.conf..i have looked at the compcache threads and linux swap but im not getting it...i want to be able to update it through terminal emulator and do i have to do nething to the userinit.sh if i change the user.conf...because numerous configs i have done for swappiness and linux swap...etc, have shown no difference..can somone give me a walkthrough...thanks so much..sry if i have a lot of questions just want to make myself more knowledgeable so i can hopefully return the favor to somone else one day
i do not know if you can edit it through the terminal sorry. i do know that you do not have to change the userinit.sh if you change user.conf, also i do know that you can open it up with PSPad (thats what i use) on a computer edit it there and push it back to phone and reboot. sorry i couldn't answer all of your questions
well i have had no problems editing it...its just putting it back nd making sure it works..now i have no problem using adb if u know of a tutorial to use it on mac...or know how to use it on mac
when you put it back on the phone did you make sure to chmod 755 it after you put it back on the phone and reboot?
then to text it with adb just type adb shell sh /system/sd/userinit.sh -s and see if the new values you put in are reflected in the output of that command
david1171 said:
when you put it back on the phone did you make sure to chmod 755 it after you put it back on the phone and reboot?
then to text it with adb just type adb shell sh /system/sd/userinit.sh -s and see if the new values you put in are reflected in the output of that command
Click to expand...
Click to collapse
delete this post; see below...
david1171 said:
when you put it back on the phone did you make sure to chmod 755 it after you put it back on the phone and reboot?
then to text it with adb just type adb shell sh /system/sd/userinit.sh -s and see if the new values you put in are reflected in the output of that command
Click to expand...
Click to collapse
this applies to tools and location of user.conf on cyanogen's roms ->
-transfer it to the root of your sdcard from your pc or mac to the g1.
-unmount sdcard from dropdown on the g1
-open up terminal on the g1
type and hit enter afterwards: cp /sdcard/user.conf /system/sd
type and hit enter afterwards: dos2unix /system/sd/user.conf
type and hit enter afterwards: chmod 664 /system/sd/user.conf
type and hit enter afterwards: exit
reboot
see this is my problem..it does not find it in system/sd...it is in system/bin so am i suppsed to copy it back to /system/bin or system/sd
and can someon explain what the difference is between chmod 664 and chmod 755 nd why i should do them
bonkasnucca said:
see this is my problem..it does not find it in system/sd...it is in system/bin so am i suppsed to copy it back to /system/bin or system/sd
and can someon explain what the difference is between chmod 664 and chmod 755 nd why i should do them
Click to expand...
Click to collapse
i think chmod 755 gives it read/write permissions. do not know about 664. try putting it in system/sd with adb then chmod 755 it and see if that works
david1171 said:
i think chmod 755 gives it read/write permissions. do not know about 664. try putting it in system/sd with adb then chmod 755 it and see if that works
Click to expand...
Click to collapse
775 = rwx-rwx-rx. conf file does not need executable in u-g nor x in o groups.
664 = rw-rw-r
if it is in /system/bin do this:
open up terminal
dos2unix /sdcard/user.conf
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/user.conf /system/bin
chmod 664 /system/bin/user.conf
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
reboot
HOW DO I LOAD A CUSTOM LAUNCHER?????CAN SOMEONE HELP ME PLZ
Jerzdre said:
HOW DO I LOAD A CUSTOM LAUNCHER?????CAN SOMEONE HELP ME PLZ
Click to expand...
Click to collapse
You can use adb: (enter after each line) Put Launcher.apk in C: 1st.
adb shell
rwsystem or mount -o rw,remount /dev/block/mtdblock3 /system
exit
adb push C:\Launcher.apk /system/app
or you can use terminal: (enter after each line) Make sure Launcher.apk is on the root of your sd card 1st
su
rwsystem or mount -o rw,remount /dev/block/mtdblock3 /system
rm system/app/Launcher.apk
cp sdcard/Launcher.apk /system/app
exit
exit
Hope this helped.
Exiting out will cause problems. A lot!
Rather than typing exit type reboot instead.
"Hi" all.
I was wondering. If anybody could be so nice and tell if I I can push adb files with. This app... or better can I push files via phone.
Thank you in advanced. .
Sent from my HERO200 using XDA App
Adb commands are completely different than terminal commands.
First enter "su" to get substitute user (the # sign)
Then enter "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system" to make the root r/w
to copy files use "cp" command
to move files use "mv" command
to remove files use "rm" command
to change file/dir permissions use "chmod"
to change directories use "cd" - "cd .." will bring you back one directory - "cd //" brings you back to root
to list files in the dir use "ls"
to read/mod/combine a file use "cat"
to edit a value use "echo"
to see running processes use "top"
to kill a process use "kill -9 PID#HERE"
ex) cp /sdcard/download/myapplication.apk /data/app/myapplication.apk
If you know any linux commands then you should know your way around terminal emulator. If you want i can give you more examples just let me know. Hope this helped
A terminal emlator on the phone works the exact same way at typing "adb shell" into ADB. Kyouko gave you most of the commands you'll need.
hey guys thanks for the support.. but if i want to push a .txt what command would i put in..
Depends where you want to push the text and where it's located.
For example if its located just straight on the sdcard and you want to move it to /system/etc/ you'd enter:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cp /sdcard/nameoffile.txt /whereeveryouwantit/nameoffile.txt
its Exactly the same way as the example i had on my last post
kyouko said:
Depends where you want to push the text and where it's located.
For example if its located just straight on the sdcard and you want to move it to /system/etc/ you'd enter:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
cp /sdcard/nameoffile.txt /whereeveryouwantit/nameoffile.txt
its Exactly the same way as the example i had on my last post
Click to expand...
Click to collapse
Yo.... kyouko thank you so much..
Sent from my HERO200 using XDA App
Hello guys, i know that maybe some people have the same issue, i was able to bypass this using a not very beautiful solution but it works perfect lol.
Check this:
Code:
1. Connect your phone with adb, then type adb shell
2. Type su, to get root access
3. Type stop ric
4. Type busybox pkill -f /sbin/ric
5. Type this "mount -ro remount,rw /" without the quotes to remount / as rw
6. Type this "chmod 0440 /sbin/ric" without the quotes
6. Copy the file build.prop from /system to /
7. Open this file using a root text editor, in my case i used Root Explorer
8. Add this "ro.secure=0" without the quotes below "ro.build.host"
9. Save the changes to the file
10. Type stop ric
11. Type busybox pkill -f /sbin/ric
12. Type "mount -ro remount,rw /system" without the quotes to remount /system as rw, after you do this, please continue to other steps as fast you can.
12. Type busybox cp -af /build.prop /system/build.prop
13. rm /build.prop
14. Done. Now you should be able to mount /system as rw too.
I tested this because i was trying to get ubuntu to run on my system but the bootscript was trying to mount my /system as rw, it was rebooting my tablet but now i've ubuntu perfect and running.
See my attachments
UPDATE: Links to the Full HD images
1. http://cl.ly/image/42210t2X3B1r
2. http://cl.ly/image/2P2S3T1S0k3v
3. http://cl.ly/image/04120x0r1B0B
4. http://cl.ly/image/1f0N310P1O0c
juanyunis said:
Hello guys, i know that maybe some people have the same issue, i was able to bypass this using a not very beautiful solution but it works perfect lol.
Check this:
Code:
1. Connect your phone with adb, then type adb shell
2. Type su, to get root access
3. Type stop ric
4. Type busybox pkill -f /sbin/ric
5. Type this "mount -ro remount,rw /" without the quotes to remount / as rw
6. Type this "chmod 0440 /sbin/ric" without the quotes
6. Copy the file build.prop from /system to /
7. Open this file using a root text editor, in my case i used Root Explorer
8. Add this "ro.secure=0" without the quotes below "ro.build.host"
9. Save the changes to the file
10. Type stop ric
11. Type busybox pkill -f /sbin/ric
12. Type "mount -ro remount,rw /system" without the quotes to remount /system as rw, after you do this, please continue to other steps as fast you can.
12. Type busybox cp -af /build.prop /system/build.prop
13. rm /build.prop
14. Done. Now you should be able to mount /system as rw too.
I tested this because i was trying to get ubuntu to run on my system but the bootscript was trying to mount my /system as rw, it was rebooting my tablet but now i've ubuntu perfect and running.
See my attachments
Click to expand...
Click to collapse
Also i've my bootloader locked, so i believe this could work for both (unlocked and locked).
juanyunis said:
Also i've my bootloader locked, so i believe this could work for both (unlocked and locked).
Click to expand...
Click to collapse
unlocked bootloader users don´t have the reboot problem :silly: o i think sony want´s to stop the people from rooting without having an unlocked bootloader.
mine is unlocked, had no reboot problems on .370 rooted but i´m on cm10.1 now tough i had no probs with stock. i love the stock android interface and top statusbar.
om22 said:
unlocked bootloader users don´t have the reboot problem :silly: o i think sony want´s to stop the people from rooting without having an unlocked bootloader.
mine is unlocked, had no reboot problems on .370 rooted but i´m on cm10.1 now tough i had no probs with stock. i love the stock android interface and top statusbar.
Click to expand...
Click to collapse
That's nice to hear, but it makes sense because with a customer recovery that would be very easy to fix lol.
I do love CM 10.1, but i don't want to loose BE2. In my case i love how it works making my colors more vibrant but well i'm use to AMOLED displays so you can imagine.
I hope to see a way to bypass this or maybe a new stock firmware from Sony with the new status bar.
Thanks for reporting that you don't have this issue!
juanyunis,
Could you please share or write a manual for installation of Ubuntu on Tablet Z?
theZest said:
juanyunis,
Could you please share or write a manual for installation of Ubuntu on Tablet Z?
Click to expand...
Click to collapse
Sure I'll write one tomorrow. It's very easy once you have root with remount system fixed. Have a good day.
Sent from my Samsung Galaxy S4
This fix didn't work for me. To be more precise, it worked until I turned off the tablet. After I started the tablet, remouting caused reboots again. :crying:
---------- Post added at 10:11 PM ---------- Previous post was at 10:07 PM ----------
Oh, just to add,. I verified that the /system/build.prop file was saved correctly. The line is added.
fness said:
This fix didn't work for me. To be more precise, it worked until I turned off the tablet. After I started the tablet, remouting caused reboots again. :crying:
---------- Post added at 10:11 PM ---------- Previous post was at 10:07 PM ----------
Oh, just to add,. I verified that the /system/build.prop file was saved correctly. The line is added.
Click to expand...
Click to collapse
It's a temporal fix lol, but you can use Fisherman ROM with that fixed, i just don't need to use this fix all the time. But once you did this, you can open a terminal on your tablet and run this:
1. su
2. chmod 0444 /sbin/ric
3. stop ric
4. busybox pkill -f /sbin/ric
If you want this to be a permanent solution you can create a sh script with those commands and then user a init.d app like CPD Adjuster to run that script on boot. I'll try to do this for you.
Thanks, now I understand. Stupid of me really. It says temporal in the title.
juanyunis said:
Hello guys, i know that maybe some people have the same issue, i was able to bypass this using a not very beautiful solution but it works perfect lol.
Check this:
Code:
1. Connect your phone with adb, then type adb shell
2. Type su, to get root access
3. Type stop ric
4. Type busybox pkill -f /sbin/ric
5. Type this "mount -ro remount,rw /" without the quotes to remount / as rw
6. Type this "chmod 0440 /sbin/ric" without the quotes
6. Copy the file build.prop from /system to /
7. Open this file using a root text editor, in my case i used Root Explorer
8. Add this "ro.secure=0" without the quotes below "ro.build.host"
9. Save the changes to the file
10. Type stop ric
11. Type busybox pkill -f /sbin/ric
12. Type "mount -ro remount,rw /system" without the quotes to remount /system as rw, after you do this, please continue to other steps as fast you can.
12. Type busybox cp -af /build.prop /system/build.prop
13. rm /build.prop
14. Done. Now you should be able to mount /system as rw too.
I tested this because i was trying to get ubuntu to run on my system but the bootscript was trying to mount my /system as rw, it was rebooting my tablet but now i've ubuntu perfect and running.
See my attachments
UPDATE: Links to the Full HD images
1. http://cl.ly/image/42210t2X3B1r
2. http://cl.ly/image/2P2S3T1S0k3v
3. http://cl.ly/image/04120x0r1B0B
4. http://cl.ly/image/1f0N310P1O0c
Click to expand...
Click to collapse
Hi!
When i edit the build.prop file i have bootloop issue!
So i'm traying the bellow
su
mount -ro remount,rw /
chmod 0440 /sbin/ric
stop ric
busybox pkill -f /sbin/ric
Then you can mount /system as rw from a file explorer (estrong)
The attached file (unzip first) you can use it with ROM toolbox (add as new script) and execute as root and on boot option (if you want a permanent solution)
It's very useful when I deodex my ZULTRA without CWM.
Just to say thanks.
And.....can I use your method in my post?
http://forum.xda-developers.com/showthread.php?t=2468109
Easy Method Linux Install...
There is an app on the play store called "Complete Linux Installer" it works perfectly fine and you can pick from different distros, I tried Ubuntu and Debian. If you can find the full version somewhere for "free" you can customize your screen rez. There is a free version that has some restrictions. You also need androidVNC to mount. This runs on top of android so when you are done with linux you just shut it down to go back to android.
juanyunis said:
Hello guys, i know that maybe some people have the same issue, i was able to bypass this using a not very beautiful solution but it works perfect lol.
Check this:
Code:
1. Connect your phone with adb, then type adb shell
2. Type su, to get root access
3. Type stop ric
4. Type busybox pkill -f /sbin/ric
5. Type this "mount -ro remount,rw /" without the quotes to remount / as rw
6. Type this "chmod 0440 /sbin/ric" without the quotes
6. Copy the file build.prop from /system to /
7. Open this file using a root text editor, in my case i used Root Explorer
8. Add this "ro.secure=0" without the quotes below "ro.build.host"
9. Save the changes to the file
10. Type stop ric
11. Type busybox pkill -f /sbin/ric
12. Type "mount -ro remount,rw /system" without the quotes to remount /system as rw, after you do this, please continue to other steps as fast you can.
12. Type busybox cp -af /build.prop /system/build.prop
13. rm /build.prop
14. Done. Now you should be able to mount /system as rw too.
I tested this because i was trying to get ubuntu to run on my system but the bootscript was trying to mount my /system as rw, it was rebooting my tablet but now i've ubuntu perfect and running.
See my attachments
UPDATE: Links to the Full HD images
1. http://cl.ly/image/42210t2X3B1r
2. http://cl.ly/image/2P2S3T1S0k3v
3. http://cl.ly/image/04120x0r1B0B
4. http://cl.ly/image/1f0N310P1O0c
Click to expand...
Click to collapse
it will be better to execute the commands like this in a row (one single line) as to execute them asap:
mount -o remount,rw /system; mv /build.prop /system/; chmod 644 /system/build.prop; mount -o remount,ro /system
Bootloop!
I followed the instructions on the first page and successfully mounted /system as RW. Then I rebooted (by typing reboot in ADB), and now my tablet is in a bootloop.
I didn't touch anything other than build.prop and media_codecs.xml. What should I do?
Edit: Solved by flashing FTF.
is there any save way to run it on a 16GB wifi only model ? I have root, but my BL is locked.
did try the script form page 1 but this did not work. I am not sure about edeting the build.prop witht the bootloop problems :/
greetings
edit: it would be fine if i can edit the host file from the pc just once, without rw access from the tab itself, i just wanna get rid of those annoying ads everywhere
very usefull on xperia z1 thanks man :good: