Hi all!
Was about to purchase a Nexus 7 when I saw a huge discount on the Asus TF101 and decided to take it. How I have a it in front of me proudly informing it has the firmware revision IML74K.WW_epad-9.2.1.27-20120615. BTW, the s/n starts with B50 if it matters.
And now what? Wait for the official JB or root it right now? I usually root all my devices at least to have nandroid + TiBu, even if I don't plan to install any alternative FW.
The problem is it's an ICS 4.0.3 with the problem to enter into recovery mode and I have only a Mac computer, no Windows and no Linux machines around. I read the threads and see every time the Windows tools, nothing for Mac. No root from SD card neither.
Any advice how to root using the Transformer itself or my Mac? And any advice regarding best JB ROM or at least best kernel for stock 4.0.3 ROM with exFAT support? I don't use NTFS because my Macs can't write on and old FAT16 has the famous 4 Gb limit, not good for the movies.
Many thanks in advance.
You could try and install Windows on your Mac to essentially have a dual boot of both OS's. Or you could use something like VMWare (I think that's what it is but I'm like 5% sure) which allows you to run windows without necessarily installing it. Anyway, I suggest, if you can, to go ahead and root your device and install a JB ROM like EOS or CM10 or something.
If it's not possible to do Android modifications on a Macintosh it looks like your only option would be to setup a dual boot with Linux to do your Android Rooting and ROM flashing since I would imagine you would want to avoid having to use Windows for this It would be better to avoid virtual machines to do device modifications and just stick to the dual boot option since support for USB devices is iffy in virtual machines.
Hi all,
Shmi117 said:
You could try and install Windows on your Mac to essentially have a dual boot of both OS's.
Click to expand...
Click to collapse
No chance! I don't like to spend hours installing Windows and all this stuff again !!! :crying:
WCL1990 said:
If it's not possible to do Android modifications on a Macintosh it looks like your only option would be to setup a dual boot with Linux to do your Android Rooting and ROM flashing since I would imagine you would want to avoid having to use Windows for this It would be better to avoid virtual machines to do device modifications and just stick to the dual boot option since support for USB devices is iffy in virtual machines.
Click to expand...
Click to collapse
Basically what Linux can to Mac OS X can do. At least regarding adb and the command line use. The problem is I have found tons of good information about how to do it using Windows, but nothing for Linux nor Mac.
OK, here is the answer. One can root the Asus Eee Pad Transformer TF101 using Mac OS X only!
Developing in next message...
OK, here is the solution. :fingers-crossed:
First of all, I presume the Android SDK for Mac OS X is installed and upgraded.
Next, on the Transformer please go to Settings -> Developer options and activate the USB debugging. Finally, please check this forum thread and download the latest version of PERI. Yes, PERI for Windows 0.4 as of today. Please unzip the downloaded file.
No sorcery or black magic here, I've just learned from the bat file and tried to reproduce the whole procedure manually using adb.
Most Linux users will smile, but I will show the commands the way most Mac OS X user will need to input them. Basically, you don't really know that the shell path is and what "finally add adb to your path" means, right?
1. OK, please open the Finder and go to the directory where the adb executable lives. Something like ~/Downloads/android_sdk/android-sdk-macosx/platform-tools/.
2. Now please open the Terminal.app inside Application/Utilities folder and go to the same directory.
3. Please connect the Transformer to the Mac using the USB cable.
4. First of all, let's see if adb sees the Transformer. Please input
Code:
./adb devices
If everything is OK, you'll see something like this:
Code:
List of devices attached
024640c082db4561 device
5.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/recoveryblob /sdcard/
Basically you input ./adb push, drag the a.m. file and next input /sdcard/
6.
Code:
./adb shell mv /data/local/tmp /data/local/tmp.bak
7.
Code:
./adb shell exit
8.
Code:
./adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
9.
Code:
./adb reboot
Wait while the Transformer reboots.
10.
Code:
./adb shell dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
11.
Code:
./adb shell exit
12.
Code:
./adb reboot
Wait while the Transformer reboots.
13.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/Superuser-3.0.7-efghi-signed.zip /sdcard/
See #5.
14.
Code:
./adb reboot
Wait while the Transformer reboots.
15. Now please shut down the Transformer manually and boot into recovery. Please hold Power + Volume Down buttons and next confirm with Volume Up button when asked. Rogue XM recovery will boot.
16. Wipe cache, wipe Dalvik cache, next choose Install zip file from internal storage and choose the Superuser-3.0.7-efghi-signed.zip.
17. When it's done, reboot.
18. PROFIT. :good: Your device is rooted with Rogue XM recovery installed.
From there I suggest to install SuperSU and eventually SuperSU Pro as it seems to work better than Superuser and Superuser Elite respectively. You can eventually get rid of Superuser if you wish so, instructions available in this forum thread. As I own both SuperSU Pro and Superuser Elite, I've installed SuperSU and upgraded Superuser, just in case of. You should not mix them, though, thus I've revoked the root permission of Superuser.
Next I've installed Busybox. I don't know if it's the best version for TF101, works well on my GNote.
Finally, let's play with the recovery options courtesy of some awesome developers. :good: We can choose among Rogue XM Touch, CWM classic, CWM 6.x and official or modified TWRP. I've chosen the official TWRP with GooManager.
Next stop, Titanium Backup.
Should you have other recommendations, please do not hesitate.
Thanks a lot friend. I used the same procedure to root my TF101 using Ubuntu Are you using any Customised ROM ? I am using CM10 based ROM built by RaymanFX and it is simply awesome
iLearner said:
OK, here is the solution. :fingers-crossed:
First of all, I presume the Android SDK for Mac OS X is installed and upgraded.
Next, on the Transformer please go to Settings -> Developer options and activate the USB debugging. Finally, please check this forum thread and download the latest version of PERI. Yes, PERI for Windows 0.4 as of today. Please unzip the downloaded file.
No sorcery or black magic here, I've just learned from the bat file and tried to reproduce the whole procedure manually using adb.
Most Linux users will smile, but I will show the commands the way most Mac OS X user will need to input them. Basically, you don't really know that the shell path is and what "finally add adb to your path" means, right?
1. OK, please open the Finder and go to the directory where the adb executable lives. Something like ~/Downloads/android_sdk/android-sdk-macosx/platform-tools/.
2. Now please open the Terminal.app inside Application/Utilities folder and go to the same directory.
3. Please connect the Transformer to the Mac using the USB cable.
4. First of all, let's see if adb sees the Transformer. Please input
Code:
./adb devices
If everything is OK, you'll see something like this:
Code:
List of devices attached
024640c082db4561 device
5.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/recoveryblob /sdcard/
Basically you input ./adb push, drag the a.m. file and next input /sdcard/
6.
Code:
./adb shell mv /data/local/tmp /data/local/tmp.bak
7.
Code:
./adb shell exit
8.
Code:
./adb shell ln -s /dev/block/mmcblk0p4 /data/local/tmp
9.
Code:
./adb reboot
Wait while the Transformer reboots.
10.
Code:
./adb shell dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
11.
Code:
./adb shell exit
12.
Code:
./adb reboot
Wait while the Transformer reboots.
13.
Code:
./adb push /Users/YOURUSERNAME/Downloads/OneclickrecoveryV0.4/Superuser-3.0.7-efghi-signed.zip /sdcard/
See #5.
14.
Code:
./adb reboot
Wait while the Transformer reboots.
15. Now please shut down the Transformer manually and boot into recovery. Please hold Power + Volume Down buttons and next confirm with Volume Up button when asked. Rogue XM recovery will boot.
16. Wipe cache, wipe Dalvik cache, next choose Install zip file from internal storage and choose the Superuser-3.0.7-efghi-signed.zip.
17. When it's done, reboot.
18. PROFIT. :good: Your device is rooted with Rogue XM recovery installed.
From there I suggest to install SuperSU and eventually SuperSU Pro as it seems to work better than Superuser and Superuser Elite respectively. You can eventually get rid of Superuser if you wish so, instructions available in this forum thread. As I own both SuperSU Pro and Superuser Elite, I've installed SuperSU and upgraded Superuser, just in case of. You should not mix them, though, thus I've revoked the root permission of Superuser.
Next I've installed Busybox. I don't know if it's the best version for TF101, works well on my GNote.
Finally, let's play with the recovery options courtesy of some awesome developers. :good: We can choose among Rogue XM Touch, CWM classic, CWM 6.x and official or modified TWRP. I've chosen the official TWRP with GooManager.
Next stop, Titanium Backup.
Should you have other recommendations, please do not hesitate.
Click to expand...
Click to collapse
Thanks, that worked nicely for me!
One thing I can't figure out yet, though, is how to do a backup - the microsd card doesn't mount at /sdcard/ and backing up to internal storage is not recommended...
Wheelie
Hi!
A linux only solution for B70(+) devices can be found here:
http://androidroot.mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/
It is what I used twice so far. Works as it should.
I do not claim credit for anything! I just stumbled upon the solution.
Problem rooting
Hi,
this is my first post on XDA.
After a lot of readings here, I think I have tried everything I could, but my knowledge in rooting is too limited to understand these bugs:
At first, when I tried running these lines on the terminal, I couldn't push the files to /data/local: permission denied.
Then, I tried pushing to /sdcard/ and it worked.
But the next error I get is when linking:
"link failed Function not implemented"
Can you help me please?
My computer is a Mac, so I have tried you method first. I also tried on my Parallel Desktop with Windows 8 and on the PC with Windows 8.1 of my girlfriend, with RootDebugFs.
Here is the description of my Infinity pad:
model: ASUS Transformer Pad TF700T
Android: 4.2.1
Kernel: 3.1.10-g9827b9a, [email protected] #1
Build: JOP40D.WW_epad-10.6.1.14.8
I had the build 14.10 but I found that I should downgrade to 14.8, so I did, but nothing changed.
I also unlocked my tablet by mistake, thinking it would help rooting.
Thanks for your help.
Best,
Yohan.
Just did this!!! Still works!!! Followed your steps. Now the recovery is TWRP 2.5!!! As the peri version changed I checked if the .bat was still doing the same things, and it is!!
Thanks for your tuto! Saved me some time installing W**** ...
Hi guys, i tried to root Bluestacks Apps Player Beta for Mac OS X on Windows by using a method similar to the one used to root BS for Windows.
But unfortunately i am not able to test the modded files as i do not actually own a Mac OS X device, and i am not familiar with the OS either.
So i am asking, any volunteer here willing to help me test this experimental modded files?
How to use
1) Download BlueStacks AppPlayer Beta .dmg for Mac OS X & install it.
2) Download modded files provided below, make sure the targeted version is same as your installed version.
3) Extract the downloaded zip and use the modded files to replace the following folders:
Code:
~/Library/BlueStacks App Player/Android/Root.sparsefs/
~/Library/BlueStacks App Player/Android/Prebundled.sparsefs/
~/Library/BlueStacks App Player/Android/Data.sparsefs/
~/Library/BlueStacks App Player/Android/SDCard.sparsefs/
Downloads & Changelogs:
Code:
[URL="http://goo.gl/wJYSR"][SIZE="3"]BSRoot_0.3.6.102d.zip[/SIZE][/URL] (99.88 MB, Pass: [COLOR="Red"][email protected][/COLOR], Last Update: [COLOR="Red"]03/04/2013[/COLOR])
~ Target: BlueStacks for Mac OS X v[URL="http://goo.gl/ILhtK"]0.3.6.102[/URL] Only (Released: 21/03/2013)
+ Allow /system rw
+ su (standalone/on the fly)
+ Google Play v3.10.14
+ Google Contacts/Calendar Sync
+ Flash Player v11.1
+ Holo Launcher v2.0.2 Free
+ Terminal Emulator v1.0.52 OS
- Most bloatware
Notes:
- By replacing above folders, your existing settings & data will be gone, you are advised to create a backup before trying the mod.
* Please note that all version prior to the 03/04/2013 update probably will not work, try the latest version.
* If you tried please at least COME BACK TO VOTE so that i can know how it goes. Thank you!
-Reserved-
I think this worked, still trying to find a way to test the "rooted-ness" of it. Do you know where bluestacks puts the apps it installs from the market? /data seems to be empty.
---------- Post added at 04:58 PM ---------- Previous post was at 04:41 PM ----------
typing su into terminal gets me a segmentation fault
SuperSu hangs or doesn't run.
ESFile Explorer can't use it's "root" features. (Test Fails)
efdisastet said:
I think this worked, still trying to find a way to test the "rooted-ness" of it. Do you know where bluestacks puts the apps it installs from the market? /data seems to be empty.
typing su into terminal gets me a segmentation fault
SuperSu hangs or doesn't run.
ESFile Explorer can't use it's "root" features. (Test Fails)
Click to expand...
Click to collapse
Hi, Thanks for the feedback.
Without SuperSU working properly, terminal is running as app user thus you will not be able to view contents of /data/ as the folder is owned by 'system'.
Not sure why SuperSU is not working. Anyway, I have updated the files to use Superuser 3.2 instead of SuperSU, now with the updated files,
Superuser can be uninstalled easily, and if the superuser still causing problem, try uninstall it & run su without the apk installed.
Appreciate if you can retry the new file & also provide me the output for 'mount'. Thank you.
codelover said:
Hi, Thanks for the feedback.
Without SuperSU working properly, terminal is running as app user thus you will not be able to view contents of /data/ as the folder is owned by 'system'.
Not sure why SuperSU is not working. Anyway, I have updated the files to use Superuser 3.2 instead of SuperSU, now with the updated files,
Superuser can be uninstalled easily, and if the superuser still causing problem, try uninstall it & run su without the apk installed.
Appreciate if you can retry the new file & also provide me the output for 'mount'. Thank you.
Click to expand...
Click to collapse
Superuser app opened, but then closed on its own before I could check the settings.
I cleared data and then it seemed to stay open, so that I can go through the settings.
here's the result of su (still Segmentation fault)
and then mount
(sorry that it's a picture, copy seems to be an option, but can't find a way to paste.)
why does xda resize the pictures so small?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Re: [Emulator][BlueStacks Beta for Mac] Getting root access - Testers wanted
Would love to try this, codelover, but am wondering if you are testing in your own environment first, or are you expecting us to QA it? Don't get me wrong... I really appreciate you taking the lead on this, I just need to understand what my effort and interest level need to be. Thanks.
Sent from my SAMSUNG-SGH-I317 using xda premium
efdisastet said:
Superuser app opened, but then closed on its own before I could check the settings.
I cleared data and then it seemed to stay open, so that I can go through the settings.
here's the result of su (still Segmentation fault)
and then mount
Click to expand...
Click to collapse
Thanks! Now i know that /system can be mounted rw, one step forward. Next step is to find a working copy of su then we are done.
Can you confirm the Segmentation fault still appear after the apk been removed/uninstalled? One more thing, can you test run su after cd to /sdcard?
Just checked the alpha root by @bitstra, looks like they faced the same problem with superuser apk, so they have su working alone without the apk, maybe i will get you a copy of the su to test.
Btw do you have adb for Mac? Might need it to push su to BS for testing.
meatlocker said:
Would love to try this, codelover, but am wondering if you are testing in your own environment first, or are you expecting us to QA it? Don't get me wrong... I really appreciate you taking the lead on this, I just need to understand what my effort and interest level need to be. Thanks.
Click to expand...
Click to collapse
Hi meatlocker, Thank you for your interest. The answer is no, i have no chance to test it because i do not actually own a Mac.
But i have been working with BS for Windows for months that i am pretty sure Mac version can be rooted too.
I am just trying to help, it's really up to Mac users effort if they really want to see it get rooted.
The more feedback the faster it can be done. If i got a Mac that would be easier since i got several test cases that i can run on my own.
For now, everything is based on my assumption.
codelover said:
Thanks! Now i know that /system can be mounted rw, one step forward. Next step is to find a working copy of su then we are done.
Can you confirm the Segmentation fault still appear after the apk been removed/uninstalled? One more thing, can you test run su after cd to /sdcard?
Just checked the alpha root by @bitstra, looks like they faced the same problem with superuser apk, so they have su working alone without the apk, maybe i will get you a copy of the su to test.
Btw do you have adb for Mac? Might need it to push su to BS for testing.
Click to expand...
Click to collapse
yup, I've got adb installed and it see bluestacks, haven't tried to run any commands or anything
still get the Segmentation Fault and never get a typical su request popup for any app.
uninstalled superuser.
tried su in terminal, still Segmentation fault
installed SuperSu from play store
same results... app didn't run very well... tried to update itself and failed.
uninstalled
installed superuser (3.1.3?) from the Play store
took some screenshots (looked kinda hopeful?)
still same errors in terminal, no access to /data
efdisastet said:
installed SuperSu from play store
same results... app didn't run very well... tried to update itself and failed.
uninstalled
installed superuser (3.1.3?) from the Play store
took some screenshots (looked kinda hopeful?)
still same errors in terminal, no access to /data
Click to expand...
Click to collapse
You cannot install Superuser/SuperSU directly from market because it will install an arm version of the binary instead of the x86 that we need.
Now we need to identify which su binary version works with BS for Mac.
Please download the attached su-test.zip that contains various versions of su, extract to adb folder and then run the following commands:
Code:
adb push su-test /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su*
adb shell /data/local/tmp/su-3.1-x86 -v
adb shell /data/local/tmp/su-3.1.1-x86 -v
adb shell /data/local/tmp/su-3.2-x86 -v
adb shell /data/local/tmp/su-bin-3.1 -v
adb shell /data/local/tmp/su-1.25 -v
adb shell /data/local/tmp/su.x86 -v
adb shell /data/local/tmp/su.orig -v
* Also try to run above su without -v
We are expecting su to returns a version number or 'permission denied' message from a working copy, instead of segmentation fault.
Please let me know which version works. I think we can finalize this soon. Thank you again.
Re: [Emulator][BlueStacks Beta for Mac] Getting root access - Testers wanted
Also, how can we get into the contents of the Android disk image files on a Mac to extract android files, etc?
And how much space do we have in the simulated Android to install apps?
Code:
adb push su-test /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su*
adb shell /data/local/tmp/su-3.1-x86 -v
[COLOR="Red"]returned 3.1[/COLOR]
adb shell /data/local/tmp/su-3.1.1-x86 -v
[COLOR="red"]returned Segmentation fault[/COLOR]
adb shell /data/local/tmp/su-3.2-x86 -v
[COLOR="red"]returned Segmentation fault[/COLOR]
adb shell /data/local/tmp/su-bin-3.1 -v
[COLOR="red"]hung[/COLOR]
adb shell /data/local/tmp/su-1.25 -v
[COLOR="red"]hung[/COLOR]
adb shell /data/local/tmp/su.x86 -v
[COLOR="red"]returned Segmentation fault[/COLOR]
adb shell /data/local/tmp/su.orig -v
[COLOR="red"]returned su: permission denied[/COLOR]
* Also try to run above su without -v
[COLOR="red"]same results as above except that I got Segmentation fault on the ones that hung with -v[/COLOR]
efdisastet said:
Code:
adb shell /data/local/tmp/su-3.1-x86 -v
[COLOR="Red"]returned 3.1[/COLOR]
.....
adb shell /data/local/tmp/su.orig -v
[COLOR="red"]returned su: permission denied[/COLOR]
Click to expand...
Click to collapse
Definately a good news! I will try to rebuild Root.sparsefs to include both working copies of su-3.1 & su.orig.
But if i am not mistaken su.orig only works alone thus not supporting Superuser apk for confirmation.
EDIT: Files updated, download HERE.
CHANGES: Using su.orig copy without any Superuser apk.
NOTE: Might need to replace all new .sparsefs files instead of just Root.sparsefs.
Kinda weird as all su in su-test can run in BS for Windows except su.orig that returned Seg. fault.
Anyway, hope to hear some good news soon.
I replaced the files and kill Bluestacks, then I re-open Bluestacks .... NOTHING HAPPENED, my data and apps still there, and NO ROOT. Why?
nudawa said:
I replaced the files and kill Bluestacks, then I re-open Bluestacks .... NOTHING HAPPENED, my data and apps still there, and NO ROOT. Why?
Click to expand...
Click to collapse
1) Make sure you are using the required version, as these rooted files only works for v0.3.6.102.
2) Once you have replaced Data & SDCard, non of your existing apps should remain; If the apps still there you probably did it wrong.
3) Make sure you close your Bluestacks before replacing those files.
* Please note that the 'rooted files' mentioned above are 4 folders that contains 2 files in each folder.
codelover said:
Definately a good news! I will try to rebuild Root.sparsefs to include both working copies of su-3.1 & su.orig.
But if i am not mistaken su.orig only works alone thus not supporting Superuser apk for confirmation.
EDIT: Files updated, download HERE.
CHANGES: Using su.orig copy without any Superuser apk.
NOTE: Might need to replace all new .sparsefs files instead of just Root.sparsefs.
Kinda weird as all su in su-test can run in BS for Windows except su.orig that returned Seg. fault.
Anyway, hope to hear some good news soon.
Click to expand...
Click to collapse
did you want me to run some more tests?
so far all I've done is load the new files, open terminal, and try su: got permission denied
efdisastet said:
did you want me to run some more tests?
so far all I've done is load the new files, open terminal, and try su: got permission denied
Click to expand...
Click to collapse
Have you tried executing 'su' from adb instead of Terminal?
I am not sure how the included su.orig from alpha should behave as i got segfault here on Windows.
Unlike the newer SuperSU that works without apk, the su-3.1-x86 that worked for you during the test needs superuser apk,
but non of the apks i tested here work with that binary (All hung), kinda weird, until we have a working su+apk, other apps cannot gain root.
So i was thinking maybe we should try other superuser app, like the opensource ClockworkMod Superuser since it support x86 too.
Please download the attached su to test, let's see whether this one still causing segfault or not.
Code:
adb push su /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/su -v
As usual, we are expecting su to return some version info.
As i don't think it's a good idea to keep asking you to download & test a new 100M file for something unsure, i provide you an alternative:
By replacing with this modded initrd.img (~/Library/BlueStacks App Player/AppBundle/Contents/Android/initrd.img), if this work (hopefully), it will:
- Create the following public accessible folder if not exists: /data/root
- Create the following test files: /data/root/test
- Change ownership, group & permissions needed for su for all files found inside /data/root/ on every boot.
Click to expand...
Click to collapse
Once replaced initrd.img, reboot and if you see a new file /data/root/test and it's owned by root then you can proceed to the below tests, otherwise useless.
Code:
1) Install ClockworkMod [URL="https://play.google.com/store/apps/details?id=com.koushikdutta.superuser"]Superuser[/URL] or download [URL="http://download.clockworkmod.com/apks/Superuser.apk"]here[/URL].
2) adb push su /data/root/su
3) Restart Bluestacks to get the permissions needed by su.
4) Open terminal & type the following command: /data/root/su # Should get a prompt
* Note that you will be asked to update su binary but you won't be able to do so at the moment. leave that first.
If non of the above work i guess the only option is to test all su binaries and apks, which is very time-consuming.
But i guess i am to giving up instead as it's too hard for me to debug without actually owning a Mac to test it.
codelover said:
Have you tried executing 'su' from adb instead of Terminal?
Click to expand...
Click to collapse
tried running it from an adb shell, still permission denied
I am not sure how the included su.orig from alpha should behave as i got segfault here on Windows.
Unlike the newer SuperSU that works without apk, the su-3.1-x86 that worked for you during the test needs superuser apk,
but non of the apks i tested here work with that binary (All hung), kinda weird, until we have a working su+apk, other apps cannot gain root.
So i was thinking maybe we should try other superuser app, like the opensource ClockworkMod Superuser since it support x86 too.
Please download the attached su to test, let's see whether this one still causing segfault or not.
Code:
adb push su /data/local/tmp/
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/su -v
As usual, we are expecting su to return some version info.
Click to expand...
Click to collapse
tried this: segmentation fault
As i don't think it's a good idea to keep asking you to download & test a new 100M file for something unsure, i provide you an alternative:
By replacing with this modded initrd.img (~/Library/BlueStacks App Player/AppBundle/Contents/Android/initrd.img), if this work (hopefully), it will:
Once replaced initrd.img, reboot and if you see a new file /data/root/test and it's owned by root then you can proceed to the below tests, otherwise useless.
Code:
1) Install ClockworkMod [URL="https://play.google.com/store/apps/details?id=com.koushikdutta.superuser"]Superuser[/URL] or download [URL="http://download.clockworkmod.com/apks/Superuser.apk"]here[/URL].
2) adb push su /data/root/su
3) Restart Bluestacks to get the permissions needed by su.
4) Open terminal & type the following command: /data/root/su # Should get a prompt
* Note that you will be asked to update su binary but you won't be able to do so at the moment. leave that first.
If non of the above work i guess the only option is to test all su binaries and apks, which is very time-consuming.
But i guess i am to giving up instead as it's too hard for me to debug without actually owning a Mac to test it.
Click to expand...
Click to collapse
did all that. /data/root exists and seems writable (though trying to do an ls in /data still gives me permission denied)
but /data/root/su still gave me segmentation fault...
which version was that? Which versions did we get to give us a version number the other day?
efdisastet said:
tried running it from an adb shell, still permission denied
/data/root exists and seems writable (though trying to do an ls in /data still gives me permission denied) but /data/root/su still gave me segmentation fault...
which version was that? Which versions did we get to give us a version number the other day?
Click to expand...
Click to collapse
It was su-3.1-x86 that i got it from here but the site is down at the moment. You can still find the binary on my previous post, inside su-test.zip.
With that version i managed to get root with adb, but without a working apk you cannot gain root from other apps since it was designed to act like that.
But what makes me wonder is that the su.orig that worked without apk (anyone confirm?) on alpha supposed to work on this beta too.
Now that /data/root/ is working as expected, it's so much easier for you to test the binaries, just push to /data/root/ and reboot to get the required permissions.
codelover said:
It was su-3.1-x86 that i got it from here but the site is down at the moment. You can still find the binary on my previous post, inside su-test.zip.
With that version i managed to get root with adb, but without a working apk you cannot gain root from other apps since it was designed to act like that.
But what makes me wonder is that the su.orig that worked without apk (anyone confirm?) on alpha supposed to work on this beta too.
Now that /data/root/ is working as expected, it's so much easier for you to test the binaries, just push to /data/root/ and reboot to get the required permissions.
Click to expand...
Click to collapse
/data/root/ may be working as expected, but there still seems to be a "su" in the path somewhere, whose permissions are denied. Will that cause problems
I put the 3.1 file from the su-test folder into /data/root, restarted bluestacks, and then went to terminal, I've attached a screenshot of those results, including calling just "su" to note the difference
Maybe if I had a better handle on what we wanted all the permissions to be and where we wanted this executable su to be, and what su an app/apk like superuser tries to use, I could help more.
Basically I froze a system app that should not have been frozen through TitaniumBackup the result being my system refuses to boot, looping once and giving an error "cannot load Android system" and suggesting a full wipe, which I hope to avoid in either case.
What are my options at this point, in defrosting it or undoing what TitaniumBackup has done within the confines of the TWRP recovery or adb systems? I don't remember the package by name as I froze 2-3 of them, but I assume defrosting them all would suffice.
I will try to provide some basic information about the unit and its software if it helps. Moto G Power running Android 10 and TWRP 3.4.0.0 which is not installed but booted using fastboot and it has Magisk as root.
TaZeR369 said:
Basically I froze a system app that should not have been frozen through TitaniumBackup the result being my system refuses to boot, looping once and giving an error "cannot load Android system" and suggesting a full wipe, which I hope to avoid in either case.
What are my options at this point, in defrosting it or undoing what TitaniumBackup has done within the confines of the TWRP recovery or adb systems? I don't remember the package by name as I froze 2-3 of them, but I assume defrosting them all would suffice.
I will try to provide some basic information about the unit and its software if it helps. Moto G Power running Android 10 and TWRP 3.4.0.0 which is not installed but booted using fastboot and it has Magisk as root.
Click to expand...
Click to collapse
Have you tried this?. Don't forget to thank that person if it works.
If it doesn't work, you can use ADB through twrp with the Package Manager binary from /system/xbin/pm to list all disabled apps like this:
Bash:
adb shell pm list packages -d
then you can enable those disabled apps/packages through:
Bash:
adb shell pm enable <userID> <package name>
Slim K said:
Have you tried this?. Don't forget to thank that person if it works.
If it doesn't work, you can use ADB through twrp with the Package Manager binary from /system/xbin/pm to list all disabled apps like this:
Bash:
adb shell pm list packages -d
then you can enable those disabled apps/packages through:
Bash:
adb shell pm enable <userID> <package name>
Click to expand...
Click to collapse
Thank you so much for the prompt reply, this totally answered my question into how TB freeze works in android, and solved my problem I can use my phone again =)