Related
Hey guys! Is there any way to unlock Redmi Pro's bootloader without waiting for permission from Xiaomi? Have anybody found a way to bypass it?
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
hello i haven't on my xiaomi redmi pro eom unlock in the devlopper mode help me pls
criszz said:
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
Click to expand...
Click to collapse
press in settings about phone 7 time on miui version
after that you will find developer options in aditional settings
criszz said:
press in settings about phone 7 time on miui version
after that you will find developer options in aditional settings
Click to expand...
Click to collapse
Sadly there is no oem unlock option in developer options. I'm on MIUI 8.1.2.0 Stable (MHQCNDI)
EDIT: i just switched to Developer ROM and still nothing.
sorry, my mistake i use another laguage, activate usb debuging , conect to the pc and run adb , if some permision asked alow
I can't unlock it using fastboot oem unlock since it's mediatek device =/ When I try I get
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0xffffffff
)
finished. total time: 0.016s"
Click to expand...
Click to collapse
i unlocked that way, maybe you do something wrong
try another way without unlocking try flash twrp with spflash tool
Do you remember what miui version did you have when you unlocked this way? Maybe I can roll back to it and then try again. Were you using developer or stable rom?
i was on fake/vendor rom this i thinlk http://blog.geekbuying.com/index.ph...ndroid-6-0-smartphone-firmware-212302-161109/
Crissz, your bootloader was allready unlocked when you received your phone. You cannot do a simple oem unlock via fastboot with a xiaomi phone. It's a fact..
@KarKlim please try fastboot oem unlock-go comand too
This method does not work as many say
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0xffffffff
)
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Redmi Pro with Latest stable china rom
Is it possible? Xiaomi regoke my unclock previleges and now i have my Redmi Pro stuck in China Developer Rom. No way to install multilanguase Xiaomi.eu... can someone help please?
Maybe try with a new xiaomi account with different sim card.
And then from a different internet ip, from your friend or something.
I have no idea how they collect data or what. I'm just guessing here.
wow great news for Xiaomi lovers:
wow great news for Xiaomi lovers:
GeekBuying offering 73% off ( Xiaomi Redmi Pro 3GB + 64GB) 184.65 EURO
spam, all post of this user is spam
So, I bought my Redmi Pro today and i want to install xiaomi.eu ROM. Do I have to unlock bootloader first? Or can I do it with unlock bootloader?
No OEM in my xiaomi redmi pro
[[/B]
criszz said:
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
Click to expand...
Click to collapse
Can you help me please because I don't have a OEM unlock option in redmi pro and how to unlock bootloader... please man
criszz said:
easy, first make sure you have spflash tool and a working fastboot rom (just in case of trouble)
Next make sure your computer has working fastboot and adb.
Enable USB debugging on the device.
Enable OEM unlock in the Developer options settings on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
From the same terminal, type the following command to unlock the bootloader:
fastboot oem unlock
Device is wiped & unlocked & no OS
Now flash twrp, reboot into it and copy xiaomi.eu rom on card & install
Good luck
Click to expand...
Click to collapse
Not worked for redmi note 8 pro ......failed.....
Hi everybody...I'm in trouble with my Yotaphone YD201.
I done format data with TWRP.
Then, I run these commands with Win10 for clean flash of RU144:
Code:
fastboot flash boot {Directory_firmware/boot.img}
fastboot flash -S 512M system {Directory_firmware/system.img}
fastboot flash recovery {Directory_firmware/recovery.img}
fastboot flash cache {Directory_firmware/cache.img}
fastboot flash modem {Directory_firmware/radio/NON-HLOS.bin}
fastboot flash sbl1 {Directory_firmware/radio/sbl1.mbn}
fastboot flash rpm {Directory_firmware/radio/rpm.mbn}
fastboot flash tz {Directory_firmware/radio/tz.mbn}
fastboot flash userdata {Directory_firmware/userdata.img}
fastboot flash aboot {Directory_file__emmc_appsboot.mbn}
fastboot reboot
After the last one, Screen gone black and nothing appends...
Now, adb and fastboot can't contact with Yota ("adb devices" give "<waiting for devices") .
Now, In Win devices, I can find " QHSUSB_BULK".
After some search, I found out that my phone is in a recovery mode of Qualcomm. Does anybody know how to unblock it? Problably I need of specific driver to contact with this phone. Thanks so much!
P.S.: do not esitate to contact me if my english is not clear =)
How about a method like this https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/ but use Yotaphone files instead?
evilracer123 said:
How about a method like this (...) but use Yotaphone files instead?
Click to expand...
Click to collapse
This discussion uses Msm8974DownloadTool.exe from the directory of ColorOS but the wire connection does not work (the file is no longer available, from Mega).
Also, not sure if I can use Msm8974DownloadTool.exe with Yotaphone. Alternatively, what can I use?
1.
Connect your Android device to computer via USB.
2.
Ensure USB Debugging mode is ENABLED on Android device.
Settings > About Phone > Build number > Tap it 7 times to become developer;
Settings > Developer Options > USB Debugging.
3.
download adb driver
http://adbdriver.com/downloads/
download Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
4.
unzip adb driver and instal it
http://adbdriver.com/documentation/...river-installer-for-windows-xp-vista-7-8.html
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
5.
Extract the Minimal ADB and Fastboot Tool file to your PC
6.
Download your RecoveryFile.img file or full fastboot Rom file
and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ”
so all files will be in single folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7.
open folder Minimal ADB and Fastboot
in the folder , On your keyboard press SHIFT and right click with your mouse " Shift + right click "
click on " open command window here "
8.
Now type following command
adb fastboot
Unlocking the bootloader
Note: Using the fastboot command
When the fastboot command is used on the Storm, the vendor id command option must be added.
The vendor id for the Storm is 0x2970. For example, fastboot devices, would be fastboot -i 0x2970 devices.
Enable OEM unlock in the Developer options settings on the device.
(Note: Not all devices have this setting, so continue with next step if yours does not.)
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", try running fastboot as root.
From the same terminal, type the following command to unlock the bootloader:
fastboot -i 0x2970 oem unlock-go
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
fastboot reboot
Installing a custom recovery using fastboot
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
fastboot reboot
full rom fastboot
adb reboot bootloader
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
Thanks for the great step by step tutorial.
I've tried to instal the Fastboot Image via the above guidem
1. Connect your Android device to computer via USB.
2. Ensure USB Debugging mode is ENABLED on Android device.
3. download adb driver
4. unzip adb driver and instal it
5. Extract the Minimal ADB and Fastboot Tool file to your PC
6. Download your RecoveryFile.img file or full fastboot Rom file and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ” so all files will be in single folder. (Which I've done with TOS319I Fastboot Image file)
7. open folder Minimal ADB and Fastboot, click on " open command window here "
8. Now type following command
adb fastboot
Unlocking the bootloader
adb reboot bootloader
fastboot reboot
Then, adb reboot bootloader
fastboot devices
*** But when I use the fastboot flash recovery TOS319I.img and to use the downloaded and renamed recover image, it says unable to load file TOS319I.img
Can you please let me know what should I do?
Thanks in advance
sellfy said:
Thanks for the great step by step tutorial.
I've tried to instal the Fastboot Image via the above guidem
1. Connect your Android device to computer via USB.
2. Ensure USB Debugging mode is ENABLED on Android device.
3. download adb driver
4. unzip adb driver and instal it
5. Extract the Minimal ADB and Fastboot Tool file to your PC
6. Download your RecoveryFile.img file or full fastboot Rom file and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ” so all files will be in single folder. (Which I've done with TOS319I Fastboot Image file)
7. open folder Minimal ADB and Fastboot, click on " open command window here "
8. Now type following command
adb fastboot
Unlocking the bootloader
adb reboot bootloader
fastboot reboot
Then, adb reboot bootloader
fastboot devices
*** But when I use the fastboot flash recovery TOS319I.img and to use the downloaded and renamed recover image, it says unable to load file TOS319I.img
Can you please let me know what should I do?
Thanks in advance
Click to expand...
Click to collapse
i know that you should use cyanogen os version rom of wileyfox storm (FIRST)
then you can flash custom rom or upgrade to official android 7 rom
that means , first you should downgrade to cyanogen 13
Again bootloop
ghertas said:
1.
Connect your Android device to computer via USB.
2.
Ensure USB Debugging mode is ENABLED on Android device.
Settings > About Phone > Build number > Tap it 7 times to become developer;
Settings > Developer Options > USB Debugging.
3.
download adb driver
http://adbdriver.com/downloads/
download Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
4.
unzip adb driver and instal it
http://adbdriver.com/documentation/...river-installer-for-windows-xp-vista-7-8.html
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
5.
Extract the Minimal ADB and Fastboot Tool file to your PC
6.
Download your RecoveryFile.img file or full fastboot Rom file
and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ”
so all files will be in single folder
7.
open folder Minimal ADB and Fastboot
in the folder , On your keyboard press SHIFT and right click with your mouse " Shift + right click "
click on " open command window here "
8.
Now type following command
adb fastboot
Unlocking the bootloader
Note: Using the fastboot command
When the fastboot command is used on the Storm, the vendor id command option must be added.
The vendor id for the Storm is 0x2970. For example, fastboot devices, would be fastboot -i 0x2970 devices.
Enable OEM unlock in the Developer options settings on the device.
(Note: Not all devices have this setting, so continue with next step if yours does not.)
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", try running fastboot as root.
From the same terminal, type the following command to unlock the bootloader:
fastboot -i 0x2970 oem unlock-go
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
fastboot reboot
Installing a custom recovery using fastboot
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
fastboot reboot
full rom fastboot
adb reboot bootloader
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
I've exactly followed your instructions for *"full rom fastboot"*, and all was done 'OK'. But Still the device is in bootloop and not going into recovery OR andriod system
ghertas said:
"full rom" was a zip file of cyanogen version
cyanogen realised two files of each rom
recovery version and fastboot version
if you want to install a custom rom on your device
Yes, I've download cyanogen Fastboot version, The only problem i've got is that my phone doesn't go into recovery mode although I've flashed TWRP also cn 13, but still the device only boots in fastboot only
When I select Recovery mode in Fastboot menu the device goes into bootloop.
Click to expand...
Click to collapse
idforpc said:
ghertas said:
"full rom" was a zip file of cyanogen version
cyanogen realised two files of each rom
recovery version and fastboot version
if you want to install a custom rom on your device
Yes, I've download cyanogen Fastboot version, The only problem i've got is that my phone doesn't go into recovery mode although I've flashed TWRP also cn 13, but still the device only boots in fastboot only
When I select Recovery mode in Fastboot menu the device goes into bootloop.
Click to expand...
Click to collapse
"fastboot reboot"
after boot the device , "Power off" the device and press volume down and power at the same time until you see the recovery on screen
"TWRP" is a custome recovery for install custom rom s
did you do all of those on " lineage wiki " ?
https://wiki.lineageos.org/devices/kipper/install
download the last version of twrp recovery
https://androidfilehost.com/?fid=1395089523397922500
Click to expand...
Click to collapse
Hello,
i really searched the whole web to bring my g4 in the diag mode to use QPSD but i find nothing. Maybe someone can help me?
i installed cm13 on a xt1622.
Greetz from Germany
Tyrantre said:
Hello,
i really searched the whole web to bring my g4 in the diag mode to use QPSD but i find nothing. Maybe someone can help me?
i installed cm13 on a xt1622.
Greetz from Germany
Click to expand...
Click to collapse
To enter diag mode, you need to put the phone into QCDiag mode. To do that you choose BPTools from bootloader (use up/down volume key) , then you press Start.
Once booted into BPtools, you will get 3 new unknown Moto G(4) devices in Windows Device Manager. You better have Mototrola's own software installed (https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481). If you do, you just select the first Moto G(4) and update driver > Let me Pick > Ports and ... > Select Motorola from list of manufacturers and set the driver on the right pane to the "QCDiag" one, guess the 4th or 5th item.
BTW: if you do the process more than once, order of unknown Moto G(4) devices get scrambled, so you just update driver for all 3!
MK+2017 said:
To enter diag mode, you need to put the phone into QCDiag mode. To do that you choose BPTools from bootloader (use up/down volume key) , then you press Start.
Once booted into BPtools, you will get 3 new unknown Moto G(4) devices in Windows Device Manager. You better have Mototrola's own software installed. If you do, you just select the first Moto G(4) and update driver > Let me Pick > Ports and ... > Select Motorola from list of manufacturers and set the driver on the right pane to the "QCDiag" one, guess the 4th or 5th item.
BTW: if you do the process more than once, order of unknown Moto G(4) devices get scrambled, so you just update driver for all 3!
Click to expand...
Click to collapse
Thanks for your fast reply!
I also thought that it will work like you told me, but i cant see the devices in devicemanager... I only see 1 entry of" Moto G(4)" in "portable devices" and one entry in "Andoid Devices" named "Motorola ADB Interface" ...
Maybe it wont work on win7 64 bit ?
And if i select: "boot in BP tools", is it normal that it boots the os as normally?
Search for "Qualcomm QPST Diag drivers", something like this:
http://forum.gsmdevelopers.com/showthread.php?t=6396
I installed the drivers you linked. But no devices are in my devicemanager..
Could it be a problem that i have not the stock firmware? i tried cm13 and lineageos14. At this time im downloading the stock firmware to test it.
I think that the g4 is not getting in the diag mode. Is there the possibility to see if its in the diag mode? I plugged the device in a nother computer. Also no DIAG USB device is detected. I should see the device as usb diag device in devicemanager even if the drivers are not installed or?
do you get in the diag mode with the g4 on cm13 or any other os?
I forgot where I too my drivers from, try different ones, from here even. The diag mode is functional, at least with stock bootloader and stock OS (ElementalX rooted).
PS: I don't flash TWRP, when I need it, I just load it up for that instance. I don't do anymore CM (Lineage), too many problems for me.
Did you try "adb reboot edl" from os, or "fastboot reboot-edl" from bootloader ?
Get root access on the phone and adb working.
adb shell
$ su
$ setprop sys.usb.config diag,adb
Device will disconnect/reboot probably. Now reconnect and see if the diag mode works and your phone shows as a COM port.
Else try changing the selinux status via the build.prop file (Sorry forgot the code) and then repeating the steps
vache said:
Did you try "adb reboot edl" from os, or "fastboot reboot-edl" from bootloader ?
Click to expand...
Click to collapse
It works, i did it from the os and the device rebooted. dont know what this mode is for, but i get in "Device Manager": Qualcomm HS-USB QDLoader 9008 (COM4).
But if i try to make a backup in QPST i got an error: "There is no Phone connected to the selected Port".. so i think its still not in diag mode. What is that mode for?
I also tried "setprop sys.usb.config diag,adb" but nothing happens in the phone.
Now i flash the original os and try it aggain. If it wont work, im at the end with my nerves :laugh:
EDIT:
Ok, i think to flash to stock rom with this guide:
3. Reboot your Moto G4 into the Bootloader Mode. To do so, turn off your phone and then press and hold the Volume Down & Power buttons simultaneously for a few seconds.
4. Connect your phone to your PC via USB cable.
5. Now, launch a command window from inside the ADB folder (where firmware files are saved). To do, click shift key, right click and select open command window here option).
6. In the command window, issue the following commands one by one:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
8. And, finally, reboot your device by issuing the below command:
mfastboot reboot
Your Moto G4 will reboot now. If you have unlocked Bootloader warning, then do the following:
Click to expand...
Click to collapse
but i got a bit fear because the command erase modemst1... isnt then my imei gone? ok, i first try to flash a custom stock rom from here
Else try changing the selinux status via the build.prop file (Sorry forgot the code) and then repeating the steps
Click to expand...
Click to collapse
ok, idont know what you mean with this :/
@Tyrantre what are you actually trying to accomplish using QPSD?
tywinlannister7 said:
@Tyrantre what are you actually trying to accomplish using QPSD?
Click to expand...
Click to collapse
Nothing special, just doing some backups and playing around with some things because last time i bricked my phone complete So for other software i need the diag mode too, and honestly it just get my angree that it not work on my phone.
EDIT:
Maybe you know a kernel or rom where you are sure you can load in diag mode?
tywinlannister7 said:
$ setprop sys.usb.config diag,adb
Click to expand...
Click to collapse
That doesn't work on Moto. Only the boot menus work.
PS: I use this mode to change the LTE bands (add band 20 on the US). It "took" the required change (not like Asus Zenfone Laser 2), but when tested in EU, it didn't really work. You need QXDM also, besides the QPST.
SoNic67 said:
That doesn't work on Moto. Only the boot menus work.
PS: I use this mode to change the LTE bands (add band 20 on the US). It "took" the required change (not like Asus Zenfone Laser 2), but when tested in EU, it didn't really work. You need QXDM also, besides the QPST.
Click to expand...
Click to collapse
Thanks!
now i figured out that the Diag mode seems to work only in the "stock rom" by choosing BP TOOLS.. I got the 3 unknown devices now. I test arround and will make an update if i get it to run. But it looks better now
Ok now it works till the point where i can do a backup in qpst. But if i want to restore the backup it just dont start and gives an error that it became a error.
could it be that there is a write protection on the modem partition and i have first to clean the modem partition? Or is it a bad idea?
Ok, im now a bit sure that there is a write protection. So if i want to change/add bands to the modem in NV Manager or try to recover a qpst backup, it wont work. Is there a way to make the partition writeable?
i reade in an other guide, that there is a way to restore the qpst backup. I have to delete some modem partitions:
This is the inside of your Snapdragon 820/821 based Xiaomi. Only 3 part form here matters for us, modemst1, modemst2 and fsg, those the partititions hosting your baseband and imei info (not all Snapdragons, but most Chinese made Qualcomms). Please keep in mind, this is very important, numbers are variable depending on the phone model, so names are important for us, not numbers, don’t try these numbers on a phone other then Mi 5 series, just list your parititon table and look for modemst1, modemst2 and fsg. Let’s zero/emty these 3 partitions :
dd if=/dev/zero of=/dev/block/sdf3
dd if=/dev/zero of=/dev/block/sdf5
dd if=/dev/zero of=/dev/block/sde28
reboot
Click to expand...
Click to collapse
after this it should works. But i fear to try this, because i fear to loose my imei ect. for ever. Is there a way to backup the whole phone with all partitions up just to get save if something happens?
@SoNic67 , how do you changed the lte band? do you didnt got a error by writing to the phone with qpst? Do you done it with moto g4?
EDIT;;
Ok, deleting the modem Partitions works, but flashing after with qpst doesnt. and flashing with flashfire works too. But why no qpst? why can falshfire flash the partition and qpst cant?
I think you have to allow the writing in QPST. Never messed up with flashing the whole modem in QPST, just used it as as server (QPST Configuration) for changing the LTE with QXDM.
Ok, thanks for all help, i think its not possible becaus i couldnt find a way to to make those writeable..
tywinlannister7 said:
@Tyrantre what are you actually trying to accomplish using QPSD?
Click to expand...
Click to collapse
repair imei as an example. isnt there a way to make it writeable?
Tyrantre said:
repair imei as an example. isnt there a way to make it writeable?
Click to expand...
Click to collapse
Actually I tried using QPSD for writing the IMEI on my mum's (apparently mine) Xiaomi RedMi Note 4G (dior) usong that .qcn file method. But it failed to write. Another thing what I tried was flashing CM 13 on it amd followed by Xposed Framework...using a module for changing IMEI I was able to write the IMEI successfully. But alas, the baseband of the phone was lost too, so IMEI writing was useless in my case.
IMEI change is illegal. And unethical because it affects other people phone too (the one that you clone the IEMI).
SoNic67 said:
IMEI change is illegal. And unethical because it affects other people phone too (the one that you clone the IEMI).
Click to expand...
Click to collapse
Ok, i thought and just waited for the point when someone post that this is illegal. It´s just illegal if i change it to an other number, just repairing it and changing it to its own imei is not. So second, why everybody makes such a big deal that it is illegal to change the imei? In times where you are so fast a political enemy in some countrys i think it could be usefull for many people. (not in my case, Germany best country in the world )
Im at the point where i thinks that there is no way to "restore" the imei of the moto g4 without using somekind of flashbox ect. So i look out to buy an other phone to play around with Thanks for al the help, learned much
i downloaded factory image of 7.12.29 oreo
i used flash_factory.bat
it reflashed partitioning
apparently it had a command "fastboot flash modem_a NON-HLOS.bin"
the NON-HLOS.bin file does not exist in images folder nor in any fastboot rom
now i dont have any connectivity... signal.. wifi etc..
can anybody provide NON-HLOS.bin file for the A1
Hello,
Inside the fastboot ROM file "tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz" (Nougat 7.1.2) ... in the file "flash_all_lock_crc.bat" for example, these lines appear:
fastboot %* flash modem_a %~dp0images\modem.img || @ECHO "Flash modem_a error" && exit /B 1
fastboot %* flash modem_b %~dp0images\modem.img || @ECHO "Flash modem_b error" && exit /B 1
It seems that the file is called "modem.img", not "NON-HLOS.bin".
May be?
Regards!
PS: Sorry for my English!
i managed to flash all images from fast boot to partitions manually step by step
except something called fsg and persist partitions
which i managed to flash through twrp using dd command via terminal
now it boots but i dont have imei number "says imei number unknown"
and it reboots after less than a minute
i read something about qcn file restore and editing from another mi A1
and that i can edit it to put my imei numbers back
anybody please provide a valid qcn number and how can i restore it
m.hashem said:
i managed to flash all images from fast boot to partitions manually step by step
except something called fsg and persist partitions
which i managed to flash through twrp using dd command via terminal
now it boots but i dont have imei number "says imei number unknown"
and it reboots after less than a minute
i read something about qcn file restore and editing from another mi A1
and that i can edit it to put my imei numbers back
anybody please provide a valid qcn number and how can i restore it
Click to expand...
Click to collapse
if it is under warranty just brick your phone and give it to service centre they will flash it and give you back
m.hashem said:
i downloaded factory image of 7.12.29 oreo
i used flash_factory.bat
it reflashed partitioning
apparently it had a command "fastboot flash modem_a NON-HLOS.bin"
the NON-HLOS.bin file does not exist in images folder nor in any fastboot rom
now i dont have any connectivity... signal.. wifi etc..
can anybody provide NON-HLOS.bin file for the A1
Click to expand...
Click to collapse
i have same problem last night
then i reflash 7.12.19 using miflash 2016.08.30.0
my imei normal again
Wow! The file NON-HLOS.bin is the modem for other Xiaomi phone. May be you use a batch file (flash_factory.bat) for other phone, not Mi A1. Please use Mi Flash with right rom.
this is method not working
bangir said:
i have same problem last night
then i reflash 7.12.19 using miflash 2016.08.30.0
my imei normal again
Click to expand...
Click to collapse
this is method not working
gautamaurya said:
this is method not working
Click to expand...
Click to collapse
What happens if you try to re-flash your modem with the flash_all or flash_all_except_storage scripts from here: https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929 ?
Can you please report, if it works and if should not work, please attach the terminal/ shell outpout of the failed flashing attempt here.
modemst1 and modemst2
hey ... i managed to flash the fastboot rom via miflash via hsusb 9008 mode through miflash tool (run as administrator)
the remainig problem is 2 partitions modemst1 and modemst2
which are dev/block/mmcblk0p14 & 15 respectively
can somebody please send me a backup of modemst1 and modemst2
it's doable via twrp
fastboot boot twrp3.1.1.1.img
advanced
terminal
dd if=/dev/block/mmcblk0p14 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p15 of=/sdcard/modemst2.img
i'll flash them back and edit the imei numbers via hex after qcn backup
thanks everybody
m.hashem said:
hey ... i managed to flash the fastboot rom via miflash via hsusb 9008 mode through miflash tool (run as administrator)
the remainig problem is 2 partitions modemst1 and modemst2
which are dev/block/mmcblk0p14 & 15 respectively
can somebody please send me a backup of modemst1 and modemst2
it's doable via twrp
fastboot boot twrp3.1.1.1.img
advanced
terminal
dd if=/dev/block/mmcblk0p14 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p15 of=/sdcard/modemst2.img
i'll flash them back and edit the imei numbers via hex after qcn backup
thanks everybody
Click to expand...
Click to collapse
I have done some digging in order to assist you to get this fixed. I think I have 2 very hot leads (untested as I don't have any issues with my IMEI):
1. http://www.androidbrick.com/ultimat...agon-xiaomi-mi5-imei-and-baseband-repair-fix/ & http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/
2. https://androidmtk.com/use-qualcomm-smartphone-write-imei-tool (looks almost to easy, but worth a try?)
Please report your feedback here
hey bro how to the editting modem1st.img
m.hashem said:
i downloaded factory image of 7.12.29 oreo
i used flash_factory.bat
it reflashed partitioning
now i dont have any connectivity... signal.. wifi etc..
Click to expand...
Click to collapse
Hello!
I made the same mistake. Is there a way to solve this problem?
m.hashem said:
i downloaded factory image of 7.12.29 oreo
i used flash_factory.bat
it reflashed partitioning
apparently it had a command "fastboot flash modem_a NON-HLOS.bin"
the NON-HLOS.bin file does not exist in images folder nor in any fastboot rom
now i dont have any connectivity... signal.. wifi etc..
can anybody provide NON-HLOS.bin file for the A1
Click to expand...
Click to collapse
Same problem here. Phone doesn't work correctly now. Boots, freezes and reboots. :crying:
persist image problem
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
try ghis to restore persist img from twrp see if it fixes the freeze and reboot problem
also download the persist.img from the guide not from a fastboot rom... it should be 32 mb in size
i actually bricked my phone via doing fastboot flash partition partition-both-gpt.bin from fastboot folder then fastvoot reboot.... warning this bricks the phone completely... theres no bootloader now... i gave it to service center... ill take my chances for replacement
m.hashem said:
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
try ghis to restore persist img from twrp see if it fixes the freeze and reboot problem
also download the persist.img from the guide not from a fastboot rom... it should be 32 mb in size
i actually bricked my phone via doing fastboot flash partition partition-both-gpt.bin from fastboot folder then fastvoot reboot.... warning this bricks the phone completely... theres no bootloader now... i gave it to service center... ill take my chances for replacement
Click to expand...
Click to collapse
thank you very much broo my device is fixed freezee and reboots problem
Ok. But what is the persist partition? Someone tried already? Doesn't want to brick my phone completely.
how to the editting qcn file beacuse my imei 0 null please help me editting brother
m.hashem said:
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
try ghis to restore persist img from twrp see if it fixes the freeze and reboot problem
also download the persist.img from the guide not from a fastboot rom... it should be 32 mb in size
i actually bricked my phone via doing fastboot flash partition partition-both-gpt.bin from fastboot folder then fastvoot reboot.... warning this bricks the phone completely... theres no bootloader now... i gave it to service center... ill take my chances for replacement
Click to expand...
Click to collapse
The freeze and reboot problem is fixed. Thanks. Still one problem. IMEI1 is 0 and IMEI2 is null. Anyone has an idea?
Nordland_ua said:
Hello!
I made the same mistake. Is there a way to solve this problem?
Click to expand...
Click to collapse
Me tooo
Sent from my Mi A1 using Tapatalk
https://www.androidfilehost.com/?fid=673956719939818468
Replace the IMEi with UR Own IMEI . if not it's illegal to use this QCN
Password : testnreport
if you don't know how to change IMEI Using hex editor , try my method . DO NOT use QCN to restore .
(hex and imei provided in order for u to find n replace)
i lost my imei n spent me about 6days n 8 hours per day to find a way to fix it .
actually it's easy to fix the problem .
My own method
1. download the older rom (7.8.23) Link
2. Use flash_all.bat
3.reboot into fastboot mode , erase modemst1 and modemst2 .
fastboot erase modemst1
fastboot erase modemst2
4. reboot
5. go to phone , enter *#*#717717#*#*
6.got to settings enable USB Debugging (ADB)
7. disconnect your phone n connect it back
8.Use WriteDualIMEI(W+G_eMMC) Remember run as administrator , enter your IMEI .
9.if success , go to phone enter *#*#717717#*#* to disable the diag port
10. reboot
Done .