I've flashed a number of ROMs on my XT1575 (thank you devs for much hard work). A week ago I noticed that the second greatest consumer of battery on my phone was Cellular Standby and my "Time Without A Signal" was running 35-65% even though I'm in the middle of Manhattan with strong LTE service. I've flashed three different ROMs, always wiping and doing clean installs, and I have the same problem with all three. Could this be a modem problem? Should I flash a stock modem or a custom modem? I've tried different settings and got the same result. What am I missing?
If you have a TWRP backup of your EFS I'd try restoring that.
Another thing to try might be grabbing the firmware that matches yours from this thread and flashing your modem again.
Code:
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
I'm not very familiar with flashing via ADB (I've done it but not often enough to be comfortable with it). I flash via TWRP all the time. Is there a method of reflashing the modem that I can do on the phone via TWRP or must I go the ADB route?
Related
so i did a restore to stock for the moto x pure on my style, and everything works; however, wifi does not turn on, the *#*#4636#*#* menu says that the supplicant is uninitialized, is there anything i can do to get it working again?
running ifconfig tiwlan0 returns no such device
I have root and twrp installed.
Having same issue. Restored stock and without root it works. After installing root the same problem occurred
search the site for the firmware. Download the firmware page and look for the file non-hlos.bin. Do the fastboot method but UNCAPS it. The file is in CAPS, rewrite the thing in lower case.
You may also have to flash the NON-HLOS.bin multiple times, it took me 3 flashes to get it to finally flash properly (There is no way to determine if it worked without booting android).
Go to your fastboot files folder
Open notepad
Paste this:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
Save it like flashmodem.bat in adb folder
Take from original decompressed ROM
NON-HLOS.BIN & fsg.mbn and copy those files in adb folder with the bat file.
Run it
Enjoy
Remember to remove your sim card
nitros12 said:
so i did a restore to stock for the moto x pure on my style, and everything works; however, wifi does not turn on, the *#*#4636#*#* menu says that the supplicant is uninitialized, is there anything i can do to get it working again?
running ifconfig tiwlan0 returns no such device
I have root and twrp installed.
Click to expand...
Click to collapse
zakoda said:
Having same issue. Restored stock and without root it works. After installing root the same problem occurred
Click to expand...
Click to collapse
Restore your stock backup and flash SuperSU 2.62 this should give you root and no problems with wifi.
After flashing 2.62 you can flash the latest SuperSU.
[email protected] said:
Restore your stock backup and flash SuperSU 2.62 this should gif you root and no problems with wifi.
After flashing 2.62 you can flash the latest SuperSU.
Click to expand...
Click to collapse
Forgot to update my post, solved by flashing the stock ROM and then flashing whatever I wanted on top
Ok, so this is an odd issue. I've had my N7 Grouper unlocked and have been running custom roms for a long time now, and about 6 months back I tossed on the All-F2FS version of Slimkat. Everything was running fine and has been since then, up until the last few days. Now the device just reboots randomly after it gets into the system. It runs fine in bootloader or recovery so I know it's not a loose battery connector as I've read about. I'm at a loss as to why and I gave up trying to find out.
I've since been trying to simply wipe my tablet and reset back to a clean install of the All-F2FS Slimkat as I've had or even tried a stock restore now. Nothing I do works at all. I've tried everthing from the modified All-F2FS TWRP 2.7.0.0 that I installed as a part of the move to F2F2 but although it reports that it's wiped everything fine, or flashed a new rom fine, it does nothing in truth. After a quick reboot its as if nothing happened at all. I've then tried to run things from adb/fastboot and I'm even after running all the commands in fastboot which all say they run fine (flashing, reformatting partitions, etc.) nothing at all actually happens to the N7.
Anyone else seen this or have any ideas?
Hello,
please try this command's:
Code:
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot erase boot
Then flash a FactoryImage! At least root and flash again.
Trafalgar Square said:
Hello,
please try this command's:
Code:
fastboot erase cache
fastboot erase system
fastboot erase userdata
fastboot erase recovery
fastboot erase boot
Then flash a FactoryImage! At least root and flash again.
Click to expand...
Click to collapse
I've tried all of those commands multiple times. I'm an old hat at rooting, unlocking, and running custom roms on Android so I've been doing literally everything I can think of. Every command shows that it completes successfully but nothing actually happens. I've tried fastboot erase commands, fastboot format commands, fastboot flash commands, and many many more. I've run six different versions of the factory image, everything from 4.0.0 to 5.1.1. The only errors I've ever seen while working with the tablet is while attempting to erase/format partitions within the recovery there are some errors about not being able to access the cache. I'll update this with the specific errors.
Anyone? I'm at a loss here. I've run everything I can think of and the commands always complete successfully, then don't actually work at all.
Hi,
I have G4 Plus XT1642 (retapac). It came shipped with 6.0.1 MPJ24.139-48 preinstalled.
Well i flashed, deleted, maybe bricked and then made it work again with the latest version i wanted to have (139-63) and then rooted it. Everything worked/works, but the wifi mac shows as 02 000000 or something (but no problem with that, wifi mac is fixed with some earlier backup i have, it also gets fixed when i flash to original).
But the worst thing is: Both IMEI show as 0. In the setting menu, and also when dialing the command *#06# (Both IMEIs show 0).
It gave some errors at fastboot because of "downgrade" or so, but i think that's not the issue.
I tried everything, also reflashed to my original version (ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip). Everything is fine, wifi mac displays as original also, but IMEIs still are 0.
No matter what I do, both IMEI show as 0, and SIM cards don't work ofcourse (they work, show carrier names etc but don't get accepted, ---> "emergency calls only", because IMEI is 0 i think.
Before you ask: No i don't have a very early TWRP backup from before flashing, deleted it because I had later backup I though everything was working, didn't try any SIM at that time.
How can I fix this? Is there any hope?
What gives me the little hope: At "boot thing" when I type fastboot getvar imei, it shows the correct imei! It doesn't list the second sim though.
Thanks in advance!
bauss1 said:
Hi,
I have G4 Plus XT1642 (retapac). It came shipped with 6.0.1 MPJ24.139-48 preinstalled.
Well i flashed, deleted, maybe bricked and then made it work again with the latest version i wanted to have (139-63) and then rooted it. Everything worked/works, but the wifi mac shows as 02 000000 or something (but no problem with that, wifi mac is fixed with some earlier backup i have, it also gets fixed when i flash to original).
But the worst thing is: Both IMEI show as 0. In the setting menu, and also when dialing the command *#06# (Both IMEIs show 0).
It gave some errors at fastboot because of "downgrade" or so, but i think that's not the issue.
I tried everything, also reflashed to my original version (ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip). Everything is fine, wifi mac displays as original also, but IMEIs still are 0.
No matter what I do, both IMEI show as 0, and SIM cards don't work ofcourse (they work, show carrier names etc but don't get accepted, ---> "emergency calls only", because IMEI is 0 i think.
Before you ask: No i don't have a very early TWRP backup from before flashing, deleted it because I had later backup I though everything was working, didn't try any SIM at that time.
How can I fix this? Is there any hope?
What gives me the little hope: At "boot thing" when I type fastboot getvar imei, it shows the correct imei! It doesn't list the second sim though.
Thanks in advance!
Click to expand...
Click to collapse
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/XT1642/
#for marshmallow
Try to flash modem files for your phone
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
#for nougat
BlackBeats said:
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/XT1642/
#for marshmallow
Try to flash modem files for your phone
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
#for nougat
Click to expand...
Click to collapse
Yes. Did exactly that. Flashed the files of XT1642_ATHENE_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip ... with the commands
Code:
fastboot oem fb_mode_set
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 system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Showed some "errors" at fastboot at some, but I think that was normal. And flashing worked.
But in the end, both IMEI are still 0.
Even reflashed the NON-HLOS.bin. IMEI numbers are still 0.
Additional information:
The original version this retapac XT1642 G4 plus came shipped with was MPJ24.139-48.
I then wanted to update to the latest non-nougat version, which is MPJ24.139-63.
I could not update directly to MPJ24.139-63 from MPJ24.139-48. (Because the internal recovery showed error, that flashed version must origin from MPJ24.139-23.4).
So I overflashed (with fastboot) to MPJ24.139-23.4. So the version then was even lower than it came shipped with lol. Then from MPJ24.139-23.4, used the internal recovery (not TWRP), to apply the OTA update file MPJ24.139-63. Since then the Wifi mac was 020000000 or something, sometimes random wifi disconnects, and imei 0. After going back to original again, wifi mac is fixed, but sim imei numbers still are 0.
Edit: not sure if the imei and wifi errors accured since MPJ24.139-23.4, or after the OTA update file, or sometime inbetween because i deleted something in TWRP.
bauss1 said:
Additional information:
The original version this retapac XT1642 G4 plus came shipped with was MPJ24.139-48.
I then wanted to update to the latest non-nougat version, which is MPJ24.139-63.
I could not update directly to MPJ24.139-63 from MPJ24.139-48. (Because the internal recovery showed error, that flashed version must origin from MPJ24.139-23.4).
So I overflashed (with fastboot) to MPJ24.139-23.4. So the version then was even lower than it came shipped with lol. Then from MPJ24.139-23.4, used the internal recovery (not TWRP), to apply the OTA update file MPJ24.139-63. Since then the Wifi mac was 020000000 or something, sometimes random wifi disconnects, and imei 0. After going back to original again, wifi mac is fixed, but sim imei numbers still are 0.
Click to expand...
Click to collapse
Try flashing nougat I guess downgrade created a problem
BlackBeats said:
Try flashing nougat I guess downgrade created a problem
Click to expand...
Click to collapse
I don't want nougat. Can I go back to MPJ24.139-63 from nougat? But maybe worth a try if nobody knows any other possibility
bauss1 said:
I don't want nougat. Can I go back to MPJ24.139-63 from nougat? But maybe worth a try if nobody knows any other possibility
Click to expand...
Click to collapse
Try removing oem fb set command
If it doesn't work then flash nougat then use 6.0.1 custom ROM
Edit fb_mode_set
Flashed everything again, without the fastboot oem fb_mode_set (MPJ24.139-48). Both IMEIs are still 0, everything else is fine though, original wifi mac.
---
Then took original over the air update it offered me (NPJ25.93-14). Installed without problems.
But, guess what.... it made things worse.
Now i am on NPJ25.93-14, the IMEIs still are 0, and the wifi mac address is at 02:00:00:00:00:00 again.
What I noticed is, in settings it shows the IMEI SV (Slot1) and IMEI SV (Slot2). They both changed to 08. I think they were 03 or so before.
Edit: In the boot recovery thing it says the usual stuff:
Battery OK (Charging)
flashing_unlocked
Software status: Official
...
So... updating to Nougat did not help, made things worse (wifi mac weird again, IMEI still 0).
Any other ideas?
Anyone looking for the solution to this problem, it has been fixed here: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
I am considering switching to Verizon and not sure if anyone’s successfully used Verizon on a Sprint 10, or even tried it.
I’m currently running stock Nougat, haven’t updated since July because HTC’s OTAs don’t play nice with TWRP last time I checked. Already manually unlocked my phone. Have not done SuperCID yet but will definitely do that before flashing anything.
Confused because AT&T and Tmo SIMs work fine and I get LTE instantly when I put them in - but when I put in a Verizon SIM (activated) I get nothing. I did enable Band 13 through cdmatool, and Verizon has Band 4 (which works fine with AT&T/Tmo) in my area, but no signal. This leads me to believe Sprint could have locked it on the stock rom, and enabling Verizon would be as simple as flashing leedroid or viper.
Or if that doesn’t work, I might have to RUU the latest Verizon update and hope for the best. And hopefully not completely brick my phone. Since I’m just testing at the moment, I want to be able to restore back to stock Sprint.
So the possibilities are: (after supercid)
1) flash leedroid or viper
2) select Sprint when installing
3) hope it was a lock on the Sprint rom and Verizon works
Or:
1) flash leedroid or viper
2) select Verizon when installing
Or:
1) erase modemst1 and modemst2
2) flash the Verizon radio over my current rom, no idea where to find a good .img for this
Or:
1) install the entire Verizon RUU
Any thoughts? Which method has the best chance of working? Can either of these brick my phone for good?
EDIT 1/26
Just tried wiping the radio, modemst1 and modemst2, and flashing the Verizon radio. Interestingly, sprint still works with this radio, though it may just be LTE that works. Verizon doesn't work, still thinks it's roaming just like on the sprint radio. So definitely a lock in the ROM.
Anyone wanting to try this - be aware that information such as unlock status are stored in the modemst partitions. So if you erase them, they will restore on the next reboot (anyone know what partition stores backups of these?) but if you manually unlocked your phone or added LTE bands with cdmatool, they will be restored to default.
Backup your radio partitions before doing anything:
Code:
dd if=/dev/block/mmcblk0p30 of=/sdcard/backup-radio.img
dd if=/dev/block/mmcblk0p39 of=/sdcard/backup-modemst1.img
dd if=/dev/block/mmcblk0p40 of=/sdcard/backup-modemst2.img
copy these to your computer.
To restore your sprint radios, boot to bootloader (not download mode) and:
Code:
fastboot flash radio "C:\path\to\files\backup-radio.img"
fastboot flash modemst1 "C:\path\to\files\backup-modemst1.img"
fastboot flash modemst2 "C:\path\to\files\backup-modemst2.img"
It might be possible to restore through dd, but it's extremely risky so use fastboot to do it.
Just struggled for the last 5 hours or so trying to get my Moto G5 Plus back to stock firmware. It turns out I had to install Pixel ROM to get any kind of cellular signal / SIM card reading, then reinstall what my best guess was as to the correct stock firmware leaving out the modemst1 and modemst2 fastboot commands, relock the bootloader, and then install the stock firmware again, leaving out the modemst1 and modemst2 fastboot commands again. Doesn't sound so bad, right? Well, if there was a more intuitive way of going about doing it, and better information as to which firmware you need (as there are about 15 different versions - I had to guess), it may have taken me 20 minutes total. Unbelievable.
Does anyone know why this is so difficult or is it simply by design? And why does the stock contain corrupt modem software? I'd expect it to be working in one, single package, including locking the bootloader.
Maybe I'm missing something here. Any ideas?