Related
Hola esta ves en un tutorial de como instalar recovery en pc xperia c3 bootloader lock
1-. ser usuario root
2-. descargar archivos desde la pagina del desarrollador nuts
-ingresar a la pagina http://nut.xperia-files.com/ luego seleccionar XZDUALRECOVERY, LUEGO XZDUALRECOVERY 2.8.20 Y DESCARGAR T2U-lockeddualrecovery2.8.20-RELEASE.installer
una vez descargado el archivo "T2U-lockeddualrecovery2.8.20-RELEASE.installer" lo descrompimen les aparesera una nueva carpeta llamada T2U-lockeddualrec.... la abren una vez dentro de ella conectan su celular al pc (modo depuracion usb deve estar activo) y abren la ventana install una vez abierta la ventana aplican el metodo N°1 y listo esperar a que el proceso termine correctamente se reiniciara el celular prendera un led azul y ya estaran dentro del recovery
agradecimientos a #Nuts
Hi this see a tutorial on how to install recovery in xperia c3 pc bootloader lock
1-. be root
2-. download files from the product developer's nuts
-Enter a page http://nut.xperia-files.com/ then select XZDUALRECOVERY, THEN AND DOWNLOAD XZDUALRECOVERY 2.8.20 T2U-lockeddualrecovery2.8.20-RELEASE.installer
once downloaded the "T2U-lockeddualrecovery2.8.20-RELEASE.installer" file is descrompimen aparesera them a new folder called T2U-lockeddualrec .... the open once inside it connect your phone to PC (USB debugging mode deve be active ) and install the window open window open after applying the method No. 1 and ready to wait for the process to complete successfully the phone will turn on a blue lED will reboot and you will be within the recovery
thanks to #Nuts
[Deleted]
abc
work on c3 d2502 ?
perfectoo! funciono, al fiin habrán nuevos mod para nuestro telefonoo
exTALIA said:
My C3 D2533 successfully installed
Click to expand...
Click to collapse
I do not know King d2533 have a thing to try is xd
pelao160312 said:
Hola esta ves en un tutorial de como instalar recovery en pc xperia c3 bootloader lock
1-. ser usuario root
2-. descargar archivos desde la pagina del desarrollador nuts
-ingresar a la pagina http://nut.xperia-files.com/ luego seleccionar XZDUALRECOVERY, LUEGO XZDUALRECOVERY 2.8.20 Y DESCARGAR T2U-lockeddualrecovery2.8.20-RELEASE.installer
una vez descargado el archivo "T2U-lockeddualrecovery2.8.20-RELEASE.installer" lo descrompimen les aparesera una nueva carpeta llamada T2U-lockeddualrec.... la abren una vez dentro de ella conectan su celular al pc (modo depuracion usb deve estar activo) y abren la ventana install una vez abierta la ventana aplican el metodo N°1 y listo esperar a que el proceso termine correctamente se reiniciara el celular prendera un led azul y ya estaran dentro del recovery
agradecimientos a #Nuts
Hi this see a tutorial on how to install recovery in xperia c3 pc bootloader lock
1-. be root
2-. download files from the product developer's nuts
-Enter a page http://nut.xperia-files.com/ then select XZDUALRECOVERY, THEN AND DOWNLOAD XZDUALRECOVERY 2.8.20 T2U-lockeddualrecovery2.8.20-RELEASE.installer
once downloaded the "T2U-lockeddualrecovery2.8.20-RELEASE.installer" file is descrompimen aparesera them a new folder called T2U-lockeddualrec .... the open once inside it connect your phone to PC (USB debugging mode deve be active ) and install the window open window open after applying the method No. 1 and ready to wait for the process to complete successfully the phone will turn on a blue lED will reboot and you will be within the recovery
thanks to #Nuts
Click to expand...
Click to collapse
Will it work with latest lollipop firmware?
cezer kiran said:
Will it work with latest lollipop firmware?
Click to expand...
Click to collapse
Yes, it works perfectly in lollipop and latest firmware
Hello, I have the same version of Android (19.3.A.0.472) and phone (D2533) and samples in the images. I haver root with KingRoot, however, will not let me install the recovery. I get only errors and have all the drivers installed. If you can tell me what kind of ROOT you are using, it would help a lot.
UPDATE: I updated my ADB and Fastboot and that I could install without problems. Thank you very much for this excellent contribution
What kind of Root used to install the Recovery?
Hi, I'm using the Installer T2U: T2U-lockeddualrecovery2.8.21-RELEASE.installer.zip (http://nut.xperia-files.com/)
Perhaps the problem lies in the type of root that I am using, which is KingRoot. In that application I can see that automatically permits the ADB for implementation is given, so therefore I believe that while my phone is rooted, the problem may be in the form of grants read-write access to the system.
So I wonder what kind of root you used for version 5.0.1 Lollipop (D2533_19.3.A.0.472_AU.ftf) to which you installed the Recovery successfully
SOLVED: I updated my ADB and Fastboot and that I could install without problems. Thank you very much for this excellent contribution
iceman2029 said:
hi, i'm using the installer t2u: T2u-lockeddualrecovery2.8.21-release.installer.zip (http://nut.xperia-files.com/)
perhaps the problem lies in the type of root that i am using, which is kingroot. In that application i can see that automatically permits the adb for implementation is given, so therefore i believe that while my phone is rooted, the problem may be in the form of grants read-write access to the system.
So i wonder what kind of root you used for version 5.0.1 lollipop (d2533_19.3.a.0.472_au.ftf) to which you installed the recovery successfully
solved: I updated my adb and fastboot and that i could install without problems. Thank you very much for this excellent contribution
Click to expand...
Click to collapse
great change to supersu bro
iceman2029 said:
Hi, I'm using the Installer T2U: T2U-lockeddualrecovery2.8.21-RELEASE.installer.zip ()
Perhaps the problem lies in the type of root that I am using, which is KingRoot. In that application I can see that automatically permits the ADB for implementation is given, so therefore I believe that while my phone is rooted, the problem may be in the form of grants read-write access to the system.
So I wonder what kind of root you used for version 5.0.1 Lollipop (D2533_19.3.A.0.472_AU.ftf) to which you installed the Recovery successfully
SOLVED: I updated my ADB and Fastboot and that I could install without problems. Thank you very much for this excellent contribution
Click to expand...
Click to collapse
Hi! im also rooted with Kingroot, how did you do it? wich option did you use ? thanks =)
tiencuong said:
work on c3 d2502 ?
Click to expand...
Click to collapse
Yes it works well
Lesigh. Unable to root 19.4.A.0.182 with Nut's T2U root tool V2.8.21 and V2.8.23. Stuck at step, no binaries installed on phone.
Hello, will this work on D2533 with Kingroot? Sorry I am a newbie on these kind of things.
Nekoneki said:
Hello, will this work on D2533 with Kingroot? Sorry I am a newbie on these kind of things.
Click to expand...
Click to collapse
You're on KingRoot? Try this guide first http://androidmtk.com/replace-kinguser-with-supersu to get SuperSU. Then use this updated guide for recoveries and stuff http://forum.xda-developers.com/sony-xperia-c/help/comprehensive-guide-rooting-flashing-c3-t3277939
Ahahahahha.... My phone went on bootloop. I can't download ftf because of my ISP's data cap. I'm 80% doomed.
---------- Post added at 01:18 AM ---------- Previous post was at 01:12 AM ----------
AutumQueen92 said:
You're on KingRoot? Try this guide first http://androidmtk.com/replace-kinguser-with-supersu to get SuperSU. Then use this updated guide for recoveries and stuff http://forum.xda-developers.com/sony-xperia-c/help/comprehensive-guide-rooting-flashing-c3-t3277939
Click to expand...
Click to collapse
Please help D:
Nekoneki said:
Ahahahahha.... My phone went on bootloop. I can't download ftf because of my ISP's data cap. I'm 80% doomed.
---------- Post added at 01:18 AM ---------- Previous post was at 01:12 AM ----------
Please help D:
Click to expand...
Click to collapse
Write down the steps and what you were doing until you encountered a bootloop.
AutumQueen92 said:
Write down the steps and what you were doing until you encountered a bootloop.
Click to expand...
Click to collapse
I pressed the "update" button on the superSU as I remembered. That was the dumbest move I did.
Nekoneki said:
I pressed the "update" button on the superSU as I remembered. That was the dumbest move I did.
Click to expand...
Click to collapse
That's weird. SuperSU update shouldn't do that at all. You will need to flash a new firmware to get out of the bootloop unless you already have a recovery.
AutumQueen92 said:
That's weird. SuperSU update shouldn't do that at all. You will need to flash a new firmware to get out of the bootloop unless you already have a recovery.
Click to expand...
Click to collapse
I can't download firmwares 800MB and up. I'll try to flash a newer firmware as soon as possible. Thank you for your advices.
guys help, I'm desperate
I was pretty much in stock rom l29c432b192
have this flash TWRP whit:
1- Download These 3 files (update.zip, update_full_hw_eu.zip, supersu_v2.79_sr2.zip)
1.1- http://update.hicloud.com:8180/TDS/d...ull/update.zip
1.2- http://update.hicloud.com:8180/TDS/d...full_hw_eu.zip
1.3- http://www.sillanwali.com/downloads/..._v2.79_sr2.zip
hi have wipe sistem, my phone no charge system
Fail dload medod
Fail unbrick fastboot metod, this complete total but the sistem no works
i do not have other metod
help my
fastbbot works
bootloader works
recovery works
system is found
system does not charge
Try DC Phoenix, search google for it.If any attempt of you with other methods fail, this should do the job.
GUKA81 said:
guys help, I'm desperate
I was pretty much in stock rom l29c432b192
have this flash TWRP whit:
1- Download These 3 files (update.zip, update_full_hw_eu.zip, supersu_v2.79_sr2.zip)
1.1- http://update.hicloud.com:8180/TDS/d...ull/update.zip
1.2- http://update.hicloud.com:8180/TDS/d...full_hw_eu.zip
1.3- http://www.sillanwali.com/downloads/..._v2.79_sr2.zip
hi have wipe sistem, my phone no charge system
Fail dload medod
Fail unbrick fastboot metod, this complete total but the sistem no works
i do not have other metod
help my
fastbbot works
bootloader works
recovery works
system is found
system does not charge
Click to expand...
Click to collapse
Erecovery tried...?
I have an L09, but the only advice I can give is try different files. I had a lot of issues flashing things trying to get to 7.0 and I flashed the same version of the same images multiple times, but for some reason certain files did not seem to work. After trying other people's links eventually I found a post in which all links flashed through in a breeze and without issue.
thanks a lot for you support friend.
i have succeeded whith dc phoenix second medod.
problem partition memory system.
ok 15 euro,but restore my device
GUKA81 said:
thanks a lot for you support friend.
i have succeeded whith dc phoenix second medod.
problem partition memory system.
ok 15 euro,but restore my device
Click to expand...
Click to collapse
Perhaps it was possible to make without dc phoenix, I had the same issue like you, you saw it. I said you that I had used the dload method and factory reset after... but I forgot to say you, I've also repair several partitions (system - data - cust) via the TWRP. I made it before.
Sorry to have forgotten... maybe This you will have avoided to spend 15€.
hi friend.. Phoenix IS only medod becouse is impossible works twrp but touch screen not works.
Impossible use twrp o normal recovery
GUKA81 said:
hi friend.. Phoenix IS only medod becouse is impossible works twrp but touch screen not works.
Impossible use twrp o normal recovery
Click to expand...
Click to collapse
So we hadn't the same issue.
franzyroy said:
So we hadn't the same issue.
Click to expand...
Click to collapse
we used the same zip, but I was in Android miui 6 and 4 and I did delete system
so I assume the problem
at most; serious;
Patience 15 Euros, fortunately I recovered the phone
GUKA81 said:
we used the same zip, but I was in Android miui 6 and 4 and I did delete system
so I assume the problem
at most; serious;
Patience 15 Euros, fortunately I recovered the phone
Click to expand...
Click to collapse
OK
Para que funcione Dload tienes que tener instalada y no dañada el recovery stock de la versión ROM que tiene tu teléfono, y segundo tener la versión ROM de tu Modelo NXT-L29 C432 BXXX Asegurate de cargar la carpeta dload en la raíz con el archivo .zip de tu version (29c432)
Enviado desde mi HUAWEI NXT-L29 mediante Tapatalk
which twrp are you using?
which is more stable?
Well as you are only using TWRP at the instant when you are flashing ROMs / rooting, no need to worry about stability. As far as I know TWRP, no matter what version, will not / very rarely , crash while flashing, as long as you install them correctly.
By the way what model is your phone?
LR7875 said:
Bem, como você está usando o TWRP apenas no instante em que está atualizando ROMs / enraizando, não precisa se preocupar com a estabilidade. Pelo que eu sei, o TWRP, não importa a versão, não irá / muito raramente travará durante a atualização, contanto que você os instale corretamente.
Aliás, qual é o modelo do seu telefone?
Click to expand...
Click to collapse
I have a Poco f3
Well carefully follow the instructions of installation of the TWRP.
You may need to disable vertified boot( if you don't know, ask further below)
i cant seem to find a stable twrp that will install. im rooted with magisk on my N985F running android 11. twrp doesnt even have my phone model on their device section of their website. i tried installing twrp from several places and ended up bricking my phone several times. i was able to bring it back to stock and reroot. but i need to fix the bluetooth issue with the watch and i know how to flash the the file in twrp.. been doing this on and off for years. just cant find a twrp or twrp alternative that is compatible. maybe i can edit one for my phone? im pretty frustrated. ive rooted last year with Dr. Ketan. i still owe him a beer from helping me then.
First I want to know if it's worth the risk, because the last time I've rooted a device was a moto g2 back in 2015, and afaik Galaxy devices are easy to brick.
I want to do it because Android 11 it's a mess and bad optimized to A10S. Since the last update my phone just got worse, and since a week ago it just closes almost every app without even warning.
I can't even open something like a browser without a 2 min loading.
I want to know if downgrading can make it less heavier, and if yes, I want at least to know if it's worth using an old original SO (Android 9 or 10), or if it's better using a custom ROM.
From what i understand there are no custom roms for a107m, it doesn't even come twrp. I tried and my phone went into hard brick but luckily I revived it.
When I managed to revive my device, it went up to binary 5, so I had to put Android 10. The problem with this is that I can't open the camera and I don't know if I can go back to Android 9 (the one I had originally) due to the binary . That is my situation. If you know any solution to my problem, I would appreciate it.
Sorry for my bad english.
MolhodeSoja said:
First I want to know if it's worth the risk, because the last time I've rooted a device was a moto g2 back in 2015, and afaik Galaxy devices are easy to brick.
I want to do it because Android 11 it's a mess and bad optimized to A10S. Since the last update my phone just got worse, and since a week ago it just closes almost every app without even warning.
I can't even open something like a browser without a 2 min loading.
I want to know if downgrading can make it less heavier, and if yes, I want at least to know if it's worth using an old original SO (Android 9 or 10), or if it's better using a custom ROM.
Click to expand...
Click to collapse
Downgrading is not possible unless the binary of the downgraded firmware is equal to the binary of the currently installed firmware. If the binary of the downgraded firmware is lower than the binary of your currently installed firmware, you will not be able to downgrade. No, there are no "tricks" to bypass the binary block, it is not possible.
H
Mely Gamer said:
From what i understand there are no custom roms for a107m, it doesn't even come twrp. I tried and my phone went into hard brick but luckily I revived it.
When I managed to revive my device, it went up to binary 5, so I had to put Android 10. The problem with this is that I can't open the camera and I don't know if I can go back to Android 9 (the one I had originally) due to the binary . That is my situation. If you know any solution to my problem, I would appreciate it.
Sorry for my bad english.
Click to expand...
Click to collapse
Camera may not be working due to leftover data from the previous system, if this is the cause of the issue, try booting into stock recovery and choose the factory reset option then choose the wipe cache partition option then reboot the device.
If the binary of the android 9 firmware is the same as the binary of your currently installed android 10 firmware, you should be able to downgrade to the android 9 firmware.
Droidriven said:
H
Camera may not be working due to leftover data from the previous system, if this is the cause of the issue, try booting into stock recovery and choose the factory reset option then choose the wipe cache partition option then reboot the device.
If the binary of the android 9 firmware is the same as the binary of your currently installed android 10 firmware, you should be able to downgrade to the android 9 firmware.
Click to expand...
Click to collapse
I have a problem because I try to enter the recovery mode and apparently I do not have it, because it does not enter (when my a10s got hard brick I had tried to flash a twrp recovery)
Mely Gamer said:
I have a problem because I try to enter the recovery mode and apparently I do not have it, because it does not enter (when my a10s got hard brick I had tried to flash a twrp recovery)
Click to expand...
Click to collapse
Extract the stock recovery.img from the firmware file then use it to create an Odin flashable .tar by using 7zip to compress the recovery.img into .tar format using the highest level of compression. Then flash the newly created recovery.img.tar via Odin. Place the recovery.img.tar in the AP slot.
Then see if you can boot into stock recovery.
Droidriven said:
Extraiga el archivo recovery.img del archivo de firmware y luego úselo para crear un .tar flasheable de Odin usando 7zip para comprimir el recovery.img en formato .tar usando el nivel más alto de compresión. Luego actualice el recovery.img.tar recién creado a través de Odin. Coloque recovery.img.tar en la ranura AP.
Luego, vea si puede iniciar la recuperación de valore
Click to expand...
Click to collapse
ok, acabo de mostrar la recuperación de stock y todavía no entra.
Mely Gamer said:
ok, acabo de mostrar la recuperación de stock y todavía no entra.
Click to expand...
Click to collapse
Hmm...Strange.
Try flashing the full stock firmware again.
Droidriven said:
Downgrading is not possible unless the binary of the downgraded firmware is equal to the binary of the currently installed firmware. If the binary of the downgraded firmware is lower than the binary of your currently installed firmware, you will not be able to downgrade. No, there are no "tricks" to bypass the binary block, it is not possible.
Click to expand...
Click to collapse
Oh boy, this is sad to read. My friend told me that the newest Samsung UI was developed to run on their high-end phones and this made me a little upset to why they insisted on bringing it to weaker devices. If I could just override it with another UI or an new rom, my life would be a lot easier
Droidriven said:
Hmm ... Extraño.
Intente actualizar el firmware completo de nuevo.
Click to expand...
Click to collapse
Logré acceder a la recuperación restableciendo de fábrica el teléfono celular, pero la cámara aún no funciona ...
Hello, does anyone know how to root the A127M U7? This is the build version A127MUBS7BVJ2 (Android 12)
AlexGWM said:
Hello, does anyone know how to root the A127M U7? This is the build version A127MUBS7BVJ2 (Android 12)
Click to expand...
Click to collapse
Yeah, the same way you root all the A12s
Look around the A12 forum, and there are a lot of ways.
AlexGWM said:
Hello, does anyone know how to root the A127M U7? This is the build version A127MUBS7BVJ2 (Android 12)
Click to expand...
Click to collapse
Root on most Samsung devices works pretty much the same. Enable developer options, enable OEM Unlocking, reboot to download mode, unlock the bootloader. From this point it gets a bit more complicated - if TWRP is not available for your device, you have to patch the AP file in Magisk, then flash with Odin.
Edit: Please make sure you use the Search functions and browse existing threads as the answer you need may already be available.
Here is the unofficial TWRP thread for your device.
V0latyle said:
Root en la mayoría de los dispositivos Samsung funciona más o menos igual. Habilite las opciones de desarrollador, habilite el desbloqueo OEM, reinicie en modo de descarga, desbloquee el gestor de arranque. A partir de este punto, se vuelve un poco más complicado: si TWRP no está disponible para su dispositivo, debe parchear el archivo AP en Magisk y luego flashear con Odin.
Editar: asegúrese de usar las funciones de búsqueda y explore los hilos existentes, ya que es posible que la respuesta que necesita ya esté disponible.
Aquí está el hilo TWRP no oficial para su dispositivo.
Click to expand...
Click to collapse
Thank you, my problem is that when I try to put a file patched with magisk it stays in the download, it gives me boot error
My problem really is that I have binary 7, I don't know how to do it there.
did you use 25.1 patched magisk? or 23.0 patched magisk?
If you used 25.1, patch the whole ap, not just the boot img
If you use 23.0, install 25.1 patched magisk.
TheWorldYT said:
did you use 25.1 patched magisk? or 23.0 patched magisk?
If you used 25.1, patch the whole ap, not just the boot img
If you use 23.0, install 25.1 patched magisk.
Click to expand...
Click to collapse
I used 25.1
Do I patch only the AP? It's what I did, don't patch the BL.
AlexGWM said:
I used 25.1
Do I patch only the AP? It's what I did, don't patch the BL.
Click to expand...
Click to collapse
huh? did you unlock bootloader and flash the patched ap with odin?
Follow the instructions in the thread I linked to flash TWRP, then once you're booted into TWRP, flash Magisk.
V0latyle said:
Siga las instrucciones en el hilo que vinculé para flashear TWRP, luego, una vez que haya iniciado TWRP, flashee Magisk.
Click to expand...
Click to collapse
Okay
V0latyle said:
Follow the instructions in the thread I linked to flash TWRP, then once you're booted into TWRP, flash Magisk.
Click to expand...
Click to collapse
You cannot boot to twrp without custom vbmeta. Install magisk before installing twrp or your device will have a DTB Load Fail
AlexGWM said:
Okay
Click to expand...
Click to collapse
Don't follow the tutorial he gave. It is incorrect and it will result into a DT Load Fail, and you will lose all your data.
TheWorldYT said:
You cannot boot to twrp without custom vbmeta. Install magisk before installing twrp or your device will have a DTB Load Fail
Click to expand...
Click to collapse
Ah, thanks for the clarification
TheWorldYT said:
Don't follow the tutorial he gave. It is incorrect and it will result into a DT Load Fail, and you will lose all your data.
Click to expand...
Click to collapse
Samsung changes a lot with their devices so it's impossible to stay atop everything. Most of my Samsung experience is with devices that accept a custom recovery binary with no other modifications, except maybe Multidisabler
V0latyle said:
Ah, thanks for the clarification
Samsung changes a lot with their devices so it's impossible to stay atop everything. Most of my Samsung experience is with devices that accept a custom recovery binary with no other modifications, except maybe Multidisabler
Click to expand...
Click to collapse
That's actually quite true, I remember the phones before the S6 and how it didn't even need a vbmeta and now these days, you need a custom vbmeta or it will result in a DT Load Fail.
TheWorldYT said:
Don't follow the tutorial he gave. It is incorrect and it will result into a DT Load Fail, and you will lose all your data.
Click to expand...
Click to collapse
Thank you, I had not done it yet, everything did not seem correct to me and I preferred to continue looking for information.
TheWorldYT said:
You cannot boot to twrp without custom vbmeta. Install magisk before installing twrp or your device will have a DTB Load Fail
Click to expand...
Click to collapse
Do I need to create the custom vbmeta? Or after installing Magisk it is no longer necessary?
AlexGWM said:
Do I need to create the custom vbmeta? Or after installing Magisk it is no longer necessary?
Click to expand...
Click to collapse
after installing magisk, it is no longer nessecary.