I recently build my own kernel and Im facing this issue which I could not sort.
My kernel just stucks or hangs at Galaxy Y logo which does not move further.
I am neither able to enter clockworkmode recovery in my kernel nor connect to adb.
But I can enter download mode and flash stock kernel using ODIN.
I built my kernel in Ubuntu 12.04 lts 64 bit environment using gcc 4.4.7
I tried a clean build also but still with no luck.
Can any one suggest me a solution to fix this in kernel.
And For Information : I can Install stock kernel using odin but I need to correct the errors in it.
Ramdisk error
I tried using stock ramdisk also but still no luck..
Related
My specs are as followed:
firmware 2.2
baseband version i9000UGJL2
Kernal Version 2.6.32.9 [email protected] #6
Mind you also that when I go on stock recovery, it says <3e>. I know that there is some troubles with that.
Well, you just have to flash a kernel that includes CWM (flash with Odin, put it into PDA-field, boot into download mode, connect your Galaxy with your PC and press 'Start').
Sent from your device
roma17 said:
My specs are as followed:
firmware 2.2
baseband version i9000UGJL2
Kernal Version 2.6.32.9 [email protected] #6
Mind you also that when I go on stock recovery, it says <3e>. I know that there is some troubles with that.
Click to expand...
Click to collapse
I had the same setup as you, including 3e recovery. I flashed speedmod k13e kernel for froyo, using odin, and it included cwm 2.5.1.0. Just leave it at that and you should always get into cwm when booting into recovery. Anytime I tried to upgrade cwm, or use rom manager, it just screwed it all up and reverted to stock 3e recovery. So I would advise against trying that stuff.
Good luck1
masterslacker said:
I had the same setup as you, including 3e recovery. I flashed speedmod k13e kernel for froyo, using odin, and it included cwm 2.5.1.0. Just leave it at that and you should always get into cwm when booting into recovery. Anytime I tried to upgrade cwm, or use rom manager, it just screwed it all up and reverted to stock 3e recovery. So I would advise against trying that stuff.
Good luck1
Click to expand...
Click to collapse
yep you and the guy above me were right indeed. Flashed it and it all works perfectly now
However there are some problems I've encountered, which i will post another thread about. They aren't Major problems but they are annoying ones nonetheless.
Hi, im using ROMAUR 1.2 with his kernel, i tried to flash via odin francos kernel v6 and the odin stayed in Nando Write Start, waited for like 10 minutes and nothing....any help pls?
im still with root, and my rom boots normaly but i cant flash via odin anymore, i reistaled all the drivers already, was using SGS3 ToolKit v2.0.
tnx
I'm trying to use Heimdall to flash a kernel because I have the NI1 kernel and can't find any other way to root. I don't have access to a Windows machine so I can't use Odin. When I try to flash the kernel with heimdall, it says I don't have a kernel partition (nor KERNEL). I checked the PIT file and sure enough, kernel is nowhere to be found.
So how do I flash a kernel with Heimdall?
Not sure what you're going to do with this. Personally, I'd find a Windows pc and use Odin. Messing with the partitions can brick your device if you don't know what you're doing.
http://forum.xda-developers.com/showthread.php?p=40557141
Sent from my Nexus 9 using XDA Free mobile app
I'm following this guide http://www.droidviews.com/root-att-galaxy-s4-sgh-i337-android-4-4-4-kitkat-firmware-i337ucufnj4/
Basically, it seems like the NI1 kernel is not rootable, so you flash a different one, root, then flash back. You think it'll brick if I flash a different kernel to the boot partition?
I'm running into a really annoying issue trying to compile a custom kernel from the Samsung source for my T230NU (Galaxy Tab 4, 7"), the first image I assembled flashed fine via Odin, but wouldn't boot. So I tried just unpacking the boot image, modifying build.prop and repacking it, but now it won't even flash! I get a FAIL error from Odin immediately after NAND Write Start.
Does anyone have experience modifying this kernel? Can you weigh in on which toolchain I need to use, or maybe have some scripts for packing and unpacking the boot image? Right now I'm using this: https://github.com/kumajaya/degas-mkbootimg which does seem to be working, besides the issues I'm having with boot and such.
any luck?
just checking if youve had any success with that kernel and if youre planning on implementing USB OTG.
thank you!
Hi,
Below is was my setup:
Latest TWRP Recovery
Alucard Kernel
S4 i9505
CM12.1 nightly
XPOSED v75
Viper4Android
Two days ago I decided to flash the sabermod kernel. At first I couldn't install it using the .zip (script error of some sort)
I then flashed the boot.img file as boot.
The phone was working fine for two days (rebooted twice at least).
On every Friday I download the latest nightly and flash it using the dirty flash method.
This is when I ran into trouble...
The TWRP is stuck on the Team Win screen.
I found a way to boot normally and decided to flash the alucard kernel back using Kernel Adiutor (boot.img).
The phone booted but now I have endless process stop errors (com.google.process.gapps) and I have lost root.
I need help...
Regards,
Jat
jdhot2 said:
Hi,
Below is was my setup:
Latest TWRP Recovery
Alucard Kernel
S4 i9505
CM12.1 nightly
XPOSED v75
Viper4Android
Two days ago I decided to flash the sabermod kernel. At first I couldn't install it using the .zip (script error of some sort)
I then flashed the boot.img file as boot.
The phone was working fine for two days (rebooted twice at least).
On every Friday I download the latest nightly and flash it using the dirty flash method.
This is when I ran into trouble...
The TWRP is stuck on the Team Win screen.
I found a way to boot normally and decided to flash the alucard kernel back using Kernel Adiutor (boot.img).
The phone booted but now I have endless process stop errors (com.google.process.gapps) and I have lost root.
I need help...
Regards,
Jat
Click to expand...
Click to collapse
Just reflash TWRP. Uncheck auto-reboot in Odin before flashing.
F2FS Support
I have all partitions formatted in F2FS apart from system which is EXT4. Can I flash TWRP via Odin if it is not . tar?
jdhot2 said:
I have all partitions formatted in F2FS apart from system which is EXT4. Can I flash TWRP via Odin if it is not . tar?
Click to expand...
Click to collapse
Flashing a firmware will fix the issue, both for recovery and rom
Which Firmware?
Which Firmware to flash? Obviously I can only flash via odin. Also what will happen to the F2FS partitions?
jdhot2 said:
Which Firmware to flash? Obviously I can only flash via odin. Also what will happen to the F2FS partitions?
Click to expand...
Click to collapse
Flashing will return you to ext4
Because f2fs needs a special recovery files etc... and it will be replaced.
Test it out you wont lose nothing
Flash latest samsung touchwiz?
Just to confirm you are asking to flash the latest Sammy rom which I believe is 5.0.1. however Cm12.1 is 5.1.1. If you are confident in me trying this I will download the stock rom and flash it via odin and will let you know how I go. Thanks for your help so far.
jdhot2 said:
Just to confirm you are asking to flash the latest Sammy rom which I believe is 5.0.1. however Cm12.1 is 5.1.1. If you are confident in me trying this I will download the stock rom and flash it via odin and will let you know how I go. Thanks for your help so far.
Click to expand...
Click to collapse
Yes flashing sammy, no prob always here to help
Flashing Now
I am now flashing latest Sammy rom with latest Odin.
You're a lifesaver!
Thanks for your help much appreciated.
My phone is up and running again.
Next time if I have any issues with my s4 I'll just flash the latest Sammy rom.