yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] mixmoto:
Hi! [MENTION=4277844]chenxiaolong[/MENTION] I'm writing here to use this good thing on xiaomi mi 4. Dual boot patcher work's very well on rom's like MIUI or pre marshmallow roms but if I try to install a newer ROM like nougat I have baseband err.. I add log and SS of error. Thank you for your good work!
[Galaxy S 4 i9505 Original Android Development] Rambooka:
Hi all.... Dual boot patcher's inbuilt rom installer worked well on my s7 running Android 6.0.1 tw roms.. .. Now I am on 7.0 tw rom the inbuilt rom installing fails... here is log
[Galaxy S 4 i9505 Original Android Development] Eleo:
Could this be your issue? Though there are many more errors in the log
[Galaxy S 4 i9505 Original Android Development] jcrompton:
May be a question that has been asked and answered ..... But when you made reference to the setenforce commands are you able to get Safety net to pass on secondary ROMs or are you just referring to primary??

Thanks

PS if by some miracle you are successful on secondary can you please explain how
[Galaxy S 4 i9505 Original Android Development] Filip013:
No, sorry. I don't think that can be done.
[Galaxy S 4 i9505 Original Android Development] gaww:
Have many others have installed on ExtSD and have had the ROM not see the ExtSd after that? I am trying to determine if it is DuleBoot or a problem with only the ROm (BobCat 7.0).

