Database Info

(DEVS)Kernel Config from Mytouch 2.1/ Fender LE

Not really sure what this does..
Its the kernel config file from the fender 1.6 dump. No other rom will use touch screen abilities with this phone except stock so Cursordroid concluded the kernel may be different.
If anyone can use this to make a kernel, or port roms it would be greatly appreciated. Sux having a rooted phone while having to use the stock rom lol
If I knew how to do it I would hop on it... but I is not as smarts as youu guyz
Remove .zip from end of file
EDIT- When the new Mytouch 1.2 comes out in the next couple months, this will be the same build included on it. so nothing like ahead start lol

crypysmoker said:
Not really sure what this does..
Its the kernel config file from the fender 1.6 dump. No other rom will use touch screen abilities with this phone except stock so Cursordroid concluded the kernel may be different.
If anyone can use this to make a kernel, or port roms it would be greatly appreciated. Sux having a rooted phone while having to use the stock rom lol
If I knew how to do it I would hop on it... but I is not as smarts as youu guyz
Remove .zip from end of file
EDIT- When the new Mytouch 1.2 comes out in the next couple months, this will be the same build included on it. so nothing like ahead start lol
Click to expand...
Click to collapse
Going to look at this - thanks

will be so happy if this is an easy fix. Thanks Wes. Didnt even occur to me the changes for the 3.5mm jack output would cause problems

wesgarner said:
Going to look at this - thanks
Click to expand...
Click to collapse
See a few things different in the config
Will have to port over the 3.5mm headphone drivers

Try this one out - should work on an WG-Kernel builds aka WG-Build and maybe a couple others, not sure
But should let you test real quick if you through my build on there then fastboot this boot.img
Oo it technically works on CM builds too - but nothing would really work lol (at least the touchscreen would)
I am betting this won't work but eh worth a try lol

crypysmoker said:
will be so happy if this is an easy fix. Thanks Wes. Didnt even occur to me the changes for the 3.5mm jack output would cause problems
Click to expand...
Click to collapse
lol yea requires new drivers to get it to work - they are on the MSM .32 git, I will have to backport them - no biggie for that I'm sure

wesgarner said:
Try this one out - should work on an WG-Kernel builds aka WG-Build and maybe a couple others, not sure
But should let you test real quick if you through my build on there then fastboot this boot.img
Oo it technically works on CM builds too - but nothing would really work lol (at least the touchscreen would)
I am betting this won't work but eh worth a try lol
Click to expand...
Click to collapse
lol Worth a shot.. I already got through the dangourus stuff. I use yours as it is on my spare G1 so no worries about it on here. Ill let you know the outcome.

wesgarner said:
Try this one out - should work on an WG-Kernel builds aka WG-Build and maybe a couple others, not sure
But should let you test real quick if you through my build on there then fastboot this boot.img
Oo it technically works on CM builds too - but nothing would really work lol (at least the touchscreen would)
I am betting this won't work but eh worth a try lol
Click to expand...
Click to collapse
Argh..
Flashed your newest build, then tried to flash the boot.img.zip file with verification failed. then onto remember that I have the perfected spl on when I tried to flash it lol. Without having a physical keyboard like the g1, and needing to flash the boot.img before boot... is there another way?
Also find that since we had to use a 32B recovery on a 32a phone... nandroid will not work in recovery. Guess ill try fastboot laster

crypysmoker said:
Argh..
Flashed your newest build, then tried to flash the boot.img.zip file with verification failed. then onto remember that I have the perfected spl on when I tried to flash it lol. Without having a physical keyboard like the g1, and needing to flash the boot.img before boot... is there another way?
Also find that since we had to use a 32B recovery on a 32a phone... nandroid will not work in recovery. Guess ill try fastboot laster
Click to expand...
Click to collapse
Try:
adb remount
adb shell
flash_image boot /sdcard/boot.img
reboot
EDIT: I tried that and this is what I got:
mtd: write error at 0x00140000 (Out of memory)
mtd: verification error at 0x00140000 (Out of memory)
mtd: wrote block after 1 retries
mtd: write error at 0x00160000 (Out of memory)
mtd: verification error at 0x00160000 (Out of memory)
mtd: wrote block after 1 retries
darn

