How to root Bluestacks 2 using Linux in VirtualBox (Modify .vdi file) - Miscellaneous Android Development

BlueStacks 2.2.17.6203 is introducing "VirtualBox VMs".
The filesystems have been changed to "vdi format" (VirtualBox).
For linux experts: if you know how to mount and modify .vdi without VirtualBox, skip to step 9.
Well, let's get started!
First of all, to root BlueStacks this way you need VirtualBox and you have a Linux OS installed. If you just got started, I'll recommended Ubuntu, you can follow the guide installing Ubuntu on BirtualBox. http://www.wikihow.com/Install-Ubuntu-on-VirtualBox
Also, you will need some linux knowledge. It's not necessessary, but I won't provide any support about the part dealing with linux commands. Just follow the instructions and probably you will be able to root it, but it might not be that simple.
The second mandatory stuff you will need is the Android App called SuperSU. At this time, you should be able to find the latest SuperSU. The instructions should be the same with other SuperSU versions.
Here is a direct link http://www.supersu.com/download
This tutorial assumes you already have an installed BlueStacks you wish to root, but make sure Bluestacks and Ubuntu isn't running isn't running. So, let's get started.
In this tutorial i'm using Ubuntu.
1. MAKE A BACKUP OF ROOT.VDI FILE FIRST!
2. To modify Root.vdi, you need to mount it in Ubuntu virtual machine. Select Ubuntu and click Settings -> Storage. Select Controller: SATA and click on the HDD with green plus symbol.
{
"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"
}
3. A dialog box will appear. Select Choose existing disk
4. Navigate to Bluestacks directory where you installed. Select Root.vdi and Open
ProTip: You can mount Data.vdi and SDcard.vdi to transfer files between guest and VDI.
5. Root.vdi should be added in Storage. Click OK
6. Start Ubuntu on VirtualBox
7. Ubuntu: On your desktop, you should see the grey Hard Drive icon on the right taskbar. Yep, that's root.vdi image file that has been mounted and the disk name should be named 8,6 GB Volume
8. Extract x86 Folder from .zip (Recovery Flashable.zip) archive file and /common/SuperSU.apk somewhere on Ubuntu. Bluestacks is based on Android x86.
8.1. If you already downloaded it on your host computer, Click Devices -> Drag and Drop, Select Bidirectional and you can transfer the file to guest
If you haven't download it yet, download it from http://www.supersu.com/download and click Recovery Flashable.zip
9. Copy the following SuperSU files into your mounted root.vdi
Add file: /x86/su -> (8,6 GB Volume)/android/system/xbin/su
Rename file: /x86/su ---> (8,6 GB Volume)/x86/daemonsu
Add file: /x86/daemonsu ---> (8,6 GB Volume)/android/system/xbin/daemonsu
Add file: /x86/supolicy ---> (8,6 GB Volume)/android/system/xbin/supolicy
Add file: /x86/libsupol.so ---> (8,6 GB Volume)/android/system/lib/libsupol.so
Add file: /common/Superuser.apk ---> (8,6 GB Volume)/android/system/app/Superuser.apk
10. You need to change file permissions in order for SuperSU to work correctly. Open terminal and type the following commands. Type your password when asked
Note: The disk name might be different. You can check it by right click on 8,6 GB Volume and select Properties
ProTip: Type sudo chmod xxx in terminal and drag a file to get the full path like below. Press UP ARROW on your keyboard to show the last command you used.
sudo chmod 755 '/media/test/<disk udid>/android/system/xbin/su'
sudo chmod 755 '/media/test/<disk udid>/android/system/xbin/daemonsu'
sudo chmod 755 '/media/test/<disk udid>/android/system/xbin/supolicy'
sudo chmod 644 '/media/test/<disk udid>/android/system/lib/libsupol.so'
sudo chmod 644 '/media/test/<disk udid>/android/system/app/Superuser.apk'
Files should be owned by root:root. No need to change it on Ubuntu.
11. Now we need to start "daemonsu" on every reboot. BlueStacks init procedure is quite simple. Seems like there is only android/system/etc/init.sh. So, open android/system/etc/init.sh in your preferred linux text-editor, go at the bottom of the file and search for:
Code:
init|"")
do_init
;;
esac
Add this
Code:
init|"")
do_init
/system/xbin/daemonsu --auto-daemon &
;;
esac
I'd say we're done now! Shutdown your Virtualbox
12. Now you can start your BlueStacks. When it's booted, launch SuperSU via Play Store.
You will be prompted about a SuperSU update. Choose the "normal" way and after the update, restart your BlueStacks.
13. That should be it. Now your BlueStacks is rooted.
To be certain you should open your PlayStore and install your preferred RootChecker.
An additional task you might want to do would be using some apps like "/system/app Mover" and "System App Uninstall" and change the SystemDefaultAppLauncher and SystemDefaultAppBrowser.
I usually install Nova Launcher.
Also, as Root FileExplorer, I install X-Plore.
You might want to install a CatLog too!
Hope you enjoyed this tutorial
Hope you will enjoy you newly rooted BlueStacks.
Tweak your Bluestacks and share your .vdi files to everyone.
Credit goes to rumbla (mybot.run) for the original tutorial how to modify root.fs
And me for this new tutorial

