yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] Casual Gamer:
Stuck on BootAnimation

Hello [MENTION=4277844]chenxiaolong[/MENTION] I have a problem with the rom "Resurrection Remix v 5.58 for GT-I9505".

I patch the rom for slot-date. When I flash in recovery and restart the phone, the screen stays on animation boot without end.

The problem will be the kernel of the rom?

Please answer me.

This is the log..
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Out of curiosity I tried to install cm13 alpha for klte on data slot but it did not work : script aborted: system partition has unexpected contents after OTA update
[Galaxy S 4 i9505 Original Android Development] Tom-Helge:
Here is the 'GetLogs' file from my Galaxy S6 edge+ (SM-G928F).

https://dl.dropboxusercontent.com/u/7309753/Apps/20151102.160144.tar
[Galaxy S 4 i9505 Original Android Development] ktm_91:
This is exactly the same problem I presented a few pages ago, but no solutions by now.. I get this loop for every patched ROM with original cm 12.1 kernel

What device and primary ROM have you got?
[Galaxy S 4 i9505 Original Android Development] Casual Gamer:
I have a samsung galaxy s4 GT- I9505 . The primary ROM is the TouchWiz 4.4.2 KitKat
[Galaxy S 4 i9505 Original Android Development] ktm_91:
Well, so you are exactly in my situation.. Let's stay awaiting for news..
[Galaxy S 4 i9505 Original Android Development] mabuan:
When reboot to 2nd rom, it has just shown "Samsung Galaxy Note 4 Power by Android" and at left top of screen is red text "kernel is not seandroid enforcing", loop at this stage. I attached log file, please see and help me. My phone is N910L, used Sixperience N5 Port for N4 as primary, Stockrider kernel 2.5.4, miui 5.10.23 as secondary. Thank you!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION] Hi

I'm the guy with the Lenovo K3 Note who helped you (a little) to add support for it.

Well now I was trying to flash a ROM for the first time, and it doesn't work and fails after "Patching image unconditionally"

Can you please tell me what's wrong?

I'm attaching the multiboot.log

The ROM was Flyme OS, BTW (if it may be of any use, here's the link to it: https://cloud.mail.ru/public/4pFvdmU7gtdX/Lenovo_K3note_Flyme_4.5.6_Final.zip)
[Galaxy S 4 i9505 Original Android Development] GioBasi:
it is log created by Getlogs folder. and how to get log after flashing from recovery ? I should create or it's somewhere on internal storage?
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
I:=> product model: 'K50'
I:=> using device id: 'K50'

.....

[MultiBoot] Patched zip is for:
[MultiBoot] - K50a40
[MultiBoot] - K50t5
[MultiBoot] - aio_otfp
[MultiBoot] This device is 'K50'

is this rom compatible to your device? I don't know if your device is supported because the patch was different. is you primary rom ported from other device? if it is you have to edit your /system/build.prop
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
It's for the same phone as mine but with different model no.

I've edited the updater-script for that
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
okay. so your device is K50? or K50a40. you might wanna change your system/build.prop ro.patcher.device.
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
My device is K50a40
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
OmniROM 6.0 marshmallow won't boot after enabeling data sharing. Log is attached
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
okay. that's it. edit your system/build.prop either add or edit this line on your primary rom. restart and repatch the zip see if that works for you.

ro.patcher.device=K50a40

---------- Post added at 07:43 AM ---------- Previous post was at 07:33 AM ----------

did you update the ramdisk on both roms?
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
It wasn't the problem [emoji17]

I've flashed the official ROM of this device which has made it K50-T5(which was model no. In the ROMs) from K50a40 .. (See attached screenshots)

But it's still not working [emoji21]

It's still fails at the same position..
[Galaxy S 4 i9505 Original Android Development] remowrx:
deleted
[Galaxy S 4 i9505 Original Android Development] crazyraiga:
i dont understand.

You should put there the original device name. then repatched the file. see if that works. im confuse with k50,k50a40,k50-t5. use the orig.

your log says no space left. you need atleast 2.5gb on your internal if you are going to use dual, data slot... use extsd it might work.
[Galaxy S 4 i9505 Original Android Development] dave7802:
Has Op or [MENTION=4277844]chenxiaolong[/MENTION] been asked about Linux Distros?

Would there be much / alot of work to run something like Arch as a dual boot?

My only solution to do this so far, is to install CM, change kernel, then install Arch ontop.

While this works, it seriously slows and kills the battery (Am running a phone OS and Part linux side by side)

Anyway to just get Unix, I would love to be able to turn my phone on, and boot between Arch and Android :)

