Does anyone have working solution for Multi boot or dual boot for Sprint variant?
I've tried with MultiROM but no luck with that. The modified TWRP doesn't work with Sprint so good.
Thread here > http://forum.xda-developers.com/showthread.php?t=2460886&highlight=sprint
Related
Today i get error while installing magisk on dual boot rom
Here my setup:
Device: Redmi Note 4X (codename: mido)
Primary rom: crDroid Official v3.8.2 (Android 7.1.2)
Secondary rom: MIUI 9 v9.0.4.0 (Android 7.0)
Recovery: Red-Wolf 021 based on TWRP 3.1.1
Error when installing on secondary rom, even i already patched magisk zip with dualboot patcher tool for windows i still can't install it.
Screenshot and logs attached.
Cc @topjohnwu
There was recently a guide posted about that. Tried that?
Searching the forum works pretty well sometimes...
Didgeridoohan said:
There was recently a guide posted about that. Tried that?
Searching the forum works pretty well sometimes...
Click to expand...
Click to collapse
When i reate this bug there no suggestion thread like my problem
Method 2..
Just patch Magisk v12.0
Flash from dual boot patcher
Reboot to non-primary ROM
Install magisk manager app (latest)
Flash magisk v14.0/14.3 manually
Reboot
Click to expand...
Click to collapse
Does "Flash from dual boot patcher" is same as flash rom on dual boot patcher app?
exodius48 said:
When i reate this bug there no suggestion thread like my problem
Does "Flash from dual boot patcher" is same as flash rom on dual boot patcher app?
Click to expand...
Click to collapse
Using the correct search terms is the hardest part about finding useful information...
Ask in the guide thread. I have absolutely no clue about dual boot.
Didgeridoohan said:
Using the correct search terms is the hardest part about finding useful information...
Ask in the guide thread. I have absolutely no clue about dual boot.
Click to expand...
Click to collapse
OK.
But we would happy if magisk support dual boot out of the box in the future as of supersu already did it. @topjohnwu
I was doing some research about custom roms for the mediatek variant (nicklaus), and found lineage 14.1 and 15 from some user on android filehost, anyone has tried the roms or know what is happening with the development of the mediatek variant??
i can provide the link where the roms are alocated, i dont know if the account belongs to some user banned, that is why i dont post any link. if you want it, pm me
sorry for my english and any misundertood
15 don't boot, and 14.1 donĀ“t have pt br lang.
try rr 5.8.5 v1.3
works all fine.
I try rr 5.8 but boot loader logo stuck my phone is xt1772 mt6737
i have the same model, that is why i wanna know about these roms
you need wipes
install the 3 img files, each one on your correct partition.
restart the system, back to recovery and install gapps pico arm 7.1
works fine.
Not working
I tried lineage 14 and lineage 15 to my device Mediatek Variant (XT1770).
None of them are working.
Error: Stuck at Boot Animation.
I've seen RR 6.0.0 on that guys android file host, but the latest TWRP (3.2.1) he provided doesn't work on XT1771, so i can't flash it :\
Hello everyone,
I recently wanted to root my galaxy tab s2 and install a custom rom on it to enhance performance, someting i've done before with my old phone where everything worked fine. So i used autoroot to root the tablet which worked fine and choose to install lineageos afterwards. i found a fitting version of lineage on their official website, installed twrp on my tablet and used it to install lineageos and GApps. However i did not unlock my bootloader using adb since i didnt have to do that back when i rooted my phone and i read on a forum that unlocking oem in the developer settings would be enough. This is where the problems start. After i installed the custom rom the tablet would try to boot into the os for a couple of minutes only showing a loading animation just to boot straight into recovery mode afterwards. In an attempt to fix the error i used odin to install a stock rom from sammobile on the tablet. However now it doesnt even boot into recovery anymore. instead it only shows the stock rom loading animation until the battery emptys. Though i can enter download mode from that position and then cancel it in order to reboot the device which enables me to enter recovery mode. Does anyone have an idea how i could boot a normal os again or is the device hard bricked? The only idea i have left is trying to install a new os from an sd card.
I have the same issue. I installed unofficial lineageos 16 to exynos 2015 t810. I have newest odin and twrp. Im wondering if i need to install or unlock the bootloader to get past the logo loop then recovery bootup after 5 minutes. I followed clean tutorials.
Update: i found this to try.
Quote:
Originally Posted by -beluga-
Hi, first of all thanks for the ROM. Unfortunately I am unable to get my T710 running properly with today's packages (it ran 15.1 so far)
- lineage-16.0-20191009-UNOFFICIAL-gts28wifi.zip
- addonsu-16.0-arm-signed.zip
- open_gapps-arm-9.0-pico-20191009.zip (some with nano or stock)
I am doing a full clean install every time (over 10x so far) but only get it to boot using the ROM alone. Any mod, such as addonsu, gapps or even trwp app cause it to show the Lineage boot screen for quite a while until dropping back into TWRP. Since there is a virtually infinite amount of permutations which versions to try - can someone who is successfully installed 16.0 with Gapps on a T710 let me know their version combination please?
Thanks.
pico-20191009 is giving problems with the 1009 build on my T810 too. Pico-20191006 and Magisk 19.4 are doing the trick for me.
Don't know about other combinations
BTW, it's advised not to install the TWRP app as it is known for causing bootloops on this rom.
Don't know for sure, but wiping internal storage before installing rom might be useful too.
I wanted to start this thread to keep up with the information i've gathered working with this.
So far, magisk roms seem to work fine.
Working with other roms built for other OP7P models is not, however, ive had good progress with one. I initially tried havoc (didn't know it but it was Q based) and flashing each partition in fastboot worked, but i had no service. No sim error in fact. I then used a recovery msm tool and went back to OOS. Proximity sensor broke for some reason.
I then tried the same thing but with a Pie based Havoc rom. No dice, twrp wont even boot (twrp would boot on the opposite slot and install to both). Even with installing twrp, it wouldnt load it or the os. Now, im going to continue testing things out here, but if anyone has any more info or wants to try this, that would be awesome.
Update: Tried Aosip, same as Havoc pie. I found I was able to store my OOS Pie installation on slot B, and reboot to it by changing slots with
Code:
fastboot --set-active=other
fastboot format userdata
fastboot reboot
How can i dual boot? So i can boot into testing roms/kernals with out messing with my working main boot, using twrp. Im on 3.7 twrp