Database Users

Bluetooth Issues, Tried Fastboot flash AND mFastboot for Shiggles. Need some aid.

Hey folks, So I just can't seem to keep from screwing something up, so I could really use some help.
I have the xt1575 on sprint. Few days ago I ran into the problem where my baseband was erased from my device. Well I fixed that with RootJunky's tutorial. Well it would seem my BTFM.bin file is missing, took a vacation or was forcefully and violently removed from my device.
I have tried everything I can think of, I have searched everything under the Help section that has the word bluetooth in it. Everything I could find said to use Fastboot and viola it works. Well not for me. I have tried that. I have put that command in 2-3 times and nothing seems to "stick" . This is the command for mfastboot
Code:
mfastboot flash bluetooth BTFM.bin
and it outputs this
Code:
C:\Users\UsernameHere\Desktop\RSD_Lite_Motorola_XML_To_Batch_Script\mfast>mfastboot flash bluetooth BTFM.bin
target max-sparse-size: 256MB
sending 'bluetooth' (1295 KB)...
OKAY [ 0.031s]
writing 'bluetooth'...
OKAY [ 0.060s]
finished. total time: 0.093s
this is the command for fastboot used
Code:
fastboot flash bluetooth BTFM.bin
and i am given this as the output
Code:
C:\Users\skell\Desktop\bluetooth fastboot>fastboot flash bluetooth BTFM.bin
(bootloader) has-slot:bluetooth: not found
target reported max download size of 536870912 bytes
sending 'bluetooth' (1295 KB)...
OKAY [ 0.030s]
writing 'bluetooth'...
OKAY [ 0.054s]
finished. total time: 0.086s
So with all that said. Can anyone offer any help?

Is the Bluetooth firmware your flashing match the version of ROM you have installed? Is not, it needs to...
Otherwise flash the full factory image, not just the BT firmware.

acejavelin said:
Is the Bluetooth firmware your flashing match the version of ROM you have installed? Is not, it needs to...
Otherwise flash the full factory image, not just the BT firmware.
Click to expand...
Click to collapse
Thank you for replying, I am like 80% sure it is the correct firmware. I pulled it from 6.0 MPH24.49-18. Which I downloaded from Moto themselves. Would flashing another rom rectify the issue? For example RR or Aicp?
Genuinely thank you. I know these questions probably get old.
I flashed AICP and it would seem I have a BT mac address again. That leads me to believe that I will no longer have issues connecting to my Car. I thank you for your support and suggestions. If there is any change I will post in the Q&A forum moving forward. Thank you again!

Onclot said:
Thank you for replying, I am like 80% sure it is the correct firmware. I pulled it from 6.0 MPH24.49-18. Which I downloaded from Moto themselves. Would flashing another rom rectify the issue? For example RR or Aicp?
Genuinely thank you. I know these questions probably get old.
I flashed AICP and it would seem I have a BT mac address again. That leads me to believe that I will no longer have issues connecting to my Car. I thank you for your support and suggestions. If there is any change I will post in the Q&A forum moving forward. Thank you again!
Click to expand...
Click to collapse
The firmware on Moto's site is ancient... that is your core problem. You are probably on MPH24-49-18-8 or -16, the last -XX is pretty important, you need newer firmware.

Guys there is any chance of volte update because jio expanding their services to next one year
Can it is possible that after nought update it is possible

How can oem unlock leEco le pro 3 x722

Hi guys
I destroyed my leEco le pro 3 x722
After passing the custom rom
Now the device is locked on fastboot only
There is no system and no recovery
The problem I have now is the decryption. If the oem unlock is I can update it. Please help oem unlock
The device does not respond to commands
Everything is written
PS C: \ adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (39337 KB) ...
OKAY [0.895s]
writing 'recovery' ...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.940s
How can oem unlock in another way ????

What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.

sk8223 said:
What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.
Click to expand...
Click to collapse
You installed Batyan's 20s developer ROM
In the past I opened the boot loader but when I tried Rum Miwi did not work
I wanted to go back to the official 26s Rom
Unfortunately everything has lost and the device is ruined
I did not see the warning of testing
How is the solution now

