[Guide/Tutorial] Fix Nexus 6P Bootloop of Death Boot Image Patch - Android 8.1 & More

[Guide/Tutorial] Fix Nexus 6P Bootloop of Death Boot Image Patch - Android 8.1 & More - Nexus 6P General

[Guide/Tutorial] Fix Nexus 6P Bootloop of Death Boot Image Patch - Android 8.1 & More
A Fix for the Nexus 6P Bootloop of Death
Read Me
This requires you to have an unlocked bootloader. You can try different methods to get your phone to boot up and to enable OEM unlocking so you are able to unlock the bootloader and flash these 4core patched boot images.
Note
Not to deduct from the original work of @XCnathan32 or @xls654 in the original thread, but some members have asked me if I would like to create a new thread that is more regularly updated to make it easier for new and returning people to find the appropriate downloads.
You can visit the original thread here.
What needed to be fixed?
This explanation was taken from the original thread. Minor adjustments made.
The problem with most of the devices in a BLOD, is that a hardware failure related to the BIG cluster has occurred. This fix remedies the problem by disabling the BIG cores. Unfortunately, this does mean that you will take a performance hit.
The ramdisk has been modified to reflect use of the 4 cores that remain enabled. This should help performance.
What if my phone doesn't have an unlocked bootloader yet?
You'll want to try heating up your phone just underneath the camera, or leaving it on a low charge in order to get it to boot. Then quickly enable OEM unlocking in the developer options. Different ways of doing it may be explored in the original thread (see above).
Downloads and Instructions on Post #2
Tutorial on patching your own boot images on Post #3
Happy flashing!
Changelog
18/01/2018 - Updated new bootloader unlocking method via the use of `fastboot flashing unlock_critical`
9/01/2018 - Last added TheToto318 AFH Folder, MrMarques01 ElementalX and LOS 15.1 Unofficial (KevinIPS)
8/12/2017 - Initial Post

Downloads Section & Flashing Instructions
Downloads
No more patching each image! Thanks to @osm0sis 's AnyKernel2, has made available a flashable zip that can patch the current kernel and recovery! So there's no more need in patching each image manually. You can find the downloads at osm0sis's BasketBuild: https://basketbuild.com/devs/osm0sis/osmods
Take a look at the BLOD Workaround AK2 .zip as well as the patched versions of TWRP with FBE support.
Original post: https://forum.xda-developers.com/showpost.php?p=75203491&postcount=2142
If you can't access TWRP for whatever reason, I have patched more of the recent boot images. You can find them as the factory images get released: https://basketbuild.com/devs/squabbi/angler/4core-images
Instructions / Flashing Guide
To use these images in a TL;DR way of saying it, is to flash or boot a patched TWRP image and then flash the BLOD Workaround ZIP provided above last!
(Old) YouTube guide for the following instructions: https://youtu.be/czMMp2M6SEo
Now for the more detailed way.
Downloads
Latest SDK Platform Tools (adb & fastboot)
Nexus 6P Factory Images
Latest version of Magisk (for root)
BLOD Workaround AK2 flashable ZIP above.
Patched TWRP also above.
Procedure
You must have the latest version of the SDK Platform Tools or you may experience issues when flashing the images.
You must also need to have an unlocked bootloader.
If you need help installing drivers for your phone, follow this video and skip to the bootloader driver installation part:
https://youtu.be/NGy85rFFhLM?t=4m29s
You must have downloaded the Google USB drivers in the more info of the video!
Script for Reviving a BLOD Device using patched boot images (No TWRP)
Have a look at this great script made by @R3tro7, my quick look says it should do the job just fine!
https://forum.xda-developers.com/nexus-6p/general/tool-utility-script-to-fix-bootlooping-t3761085
For Reviving a BLOD Device
Unlock the bootloader.
Flash/boot patched TWRP.
Flash BLOD Workaround ZIP.
Reboot.
For Updating a BLOD Device
Extract the bootloader and radio images from the downloaded Factory Image
Open the 'images-angler-xxxxx.zip' inside the Factory Image
Extract the system and vendor images.
Reboot your phone into the bootloader.
First update the bootloader: fastboot flash bootloader *drag in extracted bootloader image*.
Reboot back into the bootloader: fastboot reboot-bootloader.
Flash the updated Radio image: fastboot flash radio *drag radio image here*.
Flash the updated boot image: fastboot flash boot *drag boot image here*.
Flash updated system image: fastboot flash system *drag extracted system image here*.
Flash the updated Vendor image: fastboot flash vendor *drag extracted vendor image here*.
Flash the updated PATCHED TWRP: fastboot flash recovery *drag patched TWRP image here*.
Reboot into recovery mode using the volume buttons to change the selection and press the power button to select.
Flash the Magisk zip in TWRP.
Flash the BLOD Workaround ZIP (remember to flash this ZIP last).
Reboot
...
Profit $$$
Previous images & TWRP /data decryption:
Patched Image Collections
All 4core patches can be found in my Android File Host folder.
@TheToto318 Collection - Android File Host Folder
This collection contains (may not be up to date):
Super XE 8.1.0_r2
TWRP 3.2.1-0
crDroidAndroid 8.1 20180103
LineageOS 15.1 - 20171229
Nitrogen-OS-O - 20171226
ElementalX N6P 6.01
crDroidAndroid 8.1 - 20180107
Nitrogen-OS - 20180106
Assorted Downloads
However, for ease of use, here are the links by build number:
Android Nougat Custom ROMs (7.0-7.1)
AOSiP 6.3 SLOBS - MD5: bac7c0ae9c84c9b9a730c2146c145e42
Android Oreo (8.0)
8.0.0 (OPR5.170623.007, Oct 2017) - MD5: ec04aac81a4967712d1c8e619ef400f5
8.0.0 (Unknown Build), build by @SkinlessMage006
Android Oreo (8.1)
8.1.0 (OPM1.171019.011, Dec 2017) - MD5: d1f34010ada50a34b446ab23d2cf850a
Source: GitHub
8.1.0 (Unknown Build), build by @SkinlessMage006
8.1.0 (OPM3.171019.013, Jan 2018) - MD5: 0d937293bfc53cf820c8ee43200d7676
May, June and July Builds of Android
Android Oreo 8.1 Custom ROMs
SuperXE - OPM2.171019.012(8.1.0_r2), thanks to @TheToto318
LineageOS 15.1 Unofficial (Unknown Build). Thanks to @kevinips
Nitrogen-OS-angler-20180106 4 Cores Fix. Thanks to @TheToto318
crDroidAndroid-8.1-20180103 4 Cores Fix. Thanks to @TheToto318
crDroidAndroid-8.1-20180107-angler-v4.0-BETA7 4 Cores Fix. Thanks to @TheToto318
Nitrogen-OS-O-angler-20171226 4 Cores Fix. Thanks to @TheToto318
lineage-15.1-20171229 4 Cores Fix. Thanks to @TheToto318
Android Oreo (8.1) Custom Kernels
Elemental-X 6.00 4-core- Thanks to: @MrMarques01
Instructions & Source: XDA Post #18
Elemental-X 6.01 4-core- Thanks to: @MrMarques01
Instructions & Source: XDA Post #114
TWRP
TWRP 3.2.0-0 - MD5: fdf4030d46a1be1af72777b02271fb21
TWRP 3.2.1-0 - MD5: 11c769711c02912abaa77cebf663e656
TWRP can't Decrypt my Data Partition!
If TWRP cannot decrypt your /data partition, you will need to format the userdata and ensure you do not use a boot image that forces encryption! All stock boot images do by default so be careful!
To format your userdata partition you can do it in either TWRP or the bootloader via fastboot.
Via fastboot: fastboot format userdata
The boot into TWRP, and it should load your internal storage.
OR
Boot into TWRP.
Select Wipe
Then Advanced Wipe
And check 'Internal Storage'
Swipe to wipe.
Reboot back into recovery.
TWRP should load your internal storage.

