Database Info

Accelerometer stops working

I'm running the latest release on my Oneplus 64Gb. I've experienced this 2 times already. My screen rotation just stops. Happened both times in the morning when trying to watch a video on YouTube. Only solution is a reboot.
Is anyone else seeing this sporadic behavior with the device screen rotation?

greystealth said:
I'm running the latest release on my Oneplus 64Gb. I've experienced this 2 times already. My screen rotation just stops. Happened both times in the morning when trying to watch a video on YouTube. Only solution is a reboot.
Is anyone else seeing this sporadic behavior with the device screen rotation?
Click to expand...
Click to collapse
I think i've just experienced it. No idea if it's related to YouTube. CM 11S 30O

Happening to me on homescreen with adwlauncher, rooted.

same problem here,
can happen on any screen, rotation stops, if checking accelerometer its dead, reboots revives it

If you're running CM11 nightly, the 27/10 had this problem

+1
accelerometer and compass stops working, reboot solved the issue, I was afraid it was a hardware problem but it seems soft related at least.

same problem here, solution ?

acetrip said:
same problem here, solution ?
Click to expand...
Click to collapse
Reboot or dirty flash the rom.
This problem is only happening for me when i install optimized dalvik libs.
Sent from my A0001 using XDA Free mobile app

Solution found
I found a solution on the cyanognemod forum !
Download the last CM nightlies (zip file) you found, extract it, and flash with fastboot manually thoses files:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash boot boot.img
fastboot flash dbi sdi.mbn
fastboot reboot

Stuck at "Launching flashstock.bat"

So I had an old Nexus 5 running a custom KK rom. I tried getting it back to stock using Wugs Toolkit. I've been playing with it for hours trying to get it to work. I ended up making it worse and it gets stuck on Google Logo now. I tried using the revert to stock option on the toolkit. It looks like everything is working.. Here is the log..
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: hammerhead
finished. total time: 0.001s
Launching flashstock.bat
and then it just stops.. I tried downloaded two seperate .tgz images from Google. They both do the same thing. It doesn't go out of the bootloader screen or anything. It writes the radios and that's about it.

This is a *very* high-level suggestion - there are many tutorials that take you through drivers/ADB, etc. I just want to give you the script I followed for the manual procedure, which turned out to be extremely quick and simple.
After suggesting Wugfresh's NRT to several people in these forums (I'm a very big fan) I decided to refresh my Nexus 6 with the latest image and make it unencrypted - a problem that doesn't exist on the N5. I wasn't sure that NRT would do this for me, since the script automatically restarts the device and I wanted to be sure that it didn't start before I had flashed a modified no-encrypt boot image, since it would just encrypt itself again. So I downloaded the factory image, a no-encrypt boot image (thanks, doitright ) and TWRP - naturally being very careful to get the right ones. I unzipped the TGZ and the image files down to their final *.img components. To make things simple I renamed the various images to one-word names (e.g. radio.img). I put all of them in the same directory as ADB & fastboot.
Since all Nexus devices are updated the same, this should also work for you. Since you've used NRT I'm guessing that you have the PC drivers already installed. You'll also need ADB/Fastboot. Switch on USB debugging, connect the N5 to your PC, and in a CMD window type these commands:
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot -w flash system system.img
fastboot flash cache cache.img
fastboot reboot
Some of these may be overkill (I believe the -w wipe command erases userdata anyway), but it worked for me.
I would say take a TWRP image first as well so that you can recover, but it sounds as if you have nothing to recover anyway.
If the more expert member want to suggest amendments to the script, I won't be insulted...

dahawthorne said:
Switch on USB debugging, connect the N5 to your PC, and in a CMD window type these commands:
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery twrp.img
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot -w flash system system.img
fastboot flash cache cache.img
fastboot reboot
Click to expand...
Click to collapse
USB debugging means nothing if you're trying to use fastboot.
http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
gregs1213, stop using a toolkit, since you don't know what you're doing. read the above link and the following one as well:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701

Just trying to help, beekay...
Thanks for the link - I'll read it carefully.

dahawthorne said:
Just trying to help, beekay...
Thanks for the link - I'll read it carefully.
Click to expand...
Click to collapse
Hey, sure, I didn't mean to "attack" you. I noticed that you wanted to help. Really. Thanked you for that.

