stuck always #61
Comments
|
Hi, |
|
start like this (the avd is androidapiversion 23, armv7a): the second question, i am not sure what you mean. simply i downloaded the whole git - went here: https://github.com/newbit1/rootAVD, and then there is a CODE button, then press DOWNLOAD ZIP. thats it. |
|
Ok i see. In your log it says: Which means the busybox is missing, which is embedded at the end of the script. So this indicates Usually this is not a big issue, the script trys to download the complete script, but your log also says: Which is also not a big issue, the script trys to install magisk temporally to get it hands on the busybox From this point on, it should be able to execute the busybox binary, but your log says: Which indicates the execute permissions are not set correctly. I've changed something in that routine, and it did work for me. Btw: Magisk doesn't support Android 6 anymore, I think minimum Version is Android 7. If I run a working script with busybox embedded, I got this log: If I run a working script without busybox embedded, I got this log: |
|
i have downloaded the updated script. it seems it was successful. when i try "adb shell --- then: su", it seems rooted (????): C:\xxxx\xxxx\xxxx\ADB>adb shell BUT, the app ROOT CHECKER PRO shows not rooted. i dont know. yes, here is the log (i had to shut down avd manually) (avd is api level 25, android 7.1.1): rootAVD.bat C:\xxx\xxxx\AppData\Local\Android\Sdk\system-images\android-25\google_apis\armeabi-v7a\ramdisk.img |
|
Thanks, still the script doesn't work proper in your situation. could mean, that busybox doesn't have the execution rights. I can't fully reproduce your issue. I don't understand, why your rootAVD.sh file, doesn't have To get more information, could you please add a debug command in your script? to: and then post everything after Also, please use the fanced code block to post your log. If you are on a Windows machine, wouldn't it make more sense, to use a x86 or x86_64 image? Can you please upload your rootavd.sh file? So I can see if there is anything wrong with it? |
|
no files were edited by me, all are the original ones from this github. no, i doesnt make sense for me (the x86). i would like to use this emulator for native arm coding a do some research of android/linux (arm version). yes, this emulation (based on qemu) is really slow (even when you have a fast pc). upload my rootavd.sh? does it have any sense?? i didn't made any changes, so the file is the same as the one uploaded in this github repo. changed the lines, here is the cmd output: |
Well, this is what we expect, and what is normally the case, yes! But the observations clearly indicates, that there So please, upload it for me If you can. So I can further investigate the issue. Did you really put in
Yeah performance in this case doesn't bring you much, you need a similar host architecture. |
|
I have changed the whole unzip and busybox routines, also I removed the busybox behind the |
|
the file rootAVD.sh, is uploaded. the old one, and the new new one modified by you few days ago (i had to add .txt extension, just remove it). yes, i made the exact modification as you wrote: thank you, i didn't know that. i tried to use all major emulators, but none of them was able to run any armv7a/armv8 native binary (even the genymotion with ARM TRANSLATION using libhoudini could't do that). so the only option for me was to use a qemu based emulator (which could possibly run a native binary). i thought that, you must use a armv7a/armv8a image/avd to run a native arm binary. BUT, thank you for your advice, it seems like you are right, i tried ANDROID 11 avd... and, surprise, IT DID WORK! lul and more important thing, the android 11 avd runs really fast, and another more important thing is, that rootavd is working!! i have root access. so, i have to tell you, i am really grateful for your advice. now i can play with (debug binaries, hope that debugging will also work, i didn't tried it yet, uff!!) fast running avd (x86/64) which seems to work with arm binaries. also i tried the new rootavd, the new modified, on the arm avd/image, still not working: |
|
aaaah, shit! i thought that it would be possible to debug arm code, but no it is not. the debug server arm binary works on the x86/64 avd (android 11), it can run. but the debugging itself doesn't work. it is maybe because of the libhoudini translation library, who knows. so, it's look like that the only hope is to use one of the VEEERY slow ARM images/avds - but the root still doesn't work. |
|
Interesting, so debugging doesnt work with the ndk libtranslation. I dont get why the script acts different on your machine, while tested it with the same configuration. You can try to add the debug commands again, and show me the log files. RemoveTemporarilyMagisk You could also delete your system-image, and re download it. While it is downloading, it shows you the complete download link. Copy and paste it here please. Perhaps you system image has a difference to mine. With that download link i can try to use it and see how it works on my machine. |
|
i don' know if i am doing it right (the rootAVD.sh file has changed), the right place for the debug commands is here: changed it to: is that place right? anyways, it doesn't work, here's the latest log: for example i chose this system image, here is the info: |
|
Yes, add the lines in the rootavd.sh insert: to: These commands are for debugging, not for fixing. Thanks for the download link, i will have a look into it. |
|
here's the log: |
|
ok great, thanks. Somehow, the just copied busybox is not there. |
|
hm, i was reading the output, and this seems interesting to me: the sentence tell's it all. so i tried it. i pushed a debugging server to that directory "/data/data/com.android.shell", and it worked homehow (as root??). but unfortunately i wasn't able to attach to any process (only the system process was shown). so maybe the server isn't doing what it should. that was just an sudden idea.. anyways, hope you will make the root run! |
|
I am getting the same issue, surprisingly I did root a device with this prior, but after using the updated version I'm getting similar error. |
|
Hey @revolta, |
|
Hey @revolta 
|
|
yes, i think it works. maybe. there is a problem, but, apparently only on my side. i am not sure why is that happening. the rootavd.bat is running fine, but the avd itself is not responding after the process. it is somehow stuck (freezed), it takes not any input. it is not even possible to restart the avd (not byt clicking the little "x" in the corner of window, and not by using ADB). there is only one possibility to go to DEVICE MANAGER and push the little quadrangle associated to this avd (it is the STOP button), or from windows task manager and force to terminate the process/thread of the avd. but, when i use these two only possible solution (push STOP, or terminate process/thread), it always saves the current state of emulator - and maybe that's why the root isn't somehow "saved to the avd". i don't really know why is this happening. maybe a performance issue? i run a new notebook, and i have to go with FULL PERFORMANCE with the cable of notebook plugged in the socket. then the cable is plugged in the performance of all avds are better, but maybe not enought to save the root on avd. ps: newbit1 many thanks for your effort. here is the log, this time i tried a lower android version (api level 23) (don't worry about the version, the freezing is the same on api level 25.. and so on): |
|
Great, yeah the freezing comes from the qemu .exe You must cold boot your avd. Otherwise it is loading a snapshot! |
hello sir,
i must be doing something not goot. the script doesnt work at all. i am using newest android studio and newst emulator. every time i create a new virtual device (no matter its armv7a or armv8a, old or new images/api versions) i got stuck here (any help or advice would be appreciated, thank you):
[] Set Directorys
[-] Test if ADB SHELL is working
[-] ADB connectoin possible
[-] In any AVD via ADB, you can execute code without root in /data/data/com.android.shell
[] looking for Magisk installer Zip
[] Cleaning up the ADB working space
[] Creating the ADB working space
[] Push Magisk.zip into /data/data/com.android.shell/Magisk
[-] rootAVD-master\Magisk.zip: 1 file pushed, 0 skipped. 62.3 MB/s (11278270 bytes in 0.173s)
[] create Backup File
[] Push ramdisk.img into /data/data/com.android.shell/Magisk
[-] Android\Sdk\system-images\android-23\google_apis\armeabi-v7a\ramdisk.img: 1 file pushed, 0 skipped. 1126.7 MB/s (890197 bytes in 0.001s)
[-] Copy rootAVD Script into Magisk DIR
rootAVD.sh: 1 file pushed, 0 skipped. 81.1 MB/s (7855800 bytes in 0.092s)
[-] run the actually Boot/Ramdisk/Kernel Image Patch Script
[] from Magisk by topjohnwu and modded by NewBit XDA
[!] We are in a ranchu emulator shell
[-] Api Level Arch Detect
[-] Device Platform is arm only
[-] Device SDK API: 23
[-] First API Level:
[-] The AVD runs on Android 6.0
[-] Switch to the location of the script file
[] Extracting busybox from script ...
[!] There is no busybox behind the script
[] Trying to Download the Up-To-Date Script Version
[!] Temporarily installing Magisk
[!] Removing Temporarily installed Magisk
[-] Checking AVDs Internet connection...
[!] AVD is offline
[] Extracting Magisk.zip ...
/data/data/com.android.shell/Magisk/rootAVD.sh[2608]: /data/data/com.android.shell/Magisk/busybox: can't execute: Permission denied
[] Extracting busybox from script ...
[!] There is no busybox behind the script
[] Trying to Download the Up-To-Date Script Version
[!] Temporarily installing Magisk
[!] Removing Temporarily installed Magisk
[] Re-Run rootAVD in Magisk Busybox STANDALONE (D)ASH**
The text was updated successfully, but these errors were encountered: