Database Info

FreedomPop Motorola Photon Q 4G LTE xt897c, want help with Cyanogenmod

Hi xdadevelopers,
I ordered a Motorola Photon Q 4G LTE (xt897c) phone from FreedomPop for $25 and 28 days later it has arrived. My experience with FreedomPop has been decidedly mixed. Lots of hassle from customer service combined with a product that is sometimes very useful and always cheap. (Unless you use over 2GB of data per month) The phone itself seems very adequate for an excellent price. I would like your assistance in putting Cyanogenmod or another appropriate ROM on it.
Here's where I am,
The phone appears to have been rooted out of the box according to "Root Checker Basic" from Google Play
I installed "Superuser" from Google Play and that seems to work correctly
Busybox seems to be present already according to "Online Nandroid" from Google Play
I have created a TWRP Backup using Online Nandroid without modifying the recovery
The phone currently has Android 4.1.2
Where I want to be
I want to install a custom recovery, preferably one I can make backups from
I want to update to a more recent version of Android such as the stable one found here DUCK RULES cyanogenmod bot org /?device=xt897c or another version where everything just works
Notes. I have ADB and Fastboot installed from "Android Studio". I have an appropriate USB cable. I do not have a microsdhc card right now. It appears "Sandisk 64GB Extreme Micro SD (SDXC) Card + Adapter 60MB/s Class 10 U3 UHS-1" at DUCK RULES amazon bot com /gp/product/B00N98QLRQ is a good choice for a good price. I have this on order and should have it within the week.
I understand this phone has a locked bootloader. The "Messaging" app from FreedomPop available in Google Play seems to control messaging and the phone dialer. I went to the official Motorola Bootloader unlock page DUCK RULES motorola-global-portal bot custhelp bot com /cc/cas/sso/redirect/standalone%2Fbootloader%2Funlock-your-device-b I booted into recover with Power and volume up and volume down held, selected fastboot, connected to the computer , ran fastboot, as described, got the code, put the code in the webpage as described, and got a blank page. This happened 2x, with no emails form Motorola. I tried a third time 6 hours later, and it loaded a page with more instructions and I had the bootloader unlock code in my email instantly (There were no preceding messages, they didn't go to spam or somewhere else). I have installed TWRP Manager by Jmz software from Google Play. The standard reboot method doesn't work I changed the settings to "Reboot using an alternate method". I attempted to the TWRP recovery with the "Install TWRP". One must select their device and the closest thing to mine was "Motorola Photon 4G" codename "sunfire". This didn't appear to be it exactly but there wasn't a better choice. The next line down says "custom recovery not installed or detected". Then I selected the recovery version to install "2.6.3.0" "openrecovery-twrp-2.6.3.0-sunfire.img appeared the most recent, then I attempted to "Install Recovery" The phone downloaded the image, and said "Ensure the partition listed below is the correct one for your device..." "/dev/block/mmcblk0p10" how do I know if that's correct or not? I said yes to the question and went ahead, the phone rebooted to an Android on it's side with a yellow triangular sign with an exclamation point above it. Thirty seconds later the phone rebooted normally and everything worked no custom recovery was flashed.
Also thanks to the xdadevelopers community for your past and future efforts. I threw in my lot with Android when the neXus One launched after watching the keynote, buying it full price and paying extra for next day air shipping. I stayed stock despite the cool stuff being done by the development community until Google fell behind in updates. Then I started with CM6 and later went to CM7. That was wonderful software, thanks everyone who was involved in that. Unfortunately way late in the life of my phone I was homeless and got robbed for it. I got a used HTC HD7 Windows Phone for free from a friend. It was great for movies and music with a great screen and touch sensor but it was very early in the life of the new Windows Phone and there wasn't a lot of quality software being developed. That, and it just wasn't Android, and I longed for freedom. The integrated Web browser IE 9 variant sucked, and T-mobile denied me the final Windows Phone 7 update. The phone has gotten less and less useful as time went by though it always sucked for web browsing. This fall I got a One Plus One, it made a wonderful Wifi phablet, but when I tried to use it as a phone I found the radio was severely deficient in range, possibly due to defective manufacture as it got better range in colder weather. I had to initiate a chargeback with my credit card company to get support to talk to me and then ultimately get a refund. That's how I got where I am now and this is the first time I've needed to register for an account here. Thanks again xdadevelopers.
What is the best way to proceed? Semi detailed logical instructions please, as while I am intelligent and not a noob, I have been out of the game since CM7
Code:
.. ("`-''-/").___..--''"`-._
.. `6_ 6 ) `-. ( ).`-.__.`)
.. (_Y_.)' ._ ) `._ `. ``-..-'
.. _..`--'_..-_/ /--'_.' ,'
.. (il),-'' (li),' ((!.-'

Holy wall of text. This seems to be the crux:
Aslan_ said:
I have installed TWRP Manager by Jmz software from Google Play. The standard reboot method doesn't work I changed the settings to "Reboot using an alternate method". I attempted to the TWRP recovery with the "Install TWRP". One must select their device and the closest thing to mine was "Motorola Photon 4G" codename "sunfire". This didn't appear to be it exactly but there wasn't a better choice. The next line down says "custom recovery not installed or detected". Then I selected the recovery version to install "2.6.3.0" "openrecovery-twrp-2.6.3.0-sunfire.img appeared the most recent, then I attempted to "Install Recovery" The phone downloaded the image, and said "Ensure the partition listed below is the correct one for your device..." "/dev/block/mmcblk0p10" how do I know if that's correct or not? I said yes to the question and went ahead, the phone rebooted to an Android on it's side with a yellow triangular sign with an exclamation point above it. Thirty seconds later the phone rebooted normally and everything worked no custom recovery was flashed.
Click to expand...
Click to collapse
Why would you flash something that is OBVIOUSLY not for your device!? I sincerely hope it did nothing because you could do some permanent damage to your device by flashing stuff that's not made for it.
Did you bother looking for any recovery threads? Say my TWRP thread?
I recommend 2.7.1.2 in that thread, which is fine for CM11. If you want CM12, grab 2.8.5.0 in that thread.
Flash it per my directions using fastboot in my TWRP thread.

Got it thanks, now which rom?
Thank you very much arrrghhh. First off I sucessfully flashed TWRP 2.7.1.2. I did see the "[recovery] TWRP 2.7.1.2" thread, but it was from 2012 and it's 2015 now, plus it was 25 pages. Now I do see that the initial post was last edited 23rd July 2014, so that's better, but that's still over six months ago, so I'd have asked the question anyway having seen that. Several things to note, GooManager has been retired since the new cdn for goo.im was implemented, so that should be removed from the post. I like apps, they make me feel like there's less risk in my actions, though after some poking around I see it's probably the opposite. People are doing so much more low level stuff in apps compared to CM7 it's amazing.
arrrghhh said:
I recommend 2.7.1.2 in that thread, which is fine for CM11. If you want CM12, grab 2.8.5.0 in that thread.
Click to expand...
Click to collapse
It would be nice to see that info in the 2.7.1.2 thread. that the newer version is recommended for CM12 and where to get it, that would show you're on top of the latest changes not to mention make the thread even more useful. Perhaps include the reason for stopping at 2.7.1.2, the SELinux split. Seeing a new version that works always makes me want to get the newer version, but in this case there's a good reason not too.
I'm always hated vague it's broken posts that don't adequately describe the problem, the hardware used and the environment, so I head in the opposite direction with mine.
Next question is which rom should I choose? I want something stable and secure with everything or just about everything working. I like Cyanogen Mod, but I'm open to other things. As new as I can get, but stable. I thought I needed something from download bod cyanogenmod bot org /?device=xt897c , but now looking around it looks like I might be able to use other sources like download bot cyanogenmod bot org /?device=xt897 I'm not sure though. Again I have the Motorola Photon Q 4G LTE which is CDMA, from FreedomPop running on the Sprint Network.
Code:
.. ("`-''-/").___..--''"`-._
.. `6_ 6 ) `-. ( ).`-.__.`)
.. (_Y_.)' ._ ) `._ `. ``-..-'
.. _..`--'_..-_/ /--'_.' ,'
.. (il),-'' (li),' ((!.-'

