Database Users

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

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

[Q] Please i need full firmware for Huawei nova

Hello!
My huawei nova was marshmallow version 6.0
I unlocked bootloader and i did custom recovery
And then i rooted it, was working well.
But when i did format from recovery its stop working
Please i need full firmware file
Huawei nova CAN-L01C02B130 (belgium)

hi...in HiSuite,
try with Recover phone or phone recovery in the main tabs...

Yahyakhalid.be said:
Hello!
My huawei nova was marshmallow version 6.0
I unlocked bootloader and i did custom recovery
And then i rooted it, was working well.
But when i did format from recovery its stop working
Please i need full firmware file
Huawei nova CAN-L01C02B130 (belgium)
Click to expand...
Click to collapse
Hey, today afternoon was so boring therefore I'm wondering around threads and then i found your update here.
You can try it out if your problem isn't solved yet. I think it'll help because it's the official nova 7.0 nougat version for Europe. Do reply so that others can benefit from your experience.

dviraj00 said:
Hey, today afternoon was so boring therefore I'm wondering around threads and then i found your update here.
You can try it out if your problem isn't solved yet. I think it'll help because it's the official nova 7.0 nougat version for Europe. Do reply so that others can benefit from your experience.
Click to expand...
Click to collapse
Your linking a old version of the Nougat update for the Nova variant CAN-L01C432 and the CAN-L11C432 which if your not careful could damage your phone if you don't have that version of the Nova. There is the CAN-L01C432/CAN-L11C432 variants, the MLA-L03C654 variant, the CAN-L01C02 variant and a couple of others I believe.

lintern said:
Your linking a old version of the Nougat update for the Nova variant CAN-L01C432 and the CAN-L11C432 which if your not careful could damage your phone if you don't have that version of the Nova. There is the CAN-L01C432/CAN-L11C432 variants, the MLA-L03C654 variant, the CAN-L01C02 variant and a couple of others I believe.
Click to expand...
Click to collapse
my bad i didn't know that there are these many variants.. Thank you for notifying

Hi everyone, my first post here.
Looks like im in the same situation.
I have Nova Plus from Bell/Virgin Canada. MLA-L03. Purchased it on Caraigslist and after 2 month they blacklisted my Imei. I decided to root the phone and maybe change imei as the phone was useless anyways. So i installed TWRP and rooted it successfuly .
The problem was that i could never get diagnostic port open for Qualcomm QPST program. So i upgraded to Nougar 7.0 ( NRD90M) it got UNrooted and i wanted tio install a newer version of TWRP, i guess i got a wrong version. Now its properly screwed up. I have FRP Lock in fasboot, it makes fastboot useless as i cant adb flash boot, or flash recovery. I can boot back to OS but OEM Unlocking is off and grayed out and FRP Lock blocks all communication, so ADB or Fastboot commands dont get through. i get "waiting for device" crap in command line. SD card upgrade doesn't work either. I dont know why and eRecovery wants to download update but fails all the time. I dont know how to get rid of FPR lock. If i find anything i will post here.

Used Pixel XL: Warning about Firmware and no updates

Hi guys,
I got a Pixel replacement for my Nexus 6P, love the phone but missed the larger screen so selling it and bought second hand Pixel XL with 2 year warranty from CeX.
I noticed when it booted it said something about not running the initial Firmware. I asked the shop as was sold as the "unlocked" version. They told me was ee but genuine firmware that unlocked the phone and will function no differently and receive all updates without delay.
Having set up the phone, it's still running 7.1 and not detecting anything newer. Plus security patches are 05/10/16. This seems like a problem.
Do I need to return it?
EDIT: just started WhatsApp which told me I have a custom ROM which child cause issues. I bought the pixel to have native android.
Many thanks,
Max

Just flash the latest firmware
Sent from my Le X526 using Tapatalk

Thanks for the reply. But will I have to do this for every update and also to get security patches?
Just realised I'm in the wing sub forum. Can I ask to have it move?

maxcovergold said:
Thanks for the reply. But will I have to do this for every update and also to get security patches?
Just realised I'm in the wing sub forum. Can I ask to have it move?
Click to expand...
Click to collapse
No, you shouldn't have to flash every update once you are on official images. Just flash the stock Google images and you should be good to go. https://developers.google.com/android/images

calripkenturner said:
No, you shouldn't have to flash every update once you are on official images. Just flash the stock Google images and you should be good to go. https://developers.google.com/android/images
Click to expand...
Click to collapse
I noticed in the FAQ about meeting through boot loader unlocked and not relocking it. Presumably it must have been unlocked to change the original Firmware, but I don't get that message "Your device software can't be checked for corruption. Please lock the bootloader".
Is this going to be a problem in fishing the firmware? Sorry, I bought the Pixel as I really have no idea about the things, want exciting this.

The sign is just shown that your bootloader is unlocked.

No Updates at all

