yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] yfriday14:
I could save many Gb, if the system.img could be around 300-400 Mb, and not 2600 Mb.

[MENTION=4277844]chenxiaolong[/MENTION]: what is the reason of using so big system.img size?
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
I told you once, 2760 Mb is the size of your device's real system partition. So, any ROM installed to an extsd-slot will a system image of the exact same size. It is set that way otherwise ROMs and mods will have issues while flashing. Chen explained it once. If I remember right, there's nothing he can do.

If you have good amount of storage remaining in your internal storage, you can install a ROM into the data slots
[Galaxy S 4 i9505 Original Android Development] turbopas:
choice at boot...

I would like to know if there is a possibility to choose the ROM to boot...

Thanks.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
You mean while booting? Chen is working on such a feature. See a few posts above.
[Galaxy S 4 i9505 Original Android Development] turbopas:
Thanks...
[Galaxy S 4 i9505 Original Android Development] carandcar:
Can someone tell me what may cause this error when switching to my secondary ROM?

"The SHA512 checksums for this ROM's boot.img or other *.img files in /sdcard/MultiBoot/dual/ do not match the expected checksums. A third party app may have maliciously changed these images. Proceed with switching the ROM?"
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
This error is shown when the checksums don't match (as it says). Like when you (or some app) change the boot.img in that given directory not through the app. It's a security measure, I think. But I get this error usually when I've updated the ramdisk of that ROM. And it switches to and boots that ROM without any issues. So, maybe it's a bug? [MENTION=4277844]chenxiaolong[/MENTION] Is it a bug?
[Galaxy S 4 i9505 Original Android Development] carandcar:
Thank you. It does seem to happen after I update the ramdisk.
[Galaxy S 4 i9505 Original Android Development] giovan797:
stopped developing the project? will not have more updates ? You have to have the bug fix sim ?

thank you to have answers ... thanks ..
[Galaxy S 4 i9505 Original Android Development] youlun.zhai12:
Does anyone figure me out how to port this great patcher to other devices? What I need to do to the source code?
[Galaxy S 4 i9505 Original Android Development] midi_1996:
I dont really know but i think you need to wait for Chen to suddenly appear again in the forums and he'll be asking you for some information about your device, he'll later add support to it, if possible.
[Galaxy S 4 i9505 Original Android Development] sronweb:
The developer has never stopped but he has as everyone a private life, school etc. So it's not necessary to push or ask for updates.
[Galaxy S 4 i9505 Original Android Development] yfriday14:
Because of some os bootloops and Titanium Backup restore hang issues (Samsung Galaxy S4 i9505), I got recommendation to start rom flashing from beginning, by flashing original os using Odin, root again, then install Resurrection Remix v5.7.0 again.

However, I have 1 primary and 4 external sdcard os flashed, and I would not want to lose them:

http://xdaforums.com/showthread.php?p=67489771

Is there any new method implemented to make backups of installed roms separately?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
Yes there is a method, you will have to search back in the thread. The OP explains how to backup any of the roms installed and also how to backup to external SD as well.
[Galaxy S 4 i9505 Original Android Development] yfriday14:
Yes, I know about that backup method, but I'm waiting for the backup feature to be implemented into Dual Boot Patcher by [MENTION=4277844]chenxiaolong[/MENTION].
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
A little over two months later, we finally have a new release! 8.0.0.r2545.g631bbff brings one new feature and just one: the Boot UI.

What is the Boot UI?

The Boot UI is a boot menu that allows choosing which ROM to boot. It's a little similar to GRUB and rEFInd on PCs. During boot, you can wait for the 5-second countdown to boot into the last used ROM or select another ROM to boot. It's based on a heavily modified version of TWRP's graphics code and the default TWRP theme, so there's no doubt it will look very familiar. (Any ideas for a custom theme are welcome!) Unlike TWRP, the same build of Boot UI can run on any supported device, like the rest of DualBootPatcher.

How do I use it?

First of all, the Boot UI is completely optional (and always will be). To install it, simply go to the DualBootPatcher settings and tap "Install Boot UI". Then, update the ramdisk for every ROM. The ramdisk update is absolutely necessary since otherwise, the device won't know that the Boot UI should run during boot.

Which devices are supported?