No worries, beekay. Posts don't allways mean what they look like, which is why we have smilies.
And I did read the articles. I tried with my N6 to attach it in bootloader mode with no USB debugging, and you're absolutely right. I suppose I just read "Remember to switch on USB debugging" so often that I assumed it was needed for any sort of work. Thanks for the tip. It's things like this that encourage all of us to try new things - like flashing a ROM manually instead of with NRT...

This problem occurred to me when I updated Wugfresh NRT to 2.0.6.
So I return back to 2.0.5 and this problem solved.
Try using NRT 2.0.5 to see if the problem solved or not

mraramesh said:
This problem occurred to me when I updated Wugfresh NRT to 2.0.6.
So I return back to 2.0.5 and this problem solved.
Try using NRT 2.0.5 to see if the problem solved or not
Click to expand...
Click to collapse
Toolkits don't teach people stuff, they just hide it from them

mraramesh said:
The problem is Wugfresh NRT
Click to expand...
Click to collapse
I edited your post to show you the error of your ways
Sent from my Xperia z5 using Tapatalk

While replying to another thread asking for help in installing a ROM, I linked to this, and I notice that the OP never did tell us if he managed to get his device working. Feedback is not only helpful to the forum, it's also polite.
So bump for gregs1213's attention...

Serious OnePlus One Bootloop Issue

Hey guys, I have a 64gb OnePlus One and it's seems to be stuck on an infinite bootloop(soft-brick). I am able to access both fastboot mode and recovery. My phone's bootloader is unlocked and I have the stock cyanogen recovery presently.
I had run into this issue several times earlier, and was quickly able to resolve it... Either by flashing a different custom rom or factory resetting the phone using TWRP recovery and it all worked out, but this time, nothing seems to work. After reading several guides and watching many videos, I frequently came across that flashing the stock(cm12.1 factory image) would fix the bootlooping issue once and for all, and it turns out and it did work, but only momentarily and it was quite weird infact... After the fastboot flashing process was done, the phone started bootlooping once again and I let it happen for 5-10 mins, after which I gave up and turned it off. But after leaving it off for sometime and then turning it on later, it did boot up once for sometime to the initial boot setup screen, only to start rebooting again.
I gave it some more time to be turned off and the next time I turned it on, it booted normally and everything seemed to be working fine... I installed whatever apps I needed, downloaded music and everything looked great, but then it started crashing into random reboots once again, at random instances, but using the temporary power off technique I talked about earlier, I made it work somehow, until even that stopped working.
I've tried literally every method, even locking and unlocking the bootloader and then flashing stock again... Also... using the single command method mentioned which fixed persist partitions on that phone, and even that was in vain.
Infact, now my phone is in an even worse condition, it won't even make it past the 1+ logo, just keeps on rebooting there. Any help with this issue would be greatly appreciated... Thank you.

Sounds like the exact final stage issue that my friend was having. Finally his phone even bootlooped in fastboot when he was on holiday.
I had the phone with me for a couple of hours when he returned and nothing worked. I couldn't even connect to the pc in the end. I personally think his memory had an issue.
Seems like you tried all you could. Does it stay on in fastboot?
In the end I had my friend rma his phone and Oneplus said the warranty was void because one sticker was slightly red .... complete bull story since the phone was never ever in contact with water or other liquid stuff and they would not answer a single question in regards to that. So my advice if someone else doesn't have a hocus pocus solution is to check if you have warranty and see if you can't see these moisture indicator through the headphone jack and try to go for warranty repair.

Download the latest fastboot signed ROM from here: https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash recovery recovery.img
fastboot flash userdata userdata_64G.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img

[DEV] Lineage OS for Oppo F1 (f1f)

Hi there!
I've been trying to port CM14.1 to my Oppo F1 (code f1f with Snapdragon 616). I got a build with backlight always on and a lot of things already working (touchscreen, 4G, camera).
After a few hours digging into the code and a dozen of kernel builds, I couldn't find a way to make the backlight brightness level work correctly. From my understanding, this Oppo device (among other CM friends sharing the same kernel repo) seems to be the only one using GPIO to initialize the backlight. It seems that the MSM video driver is using this kind of Qualcomm SoC « magic » registers to control the backlight.
Has anyone been working on this? Any repo recommandations from where I could take inspiration to fix this?
A picture to encourage anyone to work on this…

