Question Root on Moto G100? - Motorola Moto G100 / Edge S

Hello forum members, I recently purchased my MOTO G100 and I've already broken its warranty UNLOCKING BOOTLOADER XD, I would like to know how to install MAGISK on it, I saw that there is no TWRP for this model yet and I don't even know if there will ever be one day, finally, I would like to know if it is possible to ROOT it, thank you all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com

sd_shadow said:
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, Work!!

Jota96 said:
Thanks, Work!!
View attachment 5366173
Click to expand...
Click to collapse
How did you find the correct boot.img to download?

Slowboytommy said:
How did you find the correct boot.img to download?
Click to expand...
Click to collapse
Use
Device Model #, Codename, and Software Channel

Slowboytommy said:
How did you find the correct boot.img to download?
Click to expand...
Click to collapse
The safest way is as follows I think...
Update your stock ROM to the newest one, and use LMSA.
Just specify your IMEI then LMSA will select and download the ROM for you.
And look for the ROM folder in the LMSA Download folder so that you can find the boot.img.

Hola gente como estan yo bajé e instale el programa de rescate de Motorola en Windows y ya estaba registrado en Motorola y bajé la ROM de ahi android 12. Descomprimi la ROM y encontré el archivo boot.img y con eso desbloquee el bootloader. Desde adb fastboot. Después trate de cargar el twrp le cambié el nombre al twrp a recovery y lo tomo con fastboot boot recovery.img pero no puedo ver las particiones ni el almacenamiento interno. Ese es mí problema. Después inicie el celular moto g100 e instale el magisk y listo. Pero el problema es el twrp.. Saludos a todos y si alguien tiene alguna solucion. Muchas Gracias

lualdi63 said:
Hola gente como estan yo bajé e instale el programa de rescate de Motorola en Windows y ya estaba registrado en Motorola y bajé la ROM de ahi android 12. Descomprimi la ROM y encontré el archivo boot.img y con eso desbloquee el bootloader. Desde adb fastboot. Después trate de cargar el twrp le cambié el nombre al twrp a recovery y lo tomo con fastboot boot recovery.img pero no puedo ver las particiones ni el almacenamiento interno. Ese es mí problema. Después inicie el celular moto g100 e instale el magisk y listo. Pero el problema es el twrp.. Saludos a todos y si alguien tiene alguna solucion. Muchas Gracias
Click to expand...
Click to collapse
Hello people, how are you? I downloaded and installed the Motorola rescue program in Windows and it was already registered in Motorola and I downloaded the ROM from there android 12. I unzipped the ROM and found the file boot.img and with that I unlocked the bootloader. From adb fastboot. Then try to load the twrp I renamed the twrp to recovery and take it with fastboot boot recovery.img but I can't see the partitions and internal storage. That's my problem. Then start the moto g100 cell phone and install the magisk and that's it. But the problem is the twrp... Greetings to all and if someone has a solution. Thank you so much
Sir, this is an English language forum. Please provide a translation next time.
TWRP isn't compatible with A12 for our device, you need to patch the boot.img manually in the magisk app and flash it in fastboot.

Beetle84 said:
Hola gente, como estan? Descargué e instalé el programa de rescate de Motorola en Windows y ya estaba registrado en Motorola y de allí descargué la ROM android 12. Descomprimí la ROM y encontré el archivo boot.img y con eso desbloqueé el bootloader. Desde adb fastboot. Luego intente cargar el twrp. Cambie el nombre del twrp a recovery y tómelo con fastboot boot recovery.img pero no puedo ver las particiones y el almacenamiento interno. Ese es mi problema. Luego encienda el celular moto g100 e instale el magisk y listo. Pero el problema es el twrp... Saludos a todos y si alguien tiene una solucion. muchas gracias
Señor, este es un foro en inglés. Proporcione una traducción la próxima vez.
TWRP no es compatible con A12 para nuestro dispositivo, debe parchear boot.img manualmente en la aplicación magisk y actualizarlo en fastboot.
Click to expand...
Click to collapse
Beetle84 said:
Hello people, how are you? I downloaded and installed the Motorola rescue program in Windows and it was already registered in Motorola and I downloaded the ROM from there android 12. I unzipped the ROM and found the file boot.img and with that I unlocked the bootloader. From adb fastboot. Then try to load the twrp I renamed the twrp to recovery and take it with fastboot boot recovery.img but I can't see the partitions and internal storage. That's my problem. Then start the moto g100 cell phone and install the magisk and that's it. But the problem is the twrp... Greetings to all and if someone has a solution. Thank you so much
Sir, this is an English language forum. Please provide a translation next time.
TWRP isn't compatible with A12 for our device, you need to patch the boot.img manually in the magisk app and flash it in fastboot.
Click to expand...
Click to collapse
well thanks for the information but i did that a while ago twrp in its version 3.5.2 starts from adb fastboot only it doesn't let you mount the partitions. I have already rooted a lot of devices and I know how to do it anyway thanks for the observation but as I said I already did it. I just wanted to see if anyone knew of any other solutions with twrp. Greetings to all members of the forums. and it would be advisable to use a translator from English to Spanish and from Spanish to English and there would be no problem. because here there must be people who are members who speak Spanish and speak English, so it is very simple to use a translator.

