yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Eleo:
Yup. I may try to get rid of some of them. I dont use all of the installed.apps. Some of the apps are there for "just in case I need them" :fingers-crossed: (I mean I have 8 camera apps and more than 10 image editing apps and I don't take photos at all, that is how just in case apps I have :silly: )

I want to try some AOSP ROMs too. Pretty sure will miss most of the TW functions but eager to meet nougat too.

I am trying to add a new partition by the pc apps you told. They will be invisible to pc but I would be able to use them in smartphone. Now, I know that only system images of extsd slot are in extsd card. If I divide extsd to two partitions: media (music+series and titanium backups) and system (for dual boot), can I move the apps and system images to system partition of sd? Or should I have different partitions for app files and system images?
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
OK. Maybe going from 161 to 72 could be the issue. Lol
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
This is pretty nice idea, but unfortunately it won't work that way. The reason is usually Android is not mounting the 2nd partition (your ext4 partition) with the small exception of some custom roms like cm13 or aicp, rr also. This partition is mounted with a script that the Apps2sd app is executing. I suggest to keep the ext4 partition only for moving apps and data. Choose size around 6-8GB. Then the other primary partition will be with size 51-53GB with plenty of space for your files and your multiboot setup. This will be the partition mounted in Android by default.

---------- Post added at 13:49 ---------- Previous post was at 13:46 ----------

You know that r161 is not the latest build. r72 is far than perfect when we talk for TW roms.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Ok. Now I got it. I was checking some FS on minitool partition wizard. But first time I checked I forgot to label any partition as primary so it wasnt recognized. I have fat32, fat, nfts and ext4 choices. So I should have a primary with fat32 (because primary with nfts is not recognized by PC and most probably will not be recognized by android too) and a logical one with ext4 (or this should be primary too?). I have 50GB fat32 primary and 9GB ext4 logical. Is it right?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Sounds good, but the ext4 must be also primary. This is important.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Just downloaded 9.1. Would it be OK to delete the old dbp and install new one? Will there be any issues?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
No worries, uninstalling the patcher won't delete the installed roms or their data. I usually just install the new build over the previous.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
OK. Tyvm. I been doing that too. I thought maybe that was the reason I was having issues
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Ok, seems all 9.1.0 builds starting from r0 are having issues with infinite "verifying zip". Just tried all of them. You can bypass this installing the zip in recovery.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
I have to flash SuperSU to tems rom...do I patch su also?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yup, you should patch every zip you're installing to make sure it would be flashed to the correct slot.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
OK. What if I just install it via play after ROM boots?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Nothing. It will work. We talk about you have for example primary and data slot roms. You can't just flash supersu right away, you must patch it for the corresponding rom.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Yea. I know I have to patch su. It's just that when I patched it to the ROM/slot, I lost root. And device was wonky. Lol. Thanks again.

---------- Post added at 02:04 PM ---------- Previous post was at 01:58 PM ----------

Ugh. Keep getting error code 200
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] I found it! At least the problem with the infinite verifying zip is localized! Tried many builds and build 9.0.0.r158 is fine while the issue starts with the next 9.0.0.r159. All builds newer than r159 are verifying zip forever. The zip is patched with the latest 9.1.0.r23.

Edit: Added log for r158 build where the verifying works fine.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Dude...ur on top of everything! Good job!

---------- Post added at 04:39 PM ---------- Previous post was at 04:35 PM ----------

So, you went and wiped primary and flashed rom normally? Couldn't you have wiped primary and rebooted and made the second rom primary?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Oh come on my friend! I'm just having free time today. :fingers-crossed:
[Galaxy S 4 i9505 Original Android Development] Eleo:
I didnt have primary. I wiped that long time ago. I had only exsd slot 2. Then I flashed another TW ROM to extsd slot 1 (still no primary, just two extsd slot ROMs). After that I tried to change fs of extsd (forgot that botb of my ROMs are in extsd) and couldnt boot into any extsd slots after autoreboot. I just flashed a rom zip (not patched one) via recovery and now have only one ROM. As soon as I get to move my apps (and files) to extsd I will flash one TW and one AOSP ROMs.

Thanks for guidance :good: (sorry, ran out of thanks today :o)
[Galaxy S 4 i9505 Original Android Development] andyfmking:
I'm also experiencing the obb folder problem when I install an app from play store that has an obb file. The playstore crashes. So I can't install Asphalt Xtreme :crying:

I found a way to manually move the files by accessing the obb folder through /raw/data/media... But this isn't useful if I don't already have the obb file downloaded in the phone.

I already did RamDisk update but still having the problem.

Anyone knows how to fix this?

