Database Users

[Q] Can't find SD card after flash

I just flashed the CM 6.1 rom to my legend, and not it can't find my SD card. I made a backup in rommanager (of my old rom) before i flashed, but when i enter rommanger it writes that my SD card has to mounted. So can't really install a new rom from there.
I can get into recovery, but when i run the recovery-windows.bat from my comp, nothing happends. Adb can't find my device, but fastboot can.
My SD cards work everywhere else, and i have formated it.
i have also tried with other SD cards that i have used before, but none of them have worked.
I have tried to follow this guide:
http://forum.xda-developers.com/showthread.php?t=751265
but when i do the the "fastboot eom enableqxdm 0"-command it says:
C:\androidSDK\tools>fastboot eom enableqxdm 0
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\androidSDK\tools>fastboot devices
HT03KNX04556 fastboot
Help anyone?
oh and when the phone is on and i connect it to the PC it just start charging, no notification or anything (on PC or phone)

just found out my legend keeps creating files on my SD card called: qxdm_20101213_163620_1.dm

mertins said:
I just flashed the CM 6.1 rom to my legend, and not it can't find my SD card. I made a backup in rommanager (of my old rom) before i flashed, but when i enter rommanger it writes that my SD card has to mounted. So can't really install a new rom from there.
I can get into recovery, but when i run the recovery-windows.bat from my comp, nothing happends. Adb can't find my device, but fastboot can.
My SD cards work everywhere else, and i have formated it.
i have also tried with other SD cards that i have used before, but none of them have worked.
I have tried to follow this guide:
http://forum.xda-developers.com/showthread.php?t=751265
but when i do the the "fastboot eom enableqxdm 0"-command it says:
C:\androidSDK\tools>fastboot eom enableqxdm 0
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
C:\androidSDK\tools>fastboot devices
HT03KNX04556 fastboot
Help anyone?
oh and when the phone is on and i connect it to the PC it just start charging, no notification or anything (on PC or phone)
Click to expand...
Click to collapse
Happens sometimes when u try to flash a rom on your device.
Your phone has bricked, u now need to learn how to unbrick it.
Search the forums for how to unbrick, im sure u gonna be able to find a solution.
peace
ps don't worry its solvable

Thanks, now at least i know what is wrong
tried to follow the howto USB Unbrink-thread (mentioned it in first post) and as i said i cant even get past "step one"
I'll keep searching

mertins said:
C:\androidSDK\tools>fastboot eom enableqxdm 0
Click to expand...
Click to collapse
Right command: fastboot oem enableqxdm 0

posted at another forum and found that out
feel kinda dumb now, been trying to execute that command for three days :/

Bootloader won't unlock on 6.0.1

I checked oem unlocking and usb debugging. Fastboot and adb work. I unlocked to update to 6.0.1 a few days. I want to flash custome roms. so I went to unlock bootloader and get the following:
C:\adb>fastboot devices
ertyugg(this edited for privacy) fastboot
C:\adb>fastboot flashing unlock
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
any suggestions??

You have to be using the latest version of fastboot, so you should update your sdk

GCbard said:
I checked oem unlocking and usb debugging. Fastboot and adb work. I unlocked to update to 6.0.1 a few days. I want to flash custome roms. so I went to unlock bootloader and get the following:
C:\adb>fastboot devices
ertyugg(this edited for privacy) fastboot
C:\adb>fastboot flashing unlock
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
any suggestions??
Click to expand...
Click to collapse
Your issue is the version of Fastboot you are using. Just search for Minimal ADB and use that tool instead.

chichu_9 said:
Your issue is the version of Fastboot you are using. Just search for Minimal ADB and use that tool instead.
Click to expand...
Click to collapse
got it. works! Thanks!!

Instal Blackberry priv Non US Carrier autoloader on AT&T

