Database Develop

Remake the phone warranty valid?

Hello guys,
Today when I tried to plug my headphones to listen to music, I noticed that the pone hardly recognises them. First I thought it was problem of the headphones but I tried to plug another and I almost must keep my finger pressing the cable where is plugged
So I think is problem of the headphone jack.
I have the bootloader unlocked so the warranty is void. I want to know if there is any method to lock it again to re valid the warranty
Sent from my XT890 using xda premium

Aljecama12 said:
Hello guys,
Today when I tried to plug my headphones to listen to music, I noticed that the pone hardly recognises them. First I thought it was problem of the headphones but I tried to plug another and I almost must keep my finger pressing the cable where is plugged
So I think is problem of the headphone jack.
I have the bootloader unlocked so the warranty is void. I want to know if there is any method to lock it again to re valid the warranty
Sent from my XT890 using xda premium
Click to expand...
Click to collapse
It´s hard because when you did the Bootloader Unlock procedure on Motorola website you gave to them your IMEI, so theorically if you send the phone to repair it will be rejected.
But I don´t. Here on Brazil a lot of users had general problems with Razr i, sended the phone with BL unlocked to the technical support and got a new one... So I don´t know, it deppends of how stuff works with Motorola in your country..
The command "fastboot oem lock", or something else, doesn´t work as other phones. So the bootloader is not lockable again via PC...

WendelSchelhan said:
It´s hard because when you did the Bootloader Unlock procedure on Motorola website you gave to them your IMEI, so theorically if you send the phone to repair it will be rejected.
But I don´t. Here on Brazil a lot of users had general problems with Razr i, sended the phone with BL unlocked to the technical support and got a new one... So I don´t know, it deppends of how stuff works with Motorola in your country..
The command "fastboot oem lock", or something else, doesn´t work as other phones. So the bootloader is not lockable again via PC...
Click to expand...
Click to collapse
the command fastboot oem lock works, but two things:
The warranty is still void, because you require the code in the motorola website
The BL still show the "WARNING BOOTLOADER UNLOCKED" message
So if you want to lock the bootloader and don't want the "WARNING BOOTLOADER (...)" message follow this commands, This will delete your /data & /cache partition, and you need flash motorola signed files (firmware):
cd (firmware folder)
fastboot oem lock begin
fastboot flash boot boot_signed
fastboot flash bos bos_signed
fastboot flash cdrom cdrom_signed
fastboot flash gpt gpt_signed
fastboot flash motoboot motoboot
fastboot flash radio radio_signed
fastboot flash recovery recovery_signed
fastboot flash system system_signed
fastboot flash ulogo ulogo_signed
fastboot erase userdata
fastboot erase cache
fastboot oem lock
the first command will start the lock and wait for signed partitions, all the fastboot flash (...) commands will flash ALL the partitions signed's; the fastboot flash ulogo_logo will remove the "WARNING BOOTLOADER UNLOCKED" message; "fastboot erase (...)" will wipe the data partitions (required); Fastboot oem lock finalizes the bootloader lock process

Boss442 said:
the command fastboot oem lock works, but two things:
The warranty is still void, because you require the code in the motorola website
The BL still show the "WARNING BOOTLOADER UNLOCKED" message
So if you want to lock the bootloader and don't want the "WARNING BOOTLOADER (...)" message follow this commands, This will delete your /data & /cache partition, and you need flash motorola signed files (firmware):
cd (firmware folder)
fastboot oem lock begin
fastboot flash boot boot_signed
fastboot flash bos bos_signed
fastboot flash cdrom cdrom_signed
fastboot flash gpt gpt_signed
fastboot flash motoboot motoboot
fastboot flash radio radio_signed
fastboot flash recovery recovery_signed
fastboot flash system system_signed
fastboot flash ulogo ulogo_signed
fastboot erase userdata
fastboot erase cache
fastboot oem lock
the first command will start the lock and wait for signed partitions, all the fastboot flash (...) commands will flash ALL the partitions signed's; the fastboot flash ulogo_logo will remove the "WARNING BOOTLOADER UNLOCKED" message; "fastboot erase (...)" will wipe the data partitions (required); Fastboot oem lock finalizes the bootloader lock process
Click to expand...
Click to collapse
I didn´t knew about this. Stills impossible to remove WARNING BOOTLOADER UNLOCKED message on unlocked devices using this "fastboot flash ulogo ulogo_signed" command?

