Related
I have the 0.7 rom load with both patchs and the blue theme, I want to try out apps 2 SD i just didnt know the best route in doing so, for it to work correctly with your rom. If i use the format function in the recovery menue would it automatically save my apps on the SD and work properly or would i have to reinstall them?
BAttitude7689 said:
I have the 0.7 rom load with both patchs and the blue theme, I want to try out apps 2 SD i just didnt know the best route in doing so, for it to work correctly with your rom. If i use the format function in the recovery menue would it automatically save my apps on the SD and work properly or would i have to reinstall them?
Click to expand...
Click to collapse
(I personally don't like apps2sd but if you really have that many apps...)
Yea. Backup your sd card (it will get wiped). Boot in to recovery and create swap+ext2+fat32 and then convert ext2 to ext3 (all are options in the recovery menu). It will move everything for you.
Why don't you like apps 2 sd? I just figure if you have that you won't have worry about internal memory if you wanted to have a lot o
PHP:
f apps
This is why he doesn't like it:
flipzmode said:
**My note about Apps2SD: I added support for it in this release of the rom because people who were using it in other roms that tried to install this rom were receiving errors. Here's my point of view on it.
I played with it for over 8 hours today between implementing it and then testing it to make sure this fix would work. I have personally come to not like apps2sd, but I am including it for those who use it.
The reason I don't like it is because it puts your phone at a huge risk of having problems once anything goes wrong. If you install a program that causes issues, a nandroid backup will not resolve the issue because the application is installed on your SD card not your phone. If your phone starts going crazy as reported here and here, then even just a restore possibly won't fix it. You might need to go as far as to wipe your SD card too. If you are lucky enough to have a restore fix your problems you will still need to reinstall every app, even if you didn't wipe your card. And on top of that when you try to reinstall any app it will think it's still installed, even though you restored your phone. But when you click "uninstall" it will just freeze half the time because there's nothing on the phone for it to actually install. I have also read many threads that say if you happen to boot the phone up without the SD card in then it will screw everything up.
So now maybe you are wondering why I would add Apps2SD support in this rom. In order for people who are currently using Apps2SD to upgrade to this rom I must support it or require them to do a hard reset before coming to fresh. Clearly I don't want you to have to reset so I have supported it. With that said: I personally recommend not using it. This rom will auto-use it if your SD card is formatted for it (fat32+ext2+swap partitions) but it won't use it if you are only partitioned as 1 fat32. My suggestion is to stick to the 1 partition and let your applications install on the phone. Linux is not like Windows in the sense that it will run the same whether you phone has 140 megs free of storage space or 10 megs free. So unless you plan on installing 100 apps, I don't see the practical purposes of using Apps2SD. But a lot of people like it.
Now with all of THAT said -- this rom officially has and supports Apps2SD. It is a program that I think has the possibility of being great, but has to work within the confines of the phone which means tricking Android in to thinking that the applications are installed on the phone when they aren't. That is what leads to all the problems mentioned above.
Click to expand...
Click to collapse
If i have apps2sd already from the previous rom i don't have to re-do it for the new one correct?
no you dont.
using apps2sd2 problems
I followed all the instructions here http://forum.xda-developers.com/showthread.php?p=5618439#post5618439 for apps2sd2 yet when I open the app, it STILL says Oops, you have to run through the tutorial to set it up. I've DONE THIS. I'm extermely frustrated. I have no idea what more to do. My sd card is partitioned correctly. I've run all the commands listed in that tutorial. PLS HELP! Also all my apps are showing in /system/sd/app AND data/app. Is this correct? Why won't Apps2sd2 work for me? I really need some troubleshooting help.
I have a rooted CMDA HTC Hero using the Fresh ROM. Also is there a way to still get Sprint TV using this ROM?
Fresh .7 doesn't support A2SD, only Fresh 1.0 & 1.1.
Before I do the OTA update would you all recommend skipping it and going for the hacked ROMs? I will be working on this tonight.
Woot, EXCITED
Also what is the best 8-16g SD card to get? Does it matter?
Thanks
WantADroid said:
Before I do the OTA update would you all recommend skipping it and going for the hacked ROMs? I will be working on this tonight.
Woot, EXCITED
Also what is the best 8-16g SD card to get? Does it matter?
Thanks
Click to expand...
Click to collapse
My vote would be to start with the modding... I have my first ROM flashed before I was out the door at sears.
A for the SD Card, there are several different choices; some prefer one brand over the other. I don't think I use mine as extensively as others. The higher the class (class 2,6,10) the faster the read/writes are supposed to be. I just recently picked up a 16gb Class 10 from Fry's for $32. Couldn't pass that deal up even though I didn't really need it.
Good luck!
Having just flashed mine from Stock 3389 + Enhancement Pack to TNT 3.1.3, I can tell you that there isn't a ton of difference between the two. I do like CWM and the ability to back everything up, but the Stock 3389 delivered very similar performance and Quadrant scores compared to TNT 3.1.3, in that when browsing, I can't really tell any difference at all.
It really wasn't very hard to flash a custom ROM. Just follow the directions from the one thread that talks about CWM, TNT, and Flash/Market fix, and just substitute the ROM of your choice. It's likely that you won't have to do the Flash fix either.
Enjoy!
Thanks
Thanks for the replies!
In order to use the custom ROMs I need an SD card correct? Is there anything in the new update that screws up using the custom ROMs?
WantADroid said:
Thanks for the replies!
In order to use the custom ROMs I need an SD card correct? Is there anything in the new update that screws up using the custom ROMs?
Click to expand...
Click to collapse
Technically no... you can boot up and drop what you need on the internal SD and run from there. It's good to have a MicroSD on hand as you can run recovery/command directly from there if you'd like. It's also recommended to keep recovery files and a rom (stock) on the MicroSD in case of a boo boo, it allows you to boot to recovery and re run it.
Remember that in the recover folder there is a command file. That file is telling the tab where to look, either SDCARD (built in) or SDCARD2(microSD). That command is WIPED every time its run weather successful or not. Therefore it's a good idea to have a pc nearby in case you need to replace it.
Also, depending on where you are running it from make sure the command is pointing to where you are wanting to go SDCARD (built in) or SDCARD2(microSD). Some grab a stock recovery folder from here (which tells it to look locally) then put the ROM on the MicroSD and nothing happens.
Again, IMHO Clockwork is the way to go. I personally drop all ROMS in the internal SD and play from there. Boot into recovery (Clockwork) and tell it to install the flavor of the day.
UPDATE: This can't be used with CM10 Alpha 4 (or later) as it is due to the new partitioning system.
____
I made this thing time ago and I thought to share.
What it does is to boot a stock ROM from the external SD card. It's nothing special, I simply changed few things here and there. I did it because I needed a stock ROM for a couple of minutes and this was the faster way to get it.
I'm using CM and I made this with that in mind, so, don't use while using a stock ROM. It won't mess your current setup, but it won't work.
You need to change kernel to boot the stock ROM (reboot recovery > flash zip. Simple and fast). That's because, as you probably now, kernels made for stock ROMs are not compatible with CM.
Prepare you SD card
You need first to repartition your external SD like this:
Code:
1° partition (mmcblk1p1): FAT - it will be the usual external SD
2° partition (mmcblk1p2): ext4 - /system (make it around 300MB big, 254MB will be more or less the space used)
3° partition (mmcblk1p3): ext4 - /data
I can't help you with this, I did it with adb and parted (the command is available in CWM). Look for instructions on the web, it's full of guides out there. Your external SD card is /dev/block/mmcblk1 (mmcblk0 is the internal one).
If you'll use the zip linked to flash the ROM, the two partitions (mmcblk1p2 and mmcblk1p3) will be automatically converted, unless they are already two ext4/ext3/ext2 partitions.
It shouldn't matter which kernel you are currently using and it should be safe flashing it, the only important thing is to have three partitions. If mmcblk1p2 or mmcblk1p3 are not detected, the installation will be aborted (it means that your SD card is not partitioned). Nothing else will be touched.
If you don't want to use the zip, mount mmbclk1p2 and copy the ROM there.
/dbdata will be the usual one (it's not used in CM. This will also makes Samsung apps a lot faster when using a slow SD card), same for /cache.
The flashable ROM is a stock XXLE4 + su/Superuser.apk.
How to use the additional ROM
To use the ROM on your SD, flash kernel-stock-SD.zip (see below) from recovery.
To go back to the real ROM you have to flash its kernel. Here below you can find CM10 Alpha 2 kernel, flashable from recovery. If you have doubts, reflash the entire ROM, it won't wipe your data.
I only mentioned CM10 because it's what I'm using, but this thing should work with CM9 too.
Things to know
I built the kernel using the latest Samsung sources with inbuilt ext4 support (and ext3/ext2 compatibility). Nothing else was changes, so I think there's no need to publish the sources, they are available here.
I attached the tools I use to unpack/repack boot images (they are a modified version of skin1980's tools):
Code:
./unpack.pl boot.img
./repack.sh [gz|lzma|bzip2|xz]
To see the changes I made, compare "out/android" with the stock XXLE4 ramdisk and the other two directories with CM10 boot.img ramdisk.
I changed recovery.fstab accordingly, but I can't tell you if flashing stuff from CWM while using the additional ROM will work as expected. You should read the updater-script to know it for sure.
I can only tell you that dhiru's builds will be flashed into the real /system partition and not your SD card.
Backups should work too, but I didn't try.
Of course, performances depends on your SD card. Mine is not that good I think, I took it from an old phone and I really don't know anything about it. The ROM is still usable, but apps that intensely use databases are slow (not Samsung apps, those will use /dbdata). Maybe disabling journaling will help (search for more info).
The Galaxy SL screen will last more than usual because I intentionally added a delay (3 seconds, SD cards are detected after a while) and of course because of the slower load.
Please, use this if you have some experience.
Note: dual booting two ROMs with a single kernel is possible, but only if they use the same kernel image. See this and this.
Downloads
XXLE4-CWM.zip: CWM flashable ROM
kernel-stock-SD.zip: kernel to boot the ROM from the external SD, flashable from recovery
kernel-CM10-Alpha2.zip: CM10 Alpha 2 kernel, flashable from recovery
Wow ! thats dualboot for i9003 ! sweet gud to see development back in action
Good work.
The class of an SD card can be misleading. It is only a measure of the sequential Write access and that doesn't tell the whole story. Class 10 cards are great for cameras and applications that write or read sequential data, such as saving a picture and transferring a file. They are not so good for random access which is what the Android OS does when operating. In fact the random access speed for class 10 cards is lower than class 4 or 6 cards. From what I have seen, the sweet spot for smartphones is class 6.
Awesome. Only if we could achieve dual boot without flashing kernel everytime. But anyways awesome guide. Thanks.
Reminded me of dual booting of maemo and android on my brother's n900.
Whats the benefits of dual boot? I heard about it but i dont have an idea
juztinlee said:
Whats the benefits of dual boot? I heard about it but i dont have an idea
Click to expand...
Click to collapse
Dual Booting means you can have two OS's (here firmware) on the phone at the same time. You can choose on which you want to go. This, besides being awesomely cool, is really helpful in many scenarios.
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
santoshsadani009 said:
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
Click to expand...
Click to collapse
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
loSconosciuto said:
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
Click to expand...
Click to collapse
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
Ya a Universal kernel will do the trick.If later then we can achieve dual boot then the people who were holding back from CM9 or CM10 can flash that for features and a stock rom for stability and camera.
shriomman said:
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
Click to expand...
Click to collapse
As long as the kernel is the same, yes.
If you want, here you can find the unpacked boot.img I (probably) used to dual boot CM10 and CM9 (SD).
There's no zImage in there, use the one you prefer, CM10 and CM9 are using the same kernel.
EDIT:
I almost forgot. "out/ramdisk/2ndROM" is for the ROM stored in your SD card, so you have to adjust the mount points there (already done in the one linked). "out/ramdisk/android" should be the "stock" ramdisk.
recovery will work only for the primary ROM in this case, maybe with some scripting you can make it works for both the ROMs, but I won't do it (if it's something possible).
The tools I posted will automatically take care of the additional ramdisk.
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
nick0016 said:
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
Click to expand...
Click to collapse
I don't know what happened to the links, probably I deleted the files by mistake on dev-host. Sadly I no longer have them and I currently don't have the time to make them again.
Anyway, I suggest you to follow other guides in order to replace only the corrupted memory instead (we have two different memories). This one for example, but there are other guides probably.
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
nick0016 said:
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
Click to expand...
Click to collapse
The guide I linked is fine then.
It explains how to repartition your SD card and the script Dipu K attached to his post is to use the newly created partition inside your external SD for /data. It's not to swap internal and external SD.
As I said, we have two memories, /data is in one, /system, kernel and other things are in the other memory. The corrupted one must be the one which holds /data.
Try to do as explained in the guide, if the problem persists, I'll see what I can do to help.
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
nick0016 said:
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
Click to expand...
Click to collapse
The content of /data is generated, there's nothing like what you asking for.
Maybe the problem is that the script posted in the guide copies the content of the old /data partition to the new partition inside the SD card. Wiping data shouldn't work because the path to the SD card is not specified.
Try the script attached. I zipped it to be able to upload it here, but it's not flashable. Since you've been able to follow the guide I assume you know how to use adb.
Wipe the content of the data partition you created inside you SD card (/dev/block/mmcblk1p2). You could reformat it with make_ext4fs, use a computer and so on. What's important is that it's ext4 formatted.
While in recovery, run:
Code:
adb shell mount /system
adb shell mkdir -p /system/etc/init.d/
adb push [I]PATH_TO[/I]/remount_data /system/etc/init.d/
adb shell chmod 777 /system/etc/init.d/remount_data
I'm sorry, but I currently don't have much free time to help more than this. With no logs or access to the device it's really hard for me to know what's the problem.
Ok I got a HTC Sensation (XE) with ARHD 7.2 flashed on it. Kernel:Faux something
My problem my android crashed the 2nd time now. By that I mean, I can not access my SD card, all apps downloaded force close as soon as I open them, gallery (pics, vids etc) all empty but Android is showing me that the SD card has files on it and also accessible on the pc.
Read on the internet, a factory reset might help so I did and it worked...for a few weeks then again same thing happened.
Question is, is it the ROM that's causing this or the Kernel (which afaik faux is fast but unstable), maybe the extra features I selected when flashing are incompatible with the phone, or my SD card is dying?
any help appreciated
Anti_simlock said:
Ok I got a HTC Sensation (XE) with ARHD 7.2 flashed on it. Kernel:Faux something
My problem my android crashed the 2nd time now. By that I mean, I can not access my SD card, all apps downloaded force close as soon as I open them, gallery (pics, vids etc) all empty but Android is showing me that the SD card has files on it and also accessible on the pc.
Read on the internet, a factory reset might help so I did and it worked...for a few weeks then again same thing happened.
Question is, is it the ROM that's causing this or the Kernel (which afaik faux is fast but unstable), maybe the extra features I selected when flashing are incompatible with the phone, or my SD card is dying?
any help appreciated
Click to expand...
Click to collapse
Its the kernel,try a different one,one thats a little more stable,this one obviously has bugs or is'nt compatible with your rom,also try this thread,it might help you a little.... http://forum.xda-developers.com/showthread.php?t=1466228
To determine wether this is the ROM or not I would personally go back to stock for a period of time and see if the same problem is persistent.
From what you have said it does sound like a bug, possible unstable software.
But attempt reverting back to stock as this may be hardware based with the XE being a older generation handset now.
Hope this helps
Attention developers!!!
I have an idea of a concept where the A/B slots could be used to boot 2 different ROMs simultaneously one on Slot A and another on slot B using another data partition. Is it possible?
Feel free to discuss in this thread.
It would work, but we only have one data partiton. You have to split it (like on the mi a1 I think?)
I have found a good method for dual-booting, but some roms don't work and there is only 1 data partition.
I have lots of ideas ???
Can we not split the single data partition into two separate partitions for data?
shaunakdsilva said:
Can we not split the single data partition into two separate partitions for data?
Click to expand...
Click to collapse
Well then storage for each partition will decrease and it may be a issue for installing apps and other data am i right?
Aduser345 said:
Well then storage for each partition will decrease and it may be a issue for installing apps and other data am i right?
Click to expand...
Click to collapse
You can use one slot for daily driver rom with a bigger data partition size and use the other spot for experimental rom with a smaller data partition size. How many of us really use the entire 64gb or 128gb storage for data?
shaunakdsilva said:
You can use one slot for daily driver rom with a bigger data partition size and use the other spot for experimental rom with a smaller data partition size. How many of us really use the entire 64gb or 128gb storage for data?
Click to expand...
Click to collapse
Hmmm.....but what about that encrypted storage thing??
Won't it interefere with booting the rom?
And would our device be able to handle rom switching?
I mean im not that an expert but atleast what i hav heard about the boot.img being incompatible with both the roms is it possible to dual boot???? I really want a custom rom and oos pie in my device???
Aduser345 said:
Hmmm.....but what about that encrypted storage thing??
Won't it interefere with booting the rom?
And would our device be able to handle rom switching?
Click to expand...
Click to collapse
Only a developer would be able to answer those questions. As far as i know, anything is possible!
Anyway, we can use twrp as dual boot manager?
core7x said:
Anyway, we can use twrp as dual boot manager?
Click to expand...
Click to collapse
TWRP offers to switch the slot which is how i got the idea that probably we could have two ROMs installed and switch the slot from TWRP as and when required.
Aduser345 said:
Hmmm.....but what about that encrypted storage thing??
Won't it interefere with booting the rom?
And would our device be able to handle rom switching?
I mean im not that an expert but atleast what i hav heard about the boot.img being incompatible with both the roms is it possible to dual boot???? I really want a custom rom and oos pie in my device???
Click to expand...
Click to collapse
In order to make things simpler, decrypted data partition would be a pre requirement.
Encryption is not really useful for most people and a possible issue doing this kind of manipulation to actually make some sense out of (otherwise useless) A/B partition scheme
This idea would probably be slow and a lot of overhead (i.e. wasted battery) but you could theoretically create a writable disk image and then have the ROM dynamically mount that in the data location. No idea how it would work or if it would work.
Otherwise, you could always look into chroot or something like that. Just throwing ideas out, I have no development capability.
can i install pie on one slot and if for whatever reason do not like can i go back to the other slot? rooted as well? thank u!
Smartest op ever
maybe a possibility?
Ive used "DualBootpatcher" on many devices in the past. I don't know if it works on a/b devices like the op6.
Let me know if it does, and if it bricks your device.
Https://forum.xda-developers.com/cr...ualboot-dualbootpatcher-simpler-dual-t3297414
Looks like it works on the op5!:
https://forum.xda-developers.com/oneplus-5/development/patcher-dualboot-multiboot-oneplus-5-t3633150
And the 5t is officially supported!
Https://dbp.noobdev.io/supported_devices.html
Maybe somebody can reach out to the developer
Neil_Armstrong_ said:
Smartest op ever
Click to expand...
Click to collapse
I can't really figure if that is sarcasm... could you explain how it's so smart?
Yeah I'd love to dual boot my op6, I'm really missing it because I used it on my Nexus 5x and it was really useful, we should all reach out to the devs of multiboot or dual boot patcher or someone could port it, that'd be amazing
Anything is possible, the issue how much development would be required. My guess here is the answer is "so much that no one is going to bother."
There's nothing special about A/B. It's just duplicated partitions, a system for flagging which set is active, and using the arrangement for seamless updates. It's not designed for dual boot because both slots are intended to use the same data partition. So at the very least you'd need some function to split or otherwise change how the data partition is used. Given that much of this is baked into core Android, I suspect that hacking it for dual boot would be both unstable and a risk of brickage. Past tools for non-A/B phones are most certainly not going to work here.
https://www.google.com/amp/s/forum.xda-developers.com/pixel/help/dual-booting-t3507924/amp/