Here are the links that helped me a lot to copy/paste text and also files between guest operating system (Ubuntu) and host computer (Windows 10)
"How do I tell if virtualbox guest additions is installed and working correctly" on Ubuntu Forums
"Virtualbox and shared folders - permissions problem" also on Ubuntu Forums
Also I had to chown root:root "files"
Working ................. so far, so good
Thanks a lot

I comfirmed that it still working on bluestack 4 (mac os) thanks a lot! <3
Note that if BS is "x86_64" then you need using files in "x64" folder!

evildog1 said:
BlueStacks 2.2.17.6203 is introducing "VirtualBox VMs".
The filesystems have been changed to "vdi format" (VirtualBox).
For linux experts: if you know how to mount and modify .vdi without VirtualBox, skip to step 9.
Well, let's get started!
First of all, to root BlueStacks this way you need VirtualBox and you have a Linux OS installed. If you just got started, I'll recommended Ubuntu, you can follow the guide installing Ubuntu on BirtualBox. http://www.wikihow.com/Install-Ubuntu-on-VirtualBox
Also, you will need some linux knowledge. It's not necessessary, but I won't provide any support about the part dealing with linux commands. Just follow the instructions and probably you will be able to root it, but it might not be that simple.
The second mandatory stuff you will need is the Android App called SuperSU. At this time, you should be able to find the latest SuperSU. The instructions should be the same with other SuperSU versions.
Here is a direct link http://www.supersu.com/download
This tutorial assumes you already have an installed BlueStacks you wish to root, but make sure Bluestacks and Ubuntu isn't running isn't running. So, let's get started.
In this tutorial i'm using Ubuntu.
1. MAKE A BACKUP OF ROOT.VDI FILE FIRST!
2. To modify Root.vdi, you need to mount it in Ubuntu virtual machine. Select Ubuntu and click Settings -> Storage. Select Controller: SATA and click on the HDD with green plus symbol.
3. A dialog box will appear. Select Choose existing disk
4. Navigate to Bluestacks directory where you installed. Select Root.vdi and Open
ProTip: você pode montar Data.vdi e SDcard.vdi para transferir arquivos entre o convidado e o VDI.
5. Root.vdi deve ser adicionado ao Storage. Clique OK
6. Inicie o Ubuntu no VirtualBox
7. Ubuntu: em sua área de trabalho, você deve ver o ícone cinza do disco rígido na barra de tarefas direita. Sim, esse é o arquivo de imagem root.vdi que foi montado e o nome do disco deve se chamar Volume de 8,6 GB
8. Extraia a pasta x86 do arquivo .zip (Recovery Flashable.zip) e /common/SuperSU.apk em algum lugar do Ubuntu. Bluestacks é baseado no Android x86.
8,1 Se você já fez o download em seu computador host, clique em Dispositivos -> Arrastar e soltar, selecione bidirecional e você pode transferir o arquivo para o convidado
Se você ainda não fez o download, faça o download em http://www.supersu.com/download e clique em Recovery Flashable.zip
9. Copie os seguintes arquivos SuperSU para o root.vdi montado
Adicionar arquivo: / x86 / su -> (Volume de 8,6 GB) / android / system / xbin / su
Renomear arquivo: / x86 / su ---> (Volume de 8,6 GB) / x86 / daemonsu
Adicionar arquivo: / x86 / daemonsu ---> (Volume de 8,6 GB) / android / system / xbin / daemonsu
Adicionar arquivo: / x86 / supolicy ---> (Volume de 8,6 GB) / android / system / xbin / supolicy
Adicionar arquivo: /x86/libsupol.so ---> (Volume de 8,6 GB) /android/system/lib/libsupol.so
Adicionar arquivo: /common/Superuser.apk ---> (Volume de 8,6 GB) /android/system/app/Superuser.apk
10. Você precisa alterar as permissões do arquivo para que o SuperSU funcione corretamente. Abra o terminal e digite os seguintes comandos. Digite sua senha quando solicitado
Nota: o nome do disco pode ser diferente. Você pode verificar clicando com o botão direito em Volume de 8,6 GB e selecione Propriedades
ProTip: Digite sudo chmod xxx no terminal e arraste um arquivo para obter o caminho completo como abaixo. Pressione a SETA PARA CIMA no teclado para mostrar o último comando usado.
sudo chmod 755 '/ media / test / <disk udid> / android / system / xbin / su'
sudo chmod 755 '/ media / test / <disk udid> / android / system / xbin / daemonsu'
sudo chmod 755 '/ media / test / <disk udid> / android / system / xbin / supolicy'
sudo chmod 644 '/ media / test / <disk udid> /android/system/lib/libsupol.so'
sudo chmod 644 '/ media / test / <disk udid> /android/system/app/Superuser.apk'
Os arquivos devem pertencer a root: root. Não há necessidade de alterá-lo no Ubuntu.
11. Agora precisamos iniciar o "daemonsu" a cada reinicialização. O procedimento de inicialização do BlueStacks é bastante simples. Parece que só existe android / system /etc/init.sh. Portanto, abra android / system / etc / init.sh em seu editor de texto Linux preferido, vá até o final do arquivo e pesquise por:
[CÓDIGO] init | "")
fazendo
;;
esac [/ CODE]
Adicione isso
[CÓDIGO] init | "")
fazendo
/ system / xbin / daemonsu --auto-daemon &
;;
esac [/ CODE]
Eu diria que terminamos agora! Desligue seu Virtualbox
12. Agora você pode iniciar seus BlueStacks. Quando ele for inicializado, inicie o SuperSU via Play Store.
Você será avisado sobre uma atualização do SuperSU. Escolha o caminho "normal" e após a atualização reinicie seus BlueStacks.
13. Deve ser isso. Agora seu BlueStacks está enraizado.
Para ter certeza, você deve abrir sua PlayStore e instalar o RootChecker de sua preferência.
Uma tarefa adicional que você pode querer fazer seria usar alguns aplicativos como "/ system / app Mover" e "System App Uninstall" e alterar SystemDefaultAppLauncher e SystemDefaultAppBrowser.
Eu geralmente instalo o Nova Launcher.
Além disso, como Root FileExplorer, eu instalo o X-Plore.
Você pode querer instalar um CatLog também!
Espero que tenha gostado desse tutorial
Espero que você goste de seu BlueStacks recém-enraizado.
Ajuste seus Bluestacks e compartilhe seus arquivos .vdi com todos.
O crédito vai para rumbla (mybot.run) pelo tutorial original sobre como modificar root.fs
E eu para este novo tutorial
Click to expand...
Click to collapse
Não dá

