Develop Bugs

Why bother unlocking and rooting?

Hi,
Please help me understand why I would bother unlocking and rooting my Pixel XL when there isn't an custom recoveries available thus no options for custom roms.
In the past I've always rooted for custom roms and especially for the option to use my hot spot on my unlimited data plan.
Is everyone basically just waiting for custom recovery to become available?
I'm just trying to figure out if I should bother unlocking and rooting now or if I should wait for custom recovery.
and please, if I have no idea what i'm talking about please correct me.
I never thought I would see the day a google phone would come with a locked bootloader regardless of who the vendor it.
Thanks
Ken

Kc0r8y said:
Hi,
Please help me understand why I would bother unlocking and rooting my Pixel XL when there isn't an custom recoveries available thus no options for custom roms.
In the past I've always rooted for custom roms and especially for the option to use my hot spot on my unlimited data plan.
Is everyone basically just waiting for custom recovery to become available?
I'm just trying to figure out if I should bother unlocking and rooting now or if I should wait for custom recovery.
and please, if I have no idea what i'm talking about please correct me.
I never thought I would see the day a google phone would come with a locked bootloader regardless of who the vendor it.
Thanks
Ken
Click to expand...
Click to collapse
It's simple, there's still root and many other editions that can be done with an unlocked bootloader and root. If you want details by details then you should do some research. Maybe drop by the themes and app section

TechBSwift said:
It's simple, there's still root and many other editions that can be done with an unlocked bootloader and root. If you want details by details then you should do some research. Maybe drop by the themes and app section
Click to expand...
Click to collapse
No, I'm not looking for detail, by detail. I'm just asking high level, what is the benefit of an unlocked bootloader and root without custom recovery. At this point is it just a few custom apps?

Actually I'm pretty sure it makes him the coolest cat in town ?

Even if nothing else I'll root just to be able to switch to IOS emojis from those godawful Android emojis. But once recoveries and ROMs come out I'll be back to being a flashaholic.

Kc0r8y said:
Hi,
Please help me understand why I would bother unlocking and rooting my Pixel XL when there isn't an custom recoveries available thus no options for custom roms.
In the past I've always rooted for custom roms and especially for the option to use my hot spot on my unlimited data plan.
Is everyone basically just waiting for custom recovery to become available?
I'm just trying to figure out if I should bother unlocking and rooting now or if I should wait for custom recovery.
and please, if I have no idea what i'm talking about please correct me.
I never thought I would see the day a google phone would come with a locked bootloader regardless of who the vendor it.
Thanks
Ken
Click to expand...
Click to collapse
Custom kernal (elementalX) that enables amongst other things ...
Swipe to wake / sleep feature
High brightness mode .... Excellent when outdoors
Root... Gives ability to use apps that otherwise don't work, eg skvolex Call recorder

Thank you everyone. I really appreciate the explanation.

Don't forget that if you don't unlock your bootloader now, assuming you are on VZW, you may (most likely) not be able to do so in the future. I didn't want to trust that I could postpone an update (even with auto update turned off), so I unlocked my bootloader. In fact, as I was unlocking, my phone automatically took the first update when it rebooted during my first attempt to unlock the bootloader - even though I had auto update turned off.
I have 3 main desires to change on the phone:
- run custom kernel with swipe to unlock/lock
- enable tethering
- keep Android Pay available.
For now, I have flashed a kernel does swipe to unlock, along with enabling Android Pay while maintaining an unlocked bootloader, and not flashing root. I haven't needed to root to get tethering because of the network switching workaround.
I recognize I'm probably fighting a losing battle, though. Android Pay will probably be patched to recognize unlocked bootloader. And there's a possibility that VZW will adapt its tethering detection to disable the workaround.

jasoraso said:
Don't forget that if you don't unlock your bootloader now, assuming you are on VZW, you may (most likely) not be able to do so in the future. I didn't want to trust that I could postpone an update (even with auto update turned off), so I unlocked my bootloader. In fact, as I was unlocking, my phone automatically took the first update when it rebooted during my first attempt to unlock the bootloader - even though I had auto update turned off.
I have 3 main desires to change on the phone:
- run custom kernel with swipe to unlock/lock
- enable tethering
- keep Android Pay available.
For now, I have flashed a kernel does swipe to unlock, along with enabling Android Pay while maintaining an unlocked bootloader, and not flashing root. I haven't needed to root to get tethering because of the network switching workaround.
I recognize I'm probably fighting a losing battle, though. Android Pay will probably be patched to recognize unlocked bootloader. And there's a possibility that VZW will adapt its tethering detection to disable the workaround.
Click to expand...
Click to collapse
You could always root your phone, add the build.prop setting, and then unroot.

skaforey said:
You could always root your phone, add the build.prop setting, and then unroot.
Click to expand...
Click to collapse
Thanks! As I was typing my reply, I actually thought about doing that. Perhaps the next elemntal kernel update, I'll do that. I don't often tether - usually its when I'm in the car with my kids on a trip and they want to stream some netflix to their chromebooks, and I'm usually driving, and trying to get my wife to do the network switching workaround while I'm driving will be a challenge.

wolfu11 said:
I haven't been impressed with a custom rom in a long time.
Click to expand...
Click to collapse
Same here dude...same here. Towards the end of KitKat was an amazing time for ROMs especially when talking about Slim ROMs and Paranoid Android. I haven't even rooted anything since Lollipop. I just don't have a need for it anymore.

I'll give you an obvious reason to unlock your bootloader right now.
If you wait too long and the exploits are patched out (which google apparently said they will be) then when custom recovery is released for Pixel XL you probably SOL.
If you sit there for a while refusing update waiting for TWRP, why not root now and disable the update notification?
And mods are already out. Look at my notification bar.
{
"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"
}
Sent from my Pixel XL using Tapatalk

skaforey said:
You could always root your phone, add the build.prop setting, and then unroot.
Click to expand...
Click to collapse
I thought that once you unroot, then reboot, build.prop will get overwritten and all your changes will be lost. I am looking to do this for enabling wireless display as well.

