yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] eRode:
R3 installed using Mobile Odin. Read the OP, the ROM carries recoveries (R1 didnt).

What's the point of implementing the "MMC_CAP_ERASE" fix if it still doesnt allow safe flashing/wipe/restore? I'm very keen to hear your logic on that.

As an update, brought the bricked phone to the local (HK) Sammy service centre and they had it fixed within an hour by replacing the main board....230 euros later i'm back in business, with the knowledge from the engineer that it was indeed a hard brick.

I paid for my mistake, and am not complaining, I'm not sharing my grief with others on bricking given it was my own decision.

But what I'm sharing is that this MMC_CAP_ERASE fix is not golden. Those that repeatedly post "how do I flash this" should stay away for your own good if you have to ask that level of question.

---------- Post added at 11:54 AM ---------- Previous post was at 11:49 AM ----------

If you read a little more closely PC Odin wasnt able to write to the device like I said.

Same result with a manual adb push (InitialCFRootFlasher) method.

I've been using linux for almost 20 years now since i was a high school student and hold a doctorate in CS, not saying that earns me the right to report a brick but crying wolf and discrediting the alert doesnt really do the community a favour other than to give false confidence to others.
[Galaxy Note GT-N7000 Android Development] frankcilo:
Do you use tegrak overclock?

If yes, it is not compatible with this kernel
[Galaxy Note GT-N7000 Android Development] jonpaslim:
Use the mobileodin pro. Flash this kernel r3 by unzipping it, you get z image then flash it in mobileodin. I use this method in my note with lp9. Because of erode warning dont wipe or reset.
[Galaxy Note GT-N7000 Android Development] debernardis:
I tried your steps, wifi on-off, but got no reboot.
[Galaxy Note GT-N7000 Android Development] stekarson:
No wifi-problems with r3 and TheMIDTeam 1.4! :-)
[Galaxy Note GT-N7000 Android Development] Elmar1801:
I can do this multiple times without any problems on lpy rom.
[Galaxy Note GT-N7000 Android Development] aussiebum:
Thanks for trying guys, just found what the problem was.

franco r3 + Tegrak O/C Module = Wifi reboot bug :/

I was kind of surprised that Tegrak's O/C module actually loaded in the first place. Oh well, no undervolting for now then.

---------- Post added at 10:10 PM ---------- Previous post was at 10:09 PM ----------

Yeah I just found out myself thanks. Normally wouldn't have expected his O/C module to even load but it did.
[Galaxy Note GT-N7000 Android Development] musashiro:
thanks buddy, pressing the thanks button is not enough for this feat. stay on GB like me and wait for further investigations...

one thing is for sure : MMC_CAP_ERASE is not the "silver bullet" for this bug. devs or better yet, SAMSUNG, should consider other factors,

but again, we can't blame kernel developers for this bug, i will bet that samsung should absorb all the blame..
[Galaxy Note GT-N7000 Android Development] Sharespeare:
Fantastic Kernel, thank you for your work ;-)
[Galaxy Note GT-N7000 Android Development] Elmar1801:
Tested usb otg and it's working fine with r3.
[Galaxy Note GT-N7000 Android Development] debernardis:
Another thing that seems not to work in the updater (version 2) is the custom boot animation. Even if something gets downloaded from the internet, when rebooting the animation is still stock.
[Galaxy Note GT-N7000 Android Development] E90 Commie:
I have the impression that Nandroid restores is troublesome on a couple of kernels. If a device "bricks" during such a restore, that doesn't mean that the kernel itself is dangerous during a traditional flash/wipe. In that case, all kernels that fails to produce a working Nandroid restore could be labelled as brick prone ones and that includes GB too.

There is a reason why common recommendations (even during the GB era) has been to flash a kernel like Abyss 3.9 Redpill and do the Nandroid rather than using [insert kernel of choice]. The common bricking and the one that should be blocked with removal of MMC_CAP_ERASE is the wipe brick, i.e wipe data/factory reset from Settings, stock recovery or CWM.

Since this Franco kernel has the MMC_CAP_ERASE disabled, it is a safe kernel for ROM flashing and wiping, the Nandroid issue is unrelated and shared with a couple of kernels.

