Database Info

Update

Small 64.26 MB update coming in this morning.
Sent from my SAMSUNG-SM-G920A using Tapatalk

Android Police describes what the update brings here:
http://www.androidpolice.com/2015/07/02/att-galaxy-s5-receives-hefty-performance-and-security-related-update-while-lg-g3-gets-mcafee-factory-reset-protection/

While I'm not expecting much in the way of changes compared to 21l, if you are stock rooted on this ROM, could you please do the following in adb and upload the resulting image files?
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/sdcard/rpm.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/sdcard/tz.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
system may fail due to it's size, but if so, no worries.

This assumes rooting still works after the update....does it?

dkephart said:
This assumes rooting still works after the update....does it?
Click to expand...
Click to collapse
One click root still works with the latest update. Seems they removed VoLTE with this newest build. Not sure if anything else is different.

I just got 21q after weeks of asking why I never got 21l. VoLTE is still present and enabled in the hidden menu.
I can upload those partitions if it helps (assuming it hasn't been done already and that there's no reason not to). Mediafire, Mega, else -- what's good for free?

ae10u said:
I can upload those partitions if it helps (assuming it hasn't been done already and that there's no reason not to). Mediafire, Mega, else -- what's good for free?
Click to expand...
Click to collapse
Mega and AndroidFileHost appear to be popular options.