Or Arch, CM and TW :)

(I only say arch, as its all i use, and easy to build up from nothing with complete customisation and ARM support.
[Galaxy S 4 i9505 Original Android Development] piskor:
Hi [MENTION=4277844]chenxiaolong[/MENTION]

Could you please add device Samsung Galaxy S4 mini LTE, GT-i9195, serranoltexx to the patcher

Thanks in advance
[Galaxy S 4 i9505 Original Android Development] v00d007:
Although not officially supported it works with the S4 mini. I had that crappy phone myself and set up dual boot without problems. Just choose the 'S4 jflte' profile when patching.
[Galaxy S 4 i9505 Original Android Development] piskor:
[MENTION=5749514]v00d007[/MENTION]

I know that. I saw your posts in the thread. Thanks for info.

Without official support i cannot set kernel for my Primary rom. I want to stick with AICP rom as my primary rom. I am flashing almost all nightly builds. Without official support I would have to patch every flashed zip.

Am I right or can i live without official support in this case?
[Galaxy S 4 i9505 Original Android Development] v00d007:
I'm not sure what you mean. Primary roms can always be installed without patching. If setting rom kernel doesn't work for some reason you always got the option to flash the kernel with recovery and the kernel is set. But my experiences with that phone + dualboot patcher are quite outdated, I'm not really sure if all still works with post 436 builds...
[Galaxy S 4 i9505 Original Android Development] piskor:
Thank you for explanation [MENTION=5749514]v00d007[/MENTION]

I will try to test, what you say.

After all, would be nice to see native support for our device in a patcher.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Oops, I completely forgot about that! I've uploaded a new version of the GetLogs zip that arch-independent, so it should work on your x86 tablet.

Btw, the log TWRP saves is somewhat useful, but does not contain enough information for debugging purposes.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
/sdcard/logs and /data/media/0/log/ should be the same paths. I'm not sure why it wouldn't be the case for you.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Can you send me a link to the ROM's thread and link to the exact version of the ROM you used? This might take quite a bit of debugging to fix. The ROM's SELinux policy is blocking mbtool from communicating with installd, which prevents dexopt/dex2oat (dalvik-cache generation) from running. That's why it's stuck on the boot animation.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION] thanks a lot for including a getlogs.zip that's arch independent, find attached my log for tab 3 p5200 3G model!

Thanks again for your hardworking and plz add my device to list of supported thank you so much!!

https://www.dropbox.com/s/2dvx1q4jo2qfjpl/20151105.155144.tar?dl=0
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r1880.g25d7b14 :)
[Galaxy S 4 i9505 Original Android Development] coldgin_:
Hi !

now you have, just pick "S4 mini / Duos" from the device's combo selection and that's just fine, because them (regular 3g and duos) have the exact same /dev/block structure than your LTE version, so you won't have any problems, I mean, we have official support now ... but the problems can come from any other places as Murphy says [emoji14] ... you can just trust me and give it a try ;) ... or first have a look inside the "serrano3gxx" commit for the today's release, here:

https://github.com/chenxiaolong/DualBootPatcher/commit/a8c29999e69eef59a0a5755c695fb49830f9cee4

and verify by yourself that your phone's partition table matches the serrano3g's one.

Regards.

EDIT: Now there's native support for Serrano LTE . Good Job Dev !!!!!!!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Could you try again with 8.0.0.r1881.g55d28d6? I made some changes that may fix this issue.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Your recovery is reporting the device codename as "K50" instead of "K50a40". I've added it to the list of valid codenames in 55d28d6..1f3c30c :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
What do you mean by it not booting? Is it getting stuck on the ROM animation? The manufacturer logo? I can't seem to find anything wrong in the log files.

Anyway, data sharing can be manually disabled by setting individual: "false" in /sdcard/MultiBoot/[Your ROM]/config.json or by deleting that config file completely.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'm very, very interested in this! I've never attempted running Arch on my phone (though it powers my laptop, 3 servers, HTPC, and Raspberry Pi :D). Do you have a link describing the process? Since you mentioned that you need a custom kernel, does Arch run natively on the phone or inside a chroot?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
8.0.0.r1883.g9e60959 :)
[Galaxy S 4 i9505 Original Android Development] Casual Gamer:
Here is the link of the ROM thread: http://xdaforums.com/galaxy-s4/i9505-develop/rom-resurrection-lollipop-v5-5-5-t3195202

