well one my friend have problem with his HTC Tattoo while he was trying to delete a font from font folder he accidentally deleted the FONT FOLDER now his phone is not working...
is there anyway to fix this problem ?
I suppose that usb connection works, so he can push them to device via adb.
Here is the fonts folder.
Or he can use Android commander: http://forum.xda-developers.com/showthread.php?t=628138 to push them in system with an easier way.
can u pls explain how i can do it via ADB ?
Sorry, I'm not a linux expert and I don't know exactly which commands you must give. For this I suggested Android commander, cause you can drag & drop the folder to device's system folder like you do in windows file explorer.
You can also push the folder along with files with the Android SDK... It's easier as it is GUI based...
rre_za said:
can u pls explain how i can do it via ADB ?
Click to expand...
Click to collapse
1. Unpack the zip file into a folder
2. Connect Tattoo via USB, start recovery, open a terminal and type adb start-server
3. cd into the fontfolder: cd fontfolder
3. PATH\TO\adb push . /system/fonts (please note the DOT!!!! sign)
You're done.
What prob with my tattoo?
I used root1click tool
And I installed Enable Market >>>>> My phone's rooted
but when I try to push font in /system/fonts
ADB say : Permission Denied
Please Help
You need to remount the filesystem with the read-write permission.
Before typing "PATH\TO\adb push . /system/fonts" you need to execute "PATH\TO\adb remount"
I tried
adb remount
adb say:
remount failed: operation not permitted
what prob?
If you type
adb shell
Do you see a # or a $ ? (if you see a $ something has gone wrong with the root)
I believe you cannot remount via adb with stock (didn't try)...install Root Explorer and then try to remount from phone side (there is a button on the upper side saying: Mount RW)
Else do it manually and open adb shell and type:
1. su
2. insmod /data/local/bin/tattoo-hack.ko
3. mount -o rw,remount /dev/block/mtdblock5 /data
4. mount -o rw,remount /dev/block/mtdblock3 /system
I have searched but haven't been able to find a solution to my problem.
I am on the latest CM9 nightly and I have installed ADB on my Windows 7 64bit computer and it seems to be working but when I try and use the 'push' command, I get this "C:\android-sdk-windows\platform-tools>adb push Trebuchet.apk /system/app
failed to copy 'Trebuchet.apk' to '/system/app/Trebuchet.apk' : Read-only file system"
I have tried the 'Remount' command, but that just throws back "Remount failed: Operation not permitted"
Any help is much appreciated.
You need to change permissions on the system folder
C:\android-sdk-windows\platform-tools>adb remount
then
C:\android-sdk-windows\platform-tools>adb push Trebuchet.apk /system/app
Didn't see that you had tried this !!
if you have root explorer or such navigate to system directory and change permissions to r/w...
otherwise...
adb shell
su
#mount -o rw,remount /dev/block/mtdblock3
Thank you for the help, however it still isn't working. I used the commands;
adb shell
su
#mount -o rw,remount /dev/block/mtdblock3
and it didn't throw me an error, but then when I tried to push the Trebuchet.apk it says the say as before. "failed to copy 'Trebuchet.apk' to '/system/app/Trebuchet.apk' : Read-only file system" "
Try
adb root
It could also be your version of busybox...
running out of ideas but one more...
Actually try this reboot into recovery (I presume you have some type installed), if you have an option to 'mount system' select it and then push the file...
Sent using my fingers and some technology from my HD2
Thank for your help! In the end it was my bad.
I didn't realise that on CM9 nightlies you have to go to Settings > Developer Options > Root Access > Apps and ADB.
Bling
Firstly what i would like to say is this is not a one click root like update.zip or superoneclick you will need to have some basic knowledge of adb and ubuntu and a little bit working mind which can follow the provided steps.
Requirements:-
*cwm recovery already flashed (if not refer here)
* Working linux distro (ubuntu, mint, kubuntu etc.) with atleast sudo rights
* adb setted-up (if not refer here, may not need to follow the usb drivers steps)
* must know how to use adb
* superuser package from here
Click to expand...
Click to collapse
So we are now ready to start
STEPS:-
1. Extract all file (su, busybox) from the downloaded package to the folder where you have adb setted-up
2. open a terminal
3. cd to the directory where you have placed adb and files
4. boot your phone into cwm recovery mode (home power) connect through usb
5. type "sudo chown root:shell /path to su"
6. type "sudo chmod 06755 /path to su"
7. type " sudo chmod 04755 /path to busybox"
8. type " adb devices" if you will see anything attached you are good to go
9. type " adb remount" if you get remount succedd then you can do below steps if not you are doing something wrong do again
10. type "adb push su /system/xbin"
11. type "adb push busybox /system/xbin
12. type adb push supersu.apk ( or what it is called) /system/app
13. now type "adb shell"
14. type su if accepted then you are rooted
15. now type "reboot"
Click to expand...
Click to collapse
you are successfully rooted
enjoy your phone
awesome guide buddy very useful for n0obs
First of all great guide! But please correct these:
You have to mount the system partition manually. Adb remount won't do it!
adb shell
# mount -rw -t rfs /dev/block/stl12 /system
Do chmod/chown in adb. It isn't enough to set it before copying.
# chown root:shell /system/xbin/*
# chmod 06755 /system/xbin/su
# chmod 04755 /system/xbin/busybox
# chmod 04755 /system/xbin/sqlite3
# chmod 04755 /system/xbin/ssh
if we were able to chmod with adb there was no need to use ubuntu
we cannot chmod it shows operation not permitted as as we yet dont have root
have you tried to do adb remount or just saying that i will not do the work
and thanks for chown part
dheeraj (dhlalit11) said:
if we were able to chmod with adb there was no need to use ubuntu
we cannot chmod it shows operation not permitted as as we yet dont have root
have you tried to do adb remount or just saying that i will not do the work
Click to expand...
Click to collapse
Hi!
For me, adb remount didn't work. It exited with an error code. I don't remember the exact error code... (cwm couldn't mount too)
When I experienced "operation not permitted" while chmoding, the partition was mounted as vfat! Because if you do "mount /dev/... /system" without switches, it automatically mounts it as vfat. In vfat you can't set setuid, setgid permissions.
I think it was just a coincidence that i could rooted with ubuntu. But it worked, so better to use linux (better adb perhaps?).
Rooting is a bit strange in this new firmware. For example when you do "adb shell" while the phone is in cwm, you have root access. So you have to do those things manually while you have temporary root access.
how can you mount rfs file system as vfat i dont think it can be done
dheeraj (dhlalit11) said:
how can you mount rfs file system as vfat i dont think it can be done
Click to expand...
Click to collapse
Yes it's really strange. I don't know how this thing possible too...
But I checked multiple times with "cat /proc/mounts" , and mounting without "-t rfs" it was mounted as vfat.
a bit of googling:
"You can mount as rfs as Fat in ubuntu and read/copy the files
editing them wont work at all ."
So maybe it is possible.
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:
Is it still possible to root my original droid (running 2.2.3)? Baseband version C_.1.43.1P , kernel 2.6.32.9
I checked many threads but most of the download links of apk or other app are dead.
I really need to root this phone, if somebody has instructions and files, I would really appreciate it.
So I found this working root method from some other forum, sharing in case anyone needs it, I doubt it though
Go to settings on your phone
then applications
then development
check the box for usb debugging[/Hide]
2.) Extract rageagainstthecage.zip to c:\droidroot
3.) Connect your phone to the computer via usb cable
4.) on the computer open the command prompt. (In the start menu under accessories)
5.) cd to your adb tools directory. For most the command would look like this cd C:\android-sdk-windows\tools
6.) adb devices (This should list a device as a long number under list of devices. If it doesnt something is wrong.)
7.) adb push c:\droidroot\rageagainstthecage-arm5.bin /data/local/tmp
8.) adb shell
9.) cd /data/local/tmp
10.) chmod 0755 rageagainstthecage-arm5.bin
11.) ./rageagainstthecage-arm5.bin (This can take a minutes just let it go until you are returned to your adb tools folder)
12.) adb devices
13.) adb shell (you should now see a # instead of a $)
14.) mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
15.) exit
16.) adb push c:\droidroot\Superuser.apk /system/app
17.) adb push c:\droidroot\su /system/bin
18.) adb push c:\droidroot\busybox /system/bin
19.) adb shell
20.) chmod 4755 /system/bin/su
21.) chmod 4755 /system/bin/busybox
22.) mv /system/recovery-from-boot.p /system/recovery-from-boot.p.disabled Note if you are on a build earlier than froyo this step will fail. That is fine and expected.
23.) mount -o ro,remount -t yaffs2 /dev/block/mtdblock4 /system
24.) rm /data/local/tmp/rageagainstthecage-arm5.bin
25.) exit