Aslan_ said:
Thank you very much arrrghhh. First off I sucessfully flashed TWRP 2.7.1.2. I did see the "[recovery] TWRP 2.7.1.2" thread, but it was from 2012 and it's 2015 now, plus it was 25 pages. Now I do see that the initial post was last edited 23rd July 2014, so that's better, but that's still over six months ago, so I'd have asked the question anyway having seen that. Several things to note, GooManager has been retired since the new cdn for goo.im was implemented, so that should be removed from the post.
Click to expand...
Click to collapse
I no longer use this as my primary device, so my threads are basically stagnant. fastboot always works, where apps come and go... I'll try to find some time to adjust the post.
Aslan_ said:
It would be nice to see that info in the 2.7.1.2 thread. that the newer version is recommended for CM12 and where to get it, that would show you're on top of the latest changes not to mention make the thread even more useful. Perhaps include the reason for stopping at 2.7.1.2, the SELinux split. Seeing a new version that works always makes me want to get the newer version, but in this case there's a good reason not too.
Click to expand...
Click to collapse
Reason for stopping at 2.7.1.2 was they implemented MTP in 2.8.x, and I could never get it working right for both Win & Lin. I spose my bar was too high and I should've just released it, but I hate releasing half working stuff. It was a new feature that didn't work right.
Again, this is no longer my primary device so I'm not working on it very much at all. I have to pry the thing from my roommate's hands to even play with it, I haven't flashed CM12 yet (because it's no longer my device really).
I'd like to update the official TWRP, but in the meantime the CM maintainer has taken care of updating it so F2FS can be utilized.
Aslan_ said:
Next question is which rom should I choose? I want something stable and secure with everything or just about everything working. I like Cyanogen Mod, but I'm open to other things. As new as I can get, but stable. I thought I needed something from download bod cyanogenmod bot org /?device=xt897c , but now looking around it looks like I might be able to use other sources like download bot cyanogenmod bot org /?device=xt897 I'm not sure though. Again I have the Motorola Photon Q 4G LTE which is CDMA, from FreedomPop running on the Sprint Network.
Click to expand...
Click to collapse
Well obviously some of that does go down to choice - if you want CM, it is a little confusing. The device started out in CM10 as its own device, xt897 for GSM xt897c for CDMA. Then in CM11 they merged the devices into moto_msm8960. Of course they had to split again when the new bootloaders were released for the other moto_msm8960's (Razr HD, Atrix HD, etc) and moto_msm8960_jbbl was kind of a stopgap device at the end of CM11. Again, reading is your friend here although I realize all of that history is hard to glean. At least read the OP of the CM thread:
kabaldan said:
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
Click to expand...
Click to collapse
Good luck. The device is now semi-unified (GSM & CDMA), as xt897.

