[Q] Help me to brick my SGSII! - Galaxy S II Q&A, Help & Troubleshooting

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

Related

CWM Question

Hey guys
I've never modded my phone at all when it comes to custom ROM's, etc. My friend told me today that he flashed a CM9 ICS nightly build and it sparked some interest in me.
I read that to get the CM9 ROM you need to have CWM installed on your phone. Is that necessary? If so, why?
I also read that it will void my phones warranty if I install CWM...now obviously nothing is "suppose" to go wrong with the phone while doing this process and I heard that if the phone is soft bricked it can be recovered with nvflash (is this true?).
Finally, is there anything stopping me from flashing a stock bootloader (is that what CWM is?) onto the phone and then a stock ROM, allowing me to do a return on the phone without them knowing?
I'm completely new to this and this whole forum is so confusing and the only real easy instructions I found were on the CM9 site.
Thanks guys,
Elliott
EDIT: I also just saw on this video: http://www.youtube.com/watch?v=1uK-k3KfY5c
He used some sort of USB dongle at the end for something...what did it do?
Everything you need and more in the relevant thread. With such basic questions and the apparent lack of ability to search, read and digest information, you would be wiser to stick to stock, official ROMs though.
http://forum.xda-developers.com/showthread.php?t=1419102
Thanks but of course that did not answer any of my questions. I have already seen that and obviously you didn't read my post correctly. I am more interested in the warranty issues with doing this...and if it's possible to comletely revert everything to the point where they can't tell what was done with the phone...I have searched around.
What issues do you think you'll run into that will warrant you sending the phone in? Im on my second samsung phone and they've been flawless, warranty be damned, flash away.
CWM "clockworkmod" is a recovery mode replacement for the stock SGS2.
It's used to do a number of things, one of which is to flash items to the device such as full roms or kernels. I'll let you read up on the rest. Without the need to have your device connected to a pc.
Flashing anything unofficial is bound to void your warranty whether via CWM or Odin etc.
The older bootloader allows the use of a USB jig to reset the warning triangle and flash counter to conceal any warranty voiding activity. At some point (can't remember when) Samsung updated the bootloader to prevent the jig working. A simple flash of the older one fixes the issue and doesn't appear to affect the device usage.
There are some great articles on xda to read about flashing etc. Worth a look.
Hope this helps.
Sent from my GT-I9100 using XDA
peachpuff said:
What issues do you think you'll run into that will warrant you sending the phone in? Im on my second samsung phone and they've been flawless, warranty be damned, flash away.
Click to expand...
Click to collapse
Hey
Well I'm not planning on the phone having any issues...but you never know what could happen...When I first got my SGS2 the home button stopped working within 24 hours and I had to go back and get another one...
I'm just saying anything could happen...ex: buttons breaking, etc.
aceofclubs said:
CWM "clockworkmod" is a recovery mode replacement for the stock SGS2.
It's used to do a number of things, one of which is to flash items to the device such as full roms or kernels. I'll let you read up on the rest. Without the need to have your device connected to a pc.
Flashing anything unofficial is bound to void your warranty whether via CWM or Odin etc.
The older bootloader allows the use of a USB jig to reset the warning triangle and flash counter to conceal any warranty voiding activity. At some point (can't remember when) Samsung updated the bootloader to prevent the jig working. A simple flash of the older one fixes the issue and doesn't appear to affect the device usage.
There are some great articles on xda to read about flashing etc. Worth a look.
Hope this helps.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Hey thanks for posting.
So you're saying that if I flash CWM, and then need to return the phone for whatever reason, I can install the original Samsung recovery tool that was there prior to installing CWM? Is that what you mean by "a simple flash of the older one..."?
Basically, if I ever need to return the phone, can I make it reset 100% original so that even if they knew how to check for stuff like CM9 and CWM, they wouldn't be able to find out that it was ever installed?
And when Samsung releases their official firmware and I decide I want to flash to that one, can I still use it? I'm guessing I could just flash it normally using CWM, but what if I wanted to go back to 100% original and update from there?
Starholdest said:
Thanks but of course that did not answer any of my questions. I have already seen that and obviously you didn't read my post correctly.
Click to expand...
Click to collapse
Well that kind of attitude just irks me.
Unless I lack the ability to count, you asked a total of five questions, all of which are answered in that thread and countless others around this forum.
Anyway, your apparent main concern has to do with wanting to commit fraud. If you're okay with that, keep going. I guess since you're happy to break forum rules (rule #1), why not try and fudge a warranty claim?
Yes you can return your device to completely Telco/carrier stock.
If you want to do it...
Make a CWM backup.
Backup everything to pc from internal SD. A simple copy will do.
Use CWM to format internal SD.
Boot into download mode and flash Telco/carrier stock firmware via Odin.
Use jig to reset flash counter.
Use stock recovery to wipe device.
This should be as it was when you pulled it out of the box on day one.
When you get it back use cfroot kernel to root via Odin.
Copy SD card backup from pc to SD.
Restore CWM backup.
Should now be as it was before resetting to stock. Except maybe the modem if you like a different one from Telco/carrier stock.
Sent from my GT-I9100 using XDA
aceofclubs said:
Yes you can return your device to completely Telco/carrier stock.
If you want to do it...
Make a CWM backup.
Backup everything to pc from internal SD. A simple copy will do.
Use CWM to format internal SD.
Boot into download mode and flash Telco/carrier stock firmware via Odin.
Use jig to reset flash counter.
Use stock recovery to wipe device.
This should be as it was when you pulled it out of the box on day one.
When you get it back use cfroot kernel to root via Odin.
Copy SD card backup from pc to SD.
Restore CWM backup.
Should now be as it was before resetting to stock. Except maybe the modem if you like a different one from Telco/carrier stock.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Excellent thanks for your help!
So as soon as I boot into download mode and flash telco/carrier stock firmware via Odin, will CWM be erased? Also, what about what this gentleman said?
The older bootloader allows the use of a USB jig to reset the warning triangle and flash counter to conceal any warranty voiding activity. At some point (can't remember when) Samsung updated the bootloader to prevent the jig working.
Click to expand...
Click to collapse
What if I have the updated bootloader?
Yes CWM is removed by flashing official firmware so original recovery from then.
If jig doesn't work use Odin to flash the old bootloader. It definitely will work then.
Sent from my GT-I9100 using XDA
aceofclubs said:
Yes CWM is removed by flashing official firmware so original recovery from then.
If jig doesn't work use Odin to flash the old bootloader. It definitely will work then.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Great thanks for all your help.
Going here to see the stock firmware (I guess bootloader is the same thing?), and scrolling down to the "Bell" section, there are two items listed there.
http://forum.xda-developers.com/showthread.php?t=1113928
UGKG2: http://www.multiupload.com/WHKOJ8A5FG
Firmware info: PDA: UGKG2 Phone: UGKG2 CSC: BMCKG2
UGKG2 Stock Kernel:http://www.multiupload.com/43QUKBBK47
Password is: [email protected]
Click to expand...
Click to collapse
What's the difference between the two?
The first link has the entire rom, the 2nd has just the kernel. However...
These links have been dead for a while now, so you'll need to head over to Samfirmware.com & search for the firmware you need. Follow whatever instructions they have for flashing firmware downloaded from their site.
Starholdest said:
Great thanks for all your help.
Going here to see the stock firmware (I guess bootloader is the same thing?), and scrolling down to the "Bell" section, there are two items listed there.
http://forum.xda-developers.com/showthread.php?t=1113928
What's the difference between the two?
Click to expand...
Click to collapse
Thanks. And what is the difference between just the kernel and the whole thing? Is kernel just another word for bootloader? I looked up the terms briefly...
Also, samfirmware.com doesn't have the one I have...is there another source or something?
The rom has stuff like themes, fonts, and other stuff (nuts & bolts) the kernel is like the engine (controls stuff like WiFi, controls everything you can do as root, etc). The package containing the whole rom also has the kernel in it.
No idea. Do a Google search. Alternatively, you can get the latest firmware available for your country/carrier (which may or may not be the same as the one you're looking for, depending on whether the carrier has updated firmware since the one you're looking for was released) with the PC version of Checkfus (do a search for it on here Google).
Edit to add - A better analogy for rom/kernel. Think of your phone as a car. The kernel is the engine, the rom is everything else/the car itself.
Starholdest said:
Thanks. And what is the difference between just the kernel and the whole thing?
Also, samfirmware.com doesn't have the one I have...is there another source or something?
Click to expand...
Click to collapse
Bootloader etc.
Starholdest said:
Excellent thanks for your help!
So as soon as I boot into download mode and flash telco/carrier stock firmware via Odin, will CWM be erased? Also, what about what this gentleman said?
What if I have the updated bootloader?
Click to expand...
Click to collapse
I think everyone has cleared everything else for you, so I'll talk about the jig! Firstly you most likely have the new bootloader so your flash counter will still be on, therefore your warranty will still be void. LUCKILY there's an app called TriangleAway (made my Chainfire) which you can find with a simple search, this will let you reset your flash counter and get rid of the yellow triangle as long as you're running a rooted ICS ROM (like CM9) and you can then flash back to stock and all traces of any root will be gone. There is a warning that the app can brick your phone but through my many uses of it, it has never happened and no-one has reported any brick.
Cool thanks for your help!

Thread can be deleted now

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

Another Bricked GS2 Thread :( Help please!!

Hello everyone,
Hoping you can help me before my mrs cuts my nuts off. She asked me to update her GS2 (GT-I9100 on 02) and completly wipe the phone as she has had random apps appear etc etc.
I said that wouldnt be a problem as ive done alot on my GS3, though i am still pretty new to the Android scene (Previously iPhone).
So she was on Stock 4.0.4 XXLQ6 firmware.
I followed the guide to root from here as i was aware of the hardbrick bug in this firmware.
http://forum.xda-developers.com/showthread.php?t=1501719
After that it was time for the Wipe data etc and flash the new rom. I chose JELLYBAM as its Android 4.2 with a mix of other things. Sounded perfect.
I followed all the steps EXACTLY from the Devs page:
http://www.igio90.net/how-to-install/
All seemed to be going well at first, got to select afew options etc. Then it said it was Extracting the package...This is were the problems started.
It was stuck at 2% for AGES, then out of the blue the screen just went BLACK/BLANK......Hmmmm i thought!
I have since been trying to source info from everywere about how to turn the phone back on but having no luck at all. I have tried all the Soft/Hard boot methods, ive left it on charge (Yes it gets hot near the camera) and tried all boot methods whilst plugged into laptop with ODIN loaded up.
Nothing seems to be working.
Any help what so ever will be much appreciated. This device was never previously rooted. Im gutted a it was all going so well...I shoulda guessed something would go wrong.
Toon
Are you able to enter download mode? If you can make sure you have samsung drivers installed! Also JellyBam rom is not only for i9100 but other models too, are you sure you had the right rom? If you can't enter downlaod mode then try a USB jig?
Sent from my GT-I9100 using xda premium
UltimateAnas said:
Are you able to enter download mode? If you can make sure you have samsung drivers installed! Also JellyBam rom is not only for i9100 but other models too, are you sure you had the right rom? If you can't enter downlaod mode then try a USB jig?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thank you for your reply, Unfortunatly i cannot enter any mode what so ever. The phone is literally dead...yet getting VERY hot as its plugged in.
Was thinking about taking it in to O2 2mora and seeing what they can do. Damn.
If your still under warranty you should get a new motherboard.They won't be able to tell you've rooted it since it seems hard bricked.
Next time,get a custom kernel on it a.s.a.p and backup efs and make a nand backup before you start flashing roms.
Either that or stay away from 4.0.4 stock.
Sent from my GT-N7000 using xda premium
theunderling said:
If your still under warranty you should get a new motherboard.They won't be able to tell you've rooted it since it seems hard bricked.
Next time,get a custom kernel on it a.s.a.p and backup efs and make a nand backup before you start flashing roms.
Either that or stay away from 4.0.4 stock.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks for your reply, I did put a custom kernal (Sirayh?) on it prior.
The phone was a year old august just gone! Not sure Samsung be interested.
See if you can get your hands on a usb jig.If that fails try for a jtag.
Samsung warranty should be 24 months if you need it.
Sent from my GT-N7000 using xda premium
So you did a wipe on a Samsung 4.0.4 ROM with original kernel? Then you have indeed hardbricked your phone. You said you were aware of this bug, so I can't figure out why you would do a wipe?
Cenobite_ said:
So you did a wipe on a Samsung 4.0.4 ROM with original kernel? Then you have indeed hardbricked your phone. You said you were aware of this bug, so I can't figure out why you would do a wipe?
Click to expand...
Click to collapse
No i changed the kernal, but followed the guide posted by DEV to install the ROM. Guessing i made a mistake somewere down the line as the phone is bricked!!
JIG & JTAG....will these help solve my problem? Not really clued up on them though i have done a brief look around. JTAG services is not in my area.
NO, on hardbricked S2 JIG/JTAG won't be useful. You can check my thread http://forum.xda-developers.com/showthread.php?t=1756242 for more info.
PS : the direct signs of this kind of hardbrick is a totally dead phone & back side getting hot (near the camera lens)
googy_anas said:
NO, on hardbricked S2 JIG/JTAG won't be useful. You can check my thread http://forum.xda-developers.com/showthread.php?t=1756242 for more info.
PS : the direct signs of this kind of hardbrick is a totally dead phone & back side getting hot (near the camera lens)
Click to expand...
Click to collapse
Is there any way to fix this or do i owe my mrs a new phone?
Just took it to a repair store and he said its knackered, but to be honest he wasnt much help...more interested in the texts he was getting on his phone!.....Typically a GS2...Im still pondering if he was taking the micky :silly:
if your s2 is still under warranty, just take it to the reapir service and tell them that the phone was on charge all night and didn't wake up in the morning
they won't be able to know what you did to it since it's completely unaccessible. If you successfully convince them, they'll change the motherboard !
PS : That isn't my idea but from what I saw in the hardbrick warning thread, most of the concerned people did the same trick ...
googy_anas said:
if your s2 is still under warranty, just take it to the reapir service and tell them that the phone was on charge all night and didn't wake up in the morning
they won't be able to know what you did to it since it's completely unaccessible. If you successfully convince them, they'll change the motherboard !
PS : That isn't my idea but from what I saw in the hardbrick warning thread, most of the concerned people did the same trick ...
Click to expand...
Click to collapse
Yeah i think this is the route imgoing to have to take Just spoke with them regards my GS3 and they said itll be 2 weeks to repair and return. No phone for 2 weeks
I just got off the phone with Samsung and they are taking it in for repair. No local service centers so im awaiting a jiffy bag. Then 2 weeks to get the phone back!
Plese, need help, tried to downgrade firmware from 4.0.4 to 4.0.3 using Odin and now i'm getting an error: android.process.acore has stopped, and can't really do anything.
is there anything I could do now or is my phone bricked?
Thanks in advance!
Pooshkis said:
Plese, need help, tried to downgrade firmware from 4.0.4 to 4.0.3 using Odin and now i'm getting an error: android.process.acore has stopped, and can't really do anything.
is there anything I could do now or is my phone bricked?
Thanks in advance!
Click to expand...
Click to collapse
Please be more specific if you expect anybody to bother to help you.
When you say "can't really do anything" that doesnt tell us what you have tried and not tried!
1) Can you enter recovery mode?
2) Can you enter download mode?
3) Have you tried a USB Jig?
4) Have you removed battery for 30 mins?
5) What happens when you power on phone?
TheATHEiST said:
Please be more specific if you expect anybody to bother to help you.
When you say "can't really do anything" that doesnt tell us what you have tried and not tried!
1) Can you enter recovery mode?
2) Can you enter download mode?
3) Have you tried a USB Jig?
4) Have you removed battery for 30 mins?
5) What happens when you power on phone?
Click to expand...
Click to collapse
Sorry.
1) Yes
2) Yes
3) trying to find now what it is
4) For 30 mins no, for few minutes - yes
5) It starts and then i got some errors memo.process, process.acore and few others (can't remember now). I can get email, explore through home screens and menus, but can't call, receive calls, write messages, look up contacts or memos and stuff only going through screens. Maybe I could do a hard reset or wipe the phone, but then won't i brick my phone?
EDIT: As user Pilaf suggested (thanking him a lot!) I installed a new siyha kernel then did a full wipe / factory reset, seems everything is backing up from google account and phone is working..
So you're telling me that the official 4.0.4 has a hardbrick bug? Well that's great.
Should I just wait for the official 4.1 or can I flash for example the Siyah kernel and then start flashing other ROMs?
krnrdstrm said:
So you're telling me that the official 4.0.4 has a hardbrick bug? Well that's great.
Should I just wait for the official 4.1 or can I flash for example the Siyah kernel and then start flashing other ROMs?
Click to expand...
Click to collapse
Did you just get released from a 6 month stretch in jail/or been in a coma or something.
Sent from my GT-N7000 using xda premium
theunderling said:
Did you just get released from a 6 month stretch in jail/or been in a coma or something.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
:laugh:
Come on man, he's serious, so let's answer seriously
@krnrdstrm : to avoid the hardbrick, just flash a safe kernel (siyah, speedmod, dorimanx, philz ...) and enjoy ...
PS : didn't you have internet in jail ? :silly:
emmc bug
krnrdstrm said:
So you're telling me that the official 4.0.4 has a hardbrick bug? Well that's great.
Should I just wait for the official 4.1 or can I flash for example the Siyah kernel and then start flashing other ROMs?
Click to expand...
Click to collapse
Yea, have a look here http://forum.xda-developers.com/showthread.php?t=1756242
Siyah should be good,
Thanks: googy_anas

[Q] [HELP!] S3 wont even boot

So my S3 went into a boot loop. And I dont know how I got to this point but now the phone wont even boot, when plugged in to my comp it shows the battery symbol but its greyed out with the circle in the middle, and it stays like that. If i hold the power putton it comes up with the Galaxy SIII GT i9300 screen but then goes back to the battery. I can get it to go into download mode though. I think somehow I may have deleted all the files required for the phone to actually boot(Im a n00b so im not completely sure) Can somebody please help me?
I was on custom ROM before and my binary counter is at 4, so sending into samsung doesn't sound like a great idea :/
Thanks for the help and sorry if this has been asked before, I have searched for hours.
Luke2508 said:
So my S3 went into a boot loop. And I dont know how I got to this point but now the phone wont even boot, when plugged in to my comp it shows the battery symbol but its greyed out with the circle in the middle, and it stays like that. If i hold the power putton it comes up with the Galaxy SIII GT i9300 screen but then goes back to the battery. I can get it to go into download mode though. I think somehow I may have deleted all the files required for the phone to actually boot(Im a n00b so im not completely sure) Can somebody please help me?
I was on custom ROM before and my binary counter is at 4, so sending into samsung doesn't sound like a great idea :/
Thanks for the help and sorry if this has been asked before, I have searched for hours.
Click to expand...
Click to collapse
If you also can go into recovery, try to wipe. In addition did you flash any custom kernel?
If not, try to reflash a rom with odin after you got into download mode or did you try this already?
Sent from my GT-I9300 using xda app-developers app
chrismast said:
If you also can go into recovery, try to wipe. In addition did you flash any custom kernel?
If not, try to reflash a rom with odin after you got into download mode or did you try this already?
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
If you mean with CWM mod, no I cant, it just shows the Galaxy S3 GT i9300 screen then goes black. Yes i did have a custom kernel, I believe it was the latest Perseus one. I already tried this with a stock rom and it idnt work, it said it had passed but i still can boot the phone.
Luke2508 said:
If you mean with CWM mod, no I cant, it just shows the Galaxy S3 GT i9300 screen then goes black. Yes i did have a custom kernel, I believe it was the latest Perseus one. I already tried this with a stock rom and it idnt work, it said it had passed but i still can boot the phone.
Click to expand...
Click to collapse
as you can go into download mode but not recovery, what about flashing CWM another time (if you did not try it already). Maybe it solves the issue with recovery and from there you could go on trying to wipe etc.
Other options would be to do a mega or super wipe (if this is possible from odin & download mode, not sure though), to get your phone completely empty (mega) or at least to factory reset (super).
Luke2508 said:
So my S3 went into a boot loop. And I dont know how I got to this point but now the phone wont even boot, when plugged in to my comp it shows the battery symbol but its greyed out with the circle in the middle, and it stays like that. If i hold the power putton it comes up with the Galaxy SIII GT i9300 screen but then goes back to the battery. I can get it to go into download mode though. I think somehow I may have deleted all the files required for the phone to actually boot(Im a n00b so im not completely sure) Can somebody please help me?
I was on custom ROM before and my binary counter is at 4, so sending into samsung doesn't sound like a great idea :/
Thanks for the help and sorry if this has been asked before, I have searched for hours.
Click to expand...
Click to collapse
Look at the tread above yours,sudden death.
You are not the only one here mate.
I have it too.
Mods,can we have one tread for this huge problem.
It seems that there are many of us have this problem.
Thanks.
painterceessie said:
Look at the tread above yours,sudden death.
You are not the only one here mate.
I have it too.
Mods,can we have one tread for this huge problem.
Pointless having another thread why not post /read the original thread for this problem .
a hint look for sudden death thread
jje
Click to expand...
Click to collapse
chrismast said:
as you can go into download mode but not recovery, what about flashing CWM another time (if you did not try it already). Maybe it solves the issue with recovery and from there you could go on trying to wipe etc.
Other options would be to do a mega or super wipe (if this is possible from odin & download mode, not sure though), to get your phone completely empty (mega) or at least to factory reset (super).
Click to expand...
Click to collapse
I successfully flashed CF root with CWM, now shall I do a wipe and then restore back to a nandroid backup I made? and if so how will I? The phone now shows the samsung logo when turned on but just stays there forever.
JJEgan said:
painterceessie said:
Look at the tread above yours,sudden death.
You are not the only one here mate.
I have it too.
Mods,can we have one tread for this huge problem.
Pointless having another thread why not post /read the original thread for this problem .
a hint look for sudden death thread
jje
Click to expand...
Click to collapse
Oke sorry mate.
I didn't no that.
Click to expand...
Click to collapse
Furthermore i suggest anyone having motherboard dead problems and vendor Samsung saying no warranty .
To pull up the many posts regarding this now known manufacturing defect and don't accept in this case root/ custom rom warranty is rejected .
jje
JJEgan said:
Furthermore i suggest anyone having motherboard dead problems and vendor Samsung saying no warranty .
To pull up the many posts regarding this now known manufacturing defect and don't accept in this case root/ custom rom warranty is rejected .
jje
Click to expand...
Click to collapse
The thing is there is nothing wrong with my phone in terms of hardware. The problem that I am having is purely software, I think I just need to restore my phone to a previous version. I did see that thread but didnt feel my post belonged there as my problem is nothing to do with broken battery or mobo or anything along those lines. Hence why I am posting here
Just factory reset via recovery then flash a stock rom via Odin .
No recovery flash CF root via Odin .
jje
JJEgan said:
Just factory reset via recovery then flash a stock rom via Odin .
No recovery flash CF root via Odin .
jje
Click to expand...
Click to collapse
I did install a stock ROM and it was still stuck on bootloop, left it like that for an hour, still nothing. So I went into CWM (after flashing it) Wiped and factory reset (noticing it said error mounting /data but ignored) and then restored with a backup I had. it did say error mounting /data and so skipped that step. Still stuck in boot loop. now that I try wiping again the same error occurs, error mounting /data any ideas please?
I did have this problem a few days back. The only thing i did was downloaded my Carrier stock firmwaer and extracted boot.img and used Samsung galaxy toolkit and make a filé that i was able to use with Odin. Dunno if ot helps you but my Phone is still going strong
I was only trying to root my Phone tho. No custom rom installera when i got The boot problem
Sounds like you have permission problem. I can't find the three about that but I update my post here if I can find it.
you can try to fix permission in cwm it seems, hope it works
Sent from my GT-I9300 using xda app-developers app
xda-napp3 said:
I did have this problem a few days back. The only thing i did was downloaded my Carrier stock firmwaer and extracted boot.img and used Samsung galaxy toolkit and make a filé that i was able to use with Odin. Dunno if ot helps you but my Phone is still going strong
I was only trying to root my Phone tho. No custom rom installera when i got The boot problem
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks, do you have any idea where I will find my carrier specific firmware? And any other kind of tips on how to do/get things? But hopefully this works
Checkout this thread hope you find what you need there
http://forum.xda-developers.com/showthread.php?t=1927113
Sent from my GT-I9300 using xda app-developers app

Have I fallen in to the superbrick bug?

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...

Categories

Resources