Related
Hi
I had installed NamelessRom along with the unified storage layout. All was working smoothly and then I was getting random freezes.
Only way to avoid was to revert back to stock ColorOs. Now however I have the 48mb problem with the partition. On top of that, I can't boot to recovery, it just goes to fastboot. I have tried running the swaplayout.bat partition tool again, but the phone just stays on fastboot for half an hour at least.
Is there any way that I can install NamelessRom again and see if it recognises the unified layout from the first boot?
Any help would be greatly appreciated. Virtual hugs and beers await...
I had the same problem.
download colorOS 1.2.7i and extract the zip
in adb
fastboot flash boot boot.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash LOGO logo.bin
fastboot flash reserve4 reserve4.img
if your bootloader is locked
Fastboot oem unlock
here is a stock oppo recovery that will handle colorOS1.2.7.i install. http://s000.tinyupload.com/file_upl...3653419942379&del_id=58779725699588589872&gk=
TWRP recovery to remove LVM
Custom ROMS cause random reboots for me. I'm stuck on coloros 2 beta but that is stable. I really want Nameless LVM unified though.
i have a oppo find 7 a year and since then I did to the root, but today decided to change rom but something went wrong because now he is always the restart and go to the screen of fastboot ? I can do is urgent ...
The rom and I put SlimSaber - find7-5.1.1-20150926 find 7
Hello.
Use "fastboot oem unlock", then flash recovery again and everything should work.
Regards.
Hei kucici a link to donwload please?
Hello. I already have an oppo find 7 for a year and I've root it and changed its rom twice. Last rom was color os 1.2.7 and I've changed it to SlimSabet find 7-5.1.1-20150926 find 7 and all went right but when it was 100% the phone reset and it was like you can see in the picture above.
The problem now is that my pc windows 7 has no conection to my oppo find 7. In the device manager it appears android phone and below alcatel adb interface. I can't do the connection between my pc and the oppo and I can't do the recovery.
I always had smartphones, but as it is the first time I have one with windows os and the first time I do this kind of stuff to an android I'm a bit confused...
My oppo is like thart for two weeks now and I don't know what else to do. I've searched in a lot of foruns, but no one has a solution for my problem. Can anybody help me, please?
THANK YOU
darrenpauli said:
I had the same problem.
download colorOS 1.2.7i and extract the zip
in adb
fastboot flash boot boot.img
fastboot flash aboot emmc_appsboot.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash LOGO logo.bin
........=[/url]
TWRP recovery to remove LVM
Custom ROMS cause random reboots for me. I'm stuck on coloros 2 beta but that is stable. I really want Nameless LVM unified though.
Click to expand...
Click to collapse
YOU MADE MY DAY...... Thank you so much, everything works again.
Hi,
I am currently running Cyanogen OS 13.0 and I have not managed to update via OTA and TWRP. After TWRP-Update the system just hangs on boot. OTA just does not do the update after reboot. I just keeps downloading the OTA-Update again and again which eats my data plan, unless I notice and stop it. I am looking for a clear instruction on how to flash the newest version directly via cable. I could not find one. Alternatively I would be happy if someone could show me a way to stop the repeating downloads of the latest OTA-version.
Thanks!
basically you unzip the flashtool zip and do
Code:
fastboot flash splash splash.img
fastboot flash modem NON-HLOS.bin
fastboot flash aboot emmc_appsboot.mbn
fastboot flash hyp hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash system system.img
if you want to keep data skip userdata (but clear dalvik cache in twrp)
if you want to keep twrp do not flash recovery
Dior DNA said:
basically you unzip the flashtool zip and do
Code:
fastboot flash splash splash.img[/QUOTE]
It worked thanks. Unfortunately I am back to bootloops after flashing supersu.v2.46 via twrpThis worked with previous versions.
Any idea how to do this correctly?
Click to expand...
Click to collapse
sambahb said:
It worked thanks. Unfortunately I am back to bootloops after flashing supersu.v2.46 via twrp. This worked with previous versions.
Any idea how to do this correctly?
Click to expand...
Click to collapse
You need to root MM with system less SuperSU ZIP version, I believe v2.65 onwards (v2.76 may be latest, you need to check). And each time you flash kernel (aka boot.img) again you need to root.
Dior DNA said:
You need to root MM with system less SuperSU ZIP version, I believe v2.65 onwards (v2.76 may be latest, you need to check). And each time you flash kernel (aka boot.img) again you need to root.
Click to expand...
Click to collapse
Its better to use super su 2.76 because it has boot image patcher.
Sent from my Wileyfox Swift using XDA-Developers mobile app
Hi People, I'm a Moto G5 (XT1676) user. After unlocking bootloader, rooting, flashing ROMs, etc. I "broke" my phone and now mi IMEIs are 0 and lost my phone signal.
I've been reading posts of older versions (Moto G1, G3) that people seem to fix this problem by flashing oher phone's back up of fsc, hob and dhob partitions. The problem is that in my Moto G5 only fsc partition appears.
I'm not expert and don't understand too much , I'm just asking for your help please, my phone turned into a tablet .
Do anyone of you guys know what partition do I have to fix in this phone?
Can you upload a back up of those partitions for me please?
Flashing those partitions on other versions of the phone seem to fix signal problem leaving IMEI = 0, I just need my signal back.
Something that I don't know if is relevant is that when I messed up flashing things, reading posts around internet I used some commands that I think modified "persist" and "misc" partitions.
Can anyone upload those just in case too?
Sorry if something is wrong, english is not my native language.
Please help me!
EDIT!!:
I've managed to revive my phone restoring someone's persist backup from twrp, "Backup & Restore partitions" doesn't work. The file I used to fix this problem is in this link: https://mega.nz/#!Yd82hSZZ!vdmbqAG0bQhNyR5g95KOrZjVvBw2QDrirpOwhD96gPc
The only file i needed was the persist backup in that .rar
It's no my partition, I've found it around internet, searching everywhere, but it worked.
Thanks for all the people that tried to help me!
IMEI stayed 0 but my mobile signal is back!!
How to restore that partition?:
1-Install TWRP.
2-Go into Backup and make a backup of any partition there. This will create a partition folder inside TWRP folder.
3-Copy the persist backup I've shared into that backup folder.
4-Boot into twrp, restore and select persist.
5-Restore.
6-Flash stock rom again for your device.
I hope that this help anyone in the same situation. This works for Moto G5 Plus too from what I've been reading.
It would be nice if people comment their results so we can help others.
Attention!: This doesn't fix IMEI, it stays 0 but mobile signal is back.
Good Luck and thanks!
flash stock rom via fastboot
never play around with partitions unless you know what you are doing - simply typing in commands without knowing their meaning will likely muck up your device
find your stock rom firmware via the power of google
Open a command/terminal prompt where you have fastboot (if you have added fastboot to the environmental settings you can run it from any location)
The commands you will likely need are
Code:
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I have included fastboot in the link below - You will also need to download and install the moto usb drivers if you have not already done so
Platform-tools Download
TheFixItMan said:
flash stock rom via fastboot
never play around with partitions unless you know what you are doing - simply typing in commands without knowing their meaning will likely muck up your device
find your stock rom firmware via the power of google
Open a command/terminal prompt where you have fastboot (if you have added fastboot to the environmental settings you can run it from any location)
The commands you will likely need are
Code:
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I have included fastboot in the link below - You will also need to download and install the moto usb drivers if you have not already done so
Platform-tools Download
Click to expand...
Click to collapse
I've already tried flashing stock rom but the problem is still there, I've also tried some custom roms too without success.
I know is my fault, I touched where I didn't have to.
I don't know what else to try, I think flashing other's back up partitions is my last shot.
I don't know if you are a Moto G5 user, but if you are, can you share those partitions to me?
Thanks for your reply.
Your gonna need an EFS / QCN backup. Do you know how to set the modem to diagnostic mode?
SvenRL said:
Your gonna need an EFS / QCN backup. Do you know how to set the modem to diagnostic mode?
Click to expand...
Click to collapse
From what I've been reading Moto G doesn't have a EFS partition, I've found in other forums that Moto G4 series have that data in "Persist" partition, and that partition is the one i've been touching..
That's why I'm asking if someone can backup that partition and share to me.
There is an app that does the job "Partitions Backup & Restore", I think you need root to use it.
I need that Persist backup just to try fix my phone, if you have Moto G5, can you help me with that?
Yes I know how to set it into diagnostic mode. (I've been trying apps and programs that in that mode fix qualcomm devices without success).
Thanks for your reply!
Can someone please help me with a "persist" partition backup please? I really need help.
Hi Jerito. Sorry to take a few days to reply to your PM. Been away.
Not sure i can help with this one as am not knowledgeable about copying particular partitions.
About the most comprehensive rebuild i have ever done was what i posted about doing it file by file and if i was in your situation, well, thats what i'd try.
Can you somehow extract the partition you are after out of a ROM??
I'll do you a qcn backup, wait till early hours of Monday morning. I'm curious cause i have the same issue with my lenovo P2, no persist partition, but I think the persist partition is created from the fsg partition
astmacca said:
Hi Jerito. Sorry to take a few days to reply to your PM. Been away.
Not sure i can help with this one as am not knowledgeable about copying particular partitions.
About the most comprehensive rebuild i have ever done was what i posted about doing it file by file and if i was in your situation, well, thats what i'd try.
Can you somehow extract the partition you are after out of a ROM??
Click to expand...
Click to collapse
No problem, the best way I've found of doing a back up of that partition is through the app I've mentioned "Partition Backup and Restore", I will watch your post!
SvenRL said:
I'll do you a qcn backup, wait till early hours of Monday morning. I'm curious cause i have the same issue with my lenovo P2, no persist partition, but I think the persist partition is created from the fsg partition
Click to expand...
Click to collapse
Ok, I'll be waiting, thanks both!
My nexus 5x is stuck in the boot animation (spinning circles) after erase/format of userdata (for at least 30 minutes, and tried holding power to reboot several times with the same result).
I recently updated to the latest Oreo build in the same way that I always have in the past. This time the only thing different was that I wiped userdata. I had already updated from 7.1.2 to the 8.0.0 August build, and then to the September build without any problems.
I got tired of lagging and other issues so I did a factory reset and wipe data using settings. After that the steps I used to flash the October update:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot erase userdata
fastboot format userdata
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
This is the first time that I've formatted and erased userdata so I think that's what caused the problem. I've never had a problem until now and the only reason I tried those two commands is because none of the recent nexus images come with a userdata.img file. What can I do to get back up and running with a successful boot?
Thanks much!
Update:
I flashed the userdata.img file from the stock 7.1.1 build (the last build that included a userdata.img file that I was able to find). After reboot it continued to hang on the spinning circles. Then I went ahead and flashed the full 7.1.1 build and it booted to the initial setup screen like normal.
Since that worked, I flashed the October 8.0 update and it's now stuck at the Google logo (plain white google text on black background) while overheating. Any advice at this point would be appreciated. I don't really want to go back to 7.1.2 and be stuck there.
Flash the complete Oreo-firmware. If you cleaned everything, why to trust in functionality of a big update?
rp158 said:
Flash the complete Oreo-firmware. If you cleaned everything, why to trust in functionality of a big update?
Click to expand...
Click to collapse
I did flash the complete Oreo (October update). I resolved the issue by flashing 7.1.2 with the vendor and cache img from 7.1.1 and letting the OTA updates happen. Now I'm on the October 8.0 update.
I'm not sure what the problem was, maybe a corrupted download of the OPR4.170623.009, Oct 2017. I resolved the issue before I did an SHA-256 Checksum.
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
CompostKicker said:
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
Click to expand...
Click to collapse
Hey man, have you have any success on this?
CompostKicker said:
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
Click to expand...
Click to collapse
ogabriel said:
Hey man, have you have any success on this?
Click to expand...
Click to collapse
Yes and no. I was able to get a backup of the EFS partition from the LineageOS 15.1 ROM, which does restore cell service. However, it does not provide 4G LTE. I can get LTE on LineageOS, but when I reflash stock and then restore the EFS partition, it only gets me 3G connectivity. So far, the only way that I have been able to get LTE is to flash LineageOS, then run this:
Code:
fastboot erase modemst1 && fastboot erase modemst2
Apparently, those are cache files for something that has an effect on connectivity, though I don't know specifically what. Unfortunately, I must remain on LineageOS in order to keep the LTE. If I try erasing the modem caches on stock, it wipes all connectivity and returns me to IMEI 0. Downsides to this are bluetooth calls don't work at all, GPS navigation doesn't work, absolutely no torch (even with a third party app) and battery life is poo.
I am still looking in to this, including compiling my own ROM from source. Really, this whole ordeal has taught me two very important things:
1) Always make a complete backup of everything.2) Don't buy a phone that has no developer support on XDA. Honestly, this is the biggest one right here. Its revolting how little support there is for this device.I will update this thread as I get new information on potential fixes.
Thank you compostkicker ..would apprentice if you post the solution if you find one..I am also going through a ditto condition
ogabriel said:
Hey man, have you have any success on this?
Click to expand...
Click to collapse
I'm facing the same here. My problems started after the "erase modemst" command. After that I never was able to use my LTE connection again. I was able to use at least a H+ connection after I flashed a stock rom WITHOUT wiping nor formating data from a Lineage install. But, still no LTE. =/
I'm afraid this is caused by wrong modem driver w/ the downloaded stock rom. Don't know if there's a different driver for the Brazillian device.
CompostKicker said:
Yes and no. I was able to get a backup of the EFS partition from the LineageOS 15.1 ROM, which does restore cell service. However, it does not provide 4G LTE. I can get LTE on LineageOS, but when I reflash stock and then restore the EFS partition, it only gets me 3G connectivity. So far, the only way that I have been able to get LTE is to flash LineageOS, then run this:
Code:
fastboot erase modemst1 && fastboot erase modemst2
Apparently, those are cache files for something that has an effect on connectivity, though I don't know specifically what. Unfortunately, I must remain on LineageOS in order to keep the LTE. If I try erasing the modem caches on stock, it wipes all connectivity and returns me to IMEI 0. Downsides to this are bluetooth calls don't work at all, GPS navigation doesn't work, absolutely no torch (even with a third party app) and battery life is poo.
I am still looking in to this, including compiling my own ROM from source. Really, this whole ordeal has taught me two very important things:
1) Always make a complete backup of everything.2) Don't buy a phone that has no developer support on XDA. Honestly, this is the biggest one right here. Its revolting how little support there is for this device.I will update this thread as I get new information on potential fixes.
Click to expand...
Click to collapse
YEEEEEEESSS I FIXED IT!!! HAHAHAHAHA
I followed what you said installing Lineage OS and did the "erase modemst" command. After that, I formated data using TWRP and flashed a stock rom but I skipped "erase modemst" command. And now my LTE is working on the stock rom. OMG!!!! \o/
So...
1. Flash Lineage OS 15.1
2. Restart in Bootloader and run the fastboot code [fastboot erase modemst1 && fastboot erase modemst2]
3. Restart the system.
4. Restart and use TWRP to FORMAT data.
5. Flash the stock rom using Fastboot and the following 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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
DON'T RUN THE MODEM ERASE CODE AGAIN!!!
This steps will fix the issue!
varun.katoch said:
Thank you compostkicker ..would apprentice if you post the solution if you find one..I am also going through a ditto condition
Click to expand...
Click to collapse
Sorry to leave you hanging, I stopped getting alerts on this thread for some reason. I am on shift until tomorrow and away from my computer, and it is a lot to type for a phone, but as soon as I am able I will type out the exact steps I used to fix the LTE issue, for both LineageOS and stock ROM.
Rodrigo Fernandes said:
YEEEEEEESSS I FIXED IT!!! HAHAHAHAHA
I followed what you said installing Lineage OS and did the "erase modemst" command. After that, I formated data using TWRP and flashed a stock rom but I skipped "erase modemst" command. And now my LTE is working on the stock rom. OMG!!!! \o/
So...
1. Flash Lineage OS 15.1
2. Restart in Bootloader and run the fastboot code [fastboot erase modemst1 && fastboot erase modemst2]
3. Restart the system.
4. Restart and use TWRP to FORMAT data.
5. Flash the stock rom using Fastboot and the following 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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
DON'T RUN THE MODEM ERASE CODE AGAIN!!!
This steps will fix the issue!
Click to expand...
Click to collapse
Thank you bro, can you say which model you have and which retail firmware have you chosen for flashing via fastboot?
HTCDevil said:
Thank you bro, can you say which model you have and which retail firmware have you chosen for flashing via fastboot?
Click to expand...
Click to collapse
Moto Z2 Play - XT1710-07 and the retail firmware was NPSS26.118-19-1-6. Still working ok yet.
CHECK THIS LINK IF YOU WANT YOUR VOLTE TO WORK :
100% working
https://forum.xda-developers.com/newthread.php?do=postthread&f=6506
Rodrigo Fernandes said:
Moto Z2 Play - XT1710-07 and the retail firmware was NPSS26.118-19-1-6. Still working ok yet.
Click to expand...
Click to collapse
Without erasing modem1st and 2st, is it right?
HTCDevil said:
Without erasing modem1st and 2st, is it right?
Click to expand...
Click to collapse
That's right! But only after you follow the step 2. Otherwise it won't work.
Rodrigo Fernandes said:
That's right! But only after you follow the step 2. Otherwise it won't work.
Click to expand...
Click to collapse
I would like to pass from ZUI (on xt1710-08) to a retail one without flashing Lineage before. So, if the problem is about modem i should not erase them, so I would leave those present on the initial version unchanged
So, my situation is : signal is ok lte\4g bit IMEI is 0. I think i understand i must flash stock lineage rom with this commands, then backup efs (i've already had It), so flash stock nougat and restore efs and i should have IMEI. Is It correct?
Inviato dal mio Moto Z2 Play utilizzando Tapatalk
Rodrigo Fernandes said:
YEEEEEEESSS I FIXED IT!!! HAHAHAHAHA
I followed what you said installing Lineage OS and did the "erase modemst" command. After that, I formated data using TWRP and flashed a stock rom but I skipped "erase modemst" command. And now my LTE is working on the stock rom. OMG!!!! \o/
So...
1. Flash Lineage OS 15.1
2. Restart in Bootloader and run the fastboot code [fastboot erase modemst1 && fastboot erase modemst2]
3. Restart the system.
4. Restart and use TWRP to FORMAT data.
5. Flash the stock rom using Fastboot and the following 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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
DON'T RUN THE MODEM ERASE CODE AGAIN!!!
This steps will fix the issue!
Click to expand...
Click to collapse
Hey, I just flashed 9 on my XT1710-8 and lost singal. do you think this trick works in my case? (havent tried yet cause didnt want to format my device!)
CompostKicker said:
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
Click to expand...
Click to collapse
Try Moto lenovo smart asistant to rescue your device @CompostKicker
kevoroid said:
Hey, I just flashed 9 on my XT1710-8 and lost singal. do you think this trick works in my case? (havent tried yet cause didnt want to format my device!)
Click to expand...
Click to collapse
I can't guarantee you can fix it using my step-by-step because I did it for the XT1710-07 model. Maybe you'll have to adapt the solution to yours.
Rodrigo Fernandes said:
I can't guarantee you can fix it using my step-by-step because I did it for the XT1710-07 model. Maybe you'll have to adapt the solution to yours.
Click to expand...
Click to collapse
I fixed it by flashing the original -08's Oreo ROM (Chinese ROM) and then reflashing Pie without doing the "erase modemst1.." steps.
moto z2 play imei repair
Hello everyone . i have moto z2 play xt1710-6 with stock rom. i wanna change my imei coz of lost signal. i tried many softs but i was not ablet to change it. i went to some techical shops , they used sigma and miracle , they couldnt as well. overall , how may i change its imei ? are there any way ?