yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] royredman:
Hey, Im really having problems trying to patch this rom manually.

For some reason it won't let me patch the kernel for it. I have the Verizon Galaxy S4. Is anyone able to complete this?

http://xdaforums.com/showthread.php?t=2487979
[Galaxy S 4 i9505 Original Android Development] jova33:
Pull the boot.img out and patch it with the phone app. Delete old boot.img, rename boot_dualboot.img to boot.img.

It worked for me with AOKP.

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] jova33:
Say... how do I patch a boot.lok boot image? I d/l faux's kernel and the patcher said can't patch. Looked in the zip, and instead of a boot.img, it's a boot.lok.

Renamed it boot.img just to see if that'd work lol. Seems it's not that simple.

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] traicer:
so patching the whole rom zip with the phone app works then?
[Galaxy S 4 i9505 Original Android Development] `SBR`:
yes even i had the same issue in IOKP using manual patching and Patched KT Kernel.....

But i tried the Dirty Unicorns AOKP and Patched KT 4.3.1 (using 1.14) it worked without any issues.. rom runs smoothly

But primary TW rom have the Wifi Connectivity issues (wifi is not switching on), don't know where the problem is.. only solution is reflash the TW rom..

EDIT: Ideally Wifi modules will not overwrite btw TW/Dual roms.

flashed the TW rom with formatted System and existing data partions, still wifi not connects. Clean flash brings the Wifi back in TW but lost the dual rom.. have to try Odin and install back everything... will share the results later.
[Galaxy S 4 i9505 Original Android Development] jova33:
If the ROM you're trying to patch has been manually patched in the past and someone submitted a patch info file for the dev to include in the app.

Most VZW ROMs have not been submitted because most people with the VZW S4 took OTA updates that patched loki. So I've manually patched anything I want to work.

The boot.img can be auto patched though.

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] royredman:
hey, I wasn't able to dualboot after following your instructions. One thing that I am confused about is that on your primary rom when you install the rom switcher app, it doesn't ask which rom your on, just which kernal your on. When I installed it on my second rom, it allows me to choose which rom im on. :/ When I tried switching roms, it bootloops
[Galaxy S 4 i9505 Original Android Development] jova33:
You may not have patched your secondary ROM properly and it wiped system.

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] royredman:
I used the rom patcher app though, I don't understand why thats happening.
[Galaxy S 4 i9505 Original Android Development] jova33:
Well, when you first install the app, before you flash a secondary ROM, you only have one ROM, so the app knows this.

Did you set the primary kernel as that in the app before you flashed your secondary ROM?

Did you try flashing your primary ROM's kernel or ROM again?

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] rlorange:
You can just delete the following folders:

/system/dual

/data/dual

Factory reset won't get rid of second rom system folder. Or you can use the CWM dual boot utilities zip
[Galaxy S 4 i9505 Original Android Development] Brandroid28:
Any ideas on this? I don't wanna choose between Hyperdrive and Liquid Smooth. Lol.
[Galaxy S 4 i9505 Original Android Development] jova33:
Try manually patching?

Sent from your mom's smartphone
[Galaxy S 4 i9505 Original Android Development] chavdar:
Dual booting is working fine with me but I have a problem with Foldermount on the second ROM - it only mounts Android obb. I also want to mount Android data from my extSdCard as well as two other folders but it does not work. Any ideas?

I tried pacman and probam with different kernels but the result was always the same.

Any help will be appreciated
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
Congrats :)

Here are the links:

update-binary: https://drive.google.com/file/d/0B20JfVIKCreWXy1zcWM5bDJNNUE/view?usp=docslist_api

updater-script: https://drive.google.com/file/d/0B20JfVIKCreWVVhocDY4a2YycWs/view?usp=docslist_api

These are the untouched files. I'm saying that because I was able to flash this ROM after using a hugely edited updater-script by [MENTION=5048731]911-Future_Maker[/MENTION]

Here's it is (if it maybe of any use for you): https://cloud.mail.ru/public/MoRd/aLJpNZnr8.

