Related
Hello,
i recently installed 3rd party kernel on my rom and i would like to revert back to the rom stock kernel, i'm aware that i can flash boot.img, but I got a bit confused when I tried to flash it via gnex toolkit - what options shall I choose ? permanent/temporary - and which section shall I select after that screen ? unless of course there are easier methods to install boot.img - such as through manual adb fastboot command.
any help would be greatly appreciated,
Thanks!
If you want the rom stock kernel just reflash the rom.
"Long is the way, and hard, that out of hell leads up to light."
thanks, of course that's an option, but i was trying to avoid that, anyhow I managed to install just the stock kernel without having to reflash rom - i used gnex toolkit, copied boot.img (extracted from rom) into appropriate toolkit folder and selected the first option (boot) and voila i have the rom stock kernel...thanks anyway.
If you had a nandroid with that stock kernel just do advanced restore of the boot.img only.
Was this a question or a statement? As its in the q&a section, people gave you suggestions and you reply by correcting them and telling them what you did.
Why even ask or post it in the q&a thread??? (question)
Sent from a phone...
this seamer
@edfunkycold
easy mate, chill...was just a question, I didn't correct anyone, just wanted to let anyone know that I sorted it out somehow...perhaps it can help other users, especially newbies like me..
@jerrycycle
thanks mate!
zeelog said:
@edfunkycold
easy mate, chill...was just a question, I didn't correct anyone, just wanted to let anyone know that I sorted it out somehow...perhaps it can help other users, especially newbies like me..
Click to expand...
Click to collapse
I wasn't in attack mode just inquisitive as I didn't understand is you were asking or saying. Suggestion maybe you should update title of thread and place [fixed] or something like that. Glad you got it worked out. Another question for you, why where you so opposed to just reflashing your rom? You don't have to wipe just flash right over and in less than 1 minute it would have been done and the kernel your rom came with back on?
Sent from a phone...
Sorry repost please delete
edfunkycold said:
I wasn't in attack mode just inquisitive as I didn't understand is you were asking or saying. Suggestion maybe you should update title of thread and place [fixed] or something like that. Glad you got it worked out. Another question for you, why where you so opposed to just reflashing your rom? You don't have to wipe just flash right over and in less than 1 minute it would have been done and the kernel your rom came with back on?
Sent from a phone...
Click to expand...
Click to collapse
ed, for the simple reason that i'm using paranoidandroid, now imagine i have tons of apps using different lcd densities, thus reflashing the rom would have resulted in re-setting the densities for each and every app from scratch (at least i'm assuming that would have happened) - i wouldn't have bothered if i was using another rom such as aokp or something similar...
edfunkycold said:
Was this a question or a statement? As its in the q&a section, people gave you suggestions and you reply by correcting them and telling them what you did.
Why even ask or post it in the q&a thread??? (question)
Sent from a phone...
Click to expand...
Click to collapse
Because the first suggestion (flash a stock rom) doesn't make sense. Why would he flash a stock ROM when all he wanted was the stock kernel? (Yes, it was not written clearly, but it was pretty obvious he wanted to flash the stock kernel, not the stock ROM...)
joshnichols189 said:
If you want the rom stock kernel just reflash the rom.
"Long is the way, and hard, that out of hell leads up to light."
Click to expand...
Click to collapse
It said reflash rom it didn't say anything about stock. He wanted the kernel which his rom came with.
simply by flashing it over his existing setup without wiping would have replaced the kernel to what he wanted and maintained all his settings as he currently has them. Simple less than 1 minute resolve. But hey he did it anyway the long route by extracting and flashing image on fastboot. That he resolved what he was trying to accomplish is all that matters. Symantics about which way may have been easier is of no consequence, I was just curious as to why he didn't try what seemed as the simplest route.
efrant said:
Because the first suggestion (flash a stock rom) doesn't make sense. Why would he flash a stock ROM when all he wanted was the stock kernel? (Yes, it was not written clearly, but it was pretty obvious he wanted to flash the stock kernel, not the stock ROM...)
Click to expand...
Click to collapse
Sent from a phone...
The way i see it, OP should just use the tools, not the toolkits.
Simply rebooting to bootloader, extract boot.img from his current rom, 'fastboot flash boot boot.img' would avoid reflashing the entire rom.
Or, through a previously taken nandroid, choose advanced restore in recovery, and only restore boot.img.
Sent from my i9250
I'm a long time user of CWM on my SGS1 and, lately, of TWRP on my SGS3, but I never had to restore a backup created in either recovery.
Now, I'm looking forward to flashing ktoonsez's Sammy kernel on my rooted Bell LH1 ROM and there is one piece of warning that makes me a little unconfortable...
ktoonsez said:
WARNING: This kernel has updated WIFI and Bluetooth drivers. If you are going back to stock, you need to get those drivers back or those 2 devices will not work. Simply flashing a kernel will not do it unless it also flashs back those drivers (they are in "/system/lib/modules" folder).
Click to expand...
Click to collapse
Let's say I create a backup of my current config in TWRP, flash ktoonsez kernel and then restore my backup.
Will I restore the original kernel along with the rest (wifi and usb drivers included) or is the kernel not part of the backup ?
Thanks
HiKsFiles said:
I'm a long time user of CWM on my SGS1 and, lately, of TWRP on my SGS3, but I never had to restore a backup created in either recovery.
Now, I'm looking forward to flashing ktoonsez's Sammy kernel on my rooted Bell LH1 ROM and there is one piece of warning that makes me a little unconfortable...
:laugh:
Let's say I create a backup of my current config in TWRP, flash ktoonsez kernel and then restore my backup.
Will I restore the original kernel along with the rest (wifi and usb drivers included) or is the kernel not part of the backup ?
Thanks
Click to expand...
Click to collapse
I suggest you test it out for another type of kernel like flash two jb roms and flash a cm10 kernel and see if you still have the original kernel with the first rom just to test if it actully backups the kernel too.. i have TWRP too xD too bad i got my fone tooken away or id test this out my self :laugh:
nandroid backs up your kernel and drivers. So as long as you have a backup you should be fine
amzi said:
I suggest you test it out for another type of kernel like flash two jb roms and flash a cm10 kernel and see if you still have the original kernel with the first rom just to test if it actully backups the kernel too.. i have TWRP too xD too bad i got my fone tooken away or id test this out my self :laugh:
Click to expand...
Click to collapse
Dude, that's like going to New-York from Montréal but stopping by Los Angeles on your way.
Feasable... but it'll take you ages!
HiKsFiles said:
Dude, that's like going to New-York from Montréal but stopping by Los Angeles on your way.
Feasable... but it'll take you ages!
Click to expand...
Click to collapse
bro ur just lazy it doesnt take that long LOL
True, I am lazy by nature and I assume it pretty well!
hi..
i have a stock rooted and bloated xplay (not much time to fiddle) w/c i bought a year ago.. so i was thinking of changing roms and i plan on using the phone for gaming.. i have read some thread about pros/cons of custom and stock-based. others say that the stock rom is still the best for gaming (debloated of course).. so my question is..
should i go for a custom rom..? or stick with stock..?
if i'll stick with stock.., what's the best baseband(?) ..? currently mine's on .42...
what are the apps w/c are safe to delete..?
as for overclocking.., what is the best kernel that you'd recommend..?
thanks...
Xperia NXT lite with doomkernel
i was looking into that actually...
but some cons have given me second thoughts.. like wifi issues and unsupported touchpads (other roms).. that's why i'm asking about stocks..
this will also be my first time flashing custom roms.. kinda scary.. wehehehe...
qtjecs said:
i was looking into that actually...
but some cons have given me second thoughts.. like wifi issues and unsupported touchpads (other roms).. that's why i'm asking about stocks..
this will also be my first time flashing custom roms.. kinda scary.. wehehehe...
Click to expand...
Click to collapse
I think you should stick with the stock. This is the most.stable & supports full touchpad.
Custom roms are not as stable as stock...
I think you can just use v6 supercharger or supremacy script to make your rom fast...
[ you have to do it manually with smanager]
Press thanks if I helped..
Sent from my ST18i
thanks.. maybe i'll try them both...
i just want to ask for the list of bloatwares.. : )
thanks
First of all, you have to give MORE info about the phone: locked/unlocked bootloader, phone model.....
I advice you to get a stock-based rom, instead of sticking with the stock one, because those are inproved with some tweaks that cannot be flashed on your current stock, and have built-in apps and are already debloated.
If this is your first rom flash, just follow this steps:
BEFORE DOING ANYTHING, get the stock firmware that fits your region and stock android version if you want to go back from here or anywhere else
- root with any method, I recommend SuperOneClick
- install ClockWorkMod via RecoverX
- install TitaniumBackup from the market, and backup all user apps you want have in your new rom (be careful, some roms and kernels doesn't go well with backup restoration. Check the rom's thread for backup issues)
- reboot into CWM recovery and do a nandroid backup. It will save everything and you can restore your phone to its initial state, to the point you can not tell if it has had any changes
- flash the rom following the instructions given by rom builder
- flash any addons you want after rebooting at least one time, every addon separately (1 reboot after every addon)
- if you want better performance, get supercharger v6 or supremacy script as said before
Now, the stock firmware you got at first is to repair your phone if a nandroid backup restore doesn't do it.
If youwant to go back to stock, just restore the nandroid backup. If you want to take it to the carrier to fix it for whaterever reason, you also have to unroot and delete any app that uses root permissions, like TitaniumBackup. Then, when you see your Play is exactly as it was before doing anything of this, you can take it there safely
And finally, the best baseband is -36 cause it has the more balanced stats between signal reception on gsm/wifi and battery consumption, but some roms use -64. If you're adviced to flash a stock firmware before the custom rom flashing process, thats for installing the needed baseband and some other components. Happy flashing!!!!
---------- Post added at 04:02 AM ---------- Previous post was at 03:37 AM ----------
qtjecs said:
as for overclocking.., what is the best kernel that you'd recommend..?
thanks...
Click to expand...
Click to collapse
All custom kernels support overclock and all are good at it. Just flash the kernel according to your rom cook's advice
And if you were wondering, custom roms doesn't have any problems/bugs if they are finished. You should expect bugs if there is only the first or second release of that rom, but if it's finished you'll be fine by following the steps exactly as directed.
You can try The JokaWild ROM 'S.B .69 Tweaked ROM' FINAL (v3) and DiXperia 2 'Everlasting' | Performance. Stability. Experience. if you want a stable, fast rom. Those have given me good results, but if you want to know which is the best rom you have to try them all cause they don't run exactly they same on all phones, even if it's the same model. Maybe NXT or Aurora rom could be better for you....
Please click "thanks" button if I helped
While you're dispensing advice, may I ask which upgraded kernel is best to use with R800i_4.0.2.A.0.62_(1253-4437)? That's what I have on my device.
Is there any benefit to actually installing cwm with RecoveryX as opposed to just loading it with fastboot when needed? That is, will I be more likely able to launch it in a crisis if it is installed on the device?
drinkypoo said:
While you're dispensing advice, may I ask which upgraded kernel is best to use with R800i_4.0.2.A.0.62_(1253-4437)? That's what I have on my device.
Is there any benefit to actually installing cwm with RecoveryX as opposed to just loading it with fastboot when needed? That is, will I be more likely able to launch it in a crisis if it is installed on the device?
Click to expand...
Click to collapse
RecoverX is the easiest way to get CWM. Think about it as a quick 3-step process that you will do only one time. You don't lose anything
Additionally, I don't know what process are you talking about, since flashing a clockworkmod.img, installing the CWM app from the market and RecoverX have permanent effects all of them. The only exception is when you change kernel and it has a built-in recovery, you get the kernel's recovery instead of the original one. I recommend RecoverX because it supports the widest range of phone models and firmwares (I have an r800a, but it was not listed as a supported device in the CWM app, so...)
And again, it's always better to have a custom stock-based rom than just the 4.0.2.A.0.62 stock one
julian280 said:
Additionally, I don't know what process are you talking about, since flashing a clockworkmod.img, installing the CWM app from the market and RecoverX have permanent effects all of them. The only exception is when you change kernel and it has a built-in recovery, you get the kernel's recovery instead of the original one.
Click to expand...
Click to collapse
fastboot boot boot.img (with a cwrecovery boot) appears to get you straight into cwrecovery without installing anything, as opposed to fastboot flash boot boot.img
julian280 said:
And again, it's always better to have a custom stock-based rom than just the 4.0.2.A.0.62 stock one
Click to expand...
Click to collapse
Well, I took your advice, and I installed doomkernel and jokawild
http://forum.xda-developers.com/showthread.php?t=1176502
http://forum.xda-developers.com/showthread.php?t=1532883
I only wish I had known sooner what was in the addon packages for jokawild, that could be documented a lot better. basically that's where all the apps went.
now I will probably reflash and do it right
no cifs in doomkernel
JIC anyone is wondering
CIFS and NFS were taken out and then he moved on to the ray or something
drinkypoo said:
Well, I took your advice, and I installed doomkernel and jokawild
http://forum.xda-developers.com/showthread.php?t=1176502
http://forum.xda-developers.com/showthread.php?t=1532883
I only wish I had known sooner what was in the addon packages for jokawild, that could be documented a lot better. basically that's where all the apps went.
now I will probably reflash and do it right
Click to expand...
Click to collapse
So, have you had a happy flashing? I hope so.....
About the addons you don't have to reflash everyting to install them, just flash one by one, separated by a reboot (you can reboot directly into CWM instead of loading to homescreen everytime, that woluld take ages to flash all of them ).
If you were wondering about root, it's not necesary to flash the root addon since doomkernel is already prerooted, so you get superuser since the first boot with it
I have had a pretty happy flashing, in that nothing went horribly wrong
I do think I more or less know what I'm doing now. Heh heh.
As you can see from my sig I am now running lupus v6 and it's been very stable, smooth, etc. And I added the cifs and ntfs modules. I didn't reboot between everything which is probably why I had to load the wifi modules over again, so I'm very glad they were provided. But everything is working great now, thanks.
drinkypoo said:
JIC anyone is wondering
CIFS and NFS were taken out and then he moved on to the ray or something
Click to expand...
Click to collapse
I don't know you, but I can access my pc files from my Play with "ES file explorer" without even installing CIFSmanager. The changelog in DK's thread says he removed it, but at least for me it works .
To access from the phone to pc you have to put the folder you want as a "shared folder" and give "total control" permissions to "all". For accessing from the pc to phone just do the same with the folder on your sdcard connected to pc and, go to tools/connect to network device and select that folder. Now you can view your files and do streaming by opening the folder on ES file explorer in LAN section and from "My PC", where it appears as a hard disk with drive letter
e.g. music on "Xperia PLAY R800a" (H:/)
Hope this helped. I'm on DooMKernel v14 with jokawild but this has worked on other ROMs
Please click "thanks" button if I helped
---------- Post added at 06:01 PM ---------- Previous post was at 05:42 PM ----------
drinkypoo said:
fastboot boot boot.img (with a cwrecovery boot) appears to get you straight into cwrecovery without installing anything, as opposed to fastboot flash boot boot.img
Click to expand...
Click to collapse
I rarely use command prompt to perform operation cause I prefer to use flashtool instead, and the only time I installed CWM was through RecoverX, so I haven't experienced the difference.....
Yeah I've used the smb built into ES but I prefer to use the smb functionality built into the Linux kernel to using libsmb, which is what's happening when you use es file explorer, or pretty much anything else with built in smb browsing. I also don't care for ES file explorer's interface. Of course, open manager doesn't have smb support...
I have figured out the mtp/msc stuff some time ago.
anyway, pretty much all the kernels have a recovery, some of them have too many recoverys in my opinion so it doesn't really matter. but if you use fastboot boot boot.img then it boots without installing. I don't know if this works for anything but recovery, like if you could boot a kernel this way, probably not. I like command-line stuff. I do use flashtool's gui for ftfs though, of course.
a little off topic..
what should be the sequence..?
from stock..,
nandroid BU, flash pre-req stock ROM, unlock bootloader, flash custom ROM,..?
- or -
nandroid BU, unlock boot loader, flash pre-req, then custom ROM..?
will i lose root access when i unlock the boot loader.?
thanks...
qtjecs said:
will i lose root access when i unlock the boot loader.?thanks...
Click to expand...
Click to collapse
In my case I reflashed with a stock ftf right after unlocking, and then installed a kernel which rooted.
drinkypoo said:
In my case I reflashed with a stock ftf right after unlocking, and then installed a kernel which rooted.
Click to expand...
Click to collapse
..?
so it's nandroid BU, unlock boot, kernel, stock ROM then custom ROM..?
a few more question..
will i lose unlocked bootload when i flash rom..?
is kernel also included when you do a nandroid BU..?
sorry.. just a newbie...
thanks...
qtjecs said:
..?
so it's nandroid BU, unlock boot, kernel, stock ROM then custom ROM..?
a few more question..
will i lose unlocked bootload when i flash rom..?
is kernel also included when you do a nandroid BU..?
sorry.. just a newbie...
thanks...
Click to expand...
Click to collapse
you have the sequence right, I don't know if nandroid backs up the kernel. I would guess no, but I could be wrong, and hope I am.
you don't care anyway. you can reflash back to a stock kernel. just make very very sure you never flash a cdma to a gsm or a gsm to a cdma. a, at, i are all gsm... if you do that you need testpoint reflash as far as I know.
you should also do a titanium backup, that gets you all the apks on your system now, handy for restoring any games on your current rom that aren't on your new rom.
Well, you can unlock your downloader at any time, by IMEI method through Sony webpage or through alejandrissimo's testpoint method. It is permanent, so it doesn't matter if you change Rom or kernel, it will remain unlocked forever , and if for whatever reason you have to take your phone to carrier for warranty, it will appear locked for Sony (I already did it, and they didn't void my warranty)
Just follow the steps I gave you, it's not that complicated. You can flash first the Rom or first the kernel, it doesn't affect anything, except when you change android version (GB to ICS or something), then flash the kernel first and then the new Rom.
Flashing a rom doesn't change the kernel, so if you're on DoomKernel and "A" Rom, you can switch to "B" Rom and stick to DK, IF IT'S ON THE SAME ANDROID VERSION.
Also you can change kernel while keeping the same rom
And respecting to nandroid backup, it saves everything but kernel, baseband and some sections of internal memory that you should not worry about. That's why you're able to restore a backup with the same or other kernel without any worry
Sent from my R800a using xda app-developers app
I have a GSM Galaxy Nexus and I am currently using 4.2.2 Cyanogen Mod released in April 2013.
It has the following Kernel
3.0.31-cyanogenmod-g64e9296
I have flashed ROMs many times mostly CM ROMS.
I want to try changing kernel to improve battery life and check what kernel changes actually is all about.
Since I havent done it earlier, I want answers to following questions:
1) Is it safe to change my kernel to another one? I want to install http://forum.xda-developers.com/showthread.php?t=2115590 or maybe someone can tell me a better one with focus on improved battery life.
2) What if the above kernel screws up? can I recover the old kernel back?
3) Is kernel flashing Permanent or any ROM I flash will have it's own kernel?
4) Just in case my kernel screws up, I have a full TWRP backup as well, would flashing that change my current kernel to old one that came with cyanogenmod last ROM?
Thanks.
You can pretty much flash any kernel you want. Just make sure the kernel is made for the version of Android you are on. If something goes wrong, you should be able to flash your ROM again and get back to normal. ROMs come with their own kernels so every time you flash a ROM, you will get the kernel that comes with it. But the best way to recover from a screw up is to restore a nandroid from your recovery.
jsgraphicart said:
You can pretty much flash any kernel you want. Just make sure the kernel is made for the version of Android you are on. If something goes wrong, you should be able to flash your ROM again and get back to normal. ROMs come with their own kernels so every time you flash a ROM, you will get the kernel that comes with it. But the best way to recover from a screw up is to restore a nandroid from your recovery.
Click to expand...
Click to collapse
Advanced restore should work, no need to restore the whole thing, just system.img and boot.img should do the trick.
Sent from my Nexus
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.