Related
I think we need to sticky/pin this for us who just flash the stock/leaked GB 2.3.3 along with the optional root from this thread since we can't post there http://forum.xda-developers.com/showthread.php?t=1127249
Since this is the route that I went I would be able to help answer questions for others. I see cognition, mosaic.... but how about us who like to keep it stock?
Brickster
Just want to say that I have learned so much on here and I have a lot of fun trying out different ROMs. Thanks to all the DEVs, when I get a job I'll buy you guys some beers lol.
So... This has soft bricked my phone every single time. The first 4 attempts were from stock eclair. My last attempt I was successfully running Stock I9000 2.3.3 NEE so I thought I would try it from there. Odin gets to boot.bin and then says FAIL! I got into download mode using VOL DWN and PWR which is the key combination from Stock I9000 2.3.3 NEE. I have been running I897UCJF6-final-OCD-REV0 to flash back to stock after brickness.
So i'm sure i'm missing something pretty simple, but any help is appreciated.
Woah dude, that was very very very close to being a hard brick. Boot.bin is the primitive bootloader. so you had a kf1 pbl, and since you had the combos for I9k boots you obviously had an I9000 sbl, (secondary bootloader that's where the combos are contained.)
Make sure the usb chord is on a port attached to the motherboard (in the back of the pc), if it is already switch to another. Reboot the computer and try again.
But with such a close call like that, and the fact that you said it fails every time I would avoid it altogether I mean its a stock rom, is it worth bricking over??
Well, I really wanted to try the Cognition 5 v2 ROM. Instructions say to be on Samsung Gingerbread. So that's why I tried so many times and I am really more curious to find out why it's not working than I am worried about it bricking.
I was on a port directly on the motherboard Odin displayed as com10.
I was thinking that maybe it is my computer since most have success with this 1-click. I forget sometimes I'm running a 64-bit version of Windows 7 maybe that's the culprit. Is there anything I can check on my computer to keep this from happening again?
ttr187 said:
Well, I really wanted to try the Cognition 5 v2 ROM. Instructions say to be on Samsung Gingerbread. So that's why I tried so many times and I am really more curious to find out why it's not working than I am worried about it bricking.
I was on a port directly on the motherboard Odin displayed as com10.
I was thinking that maybe it is my computer since most have success with this 1-click. I forget sometimes I'm running a 64-bit version of Windows 7 maybe that's the culprit. Is there anything I can check on my computer to keep this from happening again?
Click to expand...
Click to collapse
Use admin mode for Odin and change the compatiblity to Xp service pack 2. This is the best way to run Odin for Windows 7 x 64. Since I use Cog 5 v2, I strongly recommend following the instructions 100%. Please remember when you need to loading stock UCKF1 and when you load UCKF1, you are loading bootloaders, so any disconnection can brick you hard. Thank goodness for the simplified instructions there.
GB stock? I thougth captivate stock were eclair or froyo.
KF1 is the leaked gingerbread firmware for the captivate...
popfan said:
Use admin mode for Odin and change the compatiblity to Xp service pack 2.
Click to expand...
Click to collapse
After changing the compatibility mode to XP pack 2 everything worked like a charm. Then I was able to successfully flash Cognition 5 v2. Sweet!
Thanks.
Hello. I use Darky's rom 10.2. And I have problem with Dialer. It sometimes crushes and exits. Problem will be solved with reboot. how can I fix it? thanks.
I would try to flash again and make sure you do a data/cache wipe. I've had random issues with other ROMs when I did not wipe, and all was fixed once I flashed properly.
I know I'm not wiping everything while flashing, but I flash it as told as in FAQ. But my memory will stay unwiped after I run newly installed ROM.
When you say "memory" what exactly do you mean?
If you mean the /sdcard storage partition, that is normal.
yes, /sdcard storage partition.
Before flashing, I get warning message about wiping all data in my internal storage... what does it mean then?
The /data and /cache partitions. And the dalvik cache.
The first 2 are in the cwm main menu. Wipe data/factory reset and wipe cache. Dalvik is in the advanced sub menu.
When i flash this, my phone asks me for a password. It won't let me do anything without the password and I have no idea what it is. I've tried samfirmware.com and that most certainly is not it.
Griff1220 said:
When i flash this, my phone asks me for a password. It won't let me do anything without the password and I have no idea what it is. I've tried samfirmware.com and that most certainly is not it.
Click to expand...
Click to collapse
It appears to be asking for some encryption password according to one of these guys that posted in the following thread. But there is a way to get past it by the method in this thread...http://forum.xda-developers.com/show...02&postcount=7
Remove ur external sd and copy over/back up anything u want to save from ur internal sd before u do this, just in case.
data/chache wipe i should do right after flashing right?
I'm on ICS Stunner right now which means my kernel is I9220ZCLP6. I've read that i can not flash from this kernel which is about to be right because since I'm on this ROM I can't flash any other custom rom because of some error while installing a ROM. I did full wipe in CWM many times and i remember that about four months ago my phone stopped working correctly and I couldn't install any ROM not even ISC Stunner. Then what I did was installed I9220LP1-N7000-ICS-REPACK again and it worked fine and since then I'm on ISC Stunner. But now I want change and install Rocket ROM or Asylum. Mostly I need tablet mode and I know that Asylum got one but I'm not sure if Rocket ROM have one? In Rocket ROM thread I found:
d) coming from CM9, ROMs based on CM9 or other ICS AOSP ROM:
- boot in Recovery
- FullWipe
- Flash ROM
- reboot system
-...you are done
Whenever you do a FullWipe:
- install Abyss Kernel 4.2
- boot back in Recovery (find it under 'advanced')
- now FullWipe!!!
- Flash ROM
- reboot system
-...you are done
==> ONLY, ONLY, ONLY FullWipe with Abyss Kernel 4.2 installed!!!! NEVER, NEVER, NEVER Full Wipe with CF-Root Kernel installed!!!
But I also found that first I have to return to stock ROM and some people hardbricked theirs phones doing this. So I don't want any mistakes. Please tell me what's best in my situation?
Its suggested to flash stock root able gb rom first and foremost, then you can follow the steps above.
It sounds like the damage is already done though. If the flash gets stuck at factoryfs.img then you know there's trouble ahead and you may need to repartition the emmc chip.
Best of luck.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
Since Stunner thread got closed and many people suppose that ROM won't get any further development it would be a good idea to write a thorough instruction on how to switch from the Stunner ROM safely.
Need some brave guy to try to escape "already damaged but still working NOTE by Stunner" and update an instruction on this for everyone.
The reason I said that it seems the damage has already been done is that you were only able to reflash the same ics repack kernel. This suggests that you're only able to access the emmc that you were originally using. When trying to write a different kernel or rom, it sounds like its failing to write to the new sections of emmc, suggesting damage.
It would be more helpful if you tell us how the writes were failing, how you were flashing (PC Odin/mobile)? Was it failing at factoryfs.img?
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
SpyderTracks said:
The reason I said that it seems the damage has already been done is that you were only able to reflash the same ics repack kernel. This suggests that you're only able to access the emmc that you were originally using. When trying to write a different kernel or rom, it sounds like its failing to write to the new sections of emmc, suggesting damage.
It would be more helpful if you tell us how the writes were failing, how you were flashing (PC Odin/mobile)? Was it failing at factoryfs.img?
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
Click to expand...
Click to collapse
It was few months ago and I don't remember but 90% it was factoryfs.img error and that happened few seconds after begining install process of other ROM then Stunner. All the time I've been using CWM for data wipe/cashes/dalvik/installing roms/fixes. I didn't know about this issue then and I don't think that anyone knew. I remember that my phone didn't want to boot up sometimes before stopped working but after i fixed it it's alright so obviously I shouldn't change anything and leave it like that But before I start doing anything with this phone I need to know where can I get new motherboard from in UK and what is the cost? For 50 pound I can take the risk but if it's much more it's not worth it. It needs to be in the UK because if I'll ****ed up I need new parts as soon as possible. Ok, I'm waiting for some answers now. Thanks.
PS. I've found this tutorial
bulla666 said:
It was few months ago and I don't remember but 90% it was factoryfs.img error and that happened few seconds after begining install process of other ROM then Stunner. All the time I've been using CWM for data wipe/cashes/dalvik/installing roms/fixes. I didn't know about this issue then and I don't think that anyone knew. I remember that my phone didn't want to boot up sometimes before stopped working but after i fixed it it's alright so obviously I shouldn't change anything and leave it like that But before I start doing anything with this phone I need to know where can I get new motherboard from in UK and what is the cost? For 50 pound I can take the risk but if it's much more it's not worth it. It needs to be in the UK because if I'll ****ed up I need new parts as soon as possible. Ok, I'm waiting for some answers now. Thanks.
Click to expand...
Click to collapse
Where did you buy the phone? If it was bought new from operator or sim-free then you'll be under warranty and if you brick again, there's no way they can check for binary counter or what rom you have installed. You just say it broke after ota update to ics, and it'll be fixed under standard 1 year warranty. Just need proof of purchase. Either send it to your operator, usually next day collection and up to 2 weeks fix, or Samsung will direct you to a local partner who'll fix it, probably under similar time frame.
If it was eBay or second hand then different story. From what I've read of others getting replacements outside warranty its around £150-200 for new motherboard.
That emmc "fix" you've found will repartition the chip so you bypass the damaged section, so you lose storage, often between 3 or 4gb of internal storage.
Hope it helps.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
SpyderTracks said:
Where did you buy the phone? If it was bought new from operator or sim-free then you'll be under warranty and if you brick again, there's no way they can check for binary counter or what rom you have installed. You just say it broke after ota update to ics, and it'll be fixed under standard 1 year warranty. Just need proof of purchase. Either send it to your operator, usually next day collection and up to 2 weeks fix, or Samsung will direct you to a local partner who'll fix it, probably under similar time frame.
If it was eBay or second hand then different story. From what I've read of others getting replacements outside warranty its around £150-200 for new motherboard.
Hope it helps.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
Click to expand...
Click to collapse
I've got my phone from affordablemobiles.co.uk with T-mobile. Now I don't know if there won't be any problem returning this to T-mobile. Propably I'll have to deal with affordablemobiles because they sold me the contract about 10 months ago. That tutorial I've posted in my last post it seems to be alright. Maybe I'll test it later. First I need to change display in my old HTC HD2 for in case of hardbricked N7000.
All the best dude. Repartitioning does work, no doubt about it, but for a true fix and if you're able, it would be worth sending it for replacement under warranty to regain maximum internal storage space.
Sent from my Paranoid Android GT-N7000. It doesn't get much better than this!
Hey guys,
First of all, I'm new to this, so please bear with me. To cut a long story short, I attempted to install the CyanogenMod RC on my Galaxy Note N7000 today. I followed the instructions I found on the web somewhere (can't remember of it was XDA) and after attempting to wipe my device from the ClockwordMod, I appear to have bricked it.
My Note no longer gets passed the startup screen. I've tried everything I can to revive it, and I've been searching XDA all day for a solution, with little success. I've tried flashing a number of kernels, and a number of ROMs, including stock GB and stock ICS. I can still get into both Download and Recovery mode (which I'm hoping is a good sign) but when I try to flash a ROM with Odin, it gets stuck on the "factoryfs" stage.
I've tried flashing the PIT repartition file at least four or five times, but that doesn't seem to be helping at all.
Does anyone have any other ideas? I'd really just like to get back to stock ICS. I just fancied playing around with CyanogenMod for a bit, but I wish I hadn't tried. Thanks in advance for any help!
Were you on stock ICS when you did the wipe ?
Akiainavas said:
Were you on stock ICS when you did the wipe ?
Click to expand...
Click to collapse
Yes, downloaded via Kies.
I think you have fallen victim to the infamous eMMC "superbrick". Contact Samsung, they are well aware of this problem and will surely replace it for you as it's plaguing devices running their stock ICS. The problem is with their kernel and the eMMC chip to it doesnt even matter what were you trying to do.
When they do replace it - first, flash a GB rom via Odin, and then install CM9. CM9 kernel is safe and superbrick bug free. Whatever you do - never try doing a wipe/factory reset on stock Samsung ICS rom.
Akiainavas said:
I think you have fallen victim to the infamous eMMC "superbrick". Contact Samsung, they are well aware of this problem and will surely replace it for you as it's plaguing stock ICS devices. The problem is with their kernel and the eMMC chip to it doesnt even matter what were you trying to do.
When they do replace it - first, flash a GB rom via Odin, and then install CM9. CM9 kernel is safe and superbrick bug free. Whatever you do - never try doing a wipe/factory reset on stock Samsung ICS rom.
Click to expand...
Click to collapse
Yeah, I feared that was the case. The problem is, I now have the yellow warning triangle on bootup, and my "binary count" has increased to 9. Does this mean Samsung won't replace it?
if that's the case, is there any way to reset the binary count and remove the triangle in its current state?
You might try resetting the counter with a jig. I don't know if it will work in its state, but you may not have much to lose.
Sent from a guy on a buffalOOooo.
Generally - USB Jig is the only way to reset it on a bricked device.
There is one way other way though:
http://www.mediafire.com/?5bmrc6cf81w5mya
This kernel is supposed to reset binary counter, and many users reported that it actually did the trick - mind that this kernel also causes hard brick. It's a last effort for people whose devices are already bricked.
You nees to flash it via Odin, disconnect and go into recovery. At first boot you will still see the triangle - in the recovery, select reboot. Now the triangle should disappead, and binary counter should be set to "no".
Remember that this kernel causes a hard brick. Use it only if your device is already bricked and you intend to send it to Samsung. It will work only on ICS devices.
Akiainavas said:
Generally - USB Jig is the only way to reset it.
There is one way other way though:
http://www.mediafire.com/?5bmrc6cf81w5mya
This kernel is supposed to reset binary counter, and many users reported that it actually did the trick - mind that this kernel also causes hard brick. It's a last effort for people whose devices are already bricked.
You nees to flash it via Odin, disconnect and go into recovery. At first boot you will still see the triangle - in the recovery, select reboot. Now the triangle should disappead, and binary counter should be set to "no".
Remember that this kernel causes a hard brick. Use it only if your device is already bricked and you intend to send it to Samsung.
Click to expand...
Click to collapse
Thanks very much for your help. I really appreciate it.
So do you think it's worth contacting Samsung first - before trying to reset the binary - or do you think they'll refuse to replace it once they know I tried flashing an unsupported ROM?
Thanks again!
I think you might try contacting them first, just ask all the info you need without giving them the serial numbers - before you send the phone in. They might replace it anyway - they know very well it happens because of their defective kernel/emmc chip. Although i'm afraid they might find out and refuse to fix it for free.
If they turn you down, then flash the kernel and contact them again. If you're going to do it in person and they refuse cause they "remembered you" ( shocking, but it happens... ) then simply get a friend or family to bring them your phone.
Just say that Kies messed up your phone - they'll know what the problem is
Hope they'll get it fixed for you. Let us know how it went.
Akiainavas said:
I think you might try contacting them first, just ask all the info you need without giving them the serial numbers. They might replace it anyway - they know very well it happens because of their defective kernel/emmc chip.
If they turn you down, then flash the kernel and contact them again. If you're going to do it in person and they refuse cause they "remembered you" ( shocking, but it happens... ) then simply get a friend or family to bring them your phone.
Just say that Kies messed up your phone - they'll know what the problem is
Hope they'll get it fixed for you. Let us know how it went.
Click to expand...
Click to collapse
Okay, I'll do that. Thanks again for all the info! I'll let you know how I get on.
kill.i.an said:
Hey guys,
First of all, I'm new to this, so please bear with me. To cut a long story short, I attempted to install the CyanogenMod RC on my Galaxy Note N7000 today. I followed the instructions I found on the web somewhere (can't remember of it was XDA) and after attempting to wipe my device from the ClockwordMod, I appear to have bricked it.
My Note no longer gets passed the startup screen. I've tried everything I can to revive it, and I've been searching XDA all day for a solution, with little success. I've tried flashing a number of kernels, and a number of ROMs, including stock GB and stock ICS. I can still get into both Download and Recovery mode (which I'm hoping is a good sign) but when I try to flash a ROM with Odin, it gets stuck on the "factoryfs" stage.
I've tried flashing the PIT repartition file at least four or five times, but that doesn't seem to be helping at all.
Does anyone have any other ideas? I'd really just like to get back to stock ICS. I just fancied playing around with CyanogenMod for a bit, but I wish I hadn't tried. Thanks in advance for any help!
Click to expand...
Click to collapse
You may also try manual/adb repartition method described in here to revise your phone. cheers.
kill.i.an said:
Hey guys,
First of all, I'm new to this, so please bear with me. To cut a long story short, I attempted to install the CyanogenMod RC on my Galaxy Note N7000 today. I followed the instructions I found on the web somewhere (can't remember of it was XDA) and after attempting to wipe my device from the ClockwordMod, I appear to have bricked it.
My Note no longer gets passed the startup screen. I've tried everything I can to revive it, and I've been searching XDA all day for a solution, with little success. I've tried flashing a number of kernels, and a number of ROMs, including stock GB and stock ICS. I can still get into both Download and Recovery mode (which I'm hoping is a good sign) but when I try to flash a ROM with Odin, it gets stuck on the "factoryfs" stage.
I've tried flashing the PIT repartition file at least four or five times, but that doesn't seem to be helping at all.
Does anyone have any other ideas? I'd really just like to get back to stock ICS. I just fancied playing around with CyanogenMod for a bit, but I wish I hadn't tried. Thanks in advance for any help!
Click to expand...
Click to collapse
IF U CAN GET INTO RECOVERY UR NOT BRICKED OR SUPER BRICK TRUST ME I HAVE A NOTE HERE THATS BRICKED...IF INDEED ITS BRICKED U CANT GET IN ****!!! u just soft bricked it...flash stock recovery b4 tar or what ever it is
Sent from my SAMSUNG-SGH-I717 using xda premium
forest1971 said:
You may also try manual/adb repartition method described in here to revise your phone. cheers.
Click to expand...
Click to collapse
Thanks!
JB calhoun said:
IF U CAN GET INTO RECOVERY UR NOT BRICKED OR SUPER BRICK TRUST ME I HAVE A NOTE HERE THATS BRICKED...IF INDEED ITS BRICKED U CANT GET IN ****!!! u just soft bricked it...flash stock recovery b4 tar or what ever it is
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Stock recovery? Where would I find that?
The problem is, I cannot flash any ROM. It just hangs during the "factoryfs" process in Odin. When I try to install stuff via ClockworkMod recovery, it fails. Sometimes I get an error like "cannot mount (or access) /system."
JB calhoun said:
IF U CAN GET INTO RECOVERY UR NOT BRICKED OR SUPER BRICK TRUST ME I HAVE A NOTE HERE THATS BRICKED...IF INDEED ITS BRICKED U CANT GET IN ****!!! u just soft bricked it...flash stock recovery b4 tar or what ever it is
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Not true I'm afraid...
If you've damaged the eMMC chip:
- You can still get into recovery.
- You can still get into download mode.
If you did a factory reset on stock ICS kernel and can't flash "factoryfs" data because Odin gets stuck at this point, and repartitioning does not help - that's the "superbrick".
It happens because using data wipe on stock ICS kernel runs a format procedure which damages Note's defective eMMC chip. If it happened, repartitioning won't help as parts of the storage are corrupted and Odin simply cannot put data there. I seriosusly don't know how could Samsung not see that the format command introduced in ICS ( it was not present in GB, that's why GB kernels are safe ) damages the chip... didn't they test the software at all ?
Take a look here:
http://forum.xda-developers.com/showthread.php?p=28048062
This guy managed to recover his device, but what he's left with is Note with 3-4GB less storage, and remember that once the eMMC chip is damaged, it will never be completely reliable again.
Here's a guide on how to revive superbricked Note. Bear in mind it might not work though:
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
It's still best to try and get it replaced though. If Samsung won't replace it for free - then try reviving it.
Akiainavas said:
Not true.
If you've damaged the eMMC chip:
You can still get into recovery.
You can still get into download mode.
If you did a factory reset on stock ICS kernel and can't flash "factoryfs" data because Odin gets stuck at this point, and repartitioning does not help - that's the "superbrick".
It happens because using data wipe on stock ICS kernel runs a format procedure which damages Note's defective eMMC chip. If it happened, repartitioning won't help as parts of the storage are corrupted and Odin simply cannot put data there.
Take a look here:
http://forum.xda-developers.com/showthread.php?p=28048062
This guy managed to recover his device, but what he's left with is Note with 3-4GB less storage, and remember that once the eMMC chip is damaged, it will never be completely reliable again.
Here's a guide on how to revive superbricked Note. Bear in mind it might not work though:
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
It's still best to try and get it replaced though. If Samsung won't replace it for free - then try reviving it.
Click to expand...
Click to collapse
Yeah, I'm certainly going to speak to Samsung over the next few days. I'm going to wait a little while for my JIG to arrive and try to remove the binary count, then I'll give them a call. I don't see how they can refuse to replace it really —*it is their software that caused this (I think).
Keeping my fingers crossed.
Thanks for all the advice, guys.
kill.i.an said:
Yeah, I'm certainly going to speak to Samsung over the next few days. I'm going to wait a little while for my JIG to arrive and try to remove the binary count, then I'll give them a call. I don't see how they can refuse to replace it really —*it is their software that caused this (I think).
Keeping my fingers crossed.
Thanks for all the advice, guys.
Click to expand...
Click to collapse
JIG is probably the best thing to do. Clear the counter, get rid of triangle and send it in. As you said - it's Samsung's kernel that causes this, and they know it.
Good luck mate.
Okay, here's a surprise: Because I can still enter download and recovery mode, I decided I would try to reset the binary counter before my JIG gets here. So I downloaded the kernel from another thread, and it worked perfect. I then tried to flash the stock ICS ROM so that there was no evidence of another one, and this time it didn't get stuck on "factoryfm" in Odin.
So I now have a working Galaxy Note. I have no idea how that happened (maybe the PIT I flashed earlier kicked in), but it's working.
Now the question is, do I attempt to install CyanogenMod again, or should I just stick to a working Galaxy Note and be happy?
Stay with what you have.
Sent from my GT-N7000 using xda app-developers app
kill.i.an said:
Okay, here's a surprise: Because I can still enter download and recovery mode, I decided I would try to reset the binary counter before my JIG gets here. So I downloaded the kernel from another thread, and it worked perfect. I then tried to flash the stock ICS ROM so that there was no evidence of another one, and this time it didn't get stuck on "factoryfm" in Odin.
So I now have a working Galaxy Note. I have no idea how that happened (maybe the PIT I flashed earlier kicked in), but it's working.
Now the question is, do I attempt to install CyanogenMod again, or should I just stick to a working Galaxy Note and be happy?
Click to expand...
Click to collapse
How much capacity do you have on your internal storage? If it is less than 11GB you may have a damaged chip and just managed to unbrick it.
I think if you can flash GB with Odin you should be fine, and once you get to GB everything is (relatively) safe.
I had a similar problem when I was trying to flash GB from stock ICS using odin, it stuck at FactoryFS and I thought I had superbricked it, but it turns out I was using a dodgy USB cable and using a good USB cable I managed to flash GB again and recover it, and now I am using CM9 - Never going back to stock ICS after this.
Hi there fellow time bomb owners!
Let me start out........... Ive had my note for many months now. Ive flashed many GB and ICS roms, both TW and AOSP.
Ive always been very careful with the brick bug issue and always flashed every rom via the OP's method to the letter.
I finally settled with Kingdroid. After running it for nearly 2 months without ever having a random reboot/FC or any issues at all it started to misbehave, crashing, freezing and somtimes making me resort to battery pulls!
This all culminated last night, when after installing an app, I tried to open the said app and the phone froze on me. I long pressed the power button to reboot and then got stuck in a bootloop. In all my months with my Note ive never had a bootloop. I could still get into recovery and download so I thought no big deal.
I tried to wipe the cache and davlik cache to see if there was any nasties in that causing the bootloop. They both wiped fine but when I rebooted the loop was still there. Still Not a problem I thought, I will just have to reflash. Pain in the ass I know, but at least Im not bricked. So I placed abyss kernel and kingdroid onto my SD booted into recovery and went to flash Abyss. All went well so went to reboot recovery and........Boom in some kind of elongated (graphically) version on the same recovery I had before? Not abyss? Ok, it must not have taken properly, flash it again, as soon as I went to move through the recovery menus the recovery restarted, not rebooted, just restarted? It did this everytime I tried to move in the menus? I though thats very odd indeed? then all on its own it started to restart? Then I worried, could this be damage to my partitions or emmc in general? Never done any wiping on unsafe kernels, surely it cant be?
So I resorted to Odin and the factory firmware I keep for warranty purposes. Plugged everything in and set it running. The phone was recognized, Md5 checked then.................Couldnt open COM port to device? S**T, F**K. I must be bricked now I thought. So as all good software people do, I unplugged everything rebooted my computer and tried again. It worked this time around!? I was a little nervous going through the FACTORYFS bit but it took, pass! Yes! Booted into stock recovery did the full wipe and now all is well with my note, all be it on stock nastiness.
I apologize for the lengthy post but I think its important to share potentially dangerous behaviour in depth with the note community. Many people may have had a panic and jumped straight on the Brickbug bandwagon (as I nearly did).
So after all that I would like to know if someone far more intelligent than me could give a possible cause? Not only out of curiosity but so that people (and me!) could avoid this worrying behaviour. And also how or if you can check your EMMC for bad blocks without Root and the emmc checker app?
If you read all this, well done! and thankyou for looking,
x5starguerillaa said:
Hi there fellow time bomb owners!
Let me start out........... Ive had my note for many months now. Ive flashed many GB and ICS roms, both TW and AOSP.
Ive always been very careful with the brick bug issue and always flashed every rom via the OP's method to the letter.
I finally settled with Kingdroid. After running it for nearly 2 months without ever having a random reboot/FC or any issues at all it started to misbehave, crashing, freezing and somtimes making me resort to battery pulls!
This all culminated last night, when after installing an app, I tried to open the said app and the phone froze on me. I long pressed the power button to reboot and then got stuck in a bootloop. In all my months with my Note ive never had a bootloop. I could still get into recovery and download so I thought no big deal.
I tried to wipe the cache and davlik cache to see if there was any nasties in that causing the bootloop. They both wiped fine but when I rebooted the loop was still there. Still Not a problem I thought, I will just have to reflash. Pain in the ass I know, but at least Im not bricked. So I placed abyss kernel and kingdroid onto my SD booted into recovery and went to flash Abyss. All went well so went to reboot recovery and........Boom in some kind of elongated (graphically) version on the same recovery I had before? Not abyss? Ok, it must not have taken properly, flash it again, as soon as I went to move through the recovery menus the recovery restarted, not rebooted, just restarted? It did this everytime I tried to move in the menus? I though thats very odd indeed? then all on its own it started to restart? Then I worried, could this be damage to my partitions or emmc in general? Never done any wiping on unsafe kernels, surely it cant be?
So I resorted to Odin and the factory firmware I keep for warranty purposes. Plugged everything in and set it running. The phone was recognized, Md5 checked then.................Couldnt open COM port to device? S**T, F**K. I must be bricked now I thought. So as all good software people do, I unplugged everything rebooted my computer and tried again. It worked this time around!? I was a little nervous going through the FACTORYFS bit but it took, pass! Yes! Booted into stock recovery did the full wipe and now all is well with my note, all be it on stock nastiness.
I apologize for the lengthy post but I think its important to share potentially dangerous behaviour in depth with the note community. Many people may have had a panic and jumped straight on the Brickbug bandwagon (as I nearly did).
So after all that I would like to know if someone far more intelligent than me could give a possible cause? Not only out of curiosity but so that people (and me!) could avoid this worrying behaviour. And also how or if you can check your EMMC for bad blocks without Root and the emmc checker app?
If you read all this, well done! and thankyou for looking,
Click to expand...
Click to collapse
Mate, feel for the brown pants time you've ordealed, glad you got out of it. I'm fairly certain, although no dev, that there is an incremental damage obtained via certain kernels, be it wipes or even large file transfers. There's an app that can judge if any sectors are past repair...
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
So at least you know if it's an emmc issue. Let me know.
Sent from my GT-N7000 using xda app-developers app
Cheers for the link.
Do you know of a way that I can check for bad sectors without that app? It needs root and I dont really want to flash/root anything until I can (if possible) determin whether or not Im damaged.
The only reason I ask is that now is the phone is primed ready to go back to samsung if so.
No counter or triangle or reminants of root.
Sent from my GT-N7000 using xda app-developers app
accessing the internal NAND flash memory of your phone requires root privileges. Without Root, The System would simply deny you poking and probing on the internal storage of your phone.
That is why it is important to Root.
On the lighter side. You can actually Root your phone.. use that app to know if your phone has bad sectors and once you've done knowing it... you can simply UNROOT your device.
In that way, Samsung would never know the how's and wherefore's if you have tinkered your device or not.
Simple as that.
Ok. I rooted with a older version of GB.
Checked the NAND and everything says its ok. So I put it back to the latest GB uk firmware, updated via KIES to latest ICS and then rooted with the super su.zip and the full root busybox.zip from Dr Keatens post.
So im now running the latest stock firmware with full root. Can I install a rom from where Im at now? With stock recovery with full root? Or do I need to flash a kernel like abyss first to get the red pill recovery?
Sent from my GT-N7000 using xda app-developers app
Things may have changed but I think general guidance is to flash from rooted gb kernel like abyss or stock. Certainly for AOSP roms like cm9 variants or cm10 that's the case.
Sent from my GT-N7000 using xda app-developers app
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.