Database Info

[RECOVERY][OFFICIAL] TWRP 3.3.1-0 for Galaxy A8+ 2018

Team Win Recovery Project
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about doing this to your device
* 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.
*/
{
"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"
}
Disclaimer:
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox TZ Features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
- If you like my work please hit the "Thanks" button to support me. You're also free to donate me via my donation link here in XDA.
What is TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Read more about TWRP here: https://twrp.me/about/
How to flash and setup it completely?
- First, make sure your phone isn't RMM Locked.
- Download Odin3 v3.13.1, Samsung USB Drivers, latest TWRP's tar for your variant, latest no-verity-opt-encrypt zip and RMM Bypass v3 zip.
- Go to Settings App, Developer Options and enable OEM Unlock (If you don't see Developer Setings, go into About phone>Software info and tap "Build number" 10 times to show Developer Options menu).
- Do a backup of all your important data and files in your phone.
- Shutdown the phone. Once it's off, Power it On in Download Mode (Press and hold Power, Vol + and Vol - buttons together)
- Connect your phone in your PC, open Odin3, go in Option section and untick "Auto-reboot". Once that click the "AP" button and select the TWRP tar you downloaded before, then press the "Start" button.
- Once Odin3 finished to flash the recovery (you should see a "PASS" message), force reboot your phone (Press and hold Power and Vol - buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
- Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
- Once it finished go back at the home screen and touch Reboot>Recovery. TWRP should be able to mount your data partition. Now copy the no-verity-opt-encrypt and RMM Bypass zip you downloaded before and flash them (touch Install and select each zip to flash it)
- You're now able to reboot to your OS without re-encrypting /data partition and without RMM Prenormal lock.
Download:
Galaxy A8 2018 (jackpotlte):
https://twrp.me/samsung/samsunggalaxya82018.html
Galaxy A8+ 2018 (jackpot2lte):
https://twrp.me/samsung/samsunggalaxya8plus2018.html
Sources:
Kernel Source Code: https://github.com/devkingsteam/android_kernel_samsung_universal7885/
Device Tree (jackpotlte): https://github.com/TeamWin/android_device_samsung_jackpotlte
Device Tree (jackpot2lte): https://github.com/TeamWin/android_device_samsung_jackpot2lte
Changelog:
Check Post #2.
A8 2018 Community Telegram Group:
Invite Link
Credits:
- Samsung for kernel source code
- TeamWin for their awesome recovery
- @ananjaser1211 and @McFy for their help and support
- @SaboorTheCool for testing out the recovery
XDA:DevDB Information
TWRP for Galaxy A8+ 2018, Tool/Utility for the Samsung Galaxy A8+ (2018)
Contributors
BlackMesa123
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-05-20
Created 2018-07-18
Last Updated 2019-06-17

Changelog:
Note that this page only includes device-specific changes. For global TWRP changes, go to twrp.me.
20180921 (3.2.3-0)
- Updated kernel source code
- Fixed USB OTG
- Enabled FBE support (general AOSP only, Samsung method is still not supported)
20180730 (3.2.3-0)
- Removed /preload from partitions table
- Added /system_image (raw system partition backup)
- Enabled software encryption support (general AOSP only, Samsung method is still not supported)
20180718 (3.2.2-0)
- First release

Reserved

Plan to do nightlies for TWRP?

SRIHARI_GUY said:
Plan to do nightlies for TWRP?
Click to expand...
Click to collapse
Nope, gonna update it just if omni/A8 sources gets updated

TWRP 3.2.3 released. Enjoy!

Will this work with A8+ oreo?

Bad.Server said:
Will this work with A8+ oreo?
Click to expand...
Click to collapse
TWRP isn't built for a specific OS since it's totally separated from OS, so it works on all of them if there aren't significately changes in bootloader/kernel. Even if it was, mine is compiled with latest Oreo kernel source code and based on omniROM 8.1, so...

I lost mobile network?
Hi all. I have an unlocked A8+. I rooted when I had Nougat. I installed the oreo firmware from Columbia and the phone works great. I like the enhancements. I followed the instructions to install the new twrp. Took a bit but got magisk working and root explorer but had issues with busy box and titanium bkup. No biggie. The issue I had is the when I went to send a text I got an error and then I noticed I had no signal. So I checked and low and behold I had no mobile networks in the connections list. Does anyone have a clue as to why it disappeared? Did I miss something? I tried it 2 times with the same result. And help would be greatly appreciated.
P.S. OEM unlock is enabled as well as USB debugging enabled also.

Really proud to announce my request to became the official TWRP Maintainer for Galaxy A8/A8+ 2018 has been accepted! You can download the new build of TWRP directly from twrp.me now.

BlackMesa123 said:
Really proud to announce my request to became the official TWRP Maintainer for Galaxy A8/A8+ 2018 has been accepted! You can download the new build of TWRP directly from twrp.me now.
Click to expand...
Click to collapse
Good work

Help Flash odin erro
Flash odin file twrp 3.2.3 erro “only official released binaries are allowed to be flashed” help me..

vantanvu0804 said:
Flash odin file twrp 3.2.3 erro “only official released binaries are allowed to be flashed” help me..
Click to expand...
Click to collapse
Please read and follow the RMM State guide linked in OP.

Congrats on getting Official xD

vantanvu0804 said:
Flash odin file twrp 3.2.3 erro “only official released binaries are allowed to be flashed” help me..
Click to expand...
Click to collapse
Same thing happened to me.
had to download and install the whole firmware.
downloaded from this
https://forum.xda-developers.com/galaxy-a8-plus/how-to/pie-a8-pie-a730fxxu4csb9-t3908703
probably happened because I still have RMM lock (can't do anything to unlock) in oreo. Bootloader got unlocked in Pie so I thought i can now flash custom binaries. Turns out, you still can't

Its been a long time since I had this phone, June 2018 when I had my first "A" series phone. Since then, I'm planning to root it right away but reading a bunch of forum saying new security patch that samsung did some tells its worst than frp locked something about rmm locked and they say if it happens, theres no way to fix the device unless you have to wait for 7 days without turning off the phone and stay connected and after a week of waiting the "OEM Unlock" option will now be available. There after, with that option now ticked you can now proceed to the common thing here in xda usually do, which is "FLASHING" after that is "CUSTOMIZING" for us to have a unique device amongst others and also enhancing anything to the very limit can handle, system app we only need without those useless bloatwares...
Flashing, rooting and customizing sure is fun and satisfies our needs but it comes with risk. Even we have same device model flashing custom rom in other but same device can experience bugs and some are not, some will experience less issue and some even worst so that caution about the disclaimer always there and proceeding means you take the risk and if something went wrong you're the one responsible and no one but your self will be the only person to blame so if you have no idea what you're doing just stop for a while.
If you really want to start rooting your phone just like me, all you need to do is read, study and understand every aspect, because in some complicated proceedure, there's no room for error and you'll end up crying with a dead phone...
Few months ago from time to time of visiting xda, I have a positive feeling and also I'm completely aware that I can now flash my A8+ 2018 without a doubt, just a piece of cake!
While reviewing step by step, downloaded everything, preparing for every "what if" then the problem came up...
Well, just a little problem, but that small little problem thing suddenly stop me to proceed.
(Read more)
To fully understand the procedure, it took me time, very long waiting time. Passing almost a year now and I'm still stock with the same phone running also in stock os.
Although it's in the "mid-end" phone, having such as this device for almost a year was long enough to love it, enough to get used to it.
Until now, this mid-end phone with stock Android 8.0.0 official operating system runs impressively very smooth and not a single issue ever experienced and to be honest, it exceeds my expectations but still, there's a limitation and that's the customization. To make it possible, I need privilege access to these "four letters" R O O T.
We all know that with a stock os, accessing root surely not possible, it need the superuser (su) to grant permission to access the root and installing su ofcourse is not just like the ordinary apk that can easily be installed, it needs to be flash manually but not in odin. It will be flash in recovery mode but flashing it there still be impossible because that su.zip file cannot be flashed with the stock recovery, you need to modify the recovery mode... Do you how to mdofy it? Well, if you can, that's good and you will have a unique version of it, but me? No way I can modified it...
So, to those people like me who cannot make a customized recovery, NO WORRIES! good news for us because xda geniuses made us for free, custom recovery like twrp, hurray!
It must be flashed via odin, after flashing twrp you can now flash su and congrats, your done rooting...
How I wish rooting todays device was that easy do...
BUT IT'S NOT!
IT'S GETTING MUCH COMPLICATED NOW...
THANKS TO THE GENIUSES HERE IN THE XDA!
Like what I said, it took me too long to fully understand, long enough to like it a lot that putting lots of apps, games, gig to gig files in my secured folder, dozen of duplicated media apps and multiple accounts, in short "LOTS OF THINGS" and for me all those are important and I can't afford to lose a single file...
In the step by step procedure, when everything was already correct settings and before to click and start the flashing of twrp recovery via odin there's instructed or warning that must not be ignored, something like this:
BE SURE "AUTO-REBOOT" IS NOT CHECKED and then after the successful flashing and see the PASS message, force reboot your phone (Press and hold Power and Vol -+ buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
Not following the "EXCACT" instruction? Well, it still boot hopefully to normal but then if you try to check if the custom recovery is there... SURPRISE! Nothing's new! Just the same old samsung recovery and you just made your newly flashed recovery useless because it will revert back to stock recovery, instantly replace the twrp recovery you've flashed. That's the reason it have to force reboot to recovery mode.
But there's more, if you start the procedure without enabling the OEM Unlocked somehow kick-in the device "enhanced" security and trip the RMM "TO LOCKED" (not locked yet but it will as soon as the device reboot) if that happens, your'e in some kind of trouble now because at that moment the OEM automatically locked meaning the bootloader will also locked and also means NO FLASHING CAN BE MADE and there's no way the OEM to unlocked because the "OEM Unlocked" option in the developer setting will removed and "UNABLE" to access it for exactly 7 days and forcing odin to flash it again without waiting the said time not an option because doing so while OEM is locked will trip next the Factory Reset Protection aka FRP Locked and it's very hassle. Doing it again and again will not help, the 7 days period will only reset 0 so if it happen, just be patient.
Now back to:
BE SURE "AUTO-REBOOT" IS NOT CHECKED
after successfully flashing your custom recovery it will manage to reboot to your new recovery which is twrp (preferably latest)
Next step to do is yet very simple and easy up to the last step of the procedure...
Its been a long time since I had this phone, June 2018 when I had my first "A" series phone. Since then, I'm planning to root it right away but reading a bunch of forum saying new security patch that samsung did some tells its wosrt than frp lovked something about rmm locked and they say if it happens, theres no way to fix the device unless you have to wait for 7 days without turning off the phone and stay connected and after a week of waiting the "OEM Unlock" option will now be available. There after, with that option now ticked you can now proceed to the common thing here in xda usually do, our only and always be our favorite to do... which is "FLASHING" after that is "CUSTOMIZING" for us to have a unique device amongst others and also enhancing anything to the very limit can handle, having an app that we need and removes those useless bloatwares...
Flashing, rooting and customizing sure is fun and satisfies your needs but it comes with risk. Even we have same device model flashing custom rom some device can face bugs some is not, some will experience less issue and some even worst so that caution about the disclaimer always there and proceeding means you take the risk and no one but your self will be the only person to blame so if you have no idea what you're doing just stop for a while.
Like me, if you really want to make it happen, all you need to do is read, study and understand, because in some complicated proceedure, there's no room for error and you'll end up crying with a dead phone...
Few months ago from time to time visiting xda, I have a positive feeling and completely aware that I can now flash my A8+ 2018 without a doubt, just a piece of cake!
While reviewing step by step, downloaded everything, preparing for every "what if" then the problem came up...
Well, just a little problem, but that small little problem thing stops me to proceed.
(Read more)
To fully understand the procedure and , it took me time, very long waiting time. Passing almost a year now and I'm still stock with the same phone running also in stock os.
Although it's in the "mid-end" phone, having such as this device for almost a year was long enough to love it, enough to get used to it.
Until now, this mid-end phone with stock Android 8.0.0 official operating system runs impressively very smooth and not a single issue ever experienced and to be honest, it exceeds my expectations but still, there's a limitation and that's the customization. To make it possible, I need access to these "four letters" R O O T.
Accessing it is not possible, I need the superuser to grant me permission to access the root and su ofcourse is not just like the ordinary apk that can easily be installed, it will be flash, not in odin but recovery but flashing it will not be possible because that su.zip file cannot be flashed with the stock recovery, but custom recovery can like twrp.
It must be flashed via odin, after flashing twrp you can now flash su and congrats, your done rooting...
How I wish rooting todays device was that easy do...
BUT IT'S NOT!
IT'S GETTING MUCH COMPLICATED NOW...
THANKS TO THE GENIUSES HERE IN THE XDA!
Like what I said, it took me too long to fully understand, long enough to like it a lot that putting lots of apps, games, gig to gig files in my secured folder, dozen of duplicated media apps and multiple accounts, in short "LOTS OF THINGS" and for me all those are important and I can't afford to lose a single file...
In the step by step procedure, when everything was already correct settings and before to click and start the flashing of twrp recovery via odin there's instructed or warning that must not be ignored, something like this:
BE SURE "AUTO-REBOOT" IS NOT CHECKED and then after the successful flashing and see the PASS message, force reboot your phone (Press and hold Power and Vol -+ buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
Not following the "EXCACT" instruction? Well, it still boot hopefully to normal but then if you try to check if the custom recovery is there... SURPRISE! Nothing's new! Just the same old samsung recovery and you just made your newly flashed recovery useless because it will revert back to stock recovery, instantly replace the twrp recovery you've flashed. That's the reason it have to force reboot to recovery mode.
But there's more, if you start the procedure without enabling the OEM Unlocked somehow kick-in the device "enhanced" security and trip the RMM "TO LOCKED" (not locked yet but it will as soon as the device reboot) if that happens, your'e in some kind of trouble now because at that moment the OEM automatically locked meaning the bootloader will also locked and also means NO FLASHING CAN BE MADE and there's no way the OEM to unlocked because the "OEM Unlocked" option in the developer setting will removed and "UNABLE" to access it for exactly 7 days and forcing odin to flash it again without waiting the said time not an option because doing so while OEM is locked will trip next the Factory Reset Protection aka FRP Locked and it's very hassle. Doing it again and again will not help, the 7 days period will only reset 0 so if it happen, just be patient.
Now back to:
BE SURE "AUTO-REBOOT" IS NOT CHECKED
after successfully flashing your custom recovery it will manage to reboot to your new recovery which is twrp (preferably latest)
***Next step to do is very simple and easy up to the last step of the procedure...
Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
Can do it with a couple of swipes to wipe (format data), reboot to recovery again flash su, flash no-verity and also RMM bypass zip just for sure... after that fun stuff can now be available, flash custom roms, blah.. blah.. etc. Boot normally without worries.
About the:
" ***Next step to do is very simple and easy "(above)
Yet very simple and very easy, that's the actual problem dive-in...
As I've mentioned above about having this device from such time and putting lots of apps, games, gig to gig files in my secured folder, dozen of duplicated media apps and multiple accounts, in short "LOTS OF THINGS"
The next step was about formatting and it's a must thing to do to make it work and using unrooted device is impossible to make NANdroid backup, the 64Gb internal storage were almost full and because of that it makes much harder backing-up...
Any advise?
Please help...

@BlackMesa123, please build latest twrp for A8 star, source https://github.com/sabpprook/android_device_samsung_astarqlte

mark0021 said:
bla bla bla...
Click to expand...
Click to collapse
Well the answer is no of course, if you don't wipe your /data partition it will be unreadable from TWRP, equals you can't flash anything that needs to write data in that partition, like Magisk itself. Was it necessary to write that whole post when all you're asking is just a way to avoid /data partition wiping? You basically blamed the "master XDA devs" (which I feel like I'm part of it, sort-of) because "they made the steps for root so hard". I imagine you know "we" aren't the "bad guys that wanna make you lose your precious time" and if I wrote all those steps to follow in the main post (that you copy-pasted twice in your post, without any sense I'd add since users can read the steps from there instead of reading a 1500 lines post) are there because... they are needed? You even noticed and wrote yourself that if you miss one you break something in the way and you get no TWRP if you don't follow all the steps correctly... Wanna blame someone? Then blame the OEMs that add all those security features instead of blaming people that dedicated their time to bypass those and bring you custom softwares for your phone.

inunxelex said:
@BlackMesa123, please build latest twrp for A8 star, source https://github.com/sabpprook/android_device_samsung_astarqlte
Click to expand...
Click to collapse
Sorry but I'm not interested on that phone (since I don't even own it), ask the device tree maintainer to do that.

pls someone help me. Everytime I install TWRP through odin my entire system wipes, and in TWRP it recognizes as 0mb. How can I install TWRP without wiping the entire phone?

Custom recovery anytime soon?

Any word on whether custom recovery can be available anytime soon for the 4a? Mine arrives in 2 weeks or so and I hope it's available by then.

Crickets... Is this because the device is shipping globally pretty slowly? I figured with a Pixel we'd see this sooner.

With the new security enhancements of android there isnt a custom recovery for android 10 so I doubt there will be one going forward.

It's really unnecessary these days anyhow

Still seems to me like there is a role for custom recovery to play. If the phone won't boot, it's a way to get in and unscrew it or at least do a full backup before any sort of full reset. I do see Pixel 4 has an experimental version for Android 10.

cmstlist said:
Still seems to me like there is a role for custom recovery to play. If the phone won't boot, it's a way to get in and unscrew it or at least do a full backup before any sort of full reset. I do see Pixel 4 has an experimental version for Android 10.
Click to expand...
Click to collapse
Agree - the ability to do a full backup on the device and restore it is a nice-to-have, and an unofficial version does exist for A10 Pixel 4.
That said, the September update is probably the last update of A10 for this device.

That backup is fully available function of adb
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
But based on this I will admit, when it's not creating problems twrp can be quite convenient and simplify many processes. I'm building it now, will post soon™

It's going to be an adjustment having to flash ROMs through ADB/fastboot. I've kept my 2xl up to date solely through TWRP for months.
Gonna have to dust off my computer!

EDIT: oops double posted

xstefen said:
That backup is fully available function of adb
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
But based on this I will admit, when it's not creating problems twrp can be quite convenient and simplify many processes. I'm building it now, will post soon™
Click to expand...
Click to collapse
In my experience, adb backup can have unpredictable results. Plus if I need to unscrew a non booting device, I can't get into adb without a recovery. Glad to hear you are working on a build! My 4a should arrive in a week or two and I can test it eventually.

xstefen said:
That backup is fully available function of adb
https://9to5google.com/2017/11/04/how-to-backup-restore-android-device-data-android-basics/
But based on this I will admit, when it's not creating problems twrp can be quite convenient and simplify many processes. I'm building it now, will post soon™
Click to expand...
Click to collapse
Any luck? ?

Well my Pixel arrived (Canada). I guess no recovery available for now. Hoping that with increased global distribution of the 4a as of this month, we'll see dev interest pick up.

Flashing through ADB isn't so bad. Just got DU flashed without a hitch

For me the primary benefit of a recovery is ability to extract data from a non bootable device. Gives the ability to recover from a flashing disaster.

xstefen said:
I will admit, when it's not creating problems twrp can be quite convenient and simplify many processes. I'm building it now, will post soon™
Click to expand...
Click to collapse
Any updates? ?

As mentioned previously, the unofficial TWRP does work in fact for Android 10 because I tested it with a backup from one device and then did a restore to another device and they were both identical:
TWRP 3.7.0-12 for Sunfish[Testing]
[RECOVERY] TWRP 3.7.0-12 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
forum.xda-developers.com
*You just need to flash it with a compatible kernel - this guide is a very good how to:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com

Question Issues with SM-A125M

I have a SM-A125M that I'm trying to use with Visible. The officially supported device is the SM-A125U. This one seems to work on the network (download speed is even good), except for VoLTE and texts. These work very strangely. They will work for a short time after a reboot or turning airplane mode on then off. Then they both fail to work.
Any suggestions? I'm wondering if I can flash the CSC from the U variant and maybe that will help? The M and U variants seem to be identical hardware wise (the U variant actually seems to even physically have 2 sim slots on the motherboard, from the pictures I've seen). Maybe I can flash the U firmware on it? How likely is it that I permanently brick it if I do that? What can I look at to make sure that I could try that without permanently bricking it (as long as I can recover it by some means, I'm fine)? Or maybe you have another idea?

Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about features included
* before flashing it! YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
Maybe flash a a125u ROM at www.samfw.com . In most of the time you can still boot into download mode and recover to a a125m ROM in case anything is wrong.

Yeah, I was considering doing just that. I figured as long as it wasn't likely to nuke the bootloader, I'd probably be OK. I'll give it a try and report back.

So, I just gave that a try. It says:
CADDIER_ID: TPA
Only official released binaries are allowed to be flashed: pit
Click to expand...
Click to collapse
Odd, since I unlocked the bootloader. I'm wondering if maybe this post is helpful: https://forum.xda-developers.com/t/...d-binaries-are-allowed-to-be-flashed.3893592/
In particular:
You must have forgot to flash the RMM fix. You either have to flash the RMM disabler or flash a custom Kernel that disables it that way before the first reboot after flashing TWRP. It's a new safety feature Samsung has introduced that locks the device after anything gets flashed or modified. Unfortunately, your only option is to re-odin stock files and then wait 7 days again for OEM unlock to appear.
After you get TWRP flashed again, mke sure you flash the fix or a custom Kernel.
Click to expand...
Click to collapse
So, maybe I just need to wait? Or maybe i just need to wait for TWRP to become available for this device before I can try this.

[ROM][UNOFFICIAL][12.1] StagOS [instantnoodle]

Disclaimer
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM 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.
Click to expand...
Click to collapse
Hello,
Let me share with you my unofficial StagOS build. More informations on the rom on their website.
Don't expect regular updates and full support until the official StagOS comes out, as i do it on my free time for my personal use.
Instructions & Prerequisites.
Read documentation before doing anything
adb and fastboot, platform-tools
Bootloader unlocked
Be on the latest OOS 11 firmware. You can try from a different firmware version but i can't guarantee it will work.
Follow the installation guide carefully, the instructions work with A12.1 also
If you need Gapps, check the Gapps section in Lineage documentation before doing anything
Root : TRY AT YOUR OWN RISK. You may patch the boot.img from the Google Drive folder with Magisk
Downloads.
ROM : need some fixes after bug report
Recovery : Lineage recovery
Credits to StagOS founder @pranavasri !
Sources.
Kernel tree : Kernel source
Hardware tree : android_hardware_oneplus Source
Device trees :device_oneplus_sm8250-common
android_device_oneplus_instantnoodle
Vendor tree : android_vendor_oneplus
Android version : 12.1
Security patch level : June, 2022

Oneplus 8 Pro build is almost ready, Oneplus 8 will follow soon
Thanks to @Rustii2022 for his alert.

res2

Neil_Armstrong_ said:
I haven't tested the build yet
Click to expand...
Click to collapse
Do Not install this... theres a couple of errors and even after fixing them it doesnt boot..
that old error from spark/blaze (error : expect oneplus 8 but device is instanoodle)
fixed that the same way you used to fix it.. BUT..
recovery does NOT work AND
Does NOT boot ...
you will need to fastboot into bootloader and choose another recovery to help load another ROM ..
waiting to hear back from the dev on telegram to see if he wants me to log what i can..

[ROM][UNOFFICIAL][11][ARM64] LineageOS 18.1 for Amazon Fire HD 10 (maverick/9th gen)

{
"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"
}
Disclaimer
Code:
/*
* Your warranty is... still valid?
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are the one choosing to make these modifications.
*/
IMPORTANT
This ROM is only for the Amazon Fire HD 10 2019 (maverick) Do not try to flash it on any other device.
This ROM requires the temporary bootloader unlock found here. Read the instructions carefully and come back once you have a working temporary unlock.
This thread will be updated should another unlock method be available.
This ROM requires that you be on the 7.3.1.0 launch firmware. If you have temp unlocked your device, you should already be on this firmware.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
This is a custom build of LineageOS for the Amazon Fire HD 10 9th generation (maverick) which is 64-bit, allowing you to run 64-bit applications and benefit from better performance, unlike the stock OS which is 32-bit.
Working
Audio
Bluetooth
Camera
DRM L1 (playback not tested)
DT2W (double-tap-to-wake)
Media Playback (Hardware OMX)
Sensors
SDcard
USB (MTP, PTP, etc)
Wi-Fi
Not Working
SELinux is Permissive
Deep Sleep (?)
Hotspot
Notes
The stock gallery app has some issues playing media which is higher than 1920x1080, if you face this issue please try a third-party gallery app.
If you have flashed GApps, you should wait for the device to "settle" after completing setup wizard. During the first 10-ish minutes of use, the tablet could heavily lag and freeze.
Since this is a beta build, you should be prepared to face bugs and issues, along with possible stutters and lags.
You are free to use any recovery to flash this ROM, however, I recommend using the attached recovery (Lineage Recovery) to flash this ROM in order to avoid any potential issues.
How to Flash?
Spoiler: Flashing Instructions
It's important to note that you will have to boot your device with mtkclient every time you reboot!
First of all, boot the device into fastboot mode. Once you see something like => FASTBOOT mode... appear on your devices display, you can flash the Lineage Recovery image with the following fastboot command:
Code:
fastboot flash recovery lineage-18.1-XXXXXXXX-UNOFFICIAL-maverick-recovery.img
fastboot reboot recovery
This flashes the custom recovery to the devices recoverypartition, and then tells it to reboot into recovery mode.
To make sure the device boots into recovery upon the next reboot, hold the volume up button on the device after sending the preloader again with mtkclient.
DO NOT let the device boot back into FireOS at this point, as it will flash the old recovery back to the device, and you will need to start from the beginning again.
The unlocked LK indicates which mode the device will boot into, you should see something like lk boot mode = 2 on the devices display, meaning it is booting into recovery mode.
Once in Lineage Recovery, tap on "Apply Update", and then tap on "Apply from ADB". There are also options to apply updates from external storage if you wish.
Now, it's time to actually install the ROM. We are going to sideload the Lineage ZIP to our device using adb with the following command.
Code:
adb sideload lineage-18.1-XXXXXXXX-UNOFFICIAL-maverick.zip
At this point, all you need to do now is wait for the flashing process to complete.
Once finished, you will be brought back to the apply update menu. Simply press the back button to go back to the main menu.
Now, tap on factory reset and tap on the option Format data/factory reset. This is going to erase all of the old FireOS userdata from the device.
If you do not wish to install GApps, skip to the finishing up process below the GApps flashing instructions.
Optional: Flashing GApps
To install Google Services to your new ROM, you will want to start by downloading the recommended GApps package (see Downloads section).
Once downloaded, you can follow a similar process that you did for installing the ROM ZIP.
Tap on "Apply Update" again, and "Apply from ADB".
Once you have done that, you can sideload the GApps package with the following command:
Code:
adb sideload MindTheGapps-11.0.0-arm64-XXXXXXXX_XXXXXX.zip
If you wish to install other addons (e.g. Magisk), repeat the same steps, substituting the GApps package file name with the Magisk zip file name.
Finishing Up
Once you have done everything you need to do in Lineage Recovery, it's time to boot into the new ROM.
It's important to note that the reboot system now option does not work correctly, so follow these steps to workaround it.
Tap on Advanced, and then tap on Reboot to bootloader.
Once you see => FASTBOOT mode... on the devices display once again, type the following fastboot command to reboot.
Code:
fastboot reboot
After a short while, you should see the LineageOS boot animation on your device. First boot usually takes 5-10 minutes, especially if you have installed Google Services.
Wait for the device to boot and you should be presented with the setup wizard. Enjoy!
Downloads
ROM
Recommended GApps
Source Code
Device
Kernel
Vendor

Screenshots attached below.

Reserved #3

Amazing job.

@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)

JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
The device tree is currently private for whatever reason. I will let bengris know through Telegram.

JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
Hey, currently the new device tree is not open source yet, I will make it open source once I fix the remaining issues (mainly getting SELinux Enforcing). Kernel tree is open due to the GPL license.

Hi there, I'm having issue with this ROM as it is bootlooping after install with TWRP or provided LOS Recovery. For what it's worth, I have a maverick that is permanently bootloader unlocked, so as far as I know I do not have to use mtkclient. I'm not sure if this is a hard requirement. Flashing via TWRP or provided LOS recovery does not work for me. Am I missing something?

I will pay $1,000 or more to anyone who can open bootloader to the new systems amazon

jasonjohn95 said:
Hi there, I'm having issue with this ROM as it is bootlooping after install with TWRP or provided LOS Recovery. For what it's worth, I have a maverick that is permanently bootloader unlocked, so as far as I know I do not have to use mtkclient. I'm not sure if this is a hard requirement. Flashing via TWRP or provided LOS recovery does not work for me. Am I missing something?
Click to expand...
Click to collapse
Hello, interesting to say you have "a maverick that is permanently bootloader unlocked", is it an engineering unit? Could you provide more details such as the firmware version you are on? Also, which kind of boot loop, does it at least get past the Amazon logo or just reboot? Or do you see LineageOS boot animation which never ends?

JJ2017 said:
@bengris32 - great to see this post, thanks!
I see you've put vendor and kernel on github already.
Is there a maverick device tree you could recommend for a lineage self-build? (Maybe: https://github.com/PQEnablers/android_device_amazon_maverick ?)
Click to expand...
Click to collapse
FYI, I have open sourced the device tree, so feel free to build it yourself! You SHOULD be able to compile a booting build this time, just make sure to sync the device tree, kernel tree and vendor tree.

Hello, how are you? I have a question regarding the installation of the ROM. If I have the OS in the Fire OS 7.3.2.7 version, can I still install the ROM without any problem? Greetings from Chile, sorry for use google translate

ＤＥＭＯＮ said:
Hello, how are you? I have a question regarding the installation of the ROM. If I have the OS in the Fire OS 7.3.2.7 version, can I still install the ROM without any problem? Greetings from Chile, sorry for use google translate
Click to expand...
Click to collapse
no, you have to be on 7.3.1.0. Only the first 3-4 months of release of the device was rootable and available to any exploits. Before jan 2020.... If your was bought before that, you might be able to downgrade...

Michajin said:
no, you have to be on 7.3.1.0. Only the first 3-4 months of release of the device was rootable and available to any exploits. Before jan 2020.... If your was bought before that, you might be able to downgrade...
Click to expand...
Click to collapse
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?

ＤＥＭＯＮ said:
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?
Click to expand...
Click to collapse
Depends on when you bought your tablet.... When released it had a exploit. The bootrom was available to do some things..... If the device was released from amazon after about jan 2020, you are probably out of luck. The biggest problem here is even if you have the root access, you have to plug it in to a PC and run the script to get it to boot every time. It is still partially locked down.... Temp unlock (and temp root, which you have to run after boot every time) means you can get access but have to run the script every time....

ＤＥＭＯＮ said:
I have installed many ROMs in the past, it is my first time downgrading one of these tablets, as if that were not enough, I barely understand the tutorial, it is that I have never used mtkclient and I do not understand the "temporary bootloader unlock" please... Can you help me?
Click to expand...
Click to collapse
that being said, i hope you have updates disabled, because there might be another root option coming.

bengris32 said:
Hello, interesting to say you have "a maverick that is permanently bootloader unlocked", is it an engineering unit? Could you provide more details such as the firmware version you are on? Also, which kind of boot loop, does it at least get past the Amazon logo or just reboot? Or do you see LineageOS boot animation which never ends?
Click to expand...
Click to collapse
I'm not sure exactly what you're looking for (or how to find it on the current ArrowOS 13 build I'm running), so I'm attaching my entire getprop dump. Sorry!
The Maverick I have is a retail Maverick, but has been bootloader unlocked by "official" means for development as I am an Amazon employee/engineer on some of their Android products, so I guess I'm cheating on that front
The device will get to the Amazon logo, and then reboot after some time back again to the Amazon logo. I am able to boot into recovery with the vol+ key.
Another thing that might be an issue, I failed to check if I was originally on 7.3.1.0 before flashing, which could be the cause of the issues...oops

Michajin said:
Depends on when you bought your tablet.... When released it had a exploit. The bootrom was available to do some things..... If the device was released from amazon after about jan 2020, you are probably out of luck. The biggest problem here is even if you have the root access, you have to plug it in to a PC and run the script to get it to boot every time. It is still partially locked down.... Temp unlock (and temp root, which you have to run after boot every time) means you can get access but have to run the script every time....
Click to expand...
Click to collapse
Thank you very much for your answers, I don't know when I bought the Tablet, I forgot, but I imagine that it is possible to downgrade to Fire OS 7.3.1.0 in some way which I don't know, apart from I don't understand the tutorials that I found on XDA, I really have 2 days and my head hurts a lot because I do not understand the explanations of the users, if there was even the slightest possibility that you could contact me and tell me step by step what I should do and I will show you with screenshots how I progress and do everything to have a guide, I promise to pay you if I succeed in installing this ROM by PayPal

jasonjohn95 said:
I'm not sure exactly what you're looking for (or how to find it on the current ArrowOS 13 build I'm running), so I'm attaching my entire getprop dump. Sorry!
The Maverick I have is a retail Maverick, but has been bootloader unlocked by "official" means for development as I am an Amazon employee/engineer on some of their Android products, so I guess I'm cheating on that front
The device will get to the Amazon logo, and then reboot after some time back again to the Amazon logo. I am able to boot into recovery with the vol+ key.
Another thing that might be an issue, I failed to check if I was originally on 7.3.1.0 before flashing, which could be the cause of the issues...oops
Click to expand...
Click to collapse
Let's try to dump pstore from the device when it's trying to boot then.
Wait for the device to reboot after being on the amazon logo, immediately on the next boot up, go into recovery mode. Then, enable ADB.
You can dump pstore with the following adb command (adbd should run as root in recovery):
adb pull /sys/fs/pstore
Hopefully there should be some logs in there which you can attach here, if not, keep retrying until you get something in there. If you are 100% nothing is being dumped to pstore, just let me know.
As a side note, I am using the kernel source and blobs from the 7.3.2.7 firmware, so I'm not sure why it's not seeming to boot on later firmware.

bengris32 said:
FYI, I have open sourced the device tree, so feel free to build it yourself! You SHOULD be able to compile a booting build this time, just make sure to sync the device tree, kernel tree and vendor tree.
Click to expand...
Click to collapse
It works!
Completed a Lineage build using the info on "amazon-mt8183-devs" repo - now installed & working fine.
Many Thanks