I used http://forum.xda-developers.com/showthread.php?t=1136261 to unlock and root my atrix. would like help to unroot it.
Thanks
What you say is to unlock the bootloader and did you root for and want to remove the cel cel the root?
If this is so you must flash the SBF for your version of GB and your phone if AT&T
I believe there is a script called "SuperOneClick" that allows you to unroot it.
The rooting method listed in your link is the preinstall method. To unroot the preinstall method:
from here
1. Open adb
2. Type in the following commands, hitting ENTER after each line of code: (after typing 'su' below, look for the Superuser request and approve it, you can only continue if you get the # prompt.
Code:
su
mount -o rw,remount /dev/block/mmcblk0p12 /system
mount -o rw,remount /dev/block/mmcblk0p17 /preinstall
rm /system/bin/su
rm /preinstall/sqlite3
rm /preinstall/dosu
rm /preinstall/Superuser.apk
rm /preinstall/su
reboot
3. Let the phone reboot fully and then go into Settings > Applications > Manage Applications > find Superuser and uninstall it just like any other app.
Click to expand...
Click to collapse
I unrooted my phone using the above steps back when I did the update to OTA 141. I don't think the superoneclick unroot works for the preinstall root.
I also found and tried that method but for some reason when i type the 2nd line it says mount: mounting /dev/block/mncblk0p17 on /preinstall failed: No such file or directory
PS. I'm not using AT&T
2147483647 said:
I also found and tried that method but for some reason when i type the 2nd line it says mount: mounting /dev/block/mncblk0p17 on /preinstall failed: No such file or directory
PS. I'm not using AT&T
Click to expand...
Click to collapse
are you copy/pasting into adb? It's mmcblk0p17 not mncblk0p17
gnahc79 said:
are you copy/pasting into adb? It's mmcblk0p17 not mncblk0p17
Click to expand...
Click to collapse
i dont copy and paste. But correcting the n to m did nt help
Any help?
2147483647 said:
Any help?
Click to expand...
Click to collapse
you should have both directories, try root explorer or some file manager to make sure you have the following directories:
/dev/block/mmcblk0p17
/preinstall
IMO copy/paste those commands to avoid typos.
gnahc79 said:
you should have both directories, try root explorer or some file manager to make sure you have the following directories:
/dev/block/mmcblk0p17
/preinstall
IMO copy/paste those commands to avoid typos.
Click to expand...
Click to collapse
/preinstall
diectory nt in my root explorer.
2147483647 said:
/preinstall
diectory nt in my root explorer.
Click to expand...
Click to collapse
You should have that directory, it could be you manually removed the entire preinstall directory at some point. I'm not sure what impact that has if for future OTA updates (might soft brick).
in adb issue the following command and you should be unrooted.
rm /system/bin/su
then uninstall the superuser app.
Related
going through the entire 1.5 to 2.1 root tutorial to a tee, but once i get to the recovery image, this happens (following is an entire copy/paste of what I went through, incase i did something wrong before i hit the point)
Code:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Lemcott>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb shell mount -o rw,remount /dev/block/mtdblock3
/system
adb server is out of date. killing...
* daemon started successfully *
C:\android-sdk-windows\tools>adb shell mount -o rw,remount /dev/block/mtdblock3
/system
C:\android-sdk-windows\tools>adb push recovery.img /sdcard
1192 KB/s (3926016 bytes in 3.215s)
C:\android-sdk-windows\tools>adb push flash_image /system/bin/flash_image
448 KB/s (9640 bytes in 0.021s)
C:\android-sdk-windows\tools>adb shell flash_image recovery /sdcard/recovery.img
flash_image: permission denied
C:\android-sdk-windows\tools>
EDIT: I am a complete ass hat. nothing to see here, move a long. mods delete this if you please.
P.S. Everyone else: ALWAYS DOUBLE CHECK BEFORE POSTING FOR HELP. *ahem* now be on your way.
try programming thru fastboot. press call + vol down and select the fastboot option and use this command from the pc
fastboot flash recovery recovery.ing
Sent from my Evil Eris v1.1 using the XDA mobile application powered by Tapatalk
It looks like you forgot the step where you modify the flash_image's permissions
Code:
adb shell chmod 755 /system/bin/flash_image
I had the same thing but I just kept reentering
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
and after maybe 4 iterations it worked.
I have a very simular problem:
(moto droid with android 2.1)
$su
su
Permission denied
Click to expand...
Click to collapse
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
>adb shell chmod 755 /system
unable to chmod /system: Read-only file system
>
Click to expand...
Click to collapse
penthoy said:
I have a very simular problem:
(moto droid with android 2.1)
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
Click to expand...
Click to collapse
make it read/write
penthoy said:
I have a very simular problem:
(moto droid with android 2.1)
I have try to use chmod the file but it said permission denied on chmod... please help T_T
note this is rooted, of course, when i'm in the phone type su, it'll pop up ask for me to allow or not, allowed, everything seems fine, but when i try to modify files in /system/etc/wifi (trying to make it work for ad hoc) it said permission denied....(even in su???) I tried in adb and it's the same, very very frustrating, any help is appreciated, Thanks.
edit: here's what it looks like using chmod...
Click to expand...
Click to collapse
I wouldn't try to flash anything you find here to a Moto Droid.
This is for the HTC Droid Eris.
Otherwise, and if I'm misunderstanding you, good luck with your problem.
archmagus said:
It looks like you forgot the step where you modify the flash_image's permissions
Code:
adb shell chmod 755 /system/bin/flash_image
Click to expand...
Click to collapse
I've been bashing my head in ALL day trying to get past this and finally found this thread! This worked perfectly!
theboo7 said:
make it read/write
Click to expand...
Click to collapse
How should i make is read/write?????
i cant get it to work at all.. need help plz.
Hello Guys
why cant i mount that **** together, i have the root permission, but also i dont..somehow
Code:
Microsoft Windows [version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle rettigheder forbeholdes.
C:\Users\Rasmus H. G. Johnsen>d:
D:\>cd android\tools
D:\android\tools>adb devices
List of devices attached
HT9B7LG00092 device
D:\android\tools>adb shell mount -o rw,remount /dev/block/mtdbloc3 /system
mount: Operation not permitted
D:\android\tools>adb shell
$ ls
ls
sqlite_stmt_journals
cache
sdcard
etc
system
sys
sbin
proc
logo.rle
init.rc
init.goldfish.rc
init.bahamas.rc
init
default.prop
data
root
dev
$ exit
exit
Also if I go on and try to do this:
Code:
D:\android\tools>adb push flash_image /system/bin
failed to copy 'flash_image' to '/system/bin/flash_image': Read-only file system
I know that the flash_image fil and my recovery.img file is in this library and also on my sdcard, but I cant push the gotdamn flas_image file in the /system/bin catalog.
Can some one please help me ?
PS. I have the USB-debugging turned ON.
How do you know that you have root? Or, how did you gain root?
doogald said:
How do you know that you have root? Or, how did you gain root?
Click to expand...
Click to collapse
I have the app called androot from google market, ang i have run it to get root.
wfdi said:
I have the app called androot from google market, ang i have run it to get root.
Click to expand...
Click to collapse
I'm not aware of that app, and cannot find it in the market myself (do you have a link?)
However, one way to check for sure if you truly have root is run the adb command adb shell and, when you get a prompt, type the command "su". If it returns with a "#" prompt (rather than the "$" prompt that you are seeing), then you have root on the phone.
Most people these days root with either jcase's 1click root for eris: https://market.android.com/details?id=net.andirc.erisrooter or they use the procedure here: http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies.html
You may be able to use the steps here as well, since you seem pretty comfortable with adb and have that working already: http://androidforums.com/eris-all-things-root/125436-detailed-leak-root-tutorial.html
Guys new I found another solution (tested on u8150)
First make sure that you are rooted first.
Open adb shell
Type in su.
Remount the system partition as read write.
Change the owner of system from root to system via chown root system
the exit the shell and push flash_image to system/
also push clockworkmodrecover.img into the system partion dont forget the last /.
then exit.
use a file manager, I used rootbrowser.apk without a memory card and installed recovery.
with rootbrowser copy flash_image to the bin directory.
don't forget to change the owner back to root to the system partition after you finish with rootexplorer or whatever u use even adb can work.
then the rest follows.
The above works only if your'e rooted and have adb.
Goodluck
haha am a genius Installing ROM +Recover without sdcard on u8150
all you have to do is:-
1. Make sure u have installed clockwork mode recovery on your device and have su binary.
2. Open adb with the device normally on.
3. Remount the data partition as read write using mount remount in adb .
4. use adb and push the cynogenmode.zip or any rom that fits into the data partition using
adb push romname.zip /data/
5. Reboot into clockworkmod recovery using the various options available.
6. This is what to do if you don't have a sdcard.
open adb with phone connected and run
adb shell
mount /data /sdcard
then go back to the main recovery menu and wipe dalvik cache only
then choose update from sdcard
flash your rom and tadaaa.
your'e done.
NB:CAUTION MAKE SURE TO FLASH A ROM THAT DOES NOT WRITE INTO THE DATA PARTION
THIS CAN BE DONE BY LOOKING FOR A FILE CALL UPDATE SCRIPT IN THE zip OF THE ROM U WANT TO INSTALL
Am going to make a post about this later.
Goodluck
Lol, 3 and a half year break between responses.
The problem with flash_image & dump_image is that it doesn't work on devices devices which use emmc (recent phones)and have
mmcblk0
and cat /proc/mtd won't work here either.
This means that you have to use dd to write to this devices.
I wonder how guys determine the partitions to use on such devices, and someone should hint as to what is going on since it seems manufacturers seriously don't want people to exploit their devices.
hey guys,
ive just started to learn how to modify apks and use adb.
my problem is that after i pull the file, i modify the icon i want to change, re-sign it and push it back to the phone. after i reinstall, the icons have not changed :S i re-pulled it, and the icons in the drawable_hdpi file are the one i wanted.
also, completely unrelated to that.... in adb when i try to run adb remount, it says permission denied, but im rooted and i even tried running the shell root beforehand aswell.
i ran a search and followed the various instructions from the different threads and forums but im just stuck at that point
thanks guys
kylec said:
also, completely unrelated to that.... in adb when i try to run adb remount, it says permission denied, but im rooted and i even tried running the shell root beforehand aswell.
Click to expand...
Click to collapse
If you're getting permission denied how have you pushed it back?
XperiaX10iUser said:
If you're getting permission denied how have you pushed it back?
Click to expand...
Click to collapse
i push it to the sdcard lol because it wont let me push to the system/app folder nor the data/app folder. i check my screen and a pop up appears saying that superuser granted access, so i have that.
kylec said:
i push it to the sdcard lol because it wont let me push to the system/app folder nor the data/app folder.
Click to expand...
Click to collapse
Then it's no wonder your icons haven't changed if you haven't installed it to the phone.
Try, but keep your phones screen on whilst you try it...
adb shell (enter)
su (enter)
...allow super user access on phone...
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
XperiaX10iUser said:
Then it's no wonder your icons haven't changed if you haven't installed it to the phone.
Try, but keep your phones screen on whilst you try it...
adb shell (enter)
su (enter)
...allow super user access on phone...
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Click to expand...
Click to collapse
ok i just tried that. when i typed su, it echoed and on my phone it said "unknown has been grandted superuser permissions" so i didnt need to click allow or anything.
then i typed the mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system and got mount: operation not permitted
any ideas?
kylec said:
any ideas?
Click to expand...
Click to collapse
Try...
cd C:\android-sdk-windows\tools
adb shell
su
chmod 4755 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
...and report back.
XperiaX10iUser said:
Try...
cd C:\android-sdk-windows\tools
adb shell
su
chmod 4755 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
...and report back.
Click to expand...
Click to collapse
yup that worked, i got an echo without errors
EDIT: ok after that i then tried to push the apk to the system/app and also the data/app folders, but i got a different error this time.
it said failed to copy .apk permission denied
kylec said:
it said failed to copy .apk permission denied
Click to expand...
Click to collapse
Try, in a terminal on the phone...
su
chmod 4755 /system/bin/sh
I always struggle trying to get permissions after I've first rooted but can never remember the exact sequence, but do know it's a combination of what I've suggested.
XperiaX10iUser said:
Try, in a terminal on the phone...
su
chmod 4755 /system/bin/sh
I always struggle trying to get permissions after I've first rooted but can never remember the exact sequence, but do know it's a combination of what I've suggested.
Click to expand...
Click to collapse
ill give it a try after uni lol. thanks for all the help mate, its awesome having a place to get advice and help
EDIT: finally got it working... i pushed the file to sdcard then used the terminal emulator and used:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
cd sdcard
cat x.apk /data/app/x.apk
and that worked perfectly lol
I am trying to root an elocity A7 and I pretty new at this. I installed root explorer but the mount r/w button does not work in the system folder. I tried the terminal command below but it does not seem to accept the command. I get back a message that says shows Usage: mount [-r] [-w] [-o options [-t type] device directory. I retried root explorer and still can't write. Thanks for any help.
- open Terminal emulator:
$ su
# mount -o remount,rw /system
- open Root Explorer \system folder and press r/w
adb remount
or search the market for "mount system"
I'm not following how to use adb remount. What would be the complete command line? Also, I can't get to the market which is why I am trying this. I read it on another thread here.
i cant find mount r/w button
download this program from the market "Mount /system (rw / ro)"
I can't get to the market on this device. Any other way of getting it?
Try the attached zip
Thank you! That worked.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Thanks For the App Recomendation
joenathane said:
download this program from the market "Mount /system (rw / ro)"
Click to expand...
Click to collapse
This was kicken my @$$ - thanks for the help and recommendation
zte with magisk
joenathane said:
Try the attached zip
Click to expand...
Click to collapse
my rom is stock but got a version that used zpst to force magisk to allow root, root is good but cant move 1 app to system without read only i tried this it says it worked but when i try to move it says i dont have permission .. guessing there isnt a recovery for this model the z835
I thought I'd bricked my NT but it would appear that it is actually alive because it turns up with adb and I can get shell and then issue command su, but what I can't do is replace the old build.prop because file system is not writable. How do I remount it to be writeable from a shell please?
Thanks!
CelticWebSolutions said:
I thought I'd bricked my NT but it would appear that it is actually alive because it turns up with adb and I can get shell and then issue command su, but what I can't do is replace the old build.prop because file system is not writable. How do I remount it to be writeable from a shell please?
Thanks!
Click to expand...
Click to collapse
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify rw, make your changes
mount -o ro,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify ro
Thank you!
hwong96 said:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p8 /system
Type mount to verify rw, make your changes .....
Click to expand...
Click to collapse
I don't have this tablet but a phone with similar problem.
this does not work for me, although I have ROOTED phone MTK6572, android 4.2.2 ;
"/ root" gets RW, but "/system" stays RO.
I get this message:
error
"the item "system" is read only"
I have tried many apps in phone (remount system RW, FX file expl. ....), and mtkdroid-tools and ADB shell in PC.
I have tried many similar version of that command, too, inc. busybox remount. non of those work.
any ideas, what to try next?
what file or thing or item and where I need to change to get this remounting system to RW done?
it is ext4, and remountable.
I have SuperSU in phone but can't update its binaries: /system stays RO, what ever I try...
I can't change audios, anything in /system.
very annoying...
Jack_Rover said:
I don't have this tablet but a phone with similar problem.
this does not work for me, although I have ROOTED phone MTK6572, android 4.2.2 ;
"/ root" gets RW, but "/system" stays RO.
I get this message:
error
"the item "system" is read only"
I have tried many apps in phone (remount system RW, FX file expl. ....), and mtkdroid-tools and ADB shell in PC.
I have tried many similar version of that command, too, inc. busybox remount. non of those work.
any ideas, what to try next?
what file or thing or item and where I need to change to get this remounting system to RW done?
it is ext4, and remountable.
I have SuperSU in phone but can't update its binaries: /system stays RO, what ever I try...
I can't change audios, anything in /system.
very annoying...
Click to expand...
Click to collapse
I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. Anyway, since you have asked I'll answer. The mount point for /system is different on each phone model. There is no one standard /system mount point. On the Nook Tablet and Nook Color it is mmcblk0p8. On your device it is different, so the command you tried will not work.
You need to find out what the /system mount point is for your phone.
Open terminal from phone and type su.
Press enter.
At the # prompt type cat /proc/mtd
Press enter.
Look at the output on the screen and see what the mount point is for /system.
A the the # prompt type mount -o rw,remount -t ext4 /dev/block/enteryoursystemmountpointhere /system
Note: replace enteryourmountpointhere with your mount point from the previous step.
Change /system to ro when done. Hope this works for you.
Also download root checker app to ensure you rooted properly.
hwong96 said:
I understand your frustration, however, you should try to post your question to the MTK6572 or Samsung S4 thread. ......
Click to expand...
Click to collapse
thanks for your responce.
with that "cat ..." I got : "no such file or dir"...
I know already that my mnt point is (did try already these earlier):
mount -o rw,remount /dev/block/mmcblk0p4 system
mount -o remount,rw -t ext4 /[email protected] /system
but no success, " system read only" stays, and no change.
Jack_Rover said:
thanks for your responce.
with that "cat ..." I got : "no such file or dir"...
I know already that my mnt point is (did try already these earlier):
mount -o rw,remount /dev/block/mmcblk0p4 system
mount -o remount,rw -t ext4 /[email protected] /system
but no success, " system read only" stays, and no change.
Click to expand...
Click to collapse
Did you use the root checker app to verify for proper root?
hwong96 said:
Did you use the root checker app to verify for proper root?
Click to expand...
Click to collapse
yes.
I have many apps (e.g. FX, ATools, TitaniumBup, busybox, ES, mount /system rw, SD maid, root expl., adbd insec., rootAppDel, a.s.o.) that use root rights, and phone's superSU gives the rights to them.
AT:s terminal has # prompt, so it must be root. (?)
adbd insecure's current status = binary: insecure; usb debugging: enabled.
I have earlier version SU's binaries working ok, but updating SU made this binary-update-issue: " binary update failure" and so SU-app won't open (it closes after failing binary update), though otherwise it works ok (and worked earlier until I did let G-play to update it, silly me!).
somehow my /system has been "open" i.e. RW earlier, since busybox and superSU has been installed, but now it is "stuck" to that RO-status. "/" opens, but "/system" not.
MTK Droid Root & Tools v2.5.3 (from here xdadevs) gets root shell ok, but fails when trying to install SU, busybox a.s.o. ("read-only system") - and it "crashes".
maybe kernel related? or boot loader, or .... what?
-----
btw, my apologises, that I wrote this issue to this thread, but I found my "problem" here with the search, and after posting I realized that this is "tablet area..."
so this part can be moved to better place by those who know best where to - though not to trash, anyway....
Jack_Rover said:
yes.
I have many apps (e.g. FX, ATools, TitaniumBup, busybox, ES, mount /system rw, SD maid, root expl., adbd insec., rootAppDel, a.s.o.) that use root rights, and phone's superSU gives the rights to them.
AT:s terminal has # prompt, so it must be root. (?)
adbd insecure's current status = binary: insecure; usb debugging: enabled.
I have earlier version SU's binaries working ok, but updating SU made this binary-update-issue: " binary update failure" and so SU-app won't open (it closes after failing binary update), though otherwise it works ok (and worked earlier until I did let G-play to update it, silly me!).
somehow my /system has been "open" i.e. RW earlier, since busybox and superSU has been installed, but now it is "stuck" to that RO-status. "/" opens, but "/system" not.
MTK Droid Root & Tools v2.5.3 (from here xdadevs) gets root shell ok, but fails when trying to install SU, busybox a.s.o. ("read-only system") - and it "crashes".
maybe kernel related? or boot loader, or .... what?
-----
btw, my apologises, that I wrote this issue to this thread, but I found my "problem" here with the search, and after posting I realized that this is "tablet area..."
so this part can be moved to better place by those who know best where to - though not to trash, anyway....
Click to expand...
Click to collapse
Don't know what else to suggest, except maybe contact Chainfire on G+.
.
Hi, does anyone know how to delete a file on root with terminal, as rm -r returns screenshotted error.
kriki200 said:
Hi, does anyone know how to delete a file on root with terminal, as rm -r returns screenshotted error.
Click to expand...
Click to collapse
Did you execute this command as root ? If not enter "su" then enter your command. (Make sure you hit "Allow" when the prompt for you to allow root accès to the shell appears)
And maybe it sounds stupid but try chmod commands if your command doesn't work.
I'm not an expert with android terminal so if the problem is persistent you can try this with a root explorer.
Hope all of this helped
Have a good day
kriki200 said:
Hi, does anyone know how to delete a file on root with terminal, as rm -r returns screenshotted error.
Click to expand...
Click to collapse
The partitition you want to deal with must be mounted as READ-WRITE before.
Raiz said:
Did you execute this command as root ? If not enter "su" then enter your command. (Make sure you hit "Allow" when the prompt for you to allow root accès to the shell appears)
And maybe it sounds stupid but try chmod commands if your command doesn't work.
I'm not an expert with android terminal so if the problem is persistent you can try this with a root explorer.
Hope all of this helped
Have a good day
Click to expand...
Click to collapse
I did, kinda don't want to change permissions... same.
jwoegerbauer said:
The partitition you want to deal with must be mounted as READ-WRITE before.
Click to expand...
Click to collapse
How do I do and undo that, will it change any file permissions?
Example:
Code:
su
cd /
mount -o rw,remount -t auto /system
jwoegerbauer said:
Example:
Click to expand...
Click to collapse
Thank you, it worked, do you know how to undo it, the below command deosn't seem to work and do you know what the "auto" is for in the command?
Code:
mount -o ro,remount -t auto /system