I flashed **** kernel and now I have issues with aosp roms. Is there a way to go back to base? Its very annoying not being able to use PE
Kernel is actually in boot.img so whichever rom you were using just flash it's boot.img back and it will work
Related
how should i install miui over cm7 rom ??? Should i go back to stock or is it ok to use CM7 cwm recovery ???
You can just use the recovery that came with CM7, no need to flash to stock.
*Get Chance and Luck*
And what if i want to go back from miui to cm7? Should i have to go back to stock or miui cwm wil b ok to flash cm7 ?
again no need to flash to stock...as MiUI is based on CM7...only flash to stock if you are going to flash to non-CM7 (MIUI) rom.....
also flash to stock if you are stuck in bootloop....
To follow up / add on to what vinyl2cool said, you can think of it this way:
MIUI, CyanogenMod, and ICS are all based around CyanogenMod's take on Android. It may take a couple of reflashes in CWM to move between them, but they will all work together, no special steps (e.g. Odin or Heimdall) needed.
Any rom with a 3-letter acronym starting with J or K (e.g. KK4, JVZ) will allow you to jump to another one from CWM. It may take a couple of preparation steps, but again, you shouldn't need Odin or Heimdall.
Pretty much the only time you will need Odin or Heimdall for rom flashing is if you're jumping between those two camps. (That's not to say there aren't cases where Odin/Heimdall have other uses, but that's another topic for another day.)
I have been using Samsung for a long time and so this process seems weird. All we use to do there was just put the custom ROM and GAAPS and flash it via recovery and wipe phone. But when i was going through a lot of forums here..i see that the OP has asked people to flash the boot file using command prompt and then flash the ROM. Is this process really required even if we have the dual recovery installed?
If the updater script in the .zip does not have the correct commands to install the boot.img itself it has to be manually flashed.
Untill recently this was always the case, it was not possible to flash a kernel using recovery, it had to be done via fastboot.
I think this is probably a hangover from then, but now it can be done in recovery.
Also, if you have just unlocked, but do not have recovery installed the quickest way to get recovery is to flash the boot.img using fastboot, then flash the update.zip.
If you already have recovery, just flash the update.zip and the boot.img will be flashed.
This is only for roms int he original development section, as they require a custom kernel, roms in the development section will work on the stock kernel, so there is no need to flash a boot.img at all
Actually you need to flash different kernels for different roms... Like Stock-based(Sony) Roms can be either run on Stock Kernel(Sony) or Stock-Based Custom Kernel(like DooMKerneL). while AOSP Roms(like CM11) should be run on AOSP-based Custom Kernels(like Pimped Kernel).
You can flash custom Kernels only if you have unlocked your bootloader. if you have recovery on locked bootloader, then you can flash only Stock-based roms because they dont need a different kernel becoz they run on Sony Kernel itself. If you have a unlocked bootloader you can flash custom kernel, Then you can use both Stock-based Roms or AOSP-based Roms by flashing respective kernels.
If you already have Custom rom installed and changing to another Custom rom, Then if you are changing from (Stock-Based Rom to another Stock-Based Rom) or (AOSP-based Rom to another AOSP-based Rom) then you need not flash the kernel again, you can just wipe all partitions and install the new Custom rom over it. But if you are Cross flashing from (Stock-Based Rom to AOSP-Based Rom) or (AOSP-based Rom to Stock-based Rom), Then you should flash respective kernel, wipe partitions and install the rom over it.
if you dont know, whether the rom is Stock-based or AOSP-based, it will be mentioned in the OP of each Thread.Usually Roms that are available for a wide range of devices across OEMs are AOSP. Roms like CM, AOKP, PAC, Carbon, etc. are all AOSP roms.
Hope it helped.
My device is GT-N7000, using N7000ZSLR1 Android 4.1.2 stock ROM （Build number：JZO54K.N7000ZSLR1）, used Chinese one key root app to root but unrooted to go to stock recovery to flash the newest Philz recovery (because Odin v3.09 failed to flash it), but fail like below screenshots:
I wonder why, I downloaded from the official platform (https://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7000/), and my internet is good so there should be no corrupted files. All stuffs are stock now, so I dunno why.
(Additional info: If I flash "PhilZ-cwm6-XXLTA-ATL-5.15.0.tar.md5" using Odin, it works, but I want to use the latest Philz recovery, plus, the recovery will switch back to stock one after usage, that means after I press "reboot system now" in Philz recovery XXLTA-ATL-5.15.0, and power off and go to recovery mode again, it's the stock one. Dot't say something like "Oh flash this one then").
If you are on a stock 4.1.2 rom there is no way you can update to a newer recovery using philz. As he stopped updating the old kernels. You may try some other custom kernel.
The advanced Cwm edition will not work using odin or recovery. So leave that alone.
The XXLTA you flashed is a right path but it should not revert to stock recovery. There is zip version of that file. Flash it through the stock recovery.
nokiamodeln91 said:
If you are on a stock 4.1.2 rom there is no way you can update to a newer recovery using philz. As he stopped updating the old kernels. You may try some other custom kernel.
The advanced Cwm edition will not work using odin or recovery. So leave that alone.
The XXLTA you flashed is a right path but it should not revert to stock recovery. There is zip version of that file. Flash it through the stock recovery.
Click to expand...
Click to collapse
Which custom kernal you recommend, and is stable then?
And which 'Old" Philz kernal is the "newest" to my ROM? I mean the newest in the old kernal, if you get what I mean.
Vulturon said:
Which custom kernal you recommend, and is stable then?
And which 'Old" Philz kernal is the "newest" to my ROM? I mean the newest in the old kernal, if you get what I mean.
Click to expand...
Click to collapse
The XXLTA you flashed seems to be the latest from Philz list of recoveries for TW 4.1.2 kernels for now.. You may check forest's kernel.. I think it has an updated recovery.
If I flashed a rom that has a different kernel and then went back to a rom that has a stock kernel do I not have a stock kernel anymore?
I went from Poprocks to texodus then back to poprocks.
If the new rom you flashed included the stock kernel, then that's the kernel you have now. Kernels don't survive a rom flash, they get overwritten by whatever kernel is included in the rom.
Thanks
So I'm still kind of a newb in this flashing thing and since I couldn't find anything using the search box here it go:
I an using Xceed custom kernel and now I want to try another one, but even after I flashed another custom ROM I noticed that Xceed still is my current kernel.
How do I safely change from one custom kernel to another? Do I have to flash stock MIUI again to return to stock kernel or is there an easier way? I ask because the last time I flashed the stock ROM I thought I had bricked the device.
Thanks in advance.
You shouldn't flash a custom kernel over another custom kernel. If you have made a backup of 'boot' in twrp, restore 'boot' only and then flash another kernel. If you haven't made a backup, then your only option is reflashing miui.