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

[kopitalk]

I know it sounds strange ( see my post "hanger at Sam Logo") but when I called my Service Tech Guy in China, he mentioned this problem also.
He said: quote:"after flashing the ROM you MUST restart your phone at least two times before rooting or flashing other kernels, otherwise you lose the USER apps and the CSC specific bload ware"
He also recommends (again see my other post) to flash the ROM at least three times." unquote
Again it is all strange, but it worked here. I was suspicious and ask for names and telephone numbers of others here in Chengdu in order to verify his strange advise. I called 5 of his customers, they all confirmed it worked.
It also worked for me b.t.w.
So it is up to you. To do it or not. I think its worth to give it a try.

It's crazy yet I'm close to desperation so I took a plunge, and somehow it went well!
I think the problem is because I flash stock XXLSZ using PC ODIN and somehow the bootloader issue gets the data partition corrupted?
Those who flash custom XXLSZ via CWM don't get this problem.
A VERY BIG THANK YOU FOR SHARING THIS!

Edit: I think those who flash official XXLSZ first time using PC Odin will get this issue, and subsequent flashing XXLSZ (and bootloader) via CWM won't help. However those who flash custom XXLSZ first time using CWM can escape this issue unscathed, whether or not they flash the new bootloader.
I may be wrong, but this is based on my personal encounter.

 

[Formhault]

Re: [21.02.2013][PhilZ-cwm6][n7000] v4.63 Safe Stock Kernel+CWM6+Root+exFAT+ext4-LSZ

It's crazy yet I'm close to desperation so I took a plunge, and somehow it went well!
I think the problem is because I flash stock XXLSZ using PC ODIN and somehow the bootloader issue gets the data partition corrupted?
Those who flash custom XXLSZ via CWM don't get this problem.
A VERY BIG THANKS FOR SHARING THIS!

Flashing LSZ through CWM (already having XXLSZ ROM + new bootloader installed)... Doesn't mean you're gonna be bootloop (actually, boot stuck?). I got stuck

If it's a Samsung firmware issue... We're gonna get an updated revision soon... Hopefully...

Sent from my Galaxy Note held captive in Chasmodo's Asylum

 

[fulltank]

Is it ok to flash v4.63LSZ over existing 4.35LM5 ? , I have official LM5 ROM.

Why should I do it ? > No 4.63 LM5 release , and I am a flasholic , But just don't want to end up in bootloop ,,!

Also , Is it possible to make incremental back ups with CWM ?

 

[zai89]

Is it ok to flash v4.63LSZ over existing 4.35LM5 ? , I have official LM5 ROM.

Why should I do it ? > No 4.63 LM5 release , and I am a flasholic , But just don't want to end up in bootloop ,,!

Also , Is it possible to make incremental back ups with CWM ?

yes, its ok to flash...just make Nandroid backup 1st..

 

[fulltank]

yes, its ok to flash...just make Nandroid backup 1st..

Thanks,works fine....

 

[kopitalk]

Re: [21.02.2013][PhilZ-cwm6][n7000] v4.63 Safe Stock Kernel+CWM6+Root+exFAT+ext4-LSZ

Flashing LSZ through CWM (already having XXLSZ ROM + new bootloader installed)... Doesn't mean you're gonna be bootloop (actually, boot stuck?). I got stuck

I think the first PC Odin could be the culprit, because subsequently I flash CWM but problem still exists. Maybe one can try flashing eybee's Sbl.bin package via CWM repeatedly around 3 times in a row to clear bootloader issue rather than PC Odin the whole ROM repeatedly 3 times in a row?

 

[rraaka]

i know codeworkx provides tar file of JB bootloader with CM 10.1, that would be more effective

 

[jaguaralani]

I know it sounds strange ( see my post "hanger at Sam Logo") but when I called my Service Tech Guy in China, he mentioned this problem also.
He said: quote:"after flashing the ROM you MUST restart your phone at least two times before rooting or flashing other kernels, otherwise you lose the USER apps and the CSC specific bload ware"
He also recommends (again see my other post) to flash the ROM at least three times." unquote
Again it is all strange, but it worked here. I was suspicious and ask for names and telephone numbers of others here in Chengdu in order to verify his strange advise. I called 5 of his customers, they all confirmed it worked.
It also worked for me b.t.w.
So it is up to you. To do it or not. I think its worth to give it a try.

Thanks mate for this method, could you please elaborate a bit on the steps ?

1-So we should flash the STOCK LSZ using PC ODIN, 3 times in a row, at which stage should you get back to DOWNLOAD MODE to reflash ? should we wait until the rom boots up completely, set the gmail etc, the back to download mode ? or back to download mode as soon as the rom starts asking to choose language ?

2-When should we do the restarts ( you mentioned to do a couple of restarts ), after doing the triple flashes or after each of them ?

3-When to root the rom with a rooted kernel ?

4- lastly, what if we flashed a custom rom afterwards ?