Edit: Since the nandroid restore issue is common, I would say that "brick alerts" is more relevant for bricks occuring during wipes, i.e when the device is left with a dead /data or /system with factoryfs fail during flash. THAT is the brick. If someone bricks the device with this kernel, i.e WIPES and then is left with a dead /data or /system partition followed by the failed Odin flash (stucks on factoryfs) - then it is time to issue a brick warning.
[Galaxy Note GT-N7000 Android Development] marcus70:
good to hear that,using tmt 1.4 oso, been refraining from flashing r3 due to the wifi problem as stated
[Galaxy Note GT-N7000 Android Development] grgsiocl:
no wifi problem for me too ....may be problem ROM related!
[Galaxy Note GT-N7000 Android Development] Goodm7sn:
I ended up reflashing a non wipe lpf firmware via mobile Odin + selecting franco's zimage file as the kernel + keep root checked..

flashed them all together and now wifi works perfectly and connects automatically like it used to..

Hope this helps people with wifi issues.

Cheers
[Galaxy Note GT-N7000 Android Development] REVERSiN:
It's a perminate fix this is only for now as all review its fine to wipe with it just be carefull and take responsibilty you always can flaah a kernel reboot recovery wipe then flash the ics kernel again and done....

MMC_CAP_erase isn't the only issue, as the expert answered to the questions you can write zero's instead of using the function for this it's a total work around that should be implemented I guess this is the best option for now and btw its google's fault too not just samsung devices so I've heared :/

Badass bug that can't be undone yet, a little longer dev will delete related files probably implement a new wipe method and override the function itself or best for now is disabling the wiping option so that none would do a mistake and wipe with it.
[Galaxy Note GT-N7000 Android Development] sangalaviral:
As Mr. Sumrall says its not just Kernal bug, there is a bug in CWM too.

---------- Post added at 07:01 PM ---------- Previous post was at 06:59 PM ----------

Google fixed the bug even before the launch of galaxy nexus. It is samsung who is not ready to fix the bug.
[Galaxy Note GT-N7000 Android Development] franciscofranco:
I never said erasing MMC_CAP_ERASE was a final fix. It's just a workaround suggested by Entropy so you'll all still flash/wipe etc on your own risk.

On another note it's nice to see that the kernel is behaving so well seeing from this initial feedback. It leaves me a lot more free time to implement some ****s in the application and allows me to think about a few implementations that I want to introduce in the kernel.
[Galaxy Note GT-N7000 Android Development] rogconnect:
I am using Midteam 1.4.2. flashed r3 with CWM. Then used the jBroid_Kernel_Cleaning_Script_Ed-1.zip.

The first boot seem to hung. Then rebooted it, and every thing work fine. No wifi problem on 5G connection. Turn On and Off most of the time. I have Antutu CPU Master Pro too, but didn't touch the setting. Battery life is good and run much smoother.
[Galaxy Note GT-N7000 Android Development] sangalaviral:
There is bug in the CWM 5.5.x

If you can have a look in that too
[Galaxy Note GT-N7000 Android Development] LOulOo:
can not connect to wifi after flashed zimage throught mobile Odin.

Wifi still stays "obtaining an IP adress" but can not connect.

i flashed back stock LPF kernel with Odin PC and wifi connect normaly :(

PS : i'm running stock OZS LPF rooted (without cf-root because it's the same, no more wifi..)
[Galaxy Note GT-N7000 Android Development] marcus70:
thks already flashed this great kernel,no wifi problem oso...
[Galaxy Note GT-N7000 Android Development] frankcilo:
Good morning francisco, how I can reduce voltage of cpu?

Francokernel app have bug....
[Galaxy Note GT-N7000 Android Development] sotmax:
That was what about to say.

Franco never wrote that the bug was fix but only that there was a workaround for fix.

So ppl have to stop spreading wrong things.

One said kernel bug fix and another brick.by that kernel.

Come on guys it s all about YOUR OWN RISK.

Respect devs and their work.

If you want flash it if you dont want dont flash it.

For the specific kernel all i can say is congratulations to Franco for his great job.

Is.performing well, wi-fi connects fast and it have very good battery performance.Also it is much faster n smoother than cf s kernel(wich is stock but with root n cwm).

Anyone with bugs first check md5 and after that if the installation is correct.

Some ppl here spend hours for you so stop complaining...

Regards

Sotiris