Patch your own Boot images to use 4 Cores
Here is a YouTube tutorial if you prefer that instead: https://youtu.be/PhObuifEp3Y
Introduction
Patching your own boot image is quite simple, all you need is essentially one tool, your boot image you want to patch and that's about it. The time it takes to patch one may take around 5-10 minutes and less as you get more comfortable with it.
If you feel this is still a little tricky, you can upload the boot image and send me a PM or reply to this thread and I, or someone will patch it for you.
Downloads
Android Image Kitchen by @osm0sis.
Your boot image that needs patching.
Steps
1. Extract the Android Image Kitchen zip that you downloaded. The extracted folder/files 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"
}
Drag the boot image you want to patch onto the unpackimg.bat, as for Linux or macOS AIK downloads, you will probably need to use the script via the Terminal in a way like this:
Code:
./unpackimg.sh '~/Downloads/boot.img'
Once the image is unpacked, 2 new folders will be created: split_img and ramdisk.
Now you'll need to edit 3 files in total. Details can be found on GitHub here: https://github.com/squabbi/4core-boot-angler-opm1.171019.011
Once you've done that, just run the repackimg.bat script again and you should see a new file created: image-new.img. This is your newly patched boot image.
Flash it via fastboot or TWRP and see if your phone boots.
Optionally run the cleanup.bat script to return your AIK into a clean state for your next boot image to patch. Be sure to copy the image-new.img to another directory or rename it, otherwise it will be cleaned up! (deleted)
Now that you've patched your boot image, the last step you need to do is share it! Post it as a reply here in this thread and I'll add it to the downloads post, just make sure to mention me using the '@' symbol. Or alternatively, send me a PM and I'll add it to the downloads post as well.

I was closely monitoring the original thread and couldn't keep up OP is not updated for the newer build (DP's and the latest official).
This is a great thread for those who are like me. I just hope first OP would not mind.
Thank you all for your tinkering!
EDIT: does any of your patched boot.img work with any Oreo custom rom? Just asking for when I get bored with stock.

kemistry01 said:
I was closely monitoring the original thread and couldn't keep up OP is not updated for the newer build (DP's and the latest official).
This is a great thread for those who are like me. I just hope first OP would not mind.
Thank you all for your tinkering!
EDIT: does any of your patched boot.img work with any Oreo custom rom? Just asking for when I get bored with stock.
Click to expand...
Click to collapse
I too hope they won't mind. :fingers-crossed:
I always thought that each ROM needed their own boot image, so I would assume that the stock Oreo one will not work on custom ROMs.
I'm more than happy to take requests for patching boot images, so just upload the boot image and send me a link. I'll patch it and then add it to post #2.

Wow man! Thanks for keeping the bootloop solution alive!
Do you know if there is any performance difference when using that modified ElementalX kernel from the other bootloop thread and using just the modded boot image?

Android 8.1 Working Great
Just flashed your 4-core version of TWRP 3.2 and the Android 8.1 boot image, Nexus 6P seems to have updated fine and is running reasonably smooth. Thanks for making a new post and releasing updated 4-core stuff!

Thank you for turning my paperweight 6P into a functional device!

How can I update to 8.1 and use 4 core mod? I'm running 8.0 currently.

Hi squabbi,
First of all thanks for your great work. I'm currently trying to patch the latest ElementalX kernel to used 4 cores only, but I'm a little bit confused as to which files need to be changed, since the github page from post 3 doesn't really detail that. Is it only the changes in fstab, init.angler.rc and boot.img-cmdline (the changes made in the commit history), or does anything else need to be changed?
Thanks for your help
EDIT: Nevermind, I think I figured it out. I think all that needs to be changed is to add maxcpus=4 to the last line of cmdline.sh for ElementalX to use 4 cores only (provided a modified stock boot.img was flashed before ElementalX kernel). I'll test it later and if it's working I'll post the modified ElementalX kernel for Android 8.1.

gb_14 said:
How can I update to 8.1 and use 4 core mod? I'm running 8.0 currently.
Click to expand...
Click to collapse
There are instructions in post 2.

MrMarques01 said:
Hi squabbi,
First of all thanks for your great work. I'm currently trying to patch the latest ElementalX kernel to used 4 cores only, but I'm a little bit confused as to which files need to be changed, since the github page from post 3 doesn't really detail that. Is it only the changes in fstab, init.angler.rc and boot.img-cmdline (the changes made in the commit history), or does anything else need to be changed?
Thanks for your help
EDIT: Nevermind, I think I figured it out. I think all that needs to be changed is to add maxcpus=4 to the last line of cmdline.sh for ElementalX to use 4 cores only (provided a modified stock boot.img was flashed before ElementalX kernel). I'll test it later and if it's working I'll post the modified ElementalX kernel for Android 8.1.
Click to expand...
Click to collapse
Yep, that should be it! Do let us know how to does.
And for the necessary file changes that are shown on GitHub, that's only for boot images.

I'm currently using 7.1 modded boot and my phone just shut down and it can not power on, no charging, no led light, just black screen. It's literally a brick right now, so, any guess?

It cant boot to TWRP
Hi
i have followed every step, but when i want to boot into recovery mode, it will go back to bootloop... goes to the yellowish warning then to Google logo screen with an unlocked lock and it reserts....
i really need your help...
thanks much in advance.

Anyone knows where to get a specific bootloader image ?

MrMarques01 said:
Hi squabbi,
First of all thanks for your great work. I'm currently trying to patch the latest ElementalX kernel to used 4 cores only, but I'm a little bit confused as to which files need to be changed, since the github page from post 3 doesn't really detail that. Is it only the changes in fstab, init.angler.rc and boot.img-cmdline (the changes made in the commit history), or does anything else need to be changed?
Thanks for your help
EDIT: Nevermind, I think I figured it out. I think all that needs to be changed is to add maxcpus=4 to the last line of cmdline.sh for ElementalX to use 4 cores only (provided a modified stock boot.img was flashed before ElementalX kernel). I'll test it later and if it's working I'll post the modified ElementalX kernel for Android 8.1.
Click to expand...
Click to collapse
Looking forward to a positive result!

squabbi said:
There are instructions in post 2.
Click to expand...
Click to collapse
I want to update, without losing any data.

