Hello,
I have Galaxy S2 Canadian Rogers version SGH- I727R with GB 2.3.5. I wanted to Install a custom Rom into my phone for that i followed below
steps :
1. Root with CWM recovery
2. Wipe data
3. Installed this "http://forum.xda-developers.com/showthread.php?t=1824586" rom through recovery.
I rooted and installed CWM recovery successfully. wiped data successfully phone was ok till then.
after that installed the rom. Rom installation was successful as well. after that i select reboot phone but my Phone never Reboot.
I removed the battery for few minutes then put that back in and tried to start the phone but my phone is dead now. When i Flashed my battery was fully charged. so this is not a low battery issue.
What went wrong Here. Please can anyone Help me. How can i Start my phone again...Please..need help urgently
Can u enter recovery or download mode ?
Thats an ICS rom and you where on GB, you should never flash ics roms on gb
No i cant enter in Download or Recovery mode. If i could then this should be solved.
My phone is total dead now. Please give me any solution or tell me a way to turn my Phone On..
killer_nave said:
No i cant enter in Download or Recovery mode. If i could then this should be solved.
My phone is total dead now. Please give me any solution or tell me a way to turn my Phone On..
Click to expand...
Click to collapse
Wave a magic wand maybe??
If your phone is totally dead as you say what do you expect us to say other then get it fixed? You will need to send it away for JTAG flash or mobo replacement. Only thing you could try really is a USB jig see if it forces it into download mode.
Also why on earth create this topic when we have plenty of this EXACT same subject? no need to create another when you can go read them or reply if needed.
i just want to know, what went wrong that my phone is not starting?? i just followed every steps i found in the forum
but after flashing the rom all went wrong..
WITHOUT JTAG flash is there any other way left with the help of software i can start the phone???
Nope. As my learned colleague has already intimated, in scientific terms, your phone is Donald. Service centre or possibly JTAG repair by 3rd party repairer; will be cheaper than having Samsung/authorised repairer fixing/replacing it if it can be repaired this way.
killer_nave said:
i just want to know, what went wrong that my phone is not starting?? i just followed every steps i found in the forum
but after flashing the rom all went wrong..
WITHOUT JTAG flash is there any other way left with the help of software i can start the phone???
Click to expand...
Click to collapse
Good Lord.
You apparently know what your phone model is, because it's in the title of your thread.
The ROM you said you tried to install is an i9100 ROM. NOT a ROM for the SGH-I727.
MAYBE you should have made sure the ROM you tried to install was for your model of phone before you did so?
Your model has a totally different SoC than the i9100. That is what happened.
killer_nave said:
Hello,
I have Galaxy S2 Canadian Rogers version SGH- I727R with GB 2.3.5. I wanted to Install a custom Rom into my phone for that i followed below
steps :
1. Root with CWM recovery
2. Wipe data
3. Installed this "http://forum.xda-developers.com/showthread.php?t=1824586" rom through recovery.
I rooted and installed CWM recovery successfully. wiped data successfully phone was ok till then.
after that installed the rom. Rom installation was successful as well. after that i select reboot phone but my Phone never Reboot.
I removed the battery for few minutes then put that back in and tried to start the phone but my phone is dead now. When i Flashed my battery was fully charged. so this is not a low battery issue.
What went wrong Here. Please can anyone Help me. How can i Start my phone again...Please..need help urgently
Click to expand...
Click to collapse
I hate to be the bearer of bad news but your issue is one of two things. Galaxy S2 phones have something called the emmc brick. It often occurs when flashing a new rom from recovery. Unfortunately it is a hard brick, and is unable to be recovered from. For more details on the emmc brick there is sticky in S2 forum.
The other likely but equally unfortunate scenario is you flashed an improper rom that contained a kernel that was not intended for your device.
The symptom for both of these issues are a phone that does not turn on, as if you were trying to turn it on without battery in. Your best option is to have rogers send it off for repair as long as you remain within warranty period and be hopeful they don't refuse repair or replacement due to voided warrenty.
Wish I could offer you a better solution, and I wish you the best of luck in your situation.
Side note: just a couple comments directed at those who replied with less than helpful responses. Let's try a little to have some empathy for people. Chewing the ops head off for not replying in a pre established thread and for making a mistake and flashing the wrong rom is not productive at all and paints a pretty nasty image on us as a community. Consider for a moment the circumstances surrounding this thread, the op is likely stressing out or even worse panicking because he fears he has ruined his device and all we can do is berate him for his mistakes. Put yourself in his or her shoes.
Thank you.
Sent from my SGH-I757M using Tapatalk 2
skodazek said:
I hate to be the bearer of bad news but your issue is one of two things. Galaxy S2 phones have something called the emmc brick. It often occurs when flashing a new rom from recovery. Unfortunately it is a hard brick, and is unable to be recovered from. For more details on the emmc brick there is sticky in S2 forum.
The other likely but equally unfortunate scenario is you flashed an improper rom that contained a kernel that was not intended for your device.
The symptom for both of these issues are a phone that does not turn on, as if you were trying to turn it on without battery in. Your best option is to have rogers send it off for repair as long as you remain within warranty period and be hopeful they don't refuse repair or replacement due to voided warrenty.
Wish I could offer you a better solution, and I wish you the best of luck in your situation.
Side note: just a couple comments directed at those who replied with less than helpful responses. Let's try a little to have some empathy for people. Chewing the ops head off for not replying in a pre established thread and for making a mistake and flashing the wrong rom is not productive at all and paints a pretty nasty image on us as a community. Consider for a moment the circumstances surrounding this thread, the op is likely stressing out or even worse panicking because he fears he has ruined his device and all we can do is berate him for his mistakes. Put yourself in his or her shoes.
Thank you.
Sent from my SGH-I757M using Tapatalk 2
Click to expand...
Click to collapse
He was running GB, does the emmc brickbug also affects GB ? I thought it only affected 4.0.4 running stock kernel
Poroto said:
He was running GB, does the emmc brickbug also affects GB ? I thought it only affected 4.0.4 running stock kernel
Click to expand...
Click to collapse
no it will affect only the stock ICS v4.0.4, that to with the stock kernel's of those firmwares ma8
the OP's issue is mainly because he flashed a rom meant for i9100 on his phone, since both the phones i1900 and I727R have diff hardware altogether
i9100 - 1.2ghz with Exynos chipset and mali 400 gpu.
I727R- 1.5ghz with Scorpion chipset and adreno 220 gpu.
Related
Hey all, I come from SGS4G forums, I know my way of flashing and whatnot with that device. However, a friend of mine owns a SGSII and has a weird issue that I hope you guys can help me fix.
The thing is, the device no longer recognizes the SIM card, or any other sim card. She already tried it on another device and the SIM is working fine. Also, the IMEI got corrupted.
I asked her what she was doing or what did she do with the phone. She told me that she was playing the sims and the battery died. So she plugged it in, waited a few minutes and then she turned it on.
After booting up, the phone didn't recognize the SIM card anymore.
As for ROM installed, she never replaced original ROM, nor ever tried to root the phone. This is what her device status states:
Baseband version: unknown
Kernel: [email protected]#2.
Build gingerbread.uhkg7
I really don't know how to proceed in this case. If it was my SGS4G, I would try to flash another modem using odin, but I don't know how it's done with this sgs2. So I ask the experts here to help me a bit.
Thanks in advance!
ps: i have no access to the device, my friend lives in a town far, far away.
I guess she didn't have efs backup, there are guide to recover imei I think it was in general thread, if those guides don't work, her pretty much final chance is to contact xda member called odia, he can restore imei's
Sent from my sgs2 running cm9 using xda app
If the phone is running stock firmware, why would you risk voiding the warranty by messing around with it ? If you stuff it up, your friend will either end up with a $500 paperweight, or she'll end up paying to have it repaired.
In other words, tell her to send the phone in for warranty repair/replacement. It's a no brainer.
MistahBungle said:
If the phone is running stock firmware, why would you risk voiding the warranty by messing around with it ? If you stuff it up, your friend will either end up with a $500 paperweight, or she'll end up paying to have it repaired.
In other words, tell her to send the phone in for warranty repair/replacement. It's a no brainer.
Click to expand...
Click to collapse
I was just asking if there was an "easy" way to fix this, like, flashing some other rom. If that didn't work we would just rollback to stock.
Anyway, looks like we're going to go with the warranty card this time.
I'm still open for suggestion though, I can't believe this device would damage itself just by running out of battery when playing a game.
And yeah, no efs backup I'm afraid.
There isn't easy fix for this
Sent from my sgs2 running cm9 using xda app
It's not a matter of an easy fix. There's never an easy fix for borked EFS details. You risk stuffing the phone up & voiding the warranty in the process, which means if your friend wants it fixed, she ends up paying whatever it costs on top of what she's forked out for the phone.
Use the warranty, she pays nothing.
Think about it.
Edit to add - Also bear in mind you're going to be telling her what to do with the phone given you don't have access to it yourself. If she misunderstands something you tell her to do, kaput.
mikeflash said:
I was just asking if there was an "easy" way to fix this, like, flashing some other rom. If that didn't work we would just rollback to stock.
Anyway, looks like we're going to go with the warranty card this time.
I'm still open for suggestion though, I can't believe this device would damage itself just by running out of battery when playing a game.
And yeah, no efs backup I'm afraid.
Click to expand...
Click to collapse
You could try first a factory reset
Then flash stock firmware both have been known to occasionally fix IMEI .
Did for me once .
jje
JJEgan said:
You could try first a factory reset
Then flash stock firmware both have been known to occasionally fix IMEI .
Did for me once .
Click to expand...
Click to collapse
The first thing I suggested my friend was to do a factory reset. However, it didn't make any difference. In fact, I thing she came across with an error message saying something about not being able to mount efs files or something like that (she wasn't very clear, but she did mention EFS).
I would definitely try to odin (or kies) another stock ROM but since it isn't my phone and my friend isn't too tech savvy either then I think it's better to send it back for warranty.
Thank you all
Hey guys need some help. I've gone through as much of the forums as possible and still trying to resolve this without having to send it away.
My brother's SGS II has the following symptoms:
-turns on and stays at the SGS II GT-i9100 screen (will not change)
-phone can enter download and recovery modes
-when phone is plugged in to charge the battery symbol will not show that it's charging then continue to the SGS II GT-i9100 screen...then back to the battery icon (and loop)
-attempts to reflash anything will either be successful or fail in ODIN but still results in the 1st issue above.
What should I try next?
Hi,
your searching skills are enormous
http://forum.xda-developers.com/showthread.php?t=1108499
http://forum.xda-developers.com/showthread.php?t=1457458
..
wow they are sticked
*edit*
fullwipe - flash via CWM Recovery, thats what i would try
greetz
Are you using pit file when you flash with odin ? could be partition problem so using pit would fix that
Please don't tell people to flash pit files unless you know for absolute certain their problem (which at this stage is vague/undiagnosed; I.E we don't know what the problem is exactly) will be fixed by flashing a pit.
(You should know) flashing a pit can permanently bork a phone if that isn't what's wrong with the phone :-|
Thanks for the sarcasm my friend but when I say i've gone through most of the forum as possible I meant I've tried both those fixes to no avail...thanks anyway though :good:
leechseed said:
Hi,
your searching skills are enormous
http://forum.xda-developers.com/showthread.php?t=1108499
http://forum.xda-developers.com/showthread.php?t=1457458
..
wow they are sticked
*edit*
fullwipe - flash via CWM Recovery, thats what i would try
greetz
Click to expand...
Click to collapse
yeah right now I haven't gone any pit routes yet. I've gone through both boot/bricked guides and right now it's a wash...hell i'm getting a loop between the battery screen and GT-i9100 screen now.
MistahBungle said:
Please don't tell people to flash pit files unless you know for absolute certain their problem (which at this stage is vague/undiagnosed; I.E we don't know what the problem is exactly) will be fixed by flashing a pit.
(You should know) flashing a pit can permanently bork a phone if that isn't what's wrong with the phone :-|
Click to expand...
Click to collapse
OK. What we really need to know is exactly what's been done to the phone. Every little detail (important). From before it started acting up till now. Time to interrogate your brother & find out exactly what he's been doing with/to the phone.
The more info we get the better the chance you don't have to blindly flash that recovery package in the 2nd thread Leechseed linked to with the pit file & hope it works without knowing exactly what/why is wrong with the phone.
He was doing an upgrade to the Omega rom I believe (sorry I'm a galaxy 1 guy so I'm not familiar with the s2 roms). It was flashed succesfully but once it rebooted that was all she wrote...phone just sat there at the GT-i9100 screen.
So at this point we've tried the ICS recovery, the ginerbread recovery and the i9100M recovery (that's the version he has). All the 1 file tars will run through successfully but the ones with the multiple files (phone, csc, pda) will hang up in odin on the DATAFS:
http://i297.photobucket.com/albums/mm235/sirknattar/Untitled.jpg
MistahBungle said:
OK. What we really need to know is exactly what's been done to the phone. Every little detail (important). From before it started acting up till now. Time to interrogate your brother & find out exactly what he's been doing with/to the phone.
The more info we get the better the chance you don't have to blindly flash that recovery package in the 2nd thread Leechseed linked to with the pit file & hope it works without knowing exactly what/why is wrong with the phone.
Click to expand...
Click to collapse
There's some details missing somewhere. It just doesn't make sense for a phone to do that upgrading a rom under normal circumstances. So you have two choices essentially given you've already tried the obvious. You could send it in for warranty service, hope they don't care it's been messed with & repair it. Tho there's obviously a better than even chance you will end up paying for it (not unreasonably).
Or I guess you could flash whatever recovery package from that thread with the PIT file & hope that fixes whatever is wrong with it. Obviously if it doesn't that makes it certain you're either sending it to Samsung/an authorised repairer (quite possibly for repair at your expense, unless they don't notice/care), or to a 3rd party repairer (again at your expense; might be cheaper than Samsung if they decide to charge you for the repair).
Given the info you've provided, there's absolutely no clues whatsoever as to what caused it to happen. Unless someone else reads the thread & has other ideas. Might want to hold off on the PIT for a while & see if someone else does have other ideas given that's pretty much a final step.
Doing the .pit and re-partition as we speak and hangs up on the exact spot...DATAFS (data.img). *sigh*
I'm going to try the bootloader option next. I know my bro says he's done it already but I want to be sure. Thanks for your help man.
MistahBungle said:
There's some details missing somewhere. It just doesn't make sense for a phone to do that upgrading a rom under normal circumstances. So you have two choices essentially given you've already tried the obvious. You could send it in for warranty service, hope they don't care it's been messed with & repair it. Tho there's obviously a better than even chance you will end up paying for it (not unreasonably).
Or I guess you could flash whatever recovery package from that thread with the PIT file & hope that fixes whatever is wrong with it. Obviously if it doesn't that makes it certain you're either sending it to Samsung/an authorised repairer (quite possibly for repair at your expense, unless they don't notice/care), or to a 3rd party repairer (again at your expense; might be cheaper than Samsung if they decide to charge you for the repair).
Given the info you've provided, there's absolutely no clues whatsoever as to what caused it to happen. Unless someone else reads the thread & has other ideas. Might want to hold off on the PIT for a while & see if someone else does have other ideas given that's pretty much a final step.
Click to expand...
Click to collapse
here's another note...when flashing bootloader it comes up into the recovery screen and says "E: failed to mount /data (unknown error: 0)
trying a format data/system
MistahBungle said:
There's some details missing somewhere. It just doesn't make sense for a phone to do that upgrading a rom under normal circumstances. So you have two choices essentially given you've already tried the obvious. You could send it in for warranty service, hope they don't care it's been messed with & repair it. Tho there's obviously a better than even chance you will end up paying for it (not unreasonably).
Or I guess you could flash whatever recovery package from that thread with the PIT file & hope that fixes whatever is wrong with it. Obviously if it doesn't that makes it certain you're either sending it to Samsung/an authorised repairer (quite possibly for repair at your expense, unless they don't notice/care), or to a 3rd party repairer (again at your expense; might be cheaper than Samsung if they decide to charge you for the repair).
Given the info you've provided, there's absolutely no clues whatsoever as to what caused it to happen. Unless someone else reads the thread & has other ideas. Might want to hold off on the PIT for a while & see if someone else does have other ideas given that's pretty much a final step.
Click to expand...
Click to collapse
MistahBungle said:
Please don't tell people to flash pit files unless you know for absolute certain their problem (which at this stage is vague/undiagnosed; I.E we don't know what the problem is exactly) will be fixed by flashing a pit.
(You should know) flashing a pit can permanently bork a phone if that isn't what's wrong with the phone :-|
Click to expand...
Click to collapse
Seems I must have been lucky over the last 24 months having flashed 100's of times with Odin and pit file on SGS 1, 2 and 3 and not bricked 1 yet in fact I've never known anyone brick an SGS flashing a rom with pit other phones maybe but not SGS's
yeah i'm comfortable with flashing pit files due to my weekly rom addiciton from my SGS/cappy hahaha
Anyway I may be experiencing that corrupt SD card issue i've been reading about...not sure.
sminky01 said:
Seems I must have been lucky over the last 24 months having flashed 100's of times with Odin and pit file on SGS 1, 2 and 3 and not bricked 1 yet in fact I've never known anyone brick an SGS flashing a rom with pit other phones maybe but not SGS's
Click to expand...
Click to collapse
Why dont you just try to flash a Stock Rom??
I would try that first - wipe - flash Stock (via CWM)
I always used the ONE file package of Roms and never had any probs..
Why on earth are you re partitioning with Odin? You know Odin isn't build for the S II, and the re-partitioning it does is for the Nexus or something. IE using Odin to re partition an S II royally ****s it. Flashing a PIT might work but why don't you just start at a logical place, before going out and doing a full manual JTAG on your phone with a pair of pliers, some masking tape and a bunsen burner, why don't you do the obvious. Which is update your Odin, uninstall Kies and reinstall it for the Samsung drivers, check the USB etc. something is clearly going wrong during the flash process despite it being "successful". Failing that, take it back to the shop, if your phone isn't a £500 paper weight by the time you read this, just apply for a new one. Make sure you erase any evidence of you messing around with it and return it.
sirknattar said:
He was doing an upgrade to the Omega rom I believe (sorry I'm a galaxy 1 guy so I'm not familiar with the s2 roms). It was flashed succesfully but once it rebooted that was all she wrote...phone just sat there at the GT-i9100 screen.
So at this point we've tried the ICS recovery, the ginerbread recovery and the i9100M recovery (that's the version he has). All the 1 file tars will run through successfully but the ones with the multiple files (phone, csc, pda) will hang up in odin on the DATAFS:
http://i297.photobucket.com/albums/mm235/sirknattar/Untitled.jpg
Click to expand...
Click to collapse
The problem might be the Omega rom ??? is it compatible with I9100M series or just the I9100 the M could be the clue to the flash failing same as when Samsung released the I9100G and people who flashed that got screwed up with the incorrect bootloaders since the hardware is different in the I9100 and I9100G same problem might exist with I9100M
Thanks for everyone's help and suggestions. I've got a vague idea of the problem now and it's being sent back to Samsung for warranty (after I clear it with the JIG).
try to do the following.
1-flash any gingerbread CF kernel via odin
2-boot into recovery mode
3- wipe everything under mounts and storage including system partition
4-reboot into download mode
5-try to flash the CM9 Resurrection Edition
hope this helps mate. mine just emmc bricked on me, with the crappy LQ5 samsung firmware and had to RMA the bastard.
check ur pm mate
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
I'm guessing the infamous brick bug is responsible.
What was your configuration before flashing the new ROM?
What ROM and kernel?
Sent from a GT-I9100 having a mind of its own
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
I'm sorry bro but you might have suffered from the infamous super brick bug and your inability to read.
Solution:
Package the phone and send it to Samsung repair center
Swyped from Samsung Galaxy SII
TechnicallyImpaired said:
I got a brand new BELL SGS2HDLTE yesterday model SGH757 and flashed CWM, everything was ok. This morning I decided I wanted to flash a samsung based ICS rom specifically this on here (http://forum.xda-developers.com/showthread.php?t=1569686). I booted into CWM Recovery, wipe/factory reset wiped cache and dalvik cache and installed the ROM. The setup show up and eventually said complete please reboot. I pressed reboot and the phone turned off and refuses to turn on anymore. The battery was at 44% when I was flashing, even if I plug the phone in via usb nothing happens. I've tried taking out the battery for a few second and putting it back in but nothing happens. I can't boot into CWM or DL mode either, its as if the phone is completely dead... Can someone tell me whats going on here??? I never had an issue like this on my old SGS.. Thanks in advance!
Click to expand...
Click to collapse
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
ctomgee said:
No offense to the two responders above me, but you can ignore them.
The problem is that you attempted to flash a firmware not meant for your phone.
You yourself said you have an SGH-I757. Well, that ICS ROM you linked that you tried to flash is for the GT-i9100. The two models have different hardware, so firmwares, kernels, and ROMs are NOT compatible between them.
This probably screwed up the bootloader. Your only course of action at this point will probably be either JTag repair, or sending it to Samsung for repair.
Click to expand...
Click to collapse
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
TechnicallyImpaired said:
Thanks for not being a douche bag in your response, much appreciated. Thanks for the info BTW, I just got myself a new one and I'll be more careful now. My biggest annoyance with native ICS on this phone is one is looks like gingerbread and two it comes with a tonne of bloatware that you can't remove without rooting ect. At this point should I flash CWM again since it installed successfully last time, root, and use that as a method to remove the unwanted bloatware. I'm so hesitant to flash this phone now, it seems it was much ease on my SGS1.
Click to expand...
Click to collapse
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
ctomgee said:
Just make sure you stick to flashing things meant for your model. Those things compatible with your device will be clearly labeled with the model number.
Problem is the SGH-i757 doesn't have its own forum, so stuff for it gets posted in here.
Click to expand...
Click to collapse
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
TechnicallyImpaired said:
Yup, I've found a few but I also have a few questions maybe you can help me with. According to this thread ( http://forum.xda-developers.com/showthread.php?t=1756242) only stock ICS v 4.0.4 is effected by this superbrick. The SGS2 I hardbricked earlier today was updated to this version via keys to 4.0.4 before installing the custom ROM. So provided I stick to ROMS such as lets say the one here (http://forum.xda-developers.com/showthread.php?t=1740188) and avoid upgrading to 4.0.4 I should be able to CWM + Flash + Root correct? I should also be able to do the standard factory reset / wipe cache / wipe dalvik? I also used the eMMC Brickbug Check app in the first post I liked under how to AVOID the superbrick and it came up saying my chip was sane. Thanks in advance and also I pressed the thank you button
Click to expand...
Click to collapse
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
ctomgee said:
The brick bug may not affect you at all. The most common Galaxy S2 affected is the i9100, which we have established is NOT your device. And you already used the app that said your chip is "sane", so it's confirmed you don't have to worry about it.
Again, you bricked the device by flashing a ROM meant for a different device. Had nothing to do with the brick bug.
Click to expand...
Click to collapse
Thanks, I wasn't aware flashing a rom not meant for your device can cause a hard brick to the point where you cant turn anything on and no buttons are responsive ect. Thanks for the help.
Hey I recently rooted my Samsung Galaxy S II I9100, at first everything was fine, but i had some trouble installing apps so i used es file manager to install them, it began to work for some apps. anyway, this morning I woke and turned it on and it didn't get past the bootscreen(i left it for about 45 minutes on one occasion, and I tried rebooting many times.
The first thing i did after attempting to boot my device was to flash the kernel again via odin, this did not work(tried twice).
so i did a lot of research over the past 10 hours into my problem and have tried many different things; installing a stock rom, removing battery, pretty much anything on the forums that people said have worked. nothing.
I can get into recovery mode and download mode.
I don't care about my data on my phone, it has already been wiped.
It's still covered by warranty so i can wipe the flash count(?) and send it in for warranty IF I HAVE TO. preferably not however.
although i highly doubt it, I may have been using the wrong rom, and I may have forgotten to reset my phone before one of the re-flash's
So if you havn't figured out my question by now, how do i return my phone to working condition?
Don't get mad at me for making a thread that has probably been made a hundred times, none of the solutions in the other threads fixed my problems, and I was browsing not only xda but other forums for hours, I found that reason enough to post a new thread. Apologies if this is in the wrong section, I am new here, and never found it necessary to create an account until now, when I couldn't find a solution.
Help is appreciated, this problem is really rustling my Jimmies on Christmas day.
because this is such a problem, I will REWARD anyone who presents a working solution that does not involve sending it off for warranty or buying a jig. Sorry if i missed out some information, please request for missing info in a response.
1.forget about warranty and jig....that has nothing to do with your current situation.
2.post the details about your phone and what firmware your on and what crap you were flashing.
Maybe a simple reset/wipe in stock recovery is needed.
.
theunderling said:
1.forget about warranty and jig....that has nothing to do with your current situation.
2.post the details about your phone and what firmware your on and what crap you were flashing.
Maybe a simple reset/wipe in stock recovery is needed.
Click to expand...
Click to collapse
originally i was on ics 4.0.3, and i used this tutorial galaxys2root.com/galaxy-s2-root/how-to-root-galaxy-s2-i9100-icsandroid-4-0/ (can't post url link because im a new user) and this kernel by the file name "CF-Root-SGS2_XX_XEO_LPQ-v5.3-CWM5.tar". I then searched for stock roms for it and got "CF-Root-SGS2_XX_OXA_KP8-v5.2-CWM5.tar" and "CF-Root-SGS2_XX_XEO_LPQ-PROPER-v5.4-CWM5.tar"
If you want a stock rom go to Sammobile,join(so you can download).....then input smartphone>android>your phone model>your country/carrier.
Choose whatever 4.0.3 it recommends after you input the above and hit send.
Then flash that with Odin and see what happens.
Then report back here.
I am from Australia and when I searched for roms for the I9100, no Australian roms showed :s
would one from another country work, or would that be locked or...?
Theres 3 listed for starters for the plain gt-i9100.....is that your exact model....or is it p/g/m etc.
This is why I asked for your model.
gt-i9100 is my model that's all it said in my phone information in the settings (before it stuffed up), manual, on start up and in download mode.
sorry, I'm not excellent with my technical android terminology.
false alarm, it just didn't load properly before, I will start a the download (will take like 15 minutes) and report back when i flash it. gt-i9100 is definitely my model.
You just input which one of these 3 applies,hit send,then download.
Then flash it (the extracted file)in download mode with Odin.
so i put the extracted file in the 'PDA' field, put it into download mode, plug it in and start the process?
Yep.
It failed the first 2 tries, I think I have a bad usb cord, but worked the third, might of been what stuffed it up in the first place maybe (?), thank you so much for your help man
Good.Wait til boxing day til you flash siyah-s2.v.4.1.5 kernel for root.......lol.
hehe... yeah... I'm not going to try root again... lol
syntaxibles said:
It failed the first 2 tries, I think I have a bad usb cord, but worked the third, might of been what stuffed it up in the first place maybe (?), thank you so much for your help man
Click to expand...
Click to collapse
Going back to your first post,maybe you could make a donation to one of the developers on this site of your choosing.
sounds good, which developer in particular would be a good choice?
I quite like Doomlord,but its up to you
And just post back on this thread if you need help rooting etc.
Hi all,
I have had my S3 since July '12 and in true Android style rooted it and started flashing ROM's left right and centre. Eventually I stuck on Omega, mainly because I got bored of continually flashing a ROM, installing my fave apps, restoring backups from Titanium, setting up my settings etc...
Christmas eve came and, having some time off work, I decided to start flashing some new ROM's...
Jump forward a few hours.... Tried CM10... liked it but wanted more of the Google/stock bits and pieces back so went to flash another ROM off XDA.
All of a sudden the phone goes off. Phone hard bricked. Wouldn't turn on, wouldn't charge... I shat myself.
I got a little brave and RMA'd to Samsung hoping that if its hard bricked they'll just swap the system board or whatever, and thankfully, a few weeks later and I have my phone back. Yay me!
First thing phone does when I connect to my home Wifi, OTA. Only a small update, and wasn't really paying attention as I was still setting up the phone.
Left it stock for a week and then decided I needed root. Rooted phone using the Samsung S3 all in on toolkit v7 from the XDA boards. All well.
So now I'm a little gun shy of flashing my phone, especially after reading a note in Christiano Matos' ROM thread for crDroid v11 about flashing various Bootloaders; and admittedly not properly understanding it as it seems a little Google-translate jumbled up.
Also http://crave.cnet.co.uk/mobiles/samsung-galaxy-s3-sudden-death-security-flaw-fixed-in-uk-50010094/ makes me a little nervous...
Is the 'hard brick' a hardware fault (and as such I wouldn't link it to any software or ROM I installed and something I'd hope my replacement phone wouldn't suffer twice) or a software issue that can be exploited (in which case which update is it that fixes it and do all decent ROM's include this update)?
And finally, what ROM do people suggest? I want to get rid of the Samsung bloat and have a nice speedy UI with plenty of battery life.
(ignore the FoxHound banner in my sig!!)
Post from crDroid thread:
Quote:
- SAMSUNG APPARENTLY SUDDEN DEATH PREVENT: AS YOU GUYS KNOW SOME S3 I9300 IS SUFFERING WITH A WEIRD BUG THAT SIMPLY ENDS IN SUDDEN DEATH .
USE WITH LAST STOCK, PERSEUS, BOEFFLA OR YANK55.LU KERNELS AND PHILZ RECOVERY.
THIS LATEST FIRMWARE XXELLA COMES WITH NEW BOOTLOADER APPARENTLY THAT FIX THIS BUG. THE BAD NEWS IS: THIS BOOTLOADER CAN ONLY BE INSTALLED THROUGH ODIN PACKAGE. BUT WE DON'T WANT THIS, RIGHT?
FLASHING THIS BOOTLOADER BECOME UNABLE TO GET BACK TO THE OLD ONE. BINARY COUNTER CAN'T BE RESETED (STAY ALWAYS WITH 1 COUNT).
HERE IS A LINK WITH BOOTLOADER FILES. ONLY FLASH IT WITH ODIN PC AND PUT IN PDA FIELD.
If you're scared then just don't do it.
I highly doubt your brick had anything to do with flashing ROMs, just Samsung ****ing up on the hardware front again.
You don't really need to flash any new bootloaders etc. because if it breaks like it did before,you know what's going to happen - Samsung will fix your phone, and that's it.
If you don't like the stock Samsung firmware, try CM10.1. Read about bugs etc. before you start crying about things not working though, because it still isn't, and most probably never will be 100% stable.
bortak said:
If you're scared then just don't do it.
I highly doubt your brick had anything to do with flashing ROMs, just Samsung ****ing up on the hardware front again.
Click to expand...
Click to collapse
Exactly what I thought, until I hardbricked my cousins S2 on the weekend. Never ever thought it could happen. Seems like Samsung is releasing firmware/kernels on the S2 that can hardbrick a phone whenever any sort of wipe is performed in cwm recovery.
Sticky from the S2 forum:
http://forum.xda-developers.com/showthread.php?p=36947154
Anyway, this is the last thing I wanted to hear. Fingers crossed it was just a one off and not actually related to flashing.
Sent from my GT-I9300 using xda premium
well, basically if you don't touch BOOTLOADER staff , it should be highly unlikely to brick devices , except in the case they released problematic firmware as once i bricked my Nexus S with problematic bootloader released by Google... damn it ...
only thing concerns me about S3 is SDS , but i have installed patched recovery and kernel i think i can breath a little easier now ... but still don't like taking ticking bomb around my pocket... it really sucks...
Seems like Samsung is releasing firmware/kernels on the S2 that can hardbrick a phone whenever any sort of wipe is performed in cwm recovery.
Click to expand...
Click to collapse
You are referring to the brickbug in _leaked_ firmware builds. All official releases by Samsung are not affected.
Also the bug is not only triggered by CWM but by every major operation when a kernel with the MMC_CAP_ERASE flag set.
but still don't like taking ticking bomb around my pocket... it really sucks...
Click to expand...
Click to collapse
Afaik the problem was related to a ****-up in the SSD's wear leveling - so if it is fixed it is fixed =)
Btw, just because it is _now_ impossible to reset the flash counter does not mean it will never be. Samsung does not use eFuse's so there is always a hidden switch that can be reset =)
For CM10 - I never expected the full functionality that Samsung's own firmware had, or at least not the polish and extra apps that are bundled but to be honest, I can live without SVoice, kies etc.
I have read the thread on SDS and have checked my phone with eMMC check (and also advised three others who I work with to check their S3's too), and I have also updated recovery (TWRP) to latest version so I should have some protection... shouldnt I?
I think I will stick with stock for now, see what comes in the future, and what Samsung release through OTA etc. (BTW phone was bought outright by me so is UK Unlocked, no branding).
Dear @OP.
Feel free to answer all your questions by yourself. I'd recommend you to stop being lazy, move your ass and read a few things, starting from here as it triggered your attention.
Furthermore, personally I would recommend you to read carefully this to avoid your threads being locked.
In relation to above, I'd like to recommend you visiting this section of XDA Froums, if you want to use something customized. If not, feel free to use this top secret trick to find Stock ROMS here on XDA....
Wow! Who knew! Consider me put in my place... [edit]
Now I will go and beat myself with a wet towel tied in a knot at the end.
If you want to flash the ELLA firmware then flash it but if you need to get bacck to an older bootloader to reset you counter with Triangle Away then flash the CWM Zip below in recovery.Its an oldr bootloader thats CWM flashable.Perfectly safe as Ive flashed it myself.The SDS problem will be in all i9300 models that have the emmc 0xf1 revision chip.You can check it with this app.Doesnt matter if it says you are safe or not as it wrongly checks for the error.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Flash an official firmware and then a custom kernel with the SDS patch fix.Im using yank555
cooza said:
If you want to flash the ELLA firmware then flash it but if you need to get bacck to an older bootloader to reset you counter with Triangle Away then flash the CWM Zip below in recovery.Its an oldr bootloader thats CWM flashable.Perfectly safe as Ive flashed it myself.The SDS problem will be in all i9300 models that have the emmc 0xf1 revision chip.You can check it with this app.Doesnt matter if it says you are safe or not as it wrongly checks for the error.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Flash an official firmware and then a custom kernel with the SDS patch fix.Im using yank555
Click to expand...
Click to collapse
Thanks for that Cooza; one thing there I didn't know; you can flash a 3rd party kernel to a stock firmware.
cooza said:
If you want to flash the ELLA firmware then flash it but if you need to get bacck to an older bootloader to reset you counter with Triangle Away then flash the CWM Zip below in recovery.Its an oldr bootloader thats CWM flashable.Perfectly safe as Ive flashed it myself.The SDS problem will be in all i9300 models that have the emmc 0xf1 revision chip.You can check it with this app.Doesnt matter if it says you are safe or not as it wrongly checks for the error.
https://play.google.com/store/apps/...sIm5ldC52aW5hZ3JlLmFuZHJvaWQuZW1tY19jaGVjayJd
Flash an official firmware and then a custom kernel with the SDS patch fix.Im using yank555
Click to expand...
Click to collapse
Kind sir,you can reset the counter on the new bootloader as long as you are running stock kernel and stock recovery! last night i flashed trough modile odin the stock kernel and the stock recovery over philz recovery ,and after i used triangle away without any problems!
bottom line short,with the new bootloader you cannot reset the counter while you are runing custom kernel and/or custom recovery!