Database Develop

Stuck in Fastboot Flash Mode PLease Help

Running everything stock and unrooted, last night I got a System Update Notification that was only a security update (around 4.0MB). I connected the Nexus 6 to the outlet with the factory charger (battery was too low to install update) and hit INSTALL UPDATE.
As usual, I got a 10 second timer for a reboot, and this is the point where I stopped looking at it and begun reading for around 10-20min. When I grabbed the phone again, it was "stuck" in the waiting for reboot screen. I hit CANCEL INSTALL a few times, thinking it had locked up, but nothing happened.
So I powered off the phone.
And now it won't boot, it's stuck in a screen saying:
Code:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.15(*) (sha-96f7faf, 2015-08-04 11_36_17)
Baseband:
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: (let me know if this is relevant)
CPU: APQ8084 ES 1.1
eMMC: 32GB SanDisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix s( SDRAW DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Staus Code: 0
Nothing I try gets past this, although using the VOL keys I can get to a BOOTLOADER LOGS option that says:
Fastboot reason: Failed to initialize partition table
I downloaded Wug's Nexus Root Toolkit and the Softbrtick option doesn't work... it seems it can't unlock the device? (Only fastboot access, no ADB).
I'm desperate here, I bought the phone directly from Motorola Mexico (I'm in Mexico) but I doubt RMA is an option? Is my phone completely bricked at this point?

It's stock, locked and unrooted. All you did was try to install their OTA right? Sounds like their fault to me.

Calleja said:
Running everything stock and unrooted, last night I got a System Update Notification that was only a security update (around 4.0MB). I connected the Nexus 6 to the outlet with the factory charger (battery was too low to install update) and hit INSTALL UPDATE.
As usual, I got a 10 second timer for a reboot, and this is the point where I stopped looking at it and begun reading for around 10-20min. When I grabbed the phone again, it was "stuck" in the waiting for reboot screen. I hit CANCEL INSTALL a few times, thinking it had locked up, but nothing happened.
So I powered off the phone.
And now it won't boot, it's stuck in a screen saying:
Code:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.15(*) (sha-96f7faf, 2015-08-04 11_36_17)
Baseband:
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: (let me know if this is relevant)
CPU: APQ8084 ES 1.1
eMMC: 32GB SanDisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix s( SDRAW DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Staus Code: 0
Nothing I try gets past this, although using the VOL keys I can get to a BOOTLOADER LOGS option that says:
Fastboot reason: Failed to initialize partition table
I downloaded Wug's Nexus Root Toolkit and the Softbrtick option doesn't work... it seems it can't unlock the device? (Only fastboot access, no ADB).
I'm desperate here, I bought the phone directly from Motorola Mexico (I'm in Mexico) but I doubt RMA is an option? Is my phone completely bricked at this point?
Click to expand...
Click to collapse
you are going to have to flash a factory image

simms22 said:
you are going to have to flash a factory image
Click to expand...
Click to collapse
But how if the Rootkit can't? I can't seem to be able to flash anything to the device :/

Calleja said:
But how if the Rootkit can't? I can't seem to be able to flash anything to the device :/
Click to expand...
Click to collapse
rootkit is nothing official and only has in it whatever the developer has in it, flashing a factory image is why we have fastboot. if the rootkit cant do it, fastboot can. anyways, new users, newbs, should never be using root toolkits.

simms22 said:
rootkit is nothing official and only has in it whatever the developer has in it, flashing a factory image is why we have fastboot. if the rootkit cant do it, fastboot can. anyways, new users, newbs, should never be using root toolkits.
Click to expand...
Click to collapse
I wouldn't consider myself a newb, I've used fastboot and adb to flash factory images before. I used the toolkit in this instance because googling around made the toolkit's Soft Brick option seem like my best bet. It did not work.
How do I do that if the Fastboot Flash Mode seems to be borked/soft bricked and I can't seem to unlock the bootloader?