WendelSchelhan said:
I didn´t knew about this. Stills impossible to remove WARNING BOOTLOADER UNLOCKED message on unlocked devices using this "fastboot flash ulogo ulogo_signed" command?
Click to expand...
Click to collapse
No, Only fastboot flash ulogo logo_signed.
If you flash ulogo file still show warning bl unlocked, but if you do in fastboot "fastboot oem lock" they said: [FAIL] Already locked :silly: maybe motorola don't want the users relock the bootloader

Is our phone water resistant? Not submersions Because I had a problem when it was raining is that the problem? Does Motorola warranty covers this?
Sent from my XT890 using xda premium

Would do the same procedure on the Motorola Razr HD? In firmware does not have the files "bos_signed, gpt_signed, motoboot and radio_signed" if any can help, I really need. Grateful.

USB Drivers

Back Story:
I cracked the screen on my Moto X a few days ago and just received my insurance replacement. Before I send the old one back I want to return it to stock. I am attempting to do so using RSD Lite and the FXZ from the the Android Development section.
My problem is that the usb drivers are not installing correctly! I downloaded the device manager, and when my phone connects and Windows says it is installing driver software it returns this error. (see attached)
As a result, I cannot get the phone to be recognized by RSD Lite, therefore not being able to return to stock.
PLEASE HELP!

Troubleshooting up to this point:
-Uninstalled and reinstalled drivers
-rebooted computer
-rebooted phone
-tried different usb ports
-tried new phone
In case I cannot resolve this issue, is there another way to return to stock? I really don't think Asurion will like me very much when they try to factory reset this phone and nothing happens

jmcharles said:
Back Story:
I cracked the screen on my Moto X a few days ago and just received my insurance replacement. Before I send the old one back I want to return it to stock. I am attempting to do so using RSD Lite and the FXZ from the the Android Development section.
My problem is that the usb drivers are not installing correctly! I downloaded the device manager, and when my phone connects and Windows says it is installing driver software it returns this error. (see attached)
As a result, I cannot get the phone to be recognized by RSD Lite, therefore not being able to return to stock.
PLEASE HELP!
Click to expand...
Click to collapse
I had this issue too. Simply boot into the bootloader and choose BP Tools. Your computer should recognize it now. Also, make sure you have USB Debugging checked in developer options in the phone settings. If you are running Windows 8 you may run into issues running RSD Lite. If that is the case you can use fastboot to flash back to stock. Simply unzip the FXZ and place the fastboot files in the same folder. Then boot your phone into the bootloader. and connect your phone. Run the following commands:
cd C:\<the directory your files are in>
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin (optional: this is the boot logo)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
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 (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem config carrier <carrier name>
fastboot oem fb_mode_clear
fastboot reboot
That should reset your phone. You may want to double check the oem commands against the ones listed in the xml file in the zip. I have the AT&T version and that's what I'm basing it off of.
EDIT:
You can also just flash the recovery partition and factory reset that way. However, it might not erase any root files. I've done some factory resets on other devices and maintained root.
EDIT 2:
I attached the fastboot files in case you needed them.
EDIT 3:
Just though of this. Make sure when you run RSD Lite that your phone is booted into the bootloader.

Thank you!
So...I tried to get it recognized using the Motorola drivers, but it just was not working. Instead, I attempted to update the drivers manually to Android ADB interface while in the bootloader. This worked, and my device was recognized. However, RSD Lite still failed to work, so I did it manually thru command prompt. I double checked all the commands with the Verizon XML file, and it worked!
Thank you for giving such an exhaustive reply. I am still unable to get the phone recognized with Motorola drivers, but the Android ADB drivers I already had on my computer seem to work. I'm not too smart on that stuff, so maybe someone can explain why this is and why I was able to get it to work.

jmcharles said:
So...I tried to get it recognized using the Motorola drivers, but it just was not working. Instead, I attempted to update the drivers manually to Android ADB interface while in the bootloader. This worked, and my device was recognized. However, RSD Lite still failed to work, so I did it manually thru command prompt. I double checked all the commands with the Verizon XML file, and it worked!
Thank you for giving such an exhaustive reply. I am still unable to get the phone recognized with Motorola drivers, but the Android ADB drivers I already had on my computer seem to work. I'm not too smart on that stuff, so maybe someone can explain why this is and why I was able to get it to work.
Click to expand...
Click to collapse
Glad to hear you were able to get your phone back to stock. I haven't figured out why it does that either. Never had that issue with my other phones and they were Motos too.
Sent from my XT1058 using XDA Premium 4 mobile app

File Error
Dark9781 said:
I had this issue too. Simply boot into the bootloader and choose BP Tools. Your computer should recognize it now. Also, make sure you have USB Debugging checked in developer options in the phone settings. If you are running Windows 8 you may run into issues running RSD Lite. If that is the case you can use fastboot to flash back to stock. Simply unzip the FXZ and place the fastboot files in the same folder. Then boot your phone into the bootloader. and connect your phone. Run the following commands:
cd C:\<the directory your files are in>
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin (optional: this is the boot logo)
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
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 (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem config carrier <carrier name>
fastboot oem fb_mode_clear
fastboot reboot
That should reset your phone. You may want to double check the oem commands against the ones listed in the xml file in the zip. I have the AT&T version and that's what I'm basing it off of.
EDIT:
You can also just flash the recovery partition and factory reset that way. However, it might not erase any root files. I've done some factory resets on other devices and maintained root.
EDIT 2:
I attached the fastboot files in case you needed them.
EDIT 3:
Just though of this. Make sure when you run RSD Lite that your phone is booted into the bootloader.
Click to expand...
Click to collapse
I'm very new to this. I got caught up in the PwnMyMoto boot loop after the Verizon OTA. I am trying to reload the phone back to Factory Default without root. When I try to use the commands above I get the error "Variable not supported! target reported max download size of 805306368 bytes
I have the files in the same directory as fastboot.exe so they are in the path. Can anyone tell me why I am getting this error, and what I can do to resolve it? Thanks

How to get back to Android 8.1 from Android 9?

Hello, please help me with the following.
My Moto X4 (XT1900-7) recently got the Android 9 (Pie) update. Since then I have problems with wifi and it's always dropping. Because of that I reset the phone, but now I can't even log into Play Store, because wifi keeps dropping all the time. I can't use the phone at all. Every guide I've tried getting back Android 8.1 back didn't work so far. Maybe the guides were **** or I simply didn't understand them. Also, my recovery mode doesn't even start.
I've downloaded "PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml". Would that be the correct version to install?
Please help.
Thanks in advance.

curious45 said:
Hello, please help me with the following.
My Moto X4 (XT1900-7) recently got the Android 9 (Pie) update. Since then I have problems with wifi and it's always dropping. Because of that I reset the phone, but now I can't even log into Play Store, because wifi keeps dropping all the time. I can't use the phone at all. Every guide I've tried getting back Android 8.1 back didn't work so far. Maybe the guides were **** or I simply didn't understand them. Also, my recovery mode doesn't even start.
I've downloaded "PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml". Would that be the correct version to install?
Please help.
Thanks in advance.
Click to expand...
Click to collapse
This one:
PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
but two things:
1) Your bootloader needs to be unlocked. If you have a locked bootloader and try to go 9 -> 8.1 you are bootlooped.
2) You will still get prompts to upgrade to Android 9. You can ignore them but they won't ever go away.