Ambient Display
Audio Mods
Touch to wake
Sleep to wake
Camera Mods
Emojis
Themes
Kernels
Just to name a few off the top of my head. I am only on day 1 with pixel but if i keep it will get rooted/rommed and modded. Take full advantage of an unlocked phone. No point in getting if you just use like a normal device imo

oneandroidnut said:
Ambient Display
Audio Mods
Touch to wake
Sleep to wake
Camera Mods
Emojis
Themes
Kernels
Just to name a few off the top of my head. I am only on day 1 with pixel but if i keep it will get rooted/rommed and modded. Take full advantage of an unlocked phone. No point in getting if you just use like a normal device imo
Click to expand...
Click to collapse
Thanks for your feedback! I am now unlocked and rooted!

marcjc said:
I thought that once you unroot, then reboot, build.prop will get overwritten and all your changes will be lost. I am looking to do this for enabling wireless display as well.
Click to expand...
Click to collapse
Just to update anyone who may be interested. I rooted, made my changes, then unrooted, rebooted a whole bunch of times and my changes survived unrooting and rebooting.

Kc0r8y said:
Thanks for your feedback! I am now unlocked and rooted!
Click to expand...
Click to collapse
Don't forget custom kernels to increase the speed of the 821 CPU. Out of the box, the CPU is clocked down to the 820 level. With a little over clocking we can experience the full potential of the 821.

Thread cleaned.
Folks, keep the thread on topic and post in accordance with the forum rules you agreed to when you joined XDA.
Cheers,
Magnum_Enforcer
FSM

HTC 10 *One Click Root* Oreo 8.0.0 & All android version

HTC 10 *ONE CLICK ROOT*
ANDROID OREO & ALL VERSION
VIDEO DEMOSTRATION
youtu.be/Y00fzX9Ok4g
BOOTLOADER MUST BE UNLOCKED
AND USB DEBUGGING ENABLED
Download File:
{
"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"
}
HTC-10_ONE-CLICK-ROOT.exe
Thanks to Magisk and Twrp
Celular.Doctor

I will test this for other users, is this MAGISK or SuperSU?

GROOVYJOSHCLARK said:
I will test this for other users, is this MAGISK or SuperSU?
Click to expand...
Click to collapse
It's magisk

stefan1234566789 said:
It's magisk
Click to expand...
Click to collapse
Thanks, I hate magisk, I am a SuperSU guy but I have tested it for others and works

GROOVYJOSHCLARK said:
Thanks, I hate magisk, I am a SuperSU guy but I have tested it for others and works
Click to expand...
Click to collapse
I'm curious, why do you hate magisk? What's it's downside compared to SuperSU?

jabia said:
I'm curious, why do you hate magisk? What's it's downside compared to SuperSU?
Click to expand...
Click to collapse
Loss of ROOT, sound issues with certain AOSP ROMs, buggy interface, continual root permissions denied when set to allowed, ETC. The list goes on and on, but I am NOT saying I will never return to MAGISK as it is great for things like Pay and hiding root. I just cannot use it nor rely on it until it is stable without issues. I run numerous production scripts and remote calls (for work and personally for backups) throughout the night that ALL rely heavily on ROOT, without ROOT, they fail and cannot move onto the next steps. I cannot have these processes fail by losing root, and as of now, MAGISK lost root 5 out of the 10 nights when I test MAGISK. I have tried every version, including the latest and there are still issues with stability.
Again, once these are worked out and once it is stable, I will most definitely be testing it for daily use but it is no where near ready yet.
I should not have said I HATE it, that was the wrong wording and not my intended wording. Readers may see this and get the wrong impression og MAGISK. I should have said, I cannot use it until its stable, so I apologize for that and to the devs of MAGISK, it is not my intention to bad mouth MAGISK. Its just not ready yet for daily use for what I need it for.

GROOVYJOSHCLARK said:
Loss of ROOT, sound issues with certain AOSP ROMs, buggy interface, continual root permissions denied when set to allowed, ETC. The list goes on and on, but I am NOT saying I will never return to MAGISK as it is great for things like Pay and hiding root. I just cannot use it nor rely on it until it is stable without issues. I run numerous production scripts and remote calls (for work and personally for backups) throughout the night that ALL rely heavily on ROOT, without ROOT, they fail and cannot move onto the next steps. I cannot have these processes fail by losing root, and as of now, MAGISK lost root 5 out of the 10 nights when I test MAGISK. I have tried every version, including the latest and there are still issues with stability.
Again, once these are worked out and once it is stable, I will most definitely be testing it for daily use but it is no where near ready yet.
I should not have said I HATE it, that was the wrong wording and not my intended wording. Readers may see this and get the wrong impression og MAGISK. I should have said, I cannot use it until its stable, so I apologize for that and to the devs of MAGISK, it is not my intention to bad mouth MAGISK. Its just not ready yet for daily use for what I need it for.
Click to expand...
Click to collapse
That's weird. I haven't encountered any of these problems. I have used Magisk on RR, LOS, Viper and Leedroid without any problem.
If I'm not mistaken developer of Magisk owns a HTC 10 as daily driver and I thought HTC 10 is the most supported device for using Magisk.

Sir-Shadow said:
That's weird. I haven't encountered any of these problems. I have used Magisk on RR, LOS, Viper and Leedroid without any problem.
If I'm not mistaken developer of Magisk owns a HTC 10 as daily driver and I thought HTC 10 is the most supported device for using Magisk.
Click to expand...
Click to collapse
That may be very true for sense based ROMs but entirely not true for any AOSP ROMs. It's riddled with bugs for AOSP, I don't use any sense based ROMs as my DD but I do test them for others.
Magisk loses root for AOSP users (and not just myself) many others have reported the same (again in AOSP), the audio issues were also ruled to magisk (again may only be on AOSP). So I only ever recommend SuperSU to AOSP users until magisk issues are working on AOSP. Again I am NOT saying root does with MAGISK but it does LOSE root over time so its possible you never noticed it as an issue. It is definitely an issue. You can read about it in the PF forums, or RR forums (basically the most used AOSP forums for the HTC10), its all over the forums.
sent from my HTC 10 droid running AOSP ***note do not PM me, I do not check PM's ever, instead ping me on the forums***