Note that we usually remove the first few lines that verify the model no. and custom recovery and all that (since it is official stock ROM) and the log I provided in that post is after those edits, and that failed showing some assert failed error as you must have seen in the log.
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
That's coz the script is getting to check conditions and it's no fault of dualpatcher coz your system is not completing those conditions, it could be a specific bootloader, a modem or anything. You can simply remove these conditions from script and try to flash again. I tried this with one of cm13 rom that's checking a specific bootloader.

Sent from my "i9300/1+2" powered by Carbon/Temasek

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S 4 i9505 Original Android Development] Russiamen:
Yes,he have 6.0
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
I don't think so. The first lines are used for verification, as I said. But the error was from some assert (write raw image) command. Let the dev see it anyway.
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
Verification doesn't happen only in the beginning and you would know if you read the script, anyways leave it. Since u already provided the log to the dev, let him check them.

Sent from my "i9300/1+2" powered by Carbon/Temasek

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S 4 i9505 Original Android Development] Gerxp:
When I want to flash to SD card I get an error that my SD card is read-only...

It is not. And permissions are fine.
[Galaxy S 4 i9505 Original Android Development] Russiamen:
Add gt-p5100/(Samsung galaxy tab 2 3g)
[Galaxy S 4 i9505 Original Android Development] Gerxp:
Flashing to Multislot I get this error:

Any idea what is the problem here?
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
Thanks, bro
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
You have to provide logs to get an answer
[Galaxy S 4 i9505 Original Android Development] Wislley Frauner:
This is happening with the Moto G 2014, how to solve?

---------- Post added at 02:09 PM ---------- Previous post was at 01:48 PM ----------

Something went wrong, the following error appears:

failed to backup current selinux policy read only file system.

How to solve this problem?
[Galaxy S 4 i9505 Original Android Development] Russiamen:
Update mbtool
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I can't connect to mbtool on the latest build went back to 2360 and all is fine. Roms are detected fine, but when trying to flash some zip I get mbtool no connection or something like that.

Anyone with similar experience? [MENTION=4277844]chenxiaolong[/MENTION] I'll provide logs if you're interested dude. :)
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION], hello sir!

Assist with this task plz:

Can you add patching of *.tar files to the patcher?

I'm unable to boot my ROM(2nd) ,I restored my ROM but my kernel somehow is missing, the only kernel I have it's a *.tar NOT *.tar.md5 and thus can't patch it, at this moment my only option it's to reinstall the OS!

Thank you!

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] corsicanu:
Can't restore it with recovery? If it was patched before you can simply restore it, doesn't matter the slot. Or try to untar and make it flashable zip. I can provide updater-script for kernel if you need. Cheers!

LE: Post #9000 [emoji23]
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Pls do provide the script, I'm not sure how to create the flashable file either!

Can you guide/send where to read up to create a flashable kernel,I have the boot file!

....

The *.tar file I have can only be installed from Odin unless I create flashable file with that boot image,

My device it's note 10.1 2014LTE

And weirdly now my primary rom,AOSP6, can't connect to multiboot tool and thus my patcher it's not showing the ROM, it's claiming I'm not rooted...which it's really retarded thing to say considering other ROMS are getting root promnt!

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If it's an Odin tarball, just rename it to .tar.md5. There's no difference except that the .tar.md5 files have the MD5 hash appended to the end of the file (which is ignored by the patcher anyway).
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
I did that them upon flashing there was an error preventing installation, I'll update log!

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] Ranomez:
[MENTION=4277844]chenxiaolong[/MENTION] please add support for Xiaomi Redmi Note 2 (hermes) if possible.

Also since most ROM's for this device have uboot included in the zip I guess it would be recommended to remove the uboot and the uboot flashing lines from the scripts in the zip before patching for dual-boot, right?
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] I have an idea for a new feature: Can you add sorting ability in roms list? Sort by installed date, name or size would be great.
[Galaxy S 4 i9505 Original Android Development] martyh1:
Noob here for dual boot. I don't see anywhere in the instructions about what to do with the DualBootUtilities.zip file once it's downloaded. Obviously it's flashable, but the instructions don't say to flash it. Is it really necessary at all? I ran the patcher on a Beanstalk 6.0 rom zip file (and on the gapps zip file also) for my tmobile note 4 that is currently booted stock TW rom (5.1). It appeared to be successful. I already set the kernel for the TW primary rom also. I'm ready to flash the Beanstalk patched (dual) rom (and gapps dual patched). Where do I need DualBootUtilities.zip?
[Galaxy S 4 i9505 Original Android Development] nicesoni_ash:
That's to switch roms or clean them from recovery.

