[Q] Related to GamerzRom v9 (BT) - Samsung Infuse 4G

Hello all, quick question kinda new to posting, a bit shy. but i know my way around android, has anyone notice bluetooth pairing issues on this rom. Work on my car's radio but only for phone, no media connection. and when i tried it on my stereo bluetooth headset, it comes up with an error stating that wrong pairing code. Any light on this issue would be appreciated or if im the only one having this problem. PS: its never happened on any other ported rom, and i came from Revelations rom and it was working perfectly. (the bluetooth).

ltcarlos2 said:
Hello all, quick question kinda new to posting, a bit shy. but i know my way around android, has anyone notice bluetooth pairing issues on this rom. Work on my car's radio but only for phone, no media connection. and when i tried it on my stereo bluetooth headset, it comes up with an error stating that wrong pairing code. Any light on this issue would be appreciated or if im the only one having this problem. PS: its never happened on any other ported rom, and i came from Revelations rom and it was working perfectly. (the bluetooth).
Click to expand...
Click to collapse
Did you flash GamerzRom v9 then Hellrasier or is this a full port you flashed?
Sent from my SAMSUNG-SGH-I997 using Tapatalk

bigfau said:
Did you flash GamerzRom v9 then Hellrasier or is this a full port you flashed?
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply, and yes its from the port posted by Gosooners, i believe though he didn't put the linux bozo kernel inside the rom because afterwords i flashed with sgs kernel flasher the Linux bozo kernel and booted with the galaxy s boot animation. if i hadn't flash the linux bozo kernel it would have booted with an AOSP boot animation.
Thanks again for the quick response. have you tried paring any of your own bluetooth devices?

ltcarlos2 said:
Thanks for the quick reply, and yes its from the port posted by Gosooners, i believe though he didn't put the linux bozo kernel inside the rom because afterwords i flashed with sgs kernel flasher the Linux bozo kernel and booted with the galaxy s boot animation. if i hadn't flash the linux bozo kernel it would have booted with an AOSP boot animation.
Thanks again for the quick response. have you tried paring any of your own bluetooth devices?
Click to expand...
Click to collapse
LinuxBozo's kernel is not necessary for a port. Most of the ports I've done, I used either the Infusion kernel or Entropy's DD. I didn't see a link for GamerzRom v9 Ninja Edition. I don't use BT so I haven't tested it.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2 Beta-5

Same here
Sent from my SAMSUNG-SGH-I997 using xda premium

Related

[ATT dev] Kernels Causing Wired HEADSET ISSUES!

