Database Develop

Removing warning bootloader unlocked

hi
i unlocked my bootloader and then i reflash thr original firmware and lock the bootloader succesfully
but the red warning of bootloader unlocked still is present every time i power on my moto x
some help?
thank u
( i tried with a original logo from Moto g but got a weird image with all blured lines)

There's a thread for this. It's not difficult to find.

nhizzat said:
There's a thread for this. It's not difficult to find.
Click to expand...
Click to collapse
/// solved
thank u

danger2u said:
/// solved
thank u
Click to expand...
Click to collapse
How did you solve it because no matter what I do the warning still there .... Thanks

aburyan1 said:
How did you solve it because no matter what I do the warning still there .... Thanks
Click to expand...
Click to collapse
put in fastbootmode
download this recovery
https://drive.google.com/file/d/0BwTULBGmnkwqYVlkODlva2hNbzA/edit?usp=sharing
make a folder and copy adb files and mfastboot
open a cmd or terminal in that folder
write in cmd the folowing comands
mfastboot devices
mfastboot flash recovery logo_nowarning-4.4.bin
mfastboot reboot
done
enjoy

aburyan1 said:
How did you solve it because no matter what I do the warning still there .... Thanks
Click to expand...
Click to collapse
Keep in mind the logo.bin (used if you unlocked your bootloader) has changed between versions, so 4.2.2 uses a different file from 4.4. You need to make sure you're using the right file for the ROM version on your phone.
And if you've seen the threads on using the clogo.bmp, that is for an locked bootloader that has never been unlocked.
Consider also reading this thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961
---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------
danger2u said:
put in fastbootmode
download this recovery
https://drive.google.com/file/d/0BwTULBGmnkwqYVlkODlva2hNbzA/edit?usp=sharing
make a folder and copy adb files and mfastboot
open a cmd or terminal in that folder
write in cmd the folowing comands
mfastboot devices
mfastboot flash recovery logo_nowarning-4.4.bin
mfastboot reboot
done
enjoy
Click to expand...
Click to collapse
dude... your command "mfastboot flash recovery logo_nowarning-4.4.bin" is not correct. that would be trying to flash the logo.bin file over the recovery partition. you want to use "mfastboot flash logo logo_nowarning-4.4.bin" and this assumes the person is on 4.4 or 4.4.2.
---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------
I've posted this elsewhere....
for unlocked bootloader phone, or one that has been unlocked and relocked, it would be...
Code:
adb reboot bootloader
fastboot flash logo name.bin
(where name.bin is the name of your new logo file)
and these steps should be performed with phone normally booted, and USB Debugging enabled.
The first command mitigates the need to power off and try and mess with buttons while powering on
On a side note... For those interested in making your own LOGO.BIN...
There is already a thread discussing how to do that -> Moto X Boot Logos which includes a script by carock -> <HERE> to help make it easier. NOTE1: you might want to see THIS POST with tips on formatting the graphics you want to use with the script. NOTE2: The LOGO.BIN format was different between 4.2.2 and 4.4. This script does work with KitKat 4.4. I have not looked to see if the KitKat 4.4.2 logo.bin has changed or not.
For my contribution of sharing...
I took the 24 CLOGO's from -> HERE, converted them to logo.bin's using carock's script. And did one or two others I found that I liked. I put them in -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip (when you un-zip it, there will be two folders, one containing the original graphics so you can see them and choose without flashing, and one with the logo.bin's. NOTE: the originals can be used by those with locked booloaders looking to flash their clogo.bmp). These flash fine on my Verizon Moto X Developer Edition with unlocked bootloader and KitKat 4.4.