Sent from my "i9300/1+2" powered by Carbon/Temasek

Fueled by 7000mAh ZeroLemon Battery
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
Good day [MENTION=4277844]chenxiaolong[/MENTION] and everyone ....

While making backups of roms from recovery via ADB, can I command the backups to be stored on the PC instead of sdcard/external_sd/usbstorage ...?

My current backup directory it's "-d /sdcard/backups" what Xud I change here so the backup goes to PC directly!

Reason: my current room has data of >9gb due to deezer cache, this backup fits no where, total compression takes centuries!

Plz advice

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2438.g47c62b9 should hopefully fix this :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I think 8.0.0.r2440.g2dcff34 should fix this.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
ADB currently doesn't provide a way for the device to access files on the computer, so unfortunately, there's no way to do what you want.
[Galaxy S 4 i9505 Original Android Development] nandofer:
when trying to install the error appears that the rom was not made pro osprey_usdtv. My device is a moto g 2015 osprey xt1544
[Galaxy S 4 i9505 Original Android Development] coldgin_:
Hi ,

this is because your specific version of the Moto G 2015 isn't included in the patcher.

Add the following line to your build.prop file in the primary Rom:

ro.patcher.device=osprey

Reboot your phone and then try again. It should work, It works for me :)

Regards!
[Galaxy S 4 i9505 Original Android Development] Harjito:
galerry and camera error

Please help

after updating the ramdisk , I could install secondary rom . but the gallery and camera error after update ramdisk.

if I do not update ramdisk , I can not flash in the secondary rom . it says "failed to create temp directory:read only file system".

how to update ramdisk without effect to the gallery and camera .

# galaxy s4 i9500, the atom rom v . 1 in primary rom .

thank you
[Galaxy S 4 i9505 Original Android Development] chavdar:
[MENTION=427477]chenxialong[/MENTION]:Hi chen, is the issue with booting from extsd fixed in some of the new versions? Last time I tried booting from extsd card landed in Recovery on my Galaxy S5 Snapdragon.

Is there a way to put data also in extsd? I am unfortunately running very quickly out of space on /data :)
[Galaxy S 4 i9505 Original Android Development] Russiamen:
[MENTION=4277844]chenxiaolong[/MENTION]

Is it possible to add these two devices p5100 and p5110,they range rom with 4.0-6.0 :good:
[Galaxy S 4 i9505 Original Android Development] Killerdog:
[MENTION=4277844]chenxiaolong[/MENTION]

Hi,

you make a pretty good job with this tools, i have a LG G4 (H815) with Latest Official rom as a base (H815v20D)

i succesfully install 2 rom in the data partition (AOSP and CM13) for an unknow reason when i patch the latest SuperSU (i try from 2.66 to 2.71) and flash it, the Root is not present in Both of this rom (in CM13 it doesn't matter because i can activate CM Root inside dev option).

but i've got another problem, i can't use app sharing functionnality, it say i need to update mbtool, so i update ramdisk in the primary rom (Stock LG) but after the reboot my phone vibrate five times and goes directly to TWRP.

if i reboot my phone again it does the same things.

with some attemps when i flash the backed up boot img before ramdisk update my phone restart correctly to Primary ROM, sometime not (i need to flash stock boot.zip to correct this).

i made two logfile, one before update and one after.

if you have an explanation AND a solution it will be very appreciated.

Thanks
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] Using the 2347 build I don't have wifi on the CM and AOSP roms I have installed on extsd-slot. The wifi switch is not working . I have wifi only on primary rom (BlissPop v4.0.3 Android 5.1.1) and on MIUI7 7.2.2.0 (Android 5.0.2) on my extsd-slot. Went back to 2360, updated the ramdisk on all roms (even forced) and all is good again.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
I also ran into a weird problem, my cm13 note 10.1 2014 p605 when running as secondary doesn't see SIM card, but when primary all good...Is this related to the patcher and if so how?