This is the link for the ROM: https://www.androidfilehost.com/?fid=24052804347841577

The ROM is "Resurrection Lollipop v5.5.8"
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! Added support in 8.0.0.r1885.g19e23d4. Please let me know if you run into any issues as you are the first person to try this on a device with an x86 chipset :)
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
I'll defenately do that,once the the file is uploaded I'll surely test and give feed back,thank you so much for considering my/our device!
[Galaxy S 4 i9505 Original Android Development] coldgin_:
Hi !

that concept was implemented by several programmers and contributors here at XDA, for the Asus Transformer Tablet. This is the main thread:

http://xdaforums.com/showthread.php?t=2387133

The main idea is having a dual boot device where you can have Android by one side, and a separate Linux armf distro by the other. They share the kernel (not the ramdisk of course) and when you choose to boot into "pure Linux" it runs in native mode, not chrooted, and not Android running aside. And yes, even with GUI !!

Its a very interesting project, it's still alive and It actually works with several armf distros, including Arch .

I've got it running in my tablet by the way :)

Hope it helps, it's a very good material for Linux maniacs ;) and I certainly believe that you will find the way to adapt the idea for your own device.

Regards!
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION] from the x86 arch tester(tab 3 10.1) I've encountered errors during install from recovery.

1.PATCHER: works well, and able to set kernel for primary ROM!

2.DualBootUtilities-8.0.0.r1885 gives an error about not being able to update script, same error I got while attempting to flash the getlogs.zip before it was made arch independent!

Attachment: https://www.dropbox.com/s/uxa676yja..._error from utilities,AROMA cant run.tar?dl=0

3.CM 12.1 based 5.1.1 installs well and script properly updated but gives boot loops, system reboots back into recovery every time!!

Attachment: https://www.dropbox.com/s/72b33acx99s7m25/20151105.205417_boot loop after CM12.1 flash.tar?dl=0

4.AOSP 6.0 also gives error seen in#2 of this feedback, but this is android M and have seen same error also with CM13 on note 3 maybe compatibility issues to date!

Attachment: https://www.dropbox.com/s/t8gepo41plh1na9/20151105.204822_error AOSP 6 cant instsll.tar?dl=0

See also attachment below after failing to run the DualBootUtilities-8.0.0.r1885.zip

Currently can't boot into any system, the bootUtulitities were gonna help me select OS I want to use without restoring NANDROID!!

Plz help where possible!

Thanks in advance!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I haven't had a chance to look at anything yet, but to manually switch ROMs, all you need to do is (from TWRP): Tap Install -> Tap "Images" (Bottom right corner) -> Flash /sdcard/MultiBoot/[Your ROM]/boot.img. There's no need to restore an entire nandroid :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I just blocked a few hundred IPs and subnets that were brute forcing passwords and/or port scanning https://snapshots.noobdev.io/. If you are no longer able to access the site, please make the devices on your network are free of malware and let me know so I can unblock the IP.
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
I have a OnePlus One.

I installed OmniRom 6.0 on data-slot and it booted fine. After i've set everything up, installed dual boot patcher and tested ROM switching (worked fine) i enabled app sharing in omnirom chose whatsapp and only shared data not the apk. Then i rebooted and it rebooted to recovery. In recovery i flashed boot.img from omniroms multiboot folder and it booted back up. Checked app sharing settings and saw it was disabled. Reenabled it and again shared whatsapp data, rebooted and ended up in recovery again. There i immediately flashed the getlogs.zip

By the way when i tried to flash a patched AOSParadox Marshmallow Rom which comes in system.image.new.dat format resulted in "could not execute updater script" or something the like. flashing the patched omnirom marshmallow build (no image, individual files) all went fine. Which logs do you need? Is the multiboot.log enough?

And many thanks again for taking care of our problems. You're a really great dev.
[Galaxy S 4 i9505 Original Android Development] dave7802:
Runs well in Chroot works well on CM kernel actually

