yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] sronweb:
Hello, the error for CM11 occurs when installing.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Omg thanks man!! You work supa fast!

EDIT: Check out this log. https://docs.google.com/file/d/0B1d_Il6yTO73M0FOTk4zYzk2dEU/edit?usp=docslist_api [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ahh ok, loki needs the aboot partition to work. Should be fixed in 8.0.0.r627.g808ec1b :)
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Again with the magic. Lets see. In the midst of changing my twrp splash screen lmao

EDIT: More progress visually but here is the log. https://drive.google.com/file/d/0B1d_Il6yTO73OU83T0NrYjVMR1E/view?usp=sharing

[MENTION=4277844]chenxiaolong[/MENTION] It seems like its not finding aboot.IMG?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Stupid typo on my side lol :D Should (hopefully) be fixed in 8.0.0.r628.g7976fbd.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I'll do some more testing when I get home, but "cm-11-20150118-NIGHTLY-jflte.zip" seems to install fine for me:
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
And testing now
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Server is still building it ;) https://jenkins.cxl.epac.to/job/DualBoot_Patcher/345/console
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
noticed. Patching now though ?
[Galaxy S 4 i9505 Original Android Development] sronweb:
I have just patched with r628 both CM12 and CM11. I will install soon.

I noticed that using last patcher I miss the installed roms in the "Choose rom" menu but if I install r623 I have the 3 roms installed visible for the selection
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] it all flashes now but says the boot partition was modified
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Yeah, at the moment, the new patchers (newer than ~r600) are incompatible with ROMs that were patched before because many paths have changed. For example:

/system/dual -> /system/multiboot/dual
/cache/multi-slot-1/system -> /cache/multiboot/multi-slot-1/system
/data/media/0/MultiKernels/dual.img -> /data/media/0/MultiBoot/dual/boot.img
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Are you talking about the "Boot partition was modified. Setting kernel" message? That one is normal when you flash a ROM.

EDIT: Just realized that ls980 needs loki. 8.0.0.r633.g22e3741 contains a few fixes for loki (both LG and Samsung).
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Testing now.
[Galaxy S 4 i9505 Original Android Development] seijisandrei:
As much as I would love to test, my I9505 is my daily phone, and it's a little inconvenient for me to always do backups and restores if patching and booting fails. I guess I am not of a big help here. But I would like to thank the developer for spending his valuable time and braincells for this MOD. I guess I have to wait for a very stable version for me to patch 2 official lollipop roms. This mod is great!
[Galaxy S 4 i9505 Original Android Development] monkteo:
Snapshot 435

THX
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Ah ok thanks! Lollipop ROMs (specifically CM12-based) require snapshot 8.0.0.r623 or newer. Make sure you have a working backup because the newer snapshots are still a bit unstable :)
[Galaxy S 4 i9505 Original Android Development] franzyroy:
The 423 snapshot works almost well with Lollipop and unfortunately, I do not have time to involve me more in the tests now. So I keep this one for the moment.
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
[MENTION=4277844]chenxiaolong[/MENTION]

Any chance your patcher will support LG G2 D802?

Do you need any infos?

thanks in advance
[Galaxy S 4 i9505 Original Android Development] gyxter:
Tried flashing a patched cm11 based rom in my s5 with standard system folder partition in it and it fails in recovery. Does the patcher only work now for block image roms?

using latest official TWRP
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If you're using the latest snapshot, then the patcher created a MultiBoot.log file on the internal SD. Could you sent that to me so I can see what's going on? Thanks!
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
The snapshots page got completely revamped! Let me know what you guys think ;)

https://dl.dropboxusercontent.com/u/486665/Snapshots/DualBootPatcher/index.html
[Galaxy S 4 i9505 Original Android Development] gyxter:
Here it is https://docs.google.com/file/d/0ByT9GOe9c3SIQ0VDTHlIdGhINDg/edit?usp=docslist_api

---------- Post added at 05:23 PM ---------- Previous post was at 04:55 PM ----------

Looking good! Bootstrapped :good: :cool:
[Galaxy S 4 i9505 Original Android Development] rboy28:
[MENTION=4277844]chenxiaolong[/MENTION] , will the DualBootUtility work with the new directions?
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Alright going to try out RR 3.0 with r635. Will let you know ls980.

EDIT: Just flashed and it went all the way through but the flash still failed. I took a screenshot. I also reboot and now stuck at lg logo. Going back to check and see if their are logs.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Here we are.

