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, 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