<<<New World Order (NWO)>>>
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
I believe it is. Because when changed the build and switched to an older one the things are working fine.
[Galaxy S 4 i9505 Original Android Development] messi2050:
Please can you add support for Samsung note 8 kona3g (n5100)

here is the log

http://www.mediafire.com/?xyefsaqrw5sj3rd
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Hey [MENTION=4277844]chenxiaolong[/MENTION] Is it possible to implement restoring twrp backups as feature? Or it even exist? I know that the patcher supports backup/restore, but want to clarify. It can restore fine a rom that was previously patched for multiboo, but now I'm talking about restoring a non patched backups. I'm asking this because recently many guys are sharing rom at the form of twrp backups instead of flashable zips.

In short can we restore a non patched twrp backups? I'll guess even if it's possible it will break the multiboot code for the others installed roms. It will just replace the primary rom.
[Galaxy S 4 i9505 Original Android Development] martyh1:
I got this dual boot working which was pretty amazing but I can't use this on a regular basis. Two dealbreakers.:

- My primary slot can't write to the internal sd card. I tried two different ROMs in that slot, but no luck.

- I can't hear anyone on the phone on both the primary slot and the dual slot.

Pretty cool work though! I'm using a US Tmobile Note 4 (n910t3).
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION], I'm still having issues with my primary stock MM6.0 and being able to use the external SD card. Previously you mentioned that the system is calling for exfat and you made some updates to address the issue. The fixes made seemed to fix the issue for non-primary slot ROMs, but still no good in primary. I installed the current version of DBP and still have the issue, but looking at the Ramdisk-update log, I think I might see a disconnect. I've attached the ramdisk log for reference, but think the part in question is here. What do you think?

mbtool says current ROM ID is: primary
04-09 12:03:29.306 1125 1184 D UpdateRamdiskTask: Original boot image type: 1
04-09 12:03:29.306 1125 1184 D UpdateRamdiskTask: Original boot image had /romid file in ramdisk: false
04-09 12:03:29.306 1125 1184 D UpdateRamdiskTask:
[B]vold uses fuse exfat: NO[/B]

