Moto G4 Plus's Model changed to G4,lost one imei and finger print.

Soureen

Senior Member
Mar 21, 2013
127
246
0
Siliguri
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
 
Last edited by a moderator:

caravana

Senior Member
Sep 28, 2010
107
129
73
Rio de Janeiro
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.
 
  • Like
Reactions: benedictusg

D1AMONDH3AD

Member
Aug 15, 2016
41
7
8
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
 

caravana

Senior Member
Sep 28, 2010
107
129
73
Rio de Janeiro
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.

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
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.
 
Last edited:
  • Like
Reactions: jim_r0x

SoNic67

Senior Member
Apr 10, 2011
1,058
202
0

Attachments

Last edited:

benedictusg

Member
Apr 10, 2015
46
3
0
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?
 
Last edited:

m.swastik

Senior Member
Feb 19, 2011
191
29
0
Mumbai
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.
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?
 

m.swastik

Senior Member
Feb 19, 2011
191
29
0
Mumbai
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!!!
 

rooban90

Senior Member
Dec 12, 2015
146
36
0
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!!!
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
 

m.swastik

Senior Member
Feb 19, 2011
191
29
0
Mumbai
Radio is working after TWRP backup + modem flash. Still fingerprint is not working and it is pointing out as athene not as athene_f
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.
 
  • Like
Reactions: GeeteshKhatavkar

rooban90

Senior Member
Dec 12, 2015
146
36
0
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.
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.
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone