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
Hello guys,
I would really appreciate some help with the following:
Issue
My proximity and light sensor is not working at all. And I am not convinced that it is a hardware issue. It happened on Oxygen OS 3.5.8 which was rooted with TWRP as recovery. The various sensor test apps available on the store will just report that there is actually no proximity/light sensor.
I read around and what I understood is that superSU can break the sensor, and that it is somehow tied to the radio firmware of the device.
What I tried
On OOS I flashed an older radio with no effect (I stupidly flashed the old superSU I had on my device just after, so it might have broken it again).
I also flashed the stock OOS image from Oneplus site.
What I would like to try
I just flashed Vertex OS Carbide. Sadly the sensor is still reported as 'No proximity/light' sensor. I would like to have a link to a compatible radio firmware so that I can test if it somehow help me fix the issue. I am confused on which radio firmware this ROM uses.
Also, if some of you experts are convinced that its a hardware issue (I live in a country where there is no official Oneplus representative), could you share a link to a replacement part? I checked Ebay but they are selling the capacitive buttons ribbons and are labeling it as proximity sensor.
Thank you for your help and excuse my noob-ness.
I think there's a persist file somewhere in the forum that's what you need
Sent from my ONE A2005 using Tapatalk
Hey, I'm from Brazil and I own a H342 model of this phone.
I was thinking about installing the v20b marshmallow kdz released for H340 because I'm done with the ***ty, ugly and laggy 5.0.1 build that I'm stuck in, but I know that even if the processor is the same for both devices the baseband will still differ because my model is dual.
You know how can I install 6.0 and flash the baseband from the H342 after?
Sorry for any concordances errors and thank u for your time
TLDR: Samsung N920F seems to be a N920T, and you can flush ROM from N920T.
Recently my friends asked to help them with their Galaxy Note 5 which was bought somewhere in China. It was stuck at Android 6, with last updates from 2016, and seemed to have some malware (factory reset did not help).
It was really strange to see model N920F - I checked many threads here, and everyone says that there should be no such version as N920F:
https://forum.xda-developers.com/note5/help/note-5-n920f-n920t-t3310411
https://forum.xda-developers.com/note5/help/settings-sm-n920f-boot-loader-sm-n920p-t3776224
https://forum.xda-developers.com/note5/help/note-5-sm-n920f-eu-variant-please-help-t3527449
https://forum.xda-developers.com/note5/help/sm-n920f-stock-roms-t3482405
https://forum.xda-developers.com/note5/help/note-5-european-version-sale-sm-n920f-t3190929
Unfortunately, not even one of those topics found any reason for this or solution for updating. So I tried to find out the true and update phone myself.
At first, I booted to recovery. And there I saw that it model name was nobleltetmo - same as for N920T.
So I tried to install TWRP from N920T via Odin. TWRP successfully installed but phone stopped booting and TWRP only booted but did not work - it told me about bootloader version mismatch. So I found out that phone's bootloader version was N920TUVU4DPK6. So I tried to find a working firmware for this bootloader version and found it on xda: https://forum.xda-developers.com/tm...eral/stock-n920t-stock-n920tuvu4dpk6-t3518252
Fortunately, I could enter download mode and flush it with Odin. After it, phone worked fine, and now it was officially N920T. But even better things awaited - after updating it managed to fetch fresh updates! So I downloaded and installed them. Phone updated... And found new updates... And about 10 times again like this. Finally, I got the latest official Samsung Firmware with Android 7.0 - and it works flawlessly. Even Googe Play, NFC and banking services. I suppose that after this I could flush TWRP again because bootloader version also updated - but official firmware was quite okay so I didn't want to set up Lineage OS.
By the way, I think that I could find latest firmware and flush it with Odin in one go - but I didn't succeed in finding it.
Please beware that this N920F turned to be N920T - but your one can be another (N920V or N920P, for example)!
Now I am pretty sure that F in model version stands for "F***ed up".
So check bootloader version and be accurate.
jehy_rus said:
TLDR: Samsung N920F seems to be a N920T, and you can flush ROM from N920T.
Recently my friends asked to help them with their Galaxy Note 5 which was bought somewhere in China. It was stuck at Android 6, with last updates from 2016, and seemed to have some malware (factory reset did not help).
It was really strange to see model N920F - I checked many threads here, and everyone says that there should be no such version as N920F:
https://forum.xda-developers.com/note5/help/note-5-n920f-n920t-t3310411
https://forum.xda-developers.com/note5/help/settings-sm-n920f-boot-loader-sm-n920p-t3776224
https://forum.xda-developers.com/note5/help/note-5-sm-n920f-eu-variant-please-help-t3527449
https://forum.xda-developers.com/note5/help/sm-n920f-stock-roms-t3482405
https://forum.xda-developers.com/note5/help/note-5-european-version-sale-sm-n920f-t3190929
Unfortunately, not even one of those topics found any reason for this or solution for updating. So I tried to find out the true and update phone myself.
At first, I booted to recovery. And there I saw that it model name was nobleltetmo - same as for N920T.
So I tried to install TWRP from N920T via Odin. TWRP successfully installed but phone stopped booting and TWRP only booted but did not work - it told me about bootloader version mismatch. So I found out that phone's bootloader version was N920TUVU4DPK6. So I tried to find a working firmware for this bootloader version and found it on xda: https://forum.xda-developers.com/tm...eral/stock-n920t-stock-n920tuvu4dpk6-t3518252
Fortunately, I could enter download mode and flush it with Odin. After it, phone worked fine, and now it was officially N920T. But even better things awaited - after updating it managed to fetch fresh updates! So I downloaded and installed them. Phone updated... And found new updates... And about 10 times again like this. Finally, I got the latest official Samsung Firmware with Android 7.0 - and it works flawlessly. Even Googe Play, NFC and banking services. I suppose that after this I could flush TWRP again because bootloader version also updated - but official firmware was quite okay so I didn't want to set up Lineage OS.
By the way, I think that I could find latest firmware and flush it with Odin in one go - but I didn't succeed in finding it.
Please beware that this N920F turned to be N920T - but your one can be another (N920V or N920P, for example)!
Now I am pretty sure that F in model version stands for "F***ed up".
So check bootloader version and be accurate.
Click to expand...
Click to collapse
Same prob here malware and pops up ads in N920F. And device cannot be registered for updating. And odin says its N920K. If you have any link help me.
Mynouddin said:
Same prob here malware and pops up ads in N920F. And device cannot be registered for updating. And odin says its N920K. If you have any link help me.
Click to expand...
Click to collapse
I think you can try this rom: https://forum.xda-developers.com/note5/general/rom-lineageos-15-1-note-5-android-8-1-t3737405
If it is not compatible, you can enter rescue mode and check bootloader version.
jehy_rus said:
I think you can try this rom: https://forum.xda-developers.com/note5/general/rom-lineageos-15-1-note-5-android-8-1-t3737405
If it is not compatible, you can enter rescue mode and check bootloader version.
Click to expand...
Click to collapse
Thread closed
I need your help.
I am very glad to find your article because i ve the n920f and am really ****ed up.
How can i find my recovery code to know which model am on. I will be very glad if you can help me out. Thanks
Nanakwameampong said:
I am very glad to find your article because i ve the n920f and am really ****ed up.
How can i find my recovery code to know which model am on. I will be very glad if you can help me out. Thanks
Click to expand...
Click to collapse
Download this app it will show you your correct software and model.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Hi,
a few weeks ago I tried to root my Galaxy A5 (A520F).
But I forgot to turn on OEM unlock.
Then I installed Lineage OS (official built) with TWRP.
I never liked Lineage OS, but it was the easiest to install.
I realized that my sim didn't work and when I looked in the settings app, I saw that my Baseband and Model Number was missing.
I installed the stock ROM that I downloaded from SamMobile (A1 Austria / MOB), but it still didn't work.
Then I decided to install HADES ROM (I never heard of it until that day), but it still didn't show up any Baseband or Model Number.
Then I went to a guy that is very famous for repairing phones in our city.
After a week I got my phone back, but even he couldn't repair it.
I tried it again myself but after a few days I gave up and bought a Honor Play.
My question is:
Is it possible to bring back the Baseband and Model Number (without a box)?
If yes, then please let me know I would try everything.
Thank you!
( sorry for my bad english )
senad1912 said:
Hi,
a few weeks ago I tried to root my Galaxy A5 (A520F).
But I forgot to turn on OEM unlock.
Then I installed Lineage OS (official built) with TWRP.
I never liked Lineage OS, but it was the easiest to install.
I realized that my sim didn't work and when I looked in the settings app, I saw that my Baseband and Model Number was missing.
I installed the stock ROM that I downloaded from SamMobile (A1 Austria / MOB), but it still didn't work.
Then I decided to install HADES ROM (I never heard of it until that day), but it still didn't show up any Baseband or Model Number.
Then I went to a guy that is very famous for repairing phones in our city.
After a week I got my phone back, but even he couldn't repair it.
I tried it again myself but after a few days I gave up and bought a Honor Play.
My question is:
Is it possible to bring back the Baseband and Model Number (without a box)?
If yes, then please let me know I would try everything.
Thank you!
( sorry for my bad english )
Click to expand...
Click to collapse
Flash RIL fix for your device after flashing a custom rom. Or get the correct stock firmware from sammobile, flash it via odin, and voilla, your baseband and model number will be back If you want more detailed guide, just reply and ask me.