Database Info

[GUIDE] REcovery for Sony xperia c3 D2533 locked bootloader LOLLIPOP

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.

Le Pro3 AI X650 EUI5.9_25S streamlined ROOT V4

Le Pro3 AI version X650 EUI5.9_25S streamlined ROOT V4
1.31 GB
letv-x650-7to-twrp3.1-recovery-new
19.4 MB
Update log:
Based on the official 25S unpack optimization, the ROM main streamlined, suitable for like the original friend
Maintain the official input method and store and the necessary procedures
Repair official yellow box problem (mandfx & winter)
Streamline redundant programs and residual files
Modify the kernel to add init.d support
Change kernel selinux status to permissive
Built-in viper sound
Update the busybox component
Add ROOT Privilege Pro, perfect ROOT
Other features of their own experience.
Android version: 6.0.1
Updated on: 2017-05-02
Applicable models: Le Pro3 AI version X650
original link

1.) Copy ROM to your phone
2.) install the adb fastboot on the pc
3) Unlocking:
Go to Settings -> About -> Hit Build 7 times
Go to Settings -> Developer Options -> Enable OEM unlocking
Run 'adb reboot bootloader'
Use 'fastboot oem unlock'
4.) Install TWRP via fastboot
5.) Go in TWRP (WIPE - Dalvik/caсhe, Data, и Cache.)
6.) Installing the ROM
7.) The first boot and set your phone.

А русский язык в прошивке есть?

Когда появится Кастом?кто то знает?

vadanorsk said:
а русский язык в прошивке есть?
Click to expand...
Click to collapse
нет.
flixxxua1 said:
когда появится кастом?кто то знает?
Click to expand...
Click to collapse
в настоящее время ничего, кроме этого.

Who know, where whill been castom ROM to Leeco LEX650

Someone has an account here.
bbs.ydss.cn/forum.php?mod=vie...&pe=1&mobile=2
It seems like it's a new rom.

Its a fake or the author remove the link, anyways the post it's from few months ago

angelusx85 said:
Someone has an account here.
bbs.ydss.cn/forum.php?mod=vie...&pe=1&mobile=2
It seems like it's a new rom.
Click to expand...
Click to collapse
Maybe you give not bad link

sorry, I have set myself apart

can i apply this on my LeEco Pro 3 AI Edition LEX653?

LeEco Le Pro 3 AI (X650 ) - IMEI Lost
laikexpert said:
Le Pro3 AI version X650 EUI5.9_25S streamlined ROOT V4
1.31 GB
letv-x650-7to-twrp3.1-recovery-new
19.4 MB
Update log:
Based on the official 25S unpack optimization, the ROM main streamlined, suitable for like the original friend
Maintain the official input method and store and the necessary procedures
Repair official yellow box problem (mandfx & winter)
Streamline redundant programs and residual files
Modify the kernel to add init.d support
Change kernel selinux status to permissive
Built-in viper sound
Update the busybox component
Add ROOT Privilege Pro, perfect ROOT
Other features of their own experience.
Android version: 6.0.1
Updated on: 2017-05-02
Applicable models: Le Pro3 AI version X650
original link
Click to expand...
Click to collapse
Hello, I need some help.
I got a brand new X650 (4GB/64GB) two days ago and tried TWRP from laikexpert in fastboot mode (not flashed).
This was just to see if it is a suitable candidate for flash. TWRP loaded succesfully, but was completely in chinese and did not respond on touch. MTP with PC worked.
Only choice to get out of this was long press of power-button. Even I did not flash or did anything else, Phone got stucked in first leeco screen.
Stock Recovery was still ok. I tried to perform factory reset but it did not succeed.
Maybe I mistook something with stock recovery but when I checked back later with fastboot of TWRP 3.1 from laikexpert i could see at my PC that all files were gone from phone except an empty TWRP-Folder was there.
After this I tried other older TWRP (LePro3AI_TWRP_3.0.3_recovery) from other post which had standard user interface in english and responded almost normally. I did a backup from what was remained in the phone and copied it to my PC. Afterwards I flashed this TWRP 3.0.3.
Finally I decided to flash "Le Pro3 AI version X650 EUI5.9_25S streamlined ROOT V4" which succeded in booting system, but now I am without IMEI. Means my phone is perfectly rooted and has somehow custom-ROM, but without IMEI and therefore is useless.
Can somebody help me out ?
fastboot ok
TWRP (LePro3AI_TWRP_3.0.3_recovery)
TWRP backup with unknown status before I flashed new ROM
Le Pro3 AI version X650 EUI5.9_25S streamlined ROOT V4
no IMEI in phone, only hardcopy of IMEI-label from backside of phone