kdd998 said:
Hi there!
I've been trying to port CM14.1 to my Oppo F1 (code f1f with Snapdragon 616). I got a build with backlight always on and a lot of things already working (touchscreen, 4G, camera).
After a few hours digging into the code and a dozen of kernel builds, I couldn't find a way to make the backlight brightness level work correctly. From my understanding, this Oppo device (among other CM friends sharing the same kernel repo) seems to be the only one using GPIO to initialize the backlight. It seems that the MSM video driver is using this kind of Qualcomm SoC � magic � registers to control the backlight.
Has anyone been working on this? Any repo recommandations from where I could take inspiration to fix this?
A picture to encourage anyone to work on this�
Click to expand...
Click to collapse
Backlight works fine on cm13 builds. Are you using kernel source from the cyanogenmod git? Did you have to make any changes to the kernel source? CM kernel source was working fine for me with cm13 up to about a month ago but then started causing bootloops (seems to be something in the dtb). Also, does rotation work, I have been having problems using their sources with accelerometer. I do have a build of cm13 with everything working well, but it is using @uberlaggydarwin kernel source from github and I don't think he wants me to share things built from it (better moving forward to be on official cm sources anyway).

Try this op2 also has backlight issue in custom rom.
Group Butler [beta]:
Type the below commands in terminal to turn off backlight
su (give permission when prompted)
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness

MiniBlu said:
Backlight works fine on cm13 builds. Are you using kernel source from the cyanogenmod git?
Click to expand...
Click to collapse
Yes, the msm8939 kernel common to Oppo devices.
MiniBlu said:
Did you have to make any changes to the kernel source?
Click to expand...
Click to collapse
Yes, changes are necessary. I didn't have a look at audio yet, but the touchscreen driver needs changes, dtsi files to clear warnings and the lm3630 driver needs a lot of changes to make the probe work.
MiniBlu said:
CM kernel source was working fine for me with cm13 up to about a month ago but then started causing bootloops (seems to be something in the dtb).
Click to expand...
Click to collapse
Yes, but with cm-14.1, there's a big gap in the kernel source. It seems to be nearer the CAF source and all the ugly Oppo ifdefs are out (seriously, Oppo's coding style is awful ).
MiniBlu said:
Also, does rotation work, I have been having problems using their sources with accelerometer.
Click to expand...
Click to collapse
I'll try to see if rotation is OK but I have doubts. I didn't have a look at it yet. Which device is it?
Ucihaflash said:
Type the below commands in terminal to turn off backlight
su (give permission when prompted)
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
Click to expand...
Click to collapse
Thanks for the tip, I'll have a look, but I find it strange that this device is in the leds class, I thaught it was in the backlight class. It needs to be tried anyway

So, rotation doesn't work. But button-backlight is there, but I cannot control backlight. I'll continue digging…

Wow u actually been able to put cm14 on oppo f1. C
When you finish this will you make it public? Many people would love this

Of course, if ever I succeed, it's open source. The goal is to have an official device in CM. But on CM14.1, we're far from it. On CM13, I believe it's almost ready, but i'll let the actual devs who did the job take care of it.

Thanks so much. Good luck with cm14. Hope u succeed! ?

verry happy to see that, good luck thank's:good::good::good::good::good::good:

kddoran said:
verry happy to see that, good luck thank's:good::good::good::good::good::good:
Click to expand...
Click to collapse
- 6months latter
........... . .when you guys realize that Oppo has the worst vendor ive ever seen on the planet, bad,slowest(never)get update at all..

MiniBlu said:
Backlight works fine on cm13 builds. Are you using kernel source from the cyanogenmod git? Did you have to make any changes to the kernel source? CM kernel source was working fine for me with cm13 up to about a month ago but then started causing bootloops (seems to be something in the dtb). Also, does rotation work, I have been having problems using their sources with accelerometer. I do have a build of cm13 with everything working well, but it is using @uberlaggydarwin kernel source from github and I don't think he wants me to share things built from it (better moving forward to be on official cm sources anyway).
Click to expand...
Click to collapse
Which sources did you use to build? Last time I tried compiling from the official sources I got some errors building the kernel so I gave up but that was a while ago.

As an Oppo f1 user, good luck to your project since oppo never update its thing

