Related
What for SuperUser command does exists?
Is there a List?
How can i get the file from
/data/data/com.android.providers.settings/databases/settings.db ?
i used:
adb pull /data/data/com.android.providers.settings/databases/settings.db C:
but it says:
failed to copy '/data/data/com.android.providers.settings/databases/settings.db' to 'C:': Permission denied
any solution?
try typing
Code:
su
or if not try
Code:
adb remount
I dont know much about this stuff yet, but that could help
ilendemli said:
How can i get the file from
/data/data/com.android.providers.settings/databases/settings.db ?
i used:
adb pull /data/data/com.android.providers.settings/databases/settings.db C:
but it says:
failed to copy '/data/data/com.android.providers.settings/databases/settings.db' to 'C:': Permission denied
any solution?
Click to expand...
Click to collapse
are you rooted?
try:
Code:
adb shell "su -c 'cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/'"
this will use su to copy it to the sdcard, then you should be able to pull it from there. Phone may pop up a "Superuser request". Be prepared to allow it.
when i type:
adb shell "su -c '/data/data/com.android.providers.settings/databases/settings.db /sdcard/'"
It says:
/data/data/com.android.providers.settings/databases/settings.db: permission denied
My Device is rooted, and i gave su permission
You forgot the "cp" between "su -c" and "/data/data/..."
C:\Users\ilendemli>adb shell "su -c '/data/data/com.android.providers.settings/databases/settings.db /sdcard/'"
/data/data/com.android.providers.settings/databases/settings.db: permission denied
C:\Users\Muhammet ilendemli>adb shell "su -c 'cp /data/data/com.android.provider
s.settings/databases/settings.db /sdcard/'"
cp: not found
My CMD Window, whats wrong?
Hum, that's strange.
Try this : (<Enter> means pressing the Enter key on your keyboard)
adb shell <Enter>
su <Enter> (here you may have to look at your phone to give him the autorisation it needs)
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/ <Enter>
If it says "cp: not found", try this line :
busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/ <Enter>
busybox: not found
Try to replace busybox by bb in the command I gave you.
If it doesn't work, well, I'll doubt you did your root well ^^ Cause it should have install BB
Can you explain us what you did to root your phone ?
I used SuperOneClick Root, to root my Phone. it installed the su files and superuser.apk nothing else
EdIT:
I installed busybox manually and rebootet my phone, now when i type:
>adb shell "busybox -c cp '/data/data/com.android.providers.settings/databases/settings.db /sdcard/'"
it says:
-c: applet not found
EDIT2:
>adb shell
$ busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/
busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/
cp: can't open '/data/data/com.android.providers.settings/databases/settings.db': Permission denied
$
That's normal, you missed the "su" command in your Edit 2.
So, 2 ways to do it.
Edit 1 version :
adb shell "su -c busybox cp '/data/data/com.android.providers.settings/databases/settings.db /sdcard/'"
Edit 2 version :
adb shell
su
busybox cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/
And I thought SuperOneClick did install BB... Well, I thought wrong ^^
Edit 1 version: Didnt worked..
Edit 2 version: WORKED!? i have the database,
now, how can i give these command in java?
anything with exec("..
From adb, you can't execute Java methods (because you're not in a JVM).
And I don't think you can access the DB like that in fact.
You have to make an app that read/write/do what you want on the DB (and it seems you're doing so, refering to the other topic you made )
it's not allowed, to edit databases directly, so my app will copy the database somewhere else, edit it, and copy it back, then it should work.
€: and i don't want to edit databses from the adb, i cant do it, the program cant do it, but java can do it:
Code:
myDB.execSQL("DELETE FROM system WHERE name = 'name1';");
myDB.execSQL("DELETE FROM system WHERE name = 'name2';");
myDB.execSQL("INSERT INTO system (name, value) VALUES ('name1', '"+arr[0]+"');");
myDB.execSQL("INSERT INTO system (name, value) VALUES ('name2', '"+arr[1]+"');");
Yes it should.
Make sure you don't mess with the DB though. It's an easy thing to break
Edit : From adb, apparently you can do something like
sqlite3 settings.db
Then you'll have a DB prompt where you can write SQL commands like SELECT, INSERT, etc.
can busybox delete and replace files?
BB lets you use any Unix command.
So you can use (in your example) the mv command, which will move a file from a directory to another one.
Runtime.getRuntime().exec("busybox mv /sdcard/ /data/data/com.android.providers.settings/databases/settings.db");
this should work
E: Hmm, doesn't work..
E2: should look like this: Runtime.getRuntime().exec("busybox mv /sdcard/settings.db /data/data/com.android.providers.settings/databases/");
will try it.
Yes. But remember you have to be root to do that
I have already have the clockrecovery mod recovery flashed and i have the app that says superuser permission...
But this is what error i am getting when i try to confirm that my -s is off so i can install the rom i want:
C:\Users\Tariq Khan\Desktop\g verify>adb shell
$ su
su
cd /data/Permission denied
$ cd /data/local
cd /data/cd /data/local
cd: bad substitution
$ cd /data/local
cd /data/local
$ chmod 777 gfree_verify
chmod 777 gfree_verify
$ stop ril-daemon
stop ril-daemon
$ ./gfree_verify
./gfree_verify
Error: could not open modem device: /dev/smd0
Error: verify could not initialize device!$
i got it figured out thanks guys so now i can flash the desire z rom directly right no need to do anything just rename it as update and apply it in recovery i have the g2 and i want the desire z rom so thats what i do right?
right you should have no problems
I had exactly the same problem. I think I rooted correctly. When I run TM and type su, it asks me allow such application to request superuser permissions.
but when I try to fun gfree_verify to confirm, I got above errors.
Please help, thanks
To downgrade your HBOOT to go back to 2.2 visit this link http://forum.xda-developers.com/showthread.php?t=1255474
This will allow you to flash 2.2 to perm root the phone
If you wish to help with perm root status for Android 2.3.3, please visit this thread http://forum.xda-developers.com/showthread.php?t=1218580
Thanks to everyone in this post who has helped get this far. You will need to have the Android SDK installed and working knowledge of ADB and basic file system structure.
Major help from minneyar
TEMP ROOT Instructions:
Download http://tinyw.in/1lI
Unzip if required and put in your ADB folder
Launch command prompt and navigate to your ADB folder
adb push fre3vo /data/local/tmp/
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF (if this doesn't work, try rebooting phone)
Download these 2 files here and put them in your ADB directory: http://forum.xda-developers.com/showthread.php?p=14927732#post14927732
exit back to command prompt if you aren't there already
adb push Superuser3-beta1.apk /data/app/
adb push su-3.0-alpha7 /data/local/tmp
adb shell (should now see # instead of $)
cd /data/local/tmp
chmod 777 su-3.0-alpha7
./su-3.0-alpha7
cd /
mount -o remount,rw -t rootfs rootfs /
rm vendor
mkdir vendor
mkdir vendor/bin
cat /data/local/tmp/su-3.0-alpha7 > /vendor/bin/su
chmod 4755 /vendor/bin/su
You now have temp root. Disregard any notification about outdated SU binary. Root will go away if you reboot. If you reboot your phone you can obtain root again by just running the following
adb shell
chmod 777 /data/local/tmp/fre3vo
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF
adb shell (should now see # instead of $)
cd /data/local/tmp
chmod 777 su-3.0-alpha7
./su-3.0-alpha7
cd /
mount -o remount,rw -t rootfs rootfs /
rm vendor
mkdir vendor
mkdir vendor/bin
cat /data/local/tmp/su-3.0-alpha7 > /vendor/bin/su
chmod 4755 /vendor/bin/su
I haven't found a way to re-root after rebooting without connecting to a PC
Type su and see if it gives you root permissions
Sent from my MiuiSpeedy
says su: not found.
You are saying you cannot install the superuser app? From reading in the Evo3D forums, you could install Superuser, even without being rooted, but it obviously won't allow root access, until you run a root exploit.
Try rebooting the phone, installing superuser, run fre3vo, and then try the adb shell, and su method.
This is getting interesting. Hopefully you are on to something.
Stuke00 said:
See screenshot. Doesn't the # mean temp rooted? Tho I cannot install SU and Root Explorer isn't working. Anything else I need to do first or something?
Click to expand...
Click to collapse
Looks hopeful!
tokuzumi said:
You are saying you cannot install the superuser app? From reading in the Evo3D forums, you could install Superuser, even without being rooted, but it obviously won't allow root access, until you run a root exploit.
Try rebooting the phone, installing superuser, run fre3vo, and then try the adb shell, and su method.
This is getting interesting. Hopefully you are on to something.
Click to expand...
Click to collapse
Okay let me clarify
I can install SU but it wouldn't install the binaries. I did all of the above. Says su: not found.
I then tried something else.
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cat /system/bin/sh > /system/bin/su
# chmod 4755 /system/bin/su
I was then able to get the SU binaries to install but Titanium Backup says:
"Busybox works but the "su" command does not elevate to root: "whoami" reports "app_135" instead of root/uid 0.
then su from the command prompt was saying "link_image[1935]: 3160 missing essential tablesCANNOT LINK EXECUTABLE" and now back to su: not found again....
I don't know enough about linux commands to give you any real info. Like in the other thread, talk to agrabren, to see what he has to say.
tokuzumi said:
I don't know enough about linux commands to give you any real info. Like in the other thread, talk to agrabren, to see what he has to say.
Click to expand...
Click to collapse
Yeah I tweeted him with what I could provide with 160 characters. Just waiting now.
Well here's a tweet he put out a couple of hours ago.
@agrabren: For those with the SHIFT, it's a known bug in my code that we missed the address. One too many zeroes in the list. I'll try to fix it soon.
Sent from my PG06100 using XDA App
crump84 said:
Well here's a tweet he put out a couple of hours ago.
@agrabren: For those with the SHIFT, it's a known bug in my code that we missed the address. One too many zeroes in the list. I'll try to fix it soon.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Yeah he posted that right after I gave him the memory address for the exploit. Just means that I did it the manual way through debugging. At least I think so... hopefully soon!
Good news, everybody! I have successfully acquired temp root on my Shift!
First, fre3vo has to be pointed at the right address. After copying it over to my phone, I did "adb shell" and then ran it like so:
/data/local/tmp/fre3vo -debug -start fbb58a00 -end FFFFFFFF
That printed out a message that it found an exploit and kicked me out of the shell. After doing "adb shell" again, I got a command prompt. I tried installing the 2.3.6.3 version of Superuser, but it complained about being unable to install "su"; I tried to find a separate su binary and copy it over manually, but it didn't work due to a linker error.
After searching around, I found a beta version of Superuser 3:
http://forum.xda-developers.com/showthread.php?p=14927732#post14927732
First I uninstalled the old version of Superuser and then used adb to install the new one from that thread. I ran it and it said it was unable to install su, so I downloaded the version of su provided there and installed it manually. The process went something like:
Code:
adb push su-3.0-alpha7 /data/local/tmp
adb shell
# cd /data/local/tmp
# chmod 4755 su-3.0-alpha7
# ./su-3.0-alpha7
# mount -o remount,rw -t ext3 /dev/block/mmcblk0p26 /system
# cat su-3.0-alpha7 > /system/bin/su
# chmod 4755 /system/bin/su
I don't know if explicitly running "./su-3.0-alpha7" is necessary, it just seemed like a good idea at the time. I don't know if everybody's block device will be named "mmcblk0p26", I used "mount" to figure out what was mounted at /system.
Anyway, after all that was done, I ran Superuser again and it didn't complain. To test it out, I started up Wireless Tether. It asked me for superuser permissions, which I granted it, and it's working fine.
Root successful!
Good job!!
Sent from my Speedy HTC EVO shift on XDA Premium app
I followed those steps exactly and got what I would call a partial root. Some of the 'you need root' errors are gone but "su" still results in 'not found' even though "mkdir su" results in 'file exists.'
mmcblk0p26 exists on this unit.
The weirdest part is that Adfree will accept the device as rooted and with superuser but says it can't find a partition to modify. And after a reboot root is definitely gone.
I think you're on to it but it isn't quite there yet.
It seems to be fully temprooted to me; I have to redo it if I reboot, but otherwise it's working perfectly. After following the steps I listed above, running "ls -l /system/bin/su" should produce this output:
Code:
# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-xr-x root root 22228 2011-07-25 19:14 su
If it says "No such file or directory" instead, then the su binary isn't in the right place.
Looking back over what I wrote, I think I left out a step -- if you were following what I listed exactly, it probably won't work, because I forgot to change to the /data/local/tmp directory. I'll update that...
Update: after playing around with it for a while, something is definitely not quite right. Everything works fine at first; I've tested Wireless Tether and Titanium Backup and they're both fine. After leaving my phone for a while and coming back, though, applications that try to get root access mysteriously fail. The dialog prompt doesn't even appear.
Going back into the adb shell, /system/bin/su is still there, but trying to run "su" causes this to happen:
Code:
# su
su
link_image[1935]: 3802 missing essential tablesCANNOT LINK EXECUTABLE
But if I use cat to overwrite su and then chmod it again, everything works. su must somehow be getting modified by something else and replaced with a bad version... but I'm not sure where to look.
I caught something like that.
I think there should be a chmod 777 su-3.0-alpha7 after cd /data/local/tmp
minneyar said:
It seems to be fully temprooted to me; I have to redo it if I reboot, but otherwise it's working perfectly. After following the steps I listed above, running "ls -l /system/bin/su" should produce this output:
Code:
# ls -l /system/bin/su
ls -l /system/bin/su
-rwsr-xr-x root root 22228 2011-07-25 19:14 su
If it says "No such file or directory" instead, then the su binary isn't in the right place.
Looking back over what I wrote, I think I left out a step -- if you were following what I listed exactly, it probably won't work, because I forgot to change to the /data/local/tmp directory. I'll update that...
Update: after playing around with it for a while, something is definitely not quite right. Everything works fine at first; I've tested Wireless Tether and Titanium Backup and they're both fine. After leaving my phone for a while and coming back, though, applications that try to get root access mysteriously fail. The dialog prompt doesn't even appear.
Going back into the adb shell, /system/bin/su is still there, but trying to run "su" causes this to happen:
Code:
# su
su
link_image[1935]: 3802 missing essential tablesCANNOT LINK EXECUTABLE
But if I use cat to overwrite su and then chmod it again, everything works. su must somehow be getting modified by something else and replaced with a bad version... but I'm not sure where to look.
Click to expand...
Click to collapse
YES! I have root! I was able to install a screenshot app and test it this is amazing progress! Thanks for that.
So now when I reboot, you have to do the entire thing again? SU and all?
Stuke00 said:
So now when I reboot, you have to do the entire thing again? SU and all?
Click to expand...
Click to collapse
Yes, every time you reboot you'll have to redo the whole process, including running fre3vo and then copying su into /system/bin. Hopefully somebody will figure out a permanent root soon.
Wow those SU binaries are disappearing before I even reboot! Already gone and I haven't rebooted the phone
I think I had that issue too. I just couldn't believe the files just disappeared and thought I did something wrong somewhere.
Would a logcat help anyone at all? Anything I should look for?
Hi,
I am trying to push
Code:
$ adb push androidvncserver /data/androidvncserver
failed to copy 'androidvncserver' to '/data/androidvncserver': Permission denied
When I do 'su' in 'adb shell', i get a root prompt , that means I have rooted my device, right?
Code:
$ adb shell
$ su
#
If so, how can I push to /data?
Thank you.
Your default shell is secured - means, when you're executing ADB command without executing something through SU, you're going through the regular permissions.
To enable insecure boot, set ro.secure to 0 in your build.prop. I'm not sure if it's enough, though, or if you need a kernel compiled with security off to take full advantage of insecure adb commands.
You can push the file to sdcard, enter shell, enter su, and in root shell copy the file where you want it to be.
And you're posting in the wrong section. There is Q&A for questions, please move there.
Hello everyone...
I have a Motorola RAZR 201M(XT902) in Japan and use Motofail2go to root it.But it doesn't work.
(follow http://forum.xda-developers.com/showthread.php?p=32889627)
I installed Sudoku.apk and push the motofail2go to the device(also su,Superuser.apk,busybox).
when
$ run-as com.motorola.bug2go /data/local/tmp/motofail2go prep2
Here is the error message:
"run-as: exec failed for /data/local/tmp/motofail2go Error: Operation not permitted"
and i try $ run-as com.motorola.bug2go
but error message : "run-as: exec failed"
Anyone help? Thanks...
Sorry buddy. Nothing works. We 201m users are SOL.
Have you tried this?
http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/
Thanks Paul!
No luck with that either. Appreciate the feedback, however.
I hope somebody will study the XT902 root.
goodayoo said:
I hope somebody will study the XT902 root.
Click to expand...
Click to collapse
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Almalieque said:
I really want this thing rooted. How do one go about figuring out how to root it? I assume because of it's lack of popularity, no one has done it, but I'm willing to do the grunt work if there's some sort of guide or assistance. I changed over to DoCoMo with the GS4 and now have this paperweight that I would want to actually use.
Thanks!
Click to expand...
Click to collapse
There some Japanese guys doing some things to try and get root. They are active. The site has a lot of rather unpleasant (read offensive) advertisements. PM if you are interested (its in Japanese)
root
help!!!
Root and Unlocked bootloaders!
Proceed at yor own risk
hungln03 said:
help!!!
Click to expand...
Click to collapse
1)Prep
Android SDKと各種ドライバを導入する。
以下の必要ファイルをC:\***（何でも良い）に配置する。
・XT902_SBMの中身(http://www1.axfc.net/uploader/so/2991543 >>125氏)
・su（http://www1.axfc.net/uploader/so/2918729 password：f10d）
・Superuser.apk（in the above downloaded）
・busybox（in the above downnloaded）
201M Plug the phone into the comp
any port will do
2)adb pushで必要ファイルを/data/local/tmp転送
コマンドプロンプトを開く
C:\Users\（ユーザー名） >cd C:\***
adb push su /data/local/tmp
adb push Superuser.apk /data/local/tmp
adb push busybox /data/local/tmp
adb push unlock_security_module /data/local/tmp
adb push break_setresuid /data/local/tmp/
adb push mole-plough-ccsecurity.so /data/local/tmp/
adb push mole-plough-lsm.so /data/local/tmp/
3)unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ chmod 777 *
[email protected]:/data/local/tmp $ ./unlock_security_module
[email protected]:/data/local/tmp $ ./break_setresuid
（unlock_security_moduleが動いてMIYABIとNANDロック解除）
（色々表示されるので↓が出る間で待つ）
Unlocked LSM.
Do setresuid...
OK.
[email protected]:/data/local/tmp #
（#if done correctly temp root should be achieved）
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
4)system putting together su，Superuser.apk，busybox
[email protected]:/data/local/tmp # mount -o rw,remount /system /system
[email protected]:/data/local/tmp # cat /data/local/tmp/su > /system/xbin/su
[email protected]:/data/local/tmp # cat /data/local/tmp/busybox > /system/xbin/busybox
[email protected]:/data/local/tmp # cat /data/local/tmp/Superuser.apk > /system/app/Superuser.apk
[email protected]:/data/local/tmp # chmod 644 /system/app/Superuser.apk
[email protected]:/data/local/tmp # cd /system/xbin
[email protected]:/system/xbin # chown root.root su
[email protected]:/system/xbin # chown root.root busybox
[email protected]:/system/xbin # chmod 6755 su
[email protected]:/system/xbin # chmod 755 busybox
[email protected]:/system/xbin # mount -o ro,remount /system /system
After the opperation is done it is ok to remove the cable from the pc。
check and see if「SuperSU」was installed if it wasn't download chainfire (su) from the play store
⇒SU --> update
Fro the play store download busybox。
⇒busybox -->update
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
I don't own the 902, but it's good to see this. I know quite a few people have been looking for this. You should start your own thread with the procedures, so it will get more publicity.
Thank u!
thank u so much.!1
sbeaber4 said:
Proceed at yor own risk
271 ：270：2013/09/15(日) 23:31:42.67 ID:tIg7fkl6
Get the right CWM.img http://forum.xda-developers.com/showthread.php?t=2298521の201M
put the CWM.img you downloaded in motoapoc file you find here
adb push unlock /data/local/tmp/
adb shell chmod 755 /data/local/tmp/unlock
adb shell
cd /data/local/tmp/
chmod 777 *
./unlock_security_module
./break_setresuid
./unlock
New Command prompt
5)Inserting CWM(PC Operation)
adb shell "su -c 'mount -o remount,rw /system'"
adb shell "su -c 'mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak'"
adb shell "su -c 'mv /system/recovery-from-boot.p /system/recovery-from-boot.bak'"
adb push cwm.img /data/local/tmp/cwm.img > nul
adb shell "su -c 'dd if=/data/local/tmp/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'rm /data/local/tmp/cwm.img'"
adb reboot recovery
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Can you tell me more about this step
Confirm?
Can confirm if the latest instructions have worked for your 201m?
That your rooted and bootloader unlock.
Thanks a bunch!
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
sbeaber4 said:
Boot loader is unlocked and CWM is installed. Initially I still
Had temp root so I flashed slim beans xt907 rom. It works. I'm unable to test data with it as I don't have a SoftBank sim. Also I still can't connect to the play store.
Click to expand...
Click to collapse
Thanks for the feedback.
Still awaiting more confirmation with others. It's a step forward though.
I've had my phone for almost a year now. If I cancel my softbank service or run the contract to the end I want an option to root and unlock the bootloader in the future.
could u provide more friendly filehost?
i can't find the download button there
Root! (temp root that is...)
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Quick Tip
zenstarlight said:
I'm just posting to confirm I've rooted my 201m (xt902).
Props to sbeaber4!
From my limited knowledge since it's temp root if I restart my phone I lose root access...
Next step in the future unlock bootloader.
Peace y'all.
Click to expand...
Click to collapse
Found that if I a did restart my phone root was lost but I found a quick fix without going through the whole process again.
Just do these steps
unlock_security_module（temp root）
adb shell
[email protected]:/ $ cd /data/local/tmp/
[email protected]:/data/local/tmp $ ./unlock_security_module
Just enter those three steps then you're back to temp root
Also you can just to a quick reboot with link2sd or any other app that just reboots the android ui. You don't have to enter commands every time you reboot unless it's a full reboot.
Help for Gaigin rooting 201M
sbeaber4 said:
Proceed at yor own risk
...
You should be in CWM
Cheers! I take 0 credit. Long Live the Developers!!
Click to expand...
Click to collapse
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
kprower said:
Noob on XDA, and rooted a MT4G in the past wth help from these forums.
Can someone help translate the kanji for rooting the 201M? Will rooting allow you to change the device location and prevent random all Japanese pop-up alerts/"are you sure" messages? Thanks for any help
Click to expand...
Click to collapse
Once CWM is online you might be able to flash a VZW or Aussie stock ROM. Actually, you could probably flash CM... That'll fix the Japanese popups. Of course, it also could very possibly brick it. Proper precautions must be made... On my tablet at the moment, does anyone know if sbf.droid-developers has 902 images?
Sent from my Nexus 7 using Tapatalk 4