Mobile phone technician/engineer.

) ) ) over the air on Galaxy Note ( ( (
[Galaxy Note GT-N7000 Android Development] DJ-Tumor:
I´ve heard of such strange behaviour.

Try changing the wifi-channel to 6 or 8.

Other than that im running the kernel on a rocket rom v2 without any problems tough not having tested everything yet.

Antutu shows CLEARLY new highscore of 7040 point which might state that the kernel offers some serious speed ;)
[Galaxy Note GT-N7000 Android Development] sotmax:
For anyone with problems(perhaps related at 95% on installation) do the following.

Boot into recovery manually (3 buttons).

Wipe dalvik cache n cache partition.

Flash kernel without fear(bug is for restore,meaning nandroid menu, not flash).

Wipe one more time wipe cache n dalvik cache.

Fix permissions.

Reboot n enjoy.

After that you can maybe blame kernel.....

) ) ) over the air on Galaxy Note ( ( (
[Galaxy Note GT-N7000 Android Development] Anonymous Vagrant:
What does Fix permission do? when u mentioned wipe one more time, does it mean wipe data follow by wipe cache n dalvik? correct me if i'm wrong
[Galaxy Note GT-N7000 Android Development] debernardis:
@franciscofranco: could it be possible in your future versions to enable swap on partitions or loopback devices?

This could be useful for running those gnu-Linux distros like ubuntu in a chroot; the possibility to swapon could give more ram to the chrooted system and ameliorate its performance.

Thanks :-)
[Galaxy Note GT-N7000 Android Development] motumbo:
Have you tried clearing out RAM from task manager? I think memory management is not very efficient on ics, maybe our device ram capacity is too low for this OS.
[Galaxy Note GT-N7000 Android Development] REVERSiN:
Well yeah they did but the base is from google a wrong use may trigger this, anyway they fixed it but looks like not permenatly samsung's sources has it its the same as google's just a few more tweaks probably bull**** nothing that helps .

CWM has no bug never did its just the way it uses those functions that gives false behaviour so we call it I guess.

Fo now fran.. did a good job disabling but its for now I mean we can't reflash other kernels to wipe for eternity.... nosense
[Galaxy Note GT-N7000 Android Development] Latoc:
Wipe is always from recovery, since only recovery can wipe...

Even when done from settings, the phone reboots to recovery THEN wipes.

The recovery screen is hidden from view when done from settings, that's all.

A wipe is a wipe.
[Galaxy Note GT-N7000 Android Development] franciscofranco:
Loopback devices is always enabled for every Android kernels. Swap... Im gonna have to think.
[Galaxy Note GT-N7000 Android Development] sotmax:
The only wipe that you can do safe is cache partition n dalvik cache...only.

Fix permissions is under advanced and you have to do it by my opinion everytime that you flash something outside of the rom installation.

After rom installation only there is no nesessary to do that because the updater script do that for you....

) ) ) over the air on Galaxy Note ( ( (
[Galaxy Note GT-N7000 Android Development] garyd9:
Wifi on or off? Any mail polling or pushing going on? Any services running and signed in (such as skype, google+ or talk, facebook, etc?) Strength of mobile signal?
[Galaxy Note GT-N7000 Android Development] Chillz88:
I think ys222 meant he just lost 3 percent of battery in 7hrs....:)
[Galaxy Note GT-N7000 Android Development] garyd9:
I understood that. If his phone was in airplane mode with absolutely nothing running, that would be horrible. If the phone was polling 4 email accounts every 5 minutes, had wifi turned on (but not connected), skype logged in and facebook going; then that would be incredible.
[Galaxy Note GT-N7000 Android Development] garyd9:
Wow... so that was a very interesting test. Seems that offlining exynos cores doesn't do anything whatsoever. Nothing at all.

Here's the test and results:

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

Gary
[Galaxy Note GT-N7000 Android Development] franciscofranco:
There you go, I wasn't crazy!! Good to know =) I'll do a more in-depth reading in a bit and comment it properly, but thanks for taking your personal time for those tests.
[Galaxy Note GT-N7000 Android Development] garyd9:
Never assume you aren't crazy. I thought that once about myself. Then I got married and had two kids. Thank God I really AM crazy.. or I might lose my mind. ;)

Oh, and don't thank me. My intention was to "prove" to you that disabling core hotplug was a bad idea. (...and now I have to eat my own words.)

I'm still in shock that offlining cores on the exynos offers no power savings whatsoever. Samsung screwed something up... Either the hardware isn't working, the kernel code isn't working, or the kernel code (written by samsung) is offlining a processor when it doesn't have any impact (which is also a fault.)

Take care

Gary
[Galaxy Note GT-N7000 Android Development] franciscofranco:
I'm pretty sure its the whole hotplug action that isn't well implemented. I've read Russel King saying that hotplug was broken and extremely unstable and not viable yet. Having read that, tried myself to implement a dynamic hotplug to a TI device and seeing my Note dmesg being swarmed with on/off messages I'm pretty sure it's broken like hell.
[Galaxy Note GT-N7000 Android Development] Caillin:
I don't think your nuts. It definitely feels more sensitive to me. I hand write very lightly and the pressure needed to get the s-pen to register always used to be just that small amount too heavy to make it slightly annoying to use. Now it writes perfectly with my normal pressure.
[Galaxy Note GT-N7000 Android Development] vuidoi:
Perfek kernel franco 2. I can't question anything. Thank so much franco
[Galaxy Note GT-N7000 Android Development] afilopou:
Hi Franco,

Did you have time to check my logs?Is app related the freeze?I also have battery drain and with the same setup with hardcore kernel i dont see the same battery drain.

Thanks a lot and congrats for your work
[Galaxy Note GT-N7000 Android Development] [David]:
I was waiting for night CPU beheviour 'cuz with AbyssNote 3.7 I saw CPU sleeps not for the whole time I slept too!

And here we are, Sleep time of my CPU during this night (in charge) 0 sec :(

Don't know why 'cuz it slept yesterday evening... Maybe charging won't sleep? :(

Thank You again Franco

Sent from my Galaxy Note with ROMOW 5.1
[Galaxy Note GT-N7000 Android Development] Chillz88:
Cpu wont sleep when your phones on charge mate... It goes to the lowest voltage when on charge and on screen off. There is nothing wrong with your phone...:)
[Galaxy Note GT-N7000 Android Development] robertberma:
I got fps score of only 37. Is that not little low? With abyss 52.
[Galaxy Note GT-N7000 Android Development] [David]:
Allright dude, device starts sleeping since I pull charger off, BUT I was meaning with AbyssNote 3.7 it did ;)

There's not a problem anyway thank You again

Sent from my Galaxy Note with ROMOW 5.1
[Galaxy Note GT-N7000 Android Development] gee2012:
Best kernel i tied so far, so far had no sod. Temperature is really good (17 celsius in idle). Real responsive, smooth and no stutters.

Keep up the good work :)
[Galaxy Note GT-N7000 Android Development] g4ndr1k:
Indeed. This is very excellent kernel.

