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
Related
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd? The reason I ask is because I have been bouncing between cognition and paragon for about 2 weeks now NOT using the method of flashing back to stock 2.1 without a single problem. I'm sure there is a good reason flashing back to 2.1 before trying new roms, I would just like to know why. I was able to preform a stock wipe using odin3 one time last week (just did it to make sure the phone would do it) it just seems like a really long process, but I'll start doing it that way to avoid a brick.
Thanks
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
For the most part, you don't really need to flash back to stock. It used to be a bigger deal to flash back to stock because some of the Roms would intervene with each other and mess things up. It is still recommened for a clean flash, but I rarely do it and my flashes work great.
EDIT: @Trusselo: damn it! Second time someone beat me to the answer tonight!
HAHA
and forget ODIN ONE CLICK !!
i keep forgetting about this
http://forum.xda-developers.com/showthread.php?t=944418
ALL IN ONE CAPTIVATE TOOLBOX
I have been trying roms weekly since November and have only needed to flash to stock twice, after failed flashes caused by my lack of patience. YMMV of course
jayjr1105 said:
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd?
Click to expand...
Click to collapse
It's not necessary and not even a good idea. Also, why wipe cache and d-cache when the install script does that?
Trusselo said:
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
Click to expand...
Click to collapse
ROMs don't mod or use any files which are on the phone prior to installing them. All the files on your phone after the install were in the CWM flashable zip file. Any ROM cook would be stupid to do otherwise. The exception would be no-wipe ROMs, but you would never flash to stock before using one of those.
Ive also wondered this as well and talking to guys like opcow, and a couple other Devs such as MikeyMike and a lot of guys at the Andromeda IRC they all agree that you should be perfectly fine now as long as you wipe everything before you flash.
I may try with Andromeda when I get home because I have my PC and Jig there just in case but still may try now. But also tlaking to a lot of users that they dont even do it anymore now because of the install scripts and as Opcow said if you think logically its technically safer.
Trusselo said:
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
Click to expand...
Click to collapse
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Dlev7 said:
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Click to expand...
Click to collapse
+1 Guys if you don't know exactly what to do/suggest please don't say it. I'm not trying to start a war, but a wrong suggestion can easily soft or hard brick someones phone. This is a forum, so no one can stop you from saying things, but think about if it happened to you? You would be pissed!
Anyways back on topic, what model phone do you have, because having a 1009 model phone makes flashing and going back to stock (usually) so much easier. But then again, I rarely use odin because all the roms are compatible for the most part.
Sent from my SGH-I897 using XDA App
I've never used ODIN because I haven't wanted to try to run it from GNU/Linux in a virtual box.
I just wipe and flash from clockwork like the op. Been flashing roms for a couple months now, never had a single problem. (except when I noobed it up by trying to flash back to a nandroid backup via Rom Manager. Even then, didn't need Odin to sort it out).
If I ever run into a problem, then I'll try Odin, but I'm waiting to cross that bridge till I come to it.
To prevent exceptions or troubles from the version you already have... so everybody comes from the same rom, understand?
I flash to jf6 because that's what I have been conditioned to do for a while. However, the few times I was impatient and didn't....no problems either.
From all the reading I've done here, the only reason to do it is for the placebo effect.
There was once a time when all the new roms were built on the unofficial froyo and it only had 3e recovery. The quickest way to get around that was to flash stock. Also the lag fixes were tricky and easily fixed by flashing stock. Now recovery is in the kernel. As long as you insure the kernal lag fix in rom A understands the kernal lag fix in rom B flash away. Nandroid backups are kind of useless they don't backup the kernal or the modem. Save odin for when things go really wrong(;~ )
Sent from my i897 using XDA App
I have done it both ways, and there its no difference going back to stock and or flashing over other roms. I flash often, have not got stick in boot loop in months
I like to go back to stock since I KNOW that everything has been defaulted back to normal. Just a security blanket step for me.
I flashed andromeda over darkyy 9.3 just wiping data cache and d cache. Nothing wrong. Everything worked perfect so I got to believe that if you just wipe everything it should work perfectly.
Just for safety I got a jig and odin but for now I'm saving a good 45 minutes to not flash back to stock
Sent from my SGH-I897 using XDA App
Okay so..
I have to spend my days serving my time in the finnish army, so I am a bit clueless of the GNote scene from time to time. I ran Midnote LPF (?) ICS for quite some time and then tried to decrease my DPI. Unfortunately, this resulted in a bootloop, and I tried to fix it by factory reset. Whoop-de-doo. I cancelled it mid way though, if I remember correctly.
8 hours later I got my hands on a computer and tried flashing a firmware with pc-odin. Didn't work. Here's where I've gotten so far:
Flashing PIT and CWM based recovery v5.0.2.7
Flashing Kingdroid ICS Via CWM based recovery or AbyssNote causes phone to reboot at "Flashing /system"
Trying to flash stock GB via Odin hangs at "factoryfs.img"
Tried to reflash bootloader, no help.
Currently trying out flashing GB rom via CWM recovery.
I need quick help as I am going to a Battle-excercise for two weeks tomorrow and I'd really appreciate have my GNote working by that time..
Thank you very much in advance
EDIT: I can confirm that the partinioning guide in http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12 IS INDEED an effective guide to un-superbrick. The guide can be very intimidating for beginners, so bear that in mind. I ran into a faulty partition on the UMS folder, and repositioning it did the trick. Then I just rebooted recovery and installed KingDroid 7.0 GB and it opened like a charm.
Big chance you have a superbrick now, sending it to Samsung repair center is the only option. Search for "superbrick" in this forum. You'll find my name also
I had to send in my device and probably get it back on wednesday...with a new mainboard. On my device a recovery always ended at /system and a pc odin reflash always stopped at factoryfs.img
The last option without sending in your device is following a few threads here. Some posters were talking about a possible solution.
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Posibly meaning this.. I am trying to run this through and will post results.
Yep, that's one of the posts. This was way too complicated for me.
I've send my Note to a samsung service center and they repaired it without any costs. I only reset the binary counter to zero and (partly...because of factoryfs.img) flashed a stock rom before sending the device.
Morality said:
http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Posibly meaning this.. I am trying to run this through and will post results.
Click to expand...
Click to collapse
Sounds like a superbrick. Unless you are willing to go through the partitioning experience, I recommend sending it back.
joe2316 said:
Sounds like a superbrick. Unless you are willing to go through the partitioning experience, I recommend sending it back.
Click to expand...
Click to collapse
Im not gonna lie, It was a scary as **** experience. Currently trying to install.. well.. anything.
oh
my
GOD
ITS ALIVE OH MY GOD ITS ALIVE...
the guide worked.. But definately not recommended for beginners, as the dos prompt might be quite intimidating. but the thing definately works.
I found a bad partition from UMS and just relocated it a bit. I think I lost 3gb of space (not sure, will check on that), and unfortunately it formats your INTERNAL sdcard, as i backuped my external one.. BUT WHATEVER
JESUS CHRIST IT WORKED. After following the guide, recovery needed to be rebooted and then I just installed Kingdroid 7.0 GB. The only problem that appeared was that the Samsung Logo screen lasted longer than usually when flashing new firmware. Will update OP.
Hi,
I am really confused, yesterday I flash Alba LQ2 rom latest full with no problems.
I like ICS its very good but slight problems occurred today.
This all happened during my travels to London in the train.
so I noticed my note did not go to deep sleep, so read in the forums to put on flight mode, turn off phone. take out batteries for a few mins(in my case 5 mins), put it back in turn on phone and turn off flight mode.
I did that but when I attempted to turn on the phone it just stayed on the samsung logo flashing white and blue for 20 minutes. I restarted it and the same thing.
As this happened in the train i panicked. I went to CWM with no problems and tried to flash the same rom again without clearing any data or cache and so on.
the following came up:
CWM-based Recovery v5.0.2.7
-- Installing: /emmc/AlBa_XXLQ2_Full.zip
Finding update package...
Opening update package...
Installing update...
AlBa XXLQ2 Full
and the bar where it shows it working stayed empty for 15 or so minutes, so i got annoyed and tried it again, went back to cwm without a problem did the same and the same thing popped up. I've kept it till now and it is still the same for the past 1 hour and 20 or so minutes.
I don't want ICS anymore, I just want to go back to GB right now. Have I bricked my note? if not, can anyone guide me to get back to GB if possible.
Thanks in advance.
oh and my phone was not overheating whatsoever. it seems cool till now.
assuming no one has replied, just to say, ive sorted it out, i restored to a rooted gb rom via pc odin and then wiped data. and now its fine, may give paranoidandroid a shot.
You may have to give your flashing hobby a breather for now.. .you just came from a nearly brick experience and now you want to try to flash another ROM again?
Sooner or later, you may encounter that infamous HARD BRICK BUG that people are saying all over the Galaxy's Note's thread..
Just caveat in flashing or changing ROM always...
you never know what your gonna get until you will finally get it....
Cheers!.
From what I gather so far, you were smart enough to not wipe data or anything so you were not bricked at all with the eMMc bug and you knew what to do on your own (probably by reading the forums) which I would say I am proud of you for.
You did correctly by flashing to Gingerbread. Now, you want to try ParanoidAndroid (I must say it is fantastic). It's based on CM9 so it's easy. Since you are on GB, make sure you are rooted. Flash the CWM.zip file (in drketan's thread). Then, flash ParanoidAndroid. Wipe cache, dalvik cache, and data. Reboot. Enjoy awesome hybrid settings.
thanks both of you. oh my, i must paranoidandroid is really good, never thought i could witness so much from a community built rom.
yh I didn't wipe data when i was at ics, i knew the phone will die if I did. anyhow thanks.
@letters_to_cleo, i guess your right, ill stop flashing for a while.
the reason i do this, its just because I have some knowledge on the linux world coming from n900 maemo and so on its all good fun and interesting to see how open android really is.
If you read the OP and stickies, you will be fine. So, continue flashing! It's fun when you follow the rules given.
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.
ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.
i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
drastic00 said:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.
http://forum.xda-developers.com/showthread.php?p=39269819
Part 1 can be tricky, so take your time and get that right before proceeding.
Click to expand...
Click to collapse
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
I missed that you wiped bootloader. You need that . So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)
http://forum.xda-developers.com/showthread.php?p=39130435
I think Jellycream actually requires you have it, if I remember correctly.
Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.
Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
drastic00 said:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.
Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.
I'm just trying to understand why a factory reset could brick your phone...
Click to expand...
Click to collapse
ok basic rundown of what i did in the last year;
when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.
after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.
failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.
ill find links when i get off work today. thats the basic history of the phone though.
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
http://forum.xda-developers.com/showthread.php?t=2392309
thats the jellycream rom.
im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
drastic00 said:
Oh, ok, OptimusRS's ROM.
Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.
Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.
If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
Click to expand...
Click to collapse
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.
will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.
HUGE thanks regardless
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
drastic00 said:
Cool :thumbup::beer:
The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.
The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
Click to expand...
Click to collapse
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.
You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.
Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.
Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.
I have not actually measured the speed in either, however.
And for either of those ROMs, you must flash his large partition version of v28B first...very important.
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.
my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.
side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...
If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?
Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.
I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.
You can usually flash to recover from a problem, but then you have to set your phone up again
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
Sent from my LG-P920 using xda app-developers app
I'd try another baseband.