This is the new refined home for DarkRoom Development. If you submit bug reports without a log, you may be prosecuted...or executed.
Disclaimer:
If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.
Links:
Social:
Telegram - https://t.me/darkroomdev
Discord - https://discord.gg/BGTFutW
Downloads:
https://drive.google.com/open?id=1SLC6A4RvTE_yYF_u6GMKU_q7lvX3YCFB
Source:
Github – https://github.com/DespairFactor/
Credits:
Google
Will certainly give it a try, appreciate your work!!
Will this make the touch screen work on TWRP (for 3XL?)
+1 will try once i get behind my PC
is the function to disable FSYNC available?
Ariel_PR said:
Will this make the touch screen work on TWRP (for 3XL?)
Click to expand...
Click to collapse
As of now, it does not.
Would it be possible for a list of items that are different / features of the kernel.
Thanks!
your the man
can we please get a list of features, etc
what is the purpose of performanced? @DespairFactor
---------- Post added at 08:20 PM ---------- Previous post was at 07:55 PM ----------
disable fsync
reap the benefits of speed
+1
@DespairFactor
curious to know if the kernel would let us boot /data as EXT4 - i have tried formatting /data as EXT4 with stock kernel (and adding appropriate lines for fstab.sdm845) but it always returns device is corrupt, please format device. when i boot. (i dont know if this is a kernel issue because i have formatted ext4 to f2fs before on other devices with stock kernel that support f2fs)
as odd as it sounds, i believe we can extract more performance out of the device if we format as EXT4 instead of the stock F2FS
the partitioning of F2FS on the pixel 3/xl is disgusting i believe this is why if you run /data decrypted you can no longer set a fingerprint or change PIN from settings.
accordng to the TWRP thread - -and old Pixel XL 2 forums - there is something that needs to be included in the kernel in order for touch responsiveness to work properly after flashing TWRP - this is supposed to come with a custom kernel - I don't know what files are needed - but hopeing this can be done with this kernel so we can finally flash TWRP on the 3 XL - (we can boot into twrp with adb and flash a kernel that way - but it is only a temporary custom recovery then)
Geekser said:
accordng to the TWRP thread - -and old Pixel XL 2 forums - there is something that needs to be included in the kernel in order for touch responsiveness to work properly after flashing TWRP - this is supposed to come with a custom kernel - I don't know what files are needed - but hopeing this can be done with this kernel so we can finally flash TWRP on the 3 XL - (we can boot into twrp with adb and flash a kernel that way - but it is only a temporary custom recovery then)
Click to expand...
Click to collapse
https://github.com/DespairFactor/bl...c0260/arch/arm64/configs/b1c1_defconfig#L1996
The touchscreen drivers need to be built inline instead of a module
Freak07 said:
https://github.com/DespairFactor/bl...c0260/arch/arm64/configs/b1c1_defconfig#L1996
The touchscreen drivers need to be built inline instead of a module
Click to expand...
Click to collapse
thanks for the clarity - honestly, this is way over my head - but hoping that someone will do what is needed to make this happen. When you say they touchscreen drivers need to be built inline - do you meant they need to be built inline in the kernel itself? if that is the case, hopefully the Dev for the Despair Kernel can look into that for a future update -
Geekser said:
thanks for the clarity - honestly, this is way over my head - but hoping that someone will do what is needed to make this happen. When you say they touchscreen drivers need to be built inline - do you meant they need to be built inline in the kernel itself? if that is the case, hopefully the Dev for the Despair Kernel can look into that for a future update -
Click to expand...
Click to collapse
I’m pretty sure you won’t be disappointed
Freak07 said:
https://github.com/DespairFactor/bl...c0260/arch/arm64/configs/b1c1_defconfig#L1996
The touchscreen drivers need to be built inline instead of a module
Click to expand...
Click to collapse
You can't, the kernel won't boot with the Samsung touchscreen driver compiled inline
DespairFactor said:
You can't, the kernel won't boot with the Samsung touchscreen driver compiled inline
Click to expand...
Click to collapse
Oh well.... That’s bad news
DespairFactor said:
You can't, the kernel won't boot with the Samsung touchscreen driver compiled inline
Click to expand...
Click to collapse
Does that mean it won't be possible to ever flash TWRP as a permanent Recovery solution? That instead we will have to boot into TWRP each time we watn to flash something? Just curious....I guess it wouldn't be that big of a pain the butt....
Geekser said:
Does that mean it won't be possible to ever flash TWRP as a permanent Recovery solution? That instead we will have to boot into TWRP each time we watn to flash something? Just curious....I guess it wouldn't be that big of a pain the butt....
Click to expand...
Click to collapse
I use EXKM or Franco Kernel Updater to flash kernel and then flash magisk with magisk manager followed by a reboot
DespairFactor said:
I use EXKM or Franco Kernel Updater to flash kernel and then flash magisk with magisk manager followed by a reboot
Click to expand...
Click to collapse
I think he's referring to getting an up and running permanent TWRP install for flashing ZIPs.
DespairFactor said:
I use EXKM or Franco Kernel Updater to flash kernel and then flash magisk with magisk manager followed by a reboot
Click to expand...
Click to collapse
I was wondering about that. So, flash with kernel app but don't reboot. Immediately flash magisk via magisk manager and reboot. Any chance dispair kernel maintains root after a kernel flash in the future?
Sent from my crosshatch using XDA Labs
airmaxx23 said:
I think he's referring to getting an up and running permanent TWRP install for flashing ZIPs.
Click to expand...
Click to collapse
Well, I don't know if we can do that right now, we'd need to load the modules in TWRP
ridobe said:
I was wondering about that. So, flash with kernel app but don't reboot. Immediately flash magisk via magisk manager and reboot. Any chance dispair kernel maintains root after a kernel flash in the future?
Sent from my crosshatch using XDA Labs
Click to expand...
Click to collapse
Yeah that's what I did, but I don't think so
Related
Team Win Recovery Project 2.x, or twrp2 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 completely theme-able. You can change just about every aspect of the look and feel.
TWRP 3.2.1 Changelog: https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
Installation instructions: Use the official TWRP app (requires root), available here and here. If you already have TWRP installed, you can also download the latest available img and flash it from recovery.
DOWNLOAD (palman): https://dl.twrp.me/palman/
DOWNLOAD (v500): https://dl.twrp.me/v500/
More info: https://twrp.me/devices/lggpad83.html
Warning: builds for v500 require kitkat bootloader. If you are stuck on Lollipop bootloader, check this post.
Device source (palman): https://github.com/TeamWin/android_device_lge_palman
* The kernel in palman source is from 5.1 official build (source found here).
Device source (v500): https://github.com/TeamWin/android_device_lge_v500
* The kernel in v500 source is based on cm-14.1 sources.
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the LG G Pad 8.3
Contributors
fefifofum, Dees_Troy, bigbiff
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2015-06-15
Last Updated 2017-12-10
Thanks very much for this! Great work! That is really nice that there is now official support for awifi/v500.
I assume the images are bumped?
Are the kernel sources for official twrp using your kernel sources?
Sources
This is the device repo for awifi/v500: https://github.com/TeamWin/android_device_lge_v500
The kernel in awifi/v500 repo was compiled from here, which is V50030A based.
This is the device repo for palman/v510: https://github.com/TeamWin/android_device_lge_palman
The kernel in palman/v510 repo is from 5.1 official build.
So, now we should be able to just flash the .img file directly within TWRP to update.
Deltadroid said:
So, now we should be able to just flash the .img file directly within TWRP to update.
Click to expand...
Click to collapse
Yes!
The repo for v510 is going to be renamed since it doesn't need to follow the "cyanogen" way, which is using the model name instead of the device name. That's why there is a little confusion with the names v500/awifi and v510/palman. The GPE repo will be named palman (which is the correct way) and the non GPE repo will stay as v500 (it should be called awifi), since almost every custom rom uses "cyanogen" way. If we wanted the non GPE to be named correctly we would need the devs of every custom rom to add an assert to their boardconfig so both, v500 and awifi, would be valid at installation time. It's just one line change.
Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?
fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?
luisbraz said:
Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?
Click to expand...
Click to collapse
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
aidfarh said:
fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?
Click to expand...
Click to collapse
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?
fefifofum said:
Why would you need to backup recovery partition?
Click to expand...
Click to collapse
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.
fefifofum said:
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?
Click to expand...
Click to collapse
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work
I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.
aidfarh said:
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.
Click to expand...
Click to collapse
Old versions will still be available to download, so if a new version had issues you could always download and install an older version. No need to backup recovery I guess...
luisbraz said:
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work
Click to expand...
Click to collapse
We don't need loki anymore, you just need to be on kitkat bootloader.
luisbraz said:
I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.
Click to expand...
Click to collapse
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.
fefifofum said:
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.
Click to expand...
Click to collapse
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!
luisbraz said:
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!
Click to expand...
Click to collapse
Glad to hear that! It seems the app TWRP manager cannot reach the new servers where official builds of TWRP are, so it's better not to use the app installation method to avoid installing old versions.
@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.
bokoy said:
@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.
Click to expand...
Click to collapse
I guess V50010B bootloader is what you need, but then you will probably have brightness issues while using this recovery.
New version
TWRP 2.8.7.0 released.
fefifofum said:
TWRP 2.8.7.0 released.
Click to expand...
Click to collapse
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!
Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.
D4xel said:
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!
Click to expand...
Click to collapse
This one is official (without the quotes), doesn't require loki and is adapted to kitkat bootloader backlight. The other one you mention is adapted to jellybean bootloader backlight and requires loki. Just install the one that fits your needs.
cianz94 said:
Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.
Click to expand...
Click to collapse
You have the install instructions on the first post. You can also download the image and flash it with THIS APP.
Stock Kernel + SafetyNet Patch + DRM Fix
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- Now You can use Android Pay with an unlocked bootloader.
Installation:
- Installation using TWRP
- Installation via the bootloader
Code:
fastboot flash boot boot.img
Downloads: Dropbox; AndroidFileHost
Sourse: 32.3.A.2.33; 32.4.A.0.160; 32.4.A.1.54
I compiled the stock kernel and applied the SafetyNet patch by sultanxda.
DISCLAIMER:
No one is responsible for any damage caused to your device except You. You have been warned.
TWRP 3.1.1 for Xperia Z5, Z5C, Z3+
Vulkan API for Adreno 430
There's a better way than using the boot partition. If you use the ramdisk method, and get it to a recovery partition, you can do almost anything back and forth without having to change boot images. you can just flash over everything and still maintain your recovery partition.
https://forum.xda-developers.com/showthread.php?t=3588365
https://forum.xda-developers.com/showthread.php?t=3609358
@NeoBeum
At me on stock firmware of Magisk, doesn't hide SafetyNet and therefore I compiled this kernel.
grayleshy said:
@NeoBeum
At me on stock firmware of Magisk, doesn't hide SafetyNet and therefore I compiled this kernel.
Click to expand...
Click to collapse
grab the recovery image I made and then flash it to recovery while you're using your kernel, then flash magisk I the fota/recovery partition recovery, then magisk will be able to capture the sepolicy it needs, then you should be able to flash a full ftf excluding FOTAKernel. to test, you'll have 2 recovery working. the one that's in the boot img, and recovery img.
I had this at the start, and once I got recovery to the recovery partition, ive been free to flash anything if I exclude the fotakernel wipe.
I had to add the fstab for the older Android versions. but I haven't included that in the prebuilt recovery.
magisk only needs to capture a pure system and boot image once, and it mirrors it. after that, you can load up modified kernels
IT s nice to see A kernel for nougat..
What about other functions of kernel? All stock?
emosis said:
What about other functions of kernel?
Click to expand...
Click to collapse
In the future, if I have the desire, then I will make a custom kernel with improvements.
The first will be a raised version of the kernel with 3.10.84 to 3.10.105.
emosis said:
All stock?
Click to expand...
Click to collapse
What do You mean?
Can i flash and working with LOS 14.1?
reevdre said:
Can i flash and working with LOS 14.1?
Click to expand...
Click to collapse
The kernel is only for stock firmware!
On other firmware, the stability is not guaranteed.
reevdre said:
Can i flash and working with LOS 14.1?
Click to expand...
Click to collapse
if they haven't made a recovery for LOS, I'll have a recovery twrp port for it after the Z5C gets official support for the Omni base, AOSP is completed, but there's no room on their build server for new AOSP devices
Can you update this for .160? I have the kernel. Thanks!
dlee390 said:
Can you update this for .160? I have the kernel.
Click to expand...
Click to collapse
Sony did not post the kernel sources. dev
oh ok thanks!
also, why doesn't this work with magisk like your other kernels for z5p and z5? thanks!
dlee390 said:
also, why doesn't this work with magisk like your other kernels for z5p and z5? thanks!
Click to expand...
Click to collapse
Use magisk v13.
Upd 32.4.A.0.160
Need update for 32.4.A.1.54 rom
frager45 said:
Need update for 32.4.A.1.54 rom
Click to expand...
Click to collapse
Well, I'll do it!
Upd 32.4.A.1.54.
GreyLeshy said:
Upd 32.4.A.1.54.
Click to expand...
Click to collapse
Thnaks, but wi-fi not opening...
I try press on button but not pressing...
frager45 said:
Thnaks, but wi-fi not opening...
I try press on button but not pressing...
Click to expand...
Click to collapse
Provide a screenshot of the terminal command lsmod.
Stock Kernel + SafetyNet Patch + DRM Fix
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- Now You can use Android Pay with an unlocked bootloader.
Installation:
- Installation using TWRP
- Installation via the bootloader
Code:
fastboot flash boot boot.img
Downloads: Dropbox (E6633,E6653,E6683)
Current version: 32.3.A.2.33 -perf-g1016077
I compiled the stock kernel and applied the SafetyNet patch by sultanxda.
DISCLAIMER:
No one is responsible for any damage caused to your device except You. You have been warned.
TWRP 3.1.1 for Xperia Z5, Z5C, Z3+
Vulkan API for Adreno 430
please port for E6853
anjelz2012 said:
please port for E6853
Click to expand...
Click to collapse
Try the Zach's Kernel, in it the SafetyNet check is partially disabled.
Great work!
delete
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
rrdna said:
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
Try to install TWRP 3.1.1.
grayleshy said:
Try to install TWRP 3.1.1.
Click to expand...
Click to collapse
Thanks, 3.1.1 worked for me
rrdna said:
Thanks, 3.1.1 worked for me
Click to expand...
Click to collapse
It's great that TWRP came up and Magisk hides root.
Thanks for the work!!! Any chance for E6633?
christis said:
Thanks for the work!!! Any chance for E6633?
Click to expand...
Click to collapse
If the kernel don't work for You, give me Kernel.sin, then I will do it for E6633.
Thanks for the work. @grayleshy
SIN Files : https://drive.google.com/drive/folders/0B9v3aNFonkyMWlFMbF9yME5EaTg
Did you use sultanxda safetynet patch?
Added kernel for E6633.
sceryavuz said:
Did you use sultanxda safetynet patch?
Click to expand...
Click to collapse
I will soon lay out the source code. There and see, what patch is applied.
Thanks a lot. Can't wait to see the source code! Do you have an eta?
rrdna said:
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
I've the same issue...
MichaMichaMicha said:
Can't wait to see the source code!
Click to expand...
Click to collapse
Patch in kernel from @Sultanxda . Patch of may 23.
Earlier I didn't publish information on a patch as checked this patch.
Looks like you're working on an all in-built kernel ?
If you're making an progress towards in-built MHL please, please let us know
The magic seems to be in the configuration or additional patches (I had it working in the SunKernel Corona source)
but it doesn't seem to work out of the box with Sony's source [or I missed something],
anyway:
Keep up the good fight !
rrdna said:
Thank you! SafetyNet check passes without errors
But one question: I want to flash recovery afterwards, so i can use (or at least try to use) the magisk root + magisk hide method along with safetynet passed.
I tried different twrp.img (3.0.2 and 3.1.0) for e6653, but no recovery seems to work.
I tried to flash it via "fastboot flash recovery twrp-x.x.x.img" but it does not boot into recovery ("adb reboot recovery" and hotkeys result in a simple system reboot).
I am not sure though, if i have to flash twrp into a different partition than "recovery"?
Thank you in advance.
Click to expand...
Click to collapse
When you install magisk is the drmfix still active? The last time I installed magisk I was facing issues where I'd get white noise when taking pictures and no post processing being done
Thank you!
Now I can use OTA updates for my Z5!!
The_Miggs said:
Thank you!
Now I can use OTA updates for my Z5!!
Click to expand...
Click to collapse
This is not about OTA. SafetyNet : https://www.howtogeek.com/241012/sa...y-and-other-apps-dont-work-on-rooted-devices/
Hi,
I am getting into kernel development with a Google Pixel phone. I noticed that I need root permission in order to access syslog. My phone is on stock ROM with Magisk installed.
However, since Magisk only patched the original boot image, and since I am testing my kernel by temporarily booting it using "fastboot boot", I don't have access to root when using my own kernel. (I know this is sarcastic...)
I wonder how other kernel devs handle this situation. Do I need to compile the entire AOSP into a ROM with root builtin? Or is there another way around this using Magisk?
Thank you!
You don't fastboot boot a kernel, do you?
Anyway, if you use Anykernel you can flash your kernel over the Magisk patched boot image and Magisk should stay intact.
DISCLAIMER: I know absolutely nothing, zip, and null about kernel development.
Eventually I found out that, there was no way for my kernel to coexist with Magisk, because Magisk also modifies the kernel and I wouldn't want to merge its changes.
I think I'll just have to compile an engineering variant of AOSP from scratch... Are there any precompiled "official" images?
Didgeridoohan said:
You don't fastboot boot a kernel, do you?
Anyway, if you use Anykernel you can flash your kernel over the Magisk patched boot image and Magisk should stay intact.
DISCLAIMER: I know absolutely nothing, zip, and null about kernel development.
Click to expand...
Click to collapse
Thanks for the suggestion. But I couldn't get it to work. I think I'll just build an entirely new system.img from AOSP.
I'd also recommend building the entire AOSP for any other people facing this question. It takes more time but is officially supported by Google.
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 loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Oneplus 6 that supports Android 11
can be flashed to boot with working decryption on android 11 roms
bugs:
backup/restore is unreliable
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_oneplus_enchilada
https://github.com/TeamWin/android_device_oneplus_sdm845-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/oneplus/oneplus6.html
Can anyone confirm if it work with the enchilada hotfix update for OOS 11 OB1?
Edit: Nope! Qualcomm Crashdump all the way
does not work. crash_dump. If repackaged with a stock kernel, it hangs on the TWRP logo.
Soft_M said:
does not work. crash_dump. If repackaged with a stock kernel, it hangs on the TWRP logo.
Click to expand...
Click to collapse
The kernel I'm using is Q based as that's the stable one, can you get logs after repacking with stock?
adb pull /tmp/recovery.log
adb logcat > logcat.txt
Nebrassy said:
The kernel I'm using is Q based as that's the stable one, can you get logs after repacking with stock?
adb pull /tmp/recovery.log
adb logcat > logcat.txt
Click to expand...
Click to collapse
For me this is a mystery, but now I repackaged it again with the stock kernel, and it started correctly.
Soft_M said:
For me this is a mystery, but now I repackaged it again with the stock kernel, and it started correctly.
Click to expand...
Click to collapse
cool,not much can be done right now though, as the android 11 kernel sources haven't been published yet for custom kernels to integrate what they did, and I nee to modify the kernel for fastboot boot to work, so consider this TWRP for stock 10 and customs, it's working on custom 11 roms
Maby remove the link or hole posted , because now people get crash dump error and that can't be good
NLhardcore said:
Maby remove the link or hole posted , because now people get crash dump error and that can't be good
Click to expand...
Click to collapse
this is for custom roms currently, not for stock 11
anyone can test on latest beta?, join the tg group
uploaded new build supporting stock android 11
Nebrassy said:
uploaded new build supporting stock android 11
Click to expand...
Click to collapse
bro i, we, love you, you just saved my life now, im testing it and i will try to flash something, last build is working but boot only didnt flash it yet, but seems working good, anyway super thx for your work <3
edit 1 : i just flashed a file, flashed without any problem
edit 2 : i flashed current twrp, working good <3
edit 3 :
i tell you guys, this TWRP working PERFTECT for ONEPLUS 6 ANDROID 11 STABLE
data decryption works?
CYB3R0ID694 said:
data decryption works?
Click to expand...
Click to collapse
i dont know what u mean bro, but i have password on my device and twrp asked me for it and i use it to unlock twrp, i think this is ur question? sorry for bad english
Evon88 said:
bro i, we, love you, you just saved my life now, im testing it and i will try to flash something, last build is working but boot only didnt flash it yet, but seems working good, anyway super thx for your work <3
edit 1 : i just flashed a file, flashed without any problem
edit 2 : i flashed current twrp, working good <3
edit 3 :
i tell you guys, this TWRP working PERFTECT for ONEPLUS 6 ANDROID 11 STABLE
Click to expand...
Click to collapse
How do I root after this? can I directly install magisk zip or is it not supported yet?
Nitesh Gohil said:
How do I root after this? can I directly install magisk zip or is it not supported yet?
Click to expand...
Click to collapse
i was hava a problem with my root, i installed GPU Booster and its bootloop ( before TWRP ) so i installed official boot.img again, and i was trying to root again with patched boot.img its bootloop again so i flashed official boot.img again and my phone start working normal,
AFTER TWRP, i FLASHED magisk uninstaller and boot to sys, work 100%
reboot to TWRP and install MAGISK installer and flashed 100%
now im rooted by TWRP
sorry for saying all this but just to make u sure that i FLASHED uninstaller once, and installer and working super fine
ADVICE: For battery drain in A11 : root and download this app
NoAd Battery Calibrator [ROOT] - Apps on Google Play
Calibrating your battery after flashing a new ROM may increase your battery life
play.google.com
get your phone to 100% battery and give root access to the app and click on Calibrate it will ask u for root give access and after give access press again on Calibrate, its working so good
Evon88 said:
i was hava a problem with my root, i installed GPU Booster and its bootloop ( before TWRP ) so i installed official boot.img again, and i was trying to root again with patched boot.img its bootloop again so i flashed official boot.img again and my phone start working normal,
AFTER TWRP, i FLASHED magisk uninstaller and boot to sys, work 100%
reboot to TWRP and install MAGISK installer and flashed 100%
now im rooted by TWRP
sorry for saying all this but just to make u sure that i FLASHED uninstaller once, and installer and working super fine
ADVICE: For battery drain in A11 : root and download this app
NoAd Battery Calibrator [ROOT] - Apps on Google Play
Calibrating your battery after flashing a new ROM may increase your battery life
play.google.com
get your phone to 100% battery and give root access to the app and click on Calibrate it will ask u for root give access and after give access press again on Calibrate, its working so good
Click to expand...
Click to collapse
Thanks! I just flashed magisk zip directly and I can confirm it's working without any hiccups
Evon88 said:
ADVICE: For battery drain in A11 : root and download this app
NoAd Battery Calibrator [ROOT] - Apps on Google Play
Calibrating your battery after flashing a new ROM may increase your battery life
play.google.com
get your phone to 100% battery and give root access to the app and click on Calibrate it will ask u for root give access and after give access press again on Calibrate, its working so good
Click to expand...
Click to collapse
Battery calibration apps don't do anything that any android rom couldn't do. What those apps do is reset your battery stats. But every time your phone is charged to 100% and you unplug it, your battery stats get automatically reset.
Any chance for 6t build?
Moe2003 said:
Any chance for 6t build?
Click to expand...
Click to collapse
same build should boot on 6t
Siddk said:
same build should boot on 6t
Click to expand...
Click to collapse
if thats true then why is there a 6t and 6 twrp separate?