The official 26s ROM locks the bootloader down. If you try to flash anything through it, you'll end up with a bricked device. I'm sorry.
Did you say that you tried to install MIUI? I don't know what "Miwi" is. All I know is, that's something you shouldn't have done.
I'm not sure if you successfully flashed the official 26s ROM or not, and then tried to flash something else... that would cause a brick for sure, AFAIK.
Again, post to the thread about bricked phones that I linked. There are quite a few people with bricks here. Hopefully a solution will present itself soon. Until then, hold onto your phone and hope. :/

sk8223 said:
The official 26s ROM locks the bootloader down. If you try to flash anything through it, you'll end up with a bricked device. I'm sorry.
Did you say that you tried to install MIUI? I don't know what "Miwi" is. All I know is, that's something you shouldn't have done.
I'm not sure if you successfully flashed the official 26s ROM or not, and then tried to flash something else... that would cause a brick for sure, AFAIK.
Again, post to the thread about bricked phones that I linked. There are quite a few people with bricks here. Hopefully a solution will present itself soon. Until then, hold onto your phone and hope. :/
Click to expand...
Click to collapse
Yes, unfortunately, the device is locked
Updated 26s
The manufacturer must find us a solution
Thank you for the kind word

sk8223 said:
What did you try to flash, and on which firmware?
If you tried flashing stock 26s, that locks the bootloader permanently. There really ought to be a sticky about this here. The mods here aren't active at all, which is a shame. And you cannot flash any random ROM you come across, like MIUI. Someone on this forum tried to flash a MIUI ROM and bricked their phone. There is no one-size-fits-all universal ROM that you can flash on every phone... every ROM requires a set of drivers unique to your device, so you need a dev to port specific ROMs to your device. Just clearing that up for anyone who's confused about ROM availability.
What you're supposed to do in order to flash anything at all is to first flash Batyan's 20s developer ROM via stock recovery, unlock the bootloader via Dev options and fastboot, and then flash TWRP and then your ROM. Apparently the vendor ROMs on 20s (from Banggood, Geekbuying, Gearbest, etc.) cannot be unlocked, even though the OEM unlocking option is present in eUI's Developer options.
As for resolving your brick, post to this thread: https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
Hopefully your brick is a soft one that can be resolved without a QFIL file. Because there's no QFIL available for the x722, and it seems to be very difficult to obtain anyway.
Click to expand...
Click to collapse
So your fastboot works just flash the boot loader .
Nice. I finally able to unlock and root. Although I just wished, the first page gets updated with the current method. I have to go through all the pages to fully understand what to do.
So basically a quick roundup:
go in fastboot
flash emmc_appsboot.mbn inside the zip.
reboot
it will ask for a password, just ignore it and reboot back to fastboot
unlock the bootloader
flash twrp
boot into twrp
format phone
then you're done!
Sent from my LEX727 using xda premium

mchlbenner said:
So your fastboot works just flash the boot loader .
Nice. I finally able to unlock and root. Although I just wished, the first page gets updated with the current method. I have to go through all the pages to fully understand what to do.
So basically a quick roundup:
go in fastboot
flash emmc_appsboot.mbn inside the zip.
reboot
it will ask for a password, just ignore it and reboot back to fastboot
unlock the bootloader
flash twrp
boot into twrp
format phone
then you're done!
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Unfortunately I do not know how to scroll
Our Lord is wrong
PS C:\adb> fastboot devices
7b61ab59 fastboot
PS C:\adb> fastboot flash emmc_appsboot.mbn
unknown partition 'emmc_appsboot.mbn'
error: cannot determine image filename for 'emmc_appsboot.mbn'
PS C:\adb> fastboot flash emmc_appsboot.zip
unknown partition 'emmc_appsboot.zip'
error: cannot determine image filename for 'emmc_appsboot.zip'

That file has to be in adb main file.
Sent from my LEX727 using xda premium

mchlbenner said:
That file has to be in adb main file.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
If you have a file please give me the link
Or where I find it

I think you talk about different terminals.
The X722 with 26S strock brick CAN NOT FLASH FOR FASTBOOT.
Greetings.