[MENTION=4277844]chenxiaolong[/MENTION] No multiboot.log either.
[Galaxy S 4 i9505 Original Android Development] sronweb:
Thanks again for your great support. It's very appreciated and your app is a must have for any android user!!!

Then I understand that I should patch again the primary rom to have the option to select the other newly patched roms. In my case I have Shostock 8.0 which has 1.4 Gb zip which can be patched only on a pc, then I understand I should wait for the pc version compatible with new patcher.

I'm having an issue to restore apps with Titanium Backup (it stuck restoring apps+data) and I guess it require the update of SuperSU binary. But how can I update it in case of multiboot roms?

PS: I have patched latest Supersu.zip and installed.

And working!!!! :)
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks for the log! It's failing because of the :

failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
symlink: failed to symlink /system/etc/firmware/wcd9320/wcd9320_mbhc.bin to /data/misc/audio/mbhc.bin: making parents failed
symlink: failed to symlink /system/etc/firmware/wcd9320/wcd9320_mbhc.bin to /data/misc/audio/mbhc.bin: No such file or directory

Did you originally have a ROM installed in multi-slot-1 that was patched using an old version?
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Going to try and Patch CloudyFlex 2.8 for LS980. Will I have to flash a patched kernel afterwords because Cloudy has an aroma installer for all LG G2 versions. You select your version and it flashes corresponding fixes including boot.img
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Oh man, that's new, it crashed... (most likely at the loki step). 8.0.0.r640.gd834cbb should be up soon with some more loki fixes. If is still doesn't work, could you pull the following files from adb right after it fails?

/dev/block/platform/msm_sdcc.1/by-name/aboot
/tmp/recovery.log
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
If the aroma installer has an option for ls980, then it should work (assuming there aren't anymore bugs).
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Just tried and it didn't work. Another you have to do is switch modems when using AOSP and stock LG Firmware for LS980. Which I did. Put me into fastboot. Also flashed a patched kernel with it so that might have been the problem. No go either way. Going to try lollipop again from Stock Flex 4.4.2.
[Galaxy S 4 i9505 Original Android Development] gyxter:
That's weird. I am pretty sure I have 1.40 GB of space in the system partition because I removed all the multiboot folders and wiped the old dual boot folders via dualbootutilities
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
[MENTION=4277844]chenxiaolong[/MENTION] here is the latest log. From latest apk of course. I had to switch modems and then switch back because I am running stock 4.4. Also tried using dual boot utility to go back to stock after flashing the patched 5.0 ROM, and it didn't boot, had to reflash kernel

https://docs.google.com/file/d/0B1d_Il6yTO73NGV4eXNkbUtHTDg/edit?usp=docslist_api
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
There we go, here's the culprit:

[Debug]: Found Android boot image header at: 0
[Debug]: - magic: ANDROID!
[Debug]: - kernel_size: 8619872
[Debug]: - kernel_addr: 0x00008000
[Debug]: - ramdisk_size: 2013393
[Debug]: - ramdisk_addr: 0x05000000
[Debug]: - second_size: 0
[Debug]: - second_addr: 0x00f00000
[Debug]: - tags_addr: 0x04800000
[Debug]: - page_size: 2048
[Debug]: - dt_size: 622592
[Debug]: - unused: 0x00000000
[Debug]: - name:
[Debug]: - cmdline: console=ttyHSL0,115200,n8 androidboot.hardware=g2 user_debug=31 msm_rtb.filter=0x0 mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_g2_lgd_cmd
[Debug]: - id: 51511de1e6b5921867a625ddefcaa5ee48cfc2ba0000000000000000000000000000000000000000
[Warning]: libarchive: Unrecognized archive format
[MultiBoot] Failed to load ramdisk
[MultiBoot] Failed to flash zip file.
[MultiBoot] Destroying chroot environment

chenxiaolong@cxl-4270cto DualBoot/cloudy » file boot.img-ramdisk.lz4
boot.img-ramdisk.lz4: LZ4 compressed data (v0.1-v0.9)

It looks like the ramdisk is compressed with LZ4, which the patcher doesn't support yet. I'll work on implementing that, it shouldn't be too hard.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
AhhI thank you so much hopefully all this testing will help everyone in the long run.
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Tested and It didn't work for me.

I guess we will have to wait for an update for this too.

Awesomeness is what keeps coming in here :thumbup::thumbup:
[Galaxy S 4 i9505 Original Android Development] Houndcatcher:
Hi,

I've just redone my phone using the more recent patcher and for my 3 Roms it appears to be working fine apart from one issue that is bugging me :confused: I run PA 4.6 Beta 5 currently as my primary with Alucards Kernel 2.7.2a. Since switching to the new patcher as soon as I flash the new Kernel I lose my Radio/WiFi, baseband becomes unknown with no APN's etc. Dirty flash the Rom back over the top and back come all my connections. Anything I can try as I'd rather use Alucards Kernel as the battery life is so much better :)
[Galaxy S 4 i9505 Original Android Development] todivefor:
I just tried flashing GPE 5.0.1 with the 8.0 patcher. I was flashing to my slot-1 with Sacs (TW) as my primary on sph-l720. Patcher worked fine. I wiped everything for slot-1 in dual utilities. I could not boot anything following install. During the aroma install it wiped /system. Is this slot-1 system for system system? If I use R436, will it have a better chance of working, or do I need to wait for new system?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
[MENTION=2688336]todivefor[/MENTION], 633 should work for you, it can be found here in snapshots posted by [MENTION=4277844]chenxiaolong[/MENTION].

http://xdaforums.com/showpost.php?p=58320472&postcount=4868

It will give you a _patched zip file, when installed you will be able to choose primary, secondary, multiboot1, etc.........
[Galaxy S 4 i9505 Original Android Development] todivefor:
That requires me to start over with all my secondary roms or change the pathes. Correct?
[Galaxy S 4 i9505 Original Android Development] JhoonB51:
I would assume so...however you could try "dirty flash" with the newly patched and see. I personally have not tried that. IMO doing the secondary over is prob the right way to go.
[Galaxy S 4 i9505 Original Android Development] gyxter:
Are there any G900H owners here using this patch and are able to make it work?
[Galaxy S 4 i9505 Original Android Development] robertogl:
Has anyone tried to patch echoe rom, lollipop version (Chinese leak)? :)

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Your testing has already helped me fix quite a few bugs, so thank you! :)