Hi everybody.
As promised, here's the modified 4-core ElementalX 6.00 kernel. Please note that this kernel works with Android 8.1 only.
Download
https://goo.gl/qhhJx8
Instructions:
Flash the modified stock boot.img for Android 8.1 that can be found in post 2 using fastboot or TWRP (This is important)
Flash ElementalX-N6P-6.00-4cores.zip using TWRP
All credit goes to @flar2 for the kernel, @XCnathan32 and @xls654 for creating the 4core patch, and @squabbi for the modified 8.1 stock image.
@squabbi Feel free to add the zip to the OP.

MrMarques01 said:
Hi everybody.
As promised, here's the modified 4-core ElementalX 6.00 kernel. Please note that this kernel works with Android 8.1 only.
Download
https://goo.gl/qhhJx8
Instructions:
Flash the modified stock boot.img for Android 8.1 that can be found in post 2 using fastboot or TWRP (This is important)
Flash ElementalX-N6P-6.00-4cores.zip using TWRP
All credit goes to @flar2 for the kernel, @XCnathan32 and @xls654 for creating the 4core patch, and @squabbi for the modified 8.1 stock image.
@squabbi Feel free to add the zip to the OP.
Click to expand...
Click to collapse
Feedback: Working with Android 8.0. Thanks :good:

v0ne said:
Feedback: Working with Android 8.0. Thanks :good:
Click to expand...
Click to collapse
I hope you mean Android 8.1. Because with 8.0 it actually shouldn't work

Related

[ROM][OFFICIAL] LineageOS 14.1 for Nexus 9 (flounder)

Reserved
This post is for Nexus 9 (LTE) model.
Important Info
The newest lineage 14.1 flounder_lte (LTE) builds rely on proprietary vendor and firmware components from the N4F27P (October 2017) monthly update from google. This means your device needs to have the vendor and bootloader img from that update. They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
* vendor-flounder_lte-n4f27p.img
* bootloader-flounder_lte-3.50.0.0143.img
The vendor img is flashable with twrp or fastboot, but for the bootloader img use fastboot.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/flounder_lte
LineageOS servers no longer make 14.1 builds for any devices. You can use my builds here. My older builds are here.
Google apps: http://opengapps.org/?arch=arm64&api=7.1&variant=nano (Use arm64 / 7.1)
su addon zip (for root): Install zip / Removal zip
NOTE#1: After su addon install, root is disabled by default. You can enable it in developer options.
NOTE#2: My unofficial builds do not force encrypt.
Weather Provider Addon (Optional)
For those that like the lineage cLock widget, here's the OpenWeather apk you need to get weather info.
https://mirrorbits.lineageos.org/WeatherProviders/OpenWeatherMapWeatherProvider.apk
Note: You'll need an api key from OpenWeather.
Stats
https://stats.lineageos.org/
Credits
Many thanks to the LineageOS team and all the contributors out there in the community :good:
Contributors
Hashbang173, razorloves
Source Code:
Main device tree: https://www.github.com/LineageOS/android_device_htc_flounder_lte/tree/cm-14.1
Inherited device tree: https://www.github.com/LineageOS/android_device_htc_flounder/tree/cm-14.1
Kernel tree: https://www.github.com/LineageOS/android_kernel_htc_flounder/tree/cm-14.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_htc/tree/cm-14.1
Android version: 7.1.2 Nougat
Kernel version: Linux 3.10.103
Status: Nightly

Wooooh! It's here

Can Nexus9 (lte) use this rom? If flash this rom only can not use lte,i can accept it.

Yeah! This is great news!
Will definitely flash this rom on my laggy N9

Can I dirty flash from the unofficial builds or should I do a full wipe?

Will it work on the LTE version? I don't mind if LTE does not work as long as I can try out the ROM without getting boot loops.

hextence said:
Will it work on the LTE version? I don't mind if LTE does not work as long as I can try out the ROM without getting boot loops.
Click to expand...
Click to collapse
I think so!

LTE version?
For people who need LTE

perfec

Is the Nexus 9 LTE going to have official support?
Sent from my iPhone using Tapatalk

Thank you very much! I hope it is less laggy than the stock firmware.

vendor image is critical at time of OS installation
Hi there.
First of all, thanks so much for the official N9 build for Lineage. Really appreciate it.
I wanted to describe my experience this morning. I should start by saying that I am *not* a hacker, just an enthusiastic user. I can follow instructions, and have been using non-stock ROMs since Cyanogen 7.
I was upgrading from the most recent version of Cyanogen. Before I started, I upgraded to the latest TWRP. Then when booting into recovery, found that my decryption passphrase didn't work. I downgraded version by version until twrp-3.0.2-0-flounder.img which is apparently the latest that worked. After installing Lineage OS, I upgraded to the newest TWRP again.
More importantly, I wanted to point out that by following the instructions on the Lineage OS wiki for the Nexus 9, I almost got to the point of thinking I had bricked my device.
The main reason is that the instructions don't mention the Vendor image issue at all: https://wiki.lineageos.org/devices/flounder/install
After wiping, installing Lineage OS and GApps pico, I rebooted. When it got to the decryption passphrase, I got the pop-up warning about the Vendor image being mismatched. No problem, I thought, as I've seen that before on Cyanogen installs. I put in my decryption passphrase. The screen remained unchanged for a couple of minutes, then I got something I'd never seen before. A page notifying me that my passphrase was correct, but the system was corrupt, and an option to fix it (no other option was available except to force power-off). So I took that option and it rebooted into TWRP. It boots into recovery and apparently runs a script and reboots the system again. But the same issue occurred again, nothing was fixed.
No problem, I thought, I'll just power-off, boot into the bootloader, enter recovery, and try again. Except that after installing Lineage, I found that volume-down+power button no longer started the bootloader!!! I tried many times, but the best I got was the device booting into the system and getting the same problem where it said the system is corrupt. It was at this point that I thought I had bricked the device - can't boot into system, can't get to the bootloader, so can't get to the recovery.
After many attempts, I tried one last thing:
Boot into system
On the corruption notification screen, I pressed the button to "fix" the system corruption
when the device rebooted into Recovery to run the script, instead of entering my passphrase, I hit cancel. This cancelled the script process but left me in recovery. I then selected reboot -> bootloader. Success!!
I was then able to connect the device to my laptop and copy the Vendor image I had extracted from the official Google system image using
Code:
fastboot flash vendor vendor.img
I then rebooted, and everything worked fine.
So it seems that in this instance, it may be critical to install the Vendor image before the first reboot. In earlier versions of Cyanogen when I had a vendor image mismatch it never prevented the device from booting and I was able to update it later on.
In which case, whoever has access to the wiki on the Lineage website - could you add those instructions in?

Just to add - I now seem to have bricked the device. Everything was working fine. I rooted the device using the supplied zip. It booted up fine. Now it won't reboot. It gets to the decryption passphrase field - verifies the password, continues to boot, and never finishes.
I can't get into the bootloader. Volume down+power doesn't work. Is there another way to do this?

Was using stock android on my Nexus 9. Already had root with the latest TWRP recovery installed. Did not run into any issues during the install(forgot to flash the Gapp at first, but could do it later in recovery, again no issues)
This is the first time I am using a Custom ROM. Got some questions .
1. I have the default apps for the lineage OS along with the same Gapps, How to remove the default lineage OS apps?
4. If anyone can share the advantages of the Nightly over custom ROM , it'll be great.
Other than these, no other major issues so far. will update the thread with the user experience