KidJoe said:
Keep in mind the logo.bin (used if you unlocked your bootloader) has changed between versions, so 4.2.2 uses a different file from 4.4. You need to make sure you're using the right file for the ROM version on your phone.
And if you've seen the threads on using the clogo.bmp, that is for an locked bootloader that has never been unlocked.
Consider also reading this thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961
---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------
dude... your command "mfastboot flash recovery logo_nowarning-4.4.bin" is not correct. that would be trying to flash the logo.bin file over the recovery partition. you want to use "mfastboot flash logo logo_nowarning-4.4.bin" and this assumes the person is on 4.4 or 4.4.2.
---------- Post added at 04:49 PM ---------- Previous post was at 04:44 PM ----------
I've posted this elsewhere....
for unlocked bootloader phone, or one that has been unlocked and relocked, it would be...
Code:
adb reboot bootloader
fastboot flash logo name.bin
(where name.bin is the name of your new logo file)
and these steps should be performed with phone normally booted, and USB Debugging enabled.
The first command mitigates the need to power off and try and mess with buttons while powering on
On a side note... For those interested in making your own LOGO.BIN...
There is already a thread discussing how to do that -> Moto X Boot Logos which includes a script by carock -> <HERE> to help make it easier. NOTE1: you might want to see THIS POST with tips on formatting the graphics you want to use with the script. NOTE2: The LOGO.BIN format was different between 4.2.2 and 4.4. This script does work with KitKat 4.4. I have not looked to see if the KitKat 4.4.2 logo.bin has changed or not.
For my contribution of sharing...
I took the 24 CLOGO's from -> HERE, converted them to logo.bin's using carock's script. And did one or two others I found that I liked. I put them in -> http://mark.cdmaforums.com/X-STUFF/X-LogoBins.zip (when you un-zip it, there will be two folders, one containing the original graphics so you can see them and choose without flashing, and one with the logo.bin's. NOTE: the originals can be used by those with locked booloaders looking to flash their clogo.bmp). These flash fine on my Verizon Moto X Developer Edition with unlocked bootloader and KitKat 4.4.
Click to expand...
Click to collapse
this was tested and working great on Moto x xt1053
is the same logo as before the unlocked bootloader
i just want to help
if my thread is not helping u can close it

[Q] HELP PLEASE Deleted OS cant install rom

I was trying to install ViperOne and everything went south. I somehow deleted my OS in the process. ADB is not working it only freezes my computer. I was able to ADB Push my viperone.zip but I tried the install and it fail for some reason and now it seems to be in a boot loop please help me with this.

also
i have been read all threads on here and there not really helping. just want to put that out there so i dont get called lazy for not searching.

1. Fix ADB issues.

SaHiLzZ said:
1. Fix ADB issues.
Click to expand...
Click to collapse
not sure of the reason for the freezing om the computer.

MuskRat40 said:
not sure of the reason for the freezing om the computer.
Click to expand...
Click to collapse
without adb you can't do anything.
please tell us more about what you did? What recovery are you using? What version? What rom version (and link please)? also post the output of ''fastboot getvar all'' minus IMEI/SN when in bootloader.
and what operating system are you using on your computer?

alray said:
without adb you can't do anything.
please tell us more about what you did? What recovery are you using? What version? What rom version (and link please)? also post the output of ''fastboot getvar all'' minus IMEI/SN when in bootloader.
and what operating system are you using on your computer?
Click to expand...
Click to collapse
***TAMPERED***
***UNLOCKED***
M7_UL PUT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-3.62.206.1
eMMC-BOOT 2048MB
I rooted my phone with the Hasoon2000 AIO kit
downloaded ViperOne5.5.0 from the link Here on XDA
I tried to install said ROM but it said it failed
so i thought I might delete a few thing and trying to rush because im at a library my OS was one of the things to go.
ADB pushed Viper back onto phone tried to install again and failed
tried to reboot and its a loop only thing opening now is fastboot and hboot
recovery flashes on for a sec then its gone.

fastboot erase cache did let me back into recovery but will not install
ViperOne v5.5.0 install failed
installer status 7

MuskRat40 said:
I rooted my phone with the Hasoon2000 AIO kit
Click to expand...
Click to collapse
Never use toolkit, learn how to use adb and fasboot. Toolkit are for lazy ppl imo. When something goes wrong with a toolkit then you can't know why.
MuskRat40 said:
downloaded ViperOne5.5.0 from the link Here on XDA
Click to expand...
Click to collapse
Did you downloaded the M7 version of viperone or the sprint version?
MuskRat40 said:
I tried to install said ROM but it said it failed
so i thought I might delete a few thing and trying to rush because im at a library
Click to expand...
Click to collapse
Take your time and don't rush, you will make things worse.
please answer all my questions:
please tell us more about what you did? What recovery are you using? What version? What rom version (and link please)? also post the output of ''fastboot getvar all'' minus IMEI/SN when in bootloader.
and what operating system are you using on your computer?
Click to expand...
Click to collapse
erase cache and flash latest twrp (2.6.3.3 or 2.6.3.4)
then use adb to push rom to sdcard or adb sideload your rom.
---------- Post added at 04:15 PM ---------- Previous post was at 04:07 PM ----------
MuskRat40 said:
fastboot erase cache did let me back into recovery but will not install
ViperOne v5.5.0 install failed
installer status 7
Click to expand...
Click to collapse
make sure you are using the correct recovery for your phone variant
md5 checksum the recovery.img after download before you flash it
also md5 checksum the rom before pushing it to the phone
did you selected ''full wipe'' at the installation?

