Develop Bugs

[Q] ROMs and Kernels?

Hi. I currently own the CDMA Galaxy Nexus, and I have rooted it.
I'm new on Android, and I have many, many questions.
One of the many questions I have is about ROMs and Kernels.
I know how to download and put it in my phone. However, what I'm confused is if I have to wipe the data and do a factory reset before I install a new kernel.
That applies to ROMs as well. Currently, I have the Revolution HD ROM, and I like it. If I want to put on a new ROM, would I have to do a factory reset and then install it?
The rooting world is so very confusing... I hope that someone could help me out.

new rom:
wipe factory, cache, dalvik
flash rom
flash gapps (if required)
flash kernel
reboot.
upgrade rom:
same rom (standard unless specified otherwise by dev)
wipe cache,dalvik [optional]
flash rom
flash gapps (if required)
flash kernel
upgrade kernel:
wipe dalvik, cache
flash kernel

I would add, that at first it seems like a pain, but after awhile, it's no problem.
Also, when you flash a new ROM (and gapps, depending on instructions) I'd recommend waiting on flashing the kernel until you've booted into the ROM and given it some time.

Follow zephik's guide and also remember to backup your apps and data using titanium backup or nandroid. Also it would be a good idea backup your stock radio so that you can reflash it after you flash from and kernel.
Sent from my Galaxy Nexus using xda premium

Superwipe question?

Is it only necessary when coming from ICS to JB or is it necessary to do when coming from a JB ROM to another JB ROM? In my SGS2 days it was factory data wipe, wipe cache, wipe delvik cache, and maybe a kernel cleaning script for good measure, but never touched my SD user content( PDFs, music, etc.).
Super wipe will erase everything( as indicated by the warning in CWM), if you don't think it did cuz you still see the files, try and open them, its a shell only, no content (still lists correct file sizes though???)
I found this out by trying to flash some alternate ROM firmware or kernels I had but couldn't get them to work.

