yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] razorj7:
Yes sir, here you are:

Detected IOKP ROM zip

--- Please wait. This may take a while ---

Extracting ramdiskTraceback (most recent call last):

File "/Users/jesselira/Downloads/DualBootPatcher-2.4.3/scripts/patchfile.py", line 559, in <module>

newfile = patch_zip(filename, fileinfo)

File "/Users/jesselira/Downloads/DualBootPatcher-2.4.3/scripts/patchfile.py", line 459, in patch_zip

new_boot_image = patch_boot_image(boot_image, file_info)

File "/Users/jesselira/Downloads/DualBootPatcher-2.4.3/scripts/patchfile.py", line 285, in patch_boot_image

extracted

File "/Users/jesselira/Downloads/DualBootPatcher-2.4.3/scripts/patchfile.py", line 199, in process_ramdisk_def

plugin.patch_ramdisk(directory)

File "/Users/jesselira/Downloads/DualBootPatcher-2.4.3/scripts/../ramdisks/jflte/AOSP/AOSP.py", line 98, in patch_ramdisk

modify_init_qcom_rc(directory)

File "/Users/jesselira/Downloads/DualBootPatcher-2.4.3/scripts/../ramdisks/jflte/AOSP/AOSP.py", line 64, in modify_init_qcom_rc

write(f, line)

File "/Users/jesselira/Downloads/DualBootPatcher-2.4.3/scripts/../ramdisks/jflte/AOSP/AOSP.py", line 8, in write

f.write(line.encode("UTF-8"))

UnicodeDecodeError: 'ascii' codec can't decode byte 0xc2 in position 5: ordinal not in range(128)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! It looks like somethings not working with Python 2 (but it works with Python 3). I'll get it fixed in a sec.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Version 1.5 is now released :)

This release fixes the Python 2 bug mentioned above and adds support for loki'd ROMs and kernels. This means custom kernels for AT&T and Verizon can now be patched and also pre-loki'd TouchWiz ROMs. Note that loki-doki needs to be flashed afterwards (the patcher will remind you :p). This also means that Kangabean finally works.

For users and devs who want to modify a loki'd kernel, here's the source code for unlokibootimg: https://github.com/chenxiaolong/DualBootPatcher/blob/master/scripts/unlokibootimg.py It has no dependencies and can be run separate from the patcher.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Fixed in version 1.5 :)
[Galaxy S 4 i9505 Original Android Development] hemmie:
After reading Dan Rosenberg's method , it is infact truly genius how it has been done. In the aboot.img (bootloader) there is a pirce code that checks signatures on the boot.img, so he wrote an piece of function that actually get overlaid into the exact memory location where the aboot.img signature verification function resides. Therefore effectively gaining control on the aboot signature verification and always pass the signature verification on the loki'd boot.img

And you are right since it does not touch the kernal and ramdisk functionality in boot.img when you try to patch only the ramdisk it could done and without touching the loki code (function snippet)
[Galaxy S 4 i9505 Original Android Development] karanpats:
[MENTION=4277844]chenxiaolong[/MENTION]

Hi am using dual boot patcher on my OnePlus 2..

I have successfully dual boot Oxygen Os as primary and AICP as data-slot secondary.. The only functionality I am missing is App Sharing.

If I update the ramdisk then on restart it gets into recovery boot.

I do need to update the ramdisk to enable the app sharing, right? Sorry if already asked. But I am asking for OnePlus 2 specific.

BTW.. Great app.. Love it..!! Easiest way to dual boot and use different OS..
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Hello [MENTION=4277844]chenxiaolong[/MENTION], it seems you are busy lately, still your midterms ? Good luck then.

I have some news with my 128 GB SD, I formatted it with cm13 and now I am able to install cm13 to an extsd slot, unfortunately it boots straight to recovery. I use r1929.

