Related
Hi,
I have an Atrix HD with an unlocked bootloader and root access running on Bell Canada. Before getting my AHD, I was using an HTC HD7 running Deepshining Rom 7.8.
When driving around in my car with the phone connected to my handfree BT speakerphone, I would sometimes get a message that I have no cell service on my AHD. I tend to drive the same routes and this never happened with my HTC. I have this issue with all custom 4.2.2 roms I have tried. The baseband version is MB886_BP_100740.071.6561P.
Anyone else experience this issue?
Any information would be appreciated.
Thanks
audit13 said:
Hi,
I have an Atrix HD with an unlocked bootloader and root access running on Bell Canada. Before getting my AHD, I was using an HTC HD7 running Deepshining Rom 7.8.
When driving around in my car with the phone connected to my handfree BT speakerphone, I would sometimes get a message that I have no cell service on my AHD. I tend to drive the same routes and this never happened with my HTC. I have this issue with all custom 4.2.2 roms I have tried. The baseband version is MB886_BP_100740.071.6561P.
Anyone else experience this issue?
Any information would be appreciated.
Thanks
Click to expand...
Click to collapse
this is because of signal changing from 3g to lte or vice versa,, if you dont want that you can change prefrance to only lte or only hspa+ on *#*#4636#*#*
audit13 said:
Hi,
I have an Atrix HD with an unlocked bootloader and root access running on Bell Canada. Before getting my AHD, I was using an HTC HD7 running Deepshining Rom 7.8.
When driving around in my car with the phone connected to my handfree BT speakerphone, I would sometimes get a message that I have no cell service on my AHD. I tend to drive the same routes and this never happened with my HTC. I have this issue with all custom 4.2.2 roms I have tried. The baseband version is MB886_BP_100740.071.6561P.
Anyone else experience this issue?
Any information would be appreciated.
Thanks
Click to expand...
Click to collapse
Try the Mex Retail baseband -- is version QINARA_BP_100740.081.65.05p. I have great service with it (better than Stock AT&T JB actually).
//Due to my paranoia, I take different routes all the time. I just don't like the police seeing me take the same route over and over again....
Aingaran said:
this is because of signal changing from 3g to lte or vice versa,, if you dont want that you can change prefrance to only lte or only hspa+ on *#*#4636#*#*
Click to expand...
Click to collapse
Hi,
Would this be the same as changing option under mobile network or should I use your option to make it stick?
Thanks for your help.
skeevydude said:
Try the Mex Retail baseband -- is version QINARA_BP_100740.081.65.05p. I have great service with it (better than Stock AT&T JB actually).
Click to expand...
Click to collapse
Hi,
Is that the rom under your stock AHD rom thread? If it is, can I just flash it using cwm like I did with the untested Bell rom?
Edit: I should mention that I disable my data connection unless I'm checking my email or surfing the WWW.
audit13 said:
Hi,
Would this be the same as changing option under mobile network or should I use your option to make it stick?
Thanks for your help.
Hi,
Is that the rom under your stock AHD rom thread? If it is, can I just flash it using cwm like I did with the untested Bell rom?
Click to expand...
Click to collapse
ya, nearly same.... but once rebooted, it goes back to default, should change at every reboot.. and stock MR is available in that same thread and it is not CWM flashable.. you need to flash it through fastboot..
Aingaran said:
ya, nearly same.... but once rebooted, it goes back to default, should change at every reboot.. and stock MR is available in that same thread and it is not CWM flashable.. you need to flash it through fastboot..
Click to expand...
Click to collapse
Thanks. I'll try changing the preferred network using the hidden menu.
audit13 said:
Hi,
Would this be the same as changing option under mobile network or should I use your option to make it stick?
Thanks for your help.
Hi,
Is that the rom under your stock AHD rom thread? If it is, can I just flash it using cwm like I did with the untested Bell rom?
Edit: I should mention that I disable my data connection unless I'm checking my email or surfing the WWW.
Click to expand...
Click to collapse
Yes, but that rom only contains the MR system and is/was made for the stock AT&T kernel.
Download the fastboot and manually flash just the radio. No wipe required that way.
skeevydude said:
Yes, but that rom only contains the MR system and is/was made for the stock AT&T kernel.
Download the fastboot and manually flash just the radio. No wipe required that way.
Click to expand...
Click to collapse
Just downloaded the Mexico rom from Goo. Took quite a while. I'll have to do some research to figure out how to flash the radio. Thanks for your help.
audit13 said:
Just downloaded the Mexico rom from Goo. Took quite a while. I'll have to do some research to figure out how to flash the radio. Thanks for your help.
Click to expand...
Click to collapse
Extract the fastboot
Download the snapdragon fastboots (linked in fastboot guide)
Place the appropriate one in the folder with the fastboot's files
fastboot flash modem NON-HLOS.bin
skeevydude said:
Extract the fastboot
Download the snapdragon fastboots (linked in fastboot guide)
Place the appropriate one in the folder with the fastboot's files
fastboot flash modem NON-HLOS.bin
Click to expand...
Click to collapse
Okay, I have the NON-HLOS.bin file from the Mexico retail. I assume I have to do the following on my Windows machine:
1) install the adb/fastboot files to a single directory on my computer;
2) place the NON-HLOS.bin file in the adb/fastboot directory from step 1;
3) open a command prompt window as an administrator;
4) install the Motorola USB drivers and connect my booted phone with USB debugging enabled;
5) from the command line, type "adb reboot bootloader" and press the enter key to get my phone into AP Fastboot Flash mode;
6) from the command line, type "fastboot flash modem NON-HLOS.bin" and press enter; and
7) reboot the phone and check to made sure my baseband now says "QUINARA_BP_100740.081.65.05P".
If I want to flash back to the stock Bell baseband, I assume I would substitute the Mexico NON-HLOS.bin file for the Bell file.
Pardon my noobness. It's just that I don't want to screw up my phone. It's barely 3 months old.
audit13 said:
Okay, I have the NON-HLOS.bin file from the Mexico retail. I assume I have to do the following on my Windows machine:
1) install the adb/fastboot files to a single directory on my computer;
2) place the NON-HLOS.bin file in the adb/fastboot directory from step 1;
3) open a command prompt window as an administrator;
4) install the Motorola USB drivers and connect my booted phone with USB debugging enabled;
5) from the command line, type "adb reboot bootloader" and press the enter key to get my phone into AP Fastboot Flash mode;
6) from the command line, type "fastboot flash modem NON-HLOS.bin" and press enter; and
7) reboot the phone and check to made sure my baseband now says "QUINARA_BP_100740.081.65.05P".
If I want to flash back to the stock Bell baseband, I assume I would substitute the Mexico NON-HLOS.bin file for the Bell file.
Pardon my noobness. It's just that I don't want to screw up my phone. It's barely 3 months old.
Click to expand...
Click to collapse
Yes to all, but with step 6, make damn sure you're using the fastboot from the guide. Using the SDK fastboot is the cause of 99% of the fastboot questions we answer.
LoL @ 3 Months. Flashed my first android rom (2.5 years ago) within 4 hours of having my Bravo -- and I had never even used an Android Phone before that. Found XDA during the initial charge, read up on my phone, learned a bit, and flashed away. Luckily I'm a quick studier and learner. Didn't even join XDA till 6 months later. Saw some questions I could answer, joined, and answered them....now I compile roms and am learning Java. XDA is a great place if you use it properly.
skeevydude said:
Yes to all, but with step 6, make damn sure you're using the fastboot from the guide. Using the SDK fastboot is the cause of 99% of the fastboot questions we answer.
LoL @ 3 Months. Flashed my first android rom (2.5 years ago) within 4 hours of having my Bravo -- and I had never even used an Android Phone before that. Found XDA during the initial charge, read up on my phone, learned a bit, and flashed away. Luckily I'm a quick studier and learner. Didn't even join XDA till 6 months later. Saw some questions I could answer, joined, and answered them....now I compile roms and am learning Java. XDA is a great place if you use it properly.
Click to expand...
Click to collapse
Thanks for the confirmation. I just finished flashing the radio and it's all good so far. I used the fastboot files from the Myth Tools and they worked without any issues. Maybe I got lucky:fingers-crossed:
I've rooted some Samsung and HTC phones using the great guides on this forum and a helping hand from users like yourself.
Could I compile roms? I doubt it. I don't think I'm anywhere close to being that competent.
audit13 said:
Thanks for the confirmation. I just finished flashing the radio and it's all good so far. I used the fastboot files from the Myth Tools and they worked without any issues. Maybe I got lucky:fingers-crossed:
I've rooted some Samsung and HTC phones using the great guides on this forum and a helping hand from users like yourself.
Could I compile roms? I doubt it. I don't think I'm anywhere close to being that competent.
Click to expand...
Click to collapse
The files with Myth are the proper ones. I think most Myth Tools issues are from when/if whomever followed an SDK Install Guide that had whomever add the SDK fastboot to the system's $PATH. If you've never installed the SDK or only use Myth, you'll be fine.
Thanks. Remember back when rooting was as simple as installing an APK from the market? Good times back then.
You probably could compile them, its fixing it when the compile breaks that's the actual hard part (or waiting on upstream to fix it that's the really hard part ....waiting sucks )
downloaded the mexico retail from goo.im and extracted the .zip, but where is the NON-HLOS.bin file?
?
davwman said:
downloaded the mexico retail from goo.im and extracted the .zip, but where is the NON-HLOS.bin file?
?
Click to expand...
Click to collapse
Try here: http://sbf.droid-developers.org/dinara/list.php
I have tried a reset to stock, and regardless of my ROM (clean flash every time) I cannot receive any bars, after some research I feel I may need a new modem.img or some advice! Was running fine, currently running titan prime 1.1.3 (/64).
I do have an IMEI number and APN shows up but when I go to network operators there is an "error while searching for networks". Have taken SIM out and rebooted.
Regards
Hello!
Restore your original stock firmware.
Are you familiar with this procedure?
Mario
M4puk said:
Hello!
Restore your original stock firmware.
Are you familiar with this procedure?
Mario
Click to expand...
Click to collapse
Yes I have restored to 4.4.4 and still have no service. Bell Internet APN shows up though. I may require a walkthrough,
Hi there, having a feeling you've got the same problem as I had.
after flashing stock firmware 4.4.4 or 5.0.2 the phone is unable to enable the simcards, leaving you with no bars, error signs and greyed out options in the settings.
Download this package and extract to a folder, delete the NON-HLOS.bin that comes with it and copy your original stock NON-HLOS.bin to this folder. run the BAT file.
Mega
I think there's a incompatibility problem with ADB and flash software provided with the stock rom packages that crops up on rare occasions.
The package I linked uses a tool called "fastboot" while stock packages use "mfastboot" and using the fastboot tool and bat provided in this package I have successfully flashed the stock modem file using these tools and it works perfectly!
C:\Users\Ragarok\Desktop\Reparar Señal Modem moto g 2 xt1068\Modem>adb devices
adb server is out of date. killing...
* daemon started successfully *
Click to expand...
Click to collapse
ragarok said:
Hi there, having a feeling you've got the same problem as I had.
after flashing stock firmware 4.4.4 or 5.0.2 the phone is unable to enable the simcards, leaving you with no bars, error signs and greyed out options in the settings.
Download this package and extract to a folder, delete the NON-HLOS.bin that comes with it and copy your original stock NON-HLOS.bin to this folder. run the BAT file.
Mega
I think there's a incompatibility problem with ADB and flash software provided with the stock rom packages that crops up on rare occasions.
The package I linked uses a tool called "fastboot" while stock packages use "mfastboot" and using the fastboot tool and bat provided in this package I have successfully flashed the stock modem file using these tools and it works perfectly!
Click to expand...
Click to collapse
Thank you thank you thank you!!!
I scratched my head so much over this, thank you! It works like a charm.
Can you provide another like for the "NON-HLOS.bin" file as the one given in the link is no longer active. It would be very helpful. Thanks.
Hey I'm having this problem and I've found nothing else to help
I've seen this thread here http://forum.xda-developers.com/nexus-6/help/rooted-nexus-6-updating-to-android-6-0-t3228796 but It doesn't really answer my question. I've also read that I can just flash the system.img, boot.img, and recovery.img without losing data, but will I lose my root or anything else by doing that?
steam374 said:
I've seen this thread here http://forum.xda-developers.com/nexus-6/help/rooted-nexus-6-updating-to-android-6-0-t3228796 but It doesn't really answer my question. I've also read that I can just flash the system.img, boot.img, and recovery.img without losing data, but will I lose my root or anything else by doing that?
Click to expand...
Click to collapse
What is required for root work?
Root adds a binary file and some scripts to the /system partition
What happens when you flash a system.img?
Everything in the /system partition is wiped and replaced with the contents of the system.img
So, basically as long as I flash super su in twrp I'll be good to go?
steam374 said:
So, basically as long as I flash super su in twrp I'll be good to go?
Click to expand...
Click to collapse
Well, not quite, because on 6.0, you also need a modified boot.img (kernel) too, to get root.
The main question is, are you encrypted? If so it is fairly easy and I will let you know what to do. But if you are not encrypted there is an extra step.
danarama said:
Well, not quite, because on 6.0, you also need a modified boot.img (kernel) too, to get root.
The main question is, are you encrypted? If so it is fairly easy and I will let you know what to do. But if you are not encrypted there is an extra step.
Click to expand...
Click to collapse
Yeah, I'm totally stock besides root and twrp. I used the nexus tool kit to obtain root and an unlocked bootloader.
steam374 said:
Yeah, I'm totally stock besides root and twrp. I used the nexus tool kit to obtain root and an unlocked bootloader.
Click to expand...
Click to collapse
OK.
So flash system.img and boot.img (you may also want to flash bootloader.img and radio.img). You do not need recovery.img.
Boot android as 100% stock until it starts up. This will likely replace TWRP with the stock recovery.img too. If you don't boot with the stock boot.img, you will likely get a bootloop once rooting. (unencrypted users need to flash a modified stock boot.img instead of stock, that does not enforce encryption and boot with that).
Flash chainfires modified boot.img, TWRP.img then boot into recovery and flash latest SuperSU beta (2.52 I think)
danarama said:
OK.
So flash system.img and boot.img (you may also want to flash bootloader.img and radio.img). You do not need recovery.img.
Boot android as 100% stock until it starts up. This will likely replace TWRP with the stock recovery.img too. If you don't boot with the stock boot.img, you will likely get a bootloop once rooting. (unencrypted users need to flash a modified stock boot.img instead of stock, that does not enforce encryption and boot with that).
Flash chainfires modified boot.img, TWRP.img then boot into recovery and flash latest SuperSU beta (2.52 I think)
Click to expand...
Click to collapse
Okay! Thank you very much! This is the help I needed.
steam374 said:
Okay! Thank you very much! This is the help I needed.
Click to expand...
Click to collapse
No probs
danarama said:
No probs
Click to expand...
Click to collapse
So I was successfully able to flash Android 6.0 thanks to your steps. Is there any benefit to updating my radio? I just fear I could brick my device because I remember the old Evo 3D days when that happened.
steam374 said:
So I was successfully able to flash Android 6.0 thanks to your steps. Is there any benefit to updating my radio? I just fear I could brick my device because I remember the old Evo 3D days when that happened.
Click to expand...
Click to collapse
Older HTC devices did seem to have issues with a dodgy radio flash. if you disconnected the connection / power during a radio flash, it could corrupt the filesystem and wasn't easy to fix. Often thought to be a brick. I saw that commonly on the Original HTC Desire.
The great thing with Nexus devices are that you can fastboot format partitions which will repair the file system, so you shouldn't have an issue with bricking from flashing a radio. I literally haven't seen a radio brick for years. That said, still be careful when it comes to power and USB connectivity.
Different radios may work better for you. There are too many variables to say that Radio X will work better than Radio Y for you, but there definitely can be improvements to be found by trying different ones.
danarama said:
Older HTC devices did seem to have issues with a dodgy radio flash. if you disconnected the connection / power during a radio flash, it could corrupt the filesystem and wasn't easy to fix. Often thought to be a brick. I saw that commonly on the Original HTC Desire.
The great thing with Nexus devices are that you can fastboot format partitions which will repair the file system, so you shouldn't have an issue with bricking from flashing a radio. I literally haven't seen a radio brick for years. That said, still be careful when it comes to power and USB connectivity.
Different radios may work better for you. There are too many variables to say that Radio X will work better than Radio Y for you, but there definitely can be improvements to be found by trying different ones.
Click to expand...
Click to collapse
Okay, thanks again you're always very helpful I also didn't update the bootloader is that okay?
steam374 said:
Okay, thanks again you're always very helpful I also didn't update the bootloader is that okay?
Click to expand...
Click to collapse
If it boots up, then yes that is fine. Only may see an issue with older 5.0 bootloaders on 6.0 but 5.1.x is fine.
danarama said:
If it boots up, then yes that is fine. Only may see an issue with older 5.0 bootloaders on 6.0 but 5.1.x is fine.
Click to expand...
Click to collapse
Okay, that should conclude my questions. Sorry for all the noob questions. I did all my major custom rom flashing back when the evo 3d was just released. Things are still very similar, but there's always that extra bit to learn. Thanks again for all the help and have a great day.
steam374 said:
Okay, that should conclude my questions. Sorry for all the noob questions. I did all my major custom rom flashing back when the evo 3d was just released. Things are still very similar, but there's always that extra bit to learn. Thanks again for all the help and have a great day.
Click to expand...
Click to collapse
Hey, don't worry. We prefer "noob" questions to "noob-help-me-i-screwed-up" requests
i am sorry if this method did anything wrong with your device, but i already mentioned that this tweak worked for me and i would not be responsible for anyone else.
muklshakya123 said:
Now You Can Easily Fix Broken VoLTE, Follow All The Steps Carefully And Voilla You Are Done With Your Job
STEPS :-
1. Your Device Must Have Bootloader Unlocked With TWRP Installed.
2. Download Persist.zip From Attachments.
3. Put Extracted File In TWRP/Backups/XXXXX/XXXX Folder.
4. Go To TWRP And Restore Persist Backup.
5. Reboot And Check If VoLTE Works Fine Now.
P.S :- This Guide Is Personally Tested By Me On My Moto G5S Plus XT1804 (Still I Am Not Responsible If Anything Goes Wrong, Just Follow The Steps Carefully)
Credits
@akshu2697 For Persist Backup
Me For Testing On XT1804
HIT THANKS IF IT HELPED
Click to expand...
Click to collapse
Good work bro,share this method to as many people as possible to help them all
This worked for my xt1805 that had no LTE after installing a custom ROM then restoring stock. Had no IMEI at first and installing a new custom ROM fixed that, but tried everything including deleting the modem environment partition (e.g. here) but only this persist solution would restore the LTE.
Many thanks!
Can anyone help me and elaborate how to restore the persist file?
EDIT: I used older TWRP, I flashed newer one and I got it. Thanks.
Will this work on an XT1803?
@lynxblaine yes it'll work
Hi,
I restored this extracted file using TWRP and now my IMEI is 0.
Here are the steps I did to get back my IMEI. none of these worked. Please advice.
1. Locked bootloader and went back to stock ROM (version NPSS26.116-61-5 with march update)
2. Did erase of modemst1 &t2 with out any success
3. Flashed just Non-Hlos and Fsg and DSP only.
4. Flashed various ROMS like Pixel experience, Validus, Resurrection Remix, franken ROM. Didn't even get 3G after this.
None of this seem to restore my imei.
But when I did fastboot getvar all I am able to see one IMEI of 15 digits.. So I don't think I bricked my phone.
You should try the restore method in this section of forums for your imei it worked flawlessly for me.
muklshakya123 said:
Now You Can Easily Fix Broken VoLTE, Follow All The Steps Carefully And Voilla You Are Done With Your Job
STEPS :-
1. Your Device Must Have Bootloader Unlocked With TWRP Installed.
2. Download Persist.zip From Attachments.
3. Put Extracted File In TWRP/Backups/XXXXX/XXXX Folder.
4. Go To TWRP And Restore Persist Backup.
5. Reboot And Check If VoLTE Works Fine Now.
For Those Who Are Facing Green Cam Issue
Download persist_fix.zip And Restore Persist Only (Don't Restore EFS This Time)
P.S :- This Guide Is Personally Tested By Me On My Moto G5S Plus XT1804 (Still I Am Not Responsible If Anything Goes Wrong, Just Follow The Steps Carefully)
Credits
@akshu2697 For Persist Backup
Me For Testing On XT1804
HIT THANKS IF IT HELPED
Click to expand...
Click to collapse
flashed from your persist fix zip... imei went 0, and now i can't fix it. Kindly share your efs backup or provide any help if you can...
@caballerobhanu first restore your imei following the guide mentioned in another thread in this section and after that follow my guide. And most importantly follow all these steps on latest march stock rom
muklshakya123 said:
@caballerobhanu first restore your imei following the guide mentioned in another thread in this section and after that follow my guide. And most importantly follow all these steps on latest march stock rom
Click to expand...
Click to collapse
hey, i tried to restore it, but no matter what i do, i am not able to recover it.
caballerobhanu said:
hey, i tried to restore it, but no matter what i do, i am not able to recover it.
Click to expand...
Click to collapse
Same for me as well. I tried each and every rom but still no IMEI. No EFS backup available as well:crying::crying:
sreekanthdb said:
Same for me as well. I tried each and every rom but still no IMEI. No EFS backup available as well:crying::crying:
Click to expand...
Click to collapse
U have to restore these on stock rom bro
---------- Post added at 03:38 AM ---------- Previous post was at 03:38 AM ----------
sreekanthdb said:
Same for me as well. I tried each and every rom but still no IMEI. No EFS backup available as well:crying::crying:
Click to expand...
Click to collapse
For imei flash validus then rebopt Erase modemst1 modemst2... Or flash rr
s.k.rajput said:
U have to restore these on stock rom bro
---------- Post added at 03:38 AM ---------- Previous post was at 03:38 AM ----------
For imei flash validus then rebopt Erase modemst1 modemst2... Or flash rr
Click to expand...
Click to collapse
Did that as well. Flashed Validus Rom, Pixel Experience, Resurrection Remix, AOSP Extended Rom and Franken ROM. No success on any of the roms.
PS: I went to Moto service center today and asked them if they will restore software. They said for unlocked bootloaders they'll not do it.. :crying: Guess I need to wait till OREO is officially released.
sreekanthdb said:
Did that as well. Flashed Validus Rom, Pixel Experience, Resurrection Remix, AOSP Extended Rom and Franken ROM. No success on any of the roms.
PS: I went to Moto service center today and asked them if they will restore software. They said for unlocked bootloaders they'll not do it.. :crying: Guess I need to wait till OREO is officially released.
Click to expand...
Click to collapse
Flash validus/rr boot... Then reboot to Bootloader... Islf imei is still null... Then do erade modemst1 modemst2 commands
s.k.rajput said:
Flash validus/rr boot... Then reboot to Bootloader... Islf imei is still null... Then do erade modemst1 modemst2 commands
Click to expand...
Click to collapse
Done that. I flashed all the above mentioned roms and after boot there's no IMEI. so I erased modemst1 & t2. but not working
s.k.rajput said:
Flash validus/rr boot... Then reboot to Bootloader... Islf imei is still null... Then do erade modemst1 modemst2 commands
Click to expand...
Click to collapse
thing is signal is there, 4g is there, data can be used, but imei = 0.
caballerobhanu said:
thing is signal is there, 4g is there, data can be used, but imei = 0.
Click to expand...
Click to collapse
That's strange... As usually signal wont come if imei is null
s.k.rajput said:
That's strange... As usually signal wont come if imei is null
Click to expand...
Click to collapse
Yeah, I tried RR vali aex, nothing was happening so I reverted to stock and locked the bootloader and submitted it to service center , they might be able to do something here. But they said your phone was rooted and we can't help you here. We can replace PCB which will cost you around 9-10k... So will go back tomorrow to collect.
Then will try something else.
caballerobhanu said:
Yeah, I tried RR vali aex, nothing was happening so I reverted to stock and locked the bootloader and submitted it to service center , they might be able to do something here. But they said your phone was rooted and we can't help you here. We can replace PCB which will cost you around 9-10k... So will go back tomorrow to collect.
Then will try something else.
Click to expand...
Click to collapse
U lost imei & locked bootloader y tho?? Some peeps who did the same thing are unable to get unlock code from Moto... U need to contact them via social media to get if u dont get the code from official site... Also u cant be able to use data or ur device will shows signals if u have imei lost
I was trying to install Lineage 16.0 OS and Magisk Root my android but in the process I got some trouble when tried to install TWRP on IT (TWRP works fine when I flashboot it from pc but not when I try to install it, causes slot issues). After that I performed a total wipe to "clear" the phone system (I never know when is needed to wipe but I wanted to have the cleanest setup) and installed just the Lineage, then It worked fine besides it got no way to connect to the internet. The wi-fi just doesn't turn on and the SIM Cards aren't detected.
After that I found out that my phone wasn't registered with any IMEI and I tried two other Stock ROMs trying to get my internet back but neither seemed to work. All I wanna know is how do I got my Moto X4 with Lineage 16.0 OS working fine? I think register the IMEI's I got here would solve the problem, but I don't find anywhere how do I repair the IMEI on a X4 Cortex-A53 (Qualcomm). The other solutions I found here on the forum consist of trying to flash some Stock ROMs until it works xD.
I wonder if there's a way to replace back my IMEI and still keep the Lineage OS
Obs 1: Before I flashed my phone, It had a up to date 9.0 android here in Brazil and I was using a SIM Card from TIM.
Obs 2: The Stock ROM's I tried to flash it back were "XT1900-6_PAYTON_RETBR_9.0_PPWS29.69-26-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" and the other one that I've alredy deleted I think it was a RETAIL one.
Please help, guys
Does you created full backup via TWRP before install LineageOS? If "yes" please restore EFS partition, and all will be fine, I hope.
Lennon_ said:
I was trying to install Lineage 16.0 OS and Magisk Root my android but in the process I got some trouble when tried to install TWRP on IT (TWRP works fine when I flashboot it from pc but not when I try to install it, causes slot issues). After that I performed a total wipe to "clear" the phone system (I never know when is needed to wipe but I wanted to have the cleanest setup) and installed just the Lineage, then It worked fine besides it got no way to connect to the internet. The wi-fi just doesn't turn on and the SIM Cards aren't detected.
After that I found out that my phone wasn't registered with any IMEI and I tried two other Stock ROMs trying to get my internet back but neither seemed to work. All I wanna know is how do I got my Moto X4 with Lineage 16.0 OS working fine? I think register the IMEI's I got here would solve the problem, but I don't find anywhere how do I repair the IMEI on a X4 Cortex-A53 (Qualcomm). The other solutions I found here on the forum consist of trying to flash some Stock ROMs until it works xD.
I wonder if there's a way to replace back my IMEI and still keep the Lineage OS
Obs 1: Before I flashed my phone, It had a up to date 9.0 android here in Brazil and I was using a SIM Card from TIM.
Obs 2: The Stock ROM's I tried to flash it back were "XT1900-6_PAYTON_RETBR_9.0_PPWS29.69-26-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml" and the other one that I've alredy deleted I think it was a RETAIL one.
Please help, guys
Click to expand...
Click to collapse
I had this problem days ago and the TWRP EFS restore did not fix it. I just had a "0" as an IMEI.
Someone over in the dev section told me to flash 8.1 in fastboot, boot and then flash the latest 9.0 it worked perfect and all my info is back.
@johnjingle Which version of 8.1 did you use? I'm having the same issue even with the 8.1 I flashed.
crazyramen said:
@johnjingle Which version of 8.1 did you use? I'm having the same issue even with the 8.1 I flashed.
Click to expand...
Click to collapse
The first release of 8.1. Nothing worked at all until I flashed the latest 9.0 update.
johnjingle said:
The first release of 8.1. Nothing worked at all until I flashed the latest 9.0 update.
Click to expand...
Click to collapse
I do not have the rules and i don't need to get kicked posting a link, I went to lolinet and used the 46-13 update which made the imei, esn, etc null. then flashing 9.0 fixed the radio/modem etc.
johnjingle said:
I do not have the rules and i don't need to get kicked posting a link, I went to lolinet and used the 46-13 update which made the imei, esn, etc null. then flashing 9.0 fixed the radio/modem etc.
Click to expand...
Click to collapse
Try reflash NON-HLOS.bin and fsg.mbn from ADB, i have the same problem with diferent rom in my X4, find your model (1-2-4-6-7) here and flash those files
HTML:
https://mirrors.lolinet.com/firmware/moto/payton/official/
Datclefxuj said:
Try reflash NON-HLOS.bin and fsg.mbn from ADB, i have the same problem with diferent rom in my X4, find your model (1-2-4-6-7) here and flash those files
HTML:
https://mirrors.lolinet.com/firmware/moto/payton/official/
Click to expand...
Click to collapse
How do I flash just those files? What partitions will they go to?
---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------
johnjingle said:
I do not have the rules and i don't need to get kicked posting a link, I went to lolinet and used the 46-13 update which made the imei, esn, etc null. then flashing 9.0 fixed the radio/modem etc.
Click to expand...
Click to collapse
Thanks for the help, but I've tried all that and am not getting anything. I have a new moto x4 also, the same model. I tried backing up everything in TWRP and copying it over, but am not getting any luck.
crazyramen said:
How do I flash just those files? What partitions will they go to?
---------- Post added at 09:26 PM ---------- Previous post was at 09:25 PM ----------
Thanks for the help, but I've tried all that and am not getting anything. I have a new moto x4 also, the same model. I tried backing up everything in TWRP and copying it over, but am not getting any luck.
Click to expand...
Click to collapse
Dowload the full stock rom of your model, unzip the rom and find those files, in cmd promt, use abd
Flash modem NON-HLOS. bin
Flash fsg fsg.mbn
Datclefxuj said:
Dowload the full stock rom of your model, unzip the rom and find those files, in cmd promt, use abd
Flash modem NON-HLOS. bin
Flash fsg fsg.mbn
Click to expand...
Click to collapse
I tried that... still a 0 for IMEI...
I have an XT1900-1, that's retus, right?
crazyramen said:
I tried that... still a 0 for IMEI...
I have an XT1900-1, that's retus, right?
Click to expand...
Click to collapse
Maybe nougat or oreo versión, try with a direfent stock rom (amz, ret, fi), I dont know more options, i try 5-6 stock roms to find one works in my tx1900-4
Dang. Ok I guess I'll just go through all the versions on lolinet. Thanks for all the advice
Hi Guys, thanks for your cooperation on this post, I'm able to recover my phone thanks to you. What I did was flash the fsg and NON-HLOS files from the retail 7.1.1, then upgraded to retail 8.0 and then go to the last retbr 9.0 firmware, cuz, I'm from Brazil, so thank you Guys, you're all awesome.
omegajoey said:
Hi Guys, thanks for your cooperation on this post, I'm able to recover my phone thanks to you. What I did was flash the fsg and NON-HLOS files from the retail 7.1.1, then upgraded to retail 8.0 and then go to the last retbr 9.0 firmware, cuz, I'm from Brazil, so thank you Guys, you're all awesome.
Click to expand...
Click to collapse
Hi man, I'm in a almost identical situation as yours, so I tried to do the same as you said in this post. I have a XT1900-6, using TIM carrier.
I flashed retail 7.1.1 but still got no signal or wifi, I have mac address tho, but anyway, how can I reflash fsg and NON-HLOS? in fastboot?
Thanks in advance
-------------
EDIT:
I've managed to regain mobile data by flashing the the NON-HLOS.bin and erase modemst1 and 2 with XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (actually running android 7.1.1) but still I have no wifi
EDIT 2:
After that I decided to flash the whole rom XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and now my Moto X4 is fully functional with mobile and wifi connections.
mariotullece said:
Hi man, I'm in a almost identical situation as yours, so I tried to do the same as you said in this post. I have a XT1900-6, using TIM carrier.
I flashed retail 7.1.1 but still got no signal or wifi, I have mac address tho, but anyway, how can I reflash fsg and NON-HLOS? in fastboot?
Thanks in advance
-------------
EDIT:
I've managed to regain mobile data by flashing the the NON-HLOS.bin and erase modemst1 and 2 with XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (actually running android 7.1.1) but still I have no wifi
EDIT 2:
After that I decided to flash the whole rom XT1900-1_PAYTON_FI_9.0_PPWS29.69-39-2-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip and now my Moto X4 is fully functional with mobile and wifi connections.
Click to expand...
Click to collapse
Great!, the principal problem is find the "drivers" of the model, when you find it, you can flash any version compatible (FI, RT, AMZ) and flash only NON-HLOS and fsg (i don´t need erase the modem but isn´t bad idea). My X4 is XT900-4 version, and flash any XT900-6 version and works, be careful if you flash an incompatible version or you have a hardbrick. If you dont want reflash NON-HLOS and fsg, overwrite the files in the same folder on the rom and flash whole version, when reboot de system the sim and wifi are works. The only problem I have is cannot update via OTA, because it isn´t the same version of the chip and firmware
hi guys, i have moto x4 xt1900-2 flashed ppws29.69.26-4 and lost wifi and network signal and shows IMEI is 0. my x4 bootloader was locked during flashing the said stock rom as it contains the cmd as fastboot oem lock but i didnt notice that while flashing that rom. now my moto x4 is not detecting any wifi and signal..not able to flash any rom through flashing as it showing that flashing permission denied..please help me....
thanks in advance
rayudu123 said:
hi guys, i have moto x4 xt1900-2 flashed ppws29.69.26-4 and lost wifi and network signal and shows IMEI is 0. my x4 bootloader was locked during flashing the said stock rom as it contains the cmd as fastboot oem lock but i didnt notice that while flashing that rom. now my moto x4 is not detecting any wifi and signal..not able to flash any rom through flashing as it showing that flashing permission denied..please help me....
thanks in advance
Click to expand...
Click to collapse
fixed ?
علاء