Ok... would have just built a kernel for this that should (theoretically) work based off the nexusone kernel...
My battery just died on my laptop
Was a good idea! lol
Will compile in a little while and post

no rush at all guys and I thank those of you that hopped on this much quicker then I expected. eminds me of the old dreamcast homebrew days where everyone actualy worked together rather then who gets the most credit for what.
We got the hard part done.. now onto the fun part. And, at the same time if we dont get a full rom going by the OTA 2.1 update, at least we will have straight dumps off the phones lol

use the custom kernel, and post the dmesg

Compiling the new kernel now lol - sorry for the delay
Will build it into my current git beta build of y-2.7 lol

wesgarner said:
Compiling the new kernel now lol - sorry for the delay
Will build it into my current git beta build of y-2.7 lol
Click to expand...
Click to collapse
Awesome. If possible please let me know once finished for testing.
I cant belive at how many people start bugging you for stuff when your the first to find something. Honestly, My gtalk friends grew 10fold by 3am, of which 6 I had to explain what "stock rom" meant lol How many times can I hear "but whats the point if it doesnt look different" before I want to smackanoob lol

HTC has to release this Kernel source too.

maxisma said:
HTC has to release this Kernel source too.
Click to expand...
Click to collapse
Awwww. noo BOOOO dont tell me that lol. I mean, its fine now because im still using my g1 as to no hurt my wittle fender baby lol.
But once the new mytouch comes out there will be a flood of noobiness over this. But at least I got it out thier early so the good ones can have at it.
By the way, LOVE the quote in yoru sig. Kinda like question I used to get asked back in Xbox 1 modding days. "where is bios and can I take it out?" "I type FTP into my web browser and it wont see my xbox" "

maxisma said:
HTC has to release this Kernel source too.
Click to expand...
Click to collapse
Actually looks like the kernel source is active on the android-msm-2.6.29-nexusone

wesgarner said:
Actually looks like the kernel source is active on the android-msm-2.6.29-nexusone
Click to expand...
Click to collapse
Ouuuu. so if its running on same/similar kernel to Nexus one... 2.1 will run with ease.. at least the OTA version will lol.
But, at same time, lot of people going to be ad they grabbed up that nexus one.

wesgarner said:
Actually looks like the kernel source is active on the android-msm-2.6.29-nexusone
Click to expand...
Click to collapse
You could be right..
http://android.git.kernel.org/?p=ke...118;hb=refs/heads/android-msm-2.6.29-nexusone
-rwxr-xr-x
board-sapphire-gpio.c
blob | history | raw
-rwxr-xr-x
board-sapphire-h2w.c
blob | history | raw
-rwxr-xr-x
board-sapphire-keypad.c
blob | history | raw
-rwxr-xr-x
board-sapphire-mmc.c
blob | history | raw
-rwxr-xr-x
board-sapphire-panel.c
blob | history | raw
-rwxr-xr-x
board-sapphire-rfkill.c
blob | history | raw
-rwxr-xr-x
board-sapphire-wifi.c
blob | history | raw
-rwxr-xr-x
board-sapphire.c
blob | history | raw
-rwxr-xr-x
board-sapphire.h
blob | history | raw
Click to expand...
Click to collapse

crypysmoker,
If we are rocking the same kernel off of the nexus one, what does that mean for us in the future? Are we going to be able to do things quite similar?

A fix for POLA100, Haret and waiting for notbusy error

I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
It also seems that this error is caused by the double vibration at the beginning of boot process and was solved once by paipo (see this post) by commenting out the vibration part and rebuilding. But those kernel is outdated and misses some latest features and fixes.
So I did the same as paipo but with the latest kernel from the git repository (as of 19.07.2010, revision d5d0a56fae6df779443a82e2d90b7ec8097cb332). zImage is attached to this post. I'll try to update the kernel from time to time.
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post

