[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy S8 and S8+ Exynos - Samsung Galaxy S8 & S8+ Cross Device Development

{
"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"
}
Official TWRP 3.6.1-* For Galaxy S8/S8+ Exynos​Only for exynos variants - G950F (Europe, Global Single-SIM); G950FD (Global Dual-SIM); G950N (South Korea); G955F (Europe, Global Single-SIM); G955FD (Global Dual-SIM); G955N (South Korea);
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Features:
Code:
- built from Pie kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 8.*/9.0/10.0
Downloads:
S8 - https://twrp.me/samsung/samsunggalaxys8.html
S8+ - https://twrp.me/samsung/samsunggalaxys8plus.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Bixby key" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Bixby key" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
S8 Device tree - https://github.com/TeamWin/android_device_samsung_dreamlte
S8+ Device tree - https://github.com/TeamWin/android_device_samsung_dream2lte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal8895/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible

Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary

FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.

Finally no more noobs telling you that quota causes encryption.

I assume that we will going to get 3.2.3.1 soon? No eta just curious ? Twrp on the server is from July...
And finally we get official with proper support??
Big thx

Many thanks

Thanks @corsicanu

Official builds are up!
Regards.
Sent from my SM-N950F using Tapatalk

S8 plus cannot mount usb otg 3.2.3.1 pls help

Iyaadali said:
S8 plus cannot mount usb otg 3.2.3.1 pls help
Click to expand...
Click to collapse
I'm looking into it. Thanks for reporting.
Sent from my SM-N950F using Tapatalk

OTG fix was only required for N8 devices as first time introduced by Tkkg1994, while the official device tree by Jesec had working OTG for dream(2). Moreover the features list says this TWRP is based on latest TWRP source, but the recovery is based on 7.1.2.

Noxxxious said:
OTG fix was only required for N8 devices as first time introduced by Tkkg1994, while the official device tree by Jesec had working OTG for dream(2). Moreover the features list says this TWRP is based on latest TWRP source, but the recovery is based on 7.1.2.
Click to expand...
Click to collapse
My bad that i didn't tested otg on s8 assuming that if it works on note8, it works on s8* too. I submitted a patch in review and will test it myself today as i don't have the otg dongle right now.
As for twrp source, yes it's 7.1, will edit OP if this causes troubles. I don't want to argue with anyone, i only made things official as you know the quota issues, not to mention all the flame from telegram regarding "use official even if it doesn't properly work".
Peace.
Sent from my SM-N950F using Tapatalk

corsicanu said:
My bad that i didn't tested otg on s8 assuming that if it works on note8, it works on s8* too. I submitted a patch in review and will test it myself today as i don't have the otg dongle right now.
As for twrp source, yes it's 7.1, will edit OP if this causes troubles. I don't want to argue with anyone, i only made things official as you know the quota issues, not to mention all the flame from telegram regarding "use official even if it doesn't properly work".
Peace.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
:laugh::good:
Just use the same otg path as from jesecs device tree. I can confirm it works as I am still using his TWRP and tried it yesterday.

Good job bro after testing your last beta file seems that otg its fixed on S8 thanks again brother

Hi, USB OTG option is not working in S8+ SM-G955FD

I flashed latest TWRP 3.2.3.2 but I cant mount /data partition on stock rom:
"Could not mount /data and unable to find crypto header"
Is this fixable - or
Is there a way to access /data without flashing no-dm-verity.zip? (e.g. systemless root or dump userdata img and mount on PC?)

TearsDontFalls said:
I flashed latest TWRP 3.2.3.2 but I cant mount /data partition on stock rom:
"Could not mount /data and unable to find crypto header"
Is this fixable - or
Is there a way to access /data without flashing no-dm-verity.zip? (e.g. systemless root or dump userdata img and mount on PC?)
Click to expand...
Click to collapse
I'm pretty sure you have data encrypted. You can only access it in the running rom. If you can't boot as you are now, flash no-verity-opt-encrypt and you can boot with that, even if encrypted. Boot up stock rom, use titanium or any other solution to backup your data and after that you can format data, boot unencrypted and restore the backups.
As for userdata dump, even if you dump it you can't decrypt it, also systemless root can't decrypt it either.
Sent from my SM-N950F using Tapatalk

corsicanu said:
I'm pretty sure you have data encrypted. You can only access it in the running rom. If you can't boot as you are now, flash no-verity-opt-encrypt and you can boot with that, even if encrypted. Boot up stock rom, use titanium or any other solution to backup your data and after that you can format data, boot unencrypted and restore the backups.
As for userdata dump, even if you dump it you can't decrypt it, also systemless root can't decrypt it either.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Right now I'm on stock(non-rooted, stock kernel) with the default encryption.
So I can just:
1. flash no-verity-opt-encrypt.zip
2. flash Magisk or SuperSU
3. Boot and have root with my encrypted data partition?
Thanks for fast answer btw
Edit; tried that, its booting, but now getting integrity verification failed screen. Even after flashing stock. So I guess I tripped some trusted execution environment and key is gone now.

I have one question to / problem with the encryption:
installed latest TWRP
flashed no-verity-opt-encrypt.zip in order being able to boot
formatted data
Everything works smoothly and as expected. BUT: How do I get the encryption (my company requires that) back now?
Out of the system I can select encrypt data, which is displaying 'Encrypting'. But after the automatic re-boot data is still not encrypted...
Am I missing something?

Phone keeps rebooting into "Galaxy S8" Welcome screen
Hi,
I have followed the process on my G950F but the phone keeps rebooting in a 10 second cycle into the welcome screen. Any ideas?
I am using Odin v3.13.1 and trying to load twrp-3.2.3-2-dreamlte.
I have enabled OEM unlock and it shows OEM LOCK: OFF in Download mode
I can successfully flash TWRP, wipe the DATA partition and transfer and install twrp-3.2.3-2-dreamlte.img. However, once I hit "reboot device" it keeps cycling into this welcome page.
Any ideas? I have tried going back to the official firmware and flashing twrp-3.2.3-1-dreamlte.img but the same happens. Is there anything I am missing?
EDIT: Solved by installing the no-verity-opt-encrypt-6.0.zip with TWRP

Related

[RECOVERY][ROOT]TWRP 3.1.0-1 Samsung Galaxy On8 SM-J710FN

Unofficial release -TWRP recovery for the Galaxy On8 - SM-J710FN, Exynos 7580
{
"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"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
INSTRUCTIONS FOR ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
Update 1/5/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
ADB backup
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
TWRP: twrp_3.1.0-1_sm-j710fn_29417
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, TeamWin, special thanks to my tester hhaawwkk
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
You did good job. If I helped you. hit a thank.
thank you
hhaawwkk said:
You did good job. If I helped you. hit a thank.
thank you
Click to expand...
Click to collapse
Added to credits.
It wud be great help if we could get a custom rom.
Sent from my Redmi Pro using Tapatalk
apna.suresh0305 said:
It wud be great help if we could get a custom rom.
Sent from my Redmi Pro using Tapatalk
Click to expand...
Click to collapse
try a j7 2015 rom and see if it boots
Oves786 said:
try a j7 2015 rom and see if it boots
Click to expand...
Click to collapse
Did anyone tried that..? I can't try without confirmation.
Sent from my Redmi Pro using Tapatalk
great mate.my props here
exynos 7580??typo mate ?
side said:
great mate.my props here
exynos 7580??typo mate ?
Click to expand...
Click to collapse
Typo? No why?
ashyx said:
Typo? No why?
Click to expand...
Click to collapse
isnt j710fn based on 7870 ? is it my fault ?
That's not for j710fn bro.. Maybe you mean j700f? J710fn is SG J7 2016
side said:
isnt j710fn based on 7870 ? is it my fault ?
Click to expand...
Click to collapse
No different device that is the J7. This is ON8.
Oves786 said:
try a j7 2015 rom and see if it boots
Click to expand...
Click to collapse
J700h is common with on8(exynos 7580) but it can't work without some changes. Main problem is meta inf folder (Update script).
We may take j700h custom rom for modify on8,s stock rom and port it into custom rom
hhaawwkk said:
J700h is common with on8(exynos 7580) but it can't work without some changes. Main problem is meta inf folder (Update script).
We may take j700h custom rom for modify on8,s stock rom and port it into custom rom
Click to expand...
Click to collapse
Try 1st if not installs then ill make meta folder for u
But 1st try and install
Guys can we keep it on topic and post rom talk below:
https://forum.xda-developers.com/galaxy-j7/help/samsung-galaxy-8-t3499001
@ashyx It will be great if you can also provide link to stock recovery, or any roll back steps to move to stock recovery.
Thanks in advance.
Link to Stock Recovery
Will the device status be official after rooting? I am worried about the updates.
bnayagrawal said:
Will the device status be official after rooting? I am worried about the updates.
Click to expand...
Click to collapse
Well not being funny but the clue is in the question.
TWRP = not official software.
Rooting = Unofficial modification
Knox = Tripped
Device status =?
ashyx said:
Well not being funny but the clue is in the question.
TWRP = not official software.
Rooting = Unofficial modification
Knox = Tripped
Device status =?
Click to expand...
Click to collapse
Well, that says it all. The only reason i wanted to root is substratum. But got to know that it wont work. And after getting nougat, root will not be required for substratum to work.
Do I need to unlock bootloader before flashing twrp or does odin do it itself? If I need to unlock it, how do I do it?

[ROM][9.0][berkeley][Official] Pixel Experience [AOSP][r44][10-07-2019]

{
"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"
}
PixelExperience for Honor View 10 [berkeley]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
NFC
Lights
Sound / vibration
Facelock
Known issues
Nothing
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from my mirror
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Telegram channel
Stay tuned​
XDA:DevDB Information
PixelExperience Pie, ROM for the Honor View 10
Contributors
Codebucket, jhenrique09, GtrCraft
Source Code: https://github.com/PixelExperience
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked Bootloader, EMUI 9
Based On: AOSP
Version Information
Status: Stable
Created 2018-11-14
Last Updated 2019-07-13
DON'T FLASH IF YOU ARE ALREADY ON EMUI 9, IT WON'T BOOT!!
IMPORTANT!
Before you start flashing, make sure you are using a version of TWRP with encryption disabled, otherwise you might end up using eRecovery to rescue your device from a bootloop!
You can also use official TWRP, but it will only work until you have not flashed the ROM!
Unofficial TWRP: https://storage.codebucket.de/public/twrp-3.2.2-0-berkeley.img
(That's not mine actually, I found that on Telegram and uploaded it to my mirror)
Flashing instructions from stock EMUI
Make sure you have TWRP installed and working!!
Reboot phone into recovery mode
Go to "Wipe" and select "Format data", then confirm with yes (some devices might require to disable encryption, see post #54)
Then go to "Advanced" and select /system, /data, /cache and Dalvik-cache for wipe
Copy ROM zip over to your phone (use whatever works for you, I personally use adb push)
Go to "Install" and select the ROM zip (and Magisk if you want), swipe to flash
Done! You can now reboot to system.
Update instructions
Simply go to TWRP and wipe /system, /cache and Dalvik-cache, then flash the update ROM zip and all additional stuff you need.
I also recommend having a backup of boot ramdisk to install Magisk again on a stock boot ramdisk.
Where is the source code of the device tree?
I combined all commits needed to run this ROM into one organization, you can inspect the source code here:
https://github.com/berkeley-pie
Device tree used for this ROM: https://github.com/divadsn/android_device_huawei_berkeley
My submitted patches: https://gerrit.pixelexperience.org/#/q/topic:huawei-derps+(status:open+OR+status:merged)
Special thanks go to @flex1911, @sirhc and @LuK1337 for your hard work, without your commits I wouldn't be able to get this ROM booting for the Honor View 10!
Where are the experimental builds gone?
They are still available on my mirror: https://mirror.codebucket.de/pixelexperience/berkeley/experimental/
But please be aware that those aren't official and you will loose OTA support!
Screenshots
Tried downloading about 6 times with different browsers. Fails at about 80m or so.
thecdn said:
Tried downloading about 6 times with different browsers. Fails at about 80m or so.
Click to expand...
Click to collapse
Try downloading using a download manager, Cloudflare sometimes looses connections.
Hi, is there a guide to follow for installing this rom? I read aosp and i thought to flash system.img through fastboot with stock recovery but i found many files and system is a .br file. Do i need twrp?
Thanks
How do you get this to boot? I have L09 and have wiped all partitions via twrp and stock recovery yet still bootlooping. I have even tried adb sideload and nothing.
passion8059 said:
How do you get this to boot? I have L09 and have wiped all partitions via twrp and stock recovery yet still bootlooping. I have even tried adb sideload and nothing.
Click to expand...
Click to collapse
You need to format data and remove encryption. The procedure is as follow: Download stock firmware using eRecovery, flash TWRP, format data in wipe, reboot TWRP and flash ROM.
Will include some instructions to the #2 post soon.
Codebucket said:
Flashing instructions
Reboot phone into recovery mode
Go to "Wipe" and select "Format data", then confirm with yes
Then go to "Advanced" and select /system and /data for wipe
Return back to home and go to "Settings" to enable "Remove instead formatting"
Go back to "Wipe" => "Advanced" and select /cache and Dalvik-cache to wipe
Reboot to recovery and connect to your PC via USB
Select "Advanced" and "Adb Sideload" to start flashing
On your PC open a terminal and type "adb sideload update.zip", hit enter
Now repeat that procedure if you want to flash Magisk
Done! You can now reboot to system.
Click to expand...
Click to collapse
So dalvik/art cache are to be removed and data and system are formatted?
'update.zip' is the generic name for your rom?
Do the rom and magisk have to be sideloaded? They can't be flashed via twrp?
thecdn said:
So dalvik/art cache are to be removed and data and system are formatted?
'update.zip' is the generic name for your rom?
Do the rom and magisk have to be sideloaded? They can't be flashed via twrp?
Click to expand...
Click to collapse
Update.zip is the placeholder, you have to type the path yourself to the downloaded file. Also sideload is a feature in TWRP.
Codebucket said:
IMPORTANT!
Before you start flashing, make sure you are using a version of TWRP with encryption disabled, otherwise you might end up using eRecovery to rescue your device from a bootloop!
Unofficial TWRP: https://storage.codebucket.de/public/twrp-3.2.2-0-berkeley.img
(That's not mine actually, I found that on Telegram and uploaded it to my mirror)
Flashing instructions
Reboot phone into recovery mode
Go to "Wipe" and select "Format data", then confirm with yes
Then go to "Advanced" and select /system and /data for wipe
Return back to home and go to "Settings" to enable "Remove instead formatting"
Go back to "Wipe" => "Advanced" and select /cache and Dalvik-cache to wipe
Reboot to recovery and connect to your PC via USB
Select "Advanced" and "Adb Sideload" to start flashing
On your PC open a terminal and type "adb sideload update.zip", hit enter
Now repeat that procedure if you want to flash Magisk
Done! You can now reboot to system.
Click to expand...
Click to collapse
but it keeps rebooting brother
Install Question
Very much curious, why couldn't we simply flash the rom through TWRP? Why through ADB Sideload? Just curious, since I've only ever used sideload for official ROMs, but never for custom ones Will try this out soon though! Love Pixel Experience ROMs! Thank you for the hard work!
Is volte working in this Rom?
Gesendet von meinem BKL-L09 mit Tapatalk
mgs250 said:
Very much curious, why couldn't we simply flash the rom through TWRP? Why through ADB Sideload? Just curious, since I've only ever used sideload for official ROMs, but never for custom ones Will try this out soon though! Love Pixel Experience ROMs! Thank you for the hard work!
Click to expand...
Click to collapse
You flash the ROM using ADB Sideload because the TWRP I have used has not working MTP, therefore I have no other way to copy the ROM over. But if you have a version of TWRP which works with Pie and has working MTP then go ahead
Tk19882401 said:
Is volte working in this Rom?
Gesendet von meinem BKL-L09 mit Tapatalk
Click to expand...
Click to collapse
No, there is no fix for that yet.
Ashinnazer said:
but it keeps rebooting brother
Click to expand...
Click to collapse
Have you formatted data and removed encryption?
Update available!
This is hopefully the last unofficial build, as I have pushed the patches made by flex1911 to PixelExperience Gerrit, so we can apply for official device status.
Oh and this build has fixed a derp I made when I cherry-picked a patch, sorry
Download: https://mirror.codebucket.de/pixele...nce_berkeley-9.0-20181116-0926-UNOFFICIAL.zip
Changelog: https://mirror.codebucket.de/pixele...ey-9.0-20181116-0926-UNOFFICIAL-Changelog.txt
(I also tweaked around with some NGINX settings to improve download stability )
Does this ROM work on BKL09 with EMUI Oreo 8.0?
sbtourist said:
Does this ROM work on BKL09 with EMUI Oreo 8.0?
Click to expand...
Click to collapse
Should work, but I can't guarantee, I use a BKL-L04.
Does wifi hotspot work?
Nice work! Working great on BKL-L04 flashed on top of GPU Turbo update.
Next update, should disable nav bar when registering fingerprint. Part of my thumb keeps hitting the home button.
Edit- after registering FP in security settings, device went black and became unresponsive.

[RECOVERY][OFFICIAL][3.6.1-x] TWRP for Galaxy Note9 Exynos

{
"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"
}
Official TWRP 3.6.1-* For Galaxy Note9 Exynos​Only for exynos variants - N960F (Single SIM: Europe, Australia); N960FD (Global Dual SIM: Europe, LATAM, Brazil; Australia); N960N (South Korea)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Features:
Code:
- built from Android 10 kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 9.0/10.0
Downloads:
https://twrp.me/samsung/samsunggalaxynote9.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Bixby Key+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Bixby key" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Bixby key" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
Device tree - https://github.com/TeamWin/android_device_samsung_crownlte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9810/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
File not found. 404.
BltLkATnk1972 said:
File not found. 404.
Click to expand...
Click to collapse
Try again now, page is up.
Is the Korean(N) version supported?

			
				
Thank YOU
Yeah Thanks ?
Thank you!
I'll try now.
Best
Finally official twrp for note 9
official twrp and official lineage os same month.. wow!! thank you!
Is this compatible with SM-N960F/DS purchased in Thailand? Thank you.
aZooZa said:
Is this compatible with SM-N960F/DS purchased in Thailand? Thank you.
Click to expand...
Click to collapse
Yes
Thank you very much!
Excellent, will give it a try tonight
Backup & Restore
Backup work but restore failed. Help me!
e2fsdroid -e -S /file_contexts -a /odm /dev/block/
sda20 process ended with ERROR: 1
Unable to wipe ODM
Corsicane, poate ma ajuti, thx!
Detonatte said:
Backup work but restore failed. Help me!
e2fsdroid -e -S /file_contexts -a /odm /dev/block/
sda20 process ended with ERROR: 1
Unable to wipe ODM
Corsicane, poate ma ajuti, thx!
Click to expand...
Click to collapse
Are you restoring a backup made with this specific twrp? If yes then try to reboot and then again try to restore. if it still fails please try to send /tmp/recovery.log to see what's happening.
Regards
Sent from my SM-G975F using Tapatalk
Do we still need to format partition after installing trwp ? if so what is the use of official status ? If we can update firmware and still can manage to install twrp without data loss, than its useful.

[RECOVERY][UNOFFICIAL] TWRP for Galaxy Note 20/Note 20 Ultra

Team Win Recovery Project 3.4.0​
{
"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"
}
Exynos ONLY.
In NO way it is compatible with Snapdragon variants including but not limited to American(U/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
Download: Note 20/Note 20 Ultra(Exynos variants)
Download
Sources:
Kernel source
TWRP source
Device Tree: Sorry are not under GPL License since are my own so they will not get released
Changelog:
03.09.2020
- V4 Release
- Twrp boots now without nulled Vbmeta.img
03.09.2020
- V3 Release
- Fixed Optics and Prism Backup and Restore
- Brightness is now no more at max
- CPEFS error is gone
- Sec-EFS added in the FStab
26.08.2020
- V2 Release that fixes Problems booting in TWRP (RKP was not disabled in kernel config)
24.08.2020
-Initial Release
Discord server for support:
https://discord.gg/BCHTXSQ
Bugs:
-MTP and Encryption (ADB PUSH WORKS when you disable mtp in TWRP mount settings!)
XDA:DevDB Information
[RECOVERY] TWRP for Galaxy Note 20/Note 20 Ultra, Kernel for the Samsung Galaxy Note 20 Ultra
Contributors
geiti94
Kernel Special Features:
Version Information
Status: Stable
Stable Release Date: 2020-09-03
Created 2020-08-24
Last Updated 2020-10-18
Guide:
Go to Developer settings and enable oem unlock
power off the device and boot in download mode with vol up+ vol down buttons and plug in the usb (make sure usb cable is connected to the pc)
in download mode you see the long press vol up option for unlock bl
unlock the bootloader (that will wipe your device so be sure you made a backup of your data)
after bootloader unlock boot up the phone and make sure it is connected to the internet or he triggers rmm prenormal
setup the phone without google account etc
reboot in download mode and flash twrp tar for your device with odin in the AP field
hold vol up + power button while odin is flashing until you are in twrp.
format data in twrp and disable encryption! (Encryption disabler is in download folder!)
Flash Latest Magisk
press reboot to system in twrp.
Kudos to you!
Will test tomorrow when get my device. Fun begins!
geiti94 said:
Guide:
Go to Developer settings and enable oem unlock
power off the device and boot in download mode with vol up+ vol down buttons and plug in the usb (make sure usb cable is connected to the pc)
in download mode you see the long press vol up option for unlock bl
unlock the bootloader (that will wipe your device so be sure you made a backup of your data)
after bootloader unlock boot up the phone and make sure it is connected to the internet or he triggers rmm prenormal
setup the phone without google account etc
reboot in download mode and flash twrp tar for your device with odin in the AP field
hold vol up + power button while odin is flashing until you are in twrp.
format data in twrp and disable encryption! (Encryption disabler is in download folder!)
Flash Latest Magisk
press reboot to system in twrp.
Click to expand...
Click to collapse
Is it compatible with super img. partitions? Does it mount /system, /data, etc?
Great! Number one!
rodrigofd said:
Is it compatible with super img. partitions? Does it mount /system, /data, etc?
Click to expand...
Click to collapse
Yes but flashables needs to be made for super partition
geiti94 Bro. You are Simply Outstanding and You Kick My Bro. Huge Thanks Buddy.
Dr Ketan My Bro. Thanks For All your Time and Hard Work.
Anyone tried this?
Mine doesn't boot to twrp
I could only wrong as recovery, in which I had created a tar that did not contain the vbmeta.
It doesn't start for me, German N986B, it gets stuck in the screen.
i had this issue i am stuck now with no rom
AboodySahhaf said:
i had this issue i am stuck now with no rom
Click to expand...
Click to collapse
Flash magisk patched AP file
dr.ketan said:
Flash magisk patched AP file
Click to expand...
Click to collapse
Can you give me the link of the method
AboodySahhaf said:
Can you give me the link of the method
Click to expand...
Click to collapse
Read my how to root thread in general section
I didn't got the TWRP to Work so next thing i did was :
OEM Unlock
Unlock Bootloader
Factory Reset (because of unlock bootloader)
Setup Device and install Magisk Manager.
Download Stock FW
Extract Boot.img
Put Boot.img on to phone.
Patch boot.img with magisk manager.
extract output file name it boot.img.
Create TAR file of boot.img (boot.tar)
Flash TAR file with Odin AP slot.
Now Succesfully rooted
Sigh... when we only got the Exynos variants here in Korea, TWRP was only released for Snapdragon. Now that Snapdragon is released in Korea, TWRP is only available for Exy XD
Still, job well done~
@geiti94
Last test version you sent me booted fine. Testing further now :good:
:good:
so twrp is fixed. thx to @dr.ketan for testing it since i dont got the n20 since is like a downgrade for me (i still love the 5000mah battery of my s20 ultra). i see next month if get it or not. was my fault that twrp dont booted because on n20 kernel config i forgot to disable rkp
Code:
You've sent *** CHF to [email][email protected]*com[/email]
@geiti94 Here small token of appreciation kindly accept. Request users to support geiti for more development & his well deservet efforts!
Regards
dr.ketan said:
@geiti94
Last test version you sent me booted fine. Testing further now :good:
Click to expand...
Click to collapse
Thank you guys.
Does backup/restore work?

[ROM][Android 12L][BERYLLIUM] crDroid v8.12 [19.12.2022]

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.1/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (from download page, recovery button)
NikGapps core (Download from here - note that you may also need setup wizard addon if you rely on Google restore)
Magisk root (after first boot)
First time installation:
Backup your data to PC, OTG flash drive
Boot to fastboot and flash recovery
Code:
fastboot flash recovery recovery.img
Now boot to recovery by holding VOL UP + POWER
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
If you are running with gapps, choose again to apply from adb and sideload gapps.zip
Reboot to system
Update installation:
Via recovery
Boot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
Via OTA:
Go to Settings -> System -> Updater and download latest build
Choose install and let it finish
Reboot
Do note that crDroid 8 is encrypted by default, so if you want to run decrypted, you'll need to sideload dfe.zip
Sources:
ROM: https://github.com/crdroidandroid
Kernel source: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm845
Download:
ROM https://crdroid.net/beryllium
Known isues:
- none critical
Visit official website @ crDroid.net
crDroid Poco Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
The installation worked liked charm. Thank you so much!!
Thanks for your work Gabriel! Wonderful, I'm glad the ROM is finally encrypted by default
Bug: Bluetooth is trying to turn on and off, repeatedly.
Overall, it feels like a LOS developer build with unlocked features.
HI GWOLFU TNX IN ADVANCE
im not be able to root
flash latest magisk apk or zip no difrens beetwin apk and zip
Sia_scazy said:
HI GWOLFU TNX IN ADVANCE
im not be able to root
flash latest magisk apk or zip no difrens beetwin apk and zip
Click to expand...
Click to collapse
Needs magisk canary
That has support for A12
a9k1t said:
Bug: Bluetooth is trying to turn on and off, repeatedly.
Overall, it feels like a LOS developer build with unlocked features.
Click to expand...
Click to collapse
Aware from telegram chat
Will try to fix with next update
Thanks
Best rom.
Thanks gwolfu! I'd love to upgrade this week, but I've got a few questions first:
Is a dirty flash upgrade from crDroid 7 supported?
I had issues with nikgapps before, with the signal app not receiving any messages unless I open the app (nikgapps specific issue). I'd like to try bitgapps instead. your rom should also work well with that gapps pack, right?
I use encrypted f2fs data partition right now. is that also supported by this crdroid 8 build? or do I have to update the fstab again?
Does it pass safetynet (with/without magisk)?
Oehr said:
Thanks gwolfu! I'd love to upgrade this week, but I've got a few questions first:
Is a dirty flash upgrade from crDroid 7 supported?
I had issues with nikgapps before, with the signal app not receiving any messages unless I open the app (nikgapps specific issue). I'd like to try bitgapps instead. your rom should also work well with that gapps pack, right?
I use encrypted f2fs data partition right now. is that also supported by this crdroid 8 build? or do I have to update the fstab again?
Does it pass safetynet (with/without magisk)?
Click to expand...
Click to collapse
1. Not possible to dirty flash
2. Should work with other gapps (I just shared what I used, however not tested by me)
3. F2FS data is not added yet due to some bug I've noticed
4. Passed SN out of the box even without magisk
Build 20200124 is up
Changelog
- Fixed bluetooth issues
There is an issue with the recovery: it does not automount the micrsod card. manually mounting using adb shell works, but as I am not sure where to mount it, I have no means of applying the update from the microsd card.
P.S. I am using a 1TB microSD card with a single exfat partition
gwolfu said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
Recovery (here)
NikGapps core (Download from here)
Magisk root (after first boot)
First time installation:
Backup your data to PC, OTG flash drive
Boot to fastboot and flash recovery
Code:
fastboot flash recovery recovery.img
Now boot to recovery by holding VOL UP + POWER
Navigate to Factory reset and format data, wipe cache and wipe system
Now reboot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
If you are running with gapps, choose again to apply from adb and sideload gapps.zip
Reboot to system
Update installation:
Boot to recovery
Navigate to Apply update and choose from adb (if you have crDroid.zip on external sdcard, you may choose this option and navigate to where the zip is)
Now sideload crDroid zip
Code:
adb sideload crDroid.zip
Do note that crDroid 8 is encrypted by default, so if you want to run decrypted, you'll need to sideload dfe.zip
Sources:
ROM: https://github.com/crdroidandroid
Kernel source: https://github.com/crdroidandroid/android_kernel_xiaomi_sdm845
Download:
ROM https://crdroid.net/beryllium
Known isues:
- none critical
Visit official website @ crDroid.net
crDroid Poco Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal
Click to expand...
Click to collapse
Bug bluetooth.....not working
wladoom said:
Bug bluetooth.....not working
Click to expand...
Click to collapse
Works fine for me with Build 20200124:
gwolfu said:
Build 20200124 is up
Changelog
- Fixed bluetooth issues
Click to expand...
Click to collapse
gwolfu said:
1. Not possible to dirty flash
2. Should work with other gapps (I just shared what I used, however not tested by me)
3. F2FS data is not added yet due to some bug I've noticed
4. Passed SN out of the box even without magisk
Click to expand...
Click to collapse
as for bitgapps: doesn't work. It fails mounting the vendor partition. tried nikgapps now and receiving message in signal seems to work for now. only time will tell!
as for f2fs, the mounting parameters for encryption differ. I didn't check out the fstab yet, but for crdroid 7, I had to remove the ext4 mount for /data and leave only f2fs with the following permissions in there:
Code:
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,background_gc=off,fsync_mode=nobarrier latemount,wait,fileencryption=ice,quota
And even then it was wonky: it only worked when the data partition was COMPLETELY empty, so that encryption was enabled on first boot. encrypting afterwards failed. Maybe that helps you in troubleshooting f2fs support for data.
P.S. Unless it goes mainline again, I'll stick with the current ext4 variant, as I had to patch fstab every time I updated the rom back with crdroid 7...
Hey, huge thanks for crDroid, currently on 7.13, will flash 8 this weekend. I've noticed that when hiding nav bar, the back gesture doesn't work anymore and haven't find out how to fix this (7.13 version though). Did I miss something ?
Oehr said:
Works fine for me with Build 20200124:
as for bitgapps: doesn't work. It fails mounting the vendor partition. tried nikgapps now and receiving message in signal seems to work for now. only time will tell!
as for f2fs, the mounting parameters for encryption differ. I didn't check out the fstab yet, but for crdroid 7, I had to remove the ext4 mount for /data and leave only f2fs with the following permissions in there:
Code:
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,background_gc=off,fsync_mode=nobarrier latemount,wait,fileencryption=ice,quota
And even then it was wonky: it only worked when the data partition was COMPLETELY empty, so that encryption was enabled on first boot. encrypting afterwards failed. Maybe that helps you in troubleshooting f2fs support for data.
P.S. Unless it goes mainline again, I'll stick with the current ext4 variant, as I had to patch fstab every time I updated the rom back with crdroid 7...
Click to expand...
Click to collapse
you can't encrypt afterwards
you either do it at first boot (does that automatically in crDroid 8), or you flash DFE and no encryption from there on
also no real benefits in F2FS imo
gwolfu said:
you can't encrypt afterwards
you either do it at first boot (does that automatically in crDroid 8), or you flash DFE and no encryption from there on
also no real benefits in F2FS imo
Click to expand...
Click to collapse
f2fs has been specifically developed for flash memory. it comes with fs-based wear leveling which is great for flash memory without a proper flash controller (microsd cards, emmc, etc.). Some more recent android phones (e.g. pixel 6, poco x3) use f2fs as its default fs for the data (and cache) partition.
Makigo123 said:
Hey, huge thanks for crDroid, currently on 7.13, will flash 8 this weekend. I've noticed that when hiding nav bar, the back gesture doesn't work anymore and haven't find out how to fix this (7.13 version though). Did I miss something ?
Click to expand...
Click to collapse
do not disable nav bar. switch to gesture bar and set its size to compact and/or disable navigation hint instead. i stumbled into the same "issue" in crdroid 8, until i figured out that I was doing it wrong. It is confusing, as all these options are split between basically three different screens.
Oehr said:
do not disable nav bar. switch to gesture bar and set its size to compact and/or disable navigation hint instead. i stumbled into the same "issue" in crdroid 8, until i figured out that I was doing it wrong. It is confusing, as all these options are split between basically three different screens.
Click to expand...
Click to collapse
Thanks, you made my day brighter
Unfortunately, I have the issue with receiving message in the Signal app again: After a while, especially while not charging, signal stops receiving messages on the phone unless I specifically open the signal app again...
I checked the usual culprits, such as battery optimization and such, but everything checks out... I had the issue before with crdroid back when I also tried nikgapps... There was no issue when I later switched to opengapps, but that is not possible for now.
Any clue as to how to fix this? I really don't want to check my signal app all the time
Oehr said:
Unfortunately, I have the issue with receiving message in the Signal app again: After a while, especially while not charging, signal stops receiving messages on the phone unless I specifically open the signal app again...
I checked the usual culprits, such as battery optimization and such, but everything checks out... I had the issue before with crdroid back when I also tried nikgapps... There was no issue when I later switched to opengapps, but that is not possible for now.
Any clue as to how to fix this? I really don't want to check my signal app all the time
Click to expand...
Click to collapse
issue is with nikgapps
should be fixed in latest build released today
if dirty flashing new gapps on top, do also clear app data of Google Play Services app and reboot after dirty flash done and booted

Categories

Resources