Related
So just got back my phone from samsung. I hard bricked it after messing with GB bootloaders. My bad. Anyway, they said to fix it they had to replace the PBA? Anyone help me on what this is? Also, how do i know if this still has GB boots on it? I'm thinking they completely cleared this thing out. It's running 2.2, with 3e recovery. Pretty sure everything GB is gone from this phone, just trying to be sure. I plan on keeping it simple with this phone and rooting and flashing a 2.2 rom w/o bootloaders, so I know that won't be a prob, I just want to make sure that if I do mess with boots, I'll know what's currently running so I won't brick again. Btw, don't really want to mess with oneclick, cuz it's a 1010 build and I know that is causing some issues with oneclick.
Does it say galaxy s when you boot?
Sent from my GT-I9000 using XDA Premium App
Yeah, it does all the original annoying galaxy s swooshing crap. Like I said I'm pretty sure this thing is stock 2.2 froyo, just need that assurance that i won't have bootloader issues. Kinda timid after the first brick. At least Samsung fixed it under warranty.
If it has the GB bootloaders the key combos are different. Power off, hold volume down and power, if you get download mode it's GB bootloaders.
Sent from my Captivate running GR-12
Cdub3 said:
So just got back my phone from samsung. I hard bricked it after messing with GB bootloaders. My bad. Anyway, they said to fix it they had to replace the PBA? Anyone help me on what this is? Also, how do i know if this still has GB boots on it? I'm thinking they completely cleared this thing out. It's running 2.2, with 3e recovery. Pretty sure everything GB is gone from this phone, just trying to be sure. I plan on keeping it simple with this phone and rooting and flashing a 2.2 rom w/o bootloaders, so I know that won't be a prob, I just want to make sure that if I do mess with boots, I'll know what's currently running so I won't brick again. Btw, don't really want to mess with oneclick, cuz it's a 1010 build and I know that is causing some issues with oneclick.
Click to expand...
Click to collapse
PBA = Printed Board Assembly. It's the main circuit board in the phone.
The GB bootloaders are almost certainly gone. You should be able to tell by booting into recovery.
Hi all,
I have flashed my phone a few times (actually only once to perception, and then recently back to stock before then flashing stock rogers 2.2 - as I didn't have internet at the time to use kies, even though I am US based). I am currently traveling around Europe, and will be heading to the UK soon from Sep-Dec. As such I would like to unlock the phone and use an Orange or Vodafone pay as you go sim.
Unfortunately when I tried to unlock the phone I was unable to, I am assuming because the rom on there (stock rogers 2.2) doesn't have some of the correct things...(sorry for not being more specific).
Right now my plan is to reflash back to stock 2.1 and try and unlock from there? I don't want to turn this into a "what rom should I use now" thread, but is there an good battery life 2.2 rom that would let me unlock. I've looked into flashing a 2.3 rom, but it seems like more work than I am willing to put in right now (although I'm sure it's not tooo hard, I don't have a ton of experience flashing, and I can't afford to really screw this phone up right now), especially with AT&T announcing they will be upgrading it to 2.3 sometime "soon" (hah).
Sorry I know this is a long post and not especially clear, but I'd really really appreciate the help.
thanks,
-Foofie
Hmmm, maybe flashing to gingerbread isn't as hard as I thought it was? According to this:
http://forum.xda-developers.com/showthread.php?t=1127249
it's just an odin 1 click now? Maybe it always has been and I'm an idiot, I wouldn't be surprised. So if I flash back to stock 2.1 and then flash to 2.3 using the above method (although I'm a bit confused about the extra files on that page, why do I need to change the kernel, how do I do so?) could I unlock the phone at that point? Or would I need to flash to a custom rom like cognition 5 or perception first?
Just flash to 2.1 root and unlock it from there. After that it will be unlocked and you can flash whatever. I've unlocked once six months ago flashed 1,000,001 times, still unlocked.
studacris said:
Just flash to 2.1 root and unlock it from there. After that it will be unlocked and you can flash whatever. I've unlocked once six months ago flashed 1,000,001 times, still unlocked.
Click to expand...
Click to collapse
Ahhh thanks, this is what I was hoping to hear!
So even flashing with Odin wouldn't reset the unlocking? Doesn't Odin wipe all the phone data?
Not ALL data. The efs folder contains the imei number which is unique to each device. Just make sure and back that up (the efs folder), so if you have any network connectivity issues you can restore your imei...
Thanks.
God flashing to 2.2 the way I did was a huge mistake. Trying to flash back to stock soft bricked (hopefully that is what this is) my phone. Trying to get heimdall running now so I can use the 1 click unbrick.
Well let me just skip to the issue,
Flashed with KIES to latest ICS, came from GB. No root, no nothing just stock !!
After reading and reading and did some more reading i think it's time to ask the experts.
I know that ICS has the superbrick bug, i know that GB doesn't. Well the solution is that just for a precaution i would go back to GB (LOL) but here is the issue: if i go back to GB i might get bricked (right??) if i don't go back i might get bricked with a full wipe (factory reset included??). Ok if i flash ANY rom and kernel included i will get the chance to get bricked???
All roms and kernels do a full wipe before installing a new one, this i know. So where are my options ?? Flash back to GB and might get bricked, wait for samsung response and might get bricked then, try any other rom (with or without root) and may get bricked??? As far as i see it i may get bricked with all these options. Maybe i get lucky ??? Yeh right with my life......
Please explain this to me as i'm not getting any solution with all the threads (+ 1 from me) that are here.
becosemsaida
becosemsaida said:
Well let me just skip to the issue,
Flashed with KIES to latest ICS, came from GB. No root, no nothing just stock !!
After reading and reading and did some more reading i think it's time to ask the experts.
I know that ICS has the superbrick bug, i know that GB doesn't. Well the solution is that just for a precaution i would go back to GB (LOL) but here is the issue: if i go back to GB i might get bricked (right??) if i don't go back i might get bricked with a full wipe (factory reset included??). Ok if i flash ANY rom and kernel included i will get the chance to get bricked???
All roms and kernels do a full wipe before installing a new one, this i know. So where are my options ?? Flash back to GB and might get bricked, wait for samsung response and might get bricked then, try any other rom (with or without root) and may get bricked??? As far as i see it i may get bricked with all these options. Maybe i get lucky ??? Yeh right with my life......
Please explain this to me as i'm not getting any solution with all the threads (+ 1 from me) that are here.
becosemsaida
Click to expand...
Click to collapse
If Kies has provided you with the ICS update, i.e you don't have any Custom Roms installed, then where is the issue? That means you're perfectly safe.
becosemsaida said:
Well let me just skip to the issue,
Flashed with KIES to latest ICS, came from GB. No root, no nothing just stock !!
After reading and reading and did some more reading i think it's time to ask the experts.
I know that ICS has the superbrick bug, i know that GB doesn't. Well the solution is that just for a precaution i would go back to GB (LOL) but here is the issue: if i go back to GB i might get bricked (right??) if i don't go back i might get bricked with a full wipe (factory reset included??). Ok if i flash ANY rom and kernel included i will get the chance to get bricked???
All roms and kernels do a full wipe before installing a new one, this i know. So where are my options ?? Flash back to GB and might get bricked, wait for samsung response and might get bricked then, try any other rom (with or without root) and may get bricked??? As far as i see it i may get bricked with all these options. Maybe i get lucky ??? Yeh right with my life......
Please explain this to me as i'm not getting any solution with all the threads (+ 1 from me) that are here.
becosemsaida
Click to expand...
Click to collapse
You should be OK if you haven't done any wipes/factory resets/formats since you installed your stock ICS. If you haven't done any of those, use PC Odin to go back to GB like this:
http://forum.xda-developers.com/showpost.php?p=25285584&postcount=3
Thank you for talking the time to respond me. I will get back to GB and avoid (for now or at least untill it's safe) the updates from samsung.
becosemsaida
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.
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.