lualdi63 said:
well thanks for the information but i did that a while ago twrp in its version 3.5.2 starts from adb fastboot only it doesn't let you mount the partitions. I have already rooted a lot of devices and I know how to do it anyway thanks for the observation but as I said I already did it. I just wanted to see if anyone knew of any other solutions with twrp. Greetings to all members of the forums. and it would be advisable to use a translator from English to Spanish and from Spanish to English and there would be no problem. because here there must be people who are members who speak Spanish and speak English, so it is very simple to use a translator.
Click to expand...
Click to collapse
Yes, twrp doesnt let you mount the partitions or access data on A12... So you need to patch yourself. As for the translator, its up to the user to translate, not the site.

Beetle84 said:
Yes, twrp doesnt let you mount the partitions or access data on A12... So you need to patch yourself. As for the translator, its up to the user to translate, not the site.
Click to expand...
Click to collapse
ok thank you very much

Jota96 said:
Hola miembros del foro , recientemente compre mi MOTO G100 y ya rompí su garantía DESBLOQUEANDO BOOTLOADER XD, me gustaría saber cómo instalar MAGISK en él, vi que todavía no hay TWRP para este modelo y no lo sé aun se si algun dia habra, por ultimo me gustaria saber si es posible ROOTEARLO, gracias a todos.​​
Click to expand...
Click to collapse
Jota96 said:
Hello forum members, I recently purchased my MOTO G100 and I've already broken its warranty UNLOCKING BOOTLOADER XD, I would like to know how to install MAGISK on it, I saw that there is no TWRP for this model yet and I don't even know if there will ever be one day, finally, I would like to know if it is possible to ROOT it, thank you all.​​View attachment 5365181​
Click to expand...
Click to collapse
Thanks a lot

Jota96 said:
Hello forum members, I recently purchased my MOTO G100 and I've already broken its warranty UNLOCKING BOOTLOADER XD, I would like to know how to install MAGISK on it, I saw that there is no TWRP for this model yet and I don't even know if there will ever be one day, finally, I would like to know if it is possible to ROOT it, thank you all.​​View attachment 5365181​
Click to expand...
Click to collapse
Thanks a lot. thank you very much very good job

Sorry to revive an old thread, but installing Magisk on latest stock rom prevents touch from working

Kandroid#6386 said:
Sorry to revive an old thread, but installing Magisk on latest stock rom prevents touch from working
Click to expand...
Click to collapse
Usually that problem is caused from using an old boot.IMG
Try flashing the current available firmware from lsma and use that boot.IMG
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com

sd_shadow said:
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
Click to expand...
Click to collapse
will I need to go through this process every time I update my stock rom device?
I have an edge s with a g100 stock rom

Related

[5.1.1][D2533] C3 - 19.4.A.0.182 - PreRoot + XZDual recovery

