Database Users

[Q] ANSWERED!! NAND.. can you change kernels?

Hi guys,
Is it possible to change the kernel of a nand build at all?
I am an Extended Battery user and find only NAND builds with Hastarins kernel work at all..
Is there a way of mixing and matching Kernels with builds?
Ta

nutmegy said:
Hi guys,
Is it possible to change the kernel of a nand build at all?
I am an Extended Battery user and find only NAND builds with Hastarins kernel work at all..
Is there a way of mixing and matching Kernels with builds?
Ta
Click to expand...
Click to collapse
Yes
Just made something for you, note: haven't tested it:
Kernel Theiving
How to:
- Install Nand version which has the kernel you want.
- Run "extract_kernel.bat"
- Install Nand version you like, and want to keep.
- Run "install_kernel.bat".
- Et voila!
Now, you only have to use "install_kernel.bat" if you flash another rom.
Note: You need adb installed on your PC
Quickie on how to install adb:
Moon2 said:
You need adb:
-Get this installer: http://developer.android.com/sdk/index.html
-Go to Available Packages, Expand Third Party - Google - select USB Driver
-Update adb driver, if not already installed from: C:\Program Files\Android\android-sdk-windows\google-usb_driver
-Copy "adb.exe" and "AdbWinApi.dll" from "C:\Program Files\Android\android-sdk-windows\platform-tools" to "C:\Windows\System32".
-Run the batch file.
Click to expand...
Click to collapse

thank you very much!
I will give this a go!

Moon2 said:
Yes
Just made something for you, note: haven't tested it:
Kernel Theiving
How to:
- Install Nand version which has the kernel you want.
- Run "extract_kernel.bat"
- Install Nand version you like, and want to keep.
- Run "install_kernel.bat".
- Et voila!
Now, you only have to use "install_kernel.bat" if you flash another rom.
Note: You need adb installed on your PC
Quickie on how to install adb:
Click to expand...
Click to collapse
I read the batch file and
you have created a folder called boot under data folder and pasted the zimage
so everytime when we boot out Hd2s it going to replace the zimage with the one in boot folder, so i guess its going to delay the booting process (correct me if im wrong) so is it possible to delete that folder after booting our Leos?

agarp said:
I read the batch file and
you have created a folder called boot under data folder and pasted the zimage
so everytime when we boot out Hd2s it going to replace the zimage with the one in boot folder, so i guess its going to delay the booting process (correct me if im wrong) so is it possible to delete that folder after booting our Leos?
Click to expand...
Click to collapse
No, that's not what it does. it mounts the boot partition temporarily to /data/boot, and after it's mounted, adb copies over the zImage file, and overwrites the preexisting kernel image, after this, the partition is unmounted. So it's not repeated at each boot.

works a treat...
I just used Android commander..
made sure it was connected..
then ran the extract batch file
installed the nand build i wanted...
then ran the install Kernel.bat
and it works a treat!!!!

Moon2 said:
No, that's not what it does. it mounts the boot partition temporarily to /data/boot, and after it's mounted, adb copies over the zImage file, and overwrites the preexisting kernel image, after this, the partition is unmounted. So it's not repeated at each boot.
Click to expand...
Click to collapse
thnxx for the clarification, now i get it

nutmegy said:
works a treat...
I just used Android commander..
made sure it was connected..
then ran the extract batch file
installed the nand build i wanted...
then ran the install Kernel.bat
and it works a treat!!!!
Click to expand...
Click to collapse
Is all that done on the phone? It seems you installed the kernel on the phone somehow. I'm clueless about adb, I tried to use it before but was dumbfounded by it all.
Do I need Eclipse? Downloading the SDK stuff...installing JDA SE and it talks about Eclipse.

Moon2 the links dead it says file has been removed anybody re upload it????

[CWM] [Flashable] [Only for Aurora 4.1a] Updated init.d support

