Related
This might be a standard question, if so please delete.
I have found some posts on flashing stock with fastboot but sadly I can't due to a fastboot issue on my phone (fastboot secure, no baseband) but I can flash a rom using twrp.
If the answer is no, is there a rom similar to stock? I just want the stability of stock now and the stock apps.
What is your model, xt1575 or 72?
Somewhere was backups, you need boot+system. @Walgeon
I have 72. I can only flash a rom due to some odd issue I have that I can't fix. @dzidexx
I don't understand - you can flash rom.zip but cannot restore backup? @Walgeon
---------- Post added at 09:14 PM ---------- Previous post was at 09:01 PM ----------
Here you can download my backup:
https://forum.xda-developers.com/mo...ock-backup-reteu-xt1572-6-0-1-twrp-3-t3630568
Do your own any backup(to usb, sd card, memory) and replace files, restore.
Here are flashable modems:
https://forum.xda-developers.com/mo...odem-flashable-modem-files-eu-single-t3297051
Flash for your region and reboot.
Basically i rooted systemlesly and changed my emojis to the IOS ones with an app on the playstore. Then i reset my phone because of reasons. Now i want to remove my root and get magisk and xposed. To do this i need to remove my SU root and flash magisk, however magisk will only flash with an unmodified system.
This is where my problem occurs. When i reset my phone my original emojis were removed, leaving me with the IOS emojis. I made no backup of my original emojis. When i click restore emojis on the app no emojis change, and when i install the nougat emojis from the app my system is still considered "modified"
Therefore, im asking if anyone has a boot.img of my Moto x style, as i think flashing that would fix it. I also think that if anyone has the original NotoColorEmoji.ttf file, i can replace it with mine and it could fix it aswell. If anyone has any of these 2 files it would be much appreciated ??
Supersu can restore boot - unroot & clean option.
Tts you can extract from stock latam:
https://forum.xda-developers.com/moto-x-style/general/xt1575-72-nougat-7-0-stock-official-t3671995
Or
Somewhere in general was twrp backup of reteu:
https://forum.xda-developers.com/moto-x-style/general
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
@XxperexX
dzidexx said:
Supersu can restore boot - unroot & clean option.
Tts you can extract from stock latam:
https://forum.xda-developers.com/moto-x-style/general/xt1575-72-nougat-7-0-stock-official-t3671995
Or
Somewhere in general was twrp backup of reteu:
https://forum.xda-developers.com/moto-x-style/general
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
@XxperexX
Click to expand...
Click to collapse
Trying to restore boot from SuperSU resulted in it saying uninstallation failed. I also tried looking through the general section and none that ive found have a boot.img file i can just flash.
Very funny
https://forum.xda-developers.com/moto-x-style/general/backup-image-moto-x-style-android-7-0-t3637111
---------- Post added at 08:56 PM ---------- Previous post was at 08:54 PM ----------
@XxperexX
dzidexx said:
Very funny
https://forum.xda-developers.com/moto-x-style/general/backup-image-moto-x-style-android-7-0-t3637111
---------- Post added at 08:56 PM ---------- Previous post was at 08:54 PM ----------
@XxperexX
Click to expand...
Click to collapse
Funny indeed ? That image doesn't have a -3 at the end, and mine does, so idk if it will work and i wanna be sure
For sure you should have your own backup.
Why don't?
I'm not sure but boot(kernel) should work. @XxperexX
Do full backup first.
In supersu thread shoul be su uninstaler.zip.
dzidexx said:
For sure you should have your own backup.
Why don't?
I'm not sure but boot(kernel) should work. @XxperexX
Do full backup first.
In supersu thread shoul be su uninstaler.zip.
Click to expand...
Click to collapse
Ive already uninstalled supersu, i just said no when it asked to restore ti stock boot because when i chose yes it said failed. The only backups i have are of marshmallow 18-8 and nougat, but with the changed emojis (pretty stupid on my part)
I also have no idea what u mean by boot(kernel)
Sypersu(magisk too) modify boot partition(kernel), both are systemless.
If you want change susu to magisk you need uninstall susu and restore stock boot.
I haven't now supersu but I know it is backing up stock boot and can restore it when uninstalling.
This option is in supersu app.
/Supersu on MM needed to make folder .su if I good remember, maybe you didn't do it/
You can stay at what you have or restore boot + system(linked) and format/wipe data, cache, dalvik. @XxperexX
You can't downgrade now - bootloader is Nougat, you will not get ota.
Sorry for my english.
dzidexx said:
Sypersu(magisk too) modify boot partition(kernel), both are systemless.
If you want change susu to magisk you need uninstall susu and restore stock boot.
I haven't now supersu but I know it is backing up stock boot and can restore it when uninstalling.
This option is in supersu app.
/Supersu on MM needed to make folder .su if I good remember, maybe you didn't do it/
You can stay at what you have or restore boot + system(linked) and format/wipe data, cache, dalvik. @XxperexX
You can't downgrade now - bootloader is Nougat, you will not get ota.
Sorry for my english.
Click to expand...
Click to collapse
Lol its fine. Well eventually i managed to install magisk. I downloaded the boot/sys backup from https://forum.xda-developers.com/mo...gust-2017-security-patch-nph25-t3673373/page3 and restored it via twrp, then flashed magisk and it worked
Good Morning everybody,
so yesterday was a rough day and when it eventually end i recive the october security update on the phone, without thinking i installed it and the phone does not boot up , instead i face my recovery (TWRP 3.1.1-0).
Of course i've made a mess because i was on stock rooted 7.0 on my retEU XT1572 phone with unlocked bootloader and status 3
i've tryed to restore a previous nandroid backup wihtout success, so today i downloaded the new RESURRECTION REMIX v5.8.4 (4 december wich is based on stock android 7) but i have no luck even with that...
Do i miss something?is there any rom to try with now? or i have to make a downgrade of my firmware to make it work again?
thanks in advice!
UPDATE:
phone boot now but always in recovery and after rebooting in bootloader i can reboot system from there.. it seems that if you download an update and the install process doesen't go in place every time you restart the device it always try to re-flash it, that's why i'm always in recovery.. i foun a similar post with this solution but i think it need some changes before it will work on our device (but i don't have the knowledge to set it right :S )
LAST UPDATE:
boot fixed by using this command in twrp recovery
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
misc file running at the startup redirecting the boot in the recovery, put blank in the file let the system boot up normally
You missed very much.
Here is stock RetEu, before october update:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
Wipe all with twrp and flash all. After it you can get OTA's.
---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------
Here is RR 5.8.5 working on N modem:
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page40 post #397
Wipe all with twrp, update twrp to 3.2 and you can flash it right now.
@
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
@Husky34
oh thanx man! i've already seen that post but i wasn't sure that it can work for me. i have some question befor starting:
1) i need the new twrp 3.2 to flash resurrection-remix? because as i mention before i've already tried to flash it with twrp 3.1 and it doesen't work (the rom is the same that you linked page40 post #397 )
2) do i have to flash stock-xt-1572-reteu-7-0-ddumped-files before point 1)?
dzidexx said:
You missed very much.
Here is stock RetEu, before october update:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
Wipe all with twrp and flash all. After it you can get OTA's.
---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------
Here is RR 5.8.5 working on N modem:
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page40 post #397
Wipe all with twrp, update twrp to 3.2 and you can flash it right now.
@
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
@Husky34
Click to expand...
Click to collapse
Husky34 said:
oh thanx man! i've already seen that post but i wasn't sure that it can work for me. i have some question befor starting:
1) i need the new twrp 3.2 to flash resurrection-remix? because as i mention before i've already tried to flash it with twrp 3.1 and it doesen't work
2) do i have to flash stock-xt-1572-reteu-7-0-ddumped-files before point 1)?
Click to expand...
Click to collapse
1. I think so. 3.2.x will be needed for future builds.
1a. You flashed RR for MM modem.
2. No, but this is only way to get ota update.
"swearing in italian" it was a twrp bug.. after a backup restore if you hit restart the phone restart in recovery, you need to boot into bootloader and reboot system from there -.-
thanks to all of you guys!!
strange fact, now if i turn off the phone and again on i'm still on recovery, i have to reboot bootloader and system from there.
i think something is pointing at the recovery instead system..
edit: it seems that if you download an update and the install process doesen't go in place every time you restart the device it always try to re-flash it, that's why i'm always in recovery.. i foun a similar post with this solution but i think it need some changes before it will work on our device (but i don't have the knowledge to set it right :S )
Ota update didn't end.
I think you can try clear data & cache otaupdate app and disable it. Link2sd can help with it. @Husky34
dzidexx said:
Ota update didn't end.
I think you can try clear data & cache otaupdate app and disable it. Link2sd can help with it. @Husky34
Click to expand...
Click to collapse
just tried but wihout luck.. maybe i can wait someone make the flashable update but i don't think this fix the issue
Flash uploaded stock.
dzidexx said:
Flash uploaded stock.
Click to expand...
Click to collapse
actually i fixed the issue using this command
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
misc file running at the startup redirecting the boot in the recovery, put blank in the file let the system boot up normally
Husky34 said:
actually i fixed the issue using this command
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
misc file running at the startup redirecting the boot in the recovery, put blank in the file let the system boot up normally
Click to expand...
Click to collapse
thanks, this command just saved me. but misc file in my XT1575 is under
/dev/block/platform/0/f9824900.sdhci/by-name/misc
but now I can't check system update in the OS anymore, I think flash back factory recovery mine help. Do you know where to download stock 7.0 recovery for 1575?
Edit: found it for 1575 here.
pshadoww said:
thanks, this command just saved me. but misc file in my XT1575 is under
/dev/block/platform/0/f9824900.sdhci/by-name/misc
but now I can't check system update in the OS anymore, I think flash back factory recovery mine help. Do you know where to download stock 7.0 recovery for 1575?
Edit: found it for 1575 here.
Click to expand...
Click to collapse
you can also use link2sd to disable the update app so it doesn't bother you,
or wait untill someone create a zip of the update and flash it into recovery.
thanks, that worked for me as well.
File was located at /dev/block/platform/soc.0/f9824900.sdhci/by-name/misc
friends, I have xt1640, after it upgraded to android 8.1, the cell phone ran out of network service, I downgraded, and nothing ...
What does your baseband report in Settings>About phone? Do you see your IMEI in Settings as well?
A side note, if you've downgraded, do not use stock OTA updates. You'll hard brick your device else, and the fix is expensive.
echo92 said:
What does your baseband report in Settings>About phone? Do you see your IMEI in Settings as well?
A side note, if you've downgraded, do not use stock OTA updates. You'll hard brick your device else, and the fix is expensive.
Click to expand...
Click to collapse
the mobile was working perfectly ... after it updated via OTA, for 8.1 it was out of service, the baseband is ok, when I'm going to call it it says to disable the airplane mode
herbao said:
the mobile was working perfectly ... after it updated via OTA, for 8.1 it was out of service, the baseband is ok, when I'm going to call it it says to disable the airplane mode
Click to expand...
Click to collapse
Hmm, that's odd - did you try to re-flash the Oreo stock firmware? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
When you downgraded, did you erase modemst1 and modemst2? Have you verified your IMEI is present and your SIM card is still working (i.e. try it in another device) and you do not have network issues?
echo92 said:
Hmm, that's odd - did you try to re-flash the Oreo stock firmware? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
When you downgraded, did you erase modemst1 and modemst2? Have you verified your IMEI is present and your SIM card is still working (i.e. try it in another device) and you do not have network issues?
Click to expand...
Click to collapse
I did not delete the modemst, the imei is showing up !! I was researching, and I saw that there are some people with the same problem ...
herbao said:
I did not delete the modemst, the imei is showing up !! I was researching, and I saw that there are some people with the same problem ...
Click to expand...
Click to collapse
I'm not sure if your Oreo modemst would be working with your Nougat baseband if you're still downgraded. You might like to backup your modemst with Lyuu's TWRP (back up your EFS) and then try erasing modemst. The Oreo OTA update would have erased the modemst1/modemst2 (EFS) as part of its update.
echo92 said:
I'm not sure if your Oreo modemst would be working with your Nougat baseband if you're still downgraded. You might like to backup your modemst with Lyuu's TWRP (back up your EFS) and then try erasing modemst. The Oreo OTA update would have erased the modemst1/modemst2 (EFS) as part of its update.
Click to expand...
Click to collapse
Okay, I installed twrp, to try to backup efs, but the partition does not appear to back up ... could you help me?
I'm using google translate. Brazil
herbao said:
Okay, I installed twrp, to try to backup efs, but the partition does not appear to back up ... could you help me?
I'm using google translate. Brazil
Click to expand...
Click to collapse
Did you flash Lyuu's TWRP as I mentioned? https://forum.xda-developers.com/mo...t/recovery-team-win-recovery-project-t3842903 Other TWRP recoveries may not be able to back up this partition.
echo92 said:
Did you flash Lyuu's TWRP as I mentioned? https://forum.xda-developers.com/mo...t/recovery-team-win-recovery-project-t3842903 Other TWRP recoveries may not be able to back up this partition.
Click to expand...
Click to collapse
Okay, I'll do it tomorrow morning and post the result, so I backup efs, I delete the modemst partition, and install the 8.1 stockrom, right? I do not do it now, because of the schedule, it's already late here, but thanks for your attention,
herbao said:
Okay, I'll do it tomorrow morning and post the result, so I backup efs, I delete the modemst partition, and install the 8.1 stockrom, right? I do not do it now, because of the schedule, it's already late here, but thanks for your attention,
Click to expand...
Click to collapse
Yeah - so the plan is:
1)Backup your EFS (though it might be already damaged, might as well keep it safe).
2)Erase modemst1/modemst2 via fastboot. Reboot. Test if SIM service is working. Check IMEI and baseband (baseband should be reporting ATHENE_BRAZIL_DSDS_CUST, and ending in 77R if on Oreo, .62.02R if on April 2018 stock Nougat).
3)If device is still not in service, flash stock Oreo firmware. You do not need to re-lock, so you could omit the fastboot OEM lock begin commands to avoid locking the bootloader.
echo92 said:
Yeah - so the plan is:
1)Backup your EFS (though it might be already damaged, might as well keep it safe).
2)Erase modemst1/modemst2 via fastboot. Reboot. Test if SIM service is working. Check IMEI and baseband (baseband should be reporting ATHENE_BRAZIL_DSDS_CUST, and ending in 77R if on Oreo, .62.02R if on April 2018 stock Nougat).
3)If device is still not in service, flash stock Oreo firmware. You do not need to re-lock, so you could omit the fastboot OEM lock begin commands to avoid locking the bootloader.
Click to expand...
Click to collapse
friend I did what you asked me, and it did not work, I sent you a print for you to see
https://uploaddeimagens.com.br/imagens/g4-jpg-f5886a19-b5f6-4d4a-83b7-bb6b77bde02c
herbao said:
friend I did what you asked me, and it did not work, I sent you a print for you to see
https://uploaddeimagens.com.br/imagens/g4-jpg-f5886a19-b5f6-4d4a-83b7-bb6b77bde02c
Click to expand...
Click to collapse
Your baseband, modern or fsg is corrupted, it is reporting DFLT_FSG as the suffix - for your device, it should be reporting ATHENE_BRAZIL_DSDS_CUST or similar. Your baseband clearly is not okay, was it DFLT_FSG also when you updated to Oreo via OTA?
You could try this https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
echo92 said:
Your baseband, modern or fsg is corrupted, it is reporting DFLT_FSG as the suffix - for your device, it should be reporting ATHENE_BRAZIL_DSDS_CUST or similar. Your baseband clearly is not okay, was it DFLT_FSG also when you updated to Oreo via OTA?
You could try this https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
Click to expand...
Click to collapse
was updated on the 28th, how can I recover ??
herbao said:
was updated on the 28th, how can I recover ??
Click to expand...
Click to collapse
I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
echo92 said:
I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
Click to expand...
Click to collapse
Brother, you saved me ... Thank you.
echo92 said:
I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
Click to expand...
Click to collapse
Dude, you're a god. I looked all over the internet for this solution, I do not believe it really worked!
echo92 said:
I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
Click to expand...
Click to collapse
Can I do this now because recently recovered my phone 8.1.0
---------- Post added at 04:47 PM ---------- Previous post was at 04:40 PM ----------
echo92 said:
I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
Click to expand...
Click to collapse
Password please...
---------- Post added at 04:57 PM ---------- Previous post was at 04:47 PM ----------
echo92 said:
I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
Click to expand...
Click to collapse
This file asking password bro...please tell me
---------- Post added at 05:13 PM ---------- Previous post was at 04:57 PM ----------
echo92 said:
I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?
You could try:
Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.
Extract the firmware, and open the extracted firmware folder.
Find the programutags.bat in the folder.
Run the .bat script and follow the instructions.
Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
Click to expand...
Click to collapse
This file extract with winRAR.it showing all errors
And extract the file 7zip aslo all files error
Bro
---------- Post added at 05:13 PM ---------- Previous post was at 05:13 PM ----------
Tetcare99 said:
Can I do this now because recently recovered my phone 8.1.0
---------- Post added at 04:47 PM ---------- Previous post was at 04:40 PM ----------
Password please...
---------- Post added at 04:57 PM ---------- Previous post was at 04:47 PM ----------
This file asking password bro...please tell me
---------- Post added at 05:13 PM ---------- Previous post was at 04:57 PM ----------
This file extract with winRAR.it showing all errors
And extract the file 7zip aslo all files error
Bro
Click to expand...
Click to collapse
I can't extract it
Tetcare99 said:
Can I do this now because recently recovered my phone 8.1.0
---------- Post added at 04:47 PM ---------- Previous post was at 04:40 PM ----------
Password please...
---------- Post added at 04:57 PM ---------- Previous post was at 04:47 PM ----------
This file asking password bro...please tell me
---------- Post added at 05:13 PM ---------- Previous post was at 04:57 PM ----------
This file extract with winRAR.it showing all errors
And extract the file 7zip aslo all files error
Bro
---------- Post added at 05:13 PM ---------- Previous post was at 05:13 PM ----------
I can't extract it
Click to expand...
Click to collapse
1) you should be able to use this procedure, this thread you're replying in had a similar scenario to you.
2) make sure the firmware you've downloaded is the correct size. I've just checked and it's 893 MB in size. The first download I tried failed towards the end.
3)I used the app 7-zipper, with the password lenovo-forums.ru and it seemed to work. Not sure why you're having trouble extracting the files, I'd try to redownload the firmware. I don't know if the script on its own works or if you need the full firmware.
Also, please note these are not real time forums, repeatedly posting will not necessarily make a member post any faster. I get you're frustrated by your device only partially working, please be patient.
echo92 said:
1) you should be able to use this procedure, this thread you're replying in had a similar scenario to you.
2) make sure the firmware you've downloaded is the correct size. I've just checked and it's 893 MB in size. The first download I tried failed towards the end.
3)I used the app 7-zipper, with the password lenovo-forums.ru and it seemed to work. Not sure why you're having trouble extracting the files, I'd try to redownload the firmware. I don't know if the script on its own works or if you need the full firmware.
Also, please note these are not real time forums, repeatedly posting will not necessarily make a member post any faster. I get you're frustrated by your device only partially working, please be patient.
Click to expand...
Click to collapse
1 - LATAM
2 - APAC
3 - Canada
4 - US
5 - EMEA
6 - QUIT
please select region : 2
A - Retail APAC
B - Retail India
C - Quit
Please select carrier : B
Waiting for fastboot enumeration...
Still waiting.....
Do you by any chance have a JTAG flex attached?
If so , detach the JTAG flex and try again
Still waiting.....
Do you by any chance have a JTAG flex attached?
If so , detach the JTAG flex and try again
Still waiting.....
Do you by any chance have a JTAG flex attached?
If so , detach the JTAG flex and try again
Still waiting.....
Do you by any chance have a JTAG flex attached?
If so , detach the JTAG flex and try again
Bro..:crying::crying:
Tetcare99 said:
1 - LATAM
2 - APAC
3 - Canada
4 - US
5 - EMEA
6 - QUIT
please select region : 2
A - Retail APAC
B - Retail India
C - Quit
Please select carrier : B
Waiting for fastboot enumeration...
Still waiting.....
Do you by any chance have a JTAG flex attached?
If so , detach the JTAG flex and try again
Still waiting.....
Do you by any chance have a JTAG flex attached?
If so , detach the JTAG flex and try again
Still waiting.....
Do you by any chance have a JTAG flex attached?
If so , detach the JTAG flex and try again
Still waiting.....
Do you by any chance have a JTAG flex attached?
If so , detach the JTAG flex and try again
Bro..:crying::crying:
Click to expand...
Click to collapse
Was your device booted to fastboot for this procedure, as requested by the script? Does your device properly communicate with your computer in fastboot (i.e. if you type fastboot devices into an ADB terminal, does your device respond with its serial number)?
Hello, I have been trying to fix this oddly specific issue with my Moto G7 running LineageOS. I can make and receive calls fine, but I have issues receiving texts. I can send them, but replies are delayed from a few minutes to an hour or two. I am unsure of why this has happened, but I remember trying to install LineageOS for Micro G and noticing this after. However, I didn't happen to be texting much before this, so it may not be relevant.
Anyways, I went to Verizon twice and they confirmed there was no issue with the sim card. However, when they tried replacing it, the system didn't recognize it at all and it couldn't even make a phone call.
I am honestly stuck and I do not know where to go from here. I've tried finding stock firmware but the issue persists after flashing what I THINK is the correct firmware and reinstalling. I really don't want to have to pay for a new phone (one that would likely be way more expensive than this one), so please give me anything I could work with.
Go back to stock 10, make calls and texts (including MMS), and then twrp, los17.1, gapps, root and start over
What's your phone model?
---------- Post added at 11:40 AM ---------- Previous post was at 11:39 AM ----------
Xt1962-1 from Amazon is mine
---------- Post added at 11:41 AM ---------- Previous post was at 11:40 AM ----------
https://mirrors.lolinet.com/firmware/moto/river/official/
---------- Post added at 11:49 AM ---------- Previous post was at 11:41 AM ----------
May have to erase modem partitions and then reinstall stock 10 using "adb shell" command while in fastboot mode:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
I have the same model, I'll try your solution now.
HueyT said:
Go back to stock 10, make calls and texts (including MMS), and then twrp, los17.1, gapps, root and start over
Click to expand...
Click to collapse
After installing the firmware, my device does not boot and stays on the unlocked bootloader warning. I can easily reinstall LineageOS, but my issue still persists.
CheeseESimp said:
After installing the firmware, my device does not boot and stays on the unlocked bootloader warning. I can easily reinstall LineageOS, but my issue still persists.
Click to expand...
Click to collapse
Do you mean that stock 10 won't boot? Any errors while installing stock 10? Which batch file did u use to automate all the fastboot commands?
Fastboot batch file
Unzip for bat file, put file in adb folder which should have all the files of stock ROM zip file that's been unzipped, and run it at dos prompt
https://forum.xda-developers.com/moto-g7/how-to/to-stock-relock-boot-loader-google-fi-t3966959
Is a guide to flashing stock rom (your rom will be different but the steps are similar except Q rom has 10 sparsechunks while PIE rom only has 9)
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Is a guide to flashing via LMSA
HueyT said:
https://forum.xda-developers.com/moto-g7/how-to/to-stock-relock-boot-loader-google-fi-t3966959
Is a guide to flashing stock rom (your rom will be different but the steps are similar except Q rom has 10 sparsechunks while PIE rom only has 9)
---------- Post added at 10:20 PM ---------- Previous post was at 10:18 PM ----------
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Is a guide to flashing via LMSA
Click to expand...
Click to collapse
Okay I went back to stock and found that the issue was not present. I shall report this to the LineageOS devs or something. Is there anything else this could possibly be?
Once VZW drops CDMA and adopts GSM, this prob will be gone (1/2021)