Hi members of XDA,
I created a preRoot + dual recovery.
DO NOT FLASH THIS IF YOU DONT KNOW WHAT YOU DO, DONT BLAME ME IF YOUR DEVICE EXPLODE
whath do you need?
A)D2533 model
B) 4.4 or 5.0 firmware with funtional recovery (TWRP).
opcional:
C) conect your device to your pc and install yours drivers
Steps:
1) Put "D2533_19.4.A.0.182 - PreRoot + XZDual recovery", in your internal memory.
2) Reboot in to recovery TWRP (yes only TWRP)
3) Make a BackUp (optional)
4) Wipe caches
5) Flash D2533_19.4.A.0.182 - PreRoot + XZDual recovery ( flash with TWRP)
6)done!
Download: https://www.androidfilehost.com/?fid=24052804347822285
Note:
If you need it for another model, tell me.
If you need another mirror link, tell me
If you put it on another forum/web, put the original thread and rom link, thanks.
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hola chicos
He creado una Rom 5.1.1 Pre-Root + Recovery de la 19.4.A.0.182 para el Xperia C3
NO HAGAS ESTO SI NO SABES QUE ESTAS HACIENDO, NO ES MI RESPONSABILIDAD SI TU TELÉFONO EXPLOTA Y MUERE.
Sigamos
Requisitos:
A) tener el modelo d2533
B) Estar en 4.4 ó 5.0 con recovery funcionando (TWRP recovery)
Opcionalmente pueden conectar su C3 al pc e instalen sus drivers (solo en caso de necesitarlos ...)
Pasos:
1) Colocar el archivo "D2533_19.4.A.0.182 - PreRoot + XZDual recovery" en la memoria interna
2) Entrar en recovery (TWRP, solo usar este recovery)
3) Hacer un backup de su rom actual (opcional pero recomendado)
4) Hacer wipes
5) Flashear la rom prerooteada+recovery (mediante twrp recovery)
6) Si todo sale bien, deberás reiniciar y esperar
Recuerden que el primer inicio tarda mucho más de lo normal (5-10 min)
Descarga la rom en el primer post.
Nota:
Si necesita la rom para otro modelo, dime y te lo creare.
Si no puedes descargar el archivo, dime y lo subiré en otro lado
Si colocas esto en otro foro/web, coloca el link original al tema, gracias.
Special Thanks to:
@[NUT]
@zxz0O0
@Chainfire
Tried flashing on your GF's phone?
AutumQueen92 said:
Tried flashing on your GF's phone?
Click to expand...
Click to collapse
Not yet, sadly she will not leave me your phone because she is on finals tests in the university all the week and need it... So I cant test it.
Need feedback guys, If it dont work I will create only a preRoot 5.1.1 without recovery
Lo probaré pero como ya estoy en 5.1.1 tendré q flashear de nuevo a 5.0? Y a partir de ahí trabajar?
Enviado desde mi D2533 mediante Tapatalk
GugaBarrera said:
Lo probaré pero como ya estoy en 5.1.1 tendré q flashear de nuevo a 5.0? Y a partir de ahí trabajar?
Enviado desde mi D2533 mediante Tapatalk
Click to expand...
Click to collapse
Yes, LP 5.1.1 dont have root/recovery yet, so you need a functional recovery,.
Downgrade to 5.0 or 4.4 with funtional recovery for flash the rom.
Ya que no es posible tener root o recovery (con boot cerrado) en 5.1.1, si, deberías bajarte a una versión donde se pueda tener recoveey funcional, la que quieras, y ahí flashear siguiendo los pasos que coloqué. Estaré atento a tu respuesta.
Ya instalado y corriendo, ningún problema, todo bien, gracias [emoji122] [emoji106]
Cualquier cosa la comento.
Enviado desde mi D2533 mediante Tapatalk
GugaBarrera said:
Ya instalado y corriendo, ningún problema, todo bien, gracias [emoji122] [emoji106]
Cualquier cosa la comento.
Enviado desde mi D2533 mediante Tapatalk
Click to expand...
Click to collapse
Grqcias, comentame si puede montar r/w y usar plenamente recovery
panchuckles said:
Grqcias, comentame si puede montar r/w y usar plenamente recovery
Click to expand...
Click to collapse
Dime como hacerlo...
Enviado desde mi D2533 mediante Tapatalk
GugaBarrera said:
Dime como hacerlo...
Enviado desde mi D2533 mediante Tapatalk
Click to expand...
Click to collapse
por ejemplo con root explorer arriba sale "montar R/W", pinchas y te deberia de salir la app de superSU permitiendo el acceso. También puedes hacerlo tratando de borrar alguna app en System/app.
Comentame si resulta.
para entrar al recovery deberias de tener una app instalada llamada NDR Utils, ahi sale la opcionde reiniciar en recovery.
---
for example with root explorer comes up "mount R / W", click it and you should see the app SuperSU allowing access. You can also do it trying to erase an app in System/app.
to enter the recovery you should have an installed app called NDR Utils, there is an option of restarting in recovery.
panchuckles said:
por ejemplo con root explorer arriba sale "montar R/W", pinchas y te deberia de salir la app de superSU permitiendo el acceso. También puedes hacerlo tratando de borrar alguna app en System/app.
Comentame si resulta.
para entrar al recovery deberias de tener una app instalada llamada NDR Utils, ahi sale la opcionde reiniciar en recovery.
---
for example with root explorer comes up "mount R / W", click it and you should see the app SuperSU allowing access. You can also do it trying to erase an app in System/app.
to enter the recovery you should have an installed app called NDR Utils, there is an option of restarting in recovery.
Click to expand...
Click to collapse
Si se puede, adjuntaria fotos pero como soy nuevo no me deja, de todas formas esta todo funcionando [emoji122] [emoji106]
Enviado desde mi D2533 mediante Tapatalk
GugaBarrera said:
Si se puede, adjuntaria fotos pero como soy nuevo no me deja, de todas formas esta todo funcionando [emoji122] [emoji106]
Enviado desde mi D2533 mediante Tapatalk
Click to expand...
Click to collapse
Gracias
Is the rom deodexed? Is it theoretically possible to get Xposed in it?
El rom está deodexed o odexed? En teoría sería posible instalarle Xposed?
Benja-S said:
Is the rom deodexed? Is it theoretically possible to get Xposed in it?
El rom está deodexed o odexed? En teoría sería posible instalarle Xposed?
Click to expand...
Click to collapse
Unless OP says it is deodexed, then you can't use Xposed.
Benja-S said:
Is the rom deodexed? Is it theoretically possible to get Xposed in it?
El rom está deodexed o odexed? En teoría sería posible instalarle Xposed?
Click to expand...
Click to collapse
It Is odex, I just put superSU and recovery on it, no more.
Edit, Is not possible with odex rom.
Anyway if you try xposed, theorically yes if you deodexed the rom, is posible, in Google I search and I found that the phone has armv7, so you need flash "rovo89's official arm versión SDK22"
Read the discussion of xposed thread and make a BackUp before.
I'll be wainting for your response (if it works or not), maybe in a futuro I will work on a custom rom.
panchuckles said:
It Is odex, I just put superSU and recovery on it, no more.
Anyway if you try xposed, theorically yes, is posible, in Google I search and I found that the phone has armv7, so you need flash "rovo89's official arm versión SDK22"
Read the discussion of xposed thread and make a BackUp before.
I'll be wainting for your response (if it works or not), maybe in a futuro I will work on a custom rom.
Click to expand...
Click to collapse
Maybe I can try this two day, I will update it as soon as possible!
Jesus people, please don't install Xposed on an odex Lollipop rom, you'll bootloop to kingdom come.
AutumQueen92 said:
Jesus people, please don't install Xposed on an odex Lollipop rom, you'll bootloop to kingdom come.
Click to expand...
Click to collapse
Ah, of course, my bad guys.
But you can deodex the rom, is easy, just search "how to deodex a rom"
Anyway, If you have a question of xposed guys, lets try Q&A section
in a few days i will uplod the dual version D2502 5.1.1 with root + recovery, stay tuned
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.
Here some of the messages coming out:
Getting ro.build.product
=============================================
Device model is D2533
Firmware is 19.3.A.0.472
=============================================
Step2 : Sending the recovery files.
=============================================
cannot stat 'dr.prop': No such file or directory
cannot stat 'chargemon.sh': No such file or directory
cannot stat 'mr.sh': No such file or directory
cannot stat 'dualrecovery.sh': No such file or directory
cannot stat 'NDRUtils.apk': No such file or directory
cannot stat 'rickiller.sh': No such file or directory...
Si tienes algún dato adicional, envíalo por favor. También soy de Chile.