Actually, I just found out there are two LZ4 formats, one for lz4 0.1-0.9 and another for lz4 >1.0. Would you mind sending me your non-multiboot boot.img? I'd like to try two things:

Decompress and recompress using the newer LZ4 format

Decompress and recompress using the normal gzip format

If either one boots, it'll be a quick one-liner fix in the patcher, and things should hopefully start working again :)
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
First try on LG G2 D802 resulted in an error while flashing.

Tried newest snapshot build.

Recovery log is here

https://docs.google.com/file/d/0B8bTcpicQUmsNzd3SGZVWlY1aUU/edit?usp=docslist_api

Edit

Sorry found no multiboot.log on sdcard

Tried again with kk rom (liquidsmooth) but same error.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Thank you, will continue to support as long as I am using this G2.

Any who, here is the boot.IMG from SlimLP. https://docs.google.com/file/d/0B1d_Il6yTO73WlRMeS1uQ3E4M3M/edit?usp=docslist_api

I can also get you the boot.IMG from a lovely AOSP Kernel from [MENTION=5438598]RenderBroken[/MENTION]. R8 TEST LS980 https://docs.google.com/file/d/0B1d_Il6yTO73c0F2aHBhMDYyWVk/edit?usp=docslist_api
[Galaxy S 4 i9505 Original Android Development] todivefor:
I have something unusual happening. I can't attribute this to dualboot, but have only seen it since using dualboot. I hope someone can explain. Running Galaxy S4 (Sprint - SPH-L720). I am running Sacs-V4 (TW) as my primary. I run CM11-nightly (JFLTE), CM12 (AntaresOne optimized), and Pacman (JFLTE) as secondaries. I was running my primary and noticed on the play store my carrier was set to Verizon Wireless. I tried clearing cache/data on Play Store, no good. Cleared Google Play Services and Framework. This FUBARed my device. Restored from a nandroid backup and I ended back again with carrier Sprint on PS. I switched to my Pacman ROM and discovered PS was reset to Verizon Wireless. Anyone know what could be causing this or how to recover?
[Galaxy S 4 i9505 Original Android Development] rboy28:
Will be the DualBootUtilities updated?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
This annoying crash is finally fixed! I must have fallen asleep when I wrote some of the Loki code. 3 bugs in 3 lines of code lol: https://github.com/chenxiaolong/DualBootPatcher/commit/8ab60033747234229d489306da60f7505cd11ad4

