Related
Was downgrading from ICS to Gingerbread.....
Loaded all the files into odin and also loaded a 512 pit file? So the flashing starts and on the pit file it froze for ages so i google'd and someone wrote just unplug and retry a flash again.
Unplugged and... Phone doesnt boot at all or doesnt charge or do anything? Tried the download mode keys and plugged in. Computers see's nothing thier.
Any helps guys? Im out of warranty
thats it http://forum.xda-developers.com/showthread.php?t=1807995 and u can't fix it
u have to change the main board then don't use stock kernel again cuz its not safe :cyclops:
but give usb jig a try if didn't work , maybe u should try jtag (maybe bootloader ****ed up )
yahyoh said:
thats it http://forum.xda-developers.com/showthread.php?t=1807995 and u can't fix it
u have to change the main board then don't use stock kernel again cuz its not safe :cyclops:
but give usb jig a try if didn't work , maybe u should try jtag (maybe bootloader ****ed up )
Click to expand...
Click to collapse
Ok i will give them a go... Is the chances my phone is now a door stop?
why flash a pit file to begin with ?
S2 uses the same pit format in GB and ICS so no pit file flashing is needed
LScottB said:
Was downgrading from ICS to Gingerbread.....
Loaded all the files into odin and also loaded a 512 pit file? So the flashing starts and on the pit file it froze for ages so i google'd and someone wrote just unplug and retry a flash again.
Unplugged and... Phone doesnt boot at all or doesnt charge or do anything? Tried the download mode keys and plugged in. Computers see's nothing thier.
Any helps guys? Im out of warranty
Click to expand...
Click to collapse
while flashing pit if u unplug it then basicially ur phone is dead
so confirm it by connecting in to ur charger and keep it for like 20 mins
if the portion near the camera gets hot then u have a hard brick
wither jtag it to recover it
or
if its in warranty get it to the service center and they will change ur mb
Wow, sorry mate, i didn't even know that you can hard brick this phone...
Sent from my GT-I9100 using Tapatalk 2
Ye defo bricked it.
Camera is heating up as says above. How much is a new mainboard for these? Is it usual crazy company prices?
Any companys online that stock the part?
Thanks guys
LScottB said:
Ye defo bricked it.
Camera is heating up as says above. How much is a new mainboard for these? Is it usual crazy company prices?
Any companys online that stock the part?
Thanks guys
Click to expand...
Click to collapse
there are chances to recovery via jtag (Google jtag service to know more) as the brick was caused by pit
or if u have ur phone in warranty then get ti to service center and make sure u don tell them wat u did
neerajganga said:
there are chances to recovery via jtag (Google jtag service to know more) as the brick was caused by pit
or if u have ur phone in warranty then get ti to service center and make sure u don tell them wat u did
Click to expand...
Click to collapse
What do i need for use of the warranty ?
Dont have the receipt but have the box and papers inside etc? No sure if this is of any use. Thiers a repair centre about 20 mile away.
Is thier companys who jtag in the uk ?
Thanks
They ask you for proof of purchase.Theres sellers on eBay offering them services(money back less postage if they cant fix).
Theres a company selling boards for $180 on eBay but only sell to US/Canada.
Sent from my GT-I9100 using xda premium
theunderling said:
They ask you for proof of purchase.Theres sellers on eBay offering them services(money back less postage if they cant fix).
Theres a company selling boards for $180 on eBay but only sell to US/Canada.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thank you !
Seems a company on ebay do it for 20 pound + postage. Under 30 quid
Will give them a go.
Thanks for the help guys
yahyoh said:
then don't use stock kernel again cuz its not safe
Click to expand...
Click to collapse
Yesterday I was stuck on a bootloop when trying to flash Stock ROM.
I was on RR 3.1.2 - Dorimanx 7.12 Kernel and I decided to flash stock rom (4.0.4 - Unbranded UK/Ireland), CheckFus download + Odin method. I was stuck in the S logo for a long time and flashed Stock like 2-3 times again, finally wiped cache + data and flashed again then it was all ok.
Where did I go wrong and did I miss something when flashing stock? Or as said is stock rom / kernel really not safe?
ysrini said:
Yesterday I was stuck on a bootloop when trying to flash Stock ROM.
I was on RR 3.1.2 - Dorimanx 7.12 Kernel and I decided to flash stock rom (4.0.4 - Unbranded UK/Ireland), CheckFus download + Odin method. I was stuck in the S logo for a long time and flashed Stock like 2-3 times again, finally wiped cache + data and flashed again then it was all ok.
Where did I go wrong and did I miss something when flashing stick? Or as said is stock rom / kernel really not safe?
Click to expand...
Click to collapse
they r safe, but with ICS 4.0.4 u should not do anything silly in its stock recovery , since stock rom kernels of 4.0.4 r plagued with the in famous 'mmc cap erase' stuff which will hard brick ur phone
also while dwngrading or upgrading from one android version to another its better to wipe Data/cache to avoid version conflicts
Sun90 said:
stock rom kernels of 4.0.4 r plagued with the in famous 'mmc cap erase' stuff which will hard brick ur phone
Click to expand...
Click to collapse
Read about the mmc_cap_erase in forum and mine was 0x19 and prone to brick. I guess I got luck that day. Did not have to learn it the hard way.
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
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
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...
Hi guys i have a issue here.
My phone was initially rooted in clockworkmod and running cyogenomod 10. But the rom kept hanging which pisses me a little.
So, i did a stock rom install using odin. After the reflash, i can see and hear the startup music, thereafter, it starts to restart. From there on, it reloops at the samsung S3 GT-I9300.
I tried to send to samsung for repair and they couldnt resolve this. Instead the recovery mode was restored back to the original (without clockworkmod now).
With my issues, can you guys help me on this whether can i restore the phone again? Appreciate your comments!
*BTW, i had backup in clockworkmod on my external sd card.
factory reset
Glebun said:
factory reset
Click to expand...
Click to collapse
sorry, i am noob on this, how do i do a factory reset?
kamiru21 said:
sorry, i am noob on this, how do i do a factory reset?
Click to expand...
Click to collapse
BASICS
http://forum.xda-developers.com/showthread.php?t=1927113
or return the phone to a service centre .
jje
Could not do factory reset in software because i cant even get to that.
Did the "reset" in recovery mode by deleting user data files, doesn't work
Is this a complete brick for me?
I do not wanna send in the phone for the MB changeout till i can resolve this.
Anyone knows what to do next? Appreciate the help given.
kamiru21 said:
Could not do factory reset in software because i cant even get to that.
Did the "reset" in recovery mode by deleting user data files, doesn't work
Is this a complete brick for me?
I do not wanna send in the phone for the MB changeout till i can resolve this.
Anyone knows what to do next? Appreciate the help given.
Click to expand...
Click to collapse
If you wont read the basics then yes take to service and pay for a repair as you do not have a clue what you are doing its safer .
jje
I also think something went wrong while flashing. As stated above, try factory reset and flash again. My guess would be you forgot to wipe your (Dalvik) cache, had a similar problem.
JJEgan said:
If you wont read the basics then yes take to service and pay for a repair as you do not have a clue what you are doing its safer .
jje
Click to expand...
Click to collapse
Yes, i will try to read the rest. Seems a lot though.
kuhfi said:
I also think something went wrong while flashing. As stated above, try factory reset and flash again. My guess would be you forgot to wipe your (Dalvik) cache, had a similar problem.
Click to expand...
Click to collapse
u meant the deletion of the cache in recovery mode?
If that is, i had done that also.
You said Samsung didn't manage to fix it? It it was a local repair center?
The only thing to do is to flash a whole complete stock Rom with Odin, see in stock roms there's I'm general section to grab one. You can try also to use Samsung s3 toolkit in original android section, stickies.. if you have a Rom image it will be easier to flash it with it no risk messing with Odin settings.
Perhaps you should read about pit corruption, it can be this also.
Striatum_bdr said:
You said Samsung didn't manage to fix it? It it was a local repair center?
The only thing to do is to flash a whole complete stock Rom with Odin, see in stock roms there's I'm general section to grab one. You can try also to use Samsung s3 toolkit in original android section, stickies.. if you have a Rom image it will be easier to flash it with it no risk messing with Odin settings.
Perhaps you should read about pit corruption, it can be this also.
Click to expand...
Click to collapse
Yes, it is the official samsung service centre. And their service and knowledge really sucks....(in my country)
Thx bro, i will read up and check on PIT corruption as well.
kamiru21 said:
Hi guys i have a issue here.
My phone was initially rooted in clockworkmod and running cyogenomod 10. But the rom kept hanging which pisses me a little.
So, i did a stock rom install using odin. After the reflash, i can see and hear the startup music, thereafter, it starts to restart. From there on, it reloops at the samsung S3 GT-I9300.
I tried to send to samsung for repair and they couldnt resolve this. Instead the recovery mode was restored back to the original (without clockworkmod now).
With my issues, can you guys help me on this whether can i restore the phone again? Appreciate your comments!
*BTW, i had backup in clockworkmod on my external sd card.
Click to expand...
Click to collapse
Just a short update, i had install clockworkmod. But still facing similar issues.
Tried PIT flashing method, still no help...
Hello.. I have faced similar issue in India with looping of logo on my Galaxy S3.
I went to the official service center and they flashed my phone 2 times with original stock rom but the issue did not go.
Finally they have to replace my phone's mother board completely and it got resolved.
I am still not sure how this has happened or is it some kind of virus.. but i was watching a video and my phone hanged and looping of logo started on my S3.
Good that my phone was under warantee so i did not have to pay any money...
But some senior members should through some light on it...
Hi Guys,
i managed to get it back to stock rom by flashing the below linked rom.
The samsung service are really......What they can't solve, they would use the worst scenario which is to change the board...
Actually i have been charged (30 bucks) by them which they can't resolve. They told me that they had flashed the ROM and that incured the charges....I was thinking wat dafuq....Cannot resolve still have the cheek to charge me. Anyway in short, they void my warranty because they saw the cwm. They were very happy when they saw that.... Anyway the warranty left 3 months, not of a issue to me.
For people who have the same issue with me, just flashed the rom (JB) that was in the below link. All the best.
http://forum.xda-developers.com/showthread.php?t=1825272
And not forgetting the seniors and juniors whom helped. Appreciate that!