Disabling the vibration and rebuilding the kernel yourself
So how do you do this?
First of all, follow the steps 1 to 4 of Building kernel For Vogue, Kaiser, and Polaris part from this guide to prepare your building environment.
Now you need to open the arch/arm/mach-msm/board-htcpolaris.c file in your favourite text editor.
Search for vibrate word (it was line 1019). You'll see something like this:
Code:
// vibrate
for (i=0; i<2; i++) {
while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
mdelay(150);
while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
mdelay(75);
}
Remove this part or replace with the following:
Code:
// vibrate
// for (i=0; i<2; i++) {
// while(msm_proc_comm(PCOM_VIBRA_ON,0)==-EAGAIN);
// mdelay(150);
// while(msm_proc_comm(PCOM_VIBRA_OFF,0)==-EAGAIN);
// mdelay(75);
// }
As you can see, all lines now start with two slashes.
Now follow step 5 from the guide, mentioned above. You'll see a menu.
Go to System Type and select Android Optimization accroding to your needs. Then select Exit, than again Exit, then Yes.
Now follow step 6 from the guide. This will take some time. At the end you should see:
Code:
Kernel: arch/arm/boot/zImage is ready
Copy zImage from arch/arm/boot folder to \Storage Card\andboot folder on your device and use it

I update this option in the kernel.
Now double vibration is disable by default.

You are great !!!
leppa said:
I think that this error needs no intorduction for POLA100 users who tried running latest Android kernels using Haret.
...
Please, note that the attached kernel image is optimized for Eclair (CONFIG_ECLAIR=y in .config or System Type/Android Optimization is set to Eclair in make menuconfig).
And yes, you can do it yourself. Just follow the guide in the second post
Click to expand...
Click to collapse
YOU ARE GREAT !!!
THANKS A LOT A LOT A LOT !!!
THIS EVENING I WILL TRY SURELY !!!!!!!
Only a question: Optimized for Eclair is equal to Optimize to FROYO ?
Can I use your zImage to Froyo RLS 11 ?
Thanks in advance.
Bye

This flag now do nothing, so it's indifferent

GGGGGGGGGGGGGGRRRRRRRRRRRRRRRRRREEEEEEEEEEEEEEEEEAAAAAAAAATTTTTTT !!!!!!
I Have Just tested zImage in attached files.
Froyo seems better reactive, more smooth and rock stable.
Thanks a lot ...
When Video Playback will be solved... I will flash immediately Froyo to give a new life to my Cruise!!!
Thanks thanks thanks!

@foxct2005 : you can flash it month ago!
All these problems are only for haret!

l1q1d said:
I update this option in the kernel.
Now double vibration is disable by default.
Click to expand...
Click to collapse
This change isn't yet in the git repository, is it?
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
The attached kernel images work as they did before - with double vibration on boot and "waiting for notbusy" error. To disable the double vibration (and get rid of the error) add board-htcpolaris.no_boot_vibration=1 to default.txt so this line:
Code:
set cmdline "board-htcpolaris.panel_type=1 ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
will look like this:
Code:
set cmdline "board-htcpolaris.panel_type=1 [COLOR="Red"]board-htcpolaris.no_boot_vibration=1[/COLOR] ppp.nostart=0 pm.sleep_mode=1 mddi.width=240 mddi.height=320 no_console_suspend clock-7x00.mddi=0xa51"
Adding this parameter is mandatory if you suffer from "waiting for notbusy" error.

big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!

leppa said:
I was thinking about how to make this option available to any user without having to recompile the kernel. And came up with the idea of the new kernel parameter. So I added board-htcpolaris.no_boot_vibration parameter.
Click to expand...
Click to collapse
Good idea!
I have long think why developers not added it to the cmdline.

Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..