I'm sorry to have to open another thread just for this, but I was waiting for zephyr1988 to update his files for aurora 4.1a. As he didn't do it yet, here it is
I had posted these in the other thread, but the files are now outdated and there was some confusion regarding the kernel inside the zip. These files, fix this, because I updated the kernel and services.jar for Aurora 4.1a.
Please, to understand what this does, read this thread:
http://forum.xda-developers.com/showthread.php?t=1710233
Notes:
- This is only for those with Aurora 4.1 + 4.1a update. For other versions, there will be auto-reboots, especially with the gallery, so, if don't have the latest aurora version, don't install this.
To install, flash both zips in recovery. Boot takes a little longer, but believe it, it's worth it
MIRROR

Thanks, fjsferreira! You're incredibly helpful all the time.

I get this error when i try to download.
404 - Not Found

greddyrx7 said:
I get this error when i try to download.
404 - Not Found
Click to expand...
Click to collapse
Yes, I get that too, looks like a problem with xda. Here is an alternate download. Extract the two zip files first
http://www.mediafire.com/?ifhpwtzmtevv1fl

Sorry if this question was already answered.
What are the changes in the boot.img?
dzo already added support to run init.d scripts already in kernel of the versions 4.1+, correct?
Why you need to add it to your zip?
Another question, what does the OOM_Priority_Charger_Aurora_4.1a.zip?

Couldn't flash OOM_Priority_Charger_Aurora_4.1a.zip through recovery, says installation aborted..
In on update 4.1a
Sent from my U8800

sr21 said:
Sorry if this question was already answered.
What are the changes in the boot.img?
dzo already added support to run init.d scripts already in kernel of the versions 4.1+, correct?
Why you need to add it to your zip?
Another question, what does the OOM_Priority_Charger_Aurora_4.1a.zip?
Click to expand...
Click to collapse
It's the same one that's in update 4.1a, I kept it because there was a boot.img in the original script, I don't know if removing it would lead to the script not working...

demolition23 said:
Couldn't flash OOM_Priority_Charger_Aurora_4.1a.zip through recovery, says installation aborted..
In on update 4.1a
Sent from my U8800
Click to expand...
Click to collapse
It's working here, I tried it again just now... what CWM are you using? You can also just extract the services.jar that's inside the zip, and copy it to /system/framework, replace the default and set permissions like the default and reboot.

fjsferreira said:
It's working here, I tried it again just now... what CWM are you using? You can also just extract the services.jar that's inside the zip, and copy it to /system/framework, replace the default and set permissions like the default and reboot.
Click to expand...
Click to collapse
I tried with 5.5.0.4 and then with 5.8.4.5.
i will redownload and try again..
EDIT
Same again...Will try manually. Thanks anyway!

Priority charger in attached files didn't work but files from Mediafire did.

fjsferreira said:
It's the same one that's in update 4.1a, I kept it because there was a boot.img in the original script, I don't know if removing it would lead to the script not working...
Click to expand...
Click to collapse
If I already have the 4.1 or 4.1a installed I already have the boot.img in my phone and It already have the support for init.d. So I think you do not need to add it to your zip.
That is creating problems only.
This is just a comment to improve your work and correct me if I'm wrong. I'll appreciate.

sr21 said:
If I already have the 4.1 or 4.1a installed I already have the boot.img in my phone and It already have the support for init.d. So I think you do not need to add it to your zip.
That is creating problems only.
This is just a comment to improve your work and correct me if I'm wrong. I'll appreciate.
Click to expand...
Click to collapse
It doesn't create any problem at all, because I didn't modify the 4.1a kernel in any way, it's the same that it's in dzo's 4.1aupdate zip.
On the other hand, removing it could cause problems with the updater script in this flashable zip, that's why I kept it in my flashable zip. You are not forced to install this zip if you don't want, but I can guarantee the boot.img is the same that's in dzo update, there's nothing bad coming from flashing it.

fjsferreira said:
It doesn't create any problem at all, because I didn't modify the 4.1a kernel in any way, it's the same that it's in dzo's 4.1aupdate zip.
On the other hand, removing it could cause problems with the updater script in this flashable zip, that's why I kept it in my flashable zip. You are not forced to install this zip if you don't want, but I can guarantee the boot.img is the same that's in dzo update, there's nothing bad coming from flashing it.
Click to expand...
Click to collapse
Hello fjsferreira,
Thanks for updating the zip, I was away for a week with no access to a PC.
I have updated the original thread with 4.1a OOM priority charger and a init.d zip that does not mess with the boot.img now that dzo has included it in his ROM, so it should be compatible with newer versions.