Aslan_ said:
[*]I have created a TWRP Backup using Online Nandroid without modifying the recovery
Click to expand...
Click to collapse
Would you mind terribly to share this? My device shipped with a Sprint branded ROM and I'd like a proper backup.

I flashed CM 12.1 and lost data (3g/LTE) connection
I tried to flash FreedomPOP APN fix but it did not help
Anyone knows how to fix this?
How do I update PRL/Profile on CM 12.1?

turbozapekanka said:
I flashed CM 12.1 and lost data (3g/LTE) connection
I tried to flash FreedomPOP APN fix but it did not help
Anyone knows how to fix this?
How do I update PRL/Profile on CM 12.1?
Click to expand...
Click to collapse
You don't update PRL/Profile in CM, you do that on the stock ROM. Make sure EVERYTHING works on stock before flashing CM.

I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?

turbozapekanka said:
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
Click to expand...
Click to collapse
Correct.

turbozapekanka said:
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
Click to expand...
Click to collapse
Can you share this "another APN fix"?

already shared here http://forum.xda-developers.com/showpost.php?p=60153295&postcount=18

Anyone still have issues? I was running a June Nightly and it was working somewhat. It would randomly lose connection and I would have to flash the APN.zip. It happened again a few days ago and I decided to go up to 722 Nightly and now I haven't been able to connect. When I go to APNs the list is empty and even if I manually add one it does not seem to stick. The APN zip doesn't help either. The phone is connected but shows an exclamation mark next to the signal and I have no data.
Sort of solved my own problem
Flashed back to stock Spring using RSD lite and a modified XML that didn't flash the system.img since it kept giving me errors. Found a stock TWRP dump on the forums and flashed that. Updated PRL and Profile, reflahsed back to CM11 Snapshot and flashed the 2015 FreedomPOP APN fix. Working for 1 day now.