DmK75 said:
Good idea!
I have long think why developers not added it to the cmdline.
Click to expand...
Click to collapse
I think, they have much more other, more serious, things to do
michasch said:
big thanks for that patch!
I started a new try with android and my polaris yesterday but froyo doesn't work (with haret). Now with this patch it work and even booting and boot logo is much faster on my Pola200! Great! Thanks!
Click to expand...
Click to collapse
nikiiv said:
Thank you, thank you, thank you..
I almost sold my Polaris in despair that this problem will never get fixed..
Click to expand...
Click to collapse
You're welcome
If this patch gets upstream, we will not need to rebuild the kernel every time a new build comes out. I already posted it in the Polaris Android Linux Kernel Development Project thread.

thanks leppa,
i tried the froyo one, but for me doesn't work. last days i used the last dzo one, it worked for 2 or 3 days, and now doesn't work again. the only zimage that works is the 29-04 one, but my battery doesn't like it so much

loscassapalle said:
thanks leppa,
i tried the froyo one, but for me doesn't work.
Click to expand...
Click to collapse
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.

leppa said:
What do you mean by that? Do you still get "waiting for notbusy" error?
If yes, did you add the kernel parameter board-htcpolaris.no_boot_vibration=1?
If no, than I can't help, cause this is the only thing I changed in the kernel.
Click to expand...
Click to collapse
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.

loscassapalle said:
maybe is not my problem...i can't see an error string, the problem is the animation at the start that never end.
Click to expand...
Click to collapse
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).

leppa said:
Then this is some other problem. Cause "waiting for notbusy" error occurs almost at the very beginning of the boot process (while text is running, before even "Hold down Volume Up or DPad..." message).
How long do you wait? At first boot the animation may run for five and even more minutes. Try reinstalling from scratch (i.e., wiping system and data partitions).
Click to expand...
Click to collapse
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
the animation problem is strange. the zimage of 29-4 works, the animation ends in a few seconds, but the battery life is very short. the last dzo zimage worked for a couple of days, then i had the same problem after a softreset...and this one is the same...
EDIT: now it works... lol

loscassapalle said:
i checked now, i also have this string that you said (now i'm using the froyo image you uploaded in 8# post).
Click to expand...
Click to collapse
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
loscassapalle said:
EDIT: now it works... lol
Click to expand...
Click to collapse
So, it started working?

leppa said:
I didn't test the Froyo image, cause I'm playing with Eclair. Does it vibrate on start? It shouldn't or you forgot to put the kernel parameter.
So, it started working?
Click to expand...
Click to collapse
i don't know how to edit the zimage...but now it works...i didn't change anything...

loscassapalle said:
i don't know how to edit the zimage...
Click to expand...
Click to collapse
You don't need to. I was talking about editing default.txt as I described in post 8.

[TOOL][All devices & OS] Fastboot Commander [v.1.51][UPD 15 AUG 2011]

Don't forget to hit that "thanks"/Donate button or check out my APK(s) installer tool found in my signature :0)
Updated to version 1.51.
Added: Conversion of BMP images to ready-to-flash splash files on all 3 systems.
Modified: Graphical layout is now more in sync in all 3 systems.
Modified: All tooltips are now corrected and fully helpful :0)
Hi everyone.
This is a tool written in JAVA for easier flashing of the following partitions:
Radio, hboot/spl, recovery, system, boot, userdata, kernel and splash.
It can do much more, like:
Conversion of 24bit BMP images to ready-to-flash splash files.
Erase/wipe multiple or single partitions.
Reboot device either to system or fastboot.
Print of device info.
Flash of kernel.
Possible to run custom fastboot commands instead of using cmd/shell.
Flash of signed zip files (E.g. fastboot flash zip myzip.zip)
The above(Flash of signed zip) should not to be confused with flashing of custom rom files!
It's only meant for signed HTC roms with complete system layout.
Flash multiple files in one click by using custom folders and tags.
It's basically a GUI over most fastboot commands.
It works for Windows, Linux and Mac.
No need for Android SDK, the jar-file has all needed files bundled!
It's well tested and have more than +10000 users.
It works for all devices which has fastboot :0)
Any feedback is appreciated.
Requirements:
Min 30 % battery!
Engineering hboot/spl OR S-OFF!
Do not reboot or shutdown, if you ever get an error flashing the radio or the hboot/spl!
Ask here for help if it happens!
Instead of having to maintain multiple OPs, i have decided to redirect the OP to the desire forum. It's only the facade and nothing else. All questions and ect regarding the Desire HD will still be on this thread :0)
The tool is the same and will work on any device which have fastboot mode.
LINK:
http://forum.xda-developers.com/showthread.php?t=1193915