Here are the logs. Kernel log shows something about a partition not found. Thanks for your insight when you will have time.
[Galaxy S 4 i9505 Original Android Development] todivefor:
I have another use case. Unfortunately, development on the Galaxy S6 Sprint is nearly non-existent (basically stock rom with root). Root breaks Android Pay and flashing custom kernel or recovery breaks knox (waranty bit set) which in turn breaks Samsung Pay. I've broken both. :D There is no way, at this time, to un-knox. It is possible to un-root by odining back to stock. It would be nice to run DB with a primary or secondary rom without root in which I could run Android Pay. This poses at least two problems for DB. 1. Run primary/secondary without root. 2. Odin to stock. On 2, I have found no way to flash stock unrooted (ie there is no stock unrooted zip). Therefore, no way to DB patch. I have tried flashing stock boot.img from TWRP and flashing a stock Kernel.zip I have built, but neither will boot. So I need a way to either flash zip to un-root, or have a method to odin with DB. [MENTION=4277844]chenxiaolong[/MENTION], Is there any hope?
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
@chenxiaolong.

I have now tried to to install a ROM on my Galaxy S6 edge+ in the 'Dual Boot Patcher' app after i have patched it. I have both tried to patch a ROM on my phone and on my computer. When i try to install a Galaxy S6 edge+ custom ROM on my Galaxy S6 edge+, then it stops with different errors.

So here is a picture that shows the installation failure and the errors.

And here is the 'MultiBoot.log' file that was created after this: https://dl.dropboxusercontent.com/u/7309753/Mobiltelefoner/Samsung Galaxy S6 edge+/MultiBoot.log