Don't use those stupid superwipe .zip's.
They're running the same scripts as your recovery runs...potentially multiple times for the "LULZOMGCLEAN" factor. [Uh...not needed]
Even installing a rom wipes /system...but %90 of people say "lul wipe /system/ /data/ /cache/ /dalvik/ and then flash superwipe..."
(Yes, I realize a script has to be run for the .zip to wipe system...and the Rom dev MAY leave it out. Personally, if the developer of my rom doesn't even make a "wipe system" script in the .zip I would not use that rom.)
NOT necessary.
If you don't trust your recovery to do it's job...wipe everything with one wipe...
Maybe you should get a new one.

Jubakuba is right but rather than assume the ROM zip wipes /system I find it easier to just wipe it. I never have the problems that others do when they flash ROMs and I always do a factory reset from recovery and wipe system. And if a ROM requires Gapps I always reflash the Gapps after a new ROM update. May not be needed but has saved me from problems before and only takes a couple seconds. Wipe zips are for chimps.

jesusice said:
Jubakuba is right but rather than assume the ROM zip wipes /system I find it easier to just wipe it. I never have the problems that others do when they flash ROMs and I always do a factory reset from recovery and wipe system. And if a ROM requires Gapps I always reflash the Gapps after a new ROM update. May not be needed but has saved me from problems before and only takes a couple seconds. Wipe zips are for chimps.
Click to expand...
Click to collapse
You have to flash Gapps after flashing a rom as they reside in /system/
FYI!

Jubakuba said:
You have to flash Gapps after flashing a rom as they reside in /system/
FYI!
Click to expand...
Click to collapse
Right. Many ROMs like CM are supposed to have a script to preserve Gapps and they say that you don't need to flash Gapps after, say, updating to a new nightly but I've learned the hard way not to depend on it.

[Q] How do I upgrade my CM10?

Total newb question but on the CM10 thread they say:
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Click to expand...
Click to collapse
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?

oshax said:
Total newb question but on the CM10 thread they say:
Instructions:
First time flashing CyanogenMod 10 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
Click to expand...
Click to collapse
dirty flash means you didnt wipe data/cache.
most of the time, you can dirty flash newer versions of the same rom over the older version of the rom you have.
HOWEVER, if you have problems, you need to wipe data/cache and reflash the rom completely

Zepius said:
dirty flash means you didnt wipe data/cache.
most of the time, you can dirty flash newer versions of the same rom over the older version of the rom you have.
HOWEVER, if you have problems, you need to wipe data/cache and reflash the rom completely
Click to expand...
Click to collapse
Guess I might as well wipe the cache and dalvik even on a dirty flash?
Thanks

I upgraded from CM10 M1 to M2 with only a wipe of Dalvik cache. Works fine.

I finished installing M2 after wiping both the cache and dalvik cache (figured I would do the cache just in case).
Worked great!
Thanks all

oshax said:
Total newb question but on the CM10 thread they say:
Instructions:
.... they don't say how to flash if you are upgrading.
Some in the thread say that they just "dirty flash" it.
What exactly is a "dirty flash"?
Click to expand...
Click to collapse
***what Nexus version do you have?*** i've used the below instructions with GSM GNex***
If you're coming from an AOSP CM9 rom, Do the following :
Download Maguro (or your models ROM+Gappsl).
- boot into recovery.
- Preform NANDroid Backup.
- Wipe Dalvik cache.
- Wipe Factory reset.
- Wipe Cache.
- install zip from SDcard>choose zip from SDcard>ROM.zip (your ROM)
- Flash Gapps.zip
- Flash kernel.zip (if you have one)
- go to Advanced> Fix Permissions
- Reboot system now !
- Enjoy.
***I've used this method for a trillion flashes !***

No need to wipe anything when updating nightlies. Like it was said before, wipe data and reflash when you face problems.
Sent from my i9250

bk201doesntexist said:
No need to wipe anything when updating nightlies. Like it was said before, wipe data and reflash when you face problems.
Sent from my i9250
Click to expand...
Click to collapse
+1

[Q] Moving from AOSP ROM's to Touchwiz/Stock Samsung Based ROM's.

Hello,
I had a few clarifications on moving from a CM/AOSP ROM to Stock Samsung Based ROM's.
My phone is a N7100 International Version.
I'm running PACman ROM as my daily driver and I'm actually looking to sell off this phone to a friend who is a Touchwiz fan (bleugh!). He would want to keep root however but wants me to install a stock based ROM.
Questions.
1. Does doing a data/cache/dalvik cache wipe and flash the touchwiz based ROM work? Is it that simple? Is the process similar to flashing CM/AOSP ROM's?
2. I read somewhere that there would be modem issues if the above method is used.
Could someone be kind enough to help me out here. I'm using PhilZ recovery.

Before anything else. EFS Backup and Nandroid back up just in case.
1. PhilZ Recovery
2. Wipe Data & Cache - Clean Install a new ROM then Wipe data & Factory reset
3. Mounts and Storage - FORMAT SYSTEM
4. Install your preferred STOCK ROM TW based.
5. Wipe cache
6. Wipe Dalviks
7. Reboot

warlycastro said:
Before anything else. EFS Backup and Nandroid back up just in case.
1. PhilZ Recovery
2. Wipe Data & Cache - Clean Install a new ROM then Wipe data & Factory reset
3. Mounts and Storage - FORMAT SYSTEM
4. Install your preferred STOCK ROM TW based.
5. Wipe cache
6. Wipe Dalviks
7. Reboot
Click to expand...
Click to collapse
I tried what you had suggested, did not work. Ended up in a bootloop. Had to flash a stock 4.1.2 firmware through ODIN and then root and finally flashed DN3 ROM through recovery. Now it works.
So you just have to move to stock before going from AOSP to TW based ROM's.

Custom rom + Custom Kernel = Black screen..

Hi,
When i tried flashing a custom rom and a custom kernel it just gives me black screen after starting up again maybe you guys have got the same problem before and what did you do to solve this issue? I tried these custom rom/custom kernel combinations :
FreedomOS-op3-nevax-1.7-CE-signed / blu_spark_r114-OOS-6.0.1 thulium
FreedomOS-op3-nevax-1.7-CE-signed / ElementalX-OP3-0.23
ResurrectionRemix-M-v5.7.2-20160804-oneplus3 / blu_spark_r114-OOS-6.0.1_thulium_e476ded
ResurrectionRemix-M-v5.7.2-20160804-oneplus3 / ElementalX-OP3-0.23
My TWRP version is 3.2.1 official
These are one of the many methods i tried:
Method 1
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Wipe cache, Dalvik/art cache.
4. Flash Custom Kernel.
5. Reboot.
Method 2
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Flash Custom Kernel.
4. Wipe cache, Dalvik/art cache.
Method 3
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Flash Custom Kernel.
These are some of the combinations i tried and even some of the methods i tried are nonsens but i am just trying to get it to work. If you need any more information just tell me . Help is very much appreciated .

3.5.2 base dont work with custom kernel yet. The twrp Version is a non known at my End. I think you better read this forum. From A to Z. Since all your awnsers can be found easy.

Saqrez said:
Hi,
When i tried flashing a custom rom and a custom kernel it just gives me black screen after starting up again maybe you guys have got the same problem before and what did you do to solve this issue? I tried these custom rom/custom kernel combinations :
FreedomOS-op3-nevax-1.7-CE-signed / blu_spark_r114-OOS-6.0.1 thulium
FreedomOS-op3-nevax-1.7-CE-signed / ElementalX-OP3-0.23
ResurrectionRemix-M-v5.7.2-20160804-oneplus3 / blu_spark_r114-OOS-6.0.1_thulium_e476ded
ResurrectionRemix-M-v5.7.2-20160804-oneplus3 / ElementalX-OP3-0.23
My TWRP version is 3.2.1 official
These are one of the many methods i tried:
Method 1
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Wipe cache, Dalvik/art cache.
4. Flash Custom Kernel.
5. Reboot.
Method 2
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Flash Custom Kernel.
4. Wipe cache, Dalvik/art cache.
Method 3
1. Wipe Cache, Data, Internal storage, Dalvik/art cache and system.
2. Flash Custom Rom.
3. Flash Custom Kernel.
These are some of the combinations i tried and even some of the methods i tried are nonsens but i am just trying to get it to work. If you need any more information just tell me . Help is very much appreciated .
Click to expand...
Click to collapse
try to flash supersu after the rom, reboot to system. Reboot back to recovery and flash kernel

otonieru said:
try to flash supersu after the rom, reboot to system. Reboot back to recovery and flash kernel
Click to expand...
Click to collapse
I didn't flash SuperSU as it is pre installed..

Darkje said:
3.5.2 base dont work with custom kernel yet. The twrp Version is a non known at my End. I think you better read this forum. From A to Z. Since all your awnsers can be found easy.
Click to expand...
Click to collapse
3.5.2 base? Can you please explain it a little bit more detailed thank you and i already read alot and can't find it thats why i made a thread.

Please read the freedom os topic. It address well why you cannot Flash a custom kernel. It is simply that kernel sources for Version 1.7 (aka 3.5.2 base) are not releases.

Darkje said:
Please read the freedom os topic. It address well why you cannot Flash a custom kernel. It is simply that kernel sources for Version 1.7 (aka 3.5.2 base) are not releases.
Click to expand...
Click to collapse
Oh i see any other idea for doing this with a different freedom os or something

Saqrez said:
Oh i see any other idea for doing this with a different freedom os or something
Click to expand...
Click to collapse
As suggested earlier try reading some ROM threads, going around flashing ROMs and kernels with no purpose is going to get you a soft brick very quickly.
My suggestion decide what you need out of a ROM, that is missing from stock, read a few rom threads to identify one that fills your needs. Then when you've got a ROM in mind go back and read the thread THOROUGHLY before flashing, had you done this with FreedomOS you wouldn't be here now.