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"
}
Introduction
MultiROM is one-of-a-kind multi-boot mod for OnePlusX. 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.
-- updated for new bootloader 10/24--
Installation
Download & Flash:
TWRP Modified Recovery: TWRP_multirom_onyx_20161024-01.img
MultiROM Installer: multirom-20161024-v33b-onyx.zip
MultiROM uninstaller: multirom_uninstaller.zip
Patched Kernel: Primary roms Must NOT have a Kexec Hardboot Patched Kernel
Modified recovery (TWRP_multirom_onyx_YYYYMMDD.img) - download the IMG file and use fastboot, TWRP or Flashify app to flash it.
MultiROM (multirom.zip) - download the ZIP file and flash it in recovery.
You current rom will not be erased by the installation.
-> Installation guide by @Vatsal
Adding ROMs
1. Android
Go to recovery, select -> MultiROM menu -> Add ROM. Select the ROM's zip file and confirm.
Go into mr settings and tick the No-Kexec workaround, to be sure (adb is handy too)
2. Ubuntu Touch
Use the MultiROM Manager app to install Ubuntu Touch.
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 -> 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 -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Source code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/MR-op3/android_bootable_recovery (branch mr)
Kernel w/ kexec-hardboot patch - Not needed
Device Tree - https://github.com/MR-op3/device_oneplus_onyx/commits/mr
XDA:DevDB Information
MultiROM, Tool/Utility for the OnePlus X
Contributors
martinusbe, Vatsal, DavyA
Source Code: https://github.com/MR-op3
Version Information
Status: Beta
Created 2016-02-17
Last Updated 2016-10-24
Reserved
Downloads
in OP for now
Reserved
Please read all about the no-kexec workaround from the author directly, (to avoid duplicity and get latest information), thanks to @nkk71
http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4
Looking forward to this!
Verstuurd vanaf mijn ONE E1003 met Tapatalk
Looks very interesting.
Will this include the ability to install ROMs to SD card in the future since the phone only has 16 GB of internal storage?
Good to see great development on OPX thus far.
I'd like to point out that MultiROM v33 is out now!
Thanks for all the development
Regards.
very cool, i was just looking into that
Hey
So, I've waited long and now is it here *yeah*
Thank you a lot
But I have a (dumb?) question: Where do I have to download Sailfish OS? I know, in the "Sailfish wiki" but I didn't find it. Maybe it's WIP and it's not finished yet, but if it's somewhere in the world wiiiiideee web, please post a link, because I'm very interested to this ROM.
Sorry for my Bad english
IchBinNoob said:
Hey
So, I've waited long and now is it here *yeah*
Thank you a lot
But I have a (dumb?) question: Where do I have to download Sailfish OS? I know, in the "Sailfish wiki" but I didn't find it. Maybe it's WIP and it's not finished yet, but if it's somewhere in the world wiiiiideee web, please post a link, because I'm very interested to this ROM.
Sorry for my Bad english
Click to expand...
Click to collapse
Salfish OS is WIP and there isn't a download link. You can find the post in "OnePlus X General"
DavyA said:
Salfish OS is WIP and there isn't a download link. You can find the post in "OnePlus X General"
Click to expand...
Click to collapse
Yeah, thanks I already knew the post, but I want to test it now
Any bug list? or things that needs to improve?
Just curious whether or not you're using MM sources included in the new TWRP with eng.stk's commits. Great work
It is testing and will be some bug.
Yes, it's a old build and in the next days I'll build with new sources
finally.. waiting for multirom-enabled kernel for 1+x..
DavyA said:
It is testing and will be some bug.
Yes, it's a old build and in the next days I'll build with new sources
Click to expand...
Click to collapse
Does installing secondary and swapping primary-secondary works?
A video demo would be great...
Did anyone actually test this yet?
taaeem said:
Did anyone actually test this yet?
Click to expand...
Click to collapse
Just tried it. When adding a ROM it fails as it requires a MULTIROM binary but besides that it's great.
any news for the Kernel?
I try it. Look cool. For uninstall it I use the Moto G Multirom uninstaller zip. Works pretty good!
{
"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 Galaxy A5. 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.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting, once they are ported to Galaxy A5
* 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 messing with boot sector and data partition. 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) Flash Modified TWRP with odin or extract the tar file and install the img file with flashify or another recovery that has img install feature
2) Flash MultiROM zip in TWRP
3) enjoy
MultiROM has 3 parts you need to install:
Modified recovery Download the Modified TWRP for MultiROM
Patched kernel *OPTIONAL* : Not Needed
MultiROM download the ZIP file from second post and flash it in recovery.
Downloads:
Modified TWRP for MultiROM: https://www.androidfilehost.com/?w=files&flid=110082 Since the recovery image was too big for recovery partition, I used LZMA compression instead of LZO for the kernel, which saved about 3 MB
MultiROM: https://www.androidfilehost.com/?w=files&flid=110089
MultiROM Uninstaller: https://www.androidfilehost.com/?w=files&flid=110117
If you get force closes on secondary nougat ROMs:
Flash the rom, open /sdcard/multirom/roms/rom_name/system/build.prop on primary, or on TWRP with "vi" editor
and change:
Code:
ro.sys.sdcardfs=true
to
Code:
#ro.sys.sdcardfs=true
Then reboot.
DO NOT reboot the rom before changing build.prop line otherwise you will still get force closes!
You current rom will not be erased by the installation.
Important: Since the Kernel hasn't Kexec Hardboot patch, you have to check "use no kexec workaround" box in multirom settings
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive (not tested yet)
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 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.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
How does Kexec workaround works
You need to a kexec-hardboot supporting kernel or the non-kexec workaround as described perfectly by @nkk71 here: http://forum.xda-developers.com/show...26&postcount=4 (Be sure to leave him a thanks!)
Source code
MultiROM - https://github.com/nkk71/multirom
Modified TWRP - https://github.com/nkk71/android_bootable_recovery
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx branch cm-13.0-mrom
Kernel w/ kexec-hardboot patch: NOT NEEDED
Credits
A big thanks for:
@nkk71 For kexec workaround and for helped me in IRC
@Tasssadar For MultiRom Source Code
That made this possible
Donations (Please donate to the Creator @Tasssadar )
I'd be glad if you could spare a few bucks. You can use either paypal or Bitcoins, my address is 172RccLB2ffSnJyYwjYbUD3Nx4QX3R8Ris
Click to expand...
Click to collapse
XDA:DevDB Information
MultiROM for Galaxy A5 (SM-A500), Tool/Utility for the Samsung Galaxy A Series
Contributors
DeadSquirrel01
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2016-09-10
Created 2016-09-10
Last Updated 2016-09-10
Reserved
AWESOME!!!!!!!!!!!!!!!FINALY!!!!!!!!!!!:good::good::good:
-CALIBAN666- said:
AWESOME!!!!!!!!!!!!!!!FINALY!!!!!!!!!!!:good::good::good:
Click to expand...
Click to collapse
He he thanks
one lil question from me.my current rom be untouched when i flash it,right?Because my current rom is working perfect and i dont need fail,thanx.
-CALIBAN666- said:
one lil question from me.my current rom be untouched when i flash it,right?Because my current rom is working perfect and i dont need fail,thanx.
Click to expand...
Click to collapse
No, it will br untouched, but a backup waste only 5 times, at massimum, so, if you have some free space make a backup, but as I said, it will be untouched
;DD will it work like this?
primary - stock touchwiz
secondary - cm 13
?
Thanks
supertiger1234 said:
;DD will it work like this?
primary - stock touchwiz
secondary - cm 13
?
Thanks
Click to expand...
Click to collapse
Sure
It's working perfectly! Thanks! hmm is cm 13 the best or rr? or anything else? xD
Edit: I'll choose your PacRom ;D
supertiger1234 said:
It's working perfectly! Thanks! hmm is cm 13 the best or rr? or anything else? xD
Click to expand...
Click to collapse
CM is pure android, rr has lots of feature regarding the personalization, so, if you want a rom wich is pure android, get the cyanogenmod, otherwise, if you like to personalize your android get the resurrection remix. Oh you installed multirom, so you can install both of them (you can install more than 2 roms) and decide which one is better for you
EDIT: if you use pac-rom you have to move this as primary, because it has a bug that won't boot if you set it as secondary
hmm is it normal to have "failed to mount /preload (invalid argument)"? happens when i flash rr
Edit: when i choose rr from the list, the device just reboots to multirom menu. hmm
supertiger1234 said:
hmm is it normal to have "failed to mount /preload (invalid argument)"? happens when i flash rr
Click to expand...
Click to collapse
Not, try to reboot to recovery and then reflash
DeadSquirrel01 said:
Not, try to reboot to recovery and then reflash
Click to expand...
Click to collapse
Okay I deleted and reflashed the rom, still the same error, hmm
Edit: when i go to mount and try to tick preload, it doesnt tick
Mmm, maybe i have to remove preload from the fstab. Now i'll do and notify once it's done
Works on my A500M with Stock 6.0.1 and CyanogenMod 13, thank you very much for port this mod to Galaxy A5
supertiger1234 said:
Okay I deleted and reflashed the rom, still the same error, hmm
Edit: when i go to mount and try to tick preload, it doesnt tick
Click to expand...
Click to collapse
Fixed, now download new twrp version (link in main post) and it should work
@codebseraph thanks for the support
DeadSquirrel01 said:
Fixed, now download new twrp version (link in main post) and it should work
@codebseraph thanks for the support
Click to expand...
Click to collapse
Hmm, The errors fixed buut now when I choose my second rom, it reboots to multirom menu xD
The non-kecex link doesn't work. Is there something important there?
Is the secondary rom pac-rom?
If yes, u have to move it as primary because it has a bug
DeadSquirrel01 said:
Is the secondary rom pac-rom?
If yes, u have to move it as primary because it has a bug
Click to expand...
Click to collapse
I'm trying rr and it's not working xD it's scary swapping
ResurrectionRemix-M-5.7.3-20160830-a5ultexx
supertiger1234 said:
I'm trying rr and it's not working xD it's scary swapping
ResurrectionRemix-M-5.7.3-20160830-a5ultexx
Click to expand...
Click to collapse
Well, it's a problem of the zip of the ROM. move it as primary or wait until I create a working installer
EDIT: maybe try with this installer https://www.androidfilehost.com/?w=file-thanks&fid=24591020540824243&mid=71&download_id=vlofv1jeu8k8ubpcpd375ql164&tid=1473585621&hc=c6de356c2e1c646fcb44f52216b36595df13152b92265bbb693814053fe5ca85
{
"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"
}
For kenzo/kateSupports all Roms (SHOULD)
NOTE:
Code:
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 Kernel
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.
What is MultiRom?
MultiRom is one-of-a-kind multi-boot mod. 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. Roms are installed and managed via the 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.
I am not the developer of MultiRom. All Credits for it goes to Tasssadar, the actual developer of it.
Features:
MultiBoot any number of Android Roms
Restore Nandroid Backup as secondary ROM
Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting
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 messing with boot sector and data partition. 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 Stock Rom zips again. Make backups. Always.
TESTED ON ROMS:
Test and Report
SUPPORTED DEVICES:
kenzo
kate
Please Test it in other Similar SD Variants and Report it Below.
Bugs:
You tell me
SCREENSHOTS:
All Screenshots HERE
INSTALLATION INSTRUCTIONS:
Via The MultiRom Manager App:This is the easiest way to install everything MultiRom needs... Just follow the Below Instructions:
Install the app (Links Below)
Select MultiRom and Recovery on the Install/Update card.
Press "Install" on the Install/Update card to start the installation.
DONE! MULTIROM IS READY TO ROCK!
You current rom will not be erased by the installation.
Download link is in the second post.
Adding ROMs:
Android
Boot into MultiRom Recovery -> select MultiRom -> Add Rom -> Select the Rom's zip file and click Confirm.
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 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 the Rom, follow these steps:
Go to MultiRom -> List Roms and select the Rom you want to update.
Select "Flash zip" and Flash the Rom's zip File.
Explanation of recovery menus:
Main menu
- Add Rom - Add Rom to Boot
- List Roms - List Installed Roms and Manage Them
- Inject boot.img File - When you Download something, for example a Kernel, which is Distributed as a Whole boot.img (eg. Qassam Kernel), you have to use this option on it, otherwise you would lose MultiRom.
- Inject curr. boot sector - Use this option if MultiRom does not show up on boot, for example after Kernel Installation.
- Settings - Well, SETTINGS!
Manage Rom
- Rename, Delete - No Need to Explain this I Think!
- Flash Zip (Only Android Roms) - Flash zip to the Rom, for example GAPPS
- Add/Replace boot.img - Replaces boot.img used by this Rom, this is more like a Developer Option.
- Re-Patch init - This is available only for Ubuntu. Use it when Ubuntu cannot find the root partition, i.e. after apt-get upgrade which changed the init script.
GitHub Source Codes:
MultiRom Organization for Xiaomi DevicesKenzo/Kate MultiRom Device TreesMultiRom Manager App Source Codes
Current Status:
Test and Report...
CREDITS:
Rishabh Rao (ME) - For Porting MultiRom to kenzo/kate
Tasssadar - For his awesome MultiRom
nkk71 - For his No-KEXEC workaround
Version Information:
Status: Unofficial, IN TESTING, Version 33
ENJOY!:good:
XDA:DevDB Information
MultiRom For kenzo/kate, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
Rishabh Rao
Source Code: https://github.com/multirom-xiaomi
Version Information
Status: Testing
Current Beta Version: v33
Beta Release Date: 2017-03-29
Created 2017-03-29
Last Updated 2017-03-30
1.Can I flash any Other Kernel?
- YES! You CAN flash ANY Kernel!!!
2. Can I Flash Roms to USB-OTG? How?
- Yes, You CAN Flash Roms to USB-OTG.
Follow these steps to do so:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on Add Rom.
4. Select the correct Location and Flash it...
Note: Flashing on a USB-OTG takes some Time, so be patient & Don't Worry!
3.Where to Find Roms Installed in my USB-OTG Drive? How to Boot into Them?
- After Flashing the Rom you will be Booted into the MultiRom Boot Menu.
All your Roms Flashed on the Internal Memory will be in Internal Tab.
All Others will be in the External Tab.
4. How to Rename/Remove/Delete/Wipe Dalvik Cache or Flash any Other zips to an Existing Rom?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the Rom which you want to Remove/Add zips.
You will find all the options you need there!
5. "Unable to Flash, I am getting Errors" / "Executing Updater Script Failed" / "Rom is not Booting". ANY HELP???
- Please Provide Logs. It will be located in /sdcard/multirom/error.txt OR if that's not present here: /proc/last_kmsg
It would be Great if you can Provide Some Screenshots.
Press Volume Down + Power Buttons Together to take Screenshots.
6. How to Disable Auto Boot / Change Rom Name / Hide Roms / Change Brightness of MultiRom Boot Menu?
- Follow these steps:
1. Boot into TWRP Recovery.
2. Tap on Multirom.
3. Tap on the 3 Dots on the Top Right of the Screen.
4. Select Settings.
You will find all the Customizations of the MultiRom Boot Menu you need there!
7. What is the No-Kexec Workaround?
- The No-Kexec Workaround by @nkk71 allows you to use MultiROM without having to flash a Kexec Enabled Kernel.
Please read More about No-Kexec Workaround from the author words only (to avoid duplicity and to get the latest information), thanks to @nkk71 once again!
http://forum.xda-developers.com/showpost.php?p=68738134&postcount=4
Download Links:
MultiRom Manager App 2.4-rishabhrao
Guys please test this in your Kenzo/Kate and Please tell me how it works
Will it work on 16 gb
pdpmoto said:
Will it work on 16 gb
Click to expand...
Click to collapse
All devices which support TWRP 3.1 official for kenzo or kate should definitely support this
Well try it out, definitely won't harm your device....
Also, uninstaller inckuded
Sent from my LeEco Le 2 using XDA Labs
Will test after exam
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
Everything is ok as of now twrp flashed but will check more if i am in my town because If something go wrong then i will fix with my pc
Does it support the sailfish os?
Is f2fs supported?
Because I can't inject current boot sector
Anyone know if MIUI works?
Installing now on miui,reaaaally thx,because I was working on it without any result....
I will report if it worked
---------- Post added at 08:26 AM ---------- Previous post was at 08:17 AM ----------
It doesn't work on miui
It injects mltrm but,after a reboot boots normally.
Also its impossible to add roms,it says:
Failed to extract update script
Erasing incomplete Rom...
Plz fix it....
SMYM said:
Installing now on miui,reaaaally thx,because I was working on it without any result....
I will report if it worked
---------- Post added at 08:26 AM ---------- Previous post was at 08:17 AM ----------
It doesn't work on miui
It injects mltrm but,after a reboot boots normally.
Also its impossible to add roms,it says:
Failed to extract update script
Erasing incomplete Rom...
Plz fix it....
Click to expand...
Click to collapse
Hey Thanks a lot for trying and reporting...
Can you test something?
Just install mrom from app
Then goto recovery and add rom and see if you can add roms?
Also try once without injecting anything?
Coz that sometimes works too?
Sent from my LeEco Le 2 using XDA Labs
午夜听雪 said:
Does it support the sailfish os?
Click to expand...
Click to collapse
try it !
Rishabh Rao said:
Hey Thanks a lot for trying and reporting...
Can you test something?
Just install mrom from app
Then goto recovery and add rom and see if you can add roms?
Also try once without injecting anything?
Coz that sometimes works too?
Click to expand...
Click to collapse
I can't add any rom and the mltrm menu hasn't been shown up...
SMYM said:
I can't add any rom and the mltrm menu hasn't been shown up...
Click to expand...
Click to collapse
Let me check it out once...
EDIT: Can anyone try on some Rom other than miui?
So i can get a sure idea if it's a problem only with Miui or with all Roms...
Sent from my LeEco Le 2 using XDA Labs
I tried installing a few different ROMs and it always gave an error..
Hope this helps
Doesn't seem it is able to install roms to the sd card
4I-I said:
I tried installing a few different ROMs and it always gave an error..
Hope this helps
Click to expand...
Click to collapse
I have exactly the same error...
SMYM said:
I have exactly the same error...
Click to expand...
Click to collapse
Download links
[email protected] said:
Download links
Click to expand...
Click to collapse
Download via the app attached to first post
{
"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"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Decryption
Installation :
Procedure:
1.Boot into TWRP(using old twrp that u guys use)
2.Go to wipe option (optional reason on 3 rd step)
3.Select format data ((if you want to make internal storage readable)(This will erase all data on internal storage)
4.Then go back and flash twrp installer from the install option.
5.After installation,go to reboot option (select recovery) and reboot.
6.Done!
Download Link : Download
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] TWRP-3.2.3-0 Permanent Installer [20190122], Tool/Utility for the Nokia 7 Plus
Contributors
nageen9211, sriram prakhya
Source Code: https://github.com/Ram9199/TWRP_Basil_Device_tree
Version Information
Status: Stable
Created 2019-01-22
Last Updated 2019-01-22
nageen9211 said:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Decryption
Installation :
Procedure:
1.Boot into TWRP(using old twrp that u guys use)
2.Go to wipe option (optional reason on 3 rd step)
3.Select format data ((if you want to make internal storage readable)(This will erase all data on internal storage)
4.Then go back and flash twrp installer from the install option.
5.After installation,go to reboot option (select recovery) and reboot.
6.Done!
Download Link : Download
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] TWRP-3.2.3-0 Permanent Installer [20190122], Tool/Utility for the Nokia 7 Plus
Contributors
nageen9211, sriram prakhya
Source Code:https://github.com/Ram9199/TWRP_Basil_Device_tree
Version Information
Status: Stable
Created 2019-01-22
Last Updated 2019-01-22
Click to expand...
Click to collapse
Make it normal flash able and also provide order twrp link
Great work bro.:good:
Purak6 said:
Make it normal flash able and also provide order twrp link
Click to expand...
Click to collapse
Normal flashable won't work with every rom , as every one is using different variant and different security patches .. that's why I have made it ...
nageen9211 said:
Normal flashable won't work with every rom , as every one is using different variant and different security patches .. that's why I have made it ...
Click to expand...
Click to collapse
And older twrp link ?
It's possible to use with TA-1055 or isn't tested on that variant?
death_jax said:
It's possible to use with TA-1055 or isn't tested on that variant?
Click to expand...
Click to collapse
test it and report. Bdw, android pie is preffered. It is reported that it stuck at boot logo on oreo roms
Purak6 said:
And older twrp link ?
Click to expand...
Click to collapse
i dont know about them, this is the fresh twrp . and we will maintain this only..
nageen9211 said:
[...] TWRP-3.2.3-0 Permanent Installer [20190122] [...]
Click to expand...
Click to collapse
can you please clarify what is mean "Permanent Installer"?
1) is this TWRP universal for any Android9 version? does not require exactly version?
2) is persistend after OTA update?
i ask because N7p don't have separate recovery partition and use hybrid boot for boot+recovery, this TWRP is not in boot partition?
k3dar7 said:
can you please clarify what is mean "Permanent Installer"?
1) is this TWRP universal for any Android9 version? does not require exactly version?
2) is persistend after OTA update?
i ask because N7p don't have separate recovery partition and use hybrid boot for boot+recovery, this TWRP is not in boot partition?
Click to expand...
Click to collapse
yes, This installer will unpack your boot.img from your current rom , and patch the twrp in it and repack it.
it works on almost all pie roms . have problem on oreo gsi .
and i think.. as long as boot partition is not affected by ota (which most of the times is affected ) twrp will persist. other wise u have to repatch your boot.img with this installer.
How to install twrp recovery on Nokia tell me set by step
bharath moram said:
How to install twrp recovery on Nokia tell me set by step
Click to expand...
Click to collapse
You can use this me howto for Magisk install:
https://forum.xda-developers.com/nokia-7-plus/help/pie-october-update-failed-t3862758/post78285662
Where is say Magisk.zip you use TRWP installer zip from first post in this thread..,
Good work, sir.
By the way, does it have format data to f2fs support? TWRP images for this device out there doesn't have.
Lot of warnings in recovery.log
Thanks for making this!
I'm getting lots of warnings like this one:
Code:
WARNING: linker: Warning: couldn't read "/system/etc/ld.config.txt" for "/sbin/busybox" (using default configuration instead): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered
Should I be worried about TWRP correct functioning?
Busybox seems to be all well and good though!
k3dar7 said:
You can use this me howto for Magisk install:
https://forum.xda-developers.com/nokia-7-plus/help/pie-october-update-failed-t3862758/post78285662
Where is say Magisk.zip you use TRWP installer zip from first post in this thread..,
Click to expand...
Click to collapse
Hi, thanks for this.
But after I fastboot boot the twrp boot img, all the folder names in TWRP are strange, like they're encrypted. How do I get around this?
Read step 3 in the OP. You have to format data.
I've found that using another twrp image to boot (not flash) it decrypts the data by asking the pattern I've set up in the os.
Now I want to ask the dev @nageen9211 if he can use that image to make this script.
ban.codrut said:
Read step 3 in the OP. You have to format data.
I've found that using another twrp image to boot (not flash) it decrypts the data by asking the pattern I've set up in the os.
Now I want to ask the dev @nageen9211 if he can use that image to make this script.
Click to expand...
Click to collapse
Thanks for the reply - actually I tried the OP originally, but formatting data got rid of my google play services as well, and I couldn't use my phone at all as a result, because a popup saying "google play services stopped working"/"google battery saver had stopped working" kept popping up repeatedly.
I had to reflash using OST and start over again. Which is why I was interested in another method without formatting data
Unless there is a way around fixing the Google Play services issue after formatting data?
Iam using Nokia 7 pLus rom having Android pie how to install twrp recovery tell step buy step
bharath moram said:
Iam using Nokia 7 pLus rom having Android pie how to install twrp recovery tell step buy step
Click to expand...
Click to collapse
If you have unlocked bootloader, howto i write before some mess on this page of this thread.. then first step is read this thread
I saw that on 15 of april was out the 3.3.0-0 of TWRP...how can we get it?
There is a very good changelog, especially for our A/B device(s):
Merge AOSP 9.0 r3 (Dees_Troy)
Use ANDROID_ROOT variable instead of hard coding to /system (CaptainThrowback)
Decrypt FBE on 9.0 and metadata decrypt (Dees_Troy)
vold decrypt updates (CaptainThrowback and nijel8)
Support vibration on LED class devices (notsyncing)
Metadata decrypt support for Pixel 3 (Dees_Troy)
Support rotating the display via build flag (vladimiroltean)
Reboot to EDL mode button (mauronofrio)
Support MTP on FFS devices (bigbiff)
Update FDE decrypt to support keymaster 3 and 4 (Dees_Troy)
Detect mkfs.f2fs version to properly format on f2fs partitions (Dees_Troy)
Allow TWRP to use md5 and sha256 checksums for zip installs (bigbiff)
TWRP can use /data/cache/recovery and /persist/cache/recovery on AB devices with no cache partition (bigbiff)
Switch part of advanced menus in TWRP to use a listbox of options (Dees_Troy)
Use magiskboot to allow repacking boot images for installing TWRP (Dees_Troy with thanks to topjohnwu of course)
{
"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"
}
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 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
I've put a huge amount of time and effort in this SOLO project (no other dev has been involved), so respect me and respect my work. You are NOT allowed to use this rom, its vendor or any of the other files included as base for your projects.
FEATURES
OneUI 2.0 under Android 10, ported from the SM-A750FN
All G610 variants should be supported
Arm64 with Treble support
Fully deodexed
SIMPLE-KERNEL included, compiled from A600FNXXU5CTB9 sources. Built permissive
Deknoxed, debloated, and removed all samsung useless security stuff in rom and kernel level
N20 multi CSC with additional features (call recording, etc)
And many more!
KNOWN BUGS
Light in capacitive buttons for those devices with hardware buttons
Some 3rd camera apps like footej don't work. Whatsapp video calls could be bugged too. If so, use Whatsapp business
Other inherent bugs from OneUI and/or 7870 limitation
You tell me
DOWNLOAD
Current version: 6.0 (02/12/2020)
More info in 2nd post
INSTALLATION
Vendor partition is required.
Wipe system, data (clean install mandatory), vendor, dalvik&cache and cache
Flash rom zip
Reboot
First boot will take much time, be patient
SCREENSHOTS
https://imgur.com/a/Q5Ysvoz
ROOT
Flash Magisk canary. Stable Magisk will give bootloop.
SUPPORT
Telegram group
CREDITS
Me, for infinite hours spent with this project
Special thanks to @ananjaser1211, @SPARTANICUS and @Valera1978 for their huge contribution to the 7870 development
Thanks to my testers and @neel0210 for camera rework
And thanks one more time to @SaiFurR for his design work with banner
@topjohnwu for Magisk
DONATIONS
I don't need them, I don't need coffees or beers. I really hate see here people with high end devices asking for donations, but you can still donate money to charity. Donate money or simply help people that is really needed. If you like this rom you can make me very happy just pushing THANKS
XDA:DevDB Information
H-ROM A7 PORT, ROM for the Samsung Galaxy J7
Contributors
Astrako
Source Code: https://github.com/samsungexynos7870/android_kernel_samsung_exynos7870/tree/simple_q_permissive
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Oreo bootloader
Version Information
Status: Stable
Current Stable Version: 4.0
Created 2020-07-19
Last Updated 2020-08-27
H-ROM A7 PORT V6.0 (02/12/2020)
November security patch
Fixed Dual sim detection
Added High Perfomance mode
Setting volume in different apps should be fixed
You will need around a 3100Mb system partition, so if you dont have it, go and flash my repartition script
GoogleDrive folder
Mega
Md5: a9f3cacee034142024fd2802eed21b61
Spoiler: Old versions
H-ROM A7 PORT V5.0 (27/08/2020)
Spoiler: Old versions
Firmware ported from A750FNXXU4CTG2. July security patch
Added SIMPLE kernel
Echo in calls should be fixed. Other minor bugs can be present depending the phone/variant
You will need around a 3100Mb system partition, so if you dont have it, go and flash my repartition script
GoogleDrive folder
Mega
Md5: 87fc5ef5c031a2f586d762debcf7b3e0
Added a navbar enabler/disabler to the download folder
H-ROM A7 PORT V4.0 (19/07/2020)
Firmware ported from A750FNOXM4CTE3. June security patch
Specifig bugs: echo in calls
GoogleDrive folder
https://drive.google.com/drive/folders/13UG-hdqWU8nud1JCm6DD0vQXAQjeJCVP
Remember, a lot of time has been put in this project. If you like it and want to support me, no donations at all are required, just pushing thanks buttons.
Reserved
Great job
what is vendor partition? can you explain more detail? this is the first time im going to try treble rom. i dont understand what is vendor partition (what is that? is it a flashable file? or what?)
leo31 said:
what is vendor partition? can you explain more detail? this is the first time im going to try treble rom. i dont understand what is vendor partition (what is that? is it a flashable file? or what?)
Click to expand...
Click to collapse
Vendor partition is a partition that comes with treble supported phones j7 isnt one of them but with project spaget you can enable treble support on our phone so that it can install treble roms. To get the vendor partition got to this link and download the latest version (spaget x) and flash create vendor 2.0 and you will have a vendor partition.
which kernal is install ? .... i have downloaded h20 rom for g610f but i face some problem such as phone stuck and reboot automatically.... so i need to know whick kernal is installed......
Great work on the ROM
Kindly help with a working SIM Toolkit zip file for this ROM. Or anybody with a working SIM Toolkit zip file can help me with it. Thanks.
HELP! no me deja hacer vídeos llamadas en ws, en j7 prime
won't let me make video calls on
facing random reboot twice on setup screen, now it boot. no flash light on camera (light burst from screen?) like stock oreo.
hyperlapse - wide selfie nor working
i dont even know what is hyperlapse
@Astrako will you keep H-ROM A7 and S20 versions support simultaneously?
Adriano-A3 said:
@Astrako will you keep H-ROM A7 and S20 versions support simultaneously?
Click to expand...
Click to collapse
Don't ask ?... just install the rom and enjoy bro
Mscreams said:
Don't ask ... just install the rom and enjoy bro
Click to expand...
Click to collapse
Bruh
I can't install it please get me a complete manual for install
With spaget x project get bootloop l
Without show logo cant boot
Recovery: Orange Fox
Vendor 2
G610f/ds
use vendor create v1 not v2
yahiaashraf111 said:
use vendor create v1 not v2
Click to expand...
Click to collapse
And don't need change recovery ?
Now it's OrangeFox based twrp 3.4.0
Should install spaget x?
What working :
1. Wifi
2. Mobile data
3. Hotspot
4. Bluetooth
5. Gps
6. Camera
7. Phone
8. Live drawing camera
9. screen recording
10. Almost everything are working well
But, so far i found some 'not so important' bugs :
1. Opening battery usages give me FC.
2. I cant rename, remove files inside priv-app folder, but copying files to folder inside priv-app worked.
3. Removing app which located on priv-app folder using titanium backup, did not removed the apps. After reboot, the apps are there again. (Problem number 2, i cant remove apk inside priv-app)
4. no blue-light filter (i dont use it, so i dont care)
5. Some camera feature not working (hyperlase, wide selfie, front facing camera only support 4:3 size for taking photo, but video are fine). I dont know what is the function of icon at the right side of resolution inside camera (right side of 4:3 icon)
6. Since aod is not working and im not using it, better remove it.
7. Cant change clock style on lockscren (inside phone setting), but fixed by installing lockstar
8. Screen mode inside display setting has no effect at all (even stock rom does not have that feature, so.... No problem at all)
I really love this rom! Why? Because :
1. Battery life is PERFECT
2. Performance? This rom is running perfectly smooth on UI, and also while playing game and opening apps.
3. Multitasking is great
4. Android Q on 2016 device? Hell yeah.
Please fix the 1st and 2nd problem, because i need to replace gametool apk inside priv-app folder.
Installation variant 610mn-16gb
Installation variant 610mn-16gb
1- Have prepared the Vendor.zip and revertvendor files specifically this => Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor <= not vendor v2.0 and it is not necessary to download Exynos7870_Spaget_X-V3.0. If you want root, download the magisk provided on the first page. Also have OrangeFox-R10.1_2-Unofficial-on7xelte and a version of a preferable rom oreo available to reverse the vendor and reinstall for anything.
2- Before flash create vendor, install OrangeFox-R10.1_2-Unofficial-on7xelte and restart fox recovery, then flash create vendor, without deleting anything and restarting recovery, once in TWRP-Fx, follow the steps on the first page , wipe 1DC, 2C, 3S, 4V, 5D. Internal memory is not necessary (if you view the preload between the partitions, in this step, read notes below), once the wipe has finished, install the ROM and restart. Everything should work perfectly, (at the end of the startup, perform a hard restart before configure, and then it starts without problems, that happened to me, in particular, since generally when finishing the installation of the ROM and when rebooting it usually restarts again, in this case it did not, I start directly until hello .. and then reboot)
3- Optional, once the startup is configured, restart TWRP-FX and flash magisk.
Notes: At the beginning, you could not install any ROMx64, or you needed the vendor partition, you can check the following: when you install TWRP 3.3 and when you start TWRP, the following appears in red letters at the top: “recovery is not seandroid enforcing… .. etc ”it only comes out with twrp from version 3.3, definitely you will not be able to install any rom x64, gsi, etc, since you don't have to get any errors or messages. It means that also like mine you have the smartphone since marshmallow 6.0 and it was root with supersu and odin, and you were making updates from that version; solution: restore with stock Firmware android 8.1 via odin all the partitions (BL-AP-CP-CSC-USERDATA) can be found on the network and downloaded according to your country, but always being oreo stock 8.1. Once this is done, install TWRP 3.2 with odin and then root with magisk latest stable version, not the one provided here. After that, you will be able to install several roms that you could not previously and will not have problems with the vendor, create and revert if you want. Some only install the AP to fix, but I decided on a full restore and start from scratch.
PD: I felt the need to share this experience with you so that those who have the 610mn and have problems can install it without problems, always remember to back up your important data before flashing and having a good battery charge *GOOGLE TRANSLATE*
RODRI2688 said:
Installation variant 610mn-16gb
1- Have prepared the Vendor.zip and revertvendor files specifically this => Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor <= not vendor v2.0 and it is not necessary to download Exynos7870_Spaget_X-V3.0. If you want root, download the magisk provided on the first page. Also have OrangeFox-R10.1_2-Unofficial-on7xelte and a version of a preferable rom oreo available to reverse the vendor and reinstall for anything.
2- Before flash create vendor, install OrangeFox-R10.1_2-Unofficial-on7xelte and restart fox recovery, then flash create vendor, without deleting anything and restarting recovery, once in TWRP-Fx, follow the steps on the first page , wipe 1DC, 2C, 3S, 4V, 5D. Internal memory is not necessary (if you view the preload between the partitions, in this step, read notes below), once the wipe has finished, install the ROM and restart. Everything should work perfectly, (at the end of the startup, perform a hard restart before configure, and then it starts without problems, that happened to me, in particular, since generally when finishing the installation of the ROM and when rebooting it usually restarts again, in this case it did not, I start directly until hello .. and then reboot)
3- Optional, once the startup is configured, restart TWRP-FX and flash magisk.
Notes: At the beginning, you could not install any ROMx64, or you needed the vendor partition, you can check the following: when you install TWRP 3.3 and when you start TWRP, the following appears in red letters at the top: “recovery is not seandroid enforcing… .. etc ”it only comes out with twrp from version 3.3, definitely you will not be able to install any rom x64, gsi, etc, since you don't have to get any errors or messages. It means that also like mine you have the smartphone since marshmallow 6.0 and it was root with supersu and odin, and you were making updates from that version; solution: restore with stock Firmware android 8.1 via odin all the partitions (BL-AP-CP-CSC-USERDATA) can be found on the network and downloaded according to your country, but always being oreo stock 8.1. Once this is done, install TWRP 3.2 with odin and then root with magisk latest stable version, not the one provided here. After that, you will be able to install several roms that you could not previously and will not have problems with the vendor, create and revert if you want. Some only install the AP to fix, but I decided on a full restore and start from scratch.
PD: I felt the need to share this experience with you so that those who have the 610mn and have problems can install it without problems, always remember to back up your important data before flashing and having a good battery charge *GOOGLE TRANSLATE*
Click to expand...
Click to collapse
Hello
Thanks for your help
This installation help isn't for F variant?
SyntaxDroid said:
Hello
Thanks for your help
This installation help isn't for F variant?
Click to expand...
Click to collapse
Really if it could work, especially if you have been making updates from android v6, it is best to start the root from android v8.0 or 8.1, once achieved, try the installation, but if you already come from that version, you shouldn't have drawbacks. Try it, it's really worth it.