Related
hi how are you
I have a problem with the phone ls980 . It updated the wrong way and I have a fastboot problem
But I fixed it with srktool . Process and has successfully
now the download mode work good but When I have flash this phone withe tot file and dll file ( ls980 )
the flash tool show me error 'laf read gpt' on 6%
I have to use everything but the same thing happened
- Using a new file dll LGUP_8974 but no think hapend
- using a new tot file but same probleme
- When in use fastboot mode and flash or erase any partition like lif.recovery.... the cmd show me error message ' remote: failed to erase partition'
I've used all the solutions of the sites but same problem ' laf read gpt failed ' in flashtool
Please help before I will break this phone plz plz plz
sorry for bad english
Plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
Plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz
Greetings,
I have an XT1562 which I attempted to flash cm13 on but I was stuck in a bootloop. I read somewhere that using fastboot erase all would fix this problem and indeed it did but at the cost of setting my IMEI to 0. The getvar imei command returns the correct IMEI value. I tried reflashing the modem, reverting to stock, QPST (device manager couldn't detect the COM port) and using dd from TWRP terminal to overwrite hob, dhob and fsc with similar files I found for Moto G. This somewhat helped by restoring 2G functionality but only lasted until reboot. At this point, I am out of ideas, so any assistance is immensely appreciated.
AegisBg said:
Greetings,
I have an XT1562 which I attempted to flash cm13 on but I was stuck in a bootloop. I read somewhere that using fastboot erase all would fix this problem and indeed it did but at the cost of setting my IMEI to 0. The getvar imei command returns the correct IMEI value. I tried reflashing the modem, reverting to stock, QPST (device manager couldn't detect the COM port) and using dd from TWRP terminal to overwrite hob, dhob and fsc with similar files I found for Moto G. This somewhat helped by restoring 2G functionality but only lasted until reboot. At this point, I am out of ideas, so any assistance is immensely appreciated.
Click to expand...
Click to collapse
Flashing the stock rom should have solved this problem.
Sent from my XT1562 using Tapatalk
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
Hello,
My Asus ze550kl m8916
Snapdragon 410 2gb/16gb model
is hardbrick
It is still in locked state
However, I have used QFIL using Test Point and managed to reach Fastboot Mode
When I flashed TWRP it always Reboot
I can flash all the firmwares files even in locked state using
Emmc RAW tool
But ai need the Working Dump flash file
Can anyone help me?
Download the EMMC Raw Tool
Boot into Download mode Q9006 mode) and dump the Firmware Only
this include
1.ASDF, SEC, sbl1, hyp, tz, aboot, adf, Asusfw, asusgpt1, 2, Asuskey, asuakey2, 3,4,5, boot, cache, config, ddr, devinfo, factory, fsc, gaps#1, keystorre, mbr-gpt-other, misc, modem, modemstr1, modrmstr2, oem, presist, persistent, recovery, splash, ssd,
You can dump all these files using emmc raw tool while in Q9006 Mode..
To be in q9006 mode just flash the wrong emmc_aboot to your phone
you'll be in q9006 mode
to get back on track install the correct emmc_aboot.mbn file again
OR
you can dump your Firmware using root
adb shell command
dd if=/dev/........ of=/sdcard
if u need help in How to dump these files to your memory card or internal storage, Reply I'll help u how to dump
Please send me the files after you're dump
Contact me on what app +918974796939 if u r willing to help me
Let's learn things together
Can anyone help me. with this?.?
Thanks a lot in advance
Just take it to service centre I think you got a flash lock on your partition (just assuming). I have a custom ROM so if you want I can send you the dump files.
Hello.
What are the test points you connected?
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 .