Related
this is in regards to http://forum.xda-developers.com/showthread.php?t=754020
I'm ready to kick myself, it worked for everyone else, but here is what i get:
C:\and_sdk\tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i have tried - remount command and it didn't do a thing.
please help!
dialbat said:
this is in regards to http://forum.xda-developers.com/showthread.php?t=754020
I'm ready to kick myself, it worked for everyone else, but here is what i get:
C:\and_sdk\tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i have tried - remount command and it didn't do a thing.
please help!
Click to expand...
Click to collapse
You're in recovery mode right? I rooted before the tmobile update so I used the original method not the one you're using. I assume that for the most part you need to have your phone in recovery mode.
The /system/ directory is read only unless you're in recovery and I believe that's were that method attempts to write. You usually only get that message when you attempt to write to the system when not in recovery.
Thank you, but there is not a single word about puting phone into recovery mode in the instructions. Unless they mean it my default
i will try though.
Yeah, some steps are left out in certain 'common' tasks like rooting. It's assumed to be common knowledge or that if you don't know to automatically do a step then maybe you shouldn't be attempting it. At least that's the feeling I get sometimes but that's why it's important to search and ask if you don't find the answer.
Recovery mode is not necessary, nor possible at this point. The phone just needs to be on and connected with adb. No steps are left out (I've used this method), you just need to make sure you follow every step exactly.
Sent from my T-Mobile myTouch 3G Slide using XDA App
If it's under/system, you need to be in recovery. I rooted with the original method though, so I can't really tell you much.
guitarist5122 said:
Recovery mode is not necessary, nor possible at this point. The phone just needs to be on and connected with adb. No steps are left out (I've used this method), you just need to make sure you follow every step exactly.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You're kidding about recovery mode right? I really hope so or that you stated that wrong... wow...
In order to write to ./system on the mytouch 3g slide you HAVE to be in recovery. Not saying this method has to be in recovery or not because I never used it. Just thought I'd throw out the suggestion to try it just in case it needs to be.
Well, i've followed steps to the point. I have rooted my phone before, so even though i am a newbe, i do have a general idea of the process.
But i have no idea why it just won't work for me.
I have tried putting it into recovery using loop script, otherwise it just states that it's in recovery and still won't let me write to it
KCRic said:
You're kidding about recovery mode right? I really hope so or that you stated that wrong... wow...
In order to write to ./system on the mytouch 3g slide you HAVE to be in recovery. Not saying this method has to be in recovery or not because I never used it. Just thought I'd throw out the suggestion to try it just in case it needs to be.
Click to expand...
Click to collapse
Why would I be kidding? It isn't necessary to be in recovery to push files to /system. I know since I've rooted my phone twice from a fully booted state (which is necessary to toggle the wifi).
Sent from my T-Mobile myTouch 3G Slide using XDA App
guitarist5122 said:
Why would I be kidding? It isn't necessary to be in recovery to push files to /system. I know since I've rooted my phone twice from a fully booted state (which is necessary to toggle the wifi).
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Hmm... Allow me to copy and paste a few lines from that thread, written by the developer:
1:After many long hours of trying to restore my phone, I have now ported the exploid exploit to the MyTouch Slide! This means that you can gain root on any version of the Slide, INCLUDING the latest OTA! However, this isn't necessarily "easy" as in the One-Click Root program, but there are reasons for this. While Android is running we cannot write to /system and even if we force Linux to let us, the NAND protection will prevent Linux from completing the write!
2:Important: If you do nothing after step 12 then you are not "rooted." This program grants itself root permissions in a shell, that is ALL. If you want system-wide root access (what most people consider "rooted"), you MUST flash a custom ROM since the NAND protection on our device prevents us from giving global root access while inside the ROM. When following Eugene's instructions on flashing ENG, make note to NOT run the command 'su' if you already have a pound symbol (#) at your command prompt!
Basically, this 'root' method is actually a program that allows you to flash the ENG package to give you root. By itself, the program does nothing but allow you to operate inside the shell as root for a short time. Sort of like the 'sudo' command in linux - at least from what I can tell.
I'm aware of what the developer said. I'm also aware that I disregarded not having the phone booted since it would be a little tough to toggle wifi without being booted. If you don't believe it can be done, do a nandroid backup and unroot your phone and try rerooting. Pushing exploid and do the root whole process before flashing the eng-build while booted. Or just take my word. Personally I figure out for the life of me how anyone toggles the wifi (which is one of the steps) if not fully booted.
I don't argue just to be right. I just don't want people to be given incorrect info and never solve their problem. Rooting and can be frustrating on this phone if your not too familiar with rooting or using command prompt.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I wan't saying the files can't be pushed while it's on, I've done that before but NAND will undo or not complete it once you reboot. It's the same reason that you can't delete a system app while the slide is booted - well you can but it will still be there, and once you reboot the delete is undone - unless you're in recovery.
All I was saying is that it's not a permanent write to the system, if that's where it's even being pushed and he still has to flash the ENG build to gain full root. I think this guy needs to just redo the steps, maybe read the old root methods to gain some insight too. It might help.
btw, I think there actually is a command to toggle wifi through adb, not sure if it does much in recovery or not. Also, not a chance in hell am I going to unroot - it was a pain in the a** catching my phone in recovery even when I used the loop.bat file
Good to know that's why my apps didn't stay deleted.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I came across this thread while trying to understand why my rooted phone won't let me pull or rm from a terminal emulator. The way I rooted my phone was by flashing an update in recovery. Does anyone know of a file that would unroot by using the same method in recovery?
Thainfamous20v said:
I came across this thread while trying to understand why my rooted phone won't let me pull or rm from a terminal emulator. The way I rooted my phone was by flashing an update in recovery. Does anyone know of a file that would unroot by using the same method in recovery?
Click to expand...
Click to collapse
rm, rm -f or any other commmands will not work with terminal emulator because in order to use that program you phone has to be on, and since we can only write to the /system in recovery I'm sure you see what I'm getting at. You can still pull from the /system when the phone is on. The command isn't 'pull' though, it's:
Code:
cp <path to file> <location to copy to>
As far as the unroot thing, use the search bar [slide rom bible].
just found this thread while looking for a solution to the OP's problem (same as my own).
If my phone is ON, usb debugging ON, Charge Only, i cannot push exploid to /sqlite_stmt_journals.
this is what i did:
C:\android-sdk-windows\platform-tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i tried to follow the directions as closely as possible. can someone please tell me where i'm going wrong here?
PunkRockJesus said:
just found this thread while looking for a solution to the OP's problem (same as my own).
If my phone is ON, usb debugging ON, Charge Only, i cannot push exploid to /sqlite_stmt_journals.
this is what i did:
C:\android-sdk-windows\platform-tools>adb push exploid /sqlite_stmt_journals
failed to copy 'exploid' to '/sqlite_stmt_journals': Read-only file system
i tried to follow the directions as closely as possible. can someone please tell me where i'm going wrong here?
Click to expand...
Click to collapse
Its been so long since i used that method and rooted i cant quite recall. But it does look like you need to change the path to c:/android-sdk-windows/platform-tools
Command prompt is picky about using / or \
Sent from my T-Mobile myTouch 3G Slide using XDA App
guitarist5122 said:
Its been so long since i used that method and rooted i cant quite recall. But it does look like you need to change the path to c:/android-sdk-windows/platform-tools
Command prompt is picky about using / or \
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
No, windows uses \ for local and local network file paths, it only uses / for remote locations and networks.
I'm not sure if this would work without already having root (I received my phone already rooted, never had to do it)
In command prompt, try
adb remount
You can also try this:
adb shell mount -o rw,remount /sqlite_stmt_journals
See if any of those work. Like I said, it may not, since those might be things that need root.
Any updates on this? I cannot push the file either. And "adb shell mount -o rw,remount /sqlite_stmt_journals" does nothing.
Im trying to root the mytouch slide 3g. Ive tried several tutorials with no luck. The tutorial below Is the most current im trying and i keep getting stuck where it says to type in chmod 0755 exploid. I keep getting the error no such file or directory any clue what im doing wrong? Do I have something setup incorrectly for the sdk? Any help is highly appreciated. Thanks
http://richard.gluga.com/2010/08/co...eL0aDS15jzy-h53sdvixwwnM#c2020298098253482744
davethedrummer84 said:
Im trying to root the mytouch slide 3g. Ive tried several tutorials with no luck. The tutorial below Is the most current im trying and i keep getting stuck where it says to type in chmod 0755 exploid. I keep getting the error no such file or directory any clue what im doing wrong? Do I have something setup incorrectly for the sdk? Any help is highly appreciated. Thanks
http://richard.gluga.com/2010/08/co...eL0aDS15jzy-h53sdvixwwnM#c2020298098253482744
Click to expand...
Click to collapse
Are the other commands successful? Like when you did adb push exploid, did it succeed? and you did CD to the directory it told you to?
[Q] Help me root my OTA upgraded G2 Visionary R14 Don't Work "Visionary R7 needed"
HELP...HELP....HELP.....PLEASE HELP
I have the T-mobile G2 and I did an over the air upgrade in December of 2010, ever since then the only version of VISIONARY that work on my phone was "Visionary R7" I have search all over the web trying to find the "Visionary R7" so far I have yet to find it...that is why I am posting on this forum......By the way I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA upgraded T-mobile G2....
So if anyone know where I can download "Visionary R7" please let me know...
Or
If someone know of a way to either Temporary or permanently root the G2 without Visionary please let me know as well
Thanks so much for your kind help......
Is temp root working?
Sent from my HTC Vision using XDA App
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
My whole goal is to get the phone temporary rooted using visionary and then finding a way to permanently root the phone....so to answer your question temp root is not working using Visionary R14....It did work when I was using Visionary R7... but since the visionary app (which was the R7 version) came off the Android Market, the process has be super difficult...thanks
My whole goal is to get the phone temporary rooted using visionary and then finding a way to permanently root the phone....so to answer your question temp root is not working using Visionary R14....It did work when I was using Visionary R7... but since the visionary app (which was the R7 version) came off the Android Market, the process has be super difficult...thanks
Nonentity018 said:
Is temp root working?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
+1
Like he said, use that, don't waste your time with visionary
sammd301 said:
HELP...HELP....HELP.....PLEASE HELP
I have the T-mobile G2 and I did an over the air upgrade in December of 2010, ever since then the only version of VISIONARY that work on my phone was "Visionary R7" I have search all over the web trying to find the "Visionary R7" so far I have yet to find it...that is why I am posting on this forum......By the way I have tried the latest version of Visionary "R14" but it doesn't work, I have also tried Visionary "R3" "R11" "R12" and "13" and they all don't work on my OTA upgraded T-mobile G2....
So if anyone know where I can download "Visionary R7" please let me know...
Or
If someone know of a way to either Temporary or permanently root the G2 without Visionary please let me know as well
Thanks so much for your kind help......
Click to expand...
Click to collapse
I'd stay away from visionary if I were you! Its messing up just as many phones as it is rooting them!
part of the problem is that a visionary method is stickied in one of these subforums... that needs to be taken down desperately and replaced with gfree/rage.
Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
I am in the process of using this method....I'll let you all know how it turns out. by the thanks for pointing me to it...
Cobra281 said:
use this method, it's easier and safer:
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Click to expand...
Click to collapse
Yes I am in the process of using ADB / RAGE method....I run in problem and I could use someone help please...
TEMP ROOT
ON YOUR PC: Unzip the gfree_temp-root.zip files to a folder. From a cmd window or terminal, navigate to that folder and execute these commands:
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
===========
All the commands are working except
$ adb push rage /data/local/tmp/rage
the reply I get after input the command is
Cannot open 'rage': No such file or directory
I have search the web for help...but I could find help on that issue
SO please if anyone knows what I am doing wrong could you please help....
thanks
unzip the gfree_temp-root.zip again and make sure it extracted rage.
rage IS in there, I just downloaded the zip and opened it and looked.
yeah, look for a file called "rage". if it's there, you didn't get the proper directory. you have to get to the "gfree_temp-root" directory on your computer, and THEN adb push it
Cobra281 said:
yeah, look for a file called "rage". if it's there, you didn't get the proper directory. you have to get to the "gfree_temp-root" directory on your computer, and THEN adb push it
Click to expand...
Click to collapse
Yes the "Rage" file is there, all the other command work fine...except the one dealing with the "Rage" file
ratchetrizzo said:
unzip the gfree_temp-root.zip again and make sure it extracted rage.
rage IS in there, I just downloaded the zip and opened it and looked.
Click to expand...
Click to collapse
Thanks so much for your input....when I gfree_temp-root.zip file I can see that the "RAGE" file is present but after 20 to 30 minutes the "RAGE" file disappear from the folder but all the other files remains....Is an alternative gfree_temp-root download link that anyone might know of....thanks again
Disable your virus scanner while you do this, I bet its giving a false positive to the rage file and deleting it
Sent from my HTC Vision using XDA App
ratchetrizzo said:
Disable your virus scanner while you do this, I bet its giving a false positive to the rage file and deleting it
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Thanks so much "Ratchetrizzo" for the tip on disable my anti-virus program, I was able to get the "Rage" command line to work....But now I have run into another ROAD BLOCK and truly hoping someone could help me out as well
I am now getting this error on the Terminal Emulator on my G2 after inputting the following command line from rooting instruction...
'You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:'
"# /data/local/tmp/root" without the # sign
I got this error message
"## mkdir failed for /system/xbin, File exists
## cp: can't stat '/system/xbin/busybox': Not a directory
## Unable to chmod /system/xbin/busybox: not found
## cp: not found
## cp: not found
## Unable to chmod /system/bin/su: No such file or directory"
Once again I am seeking help on this...So if anyone can help...please let me know. Thanks again for all of the support that I have received so far ...
sammd301 said:
Thanks so much "Ratchetrizzo" for the tip on disable my anti-virus program, I was able to get the "Rage" command line to work....But now I have run into another ROAD BLOCK and truly hoping someone could help me out as well
I am now getting this error on the Terminal Emulator on my G2 after inputting the following command line from rooting instruction...
'You now have read-write access to your /system, hboot, and recovery partitions. But you still need to "lock in" root, and give you 'su' access in the future. So just do:'
"# /data/local/tmp/root" without the # sign
I got this error message
"## mkdir failed for /system/xbin, File exists
## cp: can't stat '/system/xbin/busybox': Not a directory
## Unable to chmod /system/xbin/busybox: not found
## cp: not found
## cp: not found
## Unable to chmod /system/bin/su: No such file or directory"
Once again I am seeking help on this...So if anyone can help...please let me know. Thanks again for all of the support that I have received so far ...
Click to expand...
Click to collapse
Well, start all over but once you get a root (a #) for the first time, rm -rf /system/xbin then reboot the phone, then start all over again and see if that works. for some reason you have a /system/xbin FILE, not a directory.
ratchetrizzo said:
Well, start all over but once you get a root (a #) for the first time, rm -rf /system/xbin then reboot the phone, then start all over again and see if that works. for some reason you have a /system/xbin FILE, not a directory.
Click to expand...
Click to collapse
When I input "rm -rf /system/xbin" command I got back
"rm failed for -rf, Read-only file system
sammd301 said:
When I input "rm -rf /system/xbin" command I got back
"rm failed for -rf, Read-only file system
Click to expand...
Click to collapse
well that's a problem, if /system is read only you can't lock in root
do this before you rm that stuff (remember to be at a root # prompt)
mount -o remount,rw /system
then rm the stuff, then start the root process over.
ratchetrizzo said:
well that's a problem, if /system is read only you can't lock in root
do this before you rm that stuff (remember to be at a root # prompt)
mount -o remount,rw /system
then rm the stuff, then start the root process over.
Click to expand...
Click to collapse
Yes, I did what you suggested, but now I am getting
"rm failed for -rt, no such file or directory" after inputting ""rm -rf /system/xbin" command...by the way thanks so much for helping me out on this...
I am currently in the process of rooting my G2 and when i have to enter this command, (adb shell chmod 755 /data/local/tmp/* and adb shell /data/local/tmp/psneuter) i get no such file or directory everytime. All other commands enter in without a problem. What is chmod 775 anyway. it is the only thing not previously included in the rooting process. Can anyone please give me some feedback on what is going wrong here
thanks
What ever you are doing stop now.
You're doing that the hard way. Here's what u do goto theunlockr.com and then click how to's, then goto the g2 picture then u want to do the how to get temp root first then once that is completed do the permanent root tutotrial. Everything on theunlockr has a video and text so u can't f up.
My best wishes and if u need help like asap jus send a pm or email me [email protected] gmail
gamestar21 said:
I am currently in the process of rooting my G2 and when i have to enter this command, (adb shell chmod 755 /data/local/tmp/* and adb shell /data/local/tmp/psneuter) i get no such file or directory everytime. All other commands enter in without a problem. What is chmod 775 anyway. it is the only thing not previously included in the rooting process. Can anyone please give me some feedback on what is going wrong here
thanks
Click to expand...
Click to collapse
What guide are you following?
Sent from my T-Mobile G2 using XDA App
I'm stuck in the same place. I get operation denied every time...
Please help
A lot of people say its because you haven't set up the path correctly to the abd folder or haven't put the root files in the right abd folder.
Sent from my HTC Vision using XDA Premium App
Where to find 'chmod' answers
I had to exchange my G2. The one T-Mo sent is running Gingerbread(?) ver 2.3.4
I've been to theunlocker.com and in the procedure to downgrade so that I can root, http://theunlockr.com/2011/07/22/how-to-downgrade-a-gingerbread-t-mobile-g2-so-it-can-be-rooted/ two of the steps are to enter in terminal:
chmod 777 /data/local/tmp/fre3vo
and
chmod 777 /data/local/tmp/misc_version
When I do this I get 'chmod' is not recognized as an internal or external command, operable program or batch file
I have spent several hours in the forums and can't find where I've gone wrong or where to find 'chmod'
Someone please help me
SOLVED, use this link http://forum.xda-developers.com/showthread.php?t=1178912 and also (from one noob to another) it helps to type 'adb shell chmod....' if that is one of the issues you're having
You don't seem to be in the directory that you have adb installed. Change directory to there and you should be good
Sent from my Bulletproof G2
I've searched my entire hard drive, both mac & xp. It's not there. I've downloaded the SDK twice, I can't find it anywhere.
Sent from my T-Mobile G2 using XDA App
noflopscott said:
I've searched my entire hard drive, both mac & xp. It's not there. I've downloaded the SDK twice, I can't find it anywhere.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
On my xp it installed to c:/program files/android/android-sdk/platform-tools/ automatically, maybe try there. If you can't find it try downloading just the adb program and putting it in your adk platform-tools folder. You did also download the android development package right?
Sent from my Bulletproof G2
I went ahead and downloaded the ENTIRE sdk, from 1.5 to 3.3, did a hard drive search, still nowhere to be found :-c. Any other ideas?
Sent from my T-Mobile G2 using XDA App
noflopscott said:
I went ahead and downloaded the ENTIRE sdk, from 1.5 to 3.3, did a hard drive search, still nowhere to be found :-c. Any other ideas?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Are you even installing the SDK? Follow this guide to get ADB up and running: http://forum.xda-developers.com/showthread.php?t=865685
Sent from my HTC Vision using XDA App
This method worked http://forum.xda-developers.com/showthread.php?t=1178912
Followed it letter by letter and I was downgraded from 2.3.4 to 2.2 in just a few minutes :-D
I've followed the instruction of firewater s-off.
After successfully pushed 'firewater' to /data/local/tmp and changed the permission to 755, I've typed '/data/local/tmp/firewater' but nothing happened.
View attachment 2809420
It's the same problem under Windows 7.
Whats more, the file 'firewater' in /data/local/tmp disappeared automatically after '/data/local/tmp/firewater' has been executed.
Another question was that I had never entered 'su' after 'adb shell', but still got root permission?
Tried with both my MacBook Pro and desktop computer and got exactly the same results.
Seems you have got su permissions maybe you shouls check its log
Same issue, after adb push, I don't get SU request and everything else goes quite.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Some people have said using a different Superuser app gives a better result so perhaps change and see how you get on