Related
hi all
got the official update to ICS yesterday and now my phone is awful!
unlocking is slow, swiping is slow, typing is slow, most apps crash! whats happened?!
ive read that a factory reset will fix issues but will this loose everything i have on the phone? i dont want to have to start again on games etc just had it the way i liked.
any help or info on factory reset?
ps phone is not rooted and as is out the box
I installed the update afew days ago but i have not noticed that at all on the samsung stock launcher. Now cus i use hi launcher its abit laggy but apps n internet is superfast for me.
I wont hold my breath thoe on the decent speed. My reboots might stil happen but not as yet.
Sent from my GT-N7000 using XDA
How did you update? Did you re cover apps throught a certain tool?
Bad thing about updates are the mess old stuff leaves, or create when recovering. Stock as well as custom. That's why clean install is best.
So sad its needed
Be carefull with factory reset because of ics bug, but that together with. Wiping cache or dalvik cache have been reported to work. Again be carefull cause of ICS bug, a wipe or factory reset can destroy your phone. Enought threads on that.
Sent from my GT-N7000 using Tapatalk 2
i updated from the indian rom yesterday to the official lq2 and find it much smoother and snappier i dont have permanent cwm i do have root if its that bad either reflash the rom to see if it was a bad flash or do a factory reset
thanks for the replies!
whats dalvik cache??
i think ill have to reinstall :-(
I updated to the German rom last month and had to do a factory reset afterwards to clear up a few issues.
There have been reports of phones bricking while factory resetting (though very very few reports tbh) but so long as you updated officially (ie your phone told you an update was ready, or you did it over kies air) then you should be safe enough, even if your phone does die you'll be fully covered by your warranty as factory resets are a perfectly normal function of the phone.
Ftb
well i had to do a factory reset went for the gamble and so far its working ok.
had problems with kies trying to backup up ive never got that to work correctly. only thing ive really lots is my save for wheres my water lol
thanks for all the help xx
Flashed UK ICS stock with mobile Odin + speedmod kernel .one reboot then one hit code *2767*3855# Full Factory format Reset and its quite smooth and nice result.
scrott901 said:
well i had to do a factory reset went for the gamble and so far its working ok.
had problems with kies trying to backup up ive never got that to work correctly. only thing ive really lots is my save for wheres my water lol
thanks for all the help xx
Click to expand...
Click to collapse
Try flashing the speedmod kernel using Odin pro. It will definitely improve your experience.
Sent from my GT-N7000 using XDA
When I first got the phone a few weeks ago i was prompted to update to ICS as soon as I connected to wifi. I did so (before reading these forums) and had no issues. After playing wtih phone for a while and deciding I wanted to keep it, rooted it (using rootgalaxynote.com method) and I popped in my SIM and activated it. This somehow screwed up my dialer (such that it would force close after one number) so I factory reset it. It reset perfectly as far as I can tell and i've now been using the phone for the last 2 weeks without issue.
I keep reading here that doing this should have bricked my phone. But it did not. Is there an explanation for this? Here are details about my phone:
ICS 4.0.3
Kernel: [email protected] #3 SMP PREEMPT Fri May 4 2012
Build number: IML74K.XXLPY
eMMC:
Type: vyl00m
Date: 03/2012
FwRev: 0x19
eMMC check says: Brickbug? Yes. Insane chip.
I also now read that so long as I don't install any ROMs or do another factory reset i'm ok, but that I should install a kernel like speedmod v3. I'm naturally concerned about all this conflicting information. I'm happy with stock ICS. Will installing this kernel really fix the emmc brickbug issue?
My mate had stock and did a factory reset as he was having lag after upgrading from gb. Yesterday I tried to root and in cwm it failed when i tried to get file from internal sd by saying
Error can't mint e:/emm/ or something along those lines. I think his emmc is corrupted. His ics works fine though.
Sent from my GT-N7000 using xda premium
indie said:
My mate had stock and did a factory reset as he was having lag after upgrading from gb. Yesterday I tried to root and in cwm it failed when i tried to get file from internal sd by saying
Error can't mint e:/emm/ or something along those lines. I think his emmc is corrupted. His ics works fine though.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Ahh. I don't have CWM installed so I can't tell you if mine does this too. All I did was root it. I didn't put any custom kernel on there so I don't have CWM. From what i've read, in ICS the kernel is how recovery changed from samsung recovery to CWM recovery. Someone correct me if i'm wrong.
I did root it no problem using CWM-SuperSU-v0.87.zip though. Did you attempt this method and this is where you got the e:/emm/ error?
The bricks happen on a hit and miss basis.
Sent from my GT-N7000 using xda app-developers app
praetorius said:
The bricks happen on a hit and miss basis.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Sure seems so. Interestingly I had an epic 4g touch which had the same ICS bug. Before I switched to the note I remember seeing a thread about a guy who flashed 25-30 roms before he bricked randomly. I think we have our answer here. It may take 25-30 flashes I guess?
I did just use CWM to flash speedmod k3-3. I'm not sure what else it does besides prevent a hard brick. Now my kernel reads:
3.0.15
[email protected] #k3-3
SMP PREEMPT Sun May 27 22:49:18 SGT 2012
I should be ok until samsung releases an official fix?
Also, if I wanted to flash cyanogenmod i'd have to downgrade to GB stock before doing so? That is the only known safe method at this point?
Yes to go to any CM / AOSP ROM you must go back to GB first
As for you avoiding the brick...... Your lucky, I wouldn't recommend doing it again, I see your on a Safe kernel now so stick with that.
Samsung are apparently working on a fix, But all that fix will be is bypassing the MMC_CAP_ERASE command but on stock kernels, Its the actual chip at fault, They cant fix the chip with updates.
Any way, thank god you didnt brick your phone, and be careful in future, you got lucky, your not superior to the rest of us lol
My mate did not put a cf kernel either. He just loaded the temp CWM via stock recovery and rooted. He then went to install a zip via sd card and it keeps coming up with e:/can't mount emmc/ but internal card works fine.
LxMxFxD said:
When I first got the phone a few weeks ago i was prompted to update to ICS as soon as I connected to wifi. I did so (before reading these forums) and had no issues. After playing wtih phone for a while and deciding I wanted to keep it, rooted it (using rootgalaxynote.com method) and I popped in my SIM and activated it. This somehow screwed up my dialer (such that it would force close after one number) so I factory reset it. It reset perfectly as far as I can tell and i've now been using the phone for the last 2 weeks without issue.
I keep reading here that doing this should have bricked my phone. But it did not. Is there an explanation for this? Here are details about my phone:
ICS 4.0.3
Kernel: [email protected] #3 SMP PREEMPT Fri May 4 2012
Build number: IML74K.XXLPY
eMMC:
Type: vyl00m
Date: 03/2012
FwRev: 0x19
eMMC check says: Brickbug? Yes. Insane chip.
I also now read that so long as I don't install any ROMs or do another factory reset i'm ok, but that I should install a kernel like speedmod v3. I'm naturally concerned about all this conflicting information. I'm happy with stock ICS. Will installing this kernel really fix the emmc brickbug issue?
Click to expand...
Click to collapse
Good for you then... Cause my mine is Bricked and i brought it to Samsung Service Center. They fixed it by changing my Motherboard... Good thing i have a Warranty.
azzledazzle said:
Yes to go to any CM / AOSP ROM you must go back to GB first
As for you avoiding the brick...... Your lucky, I wouldn't recommend doing it again, I see your on a Safe kernel now so stick with that.
Samsung are apparently working on a fix, But all that fix will be is bypassing the MMC_CAP_ERASE command but on stock kernels, Its the actual chip at fault, They cant fix the chip with updates.
Any way, thank god you didnt brick your phone, and be careful in future, you got lucky, your not superior to the rest of us lol
Click to expand...
Click to collapse
Ok cool. You brits and your pluralizing companies always throws me off. Every time.
Speedmod seems to have lowered my benchmark scores significantly but otherwise it seems as snappy as before. Does speedmod have built in cpu governors that restrict top speed or anything of that nature? If so, can this be changed?
ryn888 said:
Good for you then... Cause my mine is Bricked and i brought it to Samsung Service Center. They fixed it by changing my Motherboard... Good thing i have a Warranty.
Click to expand...
Click to collapse
how long did it take untill you got your phone back? because mine bricked after a stock factory reset.
azzledazzle said:
Yes to go to any CM / AOSP ROM you must go back to GB first
As for you avoiding the brick...... Your lucky, I wouldn't recommend doing it again, I see your on a Safe kernel now so stick with that.
Samsung are apparently working on a fix, But all that fix will be is bypassing the MMC_CAP_ERASE command but on stock kernels, Its the actual chip at fault, They cant fix the chip with updates.
Any way, thank god you didnt brick your phone, and be careful in future, you got lucky, your not superior to the rest of us lol
Click to expand...
Click to collapse
I was also lucky, apperently - cause I also flashed 4.0.3 German Stock (N7000XXLPY_N7000OXALPY_N7000XXLPT_HOME.tar.md5 flashed with Odin) this summer - happily unknowing of the HW problems with Samsungs flash circuit :angel:
I was up and running, but things was not fine - a lot of progrmas worked strange so I did a factory reset and everything was fine:good: but I'm feelling lucky enough to repeat the procedure....
I'm thinking about updating to the newly leaked Samsung JB test stock 4.1.2 (N7000XXLS2.tar.md5)
- What is the safe road here ? Is it OK(=safe) to flash 4.1.2 through Odin, restart the phone and make a factory reset if nessasary ?
OR must I go back to GB (and I suppose when doing this for ICS update, you make factory reset on GB and then update to ICS) and then flash 4.1.2 through Odin and restart.
Thanks for any help :good:
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
Hello everyone, Thank you for taking your time to look at thi and sorry for my bad english.
I have used my I9305 for 4 months until now without any fault. It was on official 4.1.2 XXBME3 stock rom with stock kernel but rooted, Philz Touch recovery. I have flashed PAC and Sentinel Rom before(2 months ago I think) but didnt stay on them as they had bugs to use as a daily driver. So it was on always stock.
And now, from 4 days ago, phone began to get laggy and everything suddenly force closes. Even though it had 2gb ram, dolphin browser get closes if i pressed home button. and after a day, it began to drain battery even in sleep and then after display time out, it goes to sleep and then turns off itself and battery gets very hot in that state. And I noticed that sound not coming out from speaker when ringing or I cant open music player or video player or voice recorder as the phone hangs and then reboots and after boot up, again reboots in like within 5 minute intervals.
So here What I tried,
1. Flashed stock from samsung updates firmware sites via ODIN 1.85. And yes I wiped everything before rom flash incl. Cache,Dalvik Cache, Data,SD card, System and everything except EFS partition as listed in philz recovery.
Result - Still no luck, reboots randomely, battery getting hot, music player video player crashes(video player doesn;t crash but when tried to play video it says cant play this video)
2. Again Rooted, installed TWRP and wiped Everything I could find and flashed stock again.(When wiping, TWRP fails to wipe data where it says type yes to wipe saying failed to format....unknown format and failed to remove encryption)
Result - Same again.
3. Flashed stock again without wiping. Result - Same.
4. Rooted, installed recovery, wiped everything and flashed PAC latest nightlies. stll same. Then flashed sentinel but same.
5. After trying 5 6 times flashing stock, I gave up and now its on Stock 4.1.2 BME3 and removed binary counter and ready to go for warranty claim.
But I still will to make this myself as it will take 2 weeks to get back to me if I give it to the retailer. So can you please help me guys. Thank you again.
Faqs and guides return to stock for warranty post and return to service .
Or just mess about for weeks and achieve nothing .
Thank you,
Yes, its returned to stock as mentioned. But may I know what cause this? cuz I use a S2 for years now and nothing wrong with it. So I think I know how to properly use android. I searched a lot. but sees lot of people complaining but no solution.
suspect008 said:
Thank you,
Yes, its returned to stock as mentioned. But may I know what cause this? cuz I use a S2 for years now and nothing wrong with it. So I think I know how to properly use android. I searched a lot. but sees lot of people complaining but no solution.
Click to expand...
Click to collapse
Ask a service centre read the faqs and guides .
JJEgan said:
Ask a service centre read the faqs and guides .
Click to expand...
Click to collapse
Yeah, I suppose. Thanks for the reply.