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

http://forum.xda-developers.com/showpost.php?p=34537819&postcount=1182


  • Total voters
    265
  • Poll closed .
Z

zylor

Guest

rraaka

Senior Member
Sep 8, 2010
2,608
671
0
Would be fantastic if anyone could port siyah from s2 to note 1 :D

Well just an idea... But.. Most likely a dream ;)

Sent from my GT-N7000 using Tapatalk 2
"Everything great that has ever happened to humanity has started as a single thought in someones mind" - Greek composer Yanni. Refer also his composition- One Mans Dream :)

I just wanted to take a moment to reflect on the poll above- if 88 of those who voted for not patching the JB kernel had tried the unpatched kernel released for LSA and reported back here it would have helped in the development of this community.

But many are unwilling to report back honestly about their experiences because the other 179 might bully them into silence - look how this guys honest sharings are treated -

http://forum.xda-developers.com/showpost.php?p=35215686&postcount=483

we'll never know if the JB kernel is safe or not.
 
A

AndroidSlave

Guest
Don't get me started shoey. How many people have had to spend hundreds of dollars to fix their devices because of blind trust in Samsung. He should be ripped.
Until entropy says it works, I don't believe it.
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,557
33,049
0
For now, the patching doesn't have major side effects except the no way to format sdcard in phone, but you can do from recovery or PC. All other functions do work, include a reset factory settings from phone.

For now, JB is still leak, so I will continue to patch kernels
Once it is official, the feedback will be huger. If no brick reports, I could decide to make 2 versions, patched and unpatched. If it is proved to be safe, I will stop patching kernel

For now, I also think it is too early. I won't like to have people coming to say my kernel bricked their phone. Many noobs come and flash without any second thought...

Look at this post in the i9100 thread:
http://forum.xda-developers.com/showthread.php?p=35473648#post35473648

Well, I am happy people can answer his yes without a second thought or doubt
 
Last edited:

Phil3759

Inactive Recognized Developer
May 30, 2012
9,557
33,049
0
@Phil3759. Have you seen this thread? http://forum.xda-developers.com/showthread.php?p=35549838

Sent from my GT-N7000 using xda app-developers app
Yes reminds me of the gb ZR exploit but through adb. This one is so severe that it will be soon fixed by Samsung. I am not sure I'd bother fixing it at ramdisk level for now, maybe if new kernels still affected. For now, CF app should do the trick

Sent from my GT-I9100 using Tapatalk 2
 
  • Like
Reactions: rraaka and shoey63

angelomaldito

Senior Member
May 26, 2011
299
70
0
Yes reminds me of the gb ZR exploit but through adb. This one is so severe that it will be soon fixed by Samsung. I am not sure I'd bother fixing it at ramdisk level for now, maybe if new kernels still affected. For now, CF app should do the trick

Sent from my GT-I9100 using Tapatalk 2
The problem is that unfortunately CF's apk breaks camera :( in my case, even unchecking the boxes doesn't solve the camera issue, unless I do a reboot, but then I'll be exposed :(

Sent from my GT-I9100 using xda app-developers app

[EDIT]: Actually, after making a few more tests, I've realised that even if I reboot the device with the two boxes ticked (i.e Disable exploit/ Disable exploit on boot), hence protected from malwares on boot, and then untick the first box (Disable exploit) before opening the Camera apk and then ticking "Disable exploit" box again, camera will work fine until the next reboot, when it will be necessary to repeat the process (untick "Disable exploit" > open Camera apk, tick "Disable exploit" again > done

Conclusion: it is possible to safely use (patched with CF's ExynosAbuse.apk) the i9100 XXLSJ (Jelly Bean leak) with working camera. ;)
 
Last edited:

Phil3759

Inactive Recognized Developer
May 30, 2012
9,557
33,049
0
The problem is that unfortunately CF's apk breaks camera :( in my case, even unchecking the boxes doesn't solve the camera issue, unless I do a reboot, but then I'll be exposed :(

Sent from my GT-I9100 using xda app-developers app
But fixing in ramdisk will do the same exactly unless patched from kernel source which I do not do and not on my plans now
I would only add what the apk does on system boot, so you'll experience same issues
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,557
33,049
0
PhilZ Touch v3.81 Recovery (CWM 6.0.2.3 based)
  • merge last cwm 6.0.2.3 updates from jellybean cm10 branch
    * remove wipe battery stats
    * better implementation for setting default backup format
    * fix crash in recovery that occurs during backup (popen.c)
    * dedupe: fix buffer overflow​
  • i9300: fix vibrator not working
  • n7100: fix exfat support
  • n7100: fix aroma file manager failure
  • n7100/i9300: fix ramdisk/kernel used: now based on stock kernel/recovery: fixes potential exfat and aroma issues
  • enable mount external sd over usb in recovery for /data/media devices
  • complete re-write of Special Backup and Restore menu and functions: more efficient code to easily add new backup/restore jobs
  • complete rewrite of toggle gui menu code: 4Kb size gain on recovery binary + more efficient code performance wise
  • new Misc Nandroid Settings: toggle md5 checksum, toggle /preload processing, set time zone
  • no fail of nandroid job on /preload error (auto skip on error)
  • set time zone for nandroid backup path moved to new Nandroid Misc Menu
  • add credits to special backup and restore sh scripts
  • fix mount /system error log on recovery start
  • key repeat toggle now applied live, no more need to restart recovery to take effect

New visible parts:

Special Backup and Restore



Misc Nandroid Settings



Downnload:
UBLS4-TCE (JB Leak)
http://www.mediafire.com/file/tmukpmf8bx2tgtq/PhilZ-cwm6-UBLS4-TCE-3.81-signed.zip
http://www.mediafire.com/file/9ikmm3x76gayuej/PhilZ-cwm6-UBLS4-TCE-3.81.tar.md5


Since JB official seems to be delayed because of the new bug, I will update in the next days last ICS 4.0.4 kernels
 

ayong chia

Senior Member
Jan 8, 2011
477
42
0
Batam
Hi PhilZ,

May I delete the blobs's folder in cmw folder? Is it safe? I found the blobs contains too many files and folders, it take very long time to process to open the folder, so maybe delete them to lighten the folder, thank you.

Sent from my GT-N7000 using xda premium
 

sofes

Senior Member
Jun 28, 2012
80
8
0
Hi Philz

I have flashed BULR1-SWC (3.75) version to my DXLR5.

It worked, but it seems that I am always stucked at 2G, hardly can get to 3G or H or H+. I have flash back to DXLR5 (2.7) for now.

Which version should I flash to avoid the signal problem that I encounter?

Thanks.
 

ayong chia

Senior Member
Jan 8, 2011
477
42
0
Batam
Hi Philz

I have flashed BULR1-SWC (3.75) version to my DXLR5.

It worked, but it seems that I am always stucked at 2G, hardly can get to 3G or H or H+. I have flash back to DXLR5 (2.7) for now.

Which version should I flash to avoid the signal problem that I encounter?

Thanks.
Maybe set your network mode to UMTS only,I hate to use dual mode :)

Sent from my GT-N7000 using xda premium
 

Phil3759

Inactive Recognized Developer
May 30, 2012
9,557
33,049
0
Hi Philz

I have flashed BULR1-SWC (3.75) version to my DXLR5.

It worked, but it seems that I am always stucked at 2G, hardly can get to 3G or H or H+. I have flash back to DXLR5 (2.7) for now.

Which version should I flash to avoid the signal problem that I encounter?

Thanks.
Try closest dxlr version

Sent from my GT-I9100 using Tapatalk 2