nice tool : )
thank you for your work!

Should add zimage partition flashability as well

What do you mean?
zimage = ?

This is Absolutely Best Tool for HDHD! Needs visibility in this forum...

Awesome tool mate, should make things easier for new people

Glad you like it :0)

Nice work

mumilover said:
What do you mean?
zimage = ?
Click to expand...
Click to collapse
kernel mumi

capychimp said:
kernel mumi
Click to expand...
Click to collapse
Ohh... thx O' great rom master :0)
Hope life is treating you well :0)
For the kernel flashing part... the tool is just a graphical interface build on top of the fastboot binary. So i can only do what fastboot can do.... so no kernel flashing or the like..
I think i have milked every thing i could from the fastboot binary :0)

hehe well nice to see your still here mumi, been awhile

good job
thanks for your nice work

capychimp said:
hehe well nice to see your still here mumi, been awhile
Click to expand...
Click to collapse
Some bastards stole my laptop and magic device... so i have busy lately securing my home and changing all my passwords etc...
But i'm hot again.

Flashed new Radio without any problems, great prog.
Thnx

mumilover said:
Ohh... thx O' great rom master :0)
Hope life is treating you well :0)
For the kernel flashing part... the tool is just a graphical interface build on top of the fastboot binary. So i can only do what fastboot can do.... so no kernel flashing or the like..
I think i have milked every thing i could from the fastboot binary :0)
Click to expand...
Click to collapse
Erm, correct me if i'm wrong, but sometime i/we flash the kernel via fastboot.. "fastboot flash zimage zImage"
So, i think, it can be implemented in your tool.. good job anyway..

so if i want to flash a splash image what do I name that as ??, thanks.

vtec303 said:
so if i want to flash a splash image what do I name that as ??, thanks.
Click to expand...
Click to collapse
Normally it's called splash1.nb0 (that's nbZERO).

SAPPH1RE said:
Erm, correct me if i'm wrong, but sometime i/we flash the kernel via fastboot.. "fastboot flash zimage zImage"
So, i think, it can be implemented in your tool.. good job anyway..
Click to expand...
Click to collapse
I DID NOT KNOW THAT... Just to be sure, can anyone confirm that!
If it's confirmed then i will implement it in 2 min :0).... maybe 2.5!

To flash a kernel, you can use
fastboot flash zimage c:\zimage
Sent from my Desire HD using Tapatalk

Thx for the confirmation ( i used Google to double check anyway :0)
I will add it as soon as possible... i cannot test it though :0|
The bastards stole my magic device :0(
Anybody here willing to test ( it will be a piece of cake to make the functionality, i have the code, just have to modify a very small portion). If there is anybody, just post here or pm me :0)

Stupid SU: Galaxy S 4 stock+root helper

