[PhilZ-cwm6][n7000] Stock Kernel+CWM6+Root+exFAT+NTFS-LTA

[sirgawain123]

Go to the supersu xda thread and flash his newest update zip in cwm
I think that may fix it. Post back.

Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta

Did as you said flashing SuperSU from recovery, and root was regained, also superuser disappeared. (I had previously tried installing SuperSU from Google play, without regaining root)
Many thanks to both Philz, for his helpful post, and you.

Enviado desde mi GT-N8010 usando Tapatalk 4 Beta

 

[skandats]

/Data partition must be corrupted. Freezes and reboots will continue until its formatted unfortunately. It's a typical problem with stock JB Roms for the Note.

Hi shoey63,

I faced the same problem what jarlaxlebaenre faced. My note kept on crashing and hanging. no response to touch. I had even tried to take the backup after this happened and did a restore. It did not help. Finally, today, I did a factory reset and installed all the apps I needed. Have taken a new back up now and everything is working fine. But I'm not aware of data partition corruption. Can you please let me know would there be any chance of this happening again? If the same happens again and if I restore the good back up I now have, will it work fine or full wiping the rom is the only solution that I have?

Thanks in advance.

 

[br54]

Hi shoey63,

I faced the same problem what jarlaxlebaenre faced. My note kept on crashing and hanging. no response to touch. I had even tried to take the backup after this happened and did a restore. It did not help. Finally, today, I did a factory reset and installed all the apps I needed. Have taken a new back up now and everything is working fine. But I'm not aware of data partition corruption. Can you please let me know would there be any chance of this happening again? If the same happens again and if I restore the good back up I now have, will it work fine or full wiping the rom is the only solution that I have?

Thanks in advance.

I was having these same problems on this kernel. but after some checking it was some mods on my ROM that was causing it.
check you ROM for "seeder" app.....delete it!!
and also check for these mods, 02evolution and 03smooth from /system/etc/init.d
If you have these delete them reboot into recovery wipe cashe and dalvik.
It totally fixed it for me!!!
If this don't fix it.. Flash chosen ROM, delete said files... Do your wipes then flash philz. I can confirm this is what fixed my freezing and crashing problems. Good luck

 

[skandats]

I was having these same problems on this kernel. but after some checking it was some mods on my ROM that was causing it.
check you ROM for "seeder" app.....delete it!!
and also check for these mods, 02evolution and 03smooth from /system/etc/init.d
If you have these delete them reboot into recovery wipe cashe and dalvik.
It totally fixed it for me!!!
If this don't fix it.. Flash chosen ROM, delete said files... Do your wipes then flash philz. I can confirm this is what fixed my freezing and crashing problems. Good luck

Thanks for the info. However, I have not installed seeder app and I do not have file named init.d in my system/etc folder. After factory reset, I was still facing issues with screen becoming non responsive. I flashed 5.03.0 (I have DDLSC stock ROM) and now it seems to be working fine. Not sure if there is any issue with 5.06.1 with some apps.

 

[kona786]

thanks Phil for this thread - My wifes Note is now rooted + custom recovery

 

[screamwork]

So no xwlsd support??

 

[AndroidSlave]

So no xwlsd support??

Either (A) SEARCH the thread; or (B) update to a CURRENT ROM if you are too lazy to type in the word "LSD" into the search box, as required per XDA rule #1.
People are here to help you, but no one will help someone who can't type 3 letters in the search box and then hit enter.

 

[mpierce]

Which Kernel?

There is no kernel info for the latest CM kernel when installed on my Samsung Galaxy Note N7000.

If I simply flash a PhilZ and then install the CM rom, I lose PhilZ and everything wonderful that I want.
If I then use ODIN and install PhilZ, I get the yellow triangle and the phone will not boot.
If I flash a PhilZ, I get the yellow triangle and the phone will not boot.

I am wondering what kernel do I select, I've tried everything in the XXLT4 and XXLT6 without success.

I need a PhilZ as I use a 64Gb exFAT SD card.

I've had to revert back to the Ultimate ROM using PhilZ XXLT6.

Does anyone have a recommendation as I would like to use a CM based rom using the latest CM kernel.
Thanks in advance.

 

[AndroidSlave]

There is no kernel info for the latest CM kernel when installed on my Samsung Galaxy Note N7000.

If I simply flash a PhilZ and then install the CM rom, I lose PhilZ and everything wonderful that I want.
If I then use ODIN and install PhilZ, I get the yellow triangle and the phone will not boot.
If I flash a PhilZ, I get the yellow triangle and the phone will not boot.

