It all started when I decided to unroot my phone. First I backed up my data. Second, I formatted the cell phone directly through its settings. So root was removed. So far, everything was fine. The cell phone turned on normally and I did the initial settings. After that I decided to lock the bootloader again. I put the phone in bootloader mode and gave the command to block (Fasboot flashing lock). A confirmation message appeared on my cell phone and I accepted it. After that the phone was like this... Blinking at boot. I can't enter fasboot or bootloader through the buttons.
Heelp please!!
See the problem (video link)
Diguinho76 said:
It all started when I decided to unroot my phone. First I backed up my data. Second, I formatted the cell phone directly through its settings. So root was removed. So far, everything was fine. The cell phone turned on normally and I did the initial settings. After that I decided to lock the bootloader again. I put the phone in bootloader mode and gave the command to block (Fasboot flashing lock). A confirmation message appeared on my cell phone and I accepted it. After that the phone was like this... Blinking at boot. I can't enter fasboot or bootloader through the buttons.
Heelp please!!
See the problem (video link)
Click to expand...
Click to collapse
Pretty sure factory resetting the phone from the settings doesn't remove root. You root by flashing a patched boot.img but the factory reset doesn't touch the boot partition at all. So you locked the bootloader and now the phone won't boot because the boot partition is not signed by the OEM. If you can't enter bootloader mode you only have two solution.
- Flashing in EDL mode through MSM tool. However, since this phone OnePlus requires an authorized account to flash through MSM tool. You can try requesting a remote session through the official support (probably they won't do it) or find someone on telegram or somewhere else who sells tokens for MSM tool.
- Shipping the phone to OnePlus for repair or going to a local repair center of your choice.
Did you complete unninstalled magisk or just have formatted?
TheNewHEROBRINE said:
Pretty sure factory resetting the phone from the settings doesn't remove root. You root by flashing a patched boot.img but the factory reset doesn't touch the boot partition at all. So you locked the bootloader and now the phone won't boot because the boot partition is not signed by the OEM. If you can't enter bootloader mode you only have two solution.
- Flashing in EDL mode through MSM tool. However, since this phone OnePlus requires an authorized account to flash through MSM tool. You can try requesting a remote session through the official support (probably they won't do it) or find someone on telegram or somewhere else who sells tokens for MSM tool.
- Shipping the phone to OnePlus for repair or going to a local repair center of your choice.
Click to expand...
Click to collapse
I can't believe I did this... All I wanted was to remove root and I forgot to do it through magisk. I just ****ed myself
Diguinho76 said:
I can't believe I did this... All I wanted was to remove root and I forgot to do it through magisk. I just ****ed myself
Click to expand...
Click to collapse
Just to confirm, holding vol + and vol - together at boot doesn't do anything?
Machad3x said:
Did you complete unninstalled magisk or just have formatted?
Click to expand...
Click to collapse
No.... just formatted
TheNewHEROBRINE said:
Just to confirm, holding vol + and vol - together at boot doesn't do anything?
Click to expand...
Click to collapse
Nop. nothing
Diguinho76 said:
Nop. nothing
Click to expand...
Click to collapse
I just remembered that with this phone you can't boot into EDL mode by holding the volume buttons like in the old days. To get into EDL mode you would need to disassemble the phone and short two pins and I immagine you don't want to do that at all. There are some special cables that can boot Qualcomm phones into EDL, although I don't know if they work with the OP10 Pro specifically.
I think your best option at the moment is to send it for repair to OnePlus or to whichever repair center you prefer.
Diguinho76 said:
No.... just formatted
Nop. nothing
Click to expand...
Click to collapse
When you can not boot to booloader (fastboot) or fastbootd you need a Services Center (for flash over edl with msm tool )
I got it. Payed 15$ and a guy from vietnam solved the problem for me.
FIXED!!! Flashed over edl.
Diguinho76 said:
I got it. Payed 15$ and a guy from vietnam solved the problem for me.
FIXED!!! Flashed over edl.
Click to expand...
Click to collapse
How did you put the phone into EDL?
TheNewHEROBRINE said:
How did you put the phone into EDL?
Click to expand...
Click to collapse
Vol+ Vol- Power Button ( All of them at the same time) plugged on the pc
Diguinho76 said:
Vol+ Vol- Power Button ( All of them at the same time) plugged on the pc
Click to expand...
Click to collapse
ah so it still works! I thought it wouldn't.
TheNewHEROBRINE said:
ah so it still works! I thought it wouldn't.
Click to expand...
Click to collapse
But now im trying to go to 2213... I flashed a 2213 payload.bin from fastboot enhance and its not booting the system. I can acess bootloader. Do you have any suggestion to change the region from bootloader now ?
Diguinho76 said:
But now im trying to go to 2213... I flashed a 2213 payload.bin from fastboot enhance and its not booting the system. I can acess bootloader. Do you have any suggestion to change the region from bootloader now ?
Click to expand...
Click to collapse
I would have installed the update through the settings. I don't think switching slot can help this time. The only thing I think you can do is extract the payload.bin with payload-dumper-go and flash the partitions manually through fastboot but this procedure doesn't have a 100% success rate. If you write me the partitions you extracted from the payload.bin I can write you the commands to do as I'm not used to the partition layout of the 10 Pro specifically.
TheNewHEROBRINE said:
Eu teria instalado a atualização através das configurações. Eu não acho que mudar de slot pode ajudar desta vez. A única coisa que acho que você pode fazer é extrair o payload.bin com payload-dumper-go e atualizar as partições manualmente por meio do fastboot, mas esse procedimento não tem uma taxa de sucesso de 100%. Se você me escrever as partições extraídas do payload.bin, posso escrever os comandos a serem feitos, pois não estou acostumado com o layout da partição do 10 Pro especificamente.
Click to expand...
Click to collapse
Ok. Ill try. But do you know any way to do this using fastboot enhance ?
Diguinho76 said:
Ok. Ill try. But do you know any way to do this using fastboot enhance ?
Click to expand...
Click to collapse
When you flashed the payload.bin in fastboot enhance were you in fastbootd or bootloader mode?
TheNewHEROBRINE said:
When you flashed the payload.bin in fastboot enhance were you in fastbootd or bootloader mode?
Click to expand...
Click to collapse
fastbootd
Diguinho76 said:
fastbootd
Click to expand...
Click to collapse
I don't know why it has failed then. Can you still boot to fastbootd? Or does it say something like userspace not bootable?
TheNewHEROBRINE said:
I don't know why it has failed then. Can you still boot to fastbootd? Or does it say something like userspace not bootable?
Click to expand...
Click to collapse
Yes, i can. I tried to flash the payload again but havent success
Diguinho76 said:
Yes, i can. I tried to flash the payload again but havent success
Click to expand...
Click to collapse
In the fastboot mode the touch is not working. so i cant format data etc. Only buttons working
Related
Hello.
I was on the September update, unlocked and rooted, but I wanted to update to the october one, so I uninstalled magisk and flashed the september boot and system images.
Unfortunately that didn't work (I still couldn't install the OTA), so I' ve decided to flash manually all the images of the october update (I got them on the OTA thread).
After that my device went on bootloop, so I decided to flash again all the images of the September update (V9.6.13.0).
When I run "fastboot flash system_a system.img" I got the error "Invalid argument" and after that my device turned off.
Now IT IS TOTALLY BRICKED, I can't turn it on and I can't even enter fastboot.
I really don't know what to do, do you have any idea?
If you have working fastboot try to Flash full September update with Mi flash tools, wipe everything and Lock bootloader.
After that you will receive ota from October.
Sent from my Mi A2 using Tapatalk
tomgv said:
If you have working fastboot try to Flash full September update with Mi flash tools, wipe everything and Lock bootloader.
After that you will receive ota from October.
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
As I've said, I can't enter fastboot mode.
My device is bricked
Lurensu said:
As I've said, I can't enter fastboot mode.
My device is bricked
Click to expand...
Click to collapse
Open your phone and flash through EDL mode by shorting test points...
Yep, your last hope is attempt to flash through edl mode by shorting those pins, that's why I always re-install stock rom using Mi flash through edl mode booted from fastboot
Thanks guys, I hope to find a method which doesn't require to open the device.. if I fail I'll try the test points one.
However my device is still recognized by Windows and by MiFlash as Qualcomm QDLoader 9008 and I've read that some people managed to flash a fastboot rom in this mode (on the Mi A1).
Isn't this EDL mode already?
Looking at this guide it looks like the whole point of "test points" is to get the device recognized as QDLoader 9008, isn't it?
https://forum.xda-developers.com/redmi-note-5-pro/how-to/edl-mode-redmi-note-5-pro-t3779267
Lurensu said:
Thanks guys, I hope to find a method which doesn't require to open the device.. if I fail I'll try the test points one.
However my device is still recognized by Windows and by MiFlash as Qualcomm QDLoader 9008 and I've read that some people managed to flash a fastboot rom in this mode (on the Mi A1).
Isn't this EDL mode already?
Looking at this guide it looks like the whole point of "test points" is to get the device recognized as QDLoader 9008, isn't it?
https://forum.xda-developers.com/redmi-note-5-pro/how-to/edl-mode-redmi-note-5-pro-t3779267
Click to expand...
Click to collapse
When phone is recognized as qualcomm it means it's bricked so it entered edl by itself, you can use mi flash to get back to september patch, then boot into fastboot and flash it again, then ota
EDIT: anti rollback is still not activated in october patch
Nebrassy said:
When phone is recognized as quallcomm it means it's bricked so it entered edl by itself, you can use mi flash to get back to september patch, then boot into fastboot and flash it again, then ota
EDIT: anti rollback is still not activated in october patch
Click to expand...
Click to collapse
Whoaa that's great! (well, obviously it isn't, but at least I don't have to open the phone)
Are you sure about the anti rollback? So am I safe flashing the September fastboot images?
Thank you very much, I really appreciate your help
Lurensu said:
Whoaa that's great! (well, obviously it isn't, but at least I don't have to open the phone)
Are you sure about the anti rollback? So am I safe flashing the September fastboot images?
Thank you very much, I really appreciate your help
Click to expand...
Click to collapse
Yes, all A2 firmwares got ARB set to 2, I'm on 9.6.15
also, I was on first october build 9.6.14 but I had modified vendor, so I flashed september patch then got the ota to 9.6.15 so I'm sure, there's no ARB yet
Nebrassy said:
Yes, all A2 firmwares got ARB set to 2, I'm on 9.6.15
also, I was on first october build 9.6.14 but I had modified vendor, so I flashed september patch then got the ota to 9.6.15 so I'm sure, there;s no ARB yet
Click to expand...
Click to collapse
Thank you so much, I'll try to flash the september update then, let's hope everything goes right!
EDIT:
well, everything went smoothly and I'm now on the october update
I can enter un fastboot mode but my PC doesn't recognized my device, Someone can help me?
I have all drivers installed but always the same issue.
Hi guys.. Thanks for this article!!!. It was very useful. I had my Mi A2 bricked, I was in QDLoader 9008 state, but I didn't need to disassemble the MI A2, I think as Lurensu my device was already in the QDLoader state. I reached this state trying to manually update to the November patch, then "fastboot" didn't flash the aboot_b image, yes sure; I didn't realize this until the reboot.
I had the error "Cannot receive hello packet" with fails trying to flash with MiFlash, but the solution finally, was to have pressed the Power button for various seconds then the device was again ready for flash, and finally this was flashed to the September patch. I had this image files from some tools for rooting and updating.
Thanks again!...
---------- Post added at 01:14 AM ---------- Previous post was at 01:06 AM ----------
kevin2546 said:
I can enter un fastboot mode but my PC doesn't recognized my device, Someone can help me?
I have all drivers installed but always the same issue.
Click to expand...
Click to collapse
I'm pretty sure your problem is more simple than you think. Perhaps this is not the more adequate Thread, you need the windows drivers for Mi A2. This trouble is easily "googleable" :good:
yisao said:
Hi guys.. Thanks for this article!!!. It was very useful. I had my Mi A2 bricked, I was in QDLoader 9008 state, but I didn't need to disassemble the MI A2, I think as Lurensu my device was already in the QDLoader state. I reached this state trying to manually update to the November patch, then "fastboot" didn't flash the aboot_b image, yes sure; I didn't realize this until the reboot.
I had the error "Cannot receive hello packet" with fails trying to flash with MiFlash, but the solution finally, was to have pressed the Power button for various seconds then the device was again ready for flash, and finally this was flashed to the September patch. I had this image files from some tools for rooting and updating.
Thanks again!...
---------- Post added at 01:14 AM ---------- Previous post was at 01:06 AM ----------
I'm pretty sure your problem is more simple than you think. Perhaps this is not the more adequate Thread, you need the windows drivers for Mi A2. This trouble is easily "googleable" :good:
Click to expand...
Click to collapse
hola amigo me puedes dar una mano tengo mi a2 en estado EDL no prende solo lo reconoce
gian789 said:
hola amigo me puedes dar una mano tengo mi a2 en estado EDL no prende solo lo reconoce
Click to expand...
Click to collapse
Con la herramienta Mi Flash de Xiaomi lo puedes recuperar fácilmente, todo está en Google. En parte es tener el programa MiFlash y que te bajes una ROM OEM de este sitio, lo flashees y queda como nuevo; todo esto suponiendo que no tenga un daño peor, pero eso es raro
Lurensu said:
Hello.
I was on the September update, unlocked and rooted, but I wanted to update to the october one, so I uninstalled magisk and flashed the september boot and system images.
Unfortunately that didn't work (I still couldn't install the OTA), so I' ve decided to flash manually all the images of the october update (I got them on the OTA thread).
After that my device went on bootloop, so I decided to flash again all the images of the September update (V9.6.13.0).
When I run "fastboot flash system_a system.img" I got the error "Invalid argument" and after that my device turned off.
Now IT IS TOTALLY BRICKED, I can't turn it on and I can't even enter fastboot.
I really don't know what to do, do you have any idea?
Click to expand...
Click to collapse
09
I just received this smartphone from a friend of mine.
The smartphone is locked on the "androidone" logo.
In the past I fiddled with different andorid devices but with xiaomi I am really puzzled, I don't know how to move.
I tried to enter recovery mode, pressing "vol +" and "power" without a positive result.
I can get into fastboot mode and try to flash the rom with miflasher but I get an error: can not file all.bat.
How can I solve it?
Is your bootloader unlocked?
first unlock bootloader (critical too) then try to flash original stock rom with miflash. Dont try to downgrade android version idk you know it or not but A2 has antiroolback projection which if you downgrade your android version (ex: 9.0 to 8.0) device will delete your phones IMEI code. And the only way of fix that is change main board.
Maharram said:
first unlock bootloader (critical too) then try to flash original stock rom with miflash. Dont try to downgrade android version idk you know it or not but A2 has antiroolback projection which if you downgrade your android version (ex: 9.0 to 8.0) device will delete your phones IMEI code. And the only way of fix that is change main board.
Click to expand...
Click to collapse
thanks for replay.
I tried to unlock the bootloader with adb commands but the console returns an error.
I remind you that the phone does not start.
cicci0 said:
thanks for replay.
I tried to unlock the bootloader with adb commands but the console returns an error.
I remind you that the phone does not start.
Click to expand...
Click to collapse
You must boot to phone and check oem Unlocking at developer options first. You said u can't enter recovery, at mi a2 is little bit tricky, you keep power and volume + buttons until restart and enters a black screen and after u push 1 time (without keeping buttons) power and volume + button again and it enters at recovery
vagsvag said:
You must boot to phone and check oem Unlocking at developer options first. You said u can't enter recovery, at mi a2 is little bit tricky, you keep power and volume + buttons until restart and enters a black screen and after u push 1 time (without keeping buttons) power and volume + button again and it enters at recovery
Click to expand...
Click to collapse
Arrivo alla schermata nera, ma poi non entra in recovery, premo i tasti ma non va.
I get to the black screen, but then it doesn't go into recovery, I press the keys but it doesn't work.
cicci0 said:
Arrivo alla schermata nera, ma poi non entra in recovery, premo i tasti ma non va.
I get to the black screen, but then it doesn't go into recovery, I press the keys but it doesn't work.
Click to expand...
Click to collapse
Power first volume +after, it is little bit tricky but try again it is working. Also if you can't find the compo try this at black screen hold power button and push once volume +
vagsvag said:
Power first volume +after, it is little bit tricky but try again it is working. Also if you can't find the compo try this at black screen hold power button and push once volume +
Click to expand...
Click to collapse
I have seen many videos on youtube and I realize that the system is compromised.
Recovery mode is impossible to start. Following all the steps I get only a black screen and the recovery does not start.
My question is: Can't I install the firmware via fastboot?
I saw some videos showing a jumper to send the phone to QUALCOMM mode.
Can I flash in this mode having the bootloader blocked?
cicci0 said:
I have seen many videos on youtube and I realize that the system is compromised.
Recovery mode is impossible to start. Following all the steps I get only a black screen and the recovery does not start.
My question is: Can't I install the firmware via fastboot?
I saw some videos showing a jumper to send the phone to QUALCOMM mode.
Can I flash in this mode having the bootloader blocked?
Click to expand...
Click to collapse
I can't enter to TWRP recovery u right there is a problem with some Mi A2 devices.
Qualcomm mode is EDL (Qualcomm emergency downloader) and no u can't install firmware or any other thing with bootloader locked. I have googled the enabling oem unlock via fastboot but thats too hard and complicated thing u need to know a lot of things about Android system files, fastboot and .java files to enable it if there is a someone can try to find how to do it and give us a tutorial about that that will be great because thats important thing cuz we can get boot loop with system updates .
Here is the screenshot of the enabling oem unlock via fastboot
cicci0 said:
I have seen many videos on youtube and I realize that the system is compromised.
Recovery mode is impossible to start. Following all the steps I get only a black screen and the recovery does not start.
My question is: Can't I install the firmware via fastboot?
I saw some videos showing a jumper to send the phone to QUALCOMM mode.
Can I flash in this mode having the bootloader blocked?
Click to expand...
Click to collapse
I haven't try this but I think you can do that. There are many persons here at forum that they have used this. Search them threads before u start to see exactly how you do this (I think it is time limited the edl mode via jumper)
Here is a similar situation, read the last messages, there is also a video tutorial.
https://forum.xda-developers.com/mi-a2/help/mi-a2-bricked-bootloop-solution-edl-t3911466
Solved !
I have solved with qualcomm mode.
Please give me some details about solution
cicci0 said:
I have solved with qualcomm mode.
Click to expand...
Click to collapse
which version of MiFlashTool You use. 2018 or 2016??
and which rom package you use. can you send links. oreo / pie ??
I have stuck android one logo after flashing 8.1 or 9.0 flashtool 2016.04.01(64bit) didnt open system
I do EDL mode with two pin shortcut. but rom not open anymore.
I failed at flashing my mi 9 from android 10 beta back to stock after that my mi 9 won´t restart:
-no vibration
-no fastboot logo
-no recovery enter
+my pc cant detect my phone
any thoughts or ideas?
I suggest using a edl cable first if that fails I would probably go fro a refund claim if its totally unresponsive...
Knubz1337 said:
I failed at flashing my mi 9 from android 10 beta back to stock after that my mi 9 won´t restart:
-no vibration
-no fastboot logo
-no recovery enter
+my pc cant detect my phone
any thoughts or ideas?
Click to expand...
Click to collapse
Someone else had the same problem as you on here.
Edit
Here is the link
https://forum.xda-developers.com/Mi-9/help/brick-help-t3930230/page2
Knubz1337 said:
I failed at flashing my mi 9 from android 10 beta back to stock after that my mi 9 won´t restart:
-no vibration
-no fastboot logo
-no recovery enter
+my pc cant detect my phone
any thoughts or ideas?
Click to expand...
Click to collapse
Miuiflashpro maybe? I managed to find an Italain version. Good luck mate?
What did you do? How can you "fail" to flash it?
SmallTarzan said:
What did you do? How can you "fail" to flash it?
Click to expand...
Click to collapse
Error too many links
Thargorsson said:
I suggest using a edl cable first if that fails I would probably go fro a refund claim if its totally unresponsive...
Click to expand...
Click to collapse
i ordered a xiaomi edl deep flash cable. I will try it tomorrow
Did you fix it? If so, how?
Knubz1337 said:
i ordered a xiaomi edl deep flash cable. I will try it tomorrow
Click to expand...
Click to collapse
edl without authorized account won't work....
Addymore said:
edl without authorized account won't work....
Click to expand...
Click to collapse
I couldn't enter edl Mode with the cable.
I think I will send It back
Same issue here.
I did the same thing. And it hard bricked my phone. I send it back, and they change the motherboard for me.
I have the same issue. Mine is mi9se. Managed to solve?
hi, I unlocked the bootloader, did the twrp, did the root and, when installing the pixel rom, it crashed on FASTBOOT and didn't come out anymore, help me
sd brasil said:
hi, I unlocked the bootloader, did the twrp, did the root and, when installing the pixel rom, it crashed on FASTBOOT and didn't come out anymore, help me
Click to expand...
Click to collapse
You didn't flash the last firmware.zip before flashing pixel, or a full miui rom?
On pc, no sign of life in fastboot?
Oel said:
You didn't flash the last firmware.zip before flashing pixel, or a full miui rom?
On pc, no sign of life in fastboot?
Click to expand...
Click to collapse
Sim fiz tudo... Mesmo assim entrou em unbrick...
Consegui com o miflash PRO voltar a rom original
So I ended up in the brick wagon, basically doing this:
- Tencent CN version converted to WW by vendor.
- Rooted / uptaded from root folder
- Changed fingerprint to WW
- Decided things got buggy here and there, did a factory reset
-> Slot _b is unbootable / Bricked
I tried flashall_AFT.cmd from both WW and CN raw firmware, both by clicking and command prompt, nothing happens (windows either disappear or stay still).
Phone does still answer to .\fastboot devices with powershell cmd.
Could somebody put me out of my misery ?
duck from space said:
So I ended up in the brick wagon, basically doing this:
- Tencent CN version converted to WW by vendor.
- Rooted / uptaded from root folder
- Changed fingerprint to WW
- Decided things got buggy here and there, did a factory reset
-> Slot _b is unbootable / Bricked
I tried flashall_AFT.cmd from both WW and CN raw firmware, both by clicking and command prompt, nothing happens (windows either disappear or stay still).
Phone does still answer to .\fastboot devices with powershell cmd.
Could somebody put me out of my misery ?
Click to expand...
Click to collapse
This happens when we root the phone.. so basically when you factory reset, phone tries to boot to recovery and doesn't work.. this is a known issue.. just get stock boot image for your versionand flash it using fastboot...
Thanks a lot !
duck from space said:
Thanks a lot !
Click to expand...
Click to collapse
Did it work OK flashing boot stock?
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
duck from space said:
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
Click to expand...
Click to collapse
Does the cmd window pop up briefly and go again? If so, try removing or deleting the original zip from that folder, the one with the same name as the raw. Cmd gets confused /conflicts and crashes out...
Thanks for your help dude, yes that's what it does. I already done most known tricks to solve that issue to no avail. Might try on another PC now.
duck from space said:
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
Click to expand...
Click to collapse
i have same problem too.
Experienced that as well at first, flashall_aft.cmd not doing at all. But I got it work by putting the extracted raw folder to the root of my C: in my pc.
ram4ufriends said:
This happens when we root the phone.. so basically when you factory reset, phone tries to boot to recovery and doesn't work.. this is a known issue.. just get stock boot image for your versionand flash it using fastboot...
Click to expand...
Click to collapse
if we flash stock boot image, are the phone still rooted..?
ghayathok said:
if we flash stock boot image, are the phone still rooted..?
Click to expand...
Click to collapse
No, you need to update Magisk after ota or flash root boot
I can't flash the stock boot image. It says my phone is locked. I tried relocking the bootloader and it gave me the Slot_b is unbootable message as well. Any advice?
---------- Post added at 09:12 PM ---------- Previous post was at 08:36 PM ----------
Schramx4 said:
I can't flash the stock boot image. It says my phone is locked. I tried relocking the bootloader and it gave me the Slot_b is unbootable message as well. Any advice?
Click to expand...
Click to collapse
Nevermind, I figured out I could switch the boot image over to Slot_a and that worked for me.
Just flash the raw full rom with bootloader by pc
How to do
Ajmi24 said:
How to do
Click to expand...
Click to collapse
Download the RAW firmware version you want, then;
'Extract the file on your PC. Boot the phone into fastboot mode (hold volume up then press and hold power button, Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...) connect to the side port and run "flashall_AFT.cmd" wait for it to finish and the phone will restart itself (it will take a number of minutes to complete, with the cmd window open all the time. If the cmd window only flashes up and closes down, then check the rest of the notes with this step).
NOTE: you need to remove or delete the original zip from the raw folder once extracted as it confuses the Flashall_AFT.cmd with the raw rom and zip having the same name. Also, it can help to extract to the root of C drive.'
Taken from my guide;
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
duck from space said:
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
Click to expand...
Click to collapse
BOA TARDE AMIGOS
ESTOU TENDO O MESMO PROBLEMA APÓS INSTALAR O TWRP
APAGO O TECIDO ROM WW ANDROID 10
REINICIALIZE O SISTEMA E APENAS LIGA E DIZ ESTAS INFORMAÇÕES (Slot _b não pode ser inicializado) VOCÊ PODE ME AJUDAR ONDE EU ENCONTRAR A IMAGEM DE BOOT, POSSO ENTRAR EM FASTBOOTON SMATPHONE MAS NO PC DE DISPOSITIVO DESCONHECIDO
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 !