I have an untouched Note running stock ICS 4.03 -- Kernel 3.0.15-N7000XXLPY ...). I'd like to be able to safely flash a custom ROM, avoiding the brick bug. I've been digging through a lot of threads, but some uncertainties remain.
Here's what I'm about to do: I'll get the Philz kernel matching my current rom (this would be PhilZ-cwm6-XXLPY-XEN-v3.99, right?), boot into stock recovery, flash the .zip from the sd card, and boom, I'll have a safe kernel with root and CWM to flash any ROM from. Is this about the right plan?
2 more specific questions:
1. The matching Philz kernel was posted under the headline "Update to all ICS 4.0.4 kernels from 3.71 ---> 3.99" in the Philz kernel thread. But I'm running 4.03. So is this the right kernel for me?
2. Will the ROM I install after that have to match the Philz kernel in some way? I'm thinking of getting the Official CM 10.1 from the nightlies thread.
Thanks so much!!
That's the right plan
1. The correct rom is found under rom build which is the last in the section where you found the kernel version. The 4.0.4 also works with 4.0.3 so it's ok.
2. No the new rom will install a new kernel. Philz won't work with cm as philz is Samsung kernels repacked for safety and recovery..
Thanks, man.
Just to clarify: once I'm done flashing CM 10.1 from the philz kernel, I will no longer be running the philz kernel, but the CM kernel? Is there a reason why I can't go directly to flashing CM 10.1 from the stock rom and recovery, skipping the Philz kernel part (if I refrain from wiping in the stock recovery, when the faulty stock ICS is still on there)?
loxdp said:
Thanks, man.
Just to clarify: once I'm done flashing CM 10.1 from the philz kernel, I will no longer be running the philz kernel, but the CM kernel? Is there a reason why I can't go directly to flashing CM 10.1 from the stock rom and recovery, skipping the Philz kernel part (if I refrain from wiping in the stock recovery, when the faulty stock ICS is still on there)?
Click to expand...
Click to collapse
Correct me if I'm wrong but I don't think you can flash CM 10.1 from stock recovery.
Philz kernel comes with CWM recovery which provides more functionality than the stock recovery.
For example you can do a nandroid backup (basically a snapshot of your current phone system) so if you ever flash a rom that you don't like or something screws up, you can just restore your backup.
I think your first priority should just be flashing a safe kernel (Philz) and only then should you be looking into flashing custom roms.
loxdp said:
Thanks, man.
Just to clarify: once I'm done flashing CM 10.1 from the philz kernel, I will no longer be running the philz kernel, but the CM kernel? Is there a reason why I can't go directly to flashing CM 10.1 from the stock rom and recovery, skipping the Philz kernel part (if I refrain from wiping in the stock recovery, when the faulty stock ICS is still on there)?
Click to expand...
Click to collapse
Custom rom can only be installed using Cwm
OK, thanks for your help guys. I just flashed the Philz kernel following to the instructions and all is well. CWM is working, and I appear to have root access in my old stock ROM.
But in the phone info, the kernel version is unchanged. It stil says: "3.0.15-N7000xxlpy-cl474507 [email protected] # 3 SMP PREEMT Fri May 4 04" -- which is the exac same thing it said before I flashed the kernel.
How can I verify if I'm actually running the safe Philz kernel now?
PhilZ Kernel are only modded kernel, so they aren't change and stock kernels. And so you won't see a description made by PhilZ but only the normal information of the original kernel.
To be sure: boot into recovery and check the CWM version and compare it with the infos in PhilZ thread.
But you told already that you do not have the stock recovery, so everything is ok.
Thanks ThaiDai. The fact that I had moved successfully from stock recovery to CWM was already a strong hint that things worked out.
I wanted to make extra sure, so before flashing the first custom ROM I went into CWM, made a backup of the stock samsung, and then took this script right here to examine the operating kernel (boot.img in the backup folder) for the brick bug: http://forum.xda-developers.com/showthread.php?t=1807995 -- the script returned that the kernel was safe.
So I went on to flash CM 10.1 and I'm a happy camper now! This forum is a great place for getting help, you guys are terrific!
Related
I apologize if this has been asked several times before but I want to be 100% sure I'm doing the right thing since my Note currently has brickbug. When I first got ICS via a Kies update, I had to do a stock wipe from Settings because apps were crashing and freezing. As far I can tell there hasn't been any permanent damage. I've since done another OTA update via WiFi.
I want to go from Stock ICS 4.0.4 to ParanoidAndroid JellyBean
Region - Open Germany
Baseband version - N7000XXLRK
Kernel version - 3.0.15-N7000XXLRK-CL811902
Can I simply download the PhilZ-cwm6-XXLRK-XEU-2.7 kernel http://www.mediafire.com/file/269h649de0bch14/PhilZ-cwm6-XXLRK-XEU-2.7-signed.zip onto my microsd card and flash from stock recovery?
Then can I use CWM to flash latest build of JB ParanoidAndroid from http://goo.im/devs/Utacka/n7000?
Also will this cause the Yellow Triangle?
what i did was flash hydracore kernel with mobile odin then flash paranoid android as described in its own thread.
also make a full wipe AFTER flashing hydracore from CWM
kromosto said:
what i did was flash hydracore kernel with mobile odin then flash paranoid android as described in its own thread.
also make a full wipe AFTER flashing hydracore from CWM
Click to expand...
Click to collapse
Flashing the PhilZ kernel via Stock Recovery wouldn't work? That seems to be the most simple method. Does HydraCore have advantages over PhilZ?
it should work too. i just write the method i used and of course it is not the only method to do it.
kromosto said:
it should work too. i just write the method i used and of course it is not the only method to do it.
Click to expand...
Click to collapse
Great, thanks.
dr.ketan said:
yes you can root directly from stock recovery with Phillz kernel (Method 1A) OR with simlpe SuperSU file (method 1B)
read this
http://forum.xda-developers.com/showthread.php?t=1329360
Click to expand...
Click to collapse
I found another recent thread. This was also helpful, thank you!
kromosto said:
it should work too. i just write the method i used and of course it is not the only method to do it.
Click to expand...
Click to collapse
Ok, I have PhilZ on my Note now. But still have stock ICS. The ParanoidAndroid threads say "Make sure to run CM9 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK!"
So does that mean I can't just flash HydraCore and then flash ParanoidAndroid? Do I have to flash a CM9 ROM or other AOSP ROM before ParanoidAndroid? Also is PhilZ kernel compatible with ParanoidAndroid?
orificium said:
Ok, I have PhilZ on my Note now. But still have stock ICS. The ParanoidAndroid threads say "Make sure to run CM9 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK!"
So does that mean I can't just flash HydraCore and then flash ParanoidAndroid? Do I have to flash a CM9 ROM or other AOSP ROM before ParanoidAndroid? Also is PhilZ kernel compatible with ParanoidAndroid?
Click to expand...
Click to collapse
I did exactly the same recently (but I went from stock to another ROM which had the same message, not ParanoidAndroid) - ran philz then the kernel should be safe which means you should be safe to flash to another ROM. That brick message on the thread I assume only applies if you are running a stock ROM with the stock kernel. If you want to be sure check in Settings>About Phone>Kernel Version - see thread here http://forum.xda-developers.com/showthread.php?t=1857556.
orificium said:
I apologize if this has been asked several times before but I want to be 100% sure I'm doing the right thing since my Note currently has brickbug. When I first got ICS via a Kies update, I had to do a stock wipe from Settings because apps were crashing and freezing. As far I can tell there hasn't been any permanent damage. I've since done another OTA update via WiFi.
I want to go from Stock ICS 4.0.4 to ParanoidAndroid JellyBean
Region - Open Germany
Baseband version - N7000XXLRK
Kernel version - 3.0.15-N7000XXLRK-CL811902
Can I simply download the PhilZ-cwm6-XXLRK-XEU-2.7 kernel http://www.mediafire.com/file/269h649de0bch14/PhilZ-cwm6-XXLRK-XEU-2.7-signed.zip onto my microsd card and flash from stock recovery?
Then can I use CWM to flash latest build of JB ParanoidAndroid from http://goo.im/devs/Utacka/n7000?
Also will this cause the Yellow Triangle?
Click to expand...
Click to collapse
My advice is dont use Philz kernel for flashing ICS to JB... becz i read somewhere no unique Philz kernel to supports for ICS and JB
I had done many time ICS to JB (like Kingdroid RAM to Paranoid JB, Paranoid JB to STOCK ICS etc. ) no issues...... because of I used Hydracore 4.3b kernel..
thanks
koosh34 said:
I did exactly the same recently (but I went from stock to another ROM which had the same message, not ParanoidAndroid) - ran philz then the kernel should be safe which means you should be safe to flash to another ROM. That brick message on the thread I assume only applies if you are running a stock ROM with the stock kernel. If you want to be sure check in Settings>About Phone>Kernel Version - see thread here http://forum.xda-developers.com/showthread.php?t=1857556.
Click to expand...
Click to collapse
The Kernel version looks the same to me as it did before I went to PhilZ. I rebooted into recover to make sure CWM is on there, which it is. And I installed a custom boot animation to make sure that worked, and it did.
Sounds like I should go to HydraCore Kernel first since it's compatible with TW ICS and JB then flash ParanoidAndroid ROM.
m_rajaganesh said:
My advice is dont use Philz kernel for flashing ICS to JB... becz i read somewhere no unique Philz kernel to supports for ICS and JB
I had done many time ICS to JB (like Kingdroid RAM to Paranoid JB, Paranoid JB to STOCK ICS etc. ) no issues...... because of I used Hydracore 4.3b kernel..
thanks
Click to expand...
Click to collapse
Thanks, sounds like my best course of action is to flash HydraCore now and that way I can test various ICS/JB ROMs.
Since my original post I have:
Flashed PhilZ-cwm6-XXLRK-XEU-2.7-signed kernel in stock recovery to get original root and safe kernel.
Flashed GL_HYDRACORE_v5-4_STD kernel because I thought that's what I needed for PA.
Flashed pa_n7000-2.51-24OCT2012-192916 and followed instructions from Hydracore thread which said to flash kernel after done flashing new ROM and gapps. However - PA would not boot after that. I also tried pa_n7000-2.52-29OKT2012-101254-Utacka this way. Same problem.
So I decided to flash pa_n7000-2.51-24OCT2012-192916 this time but without changing the kernel. Booted fine this time and my phone flys now! Way faster than Stock ICS 4.0.4. It's nuts that official ROMs, by comparison, are so slow.
So I'm trying to understand how to know which kernels will work with which ROMs. So I've been reading the various stickies and this thread in particular - very carefully. And I see the part about "WARNING: Do NOT use the below listed kernels for any CM10 build dated October 3rd or newer because your system will not boot.". I assume this why I was having issues after flashing Hydracore immediately after PA? And if I'm understanding this right, I could use the new HydraCore v7 with this PA JB ROM I'm on now? Is that because of this new MALI driver?
I did an EFS Backup after I did the original PhilZ kernel install but I never did a Nandroid backup while I had stock ICS. Should I just do that on any functional ROM now to make sure I have a full working copy of something to get my phone restored if something goes haywire? Is that the idea?
Also a lot of people seem to recommend flashing ROMs using PC ODIN. Is this considered safer or less risky than using CWM?
ParanoidAndroid JB imilka build has been great - but I noticed a few annoying issues:
1. WiFi signal seemed a lot better in Stock ICS than it does with PA. My signal is always "Poor" in my bedroom and I'm not very far from the wireless router but when I'm in the living room - it's excellent. Is this to be expected or is there something I can do about that?
2. Audio issues - sometimes I have to play with the volume to get speaker phone working after hitting the on-screen toggle.
3. None of the Voice Input stuff works. It just says "Initializing" and then "I didn't catch that". Also described near the end of the PA thread but haven't seen anyone reply with a fix.
4. No timer/stopwatch built into clock app. Can someone recommend a good app?
5. When I change the Slider shortcuts under Settings->Interface->Lock screen, they don't save. It always go back to default - Camera, Google Search and Unlock options only.
6. Looking for a nicer clock widget. Can someone make a recommendation?
Just wanted to point out that I love that it automatically had the StraightTalk APN configured for me. I know you're probably thinking - yeah so? - but I'm relatively new to android ROMing - just been lurking for awhile - so it was a pleasant surprised.
Any help would be greatly appreciated.
Hi guys,
I am new to this forum and to flashing custom roms in particular. I have read a lot of stuff about the eMMC chipbug and how to avoid it. I want to install pa_n7000-2.53-05NOV2012-125144-Utacka from stock ICS 4.0.4 with this kernel: speedmod-kernel-n7000-ics-k3-15-Odin. Is it safe to flash the PA with the CWM of the speedmod kernel or should I go back to gingerbread as I have read on some other fora?
Thanks in advance!
yes its safe. speedmod is a safe kernel
nokiamodeln91 said:
yes its safe. speedmod is a safe kernel
Click to expand...
Click to collapse
So all I have to do is reboot in cwm recovery, and install PA from sd card, then install Gapps, then wipe/factory reset, wipe cache and wipe Dalvik cache and it should work 'without' risk?
yeah.. first wipe data /factory reset
wipe cache
wipe dalvik
format /system
then install zip from sd
nokiamodeln91 said:
yeah.. first wipe data /factory reset
wipe cache
wipe dalvik
format /system
then install zip from sd
Click to expand...
Click to collapse
And then it should be good to go or should I wipe again?
not until you face any app issues or so
want to be safe before flashing PA
hi guys
i m using rocket rom. now i want to flash PA 2.99
i m concerned about this warning...Make sure to run CM9/10 or an AOSP-based ROM : FLASHING FROM STOCK ICS OR ROMS BASED ON STOCK ICS WILL RESULT IN A BRICK! - You're warned!
what should i do..?
RR version ? It has a safe kernel so you are good to go. You can ignore that warning
nokiamodeln91 said:
RR version ? It has a safe kernel so you are good to go. You can ignore that warning
Click to expand...
Click to collapse
YES it has one of philz safe kernels..
so what i think is its totally safe to flash a new rom if u have a safe kernel. Am i right???
what if i flash a kernel(safe one) which is not compatible with my currrent rom....is it risky or my device will just not boot or anything else.....??
Hi guys I'm new to the N7000 forums, but I am no means new to the android and flashing scene. I'm just a bit confused as to how to safely install ROM's on the note.
I've attached a screenshot of my "about phone" so you guys can tell me what kernel I should flash before installing different ROMs
The ROM(s) I'm interested in flashing are Jellybam, Sweet ROM (JB version) and Ultimate jellybean. Can these roms work with any safe kernel? i.e. once iv'e flashed philz or franco kernel I can let the flashing begin.
Also do I need to flash a safe kernel in order to install cyanogenmod or other, not based on stock roms?
Forgot to mention that I am rooted. Any help at all would be appreciated, if I am wrong about anything so far, feel free to set me straight.
Thanks to all who responded, if anyone else wants to reply feel free but i'm going to mark this as resolved so their won't be any confusion.
amd-dude said:
Hi guys I'm new to the N7000 forums, but I am no means new to the android and flashing scene. I'm just a bit confused as to how to safely install ROM's on the note.
I've attached a screenshot of my "about phone" so you guys can tell me what kernel I should flash before installing different ROMs
The ROM(s) I'm interested in flashing are Jellybam, Sweet ROM (JB version) and Ultimate jellybean. Can these roms work with any safe kernel? i.e. once iv'e flashed philz or franco kernel I can let the flashing begin.
Also do I need to flash a safe kernel in order to install cyanogenmod or other, not based on stock roms?
Forgot to mention that I am rooted. Any help at all would be appreciated, if I am wrong about anything so far, feel free to set me straight.
Click to expand...
Click to collapse
if you are on stock kernel then download Philz kernel for LP7, flash that in recovery, should give you root again aswell. then you can flash away to any of the ROMs you listed above. just every time you flash a ROM or think of factory reset or data wiping make SURE you're on a SAFE kernel. that's all
as you are rooted, just install any safe kernel like hydracore or philz. thats all. then you can try out any rom. Just make sure you follow the instruction to flash the rom in the OP
I saw that the Philz kernel has a lot of different versions, which one do I choose, am I right in saying the UBLPC one, as that is my build number? Or any one can work, I also read that you should not flash with the temp CWM, I will admit though I used the temp CWM to flash the root files and i'm still ok but I don't want to take any chances, how do I flash with the stock recovery?
amd-dude said:
I saw that the Philz kernel has a lot of different versions, which one do I choose, am I right in saying the UBLPC one, as that is my build number? Or any one can work, I also read that you should not flash with the temp CWM, I will admit though I used the temp CWM to flash the root files and i'm still ok but I don't want to take any chances, how do I flash with the stock recovery?
Click to expand...
Click to collapse
this is the one you use - PhilZ-cwm6-UBLPC-UUB-2.7
http://www.mediafire.com/file/35d4kd...2.7-signed.zip
the zip file mentioned above can be flashed using stock recovery. Put the file on ext SD card > boot into recovery > apply update from external storage > thats it
nokiamodeln91 said:
the zip file mentioned above can be flashed using stock recovery. Put the file on ext SD card > boot into recovery > apply update from external storage > thats it
Click to expand...
Click to collapse
First, forget about the franco kernel. The franco kernel for the Note is outdated and thus useless. Second, if you plan to flash a JB leak the only kernel you should use is PhilZ. And especially important with the JB leaks is to stick exactly to the instructions how to flash. Otherwise your phone won't even boot.
Have fun with your device! The Note is still an outstanding phone.
Sent from my revived Galaxy Note
Thanks guys for the quick replies, i'm gonna flash the philz kernel now and give the leaked version of JB a try.
make nandroid backup 1st..
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.
Hi
I can't seem to flash anything from philz kernel on any jb rom. So when I flash a rom I flash franco kernel 6 and then the rom and it works fine, but I want to flash Darboc's transparent mods on ultimate jb rom, but it just freezes (like it does when installing a rom) and when I try to reboot It gets stuck on the boot screen or I just can't get out of recovery. I then need to flash franco kernel 6 and flash the rom again. I'm also unable to wipe system in philz recovery. I have also tried to flash the new version of philz kernel, but it freezed when flashing the kernel. Then I ran a kernel cleaning script and flashed the rom again but it still does the same.
Any suggestions will be appreciated.
get back to ultimate rom the latest version. if it doesnot have Philz 3.99 version of the kernel, then instead of installing the new version using recovery. try using mobile odin to flash the tar version of the kernel. then try flashing what ever you want. hopefully this time it will work
Iconia500 said:
Hi
I can't seem to flash anything from philz kernel on any jb rom. So when I flash a rom I flash franco kernel 6 and then the rom and it works fine, but I want to flash Darboc's transparent mods on ultimate jb rom, but it just freezes (like it does when installing a rom) and when I try to reboot It gets stuck on the boot screen or I just can't get out of recovery. I then need to flash franco kernel 6 and flash the rom again. I'm also unable to wipe system in philz recovery. I have also tried to flash the new version of philz kernel, but it freezed when flashing the kernel. Then I ran a kernel cleaning script and flashed the rom again but it still does the same.
Any suggestions will be appreciated.
Click to expand...
Click to collapse
When u flash kerenel u have to reboot into recovery so that flashing could take effect.
PhilZ JB kernel's are safe to wipe and philZ kernel's are best for TW based ROM's.
So if u running CM10,CM10.1,AOSP,AOKP,PA ROM's u shuold look for Hydra,Franco,etc..
And make sure that u reboot into recovery when u flash kerenel...
nokiamodeln91 said:
get back to ultimate rom the latest version. if it doesnot have Philz 3.99 version of the kernel, then instead of installing the new version using recovery. try using mobile odin to flash the tar version of the kernel. then try flashing what ever you want. hopefully this time it will work
Click to expand...
Click to collapse
Hi thanks for the reply, I managed to flash the kernel with mobile odin, but I'm still unable to flash in cwm.
Are you able to format system with other kernel?
nokiamodeln91 said:
Are you able to format system with other kernel?
Click to expand...
Click to collapse
Yes and I always do before flashing a rom.
Not sure then why this is happening. I tried the same and I am able to format or flash mods using philz
nokiamodeln91 said:
Not sure then why this is happening. I tried the same and I am able to format or flash mods using philz
Click to expand...
Click to collapse
Thanks for your help anyway, at least I'm on the latest philz kernel now.
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.