I am wondering what kernel do I select, I've tried everything in the XXLT4 and XXLT6 without success.

I need a PhilZ as I use a 64Gb exFAT SD card.

I've had to revert back to the Ultimate ROM using PhilZ XXLT6.

Does anyone have a recommendation as I would like to use a CM based rom using the latest CM kernel.
Thanks in advance.

Did you bother the read the first posts?
Read them. This will not boot CM
And you will have to use fat32. Try NX kernel.

Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta

 

[mpierce]

Did you bother the read the first posts?
Read them. This will not boot CM
And you will have to use fat32. Try NX kernel.

Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta

You are correct and I apologize as I see that the PhilZ kernel does not work on CM.
Should have gone back 4/5 pages and read the thread which I was doing after my post.

PhilZ is supporting exFAT using Ultimate ROM but I'm probably using the wrong PhilZ.

Android version: 4.1.2
Baseband: N7000XXLT3
Kernel: 3.031-1103517 [email protected] #3 SMP PREEMPT
Build: Ultimate N7000 XXLT4 JB4.1.2v6
ROM: Ultimate XXLT4

 

[Phil3759]

You are correct and I apologize as I see that the PhilZ kernel does not work on CM.
Should have gone back 4/5 pages and read the thread which I was doing after my post.

PhilZ is supporting exFAT using Ultimate ROM but I'm probably using the wrong PhilZ.

Android version: 4.1.2
Baseband: N7000XXLT3
Kernel: 3.031-1103517 [email protected] #3 SMP PREEMPT
Build: Ultimate N7000 XXLT4 JB4.1.2v6
ROM: Ultimate XXLT4

Some kernel devs added it to support cm zImage
However, my self, i only repack stock kernels

Sent from my GT-I9100 using Tapatalk 2

 

[ValenteL]

Hi Phil3759

Can You build for ROMs based XXLT9 ORA whit CWM6? Attached the Stock kernel XXLT9.
3.0.31-1103517 [email protected]#3 04 Jun 2013

Thanks
(For now, installed LT6 kernel)
Valente

 

[AndroidSlave]

What an awesome poster. Actually included the image.

Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta

 

[Phil3759]

Released v5.08.5
DDLSC - DXLSE - JPLSB - XXLT9 - ZCLSF - ZSLO2

**NEW**
Cyanogenmod/AOKP release (cm-10.1)
The cyanogenmod/aokp compatible version is not repacked to offer multi-bootanim and dual usb mount. However, it offers all PhilZ Touch recovery features


Change list 5.06.1 ---> 5.08.5

5.08.5 (11.07.2013)
- Compile Aroma File Manager (by amarullz) zip installer under recovery:
* either compile whole recovery, zip will be created at first pass
* or only compile aroma zip installer in two pass:
1- mmm bootable/recovery/aromafm
2- mmm bootable/recovery/aromafm/tools
* output: [target_out]/aromafm_out/aromafm_[DeviceID].zip
- detect aroma compatibility with non NEON devices during compiling
- use less conflicting flags: TARGET_NAME --> TARGET_COMMON_NAME

5.08.0 (07.07.2013)
- improve nandroid progress bar update
- fix recovery was not prompting when backup estimated size is larger than free space
- add ors backup support for twrp format requested by BillGoss
- ors backup: when no backup name is given, generate it using same way as nandroid operations (time stamp + rom name tag)
- support separated compiling for Loki patched devices (S4 AT&T and Verizon)
- i9505: revert some changes to fix time bug for some users
- Galaxy S4 US variants: repack around Audism stock JB 4.3 kernel v3 + Samsung exfat modules + revert use of mkefs for partition corruption issue
- fix missing break in set backup compression value menu (misc_nandroid_menu())
- misc clean up code
- sync latest sources

5.07.6 (05.07.2013)
- update version 6.0.3.3
- add exfat-fuse 1.0.1.362 / 2.9.2 optional support by enabling USE_EXFAT_FUSE_BIN CFLAG in BoardConfig (exfat support on cyanogenmod repacks)
- i9505: use Audism kernel v3 (Stock Samsung sources) to fix partition corruption without additional code and for better exfat support

5.07.1 (01.07.2013)
- i9100G support

5.07.0 (30.06.2013)
- fix "unknown volume for path /res/images/koush.png" on boot (do not search for a volume on ramdisk path)

