Related
Is is possible two set an Andriod device up to have one rom on the internal memory of the phone and then another custom rom on the SD card and just be asked which way you want to boot it up when you turn it on or reeboot. could be a good way to test out new versions of roms almost side by side.
I used to have two versions of win on my pc and choose which way to boot it up when rebuliding it so other peole could use the machine still while i was in the process
Anyway just and idea
I am pretty new here but love the forum
Cheers
TheKaptone
Good question, i want know the same.... ++1
As far as i know it is not possible with an android phone. There are possibilities to dual boot with wm.
You could keep both ROMs as flashable version on your SD card and just switch by flashing another one. I don't know if you would retain all data like call history or sms if the roms are too different.
Well whaddaya know, the HTC Desire has taken on a new amazing feat; it can now dual boot ROMs. While I sit here in jealousy I must ask, how is this possible? I mean is it device specific? I'd love to dual boot on myTouch, I have 3 SD Cards just laying around chilling, and they would be really useful for this.
http://forum.xda-developers.com/showthread.php?t=1173309
We're always missing out on some, this is on many htc devices I've noticed, including things like the Cwm4 recovery. I wish I could help get those things on our phones.
Sent from my HTC Glacier using XDA App
What is dual boot?
Sent from my HTC Glacier using XDA App
Google: What is dual boot? ANSWER: A dual boot system is a computer system in which two operating systems are installed on the same hard drive, allowing either operating system to be loaded and given control. When you turn the computer on, a boot manager program displays a menu, allowing you to choose the operating system you wish to use.
Click to expand...
Click to collapse
In our case it would be the device your using is partitioned for two seperate areas in which two independent Roms are installed, when you first power on the device you get a boot manager that gives you a choice to boot into one or the other.
The issue with doing this with a phone is the two Roms you choose would have to be able to run on the same Kernel. So if your running a Sense Rom and you decided to install an AOSP requiring a different kernel on the other partition you would run into some real issues.
This is completely doable on our device, the question is how important is it for anyone to have and would you mind giving up battery time for the feature, YES this will cause you to drink up some power which is something most Devs work hard on to keep consumption down.
EDIT: You can follow the same instructions here but there maybe a few things you need to do in C for this to work properly I didn't look to far into it, Also I would upgrade the SD Card as your going to have to have 3 partitions so an 8gb will get real crowded quick if you try to do this. The least I would try this with is a 16gb considering all of the files you may have already on your sd card that apps need for cache, pics, storage, ect.
I'll see what I can do with it after I pick up a 32gb sd card but it shouldn't be too hard.
Orical said:
In our case it would be the device your using is partitioned for two seperate areas in which two independent Roms are installed, when you first power on the device you get a boot manager that gives you a choice to boot into one or the other.
The issue with doing this with a phone is the two Roms you choose would have to be able to run on the same Kernel. So if your running a Sense Rom and you decided to install an AOSP requiring a different kernel on the other partition you would run into some real issues.
This is completely doable on our device, the question is how important is it for anyone to have and would you mind giving up battery time for the feature, YES this will cause you to drink up some power which is something most Devs work hard on to keep consumption down.
EDIT: You can follow the same instructions here but there maybe a few things you need to do in C for this to work properly I didn't look to far into it, Also I would upgrade the SD Card as your going to have to have 3 partitions so an 8gb will get real crowded quick if you try to do this. The least I would try this with is a 16gb considering all of the files you may have already on your sd card that apps need for cache, pics, storage, ect.
I'll see what I can do with it after I pick up a 32gb sd card but it shouldn't be too hard.
Click to expand...
Click to collapse
That was mentioned in the Desire HD thread. They say if you want to use a Sense and an AOSP ROM, you're going to have to use the Sense kernel and deal with the problems that may occur, like no bluetooth. Additionally, it seems to break Wifi for almost everyone who use it. Nevertheless its freaking awesome, and something I'd love to do.
There's not much to this and it can be implemented easily. I did it a different way, but the way the guy on that desire HD thread works much more elegant than my way did (although my way allowed for two different kernels).
To understand how this works, you first have to understand the boot process. When you turn on the phone, the bios starts the radio and then the radio starts the SPL which contains the information for partitioning, location of boot on nand, etc.
Unless you interrupt normal spl boot (which would take you to the other two boot options, spl and recovery), the spl looks for the "init" program in the specified boot partition.
This init program can be anything. From a basic linux perspective, it could be a simple script to set-up devices and then just toss user control to a command line (for basic linux usage) or, in Android's case, it runs the init scripts (device.init.rc and init.rc) and has the kernel run the whole Android stack.
What this guy did was make his own init program (I haven't looked at the thing since I'm at work) which, from what I read, is just a small binary, which possibly relies on two different init scripts to boot either from nand (mmcblk0p25) or sdcard (mmcblk1pX [depending on your partitioning]).
The disadvantage to this is that, as he stated, you can only use one kernel, since boot is still starting as normal and the spl is booting to the boot partition which only contains one kernel (you can toss in more, but only one will be started by the spl) and then his init program takes care of the rest of the bring-up.
The way I did it was having two boot images for two different builds, my regular nand rom (which would boot when booting normally) and my SD build (which would boot instead of recovery). All this requires is flashing a boot.img to recovery and then modifying the init.rc to boot from SD (mmcblk1pX) instead of nand. The clear disadvantage, ofcourse, is the loss of recovery, but by using this guy's method, I could have a menu on the SD boot to boot either the SD build or a recovery (means a modified recovery rather than a regular boot.img).
Both options are easily doable on any rooted device. The one thing lacking currently is a recovery that will allow to update.zip install to sdcard (I'd suggest using partitions 4 for system and 5 for data, since 2 and 3 are historically been used for sd-ext and swap).
So you guys can just find a recovery dev, point him to this thread, and show him my post to see if he can make such a recovery (should be easy) and it could become mainstream feature of rooted androids.
Bump. This would be amazing to port over. This would be donation worthy.
Sent from my HTC Glacier using XDA Premium App
im trying to get madmaxx to compile the mt4g into that amazing 4ext recovery he made. It's like amon_ra recovery but better!
Sent from my HTC Glacier using XDA Premium App
You can dual boot on the MT4G with Boot Manager,available in the Android Market, though it cost 2.99 but it does allow you to run two separate ROMs.
I got BootManager but i need to set everything manually and i dont know them can someone help me with these?
What is your sdcard block?
What is your system's size in mb?
What is your data's size in mb?
What is your cache's size in mb?
I have MIUI DemonSpeed 1.29 and the 8gb sdcard that comes with the mytouch
harei84 said:
You can dual boot on the MT4G with Boot Manager,available in the Android Market, though it cost 2.99 but it does allow you to run two separate ROMs.
Click to expand...
Click to collapse
is it officially supported? I have a fear of it writing to the wrong partition and fμck up the device.
GazaIan said:
is it officially supported? I have a fear of it writing to the wrong partition and fμck up the device.
Click to expand...
Click to collapse
its not supported it asks the questions i posted in the first page <
I really know nothing about the app just saw a feature about it on Lifehacker.com
It works on myTouch 4G. It is supported, but support is weird. Im beta testing one that works and for the most part everything works as it should, but the app recognizes the phone on Virtuous Unity and doesn't recognize it in MIUI. I'm triple booted at the moment (I can install 2 more ROMs, but I don't want to) and MIUI is on the SD Card and doesn't recognize my phone.
Bottom line is, it works, try it. It's definitely worth the $2.99.
Doesnt work
Sent from my HTC Glacier using XDA Premium App
I take that back it does running VI 1.31 double shot and miui
Sent from my HTC Glacier using XDA Premium App
Thanks to @chenxiaolong DualBoot is possible on LG G5 (root and twrp needed)
Original thread for DualBoot patcher is located here:
http://forum.xda-developers.com/showthread.php?t=2447534
Bugs report or questions for the developer please post in original thread.
Questions about how to use DualBoot you can ask here.
Download patcher app from here:
https://dbp.noobdev.io/files/9.1.0....tcherAndroid-9.1.0.r38.g5d5b401-snapshot.apk
DualBoot Patcher is still under development, expect bugs.
I'm not responsible for bricked phones.
You have been warned!
How to:
First make nandroid backup in TWRP!
1. Install DualBoot patcher apk, open an app and go to ROMs section
2. Set the current running kernel as kernel for Primary ROM (app will ask you to do so)
3. Download CM13 or any different AOSP ROM, Gapps and go to "Patch zip file" section.
Use minimal Gapps if you installing on stripped /system partition.
4. Patch the CM13 ROM zip (for LG G5 choose "secondary") and patch Gapps ("secondary")
a) Go to settings of the app and install Boot UI.
25.11.2016 -> Note for H830 users,go with data slot instead of secondary until the secondary slot is fixed.
5. Flash patched ROM and Gapps in TWRP or ROMs section in DualBoot app, click red button to do it.
6. Go to ROMs in the app and tap on the rom you want to boot
7. Reboot
You second system should start. (if you get a black screen,wait a bit,first boot usually takes a while)
How to switch between ROMs:
1. Both ROMs needs DualBoot patcher installed, in "ROMs" section you should see ROMs list.
2. To switch the ROM simply tap Primary or Secondary, tick indicator should appear on ROM.
3. Reboot
To check partition sizes and free space, go to "Free space" section.
App sharing probably still don't work, I didn't try it but most likely after you try it you will need to restore your nandroid.
Location explanation :
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
Lockscreen security solution:
On all ROMs you must set lockscreen to have the same lock e.g. a pattern lock with the same pattern on each ROM to unlock.
The issue has something to do with the secondary ROM overwriting the gatekeeper.pattern.key file, so then when you switch to primary you have a pattern lock but with no correct pattern even set, hence why the pattern you enter is always incorrect.
Steps:
1. Set lockscreen security (what ever you decide to use, fingerprints,pin,password, pattern) in the secondary rom first.
2. Set the exact same lockscreen security in the primary rom
3. That's it,now it works on both roms
Tested on LG G5 H850, I'm running stock lg rom as Primary and CM13 as Secondary.
Tested stock roms with aroma installer,doesn't work as secondary,only as primary.
Tested on LG G5 H830, everything works now.
Stock can't be dual booted as secondary due to size,so go with other slots like,for example, data slot
If in app flashing doesn't work,use twrp to flash the patched ROM and the patched gapps
Since the 25.10.2016 the SD card bug on second rom is fixed,link above updated.
Since 25.11.2016 LG G5 H830 is supported, thanks to jeffsga88 for helping with that.
Updated: 04.12.2016
Awesome, thanks....
Enviado desde mi LG-H850 mediante Tapatalk
I can comfirm this works well running stock rooted and cm13 beta with no issue. Many Thanks
It doesn't seem to work on the h830 : (
eminem5055 said:
It doesn't seem to work on the h830 : (
Click to expand...
Click to collapse
Can you explain that a bit more,did you followed the steps,what happened after reboot,did you chose to boot in cm13 before restarting?
onestyle007 said:
Can you explain that a bit more,did you followed the steps,what happened after reboot,did you chose to boot in cm13 before restarting?
Click to expand...
Click to collapse
When trying to flash the cm13 dual from twrp it told me that the file was for h850 (which makes no sense because the rom clearly supports h830).
eminem5055 said:
When trying to flash the cm13 dual from twrp it told me that the file was for h850 (which makes no sense because the rom clearly supports h830).
Click to expand...
Click to collapse
I also have the h830 and got the same error message.
---------- Post added at 10:30 PM ---------- Previous post was at 09:47 PM ----------
eminem5055 said:
When trying to flash the cm13 dual from twrp it told me that the file was for h850 (which makes no sense because the rom clearly supports h830).
Click to expand...
Click to collapse
The issue is not with rom, the issue is with the patcher. I believe that as of now, the patcher supports only the h850 version.
If the issue is with the patcher then I'm sure it won't be that hard to fix.
Yeah I've just looked at the zip created by the app, it automatically sets it for h850. Thanks for letting me know
onestyle007 said:
Thanks to @chenxiaolong DualBoot is possible on LG G5 (root and twrp needed)
DualBoot Patcher is still under development, expect bugs,currently on LG G5 there is an sd card bug on second rom,shows as corrupted,hopefully it will be fixed soon!
Click to expand...
Click to collapse
Any news regarding the sd card bug?
Thank you in advance
kafisc said:
Any news regarding the sd card bug?
Thank you in advance
Click to expand...
Click to collapse
No news yet. If anything changes I'll inform everyone about it in the first post
Can I have CM 13 as primary and Stock ROM as secondary using a flashable zip?
nima0003 said:
Can I have CM 13 as primary and Stock ROM as secondary using a flashable zip?
Click to expand...
Click to collapse
I had a problem with aroma,so if you have stock zip without aroma you can patch it and use it as secondary
onestyle007 said:
I had a problem with aroma,so if you have stock zip without aroma you can patch it and use it as secondary
Click to expand...
Click to collapse
OK thanks!
So if I wanted it to work on h830, I would have to port the patched ROM to work on h830?
nima0003 said:
So if I wanted it to work on h830, I would have to port the patched ROM to work on h830?
Click to expand...
Click to collapse
I would assume so, the rom would have to be compatible with H830. From what i can tell the Boot Patcher allows you to patch a rom to work on a different partition/slot. It uses a certain set on scripts before to allocate where the files will go then the rom is installed as it normally would.
Please correct me if im wrong anyone
Hi, is the version here different in any way from the original version? Thanks
bonotheedge said:
Hi, is the version here different in any way from the original version? Thanks
Click to expand...
Click to collapse
Version that is posted here has support for LG G5,and since lg g5 is not fully supported (sdcard issue) it's not added to the original version. That's the difference
Thanks. That's what I thought. I hope that this version in some point will also support h830.
Any news about his being available on the h830?
Are any devs working on a method to repartition the Pixel? It seems that most flashing issues are due to the A/B partition scheme. Also, in the case of custom ROMs, the duplicate partitions are a waste of space (unless you want to dual boot, which doesn't work well either since the data partition is shared).
Anyway, it would be awesome if the Pixel could be repartitioned.
I think this is highly unlikely. The Nexus 7 had a laughably small system partition, which led to people being SOL when trying to get newer Android versions and gApps to work together. The other reason this is unlikely is because it's a pretty dangerous process (mess something up and you might completely brick the device, since factory images don't do any partitioning work), and this would modify the hashes used by SafetyNet, so there would be no easy way of passing the CTS checks.
The a/b partitions weren't made for dual booting, they were made for google and ota's/updates
Now, you can dual boot with the same custom rom, one rooted, the other non-rooted same with stock.
Sent from my Pixel using XDA-Developers Legacy app
creeve4 said:
Are any devs working on a method to repartition the Pixel? It seems that most flashing issues are due to the A/B partition scheme. Also, in the case of custom ROMs, the duplicate partitions are a waste of space (unless you want to dual boot, which doesn't work well either since the data partition is shared).
Anyway, it would be awesome if the Pixel could be repartitioned.
Click to expand...
Click to collapse
What space are you wasting? Its the system partition. The biggest reason I think that it exists is for the seamless updates. Its also a redundancy should you not be able to boot or an OTA fries your device.
The only issues I have ever had (and most of the ones I have encountered) were users not doing research. Its not hard to flash on this device, its just that details arent laid out very well and up to date in any one spot.
Can we continue to discuss topics about the new - big thx to devs, btw! - official 17.1 version in this thread, pls?
(I know the differences to the unofficial version(s) might be minimal - or even null? - however I think it's always of value to be as clear, sharp and crisp avoiding ambiguities, esp. for folks who are not too familiar with the different contexts)
BTW: just for the record my (dirty) upgrade path from lineage-16.0-20201003-nightly-hlte-signed.zip version to lineage-17.1-20201010-nightly-hlte-signed.zip was as follows:
DLed / copied off my NAS the files of lineage-17.1-20201010-nightly-hlte-signed.zip, open_gapps-arm-10.0-nano-20201010.zip and Magisk v20.4 to external SD)
Let the system DL and install recent pending updates
Rebooted into Recovery (twrp-3.4.0-1-hlte)
Created a nandroid backup of Boot, System, Data and EFS partition to internal SD (and copied those to the external SD, plus a further copy to my NAS)
Wiped Dalvik / ART Cache, System and Cache partition
Installed LOS and GApps
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Rebooted into Recovery
Installed Magisk
Wiped Dalvik / ART Cache
Rebooted into System
(Enabled systemless host file in Magisk to support Adaway Adblocker app)
PS: This thread has been moved off the Development Folder by a Forum Moderator
Quick questions:
1. Does that AdAway work well?
2. Does automatic dark mode work for you? I have to turn it on manually. Maybe due to turned off GPS so it can't get my location and set sunrise and sunset times?
asassello said:
Quick questions:
1. Does that AdAway work well?
2. Does automatic dark mode work for you? I have to turn it on manually. Maybe due to turned off GPS so it can't get my location and set sunrise and sunset times?
Click to expand...
Click to collapse
1 : yes
2 : yes..update maybe your modem
re 1: yes2 (using it quite some time on various devices and it seems to do what I expect it should do, though some apps seem to bypass the 'normal' DNS resolution. OT: And I'm still haven't made up my mind yet if DoH or DoT are good or bad ...)
re 2: dark mode? What's that?
rayman95 said:
1 : yes
2 : yes..update maybe your modem
Click to expand...
Click to collapse
Are you sure NFC works? I mean paying in shops? I updated modem and now it's N9005XXUGPQB1. And paying still doesn't work. I've just tried.
odoll said:
re 2: dark mode? What's that?
Click to expand...
Click to collapse
Sorry. It's dark theme (I don't have English set as default language). [emoji846]
installation error
https://download.lineageos.org/hltetmo
Can somebody please confirm that paying through NFC works? If so - what's your modem and baseband?
Also I've installed GAPPS PICO maybe that's the case? Although on LOS 16 I also had Pico and it worked, but maybe I'm missing some app like Google search or something?
Been using Lineage OS 16 ever since it was officially released for HLTE. I gotta say, the development of that release has came a long way and by the time of writing this, I'd say it's the most stable and clean custom rom for the Note 3 out there.
I did try the new release the second I received a notification for an update. How did it go? Well let's just say I'm glad I created a full system backup before wiping LOS 16. This new release is still very buggy, unpolished and missing a lot of features. Nothing that will render your phone unusable, but compared to 16, it doesn't stand a chance, which is understandable.
I do appreciate all of the time that the devs are still willing to put into the platform. However I'd recommend users that are looking for a rock stable experience to stick with Lineage OS 16 for the time. You're not missing out on a lot.
loudseries said:
This new release is still very buggy, unpolished and missing a lot of features. Nothing that will render your phone unusable, but compared to 16, it doesn't stand a chance, which is understandable.
Click to expand...
Click to collapse
I think your statement will get more weight, when it will be supported with some facts:
It'd be helpful if you would underpin your statement with some of your findings about e.g. which bugs you found and which features you are missing!? thx
odoll said:
I think your statement will get more weight, when it will be supported with some facts:
It'd be helpful if you would underpin your statement with some of your findings about e.g. which bugs you found and which features you are missing!? thx
Click to expand...
Click to collapse
I have to agree with you, because except my 2 issues (with NFC payments and night mode that doesn't switch automatically) I actually don't have any other problems.
Ver. 17 seems faster and snappier than 16.
Also on 16 sometimes sharing from ie. Firefox to WhatsApp caused the later one not loading (just black screen).
So for me only that NFC seems to be a real issue. Other than that I'd advice anyone trying 17.
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
rayman95 said:
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
Click to expand...
Click to collapse
for me the only difference is the size of the home screen changed (changed trebuchet to a larger grid before), otherwise i would not even have noticed it is not 16 anymore, rock stable even after a dirty flash
rayman95 said:
made a clean flash with nanodroid and last lolz..the rom is mostly usable ..
got sometimes, not often some little freezes and stock music stop..otherwise it's reliable
both options, stay on 16.0 for stability or move to 17.1 are possible...
Click to expand...
Click to collapse
Yea,i have the same issue . Sometimes works okey and sometimes phone is just unresponsive, freezing. Youtube vanced most of the time stuck while screen is turned off ect.
Some really weird stuff there but I'm sure all will be okej later on.
Btw what BL and CP u using?
Scorpionea said:
Yea,i have the same issue . Sometimes works okey and sometimes phone is just unresponsive, freezing. Youtube vanced most of the time stuck while screen is turned off ect. Some really weird stuff there but I'm sure all will be okej later on.
Btw what BL and CP u using?
Click to expand...
Click to collapse
I'm on PQB1 nordic modem and BRL1 bootloader.
rayman95 said:
I'm on PQB1 nordic modem and BRL1 bootloader.
Click to expand...
Click to collapse
Have the same as you . I thought it could be bootloader issue but guess not.
Thx
Dirt update and no more freezes issues...I don't know if it's a the new rom or the dirt update... Anyway, but now got dl issues..browser fc when I want to dl a file...
odoll said:
Can we continue to discuss topics about the new - big thx to devs, btw! - official 17.1 version in this thread, pls?
(I know the differences to the unofficial version(s) might be minimal - or even null? - however I think it's always of value to be as clear, sharp and crisp avoiding ambiguities, esp. for folks who are not too familiar with the different contexts)
BTW: just for the record my (dirty) upgrade path from lineage-16.0-20201003-nightly-hlte-signed.zip version to lineage-17.1-20201010-nightly-hlte-signed.zip was as follows:
DLed / copied off my NAS the files of lineage-17.1-20201010-nightly-hlte-signed.zip, open_gapps-arm-10.0-nano-20201010.zip and Magisk v20.4 to external SD)
Let the system DL and install recent pending updates
Rebooted into Recovery (twrp-3.4.0-1-hlte)
Created a nandroid backup of Boot, System, Data and EFS partition to internal SD (and copied those to the external SD, plus a further copy to my NAS)
Wiped Dalvik / ART Cache, System and Cache partition
Installed LOS and GApps
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Rebooted into Recovery
Installed Magisk
Wiped Dalvik / ART Cache
Rebooted into System
(Enabled systemless host file in Magisk to support Adaway Adblocker app)
PS: This thread has been moved off the Development Folder by a Forum Moderator
Click to expand...
Click to collapse
Hello. I have the latest version of LineageOS 16 installed and TWRP (3.3.1.0). I ask you if, after transferring the ROM file to the phone, it is possible to use TWRP to upgrade to 17.1 (by installing the zip file) or if I have to use ADB shell (as it says on the LineageOS official site).
Sorry I'm not an expert and some steps are not clear to me
Thank you
PS
Why you wrote "dirty"
(Dirty) Rebooted into System letting the system run a couple of minutes, checking for updates etc.
Hi Apten
i) think your Qs won't need a full quote
ii) drity flashing
iii) sure you can DL the ROM (and TWRP) to your (internal RAM) of your phone and upgrade or clean install from recovery (twrp)
rayman95 said:
Dirt update and no more freezes issues...I don't know if it's a the new rom or the dirt update... Anyway, but now got dl issues..browser fc when I want to dl a file...
Click to expand...
Click to collapse
I've just dirty updated from 1010 to 1017 build . Will see how it goes later on.
Just tested with chrome downloading lineage and no issue with Fc