I'm on OP3 Resurrection Remix 5.7.4 with playstore version 7.0.18H and Dual Boot Patcher 9.0.0.r71
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
Master can i have your guide on multirom install in extcard slot? So far i just try in data slot in internal storage and would like to know more on external storage. Thx.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Have you tried latest playstore and latest dualboot patcher app?

P.S. Dont mind the name "multiboot patcher". It is the same dual boot patcher apk (I just changed its name by using flipster module so that an icon could be applied)
[Galaxy S 4 i9505 Original Android Development] andyfmking:
Let me try to update those two apps then I'll report back.

I'm assuming with these versions you don't have the same problem when installing apps with obb files from the playstore.
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
Can i have link on this build 9.0.0.r158?

I need to try for the verify zip section to see if it same result. Thx.
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
The backup was successful but the in-app flashing can't find any backup to restore. Any idea? Note 4, v9.1.0.r13.

Update: problem solved after reset backup folder. I promised I set it right and it was backed up to that folder. Weird but glad I figured it out.

Sent from my N910P PH4 on Aurora v4.1 Rom, Ram Kernel v3
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Oh, so you're expecting a guide for installing a rom to the external card? Hey, it's not so hard. You really don't have to do anything special.

---------- Post added at 21:07 ---------- Previous post was at 21:04 ----------

https://jenkins.noobdev.io/job/Dual...tcher-builder && fast,target=android-all-gcc/
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Anyone know why when I flash patched SuperSU zip I get probs? It will hang on reboot. Sometimes I have to battery pull...and I get SuperSU saying not currently available for system root. Sounds to me like I'm getting systemless root. Ugh!

---------- Post added at 09:20 PM ---------- Previous post was at 09:19 PM ----------

This

---------- Post added at 09:22 PM ---------- Previous post was at 09:20 PM ----------
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
This
[Galaxy S 4 i9505 Original Android Development] rifle007:
[MENTION=4277844]chenxiaolong[/MENTION] can you make support to redmi 3S (land) . I attached log here and thanks..
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Anyone have a T-Mobile note 3...and if so, what dbp works best? Thanks.
[Galaxy S 4 i9505 Original Android Development] Eagle:
There is no "best" in anything. You'll have to find one which works fine for your device.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I suggest using SuperSU SystemMode

http://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120

---------- Post added at 09:17 ---------- Previous post was at 09:16 ----------

Until the verifying is fixed use the r158 build.

---------- Post added at 09:25 ---------- Previous post was at 09:17 ----------

You can backup only system and Multiboot files if you wish. If a problem occurs there is a high chance the phone will reboot to recovery on it's own. You don't need a backup to restore the boot.img for the last working rom. Go to twrp, install image-> navigate to /sdcard/Multiboot/xxx selecting the boot.img for the Rom you want to boot and flash it as boot from the options. Of course you can switch to other rom with the DualBoot Utilities also.
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Um...yea there is...since this app is broad in many devices, this is a legitimate question. :)
[Galaxy S 4 i9505 Original Android Development] Eagle:
Well, you've been asking silly questions through private message so I could not figure out whether this question of yours was a 'legitimate' one. ;)
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
[/QUOTE]

You can backup only system and Multiboot files if you wish. If a problem occurs there is a high chance the phone will reboot to recovery on it's own. You don't need a backup to restore the boot.img for the last working rom. Go to twrp, install image-> navigate to /sdcard/Multiboot/xxx selecting the boot.img for the Rom you want to boot and flash it as boot from the options. Of course you can switch to other rom with the DualBoot Utilities also.[/QUOTE]

Can i know how is the dualboot utilities is working? Do we need flash it after we install the dbp for any usage? For me i just use the patcher and left my utilities. Let say if I accidentally wipe internal storage and no more multiboot file in my storage can I restore it back ? And in wipe rom section we need to wipe system data cache multi config as well as too? Or it's have optional on it?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
You're flashing the zip in recovery and as it's Aroma installer based you can select the desired options with the volume and power keys. You must have at least two roms installed with the patcher otherwise I don't see why you'll want to use it. If you wipe the internal you'll also wipe the multiboot setup assuming the rom is not in extsd. The rom in extsd will be intact, but as the Multiboot folder in /sdcard was deleted your only option is to extract the boot.img for the rom from it's patched zip, and flashing it in recovery. You can leave the multiboot config alone when wiping a rom, it will keep the rom name and the assigned image. I found that if I don't delete the multiboot config the rom is wiped, but it's still showing in the roms list in the patcher, may be because the folder in /raw/data/multiboot/xx is present, even being empty.
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
Just have try backup data slot1 the system, multiboot config to be restore in my primary slot. What I eventually disappointed is some of the features is not working on the rom when I go back to primary rom. So it should be a need on data when you are in restore section. Have try wipe with multifiles and it doesnt give me see the primary slot again. I wipe system cache

