yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] todivefor:
I have not been able to set the kernel from the app. I thought you had to be running the rom in which you want to set the kernel and that is the rom that is bootlooping. Is there a way to set kernel for data-slot-test from say primary?

The only difference between the kernel that crashed and the one that was running good was an intervening TWRP backup. I have not done any restores. I am running an alpha Xposed in this rom. The only reason I thought the problem was a DB issue was due to the fact that the DBUs did not list this rom.

I had just noticed that the DBUs get updated regularly. I have the latest and will try them the next time.

Thank you for your efforts.
[Galaxy S 4 i9505 Original Android Development] calj17:
Can anyone please help me. Never did the dual rom patch. I have a Note 4 with stock rom and wanted to dual boot with cm12. 1 and share apps in both roms. Can anyone help me with a tutorial on how to do it?

Enviado de meu SM-N910C usando Tapatalk
[Galaxy S 4 i9505 Original Android Development] cruor.am:
Hi dev!

Temasek's CM12.1 Rom (you will find url for download only Temasek's kernel too) http://xdaforums.com/showthread.php?t=2953375

BlissPop Rom http://xdaforums.com/showthread.php?t=3007958

Dirty Unicorns Rom http://xdaforums.com/showthread.php?t=3006601

So, if I downgrade to an older version of dualboot patcher, I should be able to multiboot again, shouldn't it?