fastboot flash emmc_appsboot.mbn <- that command is not correct, that's why it errors saying partition not found. The partition to flash is missing, not sure what partition is supposed to be specified, but the command should look like this...... fastboot flash 'thecorrectpartition' emmc_appsboot.mbn

meangreenie said:
fastboot flash emmc_appsboot.mbn <- that command is not correct, that's why it errors saying partition not found. The partition to flash is missing, not sure what partition is supposed to be specified, but the command should look like this...... fastboot flash 'thecorrectpartition' emmc_appsboot.mbn
Click to expand...
Click to collapse
Explain more please
What should i do
Put the file in disk c
Show me this message
PS C:\adb> fastboot flash thecorrectpartition emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'thecorrectpartition' (791 KB)...
OKAY [ 0.034s]
writing 'thecorrectpartition'...

toufik_d said:
Explain more please
What should i do
Put the file in disk c
Show me this message
PS C:\adb> fastboot flash thecorrectpartition emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'thecorrectpartition' (791 KB)...
OKAY [ 0.034s]
writing 'thecorrectpartition'...
Click to expand...
Click to collapse
Your terminal is blocked. It does not have a solution.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
What they say is for x720 and x727 NOT FOR X722.
The command they say is:
fastboot flash aboot emmc_appsboot.mbn
but as I say, it's NOT GOING TO WORK.
Greetings.

how you wiped everything?
do you have recovery?

F.J.V said:
Your terminal is blocked. It does not have a solution.
Read this:
https://forum.xda-developers.com/le...velopment--and-mods/try-unbrick-x722-t3686191
What they say is for x720 and x727 NOT FOR X722.
The command they say is:
fastboot flash aboot emmc_appsboot.mbn
but as I say, it's NOT GOING TO WORK.
Greetings.
Click to expand...
Click to collapse
That command work for me.
Lex 727 21s.
Sent from my LEX727 using xda premium

mchlbenner said:
That command work for me.
Lex 727 21s.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Of course.
That's what I say, for X720 and X727.
For X722 DOES NOT WORK
Greetings.

danielpinto8zz6 said:
how you wiped everything?
do you have recovery?
Click to expand...
Click to collapse
I wanted to restore the official order
The device is running on fastboot only

[HELP] Bricked LG G6 US997, Need help

Hey everyone, I just bricked my LG G6. I was trying to use Uppercut and LGUP to flash a stock firmware, but it wouldn't detect my phone, so i followed this post: https://forum.xda-developers.com/showpost.php?p=70446385&postcount=70
Once I did that and restarted my phone, it got stuck in bootloop and it will display this: "Your device has failed routine safety check and will not boot."
Right now, I can only access fastboot and download mode, but download mode doesn't stick and my PC doesn't detect the phone in download mode, only Fastboot. I can't enter recovery.
Please help guys I don't want my phone to be scrap metal
P.S.: Was running LineageOS prior to bootloop.

Have you tried flashing anything from fastboot?

If you phone has bootloader unlocked then flash twrp via fastboot. If not contact LG for a service
---------- Post added at 07:00 AM ---------- Previous post was at 06:59 AM ----------
Also wiping misc is a very bad idea

boksquare said:
Hey everyone, I just bricked my LG G6. I was trying to use Uppercut and LGUP to flash a stock firmware, but it wouldn't detect my phone, so i followed this post: https://forum.xda-developers.com/showpost.php?p=70446385&postcount=70
Once I did that and restarted my phone, it got stuck in bootloop and it will display this: "Your device has failed routine safety check and will not boot."
Right now, I can only access fastboot and download mode, but download mode doesn't stick and my PC doesn't detect the phone in download mode, only Fastboot. I can't enter recovery.
Please help guys I don't want my phone to be scrap metal
P.S.: Was running LineageOS prior to bootloop.
Click to expand...
Click to collapse
Did you relock the bootloader ?

