Related
Hi,
today I received my Mi A2. I unlocked developer options and enabled OEM unlock.
Then I rebooted to fastboot via power + vol down and executed
fastboot flashing unlock_critical
as fastboot oem unlock didn't work (command unknown).
I got the bootloader unlock screen and commited by "unlock bootloader" + power button.
Until then the phone booted up. However I wasn't able to boot TWRP-3.2.3-jasmine-20180804.img or a magisk patched_boot.img, both attempts just hung without progress.
Now I'm stuck at the android one logo and nothing happens or at fastboot logo with no device detected.
I suspect it's bad RAM.
anyone else?
{
"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"
}
meltbanana said:
Hi,
today I received my Mi A2. I unlocked developer options and enabled OEM unlock.
Then I rebooted to fastboot via power + vol down and executed
fastboot flashing unlock_critical
as fastboot oem unlock didn't work (command unknown).
I got the bootloader unlock screen and commited by "unlock bootloader" + power button.
Until then the phone booted up. However I wasn't able to boot TWRP-3.2.3-jasmine-20180804.img or a magisk patched_boot.img, both attempts just hung without progress.
Now I'm stuck at the android one logo and nothing happens or at fastboot logo with no device detected.
I suspect it's bad RAM.
anyone else?
Click to expand...
Click to collapse
try with this
http://en.miui.com/download-353.html
https://rmtxpg.db.files.1drv.com/y4...ubZwX8fw6A?width=463&height=739&cropmode=none
tzadkiel2 said:
try with this
http://en.miui.com/download-353.html
https://rmtxpg.db.files.1drv.com/y4...ubZwX8fw6A?width=463&height=739&cropmode=none
Click to expand...
Click to collapse
fastboot doesn't work, it's stuck at "waiting for device" and fastboot devices shows a blank space, though I see the mi bot logo.
I'll return it.
for me every single attempt to flash a file failed though it showed the unlocked logo for the few times it booted.
it even showed random behaviour (fastboot returned unknown command, etc.), took several times for fastboot reboot or did nothing, it's defective.
meltbanana said:
fastboot doesn't work, it's stuck at "waiting for device" and fastboot devices shows a blank space, I'll return it.
for me every attempt to flash a file failed though it showed the unlocked logo for the few times it booted.
Click to expand...
Click to collapse
Change port USB, remove driver's and begin cero.
Si entiendes algo de expañol, elimina los drivers del pc y comienza como si estuvieras comenzando desde cero, cambia de puerto USB y conecta con el teléfono en fastboot se debería de instalar el driver.
Prueba también a Agregar hardware heredado, y ya sea por puertos COM o por otros lados Android Bootloader Interface.
Como yo lo desbloqueé fue con fastboot oem unlock.
Le he dejado en peores condiciones en varias ocasiones no he visto manera de pasar al Sistema después de instalar TWRP, así que me ha tocado recuperarlo en bastantes ocasiones.
tzadkiel2 said:
Change port USB, remove driver's and begin cero.
Si entiendes algo de expañol, elimina los drivers del pc y comienza como si estuvieras comenzando desde cero, cambia de puerto USB y conecta con el teléfono en fastboot se debería de instalar el driver.
Prueba también a Agregar hardware heredado, y ya sea por puertos COM o por otros lados Android Bootloader Interface.
Como yo lo desbloqueé fue con fastboot oem unlock.
Le he dejado en peores condiciones en varias ocasiones no he visto manera de pasar al Sistema después de instalar TWRP, así que me ha tocado recuperarlo en bastantes ocasiones.
Click to expand...
Click to collapse
cannot even reach it under ubuntu via fastboot
it's impossible that I broke it cause I wasn't able to flash a kernel (boot.img) or something else
and I wasn't able to switch a slot: "this device doesn't support slots". when I entered fastboot set_active a it returned
this device only support slots
a
b
it acted as if it was infected with an ART rootkit or had bad memory.
meltbanana said:
cannot even reach it under ubuntu via fastboot
it's impossible that I broke it cause I wasn't able to flash a kernel (boot.img) or something else
and I wasn't able to switch a slot: "this device doesn't support slots". when I entered fastboot set_active a it returned
this device only support slots
a
b
it acted as if it was infected with an ART rootkit or had bad memory.
Click to expand...
Click to collapse
In my case I was trying to flash MIUI 10 the third time then it fails I was using Android One rom September update and it was working flawlessly without any problem.
After miflash tool fails to flash my phone wont be detected either of my PC and Mac
I am thinking using deep flash cable to enter EDL but is it possible for MI A2 hopefully it is because I don't want my phone to be opened, ITS NEW :crying:
Am I still covered by warranty? If not I have to send my phone to repair shop to just enter EDL mode and to be able to flash stock or miui again
About me flashing MIUI I did follow instructions to avoid Anti Rollback (Never flashed MIUI 10 via twrp instead I flash custom roms)
johnsci911 said:
In my case I was trying to flash MIUI 10 the third time then it fails I was using Android One rom September update and it was working flawlessly without any problem.
After miflash tool fails to flash my phone wont be detected either of my PC and Mac
I am thinking using deep flash cable to enter EDL but is it possible for MI A2 hopefully it is because I don't want my phone to be opened, ITS NEW :crying:
Am I still covered by warranty? If not I have to send my phone to repair shop to just enter EDL mode and to be able to flash stock or miui again
About me flashing MIUI I did follow instructions to avoid Anti Rollback (Never flashed MIUI 10 via twrp instead I flash custom roms)
Click to expand...
Click to collapse
Same thing happened with me no fastboot no edl .
Then I flashed my phone using test points method.
And yes you need to open your phone for that.
ARNOB XENON said:
Same thing happened with me no fastboot no edl .
Then I flashed my phone using test points method.
And yes you need to open your phone for that.
Click to expand...
Click to collapse
Then I guess I need to open mine too
Is it guaranteed that the phone will work again?
Have you tried it yourself?
johnsci911 said:
Then I guess I need to open mine too
Is it guaranteed that the phone will work again?
Have you tried it yourself?
Click to expand...
Click to collapse
Yes It will work 100%....Best of luck ..Open it very carefully..Must watch some videos in YouTube how to open Mi A2.
Does it work with deep-cable? Or another option before open it? I prefer return to Amazon than open...
Fix it?
meltbanana said:
Hi,
today I received my Mi A2. I unlocked developer options and enabled OEM unlock.
Then I rebooted to fastboot via power + vol down and executed
fastboot flashing unlock_critical
as fastboot oem unlock didn't work (command unknown).
I got the bootloader unlock screen and commited by "unlock bootloader" + power button.
Until then the phone booted up. However I wasn't able to boot TWRP-3.2.3-jasmine-20180804.img or a magisk patched_boot.img, both attempts just hung without progress.
Now I'm stuck at the android one logo and nothing happens or at fastboot logo with no device detected.
I suspect it's bad RAM.
anyone else?
Click to expand...
Click to collapse
Did you fix ir?
I hace the same issue but Idk how to fix it, Any help?:c
---------- Post added at 03:16 PM ---------- Previous post was at 03:13 PM ----------
tzadkiel2 said:
Change port USB, remove driver's and begin cero.
Si entiendes algo de expañol, elimina los drivers del pc y comienza como si estuvieras comenzando desde cero, cambia de puerto USB y conecta con el teléfono en fastboot se debería de instalar el driver.
Prueba también a Agregar hardware heredado, y ya sea por puertos COM o por otros lados Android Bootloader Interface.
Como yo lo desbloqueé fue con fastboot oem unlock.
Le he dejado en peores condiciones en varias ocasiones no he visto manera de pasar al Sistema después de instalar TWRP, así que me ha tocado recuperarlo en bastantes ocasiones.
Click to expand...
Click to collapse
Yo intenté todo eso, el problema es que ningún PC reconoce el Xiaomi mi A2 aún cuando está en modo fastboot, lo único que sale es esperando dispositivo, no más no lo reconoce.
Did anyone solved this problem?
I've bricked my device and I can get on fastboot mode but the PC won't recognize the device.
I've tried several computers and systems, windows, ubuntu, debian...
Did the deep flash USB cable work?
Hello
Can I downgrade my P10 VTR-L09 from 9.1.0.262
to EMUI 5, via firmware finder?
Is it safe?
kenzyyy said:
Hello
Can I downgrade my P10 VTR-L09 from 9.1.0.262
to EMUI 5, via firmware finder?
Is it safe?
Click to expand...
Click to collapse
No, you cannot
Bootloader has changed since EMUI 8, Security Patch 06/2018, trying to roll-back to the old Bootloader from a firmware with the new Bootloader causes a serious brick
(although, dload will probably just fail with no result and no harm - depending on which package you take, you need a stronger/root method to enforce 'rollback' and therfore to brick)
Anyway, do not even try - there were numerous people who tried with various Huawei phones and ended up with fully bricked devices (they could be repaired only by Testpoints methods, and only by Testpoints method you can rollback over the Bootloader change divide)
zgfg said:
No, you cannot
Bootloader has changed since EMUI 8, Security Patch 06/2018, trying to roll-back to the old Bootloader from a firmware with the new Bootloader causes a serious brick
(although, dload will probably just fail with no result and no harm - depending on which package you take, you need a stronger/root method to enforce 'rollback' and therfore to brick)
Anyway, do not even try - there were numerous people who tried with various Huawei phones and ended up with fully bricked devices (they could be repaired only by Testpoints methods, and only by Testpoints method you can rollback over the Bootloader change divide)
Click to expand...
Click to collapse
Thanks buddy for that information!
Sine I can't go back to Nougat is it possible to roll back to EMUI 8.0? Via firmware flasher or something?
I tried with hisuite but it says I have the latest OS and there is no roll back option.
kenzyyy said:
Thanks buddy for that information!
Sine I can't go back to Nougat is it possible to roll back to EMUI 8.0? Via firmware flasher or something?
I tried with hisuite but it says I have the latest OS and there is no roll back option.
Click to expand...
Click to collapse
In HiSuite, there must be option for Other firmware or so, to go backwards.
Maybe it depends on info from oeminfo and shown only for users who regularly updated byOTA.
Just tried my HiSuite, to roll-back:
click to Update,
switch to Other version / Earlier versions,
and accept Restore
Beware:
>> Bootloader has changed since EMUI 8, Security Patch 06/2018, trying to roll-back to the old Bootloader from a firmware with the new Bootloader causes a serious brick
Which means, you cannot rollback to the old Bootloader (even with Oreo), to be able to seek for BL code the old and cheap way through DC Unlocker (if that was your agenda for rolling back)
zgfg said:
In HiSuite, there must be option for Other firmware or so, to go backwards.
Maybe it depends on info from oeminfo and shown only for users who regularly updated byOTA
Beware:
>> Bootloader has changed since EMUI 8, Security Patch 06/2018, trying to roll-back to the old Bootloader from a firmware with the new Bootloader causes a serious brick
Which means, you cannot rollback to the old Bootloader (even with Oreo), to be able to seek for BL code the old and cheap way through DC Unlocker (if that was your agenda for rolling back)
Click to expand...
Click to collapse
On latest version I don't have rollback option, but I used to have it on previous builds.. I will try to download previous build and try to rollback.
So it's safe to downgrade from 9.1 to 9.0 and to latest 8.0? EMUI ofc
Bricked it.. Black screen no signs of life I can only hear windows connection sounds USB
Please help. Was trying to downgrade from 9.0 to 8.0
kenzyyy said:
On latest version I don't have rollback option, but I used to have it on previous builds.. I will try to download previous build and try to rollback.
So it's safe to downgrade from 9.1 to 9.0 and to latest 8.0? EMUI ofc
Click to expand...
Click to collapse
Again, make sure you don't go back to Sec Patch Jun 2018 or earlier.
Install Firmware Finder on the phone or PC (or go by browser to pro-teammt.ru) find the given version (model, cust and version must match), open ChangeLog and read which Sec Patch it includes (you must double-check yourself, it depends on your model/cust and which build number will HiSuite offer to you for going back)
And before you go, make sure you have stock Recovery (not eg TWRP), also unroot if it was rooted. No hack modifications that included flashing
zgfg said:
Again, make sure you don't go back to Sec Patch Jun 2018 or earlier.
Install Firmware Finder on the phone or PC (or go by browser to pro-teammt.ru) find the given version (model, cust and version must match), open ChangeLog and read which Sec Patch it includes (you must double-check yourself, it depends on your model/cust and which build number will HiSuite offer to you for going back)
And before you go, make sure you have stock Recovery (not eg TWRP), also unroot if it was rooted. No hack modifications that included flashing
Click to expand...
Click to collapse
Its bricked now. I tried to downgrade from 9.0.1.190 to EMUI 8 latest version. Now phone has black screen, I cant seem to turn it on I tried all key combinations still no luck. But my PC recognizes my phone as HI386 something. In Multi-Tool says phone is still on 9.0.1.190 and it hasnt reverted back to EMUI 8. So I think there is a chance probably, I dont have unlocked bootloader nor enabled OEM unlock.
Please I need help getting it back to life. fastboot commands work fine eg. reboot etc..
kenzyyy said:
Its bricked now. I tried to downgrade from 9.0.1.190 to EMUI 8 latest version. Now phone has black screen, I cant seem to turn it on I tried all key combinations still no luck. But my PC recognizes my phone as HI386 something. In Multi-Tool says phone is still on 9.0.1.190 and it hasnt reverted back to EMUI 8. So I think there is a chance probably, I dont have unlocked bootloader nor enabled OEM unlock.
Please I need help getting it back to life. fastboot commands work fine eg. reboot etc..
Click to expand...
Click to collapse
You don't have BL code - or just Bootloader and OEM/FRP were not unlocked?
Have you tried to boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+, boot),
does it offer to (re)install latest firmware and recovery
With the locked BL and/or FRP, you could only try to fix with DLOAD and a proper firmware for your phone and DLOAD,
try the following queries from Fastboot (switch off, connect to PC, press and keep pressing Vol-, boot):
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Edit: You can check the following post and ask the poster who also had a brick with P10 and EMUI 9, and how he repaired: https://forum.xda-developers.com/p1...enkirin-aosp-collection-t3828797/post80996581
{
"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"
}
zgfg said:
You don't have BL code - or just Bootloader and OEM/FRP were not unlocked?
Have you tried to boot to eRecovery (switch off, connect to charger, press and keep pressing Vol+, boot),
does it offer to (re)install latest firmware and recovery
With the locked BL and/or FRP, you could only try to fix with DLOAD and a proper firmware for your phone and DLOAD,
try the following queries from Fastboot (switch off, connect to PC, press and keep pressing Vol-, boot):
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Edit: You can check the following post and ask the poster who also had a brick with P10 and EMUI 9, and how he repaired: https://forum.xda-developers.com/p1...enkirin-aosp-collection-t3828797/post80996581
Click to expand...
Click to collapse
Thanks for the reply!
So I have to get exact same build number and system version? In Multi Tool it says its on EMUI 9.0.1, phones is recognized in fastboot. But my phone wont go to eRecovery none of the key combinations work its a hard brick
https://prnt.sc/q2r3cn
kenzyyy said:
Thanks for the reply!
So I have to get exact same build number and system version? In Multi Tool it says its on EMUI 9.0.1, phones is recognized in fastboot. But my phone wont go to eRecovery none of the key combinations work its a hard brick
Here is the screenshot of powershell via fastboot https://prnt.sc/q2r3cn
Click to expand...
Click to collapse
kenzyyy said:
https://prnt.sc/q2r3cn
Click to expand...
Click to collapse
Per Fastboot, Bootloader is locked - I guess, you never had BL unlocked?
It shows two versions for VTR-L09 C432, first 9.0.1.190, then 9.0.1.185 - do you remember, did you have 9.0.1.190 and were you downgrading by HiSuite to 9.0.1.185?
Or, were you downgrading by HiSuite from 9.1.0.262 to 9.0.1.190
Try from androidhost.ru, they don't have 190 for c432, but they have 185:
https://androidhost.ru/2AQn
As for their other firmwares (other Huawei phones) that should be the official Huawei Service Repair package
You need to download, unzip, unarj or whatever compression/archiving you find - until you find two folders:
Docs
Software
In Docs folder there must be an installation guide in English, describing (standard, forced) DLOAD procedure
In Software folder, there must be one or more update*.zip files.
You must not unzip those files.
If some of them have c636 or L29 or so in the name, not matching your L09 c432, then exclude such file(s)
Copy these update*.zip files (zipped, with original names) to /DLOAD folder on SD card (not Internal memory) - pull the SD card out, use another phone or card reader to connect to PC and for copying
Read the Installation guide from Software folder to double-check about DLOAD details!
Switch the phone off, put SD card, have it charged at least 50%, press and keep pressing Vol+ and Vol- simultaneously, then boot by Pow
It should start DLOAD installation for 9.0.1.185
If it asks you at the end for Factory Reset (from Recovery), better take it (or take it later)
zgfg said:
Per Fastboot, Bootloader is locked - I guess, you never had BL unlocked?
It shows two versions for VTR-L09 C432, first 9.0.1.190, then 9.0.1.185 - do you remember, did you have 9.0.1.190 and were you downgrading by HiSuite to 9.0.1.185?
Or, were you downgrading by HiSuite from 9.1.0.262 to 9.0.1.190
Try from androidhost.ru, they don't have 190 for c432, but they have 185:
https://androidhost.ru/2AQn
As for their other firmwares (other Huawei phones) that should be the official Huawei Service Repair package
You need to download, unzip, unarj or whatever compression/archiving you find - until you find two folders:
Docs
Software
In Docs folder there must be an installation guide in English, describing (standard, forced) DLOAD procedure
In Software folder, there must be one or more update*.zip files.
You must not unzip those files.
If some of them have c636 or L29 or so in the name, not matching your L09 c432, then exclude such file(s)
Copy these update*.zip files (zipped, with original names) to /DLOAD folder on SD card (not Internal memory) - pull the SD card out, use another phone or card reader to connect to PC and for copying
Read the Installation guide from Software folder to double-check about DLOAD details!
Switch the phone off, put SD card, have it charged at least 50%, press and keep pressing Vol+ and Vol- simultaneously, then boot by Pow
It should start DLOAD installation for 9.0.1.185
If it asks you at the end for Factory Reset (from Recovery), better take it (or take it later)
Click to expand...
Click to collapse
Thanks again for replying.
I downgraded from 9.1.0.262 to 9.0.1.180. it booted fine i used the phone normally. Then I decided to downgrade it to EMUI 8 latest version via firmware finder, since it was complete phone wont boot, respond, nothing. When charging the phone gets pretty warm. So to conclude it its bricked on 9.0.1.190..
Still no luck..
I cannot downgrade from 9 to 8 anymore. This opion is not displayed in HiSuite, did they kill this option? Can someone confirm?
Is there any other option to downgrade from 9.0.1.185 to 8?
Thanks
---------- Post added at 07:25 PM ---------- Previous post was at 07:22 PM ----------
tangmubuddy said:
I cannot downgrade from 9 to 8 anymore. This opion is not displayed in HiSuite, did they kill this option? Can someone confirm?
Is there any other option to downgrade from 9.0.1.185 to 8?
Thanks
Click to expand...
Click to collapse
Update:
Works again after restarting HiSuite, strange
First of, sorry for i don't mean to hijack this thread.
Now here is my question, if for example I was able to unlock my P10 (android ver.7.0) bootloader using DC-unlocker then relock it will I be able to use the unlock code again if my P10 is already in android 9 Pie version?
Thanks!
eyeyousee said:
First of, sorry for i don't mean to hijack this thread.
Now here is my question, if for example I was able to unlock my P10 (android ver.7.0) bootloader using DC-unlocker then relock it will I be able to use the unlock code again if my P10 is already in android 9 Pie version?
Thanks!
Click to expand...
Click to collapse
Bootloader code is bound to the Serial Number of your device, you can reuse it for unlocking/relocking as many times you want, no matter did you upgrade/downgrade, etc
zgfg said:
Bootloader code is bound to the Serial Number of your device, you can reuse it for unlocking/relocking as many times you want, no matter did you upgrade/downgrade, etc
Click to expand...
Click to collapse
Ok thank you for clearing that up.
[QUOTE = "zgfg, publicación: 81031851, miembro: 7786725"]
Por Fastboot, Bootloader está bloqueado, supongo, ¿nunca desbloqueaste BL?
Muestra dos versiones para VTR-L09 C432, primero 9.0.1.190, luego 9.0.1.185 - ¿recuerdas, tenías 9.0.1.190 y estabas bajando por HiSuite a 9.0.1.185?
O, ¿estaba cambiando HiSuite de 9.1.0.262 a 9.0.1.190?
Pruebe desde androidhost.ru, no tienen 190 para c432, pero tienen 185:
https://androidhost.ru/2AQn
En cuanto a sus otros firmwares (otros teléfonos Huawei), ese debería ser el paquete oficial de reparación de servicios de Huawei.
Necesita descargar, descomprimir, unarj o cualquier compresión / archivo que encuentre, hasta que encuentre dos carpetas:
Docs
Software
En la carpeta Docs debe haber una guía de instalación en inglés, que describa el procedimiento de DESCARGA (estándar, forzado)
En la carpeta Software, debe haber uno o más archivos * .zip de actualización.
No debe descomprimir esos archivos.
Si algunos de ellos tienen c636 o L29 más o menos en el nombre, y no coinciden con su L09 c432, excluya dichos archivos.
Copie estos archivos * .zip de actualización (comprimidos, con los nombres originales) a la carpeta / DLOAD en la tarjeta SD (no en la memoria interna); extraiga la tarjeta SD, use otro teléfono o lector de tarjetas para conectarse a la PC y para copiar
¡Lea la guía de instalación de la carpeta Software para verificar los detalles de DESCARGA!
Apague el teléfono, coloque la tarjeta SD, cargue al menos al 50%, presione y mantenga presionado Vol + y Vol- simultáneamente, luego arranque con Pow
Debería iniciar la instalación DLOAD para 9.0.1.185
Si al final te pide el restablecimiento de fábrica (desde la recuperación), mejor tómalo (o tómalo más tarde)
[/CITAR]
I have a similar case, I tried to go down from 9 to 8 but I got an absolute black screen (It does not load, it does not turn on, not erecovery, not fastboot), only when connecting it to the PC, fastboot mode comes out due to the sound of the pc and in fastboot devices it appears but nothing more than there.
I have tried the method you mentioned but without any success, the phone is still dead. My last option is to unlock the bootloader but I don't know if it will be a good idea. I would appreciate your help.
Hi i recently bought the Asus ROG phone 2 Tencent edition, it came with WW rom 1908_12 but CN fingerprint. I followed the tutorial from Bobbyprats to fully convert it to global, unlocked bootloader etc. but after step 2 (the root part) when trying to boot the phone it says ''Slot A is unbootable''. I can still run the ''fastboot devices'' cmd and I can still see the fastboot menu. Now I read some other posts about this and I read that you need to flash the stock img again but since I don't have experience with flashing at all I am pretty clueless. Do I just connect the phone to my computer in fastboot mode and start adb&fastboot and use the ''fastboot flash boot bootstockww190812.img'' command? Thanks for the help.
Asparas said:
Hi i recently bought the Asus ROG phone 2 Tencent edition, it came with WW rom 1908_12 but CN fingerprint. I followed the tutorial from Bobbyprats to fully convert it to global, unlocked bootloader etc. but after step 2 (the root part) when trying to boot the phone it says ''Slot A is unbootable''. I can still run the ''fastboot devices'' cmd and I can still see the fastboot menu. Now I read some other posts about this and I read that you need to flash the stock img again but since I don't have experience with flashing at all I am pretty clueless. Do I just connect the phone to my computer in fastboot mode and start adb&fastboot and use the ''fastboot flash boot bootstockww190812.img'' command? Thanks for the help.
Click to expand...
Click to collapse
fastboot flash boot bootstockww190812.img thts all you need to do in fastboot mode And your phone will boot up .
kashif31 said:
fastboot flash boot bootstockww190812.img thts all you need to do in fastboot mode And your phone will boot up .
Click to expand...
Click to collapse
Thanks for the fast reply! will it boot by itself? ADB says it finished but i still see the fastboot menu on my phone, do i just press start? Also is it normal that it only takes 3 seconds too finish that process?
Asparas said:
Thanks for the fast reply! will it boot by itself? ADB says it finished but i still see the fastboot menu on my phone, do i just press start? Also is it normal that it only takes 3 seconds too finish that process?
Click to expand...
Click to collapse
Hey did you fix your issue? Yes you have to manually press on start on your phone
Slot a unbootable
Any ideas to fix this thank you
Slot -a unbootable
Asparas said:
Hi i recently bought the Asus ROG phone 2 Tencent edition, it came with WW rom 1908_12 but CN fingerprint. I followed the tutorial from Bobbyprats to fully convert it to global, unlocked bootloader etc. but after step 2 (the root part) when trying to boot the phone it says ''Slot A is unbootable''. I can still run the ''fastboot devices'' cmd and I can still see the fastboot menu. Now I read some other posts about this and I read that you need to flash the stock img again but since I don't have experience with flashing at all I am pretty clueless. Do I just connect the phone to my computer in fastboot mode and start adb&fastboot and use the ''fastboot flash boot bootstockww190812.img'' command? Thanks for the help.
Click to expand...
Click to collapse
I follow the same steps and got the same error but now I can fix. If any knows the solution please contact me.
i have same proplem and it sayes to me its locked
Hello Team,
I am also facing same problem. Please help any one
You have to reflash the entire RAW firmware image through fastboot. Then it will boot.
I have the same problem. I tried flashing a new boot image, but it still doesn't work. PLEASE HELP
aliferous said:
I have the same problem. I tried flashing a new boot image, but it still doesn't work. PLEASE HELP
Click to expand...
Click to collapse
Check one post above you.
I am getting a slot a is unbootable error. When I try to flash any raw images i am getting vender.img errors. see attached file.
> ROG2 Bootloader Unlocked.
> Download Stock.img of which firmware version you're on.
> switch the phone to fastboot mode
> launch adb > fastboot devices > alpha numeric should appear
> make sure stock.img is in the same folder as your adb
> fastboot flash boot stock.img
> fastboot restart
if above didn't work.
> download RAW Firmware
> Extract Content to a folder
> Switch phone to Fastboot mode
> double click Flash_all.bat
> Wait for process to finish
> Factory Wipe to boot
If Phone says LOCKED and you can't boot to system
you can unlock through EDL mode
sorry for resuming this "old topic",
after i did the thing in fastboot (my phone reboot and now it "works") is not able anymore to get LTE/4G any suggestion? i only did the fastboot thing
says galerVersion WW-17.0240.2009.49a where I find the boot.img of this rom
please help me to recover my rog 2 is with storage Slot a is unbootable
kashif31 said:
Ei, você consertou seu problema? Sim, você deve pressionar manualmente para iniciar no seu telefone
Click to expand...
Click to collapse
bom dia galera, alguem pode me ajudar a recuperar meu rog2, estou com o mesmo problema, meu ROM é ww17.0240.2009.49
como posso digitar esse comando no adb, obrigado pela força! estamos juntos !
{
"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"
}
How to Fix BOOTLOOP | Asus Zenfone Max M2
Requirements:
Unlocked Bootloader
Twrp installed
Download Stock ROM android 10
Download Vbmeta.img
Download Tool Kit
Download red warning fix.zip
Using toolkit you can fix
Red warning
Fastboot stuck (continuously reboot into fastboot)
Flash twrp 3.4
Lock Bootloader
Unlock Bootloader
If you facing fastboot stuck or continuously rebooting to fastboot mode
so download toolkit and extract it then connect phone to pc in fastboot mode (press volume + and power)
then run (double click) on Click me to fix stuck fastboot problem.cmd [file]
Or flash file manually
Code:
fastboot flash vbmeta vbmeta.img
Fastboot reboot
{ Now your fastboot stuck problem is fix but still phone not booting so follow below steps also you facing bootloop problem follow below steps }
------------------------------------------------------------------------------------------------------------------------
Fix BOOTLOOP using Recovery
Download any custom ROM
Download firmware
Wipe dalvik cache data, system, vendor
Flash Firmware.zip
Flash ROM.zip
Format data
Reboot system
------------------------------------------------------------------------------------------------------------------------
Fix BOOTLOOP using Stock ROM
Download stock ROM
Download magisk
Download dm-verity
Reboot recovery
Wipe dalvik,data,cache, system,vendor
Flash stock rom.zip
Format data (type yes)
Flash magisk
Flash Dm-Verity
Reboot system
Wait 5-10 minutes until phone Boot up :good:
------------------------------------------------------------------------------------------------------------------------
Fix RED WARNING using phone
Method 1
First Download RED warning fix.zip
- Reboot recovery
- Flash red warning-fix.zip
Your phone automatically boots to system
This fix only works when your system are bootable
if you facing bootloop + red warning so you need to fix bootloop then reboot system
----- Then reboot recovery then flash red warning fix.zip
------------------------------------------------------------------------------------------------------------------------
Method 2. using /ROOT
Install any terminal emulator app
Type su and hit enter
Grant root permission
Copy pest below command
reboot "dm-verity enforcing"
Now hit enter
Your device well be automatically reboot wait until it's Boot
-----------------------------------------------------------------------
Method 3
Fix using PC
Install ADB drivers on pc
Enable developers option from settings
enable USB debugging plug the cell phone into the PC,
type in cmd if not works then download minimal adb.exe
Open it
Type adb devices
(if devices have been detected, proceed to the next command just copy pest)
adb reboot "dm-verity enforcing"
The phone will automatically reboot and the red warning disappears
--------------------------------------------------------
Fix Stuck AT ASUS LOGO
Download Fix-Stuck-at-ASUS-LOGO.zip
IF you flash ROM.zip
but phone stuck at Asus logo so just flash fix stuck-at-Asus.zip
using recovery after flashing ROM.zip
OR......
Reboot recovery
Flash Fix_stuck-at-ASUS-logo.zip
Reboot system
If your Problem are solved then Enjoy
IF not then try again once (read thread carefully)
Agar phone lock ho and eio state se OS pe boot na ho raha ho to kya karoge bhai ?
Techgaming432 said:
Agar phone lock ho and eio state se OS pe boot na ho raha ho to kya karoge bhai ?
Click to expand...
Click to collapse
Go fastboot unlock Bootloader
Then follow steps buddy [Bhai]
Thank you my friend! God bless you!
Noesao said:
Thank you my friend! God bless you!
Click to expand...
Click to collapse
Thank you:angel:
Surendra R sonawane said:
Thank you:angel:
Click to expand...
Click to collapse
Can anyone help with red warning "g.co/ABHg.co/ABH"?
I already googling about it but there are only exist solution to red warning "g.co/ABH".
I've tried the solution but no succeed.
BTW I cannot enter the recovery mode.
Every time I've tried to enter recovery mode, it just restarted.
And I have no idea if the phone has unlocked bootloader nor TWRP installed.
Does anyone has the same trouble?
ipta said:
Can anyone help with red warning "g.co/ABHg.co/ABH"?
I already googling about it but there are only exist solution to red warning "g.co/ABH".
I've tried the solution but no succeed.
BTW I cannot enter the recovery mode.
Every time I've tried to enter recovery mode, it just restarted.
And I have no idea if the phone has unlocked bootloader nor TWRP installed.
Does anyone has the same trouble?
Click to expand...
Click to collapse
hello, mine was having the same problem. to solve it I downloaded a rom on this site https://firmwarex.net/asus-zenfone-max-m2-zb633kl-zb632kl-official-firmware/ then when I finished flashing the rom he gave the same error but this time with the system installed , so I went to fastboot and unblocked it. so the device was working again, but I still haven't found a solution to keep it blocked without the error. if i find i will come back here. sorry if there are mistakes in writing, i don't speak english and use a translator to write
Paulo Ricardo zenfone said:
hello, mine was having the same problem. to solve it I downloaded a rom on this site https://firmwarex.net/asus-zenfone-max-m2-zb633kl-zb632kl-official-firmware/ then when I finished flashing the rom he gave the same error but this time with the system installed , so I went to fastboot and unblocked it. so the device was working again, but I still haven't found a solution to keep it blocked without the error. if i find i will come back here. sorry if there are mistakes in writing, i don't speak english and use a translator to write
Click to expand...
Click to collapse
And how did you unblocked it?
I've already tried using those ROM (FirmwareX.Net_WW_ZB633KL_16.2018.1905.44_20190522_Phone-user.raw) but still gave the same error and when i tried to enter to the recovery, it just restart.
ipta said:
Can anyone help with red warning "g.co/ABHg.co/ABH"?
I already googling about it but there are only exist solution to red warning "g.co/ABH".
I've tried the solution but no succeed.
BTW I cannot enter the recovery mode.
Every time I've tried to enter recovery mode, it just restarted.
And I have no idea if the phone has unlocked bootloader nor TWRP installed.
Does anyone has the same trouble?
Click to expand...
Click to collapse
I think you using official twrp they have some problems try unofficial 3.4
[RECOVERY][3.4.0][X01AD]Unofficial TWRP for Asus Zenfone Max M2
Features: - Decryption works So I'm always confused about this encryption/decryption. Decryption works means: in TWRP i can decrypt my phone data if I have enabled encryption? this decryption option only affects me if I want to make backups of...
forum.xda-developers.com
Paulo Ricardo zenfone said:
hola, el mío estaba teniendo el mismo problema. para resolverlo descargué una rom en este sitio https://firmwarex.net/asus-zenfone-max-m2-zb633kl-zb632kl-official-firmware/ luego, cuando terminé de flashear la rom, dio el mismo error pero esta vez con el sistema instalado, así que fui a fastboot y lo desbloqueé. por lo que el dispositivo estaba funcionando de nuevo, pero todavía no he encontrado una solución para mantenerlo bloqueado sin el error. si lo encuentro volveré aquí. perdón si hay errores al escribir, no hablo inglés y uso un traductor para escribir
Click to expand...
Click to collapse
amigo, ¿podría ayudarme sobre cómo poner el firmware original? Es que no puedo encontrar con qué programa actualizar el firmware
help me i'm stuck.
my phone asus zenfone max m2 got restarted by itself and then stuck on bootloop(showing logo then switch off) . i tried something to solve it and things got even worse.
now no asus logo showing red warning ,can't flash any version of twrp(tried many)
sometimes showing this sometimes some error.
C:\adb>fastboot flash recovery twrp.img
Sending 'recovery' (38936 KB) OKAY [ 1.172s]
Writing 'recovery' OKAY [ 0.500s]
Finished. Total time: 1.726s
tried diretly booting in to recovery after flashing twrp but
fastboot boot twrp.img is not temporarily booting twrp on phone.
I don't know what to do now. help me out please.
Saurabh.010101 said:
help me i'm stuck.
my phone asus zenfone max m2 got restarted by itself and then stuck on bootloop(showing logo then switch off) . i tried something to solve it and things got even worse.
now no asus logo showing red warning ,can't flash any version of twrp(tried many)
sometimes showing this sometimes some error.
C:\adb>fastboot flash recovery twrp.img
Sending 'recovery' (38936 KB) OKAY [ 1.172s]
Writing 'recovery' OKAY [ 0.500s]
Finished. Total time: 1.726s
tried diretly booting in to recovery after flashing twrp but
fastboot boot twrp.img is not temporarily booting twrp on phone.
I don't know what to do now. help me out please.
View attachment 5368365
View attachment 5368367
View attachment 5368365View attachment 5368367
Click to expand...
Click to collapse
try this method
#Fix RED WARNING using phone
maybe you can try method 3
Surendra R sonawane said:
How to Fix BOOTLOOP | Asus Zenfone Max M2
View attachment 5308849
Requirements:
Unlocked Bootloader
Twrp installed
Download Stock ROM android 10
Download Vbmeta.img
Download Tool Kit
Download red warning fix.zip
Using toolkit you can fix
Red warning
Fastboot stuck (continuously reboot into fastboot)
Flash twrp 3.4
Lock Bootloader
Unlock Bootloader
If you facing fastboot stuck or continuously rebooting to fastboot mode
so download toolkit and extract it then connect phone to pc in fastboot mode (press volume + and power)
then run (double click) on Click me to fix stuck fastboot problem.cmd [file]
Or flash file manually
Code:
fastboot flash vbmeta vbmeta.img
Fastboot reboot
{ Now your fastboot stuck problem is fix but still phone not booting so follow below steps also you facing bootloop problem follow below steps }
------------------------------------------------------------------------------------------------------------------------
Fix BOOTLOOP using Recovery
Download any custom ROM
Download firmware
Wipe dalvik cache data, system, vendor
Flash Firmware.zip
Flash ROM.zip
Format data
Reboot system
------------------------------------------------------------------------------------------------------------------------
Fix BOOTLOOP using Stock ROM
Download stock ROM
Download magisk
Download dm-verity
Reboot recovery
Wipe dalvik,data,cache, system,vendor
Flash stock rom.zip
Format data (type yes)
Flash magisk
Flash Dm-Verity
Reboot system
Wait 5-10 minutes until phone Boot up :good:
------------------------------------------------------------------------------------------------------------------------
Fix RED WARNING using phone
Method 1
First Download RED warning fix.zip
- Reboot recovery
- Flash red warning-fix.zip
Your phone automatically boots to system
This fix only works when your system are bootable
if you facing bootloop + red warning so you need to fix bootloop then reboot system
----- Then reboot recovery then flash red warning fix.zip
------------------------------------------------------------------------------------------------------------------------
Method 2. using /ROOT
Install any terminal emulator app
Type su and hit enter
Grant root permission
Copy pest below command
reboot "dm-verity enforcing"
Now hit enter
Your device well be automatically reboot wait until it's Boot
-----------------------------------------------------------------------
Method 3
Fix using PC
Install ADB drivers on pc
Enable developers option from settings
enable USB debugging plug the cell phone into the PC,
type in cmd if not works then download minimal adb.exe
Open it
Type adb devices
(if devices have been detected, proceed to the next command just copy pest)
adb reboot "dm-verity enforcing"
The phone will automatically reboot and the red warning disappears
--------------------------------------------------------
Fix Stuck AT ASUS LOGO
Download Fix-Stuck-at-ASUS-LOGO.zip
IF you flash ROM.zip
but phone stuck at Asus logo so just flash fix stuck-at-Asus.zip
using recovery after flashing ROM.zip
OR......
Reboot recovery
Flash Fix_stuck-at-ASUS-logo.zip
Reboot system
If your Problem are solved then Enjoy
IF not then try again once (read thread carefully)
Click to expand...
Click to collapse
please update link of stuck at asus logo
Saurabh.010101 said:
please update link of stuck at asus logo
Click to expand...
Click to collapse
Link updated
zeo270183 said:
try this method
#Fix RED WARNING using phone
maybe you can try method 3
Click to expand...
Click to collapse
i was missing one step while in red warning. just pressing power button at red warning took me to recovery. this was my first time dealing with red warning.
Saurabh.010101 said:
i was missing one step while in red warning. just pressing power button at red warning took me to recovery. this was my first time dealing with red warning.
Click to expand...
Click to collapse
I haven't had a red warning problem yet, but I've had fastboot stuck and tried the tricks in this post and I succeeded and I hope you too
WARNING!
There is no official / stable release neither for twrp nor lineageos, that being said on my device the A33 5G SM-A336B-DSN *everything* works so far.
I do not take any responsibility for any damage that might happen to your device, same goes for the developers regarding unofficial twrp and lineageos releases.
{
"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"
}
This Guide will provide instructions how to install TWRP and LineageOS, the Kernel will not be modified.
• After unboxing, complete the initial setup of the Phone
• In Phone Settings press 7 times on "Build Number" to enable Developer Options
• In Developer Options enable OEM Unlock and USB Debugging
• Power Off the Phone
• Boot the Phone in OEM Unlocking Mode, for that you must:
• Hold volume up and volume down while the Phone is powered-off
• While holding the buttons connect the Phone to the PC via USB Cable
• Keep holding the buttons untill Phone is booted to OEM Unlocking Mode
• In OEM Unlocking Mode hold volume up for few seconds - This will unlock OEM and ERASE all Data
• After Erase, Complete again the initial setup and enable Developer Options aswell as USB Debugging
• Download TWRP and vbmeta_disabled_r on the PC (Credits go to Zillion for TWRP and afaneh92 for vbmeta_disabled_r)
• Boot phone in OEM Unlocking Mode and press vol-up to continue to Download Mode
• On the PC download Odin and Samsung USB Driver
• Install USB Drivers and connect the Phone to PC via USB Cable, then start Odin
• In Odin klick on AP and select a33x_experimental_twrp-tar
• In Odin klick on USERDATA and select vbmeta_disabled_r-tar
• Klick start to flash TWRP on the A33 Phone
• Download LineageOS GSI 20.0 Light Version on the PC (Credits go to Andy Yan)
• Extract the downloaded LineageOS GSI to get the .img
• Copy the "LineageOS_GSI.img" on any SD Card or USB Drive
• Insert SD Card to Phone or connect Phone to USB using USB Adapter
• Boot Phone in Recovery Mode (TWRP)
• In TWRP select INSTALL then press SELECT STORAGE, select SD Card or USB
• Choose INSTALL IMAGE and flash "LineageOS_GSI.img" to System
Note: When i first flashed Lineage, instead of booting to system the phone kept booting to recovery (twrp), i can't tell you why but it did not work.
Same happened with Andy's 19.1 Lineage GSI's.
I ended up re-flashing LineageOS GSI 20.0 Light Version again, and it suddenly worked, the phone booted to system (lineage).
If you have similar issues i suggest keep trying untill it works, like it did for me.
Many thanks to V0latyle for helping me getting twrp and lineageos running on the A33
Is it compatible with the A336M?
jejexd said:
Is it compatible with the A336M?
Click to expand...
Click to collapse
I don't know the differences between A336B and A336M
Just try it i would say. Probably will work, if not simply flash stock firmware.
• Update - For anyone following this guide, you can probably replace the TWRP listed in the original post with this one:
[RECOVERY] [OFFICIAL] [a33x] TeamWin Recovery Project 3 for Galaxy A33 5G (exynos)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
I have not personally tested it.
Privacydroid said:
I don't know the differences between A336B and A336M
Just try it i would say. Probably will work, if not simply flash stock firmware.
Click to expand...
Click to collapse
May I PM you?
have you tested the lineage os? does it run better and smoother than samsung ui?? if it does then imma do this
perfect brother. thank you soooo much it works perfectly. even tho i had some issues with twrp install it works now
jejexd said:
Is it compatible with the A336M?
Click to expand...
Click to collapse
Si, es compatible.
How did you install gapps? if I try to flash it will complain there is insufficient space. Do I have to take the lineageOS containing gapps already or is there a way to flash it without the space error ?
rgaxiola said:
Si, es compatible.
Click to expand...
Click to collapse
Vale, gracias. Ya tengo el teléfono rooteado, me gustaría la custom ROM y TWRP pero, creo ando genial con el móvil tal cuál cómo va.
Gracias por confirmar nuevamente. Tan pronto como vea viable tener LineageOS, lo instalaré.
jejexd said:
Vale, gracias. Ya tengo el teléfono rooteado, me gustaría la custom ROM y TWRP pero, creo ando genial con el móvil tal cuál cómo va.
Gracias por confirmar nuevamente. Tan pronto como vea viable tener LineageOS, lo instalaré.
Click to expand...
Click to collapse
Honestamente no te lo recomiendo si manejas aplicaciones de bancos, tuve muchos problemas, ni con Magisk pude lograr que dichas aplicaciones no detectaran el teléfono como rooteado y potencialmente peligroso.
Tuve que regresar a Samsung One UI.
Saludos
Privacydroid said:
that being said on my device the A33 5G SM-A336B-DSN everything works so far
Click to expand...
Click to collapse
Are you sure? Have you tested things like USB tethering, MMS, SMS, calling etc.? Many people just simply don't bother to test these & then say "everything works"; had a problem like that on my previous phone where I couldn't send or receive MMS despite the ROM being considered "stable"
Sithhy™ said:
Are you sure? Have you tested things like USB tethering, MMS, SMS, calling etc.? Many people just simply don't bother to test these & then say "everything works"; had a problem like that on my previous phone where I couldn't send or receive MMS despite the ROM being considered "stable"
Click to expand...
Click to collapse
WIFI thethering at 5 Ghz is broken and no NR band, and I think game are not running at 90hz. I tried to contact Andy who just ignored my message so I guess the phone is too "young" for custom rom yet
My phone is stuck in the lineageOS bootscreen, i cannot access either TWRP or OEM download mode as the button combinations do not work, can anyone help me on how may i be able to fix that issue? I used TWRP from this post because the link on this one is down
i once got stuck on the charging animation and i just held both the side buttons and the power button, it phone should then boot off
Dryfty said:
i once got stuck on the charging animation and i just held both the side buttons and the power button, it phone should then boot off
Click to expand...
Click to collapse
It does boot off, but then it boots back to lineageOS charging animation, I have tried using button combinations to open twrp and download mode
Sithhy™ said:
Are you sure? Have you tested things like USB tethering, MMS, SMS, calling etc.? Many people just simply don't bother to test these & then say "everything works"; had a problem like that on my previous phone where I couldn't send or receive MMS despite the ROM being considered "stable"
Click to expand...
Click to collapse
I don't use a simcard so i haven't tested mms/sms, anways sms is a very insecure way of communication.
For chatting i would use one of these, Briar, Element, Session.
Neither have i tested usb tethering.
The only "bug" i experience is, when charging the phone while it is powered-off, it does not charge the battery, and the screen goes on showing that it's charging but it does not show the percentage...
I'm forced to power-on the phone everytime i want to charge it, otherwise charging doesn't work, it's annoying but i'm afraid there's nothing i can do.
So that's just my personal opinion, i preffer a "relatively stable" operatingsystem which is privacy oriented rather than a fully functional privacy invasive operatingsystem.
DiegoRuiz said:
My phone is stuck in the lineageOS bootscreen, i cannot access either TWRP or OEM download mode as the button combinations do not work, can anyone help me on how may i be able to fix that issue? I used TWRP from this post because the link on this one is down
Click to expand...
Click to collapse
Hello, i had the same issue.
As DiegoRuiz said, you should be able to poweroff the phone by holding all buttons at the same time.
Then when powered off, immediately hold the buttons to boot into downloadmode and try reflashing the os again.
The process seems somewhat broken, but as i said in the original post i managed to install lineage after all.
DiegoRuiz said:
My phone is stuck in the lineageOS bootscreen, i cannot access either TWRP or OEM download mode as the button combinations do not work, can anyone help me on how may i be able to fix that issue? I used TWRP from this post because the link on this one is down
Click to expand...
Click to collapse
Did you install the custom kernel as described in this post?
"Gabriel260BR - if you don't flash the custom kernel, the system will NOT boot!"
Privacydroid said:
Did you install the custom kernel as described in this post?
"Gabriel260BR - if you don't flash the custom kernel, the system will NOT boot!"
Click to expand...
Click to collapse
Yes i did, i flashed the custom kernel and it booted correctly, it was when I installed lineageOS that I started to have this problem