XT1900-1 November security patch link request

Does anyone have a link to the new Nov security patch that came through last night for Fi?
Even with uninstalling Magisk, my phone doesn't want to install the update, so i'll just flash manually with fastboot.
I've checked https://mirrors.lolinet.com/firmware/moto/payton/official/FI/ but haven't seen the Nov firmware yet.
Thanks in advance,

You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.

NeoandGeo said:
You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.
Click to expand...
Click to collapse
Same situation here as Enemy Lines, but to be clear N&G, the only way updating this security patch is happening is with a factory reset, correct? Either one right now to install the OTA, or flashing the full updated firmware once it's on Lolinet which means a reset as well. According to Magisk, it should handle this with no problem. But apparently can't in this case.

lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.

I just went ahead and reflashed the Oct rom (minus the userdata delete), let the Nov update install, then repatched for magisk.
I must have changed something in the system partition and didn't realize it ?*

KrisM22 said:
lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.
Click to expand...
Click to collapse
Didn't know that, but suspected that was the case. Thanks for confirming. Guess I'll just full flash it when it hits Lolinet.

If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like. I will post this as a new thread.

Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.

SilverPosition said:
Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.
Click to expand...
Click to collapse
LOL I have heard that complaint before and I know of no way to stop the notification. Go for it!!!

I'm going to give Enemy's October approach a try. It's all tediously [un]necessary, I suppose. Anyway, thanks for everyone weighing in. Always useful stuff here.

That should work with no problem. and no waiting!
EDIT - I found when I was doing that a lot, I used Nova launcher as it would save apps and desktop and made setup after flash much faster.

If you are just looking to get rid of the update notification you can use Titanium Backup or similar to freeze the 'Motorola Update Services' process.

Thanks Kris and Neo. Nova launcher certainly helps and I appreciate the tip with Titanium Backup and Motorola Update.
That said, here's this for anyone interested:
Like Enemy Lines I went to Lolinet and downloaded the October firmware. I used @munchy_cool’s useful firmware flash guide because he’s got the right Flash-All.sh or .bat scripts in his links. (Link below.) Before flashing I opened the Flash-All.sh and deleted the following command: ./fastboot erase userdata
That preserved my stuff which I’d have lost in a straight flash or factory reset. I downloaded the November patch, updated, reinstalled TWRP and Magisk.
Mac people, once you’ve opened terminal, you may have to activate the Flash-All.sh script with the following command and your password: sudo chmod +x flash-all.sh
If you’re unsure about any of this, read Munchy_Cool’s guide and watch the included vid.
https://forum.xda-developers.com/mo...-to-flash-official-factory-t3808348?nocache=1

No idea why this posted twice.

Thanks!

The stock firmware repository updated a few days ago, new date showing for last activity. No new uploads as of yet, but I believe the updated date precedes the actual firmware being available.

39-6-2 for fi - yeah that's the "Nov 1" one I ota'ed on 11-27, and 11-27 is the date of the ota. So it takes about 4 weeks for us to get it and another 3 weeks for lolinet to post it. So, yeah, if you're in a rush, grab the latest and then let it ota. - at least on retus ATT prepaid...

Nokia 8 Multiple Stock Boot Images

Since people have trouble getting the boot images, here is my GoogleDrive folder containing stock boot images for Nokia 8 TA-1004 (NB1). Versions uploaded as follows:
2018 patches: October, November, December
2019 patches: January, February, March, April, May, Juni, July, August, September, October
2020 patches: January, April, July
You can root the images via Magisk manager and then flash the rooted versions as needed, or flash them directly to restore stock.
GoogleDrive link:
https://drive.google.com/drive/folders/1S5LkbSWECQN2GzKbGOSLZwSAM8238DXb

