yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] Kamy:
No, got me wrong dear. I tired totally stock: rom and kernel, actually I falshed the LS4 Firmware just for testing new build using PC odin.
[Galaxy Note GT-N7000 Android Development] majdinj:
As I understand from philz, bootloop issue started after LS2.. so try LS2 ROM
[Galaxy Note GT-N7000 Android Development] Phil3759:
LT4

bootloops or no, when stock? not LS4
[Galaxy Note GT-N7000 Android Development] Kamy:
Sorry my bad that was only a type I tried LT4, new German build: N7000XXLT4_N7000OXALT4_DBT and got bootloop while trying to reproduce the bootloop issue

Edit: Flashing procedure: 3 wipes and all required formats before using ODIN
[Galaxy Note GT-N7000 Android Development] mac20dnangel:
Yes, for some instances it really happens after installing a new Stock Firmware in Odin.

What you need to do is Wipe it. But wiping from the original or stock recovery will brick your Note.

One thing you can do is Flash Philz Touch Kernel and wipe it there after getting into Custom Recovery.

or

If, installing from Zip doesn't work, you can flash the Odin file of Philz Touch Kernel for your firmware then wipe it there.

After wiping data/factory reset and cache, try to boot now into system.

See if this work for you.

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

I use the LT4 Custom Kernel from 4pda.ru and it bootloops sometimes. Pressing Power Button 7 seconds turn it into bootloop.
[Galaxy Note GT-N7000 Android Development] zai89:
I also wipe my screen but still had bootloop on stock lt4..:p
[Galaxy Note GT-N7000 Android Development] mac20dnangel:
Well, Philz is already doing the LT4 kernel and I'm sure he is already aware of this. I believe he will fix this bootloop issue on XXLT4 firmware.

I think it's a kernel issue because even in my Custom ROM it bootloops.

Here are some of the details where it get bootloop:

Pressing Power Button 7 seconds long

Removing Battery Before Complete Shutdown

Low Battery Level

And sometimes on Restarting the Phone

This is based on my experience.
[Galaxy Note GT-N7000 Android Development] :
Phil3759, Many users, and I'm including, reports, that in the kernel of PhilZ-cwm6-XXLSZ-OXA-4.93.6-signed.zip bootloop missing
[Galaxy Note GT-N7000 Android Development] mac20dnangel:
I'm Super Excited for the New Release....
[Galaxy Note GT-N7000 Android Development] LG-Viking:
I installed stock XXLT4 with mobile odin and have no bootloop issues...
[Galaxy Note GT-N7000 Android Development] ntony17:
Lol +1

:D:D:D:D

Philz the boss! :D

Inviato dal mio GT-N7000 con Tapatalk 2
[Galaxy Note GT-N7000 Android Development] Phil3759:
v4.93.6 - fixed for bootloop

DDLSC - DXLSE - JPLSB - XXLSZ - XXLT4 - ZSLO2

Download folder

ZCLSF - not bootloop fix

Download folder
[Galaxy Note GT-N7000 Android Development] mac20dnangel:
Thanks Philz... Downloading Now... You make my Day Complete.
[Galaxy Note GT-N7000 Android Development] RomWiz:
there is only "aply update from sdcard" not external...
[Galaxy Note GT-N7000 Android Development] Phil3759:
That never changed!

I never added apply update.zip from internal and I do not see the need of it. Just use Install zip menu instead
[Galaxy Note GT-N7000 Android Development] RomWiz:
I mean in stock recovery!

but nevermind, i don't need this anymore since i got it booting!
[Galaxy Note GT-N7000 Android Development] Phil3759:
Well, for stock recovery you have to ask Samsung...
[Galaxy Note GT-N7000 Android Development] ntony17:
Thx philz;)

Inviato dal mio GT-N7000 con Tapatalk 2
[Galaxy Note GT-N7000 Android Development] liron_69:
hello Phil...

I've flashed the new LT4 kernel v4.93.6 but now I have no root....

Superuser is not functioning....

I'm with JonROM LT4...
[Galaxy Note GT-N7000 Android Development] Phil3759:
If the ROM puts superuser.apk and su in preload, than ask the ROM maker to clean things...
[Galaxy Note GT-N7000 Android Development] liron_69:
well I tell you what I did that cause it...

this morning I flashed the ROM zip file

and flashed your kernel LO2 .... rebooted

I had root and everything perfect...

now, I updated the kernel to LT4

and I have no root... I cant understand why....

I need to look for some zip file on the net to push SU to get the root back ?
[Galaxy Note GT-N7000 Android Development] zai89:
Just re-flash your rom without any wipe..and ask your Rom dev about this.
[Galaxy Note GT-N7000 Android Development] thermax04:
is this normal?