Hey
Is it possible to install Non US Carrier autoloader on AT&T to get rid of AT&T bloatware and to getting latest update via OTA?
Because I am live outs the US and did not have AT&T SIM.
Sent from my STV100-1 using Tapatalk

Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Run flashall script in AT&T autoloader to flash your phone as usual, you will be upgraded to the latest AT&T ROM without those AT&T bloatware.
Bonus:
If you would like to preserve data when flashing autoloaders, i.e. upgrade without reset your phone to factory default, follow this:
Open flashall script and comment out two lines that run below commands:
fastboot.exe oem securewipe
flash userdata %IMG%\userdata.img
Then run flashall script as usual.
Above are all tested on my phone without problem.

Thank you.
Sent from my iPad using Tapatalk

I did it today. It is woks perfectly. Thank you a lot :good:

I had a typo in my post regarding how to avoid wiping data while flashing. The 2nd command to comment out should be "flash userdata %IMG%\userdata.img".

Hey Kraml, your solution has a lot of interested folks over at Crackberry. Can you post some more detailed instructions?
Better yet, if you have an autoloader that's Marshmellow based already set up and share it with the community you'd become an instant rock star!
Here's the thread I started:
forums dot crackberry dot com/blackberry-priv-f440/potential-solution-our-vzw-att-friends-older-roms-1085292/#post12578681
replace dots with periods to get the link!

Does this convert AT&T to factory unlock??

zed011 said:
Does this convert AT&T to factory unlock??
Click to expand...
Click to collapse
No. It removes ATT software only.