Hi all,
I just recently went back to complete stock, from CM, as I want to hand it over to a friend.
I successfully switched back to C432B160 last week.
But still not a single update does show up, though that build is from November 2016.
It always tells me, that there are no updates. I am aware that Updates will show up with Hisuite, but shouldn't the stock updater present updates, too?
(I am not even talking about Nougat)
I already successfully tried a factory reset.
The only idee I have, is that I now have a DS oeminfo on an originally SS phone.
Does anyone have an idee, what might be wrong?

fireburner-de said:
Hi all,
I just recently went back to complete stock, from CM, as I want to hand it over to a friend.
I successfully switched back to C432B160 last week.
But still not a single update does show up, though that build is from November 2016.
It always tells me, that there are no updates. I am aware that Updates will show up with Hisuite, but shouldn't the stock updater present updates, too?
(I am not even talking about Nougat)
I already successfully tried a factory reset.
The only idee I have, is that I now have a DS oeminfo on an originally SS phone.
Does anyone have an idee, what might be wrong?
Click to expand...
Click to collapse
well, if you have ds oeminfo while your phone is ss, try flashing ss oeminfo and then the stock rom again

mjz2cool said:
well, if you have ds oeminfo while your phone is ss, try flashing ss oeminfo and then the stock rom again
Click to expand...
Click to collapse
Well the phone was SS at the beginning, but now I have oeminfo for DS and Stock Rom for DS (B160)

I wiped all and completely new flashed B160.
I did not setup any account (Google, Huawei), but only connected the phone to my WIFI.
Still neither Update nor HiCare show any available updates.
Does this need a SIM Card to be in the phone? Are there any other precautions?
I have no idea why it behaves like this.
edit: both frp and bootloader are locked according to the Bootloader Menu
I might add 2 weeks ago when coming from CM, there were no updates in update menu but HiCare, so I went fo Nougat. Nougat did not work properly, so I went back to B160 in order to start again, but since then, I never saw any update in menu, nor HiCare.
Might Huawei block DS Roms for IMEIS of originally SS phones?

Push, maybe @k1ll3r8e has an answer for me?

fireburner-de said:
Push, maybe @k1ll3r8e has an answer for me?
Click to expand...
Click to collapse
Heyho,
sounds really wired...
-
Here is what u can try,
1) bring the device back to stock (unrooted, loader closed)
2) do a factory reset and also the cache clear which is offered in the stock recovery
-
Start the device, do a dummy setup (only wlan is needed) check if the device offers an update. If not, well, try to manually update from C432B160 to C432B210 and check the update app again.
About this issue, i'm not sure, but maybe Huawei have a "downlaod limit" for an IMEI, that u can only download the update for example 10 times or so... I don't know^^ - I can only say, my device "L31 - Single-SIM - T-Mobile" modded to C432B380 dual-SIM have no issues with updates... I got since B130 every update via the normal update app. - But i also know that the updates will be released in waves, i don't know how they exclude/include devices in such an wave. But maybe, u have an oeminfo from an device which wasn't in the "current wave list". - As already mentioned i don't know how they manage those waves or what the trigger is...
Hope i could help u a bit
Regards
Sebastian

fireburner-de said:
I wiped all and completely new flashed B160.
I did not setup any account (Google, Huawei), but only connected the phone to my WIFI.
Still neither Update nor HiCare show any available updates.
Does this need a SIM Card to be in the phone? Are there any other precautions?
I have no idea why it behaves like this.
edit: both frp and bootloader are locked according to the Bootloader Menu
I might add 2 weeks ago when coming from CM, there were no updates in update menu but HiCare, so I went fo Nougat. Nougat did not work properly, so I went back to B160 in order to start again, but since then, I never saw any update in menu, nor HiCare.
Might Huawei block DS Roms for IMEIS of originally SS phones?
Click to expand...
Click to collapse
So, did you try upgrade on N using Firmware finder?
If not, try it and you will see if your device in black list. I also use DS firmware for SS model and just last night I upgraded normaly from B160 to B370 Ota, and after that to B380 Ota.

@k1ll3r8e
Yes it already is a dummy setup. I will manually upgrade to B210 and try again, Thanks alot! @Alexxxx1
Firmware Finder is the Windows tool, isn't it? If above progress won't work I might boot my Windows partition and check on that.
Is there by chance any other way to check if the device is somehow blacklisted?
@all
Would Huawei push the updates to my device, if I would contact them? (I ask because of the altered oeminfo. Or would the refuse support in that case, which is what I guess)
edit: Does by chance anyone have a link to the C432B210 ROM?