iam on Note 1 with glory rom v4.5 with PhilZ kernel

I tried to clean my rom from some problem

I wibed the data/factory reset from CWM, thinking that it will be like format to refresh the rom, but after wiping the phone did not reboot and stuck at samsung logo, like it deleted the rom!!!

I had to restore my previous backup to reboot the phone

is this normal behavior from this kernel or not? and what is the reason?
[Galaxy Note GT-N7000 Android Development] zai89:
data/factory reset?, it will need more time to boot just like on 1st flash...its normal.

if you want to clean your rom from some problem just wipe cache and dalvik cache.
[Galaxy Note GT-N7000 Android Development] Nodens:
Since the bootloop fix is not really a fix it should not be applied anywhere imho. Allowing you to boot properly and work with a corrupted file system will only cause more issues and data loss. Hiding dust under carpets only makes for a higher amount of dust.. It seems that a lot of people here did not understand what Phil explained about this and think their devices are working properly..
[Galaxy Note GT-N7000 Android Development] zai89:
So, do you have bootloop bug? Your phone infected?
[Galaxy Note GT-N7000 Android Development] Phil3759:
You should read instructions + popup messages

That option really wipes everything include /system and /preload

So, you need odin after that. It is well explained in popup message when you said Yes
[Galaxy Note GT-N7000 Android Development] thermax04:
So, wipe data/factory reset will wipe my rom files, right? and it leave me with no rom to reboot

What is the use of Odin after the wipe?
[Galaxy Note GT-N7000 Android Development] Phil3759:
No, factory reset just does a factory reset
[Galaxy Note GT-N7000 Android Development] qnt:
Few days ago I've installed the LT4 stock ROM using Odin mobile to get root in waiting for Philz kernel. This morning I've flash the last LT4 Philz kernel. As usual all are OK, root is still there. Thank Phil3750 very much.

Just my two cents: Do not forget to donate to Phil3759 for his excellent work.
[Galaxy Note GT-N7000 Android Development] Nodens:
How is that even relative to what I'm saying. You are probably not understanding. It is not a fix. If you have the issue and use the "fix" you will have corruption that you won't know about and can cause you loss of valuable data.

Still to answer your question I have the issue on abnormal shutdowns. I do not want the older init as I if it hits me again I don't want to overwrite my backups with corrupted data. I prefer to restore my proper backups every time it hits me until a real fix is found.

This is not a fix. It is asking for trouble.
[Galaxy Note GT-N7000 Android Development] mac20dnangel:
Well not everyone is experiencing those problems and you cannot say that what Philz said about the fix is not really a fix. Try to observe first what causes that trouble and give him some details and logcat.

Philz's work help me a lot in my current project especially with the LT4 one. It fixes bootloop issue with me. What Philz Touch version are you trying to use?

Just check it first and give him some feedbacks so he might fix it.
[Galaxy Note GT-N7000 Android Development] Nodens:
It is not me who said this. It was Phil himself. I am just pointing out that people did not understand what he said, I'm quoting the post bellow:

See the parts I highlighted. The fix is not a fix. It just allows you to boot with /data still corrupted. It can not even be classified as a workaround (by development standards) as it does not even work around the issue. Sure it can help you if you're actually debugging and need access to the device but this should not be included in what end-users use as they will just run around with devices with corrupted /data, thinking they're fine when they're actually not. If user ends up with corrupted /data, they should restore from a valid backup, refrlash or if it's happening all the time, downgrade to a ROM that doesn't cause this. Leaving /data corrupted is not a good idea in any kind of way.

To use an oversimplified example, imagine you have a corrupted installation of Linux or Windows. Should you fix it? Or should you continue working in the operating system as if nothing is wrong?
[Galaxy Note GT-N7000 Android Development] Phil3759:
I myself sticked to XXLSJ leak JB ROM + latest kernel as no /data corruption occurs. I said that so many times

I also said many times that the "fix" is temporary and that's the best i9100 community have for TW ROMs. Else, you have to move to cm/aokp, which is not what most like

If backups or online syncs are made regularly and data integrity is not a prime issue, then the workaround is acceptable as it is all we have and can let people access their data for eventual backups.

I could verify on 2 occasions that a nandroid backup can still happen without any data loss on such bootlooping systems after unattended reboot. Once you format /data and restore the nandroid backup, all is back. So maybe more related to some partition structure errors than real user data corruption.

Having the init changed let people use their phone longer, and once it bootloops, they can do a nandroid backup, format /data and restore their nandroid backup as it is a tarball image, not a raw backup

