Database Info

bricked? please help

i received an OTA update on friday, i installed it and after it was completed it restarted and now just shows the bootup screen and restarts over and over. i could access recovery but nothing helped eg clearing catche etc so i downloaded Retail Europe (1GB) - XT1541_OSPREY_RETEU_6.0_MPI24.65-33.1_cid7 and followed theses steps
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
every step says it passed ok but when it restarts its still stuck on boot loop the only difference now is if i try to enter recovery it just restarts and again just keeps rebooting.
ive got an aftermarket screen dont know if that makes a difference as ive read apple are bricking phones that havnt been repaired by them selves.
please help im stuck for ideas now

also my bootlocker is locked and cant be unlocked.
just noticed that even though it all pass`s ok my software is staying the same and not updating, ive tried it at least 20 times and on different machines. also tried rsd lite and that also says completed but no change in software
the sotfware listed in the bootloader is, m8919_2020613.22.03.21.29r osprey_emea
and the one im tryig to update to is, m8916_2020629.41.03.21.51r osprey-reteu

bower123456 said:
also my bootlocker is locked and cant be unlocked.
just noticed that even though it all pass`s ok my software is staying the same and not updating, ive tried it at least 20 times and on different machines. also tried rsd lite and that also says completed but no change in software
the sotfware listed in the bootloader is, m8919_2020613.22.03.21.29r osprey_emea
and the one im tryig to update to is, m8916_2020629.41.03.21.51r osprey-reteu
Click to expand...
Click to collapse
Same problem with my Moto 2015 after OTA update, i tryed everything and nothing... =/ boot locked, stock recovery. My baseband M8919_2020613.22.03.21.29R osprey_emea
Tomorrow i will send my moto for Motorola.

wish i could but ive got a replacement screen so they wont touch it so looks like bin for mine

Nothing to do pretty much, same happened to me and there's no fix for that

I think the problem it's the Stock ROM we try flash, because the software version it's different.
I try flash with this ROM [XT1541_OSPREY_RETEU_6.0_MPI24.65-33.1_cid7_subsidy-DEFAULT_CFC__v2.xml], and i could flashing all files without errors, but still looping on motorola logo.
<software_version version="osprey_reteu-user 6.0 MPI24.65-33.1 1 release-keysM8916_2020629.41.03.21.51R"/>
M8919_2020613.22.03.21.29R osprey_emea - Original

if you manage to sort it please let me know

[HELP] XT1563 Bricked after trying to root it

After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
My bootloader is locked, so I tried to unlock it following the Motorola's guide. Got my device ID via fastboot, copy and paste on their site and requested the unlock key.
Then again, when I use "fastboot oem unlock CODE"
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
The problem is that I can't pass trough flash mode screen.
I've been reading some threads over here, and one guy which had his bootloader locked on XT1563 tried to flash the Canadian firmware and didn't get any error, then he was able to fully unlock his bootloader and after this he was able to flash the Brazilian firmware.
I didn't try to flash the Canadian firmware yet. How risky is this? There is another way to unlock the bootloader?

If you flash the right firmware for a locked phone (model and version), it won't give the prevalidation error. Then it can boot again and you can turn on the OEM unlock, and unlock the bootloader.
Try to use the right firmware for your phone.

TImMaia said:
After tried to root my device without the assist of PC (only using apk), my device only starts on AP Fastboot Flash Mode (Secure).
I downloaded the brazilian firmware, tried to flash it but I can't.
Was getting this ERROR: "(bootloader) Preflash validation failed".
Click to expand...
Click to collapse
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?

MrTooPhone said:
I don't believe it is possible to root without first unlocking your bootloader (which will factory reset your device). What apk were you attempting to install?
Click to expand...
Click to collapse
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:

TImMaia said:
I'm a real noob at this issue. I tried to root with Kingroot. I took the device to the Motorola Tech Support in my city yesterday afternoon and it is ready to pick up.
Thank you guys for helping me :good::good::good:
Click to expand...
Click to collapse
If you really want to root, you need to follow these instructions. Although you can use the latest version of TWRP, do not use any other version of Supersu except v2.62-3. Any other methods will most likely soft brick your phone.