X650 4gb/64gb
123Bart said:
Hello, I need some help.
Click to expand...
Click to collapse
The zip-file from the linked thread below restored my phone. IMEI's are back. Phone is operational again but is now EUI 25S CN
(english language is available)
It is not exactly as before, because in fastboot it was named somehow "X650-oversea" before the mess.
Now it is changed to "whole netcom".
"Le Pro3 AI X650 EUI5.9_25S install ROM via Fastboot" the other link from laikexpert
https://forum.xda-developers.com/le...e-pro3-ai-x650-eui5-925s-install-rom-t3716920

123Bart said:
The zip-file from the linked thread below restored my phone. IMEI's are back. Phone is operational again but is now EUI 25S CN
(english language is available)
It is not exactly as before, because in fastboot it was named somehow "X650-oversea" before the mess.
Now it is changed to "whole netcom".
"Le Pro3 AI X650 EUI5.9_25S install ROM via Fastboot" the other link from laikexpert
https://forum.xda-developers.com/le...e-pro3-ai-x650-eui5-925s-install-rom-t3716920
Click to expand...
Click to collapse
If you can flash by fastboot, you can try to install twrp again and flash magisk for root, if something goes wrong, you can restore the phone again via fastboot.

Toni Moon said:
If you can flash by fastboot, you can try to install twrp again and flash magisk for root, if something goes wrong, you can restore the phone again via fastboot.
Click to expand...
Click to collapse
I tried already flash of TWRP succesfully afterwards of fastboot restore, but TWRP asks for password and could only be used in read only mode.
Phone has encrypted data partition after fastboot restore with "leecopro3 ai.zip ". I tried "default_password" and also method with setting PIN in restored phone and tried this PIN for TWRP, but without being successful in both cases.
I formatted data partition and reflashed "streamlined Root v4" again, but than again both IMEI are blank.
Would flash of "STOP_Orange+_state+S20.zip" and "no-verity-opt-encrypt.zip" help against blank IMEI in streamlined rom?
Any idea how to continue ?

X650
Toni Moon said:
If you can flash by fastboot, you can try to install twrp again and flash magisk for root, if something goes wrong, you can restore the phone again via fastboot.
Click to expand...
Click to collapse
Ok, I flashed again the LePro3AI_TWRP_3.0.3_recovery. Due to encrypted data partition I formatted data partition, rebooted into TWRP and put Magisk on the now available data partition.
Flash of Magisk was succesful, reboot also !
Only thing is, that english language was gone due to formatted partition, but meanwhile I know where to touch to come inside the menues.
Magisk was not there and no GSM and no IMEI was available.
Now I am back with leecopro3 ai.zip method.

you're doing something wrong, try this twrp, works fine for me:
https://mega.nz/#!tfJn2J7B!Ggtdd_pTFA1-JLUERllhpspFrE_NY9CR-f2zcfW_0dc
you must wipe all before flash