Currently, only the Snapdragon Galaxy S4 (jflte/jgedlte) and Moto G (2013) (falcon) are supported because those are my two test devices. Adding Boot UI support for a device is harder than adding general DualBootPatcher support because it needs to directly interact with the GPU's framebuffer, which is done very differently across devices. To add Boot UI support for your device, please:

Ensure that TWRP officially supports the device (not a custom build)

Send me a link to the TWRP thread here on XDA (and the link to the device tree source code, if known)

Be ready to help me with a bit a testing :)

Screenshots
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, it's a bug! The ramdisk update process modifies the boot.img, but doesn't update the checksums. I'll fix this ASAP :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Haha, I was just enjoying my freedom while I still could after my graduation. Starting tomorrow, I will be working full-time at my new job :D
[Galaxy S 4 i9505 Original Android Development] Eliminater:
[MENTION=4277844]chenxiaolong[/MENTION]

How likely is it will support OnePlus 3 ?

I love this app, and I hope you make it!

Thx for all your efforts
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Lol you're BACK man!! Believe me or not, but I was checking the snapshot page every single day looking for a new version. :D Glad to see you around bro!! :highfive:

Edit: I saw you're hired and starting a new job? Cheers. If it's not a secret can you tell us what would you work?
[Galaxy S 4 i9505 Original Android Development] tomaasz:
[MENTION=4277844]chenxiaolong[/MENTION]

Thanks for your come back with new staff :)

I would like to request about support for:

- Samsung Galaxy S5 SM-G900F (klte)

- official webside of TWRP for Samsung Galaxy S5 Qualcomm

- XDA [RECOVERY][klte] TWRP 3.0.2-0 touch recovery

BR!
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
I just tested the latest version of Dbp on a Samsung s4 i9505.Stock based rom,with minor modifications. While trying to acces patch zip file,I got a crash.I attached zip below.Please check it out.Apparently,resources are missing

..
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Cool feature, but my phone isn't officially supported by TWRP. That's really disappointing. :( I think you need the source, right?

Will phones without official TWRP ever be supported?

Thanks.
[Galaxy S 4 i9505 Original Android Development] Rebel021:
Can somebody point me to a guide or a post that shows how to get this working on a Note4 international Snapdragon SM-N910F.

I have searched and tried a few guides but keep getting error 01
[Galaxy S 4 i9505 Original Android Development] hankching:
[MENTION=4277844]chenxiaolong[/MENTION]

Thanks for your come back.

I tried using Lenovo K3 note (codename:k50) setting for Jiayu S3. It works, so I created files based k50 setting which you can quickly support it. I also provide files from getlogs to you checking.

About Boot UI

Here is TWRP app. I hope following information can help you support MTK CPU.

http://www.needrom.com/download/twrp-3-0-2-2-5/

Basic source code:

https://github.com/lj50036/platform_manifest_twrp_omni/commits/twrp-6.0

Source code variant 3.0.2-2:

https://github.com/IcemanDev/Twrp-3.0.2-2-Umi-X3/blob/master/README.md
[Galaxy S 4 i9505 Original Android Development] giovan797:
I thought it had stopped development, thought it was a working team of developers, but thank you and waiting for updates as availability ...

---------- Post added at 01:51 PM ---------- Previous post was at 01:46 PM ----------

I thought it had stopped development, thought it was a working team of developers, but thank you and waiting for updates as availability ...
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Please try out the test build here and let me know how it goes: https://github.com/chenxiaolong/DualBootPatcher/pull/104

I won't be able to make further changes until I'm back from my business trip on Wednesday, so my fingers are crossed that this test build works. :)
[Galaxy S 4 i9505 Original Android Development] JoshDaWhite:
Check the previous page ...Cannot patch zip files .Log attached in my previous post .
[Galaxy S 4 i9505 Original Android Development] yfriday14:
Do you installed your rom to external sdcard, or to primary or other internal sdcard.

Just because my roms installed to primary are up within minutes.

Just roms installed to external sdcard takes forever...
[Galaxy S 4 i9505 Original Android Development] tomaasz:
"Failed to install Boot UI"

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Galaxy S 4 i9505 Original Android Development] yfriday14:
[MENTION=4277844]chenxiaolong[/MENTION]: in r2561, in wipe pop up dialog, text & dialog background are both white, while using the dark mode. This results, that text is not readable.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Two extsd-slots. I told you once. Ask Chen. It should be a bug. My extsd-slot ROMs at the same speed
[Galaxy S 4 i9505 Original Android Development] fishersfish:
Hi, Chen ! I am enjoying your Patcher on my Oneplus 2 ( A2001 ) .