alray said:
Never use toolkit, learn how to use adb and fasboot. Toolkit are for lazy ppl imo. When something goes wrong with a toolkit then you can't know why.
Did you downloaded the M7 version of viperone or the sprint version?
Take your time and don't rush, you will make things worse.
please answer all my questions:
erase cache and flash latest twrp (2.6.3.3 or 2.6.3.4)
then use adb to push rom to sdcard or adb sideload your rom.
Click to expand...
Click to collapse
right now im usind twrp touch v2.6.0.1 i downloaded the m7 verson and the tool is not getting the other stuff

alray said:
Never use toolkit, learn how to use adb and fasboot. Toolkit are for lazy ppl imo. When something goes wrong with a toolkit then you can't know why.
Did you downloaded the M7 version of viperone or the sprint version?
Take your time and don't rush, you will make things worse.
please answer all my questions:
erase cache and flash latest twrp (2.6.3.3 or 2.6.3.4)
then use adb to push rom to sdcard or adb sideload your rom.
---------- Post added at 04:15 PM ---------- Previous post was at 04:07 PM ----------
make sure you are using the correct recovery for your phone variant
md5 checksum the recovery.img after download before you flash it
also md5 checksum the rom before pushing it to the phone
did you selected ''full wipe'' at the installation?
Click to expand...
Click to collapse
md5?? not sure how to do that

MuskRat40 said:
right now im usind twrp touch v2.6.0.1 i downloaded the m7 verson and the tool is not getting the other stuff
Click to expand...
Click to collapse
your recovery version is pretty out dated.
as i said before, don't use toolkit, you know why now...
download latest twrp recovery here
Code:
fastboot flash recovery <name_of_file>.img
fastboot erase cache
fastboot reboot-bootloader
then go back in recovery and flash the rom again and select full wipe.

alray said:
your recovery version is pretty out dated.
as i said before, don't use toolkit, you know why now...
download latest twrp recovery here
Code:
fastboot flash recovery <name_of_file>.img
fastboot erase cache
fastboot reboot-bootloader
then go back in recovery and flash the rom again and select full wipe.
Click to expand...
Click to collapse
you are the man!!! TWRP was out dated. It says it was successful. its loading now. Thank you so much.

MuskRat40 said:
you are the man!!! TWRP was out dated. It says it was successful. its loading now. Thank you so much.
Click to expand...
Click to collapse
np, glad it worked
hope you learned this:
don't use toolkit
don't rush
newer roms don't like old recoveries (especially 4.4 roms) So in the future be sure to update your recovery to latest version (or that one specified in the rom thread) before flashing.
hope you'll enjoy your new rom :highfive:

[Q] (Bootloader) Failed to Erase partition Moto X 2014

I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error. I cannot even go into recovery I am stuck anyone please help!.
I am getting Failed to erase partition error when i try to flash anything!.

vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error. I cannot even go into recovery I am stuck anyone please help!.
I am getting Failed to erase partition error when i try to flash anything!.
Click to expand...
Click to collapse
If you are in bootloader mode you should be able to get into recovery. Just hit volume down to scroll to recovery and then volume up to select recovery.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked.
Click to expand...
Click to collapse
Just remember - you cannot downgrade the bootloader or the partition table!!

JulesJam said:
If you are in bootloader mode you should be able to get into recovery. Just hit volume down to scroll to recovery and then volume up to select recovery.
---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------
Just remember - you cannot downgrade the bootloader or the partition table!!
Click to expand...
Click to collapse
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!

