Hi,
I was wondering where I would be able to find the stock kernel used with Roman's AOKP (b38) for the Galaxy Nexus (GSM).
Main reason is I am wishing to try franco's 181 with 384 GPU, but would like the option to switch back to stock if I find that franco's isn't as smooth or reliable.
Thanks in advance.
mk_ln said:
Hi,
I was wondering where I would be able to find the stock kernel used with Roman's AOKP (b38) for the Galaxy Nexus (GSM).
Main reason is I am wishing to try franco's 181 with 384 GPU, but would like the option to switch back to stock if I find that franco's isn't as smooth or reliable.
Thanks in advance.
Click to expand...
Click to collapse
Settings - about phone - kernel version. I think it's faux's kernel, at least used to be. Or just flash the rom again, it'll put back the stock (rom) kernel.
thanks, but doesn't flashing the rom again wipe data?
mk_ln said:
thanks, but doesn't flashing the rom again wipe data?
Click to expand...
Click to collapse
It doesn't, no
thanks again for the quick reply, and yes, it does seem that the kernel used is faux's kernel (017+). currently faux's seems to be on 018.
mk_ln said:
thanks again for the quick reply, and yes, it does seem that the kernel used is faux's kernel (017+). currently faux's seems to be on 018.
Click to expand...
Click to collapse
Not always necessary to update, 17+ is a heck of a kernel..
maybe it was just me, but it seems you were right about kernel 017; I probably should have left everything as it was.
after flashing franco's as well as faux's 018, it seemed that 017 was actually slightly smoother. in order to get back to 017 i did as you suggested and flashed the entire rom. unfortunately all my gmail accounts were lost/forgotten as well as the gapps; opening gmail would result in a crash w/o a message...same thing happened with the play store and i had to reinstall the gapps.
i was thinking about flashing just the boot.img from the flashable zip using fastboot, but i wasn't, and still am not, sure if that would have provided me the same result as flashing through CWM.
If you reflash the rom you have to reflash the gapps and you should be fine.
"Long is the way, and hard, that out of hell leads up to light."
Nandroid. It will backup the kernel, just make sure if you go back, you restore system as well because each kernel can have a few libs with it that another might not.
Also, you should be in the ha bit of making a nandroid whenever you flash something, until you can verify there are no bugs you can't live with.
Sent from my Sensation using Tapatalk 2
mk_ln said:
maybe it was just me, but it seems you were right about kernel 017; I probably should have left everything as it was.
after flashing franco's as well as faux's 018, it seemed that 017 was actually slightly smoother. in order to get back to 017 i did as you suggested and flashed the entire rom. unfortunately all my gmail accounts were lost/forgotten as well as the gapps; opening gmail would result in a crash w/o a message...same thing happened with the play store and i had to reinstall the gapps.
i was thinking about flashing just the boot.img from the flashable zip using fastboot, but i wasn't, and still am not, sure if that would have provided me the same result as flashing through CWM.
Click to expand...
Click to collapse
That is exactly what you should have done. Just restoring boot.img is only the kernel. I do it all the time.
RogerPodacter said:
That is exactly what you should have done. Just restoring boot.img is only the kernel. I do it all the time.
Click to expand...
Click to collapse
thanks.
just to confirm, is the command "fastboot boot boot.img" or "fastboot flash boot.img"...? or perhaps something else entirely?
Fastboot flash boot boot.img
"Long is the way, and hard, that out of hell leads up to light."
thanks!
Related
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
joshnichols189 said:
No you didn't do anything wrong. A lot of the kernels aren't updated as fast as kernel changes in CM. Have you tried the latest nightly with the latest LK?
Sent from my SGH-T999
Click to expand...
Click to collapse
I've tried all the latest kernels. Every kernel I've tried is compatible with the ROM I've tried it on.
isikh said:
I really wanna use this kernel/custom kernels, but I give up! Constant force closing and crashes for me Now I'm wondering, did I do something wrong during the root process? I rooted my device a couple weeks ago using this link: http://forum.xda-developers.com/show....php?t=1771687 (Root without tripping flash counter), followed by flashing Team Sonic's TouchWiz Rom, and then now, recently as of a little over a week ago I started using Cyanogen Mod 10. Did I miss a step in between which is causing so many problems with installing a custom kernel on my phone? Lean kernel worked earlier around the 8/20-25 nightlies, but now everything's pretty much a bust
It's a T-Mobile GSIII
Click to expand...
Click to collapse
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
TheAxman said:
if it was me, which btw am running CM10/LeanKernel, I would use odin to flash back to a rooted stock app, then install NEWEST CWM, and try again, I have had no issues EVER using the combo's that you are using. Also, I NEVER flash a kernel on a new rom until the rom has booted correctly, then reboot and flash whatever compatible kernel.
Good Luck.
Click to expand...
Click to collapse
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
isikh said:
Okay I'll do that, but tell me this. How did you come to CM10 exactly? What steps did you do? I want to see if you did something different from me and I may have sent wrong somewhere.
I simply rooted installed freegs3, wiped data and caches and all, then I flashed cm10. Was that the wrong way? Should I go back to stock and restart the process? Because right now for one, custom kernels are giving me strange issues. Also, a ktoonz kernel dev told me my log cat pointed towards corrupt partition or Rom, but I'm using cm10
How do I go back to stock basically? Can you link me to some guides and/or videos? I'm on the T-Mobile galaxy s3. The reason I ask is because I'm mobile and can't search for some reason but I'd like to read up on it before I do it
Click to expand...
Click to collapse
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
TheAxman said:
I started here, READ EVERY LINE in a separate window, so you can reference back in forth between the windows. And do it STEP BY STEP. Once you are rooted and using the stock rom, back that up, so you can revert back to if you crash, once you have those 2 done, get the newest copy of Clockwork, install it. (by the way, the flash counter will tick you using Odin) so make sure you wipe the tick counter before installing any custom roms. Now get CM10 from the thread, install, do not flash the kernel until you have booted the first time, then reboot to recovery and flash kernel of choice. then your set. Now these are MY DIRECTIONS ONLY! and worked for me. So anyone want to add, feel free, or if I missed something, but do NOT slam me for trying to help, again this worked for me, may not for others, but it has been flawless for me. Hope this helps good luck.
Start here>>>http://forum.xda-developers.com/showthread.php?t=1746682
Click to expand...
Click to collapse
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Use this kernel it works perfectly on CM10
http://forum.xda-developers.com/showthread.php?t=1845836
EDIT: nvm use this one http://forum.xda-developers.com/showpost.php?p=31025930&postcount=1152
isikh said:
Thanks for the input! I just wiped everything properly, other than odining back to stock again because that wasn't really necessary I thought since I did everything right, maybe? Well, I don't know lol. I don't have time to go back to stock atm, so I wiped all things including external/internal sd, used superwipe and just flashed a touchwiz rom, by xquizit: http://forum.xda-developers.com/showthread.php?t=1843409 UVALH2 and flashed the kernel for touchwiz by ktoonz and it is running smooth and solid. So, now, I'm going to go back and flash CM from scratch superwiping and all because I have now confirmed ktoonz's kernels work, and for some odd reason it wasn't working with my CM setup, so I'm going try it again from start and see if it works on CM, and go from there. I'll report back either ways in case anyone is having this problem. If I still have the same issue back on CM, I'll live with it or come back to touchwiz. I kinda like it Weird. Haha, but either ways, I'll keep yall updated! I'm wondering if I need to/should flash the UVALH2 radio/baseband since I"m on a UVALH2 ROM though.
Click to expand...
Click to collapse
Now I am a tad confused, you have UVALH2 on the phone already, and you want to flash UVALH2? or did you typo? I am no dev, but from what I have been seeing, the radio should not matter at the moment, if I am wrong, someone please set me straight, also, I will be on the web all night and tomorrow, so I will help where ever I can, I will check here for your progress. Good luck my friend.
BTW, I do not like stock roms, so to me CM10 is for sure better. Faster also.
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
joshnichols189 said:
There is no wrong way to root. I bought my phone, didn't even set it up. Downloaded the toolkit, rooted and flashed a custom recovery, then flashed CM10. You didn't miss any steps, and you didn't do anything in the wrong order.
Your radio and ROM do NOT have to match.
Click to expand...
Click to collapse
Yeah, I know all this, but I wanted to ask in case I may have missed something. Even when you're pretty Android savvy when it comes to rooting and whatnot, you do miss things on occasion. In this instant I didn't, but I was hoping I did because a bunch of custom kernels won't work on my phone with CM10! Trinity worked well, so I'm waiting for those. It must be some specific chip related issue because I'm not the only one. Anyways, thanks everyone!
Hi all,
i´m testing francos kernel for now. But if i want to get back to Stock, where i can download it ? Searched all thru but found nothing.
Thanks for help!
peste
peste76 said:
Hi all,
i´m testing francos kernel for now. But if i want to get back to Stock, where i can download it ? Searched all thru but found nothing.
Thanks for help!
peste
Click to expand...
Click to collapse
If you want to go back to stock, either reflash the stock ROM, or extract the .zip file and then use fastboot to flash boot.img in it "fastboot flash boot boot.img"
kyokeun1234 said:
If you want to go back to stock, either reflash the stock ROM, or extract the .zip file and then use fastboot to flash boot.img in it "fastboot flash boot boot.img"
Click to expand...
Click to collapse
ahh, boot.img - how noobish from me Thanks a lot.
Yes boot.img. If you want to go back to stock... If you want ONLY kernel, you should search it up, because I don't know which file does that...
Let me explain it a little bit more. boot.img is ramdisk+kernel. There's another file I believe that only handles kernel. But if you want to go back to stock, you'll need to flash ramdisk too (Since Franco uses its own ramdisk). I hope that helped you
boot.img = ramdisk+zImage
zImage = kernel
thanks kyokeun1234.
One thing you guys need to keep in mind is that some custom kernels (like franco's) change some files on your ROM (i.e., system partition), so flashing just the stock boot image is not going to be enough. (Don't ask me which files, as I can't remember right now, but there is a few, i.e., 1-3.)
efrant said:
One thing you guys need to keep in mind is that some custom kernels (like franco's) change some files on your ROM (i.e., system partition), so flashing just the stock boot image is not going to be enough. (Don't ask me which files, as I can't remember right now, but there is a few, i.e., 1-3.)
Click to expand...
Click to collapse
Yeah, I always forget that, but actually I am aware of some kernels tweak/place init.d scripts, for example, and that could conflict with stock or any other kernel.
I'll be sure to add that to the usual procedure, making a mental note. thanks efrant.
efrant said:
One thing you guys need to keep in mind is that some custom kernels (like franco's) change some files on your ROM (i.e., system partition), so flashing just the stock boot image is not going to be enough. (Don't ask me which files, as I can't remember right now, but there is a few, i.e., 1-3.)
Click to expand...
Click to collapse
So basically flashing the whole Rom is the only choice
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
You can use franco's app to restore your stock kernel without re flashing your rom.
Sent from my Galaxy Nexus using Tapatalk 2
kyokeun1234 said:
So basically flashing the whole Rom is the only choice
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
It depends on the kernel. What I would do personally is: before flashing a custom kernel, open up the file that you are flashing, and see which files it is replacing (aside from boot.img). Then I would back those up. That way, if you ever want to go back to stock, you just have to replace those files.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
It depends on the kernel. What I would do personally is: before flashing a custom kernel, open up the file that you are flashing, and see which files it is replacing (aside from boot.img). Then I would back those up. That way, if you ever want to go back to stock, you just have to replace those files.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Oh thanks! It's been long time since I've learned a new thing I'll keep that in mind!
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
I have never flashed any kernels, just custom roms. From what I have read it goes down the same way, just flash the zip from SD in recovery and wipe cache. Correct?
Also, if I want to go back to stock kernel can I flash back to a JOP40C ( this one http://forum.xda-developers.com/showthread.php?t=1992483 ) even though my build is JOP40D ?
Robert00001 said:
I have never flashed any kernels, just custom roms. From what I have read it goes down the same way, just flash the zip from SD in recovery and wipe cache. Correct?
Also, if I want to go back to stock kernel can I flash back to a JOP40C ( this one http://forum.xda-developers.com/showthread.php?t=1992483 ) even though my build is JOP40D ?
Click to expand...
Click to collapse
just flash it in your recovery(if its a flashable zip). dont wipe a single thing, dalvik and cache have nothing to do with kernels. worst case scenario, it doesnt boot. then just reflash your rom in your recovery to fix it.
simms22 said:
just flash it in your recovery(if its a flashable zip). dont wipe a single thing, dalvik and cache have nothing to do with kernels. worst case scenario, it doesnt boot. then just reflash your rom in your recovery to fix it.
Click to expand...
Click to collapse
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Robert00001 said:
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Click to expand...
Click to collapse
franco is a good kernel. but most his kernels are in a img form, need fastboot for that. if its a zip, then flash it in your recovery, dont wipe a thing.
simms22 said:
franco is a good kernel. but most his kernels are in a img form, need fastboot for that. if its a zip, then flash it in your recovery, dont wipe a thing.
Click to expand...
Click to collapse
Yes I am sure this is a flashable zip. I found the img files and the zip files on the franco thread.
What about going back to stock? I just want to know if something goes wrong. Does flashing my rom get me the stock kernel back?
Robert00001 said:
Yes I am sure this is a flashable zip. I found the img files and the zip files on the franco thread.
What about going back to stock? I just want to know if something goes wrong. Does flashing my rom get me the stock kernel back?
Click to expand...
Click to collapse
It gets you whatever kernel was originally in the ROM.
063_XOBX said:
It gets you whatever kernel was originally in the ROM.
Click to expand...
Click to collapse
Okay thanks for the replies.
Robert00001 said:
Ok thanks. Yes its a flashable zip, im going for the franco kernel.
Click to expand...
Click to collapse
Even the .IMG files are easy enough to handle, OK so perhaps it might cost you a little money but within the Franco app (I don't know about others as not tried them) but you can simply just choose to restore a .IMG kernel file be it stock (which I have a copy of if you wanted it?) So you can swap and change as you wanted and the plus side of flashing this way is that you avoid the long reboot time dues to catch building again due to ram disk changes. I really think this is the best way of flashing kernels and certainly the easiest way if you wanted to carry on back to the OTA update route from Google.
For instance, I'm running stock takju rom 4.2.1 rom with Franco kernel and I have the stock boot loader and baseband and recovery and to install an OTA I just need to delete just one file and restore back to stock kernel that OTA update will install without troubles
Sent from my Galaxy Nexus
hello all, have a small question, right after i rooted, using odin. ( im on a boost Galaxy SII) i flashed this kernel "41g-VolDbg4-1109" and then the "vanilla rootbox rom" followed its directions. well it was actin a little buggy, so i decided to try a few other roms. flashed the amazing unicorn rom, went just fine., same bugs so i tryed "jelly bam" i think i was flashin the EL26 kernel betweeen all of em. expet for the rootbox rom. well wen i tryed EL26 and then jellybam, it gave me about a paragraph of errors and said "install aborted at the end", tryed to flash the rootbox rom again, same thing. so I flashed the "41g-VolDbg4-1109" zip kernel, rebooted recovery, and flashed rootbox just fine. What was a i doing wrong? it seems like most roms say to use EL26? it was the stock with CW5 in it. Should i just use the 41g kernel i stated above from now on? unless im downgrading or goin back to stock? any help greatly appreciated.
BAleR said:
hello all, have a small question, right after i rooted, using odin. ( im on a boost Galaxy SII) i flashed this kernel "41g-VolDbg4-1109" and then the "vanilla rootbox rom" followed its directions. well it was actin a little buggy, so i decided to try a few other roms. flashed the amazing unicorn rom, went just fine., same bugs so i tryed "jelly bam" i think i was flashin the EL26 kernel betweeen all of em. expet for the rootbox rom. well wen i tryed EL26 and then jellybam, it gave me about a paragraph of errors and said "install aborted at the end", tryed to flash the rootbox rom again, same thing. so I flashed the "41g-VolDbg4-1109" zip kernel, rebooted recovery, and flashed rootbox just fine. What was a i doing wrong? it seems like most roms say to use EL26? it was the stock with CW5 in it. Should i just use the 41g kernel i stated above from now on? unless im downgrading or goin back to stock? any help greatly appreciated.
Click to expand...
Click to collapse
I have flashed vanilla rootbox using EL26 repacked w/ CWM with no issues. Maybe the kernel download is bad. Also don't use wipe all scripts especially the one that wipe the system partition.
BluesRulez said:
I have flashed vanilla rootbox using EL26 repacked w/ CWM with no issues. Maybe the kernel download is bad. Also don't use wipe all scripts especially the one that wipe the system partition.
Click to expand...
Click to collapse
ok, it was jellybelly that gave me the error. everything ells flashes fine. Should i only use the repacked kernels? i was usin just the stock with cwm. i think. and i have always manually wiped system, should i leave it alone from now on? should i just do a factory reset when switching roms?
Use the Stock EL26 w/CWM http://www.rwilco12.com/downloads.p...ernels/Recovery Kernels/GB/Chris41g/Stock CWM
And yes just a factory reset. Blues is right about not using the wipe scripts unless specifically called for by the developer.
leaderbuilder said:
Use the Stock EL26 w/CWM http://www.rwilco12.com/downloads.p...ernels/Recovery Kernels/GB/Chris41g/Stock CWM
And yes just a factory reset. Blues is right about not using the wipe scripts unless specifically called for by the developer.
Click to expand...
Click to collapse
ok, got it. thanks for the info, clears some things up. I always follow directions exactly, sometimes their just not very spacific. this all will help me alot, i have been reading for the past 2 days straight. thanks for helpin me. one last thing, i notice, if i flash EL26, then after flashing rootbox, it replaces the recovery with CWM6, is it ok to just stay in that if flashing another cm10.1 based rom or another rom that has the exact same directions as the last? or do i have to flash EL26 every time i flash a new rom that requires it?
BAleR said:
ok, got it. thanks for the info, clears some things up. I always follow directions exactly, sometimes their just not very spacific. this all will help me alot, i have been reading for the past 2 days straight. thanks for helpin me. one last thing, i notice, if i flash EL26, then after flashing rootbox, it replaces the recovery with CWM6, is it ok to just stay in that if flashing another cm10.1 based rom or another rom that has the exact same directions as the last? or do i have to flash EL26 every time i flash a new rom that requires it?
Click to expand...
Click to collapse
To be fully safe, flash EL26 every time.
BluesRulez said:
To be fully safe, flash EL26 every time.
Click to expand...
Click to collapse
^ that ^
leaderbuilder said:
^ that ^
Click to expand...
Click to collapse
i read somewhere that 4.2 roms have different partition settings and you have to use the one click kernel, not the zip or tar, for it to partition correctly, is this true?
BAleR said:
i read somewhere that 4.2 roms have different partition settings and you have to use the one click kernel, not the zip or tar, for it to partition correctly, is this true?
Click to expand...
Click to collapse
No. Flashing a kernel doesn't repartition anything. It flashes kernel to kernel partition and that's about it.
BluesRulez said:
No. Flashing a kernel doesn't repartition anything. It flashes kernel to kernel partition and that's about it.
Click to expand...
Click to collapse
hmmmm, alright, I wonder why this person claimed this, maybe it was rom spacific, dunno, ill try to find where i read that, and maybe see if i miss read something. thanks for the help. again. thank you.
Edit: i just noticed in the OP i put "jelly bam"... lol i ment jelly belly...
I just got my replacement HTC One V CDMA unlocked and rooted. I want to overclock and understand I need a custom ROM to do so. My first HTC One V I bricked trying to flash rhythmicrom. I unlocked, rooted, backed up using TWM. Each time I tried to flash the new ROM it would get stuck on the HTC screen with the red writing talking about developmental purposes, etc. Each time it would hang on that screen I would simply do a recovery to the back up file and everything would go back to normal. The last time I tried to flash it hung up, and when I tried to go back it would not go back. I am not sure why Rhythmicrom would not work. Is there another one I should try? Does it matter if my HTC one V is a newer version, etc? I just need a basic ROM with the ability to overclock. MMS is a necessity and the camera would be nice. Thanks for any help you can give me.
Did you make sure to flash the appropriate kernel via fastboot aftter flashing the ROM, because if not that could be the cause of your phone failing to boot. As for ROM's, well I guess that depends on whether you have a PrimoU or a PrimoC, I personally use SHPONGLE for the PrimoU, but I can't comment on the PrimoC as I do not own one
zzjoshzz said:
Did you make sure to flash the appropriate kernel via fastboot aftter flashing the ROM, because if not that could be the cause of your phone failing to boot. As for ROM's, well I guess that depends on whether you have a PrimoU or a PrimoC, I personally use SHPONGLE for the PrimoU, but I can't comment on the PrimoC as I do not own one
Click to expand...
Click to collapse
Thank you for the reply. Yes I used the kernel (boot.img) that was included with the rythmicrom rom. I have a PrimoC. I was reading and see that my problem might be caused due to maybe having a newer version of the phone and the hboot or radio might be different?
tackj said:
Thank you for the reply. Yes I used the kernel (boot.img) that was included with the rythmicrom rom. I have a PrimoC. I was reading and see that my problem might be caused due to maybe having a newer version of the phone and the hboot or radio might be different?
Click to expand...
Click to collapse
Hey, so some kernels support the newer radio and some do not. If you are on the newer radio: Baseband version 1.00.00.0928 (check in about phone in settings) then you have to use a kernel that supports the OTA, such as for sense use the FOTA kernel posted under the cdma development thread, for android 4.1 use the kernel I made that can be found in the slim bean rom thread by curtis, and for 4.2 rythmic rom's kernel should work just fine. If not, try the codefirex kernel from simon's rom (original dev. thread) but you'll lose functionality of the camera as it is an ion kernel.
I hope this helps, quote me in the reply if you have more questions, otherwise I may forget to check back here.
why u no flash kernel omg! just read the trouble shooting section
lilrob1213 said:
Hey, so some kernels support the newer radio and some do not. If you are on the newer radio: Baseband version 1.00.00.0928 (check in about phone in settings) then you have to use a kernel that supports the OTA, such as for sense use the FOTA kernel posted under the cdma development thread, for android 4.1 use the kernel I made that can be found in the slim bean rom thread by curtis, and for 4.2 rythmic rom's kernel should work just fine. If not, try the codefirex kernel from simon's rom (original dev. thread) but you'll lose functionality of the camera as it is an ion kernel.
I hope this helps, quote me in the reply if you have more questions, otherwise I may forget to check back here.
Click to expand...
Click to collapse
Thank you very much for you help. I checked my radio and it is 1.00.00.0928. Is this the reason why the rythmicrom kernel would not work? So you recommend using the FOTA kernel with which ROM? Sorry for the dumb questions. I tried my best to read everything I could before asking for help. I just don't want to brick my replacement phone. I am not sue they will be as understanding as they were the first time.
tackj said:
Thank you very much for you help. I checked my radio and it is 1.00.00.0928. Is this the reason why the rythmicrom kernel would not work? So you recommend using the FOTA kernel with which ROM? Sorry for the dumb questions. I tried my best to read everything I could before asking for help. I just don't want to brick my replacement phone. I am not sue they will be as understanding as they were the first time.
Click to expand...
Click to collapse
well it shouldn't have been the reason because if you type "fastboot flash boot boot.img" in command line for the kernel you want to flash then it should flash correctly and rythmic rom's kernel has supported new radio since the beginning pretty much. Unless you have a really old version or something. The FOTA kernel is for sense roms or cm9 (which is based on android 4.0 ics). I really like and very much recommend MyOneV rom that curiousnoob has ported under the cdma dev. thread. It's fast, smooth, and has the least amount of lag compared to any other sense rom that I've tried. It's my daily and go-to rom!
You shouldn't brick your phone as long as you fastboot flash the correct kernel (for primoc/cdma), even if you end up in a bootloop you can hold power button and get back to bootloader to flash a new rom or restore a backup
lilrob1213 said:
well it shouldn't have been the reason because if you type "fastboot flash boot boot.img" in command line for the kernel you want to flash then it should flash correctly and rythmic rom's kernel has supported new radio since the beginning pretty much. Unless you have a really old version or something. The FOTA kernel is for sense roms or cm9 (which is based on android 4.0 ics). I really like and very much recommend MyOneV rom that curiousnoob has ported under the cdma dev. thread. It's fast, smooth, and has the least amount of lag compared to any other sense rom that I've tried. It's my daily and go-to rom!
You shouldn't brick your phone as long as you fastboot flash the correct kernel (for primoc/cdma), even if you end up in a bootloop you can hold power button and get back to bootloader to flash a new rom or restore a backup
Click to expand...
Click to collapse
Thanks for the information. Is it necessary to wipe the sd card before installing the new ROM? This is how I bricked my last one. I read somewhere that I needed to do a full wipe including the sd card. The sd card is where my recovery was and when I wiped it I didn't have anything to recover to. I tried RUU and that did not work.
So I think I might do this kernel [KERNEL][VM/PRIMOC][ICS:Sense] FOTA-Compatible Sick Kernel
With this ROM: myOneV 9.5+CDMA
Does this look ok?
tackj said:
Thanks for the information. Is it necessary to wipe the sd card before installing the new ROM? This is how I bricked my last one. I read somewhere that I needed to do a full wipe including the sd card. The sd card is where my recovery was and when I wiped it I didn't have anything to recover to. I tried RUU and that did not work.
So I think I might do this kernel [KERNEL][VM/PRIMOC][ICS:Sense] FOTA-Compatible Sick Kernel
With this ROM: myOneV 9.5+CDMA
Does this look ok?
Click to expand...
Click to collapse
It isn't necessary to wipe sd card, although if you get any weird bugs that no one else has reported (read threads) then yeah, I'd wipe sd card. In fact, I do actually wipe everything (except sd-ext) from twrp 2.6.1. But before I wipe I mount usb to my computer and copy over the twrp folder with my backup and any pictures I wanna save. Then, wipe everything including sd card (although not necessary I like to do it) and then mount usb again and copy the files I need (rom.zip and twrp folder). But to do a full wipe technically it's just wiping data, cache, dalvik cache, and system.
RUU will not work if you are on the newer hboot version (forgot the number but it's around here which is new vs old).
that combination works for me (I'm on new hboot and radio) so should work fine! btw that's the rom and kernel I mentioned earlier idk if you caught that or not
lilrob1213 said:
It isn't necessary to wipe sd card, although if you get any weird bugs that no one else has reported (read threads) then yeah, I'd wipe sd card. In fact, I do actually wipe everything (except sd-ext) from twrp 2.6.1. But before I wipe I mount usb to my computer and copy over the twrp folder with my backup and any pictures I wanna save. Then, wipe everything including sd card (although not necessary I like to do it) and then mount usb again and copy the files I need (rom.zip and twrp folder). But to do a full wipe technically it's just wiping data, cache, dalvik cache, and system.
RUU will not work if you are on the newer hboot version (forgot the number but it's around here which is new vs old).
that combination works for me (I'm on new hboot and radio) so should work fine! btw that's the rom and kernel I mentioned earlier idk if you caught that or not
Click to expand...
Click to collapse
Cool thank you. Yes I did catch that I just wanted to confirm that was the one you are talking about. I went to download that rom and it said it was not available any longer.
tackj said:
Cool thank you. Yes I did catch that I just wanted to confirm that was the one you are talking about. I went to download that rom and it said it was not available any longer.
Click to expand...
Click to collapse
oh right... curiousnoob is revamping it to make it better, you can either be patient or I can upload you an older version give me a second
here: https://docs.google.com/file/d/0By_o-NyPojUXNTdna3p5bGdSNVU/edit?usp=sharing it's from 09/02/2013 but it's the best I think so far... next update should be awesome-er! haha
lilrob1213 said:
oh right... curiousnoob is revamping it to make it better, you can either be patient or I can upload you an older version give me a second
here: https://docs.google.com/file/d/0By_o-NyPojUXNTdna3p5bGdSNVU/edit?usp=sharing it's from 09/02/2013 but it's the best I think so far... next update should be awesome-er! haha
Click to expand...
Click to collapse
Thank you for all of your help! Will this ROM work with the stock kernel? Just wondering. I would like to overclock so i will be flashing the sick kernel, but I was just curious. Thank you again.
tackj said:
Thank you for all of your help! Will this ROM work with the stock kernel? Just wondering. I would like to overclock so i will be flashing the sick kernel, but I was just curious. Thank you again.
Click to expand...
Click to collapse
kinda... but with stock kernel wifi didn't work... however fota kernel works so great with overclock that there's no need for stock kernel and it's not a problem, I'm happy to help
lilrob1213 said:
kinda... but with stock kernel wifi didn't work... however fota kernel works so great with overclock that there's no need for stock kernel and it's not a problem, I'm happy to help
Click to expand...
Click to collapse
Thank you for the link! I downloaded and got the ROM working now with the stock kernel. Now I am going to try and flash the sick kernel. Just to confirm, this is the one I need:
http://forum.xda-developers.com/showthread.php?t=2261819
I am going to put it in my fastboot folder, rename it boot.img and then flash it using cmd.
Does this sound right?
Also, just an FYI...I received a PM from Curiousn00b stating that the newest version is now available.
tackj said:
Thank you for the link! I downloaded and got the ROM working now with the stock kernel. Now I am going to try and flash the sick kernel. Just to confirm, this is the one I need:
http://forum.xda-developers.com/showthread.php?t=2261819
I am going to put it in my fastboot folder, rename it boot.img and then flash it using cmd.
Does this sound right?
Also, just an FYI...I received a PM from Curiousn00b stating that the newest version is now available.
Click to expand...
Click to collapse
Yup sounds flawless to me! Enjoy it! and thanks for the headsup I will probably download that and test myself
lilrob1213 said:
Yup sounds flawless to me! Enjoy it! and thanks for the headsup I will probably download that and test myself
Click to expand...
Click to collapse
Hey, I got the kernel to work! Now my wifi is operational. Now that the new version is available, do I dare ask how to go about updating? Is it just the same process? Thanks!
tackj said:
Hey, I got the kernel to work! Now my wifi is operational. Now that the new version is available, do I dare ask how to go about updating? Is it just the same process? Thanks!
Click to expand...
Click to collapse
You flashed the fota sick kernel? Well, you can update by just wiping dalvik and cache and flashing the new rom, but it's a full wipe (same process as before) is always recommended over the previous "update"
lilrob1213 said:
You flashed the fota sick kernel? Well, you can update by just wiping dalvik and cache and flashing the new rom, but it's a full wipe (same process as before) is always recommended over the previous "update"
Click to expand...
Click to collapse
Yes, I was able to flash the FOTA sick kernel. I have it set at 1.709 GHz max and 245 mhz min. with the I/O scheduler on noop. I put the governor on "performance" and did a benchmark test with antutu. My score was 7069 which didn't look all that great compared to the others. Does this sound about right? I was also only getting 6.2 fps on the 3D testing.
tackj said:
Yes, I was able to flash the FOTA sick kernel. I have it set at 1.709 GHz max and 245 mhz min. with the I/O scheduler on noop. I put the governor on "performance" and did a benchmark test with antutu. My score was 7069 which didn't look all that great compared to the others. Does this sound about right? I was also only getting 6.2 fps on the 3D testing.
Click to expand...
Click to collapse
hmmm... I have no idea... I've never really messed with benchmarks before, don't think they matter much, I'm happy just having a lag-free phone btw for typical use, I'm sure you know, performance gov. will kill your battery fairly quickly, so I usually use [email protected]$$v2 gov. or lionheart, but usually the first
lilrob1213 said:
hmmm... I have no idea... I've never really messed with benchmarks before, don't think they matter much, I'm happy just having a lag-free phone btw for typical use, I'm sure you know, performance gov. will kill your battery fairly quickly, so I usually use [email protected]$$v2 gov. or lionheart, but usually the first
Click to expand...
Click to collapse
You are right, the phone is more snappy for sure. What GHz do you use for everyday? I was using [email protected]$$v2 gov but put it on performance just during the test. I also have buzzlauncher as my launcher so I am not sure if that is taking away from the performance, but it looks nice. I am just happy that it is working, so again thanks for your help.