Hi,
I received my Le Max 2 a couple days ago and all was ok, except the fingerprint sensor worked 2-3 times then just stopped recognising anything at all.
I flashed LineageOS 15.1 (Oreo) today in the hopes it would fix the issue. Later I read in the forums here that modem firmware handles the fingerprint.
Read through a few posts, most notably: CN 26S 05.09 might be the best modem firmware
Now to the problem:
I am not new to flashing, it's not my first (or second ) time using ADB and Fastboot tools, but for the love of God, I cannot flash modem..
I downloaded various modems from the aforementioned link. I tried flashing via TWRP, no errors reported (also tried wiping cache/dalvik after flash). I also tried extracting NON-HLOS.bin and flashing via fastboot.
In both cases, I get no errors, everything goes through, but my Baseband version remains at: [MPSS.TH.2.0.c1.9-00050-M8996FAAAANAZM-1 1 [Aug 21 2016 15:00:00]] (and more importantly, the fingerprint reader does not work).
The only thing I haven't tried is erasing the modem "partition" using fastboot before flashing (and I'm reluctant to do so because if erase succeeds and flash fails again, I don't want to be stuck with a 5.7-inch device with no wireless capability).
If it makes any difference, the model is X820 (at least, came from the factory like that ). 6/128 GB option.
Bootloader was unlocked from the factory (seemed strange to me).
When I ran fastboot oem unlock, it reported that bootloader was already unlocked.
fastboot oem device-info returns the following:
Code:
D:\LeEcoMax2>fastboot oem device-info
...
(bootloader) Device product name: [le_x2_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Display panel:
OKAY [ 0.073s]
finished. total time: 0.076s
Any help is appreciated.
Thanks.
EDIT:
I apologise, looks like the radio is flashing fine, the ...c1.9-00050... part and the timestamp had changed, I just noticed this morning. Stock was ...00033...
I was under the impression that c1.9 implied China, 19S (or something like that). I noticed the change when my second SIM card showed "No Service" last night and after flashing 26S radio at 4 AM, I just went to bed, but this morning I noticed full level (no discrete "bars" on Lineage 15.1 ). So flashing was successful.
Anyway, I'm back to square one, fingerprint sensor is still not working.
Afaik 0050 modem and 466d firmware is the best, at least for oreo
where do i get that modem and firmware from?
ankerede said:
where do i get that modem and firmware from?
Click to expand...
Click to collapse
466D -> https://yadi.sk/d/woKdrlRrv8yhr/Для разработчиков
Heyyo, I'm the dude who made that 26s firmware thread long ago.
So since then I've learned the difference between modem firmware and full firmware.
I host FULL firmware links on my LineageOS 15.1 x2 thread. I'd recommend those over the yadisk modem only firmwares.
https://forum.xda-developers.com/le...x-lineageos-15-1-oreo-leeco-le-max-2-t3771577
Try them out. See which one works best for you as the experience flashing full firmware feels different to everyone.
ThE_MarD said:
Heyyo, I'm the dude who made that 26s firmware thread long ago.
So since then I've learned the difference between modem firmware and full firmware.
I host FULL firmware links on my LineageOS 15.1 x2 thread. I'd recommend those over the yadisk modem only firmwares.
https://forum.xda-developers.com/le...x-lineageos-15-1-oreo-leeco-le-max-2-t3771577
Try them out. See which one works best for you as the experience flashing full firmware feels different to everyone.
Click to expand...
Click to collapse
Sorry, a newbie question. If I flash the full firmware does that interfere with a custom rom? Do I have to re-flash the rom afterwards? (I'm not using lineage right now)
surfersea said:
Sorry, a newbie question. If I flash the full firmware does that interfere with a custom rom? Do I have to re-flash the rom afterwards? (I'm not using lineage right now)
Click to expand...
Click to collapse
Heyyo, firmware is separate from ROM. I know it is a bit confusing as some manufacturers call their ROM's firmware but firmware in the proper sense means the hardware firmware and ROM means Android operating system.
You may flash any firmware from my first post at any time via TWRP and it will not require reinstalling your ROM or Gapps.
ThE_MarD said:
Heyyo, firmware is separate from ROM. I know it is a bit confusing as some manufacturers call their ROM's firmware but firmware in the proper sense means the hardware firmware and ROM means Android operating system.
You may flash any firmware from my first post at any time via TWRP and it will not require reinstalling your ROM or Gapps.
Click to expand...
Click to collapse
I hijack a little the discussion toward fingerprint, which was the reason for the original post btw:
I both tried the 466d and the 20s full firmwares but the fingerprint didn't resuscitate (it worked when the phone was brand new then after the first rom flashing it stopped and never resumed).
Any suggestion?
And just to speculate about it, how can it happen ? Does the rom interfere with the fingerprint part of the firmware?
If so it's strange because I read in multiple thread of people with the same rom both with the fingerprint running and not running.
I read also about a possible problem with the fast charging feature. Is the fingerprint hardware really sensitive to the fast charge?
surfersea said:
I hijack a little the discussion toward fingerprint, which was the reason for the original post btw:
I both tried the 466d and the 20s full firmwares but the fingerprint didn't resuscitate (it worked when the phone was brand new then after the first rom flashing it stopped and never resumed).
Any suggestion?
And just to speculate about it, how can it happen ? Does the rom interfere with the fingerprint part of the firmware?
If so it's strange because I read in multiple thread of people with the same rom both with the fingerprint running and not running.
I read also about a possible problem with the fast charging feature. Is the fingerprint hardware really sensitive to the fast charge?
Click to expand...
Click to collapse
Hmm tbh not too sure why FP readers can go bad. It could be a hardware defect as some people have reported even reverting back to EUI ROM doesn't fix it as it still will not work.
At that point the only fix is to replace the fingerprint reader... Does your Le Max 2 still have any warranty? If so I'd recommend flashing back to the EUI ROM version it came with and lock your bootloader again and then contacting LeEco or the vendor you purchased it from for repairs.
Usually though after flashing a custom ROM for the first time, upgrading the firmware of the Le Max 2 resolves it as I'm guessing the source code for the kernel requires 19s or higher firmware.
ThE_MarD said:
Hmm tbh not too sure why FP readers can go bad. It could be a hardware defect as some people have reported even reverting back to EUI ROM doesn't fix it as it still will not work.
At that point the only fix is to replace the fingerprint reader... Does your Le Max 2 still have any warranty? If so I'd recommend flashing back to the EUI ROM version it came with and lock your bootloader again and then contacting LeEco or the vendor you purchased it from for repairs.
Usually though after flashing a custom ROM for the first time, upgrading the firmware of the Le Max 2 resolves it as I'm guessing the source code for the kernel requires 19s or higher firmware.
Click to expand...
Click to collapse
I just saw on my build.prop file that the fingerprint is recorded as Letv/LeMax2_WW/..... but the device model is the LEX820. Does that mean that I have to try the 19s firmware even though the device is X820 and not X821?
In case, is it safe to flash a X821 firmware on a X820 phone?
surfersea said:
I just saw on my build.prop file that the fingerprint is recorded as Letv/LeMax2_WW/..... but the device model is the LEX820. Does that mean that I have to try the 19s firmware even though the device is X820 and not X821?
In case, is it safe to flash a X821 firmware on a X820 phone?
Click to expand...
Click to collapse
It should be fine as the only real difference between Le Max 2 models is x829 lacks LTE band 20.
The build fingerprint used is from Indian 19s x821 because it is certified by Google.
For reference, I have an x829 (no LTE b 20 for me lol) and I have flashed x821 19s (my device then detected as le_x2_india) and have also flashed x820 20s, 26s, 28s and 416d and 466d (and my device then detected as le_x2) without any issues.
Related
I have switched to a new device and no longer use this phone but i see many others facing this issue as well so I am keeping this thread open, please do not message me regarding the solution to this issue cause all i did to get out of this mess was getting a new phone.
Hello !
Due to some error while flashing stock rom on Moto G4 Plus XT-1643 my Moto G4 Plus has changed into Moto G4 but the model no shown in the "About Phone" section is correct.
I have lost one Imei no. fingerprint option is no where sim or mobile network doesn't work other than that the phone is fully functional(WiFi,Camers,Audio etc)
There are multiple threads on the same issue but no solution is available I would be highly grateful if anyone could find out any solution to this issue.
P.S : I have tried flashing multiple ROMs available on the forum specific to XT-1643 i.e Indian Version
Also I flashed the OTA file for the Android 7.0 Soak Test due to which I cannot relock the bootloader.
I am currently on Stock Marshmallow 6.0.1 139-63 Rooted&TWRP installed
The phone is basically an iPod without fingerprint sensor
I had the same issue. I relocked the bootloader and sent to service center. They flashed the original firmware. Stock roms roaming here are not exactly stock roms.
this happened to my phone (1640 - brazilian moto g 4 plus), and I tried every single rom out there for moto g 4 plus, and it is only identified as Moto G 4, without fingerprint or any modem activity.
i still cannot recover previous bootloader, because it don't downgrade bootloader version. nothing worked for me so far.
i'll be watching this thread to see if anyone comes with any alternative.
sabithmk said:
I had the same issue. I relocked the bootloader and sent to service center. They flashed the original firmware. Stock roms roaming here are not exactly stock roms.
Click to expand...
Click to collapse
Umm, so according to you too it's a software issue and not a hardware one right ?
The first thing that I do when I boot in TWRP, I do a full backup of all the phone's partitions, and save a copy on my PC, so I can restore the phone in cases like this.
Guys, maybe you need to read this thread:
http://forum.xda-developers.com/showthread.php?t=2617276
if you flashed android 7.0 and then downgraded to android 6.0.1 then expect some bugs because your bootloader gets updated you have to do clean flash but you cannot actually completely downgrade to android 6.0.1 after you updated to 7.0 soak test bootloader still remains updated and your phone will brick when you click update after you receive 7.0 official OTA i warned you this happened to lot of moto x users do some research before you do anything if the phone is your primary device
Soureen said:
Umm, so according to you too it's a software issue and not a hardware one right ?
Click to expand...
Click to collapse
I think so. May be if we flash a wrong modem, the right one never flashes correctly. I don't know how do they managed to flash it correctly.
For me its a software issue... looks like it messed with the bootloader, and since you cannot rollback to an older bootloader, the phone works like an iPod Touch. haha
I hope that when Motorola releases the final 7.0 version for 1640, I'll be able to flash again the right bootloader and that will fix the phone.
SoNic67 said:
The first thing that I do when I boot in TWRP, I do a full backup of all the phone's partitions, and save a copy on my PC, so I can restore the phone in cases like this.
Guys, maybe you need to read this thread:
http://forum.xda-developers.com/showthread.php?t=2617276
Click to expand...
Click to collapse
I did a full flash of an older 6.0.1 ROM, and it still doesn't work. Since the only thing that I couldn't flash is the bootloader, and the phone identify itself as Moto G 4 (and not Moto G 4 Plus) my guess is that the problem is with the bootloader.
I guess i'll have to wait for the official 7.0 for my specific phone (1640) to fully replace this broken bootloader.
Yeah, that's why I didn't upgrade to the N yet, I was sure that the bootloader will be different.
I also have saved the partitions with Partitions Backup & Restore app, after rooting.
Did you try the ElementalX kernel?
http://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
I was also having same issue,got my bootloader locked and went to service center and they replaced the motherboard for free????
Lucky you
Has anyone found a solution to get the plus (fingerprint) back to the phone?
Nope funny thing no one knows anything ??
I am waiting for the Android 7.0 official update so that I can relock my bootloader and send it for service.
That's a bummer but there might be some solution. The phone version number shouldn't be that hard to find if you'd knew witch file that flashes it.
How do you do these backups for they don't look at all as twrp backups so I guess twrp is second best to something. But what?
What is the different with 7.0 coming up? Can't you just relock a backup?
Soureen said:
Nope funny thing no one knows anything ??
I am waiting for the Android 7.0 official update so that I can relock my bootloader and send it for service.
Click to expand...
Click to collapse
I have the same issue, I have seen people with XT1643 having athene_f in build fingerprint but I have only athene. Which one is correct, could this be the issue?
Managed to solve the issue at least to get the signal. This is what I have done
- Restore my first TWRP backup.
- Booted directly into bootloader and NOT system, flashed modem for the build.
- Rebooted and I am getting the signal!!!
m.swastik said:
Managed to solve the issue at least to get the signal. This is what I have done
- Restore my first TWRP backup.
- Booted directly into bootloader and NOT system, flashed modem for the build.
- Rebooted and I am getting the signal!!!
Click to expand...
Click to collapse
Radio is working after TWRP backup + modem flash. Still fingerprint is not working and it is pointing out as athene not as athene_f
(bootloader) ro.build.fingerprint[0]: motorola/athene/athene:6.0.1/MPJ24
(bootloader) ro.build.fingerprint[1]: .139-63/64:user/release-keys
Click to expand...
Click to collapse
l2o88j said:
Radio is working after TWRP backup + modem flash. Still fingerprint is not working and it is pointing out as athene not as athene_f
Click to expand...
Click to collapse
I have spent 1 whole week to get the signal working, at least be glad that you can now use your phone and press thanks if I helped. Regarding athene in build fingerprint you can easily change that in build.prop but it won't help. I think fingerprint service is disabled because ROM thinks that our phone is G4 and not G4 plus. I have tried few things to enable it but not getting it to work, will update if any of my experiment is successful.
m.swastik said:
I have spent 1 whole week to get the signal working, at least be glad that you can now use your phone and press thanks if I helped. Regarding athene in build fingerprint you can easily change that in build.prop but it won't help. I think fingerprint service is disabled because ROM thinks that our phone is G4 and not G4 plus. I have tried few things to enable it but not getting it to work, will update if any of my experiment is successful.
Click to expand...
Click to collapse
I found this trick early and I am using it now. I thought you cracked the last part (fingerprint sensor) which my post was about. I think that the issue is with gpt bin as I tried different bootloader versions along with all possible combinations. Gud to see someone else is working on the same. Will update if found any.
find the correct firmware for the device and flash it else it would lead to such errors
Hi guys,
I switched from Stock MM directy to CM 14.1.
Is there a way for me to get N Firmware & modem without going back to stock?
Thanks in advance
a little push
Das_OSi said:
Hi guys,
I switched from Stock MM directy to CM 14.1.
Is there a way for me to get N Firmware & modem without going back to stock?
Thanks in advance
Click to expand...
Click to collapse
If you read the threads for updating to N soak test you will see that it is not possible as you need to sideload the N soak test with official recovery. Only with soak test you receive all firmware files which isn't possible with flashing modem only. And please don't push.
The "official" that rolls out now in India is the same version that pas posted here on Dec 11:
http://forum.xda-developers.com/moto-g4-plus/how-to/captured-ota-nougat-ota-moto-g4-plus-t3517059
Hello again,
haven't been here for a while...
I'm still facing problems with 4G and the camera, because I'm still not on N Firmware & modem :angel:
Has something changed about this process?
Do I still need to go back to stock or is there an easier way now?
Huge thanks in advance
Das_OSi said:
Hello again,
haven't been here for a while...
I'm still facing problems with 4G and the camera, because I'm still not on N Firmware & modem :angel:
Has something changed about this process?
Do I still need to go back to stock or is there an easier way now?
Huge thanks in advance
Click to expand...
Click to collapse
Don't know about your device type but yes, there are fastboot images as well as detailed guides available at guides section like this one http://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
strongst said:
Don't know about your device type but yes, there are fastboot images as well as detailed guides available at guides section like this one http://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
Oh, totally forgot to mention it.
According to the sticker on the back of it:
Model: XT1622
Type: M1B89
bought on Amazon.de, they sold it as an "Lenovo Moto G4 Smartphone (14 cm (5,5 Zoll) 16GB, Android) schwarz"
Das_OSi said:
Oh, totally forgot to mention it.
According to the sticker on the back of it:
Model: XT1622
Type: M1B89
bought on Amazon.de, they sold it as an "Lenovo Moto G4 Smartphone (14 cm (5,5 Zoll) 16GB, Android) schwarz"
Click to expand...
Click to collapse
You don't have a g4 plus. So AFAIK there's no fastboot image out for xt1622 yet. And this forum is for g4 plus, not g4. You should read and ask in g4 forum, but I can't find images there.
Das_OSi said:
Oh, totally forgot to mention it.
According to the sticker on the back of it:
Model: XT1622
Type: M1B89
bought on Amazon.de, they sold it as an "Lenovo Moto G4 Smartphone (14 cm (5,5 Zoll) 16GB, Android) schwarz"
Click to expand...
Click to collapse
Provided your device isn't the one with Amazon adverts on, the fast boot ROM linked by strongst appears to flash onto XT1622 devices. Bear in mind this is a stock ROM and flashing it will revert you back to stock recovery and system. There was a TWRP image of the baseband modem and firmware, though that got taken down as it seemed not to work well for US devices. However, in my opinion, flashing the whole stock ROM should be more stable.
strongst said:
You don't have a g4 plus. So AFAIK there's no fastboot image out for xt1622 yet. And this forum is for g4 plus, not g4. You should read and ask in g4 forum, but I can't find images there.
Click to expand...
Click to collapse
It must be an Plus, because I can only flash "athene" builds via TWRP.
TWRP won't let me flash G4 builds.
echo92 said:
Provided your device isn't the one with Amazon adverts on, the fast boot ROM linked by strongst appears to flash onto XT1622 devices. Bear in mind this is a stock ROM and flashing it will revert you back to stock recovery and system. There was a TWRP image of the baseband modem and firmware, though that got taken down as it seemed not to work well for US devices. However, in my opinion, flashing the whole stock ROM should be more stable.
Click to expand...
Click to collapse
No, there were no Amazon adverts on mine.
This one here:
https://forum.xda-developers.com/moto-g4/development/fxz-athene-twrp-flashable-fastboots-t3562147
?
Das_OSi said:
It must be an Plus, because I can only flash "athene" builds via TWRP.
TWRP won't let me flash G4 builds.
No, there were no Amazon adverts on mine.
This one here:
https://forum.xda-developers.com/moto-g4/development/fxz-athene-twrp-flashable-fastboots-t3562147
?
Click to expand...
Click to collapse
Yeah, that was the thread I was referring to. The 93-14 fastboot ROM has been reported to flash on xt1622 devices okay https://forum.xda-developers.com/mo...1640-43-athene-npj25-93-t3549369/post70843323 this will also give you the same build as has been deployed over the EU and globally. Still though, have a read of the thread before flashing.
echo92 said:
Yeah, that was the thread I was referring to. The 93-14 fastboot ROM has been reported to flash on xt1622 devices okay https://forum.xda-developers.com/mo...1640-43-athene-npj25-93-t3549369/post70843323 this will also give you the same build as has been deployed over the EU and globally. Still though, have a read of the thread before flashing.
Click to expand...
Click to collapse
Thanks a lot, I would probably never have found this thread without you.
Just doing an "fastboot flash modem NON-HLOS.bin" won't be enough, right? :fingers-crossed:
I can confirm the method mentioned by echo92 above. Works perfect on my XT1622. If you have sucessfully installed the 93-14 Stock N build, you could upgrade to the latest update 93-14-4, provided in this thread:
https://forum.xda-developers.com/mo...ial-moto-g4-plus-ota-update-build-t3584982...
1.page....thanks to lexie90
Worked like a charm
Now I'm on
[ROM][OFFICIAL][7.1.1][XT16xx]LineageOS 14.1[athene][Moto G4/Moto G4 Plus]
and handover from WiFi to LTE finally works, also my camera is working again
Thanks a lot guys :victory:
TWRP doesn't flash stock. You need to do it in fastboot mode.
To find out what device you have, while in fastboot, type this in cmd window:
Code:
fastboot getvar all
SoNic67 said:
TWRP doesn't flash stock. You need to do it in fastboot mode.
To find out what device you have, while in fastboot, type this in cmd window:
Code:
fastboot getvar all
Click to expand...
Click to collapse
No,
with the help of you guys I managed to flash the latest stock (using fastboot), and now I'm back on CM again :highfive:
hi after uploading a new uptade mk 7.1 almost reach and it does not show me the card idea i have moto g4 plus xt 1642 dual sim help?
The phone shows that I have g4 plus and when connected to the computer that g4
Has anyone got any idea how to fix this?
szymon1515 said:
hi after uploading a new uptade mk 7.1 almost reach and it does not show me the card
Click to expand...
Click to collapse
English is not you main language, but I think that nobody here understand what your question/problem exactly is.
Gero71 said:
English is not you main language, but I think that nobody here understand what your question/problem exactly is.
Click to expand...
Click to collapse
My language is Polish
I need rom to moto g4 plus xt 1642 dual sim 16gb in european version someone give link?
If you're looking for a stock ROM, here's the Nougat (v7.0, Dec 2016 security update) stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 I've successfully flashed it several times on my XT 1642 and appears to be the same build as that which came out on the official OTA update.
If you need Marshmallow ROMs, try https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 , which is MM 6.0.1, July 2016 security patch. Again, I've been able to flash this on my XT 1642 and received the Nougat OTA update, your experience may vary.
As always, with both ROMs, please carefully read the instructions and be aware you may lose your data, back up accordingly.
EDIT - just for info, I've got a XT 1642, retgb (UK) software update channel with an EMEA baseband. With both ROMs, those details were preserved.
echo92 said:
If you're looking for a stock ROM, here's the Nougat (v7.0, Dec 2016 security update) stock ROM: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 I've successfully flashed it several times on my XT 1642 and appears to be the same build as that which came out on the official OTA update.
If you need Marshmallow ROMs, try https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 , which is MM 6.0.1, July 2016 security patch. Again, I've been able to flash this on my XT 1642 and received the Nougat OTA update, your experience may vary.
As always, with both ROMs, please carefully read the instructions and be aware you may lose your data, back up accordingly.
EDIT - just for info, I've got a XT 1642, retgb (UK) software update channel with an EMEA baseband. With both ROMs, those details were preserved.
Click to expand...
Click to collapse
Will it work on xt 1642 dual sim 16gb reteu?
szymon1515 said:
Will it work on xt 1642 dual sim 16gb reteu?
Click to expand...
Click to collapse
They should work, as mentioned I have a xt 1642, same as you, dual SIM, (32 GB model) just on the UK software channel as opposed to the EU channel. Other members appear to have successfully flashed these ROMs on their EU devices, the only way to be certain is to try on your device.
echo92 said:
They should work, as mentioned I have a xt 1642, same as you, dual SIM, (32 GB model) just on the UK software channel as opposed to the EU channel. Other members appear to have successfully flashed these ROMs on their EU devices, the only way to be certain is to try on your device.
Click to expand...
Click to collapse
Will I detect the sim card because now I have so ...IMEI 1 0
IMEI 2 0
szymon1515 said:
Will I detect the sim card because now I have so ...IMEI 1 0
IMEI 2 0
Click to expand...
Click to collapse
Uh oh, that's not good, which firmware did you flash? That could be a result of the wrong firmware being flashed onto your device (especially as we don't have an official 7.1 firmware yet). You can try flashing the above firmware to try, there's a couple of other topics on this missing imei, the only other resolution I've seen so far is to service or replace your device.
echo92 said:
uh oh, that's not good, which firmware did you flash? That could be a result of the wrong firmware being flashed onto your device (especially as we don't have an official 7.1 firmware yet). You can try flashing the above firmware to try, there's a couple of other topics on this missing imei, the only other resolution i've seen so far is to service or replace your device.
Click to expand...
Click to collapse
jx's cream pie for nougat 25 93.11
szymon1515 said:
jx's cream pie for nougat 25 93.11
Click to expand...
Click to collapse
The phone shows that I have a g4 plus and a g4 computer
Which software should you try 6.0 or 7?
Can I get my imei number? How does that come from?
The IEMI "disappears" when is a mismatch of the radio (modem) files and the system, like if you try to flash a custom 7.1 ROM over stock 6.0 (MM). Sometimes is hard to recover from that.
First, in TWRP, wipe Data. Then, flash in fastboot the official 7.0:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Follow exactly the procedure, run the "OEM Flash.bat" script. Since you don't seem to be very skilled, stop using un-tested ROM's or you will loose your phone. You can add the ElementalX kernel if you need root on the stock 7.0.
https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
SoNic67 said:
The IEMI "disappears" when is a mismatch of the radio (modem) files and the system, like if you try to flash a custom 7.1 ROM over stock 6.0 (MM). Sometimes is hard to recover from that.
First, in TWRP, wipe Data. Then, flash in fastboot the official 7.0:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Follow exactly the procedure, run the "OEM Flash.bat" script. Since you don't seem to be very skilled, stop using un-tested ROM's or you will loose your phone. You can add the ElementalX kernel if you need root on the stock 7.0.
https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
Click to expand...
Click to collapse
Still does not show imei and when connected to computer shows i have g4 and should show g4 plus
What outputs "fastboot getvar imei"? Do you see the two IEMI there? Don't post them here, just look!
1. If the IEMI are missing, and you still have the original phone box (with printed IEMI numbers), you can try to set new IMEI:
"fastboot oem writeimei 123456789012347" This is a example write your own imei there.
2. If you see the IEMI listed by getvar... don't know anything besides what I have already typed in the first post.
SoNic67 said:
What outputs "fastboot getvar imei"? Do you see the two IEMI there? Don't post them here, just look!
1. If the IEMI are missing, and you still have the original phone box (with printed IEMI numbers), you can try to set new IMEI:
"fastboot oem writeimei 123456789012347" This is a example write your own imei there.
2. If you see the IEMI listed by getvar... don't know anything besides what I have already typed in the first post.
Click to expand...
Click to collapse
Im showing imei 1 .... 0
******************** Imei 2 .... 0
Then you can use the #1 from above. Copy the IEMI from the battery label first.
"fastboot oem writeimei 1 123456789012347" and "fastboot oem writeimei 2 123456789012347"
Or... try this.
http://www.hugestreet.info/2015/08/Free-Android-Device-ID-and-IMEI-number-changer.html
http://www.shelaf.com/2014/06/universal-method-for-changing-any.html
SoNic67 said:
Then you can use the #1 from above. Copy the IEMI from the battery label first.
"fastboot oem writeimei 1 123456789012347" and "fastboot oem writeimei 2 123456789012347"
Or... try this.
http://www.hugestreet.info/2015/08/Free-Android-Device-ID-and-IMEI-number-changer.html
http://www.shelaf.com/2014/06/universal-method-for-changing-any.html
Click to expand...
Click to collapse
Unfortunately nothing works still does not show imei
With the stock firmware that I have linked above?
I always make a backup - at least with TWRP and also with this
https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=en
SoNic67 said:
With the stock firmware that I have linked above?
I always make a backup - at least with TWRP and also with this
https://play.google.com/store/apps/details?id=ma.wanam.partitions&hl=en
Click to expand...
Click to collapse
So still not reachable and does not show imei
szymon1515 said:
So still not reachable and does not show imei
Click to expand...
Click to collapse
Hmm, that's not good, before flashing J-X's Creampie for Nougat, did you flash any other ROMs?
You may wish to have a look through this thread https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912 or this thread https://forum.xda-developers.com/moto-g4-plus/help/imei-0-t3476876/ for example, see if any of the tips within help.
Else, as I previously mentioned, looks like it might be either sending your device to service or for a replacement.
echo92 said:
Hmm, that's not good, before flashing J-X's Creampie for Nougat, did you flash any other ROMs?
You may wish to have a look through this thread https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-pluss-model-changed-to-g4-lost-t3496912 or this thread https://forum.xda-developers.com/moto-g4-plus/help/imei-0-t3476876/ for example, see if any of the tips within help.
Else, as I previously mentioned, looks like it might be either sending your device to service or for a replacement.
Click to expand...
Click to collapse
Such as lineage and RR
So, I have a 32gb Amazon-variant XT1625 on MPJ24.139-48 with an unlocked bootloader and root. I want to update to Nougat, but it's looking like setting up to take the Amazon update is going to be a fair amount of effort; I'm wondering if it's possible to just flash the retail version of Nougat since it's looking like I'm going to have to go to a fair sum of effort anyway.
I've also heard that Moto G4 Plus ROMs will work on the G4, but I don't know the specifics on that.
i dont see why not as long as you already unlocked the bootloader prior to Moto(Lenovo) disallowed unlocking of amazon varients of the g4. heres a link to the stock nougat firmware
https://androidfilehost.com/?fid=673368273298955218
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Travisholt92 said:
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Click to expand...
Click to collapse
then you was able to flash retail version in a amazon prime phone? I have one and it dont boot if i instal a retail version.
di anybody actually get this working? I had the same issue as @iurd2007 I was able to unlock the bootloader just fine. The flash appeared to have taken successfully. But it just gets caught in a boot loop when trying to reboot the system after the flash. I followed the instructions here:
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
okay, so i've tried various roms both official and unofficial, as well as even the stock Nougat and Oreo flashable roms found here:
https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367
So far, the only ROM i've been able to get installed is omni rom 9, but it keeps crashing several apps over and over on the setup wizard. I've read somewhere that using a different version of TWRP recovery image might help. I've tried the official TWRP recovery from twrp.me, the patched arm64 version found here: https://sourceforge.net/projects/tw...3-r1-athene-arm64_rajatgupta1998.img/download , also the latest version patched for efs backup/restore here: https://forum.xda-developers.com/devdb/project/?id=29106#downloads. So far the the one that seems to work the best is the third version of TWRP. It would be nice if all these custom patches made it back into an official release, but it's probably asking a lot of a phone that is almost 4 years old at this point. and a budget friendly phone at that.
RR gives me problem with the fingerprint. So i'd Like to know that
Settings > about > baseband .
It should be M8952_70030
And if i remember correctly 70029 was for soak test..
EDIT: for soak it was 70025.20.03.52R
For official N, it should be newer than it.
sam1101119 said:
RR gives me problem with the fingerprint. So i'd Like to know that
Click to expand...
Click to collapse
If you go to Settings > About Phone, does your baseband end in .52R, .60R or .62R (e.g. M8952_70030.25.03.62R ). If so, you're on a Nougat modem. Also, if you were on any Nougat stock ROM before flashing RR, you'll have the correct modem.
If your baseband doesn't have the endings as mentioned above, you'll either have to try flashing a TWRP Nougat baseband file (e.g. from https://forum.xda-developers.com/moto-g4-plus/how-to/fxz-flashable-stock-npjs25-93-14-4-t3623010 ) or revert back to Nougat stock, then flash TWRP and RR. For the latest stock fastboot ROM we have: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Alternatively, you could try just enrolling one fingerprint and see how you get on.
I have .52R, but anyways when I unlock the phone with fingerprint the touch doesn't work. How can I solve?
sam1101119 said:
I have .52R, but anyways when I unlock the phone with fingerprint the touch doesn't work. How can I solve?
Click to expand...
Click to collapse
So you've likely got the Nougat soak test from October 2016 running on your device, the modem should play nice though. You may wish to update to the latest Nougat stock ROM however.
What build of RR are you running and what GApps, and on what device? Any custom kernels/modifications? Does the fingerprint sensor still fail to work if you wipe your fingerprints and set them up again?
Now the problemi seems to have fixed on its own. The problemi has happened for like a week. If it wil represent, I'll tell you