I ve read the threads but still dont know what is OOM priority charger or any charger and init.d . Can someone explain it to m?
Sent from my U8800 using xda app-developers app

bassdrum01 said:
I ve read the threads but still dont know what is OOM priority charger or any charger and init.d . Can someone explain it to m?
Sent from my U8800 using xda app-developers app
Click to expand...
Click to collapse
These are scripts that run at boot time to change memory management so that you always have a good amount of memory available. The package also contains some scripts to fine tune screen sensitivity, sdcard and CPU performance, those require editing the script files to uncomment some lines. Read the instructions on the other thread to fine out how to use this.
Sent from my U8800

Help-v6 supercharger script

HELLO EVERYONE
I AM CURRENTLY DEVELOPING A ROM AND I WANT TO KNOW HOW TO ADD V6 SUPERCHARGER SCRIPT TO
MY ROM
--abhishekr700

just run v6 supercharger in your rom - set it all up then pull your system to your pc either with adb or use the tar command in android terminal emulator on phone and copy to pc
then use the tar file generated in android kitchen to set up working folder

one more thin
i started building rom from stock rom and stock kernel
i added int.d support via android kitchen
so will init.d work

one more thin
i started building rom from stock rom and stock kernel
i added int.d support via android kitchen
so will init.d work

yes if the user uses a kernel that supports init.d

marcussmith2626 said:
just run v6 supercharger in your rom - set it all up then pull your system to your pc either with adb or use the tar command in android terminal emulator on phone and copy to pc
then use the tar file generated in android kitchen to set up working folder
Click to expand...
Click to collapse
But I have already built much of the rom.
Isn't there a way to add it by other method
Like I run v6 supercharger on my phone then copy 99supercharger from init.d folder to my rom init.d folder
Also my stock rom has stock kernel
And I added init d support to my rom via kitchen
Will.init.d script work

abhishekr700 said:
But I have already built much of the rom.
Isn't there a way to add it by other method
Like I run v6 supercharger on my phone then copy 99supercharger from init.d folder to my rom init.d folder
Also my stock rom has stock kernel
And I added init d support to my rom via kitchen
Will.init.d script work
Click to expand...
Click to collapse
if thats the only file it produces then yes
but you could just flash the rom you have built so far then install v6 supercharger then pull the system
and yes init.d will work if the end user uses a kernel that supports it

marcussmith2626 said:
if thats the only file it produces then yes
but you could just flash the rom you have built so far then install v6 supercharger then pull the system
and yes init.d will work if the end user uses a kernel that supports it
Click to expand...
Click to collapse
hey
canu do a favour for me
i will upload the update script from kitchen
can u tell me if it will give error while flashing

marcussmith2626 said:
if thats the only file it produces then yes
but you could just flash the rom you have built so far then install v6 supercharger then pull the system
and yes init.d will work if the end user uses a kernel that supports it
Click to expand...
Click to collapse
hey
canu do a favour for me
i will upload the update script from kitchen
can u tell me if it will give error while flashing

abhishekr700 said:
hey
canu do a favour for me
i will upload the update script from kitchen
can u tell me if it will give error while flashing
Click to expand...
Click to collapse
why dont you build the rom then flash it and see?

marcussmith2626 said:
why dont you build the rom then flash it and see?
Click to expand...
Click to collapse
what if the phone bootloops or doesn't boot
will i be able to open recovery mode

abhishekr700 said:
what if the phone bootloops or doesn't boot
will i be able to open recovery mode
Click to expand...
Click to collapse
you will only not be able to get into recovery mode if you incorrectly flash a kernel or a kernel that has a bug in it with recovery mode
if your rom does not contain a kernel in the rom zip or there is no problem with the kernel then the recovery mode will not be touched and you can always restore via odin in download mode