kdd998 said:
Of course, if ever I succeed, it's open source. The goal is to have an official device in CM. But on CM14.1, we're far from it. On CM13, I believe it's almost ready, but i'll let the actual devs who did the job take care of it.
Click to expand...
Click to collapse
Is there a hope for getting officially build on CM

i am currently on project spectrum and want to flash back colour os through fastboot. has anyone done it before. i want to do it but have a habit of bricking my device. Would this be correct.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery.img
or
flashall
or will fastboot -w and fastboot update colouros.zip work?
which would work?

Jamie_oppo said:
i am currently on project spectrum and want to flash back colour os through fastboot. has anyone done it before. i want to do it but have a habit of bricking my device. Would this be correct.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery.img
or
flashall
or will fastboot -w and fastboot update colouros.zip work?
which would work?
Click to expand...
Click to collapse
no. none of the above will work. System image is to large to flash by fastboot.
To return to coulouros you would need to pull these files form the colouros.zip and put them in you fastboot folder
boot.img
logo.bin
NON-HLOS.bin
reserve4.img
rpm.mbn
sbl1.mbn
static_nvbk.bin
tz..mbn
then pull emmc_appsboot.mbn from magictricks.zip, and put it in fatboot folder.
then put twrp-3.0.2-0-f1f.img in fastboot folder.
then put modified colouroszip file from here on your external sdcard.
From cmd in fastboot folder run
fastboot flash boot boot.img
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash reserve4 reserve4.img
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash oppostanblk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash recovery twrp-3.0.2-0-f1f.img
fastboot boot recovery twrp-3.0.2-0-f1f.img
Unplug usb cable.
This should have flashed all firmware back to stock (except bootloader to magicktricks unlocked bootloader and recovery to twrp) and rebooted you into twrp. You can now WIPE data and cache then flash the colouros.zip. (once in colouros you may need to enable oem unlocking in developer settings and then do a fastboot oem unlock.)
From here if you want to go back to project spectrum you can just flash the colouros recovery I sent you earlier and the flash project spectrum from it.
*NOTE* all the above should work but you attempt this at your own risk. I take no responsibility for possible bad outcome.

Thanks so much. I will try this as soon as I can. If something goes wrong after fastboot boot the twrp image will I still have fastboot just in case??

MiniBlu said:
no. none of the above will work. System image is to large to flash by fastboot.
To return to coulouros you would need to pull these files form the colouros.zip and put them in you fastboot folder
boot.img
logo.bin
NON-HLOS.bin
reserve4.img
rpm.mbn
sbl1.mbn
static_nvbk.bin
tz..mbn
then pull emmc_appsboot.mbn from magictricks.zip, and put it in fatboot folder.
then put twrp-3.0.2-0-f1f.img in fastboot folder.
then put modified colouroszip file from here on your external sdcard.
From cmd in fastboot folder run
fastboot flash boot boot.img
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash reserve4 reserve4.img
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash oppostanblk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash recovery twrp-3.0.2-0-f1f.img
fastboot boot recovery twrp-3.0.2-0-f1f.img
Unplug usb cable.
This should have flashed all firmware back to stock (except bootloader to magicktricks unlocked bootloader and recovery to twrp) and rebooted you into twrp. You can now WIPE data and cache then flash the colouros.zip. (once in colouros you may need to enable oem unlocking in developer settings and then do a fastboot oem unlock.)
From here if you want to go back to project spectrum you can just flash the colouros recovery I sent you earlier and the flash project spectrum from it.
*NOTE* all the above should work but you attempt this at your own risk. I take no responsibility for possible bad outcome.
Click to expand...
Click to collapse
i extacted all the files and put twrp and the magictricks thing in the fastboot folder
fastboot flash boot boot.img
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin These all worked fine
but when i got to reserve4 i got C:\Users\ponyd\Desktop\back to colour os>fastboot flash reserve4 reserve4.img
target reported max download size of 268435456 bytes
sending 'reserve4' (5176 KB)...
OKAY [ 0.200s]
writing 'reserve4'...
FAILED (remote: size too large)
finished. total time: 0.216s
i shat my self when that happened? i then flashed the boot.img logo and modem of project spectrum and went back to spectrum. DId i do something wrong?

Backlight fix
Try coloros setting app. Search and u will get it.