Recently, oneplus get a newer firmware (based on Marshmallow ,the previous is based on Lollipop ). And the latest CM / AOSP-CAF based ROMs and the latest TWRP recovery are relying on the Marshmallow firmware. But your Multi-Boot Utilities is incompatible with the latest TWRP recovery (3.0.2.1), when I switch the roms, it says:

[D] ro.product.device = OnePlus2

...

[D] Attempting to switch to data-slot-xxxx

...

[E] /dev/block/platform/f9824900.sdhci/byname/boot: Failed to write image:No such file or directory.

It cannot find boot partition! I've found the real path in the newest TWRP recovery:

/dev/block/platform/soc.0/f9824900.sdhci/byname/boot

[MENTION=4277844]chenxiaolong[/MENTION] Can you add an alternative boot path to your Utility for OnePlus2 ? Thanks A LOT !
[Galaxy S 4 i9505 Original Android Development] skezza:
Does it still boot okay in a TW ROM, if I use adoptable storage for my CM13 ROM?
[Galaxy S 4 i9505 Original Android Development] skezza:
Tried adoptable storage. Can't recommend it tbh. Seems to slow the phone down a bit and just doesn't seem to work nicely.

Stick to portable storage imo.
[Galaxy S 4 i9505 Original Android Development] vitaly51370:
chenxiaolong, please do not pass by: http://xdaforums.com/showpost.php?p=67333614&postcount=9358
[Galaxy S 4 i9505 Original Android Development] yfriday14:
It seems, it is fixed in r2561.

Sent from Samsung Galaxy S4 i9505 using Tapatalk

---------- Post added at 11:38 PM ---------- Previous post was at 11:36 PM ----------

Dual Boot Patcher crashes in MIUI V5 with this error, when touching the big plus sign (file selector):