Any feedback would be helpful.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Nope. I had two ROMs in extsd and both of them, including primary ROM could see extsd.
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
I have 3 ROMs on my T800, 2 are on ExtSD. All ROMs see & use the Extsd just fine.
[Galaxy S 4 i9505 Original Android Development] zaiyiera:
I've tried Resurrection Remix on ExtSD, but sadly it didn't boot :(

Running LineageOS Official (Primary) and LineageOS Unofficial OMS (Secondary) without problems at all.
[Galaxy S 4 i9505 Original Android Development] gaww:
So looks like a problem with my sd or the patched rom.

Another question - have you been able to back up the ExtSD system partition (assuming data is included in twrp backup)?
[Galaxy S 4 i9505 Original Android Development] Eleo:
You can backup every ROM on multiboot from dualboot patcher apk. It may take up to 10GB space
[Galaxy S 4 i9505 Original Android Development] gaww:
I did so for all roms and data except for the EXTSD rom system with twrp. Tried to do that with the app, which is 1 rom at a time and it fails.
[Galaxy S 4 i9505 Original Android Development] Eleo:
You cant backup multiboot by twrp. Logs?
[Galaxy S 4 i9505 Original Android Development] gaww:
You can back up everything in system, data, and cache partitions which includes everything but the ExtSD rom.

Note - I just did that to data rom ok.

So I am only having issues with extsd. Going to try different sd and possibly back it up and reformat it and restore with the backup.
[Galaxy S 4 i9505 Original Android Development] Dnorris55:
I've never been able to backup the system partition of ROMs on my extsd.
[Galaxy S 4 i9505 Original Android Development] Eleo:
What about your logs? Your system img is stored on extsd but everything else is still on internal memory. Have this on mind
[Galaxy S 4 i9505 Original Android Development] webmaster33:
I also had problems with ROMS flashed to external sdcard. They doesn't boot.

It is a bug in Dual Boot Patcher.

Chenxiaolong is working on the fix.
[Galaxy S 4 i9505 Original Android Development] Eleo:
You cant even boot to extsd slots?:eek:
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Nope. Neither one.

This bug is specific to those mobiles, where fstab has multiple entries for external sdcard.

Currently only the first dev path is readed, then if doesn't mount, then 5 vibrations & reboot to recovery.

Not sure tough, if fstab.qcom is the original one, or created by Dual Boot Patcher.
[Galaxy S 4 i9505 Original Android Development] gaww:
Some roms are apparently not compatible, but most likely for patching at all and not only on ExtSD. I patched Echoe, it said completed successfully but on flashing, it would not boot up on data partition or ExtSD. For now it is primary and a stock ROM is running on a data slot Ok and Bobcat was running OK - but couldn't use the External SD.

I have reformatted that, and am copying back all the files - hope it will see it now - lol.

Update - no luck. If anyone has successfully installed this as a Data partition ROM on duelboot and it can use ExtSD, please post how you installed it. it works good overall but for that situation.
[Galaxy S 4 i9505 Original Android Development] monkteo:
External dualboot working perfect ( maybe your make something wrong)
[Galaxy S 4 i9505 Original Android Development] webmaster33:
I wrote the case:
[Galaxy S 4 i9505 Original Android Development] gaww:
Wish I had read the above early today - spent all day rebuilding my setup - total waste of time.

Other than the OP of that ROM restructuring his ROM differently (highly unlikely) - is there anything that can be done with respect to the fstab situation?
[Galaxy S 4 i9505 Original Android Development] himuslg123:
im having same devxie same primary rom installed ..but when ever i try to flash the patched RR cm based rom 5.7.4 ..im getting a error called "this devcie is noblelte"

how can i fix this
[Galaxy S 4 i9505 Original Android Development] monkteo:
[MENTION=8008957]webmaster33[/MENTION] I am shore that you are right but I show that dualboot it's working on exsd for users who try one's and make smole mistakes and instead to read just post "it's a bug"

I hope you understand me.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
I think we have to wait for fix.

Chenxiaolong is close to fix it, so I think it will be done within maximum a week.

I suffer from this problem since 3-4 months, so waiting a bit more, can be acceptable ☺

---------- Post added at 09:23 AM ---------- Previous post was at 09:20 AM ----------

I described clearly which case is affected by the bug.
[Galaxy S 4 i9505 Original Android Development] :
Thread cleaned up.

Please stay on topic and avoid off topic discussions. This is a development thread and hence staying on relevant topic will be more than appreciated.

Also, please keep your personal disputes to PM, don't take it out in public forums.

And if you find something annoying, either report it or add the user to your ignore list and move on. Kindly don't reply to it.

Not everyone has the same view as yours, keep that in mind.

Regards

Vatsal,

Forum Moderator.
[Galaxy S 4 i9505 Original Android Development] dancekid:
Hello Community,

i tried to install Dual Boot Patcher inside xXx No Limits 6.0 as Primary Rom.

I get some error messages "not enough space" and was unable to boot or select primary in tools using recovery (error message: not enough space).

anybody tried successfully to use Dual Book Patcher with xXx No Limits ?

greetings Dance.
[Galaxy S 4 i9505 Original Android Development] monkteo:
What phone model and what partition you try to dualboot (secondary - data slot - exsd ?)
[Galaxy S 4 i9505 Original Android Development] dancekid:
using S5 KLTE

I installed APK file, clicked "Install Boot UI" and tried to update Ramdisk (failed). rebooted and was stuck at bootscreen. recovery tools failed to select primary.

next planned step was installing CM13 .... atm no other rom installed or tried to install.

System: 158 MB / 2,4 GB free

Cache: 192 MB / 200 MB free

Data 5,7 GB / 11,8 free

Reinstalled primary rom, installed APK and tried to update Ramdisk but failed. Logfile attached.

Now restarted phone and got stuck on bootscreen with "Samsung Galaxy S5" before starting Bootanimation.

dualbootpatcher crashes my bootimage at the moment. will dirtyflash xXx rom again to get phone working again.
[Galaxy S 4 i9505 Original Android Development] SubwayChamp:
You have two options in this point;

1. Edit build prop in the line that say "ro.product.line=" and put like it is in your build prop, compare with notepad both, specifically in this line, or..

2. At moment to patch choose the file and change the option in DBP of your device i9500 for noblelte-note 5.

Note:If is really this rom a ported from noblelte take care before flash cause this is LTE and yours is exynos non LTE, maybe was correctly ported but just be carefull
[Galaxy S 4 i9505 Original Android Development] gaww:
Yes you did - apparently these posters didn't read it or didn't understand it.

Not a duelboot problem, although if Chen had a fix for roms with this issue it would be great.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
I miss the patching step from your list.

Did you patch the zip file before flashing?
[Galaxy S 4 i9505 Original Android Development] dancekid:
I never patched primary.

1) install primary

2) install apk

3) set kernel

4) update ramdisk failed

5) stuck on boot

I patch any additional rom but never patched primary. It worked without everytime i used slim or cm as primary and secondary.

This time i installed a TW rom as primary.

How much space to i need in System partition ? I will try to cleanup some with barebonecleaner
[Galaxy S 4 i9505 Original Android Development] himuslg123:
it worked mate.. thanks for your vaulable tips.. :laugh::good:
[Galaxy S 4 i9505 Original Android Development] dancekid:
hello community,

do i need to patch primary, too ? i never patched any CM Rom as Primary before installing. applying APK and updating ramdisk always worked.

My first installed TW Rom does not like to get an updated Ramdisk (fails to create).