Toni Moon said:
you're doing something wrong, try this twrp, works fine for me:
https://mega.nz/#!tfJn2J7B!Ggtdd_pTFA1-JLUERllhpspFrE_NY9CR-f2zcfW_0dc
you must wipe all before flash
Click to expand...
Click to collapse
Thanks for your assistance
I flashed it but it is in chinese language which I can not read. In flashed condition screen touch works perfect.
Is it possible to change this TWRP to english ?
If so can you guide me to the menue to set to english?

123Bart said:
Thanks for your assistance
I flashed it but it is in chinese language which I can not read. In flashed condition screen touch works perfect.
Is it possible to change this TWRP to english ?
If so can you guide me to the menue to set to english?
Click to expand...
Click to collapse
youtube:
https://www.youtube.com/watch?v=vxPeYJYsUYU
Mira aquí:
Le Pro3 AI X650 EUI5.9_25S simplificado ROOT V4
P.S.
1.) Desbloquee el gestor de arranque
2.) Instale TWRP a través de fastboot
3.) Vaya a TWRP. Weip: WIPE - Dalvik / cace, Datos y Caché.
4.) Instale el firmware
5.) La primera descarga y configure el teléfono.

Toni Moon said:
youtube:
https://www.youtube.com/watch?v=vxPeYJYsUYU
Mira aquí:
Le Pro3 AI X650 EUI5.9_25S simplificado ROOT V4
P.S.
1.) Desbloquee el gestor de arranque
2.) Instale TWRP a través de fastboot
3.) Vaya a TWRP. Weip: WIPE - Dalvik / cace, Datos y Caché.
4.) Instale el firmware
5.) La primera descarga y configure el teléfono.
Click to expand...
Click to collapse
Your linked Youtube video is for classical TWRP which I know well, but please see my screenshot in my previous post. It has completely different user interface and look

its say: SW REV. Check fail(Bootloader) Device 2 binary 1

i want to get back to nougat. so i using odin for flash old rom file. but its say: SW REV. Check fail(Bootloader) Device 2 binary 1. now this. what can i do for back to nougat from oreo. pls help me.

I had the same issue but the only way i found was to flash through odin without the BL file selected then you will get nougat to install but you will loose "IMEI" and will show "NULL" in settings.
Even with a "EFS" backup trying to reinstall the EFS backup through TWRP no IMEI will show up something in the bootloader has disabled the downgrade process.
I has to give up and reinstall oreo and boom IMEI is back.
Sorry i can't be more help

sobuj0191888 said:
i want to get back to nougat. so i using odin for flash old rom file. but its say: SW REV. Check fail(Bootloader) Device 2 binary 1. now this. what can i do for back to nougat from oreo. pls help me.
Click to expand...
Click to collapse
you are tryng to flash a older bootloader on top of a newer one is what it looks like to me what is your current firmware installed?

Do not get complicated with this issue, to solve it permanently, install the following kernel TGPKernel.G95xx.v2.8.1.20180816.zip with the can do what they want, I have a sm-g955fd install it with twrp and go! the blocks are over. Greetings from Panama.
No se compliquen con este tema, para solucionarlo definitivamente, instalen el siguiente kernel TGPKernel.G95xx.v2.8.1.20180816.zip con el pueden hacer lo que quieran, yo tengo un sm-g955fd lo instale conel twrp y listo! se acabaron los bloqueos. saludos desde Panamá.
Página del Kernel en su ultima versión para Oreo.
https://forum.xda-developers.com/ga...-device-development/kernel-tgpkernel-t3654423
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
iNeoTom said:
I had the same issue but the only way i found was to flash through odin without the BL file selected then you will get nougat to install but you will loose "IMEI" and will show "NULL" in settings.
Even with a "EFS" backup trying to reinstall the EFS backup through TWRP no IMEI will show up something in the bootloader has disabled the downgrade process.
I has to give up and reinstall oreo and boom IMEI is back.
Sorry i can't be more help
Click to expand...
Click to collapse
Do not get complicated with this issue, to solve it permanently, install the following kernel TGPKernel.G95xx.v2.8.1.20180816.zip with the can do what they want, I have a sm-g955fd install it with twrp and go! the blocks are over. Greetings from Panama.
No se compliquen con este tema, para solucionarlo definitivamente, instalen el siguiente kernel TGPKernel.G95xx.v2.8.1.20180816.zip con el pueden hacer lo que quieran, yo tengo un sm-g955fd lo instale conel twrp y listo! se acabaron los bloqueos. saludos desde Panamá.
Página del Kernel en su ultima versión para Oreo.
https://forum.xda-developers.com/ga...-device-development/kernel-tgpkernel-t3654423

