yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] wildalan:
ur right...we need someone who was bricked to tell us his experience and what was he did step by step
[Galaxy Note GT-N7000 Android Development] GocaS6:
So let's gather our knowledge...

The ONLY guy that hardbricked his device is Chasmodo right?

Few hundreds of people uses LPY ROM with CF Root kernel without any problems, right?

There's no proof that stock LPY has any issues, right?

It's pretty dumb to say that Samsung would release potentially dangerous kernel, right? I mean deleting large files will cause hard brick of the device? Are you kidding :cool:?

Secondly as i recall CM9 is based on SGS2 ROM and what good you can expect when you flash Note kernel on top if it? (and yes i know that CM9 is adopted to suit Note but maybe has few things to improve?)

I mean i respect Chasmodo of course but is it a time already to consider that it is simply his own fault or set of circumstances?
[Galaxy Note GT-N7000 Android Development] MR.change:
Reporting a near brick condition from official LPY ROM ,read my post:

http://xdaforums.com/showpost.php?p=25974632&postcount=55

so yeah ,steer clear of this kernel\ROM
[Galaxy Note GT-N7000 Android Development] toxicthunder:
Yes thus has been correctly stated. Icab personally confirm this as well. Majority of the problems are arising when users try to go back to GB from a Custom Rom and then upgrade back to ICS without following the proper procedures.

Ofcourse there are some tricky issues with regards to CF code and the latest LPY release but I am sure it will be sorted out very soon. But most problems I have come across arise due to users getting over-excited and jumping essential steps.

For the time being, I would advise lesser experienced users to show a bit more patience and wait for more news. We waited so long for this, why spoil everything by any rash act of impatience?
[Galaxy Note GT-N7000 Android Development] thay:
Flashed 2 gnotes with LPY chroot no problems all seems ok

How many bricks are reported at the moment? Seems only 1...
[Galaxy Note GT-N7000 Android Development] ykkfive:
@ESANEST

congratulation, man.

btw, i just have a thought. maybe we (you) can tell us what/which rom u r using, so we can figure out what is safe instead of what is unsafe?
[Galaxy Note GT-N7000 Android Development] ykkfive:
i agreed with u. but i bricked my phone before with the leaked roms when i was switching to cm9 (i built it myself), in the recovery, during formatting (very likely since it bricked so i couldnt have access to the phone)
[Galaxy Note GT-N7000 Android Development] satanduck:
thanks for the warning, better safe than sorry imho
[Galaxy Note GT-N7000 Android Development] mR.fR34ky:
no time to read all the commants but successfully reverted back to stock lc via pc odin then flashed speedmod kernel via odin to get root and cwmr. booted into cwmr format system, cache and data and installed checkrom. then wiped caches and installed jbdroid kernel wipeing script and then again installed speedmod kernel k2-12 from cwmr. Fineally got everything working! huhh
[Galaxy Note GT-N7000 Android Development] easycure1974:
I have been flashing Stock LPY, Alba several versions, and Stock deodexed with root several times, all using CF kernel bar the first Stock flash wich I rooted with evernote when flashing the rom from Mobile Odin.

Have been flashing, wiping and formated my storage at least 20 times untill now when I settled on Stock LPY with CF kernel and no problems what so ever untill this moment :) And I have not been back on GB kernels or roms.
[Galaxy Note GT-N7000 Android Development] npras42:
Im sorry, I understand that everyone wants to be "safe" but I feel this thread is a bit hysterical.

I have no problems with someone creating a thread and pointing out a potential serious issue, but it doesnt seem to be that well founded, so I think a warning to "STOP USING LPY CFROOT IMMEDIATELY" is over-the-top.

Only one person has so far had a problem... As I was feeling a little brave and don't really believe the fuss, I just wiped my phone (and booted) 14 times in a row (I was going for 20 but got very bored!) It still works fine. Came from GB LA1 XEU to start off using the normal instructions with MO.