dance
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Interesting question.

Currently I don't have my stock primary rom patched. But based on words of Chenxiaolong, I should.

Chenxiaolong wrote this:

https://github.com/chenxiaolong/DualBootPatcher/issues/270
[Galaxy S 4 i9505 Original Android Development] RomanSkyline:
Please guys, like this comment if someone want the support for the Xperia XZ, thanks

Enviado desde mi F8331 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] Eleo:
Really?! You know that to get support for your phone all you need to is to send the logs, right? Try reading thread or at least search to find out what you need to do:eek:

P.S. Asking for thanks is prohibited on xda for whatever reason you do it. FYI
[Galaxy S 4 i9505 Original Android Development] RomanSkyline:
Ooh! Sorry, thanks [emoji28]

Enviado desde mi F8331 mediante Tapatalk
[Galaxy S 4 i9505 Original Android Development] jinkerz9430:
hello. I have an LG V20 h918. I have a stock rom as my primary rom, and an aosp based rom as my secondary one. however... I cant manage to flash the gapps. I have flash both 7.0 and 7.1. And i have try reflashing it from the app (adding it to the same secondary slot, changing the slot too, also using the extrnal and the data slot) also i have tried by manually flashing it via TWRP with the secondary rom active and it still wont allow me.
[Galaxy S 4 i9505 Original Android Development] Eleo:
What does it show? Does it give an error? What kind of an error? Can you share logs please?
[Galaxy S 4 i9505 Original Android Development] jinkerz9430:
This is what i get

Error code:64
[Galaxy S 4 i9505 Original Android Development] Eleo:
Are you trying to flash 64bit to non 64-bit architecture?
[Galaxy S 4 i9505 Original Android Development] jinkerz9430:
Oh wait. I believe it is totally the opposite. I was flashing a non 64bit arch zip into a 64bit arch. Sorry. Now it is flashing correctly. The issue was that all my previous devices have been arm and not arm 64 so i kinda got stuck with using just arm. Thanks for reminding me that!
[Galaxy S 4 i9505 Original Android Development] Gravemoss42:
I see this is running on the lgv20 918 (T-Mobile). Any chance ya'll can get it working for vs995 (Verizon lgv20?) I loved this app on my note 4! I tried the T-Mobile version, but it won't even patch a ROM so I don't know if there is any data I can share that would help.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Get logs via getlogs zip and share the tarball
[Galaxy S 4 i9505 Original Android Development] Gravemoss42:
Ok, I'll see if I can figure that out today
[Galaxy S 4 i9505 Original Android Development] Eleo:
Read:

That was posted at least hundred times. A quick search on thread will reveal every detail.
[Galaxy S 4 i9505 Original Android Development] Gravemoss42:
ok here is the log from my verizon vs995, hope it helps. i couldnt even get the rom to patch, so i never got to the install portion .
[Galaxy S 4 i9505 Original Android Development] jthrasher47:
You need to post your logs in the original dual boot Patcher thread and the original Creator will add support.

Thanks [MENTION=4598795]Eleo[/MENTION] for answering all the questions lately
[Galaxy S 4 i9505 Original Android Development] Eleo:
No problem at all. You mean this thread? Which one is original thread?
[Galaxy S 4 i9505 Original Android Development] jthrasher47:
The one I have linked in the original post. [MENTION=4277844]chenxiaolong[/MENTION]'s thread. Or anyone needing support for their phone just post the get logs. Zip in his thread. And he will add support whenever he gets a chance
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Sorry everyone, I will continue to unavailable for the near future. I'm currently involved in a new project at work that is a very significant career goal for me, so I'm dedicating all my time and energy towards it. I'm not allowed to say any more than that, but it's why DualBootPatcher hasn't gotten much activity lately. Rest assured that the project is not dead!

In the little free time I had in the past few weeks, I made some pretty important changes to the core of the patcher. The most significant one is probably libmbbootimg, a new boot.img file parser. It is much more secure than the current code (in terms of handling malicious boot.ing files) and is somewhere around 600% faster. It will be noticeable when loading the list of ROMs, switching ROMs, updating the ramdisk, etc.

I know a lot of people have jumped in and submitted pull requests while I was gone. Thanks to everyone who has done so; it's much appreciated! I will be reviewing and merging those PRs ASAP.

And as usual, thanks to everyone in this thread for helping each other out!

Cheers,