The fix is available in 8.0.0.r666.gab30fb0, which should be up in a few minutes.

--

Tagging [MENTION=4491606]ktetreault14[/MENTION] because this bug affected the Lollipop ROM you tried to install.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Thanks! I'll update this post in a little bit with the links.

EDIT: Completely unmodified boot.img, just LZ4-repacked:

SlimLP: https://dl.dropboxusercontent.com/u/486665/ktetreault14/SlimLPboot_lz4repack.img

RenderR8: https://dl.dropboxusercontent.com/u/486665/ktetreault14/RenderR8boot_lz4repack.img
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Everything flashed right but as usual there was an error in the updater binary. After the boot image as usual. No multiboot log. Side note error in the aroma. Where is says multi-slot-1 it says 1 for all three of them ? [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Whoops, fixed the multi-slot description :)

Since the patcher couldn't copy the log itself, could you use TWRP's "Copy log to SD" option to get it?
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Yeah let me repatch and flash. Or can I get the log myself from within android?
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Cool ;) No there's no way to get the log from Android. It's stored on a temporary filesystem that's cleared on reboot, so that's why the patcher has to create multiboot.log.
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
NEW: https://docs.google.com/file/d/0B1d_Il6yTO73NnFyVFZRTGdMSDg/edit?usp=docslist_api

Some errors in their related to boot.IMG I think. Still learning how to read stuff. Gzip errors? Maybe lol. Had to manually pull this log

Here we are [MENTION=4277844]chenxiaolong[/MENTION]

Looks like the patcher isn't deleting the system.tmp file. Lemme delete it manually.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Now that's really interesting. It looks like the end of the boot.img might be getting cut off.

Any way you could pull /dev/block/platform/msm_sdcc.1/by-name/boot for me? I hope you haven't rebooted yet ;)
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Yeah I rebooted but no problem. Should I just adb pull etc. From the laptop or terminal.

Boot.IMG from Dev block https://docs.google.com/file/d/0B1d_Il6yTO73MWZfNS1HeFBuRVE/edit?usp=docslist_api
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
I found a way to flash the LS980 bootloader on my Nexus 5 which made debugging this easy lol.

The crash was caused by freeing resources too early when an error occured (fixed by [1]). The error itself was caused by my un-loki code. It's supposed to handle old-style and new-style loki boot.img files differently, but the old-style gzip searching code was called for your boot.img (fixed by [2]).

I'm able to patch and install CloudyFlex 2.8 and SlimLP on my hybrid ls980-nexus-5. Let's hope it'll work on your real one :)

[1] https://github.com/chenxiaolong/DualBootPatcher/commit/75feba5195e5ac7f7b2f04ca8028c84dd021c00d

[2] https://github.com/chenxiaolong/DualBootPatcher/commit/f8e43779b8a2cfcb096f5cac655eb82d831062e8
[Galaxy S 4 i9505 Original Android Development] sronweb:
[MENTION=4277844]chenxiaolong[/MENTION]

do you think is it possible to patch Shostock rom 8.0 for S4 with the new method? It's 1.4 Gb so I guess I cannot patch on the mobile phone but only with the windows patcher.

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

Please, what do you think?
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Why I can't choose the slot to patch for. I have only one which is called "multi boot patcher"
[Galaxy S 4 i9505 Original Android Development] sronweb:
With the new patcher the selection will be done during the installation. Go ahead!!
[Galaxy S 4 i9505 Original Android Development] jigsawcrank:
Ok thanks, i will try
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Excuse my language but holy hell. You got the sprint g2 boot loader in your nexus 5. That's amazing lmao. I'll be patching now!! Great Work

---------- Post added at 03:01 PM ---------- Previous post was at 02:46 PM ----------

Well I'm running cloudyflex on the zvc modem. I booted into recovery after I patched SlimLP and flashed the zv8 modem. I then flashed and installed to /dual. No problems so far. I reboot into system and it boots me into recovery lol ? Where to from here?

The recovery log looks clean. https://docs.google.com/file/d/0B1d_Il6yTO73UlV4TUdxY3A5Wnc/edit?usp=docslist_api

EDIT: When you flashed did you replace the boot.IMG with the one from you? Downloading latest Vanir and about to test it.