I have previously used imilka's CM9 with the leak kernel (which I know and belive completely is not safe) and the official TeamHacksung CM9 with its own kernel.

Anyway, just thought I would post my experiences.
[Galaxy Note GT-N7000 Android Development] EdgaBimbam:
Hmmm my phone goes deep sleep with lpy+rooted kernel, however i flashed lp6 modem, because that lpy firmware modem was gay. Also came from rocket rom. Made full wipe even sd cards formats, flashed via pc odin LPY firmware, rebooted several times and then flashed cf root kernel and no problems so far. Smooth, bug free, good battery life ;)
[Galaxy Note GT-N7000 Android Development] GocaS6:
Yes exactly - before. That of course has nothing to do with XXLPY Rom, right?

I've got one simple advice for all of us flashers of XXLPY:

Flash it from full rooted GB and i believe that you'll not have ANY problems. No CM9 no chinese leaks no any chinese crap no anything that isn't original for this device!

That's just my personal opinion and i believe that it will eventually demonstrate proper. :cool:
[Galaxy Note GT-N7000 Android Development] Yucko:
well, you are talking about a leaked ROM while this is an official released ROM (which was also delivered OTA).

I like to think that even Samsung at least reads on XDA (as XDA can provide many info about problems and such things regarding ROMS, etc. etc.) and knows about the problems with the eMMC and made sure the ROM that was released to the general public is clean of the eMMC bug.
[Galaxy Note GT-N7000 Android Development] ykkfive:
right, nothing to do with lpy for me yet

btw, no cm9? why?
[Galaxy Note GT-N7000 Android Development] Kikasa23:
Had some input from me,

earlier today before this announcement i tried to flash the LPY deodexed rom by i9000 with cf-kernel using mobile odin. despite flashing succeeded, i wasn't able to boot into the phone itself.

1. Samsung Galaxy Note Logo flashes for about 10sec than screen off

2. managed to get into cwm and tried to wipe data, however it just hanged at the formatting cache step.

i took out my battery and inserted the usb jig, and was able to get into download... flash a stock gb and this time i thought of retrying with the stock LPY instead this time. Flashed with mobile odin and viola, every thing works... i even into cwm to wipe data, cache, dalvik cache, battery stats few times for customisation, no issue so far. Till i chanced upon this thread.

Anyway, i having been reading on this subject for the past 1 hour, so i think maybe this guy use the kernel or modem from the deodexed rom instead of stock LPY?

*Anyway i'm just a normal user, ain't no developers :)
[Galaxy Note GT-N7000 Android Development] beestee:
I have a +1 for this, but simply as a precaution until the bug is either

(a) disproved or

(b) proven and stamped out

I will not make intentional file movements or use of CWM.

It seems that if this issue is real, then the safest thing for those on LPY to do is remain on LPY, avoid CWM and avoid data movement. It also seems that the worst idea right now is to move back to GB as that is a tempermental process in and of itself and typically requires a factory reset which is known to be dangerous from the previous unofficial ICS debacle if this issue proves to be real.

I did a factory reset from CWM just for good measure before this became an issue. I had zero problems before, and now have zero problems after. I am very lightweight right now with 18 downloaded apps total and my biggest installed non-Gapps non-preinstalled app being Apex Launcher at 3.07 MB. I have not had the charging issue, and I am currently at 94% battery after nearly 7 hours off of the charger. Everything runs unbelievably smooth.

To give a bit of my history with updating on my note, I have always used official stock ROMs with CF-Root kernels and my move to LPY was from official LC1 with CF-Root kernel utilizing Mobile Odin Pro with Everoot plus injections, my typical procedure.
[Galaxy Note GT-N7000 Android Development] ahalford:
So, lp6...it strengths my suspects regarding lpy modem. Thanks!
[Galaxy Note GT-N7000 Android Development] GocaS6:
Because i explained it before, CM9 for Note is based on SGS2 ROM and it isn't original for this device! And who knows what's happening in system when you flash Note's rooted kernel on SGS2 based ROM :confused:

And Chasmodo as i understood was on CM9 when he tried too flash CF Root kernel (LPY) on CM9.

So people let's calm down a little bit with all this warnings :cool: i mean maybe just maybe is something of this true but currently there's 0 (zero) evidence for that.
[Galaxy Note GT-N7000 Android Development] robertberma:
Can not believe there are people who flashed this from a chinese crap kernel. Mine stock rooted ics run very good.
[Galaxy Note GT-N7000 Android Development] ESANEST:
Ginger XCL1 oficial rooted, previous flash with mobile odin. Before KingDroid Ginger.

I think if you no change base ROM (cm9,aosp...) Example- no problems.

Sorry for my English poor xddddd

Salute

Enviado desde mi Galaxy Note desde la punta del S-pen usando Telequinesis
[Galaxy Note GT-N7000 Android Development] ykkfive:
nvm, as i said, this is just a warning. what worried me is the post from cf i quoted, and the post from Entropy512, for:

- cf is commonly used

- chainfire himself made this serious alert

- Entropy512 were informed about 'OTA update of ICS is affected'

as i result, after waiting for a few minutes and still no relevant posts, i decided to alert all ppl here for their own benefits, but not mine, since i believe they should be informed especially many ppl comes here for downloading roms only
[Galaxy Note GT-N7000 Android Development] robertberma:
Very stupid but brave.
[Galaxy Note GT-N7000 Android Development] easycure1974:
No problems at all with rooted stock LPY and included modem and deep sleep
[Galaxy Note GT-N7000 Android Development] ahalford:
Thanks..

Let's keep posting, there is the way to find communality.
[Galaxy Note GT-N7000 Android Development] ykkfive:
oh yes, thx for reminding me, i yet to read that post
[Galaxy Note GT-N7000 Android Development] GocaS6:
I'm just waitin for your "smart" opinion or explanation? If you have any?

I guess not, you just love to wrote stupid posts on the forum right? :cool:
[Galaxy Note GT-N7000 Android Development] ykkfive:
i'm on deodexed lpy with cf root, from cm9 v7
[Galaxy Note GT-N7000 Android Development] DominionZA:
I flashed LPY yesterday via PC Odin. Was on CM9 #7.

Device would not move past boot screen. Waited 20 minutes.

So flashed CF Root via PC Odin. Afterwards I booted to CWM, did a full wipe and reboot system.

Everything 100% since.
[Galaxy Note GT-N7000 Android Development] npras42:
Beleive me when I say this is NOT a personal attack or anything. The topic is relevant and important but I think the warning can be toned down a bit.
[Galaxy Note GT-N7000 Android Development] GocaS6:
And i was saying about :cool:...
[Galaxy Note GT-N7000 Android Development] beestee:
For reference in helping others potentially avoid softbrick, what ROM/Kernel were you flashing from to get to LPY? This seems to be important/relevant.
[Galaxy Note GT-N7000 Android Development] andywright1982:
I was on litening 1.0 and then flashed via mobile odin yesterday with the full rom and chainfires kernel. No wipe

So far no problems at all and phone goes into deep sleep. 24 hours turned on and less than 50% battery used.

I am not going to do anything via CWM or change rome, but so far no probles experienced.

I have never had any chinese/cm9 rome on my note either.

Hope this helps
[Galaxy Note GT-N7000 Android Development] X-Files:
I have a problem with new firmware.

When phone is connected to Car Dock and if somebody call's me, then note freeze and popup the text: Killed ...android.com
[Galaxy Note GT-N7000 Android Development] E90 Commie:
I flashed the LPY and CF-Root from Criskelo V2 LP6 without any problems.

The kernel was LP6 when I did it but Mobile Odin uses its own kernel for the flash so the leaked one wasn't involved in the process.

I haven't noticed any problems with the CF-Root LPY either despite doing factory reset and Dalvik wipe with it.
[Galaxy Note GT-N7000 Android Development] ykkfive:
no problem, my english is not very good but i got what u mean, at least this time