Calleja said:
I wouldn't consider myself a newb, I've used fastboot and adb to flash factory images before. I used the toolkit in this instance because googling around made the toolkit's Soft Brick option seem like my best bet. It did not work.
How do I do that if the Fastboot Flash Mode seems to be borked/soft bricked and I can't seem to unlock the bootloader?
Click to expand...
Click to collapse
because before unlocking the bootloader, you have to enable the developer setting. if your bootloader is still locked, then there is nothing that you can do except try to get a rma, sorry.

simms22 said:
because before unlocking the bootloader, you have to enable the developer setting. if your bootloader is still locked, then there is nothing that you can do except try to get a rma, sorry.
Click to expand...
Click to collapse
The developer setting WAS unlocked before all this started.... the problem seems to be with the partition table? Does anyone have any ideas?

Calleja said:
The developer setting WAS unlocked before all this started.... the problem seems to be with the partition table? Does anyone have any ideas?
Click to expand...
Click to collapse
oh, it was unlocked? and you tried unlocking the bootloader?

simms22 said:
oh, it was unlocked? and you tried unlocking the bootloader?
Click to expand...
Click to collapse
Yeah, using fastboot I can see the phone with "fastboot devices" but both "fastboot flashing unlock" and "fastboot flashing unlock_critical" give FAILED errors... are there other commands I'm missing?

Calleja said:
Yeah, using fastboot I can see the phone with "fastboot devices" but both "fastboot flashing unlock" and "fastboot flashing unlock_critical" give FAILED errors... are there other commands I'm missing?
Click to expand...
Click to collapse
Have you tried doing fastboot oem unlock? The cammands you're using are for the 6P

nms247 said:
Have you tried doing fastboot oem unlock? The cammands you're using are for the 6P
Click to expand...
Click to collapse
Yeah, fastboot oem unlock brings up:
FAILED (command write failed (Unknown error))
The funny thing is I get the same exact error when I try "fastboot oem device-info", is that a driver/fastboot installed wrong thing, maybe? (I had only used fastboot from OSX before, now on Win10, although "fastboot devices" does seem to work)

Calleja said:
Yeah, using fastboot I can see the phone with "fastboot devices" but both "fastboot flashing unlock" and "fastboot flashing unlock_critical" give FAILED errors... are there other commands I'm missing?
Click to expand...
Click to collapse
you are missing the one and only command that you can unlock the bootloader with.. fastboot oem unlock. if it gets unlocked, then you can flash a factory image.

simms22 said:
you are missing the one and only command that you can unlock the bootloader with.. fastboot oem unlock. if it gets unlocked, then you can flash a factory image.
Click to expand...
Click to collapse
Ok, so if "fastboot oem unlock" returns "FAILED (remote failure) there's nothing whatsoever I can do? RMA is the only option?
The first android device I don't root and leave completely stock and it's the only one I've ever bricked..... sigh

No, Google bricked it, with his stupid OEM unlocking switch, which is totally stupid. But they'll give you a new one.

istperson said:
No, Google bricked it, with his stupid OEM unlocking switch, which is totally stupid. But they'll give you a new one.
Click to expand...
Click to collapse
Anyone know how trustworthy Motorola's RMA service is in Mexico? Bought the N6 through motorola.com.mx, kinda regretting that decision now.

help
Calleja said:
Running everything stock and unrooted, last night I got a System Update Notification that was only a security update (around 4.0MB). I connected the Nexus 6 to the outlet with the factory charger (battery was too low to install update) and hit INSTALL UPDATE.
As usual, I got a 10 second timer for a reboot, and this is the point where I stopped looking at it and begun reading for around 10-20min. When I grabbed the phone again, it was "stuck" in the waiting for reboot screen. I hit CANCEL INSTALL a few times, thinking it had locked up, but nothing happened.
So I powered off the phone.
And now it won't boot, it's stuck in a screen saying:
Code:
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.15(*) (sha-96f7faf, 2015-08-04 11_36_17)
Baseband:
Product/Variant: shamu XT1103 32GB P3A0
Serial Number: (let me know if this is relevant)
CPU: APQ8084 ES 1.1
eMMC: 32GB SanDisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix s( SDRAW DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Staus Code: 0
Nothing I try gets past this, although using the VOL keys I can get to a BOOTLOADER LOGS option that says:
Fastboot reason: Failed to initialize partition table
I downloaded Wug's Nexus Root Toolkit and the Softbrtick option doesn't work... it seems it can't unlock the device? (Only fastboot access, no ADB).
I'm desperate here, I bought the phone directly from Motorola Mexico (I'm in Mexico) but I doubt RMA is an option? Is my phone completely bricked at this point?
Click to expand...
Click to collapse
How do you overcome? can show me the
thanks !