android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.OPEN_DOCUMENT cat=[android.intent.category.OPENABLE] typ=*/* (has extras) }

at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:1632)

at android.app.Instrumentation.execStartActivity(Instrumentation.java:1541)

at android.app.Activity.startActivityFromFragment(Activity.java:3957)

at android.app.Fragment.startActivityForResult(Fragment.java:1079)

at android.app.Fragment.startActivityForResult(Fragment.java:1063)

at com.github.chenxiaolong.dualbootpatcher.switcher.ZipFlashingFragment$1.onClick(ZipFlashingFragment.java:190)

at android.view.View.performClick(View.java:4445)

at android.view.View$PerformClick.run(View.java:18446)

at android.os.Handler.handleCallback(Handler.java:733)

at android.os.Handler.dispatchMessage(Handler.java:95)

at android.os.Looper.loop(Looper.java:136)

at android.app.ActivityThread.main(ActivityThread.java:5139)

at java.lang.reflect.Method.invokeNative(Native Method)

at java.lang.reflect.Method.invoke(Method.java:515)

at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:796)

at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:612)

at dalvik.system.NativeStart.main(Native Method)

Sent from Samsung Galaxy S4 i9505 using Tapatalk
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Hi chen!

Here is the twrp but right now im using the twrp 3.

But on xda i found this:

http://xdaforums.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129

This is 2.8.2.0 twrp. Its important having different versions of twrp or should be the same???

I forgot xD my device is LG G3 D855
[Galaxy S 4 i9505 Original Android Development] fishersfish:
[MENTION=4277844]chenxiaolong[/MENTION] , I thought you ignored my incompatible issue. And You must be kidding, I don't think my issue need logs.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I didn't ignore it. I just don't have the time every day to work on the patcher. (For example, if I even visit XDA during work hours, I might lose the right to work on this project due to company policy.)

Anyway, this is now fixed in 8.0.0.r2592.g3523d6e :)

Yeah, I don't need logs for simple fixes like this, but thanks for providing them anyway!
[Galaxy S 4 i9505 Original Android Development] fishersfish:
I am sorry for not believing you ,after all, it's only your leisure work, we cann't ask too much! Thanks for your great work! [MENTION=4277844]chenxiaolong[/MENTION] :)

uh....Bad news, when switching roms in TWRP 3.0.2.1 ,it says the same:

[E] /dev/block/platform/f9824900.sdhci/by-name/boot:

Failed to write image: No such file or directory

Missing: sdc.0/

Wait for fix for Oneplus 2 ...patiently...

:)
[Galaxy S 4 i9505 Original Android Development] Technical:
[MENTION=4277844]chenxiaolong[/MENTION],

Is it possible to implement a sort feature into the sharing app list? Data shared / Data non shared / System apps ?

Or, at least, a visual indication in red/green if the data is shared or not?

Scrolling the list all the times to check for new installed app is quite time consuming...

I suppose you do not implement a "select all" app for security reasons.

Maybe a way that will help us a lot would be a blacklist to share all the other apps (i.e., the non-blacklisted).

Thanks.
[Galaxy S 4 i9505 Original Android Development] AM.8:
I can't set the kernel :/ what can i do??

Thanks

Gesendet von meinem SM-G935F mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] ewangw:
Chenxiaolong,

Definitely appreciating all the good things you're doing with DBP. Here is the link for TWRP 3.0.2 for the Moto X Pure (2015).

http://xdaforums.com/moto-x-style/orig-development/recovery-twrp-2-8-7-0-touch-recovery-t3200520

Also,

Quick question on setting up a ROM on External SD. Not sure if this has been addressed in your most recent updates, but on my Moto X I can install the system.img to the external sd, but the GApps always fails since it claims there is no room left in the System Partition. I will try the most recent version of DBP later today and see if it still occurs. If so, I will capture some logs.

Thanks
[Galaxy S 4 i9505 Original Android Development] AM.8:
Anyone have a solution please:/

Gesendet von meinem SM-G935F mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] hankching:
Did you update Ramdisk? Try it first.
[Galaxy S 4 i9505 Original Android Development] AM.8:
:/

Gesendet von meinem SM-G935F mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] hankching:
Upload Ramdisk-update. log to check the error.
[Galaxy S 4 i9505 Original Android Development] AM.8:
Ramdisk-update.log:

https://mega.nz/#!GdUwiSZZ!q7eMKNp6axI3fe1RXpikFGUUytbFzBvAy_fxQ0JQ58E

Gesendet von meinem SM-G935F mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] hankching:
Error is the app did not backup boot. img.

Which means no free space or backup function incorrrct.
[Galaxy S 4 i9505 Original Android Development] AM.8:
Any solution mate??

Gesendet von meinem SM-G935F mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] hankching:
Delete unnecessary files.

When I update Ramdisk is OK. That meand your os hss incompatible issue.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Which zip file? Do you mean the DBUtilities?? Please clarify. :)
[Galaxy S 4 i9505 Original Android Development] fmotta:
Welcome back Chen and all the best for your job.

Thanks for adding OnePlus 3 but I'm still facing with the impossibility of selecting any zip file for patching.

Whenever I select a zip the program shows its content instead of opening the patch window.

Also I have no external programs available to search zip in left column like I remember I had with my old OnePlus.

Cheers

Inviato dal mio ONEPLUS A3003 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Anybody?

How can I completely remove everything related DBP? Not for me, but for someone else.
[Galaxy S 4 i9505 Original Android Development] hi_blues:
This is how I remove DBP

1. In app manager open up DBP settings clear data/cache. And uninstall.

2. From internal storage and external storage delete Multiboot folder.

3. With root explorer delete Multiboot folder from

/data

/cache

/system

4. Delete corresponding snapshot.xxx.xxx.xxx folder from root/data/data if you find it.

That's pretty much it. I hope not missed anything.

Thanks
[Galaxy S 4 i9505 Original Android Development] Eliminater:
The problem ist on the stock data app not on the patcher at this point, but i got patched a rom to data and I have bootloops to the recovery.
[Galaxy S 4 i9505 Original Android Development] hankching:
You can try this feature if your phone is lenovo K3 Note.:silly::laugh:
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Fixed in 8.0.0.r2607.g82420a9. It was a separate issue causing the same error. I did add the "soc.0" path to the list, but the code for switching in TWRP was choosing the first path in the list instead of the path that actually exists.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
There are other bugs (unrelated to this particular one) that currently prevents DualBootPatcher from working on the S7 Flat/Edge. I don't recommend trying it right now.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Could you post your build.prop file here? I'll just have to blacklist the ROM like I did for the OnePlus 2 so it falls back to another file chooser. I'm not sure why they still haven't fixed this bug yet.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yep, this might actually work because your device's hardware is very similar to [MENTION=7320148]hankching[/MENTION]'s :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the link! I'll get started on that. Unfortunately, your device uses the Qualcomm overlay for rendering the TWRP interface, which is a huge pain in the rear end because of incompatibility across devices.

As for the GApps issue, a link to the logs would be great. I'm not sure I'll be able to fake the disk space information to the installer, but I might be able to have the patcher remove the check.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2610.g56b9f45 should hopefully fix this :)
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
WTH? What do you mean? Does it work for you? Doesn't work for me.

WTH??!? I was talking about the Boot UI feature, not *dualbooting*. I was the one who helped you fix the bugs my phone was having, remember? The crappy updater-script coding, closed sourced and all.

P.S.: Or did I get all wrong? :o I did :mad:

Just saw this: https://github.com/chenxiaolong/DualBootPatcher/commit/75e7be90dcfa4ce1e023fd1df6bf3ea2edc055f1.

But it fails for me.

Another thing, Chen. After I click Install Boot UI (which fails), I cannot close the app by pressing the back button, then I've to close it from recent apps. Is it bug?
[Galaxy S 4 i9505 Original Android Development] Eliminater:
Oneplus3

Nope I can now choice a third party data manager but wen i try to choice the zip I root again in it.. I try two different data Manger.
[Galaxy S 4 i9505 Original Android Development] rkrohan:
[MENTION=4277844]chenxiaolong[/MENTION] Thanks for adding support for oneplus 3. But now all the users are getting a problem. After updating ramdisk and rebooting, the phone reboots to recovery and dosen't boot to the rom even if we try to boot from recovery. And if eventually by switching rom location to /data, the phone dosen't boot the rom
[Galaxy S 4 i9505 Original Android Development] hankching:
The same CPU MT6752. If it fail for you, that your phone is bad!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Your device is Jiayu S3, right? And how is this my phone's problem? Is your phone also having unofficial TWRP?
[Galaxy S 4 i9505 Original Android Development] AM.8:
Thats mean that i can't use it right now ?? :/

Gesendet von meinem SM-G935F mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] AM.8:
---------- Post added at 09:09 AM ---------- Previous post was at 09:01 AM ----------

[/COLOR]

Thats mean that i can't use it right now ?? :/

Gesendet von meinem SM-G935F mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] hankching:
Yes. Jiayu S3.

I find Lenovo K3 note has TWRP 3.0 by IceMan which is OK and it is the same as Boot UI.

Therefore, your phone should work. If it does not work, probably your phone has other problem. You can try using TWRP 3.0 by IceMan, for testing to ensure compatibility, even it works, I don't know its original version. So, forget it!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Can the link to this IceMan TWRP?
[Galaxy S 4 i9505 Original Android Development] fishersfish:
Thanks !! I've tried the latest version, and it works perfect now! :good:
[Galaxy S 4 i9505 Original Android Development] fmotta:
I can choose third party apps too but I have force exit from Dualboot app when selecting any zip file to patch.
[Galaxy S 4 i9505 Original Android Development] vitaly51370:
chenxiaolong, can you explain why you can not add support LG G3s (D724)?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah okay, can you try again with 8.0.0.r2611.g1c5bd58 and send me the log in /sdcard/MultiBoot/boot-ui-install.log?

Also, I can't seem to reproduce the back button error. If I change the code and force it to fail, my back button still works fine.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Alright, I just received some logs from https://github.com/chenxiaolong/DualBootPatcher/issues/124. The issue is caused by the device being encrypted. I completely forgot that new devices must be encrypted by default.

For now, your only option is to decrypt the device if you want to dual boot (and that entails the need to format /data). I'm currently working on supporting encryption, but I don't know how long it will be until I finish. If you want to undo the ramdisk update, just flash /sdcard/MultiBoot/primary/boot.img.before-ramdisk-update.img from TWRP.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I don't think that's the issue. He hasn't been able to install the Boot UI yet because the installation fails for some reason.
[Galaxy S 4 i9505 Original Android Development] rkrohan:
So if I remove encryption, the data slot will work?