i just went back to your old post and wanna reply you with a quick question:

i am not good at english since it's not my main lang, so can u pls give me some suggestions for the post title, so that it sounds better?
[Galaxy Note GT-N7000 Android Development] ahalford:
I started from flashing pre-rooted lc1 wipe ROM, then lc1 cf-root 5.3 Gb kernel, then lpy ROM through mobile Odin with cf-root lpy kernel .
[Galaxy Note GT-N7000 Android Development] andywright1982:
I would change it to

WARNING - Possible issue with LPY ICS upgrade. Please read
[Galaxy Note GT-N7000 Android Development] dragonnis:
It's sad how many people have bricked their gNotes of late. I don't get why regular users (by which I mean non-developers) don't wait a week or two till the amazing devs have had a chance to sort out any issues and confirm there's nothing wrong... especially after the whole leaked ICS bricking fiasco. Although I guess people wouldn't suspect the official OTA...but still...:p
[Galaxy Note GT-N7000 Android Development] ykkfive:
i have to admit that this is a better one. mine is too strong perhaps

thx

EDIT just chg'd the title, hope it's better now, thx again :D
[Galaxy Note GT-N7000 Android Development] lingamkrishnan:
My note was running on Chrack's rom v18 small LC1 with franco kernel 10.

I flashed the ICS LPY and CF KERNEL using Mobile Odin Pro..first time, the note was stuck at samsung logo..so did factory reset and did wipe cache. then note was booting okay.

But Since ICS LPY, Google play is throwing an error "google stop stopped unexpectedly" and Seems i lost the root access(can't paste anything system folder) also Note is not going into deep sleep :(

Any help on this? should i stay on this ICS ROM or go back to GB? please advise.
[Galaxy Note GT-N7000 Android Development] hykhleif:
so why don't we just get more info from chainfire, and is he still holding up to his post about the warning

i am so confused and i am sick and tired of flashing and flashing in hopes of a stable dam ICS rom for me note.

now what, will there be more ics updates besides the german one.

i still don't understand is it the kernel that caused this panic, if yes then chainfire would be the best to give us his final verdict
[Galaxy Note GT-N7000 Android Development] Jade Eyed Wolf:
I'm wondering if my Note has been affected by this bug... PC Odin fails to flash anymore now. No matter what kind of ROM (stock or otherwise) I try to flash, it'll get to "NAND Write Start!!" and will fail "Complete(Write) operation failed."

I'm unable to get back to stock GB, or stock ICS. My bootloader is back to stock 3e, so CWM isn't an option (unless there's an update.zip out there that flashes the CWM bootloader). Can a JTAG recovery possibly fix this issue?
[Galaxy Note GT-N7000 Android Development] praetorius:
Bah, flashed both my note to the latest ICS flavor today but at the end, decided to revert back to GB for safety reasons.

Imho, these so called "kernel bugs" may actually be a feature incorporated by samsung developers to discourage people from tinkering with the /system folder specifically.

Zapped through server hops to XDA forums
[Samsung Galaxy SL i9003] loukalok:
hi

anyone who have blacklight issues in aosp rom pls reply here....

let us know how many users have the blacklight:D:D:D

thanks

EDIT(Out date):

Temporary method:

By:arindammanidas

NOTES:

* Flash it using CWM from the Internal SD card (Turn off Signature verification).

* Flash over a clean CM7/MIUI.

* Please remove any backlight killer apps you might have installed.

* Disable screen-on animation if you have enabled it.

* Please do not mirror the files.

THANKS:

* Vurrut for his Kernel sources. :)

* The i9003 devs/ex-devs and the community. :)

CM7/MIUI

CM9

EDIT:

Arindam is finally full fixed the blacklight here:

Hi,

I guess I nailed it!!! Please test the following kernel and report. And just to be extra sure, check your governor and set it to ondemand. Also charge your battery fully and check battery drain.

Download: ArindamKernel-CM9-v5