cory733 said:
Have you tried flashing anything from fastboot?
Click to expand...
Click to collapse
No I have not. Should I? What should I flash thru fastboot?
jimbomodder said:
If you phone has bootloader unlocked then flash twrp via fastboot. If not contact LG for a service
Ok I will try that
---------- Post added at 07:00 AM ---------- Previous post was at 06:59 AM ----------
Also wiping misc is a very bad idea
Click to expand...
Click to collapse
numpea said:
Did you relock the bootloader ?
Click to expand...
Click to collapse
No I did not. Should I? I bricked my HTC One once doing this and I remember locking bootloader would make things harder to fix for me.

Sometimes getting the phone detected in download mode can be tricky, often you will have to play around with different usb cables and / or computers.
I would try flashing TWRP in fastboot. See if you can get into TWRP, then you can try flashing a rom.

cory733 said:
Sometimes getting the phone detected in download mode can be tricky, often you will have to play around with different usb cables and / or computers.
I would try flashing TWRP in fastboot. See if you can get into TWRP, then you can try flashing a rom.
Click to expand...
Click to collapse
I don't really have lots of USB cables or computers at my disposal though.. Do I just keep trying until it works, and even if so, how do I know when the phone is detected in download mode?
I also found out that even though I can enter fastboot, my bootloader is somehow locked again, and I can't flash the unlock bin so I can't even get a custom recovery to be flashed on there. Any other ideas or is my phone dead for good?

New update:
- I entered fastboot and tried flashing TWRP but bootloader is locked. Tried to flash unlock bin but i get this:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.039s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
I'm super desperate at this point. Will LG fix my device if I send it to them? I know warranty is out the window but would they fix it for a payment?

boksquare said:
New update:
- I entered fastboot and tried flashing TWRP but bootloader is locked. Tried to flash unlock bin but i get this:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.039s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
I'm super desperate at this point. Will LG fix my device if I send it to them? I know warranty is out the window but would they fix it for a payment?
Click to expand...
Click to collapse
maybe you locked the bootloader at some point with twrp !
maybe your unlock.bin is corrupted you need either unlock bootloader or try to flash kdz via download mode accessing
if you can't do that, LG center is the only way good luck

Why were you originally trying to flash stock firmware?

cory733 said:
Why were you originally trying to flash stock firmware?
Click to expand...
Click to collapse
I realized the visual appeal of custom OSes no longer attract me as much as full usability (Using google pay or fingerprint in some apps) and stability as I used to when I was young. I wanted to flash stock firmware and just keep root and xposed to enhance my stock experience.

Update 2:
I contacted LG and they quoted me a minimum of $300 and up for repairs.. Really hope someone has a fix to my issue or any other suggestions. I'm thinking about taking to a phone repair store but I doubt they will be able to fix this. I live in Houston, TX area if anybody has store suggestions. Thank you

So what rom were you on? And how did you flash it without TWRP? Can you go through from start to finish exactly what you did?

Revert to stock failed and cannot install custom rom as well.