Boys, is not difficult, not just fiddling around to fix it.
Motorola install drivers
Install ADB and fastboot
Looking for your stock rom here: " github dot com dash motoxplay dash stock dash releases " for example.
Saddled with fastboot Tooda the rom (eye, if downloaded from out there commands, you may be wanting to them upload any image rom, this drove me crazy to me all one day until I realized I was missing two sparsechunk).
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
On the subject battery, the XT1563 charge the batt when it is in this mode, we just have to leave it connected to the charger and is loading very slowly.
On the bootloader issue, I have LOCK, and may do so without problems because they look the same version of rom that he had.
About not having DEPURACION USB, I did not have it on, and yet I could do it.
My stay in Fastboot mode I when installing the app Kingroot, and turned off the phone and start no more.
In this way it is solved, 100% sure I did not do myself. Do not try other methods like TWRP or things like that because with locked bootloader will hit the wall every time.
Anyone who needs a hand, ask or send mail.
Sorry if he had been resolved, but it was a big achievement for me, so I leave the info. I cost a lot to buy the cell phone and had ****ed the other day.
Regards!
(Sorry, its googletranslated, im from argentina)

Yeah, what ever @jonatandirocca1 said is right
i also once faced the problem of missing sparse file but after flashing every file you can make your Phone revoke
if you want to install STOCK FIRMWARE , you dont need to unlock bootloader, you just need your phone detected in ADB

Phone doesn't charge or connect to computer

This started happening since today morning. The phone doesn't charge or get detected when connecting to a computer.
I tried wiping everything and clean installing different roms and kernels, but nothing helped.
For some reason, the phone is charging when in the Bootloader screen though. What should I do?

Windows 10? Install this

Huh?
Let me clarify, it was working properly until last night, and I have Windows 10.
I'm currently forced to charge using the bootloader screen as the phone refuses to charge otherwise - not while fully switched off, and also not when switched on.
The computer and the phone don't even detect that anything is connected when I plug in the USB. (The cable is okay, I'm using the same cable to charge my phone on the bootloader screen)

Wait... It charges in the bootloader (or while off I assume) but not when booted into the OS? Is this device stock? What have you tried, wipe cache, factory reset, etc?
Sent from my MotoG3 using Tapatalk

acejavelin said:
Wait... It charges in the bootloader (or while off I assume) but not when booted into the OS? Is this device stock? What have you tried, wipe cache, factory reset, etc?
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
No it's not stock.
I've tried everything. Full wipe and flashed various roms and kernels. No avail. :/

Check for lint build up in the plug on the phone and try a different cable... I know it sounds wrong but once the phone is booted it does some simple communication to the source, that may not be working.
Sent from my MotoG3 using Tapatalk

I forgot to mention something.
The battery icon in the notification bar is permanently stuck showing charging even though the phone actually isn't being charged (and the battery screen in Settings also show 'Not charging').

acejavelin said:
Check for lint build up in the plug on the phone and try a different cable... I know it sounds wrong but once the phone is booted it does some simple communication to the source, that may not be working.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
This didn't work, sorry.
So, it only seems to charge when connected the PC in bootloader mode. It doesn't charge otherwise - not with any charger, and not while being switched on. wth.

Nvm, I'll try removing the lint.

FalKoopa said:
No it's not stock.
I've tried everything. Full wipe and flashed various roms and kernels. No avail. :/
Click to expand...
Click to collapse
Did you try to install stock rom or only custom roms?

Acetyloaceton said:
Did you try to install stock rom or only custom roms?
Click to expand...
Click to collapse
Only custom roms. I'm admittedly a bit scared to try installing the stock rom as it might get bricked.
EDIT: Btw, cleaning it didn't work. I suppose I have no option but to give it for repairs.

If I were you, I would try to do this. Dont be scared. If you have the newest marshmallow partition and bootloader then flash factory images without these two. You can also skip logo if you want to keep disabled unlocked bootloader information.
fastboot oem fb_mode_set
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Wait 5-10 minutes and done

Acetyloaceton said:
If I were you, I would try to do this. Dont be scared. If you have the newest marshmallow partition and bootloader then flash factory images without these two. You can also skip logo if you want to keep disabled unlocked bootloader information.
fastboot oem fb_mode_set
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Wait 5-10 minutes and done
Click to expand...
Click to collapse
Where will I get these files?

Here you go

And if I remember correctly you have an xt1550 right? I have flashed factory image of 6.0.1 with no problems on my xt1550, just to assure.
Check in device manager & devices and printers, if something pops up when phone is connected in bootloader mode. If a device with yellow triangle shows up, you can install drivers (pointing to driver inf file) to and subsequently fastboot flash stock.
Broadcasted from Zeta Reticuli

I think if you flash partition and bootloader then it also should work. Brick issue only appears when you are trying to do downgrade from marshmallow to lollipop and you flash older partition (you should always have the newest one).

Gravemind2015 said:
And if I remember correctly you have an xt1550 right? I have flashed factory image of 6.0.1 with no problems on my xt1550, just to assure.
Check in device manager & devices and printers, if something pops up when phone is connected in bootloader mode. If a device with yellow triangle shows up, you can install drivers (pointing to driver inf file) to and subsequently fastboot flash stock.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Alright. I'm going to flash it then. Downloading it will take a while...
I don't remember ever updating the bootloader though..

