At first Volte was not working for me in cm ROM, after fooling around I got it working.
****** If something breaks I am not responsible
*-*-*-*-*- But this is simple it shouldn't break your Kenzo
Prerequisite ::::::
1. Working MIUI ROM ( to take backups)
2. ADB and fastboot.
3. Working knowledge of how to fastboot and all.
Steps :::
1. Reverted back to miui.
2. Make sure you have working su.
3. Install imei+efs backup app by wanam from play store ( or any other backup app you like.)
4. Take following backups
a. modem
b. modemst1
c. modemst2
d. fsg
5. You might get .tar.gz files. ( if you have .img files skip next step.
6. Copy .tar.gz files to PC and extracte. You will get .img of above files.
7. Now flash any CM 14.1 ROM ( with working Volte) you like.
8. Check if you got volte....... NO then follow next step.
9. Boot into fastboot
10. Copy all .img file (i.e. modem,modemst1,modemst2 and fsg ) to folder where you have fastboot and adb files. ( adb, AdbWinApi.dll, AdbWinUsbApi.dll, fastboot)
11. Then used these commands to flash
fastboot flash modem modem.img
fastboot flash modemst1 modemst1.img
fastboot flash modemst2 modemst2.img
fastboot flash fsg fsg
12. Reboot
Voilllaaaa. VOLTE working.
(P.S. don't make spelling mistake in modemst1 and modemst2 ...,.. That's how I lost my IMEI numbersnumbers..... But again I had backup.)
Hope it will solve some members problem.
Does it work with latest MM modems?
This works . Deserves more views!!
Sent from my Redmi Note 3 using Tapatalk
I can't seem to be able to use the app to backup anything. the partitions don't even show up in the app.
Edit:- Extracted files using another method. Doesn't work for the latest modems.
[email protected] said:
Steps :::
1. Reverted back to miui.
Click to expand...
Click to collapse
Revert back to miui LP or MM? Or both should work?
Jaskirat singh said:
Revert back to miui LP or MM? Or both should work?
Click to expand...
Click to collapse
MM
Related
FIRST OF ALL
(Also for downgrading to KitKat without softbricked phone!)
Okay, I decided to do the OTA to lollipop, everything went fine. So after some use I decided to play with the /system partition. I formatted it without making a working backup so my phone was kinda softbricked. REMEMBER THIS THREAD IS NOT FOR HARDBRICKED BOOTLOADERS, you guys have to wait.
SO WHAT TO DO?
1. Plug your phone into fastboot in your pc.
2. Flash a custom recovery, like CWM, I know you'll have a screen rimble effect due the new bootloader (doesn't matter)
3. Open recovery and keep it plugged into PC, recovery will have adb on by default so leave recovery as it is.
4. Open CMD and type:
Code:
cd directory-with-adb.exe-and-fastboot.exe-etc.
(I assume that you guys know how to use adb and fastboot with CMD)
5. Type:
Code:
adb devices
6. Your Moto's serial number should show up in the attached devices list (serialnumber, recovery), if not download the driver installer from http://adbdriver.com
7. Now download a firmware flashable zip to the directory in your CMD (CyanogenMod or stock firmwares from here)
8. Now you have to make sure you are able to mount the /sdcard in recovery: To make sure do a /data and media wipe. (Also helps on GPe ROM and the encryption problem!)
9. Now you can push the downloaded zip to the phone's sdcard using:
Code:
adb push yourrom.zip /sdcard/yourrom.zip
It will take some time.
10. Now you can install but you may face a not working SIM or WiFi, you need to download a .xml.zip firmware corresponding to your just flashed version. Navigate to your firmware folder using CMD. Then type:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
11. Now your phone should work. You will have that annoying screen rimble. Sometimes it's gone, just turn screen off for a few minutes. It will be fixed when you install the stock recovery and then flash an lollipop OTA zip just like before! (OTA's will still show up and works with updating )
WARNING!
SOME GUYS MADE A HUGE MISTAKE AND BRICKED THEIR BOOTLOADER. THEY FLASHED LOLLIPOP OTA, THEN DOWNGRADED TO 4.4.2 AND THEY TRIED TO UPDATE TO 4.4.4 BY OTA!
THAT RUINED THE BOOTLOADER SEE BELOW!
FOR HARDBRICKED DEVICES
You ruined your bootloader, we need a mbm-ci (blankflasher tool) with the 5.0 bootloader. We have to wait till Motorola releases it. So no support yet.
Sorry guys, that was the risk!
HOPE YOU GUYS LIKE THIS TUTORIAL!
Thanks for the guide.
restore
GI0\/\NNI said:
FIRST OF ALL
Okay, I decided to do the OTA to lollipop, everything went fine. So after some use I decided to play with the /system partition. I formatted it without making a working backup so my phone was kinda softbricked. REMEMBER THIS THREAD IS NOT FOR HARDBRICKED BOOTLOADERS, you guys have to wait.
SO WHAT TO DO?
1. Plug your phone into fastboot in your pc.
2. Flash a custom recovery, like CWM, I know you'll have a screen rimble effect due the new bootloader (doesn't matter)
3. Open recovery and keep it plugged into PC, recovery will have adb on by default so leave recovery as it is.
4. Open CMD and type:
Code:
cd directory-with-adb.exe-and-fastboot.exe-etc.
(I assume that you guys know how to use adb and fastboot with CMD)
5. Type:
Code:
adb devices
6. Your Moto's serial number should show up in the attached devices list (serialnumber, recovery), if not download the driver installer from http://adbdriver.com
7. Now download a firmware flashable zip to the directory in your CMD (CyanogenMod or stock firmwares from here)
8. Now you have to make sure you are able to mount the /sdcard in recovery: To make sure do a /data and media wipe. (Also helps on GPe ROM and the encryption problem!)
9. Now you can push the downloaded zip to the phone's sdcard using:
Code:
adb push yourrom.zip /sdcard/yourrom.zip
It will take some time.
10. Now you can install but you may face a not working SIM or WiFi, you need to download a .xml.zip firmware corresponding to your just flashed version. Navigate to your firmware folder using CMD. Then type:
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
11. Now your phone should work. You will have that annoying screen rimble. Sometimes it's gone but not sure. It will be fixed when you install the stock recovery and then flash an lollipop OTA zip just like before! (OTA's will still show up and works with updating )
FOR HARDBRICKED DEVICES
You ruined your bootloader, we need a mbm-ci (blankflasher tool) with the 5.0 bootloader. We have to wait till Motorola releases it. So no support yet.
Sorry guys, that was the risk!
HOPE YOU GUYS LIKE THIS TUTORIAL!
Click to expand...
Click to collapse
thanks for this guide
but my phone is not bricked ,can i downgrade 5.0 to 4.4.4
because my moto g is asian retail, i already installed brasil firmware and ota file
mostwantedxda said:
thanks for this guide
but my phone is not bricked ,can i downgrade 5.0 to 4.4.4
because my moto g is asian retail, i already installed brasil firmware and ota file
Click to expand...
Click to collapse
Yeah just follow guide!
Hi I have updated my Asian XT 1033 to brazil 5.0 but experienced NO NETWORK on both the sim cards... and now i downgraded to my asian 4.4.4 but still NO NETWORK on both sim cards... Please help .... m worried ;(
Imei vanished
My imei numbers are vanished.... Please help me... is there any thing i can do now??
hunterhere said:
Hi I have updated my Asian XT 1033 to brazil 5.0 but experienced NO NETWORK on both the sim cards... and now i downgraded to my asian 4.4.4 but still NO NETWORK on both sim cards... Please help .... m worried ;(
Click to expand...
Click to collapse
Flash 4.4.4
NON-HLOS.bin
fsg.mbn
Read the guide!
hunterhere said:
My imei numbers are vanished.... Please help me... is there any thing i can do now??
Click to expand...
Click to collapse
@hunterhere,
I think I found a solution!
1. Download and extract zip
2. Connect phone in fastboot mode to your PC
3. Run IMEI_fix_gio.bat
4. Should work now!
first of all i dont know where to ask this Q
after i downgrade to 4.4.4 with the guide will i be able to flash CM12 or my phone will be dead?
poran123 said:
first of all i dont know where to ask this Q
after i downgrade to 4.4.4 with the guide will i be able to flash CM12 or my phone will be dead?
Click to expand...
Click to collapse
after downgrading from 5.0 i was able to flash any rom STOCK 4.4.4 of any region and 5.0 too again... so according to this u shld be able to flash....
poran123 said:
first of all i dont know where to ask this Q
after i downgrade to 4.4.4 with the guide will i be able to flash CM12 or my phone will be dead?
Click to expand...
Click to collapse
You can flash without problems. Promise!
hunterhere said:
after downgrading from 5.0 i was able to flash any rom STOCK 4.4.4 of any region and 5.0 too again... so according to this u shld be able to flash....
Click to expand...
Click to collapse
did you try any CM roms?
---------- Post added at 01:16 PM ---------- Previous post was at 01:15 PM ----------
GI0\/\NNI said:
You can flash without problems. Promise!
Click to expand...
Click to collapse
thanks for confirming ..:good:
Adb drivers not recoganizing.
when i plug in the phone some drivers get installed.
but my phone is not showing up in adb devices.
i flashed CMW & am running Windows 10 x64
Help!!!!!
I have XT1033 and i was on brazilian 5.0 soak test, after that i convert my phone to downgrade to gpe 4.4.4 and everything was fine but then i wanted to go back to stock 4.4.4 brazilian and now im stuck at the boot logo.
these are the commands i used to convert from 5.0 brazilian soak test to gpe 4.4.4
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
and these are the commands i used to convert from gpe 4.4.4 to stock brazilian 4.4.4
SET fastboot=fastboot.exe
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe reboot-bootloader
fastboot.exe continue
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
fastboot.exe reboot
exit
did i softbricked my phone or hardbricked ?
brick my moto g
My motog is brick , I updated to 5.0 and shifted in build.prop file, not launched yet , I could not successfully restore it then installed the rom 4.4.2 , then updated to 4.4.3 and when he went to 4.4.4 he gave brick and does not want to , what I do?
I'm desperate since yesterday :crying:
Lucas Amaral said:
My motog is brick , I updated to 5.0 and shifted in build.prop file, not launched yet , I could not successfully restore it then installed the rom 4.4.2 , then updated to 4.4.3 and when he went to 4.4.4 he gave brick and does not want to , what I do?
I'm desperate since yesterday :crying:
Click to expand...
Click to collapse
i'm with you, brother....i have same problem...waiting for solution
Lucas Amaral said:
My motog is brick , I updated to 5.0 and shifted in build.prop file, not launched yet , I could not successfully restore it then installed the rom 4.4.2 , then updated to 4.4.3 and when he went to 4.4.4 he gave brick and does not want to , what I do?
I'm desperate since yesterday :crying:
Click to expand...
Click to collapse
Did you read first page before flash? It s clearly stated there that some ppl bricked phones when flashed 4.4.2 then upto 4.4.3 and so on. Please next time read all that its writed...
ganeshkmr21 said:
when i plug in the phone some drivers get installed.
but my phone is not showing up in adb devices.
i flashed CMW & am running Windows 10 x64
Click to expand...
Click to collapse
Read OP, install adbdriver!
não-soi-jo said:
I have XT1033 and i was on brazilian 5.0 soak test, after that i convert my phone to downgrade to gpe 4.4.4 and everything was fine but then i wanted to go back to stock 4.4.4 brazilian and now im stuck at the boot logo.
these are the commands i used to convert from 5.0 brazilian soak test to gpe 4.4.4
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
and these are the commands i used to convert from gpe 4.4.4 to stock brazilian 4.4.4
SET fastboot=fastboot.exe
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe reboot-bootloader
fastboot.exe continue
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
fastboot.exe reboot
exit
did i softbricked my phone or hardbricked ?
Click to expand...
Click to collapse
Just follow the guide! Flashing with fastboot won't work so flash custom recovery and push a 4.4.4 stock zip.
Lucas Amaral said:
My motog is brick , I updated to 5.0 and shifted in build.prop file, not launched yet , I could not successfully restore it then installed the rom 4.4.2 , then updated to 4.4.3 and when he went to 4.4.4 he gave brick and does not want to , what I do?
I'm desperate since yesterday :crying:
Click to expand...
Click to collapse
READ OP! You didn't read it properly so you made a huge mistake!
MadL1fe said:
i'm with you, brother....i have same problem...waiting for solution
Click to expand...
Click to collapse
Same... You should have read the OP!
samsontm said:
Did you read first page before flash? It s clearly stated there that some ppl bricked phones when flashed 4.4.2 then upto 4.4.3 and so on. Please next time read all that its writed...
Click to expand...
Click to collapse
Totally agree with you....
I did that last part... :\ Guess I'll wait for Moto.
GI0\/\NNI said:
@hunterhere,
I think I found a solution!
1. Download and extract zip
2. Connect phone in fastboot mode to your PC
3. Run IMEI_fix_gio.bat
4. Should work now!
Click to expand...
Click to collapse
Hey I flashed this file now the change is that previously my both the IMEI(S) were showing 0 now 1st one is showing 0 but 2nd one has changed to null.
Secondly i request you to please come and join the below mentioned thread and please please help us all who have erased IMEI(S) with your knowledge and skills.
http://forum.xda-developers.com/moto-g/help/info-moto-g-imei0-t2925970
Edit: can you help in telling me how you modified this fsg_gio.img file? Or if you have got it from somewhere else please point...
As it is a very important file and a developer on above mentioned thread needs to know how this file got modified this will lead us further in restoring the imei numbers... as because moto g is made in a very different way... there is a lot of encryption done in its partitions which is very difficult to decrypt.
so i did a restore to stock for the moto x pure on my style, and everything works; however, wifi does not turn on, the *#*#4636#*#* menu says that the supplicant is uninitialized, is there anything i can do to get it working again?
running ifconfig tiwlan0 returns no such device
I have root and twrp installed.
Having same issue. Restored stock and without root it works. After installing root the same problem occurred
search the site for the firmware. Download the firmware page and look for the file non-hlos.bin. Do the fastboot method but UNCAPS it. The file is in CAPS, rewrite the thing in lower case.
You may also have to flash the NON-HLOS.bin multiple times, it took me 3 flashes to get it to finally flash properly (There is no way to determine if it worked without booting android).
Go to your fastboot files folder
Open notepad
Paste this:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
Save it like flashmodem.bat in adb folder
Take from original decompressed ROM
NON-HLOS.BIN & fsg.mbn and copy those files in adb folder with the bat file.
Run it
Enjoy
Remember to remove your sim card
nitros12 said:
so i did a restore to stock for the moto x pure on my style, and everything works; however, wifi does not turn on, the *#*#4636#*#* menu says that the supplicant is uninitialized, is there anything i can do to get it working again?
running ifconfig tiwlan0 returns no such device
I have root and twrp installed.
Click to expand...
Click to collapse
zakoda said:
Having same issue. Restored stock and without root it works. After installing root the same problem occurred
Click to expand...
Click to collapse
Restore your stock backup and flash SuperSU 2.62 this should give you root and no problems with wifi.
After flashing 2.62 you can flash the latest SuperSU.
[email protected] said:
Restore your stock backup and flash SuperSU 2.62 this should gif you root and no problems with wifi.
After flashing 2.62 you can flash the latest SuperSU.
Click to expand...
Click to collapse
Forgot to update my post, solved by flashing the stock ROM and then flashing whatever I wanted on top
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 .
Have a problem flashing through Fastboot and then boot and only have warning bootloader unlocked ...
any solutions?
flash twrp for nougat and /data no get mounth...
any to help?
More info?
Screenshots from pc?
What & how did you flashed?
Update...
Flash manually every file of the firmwares and all works fine!
Really have problem to flash MM modem ...
can me provide lastest mm modem and comand to flash?
delete
bad conexion
andreskafe said:
Update...
Flash manually every file of the firmwares and all works fine!
Really have problem to flash MM modem ...
can me provide lastest mm modem and comand to flash?
Click to expand...
Click to collapse
Download highest MM, extract non-hlos, copy it to adb-fastboot folder.
If you didn't lock bootloader:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
/Repeat commands until you see OK/
Boot into twrp and install mm based custom rom.
dzidexx said:
Download highest MM, extract non-hlos, copy it to adb-fastboot folder.
If you didn't lock bootloader:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
/Repeat commands until you see OK/
Boot into twrp and install mm based custom rom.
Click to expand...
Click to collapse
Ok. Thanks.
Twrp for Nougat is compatible with MM roms?
andreskafe said:
Ok. Thanks.
Twrp for Nougat is compatible with MM roms?
Click to expand...
Click to collapse
Yes.
I wrote "MM based custom roms" - I meant custom 7.1.2 for MM modem.
dzidexx said:
Download highest MM, extract non-hlos, copy it to adb-fastboot folder.
If you didn't lock bootloader:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
/Repeat commands until you see OK/
Boot into twrp and install mm based custom rom.
Click to expand...
Click to collapse
Sorry. But no works for me.
My Moto is not signal after flash MM modem and need re flash the firmware!
I use this comand
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
Thanks!
andreskafe said:
Sorry. But no works for me.
My Moto is not signal after flash MM modem and need re flash the firmware!
I use this comand
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
Thanks!
Click to expand...
Click to collapse
After these commands you need to install custom rom, stock will not work.
dzidexx said:
After these commands you need to install custom rom, stock will not work.
Click to expand...
Click to collapse
I restore my nandroid backup...
Only way is flash custom ROM?
andreskafe said:
I restore my nandroid backup...
Only way is flash custom ROM?
Click to expand...
Click to collapse
I restore my nandroid backup of custom rom
You flashed stock Nougat,
After it u flashed MM modem - stock N will not work - you should install custom for MM modem.
/Twrp's backup don't include modem/.
Hello.
I had serial rom with all updates (non-touched nougat 7.1.1 europe). The phone became slow and laggy. Had a dream to restore lollipop to go back to geatest time of the moto x play.
Unlocked bootloader with motoroloa website and code sent on email. Installed recovery twrp 3.2.1-r1.
Roms tried:
Lollipop zips
LPH_v1.1_DS_by_Eska
LPH_v1.0_DS_by_Eska
Marshmallow zips
24.107-70-1_Debloated-lux_2.0.0 (Stock Debloated VoLTE)
SpetrumMM_VoLTE-lux_5.6.0
Nougat zips
DOT-N-v1.2-20180219-lux-OFFICIAL ( [OFFICIAL][LUX][7.1.2][V-1.2]DOT-OS [Smoothest OS] by Sharan
and finally one, that worked: PIXEL+DARK+OS+V11
and second: [ROM][7.1.2][lux][OMS] ViperOS v3.1.1
What is the reason I can't install any rom beside 2 last of them?
Process with not working roms looks similar. After wiping, installing and reboot, only boot logo image changed and sometimes showed second animated logo with no further results (even if waited many minutes )
Are you using the "stock" gapps? They take a long time to boot. Try using pico, and if not, you can revert to an earlier version by flashing each file through fastboot.
Also, the stock-based roms already have gapps. There is no need to install gapps and it may cause issues.
First, extract your stock rom zip.
(This should work for any stock rom, and will not brick your phone unless you make a mistake. However, as always, I take no reliability for your broken phone)
1. Extract stock rom
2. Reboot phone into download mode/bootloader/fastboot mode.
3. Type these commands:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.((((number)))) <-- FOR EVERY FILE LIKE THIS WITH THE NUMBER AFTER IT!!!!!
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
Then reboot.