marcussmith2626 said:
why dont you build the rom then flash it and see?
Click to expand...
Click to collapse
what if the phone bootloops or doesn't boot
will i be able to open recovery mode

marcussmith2626 said:
you will only not be able to get into recovery mode if you incorrectly flash a kernel or a kernel that has a bug in it with recovery mode
if your rom does not contain a kernel in the rom zip or there is no problem with the kernel then the recovery mode will not be touched and you can always restore via odin in download mode
Click to expand...
Click to collapse
i have stock kernel in my rom
i think the recovery mode will open ??

marcussmith2626 said:
you will only not be able to get into recovery mode if you incorrectly flash a kernel or a kernel that has a bug in it with recovery mode
if your rom does not contain a kernel in the rom zip or there is no problem with the kernel then the recovery mode will not be touched and you can always restore via odin in download mode
Click to expand...
Click to collapse
i have stock kernel in my rom
i think the recovery mode will open ??

abhishekr700 said:
i have stock kernel in my rom
i think the recovery mode will open ??
Click to expand...
Click to collapse
re-read my quote again
are you replacing the kernel? if no then no chance of loosing recovery mode!

[Utility] Android Image Kitchen & Flasher APK

Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.
This apk need root.
All credit of unpak/repack tools used in my apk are to @osm0sis

atoxyd said:
Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.
This apk need root.
Click to expand...
Click to collapse
can I use this on snapdragon 615 stock kernel
Sent from my 6045X using Tapatalk

Yes, you can try

tested on htc desire 816, cm13
unpacks and repacks kernel and ramdisk successfully, but didn't extract or repack the dtbs (device tables image, kernel 3.4) so the repacked image won't boot.

Well I use in my apk AIK.mobile tools proposed by osm0sis.

atoxyd said:
Well I use in my apk AIK.mobile tools proposed by osm0sis.
Click to expand...
Click to collapse
https://github.com/osm0sis/AnyKernel2/ ?
from http://forum.xda-developers.com/showthread.php?t=2670512

bigsupersquid said:
tested on htc desire 816, cm13
unpacks and repacks kernel and ramdisk successfully, but didn't extract or repack the dtbs (device tables image, kernel 3.4) so the repacked image won't boot.
Click to expand...
Click to collapse
Hi, I test it on cm13 and I unpack recovery.img for HTC desire 816, I think it work fine.
If the apk didn't work properly that's means the boot image doesn't not following Google's standard format so you'll need to find other tools to unpack and edit your image.

atoxyd said:
Hi, I test it on cm13 and I unpack recovery.img for HTC desire 816, I think it work fine.
If the apk didn't work properly that's means the boot image doesn't not following Google's standard format so you'll need to find other tools to unpack and edit your image.
Click to expand...
Click to collapse
I can unpack, edit, and repack successfully.
but, it wont boot.
I used official twrp 3.0.0-0 recovery.img and cm13 boot.img both, tried without editing.
just unpack/repack/flash.
boots straight into hboot, which is what happens if I build a boot.img or recovery.img without dtbs.
I pointed to the anykernel2 link because I know its scripting handles dtbs.
the whole kernel device table thing is new to me, and so far only on this device, so I'm not very savvy with dtb work. been lucky enough that it was preconfigured in the build system for cm.

nero curin said:
can I use this on snapdragon 615 stock kernel
Sent from my 6045X using Tapatalk
Click to expand...
Click to collapse
Hi, did my apk work for you?

atoxyd said:
Hi, did my apk work for you?
Click to expand...
Click to collapse
only unpacking and repacking,didnt help on my device but yet again nothing else helps me compile kernel for this idol 3 so i guess this app works just not for me, bad luck :/
Sent from my 6045X using Tapatalk

Well, this is a beta version of my apk, only for testing, I use @osm0sis tools ,this doesn't mean that you have bad luck my friend, this is due to the limitation of @osm0sis tools, but I will find another way to make it universal apk. Okay

