Hello guys. Found this guide for kernel reverse-engineering via IDA pro. I have done several steps, but can`t separate the image itself from the extractor in the zImage file. Should i even continue, or the idea is useless? Is it`s useful, you can download and try to unpack the zimage by yourself, and i also have the symbols for a script.
[email protected] said:
Hello guys. Found this guide for kernel reverse-engineering via IDA pro. I have done several steps, but can`t separate the image itself from the extractor in the zImage file. Should i even continue, or the idea is useless? Is it`s useful, you can download and try to unpack the zimage by yourself, and i also have the symbols for a script.
Click to expand...
Click to collapse
I saw your post about this in another thread, and I did not want to discourage you, so I kept quiet. But, since you now ask directly, I will advise you to not waste your time. Even with full source code, kernel hacking is not for the faint-hearted, and is far from a trivial exercise. With no source code (or with incomplete source code), you might as well want to try getting hedgehogs to fly to Mars ...
Hi there! First, I'm no dev (got some experience about building Roms/Kernel from source) so sorry if I ask noobish things .
I got the same problem with the mi4s zimage (want to reverse engineer because official kernel sources are incomplete..) couldn't I just extract everything out of boot partition and create the source-code out of that? or what's the Problem by doing this? If the extracted source code (for whatever reason) is incomplete, wouldn't it be possible to get the missing things from official source released by xiaomi?
Thanks in advance
wertus33333 said:
...couldn't I just extract everything out of boot partition and create the source-code out of that? or what's the Problem by doing this? If the extracted source code (for whatever reason) is incomplete, wouldn't it be possible to get the missing things from official source released by xiaomi?
Click to expand...
Click to collapse
You want to extract compilable linux kernel source code from a compiled kernel? Sorry to disappoint you - but human beings will learn to climb a rope from Europe to the moon before you could achieve it. You might be able to disassemble the kernel, but you would not get anything near something compilable.
Hint: if it could readily be done, do you not think someone in these and other forums would have done it already?
DarthJabba9 said:
You want to extract compilable linux kernel source code from a compiled kernel? Sorry to disappoint you - but human beings will learn to climb a rope from Europe to the moon before you could achieve it. You might be able to disassemble the kernel, but you would not get anything near something compilable.
Hint: if it could readily be done, do you not think someone in these and other forums would have done it already?
Click to expand...
Click to collapse
There are lots of people who already did this! (see xiaomi forums redmi 3s, mi pad, Samsung galaxy s3, i9000/9001 etc. etc.). And those kernel are indeed working (even better than the ones from source) (yes, I tried it).
U ask why no one already did this? maybe because Mi4s community is very small (not even our own section..) and its quite a new device.
So why is it possible with other phones but not with mi4s?
Ty for help and explanation
Btw, can u explain it technically? not like "humans will learn to breathe in space before"....
wertus33333 said:
There are lots of people who already did this! (see xiaomi forums redmi 3s, mi pad, Samsung galaxy s3, i9000/9001 etc. etc.). And those kernel are indeed working (even better than the ones from source) (yes, I tried it).
Click to expand...
Click to collapse
If you mean that somebody patched a binary kernel, yes, that can be done, and I have done it myself. If you mean that somebody disassembled a binary kernel into compilable source code, I very much doubt that. If you claim that others have done it, why not post a link to the source code that they extracted, so that we too can try our hands at compiling it?
wertus33333 said:
U ask why no one already did this? maybe because Mi4s community is very small (not even our own section..) and its quite a new device.
So why is it possible with other phones but not with mi4s?
Click to expand...
Click to collapse
I am totally unconvinced about the claim that "it is possible with other phones". Please show the evidence.
wertus33333 said:
Ty for help and explanation
Btw, can u explain it technically? not like "humans will learn to breathe in space before"....
Click to expand...
Click to collapse
A simple example - http://blog.packagecloud.io/eng/201...-and-disassmble-a-linux-kernel-image-vmlinuz/
Scroll to the bottom of the page and see what you will get for your efforts. Try compiling that. Better still, try editing it to add missing things or fix/remove broken things, and then compiling it. Finally, you are talking about 15 million lines of source code. Good luck.
for example here: http://en.miui.com/thread-125557-1-1.html
http://forum.xda-developers.com/android/software-hacking/how-to-reverse-engineer-kernel-t3137384
Maybe we're talking about different matters, I just want to implement UV and OC in the original xiaomi kernel to use it with smiui... As you seem to know a lot about linux kernels, how can this be done?
Greetz
wertus33333 said:
for example here: http://en.miui.com/thread-125557-1-1.html
http://forum.xda-developers.com/android/software-hacking/how-to-reverse-engineer-kernel-t3137384
Click to expand...
Click to collapse
These are the bases of your claim that it can be done? I cannot see anywhere in those two threads where anybody was able to do anything useful with what was being proposed.
wertus33333 said:
Maybe we're talking about different matters, I just want to implement UV and OC in the original xiaomi kernel to use it with smiui... As you seem to know a lot about linux kernels, how can this be done?
Click to expand...
Click to collapse
I know how to compile linux kernels when the full source code exists. I also know how to patch such sources to edit/add/remove specific things. I also know how to patch an uncompressed binary kernel if I know exactly which offset(s) to patch and which values to substitute for what is already there. I have done this for 32-bit RK3188 android kernels in my old tablets (search the ARCTABLET forums and you might see some of my historic work on overclocking RK3188 binary kernels). This was easier for RK kernels than for MTK, and much can go wrong. If all is that is needed for what you want to do is to change specific values at specific offsets, then all you need is a hex editor and the necessary information about offsets/values. If you are trying to add a new feature, then you need the full source code from the vendor.
Get yourself a backup phone before trying anything of the sort. Like I said before, I wish you good luck!
Thank you for that information. Wouldn't it be possible to edit the things in zimage (unpacked) and then just re-pack it and use it? There shouldn't be anything missing if I'm able to find the correct offset for the lzo compressor...
wertus33333 said:
Thank you for that information. Wouldn't it be possible to edit the things in zimage (unpacked) and then just re-pack it and use it?
Click to expand...
Click to collapse
It is a binary file, which of course you can edit with a hex editor. But what exactly are you proposing to edit in it?
Isn't it an image containing files from Kernel? Otherwise they wouldn't talk about extracting it... Yes, I need to edit it with a hex-editor to remove the lzo header (zimage is a self extracting archive, but i want to extract it with normal zip extractor) but cant find where the header starts.
wertus33333 said:
Isn't it an image containing files from Kernel? Otherwise they wouldn't talk about extracting it... Yes, I need to edit it with a hex-editor to remove the lzo header (zimage is a self extracting archive, but i want to extract it with normal zip extractor) but cant find where the header starts.
Click to expand...
Click to collapse
Your questions show a misunderstanding of what a kernel is. The best I can do is to refer you to Android kernel development information - see e.g.,
http://www.99droid.com/android-kernel-development-tutorial-let-the-development-begin/
http://source.android.com/source/index.html
http://source.android.com/source/building-kernels.html
At this point, I bow out of this discussion.
Related
NEW:
Working .34-rc3 kernel available at http://forum.xda-developers.com/showpost.php?p=6290443&postcount=45
OLD:
Code:
This is an experimental .34-rc2 kernel for the Nexus One.
Provided in the zip file is a folder (2.6.34-rc2-termana-nexusone) and the kernel (zImage).
It is extremely experimental, so only follow this if you [B][I][U]really[/U][/I][/B] know what your doing and know how to reflash another kernel back to make it boot again if it doesn't boot. I'm not responsible if your device curls over and dies.
Use adb to push the folder into /system/lib/modules/ and then use fastboot to flash the kernel.
The kernel is a rebase of cyanogen's .33.1 kernel to the latest .34-rc2 kernel. So nothing particularly new about it, besides the satisfaction that not many people would be running this kernel version on devices.
Zip file: bit.ly/94Oo6m (To download it click the link next to the text "Save file to your PC:")
Edit: Being a new member of xda-developers forum, it wouldn't let me post the link properly, but just copy and paste it and you'll be fine.
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
I just flashed the zimage, and the phone went into a boot loop. Do I have to install anything else?
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Will give it a go nad logcat it
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
thanks, thought it was a mistake that you said push that folder, glad you clarified it for me
thanks again
jlevy73 said:
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
Click to expand...
Click to collapse
damn, that is long; won't bother reading that thing
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
I used this:
adb push 2.6.34-rc2-termana-nexusone /system/lib/modules/2.6.34-rc2-termana-nexusone
Click to expand...
Click to collapse
...and it still went into a boot loop for me.
hotweiss said:
I used this:
...and it still went into a boot loop for me.
Click to expand...
Click to collapse
You sure that wouldn't create a folder within a folder?
Not really sure just saying...
So is this working for you Termana?
I tried both have the subfolder and just pushing all the files to /modules and both produced a bootloop
i pushed the folder to /system/lib/modules/ and flashed zimage, but just get bootloop
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
I seriously thought, you tested it on your Nex before posting it....was a missunderstanding.
Termana said:
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
Click to expand...
Click to collapse
Did you cross compile the source against the ARM source?
hotweiss said:
Did you cross compile the source against the ARM source?
Click to expand...
Click to collapse
You might need to rephrase your question as the way you've said it doesn't let me know exactly what you mean by "ARM source". Do you mean using the Android ARM toolchain or what?
To anyone that is willing to help me test:
New build available at - bit.ly/c1tFqg (just the zImage, don't worry about pushing the modules for now)
Info:
This is a .33.1 kernel not a .34-rc2 kernel HOWEVER, I wanted to get the source that I'm rebasing off tested to make sure it boots, because if the source I'm pulling from doesn't boot, then obviously my rebases aren't going to either. So, please test it and tell me if it boots, if it does, I'll have another .34-rc2 kernel build up shortly after. If it doesn't, I may have to try rebasing from the official .32 kernel rather than the current source I'm rebasing from at the moment (which is .33.1).
Booted for me.
Code:
2.6.33.1-cyanogenmod
[email protected] #1
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Justin241982 said:
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Click to expand...
Click to collapse
I wouldn't post it yet. The first one he posted doesn't boot and the second one he posted I don't believe has any optimizations.
Hello,
I believe a lot of us would like to do it, so let's please describe here how-to:
1. Linux
2. Mac os Leo
3. Windows
Gurus, please contribute!
Excellent initiative, I could write a short howto for Arch Linux later.
But one thing though, it might be a good idea to mention in the first post that you can't actually boot a custom kernel yet.
ddewbofh said:
Excellent initiative, I could write a short howto for Arch Linux later.
But one thing though, it might be a good idea to mention in the first post that you can't actually boot a custom kernel yet.
Click to expand...
Click to collapse
Indeed agree, but to try we need to have it!
My topic about compiling kernel sources has already many infos so do you think another similar topic is really necessary ?
alx5962 said:
My topic about compiling kernel sources has already many infos so do you think another similar topic is really necessary ?
Click to expand...
Click to collapse
Your thread is excellent but I'd guess that this thread would be more oriented towards "hand-holding", really basic guides. Your topic was very broad requiring going to the android developers site and reading their docs on cross-compilation. Gathering that info into easier guides could be beneficial, if not to demystify the process.
As it stands right now just compiling modules seems almost insurmountable. But if the information needed could be condensed into simple guides it could show that while it takes considerable time and effort it's not an impossible task even for developers not familiar with cross-compiling kernels.
And information information on setting up cross-compilers for Win, Mac and popular Linux distros is nice to have available in an easy to find topic anyway.
IMHO, the easiest way to make modules would be a virtualbox image already set up with arm gcc, kernel sources and X10 kernel config. It's a long process to set everything up; virtualbox makes this easier and cross platform.
maxrfon said:
Hello,
I believe a lot of us would like to do it, so let's please describe here how-to:
1. Linux
2. Mac os Leo
3. Windows
Gurus, please contribute!
Click to expand...
Click to collapse
Sources are here :
http://developer.sonyericsson.com/cws/download/1/823/877/1278570405/X10_mini_Donut_100630.tar.gz
Rest can be done in same way as for "big" X10.
alx5962 said:
IMHO, the easiest way to make modules would be a virtualbox image already set up with arm gcc, kernel sources and X10 kernel config. It's a long process to set everything up; virtualbox makes this easier and cross platform.
Click to expand...
Click to collapse
Do you have such virtual box image or whatever it is?
maxrfon said:
Do you have such virtual box image or whatever it is?
Click to expand...
Click to collapse
yep but can't share it as everything is set up in french and I'm sure you'll not like this
anyway, i'm sure the owner of this thread will enjoy to create one.
alx5962 said:
yep but can't share it as everything is set up in french and I'm sure you'll not like this
anyway, i'm sure the owner of this thread will enjoy to create one.
Click to expand...
Click to collapse
Yes, french for me is a bit difficult
Ok i managed to make Ubuntu on my Parallels, just finished with the gcc. Let's see how it works.
Maybe i will share it.
kernel config is included in the /etc folder if I remember well, hope it's the same for the mini X10
It's actually in /proc
zdzihu said:
It's actually in /proc
Click to expand...
Click to collapse
Hi zdzihu,
I managed somehow install arm gcc on my Ubuntu. Now it's time for the tools.
So i would like to ask what config should i use arm v4? V5?
I am so tired with this linux things, but finally at least the demo busybox compiled well
So i tried to compile with arm-v5te config but for flash read (which is normaly working) it says
Code:
# ./dump_image system /sdcard/tt.bin
error reading system: Inappropriate ioctl for device
My task it not to run flash tools available, but my own, to compile all myself, to try to do the trick with the CPU to accept kernel, that i compiled.
Thanks.
The Snapdragon is armv7 compliant, so that should be your target.
ddewbofh said:
The Snapdragon is armv7 compliant, so that should be your target.
Click to expand...
Click to collapse
http://jackytw.blogspot.com/2009/11/howto-run-native-linux-application-on.html
This tut i was using.
I can't find v7 .. Should i consider the V as the CPU ver?
Then its 1136 if i am not wrong?
maxrfon said:
http://jackytw.blogspot.com/2009/11/howto-run-native-linux-application-on.html
This tut i was using.
I can't find v7 .. Should i consider the V as the CPU ver?
Then its 1136 if i am not wrong?
Click to expand...
Click to collapse
Are you using that tool to build the toolchain? In that case it might not have the option to build for that arch. The best way to make sure you get the correct one is to build it manually from scratch.
ddewbofh said:
Are you using that tool to build the toolchain? In that case it might not have the option to build for that arch. The best way to make sure you get the correct one is to build it manually from scratch.
Click to expand...
Click to collapse
Looks like there is no other tut to build the toolchain. I searched days and nights to find something working.
I even compiled bysybox with it and it works on my x10!
But i found some sources of flash backup, called nandtools, compiled them well, no errors but the exec files are 4x bigger than the precompiled ones... And it makes the IOControl error..
the NDK won't compile, it requires Makefile or Android.mk and those are real headache to learn.
The Makefile from the archive is not compatible with NDK's make system and so on...
And so 2 weeks..
Pufff.. I am so tired if just linux things
Any hand?
Hi there, ARM is backward compatibile so compiled for v5 should run just fine. Problem must be somewhere else... I'm at work at the moment so I can't help much
By the way, there was some kind of dedicated flash tool posted already HERE, maybe you could check with jerpelea for re-upload?
zdzihu said:
Hi there, ARM is backward compatibile so compiled for v5 should run just fine. Problem must be somewhere else... I'm at work at the moment so I can't help much
By the way, there was some kind of dedicated flash tool posted already HERE, maybe you could check with jerpelea for re-upload?
Click to expand...
Click to collapse
You see, i need to compile mine, i have enough tools here already working, but my task is to compile my own and that's why i need a toolchain.
NDK is ok for the kernel, i compiled it already. But the native applications are not supported fully. Like write is deprecated and you can't use this function, and lot other limitations. So independent toolchain would help.
That's the point.
maxrfon said:
So independent toolchain would help.
Click to expand...
Click to collapse
PM sent =)
Hi I have found the way to port ICS to the galaxy players. :
http://www.freeyourandroid.com/guide/compile-ics
The problem is that I can't find the binaries for the galaxy player. Where I can find them?
arent they located in /system/bin?
Need root first though
(I would help out with this, but dont really know how to do it, and i dont have the player yet)
zaclimon said:
Hi I have found the way to port ICS to the galaxy players. :
http://www.freeyourandroid.com/guide/compile-ics
The problem is that I can't find the binaries for the galaxy player. Where I can find them?
Click to expand...
Click to collapse
Will this actually boot and run? If it's that "easy", then why don't more devices have ICS? If you can extract the binaries and cook up a rom, I would be happy to test it . Also, if I have time later this week, I'll try to follow those instructions and then post my results. If everything works on the first try, I'll be very surprised but not at all dissapointed . Thanks for sharing this
Dyskmaster said:
Will this actually boot and run? If it's that "easy", then why don't more devices have ICS? If you can extract the binaries and cook up a rom, I would be happy to test it . Also, if I have time later this week, I'll try to follow those instructions and then post my results. If everything works on the first try, I'll be very surprised but not at all dissapointed . Thanks for sharing this
Click to expand...
Click to collapse
Well maybe because people don't know how to do it. And as for the current rom the major problem is the hardware acceleration and the camera. Maybe We can find it (The binairies) at opensource.samsung.com
It should be easier than phones because you don't have to worry about not screwing with voice, data, and stuff like that. Just get it on and get all the apps working correctly. Radios are always the hardest.
I've also been triyng to compile the source for the player but i wasnt able to do so, the thing is that the source compiles fine with the pre-adjustments it comes with, i mean the androidboard.mk ( i think thats the name of the file not sure), but when i changed the variables for a armv5 build, which is the core of the device and the ones that comes in the same file on the opensource.samsung soource, it just doesnt compile and throws some kind of errors about some libraries that i didnt touched. i dont know what i had been doing wrong.
I Also found this video in which they show whats in every folder, and how to build and add packages from source to the build:
http://marakana.com/forums/android/general/269.html
This is a detail process description from the official android site to build from source, very similar like the one zaclimon found:
http://source.android.com/source/initializing.html
The source from samsung doesnt have all the drivers, just the alsa audio driver, i guess we gonna have to find a way to get the binaries like cyanogen did, maybe get some scripts they use and try to do it ourselves:
http://wiki.cyanogenmod.com/wiki/Sa...le_CyanogenMod_(Linux)#Copy_proprietary_files
it is done through the adb, but the thing is to get those files, maybe we could ask that fellow some help for this step, since he has the experience.
sodomywar said:
I've also been triyng to compile the source for the player but i wasnt able to do so, the thing is that the source compiles fine with the pre-adjustments it comes with, i mean the androidboard.mk ( i think thats the name of the file not sure), but when i changed the variables for a armv5 build, which is the core of the device and the ones that comes in the same file on the opensource.samsung soource, it just doesnt compile and throws some kind of errors about some libraries that i didnt touched. i dont know what i had been doing wrong.
I Also found this video in which they show whats in every folder, and how to build and add packages from source to the build:
http://marakana.com/forums/android/general/269.html
This is a detail process description from the official android site to build from source, very similar like the one zaclimon found:
http://source.android.com/source/initializing.html
The source from samsung doesnt have all the drivers, just the alsa audio driver, i guess we gonna have to find a way to get the binaries like cyanogen did, maybe get some scripts they use and try to do it ourselves:
http://wiki.cyanogenmod.com/wiki/Sa...le_CyanogenMod_(Linux)#Copy_proprietary_files
it is done through the adb, but the thing is to get those files, maybe we could ask that fellow some help for this step, since he has the experience.
Click to expand...
Click to collapse
The core is a ARMv7 right? because the hummingbird processor is a ARMv7. Maybe it did failed because of that? I found the gpu drivers from the opensource. Check in the kernel folder. If I can give you the gpu file if you want. Well tell me what files you are missing i'll find to give it to you. (Well I don't know how to program so I try do to my best.)
EDIT: Also its seem that to compile ICS is more difficult than the other versions. We do need ubuntu to extract the binaries right?
EDIT2: People are saying that it's easier to build from CM9 than from the source. It is right or it's the same thing?
http://forum.cyanogenmod.com/topic/38960-build-your-own-cm9ics-preview-on-ubuntu-and-perhaps-debian/
Galaxy S Phone
Shouldn't you just be able to modify a Galaxy S ICS port and take out the data and other stuff you don't need?
zaclimon said:
The core is a ARMv7 right? because the hummingbird processor is a ARMv7. Maybe it did failed because of that?
Click to expand...
Click to collapse
Well, i configured it with the files of the samsung source, and it said ARMv5, we need to know which one it is, probably faild because of libaries compatibilities for that architecture.
zaclimon said:
EDIT: Also its seem that to compile ICS is more difficult than the other versions. We do need ubuntu to extract the binaries right?
EDIT2: People are saying that it's easier to build from CM9 than from the source. It is right or it's the same thing?
Click to expand...
Click to collapse
Maybe it is easier than the official source, they modify the source and takes out some things that cellphones dont need 'cause the source it's made for all devices, so it could be smaller and easier to compile, i'm gonna try this port and let ya' know, it will take a while since the source it's huge
Would be great if a couple of us do it, if you can @zaclimon try it, you don't need ubuntu, if you know which libaries that command has (sudo apt-get install build-essential). I have debian and i compiled the source just fine, debian has a minimal installation (no X11) but to compile source you dont need anything else! Let me know if anyone else it's triyng we could excahnge some ideas!
sodomywar said:
Well, i configured it with the files of the samsung source, and it said ARMv5, we need to know which one it is, probably faild because of libaries compatibilities for that architecture.
Maybe it is easier than the official source, they modify the source and takes out some things that cellphones dont need 'cause the source it's made for all devices, so it could be smaller and easier to compile, i'm gonna try this port and let ya' know, it will take a while since the source it's huge
Would be great if a couple of us do it, if you can @zaclimon try it, you don't need ubuntu, if you know which libaries that command has (sudo apt-get install build-essential). I have debian and i compiled the source just fine, debian has a minimal installation (no X11) but to compile source you dont need anything else! Let me know if anyone else it's triyng we could excahnge some ideas!
Click to expand...
Click to collapse
how many MB or GB the source has because I can't exceed my download's limitations?
EDIT: I'm a linux newbie. Is Ubuntu is the same thing as debian? Because Ubuntu is debian based right?
EDIT2: nevermind I'll be using ubuntu
alltellmobile said:
Shouldn't you just be able to modify a Galaxy S ICS port and take out the data and other stuff you don't need?
Click to expand...
Click to collapse
I don't know if we can (we should ask permissions) but it's definitly possible.
zaclimon said:
EDIT: I'm a linux newbie. Is Ubuntu is the same thing as debian? Because Ubuntu is debian based right?
Click to expand...
Click to collapse
Yea Ubuntu should be pretty much the same.
Wish I knew how to program, because i would help out.
alltellmobile said:
Yea Ubuntu should be pretty much the same.
Wish I knew how to program, because i would help out.
Click to expand...
Click to collapse
You can help I follow the tutorials there:
http://www.freeyourandroid.com/guide/compile-ics
http://marakana.com/forums/android/general/269.html
Ok i was reading the first tutorial and got to the part about binaries for graphics acceleration; wouldn't we have to get ours before we compile it. Also i only have the US version of the galaxy player and if i made an image i couldn't test it because we don't have a custom recovery for ours.
alltellmobile said:
Ok i was reading the first tutorial and got to the part about binaries for graphics acceleration; wouldn't we have to get ours before we compile it. Also i only have the US version of the galaxy player and if i made an image i couldn't test it because we don't have a custom recovery for ours.
Click to expand...
Click to collapse
Oh that's true well you can try to port a custom recovery?
zaclimon said:
Oh that's true well you can try to port a custom recovery?
Click to expand...
Click to collapse
HaHa I'm not that good. that sounds way more complicated
hey guys, i've been following this thread and hopefully i can be of some help...
i'm currently in the process of pulling the system files from the original gingerbread build from the SGP...it looks like there will be some trial and error here comparing that of the nexus s build...correct me if i'm wrong, but is this where most of the proprietary libraries are located for the device?
i'm willing to engineer a generic build, described in the video tutorial and making the necessary adjustments for the ARMv7 board...
this is my first attempt at compiling Android source, so maybe we will have something or maybe i will have a good ol' brick...thanks for the great tutorial and video @zaclimon this has definitely shed some light on porting ICS for SGP
jdale38 said:
hey guys, i've been following this thread and hopefully i can be of some help...
i'm currently in the process of pulling the system files from the original gingerbread build from the SGP...it looks like there will be some trial and error here comparing that of the nexus s build...correct me if i'm wrong, but is this where most of the proprietary libraries are located for the device?
i'm willing to engineer a generic build, described in the video tutorial and making the necessary adjustments for the ARMv7 board...
this is my first attempt at compiling Android source, so maybe we will have something or maybe i will have a good ol' brick...thanks for the great tutorial and video @zaclimon this has definitely shed some light on porting ICS for SGP
Click to expand...
Click to collapse
Yes they are supposed to be there. But I have download all the source code of the firmware from opensource.samsung.com
Me and sodomywar are working with the internationnal version of the SGP4. If you want to join you're welcome.
EDIT: No problem for the tutorials.
alltellmobile said:
HaHa I'm not that good. that sounds way more complicated
Click to expand...
Click to collapse
Google is your friend
So this is where i'm at currently. I'm trying to compile and I got this error:
Code:
build/core/base_rules.mk:166: *** system/extras/ext4_utils: MODULE.TARGET.EXECUTABLES.setup_fs already defined by device/samsung/galaxyplayer. Stop.
Does anyone know how to remove that error?
EDIT: nvm I managed to remove this error.
Hi,
Just wondering if/when MadCatz will release the kernel?
I know linux being GPL, it has to be shared, but not sure about Nvidia's sources?
I'm new to android but not java(my day job) and linux.
I've compiled and installed my own kernels on desktop and on my mobile phone (Nokia N900).
I want to try and add a few things.. ie filesystem/DVB/webcam support etc.
Following this how to.
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
Sweet! many thanks :victory:
:highfive:
:good:
omg.... does this mean we can finally have a cifs module!? AWESOME!
So now that the kernel source is avialable, I'm looking forward to the first custom kernels. Would be great to have some kernel optimizations and other tweaks built in :good:
RollingRoman said:
So now that the kernel source is avialable, I'm looking forward to the first custom kernels. Would be great to have some kernel optimizations and other tweaks built in :good:
Click to expand...
Click to collapse
Yes i hope someone can make a kernel to re-apply resolution settings on the m.o.j.o, as mad catz said to me via a phone call some tv's can't adjust to 1080p natively because the os is preventing it,and stupidly they removed the resolution changing slider in settings don't ask me why they did that?
If there is a way to set resolution without endangering the console booting up afterwards would be awesome,i am thinking it is there but hidden away and accessable some way but don't know how,developer options can be opened but not resolution settings as far as i have found any way.
PHYSC-1 said:
Yes i hope someone can make a kernel to re-apply resolution settings on the m.o.j.o, as mad catz said to me via a phone call some tv's can't adjust to 1080p natively because the os is preventing it,and stupidly they removed the resolution changing slider in settings don't ask me why they did that?
If there is a way to set resolution without endangering the console booting up afterwards would be awesome,i am thinking it is there but hidden away and accessable some way but don't know how,developer options can be opened but not resolution settings as far as i have found any way.
Click to expand...
Click to collapse
I think it automatically sets the resolution based on the TV/monitor, try a different one?
TMK, the slider has nothing to do with the kernel.
gwaldo said:
I think it automatically sets the resolution based on the TV/monitor, try a different one?
TMK, the slider has nothing to do with the kernel.
Click to expand...
Click to collapse
I would do that but i only have a panasonic 50" plasma it's a 600hz 1080p it p50x50b model,there are 2 variants of it a hd ready and a 1080p model,i know it's the 1080p model as i used blu ray and xbox 360 and a wiiu etc in 1080p modes so it's definately not 720p only on my model.
I still think it is possible to reinstate that hdmi resolution slider though? I would love for someone to find a fix for that to bring back the slider though.
It also has nothing to do with the overscan as that's off,and the guy said it's an argument between the console's os and the tv,but maybe if i had an option to change resolution within the console when in operation it would ammend this,resolution changer pro works then looses usability eventually and it's awkward and time consuming to get that to work,only for it to stop after a time?
There is no forced hdmi resolution setting in the tv menu unless of course there is in engineer mode but all that seems to do when entered is show test and it's results coming up as ok,after testing it factory resets the tv as well so sick of trying that now.
Someone needs to get a custom rom made up with kitkat and 1080p natively set.
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
Unable to untar the tar.gz file. It says "tar: kernel/drivers/net/wireless/bcm43341/src/include/proto/p2p.h: Cannot open: Not a directory" and there are many lines like this. Tried everything from sudo, sudo -s, chmod, chown....
Also it says cannot mkdir: is not a directory
Its a .h and .c files ofcourse they aren't directories! Its not letting me execute make without errors since my source is like crap crawling with this "NOT A DIRECTORY"
Nothing is working. Command used was tar xvfz mojo-jb-kernel.tar.gz with many combinations and OS is Ubuntu 12.04 LTS 64 bit...
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
Can you help me. Is there any other place from where I can get source?
Thanks in advance..
Kingshoo said:
Can you help me. Is there any other place from where I can get source?
Thanks in advance..
Click to expand...
Click to collapse
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
gwaldo said:
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
Click to expand...
Click to collapse
It doesn't time out but it says some .c and .h cannot open: Not a directory when I use tar to extract it. Then I thought that I should install something else to extract and tried ARC. It extracted and then the same message box as appeared in windows 7 OS "file already exists cancel or overwrite"
I then said overwrite and then I get the extracted package. I just want to ask you that when you extracted it did you got any errors? What procedure you used to extract it? I downloaded twice with same results...
gwaldo said:
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
Click to expand...
Click to collapse
OK as per your suggestion I used wget c and the address. That gave me again the same file and upon extracting it I am getting same errors.
May be that the file isn't corrupted as you can extract it and its possible that I am doing something wrong in extraction..
I tried to create the kernel from sources and got a make error, to remove that I must delete a line in the make file (Line no 603) and after that I can successfully compile the zimage. But the issue is that after completing the procedure for boot.img file the original and compiled one has a difference of 0.1 MB and device don't boot with the newly compiled boot.img
Please if you can provide me with the steps on how you exctracted it and which OS you are using?then it will be really helpful. Also can you please upload the makefile of kernel and config.gz file you are using to make the kernel...
One useful information that can prove that there is an issue in extraction:
Extracted content on windows OS with Administrator priviledges: 42889 items , 487.8 MB
Extracted content on Ubuntu with Tar and other utilities: 42692 items, 482.5 MB
gwaldo said:
Hey,
I suggest downloading with wget or a good download/ftp application if it's timeout on you.
It's not corrupted, it worked for me and the date stamp is still the same.
Click to expand...
Click to collapse
Seems like you are the only person who can help me as no one else seems to be active on MOJO development department. Sorry to disturb you again friend but you know I tried extracting on Android too and it failed there too!
I am completely exhaused with two days 24hrs of searching only extraction process. Please let me know if you successfully compiled and booted the kernel on your MOJO. If yes then I need more information from you as I had compiled the kernel but as I told you earlier it didn't worked... Please reply ASAP
Kingshoo said:
Seems like you are the only person who can help me as no one else seems to be active on MOJO development department. Sorry to disturb you again friend but you know I tried extracting on Android too and it failed there too!
I am completely exhaused with two days 24hrs of searching only extraction process. Please let me know if you successfully compiled and booted the kernel on your MOJO. If yes then I need more information from you as I had compiled the kernel but as I told you earlier it didn't worked... Please reply ASAP
Click to expand...
Click to collapse
Hi,
I'm in Aust. so there's a time difference.
I'm also about to leave on a 4week holiday and don't have my mojo dev stuff on my laptop.
I just used tar -vxzf filename
I think the only errors were a bad lsymbolic links which arent required.. from memory I could be wrong.
If you read the other threads here, I and someone else explain how we got the kernel compiled and yes it works fine.
http://forum.xda-developers.com/showthread.php?t=2691985&page=2
You dont use their makefile you recreate it .
If this is your first linux kernel or even android kernel, it's a tricky process and it takes time research all the steps.
Good luck
gwaldo said:
Hi,
I'm in Aust. so there's a time difference.
I'm also about to leave on a 4week holiday and don't have my mojo dev stuff on my laptop.
I just used tar -vxzf filename
I think the only errors were a bad lsymbolic links which arent required.. from memory I could be wrong.
If you read the other threads here, I and someone else explain how we got the kernel compiled and yes it works fine.
http://forum.xda-developers.com/showthread.php?t=2691985&page=2
You dont use their makefile you recreate it .
If this is your first linux kernel or even android kernel, it's a tricky process and it takes time research all the steps.
Good luck
Click to expand...
Click to collapse
I have gone through with the links you provided already and I understand every bit of conversation. Yes I am new to kernel compiling but its reasonably understandable.
I respect your valuable answer no matter when you reply since you have a minute for me and don't worry about TimeZone differences as I am not in a great hurry, I just don't wish to waste time on errors for which I ain't responsible
OK I tried compiling modules for which I had to compile the kernel to get the module.symvar file and "THE MODULES WORK!" that too with the Default kernel Makefile and ofcourse my own module Makefile.
"You dont use their makefile you recreate it" this line you wrote.. What do you mean by that??
I mean were you talking about the kernel Makefile or our own module Makefile, Please clear me here? As far as I know the Kernel Makefile should be the same when only compiling the stock kernel as that is my purpose "JUST TO COMPILE THE STOCK KERNEL"...
My compiled kernel boots but just shows a black screen! I don't want to spoil your holidays sincerely but if some help I can get from you then I will be able to relieve me from this burden
Hmm got it compiled finally even after that make issue with -k flag to make
Also all I needed was ramdisk from latest OTA and not the one from the kernel. That was the issue with kernel booting but it freezing at blank screen...
RESOLVED :highfive:
Kingshoo said:
Hmm got it compiled finally even after that make issue with -k flag to make
Also all I needed was ramdisk from latest OTA and not the one from the kernel. That was the issue with kernel booting but it freezing at blank screen...
RESOLVED :highfive:
Click to expand...
Click to collapse
Glad you got it working.
Re the makefile, I think you have to run config first to check your systems compilers/linkers/etc which then creates the makefile.
:highfive:
Mad Catz Rich said:
Apologies for the delay in getting this released. Here's the kernel source:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-jb-kernel.tar.gz
Click to expand...
Click to collapse
is there any reason this is done via some random ftp server and not some place like github/bitbucket with better management? or heck even sourceforge would be an improvement.
is that account for developer outreach? are there any datasheets on the components used in the device? sony does a beta program for updates on their flagship devices have you considered doing something similar where people can grab images and help test updates? ever think about tossing the device trees up for aosp to help encourage a porting of 3rd party roms and spread the community?
the nook color and touchpad being hack and having Cyanogenmod and the like being ported to it drove sales up, i would imagine having a hackable android console that isnt some no name chinese brand would probably do decent. unfortunately now with android tv you guys have some serious competition on the horizon, its a matter of how you go from here and try to make the most of it so everyone already has your product and doesnt need another.
edit: i also see there is several updates yet only one kernel source... any chance of updated source?
@Mad Catz Rich
The new update (205-TS) has a new kernel build of May 2nd.
Any chance that can be put on the server?
from http://madcatz.com/mojo/en-ca/
Ready to Root
As any Android power-user knows, the best way to get the most out of your device is to root it. Root access opens up all sorts of options including adding custom keymapping capabilities and installing custom ROMs. Mad Catz provides a short step-by-step guide to rooting, and our tech support team is ready to help.
The best part – rooting won’t void your warranty.
Click to expand...
Click to collapse
Please help, tech support team!
We need custom ROMs!
make kernelversion
3.4.35
Based on the first 5.1.1 sources, version OI5
Modifications:
SELinux unlocked
Disabled protection does not allow to boot the OS(disabled at the level of Linux kernel)
Permissive mode is set automatically at boot (without the possibility to switch back to enforce)
Before(you can do it after flash,but recommended before) installing the kernel required go to build.prop,find ro.securestorage.support and set the value to false. System may forget your WiFi passwords after flash custom kernel.
SecurityLogAgent has to be removed or frozen.
Flash kernel in odin.
v2 - SELinux fix.
Download: Google Drive
Sources: Google Drive
Blue cat said:
Based on the first 5.1.1 sources, version OI5
Modifications:
SELinux unlocked
Disabled protection does not allow to boot the OS(disabled at the level of Linux kernel)
Permissive mode is set automatically at boot (without the possibility to switch back to enforce)
Before installing the kernel required go to build.prop,find ro.securestorage.support and set the value to false. System may forget your WiFi passwords after flash custom kernel.
Flash kernel in odin.
This is my first kernel which I create on Linux. I hope everything will be working stable.
Download: Google Drive
Click to expand...
Click to collapse
Thank you - I flashed it as per your instructions. Seems to have worked fine and it's showing it as running as permissive!
Hi,
I made mine for my rom, but yours is good too.
Thank you for the comunity
Re...
Oops problems !! security notification
Alan-B said:
Hi,
I made mine for my rom, but yours is good too.
Thank you for the comunity
Re...
Oops problems !! security notification
Click to expand...
Click to collapse
I think you should remove ALL knox apk,because i never not seen security notifications on my device.
This kernel have only 2 changes.
security/selinux/Makefile and security/selinux/selinuxfs.c
Blue cat said:
I think you should remove ALL knox apk,because i never not seen security notifications on my device.
This kernel have only 2 changes.
security/selinux/Makefile and security/selinux/selinuxfs.c
Click to expand...
Click to collapse
Hi,
With my boot.img I have no this message! It is when I made out a will your that and come this message!
NB:
Your Boot and all the eliminated knoks!! (Rom deodex 5.1.1)
Alan-B said:
Your Boot and all the eliminated knoks!! (Rom deodex 5.1.1)
Click to expand...
Click to collapse
Ok,I found a solution.
You need to remove SecurityLogAgent
Bluecat, thanks for this! I wonder if you know what differences exist between the P605 and the P607T. Also, did you use the EUR_LL source from Samsung's opensource portal? Its strange that they already have the source out for the P605, but nothing yet for the P607T which received the update first. Makes me think maybe the code base is the same and its only the bloatware bundled by the carrier that differs?
I am also curious to just learn and get my hands dirty with this. Can you share the Makefile for this kernel, or just point towards the guide you used (assuming you used one) to compile this?
karthikrr said:
Bluecat, thanks for this! I wonder if you know what differences exist between the P605 and the P607T. Also, did you use the EUR_LL source from Samsung's opensource portal? Its strange that they already have the source out for the P605, but nothing yet for the P607T which received the update first. Makes me think maybe the code base is the same and its only the bloatware bundled by the carrier that differs?
I am also curious to just learn and get my hands dirty with this. Can you share the Makefile for this kernel, or just point towards the guide you used (assuming you used one) to compile this?
Click to expand...
Click to collapse
Sorry,but i dont know differences between the P605 and P607T.
Yes,sources SM-P605_EUR_LL_Opensource.zip and version OI5.
If you want check have code 607 and 605 differences or not you should check checksum both original zImage(linux kernel). Extract them from both boot.img and compare.
Version 2 use standart selinux permissive way used by mostly kernel developers,it's have many changes in code now and it's will be very long to explain how to change to permissive,just use my sources available now in first post and compare them with original sources.
If you talk about how to compile kernel...was use many guides and other forums...hard part was only create .config file
Blue cat said:
Sorry,but i dont know differences between the P605 and P607T.
Yes,sources SM-P605_EUR_LL_Opensource.zip and version OI5.
If you want check have code 607 and 605 differences or not you should check checksum both original zImage(linux kernel). Extract them from both boot.img and compare.
Version 2 use standart selinux permissive way used by mostly kernel developers,it's have many changes in code now and it's will be very long to explain how to change to permissive,just use my sources available now in first post and compare them with original sources.
If you talk about how to compile kernel...was use many guides and other forums...hard part was only create .config file
Click to expand...
Click to collapse
Will try to extract the zImage from the P607T boot.img. I do not have the P605 though, do you know if the stock boot.img is downloadable anywhere?
Thanks for uploading the source. I just finished downloading the original source from the opensource site, will compare the two and try to understand.
I do know how to complile a linux kernel, I meant can you share the .config file (not the makefile, as I wrongly stated earlier), so I can see what has changed across the entire kernel. Rather than just change one line directly in the config file to disable SELinux, I wanted to use make menuconfig and go through the whole process, just to learn more about android kernels. But since I do not know much about the hardware and driver requirements, wanted to see a stock .config as well as your changed .config to understand.
karthikrr said:
Will try to extract the zImage from the P607T boot.img. I do not have the P605 though, do you know if the stock boot.img is downloadable anywhere?
Thanks for uploading the source. I just finished downloading the original source from the opensource site, will compare the two and try to understand.
I do know how to complile a linux kernel, I meant can you share the .config file (not the makefile, as I wrongly stated earlier), so I can see what has changed across the entire kernel. Rather than just change one line directly in the config file to disable SELinux, I wanted to use make menuconfig and go through the whole process, just to learn more about android kernels. But since I do not know much about the hardware and driver requirements, wanted to see a stock .config as well as your changed .config to understand.
Click to expand...
Click to collapse
My config https://drive.google.com/file/d/0BxQroXyaGzZOSmdieTNVaFY3VjA/view?usp=sharing
Boot https://drive.google.com/file/d/0BxQroXyaGzZOVFZGZGs3YmloX2s/view?usp=sharing
I dont have original config,you can create your own on linux.
Blue cat said:
My config https://drive.google.com/file/d/0BxQroXyaGzZOSmdieTNVaFY3VjA/view?usp=sharing
Boot https://drive.google.com/file/d/0BxQroXyaGzZOVFZGZGs3YmloX2s/view?usp=sharing
I dont have original config,you can create your own on linux.
Click to expand...
Click to collapse
Brilliant! Thanks for sharing ... As and when I learn anything relevant to the issue of P605 vs. P607T, will update here.
Why does the wifi password get forgotten on every boot?
Any fix for that matter?
valexi said:
Why does the wifi password get forgotten on every boot?
Any fix for that matter?
Click to expand...
Click to collapse
Blue cat said:
Based on the first 5.1.1 sources, version OI5
Before installing the kernel required go to build.prop,find ro.securestorage.support and set the value to false. System may forget your WiFi passwords after flash custom kernel.
SecurityLogAgent has to be removed or frozen.
Flash kernel in odin.
Click to expand...
Click to collapse
Maybe you missed the update to the original post, the fix is as above, set securestorage to false. Since you have already flashed, you can still go to build.prop, make this change, reboot, and you should be fine.
karthikrr said:
Maybe you missed the update to the original post, the fix is as above, set securestorage to false. Since you have already flashed, you can still go to build.prop, make this change, reboot, and you should be fine.
Click to expand...
Click to collapse
I tried this. With ro.securestorage.support false. Still no WiFi passwords saved after reboot.
Other than that, this works great!
Xposed (for Samsung by wanam) works great!
valexi, the only thing Ive seen suggested in your case is to reflash the firmware. I do not know of any other solutions for this, because pretty much everybody with this problem seems to have solved it when they changed the securestorage thing.
BlueCat, I went ahead and compared checksums for the stock p607t and p605 kernels, they do NOT match. I also extracted the kernels themselves and the zimage files are of different sizes. I then compared the default config files of the P605_LL_EUR source with the only available source for the P607T, which is KK ... They are considerably different. I am of course going with the assumption that the core config for the kernel between KK and LL should not be TOO different, but of course, this is NOT a reliable test. Lastly, I should also say, the P607T source contained an insane number of config files in the Arch/Arm/configs folder, while the P605 source only had three files! I only compared the three that were common ... It seemed like the 607T has the config files for every possible version of the device, while the 605 one had very specific configs for that device only ... This I am speculating based on the fact that the 607T folder even had a msm8894_sec_l03ltmo_defconfig file in addition to the msm8894_sec_l03leur_defconfig file in the 605.
Will do more comparisons over the next few days, but it does seem like there are more changes under the hood between the 605 and the 607T than one would expect. I really wish samsung would release the source for the 607t, but if you check that page, there is just one single KK code there and nothing else, so it does not seem likely anytime soon
Blue cat said:
Ok,I found a solution.
You need to remove SecurityLogAgent
Click to expand...
Click to collapse
Re,
Ok remove SecurityLogAgent and folder Container it is ok...
But delete all other knox and Klm gives a problem with the playstor. (Certain protections cannot be erased)
Hey guys,
Great news around, especially with roms like Alan-B's. Thanks for sharing :good:.
Running 4.4, planning to update 5.x as soon as I'm sure I can run Linux Deploy (meaning the need of permissive kernel), though I can't find any intel about VTS (Virtual Terminal Support) enabled kernel. I've been looking for months a way to run framebuffered distros and looks like this is the solution.
I could try to make it myself but I have no experience in kernels, would someone mind give me a hand to get to this goal? At least give me a hint to "quickly" develop and try one, to see if it works and how well...
Don't even know if I'm looking the right way anymore, so thanks by advance for any help and again for the sharing :highfive:.
karthikrr said:
valexi, the only thing Ive seen suggested in your case is to reflash the firmware. I do not know of any other solutions for this, because pretty much everybody with this problem seems to have solved it when they changed the securestorage thing.
Click to expand...
Click to collapse
But when I reflash the firmware how can I set securestorage BEFORE installing permissive kernel as I don't have root to change build.prop?
valexi said:
But when I reflash the firmware how can I set securestorage BEFORE installing permissive kernel as I don't have root to change build.prop?
Click to expand...
Click to collapse
You can't. Reflash, root, edit build.prop, reboot, set wifi password once again, reboot, it SHOULD be fine. If its not after this sequence, Im not sure what else may work. Every case of this particular problem that I've seen was resolved with this solution.
Luckily I didn't reflash yet. I checked again build.prop and securestorage was true. For some reason it didn't stick first time.
I edited it again and now WiFi works as intended. So I can say that this solution works. Great kernel.
Sent from my ONE A2003 using Tapatalk