Thanks!
[Galaxy S 4 i9505 Original Android Development] GioBasi:
I just update , from 19march to last version and I have error when installing rom on any place secondary, multi slot , data slot , ext sd. so I have to back to old version . sorry didnot get any log :(
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I am able to reproduce the wifi issues some are seeing in the latest builds, though I'm not sure why it happens yet. I'm working on fixing it.

EDIT: Also able to reproduce issues where the internal storage is not writable.
[Galaxy S 4 i9505 Original Android Development] Killerdog:
Hi chenxiaolong.

Did you can check why I can't update my ramdisk without having a bootloop to twrp on my h815?

I can't use app sharing without update my ramdisk.

I upload the logs some post ago.

Thanks

Envoyé de mon LG-H815 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r2450.g3cb9002 should fix a number of bugs that were introduced in the last big release:

Fixed non-writable /sdcard due to mount-namespace separation of init wrapper and app sharing daemon. Very likely also fixes wifi and modem errors that some people have encountered.

Fixed mbtool connection issues due to sepolicy patching failure

Fixed "Failed to create temp directory: Read-only file system" during in-app flashing

Fixed missing warning when the kernel has never been set (eg. in primary ROM)

Fixed missing warning when a new kernel has been flashed, but not set (eg. after restoring boot.img in TWRP)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I think this should be fixed in 8.0.0.r2450.g3cb9002 :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
It looks like the multiboot code is failing to mount the SD card for some reason. From multiboot/kernel.log in your "after" dump:

[1] mblog: 1 fstab entries for the external SD
[1] mblog: /default.prop contains fuse-exfat override: false
[1] mblog: Using fuse-exfat: 0
[1] mblog: Failed to mount /dev/block/mmcblk1p1 (exfat) at /raw/extsd: No such device
[1] FAT-fs (mmcblk1p1): bogus number of reserved sectors
[1] FAT-fs (mmcblk1p1): Can't find a valid FAT filesystem
[1] mblog: Failed to mount /dev/block/mmcblk1p1 (vfat) at /raw/extsd: Invalid argument
[1] EXT4-fs: failed_mount
[1] mblog: Failed to mount /dev/block/mmcblk1p1 (ext4) at /raw/extsd: No CSI structure available
[1] mblog: /default.prop contains fuse-exfat override: false
[1] mblog: Using fuse-exfat: 0
[1] mblog: Failed to mount /dev/block/mmcblk1 (exfat) at /raw/extsd: No such device
[4] FAT-fs (mmcblk1): bogus number of reserved sectors
[4] FAT-fs (mmcblk1): Can't find a valid FAT filesystem
[4] mblog: Failed to mount /dev/block/mmcblk1 (vfat) at /raw/extsd: Invalid argument
[4] EXT4-fs: failed_mount
[4] mblog: Failed to mount /dev/block/mmcblk1 (ext4) at /raw/extsd: No CSI structure available
[4] mblog: Failed to mount fstab

If the stock LG ROM needs to do some initialization tasks during boot (for example, turning on the SD card reader), then I don't have a way of fixing this. Are you using an obscure SD card setup, such as multiple partitions, encryption, etc.?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Patching a TWRP backup to flash as a ROM is rather difficult to do because the patcher is not designed to handle directories (eg. /sdcard/TWRP/BACKUPS/blah) or split archives (eg. system.ext4.win000, system.ext4.win001, etc.). It would take a significant amount to work to be able to implement this.

Right now, if you restore a TWRP backup like the ones you mentioned, it will almost certainly break the multiboot setup. When TWRP restores backups, it wipes the partitions before it starts restoring the files.
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
Yeah, just what I was thinking, sad :( For for answering bro!

Did you saw my idea for adding a sorting feature in the patcher? Is it possible?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, well we're one step closer! "vold uses fuse exfat: NO" is good because Motorola doesn't use fuse-exfat. It uses the exfat kernel module. The next step is to see why it's not making any difference. Can you try grabbing the dmesg output as early as possible during the boot, preferably during the boot animation? It should log how mbtool is mounting the SD card.

adb shell dmesg
# If you run into a permissions issue, try with root
adb shell su -c 'dmesg'
[Galaxy S 4 i9505 Original Android Development] Killerdog:
Hi, I only have a 128gb SanDisk formated in exfat.

I will try without my SD card in the phone.

And with another card.

Strange behavior I use my SD card only for storage (rom, backup, music...) not for dual boot.

Edit : so I test without SD, and it works.

Test with a 32gb SanDisk SD formated in exfat and it's work too.

Put my 128 SanDisk SD exfat and bootloop to twrp again.

Really disappointed because I love to have a lot of storage in my phone. [emoji20]

Envoyé de mon LG-H815 en utilisant Tapatalk
[Galaxy S 4 i9505 Original Android Development] Z-Fire821:
Hey could you implement support for our OnePlus X Onyx? That would be very nice :)
[Galaxy S 4 i9505 Original Android Development] 911-Future_Maker:
[MENTION=4277844]chenxiaolong[/MENTION] On builds newer than 2360 while the flashing is in proceed I'm getting a message: Warning: No file_contexts . Never saw that till now. The roms are being installed just fine, but the message is kind of boring. :p
[Galaxy S 4 i9505 Original Android Development] v00d007:
Am I wrong or is app sharing across LP and MM roms still not working?
[Galaxy S 4 i9505 Original Android Development] ewangw:
[MENTION=4277844]chenxiaolong[/MENTION],

Here is the log I was able to capture at boot. Hope it helps.
[Galaxy S 4 i9505 Original Android Development] SolDroid:
I'm having the exact same problem. Everything else works fine. I patch to dual. Install the rom. Everything works great on the room until I go to make phone calls. The call dials, connects, yet I cannot speak or hear. Other than that it's great. Had to raise. Restore.