EDIT2: [MENTION=4277844]chenxiaolong[/MENTION] HEEEYYYYY It works with Vanir but wasn't working with the kernels you sent me. ROM is booting on the LS980 Sprint LG G2
[Galaxy S 4 i9505 Original Android Development] gaww:
First - there is an amazing amount of work being done here by the OP and his helpers - keep on trucking!

In the meantime, I have used 8.0 #99 to patch and flash primary and multislot ROMs and the Windows 9.0 alpha GUI to patch slim 5.0.x as secondary..

I shar apps between the first two but not the 5.0, as some of the 5.0 GAPPs are incompatible between the different andriod versions, and this caused some problems.

Initially, everything works OK, but after switching back and forth between the ROMs, the primary and multiboot 4.4.x ROMs become very unstable. I restore a backup of only the other 4.4 ROMs, and the problems are gone. If it flash the 5.0.x - it starts up again. I thought that since they were in their own partitions, they would not impact each other - except for app sharing, which I don't include the 5.0.x in.

My question is - what is going on to cause this?
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Thank you so much with all your help [MENTION=4277844]chenxiaolong[/MENTION] this thing finally works with the Sprint G2. The only thing I have for input on the app is a way to have a set modem for each rom, just like the boot.img. :D:D:D
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Also, the patched apk isn't letting me save my secondary boot.IMG nor can I manually move one to the folder
[Galaxy S 4 i9505 Original Android Development] lukas77:
Does apps sharing between roms supposed to work or is still WIP? S5 TW Lollipop and cm12 as second.

| Tapatalk | Samsung Galaxy S5 | G900F |
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
WIP
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
Can't confim that. On LG G2 D802 all is running as it should.

I installed secondary ROM, opend the dual boot patcher and set kernel as secondary. Now I can switch between ROMs when I open the app and "choose ROM" without a problem.

Only difference is I don't need to switch modems as most LP ROMs on D802 run with kitkat baseband.

Big Big Thanks for all your effort [MENTION=4277844]chenxiaolong[/MENTION]
[Galaxy S 4 i9505 Original Android Development] franzyroy:
[MENTION=4277844]chenxiaolong[/MENTION]

I have a favor to ask. Could you?

Or personalize your app in black

Or give the choice of white or black theme

My reason:

Since doing my black theme, I have to change the background of the popup, make it more clear, because when we modify the framework-res.apk in the menus of your app, the background changes but not the color of text, so that we do not see anything in these menus.

I thought this would be resolved with Theme engine ... UNFORTUNATELY NO, it's the same! :(

I'll put a screenshot in order to you can see my issue.

Thanks!
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Would you mind telling me your rom combo and boot loader so I can add you to my Op?
[Galaxy S 4 i9505 Original Android Development] tropenfrucht:
That would be really great.
[Galaxy S 4 i9505 Original Android Development] seijisandrei:
Can this support Danvdh's GPE Lollipop as primary and CM12 Official as secondary or multislot-1 already? XD If yes, what snapshot number? Thanks!
[Galaxy S 4 i9505 Original Android Development] MohamedN:
Yes it does, I even have tw plus what you mentioned.

Use latest snapshot to patch.
[Galaxy S 4 i9505 Original Android Development] chenxiaolong:
Hey guys, I will be offline until the end of the week for some personal reasons.

In the meantime, the build server is making snapshot builds for Windows again :)
[Galaxy S 4 i9505 Original Android Development] Sock12345:
Is this gonna work with S5 also?

and app sharing?

I install Whatsapp on TW and have the app+data on my dualboot right?
[Galaxy S 4 i9505 Original Android Development] ktetreault14:
Could someone make me a logo for the patcher with g2 on it? I would like to make it my profile image.
[Galaxy S 4 i9505 Original Android Development] todivefor:
Maybe someone can shed some light? I love this for my Galaxy S4 (Sprint). I run sacs-v4 (TW) primary, cm11-jflte, cm12-AntaresOne, and pacman-jflte as secondaries. They all run fine. I am trying to update my cm12. I am using patcher 436. If I flash the update, it bootloops. If I then flash the kernel, it works. Why is it necessary to flash the kernel? Do any of the snapshots get around this? Since I don't have the kernel for this rom, it causes me a problem.
[Galaxy S 4 i9505 Original Android Development] seijisandrei:
Almost all latest snapshots say that the failed to patch the kernel. Sooooo.. What does this mean?