Hi guys!
As some of you must have noticed, latest Samsung GT-I9500 firmwares carry a kernel configuration supposed to prevent SETUID privilege elevation.
Stock unmodified firmware with root is my preferred setup but also a strong dependency for all my development, for me this change is a massive setback if not a dealbreaker.
While poking around I found in about an hour something weird that reveled being a vulnerability, so I created a little thing to make it useful for now.
README:
Stupid SU: Galaxy S4 root helper by François SIMOND aka @supercurio
Circumvent an extremely weak false-security "Anti Root" mechanism implemented
on latest Samsung Galaxy S4 devices (on both Exynos and Qualcomm versions)
Preventing proper root function on official firmware breaks all my Voodoo apps
requiring stock+root and is a move that's hostile to both users and developers.
Samsung security might be embarassed by this proof of concept, as it defeats
their mechanism in a single line... not even with complex ARM assembler
but *one* line of shell script.
However, the goal here is to show Superuser solutions developers how to
deal with those devices for now, and provide a working solution to people who
bought a Galaxy S4 expecting to root it cleanly and easily but cannot.
This proof of concept is slightly slowing down Superuser calls, but its
"plain text" implementation has the merit of showing how stupid this exploit is.
SELinux configuration stays unmodified and active.
Features:
- Detect and supports both SuperSU and Koush's Superuser
- Installs Super SU binary by default
Make sure you have one of those Superuser apps installed:
- https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
- https://play.google.com/store/apps/details?id=eu.chainfire.supersu
Root feature doesn't rely on a "StupidSU kernel" which is only an installer.
Feel free to flash back Samsung's original boot.img from their official firmware
after booting at least once.
Important Note:
This "exploit" is so lame that it will be fixed in no time, making updated S4
a pain to root again.
I wish Samsung will reconsider their "Anti Root" approach, which is damageable
in every regard and defective by design as demonstrated here.
Also, I'm simply not interested developing for and promoting devices from
manufacturers hostile to developers: It's just a waste of valuable time.
Click to expand...
Click to collapse
INSTALL
1/ copy rooting/ directory in your initramfs
Make sure "root.sh" file is has an executable permission (chmod 744 recommended)
2/ Add those lines at init.universal5410.rc end:
# Stupid SU
service rooting /stupidsu/root.sh
class main
user root
group root
oneshot
3/ Assemble your initramfs with the associated Samsung official kernel binary
of choice in a regular boot image
4/ flash as boot.img
5/ At each boot, Superuser app are detected automatically and su binary adjusted
accordingly.
Click to expand...
Click to collapse
Source code
On GitHub
License
Kernels downloads, only for demo purposes of the concept, you can flash back original Samsung boot.img once rooted
GT-I9500 Stock + root StupidSU v4 UBUAMDE
GT-I9500 Stock + root StupidSU v4 XXUAMDK
GT-I9500 Stock + root StupidSU v4 XXUAME1
What's next
Owners of Qualcomm Galaxy S 4 devices experiencing the same dificulties with Samsung the anti root strategy might want to try this method, please let me know if you're ready for some experimentations.

Supercurio pleas add thraed t General section i think ther well bee lots of testers for i9505.thx for suport
Sent from my LG-P500 using xda app-developers app

Going to try this on latest LE1 stock kernel now .....thread is in correct section
edit: did not work on LE1 kernel. I will try once again. DId any one tried the MDK kernel..I am having again the problem with SU binaries installation..
Edit: Thanks bro. working on ME1 kernel now. Did mistake while doing tar. Appreciate it! Root is working fine but cant update the binaries of Supersu, still the root works fine.

Here comes the master welcome to SGS4 development forum mate.. (rahulzeven from twitter here )

So the BEST thing's just happened?!:laugh::good:

i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.
Download Link
Edit: New file uploaded

grgsiocl said:
i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.
Download Link
Click to expand...
Click to collapse
Thanks fo much! Will Titanium Backup work on this kernel?

Hope chainfire will start working on mobileOdin soon. So much easier to flash than.
... tapat*lked

GSeeker said:
Thanks fo much! Will Titanium Backup work on this kernel?
Click to expand...
Click to collapse
wrong file uploaded. Please download the same in 5 minutes. Uploading is on and the kernel date should be MAY 04
---------- Post added at 12:33 PM ---------- Previous post was at 12:28 PM ----------
GSeeker said:
Thanks fo much! Will Titanium Backup work on this kernel?
Click to expand...
Click to collapse
it should work as i dont use titanium backup and instead i use gobackup pro and it works fine anyway

MDK from OP working good, thanks

