why i must install cwm every time boot into built-in recovery?
i am lpf +rooted +super su + speed mod kernael
because most likely you're using a version of speedmod kernel where CWM isn't installed by default.
I believe he added CWM in r3 ,download the latest version and you're good to go
Related
Hi all, I have the I9000 with stock (branded, h3g ita) firmware Froyo 2.2
I recently removed Ryanza OCLF and flashed Speedmod Kernel k13e in order to be able to use ROM manager and use custom ROMs... but there's my problem, if it is one...
When I enter Recovery Mode, it automatically opens ClockworkMod Recovery 2.5.1.0, that comes with Speedmod Kernel. So I thought to install ROM Manager, but when I launched it the app didn't find the CWM recovery version previously mentioned. So I said to flash CWM Recovery and he says that he has successfully downloaded it... and then he say that my current recovery is version 2.5.1.2
Then, I ask to reboot in recovery mode but what happens is that my phone reboots in the original recovery (android system 3e), it tries to run something (i think the update.zip) and fails... so I manually go into recovery mode (3 buttons combo) and it load CWM recovery version 2.5.1.0 (the one that cames with SpeedMod)
What am I doing wrong? Why ROM Manager launches 3e recovery? Is it because the 2.5.1.0 version of CWM rec has became the "default" recovery (the one automatically launched with the 3 buttons combo)?
hi
i am on stock rooted ICS rom, with stock recovery and kernel..
I rooted this rom via some temporary cwm recovery which goes away after rebooting..
i rooted via busybox_supersu method via temporary cwm recovery.
Now how can I install new custom rom?
is a permanent cwm recovery necessary? if yes, from where can I download it? Or is it ok to flash abyss kernel via this temporary cwm?
Here's the ultimate root+cwm guide by dr. Ketan.
http://forum.xda-developers.com/showthread.php?t=1329360
Just download the one for your kernel ( the last 3 numbers must match ) and run it. You'll have permanent root+cwm installed. If your kernel is not directly rootable, download and flash any of directly rootable firmwares first:
http://forum.xda-developers.com/showthread.php?t=1424997
And then repeat the first step.
To install custom rom like CM9, all you have to do is copy the .zip to your phone, reboot into recovery, install the zip via CWM, wipe/clean cache and reboot.
Hi Folks,
i have a simple question and i hope someone can answer this:
I'm on GB 2.3.6 with XXLC1 (i did this via flashing old GB ->zergrush exploit -> GB 2.3.6 via mobile odin with keep root)
Am i right when i say that all i have to do now is putting the PA.zip in the root directory and flash it via CWM?
Or do i have to change the kernel or any other things?
Download and flash abyss kernel in CWM, then reboot into recovery (under advanced in CWM) and do a full wipe and then install PA
azzledazzle said:
Download and flash abyss kernel in CWM, then reboot into recovery (under advanced in CWM) and do a full wipe and then install PA
Click to expand...
Click to collapse
with abyss kernel you mean abyssnote 4.2 right? (http://forum.xda-developers.com/showthread.php?t=1362424&highlight=abyss)
Original or RedPill?
Thank you very much!
I dont think it matters, But ive always used the redpill version
Hi All,
I'm newly registered as I have problem in using HydraCoreNirvana Kernel.
I was using ZSLPN ICS Stock ROM with PhilZ-cwm6-ZSLPN-OZS-v2.7 Kernel.
A few days ago, I booted into CWM (Power + Up + Home) to flash MaxFu_HydraCoreNirana_n3_std.zip kernel.
HydraCore Kernel is working fine except that this kernel uses a lot of battery according to the
battery monitor. I keep using it for 3 days to make sure the whole system is stable after flashing a new kernel
but it is still consuming a lot of power.
Today, I boot into CWM (Power + Up + Home) to flash back the PhilZ-cwm6-ZSLPN-OZS-v2.7.zip kernel.
After flashing, I select reboot system, the "Galaxy Note N-7000" shows up and then black screen, i.e. without
the boot animation screen. I wait for a long time but still black screen. I tried to power up serveral times but same
thing happen. I then boot into CWM (Power + Up + Home), I can see PhilZ CWM so the PhilZ kernel should be flashed.
I then use this PhilZ CWM to flash Hydra kernel again and then reboot system. It can boot up.
I then try to boot into CWM to flash PhilZ kernel again, same problem. Now I flash back to MaxFU_HydraCoreNirana Kernel.
What's wrong with my procedures? Any idea? Now, I'm afraid to flash any other kernel as I am afraid I cannot flash
back to MaxFu Kernel and that will brick my phone.
Please help. Thank you so much.
I cannot post in Max_FU kernel thread as I am new here and not allowed to post there.
http://forum.xda-developers.com/showthread.php?t=2053084
Thanks.
It is happening because the latest Hydracore kernels have the new Mali drivers, which are incompatible with previous kernels. So, when you first flashed Hydracore, it also installed these new drivers; when you flash PhilZ kernel back, the new drivers are still there, so the kernel can't boot up. The solution is to install a "revert" package which will install and older Hydracore kernel (without the new Mali drivers), and also delete the installed drivers. Search the Hydracore thread for "Returning back to Hydra v5.3 std.zip". This is the file you should get and flash through CWM. After that, you can flash PhilZ kernel again.
To make it easy, download and flash returning back to hydra.zip 1st. After that you can flah philz kernel.. You can go to philz tread you kernel has been updated to v3.99
dbolivar said:
It is happening because the latest Hydracore kernels have the new Mali drivers, which are incompatible with previous kernels. So, when you first flashed Hydracore, it also installed these new drivers; when you flash PhilZ kernel back, the new drivers are still there, so the kernel can't boot up. The solution is to install a "revert" package which will install and older Hydracore kernel (without the new Mali drivers), and also delete the installed drivers. Search the Hydracore thread for "Returning back to Hydra v5.3 std.zip". This is the file you should get and flash through CWM. After that, you can flash PhilZ kernel again.
Click to expand...
Click to collapse
Thank you so much for the detailed description. I've not noticed that Mail drivers are being installed.
zai89 said:
To make it easy, download and flash returning back to hydra.zip 1st. After that you can flah philz kernel.. You can go to philz tread you kernel has been updated to v3.99
Click to expand...
Click to collapse
Hi zai89, thank you so much for your file. I flashed it and then I can flash back to PhilZ newest version.
By the way, I have used your file (v5.3 std kernel) for a while and it consumes the power normally. I still don't
understand why the HydraCoreNirvana drains huge power in my ROM (of course I am not complaining about
HydraCoreNirvana kernel, maybe my ROM problem). Since now I can flash back to PhilZ kernel, I may try
the v5.3 standard you suggested and see how good it is.
Once again, thank you very much for your time and kindly help.
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.