Thank you very much in advance.

Cheers

 

[fadhil3536]

Re: [21.02.2013][PhilZ-cwm6][n7000] v4.63 Safe Stock Kernel+CWM6+Root+exFAT+ext4-LSZ

Hi phil. I am using your latest kernel for LM5. I am using stock odex LM5. My problem is when making nandroid backup to this rom and restore it,my google account will be reset means i have to add again my google account. When i do that (try to add accnt in setting the system ui will force close. I thought maybe a bad backup. So do it again.. flash the same rom-nandroid-wipe or not wipe - restore... still the same. So far 6 time done this but no go.. any idea?

Sent from my GT-N7000 using xda premium

 

[nokiamodeln91]

have you tried to do a backup with preload partition included?
the setting is in Backup and restore > misc nandroid settings

 

[mordauntlong]

nandroid

hi sorry for noob Q,how can i use this new philz lsz cwm6 to do a back up of the rom image only, or better yet how can i choose only what i want to back up??
and where should i best put it,on int sd or ext sd?thanks

 

[nokiamodeln91]

Philz Setting> Custom Backup & Restore> Custom Job.. then you will see a list of options to choose from

 

[mordauntlong]

..thanks a lot man!

 

[hailmary]

Philz375

is the 4.63 compatible w/ lsc? i just dont wanna go to the latest lsz...but i want to get latest kernel feats & stay w/ my own lsc bbq...

 

[nokiamodeln91]

LSZ kernel works on LSC as well.. It worked for me on Ultimate

 

[Formhault]

I think the first PC Odin could be the culprit, because subsequently I flash CWM but problem still exists. Maybe one can try flashing eybee's Sbl.bin package via CWM repeatedly around 3 times in a row to clear bootloader issue rather than PC Odin the whole ROM repeatedly 3 times in a row?

Erm... I doubt.

You flash with Odin. What gets written? System, data, preload, kernel+recovery and the bootloader (if included), right?

You flash with CWM. What do you erase before? System, data, preload. What gets written? System, data, kernel+recovery. You flash bootloader manually with CWM... and that's what you wipe & flash - the bootloader.

I don't think wiping in CWM leaves a few bits uncleared on any partition (that got written before with Odin). Unless flash memory gets half-erased... if that's even possible

Am I right...?! :/

---------- Post added at 09:04 PM ---------- Previous post was at 09:03 PM ----------

i know codeworkx provides tar file of JB bootloader with CM 10.1, that would be more effective

So... a .tar with the new bootloader and CM10.1 instead of a stock TW ROM? How could that be more efficient? It's the same bootloader. Or is it a newer, maybe fixed, build?

 

[Phil3759]

have you tried to do a backup with preload partition included?
the setting is in Backup and restore > misc nandroid settings

Exactly,
Also, people must keep in mind that despite the huge change in UI and the Custom Backup and Restore part, the backup source code / engine is same as Koush original CWM. I did not mess with it at all and credits go to Koush

Most I added is code support for single / custom selected partitions.
Only original code is for TWRP and compressed tar.gz format, but it still mostly rely on Koush source except small change in commands

 

[whitedavidp]

Oh Oh!

I updated to the official JB release the other day and replaced the HydraCore kernel I was using with Philz ZSLM5. Seemed to work great although I did miss the overclocking. Today I installed XXLSZ and it seemed to work just fine as well. But after an extended period with the screen off in my pocket, I pulled the N7000 out, hit the on button, and got NOTHING! I pulled the battery and put it back. I try to start the device and it is just stuck at the Galaxy Note GT-N7000 logo screen. I booted into recovery and flashed back LM5. But still have the same issue. Not sure what is up here. Any ideas? Thanks

 

[corsicanu]

Re: [21.02.2013][PhilZ-cwm6][n7000] v4.63 Safe Stock Kernel+CWM6+Root+exFAT+ext4-LSZ

I updated to the official JB release the other day and replaced the HydraCore kernel I was using with Philz ZSLM5. Seemed to work great although I did miss the overclocking. Today I installed XXLSZ and it seemed to work just fine as well. But after an extended period with the screen off in my pocket, I pulled the N7000 out, hit the on button, and got NOTHING! I pulled the battery and put it back. I try to start the device and it is just stuck at the Galaxy Note GT-N7000 logo screen. I booted into recovery and flashed back LM5. But still have the same issue. Not sure what is up here. Any ideas? Thanks

make a backup with cwm and then restore same backup... should work.. or full wipe if you have nothing to lose.
cheers!

Sent from my GT-N7000 using Tapatalk 2

 

[whitedavidp]

make a backup with cwm and then restore same backup... should work.. or full wipe if you have nothing to lose.
cheers!

Sent from my GT-N7000 using Tapatalk 2

Whew! My nightly online nandroid backup saved my butt! I was able to boot into recovery, restore last night's nandroid backup, and all seems well again. Scary! Thanks