I was running the June patch version of the TWRP flashable stock builds (had hard bricked my phone before so cannot use full stock firmware until and unless I get my hands on the stock Oreo firmware).
As the official Oreo update is out, (https://drive.google.com/file/d/1ZmtSW40oZi1EXD0PsRib3dqIeF9vauAY/view) I downloaded the zip file and placed it in my internal storage and tried to apply the update, which took me to TWRP, and the update failed. I rebooted to see if everything was ok and it was.
Then, I tried to revert to the stock firmware of the latest edition (to see if I could apply the update) and each time I tried to run the commands or run the flash file, it failed because I was not able to flash the stock recovery. It showed 'N/A' instead of 'bad key' every time on the screen before booting into TWRP.
I wanna get back to full stock! Help guys!

roydhritiman said:
I was running the June patch version of the TWRP flashable stock builds (had hard bricked my phone before so cannot use full stock firmware until and unless I get my hands on the stock Oreo firmware).
As the official Oreo update is out, (https://drive.google.com/file/d/1ZmtSW40oZi1EXD0PsRib3dqIeF9vauAY/view) I downloaded the zip file and placed it in my internal storage and tried to apply the update, which took me to TWRP, and the update failed. I rebooted to see if everything was ok and it was.
Then, I tried to revert to the stock firmware of the latest edition (to see if I could apply the update) and each time I tried to run the commands or run the flash file, it failed because I was not able to flash the stock recovery. It showed 'N/A' instead of 'bad key' every time on the screen before booting into TWRP.
I gave up and tried to go back to the TWRP build I was using before, and I get this error on TWRP. Why is this happening? (I had formatted my data after entering TWRP, is this th reason?)
Please help guys! Need to get my phone back and running!
Here is an image of what's going on -
Click to expand...
Click to collapse
If you're able to get into bootloade,try flashing stock rom without the bootloader,gpt codes so you
Don't lose your bootloader and flash the stock rom.

riyan65 said:
If you're able to get into bootloade,try flashing stock rom without the bootloader,gpt codes so you
Don't lose your bootloader and flash the stock rom.
Click to expand...
Click to collapse
I tried that, no success

riyan65 said:
If you're able to get into bootloade,try flashing stock rom without the bootloader,gpt codes so you
Don't lose your bootloader and flash the stock rom.
Click to expand...
Click to collapse
i tried this and am still getting the same error when im trying to flash the stock recovery:
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.497s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.497s
whats wrong?

roydhritiman said:
i tried this and am still getting the same error when im trying to flash the stock recovery:
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.497s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.497s
whats wrong?
Click to expand...
Click to collapse
Could you post the all errors while you getting in stock rom flash

roydhritiman said:
sending 'recovery' (20580 KB)...
OKAY [ 0.497s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
whats wrong?
Click to expand...
Click to collapse
The error shows clearly that you messed up the partition table (GPT).

nicolap8 said:
The error shows clearly that you messed up the partition table (GPT).
Click to expand...
Click to collapse
I think the problem is, since I was hardbricked, I needed to use blankflash to revive my bootloader. There was no proper working blankflash for the g5 plus last year, so had to use the Albus blankflash to revive the bootloader. Is that the reason why I can't flash the stock ROM? If yes, could you tell me how to get back to the g5 plus' native bootloader via its own blankflash?

roydhritiman said:
I think the problem is, since I was hardbricked, I needed to use blankflash to revive my bootloader. There was no proper working blankflash for the g5 plus last year, so had to use the Albus blankflash to revive the bootloader. Is that the reason why I can't flash the stock ROM? If yes, could you tell me how to get back to the g5 plus' native bootloader via its own blankflash?
Click to expand...
Click to collapse
By using mmcblk0 file I think we can get original bootloader of Moto g5 plus

riyan65 said:
By using mmcblk0 file I think we can get original bootloader of Moto g5 plus
Click to expand...
Click to collapse
Can you guide me with that process?

roydhritiman said:
Can you guide me with that process?
Click to expand...
Click to collapse
Here it is https://forum.xda-developers.com/moto-g5s/how-to/guide-how-to-create-mmcblk0-img-device-t3803176

riyan65 said:
Here it is https://forum.xda-developers.com/moto-g5s/how-to/guide-how-to-create-mmcblk0-img-device-t3803176
Click to expand...
Click to collapse
I'm somewhat of a noob, so could you explain what exactly does this process do?

roydhritiman said:
I'm somewhat of a noob, so could you explain what exactly does this process do?
Click to expand...
Click to collapse
You need a memory card of about your device storage or more than that. And a working device of same model. The mmcblk0 file is used as temporary bootloader of Moto g5 plus until you flash your original bootloader, the mmcblk0 file need to store in Memory card with image type so it can be used as temporary bootloader. After you get the Moto g5 plus bootloader in your device you don't need to have memory card you can use it as regular. This mmcblk0 method is used to recover a hard bricked device by flashing temporary bootloader on it and after flashing stock rom it can used normally.
---------- Post added at 05:29 PM ---------- Previous post was at 05:27 PM ----------
You can ask someone to put mmcblk0 file on XDA so you get your original bootloader.

riyan65 said:
You need a memory card of about your device storage or more than that. And a working device of same model. The mmcblk0 file is used as temporary bootloader of Moto g5 plus until you flash your original bootloader, the mmcblk0 file need to store in Memory card with image type so it can be used as temporary bootloader. After you get the Moto g5 plus bootloader in your device you don't need to have memory card you can use it as regular. This mmcblk0 method is used to recover a hard bricked device by flashing temporary bootloader on it and after flashing stock rom it can used normally.
---------- Post added at 05:29 PM ---------- Previous post was at 05:27 PM ----------
You can ask someone to put mmcblk0 file on XDA so you get your original bootloader.
Click to expand...
Click to collapse
No , no and no! You told a lot of incorrect statement.
The SD card MUST be bigger than your phone internal memory.
You are copying the ENTIRE internal memory of a phone to the SD card then copy back to your phone rewriting ALL. Not only the bootloader. Also the foundamental partitions that are unique to every phone. Read the 3d on 0 IMEI here in this forum for a good explanation.

nicolap8 said:
No , no and no! You told a lot of incorrect statement.
The SD card MUST be bigger than your phone internal memory.
You are copying the ENTIRE internal memory of a phone to the SD card then copy back to your phone rewriting ALL. Not only the bootloader. Also the foundamental partitions that are unique to every phone. Read the 3d on 0 IMEI here in this forum for a good explanation.
Click to expand...
Click to collapse
I have saw many people are using 32gb memory card for 32 gb of internal storage, so I have said that and once we get bootloader we are going to remove the memory card so we can install stock rom. IMEI lost is a small problem in front of a hard brick device as imei lost problem also have been solved.

riyan65 said:
I have saw many people are using 32gb memory card for 32 gb of internal storage, so I have said that and once we get bootloader we are going to remove the memory card so we can install stock rom. IMEI lost is a small problem in front of a hard brick device as imei lost problem also have been solved.
Click to expand...
Click to collapse
Many people write only to move digits...
If the free space of the SD card is less than the size of internal memory the procedure will abort.
IMEI lost still a problem, read better!
In some state using an IMEI duplicated is punible by law...

Bootloop redmi 7a vendor.img cant flash

so im trying this since yesterday
Please help me ive been trying to find solution everything flashes except when i try flashing vendor.img it says vendor error : buffer overreads occured due to invalid sparse header how can i fix this my device is redmi7A with unlocked bootloader using original cable on usb2 slot trying to unbrick it since yesterday using latest flashtool and drivers using this firmware eu version Xiaomi_Redmi_7A_V11.0.3.0.QCMEUXM_20200728.0000.00_EEA_10_XFT also would like to mention i unlocked bootloader installed twrp and formated all partitions (brave man i am) tryed using the default firmware upgrade tool also tryed manually installing vendor.img from the firmware but no success tryed formating the partition under twrp to ext2 and returned it to ext4 didnt try to change the size or anything ....this all because the default firmware couldnt install game me vendor error ... at this point im giving up on it ... if anyone knows what must be done hes welcome :fingers-crossed:
here is the msg :
fastboot flash vendor vendor.img
target reported max download size of 535821312 bytes
sending 'vendor' (290176 KB)...
OKAY [ 9.152s]
writing 'vendor'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 12.419s

....last time i ever buy a chinese device from 5-6 different firmwares i could test only 2 because the others didnt have all the files required in the images folder .....chinese piece of trash and thats it...no way of restoring my device even with the default firmware i still cannot understand did i do something wrong or what......

What says when you tried to flash the vendor with twrp?

first check if you using the newest fastboot version via: fastboot --version
are u sure that you have the EEA Hardware?
when u have access to twrp(recovery) try sideload via adb sideload
and here is a how to flash manually link:
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
How to flash a factory image | Return to stock | Unroot your Nexus 5 Hello Nexus 5 Users! I see many users that don't know how to restore their Nexus 5 to stock. It may come in handy, either when you want to RMA your phone, or you want to...
forum.xda-developers.com
plstanchev said:
....last time i ever buy a chinese device .....chinese piece of trash and thats it...
Click to expand...
Click to collapse
this could happen to you with any device! for me the 7A is a really great device. if you unlocked your bootloader you know that there is always a chance to brick your phone! so take responsibility for your actions and don't blame the manufacturer.
PS: if you use more dots and enter it would be much more better to read through your post if someone is trying to help :/
I am also not responsible if anything goes wrong.

May be your download file is corrupted, have you checked the integrity of that file, the extension (.tgz) fastboot firmware.
And flash them with mitool and always download from official site.