Do anyone of you here see what the issue is?
[Galaxy S 4 i9505 Original Android Development] :
I have trouble dual booting JFTLE-GPE 5.1 (by Danvdh, http://xdaforums.com/showthread.php?t=2557353) and any other ROM, AFAIK.

I use Dual Boot Patcher 8.0.0.r1927.g47f1396.

So, my primary ROM is JFTLE-GPE 5.1, but I want to dual boot it with a Marshmallow build, for exmaple any of these two:

http://xdaforums.com/galaxy-s4/i9505-develop/rom-crdroid-t3017844

http://xdaforums.com/galaxy-s4/i9505-orig-develop/jdcteam-android-source-project-mra58v-t3251663

I tried dual booting an older version of my Primary ROM, as secondary ROM, which worked fine, even though it used a different Kernel.

All ROMs I tried dual booting with are based on Linux Kernel 3.4.x.

Am I doing something wrong? I just patch any ROM using the app, or PC, install it like a normal ROM, switch to the Secondary ROM using the Utilities, I reboot my Phone, and it boots back it to recovery.

If you need any logs, please tell me.
[Galaxy S 4 i9505 Original Android Development] corncobman:
With the latest patcher, I can no longer use the Windows .exe to patch. It says "The program can't start because libharfbuzz-0.dll is missing from your computer. Try reinstalling the program to fix this problem."
[Galaxy S 4 i9505 Original Android Development] :
I have the same issue, try using the .apk file.

8.0.0.r1927.g47f1396 worked fine for me.
[Galaxy S 4 i9505 Original Android Development] todivefor:
It looks like you ran out of room:

Flashing System...
minzip: Error writing 28672 bytes from zip file from 0xffbcd844: No space left on device
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/lib64/libpac.so"
minzip: Extracted 2031 file(s)
minzip: Extracted 36 file(s)

When you patch to dual, you need to have enough space in system, cache, and data.

Try patching and flashing to data-slot.
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
LOL, so that was the problem :laugh:. Ok gonna try to patch the ROM under 'Data slot' to see if that will help.

Or will it help to delete anything on the internal storage like videos and stuffs like that and then run it as 'Secondary' under Dual boot?
[Galaxy S 4 i9505 Original Android Development] todivefor:
Cleaning up internal SDcard would not help. You would have to do major debloat on system. If S6 Edge+ is like S6, which I assume it is, you only have TW roms to work with. Two TW roms in system is very unlikely even with major deblloat. Data-slot works great for me.
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
Ok, thank you very much for helping :good:.

EDIT: That worked. Booting up the second ROM under 'Data slot' now.

EDIT 2: Setting up the ROM now, So it's working good.
[Galaxy S 4 i9505 Original Android Development] gaww:
I used 1927 on Windows to patch a modded (for S4) CM13 to ExtSD and it patched and installed it with no issues. I was on Windows Pro 8.1 64 bit. Ran into a similar problem with Windows with much earlier patcher and there was a file (forgot which) needed that fixed it.
[Galaxy S 4 i9505 Original Android Development] RWOLUPO:
Does anyone know, whether Nexus 5x is suppprted?
[Galaxy S 4 i9505 Original Android Development] sronweb:
Nexus 5 is supported but not 5x.

I don't see it in the list.
[Galaxy S 4 i9505 Original Android Development] midi_1996:
Hi,

Well, since I have my phone internal & external near full (have like ~2GB left on the internal, it's the bare minimum for the OS + Gapps + some apps to settle in) I tried the windows version of the tool but I get some missing dlls. I provided one from the net then a list of other missing ones poured on my screen ヘ（。□°）ヘ . Normally the zip should have all the dlls needed, or am I wrong? Should I keep dling each one until the program runs?
[Galaxy S 4 i9505 Original Android Development] gaww:
Forgot about the 7 tap option - lol.

All is back to pre-extSD, but it still looks like I may still have a residual file on it based on its current free space compared to earlier.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
New log!! Now it just say Failed to update ramdisk.
[Galaxy S 4 i9505 Original Android Development] pvsgh:
Support for AT & T Note 2 (SGH-I317)

Hi Chen,

I know you are busy, but whenever you get a chance can you add support for AT & T Note 2 (SGH-I317), attached are the required files.

thanks,

pvsgh
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Looks like you ran out of space on your system partition. Try using a data-slot (which installs to the data partition) or an extsd-slot (which installed to the external SD).

EDIT: Whoops! Looks like [MENTION=2688336]todivefor[/MENTION] already answered your question.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah crap, it looks like it requires some new dependencies. I'll look into that, thanks.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
There's no need to download anything normally. On the PC side, I use the Qt library (http://www.qt.io/), which looks like it got some new dependencies in the 5.5 update. I'll fix this as soon as I can :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, look's like something got really screwed up in the process (trying to update a 0 byte boot.img). Could you clear the cache and data for the app and try again?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Added support in 8.0.0.r1933.g8cfbb06.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes, that's correct. When it auto-reboots into recovery, could you pull the logs with the GetLogs zip at https://snapshots.noobdev.io? That will save the logs to /sdcard/logs/. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Stop giving me good ideas! Just kidding :D

Patching Odin images is something I've wanted to do for a very long time also. I do this manually all the time and I've just been too lazy to add support for it in the patcher. Extracting the tar.md5 file and stuffing the contents into a zip is very easy for the patcher to do. Converting the "system.img.ext4" file from a sparse ext4 image to a plain ext4 image might be slightly more difficult (Odin/heimdall does this automatically).

I'll hopefully be able to implement this feature this week. It shouldn't take more than a few hours (or so I think)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! My midterms are over (finally!), but I have the GRE exam coming up on Tuesday, so not much time to rest yet.

The error is still the same as before; It doesn't seem to be detecting the card, so it can't mount it. In a few days, I'll make a test build for you that adds a 15 second delay to see if my theory that it's detecting the card too slowly is correct. If so, it'll be a pretty simple fix: just wait until the phone detects the SD card.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, if you could grab the logs that would be great. Just flash the GetLogs zip from https://snapshots.noobdev.io/ and it will save the log files to /sdcard/logs/. Be sure to flash that zip when it auto-reboots to recovery. Otherwise, some logs, like the kernel log, will be lost. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Just throwing some ideas on the table, but is anybody interested in a version of DualBootPatcher that runs purely in the browser? I just came across the Emscripten project recently (http://kripken.github.io/emscripten-site/index.html), which allows C and C++ code to be compiled to javascript. It looks like some game engines are even starting to use this + WebGL. It would be pretty cool to be able to go to, eg. https://patcher.noobdev.io, and immediately patch zips (locally) without having to download anything. Of course, this is really only useful for those who are currently using the PC version of the patcher.

I have no plans for this yet (there are far more important things to do and fix right now), but it's just something to think about :)
[Galaxy S 4 i9505 Original Android Development] kingknuts:
No luck... It just corrupts my boot.img... Now I reflashed my boot.img and it get stuck again in please wait, I leave all night and it still showing please wait.
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
As cool as it looks like, I think this kind of stuff belongs more in a local app (and JavaScript would add nasty bugs). An auto update feature in the app would be more interesting I think. Just my 2 cents.

Envoyé de mon Samsung Galaxy S5 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[SOLUTION!] HOW TO gain the space back after inapp wipe rom on extsd.

Hello guys. For those experiencing problems with space not gained after inapp wiping a rom installed on your extsd slot I have a solution for you! ;) Currently working on my Win 10 Pro x64 machine. What you need?

-PC

-Micro SD Card Reader

You no londer need to format the whole card to fix the problem. The key here is one problematic folder named FOUND.000 containing files FILE0000.CHK, FOUND0001.CHK etc....which are eating the space. In my case the FOUND0001.CHK file was containing the whole folder structure and files of my old extsd rom. This directory is hidden by default and you can't see it even if you enable "Show hidden files" in Windows so I used DiskInternals Linux Reader and explore the folder and the files in it. But you can't delete those files with this program and that's why we'll using the Command Prompt and make sure you run it as admin!

First navigate to the specific drive letter of your extsd card typing the following command:

cd H:

(where "H" was my extsd card drive letter, make sure to use the correct letter on your pc)

then navigate to the FOUND.000 folder:

H:\>cd H:\FOUND.000\

and delete the file:

H:\FOUND.000>del FILE0001.CHK

(In my case the big file eating the space was FILE0001.CHK, make sure you typed the correct name of yours as it might be not the same.)

In the end you can delete the entire FOUND.000 folder:

H:\>rmdir FOUND.000

That's it, you're done, thanks me later.:fingers-crossed:

[MENTION=4277844]chenxiaolong[/MENTION] mate, I suggest you to link this post in the OP post in "How do I...?" section if you wish.
[Galaxy S 4 i9505 Original Android Development] :
Alright, here are the logs. I installed the ROM using the app, let it boot, but it went to recovery, flashed the GetLogs, and this is the result.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Patching ROMs without any app?? That would be pretty awesome! ?

Can you please tell me if you have made any progress with the problem with MediaTek devices' ROMs?? No hurry, take the time you need.. Just asking..

P.S.: When do you sleep?? [emoji15] If I'm right you've made this post at 2 AM at your place... How many hours do you sleep then?? Just saying..
[Galaxy S 4 i9505 Original Android Development] todivefor:
That would be nice for one reason, it is hard to keep up-to-date with you with all the time you spend fixing everyone's problems. With how useful this app is, doing all the downloads and installs is pretty trivial.
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Are you trying to install to external SD ? If yes you surely have the same issue as me. It seems the app does not succeed in mounting your external SD. It is formatted in ext4, maybe you can try reformatting it to fat32. Anyway ext4 will not work with Marshmallow

Envoyé de mon Samsung Galaxy S5 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] :
I think the ROM I am using supports ext4, since it does recommend using F2FS, that does not mean it won't work in ext4.

