yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] Stevensoe:
First: Download new version of kernel .zip file

Second: Copy into sdcard and boot into recovery mode.

Third: flash it in cwm and reboot the system.

Done.:D
[Galaxy Note GT-N7000 Android Development] zai89:
Sorry, not Rom..but some phone..bootloop story start again:(
[Galaxy Note GT-N7000 Android Development] Stevensoe:
+1
[Galaxy Note GT-N7000 Android Development] $ideWinder:
I too have a bootloop. Anyway of fixing this without having to do a clean install?
[Galaxy Note GT-N7000 Android Development] zai89:
clean Install never solve bootloop bug.
[Galaxy Note GT-N7000 Android Development] Formhault:
So, only 7 seconds power button leads to bootloop? :eek: fu@Samsuck

Sent from hyperspace

---------- Post added at 07:37 AM ---------- Previous post was at 07:36 AM ----------

Forcing a ROM .tar through Odin for several times in a row seems to have worked for a few people :silly: silly: silly: :laugh: . They claimed to be bootloop free. :) lol...

Sent from hyperspace
[Galaxy Note GT-N7000 Android Development] zai89:
No, I also try that method...:silly:

flashing about hundred times since first few days official JB released...nothing solve it..

after that I voluntarily update my friend phone and yup, his phone dont have bootloop issue..only need one clean install and he can smile..

some phone a infected, some phone a not.

the worst thing happen to me is when I really need to make a call, took out my phone from my pocket and all I can see N7000 logo..haha

for phone that infected whit bootloop bug, it will bootloop by its self after few weeks or even after few day after clean flash..

thats way I came here to ask Phil3759 to make kernel like what he did for S2 that sloved bootloop bug..

and its really work for us..
[Galaxy Note GT-N7000 Android Development] Kamy:
Bootloop due to Hotboot on v4.93.6 on a a custom JPLSB

I am facing a bootloop issue while trying to hotboot on a custom JPLSB (which I have been using it for about more than 10 days without problem of FC or stuck on Samsung logo, booting up smoothly with previous kernel)

what I have done to solve my problem:

Flashing other kernel [Speedmod and Abyss] no success, stuck on Samsung Galaxy Note GT-N7000 logo and very tiny noises come from phone, again flashed Phil's v4.93.6 no booting up.

Clearing cash and davlik still the same

Trying use to "clean before flashing a rom" option and restore my backup - This could eventually help me to run and boot it up
[Galaxy Note GT-N7000 Android Development] Formhault:
Here's how to permanently make sure you never get bootloops, freezes, lags or huge temperature buildup : flash CM10.1 with NX kernel and undervolt -75mV. :good:

Just saying...

I'm sick of Samsung and their crapware. Fails to deliver... big time.

Sent from hyperspace
[Galaxy Note GT-N7000 Android Development] ntony17:
[MENTION=643734]Philz[/MENTION]

New firmware German DBT

my thread

http://xdaforums.com/showthread.php?t=2241203

Inviato dal mio GT-N7000 con Tapatalk 2
[Galaxy Note GT-N7000 Android Development] :
What I'm doing wrong?

I don't know what I'm doing wrong, but just now again tested with previously installed kernel and both new ones - PhilZ-cwm6-ZSLO2-OZS-4.93.6-signed.zip and PhilZ-cwm6-XXLSZ-OXA-4.93.6-signed.zip.

Phone booted with long press button and battery removal when phone ON.

ROM - XXLSZ Italy stock odex.

May be there some misunderstanding relating to Hot Boot. Phone booted after battery removed. But if use program Quick Boot Plus with options Hot Boot, phone does not booted. And same if use big power menu and push options Hot Boot (or Hot Reboot) phone not booted too.

Google play link: https://play.google.com/store/apps/...pcml1c2FwcGxpY2F0aW9ucy5xdWlja2Jvb3QucGx1cyJd

And as wrote before - remember that N7000 is one model, but in reality it may have little different hardware as well as some changes in ROMs (customs)