Flash using recovery. Kernel version should read #5.

Also don't forget to wipe cache and dalvik cache.

P.S.: This is for all people regardless of the backlight issue.

If this works correctly then I'll release new kernels for CM7/MIUI as well.

CM9 V5
[Samsung Galaxy SL i9003] Gondya bhau:
either many ppl dont check the general thread or most people dont have this problem(most probable ans)...anyways there is already some kind of a list in that backlight fix for CM7 by arindam...why start another thread ????
[Samsung Galaxy SL i9003] loukalok:
but the kernel is not really fix the issues
[Samsung Galaxy SL i9003] bscraze:
No offense but I think this thread is useless. Dhiru already knows about the black light issue and since so many people have posted about it he is trying to fix it now, just go to the irc chat and he will provide some test kernels. Like vishal said in the dev thread, ask him when he'll be on.

Cheers:)

Sent from my GT-i9003 powered by Stable and Smooth CyanogenMod 9!
[Samsung Galaxy SL i9003] loukalok:
but i ask dhiru in irc..

no answer
[Samsung Galaxy SL i9003] vishal24387:
xdaforums.com/showpost.php?p=26039819&postcount=1587

Lets see...hope UC team will help us.
[Samsung Galaxy SL i9003] arifanwar:
Backlight issue

Hi Guys,

Just wanted to add my name to the list of people who are facing issues with Backlight.

I was on Dhiru's ROM and had to remove it because of the annoying backlight issue.

Just hope we have a fix soon.

Just to let you all know I tried Miui V4 B4 from Frank and have no backlight issue there, yeah the camera doesn't work, but I guess I am fine with it :)

Regards

Arif
[Samsung Galaxy SL i9003] vishal24387:
Guys I am on xxkpq. Can u tell me how to ckeck screen panel???
[Samsung Galaxy SL i9003] loSconosciuto:
From terminal emulator

dmesg | grep current_panel

You should get something like

[ XXXXX] [LCD] nt35510_panel_probe() : current_panel=[COLOR="Red"]X[/COLOR] ....

See the number (here in red)

0: Sony

1: Hitachi

2: Hydis

3: SMD

4: Sony(a-Si)

5: Hitachi

EDIT: I think we can only decrease the buffer. See this: http://xdaforums.com/showpost.php?p=26094468&postcount=11

____

If you don't have that line in dmesg output, it means that you have to increase the buffer size:

dmesg -s [COLOR="Red"]XXXXX[/COLOR] | grep current_panel

Where XXXXX is the buffer size. Use a large number, for example with 500000 I can see it, but it depends on how long your phone is running. That said, if you reboot the phone you don't need to change the size of the buffer, just type the first command I gave you.
[Samsung Galaxy SL i9003] vishal24387:
I run this command but I am not able to see any output :(

dmesg | grep current_panel
[Samsung Galaxy SL i9003] loSconosciuto:
I think we can only decrease the size of the buffer.

Anyway, try to reboot the phone or try this one

cat /proc/kmsg | grep current_panel

You should get the same output.

With this one you don't need to reboot the phone, but you can use it only once, then you need to reboot or find where kernel log messages are (I don't know where they are on Android)