Multifile and remain the data to be there. Is that a necessary to wipe data too? For other things can I try backup the primary and restore to the extcardslot1 that I havent try ? It will be interesting if I can do so. So far I just try in internal but not external . It should be my test later after clear with it.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Just wanted to share the results after app2sd pro and link2sd plus apps (previously I had 6.6GB app data on phone storage; but now both system data and app data use 6.7GB only; have more apps to move too though). Just one question though. What is difference between "moving app to sd" and "linking app to sd"? Some apps were not posssible to move to sd (android webview, SNote, Theme Store and etc) but were possible to link to sd. And I also observed that when app is moved to sd it is moved to fat32 partition but when it is linked to sd it is linked to ext4 partition (from the icons on the sizes of moved objects). So should I move apps back to phone storage and link them to sd or is it ok and I should not bother with it?

Still only on primary ROM and havent yet flashed any ROM on external. Want to make sure everything is alright before flashing any other ROM.

EDIT: Nevermind, got my answer from Link2sd FAQ ;)
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
158 is good and that su worked. Thanks again
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
How bout this:

Since you have primary rom on it. Try flash a simple rom in extsd slot1 with no extra apps on it. Run dbp. Set kernel. Backup your primary Rom . Then wipe your extslot rom . Restore the primary rom into your extcard slot1. Then you might have to know if it's something wrong with the storage issues.
[Galaxy S 4 i9505 Original Android Development] Eleo:
I dont have anything wrong with storage issues. You didn't understand my question.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Yes. I know her from other threads too :rolleyes:
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Silly question....is it advisable to set kernel in the ROM you're on before flashing a new ROM or changing Roms? Thanks.
[Galaxy S 4 i9505 Original Android Development] :
Thread cleaned

Can we keep it on track and knock off the drama before it gets out of hand please

Regards

Sawdoctor
[Galaxy S 4 i9505 Original Android Development] Eleo:
I think you set kernel when you are installing dual boot patch app the first time, i.e. in your one and only primary ROM. It is required to get the kernel of the ROM that was not installed by patched kernel zip. If you are on a ROM which was installed with a patched ROM/kernel zip I think you don't need to set kernel. But if it is the ROM that was flashed with non-patched ROM/kernel zip, then you need to set kernel so that you can come back to this ROM if you will need it. And yes, not only english, but also manners it seems.

Cheers
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
It wouldn't hurt though, right?
[Galaxy S 4 i9505 Original Android Development] Eleo:
You may try, it would probably say kernel is set if it was patched kernel zip. It should not hurt from my experience
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Ur right. Thanks again.
[Galaxy S 4 i9505 Original Android Development] shadowcliffs:
I have several non-stock roms installed on primary and data slot. Now I need to Odin flash a stock tar to update baseband. What I should do to restore systems after this? Should I do a TWRP backup, or dual boot is able to do the job as well with it's backup/restore feature? I'm thinking of install dual boot to the stock Rom then start to restore from dual boot backups from there. Will it work? Thanks.

Sent from my N910P PH4 on Aurora v4.1 Rom, Ram Kernel v3
[Galaxy S 4 i9505 Original Android Development] monkteo:
Guys I have a smole problem, please scuse me if this was already discussed but really I didn't find it.

I manage to install 4 roms on my phone (S7E)(for testing)

1.primary , and second on data slot and 2 other in exsd one nougat and one N7Port and I don't see my exsd on this 2 rom installed on exsd.

It's something to do to fix that, I mean to see my exsd from one of my rom installed on exsd ?

THX and sorry
[Galaxy S 4 i9505 Original Android Development] Tmobilefan906:
Flashing update won't hurt anything. Just don't flash the entire tar file. Only flash the bp
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The verifying zips issue with in-app flashing has been resolved in 9.1.0.r27.g65be81a. The fix was much more complicated than I originally thought due to the fact that there's no way to read a zip file reliably with the standard Java libraries when using the Android Storage Framework. (And the storage framework is needed to read from the external SD or USB OTG drive without root.)

Technical details at: https://github.com/chenxiaolong/DualBootPatcher/commit/3f97a3e18be9eb3d0363578e4c24eb7c7fa267c8
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, it seems like the shut down clears the kernel logs. I'm not sure how else I can debug this.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you try again with 9.1.0.r30.g2664a29 and attach /sdcard/MultiBoot.log if it still fails?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=5048731]911-Future_Maker[/MENTION] Holy cow, you win the award for most number of dualbooted ROMs! That is crazy :D
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Unfortunately, there's no way for me to change this behavior because it's part of Android, not the app, but you can tap and hold the file and choose "Open".
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sorry, I forgot I haven't merged the helium changes yet. The new test build at https://github.com/chenxiaolong/DualBootPatcher/pull/315 should work for you now!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Are you using adoptable storage by any chance? (or some other ROM feature to save files to the SD card?)