ADD: I do not tested Quick Boot with latest 2 kernels
[Galaxy Note GT-N7000 Android Development] zai89:
now i'm confused:silly:
[Galaxy Note GT-N7000 Android Development] hkgrob:
Perhaps post the Zimage if you have downloaded already.
[Galaxy Note GT-N7000 Android Development] Kamy:
[MENTION=4666971]Phil3759[/MENTION]

Kernel for N7000XXLT4

http://d-h.st/w6y

Edit: trying hotboot, bootloop happened on this stock kernel too.

It goes to recovery, there is a red error saying that:

E:Error in /data/log/recovery_kernel_log.txt

(Read-only file system)

and cannot boot up the phone, I suppose flash you kernel and restore my backup again
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
The DDLSC is fine with the original binaries kept.. No boot loops .. Hot reboot works fine.. battery pull > phone boots fine too..
[Galaxy Note GT-N7000 Android Development] shoey63:
I would love to contribute to the bootloop issue, but I no longer have a Note1. In fact I have just ordered Sony Xperia Z. Waterproof, dust-proof, 5" TFT screen, JB 4.1.2 and no superbrick/Sudden Death Syndrome issues. Entropy512 and Codeworkx (Plus many other heavy hitters) are over there developing CM10.1 for the device. Codeworkx refuses to develop for SGS 4. "Samsung is history" - in his own words. I hope I have a little more luck with Sony....
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
oh! :(
[Galaxy Note GT-N7000 Android Development] majdinj:
Calm down everyone, HootBoot seems to be not kernel related issue.. further searching the problem I found everybody seems complaining in other forums as well.. Some said that installing new busybox with pkill module can solve the issue (read this post here).. I personally tried that method but no go.. but since there is someone who had solved this problem by just installing some extra busybox modules will at least give us a hint where to search..

You are great Philz and always I love your modified kernels and recoveries images in other devices.. BIG THANKS and RESPECT to YOU!!
[Galaxy Note GT-N7000 Android Development] rraaka:
The important thing is shoey- YOU should have fun and enhance your knowledge. Bugs will come and go.
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
i read that too but that doesnot explain

1, with the modified kernel for boot loops the hot reboot goes into a boot loop till you use the power button

2. with the original binaries kept > hot reboot work just fine.
[Galaxy Note GT-N7000 Android Development] godmakarand:
Is it necessary to do a full wipe If I replace old philz kernel with new one? 4.90.8 by 4.93.6
[Galaxy Note GT-N7000 Android Development] rraaka:
i havent had bootloops in ages.

and im not gonna yank my battery out when rom is booted and fluid just to prove something.

i dont see this as a criteria for testing a kernel in any of the other kernel threads !!
[Galaxy Note GT-N7000 Android Development] majdinj:
Tried the latest Philz magic v4.93.6 JPLSB kernel in my custom ROM installed by the method that philz provided..

The feedback:

Tried Reboot --> OK

Tried HootBoot --> OK

Tried Recovery --> OK

Tried Download mode --> OK

Boot then take battery out then boot again --> no stuck or bootloop

Simply it is fantastic release :fingers-crossed:

BIG THANKS PHILZ
[Galaxy Note GT-N7000 Android Development] Phil3759:
Ghokanmoral and some kernel devs over the i9100 suspected the following:

- with latest JB ROMs, /data partition gets corrupted on unexpected shutdown

- changing the init binary with older ones will let the system boot even if /data is corrupted

- some ROMs seem immune to the issue, what ever kernel/init binary combo is used

- changing the init, will not fix the /data corruption issue

- many parts were suspected like bootloader, some binaries related to toolbox..., none showed to be the reason

The only person I know that can give a definite explanation for this is Ghokanmoral , but his dev over the i9100 is for now on hold because of personal reasons

In my case, using an older JB ROM with latest kernels, repacked or stock, will make all reboots work. Using any newer ROM with a non repacked kernel will stuck in the bootloop

I sadly have no time at all to focus on this. As I said, I stick to stock kernels and I do not plan any soon to start compiling kernels from source. I only focus on coding for CWM and maintaining ramdisk changes for the kernel whenever it is needed or a fix proven to be effective
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
I lost the custom settings on Touch recovery like the menu color, preload in nandroid, brightness etc after flashing the new kernel though.
[Galaxy Note GT-N7000 Android Development] Phil3759:
You missed 4th line in change log :o

http://xdaforums.com/showpost.php?p=40406321&postcount=3139

If you did a backup once, it should have restored things on next reboot

However, you can still just move the settings folder from /system to /data and your lost backups will resuscitate
[Galaxy Note GT-N7000 Android Development] Phil3759:
Would be great if you test them too (if I ever inverted them...)
[Galaxy Note GT-N7000 Android Development] dr.ketan:
Ok wait
[Galaxy Note GT-N7000 Android Development] Phil3759:
I can make the menus a bit larger, but not the font for many reasons

The Note having a higher res than s2, from your pic I feel I could space rows even a bit more, but you loose some space when scrolling folders...

On the S2, I won't increase more

What do you think, let it that way?
[Galaxy Note GT-N7000 Android Development] dr.ketan:
Ok tested all two physical and four virtual key and working as it should be.

I think current space between lines is fine, otherwise as you said we will have less space to see files, which is also useful to navigate perticular file, if we can see on same screen, it is easy to select to reach to file from ascending/descending order. As well current spacing is very comfortable too.
[Galaxy Note GT-N7000 Android Development] Phil3759:
Big thanks :good:

Going to sleep while PC runs memtest

bye
[Galaxy Note GT-N7000 Android Development] dr.ketan:
Good night

It's 3am here too. :p
[Galaxy Note GT-N7000 Android Development] shoey63:
+1 re buttons and layout (A bit late with report I know but I was already in bed when file was sent ):o
[Galaxy Note GT-N7000 Android Development] jaskiratsingh:
Thanks phil for the explanation.
[Galaxy Note GT-N7000 Android Development] shoey63:
Did it freeze an FactoryFS? Sounds like u are Superbricked. :eek: Take it to Samsung and ask for a MOBO replacement. :silly:
[Galaxy Note GT-N7000 Android Development] kopitalk:
??? Bios beep beep issue...
[Galaxy Note GT-N7000 Android Development] shoey63:
Just being silly:o
[Galaxy Note GT-N7000 Android Development] kopitalk:
Phew... man, I thought you lost your sanity or what...
[Galaxy Note GT-N7000 Android Development] shoey63:
I think I lost it when I bricked my Note using unsafe CWM.zip (thankfully replaced by grey retailer). BTW folks, Phil was talking about his PC (not his phone :D
[Galaxy Note GT-N7000 Android Development] Phil3759:
Yeh, the pc. Memtest did not errors. So i guess i will have to debug it blindly. Gonna shop for new ram again in the afternoon
[Galaxy Note GT-N7000 Android Development] shoey63:
U don't have a SSD in ur PC as Primary HD by any chance? AHCI mode causes heaps of freezes! I had to change mine back to MBR mode to stop it :(
[Galaxy Note GT-N7000 Android Development] shoey63:
Y not reflash newest BIOS if Memtest says all good? Or even do ur work from Ubuntu off a pendrive? (Abit slow - yes, but the job gets done):thumbup:
[Galaxy Note GT-N7000 Android Development] Phil3759:
No SSD, have AHCI since years, no issues. Rig a bit old. Was a fan of watercooling in the sight of silence rather than overclocking. Now, if I have to unmount the motherboard it will take me weeks to reset my old watercooling setup. Probably even the tubes will have to be changed...

So, the less I touch it, the better is, until the day I see water vapor and hear a big Pffffffffff :D

Updated to 8Gb RAM right now and put matched pairs, maybe that was the issue, heavy memory load with unmatched pairs in size and specs on an old MB. The bios hardware failure let me hope it is this. Will see...

Now, back to work on my script builder, tomorrow real life work, so will be by end of week
[Galaxy Note GT-N7000 Android Development] Phil3759:
Finally you could be right.

Undrer 8Gb RAM new modules (well 4 new and 4 old), still freeze. Anyway, I wanted those 8 gigs RAM since a while

By case, two weeks a go, I moved the ubuntu virtual partition to my AHCI drive...

Now, all freezes happened when I am writing/reading from that disk. Once it even unmounted on its own while I was compiling in Ubuntu...

Badly, this was during a... gparted resize session :eek:

So, not even sure it will ever boot again. Could have to re-install ubuntu and reset all build environment from crap, this sucks a lot if you know what I mean...

I am moving virtual disks to my C drive now to see, wishing the VM boots at least after this hang in a gparted session. I will unmount my AHCI drive since I get freezing even when virtual machine is off.

All this seems bad and I feel it will take a while :(

For now, I have no working PC... it will be fixed, hopefully, hope the sooner
[Galaxy Note GT-N7000 Android Development] dr.ketan:
Have you tried with single ram slot?

I have experienced it, even if size is same though it mismatches.

Clean contacts with eraser too.
[Galaxy Note GT-N7000 Android Development] Phil3759:
Will give it a try if still failing

Good news, the ext4 partition survived what would have killed for ever any NTFS partition, and this is even under a VM

I disabled AHCI and will give it a second go from that same drive. Keeping it on C kills my system perfs...
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
oops sorry..
[Galaxy Note GT-N7000 Android Development] zai89:
So, next built will keep the original binaries, or use the older one just like before?..
[Galaxy Note GT-N7000 Android Development] Phil3759:
You decide...

For now it is a mixed deal

But probably revert to old binary so that it is ok for all, except hotboot which will be buggy it seems...
[Galaxy Note GT-N7000 Android Development] majdinj:
Since I don't know what is the concept of immune device means... Just curious whether deleting philz-touch folder from system partition will solve others problem!!
[Galaxy Note GT-N7000 Android Development] Phil3759:
No, this has nothing to do. The issue is present on a stock ROM/kernel combo freshly installed in odin

It is Samsung crapware. At least my kernel lets you boot and run your ROM while Sammy will die in a bootloop
[Galaxy Note GT-N7000 Android Development] zai89:
for hot reboot, I can use 3rd party apps..

for bootloop bug, I will choose philz kernel..
[Galaxy Note GT-N7000 Android Development] Tassos_i:
What a shame !!!

Just installed latest OXALT4_DBT through PC Odin after cleaning everything twice. Guess what ? Before rooting or installing anything new, after initial start, pressing the power button for 7 secs leads to ...BOOTLOOP (the full one)! Back to XXLSZ stock rom with semi-bootlooping Philz 4.93.6XXLSZ kernel.

EDIT (off topic) : I kept the new XXLT3 modem though, which seems to work very nice.
[Galaxy Note GT-N7000 Android Development] Formhault:
Since the old binaries seem to fix the bootloop bug (in any way possible), and do not affect stability or functionality (right?)... I'd suggest you stick with those, Phil.

What do the new binaries add...? The bootloop bug, here and there. Besides that, no increased functionality etc...
[Galaxy Note GT-N7000 Android Development] majdinj:
So technically, the problem is triggered when you flash stock official rom with odin then flashing new philz kernel, right?? since I am on custom kernel and new philz kernel is working without any drop of problem!!!
[Galaxy Note GT-N7000 Android Development] Phil3759:
No

Read what I wrote: It is a Samsung issue. PhilZ kernel = Samsung kernel

No need to flash anything else than Samsung great files to be stuck in the bootloop
[Galaxy Note GT-N7000 Android Development] Formhault:
So... in other words... FU Samsuck.

We wanted this OTA so much... they gave it to us, but not in the form we were expecting it (no black clipping fix, not all Note 2 features ported as we were told... bootloop bug...).

[MENTION=218262]Phil[/MENTION] : keep the previous inits that resolved the bootloop. Apparently, you alone are better than Samsung's entire dev team. And I think we can all agree on this one. Most XDA devs are better than some OEM's devs, I guess. Either that, either it's juuuuuust marketing :rolleyes: .
[Galaxy Note GT-N7000 Android Development] majdinj:
So if I understand correctly, that means if you use old JB release with this new philz kernel it will be alright?? (sorry for being lazy brain!!)

I am on custom deodexed JPLSB, with PhilZ-cwm6-JPLSB-UAE-4.93.6-signed installed with philz_installer.cfg toggle to skip installing SuperSU..

I want to help since I don't have those problems that others have..
[Galaxy Note GT-N7000 Android Development] whitedavidp:
Philz For Release LT4?

I have noted on Sammobile that there is an LT4 release of 4.1.2 for my Note I. Still no idea what is changed on it from the LSZ I am currently running. Is there a Philz safe kernel with root for this? Thanks
[Galaxy Note GT-N7000 Android Development] Formhault:
Funny. LT4 ROM with LT3 modem...

Sent from hyperspace
[Galaxy Note GT-N7000 Android Development] Phil3759:
Well, then maybe your custom Deodexed ROM fixed something. I doubt the kernel is fixed.

Only LS2 ROM I think was fine for N7000, that is really an old leak one
[Galaxy Note GT-N7000 Android Development] Phil3759:
I have no problem that you repack them, but just do not name them as if they were mine.

Or at least mention that these are repacked by you, so Non Official PhilZ-cwm6 releases

I will release LT4 and release all previous versions with fixed init as soon as I am done supporting new HTC devices
[Galaxy Note GT-N7000 Android Development] Phil3759:
Maybe just name them PhilZ_Touch instead of PhilZ_CWM

PhilZ Touch is my mod CWM Advanced Edition + my touch/gui code

PhilZ-cwm6 is the special zImage combo only for N7000 and i9100

Thank you
[Galaxy Note GT-N7000 Android Development] Phil3759:
I do not read it well as you say

As I said, I am happy when people choose my recovery, even if you did without asking for permission ;)

Just I do not want that people get confused

PhilZ-cwm6 are specific stock kernels I build only for N7000/i9100 with a modified ramdisk and mainly a patched EMMC_CAP_ERASE kernel

When you repack stock kernels, I ask you to clearly state and write that they are repacked by you with PhilZ Touch recovery or TWRP. Just add it somewhere in your post, that's it. I would be fine 100% with that

Thank you a again and any contribution / addition is welcome.
[Galaxy Note GT-N7000 Android Development] koskos:
is it safe to use PhilZ kernel to flash cyanogenmod? (from stock 4.1.2 XXLSZ)?
[Galaxy Note GT-N7000 Android Development] Phil3759:
Link?

As far as I know, Entropy512 never said that. The debate was never and will not be ironed out as Samsung do not publish source for their chips. Entropy512 said probably it is enough, but he was nervous about it and would never allow it. The speed / performance is very theorical and under very special circumstances all explained by Entropy and other members. All this was debated months ago and nothing changed since that

Anyway, that's not the question. I was fair enough, but I ask you a last time:

There are clear rules in xda about developers:

- If you use someone else work, you need to ask for permission. You did not, but I say ok

- Your custom kernels I do not mind

- This N7000_JB_LT4_PhilZ_CWM_kernel.tar is not mine. So, do not tell people there is a Philz-cwm6 release of LT4 when they ask. Furthermore, you do not patch the kernel and you do not even mention it. Many do like safety, mainly for N7000 community. I always put detailed logs

- If you want to keep your post or a thread: Sate clearly from where you leach the ramdisk, what you do change and that you are the repacker/releaser

I cannot be more clear, else there are moderators in xda to decide
[Galaxy Note GT-N7000 Android Development] Phil3759:
And by the way, look at the poll in top of this page: It is enough clear what people asked for. If you do not do it, be fair and mention it
[Galaxy Note GT-N7000 Android Development] pillainp:
I am currently running DDLSC-ODD v4.90.8 with CWM 6.0.3.0 on my Note.

Can I directly upgrade to 4,93.6 from CWM recovery?

Or do I have to go to stock recovery and run the update from there?

If so, how do I do that?

Please help.
[Galaxy Note GT-N7000 Android Development] shoey63:
Phil is right. Entropy512 never has, and never will sanction Samsungs method of "non-secure" erase on Note1 devices. And on stock kernel, JB or ICS, this is exactly what happens - no difference. If you are loathe to do factory reset from recovery on stock ICS kernel, then you should have the same reservations about doing it on JB. Samsungs safety measure for JB kernel is to block the deadly "secure" erase command, which is issued by unsafe recoveries (eg. CWM.zip) and zip files using format commands with unpatched update binary.
[Galaxy Note GT-N7000 Android Development] Spo0f:
Sorry to interupt - can we use safe kernel for LSZ to root LT4(new DBT rom)?

Thanks
[Galaxy Note GT-N7000 Android Development] zai89:
Yes.
[Galaxy Note GT-N7000 Android Development] mordauntlong:
yeah u can update from CWM recovery::)
[Galaxy Note GT-N7000 Android Development] mrgnex:
I am running on stock jb 4.1.2 xxkk5. But I have no idea which version tot choose... Can someone help? If I understand correctly this can be done with stock recovery and will root your device?
[Galaxy Note GT-N7000 Android Development] Cyrion:
Mrgnex are you sure you have a n7000 ? 4.1.2 Xxkk5 seem to be a galaxy s2 kernel

Envoyé depuis mon GT-N7000 avec Tapatalk
[Galaxy Note GT-N7000 Android Development] mrgnex:
Its the baseband version. Screenshot is attached.
[Galaxy Note GT-N7000 Android Development] Cyrion:
Xxlsa is the kernel. Baseband is the modem.

You look the wrong code version

And xxlsa is the jb leak version

Envoyé depuis mon GT-N7000 avec Tapatalk
[Galaxy Note GT-N7000 Android Development] rraaka:
Phill, thank you for allowing klementy to post in your thread.
[Galaxy Note GT-N7000 Android Development] Phil3759:
I will release lt4 by end of day, now that i am quite done with htc
[Galaxy Note GT-N7000 Android Development] Formhault:
What do you mean, done with HTC?
[Galaxy Note GT-N7000 Android Development] Phil3759:
PhilZ Touch for One X and One XL. Soon One S. Maybe Xperia Z if Shoey is not too scared :D
[Galaxy Note GT-N7000 Android Development] mac20dnangel:
Philz, are you going to release it today? Thanks by the way.
[Galaxy Note GT-N7000 Android Development] Formhault:
Oh... Didn't know you're building kernels & recoveries for those, as well :p

No way I'm going to the One X. I wanted to, but then I found out about different CPU revisions and Wi-Fi issues and well... next upgrade : Note 2, S4 or One :)

Shoey has the Z? :eek:
[Galaxy Note GT-N7000 Android Development] rraaka:
i think it was wonderful mac, that you were going to release your rom with the other kernel ;)
[Galaxy Note GT-N7000 Android Development] mac20dnangel:
Thanks

Yeah... I'm already uploading the file but I thought that the ROM will make sense if I put Philz new Touch Kernel, specially for LT4 Based Firmware so I cancelled it for the moment.

Hoping that Philz will made it available soon.

More Power Philz....;);)
[Galaxy Note GT-N7000 Android Development] Phil3759:
Yes, as soon as i am home

The stock one still bootloop on unattended reboot?
[Galaxy Note GT-N7000 Android Development] Kamy:
One I tried ls4 for hotboot it gets bootloop.
[Galaxy Note GT-N7000 Android Development] mac20dnangel:
Thanks Philz,

Just take care mate. I'll wait for it right now so I could finish also my work here.
[Galaxy Note GT-N7000 Android Development] majdinj:
Try to modify ROM.zip by putting new philz kernel zImage file instead the one inside the ROM and clean everything and install the modified one..