Bootloop after updating TWRP? From MIUI official, BLU unlocked

I recently iinstalled a newer version of TWRP 5, after that i eperience bootloop and it boots automatically to recovery (TWRP). I tried wiping and factory reset, flashing a custom ROM, dowgrading TWRP to 3, still reboots to recovery? I dont have a windows machine, and I dont think I should need MIflashtool after BL unlocking?

ven1x said:
Recentemente ho installato una versione più recente di TWRP 5, dopodiché ho provato il bootloop e si avvia automaticamente al ripristino (TWRP). Ho provato a cancellare e ripristinare le impostazioni di fabbrica, eseguire il flashing di una ROM personalizzata, aggiornare TWRP a 3, riavvio ancora per il ripristino? Non ho una macchina Windows e non penso che dovrei aver bisogno di MIflashtool dopo lo sblocco BL?
Click to expand...
Click to collapse

Hi, I read what happened I have some experience in TWRP I think the Windows machine takes and you will have to start all over again I'll explain you example: I installed 3.1.1-0 and after that I flash then the personal rom bla bla and I backup and save in SDcard which helps a reset and after months I decide in the app. TWRP download 3.1.1-2.img and flash and .img does not always go to download folder so I have not used the cmd for this I have done with app. however there is because the file 3.1.1-2.img is compatible so there is no need for another backup instead from 3.1.1-0.img I download 3.2.3.img then I have to make another backup because in addition to being an emulator the software is different so I have to backup this because it has to read the ROM firmware because TWRP doesn't know what I did too I have a Rom is ViperOS on j5lte I had 3.1.1-1-j5lte.img tar i used odin 3 to download 3.4.0.-0-img.tar after i went into TWRP and goodbye backup and this made me understand error.

Braain said:
Hi, I read what happened I have some experience in TWRP I think the Windows machine takes and you will have to start all over again I'll explain you example: I installed 3.1.1-0 and after that I flash then the personal rom bla bla and I backup and save in SDcard which helps a reset and after months I decide in the app. TWRP download 3.1.1-2.img and flash and .img does not always go to download folder so I have not used the cmd for this I have done with app. however there is because the file 3.1.1-2.img is compatible so there is no need for another backup instead from 3.1.1-0.img I download 3.2.3.img then I have to make another backup because in addition to being an emulator the software is different so I have to backup this because it has to read the ROM firmware because TWRP doesn't know what I did too I have a Rom is ViperOS on j5lte I had 3.1.1-1-j5lte.img tar i used odin 3 to download 3.4.0.-0-img.tar after i went into TWRP and goodbye backup and this made me understand error.
Click to expand...
Click to collapse
ok let me try to understand, youre saying backups across different TWRP versions cannot be applied and cause bootloop?
My guess is, TWRP (some or any version) doesnt completely wipe (my Google account was still logged in after I got it working again) and I heard Orangefox recovery might be safer for MIUI devices

ven1x said:
ok let me try to understand, youre saying backups across different TWRP versions cannot be applied and cause bootloop?
My guess is, TWRP (some or any version) doesnt completely wipe (my Google account was still logged in after I got it working again) and I heard Orangefox recovery might be safer for MIUI devices
Click to expand...
Click to collapse
Hi, Fox for MiUi can solve some annoyance also on YouTube there are demonstrationd

I need some advice to downgrade my Galaxy A10S [A107M]

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