More tests are needed to confirm this, but for now, it is the best available for people that want to stay on a stock kernel

However, the best would be to stay on stock init and try to always make a clean shutdown

You have both versions released, everyone can be happy
[Galaxy Note GT-N7000 Android Development] mac20dnangel:
+100000 For this....

I totally agree with Philz. :D:D
[Galaxy Note GT-N7000 Android Development] georgios73:
Phil I have bootloop using your latest LT4 kernel.

Flashed on stock LT4 any advice please?
[Galaxy Note GT-N7000 Android Development] boris03:
Just got my note back from warranty repair - new mainboard!!

Was having LSZ on it and the phone updated automatically to LT4 this evening.

This is quite smooth I am impressed.

When I would now install the latest LT4 Kernel for getting root, will the phone allow further Samsung updates

or is it blocked with a custom Kernel like this one?

Thanks
[Galaxy Note GT-N7000 Android Development] Formhault:
No OTAs for you :p . Recovery is also not stock, so...

Sent from hyperspace
[Galaxy Note GT-N7000 Android Development] Nodens:
Partition table is pretty straightforward and if the issue was there, files read from the file system would be corrupted. It must be file system related. We could examine file system metadata after it happens. Unfortunately I'm very busy right now as I have some deadlines to meet. I'll see if I can research it when I find time.

If file i/o is not corrupted then it's fine. When you initially said /data corruption, I assumed there's actual user data corruption. If files can be read/written properly, then it boils down into file system elements for sure. Perhaps it is the handling of the unclean file system that is failing. What exactly led the researchers into the conclusion of /data corruption if user data can be read intact? Is there a thread with more information?

Thank you very much for this. Perhaps a note should also be added to the changelog that mentions what the workaround actually does. I am sure technically adept users would appreciate the information.

I am really glad I actually found your original post about it as I use this device as a beta testing device for the software I develop. Any data corruption could cause me to start chasing issues that are not really there..
[Galaxy Note GT-N7000 Android Development] Stevensoe:
Deleted.
[Galaxy Note GT-N7000 Android Development] ThaiDai:
I do not really like the mixing of kernels from different sources here. In a german forum there was already confusion about "PhilZ new Kernel for XXLT4" which simply was the clone.

And now cleaning scripts for the other kernel. There is a simple solution for it: a new thread or no thread.
[Galaxy Note GT-N7000 Android Development] Phil3759:
It is a dev thread/forum in fact

Pushing so many updates is confusing.

I also ask you to open a separate thread and leave this one.

You are welcome though to post any tech/dev contribution

So, no more updates for custom kernels here
[Galaxy Note GT-N7000 Android Development] Phil3759:
Come on

My kernel is stock kernel, no need to clean anything

Your script just deletes recovery settings and a folder that doesnt harm but adds some getprop info. It is inactive once my kernel removed

So it cleans more Wakeup stuff than mine

Please, no longer any wakeup kernel posts here. Create a thread an try to start giving proper support, info and change logs...

Good luck
[Galaxy Note GT-N7000 Android Development] rraaka:
i really appreciate what you are sharing Klementy but also agree with Phill and Thaii.

share your options in general forum- you may discuss/update or not.....its up to you...support it as much as you can or not at all.

your english is good
[Galaxy Note GT-N7000 Android Development] ahhl:
can guide how to rename without root. ( as i got binary error, cannot update)
[Galaxy Note GT-N7000 Android Development] Phil3759:
So, it is not the place. This is the dev forum. There is a general forum for that. End of discussion about it for me
[Galaxy Note GT-N7000 Android Development] Phil3759:
The problem is that people are going to use it and you are not able to support it. This is a dev forum. Move to General thread please
[Galaxy Note GT-N7000 Android Development] lionelia:
I don't like to see that kind of discussion here, it's a waste of time and it don't helps in any maner...

Thank's PhilZ for your kernel, I use it and everything is just fine :good:
[Galaxy Note GT-N7000 Android Development] godmakarand:
same with me. and i am really thankful to this forum and philz for extending his knowledge into something practical, which we can use everyday without worry. i dont know why some people just want to use this thread for their personal ego boosting.
[Galaxy Note GT-N7000 Android Development] JosH-S:
Can i flash version in quote on stock 4.0.4 LRI unrooted ?
[Galaxy Note GT-N7000 Android Development] majdinj:
Those are JB kernels and LRI is ICS kernel!!!!
[Galaxy Note GT-N7000 Android Development] himuslg123:
AROMA FM

till now everything working great ..just the

aromafm link in philz setting in recovery not working