Andrew
[Galaxy S 4 i9505 Original Android Development] gaww:
Good luck with new project - kick ass!
[Galaxy S 4 i9505 Original Android Development] jaysonic88:
Running into an issue on my LG V20 (H918). I've had several different ROMs installed and running great. I decided to do a refresh and delete them and start over. Well the ROMs flash but now i can't get GAPPS to install. It looks like it installs but when you get to the OS there's no apps--specifically the play store which i need. Suggestions?
[Galaxy S 4 i9505 Original Android Development] Antidote03:
Hello There

Guys did any one face this problem

when i want open DualBootPatcher-9.1.0.r158.gc2524036-win32 ( rom patcher for windows ) i see this

if any one have the dll file can you plz share it

thanks in advance
[Galaxy S 4 i9505 Original Android Development] gaww:
As Chen said some time ago, the windows patcher is totally dysfunctional. You have to use the app.
[Galaxy S 4 i9505 Original Android Development] haax:
Hello, what should I do when I want to flash rom with aroma that isn't supported? Should I delete something before flashing this rom in twrp or something?
[Galaxy S 4 i9505 Original Android Development] Eleo:
What is not suppported? Aroma? ROM? Recovery? Dualboot Patcher?
[Galaxy S 4 i9505 Original Android Development] haax:
DualBoot patcher I think, cause I've got this error log:
[Galaxy S 4 i9505 Original Android Development] Eleo:
You cant flash aroma-installer containing zip with dual boot patcher. It has to be in recovery. For twrp it should be not newer than twrp 2.8.7.0. Twrp3.x cannot use aroma-installer.
[Galaxy S 4 i9505 Original Android Development] haax:
Yeah sure, so my question is should I delete somehow DualBoot support before flashing aroma installer in my twrp or I can do it and I would just lose access to my other roms flashed as second or data slot?
[Galaxy S 4 i9505 Original Android Development] Eleo:
I still dont understand it.

1. Do you have a patched zip? You can flash it on recovery and it will not touch your other slots

2. You dont have patched zip file? Flashing unpatched zip fike will destroy multiboot environment.
[Galaxy S 4 i9505 Original Android Development] haax:
Ok, I think I know what you mean now, I have both patched and unpatched file, but I thought that when rom has aroma installer inbuilt, it can't be used with DualBoot overall, but it looks like it just can't be flashed through patcher app. I'll try flash it through twrp now, thanks!
[Galaxy S 4 i9505 Original Android Development] bam80:
out of RAM

Hi chenxiaolong, could you please point the commit where you solved it?

Having the same issue in MultiROM's TWRP..
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
Same here. I can only get into the third ROM right after flashing. I'm in hyper for my first one, PAC for the second, and gummy for the first multi slot. I'm on the third now, but I can't save it
[Galaxy S 4 i9505 Original Android Development] Bejda:
Did you "set current kernel as.." for all rom?

Edit:no forget,stupid thought.
[Galaxy S 4 i9505 Original Android Development] Shanks:
I guess the best we can do for now is wait for master chen to tell us how to switch to the 3rd rom,I just hope is something I'm missing
[Galaxy S 4 i9505 Original Android Development] lukemo:
Sorry but I can't find anymore the 11-8; Chen can you help us to patch the latest Ktoonsez 4.4.? Thanks in advance.
[Galaxy S 4 i9505 Original Android Development] chavdar:
No I cannot. The switcher app does not see the third rom, although it is there

Sent from the GT-I9505 Galaxy
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The ktoonsez 4.4 AOSP kernel should have no issues patching. Is the latest version not booting up or having some other issue?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'll look into missing ROM (in switcher app) issue tomorrow. I was finally able to reproduce it :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
New minor release (3.0.1) -- Changes:

Update SuperSU patch to support version 1.80

Switch to CyanogenMod 11's mkbootimg and unpackbootimg sources

Add support for Google Edition 4.4 ROMs (ie. stop trying to patch the missing MSM8960_lpm.rc in the ramdisk)

Hack to allow the file chooser in Android 4.4 Kit Kat to work properly (in the Android version of the patcher)
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
Dude, you are incredible! Never stopping lol
[Galaxy S 4 i9505 Original Android Development] UiK77:
Hi, not sure if this has been asked yet, but if I am in my primary ROM and want to do a Nandroid backup, well it backup the second ROM also?
[Galaxy S 4 i9505 Original Android Development] HearMeWhisper:
Yes, it will back up both Roms
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Version 2.0.1 of the Switcher app is now released :) This fixes the issue where the ROMs for triple/quadruple/quintuple boot aren't shown. It turned out to be a permission issue where the app can't access anything in /cache. The app will now request root access when it's started so it can get a proper list of installed ROMs.

