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
Related
Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp
erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.
hello everybody ,, if anyone facing as same my problem
ulocked bootloader and rooted then i received notification for android Pie Update
so i did it but after restart it went to bootloop for 1 hour amd still same problem , any ideas please ?
I had same problem, with MiFlash I put 9.6.10.0 and updated to 9.6.17.0
Pretty happy with this software, stable and everything works. Stay away from Pie, a lot of bugs.
Sent from my Mi A2 using Tapatalk
I had to factory reset
I had same problem. Any solution?
Odesláno z mého X52X pomocí Tapatalk
Cocagy said:
hello everybody ,, if anyone facing as same my problem
ulocked bootloader and rooted then i received notification for android Pie Update
so i did it but after restart it went to bootloop for 1 hour amd still same problem , any ideas please ?
Click to expand...
Click to collapse
If you have unlocked bootloader try with fastboot file & Mi flash tool
http://en.miui.com/download-353.html
Read Method 2: Fastboot : http://en.miui.com/a-234.html
you have to go V9.6.16.0.ODIMIFE (Android O) & after if you want update to 9.6.17 etc...
Factory Reset can not do anything in this case
[Or try with edl mode... https://in.c.mi.com/thread-37902-1-0.html
https://forum.xda-developers.com/showpost.php?p=77327325&postcount=2 ] it is not easy but can be save the device
sry for english
I tried many ways with different roms but nothing worked and bootloader locked at the end .. so i had to reset and install full rom ..anyway there wasn't important data .. thanks for your help
@ i have another question
I installed pie 10.0.2 is there patched boot for magisk and how to enable camera 2 api ..
Cocagy said:
I tried many ways with different roms but nothing worked and bootloader locked at the end .. so i had to reset and install full rom ..anyway there wasn't important data .. thanks for your help
@ i have another question
I installed pie 10.0.2 is there patched boot for magisk and how to enable camera 2 api ..
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/xiaomi-mi-a2-android-9-pie-update-t3868101
see & here : https://forum.xda-developers.com/mi-a2/how-to
Cocagy said:
I tried many ways with different roms but nothing worked and bootloader locked at the end .. so i had to reset and install full rom ..anyway there wasn't important data .. thanks for your help
@ i have another question
I installed pie 10.0.2 is there patched boot for magisk and how to enable camera 2 api ..
Click to expand...
Click to collapse
Can you explain to me how you did to reset everything thank you
Pouvez vous m'expliquer comment vous avez fait pour tout réinitialisier merci
papavegan said:
Can you explain to me how you did to reset everything thank you
Pouvez vous m'expliquer comment vous avez fait pour tout réinitialisier merci
Click to expand...
Click to collapse
I downloaded the official rom from miui 8.1 then flashed it with miflasher then i upgraded it via ota , flashed patched boot for 10.0.1 and made some commands to enable camera 2api for gcam v 6+
Cocagy said:
I downloaded the official rom from miui 8.1 then flashed it with miflasher then i upgraded it via ota , flashed patched boot for 10.0.1 and made some commands to enable camera 2api for gcam v 6+
Click to expand...
Click to collapse
I am in the same situation, but instead of a bootloop, it just gets stuck in the "androidone" screen.
I can access fastboot, but not recovery menu. And of course the bootloader is locked. So I do not even now how to do the factory reset... or flash the official rom... (It always says not possible in lock state from fast boot).
Any help/specific instructions would be appreciated.
Thanks in advance
salchi13 said:
I am in the same situation, but instead of a bootloop, it just gets stuck in the "androidone" screen.
I can access fastboot, but not recovery menu. And of course the bootloader is locked. So I do not even now how to do the factory reset... or flash the official rom... (It always says not possible in lock state from fast boot).
Any help/specific instructions would be appreciated.
Thanks in advance
Click to expand...
Click to collapse
it seems like boot issue ..
If the data in storage not important you can unlock bootloader and it will force you to factory reset
If still same problem then you should flash thought miflasher and download official rom and flash it
Cocagy said:
I downloaded the official rom from miui 8.1 then flashed it with miflasher then i upgraded it via ota , flashed patched boot for 10.0.1 and made some commands to enable camera 2api for gcam v 6+
Click to expand...
Click to collapse
Cocagy said:
it seems like boot issue ..
If the data in storage not important you can unlock bootloader and it will force you to factory reset
If still same problem then you should flash thought miflasher and download official rom and flash it
Click to expand...
Click to collapse
Thanks, at this point I don´t even care about the data... and most of it is backed up.
The problem is that I had not selected the OEM unlock option, the command fasboot oem unlock does not work, and the miflash_unlock tool tells my that my account is not valid to unlock the phone. So I do not really know how to unlock the bootloader. Do you know if there is another way to unlock it/flash, that does not require opening the phone?
Context:
en.miui.com-thread-4697442-1-1
en.miui.com-thread-3560322-1-1
Thanks
For me the problem seems to be related to magisk, once I restored the original boot.img, the phone boots. If I try to flash the magisk patched boot image, it returns to bootloop. I'm using magisk v18 btw. I'm unable to get root using magisk on this PIE version
salchi13 said:
Thanks, at this point I don´t even care about the data... and most of it is backed up.
The problem is that I had not selected the OEM unlock option, the command fasboot oem unlock does not work, and the miflash_unlock tool tells my that my account is not valid to unlock the phone. So I do not really know how to unlock the bootloader. Do you know if there is another way to unlock it/flash, that does not require opening the phone?
Context:
en.miui.com-thread-4697442-1-1
en.miui.com-thread-3560322-1-1
Thanks
Click to expand...
Click to collapse
You can use these commands on fastboot mode .. it should work then try to flash rom
fastboot flashing unlock
fastboot flashing unlock_critical
I have the same problem, stuck in the androidone mode... How do I save my data , if not possible (i have all photos and videos from south america trip there) than how to unlock bootloader and do factory reset ? ^_
norbertpoland said:
I have the same problem, stuck in the androidone mode... How do I save my data , if not possible (i have all photos and videos from south america trip there) than how to unlock bootloader and do factory reset ? ^_
Click to expand...
Click to collapse
If you are lucky, maybe you activated the photo and video backups and the videos/photos from your trips have been uploaded to https://photos.google.com from the different wifi hotspots that you may have connected to.
Cant unlock by miflash unlock cause it state that my device is not assosiated with the phone number (WTF !?) how to do hard reset in that situation when only androinone logo shows me or fastboot mode. Please help me guys I am in Rio for carnival and cant make normal photos withouyt phone
Just to add that it happened at 1 of march probably after some actualization or something.
norbertpoland said:
Cant unlock by miflash unlock cause it state that my device is not assosiated with the phone number (WTF !?) how to do hard reset in that situation when only androinone logo shows me or fastboot mode. Please help me guys I am in Rio for carnival and cant make normal photos withouyt phone
Click to expand...
Click to collapse
Had the same problem, in the end I decided to send it back for warranty repairs... and that fixed it of course, they probably had to open it to flash it in EDL mode, which I think you can do if you have the right screwdriver to open the phone.
https://www.youtube.com/watch?v=Uu7V0cBu41k
Thanks buty I m not technican to open and dig inside Is there any other possibility ?
norbertpoland said:
Thanks buty I m not technican to open and dig inside Is there any other possibility ?
Click to expand...
Click to collapse
If You are able to boot phone into bootloader (even with black screen, you can check with "fastboot devices" or looking for "Android Bootloader Interface" driver in Win DevManager), you can try this: https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718 to boot phone into EDL without opening case. More than that, may be its worth trying even simple "fastboot oem edl" command),
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 !
I was trying to get lineage and made a lot of mistakes... Now i dont have download mode, my phone is bootlooping on the LG V40 logo screen... Please help me out!!
Do you know if you are able to get into 9008 mode? If you are able to, it might be possible to save your phone still.
Having the same issue
I have the same issue, and yes I can ONLY get into it and nothing else...
I'm no longer with AT&T and wanted to use my V405 with T-Mobile, I know now that I can't but, I still wanted to have it unlocked to cross upgrade to the unlocked 405QA version, any assistance will be greatly appreciated.
If it is still bootloader unlocked and still has fastboot then you can still save it by using adb to boot into twrp. You don't need to wipe laf partition/download mode because you can always access fastboot either way so its pointless to nuke it.
Crossflashing will not make it unlocked for carrier use. You have to carrier unlock it before crossflashing. Just go out and buy an phone unlocked for the us market or the V405QA7 model.
I'm having also same problem AT&T coming from cross flashed pie
I need help!!!!
My phone is bricked flashing Lineage 17.1 and series of lots of mistakes...
erased laf_a laf_b till i got to unable to fastboot flash anything and it will return CANT FLASH IN UNLOCK STATE...
Tried to relock bootloader if it will solved the issue only worsen things...
Now,
no download mode no fastboot and connecting charger doesn't charge phone the security warning pops up and when i try to use vol+ and usb to pc combination, i get to the security warning page and ALL SLOT ARE UNBOOTABLE error...
Pc doesnt recognise phone it only reboots to same security warning screen
Any help please?
---------- Post added at 05:02 PM ---------- Previous post was at 04:39 PM ----------
Factory reset holding VOL- POWER BUTTON, releasing POWER BUTTON when screen on and still keeping VOL- pressed and pressing POWER BUTTON again doesn't change anything.
I'd suggest to those having these issues it to get into edl / qfil mode and flash (u saved them right?) the original abl (a and b) and original laf (a and b). Then get into lgup / download mode (hopefully) and flash a stock rom.
The thing about getting into qfil is that you can do it from **any** screen (well, maybe not with the device off, never tried that scenario). The difference doing it in other screens than a booted device is you won't get any 'count down' screen, you'll just have to wait the 5 seconds and when screen changes spam the vol up.
good luck
AsItLies said:
I'd suggest to those having these issues it to get into edl / qfil mode and flash (u saved them right?) the original abl (a and b) and original laf (a and b). Then get into lgup / download mode (hopefully) and flash a stock rom.
The thing about getting into qfil is that you can do it from **any** screen (well, maybe not with the device off, never tried that scenario). The difference doing it in other screens than a booted device is you won't get any 'count down' screen, you'll just have to wait the 5 seconds and when screen changes spam the vol up.
good luck
Click to expand...
Click to collapse
Luckily I was able to get to edl mode even when phone turned off
Turn off your phone and boot into edl mode (when phone is off connect usb or leave usb connected and immediately hold vol down and power buttons and keep rapidly pressing the vol up)
---------- Post added at 06:58 PM ---------- Previous post was at 06:42 PM ----------
AsItLies said:
I'd suggest to those having these issues it to get into edl / qfil mode and flash (u saved them right?) the original abl (a and b) and original laf (a and b). Then get into lgup / download mode (hopefully) and flash a stock rom
Click to expand...
Click to collapse
the original abl (a and b) and original laf (a and b)?
That is where the problem is now!!! :crying:
Instructions GUIDE by Xsavi never adviced to save the original abl and laf_a laf_b
Coming from Cross flashed US Unlocked 20e stock pie to Lineage 17.1(not latest)
Please how do I solve this???
yemkoid said:
Luckily I was able to get to edl mode even when phone turned off
Turn off your phone and boot into edl mode (when phone is off connect usb or leave usb connected and immediately hold vol down and power buttons and keep rapidly pressing the vol up)
---------- Post added at 06:58 PM ---------- Previous post was at 06:42 PM ----------
the original abl (a and b) and original laf (a and b)?
That is where the problem is now!!! :crying:
Instructions GUIDE by Xsavi never adviced to save the original abl and laf_a laf_b
Coming from Cross flashed US Unlocked 20e stock pie to Lineage 17.1(not latest)
Please how do I solve this???
Click to expand...
Click to collapse
Try these, they should work.
AsItLies said:
Try these, they should work.
Click to expand...
Click to collapse
LIKE A CHARM! :good::good::good::good:
Many Thanks
abl and laf flashed appropriately to each slot and i now have download mode
Flashed stock pie 20e and starting over again
thanks , work
AsItLies said:
Try these, they should work.
Click to expand...
Click to collapse
Can you help me to get the abl and laf_a laf_b for v409N android Q?
My V409N also stuck in fastboot after i flash a wrong oreo image to abl_a.
Thanks!!!
hkguy80 said:
Can you help me to get the abl and laf_a laf_b for v409N android Q?
My V409N also stuck in fastboot after i flash a wrong oreo image to abl_a.
Thanks!!!
Click to expand...
Click to collapse
is it 30d? 30e? 30f? I don't think they are interchangeable....
AsItLies said:
is it 30d? 30e? 30f? I don't think they are interchangeable....
Click to expand...
Click to collapse
Is there anyway to figure out which version it is in the EDL?
EDL is the only thing i can enter now.
Can I flash the rom via EDL directly?
hkguy80 said:
Is there anyway to figure out which version it is in the EDL?
EDL is the only thing i can enter now.
Can I flash the rom via EDL directly?
Click to expand...
Click to collapse
No, edl can't 'flash' a rom. Just look at the kdz file you used, it will say the version in it.
Also, you can take that kdz and use the utilities that separate out all the partitions. But I may have them already, but need version to be sure.
AsItLies said:
No, edl can't 'flash' a rom. Just look at the kdz file you used, it will say the version in it.
Also, you can take that kdz and use the utilities that separate out all the partitions. But I may have them already, but need version to be sure.
Click to expand...
Click to collapse
I didn't flashed any KDZ as the the seller flashed it already.
Since I only flashed the ABL_A, Can I save the ABL_B from the phone and comparing it with your files to guess which ABL_A should be used?
hkguy80 said:
I didn't flashed any KDZ as the the seller flashed it already.
Since I only flashed the ABL_A, Can I save the ABL_B from the phone and comparing it with your files to guess which ABL_A should be used?
Click to expand...
Click to collapse
they are all the same size, don't think that will tell you anything.
Here's what to do, use edl to save the 'b' versions (hopefully you didn't overwrite those also). Then take them and flash them to 'a'. Then write down what your version is when it boots
AsItLies said:
No, edl can't 'flash' a rom. Just look at the kdz file you used, it will say the version in it.
Also, you can take that kdz and use the utilities that separate out all the partitions. But I may have them already, but need version to be sure.
Click to expand...
Click to collapse
I just found that I may click "Read Data" during EDL before i flash the ABL_A. and i found this file ReadData_ufs_Lun4_0xdd06_Len256_DT_25_04_2021_19_07_11. Should I flashed it to ABL_A again and try to boot it again?
hkguy80 said:
I just found that I may click "read partition" before i flash the ABL_A. and i found this file ReadData_ufs_Lun4_0xdd06_Len256_DT_25_04_2021_19_07_11. Should I flashed it to ABL_A again and try to boot it again?
Click to expand...
Click to collapse
you obviously haven't used qfil at all. Yes, what u want to do is 'read partition' after selecting abl_b. Then, as you know, the file is a bizarre name found in the folder / port that qfil is using.
That file will match the output name given when it reads the data. All you need to is rename the file to (whichever partition you backed up) like abl_b.img
Then select that abl_a partition and use the manager to 'load' an image to that partition, select the one u just saved.
Keep in mind, I have no idea which one of your slots is active. In the examples above, it's assuming your 'a' slot is the active slot. If it's not! then reverse a and b examples above.
So, in worst case scenario, I'd suggest you save off both your abl_a and abl_b, and rename the results to something like abl_a_current, and abl_b_current, that way if copying one to the other doesn't make it boot, redo it but copy the opposite ones back. (because you're not on the slot you think it is.)
make sense?
AsItLies said:
you obviously haven't used qfil at all. Yes, what u want to do is 'read partition' after selecting abl_b. Then, as you know, the file is a bizarre name found in the folder / port that qfil is using.
That file will match the output name given when it reads the data. All you need to is rename the file to (whichever partition you backed up) like abl_b.img
Then select that abl_a partition and use the manager to 'load' an image to that partition, select the one u just saved.
Keep in mind, I have no idea which one of your slots is active. In the examples above, it's assuming your 'a' slot is the active slot. If it's not! then reverse a and b examples above.
So, in worst case scenario, I'd suggest you save off both your abl_a and abl_b, and rename the results to something like abl_a_current, and abl_b_current, that way if copying one to the other doesn't make it boot, redo it but copy the opposite ones back. (because you're not on the slot you think it is.)
make sense?
Click to expand...
Click to collapse
Yes..Italso help me to understand more about the qfil.
Thanks a lot for your help..
I just figured out that I actually backed up the original abl_a before i flashed the v35eng.img. After i restore the original abl_a to abl_a, my phone finally resume normal.
Can you also suggest a proper way to restore fastboot on my phone? because I want to disable the vbmeta and replace the open_kr with open_us.
hkguy80 said:
Yes..Italso help me to understand more about the qfil.
Thanks a lot for your help..
I just figured out that I actually backed up the original abl_a before i flashed the v35eng.img. After i restore the original abl_a to abl_a, my phone finally resume normal.
Can you also suggest a proper way to restore fastboot on my phone? because I want to disable the vbmeta and replace the open_kr with open_us.
Click to expand...
Click to collapse
good. Yes the best way, especially with korean rom, is to flash the v35 eng abl to your not active slot, which I think in your case is 'b', so abl_b.
the key to that working is you need to have twrp installed, so you can use it to set 'b' partition as active, then select 'reboot bootloader' and it will boot to fastboot. You can then use fastboot and follow the info in this vbmeta link. Read the directions.
the other option (if u don't have twrp yet), would be to flash v35 eng to a, boot to fastboot, do the vbmeta stuff, then use fastboot to flash the original abl_a back, so it will boot.
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