Mine in idle is 31 C, which is okay since the ambient temp is 29 C :)
[Galaxy Note GT-N7000 Android Development] skerk:
If we look at it from the angle that Samsung tried to make a superefficient idle mode instead of streamlining the hotplugging? Couldn't that be a whise design choice?

Since hotplugging more or less always have to save away data when shutting down a core, and then when resuming load up at least some data again. Aka shutting down and starting up a core will always use X amount of cycles.

I'm no kernel coder so I might be out on a limb here, just tell me to shut up if that's the case. :)

Also a most humble request, would it be possible to get your kernel in mobile odin flashable format?

Thank you for your excellent work!
[Galaxy Note GT-N7000 Android Development] franciscofranco:
Kernel app for the Galaxy Note https://market.android.com/details?id=com.franco.kernel.note

=)
[Galaxy Note GT-N7000 Android Development] Cr4z33:
Does it mean that the future releases of your kernel won't be free anymore? :(

I was going to consider to give it a try.
[Galaxy Note GT-N7000 Android Development] eliashadow:
Nope...but if you have the app you can have the updates without looking here all the time..;)

And of course you can change some important settings.
[Galaxy Note GT-N7000 Android Development] jermitano:
cant seem to understand why some find it hard to read a simple and fine print...any how the dev of francokernel is still for now the fastest here, which is greatly appreciated...

ps...can the sql defrag be pushed on the next release to on activated on booth?thanks mate...
[Galaxy Note GT-N7000 Android Development] globalm:
Can you clarify that you mean that kernel that bricked your phone was Franco R3?
[Galaxy Note GT-N7000 Android Development] debernardis:
Thanks; I was thinking of swapping on a loopback device, not enabling the latter :cool:
[Galaxy Note GT-N7000 Android Development] GocaS6:
I'm glad that you know what are you talkin about, there's lots of people here that would flash anything and report as a mistake.

I'm sorry for your phone and i'm glad that you solved your brick, i guess your example shows that indeed this "fix" isn't what we all expected to be :(..