test
works well on htc10 3.16.400.3

GROOVYJOSHCLARK said:
Loss of ROOT, sound issues with certain AOSP ROMs, buggy interface, continual root permissions denied when set to allowed, ETC. The list goes on and on, but I am NOT saying I will never return to MAGISK as it is great for things like Pay and hiding root. I just cannot use it nor rely on it until it is stable without issues. I run numerous production scripts and remote calls (for work and personally for backups) throughout the night that ALL rely heavily on ROOT, without ROOT, they fail and cannot move onto the next steps. I cannot have these processes fail by losing root, and as of now, MAGISK lost root 5 out of the 10 nights when I test MAGISK. I have tried every version, including the latest and there are still issues with stability.
Again, once these are worked out and once it is stable, I will most definitely be testing it for daily use but it is no where near ready yet.
I should not have said I HATE it, that was the wrong wording and not my intended wording. Readers may see this and get the wrong impression og MAGISK. I should have said, I cannot use it until its stable, so I apologize for that and to the devs of MAGISK, it is not my intention to bad mouth MAGISK. Its just not ready yet for daily use for what I need it for.
Click to expand...
Click to collapse
its simple, i use magisk becouse supersu fail in last new versions of android, and as we know chainfire lives supersu... magisk works perfect on android oreo phones, like htc 10 but supersu is fully of bugs. its a fact, chainfire say it, supersu is dead.

hernankano said:
its simple, i use magisk becouse supersu fail in last new versions of android, and as we know chainfire lives supersu... magisk works perfect on android oreo phones, like htc 10 but supersu is fully of bugs. its a fact, chainfire say it, supersu is dead.
Click to expand...
Click to collapse
That's really interesting, I have found the complete exact opposite results. I ONLY use SuperSU, including Oreo 8.1 (AOSP). This could very well be the opposite with Sense OS but not with AOSP and derivatives. I don't run Sense OS in any form other than to test things for other users so my phone is only AOSP, take what I'm saying with a grain of salt if you're a stock Sense user.
sent from my HTC 10 droid running AOSP ***note do not PM me, I do not check PM's ever, instead ping me on the forums***

Did you mean AOSP 8.1 ROM for HTC 10? Is so, which ROM is it? Is it stable enough for daily drive? Thanks.
GROOVYJOSHCLARK said:
That's really interesting, I have found the complete exact opposite results. I ONLY use SuperSU, including Oreo 8.1 (AOSP). This could very well be the opposite with Sense OS but not with AOSP and derivatives. I don't run Sense OS in any form other than to test things for other users so my phone is only AOSP, take what I'm saying with a grain of salt if you're a stock Sense user.
sent from my HTC 10 droid running AOSP ***note do not PM me, I do not check PM's ever, instead ping me on the forums***
Click to expand...
Click to collapse
---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------
Did you mean AOSP 8.1 for 10? If so, which ROM is it? Is it stable enough for daily drive? Thanks.
GROOVYJOSHCLARK said:
That's really interesting, I have found the complete exact opposite results. I ONLY use SuperSU, including Oreo 8.1 (AOSP). This could very well be the opposite with Sense OS but not with AOSP and derivatives. I don't run Sense OS in any form other than to test things for other users so my phone is only AOSP, take what I'm saying with a grain of salt if you're a stock Sense user.
sent from my HTC 10 droid running AOSP ***note do not PM me, I do not check PM's ever, instead ping me on the forums***
Click to expand...
Click to collapse

Steinard said:
Did you mean AOSP 8.1 ROM for HTC 10? Is so, which ROM is it? Is it stable enough for daily drive? Thanks.
---------- Post added at 07:38 PM ---------- Previous post was at 07:36 PM ----------
Did you mean AOSP 8.1 for 10? If so, which ROM is it? Is it stable enough for daily drive? Thanks.
Click to expand...
Click to collapse
I actually meant AOSP in general (including 8.1 Oreo). AOSP 8.0/1 are still early on in development but try out AOSiP 8.1 or PureFusion 8 if you're itching to test it.
AOSiP works pretty well with most things including ril (cell) but there's an open issue with the main speaker. I used it for my DD for a few days and was pretty happy with it, I only rolled back to ReserectionRemix (N) because I like to watch/listen to Netflix during my workday so no sound killed that idea.
I used PureFusion (8.0) as my DD for a good month straight when it was first released and was really happy with it, I only stopped using PF because the devs are actively working on 8.1 PF so 8 development was moved into 8.1. I will return to one or both of them in time once the bugs are worked out.

Thanks for the quick answer. I guess I will also give PF a try when the bugs are addressed. At the moment I plan to stick to stock Oreo for a while even thoogh the battery life is realy not that great
GROOVYJOSHCLARK said:
I actually meant AOSP in general (including 8.1 Oreo). AOSP 8.0/1 are still early on in development but try out AOSiP 8.1 or PureFusion 8 if you're itching to test it.
AOSiP works pretty well with most things including ril (cell) but there's an open issue with the main speaker. I used it for my DD for a few days and was pretty happy with it, I only rolled back to ReserectionRemix (N) because I like to watch/listen to Netflix during my workday so no sound killed that idea.
I used PureFusion (8.0) as my DD for a good month straight when it was first released and was really happy with it, I only stopped using PF because the devs are actively working on 8.1 PF so 8 development was moved into 8.1. I will return to one or both of them in time once the bugs are worked out.
Click to expand...
Click to collapse

Steinard said:
Thanks for the quick answer. I guess I will also give PF a try when the bugs are addressed. At the moment I plan to stick to stock Oreo for a while even thoogh the battery life is realy not that great
Click to expand...
Click to collapse
I hear ya on the battery life. If you wanted to taste AOSP O either option would work AOSiP or PF.
Personally I'm using RR (N OS) on (MM firmware) until the buggies are sorted. This setup works pretty good with no issues and is my DD I fall back to when I need stability. ReserectionRemix Nougat is pretty flawless in my opinion without the need to tweak or use any aftermarket kernels.
sent from my HTC 10 droid running AOSP ***note do not PM me, I do not check PM's ever, instead ping me on the forums***

