Is there already a method on the root 9.2.2.3 ?
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
Perhaps downgrade your ROM to an earlier version. Someone has done it with HC.
http://forum.xda-developers.com/showthread.php?t=1400532
[Edit] Ignore me. Apparently you cannot go back to a lower version number.
Bump
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
aga37 said:
Is there already a method on the root 9.2.2.3 ?
Click to expand...
Click to collapse
have you tried this
http://forum.xda-developers.com/showthread.php?t=1515470
TNS201 said:
have you tried this
http://forum.xda-developers.com/showthread.php?t=1515470
Click to expand...
Click to collapse
It has been patched up with this update
wolf849 said:
It has been patched up with this update
Click to expand...
Click to collapse
confirmed
if you have a B50 or B60 TF101 you can try my way. this will restore it back to 9.2.1.11 and then OTA 9.2.3.3
http://forum.xda-developers.com/showthread.php?t=1524302
chadster214 said:
if you have a B50 or B60 TF101 you can try my way. this will restore it back to 9.2.1.11 and then OTA 9.2.3.3
http://forum.xda-developers.com/showthread.php?t=1524302
Click to expand...
Click to collapse
Problem is that 9.2.2.3 update came for tf101g and that means SBK3 device, therefore root by nvflash will not make the trick...
P.S. As far as we are talking about 3g devices
Is it possible to flash recovery.img on device via adb ? (Fastboot) Then boot into CWM and flash a rooted rom ?
Sent from my GT-I9100 using XDA
Nick502 said:
Is it possible to flash recovery.img on device via adb ? (Fastboot)
Click to expand...
Click to collapse
The bootloader does support the fastboot protocol (and some obscure methods of booting a kernel via JTAG), but it's locked down to the point that you can't even get fastboot to recognize the device.
So no luck there
ViperMod is your answer I believe
I've not had to root since any version of ICS, but many are have success with ViperMod: http://forum.xda-developers.com/showthread.php?p=21009605
You might have to drop back to a 9.2.2.17 or 19 but there are lots of roms out there that are still on that version. I would give it a try on the 9.2.2.3 though, my guess would be it will work. cheers.
chadcspencer said:
I would give it a try on the 9.2.2.3 though, my guess would be it will work. cheers.
Click to expand...
Click to collapse
It doesn't work
I tried with my TFT101G build 9.2.2.3 but didn't work!
OK, so to sum it up:
1. SUID /proc/<pid>/mem write has been patched in this release (aka 9.2.2.3) therefore mempodroid exploit and basing on it viperMod is useless
2. qEmu vulnerability in /data/local.prop is also patched up so TPsparkyroot will also fail.
3. The location of backed up files and temp storage have been shifted out from data therefore all rooting tools connected with ASUS backup app will not do the trick.
4. Jumping back to previous software is unachievable without root.
So I ask you to post ONLY methods that are not listed above.
(However I think that we have to wait for next linux Local Privilage Escalation bug to be discovered in order to get rooted)
Cheers
P.S. Sorry for any mistakes English is not my native.
ICS 9.9.23G
I have a question is 9.2.23 ics available for all transformers? When I got my update it was 9.2.17. Then I used vipermod to root and voodoo root keeper.do I need to temp unroot to receive this update?
thunderman98 said:
I have a question is 9.2.23 ics available for all transformers? When I got my update it was 9.2.17. Then I used vipermod to root and voodoo root keeper.do I need to temp unroot to receive this update?
Click to expand...
Click to collapse
OTA is only for TF101G. You can install firmware pack from ASUS website through custom recovery, but I do not see any point of doing that.
Any news ? Anyone succeeded in rooting 9.2.2.3??????
Thanks in advance
hearts king101 said:
Any news ? Anyone succeeded in rooting 9.2.2.3??????
Thanks in advance
Click to expand...
Click to collapse
Nope, I've only achieved /data and /cache readwrite access but nothing more Unless you know any thing that can be done in that situation.
wolf849 said:
Nope, I've only achieved /data and /cache readwrite access but nothing more Unless you know any thing that can be done in that situation.
Click to expand...
Click to collapse
If you can write to arbitrary locations on /data try dropping a /data/local.prop with 'ro.kernel.qemu=1' inside (without quotes), reboot and then issue "id" through adb shell to check if adb is running as root.
If it works, ViperMod can be adapted almost painlessly to push su, Superuser.apk and busybox with the correct permission bits
sbiriguda said:
If you can write to arbitrary locations on /data try dropping a /data/local.prop with 'ro.kernel.qemu=1' inside (without quotes), reboot and then issue "id" through adb shell to check if adb is running as root.
If it works, ViperMod can be adapted almost painlessly to push su, Superuser.apk and busybox with the correct permission bits
Click to expand...
Click to collapse
Unfortunately I've tried that and than I came to a conclusion that 'ro.kernel.qemu=' has been shifted... Try read build.prop on /system and you will find it there, so /data write does nothing for now
EDIT:
Nonetheless, I have rw access to /cache where dlpkgfile is held, so maybe it is possible to do a downgrade of firmware through that hole.
EDIT2:
BTW, I did it by flashing TW 9.2.2.3 firmware on to WW 9.2.2.3 through EP101_SDUPDATE (or similar).
Than:
adb mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /cache /data/local/tmp
adb rebbot
After that /data becomes readwrite
EDIT3:
There is also one more question: where is held /tmp partition needed to repack the blob maybe by accessing it and pushing blob we can manually force its update.
Related
Update: I'd recommend using the full update found here instead - it's less likely to fail than this one based on the patch update.
I've managed to build a working RC30 update that retains root via adb shell. Much of the credit goes to the people in this thread. All I did was build an updated boot.img with ro.secure set to 0, and reinsert it into the RC30 update.
Installing it will require the modded RC29 recovery image found in that thread.
A warning: if you've modified any files that are patched in the RC30 update, bad things will happen. Also, I had to disable the version check, so if you attempt to apply the update to anything but RC29, bad things will happen. I'm not responsible if your phone is bricked, bursts into flames, or even starts walking around on it's own and attacks you.
Modified RC30 update
did you have any trouble installing it? I will give it a try later today.
1 question, so theres no root on the phone Only by adb?
Edit:2 questions have you try to put busybox on?
It worked fine for me. Just follow the manual firmware update procedure, and it should work, as long as you're already running the modified RC29.
humble said:
1 question, so theres no root on the phone Only by adb?
Click to expand...
Click to collapse
Yeah, it closes the root console bug. However, once you have root via adb, you can do pretty much anything you want, including create a new suid root shell.
yes thats all i need to know disregard my edit
it dose not work I'm stuck! i got some sort of error
It won't let me mount the SD card... gonna ask in the other thread
What was the error exactly? Did it come at the recovery screen when you first tried to update, or later? Is your phone still working?
rale00 said:
What was the error exactly? Did it come at the recovery screen when you first tried to update, or later? Is your phone still working?
Click to expand...
Click to collapse
Thanks for asking the error was 105, yes later, and yes
and this is what i did
THANK GOD!! for JesusFreke Restore Original RC29 Boot Image.zip. if what happened to me happens to anyone just rename that file up above to update and your golden.
Note: i used it and now i have
kila-user 1.0 TC4-RC30 116143
ota-rel-keys,release-keys
i dont understand... and i sill have root on my phone and busybox, and telnetd exploit still works
maybe i should try it again?
It sounds like the update partially completed for you, since it claims to be RC30, but it failed either sometime before or during the flash of the updated boot.img. boot.img has the fix for the telnetd exploit, which is why it's still working for you after restoring the RC29 version.
If you try to run the RC30 update again, it will probably fail, since some or all of your other files are already updated.
The bad news is, you probably won't be able to install any future updates with the state you're in now. What you probably want to do now is try to figure out how far along in the update script it failed.
If you can download the following files off your phone, and post them somewhere, I'll compare them to the versions in a completely updated RC30 and should be able to get a better idea of where you are.
/system/framework/android.awt.jar
/system/app/GoogleSearch.apk
/system/app/Bugreport.apk
What good thing i made a backup of my flash i am going to see if i can restore it using this methodhttp://forum.xda-developers.com/showthread.php?t=442831
but witch partitions should i flash? and is it a good idea
rale00 said:
/system/framework/android.awt.jar
/system/app/GoogleSearch.apk
/system/app/Bugreport.apk
Click to expand...
Click to collapse
how do i get them to the sdcard? i will post them
I can get root through adb shell after this, which is fantastic!
So I try this from adb shell:
cd /system/bin
echo sh > su
chmod 4755 su
But when I run su from the phone's terminal, I don't get a root shell. (reboot gives me a reboot: Operation not permitted.
Any ideas?
humble said:
What good thing i made a backup of my flash i am going to see if i can restore it using this methodhttp://forum.xda-developers.com/showthread.php?t=442831
but witch partitions should i flash? and is it a good idea
Click to expand...
Click to collapse
Oh, that's good news. If you have a backup of mtd3 / "system", then you should be able to just restore that and be in good shape.
rale00 said:
Oh, that's good news. If you have a backup of mtd3 / "system", then you should be able to just restore that and be in good shape.
Click to expand...
Click to collapse
thanks, but i wanna help out with those files. and do you know the exact commands to copy(i know cp and"???? ") and to restore mtd3
SORRY........
to restore is this right....
cat /dev/zero >> /dev/mtd/mtd3
flash_system /sdcard/mtd3.img
To copy them to sd card:
cat /system/framework/android.awt.jar > /sdcard/android.awt.jar
cat /system/app/GoogleSearch.apk > /sdcard/GoogleSearch.apk
cat /system/app/Bugreport.apk > /sdcard/Bugreport.apk
I haven't tried this, so I don't know if it works, but to restore system, if you backed it up using the directions in the other thread, should just be:
flash_image system /sdcard/mtd3.img
I wouldn't recommend cat /dev/zero to it first, because flash_image is actually on the system partition.
rale00 said:
To copy them to sd card:
cat /system/framework/android.awt.jar > /sdcard/android.awt.jar
cat /system/app/GoogleSearch.apk > /sdcard/GoogleSearch.apk
cat /system/app/Bugreport.apk > /sdcard/Bugreport.apk
I haven't tried this, so I don't know if it works, but to restore system, if you backed it up using the directions in the other thread, should just be:
flash_image system /sdcard/mtd3.img
Click to expand...
Click to collapse
Thanks rale00, when im finish if it works i'l post
Hello guys! the instructions are very easy if you do the steps correctly.
This is my first post in the development section.
First, go to market and download OTA Rootkeeper
Second, open the app, Select Create SU Backup.
Third, Select Temp UnRoot(with backup)
Fourth, uninstall Superuser, if you have superuser elite uninstall it also! and uninstall OTA Rootkeeper(dont worry it will not delete UR Backup!)
Fifth, Download and install the OTA.
After it is done and reboot, do a power cycle.
and the last step, go to market, install superuser and ota rootkeeper.
Launch OTA Rootkeeper and Select RestoreRoot, accept the superuser permission, and reboot!
AND ur back with rooted 2.3.6!
Michael
Alternate method! This is Jim's method(Thanks jim for this other way)
To do the 4ever root hack do the following:
1) open root explorer or ew file manager etc...
go to /system/bin
find the file named mount_ext3.sh
touch and hold the file name until the menu appears, go to open in text editor.
Add the following line to the VERY bottom of the file, after the fi
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 644 /system/app/Superuser.apk
2) SAVE!!!! the file.
3) Do the OTA update.
4) You should still have root after the update, now.
Jim
Enjoy, Hope this helps!
I missed step 3 and 4 this is why it did not work for me
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Zoide_ said:
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Click to expand...
Click to collapse
I don't know but as soon as I get home I'm going to check and see... Just got another A2 today, its going to be a good lil Guinea Pig... (insert evil grin here)
Sent from my MB865 using XDA App
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 644 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root. but if you did not do the update maually, and you used the one-click you might need to add the following line as well....
chmod 4755 /system/xbin/su
Jim
Zoide_ said:
Does this work if coming from SuperCharged V4, or only if coming from stock 2.3.5?
Thanks
Click to expand...
Click to collapse
cant tell you, i didnt had a custom rom on it while i tried but if i am correct the update will work with stock only. wait till Iggis Pop do the test before attempting.
I just used OTA Rootkeeper normally and it worked fine for me. Backed up root, temp un-rooted, downloaded and applied the update, then restored root from OTA Rootkeeper after the update finished. I have root back just fine...
Did this not work for others?
I must of did something wrong because this did not work for me. I followed the steps to a T and it didn't take.
Sent from my MB865 using xda premium
jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
be carefull, the update brings a new security environment and new security patches that google just released. the update over writes parts of the system data. the safest way that i tested is this method. be careful with ever root
jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
Jim,
I have a question about running a Deodexed rom. Will I have a problem upgrading or do I have to SBF back to stock? I also have the 1 percent mod that I love. How can I keep this. My understanding is this only works for deodexed roms.
tmease1 said:
I must of did something wrong because this did not work for me. I followed the steps to a T and it didn't take.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
can you tell me step by step what ou did so i can help you!
jimbridgman said:
The easier way to do this, is just do the 4ever root that was done for the bionic.
Just add these lines to the bottom of the /system/bin/mount_ext3.sh files with the text editor in root explorer, or through adb.
chmod 4755 /system/bin/su
chmod 444 /system/app/Superuser.apk
Do that BEFORE the OTA update, and you will not have any issues with OTAs ever again and loosing root.
Jim
Click to expand...
Click to collapse
x2 I used this method and it works fine. No messing around with OTA rootkepper, no need to uninstall superuser/etc.
Michael443 said:
be carefull, the update brings a new security environment and new security patches that google just released. the update over writes parts of the system data. the safest way that i tested is this method. be careful with ever root
Click to expand...
Click to collapse
ever root is arguably SAFER than your method. All it does is make the system change the permission on the files on every bootup. It's not rocket science.
09CarreraS said:
Jim,
I have a question about running a Deodexed rom. Will I have a problem upgrading or do I have to SBF back to stock? I also have the 1 percent mod that I love. How can I keep this. My understanding is this only works for deodexed roms.
Click to expand...
Click to collapse
I'm not Jim but I do have the answers to your questions!
You should flash the fkz's (sbf) files before you update, just a good idea to remove any oddities or potential problems. Also most modifications do relay on a deodexed ROM , so my guess is that it won't work with the new update yet. My personal recommendation would be to wait until lfaber06 incorperates this update into a nice little cwm flashable zip (around this weekend, or next), that will already contain root, as well as the 1 percent mod and the updated theming!
Thanks for the answer! Hey I'm from Ma as well.
well that's what i get for not reading here first. My coworker was demo-ing an app to our CEO and the update notification came in. A few minutes later he comes back and says he hit download then install when it came up. When i got it it was flashing in recovery already
extide said:
x2 I used this method and it works fine. No messing around with OTA rootkepper, no need to uninstall superuser/etc.
ever root is arguably SAFER than your method. All it does is make the system change the permission on the files on every bootup. It's not rocket science.
Click to expand...
Click to collapse
Well, this definitely bricked my phone.
toastthemost said:
Well, this definitely bricked my phone.
Click to expand...
Click to collapse
Are you sure you followed the instructions and put the files in the right directory? I havn't had any problems using this exact method as for a few others.
No way if it was done correctly that it bricked your phone.correctly can be accomplished by navigating to the proper file then copy pasting the code in order.the only thing you are modifying is superuser.
toastthemost said:
Well, this definitely bricked my phone.
Click to expand...
Click to collapse
You probably edited the ext3 mount script incorrectly then, that could easily softbrick the phone.
extide said:
You probably edited the ext3 mount script incorrectly then, that could easily softbrick the phone.
Click to expand...
Click to collapse
Not sure, I just pasted those two lines under "fi" or whatever was on the last line. Checked it. Saved it. Rebooted. Boot loop.
Hello,
This is a new root method.
This is a linux / OSX version only for now.
When you untar the file. Please make sure to edit the runme.sh it has a path for adb that you need to fix. Other then that it will work.
You just chmod 755 runme.sh and run it
[COLOR="Red"]Mod Edit: removed link[/COLOR]
EDIT: This has been confirmed working on the TF201 and TF101 so its a Universal root for all transformers
EDIT: Adding a step by step guide here.
A) Install an app from market any app. (I choose rootchecker)
B) Open the app-draw and select the asus backup utility and backup rootchecker
C) follow the scripts instructions
D) When it asks you to do another backup. Go into the backup utility from the TF101/TF201 (from the app-draw) go to back and RE-BACKUP the SAME app (Rootchecker in my case)
E) The system will reboot and you will have root. Do this all while the script is running. It will pause and ask you do the above items.
Thanks!
Reserved for later
well adapted it to windows in case anyone needs it
Just extract the zip file, execute the run.bat and follow the onscreen instructions.
chan32167 said:
well adapted it to windows in case anyone needs it
Just extract the zip file, execute the run.bat and follow the onscreen instructions.
Click to expand...
Click to collapse
Both you and the OP are legends. worked like a charm.
THANK YOU
bungknees said:
Both you and the OP are legends. worked like a charm.
THANK YOU
Click to expand...
Click to collapse
Thanks............
I'm already rooted, but I like the technique- it's quite clever and a wonderful hack.
I don't recall there ever being so many root exploits for a single device. It's like a tablet with a free puzzle that keeps giving. People are going to start buying the TF just to root it.
I tried another way to root but when i rebooted i have cwm 3101 and su which updated but not the binaries. When i try anything its telling me i don't have root access.
Now when i try to rerun it or this it hangs right at waiting for device in the beginning. Any thoughts?
Windows 7 x64 machine
B50
frankwhite8536 said:
I tried another way to root but when i rebooted i have cwm 3101 and su which updated but not the binaries. When i try anything its telling me i don't have root access.
Now when i try to rerun it or this it hangs right at waiting for device in the beginning. Any thoughts?
Windows 7 x64 machine
B50
Click to expand...
Click to collapse
Dont know much about windows sorry. I used my method here to root on ICS. Started from stock -> Ota X 3 or 4 then root.
so this will root the official update? if so, i may be interested, but i need to know what kernel version is included in the official FOTA package. if it's still 2.6, i won't bother
sarreq said:
so this will root the official update? if so, i may be interested, but i need to know what kernel version is included in the official FOTA package. if it's still 2.6, i won't bother
Click to expand...
Click to collapse
Yes, This roots the current OTA as stated in the OP / Thread Topic
but what kernel version is in the FOTA?
sarreq said:
but what kernel version is in the FOTA?
Click to expand...
Click to collapse
2.6.39.4-00002
Neptune #1
sarreq said:
but what kernel version is in the FOTA?
Click to expand...
Click to collapse
Kernel is 2.6.39
rhcp0112345 said:
Dont know much about windows sorry. I used my method here to root on ICS. Started from stock -> Ota X 3 or 4 then root.
Click to expand...
Click to collapse
Thanks. I was able to flash this
http://forum.xda-developers.com/showthread.php?t=1334673
And I'm working as god intended.
frankwhite8536 said:
Thanks. I was able to flash this
http://forum.xda-developers.com/showthread.php?t=1334673
And I'm working as god intended.
Click to expand...
Click to collapse
Nice, Good
frankwhite8536 said:
2.6.39.4-00002
Neptune #1
Click to expand...
Click to collapse
rhcp0112345 said:
Kernel is 2.6.39
Click to expand...
Click to collapse
thank you both.
you'd think they would've updated that, since ICS proper is supposed to run on a 3.x kernel.
so, will a honeycomb CIFS.KO work with the FOTA? or is there an ICS specific CIFS module somewhere out there? / nevermind, found it here nope, wrong again, that's for the tfprime, and causes a bootloop when it loads. i guess we have to wait for one to be ported, then?
update: resolved. Didn't know about the App Backup Utility
Worked as promised. Remember you must run the Asus Backup Utility twice!
rhcp0112345 said:
This is a linux / OSX version only for now.
When you untar the file. Please make sure to edit the runme.sh it has a path for adb that you need to fix. Other then that it will work.
You just chmod 755 runme.sh and run it
http://www.mrcellphoneunlocker.com/V2/tf101_ics_root.tar.gz
Click to expand...
Click to collapse
Great job! thanks
tomdot said:
update: resolved. Didn't know about the App Backup Utility
Worked as promised. Remember you must run the Asus Backup Utility twice!
Click to expand...
Click to collapse
what's this utility? never seen it before
WOrks!
Working Perfectly.
This applies the 9.2.1.21 US ota update. It will install Superuser and the su and busybox binaries; and set ro.secure=0. It does not modify recovery at all.
As usual, flash at your own risk- I didn't test this.
To flash, you need:
a non-stock recovery
a stock system, rooted is OK
custom kernels, deleted system files, modified build.props or audio files will FAIL.
Good luck!
edit: new url! Find it in the OTA section.
http://www.xdafileserver.nl/geeone/
MD5(gee_one-cwm-9.2.1.21-US.zip)= 30bf3ad60698d41793d992823e942076
I made this with Ubuntu!
Thanks to doaist for paving the way! and thanks to Korumera for the server space!
Edit:
It seems like some people will "lose" root in titanium backup because it looks for the su binary in /system/bin instead of /system/xbin (X!). See post 19 and 20 for how to get it back. I don't use titanium backup very often, so I'm not familiar with it.
I get a status 7 installation aborted error when trying to flash on the stock rom thats rooted no mods.
Thanks
Worked fine on my TF101 US....
Hope it fixes some of the battery issues I've been seeing with .17
Hmmmm.............strange it didnt for me and Im on the stock ICS rom ver .17 currently.
I'm not sure what status 7 is. How much free space do you have? I don't remember the number but the patch does check free space before flashing.
sent while running with scissors
Ive got 20gigs of free space Im using Rogue Recovery............not sure if that makes a difference.......
20 gbs on the sdcard? I think it checks internal memory, or maybe you have a 32gb transformer?
sent while running with scissors
Error Im getting:
Verifying current system....
assert failed: apply_patch_check("/system/lib/modules/battery_rvsd.ko", "66c516b01d95c36310cc3e7ee7771b32ed5cb823",
E: Error in/sdcard/gee_one-cwm-9.2.1.21-US_30bf3ad606.zip
(Status 7)
Installation aborted.
---------- Post added at 04:00 PM ---------- Previous post was at 03:59 PM ----------
Ive got a 32gb transformer with a 32gb microsd card.
For whatever reason, your battery kernel module is different? Maybe you changed it while sleeping or maybe the 32gb version uses a different one.
The US firmware is available on the asus site, so you could just download it, extract the offending file, and push it to your transformer. It will be the 92121 version, but the updater will just skip it since it matches the target.
sent while running with scissors
Could it be because Im not using a stock kernel?
y2kardell said:
Could it be because Im not using a stock kernel?
Click to expand...
Click to collapse
Bingo- see the note about FAIL in the first post. You'll want to flash back to a stock kernel to apply the update, or more likely, just flash a full custom rom and a new modded kernel.
sent from my transformer
I no longer have root after I flashed this.
Any suggestions?
kdog78 said:
I no longer have root after I flashed this.
Any suggestions?
Click to expand...
Click to collapse
are you sure you flashed my version and not the other one?
type in "ls -l /system/xbin/su" and "getprop ro.secure" in the terminal and see what pops up.
Ok, I tested this on my TF and it works for me, your experience may differ.
Try updating Superuser and the su binary in superuser. Maybe I have an updated version on /data/app?
sent from my transformer
I flashed this and after I click reboot system now it just gets stuck at CWM.
I'm using CWM v3.2.0.1 by roach2010
Tried clearing cache, it still gets stuck in CWM. Help?
wzseow said:
I flashed this and after I click reboot system now it just gets stuck at CWM.
I'm using CWM v3.2.0.1 by roach2010
Tried clearing cache, it still gets stuck in CWM. Help?
Click to expand...
Click to collapse
That is a recovery issue - there is a trouble shooting thread in the dev section.
sent from my transformer
gee one said:
are you sure you flashed my version and not the other one?
type in "ls -l /system/xbin/su" and "getprop ro.secure" in the terminal and see what pops up.
Click to expand...
Click to collapse
It had a 0.
Sent from my Transformer TF101 using Tapatalk 2
can anyone advice on how to get this to flash on a system with a custom kernel? i can't seem to get it to flash with error 7
Sent from my Transformer TF101 using Tapatalk 2
kdog78 said:
It had a 0.
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Sorry to answer your earlier question, yes I used yours. I didn't know there was another. Here are two screen shots.
Sent from my Transformer TF101 using Tapatalk 2
It looks like you have 2 su binaries, and the one ti backup is looking for isn't superuser executable.
Try ls -l /system/*bin/su and this time use the -l flag to check the permissions. The bin/su will be normal, but the xbin one should be rws....
Try this in terminal
/system/xbin/su
mount -o remount,rw /system
chmod 06755 /system/bin/su
mount -o remount,ro /system
Exit...exit...
Then try getting root in tibu. I don't use it, so I'm not terrible familiar. You might also try updating the su binary via superuser apk.
sent while running with scissors
okay so i stumbled across the idea of getting my atrix 2 rooted,
so i finally get all the drivers installed that i needed for adb to recognize the phone and then this happens, saying permission denied, not quite sure what is happening
also i have a picture of what it says exactly which i can send to you if that would further help,
any help at all would be much appreciated!
kiwibro92 said:
okay so i stumbled across the idea of getting my atrix 2 rooted,
so i finally get all the drivers installed that i needed for adb to recognize the phone and then this happens, saying permission denied, not quite sure what is happening
also i have a picture of what it says exactly which i can send to you if that would further help,
any help at all would be much appreciated!
Click to expand...
Click to collapse
Which method to root are you using, and which firmware/software version is you device currently running, and lastly do you have USB Debugging enabled on your device?
Apex_Strider said:
Which method to root are you using, and which firmware/software version is you device currently running, and lastly do you have USB Debugging enabled on your device?
Click to expand...
Click to collapse
the method i tried is MOTO_4.0.4_ROOT_V5 and it's currently running 4.0.4 and yes indeed i do.
kiwibro92 said:
the method i tried is MOTO_4.0.4_ROOT_V5 and it's currently running 4.0.4 and yes indeed i do.
Click to expand...
Click to collapse
don't know if this is of any help but it might,
Root Access is not properly configured or was not granted.
Super User Applications Status:
Superuser application - is NOT installed!
The Superuser application, available in the Android Market, is recommended for managing root access.
SuperSU application - is NOT installed.
The SuperSU application is an alternative application for managing root access.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
I have got the same problem as you but someone answered my question.he said:
For my best understanding, 67.220.3.en05 is only available from the HKTW OTA update up to now (SBF is not available), which is known that it's not able to be rooted at this moment (except replacing the boot.img with the ASIA RETAIL version)
Sent from my ME865 using xda premium
thanks, guess i wont be rooting my phone then
sunnytse1 said:
I have got the same problem as you but someone answered my question.he said:
For my best understanding, 67.220.3.en05 is only available from the HKTW OTA update up to now (SBF is not available), which is known that it's not able to be rooted at this moment (except replacing the boot.img with the ASIA RETAIL version)
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
Yeah,it's too bad
Sent from my ME865 using xda premium
a new phone it is then, haha.
sunnytse1 said:
Yeah,it's too bad
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
sunnytse1 said:
For my best understanding, 67.220.3.en05 is only available from the HKTW OTA update up to now (SBF is not available), which is known that it's not able to be rooted at this moment (except replacing the boot.img with the ASIA RETAIL version)
Click to expand...
Click to collapse
Can you please check if /data/local/12m exists (and writable)? All these moto ICS root scripts depends on this vulnerability: http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/ Would like to know if HKTW does things differently.
i tried accessing it via the computer and also through my phone using root explorer, but to access that folder says my phone needs to be rooted, so no luck, how do i go about flash the asia retail .img will that make any difference ?
kousik said:
Can you please check if /data/local/12m exists (and writable)? All these moto ICS root scripts depends on this vulnerability: http://vulnfactory.org/blog/2011/08/25/rooting-the-droid-3/ Would like to know if HKTW does things differently.
Click to expand...
Click to collapse
kiwibro92 said:
i tried accessing it via the computer and also through my phone using root explorer, but to access that folder says my phone needs to be rooted, so no luck, how do i go about flash the asia retail .img will that make any difference ?
Click to expand...
Click to collapse
You can flash the ME 865 China Retail using rsdlite..its rootable
thanks! sorry, but where abouts do i get the latest version from ? if not are there any other version that will work on this phone or will all version work ?
another question, sorry! am i able to use a custom rom to flash it then root ?
devilhunter47 said:
You can flash the ME 865 China Retail using rsdlite..its rootable
Click to expand...
Click to collapse
UPDATE: attempted to download the china retail but it's not allowing me to register to be able to download it, so any other options ?
kiwibro92 said:
thanks! sorry, but where abouts do i get the latest version from ? if not are there any other version that will work on this phone or will all version work ?
another question, sorry! am i able to use a custom rom to flash it then root ?
UPDATE: attempted to download the china retail but it's not allowing me to register to be able to download it, so any other options ?
Click to expand...
Click to collapse
Download from here
http://pan.baidu.com/share/link?shareid=5145&uk=3473189901
so i finally get around to flashing it and now the phone keeps crashing, awesome!
help please!
UPDATE:
managed to flash to the asia retail version, anyone point me in the right direction as to what's best to root the phone, please!
update 2: tried rooting the asia retail no luck, still saying permission denied, going to try downloading the china retail again even though it was crashing, maybe i had a faulty download, not sure!
kiwibro92 said:
so i finally get around to flashing it and now the phone keeps crashing, awesome!
help please!
UPDATE:
managed to flash to the asia retail version, anyone point me in the right direction as to what's best to root the phone, please!
update 2: tried rooting the asia retail no luck, still saying permission denied, going to try downloading the china retail again even though it was crashing, maybe i had a faulty download, not sure!
Click to expand...
Click to collapse
update 3: okay so i managed to flash china retail again, it keeps crashing and sometimes it even just hangs on the motorola logo, can anyone please point me in the direction of a rom or something that will work, the asia retail flashes and works properly but has the same problem as the hktw folder access is restricted. :/
kiwibro92 said:
update 3: okay so i managed to flash china retail again, it keeps crashing and sometimes it even just hangs on the motorola logo, can anyone please point me in the direction of a rom or something that will work, the asia retail flashes and works properly but has the same problem as the hktw folder access is restricted. :/
Click to expand...
Click to collapse
Were you able to resolve the issues? I also have 67.220.3.en05 and I'm uncertain about flashing the china retail...
http://bbs.angeeks.com/forum.php?mo...lter=author&orderby=dateline&orderby=dateline
Try this.if you can understand chinese
Sent from my ME865 using xda premium
I found using the china retail I ran into a multitude of crashes, I can provide the right one I found worked perfectly when I get on the computer,
Sent using xda app-developers app
hunpgod said:
Were you able to resolve the issues? I also have 67.220.3.en05 and I'm uncertain about flashing the china retail...
Click to expand...
Click to collapse
flash it with this, it's asia retail, it roots perfectly fine. - http://sbf.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
then enable usb debugging through developer options in settings and connect usb.
and use this root by jim, http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip
kiwibro92 said:
flash it with this, it's asia retail, it roots perfectly fine. - http://sbf.droid-developers.org/edison/6.7.2_EDEM-18-SEARET_cfc.xml.zip
then enable usb debugging through developer options in settings and connect usb.
and use this root by jim, http://www.androidfilehost.com/main/Motorola_ATRIX_2_Developers/jimbridgman/A2_ICS_root.zip
Click to expand...
Click to collapse
Thanks
I flashed it. Everything seems to be ok, root worked as well.