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.
Related
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.
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!
Hi,
I unlocked the bootloader, flashed CWM into it. I backed up everything through CWM recovery.
However somehow the stock rom/kernel/etc don't work with this set-up. I just have "free xperia" logo until the universe will implode.
Therefore I installed cyanogenmod and it works. But I don't have the Xperia pkgs and since I own a lot of stuff from sony..those apps are usefull.
Question 1: Can I use CWM recovery with the stock sony rom?
Question 2: I just downloaded the ftf (700MB file), how can I restore everything? If I fastboot everything inside the package will it also correct the boot problem?
Question 3: Can I install sony pkgs as a 3rd party zip like google-apps?
Thanks for the help!!
Yes, you can use stock kernel with recovery.
But, since you are unlocked, you can install DoomKernel, its based on stock , it has a recovery and root included, and it is compatible with stock roms. Install it via fastboot, then you can flash a stock ftf excluding the kernel so you don't lose custom kernel.
DrKrFfXx said:
Yes, you can use stock kernel with recovery.
Click to expand...
Click to collapse
You mean in CWM menus? and install the .ftf?
forevertheuni said:
You mean in CWM menus? and install the .ftf?
Click to expand...
Click to collapse
CWM can't flash ftf, for that you need Flashtool.
CWM can only flash flasheable zips.
If you want to keep stock rom with a working cwm recovery you have choice using advanced stock kernel or doomkernel both have a recovery working normally. If you don't want to overclock/underclock and tweak stuff choose advanced it is the stock kernel with a recovery with nothing more.
Flash ftf and then fastboot the kernel you choose, or vice versa fastboot and then flash ftf and exclude kernel in flashtool.
edit : read this http://forum.xda-developers.com/showthread.php?t=2153167
Hello there.
I have a problem with my N7000. Today I've flashed stock firmware onto my phone, everything went ok, but I have a problem now. When I'm trying to install something from recovery, I can't. I select the ROM, everything is beeing checked, etc, and when it wants to install update, a message appears: "This packgage is for 'galaxynote,n7000,N7000,GT-N7000' devices: this is a ' '." . This happens with every single rom that I am trying to install via recovery. I tried to flash stock firmware two times, two different, still same effect, tried to whipe data/cache etc, still didnt got any effect. Any solution guys?
After you flash the stock ROM, the recovery will be stock as well.. You will not be able to flash roms from here.. For that you will need to flash philz kernel.
Well actually I can install anything via recovery, so installing kernel isnt possible.
Emkarcinos said:
Well actually I can install anything via recovery, so installing kernel isnt possible.
Click to expand...
Click to collapse
You can flash Philz kernel from stock recovery..
nokiamodeln91 said:
You can flash Philz kernel from stock recovery..
Click to expand...
Click to collapse
I have exactly the same problem (and the same situation) as the OP. You cannot flash Philz kernel from stock recovery because the exact same error will pop up.
Right mate I think I got it. You will need to flash an older version of Philz kernel first, and then upgrade. Worked fine for me once I decided to install "05.05.2013 - PhilZ-cwm6 v5.00.4 with CWM 6.0.3.1 based recovery" first.
I know this is not an issue forum but I CANNOT find one for the SM-i757M so this is where I'm going to put my question. One of the mods can move it if they want.
So, I tried to install CF-Auto-Root using Odin V 3.07 on my Samsung Galaxy S II i757M phone. Odin PASSes it, but it gets stuck on the red Chainfire logo with CF-Auto-Root and various info on the bottom sitting solid. It flashes every couple seconds indicating it keeps trying to run the script but it's not working. Upon going to recovery, which isn't custom, it displays the "Firmware upgrade encountered an issue" message. At the top, it's clearly in Download Mode because it says "ODIN MODE" in red. I can even connect to Odin and re-flash CF-Auto-Root again. But it won't work. Can anyone help me either get it to work, or stop it from trying to run so I can boot my phone back into the firmware without having to wipe anything?
Thank you in advance.
Whyl are you still running stock? I think its better if you try custom ROMs and recovery as your device isnt officially supported anymore.
It's easier if you try philz touch recovery as it can root your android without flashing any zip files, if you don't like custom ROMs.
Here is the link to your device kit kat thread
http://forum.xda-developers.com/galaxy-s2/general/rom-unofficial-carbon-kitkat-bell-sgh-t2661144
diabolicalprophecy said:
Whyl are you still running stock? I think its better if you try custom ROMs and recovery as your device isnt officially supported anymore.
It's easier if you try philz touch recovery as it can root your android without flashing any zip files, if you don't like custom ROMs.
Here is the link to your device kit kat thread
http://forum.xda-developers.com/galaxy-s2/general/rom-unofficial-carbon-kitkat-bell-sgh-t2661144
Click to expand...
Click to collapse
It's just a preference. I might end up doing that though... But that's only if I absolutely CAN'T get back to the firmware already there.
superluig164 said:
It's just a preference. I might end up doing that though... But that's only if I absolutely CAN'T get back to the firmware already there.
Click to expand...
Click to collapse
Flash back stock ROM and then flash philz touch.
Custom recovery won't make any difference to your stock rom experience.
If you prefer CF root kernel, then make sure you are not flashing Ice Cream sandwich version on Jellybean ROM or vice versa.
diabolicalprophecy said:
Flash back stock ROM and then flash philz touch.
Custom recovery won't make any difference to your stock rom experience.
If you prefer CF root kernel, then make sure you are not flashing Ice Cream sandwich version on Jellybean ROM or vice versa.
Click to expand...
Click to collapse
Yes, but I don't want to lose any of the apps installed, just abort OR force CF to continue. Will installing a custom recovery force it to abort, since CF USES recovery to install? Then, can't I root from philz, and boot back to the firmware still on the phone?
superluig164 said:
Yes, but I don't want to lose any of the apps installed, just abort OR force CF to continue. Will installing a custom recovery force it to abort, since CF USES recovery to install? Then, can't I root from philz, and boot back to the firmware still on the phone?
Click to expand...
Click to collapse
You don't need CF to root after flashing a custom recovery.
Just download supersu.zip and flash from philz or Twpr recovery. (download link is in supersu thread)
Flashing recovery without factory wipe will not cause any loss of data.
Yes you can boot into stock rom with philz touch or twpr as both of them support stock firmware.