Related
Is possible to implement f2fs to janice? F2FS is very fast.
{
"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"
}
Note : Not Tested on Helium hence not supported
Introduction
MultiROM is one-of-a-kind multi-boot mod for Xiaomi Mi Max (Hydrogen). It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our 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, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
This is still very experimental!
This has been tested with most popular Rom's of Xiaomi Mi Max (Android MM and N based).
*Please, keep in mind that if you've updated to latest N firmware in your primary ROM, you won't be able to boot MM as secondary any more. If you are on MM firmware then only ROMs built with MM blobs will work, doesn't matter MM or N. If you are on N Firmware then only ROMs built with N blobs will work in MultiROM.
Make backups. Seriously. Please.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive (Not yet implemented)
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 (We do not have Official Support, so this is not an option for us yet)
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 (If you want to use Kexec) - 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 3 parts you need to install:
Modified recovery - download the IMG file from second post and use fastboot to flash it.
Patched kernel - You can use either one of the stock ones in second post or third-party kernels which include the patch, you can see list in the second post. Download the boot.img and flash it in recovery by selecting image flash and flash it to boot parition. This can be avoid using no-kexec workaround in latest MultiROM versions.
MultiROM - download the ZIP file from second post and flash it in recovery.
Your current ROM will not be erased by the installation.
Adding ROMs
Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Once Installation is complete. Go to MultiRom --> List Rom's --> Select the installed secondary Rom --> Remove Boot.img
Done!
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)
Flash Kexec-hardboot patched kernel (either the kernel linked in second post or any third party kernel which supports kexec-hardboot (NOT needed when using no-kexec workaround in TWRP -> MultiROM Settings)
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.
Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.
Source code
MultiROM - https://github.com/multirom-hydrogen/multirom
Modified TWRP - https://github.com/multirom-hydrogen/Team-Win-Recovery-Project
Kernel w/ kexec-hardboot patch - https://github.com/multirom-hydrogen/kernel_xiaomi_msm8956
Device tree - https://github.com/multirom-hydrogen/android_device_xiaomi_hydrogen
Credits
This work is based on the hard work of @Tassadar (MultiROM), @nkk71 (no-kexec), 500 Internal Server Error, Geoff Levand, webgeek1234, Mike Kasick, Npjohnson, @jackeagle, Hashbang173, and many others. Thank you.
My Team mates @k2wl @Rohan purohit @TechExhibeo @Vatsal. (Thank you very much guys! )
Issues
MIUI is not supported (You should be able to boot MIUI as secondary with latest release if you're still using a MM firmware in your primary ROM).
USB OTG Support is not yet Implemented and will be done in future releases. (It should work in latest releases)
- If you find one that this thread does not know about/hasn't answered (solid rule, read the last three pages of the thread befre reporting an issue), report it on the specific repo in question.
- IF YOU GET LOCKED OUT OF YOUR DEVICE: Don't worry! Your data is fine. Simply boot to TWRP, choose 'Advanced' ==> 'Terminal Command' ==> type "rm -rf /data/system/gatekeeper.*.key" (without the quotes). This is a dirty fix, and should only be used to recover data, not as a permanent solution! After you recover your data, wipe /data (you don't have to wipe Internal Storage), and re-setup the device.
NOTE:
Third party kernel developers if you have merged Kexec-hardboot support kindly PM me linking to your kernel sources with confirmation about the working. So that I can add your kernel here in supported kernel list
Extra Information
I ask that no one build targeting the Xiaomi Mi Max using our source and post it publicly ( distribution is forbidden). Of course, I welcome and ask that anyone who wants to pull request changes in to do so!
XDA:DevDB Information
MultiRom-Xiaomi Mi Max (Hydrogen), Tool/Utility for the Xiaomi Mi Max
Contributors
jackeagle, BitOBSessiOn
Source Code: https://github.com/multirom-hydrogen
Version Information
Status: Stable
Current Stable Version: Stable 1
Stable Release Date: 2016-12-20
Current Beta Version: NO-KEXEC version
Beta Release Date: 2017-01-14
Created 2016-12-20
Last Updated 2017-03-25
Downloads
Downloads (NO-KEXEC)
MR Installer App: Play Store Link
(Still Not Supported for Hydrogen, working on it...)
TWRP 3.1.0 (MultiROM modded): Latest here
MultiROM v33 Installer Flashable ZIP: Latest here
MultiROM Uninstaller Flashable ZIP: multirom_uninstaller.zip
Changelogs
Changelogs
Code:
[COLOR="Blue"]
[SIZE="4"]24/03/2017
- Updated TWRP to 3.1.0 Release
- MultiROM and TWRP Upstream Updates
- [URL="https://forum.xda-developers.com/showpost.php?p=71576938&postcount=40"]More info about release![/URL]
02/03/2017
- Finally fixed Lockscreen security bug fixed
- MultiROM and TWRP Upstream Updates
- [URL="https://forum.xda-developers.com/showpost.php?p=71254611&postcount=24"]More info about release[/URL]
19/01/2017
- MR Upstream Updates merged
- Merged with latest TWRP Changes
- Updated MR TWRP to 3.0.3-1 Release
15/01/2017
- Added MIUI Support (Limited Support kindly read OP and Release notes for further details)
- Updated to Latest MR No Kexec v33
- Updated MR TWRP to 3.0.3 Release
- Fixed USB OTG Support
- Added Minimal Tree
20/12/2016
- Initial Release
[/SIZE][/COLOR]
Great work Jack ! glad to help , we rock
Eagle has arrived?
Great Work Bro.
Thank you for releasing (pain it was to release than to fix bugs) ????
-TechExhibeo
Awesome work buddy.
Really appreciate your efforts and hardwork Sir!
Thank you once again.
It says my device isn't supported I have Mi Max 32gb global My stock ROM is CM 14.1.
jutley said:
It says my device isn't supported I have Mi Max 32gb global My stock ROM is CM 14.1.
Click to expand...
Click to collapse
Follow the installation instructions in OP
Multirom App don't have hydrogen support
-TechExhibeo
Awesome?
is the modded kernel going to work with marshmallow based roms(especially resurrection remix) ?
wingryder said:
is the modded kernel going to work with marshmallow based roms(especially resurrection remix) ?
Click to expand...
Click to collapse
Currently Marshmallow ROMS are not supported
Maybe in future or so
-TechExhibeo
Really appreciate your efforts and hardwork!
Hope Like This You Bring More ROMs for Mi MAX!
TWRP 3.0.3 + MultiROM v33 (NO-KEXEC) Available
Well, after some testing, we can release first NO-KEXEC version for MultiROM v33 and latest modded TWRP 3.0.3 to support it.
You can download latest releases from here.
NO-KEXEC workaround (Big thx to @nkk71 ) is enabled by default so you should be able to boot WITHOUT any kexec-patched kernel as primary ROM.
If you are still using MM firmware on primary ROM you should be able also to boot ANY N, MM based ROM as secondary, included MIUI, but keep in mind that you'll get any issue if your secondary ROM needs N firmware (we can't get everything... ).
This TWRP version should support USB OTG as well and fix some prior bugs found in 3.0.2 version.
Thx to @TechExhibeo and @jackeagle for their support.
Feedback welcome.
BitOBSessiOn said:
Well, after some testing, we can release first NO-KEXEC version for MultiROM v33 and latest modded TWRP 3.0.3 to support it.
You can download latest releases from here.
NO-KEXEC workaround (Big thx to @nkk71 ) is enabled by default so you should be able to boot WITHOUT any kexec-patched kernel as primary ROM.
If you are still using MM firmware in primary ROM you should be able also to boot ANY N, MM based ROM as secondary, included MIUI, but keep in mind that you'll get any issue if your secondary ROM needs N firmware (we can't get everything... ).
This TWRP version should support USB OTG as well and fix some prior bugs found in 3.0.2 version.
Thx to @TechExhibeo and @jackeagle for their support.
Feedback welcome.
Click to expand...
Click to collapse
Good Job Sir.
Note for Users - If you are on MM firmware then only ROMs built with MM blobs will work, doesn't matter MM or N.
If you are on N Firmware then only ROMs built with N blobs will work in MR
You cannot boot different firmware ROMs in MR to boot :v
^ NON-KEXEC Multrirom
Thank you.
-TechExhibeo
TechExhibeo said:
Good Job Sir.
Note for Users - If you are on MM firmware then only ROMs built with MM blobs will work, doesn't matter MM or N.
If you are on N Firmware then only ROMs built with N blobs will work in MR
You cannot boot different firmware ROMs in MR to boot :v
^ NON-KEXEC Multrirom
Thank you.
-TechExhibeo
Click to expand...
Click to collapse
Thx for clarification, OP updated :good:
TWRP 3.0.3-1 + MultiROM v33 (20170118)
Downloads:
TWRP 3.0.3-1 available here.
MultiROM v33 (20170118) available here.
Changelog:
Code:
commit 53f72b7563c6cf358c5088246ad3af0899327df5
Author: bigbiff bigbiff <[email protected]>
Date: Thu Dec 8 21:21:17 2016 -0500
TWRP device version string
For building through jenkins. Export a variable to the shell
so that we don't monkey patch variables.h and keep the git tag
clean in the version string.
Jenkins will export the variable TW_DEVICE_VERSION=n where n > 0.
The makefile will use this variable to show the device string
in twrp startup. For mass production builds, omit the
environment variable to default to 0.
Change-Id: I0d6eb764255d7069c0fb4a378522a009cfe4054f
commit 94e5a23dd2f12c2cfca8beb9dadbde92820b1d55
Merge: 78f6699 7dde36d
Author: nkk71 <[email protected]>
Date: Sat Jan 14 16:13:41 2017 +0200
Merge remote-tracking branch 'upstream/android-7.1' into android-7.1-mrom
commit 7dde36df119a1ed0089b999641b27dc2c2a5280d
Author: sndnvaps <[email protected]>
Date: Tue Oct 4 18:09:37 2016 +0800
updater: link libcrypto_utils_static if it exist
Change-Id: I9bf238a3e29d88850a6cc69f07954949722c35d7
Signed-off-by: sndnvaps <[email protected]>
commit 1c28904749f5d0ae58b113b5b59901f7fc3731f6
Author: D. Andrei Măceș <[email protected]>
Date: Fri Dec 16 16:01:56 2016 -0500
libtar: Use relative path for crypto/ext4crypt include
Don't assume path to be bootable/recovery (i.e., support CM's
RECOVERY_VARIANT).
Change-Id: Ib53cc919c5a9beb3beee71d7227a7c957a24b601
commit 1021edf17ed57f193724a953dd159e7717e9553a
Author: nailyk-fr <[email protected]>
Date: Sun Dec 18 14:32:25 2016 +0100
bootloader_message: Allow TWRP to ignore wipe-data command into misc
* Rebase of https://gerrit.omnirom.org/#/c/20750/ patch-set 3
* Original commit message:
fix: recently a change in AOSP causes a bootloop to TWRP
(and therefore all ROM's based on it)
Reason: AOSP enables use of /misc partition and normally the fstab in
TWRP will not have /misc added. The problem is now when Android writes
a wipe command to /misc it will force TWRP to boot but TWRP will do
nothing - leaving the cmd in /misc. This results in a bootloop to TWRP.
Solution: I added a new var TW_IGNORE_MISC_WIPE_DATA which can be
set to "true" in Boardconfig.mk of a device requiring this which then
ignores /misc commands like it would be when /misc would be just not in
fstab BUT with this change TWRP clears the bit in /misc so a normal boot
can happen.
Besides that if the device do not have an own recovery key combo and
/misc is enabled we want to open TWRP after walking through the factory
reset screen - without actually doing a factory reset.
kudos to nailyk (and DevUt) for the help with the C++ code!
Change-Id: If6fed5872015f1a66304e3edbdb787c507236f69
commit dcd1e440e009b7861f09e2b718ea489bdcea34b5
Author: James Christopher Adduono <[email protected]>
Date: Sun Nov 6 13:17:34 2016 -0500
Support theme width and height offsets
Current use condition is LG V20, where the secondary screen is
actually just a corner chunk of the main screen.
In this case, we need to shift the UI down some pixels in order
to see it all, but just using Y offsets resulted in losing
the rest of the GUI below.
Example in BoardConfig.mk:
# Shift TWRP off the secondary screen
TW_Y_OFFSET := 160
TW_H_OFFSET := -160
Change-Id: I5a06638ba0d05e5b9fd8a6245c630d6ea3394f78
commit b29a5e27c33291f8134ea5f28e84e672a3c25199
Author: D. Andrei Măceș <[email protected]>
Date: Thu Dec 22 06:19:44 2016 -0500
build: Consolidate the crypto_utils presence tests
No point checking filesystem repeatedly/check may change in future
Change-Id: I0413b07b850f785eb5150c6ed18836cc56e94d6f
commit 4767caf1f4cd08cdc7d58476bc017dca17870112
Author: Ethan Yonker <[email protected]>
Date: Wed Jan 11 10:45:04 2017 -0600
Fix compile error on 4.4 tree
Change-Id: Id85fdf0f4dee02f8ee3ae50ec42423c6a154a3eb
BitOBSessiOn said:
Downloads:
TWRP 3.0.3-1 available here.
MultiROM v33 (20170118) available here.
Changelog:
Click to expand...
Click to collapse
Hi , great work! Currently fingerprint/gatekeeper issue is present, to explain in brief ( after adding a secondary ROM , when u boot into primary, u can't unlock the device (deleting /data/system/gatekeeper_pattern/password.key will fix) we need to fix this in mr_hooks.c like here https://github.com/multirom-nexus6p...mmit/2c2bb118fb125888144bb3399aefca961fa77df9
https://github.com/multirom-nexus6p/android_device_huawei_angler/blob/cm-14.1/multirom/mr_hooks.c
Secondly ,
Only tested this with dirty unicorns, aicp as primary, n du as secondary, after selecting secondary in mr menu , it will reach boot animation n reboot again from splash (mi logo) so Ul have to select secondary ROM option again, which then boots fine
Rohan purohit said:
Hi , great work! Currently fingerprint/gatekeeper issue is present, to explain in brief ( after adding a secondary ROM , when u boot into primary, u can't unlock the device (deleting /data/system/gatekeeper_pattern/password.key will fix) we need to fix this in mr_hooks.c like here https://github.com/multirom-nexus6p...mmit/2c2bb118fb125888144bb3399aefca961fa77df9
https://github.com/multirom-nexus6p/android_device_huawei_angler/blob/cm-14.1/multirom/mr_hooks.c
Secondly ,
Only tested this with dirty unicorns, aicp as primary, n du as secondary, after selecting secondary in mr menu , it will reach boot animation n reboot again from splash (mi logo) so Ul have to select secondary ROM option again, which then boots fine
Click to expand...
Click to collapse
Interesting, I will revise. Thx!
yes as described by @Rohan purohit the problem is present ... this problem has beem solved by @nijel8 in his unofficial build waiting for fix
Pitchblack recovery project
{
"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.
*
* 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.
*
*/
PitchBlack is a TWRP based on TWRP 3.2.3 developed by Reza Adi, maintained by Manjot Sidhu and Mohd Faraz and themed by FireWolf.
For devices (OFFICIAL) : https://sourceforge.net/projects/pitchblack-twrp/files/
Authors build : @Reza_adi, Mohd Faraz
Developers : @Reza_adi, Mohd Faraz
Thanks : @Reza_adi P - Indonesia (Owner / Lead Developer PBRP), George Pasakalis (G.M.L) - Greece (UI Developer), FirewolfXDA - Bangladesh (UI Developer), Manjot Sidhu - India (Source Maintained), Mohd Faraz - India (Co-Lead Developer, Source Maintained), Arbaz Khan - India (Source Maintained), PitchBlack Recovery, @ATG Droid & @dadi11 (Redwolf Developer) for MIUI OTA Support, @arra_quen for Helping and Uploading @faizhifzhan for layout to sourceforge, All Maintainer and User PBRP.
DOWNLOAD :
Recovery zip
BUGS:
When booted while charging, battery level shows 0%.
If you find any other bugs please let me know and i'll try to address them or update this section of the thread to let the bug be publicly known.
F2FS filesystem format is limited to 4GB for some reason so don't use it for /data ( I currently use /cache and /system as f2fs instead of EXT4 with no issues )
INSTALLATIONS :
Flash Zip file as if it were a ROM in TWRP, or you can flash the Recovery.img as you would TWRP (adb commands, apps such as flashify, kernel auditor/mtweaks, terminal dd commands, or using TWRP under Install > install image > recovery )
If using installing the Zip file through TWRP or other custom recovery, it will reboot automatically to recovery. If using the recovery.img method, reboot into recovery as you normally would.
Enjoy
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the LG K20 Plus
Contributors
Travisholt92,
Deadman96385 (helped to provide bandwidth and the Q6 Stock Oreo kernel which my Oreo+ builds and this project utilize)
Source Code: [url]https://github.com/PitchBlack-Recovery[/URL]
Version Information
Status: Official
Current Version: 2.9.0
Release Date: 2019-02-05
Created 2019-02-03
Last Updated 2019-02-07
My to do list for tonight, update the Fstab to properly support F2FS filesystem format and address the filesystem error.
I should have a new official build up tonight.
I must say this recovery is ? % awesome. I like the extra features that include the options to install/uninstall SuperSU and/or magisk and various more. I think twrp has met it's match.
kieffey said:
I must say this recovery is ? % awesome. I like the extra features that include the options to install/uninstall SuperSU and/or magisk and various more. I think twrp has met it's match.
Click to expand...
Click to collapse
And that's why I went for Official PBRP before official TWRP, to get people to at least give it a try. Its based on the latest TWRP so it has all of the features TWRP users love with quite a few extras.
will this work on stock rom
chacon16 said:
will this work on stock rom
Click to expand...
Click to collapse
It should, I haven't tested. The only reason to stay on stock is VoLTE.
chacon16 said:
will this work on stock rom
Click to expand...
Click to collapse
It works fine in stock. It works with every flavor of ROM out for the K20 Plus.
Sent from my LG K20 Plus using XDA Labs
New build up today that addresses the issue with rebooting to recovery from within recovery.
Screenshots
ROMs?
I read earlier that "every flavor of K20 Plus" will work with PB, so I just want to make sure I am 100% clear and sure I understand before I **** up (another) phone...
I am using a Rooted LG K20 Plus with the Resurrection Remix OS ROM and Pitch Black recovery. The only problem is that my phone has no audio function. Mic, and Speakers are nonfunctional. It won't play videos, make or receive calls, play music, or even the background sound on Games. It is my understanding that this is a common bug with Resurrection Remix ROM, so I'd like to just put a new OS. I just need to know if any OS will work as long as its compatible with the K8+ or if it has to be tailored/compatible for PB as well?
CrookedYoungHeretic said:
I read earlier that "every flavor of K20 Plus" will work with PB, so I just want to make sure I am 100% clear and sure I understand before I **** up (another) phone...
I am using a Rooted LG K20 Plus with the Resurrection Remix OS ROM and Pitch Black recovery. The only problem is that my phone has no audio function. Mic, and Speakers are nonfunctional. It won't play videos, make or receive calls, play music, or even the background sound on Games. It is my understanding that this is a common bug with Resurrection Remix ROM, so I'd like to just put a new OS. I just need to know if any OS will work as long as its compatible with the K8+ or if it has to be tailored/compatible for PB as well?
Click to expand...
Click to collapse
This phone is not compatible with k8 at all. I released lineage 15.1 and it is currently the only stable Oreo rom for this device
Travisholt92 said:
This phone is not compatible with k8 at all. I released lineage 15.1 and it is currently the only stable Oreo rom for this device
Click to expand...
Click to collapse
Whoopee, where it says K8+ on my post is a typo, idk why but my boyfriend was under the impression initially that this K20+ was a K8, I still get confused and mixed up, especially since I also tinker with an LG K4 Rebel lol. But the phone I am using/inquiering about is indeed the LG K20+.
P. S do you have any input/suggestions/advice about the Resurrection ROM 8I can just 7 send 8tnti you
leave your /system partition formatted as ext4
Flashing this ROM uses block-based patching; instead of copying the necessary files to the filesystem, it copies blocks to the disk. These blocks are data representations of files as they were expressed on the filesystem they originate from, thus copying blocks from an ext4 filesystem to any other filesystem will corrupt it.
Since this is my first post I cannot post the pictures I took of PBRPs output after flashing the ROM to both f2fs and ext4 filesystems and then running e2fsck. On f2fs, the partition is recognized as ext4 after the flash, and e2fsck.f2fs fails as the partition is corrupt beyond repair. On ext4, e2fsck executes as expected. You can also search "block-based OTAs" to find the entry on the AOSP website for more information.
dode417 said:
Flashing this ROM uses block-based patching; instead of copying the necessary files to the filesystem, it copies blocks to the disk. These blocks are data representations of files as they were expressed on the filesystem they originate from, thus copying blocks from an ext4 filesystem to any other filesystem will corrupt it.
Since this is my first post I cannot post the pictures I took of PBRPs output after flashing the ROM to both f2fs and ext4 filesystems and then running e2fsck. On f2fs, the partition is recognized as ext4 after the flash, and e2fsck.f2fs fails as the partition is corrupt beyond repair. On ext4, e2fsck executes as expected. You can also search "block-based OTAs" to find the entry on the AOSP website for more information.
Click to expand...
Click to collapse
Only /cache and /system will currently work with F2FS which needs to be formatted that way before install and only my Lineage 15.1 supports f2fs filesystem format. I have tested and confirmed it works at the time of implementation. Formatting /data as F2FS limits the partition to 4GB for some reason i have yet to figure out. I hope this bit of information helps.
CrookedYoungHeretic said:
Whoopee, where it says K8+ on my post is a typo, idk why but my boyfriend was under the impression initially that this K20+ was a K8, I still get confused and mixed up, especially since I also tinker with an LG K4 Rebel lol. But the phone I am using/inquiering about is indeed the LG K20+.
P. S do you have any input/suggestions/advice about the Resurrection ROM 8I can just 7 send 8tnti you
Click to expand...
Click to collapse
RR 8.1 was a total flop. I built it once and it had so many ROM source related bugs from no longer being supported by the RR team that i just gave up on it. More or a variety of ROMs will come after i get pie working.
Travisholt92 said:
Only /cache and /system will currently work with F2FS which needs to be formatted that way before install and only my Lineage 15.1 supports f2fs filesystem format. I have tested and confirmed it works at the time of implementation. Formatting /data as F2FS limits the partition to 4GB for some reason i have yet to figure out. I hope this bit of information helps.
Click to expand...
Click to collapse
I'm not saying it doesn't boot, only informing everyone that the f2fs partition is corrupted by the flashing process and cannot be repaired with fsck. I'm honestly not sure of the total effect of this, but those who are cautious may be thankful for this information.
I can flash the recovery.img for PBRP after doing bootloader unlock via fastboot correct? I don't need to flash TWRP and do all the flashing steps under "How to Disable encryption and flash super su [Install Root]" in the TWRP v3 thread to get PBRP and Magisk on my device? Eventually plan on putting LOS 15.1
SomeDooD123 said:
I can flash the recovery.img for PBRP after doing bootloader unlock via fastboot correct? I don't need to flash TWRP and do all the flashing steps under "How to Disable encryption and flash super su [Install Root]" in the TWRP v3 thread to get PBRP and Magisk on my device? Eventually plan on putting LOS 15.1
Click to expand...
Click to collapse
That is correct, you can use PBRP for those steps.
@Travisholt92 I am trying to flash PBRP and i can only find the .zips linked above. I have tried flashing the .zips in TWRP 3.2.1 . I am failed with "Invalid zip file format" . What am i doing wrong?
chugs said:
@Travisholt92 I am trying to flash PBRP and i can only find the .zips linked above. I have tried flashing the .zips in TWRP 3.2.1 . I am failed with "Invalid zip file format" . What am i doing wrong?
Click to expand...
Click to collapse
You have to unzip the file and fastboot flash recovery.IMG or install the image through twrp under install image
{
"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"
}
Welcome to Project Spaget X ARM64 Treble For Galaxy J530X/J730X/G610X/J701X/J710X
Some information you should know..
This is a full Treble ARM64 Vendor/Kernel implementation for the Exynos7870 Supported devices
If you want to report a Bug, read the F.A.Q First Then provide a logCat OR LoggingKit.zip with detailed explanation
Read the instructions and the F.A.Q Before installing the rom or posting a reply.
[FOR DEVS] You are allowed to customize this vendor if you want to use it in ROMs with proper credits. but not to distribute 1:1 copies
- Personal Notes
And here we are, few leaks and reworks later. X is here. i went with a letter this time just because it looks cool. This is officially going to be EOL for ARM64 AONLY vendors that i make (unless a critical bug was here that needed attention) . i dont have alot of time to work on 7870 And when i do i prefer it to be on something more productive than Treble
Anywya, TLDR : alot changed, alot was fixed. its a new vendor, flash and enjoy
Old releases
Alright, The "second" Treble update is here, this time it is FULLY ARM64 compatible. Thanks to the hard-work of @Astrako who managed to boot ARM64 Exynos 7885 bases on our device. This project is HEAVILY based on his work. and i would like to make that very clear. This is not a OneMan job. this took alot of hardwork by many people to make it reach the stage it is at. basically we are official minus the tag. This project is also possible thanks to my dear friends @Kique119 @me2 @SPARTANICUS and my other testers who spent day and night testing this with me.
At this stage, everything is mostly GSI related.
And finally, the cherry on top, is support for 3 more devices. Thanks to the devs who assisted me on adding support for their own devices. mentioned below.
If you appreciate this ambitious project, consider hitting thanks, supporting the thread, and donating (Paypal) to support my development (using cocaine of-course)
- Initial Notes:
Supports ONLY the mentioned devices Above
1. Don't forget to check bugs before asking questions
2. Since most of the GSIs are AOSP, forget about VoLTE, Knox features, Samsung apps, Camera mods or features, or other Samsung related features.
3. You can use any non-treble rom even if you have treble vendor installed, as long as you flash a non-treble kernel. The rom will ignore your vendor and everything will be as non treble.
- General Features :
- based on G965F Vendor with VNDK-28
- Adapted to J730/J530/G610/J710/J701 devices
- latest CronosKernelV5 included with most of the features of OneUI kernel + many more
- misc things enabled in framework overlay for better experience
- Seamless GSI patching, without user intervention
- Seamless setup process, with dynamic Scripts
- And Spaget
- How to Install Project Spaget:
- Flash `Exynos7870_CreateVendor` and reboot recovery
- Flash `Exynos7870_Spaget_X`
- Flash your desired ARM64_AONLY GSI
- Read OPTIONAL below
- What GSIs are support/recommended ?:
- Avoid sGSIs and flash source built GSIs (Such as PHH,PE)
- ARM64_AONLY GSIs only
- I recommend Pixel-experience or evo x and luke GSIs
- if you want a daily rom. avoid sGSIs
- More can be found here : Treble
- I dont have googleapps. what do i do ?:
ONLY for gsis that does not come with google apps
- Download Gapps pacakge from Here (ARM64 > VER > Micro or lower
- Go to TWRP > Wipe > Advanced Wipe > Tick System > Repair > Resize
- Flash opengapps_xxxx
- I need more info. where do i get it ?
Ask in this thread. if you need more , head to
Spaget Notes and support : Telegram Group
General bugs (GSI):
- offline charging is broken in Android 10 roms
- Bluetooth Calls
- Some GSIs might not include a camera, use Footej
- Some camera apps will have stretch
- I dont like it, how do i revert ?:
- Reboot to recovery
- Flash `Exynos7870_RevertVendor`
- Reboot recovery
- Flash any non treble rom or restore your previous twrp backup
Is that all ? I have treble now ? what about all the complicate process before ?
Yes, you now have a project treble device, ready to flash any GSI/sGSI of your choice aslong as it fits in your SYSTEM partition.
The entire process changed and now is much more seamless and noob-friendly. yet take caution as always
What if i didn't boot ?
In some cases, you might be stuck at a bootanimation loop or a splash loop, in this case follow the troubleshooting steps in the F.A.Q post
Credits
@corsicanu For great help with the repartition scripts, GSI patching and tons other throughout the years.
@Astrako for making booting ARM64 a possibility. and allowing this project to exists. kudos
@Kique119 For his awesome testing and documenting this project, without him there would be no spaget
@KassemSYR, for G610F Support and testing.
@Zero_Cool7870 , @DAvinash97 , @mohitsama and ORIGINALNAME123 for J710/J701 support
@SPARTANICUS For his great work maintaining KRAKEN kernel, which supports this project fully
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl @@rlukas210
@PedroDomeneghi @DaffyMirror4318 @bien2004official @AleeX157 @Alijouhara
And many more i cant remember the usernames of. please mention
Downloads. Changelogs , F.A.Qs below
OldPost (a64)---
So, i have been hesitated to release this project since last year. GSIs are not the most stable and many J users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
This is a fully featured VENDOR and KERNEL designed for this device to support project treble, it is based on other Exynos 7870 Vendors and modified to support our devices, i have also added few patches and updates that even official 7870 vendors do not have. to get the best possible experience
I have also added a GSI_PATCH zip that should be used if you want to have the least amount of bugs.
The vendor is pretty much bugles, therefore any bugs you face, Report them to the appropriate Threads of the GSI you installed. or github issues section. as those are not mine to fix. i only provide the vendor and kernel that allows GSIs to run on.
- STEPS FOR INSTALLING TREBLE VENDOR:
Flash “Treble_Jx30F.img” in TWRP as Image (Selecting RECOVERY)
Reboot recovery.
Wipe System, Data, Dalvik and Vendor.
Flash "jxy17lte_Vendor_9.0_v1.0.zip".
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be arm_binder64/A64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Flash "GSI_Patch.zip".
[OPTIONAL] Flash the “Gapps_patched.zip”
- STEPS FOR INSTALLING GAPPS:
If you flash Gapps, Google will spam you with fullscreen warnings and notifications about your device not being certified. But don't worry, you can certify it.
Just reach the homescreen, then proceed to install the "Device ID.apk". Use it to grab the Google Services Framework ID and paste it here: https://www.google.com/android/uncertified/
And paste the ID there. Then wait a few minutes and reboot. Few seconds after rebooting, you'll be done and you'll be able to normally log in as always.
- [OPTIONAL]STEPS FOR INSTALLING Magisk_GAPPS:
** Note : This gapps is recommended for all **
Download latest gapps from http://opengapps.org
place in /sdcard or /external_sd
flash magisk.zip
flash magiskgapps.zip
- Confirmed working GSIs :
** You can only use ARM_BINDER64 / A64 GSIs **
PHH AOSP V113 : Github
OmniROM GSI : XDA
Liquid Remix : GoogleDrive
Pixel Experience With Gapps : GitHub
Resurrection Remix : RR
XenonHD : TeamHorizon
P.S : only Omni and PHH Do not require the GSI_PATCH_FP The rest do in order to get Fingerprint working
- Known GSI Bugs:
Bluetooth calls are broken
Some 3rd party cameras have stretched pictures
And more here at Github Issue
Credits
@corsicanu For general help through out the years
@prashantp01 For overlay fixes and native camera fix. and other contributions
@Kique119 For his awesome testing and documenting this project
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl
And few more that didn't give me their usernames
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Project Spaget. Treble ARM64 Vendor, ROM for the Samsung Galaxy J7
Contributors
ananjaser1211, corsicanu, Astrako
Source Code: https://github.com/ananjaser1211/Helios_7870
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest bootloader and modem
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: X
Stable Release Date: 2020-01-13
Created 2019-07-31
Last Updated 2020-01-13
Downloads and changelogs
NewsChannel : Telegram
Come hang with us on our chat : Telegram
Official Treble support Group : Telegram
----------------------------------------------------------------
SpagetX Treble ARM64 Vendor Based on G965F VNDK-28
GoogleDrive : Download
P.S : If you failed to download please login and save the folder
P.S 2 : This requires Pie bootloader and modem on devices that supports them (I.E not j710 or g610)
----------------------------------------------------------------
Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor
MegaDrive Download : MEGA
GoogleDrive Mirror : GDrive
Documentation : Here
Spaget X
- ReMade fully based on VNDK-28 S9 Vendor
- Based on Project Pizza Treble (8890)
- included most fixes for audio, webview and others
- added fixes for camera
- removed alot of obsolete hacks
- samsung offline charging added
- Re-did props and features and overlays
- Added patches for Android 10 Roms
- Fixed nuke.sh script on 10 roms
- fixed performance in some GSIs
- Fixed thermal , power , memtrack and other HALs
- Improved OMX fixes
- Removed alot of samsung security services
- Improved Wifi, NFC, graphics , camera and other fixes
- Fixed some reboots on G610
- Fixed Youtube Crashes and OMX issues on most devices
- Addressed alot of random reboots
- Fixed GNSS/GPS on some variants
- Removed HKTweaks due to reboots
- Fixes for J710 Wifi and bluetooth
- Tons of other changes and improvments
[COLOR=""]Spaget V3.0[/COLOR]
- Fully based on A750FN 64Bit Vendor
- Seamlessly integrated ALL patches into the vendor
- No longer do you need customized TWRPs, patches, zips whatever. just the vendor and GSI
- Fixed all the VENDOR related issues we had
- Audio, camera, NFC, everything is redone from scratch and improved
- Supports Android Q booting
- Updated overlays and configs
- Added support for J710/J701/G610
- Updated to Helios V4.0 Kernel with tons of changes and goodies
- Automatic GSI patching at first boot
- New repartition script with extended support. fail safes, backup features and tons more
- Live TWRP patching, so it will patch whatever twrp you have instead of using my own
- And tons more through out the months of testing, using and developing
- Please read the thread agian to understand how to use it
OLD(a64)
----------------------------------------------------------------
Treble Vendor V1.5 Based on Stable A600FN Pie Vendor
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
Treble Vendor V1.0 Based on Stable A600FN Pie Vendor
GoogleDrive Project : Download
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
---------------------------------------------------------------
V1.5
1- HeliosPro 3.1 Kernel
2- Added HKTweaks
3- Fingerprint fix for All GSIs
4- Hotspot fix for All GSIs
5- AdaptiveBrightness
6- Updated included overlays with more features and pie base
7- DualbootPatcher J5/J7 Seperation
GSI_PATCH_V2.0
1- Patch fingerprint libs for all GSIs
2- Switch to samsung fingerprint
3- Add device model number detection
4- replace gsi fingerprint with stock one
GSI_PATCH_FP
1- Special patch for PE/RR/LR and other roms that do not have working FP
2- Do not flash on OMNI/PHH
3- Must be flashed AFTER the Vendor/GSI
Kernel updates
- Updated base to latest pie source
- reworked and updated helios ramdisk tweaks
- Reverted old hacks to fix some bugs
- Performance and battery greatly improved
- F2FS enabled
- LZ4 Enabled
- GPU Performance Greatly improved
- Full CPU/GPU/DEVFREQ/MIF/CAMERA Voltage control and more
- Magisk V19.1 included
Bugs :
1- some users might face SDCard issues while using PE
- if you did , back up its data and format it in PE
V1.0
-initial release
- Helios Kernel 2.8
F.A.Q
Q: Device requirements ?
A : you MUST be on an Pie Bootloader and Modem, otherwise you will have no sim, no lockscreen etc (Devices such as J710 and G610 can use OREO)
Q : Do i need to format internal storage ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : Any GSI that is ARM64_AONLY is supported [8/9/10]
Enjoy, and please report any issues you face HERE and not in the other threads.
And read the thread few times before asking. Yes this supports your G610whatever
and does not support G611X
Congrats mate. Nice work. @ananjaser1211
Small doubt ?
We have hwc and lock screen delay major bugs in lineage and all non treble aosp roms by Sid.
You did not mention those bugs in bugs list.
So those bugs are fixed ?
Thanks again.
MarkTejo said:
Congrats mate. Nice work. @ananjaser1211
Small doubt ?
We have hwc and lock screen delay major bugs in lineage and all non treble aosp roms by Sid.
You did not mention those bugs in bugs list.
So those bugs are fixed ?
Thanks again.
Click to expand...
Click to collapse
HWC bugs do not exists under this project. it has been tested on all 5 variants, non reported that issue.
let me know how it goes
good job mate!
Wow, thanks for the noob friendly explanation and description about the Project. Kudos to everyone involved
Thanks for the detailed explanation and for this project ? . Huge thanks to DEVS who are in this project ?
after gsi installation .....strucked at boot logo
ananjaser1211 said:
Welcome to Project Spaget ARM64 Treble For Galaxy J530X/J730X/G610X/J701X/J710X
Some information you should know..
This is a full Treble ARM64 Vendor/Kernel implementation for the Exynos7870 Supported devices
If you want to report a Bug, read the F.A.Q First Then provide a logCat OR LoggingKit.zip with detailed explanation
Read the instructions and the F.A.Q Before installing the rom or posting a reply.
[FOR DEVS] You are allowed to re-use the "variant" folder for your own projects. but not the vendor
Any sort of File Kanging will be reported without hesitation.
- Personal Notes
Alright, The "second" Treble update is here, this time it is FULLY ARM64 compatible. Thanks to the hard-work of @Astrako who managed to boot ARM64 Exynos 7885 bases on our device. This project is HEAVILY based on his work. and i would like to make that very clear. This is not a OneMan job. this took alot of hardwork by many people to make it reach the stage it is at. basically we are official minus the tag. This project is also possible thanks to my dear friends @Kique119 @me2 @spartanicus and my other testers who spent day and night testing this with me.
At this stage, everything is mostly GSI related.
And finally, the cherry on top, is support for 3 more devices. Thanks to the devs who assisted me on adding support for their own devices. mentioned below.
If you appreciate this ambitious project, consider hitting thanks, supporting the thread, and donating (Paypal) to support my development (using cocaine of-course)
Changes over the A64 vendor are massive. it is very recommended to re-read this thread one more time.
- Initial Notes:
Supports ONLY the mentioned devices Above
1. Don't forget to check bugs before questions
2. Since most of the GSIs are AOSP, forget about VoLTE, Knox features, Samsung apps, Camera mods or features, or other Samsung related features.
3. You can use any non-treble rom even if you have treble vendor installed, as long as you flash a non-treble kernel. The rom will ignore your vendor and everything will be as non treble.
4. No other kernel supports treble now, don't try to flash/boot with others unless they specifically mention that the kernel supports treble or you will drastically fail.
5. The CreateVendor will reduce your system size by 150MB. so keep that in mind
6. Backup all your files and revert any partition changes done to the phone (see f.a.q)
7. Android Q GSIs are supported and boo-table, however contain too much unfixable bugs at the moment. so patience
- General Features :
- based on A750FXXU1BSG1 July security patch
- Adapted to J730/J530/G610/J710/J701 devices
- latest HeliosKernel V4 included with most of the features of OneUI kernel + many more
- misc things enabled in framework overlay for better experience
- Seamless GSI patching, without user intervention
- Seamless setup process, with dynamic Scripts
- And Spaget
- How to Install Project Spaget:
- Flash `Exynos7870_CreateVendor` and reboot recovery
- Flash `Exynos7870_ProjectSpaget_V3.0`
- Flash your desired ARM64_AONLY GSI
- Read OPTIONAL below
- What GSIs are support/recommended ?:
- Avoid sGSIs and flash source built GSIs (Such as PHH,PE)
- ARM64_AONLY GSIs only
- I recommend Pixel-experience or evo x
- if you want a daily rom. avoid sGSIs
- More can be found here : Treble
- I dont have googleapps. what do i do ?:
ONLY for gsis that does not come with google apps
- Download Gapps pacakge from Here (ARM64 > VER > Micro or lower
- Go to TWRP > Wipe > Advanced Wipe > Tick System > Repair > Resize
- Flash opengapps_xxxx
- I need more info. where do i get it ?
Ask in this thread. if you need more , head to
Spaget Notes and support : Telegram Group
Spaget Documentation (By @Kique119) : Document
General bugs (GSI):
- no signal bars shown (signal is fine however)
- offline charging (The phone charges without animation)
- fingerprint gestures
- Bluetooth Calls
- Some camera apps will have stretch. use Footej instead
- I dont like it, how do i revert ?:
- Reboot to recovery
- Flash `Exynos7870_RevertVendor`
- Reboot recovery
- Flash any non treble rom or restore your previous twrp backup
Is that all ? I have treble now ? what about all the complicate process before ?
Yes, you now have a project treble device, ready to flash any GSI/sGSI of your choice aslong as it fits in your SYSTEM partition.
The entire process changed and now is much more seamless and noob-friendly. yet take caution as always
Credits
@corsicanu For great help with the repartition scripts, GSI patching and tons other throughout the years.
@Astrako for making booting ARM64 a possibility. and allowing this project to exists. kudos
@KassemSYR, for G610F Support and testing.
@Zero_cool7870 , @DAvinash97 , @mohitsama and ORIGINALNAME123 for J710/J701 support
@prashantp01 For overlay fixes and native camera fix. and other contributions
@Kique119 For his awesome testing and documenting this project, without him there would be no spaget
@spartanicus For his great work maintaining KRAKEN kernel, which supports this project fully
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl @@rlukas210
@PedroDomeneghi @DaffyMirror4318 @bien2004official @AleeX157 @Alijouhara
And many more i cant remember the usernames of. please mention
Downloads. Changelogs , F.A.Qs below
OldPost (a64)---
So, i have been hesitated to release this project since last year. GSIs are not the most stable and many J users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
This is a fully featured VENDOR and KERNEL designed for this device to support project treble, it is based on other Exynos 7870 Vendors and modified to support our devices, i have also added few patches and updates that even official 7870 vendors do not have. to get the best possible experience
I have also added a GSI_PATCH zip that should be used if you want to have the least amount of bugs.
The vendor is pretty much bugles, therefore any bugs you face, Report them to the appropriate Threads of the GSI you installed. or github issues section. as those are not mine to fix. i only provide the vendor and kernel that allows GSIs to run on.
- STEPS FOR INSTALLING TREBLE VENDOR:
Flash “Treble_Jx30F.img” in TWRP as Image (Selecting RECOVERY)
Reboot recovery.
Wipe System, Data, Dalvik and Vendor.
Flash "jxy17lte_Vendor_9.0_v1.0.zip".
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be arm_binder64/A64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Flash "GSI_Patch.zip".
[OPTIONAL] Flash the “Gapps_patched.zip”
- STEPS FOR INSTALLING GAPPS:
If you flash Gapps, Google will spam you with fullscreen warnings and notifications about your device not being certified. But don't worry, you can certify it.
Just reach the homescreen, then proceed to install the "Device ID.apk". Use it to grab the Google Services Framework ID and paste it here: https://www.google.com/android/uncertified/
And paste the ID there. Then wait a few minutes and reboot. Few seconds after rebooting, you'll be done and you'll be able to normally log in as always.
- [OPTIONAL]STEPS FOR INSTALLING Magisk_GAPPS:
** Note : This gapps is recommended for all **
Download latest gapps from http://opengapps.org
place in /sdcard or /external_sd
flash magisk.zip
flash magiskgapps.zip
- Confirmed working GSIs :
** You can only use ARM_BINDER64 / A64 GSIs **
PHH AOSP V113 : Github
OmniROM GSI : XDA
Liquid Remix : GoogleDrive
Pixel Experience With Gapps : GitHub
Resurrection Remix : RR
XenonHD : TeamHorizon
P.S : only Omni and PHH Do not require the GSI_PATCH_FP The rest do in order to get Fingerprint working
- Known GSI Bugs:
Bluetooth calls are broken
Some 3rd party cameras have stretched pictures
And more here at Github Issue
Credits
@corsicanu For general help through out the years
@prashantp01 For overlay fixes and native camera fix. and other contributions
@Kique119 For his awesome testing and documenting this project
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl
And few more that didn't give me their usernames
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Project Spaget. Treble ARM64 Vendor, ROM for the Samsung Galaxy J7
Contributors
ananjaser1211, corsicanu, Astrako
Source Code: https://github.com/ananjaser1211/Helios_7870
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest bootloader and modem
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: V3.0
Stable Release Date: 2019-08-01
Created 2019-08-01
Last Updated 2019-07-31
Click to expand...
Click to collapse
after gsi installation .....strucked at boot logo(sm-610f) ,,at installation i got /preload unable to mount. Please help
Great work my dude :good:
i installed several gsi on sm610-f all are freezing at boot logo
ananjaser1211 said:
HWC bugs do not exists under this project. it has been tested on all 5 variants, non reported that issue.
let me know how it goes
Click to expand...
Click to collapse
im not able to use gsi's freezing on bootlogo
sai1355 said:
im not able to use gsi's freezing on bootlogo
Click to expand...
Click to collapse
Use TWRP's file manager and delete system/bin/rw-system.sh
Reboot and your 64bit GSI should boot now.
No OS installed why
And just bootloop
sai1355 said:
after gsi installation .....strucked at boot logo(sm-610f) ,,at installation i got /preload unable to mount. Please help
Click to expand...
Click to collapse
Same here ...bootloop
But i haven't see the boot logo just black screen only
robinfive said:
No OS installed why
And just bootloop
Click to expand...
Click to collapse
Try a different gsi please. the no os installed happens after you wipe system and flash an image.
lineage and rr gsis are not tested, and they dont work right last time i checked.
try Pixel experience , evo x , havoc etc..
ananjaser1211 said:
Try a different gsi please. the no os installed happens after you wipe system and flash an image.
lineage and rr gsis are not tested, and they dont work right last time i checked.
try Pixel experience , evo x , havoc etc..
Click to expand...
Click to collapse
O like PE and Evo X
So i'll test it now
I test Los in first bc Los Costum ROMs is the better when we talking about Performance/stability
Anyway ..
Keep up the good work :good:
Same problem with PE just black screen
And ...Failed to mount '/preload' (invalid argument)
still in bootloop ......
ShaDisNX255 said:
Use TWRP's file manager and delete system/bin/rw-system.sh
Reboot and your 64bit GSI should boot now.
Click to expand...
Click to collapse
still in bootloop ......
sai1355 said:
still in bootloop ......
Click to expand...
Click to collapse
Which GSI ROM you're try to install
{
"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"
}
OrangeFox Recovery Project
Code:
/*
* 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 recovery
* 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.
*
*/
OrangeFox Recovery is one of the most popular custom recoveries, with amazing additional features, fixes and a host of supported devices
OrangeFox Recovery have been operating for over two years. In that time we have improved the quality, stability, and device support of the recovery. Today OrangeFox is the leader in stability, UI design, and UX. Installing OrangeFox means being with the latest code and fastest fixes.
OrangeFox Recovery was originally designed for Xiaomi Redmi Note 4X Snapdragon (mido). Right now we support 47+ devices.
Installations
Download the OrangeFox zip file to your device
Reboot to your custom TWRP-based Recovery
Install the OrangeFox zip file as a normal zip
The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
Enjoy!
Downloads
OrangeFox Official siteㅤNEW! & RECOMMENDED!
https://orangefox.download/device/onclite
OrangeFox Stable release
https://files.orangefox.download/OrangeFox-Stable/onclite/
OrangeFox Beta release
https://files.orangefox.download/OrangeFox-Beta/onclite/
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 [only for some devices]
Password
Support for Miui and Custom ROMs
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!
Frequently Asked Questions
OrangeFox Guides & FAQs
https://wiki.orangefox.tech/en/guides
OrangeFox Setup OTA
https://wiki.orangefox.tech/en/guides/ota
OrangeFox FAQs for this device
https://forum.xda-developers.com/showpost.php?p=82504299&postcount=23
Connect with us
OrangeFox Recovery Building
https://t.me/OrangeFoxBuilding
OrangeFox Recovery Updates
https://t.me/OrangeFoxUpdates
OrangeFox Recovery Support
https://t.me/OrangeFoxChat
OrangeFox Recovery Beta tracker
https://t.me/OrangeFoxBetaTracker
OrangeFox Recovery Beta testing
https://t.me/OrangeFoxBeta
Credits
TeamWin - for TWRP
The OrangeFox Team - for your hard work
All our testers - for your patience and help
Report bugs
OrangeFox reporting problems
https://wiki.orangefox.tech/en/guides/report
Notify bugs through the comments column
Take screenshots and give reasons clearly
Grab a log right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
XDA:DevDB Information
OrangeFox Recovery Project, Tool/Utility for the Xiaomi Redmi 7
Contributors
hadaddarajat
Source Code: https://gitlab.com/OrangeFox
Version Information
Status: Stable
Current Stable Version: R11.0_0
Stable Release Date: 2020-07-19
Current Beta Version: R11.0_0
Beta Release Date: 2020-07-04
Created 2020-04-09
Last Updated 2020-07-20
Warning!
before downloading this recovery, you must first read this Frequently Asked Questions
OrangeFox R11.0 Stable version is available, download via link on thread, for all updates will not be posted here again. So you can immediately check official site!
Before download, look first at "Changelogs" and "Build notes" on official site
R11 Changelogs: https://wiki.orangefox.tech/en/changelog
OrangeFox R11.0 Beta version is available, download via link on thread!
STABLE
Click to expand...
Click to collapse
R10.1_5
Build Date: 2020-05-23
Changelog
Update prebuilt kernel
Update recovery tree
Fixed no boot on some devices
Use mke2fs to create ext4 images
Multi decryption improvement
Release Notes
No need to wipe data, no need to re-install ROM. You can use this on FDE & FBE Encryption.
R10.1_4
Build Date: 2020-05-09
Changelog
Switch back from bash to shell
Updating cryptfs_hw (R10.1_3 corrupt)
Release Notes
No Need to Wipe Data, No Need to Re-Install ROM. You can use this on FDE, FBE & Metadata Encryption.
R10.1_3
Build Date: 2020-05-07
Changelog
Resync with Latest OrangeFox Source Code
Including QCOM Haptics Vibrator
Including QCOM LEDS Haptics
FDE: Automatic Decrypt of /data
FBE: Insert Lockscreen Password for Decrypt /data
Metadata: Same as FBE
Update Device Tree
Release Notes
No Need to Wipe Data, No Need to Re-Install ROM. You can use this in FDE, FBE & Metadata Encryption.
R10.1_2
Build Date: 2020-04-27
Changelog
Rearrange source code
Reconfigure fstab file
Disable system vold debug
Remove CPUs online
Reduce heat on front screen
50% default screen brightness
100% maximum screen brightness
Adding SELinux Policy
Adding Metadata decryption support
Update prebuilt kernel with Metadata support
Auto detect MicroSD Card partition type
Auto detect USB-OTG partition type
Release Notes
If you use the same type of Encryption, then wipe data and re-install ROM is not required. But if you move from a ROM that has a different type of Encryption, you must wipe data and re-install ROM. You can use this in FDE, FBE & Metadata Encryption.
R10.1_1
Build Date: 2020-04-19
Changelog
Added FBE decryption support
Added F2FS support
Recovery fast charging
Bring back Aroma File Manager
Improved "onc" detection
Release Notes
No need to wipe data, no need to re-install rom. You can use this in FDE & FBE rom.
R10.1
Build Date: 2020-04-14
Changelog
Automatic decrypt of /data
Remove Patch AVB 2.0
Auto detect onc & onclite
Fix CPUs online
Fix heat on the front screen
Release Notes
No need to wipe data, no need to re-install rom, this release is for FDE.
Because stock MIUI on Redmi 7 does not support FBE.
BETA
Click to expand...
Click to collapse
R10.1
Build Date: 2020-04-09
Changelog
Initial official build
Using precompiled stock kernel
Patch AVB 2.0
Remove Aroma File Manager
Flashlight work
Using system fingerprint
Fix OTA update manual flash error
Disable treble compatibility check
Release Notes
Need more test of Encryption, Decryption, Recovery fast charge, Patch AVB 2.0.
After installing OrangeFox it is recommended that you wipe the data, cache, and system, then re-install ROM.
Reserved
FBE Support?
loco1911 said:
FBE Support?
Click to expand...
Click to collapse
For the current release yet. Maybe I will add FBE support in the next version.
Hello, I have a problem, when I want to install the miui global stock rom it gives me an error 7 and tells me that it is for the Onc model and not Onclite, but I can install it without any problem in the TWRP
loco1911 said:
FBE Support?
Click to expand...
Click to collapse
loco1911 said:
Hello, I have a problem, when I want to install the miui global stock rom it gives me an error 7 and tells me that it is for the Onc model and not Onclite, but I can install it without any problem in the TWRP
Click to expand...
Click to collapse
Thank you for telling, for the next version I will change the prop setting to "onc"
loco1911 said:
Hello, I have a problem, when I want to install the miui global stock rom it gives me an error 7 and tells me that it is for the Onc model and not Onclite, but I can install it without any problem in the TWRP
Click to expand...
Click to collapse
Which twrp did u use??
Har****@5 said:
Which twrp did u use??
Click to expand...
Click to collapse
The official TWRP 3.3.1-0
loco1911 said:
The official TWRP 3.3.1-0
Click to expand...
Click to collapse
Try using the latest version of Orangefox (R10.1_1). I added decryption support for FBE, F2FS support, and improved "onc" detection when flashing ROM.
Thank you for your amazing work!!! This recovery works perfect!
loco1911 said:
Thank you for your amazing work!!! This recovery works perfect!
Click to expand...
Click to collapse
I'm also grateful to you for reporting a bug.
hadaddarajat said:
I'm also grateful to you for reporting a bug.
Click to expand...
Click to collapse
Can this be used to flash miui based custom roms?
olayinkajnr said:
Can this be used to flash miui based custom roms?
Click to expand...
Click to collapse
You can,
but try it first if you are still in doubt.
Then give your answer here.....
hadaddarajat said:
You can,
but try it first if you are still in doubt.
Then give your answer here.....
Click to expand...
Click to collapse
Alright. So, it means it supports both FDE and FBE based roms.
olayinkajnr said:
Alright. So, it means it supports both FDE and FBE based roms.
Click to expand...
Click to collapse
try
so far i can see FDE Works but FBE does not work. i was using andriod 9 aex then upgrade to andriod 10 clean format i cant see files anymore and it says Device not encrypted/unable to decrypt FBE device when i boot into recovery
neijzen said:
so far i can see FDE Works but FBE does not work. i was using andriod 9 aex then upgrade to andriod 10 clean format i cant see files anymore and it says Device not encrypted/unable to decrypt FBE device when i boot into recovery
Click to expand...
Click to collapse
I inserted wrappedkey on fstab, so it can't decrypt FBE. I forgot to delete it. For now, use SHRP Official, I will update the orangfox more or less after the month of Ramadan.
Hello sir,
When I searched the codename for Redmi7 all the websites showed only only one name "ONCLITE"....
But why My phone codename is showing "ONC", when it's real codename is " ONCLITE ". I checked it with cpu-z, Aidax64.. And many more other apps.
Is " ONC" and "ONCLITE" Both are same can i flash "ONC" files for "ONCLITE" and vice versa.. Can i flash "ONCLITE" TWRP file to "ONC".....
Please help me....
I hope you will understand my problem and reply me as soon as possible.
Thanking you..........
Please reply me