vignesh245 said:
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!
Click to expand...
Click to collapse
What should I do now!! to get my phone back working!

vignesh245 said:
It's not going into recovery or rebooting the only thing I see is the fastboot menu!! What ever I do to flash it says failed to erase partition!! can you tell me why this error in fastboot!
Click to expand...
Click to collapse
well the last guy who got that error had to format his data partition but he had an unlocked bootloader with TWRP and could get into TWRP.
What happens when you connect your phone in bootloader mode to your PC, open a command shell and type:
fastboot devices
Does it return your device's serial number?
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
vignesh245 said:
What should I do now!! to get my phone back working!
Click to expand...
Click to collapse
You should not be trying to flash a lower version of the partition table!!!!
You may have to do a factory reset.
---------- Post added at 07:18 PM ---------- Previous post was at 07:16 PM ----------
vignesh245 said:
I tried to go back to Stock with factory images from Motorola Unlocked. When i try fastboot flash partition gpt.bin it shows Preflash Validation Failed and Failed to erase partition error.
Click to expand...
Click to collapse
gpt.bin is the partition table. If you were trying to flash a lower version partition table than your bootloader version, you cannot do that!!!
What is your bootloader version?

JulesJam said:
well the last guy who got that error had to format his data partition but he had an unlocked bootloader with TWRP and could get into TWRP.
What happens when you connect your phone in bootloader mode to your PC, open a command shell and type:
fastboot devices
Does it return your device's serial number?
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
You should not be trying to flash a lower version of the partition table!!!!
You may have to do a factory reset.
Click to expand...
Click to collapse
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.

vignesh245 said:
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.
Click to expand...
Click to collapse
Is Motorola Device Manager installed on your computer? If not, install it:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Then connect your phone in fastboot mode to your computer and run MDM and see if MDM can repair your phone.
Also - are you using version 2 of mfastboot to flash?

vignesh245 said:
Thanks for the reply!!
Yes it returns a Serial number in fastboot! How flash the correct partition?.
Click to expand...
Click to collapse
its 60.11

vignesh245 said:
its 60.11
Click to expand...
Click to collapse
I am using normal fastboot ! and I have MDM install will try to repair using MDM !!

vignesh245 said:
its 60.11
Click to expand...
Click to collapse
That is the lollipop 5.0 bootloader. What version of stock were you trying to flash? Kit Kat 4.4.4? If so, that is what happened here - you tried to downgrade the partition table. You cannot downgrade the partition table once you upgrade the bootloader.
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
vignesh245 said:
I am using normal fastboot ! and I have MDM install will try to repair using MDM !!
Click to expand...
Click to collapse
OK let me know how it goes.

JulesJam said:
That is the lollipop 5.0 bootloader. What version of stock were you trying to flash? Kit Kat 4.4.4? If so, that is what happened here - you tried to downgrade the partition table. You cannot downgrade the partition table once you upgrade the bootloader.
---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------
OK let me know how it goes.
Click to expand...
Click to collapse
Thanks for the clarity in reply!!
Where can i get the stock rom and Files for lolipop 5.0 ?? So I can get back to my stock recovery!

vignesh245 said:
Thanks for the clarity in reply!!
Where can i get the stock rom and Files for lolipop 5.0 ?? So I can get back to my stock recovery!
Click to expand...
Click to collapse
Did MDM not fix your phone? Are you on the XT1095?
http://www.graffixnyc.com/motox.php#
Also, I don't know what build you are, there looks to be more than 1 build for 5.0. Check out the support thread that the link above links too.

JulesJam said:
Did MDM not fix your phone? Are you on the XT1095?
http://www.graffixnyc.com/motox.php#
Also, I don't know what build you are, there looks to be more than 1 build for 5.0. Check out the support thread that the link above links too.
Click to expand...
Click to collapse
MDM did not fix my phone yes I am on Xt1095.
Thanks will try it and let you know

vignesh245 said:
MDM did not fix my phone yes I am on Xt1095.
Click to expand...
Click to collapse
OK, it is probably the custom recovery.

JulesJam said:
OK, it is probably the custom recovery.
Click to expand...
Click to collapse
I am getting Preflash validation failed and I found I have 22.21.11 version installed using MDM. and it says in pink color error in phone as failed to downgrade primary_apt.
Can you help me with this now??