I noticed some Kernels have different issues with wired headset.
Headset cuts my voice during voice calls
Auto dials and auto pulls call log
Headset button doesn't work
anyone notice strange behavior with your headset plugged in? Lets make a list of issues to make it simpler for devs to find a solution.
Any solutions? (one is to use stock kernel which is linked in this thread)
Post your issues with wired headset and please note which kernel is acting up. maybe we can combine code from different kernels to make one that works. (I noticed that some kernels have one issue but not the other)
Thanks for all your support and great work everyone is doing on the Epic!
Yes, I noticed the behavior between different kernels (using stock ROM). I know for a fact that with Xtreme Kernel, it disconnects my calls whenever I plug in my headset. The devs say to use only with ACS ROM, but given that the kernel is the bridge between the hardware and software, I doubt the ACS ROM would fix the issue.
I forgot what happened with the other kernels. I settled with Pheonix for now at the conservative governor (interactive sometimes leaves the CPU running at 100MHz and wont ramp up).
Seems we wont be getting any fixes for a while. All the kernel devs are having too much fun playing with Froyo.
Glad I am not the only one! Lets see if we can work this out! Using your phone without headset will give you BRAIN CANCER! Plus its more convenient with a headset when I have to deal with clients.
had problems using epic experience w/ mixup kernel and the latest Xtreme
I can confirm that wired headset handling is kind of fubar in our community kernels. Samsung had made some bugfixes between DI07 -> DI18 versions, but those changes don't appear to have been added to the DI18 source code.
Have any of you tried using the stock DI18 kernel to test this? If it works properly, then we have to cross our fingers and hope the issues don't persist in the kernel shipped with Froyo - as it stands there's no way to know what changed to fix this stuff easily in our community kernels.
The only time I ever gotten headset to work with phone mic was using stock rom and stock kernel after an odin.
effudee said:
The only time I ever gotten headset to work with phone mic was using stock rom and stock kernel after an odin.
Click to expand...
Click to collapse
Yep, that's the exact issue with the missing changes in the source Samsung released.
effudee said:
The only time I ever gotten headset to work with phone mic was using stock rom and stock kernel after an odin.
Click to expand...
Click to collapse
It's only the custom kernel(s) that cause this issue...flash whatever rom you want, flash the stock kernel and you should be good to go...
also, FYI, already a thread on this issue here:
http://forum.xda-developers.com/showthread.php?t=771861
any link to stock Kernel? would be good if we could find a solution for the custom kernels, Is there any other way to install stock kernel besides restoring stock rom through ODIN?
lucifermoh said:
any link to stock Kernel? would be good if we could find a solution for the custom kernels, Is there any other way to install stock kernel besides restoring stock rom through ODIN?
Click to expand...
Click to collapse
Don't recall where I got it from but here is the stock DI18 kernel...
ScientificOne said:
It's only the custom kernel(s) that cause this issue...flash whatever rom you want, flash the stock kernel and you should be good to go...
also, FYI, already a thread on this issue here:
http://forum.xda-developers.com/showthread.php?t=771861
Click to expand...
Click to collapse
Oh really? I remember trying andromeda with stock kernel and it still didn't work for me. I'll try Syndicate with stock kernel eventually then. Thanks for the information
thanks for the zip!!! any idea if devs are aware of this issue?
lucifermoh said:
thanks for the zip!!! any idea if devs are aware of this issue?
Click to expand...
Click to collapse
I doubt it. I posted my bug on the Xtreme Kernel thread and Devin never responded. The only response I got was to use a specific ROM .
Yes, well at least this one is. I'm examining the audio right now to try and hunt down a fix for this and the bluetooth routing bug.
The leaked 2.2 still has the bluetooth bug afaik. I'm hoping samsung releases this fix with their source next time.
Using extreme kernel and when i plug in AUX cable for audio to my car it isnt recognized as a headset.
You mean it doesn't pop the icon in the notification bar, or that it doesn't play audio?
Nothing I plug in pops the headset icon when using a custom kernel - not even the wired headset. Pretty sure it's another symptom of the bug.
[edit] Nor in the froyo stock kernel. /shakes fist at samsung!

G2x running stock froyo, Trinity kernal, and pimp my CPU BT toggle turns phone off?

