Hello, normally I do lots of research and searching in order to figure out problems for myself, but this one I have been stuck on for weeks.
I am on SGH-T999v, here is my issue.
I am trying to use either the latest 1.5 Spirit Rom, or M4 gummy Rom in combination with KTOONSEZ Kernel from here.
If I try to flash the kernel with latest versions of those roms, my baseband says "UNKNOWN" and my IMEI gets zero'd out.
Also it tells me that I have no sim card inserted. I have tried formatting dalvic/cache before and after installation of kernel as well as fixing permissions.
Both Spirit 1.5 and Gummy M4 work no problem without the custom kernel installed.
Also, on only 1.1 Spirit and M3 gummy, am I able to use the custom KT kernel and still have my signal.
Okay now here is the strange part of the problem.
Currently I am using the custom recovery TWRP that lets me use multiboot from here
And after successfully creating a multiboot rom, I go ahead and install Gummy M4 + Gapps + KT Kernel and boot it up, to find out that it actually works perfectly fine.
My baseband shows up, and my signal connects.
Also the version im using of the recovery menu is V2.11
I am just wondering why is it that the rom + custom kernel doesn't work with a regular flash, and that it only seems to work when I multiboot it?
What I want is to not have to create a multiboot rom in order to use this, I want to actually flash these to my phone.
Please help me, anyone who has any idea of what I am talking about..Sorry if I have not been clear enough. Thank you/.
Edit: I also forgot to mention that I have tried flashing the stock modem after the kernel + rom installation through odin, that did nothing.
Related
Hi all,
Has anyone tried the new bananacakes kernel 0.4 based on the official kernel source?
I tried installing it but my phone randomly resets every now and then. I've gone back to a Nandroid backup for now but I'd really like to use the new kernel.
Can someone who has successfully updated their InsertCoin ROM with the new kernel post some tips?
Thanks.
TBH, if you have problems with a kernel or any other file you flash or install, you're better off not using it anyway. Just "suffer" with what you've got.
You could always try a different ROM with a kernel (if compatible) or try a different kernel with the existing ROM.
Have you tried reflashing/installing the ROM and kernel from new after full wipe? Sometimes you can get issues with a file and undoing then re-flashing/installing can sort this most of the time (providing the file is stable). Are there any instability notes with the ROM/kernel? If so you may want to wait until stable versions are posted.
I updated the kernel without doing a full wipe, didn't want to lose all my settings.
Oh well, I'll do a full wipe and give it a try.
Thanks.
Hey everyone, I had just flashed cyanogen 10 kang with twrp and everything was fine until I decided to try and get the nexus s 4g modem which I had failed at every time before that. I would flash the rom, then gapps, Then the nexus modem patch before the shadow kernel. This time I flashed the shadow kernel before the nexus modem patch and it had apparentally powered itself off (I had left the room) so I tried to boot back into twrp, but it popped up with cwm 5.0 something instead. And the only backups I have are for twrp. . After I looked around in it for a little I tried flashing the rom and gapps again, booted up fine except I don't believe I had any signal. At all.
I tried to find something that would put twrp back onto my phone but haven't had any luck. And for some reason when I booted back into recovery it had changed to cwm 6.0 something. I don't know what to make of any of it. Right now I'm on cm9 snapshot beta 4 i think. I thought it was the one with twrp already in it so I thought I could try and restore my stuff.
Anyone have a remedy for this? I'd really appreciate it. Thank you in advance for your time.
swiftstrike763 said:
Hey everyone, I had just flashed cyanogen 10 kang with twrp and everything was fine until I decided to try and get the nexus s 4g modem which I had failed at every time before that. I would flash the rom, then gapps, Then the nexus modem patch before the shadow kernel. This time I flashed the shadow kernel before the nexus modem patch and it had apparentally powered itself off (I had left the room) so I tried to boot back into twrp, but it popped up with cwm 5.0 something instead. And the only backups I have are for twrp. . After I looked around in it for a little I tried flashing the rom and gapps again, booted up fine except I don't believe I had any signal. At all.
I tried to find something that would put twrp back onto my phone but haven't had any luck. And for some reason when I booted back into recovery it had changed to cwm 6.0 something. I don't know what to make of any of it. Right now I'm on cm9 snapshot beta 4 i think. I thought it was the one with twrp already in it so I thought I could try and restore my stuff.
Anyone have a remedy for this? I'd really appreciate it. Thank you in advance for your time.
Click to expand...
Click to collapse
You have to flash nyankernel or just the twrp zip. And next time when you flash from twrp, you need to pick inject twrp if you don't want cwm.
Sent from my SPH-D700 using Tapatalk 2
not trying to "thread-jack" - but I have a really similar problem (minus the twrp - which i'm not familiar with). Throughout my update to the crespo modem, during the mtd/bml check the phone would reboot into cwm - and I noticed that just like OP, the cwm would change to some 5.0version (not the usual 6 version)....
Here's what I have:
I was on CM Kang 7/30 with shadow kernel
I updated to CM Kang 8/08 (no problems)
I flashed the http://darkierawr.com/Android/Users/...atchcm7AIO.zip and I kept on getting Status 7 errors... I downloaded it a few times with the same result.
Then I saw someone say they flashed the kernel first and then the modem update... so I flashed the http://dl.dropbox.com/u/820341/Shadow-2_CM10_MdmCrp.zip (successful) and then tried flashing the modem update. Got stuck in a boot loop - so I did a battery pull.
Did a cold boot (pressing power) and now the phone "doesn't have a modem" no radio, no signal etc...
Tried it all over again - mounted system - formatted system - flashed 8/08 kang, gapps, then the modem update, and kernel.
my phone boots but no signal. is there a odin version of the modem that I can flash? or does anyone have any ideas?!?!?!
thanks!!
altimuh said:
not trying to "thread-jack" - but I have a really similar problem (minus the twrp - which i'm not familiar with). Throughout my update to the crespo modem, during the mtd/bml check the phone would reboot into cwm - and I noticed that just like OP, the cwm would change to some 5.0version (not the usual 6 version)....
Here's what I have:
I was on CM Kang 7/30 with shadow kernel
I updated to CM Kang 8/08 (no problems)
I flashed the http://darkierawr.com/Android/Users/...atchcm7AIO.zip and I kept on getting Status 7 errors... I downloaded it a few times with the same result.
Then I saw someone say they flashed the kernel first and then the modem update... so I flashed the http://dl.dropbox.com/u/820341/Shadow-2_CM10_MdmCrp.zip (successful) and then tried flashing the modem update. Got stuck in a boot loop - so I did a battery pull.
Did a cold boot (pressing power) and now the phone "doesn't have a modem" no radio, no signal etc...
Tried it all over again - mounted system - formatted system - flashed 8/08 kang, gapps, then the modem update, and kernel.
my phone boots but no signal. is there a odin version of the modem that I can flash? or does anyone have any ideas?!?!?!
thanks!!
Click to expand...
Click to collapse
Try http://marcusant.com/android/epic/modem.bin
Sent from my SPH-D700 using Tapatalk 2
So, i have pure stock as my internal rom, as id just like to have it there, but i dont use it, and i've been trying to flash glitch kernel on the 10/6 build of AOKP and 10/08 pacman, and no matter what i do it refuses to flash, everything'll work, but ill boot into the rom, and the kernel will be the stock one that came with the rom. I've made sure i'm flashing the version for the latest CM because the other gives me a blue screen.
AOKP 2013-11-14 build, 's been working fine for the past two weeks or so. Since the default kernel doesn't seem to work I tried flashing other kernels but after flashing, the device doesn't boot. Tried franco.Kernel, LeanKernel, Stock 4.3 kernel, none works. What could be the cause of this?
Maguro
AOKP 2013-11-14 build (4.3.1)
TWRP 2.6.3.1
No kernels seem to work.
Update
I restored a working backup. It didn't work. It's stuck on the X logo.
Any things I can do? Flash clean ROM?
I had the same issue on another rom (carbon). They had changed something, so the kernel had to get a special fix to work. Try asking on the aokp thread or forum (can't remember if they got one)
It seems you flashed wrong kernel or it is not compatible with your current rom.
Sent from my Galaxy Nexus using Tapatalk 4.
ive installed the multi rom manager for the sprintm8 ..after reading up on everything..its the latest test version pose to help with hanging up when booting secondary roms..i still freeze up bout everyother time trying to boot from the manager app to secondary rom..i tried flashing updated firmware from hboot ..the updated firmware was the one updated in aug..hope that was the latest..still have issiue..i have bad boyz sense as base rom with elementalx as kernal with patch..have pacman as secondary..everytime ive attempted to make changes like the kitkat sd card fix..or install xposed framwork..ive had to wipe data and start over cause after rebooting would just go black screen..thinking i bricked it..also tried flashing liquid smooth as third rom..did fine..but no mobile data or wifi worked..im sticking to aosp roms cause ive read they all mostly work although id love to have another sence based rom as well..but the ones i tried never booted..read how its possible to alter the zip then repack..but sounds to advanced for me..question is do i need to flash anotherr kernal in my aosp roms to get it all working..i know the base rom gets the elementalx kernal with patch....but do i need another kernal for other roms to get everything working..and why am i freezeing dureing booting up from multirom manager into the aosp secondary roms?