grgsiocl said:
i repacked the kernel of Samsung-Updates.com-KERNEL-GT-I9500-XSE-I9500XXUAME1-1367637350 using supercurio method. Root works fine. All we need to is install it from ODIN and dont update the binaries of supersu.
Download Link
Edit: New file uploaded
Click to expand...
Click to collapse
I'm trying to repack the kernel of korean gs4,
but I am a noob in kernel devs.
I can edit ramdisc, but fist trying in initramfs, zImage.
Is rooting directory means both root.sh and files(folder)?
and paste them on first class route?
hope you give some advices.. thanks

aslak89 said:
I'm trying to repack the kernel of korean gs4,
but I am a noob in kernel devs.
I can edit ramdisc, but fist trying in initramfs, zImage.
Is rooting directory means both root.sh and files(folder)?
and paste them on first class route?
hope you give some advices.. thanks
Click to expand...
Click to collapse
when you unpack the kernel you will have two folders one is ramdisk and other one is split_img (zimage). You need to copy the folder stupidsu folder in ramdisk and modify the init.universal5410.rc as per OP stated and repack the image

grgsiocl said:
when you unpack the kernel you will have two folders one is ramdisk and other one is split_img (zimage). You need to copy the folder stupidsu folder in ramdisk and modify the init.universal5410.rc as per OP stated and repack the image
Click to expand...
Click to collapse
then, is not necessary to recompile zImage?
ok I m going to try it right now, thank you grgsiocl

muhamet said:
Supercurio pleas add thraed t General section i think ther well bee lots of testers for i9505.thx for suport
Click to expand...
Click to collapse
Yes in fact I was hesitating, but as soon as someone is ready to assist me to try on a Qualcomm device (I9505 or T-Mobile Galaxy S4) I'll make a thread here too.
grgsiocl said:
Going to try this on latest LE1 stock kernel now .....thread is in correct section
edit: did not work on LE1 kernel. I will try once again. DId any one tried the MDK kernel..I am having again the problem with SU binaries installation..
Edit: Thanks bro. working on ME1 kernel now. Did mistake while doing tar. Appreciate it! Root is working fine but cant update the binaries of Supersu, still the root works fine.
Click to expand...
Click to collapse
Great then

aslak89 said:
then, is not necessary to recompile zImage?
ok I m going to try it right now, thank you grgsiocl
Click to expand...
Click to collapse
The point here is to have stock (unmodified Samsung binary) kernel running, with associated modules and no other modification.
Which gives you several usage options:
keep the StupidSU stock+root kernel (same kernel binary, same kernel modules, only very slightly initramfs scripts) that will auto-root depending on which Superuser APK you installed
you can flash back the official kernel and still enjoy root the same.

supercurio said:
The point here is to have stock (unmodified Samsung binary) kernel running, with associated modules and no other modification.
Which gives you several usage options:
keep the StupidSU stock+root kernel (same kernel binary, same kernel modules, only very slightly initramfs scripts) that will auto-root depending on which Superuser APK you installed
you can flash back the official kernel and still enjoy root the same.
Click to expand...
Click to collapse
Thank you for awsering
then I repacked my kernel but still not work.
copyed stupidsu and edited init.universal5410.rc in ramdisk and repacked boot.img.
I guess permission is the thing,
attach my shots
hope you loot at once.
Sent from my SHV-E300S using XDA Premium HD app

walda said:
Hope chainfire will start working on mobileOdin soon. So much easier to flash than.
... tapat*lked
Click to expand...
Click to collapse
He will after he will come back from his vacation.

I'll look into a fixed CF-Auto-Root for the I9505 as soon as I'm back on Sunday. I imagine that will be tested by Sunday evening, with a I9500 test version available sometime Monday. If all is well
In StupidSU environment and for this initial release Koush's Superuser app would
be preffered as SuperSU main UI refuses to launch because it cannot detect its
original su binary. Aside from that both work as expected.
Click to expand...
Click to collapse
This is because you're not installing the backup su binary. The UI app detects this is missing and triggers an update. Bug in StupidSU

