{
"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:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.
FEATURES
* Supports Treble and non-Treble ROMs
* Increased compatibility with TWRP
* Updated with latest TWRP commits
* Built-in support for installing init.d functionality
* Built-in support for installing Magisk
* AromaFM
* Password
* Better language support
* Optimized versions of community scripts
* Fox theme engine:
- choice of theme (black, dark, etc)
- choice of color scheme
- choice of splash screen
* Alternative lockscreen
* And many more!
Downloads:
https://github.com/roynatech2544/OrangeFox_Recovery_A20e/releases
Bugs:
adb sideload
Credits
* TeamWin - for TWRP
* The OrangeFox Team - for your hard work
Contributors
XynXDotnest for providing the prebuilt images (I forked his twrp tree)
( @Mijotchi Sorry For Not crediting you)
@physwizz for the awesome kernel
(This Recovery is based on physwizz's kernel)
(Reference: https://forum.xda-developers.com/galaxy-a20/development/a20e-testers-t4183683 )
Source Code: https://gitlab.com/OrangeFox
Device-tree: https://github.com/roynatech2544/OrangeFox_Recovery_A20e
P.S. Please write a review about this recovery if it worked on your phone. I'm trying to get it official but the progress has been stopped because of lack of feedbacks
Great job
This recovery works greatly on my a20e. Everything works well. MTP is still bit buggy.
P.S. What is "Have you lost something?" on the top of recovery menu?
whiteshell said:
This recovery works greatly on my a20e. Everything works well. MTP is still bit buggy.
P.S. What is "Have you lost something?" on the top of recovery menu?
Click to expand...
Click to collapse
Have you tried the kernel
https://forum.xda-developers.com/galaxy-a20/development/a20e-testers-t4183683
physwizz v1.60 A20e (SM-a202xx)
@physwizz
-Most securities disabled
-CPU Governors: conservative, ondemand, userspace, powersave, interactive, performance.
-Interactive is default governor
-SE linux enforcing
-CPU overclocked and underclocked
-Big: 208 - 2184
-Little: 208 - 1690
-GPU: 343 - 1300
-Extended battery life
-Works with Magisk 21
-Spectrum support enabled
-1.61mb dtbo.img (Thanks to geckyn & Chatur for dtbo config method)
CAN YOU PLEASE LET ME KNOW IF IT WORKS?
A20e Root,Kernel, TWRP and custom ROM
Root & TWRP from Xyn XDotnest https://forum.xda-developers.com/galaxy-a20/development/recovery-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767 Orange Fox Recovery from @Royna...
forum.xda-developers.com
Great job man! Now I can backup/restore on my a20e (SM-A202F/DS) no decryption issues, magisk works just fine on stock ROM. I still can't get to flash any custom ROMs from recovery, tried with combinations of Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip and GSI_Fix_boot.zip also, but I get some mount error, and the no OS installed warning when rebooting After that, I can only do wipes, reboot to recovery, format, then I can try to flash ROMs again
The only ROM I was able to flash was an AOSP, but was using the TWRP guide for a20e, with no fox recovery. Don't know if is related to my phone model, all I do from scratch is:
Flash stock ROM with Odin (bootloader already unlocked)
Boot Android q, finish setup and enable USB debug.
Turn off the phone and boot into recovery
handycup said:
Great job man! Now I can backup/restore on my a20e (SM-A202F/DS) no decryption issues, magisk works just fine on stock ROM. I still can't get to flash any custom ROMs from recovery, tried with combinations of Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip and GSI_Fix_boot.zip also, but I get some mount error, and the no OS installed warning when rebooting After that, I can only do wipes, reboot to recovery, format, then I can try to flash ROMs again
The only ROM I was able to flash was an AOSP, but was using the TWRP guide for a20e, with no fox recovery. Don't know if is related to my phone model, all I do from scratch is:
Flash stock ROM with Odin (bootloader already unlocked)
Boot Android q, finish setup and enable USB debug.
Turn off the phone and boot into recovery
Click to expand...
Click to collapse
Try here too
A20e Root,Kernel and TWRP
physwizz said:
Try here too
A20e Root,Kernel and TWRP
Click to expand...
Click to collapse
Sorry but I don't know how to proceed, I'm using stock ROM and using fox recovery, what I have to do next? I gave a try flashing UltimateQ_s21_port_V9, but get stuck with no errors, maybe some magisk conflict with the magisk present in the recovery? It was the last line in the log. Maybe I'm flashing things in wrong order, or I need some specific file/tweak for my device. I get a lot of errors about vendor when flashing or mounting, when I start from scratch, I flash stock ROM with Odin, and I flash all the sections, including home, then I flash recovery with Odin.
handycup said:
Sorry but I don't know how to proceed, I'm using stock ROM and using fox recovery, what I have to do next? I gave a try flashing UltimateQ_s21_port_V9, but get stuck with no errors, maybe some magisk conflict with the magisk present in the recovery? It was the last line in the log. Maybe I'm flashing things in wrong order, or I need some specific file/tweak for my device. I get a lot of errors about vendor when flashing or mounting, when I start from scratch, I flash stock ROM with Odin, and I flash all the sections, including home, then I flash recovery with Odin.
Click to expand...
Click to collapse
try the link to the ROM on this page.
A20e Root,Kernel and TWRP
Try a different TWRP
I found Orange Fox to have some issues
physwizz said:
try the link to the ROM on this page.
A20e Root,Kernel and TWRP
Try a different TWRP
I found Orange Fox to have some issues
Click to expand...
Click to collapse
I tried TWRP 3.4 by @Topser99 worked fine, then flashed Orange Fox on top in case of compatibility issues with backup's. Now backup starts with no errors but get stuck during process, also happened the same installing Ultimate Q S21, V3 and V9. I was able to install AOSP V10 and V11, I just had to wipe only caches data and system, then flash the ROM without flashing any other file
I'm going to run some other test with other TWRP's, I still have some issues with Magisk, with a Superuser app prompt saying the app is obsolete, but can't update with Google Play Store. But roots seems to work fine, just the notification is a little boring
I can't believe to see running the latest treble available (11) on my device, using the GO version with little Google on it for low RAM devices. Still don't know what ROM to use for daily basis, is Android 11 stable for a20e devices, or better stick with V10? Custom ROM's I still wasn't able to flash/boot one, and I'm worried about privacy and lack's of future updates, have you tried some good ROMs?
handycup said:
I tried TWRP 3.4 by @Topser99 worked fine, then flashed Orange Fox on top in case of compatibility issues with backup's. Now backup starts with no errors but get stuck during process, also happened the same installing Ultimate Q S21, V3 and V9. I was able to install AOSP V10 and V11, I just had to wipe only caches data and system, then flash the ROM without flashing any other file
I'm going to run some other test with other TWRP's, I still have some issues with Magisk, with a Superuser app prompt saying the app is obsolete, but can't update with Google Play Store. But roots seems to work fine, just the notification is a little boring
I can't believe to see running the latest treble available (11) on my device, using the GO version with little Google on it for low RAM devices. Still don't know what ROM to use for daily basis, is Android 11 stable for a20e devices, or better stick with V10? Custom ROM's I still wasn't able to flash/boot one, and I'm worried about privacy and lack's of future updates, have you tried some good ROMs?
Click to expand...
Click to collapse
rom custom or gsi, I use only to test things. But for daily use, I use the stock
Topser99 said:
rom custom or gsi, I use only to test things. But for daily use, I use the stock
Click to expand...
Click to collapse
I tried debloating before messing with ROMs, but then system felt unstable... what can I do, to let things more secure? A bit worried using pay apps on rooted phone.
I just tested your TWRP 3.5, flashed AOSP 11 + backup/restore, everything's works, great job!
Still no luck installing Magisk atm
EDIT: With AOSP V10 Magisk works too!
handycup said:
I tried debloating before messing with ROMs, but then system felt unstable... what can I do, to let things more secure? A bit worried using pay apps on rooted phone.
I just tested your TWRP 3.5, flashed AOSP 11 + backup/restore, everything's works, great job!
Still no luck installing Magisk atm
Click to expand...
Click to collapse
You try flash Magisk A11 PATH_max first then flash magsik
root - Google Drive
drive.google.com
Topser99 said:
You try flash Magisk A11 PATH_max first then flash magsik
root - Google Drive
drive.google.com
Click to expand...
Click to collapse
Thanks man! With AOSP V10 Magisk works just fine, don't know if it's safe to switch to V11 regarding stability, if it's ok, how can I use those files? (MagiskA11_PATH_fix, multidisabler-samsung-3.2b5)
handycup said:
Thanks man! With AOSP V10 Magisk works just fine, don't know if it's safe to switch to V11 regarding stability, if it's ok, how can I use those files? (MagiskA11_PATH_fix, multidisabler-samsung-3.2b5)
Click to expand...
Click to collapse
It fixes init.rc
Topser99 said:
It fixes init.rc
Click to expand...
Click to collapse
I'm not sure if I still need to flash multidisabler-samsung-3.2b5, or it's already included in TWRP (I'm using Twrp-3.5.0-blue-sm-a202dd).
handycup said:
I'm not sure if I still need to flash multidisabler-samsung-3.2b5, or it's already included in TWRP (I'm using Twrp-3.5.0-blue-sm-a202dd).
Click to expand...
Click to collapse
Keep it for use when you flash your stock.
Topser99 said:
Keep it for use when you flash your stock.
Click to expand...
Click to collapse
So I have to flash multidisabler-samsung before flashing ROM?
Edit: I tried to: format-flash multi-disabler-flash AOSP V11 ROM. When I try login to google, play store come black and freeze. I tried Gapps version and Gapps vndklite, same beaviour. Magisk give me some mounting error, after flashing in TWRP
Edit2: It's working! Flashed multidisabler, AOSP V11 (vanilla),NikGapps, fix for Magisk, Magisk 22, and the Magisk apk after reboot.
I had issues flashing anything after flashing ROM step, I had to boot Rom first, then I can continue flashing with no errors
I have an issue. After flash, Orange fox stuck in start screen. How can I do?
how do i uninstall multidisabler-samsung-3.2b5 it removed fbe which i need. now i cant remove it. WILL U STOP DISABLEING ENCRYPTION
Related
{
"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 Note8 Exynos​Only for exynos variants - N950F (Single SIM: Europe, Australia); N950FD (Global Dual SIM: Europe, LATAM, Brazil; Australia); N950N (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:
https://twrp.me/samsung/samsunggalaxynote8.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_greatlte
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.
No Download. Img file?
corsicanu said:
TWRP
Click to expand...
Click to collapse
Well done mate
Benny100 said:
No Download. Img file?
Click to expand...
Click to collapse
Its directly in the github link
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Benny100 said:
No IMG file
https://github.com/TwrpBuilder/android_device_samsung_greatlte/releases
https://github.com/TwrpBuilder/android_device_samsung_greatlte/tags
Click to expand...
Click to collapse
Did you tried taping on Assets?
Found and is working Thx!...
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
tabish84 said:
I am using a modified twrp without data fix problem. Should i just flash the image file or i have to format data and setup from zero
Click to expand...
Click to collapse
datafix is for oreo issues where twrp could not properly access internal storage.
format is if you come from stock rom and still have encrypted storage.
Very nice start of the Note 8 Exy journey Bro ?
It is a big pleasure to see U around N8 development!
I am really excited now for the nearest few months and Your 'crazy' ideas which always bring some goodies ?
Thx for Ur efforts and good luck! ?
Works great thank you.
Dev Base August
Sent from my SM-N950F using XDA Labs
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Pinan said:
After flashing .img (was on 3.2.1.1) I get "Recovery is not seandroid enforcing", only when booting into recovery.
Seems to work fine otherwise.
N950N
Repulsa's ROM.
Is this normal behavior?
Click to expand...
Click to collapse
im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
bober10113 said:
1. im on the same phone and no such issue with new twrp i was on a newer twrp than yours and had formatted and flash dm verty zip initially from stock oreo. dirty flash your rom again just to see. if still no go then follow OP to the T to reflash it correctly.
2. did you ever flash oreo bootloader? because from what i understand, looks like you were on nougat before and flashed a oreo rom without upgrading fully to stock oreo before hand.
Click to expand...
Click to collapse
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Pinan said:
1. I went from stock rom to Repulsa, using SuperSU. No issues.
2. Nougat to Oreo. Could be the issue. I did not update the BL. Don't know if the ROM did. I will check.
Do you happen to have a link to the correct BL?
Thanks for the tips!
Click to expand...
Click to collapse
i could extract it but u can basically get it from unziping stock.(see link below)
since we are on the n950n, I'm almost sure repulsa rom didnt update it because mostly all roms that might include the BL will have mainly the F/DS bootloader, most dont even update it though.
latest BL would be U3. might be a good idea to update cp(modem) while you are at it too, so grab latest stock firmware and extract both from:
https://samsung-firmware.org/model/SM-N950N/
if download is slow, i can provide these 2 files in a few minutes because package is so big just to get them smaller files.
so only put bl and cp in odin and at least you will be on the latest stuff. dont know what is taking so long for BL U4 to arrive for our korean n950ns....
edit
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
bober10113 said:
latest bl and cp for N950N only:
https://1drv.ms/f/s!AhXVLDDj8g3AgdYhY8DslnHgCVMMEw
i also put samfirm downloader for future reference, its a fast way to get latest firmware. those hosting websites are so slow sometimes... updato.com is a fast one but firmwares arent always up to date though
Click to expand...
Click to collapse
Thank you very much. Most kind of you. :good:
Yes. I've used SamFirm before. Faster indeed.
@ bober10113.
All's well after new CP and BL. no more "Recovery is not seandroid enforcing".
Thanks again.
Good job mate :good:
Really glad we have this dev around. Will flash shortly
{
"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"
}
After @geiti94 and @ianmacd started the ball rolling for the Samsung Galaxy S10 series (Exynos 9820), it was really only a matter of time until we could do the same for the 2019 Galaxy Tab A 10.1 (Exynos 7904). The kernel source was released last May, allowing me to build a custom kernel with many of the problematic Knox security features disabled. What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and rely on the latest posted kernel source (T510XXU5CWA1).
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
twrp-3.7.0_11-0-T510XXU5CWA1-20230330.tar.md5
twrp-3.7.0_11-0-T510XXU5CWA1-20230330.img
Build archives:
Android File Host
Change Log:
v3.7.0_11-0 (20230330):
Updated to T510XXU5CWA1 OEM stock kernel.
v3.7.0_11-0 (20221102):
Updated to TWRP 3.7.0 release built from AOSP-11 branch.
v3.6.2_11-0 (20220905):
Updated to TWRP 3.6.2 release built from AOSP-11 branch.
Updated to T510XXU5CVG2 OEM stock kernel.
v3.6.1_11-1:
Minor update to incorporate fix from TWRP repo.
v3.6.1_11-0:
Updated to TWRP 3.6.1 release built from AOSP-11 branch.
Updated to T510XXU5CVB1 OEM stock kernel.
v3.6.0_11-2:
Updated to T510XXU5CUL1 posted kernel source.
v3.6.0_11-1:
Updated to T510XXU5CUJ1 posted kernel source.
Updated to TWRP 3.6.0 release built from aosp-11 branch.
v3.5.2_9-0:
Updated to T510XXU5CUF4 posted kernel source.
v3.5.2_9-0:
Updated to TWRP 3.5.2 release built from omni-9.0 branch.
v3.5.1_9-0:
Updated to T510XXU4BUA1 posted kernel source.
Updated to TWRP 3.5.1 release built from omni-9.0 branch.
v3.5.0_9-0:
Updated to T510XXU3BTK1 posted kernel source.
Updated to TWRP 3.5.0 release built from omni-9.0 branch.
v3.4.0-0:
Updated to TWRP v3.4.0 source
Updated to latest custom kernel
v3.3.1-7:
Updated to latest custom kernel
v3.3.1-6:
Switched to .img file for installation from TWRP
v3.3.1-5:
Fixed hang on splash with encrypted user data partition
Added OTA update (.zip) for installation from TWRP
v3.3.1-4:
Fixed MTP support in a way that supports Magisk
v3.3.1-3:
Fixed MTP support
Included boot image with custom kernel
Deprecated separate NoKnox releases
v3.3.1-2:
Changed system partition mount point to /system_root
Fixed screen brightness control
Restored screen timeout
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to system
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. More details on this process are available from @ianmacd's topic for the Galaxy S10 series here.
Source:
android_device_samsung_gta3xlwifi
android_device_samsung_gta3xl
Donations:
Your support is always appreciated! Just click here.
Good work. Well done.
Great stuff! I've received the device today, although I'm willing to test this recovery, it maybe better to wait a bit longer for a patched kernel/ROM instead? From my understanding this prevents the needs of booting in recovery every time to start the tablet and may be better to prevent Samsung/KNOX from bricking this device.
If this is untrue, please let me know and I'll remove this post asap.
Also let me know if you need any (debug) info.
beta990 said:
Great stuff! I've received the device today, although I'm willing to test this recovery, it maybe better to wait a bit longer for a patched kernel/ROM instead? From my understanding this prevents the needs of booting in recovery every time to start the tablet and may be better to prevent Samsung/KNOX from bricking this device.
Click to expand...
Click to collapse
NoKnox above will patch the T510XXU1ASC7 OEM firmware with the custom kernel and includes the vendor partition fixes in @ianmacd's Multi-disabler. Booting to recovery each time is only required with the Magisk root, which patches itself into recovery (TWRP or stock). More details on @ianmacd's post here.
Thanks for this! I successfully flashed NoKnox, TWRP and Magisk last night and all is working well! @PiCkLeS posted some helpful instructions here for those needing some extra help. Follow the instructions in this thread, but replace the last step with flashing your Magisk-patched TWRP image. No need to mess with running magisk on the stock AP file, you can just modify the TWRP recovery.img.
Magendanz said:
[*]Ensure you're running the T510XXU1ASC7 release
Click to expand...
Click to collapse
I just received the tablet and it's running T510XXU1ASCE, I suppose I should downgrade first, if possible, or will it work as-is?
3c said:
I just received the tablet and it's running T510XXU1ASCE, I suppose I should downgrade first, if possible, or will it work as-is?
Click to expand...
Click to collapse
Unfortunately, they've only posted the source for T510XXU1ASC7 at this point, so that's what we're stuck with. The safe bet is to downgrade (especially since NoKnox includes a modified vendor partition), but I wouldn't be surprised if you can mix and match these two versions.
Note: I see that the May 2019 update (T510XXU1ASCF) is already available. I've put in a request for the kernel source to be posted.
Magendanz said:
Unfortunately, they've only posted the source for T510XXU1ASC7 at this point, so that's what we're stuck with. The safe bet is to downgrade (especially since NoKnox includes a modified vendor partition), but I wouldn't be surprised if you can mix and match these two versions.
Note: I see that the May 2019 update (T510XXU1ASCF) is already available. I've put in a request for the kernel source to be posted.
Click to expand...
Click to collapse
Thanks, downgrading from ASCE worked very well, had to change OEM unlock in dev settings again though (with the date trick).
@Magendanz, l'm willing to test twrp for the 515 model. Dm me ?
I did a backup and did a restore but it kept bootlooping idk if this was because i rooted it first or what..
They released the latest kernel
Awesomeslayerg said:
They released the latest kernel
Click to expand...
Click to collapse
Yep, it's already downloaded and I'm building the kernel tonight. Unfortunately, we didn't get the May 2019 update for SM-T515 (T515XXU1ASEH).
Magendanz said:
Yep, it's already downloaded and I'm building the kernel tonight. Unfortunately, we didn't get the May 2019 update for SM-T515 (T515XXU1ASEH).
Click to expand...
Click to collapse
hello, thanks for your work, i'm building twrp for a device with the same soc [7904], i was wondering does disabling [proca] is a must to boot twrp ? if it's can you provide changes you have made to vendor partition to remove it
regards
edit: ok i see that you remove the init file for proca service [pa_daemon_teegris.rc] so my question now is, does using a custom kernel in boot image is a must ? i already use one in twrp with most of the security features such as defex/proca/samsung restrictions..etc disabled and if possible can you provide the used kernel source or used defconfig ?
messi2050 said:
hello, thanks for your work, i'm building twrp for a device with the same soc [7904], i was wondering does disabling [proca] is a must to boot twrp ? if it's can you provide changes you have made to vendor partition to remove it
Click to expand...
Click to collapse
I just manually perform everything that @ianmcd's multi-disabler script does to the vendor partition.
messi2050 said:
ok i see that you remove the init file for proca service [pa_daemon_teegris.rc] so my question now is, does using a custom kernel in boot image is a must ? i already use one in twrp with most of the security features such as defex/proca/samsung restrictions..etc disabled and if possible can you provide the used kernel source or used defconfig ?
Click to expand...
Click to collapse
Yes, you've got to build a custom kernel to disable Samsung's rooting restriction features. The custom defconfig is here.
Magendanz said:
I just manually perform everything that @ianmcd's multi-disabler script does to the vendor partition.
Yes, you've got to build a custom kernel to disable Samsung's rooting restriction features. The custom defconfig is here.
Click to expand...
Click to collapse
Been trying for a week now, still it bootloop at every attempt to enter twrp according to the testers.. not sure what's wrong, I'm building using twrp minimal source also custom kernel works good on stock rom so no idea where is the problem
Are there any release for SM-T515?
b2574028 said:
Are there any release for SM-T515?
Click to expand...
Click to collapse
I have a volunteer to test it, but I was waiting for Samsung to post kernel source for the May 2019 update (T515XXU1ASEH).
'Only official released binaries are allowed to be flashed'
Thank you for this great work. I ended up getting the 'Only official released binaries are allowed to be flashed' at booting after flashing:
- NoKnox-T510XXU1ASEF.tar
- twrp-3.3.1-1-gta3xlwifi.tar
After the flash, the tablet successfully booted into new factory status OS. Once the intial setup was done and rebooted, the phone is just soft bricked with the message. Any idea what I've done wrong?
Thank you very much in advance.
redexit said:
After the flash, the tablet successfully booted into new factory status OS. Once the initial setup was done and rebooted, the phone is just soft bricked with the message. Any idea what I've done wrong?.
Click to expand...
Click to collapse
That's Samsung's VaultKeeper "feature". To workaround it, you've got to connect to the Internet and enable Developer Options after setup.
So to recover, just flash the stock OEM firmware package with Odin, repeat the steps you took, and be sure this time to enable Developer Options and verify that OEM Unlocking is enabled. (It should also be grayed out, since the bootloader is already unlocked.)
And if you want to more permanently disabled VaultKeeper, I have a modified version of @ianmcd's multi-disabler script for the SM-T510 that you can install in TWRP.
Thank you!
Magendanz said:
That's Samsung's VaultKeeper "feature". To workaround it, you've got to connect to the Internet and enable Developer Options after setup.
So to recover, just flash the stock OEM firmware package with Odin, repeat the steps you took, and be sure this time to enable Developer Options and verify that OEM Unlocking is enabled. (It should also be grayed out, since the bootloader is already unlocked.)
And if you want to more permanently disabled VaultKeeper, I have a modified version of @ianmcd's multi-disabler script for the SM-T510 that you can install in TWRP.
Click to expand...
Click to collapse
Whoa, thank you so much for your quick and thorough reply!
I will do what you instructed after another 7 days I guess, (assuming there is no way to get around with this one).
Again I truly appreciate your contribution and hard work.
{
"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
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.2.3
PitchBlack version: 2.9.0
For device: U12+/Exodus1
Maintainer/Authors build: @JEANRIVERA @mikalovtch
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/jeanrivera/android_device_htc_ime
PitchBlack Team: @rezaadi0105, @firewolfxda, @manjot.gni, @androiabledroid, Arbaz Khan
Features
Supports Treble and non-Treble ROMs
Up-to-date Oreo kernel, built from sources (Pie is on the way)
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Temp boot Instructions
Download the PitchBlack img to your computer
Reboot to bootloader
Code:
fastboot boot recovery_name.img
The device will automatically reboot into PitchBlack Recovery
Enjoy
Permanent Install instructions
Download the PitchBlack img to your device
temp boot in TWRP or PBRP
install / install image bottom right corner / select PBRP.img / install recovery ramdisk
if you are rooted with Magisk remember to flash Magisk after install Recovery ramdisk
if your Kernel is stock flash touchscreen_hexpatcher.zip
Reboot to Recovery & Enjoy
Changelog
Code:
v2.9.1
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Known Issues
All Official TWRP Issues (not many)
Aroma not supported on U12+ / Exodus 1
Stock ROM Pie Decryption currently not possible (workaround disable Force Encrypt NOT Recommended if you want your device to be secured, your device your option
You Tell me
Downloads
https://sourceforge.net/projects/pitchblack-twrp/files/ime/
Additional Downloads
Touchscreen hexpatcher | Mirror (AFH) - SEE IMPORTANT NOTES BELOW:
Only needed when on stock kernel without touchscreen fix
Flashing touchscreen_hexpatcher.zip will make touch work when using stock kernel but render all recovery related commands unusable.
This includes "adb reboot recovery", reboot to recovery from Magisk Manager and reboot to recovery from inside TWRP. To get into TWRP you first have to reboot to bootloader and from there on to TWRP/Recovery!
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the HTC U12+
Contributors
JEANRIVERA, mikalovtch
TWRP: @Freak07, @Captain_Throwback
PBRP: Reza Adi, Firewolfxda, Manjot Sidhu, Mohd Faraz, Arbaz Khan
Source Code: https://github.com/PitchBlackRecoveryProject/android_bootable_recovery
Version Information
Status: Official
Current Version: 2.9.1
Release Date: 2020-05-21
Created 2020-05-01
Last Updated 2020-05-21
Reserved
Reserved
Great to see a updated recovery! Thanks for this! I will try it.
Do you know why is still not possible to decrypt pie? And why you do not recommended to disable it? At the beginning everyone wanted disable this.
Max128 said:
Great to see a updated recovery! Thanks for this! I will try it.
Do you know why is still not possible to decrypt pie? And why you do not recommended to disable it? At the beginning everyone wanted disable this.
Click to expand...
Click to collapse
1. it is no possible to decrypt stock pie due to HTC proprietary encryption protocol, it is not Open Source, and the Dev that made it possible @nkk71 to decrypt previous HTC Encrypted devices passed away, and no one has been able to take over his amazing work.
2. It is not secure to have an un-encrypted device, at the end is your device and your choice,
JEANRIVERA said:
1. it is no possible to decrypt stock pie due to HTC proprietary encryption protocol, it is not Open Source, and the Dev that made it possible @nkk71 to decrypt previous HTC Encrypted devices passed away, and no one has been able to take over his amazing work.
2. It is not secure to have an un-encrypted device, at the end is your device and your choice,
Click to expand...
Click to collapse
Hello, installed following the guide and got this
I also have a problem with this recovery. I want to make a nandroid backup ( system , boot and data ) i am on viper rom gsi now. I always have this error when i launch a backup , : unable to find partition for path '/system. In mount the system is checked and the mount system partition read only is not possible to uncheck it.
After that i have try the twrp updated for viper rom and is working fine this one no problem for backup.
new version uploaded, it should be as stable as official TWRP + some extras , & now become almost official release, still a pre-official test for official release
https://github.com/PitchBlackRecoveryProject/android_device_htc_ime-pbrp/releases
Max128 said:
I also have a problem with this recovery. I want to make a nandroid backup ( system , boot and data ) i am on viper rom gsi now. I always have this error when i launch a backup , : unable to find partition for path '/system. In mount the system is checked and the mount system partition read only is not possible to uncheck it.
After that i have try the twrp updated for viper rom and is working fine this one no problem for backup.
Click to expand...
Click to collapse
it has been fixed on new version!!
JEANRIVERA said:
it has been fixed on new version!!
Click to expand...
Click to collapse
Got it! , I will try it! Can you tell me if you flash permanent the recovery you still can flash a ruu later without do anything else? Also on the viper rom you suggest to flash your Touchscreen hexpatcher ? with flashing the header patch from venom or only the kernel pie 0.2 from venom i am not sure with what i have read..
Thanks you!
Max128 said:
Got it! , I will try it! Can you tell me if you flash permanent the recovery you still can flash a ruu later without do anything else? Also on the viper rom you suggest to flash your Touchscreen hexpatcher ? with flashing the header patch from venom or only the kernel pie 0.2 from venom i am not sure with what i have read..
Thanks you!
Click to expand...
Click to collapse
RUU should always works if done properly regardless of whatever you flash in your phone, and the hexpatcher will be only needed if you are on stock kernel, if you are using a custom kernel, then use the patch from venom
JEANRIVERA said:
RUU should always works if done properly regardless of whatever you flash in your phone, and the hexpatcher will be only needed if you are on stock kernel, if you are using a custom kernel, then use the patch from venom
Click to expand...
Click to collapse
I have asking it for to be sure, because some of my old phones like the htc 10 when you flashing a bootloader without a red text you should restore the original bootloader for flashing a ruu or a firmware if i am remember correctly.. I am pretty sure you are already know that but is for why i have asking it.
For my other question , so i am assuming the viper is on a custom kernel so i know now what files flashing.
Max128 said:
I have asking it for to be sure, because some of my old phones like the htc 10 when you flashing a bootloader without a red text you should restore the original bootloader for flashing a ruu or a firmware if i am remember correctly.. I am pretty sure you are already know that but is for why i have asking it.
For my other question , so i am assuming the viper is on a custom kernel so i know now what files flashing.
Click to expand...
Click to collapse
Rom and kernel are 2 different things, you can flash viper Rom and have stock kernel, or you can flash a custom kernel, custom kernel do no need the hexpatcher only stock kernel does regardless of the Rom you are using
JEANRIVERA said:
Rom and kernel are 2 different things, you can flash viper Rom and have stock kernel, or you can flash a custom kernel, custom kernel do no need the hexpatcher only stock kernel does regardless of the Rom you are using
Click to expand...
Click to collapse
Of course i know rom and kernel is a different things. I was thinking since the viper is not a official rom is need a custom kernel.
Max128 said:
Of course i know rom and kernel is a different things. I was thinking since the viper is not a official rom is need a custom kernel.
Click to expand...
Click to collapse
it doesn't requires a custom kernel, it is completely optional, just remember, if you stay on stock kernel, then you will need hexpatcher, if you use custom, as far as i know there are 3 available, CleanSlate, Kirisakura, & Beyond Stock, any of those 3 you will no need to use the hexpatcher
JEANRIVERA said:
it doesn't requires a custom kernel, it is completely optional, just remember, if you stay on stock kernel, then you will need hexpatcher, if you use custom, as far as i know there are 3 available, CleanSlate, Kirisakura, & Beyond Stock, any of those 3 you will no need to use the hexpatcher
Click to expand...
Click to collapse
Got it.
I have forget to tell you since your recovery is a port from twrp, when I write you about the bugs the other days, after that I have take the last twrp I have make a full backup with no errors , more later I have restored my backup with... I had got a bootloop on htc logo every times, I have trying to fix it but nothing to do... I was forced to install again the viper rom after that I was able to restore the data partition and is worked. Probably a bug in twrp restored, I am guessing probably have this bug on your recovery also.
@JEANRIVERA, thanks for the great job and maintaining TWRP!
I assume, it is still not possible to do a data backup on Pie (without this one)?
KotTHECat said:
@JEANRIVERA, thanks for the great job and maintaining TWRP!
I assume, it is still not possible to do a data backup on Pie (without this one)?
Click to expand...
Click to collapse
Not possible, this recovery is based on TWRP, every limitations on TWRP will also be here, Devoting HTC stock Pie at the moment is not supported by TWRP, but you can Decrypt AOSP Pie Encryption for example GSI ROMS based on PHH work like ViperExperience,
@JEANRIVERA I have done what you said and i have a problem , I have flash your recovery after that i have flash your touch patch and magisk.. reboot.. Android work fine.. ( except I was forced to delete some files in the recovery about the lockscreen , he didn't want let me to put again my password.. ) after that i has put again my password.. )
The problem now is on the recovery i boot it from the bootloader, the recovery stays on the logo pitch for a long time after that is said to me to put my password i enter it but it never want to decrypt the data. So i do not know why the recovery do not want the decrypt the data and why is stay so long on pitch logo every times. I have not flashing viper patch because is for custom kernel.
Max128 said:
@JEANRIVERA I have done what you said and i have a problem , I have flash your recovery after that i have flash your touch patch and magisk.. reboot.. Android work fine.. ( except I was forced to delete some files in the recovery about the lockscreen , he didn't want let me to put again my password.. ) after that i has put again my password.. )
The problem now is on the recovery i boot it from the bootloader, the recovery stays on the logo pitch for a long time after that is said to me to put my password i enter it but it never want to decrypt the data. So i do not know why the recovery do not want the decrypt the data and why is stay so long on pitch logo every times. I have not flashing viper patch because is for custom kernel.
Click to expand...
Click to collapse
please send me a screenshot of settings>about phone>Android Version
{
"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:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's not working:
Moto Fingerprint Gestures
You tell me
Instructions:
Download the ROM
Backup each and every partition from TWRP Recovery(optional)
Make a full wipe (system, vendor, data, cache, dalvik)
Flash LineageOS Package
Flash gapps
And at last Reboot!
[First boot will take few minutes]
Clean Flash is always recommended!
Downloads:
ROM
GAPPS
XDAevDB Information
LineageOS 17.1 for Ali, ROM for the Moto G6
Contributors
@BetoxxDios
@Electimon
@abhishek_d9
@jeangraff30
ROM OS version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Unlocked bootloader, Custom recovery
Based On: AOSP
Version information
Status: Stable
Current Stable Version: LineageOS
Stable Release Date: 2020-10-06
Created 2020-10-06
Last Updated 2020-10-06
Hi,
Thanks, I was waiting for this. I will test it on the weekend. Can you please move the thread to "Moto G6 ROMs, Kernels, Recoveries, & Other Development" section? It will be easier to find it.
roypen said:
Hi,
Thanks, I was waiting for this. I will test it on the weekend. Can you please move the thread to "Moto G6 ROMs, Kernels, Recoveries, & Other Development" section? It will be easier to find it.
Click to expand...
Click to collapse
Hi, I request to Moderators move the thread to that section. I don't have permissions to move it.
tomarc said:
Thanks you ! This is great news for me.
Can you fix the Moto Fingerprint Gestures ? Or maybe the rom has it own alternative ?
Click to expand...
Click to collapse
I'm trying to solve moto gestures but don't get a solution yet, the alternative are the android 10 gestures but they work with the screen, not with fingerprint
tomarc said:
Thanks you ! This is great news for me.
Can you fix the Moto Fingerprint Gestures ? Or maybe the rom has it own alternative ?
Click to expand...
Click to collapse
I'm trying to solve moto gestures but don't get a solution yet, the alternative are the android 10 gestures but they work with the screen, not with fingerprint
Thank you
Thank you very much for building and posting this ROM. I would very much like to try it on my G6 (XT1925-5).
Following this thread, I got as far as unlocking the bootloader and booting TWRP from fastboot. But could not flash anything because of a locked boot.img. I have requested an edited boot.img and hope to get a reply.
Is there perhaps another way to get my G6 (XT1925-5) with firmware version PPSS29.55-37-7-10 to be able to run LineageOS?
Thanks in advance,
FWieP
fwiep said:
Thank you very much for building and posting this ROM. I would very much like to try it on my G6 (XT1925-5).
Following this thread, I got as far as unlocking the bootloader and booting TWRP from fastboot. But could not flash anything because of a locked boot.img. I have requested an edited boot.img and hope to get a reply.
Is there perhaps another way to get my G6 (XT1925-5) with firmware version PPSS29.55-37-7-10 to be able to run LineageOS?
Thanks in advance,
FWieP
Click to expand...
Click to collapse
Hi, which twrp did you try? You might want to use the twrp64 as this LOS17.1-build is a 64 Bit
nightmw said:
Hi, which twrp did you try? You might want to use the twrp64 as this LOS17.1-build is a 64 Bit
Click to expand...
Click to collapse
Thanks for the reply. I used twrp-3.4.0-0-ali, downloaded from the official download page.
Is there a special download page for 64bit TWRP?
Kind regards,
FWieP
tomarc said:
You can find it here : https://forum.xda-developers.com/moto-g6/development/twrp-twrp-64-bit-ali-t4093879
Click to expand...
Click to collapse
Once again: thank you all. I downloaded the mali.img and booted TWRP from it.
Then, I flashed the new LineageOS 17.1 and OpenGapps - without any problems, warnings or errors.
If there is no way to flash TWRP into the recovery partition permanently, I can live with that.
Most important thing is, I can flash the system partition when needed.
Hope to see more of your work!
Kind regards,
FWieP
BetoxxDios said:
What's not working:
Moto Fingerprint Gestures
You tell me
Contributors
@BetoxxDios
@Electimon
@abhishek_d9
@jeangraff30
Click to expand...
Click to collapse
Having flashed this ROM a few days ago, I find it nearly perfect. Nearly
the October 2020 security patches are available from LineageOS; can they be included?
Would it be possible for you to share your kernel (link to source) and roomservice.xml?
I would like to try and build the ROM myself. Perhaps contribute, at least providing a mirror for the ROM files?
If not you (@BetoxxDios), perhaps the other contributors (@Electimon, @abhishek_d9, @jeangraff30) ?
Thanks!
Kind regards,
FWieP
failed to load kernel!
On my XT1925-5 I have flashed this rom serveral times, no errors, but it fails to boot.
When I restore the backup, I'm on stock again...
After installing twrp (mali.img) I did format data, reboot onto twrp, wipe, install etc.
Still it will boot only to fastboot: failed to load kernel!
Any suggestions?
Close, but no cigar - yet
fwiep said:
Would it be possible for you to share your kernel (link to source) and roomservice.xml?
I would like to try and build the ROM myself.
Click to expand...
Click to collapse
Thanks @BetoxxDios for providing the links to kernel, device and vendor trees in a private message.
After expanding the RAM of my machine to 16GB and some very educational experiments, the build finally succeeded.
TWRP flashed the ROM without any errors. Yeah!
Then the first reboot. I know that this usually takes a long time - say, 5 minutes. I've left it booting for more than 4 hours, but it doesn't get past the bootanimation.
Can anyone help me in solving this piece of the puzzle? Are there any logs I can get at while the phone is not yet adb-ready? What does LineageOS do while booting for the first time?
Thanks and kind regards,
FWieP
P.S. For the moment, I've flashed @BetoxxDios' original ROM. It's better (and safer) than Motorola's stock firmware.
fwiep said:
.
Then the first reboot. I know that this usually takes a long time - say, 5 minutes. I've left it booting for more than 4 hours, but it doesn't get past the bootanimation.
Can anyone help me in solving this piece of the puzzle? Are there any logs I can get at while the phone is not yet adb-ready? What does LineageOS do while booting for the first time?
Thanks and kind regards,
FWieP
A frozen boot screen like that has happened to me many times. Usually 1 of 2 issues. 1. Gapps problem 2. Magisk problem.
Cheers.
Click to expand...
Click to collapse
Baronstragen said:
A frozen boot screen like that has happened to me many times. Usually 1 of 2 issues. 1. Gapps problem 2. Magisk problem.
Click to expand...
Click to collapse
Thanks for the tip.
I'm afraid this is another issue - I haven't flashed any Gapps with my ROM (yet), and have never even used Magisk before.
@BetoxxDios has shown me a way to get logfiles during boot: build an -eng variant instead of -user or -userdebug.
Now, we're investigating what's going wrong. To be continued!
Kind regards,
FWieP
tomarc said:
Yes, you can flash it permanently :
Fastboot flash recovery xxx.img ; xxx.img being the name of the recovery file.
Click to expand...
Click to collapse
Up until today, I thought this wouldn't work. When doing so, fastboot would say:
Code:
writing 'recovery'...
(bootloader) Image not signed or corrupt
And thus, I thought it had not flashed at all.
Today, I read elsewhere on this forum, to simply ignore this message and check whether it flashed. It actually has!
So, thank you, once again
Kind regards,
FWieP
---------- Post added at 17:22 ---------- Previous post was at 17:08 ----------
fwiep said:
Now, we're investigating what's going wrong. To be continued!
Click to expand...
Click to collapse
And continue it does.
Right from the start, while building this ROM, I got an error about an undefined shared library: libqsap_sdk in /device/motorola/ali/libshims/Android.mk.
I saw it was in a section marked "optional", so I commented it out. And the build succeeded. Yes! After flashing, I got the looping boot-animation. D'oh!
But then, while trying to build another ROM (Resurrection Remix OS 8.6.3 by @abhishek_d9), I got the same error.
I again commented the section out, built the ROM successfully, but got the same looping boot-animation after flashing.
So, XDA to the rescue: I found this post which explains to include '/system/qcom' from LineageOS to get that libqsap_sdk included. I've added it to my roomservice.xml and have started another build. It looks very promising.
Maybe case solved? I'll let you know.
Update
Close, but no cigar. The looping boot-animation still persists. I'll investigate further...
Kind regards,
FWieP
whats-in-a-name said:
On my XT1925-5 I have flashed this rom serveral times, no errors, but it fails to boot.
When I restore the backup, I'm on stock again...
After installing twrp (mali.img) I did format data, reboot onto twrp, wipe, install etc.
Still it will boot only to fastboot: failed to load kernel!
Any suggestions?
Click to expand...
Click to collapse
I bought a new phone, also XT1925-5 and unlocked. But also here, I get the same error:
failed to load kernel!
Stock Android was 8.0 and this rom is 10. could that be a problem?
Solved 'kernel not found'
whats-in-a-name said:
I bought a new phone, also XT1925-5 and unlocked. But also here, I get the same error:
failed to load kernel!
Stock Android was 8.0 and this rom is 10. could that be a problem?
Click to expand...
Click to collapse
I used Motorola Rescue and Smart Assistant Tool
First of all I restored the phone by using the rescue_and_smart_assistant and installed Android 9
Then I used: fastboot boot mali.img
In TWRP, I removed encryption by installing: Force_Encryption_Disabler_For_ALI_Oreo_v2.zip
Wipe, the standard wipe (factory reset) + Format data
Then reboot to bootloader, and again load TWRP: fastboot boot mali.img
Wipe again and install the system (lineage-17.1-20201001-UNOFFICIAL-ali.zip)
install Magisk
Wipe cache and Dalvik
reboot into system
whats-in-a-name said:
Solved 'kernel not found'
I used Motorola Rescue and Smart Assistant Tool
First of all I restored the phone by using the rescue_and_smart_assistant and installed Android 9
Then I used: fastboot boot mali.img
In TWRP, I removed encryption by installing: Force_Encryption_Disabler_For_ALI_Oreo_v2.zip
Wipe, the standard wipe (factory reset) + Format data
Then reboot to bootloader, and again load TWRP: fastboot boot mali.img
Wipe again and install the system (lineage-17.1-20201001-UNOFFICIAL-ali.zip)
install Magisk
Wipe cache and Dalvik
reboot into system
Click to expand...
Click to collapse
I tried all of that and keep getting "updater process ended with ERROR: 255 Error installing zip file...." Any way to fix this issue? I'm on XT1925-6 32gb.
Never mind, I had the wrong TWRP installed like a dope.
I installed the ROM following your instructions and other sources:
- unlocked the bootloader
- flashed the unofficial TWRP recovery for the moto g6 ali (https://forum.xda-developers.com/t/twrp-unofficial-twrp-64-bit-for-ali.4093879/)
- wiped system, data, cache and dalvik, my device has no vendor partition though
- flashed your Lineage Rom
- flashed the most recent GAPPS, for Android 10, arm 64, stock
Then rebooting the phone will just end up in an infinite boot animation.
Doing it all over without the gapps and the phone boots just fine. So it seems that the gapps installation is somehow causing the trouble. I tried many different gapps packages, but all without any success.
Could you provide a link to a gapp package that is known to work with your ROM?
Thanks in advance!
I installed the ROM following your instructions and other sources:
- unlocked the bootloader
- flashed the unofficial TWRP recovery for the moto g6 ali (https://forum.xda-developers.com/t/twrp-unofficial-twrp-64-bit-for-ali.4093879/)
- wiped system, data, cache and dalvik, my device has no vendor partition though
- flashed your Lineage Rom
- flashed the most recent GAPPS, for Android 10, arm 64, stock
Then rebooting the phone will just end up in an infinite boot animation.
Doing it all over without the gapps and the phone boots just fine. So it seems that the gapps installation is somehow causing the trouble. I tried many different gapps packages, but all without any success.
Could you provide a link to a gapp package that is known to work with your ROM?
Thanks in advance!
{
"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"
}
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 19.1 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 19.1 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even more custom ROMs for this tablet.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and this one is based on the latest Android 11 release (T510XXU5CWA1).
Stock recovery will be replaced with my latest TWRP build for the SM-T510.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
lineage-19.1-20230403-UNOFFICIAL-T510XXU5CWA1.tar.md5 (Odin tarball)
lineage-19.1-20230403-UNOFFICIAL-T510XXU5CWA1.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20230403:
Updated to LineageOS 19.1 GSI (20230323) with March 2023 security patch and GApps.
Based on the latest Android 11 OEM kernel and vendor partition (T510XXU5CWA1).
Includes TWRP v3.7.0 custom recovery built on AOSP 11.
20220918:
Initial release based on LineageOS 19.1 GSI (20220912) with Sept. 2022 security patch and GApps.
Based on the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
Includes TWRP v3.6.2 custom recovery built on AOSP 11.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
If TWRP launches, factory reset with Wipe->Format Data and reboot to system. (Not necessary for incremental upgrades.)
From existing TWRP install:
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, Install Image, select your update (.img file), and then swipe to install
Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
Source:
android_device_samsung_gta3xlwifi
treble_build_los
Phh-Treble
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
Reserved
Thank you dear @Magendanz very much for keeping my Old Youtube Tab Alive!
Quick Question, is an update from "lineage-18.1-20220417-UNOFFICIAL-T510XXU5CVB1.zip" to the new 19.1 Possible or do i have to update the base version first?
Good evening Mr. Magendanz,
i installed this ROM on my Samsung SM-T510 and my tab/back/home buttons are not in the middle/bottom position they are in the right corner (i had this issue also with another unffocial lineage Os 19.1 Rom for SM-T510)
How can i solve this ?
NJey90 said:
Good evening Mr. Magendanz,
i installed this ROM on my Samsung SM-T510 and my tab/back/home buttons are not in the middle/bottom position they are in the right corner (i had this issue also with another unffocial lineage Os 19.1 Rom for SM-T510)
How can i solve this ?
Click to expand...
Click to collapse
Is the task bare active? I have the same layout when it is. You can turn it off in settings, but research the bar, you might want to use it.
@Magendanz , I dirty installed it over my lineageos gsi, and it works great so far. One problem I see, and had with the gsi is that I have a notification to finish installation, but there is no way to get past the network selection. There is no button to either skip or continue. Is there a way to fix this?
Thank you for this - I know how hard it is given your other responsibilities!
Thanks Magendanz for this news!
Coming from LineageOS 17.1 (lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN), what would be the sequence of steps for updating to this rom ?
Thanks.
galoneta said:
Coming from LineageOS 17.1 (lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN), what would be the sequence of steps for updating to this rom ?
Click to expand...
Click to collapse
I recommend you download and install the T510XXU5CVG2 firmware, do a clean install with Odin...but intercept the restart by holding Vol Up & Down so that you reenter Download mode. Then, install this custom ROM with Odin and intercept the restart by holding Power + Vol Up to enter TWRP. From there, do a factory reset and reboot to system.
If you inadvertently miss the restart intercept and have to run through OEM setup, make sure to connect to the Internet and then enter Developer options to disarm Vaultkeeper. Don't try to flash anything else until you've verified the OEM Unlock is still on (but disabled).
Magendanz said:
I recommend you download and install the T510XXU5CVG2 firmware, do a clean install with Odin...but intercept the restart by holding Vol Up & Down so that you reenter Download mode. Then, install this custom ROM with Odin and intercept the restart by holding Power + Vol Up to enter TWRP. From there, do a factory reset and reboot to system.
If you inadvertently miss the restart intercept and have to run through OEM setup, make sure to connect to the Internet and then enter Developer options to disarm Vaultkeeper. Don't try to flash anything else until you've verified the OEM Unlock is still on (but disabled).
Click to expand...
Click to collapse
Thanks Magendanz for this clarifying tutorial!
So you must first always update \ have the samsung base AND the custom recovery to a MINIMUM combination set? In this case the minimum "combo" set would be a samsung rom with android 11 as base (and recovery 3.6) right ?
Will try this sequence and give feedback as soon as possible.
Thanks again.
Hey there, just wondering -- does hardware video acceleration work on this build seeing as its based on a GSI? Thanks
I tried to flash this on T515 via twrp. Seems like it only detect and allow install on t510
Can you also make a variant for sm-t515?
Cheers and thanks
dissidius said:
Can you also make a variant for sm-t515?
Cheers and thanks
Click to expand...
Click to collapse
In the ten or so years I've been dealing with Samsung tablets and XDA, I must have seen this question asked at least a hundred times. "Can you make the wifi ROM work on the LTE version?" of whatever tablet or vice versa. And the answer is always "No." They are two different animals and normally the dev has one or the other. And it is very difficult to make a ROM for a device you don't have. And the same thing goes for tablets with the S Pen. They are NOT the same.
lewmur said:
In the ten or so years I've been dealing with Samsung tablets and XDA, I must have seen this question asked at least a hundred times. "Can you make the wifi ROM work on the LTE version?" of whatever tablet or vice versa. And the answer is always "No." They are two different animals and normally the dev has one or the other. And it is very difficult to make a ROM for a device you don't have. And the same thing goes for tablets with the S Pen. They are NOT the same.
Click to expand...
Click to collapse
of course mate i like your passion in explaining such things but i belive *i can be wrong of course* that i wasn't asking on a Xiaomi Poco thread..... this two devices are very much similar, smt510 twrp works correcly on smt515 for example. Just maybe the rom could also work with some little tweaks. Thanks
dissidius said:
of course mate i like your passion in explaining such things but i belive *i can be wrong of course* that i wasn't asking on a Xiaomi Poco thread..... this two devices are very much similar, smt510 twrp works correcly on smt515 for example. Just maybe the rom could also work with some little tweaks. Thanks
Click to expand...
Click to collapse
Yes, TWRP can work on both but recovery doesn't access the LTE modem. And, again, I'm stating MY experience from over ten years of having people ask the question about many, many SAMSUNG tablets only.
Has anyone successfully installed MindTheGApps on lineageos19? did you use an sdcard or adb or some other method? I don't have access to an sdcard but I am curious if this is the only way. I have not been successful in using adb..... yet!
This version of Lineage 19 already has Gapps installed. So MindtheGapps is not needed. Installing it using the tar ball and Odin means you don't need an SD card. Or have I missed something?
dissidius said:
Can you also make a variant for sm-t515?
Cheers and thanks
Click to expand...
Click to collapse
I installed this on my T515 via TWRP and it worked just fine. Haven't tried LTE though, but the os installed perfectly.
DingusestDingus said:
I installed this on my T515 via TWRP and it worked just fine. Haven't tried LTE though, but the os installed perfectly.
Click to expand...
Click to collapse
Scratch that, I restarted it and its now in a bootloop
This is the 2019 version. I can't get this to install. Bootloader is unlocked and tablet is rooted