I'm new to the forum and have had my Defy+ since Jan 2011 but couldn't find an answer to the issue I have. My Defy+ ME525 China Retail now has 45.0.2310.MB526.AsiaRetail.en.03 installed and build 4.5.1-134_DFP-231 which has been stable since last December when I loaded it via RSD Lite. My issue is despite getting rid of the mainland China retail version, they denied access to Google Play, many APK files, and ALL social media that wan't Chinese, I am still having issues with Google+ crashing all the time. My MotoBlur is configured for Twitter and Facebook but it won't update them or receive updates when I am out of China (tried when in Cambodia last week and no updates worked either way). When out of China I was able to download and get Facebook to work but not Google+.
I was debating to re-image with DFHKT_U_4.5.2-109_DHT-25-4_SIGNED_USADEFYPRCB1B50AA00A.0R_JRDNGIBRRTHKTW_P0 24_A023_HWp3a_Service1FF but am not sure if this would fix that issue or not, not a big issue just a minor annoyance. I have also seen issues with the camera causing the phone to reboot, lockups when turning on the APN and sometimes airplane mode just applying itself out of the blue. Is the above US version more stable and would it work better or should i just deal with the minor issues and leave well enough alone?
I also find the phone is slower and hangs more often now and not sure if I should wipe it and start over or not? The phone is NOT rooted, RDS Lite loaded the Asia Retail version fine, I need that for sending and receiving SMS in Chinese characters. Thanks!
Defy is not region coded. You can use the other sbf, but it will not really increase performance, only your Google problems should be solved(and by a clean install stability issues should disappear). Your other problems should not occur on a clean install, try wiping data and cache to check if the problems recur
Sent from my MB526 using Tapatalk 2
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
Did anyone face the problem of heating after updating to nougat 7.0? I received official OTA update before 5 days.
After updating to it, once it strangely got high temperature.
And also it slows down for some of the app.
While charging, it slows down the speed of opening keyboard and apps.
It also takes time to open google photos after taking photos.
Before updating, there wasn't any problem like this.
Can anyone help me about this? Should i downgraded to marshmallow 6.0?
And if yes, then how can i downgraded to stock marshmallow given by moto?
bhautik.andhariya said:
Did anyone face the problem of heating after updating to nougat 7.0? I received official OTA update before 5 days.
After updating to it, once it strangely got high temperature.
And also it slows down for some of the app.
While charging, it slows down the speed of opening keyboard and apps.
It also takes time to open google photos after taking photos.
Before updating, there wasn't any problem like this.
Can anyone help me about this? Should i downgraded to marshmallow 6.0?
And if yes, then how can i downgraded to stock marshmallow given by moto?
Click to expand...
Click to collapse
Did you factory reset after updating.
If no, do a factory reset and then report bugs.
First people cry for updates and then they update they cry for bugs which do not even exist.
Hello sir,
I updated my moto to nougat and factory reset due to lagging. Now struck at initial setup wizard.
Its asking to enter email I'd but its not going further.
Any solution??????
You might want to reflash using fastboot and try again. I haven't had any heating issues after the updated. Initially it was slow but got faster the more it learned my usage pattern.
I am not able to download anything from the play store after i factory reset my Moto G4 Plus. Did every possible try but again facing the same problem.
rply ASAP
rawat0708 said:
I am not able to download anything from the play store after i factory reset my Moto G4 Plus. Did every possible try but again facing the same problem.
rply ASAP
Click to expand...
Click to collapse
Have you updated to Nougat, and are you on roaming mobile data?
I bought my phone ( Redmi note 7 ) almost 2-3month ago. I was really impressed and satisfied with my battery performance. But recently I'm facing battery draining issue. I've unlocked my bootloader is this happening beacuse of unlocking bootloader ( i didn't install TWRP or i didn't root my device just unlocked the bootloader )
Many people's are saying probably this is happening beacuse of unlocking bootloader and also they are giving explanation like system was optimized, after unlocking bootloader its deoptimized on the other hand some people are saying it's happening beacuse of the new Google play service it will be fine in next update
But I'm not sure why it's happening. Now i want to know if it's happening beacuse of Google play service then it will be fine in the next update thats not a big deal but if it's happening beacuse of unlocking bootloader then what should i do ( don't advice to flash stock rom or anything i love miui ) ? Or anybody can you plz explain the real reaaon why I'm facing this prblm and how can i get rid out of it
Enayet_saidul said:
I bought my phone ( Redmi note 7 ) almost 2-3month ago. I was really impressed and satisfied with my battery performance. But recently I'm facing battery draining issue. I've unlocked my bootloader is this happening beacuse of unlocking bootloader ( i didn't install TWRP or i didn't root my device just unlocked the bootloader )
Many people's are saying probably this is happening beacuse of unlocking bootloader and also they are giving explanation like system was optimized, after unlocking bootloader its deoptimized on the other hand some people are saying it's happening beacuse of the new Google play service it will be fine in next update
But I'm not sure why it's happening. Now i want to know if it's happening beacuse of Google play service then it will be fine in the next update thats not a big deal but if it's happening beacuse of unlocking bootloader then what should i do ( don't advice to flash stock rom or anything i love miui ) ? Or anybody can you plz explain the real reaaon why I'm facing this prblm and how can i get rid out of it
Click to expand...
Click to collapse
Tested: there is something strange between Play Services, Facebook and the way the stock kernel manages the workloads, it will be fixed in the next update, play services tends to mess with battery every x versions, Facebook too, the kernel 'problem' was not expected, just wait for an update of MIUI or Google.
Model : G950U1 Samsung Galaxy S8
My camera doesn't work after update pie. There's almost no way I haven't tried. I touch the camera app and the black screen turns on and off in 2 seconds. When I touch the flashlight button, " Can't turn on flashlight because the light is being used by another app." the text comes out.
I tried some solutions on forums:
Clear camera app data and clear cache but not working.
Safe mode not working
Factory reset not working
Hard reset not working.
I changed software G950U1UES6DSI1 (android 9 on September) to G950U1UES6DSG1 (android 9 but old on July) not working.
Also;
My Samsung Galaxy S8 phone can't return to the old version. Because my software binary is 6 level how can do anything?
Same problem
I have exactly the same problem with my G950U.
I did everything said above to try to fix this but it's still the same.
However, I managed to recover the camera and flashlight with an earlier version of PIE but it didn't last. Before it defitively stop working, I had some problems with the front camera who forced camera stop sometimes.
My actual ROM is the last : G950USQSDSJ1
Please HELP US !!!!
centermap said:
Model : G950U1 Samsung Galaxy S8
My camera doesn't work after update pie. There's almost no way I haven't tried. I touch the camera app and the black screen turns on and off in 2 seconds. When I touch the flashlight button, " Can't turn on flashlight because the light is being used by another app." the text comes out.
I tried some solutions on forums:
Clear camera app data and clear cache but not working.
Safe mode not working
Factory reset not working
Hard reset not working.
I changed software G950U1UES6DSI1 (android 9 on September) to G950U1UES6DSG1 (android 9 but old on July) not working.
Also;
My Samsung Galaxy S8 phone can't return to the old version. Because my software binary is 6 level how can do anything?
Click to expand...
Click to collapse
you went from a sprint firmware to a t-mobile firmware? why?
anyways, get the patched version of Odin and flash this
https://www.sammobile.com/samsung/galaxy-s8/firmware/SM-G950U1/XAS/download/G950U1UES6DSG1/282377/
kijise said:
I have exactly the same problem with my G950U.
I did everything said above to try to fix this but it's still the same.
However, I managed to recover the camera and flashlight with an earlier version of PIE but it didn't last. Before it defitively stop working, I had some problems with the front camera who forced camera stop sometimes.
My actual ROM is the last : G950USQSDSJ1
Please HELP US !!!!
Click to expand...
Click to collapse
pretty much the same thing for you. Flash the unbranded firmware and see how that goes for you
Thanx for your answer but I've done it with no result, already.
pretty much the same thing for you. Flash the unbranded firmware and see how that goes for you[/QUOTE]