Nexus 6 stuck in fastboot

Howdy XDA peoples.
I'm hoping someone can help me. I had a Nexus 6, unrooted (atlhough the bootloader was unlocked when I purchased it). I had been recieving the official beta Android updates, but am not sure what version I got up to. Recently, while listening to some music on my drive home, the phone stopped. When I arrived home, I saw that it had put itself into Fastboot Mode, although it all looked slightly different (more 8-bit I guess). If I try and boot Android normally, whether from a powered off state, or from Fastboot etc, it fails, every time, and just boots into this 8 bit fastboot. (Although if I boot into Fastboot from a powered off state, it shows the usual Fastboot you would expect on the nexus 6. The 8 bit style one has the exact same functionality and control, just looks different). I have tried hooking it up to the Nexus Toolkit, which seems to behave normally and says its doing whatever I ask it to do, but still, nothing. I simply cannot boot into Android. In the Fastboot menu, Under bootloader logs, it displays the following message: "failed to validate boot image: ret=-1. Fastboot Reason: Fall-through from normal boot mode." The same happens if I try to boot into recovery.
If someone could nudge me in the right direction (or perhaps direct me to a forum where this issue has been dealt with, I have searched...), I would be immensely grateful.

Can you post a picture or type out the contents of this 8bit fastboot screen?

geokhentix said:
Can you post a picture or type out the contents of this 8bit fastboot screen?
Click to expand...
Click to collapse
I can type it.
So on the first screen that pops up.
Start
AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.21 (sha-f12f8c2, 2016-05-10 11:30:37)
Baseband:
Product/Variant: shamu XT1100 32GB P3A0
Serial Number: ZX1G423NQB
CPU: APQ8084 ES1.1
eMMC: 32GB Sandisk RV=07 PV=01 TY=57
DRAM: 3072MB Hynix S8 SDRAM DIE=6GB
Console (NULL): null
Battery OK (Charging)
Device is UNLOCKED. Status Code: 3
Transfer Mode: USB Connected
The colours are accurate (except what is typed in black above is white on the phone screen). On the bootloader screen:
Bootloader logs
Fastboot Reason: Reboot mode set to fastboot
USB connected
failed to validate recovery image: ret=-1
Boot up failed