Yeah, I first need to unlock the bootloader, but that's where the problems start. I found a guide on motorola web page: motorola-global-portal[.]custhelp[.com]/app/standalone/bootloader/unlock-your-device-b
I've downloaded Android SDK (1 GB??!) and installed it. Then I've installed Motorola Device Manager. I've set my X4 to Fastboot Mode. The next step "On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)" I don't even understand. How do I "go to the directory", and what's my "$PATH"? That guide is as bad as it gets. I doesn't explain anything.
Edit: I've tried it through minimal adb fastboot command and could get my unlock-key. let's see how it goes from now on.
Thanks so far.

curious45 said:
Yeah, I first need to unlock the bootloader, but that's where the problems start. I found a guide on motorola web page: motorola-global-portal[.]custhelp[.com]/app/standalone/bootloader/unlock-your-device-b
I've downloaded Android SDK (1 GB??!) and installed it. Then I've installed Motorola Device Manager. I've set my X4 to Fastboot Mode. The next step "On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)" I don't even understand. How do I "go to the directory", and what's my "$PATH"? That guide is as bad as it gets. I doesn't explain anything.
Edit: I've tried it through minimal adb fastboot command and could get my unlock-key. let's see how it goes from now on.
Thanks so far.
Click to expand...
Click to collapse
I only get error messages when entering all the fastboot commands.
FAILED (command write failed (Unknown error))

I could flash it using my laptop now, but when turning it on it says "verity mode is set to logging" and keeps on rebooting in a loop. Then I tried using twrp and mount it using an sd card, but that gave me error messages. are you sure this version is the right one for me? How difficult can it be? I wanna smash the phone against a wall.