And no, I try installing to /system/multiboot (secondary)
[Galaxy S 4 i9505 Original Android Development] wawa9292:
SM-N910G failed to flash secondary rom

Hey mate, I'm on SM-N910G running stock based ROM (SimpL ROM) as primary..

I have successfully update ram disk and etc, then the problem come when I'm installing the secondary both through recovery also snapshot app..

This is what I get in snapshot..

[IMG="this is from snapshot app 8.0.0.r1932.ga5b4ef1"]https://scontent-sin1-1.xx.fbcdn.net/hphotos-xaf1/v/t1.0-9/12243594_1264468753578773_3024665235114770182_n.jpg?efg=eyJpIjoidCJ9&oh=2633eadee9e714ea1219f4c2db15ee67&oe=56F1DCEA[/IMG]

And here is some multiboot.log..

BTW for secondary I patched SOKP LP for SM-N910G..

Hopefully someone help.. :)
[Galaxy S 4 i9505 Original Android Development] gaww:
Stupid question maybe, but why not just delete the folder right off, as its name is known and the Linux tool would not be needed ?
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Ext4 support for external SD or system/cache/data ?

---------- Post added at 03:57 PM ---------- Previous post was at 03:50 PM ----------

The app identifies your phone as trlte. The patched ROM is for trltexx, trltedt. I guess there is a mismatch in the patcher. Provide the logs generated in /sdcard/logs by flashing getlogs.zip in recovery so that the dev can look into it.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I didn't tried directly deleting the folder it might work as well.
[Galaxy S 4 i9505 Original Android Development] wawa9292:
Yess i have edited my previous post.. please dev.. guide me..
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Shoot, I totally forgot about FOUND.000. That directory is created whenever the filesystem on the SD card gets corrupted (eg. from a hard-reboot or battery pull). The OS will put whatever files it recovers into that directory, which is why you got that huge file back. Depending on what filesystem you use, you may get a "FOUND.000" (as you found), "LOST.DIR", or "lost+found" directory.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It's actually the ROM that's checking to see if your device is "trltexx" or "trltedt". and both your ROM and your recovery are reporting "trlte". Unfortunately, there's nothing I can do about this. It would have failed even if you flashed an unpatched version.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! What filesystem is your external SD formatted with? It's failing trying to mount your external SD with exFAT, FAT32, and ext4.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, can you send me your boot.img file? I'll do some testing to see if there's something weird about the file.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] please take a look at this error please. I'm running into a new episode of issues dual booting my device - Lenovo K3 Note. :D This is the first time I'm seeing this error and I believe it's related to the new 1547 update for the phone. Logs attached. For the record the rom from the screenshot that failed to install was running fine before 1547 DEV. Other roms I tried are throwing the same error message. Any suggestions other than downgrading my phone to 1546?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I haven't had time to take a look at the issue yet.