This does not work on Verizon. Only installed root checker pro. Had to manually fastboot flash twrp, then flashed latest Magisk.

I can't Download the exe file
Does it work on 3.16.401.2?
Sent from my [device_name] using XDA-Developers Legacy app

Tried it on US Unlocked model, working fine so far, thanks!

adb service out of date
hi everyone, im getting one message saying "adb service is out of service. killing..." does anyone have any clue?

Fails to work on Unlocked Sprint HTC 10
Cmd "Adb devices" sees the phone, but OneClickRoot can't see it, just says "waiting for device" and error: *something protocol* sorry-its late and I'm frustrated with it.
OneClickRoot did *almost* work, as it installed Root Checker the first time I tried, but then it failed a couple times, saying "adb didn't ack", even if I manually terminated the process in Task Mgr -Win10 latest update PC. It kept killing and restarting and spitting out daemon error msgs. It said it installed TWRP at least once, but I'm not convinced anything has installed correctly.
The most recent fail had me stuck in Download Mode screen with Start Downloading highlighted but all buttons unresponsive. After forced reboot, the device restarted fine, but now OneClickRoot keeps saying device disconnected even though CMD/adb can see it.
Using original HTC cable and the PC USB port that worked fine for unlocking with HTVdev procedure.
This phone has me more than thoroughly annoyed lately. Thanks in advance for any help and input.

[UNOFFICIAL][ROM] LineageOS 15.1 for Galaxy Tab E [SM-T560NU]

{
"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"
}
Hello my fellow SM-T560NU (gtelwifiue) owning friends, I thought I'd share with you my build of LineageOS 15.1.
This build contains the July 5 2019 security patch level. Please leave a thumbs up if this is useful to you.
If you need root, flash Magisk from recovery and install Magisk Manager.
I you wish to install the Google apps, flash opengapps from recovery after first boot (you need to get the ARM version for Android 8.1 nano package is recommended).
Code:
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the warranty
covering your device, it should be assumed that any warranty accompanying your device will
be voided if you tamper with either the system software or the hardware.
Download link: lineage-15.1-20190707-UNOFFICIAL-gtelwifiue.zip
Source: Galaxy-MSM8916 on Github

I have one of these tablets and would love to use it but the custom rom seems to slow it down. It's Android 7. I have TWRP in it but I cannot seem to find a lighter rom to help speed things up. Any thoughts, suggestions?

upyisfar said:
Hello my fellow SM-T560NU (gtelwifiue) owning friends, I thought I'd share with you my build of LineageOS 15.1.
This build contains the April 5 2019 security patch level, and I have not encountered any issues with it so far. Please leave a thumbs up if this is useful to you. I am planning to produce more builds of this ROM in the coming months.
Download link: lineage-15.1-20190409-UNOFFICIAL-gtelwifiue.zip
Source: Galaxy-MSM8916 on Github
Click to expand...
Click to collapse
Appreciate it. I hope you continue to support this tablet of mine ! I've been a fan of LineageOS for awhile !

Build 20190516
Here is a new build of that includes the May 5th 2019 Android security patch level.
lineage-15.1-20190516-UNOFFICIAL-gtelwifiue.zip

Can I install this ROM on a SM-T560 (Wi-Fi) tablet?

davideakc said:
Can I install this ROM on a SM-T560 (Wi-Fi) tablet?
Click to expand...
Click to collapse
Hello, I don't know if you can. This ROM is for devices codenamed gtelwifiue. You should search the forum and find out if the SM-T560 falls under that category.