curious45 said:
I could flash it using my laptop now, but when turning it on it says "verity mode is set to logging" and keeps on rebooting in a loop. Then I tried using twrp and mount it using an sd card, but that gave me error messages. are you sure this version is the right one for me? How difficult can it be? I wanna smash the phone against a wall.
Click to expand...
Click to collapse
It is the correct Oreo firmware for your device.
Re-verify the commands you're entering to flash are:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.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 boot boot.img
fastboot flash logo logo.bin
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_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
Bootloader is unlocked (the bottom of your fastboot screen says 'flashing_unlocked')?
Are you trying this in windows or linux?

I tried this version: PAYTON_OPWS28.46-21-16_subsidy-DEFAULT_regulatory-DEFAULT very often on my laptop (I guess it was a problem with the usb-ports on my normal pc), but I couldn't get my device to work. It always said "verity mode is set to logging". Then I tried installing PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT once (with my laptop) and it worked without any problems. The only thing is, that the device now says it's not the correct os when booting.

curious45 said:
... It always said "verity mode is set to logging"....
Click to expand...
Click to collapse
This will display for everyone with an unlocked bootloader. I know it does for me.

jhedfors said:
This will display for everyone with an unlocked bootloader. I know it does for me.
Click to expand...
Click to collapse
But it didn't boot though. It showed this text and it kept restarting over and over again.
It's fine now with this PAYTON_OPW27.57-40_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml version, but I always get the notifications that I should update to Android 9. I don't have any wifi problems whatsoever.
Do you have a solution on how to really disable / block those?

stuck at fastboot mode

i was trying to install twrp in my rog 2 but while installing twrp from fastboot and adb i got stuck in fastboot mode and cannot boot into main OS PLEASE HELP ME

Check current slot and then switch to other slot and boot.
First try
fastboot devices (make sure your device is listed)
if it boots to fastboot again
fastboot getvar current-slot
fastboot --set-active=a or fastboot --set-active=b
fastboot reboot

rabunz1105 said:
Check current slot and then switch to other slot and boot.
First try
fastboot devices (make sure your device is listed)
if it boots to fastboot again
fastboot getvar current-slot
fastboot --set-active=a or fastboot --set-active=b
fastboot reboot
Click to expand...
Click to collapse
Have the same problem. Did all that you say but keeps restarting.

ED_STUFF said:
Have the same problem. Did all that you say but keeps restarting.
Click to expand...
Click to collapse
I had this problem, and I had to download the RAW firmware files and run the "flashall.bat" file through fastboot.

ED_STUFF said:
Have the same problem. Did all that you say but keeps restarting.
Click to expand...
Click to collapse
Did you manage to solve this issue? I have the same problem.

rabunz1105 said:
Check current slot and then switch to other slot and boot.
First try
fastboot devices (make sure your device is listed)
if it boots to fastboot again
fastboot getvar current-slot
fastboot --set-active=a or fastboot --set-active=b
fastboot reboot
Click to expand...
Click to collapse
I was in csc fastboot mode then i mistakenly did some fastboot adb commands from github rog phone 2(am having rog 3, works same) try those and you will get into fast boot mode from csc fastboot mode after than try above for any query contaact me on my mail [email protected]
Thanks xda love you
rabunz1105 said:
Check current slot and then switch to other slot and boot.
First try
fastboot devices (make sure your device is listed)
if it boots to fastboot again
fastboot getvar current-slot
fastboot --set-active=a or fastboot --set-active=b
fastboot reboot
Click to expand...
Click to collapse

Flash fastboot Raw firmware

My phone is stuck in a bootloop. Original firmware, rom, everything, not rooted, bootloader locked. It just restarted by itself randomly and has been stuck in a bootloop ever since. I've flashed raw firmware but it didn't help. Help please

shinnsan said:
My phone is stuck in a bootloop. Original firmware, rom, everything, not rooted, bootloader locked. It just restarted by itself randomly and has been stuck in a bootloop ever since. I've flashed raw firmware but it didn't help. Help please
Click to expand...
Click to collapse
Have you fixed your issue? if not, have you tried flashing both slots, _a and _b, using the same raw rom? use fastboot cmd's to set either slot_a or slot_b to active so you know you're flashing each slot

MI A2 stuck in bootloop after soft reset

