2 Notes ( pure stock ) get bricked after malaysia official jelly bean update. - Galaxy Note GT-N7000 General

First of all, recently im seldom visit n7000 forum since I has upgraded to n7100. Now my n7000 using by my wife.
Last week malaysia jelly bean firmware has been out. All my friends and colleagues are upgrade thru kies.
Unfortunately something happened. 2 of my colleagues called me for sos at the same day. ( the 2nd day after upgraded). Both told me stucked at note logo. They both passed the devices for me and check whats the problem.
1st devices.
- completely stock and ugraded to official jelly bean firmware thru kies.
- failed to boot into recovery mode. Download mode ok.
- use odin flash stock ginger rom but failed at nand write start.
- sent to ssc and get mobo free replacement within 3 hours. ( under warranty.
2nd devices.
- completely stock and ugraded to official jelly bean firmware thru kies.
- totally no respond, unable to boot in any mode even using what kind of method, pull out battery and using spare battery.
-sent to ssc, get replied from ssc within 1 hour and need replace mobo with all cost rm740.50.
Both of my frends told that they did NOTHING. But the devices automatically get turn off and another keep restart and stucked.
As my knowledge, this syndrome can be consider as sds, which great different as n7000 brick bug.
Im really wonder why this will happen. Is this related to jelly bean firmware which caused the sds occured?
Sent from my GT-N7100 using xda premium

Brought to you by the world's largest Android phone manufacturer, Samsung.

Im afraid what happen to both phone is what we called 'bootloop bug' on JB.. Stuck on N7000 logo and not going to Samsung animation.... happen when you pull out the bettery without properly power off the phone or when you make a force Reboot.. Its sucks when happened to average user, my phone also infected by bootloop bug...solved by flashing Philz kernel, Speedmod kernel or TWRP kernel by Ficeto...
Sent from my GT-N7000 using Tapatalk HD

zai89 said:
Im afraid what happen to both phone is what we called 'bootloop bug' on JB.. Stuck on N7000 logo and not going to Samsung animation.... happen when you pull out the bettery without properly power off the phone or when you make a force Reboot.. Its sucks when happened to average user, my phone also infected by bootloop bug...solved by flashing Philz kernel, Speedmod kernel or TWRP kernel by Ficeto...
Sent from my GT-N7000 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for reply. I know about the bootloop bug. My n7000 previously also having the same bootloop issue before fixed method out. But now the case was different. Is refuse to boot in recovery mode. ( my both fren completely in stock recovery). And one of the affected devices was totally unable to manually boot into any mode..no download mode and no recovery mode.
And both devices confirmed by ssc was need to replace mobo.
Worst to worst ssc only give 1month warranty for the new mobo replacement.
Sent from my GT-N7100 using xda premium

Well my best advice that root your phone and change the kernel to a safe one like philz if you are using jb.
Sent from my GT-N7000 using xda premium

Just a question what's the RM? Thanks.
Sent from my GT-N7000 using xda premium

TheNoticer said:
Just a question what's the RM? Thanks.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Ringgit Malaysia...Malaysian currency

I recently upgraded to JB using PC Odin and while fiddling around, got locked at boot screen. It no longer went to recovery mode but luckily was able to boot to download mode and I flashed Philz's kernel using PC Odin. Got phone working but with yellow triangle. Chainfire's remove triangle did not run in JB. So switched back to GB, removed triangle and back to JB with Philz's kernel ready in sd card to flash ASAP. So far so good.

Related

Bricked Galaxy Note! Please Help

Hey guys, I think i may have bricked my SGN.
I rooted via adb and then flashed the abyss kernel followed by stunner ics rom. But when i restarted through CWM the phone never restarted and now it won't even turn on. No download mode either and i've tried every possible trick including the wall outlet.
Phone won't turn on at all. Is this considered hard bricked and has anyone found a solution to this. Will a USB jig work on this.
Also, the stunner ics 4.5 beta showed successfull at CWM so i'm not sure what happened. Battery was fully charged too.
Try taking out the battery for a few minutes, put it back again and try entering download mode again.
What's sky ics rom?
Sent from my GT-N7000 using Tapatalk
hey thanks for the reply, i've tried that already as well. no download mode working here.
itsjiffybruh said:
Hey guys, I think i may have bricked my SGN.
I rooted via adb and then flashed the abyss kernel followed by stunner ics rom. But when i restarted through CWM the phone never restarted and now it won't even turn on. No download mode either and i've tried every possible trick including the wall outlet.
Phone won't turn on at all. Is this considered hard bricked and has anyone found a solution to this. Will a USB jig work on this.
Also, the sky ics showed successfull at CWM so i'm not sure what happened. Battery was fully charged too.
Click to expand...
Click to collapse
hmmm try to pull down battery, put it back again, try to turn on download mode, do this several times if it wont help, try to charge phone and do same. goodluck
sorry, i meant stunner ics. got confused with sky ics cuz i just put that into my friends skyrocket.
You didnt follow the instructions ti install the rom so you now have a brick
Try pluggingn it top the pc , if you hear some noises on the pc then your noté is alive
Sent from my GT-N7000 using xda premium
Well, did you try a USB-jig to force your Note into Download-Mode?
Than you should be able to flash a stock and start over again.
Did you let your Note do the first startup at his own, I've read that the first start may took a bit longer and shouldn't be interrupted?
Regards
thor2001 said:
Well, did you try a USB-jig to force your Note into Download-Mode?
Than you should be able to flash a stock and start over again.
Did you let your Note do the first startup at his own, I've read that the first start may took a bit longer and shouldn't be interrupted?
Regards
Click to expand...
Click to collapse
Well, i was in CWM and then installed the rom then pressed restart phone on CWM menu. Went downstairs and when I came back it didn't turn on.
if it doesn't turn on at all is it a hard brick?
I ordered a usb jig from amazon for $7.00 and it will arrive tomorrow, I heard the usb jig only works on soft bricked phones though and since mines won't even turn on will there be any chance at all of it working?
Hey guys I just realized what went wrong. I download the N7000 Galaxy note roms and kernels instead of the i717 (ATT) versions. Stupid me!
Has anyone ever had success getting a fix on this? If not would I be able to go to an AT&T store and just get a new one? What should I tell them. Please help
itsjiffybruh said:
Hey guys I just realized what went wrong. I download the N7000 Galaxy note roms and kernels instead of the i717 (ATT) versions. Stupid me!
Has anyone ever had success getting a fix on this? If not would I be able to go to an AT&T store and just get a new one? What should I tell them. Please help
Click to expand...
Click to collapse
Your phone may has yellow triangle and flash counters now. So you would not be able to get a new one or order them fixing it for you.
Sent from my GT-N7000 using xda premium
Wow that really sucks . I wish you could fix it soon and please keep us updated with how you fixed if so .
Sent From My Samsung Galaxy Note N7000 Using XDA Premium
.Hell. said:
Wow that really sucks . I wish you could fix it soon and please keep us updated with how you fixed if so .
Sent From My Samsung Galaxy Note N7000 Using XDA Premium
Click to expand...
Click to collapse
Ill definitely keep you guys updated. My usb jig isn't scheduled to arrive until monday so i might just try to go to the att store today and try to get a replacement.
siuming720 said:
Your phone may has yellow triangle and flash counters now. So you would not be able to get a new one or order them fixing it for you.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
how would they be able to test it if it doesn't even turn on?
hi try this not my work dont now if it works
Default Bricked Galaxy Note N7000 or Incorrect ROM Flash Easy Fix
Ok simple you won't see nothing on the screen because the bootloader is wrong.....
Just put the battery in then do following.
1. hold vol down+home+power for 15 seconds...
2. release then press volume up...
Note: Don't worry about seeing anything on the screen or any keys light
it will be blank this is because bootloader is incorrect
3. open odin you should see comxx in listed flash the original bootloader back
into phone this will/should resume visual display.
I have attached necessary files to resume
Load File in PDA NOT BOOTLOODER
4. Wait 10 seconds.. Remove Battery Then Boot Back into Bootloader following steps 1&2
5. finally flash Stock Rom to resume the whole phone to original state.
Hope That Helps......see hear for post http://forum.xda-developers.com/showthread.php?p=23052721#post23052721
Sent from my GT-N7000 using Tapatalk
thanks for the help. i read that on another post and already tried it. unfortunately its a no go.
Just came back from att center and they said that they couldn't replace it for me on the spot because they don't have the phone in stock since its a newer phone. I gotta call the number they gave me now.
Sorry you've run into such a serious issue, but in a few way it's probably quite a good thing it's a hard brick.... It's likely you would have had a raised flash counter and the fact they can't power it on there and then is a bit of a God sent.
Hope you get a replacement soon mate :thumbup:
Sent from my GT-N7000 using xda premium
SpyderTracks said:
Sorry you've run into such a serious issue, but in a few way it's probably quite a good thing it's a hard brick.... It's likely you would have had a raised flash counter and the fact they can't power it on there and then is a bit of a God sent.
Hope you get a replacement soon mate :thumbup:
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
hey, im supposed to send my phone in to them and so your saying that when i send it in they won't be able to find out that i flashed a custom rom and kernel on it?
and im not sure if its such a good thing because if it was at least soft bricked i wouldve been able to fix it most likely. thanks for your help
itsjiffybruh said:
hey, im supposed to send my phone in to them and so your saying that when i send it in they won't be able to find out that i flashed a custom rom and kernel on it?
and im not sure if its such a good thing because if it was at least soft bricked i wouldve been able to fix it most likely. thanks for your help
Click to expand...
Click to collapse
First of all I think It wouldnt have raised the binary counter and give triangle because you didnt use Odin to flash (Am I right?).
Second thing Thought it had given you a triangle since your phone is dead.
So they cant find that you flashed a custom kernel or the binary.
itsjiffybruh said:
how would they be able to test it if it doesn't even turn on?
Click to expand...
Click to collapse
Oh.. I didn't see you can't enter to cwm
Sent from my GT-N7000 using xda premium

Samsung working on Emmc brick fix

More info and source credits here, thanks to codeworkx https://plus.google.com/111398485184813224730/posts/21pTYfTsCkB.
ATTENTION:
We've contacted Samsung about the problem where performing a mmc erase could hardbrick your phone (i9100, i9100g, n7000, m250 - MAG4FA, VYL00M, and KYL00M with firmware revision 0x19 // T989 and I727 with fw rev 0x12) if it's having a faulty emmc chip.
Read this thread for more informations about it: http://forum.xda-developers.com/showthread.php?t=1644364
They're working as hard as possible on a clean solution which will be ready soon.
Please be patient and try to not flash any leaked kernels or kernels based on sources where MMC_CAP_ERASE is present.
This app http://forum.xda-developers.com/showpost.php?p=27014974&postcount=1 can be used to identify if your phone is affected or not.
CM9 kernels are safe to flash.
Please share!
Update 14:56 CEST:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time.
Click to expand...
Click to collapse
New Clarifications by Entropy : http://forum.xda-developers.com/showpost.php?p=28416723&postcount=403 - Must Read.
To check whether your phone has the brick bug, download the Got Brickbug app from Chainfire: http://forum.xda-developers.com/showthread.php?t=1693704
Also do read the article on xda for more info.: http://www.xda-developers.com/android/samsung-diligently-working-towards-hardbrick-fix/
Nice!
That is a really good news after some time.
Sent from my GT-N7000 using Tapatalk 2
Good news!
Looking forward to see how Samsung solve this nightmare
Sent from my GT-N7000 using xda premium
How many time to fix this Samsung BUG? How maby people need ti brick our 600€? If samsung knows why no first before? Grrrrr...
All hard work its from XDA devs!!!! Thank you devs!!
Enviado desde mi GT-N7000 usando Tapatalk 2
Hmmm don't want to get my hopes up
But hmmm ok let's hope saw but how do we know is true ?
Sent from my iPad using Tapatalk
nandihno said:
Hmmm don't want to get my hopes up
But hmmm ok let's hope saw but how do we know is true ?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Teamhacksung dev codeworkx been in touch with Sammy guys so its genuine news...check link in op
Sent from my GT-N7000 using xda premium
at least we now have some hope...hopefully...
So to be clear...
Can someone confirm the following is correct please?
I have a N7000 on official (german) ICS, with the dodgy mmc chip. I must have been lucky since ive flashed a bunch of roms (including CM9, back to gingerbread, then official ICS) without issue. Ive also done a few CWM backup and restores... phew!
1. Flashing anything from the phone itself (eg using mobile odin or CWM recovery) is a no-go (assuming it issues the erase command)
2. Flashing from the PC is OK ??? (via desktop ODIN)?
If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?
thanks
George
ripnetuk said:
Can someone confirm the following is correct please?
I have a N7000 on official (german) ICS, with the dodgy mmc chip. I must have been lucky since ive flashed a bunch of roms (including CM9, back to gingerbread, then official ICS) without issue. Ive also done a few CWM backup and restores... phew!
1. Flashing anything from the phone itself (eg using mobile odin or CWM recovery) is a no-go (assuming it issues the erase command)
2. Flashing from the PC is OK ??? (via desktop ODIN)?
If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?
thanks
George
Click to expand...
Click to collapse
Flashing is not the problem but wiping is
So if they release a new update then simply don't wipe on your ics but wipe only after you install the new update
If however you want to be extra careful like I am
Flash a gb rom via odin then wipe that then flash said ics update via Odin
Sent from my iPad using Tapatalk
While there have been brickage reports using either PC Odin or CWM, there have been none regarding Odin Mobile Pro. So, when I flashed back GB, I used Odin mobile Pro. Everything went smooth.
//troll mode activated
It's just like Microsoft patching windows vista
//troll mode off
This is a true victory for XDA developers!
My deepest respect for all of you guys :thumbup:!!
Are they releasing a fix for brickd phone or a prevention update?
blue_panther9_9 said:
Are they releasing a fix for brickd phone or a prevention update?
Click to expand...
Click to collapse
Prevention.
Sent from my GT-N7000 using xda premium
I really hope this mess will soon be over. Let's hope while they are resolving the brick bug they also take a look at the wakelock thing. Contrary to others I have encountered this problem very rarely (1 time so far). Nonetheless it would be nice to see a solution.
Sent from my Galaxy Note running ICS
Good news but given that we haven't seen ics roll out in all countries, who knows when this will get fixed.
Another thing that bugs me. Is there possibility that Samsung push the solution for this bug and carriers just ignore it and continue with pushing the infected ics?
I guess that all we need is just one good release and everyone can flash it.
Hope to see it soon.
Sent from my Samsung Galaxy Note using XDA app
ripnetuk said:
Can someone confirm the following is correct please?
If 2 is untrue, how is sammy gonna issue an update (with the erase capability turned off) without bricking a load of phones during the update process? can they maybe provide a custom app which re-flashes the kernel without doing an erase first?
Click to expand...
Click to collapse
In all probability it might show a message over kies / OTA message asking to connect to kies on the comp .. and provide an update for kies desktop having 0din in it
ashoksoft said:
In all probability it might show a message over kies / OTA message asking to connect to kies on the comp .. and provide an update for kies desktop having 0din in it
Click to expand...
Click to collapse
Update 14:56 CEST:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time.
Just updated op too
This is great news! Many thanks to entropy and chasmodo and all who've worked on this and sacrificed for us!
Also thanls to those who took it seriously.
Sent from my GT-N7000 using xda premium

Galaxy gt-i9100 boot problem after 4.0.4

I upgraded to LQ5 4.0.4 and then to LPM 4.0.4 . Now when i shut down my phone then my phone wont switch on or go into recovery/download for about 5 minutes. If i try after around 5 minutes then it works.
Any solutions or advice ?
Thanks
Sent from my GT-I9100 using xda app-developers app
nemisi said:
I upgraded to LQ5 4.0.4 and then to LPM 4.0.4 . Now when i shut down my phone then my phone wont switch on or go into recovery/download for about 5 minutes. If i try after around 5 minutes then it works.
Any solutions or advice ?
Thanks
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Be very careful, you are on a very dangerous rom, LQ5 and all 4.0.4 roms are categorized unsafe (It will brick your phone if you try to restore any nandroid backup, or reset to factory setting)
PLEASE READ THIS BEFORE YOU DO ANYTHING http://forum.xda-developers.com/showthread.php?t=1756242
Very dangerous!!!
Very dangerous... now you must find a 3 files ROM package (4.0.3 or GB ROMs, not 4.0.4), a recommed .PIT file and flash via ODIN PC with 3 ROM files, .PIT file and repartition ticked.
Its strange because im back on 4.0.3 now but ill switch my phone off and it will show all the symptoms of a hardbricked phone for like 4 hours(hot while charger is plugged in when phone is off.no download mode. No recovey.nothing) but ill keep attempting to switch on my phone. Eventually afters hours it will switch. Can anyone give me a direct link to 3 file 4.0.3 roms ?
Sent from my GT-I9100 using xda app-developers app
Countless times have people said on xda don't flash 4.0.4 :/
Sent from my GT-I9100 using Xparent ICS Tapatalk 2
jaydvn said:
Very dangerous... now you must find a 3 files ROM package (4.0.3 or GB ROMs, not 4.0.4), a recommed .PIT file and flash via ODIN PC with 3 ROM files, .PIT file and repartition ticked.
Click to expand...
Click to collapse
Not necessarily, re-partition is the final thing you can do. I flashed (one-file) LPG without re-partition and it worked like a charm.
yeah me too. LPQ back to LPG and no problem until now
My S2 is in the same boot issue. I left the phone on over night to charge and the next morning it was dead.
I think I am running LPQ 4.0.4 ROM on Siyah Kernel. After few hours I still cannot get it to boot. Phone is out of warranty and I just want to get running so that I trade it in for the Note 2 that I have been planning for weeks. Anyone have a proven method to get it running again?

toasted s3i9300gt

Hi everyone , im sorry to tell but from begining i had problems with my s3 , i had a error and the battery was consumed very fast on standby then i rooted , installed other kernels roms etc , for nothing , i had an onscreen time of maximum 2.5 hours with everything shutted down gps sync geo localization setting all ...
Now i had installed original jelly bean flashed with odin and syah kernel the latest version from 1 month ago dont know exactly if something new came up.
My problem is that somehow when the phone was charging i was sending some emails and i felt a burned smell , i checked and the place in wich comes the plug into the phone was like toasted, from then i couldnt charge the phone no more and i cant put back the jelly bean using odin no more ...
The question is how do i put the original rom from tmobile germany back into my phone without odin , just with recovery mod ?
i coulndt find nothing on internet regarding this , just using odin , because when i try to start the phone i just pop the image with syah kernel and the guys from waranty will see this and my phone will be sended back as defect as i send it .
please help
Use mobile odin there is free version for xda http://forum.xda-developers.com/showthread.php?t=1347899 and paid on play store it can do all that desktop odin can and even more.
Tenacius D said:
Use mobile odin there is free version for xda http://forum.xda-developers.com/showthread.php?t=1347899 and paid on play store it can do all that desktop odin can and even more.
Click to expand...
Click to collapse
quick answer quick solving
thanks alot dude, one more thing if they see that i have still cwm recovery mode installed on the phone will they still make my waranty void ?
Use triangle away first. And then flash stock rom. Stock rom flash will install stock recovery automatically
Sent from my GT-I9300 using xda app-developers app
prabhjots said:
Use triangle away first. And then flash stock rom. Stock rom flash will install stock recovery automatically
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
well dont know how i managed to screw it complete up , it just doesnt want to install a new rom and the triangle pops up on download mode...
i hope they dont see it somehow ...
Sounds like a power surge that fried the charging circuit to me.
Sent from my GT-I9300 using xda premium

[Q] [HELP] Ive lost my mind trying to restore my phone

I have a galaxy s4 on sprint (SPH-L720). So about a week ago i reset the cache and data under Google services framework to get the update from Samsung. Well after quickly realizing how much i didnt enjoy 4.3 i wanted 4.2.2 back and began to look into flashing the old firmware back onto my phone. unfortunately i was stuck in the download mode or odin mode for a long time and after following many peoples different instructions on how to do it and not getting the proper results, i became frustrated. eventually in a desperate attempt to have a functional phone i tried rooting it, which got me out of odin mode. However, since i restarted the phone, i cannot turn on the wifi nor is there any sound. these were new problems among the same old problems that i had with 4.3 in the beginning which includes the video playback (which is non-existent). All i want to do is have my phone working like it did when i bought it with the android version of 4.2.2 with all the working features. any ideas?
I was going out of my mind too last night trying to go back to 4.2 but had no WiFi so I got fed up and just did the cyanogenmod installer video that qbking77 posted last week on YouTube which roots and installs cm10.2 all on its own at least it got me a fully functional phone for now until I get back home from work and try restoring again. Just thought I'd share a temp solution
Sent from my SPH-L720 using xda app-developers app
If you accepted the ota too go to 4.3 I believe the issue you are experiencing is due to the Knox bootloader. Unfortunately I do not think there is any way to downgrade with Knox bootloader (for now). I'd try reflashing a fresh 4.3 rom and see if that fixes your issues.
Sent from my SPH-L720 using xda app-developers app
Well I manged to restore stock 4.3 without a problem I guess it is that Knox deal
Sent from my SPH-L720 using xda app-developers app
FanOfSkynyrd said:
If you accepted the ota too go to 4.3 I believe the issue you are experiencing is due to the Knox bootloader. Unfortunately I do not think there is any way to downgrade with Knox bootloader (for now). I'd try reflashing a fresh 4.3 rom and see if that fixes your issues.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I reflashed with 4.3 and not only do i have wifi and sound back, but also i finally have video playback. it could be a more updated version of jellybean, either way, you, sir, are my hero. :highfive:
Hey guys you arent alone. There's hundreds of us....lol, try to make the best of it. Sac23 has a great rom. Check it out. There are also some other 4.3 based roms with great dev support available. It should help buy time till the devs can find a work around for the knox bootloader.

Categories

Resources