Database Develop

[Q] So...what to do with the LP5 kernel?

I've been reading a lot of different opinions on the "Bricked by Stunner ROM thread", but I didn't really see any developer's opinion and to be honest I didn't get much of a conclusion from it...
It just got me confused...
So!!!!! If I'm running imilka's CM9 (which is I'm pretty sure based on LP5 kernel):
- WILL THIS degrade my emmc and if yes...
- IS THERE any safe way to keep the current ICS Rom?
And lastly... If I have a backup made with Abyss Kernel 4.0 of a GB Rom, can I go back to GB by:
- Flashing Abyss 4.2 Redpill
- Restoring backup?
Thanks to anyone who will take the time to answer, I'm asking these because I really got confused by everyone's opinion in that thread and I'd like to know something for sure, for my own personal case.
Again, many thanks to anyone who answers.

eug3n91 said:
I've been reading a lot of different opinions on the "Bricked by Stunner ROM thread", but I didn't really see any developer's opinion and to be honest I didn't get much of a conclusion from it...
It just got me confused...
So!!!!! If I'm running imilka's CM9 (which is I'm pretty sure based on LP5 kernel):
- WILL THIS degrade my emmc and if yes...
- IS THERE any safe way to keep the current ICS Rom?
And lastly... If I have a backup made with Abyss Kernel 4.0 of a GB Rom, can I go back to GB by:
- Flashing Abyss 4.2 Redpill
- Restoring backup?
Thanks to anyone who will take the time to answer, I'm asking these because I really got confused by everyone's opinion in that thread and I'd like to know something for sure, for my own personal case.
Again, many thanks to anyone who answers.
Click to expand...
Click to collapse
I am not a developer at all but this is what I understand from Entropy's posts in that thread (and he is a REAL developer)
- The degradation occurs when you constantly flash ROMs or restore backups, i.e. anything that includes wiping and writing to the system partition
- I think having the ROM as it is will not do any harm, the danger is when you try to flash using the faulted kernels
- Yes you can go back by flashing Abyss 4.2, rebooting in recovery and then restoring your backup, but to be 100% safe use PC Odin and flash one of the pre rooted ROMs, flash CF Root then restore your backup normally
Then again, take my words with a grain of salt but that's what I think is the case

matius44 said:
I am not a developer at all but this is what I understand from Entropy's posts in that thread (and he is a REAL developer)
- The degradation occurs when you constantly flash ROMs or restore backups, i.e. anything that includes wiping and writing to the system partition
- I think having the ROM as it is will not do any harm, the danger is when you try to flash using the faulted kernels
- Yes you can go back by flashing Abyss 4.2, rebooting in recovery and then restoring your backup, but to be 100% safe use PC Odin and flash one of the pre rooted ROMs, flash CF Root then restore your backup normally
Then again, take my words with a grain of salt but that's what I think is the case
Click to expand...
Click to collapse
A million thanks mate!! You've answered my questions before! You really made things clearer for me. Someone in the Bricked by Stunner Thread even suggested that updatng apps and manipulating "large files" on the internal memory degrade the emmc...
Again, thanks a lot for putting that into perspective. I love flashing but I'm ashamed to admit I don't know many of the things that developers know...

eug3n91 said:
A million thanks mate!! You've answered my questions before! You really made things clearer for me. Someone in the Bricked by Stunner Thread even suggested that updatng apps and manipulating "large files" on the internal memory degrade the emmc...
Again, thanks a lot for putting that into perspective. I love flashing but I'm ashamed to admit I don't know many of the things that developers know...
Click to expand...
Click to collapse
Am not 100% sure about the large files transfer but I personally doubt it, before the bricked wave of Stunner users everyone was using the same kernel and nothing happened, and I personally been flashing and testing various mods with no issues so far (knocks on wood )
Still, I can be wrong of course

matius44 said:
Am not 100% sure about the large files transfer but I personally doubt it, before the bricked wave of Stunner users everyone was using the same kernel and nothing happened, and I personally been flashing and testing various mods with no issues so far (knocks on wood )
Still, I can be wrong of course
Click to expand...
Click to collapse
So far as ICS I only flashed the Chainfire Repack and 3 versions of CM9. I think I'll be sticking with the current version (which I'm really in love with...wouldn't want to go back to GB now really...) until the official CM9 comes out
Thanks again for taking the time to answer my questions and getting me on track with these things
LE: And Reloaded and themes several times

matius44 said:
)
Click to expand...
Click to collapse
This was to take you to 600!!

geo.samuel said:
This was to take you to 600!!
Click to expand...
Click to collapse
Thanks sam matey
Nice new avatar btw

matius44 said:
Thanks sam matey
Nice new avatar btw
Click to expand...
Click to collapse
This picture was taken few days back!!
However I like the Title "Recognized Contributor" you earned every bit of it!!

geo.samuel said:
This picture was taken few days back!!
However I like the Title "Recognized Contributor" you earned every bit of it!!
Click to expand...
Click to collapse
Hehe just noticed it a while ago
Thanks a lot mate

From my understanding, it's not degradation at all...but more of a chance you take each and everytime you wipe/flash a ROM. It's an instant short circuit of an emmc sector. At least that's my understanding anyway. It either happens or it doesn't. It doesn't build up the likelihood of it happening over time. I've been using 4.2 Abyss to do all my wiping and flashing, so I'm hoping that will safeguard my Note.

smalmagal said:
I've been using 4.2 Abyss to do all my wiping and flashing, so I'm hoping that will safeguard my Note.
Click to expand...
Click to collapse
True, but point is, how are you getting to Abyss Kernel in the first place? That's a /system wipe/write as well when you flash Abyss kernel unless of course you use Odin for that..

matius44 said:
Am not 100% sure about the large files transfer but I personally doubt it, before the bricked wave of Stunner users everyone was using the same kernel and nothing happened, and I personally been flashing and testing various mods with no issues so far (knocks on wood )
Still, I can be wrong of course
Click to expand...
Click to collapse
Entropy also mentioned that when the I9100 forums were using an affected kernel, several users ended up with corrupt/unusable data partitions. This brings me to believe that any operation in which the kernel is writing to the emmc, regardless of which partition it is writing to, brings risk of permanent damage to your emmc. The result of this is that if it damages your system partition you get a hardbrick, and if it damages your data partition you've got yourself a very difficult to use android install.
EDIT: this all depends, of course, on there being a bug or a hiccup in the script operating the kernel to write to the emmc. Without such a bug these operations are harmless.

chill392 said:
Entropy also mentioned that when the I9100 forums were using an affected kernel, several users ended up with corrupt/unusable data partitions. This brings me to believe that any operation in which the kernel is writing to the emmc, regardless of which partition it is writing to, brings risk of permanent damage to your emmc. The result of this is that if it damages your system partition you get a hardbrick, and if it damages your data partition you've got yourself a very difficult to use android install.
EDIT: this all depends, of course, on there being a bug or a hiccup in the script operating the kernel to write to the emmc. Without such a bug these operations are harmless.
Click to expand...
Click to collapse
So...in lame terms...just using the ROM is dangerous then...??

matius44 said:
Hehe just noticed it a while ago
Thanks a lot mate
Click to expand...
Click to collapse
Congrats to Rec Contributor. You have deserved it a thousand times over.

Anyone else paranoid about flashing ics?

With so many horror stories being posted, I don't know what to believe. When will it be relatively safe for us to update to ics?
I came from an HD2, and that was a treasure for flashing different roms. But it seems like the note is so easy to brick.
Edit: All I've done so far is root my note using Dr. Ketan's method.

It's mainly horror stories. Dozens, if not more already flashed to ICS without any problems. Of course there is occasionaly someone with bad luck, but that is also on the OTA updates. Every now and again something goes wrong, but it's a small chance and usually you are still able to fix it afterwards.
So just stick closely to the manual, don't cut corners and you'll probably be okay.
Otherwise, just wait for the OTAs. That's what I'm doing, but that is mainly because I'm a little lazy. However when I got the ICS kernel I'll put vanilla ICS over it.

I've flashed dozends of ROMs on my old HTC desire including ICS. At the end it worked always fine.
1. Backup
2. Wait after flashing - some roms need their time. After 10 min I've sometimes put out the battery to restart...
3. Enjoy
So don't fear!

I'm waiting for ICS OTA also. There have been lots of mixed reports with the previously leaked ICS ROMS - some bricked and some not. I've had a great run with flashing GB ROMs and Kernels but will wait for more official versions.
BTW - A colleague has a Note about four weeks old bought via the web. It turned out to be a German handset and he was successfully able to flash via KIES. I'm jealous - my Note 6 months old and I am still waiting for official ICS !

If you dont have any crazy combination of rom with custom kernel and cwm then is fine
Just dont wipe before flashing
And wipe after flashing
Sent from my iPad using Tapatalk

The fact that we have had ANY bricks at all suggests to me that this is not safe to flash, and even though I have been able to successfully flash LPY and run it, (not without problems), the bit that concerns me is the bricking due to large file copying which has been mentioned by various people.
Since I regularly copy large files to and from the device, I do not plan to subject my device to testing the theory.

I flashed ics yesterday and everything went fine, Iam always paranoid when comes to flashing but research before actual flash is vital! SEARCH button overheats and Iam ALWAYS following instructions!
Dont know what would I do without xda and those so capaple devs!
Galaxy Note!!!

I have flashed LPY a total of 3 times so far without any problems. I have wiped/deleted cache etc etc. The Bricks are all related to modified kernels and CWM. If you you use the stock LPY kernel then all will be fine.
I have also flashed CM9 several times and had no issues what so ever.
If you need root on LPY best method is to flash a GB rom and get root, then use mobile odin with the everoot option to flash LPY.
DO NOT flash the CF Root kernel, This is where problems may start. Keep it Stock and all should be fine.

nandihno said:
Just dont wipe before flashing
And wipe after flashing
Click to expand...
Click to collapse
Why is it safe to wipe after flashing and not before? I thought it was the other way around?

neos_83 said:
Why is it safe to wipe after flashing and not before? I thought it was the other way around?
Click to expand...
Click to collapse
It is the other way around.
Anyway, I fear this might be another superbrick in the making...
http://forum.xda-developers.com/showthread.php?t=1653290
And another one...
http://forum.xda-developers.com/showthread.php?t=1649982

vetchems said:
I have flashed LPY a total of 3 times so far without any problems. I have wiped/deleted cache etc etc. The Bricks are all related to modified kernels and CWM. If you you use the stock LPY kernel then all will be fine.
I have also flashed CM9 several times and had no issues what so ever.
If you need root on LPY best method is to flash a GB rom and get root, then use mobile odin with the everoot option to flash LPY.
DO NOT flash the CF Root kernel, This is where problems may start. Keep it Stock and all should be fine.
Click to expand...
Click to collapse
This is exactly what I did...
Mobile Odin Pro inject SuperSU and everroot......NO CF ROOT had a good GB ROM and Kernel. Only wipe done was done by Mobile Odin Pro
No I am 100% stock IPY with root...The fun will start when I begin flashing custom ROMS. Will need to flash CWR for that.

to answer the original question... no... because i thoroughly read as much as i can find before i flash anything...even google it to see if there are problems ... hence i have ics rumming and running without any strange issues...

tbong777 said:
This is exactly what I did...
Mobile Odin Pro inject SuperSU and everroot......NO CF ROOT had a good GB ROM and Kernel. Only wipe done was done by Mobile Odin Pro
No I am 100% stock IPY with root...The fun will start when I begin flashing custom ROMS. Will need to flash CWR for that.
Click to expand...
Click to collapse
I decided I did not want to "tip toe" around my normal processes with this device and went ahead and flashed CF Root with CWM. Going to need CWM to flash Roms and the LPY kernel has nt proven to be all that safe either. There is at least one case of a Superbrick wiping from Stock Recovery.
I bought these devices to mess with. I have a back up S2 and the s3 is out....Worst that can happen is I sell for parts.

well i am lucky so far as i dint have any issue with my note even after flashing lpy somany times from cwm may b me lucky till now

I'm terrified of flashing any roms on now after all the horror stories. I honestly don't even really care if I have ICS. I just hate how slow the stock ROM is. I would be very very happy with CM7 with SPen functionality.
This kind of sucks coming from an LG G2X which had so many stable roms and kernals to choose from
I thought a Samsung phone would have had even more but I guess not.

Probably like everyone else, I read Entropy's thread and became SUPER paranoid. He said there's no way to tell if you're slowly degrading the emmc or not unless you're on a 100% safe kernel / rom. I'm confused about the rest of the details. Apparently cm9 is 100% safe, but even the official ics can brick our note if we still have reminants of a leaked ics rom / kernel?
People alot more knowledgable than me have been bricking their note, so I will wait for an idiot proof method.

I would luv to see a step by step guide on video.
Also still dont grasp the fact that even if we put an official ics from Germany will won't get upgrades.
Sent from my GT-N7000 using XDA

I've been using lpy since release, and although I've had no problems so far, don't have cwm just root, but the more posts IM reading about people experiencing bricks from many different methods is definitively scaring me.
Chasmodo is a very reputable developer as is Entropy. I heed their words and will flash back to GB today, it's just not worth the risk.
Sent from my GT-N7000 using xda premium

Thijsvr said:
It's mainly horror stories. Dozens, if not more already flashed to ICS without any problems. Of course there is occasionaly someone with bad luck, but that is also on the OTA updates. Every now and again something goes wrong, but it's a small chance and usually you are still able to fix it afterwards.
So just stick closely to the manual, don't cut corners and you'll probably be okay.
Otherwise, just wait for the OTAs. That's what I'm doing, but that is mainly because I'm a little lazy. However when I got the ICS kernel I'll put vanilla ICS over it.
Click to expand...
Click to collapse
I also initially thought it was all speculation and anecdotal evidence. However, it appears that at least one user who has upgraded a brand new Note via Kies to LPY and wiped immediately thereafter has bricked his device.
That being said, I updated via PC Odin, rooted with temp CWM and full wiped from stock recovery thereafter without any issues (so far, been 3-4 days now). The performance improvements that ICS brings are significant, IMHO.
Basically, update if you really want to and refrain from wiping if possible (i.e. if you are not facing any FCs etc).

What did I do wrong? N7000 bricked.

Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!

marcelo.ellmann said:
Good evening!
I've around with Androids for quite some time, and today, I finally got my N7000 to replace my I9100.
I've played around quite a lot with my I9100 and was happy with the CM9 nightlies for it.
I got my N7000 today and did the following:
1. Rooted it with this method: http://forum.xda-developers.com/showthread.php?t=1501719t=1501719
2. Decided to install the latest CM9 nightly. I booted the same CWM from the tutorial above, chose install zip from SD card and... It hang. I left it for about 5 minutes and nada, nothing. I decided to shut if off and...
3. Nada. Black screen, no recovery, no battery charging, no download mode, no nada, nothing. Dead!
I'll take it this week to the nearest Samsung repair center and check how much it's gonna cost to get it fixed (if they can get it fixed at all). I don't intend to use any warranty whatsoever since I know even tough I have not voided the warranty flashing a different kernel, I did messing with it.
I just wish to know what was my mistake, so I do not do it again in the future. AFAIK I did not mess with the bootloader, so I was supposed to be safe, right?
Do I have ANY hope of getting it resurrected?
Any opinion helps!
Thanks!
Click to expand...
Click to collapse
ALWAYS flash a GB Kernel or ROM BEFORE flashing a CUSTOM ICS ROM.

Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.

marcelo.ellmann said:
Okay. Lesson learned, trust me.
Now here's the part where I feel very stupid: what's a GB kernel? Why is that a requirement for ICS ROMs? Was it not for Gingergread ROMs?
And now here's the second part where I feel even stupidier: doesn't the kernel reside on the ROM/OS part of Android? Why would the kernel, which comes AFTER the bootloader, affect the boot of the Android? Wouldn't it just screw my phone, but wouldn't it still give me the chance of flashing another ROM?
Thanks for the help.
Click to expand...
Click to collapse
Because of an eMMC brick bug!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
The guide I followed is from here take a few moments to read and understand then you will have no troubles in rooting/flashing again!

hing98 said:
Because ICS has not been officially released on the Galaxy Notes therefore we use a GB Kernel or ROM before we flash any custom ICS ROM.
Yes it was confusing at the start but to avoid bricking you must alwaysfollow the guides given by the Developer!
Anyways to round up, my way of flashing ROMS is flashing a GB Kernel called Abyss 4.2 and then reboot recovery, from then I wipe everything then flash any custom ICS Roms. I've had my Note for almost a week now and found no problems in flashing! But it did take me 2hrs to root doing heavy research but it paid off!
Click to expand...
Click to collapse
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium

stoney73 said:
You may want to recheck your facts....ICS has actually been officially released in many countries......
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sorry was reading from another guide. Your right
---------- Post added at 01:12 PM ---------- Previous post was at 12:23 PM ----------
hing98 said:
Sorry was reading from another guide. Your right
Click to expand...
Click to collapse
Anyways its a bug that bricks your device,
you can find more information here
Cheers

I had a galaxy S where flashing process was different Wen u flash CM9 roms and if you want to get back to GB roms only way out was PC Odin and moreover you can wipe on ICS roms and install other roms. But wen i got the note the procedure was slightly different Brickin problems and moreover wen you are in ICS you can get back to GB with GB kernel only no need for PC odin. Just keep a copy of Abyss kernel 4.2 in your sd card and be sure to flash it when changing roms.....

Doesn't Franco rev3+ solve the brick bug?
Hi all,
since you're saying we have *always* to flash a GB kernel before having a factory reset, are you talking about those having the CF/Stock kernel?
I'll make it clear: as far as I know, Franco made a kernel that should avoid the brickage since its 3rd version (thread here --> http://forum.xda-developers.com/showthread.php?t=1491428). Who installed this kernel could just wipe from ICS and install any ICS ROM. Am I wrong? If so, please explain the whys.

UNBRICKED!
I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.

[Q] N7000 emmc bricked can now only run GB

Hi,
I was quite happily running ICS4.0.4 (rooted) when I decided to try a different ROM (and/or JB - can't even remember any more).
After I did a wipe (I know, I know!!!) it got stuck on the boot logo screen.
I had the phone fixed by a 3rd-party repair shop, who installed ICS4.0.3 on it and, while at the shop, I used the phone a bit to make sure it was ok.
It kept crashing intermittently, so they had another go at it and now they tell me they could only install GB on it.
So, keeping in mind that the phone had the emmc bug and I tripped over it:
Is there anyway I can install ICS again on it?
I could use some of the tools floating around to detect damaged partition blocks and work around them.
What procedure should I use to go from a stock GB (non-root) to ICS?
Specifically,
- is there a safe way to root GB (given the emmc damage already), so that I can flash the other ROM/kernels (below)
- what kernel should I use
- what ROM should I use
I would greatly appreciate any help on this. I have been eating humble pie for a week now, so I hope there is no more 'why didn't you pay attention' coming my way
Cheers

You could use hydracore kernel which works with all GB and ICS ROMs and JB none Tw ROMs I be leave you can flash with PC odin to gain root and is a safe kernel
Sent from my GT-N7000 using XDA Premium HD app

ttibbetts83 said:
You could use hydracore kernel which works with all GB and ICS ROMs and JB none Tw ROMs I be leave you can flash with PC odin to gain root and is a safe kernel
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks ttibbetts83, I will try that and see how i go

Thanks Arobase40.
I'll get a strong coffee and read your reply from top to bottom and then plan my next move.
The repair was done by people unrelated to Samsung.
I currently have GB v2.3.5, (SGN_XX_OXA_KJ1_FACTORYFS) which works well, it would seem.
I'd love to get ICS back on it but need to gather info (such as that from yourself) before I do anything.
A bit more info on the state of the emmc storage: Using 'adb shell' and executing the command DD did in fact find bad blocks in partitions 9-11 (can't recall right now exactly which ones), so there are issues there.
The partition that is in place now, __appears__ to have successfully skipped those bad blocks.
And on something slightly tangential to the current topic, I know that doing a 'WIPE DATA' from the recovery menu zaps emmc, but does that also happen when you do a factory reset from within Android? From memory, when doing so, it seems to go into recovery mode and do it, so I'd expect that it'd also damage emmc.
Cheers

arobase said:
As opposed to all alarmist and contradictory posts about eMMC bug on stock Samsung ROM : GB or ICS, I never got any issues with this so called eMMC bug and never got bricked G-Note as long as I kept at using the stock kernel, nevertheless I made various and numerous wipe whichever the ways (from recovery or the settings)...
For rooting, I always used the temporary Touch CWM to flash (which has been may be removed from XDA, I guess as it was supposed to cause bricked devices) anything : superuser, busybox, and other custom ROM... ^^
BUT when I flash a custom ROM, I always removed the custom kernel (so called "safe"), and replace it for a stock kernel and never got issues with it.
The first and last time I flashed a custom with custom kernel I got my G-Note bricked (just forgot the replace the custom kernel for a stock one... ^^) !!!
So, if you want to flash an ICS version, get one from Sammobile, and flash it with PC Odin !
You shouldn't have any problem with them !!!
Get all root and busybox files from dr Ketan, and if you can find it again use the temporary Touch CWM which has NO kernel inside : it WORKS quite fine !!!
Click to expand...
Click to collapse
Unfortunately there are no high trees on XDA beause you should look for one before typing this utter personal nonsense that could brick anybody's Gnote.
Taking your own convictions for thruth is one thing, sending innocent ppl into the jungle is another...
What you are saying is: If there is a lightning storm, just go into an open field en enjoy. I cannot say it is 100% safe, but I never got struck....I think they removed the tree i used to seek shelter from the rain, but if you search real hard you might find it anyway.
---------- Post added at 10:33 AM ---------- Previous post was at 10:17 AM ----------
amanmasgaman said:
Hi,
I was quite happily running ICS4.0.4 (rooted) when I decided to try a different ROM (and/or JB - can't even remember any more).
After I did a wipe (I know, I know!!!) it got stuck on the boot logo screen.
I had the phone fixed by a 3rd-party repair shop, who installed ICS4.0.3 on it and, while at the shop, I used the phone a bit to make sure it was ok.
It kept crashing intermittently, so they had another go at it and now they tell me they could only install GB on it.
So, keeping in mind that the phone had the emmc bug and I tripped over it:
Is there anyway I can install ICS again on it?
I could use some of the tools floating around to detect damaged partition blocks and work around them.
What procedure should I use to go from a stock GB (non-root) to ICS?
Specifically,
- is there a safe way to root GB (given the emmc damage already), so that I can flash the other ROM/kernels (below)
- what kernel should I use
- what ROM should I use
I would greatly appreciate any help on this. I have been eating humble pie for a week now, so I hope there is no more 'why didn't you pay attention' coming my way
Cheers
Click to expand...
Click to collapse
Actually you should be happy that they revived your Note after brick even if it's only running GB for now.
However if you are a brave person you can do the same trick on ICS.
Just read and understand the thread that is a guide on doing so.
You can root your GB without a problem, but there is no obligation for it to install ICS with odin.
However what you do need is the following (besides a lot of patience and courage) :
1. get the ICS files you want to flash including the pit file.
2. get a program called PIT MAGIC to recreate a suitable pit file
3. determine where your bad blocks are located
4. Load the pit file into the magic program and alter the stock pit file
with the values needed to ommit your bad emmc area
5. save it and then flash your note in odin with your newly created pit file and repartition ticked.

@OP: could you please check your internal storage capacity? Is it aroung 8GB?

Arobase we are not going to rediscuss this matter for another 556643 pages.
Just ask yourself : if there was no problem then why did samsung patch their JB kernels for it. http://forum.xda-developers.com/showpost.php?p=34933643&postcount=683
Also nobody asks you to reconsider your own experience and beliefs, but the day someone follows your instructions and bricks his phone, are you going to pay for a new motherboard ?
I'll stop this discussion here, and just hope nobody will get struck under the tree.

Updating a Galaxy note (bought secondhand)

Bought a second hand Note. It's rooted as CWM on it. It won't update OTA (no updates showing at all for the past couple of days), and it's on 2.3.6.
Can I manually install an update via Odin? If so which one?
Direct links would help, I'm a bit of a noob
U.K Note btw

JccageX2 said:
Bought a second hand Note. It's rooted as CWM on it. It won't update OTA (no updates showing at all for the past couple of days), and it's on 2.3.6.
Can I manually install an update via Odin? If so which one?
Direct links would help, I'm a bit of a noob
U.K Note btw
Click to expand...
Click to collapse
Being a 'noob' isn't an excuse for not looking. Go to the stock ROM sticky thread and try actually looking next time.
It's always so much harder when you have to try (David Gray).

JccageX2 said:
Bought a second hand Note. It's rooted as CWM on it. It won't update OTA (no updates showing at all for the past couple of days), and it's on 2.3.6.
Can I manually install an update via Odin? If so which one?
Direct links would help, I'm a bit of a noob
U.K Note btw
Click to expand...
Click to collapse
instruction sent
check your PM

AndroidSlave said:
Being a 'noob' isn't an excuse for not looking. Go to the stock ROM sticky thread and try actually looking next time.
It's always so much harder when you have to try (David Gray).
Click to expand...
Click to collapse
Typical "Omfg do it yourself guy". Here's an idea, stop being such an ass, I evidently looked as I know what Odin is, I wanted to be sure from a member who knows what he's doing just in case I did something wrong. Imbecile.
Thank you Comscier, downloading all the stuff now

JccageX2 said:
Typical "Omfg do it yourself guy". Here's an idea, stop being such an ass, I evidently looked as I know what Odin is, I wanted to be sure from a member who knows what he's doing just in case I did something wrong. Imbecile.
Thank you Comscier, downloading all the stuff now
Click to expand...
Click to collapse
No here's a better idea - stop being a lazy
If you want someone to do it all for you, there are websites you can pay to root your phone. XDA is NOT that place.
There are threads already for this but you are just to lazy to lift two fingers to look
So you call me an ass? Okay buddy I'm an ass because your too lazy to read the guide that someone spent hours making that is at the very top of the forum as a sticky note in capital letters.
And yet with 152 posts you still refuse to just look at the guides that are step by step instructions because you expect to be spoon fed
Let's look at your other threads "which rom is best" "how to root my desire" and so on
Its not like you even try to look. You just over and over break xda policy and are lazy. Get with the picture and follow the rules
No reason to call me an ass, I am actually a very useful and helpful person to many people on this website. But everyone is expected to at least TRY to look before posting, which you consistently refuse to do (as your previous threads for other devices proves)

AndroidSlave said:
No here's a better idea - stop being a lazy
If you want someone to do it all for you, there are websites you can pay to root your phone. XDA is NOT that place.
There are threads already for this but you are just to lazy to lift two fingers to look
So you call me an ass? Okay buddy I'm an ass because your too lazy to read the guide that someone spent hours making that is at the very top of the forum as a sticky note in capital letters.
And yet with 152 posts you still refuse to just look at the guides that are step by step instructions because you expect to be spoon fed
Let's look at your other threads "which rom is best" "how to root my desire" and so on
Its not like you even try to look. You just over and over break xda policy and are lazy. Get with the picture and follow the rules
No reason to call me an ass, I am actually a very useful and helpful person to many people on this website. But everyone is expected to at least TRY to look before posting, which you consistently refuse to do (as your previous threads for other devices proves)
Click to expand...
Click to collapse
Never said you weren't a useful guy. However you for some reason insist I didn;t look beforehand. I made a thread to make sure I didn't mess up my phone, I didn't know if I could flash stock firmware over a root + recovery or not.
So before you attack members in their first post with a new phone, I'd suggest you'd think twice.
I appreciate your work. Bye.

JccageX2 said:
Never said you weren't a useful guy. However you for some reason insist I didn;t look beforehand. I made a thread to make sure I didn't mess up my phone, I didn't know if I could flash stock firmware over a root + recovery or not.
So before you attack members in their first post with a new phone, I'd suggest you'd think twice.
I appreciate your work. Bye.
Click to expand...
Click to collapse
My only thing I want to say is next time say what you read. Otherwise it looks like you have done nothing and are just posting out of laziness. There was no way I could have known you did any due diligence with your post aside from a mention of Odin.
I am going to link you to a very detailed post I wrote about upgrading from gingerbread. This post I wrote will guide you.
Sent from my Samsung Galaxy SVII using Tapatalk 6 Beta
---------- Post added at 11:10 PM ---------- Previous post was at 11:06 PM ----------
Here is my post from the philz thread. Let Mr know if u have questions. Please also be SURE to read the brickbug sticky thread
TO ANYONE READING THIS POST - NOTE THAT THIS IS ALL SPECIFIC TO UOGRADING FROM GINGERBREAD ONLY
@onetonnoodle Honestly, if you like the features of Sweet Rom, it is an Amazing rom (maybe the best?), but I personally (when I use touchwizz interface) prefer a stock interface, which is why I like @ThaiDai's stock-deodexed LT9. If you were thinking of sweet rom, just go with it. It really is spectacular and constantly updated. Just be aware you may issue a couple bugs here and there because it is in constant development, but they always get fixed right away.
Regarding hardbricking, as long as your only doing wipes while PhilZ kernel is installed, you are safe. Remember anytime a new rom is flashed it overwrites the kernel with whatever is packaged with that rom. Also any gingerbread kernel philz or not are safe. Be very careful if on an ICS ROM though.
There are 3 ways that I would do it. Obviously, there are about 100 ways to do this. These are the methods I may use
IF ITS GINGERBREAD COMPATIBLE (I dont remember), the Mobile Odin Pro method is by far the easiest way
Here is one Method (easier, but only if u have pc odin setup):
1. Flash Sweetrom via PC odin
2. it wont boot because of all your old gingerbread data. After turning it on, immediately boot to recovery. Do a factory reset, or if you want a completely clean install do a full wipe and then reflash sweetrom again via recovery.
3. reboot to system
4. YOU WILL HAVE A YELLOW TRIANGLE. Use Triangle Away from XDA (its free) to remove that, but this does have a risk.
Mobile Odin Method this would be my first choice so long as your GB rom is rooted
I think mobile odin is compatible with gingerbread. You will have to download sweet rom to your phone.
If it is, you can use mobile odin to flash the sweetrom zip, you are already on gingerbread so you are brickbug safe...
If mobile odin is gingerbread compatible, which i believe it is, this is really a simple method.
Obviously your gingerbread ROM has to be rooted if you want to do this.
NOTE: you will get issues because mobile odin doesnt really do a full wipe. if hte issues do arise you can reboot to recovery included with sweet rom and just do a factory reset and you will be fine.
Here is yet another method to update:
1. Open the browser ON YOUR PHONE. *(a) Download SweetRom to the sdcard (internal or external); (b) Download the newest LT9 Philz kernel to your sdcard also.
* **Note: if you have issues getting the download to complete, try opera mini browser because it supports resume downloads.
2. [OPTIONAL STEP, not required] Flash Abyss 4.2 kernel, and do a full nandroid backup in recovery... * I personally would skip this step. *I dont even know if you could find abyss anymore, but I am making an option for you to get a nandroid backup of your gingerbread rom that will boot... *really though, dont waste your time on this unless you want to assure you have a full backup of gingerbread with a gingerbread kernel
3. *Unfortunately, you can't flash philz directly from your 3e recovery (because you are on gingerbread)... it will give a signature verification error. *so you can either flash it via PC odin, or do an OTA upgrade and then flash it (be careful, once you do this you are not brickbug safe).
4. Flash PhilZ LT9 Kernel from either Abyss if you did step 2 (optional), from your stock android recovery if you can put it on your external sd card *only if you did an OTA update , or via PC Odin if you dont have an external SD Card. *Be sure to follow the philz flashing instructions step by step.
5. NOW YOUR PHONE WILL NOT BOOT. dont be alarmed, you only want to go to recovery. *You will have no issue getting into recovery as long as philz flashed properly. *Your phone now has a JB kernel with a GB system, this is why it won't boot.
6. boot recovery (power - volume up - home held until you get to philz touch interface)
7. Go to factory reset, and choose the wipe all option (this wipes /system /data /cache /preload and .android_secure). *Your phone now has no system, but will retain the philz kernel and touch recovery.
8. no need to reboot recovery. *Just go to flash the Sweet ROM Zip. *let it run.*
9. reboot to system
10. Done. *it will already include the kernel.
If you are confused about any step, dont even start the process. ask first.
And be aware, there is always a risk doing this. It won't brick your phone, but you may softbrick it and lose recovery if something goes wrong. The solution for this is to use PC Odin and flash a ROM via PC Odin.

Thanks.