fireburner-de said:
@k1ll3r8e
Yes it already is a dummy setup. I will manually upgrade to B210 and try again, Thanks alot! @Alexxxx1
Firmware Finder is the Windows tool, isn't it? If above progress won't work I might boot my Windows partition and check on that.
Is there by chance any other way to check if the device is somehow blacklisted?
@all
Would Huawei push the updates to my device, if I would contact them? (I ask because of the altered oeminfo. Or would the refuse support in that case, which is what I guess)
edit: Does by chance anyone have a link to the C432B210 ROM?
Click to expand...
Click to collapse
Heyho,
if u have an L31, go to my FTP (oeminfo) and go a few folders back, then u'll find a Huawei folder there are several versions stored.
Edit:
Here is the link (just back on my PC)
Regards,
Sebastian
Sent from my HUAWEI VNS-L31 using XDA Labs

Firmware finder is android app. You can find it in google play store as a free tool for upgrade huawei devices. In Ffinder you will find option for checking autorization of official firmware for your device, is it allowed or not for your device.
Regards

I did flash B210, but no Updates withiin 1 day. (I think time was to short)
I then flashed B370 Full-PV via Firmware Finder.
B380 should come automatically sometime, hopefully.
I think its time to hand it over to my friend now.
Only thing I am curious about is:
settings -> about phone -> certification: Serbia
I guess this is normal for C432?

Only thing I am curious about is:
settings -> about phone -> certification: Serbia
I guess this is normal for C432?
Click to expand...
Click to collapse
Yes, its normally for C432 if device was purchased in Serbia

Alexxxx1 said:
Yes, its normally for C432 if device was purchased in Serbia
Click to expand...
Click to collapse
It was bought from T-Mobile in Germany. But well.

fireburner-de said:
It was bought from T-Mobile in Germany. But well.
Click to expand...
Click to collapse
No worries about that
I bought mine also from T-Mobile DE, and mine shows also "Serbia"... I searched a bit for similar issues and it seems that also the P8 with C432 is for "Serbia" at least a unknown amount of it, sooo i think it comes from the "ROM" not from the device. Maybe they only certify the ROM for a "law based standart" to "Serbia". - Who knows...^^
Regards,
Sebastian

help blocked at startup htc after update

Hello
I write because following an update yesterday htc u ultra my companion he does not want to start it is blocked on htc and becomes very hot!
I tried several things seen on xda but there I am completely blocked.
I have access to different things, booloader, recoverry, etc ... but nothing changes I did a factory reset but the problem does not evolve
I tried to flash it with a ROM ruu but he told me that it is not the good CID. taken here https://forum.xda-developers.com/u-...stock-htc-ultra-dual-sim-1-64-400-10-t3758077
after i have an idea but i do not know if this is possible i have access to someone who has the same phone bought at the same place at the same time is it possible to extract the RUU rom to reinject it into that of my wife ???
I am hopeless we leave in 8 days and my wife finds herself without phone can you m help me to find the good RUU or extract that of my friend to reinject it?
the model is this one https://www.eglobalcentral.fr/htc-u-ultra-64go-4g-dual-sim-desimlocke-blanc-fr.html
apparently it's a Taiwanese model double sim
thanks for all the help !!
PS it was all original not rooted nor bootloaded unlocked just the update ota do

It would be better if you post the threads links properly, yours got truncated.
If you have, as you claim, the Taiwanese Dual SIM model you should be able to follow the downgrade procedure from Oreo to Nougat. I did it multiple times.
You cannot extract RUU. It is specially prepared package that performs several upgrade operations separately. You can only make dump of already installed system but for that you do need an unlocked bootloader and custom recovery (TWRP) on both devices.

QDT said:
It would be better if you post the threads links properly, yours got truncated.
If you have, as you claim, the Taiwanese Dual SIM model you should be able to follow the downgrade procedure from Oreo to Nougat. I did it multiple times.
You cannot extract RUU. It is specially prepared package that performs several upgrade operations separately. You can only make dump of already installed system but for that you do need an unlocked bootloader and custom recovery (TWRP) on both devices.
Click to expand...
Click to collapse
sorry i corrected the links.
on the other hand I can do this procedure despite that I have access only to bootloader and recovery?
I'm not an expert I thought I can just flash with a RUU but I can not find one

bibou0007 said:
sorry i corrected the links.
on the other hand I can do this procedure despite that I have access only to bootloader and recovery?
I'm not an expert I thought I can just flash with a RUU but I can not find one
Click to expand...
Click to collapse
It seems to me you have got yourself a wrong RUU. The ones from the post are for India, not Taiwan.

Surely I can not get my hands on a Taiwanese RUU!
do you know where can I find a link?

bibou0007 said:
Surely I can not get my hands on a Taiwanese RUU!
do you know where can I find a link?
Click to expand...
Click to collapse
Here is one:
https://androidfilehost.com/?fid=962021903579498986

thank you very much I test his and come tell you!

it does not work it tells me that it's not the right version android I have to find an android 8
thank you

bibou0007 said:
it does not work it tells me that it's not the right version android I have to find an android 8
thank you
Click to expand...
Click to collapse
We don't have RUU 8.0. Try boot to download mode and flash TWRP recovery. Downgrade to Nougat (7.0).