I was asleep at the keyboard earlier. (Uploading to my Drive now.. 1.47gb compressed) A free Mega account (unless I'm overreading it) would have afforded me 1 upload and 5 downloads of that and sorry everyone else.. And AFH I don't wanna be that guy exporting partitions to storage used by devs lol.. (but thank you)
Back at about 7pm EDT with a link.
edit: D85021q.7z Download md5: a2b7eaaa59872d5f97cf5a82cd04b6e3 now on AFH, see below

ae10u said:
I was asleep at the keyboard earlier. (Uploading to my Drive now.. 1.47gb compressed) A free Mega account (unless I'm overreading it) would have afforded me 1 upload and 5 downloads of that and sorry everyone else.. And AFH I don't wanna be that guy exporting partitions to storage used by devs lol.. (but thank you)
Back at about 7pm EDT with a link.
edit: D85021q.7z Download md5: a2b7eaaa59872d5f97cf5a82cd04b6e3
Click to expand...
Click to collapse
Thanks for that! Using AFH is fine, since devs need these partitions to get started anyway! It's a good community service!

TWRP
ae10u said:
I was asleep at the keyboard earlier. (Uploading to my Drive now.. 1.47gb compressed) A free Mega account (unless I'm overreading it) would have afforded me 1 upload and 5 downloads of that and sorry everyone else.. And AFH I don't wanna be that guy exporting partitions to storage used by devs lol.. (but thank you)
Back at about 7pm EDT with a link.
edit: D85021q.7z Download md5: a2b7eaaa59872d5f97cf5a82cd04b6e3
Click to expand...
Click to collapse
so am I able to just flash this in TWRP, or no?

ae10u said:
I just got 21q after weeks of asking why I never got 21l. VoLTE is still present and enabled in the hidden menu.
I can upload those partitions if it helps (assuming it hasn't been done already and that there's no reason not to). Mediafire, Mega, else -- what's good for free?
Click to expand...
Click to collapse
Where did you find it? I checked the hidden menu and the VoLTE options disappeared for me.

Hidden menu, 8th from the bottom. From a fresh 10d TOT, mine OTA's to 20f (skipping 10f) and then to 21q (skipping 21l). Needless to say, I have reset many times.
A factory reset would resolve any stale cache, recompiling the IMS (volte) framework along with everything else which couldn't hurt (assuming it's there).. And failing that, there is the option to start all over again and OTA with your fingers crossed it's there next time.
Standard behavior appears to be to open a submenu with an on/off ticker, where 20f and earlier always returned "ims volte package doesn't exist".

shxrm_ said:
so am I able to just flash this in TWRP, or no?
Click to expand...
Click to collapse
No. This is a partition package. It's really only for developers at this point.
I could cook up a TWRP-flashable ROM that flashes directly from these images, but I've previously found it hit-or-miss in getting system.img to extract properly.

vonmolk said:
Where did you find it? I checked the hidden menu and the VoLTE options disappeared for me.
Click to expand...
Click to collapse
I knew VoLTE was still there when I made a call last night and looked at my phone signal indicator a couple times after being shocked at the voice clarity I was hearing. Pretty noticeable difference if the other party's phone also uses VoLTE. This was my first experience with the feature.

vonmolk said:
One click root still works with the latest update. Seems they removed VoLTE with this newest build. Not sure if anything else is different.
Click to expand...
Click to collapse
The one click root method still works for you? It doesn't work for me It'll always hang at 90%

Use the new root method.
Link OP says something along the lines of "new firmwares don't parse scripts correctly in download mode". It is not confirmed for D850, but another D850 thread linked to it and I rooted 21q successfully with it. Looks like the same commands as 1-click, just that you have to copy and paste them into an adb shell.

ae10u said:
Use the new root method.
Link OP says something along the lines of "new firmwares don't parse scripts correctly in download mode". It is not confirmed for D850, but another D850 thread linked to it and I rooted 21q successfully with it. Looks like the same commands as 1-click, just that you have to copy and paste them into an adb shell.
Click to expand...
Click to collapse
How is it working for you, but it continues to fail for me?

I am currently on 20f and rooted. I just checked for an update and it shows a 205.43mb update available. Is this the same update as the op stated just with more from updates I didn't get in between? Is this safe to try to install while still rooted?
Thanks.
Sent from my LG-D850 using XDA Free mobile app

CapnPez said:
I am currently on 20f and rooted. I just checked for an update and it shows a 205.43mb update available. Is this the same update as the op stated just with more from updates I didn't get in between? Is this safe to try to install while still rooted?
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://drive.google.com/a/wfu.edu/file/d/0B48raf5IsreMSUlneENrTi14eEE/edit?usp=docslist_api
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
If you're rooted it won't work. It'll tell you the update is not supported for rooted devices.

thatkindaguy said:
If you're rooted it won't work. It'll tell you the update is not supported for rooted devices.
Click to expand...
Click to collapse
Thanks. Is the update worth unrooting for? Is there much of a hassle to unroot, update, reroot?
Sent from my LG-D850 using XDA Free mobile app

How to install January 5th patch while using custom recovery and root on Google Pixel

Okay, I am sure a lot of you already know how to do this to your Pixel. Some of us do not, and I was one of them. I am the standard noob that just followed Youtube videos to unlock previous carrier locked phones. I am now enjoying this Google Pixel that is unlocked!
So if you are reading this thread, hopefully there isn't another one just like this (yes I looked).
To start off, if you are in here reading this, you have unlocked your bootloader and installed a custom recovery such as TWRP and rooted. Now you are seeing that you need to update your phone with the latest security patch. You try and you try and you can't do it. Even when you unroot it will still fail to update, or at least it did for me. Here I will explain what I went through and did to obtain the latest update. (Warning, you will loose root and custom recovery). THIS IS INTENDED FOR THE GOOGLE STORE PURCHASED PHONES
Lets get this started finally.....
Go into your developer options and enable usb debugging.
Download the newly released package file from google that has fastboot and ADB without needing android SDK.
DOWNLOAD or read about it HERE
Now you will need to download the Factory Image for you device
Find your correct device HERE
Make sure you choose the correct device and correct update, for me I downloaded the "7.1.1 (NMF26U, Jan 2017)" for my Pixel. Also a USA phone.
So now you have the adb fastboot binary package and your factory image. You will need to extract the platform-tools-latest-windows.zip and open the folder and you will see another folder, open it and now you will see a bunch of files. Now open another window and extract your factory image. Once it is done, open the folder until you see the files. Now copy these into the Platform tools folder in the directory with the fastboot.
Once this is done your folder should look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you will want to right click "flash-all" and click edit. It will open notepad and show the contents of the batch file. You can hit Ctrl+F and type in -w in the search and hit okay, or you can look for it without search (it is near the bottom). Once you find it, just delete the "-w" and save the file. Make sure to keep it as the batch file or this won't work.
Once this is done, in the folder that is shown above, click a blank area in the folder so no file is highlighted. Now hold shift and right click, it will come up with a dialog saying open command window here, click that.
Now we are going to reboot the phone into bootloader mode. In the command window, type everything that is underlined below
adb reboot bootloader
Now your phone should have booted into the bootloader screen or it should be asking for USB rights to use adb. If it asks for permission, hit okay and re run the code above and your phone should reboot.
Once you are in the bootloader screen you will need to do is run the flash-all.bat. It will load and go though some text on the CMD window it brings up. It will say some files are missing, which is fine. But if it fails it will tell you that it did. You can also tell by rebooting the phone or click "start" in the bootloader mode and then checking for OTA updates. It should say January 5th patch installed.
Now you can go through and install your custom recovery again and re root. Which takes no time at all and I am sure someone on here has posted before. If not, let me know and I can make a tutorial over it.
Note: I am very sorry for the bad layout and extended write up. First time ever doing this and I am hoping to help people. If there are any errors, let me know!

All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.

zelendel said:
All of this is already well known and documented. It is device molding 101
No one with 2 licks of common sense uses YouTube videos for something like this.
Click to expand...
Click to collapse
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself

exbtlegends said:
Haha well my apologies, I did state that I was a complete noob about all of this. I'm sure there are other noobs like myself
Click to expand...
Click to collapse
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.

jrat69 said:
I'm not a noob, but i'm a old fart, and we forget things, even simple things like this, I'm glad to have a simple reminder of how to do things. Thanks for the refresher.
Click to expand...
Click to collapse
Not a problem ?

I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.

32BitWhore said:
I know you say this is for the GPS version, but has anyone tried it on Verizon? I'm not sure if the firmware is the same on both phones, so I don't want to soft-brick by downloading the Google version if they're different. Same boat as you were, OTA fails even after unrooting.
Click to expand...
Click to collapse
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.

This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.

Good work. This is a very minute stuff of removing -w from the batch file. Very handy work.
Sent from my Pixel using Tapatalk

Do you need to reflash stock kernel before removing root/TWRP before flashing?

32BitWhore said:
Do you need to reflash stock kernel before removing root/TWRP before flashing?
Click to expand...
Click to collapse
Flashing the image overwrites anything you customized besides the regular user data and internal storage (with the -w removed). You don't have to remove or reflash anything else before following these instructions.

TCPDump said:
This is really complicated. ADB side load the OTA file, reinstall TWRP and root, done.
Click to expand...
Click to collapse
I couldn't side load the update.. TWRP would not load the side load feature.

I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?

km8j said:
I'm having an issue also: https://forum.xda-developers.com/pixel/help/sideload-ota-t3534926... Can we just unroot, take the OTA and then reroot?
Click to expand...
Click to collapse
Even when I un rooted mine. I was still failing to get the update.

If you made any changes the the system partition then it will fail and simply unrooting doesn't make the all the changes needed. So if OTA mean anything to you then I would suggest not messing with your device as there is Jo promise that after an OTA you will be able to root again tonight away

jesssiii said:
As long as you never re-lock your bootloader, the process is the same. There's no more separate Verizon images, just USA and international.
Click to expand...
Click to collapse
I know the past 2 were the same for google pixel and Verizon pixel but I wouldn't assume they are always going to be. I'm sure some of them will be specific at times whenever Verizon decides they wanna mess with them

FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.

SpoiledHeeb said:
FYI, I was able to sideload after updating TWRP to RC1, but now SuperSU 2.79 will install from within TWRP but when the phone restarts SuperSU is not installed... not sure if we have to wait until a new version of SuperSU is released.
Click to expand...
Click to collapse
You need SuperSU 2.79 RC3

[ROM][10.0][UNOFFICIAL] Nexus Stock for Xiaomi Mi Pad 4 [clover]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here's my first effort at migrating the Nexus Stock custom ROM to the Xiaomi Mi Pad 4. It's very much a work in progress, but builds on strong foundational work by @rcstar6696.
Notes:
The system is based on @rcstar6696's LineageOS 17.1 with the latest Stock variant from OpenGApps.
Boot logo and default wallpaper is from my Nexus series of custom ROMs for Android TV, and I'm using the Pixel boot animation with black background.
Google's Pixel Launcher has been tweaked to include standard tablet layouts and default icon placement. (See attached screenshots.)
The properties now correctly identify the device as a tablet, and so the Google Dialer and Messenger are no longer installed. I've also disabled the Emergency button, but SetupWizard still insists on reminding you to insert a SIM (sigh!).
Releases are archived to Android File Host here.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Downloads:
Nexus_Stock_LQ-20210327-clover.zip
Change Log:
20210328:
Latest stable Google apps from OpenGApps Stock variant (20210327) with fix for Google News.
20210322:
Updated custom Pixel Launcher to match icon layouts for Nexus 7 (and Nexus 10 with display scaling set to Small).
Updated to official TWRP v3.5.1 custom recovery.
Updated to lineage-17.1-20210213-UNOFFICIAL-clover.
Latest stable Google apps from OpenGApps Stock variant (20210311)
20201018:
Restored LineageOS Files (DocumentsUI), which is required by some apps for file management. Google Files is also still included.
Latest Google apps from OpenGApps Stock variant (20201017)
20201011:
Switched to the Xiaomi OEM camera app from GoogleCamera v4.4, which still had some compatibility issues.
Updated to lineage-17.1-20201011-UNOFFICIAL-clover.
Latest Google apps from OpenGApps Stock variant (20201010)
20200701:
Initial build based on lineage-17.1-20200512-UNOFFICIAL-clover.
Latest Google apps from OpenGApps Stock variant (20200630)
Instructions:
Hold Vol Up during restart to enter TWRP recovery
Tap Install, select your update (.zip file), and then swipe to install
Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @rcstar6696 for the LineageOS 17.1 build, so please show him some love here!

Reserved

In LineageOS 17.1 on mi pad 4 wifi, there is a little section for xiaomi and then a section on thermals, but when i change those, the cpu frequency does not change, nor the governor.
Is it the same on Nexus ROM ?

Can't install this. I get error 7 at flashing. I'm wrong? Is this for mi pad 4 wifi (non plus)? I wipe everything like always, i'm coming from carbon rom, i wanna try this, seems good, but....

blue whale said:
In LineageOS 17.1 on mi pad 4 wifi, there is a little section for xiaomi and then a section on thermals, but when i change those, the cpu frequency does not change, nor the governor.
Is it the same on Nexus ROM ?
Click to expand...
Click to collapse
That should be the same as for the underlying LineageOS 17.1 build, since I haven't touched that area at all.

25agosto said:
Can't install this. I get error 7 at flashing. I'm wrong? Is this for mi pad 4 wifi (non plus)? I wipe everything like always, i'm coming from carbon rom, i wanna try this, seems good, but....
Click to expand...
Click to collapse
The update script is looking for "ro.product.vendor.device=clover", which should be true on the latest LineageOS and Carbon. I am noticing now that the property is called "ro.vendor.product.device" on stock OEM, so I'll add that. I didn't pick up on the transposition last night, but I believe that "ro.vendor.product.device" is deprecated in API 28 and later.
Stand by for an update script update.

Magendanz said:
The update script is looking for "ro.product.vendor.device=clover", which should be true on the latest LineageOS, and Carbon. I am noticing now that the property is called "ro.vendor.product.device" on stock OEM, so I'll add that. I didn't pick up on the transposition last night, but I believe that "ro.vendor.product.device" is deprecated in API 28 and later.
Stand by for an update script update.
Click to expand...
Click to collapse
Nice! Can't wait to test!

25agosto said:
Nice! Can't wait to test!
Click to expand...
Click to collapse
Okay, the link above has been updated. Since the actual build hasn't changed, I made it a "rolling update"...which is a sneaky term we used at Microsoft for silent updates with no version change.
Also, make sure you're using the latest TWRP for clover because that's what I've used for testing. We're up to v3.4.0-0 now. Some older versions might not map partitions to /dev/block/by-name or correctly handle system-as-root.

This need to be tested. thanks!

Can not install
- Confirming target device...
ui_print(): Failed to parse the argument(s)
Updater error:7
already use twrp 3.4.0-0

gaoxieen said:
- Confirming target device...
ui_print(): Failed to parse the argument(s)
Click to expand...
Click to collapse
That's because the update script is unable to read the vendor build.prop, which it needs to confirm it's on the target hardware. Did you erase it, by any chance?

New problem
Magendanz said:
That's because the update script is unable to read the vendor build.prop, which it needs to confirm it's on the target hardware. Did you erase it, by any chance?
Click to expand...
Click to collapse
Thank you for your reply. I format the data and install again. I think this time the script read the .prop.
But it shows
Failed to unmount /system_root: No such volume
So I checked system_root and it is blank.

Very good ROM, thanks.
I cannot access the SD card, unable to proceed "Allow to access SD card", saying app not found.

gaoxieen said:
Thank you for your reply. I format the data and install again. I think this time the script read the .prop.
But it shows
Failed to unmount /system_root: No such volume
So I checked system_root and it is blank.
Click to expand...
Click to collapse
Try downloading now. I made a tweak to the update script that should address this issue.

Chrome and webview
gaoxieen said:
- Confirming target device...
ui_print(): Failed to parse the argument(s)
Updater error:7
already use twrp 3.4.0-0
Click to expand...
Click to collapse
I tried several Roms as a base before installing this one (lineage, MiUi 12, EU dev) and finally installing on top of the latest cDroid worked ?.
Great Rom ?
I've had a problem with all the Roms I've mentioned above, and this one, when I load eBay.co.uk on Chrome, it crashes after a few seconds, think it's something to do with loading up webview, anyone else had this?
Have tried turning location off, and also using Chrome beta...

Wow, I remember using your Beelink TV Box ROMs. I'd probably still be using a Beelink today if DRM hadn't ruined all of the China boxes.
Glad to see you here.

gorilla p said:
Wow, I remember using your Beelink TV Box ROMs. I'd probably still be using a Beelink today if DRM hadn't ruined all of the China boxes.
Glad to see you here.
Click to expand...
Click to collapse
Yeah, it really is a shame how WideVine L1 and Netflix whitelists crippled those Chinese TV boxes. I made the switch to tablets for the Samsung Galaxy Tab A 10.1 (2019) and hopefully will have a little better luck at keeping the budget Android tablet segment alive. Right now it's probably more neglected than the Android TV platform was.

Magendanz said:
Yeah, it really is a shame how WideVine L1 and Netflix whitelists crippled those Chinese TV boxes. I made the switch to tablets for the Samsung Galaxy Tab A 10.1 (2019) and hopefully will have a little better luck at keeping the budget Android tablet segment alive. Right now it's probably more neglected than the Android TV platform was.
Click to expand...
Click to collapse
Yeah after a lot of research, this tablet was arguably the best value available based on the hardware that you get for the money. I paid 168 for the WiFi version.
My only gripe was that immediately after, Xiaomi stopped supporting it. They released it and dropped it almost immediately. Luckily there has been decent custom ROM support to keep this thing alive.
For the TV boxes, I have both a MiBox 3S and an eMatic Jetstream 4K. I have been happy with the JetStream 4K. I just wish they would release something with better hardware, but not go overboard like the nVidia shield so it costs 180.
A L1 Netflix supported GT King would be perfect.

I don't suppose anybody has tried google family link and is working on this Rom before I try it?
many thanks

New release is posted:
Downloads:
Nexus_Stock_LQ-20201011-clover.zip
Change Log:
20201011:
Switched to the Xiaomi OEM camera app from GoogleCamera v4.4, which still had some compatibility issues.
Updated to lineage-17.1-20201011-UNOFFICIAL-clover.
Latest Google apps from OpenGApps Stock variant (20201010)

Current list of available ROMS for SUEZ? *Am I missing any??

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*TLDR version.
Good After Mornin/Evening,
Am I missing any roms from my collection?
*Long Version.
I'm writing an application in processing.org for my tablet. I have an FPS counter in it, and for whatever reason, I seem to get different results in different roms.
The version of the ROM for what I need it for really doesn't matter. I just need one that does what I need and I'll be good. Battery life seems to also be an issue with other releases too, not sure what that is about. I have experienced the later lineage 16x versions have issues with one of the cpu's not entering sleep state *or something to that account*
I am using another piece of software called *Automate by LamaLabs, free on the play store. It's a really cool app if you have not heard about it. It allows you to Automate things *Pun*
When my tablet is powered via USB, it auto unlocks, connects to a specific AP, launches my app.
When the tablet is unpowered via USB, it auto kills the app and does a soft power off.
Really I don't even need to touch the screen, its quite amazing.
With that said, Not sure if its my old tablet, I bought 5 off ebay, because they are all old, I can't tell if the batteries are just getting weak or the usage is high when in the soft off mode. I have lots of linux experience, and about the only thing I can think of is adb into it, then run top and see if anything is chewing up CPU... or if there are other methods.
Another option would be
USB adapter powered by bench top psu, and just run various roms, with a glance at the current usage.
Anyway, Thanks again,
**Infact it would be pretty cool to be able to try the last fireHD rom if there is an easy way to download the firmware and some how load it up with TWRP? I bet it's not as easy as I would think..

likwidchz said:
bet it's not as easy as I would think..
Click to expand...
Click to collapse
Thats easy, just grab one of this bin files, rename to zip and flash it with twrp.
[FIRMWARE / Update][Stock] Fire HD 10 - 7th Gen
Fire HD10 (7th Generation) OS 5.6.0.0 : https://fireos-tablet-src.s3.amazonaws.com/nachheflb20tca1zcilvlco11ae49hnab/update-kindle-40.5.9.5_user_595457320.bin Fire HD10 (7th Generation) OS 5.6.0.1...
forum.xda-developers.com
Then the OTA updater will download/install the latest one for you.
Maybe take a full TWRP backup infront of any stock rom flash, in case something gets wrong.

Sus_i said:
Thats easy, just grab one of this bin files, rename to zip and flash it with twrp.
[FIRMWARE / Update][Stock] Fire HD 10 - 7th Gen
Fire HD10 (7th Generation) OS 5.6.0.0 : https://fireos-tablet-src.s3.amazonaws.com/nachheflb20tca1zcilvlco11ae49hnab/update-kindle-40.5.9.5_user_595457320.bin Fire HD10 (7th Generation) OS 5.6.0.1...
forum.xda-developers.com
Then the OTA updater will download/install the latest one for you.
Maybe take a full TWRP backup infront of any stock rom flash, in case something gets wrong.
Click to expand...
Click to collapse
You serious on the bin file ordeal?
I rename the bin file to a zip and flash with TWRP. I have an unrooted oem OS but the ability to wipe it out with TWRP later? My gut says it's not that easy... I mean, its worth a try right? the worst that can happen is it will fail at flashing or just not boot.
Thank you,
Is there anyway I can download the latest bin without the OTA update? I think the OTA update will probably overwrite TWRP right?
Thanks again.

likwidchz said:
I rename the bin file to a zip and flash with TWRP.
Click to expand...
Click to collapse
Yes, thats the way we flash all roms...
likwidchz said:
I have an unrooted oem OS but the ability to wipe it out with TWRP later? My gut says it's not that easy... I mean, its worth a try right? the worst that can happen is it will fail at flashing or just not boot.
Click to expand...
Click to collapse
You have a tablet with an unlocked bootloader and TWRP.
Doesn't matter if your OS is rooted, because if you flash a new rom the old one gets wiped...
likwidchz said:
Is there anyway I can download the latest bin without the OTA update? I think the OTA update will probably overwrite TWRP right?
Click to expand...
Click to collapse
Yes, you can also search for updates in the stock rom settings while capturing the whole logcat via adb, then you can see the OTA URL in the logcat.
The OTA will not wipe TWRP, it will use TWRP to install the update and TWRP will protect itself / prohibits any flash to the recovery partition, so thats not a problem.
likwidchz said:
Thanks again.
Click to expand...
Click to collapse

Development [Discontinued][ROM][13.0][Unofficial][Bluejay][Lineage OS 20.0][Feb-13-2023]

Official support is now here! You can flash right over your old installation if you are coming from this ROM (no factory reset needed).
https://download.lineageos.org/bluejay
Lineage OS 20.0 - Unofficial - Pixel 6a
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​Hi all. I noticed that there isn't official Lineage OS support for our Pixel 6a, so I decided to build it until then (if it happens). Since it appears to be working correctly, I wanted to share it with anyone else who has an interest. I'm not changing anything about it (other than making the updater allow unofficial updates) and building straight from the Lineage OS sources. I'll attempt to build it roughly 1x per month, usually around the middle to allow for most security updates to take effect. I daily drive the ROM, so I'll try to only post updates as long as basic functionality is working.
Latest ROM and Recovery:
ROM
Recovery
(Don't worry about the page saying Pixel 6. It wouldn't let me select 6a as an option)
Optional Latest Bootloader and Radio:
Bootloader
Radio
(Update with the fastboot flash bootloader / fastboot flash radio command respectively)
Old Releases:
Old
Optional Google Apps:
MindTheGapps
(Use Lineage 20 (Android 13) MindTheGapps link -> MindTheGapps-13.0.0-arm64-20XXXXXX_XXXXXX.zip)
Follow the "official" directions in order to flash the ROM and recovery files:
https://lineage.youd.dev/340458/41/devices/bluejay/install
OTA Support:
I modified the built in updater to support updates from my unofficial source for all flashed builds. I added an option under preferences to go back to the official source in the event that official builds are started. Just go to Settings -> System -> Updater to check. I plan on uploading to OneDrive and Dropbox for these updates (bandwidth might be temporarily limited). You can always manually flash without it from a PC.
Sources:
https://github.com/LineageOS
https://gitlab.com/the-muppets/proprietary_vendor_google_bluejay
https://github.com/calsurferpunk/android_packages_apps_Updater
https://github.com/calsurferpunk/lineageos_update
(roomservice.xml attached to this post for reference)

Great, thank you for your work. I'm downloading it right now. Out of my curiosity, will there be a build for raviole in the future as well?

Thx!
Face unlock built in?

CrazyLyte said:
Great, thank you for your work. I'm downloading it right now. Out of my curiosity, will there be a build for raviole in the future as well?
Click to expand...
Click to collapse
I'm just supporting the 6a/bluejay since that's what I have. If there were a lot of requests, I could attempt it, but I would have no way to test it (and the updater wouldn't be able to use the unofficial sources since I have limited space/bandwidth to share the updates from Dropbox/OneDrive).
lucky58 said:
Thx!
Face unlock built in?
Click to expand...
Click to collapse
I don't think face unlock is supported on any of the 6 series and I've seen no reference in the Lineage OS source/ROM.

Just picked up a 6a, but I'm going to run it stock for a bit just to see what that's like (I don't think I've run stock Android for at least a decade). Can confirm, the stock ROM does not have face unlock. It does have "Screen Attention" which is supposed to delay locking the screen if you're looking at it.
Looking forward to trying out your work Cal

Nice work. Thanks a bunch ..

Bruh, i accidentally flashed the android TV gapps package

New ROM update is available. You can either download it manually or use the built in updater if coming from the earlier version. You might want to update your bootloader/radio as well (optional and links are on the original post). The bootloader/radio img files are extracted from the latest official Google updates.

Mine always gets stuck on a random percentage when sideloading. I factory reset each time and have tried with and without radio/boot updates.

2mnml said:
Mine always gets stuck on a random percentage when sideloading. I factory reset each time and have tried with and without radio/boot updates.
Click to expand...
Click to collapse
Is it anywhere around 47%? It does appear to freeze for a bit but it's still loading. Did you wait a pretty long time and let it just keep going?

calsurferpunk said:
Is it anywhere around 47%? It does appear to freeze for a bit but it's still loading. Did you wait a pretty long time and let it just keep going?
Click to expand...
Click to collapse
No I only ever really waited for about 2 minutes, I know that is super impatient lol.
I am going to try it again today and let it run during my lunch. Is there a specific order in which I should sideload and update the boot/radio?

2mnml said:
No I only ever really waited for about 2 minutes, I know that is super impatient lol.
I am going to try it again today and let it run during my lunch. Is there a specific order in which I should sideload and update the boot/radio?
Click to expand...
Click to collapse
I updated my radio and bootloader first, but doing so is optional. I don't know how much it actually affects.

Looks like the official builds are coming out now:
LineageOS Downloads
download.lineageos.org

phuzz11 said:
Looks like the official builds are coming out now:
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
I just saw the XDA article as well. Thanks for the update. I tried downloading the official through the updater but got a verification failed message. I'm not sure if it's a problem with the updater or actual official .zip.
If anyone manually downloads the official update, can you let me know if it works? I had an issue happen once before with my older OnePlus 8 Pro phone to where there was a problem with the first official download. I'm a little hesitant.

I just verified the official ROM. I was able to flash it right over the existing unofficial ROM without any trouble. Just follow the same instructions as for the unofficial:
1) Boot to recovery
2) Flash official ROM .zip
(optional)
3) Reboot to recovery again
4) Flash Google apps
5) Flash Magisk
6) Reboot system
I noticed there were some odd warnings when flashing the Google apps/Magisk (other than signature verification). Google apps seemed to error out at first (never seen that before) but I just flashed it again immediately and it finished.
Thanks to all for their support and the official Lineage OS team.