atoxyd said:
Well, this is a beta version of my apk, only for testing, I use @osm0sis tools ,this doesn't mean that you have bad luck my friend, this is due to the limitation of @osm0sis tools, but I will find another way to make it universal apk. Okay
Click to expand...
Click to collapse
The scope of my tools is for Google's Android image standard as defined in the bootimg.h header from AOSP/CM. My tool forks have the widest support available for images which are standards compliant, supporting all commonly used ramdisk compression formats.
Supporting Sony's ELF, MTK's labeled and Samsung's headerless image formats along with the standard images (not to mention Samsung's and others' various deviations based on the standard header) and having the script/app differentiate between them would be a very large and difficult undertaking indeed. If that's your plan then I wish you the best of luck in your efforts.

hey, ran more tests.
no issues with the dtb or other functions either.
backup and flash functions working fine too.
here, for your devices.xml
Code:
<!-- Desire 816 a5 (710C) added by bigsupersquid -->
<device>
<model>710C</model>
<kernel>/dev/block/mmcblk0p40</kernel>
<recovery>/dev/block/mmcblk0p41</recovery>
<cache>/dev/block/mmcblk0p42</cache>
</device>
thanks for your work.
eagerly awaiting your open source as well

atoxyd said:
Hi all , I'm new here and I would like to present to you this simple application which backup, edit, repack and flash kernel.img or recovery img with a single click.
This apk need root.
All credit of unpak/repack tools used in my apk are to @osm0sis
Click to expand...
Click to collapse
Thank you for adding the appropriate credit back to your post. Patching, cross-compiling and scripting has taken significant work. :good:
The only other thing that I'd ask is that you do not use the name of Android Image Kitchen or AIK in the title of your app. I'd like to suggest maybe "Image Editor and Flasher" as a snappy alternative?

bigsupersquid said:
hey, ran more tests.
no issues with the dtb or other functions either.
backup and flash functions working fine too.
here, for your devices.xml
Code:
<!-- Desire 816 a5 (710C) added by bigsupersquid -->
<device>
<model>710C</model>
<kernel>/dev/block/mmcblk0p40</kernel>
<recovery>/dev/block/mmcblk0p41</recovery>
<cache>/dev/block/mmcblk0p42</cache>
</device>
thanks for your work.
eagerly awaiting your open source as well
Click to expand...
Click to collapse
Thank you my friend , you are the only one who supported me , and from the beginning.

atoxyd said:
Thank you my friend , you are the only one who supported me , and from the beginning.
Click to expand...
Click to collapse
it's a useful project, definitely worth a little testing and feedback.
besides, i remember what a pain it was getting my xda account eligible for posting the project i was all gung-ho about sharing (optimus v boot from sd card if i remember correctly)
sharing is cool, but a lot of the feedback tends to be annoying when there's no logs or other usable information, just "it's broken" or "can you implement for me on device XYZ."

bigsupersquid said:
I can unpack, edit, and repack successfully.
but, it wont boot.
I used official twrp 3.0.0-0 recovery.img and cm13 boot.img both, tried without editing.
just unpack/repack/flash.
boots straight into hboot, which is what happens if I build a boot.img or recovery.img without dtbs.
I pointed to the anykernel2 link because I know its scripting handles dtbs.
the whole kernel device table thing is new to me, and so far only on this device, so I'm not very savvy with dtb work. been lucky enough that it was preconfigured in the build system for cm.
Click to expand...
Click to collapse
Did you have an unlocked bootloader ?

nothing changed on the device, unlocked and still s-on, I'm not sure what went wrong the first try.
PEBKAC error probably
(problem exists between keyboard and chair)

I release AIK&Flasher v2 , I use @xiaolu unpack/repack tools.

atoxyd said:
I release AIK&Flasher v2 , I use @xiaolu unpack/repack tools.
Click to expand...
Click to collapse
Please use a different name for your app as I have requested.

