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

[anon67]

Pardon me if i am looking at the wrong place, but looks like v3.62 is only for JB leaked ROM's ? Do we have v3.62 for DDLR9-INU , as it seems for DDLR9-INU its still v3.5 ?

 

[Phil3759]

No update for previous kernels before this is cleared out:

>> I HAVE AMAZING NEWS <<​

Good news: I elucidated the mystery of loosing the possibility to format internal sd from within Settings / Storage / Format USB

Bad news: It is caused by patching the binary sequence to avoid brick bug

Now, we are stuck... until Samsung release the source for JB


Detailed Info:

After repacking new leaked JB kernels for i900/n7000, internal sd could no more be formatted from phone (Format USB storage)
After revising all my code, I noted that even a simple unpack / repack of stock kernel without any modification, still causes the issue. So, it was restricted to my unpack / repack process
I tried changing mkbootimg, recompiling it, using third party scripts, same result.
I finally decided not to patch the binary sequence to try it: Stock kernel, unpacked and repacked worked
I tried my kernel, unpack / repack with editing initramfs but no patching for emmc_cap_erase: Again, it WORKS


Conclusion: the binary sequence is no more linked absolutely to the emmc_cap_erase. As xda Elite developer Entropy512 said, Samsung added probably a workaround for the brick bug without patching emmc_cap_erase. However, without their source code for JB, no one can assert it at 100%

Debate is open HERE

What do you want: an uncertain emmc_cap_erase patch leading to potential instabilities or keep it stock and pray Samsung did their job well

 

[spacetaxi]

+1 vote for "keep it stock". I think Entropy's assumptions are right.

 

[Phil3759]

Enjoy the poll

By the way, this concerns only JB. I will continue updating old ICS kernels by patching them as it proved over time to be secure and bug free

 

[alucard8888]

Conclusion: the binary sequence is no more linked absolutely to the emmc_cap_erase. As xda Elite developer Entropy512 said, Samsung added probably a workaround for the brick bug without patching emmc_cap_erase. However, without their source code for JB, no one can assert it at 100%

Im on XXLSA ROM and XXLSA 3.63 kernel ver.
for confirmation is it safe to wipe data factory reset and flash another ROM? ( sorry just confused about the kernel issue)

Thank you

 

[Phil3759]

Im on XXLSA ROM and XXLSA 3.63 kernel ver.
for confirmation is it safe to wipe data factory reset and flash another ROM? ( sorry just confused about the kernel issue)

Thank you

0 bricks after 3 leaks for i9100 + N7000, so yes, safe

 

[kingears]

I say keep it stock

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

 

[bogdan1980]

I say keep it stock

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

Yep.

Sent from my GT-I9100 using Tapatalk 2

 

[kishd]

I have been using stock xxls7 kernel with your temp cwm and have wiped more than 10 times with no problems. I bricked my note twice with wiping under stock ics so I assume that jb is relatively safe with jb kernel and your temp cwm.

PS after Samsung replaced my phone (once repaired and the second time replaced) I still have the brick bug.

+1 for keeping it stock with custom recovery.

Sent from my GT-N7000 using xda premium

 

[shoey63]

Hard to imagine changing offending brickbug binary from 01 to 00 causes bugs but if it is the case, then better to leave it as unaltered stock. In any case your recovery still has "wipe via secure discard suppressed.." so wiping and formatting will still be safe, regardless of Samsungs patch. We would just have wait and see if anyone bricks flashing a zip with format commands and unpatched update binary.

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

 

[Phil3759]

I am testing another scenario. They changed format command and by patching kernel format is no longer possible

Sent from my GT-I9100 using Tapatalk 2

 

[ViD0]

So phil what do you want to say ? that samsung fixed emmc bug in JB kernel or what ?

 

[shoey63]

I just formatted internal (emmc) sd card from mounts and storage menu on patched LS7 without issue.

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

 

[Phil3759]

I just formatted internal (emmc) sd card from mounts and storage menu on patched LS7 without issue.

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

So maybe introduced with LSA?
Same for LSJ on i9100

 

[shoey63]

Just formatted 2gb sdcard in recovery with LSA. No problems.

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

 

[milsabords]

JB kernels

Hi Phil,
There is another customised JB kernel, made for the Alliance ROM. Robbie has a new release of his ROM based on LSA. You may try to share your experience with him, and see if he has the same problems.

 

[ViD0]

So maybe introduced with LSA?
Same for LSJ on i9100

So phil what do you want to say ? that samsung fixed emmc bug in JB kernel or what ?

 

[Phil3759]

New in v3.65 : PhilZ Touch v3.35 Recovery (CWM 6.0.1.9 based)

• Completed ors implementation: added script started on boot, with same function as custom ors (simpler code than previous versions)
• fixed ors-mount.sh support for phones without /emmc
• goomanager support fixed for phones without /emmc
• misc permissions fixes for recovery scripts

XXLSA-XJB (JB Leak)
http://www.mediafire.com/file/ba3uhmb6mpscwr6/PhilZ-cwm6-XXLSA-XJB-3.65-signed.zip
http://www.mediafire.com/file/5by5b0dd8tl6nex/PhilZ-cwm6-XXLSA-XJB-3.65.tar.md5

XXLS7-XJB (JB Leak)
http://www.mediafire.com/file/lfs6xh2odhrbfc3/PhilZ-cwm6-XXLS7-XJB-3.65-signed.zip
http://www.mediafire.com/file/uyu6bccsj3fe3uj/PhilZ-cwm6-XXLS7-XJB-3.65.tar.md5


Note: older kernels will be updated, at least the most recent ICS ones. However, the feedback is much more interesting with JB leaks, so focusing on them

 

[shoey63]

Good morning Phil.

FORMAT USB STORAGE BUG CONFIRMED!!!!!!

You awake now?
Ran the full gamut of tests on both pure stock and patched LS7 kernel in JB ROM and your recovery. Everything passes EXCEPT Format USB Storage on Philz LS7 in JB userspace. (Ie. Internal sd card/emmc/sdcard0).
Hope you get some useful feedback from Entropy512 or Tungstwenty.

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

 

[Phil3759]

Yeh short night
I think more and more at it as the proof patching mmc cap arase works
Maybe sammy changed the way sd card is formatted and it needs mmc cap arase. Until they release sources I would then continue patch it to be safe...

Sent from my GT-I9100 using Tapatalk 2