{
"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"
}
## Introduction ##
MultiROM is one-of-a-kind multi-boot mod for Nexus 6. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
Warning!:
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
## Installation ##
1. Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2.Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 4 parts, but you really only need to install 3 parts:
MultiROM Installer:
TWRP Modified Recovery:
Patched Kernel: Primary roms Must have a Kexec Hardboot Patched Kernel
MultiRom UnInstaller:
Adding ROMs:
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 5.0 after first boot (with dalvik cache generated and connected to google account) takes about 1 GiB of space.
Using USB drive:
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs:
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Special Thanks to @Tasssadar..
XDA:DevDB Information
MultiRom V32 Resurrected (VS985), ROM for the Verizon LG G3
Contributors
Eliminater74, thewalkingdude, Tasssadar
Source Code: https://github.com/Tasssadar/multirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.4.x
Version Information
Status: Beta
Created 2015-07-12
Last Updated 2015-07-12
MultiRom V32 Installer: multirom-20150712-v32-UNOFFICIAL-vs985.zip
MultiRom Modified TWRP Recovery: TWRP_MultiRom_2.8.7.x_vs985_20150712-signed.zip
MultiRom Kexec Hardboot Kernel By @777jon: AOSP-777-Kernel_vs985-R10.zip
MultiRom Uninstaller: multirom_uninstaller.zip
Warning: Kernel is for LP 5.1 Only with 32gb variants at question. Sorry 16gigers, I havent done one for you yet.. but you can try this one.. It just may work.
Note: You can compile your own Kexec Hardboot Kernel as well. @fechanaitor and @777jon both have the Correct MultiRom patch that works with this version.
SideNote: Little UnKnownFact. This MultiRom is set up to allow installing Stock OEM roms as secondery as well..
And @777jon's 777Kernel does work on secondary as well with this version..
reserved
SWEET!
Thanks for this. Can't wait for the files to be uploaded. will be trying it out right away.
are 2 roms the limit or can you install more than 2?
No you can install as many as you want as long as you have the space for it.
And its done, but I gota wait a least another hour before sending it up. I got way to much trafic on my local network. and I dont wanna grab then just yet.,
Wooohoooooo
---------- Post added at 12:58 AM ---------- Previous post was at 12:57 AM ----------
I waiittttt ..thanks man...
Update: MultiRom now available for the VS985 ...............
Eliminater74 said:
Update: MultiRom now available for the VS985 ...............
Click to expand...
Click to collapse
kernel doesnt seem to boot 5.1 PA or cm roms but the 4.4.4 mahdi rom does lol idk
Alpha_wolf said:
kernel doesnt seem to boot 5.1 PA or cm roms but the 4.4.4 mahdi rom does lol idk
Click to expand...
Click to collapse
you can use any kernel you want as long as it has the patch.. the old patch that @Skin1980 did might cause problems... but you all are on your own on that..
Eliminater74 said:
you can use any kernel you want as long as it has the patch.. the old patch that @Skin1980 did might cause problems... but you all are on your own on that..
Click to expand...
Click to collapse
lol XD ok
Hmmm interesting. Have to look into this. Sounds like it could be a bit more complex than dual boot patcher is. But I like the way this is set up.
Kickin it on my VS985
Can this be used with Kitkat ROMs? I'm on Slim right now.
gweeto85 said:
I seem to be running into a issue while trying to install multirom, I have a vs985 running skydragon v4.0 5.0.1 rooted with twrp installed. I tried to flash multirom twice and failed both times resulting in a soft brick. The first time I flashed the 3 files, the kernel first.. rebooted the phone everything was fine. went back into recovery flashed the modified twrp, rebooted into recovery to flash the multirom zip. Everything was successful according to twrp, but when I reboot my phone I get a black screen after the life is good screen.. nothing boots just hangs. The second time, after reflashing my phone back to sky dragon.. tried again but this time I tried the skydragon kernel instead with the same results.
I used this for reference
https://www.youtube.com/watch?v=jKTJ9WpMOwU
can someone help me out, I'd like to get this working on my phone if possible.
Click to expand...
Click to collapse
On the D855 thread, they are reporting that you must, Flash TWRP first then reboot into new twrp.. then flash the multirom, then flash the kernel.. then after all that you should be ok.,
Now skydragon has giving some people in the past problems even on my device.. but I got skydragon as secondary and runs with no problems......
Maybe some one else here can help you beter.. your devices are dif cause of the locked bootloaders.. we T-Mobile peeps dont have Locked Bootloaders..
So it makes it kinda hard for me to test...
Delete
No matter how I try to install this it soft bricks my phone. Tried a few different ways with the same results at boot up.
Kickin it on my VS985
Edde3d said:
No matter how I try to install this it soft bricks my phone. Tried a few different ways with the same results at boot up.
Kickin it on my VS985
Click to expand...
Click to collapse
When you say soft brick, do you mean that you can no longer boot into TWRP and have to flash back to stock image via KDZ/TOT?
I want to try this out but I have a stock image as primary, and I want to go AOSP/CM secondary.
Edde3d said:
No matter how I try to install this it soft bricks my phone. Tried a few different ways with the same results at boot up.
Kickin it on my VS985
Click to expand...
Click to collapse
Im sorry man.. I just dunno what to say on that.. there seems to be a special way that you locked bootloaders gota do it.. and I have no clue.. they been talking about it on the D855 area..
Some got it working with no problems.. and some are having problems like you.. So you would have to read up on there and see what they are doing diff.
If nobody got it working. then I would say its a Port issue.. but many have got it working.. only a few havent.. im thinking its your setup... your primary rom or something.. dunno..
I mean no disrespect by what I say.. im just trying to help out. That Locked bootloaders cra* is really a pain.. Im glad I dont have to deal with all that.
PS: could you send me a log? that would be helpfull.
\
Fix for MultiRom to get it working with your Device.
Thread Moved to: XDA Link
Edde3d said:
No matter how I try to install this it soft bricks my phone. Tried a few different ways with the same results at boot up.
Kickin it on my VS985
Click to expand...
Click to collapse
flash multirom twrp
flash flash installer
flash compatiable kernel (i use madhi rom with furnace kernel)
flashs fine for me
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 ExynosOnly 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"
}
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/10.0/README.mkdn
Downloads
Official Website
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
*****Disclaimer*****
Important note before proceeding!!!
The copy A/B partitions zip is crucial in order to prevent bricks. It only needs to be done if you're coming from the stock ROM or you recently restored stock firmware manually. Other wise without it you can brick due to Motorola's A/B partition scheme.
Only use TWRP version 3.3.1-0, it has an advanced option for recovery bootloop fix. Sorry for some hassles with TWRP. It is not ROM related but the version I use works 100% of the time.
My apologies for any confusion/problems flashing!
Preparation for A/B Roms:
01. Download TWRP version 3.3.1-0 (do not use any other version)
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Use the terminal to boot the latest twrp.img "fastboot boot twrp.img"
05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmware.)
06. While in TWRP choose Reboot > bootloader
07. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Wipe data, dalvik, system and internal storage, then format userdata.
04. Flash ROM.zip + TWRP_installer
05. Reboot > Recovery
06.Install Gapps + Magisk (if you choose)
07. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. Boot into recovery
03. Install ROM.zip + TWRP_installer
04. Reboot > Recovery
05. flash GAPPS + Magisk (if you choose)
06. Reboot > System
Notes:
Any time your internal storage aka "Userdata" is from a stock install you must "format data" in recovery before using ROMS
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
SOURCES:
ROM: https://github.com/crdroidandroid
Changelog::
https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/10.0/changelog_ocean.txt
Known issues:
<!-- list here -->
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
© 2020 GitHub, Inc.
XDA:DevDB Information
CrDroid, ROM for the Moto G7 Power
Contributors
Rondeau79
Source Code: https://github.com/Rondeau79/android_kernel_motorola_sdm632
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest TWRP unlocked bootloader
Based On: AOSP, Lineage OS
Version Information
Status: Stable
Current Stable Version: QQ2A.200305.003
Stable Release Date: 2020-03-22
Created 2020-03-22
Last Updated 2020-06-23
Reserved
Ahh the ole triple posts. Don't you just love it when that happens. lol. Hell of a job on this! Will Android 10 for Ocean device ever be able to have an enforcing kernel or no? Probably waiting for source for 10/Q before messing with all that stuff? I'm just curious and figured I'd ask.. Awesome work!!!! :good:
flash713 said:
Ahh the ole triple posts. Don't you just love it when that happens. lol. Hell of a job on this! Will Android 10 for Ocean device ever be able to have an enforcing kernel or no? Probably waiting for source for 10/Q before messing with all that stuff? I'm just curious and figured I'd ask.. Awesome work!!!! :good:
Click to expand...
Click to collapse
Thanks, this one was a tough task to get done. I don't mind a permissive kernel. I really don't dive too far into the Android system. I am a fan first and a developer second! I still really don't have an understanding of code and stuff. I just go with my instincts.
I performed a 'dirty flash' coming from crDroid 5.12 (based on Android 9).
I did not delete my Google account from the phone prior to flashing. This is the first time I've had problems upgrading crDroid. I realize it's also the first time I've done a major increment to the underlying Android OS.
Upon first boot I saw the new boot animation (it looks great!) but the phone did not complete booting after about ten minutes. I interrupted the boot by holding the power key. I tried wiping data. Later, I also tried re-formatting data partition (including built-internal media). I also tried re-installing the most recent version of crDroid 5.12 with no success with that as well.
Suggestions regarding the best way to correct this would be helpful and appreciated.
In the meantime, I'll look around and trying some other things. I hope it might be corrected without having to resort to ADB / PC connection, but I'll try whatever I can.
I don't know if this result is considered "a brick" because I can boot into TWRP.
danny8 said:
I performed a 'dirty flash' coming from crDroid 5.12 (based on Android 9).
I did not delete my Google account from the phone prior to flashing. This is the first time I've had problems upgrading crDroid. I realize it's also the first time I've done a major increment to the underlying Android OS.
Upon first boot I saw the new boot animation (it looks great!) but the phone did not complete booting after about ten minutes. I interrupted the boot by holding the power key. I tried wiping data. Later, I also tried re-formatting data partition (including built-internal media). I also tried re-installing the most recent version of crDroid 5.12 with no success with that as well.
Suggestions regarding the best way to correct this would be helpful and appreciated.
In the meantime, I'll look around and trying some other things. I hope it might be corrected without having to resort to ADB / PC connection, but I'll try whatever I can.
I don't know if this result is considered "a brick" because I can boot into TWRP.
Click to expand...
Click to collapse
You are not bricked. When coming from one version of android to another a clean flash must be done. You can dirty flash after that. Wipe both boot slots and then go about flashing like normal. First boot takes a while. It won't boot without wiping the system partition.
Excuse my ignorance, where do I have to install the rom, gapps and magisk, in slot A or B? Thank you in advance (sorry bad English)
D13Gho said:
Excuse my ignorance, where do I have to install the rom, gapps and magisk, in slot A or B? Thank you in advance (sorry bad English)
Click to expand...
Click to collapse
With the A/B partitions scene. When you flash a ROM it will be installed to the opposite slot. If you are on A then the zip will be installed to B and vica versa. Gapps are flashed after you reboot to recovery when you are on the boot slot the ROM was installed on same as Magisk.
Thank you, Rondeau79. I got it installed.
It looks great!
I've got every thing installed and running, but after setting up my apps (Chrome, messages, photos) app opening/closing is quite laggy. It become unusable after a couole hours.
Johnfoo19 said:
I've got every thing installed and running, but after setting up my apps (Chrome, messages, photos) app opening/closing is quite laggy. It become unusable after a couole hours.
Click to expand...
Click to collapse
Give it a little time to set in. Usually a fresh install takes a bit.
danny8 said:
Thank you, Rondeau79. I got it installed.
It looks great!
Click to expand...
Click to collapse
You're welcome.
pie had the option of changing colors in the display settings I am not a fan of blue I like black and red. is this in a future update it was the main reason i uninstalled the other android 10 roms
cgrimm9 said:
pie had the option of changing colors in the display settings I am not a fan of blue I like black and red. is this in a future update it was the main reason i uninstalled the other android 10 roms
Click to expand...
Click to collapse
Go to display styles and wallpapers to change to colors.
Is there any way to set the position of the battery bar? like bottom of the screen or lower status bar because where default is top of screen you kinda miss half the bar because of the notch
Has anyone had any issues with mobile data not working after installing this ROM? I was able to make calls and send texts (I have Sprint, phone: Moto G7 Power X1995-5). I reflashed it and OEM locked back to stock firmware since mobile data was not working. Also, I did not have SD card since I don't have one
n00b Samurai said:
Is there any way to set the position of the battery bar? like bottom of the screen or lower status bar because where default is top of screen you kinda miss half the bar because of the notch
Click to expand...
Click to collapse
Sorry there isn't, I can't change the base features of the ROM. However you can change the color and thickness of the bar and it's position on the screen.
You can always adjust the screen in order to account for the notch. It's in the developer settings.
barados742 said:
Has anyone had any issues with mobile data not working after installing this ROM? I was able to make calls and send texts (I have Sprint, phone: Moto G7 Power X1995-5). I reflashed it and OEM locked back to stock firmware since mobile data was not working. Also, I did not have SD card since I don't have one
Click to expand...
Click to collapse
You need an external sdCard for flashing ROMs. Wiping the user partitions properly is essential for a properly working ROM. If you just have internal storage then the installation of an OS won't be done right.
Thanks for the reply! I just bought an SD card and will try it tomorrow and will respond if it worked.
Good morning, guys I tried to install on my MOTO G 7 POWER 3/32 and the rom does not install says it is not compatible with the system. Any tips?
{
"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.
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
{
"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