@Acetyloaceton
So, I tried to flash the stock recovery.img
I got this.....
target reported max download size of 268435456 bytes
sending 'stock' (16484 KB)...
OKAY [ 0.571s]
writing 'stock'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.598s

Nevermind, I managed to flash everything and all went well, but now the phone is in a bootloop between bootloader unlocked screen and the Erasing screen.

FalKoopa said:
Nevermind, I managed to flash everything and all went well, but now the phone is in a bootloop between bootloader unlocked screen and the Erasing screen.
Click to expand...
Click to collapse
Have you tried factory resetting via stock recovery? I mean power off>power+vol. Down>bootloader>recovery. If still can't boot then after factory resetting try flashing firmware again.
Broadcasted from Zeta Reticuli

Cannot flash firmware.... And network issue

Recently I rooted my phone and flash the resurrection remix naught in moto g3 xt1550....
For some reason I start to flash firmware ROM .....but it is not flashing.... Shows " preflash validation failed " and on system image " invalid image" .......... I tried many times but it didn't flash......when I skip the partition gpt file then every image file start flashing and phone start..,..
But their is no network......
After that whenever I switch off or reboot or go to recovery rather than that it start boot loader....
Then I flashed the resurrection remix again..... When I press reboot after flashing then it goes to boot loader......
At boot loader I press power on then it start booting and there is no network in this ROM too......
What can I do now ...... Please help.........

To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.

yes U will get the error of "preflash validation failed" cause of the security update which motorola released for the month of October, January and recent April.... Do one thing again flash the appropriate stock rom according to ur mobile But skip these two steps/Files >>> 1) fastboot flash partition gpt.bin and 2) fastboot flash bootloader bootloader.img and enter the remaining command/or follow the whole procedure but skip these two file mentioned above U will succed:fingers-crossed::good:
For ur simplicity im providing u commands and plz CHECK UR SPARSECHUNK Files it varies according to mobile I have 7 thats y 7 sparsechunk files DO CHECK URs ok>>>>
fastboot oem fb_mode_set
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Do it ur own risk Im not responsible for any damage :laugh:

everything went well except my network .........i checked in about phone < status < imei no is " 0 ".......how to restore that...........i think thats why the network isn't showing.......................

acejavelin said:
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
Click to expand...
Click to collapse
where I find radio stack...... I don't know........and I didn't flash the stock images correctly because I have to skip the partition gpt and bootloader......
give me something else to solve it......
btw thanks sir......:good:

heisenberg1546 said:
where I find radio stack...... I don't know........and I didn't flash the stock images correctly because I have to skip the partition gpt and bootloader......
give me something else to solve it......
btw thanks sir......:good:
Click to expand...
Click to collapse
The "radio stack" is the relevant radio portions of the firmware image...
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.

acejavelin said:
The "radio stack" is the relevant radio portions of the firmware image...
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
Click to expand...
Click to collapse
isn't working sir........
I did without copy paste.........
boot img command gives preflash validation failed....

heisenberg1546 said:
It is not uncommon that they don't take the first time, repeat it and the boot.img command. Verify EVERY command returns an OKAY response, if not, repeat it.
And do not copy and paste the commands all at once, type them out and look at the response, or at least copy and paste each command individually.
isn't working sir........
I did without copy paste.........
boot img command gives preflash validation failed....
Click to expand...
Click to collapse
You didn't do the boot.img... but Might want to look at the IMEI 0 recovery thread... I don't have any more ideas.

acejavelin said:
You didn't do the boot.img... but Might want to look at the IMEI 0 recovery thread... I don't have any more ideas.
Click to expand...
Click to collapse
After those commands ...... I flash again all img's including the boot.img......
How to restore the imei file ..... Like in mediatek device ,,, we can write by sn tools .....

heisenberg1546 said:
After those commands ...... I flash again all img's including the boot.img......
How to restore the imei file ..... Like in mediatek device ,,, we can write by sn tools .....
Click to expand...
Click to collapse
I don't know... There is a thread here specifically about it, you will have to look there.

I want to keep the custom rom (RR-O-v6.0.0-20180511-ospreyl) with all networks
acejavelin said:
To clear the Fastboot mode, in fastboot enter "fastboot oem fb_mode_clear" and after that it should start the OS without going into fastboot each time.
The fact this is happening leads me to believe your other problem is related... meaning you didn't flash the stock images properly. If you have no network then you need to reflash the radio stack and boot.img file, they must match and you have to erase the modemstX partitions for the radios to work properly.
Click to expand...
Click to collapse
Hey, I have installed RR-O-v6.0.0-20180511-osprey on Moto G(3rd Generation), and now the error is: "No sim Detected ", IMEI number is fine. I want to flash radio firmware in this custom Rom. Will flashing radio stack of stock rom 6.0.1 (Moto G3 x1550) work?
adb reboot bootloader
fastboot flash modem NON-HLOS.bin (That must of Moto G3?)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash boot boot.img (Is it to be of RR or of Moto?)
fastboot reboot
Is there any other option or solution then please mention.