5.06.8 (19.06.2013)
- fix bug introduced in v5.06.5: folder entries duplicated in some choose file menus (custom and twrp restore modes, regenerate md5 selection menu)
- by default, if /data/media/0 exists, it will be used as internal storage. You can still alter it in Advanced menu to force /data/media

5.06.7 (17.06.2013)
- Galaxy R/Z (i9103) support, thanks to Adam77Root

5.06.6 (13.06.2013)
- fix multi-zip flash "select/unselect all" persisting (static int select_all --> int select_all)
- add sdparted option to partition in ext4 fstype
- enable partition sdcard when non vfat fstype2 option is used in recovery.fstab
- merge cm-10.1 changes (6.0.3.2 Update 8):
* Merge "recovery: Fix adb backup" into cm-10.1
* Merge "Remove (un)mount option for datamedia partitions" into cm-10.1
* recovery.c: Fix the potential segmentation fault: Extral newline can trigger recovery segmentation fault
- Nexus 10 (manta): revert font changes since they were now merged in cm-10.1 device tree
- i9505 international: migrate to jfltexx device tree and repack with newer exfat modules
- Galaxy S4: support US variants
- misc code cleaning

5.06.4 (06.06.2013)
- fix touch repeat on capacitive virtual buttons for some devices
- Pico: ramdisk changes to enable backup size detection for mtd partitions (boot, recovery, misc)

5.06.3 (05.06.2013)
- HTC One Sprint and TMO variants support
- Galaxy S3 - T-Mobile (d2tmo): ramdisk changes to fix exfat (load modules using recovery-loader script)

5.06.2 (04.06.2013)
- Galaxy S3 - T-Mobile (d2tmo) - SGH-T999 support

Upload in progress, be patient

New permanent link with latest versions:
<< Latest versions always here: >>
http://d-h.st/users/philz_touch/?fld_id=16061#files


Enjoy

 

[nokiamodeln91]

Wow

Sent from my GT-I9500 using xda premium

 

[AndroidSlave]

Released v5.08.5
DDLSC - DXLSE - JPLSB - XXLT9 - ZCLSF - ZSLO2

**NEW**
Cyanogenmod/AOKP release (cm-10.1)
The cyanogenmod/aokp compatible version is not repacked to offer multi-bootanim and dual usb mount. However, it offers all PhilZ Touch recovery features

Phil, I would like to prepack this in my ROMs.
Is that OK with you?
Is it possible for me to just change something in my manifest or cherry pick the recovery so it can just add philz touch during compile so I don't have to manually add the kernel? What would I add/do?

Sent from my GT-N7000 using Tapatalk 2

 

[Phil3759]

Phil, I would like to prepack this in my ROMs.
Is that OK with you?
Is it possible for me to just change something in my manifest or cherry pick the recovery so it can just add philz touch during compile so I don't have to manually add the kernel? What would I add/do?

Sent from my GT-N7000 using Tapatalk 2

You are welcome to unpack and use it at your wish for your ROMs/kernels
Just give credit and post a link to this thread

Best regards

 

[AndroidSlave]

You are welcome to unpack and use it at your wish for your ROMs/kernels
Just give credit and post a link to this thread

Best regards

OK so there is no git for the recovery with 4412 fork so I can compile instead of having to manually repack?

Sent from my GT-N7000 using Tapatalk 2

 

[Phil3759]

OK so there is no git for the recovery with 4412 fork so I can compile instead of having to manually repack?

Sent from my GT-N7000 using Tapatalk 2

My git is only the open source version, no touch
Please read main thread for dev details and why it is so

You do not need to compile it. I did it for you. So, just unpack it (do not forget xz padded files!), extract the recovery binaries and repack them with your kernel
Once kernel build is completed, replace these:
/etc
/sbin/[add extra files]
/res/[add extra files]

Then repack using cm commands. Easier than using xiaolu script if you compile whole kernel source

 

[AndroidSlave]

My git is only the open source version, no touch
Please read main thread for dev details and why it is so

You do not need to compile it. I did it for you. So, just unpack it (do not forget xz padded files!), extract the recovery binaries and repack them with your kernel
Once kernel build is completed, replace these:
/etc
/sbin/[add extra files]
/res/[add extra files]

Then repack using cm commands. Easier than using xiaolu script if you compile whole kernel source

Thanks buddy. Just thought I could put it in my night lies without having to manually do it
But I'll just make a shell script to do it on the nightlies. A bash script to do:
Unzip rom
Rm originals
Cp philz files
Rezip

Would that work?

Sent from my GT-N7000 using Tapatalk 2