Zbanded said:
I have one of these tablets and would love to use it but the custom rom seems to slow it down. It's Android 7. I have TWRP in it but I cannot seem to find a lighter rom to help speed things up. Any thoughts, suggestions?
Click to expand...
Click to collapse
Anything older than Nougat will probably suffer from multiple security vulnerabilities. Lineage 15.1 is the only ROM I found that works bug free on my tablet (14.1 has camera issues and 16.0 doesn't wake up when pushing the home button).

upyisfar said:
Anything older than Nougat will probably suffer from multiple security vulnerabilities. Lineage 15.1 is the only ROM I found that works bug free on my tablet (14.1 has camera issues and 16.0 doesn't wake up when pushing the home button).
Click to expand...
Click to collapse
same boat i am in sir
terribly slow with lineage 16

Here is a new build of that includes the June 5th 2019 Android security patch level.
lineage-15.1-20190612-UNOFFICIAL-gtelwifiue.zip

upyisfar said:
Here is a new build of that includes the June 5th 2019 Android security patch level.
Click to expand...
Click to collapse
What is the process after I download the file?
Just open it?
I am new to these kind of updates. Thank you for the post. Trying to get some good lock options on my 560.

tc3500 said:
What is the process after I download the file?
Just open it?
I am new to these kind of updates. Thank you for the post. Trying to get some good lock options on my 560.
Click to expand...
Click to collapse
Hi @tc3500. If you have a previous build of lineage os 15.1 installed you can just flash the new zip in twrp and then reboot. If your tablet is stock, then you need to first root it and then install twrp recovery for the gtelwifiue first. The procedure for doing this is explained in another post on the forum. Please ensure that your model is SM T560NU or else this ROM might not work.

upyisfar said:
Hi @tc3500Please ensure that your model is SM T560NU or else this ROM might not work.
Click to expand...
Click to collapse
I don't have Lineage and have not used TWRP.
But in will search for the thread with the information.
It has been awhile since I rooted a device. But I should be able to.
Thanks very much for your reply. I appreciate it.
.....And my model is exactly that number.
Says it's SM-T560NU. running 7.1.1, last patch 10/1/17.
---------- Post added at 11:54 AM ---------- Previous post was at 11:41 AM ----------
tc3500 said:
.....and my model is exactly that number.
Says it's sm-t560nu. Running 7.1.1, last patch 10/1/17.
Click to expand...
Click to collapse
sm-t560nuueu1cqk2.

tc3500 said:
I don't have Lineage and have not used TWRP.
But in will search for the thread with the information.
It has been awhile since I rooted a device. But I should be able to.
Thanks very much for your reply. I appreciate it.
.....And my model is exactly that number.
Says it's SM-T560NU. running 7.1.1, last patch 10/1/17.
Click to expand...
Click to collapse
From memory, I rooted my tablet by flashing CF-Auto-Root-gtelwifiue-gtelwifiue-smt560nu.zip using Odin (PDA button)on Windows. Can't remember if that gave me twrp or if I had to install it seperately. Hope this helps a bit.
Note: Enable Developer Options: go to Settings -> About device. Tap 7 times on Build number to enable Developer options. Enable OEM unlock and USB debugging options ( Settings -> Developer options )
Note: you will need to have the Samsung USB drivers installed, you can get those by installing the Samsung Kyes software.
Note: Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off)
Backup of my twrp recovery in case you need it.

upyisfar said:
Note: you will need to have the Samsung USB drivers installed, you can get those by installing the Samsung Kyes software.
Click to expand...
Click to collapse
I will download TWRP and the drivers to my laptop.
The other functions are done. Really awesome of you to take your time and reply.

tc3500 said:
I will download TWRP and the drivers to my laptop.
The other functions are done. Really awesome of you to take your time and reply.
Click to expand...
Click to collapse
You're welcome. I hope you succeed at installing LineageOS 15.1 on your tablet. If anything goes wrong, you can download the original firmware for your device from the sammobile.com website and flash using 0din.

upyisfar said:
You're welcome. I hope you succeed at installing LineageOS 15.1 on your tablet. If anything goes wrong, you can download the original firmware for your device from the sammobile.com website and flash using 0din.
Click to expand...
Click to collapse
I have all of the files downloaded to my laptop.
And that took some time. I got a Note 9 last year and I rarely even turn my PC on anymore. So there were many updates and and misc things to attend. Also it is frustratingly slow compared to my phone, haha.
I do need to get CF Root.
But my concern is that my Tab E is a Wifi model. And I am not sure how to verify if it will accept this modification.
It is definitely an SM-T560NU. Specifically an
SM-T560NUUEU1CQK2. I think it's an A3L, not a
gtlewifiue. So I am trying to figure that out. I backed up the device and don't mind trying to move forward if there is more of a chance that I can at least recover it to oem rather than brick it. Any advice on verification of model or recovery if install fails?
Only a guess or opinion, I know that there are no guarantees, lol. But it is very slow and I do need to make my best attempt to improve it.
Thanks.

tc3500 said:
I have all of the files downloaded to my laptop.
And that took some time. I got a Note 9 last year and I rarely even turn my PC on anymore. So there were many updates and and misc things to attend. Also it is frustratingly slow compared to my phone, haha.
I do need to get CF Root.
But my concern is that my Tab E is a Wifi model. And I am not sure how to verify if it will accept this modification.
It is definitely an SM-T560NU. Specifically an
SM-T560NUUEU1CQK2. I think it's an A3L, not a
gtlewifiue. So I am trying to figure that out. I backed up the device and don't mind trying to move forward if there is more of a chance that I can at least recover it to oem rather than brick it. Any advice on verification of model or recovery if install fails?
Only a guess or opinion, I know that there are no guarantees, lol. But it is very slow and I do need to make my best attempt to improve it.
Thanks.
Click to expand...
Click to collapse
From what I gather the letters and digits that follow SM-T560NU describe the carrier or the country of origin but I could be wrong.
I can't advise you to try or not to try flashing this ROM but there is near certainty that you can restore your original firmware from this site using the Odin method if anything goes wrong as I've mentioned in my previous post. If what you're after is speed you could even flash an older firmware (lollipop or marshmallow) and disable auto-update but you'd be left exposed to multiple android security vulnerabilities that aren't present in this updated ROM.

upyisfar said:
From what I gather the letters and digits that follow SM-T560NU describe the carrier or the country of origin but I could be wrong.
I can't advise you to try or not to try flashing this ROM but there is near certainty that you can restore your original firmware from this site using the Odin method if anything goes wrong as I've mentioned in my previous post. If what you're after is speed you could even flash an older firmware (lollipop or marshmallow) and disable auto-update but you'd be left exposed to multiple android security vulnerabilities that aren't present in this updated ROM.
Click to expand...
Click to collapse
I keep the tablet pretty clean. It's an 'extra' device.
Don't really store anything on it. Use if for the web and take it on the boat or guests can use it. I will gl with 15.1 and see what happens. Thanks so much.
I did get the Firmware downloaded, that site is SLOW if you're cheap like me, haha. Hope your day is a good one.

upyisfar said:
From what I gather the letters and digits that follow SM-T560NU describe the carrier or the country of origin but I could be wrong.
I can't advise you to try or not to try flashing this ROM but there is near certainty that you can restore your original firmware from this site using the Odin method if anything goes wrong as I've mentioned in my previous post. If what you're after is speed you could even flash an older firmware (lollipop or marshmallow) and disable auto-update but you'd be left exposed to multiple android security vulnerabilities that aren't present in this updated ROM.
Click to expand...
Click to collapse
Does this look correct?
Is it the 0:[com5] that let's it know to flash the tablet and not my laptop? Lol......
---------- Post added at 10:38 PM ---------- Previous post was at 10:12 PM ----------
@upyisfar....
Did I need to install Lineage or TWRP to the tablet before rooting?
I used the cf-auto root file from the XDA Thread on rooting the sm-t569nu.
......here.... https://consumingtech.com/how-to-root-the-samsung-galaxy-tab-a-9-7/

tc3500 said:
Does this look correct?
Is it the 0:[com5] that let's it know to flash the tablet and not my laptop? Lol......
---------- Post added at 10:38 PM ---------- Previous post was at 10:12 PM ----------
@upyisfar....
Did I need to install Lineage or TWRP to the tablet before rooting?
I used the cf-auto root file from the XDA Thread on rooting the sm-t569nu.
......here.... https://consumingtech.com/how-to-root-the-samsung-galaxy-tab-a-9-7/
Click to expand...
Click to collapse
When I did mine almost a year ago, I rooted first, then I flashed the TWRP img from an app such as rashr or flashify (might have to install the SuperSU app first to get the permission dialogs). Then rebooted into recovery and flashed lineage from there. But now I'm wondering if you might be able to flash TWRP directly from Odin without needing to root first. I wish someone with a fresh experience could chime in here.
Anyhow here's a video I came across that might be helpful to you:
Samsung Galaxy Tab E 9.6 Root & Install TWRP Recovery 100% Working
And yes the SamMobile site is painfully slow but it is a lifesaver if you brick your device. Once you have obtained the firmware, it is really easy to recover your device with Odin.

I NEED Redmi Note 8 Pro firmware v11.0.7.0 PGGMIXM Can Anyone Help?

My Phone is UK version 6gb 128GB
MIUI version: MIUI Global | Stable 11.0.7.0 (PGGMIXM)
Android Version: 9 PPR1.180610.011
Security Patch: 2020-04-01
Did anyone get a backup of the above Android 9 firmware version before the upgrade to 10 came out.
The above version supports the new front camera shipped on newer devices.
If anyone was smart enough to make a backup please upload it some place. :fingers-crossed:
I was dumb on this occasion & never got a backup.

bigrammy said:
...MIUI Global | Stable 11.0.7.0 (PGGMIXM)
Android Version: 9 PPR1.180610.011
Security Patch: 2020-04-01
Did anyone get a backup ...
Click to expand...
Click to collapse
I have begonia_global_images_V11.0.6.0.PGGMIXM_20200108.0000.00_9.0_global.tgz (fastboot image), if you want it. Reply and I'll upload it somewhere.

Thanks for the offer but it has to be the v11.0.7.0. Sadly.
I have the v11.0.6.0 but as explained the front camera is not supported on newer built hardware using this firmware version. Basically mi changed the front camera and maybe other hardware on these devices. They unified the kernels in the latest 10 update but 9 is still fragmented.

bigrammy said:
Thanks for the offer but it has to be the v11.0.7.0. Sadly.
I have the v11.0.6.0 but as explained the front camera is not supported on newer built hardware using this firmware version. Basically mi changed the front camera and maybe other hardware on these devices. They unified the kernels in the latest 10 update but 9 is still fragmented.
Click to expand...
Click to collapse
The v11.0.7.0. is an OTA recovery update, did you try to get it through updates?

No OTA's for me except the latest Android 10 update. This 11.0.7 firmware is not available any place and I have searched every official source. Since mi didn't do an official release of this firmware for the begonia I think it's the on device shipped firmware so someone would of needed to make a backup. I never gave it a second thought thinking everything would be Equal but it seems not. :crying:

OK then maybe @bigrammy could try the next update to see what happens, no need to update but only to download the package and share it here.
I also searched and nothing.
Maybe you could try with this guide https://forum.xda-developers.com/mi-mix-2/how-to/guide-reverse-engineering-xiaomi-ota-t3691612 I used to use similar method to catch some early updates on Samsung devices although is pretty probable that Xiaomi dropped this release for some reason.

SubwayChamp said:
OK then maybe @bigrammy could try the next update to see what happens, no need to update but only to download the package and share it here.
I also searched and nothing.
Maybe you could try with this guide https://forum.xda-developers.com/mi-mix-2/how-to/guide-reverse-engineering-xiaomi-ota-t3691612 I used to use similar method to catch some early updates on Samsung devices although is pretty probable that Xiaomi dropped this release for some reason.
Click to expand...
Click to collapse
Thanks but the only OTA I ever get is Android 10 even if I flash the the 11.0.6 firmware. I am well used to all this stuff rolling back and forth and capturing updates etc etc on many devices like Sonys, Nokia, etc but sadly nothing arrived for this v11.0.7.
I guess I will need to wait till someone does a backup of the shipped Android 9 firmware of these newer devices. :fingers-crossed:

@bigrammy
So...you need someone with new camera hardware and correct Android 9 version. Will TWRP backup be enough to get cam drivers?

wojownikhaha said:
@bigrammy
So...you need someone with new camera hardware and correct Android 9 version. Will TWRP backup be enough to get cam drivers?
Click to expand...
Click to collapse
That would be the dream my friend so if you have a TWRP backup of that firmware that would be totally awesome
I still kick myself now for NOT backing up my stock Android 9 first a total epic fail on my part.

bigrammy said:
I still kick myself now for NOT backing up my stock Android 9 first a total epic fail on my part.
Click to expand...
Click to collapse
Indeed. I didn't expect that Xiaomi changed front camera sensor. MIUI has terrible RAM management, so custom ROM is the only reasonable option.
To be honest I don't have TWRP backup, but I thought of buying a second N8 Pro, unlock it, take a TWRP backup and then return it to shop (with relocked bootloader of course).
If it helps the devs - why not?

wojownikhaha said:
Indeed. I didn't expect that Xiaomi changed front camera sensor. MIUI has terrible RAM management, so custom ROM is the only reasonable option.
To be honest I don't have TWRP backup, but I thought of buying a second N8 Pro, unlock it, take a TWRP backup and then return it to shop (with relocked bootloader of course).
If it helps the devs - why not?
Click to expand...
Click to collapse
OK I see. Well I wouldn't worry about it too much because without the camera driver kernel source there is not much can be done really.
The main reason for wanting the Android 9 stock ROM is I had hoped to try some experimentation using the Stock "kernel" which is fully compatible with the Engineering lk and preloader (Can Use SPFlashTool) .
I would not risk buying another one of these phones again until the official source code is updated with the New front camera driver until then we're kind of stuck.
I keep a close eye on any updates for this device and or any other Xiaomi MTK devices that could use this camera in the future.
GitHub - MiCode/Xiaomi_Kernel_OpenSource: Xiaomi Mobile Phone Kernel OpenSource
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com

bigrammy said:
Xiaomi_Kernel_OpenSource/imgsensor_sensor_list.c at cezanne-q-oss · MiCode/Xiaomi_Kernel_OpenSource
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
use camera driver #if defined(S5K3T2SUNNY_MIPI_RAW) #if defined(S5K3T2OFILM_MIPI_RAW) from above thanks.
Click to expand...
Click to collapse
Looks good. Are that a new drivers for our devices?

wojownikhaha said:
Looks good. Are that a new drivers for our devices?
Click to expand...
Click to collapse
They are used in Redmi K30 Ultra which is MTK SoC also so merging the selfie camera drivers into the (begonia) RN8P should be doable.
I am not 100% sure if they would be compatible or if they still rely on (need) the base S5K3T2_MIPI_RAW driver.
Comms with the main dev's is pretty poor and it seems like a bit of a closed club so I can't really ask any meaningful questions. I can only suggest and point and hope they pick it up and use it if it's workable.
I raised an issue on github some time ago but never got any reply just a bunch of commits that seemed unrelated to the camera. https://github.com/AgentFabulous/begonia/issues/1
We could do with a commited XDA kernel dev who is happy to use this forum platform rather than "social media like telegram, twitter, facebook sort of nonsense" which is not my idea of sharing and Learning.
Following anything on those platforms is near impossible for me as everything is a bunch of fragmented one liners
Maybe it's a age thing IDK (It means I Dont Know seemingly )

@bigrammy
I recieved new Note 8 Pro and - guess what - production date is July 2020.
{
"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"
}
I am going to see what version of firmware is installed but.... I don't expect much.
----
EDIT. Version 11.0.5.0(PGGEUXM) Kill me.

wojownikhaha said:
@bigrammy
I recieved new Note 8 Pro and - guess what - production date is July 2020.
I am going to see what version of firmware is installed but.... I don't expect much.
----
EDIT. Version 11.0.5.0(PGGEUXM) Kill me.
Click to expand...
Click to collapse
Yes that's the EU firmware for the Newer Camera like mine. If you could make a backup that would cool

I have it. how to backup the rom?

@kinder_surprise
First - you have to unlock bootloader and then install non CFW TWRP Recovery

kinder_surprise said:
I have it. how to backup the rom?
Click to expand...
Click to collapse
As @wojownikhaha as said the first step is to unlock the bootloader following the official way which is a long drawn out process sadly.
Once you have unlocked the bootloader you need to flash the engineering preloader and LK from here https://forum.xda-developers.com/t/guide-info-psa-redmi-note-8-pro-megathread-cfw.4056527/
Personally I would then just use SPFlashTool to do a "Read Back" of the device as I am not 100% sure if TWRP would boot without a modified boot.img installed which would require overwriting OUR stock boot.img with a boot.img from the other devices without these newer cameras if that makes sense
Put simply we need a copy of our device boot.img.
If TWRP is allowed to boot without any mods to the boot.img then fine simply make a TWRP backup.
Otherwise SPFlashTool is needed to do a backup of our stock partitions.
Let me know what level your at with all this stuff so we can better guide you if required.
Thanks bigrammy

bigrammy said:
I am not 100% sure if TWRP would boot without a modified boot.img
Click to expand...
Click to collapse
I confirm - this is possible. I was able to boot to recovery just after installation (on first Note with 11.0.7.0)
Anyway, I will provide full TWRP backup of stock 11.0.5.0 on next Thursday.

wojownikhaha said:
I confirm - this is possible. I was able to boot to recovery just after installation (on first Note with 11.0.7.0)
Anyway, I will provide full TWRP backup of stock 11.0.5.0 on next Thursday.
Click to expand...
Click to collapse
Hi Thanks for the confirmation that it is possible to boot TWRP without the need to flash a modified boot.img first.
Looking forward to the EU 11.0.5.0 firmware
@kinder_surprise
This info will make things much easier

Question Lack of development?

There has been 0 talk about any ROMs or development for the OP9 and it's been over a month since release. Does anyone know if any developers are working on one??

The OP9 and OP9 Pro don't even have unofficial or official TWRP support yet, so a custom ROM is kinda out of the question until TWRP is on the devices. OP9 Pro literally just got it's first custom kernel 2 days ago. I don't know what the time frame is for custom ROM development but a lot of it hinges on getting TWRP support for the phones.
Side note: You said OP9 in the OP9 Pro forums so I'm gonna assume you were referring to the OP9 Pro. Regardless my statement about needing TWRP support first applies to both phones.

GreaterLesser said:
The OP9 and OP9 Pro don't even have unofficial or official TWRP support yet, so a custom ROM is kinda out of the question until TWRP is on the devices. OP9 Pro literally just got it's first custom kernel 2 days ago. I don't know what the time frame is for custom ROM development but a lot of it hinges on getting TWRP support for the phones.
Side note: You said OP9 in the OP9 Pro forums so I'm gonna assume you were referring to the OP9 Pro. Regardless my statement about needing TWRP support first applies to both phones.
Click to expand...
Click to collapse
TWRP is absolutely not necessary and will most likely never come out for later OP devices, including the 9, unless they figure out the decryption problem. See the 8's etc, plenty of dev and none of the TWRP.
Regarding dev, it's happening, but no need for discussion here until something is at least in a semi-stable beta build.

craznazn said:
TWRP is absolutely not necessary and will most likely never come out for later OP devices, including the 9, unless they figure out the decryption problem. See the 8's etc, plenty of dev and none of the TWRP.
Regarding dev, it's happening, but no need for discussion here until something is at least in a semi-stable beta build.
Click to expand...
Click to collapse
I apologize for my lack of knowledge of what happened in the OnePlus 8 scene as I didn't have that phone. I came from the 6T. But looking through the 8, 8 Pro, and 8T forums, it seems a custom recovery is still needed for custom ROMs. Only difference was the custom recovery was provided by the ROM Dev and not TWRP.

It's early in the game.... will be happening!

ddizzy81 said:
There has been 0 talk about any ROMs or development for the OP9 and it's been over a month since release. Does anyone know if any developers are working on one??
Click to expand...
Click to collapse
We don't have a TWRP build yet, I've been looking to build one but there's a problem with Android Image Kitchen which should hopefully be fixed soon, I'm guessing that's why no-one else has built a recovery. You can read more about it here.
Custom roms are kinda a non-starter without TWRP (or another custom recovery)
OnePlus has been messing up with their source for a while now too, not to mention that we're still getting regular updates to the original release which might mess with kernels too.
We might be another month before you'll start seeing enough stability to start getting custom roms.
EDIT : Looks like AIK might be working properly now, gonna have a look and see if I can get a TWRP build working, although there's no other phones with the same resolution so that might be a problem to get some resources. LG G3 has a similar resolution but not exactly the same, it's very important for the touchscreen setup for TWRP or else the buttons on screen won't be where you're actually tapping.
{
"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"
}
For anyone else who fancies trying their hand at it, there's a porting guide here.

To add to what @craznazn said, a custom recovery isn't 100% necessary for custom ROMs. The 7T didn't require it to flash any, as a fastboot method is doable. Developing them is another story, though. Some custom ROMs were based on OOS, while AOSP ones still had some bases from OOS (YAAP, for example, was a Pixel-themed ROM but required you to have OOS11, in some shape or form, installed prior to flashing it because it needed vendor files and so on.

djsubterrain said:
We don't have a TWRP build yet, I've been looking to build one but there's a problem with Android Image Kitchen which should hopefully be fixed soon, I'm guessing that's why no-one else has built a recovery. You can read more about it here.
Custom roms are kinda a non-starter without TWRP (or another custom recovery)
OnePlus has been messing up with their source for a while now too, not to mention that we're still getting regular updates to the original release which might mess with kernels too.
We might be another month before you'll start seeing enough stability to start getting custom roms.
EDIT : Looks like AIK might be working properly now, gonna have a look and see if I can get a TWRP build working, although there's no other phones with the same resolution so that might be a problem to get some resources. LG G3 has a similar resolution but not exactly the same, it's very important for the touchscreen setup for TWRP or else the buttons on screen won't be where you're actually tapping.
View attachment 5298703
For anyone else who fancies trying their hand at it, there's a porting guide here.
Click to expand...
Click to collapse
The Samsung Galaxy S20, and S20 Plus have a very close resolution to the OP9P
OP9P: 1440x3216
SGS20/SGS20+: 1440x3200
And they already have an unofficial twrp build too.
SGS20/SGS20+ TWRP:
[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 Series (Snapdragon)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Hope this helps.

GreaterLesser said:
The Samsung Galaxy S20, and S20 Plus have a very close resolution to the OP9P
OP9P: 1440x3216
SGS20/SGS20+: 1440x3200
And they already have an unofficial twrp build too.
SGS20/SGS20+ TWRP:
[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 Series (Snapdragon)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Hope this helps.
Click to expand...
Click to collapse
Sorry to say. But portions are what we are talking about. Resolution has no bearing on getting TWRP working. Ex op7tpro

toolhas4degrees said:
Sorry to say. But portions are what we are talking about. Resolution has no bearing on getting TWRP working. Ex op7tpro
Click to expand...
Click to collapse
Portions...? As in dimensions? It is true the screens are different sizes, as well.
In regards to OP's post that there's been 0 development talk, well, not exactly zero, as unlocking and rooting, as well as conversion from T-Mobile to global, enabling dual-SIM, and the MSM and QPST tools needed for such, have been ongoing for some time. There's no custom ROMs, sure, and I get that a custom kernel was just released, but a massive part of development is simply discussion, throwing around ideas, research, testing, etc. It also helps if more devs happen to purchase our particular device (and thankfully this is something we won't have to worry about for long). It's worse when a device gets little to no development because it simply isn't popular enough to warrant much development. I do get the sentiment that it's been a while, but I guess we'll just have to be patient.

GuyInDogSuit said:
Portions...? As in dimensions? It is true the screens are different sizes, as well.
In regards to OP's post that there's been 0 development talk, well, not exactly zero, as unlocking and rooting, as well as conversion from T-Mobile to global, enabling dual-SIM, and the MSM and QPST tools needed for such, have been ongoing for some time. There's no custom ROMs, sure, and I get that a custom kernel was just released, but a massive part of development is simply discussion, throwing around ideas, research, testing, etc. It also helps if more devs happen to purchase our particular device (and thankfully this is something we won't have to worry about for long). It's worse when a device gets little to no development because it simply isn't popular enough to warrant much development. I do get the sentiment that it's been a while, but I guess we'll just have to be patient.
Click to expand...
Click to collapse
Partitions sorry typo. Also they just released kernel sources not very long ago. In order to build you need these. The dev here had this up and running on his device for a while, but just like ROM devs the first two or three bases they make are not for public and take a long time to work out bugs. Secondly twrp is not required to flash a custom ROM did it via fastboot on my op7tpro. Development is up to owners. You have an unlocked bootloader and kernel sources. If everyone is *****in about development start developing. Download a Linux distro or wubi and and build one for the community. Everyone *****es and doesn't contribute.

toolhas4degrees said:
Partitions sorry typo
Click to expand...
Click to collapse
Ahhh. That makes more sense now.

GreaterLesser said:
The OP9 and OP9 Pro don't even have unofficial or official TWRP support yet, so a custom ROM is kinda out of the question until TWRP is on the devices. OP9 Pro literally just got it's first custom kernel 2 days ago. I don't know what the time frame is for custom ROM development but a lot of it hinges on getting TWRP support for the phones.
Side note: You said OP9 in the OP9 Pro forums so I'm gonna assume you were referring to the OP9 Pro. Regardless my statement about needing TWRP support first applies to both phones.
Click to expand...
Click to collapse
Op8 doesn't even have a working twrp for A11 yet. So that's not it at all. Twrp does nothing for our devices as far as roms or kernels. You flash a kernel through a kernel manager and All the roms flash through fastboot & fastbootd. That's def not it. But it will however take time. We need msm tools prior to messing with things anyway. Or we will all be in a brick like state. And a main dev for aospa which is Paranoid Android has a 9 . That will be soon I'm guessing.

mattie_49 said:
Op8 doesn't even have a working twrp for A11 yet. So that's not it at all. Twrp does nothing for our devices as far as roms or kernels. You flash a kernel through a kernel manager and All the roms flash through fastboot & fastbootd. That's def not it. But it will however take time. We need msm tools prior to messing with things anyway. Or we will all be in a brick like state. And a main dev for aospa which is Paranoid Android has a 9 . That will be soon I'm guessing.
Click to expand...
Click to collapse
Thanks - Someone already explained this earlier.