Hello,
I have the following problem. I unlocked the bootloader with the MI Unlocker after I waitedf freaking 360h.
I then tried to flash Xiamoi EU Rom - something didn't work as expected and I tried to flash the offical rom from miui com.
During the fastboot flash the phone stuck and screen go black. I tried to power off and power on but it doesn't react to anything
Fastboot shows the device as ????????..if I try a fastboot reboot FAILED (Write to device failed (Unknown error)).
Any ideas what I can do to fix this?
Well, explain the steps you did please.
Skickat från min MI 9 via Tapatalk
As I wrote I first unlocked the bootloader
Installed TWRP and flashed the EU ROM from xiamoi.eu.
Since Google Pay wasn't working on this one either I wanted to return to the global image EEA.
So I downloaded the offical tgz with the flash_all.bat in fastboot mode..
It started but stuck at the elf file..screen went black and since that the fastboot only shows ????????
I tried holding power for 10, 15,30.up to 2min..it didn't turn of the LED is blinking when hitting the power button.
Thats all
ioglnx said:
As I wrote I first unlocked the bootloader
Installed TWRP and flashed the EU ROM from xiamoi.eu.
Since Google Pay wasn't working on this one either I wanted to return to the global image EEA.
So I downloaded the offical tgz with the flash_all.bat in fastboot mode..
It started but stuck at the elf file..screen went black and since that the fastboot only shows ????????
I tried holding power for 10, 15,30.up to 2min..it didn't turn of the LED is blinking when hitting the power button.
Thats all
Click to expand...
Click to collapse
its looked like you beeing soft bricked...try installing miflash and boot into fastboot and plug it in see if miflash can detect your device...
fatalynx05 said:
its looked like you beeing soft bricked...try installing miflash and boot into fastboot and plug it in see if miflash can detect your device...
Click to expand...
Click to collapse
As written it won't turn off..it is not responding to power button - only LED is blinking when I press it or keep it pressed..think this crappy phone died.
Just to be sure... Did you press volume down + power?
ioglnx said:
Hello,
I have the following problem. I unlocked the bootloader with the MI Unlocker after I waitedf freaking 360h.
I then tried to flash Xiamoi EU Rom - something didn't work as expected and I tried to flash the offical rom from miui com.
During the fastboot flash the phone stuck and screen go black. I tried to power off and power on but it doesn't react to anything
Fastboot shows the device as ????????..if I try a fastboot reboot FAILED (Write to device failed (Unknown error)).
Any ideas what I can do to fix this?
Click to expand...
Click to collapse
Download FASTBOOT ROM from the official site and unzip it.
After charging the phone for a while, press and hold the Power button and Volume +-button for a few seconds.
If FAST BOOT starts, flash the unzip FAST BOOT ROM with the following command:
Some of the commands may end in an error, but ignore it and proceed to the end.
Try it. Wish good luck.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash cust cust.img
fastboot flash dtbo dtbo.img
fastboot flash dummy dummy.img
fastboot flash logo logo.img
fastboot flash metadata metadata.img
fastboot flash misc misc.img
fastboot flash persist persist.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
Thanks for the suggestion but you may overerad the one important point..I tried already ...
it doesn't responds to power button press in any way except the LED is BLINKING at that moment i press it.
I have tried Power + Volume+ and - nothing really nothing happens..the battery is fully charged.
Well I return it and fill RMA.
Kaeru Sapporo said:
Download FASTBOOT ROM from the official site and unzip it.
After charging the phone for a while, press and hold the Power button and Volume +-button for a few seconds.
If FAST BOOT starts, flash the unzip FAST BOOT ROM with the following command:
Some of the commands may end in an error, but ignore it and proceed to the end.
Try it. Wish good luck.
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash cust cust.img
fastboot flash dtbo dtbo.img
fastboot flash dummy dummy.img
fastboot flash logo logo.img
fastboot flash metadata metadata.img
fastboot flash misc misc.img
fastboot flash persist persist.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
Click to expand...
Click to collapse
Related
when i try to go into download mode on VS980, the screen shows download mode, but then quickly changes to a black screen saying
[520] Fastboot mode started
[610]--reset--
[610]--portchange--
[730] fastboot: processing commads
i need to get into download mode to revert to stock 39A?
Easiest fix
markalmza said:
when i try to go into download mode on VS980, the screen shows download mode, but then quickly changes to a black screen saying
[520] Fastboot mode started
[610]--reset--
[610]--portchange--
[730] fastboot: processing commads
i need to get into download mode to revert to stock 39A?
Click to expand...
Click to collapse
Happened to me a couple days ago. Easiest fix:
1. Download Ubuntu, run it on a virtual machine, run it as a usb drive or dvd drive.
2. Get the proper images for your LG G2 version and current ROM from Autoprime site (can't post link, sorry. You will need aboot, boot, recovery, and laf).
3. Install adb and fastboot from Ubuntu's software center.
4. open Ubuntu's terminal and run the following fastboot commands with root access:
Code:
fastboot erase aboot
fastboot erase boot
fastboot erase recovery
fastboot erase laf
fastboot flash aboot /*filepath*/aboot.img
fastboot flash boot /*filepath*/boot.img
fastboot flash recovery /*filepath*/recovery.img
fastboot flash laf /*filepath*/laf
fastboot reboot
5. Then press your power button for about 15 seconds, when phone is completely off press VOL up then plug your usb cable and that should get you to Download Mode
Any questions or issues, PM me. :good:
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?
Hello, I installed Havoc OS on my MI A2, but then an update was requested, I did the update, but when I rebooted the device, it did not start, I went into fastboot mode and I reinstalled the havoc. "androidOne" screen and nothing happens, now I have to enter fastboot mode with the command "fastboot boot twrp.img" and the error "failed to load / authentication boot image" appears, I tried flashing the rom stock using the MiFlash, and the cell phone persists with the same error, now my cell phone is with the bootloader locked and I do not know what to do
gmoura5010 said:
Hello, I installed Havoc OS on my MI A2, but then an update was requested, I did the update, but when I rebooted the device, it did not start, I went into fastboot mode and I reinstalled the havoc. "androidOne" screen and nothing happens, now I have to enter fastboot mode with the command "fastboot boot twrp.img" and the error "failed to load / authentication boot image" appears, I tried flashing the rom stock using the MiFlash, and the cell phone persists with the same error, now my cell phone is with the bootloader locked and I do not know what to do
Click to expand...
Click to collapse
Hi
Enter to fastboot and try this:
open a cmd
fastboot devices
fastboot -w
fastboot getvar current-slot ( you can see it a or b)
fasboot set_active b
Then
Try boot into twrp etc
Have luck pal !!
rodrimx4 said:
Hi
Enter to fastboot and try this:
open a cmd
fastboot devices
fastboot -w
fastboot getvar current-slot ( you can see it a or b)
fasboot set_active b
Then
Try boot into twrp etc
Have luck pal !!
Click to expand...
Click to collapse
Thanks, I was able to repair after unlocking the bootloader again and then unlocking the critical parts, so I flashed a stock rom from August 2018, however didn't block the bootloader again.
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
Hi guys, im posting this hoping theres a solution for my problem. I was folowing this guide to try install the stock firmware on this device and remove a virus that i wasnt able to remove even after cleaning the user data partiton (it was an anoying bar that started every time the phone booted). Well everything went acording to plan until i send a reboot command trough adb before flashing anything. Now the phone wont turn on and my computer doesnt detect it, doesnt show anything on screen and the computer plays the pluged and unplugged hardware sound constantly.
Moto E4 Guide To Full Stock Firmware Restore and Re-lock Bootloader Any Variant
Note : Do not erase/flash Bootloader file preloader.img or preloader.binfastboot erase preloader fastboot flash preloader preloader.img Do not erase/flash partition table file pgpt.img/gpt.img or pgpt.bin/gpt.binfastboot erase pgpt or gpt...
forum.xda-developers.com
fastboot erase boot
fastboot erase efuse
fastboot erase expdb
fastboot erase flashinfo
fastboot erase frp
fastboot erase hw
fastboot erase keystore
fastboot erase lk
fastboot erase logo
fastboot erase metadata
fastboot erase nvdata
fastboot erase nvram
fastboot erase oem
fastboot erase oemkeystore
fastboot erase otp
fastboot erase para
fastboot erase persist
fastboot erase proinfo
fastboot erase protect1
fastboot erase protect2
fastboot erase recovery
fastboot erase seccfg
fastboot erase secro
fastboot erase tee1
fastboot erase tee2
fastboot erase utags
fastboot erase system
fastboot erase userdata
Click to expand...
Click to collapse
I ran all of the above, searching on the forums i find some people that could get the phones back into adb using an sd card but the image files dont match my model number. Is there any way the phone can be recovered?.
R3ISEN said:
Hi guys, im posting this hoping theres a solution for my problem. I was folowing this guide to try install the stock firmware on this device and remove a virus that i wasnt able to remove even after cleaning the user data partiton (it was an anoying bar that started every time the phone booted). Well everything went acording to plan until i send a reboot command trough adb before flashing anything. Now the phone wont turn on and my computer doesnt detect it, doesnt show anything on screen and the computer plays the pluged and unplugged hardware sound constantly.
Click to expand...
Click to collapse
If you PC is making that sound, it is connecting, it may be in some kind of bootloop.
try using wall charger for a few hours.
Moto E4 Guide To Full Stock Firmware Restore and Re-lock Bootloader Any Variant
Note : Do not erase/flash Bootloader file preloader.img or preloader.binfastboot erase preloader fastboot flash preloader preloader.img Do not erase/flash partition table file pgpt.img/gpt.img or pgpt.bin/gpt.binfastboot erase pgpt or gpt...
forum.xda-developers.com
I ran all of the above, searching on the forums i find some people that could get the phones back into adb using an sd card but the image files dont match my model number. Is there any way the phone can be recovered?.
Click to expand...
Click to collapse
Not unless it's in EDL mode, PC will show it as a Qualcomm device.
sd_shadow said:
If you PC is making that sound, it is connecting, it may be in some kind of bootloop.
try using wall charger for a few hours.
Not unless it's in EDL mode, PC will show it as a Qualcomm device.
Click to expand...
Click to collapse
Thanks ill try pluggin it to the wall for a few hours, i will post back with the updates
Well i left it overnight to charge and now ive got the same unplugged and plugged hardware sound on windows but the device manager shows up a "MT65xx preloader" that pops in and out from the list.
Do you think there is good sign?
R3ISEN said:
Well i left it overnight to charge and now ive got the same unplugged and plugged hardware sound on windows but the device manager shows up a "MT65xx preloader" that pops in and out from the list.
Do you think there is good sign?
Click to expand...
Click to collapse
Yes, the MT65xx preloader means you have a MediaTek processor.
The XT1772 MediaTek version is codename is nicklaus.
Try this Flashtool
https://mirrors-obs-2.lolinet.com/firmware/motorola/2016/nicklaus/flashtool/
sd_shadow said:
Yes, the MT65xx preloader means you have a MediaTek processor.
The XT1772 MediaTek version is codename is nicklaus.
Try this Flashtool
https://mirrors-obs-2.lolinet.com/firmware/motorola/2016/nicklaus/flashtool/
Click to expand...
Click to collapse
I dont have the MediaTek DA USB VCOM driver installed, so at the moment it only shows up a unknown device. Could you help my find the correct driver? Also, if i manage to get the tool to flash the phone do i have to untick any component from the list? (like preloader) or i jus select everything?
Thank you in advance
Hey good news i finally was able to resucitate the phone! i found the drivers searching for the device id shown in device manager. I used the latest sp flash tool with my oem rom with all the firmware modules selected and got it working!. Now im trying to relock the bootloader to completly restore it to factory defaults.