[Q] How to patch installed ROM's kernel with "kexec_kernel_42.zip" - Nexus 7 Q&A, Help & Troubleshooting

I am trying to use MultiROM v5, however, I do not know how to patch my installed stock 4.2.1 ROM with the "kexec_kernel_42.zip" patch. I have so far done:
1. Flashed "multirom....zip" via recovery
2. Flashed "twrp modified recovery.img" via recovery
3. Attempted to install Ubuntu (Not working, keeps throwing error)
How do I flash the kernel?

Flashing The Kernel
Okay this is my first post but I have been through the process myself and now dualboot ubuntu 13.04 and android.
The kernel is flashed in the same way as the multirom zip. Hope this helps.
Also two questions, what recovery are you using and where in that recovery did you flash the modded twrp image?
Last I remember you couldn't flash a custom recovery from recovery...
Also just have to makes sure; your tab is rooted right?

Related

4.2.2 recovery help

Hi! Im a noob with a couple of questions hope anyone can help me...
I was recently at 4.2.1 on my nexus 7 had twrp installed, and accidentally updated to stock 4.2.2 my cstom recovery wash flashed by a stock one and forced me to install another via fastboot, but this time i installed cwm then i decided to go back to twrp coZ i dont personally like cwm,. So here is my problem i used rom toolbox to reboot into recovery and it said that i have a cwm installed but when i rebooted i was on twrp, its confusing did i installed both? And made me decide to use rom manager it said that i have twrp and cwm already installed how can i uninstall cmw...
Hope u could help me.. Anyone?
ROM manager plays a clever trick where it temporarily replaces the recovery, even though it is not flashed into the recovery partition.
If you start the recovery from the bootloader, you'll see TWRP; and if you boot into recovery from ROM manager, you will (eventually) see the CWM recovery (you may see some graphics produced by TWRP first, though).
If you have a way (separate from ROM Manager) to boot from the OS into the recovery, you will get TWRP.
bftb0 said:
ROM manager plays a clever trick where it temporarily replaces the recovery, even though it is not flashed into the recovery partition.
If you start the recovery from the bootloader, you'll see TWRP; and if you boot into recovery from ROM manager, you will (eventually) see the CWM recovery (you may see some graphics produced by TWRP first, though).
If you have a way (separate from ROM Manager) to boot from the OS into the recovery, you will get TWRP.
Click to expand...
Click to collapse
Hi thnx for the help, actualy i was able to boot into twrp already and i belive i flashed it completely, my only concern is did i overwrite the cwm in my rec partition? Or it is still there?
Sent from my Nexus 7 using xda app-developers app
There can be only one bootable image in the recovery partition at a time.
If you boot from the bootloader into recovery, and you see TWRP... then that is what is flashed there.
If you want to see what I am talking about, go into ROM manager and select the menu item that causes a boot into recovery. What you will see (after a little bit) is the CWM U/I.
What is going on is that ROM manager boots whatever recovery is actually flashed in the recovery partition, and then immediately replaces /sbin/recovery with it's own version (CWM) and then kills & restarts that same program.
So - what you *see* is the CWM version of /shin/recovery - running on top of the kernel & ramdisk were provisioned by the whatever recovery was actually flashed to the recovery partition.
If you want to actually flash CWM to the recovery partition, ROM Manager has a menu item for that. I'm not sure what the exact wording is.
If you are confused by this, just read the first two sentences in this post.

[Q] Replace TWRP with latest ClockworkMod

Hi all,
Could not find anything related to this so will just ask.
I am currently on CarbonROM and have TWRP as my recovery. I have read that with Android 4.4, you will less problems flashing it over 4.3 if you are on CWM rather than TWRP.
So can I just flash the latest CWM over my current TWRP using the following command: fastboot flash recovery recovery-clockwork-touch-6.0.4.3-mako.img ?
Thank you in advance.
yes, you can just flash right over. or.. you can use the modified multirom version of twrp if you want to keep using twrp, kitkat flashes fine with it http://forum.xda-developers.com/showthread.php?t=2508840

kernel trouble

Ive run into a problem and need some help.
im running stock 5.0 with multi-boot and have autodroid 1.2 as a secondary rom for nethunter.
all was running well untill i used the "flash image gui" while booted into autodroid to flash the m4xx3dout .img
now my internal 5.0 rom will not boot it just loops at the circular-wavy-dots lol, i can still boot autdroid however. so still have access to storage and all my data (thanks multi-boot). autodroid rom is still showing as kangaroo kernel.
ive tried flashing the kexec_50_final zip in the "flash img gui app as well as in multiboot recovery to no avail.
any ideas?
No one?

Trouble changing recovery and ROM

Hey guys,
I'm having trouble updating both my recovery and flashing a new ROM.
My bootloader is unlocked and I'm rooted, currently have TWRP 2.8.7.0 and the final release of OxySlim 2.2.0 - http://forum.xda-developers.com/oneplus-2/development/rom-oxyslim-t3278169
Whenever I flash a new recovery via adb/fastboot I just get stuck on the One+ bootscreen.
I have to reflash 2.8.7.0 to get access to recovery again.
I've been trying to move to Seraph's ParanoidAndroid here: http://forum.xda-developers.com/oneplus-2/development/5-1-1-paranoid-android-5-1-t3205522
Or to Grarak's CM 13 here: http://forum.xda-developers.com/oneplus-2/orig-development/rom-official-cyanogenmod-13-t3392278
I've also tried flashing Seraph's HybridRecovery 3.4 with no luck.
Am I missing something? I flashed all the version of OxySlim with no problems.
Quick update.
I've flashed halogenOS: http://forum.xda-developers.com/oneplus-2/development/rom-halogenos-oneplus-2-t3377799
It booted up but I couldn't select a language... strange.
So I tried to boot into recovery and it stuck on the boot screen.
I've now flashed the latest TWRP (3.0.2) and it's working. Currently doing a full wipe and trying halogenOS again.

TWRP Loop

Hi,
after flashing serveral custom roms (with open bootloader) via twrp (latest version), which btw worked perfectly till now, i suddenly produced a twrp loop. I tried to flash another custom rom, reinstall twrp, but no rom boots. Only twrp appears.
Because of this i can´t also open the port to flash a stock rom via QFIL. Is it possible in my situation to remove twrp and install stock recovery? I can´t find a corresponding img file.
Thanks!

Resources