I've extracted the stock kernel from the 1.01.1520.0 MR4 OpenMobile leak and zipped it up for anyone who wants it.
As you can see in the screenshots, the version number and dates are newer than the 2.11.605.9 release.
How to install: Wipe cache & dalvik cache, then flash the zip in recovery.
MD5: B41325D3347DDADBDCB6933ED5A0EEF7
Confirmed working on Gingeritis 3D but should work on any Sense-based rom.
As always, flash at your own risk. Recommend performing a nandroid backup before flashing.
Related
Okay, I have successfully rooted my inspire 4g and installed cm7 killer llama v2 on it.
However, I am now interested in updating to the latest RC or nightly of cm7. To update would I simply launch Rom Manager and install the rom that I wish? Do I need to wipe my phone before/after the new rom is installed? For backups I already have titanium backup run and I have titanium sync back it up to dropbox.
Also... is it worth bothering with the radio or kernel versions? Or does the kernel change with each rom?
Thanks in advance for all of the help.
1. Download CM7 RC4 from ROM Manager, but don't flash it from there, as this is more of a chance of a brick, due to the CM7 you're running being customized, go into ClockWorkMod, and choose wipe /data and wipe /cache. Then find the folder the downloaded update is in and use CWM to flash it.
2. NEVER backup/restore system data in Ti Backup between two different ROMs, it will mess things up.
3. Sometimes the kernel changes. (If something needs fixing, or if the dev is just improving the kernel and its capabilities)
4. If you have Radio S-OFF and ENG S-Off I recommend the 12.41.60.19U_26.06.04.14_M radio for all gingerbread ROMs.
Okay, thank you very much for the detailed reply. So if I flash a new rom after wiping data and cache, will I need to reinstall and reconfigure all of my apps?
Three questions:
I was on stock root66 for a while and I had done various tweaks such as system ui, pushing inverted gapps to the system/apps file and other minor tweaks. I am now on my first rom (Paranoid Android 2.13) with Justin bean inverted Gapps. Here come the questions.
1: My baseband is vralg7 on paranoid android Is this because I had flashed this radio on root66 before the aosp rom or is this the radio that is used in paranoid android?
2: Can I just flash a new Gapps if I want to? Is there any special procedure in order to remove the old gapps? Wipe cache and dalvik? ect?
3: If a new version of paranoid android is released, what is the process in order to flash the newer version? Also, if I were to switch to Jellywiz or another rom, what would be my procedure to get from Paranoid Android to jellywiz?
I have searched and I have not exactly found the clear cut answers that I am looking for. Thank you in advance for your time.
elreydenj said:
Three questions:
I was on stock root66 for a while and I had done various tweaks such as system ui, pushing inverted gapps to the system/apps file and other minor tweaks. I am now on my first rom (Paranoid Android 2.13) with Justin bean inverted Gapps. Here come the questions.
1: My baseband is vralg7 on paranoid android Is this because I had flashed this radio on root66 before the aosp rom or is this the radio that is used in paranoid android?
Click to expand...
Click to collapse
The radio aka modem aka baseband was installed when you either accepted the latest OTA or installed it by itself. If you flash roms, this will not change. Modems are installed independent of roms UNLESS it's a Verizon OTA update. PA is likely still based on VRLG1 (like all other roms are at this moment) because either they haven't updated or the source for the latest Verizon OTA was not officially released yet. I'm not an expert on how new vs. old radios work with LTE phones since they often introduce newer versions of a file like RIL within the update itself.
2: Can I just flash a new Gapps if I want to? Is there any special procedure in order to remove the old gapps? Wipe cache and dalvik? ect?
Click to expand...
Click to collapse
Not sure about flashing whichever Gapps whenever you want to. When you install an AOSP rom it tells you which one to download. If AOSP JB IDKIDC rom requires JB IDKIDC Gapps then you must install that specific file. You can reflash the specific Gapps that is required for the rom at a later date if you notice certain Google apps are acting unusual. Does this answer your question? I usually don't mix and match Gapps across different roms if they don't utilize the same exact Gapps file which happens on newer versions of Android sometimes. Normally, they use the same Gapps but sometimes they don't.
3: If a new version of paranoid android is released, what is the process in order to flash the newer version? Also, if I were to switch to Jellywiz or another rom, what would be my procedure to get from Paranoid Android to jellywiz?
I have searched and I have not exactly found the clear cut answers that I am looking for. Thank you in advance for your time.
Click to expand...
Click to collapse
To update from an older build of PA (Paranoid Android) to a newer build of PA: just wipe cache and dalvik cache then flash the newer version OR don't wipe anything and flash the newer version (this is known as a dirty flash or flashover). If you notice issues, do a full wipe and flash the rom. Sometimes the developer changes a lot between releases and if you actively follow that thread, you will see if they announce that you need to fully wipe for the newest update or not. If they release a newer build and don't mention it whether to full wipe or not, either ask politely or likely someone else will.
Going from PA to another rom (one rom to another): full wipe, no excuses. A full wipe is at least Format data, wipe cache, and wipe dalvik cache.
Sent from my SCH-I535 using xda app-developers app
Hello Everyone,
I've just tried to install the slim ics rom.
I've a Nexus S with a version of 2.3.1 android with modaco rom, and i want to "upgrade" my phone to 4.0.4 with slim ics rom.
In the rom site, i saw that i need to "download latest cm9 nightly or any ICS kernel (odin or cmw flashable)", and then: "Enter CWM Recovery, Wipe data, Format System ( In Mounts and Storage)".
I didn't get it - I don't know what to do - to wipe the date (please explain me how to do it), and then install all the cm9 nightly rom which weighs 128mb, and after that the rom?
Thanks,
Or.
orronai said:
Hello Everyone,
I've just tried to install the slim ics rom.
I've a Nexus S with a version of 2.3.1 android with modaco rom, and i want to "upgrade" my phone to 4.0.4 with slim ics rom.
In the rom site, i saw that i need to "download latest cm9 nightly or any ICS kernel (odin or cmw flashable)", and then: "Enter CWM Recovery, Wipe data, Format System ( In Mounts and Storage)".
I didn't get it - I don't know what to do - to wipe the date (please explain me how to do it), and then install all the cm9 nightly rom which weighs 128mb, and after that the rom?
Thanks,
Or.
Click to expand...
Click to collapse
Don't worry about the cm9 rom procedure, here's what to do. I have attached a wipe all zip which is flashable in cwm recovery. Some of this is a bit of overkill, but it will get the job done.
Go to cwm recovery ... wipe data/factory reset, wipe cache partition, go to advanced and wipe dalvik cache. Return to main menu and install zip from sdcard, select zip, and flash the wipe all zip which is attached. Now flash Slim 4.2 and then flash the common zip. Reboot and you're done.
wmdunn said:
Don't worry about the cm9 rom procedure, here's what to do. I have attached a wipe all zip which is flashable in cwm recovery. Some of this is a bit of overkill, but it will get the job done.
Go to cwm recovery ... wipe data/factory reset, wipe cache partition, go to advanced and wipe dalvik cache. Return to main menu and install zip from sdcard, select zip, and flash the wipe all zip which is attached. Now flash Slim 4.2 and then flash the common zip. Reboot and you're done.
Click to expand...
Click to collapse
So don't I need to install cm9?
I only need to wipe as you said and then install the slim ics 4.2?
Thanks!!
Edit:
Never mind, thank you!!
I've just installed the Slim Beans (4.1.2), and it works excellent!
I'd a problem after installing cm10 and then slim beans - the google keyboard crashed, so I didn't have any keyboard. I repaired by wiping the data and cache.
Thanks, it works very good!
I installed the beastmode kernel on my phone a while back. I did this after flashing cleanrom 4.2.2, as I was getting what I thought were dropout issues. However, if I would like to flash my phone to a different rom, do I need to reflash the kernel back to stock, or will the rom already have the kernel included? I made a backup of my phone in TWRP before updating the kernal. If I restore the backup, will the kernel revert back to the stock kernel (I'm S-OFF)?
Thanks!
Since you are s-off, if you flash a new ROM, the kernel will also be flashed. The kernel is typically flashed automatically whenever a ROM is flashed. The exception, for those that are still s-on the kernel will not flash automatically, but needs to be done separately in fastboot.
If you simply want to revert to stock kernel and stay on the current ROM, then you can restore your nandroid (which was made pre-Beastmode) or "dirty flash" the ROM (just wipe Dalvik and cache, then flash it again).
redpoint73 said:
Since you are s-off, if you flash a new ROM, the kernel will also be flashed. The kernel is typically flashed automatically whenever a ROM is flashed. The exception, for those that are still s-on the kernel will not flash automatically, but needs to be done separately in fastboot.
If you simply want to revert to stock kernel and stay on the current ROM, then you can restore your nandroid (which was made pre-Beastmode) or "dirty flash" the ROM (just wipe Dalvik and cache, then flash it again).
Click to expand...
Click to collapse
Thank you for your quick response!!!
I was on CM12 stock 5.0.2 (version 12.0-YNG1TAS2I3) and i wanted to root my phone , so I unlocked bootloader and rooted the phone but now I want to flash a new Rom but I ve read in a couple of rom threads that we have to flash another 5.1nightly before flashing a ROM and I am not sure I understand this part.
I would be grateful if someone could help me with the process of flashing a 5.1 rom and gaaps for the first time on a freshly rooted phone
P.S : ( I also want to use calaukin's gaaps modified by mohit (http://forum.xda-developers.com/oneplus-one/themes-apps/gapps-modified-slim-gapps-calkulin-t3082242).
Flashing the CM12.1 nightly first ensures that your firmware is up to date. The process goes like this:
1. Download the latest CM12.1 nightly and install it with your custom recovery (no need to flash gapps, but make sure you perform a full wipe (system, data, cache, dalvik cache) first).
2. Boot the phone up once.
3. Boot back into your custom recovery and perform a full wipe.
4. Install your chosen ROM + gapps.
5. Boot phone.
6. Enjoy.
Heisenberg said:
Flashing the CM12.1 nightly first ensures that your firmware is up to date. The process goes like this:
1. Download the latest CM12.1 nightly and install it with your custom recovery (no need to flash gapps, but make sure you perform a full wipe (system, data, cache, dalvik cache) first).
2. Boot the phone up once.
3. Boot back into your custom recovery and perform a full wipe.
4. Install your chosen ROM + gapps.
5. Boot phone.
6. Enjoy.
Click to expand...
Click to collapse
Thank you so much . I followed your guide too so thank you for the support .
It is not necessary to flash nightly first, most ROM threads provide a separate firmware flashable .zip (just make sure it is flashed correctly, cause people reported issues with newer TWRP than 2.8.6.0)
davebugyi said:
It is not necessary to flash nightly first, most ROM threads provide a separate firmware flashable .zip (just make sure it is flashed correctly, cause people reported issues with newer TWRP than 2.8.6.0)
Click to expand...
Click to collapse
I used to share your opinion. But, while a lot of ROM threads do provide a firmware zip, they aren't maintained, it's usually uploaded and forgotten about. Flashing the nightly ensures that you're on the very latest firmware available.