You need to flash stock firmware first then your network problem solved then you can install custom roms?
Good Luck!

Moto g8 plus failed to identify current slot

hi, name's Josh, i was trying to downgrade my moto g8 plus, but i had this issue with "please lock bootloader" loop so i tried locking it, but now i cannot even pass from bootloader:
"no booteable A/B slot
failed to boot linux, falling back to fastboot
fastboot reason: Fall-through from normal boot mode"
i've tried to fix it with the rescue and smart assistant but it keeps failing, i also tried flashing it with fastboot but i get the message "failed to identify current slot", when i try to "--set-active=a" it shows (either for b):
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.172s
And when i type "fastboot getvar current-slot" i get this:
current-slot:
finished. total time: 0.064s
I don't really know what to do now, even recovery mode won't prompt, it just restarts bootloader, does anyone have a solution for this? i never had this kind of issue with samsung devices, this is my first motorola and since i bought it i had problems with touch being laggy so i was trying to downgrade android 10 to 9 but i was unable, and now i can't even use it at all, i would really apreciate if somebody could help me, in advance thanks for your time and attention

Can you unlock the bootloader again?

gfrank227 said:
Can you unlock the bootloader again?
Click to expand...
Click to collapse
when i try "fastboot oem unlock" it just says:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.190s

darkhonor said:
when i try "fastboot oem unlock" it just says:
...
(bootloader) Check 'OEM unlocking' in Android Settings > Developer
(bootloader) Options
FAILED (remote failure)
finished. total time: 0.190s
Click to expand...
Click to collapse
If you're really desperate, you can try this. I can't vouch for its success rate. Be careful.
Moto G8+ Fix/Repair Hard Brick Tutorial
hello everyone i hard bricked my moto g8 plus the other day it was totally dead it couldnt power on there was no sound no vibration my pc couldnt recognise it when connected with usb cable, But i managed to fix it and get it working again the...
forum.xda-developers.com

gfrank227 said:
If you're really desperate, you can try this. I can't vouch for its success rate. Be careful.
Moto G8+ Fix/Repair Hard Brick Tutorial
hello everyone i hard bricked my moto g8 plus the other day it was totally dead it couldnt power on there was no sound no vibration my pc couldnt recognise it when connected with usb cable, But i managed to fix it and get it working again the...
forum.xda-developers.com
Click to expand...
Click to collapse
Since you are able to get into fastboot, perhaps you should start with a blankflash from lolinet and do not take your phone apart quite yet.

When you say you tried to downgrade did you flash the previous version bootloader and partition table? You should never do that, but it sounds like you need to try and flash a blankflash like mentioned above.
One other thing you can try to do, although I doubt it would work since it can't determine the active slot is download the firmware from lolinet then fastboot boot boot.img to try and boot the kernel, which will boot the system. If that does work then you can go into dev settings and check the allow bootloader unlock option.

gfrank227 said:
Since you are able to get into fastboot, perhaps you should start with a blankflash from lolinet and do not take your phone apart quite yet.
Click to expand...
Click to collapse
ok so i tried to blankflash it but i got this error i guess is time to say goodbye jajaj
Motorola qboot utility version 3.86
[ -0.000] Opening device: \\.\COM7
[ 0.005] Detecting device
[ 34.666] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 34.666] Check qboot_log.txt for more details
[ 34.666] Total time: 34.668s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error

CodyF86 said:
When you say you tried to downgrade did you flash the previous version bootloader and partition table? You should never do that, but it sounds like you need to try and flash a blankflash like mentioned above.
One other thing you can try to do, although I doubt it would work since it can't determine the active slot is download the firmware from lolinet then fastboot boot boot.img to try and boot the kernel, which will boot the system. If that does work then you can go into dev settings and check the allow bootloader unlock option.
Click to expand...
Click to collapse
well im uncertain of how that is made, i just followed up a tutorial , downloaded official firmware and flashed it with fastboot comands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
and yeah i tried flashing the newest official firmware that rescue and smart assistant showed, but since i cannot determine slot it says "failed to identify current slot"

Yeah it looks like that would have flashed the previous version of androids parttition table for that device from the commands you ran and that's usually a rip.

CodyF86 said:
Yeah it looks like that would have flashed the previous version of androids parttition table for that device from the commands you ran and that's usually a rip.
Click to expand...
Click to collapse
So there's no other way to fix it?