I have checked it

but its unable to find that ..always showing that the file is not present

aromafm.zip is in clockworkmod/.aromafm/

but still same error
[Galaxy Note GT-N7000 Android Development] :
Phil, Excuse me, if I slam my finger in the car door while doing a factory reset through abyss 4.2 on stock JB ICS Honeycomb will my note die or will it turn into a memo?
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
You need to download the file manager an place it in that folder.
[Galaxy Note GT-N7000 Android Development] Nodens:
PhilZ, could we get a LT4 release in the 17.04 folder? It's the only one missing with stock init.
[Galaxy Note GT-N7000 Android Development] Phil3759:
Shoey tested it fine, but you are on your own

I will do asap
[Galaxy Note GT-N7000 Android Development] himuslg123:
thanks for your help

but still its same ..placed the file there with appropriate name aromafm.zip :rolleyes:
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
it has to be placed in /sdcard/clockworkmod/.aromafm/
[Galaxy Note GT-N7000 Android Development] whitedavidp:
Cannot Download For LT4

I am trying to download PhilZ-cwm6 v4.93.6 with CWM 6.0.3.1 based recovery DDLSC - DXLSE - JPLSB - XXLSZ - XXLT4 - ZSLO2 Fixed for bootloop as shown on the first page of this thread. I click on the Download Folder link (that's all I see to click on) but I get sent to a page that says it is not meant to be accessed directly. Any idea what's happening? Thanks.

Edit - never mind. Seems I was having a browser issue. Thanks
[Galaxy Note GT-N7000 Android Development] mordauntlong:
download and install PhilZ-cwm6-DXLSE-OLB-4.91.2 instead,, i didnt have any issue or anything with it when i used it with JB DXLSE before.:good:
[Galaxy Note GT-N7000 Android Development] devll:
Download the 4.93.6 version which stats fixed for bootloops. using that and it works fine. :good:
[Galaxy Note GT-N7000 Android Development] chantik:
I've got bootloop too when using PhilZ-cwm6-DXLSE-OLB-4.93.6-signed.
[Galaxy Note GT-N7000 Android Development] devll:
Mine works fine. :confused::eek:
[Galaxy Note GT-N7000 Android Development] chantik:
What version ... XLSE too ?
[Galaxy Note GT-N7000 Android Development] devll:
Deodexed DXLSE-OLB. Singapore ROM. Philz DXLSE-OLB Lastest Bootloop Fixed. ;)

Everything works as normal. :D
[Galaxy Note GT-N7000 Android Development] GIO Tarakji:
what is the best for my devise ?

im new in this world ..

my devise is XXLSO

UAE V

Best Regards
[Galaxy Note GT-N7000 Android Development] Formhault:
So... On which kernels do you guys experience bootloops and on which kernels you don’t?

I take the kernels with modified init fix the bootloop, while the ones with stock init don't?

Sent from hyperspace
[Galaxy Note GT-N7000 Android Development] satyamsit:
I am on DDLR1 and want to flash LSC. which kernel shud I flash first before flashing the ROM?
[Galaxy Note GT-N7000 Android Development] pcarth:
Hi,

After removing the

busybox+su

binaries from /system, able to boot without the looping in samsung logo. :confused: No more root function now????. Any suggestion/advice to get the root option back. Attached the log extract from the kernel messages

/proc/last_kmsg

for debugging.

Thanks in advance.
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
how are you flashing the new rom? Odin? if yes there is no need to flash any kernel before flashing the rom
[Galaxy Note GT-N7000 Android Development] mordauntlong:
http://www.mediafire.com/?3cnf2ax9apsebefdownload this and copy to sd

you can flash this one from your stock recovery so you can safely wipe your ICS DDLR! before flashing LSC,after flashing LSC, download phils safe kernel for LSC
[Galaxy Note GT-N7000 Android Development] satyamsit:
@ phill .. phill can u check is this the right link for your kernel to flash on indian jb DDLSC or not.. kindly do .. i m getting reboot and stuck @ samsung logo..

http://www.mediafire.com/download.php?jy49jgobbcbco8z

---------- Post added at 01:57 AM ---------- Previous post was at 01:57 AM ----------

@ phill .. phill can u check is this the right link for your kernel to flash on indian jb DDLSC or not.. kindly do .. i m getting reboot and stuck @ samsung logo..

http://www.mediafire.com/download.php?jy49jgobbcbco8z
[Galaxy Note GT-N7000 Android Development] shoey63:
Recognized Developer eh Phil? Well done! 6 months overdue IMO:thumbup:
[Galaxy Note GT-N7000 Android Development] Formhault:
Congrats @ Phil and welcome back @ Shoey :D