aslak89 said:
Thank you for awsering
then I repacked my kernel but still not work.
copyed stupidsu and edited init.universal5410.rc in ramdisk and repacked boot.img.
I guess permission is the thing,
attach my shots
hope you loot at once.p
Click to expand...
Click to collapse
Alright I'm adding some logging in my scripts so you'll be able to see what's happening − or not

supercurio said:
Yes in fact I was hesitating, but as soon as someone is ready to assist me to try on a Qualcomm device (I9505 or T-Mobile Galaxy S4) I'll make a thread here too.
Click to expand...
Click to collapse
Brilliant news!!!! Thanks a LOT!!
Let's make it work!! It will be AWESOME if I could use latest STOCK Kernel in my ROM's......
I'll give you a hand

[HELP NEEDED] [S7 SM-G930FD] stuck on boot animation after flashing boot.img

Hi all,
Im trying to flash a custom built kernel on a g930fd device running android 6.0.1.
ive did the following steps:
built the kernel - the source matches with the rom on the device
replaced the out Image using AIK
created a flashable zip and tried to instal it via TWRP.
another steps ive tried as sanity checks, ALL RESULTED IN BOOT ANIMATION LOOP:
1. dd out the boot.img form running device, dd that boot.img back to /dev/block/platform/*/*/BOOT
2. flash boot.img with odin
3. built dtb and Image and flashed in using Lazyflasher
IF SOMEONE KNOWS WHAT COULD BE THE PROBLEM, ILL APPRECIATE ANY HELP , THANK YOU.
@osm0sis i hope maybe you can help me with a valuble input thanks in advance!

Where's your source?

djb77 said:
Where's your source?
Click to expand...
Click to collapse
i got it from samsung opensource

qroot0 said:
i got it from samsung opensource
Click to expand...
Click to collapse
You do realise you still have to modify it in order to get it to work properly.
So where is YOUR source code? What's your github link?

djb77 said:
You do realise you still have to modify it in order to get it to work properly.
So where is YOUR source code? What's your github link?
Click to expand...
Click to collapse
Sorry,
heres the link:
github.com/IgalGokhman/8890-6.0.1-custom-kernel
Ive reverted the changes i made to the defconfig.
BTW, Its my first time building a kernel for samsung device, so im not sure about all the chhanges i need to make in order to run it on the device.
Ive read a lot through xda and othher forums but the majority of them just saying: run make and install using updater-script...

qroot0 said:
Sorry,
heres the link:
github.com/IgalGokhman/8890-6.0.1-custom-kernel
Ive reverted the changes i made to the defconfig.
BTW, Its my first time building a kernel for samsung device, so im not sure about all the chhanges i need to make in order to run it on the device.
Ive read a lot through xda and othher forums but the majority of them just saying: run make and install using updater-script...
Click to expand...
Click to collapse
Well, I really needed to see what changes you made to start with, because all I have in front of me now is clean source.
Most of us use a build.sh script of some sort which builds the zimage, dtb, and ramdisk. My script does it all, builds kernel and zip.
Here's my old MM kernel that you can have a look at:
https://github.com/TheGalaxyProject/tgpkernel-s7-mm
If you use any of this please give credit

djb77 said:
Well, I really needed to see what changes you made to start with, because all I have in front of me now is clean source.
Most of us use a build.sh script of some sort which builds the zimage, dtb, and ramdisk. My script does it all, builds kernel and zip.
Here's my old MM kernel that you can have a look at:
https://github.com/TheGalaxyProject/tgpkernel-s7-mm
If you use any of this please give credit
Click to expand...
Click to collapse
Thanks I’ll take a look.
I do have a build script, eventually I have an Image and a dtb.image, from both of them I make a boot.img with AIK.
I tried to build the kernel with the config values I pulled from the device /proc/config.gz and with the “as is” values in the arch/arm64/configs/exynos_8890_defconfig
Both boot.imgs bootlooped the device