I mention Kernel, as i have my own complied version with some additional drivers for external wifi adaptors and modifications.

I was trying to make it run Natively on the phone, but i have no way to get the device to boot Grub, And thus the question about any support for any Unix booting.

I am not familiar with how android boots from its BootLoader, to manipulate the Unix files to boot.

If its something you are interested in, I would be more than happy with work with you on the Linux side, if there is a way to boot from a blank image / shell almost, am happy to built up from there

Although my home is Arch, i would be more comfortable working on this Distro, but any changes and modifications can easily be replicated on another Distro.

If you can help me get a Boot method sorted, I can do the rest and submit whats required etc to yourself for testing / submitting and releasing.

EDITED************* Additional info i missed *********

Thanks very much for this, Great post. This is a great starting ground.
[Galaxy S 4 i9505 Original Android Development] Casual Gamer:
Hi [MENTION=4277844]chenxiaolong[/MENTION], you have fixed the ROM "Resurrection Remix v5.58 for GT-I9505"?
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
It still doesn't work :(:(

It still fails at Patching image unconditionally.. But there seems to be some progress (at least to me)

Here's the new log

BTW, why is log showing info about the CM12.1?!?
[Galaxy S 4 i9505 Original Android Development] corncobman:
I just tried flashing a couple of roms that I have patched using the latest patcher (1885)

Both failed with the same messages

Failed to determine system path

Failed to flash zip file

Destroying chroot environment

Failed to restore boot partition

E:Error executing updater binary in zip '...'

Logs file is attached.

Device is i9305 (m3), TWRP v2.8.5.0

ROMs I tried were Blisspop and Cyanide
[Galaxy S 4 i9505 Original Android Development] coldgin_:
Hi !

I think you have to forget about how to manipulate the bootloader, mainly because it's closed source in 99% of devices, and impossible to unlock in several ones. That's the hard (almost impossible?) way.

So the key is Kexec !! https://en.wikipedia.org/wiki/Kexec

That's the way it was implemented in the Transformer Tablet, described in the thread I posted yesterday.

Regards !
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
[MENTION=4277844]chenxiaolong[/MENTION]

Dualboot patcher: v1885

Device: SM-N9005 (hlte)

Rom: CyanogenMod 11 Official installed in data-slot-cm11

Problem: Device stucks in kernel logo (where there is written "kernel is not in selinux enforcing" in red)

Log: https://drive.google.com/file/d/0B2ftBoBlBHTIUW9EVUVEdFJrcXM/view?usp=docslist_api

Ps: Could you add support for i9300 (Samsung Galaxy S3 International)?
[Galaxy S 4 i9505 Original Android Development] GioBasi:
thank you , works prefect for any kind of zip file.

even for cm 11 to ext_sd_slot while cm 12.1 as primary. before wasn't able to do that. just in dual patcher from primary writen unknown version and build for ex_sd rom but everything works without problem.

I have just one question for exsd rom when I installing any apps, are using internal storage /data. what I must do to install all apps for ex_sd_rom on exsd?

thank you again
[Galaxy S 4 i9505 Original Android Development] piskor:
Awsome :) Many, many thanks .:good:

Works with AICP rom as primary, Blisspop and Resurrection Remix on extsd slots with Samsung Galaxy S4 Mini, GT-i9195, serranoltexx
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Great!

Unfortunately, there's nothing I can do about this (for the moment) because AROMA has no support for any architecture besides ARMv7. (The new libaroma should, but I don't know if it's still in active development.)

This is good! We're getting somewhere now. It's failing because the paths to the partitions in /dev are missing. It could be that it needs another second for the kernel to detect the partitions or maybe there's a bug in my code. Would you mind trying again with 8.0.0.r1886.g5764cb5? (Testing one ROM is enough) It doesn't fix anything, but should log more information to help me pin down this issue.

Yes, this is the same issue that everyone has been encountering with Android 6.0-based ROMs. I have not had the chance to look into this yet as there are no Marshmallow ROMs for the Note 4.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION] I'll don't mind at all well test as soon as r1886 is uploaded!!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Pardon my language, but I'm a dumbass lol. I think I figured out why it's not working for you. Give me a couple hours so I can give this fix a try :)
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
All the time you need mate,thanks for your time champ!!
[Galaxy S 4 i9505 Original Android Development] jcadduono:
Hello, could you please add support for kernels/ramdisks compressed with `xz --check=crc32 --lzma2=dict=2MiB`?