Thanks again![emoji6]
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
here im attaching the logs as you instructed. hope this will be enough.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the links! Unfortunately, it looks like the Lenovo S650 uses an emmc partition layout and both mtd and emmc partition layouts are not supported by the patcher. It would take significant work to add support for these and might not be worth the effort because newer devices no longer use these partition layouts. :(

(If you're interested, here's a link describing some of the differences between mtd, emmc, and mmc: http://www.digitalinternals.com/mobile/android-mmc-mmcblk-partition-layout/259/ and https://github.com/ameer1234567890/...To-Gather-Information-About-Partition-Layouts)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the links! Actually all of those implement f2fs the "good" way without using ugly scripts, so they should be working. You said it never goes past the Samsung logo and then reboots to recovery right? Would you mind trying to grab the logs again when it autoreboots to recovery? Hopefully this time, it will be able to grab the /proc/last_kmsg log. Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the logs! Unfortunately, neither of them have /proc/last_kmsg, which is what holds information about the errors. Could you check to see if your recovery has this file? (From TWRP, "Advanced" -> "File manager" -> /proc/last_kmsg)
[Galaxy S 4 i9505 Original Android Development] Ather:
hey [MENTION=4277844]chenxiaolong[/MENTION] now that we have sdcard support, is it possible to install TouchWiz based roms in ext slots? as for now i have 1 TouchWiz (primary) and 1 cm12 (extslot1), before posting i did search and all those posts are pre sdcard support..
[Galaxy S 4 i9505 Original Android Development] lilila:
I have tried TW roms in extSdCard and it works on my N910T.
[Galaxy S 4 i9505 Original Android Development] ItzShadowz:
Will do! I was planning to root my G4 soon anyway so I'll get right to it as soon as I get twrp and whatnot :)
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
i have checked but i couldn't find "last_kmsg" in the /proc/ . is it because i have done something wrong or did i miss something. if so can you please guide me. i have just followed your instruction. again thanks for your valuable time.
[Galaxy S 4 i9505 Original Android Development] ItzShadowz:
About to finish unlocking my bootloader and flashing twrp. Do you want me to send you the file via PM or on this thread?

EDIT: Sent you the .tar via PM :)
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

Why do I have free up aprox. 2.8 GB(!) on data partition to install a cm12.1 rom to dual slot??? That can't be right, ey? Tested patcher versions 1460 up to 1707.

EDIT: Result was cm12.1 nightly stuck in 1st boot cause it failed to build art cache afterwards anyways... damn!
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

With v1707 and latest cm12.1-0915 the problem still persists. Install succeeds but building art cache process on 1st boot seems to be somehow broken. See scrshot how it looks afterwards.
[Galaxy S 4 i9505 Original Android Development] todivefor:
[MENTION=4277844]chenxiaolong[/MENTION], I have had this happen again. However, DB was not being used. In updating to my latest firmware, I had to reflash to stock to take the update. Reflashed my custom rom and haven't DBed yet. Sorry for the trouble, and thank you for all you do for this great product!
[Galaxy S 4 i9505 Original Android Development] xdasree:
[MENTION=4277844]chenxiaolong[/MENTION],

I can not patch any of zip file from Kernel to any other mod. Its happening from last few builds. Attached log file.

View attachment patch-file.log

and on primary ROM once ramdisk updated and hit reboot it's keep looping the reboot at first screen itself. I have to go back to recovery and flash the kernel again to start the ROM.

Thanks for help
[Galaxy S 4 i9505 Original Android Development] cruor.am:
Hi [MENTION=4277844]chenxiaolong[/MENTION]! Sorry for the late answer, but I've been very busy. I'd really want to give you log zip but now I'm not able to get log, getlogs.zip doesn't save on my internal memory any zip. Really weird. I've just tried several times, but no luck. What can I do?
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
I'm sorry to bother you again, but the ROMs I gave in that post were all using CN (Chinese) base which is quite a bit different from the ROW (rest of the world) base. Do you think they can have different partitions and formats??

If so, please see this ROM too.

It is Lenovo's stock Vibe UI 2.5 (Android 4.4) with ROW base: https://cloud.mail.ru/public/b0622667044d/S650_ROW_S215_140714.rar

Thanks again. [emoji5]
[Galaxy S 4 i9505 Original Android Development] Ather:
does this app suport htc one m8?
[Galaxy S 4 i9505 Original Android Development] omnifarious:
Are you able to add support for the d2xar (sch-r530x)? It is a generic variant of the US CDMA Samsung Galaxy S III. It's hardware closely resembles that of the d2vzw (Verizon variant sch-i535) but I've tested different roms and kernels (AOSP and TW) and they run fine. d2lte, d2att (sgh-i747), d2spr (sph-l710), d2mtr, d2cri, d2tmo (sgh-t999), d2usc (sch-r530).

International roms, however, will brick the device. Here is the log I pulled.

I'm also trying to install cm 12.1 to multi-slot-1 on my T-Mobile LG G2 (lg-d801) and I'm getting an error.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ever since Lollipop, most AOSP ROMs are installed by a system image (system.img.dat in the zip). If they aren't extracted to a file equal to or bigger in size as the system partition, then they can't be mounted to copy files out of them. If your system partition is 2.8GB, it will need to create a 2.8GB temporary file on the data partition.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The app is unable to write to the external SD. Are you using a Lollipop TW ROM? If so, did you apply the fix that allows 3rd party apps to write to the SD card? (eg. https://play.google.com/store/apps/details?id=nextapp.sdfix)

EDIT: Btw, Xposed is throwing a bunch of errors on your device, though I don't know if it's related to the issue.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, that's weird. Does your recovery give any error messages? Are you using the latest GetLogs zip? (https://snapshots.noobdev.io/misc/getlogs/GetLogs-20150827.zip)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
That means your recovery doesn't support /proc/last_kmsg. That's quite annoying because there's no way to see what went wrong. I'm not really sure what I can do without the logs :(

The Note 4 actually had the same issue of the recovery not supporting /proc/last_kmsg. I had to ask our TWRP maintainer to rebuild the recovery with support for it.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yes, absolutely! I'm currently running the stock TW Note 4 ROM from the external SD.
[Galaxy S 4 i9505 Original Android Development] Ather:
thank you for your reply, i tried to install the new Note 5 port and it booted up, after restarting it stuck in a bootloop, coudnt switch to primary or any other rom, had to wipe my Device and reinstall the primary rom... could the included kernel in the rom cause this?
[Galaxy S 4 i9505 Original Android Development] 54NJ41:
thanks a lot for your replay. i will also request the TWRP devs for /proc/last_kmsg support. hope it will be fixed soon. thanks again for your time.
[Galaxy S 4 i9505 Original Android Development] v00d007:
Well, in the meantime I free'd up more than 4.5GB on the data part. but I still can't get a cm12.1 nightly successfully do the 1st boot. I also noticed that the very 1st boot screen hangs very long (aprox. 25s), that is strange too. Other roms like cm11 or cm12.1 optimized work. What is going on here, has the cm12.1 team newly changed something in the install script that the patcher destroys?
[Galaxy S 4 i9505 Original Android Development] cruor.am:
Yes I'm using the latest getlogs zip and TWRP recovery doesn't give me any error message. It says logs have been successfully copied in log folder.
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
Android 4.4.2 stock (also stock kernel) rooted sm-n9005.

Patching kernel works fine but after, to make the changes working, the phone doesn't boot.. it stucks in "samsung galaxy note 3"

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] xdasree:
Thanks, patching the file part worked. ( It's on TW rom as secondary)

Problem with Primary rom which is CM12.1, Once ramdisk updated and hit reboot. that's it, it is keep looping very initial screen as mentioned before have to flash kernel again to get into primary rom.

attached ramdisk-update log which might helpful.

View attachment ramdisk-update.log

Thank you again.
[Galaxy S 4 i9505 Original Android Development] ItzShadowz:
Is it possible that you could add support for CM12.1 alpha for LG G4 H815 located in this thread? Dual boot patcher doesn't recognise it as an actual ROM and I'm not able to switch.

http://xdaforums.com/g4/development/h811-h815-blisspop-cyanogenmod-12-1-t3185593

it's the build located near the bottom of the download page with h815 on the end (with a date of 2015-9-15). Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Unfortunately, the CN and ROW bases are both using the same type of partition layout (EMMC). :(
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Darn, looks like my zip might be broken then. Could you try flashing the GetLogs zip and then use TWRP's built-in Advanced -> Copy Log to SD and send me /sdcard/recovery.log? That should at least help me figure out why GetLogs doesn't work.
[Galaxy S 4 i9505 Original Android Development] todivefor:
I have used GetLogs-20150827.zip several times with no problem.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks, I'll give it a try on my S4. Was it a clean or dirty flash?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Starting from 8.0.0.r1711.ge036e99, the patcher will fall back to the external SD if there is not enough space on /data to create a temporary image. In other words, if you're low on space and have an external SD, this will no longer happen:
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
Thanks! How's the backup and restore feature doing? And any progress in data on external SD card!?

Thanks in advance!!!
[Galaxy S 4 i9505 Original Android Development] physwizz:
I just got my galaxy tab s back from the repairer and tried to set up dual boot patcher with tw as the primary.

I keep getting a fail to patch message.

Log file below

http://dl.dropboxusercontent.com/1/view/ihl736rvh52orlc/patch-file.log
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Lollipop TouchWiz does not allow 3rd party apps (file managers, etc.) to write to the external SD by default. You'll need to use an app like this to fix that: https://play.google.com/store/apps/details?id=nextapp.sdfix
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
What do you mean by not being able to switch ROMs? How were you trying to switch ROMs?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you check if your recovery has /proc/last_kmsg? On TWRP, you can check from Advanced -> File Manager. From what I've heard from several people, it seems that the Note 3 does not save the last kernel log. It makes debugging boot loops extremely difficult as there's no way to know what caused the reboot without that log.
[Galaxy S 4 i9505 Original Android Development] v00d007:
That was a clean one. But atm it doesn't matter if I do a clean or dirty flash, no cm12.1/optim. will install correctly anymore. I really can't find the reason for that, I never had those problems before. Also no matter of flashed with app or cwm. I also tried older builds like 1212, all do the same. What can be responsible for that?? Any leftovers of older builds or what?

---------- Post added at 08:02 AM ---------- Previous post was at 07:45 AM ----------

Backup&Restore is developed by [MENTION=3145598]rlorange[/MENTION], you gotta ask him. My workaround, 'cause restoring backups from ext sd can't restore the system partition, is to copy it temporarily to internal sd, from where restoring works.
[Galaxy S 4 i9505 Original Android Development] physwizz:
They put tw4.4.2 on it when they repaired it and I was going to keep it as a primary.
[Galaxy S 4 i9505 Original Android Development] cantenna:
Awesome app , thank you. I can only share all apps and data across two ROMs though, not individual, should I be trying another nightly? My phone is jflte gs4. I would share all but goggle play services crashes. Primary is lean touch wiz 5.0.1 and secondary CM 5.1.1
[Galaxy S 4 i9505 Original Android Development] physwizz:
Is this also for KitKat tw?

Edit: It looks like it's working. Just flashing now.

It let me patch the zip file and it looked like it tried but failed to flash the zip file for both secondary and extSD.
[Galaxy S 4 i9505 Original Android Development] Ather:
I meant switching the rom from the recovery using the utilities zip file, it wont even show my Primary Rom, just the other CM rom i had installed on ext-slot2
[Galaxy S 4 i9505 Original Android Development] xdasree:
It finally worked after trying different kernels. But, I don't see /proc/last_kmsg though.
[Galaxy S 4 i9505 Original Android Development] noobiedev83:
Yeah I know about the rlorange app but I remember that the developer is working in adding this feature to the app but don't know what happen with it :(
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
What do you mean when you say the patcher doesn't recognize it as an actual ROM? Do you mean that it installs, but isn't listed in the app?
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

Dear Mr Chen,

do you think that it's possible that a previous (lots of builds ago) activated 1st rom app sharing option is causing all my problems?

- cm12.1 installs but won't finish 1st boot

- cm12.1 optimised (no system.img) always aborts with "failed to run sbin/***.sh" (see screenshot)

- the folder data/multiboot/dual/data/users/0 shows up all apps of my 1st rom right after installing cm12.1 cleanly

If I really wanted to get rid of all app sharing relicts, what all would I have to delete?
[Galaxy S 4 i9505 Original Android Development] abdallah.ibbi:
[MENTION=4277844]chenxiaolong[/MENTION]

Dear chen please help can't dualboot miui v7 with my first rom sixperience for g900f

Galaxy s5 g900f
[Galaxy S 4 i9505 Original Android Development] royredman:
Hey, I love this dualboot patcher and I have used it for the longest time on my galaxy s4. My question is, does this work for the nexus 6 also? If so, which setting do I choose to patch the roms? Thanks for all the awesome work!! You are amazing!!
[Galaxy S 4 i9505 Original Android Development] ItzShadowz:
Yeah! Sorry I didn't make it very clear. As well as what you said, the secondary ROM also isn't listed in dualbootutilities.zip
[Galaxy S 4 i9505 Original Android Development] physwizz:
Finally got it to work for SlimLP on ExtSD by flashing it over the top of Blisspop.

Still trying to get lollipop tw to work as ExtSD.

Thank for a great app
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
To get rid of all the app sharing stuff, you can either edit or delete the config.json file in /sdcard/MultiBoot/[ROM ID]/config.json. If you open the file in a text editor, it will be very obvious if app sharing is enabled.

The reason CM12.1 optimized fails to install is because its kernel is way bigger than other kernels. It used to work before I added support for extsd-slots because with the multiboot files added, everything just barely fit. With extsd-slot support, I needed to add mount.exfat to the kernel (ramdisk) to allow exFAT-formatted SD cards to work. That's what made the kernel slighly too big.

As for why Optimized CM12.1's kernel is so big, it's because they include a lot of small unused binaries in the ramdisk. But they add up and make the kernel 3.6MB bigger than the official CM12.1 kernel:

6.2M cm-12.1-20150918-NIGHTLY-jfltetmo/boot.img
9.6M OptimizedCM-12.1-20150817-jflte/boot.img

I could have the patcher remove these unused binaries if you want :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
For those who were having boot loop and boot hanging issues:

Please try patching with 8.0.0.r1721.g637982d and grabbing the logs with GetLogs-20150919.zip (available at https://snapshots.noobdev.io/). This new version added a new method of dumping the kernel log because so many devices seem to be missing /proc/last_kmsg. If this new log dumping method works, I'll be able to see what's causing the boot issues.

Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! :highfive:

I have not added support for the Nexus 6 because it's one of the few devices encrypted by default and DualBootPatcher does not support encryption right now. If I add support for the Nexus 6, it will only work with ROMs/kernels that don't force encryption. Do you think it's worthwhile to add support given this limitation? If so, I'm happy to add support for it :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I haven't seen that error in a while. Could you flash the GetLogs zip (from https://snapshots.noobdev.io) and send me the logs in /sdcard/logs/?
[Galaxy S 4 i9505 Original Android Development] royredman:
Honestly, you have spent a lot of time working on this, and I can't imagine how many other things you are working on right now with that patcher, and I don't know how much work you would have to put in to add support, but I think that would be awesome especially with the insanely awesome app sharing you have set up (saves alot of space).

Honestly, I wouldn't care if encryption wasn't supported as I rarely use the stock rom/kernel.

If it isn't a huge issue doing this, it would be awesome to have this option, but if it is, I totally understand. Keep on rocking!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
.

Done! 8.0.0.r1725.gbaa9105 now supports d2att, d2can, d2cri, d2ltetmo, d2mtr, d2spi, d2spr, d2tfnspr, d2tfnvzw, d2tmo, d2usc, d2vmu, d2vzw, and d2xar as they all have the same partition table. It also recognizes "d801" now, so the install should no longer fail on your G2.
[Galaxy S 4 i9505 Original Android Development] royredman:
(ignore message)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r1727.g63a9023 :laugh:
[Galaxy S 4 i9505 Original Android Development] v00d007:
Well, thanks for this info's. I at least managed to get cm12.1-0916-nightly installed after doing a rom update on 1st rom (Echoe v51). That must have fixed something. But i still got the issue that the first boot screen hangs aprox 30 sec(!) every time when booting cm. Never had that with any rom before. Any idea?
[Galaxy S 4 i9505 Original Android Development] royredman:
awesome!! Thanks man!! :d :d
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hmm, I'll do some testing myself to see if I run into the 30 second hang issue. You said you installed to secondary ("dual") right? I know extsd-slots can be slow on the S4, but ROMs installed to the internal memory should never do this.

EDIT: By hanging at the first boot screen, do you mean the Samsung logo?
[Galaxy S 4 i9505 Original Android Development] cruor.am:
Hi [MENTION=4277844]chenxiaolong[/MENTION]!

Good and bad news. Multiboot isn't working as before, but with your new getlogs zip now I can take logs again. Here the new logs attached. Thanks for your support.
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
Hlte android 4.4.2 stock as primary after patching kernel the phone stucks in samsung galaxy galaxy note 3 logo

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] v00d007:
Yes, Dual Slot.

Yes, Samsung logo screen.

Isn't there anything that needs to be cleaned up or something, the boot part. or the preload? ...before I do a major full wipe...
[Galaxy S 4 i9505 Original Android Development] qwerfaseeh:
it is mentioned in the post that all variants of s4 are supported but on my e330s which is i9506 it is not supported. need help
[Galaxy S 4 i9505 Original Android Development] todivefor:
I see in the patcher that there is support for the Nexus 7 (Asus 2013). Are partitions the same for Nexus 7 (grouper 2012 - wifi) - attached. Is it supported? If not, can it be?
[Galaxy S 4 i9505 Original Android Development] ItzShadowz:
Here it is: https://drive.google.com/file/d/0B1dCuNsnNoHcSXVuSERPZGlNcnM/view?usp=sharing

By the way, did you get my PM with the log about the ramdisk update bootloop issue?
[Galaxy S 4 i9505 Original Android Development] royredman:
For the nexus 6, does this support only lollipop roms right now? Or does it also support android M/6.0 roms?
[Galaxy S 4 i9505 Original Android Development] v00d007:
[MENTION=4277844]chenxiaolong[/MENTION]

Yep, me too, forgot to mention.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Looks like the new logging method works. This is the important section from the kernel log.

<7>[ 4.059626] [0: init: 1] mbtool: Attempting to mount /dev/block/platform/msm_sdcc.1/by-name/system (ext4) at /raw/system
<6>[ 4.061596] [0: kworker/0:1: 24] [ssp] bootmode 121 retry: 0
<3>[ 4.149785] [0: init: 1] printing data of superblock-bh
<3>[ 4.149891] [0: init: 1] As EXT4-fs error, printing data in hex
<3>[ 4.149950] [0: init: 1] [partition info] s_id : mmcblk0p23, start block# : 376832
<3>[ 4.150055] [0: init: 1] dump block# : 1, start offset(byte) :
<3>[ 4.150159] [0: init: 1] 0, length(byte) : 1024
<3>[ 4.150269] [0: init: 1] -------------------------------------------------
...
<3>[ 4.157551] [0: init: 1] ---------------------------------------------------
<3>[ 4.157656] [0: init: 1] EXT4-fs (mmcblk0p23): VFS: Can't find ext4 filesystem
<3>[ 4.157873] [0: init: 1] mbtool: Failed to mount /dev/block/platform/msm_sdcc.1/by-name/system (ext4) at /raw/system: Invalid argument
<3>[ 4.157989] [0: init: 1] mbtool: Failed to mount /raw/system
<3>[ 4.158088] [0: init: 1] mbtool: Failed to mount fstab
<4>[ 4.158200] [0: init: 1] mbtool: --- EMERGENCY REBOOT FROM MBTOOL ---

The ROM is trying to mount /system as ext4, but it's failing either because the partition is not formatted as ext4 or the partition is corrupted. Is your system partition formatted as F2FS?