Hard Brick Moto Maxx

So i downgrade my moto maxx XT1225 to the kitkat and was happy with it, but my cousin take my phone to take some photos and downloaded and installed the ota to the 5.0.2. now my phone don't turn on. he just make a signal on windows when i conect it on the usb port but nothing more :/ can you guys please help me? Sorry for the bad english, i'm from Brasil.
antoniomalta said:
So i downgrade my moto maxx XT1225 to the kitkat and was happy with it, but my cousin take my phone to take some photos and downloaded and installed the ota to the 5.0.2. now my phone don't turn on. he just make a signal on windows when i conect it on the usb port but nothing more :/ can you guys please help me? Sorry for the bad english, i'm from Brasil.
Click to expand...
Click to collapse
http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
pedro_maciel said:
http://forum.xda-developers.com/droid-turbo/general/turbo-unbrick-t3139811
Click to expand...
Click to collapse
i followed the steps and now i'm able to boot the bootloader, but my bootloader is now the droid turbo boot loader, so i cannot flash the Moto maxx firmware :/ you know anything i can do? thanks for the help.
almost forgot and my device revived with the bootloader locked , i think thats why i cannot flash the firmware :/
antoniomalta said:
i followed the steps and now i'm able to boot the bootloader, but my bootloader is now the droid turbo boot loader, so i cannot flash the Moto maxx firmware :/ you know anything i can do? thanks for the help.
almost forgot and my device revived with the bootloader locked , i think thats why i cannot flash the firmware :/
Click to expand...
Click to collapse
Maybe you need before replace the files of the Droid
I had tried to replace with files moto maxx
Sorry for my bad english...:laugh:
antoniomalta said:
So i downgrade my moto maxx XT1225 to the kitkat and was happy with it, but my cousin take my phone to take some photos and downloaded and installed the ota to the 5.0.2. now my phone don't turn on. he just make a signal on windows when i conect it on the usb port but nothing more :/ can you guys please help me? Sorry for the bad english, i'm from Brasil.
Click to expand...
Click to collapse
https://plus.google.com/+JuniorClemente/posts/29pWDUkEDuJ
Try the guide listed in this post.
You will need to flash stock 5.0.2 for Brazil.
http://forum.xda-developers.com/showpost.php?p=65958268&postcount=94
If you followed the linked guide then you will have the wrong gpt.bin file which is a problem. I assume the guide will work but you need to use the moto maxx version of the files for your specific provider.
Possible solution (NOT tested) (see and post here in XDA a tutorial please):
https://plus.google.com/114737944807074302746/posts/USYBQc9Fqz5
Hi everyone!, i not find any solution about my error "sdl-transfer-image"; my "XT1225" still continue bricked, only mode "Qualcomm 9008". The "qboot blank-flash" method not working, every time I run I have the same "sdl-transfer-image" error, please i need help, any other method for unbrick?, jtag?, factory cable?, someone help me?; if I can corrupt the "boot", would have some possibility that the method "qboot" works for me ?, because, for many was the only solution this method... Excuse me for my bad english...
dantexperia said:
Hi everyone!, i not find any solution about my error "sdl-transfer-image"; my "XT1225" still continue bricked, only mode "Qualcomm 9008". The "qboot blank-flash" method not working, every time I run I have the same "sdl-transfer-image" error, please i need help, any other method for unbrick?, jtag?, factory cable?, someone help me?; if I can corrupt the "boot", would have some possibility that the method "qboot" works for me ?, because, for many was the only solution this method... Excuse me for my bad english...
Click to expand...
Click to collapse
Dante, como estás? Tengo el mismo problema que vos. Le hice el unbrick a mi moto maxx con la version droid, y ahora tengo un fastboot que no me deja hacer nada... ni siquiera volver atras para volver a experimentar.
Al final qué hiciste? Pasaron dos años ya, jaja
---------- Post added at 11:34 PM ---------- Previous post was at 11:28 PM ----------
antoniomalta said:
So i downgrade my moto maxx XT1225 to the kitkat and was happy with it, but my cousin take my phone to take some photos and downloaded and installed the ota to the 5.0.2. now my phone don't turn on. he just make a signal on windows when i conect it on the usb port but nothing more :/ can you guys please help me? Sorry for the bad english, i'm from Brasil.
Click to expand...
Click to collapse
Antonio, did you find any solutions?
Reemplacé la placa
Hola ¿cómo estás?, perdón por la demora al responder, he estado viajando y hacía tiempo no entraba aquí.
Respecto al brick, luego de intentar miles de soluciones sin resultados (ni siquiera pude lograr que encendiera en fastboot, nunca pude salir del modo Qualcomm) conseguí por mercadolibre otro moto maxx el cual tenía todo el módulo destrozado pero la placa funcionaba, por lo tanto con $2000 ni dude en comprarlo.
Reemplacé la placa y me quedó prácticamente otro Moto Maxx (con la placa brickeada y módulo roto) completo guardado.
La verdad que hace menos de 2 años creí que valía la pena seguir insistiendo con este dispositivo, dado sus caracteristicas; pero hoy día, viendo como va avanzando todo lo tengo en venta y apenas logre venderlo me voy a Samsung.
Bueno, sin más espero que puedas o hayas podido solucionarlo, abrazo grande.
Making the long history short.. If you are in Qualcomm 9008 in windows.. You have to install proper drivers, flash a blankflash (qboot) and flash gpt, tz, rpm, sbl, etc partitions from the latests blur ota update.