vignesh245 said:
I am getting Preflash validation failed and I found I have 22.21.11 version installed using MDM. and it says in pink color error in phone as failed to downgrade primary_apt.
Can you help me with this now??
Click to expand...
Click to collapse
I would not mess around with the partition table. See if you can do
fastboot format data
fastboot format cache
To wipe your data and cache partitions.

JulesJam said:
I would not mess around with the partition table. See if you can do
fastboot format data
fastboot format cache
To wipe your data and cache partitions.
Click to expand...
Click to collapse
I cannot do that it says the error as in the attached screenshot!
When I select recovery using volume up it says ||boot up failed||
Can Motorola help my situation Mine is a pure edition?
||version downgraded for primary_gpt||

vignesh245 said:
Can Motorola help my situation Mine is a pure edition?|
Click to expand...
Click to collapse
Yes. It is still under warranty. I would get a warranty replacement. If you can't flash anything in BL mode and can't get into recovery and MDM can't repair your phone, idk what else to do.
Motorola should let everyone who unlocks their bootloader know you can't downgrade the bootloader or partition table. They should release the factory images of every version of Android for a device and let people know they have to stick to the version for their bootloader
Quite frankly, this is Motorola's fault for not doing that.

JulesJam said:
Yes. It is still under warranty. I would get a warranty replacement. If you can't flash anything in BL mode and can't get into recovery and MDM can't repair your phone, idk what else to do.
Motorola should let everyone who unlocks their bootloader know you can't downgrade the bootloader or partition table. They should release the factory images of every version of Android for a device and let people know they have to stick to the version for their bootloader
Quite frankly, this is Motorola's fault for not doing that.
Click to expand...
Click to collapse
Thanks a lot will contact motorola get my device replaced !.

vignesh245 said:
I cannot do that it says the error as in the attached screenshot!
When I select recovery using volume up it says ||boot up failed||
Can Motorola help my situation Mine is a pure edition?
||version downgraded for primary_gpt||
Click to expand...
Click to collapse
try using the "erase" command instead of format, I've found on my PC format works, but on Mac I need to use erase.

I think I might have bricked my device

Tried to do things that are way over my head. After flashing lineage os and deciding to go back to stock, I have erased the OS. I wiped everything in twrp. I cannot boot my phone or access twrp, I can only access fastboot mode. I tried to flash the factory firmware but I recieve an error whenever it tries to erase "clogo" giving me a message: "bootloader permission denied failed remote failure." I have no idea how I can fix this. I am using a moto g5s plus US single sim model.

L4ndon said:
Tried to do things that are way over my head. After flashing lineage os and deciding to go back to stock, I have erased the OS. I wiped everything in twrp. I cannot boot my phone or access twrp, I can only access fastboot mode. I tried to flash the factory firmware but I recieve an error whenever it tries to erase "clogo" giving me a message: "bootloader permission denied failed remote failure." I have no idea how I can fix this. I am using a moto g5s plus US single sim model.
Click to expand...
Click to collapse
Almost impossible to really hard brick an Android device.
1 - install twrp - recommend the r15 version found in the forums
2 - forget lineage, what's available for this device isn't ready for prime time. Install another room - recommend latest pe (pretty much stock experience), but right now it has 1 fault - and to fix that you have to get the 1-17 version, extract boot.img and flash in twrp. Kernel frequencies are capped in the last 2 builds.
Simple!

Phazmos said:
Almost impossible to really hard brick an Android device.
1 - install twrp - recommend the r15 version found in the forums
2 - forget lineage, what's available for this device isn't ready for prime time. Install another room - recommend latest pe (pretty much stock experience), but right now it has 1 fault - and to fix that you have to get the 1-17 version, extract boot.img and flash in twrp. Kernel frequencies are capped in the last 2 builds.
Simple!
Click to expand...
Click to collapse
So wait, what version of twrp should i install? I was using twrp 3.1.1 sanders r9 prior to the brick. I am using a US single sim variant.

L4ndon said:
So wait, what version of twrp should i install? I was using twrp 3.1.1 sanders r9 prior to the brick. I am using a US single sim variant.
Click to expand...
Click to collapse
All info needed was already supplied.