For anyone with LTE model please test this build. Let me know if there's any issues with lte or anything.
https://www.androidfilehost.com/?fid=889764386195906667
Here's the N4F27E vendor img for the LTE model, if you need it.
vendor-volantisg-n4f27e.img
thanks
No more testing needed. Results were good. Nightlies started for LTE model.

yhvo2gt9 said:
Just to add - I now seem to have bricked the device. Everything was working fine. I rooted the device using the supplied zip. It booted up fine. Now it won't reboot. It gets to the decryption passphrase field - verifies the password, continues to boot, and never finishes.
I can't get into the bootloader. Volume down+power doesn't work. Is there another way to do this?
Click to expand...
Click to collapse
Decryption passphrase in TWRP? Or Lineage?
---------- Post added at 04:51 PM ---------- Previous post was at 04:49 PM ----------
Just to let you all know, I got Lineage up and running, restored from my gmail account. I had stuck with 6.0.1 stock, 7 never cooperated, it was still getting laggy and what not. I will post more details about the install in a bit, but I just wanted to let any curious parties know this build seems to be working OK

Is the poor volume fixed in the official build or do we still need to flash a custom kernel to fix it?

I just flashed a minute ago. I've been waiting for this to be released. I switched over to Lineage on my OnePlus when it first came out. The nexus has been way too laggy on the latest stock releases. I hope this helps. I received a vendor image mismatch error on boot up but so far no issues. I'm going to flash gapps and will report back later. Thanks for working on this!!

The LTE one appears to be working fine in my tablet. Thank you
Sent from my iPhone using Tapatalk

[ROM][9.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510]

Oo our first custom rom!! Thanks alot!! Cant wair to try it soon