Brick my Huawei Mate 8 NXT-L09 in rollback

Hello friends, (Sorry for my English)
This is the first time I write, but, I'm afraid. I tell you:
I have bootloader and FPR unlocked, my original rom was NXT-L09AC69B105CUSTC69D004, I did flash with NXT-L09C605B131 (C900B120 cust), then I did flash with NXT-L09C605B131, then I did flash with NXT-L09C605B580, I finally did flash with NXT-L09C605B585 , In the end I stayed with nougat.
I did root with twrp-3.1.1-1-next and install superuser_noverify.zip and phh s SuperUser_v1.0.3.3.apk, so far so good, but ..... I wanted to use snapchat and hide root with magisk, then uninstall Phh s SuperUser_v1.0.3.3.apk, I made flash with Magisk-v12.0.zip, this causes bootloop.
Perform ROLLBACK via dload 5.0 to 4.0 (NXT-L09C900B500), all ok, and instead of doing dload NXT-L09AC212B120CUSTC212D002 (Unbrick), I did the nonsense to dload with NXT-L09AC69B105CUSTC69D004 / update.app, this caused me a brick totally.
Now my mate 8 does not turn on (power on), the screen always goes black, any command in adb gives FAILED (remote: command not allowed) error, the computer recognizes the smartphone as Android phone / Android Sooner Single ADB interface. Reviewing in ADB the OEM tells me fastboot oem unlock xxxxx / FAILED (remote: fastboot unlocked). In ADB I can close and open the bootloader without problem, but the other commands do not work.
Please, help me, I can not restore my mate 8, is it that I already have a brick forever?
Many thanks and, again, sorry for my English, I only speak Spanish and I use Google translator.
"In Spanish"
Hola amigos, (Lo siento por mi inglés)
Es la primera vez que escribo, pero, tengo miedo. Les cuento:
Yo tengo bootloader y FPR desbloqueado, mi rom original era NXT-L09AC69B105CUSTC69D004, hice flash con NXT-L09C605B131 (C900B120 cust), despues hice flash con NXT-L09C605B131, luego hice flash con NXT-L09C605B580, al final hice flash con NXT-L09C605B585, al final me quede con nougat.
Hice root con twrp-3.1.1-1-next e instale superuser_noverify.zip y phh s SuperUser_v1.0.3.3.apk, hasta aqui todo bien, pero.....queria usar snapchat y ocultar root con magisk, entonces desinstale phh s SuperUser_v1.0.3.3.apk, hice flash con Magisk-v12.0.zip, esto ocasiono bootloop.
Realice ROLLBACK mediante dload 5.0 a 4.0 (NXT-L09C900B500), todo ok, y en lugar de hacer mediante dload NXT-L09AC212B120CUSTC212D002 (Unbrick), hice la tonteria de hacer dload con update.app de NXT-L09AC69B105CUSTC69D004, esto me ocasiono un brick total.
Ahora mi mate 8 no enciende, la pantalla siempre se queda en negro, cualquier comando en adb da el error FAILED (remote: command not allowed), la computadora si reconoce el smartphone como Android phone / Android Sooner Single ADB interface. Revisando en ADB la OEM me dice fastboot oem unlock xxxxx / FAILED (remote: fastboot unlocked). En ADB puedo cerrar y abrir el bootloader sin problema, pero los demas comandos no funcionan.
Por favor, ayudenme, no puedo restaurar mi mate 8, sera acaso que ya tengo un ladrillo para siempre?
Muchas gracias y, nuevamente, disculpen mi ingles, yo solo hablo español y uso traductor de Google.
enriquebunbury666 said:
Hello friends, (Sorry for my English)
This is the first time I write, but, I'm afraid. I tell you:
I have bootloader and FPR unlocked, my original rom was NXT-L09AC69B105CUSTC69D004, I did flash with NXT-L09C605B131 (C900B120 cust), then I did flash with NXT-L09C605B131, then I did flash with NXT-L09C605B580, I finally did flash with NXT-L09C605B585 , In the end I stayed with nougat.
I did root with twrp-3.1.1-1-next and install superuser_noverify.zip and phh s SuperUser_v1.0.3.3.apk, so far so good, but ..... I wanted to use snapchat and hide root with magisk, then uninstall Phh s SuperUser_v1.0.3.3.apk, I made flash with Magisk-v12.0.zip, this causes bootloop.
Perform ROLLBACK via dload 5.0 to 4.0 (NXT-L09C900B500), all ok, and instead of doing dload NXT-L09AC212B120CUSTC212D002 (Unbrick), I did the nonsense to dload with NXT-L09AC69B105CUSTC69D004 / update.app, this caused me a brick totally.
Now my mate 8 does not turn on (power on), the screen always goes black, any command in adb gives FAILED (remote: command not allowed) error, the computer recognizes the smartphone as Android phone / Android Sooner Single ADB interface. Reviewing in ADB the OEM tells me fastboot oem unlock xxxxx / FAILED (remote: fastboot unlocked). In ADB I can close and open the bootloader without problem, but the other commands do not work.
Please, help me, I can not restore my mate 8, is it that I already have a brick forever?
Many thanks and, again, sorry for my English, I only speak Spanish and I use Google translator.
"In Spanish"
Hola amigos, (Lo siento por mi inglés)
Es la primera vez que escribo, pero, tengo miedo. Les cuento:
Yo tengo bootloader y FPR desbloqueado, mi rom original era NXT-L09AC69B105CUSTC69D004, hice flash con NXT-L09C605B131 (C900B120 cust), despues hice flash con NXT-L09C605B131, luego hice flash con NXT-L09C605B580, al final hice flash con NXT-L09C605B585, al final me quede con nougat.
Hice root con twrp-3.1.1-1-next e instale superuser_noverify.zip y phh s SuperUser_v1.0.3.3.apk, hasta aqui todo bien, pero.....queria usar snapchat y ocultar root con magisk, entonces desinstale phh s SuperUser_v1.0.3.3.apk, hice flash con Magisk-v12.0.zip, esto ocasiono bootloop.
Realice ROLLBACK mediante dload 5.0 a 4.0 (NXT-L09C900B500), todo ok, y en lugar de hacer mediante dload NXT-L09AC212B120CUSTC212D002 (Unbrick), hice la tonteria de hacer dload con update.app de NXT-L09AC69B105CUSTC69D004, esto me ocasiono un brick total.
Ahora mi mate 8 no enciende, la pantalla siempre se queda en negro, cualquier comando en adb da el error FAILED (remote: command not allowed), la computadora si reconoce el smartphone como Android phone / Android Sooner Single ADB interface. Revisando en ADB la OEM me dice fastboot oem unlock xxxxx / FAILED (remote: fastboot unlocked). En ADB puedo cerrar y abrir el bootloader sin problema, pero los demas comandos no funcionan.
Por favor, ayudenme, no puedo restaurar mi mate 8, sera acaso que ya tengo un ladrillo para siempre?
Muchas gracias y, nuevamente, disculpen mi ingles, yo solo hablo español y uso traductor de Google.
Click to expand...
Click to collapse
U can use Dc Phoenix to unbrick your phone if u can enter fastboot.
If Method 1 does not work try Method 2.
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Sent from my LON-L29 using XDA Labs
Mostar088 said:
U can use Dc Phoenix to unbrick your phone if u can enter fastboot.
If Method 1 does not work try Method 2.
Sent from my LON-L29 using XDA Labs
Click to expand...
Click to collapse
Thanks for your answer, just a few questions:
It is a requisite 15 credits, right?
No matter that the screen is not seen, ¡¡¡my screen always black!!!:crying::crying::crying:, the process will restore my smarthphone?
In this case. Which rom is right? I downloaded:
NXT-L09AC69B105CUSTC69D004 (Official Telcel) - (72703 and 72708)
NXT-L09AC212B120CUSTC212D002 (76065)
NXT-L09C605B131 (65032)
NXT-L09C605B580 (75932)
It is best to flash with the original (NXT-L09AC69B105CUSTC69D004 (Official Telcel)) to leave it as factory, right?
enriquebunbury666 said:
Thanks for your answer, just a few questions:
It is a requisite 15 credits, right?
No matter that the screen is not seen, ¡¡¡my screen always black!!!:crying::crying::crying:, the process will restore my smarthphone?
In this case. Which rom is right? I downloaded:
NXT-L09AC69B105CUSTC69D004 (Official Telcel) - (72703 and 72708)
NXT-L09AC212B120CUSTC212D002 (76065)
NXT-L09C605B131 (65032)
NXT-L09C605B580 (75932)
It is best to flash with the original (NXT-L09AC69B105CUSTC69D004 (Official Telcel)) to leave it as factory, right?
Click to expand...
Click to collapse
First i need to know can u enter fastboot mode on the phone?
Yes it cost 15 credit and u can use it for 72 hour, u should try with your Original firmware AC69 if it fail test C605.
Sent from my LON-L29 using XDA Labs
Mostar088 said:
First i need to know can u enter fastboot mode on the phone?
Yes it cost 15 credit and u can use it for 72 hour, u should try with your Original firmware AC69 if it fail test C605.
Sent from my LON-L29 using XDA Labs
Click to expand...
Click to collapse
I can not see anything on the phone. When I connect the phone, the PC shows Android phone / Android Sooner Single ADB interface and another PC shows TP-LINK Android Phone / Android Bootloader Interface. I can not upload images, but that shows.
If I can, I will install the C605 update.app.
Hola tengo el mismo modelo la cosa que haciendo no se que el teléfono me quedó vacío en blanco sistema operativo y no logro instalar nada que puedo hacer logro entrar en fastboot logro cargar un twrp pero al instalar son todos errores