kraml said:
I had a typo in my post regarding how to avoid wiping data while flashing. The 2nd command to comment out should be "flash userdata %IMG%\userdata.img".
Click to expand...
Click to collapse
Hey i have tried as you said and removed both the lines "fastboot.exe oem securewipe" "flash userdata %IMG%\userdata.img" from flashall.bat But i am getting the following error.
I am using AT and T unlocked device and i have tried the AT and T version AAG202 an i am getting the following error
Could you please help me out
BY INSTALLING THE SOFTWARE, YOU ARE AGREEING TO BE BOUND BY THE BlackBerry
Solution License Agreement which can be reviewed at www.blackberry.com/leg-
al/bbsla. IF YOU HAVE ANY QUESTIONS OR CONCERNS ABOUT THE TERMS OF THIS AG-
REEMENT, PLEASE CONTACT blackberry AT [email protected]. PLEASE READ
THIS DOCUMENT CAREFULLY BEFORE INSTALLING OR USING THE SOFTWARE.
***************************************************************************
Note:If device is not in fastboot mode
Please switch to fastboot mode by holding the power and volume down key for 30s
This script will wipe off all user data. Do you want to continue? [y/n]:y
'.\host\windows-x86\bin' is not recognized as an internal or external command,
operable program or batch file.
"It may take 5 to 15 minutes to securely wipe the device"
target reported max download size of 536870912 bytes
sending 'tz' (560 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.015s
target reported max download size of 536870912 bytes
sending 'hyp' (92 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.018s
target reported max download size of 536870912 bytes
sending 'sdi' (27 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.019s
target reported max download size of 536870912 bytes
sending 'pmic' (32 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.018s
target reported max download size of 536870912 bytes
sending 'rpm' (187 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.027s
target reported max download size of 536870912 bytes
sending 'sbl1' (495 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.032s
target reported max download size of 536870912 bytes
sending 'aboot' (1453 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.027s
target reported max download size of 536870912 bytes
sending 'bootsig' (0 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'recoverysig' (0 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.014s
target reported max download size of 536870912 bytes
sending 'boot' (17908 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'recovery' (17908 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.021s
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: authboot command permission denied)
finished. total time: 0.021s
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce
flashing unlock_bootloader <request> Issue unlock bootloader using request
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
target reported max download size of 536870912 bytes
sending 'modem' (68433 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.014s
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: authboot command permission denied)
finished. total time: 0.016s
target reported max download size of 536870912 bytes
erasing 'oem'...
FAILED (remote: authboot command permission denied)
finished. total time: 0.015s
rebooting...
finished. total time: 0.008s
Press any key to close this window

its because your phone has password protection. simply remove password / pin or pattern lock screen

Could someone make a file the that is the AT&T update package minus the bloatwear and without the wipe. I would gladly donate for it working.
Sent from my STV100-1 using Tapatalk
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
kraml said:
Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Run flashall script in AT&T autoloader to flash your phone as usual, you will be upgraded to the latest AT&T ROM without those AT&T bloatware.
Bonus:
If you would like to preserve data when flashing autoloaders, i.e. upgrade without reset your phone to factory default, follow this:
Open flashall script and comment out two lines that run below commands:
fastboot.exe oem securewipe
flash userdata %IMG%\userdata.img
Then run flashall script as usual.
Above are all tested on my phone without problem.
Click to expand...
Click to collapse
Dilini said:
its because your phone has password protection. simply remove password / pin or pattern lock screen
Click to expand...
Click to collapse
Could someone make the file for our AT&T Priv, minus the firmware and where it doesn't wipe the device. I would gladly pay for it!
Sent from my STV100-1 using Tapatalk

Ew, buddy I've done for myself with the instruction pretty easy except PIN password part.
I've pack whole files as a size 1.6GB 7z file, based on my carrier upload limit it's too big to uploading it, estimate more than an hour, so I packed the "Patch"
part for u, which means u still need to access the official site to download AT&T part and decompress it http://global.blackberry.com/content/blackberry-com/en/support/smartphones/Android-OS-Reload.html
Then download my "Patch" part https://drive.google.com/open?id=0B-qpp_ciC37MUEVmSDYzR3c2OXc
Decompress it any where u like then copy it to the folder where your AT&T files decompressed, confirm overwrite the same name files.
Then just run the flashall.bat
And yes I only modified Windows version
theusername said:
Could someone make a file the that is the AT&T update package minus the bloatwear and without the wipe. I would gladly donate for it working.
Sent from my STV100-1 using Tapatalk
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
Could someone make the file for our AT&T Priv, minus the firmware and where it doesn't wipe the device. I would gladly pay for it!
Sent from my STV100-1 using Tapatalk
Click to expand...
Click to collapse

Good morning, I have a question, recently bought the BlackBerry priv AT & T unlocked, I wonder if I can put Android's own BlackBerry 6 clean without losing the unlock? or I have to put the AT & T it? I run the risk of having a locked phone? Excuse my English.

Do we know if this is an error which can be ignored safely or there is fix for this?
error: cannot load '.\img\cache.img.\host\windows-x86\bin\fastboot.exe'
target reported max download size of 536870912 bytes

Hello!
May i ask a question does your patch can work with new version AAG873?
Thanks for your kind reply
loachh said:
Ew, buddy I've done for myself with the instruction pretty easy except PIN password part.
I've pack whole files as a size 1.6GB 7z file, based on my carrier upload limit it's too big to uploading it, estimate more than an hour, so I packed the "Patch"
part for u, which means u still need to access the official site to download AT&T part and decompress it http://global.blackberry.com/content/blackberry-com/en/support/smartphones/Android-OS-Reload.html
Then download my "Patch" part https://drive.google.com/open?id=0B-qpp_ciC37MUEVmSDYzR3c2OXc
Decompress it any where u like then copy it to the folder where your AT&T files decompressed, confirm overwrite the same name files.
Then just run the flashall.bat
And yes I only modified Windows version
Click to expand...
Click to collapse

And also: Could you do a Mac Version as well?
Greetings from Germany

Did anyone else that did this get an OTA update notification today? I'm actually surprised I would get something considering I'm not using an AT&T simcard.
Update:
Looks like this is the reason why I received the OTA update. Blackberry is starting to support the unlocked AT&T phones. http://www.techtimes.com/articles/1...receives-updates-directly-from-blackberry.htm

kraml said:
Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Run flashall script in AT&T autoloader to flash your phone as usual, you will be upgraded to the latest AT&T ROM without those AT&T bloatware.
Bonus:
If you would like to preserve data when flashing autoloaders, i.e. upgrade without reset your phone to factory default, follow this:
Open flashall script and comment out two lines that run below commands:
fastboot.exe oem securewipe
flash userdata %IMG%\userdata.img
Then run flashall script as usual.
Above are all tested on my phone without problem.
Click to expand...
Click to collapse
I just did this on the Verizon variant, which i'm using on T-Mobile in the US, and it is insane how much better it's running. I'm pretty sure everyone should do this if they don't have the factory unlocked model

kraml said:
Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Run flashall script in AT&T autoloader to flash your phone as usual, you will be upgraded to the latest AT&T ROM without those AT&T bloatware.
Bonus:
If you would like to preserve data when flashing autoloaders, i.e. upgrade without reset your phone to factory default, follow this:
Open flashall script and comment out two lines that run below commands:
fastboot.exe oem securewipe
flash userdata %IMG%\userdata.img
Then run flashall script as usual.
Above are all tested on my phone without problem.
Click to expand...
Click to collapse
Do you know if this will work on a verizon branded model? I am looking at a VZ model for cheap but will be using it on Tmo, on a side note anyone know if the VZ model supports wifi calling on Tmo? Thanks.

kraml said:
Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Click to expand...
Click to collapse
I have additionally also replaced system.img with the one from the common autoloader. Otherwise the "System update" wouldn't do anything. Now I get the normal Android update screen, the not dreaded "AT&T Software update". I hope that it'll actually update.
Stefan

Redmi Note 4 Mido 4/64 Factory Reset lead to boot-loop - please help resetting!

Dear Community,
please follow my humble plea and help me getting my Xiaomi Redmi Note 4 Mido "SnapDragon" Global working again.
My device is on stock rom, bootloader LOCKED and no root.
What happened?
I updated to version V9.0.3.0.NCFMIEI without any problems.
Now the updater app tells me to upgrade to the latest version Version: V9.0.5.0.NCFMIEI (MIUI9).
The Update-App tells me that the update is only 52MB of size, I downloaded it and when I reboot the device the stock recovery tells me that "Update.zip failed to install".
Then I reboot back into the system and now the Updater-App tells me the update was 1,3Gbyte of size. When I try to download and install it, it always says that "the source could not be verified" and "not allowed to update to custom roms".
I tried this multiple times over the last weeks, nothing ever changed.
Bad thing is, I started to get random shutdowns and reboots during daily usage.
My thinking was I should factory reset the device. I backed up all data and used the android feature from settings to factory restet. When rebooting I endet up at the Mi logo with a small progress bar (not the 3 dots!!) . The factory reset fails because nothing happens when the bar is full (I let the phone work for about 2 hours). When I reboot I always get the same progress-bar but it crashes within the first third and then reboots again.
I read this forum and installed "MiFlash", downloaded the latest firmware from Xiaomi, named "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File Download" and tried to flash it. The flashing only takes about 1 second saying everything went fine, but the log says the following:
Code:
[0,00 b346e0dc0304]:image path:C:\firmware2
[0,00 b346e0dc0304]:env android path:C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android
[0,00 b346e0dc0304]:script :C:\firmware2\flash_all_lock.bat
[0,01 b346e0dc0304]:Physical Memory Usage:1728512 Byte
[0,08 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
[0,14 b346e0dc0304]:product: mido
[0,14 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
[0,20 b346e0dc0304]:product: mido
[0,20 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>rem "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 erase bk12 2>&1
[0,20 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>if not 0 == 0 exit /B 1
[0,20 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>rem "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar soc_id 2>&1 | findstr /r /c:"^soc_id: *239" || echo Missmatching image and device in soc_id
[0,20 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>rem "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar soc_id 2>&1 | findstr /r /c:"^soc_id: *239" || exit /B 1
[0,20 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 oem device-info 2>&1 | findstr /r /c:"Device unlocked: true" || echo Device oem locked
[0,28 b346e0dc0304]:Device oem locked
[0,28 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 oem device-info 2>&1 | findstr /r /c:"Device unlocked: true" || exit /B 1
[0,36 b346e0dc0304]:process exit.
[0,36 b346e0dc0304]:flash done
I figured I downloaded the wrong image, so i tried with "Redmi 4X Latest Global Stable Version Fastboot File Download" but it gave me the same positive information within MiFlash interface but the log stated the same.
So I tried with the Mediatek "Nikel" version, now MiFlash tells me right from the beginning, red light, that my image is wrong and the log looks like this:
Code:
[0,00 b346e0dc0304]:image path:L:\Downloads\nikel_update
[0,00 b346e0dc0304]:env android path:C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android
[0,00 b346e0dc0304]:script :L:\Downloads\nikel_update\flash_all_lock.bat
[0,01 b346e0dc0304]:Physical Memory Usage:1953792 Byte
[0,07 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar product 2>&1 | findstr /r /c:"^product: nikel" ||
[0,11 b346e0dc0304]:Missmatching image and device error
[0,11 b346e0dc0304]:process exit.
[0,11 b346e0dc0304]:error:Missmatching image and device error
Maybe there is an error with MiFlash itself? I installed all drivers, I run windows with unsigned drivers in test mode.
Bottom Line:
Can you help me to just reset my device and make it usable again? THANK YOU SO MUCH!!!

edwardenglish said:
Dear Community,
please follow my humble plea and help me getting my Xiaomi Redmi Note 4 Mido "SnapDragon" Global working again.
My device is on stock rom, bootloader LOCKED and no root.
What happened?
I updated to version V9.0.3.0.NCFMIEI without any problems.
Now the updater app tells me to upgrade to the latest version Version: V9.0.5.0.NCFMIEI (MIUI9).
The Update-App tells me that the update is only 52MB of size, I downloaded it and when I reboot the device the stock recovery tells me that "Update.zip failed to install".
Then I reboot back into the system and now the Updater-App tells me the update was 1,3Gbyte of size. When I try to download and install it, it always says that "the source could not be verified" and "not allowed to update to custom roms".
I tried this multiple times over the last weeks, nothing ever changed.
Bad thing is, I started to get random shutdowns and reboots during daily usage.
My thinking was I should factory reset the device. I backed up all data and used the android feature from settings to factory restet. When rebooting I endet up at the Mi logo with a small progress bar (not the 3 dots!!) . The factory reset fails because nothing happens when the bar is full (I let the phone work for about 2 hours). When I reboot I always get the same progress-bar but it crashes within the first third and then reboots again.
I read this forum and installed "MiFlash", downloaded the latest firmware from Xiaomi, named "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File Download" and tried to flash it. The flashing only takes about 1 second saying everything went fine, but the log says the following:
Code:
[0,00 b346e0dc0304]:image path:C:\firmware2
[0,00 b346e0dc0304]:env android path:C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android
[0,00 b346e0dc0304]:script :C:\firmware2\flash_all_lock.bat
[0,01 b346e0dc0304]:Physical Memory Usage:1728512 Byte
[0,08 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar product 2>&1 | findstr /r /c:"^product: *mido" || echo Missmatching image and device
[0,14 b346e0dc0304]:product: mido
[0,14 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar product 2>&1 | findstr /r /c:"^product: *MSM8953" || "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar product 2>&1 | findstr /r /c:"^product: *mido" || exit /B 1
[0,20 b346e0dc0304]:product: mido
[0,20 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>rem "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 erase bk12 2>&1
[0,20 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>if not 0 == 0 exit /B 1
[0,20 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>rem "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar soc_id 2>&1 | findstr /r /c:"^soc_id: *239" || echo Missmatching image and device in soc_id
[0,20 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>rem "C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar soc_id 2>&1 | findstr /r /c:"^soc_id: *239" || exit /B 1
[0,20 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 oem device-info 2>&1 | findstr /r /c:"Device unlocked: true" || echo Device oem locked
[0,28 b346e0dc0304]:Device oem locked
[0,28 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 oem device-info 2>&1 | findstr /r /c:"Device unlocked: true" || exit /B 1
[0,36 b346e0dc0304]:process exit.
[0,36 b346e0dc0304]:flash done
I figured I downloaded the wrong image, so i tried with "Redmi 4X Latest Global Stable Version Fastboot File Download" but it gave me the same positive information within MiFlash interface but the log stated the same.
So I tried with the Mediatek "Nikel" version, now MiFlash tells me right from the beginning, red light, that my image is wrong and the log looks like this:
Code:
[0,00 b346e0dc0304]:image path:L:\Downloads\nikel_update
[0,00 b346e0dc0304]:env android path:C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android
[0,00 b346e0dc0304]:script :L:\Downloads\nikel_update\flash_all_lock.bat
[0,01 b346e0dc0304]:Physical Memory Usage:1953792 Byte
[0,07 b346e0dc0304]:C:\XiaoMi\XiaoMiFlash>"C:\XiaoMi\XiaoMiFlash\Source\ThirdParty\Google\Android\fastboot.exe" -s b346e0dc0304 getvar product 2>&1 | findstr /r /c:"^product: nikel" ||
[0,11 b346e0dc0304]:Missmatching image and device error
[0,11 b346e0dc0304]:process exit.
[0,11 b346e0dc0304]:error:Missmatching image and device error
Maybe there is an error with MiFlash itself? I installed all drivers, I run windows with unsigned drivers in test mode.
Bottom Line:
Can you help me to just reset my device and make it usable again? THANK YOU SO MUCH!!!
Click to expand...
Click to collapse
First of all, never ever flash images or roms not made for your chipset, (Mediatek and snapdragon are like two poles of earth)
Secondly, are you able to boot in fastboot mode?
To check this press and hold power and volume down until a logo saying fastboot mode appears.
REPLY ASAP

MyNameIsRage said:
Dear Community,
please follow my humble plea and help me getting my Xiaomi Redmi Note 4 Mido "SnapDragon" Global working again.
My device is on stock rom, bootloader LOCKED and no root.
What happened?
I updated to version V9.0.3.0.NCFMIEI without any problems.
Now the updater app tells me to upgrade to the latest version Version: V9.0.5.0.NCFMIEI (MIUI9).
The Update-App tells me that the update is only 52MB of size, I downloaded it and when I reboot the device the stock recovery tells me that "Update.zip failed to install".
Then I reboot back into the system and now the Updater-App tells me the update was 1,3Gbyte of size. When I try to download and install it, it always says that "the source could not be verified" and "not allowed to update to custom roms".
I tried this multiple times over the last weeks, nothing ever changed.
Bad thing is, I started to get random shutdowns and reboots during daily usage.
My thinking was I should factory reset the device. I backed up all data and used the android feature from settings to factory restet. When rebooting I endet up at the Mi logo with a small progress bar (not the 3 dots!!) . The factory reset fails because nothing happens when the bar is full (I let the phone work for about 2 hours). When I reboot I always get the same progress-bar but it crashes within the first third and then reboots again.
I read this forum and installed "MiFlash", downloaded the latest firmware from Xiaomi, named "Redmi Note 4 Qualcomm Latest Global Stable Version Fastboot File Download" and tried to flash it. The flashing only takes about 1 second saying everything went fine, but the log says the following:
I figured I downloaded the wrong image, so i tried with "Redmi 4X Latest Global Stable Version Fastboot File Download" but it gave me the same positive information within MiFlash interface but the log stated the same.
So I tried with the Mediatek "Nikel" version, now MiFlash tells me right from the beginning, red light, that my image is wrong and the log looks like this:
First of all, never ever flash images or roms not made for your chipset, (Mediatek and snapdragon are like two poles of earth)
Secondly, are you able to boot in fastboot mode?
To check this press and hold power and volume down until a logo saying fastboot mode appears.
REPLY ASAP
Click to expand...
Click to collapse
Thanks for your reply.
I decided to unlock BL and flashed the original stock ROM via fastboot method and MiFlash. After installing twrp and wiping dalvik and cache everything runs fine now.
No crashes no reboots since then.
Sorry for everyone but seems there is no easier method then unlocking BL

edwardenglish said:
Thanks for your reply.
I decided to unlock BL and flashed the original stock ROM via fastboot method and MiFlash. After installing twrp and wiping dalvik and cache everything runs fine now.
No crashes no reboots since then.
Sorry for everyone but seems there is no easier method then unlocking BL
Click to expand...
Click to collapse
Yes that was actually the *only* thing you could've done to restore.

I have the same/similar problem, but also are the 3 screen buttons flashing in a diverent frequency. I tryed to flash with mi flash and I tryed the point methode. No responce! No bootloader is staring. Is there some body who has or had the same problem? Hope you can help me....
Verstuurd vanaf mijn MI 6 met Tapatalk

patrickharpa said:
I have the same/similar problem, but also are the 3 screen buttons flashing in a diverent frequency. I tryed to flash with mi flash and I tryed the point methode. No responce! No bootloader is staring. Is there some body who has or had the same problem? Hope you can help me....
Verstuurd vanaf mijn MI 6 met Tapatalk
Click to expand...
Click to collapse
I have the same Problem like you. I tryed also the Testpoint Methode and flash with MiFlash any Fastboot-Roms - No Chance the Bootloop is always there.
Ist the anybody who help us?
greetings Chris

Writing partition failed flashing raw file

Zenfone ZE552KL stuck at ASUS boot logo and can only access fastboot. I tried using asus flash tool and whenever I flash stock oreo raw image it fails and status says FAILED(remote: writing partition failed)
I tried extracting the raw zip and run cmd command flashall_AFT.cmd WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw and this is the result
Code:
##################################################################
####################### FLASH RAW FILE ########################
##################################################################
## RAW: WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
## ERASE DATA: 0
## SSN:
===================================================================
[command] : fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
/////////////////////////////////////////////////
// ASUS Fastboot Tool (Android N 7.1.1)
// Version V1.4 (2017/05/20)
// Support_AB : 0
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_PROJECT_NAME = ZE552KL
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// CPU ID = 046
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// RE-PARTITION ENABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_RAW_VERSION = V1
/////////////////////////////////////////////////
target reported max download size of 534773760 bytes
sending 'partition' CRC (0x3016d48d)...
OKAY [ 0.029s]
writing 'CRC'...
OKAY [ 0.022s]
sending 'partition' (33 KB)...
OKAY [ 0.062s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.227s
"FAILED, fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw failure, EXIT!"
The phone is not mine, a friend asked me to fix his phone and I hit a wall here. I cannot flash nor boot twrp.img. Whenever I try to flash twrp it fails and the error is remote: too many links. Any insights?

rexendz said:
Zenfone ZE552KL stuck at ASUS boot logo and can only access fastboot. I tried using asus flash tool and whenever I flash stock oreo raw image it fails and status says FAILED(remote: writing partition failed)
I tried extracting the raw zip and run cmd command flashall_AFT.cmd WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw and this is the result
Code:
##################################################################
####################### FLASH RAW FILE ########################
##################################################################
## RAW: WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
## ERASE DATA: 0
## SSN:
===================================================================
[command] : fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
/////////////////////////////////////////////////
// ASUS Fastboot Tool (Android N 7.1.1)
// Version V1.4 (2017/05/20)
// Support_AB : 0
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_PROJECT_NAME = ZE552KL
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// CPU ID = 046
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// RE-PARTITION ENABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_RAW_VERSION = V1
/////////////////////////////////////////////////
target reported max download size of 534773760 bytes
sending 'partition' CRC (0x3016d48d)...
OKAY [ 0.029s]
writing 'CRC'...
OKAY [ 0.022s]
sending 'partition' (33 KB)...
OKAY [ 0.062s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.227s
"FAILED, fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw failure, EXIT!"
The phone is not mine, a friend asked me to fix his phone and I hit a wall here. I cannot flash nor boot twrp.img. Whenever I try to flash twrp it fails and the error is remote: too many links. Any insights?
Click to expand...
Click to collapse