And you're rightt - Those that repeatedly post "how do I flash this" should stay away for your own good if you have to ask that level of question.
[Galaxy Note GT-N7000 Android Development] M3TALLICA:
I was trying to deodex stock rom, something went wrong and I was stuck at SAMSUNG.

Performed data wipe/factory reset... phone is still up.

No superbrick :)
[Galaxy Note GT-N7000 Android Development] jgaviota:
To all of those panicking

No One Has Bricked From Wiping In R3 yet

That is what the workarounds fixes, the bricks from wiping/factory reset.

Is it totally safe? Nothing really is. Wipe at your own risk.

What the previous warning is about is: restoring a nandroid bricked his device.

Never has it been said that the MMC_CAP_ERASE workaround was for nandroid restores.

So, don't restore a nandroid.
[Galaxy Note GT-N7000 Android Development] LOulOo:
i have tried 2 times, because i had not red all the topic, :rolleyes: , and nandroid restore failed 2 times, stay all the time at "restoring system".
[Galaxy Note GT-N7000 Android Development] Entropy512:
eRode may already have had existing damage - see all the people blaming PC Odin for causing bricks when it was a symptom.

Or he accidentally thought he was on R3 but actually did the restore from CF-Root.

Now a report of someone who was clearly running R3 (as opposed to "I flashed it and immediately did a nandroid restore without confirming that it flashed properly) and then bricking when wiping would be interesting.
[Galaxy Note GT-N7000 Android Development] Entropy512:
MMC_CAP_ERASE renders nandroid restores safe too - I9100 users have been nandroiding happily for two months.

The reason nandroids are dangerous on affected kernels is because they wipe/format before restoring.
[Galaxy Note GT-N7000 Android Development] GocaS6:
We are not panicking, bur there's no proof that this fix actually works. And what's the advantage of this kernel if we can't restore nandroid?

We can use any GB kernel for wiping and restoring, what's the point of this kernel?
[Galaxy Note GT-N7000 Android Development] DSD99:
And please stop with the "i just factory reset my phone and it still works! Superbrick is gone!" posts.

Having a succesfull wipe does not mean there is no bug.The chance of it bricking is small not 100% so you can wipe lots of times fine and then it will just brick.
[Galaxy Note GT-N7000 Android Development] zviki:
:banghead: :banghead: :banghead:
[Galaxy Note GT-N7000 Android Development] GocaS6:
You're a rocketing scientists for me Entropy but man was definitely on R3. And his phone is 7 days old so talking about previous damage? Don't think so.

And he paid 230 euros for changing his motherboard so it was definitely HB.

And yes he was restoring nandroid. That's a fact.
[Galaxy Note GT-N7000 Android Development] Entropy512:
No, half his post talks about CF-Root - The way he wrote his post, he flashed R3 in MO and then immediately dropped into recovery and did a Nandroid restore. So if MO failed to flash he was still on CF-Root.

Since r3 is released as a CWM-flashable zip and he flashed in MO - he would've had to manually extract the zImage and could easily have put the wrong one on his SD card. See below - one guy hardbricked because he accidentally mistook a ZIP for imilka's CM9 as a nightly because of a renaming mistake he made.

Did he go into CPUSpy and confirm that he WAS on Franco's latest kernel before dropping into recovery? If he didn't, there's no way to definitively know that he was actually on r3.

Is he sure he didn't accidentally flash R2 or R1?

7 days old - you can have damage on your first day. See the guy who got a refurb back after Superbrick, accidentally flashed imilka's CM9 instead of the nightly, and immediately rebricked on a wipe.

BTW, all the stuff Mr. Sumrall says about writing zeros as a workaround is for people who want a secure wipe (e.g. all data is truly erased/overwritten for privacy purposes). No need for it when just nandroiding/flashing other firmwares.
[Galaxy Note GT-N7000 Android Development] sotmax:
The advandage is that is faster and with better battery and of course with some hard work to solve some problems

You never know what someone flash in his phone.

I ve seen not 7 days but 7 hours brick phone of missunderstood of cwm app functionality in my lab so you never know what was inside the device before that... ;);)

) ) ) over the air on Galaxy Note ( ( (
[Galaxy Note GT-N7000 Android Development] GocaS6:
I do agree with every single word that you said Entropy. And you'll see that i asked him exactly same question cause i suspected that he didn't really was on R3, but it seems that man knows what's talking about, he's not some noob that was flashin his phone for a first time, anyway, you can read yourself, then we'll talk further.

http://xdaforums.com/showpost.php?p=26585186&postcount=2749