ex.

CONFIG_KERNEL_XZ=y

CONFIG_RD_XZ=y

Some users of my kernel have been saying that DualBootPatcher doesn't work with my kernel, and that's probably why.

As much as I'd like to submit a pull request, I'm a little lost in your sources and can't figure out where anything goes lol. :(

They were saying they were getting an error like "Invalid archive format"
[Galaxy S 4 i9505 Original Android Development] frequentc:
[MENTION=4277844]chenxiaolong[/MENTION]

Just wanted to mention that I'm also interested in seeing support for this. The "Invalid archive format" error message appears when you try to patch the kernel. This is on a Samsung Galaxy Note 3 (N900T).

Here's a link to the kernel he's talking about: idleKernel download (and here's the xda thread).

Thanks for all your work.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
[MENTION=5672995]jcadduono[/MENTION] [MENTION=4710301]frequentc[/MENTION]

I'm using the libarchive (https://github.com/libarchive/libarchive) library, so it was just a simple one-liner to enable xz support :) It should work in 8.0.0.r1903.g6edead0 now.

https://github.com/chenxiaolong/DualBootPatcher/commit/d2ee667eda1f599408ae0f8f5bd9cbb03259300f

https://github.com/chenxiaolong/DualBootPatcher/commit/7a234d124a818686321aa236658cbf0769e209ad
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hopefully should be fixed in 8.0.0.r1903.g6edead0 (crossing my fingers!)

[MENTION=3733477]mabuan[/MENTION]: This build may also fix the kernel crash that caused the boot loops on your device, but I'm not 100% sure about that.
[Galaxy S 4 i9505 Original Android Development] frequentc:
That fixed it. Thanks a lot.
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
[MENTION=4277844]chenxiaolong[/MENTION] from the x86 arch tester,

well done mate, you've done it!! It's perfectly working !!

Thanks a lot chief!!
[Galaxy S 4 i9505 Original Android Development] mabuan:
Thank you! I will try and reply soon. Thank you so much!
[Galaxy S 4 i9505 Original Android Development] TheDarkKnight:
[MENTION=4277844]chenxiaolong[/MENTION]

Please look into my case
[Galaxy S 4 i9505 Original Android Development] MatrixDJ96:
[MENTION=4277844]chenxiaolong[/MENTION]

Dualboot patcher: v1903

Device: SM-N9005 (hlte)

Rom: CyanogenMod 11 Official imstalled in data-slot-cm11

Problem: Device stucks in kernel logo (where there is written "kernel is not in selinux enforcing" in red)

Log: https://drive.google.com/file/d/0B2ftBoBlBHTIc1JVbEhKZFYzNXM/view?usp=docslist_api

Ps: Could you add support for i9300 (Samsung Galaxy S3 International)?

Inviato dal mio SM-N9005 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] dave7802:
Beautiful thanks, I have been reading the links you sent over, and very informative thanks, the kexec is defo the way forward to accomplish this.

I have alot of researching and work ahead of me for this.

Depending on how its implemented or done, it may be a new thread, or ill sumbit the details to OP and take it from there.

Thanks again for the links, good point in the right direction :)
[Galaxy S 4 i9505 Original Android Development] mabuan:
I'm sorry to say that still has error "kernel is not seandroid enforcing", couldn't boot to secondary rom.
[Galaxy S 4 i9505 Original Android Development] bilbonotry:
Multirom by Tassadar (originally on nexus 7 but ported on other devices) uses that feature
[Galaxy S 4 i9505 Original Android Development] AM.8:
Work it with Note 3 too or only on Galaxy s4??

Thanks in advance

Gesendet von meinem SM-N920C mit Tapatalk
[Galaxy S 4 i9505 Original Android Development] danerrickcuba@gmail.com:
It works with all note 3 models and dozens more other brands , being using it fur many months, just choose your model in the device tree
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ahh okay, this is a bug with the ROM actually. It expects the device name to be "aio_otfp", but your recovery is reporting "K50". You'll have to remove the following line from META-INF/com/google/android/updater-script in the zip file (and let the developer know of this problem):

getprop("ro.product.device") == "aio_otfp" || abort("This package is for \"aio_otfp\" devices; this is a \"" + getprop("ro.product.device") + "\".");