Related
I strongly advice the following since I hard bricked my note twice!
1. When using Odin make sure the firmware is compatible with your Note.
2. When partitioning using the pit file, make sure the file corresponds to your Note.
3. As a general rule, always wait for any flashing operations to finish before unplugging your Note.
--- I hard bricked my note due to the following
1. I used pit partition via pc odin and it took too long. I was impatient and unplugged my Note even if the operation was not finished. Good thing was I previously reset my binary counter and removed yellow triangle before my phone got bricked.(Samsung will not trace this.)
2. I flashed the wrong kernel...
3. I flashed many roms over and over until such time that my Note wouldn't open.
Sent my Galaxy Note to Samsung Service Center.
Luckily, my phone had no trace of any custom firmware flash and no yellow triangle. Samsung replaced my phone's mainboard free of charge as my phone is still in it's full warranty status.
After receiving my revived phone, as stupid as I am, I tried flashing firmware again via pc odin. This time it is the German Official Ics ROM thinking that it would do no harm. Same thing happened. Phone got hard bricked. So I told Samsung that my phone is dead again. I went to the service center again and Samsung asked me if I have done something with the software or Rom inside. I told them that I haven't done anything. They did not know because may binary counter is zero and I have no yellow triangle. They replaced again my mainboard free of charge.
That's all folks.
As of now, I stick to the ICS that the Samsung service center installed. I wouldn't risk again as I think I am one of those Galaxy Note owners who have the emmc bug.
All I did was to root my Note and that's it. No flashing...
SaXxO said:
I strongly advice the following since I hard bricked my note twice!
1. When using Odin make sure the firmware is compatible with your Note.
2. When partitioning using the pit file, make sure the file corresponds to your Note.
3. As a general rule, always wait for any flashing operations to finish before unplugging your Note.
--- I hard bricked my note due to the following
1. I used pit partition via pc odin and it took too long. I was impatient and unplugged my Note even if the operation was not finished. Good thing was I previously reset my binary counter and removed yellow triangle before my phone got bricked.(Samsung will not trace this.)
2. I flashed the wrong kernel...
3. I flashed many roms over and over until such time that my Note wouldn't open.
Sent my Galaxy Note to Samsung Service Center.
Luckily, my phone had no trace of any custom firmware flash and no yellow triangle. Samsung replaced my phone's mainboard free of charge as my phone is still in it's full warranty status.
After receiving my revived phone, as stupid as I am, I tried flashing firmware again via pc odin. This time it is the German Official Ics ROM thinking that it would do no harm. Same thing happened. Phone got hard bricked. So I told Samsung that my phone is dead again. I went to the service center again and Samsung asked me if I have done something with the software or Rom inside. I told them that I haven't done anything. They did not know because may binary counter is zero and I have no yellow triangle. They replaced again my mainboard free of charge.
That's all folks.
As of now, I stick to the ICS that the Samsung service center installed. I wouldn't risk again as I think I am one of those Galaxy Note owners who have the emmc bug.
All I did was to root my Note and that's it. No flashing...
Click to expand...
Click to collapse
I think when you flash the lpy with one file you click the re-repartition so you break your phone while using the pc odin which you should not do. Its only check if you have pit file or more than three files, others even when they have 4 files they still dont check the re repartition to be safe, the pc odin will automatically check for you anyway.
That`s what happens when you do stuff without any knowledge or background orientation (reading) :silly:
gee2012 said:
That`s what happens when you do stuff without any knowledge or background orientation (reading) :silly:
Click to expand...
Click to collapse
+1 Dont do anything without reading properly.
richness adsttl
+ Be patient when flashing firmware. I've flashed many times before when I was on gingerbread and I was successful.But when it comes to ICS much precaution should be taken. After my note got repaired I immediately installed the bugbrick checker and after almost 500 seconds my phone is bug free! Or my insane chip is asleep.
Deleted by myself..
Be patient. Why dont you try to search for zedomax in youtube. He's a good teacher on flashing roms and stuff. Follow his guide. His guides are safe. Learned a lot from him.
Sent from my GT-N7000 using xda premium
Pecityma March
@andnote. Install the eMMC brickbug check from playstore. It's free. You must be rooted. Just run the app after installation. It wilk tell you your phone passed the check.
I don't get it how could it brick when only trying to flash a stock ICS ROM??doesn't make sense...
galaxynotes said:
I don't get it how could it brick when only trying to flash a stock ICS ROM??doesn't make sense...
Click to expand...
Click to collapse
Why wouldn't it make sense? It's a bug introduced by Samsung itself ! Apparently in the eMMC driver, which can damage permanently the eMMC flash storage. It happens (not always) when you do a Wipe, or flash FROM THE RECOVERY. If you flash from outside (Odin), and do not wipe, it shouldn't affect you.
AlexProfesor said:
Why wouldn't it make sense? It's a bug introduced by Samsung itself ! Apparently in the eMMC driver, which can damage permanently the eMMC flash storage. It happens (not always) when you do a Wipe, or flash FROM THE RECOVERY. If you flash from outside (Odin), and do not wipe, it shouldn't affect you.
Click to expand...
Click to collapse
and yet the OP flashed via odin on a stock rom not via recovery and does not mention wiping at all, his issue is nothing to do with the emmc bug
That's what I'm sayin'!
So what went wrong?!
Great info mate. Useful to me and many
galaxynotes said:
That's what I'm sayin'!
So what went wrong?!
Click to expand...
Click to collapse
User error.
Sent from my GT-N7000 using xda app-developers app
galaxynotes said:
That's what I'm sayin'!
So what went wrong?!
Click to expand...
Click to collapse
Interrupting pit re partitioning is as good as setting off some tnt inside you're device, instant brick.
Sent from my GT-N7000 using xda premium
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
interesting, ive been having problems with my kernel, and used faux reset plenty of times. hopefully someone can chime in for you. Mine is still up and running with faux kernel too
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
italia0101 said:
I swear this phone is getting bricked a lot more than a y other nexus
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Are u serious Every phone has a chance of that alot of times
Soon To Be A Nexie
berz said:
I swear you are a complete moron.
As for the OP's problem download nexus tool kit , Put the phone in bootloader mode and flash stock factory image.
Click to expand...
Click to collapse
Yea ... im a complete moron.. iv not seen this " red light " problem with any other Nexus device, have you? of course i know theres a chance of bricking with anything , but iv never seen a nexus device die so easily just by running a benchmark ?!? thats all im saying
i know this isnt the problem the op is having , but its just strange..
either way , maybe chill out a bit before you start pulling out the names yea...
I want to chime in ^_^
I think the kernel reset screwed everything up IMO. I think there was maybe some left over files on the ram disk that didn't get wiped out 100% (I'm assuming you didn't wipe completely, regardless of a kernel reset) and when you flashed stock kernel it couldn't rearrange them correctly and you ended up with a bricked device.
Just my thoughts.
Sent from my Nexus 4 using xda app-developers app
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
juliano_q said:
when going back to stock just flash the factory image. it is very easy once you have the files and learn how to do it and always work,
Click to expand...
Click to collapse
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
AdamLange said:
Bricking Nexus? lol? this is a joke? just reinstall the stock firmware and you're done.
as long as u didnt fscked up the bootloader or the partition scheme then you shall be not affraid and its fairly easy to recover.
Adam
Click to expand...
Click to collapse
I still dont have my N4 but I always thought this. Coming from previous devices the only reason Ive seen a true brick is someone screwing up flashing radios or dicking with the boot-loader. I didn't think you could actually brick a device with ROMS/Kernels.
linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Click to expand...
Click to collapse
Power off. Hold "volume down" and press power button. This should get you to the bootloader. If it does, your phone is not bricked and there's loads of info on here to put it right again (stock factory image would be my first call here). If it doesn't work, I'd be tempted to remove the battery (IIRC, quite easy once you remove the screws at the bottom) and repeat the above instructions. (if you can get to the bootloader one way or another, your phone is most certainly not bricked!)
If this doesn't work, it's probably dead and you'll need to send back.
Daern
---------- Post added at 01:34 PM ---------- Previous post was at 01:27 PM ----------
berz said:
I swear you are a complete moron.
Click to expand...
Click to collapse
Didn't your mother ever teach you - "If you can't say anything nice, say nothing at all"?
This is not a site for trolling. Please go away.
I flashed different kernels many many times.
Never a problem.
OP should check for human error instead of blaming the device.
Sent from my Nexus 4 using xda premium
atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Sorry but i don't know what are you talking about ? what the same ID as bootloader? erm?
partition name in case of bootloader is bootloader, for case of kernel is boot
Adam
linh1987 said:
Hi all,
The day before yesterday I decided to move from my GNex to the new N4, but my time with it was short, because I have managed to accomplish an incredible feat: brick a N4 just 12hours after purchase :laugh:.
Now, I'm not creating this topic to moan about it, I'm fully aware that bricking is a possibility for every flash, and the phone is already sent back to LG. I just want to tell you all what I did, so we can, possibly, find what I did wrong and help other people to avoid it :highfive:. And a little bit of background, I got Gnex for a year, before that is a G1, with flashing almost become a daily job (not so with the Gnex, as I prefer the stock experience, but still a lot of rom switching and kernel flashing every few months).
My N4, right of the bat, I put it into fastboot unlock, root (the usual thingies). It's still working as normal, but the battery life is not so stellar, so I decided to try franco's kernel. I flashed r53 to my phone, it boot up normally, I feel the performance is too slow compare to stock, so I flashed the latest test version r61, too. It's still working without a hitch, abeit not as smooth as stock.
So I decided to get back to stock. I'm too lazy to do fastboot with stock image, so I download the stock kernel CWM package from this topic, and just to be safe, I flashed faux's kernel reset from here before that. The flashing was succeed, no error, but when I reboot, the phone failed to boot up, just black screen. If I plug it into my computer, it show up as qhsusb_dload, which is a telltale sign of a corrupt internal memory aka definite brick.
To put it short, the sequel is: stock -> unlock -> root -> franco r53 -> franco r61 -> faux reset -> stock kernel flash -> brick.
I guess I did something wrong between the faux reset and stock kernel flashing. can anyone tell me what I did wrong? I did happen to flash wrong kernel build on my Gnex before but the worst I got is a boot loop, not straight up brick like this. And I'm very surprised that a core part of the phone (fastboot) can be corrupted that easy.
And, flash safely :good:
Click to expand...
Click to collapse
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
tweaked said:
If you took the same amount of time to search that you took to write this terrible OP you would have already fixed your phone....
Click to expand...
Click to collapse
Hey tweaked, thanks for your contribution, but if you take 5 secs to search for a black screen issue with qhsusb_dload show up in windows, you will know that I went to a dead end.
@all: yes it's 100% my fault, I just double check and I DID flash grouper (aka N7) kernel to my N4, but I just feel it's so much easier to flash N7 kernel to N4 without any error. And again, I just want to repeat that I'm not moaning about it, it's totally my fault. I just want to help other people to avoid it :highfive:
atulalvenkar said:
Any chance you flashed N7 kernel? Read somewhere that the kernel partition of N7 has same id as bootloader partition of N4. So what happens is kernel overwrites the bootloader resulting in brick.
Sent from LG Google Nexus 4 using XDA Premium
Click to expand...
Click to collapse
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
You are the first person I heard that flashed a wrong KERNEL.
Congratz.
Sent from my Nexus 4 using xda premium
linh1987 said:
Hey atulalvenkar, yes, I just did what you say. How stupid I'm. Guess we learn new thing every day
Click to expand...
Click to collapse
Saw couple of posts on reddit where many people did the same thing. The problem is franco develops for both N7 and N4 and his XDA thread subject doesn't have any indication of the device. Because of this it's easy to get pointed to the wrong thread and download wrong kernel.
My phone bricked spontaneously. I had installed CM 10.1, with the stock kernel, about 12 hours earlier and was actually browsing facebook when the phone spontaneously rebooted. I could get into fastboot, but no matter what I tried, I couldn't flash a stable recovery or full image. Constant boot loops with the occasional successful system boot, only to reboot within a few seconds.. starting the whole process over again.
Flashed and formatted every accessible partition, followed every "how to" I could find. Absolutely no success. Luckily Google sent me a replacement and I had a new phone in 2 days. Running the same CM 10.1/stock kernel now, no issues.
My first phone (a Rev_11) always ran somewhat hot, and the battery wouldn't last a day. The replacement phone (also a Rev_11) runs much cooler and the battery lasts for 2 days easy, with the exact same software. I'm thinking the old phone just somehow toasted itself. Just speculation. Oh, the old phone was also a "slow" binned CPU.
Anyway, the point of my story is that is ISN'T entirely true that the ability to boot into bootloader/fastboot will guarantee you success when trying to resurrect a dead phone.
Good Evening XDA Note 4 Devs/Users,
The Bad News;
I seem to have gotten myself into a pickle. and, Hopefully.. one that isn't permanent.
So, I was planning on reinstalling Firekat 4.4.4 after being on CM12 (Lolipop) Remix. everything went super till I went to wipe my data/cache. In the process of being yelled at by two people and in the stress of it all I accidentally wiped the system data too. Which, seems to have deleted just about everything.. including the original backup of my device, the two ROMS and the system OS. The phone is also claiming not to be rooted now and TWRP seems to have been deleted too. The only thing I can really do is boot into download mode which ODIN keeps refusing to detect. and, Windows 8.1 keeps thinking the phone is a Banana.
The Good News;
I May have a Backup of the Original Unrooted TMO KitKat stored on my Laptop from ODIN.
I May Be able to push the Unrooted ROM by ADB / ODIN
I can boot into Download mode.
So, knowing my predicament and knowing I screwed up. Any advice or help from here to get the device working again?
Also, I promise not to try and turn the phone into a brick again. :good:
Thank you in Advance! :highfive:
Odin
follow this http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
I'm on FK, I always wipe everything. As long as my Zip (for install) is on the external SD card, I'm good. So what's wrong?
As for not having TWRP, I would also just Odin to stock, reinstall it. Should be an easy fix.
madmike23 said:
I'm on FK, I always wipe everything. As long as my Zip (for install) is on the external SD card, I'm good. So what's wrong?
As for not having TWRP, I would also just Odin to stock, reinstall it. Should be an easy fix.
Click to expand...
Click to collapse
I came from a phone that if you end up deleting everything like this. You bricked the device completely with it not even turning on. (Older android phone). So, Naturally. I thought I had screwed myself with it. lol
I did fix it though right after I posted the thread. I managed to get one of the rom's to flash through odin. (so, I guess I did not accidentally unroot it). I think I Love Samsung phones now that I can accidentally brick it and then still get myself out of trouble with the help of you all
I dont know anyone who has bricked a samsung in a while. Odin is great. Only mess up would be if you delete pit file
BACARDILIMON said:
I dont know anyone who has bricked a samsung in a while. Odin is great. Only mess up would be if you delete pit file
Click to expand...
Click to collapse
I regret to say this is my first Samsung device.. was a Motorola and HTC fanboy before both which I bricked one way or the other..
BACARDILIMON said:
I dont know anyone who has bricked a samsung in a while.
Click to expand...
Click to collapse
I would still be careful. I managed to brick my Note 3 so hard that JTAG couldn't bring it back to life. They are easy to recover from soft bricks, but they aren't invincible...
Face_Plant said:
I would still be careful. I managed to brick my Note 3 so hard that JTAG couldn't bring it back to life. They are easy to recover from soft bricks, but they aren't invincible...
Click to expand...
Click to collapse
Really. I was working on 3 phones and flashed the wrong rom on my note 3. It was from a totally different phone. Took 6 hours to bring back to life. Odin would install a part then fail so just kept pushing and wiping and finally went in. I was mad as hell since i qas going on vacation the next day. Lol.
BACARDILIMON said:
Really. I was working on 3 phones and flashed the wrong rom on my note 3. It was from a totally different phone. Took 6 hours to bring back to life. Odin would install a part then fail so just kept pushing and wiping and finally went in. I was mad as hell since i qas going on vacation the next day. Lol.
Click to expand...
Click to collapse
I couldn't get into download mode. The phone was completely unresponsive to all button combos and my laptop. I tried a USB jig, an unbrick image flashed on an SD card, yelling at it, and sending it off for JTAG but nothing could bring it back. I was quite sad because I had a lot of good memories with that phone, but my Note 4 fills the void nicely.
Hi
I managed to get in trouble with note 3...I have listed my entire trial & error here, can someone please help me bring this phone back to life.
http://forum.xda-developers.com/gal...ed-samsung-note-3-n9005-t3058408/post59580154
So I was running the hyperdrive 4.4.4 for for well over a year with no issues. Then about 2 weeks ago, it randomly shut down and bootlooped. Once it finally booted back into the rom, it would lag, freeze, bootloop, and then randomly boot into download mode, or Recovery. So after going back to a clean install of hyperdive, it would still act erratic. So I went back to stock, same problems. I then changed recoveries (from twrp to philz) and it stopped freaking out for a bit, then started again. So i clean installed 4.4.4 and still problems. So I clean install hyperdrive with philz (after the appropriate steps) and still have problems. So then I odin'd to official 5.1.1 (which might have acted as an in place upgrade)and I'm still having freezing problems. Sometimes I have to go into download mode and reboot from there just to boot into the os.
Help please?
EDIT: when it fails to boot, and goes into download mode it says "ddi : mmc_read failed."
the phone is also carrier unlocked and being used on cricket.
internal memory issue?
From the mmc_read error it sounds like the internal memory in your device is maybe starting to go out. That's the only thing I could think of. It is curious though that it will randomly boot the recovery and download partitions which I am fairly certain reside on the same internal memory. Maybe blocks in your system partition are going bad causing it to not read and boot to your 2 repair partitions to fix the problem.
---------- Post added at 04:57 PM ---------- Previous post was at 04:56 PM ----------
Though if the flash memory is going bad there's not much to be done about it
Ended up buying a v10 until I could figure out this problem.
long story short - you're screwed.
MRguyandhis2 said:
Ended up buying a v10 until I could figure out this problem.
Click to expand...
Click to collapse
Try this:
Step 1. Download Wake Lock from the Play Store
Step 2. Enable Partial_Wake_Lock (number 4)
Step 3. Enable Auto-Start
Just found this, thought you might find some use from it. Good luck. http://forum.xda-developers.com/note-4-tmobile/help/fix-mmcfailed-internal-memory-yes-t3277144
TardisJacker said:
Just found this, thought you might find some use from it. Good luck. http://forum.xda-developers.com/note-4-tmobile/help/fix-mmcfailed-internal-memory-yes-t3277144
Click to expand...
Click to collapse
Unfortunately the solution in that thread doesn't work. it's just working on the SD card partition, not the internal memory itself.
OP is screwed, just like I was, just like plenty of others here. **** samsung and their ****ty quality control on an otherwise brilliant phone
dtrinh4000 said:
Unfortunately the solution in that thread doesn't work. it's just working on the SD card partition, not the internal memory itself.
OP is screwed, just like I was, just like plenty of others here. **** samsung and their ****ty quality control on an otherwise brilliant phone
Click to expand...
Click to collapse
ive had the s3, s4. s5, note 2. note 3, and note 4. This is the only phone that I have ever had this kind of problem. it truly sucks.
Hay Guys, I have bricked my friends Galaxy S5 SM-G900A.
He handed over it to me to fix the multiple reboots it was taking and was unable to start properly.
I thought it was a common problem of bootloader so i searched for a BL file in the androidfilehost and ODIN flashed it on the BL section but thereafter the phone is totally dead and does not start at all.
I don't know what to do, Is there any thing like short circuiting kind of thing like it was there for LG G2.
I believe the only way to fix that is to flash the correct Bootloader. You did not mention if the phone is rooted, stock, android/software version, etc. Someone could probably find the correct file for you, just give us the details!
johnkirchner said:
I believe the only way to fix that is to flash the correct Bootloader. You did not mention if the phone is rooted, stock, android/software version, etc. Someone could probably find the correct file for you, just give us the details!
Click to expand...
Click to collapse
Thanks, the phone is just all dead, it doesn't boot at all. BTW it was not rooted, it was on official Marshmallow 6.0 and it is an AT&T S5. Thanks by they way for your interest. Some body told me it needs to be jtaged kinda thing.
Sent from my SAMSUNG-SM-N910A using Tapatalk
talvigi said:
Thanks, the phone is just all dead, it doesn't boot at all. BTW it was not rooted, it was on official Marshmallow 6.0 and it is an AT&T S5. Thanks by they way for your interest. Some body told me it needs to be jtaged kinda thing.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
Flash this: https://www.androidfilehost.com/?fid=529152257862703384 onto an SD CARD with at least 300MB space (THIS WILL WIPE THE CARD!!) with win32diskimager.
Then just pop the SD Card into the phone and you'll be able to boot into Download Mode
AptLogic said:
Flash this: onto an SD CARD with at least 300MB space (THIS WILL WIPE THE CARD!!) with win32diskimager.
Then just pop the SD Card into the phone and you'll be able to boot into Download Mode
Click to expand...
Click to collapse
Hey, same problem happened to my G900FQ s5. Where can i find a debrick.img for that?