Sent from hyperspace
[Galaxy Note GT-N7000 Android Development] pcarth:
Want to go back stock kernel due to boot loop.

Hi,

Please advice how to revert [PhilZ-cwm6][n7000] v4.93.6 kernel to stock Samsung N7000 JB kernel:confused:l. As my note have a boot loop and no solution available please help to get back to stock status.:( Also not able to get rooted again, want to go back.

Thanks in advance.
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
if you have an odin flashable rom that you have on the phone, the extract the zimage from it and flash it using mobile odin (/kernel)
[Galaxy Note GT-N7000 Android Development] pcarth:
stuck on samsung logo

Hi [MENTION=4677768]nokiamodeln91[/MENTION],

Thanks for the reply. Actually i have a problem in [PhilZ-cwm6][n7000] v4.93.6 kernel when note reboots after installing the 4.93.6 using "install from SD ". When note reboots back shows dialog "Android updating" and instead of loading the UI it reboots again. On that reboot, it stuck on the Samsung logo.Due to that, don't know whether to stick with v4.93.6 kernel or go back to stock rom kernel.

I tried to remove the "busybox+su" binary from the /system using a unrooting script. After that able to boot but without the root option :confused::(. now stuck without any rooting option as none of the rooting solution is working.

Thanks in advance.
[Galaxy Note GT-N7000 Android Development] rraaka:
next time when you have full root and if and when you are stuck after a reboot, or in a bootloop try getting into the recovery with three button combination and then go to advanced - reboot recovery and then reboot into system

try
[Galaxy Note GT-N7000 Android Development] pcarth:
Hi [MENTION=2933234]rraaka[/MENTION],

Thanks for the reply. Currently i have philz 4.93.6 kernel only ( no root). I tried the following steps.

1> flash from sd -> v4.93.6 again.

2> rebooted.

3> stuck in logo.

4> recovery mode (3 button) and selected advance->Reboot in recovery.

5> Rebooted and stuck in logo.

6> flash from sd ->unrooting script to remove busybox+su and reboot

7>Note loaded UI properly (no root support).

Still no change. :(.

Thanks.
[Galaxy Note GT-N7000 Android Development] Phil3759:
Are you on a custom ROM?

Do you have a superuser app in /preload?
[Galaxy Note GT-N7000 Android Development] Samsara69:
Hello and thanks (just for follow).
[Galaxy Note GT-N7000 Android Development] pcarth:
Hi [MENTION=643734]Philz[/MENTION],

* Singapore ROM - stock jb from Sammy.

* checked the /preload & no superuser.apk found.

thanks.
[Galaxy Note GT-N7000 Android Development] mordauntlong:
if your on stock,should try and look in system/app
[Galaxy Note GT-N7000 Android Development] pcarth:
Checked in /system/app & no superuser.apk. The unrooting script already removed the busybox /su/superuser.apk.

Thanks.
[Galaxy Note GT-N7000 Android Development] corsicanu:
download from market superuser or supersu and see what's telling you about root.. on my note after flashing philz kernel over alliance rom i got bootloop and after flashing second time and wipe cache/dalvik phone started with no root app.. the scripts i think were there because after downloading supersu from market i gained root back.. maybe you should try... who knows :)?
[Galaxy Note GT-N7000 Android Development] nokiamodeln91:
you could also try using an older version of philz kernel <4.90 to root and see what happens
[Galaxy Note GT-N7000 Android Development] Phil3759:
Never use third party cleaners. Mainly the busybox cleaners, they can lock your system killing many things

Anyway, either you killed something while cleaning busybox, or you still have a superuser apk around

Check also /data/app for any superuser app update
[Galaxy Note GT-N7000 Android Development] pcarth:
Hi [MENTION=4658360]corsicanu[/MENTION] / [MENTION=4677768]nokiamodeln91[/MENTION], thanks for the reply.

Hi [MENTION=643734]Philz[/MENTION], You are correct. The removal script removed busybox binary/su binary /superuser.apk. It looks like dead symbolic links in /system/xbin is still there for busybox.

Can i use ur ">Busybox Uninstaller (+600 files): http://xdaforums.com/show....php?t=1853419" to remove the dead symbolic links.

Thanks.
[Galaxy Note GT-N7000 Android Development] Phil3759:
Yes, sure, it will work, but if the installer you used hacked around toolbox links, you are stuck, unless you follow the last 3-4 pages from my uninstaller script

I never found time to add that fix to OP for people like you that messed with their toolbox. But, there is a script in the last pages of that thread