Palaryel said:
Since people have trouble getting the boot images, here is my GoogleDrive folder containing stock boot images for Nokia 8 TA-1004 (NB1). Versions uploaded as follows:
2018 patches: October, November, December
2019 patches: January, February, March, April, May, Juni, July, August, September, October
2020 patches: January, April, July
You can root the images via Magisk manager and then flash the rooted versions as needed, or flash them directly to restore stock.
GoogleDrive link:
https://drive.google.com/drive/folders/1S5LkbSWECQN2GzKbGOSLZwSAM8238DXb
Click to expand...
Click to collapse
Thank you kindly. :good:
Should I uninstall magisk and flash both slot_a and b with a stock img or is it enough with a or b?

iMaterial said:
Thank you kindly. :good:
Should I uninstall magisk and flash both slot_a and b with a stock img or is it enough with a or b?
Click to expand...
Click to collapse
Depends on what you want to do exactly. If you purely wanna go stock again, check your current active slot (fastboot getvar current-slot), reflash it to the proper version and then flash the other slot with a stock image thats one version lower than the current slot (as each OTA update does install to the opposite slot and swaps active slots on reboot).
If you want to be able to receive OTA updates it still might fail (generic error "Installation Problem") depending on what you did with root. If that is the case you'll have to reflash completely via NOST (but in most cases you can do so without erasing user data, hence keeping your apps/settings).

Palaryel said:
Depends on what you want to do exactly. If you purely wanna go stock again, check your current active slot (fastboot getvar current-slot), reflash it to the proper version and then flash the other slot with a stock image thats one version lower than the current slot (as each OTA update does install to the opposite slot and swaps active slots on reboot).
Click to expand...
Click to collapse
Ahh ok, so it switches slot for updates, so it has redundancy if the new boot doesn't work. Makes a lot of sense.
I flashed slot a with the current and the b with the one before, but I'm getting "installation problem" when trying for the july SP OTA.

iMaterial said:
Ahh ok, so it switches slot for updates, so it has redundancy if the new boot doesn't work. Makes a lot of sense.
I flashed slot a with the current and the b with the one before, but I'm getting "installation problem" when trying for the july SP OTA.
Click to expand...
Click to collapse
Something you did as root screwed up the system partition (using Adaway withotu systemless hosts enabled in Magisk will do that for example).
Your only option now is to actually reflash everything with NOST (if you want to keep user data uncheck the "Erase user data" box before flashing). After the flash your system should update without any issues (will update 3-4 times, takes a while). In case you reflash like this and it doesn't want to update, the only option is to reflash again while deleting all user data, apply all updates and the re-root.
NOST download:
Code:
https://tmsp.io/fs/xda/nb1/tools/nost/NOST-v0.6.exe
Stock image (NB1-5150-0-00WW-B05):
Code:
https://tmsp.io/fs/xda/nb1/firmware/NB1-5150-0-00WW-B05.qlz

Palaryel said:
Something you did as root screwed up the system partition (using Adaway withotu systemless hosts enabled in Magisk will do that for example).
Click to expand...
Click to collapse
So basically, if I want to keep getting the OTAs, I can do TWRP on one slot, but I shouldn't ROOT? Hmmpf, I wish we had LaOS.

