I had just flashed my phone to CF-Root 5.6. It all went very well, took about 8 seconds, and it rebootet normally.
Then my plan was to update to JELLYBAM - v5.1.0.
I copied the .zip file into the SD card, and entered recovery mode.
I Wiped the data/cache, and installed it.
In the middle of the installation, all of sudden, the phone went black.
I tried to turn it on, put out and in the battery, enter recovery mode and download mode and connect it to the pc. Nothing worked.
I can't get any picture on the phone anymore, and i really need help with this. I have tried everything that i know about.. :crying:
How do i fix this??
rotweb 1-2
Simmyen said:
I had just flashed my phone to CF-Root 5.6. It all went very well, took about 8 seconds, and it rebootet normally.
Then my plan was to update to JELLYBAM - v5.1.0.
I copied the .zip file into the SD card, and entered recovery mode.
I Wiped the data/cache, and installed it.
In the middle of the installation, all of sudden, the phone went black.
I tried to turn it on, put out and in the battery, enter recovery mode and download mode and connect it to the pc. Nothing worked.
I can't get any picture on the phone anymore, and i really need help with this. I have tried everything that i know about.. :crying:
How do i fix this??
Click to expand...
Click to collapse
Hey the exact same thing happened to me yesterday, and I was also installing JellyBam. I followed the exact same steps as you and my phone also went black during installation and is now hard bricked and needs to be JTAG repaired in order to work.
Looks like you guys have encountered phonus brickedus
This happened to me too, yesterday. There are lots of threads that discuss these things. If you cant access anything you can try a jig. (look it up)
I, however, tried jig and JTAG but no solutions found so i sent it to service center. Now i just pray to god that they don't find out that my phone's rooted (which makes my warranty vioded).
As far as my expertise says, if you cant find a Jig or JTAG solution, send it to service. When my phone arrives (if it does) i can tell you if they knew that i had rooted or not.
Regards.
PS. Did you follow it's flashing steps carefully?
WardenBerret said:
Looks like you guys have encountered phonus brickedus
This happened to me too, yesterday. There are lots of threads that discuss these things. If you cant access anything you can try a jig. (look it up)
I, however, tried jig and JTAG but no solutions found so i sent it to service center. Now i just pray to god that they don't find out that my phone's rooted (which makes my warranty vioded).
As far as my expertise says, if you cant find a Jig or JTAG solution, send it to service. When my phone arrives (if it does) i can tell you if they knew that i had rooted or not.
Regards.
PS. Did you follow it's flashing steps carefully?
Click to expand...
Click to collapse
If Jtag couldn't bring it back to life, they won't know, don't worry
WardenBerret said:
PS. Did you follow it's flashing steps carefully?
Click to expand...
Click to collapse
Yes. I followed them very carefully. Did everything that i was supposed to do..
Could it be a bug in the kernel?
Simmyen said:
Yes. I followed them very carefully. Did everything that i was supposed to do..
Could it be a bug in the kernel?
Click to expand...
Click to collapse
What ROM were you on? 4.0.4?
gastonw said:
What ROM were you on? 4.0.4?
Click to expand...
Click to collapse
Yep... the official 4.0.4
gastonw said:
What ROM were you on? 4.0.4?
Click to expand...
Click to collapse
What diff does that make? He was on custom kernel not stock.
Did you guys have at least 55% battery? On some occasions flashing roms can use allot of processing power and drain unusual amounts of battery. For example sometimes I have been on full battery, flashed a rom and its used 40% so if you guys was on low battery it could have died and screwed up your rom, kernel or worse your bootloader resulting in brick.
Sure that custom kernel was safe atheist?
Sounds like emmc to me.....
Sent from my GT-I9100 using xda app-developers app
rsr1 said:
Hey the exact same thing happened to me yesterday, and I was also installing JellyBam. I followed the exact same steps as you and my phone also went black during installation and is now hard bricked and needs to be JTAG repaired in order to work.
Click to expand...
Click to collapse
Exactly the same with me i9100. how can we make it?
Simmyen said:
I had just flashed my phone to CF-Root 5.6. It all went very well, took about 8 seconds, and it rebootet normally.
Then my plan was to update to JELLYBAM - v5.1.0.
I copied the .zip file into the SD card, and entered recovery mode.
I Wiped the data/cache, and installed it.
In the middle of the installation, all of sudden, the phone went black.
I tried to turn it on, put out and in the battery, enter recovery mode and download mode and connect it to the pc. Nothing worked.
I can't get any picture on the phone anymore, and i really need help with this. I have tried everything that i know about.. :crying:
How do i fix this??
Click to expand...
Click to collapse
I also don't think it was the bug as the phone died while flashing the rom, not during the wipe. Perhaps it was a bad download or a link that took users to a rom for the wrong model of phone. Hopefully every user effected will get there phone repaired.
Sent from my GT-I9100 using xda premium
Related
Dear Friends,
I was using a stock de-odexed XWLUP ROM and wanted to try out the Ressurection remix 2.6.1 Rom. Below are the steps i followed.
1) Went into CWM mode, did a wipe data/format
2) Did a wipe cache
3) Selected the Ressurection remix 2.6.1 rom file and started to install
4) In the aroma installer, i selected the custom installation and selected all the options that were displayed.
5) The installation stopped at 50% and it was in the same level for about 10 minutes
6) Suddenly the screen switches off and the phone becomes totally unresponsive.
Below are the methods i tried to get the phone back to life but in vain
1) Tried hard reset and soft reset
2) Tried using a USB Jig but totally unresponsive
It would be great if some experts let me know a way to get my galaxy s2 back to life,
vikranth.reddy said:
Dear Friends,
I was using a stock de-odexed XWLUP ROM and wanted to try out the Ressurection remix 2.6.1 Rom. Below are the steps i followed.
1) Went into CWM mode, did a wipe data/format
2) Did a wipe cache
3) Selected the Ressurection remix 2.6.1 rom file and started to install
4) In the aroma installer, i selected the custom installation and selected all the options that were displayed.
5) The installation stopped at 50% and it was in the same level for about 10 minutes
6) Suddenly the screen switches off and the phone becomes totally unresponsive.
Below are the methods i tried to get the phone back to life but in vain
1) Tried hard reset and soft reset
2) Tried using a USB Jig but totally unresponsive
It would be great if some experts let me know a way to get my galaxy s2 back to life,
Click to expand...
Click to collapse
bricked by kernel wipe bug?
What kernel have you used before flash?
SirKunon said:
What kernel have you used before flash?
Click to expand...
Click to collapse
I was using wanamlite's XWLPU from the below link
HTML:
http://forum.xda-developers.com/showthread.php?t=1436817
I guess the kernel is a Cf-Root LPU kernel.
Just an update incase anyone faces a similar situation.
Took the mobile to the local authorized samsung service center.
They told the motherboard has to be replaced and i got it replaced with no other choice left.
Guess no more flashing and rooting atleast for the next one year
vikranth.reddy said:
Just an update incase anyone faces a similar situation.
Took the mobile to the local authorized samsung service center.
They told the motherboard has to be replaced and i got it replaced with no other choice left.
Guess no more flashing and rooting atleast for the next one year
Click to expand...
Click to collapse
Why?
Your CF-ROOT kernel probably killed your phone. Don't ask me why
Swyped from my Galaxy SII
Cf root is the problem. Someone bicked his phone using this kernel with sammy 4.0.4 while trying to instal cMIUI rom. The same happened to him, installation stopped and screen turned off after a while. He could not save his phone with jig or sth. I don't know he tried jtag. Sorry for grammer mistakes, my brain stopped working yesterday, maybe I became ill.
I'm not certainly sure because I don't use Chainfire kernels since S1, but what I remember he didn't recompile those kernels. Only add unsecured adb and root binary files. If it's true than it is stock 4.0.4 kernel with EMMC CAP ERASE command enabled. This mean that if your EMMC chip is classified as 'INSANE' than every wipe in non stock recovery (any cwm) can brick your phone permanently.
There is a solution but at the cost of 2GB of internal memory. Use modified pit which makes data partition on space dedicated to 'internal sdcard' (user data).
But use this feature only if you can't do anything else.
i9.0.1.3k galaxy imperator
vikranth.reddy said:
Dear Friends,
I was using a stock de-odexed XWLUP ROM and wanted to try out the Ressurection remix 2.6.1 Rom. Below are the steps i followed.
1) Went into CWM mode, did a wipe data/format
2) Did a wipe cache
3) Selected the Ressurection remix 2.6.1 rom file and started to install
4) In the aroma installer, i selected the custom installation and selected all the options that were displayed.
5) The installation stopped at 50% and it was in the same level for about 10 minutes
6) Suddenly the screen switches off and the phone becomes totally unresponsive.
Below are the methods i tried to get the phone back to life but in vain
1) Tried hard reset and soft reset
2) Tried using a USB Jig but totally unresponsive
It would be great if some experts let me know a way to get my galaxy s2 back to life,
Click to expand...
Click to collapse
Are you able to go to the Download mode..?
BlueArc said:
Are you able to go to the Download mode..?
Click to expand...
Click to collapse
Nope dude. I witnessed what i thought was the perfect definition of a hard brick (Meanwhile i thought our S2 is completely unbrickable). Absolutely no life at all in any means.
As i already mentioned, i got the motherboard replaced though i had to bear the expenses.
vikranth.reddy said:
Nope dude. I witnessed what i thought was the perfect definition of a hard brick (Meanwhile i thought our S2 is completely unbrickable). Absolutely no life at all in any means.
As i already mentioned, i got the motherboard replaced though i had to bear the expenses.
Click to expand...
Click to collapse
Hi!
I'm having the same problem as you had! While installing Revolt Rom, the installation stoped after the Aroma installer and the screen suddenly went black!! No more signs of life from my S2... I'm about to send my phone to samsung and see if they repair it under waranty. If the waranty doesn't cover the repair, I'm trying Jtag first.
By the way... How much they charge you for the board?
Cheers!
Try this solution, it may be your last hope:
1. Take everything out of your phone micro sd ,sim battery
2.Get your Usb Port and connect the first side to your pc but not to the phone
3.Insert Battery
4.Hold the vol down butt and at the same time connect the Other side of the cable into the phone then you will see
DOWNLOAD MODE!!!!!
5.From there install your sock rom again using samfirmware.com
6.Done
Click to expand...
Click to collapse
(I don't know who's idea is that, thanks to the author of this if it helps)
i9.0.1.3k galaxy imperator
LPU brick bug free
I will ask Chainfire if LPU kernel is brick bug free or not. Will report it later.
SirKunon said:
Try this solution, it may be your last hope:
(I don't know who's idea is that, thanks to the author of this if it helps)
i9.0.1.3k galaxy imperator
Click to expand...
Click to collapse
Hi!
Didn't work for me. But may help others! Thanks for sharing!
Cheers!
fagundes666 said:
Hi!
I'm having the same problem as you had! While installing Revolt Rom, the installation stoped after the Aroma installer and the screen suddenly went black!! No more signs of life from my S2... I'm about to send my phone to samsung and see if they repair it under waranty. If the waranty doesn't cover the repair, I'm trying Jtag first.
By the way... How much they charge you for the board?
Cheers!
Click to expand...
Click to collapse
Hey, can you tell us which Kernel you was using?
gl
vikranth.reddy said:
Just an update incase anyone faces a similar situation.
Took the mobile to the local authorized samsung service center.
They told the motherboard has to be replaced and i got it replaced with no other choice left.
Guess no more flashing and rooting atleast for the next one year
Click to expand...
Click to collapse
+1
I also bricked my phone when I tried the Wanam's 4.0.4 for the first time, have to send it to Samsung Service center and the findings also have to replace the motherboard. Good thing it's still under warranty.
jashy67 said:
Hey, can you tell us which Kernel you was using?
gl
Click to expand...
Click to collapse
Hi!
I was using Siyah kernel with wanamlite rom. I was so curious about revolt rom and I didn't resist to test it...
Cheers!!
Try this if you can get into download mode you should be good:
Happened to me on Wanam but i didn't do a factory reset for total brick:
Pulling the battery is crucial and then going straight to download mode.
I woke up to find my phone @ the Samsung logo, tried to reboot it and it stuck there.
I then tried to get into recovery and it would not go, just reboot and stick at the logo again.
Pulled the battery, rebooted and the phone booted up and stayed for about 5 seconds then rebooted and stuck again at the Sammy logo
Flashed a stock 4.0.3 successfully and still it stuck at the logo after reboot
Flashed 4.0.3 again and the phone successfully booted
Flashed Siyah and Wanam again successfully.
Proceeded to run the emmc brick test app and test memory
Phone froze during memory test and rebooted and stuck at Sammy logo
Flashed 4.0.3 twice as before and was back up
Ran emmc brick test app and passed the memory test
Now running another 4.0.4 rom with memory test passed.
Click to expand...
Click to collapse
RMonst3r said:
Try this if you can get into download mode you should be good:
Happened to me on Wanam but i didn't do a factory reset for total brick:
Pulling the battery is crucial and then going straight to download mode.
Click to expand...
Click to collapse
Hi!
I can't get into download mode. I can't do nothing with the phone... completely dead! I'm just waiting for a jig I bought on ebay to try to get into download mode.
Thanks for your help!
Cheers!!
Ok well see if the jig works.
Flash twice to be sure and you may want to wipe your usb storage for good measure(you wil loose any files such as pics etc).
Then run this app to error test it:
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
If the jig doesn't work you may have to send it off to Sammy for repair.
fagundes666 said:
Hi!
I can't get into download mode. I can't do nothing with the phone... completely dead! I'm just waiting for a jig I bought on ebay to try to get into download mode.
Thanks for your help!
Cheers!!
Click to expand...
Click to collapse
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 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
Ok, I flashed the experimental 4.2.1 update from temasek earlier. flashed his custom kernel. all worked fine.
Told me my SD Card was 'damaged', which I now understand just needed a fix which was provided. However I decided to just forget it and restore my nandroid backup i'd taken the previous night.
Checked the folder was there, which it was, so booted to CWM, did all the wipes and chose "restore". much to my horror, it failed to find any files.
stupid mistake part: i decided to flash the perseus kernel back over the top to see if the CWM would recognise my nandroid files and restore them
the screen just went mad - had blue lines all over the place, the samsung logo jumped about and the screen went off.
i booted back to CWM and found the touchscreen was unresponsive. everything else worked - buttons, CWM. The phone is also recognised in ODIN, so I grabbed the latest stock JB leak and flashed it. it flashed fine, but it was a middle eastern rom, which didn't help, and the touchscreen was still dead.
the PC still recognised it, so i coped the temasek files back on to see if i could re-flash those, which i did, but still no luck with the touchscreen.
flashed the JB leak again with ODIN, which worked. plugged it in to the PC and copied across a nandroid backup folder i'd taken earlier in the evening last night, since the other one seems to not work. rebooted and it still wouldn't find it.
Now i've got the latest stock rom for the uk but ODIN just won't flash anything - the phone is recognised, the MD5 sum on the rom checks out but i always get "Complete(Write) operation failed" error each time. I plug the phone in to the PC, and it recognises it just fine, but KIES is sitting on the "connecting" screen and not doing anything - i've reinstalled the latest drivers as well.
I'm starting to be resigned to the fact i've killed it, but if anyone has any ideas, i'd be hugely grateful - thankyou
touchscreen dead is getting more and more common. Not sure what is going on but if u cant flash anything from odin maybe u have dead mmc chip or something. Hopefully you resolve it or a trip to sammy service centre hopefully can fix under warranty for u
Edit close down all kies software whilst using odin
Sent from my GT-I9300 using XDA Premium HD app
i dont have warranty as the phone was bought second hand.
i'm just on the phone to my insurance providers though for accidental damage ..it might mean i have to drop it downstairs though !
ooeerr .. rebooted my PC, reconnected to ODIN and it's flashing the UK Stock ROM i got .. fingers crossed. I really don't want to have to drop it downstairs. The insurers will want to inspect it and if there's a custom rom on it, it might get bounced
hankhandsome said:
Ok, I flashed the experimental 4.2.1 update from temasek earlier. flashed his custom kernel. all worked fine.
Told me my SD Card was 'damaged', which I now understand just needed a fix which was provided. However I decided to just forget it and restore my nandroid backup i'd taken the previous night.
Checked the folder was there, which it was, so booted to CWM, did all the wipes and chose "restore". much to my horror, it failed to find any files.
stupid mistake part: i decided to flash the perseus kernel back over the top to see if the CWM would recognise my nandroid files and restore them
the screen just went mad - had blue lines all over the place, the samsung logo jumped about and the screen went off.
i booted back to CWM and found the touchscreen was unresponsive. everything else worked - buttons, CWM. The phone is also recognised in ODIN, so I grabbed the latest stock JB leak and flashed it. it flashed fine, but it was a middle eastern rom, which didn't help, and the touchscreen was still dead.
the PC still recognised it, so i coped the temasek files back on to see if i could re-flash those, which i did, but still no luck with the touchscreen.
flashed the JB leak again with ODIN, which worked. plugged it in to the PC and copied across a nandroid backup folder i'd taken earlier in the evening last night, since the other one seems to not work. rebooted and it still wouldn't find it.
Now i've got the latest stock rom for the uk but ODIN just won't flash anything - the phone is recognised, the MD5 sum on the rom checks out but i always get "Complete(Write) operation failed" error each time. I plug the phone in to the PC, and it recognises it just fine, but KIES is sitting on the "connecting" screen and not doing anything - i've reinstalled the latest drivers as well.
I'm starting to be resigned to the fact i've killed it, but if anyone has any ideas, i'd be hugely grateful - thankyou
Click to expand...
Click to collapse
unfortunately your touchscreen died and your only option is to bring it for warranty because of the bad flash, if you have warranty i suggest follow my simple guide here.
http://forum.xda-developers.com/showthread.php?t=2074756
---------- Post added at 01:52 PM ---------- Previous post was at 01:49 PM ----------
hankhandsome said:
i dont have warranty as the phone was bought second hand.
i'm just on the phone to my insurance providers though for accidental damage ..it might mean i have to drop it downstairs though !
ooeerr .. rebooted my PC, reconnected to ODIN and it's flashing the UK Stock ROM i got .. fingers crossed. I really don't want to have to drop it downstairs. The insurers will want to inspect it and if there's a custom rom on it, it might get bounced
Click to expand...
Click to collapse
still follow the guide so the insurance will not detect that you have been rooted before
chris151722 said:
still follow the guide so the insurance will not detect that you have been rooted before
Click to expand...
Click to collapse
i'll see what i can do but it's now stuck in a bootloop after flashing the rom i grabbed earlier, so will try another one.
i might have to kill it stone dead if none of this works
each rom i try in ODIN never boots - just goes into a bootloop.
i suppose if the insurers do inspect it, they may well not be able to get to see the flash counter if they can't boot it up - so it'll have a stock, unrooted rom on it anyway, so does anyone think i'll be ok ?
hankhandsome said:
i'll see what i can do but it's now stuck in a bootloop after flashing the rom i grabbed earlier, so will try another one.
i might have to kill it stone dead if none of this works
Click to expand...
Click to collapse
after you flash stock firmware go to recovery try to factory reset
---------- Post added at 02:15 PM ---------- Previous post was at 02:11 PM ----------
Ausboy 2011 said:
touchscreen dead is getting more and more common. Not sure what is going on but if u cant flash anything from odin maybe u have dead mmc chip or something. Hopefully you resolve it or a trip to sammy service centre hopefully can fix under warranty for u
Edit close down all kies software whilst using odin
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
its a bad flash from odin and bad flash thru phone the reason why touch is dying.
chris151722 said:
its a bad flash
Click to expand...
Click to collapse
every rom though ?
just tried another one and it's bootlooping ..
hankhandsome said:
every rom though ?
just tried another one and it's bootlooping ..
Click to expand...
Click to collapse
can you access recovery mode? if so try to wipes or factory reset before and after firmware flash
chris151722 said:
can you access recovery mode? if so try to wipes or factory reset before and after firmware flash
Click to expand...
Click to collapse
at the moment i can't access anything - it just sits at the samsung logo now. CWM is now no longer accessible either - i pop the battery, wait a few minutes then put it back in. I hold down Up/Power/Middle button and the Samsung Logo flashes, but nothing happens.
I can still put it in to download mode and flash roms with odin, but nothing happens .. i think i'm going to have to accept it's dead
My last roll of the dice is to grab one of the earlier roms from this thread
http://forum.xda-developers.com/showthread.php?t=1835931
and see what that does in ODIN
FYI:
1. you don't have to wipe anything before restoring a backup, it doesn't make a difference.
2. insurance fraud is a felony
Glebun said:
FYI: 2. insurance fraud is a felony
Click to expand...
Click to collapse
Good job i don't live in the US then ..
I'm pretty sure it's illegal no matter where you live
Well I don't particularly want to get into an argument here, as i'd much prefer a phone that works so i'll just thank you for your input.
i think you have to solve the bootloop issue first by searching in the forum, im not expert so cant give you better advice on bootloop,
chris151722 said:
i think you have to solve the bootloop issue first by searching in the forum, im not expert so cant give you better advice on bootloop,
Click to expand...
Click to collapse
thanks. it doesn't actually bootloop now, it just sits on the glowing samsung logo and doesn't move.
i just want to get a stock rom back on it and i'm going to just let it go. i'm a bit concerned that on the download screen it says "Custom Binary Download: Yes (19 Counts)". I know I did reset the flash counter not too long ago before I flashed the Darky Rom, so if this is indeed the flash counter, then i've obviously not done something right, so it'll show multiple flashes ..
ok, we've had developments ..
i actually got it in to CWM (don't know how..) and did a factory reset. it then did boot up into the OS but - no touchscreen still.
however, i've just tried connecting it to KIES and it's detected it so i'm going to try the emergency recovery thing ..
he says, as he selects the option and KIES then goes back to "connecting" .. *GROAN* .. and then comes back to tell me it's not supported to upgrade firmware via KIES .. *BIGGER GROAN*
Ok, downloaded and flashed an earlier rom for the UK but still no luck with the screen. Kies won't do any kind of emergency firmware upgrade either so that's that. i'll have to try and get one of those OTG USB dongles so i can get the flash counter reset though ..
hankhandsome said:
Ok, downloaded and flashed an earlier rom for the UK but still no luck with the screen. Kies won't do any kind of emergency firmware upgrade either so that's that. i'll have to try and get one of those OTG USB dongles so i can get the flash counter reset though ..
Click to expand...
Click to collapse
Does not reset flash counter only allows access to download mode. Traingle Away to reset flash counter .
jje
JJEgan said:
Does not reset flash counter only allows access to download mode. Traingle Away to reset flash counter .
jje
Click to expand...
Click to collapse
i'm aware of that - that's why I've ordered the OTG dongle so I can use my desktop mouse to go in and install triangle away
I have had my s3 (i9300) for about a year now and was running fine. It was rooted and running custom ROMs.
For a month or so, I noticed that it never switched off. Even when I pressed the power off option it only restarted. The only time when it switched off was when it ran out of battery. And this was irrespective of any rom that I was using.
Someone suggested flashing the stock firmware. I did that with odin but now my phone wont boot at all. The firmware is flashed but the phone just shows the big battery icon with a circle in it. I can get to download mode and stock recovery.
I tried flashing custom recovery using CF root and flashed a custom rom but still the same result. Worse it increased my flash count.
Is there anything short of taking my phone to the service center that can be done? Also since I can boot into download mode and recovery, Is there anyway to reset the counter? I know triangle away does that but I cant boot so…..
gadgetcraze said:
I have had my s3 (i9300) for about a year now and was running fine. It was rooted and running custom ROMs.
For a month or so, I noticed that it never switched off. Even when I pressed the power off option it only restarted. The only time when it switched off was when it ran out of battery. And this was irrespective of any rom that I was using.
Someone suggested flashing the stock firmware. I did that with odin but now my phone wont boot at all. The firmware is flashed but the phone just shows the big battery icon with a circle in it. I can get to download mode and stock recovery.
I tried flashing custom recovery using CF root and flashed a custom rom but still the same result. Worse it increased my flash count.
Is there anything short of taking my phone to the service center that can be done? Also since I can boot into download mode and recovery, Is there anyway to reset the counter? I know triangle away does that but I cant boot so…..
Click to expand...
Click to collapse
You did do a full wipe after flashing the new roms right?
wangdaning said:
You did do a full wipe after flashing the new roms right?
Click to expand...
Click to collapse
In stock recovery yes (data and cache). From cwm (data cache and dalvik) also. Let me try that again
what file did you flash?
does the recovery show any errors?
gadgetcraze said:
I have had my s3 (i9300) for about a year now and was running fine. It was rooted and running custom ROMs.
For a month or so, I noticed that it never switched off. Even when I pressed the power off option it only restarted. The only time when it switched off was when it ran out of battery. And this was irrespective of any rom that I was using.
Someone suggested flashing the stock firmware. I did that with odin but now my phone wont boot at all. The firmware is flashed but the phone just shows the big battery icon with a circle in it. I can get to download mode and stock recovery.
I tried flashing custom recovery using CF root and flashed a custom rom but still the same result. Worse it increased my flash count.
Is there anything short of taking my phone to the service center that can be done? Also since I can boot into download mode and recovery, Is there anyway to reset the counter? I know triangle away does that but I cant boot so…..
Click to expand...
Click to collapse
Once you flash a stock ROM, factory reset the phone from stock recovery. That'll solve the issue of reboot loop. :good:
Be warned, you'll lose all data in the internal SD card.
Glebun said:
what file did you flash?
does the recovery show any errors?
Click to expand...
Click to collapse
Stock Firmware for my country downloaded from sammobile.
When the phone boots into Recovery, there is a dead green bot and an exclamation mark.
It says
manual mode
Appling Multi-CSC
Applied the CSC code BTU
Successfully applied multi CSC
Oomahey said:
Once you flash a stock ROM, factory reset the phone from stock recovery. That'll solve the issue of reboot loop. :good:
Be warned, you'll lose all data in the internal SD card.
Click to expand...
Click to collapse
Did not work
are you sure the file you flashed is for your model?
Glebun said:
are you sure the file you flashed is for your model?
Click to expand...
Click to collapse
I am. It was not the latest one though. I will download the latest one and give it another shot. Maybe. But if this was a firmware problem, the phone would get stuck at the samsung logo. Would'nt it? Instead the samsung logo never comes on and I just see that battery sign.
And as I mentioned, I had this problem where the phone would not switch off even if I select power off. Even after a battery pull it would boot up on its own. Even now, as I put in the battery, it starts showing the battery symbol with a circle in it. I suspect the two problems may be interconnected and may be related to a hardware failure.
I had a working phone before. Just to fix the power off thing, I might have bricked my phone.
gadgetcraze said:
I am. It was not the latest one though. I will download the latest one and give it another shot. Maybe. But if this was a firmware problem, the phone would get stuck at the samsung logo. Would'nt it? Instead the samsung logo never comes on and I just see that battery sign.
And as I mentioned, I had this problem where the phone would not switch off even if I select power off. Even after a battery pull it would boot up on its own. Even now, as I put in the battery, it starts showing the battery symbol with a circle in it. I suspect the two problems may be interconnected and may be related to a hardware failure.
I had a working phone before. Just to fix the power off thing, I might have bricked my phone.
Click to expand...
Click to collapse
Have you got a backup of your efs, if not pull it from your device while you can. Use ADB from recovery to do it.
Something else on you device is causing the power button issue. Could be some mod, or just some corruption. Are you getting other signs when booting?
Last resort, use Kies. Follow the guide posted on here. Don't plug in your device, select emegency (firmware) recovery, give the info (serial number) and plug in when prompted. Back up your efs first if you can. ADB pull the efs is /dev/block/mmcblk0p3.
wangdaning said:
Have you got a backup of your efs, if not pull it from your device while you can. Use ADB from recovery to do it.
Something else on you device is causing the power button issue. Could be some mod, or just some corruption. Are you getting other signs when booting?
Last resort, use Kies. Follow the guide posted on here. Don't plug in your device, select emegency (firmware) recovery, give the info (serial number) and plug in when prompted. Back up your efs first if you can. ADB pull the efs is /dev/block/mmcblk0p3.
Click to expand...
Click to collapse
I did backup my efs folder when I rooted my phone first. Hope that suffices. Can you point me to the guide for emergency recovery? I could locate this. http://forum.xda-developers.com/showthread.php?t=1984717
That guide would be correct, but make sure you use your model number. For international, I believe it is GT-I9300, and has to be written that way.
wangdaning said:
That guide would be correct, but make sure you use your model number. For international, I believe it is GT-I9300, and has to be written that way.
Click to expand...
Click to collapse
Worked partially. Now wont reboot. At least I was able to set the counters to 0 before it went dead again. Thanks for the help.
After working for a while, on resetting the phone, it went completely dead. I took the phone to the service center and it turned out to a case of defective mini usb jack. Maybe the reasons it was booting up in between on change of softwares was just a matter of chance.
Thanks for the help.