Haha, yeah I have a horrible sleeping habit :D Sometimes, it's 4 AM to 2 PM. Other times, it's 12 AM to 7 AM (when I have to go to work lol).
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
It's nice to mention that I have both FOUND.000 (which was pretty much related to the DB app) and LOSTDIR folders on my extsd. :P Actually I really don't mind the LOSTDIR because I have it on all my extsd cards on multiple devices.
[Galaxy S 4 i9505 Original Android Development] :
Well, my externalSD card is formatted in exFAT...

I feel really stupid now, on one of thread of the ROM is tried installing it literally says; "ExFAT is not working, format your MicroSD card in FAT32"... :silly:

I feel so stupid... Sorry for wasting your time :rolleyes:, but if you didn't point it out, it still didn't work :)

Thank you so much!
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
exFAT is pretty tricky filesystem to mount on Android. I recommend using FAT32 if you're not a fan of watching big >4GB HD movies on the go. :) With that said it's strange habit of the manufacturers to sell their cards formatted in exFAT right out of the box.
[Galaxy S 4 i9505 Original Android Development] kingknuts:
Here it is thanks for your effort!!
[Galaxy S 4 i9505 Original Android Development] karkasss:
How can I install another rom to primary without affecting sub roms installed in data-slots.

In other words, is it possible to wipe /data folder excluding data/multiboot folder?

I saw the instruction on OP about primary patch but I’m not sure how it work.

Is this patch only working for upgrading of primary rom (same rom)?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If your device supports AROMA installers, you can wipe the primary ROM (excluding /data/media and /data/multiboot) using DualBootUtilities (available at https://snapshots.noobdev.io). Otherwise, you can simply boot into another ROM and wipe it from the app (hit the 3 dots menu button for the primary ROM entry).

EDIT: I definitely recommend patching the new primary ROM you plan in installing. It prevents the ROM from overwriting/deleting /data/multiboot, /cache/multiboot, and /system/multiboot.
[Galaxy S 4 i9505 Original Android Development] wawa9292:
That's strange, I've always successfully flash and boot with that rom unpatched version as primary..

Is that could be because now i'm using SM-N910F ROM and attempting to use on my SM-N910G (as primary)??

Or maybe can you make support for SM-N910G model of snapdragon note 4??

Because when i try to update ramdisk while using ROM for SM-N910G (Dr. ketan) it get failed..

I'll try to provide the log..

What's I need to do??

EDIT : I've found a way for the mismatch device check.. Just flash lastest version of TWRP via odin and the issues is gone..

Now, finally I've succeed install, also dual booting a stock based and cm based ROM..

Device: SM-N910G

PRIMARY : SimpL ROM for SM-N910F

DUAL : SOKP for SM-N910G

Thanks chenxiaolong.. You're really awesome.. :)