2 days ago i woke up to my phone's screen already on, it had been frozen for 2 hours (woke up at 3:40pm but the phone lockscreen showed 1:14pm) so i held down the power button to soft reset it but when it turned itself back on the phone was now stuck in a bootloop. Been 2 days now of trial and error and a whole load of research which now leaves me here. I have unlocked the bootloader (also done critical unlock) but trying to flash stock rom (have tried multiple versions) through miflash gives me "Flash bluetooth_a error", trying to flash it manually through cmd on platform tools gives me the following:
fastboot flash bluetooth_a bluetooth.img
Sending 'bluetooth_a' (556 KB) OKAY [ 0.031s]
Writing 'bluetooth_a' FAILED (remote: 'Error flashing partition : Device Error')
fastboot: error: Command failed
Anyone know how i can fix this? It's not rooted and the bootloader had never been unlocked previously.

Why are you trying to flash the bluetooth_a? Any reason for this?
Have you tried to: fastboot boot recovery_image_name.img ? And from there try to solve it?

ricardohorta said:
Why are you trying to flash the bluetooth_a? Any reason for this?
Have you tried to: fastboot boot recovery_image_name.img ? And from there try to solve it?
Click to expand...
Click to collapse
"bluetoot_a" is the first thing it tries to flash through mi flash. Its also the first thing in the images.

I´m a bit of a newbie, but i would try to boot into TWRP with fastboot command. From there do a full wipe on the phone and try again.
You might loose all your data.

ricardohorta said:
I´m a bit of a newbie, but i would try to boot into TWRP with fastboot command. From there do a full wipe on the phone and try again.
You might loose all your data.
Click to expand...
Click to collapse
Im not able to boot into twrp, it just hangs on the splash screen.

It should load directly from the bootloader.
Maybe you can try different TWRP versions, maybe it helps.
Xiaomi Mi A2
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
There are some instructions also.

rxsta said:
Im not able to boot into twrp, it just hangs on the splash screen.
Click to expand...
Click to collapse
I had that too. You can use this twrp https://androidfilehost.com/?fid=17248734326145702860 provided by @tecknight (here in post 2: https://forum.xda-developers.com/t/...lineageos-nightly-if-i-update-the-os.4240753/)

Sorry @User699 I was out of town, but I'm back now. What's your current status ?

User699 said:
I had that too. You can use this twrp https://androidfilehost.com/?fid=17248734326145702860 provided by @tecknight (here in post 2: https://forum.xda-developers.com/t/...lineageos-nightly-if-i-update-the-os.4240753/)
Click to expand...
Click to collapse
When i boot this version of twrp, the screen goes black for a bit but then just reboots itself.

Finally booted but still hanging on splash screen.

Well, that's odd. I tried this on LineageOS, maybe it doesn't work with another OS...
Did you do
Code:
fastboot boot twrpIMG.img
and NOT
Code:
fastboot flash boot twrpIMG.img
?

User699 said:
Well, that's odd. I tried this on LineageOS, maybe it doesn't work with another OS...
Did you do
Code:
fastboot boot twrpIMG.img
and NOT
Code:
fastboot flash boot twrpIMG.img
?
Click to expand...
Click to collapse
Yes, think it's safe to assume it's a lost cause. Not sure if i want to buy from xiaomi again.

rxsta said:
Yes, think it's safe to assume it's a lost cause. Not sure if i want to buy from xiaomi again.
Click to expand...
Click to collapse
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')

Changed slots but still won't boot, tried doing the "fastboot -w" but got this error
fastboot -w
Erasing 'userdata' FAILED (remote: 'Check device console.')
fastboot: error: Command failed

User699 said:
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Click to expand...
Click to collapse
User699 said:
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Click to expand...
Click to collapse
Doubt there's anything else I can do.

Think it's important I also mention that I can't get into the phone's recovery.

I see.
I'm sorry, I don't have any ideas toward it right now...
The only thing I could think of is booting into edl (emergency donwload) and reflash your os that way.
But you would have to open your device to access its hardware and since I don't have any experience with it, I couldn't help with it.
Changed slots but still won't boot, tried doing the "fastboot -w" but got this error
fastboot -w
Erasing 'userdata' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Click to expand...
Click to collapse
Does your device display anything on its screen?

User699 said:
I see.
I'm sorry, I don't have any ideas toward it right now...
The only thing I could think of is booting into edl (emergency donwload) and reflash your os that way.
But you would have to open your device to access its hardware and since I don't have any experience with it, I couldn't help with it.
Does your device display anything on its screen?
Click to expand...
Click to collapse
nope, it stays on the fastboot screen with no change. Warranty ended few days before the phone died so may as well try it.

rxsta said:
nope, it stays on the fastboot screen with no change. Warranty ended few days before the phone died so may as well try it.
Click to expand...
Click to collapse
I wish you the best of luck!