My phone is running great but I can't turn off my Bluetooth and I don't want it eating battery for no reason. Whenever I attempt to turn it off it shuts my phone off instead (whether I do it through a widget or settings) If anyone has experiences this issue please help me out. Thank you guys.
jstrayy said:
My phone is running great but I can't turn off my Bluetooth and I don't want it eating battery for no reason. Whenever I attempt to turn it off it shuts my phone off instead (whether I do it through a widget or settings) If anyone has experiences this issue please help me out. Thank you guys.
Click to expand...
Click to collapse
refresh rom.. (wipe, flash again)
(wrong thread)
avetny said:
refresh rom.. (wipe, flash again)
(wrong thread)
Click to expand...
Click to collapse
I asked here because here is where everyone is flashing new roms and kernals but yea I guess I'll try wiping just didn't want to go through all of that again. Thank you though
jstrayy said:
I asked here because here is where everyone is flashing new roms and kernals but yea I guess I'll try wiping just didn't want to go through all of that again. Thank you though
Click to expand...
Click to collapse
This isnt the right section.... Read the rules
And stock rom as in? Try flashing eb 1.04... also make sure u have the right kernel.... You might have downloaded a gb kernel by mistake
Sent from my LG-P999 using XDA Premium App
Which Trinity kernel are you using? Right now there aren't any listed for stock ROM.
Also as has already been said this should be in a different section.
If he really flashed trinity on a stock rom and that's the only problem then someone should let Morfic know, maybe we can finally get a stock OC kernal, I've been waiting for one since I got the phone.
rooflessatrium said:
If he really flashed trinity on a stock rom and that's the only problem then someone should let Morfic know, maybe we can finally get a stock OC kernal, I've been waiting for one since I got the phone.
Click to expand...
Click to collapse
Yea I did, and the bluetooth issue comes about AFTER overclocking with pimpmycpu. I tried uninstalling but the problem doesn't go away so I went back to stock with Paul's Patch and everything is fine. Kinda sucks because my phone was real fast. Also when Paul's Patch and Trinity are applied together I wasn't getting sound at boot animation and I'm OCD so it did bother me lol
and if you guys are wondering I flashed the 2 following trinity versions: (without paul's patch and still got the bluetooth issue)
Trinity15 G2x - EB1.04 Froyo - EXT4 - Vibrator works, usb mounting might not
Trinity15 G2x - EB104F - EXT4 - vibrator works (new 5/16/2011), possibly usb mounting doesn't work
Usb mounting didn't work but all you need is a Multi-Mount SD card application and you're good.
UPDATE: Just redid my phone to complete stock and it seems that the bluetooth issue is still there, I think I found exactly where it's coming from and has nothing to do with the kernal or the patch. the issue comes up only after I restored my application data and apks with my backup pro so I'm guessing something is corrupt "/
mods...please move this thread
and when someone posts in the wrong section,can we refrain from answering please? all it does is create more clutter.
Thread Moved.
Mr. Clown said:
Thread Moved.
Click to expand...
Click to collapse
Thanks and sorry about that, new to the forum.
Sent from my LG-P999 using XDA Premium App

First Android Phone

Closed closed closed
Use NV flash to get the recovery installed. Flash a custom ROM. I'm using weapon g2x with faux newest kernel myself.
Sent from my LG-P999 using xda premium
well theres tons you can do. for stability you should flash one of the many fine roms we have in the dev section. since you said its your 1st android phone ill assume you arent rooted. take a look @ this thread to get you started.
http://forum.xda-developers.com/showthread.php?t=1060715
wendellc said:
Use NV flash to get the recovery installed. Flash a custom ROM. I'm using weapon g2x with faux newest kernel myself.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I said I was new, this is like another language for me lol sorry man.
uploder said:
well theres tons you can do. for stability you should flash one of the many fine roms we have in the dev section. since you said its your 1st android phone ill assume you arent rooted. take a look @ this thread to get you started.
http://forum.xda-developers.com/showthread.php?t=1060715
Click to expand...
Click to collapse
Thank you for the link, and one other question, will rooting/flashing it affect the way I have my phone set up and keeping all of my stuff? Like is it restoring my phone?
I would say go for the legendary cyanogen mod first. See the power of android first, realize what aspects are important to you, then maybe try a different rom. Or just stay with CM like so many 100s of thousands of others
Sent from my LG-P999 using xda premium
xsteven77x said:
I would say go for the legendary cyanogen mod first. See the power of android first, realize what aspects are important to you, then maybe try a different rom. Or just stay with CM like so many 100s of thousands of others
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
1. Changing roms wipe your phone? 2. Whats CM?
EDIT---
Dumb question('s), question has been revised in the first post.
Here's a quick glossary:
ROM: essentially an operating system for the phone. CM7, Miui, Weapon, Eaglesblood, are all ROMs.
Recovery: Recovery mode, accessed by holding power and volume-down while booting up the device. Most notible for ClockworkMod Recovery (abbreviated CWM), a custom recovery mode that lets you do lots of modding-related things.
Wipe: Formatting various parts of the phone's memory, necessary when installing new things. For a run-of-the-mill flash (anything other than a new ROM) just wipe Cache and Dalvik, the latter is under the Advanced option in CWM. For a new ROM, do the above but also wipe Data (factory reset) and System (under Mounts and Partitions in CWM)
Kernel: In the context of phones, this is a system change that lets you undervolt and/or overclock the CPU. Lets you save battery and increase performance respectively.
NVFlash: A tool used to flash CWM onto the phone.
Root: Access to the entire phone's system as opposed to being locked out to part of it as is the default. Lets you run special Root-only apps.
The Android Development board here is pretty definitive as far as roms go, the only significant one not hosted here is Whitehawkx's MIUI port which IMO is better than the one here.
LordButtersI said:
Here's a quick glossary:
ROM: essentially an operating system for the phone. CM7, Miui, Weapon, Eaglesblood, are all ROMs.
Recovery: Recovery mode, accessed by holding power and volume-down while booting up the device. Most notible for ClockworkMod Recovery (abbreviated CWM), a custom recovery mode that lets you do lots of modding-related things.
Wipe: Formatting various parts of the phone's memory, necessary when installing new things. For a run-of-the-mill flash (anything other than a new ROM) just wipe Cache and Dalvik, the latter is under the Advanced option in CWM. For a new ROM, do the above but also wipe Data (factory reset) and System (under Mounts and Partitions in CWM)
Kernel: In the context of phones, this is a system change that lets you undervolt and/or overclock the CPU. Lets you save battery and increase performance respectively.
NVFlash: A tool used to flash CWM onto the phone.
Root: Access to the entire phone's system as opposed to being locked out to part of it as is the default. Lets you run special Root-only apps.
The Android Development board here is pretty definitive as far as roms go, the only significant one not hosted here is Whitehawkx's MIUI port which IMO is better than the one here.
Click to expand...
Click to collapse
The help is greatly appreciated, I picked some of that up just spending an hour reading up on wiki and android and surfing the threads, but again thank you.
My revised question still stands, what is the BEST ROM out there if there is one, and what is the BEST kernel out there if there is one.
Paul Nur said:
The help is greatly appreciated, I picked some of that up just spending an hour reading up on wiki and android and surfing the threads, but again thank you.
My revised question still stands, what is the BEST ROM out there if there is one, and what is the BEST kernel out there if there is one.
Click to expand...
Click to collapse
That's like asking what is the best ice cream. Its all a preference. Cyanogenmod is the most popular rom for android and it cones with a kernel. Now try it already.
Sent from my LG-P999 using xda premium
xsteven77x said:
That's like asking what is the best ice cream. Its all a preference. Cyanogenmod is the most popular rom for android and it cones with a kernel. Now try it already.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
For me the stability of the phone is the most important, so the appearance of it will come second. I am using a rooted build of gingerbread 2.3.3 and so far it has been working flawlessly, my phone before I flashed it with the rooted ROM gave me like at least 1 problem a day, so far I am clear and it has almost been 24hr. If it stays its course I am not looking into anymore ROM's, if it does show the same signs I will search for the next best ROM.
But again, I appreciate your input, I am keeping an eye on the ROM you named and a few other, cheers
If you need A2DP then go with Weapon, it's based on 2.3.3 and everything works great.
Sent from my Nexus Prime using XDA Ultimate App
LordButtersI said:
If you need A2DP then go with Weapon, it's based on 2.3.3 and everything works great.
Sent from my Nexus Prime using XDA Ultimate App
Click to expand...
Click to collapse
What is A2DP?
a2dp is the ability to stream bluetooth in stero without it music over bluetooth is a no go but you can still use BT for phone calls it will only be in mono. You can still use your phone for music but you have to use this thing called a wire I dont know apparently back in the day you had to use this wire to listen to music throught headphones and speakers. Strange right? Anyway all ROMS that are not 2.3.3 based or 2.2.2 based Like CM7 or eaglesblood that are 2.3.5 do not have A2DP it has something to do with Nivida not releasing the drivers or something like that. It is ashames because Eaglesblood 1.08 is the best ROM ever but it will never be finished same as cm7 till Nivdia starts cooperating. It really was hard going back to wired headphones but eaglesblood is definitly worth it. Hope this helps
Charlie
a2dp is the ability to stream bluetooth in stero without it music over bluetooth is a no go but you can still use BT for phone calls it will only be in mono. You can still use your phone for music but you have to use this thing called a wire I dont know apparently back in the day you had to use this wire to listen to music throught headphones and speakers. Strange right? Anyway all ROMS that are not 2.3.3 based or 2.2.2 based Like CM7 or eaglesblood that are 2.3.5 do not have A2DP it has something to do with Nivida not releasing the drivers or something like that. It is ashames because Eaglesblood 1.08 is the best ROM ever but it will never be finished same as cm7 till Nivdia starts cooperating. It really was hard going back to wired headphones but eaglesblood is definitly worth it. Hope this helps
Charlie
Thanks bro, much appreciated, why is that mod the best tho?
Sent from my LG-P999 using XDA App
Not to hijack, but is this the only thing that doesn't work with 2.3.5 ROMs?
Sent from my LG-P999 using Tapatalk
herzzreh said:
Not to hijack, but is this the only thing that doesn't work with 2.3.5 ROMs?
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
It's cool, I have the same question.

[Q] Infuse 4G Rogers Roms

I have a small question I tried almost all popular roms on this site. And in every roms I had an issue.
Here a description:
*MIUI Link: Worked like a charme but Bluetooth didn't work, and battery couldn't handle it. I also tested the ported one, but it was worst.
*Zeus: android system was always crashing on network (4g and wifi)
*catyroms: couldn't mount my external Sd, and crashes sometimes
*BIonix: could access my rogers network, even for the phone
*CM7 the kang version: seems to work so far.
I'm a noob, but I saw that the base of the rom are ATT versions, and most of the time the kernel was UCKL2. Is it really a big deal for a rogers infuse phone to have that kind of kernel on it. Maybe that's why I had so many issues with the roms.
If for example I install Zeus and with sgs flasher I flash the zeus kernel with a UXKG3 or last entropy's kernel, would it solve my problems?
Thanks for your answers and explanation
Try Infused ROMs. They are based off Rogers ROM.
How
How do I know when a rom is based on roger rom?
When the kernel is UXKG3?
youpiyo said:
How do I know when a rom is based on roger rom?
When the kernel is UXKG3?
Click to expand...
Click to collapse
99.99% it would be mentioned in OP.
what do you mean by OP
diablo009 said:
99.99% it would be mentioned in OP.
Click to expand...
Click to collapse
Thanks, but if you go to the superthread only one thread is mention rogers only.
In custom rom section nowhere it's mention also
I also check the 7 pages in Samsung Infuse > 4GInfuse 4G Android Development> Forum anywhere roger is mention in the title
Does it mean it's not fully compatible? and it only works for ATT?
And what about that:
youpiyo said:
If for example I install Zeus and with sgs flasher I flash the zeus kernel with a UXKG3 or last entropy's kernel, would it solve my problems?
Click to expand...
Click to collapse
Rom Infused
[ROM] Infused v2.2.3
That one seems to be compatible
Do we have another one?
youpiyo said:
[ROM] Infused v2.2.3
That one seems to be compatible
Do we have another one?
Click to expand...
Click to collapse
I used it for months since I got my Infuse, and was on until I switched to Zeus. Try it out, you won't be disappointed.
Edit: If you want Froyo, try out Infused 1.5.x ROMs.
diablo009 said:
I used it for months since I got my Infuse, and was on until I switched to Zeus. Try it out, you won't be disappointed.
Edit: If you want Froyo, try out Infused 1.5.x ROMs.
Click to expand...
Click to collapse
I'm a little bit disapointed but I will wait with infused until a better miui Bluetooth working and battery life.
Thanks
I'm using Zeus on an infuse w/rogers and its working fine for me.
Originally the AT&T bloatware turned me off but dman managed to get rid of it.
Did you wipe before flashing ZEUS?
*edit*
also i may be wrong on this but i believe zeus uses the same kernel as infused, which is rogers-based.
Yep I flash data cache and devilsk.
After I install the rom even during google setup it crash. So Idon't why.
I'm on zeus on Rogers as well. This thing has been rock solid for me. One force close after initial flash, then all has been fine. Kl2 is the modem not the kernel if I'm not mistaken
Sent from my SAMSUNG-SGH-I997 using xda premium
well I will do a youtube video to show you. I tried yesterday night, and I had the same result.
Sent from my SAMSUNG-SGH-I997R using XDA App

[KERNEL] [JB 4.2/4.2.1] Stock kernel - CWM flashable

Hello all,
I made this over at the GNex forums for a stock GNex 4.2/4.2.1 kernel... here it is for the Nexus 7 for those that accidentally flashed a 4.1.2 kernel or just want to get back to stock.
Flash at your own risk, should work just fine though!
UPDATED: Kernel should work now! Sorry about the bad zip before!
Will it work on 4.1.2? I have AOKP on my device, would like to flash this, just need to check if it's safe...
Cheers
Sent from my Nexus 7 using xda app-developers app
where were you couple of days ago when I was dealing with the issue - trying to flash stock kernel.....wish you posted this before.
I will save this just in case :silly:
thanks!!!
I flashed LeanKernel and then wanted to go back to stock kernel before flashing latest Faux Kernel.
So I have just flashed your kernel but "about tablet" is telling me I still have LeanKernel installed?
If you can overclock then you're still on lean kernel. Either way, I'd suggest a reflash.
Sent from my Nexus 7 using xda premium
Caliyork said:
If you can overclock then you're still on lean kernel. Either way, I'd suggest a reflash.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
It was definetely still on LeanKernel, I tried it twice.
Only issue could be that I was using an older version of TWRP that wasn't updated for 4.2, but it seemed to flash ok.
edit
Ok, tried it again now I have the updated TWRP and the same thing happens...i.e. nothing, it flashes in the normal way but changes nothing.
This is all wrong. The boot.img inside does not match the one from the N7 nakasi factory image and the updater-script is written for the Galaxy Nexus.
Code:
"of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");
N7 certainly doesn't run OMAP. Flash at your own risk, indeed.
I urge you to take this down and make sure you know you've got it right before you put it up again. Only saving grace here is you were using the platform by-name method (which just plain won't work on the N7) instead of the actual mmc block names or you could have really messed up some peoples' devices.
osm0sis said:
This is all wrong. The boot.img inside does not match the one from the N7 nakasi factory image and the updater-script is written for the Galaxy Nexus.
Code:
"of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");
N7 certainly doesn't run OMAP. Flash at your own risk, indeed.
Click to expand...
Click to collapse
My mistake. I thought it would just transfer over. I will fix the link... Didn't realize when I tested it I already had the stock kernel on there. Gimme a minute to fix it!
OK should be fixed and good to go! Again, my apologies!
Sent from my Galaxy Nexus using Tapatalk 2
stonebear said:
It was definetely still on LeanKernel, I tried it twice.
Only issue could be that I was using an older version of TWRP that wasn't updated for 4.2, but it seemed to flash ok.
edit
Ok, tried it again now I have the updated TWRP and the same thing happens...i.e. nothing, it flashes in the normal way but changes nothing.
Click to expand...
Click to collapse
Please try again... I have updated my zip and tested it by flashing a 4.1.2 kernel, having the device sit at the X for a few minutes without doing anything (to test a non-working kernel) then flashing my zip, and my N7 is back up and running again.
I am still learning about kernel stuff... sorry about any confusion!
SkaldfraNorden said:
Will it work on 4.1.2? I have AOKP on my device, would like to flash this, just need to check if it's safe...
Cheers
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Negative. This is the stock 4.2 kernel... I found the stock 4.1.2 kernel on XDA... Should be easy to find!
Sent from my Galaxy Nexus using Tapatalk 2
Where can I find the stock kernel for the Galaxy Nexus running on 4.2? If you can redirect me to the link, I'll greatly appreciate it. Thanks in advance.
evaradar said:
Where can I find the stock kernel for the Galaxy Nexus running on 4.2? If you can redirect me to the link, I'll greatly appreciate it. Thanks in advance.
Click to expand...
Click to collapse
wasn't that hard to find out, but here you go: stock kernel
This is JOP40C kernel for 4.2 but will it work on JOP40D 4.2.1 stock ROM please ?
I've added this kernel to the Nexus 7 Complete Index
Sent from my Nexus 7 using xda premium
..
BTW..Excellent system stability with this kernel and rasbeanjelly ROM. Tested on my daughter.
cydef said:
This is JOP40C kernel for 4.2 but will it work on JOP40D 4.2.1 stock ROM please ?
Click to expand...
Click to collapse
+1
Sent from my Nexus 7 using xda app-developers app
Can anyone confirm if the kernel listed (jop40c) is the actual kernel used in the stock 4.2.1 system? The build is jop40d, and the question seams to be getting overlooked. I cannot find the stock jop40d 4.2.1 kernel anywhere, and just do not have any interest at this time in flashing the factory image/re-rooting etc. Any help would be appreciated.
annoyingduck said:
Can anyone confirm if the kernel listed (jop40c) is the actual kernel used in the stock 4.2.1 system? The build is jop40d, and the question seams to be getting overlooked. I cannot find the stock jop40d 4.2.1 kernel anywhere, and just do not have any interest at this time in flashing the factory image/re-rooting etc. Any help would be appreciated.
Click to expand...
Click to collapse
This.. I was about to post, my N7 (16g, wifi) is JOP40D as well, not 40C.
Thinking about trying out a custom kernel, but want the stock to fall back on, as it's super stable.
khaytsus said:
This.. I was about to post, my N7 (16g, wifi) is JOP40D as well, not 40C.
Thinking about trying out a custom kernel, but want the stock to fall back on, as it's super stable.
Click to expand...
Click to collapse
As it turns out, I built a "slightly rooted" JOP40D stock flash kit yesterday (mods to build.prop in boot.img, and su/SuperSU in system.img). I'm posting this reply from that.
I started with the Google JOP40D (grouper) distro to do that. I thought I was going to need to unpack the boot.img from the OP's .zip to do comparisons of the kernels (to answer your question) ... but it turns out that his boot.img has the same MD5 sig as the boot.img from Google's JOP40D... and the OP's updater-script merely flashes boot.img to the /boot partition.
That means one of two things: either the two successive Google releases (for grouper) had identical boot images (which implies identical kernels), or there is some mistake by the OP. (I don't have the 40C distro to check ... only picked up my N7 a few days ago.)
It should work in your specific case though, as you are on JOP40D.
In any event, flashing boot.img is way way more than just a kernel replacement. I haven't looked at it for a while, but I would suppose that Koush's kernel flasher is a much more appropriate technique for switching ONLY the kernel out from underneath an arbitrary ROM.
cheers
That's great info there. I'm searching for the simplicity of just flashing a kernel instead of pushing the entire boot image. Thanks for a step in clarifying this question
Sent from my Nexus 7 using xda premium

Categories

Resources