Important Note: The Night Mode setting in Developer Options is set to "Always off" by default. Don't change it! When I set it to "Automatic (based on time of day)", the screen went black and I couldn't recover without a factory reset. (I'm assuming that this was a bug in SystemUI.apk.)

Thanks for the effort and time you've put into this.
Unfortunately I can't get it to work. I will wait for detailed full instructions. I just keep getting Odin fails.

NightHawkUndead said:
Unfortunately I can't get it to work. I will wait for detailed full instructions. I just keep getting Odin fails.
Click to expand...
Click to collapse
Well, I just verified the MD5s and they match. However, to be a little more squared away, I replaced the original .tar file that I uploaded with a .tar.md5 (a.k.a. "tarball) which has the MD5 footer that Odin can use to verify the file integrity. I've also compressed the contents with LZ4, which cut the size down by a third.
Installing the new tarball with Odin3 v3.13.3 on my tablet went smoothly, so I hope this works for you.

Finally got it to work. Had to flash back to stock. Wipe. Then immediately reboot bootloader again and flash Rom.
How do I go about rooting now?
Edit: nevermind, got it rooted. Everything is working fine now!
Sent you a donation for your work. ? ?

I have a new SM-T510 on T510XXU1ASEF
I flashed this ROM with Oding3 3.13.3. Then it rebooted. The Nexus logo goes by, I am asked to confirm the ROM is non-standard by pressing the "power" button. Then I get the TWRP splash screen, and it hangs.
Tried to flash 3 times, same result.
Is there something to going back to stock, wiping, bootloader, flash again? Or is that just doing things until it works?

garyemiller said:
I flashed this ROM with Oding3 3.13.3. Then it rebooted. The Nexus logo goes by, I am asked to confirm the ROM is non-standard by pressing the "power" button. Then I get the TWRP splash screen, and it hangs.
Click to expand...
Click to collapse
It's important that you wipe the data partition before TWRP boots, since it currently hangs when it encounters an encrypted file system. (Yes, this really shouldn't happen, but I haven't found a fix for that TWRP bug yet.)
Did you select "Wipe data/factory reset" in the stock OEM recovery immediately before you flashed this custom ROM?

"Did you select "Wipe data/factory reset" in the stock OEM recovery immediately before you flashed this custom ROM? "
Yes.
I got it to work. reinstalled stock rom (link above). Booted it stock. Enabled Developer Mode, Enabled USB debugging. confirmed OEM still unlocked. Boot to recovery, wipe, boot to bootloader. Flash this ROM with Odin3. reboot. All is well.
So now I guess I gotta do the Device ID dance. Install Magisk Manager, patch the boot.img from your tar file, then use TWRP to install the magisk_patched.img as boot.
Along the way I also wasted a lot of time trying to flash with heimdall 1.4.2. But that was very flakey. Odin3 just worked.
---------- Post added at 08:46 PM ---------- Previous post was at 08:23 PM ----------
I guess I should mention my biggest issue was unlocking the bootloader. Not like before.
Power off. Hold Vol UP and Vol Down. Plug in USB. Long press Vol UP to unlock.

garyemiller said:
So now I guess I gotta do the Device ID dance. Install Magisk Manager, patch the boot.img from your tar file, then use TWRP to install the magisk_patched.img as boot.
Click to expand...
Click to collapse
If you install Magisk, you might not have to do the device certification dance. It tries to fake out Play Protect.

The device certification was painless. I've doe that before on other devices.
Rooting with Magisk was also painless:
Grab boot.img from your tarball.
adb push boot.img /storeage/emulated/0/Download
patch using Magisk Manager
adb pull /storage/emulated/0/Download/magisk_patched.img .
heimdall flash --BOOT magisk_patched.img
I can't get SafetyNet to pass, even with Magisk SafetyPatch module. But not a big deal to me.
Is there a way to turn off the google page on the launcher?
Thanks for the nice ROM! So much better than stock.
I'm still looking for a good ad blocker for Pie. Up tile now I have used a Raspberry Pi as a dnsmasq server for ad blocking.

garyemiller said:
Is there a way to turn off the google page on the launcher?
Click to expand...
Click to collapse
If you open up the Android One Launcher settings, there's a "Display Google app" option that you can disable.
garyemiller said:
I can't get SafetyNet to pass, even with Magisk SafetyPatch module..
Click to expand...
Click to collapse
Yeah, I've tried the usual tricks like spoofing the fingerprint, but that didn't work either. This kind of hard Play Protect device rejection seems to happen for me whenever the vendor partition is using release keys and the system partition is using test keys.
I haven't found an XDA thread yet that really provided deep insight into the algorithm that Google uses for Play Protect and SafetyNet. And given the proprietary nature of what it's doing, we may never get it. I think our best long-term solution is to get LineageOS 16 builds that pass CTS testing, but we may have to scrounge for 64-bit drivers.

I just went with Nova Launcher. It has been good to me.
I can wait for Lineage to catch up. I'm happy to be rid of bloatware. And with root I can block ads and my firewall works.
Thanks for the ROM! I'm happy!

ankh_hikes said:
Which stock files do I need to replace the nexus boot splash screens? I would like have the Samsung ones.
Click to expand...
Click to collapse
Just restore the original param image. (But seriously, why would you? The stock boot splash is ugly! )

Just ordered my T510, can't wait to try this out when it arrives

d4dave said:
Just ordered my T510, can't wait to try this out when it arrives
Click to expand...
Click to collapse
The 3G/128G config was selling for just $250 USD through Costco until a few days ago. That's a pretty insane value....as long as you aren't stuck with Samsung's One UI, that is.

will there be a new release coming?

DarthGW said:
will there be a new release coming?
Click to expand...
Click to collapse
Yes, I'm trying to build an unofficial LineageOS 16.0 release, but am struggling with some build issues. The primary goal is to deal with the Play Protect device certification (but I definitely won't pass SafetyNet). Eventually, I'll also get to fixing MTP.

wow dude, thanks a lot for you work

Is it possible to install this on the 510 with Product code NEE
PDA T510XXU1ASF2
CSC T510OXM1ASF3
It's the stock may Nordic firmware

12-19 - ViperExperience Beta 14 | Android 13 | November 2022 Security Patch |GSI

{
"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"
}
ViperExperience 12L GSI for U12+
"Choose your flavor! - The next Generation Viper ROM"
Dear Community,
Venom ROMs takes the next big step for your HTC, as well as other Treble A/B devices out there! You want Android 11, but don't want to miss out on the hardware benefits of your HTC U12+? Or you want to enjoy all of your beloved HTC Apps on another OEM? Then we have the best of both worlds for you today (or very soon)! Decide for yourself between an Android Stock Experience, or an HTC Sense Experience by choosing between Pixel Launcher and HTC Sense 10 UI Launcher. On your HTC U12+ you can in addition continue to use your popular HTC features like HTC Edge Sense, HTC FaceUnlock and the HTC Camera!
We at Venom ROMs are using the AOSP GSI based on Android 11 to bring you the best HTC features paired with the latest Android AND Pixel experience from Android 10.
Thanks to @phhusson for his Treble experimentations repos, @JEANFRIVERA, @5m4r7ph0n36uru, @Captain_Throwback, @MassStash, @donmarkoni for all tests you did for me to make this ROM.
mikalovtch
Must have unlocked bootloader from htcdev.com or factory S-OFF
Download Viper Experience 11 GSI from Androidfilehost.com
Download „vbmeta_noverity.zip“ from Androidfilehost.com
Download latest TWRP from #2 post or Download latest PBRP from here: PBRP
Boot your Device in Bootloader Mode
Boot to TWRP or PBRP, using the following command:
Code:
fastboot boot nameoftwrpimage.img
Rename „vbmeta_noverity.zip“ to „update.zip“ and place it inside your adb/fastboot folder
Push „update.zip“ to your device, using the following command:
Code:
adb push update.zip /update.zip
Make sure you are on slot A on reboot page of TWRP or PBRP if not switch to slot A and fasboot boot twrp.img again
Flash „update.zip“ from recovery UI
Reboot to Download from recovery UI
Erase userdata and system using the following commands: (THIS WILL FORMAT INTERNAL STORAGE!)
Code:
fastboot erase userdata
and:
Code:
fastboot erase system
Flash Viper Experience 10 GSI, using the command:
Code:
fastboot flash system nameofimage.img
Rebootyour device, using the command
Code:
fastboot reboot
Setup and enjoy an mew ROM on your HTC U12+!

XDA:DevDB Information
12-04 - ViperExperience Beta 12 | Android 12L | April 2022 Security Patch |GSI , ROM for the HTC U12+
Contributors
mikalovtch, JEANRIVERA
Source Code: https://github.com/phhusson/treble_experimentations
ROM OS Version: Android 12L
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 9 Pie
Based On: AOSP HTC Sense
Version Information
Status: Beta
Beta Release Date: 2020-12-22
Created 2020-03-07
Last Updated 2020-12-22

Prerequisites
PIE_noverity_vbmeta_both_slots-TWP.zip: This zip patches the stock vbmeta for BOTH slots to ensure the device will boot after flashing the GSI. The zip in the OP only patches slot A, so you would have to ensure you are on slot A when flashing the system image. This zip allows either slot to be used. Thanks @The_Walking_Playground for posting the updated zip!
Fixes
UPDATE-BeyondStock™_U12+_Exodus_Vendor_Fixes-CPTB-signed.zip: This zip patches the vendor partition on U12+ and Exodus devices to fix Bluetooth streaming/headset compatibility, and enables exFAT support with the stock and BeyondStock™ kernels (NOTE: The exFAT portion of this fix is no longer needed, but has no negative side effects).
Patches
UPDATE-BeyondStock™_Header_Patch_U12+_Exodus-CPTB-signed.zip: This zip patches the boot.img header of the installed kernel so that decryption will work in permanently installed TWRP. This zip should be used if you're using a custom kernel that doesn't require patching for touch.
UPDATE_BeyondStock™_U12+_Exodus_Remove_Forced_Encryption_CPTB_signed.zip: This zip disables forced encryption on the device so that it doesn't automatically get encrypted after Formatting Data in TWRP.
Custom Recovery
Official TWRP for U12+: This is the recommended TWRP version to use with the ROM, with full Android 11/12 decryption support.
Kernels
UPDATE-BeyondStock™-Kernel-Pie-v0.02-U12+_Exodus-signed.zip: This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP older than 3.4.0, and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
UPDATE-BeyondStock™-Kernel-Pie-v0.02-U12+_Exodus_TWRP_3_4_0_CPTB.zip: This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP 3.4.0 (and higher), and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.

[MANUAL] Fix CTS Profile Mismatch
Initial situation: most GSIs are rooted to a certain extent. This also applies to the AOSP GSI, which is the basis of our ViperExerience ROM.
Precondition: To correct the CTS mismatch, it is necessary that Magisk is installed.
If the precondition is fulfilled, proceed as follows:
Install the Magisk modules "Busybox" from Osmosis, and "MagiskHide Propst Config" from Didgeridoohan
After a device restart, open a Terminal App on your HTC U12+ and go through the following steps
Request root privileges by typing
Code:
su
Start the Props module by typing
Code:
props
Type
Code:
1
to set a new fingerprint for the device
Follow the instructions in order by selecting
Code:
f
and
Code:
7
(for HTC).
finally type
Code:
4
(for U12+ Pie).

How to permanently flash TWRP via the TWRP.img file inside TWRP
1. Make sure you have a working fastboot and adb environment! Your device´s bootloader must be unlocked!
2. Download the twrp.img file from here: https://github.com/CaptainThrowback/android_device_htc_ime/releases
3. Boot to TWRP. Navigate to Advanced -> Install Recovery Ramdisk -> Choose the twrp.img downloaded earlier. Wait for the flash to be completed successfully and do either
4. Download BeyondStock™-Kernel This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP, and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
5a. If you want to be rooted flash the magisk.zip
5b. If you don't want to be rooted navigate to Advanced -> Fix Recovery Bootloop to be able to boot into system
Thanks to @JEANRIVERA

reserved

reserved3

reserved4

reserved5

reserved6

Support
Hi users, I was a noob once too, believe it or not I had questions & stupid questions too but I was never afraid to ask, in my way to be part of this amazing team I have known all kind of Devs, with different levels of friendliness , but being honest in some way or another I have learned from all of them a little something, Now I want to give back to the community as much as I can, I am no Dev, but I do know a trick or two, if I don't know the answer to your questions, I will try my best to get an answer for you from the Team.
The instructions in the OP have been updated for better understanding and corrected some points, if anyone has tried unsuccessfully to flash this ROM please follow the updated instructions, if anyone have trouble or not booting device please feel free to ask, I will try to guide anyone as much as I can and as friendly as possible. I see there is 73 downloads on AFH of the ROM but only few users reported their experience here, maybe if you are afraid to ask, don't be, if you navigate through the thread you will see only friendly responses, and I will try my best to keep it that way, don't be afraid to tag me for support

And I'll take this one, just for the kicks.

I am running android 8 with viper 2.0 and i tried to update to this but ADB says that my file system is read-only. What is the recommended course of action?
Code:
adb: error: failed to copy 'update.zip' to '/update.zip': couldn't create file: Read-only file system
I read elsewhere that 'adb root' would be needed but i figured it would be better to ask here instead of following some random post about a somewhat similar situation.

First off: don't install this ROM on Android 8 firmware. It's an Android 10 GSI and all development an testing has been done on the latest EMEA firmware.
So the way to go from ViperU12+ would be to go back to full stock unsung a RUU and upgrade to Android Pie. This is to make sure you start from the correct base and environment. Then boot the device and copy the vbmeta zip onto /sdcard. Then reboot to bootloader and boot to TWRP, and follow the instructions from post #1 to the point.
Use the latest TWRP from @Captain_Throwback, found here: https://github.com/CaptainThrowback/android_device_htc_ime/releases/tag/3.3.1-2
Sent from my Pixel 4 XL using XDA Labs

it should be: 9 Reboot to Download from TWRP UI not
9 Reboot to bootloader from TWRP UI
on Production Units in Bootloader you get an error:
FAILED (remote: Erase is not allowed on PRODUCTION device)

This ROM is been running quite fantastic for me, I am so excited to help test and get this released for everybody to use! Can't believe we have Android 10 on this u12 plus Beast, it's so amazing! LOL thank you so much @mikalovtch, @JEANRIVERA, @Captain_Throwback, &
Sent from my HTC U12+ using Tapatalk

Oh man, you`ve done brilliant work:highfive::good:
it is almost perfect, butter smooth and fully functional except few bugs.
some issues are:
1. time and date automatically reset to 2020.03.07 4:47 after reboot, which can be quite annoying.
2. edgesense squeeze gesture feedback is weird. it`s not like the feedback of power btn but vibrating.
3. edgesense setting does not show in the settings.
some Pro tips:
1. flash system.img via twrp or via usb under DOWNLOAD mode. you can not flash it under BOOTLOADER mode.
2. you can access edgesense settings by this method:
goto Setting.Apps, show all system Apps and find out edgesense service app. In the detail screen(where you can clear the cache and force stop, idk the exact term), tap Advanced, Additional settings in the app.
3.kirisakura kernel tested, all good.
btw i use China version u12+, hope this will help you.
Thanks you bro!

issue has been fixed

JEANRIVERA said:
without the vbmeta.zip the ROM will not boot at all, the instructions fail to specify you must be on slot A to flash the vbmeta.zip and ROM, instructions will be updated soon, if you are on slot B another vbmeta zip should be used.
Click to expand...
Click to collapse
thank you! but i still boot without flashing vbmeta.

neoncloud4399 said:
thank you! but i still boot without flashing vbmeta.
Click to expand...
Click to collapse
is your device S-OFF? that would be the only possible reason it boots

JEANRIVERA said:
is your device S-OFF? that would be the only possible reason it boots
Click to expand...
Click to collapse
no, it still s-on.
i followed this procedure:
clear system, flash system, clear userdata under twrp
flash vbmeta.zip under twrp By sideload
reboot, failed to boot, show warning messages.
run fastboot oem rebootRUU to ruu flash mode and downgrade to 1.21
fastboot erase persist
boot to 1.21 China then upgrade to PIE.
boot to DOWNLOAD, erase system, userdata, flash system both system_a and system_b and it boots.

[DEPRECATED][ROM][diOS][N] Samsung Galaxy Tab A 7.0 LTE SM-T285 (gtexslte)

{
"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"
}
This is discoveryOS (diOS)
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About this project: discoveryOS (or in short: diOS)
I was not satisfied with any external car navigation system I can get because either they are ultra slow, outdated, having bad user experience, missing speed cam support or simply taking ages to get a gps lock within my car.
So the main approach here is not having the best ROM for all users but for those having the same need then I have. Usually these both should not conflict so if I fix an issue for my needs it might fix yours as well. But my focus is navigation, nothing (much) else.
Examples: if Camera has issues I might not solve it, if calling has issues I might not solve it, etc.
Features of discoveryOS
fully based on /e/ OS for a full google-free experience
F-Droid (OpenSource Apps as an alternative to Google Play) including extra repos
debloated everything not needed for diOS (for details check this list)
Integrated MagicEarth Navigation
Integrated Automate App
Integrated Aurora Store
Speaker output optimized for speech (i.e. increasing loudness as much as possible)
my builds come with full OTA update support (from v2.0 on)
(... you know that thing which informs you that a new update is there and where you just click to download + install)
Roadmap
Implementing Kiosk Mode for navigation only (might be provided as a separate build)
links: <--- abandoned by using the app "Automate" instead
the one I will go for (tested fine already): https://www.sdgsystems.com/post/pro...droid-devices-with-a-device-owner-application
older approaches:
Implementing Kiosk Mode in Android - Part 1
Part 2 Part 3 Part 4 Part 1: No Android Changes Required Note: Looking for Kiosk mode in Android Lollipop 5.0 or later? Skip to part 3. What is “Kiosk Mode” and why would you want to use it? Kiosk Mode basically allows a single Android application to have full control of the system. The user is...
www.sdgsystems.com
Implementing Kiosk Mode in Android - Part 3: Android Lollipop (and Marshmallow)
Part 1 Part 2 Part 4 Part 3: Android Lollipop (and Marshmallow) Android 5.0 (Lollipop) and 6.0 (Marshmallow) now have an official Kiosk Mode that anybody can use, but they don’t call it Kiosk Mode. They call it “screen pinning” or “task locking”. This article will provide information on how to...
www.sdgsystems.com
Implementing Kiosk Mode in Android - Part 4: A Better Provisioning Method for DPC / Device Owner
Part 1 Part 2 Part 3 In part 3 of our series on kiosk mode, we provided source code for our Set Device Owner app. This app allows you to provision Android Lollipop and Marshmallow devices using the “device bump” method, which configures device owner apps or device policy controllers (DPC) such...
www.sdgsystems.com
Integrate my created Automate flow to simulate a KIOSK mode (i.e. start navigation on boot and keep it on top always)
Requirements
Your device need to be unlocked (seriously?!)
Latest TWRP/SHRP build is highly recommended, e.g. mine: see my recovery post
Do a full Nandroid backup before doing anything else!
Samsung STOCK firmware should be on T285XXU0AQH1.
You can check your current firmware version in Android -> settings -> About / Phone info -> Baseband version
If you like try first without flashing this firmware but if you encounter any issues upgrade to this version first before reporting
Fast and (afaik) good site for downloading: https://sfirmware.com/samsung-sm-t285/
(scroll down and type T285XXU0AQH1 in the search box, choose the one for your country, download, flash as usual, flash TWRP/SHRP again, flash this ROM)
Installation
Backup
When you flash diOS the first time:
Wipe: System and do a factory reset !
A LOT of bad stuff can happen otherwise
Flash the ROM
Optional (if you want root): Flash Magisk
Flash OpenGapps ????? STOOOOOOOOP NO No no! you don't want that on a google-free phone! diOS contains everything you need to live without Google!
Boot (be patient on first boot!!! SIM detection might take a minute after the FIRST boot after clean flash as well)
Open Maps (MagicEarth) and click the download button to get your country/region maps
Open Automate to import the kioskmode flow
Open F-Droid -> Settings -> Repositories and choose those you want to enable (most of them are described here) & swipe down to update the repo list.
Open Aurora -> choose Anonymous as long as you don't want to have paid apps working
Enjoy
Known issues
no OMS support! OMS is a hack DEEP in the android sources and all these are outdated now. if you need that use jedl's build
build is ENG , i.e. "adb root" will work and no auth required for ADB
bluetooth is working but using the blobs by jedld's build until I find the time fixing the android sources (unfortunately the repo of jedld does not contain the full history so I have to compare manually...). Until then I keep it like that.
not charging on USB connection (normal power supply works fine) - still investigating. Seems to be an issue with my kernel.
This ROM is just coming with BASIC stuff so several apps you might want to see in a regular Android ROM are simply not there.
Examples (excerpt only!):
- no Camera app
- no Browser app
- no Gallery app
- no Email app
- no Calendar app
- no <fill-in-whatever-you-are-missing>
the complete list can be found here always
If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1
Download
Get the builds from my leech server
discovery OS: https://leech.binbash.rocks:8008/discoveryos/nougat/gtexslte/
Note:
Builds are updated when I decide to do so. There is no build cycle.
Changelogs
search results from this thread: click
Credits
LineageOS
jedld, really! thanks dude, not just for giving a starting point but also for providing your sources.
... if I forgot to mention YOU, tell me
Sources
It took me a while (2 or 3 weeks iirc) to clean up all the sources from jedld in order to be able to update and keep in sync with LOS itself.. All these can be found here:
github org
build manifest
XDA:DevDB Information
discoveryOS, ROM for the Samsung Galaxy Tab A series
Contributors
steadfasterX, jedld (without his work I would never had bought that tab! he made all the main parts until 2018!)
Source Code: https://github.com/smt285
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: /e/ OS
Version Information
Status: Beta
Beta Release Date: 2020-11-19
Created 2020-04-03
Last Updated 2020-11-20

everything around my recovery images
RECOVERY images
Download (shrp + twrp)
TWRP: here
SHRP (recommended): here
I provide 3 formats:
IMG (twrp only)
TAR (shrp & twrp)
ZIP (shrp only)
When to use the IMG (twrp only)?
If you flashed a custom recovery already
if you like to flash by download mode with heimdall
When to use the TAR (shrp & twrp)?
If you never flashed a custom recovery before you have to use this one
if you like to flash by download mode with ODIN or JOdin
When to use the ZIP (shrp only)?
If you want to switch from TWRP
if you want to upgrade from one SHRP version to another
if you flashed the TAR of SHRP in download mode by ODIN or JOdin you HAVE to flash this ZIP in SHRP once
How to flash the IMG?
boot to your custom recovery
push the IMG to your device (e.g. by adb)
select flash
ensure you select "IMG" (when in TWRP. when in SHRP that is not needed)
select the IMG file
choose "Recovery" as the "Target Partition" and flash
Reboot to Recovery to complete the setup.
How to flash the TAR?
boot to download mode
start ODIN/JOdin
put the TAR into the AP/PDA slot
ensure the "Auto Reboot" is NOT ticked/checked
flash
turn the device off (HOME+PWR+VOLDOWN) and directly switch just the VOLDOWN button to VOLUP when it wakes up and hold all 3 buttons until you see the recovery loading
How to flash the ZIP?
boot to your custom recovery
push the ZIP to your device (e.g. by adb) (or start and use adb sideload and you are done)
select flash
select the ZIP & Flash
Reboot to Recovery to complete the setup

Reserved

New build arrived
Changelog
Release date: 2020-04-03
Download: see OP
initial build:
I had a REALLY hard time to actually make LOS 14.1 boot with cleaned sources.. thought the ramp-up will take a week at most .. but that was way off..
jedld had done several patches within AOSP and I had to find out which are required where etc. the main reason why my build were not booting at all (which is f**** hard to debug without and log and/or adb ) was that one.
But I needed to clean the sources as several parts of these were incredible outdated and so needs to be udpated.
I had spent several more days to cleaning up even more stuff and finally uploaded a test build.
feel free to join but read the KNOWN ISSUES topic carefully before.
It is still in a very early state and I have tested pretty much nothing else then boot, apps, bluetooth, WiFi
Kernel:
switching to EUR kernel
implemented kernel build within LOS build!
added own TWRP defconfig
moving kernel modules like WiFi to /system
.... and more (see "Detailed changes")
LOS:
added alle needed TWRP configs
moving kernel modules like WiFi to /system
sepolicy updates for rild
.... and more (see "Detailed changes")
Detailed changes:
LOS: this build VS. last build (by jedld, yea 19 pages ... was a long time )
Device tree: github
Kernel: github
.-

For those interested I will also provide SHRP (skyhawk recovery) after some testing and fine tuning ...
Sent from my OnePlus 6T using XDA Labs

Testing and report
Thank You for this Great JOB
---------- Post added at 07:32 PM ---------- Previous post was at 07:10 PM ----------
steadfasterX said:
For those interested I will also provide SHRP (skyhawk recovery) after some testing and fine tuning ...
Sent from my OnePlus 6T using XDA Labs
Click to expand...
Click to collapse
Migration from Lineage Jed for LOS 7.1.2
Recovery 3.3.1.1 Ok
installation Ok
Magisk Ok
Google Apps Ok
Fist Boot Ok
Wifi and sensors Ok
OpenCamera working Perfectly
ROM stable Ok no errors in all files i recomend this release for all users Galaxy Tab T285
Great Job Great ROM.
Hacker.

May I know how do I flash your TWRP build? I am using Odin and I am supposed to flash .tar.md5 file right? Yours is in disc img file and when I try to extract / mount it shows "corrupted file".

nicktsh said:
May I know how do I flash your TWRP build? I am using Odin and I am supposed to flash .tar.md5 file right? Yours is in disc img file and when I try to extract / mount it shows "corrupted file".
Click to expand...
Click to collapse
Ah yea I haven't uploaded the ODIN file yet. Thanks for reminding. You can either wait for that or flash any of the other available TWRP versions for the smt285 which have a ODIN package. Once you have TWRP you can simply flash my img from within TWRP to update .
Sent from my OnePlus 6T using XDA Labs

Great piece of work, very much needed. Thanks Bro.
I wished if volte would have worked, is there any chance!
---------- Post added at 07:24 AM ---------- Previous post was at 06:33 AM ----------
Getting CTSProfile false in Magisk 20.4, any fix ?

रRudra said:
Great piece of work, very much needed. Thanks Bro.
I wished if volte would have worked, is there any chance!
---------- Post added at 07:24 AM ---------- Previous post was at 06:33 AM ----------
Getting CTSProfile false in Magisk 20.4, any fix ?
Click to expand...
Click to collapse
VoLTE is always a pita. So no.
Will check cts profile, should be fixable ..
Sent from my OnePlus 6T using XDA Labs

steadfasterX said:
VoLTE is always a pita. So no.
Will check cts profile, should be fixable ..
Click to expand...
Click to collapse
ctsprofile issue solved, I can share the solution if u need! Thanks

रRudra said:
ctsprofile issue solved, I can share the solution if u need! Thanks
Click to expand...
Click to collapse
Fingerprint .. I just need to add it but if you can share the exact one from stock it saves 2min for me
EDIT: nvm got it.
Sent from my OnePlus 6T using XDA Labs

I recently flash the rom, mobile data to long to open. Thank for this, still finding bugs

Having trouble flashing a custom recovery. Odin doesn't seem to like me. Could anyone help me out?

Installed - works fine but found one annoying bug - lockscreen is not rotating at all - it's only vertical and not want to rotate to horizontal when I rotate device.

how to install this ?
im having error on flashing it through twrp 3.1.1.1 it states error 7

jayrakiztah said:
im having error on flashing it through twrp 3.1.1.1 it states error 7
Click to expand...
Click to collapse
use the latest TWRP linked in the OP.

steadfasterX said:
use the latest TWRP linked in the OP.
Click to expand...
Click to collapse
twrp 3.1.1.1? it is already installed

jayrakiztah said:
twrp 3.1.1.1? it is already installed
Click to expand...
Click to collapse
nope. 3.3.1.1 is the latest and it is linked in the OP
.-

steadfasterX said:
nope. 3.3.1.1 is the latest and it is linked in the OP
.-
Click to expand...
Click to collapse
i flashed your sharp recvoery and it still got an error 7

Development [ROM] [QPR2] [AOSP] [ORIOLE] RisingOS Android Project v1.0 [DISCONTINUED]

Screenshots

Changelogs:
04/21/23
ROM changes:
- Initial Build for Google Pixel (oriole) due to source rebase caused by riceDroid org and source conflicts
Kernel Changes:
- Optimized CPU scheduler and GPU calculation
- Imported I/O scheduler from samsung

Does this rom have any features and customizations?

Any 6 pro version?

0967894983 said:
Does this rom have any features and customizations?
Click to expand...
Click to collapse
Dude literally the first sentence tells you the goal of this rom is customization...

Does this pass safetynet out of the box? Understand if we root its a diferent story, but wanted to check this out of the box if it does. Looks nice, thank you

thanks for ricedroid mr dev. A bug I noticed was the text messages weren't popping up like the headsup display i think its called.
Edit. Oo it seems to be working now the heads-up display. Woo thanks .

Guys, having trouble flashing this, i was on graphene, and extracted all payload contents using payloadgo, fastboot flashed all images, but it was bootlooping.
I dont see a recovary.img extracted to try and flash recovary, any ideas?

In stock Google pixel firmware flashing each img file in cmd works. Well it work for me. Going from a custom ROM u prob have to go stock. And wipe so it doesn't go weird when booted.

cbomb1337 said:
In stock Google pixel firmware flashing each img file in cmd works. Well it work for me. Going from a custom ROM u prob have to go stock. And wipe so it doesn't go weird when booted.
Click to expand...
Click to collapse
OK, from stock, booted into fasboot, using CMD you simply fastbooted each .img file? Did you have to boot into fastbootd at any point? I will give it another whirl, thanks

yeah i installed the rom twice. using fastboot flash xxxx xxxx.img and also flashed this other ricedroid of telegram which worked like fastboot update rom.zip and then went into thats recovery and flashed the rice droid from there. i got a really bad memory though and cant be of alot of help with this. i was just mentioning what i could remember lol. good luck. the dev needs to update the instructions a little. i had the same confusion at first not seeing recovery.img. which is why i tried the telegram ricedroid but at that point in time that one was buggy with sim not working so i flashed this xda one directly over it because that 1 had ricedroid/lineage recovery and easy install process. i have been running this rice droid for the day. it seems pretty good and im quite fussy and tried lots of roms and never really stuck with any due to issues. this 1 had a issue with headsup display working but later on it started working lol. other then that this seems to run fine. i think battery is about the same as stock pixel firmware. from monitoring the drain with 3c toolbox and fkm.
edit dev i see you uploaded a new version. thanks is there a changelog. i will make a bug list in time for you and post it here.
The new update has a app lock nice. Feels real secure. Thanks again.

spida_singh said:
Does this pass safetynet out of the box? Understand if we root its a diferent story, but wanted to check this out of the box if it does. Looks nice, thank you
Click to expand...
Click to collapse
yes it passes safetynet out of the box

spida_singh said:
Guys, having trouble flashing this, i was on graphene, and extracted all payload contents using payloadgo, fastboot flashed all images, but it was bootlooping.
I dont see a recovary.img extracted to try and flash recovary, any ideas?
Click to expand...
Click to collapse
the recovery is under vendor_boot.img, i have updated the installation instruction for reference you can refer to lineage's installation method https://wiki.lineageos.org/devices/oriole/install

Anhlatuananh said:
Any 6 pro version?
Click to expand...
Click to collapse
Sorry i can only build for oriole, i avoid to build on devices i do not own to avoid causing inconvenience to other people.

Bump! ROM has been updated, for changelogs please refer to post#3

dlwlrma123 said:
Bump! ROM has been updated, for changelogs please refer to post#3
Click to expand...
Click to collapse
Does your rom have a feature to customize the size of the pill, and if so, is there a camera delay?
I can't find the download link vendor_boot.img

0967894983 said:
Does your rom have a feature to customize the size of the pill, and if so, is there a camera delay?
I can't find the download link vendor_boot.img
Click to expand...
Click to collapse
I think I saw that in the setting some where. I removed my pill button at the bottom with the settings. Vendor boot image is inside the rom zip then extract the payload.bin file.

Mr dev use should look into James dsp it is the best dsp I have used. I just disable the audio fx one it's plain and crappy I also use this zip file that limits my charging to 90 percent. I'm surprised no 1 has implemented a charging limit using maybe that method. I wonder if we will one day be able to get the old qs icons back. Circle shape and other shapes. They were cool. Also I noticed there's no mod for the battery icons to alter the color like aosp mods has and can't alter the color of text for status bar icons and date and clock. There is background chip tho.

cbomb1337 said:
I think I saw that in the setting some where. I removed my pill button at the bottom with the settings. Vendor boot image is inside the rom zip then extract the payload.bin file.
Click to expand...
Click to collapse
Thanks bro, please guide me more to extract the payload.bin

Better Mobile App

welcome