iMaterial said:
So basically, if I want to keep getting the OTAs, I can do TWRP on one slot, but I shouldn't ROOT? Hmmpf, I wish we had LaOS.
Click to expand...
Click to collapse
Actually the rooting process itself isn't whats hindering the OTAs (as long as you restore the original boot images before the OTA). Its what you do with root.
Since I only use 2 apps which require root (Adaway and Titanium Backup) I found out that what has disabled me to use OTAs before was Adaway modifying the hosts file (which as I've said before you can avoid by enabling systemless hosts in Magisk - after I started using that option getting OTA updates was without problems). Having TWRP will require you to manually reflash it every time before installing an OTA (not really a big issue considering the phone is getting an OTA once every 3 months now).
Honestly HMD did quite some **** with this phone by not updating it to support Treble (considering the Hardware specs the phone is quite usable even today). I'm considering getting a Pixel 4a (or 5) once its available in the EU, I'm getting sick of HMDs carelessness.

Palaryel said:
Actually the rooting process itself isn't whats hindering the OTAs (as long as you restore the original boot images before the OTA). Its what you do with root.
Since I only use 2 apps which require root (Adaway and Titanium Backup) I found out that what has disabled me to use OTAs before was Adaway modifying the hosts file (which as I've said before you can avoid by enabling systemless hosts in Magisk - after I started using that option getting OTA updates was without problems). Having TWRP will require you to manually reflash it every time before installing an OTA (not really a big issue considering the phone is getting an OTA once every 3 months now).
Honestly HMD did quite some **** with this phone by not updating it to support Treble (considering the Hardware specs the phone is quite usable even today). I'm considering getting a Pixel 4a (or 5) once its available in the EU, I'm getting sick of HMDs carelessness.
Click to expand...
Click to collapse
Ach so! Leider! Yeah the phone is smooth as a rocket and I got it new in a box for €149 and I hate BIG clunky phones and not having 16:9 / 16:10 screen so. Flashing TWRP a few times a year wouldn't be a problem and I don't use Adaway, but greenify and file explorer Root. I do most of my backups via TWRP. Bleh! Es ist sehr wahnsinnig!

iMaterial said:
Ach so! Leider! Yeah the phone is smooth as a rocket and I got it new in a box for €149 and I hate BIG clunky phones and not having 16:9 / 16:10 screen so. Flashing TWRP a few times a year wouldn't be a problem and I don't use Adaway, but greenify and file explorer Root. I do most of my backups via TWRP. Bleh! Es ist sehr wahnsinnig!
Click to expand...
Click to collapse
Actually I forgot about File Explorer, which I also use in root mode. Also nothing Greenify does should actually compromise the system partition in away that prevents updates. But like I said, with this phone its a bit tricky, I've never been able to pinpoint the exact issue thats doing so. For OTAs to work seamlessly the phone has to be reverted to stock (unroot, stock recovery, stock hosts, unchanged system partition, etc), but apparently theres something more to it since at times even after flashing everything back to stock the updates would fail (in which case only a full revert to stock, including user data fixed the issue).
Also, what you wrote about big, clunky phones: thats exactly the reason I'm thinking about Pixel 4a/5, theyre both under 6'', hence relatively small and perfectly usable with one hand. Nowadays its become the trend to go 6,5+'' for flagships which I'm not really fond of.

Does somebody have that latest and last stock MR for October 2020 (00WW_5_16A) ?

Someone please help me.
"Fastboot devices"
(My device show up)
But after that, I can't enter any command.
It says Waiting for device.
My device show up in fastboot device as well as in Manage Devices in settings as Fastboot.
My Sp is October 2020.
I root my phone last July SP, bit lost root access after update.

Can somebody post the link to the latest Full OTA October 2020? Thanks

How to check your current security patch level. I want to root my phone, bootloader already unlock
Please someone help me
My current bulid no is
00WW_5_15G
Which image i use in above list

Need help updating metro version moto one 5g ace from 10 to 11. Rooted

Title says is all, well not all. This would literally be the first update the phone got, I rooted day one out the box and keep the same firmware for flashing when switching roms, now that root is detected with a game, yes my root is depended on access to certain things, so I'm constantly rooting doing what is needed then uninstalling magisk. Very tiring. I wanted to get to Android 11, hoping no data loss, rooted if able and twrp if available for Android 11 on this one. Any pointers in the right direction would be helpful, thanks in advanced

Without taking the OTA update, I know of nothing that will get you to 11 without wiping your data. (That is why backups are good.) lolinet has 11 firmware. TWRP can be had on Telegram. Magisk is available on the github.

RETIEF said:
Without taking the OTA update, I know of nothing that will get you to 11 without wiping your data. (That is why backups are good.) lolinet has 11 firmware. TWRP can be had on Telegram. Magisk is available on the github.
Click to expand...
Click to collapse
I have all the files needed, even without root ota says you up to date security patch January 2021 lol. I heard somewhere to edit the fstab to not auto reboot, kinda like Odin with Samsung's. Then flash thru twrp, thinking that would delete twrp, but hey is 11 really better?

I don't think you can flash a stock ROM with TWRP. No, I don't think 11 is better. That is just my opinion.

RETIEF said:
I don't think you can flash a stock ROM with TWRP. No, I don't think 11 is better. That is just my opinion.
Click to expand...
Click to collapse
I honestly hate everything after 5 lol. 10 is frustrating. 11 has rw I'm doing it, hell 5g speeds 200 apps, 10 minutes lol and for splifs and giggles, imma try thru twrp, replacing recovery.img with twrp, vbmeta blanked then go into service file and flanh file and change the md5, what could go wrong?

Let us know how that worked out I have Moto one 5ga's with Comcast, mine is also rooted.

Question issues with updates

Hi, i have a Pixel 7 pro (no carrier, eu, stock, locked bootloader) and am experiencing the following:
until yesterday i was running:
security update: november
play system update: october
os: october
i tried with the pixel repair tool to no avail. so, yesterday i applied for the beta... installed, rebooted (many times) and... still stuck with the stable from october. i then downloaded the official ota and applied it... now i have
security update: december
play system update: october
os: december
now, why the play system won't update? also, the privacy and security settings are still separated... for what is worth, the free VPN has already been active for a few days.
is my OS broken? should i try with sideloading the update again? i'm not in the mood for a reset and i have many apps (banking too) which would be a hassle to config again.

ujh said:
Hi, i have a Pixel 7 pro (no carrier, eu, stock, locked bootloader) and am experiencing the following:
until yesterday i was running:
security update: november
play system update: october
os: october
i tried with the pixel repair tool to no avail. so, yesterday i applied for the beta... installed, rebooted (many times) and... still stuck with the stable from october. i then downloaded the official ota and applied it... now i have
security update: december
play system update: october
os: december
now, why the play system won't update? also, the privacy and security settings are still separated... for what is worth, the free VPN has already been active for a few days.
is my OS broken? should i try with sideloading the update again? i'm not in the mood for a reset and i have many apps (banking too) which would be a hassle to config again.
Click to expand...
Click to collapse
I updated yesterday to Dec.Release, I I'm with this. To be honest, don't know if is as expected

well, fair enough... it may be a slow rollout of single features...? -.-

ujh said:
Hi, i have a Pixel 7 pro (no carrier, eu, stock, locked bootloader) and am experiencing the following:
until yesterday i was running:
security update: november
play system update: october
os: october
i tried with the pixel repair tool to no avail. so, yesterday i applied for the beta... installed, rebooted (many times) and... still stuck with the stable from october. i then downloaded the official ota and applied it... now i have
security update: december
play system update: october
os: december
now, why the play system won't update? also, the privacy and security settings are still separated... for what is worth, the free VPN has already been active for a few days.
is my OS broken? should i try with sideloading the update again? i'm not in the mood for a reset and i have many apps (banking too) which would be a hassle to config again.
Click to expand...
Click to collapse
Android Pixel updates get rolled out in phases, meaning it's not available for everyone at the same time. Maybe you need to wait an hour, maybe a day, maybe a week.
If you feel the need to immediately update at the earliest time possible, you should look into ADB flashing.

Morgrain said:
Android Pixel updates get rolled out in phases, meaning it's not available for everyone at the same time. Maybe you need to wait an hour, maybe a day, maybe a week.
If you feel the need to immediately update at the earliest time possible, you should look into ADB flashing.
Click to expand...
Click to collapse
That's true... But about the settings tabs not yet unified?

ujh said:
That's true... But about the settings tabs not yet unified?
Click to expand...
Click to collapse
I updated to december and also have not gotten that "feature", it's likely that it's a google sided switch/ App update that is necessary to change that, meaning it's not at all necessary to update the firmware of the phone factually, but Google still wants the "feature drop" as a sales argument, hence the big focus on the firmware updates, even though the actual features could easily be delivered as in-app updates.

yeah... i read somewhere else that that "feature" and others will be available with an upcoming update within this month... lol

ujh said:
That's true... But about the settings tabs not yet unified?
Click to expand...
Click to collapse
I think that's part of the PermissionController APK, which is part of the PermissionController Mainline module. So I think Google needs to update that Mainline module before we get it.
However, you should be able to toggle the flag on with this adb command...
adb shell cmd device_config put privacy safety_center_is_enabled true