Just like what had happened to you, mine bootlooped today, was listening to some music, the phone just restarted itself and went into an endless bootloop, any help or fix for that ? (Also, I've been running android N beta for almost a month now, and this was the first "bug/something" to happen to me)

looks like we are in same.boat
http://forum.xda-developers.com/nexus-6/help/how-to-flash-nexus-6-xt1103-rom-t3444017

Factory Image
Do You try to manually flash a Factory Image? Maybe not one from the N Preview? Otherwise to flash a Custom Recovery and try to flash a random Custom ROM?

James Bartlett said:
failed to validate recovery image: ret=-1
Click to expand...
Click to collapse
Unfortunately, I currently get the very same message for my Nexus 6 device.
It had also began 'all of a sudden', ie. without any attempts to root or whatever.
Given this applies to recovery mode as well, I fear adb sideload method with OTA is not possible.
Did you somehow manage to rescue your device?

Help me please, I don´t have gapps installed...

Hello to everyone.
I hope somebody to help me, last night i tried to update mi Lineage OS 16 (from erfanoabdi).
My device is unlocked bootloader, and i used the rom from nightly build (2018-21-09), it works fine and everything, the issue becomes when i look what was avaible a new update, so downloaded and install the new rom.
I do full wipe, after that i install the new rom, at this point everything its working fine, but after that when i changed the partition slot from A to B.
When i started to install the gapps they closed because it says what i am running Android 8.0, but its a mistake so i think that reboot the phone without install the gapps. So the phone starts well, so i decide again to boot into recovery (TWRP) to install the missing gapps.
When the device reboot in fastboot and i chosee the recovery option, the surprise was that TWRP was reemplaced by the stock recovery, and when i tried to flash the TWRP.img my device wont appear in fastboot mode, stays finding device and Windows wont recognized my phone.
I think the rom still no have usb adb support, so i cant flash TWRP
My device its unlocked and i was running the rom (but another nightly) .. without issues for a week ago... until i flashed this one
Now i have Lineage OS without GAPPS, without USB mode... Like the update from OPW 27 or 28 idk remember.
Its possible to fix? or my phone its ****ed, or there is one form to installl the gapps from anoter form?
Thanks for read this i hope somebody can help me.
My device its a XT1900-4 in Android 9.0 without google apps, only have the essencial apps like phone dialer , sms, the very very essencials app. Like an phone from 2008 jhaha
i offer some pay.
Update:
I attach some information photos from the Rom that im running:
(System Running) fine thanks
https://ibb.co/bXC7ye
(ADB is switched on, but no appears nothing)
https://ibb.co/exGpBz
(I tried with everyone of the opcions
https://ibb.co/ekv5jK
and this is my currently fastboot:
AP Fastboot Flash Mode (Secure)
BL: MBM-3.0-uefi-641a15b-180224
Baseband: M660_7042.27.01.74R PAYTON_LATAM_CUST
Product/Variant: payton xt1900-4 32GB P4
CPU: SDM630 1.0 (6)
Console [NULL]: null
Tools Mode Config: DISABLED
POWER OK
flashing_unlocked
Software status: Official
Transfer Mode: USB Connected
At this point my windows so says to my device is Error in a request for the USB device descriptor.
i tried last_usb_google driver.
Motorola Device manager 2.5.4
Minimal adb fastboot 1.4.2
and nothing works fine.
In my recovery appears this:
Android Recovery
motorola/payton/payton
8.0.0/OPW27.57.25-6-10/12
user/release-keys
Use volume to...etc and then i used the (Apply update from adb)
says:
Supported API: 3
Stopping adbd. . .
Now send the package you want to apply to the device with "adb sideload <filename>"
Help me pls:crying:

I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli

Gravemind2015 said:
I have a Nokia 7 plus which is also a A/B device. I have observed many times that the fastboot mode isn't detected by the pc. Sometimes when I have a bootloop during experimentation, I force reboot into bootloader mode but it's not recognised. I reboot into recovery and select "reboot to bootloader", and this time it's recognised. Maybe these issues are related to A/B system, I'm not sure.
I think you should have the Motorola device manager installed if you're working on Windows. It contains the necessary drivers. I can't remember if it contains adb and fastboot executable files, but if it does then try using them (launching command prompt from there).
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.

vmmiguel said:
thanks for quicky reply, but i tried that and it doesnt work for me... :c
the motorola device manager its installed correctly, but i think the usb in the Android 9 it´s no working on running s.o and even in fastboot.
Click to expand...
Click to collapse
My windows cmputer says that my device doesnt works properly, i read all night about this and i think when i some point i made wipe /system so i delete the twrp and the rom doesnt have usb adb i think so hahaha, i think now my x4 will stuck on only aosp 9.0 without g services :crying::crying::crying:

id start with a flash all of the latest stock firmware to clean it up. then start over

edufur said:
id start with a flash all of the latest stock firmware to clean it up. then start over
Click to expand...
Click to collapse
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...

vmmiguel said:
I tried but i have only stock recovey, and the usb adb it's not working, i think that i need to flash stock rom from stock recovery, but i dont know...
Click to expand...
Click to collapse
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.

Comby_sk said:
You have to flash stock rom from fastboot. Try removing "fastboot erase userdata" from script flash-all.
Click to expand...
Click to collapse
Hello Buddy, i tried that but doesnt work, recently i discover that my usb default mode is gray so i think i cant switch beetwen the usb option, and i tried ADB over network, in terminal emulator to run adbd service but it crash :c
@erfanoabdiadbi plz you cant help me, i really i was enjoying you excelent deveploment, but now in stuck in this without essencial apps like whatsapp, my smartphone works like only phone without been smart jajaja:crying::good:

Anyone?

vmmiguel said:
Anyone?
Click to expand...
Click to collapse
Read through this thread carefully...
https://forum.xda-developers.com/moto-x4/development/rom-lineage-16-0-developer-preview-t3849699

I have more or less the same problem.
I am stuck in LineageOS 15.1 and for some reason Windows does not recognize my phone (it does with other x4 phone from a friend).
I also don't have GApps installed and also don't have root access. Since I can't connect my phone, I can't root or flash some custom recovery.
I really need some help.

Moto X 2nd Gen, XT1092

Hi peoples.
And thanks to read me.
I would like to know, my work mate just gift me a motorola XT1092 becose he installed a stock rom on it to solve a screen problem.
The screen problem is solved but now the tactil isn't working anymore.
I assum he installed the wrong rom on it.
Ok so now you know evrything.
First question can i install an other rom on it ?
How ?
With or without enabling the usb debog mode ?
I work in the IT so i am ok if you point me in the good direction even if it's hard to do.
I just want to reinstall an official rom on it. To see if it's the current problem.
The things I can do =
-Normal Boot
-I can see the screen (But if you ccan provide me a way without OTG cable)
-I can boot in recovery mode but nothing work if i try to repeir or anything it is just rebooting in normal mode.
This is what the recovry mode show me :
AP Fastboot Flash mode (S)
61.00 (sha-130760b, 2016-08-24 12:39:46)
CPU: MSM8974AC ES1.1
eMMC 16GB Samsung RV=07 PV=0B TY=57
DRAM: 2048Mb ELPIDA S8 SDRAM DIE=4Gb
BATTERY OK
DEVICE is LOCKED. Statut code 0
Software status : Official
Connect USB Data Cable
He dont know if it was 5.1 or 6 before the rom (upgrade?)
Thanks guys.

Here how to: https://youfirmware.org/flash-stock-rom-motorola-moto-g-devices-tutorial/ and here stock lollypop: https://mega.nz/#!z9NQwJqJ!DXJPuTTB9-2FJOSkAcw6TDROL7Rs69RYlWMpGqHK0Pc password: www.stockrom.net

Bootloop after October security update on rooted device.

Hello, I have some problems on my Mi A2. I rooted the device in August to enable Camera2API (getting stuck in the security update of the same month.). I installed Magisk and everything was going well. Then came a notification regarding the October update. I clicked to upgrade and by the time it was done, the device was working perfectly until the moment it completely discharged its battery. After that it gets into Bootloop on the Android One boot screen. I would like some suggestions for the solution. Thanks.

until the moment it completely discharged its battery
Click to expand...
Click to collapse
same here! I am not rooted and not unlocked.

Exactly the same here...

fly23 said:
same here! I am not rooted and not unlocked.
Click to expand...
Click to collapse
This was 2 days ago. It worked again after about 150 reboots. Or i pushed a special button combination, I don't know.
In betweet I did one "fastboot reboot".
Now I have the same problem again after empty battery. Bootloop.
This is the worst android phone I ever bought after HTC desire, Galaxy Nexus, Nexus 5, 5X. I will never again buy a budget phone or a xiaomi.

I did a factory reset this morning, and itgot stuck on an Android One screen. I am trying to figure out how to reflash it, but it doesn't seem to like the firmware. Not sure if I have to unlock the bootloader? I am not family with any of this stuff. I was supposed to ship the phone to the buyer today, but I guess I may have to kill the deal and refund them. This may be the last Xiaomi I buy.
https://imgur.com/a/5J51w3D

for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me

[email protected] said:
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
Click to expand...
Click to collapse
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.

clocks11 said:
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
Click to expand...
Click to collapse
Yeah, I wonder that as well.
The arrow down + power button combination just keeps the phone frozen on a fancy picture with "fast boot" written at the bottom of the screen.

clocks11 said:
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
Click to expand...
Click to collapse
You need PC for that
Boot into fastboot (vol - + PWR)
Then use fasboot from terminal
First look which slot is active by typing
fastboot getvar current-slot
Then we can change active slot using this commands
fastboot --set-active=a
or:
fastboot --set-active=b

Unfortunately, to be able to switch booting slot one needs fully unlocked phone (bootloader and critical partitions in our case).
Being fully unlocked, one can boot device in fastboot into TWRP, and from there:
- change slots
- wipe Dalvik/Art cache (and other Cache partition if present) - which in turn very often helps to recover from OTA-generated bootloop

Aerobatic said:
Unfortunately, to be able to switch booting slot one needs fully unlocked phone (bootloader and critical partitions in our case).
Being fully unlocked, one can boot device in fastboot into TWRP, and from there:
- change slots
- wipe Dalvik/Art cache (and other Cache partition if present) - which in turn very often helps to recover from OTA-generated bootloop
Click to expand...
Click to collapse
I think this is why my phone is completely bricked. It does not have an unlocked bootloader, so it seems I can't flash firmware on it. I will likely never buy Xiaomi again after this. I just was doing a factory reset since I had sold the phone.

[email protected] said:
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
Click to expand...
Click to collapse
this method works perfectly to me :good: ! my Mi A2 update to Oct 5 2019 patch okk. but i want to restart my phone. after restart, my phone is bootloop then luckily i found this usefull guide. thanks you very much again! Android One on Xiaomi is really sh*t.

ngohoainam said:
this method works perfectly to me :good: ! my Mi A2 update to Oct 5 2019 patch okk. but i want to restart my phone. after restart, my phone is bootloop then luckily i found this usefull guide. thanks you very much again! Android One on Xiaomi is really sh*t.
Click to expand...
Click to collapse
I'm still not clear how to change slot. Does the the phone have to be unlocked for this? Is special PC software needed? My A2 has been a brick for almost a week now.

clocks11 said:
I'm still not clear how to change slot. Does the the phone have to be unlocked for this? Is special PC software needed? My A2 has been a brick for almost a week now.
Click to expand...
Click to collapse
yes. you need your phone to be unlocked Bootloader and Critical Partition to use fastboot. more info here ( read Prerequisites carefully )
after you unlocked your phone and unlock Critical Partition. turn off you phone and after that press both Power and volumn down button at the same time. then your phone is booted to fastboot mode.
in fastboot mode. type fastboot getvar current-slot . after that the system will return your current slot. example: b
then you type fastboot --set-active=a
then you disconnect your phone to PC and then reboot again.
then you turn off your phone again and turn your phone to fastboot mode. then you type this command again: fastboot --set-active=b
then you disconnect your phone and boot your phone normally. after that your phone is fixed from bootloop.
ps: remember to download the driver and minimal fastboot so that your pc recognize your phone is connected to your pc

ngohoainam said:
yes. you need your phone to be unlocked Bootloader and Critical Partition to use fastboot. more info here ( read Prerequisites carefully )
after you unlocked your phone and unlock Critical Partition. turn off you phone and after that press both Power and volumn down button at the same time. then your phone is booted to fastboot mode.
in fastboot mode. type fastboot getvar current-slot . after that the system will return your current slot. example: b
then you type fastboot --set-active=a
then you disconnect your phone to PC and then reboot again.
then you turn off your phone again and turn your phone to fastboot mode. then you type this command again: fastboot --set-active=b
then you disconnect your phone and boot your phone normally. after that your phone is fixed from bootloop.
ps: remember to download the driver and minimal fastboot so that your pc recognize your phone is connected to your pc
Click to expand...
Click to collapse
Unfortunately, I think I am screwed, as the phone was not unlocked prior to my boot issue. So I am not sure there is anything I can do. I can get to fastboot though.