It looks like files the app writes are being sent to the SD card (eg. /storage/F8EF-CBFE/MultiBoot/primary/boot.img) and it no longer finds them where it expects them (eg. /sdcard/MultiBoot/primary/boot.img).
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Please give the test build here a try: https://github.com/chenxiaolong/DualBootPatcher/pull/321
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If it contains boot.img.p, it will not work. To apply the patches (the .p files), the original file must be unchanged.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This can sometimes happen if you're dualbooting 2 different versions of Android. Can you try running the following command either via adb or with a Terminal Emulator app and then reboot?

su -c 'restorecon -RFv /data/media/obb'
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for all the testing! This should be fixed in 9.1.0.r27.g65be81a and newer. The bug was related to how the zip file was being read, which changed when I added support for flashing files from the external SD and USB-OTG drives.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Unfortunately, due to some kernel security features in the newer versions of TouchWiz, that is currently broken. I don't know if it's possible to work around this without a custom kernel.
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
[MENTION=4277844]chenxiaolong[/MENTION]

I know in app flashing is experiential but I do have a question. On the lg g5 tmobile, once I install dual boot and set kernel I'm able to flash in app without any problems. Once I update the ramdisk on primary and reboot I am no longer able to use in app flashing, it always fails (and this is happening for others on T-Mobile version as well). Flashing from twrp works, just wondering if it would be possible for you to look into this. Thank you, I've included the log file as well.

And again thanks for all the work you've done on this.
[Galaxy S 4 i9505 Original Android Development] monkteo:
But I have a custom kernel.

This is the kernel patch it and

this is what I patch and install.

THX
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs!

It looks like this will require a bit of debugging. Would you mind doing the following for me?

Undo the ramdisk update by flashing /sdcard/MultiBoot/primary/boot.img.before-ramdisk-update.img from TWRP

Using adb or a Terminal Emulator app, run the following command:

mount > /sdcard/pre-mounts.txt

Redo the ramdisk update

Run the following command:

mount > /sdcard/post-mounts.txt

and then send me the 4 files:

/sdcard/MultiBoot/primary/boot.img

/sdcard/MultiBoot/primary/boot.img.before-ramdisk-update.img

/sdcard/pre-mounts.txt

/sdcard/post-mounts.txt

Thanks!
[Galaxy S 4 i9505 Original Android Development] whymoo:
It works! Thank you, do you need a log?

It even some how seems to have made T-Mobile VoLTE work on stock ROM.
[Galaxy S 4 i9505 Original Android Development] jeffsga88:
[MENTION=4277844]chenxiaolong[/MENTION]

Yeah, no problem. I noticed that after doing ramdisk update the boot.img is 0 bytes, so not sure if that will help. I uploaded both in a .zip file to another website:

http://s000.tinyupload.com/index.php?file_id=17298273011369054682

I've included the log files in this post. If you need any more logs or me to test anything else just let me know.
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
Chenxiaolong how do we suppose to run multirom in extsdcard? Is it the same method with internal storage?

Any thing I need to caution when doing it? I hope I am doing the right way after your support.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Ok, that's why it doesn't work, thanks for clearing that out. :)
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Someone is having issues with the latest SuperSu SR5 SystemMode? The rom was stuck in boot loop, after I flashed the SR4 it booted fine.

---------- Post added at 12:07 ---------- Previous post was at 12:05 ----------

Patch the rom to extsd-slot. Install it. Boot it. That's it.

---------- Post added at 12:09 ---------- Previous post was at 12:07 ----------

Thanks! Where is my medal please? :p [MENTION=4277844]chenxiaolong[/MENTION] Periodically I have issues related to SuperSu versions that are giving me bootloop on various roms. When I change to an older or just different version the rom boots fine. I'm curious why is this happening.
[Galaxy S 4 i9505 Original Android Development] Yumiko87:
thx for reply . another question. if i want to flash to extsd-slot is it essential to divide the partition ?

or is might be encourage to do so ? as i not so familiar with that part. i hope i can doing it without divide as i have most of my files in sd card.

i afraid if divide partition i need to remove all the files in sd card before i can do so . its need me to have a free time to do so .
[Galaxy S 4 i9505 Original Android Development] kopitalk:
Working well here, on data-slot TW 6.0.1 rom. Sometimes it would stuck and a manual reboot is required.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
No, no additional action required.

---------- Post added at 12:18 ---------- Previous post was at 12:15 ----------

It's strange. It's happening not only with this SR5, but with random versions too. I found myself flashing some other supersu.zip and then it works.
[Galaxy S 4 i9505 Original Android Development] monkteo:
maybe this helps regarding exsd problems

THX