s8+ sm-g955f" only official released binary are allowed to be flashed"

hola a todos tengo un problema con mi s8+ sm-g955f, le instale twrp y root con magisk pero al reiniciar me apareció este mensaje " only official released binary are allowed to be flashed" mi celular no enciende que a quedado inservible. necesito ayuda por favor.:llorando:
Auto Translate :-
hi to everyone I have a problem with my s8+ sm-g955f
I installed twrp and root with magisk but when I rebooted this message appeared "only official released binary are allowed to be flashed"
my cell phone does not turn and its bricked. I need help please
Hi,
Kindly go through our forum rules before posting/creating new threads in future.
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
Thread moved to Q&A section of that device.
Thanks
Try downloading the official version from here https://forum.xda-developers.com/galaxy-s8+/development/rom-galaxy-s8-t3749444 and then flash it using odin.
Descargate la versión oficial desde el link que puse más arriba y luego instala mediante odin (en el mismo link esta el tutorial para hacerlo).
david050613 said:
hola a todos tengo un problema con mi s8+ sm-g955f, le instale twrp y root con magisk pero al reiniciar me apareció este mensaje " only official released binary are allowed to be flashed" mi celular no enciende que a quedado inservible. necesito ayuda por favor.:llorando:
Auto Translate :-
hi to everyone I have a problem with my s8+ sm-g955f
I installed twrp and root with magisk but when I rebooted this message appeared "only official released binary are allowed to be flashed"
my cell phone does not turn and its bricked. I need help please
Click to expand...
Click to collapse
paolol788 said:
Try downloading the official version from here https://forum.xda-developers.com/galaxy-s8+/development/rom-galaxy-s8-t3749444 and then flash it using odin.
Descargate la versión oficial desde el link que puse más arriba y luego instala mediante odin (en el mismo link esta el tutorial para hacerlo).
Click to expand...
Click to collapse
hello good afternoon, I want to know a method to get root in my sm-g955f because when flashing the updated stock room to the latest version of android I do not see the OEM option.
hola buenas tardes, quiero saber un metodo para poder obtener root en mi sm-g955f ya que al flashear la room stock actualizada al la ultima version de android no me aparece la opcion de OEM.

