Related
i had upgraded my mexi-maxx to lollipop a few months ago and could no longer stand it. outside of being picky with my phone, the GPS didn't work as I had hoped.
i reverted back to kitkat by means of a TWRP backup I had. Had some issues with doing so. some of my images would not work, but a stock on of KK did. could not use any of @ChazzMatt images either; nor factory images as RSD pinged a FAIL. started getting worried, but just about all good now.
the phone now boots directly to bootloader mode and i have to choose 'start' to boot into system.
is there a way to change this? thanks all.
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Semseddin said:
You can try Brazil 22.34.16 lollipop build, it is the most stable 5.0.2 for moto maxx / turbo atm. Your issue is caused by the incompability with the lollipop bootloader and 4.4 kitkat twrp image. Take a copy of your nandroid backup to your pc and flash 4.4.4 images except gpt.bin.
http://forum.xda-developers.com/droid-turbo/help/tutorial-how-to-flash-official-firmware-t3074724 ( following 5.step )
Then flash twrp recovery and restore your 4.4.4 nandroid, it will be fine this time.
Click to expand...
Click to collapse
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
snowboardwcu said:
Thanks. really dislike LP as a whole. are there advantages i'm not seeing? battery was the same, wasn't really faster, GPS terrible (used stock rooted and CM12.1)
want to make sure I understand what i'm doing. according to thread you linked to (thank you btw I could not find that earlier too busy freaking out) because i took the LP OTA i have the upgraded LP bootloader, but I do not need to downgrade it to go back to KK? meaning LP BL is backwards compatible?
Click to expand...
Click to collapse
You need to downgrade to 4.4.4 with stock images except gpt.bin or else, it is normal having issues like you're facing. Lollipop bootloader is meant to work on lollipop system. Anyway, just flash 4.4.4 full images with mfastboot except gpt.bin, then flash your twrp recovery and restore your kitkat nandroid. It will be fine.
I downgraded my xt1225 back in time with the same tutorial and it works fine.
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
snowboardwcu said:
this works perfectly. old twrps work again.
trying to the india version of LP as some are saying its vetter, installed and then put cm12.1 back on. gonna give it a week or so and see if GPS locks better. if not, back to kitkat. thanks for the help.
Click to expand...
Click to collapse
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Semseddin said:
India firmware is as bogus as a software can get
Click to expand...
Click to collapse
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Semseddin said:
India firmware is as bogus as a software can get and they didn't deploy patch ota's to fix its issues. Your best stock lolipop bet is brazil 5.0.2
Click to expand...
Click to collapse
snowboardwcu said:
bogus as in not official or bogus as in crap sw&support? again, no interest in using stock LP. cm12.1 fits all my needs except the double swipe to pattern unlock, which from what i read i'm stuck with.
at this point i'm only interested in the best driver set for the phone. interested in getting better GPS lock and hopefully better reception at work, in the middle of a giant metal building (kitkat worked much better IMO WRT to reception and LTE/HSPA+ handover)
Click to expand...
Click to collapse
If you were just running stock LP -- which you say you do not want to do -- then @Semseddin is correct that Brazil and Mexico factory images are better than India. Just because they both have newer updates India was never given.
In my images thread you can see,
Brazil: QUARK_RETBR_5.0.2_LXG22.33-12.13_cid12_subsidy-DEFAULT_CFC.xml.zip
vs
India: QUARK_RETEU_INDIA_5.0.2_LXG22.33-12.11_cid7_subsidy-DEFAULT_CFC.xml.zip
Then, @Jaocagomez has an OTA which takes it to:
OTA to 22.34.16 Brasil Retail Stock Lollipop 5.0.2 /// Blur_Version.22.34.16.quark_retbr.retbr.en.BR.zip
But CM12.1 beats all that by having 5.1.1.
Yes, CM 12.1 (5.1.1) is still using the stock 5.0.2 kernel source -- because Motorola has not yet released 5.1 kernel source they gave to the XT1254 Droid Turbo back at the beginning of July. But it's still 5.1.1 with 5.02 kernel source, NOT 5.0.2. with 5.02 kernel source. It's a vast improvement! Stock 5.0.2 was too laggy for me.
So, for me running CM12.1 (or another 5.1.1 custom ROM) gives me the best of both worlds. I have the latest kernel source/radio that Motorola has released for our phones, while still having 5.1.1.
_________
Now having said all that, my wife and I have two XT1225.
I flashed both to India LP 5.0.2, then flashed CM.
I also re-flashed the India radio and bootloader (5.0.2) found in the CM12.1 op post just to make sure.
I have no problem with GPS. I use GPS every day. But I use TopNTP. See this post:
http://forum.xda-developers.com/showpost.php?p=62320192&postcount=624
_____
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Fixed this issue. See here:
http://forum.xda-developers.com/showpost.php?p=63048064&postcount=696
ChazzMatt said:
The only issues I have with CM12.1 is my phone seems to lock on to HSPA when leaving Wi-Fi network even though there are strong LTE signals around -- and even though I have "LTE Preferred" chosen. As I drive it will eventually move from HSPA to LTE, but takes like 15-20 minutes.
If I stop the car, remove and put back in the SIM card 2 or 3 times, then it finally locks onto LTE network that was there all along!
It was a change CM made to APNs/telephony back end of July that seems to cause this. (I kept my wife's phone on the July 29 nightly. We will be in the car, she will have LTE and I will have HSPA. Arghhh.)
But I put up with it, and keep flashing new nightlies -- hoping it will be fixed -- and also because other than that CM12.1 is very smooth and much better than stock 5.0.2. I don't want to flash my phone back to July 29 nightly. I still have it -- but I would have to wipe my phone completely and reinstall for it to work. I already tried just flashing that older nightly over a newer one and I got boot loops. I restored latest back up from recovery and haven't bothered since.
Click to expand...
Click to collapse
Have you received it and any changelog? Battery seems much better to me now.
I received it also, no issues so far.
But how do you make any assumptions on battery life in case you just received it today?
viktor1983 said:
I received it also, no issues so far.
But how do you make any assumptions on battery life in case you just received it today?
Click to expand...
Click to collapse
I did update at 7.30 am, %100 battery percent. Same daily usage and more battery left
hiphoplife77 said:
Have you received it and any changelog? Battery seems much better to me now.
Click to expand...
Click to collapse
Updated this morning. Battery seems the same. But it was good before.
WiFi keeps disconnecting like before on previous versions. On Oreo it works like normal. Do you guys get this on Pie?
barret95 said:
WiFi keeps disconnecting like before on previous versions. On Oreo it works like normal. Do you guys get this on Pie?
Click to expand...
Click to collapse
Sometimes. I want to rollback to android 8 but I cant.
It's easy to rollback, just need flashtool and xperiFirm that is integranted into flashtool, CE1 (Central Europe) variant is on Oreo, so you can download that version and flash it. You will lose all you data, deleting everything assures that the instalation will be OK
barret95 said:
WiFi keeps disconnecting like before on previous versions. On Oreo it works like normal. Do you guys get this on Pie?
Click to expand...
Click to collapse
Not here.
juandiazmora said:
It's easy to rollback, just need flashtool and xperiFirm that is integranted into flashtool, CE1 (Central Europe) variant is on Oreo, so you can download that version and flash it. You will lose all you data, deleting everything assures that the instalation will be OK
Click to expand...
Click to collapse
I succeed with germany version of oreo. I found the ftf file from one of czech website and flashtool recognise that. Happy with this firmware now.
These updates are just monthly security, so I don't thing they would mess with battery life or performance of the phone whatsoever.
The actual build of Pie didn't change from the first one in November 2018, just security updates and thats all.
They didn't even bother to fix the sound issue, that is mostly common reported one.
Regarding WiFi problem, mine works without problems from the day 1 on Pie.
mrkubix said:
These updates are just monthly security, so I don't thing they would mess with battery life or performance of the phone whatsoever.
The actual build of Pie didn't change from the first one in November 2018, just security updates and thats all.
They didn't even bother to fix the sound issue, that is mostly common reported one.
Regarding WiFi problem, mine works without problems from the day 1 on Pie.
Click to expand...
Click to collapse
What is that sound problem that is reported by users ?
Thank you
It's so strange that the WiFi works fine on some phones and doesn't work at all on the rest. It can't be a hardware issue since the Wifi works fine on Oreo.
mrkubix said:
These updates are just monthly security, so I don't thing they would mess with battery life or performance of the phone whatsoever.
The actual build of Pie didn't change from the first one in November 2018, just security updates and thats all.
They didn't even bother to fix the sound issue, that is mostly common reported one.
Regarding WiFi problem, mine works without problems from the day 1 on Pie.
Click to expand...
Click to collapse
I have lots of WiFi problems on first version of Oreo, now they are a lot better, not perfect, but at least I can connect to my 5GHz WiFi at home, previously that was no possible
juandiazmora said:
It's easy to rollback, just need flashtool and xperiFirm that is integranted into flashtool, CE1 (Central Europe) variant is on Oreo, so you can download that version and flash it. You will lose all you data, deleting everything assures that the instalation will be OK
Click to expand...
Click to collapse
Is there a way to preserve appdata without rooting the device?
P.S.
To anyone who is rooted, is the there a rooted build available for this yet?
Hi all,
I recently upgraded to Android 10 and suddenly the mic of my bluetooth earphones stop working, battery draining very quickly, phone heating. Is there a solution to this?
If not, how to I flash stock ROM from scratch. My bootloader is locked with no root. I want to keep my bootloader locked if its possible.
Device Info:
OnePlus 7
GM1901
Oxygen OS 10.0.1.GM57AA
Thanks
faraz1992 said:
Hi all,
I recently upgraded to Android 10 and suddenly the mic of my bluetooth earphones stop working, battery draining very quickly, phone heating. Is there a solution to this?
If not, how to I flash stock ROM from scratch. My bootloader is locked with no root. I want to keep my bootloader locked if its possible.
Device Info:
OnePlus 7
GM1901
Oxygen OS 10.0.1.GM57AA
Thanks
Click to expand...
Click to collapse
You can do a factory reset from Android settings - system - reset - last point.
That's what I recommend as I'm sure there's something going roque on your phone
A friend had the same issue on the same device and Android 10 update. He flashed stock ROM and problem was solved. Is there a noob guide for flashing ROM on Oneplus7
faraz1992 said:
A friend had the same issue on the same device and Android 10 update. He flashed stock ROM and problem was solved. Is there a noob guide for flashing ROM on Oneplus7
Click to expand...
Click to collapse
Do what I suggested above, that's the same. Or download the 10.0.1 stock rom and flash it from local, but that's more complicated.
I unlocked my bootloader, flashed twrp, flashed stock rom after a full wipe. Still the problem is there. Can someone please check if this is a hardware level problem in all devices?
faraz1992 said:
I unlocked my bootloader, flashed twrp, flashed stock rom after a full wipe. Still the problem is there. Can someone please check if this is a hardware level problem in all devices?
Click to expand...
Click to collapse
You didn't mention if you have tried another headset. Also you did not mention what headset you have, maybe someone has it.
strongst said:
You didn't mention if you have tried another headset. Also you did not mention what headset you have, maybe someone has it.
Click to expand...
Click to collapse
I tried other headset. Doesn't work. I'm using boAtRocker 255.
Thanks
you can go to the oneplus website, download the official original rom to the storage, go to settings, system, system updates, click on the gear icon in upper right, and select local upgrade, then select the official rom you downloaded to the storage, that will install the original software.
This is just for a simple discussion. I've tried flashing the open beta, and since Developer Preview 4 I've not been able to get service. Flashing other modem versions ends up breaking the phone. The new modem is also ~ half the size of the old versions.
Anyone had any luck?
I'm on DP4, should I back up my modem before updating?
Edit: It works perfectly for me on TMobile converted.
Dameon87 said:
This is just for a simple discussion. I've tried flashing the open beta, and since Developer Preview 4 I've not been able to get service. Flashing other modem versions ends up breaking the phone. The new modem is also ~ half the size of the old versions.
Anyone had any luck?
Click to expand...
Click to collapse
Did you flash Global 10.5.12 first?
I can't get any 5G with global or beta. Might need to see what's going on when I return to stock.
shaneg79 said:
Did you flash Global 10.5.12 first?
Click to expand...
Click to collapse
Yes, I flashed 10.5.12 first then did a local upgrade to open beta 1. No service at all on reboot.
Dameon87 said:
Yes, I flashed 10.5.12 first then did a local upgrade to open beta 1. No service at all on reboot.
Click to expand...
Click to collapse
Did you backup your modem before?
shaneg79 said:
Did you backup your modem before?
Click to expand...
Click to collapse
No, I've tried flashing the modem from 10.5.12 from fastboot as extracted from the payload.bin
Dameon87 said:
No, I've tried flashing the modem from 10.5.12 from fastboot as extracted from the payload.bin
Click to expand...
Click to collapse
Then you will have to flash back to the T-Mobile firmware and upgrade to 10.5.20 then reunion bootloader backup your modem and everything then covert
I have my tmobile op8 on the open beta and this was the only way I was able to have service.
1. Msm to tmobile 10.5.7
2. Flash unlock token
3. Unlock bootloader
4. Flash global 10.5.7 (I still had service at this point, and I did not flash any modem)
5. Downloaded oxygen updater apk from chrome (to avoid restoring everything from the Google play store just yet)
6. Updated to 10.5.12
7. Switched oxygen updater settings to download open beta and then flashed from system settings (still had service, no modem flash)
8. Reset the phone from settings (to go through set up and restore all my data from play store)
This was just what I had done and it did work for me so good luck if you decide to try. I only did the chrome apk file for oxygen updater to avoid having a bunch of data on my phone when going to the beta. I haven't had any weird bugs and it's been smooth for me
Not sure why some are having this issue, I have signal with no issues on beta. I was on .12 and went to beta.
I had this issue on my other OnePlus 8, a data wipe fixed my signal entirely.
Dameon87 said:
Yes, I flashed 10.5.12 first then did a local upgrade to open beta 1. No service at all on reboot.
Click to expand...
Click to collapse
That sucks. I was on 10.5.12 a couple nights ago. Decided to try DP4 because all the hype about copying OneUI was making me interested. I loved OneUI on all my Samsung devices. Missed it actually!
When I flashed DP4 I loved it. I checked this morning for Beta 1 OTA after seeing it was out. It downloaded and installed. No issues at all. I have not rooted or anything else.
The only thing I did diff was I was on DP4 before OB1. However, this really should not matter. The beta is expected to be flashed from 10.5.x AFAIK so that should not be the problem.
What's weird about this phone though, I am always seeing people reporting issues with signal after flashing. I dont get it. I have yet to loose signal. Not to say I have not had ****ty signal, thats just T-Mobile where I am at. But I can say with the latest T-MO update and the latest Beta 1 I can hit almost 100 megs down. Before these updates I was getting about 10 megs. ON all devices in my house on all carriers known to man. Occasionally I could get 11 megs down
pro_granade said:
I'm on DP4, should I back up my modem before updating?
Edit: It works perfectly for me on TMobile converted.
Click to expand...
Click to collapse
Yep, me too! I was pretty happy to have good speeds, and the latest OOS.
Ok I'm on 10.5.20 do I need to downgrade first or can I flash straight to global 10.5.12
had this device all of a week (barely), seemed to work great out of the box, have left it stock intentionally.
take the April security update, reboot.
Have completely lost pinch zoom / multitouch and it seems as though the screen's settings, software or combination are completely misaligned / out of whack regarding touch input.
It's the kind of behavior you get when you have a droplet on your screen and the phone screen is getting erratic input... like it's compromised or fragmented somehow.... I've increased sensitivity which made the phone more usable, but I can barely use the bottom row of my home screeen. If I switch to left hand and try my L thumb, it better detects the input (if I aim WAY LOW). Almost like the calibration for the screen touch has been completely FUBAR.
Hoping custom software and lack of OTA updates fixes this? Has this community seen this issue and are custom ROMs a way out of the mess, or is this a hardware issue that absolutely requires the device to be returned and replaced? Seems odd the change happened with no physical change to the phone.
Same issue here when updating. Complete factory reset fixed mine
@beflythis hey did you figure the fix out? I have a similar issue. Factory reset didn't help me
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
anshuuu03 said:
Update: Downgrading the phone to Android 10 fixes everything. I. DONT. KNOW. HOW. THO
Click to expand...
Click to collapse
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
This is definetly an issue with what seems to be the software, not sure exactly what is wrong though (I dont know too much about kernel driver code),
anshuuu03 said:
Got a screen replacement from B2X and updated it to Android 13 subsequently. Since the update or repair, multi-touch has been ruined, cannot pinch-to-zoom, and the keyboard is very buggy since screen responsiveness seems to have been compromised. I flashed android 12 on it again using flash.android but the issue still persisted. I am unable to figure out a solution. Is it a hardware or software issue? Once in a while after a restart the pinch-to-zoom will work and keyboard will work fine before it gets ruined again. Please tell me what to do
Click to expand...
Click to collapse
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Do let me know if it works. It would be a life saver
fbievan said:
Exacty same issue, got a screen replacement from UbreakiFix, wonder if it might be a batch of screens that are bad on specific kernel drivers? I honestly dont know.
Click to expand...
Click to collapse
I think downgrading to Android 10 has worked for almost everyone facing this problem
vovapolischuk said:
@anshuuu03 so after downgrading the phone to Android 10, can you update it to Android 12 back? Or should you always use Android 10 now to have sensors working correctly?
Click to expand...
Click to collapse
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
fbievan said:
Same thing for me created a post just about this: https://forum.xda-developers.com/t/wanted-to-get-a-survery-multitouch-on-google-pixel-4a.4452169/ I think this might be releated in the different touch drivers in android 10 kernel and the android 11 kernel and up kernel. I was going to try and fix this by bringing the kernel touchscreen drivers from android 10 and just pasting them into a newer kernel and hoping that works. But have been really busy.
Click to expand...
Click to collapse
Now that i know that im now going crazy, and atleast one other person has very very similar story to mine, there needs to be a proper fix. I do know that android 10 and android 11 do have different touchscreen drivers. Downgrading then upgrading back wont work, atleast to my knowledge. I've done plenty of looking, and just don't know whats wrong. If any kernel devs that know their way around touchscreen drivers, and pixel 4as. Would be a life saver. But I have little idea of whats actaully going wrong.
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Yep, downgrading again to Android 10 alllows multittouch to work
anshuuu03 said:
I haven't tried doing that but I guess I'll just wait for other people to come up with a better solution since I have none
Click to expand...
Click to collapse
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
fbievan said:
Update: I actually got it working on Android 12L. So, I downgraded to Android 10, from googles flash tool. Then upgraded one by one. And for some reason that seemingly worked. Can u confirm?
Click to expand...
Click to collapse
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
fbievan said:
I flashed from android 10 to 11 t0 12 to 12L. Didnt try 13 because i use lineageOS. Also another note is that i did flash a build of the holy dragon kernel on Android 10. But that should influence it.
Click to expand...
Click to collapse
Make sure to test, test, and test
anshuuu03 said:
So you went flashed Android 10 > Android 11 > Android 12 using the flash.android tool or did you use the update drops that appear on phone? Also, did you trying going all the way upto Android 13?
Click to expand...
Click to collapse
Can I ask: has that worked for you?
fbievan said:
Can I ask: has that worked for you?
Click to expand...
Click to collapse
I think I will try and do the 10 > 11 > 12 > 13 in a few days. I am stuck with some work and cannot afford to keep resetting my phone atm. But I will update here whatever is the update on that