L4ndon said:
Tried to do things that are way over my head. After flashing lineage os and deciding to go back to stock, I have erased the OS. I wiped everything in twrp. I cannot boot my phone or access twrp, I can only access fastboot mode. I tried to flash the factory firmware but I recieve an error whenever it tries to erase "clogo" giving me a message: "bootloader permission denied failed remote failure." I have no idea how I can fix this. I am using a moto g5s plus US single sim model.
Click to expand...
Click to collapse
Error in clogo is normal
Don't worry
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
L4ndon said:
So wait, what version of twrp should i install? I was using twrp 3.1.1 sanders r9 prior to the brick. I am using a US single sim variant.
Click to expand...
Click to collapse
R15 made by cheakyourscreen

Adi5 said:
Error in clogo is normal
Don't worry
---------- Post added at 08:05 AM ---------- Previous post was at 08:03 AM ----------
R15 made by cheakyourscreen
Click to expand...
Click to collapse
My only issue is when i would try to flash stock it w0uldnt remove twrp or the custom boot animation i hade like it had done before so I assumed I had an error along the way.

Phazmos said:
Almost impossible to really hard brick an Android device.
1 - install twrp - recommend the r15 version found in the forums
2 - forget lineage, what's available for this device isn't ready for prime time. Install another room - recommend latest pe (pretty much stock experience), but right now it has 1 fault - and to fix that you have to get the 1-17 version, extract boot.img and flash in twrp. Kernel frequencies are capped in the last 2 builds.
Simple!
Click to expand...
Click to collapse
So I am able to flash a rom based on oreo even though I am on nougat right now?

L4ndon said:
So I am able to flash a rom based on oreo even though I am on nougat right now?
Click to expand...
Click to collapse
I recommend flash stock ROM,twrp And ROM
But You can flash from nougat but Make backup

Adi5 said:
I recommend flash stock ROM,twrp And ROM
But You can flash from nougat but Make backup
Click to expand...
Click to collapse
Every time I try to flash twrp I get this message in fastboot:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'twrp.img'
C:\Program Files (x86)\Minimal ADB and Fastboot>
I cant boot into my existing twrp either. The only thing I can access is the bootloader.

L4ndon said:
Every time I try to flash twrp I get this message in fastboot:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
error: cannot load 'twrp.img'
C:\Program Files (x86)\Minimal ADB and Fastboot>
I cant boot into my existing twrp either. The only thing I can access is the bootloader.
Click to expand...
Click to collapse
Hmmm
You can flash stock images?

L4ndon said:
So I am able to flash a rom based on oreo even though I am on nougat right now?
Click to expand...
Click to collapse
If done properly, yes

Adi5 said:
Hmmm
You can flash stock images?
Click to expand...
Click to collapse
Thanks guys. I ended up fixing the issue. My twrp and stock firmware files weren't in the actual adb folder, just on a folder with the adb shortcut which is why it couldn't locate the files. I seriously can't believe something like that flew over my head. Again, thank you guys so much.

L4ndon said:
Thanks guys. I ended up fixing the issue. My twrp and stock firmware files weren't in the actual adb folder, just on a folder with the adb shortcut which is why it couldn't locate the files. I seriously can't believe something like that flew over my head. Again, thank you guys so much.
Click to expand...
Click to collapse
If using Windows, you can add an environmental variable to the executable location so it'll work from anywhere

Stuck in TWRP