Related

[GUIDE] TO Root Sony C3 4g D2533 BootLoader LOCK FINAL KK 4.4 / LOLLIPOP 5.0.2

Hola a todos les traigo un nuevo post en el cual dejare mi conocimiento y test del sony xperia c3 4g modelo D2533 con SuperSU root final permanente con bootloader bloqueado
1-.ir a ajustes, luego preciona en acerca del telefono & finalmente preciona varias veces en numero de compilacion asta que nos informe que ya tenemos las opciones de desarrollador activa, luego preciona volver y en opciones de desarrollador activalas, activa depuracion usb & permitir ubicacion de prueba, ya una vez echo luego ir a ajustes, seguridad, marcar fuentes desconocidas, luego ir a pantalla, apagar despues de 10 minutos
2-. descargar kingroot apk
3-. instalar y aser root a d2533 (conexion a internet ya sea 3g o wifi ) y darle a start root asta que termine, esto te dara root pero de formal temporal
4-.instalar busybox de playstore, ejecutar app y precionar install y salir de la app una vez terminado el proceso
5-.instalar terminal de google play aun no ejecutar
6-.descargar el archivo .zip Sustitución Kinguser por SuperSU, extraer con root explorer o en pc lo importante es que quede la carpeta llamada "mrw" en la memoria interna, una vez echo esto nos vamos a terminal
7-. en terminal escribir los siguientes 2 comandos:
su (peticion de permisos root dar en allowed para conceder)
sh /sdcard/mrw/root.sh
8-.una vez echo el proceso comensara a trabajar el script, (no ejecutes ninguna otra tarea mientras el proceso finaliza)
9-. una vez terminado el proceso superSU se abrira automaticamente, te pedira actualizar binarios, continuar, instalacion normal, una vez instalados dar click en aceptar.
PD: si en el momento de la instalacion de superSU te pide desintalar otra aplicacion de super user dale en aceptar.
Asi kinguser desaparecera y tendras root de superSU
Pasar superSU al sistema
con la app root explorer ir a la siguiente ruta RAIZ/DATA/APP/(CARPETA LLAMADA) eu.chainfire.supersu-1. SELECCIONAR CARPETA Y MOVER A ESTA DIRECCION RAIZ/SYSTEM/APP una vez reiniciado el celular ya nuestra app estara en el sistema y podremos disfrutar de ella sin restricciones.
Hello everyone I bring a new post in which test fails my knowledge and c3 sony xperia 4g SuperSU model D2533 with permanent root end: D with locked bootloader
1-.ir adjustments, then preciona About phone & preciona several times finally build number till we report that we have active developer options, then preciona back and activate them Developer options enable USB debugging & allow test location, and then cast again go to settings, security, mark unknown sources, then go to screen off after 10 minutes
2. kingroot download apk
3. Asher root to install and d2533 (internet connection either 3G or WiFi) and give root start till the end, but it will give you temporary root Formal
4-.install busybox of playstore, run app precionar install and leave the app once the process is completed
5-.install terminal google play not yet run
6-Replacing the .zip file .Download Kinguser by SuperSU, extract with root explorer or pc what is important is that it is the folder called "mrw" in the internal memory, once we have done this we go to terminal
7-. in terminal enter the following two commands:
su (root permissions request hit allowed to grant)
sh /sdcard/mrw/root.sh
8-.Once made the process starts to work the script (do not run any other tasks while the process ends)
9-. SuperSU once the process is complete it will automatically open, binary update will ask continue normal installation, once installed to click OK.
PS: if at the time of the installation of SuperSU asks you uninstall other applications user dale super OK.
So kinguser disappear and you will have root SuperSU
SuperSU pass system
the app root explorer go to the next ROOT / DATA / APP / (folder called) eu.chainfire.supersu-1 route. SELECT FOLDER AND MOVE TO THIS ADDRESS ROOT / SYSTEM / APP after restarting the phone, and our app will be in the system and we can enjoy it without restrictions.
download apk kingroot
https://mega.co.nz/#!BElBQKza!_Et5VVOwNsS2R331D6eliHO_YNqhiD4sGEc_jXm7qNE
download sustitucion kinguser por superSU
https://mega.nz/#!VYlAFTRD!wRCZl0LGuwLjP7WcS2LThagnknqnC-lLsevlWZzXKhc
busybox
https://play.google.com/store/apps/details?id=stericson.busybox
terminal
https://play.google.com/store/apps/details?id=jackpal.androidterm
funcionó! lo único que podría añadir es que con la última versión de KingRoot que salió hace 2 días, ya se podía lograr un root permanente y al 100% jaja, pero siempre es mejor tener SuperSU, gracias por el tutorial, es posible hasta ahora instalar CWM? o recovery?
De alguna forma no tengo posibilidad de descargarla desde mi telefono, la app de mega no se abre cuando hago click en los links (tal vez problemas en lollypop??) tendre que hacerlo en el pc a ver que pasa...
Pregunta: despues del proceso te deja montar la particion de sistema para escritura con root explorer?? Con kinguser no me dejaba en kitkat....
Saludos de Conce compadre!!!
failed to update su binary?
Heres the transcript from terminal emulator
[email protected]:/ $ su
[email protected]:/ # sh /sdcard/mrw/root.sh
---------------------------------------
---------- Made By : Mr.W0lf ----------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
mount: Operation not permitted
/sdcard/mrw/root.sh[16]: can't create /system/bin/busybox: Read-only file system
Unable to open /system/bin/busybox: No such file or directory
Unable to open /system/bin/busybox: No such file or directory
chattr: setting flags on /system/xbin/ku.sud: Read-only file system
rm failed for /system/xbin/ku.sud, Read-only file system
chattr: setting flags on /system/xbin/su: Read-only file system
rm failed for /system/xbin/su, Read-only file system
chattr: setting flags on /system/xbin/supolicy: Read-only file system
rm failed for /system/xbin/supolicy, Read-only file system
/sdcard/mrw/root.sh[29]: can't create /system/xbin/su: Read-only file system
/sdcard/mrw/root.sh[30]: can't create /system/xbin/daemonsu: Read-only file system
/sdcard/mrw/root.sh[31]: can't create /system/xbin/sugote: Read-only file system
/sdcard/mrw/root.sh[32]: can't create /system/xbin/sugote-mksh: Read-only file system
Unable to chown /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
Unable to open /system/xbin/sugote: No such file or directory
Unable to open /system/xbin/sugote: No such file or directory
Unable to open /system/xbin/sugote-mksh: No such file or directory
Unable to open /system/xbin/sugote-mksh: No such file or directory
Unable to open /system/xbin/daemonsu: No such file or directory
Unable to open /system/xbin/daemonsu: No such file or directory
/sdcard/mrw/root.sh[41]: daemonsu: not found
rm failed for /data/data/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data-lib/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data/com.kingroot.master, No such file or directory
chattr: setting flags on /system/bin/.usr/.ku: Read-only file system
rm failed for /system/bin/.usr/.ku, Read-only file system
chattr: setting flags on /system/bin/rt.sh: Read-only file system
rm failed for /system/bin/rt.sh, Read-only file system
chattr: setting flags on /system/bin/su: Read-only file system
rm failed for /system/bin/su, Read-only file systemchattr: stat /system/bin/ddexe: No such file or directory
rm failed for /system/bin/ddexe, No such file or directory
chattr: setting flags on /system/bin/install-recovery.sh: Read-only file system
rm failed for /system/bin/install-recovery.sh, Read-only file system
chattr: stat /system/bin/install-recovery.sh-ku.bak: No such file or directory
rm failed for /system/bin/install-recovery.sh-ku.bak, No such file or directory
pkg: /sdcard/mrw/superuser.apk
Success
chattr: setting flags on /system/usr/iku/isu: Read-only file system
rm failed for /system/usr/iku, Read-only file system
chattr: setting flags on /system/etc/install-recovery.sh: Read-only file system
rm failed for /system/etc/install-recovery.sh, Read-only file system
chattr: setting flags on /system/etc/install_recovery.sh: Read-only file system
rm failed for /system/app/Kinguser, No such file or directory
rm failed for /data/data-lib/king, No such file or directory
[email protected]:/ #
omike123 said:
Heres the transcript from terminal emulator
[email protected]:/ $ su
[email protected]:/ # sh /sdcard/mrw/root.sh
---------------------------------------
---------- Made By : Mr.W0lf ----------
---- Thanks @Chainfire for SuperSU ----
---------------------------------------
mount: Operation not permitted
/sdcard/mrw/root.sh[16]: can't create /system/bin/busybox: Read-only file system
Unable to open /system/bin/busybox: No such file or directory
Unable to open /system/bin/busybox: No such file or directory
chattr: setting flags on /system/xbin/ku.sud: Read-only file system
rm failed for /system/xbin/ku.sud, Read-only file system
chattr: setting flags on /system/xbin/su: Read-only file system
rm failed for /system/xbin/su, Read-only file system
chattr: setting flags on /system/xbin/supolicy: Read-only file system
rm failed for /system/xbin/supolicy, Read-only file system
/sdcard/mrw/root.sh[29]: can't create /system/xbin/su: Read-only file system
/sdcard/mrw/root.sh[30]: can't create /system/xbin/daemonsu: Read-only file system
/sdcard/mrw/root.sh[31]: can't create /system/xbin/sugote: Read-only file system
/sdcard/mrw/root.sh[32]: can't create /system/xbin/sugote-mksh: Read-only file system
Unable to chown /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
Unable to open /system/xbin/sugote: No such file or directory
Unable to open /system/xbin/sugote: No such file or directory
Unable to open /system/xbin/sugote-mksh: No such file or directory
Unable to open /system/xbin/sugote-mksh: No such file or directory
Unable to open /system/xbin/daemonsu: No such file or directory
Unable to open /system/xbin/daemonsu: No such file or directory
/sdcard/mrw/root.sh[41]: daemonsu: not found
rm failed for /data/data/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data-lib/com.kingroot.RushRoot, No such file or directory
rm failed for /data/data/com.kingroot.master, No such file or directory
chattr: setting flags on /system/bin/.usr/.ku: Read-only file system
rm failed for /system/bin/.usr/.ku, Read-only file system
chattr: setting flags on /system/bin/rt.sh: Read-only file system
rm failed for /system/bin/rt.sh, Read-only file system
chattr: setting flags on /system/bin/su: Read-only file system
rm failed for /system/bin/su, Read-only file systemchattr: stat /system/bin/ddexe: No such file or directory
rm failed for /system/bin/ddexe, No such file or directory
chattr: setting flags on /system/bin/install-recovery.sh: Read-only file system
rm failed for /system/bin/install-recovery.sh, Read-only file system
chattr: stat /system/bin/install-recovery.sh-ku.bak: No such file or directory
rm failed for /system/bin/install-recovery.sh-ku.bak, No such file or directory
pkg: /sdcard/mrw/superuser.apk
Success
chattr: setting flags on /system/usr/iku/isu: Read-only file system
rm failed for /system/usr/iku, Read-only file system
chattr: setting flags on /system/etc/install-recovery.sh: Read-only file system
rm failed for /system/etc/install-recovery.sh, Read-only file system
chattr: setting flags on /system/etc/install_recovery.sh: Read-only file system
rm failed for /system/app/Kinguser, No such file or directory
rm failed for /data/data-lib/king, No such file or directory
[email protected]:/ #
Click to expand...
Click to collapse
1) su <------ in terminal emulator (root permissions request hit allowed to grant)
2) sh /sdcard/mrw/root.sh <------- second step
diiegooh said:
1) su <------ in terminal emulator (root permissions request hit allowed to grant)
2) sh /sdcard/mrw/root.sh <------- second step
Click to expand...
Click to collapse
That's exactly what I did. Tried it many times, installed SuperSU successfully but failed to update its binaries. And I was unable to replace Kinguser with supersu.
omike123 said:
That's exactly what I did. Tried it many times, installed SuperSU successfully but failed to update its binaries. And I was unable to replace Kinguser with supersu.
Click to expand...
Click to collapse
Try these by root, and then follow the steps
diiegooh said:
Try these by root, and then follow the steps
Click to expand...
Click to collapse
Yeah! My phone acquired root using kingroot. Are you suggesting to re-root it again by kingroot? Anyway I did just like that but this time I was unable to install the apk you provided. When installing the app it says 'application not installed'.
Someone can upload the "mrw" file (or folder) to another server please?????!!! :'(
Ok... I got full root permissions just using kingroot 4.1.0.249 (the latest), i can mount system as r/w, unninstall system apps, etc.
Now the question is: CAN WE MOVE DATA AND OBB FOLDERS FROM EMULATED TO SDCARD1??? If yes HOW???!!!
Me aparece el mismo error que el Omike123 :/, si pruebo al rootearlo con la ultima versión del kingroot y usar solo kinguser por defecto, quedara para siempre o el root o solo temporal?
1. Copy all the files to your external SD card, into a folder called mrw.
2. Install Kingroot (if you have Kinguser, go into the app and unroot your device, do not reboot) and FX File Explorer, alongside the root add-on
3. Run Kingroot (it'll root your device)
4. Open FX, then open System (root). Grant root privileges.
5. Locate and run the script mrw/root.sh as root.
6. It'll run for a while, when SuperSU appears, immediately update binaries.
7. It'll again run for a while, wait till SuperSU finishes, then select 'REBOOT'.
8. SuperSU root obtained!
Alternatively, root using Kingroot, then run Kinguser and update Kinguser itself. The latest version is a permanent root (at least, for me).
BachMinuetInG said:
1. Copy all the files to your external SD card, into a folder called mrw.
2. Install Kingroot (if you have Kinguser, go into the app and unroot your device, do not reboot) and FX File Explorer, alongside the root add-on
3. Run Kingroot (it'll root your device)
4. Open FX, then open System (root). Grant root privileges.
5. Locate and run the script mrw/root.sh as root.
6. It'll run for a while, when SuperSU appears, immediately update binaries.
7. It'll again run for a while, wait till SuperSU finishes, then select 'REBOOT'.
8. SuperSU root obtained!
Is necessary install Busybox?
Click to expand...
Click to collapse
eyedol64 said:
BachMinuetInG said:
1. Copy all the files to your external SD card, into a folder called mrw.
2. Install Kingroot (if you have Kinguser, go into the app and unroot your device, do not reboot) and FX File Explorer, alongside the root add-on
3. Run Kingroot (it'll root your device)
4. Open FX, then open System (root). Grant root privileges.
5. Locate and run the script mrw/root.sh as root.
6. It'll run for a while, when SuperSU appears, immediately update binaries.
7. It'll again run for a while, wait till SuperSU finishes, then select 'REBOOT'.
8. SuperSU root obtained!
Is necessary install Busybox?
Click to expand...
Click to collapse
If you use FX there should be an inbuilt busybox setup installed. But it is still recommended to install Stericson's Busybox.
Click to expand...
Click to collapse
please solution root with lockbootloder C3 2503
please solution root with lockbootloder C3 2503
it reboot and failed after i choose start root in kingroot 4.1
raitokun said:
it reboot and failed after i choose start root in kingroot 4.1
Click to expand...
Click to collapse
After reboot you have to restart kingroot mate.
raitokun said:
it reboot and failed after i choose start root in kingroot 4.1
Click to expand...
Click to collapse
Just keep repeating until you get it, it took me 2 reboots to get it rooted.
I got a new C3 D2533, android 5.0 with 8GB merged memory. It's the 2015 production so I now have 2.90 GB memory, what do you guys do with the phone now that it's rooted?
And are you all able to modify and use the governors+frequency in stock kernel? If yes I would like to know the min+max frequency and available governors. My phone is running smooth with decent battery life so I'm not sure if I want to root it.
pelao160312 said:
Hello everyone I bring a new post in which test fails my knowledge and c3 sony xperia 4g SuperSU model D2533 with permanent root end: D with locked bootloader
1-.ir adjustments, then preciona About phone & preciona several times finally build number till we report that we have active developer options, then preciona back and activate them Developer options enable USB debugging & allow test location, and then cast again go to settings, security, mark unknown sources, then go to screen off after 10 minutes
2. kingroot download apk
3. Asher root to install and d2533 (internet connection either 3G or WiFi) and give root start till the end, but it will give you temporary root Formal
4-.install busybox of playstore, run app precionar install and leave the app once the process is completed
5-.install terminal google play not yet run
6-Replacing the .zip file .Download Kinguser by SuperSU, extract with root explorer or pc what is important is that it is the folder called "mrw" in the internal memory, once we have done this we go to terminal
7-. in terminal enter the following two commands:
su (root permissions request hit allowed to grant)
sh /sdcard/mrw/root.sh
8-.Once made the process starts to work the script (do not run any other tasks while the process ends)
9-. SuperSU once the process is complete it will automatically open, binary update will ask continue normal installation, once installed to click OK.
PS: if at the time of the installation of SuperSU asks you uninstall other applications user dale super OK.
So kinguser disappear and you will have root SuperSU
SuperSU pass system
the app root explorer go to the next ROOT / DATA / APP / (folder called) eu.chainfire.supersu-1 route. SELECT FOLDER AND MOVE TO THIS ADDRESS ROOT / SYSTEM / APP after restarting the phone, and our app will be in the system and we can enjoy it without restrictions.
download apk kingroot
https://mega.co.nz/#!BElBQKza!_Et5VVOwNsS2R331D6eliHO_YNqhiD4sGEc_jXm7qNE
download sustitucion kinguser por superSU
https://mega.nz/#!VYlAFTRD!wRCZl0LGuwLjP7WcS2LThagnknqnC-lLsevlWZzXKhc
busybox
https://play.google.com/store/apps/details?id=stericson.busybox
terminal
https://play.google.com/store/apps/details?id=jackpal.androidterm
Click to expand...
Click to collapse
rooted successfully, tks

Xperia M2 Dual - Radio Band issue - Selected USA Band accidently

Xperia M2 Dual, D2302., Lollipop 5.1.1 - ( Firmware 18.6.A.0.182)
----------------------------------------------------------------------------------------------
This is how it accidentally happened: USA Band selected.
Dial *#*#4636#*#* > Testing menu > Phone information > Select Radio Band > USA Band (No other option in the list).
Lost network, SIM network stopped working now.
----------------------------------------------------------------------------------------------
All below action already performed:
- Bootloader is unlocked
- Successfully connects to ADB and fastboot
- Applied below Fastboot commands:
Fastboot erase modemst1 > Returns with failed (Command not allowed)
Fastboot erase modemst2 > Returns with Failed (Command not allowed)
Fastboot erase cache > Ok
- Also connected to Sony Emma > flash mode – can’t see option to flash modem.img /radio.img
------------------------------------------------------------------------------------------------
How to get to the solution to reset back now?
Please comment help!
Thank you!
solucion español adb
Abrí una ventana DOS y comencé el ADB SHELL con el teléfono conectado, hice *#*#4636#*#* y presione Información del teléfono. Después hice la siguiente instrucción con el adb:
adb shell
$ su
# stop ril-daemon
Después de hacer Enter ves que tu conexión esta perdida, presiona el menú del teléfono y escoges Seleccionar banda de red y las opciones Establecer banda GSM y UMTS aparece en la pantalla. Aquí es donde hay que repartir el ril-daemon:
# start ril-daemon
Despues de hacer Enter, ves que tienes conexión otra vez, presiona Automatic y obtienes el mensaje siguiente:
Establecer Automatic Correcto.
espero que te sirva
I love venezuela
TechGuys said:
Xperia M2 Dual, D2302., Lollipop 5.1.1 - ( Firmware 18.6.A.0.182)
----------------------------------------------------------------------------------------------
This is how it accidentally happened: USA Band selected.
Dial *#*#4636#*#* > Testing menu > Phone information > Select Radio Band > USA Band (No other option in the list).
Lost network, SIM network stopped working now.
----------------------------------------------------------------------------------------------
All below action already performed:
- Bootloader is unlocked
- Successfully connects to ADB and fastboot
- Applied below Fastboot commands:
Fastboot erase modemst1 > Returns with failed (Command not allowed)
Fastboot erase modemst2 > Returns with Failed (Command not allowed)
Fastboot erase cache > Ok
- Also connected to Sony Emma > flash mode – can’t see option to flash modem.img /radio.img
------------------------------------------------------------------------------------------------
How to get to the solution to reset back now?
Please comment help!
Thank you!
Click to expand...
Click to collapse
How we solve
gabriel1209 said:
Abrí una ventana DOS y comencé el ADB SHELL con el teléfono conectado, hice *#*#4636#*#* y presione Información del teléfono. Después hice la siguiente instrucción con el adb:
adb shell
$ su
# stop ril-daemon
Después de hacer Enter ves que tu conexión esta perdida, presiona el menú del teléfono y escoges Seleccionar banda de red y las opciones Establecer banda GSM y UMTS aparece en la pantalla. Aquí es donde hay que repartir el ril-daemon:
# start ril-daemon
Despues de hacer Enter, ves que tienes conexión otra vez, presiona Automatic y obtienes el mensaje siguiente:
Establecer Automatic Correcto.
espero que te sirva
I love venezuela
Click to expand...
Click to collapse
You should know the 4th rule of XDA forums:
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
Click to expand...
Click to collapse

[ROOT][HELP][iNTEL] I need to make root in my tablet, but like impossible.

Hi guys, I have a DL 3411 Tablet with Android 5.1, and looks like impossible make root in them, please, if you can help, help me please
Some information about it:
Genuine Intel(R) CPU 1,04 GHz
Cores: 4
Architecture: x86
CPUID: 6.5d.1
Codename: SoFIA 3GR
Process: 28 nm
L1 D-Cache: 4 x 24 KB
L1 I-Cache: 4 x 32 KB
L2 Cache 2: x 512 KB
Clock Speed: 208 MHZ - 1,04 GHZ
GPU Vendor: ARM
GPU Renderer: Mali-450 MP4
Model: Tablet_DL_3411 (TabKids_Plus)
Manufacturer: DL
Board: rk3osdk
Hardware: soflaboard
Screen Size: 5,55 inches
Screen Resolution: 600 x 1024 pixels
Screen Density: 214 dpi
Total RAM: 933 MB
InternaIStorage: 4,41 GB
Android Version: 5.1.1
API Level: 22
Bootloader: 1605.1 00_M1 S1
Build ID: LMY49F release-keys
Java VM: ART 2.1.0
OpenGL ES: 2.0
Kernel Architecture: i686
Kernel Version: 3.14.0 (eng.pb105.20160808.112201)
Olá, consegui fazer o root com o Magisk manager.
Ativei o modo depuração usb, e ativei permitir desbloquear o bootloader no modo desenvolvedor.
Depois usei os comandos para desbloquear o bootloader:
./adb reboot fastboot
-ele reinicia no modo fastboot e fica com a tela preta.
./fastboot oem unlock
./fastboot oem unlock confirm
assim consegui desbloquear o bootloader
Baixei no site DL a fimware e extrai os arquivos da firmware deste tablet com o "flstool.exe" programa que fica na pasta de instalacao do "intel flash tool" e separei o boot.fls.
./FlsTool -x "nome do aquivo firmware.fls"
./FlsTool --extract-prg "nome do arquivo firmware.fls"
ele vai extrair todos os aquivos da firmware, e separei o arquivo que tem o nome boot.fls e o copiei para o tablet.
Instalei o apk magiskmanager atualizado, apos aberto cliquei em instalar e quando pediu o arquivo boot.img para corrigir, indiquei o arquivo boot.fls que extrai da firmware. Ele vai gerar outro arquivo boot.img, copiei este arquivo do tablet para pasta onde esta o adb/fastboot no pc.
Enviar o boot.img gerado pelo magiskmanager via fastboot:
./adb reboot fastboot
espere o tablet reiniciar
./fastboot flash boot "nome do boot.img gerado pelo magisk"
./fastboot reboot
depois disso ja vai estar com root.
pode confirmar instalando o root checker.
Hi, I managed to root with the Magisk manager. I activated the USB debugging mode, and I enabled to allow the bootloader to be unlocked in developer mode. Then I used the commands to unlock the bootloader: ./adb reboot fastboot -he restarts in fastboot mode and stays with the black screen. ./fastboot oem unlock ./fastboot oem unlock confirm so I managed to unlock the bootloader I downloaded the DL site to fimware and extracted the firmware files for this tablet with the "flstool.exe" program located in the installation folder of the "intel flash tool" and separated the boot.fls. ./FlsTool -x "file name firmware.fls" ./FlsTool --extract-prg "filename firmware.fls" it will extract all files from the firmware, and I separated the file that has the name boot.fls and copied it to the tablet. I installed the updated magiskmanager apk, after opening it I clicked install and when asked for the boot.img file to fix it, I indicated the boot.fls file that it extracts from the firmware. It will generate another boot.img file, I copied this file from the tablet to the folder where the adb / fastboot is on the pc. Submit the boot.img generated by magiskmanager via fastboot: ./adb reboot fastboot wait for the tablet to restart ./fastboot flash boot "name of the boot.img generated by magisk" ./fastboot reboot after that it will be rooted. you can confirm by installing the rot checker. all this information was extracted here from the xda forum
Hint: Replace in this thread's title term tablet by your tablet's brand & model thus mainly owners of such a tablet get addressed.
AFAIK at least 3 Android tablets with Intel CPU exist.

Install GERDA OS on nokia 8110 4g

Hello xdas,
I'm an android user that started customization with my old (and beloved) galaxy s2, and then I installed custom rom on every smartphone I get.
My girlfriend gave me a present last april, a nokia 8110 because she knows that I love to custom devices.
But I have a problem (and I can't find solution on banana hackers's guides)
I want to install gerda on this feature phone and so I'm following this guide:
https://gerda.tech/#h1.4_install
I installed wallace lite, I dowloaded on my pc (win 10 home 20H2) the adb pckg. From this directory (the adb) I start the PowerShell and I give this command
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery-backup.img bs=2048
.
I have the debug mode activated, the phone rooted (and obviuosly connected the pc) but I get this error message:
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery-backup.img bs=2048
dd : Termine 'dd' non riconosciuto come nome di cmdlet, funzione, programma eseguibile o file script. Controllare
l'ortografia del nome o verificare che il percorso sia incluso e corretto, quindi riprovare.
In riga:1 car:1
+ dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery-back ...
+ ~~
+ CategoryInfo : ObjectNotFound: (dd:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Did anyone get the same problem?
Could you help me to find a way to go on?
ops, I'm sorry...
this sentence
Termine 'dd' non riconosciuto come nome di cmdlet, funzione, programma eseguibile o file script. Controllare
l'ortografia del nome o verificare che il percorso sia incluso e corretto, quindi riprovare.
In riga:1 car:1
means...
The term 'dd' is not recognized as a cmdlet, function, executable program or script file name. to check spelling the name or verify that the path is included and correct, then try again. Per row: 1 car: 1
You have to run any of Androd's Linux commands in a Linux shell started by ADB
Code:
adb shell "dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery-backup.img bs=2048"
yes, now it works!
thank you... now I'm from xubuntu.

ADB DELETE at the command prompt

Alguém pode me dizer o que acontece se eu usar este comando no prompt de comando "ADB DELETE no prompt de comando" do widowns?

Categories

Resources