[HOWTO] [ROOT] A307GN Patched Boot.img [Android9]

Important :
This will void warranty.
* I am not responsible for bricked devices, dead SD cards,or lost your Ferrari
* thermonuclear war, or you getting fired because the alarm app failed.
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
* as of now you will lose Samsung Pay and Samsung Pass forever if you root once, even unrooting won't help.
* (hope in future we can get it working on tripped knox device)
* OTA likely won't work once you root device.
Click to expand...
Click to collapse
How to root your A307gn?
1 - Enable developer option
(by head on Setting/About phone/Software information and hit build number 7 times)
2 - Go back and look at Developper option
3 - Enable usb debugging
3 - Enable OEM Unlock
4 - Boot into download mode and follow intruction to unlock bootloader
5 - Flash the ROOT_boot.img with odin via AP tab button
6- Boot into system and install magisk manager
Please report because im stuck on MDM lock and cant find developper option
Is it good for the SM-A307G?
RAFRIKY said:
Is it good for the SM-A307G?
Click to expand...
Click to collapse
Alguien lo a comprobado?
Has anyone checked it?
Gustavo Lopez said:
Alguien lo a comprobado?
Has anyone checked it?
Click to expand...
Click to collapse
al parecer no
Does it work on a307fn
abuamr said:
Does it work on a307fn
Click to expand...
Click to collapse
Since they are 2 different firmwares I wouldn't expect it to work.
You can download the boot image for your firmware and patch it with the Magisk app, then flash it.
---------- Post added at 01:58 PM ---------- Previous post was at 01:55 PM ----------
RAFRIKY said:
Is it good for the SM-A307G?
Click to expand...
Click to collapse
I believe the firmware is different, so it wouldn't work.
You can download the boot image of your firmware then patch it with Magisk and flash it.
It did not work on my a307fn, had to re-flash stock firmware.
mine is the A307GT, should the magisk patching method work? i mean, is this how we get to root samsung phones?
Jerry8538 said:
Since they are 2 different firmwares I wouldn't expect it to work.
You can download the boot image for your firmware and patch it with the Magisk app, then flash it.
Click to expand...
Click to collapse
Where can I find its boot img
Gustavo Lopez said:
Alguien lo a comprobado?
Has anyone checked it?
Click to expand...
Click to collapse
hola , yo lo comprobe y el root funciona perfecto en mi sm-a307g PERO hay un problema , una vez rooteado mi celular no detecta mi tarjeta SIM, repeti el proceso de root varias veces y siempre el mismo resultado , no entiendo a donde puede estar la causa de este problema ,
Aleale384 said:
hola , yo lo comprobe y el root funciona perfecto en mi sm-a307g PERO hay un problema , una vez rooteado mi celular no detecta mi tarjeta SIM, repeti el proceso de root varias veces y siempre el mismo resultado , no entiendo a donde puede estar la causa de este problema ,
Click to expand...
Click to collapse
El problema puede ser que no tienes IMEI, debes repararlo, para verificar si tienes IMEI marca *#06# :laugh:
Un detalle más, al rootear se ve que si rootea pero por ejemplo con lin2sd no deja eliminar aplicaciones del sistema, esto es problema de la versión de magisk la versión que si deja desinstalar app es 19.3 pero después de instalar y reiniciar no debes actualizar los componentes que pide o quedará en bootloop
Gustavo Lopez said:
El problema puede ser que no tienes IMEI, debes repararlo, para verificar si tienes IMEI marca *#06# :laugh:
Un detalle más, al rootear se ve que si rootea pero por ejemplo con lin2sd no deja eliminar aplicaciones del sistema, esto es problema de la versión de magisk la versión que si deja desinstalar app es 19.3 pero después de instalar y reiniciar no debes actualizar los componentes que pide o quedará en bootloop
Click to expand...
Click to collapse
hola, el IMEI esta perfecto , wifi tambien , solo que no detecta la SIM y en ocaciones se paso a modo avion AUTOMATICAMENTE, no entiendo por que ,.
con respecto al root , no tuve problemas , elimine varias app con LUCKY PATCHER , instale el modulo de VIPER4ANDROID sin problemas .
alguien sabe donde conseguir el chimera tool crack para poder repara imei , gracias ???
not working with samsung a307f android 9
please post root file for this model
You can always ROOT by patching the AP partition, as @Jerry8538 pointed earlier. If you see it as Un-successfull, after the procedure, try the following. Power Off the phone. Keep pressing VolUP+Power, and when appears the first screen, unpress both buttons. In this case phone shouldstart with ROOT Enabled. If you do a normal resart from mobile's menu, it will boot without ROOT. you need to restart it from inside the Magisk (from module). The problem i have (with both 20.3 & 20.4) is that also with these versions, mobile is losing SIM Cards (and quite possibly worsens much the GPS), i Have circles in the place of signal strength, os i need to reboot it normal to restart "un-Root", actually i'd call it a "Root-On-Demand"
Apologise..
Now i noticed that in Spanish Above is reported already the problem with the SIM
abuamr said:
Does it work on a307fn
Click to expand...
Click to collapse
Jerry8538 said:
Since they are 2 different firmwares I wouldn't expect it to work.
You can download the boot image for your firmware and patch it with the Magisk app, then flash it.
---------- Post added at 01:58 PM ---------- Previous post was at 01:55 PM ----------
I believe the firmware is different, so it wouldn't work.
You can download the boot image of your firmware then patch it with Magisk and flash it.
Click to expand...
Click to collapse
Terrandroid said:
It did not work on my a307fn, had to re-flash stock firmware.
Click to expand...
Click to collapse
technocaretricks said:
not working with samsung a307f android 9
please post root file for this model
Click to expand...
Click to collapse
@Jerry8538 , @papatsonis , @technocaretricks
is there anyone who has successfully rooted the SM-A307FN?
papatsonis said:
You can always ROOT by patching the AP partition, as @Jerry8538 pointed earlier. If you see it as Un-successfull, after the procedure, try the following. Power Off the phone. Keep pressing VolUP+Power, and when appears the first screen, unpress both buttons. In this case phone shouldstart with ROOT Enabled. If you do a normal resart from mobile's menu, it will boot without ROOT. you need to restart it from inside the Magisk (from module). The problem i have (with both 20.3 & 20.4) is that also with these versions, mobile is losing SIM Cards (and quite possibly worsens much the GPS), i Have circles in the place of signal strength, os i need to reboot it normal to restart "un-Root", actually i'd call it a "Root-On-Demand"
Apologise..
Now i noticed that in Spanish Above is reported already the problem with the SIM
Click to expand...
Click to collapse
ok, I want to try this procedure, but I have a problem: I have always extracted the boot.img file from the original firmware (one file) downloaded from the https://www.sammobile.com site, after unzipping the firmware I had a folder with the boot .ini.
Now that it is no longer possible to download from the official website, I use SamFirm, which, however, downloads 5 different files, decompressing them all, from the "AP" archive it comes out: boot.img.lz4.
Can I start the procedure with Magisk on the boot.img.lz4 file?
will this work for the SM-A307G ?
Will this method work for android 10 ?
nelikp said:
How to root your A307gn?
1 - Enable developer option
(by head on Setting/About phone/Software information and hit build number 7 times)
2 - Go back and look at Developper option
3 - Enable usb debugging
3 - Enable OEM Unlock
4 - Boot into download mode and follow intruction to unlock bootloader
5 - Flash the ROOT_boot.img with odin via AP tab button
6- Boot into system and install magisk manager
Please report because im stuck on MDM lock and cant find developper option
Click to expand...
Click to collapse
Hi bro. Im new member here.
I have rooted phone with this method on android 10 a307gdxU4BTD1. I hope one of you will arrange new thread for rooting a30s with android 10. If you want boot.img patched, here the file:
https://www.dropbox.com/s/9auy9qcwiw70z1c/magisk_patched.tar?dl=0
Tanks you dev... :fingers-crossed:
---------- Post added at 05:26 PM ---------- Previous post was at 05:23 PM ----------
Xmaster111 said:
ok, I want to try this procedure, but I have a problem: I have always extracted the boot.img file from the original firmware (one file) downloaded from the https://www.sammobile.com site, after unzipping the firmware I had a folder with the boot .ini.
Now that it is no longer possible to download from the official website, I use SamFirm, which, however, downloads 5 different files, decompressing them all, from the "AP" archive it comes out: boot.img.lz4.
Can I start the procedure with Magisk on the boot.img.lz4 file?
Click to expand...
Click to collapse
You can extract em with 7zip bro
---------- Post added at 05:26 PM ---------- Previous post was at 05:26 PM ----------
Xmaster111 said:
ok, I want to try this procedure, but I have a problem: I have always extracted the boot.img file from the original firmware (one file) downloaded from the https://www.sammobile.com site, after unzipping the firmware I had a folder with the boot .ini.
Now that it is no longer possible to download from the official website, I use SamFirm, which, however, downloads 5 different files, decompressing them all, from the "AP" archive it comes out: boot.img.lz4.
Can I start the procedure with Magisk on the boot.img.lz4 file?
Click to expand...
Click to collapse
You can extract em with 7zip bro
---------- Post added at 05:29 PM ---------- Previous post was at 05:26 PM ----------
Gustavo Lopez said:
El problema puede ser que no tienes IMEI, debes repararlo, para verificar si tienes IMEI marca *#06# :laugh:
Un detalle más, al rootear se ve que si rootea pero por ejemplo con lin2sd no deja eliminar aplicaciones del sistema, esto es problema de la versión de magisk la versión que si deja desinstalar app es 19.3 pero después de instalar y reiniciar no debes actualizar los componentes que pide o quedará en bootloop
Click to expand...
Click to collapse
I dont understand, but if you want efs backup, nvram, radio image or stock recovery of a30s i can give you bro.

Categories

Resources