Database Info

ViperOS acesso root

Good evening. I installed my ViperOS after all the procedures suggested in the forums. I have a Moto G2 (XT1078 Thea 4G), unlocked the bootloader, did the root process and checked with the root checker. Being OK, I followed the step by step and managed to install the Viper. I am very satisfied but after having the curiosity to verify the root checker with it installed, I verified that I do not have root access anymore. This is normal? How do I proceed?

mcbfelipe said:
Boa noite. Instalei minha ViperOS após todos os procedimentos sugeridos nos fóruns. Tenho um Moto G2 (XT1078 Thea 4G), desbloqueei o bootloader, fiz o processo de root e verifiquei com o root checker. Estando OK, segui o passo a passo e consegui instalar a Viper. Estou super satisfeito mas, após ter a curiosidade de verificar o root checker com ela instalada, verifiquei que não tenho mais acesso root. Isso é normal? Como procedo?
Click to expand...
Click to collapse
Hello, English only on xda... :good:
Good evening. I installed my ViperOS after all the procedures suggested in the forums. I have a Moto G2 (XT1078 Thea 4G), unlocked the bootloader, did the root process and checked with the root checker. Being OK, I followed the step by step and managed to install the Viper. I am very satisfied but after having the curiosity to verify the root checker with it installed, I verified that I do not have root access anymore. This is normal? How do I proceed?
Click to expand...
Click to collapse

mcbfelipe said:
Good evening. I installed my ViperOS after all the procedures suggested in the forums. I have a Moto G2 (XT1078 Thea 4G), unlocked the bootloader, did the root process and checked with the root checker. Being OK, I followed the step by step and managed to install the Viper. I am very satisfied but after having the curiosity to verify the root checker with it installed, I verified that I do not have root access anymore. This is normal? How do I proceed?
Click to expand...
Click to collapse
If the root checker is saying that your phone is rooted then where you are getting the error?

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

Twrp Vasishath vs Twrp Nebrassy

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.

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

Question ¿Some Root? Samsung A127M U7

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.