So basically I was installing TWRP onto my Mi A2. I installed twrp on slot b using fastboot flash boot_b twrp.img When then trying to boot into the b slot using fastboot set_active b That command wasn't recognized. I tried installing JDK and SDK manager to get the latest syntax etc. of adb/fastboot. I tried everything again and accidently typed fastboot flash boot twrp.img . This made me flash twrp to my a slot too. The new adb/fastboot syntax still didn't recognize the set_active command. So now I'm simply stuck with twrp on both my slots. I tried installing havoc-OS v2.0 for GSI. downloading the img.xz file. Extracting it and tried flashing it on slot a. But it kind of failed. This was the code:
PS C:\Users\noahe\Desktop\Ny mapp\platform-tools> fastboot flash system_b havoca2.img
target reported max download size of 536870912 bytes
sending sparse 'system_b' (524284 KB)...
OKAY [ 17.596s]
writing 'system_b'...
OKAY [ 0.001s]
sending sparse 'system_b' (524284 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 18.764s
PS C:\Users\noahe\Desktop\Ny mapp\platform-tools> fastboot reboot
rebooting...
finished. total time: 0.001s
I would appreciate some help

It sounds like (at least initially) your version of fastboot doesn't understand dual slots? an older version? You say you updated right? The new version does understand dual slots I'm assuming?
First thing, what happens if you press power and vol UP and hold them both until it starts to reboot?

Stop using minimal adb, use this
https://developer.android.com/studio/releases/platform-tools
Flash the stock boot image and it should work
EDIT: since you tried flashing system, flash stock system again too

If all that results in is you staying in TWRP, look at twrp and hopefully it's one of the newer versions that allows you to set the 'active slot'. Hopefully choosing the other slot and then indicating reboot in twrp will cause the device to boot normally.

AsItLies said:
It sounds like (at least initially) your version of fastboot doesn't understand dual slots? an older version? You say you updated right? The new version does understand dual slots I'm assuming?
First thing, what happens if you press power and vol UP and hold them both until it starts to reboot?
Click to expand...
Click to collapse
Nothing really, the only thing on my both slots are twrp so I can't boot into other recovery modes etc.

Nebrassy said:
Stop using minimal adb, use this
Flash the stock boot image and it should work
EDIT: since you tried flashing system, flash stock system again too
Click to expand...
Click to collapse
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.

ncse said:
Nothing really, the only thing on my both slots are twrp so I can't boot into other recovery modes etc.
Click to expand...
Click to collapse
As mentioned then, just flash stock boot.img, for the version that your device is currently running. The various stock boot images are easily found, along with the patched_boot.img (that you don't want).
The only issue is that the 2 slots, one will be the most current software you last updated to, the other will be the previous version you updated from. Do you know which one as active and what version it was running? If not, sounds like you'll have to guess.
If you can get one slot to boot you can then probably fix the other okay.
---------- Post added at 09:38 ---------- Previous post was at 09:29 ----------
ncse said:
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
Click to expand...
Click to collapse
I'd stop flashing roms. Yer bootloader is the problem now, not the rom.

AsItLies said:
As mentioned then, just flash stock boot.img, for the version that your device is currently running. The various stock boot images are easily found, along with the patched_boot.img (that you don't want).
The only issue is that the 2 slots, one will be the most current software you last updated to, the other will be the previous version you updated from. Do you know which one as active and what version it was running? If not, sounds like you'll have to guess.
If you can get one slot to boot you can then probably fix the other okay.
---------- Post added at 09:38 ---------- Previous post was at 09:29 ----------
I'd stop flashing roms. Yer bootloader is the problem now, not the rom.
Click to expand...
Click to collapse
Do I only flash the boot.img file? I don't know if you noticed but the jasmine 9.6.15 is a folder with all the stock images.
I know before all this i was on slot a with the 9.6.15 update

ncse said:
Do I only flash the boot.img file? I don't know if you noticed but the jasmine 9.6.15 is a folder with all the stock images.
I know before all this i was on slot a with the 9.6.15 update
Click to expand...
Click to collapse
If you haven't change system, you haven't flashed any rom to it, on slot a, then yeah, just flash the boot.img for that version to slot a. You should then be able to set that as active (if it isn't already) and boot.

AsItLies said:
If you haven't change system, you haven't flashed any rom to it, on slot a, then yeah, just flash the boot.img for that version to slot a. You should then be able to set that as active (if it isn't already) and boot.
Click to expand...
Click to collapse
Now i get bootloops. Should I flash system.img too? Apprently all this fault is because you have to type .\fastboot.exe instead of fastboot in powershell.
EDIT: I flashed system.img too. It works again. Thanks for all the help!

ncse said:
I don't know if you can help with this but when trying to flash roms via MiFlashTool i get the error "flash devcfg_a error"
I've tried both jasmine 9.6.13 and jasmine 9.6.15 updates and they both get stuck at this. I even tried another computer.
Do you know if I should try to flash the rom manually via powershell/command prompt?
Because I'm not really sure how to do that.
Click to expand...
Click to collapse
Fastboot flashing unlock_critical