So, I was doing a nandroid BACKUP of stock ICS 4.0.4 with secure kernel and the phone crashed, shut down and now won't power, charge, etc.
Do I have that crappy superbrick bug or will a JIG resurrect it? I've had the phone a day, bought second hand.
I thought the superbrick was caused by wiping, not by backups?
abtekk said:
So, I was doing a nandroid BACKUP of stock ICS 4.0.4 with secure kernel and the phone crashed, shut down and now won't power, charge, etc.
Do I have that crappy superbrick bug or will a JIG resurrect it? I've had the phone a day, bought second hand.
I thought the superbrick was caused by wiping, not by backups?
Click to expand...
Click to collapse
It is caused by wiping in recovery on the stock 4.0.4 kernel, and also by restoring a backup on the stock 4.0.4 kernel as well. So as to why your phone has done this whilst making a backup, I'm not sure. Can you try a different battery to see if it was the battery for some weird reason? No download mode or recovery mode? Have you got a USB Jig to try kick it into download mode? A JIG may work if it is just hard bricked, but if it is the brick bug, a JIG won't have any effect. Try those things I listed first, and see.
OP of this thread states that only wiping and restoring backup can lead to super brick on 4.0.4 kernel: http://forum.xda-developers.com/showthread.php?t=1756242
themadba said:
It is caused by wiping in recovery on the stock 4.0.4 kernel, and also by restoring a backup on the stock 4.0.4 kernel as well. So as to why your phone has done this whilst making a backup, I'm not sure. Can you try a different battery to see if it was the battery for some weird reason? No download mode or recovery mode? Have you got a USB Jig to try kick it into download mode? A JIG may work if it is just hard bricked, but if it is the brick bug, a JIG won't have any effect. Try those things I listed first, and see.
OP of this thread states that only wiping and restoring backup can lead to super brick on 4.0.4 kernel: http://forum.xda-developers.com/showthread.php?t=1756242
Click to expand...
Click to collapse
Yeah I found is super weird for it to do what it has. I definitely hit backup and not restore because I remember it telling me how much SDCard space I had, not only that but this is the first backup I have done. I've ordered a battery and JIG from eBay, it should be delivered Monday-Tuesday time. Until I get them, any chance of checking for superbrick any other way?
abtekk said:
Yeah I found is super weird for it to do what it has. I definitely hit backup and not restore because I remember it telling me how much SDCard space I had, not only that but this is the first backup I have done. I've ordered a battery and JIG from eBay, it should be delivered Monday-Tuesday time. Until I get them, any chance of checking for superbrick any other way?
Click to expand...
Click to collapse
Not really, you can just go by the symptoms your phone is producing: no charging, no powering up, no recovery/download mode etc. These all fall in line with the SuperBrick Bug and there is not much more you can do other than wait for the new battery and Jig. If it is the superbrick bug, then the 4.0.4 kernel is the most dangerous I have ever seen, seems like there is nothing you can't do without it bricking your device! Anyway, keep hoping and when the battery and Jig arrive, it should determine what you are dealing with.
themadba said:
Not really, you can just go by the symptoms your phone is producing: no charging, no powering up, no recovery/download mode etc. These all fall in line with the SuperBrick Bug and there is not much more you can do other than wait for the new battery and Jig. If it is the superbrick bug, then the 4.0.4 kernel is the most dangerous I have ever seen, seems like there is nothing you can't do without it bricking your device! Anyway, keep hoping and when the battery and Jig arrive, it should determine what you are dealing with.
Click to expand...
Click to collapse
I'm just shocked that reading from eMMC during a backup would cause such a thing, I can understand the writing to it. Is there absolutely no way of recovering from a superbrick? I'm obviously not under warranty.
abtekk said:
I'm just shocked that reading from eMMC during a backup would cause such a thing, I can understand the writing to it. Is there absolutely no way of recovering from a superbrick? I'm obviously not under warranty.
Click to expand...
Click to collapse
As far I know, there is no fix known (well, that Samsung will allow certain members of the xda community to release). I believe you can buy a new motherboard from someone with a second hand SGS2 (which is typical considering yours is second hand as well). You could call Samsung and explain that you were using their kernel and your phone just died on you. Let them decide whether to help you out or not. If not, it's either a new motherboard or a new SGS2 (Sorry).
P.S. You said you were performing a nandroid backup in 4.0.4 secure kernel recovery. Was it the stock kernel you were using? Or was it a different kernel? If so, please list.
themadba said:
As far I know, there is no fix known (well, that Samsung will allow certain members of the xda community to release). I believe you can buy a new motherboard from someone with a second hand SGS2 (which is typical considering yours is second hand as well). You could call Samsung and explain that you were using their kernel and your phone just died on you. Let them decide whether to help you out or not. If not, it's either a new motherboard or a new SGS2 (Sorry).
P.S. You said you were performing a nandroid backup in 4.0.4 secure kernel recovery. Was it the stock kernel you were using? Or was it a different kernel? If so, please list.
Click to expand...
Click to collapse
So there is a fix out there... Interesting.
Sorry, yes I was using stock 4.0.4 secure kernel with temp CWM. The ROM was rooted too, if it matters.
abtekk said:
So there is a fix out there... Interesting.
Sorry, yes I was using stock 4.0.4 secure with temp CWM. The kernel was rooted too, if it matters.
Click to expand...
Click to collapse
That's interesting. I've read somewhere that the Galaxy Notes were affected by CWM.zip (temporary CWM) and that using it with stock 4.0.4 kernel recovery could lead to superbricks. Now, whether that just included wiping/restoring I'm not sure, but I'm not sure if the SGS2 could be affected in the same way.
P.S. Ignore above, it only affected AT&T SGS2, not international GT-i9100 (which I assume you have?)
themadba said:
Now, whether that just included wiping/restoring I'm not sure, but I'm not sure if the SGS2 could be affected in the same way.
P.S. Ignore above, it only affected AT&T SGS2, not international GT-i9100 (which I assume you have?)
Click to expand...
Click to collapse
So in theory, then, the JIG + new battery has every chance of saving this phone?
Yeah it will be international.
abtekk said:
So in theory, then, the JIG + new battery has every chance of saving this phone?
Yeah it will be international.
Click to expand...
Click to collapse
Yeah, we will have to see, only when the new battery and Jig is tried will we know. If nothing comes about, at least you know that it is technically Samsung's fault for releasing a very damaged kernel to the public. I know there has been much publicity about it, but performing a nandroid backup which involves writing to the SD-Card (if you selected it?) has nothing to do with the eMMC card, and it is the eMMC card which is involved with these superbricks, the culprit known as MMC_CAP_ERASE which just kills your eMMC card.
themadba said:
performing a nandroid backup which involves writing to the SD-Card (if you selected it?) has nothing to do with the eMMC card, and it is the eMMC card which is involved with these superbricks, the culprit known as MMC_CAP_ERASE which just kills your eMMC card.
Click to expand...
Click to collapse
That's what leads me to believe it can't possibly be a superbrick. I'll be surprised if it is, because nothing went near erase.
abtekk said:
That's what leads me to believe it can't possibly be a superbrick. I'll be surprised if it is, because nothing went near erase.
Click to expand...
Click to collapse
Just stick your phone on the charger for the night, maybe it just went haywire for some weird reason. If nothing by the morning, wait for the new battery, charge it for a good while, then pray to the phone gods and try the Jig. If nothing, then you can either try sending it for JIG repair, calling Samsung and seeing what they are willing to do, or try obtain a new motherboard. Good luck anyway.
P.S. Just remembered, you can flash a .pit file (partition file, not sure which one) and it can POSSIBLY revive your phone if it was struck by the superbrick bug. However, it will cut your phones 16GB internal memory to just 8GB. Possible fix for a superbricked phone.
themadba said:
Just stick your phone on the charger for the night, maybe it just went haywire for some weird reason. If nothing by the morning, wait for the new battery, charge it for a good while, then pray to the phone gods and try the Jig. If nothing, then you can either try sending it for JIG repair, calling Samsung and seeing what they are willing to do, or try obtain a new motherboard. Good luck anyway.
Click to expand...
Click to collapse
Thanks mate I will do. I'll keep you posted on what happens. If all fails, the person I bought it from offered to give a partial refund of £100 (bought for 160) if I send the phone back, so it's not a total loss. That or I'll grovel to Samsung for a few hours.
themadba said:
P.S. Just remembered, you can flash a .pit file (partition file, not sure which one) and it can POSSIBLY revive your phone if it was struck by the superbrick bug. However, it will cut your phones 16GB internal memory to just 8GB. Possible fix for a superbricked phone.
Click to expand...
Click to collapse
Oh really? How do I do this?
abtekk said:
Oh really? How do I do this?
Click to expand...
Click to collapse
It involves flashing a custom .pit file that someone has created to partition your eMMC chip (don't hold me to this, I'm not sure and I haven't seen a thread floating about with this information for a while.) I believe it partitions your eMMC chip (which I believe is your internal memory where the OS is stored etc.) and creates a "good" sector again that is usable. However, internal memory capacity is halved, which is not a bad price to pay if it revives your phone. If I can find a thread explaining this in better detail, I shall link it here. Until then, let's wait and see if the battery and Jig do the job
themadba said:
It involves flashing a custom .pit file that someone has created to partition your eMMC chip (don't hold me to this, I'm not sure and I haven't seen a thread floating about with this information for a while.) I believe it partitions your eMMC chip (which I believe is your internal memory where the OS is stored etc.) and creates a "good" sector again that is usable. However, internal memory capacity is halved, which is not a bad price to pay if it revives your phone. If I can find a thread explaining this in better detail, I shall link it here. Until then, let's wait and see if the battery and Jig do the job
Click to expand...
Click to collapse
How can I flash it, when I get no power and can't get to download mode or what have you? But yeah, I look forward to this JIG.
abtekk said:
How can I flash it, when I get no power and can't get to download mode or what have you? But yeah, I look forward to this JIG.
Click to expand...
Click to collapse
That's a good point, I don't know how people have been flashing these custom .pit files if they have no power or download mode for Odin to work. Anyway, here is the thread I was talking about!: http://forum.xda-developers.com/showthread.php?t=1667886
themadba said:
That's a good point, I don't know how people have been flashing these custom .pit files if they have no power or download mode for Odin to work. Anyway, here is the thread I was talking about!: http://forum.xda-developers.com/showthread.php?t=1667886
Click to expand...
Click to collapse
I'll look in to it, I'm unsure how people are able to flash the PIT though, however this does pose the idea that once you flash a resized .pit, recover the superbrick, install a safe and stable android, could you not do a full wipe through CWM that way, then resize back to stock partition sizes?
Just food for thought.
abtekk said:
I'll look in to it, I'm unsure how people are able to flash the PIT though, however this does pose the idea that once you flash a resized .pit, recover the superbrick, install a safe and stable android, could you not do a full wipe through CWM that way, then resize back to stock partition sizes?
Just food for thought.
Click to expand...
Click to collapse
No idea, I'm no expert on this as I haven't needed to read up on it (touch wood!) Get the battery and Jig first and let me know how you got on.
themadba said:
Get the battery and Jig first and let me know how you got on.
Click to expand...
Click to collapse
Oh yeah of course, I shall do. The .pit method does make me wonder though. Also after doing some Googling, it appears Odin (with the right Samsung drivers installed) will still pick up a superbricked device.
I think if/when I revive this device, I'll look in to creating a method for reviving superbricks properly, this is really interesting...
Related
Hey gang,
Got my hands on a brand new S III yesterday and of course jumped straight to rooting it.
The root went fine and CWM was working beautifully. I copied the .zip file for Blackstar rom onto the internal SD card and rebooted into recovery. After running the data wipe/factory reset option as per usual, I used CWM Recovery to install the .zip I copied. It began to to it's thing and then encountered an error. This worried me for obvious reasons, so I factory reset it again and rebooted it with the command in recovery.
Which brings us to now:
The phone is completely non responsive. The computer recognizes it as QHSUSB_DLOAD but Odin doesn't recognize it at all.
The device itself stays cold. No screen. No indicator lights. No vibration.
I cannot boot into CWM or Download mode.
Any helpful ideas, or am I buggered on this one?
Thanks,
Shaiden
Probably won't work but did you try a battery pull? But judging from the info you gave you probably are bricked beyond repair . Your best bet is hope insurance (If you have insurance on the phone) will replace it.
Sent from my SCH-I535 using xda premium
shimp208 said:
Probably won't work but did you try a battery pull? But judging from the info you gave you probably are bricked beyond repair . Your best bet is hope insurance (If you have insurance on the phone) will replace it.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Sorry, forgot to mention that. I did indeed attempt the good old battery pull.
Contemplating trying a usb jig on it, but I'm none too hopeful at this point.
The jig is your only hope at this point.
Should it not work, you'll need to pay around 20 bucks in a phone repair shop (if any are around) to have the device JTAG'ed so it will go to Download mode again.
Make sure your Jig is "good". There are a lot of cheap jigs on Ebay which worked on the S1 and partially the S2 but no longer on the S3 since they
do not have the exact resistance needed to trigger the mode (301kOhm)
You could theoretically claim it to be a malfunctioning Kies upgrade (they seem to sometimes not only cause soft- but also hardbricks) but that would be fraud.
Might be a stupid Q on my part but is it a US/Canadian S3(dual core) version or the international(quad core) as if youve flashed a rom for the wrong version u have bricked it.
Shaiden said:
Hey gang,
Got my hands on a brand new S III yesterday and of course jumped straight to rooting it.
The root went fine and CWM was working beautifully. I copied the .zip file for Blackstar rom onto the internal SD card and rebooted into recovery. After running the data wipe/factory reset option as per usual, I used CWM Recovery to install the .zip I copied. It began to to it's thing and then encountered an error. This worried me for obvious reasons, so I factory reset it again and rebooted it with the command in recovery.
Which brings us to now:
The phone is completely non responsive. The computer recognizes it as QHSUSB_DLOAD but Odin doesn't recognize it at all.
The device itself stays cold. No screen. No indicator lights. No vibration.
I cannot boot into CWM or Download mode.
Any helpful ideas, or am I buggered on this one?
Thanks,
Shaiden
Click to expand...
Click to collapse
Shaiden said:
Hey gang,
Got my hands on a brand new S III yesterday and of course jumped straight to rooting it.
The root went fine and CWM was working beautifully. I copied the .zip file for Blackstar rom onto the internal SD card and rebooted into recovery. After running the data wipe/factory reset option as per usual, I used CWM Recovery to install the .zip I copied. It began to to it's thing and then encountered an error. This worried me for obvious reasons, so I factory reset it again and rebooted it with the command in recovery.
Which brings us to now:
The phone is completely non responsive. The computer recognizes it as QHSUSB_DLOAD but Odin doesn't recognize it at all.
The device itself stays cold. No screen. No indicator lights. No vibration.
I cannot boot into CWM or Download mode.
Any helpful ideas, or am I buggered on this one?
Thanks,
Shaiden
Click to expand...
Click to collapse
What's your model number? Maybe U flashed the wrong rom.
Sent from my GT-I9000(maybe I9300) using Tapatalk 2
SwiftSmoke said:
Might be a stupid Q on my part but is it a US/Canadian S3(dual core) version or the international(quad core) as if youve flashed a rom for the wrong version u have bricked it.
Click to expand...
Click to collapse
It is indeed the North American dual-core model.
And I may have done just that. I admittedly did't check to see which configuration the ROM was meant for.
Shaiden said:
It is indeed the North American dual-core model.
And I may have done just that. I admittedly did't check to see which configuration the ROM was meant for.
Click to expand...
Click to collapse
you should have taken more care in reading stuffs rather than flashing.
Coming from iOS, "brick" isn't really brick. It's just the user doesn't know what to do, but completely fixable.
Being new to Android, over a month in but stock. I didn't know you could literally "brick" a phone. Interesting.
Shaiden said:
It is indeed the North American dual-core model.
And I may have done just that. I admittedly did't check to see which configuration the ROM was meant for.
Click to expand...
Click to collapse
'QHSUSB_DLOAD' means CPU is Qualcom.. so is not international S3 and Blackstar is for international ... hence the BRICK... send back to Samsung...cook a story. All the Best.
Within North America rooting won't void your warranty but in other countries on the international market you do void it that's why I don't root. I don't know what story you will come up with to make it fly but hey best of luck to you sir.
Buy yourself this jig dongle,
http://item.mobileweb.ebay.com/viewitem?itemId=300738858103&index=2&nav=SEARCH&nid=76910404095
If doesn't work buy yourself a new phone...
Sent from my GT-I9300 using xda premium
Hey guys!
I need a little help, I want to hardbrick my phone(for warranty purposes since i have some issues...last owner overclocked it like hell... )
I actually have a plan to do it:
I am running a 4.1.1 JB rom and Siyah kernel...
so first I am going to reset the phone to its factory state(flash stock rom, kernel ect.).. and now here's where I need help..
I need a method to brick it, that is undetectable that I've done any changes to it...in one word, hardbrick not to boot up and stuff!
Thanks!
Sorry if I posted this in the wrong section, I'm reading the forums for a long time, but this is my first post on it!
I once went into CWM, mounts and storage and formatted everything... Worked for me. Well if by worked you mean hard bricked
Sent from my GT-I9100 using Tapatalk 2
DPluss said:
Hey guys!
I need a little help, I want to hardbrick my phone(for warranty purposes since i have some issues...last owner overclocked it like hell... )
I actually have a plan to do it:
I am running a 4.1.1 JB rom and Siyah kernel...
so first I am going to reset the phone to its factory state(flash stock rom, kernel ect.).. and now here's where I need help..
I need a method to brick it, that is undetectable that I've done any changes to it...in one word, hardbrick not to boot up and stuff!
Thanks!
Sorry if I posted this in the wrong section, I'm reading the forums for a long time, but this is my first post on it!
Click to expand...
Click to collapse
Easy, flash a stock 4.0.4 firmware and keep it on stock kernel.
then just boot into recovery and start wiping everything.
Dont know if this is undetectable though
Moving to Q&A, please post all future questions there.
Thanks
The-Hulk
Poroto said:
Easy, flash a stock 4.0.4 firmware and keep it on stock kernel.
then just boot into recovery and start wiping everything.
Dont know if this is undetectable though
Click to expand...
Click to collapse
But if I reflash the stock kernel, it will flash the stock recovery, or not?
The stock recovery has wiping options too?
I had a little research on other bricking topics(other phone brands) throught xda and most peoples advice was to flash corrupted files through Odin,
like a boot.img or a corrupted update.zip to prevent the phone from even getting into download mode, making it an excelent paperweight I think that is fully undetectable sinc they cant do anything with it, and I can then tell that it will not boot up, I did nothing to it, tested with another battery, never fell, never got liquid, it was in a case, it has not even a scratch on it I would not do this if it wasn't necessary...I'ts always overheating like hell(I really tried everything to prevent that), even on charger, this is my second battery, my touchcreen response is poor, the bottom buttons are also laggy...I just want replacement before it's too late...It might hold up longer but my warranty expires on 31. Oct.
Deleted.
I would try using a firmware not meant for your phone and pull the plug out half way through flashing it with odin.
Then hope it gets hot around the camera and wont come on.....lol
Jokesy said:
Let's be reasonable here.
1. If you are not the first owner of the phone, then you might not be lucky with warranty service.
2. What are the issues you are facing? Can you list them?
Click to expand...
Click to collapse
umm.. i'm the second owner, of course first, i will go and see my provider, and ask them about the warranty(will not bring the phone in first lol)!
Basicly the warranty sheet has no personal information, just the phone type, the IMEI, and the date when the other bought it!
The issues are, serious overheating around the camera area...it can never be interrupted, if the phone is on, it keeps overheating after about half an hour, I don't know what is the ideal temperature of a working device but after an hour I can't hold my phone without a thick case(or gloves lol)! It heavily affects the camera, focus has major issues, sometimes it says "can't connect to camera", touchscreen can be a little laggy when its hot...When I bought it from previous owner I didn't noticed it because on forums people kept complaining about heating, but then I realized that I was an idiot...I tried stock official roms, GB,CSI, and now JB, nothing changed!
DPluss said:
But if I reflash the stock kernel, it will flash the stock recovery, or not?
The stock recovery has wiping options too?
I had a little research on other bricking topics(other phone brands) throught xda and most peoples advice was to flash corrupted files through Odin,
like a boot.img or a corrupted update.zip to prevent the phone from even getting into download mode, making it an excelent paperweight I think that is fully undetectable sinc they cant do anything with it, and I can then tell that it will not boot up, I did nothing to it, tested with another battery, never fell, never got liquid, it was in a case, it has not even a scratch on it I would not do this if it wasn't necessary...I'ts always overheating like hell(I really tried everything to prevent that), even on charger, this is my second battery, my touchcreen response is poor, the bottom buttons are also laggy...I just want replacement before it's too late...It might hold up longer but my warranty expires on 31. Oct.
Click to expand...
Click to collapse
it only works if you have a faulty emmc chip
Rick Roll said:
it only works if you have a faulty emmc chip
Click to expand...
Click to collapse
How do I know that? My phone was first out in 31.10.2011.
DPluss said:
How do I know that? My phone was first out in 31.10.2011.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=es
Deleted.
Thanks you very much!
Its says:
"Brick bug?
YES. Insane chip."
So if I revert everything to stock and then I start wiping stuff in recovery itt will hardbricked?
Can't it be even fixed in Download mode with Odin?
Jokesy said:
Ok.
very simple way to hard brick your phone.
Flash the wrong bootloader!
PS: first confirm that you can claim warranty service.
Click to expand...
Click to collapse
I will confirm it!
So for example if I flash another phones boot.img throught Odin than it's a full disaster that can never be repaired?
Thank you!
Siyah kernel 3.1rc6 lol
DPluss said:
Thanks you very much!
Its says:
"Brick bug?
YES. Insane chip."
So if I revert everything to stock and then I start wiping stuff in recovery itt will hardbricked?
Can't it be even fixed in Download mode with Odin?
Click to expand...
Click to collapse
Exactly, flash a stock 4.0.4 firmware and start wiping, not even a jtag service fixes that lol. or yeah, as jokesy said, flash a wrong bootloader
theunderling said:
Siyah kernel 3.1rc6 lol
Click to expand...
Click to collapse
Lol, yeah, S3 kernel, I think that should work... I really want to do something that can't be reversed
What do you think? If I flash it, it would still go to the first screen? The one that says "Samsung Galaxy S2", or no response for ever?
Poroto said:
Exactly, flash a stock 4.0.4 firmware and start wiping, not even a jtag service fixes that lol. or yeah, as jokesy said, flash a wrong bootloader
Click to expand...
Click to collapse
Thanks! I almost have all the info I need! Umm.. so if I wipe it's unreversable, and if I flash a wrong bootloader or kernel? Could Jtag service fix that?
Deleted.
Jokesy said:
boot.img as far as i know is the kernel.
1. you need to download bootloader.tar Galaxy NOte GT N7000 (or any other samsung phone) and flash as pda via odin
or
2. you can download Galaxy SII bootloader.tar here.
then remove your cable as soon as odin starts writing the bootloader.
Gameover!
Click to expand...
Click to collapse
Thanks, haha I think I will try to pull out the cable when the flashing start but first I will ask my provider about the warranty of course
Sorted - Can delete thread now.
JakeLee28 said:
Hello, I need help, I have bricked my Galaxy S2.
It won't turn on.
It won't go on download mode (power+home+vol down).
It won't go on to recovery.
Odin won't recognize it when connected.
I think it's the superbrick bug in ICS 4.04.. any kinda help would be appriciated.
Click to expand...
Click to collapse
If it is the brick bug that happens when you use CWM to wipe data or rest 4.0.4 firmware then you have screwed your main board.
There is no fix apart from replacing the main board and that is very costly.
Of course if you are still under warranty then return to Samsung and get a replacement.
What were your actions leading up to the bricked device?
If you wiped on 4.0.4 STOCK kernel, then yeah, only way to fix it is by replacing the entire motherboard which is truly expensive.
Next time, remember to read all the stickys and flash a custom kernel !
yeah it is the superbrick bug. I forgot to install siyah before doing a clean wipe, i took it back to the Carphonewarehouse and they said they will send it off for samsung. I hope my flash counter is not gone up as i flashed CWM from stock recovery.?
JakeLee28 said:
yeah it is the superbrick bug. I forgot to install siyah before doing a clean wipe, i took it back to the Carphonewarehouse and they said they will send it off for samsung. I hope my flash counter is not gone up as i flashed CWM from stock recovery.?
Click to expand...
Click to collapse
Doesn't matter as they will be replacing the mobo anyway.
I would strongly advise reading/researching/learning properly before attempting to play around with expensive devices.
TheATHEiST said:
Doesn't matter as they will be replacing the mobo anyway.
I would strongly advise reading/researching/learning properly before attempting to play around with expensive devices.
Click to expand...
Click to collapse
that's a relief to hear, and yeah that's good advice. I knew about this bug but completely slipped outta my mind when i was doing it, but yeah thanks for the advice
OK maybe someone knows the right protocol and procedure. But let me first tell you my story....
So I was showing off my Galaxy Note Paranoid Android rom to my friend and bragged how great his i9100 *(M!)* would look with one of these pretty ROMS. SO I rooted, flashed a recovery (dual boot) and some beta rom (stupid move)... Later I got a call from him in a panic as he needs his phone more than me and has less patients for this stuff... I instructed him on how to run a recovery back to stock .... and in a few minutes he was smiling again...
.
Fast Forward to last week : and I convinced him again to let me... This time I used the new MIUI and CWM (couldn't find TWRP) and tried formating data factory reset and it would do ok with all the partitions but hang forever on data.... then fail... I tried again and again with different recovery apps until finally
it
HARD BRICKED .... !!!! AHHHH :crying::crying: Not knowing what to do I took it in after attempting the 301k resistor on pins 4 and 5... Nothing happened so I had someone use a RIFF BOX JTAG device and they couldn't do it saying "that the device would not format and the emmc was shot" but he didn't seem to understand what the .PIT files were that I was reading about on here....
AM I RIGHT ? ... is it the .pit files that are needed to fix this ? IF so which ones do I use ? Must I cut the top 8 gigs off ? or can that be avoided and the others fixed ? What did I do to it ? Is it my fault and if so how ?
and finally is it just as simple as JTAGing into Odin using the right .pit and right bootloader files and it's back or what ?
ANYTHING you know could really help me out thanks 10000 times over !
Can you include what was the base Rom ?.
Sent from my GT-I9100 using xda premium
Helllppppp : Pleaseeeee : I beg the forum
Mebin Robin said:
Can you include what was the base Rom ?.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Well I think it was ::: [ROM|04/11] - █ M1UI 2.10.26.v2 █ - MIUI based on CM10! :: But I could be wrong, it was one of the MIUI Nov releases... this phone has so many builds compared to my note i717 which no where near the dev work this phone does .....
but...
really what does it matter... it would seem that it had something to with the formatting the data, even cache seems faulty for a while as I would use CWM's and run data factory format and manual format it would hang for 3+ minutes on the data partition in the stock recovery for example... then reset and go into a boot loop... In the end it wouldn't even mount/unmount data ... Not understanding the potential of a hard brick (still not sure how formatting data causes a hard brick) assume it has something to do with the kernel and this bug though. I tried restoring to a backup .... I SHOULD have used opportunity to flash in download mode with ODIN in a new kernel I think... but I didn't know any better and was at that moment sweating and feeling like crap because I caused or what I did exposed a weakness in his phone....
but... now what ... is it possible that the memory is actually damaged or being this is the i9100 (m!!!!) from Bell Canada is it possible that it is the so called (no Cap erase) bug that some people had.. This unit is one of the first revisions (bought from Bell last Aug)..... So I assume that is what the problem is...
The guy who did the JTAG... was only for 50 bucks.. I opened it he did soldier the JTAG pins.. but he had no luck flashing and told me the EMMC was toast... which leads me to the idea of the .pit files... I am thinking of getting my own RIFF box and doing it myself but because I am in such a tech savy city now there are tonnes of guys willing to do it ... but I figure very few know about the .pit files etc.
DOES SOMEONE HERE know about the .pit files ... ? Does this problem depict a screwed up partition table ? If so what's the easiest way to save some memory 16 gb.... ? not to suggest I am greedy would be happy with 8 if the thing would just turn on.... also maybe I did the resistor wrong should I buy a usb dongle ?
Ohh and assuming it has the bug is there a safe way to rid it of the bug ?
and one other huge question ... Can I just replace the EMMC ? are they for sale and/or the system board ?
so confused please help me ......:crying: :crying: :crying:
Looks like you wiped stuff on MMC_CAP_ERASE enabled kernel. The only way to fix this is motherboard replacement... Sorry.
Sent from my GT-I9100
Dumb and Dumber spring to mind.
I don't think cm10 had that bug
Sent from my GT-I9100 using Tapatalk 2
hikarugo said:
I don't think cm10 had that bug
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I know, but all the symptoms are obviously here...
Sent from my GT-I9100
Does anyone know where I can get a motherboard replacement assuming the emmc is not field replaceable or even in stock...
And can we all say conclusively that there is no help for flashing in a different .PIT without ODIN ?
Take a look at this utility just released for the RIFF-BOX... I speaks directly to the ability to adjust the through JTAG partition tables and .pit files.
http://www.jtagbox.com/jtag-news/ri...ocessing-plugin-emmcdiskpartitions-dll-v2-00/
It seems like there is hope for me with 8 gig .pit after all !
BTW: Would be great... I once saw a site selling the EMMC for it but I couldn't be sure it was socket able and it said no refund so I question if it is OK or bricked....
theunderling said:
Dumb and Dumber spring to mind.
Click to expand...
Click to collapse
Seems a bit harsh when you consider I used CWM's and had no idea about how a formatting a partition could affect any other partition than the one being formatted... I assume not being a developer myself that mostly bricks occur when reading could help you avoid it. I only was able to discover the problem by looking for information regarding a 'hard brick' which I wasn't contending with until after the fact... I assumed it was an issue with the CWM's build and the recovery software itself...
You are welcome to your own opinion about my behavior. But what gets me is that you see no value in offering any valid input to the thread.
I bought a USB jig from eBay, which came in the post this morning. I turned my phone off, removed and inserted the battery, and plugged the jig in.The thing is, it only boots into download mode and doesn't clear the flash counter, and therefore not deleting the yellow triangle.
What is the problem? Is is the firmware? I'm running build 4 SuperNexus 4.2.2 JB ROM. On some website I saw that Samsung removed the ability to clear the counter after some version, and that I have to flash some zip file with odin? Or something to do with the bootloader? What's up with this? I looked around, and only saw threads like these for <4.1, therefore I don't wanna flash it so I don't mess anything up.
Here it is: http://forum.xda-developers.com/showthread.php?t=1354888. It's not for 4.2.2 though.
And here are the bootloader things: http://forum.xda-developers.com/showthread.php?t=1402286 Are they safe to flash? If so, which one?
Another bootloader: http://forum.xda-developers.com/showthread.php?t=1578866
http://www.modmymobile.co.uk/phone-...-remove-yellow-boot-triangle-galaxy-s-ii.html Something to do with samsung removing the ability in the blue box.
Shall I flash the bootloader? And what is the difference apart from the ability to reset the counter between the new one and old one? Or shall I just use TriangleAway?
Can anyone help? Thanks in advance
Try TriangleAway
domdomrys said:
I bought a USB jig from eBay, which came in the post this morning. I turned my phone off, removed and inserted the battery, and plugged the jig in.The thing is, it only boots into download mode and doesn't clear the flash counter, and therefore not deleting the yellow triangle.
What is the problem? Is is the firmware? I'm running build 4 SuperNexus 4.2.2 JB ROM. On some website I saw that Samsung removed the ability to clear the counter after some version, and that I have to flash some zip file with odin? Or something to do with the bootloader? What's up with this? I looked around, and only saw threads like these for <4.1, therefore I don't wanna flash it so I don't mess anything up.
Here it is: http://forum.xda-developers.com/showthread.php?t=1354888. It's not for 4.2.2 though.
And here are the bootloader things: http://forum.xda-developers.com/showthread.php?t=1402286 Are they safe to flash? If so, which one?
Another bootloader: http://forum.xda-developers.com/showthread.php?t=1578866
http://www.modmymobile.co.uk/phone-...-remove-yellow-boot-triangle-galaxy-s-ii.html Something to do with samsung removing the ability in the blue box.
Shall I flash the bootloader? And what is the difference apart from the ability to reset the counter between the new one and old one? Or shall I just use TriangleAway?
Can anyone help? Thanks in advance
Click to expand...
Click to collapse
Never Mess with the 'Bootloader' for now ma8
just use the 'Traingle Away' app to get rid of both the 'Yellow Triangle' and the 'Binary count' for now
Ps- do make a bkp of ur exsisting setup before hand
Sun90 said:
Never Mess with the 'Bootloader' for now ma8
just use the 'Traingle Away' app to get rid of both the 'Yellow Triangle' and the 'Binary count' for now
Ps- do make a bkp of ur exsisting setup before hand
Click to expand...
Click to collapse
Thanks, but I'm kinda freaked out about the line:
"THIS IS A DANGEROUS OPERATION AND COULD POTENTIALLY BRICK YOUR DEVICE. PROCEED AT YOUR OWN RISK. A USB JIG IS PREFERRED IF YOU HAVE A WORKING ONE.
( and by brick I mean brick - only a board replacement or a JTAG unit will be able to save you, don't mess with boot(loader) stuff unless you really mean it! )"
Have you witnessed something like this happen, as you are pretty experienced ? I'm guessing that still, it's probably safer than bootloaders...
It's safer than flashing a bootloader. Just don't go there. Unless you have a very specific reason to & absolutely no alternative (same as flashing a PIT).
You have an alternative.
MistahBungle said:
It's safer than flashing a bootloader. Just don't go there. Unless you have a very specific reason to & absolutely no alternative (same as flashing a PIT).
You have an alternative.
Click to expand...
Click to collapse
Yeah. I might try TriangleAway if I'm gonna be desperate. I can live with the triangle ;D Thanks to everyone who helped.
Triangle Away could (in the worst case scenario) cause a softbrick. I'm sure chainfire wouldn't have released an app that can cause hardbrick, and with his expertise in Android, i bet that's impossible too (unless, if he really wants too)
domdomrys said:
Yeah. I might try TriangleAway if I'm gonna be desperate. I can live with the triangle ;D Thanks to everyone who helped.
Click to expand...
Click to collapse
I've used triangle away 3 or 4 times without any problems at all. It's fast and I believe it's safe!
Cheers!!
I tried Triangle Away, and unfortunately it didn't work. I think this is mainly because of my system being slightly corrupted, as sometimes I don't have signal which requires me to go into the app SGII_repair and do the second option. Also when I press "run tracker" it says that something is wrong and requires a factory reset. I will probably return to stock and then do a clean install of SuperNexus again. Thanks to everyone who helped!
same problem
domdomrys said:
I tried Triangle Away, and unfortunately it didn't work. I think this is mainly because of my system being slightly corrupted, as sometimes I don't have signal which requires me to go into the app SGII_repair and do the second option. Also when I press "run tracker" it says that something is wrong and requires a factory reset. I will probably return to stock and then do a clean install of SuperNexus again. Thanks to everyone who helped!
Click to expand...
Click to collapse
Also using supernexus and Triangle away doesn't reset counter, I wrote chainfire an email and hope for good
If you have succeeded somehow to reset without removing the ROM , please leave instructions .
thanks