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!
Related
Hey all,
I just received my i777 and I'm impressed. Coming from a sgs4g seems like a huge improvement, though the devices look physically the same LOL (with the i777 being a bit on the larger side).
Anyways, I've been flashing roms for about a year now with my sgs4g. The forums for the sgs4g had very detailed instructions when flashing, instructions like, what to do if coming from stock, but on this forum ppl just assume you have CWM installed.
What I want is a safe way to upgrade to, let's say, phone bricker. I've noticed that all roms are installed through CWM, and all OP say is "make sure CWM is installed", but there's no mention whatsoever on how to install CWM on this phone.
Maybe i'm complicating things a little bit. On my previous phone, Rom Manager downloaded from market was a NO NO because it'd brick it. So we had to flash a modded CWM via odin made specifically for our phones. Maybe for this phone installing rom manager is all that is needed? yes? OK, found the FAQ. no ROM manager.
Also, somehow this phone came rooted... I bought it new from a store but the unlocked version since I live outside USA.
So, if I'm not mistaken, I should just install rom manager, select my phone from the list, flash CWM recovery and flash away roms on the dev section. Am I correct? I don't want to brick my phone
I would not use Rom manger it's proven to be more of a headache for this device. Look on the dev section there are a couple of packages that you can use to get cwm. If your already rooted you could simply flash a custom kernel like entropys daily driver which already has cwm included in kernel.
Again, if your rooted, easiest way could be to simply use mobile Odin to flash custom kernel(I'm assuming your running gingerbread).
I bought the full version of mobile ODIN. makes life a little simpler when flashing, in my opinion. It's worth the few bucks.
eep2378 said:
I would not use Rom manger it's proven to be more of a headache for this device. Look on the dev section there are a couple of packages that you can use to get cwm. If your already rooted you could simply flash a custom kernel like entropys daily driver which already has cwm included in kernel.
Again, if your rooted, easiest way could be to simply use mobile Odin to flash custom kernel(I'm assuming your running gingerbread).
Click to expand...
Click to collapse
Running GB, yes. It's (i think) completely stock: GB KJ4.
I've checked and I have standard recovery, so I'm looking for the best and safest way to get cmw.
Mobile odin looks like a good option, but would I need the full paid version?
mikeflash said:
Running GB, yes. It's (i think) completely stock: GB KJ4.
I've checked and I have standard recovery, so I'm looking for the best and safest way to get cmw.
Mobile odin looks like a good option, but would I need the full paid version?
Click to expand...
Click to collapse
You don't need pro version, lite version will do just fine. Are you sure you're rooted? You have superuser app? Whether you're rooted or not look here(if you are rooted look at #3 : http://forum.xda-developers.com/showthread.php?t=1311081
Check out this thread, was my experience and I'm running PhoneBricker just fine!
However, backup your apps before flashing and factory reset, wipe cache and dalvik after (possibly before as well) and you should be fine! Will root then you can flash away.
Clay
Sent from my SGH-I777 using XDA
One other point for you. Your phone was flashed, in most probability by the folks who sold it to you, with a leaked version of Gingerbread, UCKJ4. As a result, your flash count is probably at 1, and the secondary bootloader was probably replaced with one that disables the ability to clear the flash counter with a usb jig. If this matters to you, you can test first with a jig to see if it will reset, and if not, you can flash the original UCKH7 secondary bootloader to fix it. Needed files can be found in the Download Repository.
Oh, and my guide explains how to flash a modified kernel containing ClockworkMod Recovery if you need it.
Well, I flashed my phone last night. Used mobile odin for flashing a kernel (siyah) to get CWM, then flashed phone bricker via CWM like I used to do on my old phone. Everything went smooth.
Though I'm not fond on this "4.0.3", it's just a launcher that looks like ICS but I don't want to believe it's a true ICS ROM, because it feels weird, I certainly prefer stock GB (or a custom GB rom) instead of some heavily modded rom with ICS theme.
creepyncrawly said:
One other point for you. Your phone was flashed, in most probability by the folks who sold it to you, with a leaked version of Gingerbread, UCKJ4. As a result, your flash count is probably at 1, and the secondary bootloader was probably replaced with one that disables the ability to clear the flash counter with a usb jig. If this matters to you, you can test first with a jig to see if it will reset, and if not, you can flash the original UCKH7 secondary bootloader to fix it. Needed files can be found in the Download Repository.
Oh, and my guide explains how to flash a modified kernel containing ClockworkMod Recovery if you need it.
Click to expand...
Click to collapse
There're several new terms I need to learn about this phone that weren't used on sgs4g. Such as DPI (i.e lowering it, what for? isn't that a step back?) and flash counter.
I suppose flash count is just a counter for how many times you have flashed the phone with custom Roms, so that warranty people can check if a returned phone was damaged due to bad flash, or something like that. Am I correct?
If that's the case, then I'm not too worried about flash count because I live outside US, and my AT&T phone wouldn't get warranty over here, but I'll definitely look into that, to check where my counter is at and to check if resetting it back to 0 is still possible.
I'll be checking up on the links you provided.
Thanks a lot.
mikeflash said:
Though I'm not fond on this "4.0.3", it's just a launcher that looks like ICS but I don't want to believe it's a true ICS ROM, because it feels weird, I certainly prefer stock GB (or a custom GB rom) instead of some heavily modded rom with ICS theme.
Click to expand...
Click to collapse
It is a true ICS rom. Samsung didn't do a lot of cosmetic changes when they moved the S2 to ICS though...most changes are under the hood.
If you want something that looks and feels more like true ICS, you should consider trying either CM9 or AOKP. They are both based on Google's source code, nothing Touchwiz about them.
Or if you'd rather stick with what you have, you can always try different launchers. I'm running ICS, but I use Go Launcher and it runs beautifully.
mikeflash said:
There're several new terms I need to learn about this phone that weren't used on sgs4g. Such as DPI (i.e lowering it, what for? isn't that a step back?) and flash counter.
I suppose flash count is just a counter for how many times you have flashed the phone with custom Roms, so that warranty people can check if a returned phone was damaged due to bad flash, or something like that. Am I correct?
Click to expand...
Click to collapse
That is mostly correct. You're right about the purpose of the flash counter, but it actually counts how many times you flash kernels, not roms. And even then, it only increments if you flash a kernel via Odin in download mode. Flashing a kernel in Mobile Odin or CWM doesn't touch the counter.
Incrementing the flash counter also places that possibly annoying yellow triangle on bootup on your phone. Since you're on ICS, you can just use triangle away app from play store (free version is on here somewhere) to get rid of it, though I'm not sure if that'll fix the whole secondary bootloaders thing (probably not). I think it'd be worth it to fix that just so you don't run into anymore problems later if you decide to change something, especially since after the fixes you can just nandroid back to your current setup, but it's not essential and completely up to you.
Sent from my Samsung SGH-I777 using XDA
I'm confused why this thread was started. There ARE detailed instructions in the stickies and by using Google search along with the words XDA after the search u would easily find any and all information needed. Why do we need a thread dedicated to helping one person read stickies which already have this information.
Sent from my SGH-I777 using Tapatalk 2
Phalanx, did you not read the Title?
It says be nice!
crawls back into hole
Sent from my SGH-I777 using XDA
Phalanx7621 said:
I'm confused why this thread was started. There ARE detailed instructions in the stickies and by using Google search along with the words XDA after the search u would easily find any and all information needed. Why do we need a thread dedicated to helping one person read stickies which already have this information.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Thank you friend.
To sum up for OP
1. Strongly suggest NOT to use ROM Manager on any custom ROMs unless you are surely running CyanogenMod ROM.
2. Check the "About phone" to see if it is true ICS or ICS-theme GB.
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.
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.
Current setup - stock - 4.0.4 - I have not made any modifications to this phone so far other than upgrading it from GB OTA. It is the standard unlocked SIM free UK/Irelend edition.
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100XEULPA
I am interested in trying the stock leaked version of 4.1.2 - actually I'm fed up with waiting for the official release which always seems to be "coming in the very near future" but never arrives.
I have read around extensively on this site and others about how to do this, but still have some questions that I would be grateful if someone could answer.
1. Brick bug - I have run eMMC check and it reports that it reports: NO. Sane chip. Does this mean that I have nothing to fear regarding factory resets/data wiping on 4.0.4?
2. Some mention that USB debugging should be checked - others make not mention of it at all. Should USB debugging be checked in this case when going up to 4.1.2 or back down to 4.0.4?
3. Should the SIM card be removed before flashing with odin or is it alright to leave it in?
4. When the phone reboots after flashing 4.1.2 with odin, some tutorials do nothing and let the phone reboot - others suggest removing the battery as it begins to reboot and then booting into stock recovery mode and doing a factory reset, wipe cache. Some even say also wipe dalvik cache. Is this battery removal step necessary? Or should the phone be left to attempt to boot and if the process hangs enter recovery and reset/wipe cache?
5. I have read in a couple of cases that the SIM lock has been activated after this flashing procedure on a previously unlocked phone. I have found an unlock apk on this forum that can resolve this issue. But why does it happen? How common is this problem?
6. In my 4.1.2 download from Sammobile there are 2 files that are not mentioned in the articles I have read. emmc_EXT4_16GB.pit and emmc_EXT4_32GB.pit - what are these for? Are they needed for this procedure?
7. How long should the reboot process take after the flashing is complete? - or after how long should I start to get worried if it seems to be stuck?
8. If I wish to return to stock 4.0.4 (here the brick bug is the problem yes?)- is the procedure the same as flashing 4.1.2? And if I do go back to 4.0.4 stock will the phone work with KIES again?
9. I have odin 3.07 - is this version appropriate for this procedure?
dimbo33 said:
Current setup - stock - 4.0.4 - I have not made any modifications to this phone so far other than upgrading it from GB OTA. It is the standard unlocked SIM free UK/Irelend edition.
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100XEULPA
I am interested in trying the stock leaked version of 4.1.2 - actually I'm fed up with waiting for the official release which always seems to be "coming in the very near future" but never arrives.
I have read around extensively on this site and others about how to do this, but still have some questions that I would be grateful if someone could answer.
1. Brick bug - I have run eMMC check and it reports that it reports: NO. Sane chip. Does this mean that I have nothing to fear regarding factory resets/data wiping on 4.0.4?
Yes. If you have the sane/safe chip no need to worry.
2. Some mention that USB debugging should be checked - others make not mention of it at all. Should USB debugging be checked in this case when going up to 4.1.2 or back down to 4.0.4?
Doesn't matter whether it is on or off. It's just for debugging. I usually keep it on since you don't know when it might be useful. There is no harm in keeping it ticked.
3. Should the SIM card be removed before flashing with odin or is it alright to leave it in?
No need to remove sim card.
4. When the phone reboots after flashing 4.1.2 with odin, some tutorials do nothing and let the phone reboot - others suggest removing the battery as it begins to reboot and then booting into stock recovery mode and doing a factory reset, wipe cache. Some even say also wipe dalvik cache. Is this battery removal step necessary? Or should the phone be left to attempt to boot and if the process hangs enter recovery and reset/wipe cache?
After flashing, your phone will restart. If it doesn't go past the samsung logo, you'll need to pull out the battery, reinsert it, boot into recovery and perform a factory reset. Wiping cache and dalvik isn't necessary. However, if you do boot into recovery (which most certainly you'll have to, to do the data wipe), it takes less than 15 seconds to wipe the cache and dalvik.
5. I have read in a couple of cases that the SIM lock has been activated after this flashing procedure on a previously unlocked phone. I have found an unlock apk on this forum that can resolve this issue. But why does it happen? How common is this problem?
I believe it's designed to be that way. However, I am not sure about this one. Sorry.
6. In my 4.1.2 download from Sammobile there are 2 files that are not mentioned in the articles I have read. emmc_EXT4_16GB.pit and emmc_EXT4_32GB.pit - what are these for? Are they needed for this procedure?
No need for the .pit files. Better avoid them at all costs.
7. How long should the reboot process take after the flashing is complete? - or after how long should I start to get worried if it seems to be stuck?
Don't worry. You'll know when to worry ... Taking upto 5 minutes is perhaps normal. After that, update here if you think there is a problem.
8. If I wish to return to stock 4.0.4 (here the brick bug is the problem yes?)- is the procedure the same as flashing 4.1.2? And if I do go back to 4.0.4 stock will the phone work with KIES again?
Yes, and yes.
9. I have odin 3.07 - is this version appropriate for this procedure?
Better use v1.83 or v1.85. I've read a complaint against the latest one. Old is gold in some cases
Click to expand...
Click to collapse
I've replied under every question. Didn't want to quote the whole thing then write my answers, or scroll up and down continuously. Good luck and don't worry
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
I've replied under every question. Didn't want to quote the whole thing then write my answers, or scroll up and down continuously. Good luck and don't worry
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your answers. I appreciate it. I've done this kind of thing loads of times on other types of device, but I'm always nervous as hell when it's the first time and don't want any holes in my understanding of the process.
dimbo33 said:
Current setup - stock - 4.0.4 - I have not made any modifications to this phone so far other than upgrading it from GB OTA. It is the standard unlocked SIM free UK/Irelend edition.
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100XEULPA
I am interested in trying the stock leaked version of 4.1.2 - actually I'm fed up with waiting for the official release which always seems to be "coming in the very near future" but never arrives.
I have read around extensively on this site and others about how to do this, but still have some questions that I would be grateful if someone could answer.
1. Brick bug - I have run eMMC check and it reports that it reports: NO. Sane chip. Does this mean that I have nothing to fear regarding factory resets/data wiping on 4.0.4?
2. Some mention that USB debugging should be checked - others make not mention of it at all. Should USB debugging be checked in this case when going up to 4.1.2 or back down to 4.0.4?
3. Should the SIM card be removed before flashing with odin or is it alright to leave it in?
4. When the phone reboots after flashing 4.1.2 with odin, some tutorials do nothing and let the phone reboot - others suggest removing the battery as it begins to reboot and then booting into stock recovery mode and doing a factory reset, wipe cache. Some even say also wipe dalvik cache. Is this battery removal step necessary? Or should the phone be left to attempt to boot and if the process hangs enter recovery and reset/wipe cache?
5. I have read in a couple of cases that the SIM lock has been activated after this flashing procedure on a previously unlocked phone. I have found an unlock apk on this forum that can resolve this issue. But why does it happen? How common is this problem?
6. In my 4.1.2 download from Sammobile there are 2 files that are not mentioned in the articles I have read. emmc_EXT4_16GB.pit and emmc_EXT4_32GB.pit - what are these for? Are they needed for this procedure?
7. How long should the reboot process take after the flashing is complete? - or after how long should I start to get worried if it seems to be stuck?
8. If I wish to return to stock 4.0.4 (here the brick bug is the problem yes?)- is the procedure the same as flashing 4.1.2? And if I do go back to 4.0.4 stock will the phone work with KIES again?
9. I have odin 3.07 - is this version appropriate for this procedure?
Click to expand...
Click to collapse
Firstly,
Idk exactly about USB debugging but what i do know is that...
"USB Debugging is intended for development purposes only. It can be used to copy data between your computer and your device, install applications on your device without notification, and read log data." A few apps use it, like the aforementioned PdaNet app. USB Debugging can also be used with ADB when issuing commands from a command line on your computer to your Android handset or tablet. One-Click root apps often require USB Debugging to be enabled to deliver the exploit that roots your device.
SIM card wouldn't affect anything, so it doesn't matter if you leave it in the phone..
After Flashing the JB, first check whether the phone goes into boot loop or anything like that....if you experience any problems then do the factory reset, wipe cache...though its usually recommended to factory reset anyways..
I don't think we need to flash the "emmc_EXT4_16GB.pit" or the other pit file..
The reboot process shouldn't take more than 5-10 minutes max..
Well i have gone from custom ROM 4.1.2 XXLSJ back to the stock 4.0.4 using the usual flashing steps of ODIN....I didn't experience any problems..
If its anything above Odin3v1.85 it shouldn't be a problem...
Press thanx if i helped..
Is there any need to do any factory reset/cache wiping from recovery before flashing 4.1.2?
I guess that when I flashed jb leak I had all those questions, and maybe a couple of more.
Then I read about Mobile Odin, flashed & rooted my device in half a smoke (3 mins). All I had to do was select the 3 tar files.
The flash did network lock my device. Galaxysim Unlock solved it for me.
good luck and happy flashing.
dimbo33 said:
Is there any need to do any factory reset/cache wiping from recovery before flashing 4.1.2?
Click to expand...
Click to collapse
Only once. Either before flashing the ROM, or after. Order doesn't matter.
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
Only once. Either before flashing the ROM, or after. Order doesn't matter.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
I would imagine then it's better to do it whilst on 4.0.4 prior to flashing (since I have the sane chip) so that you don't get the possible failed boot after flashing 4.1.2 with odin.
So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
dimbo33 said:
I would imagine then it's better to do it prior to flashing so that you don't get the possible failed boot after flashing 4.1.2 with odin.
So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
Click to expand...
Click to collapse
No, I don't think so. Come to think of it, I've never tried that A battery pull works though
Sent from my GT-I9100 using Tapatalk 2
Spiralzz said:
No, I don't think so. Come to think of it, I've never tried that A battery pull works though
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Do you mean it's not better to factory reset before flashing or the long press doesn't turn off the phone from recovery (in which case best to pull the battery out)?
dimbo33 said:
I would imagine then it's better to do it whilst on 4.0.4 prior to flashing (since I have the sane chip) so that you don't get the possible failed boot after flashing 4.1.2 with odin.
So after doing the wipes in recovery prior to flashing, is the phone turned off by a long press of the power button?
Click to expand...
Click to collapse
Well since your flashing 4.0.4 its pretty much a must to also install custom kernel to avoid possible silly bricks by wiping data.
So simply flash rom via odin and then do same for custom kernel like Siyah and then reboot into kernel and wipe data/factory reset and you're off
TheATHEiST said:
Well since your flashing 4.0.4 its pretty much a must to also install custom kernel to avoid possible silly bricks by wiping data.
So simply flash rom via odin and then do same for custom kernel like Siyah and then reboot into kernel and wipe data/factory reset and you're off
Click to expand...
Click to collapse
Sane chip, he's already off.
gastonw said:
Sane chip, he's already off.
Click to expand...
Click to collapse
Yeah didnt notice OP was on sane chip. Was speaking more in general though anyway.
TheATHEiST said:
Yeah didnt notice OP was on sane chip. Was speaking more in general though anyway.
Click to expand...
Click to collapse
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head.
gastonw said:
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head.
Click to expand...
Click to collapse
:laugh:
gastonw said:
Sometimes I dream my phone is bricked or scracthed. This Q&A thing might be messing with my head.
Click to expand...
Click to collapse
I know what you mean. I haven't even done this procedure yet and I'm dreaming of bricked phones/ corrupted IMEIs etc.
Probably a bit melodramatic I know.
It did occur to me that instead of flashing stock 4.1.2 from stock 4.0.4, it may be better to flash the Siyah kernel to my current 4.0.4. This way I can back up efs, do a nandroid and titanium - before embarking on fully fledged ROM flashing etc.
What do you think?
dimbo33 said:
I know what you mean. I haven't even done this procedure yet and I'm dreaming of bricked phones/ corrupted IMEIs etc.
Probably a bit melodramatic I know.
It did occur to me that instead of flashing stock 4.1.2 from stock 4.0.4, it may be better to flash the Siyah kernel to my current 4.0.4. This way I can back up efs, do a nandroid and titanium - before embarking on fully fledged ROM flashing etc.
What do you think?
Click to expand...
Click to collapse
Well...the beauty of flashing is that you can do both Stock & Custom. You can also Dual Boot if you want.
My advice is this:
1) Always Back up EFS folder (HC-ktool is a good app for that).
2) Get Titanium Back up Pro.
3) Flash CMW or Flash siyah, it can't never hurt (well, if you go JB leak, might wanna try usin stock kernel first and the flash a custom kernel)
4) Get mobile odin Pro (so you can flash as many stock ROMs as you like, with the chance of getting bricked or soft bricked close to none + you'll always be rooted)
5) Read about ROMs features. You are the only person in the world that knows what ROM will fit your needs.
6) Start flashing.
7) If you are scared about bricks, read the bricked device's threads. That way you will know what NOT to do.
In my experience, I went jb and never came back.
Now, you really dream about IMEI, lol, that's something
I haven't flashed 4.1.2 yet. I was going to do it last night but realised I had forgotten my GPS active and the battery went flat. I took this as an omen and aborted the mission.
I've been reading around the subject for days. There seem to be so many people that encounter problems that it is difficult to have any perspective. The myriad of users that flash stuff via odin without any trouble obviously don't post that it went well - so you read 10 problem posts and never see the other thousand flashes that went without a hitch.
I also have read on xda that the leaked JB 4.1.2 is somewhat buggy. I'm not sure how buggy, but the lock screen freeze would be annoying in practice.
Again the carrot of official jb has been dangled before us - supposedly in February now.......Given that this will probably be the last official release for the S2 I might hang on and wait for it - then embark on the routing/custom ROM journey.
dimbo33 said:
I haven't flashed 4.1.2 yet. I was going to do it last night but realised I had forgotten my GPS active and the battery went flat. I took this as an omen and aborted the mission.
I've been reading around the subject for days. There seem to be so many people that encounter problems that it is difficult to have any perspective. The myriad of users that flash stuff via odin without any trouble obviously don't post that it went well - so you read 10 problem posts and never see the other thousand flashes that went without a hitch.
I also have read on xda that the leaked JB 4.1.2 is somewhat buggy. I'm not sure how buggy, but the lock screen freeze would be annoying in practice.
Again the carrot of official jb has been dangled before us - supposedly in February now.......Given that this will probably be the last official release for the S2 I might hang on and wait for it - then embark on the routing/custom ROM journey.
Click to expand...
Click to collapse
Well, you read 10 problems while flashing, right now we got 50.000 users going thru these threads, here, at XDA.
Jb is buggy, it's a leak, but too buggy? don't think so.
As for the bugs, we got plenty of people coming up with work arounds & fixes every day. In my case, I only have the lockscreen issue (let's face it, it doesn't always happens, like maybe 1 time a day and it's only for 3 seconds till the capacitive buttons light up. If you lock the screen and re unlock it with the power button, you're off. For me, it's not even an issue). I don't even remember when was the last time I had this issue, maybe 3 days ago now that I think about it.
Where's flashing, there's risk. TRUE. That's why I layed the Mobile Odin Pro option for you, that could be the best way to lose you flashing's fright.
BTW: we are getting the lime pie update, SII Plus was released just now
gastonw said:
Where's flashing, there's risk. TRUE. That's why I layed the Mobile Odin Pro option for you, that could be the best way to lose you flashing's fright.
Click to expand...
Click to collapse
I have had a look at mobile Odin Pro and I like the look of it. Thanks for the tip. To use it I need to root the S2.
I have seen this guide http://forum.xda-developers.com/showthread.php?t=1501719 - this seems simple. I could also flash the Siyah kernel via Odin. Which root method would you recommend? The first method seems to avoid the triangle issue - although this is not a big deal.
With a routed device I can backup efs etc before flashing anything else. Does the efs folder contain the simlock status?
Also, as you know I have been looking at the leaked jb, but perhaps it might be worth looking at neatrom 4.1.2 (or similar) instead?
I seem to get the impression that mobile Odin Pro is a safe method. Is it safer than using PC Odin?
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
muffintastic said:
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
Click to expand...
Click to collapse
To avoid brickbug is by flashing JB 4.1.2. (good alternative!)
But if you really like ICS then i suggest you move back to 4.0.3. There is no avoiding brickbug on 4.0.4.
If you have rooted it, you can check with 'Brickbug check' app on google play, to see if you have sane (or insane) chip (brickbug or not), cause most custom kernels and roms have found a solution to this bug, and use it on their roms/kernels. Which means on those you can safely wipe and restore etc.. (but check brickbug app first on google play)
Yep. Don't wipe a rooted phone running 4.0.4. And if you're really paranoid, don't even wipe a non-rooted phone running 4.0.4 (Entropy mentioned at least one case he knew of where someone borked their phone doing a wipe on a phone running 4.0.4 via stock Android recovery, tho it seems to be very rare).
The TL;DR is don't run rooted stock 4.0.4 if you mess with your phone in any way.
I know that's not a fix, but that's because there isn't one. Some chips aren't susceptible to the bug; there's an app floating around here somewhere/Google Play where you can check which chip you have (seems to be more that are susceptible).
Your 1st paragraph is a load of crap.Bootloop has nothing to do with "brickbug".More like by you not running kernel cleaning script,or not factory resetting before/after flashing a new rom.
As mentioned by others,just dont have 4.0.4 running on your phone.So you are still left with over 100 custom/stock roms to choose from........lol
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Hopper8 said:
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Im not sure Hopper.I am leaning towards the restore would be "cancelled" due to not being complete,rather than it succeeding leading to bootloop.
But hes not said.
And he cant get "factory" rom with a restore as it didnt come with cwm lol.
Sorry to clear things up.. I updated it to 4.1.2 via Kies many months ago. I used PhilZ method to root, no problem. Few months down the line since then I put LiquidSmooth 2.4 (few days ago) then restored a backup from PhilZ recovery and put 4.1.2 and everything back on no problem. Then restarted the phone and it when into a boot loop of the Orange and Samsung logo.
I'm not stupid as I've rooted my own SGS3 and Samsung Galaxy ACEs etc, Just forgotten to put that info in lol and yes I always use the Factory Reset to install a new rom.
And yes when I managed to get it restored from this so called boot loop (by putting 4.1.2 Orange UK firmeware back on via Odin) the EMMC brick bug is present as i've checked via an app via Google Play. My overall goal is to eliminate this problem or temp fix so I can put different roms on and if I don't like them recovery back to the latest restore without issues.
Are we on the same line now ?
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
help me out here please
MistahBungle said:
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
Click to expand...
Click to collapse
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
andreshbozo said:
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
Click to expand...
Click to collapse
Here is my situation.
I had 4.1.2 JB. Installed CM11 M8 and CWM_6.0.4.7(coming previously from Siyah) at the end of July. In the beginning of October my phone just shut down. That happened before on the same and previous rom so I wasn't worried. I turned it on and phone was in bootloop. That was strange because the last time that happened I installed Chainfire. So bootloop without any cause..that was strange. I tried making a backup before flashing the ROM. But I got an error. I can't remember but I can dig it somewhere if you want it. I tried then flashing recovery(bad idea) and Odin again reported an error. When I restarted phone I noticed that my Recovery mode was gone. Just gone and with no solution on how to restore it. I tried numerous methods OMAP drivers, heimdall, .pit file method but nothing. So I brought my sgs2 to the store where I bought it and they concluded that it was bad eMMC chip.
Now, your problem reminds me of mine because Odin wouldn't want to flash anything without an error(well, not exactly anything, I managed to flash some partition using Heimdall but it was not sufficient) but it doesn't have to be.
What version of cwm were you using?