[Utility] Android boot Manager APK

Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the third version of the program.
Source (GITHUB SOURCE https://github.com/aToxyD/android_boot_image_manager_apk).
WHAT'S NEW
- Some optimization.
- Add new Text Editor with high syntax.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* Modding.MyMind, for his heavily modification of boot.img tool.
* Tah Wei Hoon, for TextWarrior.
* Dmytro Tarianyk, for Android Floating Action Button.
* Anthony Restaino, for Grant.
IMPORTANT
- Root is only necessary for Unpacking boot patched by "superSu or Magisk" and Backup/Flash Operations, so if you want to unpack stock boot or you have your favorite flasher apk like "Rachr", if so you dont need to check "Root Access" in settings menu.
- Please uninstall any previous version of ABM before installing the newer.

I do not like people to coming here and take what they wanted and leave like a thief , at least leave a comment. . .
This work is for all, so help your self.

atoxyd said:
Android Boot Manager (ABM), my goal is to make the procedure (Backup, Unpack, Edit, Repack and Flashe boot.img or recovery.img) so easy and accessible to all users without resorting to the command prompt , only a single click to get a quick and successful outcome at the same time .
This is the second version of the program.
WHAT'S NEW
- Corrected some bugs related to compatibility with Android 6.
- Use xiaolu mkbootimg tools (GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools)
TODO
- add support to x86, mips arch.
- add support to put files to unpacked folder.
- add support to combinedboot , in Xperia device recovery ramdisk is combined with system ramdisk.
IMPORTANT
- The apk need root access to work.
- Note that make change by adding files to unpacked folder with root explorer, the owner will be root and the apk will not work, if you do this you must change the owner to ABM apk.
THANKS
* xiaolu, original author of boot.img tool(GITHUB SOURCE https://github.com/xiaolu/mkbootimg_tools).
* modding.MyMind, for his heavily modification of boot.img tool.
* @bigsupersquid for his support and motivate from the beginning.
Click to expand...
Click to collapse
mtk support?

lixia1998 said:
mtk support?
Click to expand...
Click to collapse
Certainly I am working on this , but you should help me.

New version won't install on Kit Kat

PiggyFlooper said:
New version won't install on Kit Kat
Click to expand...
Click to collapse
Okay my friend, try to uninstall the old version, and tell me.

atoxyd said:
Okay my friend, try to uninstall the old version, and tell me.
Click to expand...
Click to collapse
You were right, I'll start project tonight editing ramdisk on my LG Volt

Are extracted files accessible in file system? I can't find them

levone1 said:
Are extracted files accessible in file system? I can't find them
Click to expand...
Click to collapse
Unpacked to /data/local/ABM

PiggyFlooper said:
Unpacked to /data/local/ABM
Click to expand...
Click to collapse
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.

atoxyd said:
But beware when you add new files to the unpacked folder , you must take into account that owner will be. root , so you must set owner to ABM apk.
Click to expand...
Click to collapse
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?

levone1 said:
So I tested with twrp IMG, and successful unpack to /data/local. Then I tried with my current kernel, and nothing's happening. I get a message that's not clear to me, (screenshot 2), and no output. Any ideas?
Click to expand...
Click to collapse
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:

atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
That was my original thought, so I wiped data and tries again, but no different... I'll just uninstall and reinstall, and probably be fine. Thanks

atoxyd said:
It seems that you delete the directory /data/local/ABM, So close the apk and open it again or wipe apk data and try again, if any problems tell me please :thumbup:
Click to expand...
Click to collapse
Same thing after reinstall. I tried with twrp file again, and works fine, but with kernel file, error msg...

It seems that the image you want to unpack it is not an android image.

atoxyd said:
It seems that the image you want to unpack it is not an android image.
Click to expand...
Click to collapse
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk

Try to edit devices.xml in /sdcard/ABM directory and backup kernel using ABM app, after try to unpack boo.img backed up, you find it in /sdcard/ABM/backup directory.

levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, try to delete space in the name of image.
Linux ..........img will be
Linix_..........img

levone1 said:
It's the AOSP kernel from the ROM I'm currently using.
https://mega.nz/#!do51zAZS!QG5jTdpynPjNs7jrbERsdwRKjdac9tz-0SxUX6HyJsk
Click to expand...
Click to collapse
Well my friend, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img

Well my friend @levone1, delete space in the name of the image.
Linux 3.10....img
will be
Linux_3.10....img