Try to run them as root (type "su" and then the command)
[Samsung Galaxy SL i9003] vishal24387:
after reboot this worked for me & look guys what I got...! I come to know that my panel is sony :(:(:(:(

I have never switched to aosp roms because I need daily camera alot which aosp roms lack. Anyway count me in future blacklight problem candidate.
[Samsung Galaxy SL i9003] loukalok:
But the vurrut ics kernel is not fix the bug
[Samsung Galaxy SL i9003] holigan360:
no, I have installed and does not correct the error

---------- Post added at 01:02 PM ---------- Previous post was at 12:48 PM ----------

I run these commands with root and nothing comes out in the terminal

How do I get it?
[Samsung Galaxy SL i9003] vishal24387:
reboot ur phone & then try...!
[Samsung Galaxy SL i9003] loSconosciuto:
Or try with 'cat /proc/kmsg | grep current_panel'.

Another method to see the panel is:

dmesg | grep poweron

and you should get something like:

[ XXXXX] [LCD] nt35510_ldi_poweron_hitachi() +

(no reboot needed with this one, if you can't see it you just need to turn off and then on the screen)

Anyway I don't know if Sony panels are the only ones with the problem. As you can see from my previous message, our phone is shipped with different panels. This thing "Hitachi vs Sony" came up when I compared my dmesg output with crk1995's one and I noticed that we had two different panels, but few users posted their log here.

It would be better if other users check their LCD panel, just to confirm that only Sony panels are the ones with this problem.

EDIT:

I've just remembered this old message, maybe someone could take a look at that: http://xdaforums.com/showpost.php?p=24628254&postcount=35
[Samsung Galaxy SL i9003] holigan360:
I just did the test and I get this:

[78.542999] [LCD] nt35510_ldi_poweron_sony

[78.951324] [LCD] nt35510_ldi_poweron_sony

[480.024353] [LCD] nt35510_ldi_poweron_sony

[480.440155] [LCD] nt35510_ldi_poweron_sony

some help to solve this problem? thanks guys
[Samsung Galaxy SL i9003] arindammanidas:
wait for my kernel:)
[Samsung Galaxy SL i9003] loukalok:
You have doing a new kernel??
[Samsung Galaxy SL i9003] vishal24387:
just for reference check this

xdaforums.com/showpost.php?p=26155278&postcount=96
[Samsung Galaxy SL i9003] holigan360:
out waiting for the kernel to solve the problem Blacklight MIUI was solved also hope that with CM9
[Samsung Galaxy SL i9003] arindammanidas:
yes vishal... the backlight bug is ROM related. Even Dhiru said so... that's why it doesnt occur on stock ROMs. My patch is just a dirty hack until Dhiru fixes it in the CM9 sources.
[Samsung Galaxy SL i9003] vishal24387:
I think we will get this solution in aokp rom. As they dont have blacklight issue we can apply that solution in aosp cm9 rom of Dhiru.
[Samsung Galaxy SL i9003] holigan360:
How to apply this solution in CM9 rom?
[Samsung Galaxy SL i9003] arindammanidas:
That's Dhiru's job :p:D
[Samsung Galaxy SL i9003] crk1995:
Aokp carbon does have black light issue...Don't be in illusion..

It might be an exception..

By the way Dhiru is planning to release a patch which is intended to fix this issue...
[Samsung Galaxy SL i9003] arifanwar:
Back light issue

I was facing backlight issue with CM9 Alpha 4 so I had to leave it then did a clean installation of DDKP3 and installed [AOKP] [ICS] CARBON B36-rc1 (4.0.4) and interestingly there is no backlight issue.

Battery back up is decent with 2G mode.

Till we get another version of CM9 with backlight fix I think I would stick to it :)
[Samsung Galaxy SL i9003] holigan360:
Really? for I will try. What have you sony or hitachi panel?

I can spend the firm DDKP3 please? can not find it and not let me download samfirmware I have to have premium account. thanks
[Samsung Galaxy SL i9003] arifanwar:
It really doesn't matter what panel you have, check dhiru's blog you would find that some people with sony panel have issues and some don't even dhiru has a sony panel and he has no backlight issue.

so its a firmware issue, to me it looks like that when you flash on DDPK3 base it works fine.

you don't need to have premium account to download rather use sammobile and all you need is a normal account, I can't post links as I need to do 10 post :)

Press thanx if this helped you.
[Samsung Galaxy SL i9003] holigan360:
anything updated to KP3 and even with the problem of black light, waiting to be told
[Samsung Galaxy SL i9003] arifanwar:
Didn't quite get your question ?

If you mean that after installing ddkp3 any additional patch needed the answer is no.

Just root after ddkp3 and flash carbon using cwm along with gapps and you are all set !