Those who already have triple boot set up only need to update the app. No need to reinstall the ROMs.
[Galaxy S 4 i9505 Original Android Development] Shanks:
Thanks master chen, it's good to have people like you working on the s4, thanks again
[Galaxy S 4 i9505 Original Android Development] Shanks:
Everything is working now

Has anybody found a way to share apps and their data? That's the only thing left to make this project perfect
[Galaxy S 4 i9505 Original Android Development] nightranger73:
No issues at all. Ktoonsez said he only supports THIS KitKat ROM because he can't track changes made by each developer.

Other 4.4 had changes in ram disk and SD wasn't mounted and kt answered to everybody to use this rom

I have used it's latest kernel with no issues

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] blondbond:
Thanks Chen for your continued hard work. Im very greatful for all of your super skills helpung us achieve amazing things on our devices. Im having a little issue, Im still not able to access 3rd, 4th roms/slots etc.

Ive downloaded the new apk, am I missing something simple?

Thanks
[Galaxy S 4 i9505 Original Android Development] coolnessQ:
How do i format second rom? Without touching primary rom???
[Galaxy S 4 i9505 Original Android Development] chickentuna:
Flash Dualbootutilities. There should be an option on the aroma to wipe system/dual
[Galaxy S 4 i9505 Original Android Development] coolnessQ:
Yesss got the dualboot working ^^

Formatted my secondary rom, updated the apks and repatched probam rom and now it installed perfectly and it booted up without any problem ^^
[Galaxy S 4 i9505 Original Android Development] taxi333:
Thanks for fixing this!! i can see the third rom now. However when i reboot into the 3rd rom the phone gets stuck in the samsung boot logo. I'm guessing i need to clear cache/dalvik for the multislot rom #1. Anyway of adding this to dualbootutilities?
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Just posted an issue, how to build Dual Boot Patcher from source under Ubuntu Linux 16.04:

https://github.com/chenxiaolong/DualBootPatcher/issues/401

Just in case somebody wants to do it personally.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
It seems I located the problem.

If the 64GB external card is formatted to exFAT, then Dual Boot Patcher will not boot it.

If I format the external sdcard to FAT32, then it can boot correctly from external sdcard.

It seems there is a problem with the exFAT driver or kernel has no exFAT support compiled into.

Also posted to

https://github.com/chenxiaolong/DualBootPatcher/issues/375
[Galaxy S 4 i9505 Original Android Development] farshid7720:
dual boot patcher

dual boot patcher app dont work in galaxy A7 2016 ROM (failed to update mbtool. many operations such as switching ROMs will not work) :crying:
[Galaxy S 4 i9505 Original Android Development] Eleo:
That happened to me too once. I think you couldnt give root permissions. Check from su app
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Ported successfully..logs deleted
[Galaxy S 4 i9505 Original Android Development] paryav:
Sorry. What does its meens?

script aborted: gemini.verify_trustzone() failed to read current TZ version: 2

gemini.verify_trustzone() failed to read current TZ version: 2

Updater exited with status: 7
[Galaxy S 4 i9505 Original Android Development] add_pl:
I cant boot AICP from my data slot.

Anyone can review log?
[Galaxy S 4 i9505 Original Android Development] fmotta:
Hi [MENTION=5724618]chen.[/MENTION] Could you please add support to Xiaomi Mi Mix (lithium)?
[Galaxy S 4 i9505 Original Android Development] Eleo:
Get logs
[Galaxy S 4 i9505 Original Android Development] fmotta:
Here they are!
[Galaxy S 4 i9505 Original Android Development] paryav:
I found.

This is check firmware version.

For multiboot we need remove this string from updater-script file in zip installation. Next install updated Zip

assert(gemini.verify_trustzone("TZ.BF.4.0.1-77307") == "1");
[Galaxy S 4 i9505 Original Android Development] .Monkey:
Is there any way to clear up space on the system partition so that I can for the rom on it? Using an S7e if it helps.
[Galaxy S 4 i9505 Original Android Development] Eleo:
Use debloater script to remove unused "removable" system apps.

Or just dont use secondary slot, but data slot or extsd slot.
[Galaxy S 4 i9505 Original Android Development] webmaster33:
Would be possible to simply make app data sharing simply by creating hard or soft links of app data directory?

Not sure if this would work.