I'm actually under spectrum project hope you could port this cm14.1 for OPPO f1...
Thanks

I know this may be abit reluctance but you may want to open source the project on what you have now and list what is working and what's isn't, and I'm sure people will contribute to the project given that is qcom there should not be much of an issue to get it working.

[ROM][8.0.0][STOCK] Stock Android 8.0.0 ROM for Moto E5 Play (James) XT1921-3

I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Code:
fastboot devices
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:

Thanks for posting this. I was actually going to upload it myself. You save me from having to do the work

weakNPCdotCom said:
Thanks for posting this. I was actually going to upload it myself. You save me from having to do the work
Click to expand...
Click to collapse
Not a problem.... I actually found most of the firmwares that MotoJunkie01 had posted, I might repost his firmware post (copy and paste) and replace the links after i upload them to my own Gdrive, when I have time....

AesopRock127 said:
Not a problem.... I actually found most of the firmwares that MotoJunkie01 had posted, I might repost his firmware post (copy and paste) and replace the links after i upload them to my own Gdrive, when I have time....
Click to expand...
Click to collapse
sweet. sounds great man. thank you

NM connection working now

https://mirrors.lolinet.com/firmware/moto/ look here for firmware and make sure its correct one and up to date before flashing it.

AesopRock127 said:
I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:
Click to expand...
Click to collapse
How did you get your phone to work meaning when I call some one they can't hear me but I can hear them .I re-flashed so many ROMs already that I'm staying on GSI Rom 8.1.0 Hanna metro PC's also I did flash stock Rom and still the see problem maybe it's time for replacement. It's been 3 days searching and asking for help. Maybe device to new idk ..

skullkid383 said:
https://mirrors.lolinet.com/firmware/moto/ look here for firmware and make sure its correct one and up to date before flashing it.
Click to expand...
Click to collapse
dude this link is worth money. amazing. thank you so much.

weakNPCdotCom said:
dude this link is worth money. amazing. thank you so much.
Click to expand...
Click to collapse
Yeah I used it on my Perry before I got hannah so it was first place looked when I needed Hannah fw

Googleme35 said:
How did you get your phone to work meaning when I call some one they can't hear me but I can hear them .I re-flashed so many ROMs already that I'm staying on GSI Rom 8.1.0 Hanna metro PC's also I did flash stock Rom and still the see problem maybe it's time for replacement. It's been 3 days searching and asking for help. Maybe device to new idk ..
Click to expand...
Click to collapse
I got mine to work because I have a James device.... You mention Hannah device so guessing you flashed the wrong firmware and that's the issue. I have the James xt1921-3

AesopRock127 said:
I got mine to work because I have a James device.... You mention Hannah device so guessing you flashed the wrong firmware and that's the issue. I have the James xt1921-3
Click to expand...
Click to collapse
Ok Thanks

I'm glad i could be of assistance,i was actually hunting down root methods for my GFs samsung and saw a video that linked to the user who uploaded it to AFH, rootjunkie was the channel if i recall,so i can't take all of that sweet credit. Yall have fun,but not too much fun

AesopRock127 said:
I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Code:
fastboot devices
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:
Click to expand...
Click to collapse
PLEASE tell me how you fixed the IMEI/SIM not recognized issue. I can't figure this out at all. Thanks!

OMG!!!! This was a god send. Thank you guys for putting this together for us. I thought all hope was lost. My phone is back and running. YaY!!!!!!

weakNPCdotCom said:
dude this link is worth money. amazing. thank you so much.
Click to expand...
Click to collapse
I keep getting unsecured network... Is this an issue from my end?

How do you backup IMEI in TWRP?
EFS?
Mine won't mount data for backup and cache in red
Or should I do it another way?

I have XT1924-2 AND I TOO HAVE IMEI=0 ANY FIXES?

Thank you!
This was very helpful, thanks!

TheLastAlphaUK said:
I have XT1924-2 AND I TOO HAVE IMEI=0 ANY FIXES?
Click to expand...
Click to collapse
Flash most up-to-date software

skullkid383 said:
Flash most up-to-date software
Click to expand...
Click to collapse
That's a weird Necro-Response. Also updating doesn't fix IMEI, (even though this was over a year ago, they would need an IMEI flasher and the box/numbers found somewhere else)