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.
Related
If anyone has the time i would like some help on how to flash my Note without bricking the phone. Reason i ask, is because i have already bricked it!! Sent it off to mobiletechvideos.com who unbricked it so now i'm back! I love the phone alot just hate stock rom and how slow it is. I would like to use a rom that is able to overclock? I've read about the sauron rom but i can't tell if it's out dated or if there is something better now?
I'm not a noob when it comes to rom's, Htc aria, samsung captivate, inspire, then the htc one x - i've all rom'd them but now i'm stump'd. The first go around, i flashed the rom and everything went thru fine. When i booted up the phone - Nothing changed!? so i find another rom, flashed it and the phone bricked. Tried jig everything else and to no avail. So 65$ later i'm back with the stock rom and it's rooted. Anyhow, here is the info i'm sure you guys are wanting to give me a hand!
Model Number
SAMSUNG-SGH-I717
Andriod Version
2.3.6
Baseband Version
I717UCLF6
Kernel Version
2.6.35.11
Build Number
GINGERBREAD.UCLA1
Cliff Notes -- Hard bricked trying to flash rom, Main goal want to overclock, battery life not issue. Please help flashing :angel:
do you have a custom recovery ? like cwm or the other one ( ive only had my note a week)
i would start with that..
If I were you (and I fully understand that I am not nor anyone else on here...) I would:
1. Install Samsung Kies and drivers to my laptop.
2. Start Samsung Kies and plug in the phone via USB cable.
3. Update the phone's OS via Kies to ICS. You won't brick it that way.
4. Give stock ICS a chance and if you still feel it's too slow for you (rolling eyes), flash a custom ROM/kernel.
nutpants said:
do you have a custom recovery ? like cwm or the other one ( ive only had my note a week)
i would start with that..
Click to expand...
Click to collapse
Yep, already have clockwork mod, That's no big deal.
BlackZenith said:
If I were you (and I fully understand that I am not nor anyone else on here...) I would:
1. Install Samsung Kies and drivers to my laptop.
2. Start Samsung Kies and plug in the phone via USB cable.
3. Update the phone's OS via Kies to ICS. You won't brick it that way.
4. Give stock ICS a chance and if you still feel it's too slow for you (rolling eyes), flash a custom ROM/kernel.
Click to expand...
Click to collapse
Sounds good sir i will give it a try - Meanwhile Anyone want to take a stab at walking me thru a rom that would work on my phone?
not that i have any idea what i am doing...
0 MAKE VERY SURE THE ROM YOU ARE FLASHING IS FOR YOUR PHONE... FORGET THE WORDS "note" or "galaxy" or anything else..
its the i717d or i 7100 or i 7000 that matters.. if in doubt dont do it..
1 download your cwm compatible rom (like blackstar or others) ( try to pick a recent rom no older than 2 months unless all the developers have jumped ship for the new phone)
( usually ends with a .zip) to your sd card)
2 use "android file verifier " ( from the market) to make sure your md5 hash of the download is prefect
( there SHOULD be a md5 someplace to verify the file download)
then by following info like whats found here.... http://forum.xda-developers.com/showthread.php?t=1584250 ( and that i copied and pasted)
boot into recovery by pressing volume up down,and power button at same time ( when your phone is turned off)
Select wipe data/factory reset and confirm
Select wipe cache partition and confirm
Select advanced - wipe dalvik cache and confirm
Select install zip from SD card
Select from internal SD card or wherever you placed it.
Select the ROM file and confirm.
rom will install
then AGAIN
Select wipe data/factory reset and confirm
Select wipe cache partition and confirm
Select advanced - wipe dalvik cache and confirm
boot up wait 5mins for it to boot.. dont touch it for 10 minutes after it boots
then
have fun..
dont forget to wonder if you bricked it during the first boot... that one takes the longest..
i have followed these directions drunk and sober when flashing over 20 times my new note i717d i got last week and im not bricked yet.
its the same system i used with my sgs2 i9100 for over a year and it still works..
but then dont think anything i have said here is right.
i could just be stupid and very lucky that i dont brick everything i touch but will not admit it.
READ A LOT, then READ more.. then ONE MORE TIME READ.. then flash.
BlackZenith said:
If I were you (and I fully understand that I am not nor anyone else on here...) I would:
1. Install Samsung Kies and drivers to my laptop.
2. Start Samsung Kies and plug in the phone via USB cable.
3. Update the phone's OS via Kies to ICS. You won't brick it that way.
4. Give stock ICS a chance and if you still feel it's too slow for you (rolling eyes), flash a custom ROM/kernel.
Click to expand...
Click to collapse
So after about 2 hours off and on, using different cables and google. No avail, UGH!
Samsung kies
Your device is not supported to update via samsung kies. Walked thru a few xda threads and they are saying update thru odin. Hell if i'm jumping ship to odin again, mine as well do a rom. I'm giving this 1 more shot, if it bricks i'll sell it lol!!
Mobiletechvideos most have had to do something extreme to repair your device, or they gave you one that.... never mind. Well, looks like you need to flash CWM and find a zip aligned ROM on here.
BlackZenith said:
Mobiletechvideos most have had to do something extreme to repair your device, or they gave you one that.... never mind. Well, looks like you need to flash CWM and find a zip aligned ROM on here.
Click to expand...
Click to collapse
LOL, no they did exactly what was promised. Even people who haven't bricked their device have ran into this issue!
Okay - After reading up and then watching a video on how to flash roms. Which looked exactly like what i had done before time and time again. I'm proud to say i'm ROM'D! I'm now running the blackstar rom and it's very zippy love it to death. Would like to have tried ICS 4.0.4 but took the plunge and happy with the turn out.
I've always came to this site for help but never made an account and you guys are too nice! Hopefully i can/could help someone else out down the road. Until then i'm going to enjoy not being so slow! Thanks!:good:
Its because you have a LF6 modem. Its not the modem that GB had. The Kies upgrade only works if your phone is stock.
You can use the kies emergancy firmware upgrade option.
Is not black star 4.04?
nutpants said:
Is not black star 4.04?
Click to expand...
Click to collapse
1st post says GB.
rangercaptain said:
1st post says GB.
Click to expand...
Click to collapse
First post here or first post of black star ?
written in your mud with my stick
Your first post.
The latest black star is based on the ics 4.0.4 firmware from Singapore
studacris said:
Your first post.
The latest black star is based on the ics 4.0.4 firmware from Singapore
Click to expand...
Click to collapse
The original Tom I started with was 2.3.6 since lies wouldn't let me update to ice 4.0.4 I jumped the gun and flashed blackstar. While it is a great rom. I'm thinking of trying more while I got my feet wet.
1Note said:
The original Tom I started with was 2.3.6 since lies wouldn't let me update to ice 4.0.4 I jumped the gun and flashed blackstar. While it is a great rom. I'm thinking of trying more while I got my feet wet.
Click to expand...
Click to collapse
I've been flashing two roms a day looking for something that supports total recall and underclocking, with a network mode menu that has lte on it.
I think I am out of luck.and I have forgotten some roms so I may flash everything again and keep notes...
It's research not an addiction.
written in your mud with my stick
Stage 1 of acceptance is denial
studacris said:
Stage 1 of acceptance is denial
Click to expand...
Click to collapse
LOL ...
And of course my favorite ....
"Trying is the first step toward failure ".....(Homer Simpson )...(grin )
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?
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
ikradex said:
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
Click to expand...
Click to collapse
Seriously dude? Use some common sense please and give relevant information on what you have. What model/variant do you have, rom are you on, what kernel have you flashed?
How do you expect anybody to be able to help you if you dont give such basic info???
Are you sure the kernel supports the rom/version you have installed?
ikradex said:
New here. (also apologies for probable duplicate topic)
I've rooted a phone in the past with no problem. This time round was with an S2, and I flashed an insecure kernel on it, got a green pass on Odin however it's now stuck on the boot screen with the yellow triangle.
I can access recovery mode and download mode but it will never boot properly, always stuck on the yellow triangle. What's the best course of action from here?
Need a lot of help with this guys as I'd rather not have a bricked phone ><
Click to expand...
Click to collapse
Maybe because you wiped all data....so...there's no ROM to boot up to.
Try flashing one via Odin
gastonw said:
Maybe because you wiped all data....so...there's no ROM to boot up to.
Try flashing one via Odin
Click to expand...
Click to collapse
Wiping data doesnt wipe rom , It just wipes appdata, ie settings etc. All that happens is a factory reset so when you next boot its back to default. For example you would need to re-enter google account and re-install apss either manually or from a backup.
You can only wipe rom by formatting system partition.
TheATHEiST said:
Wiping data doesnt wipe rom , It just wipes appdata, ie settings etc. All that happens is a factory reset so when you next boot its back to default. For example you would need to re-enter google account and re-install apss either manually or from a backup.
You can only wipe rom by formatting system partition.
Click to expand...
Click to collapse
Thought you had me in ignore.
So there's no way you can wipe your OS via recovery? Good to know that, it's like ROM over ROM then. The new one clears the old one.
gastonw said:
Thought you had me in ignore.
So there's no way you can wipe your OS via recovery? Good to know that, it's like ROM over ROM then. The new one clears the old one.
Click to expand...
Click to collapse
I did have you on ignore but I still see little boxes saying this comment has been ignored etc which was actually more annoying so I removed ignore.
Yes you can wipe OS via recovery but only by formatting system/deleting partition etc. All the "wipe" options do is remove files that have been created by rom like app settings/cache etc.
Your confusion was probably also the reason why you made a big thing in a previous topic about you trying to avoid wiping data, because you thought it wiped rom? :silly:
Wiping data/factory reset in cwm is one of the best ways to get rid of system issues, Its basically like doing a clean install of Windows on a PC. After you have wiped you can simply restore your needed apps from a backup using Titanium Backup. Other things like sms/mms etc can be also backed up easily and contacts will be synced via Google account.
TheATHEiST said:
I did have you on ignore but I still see little boxes saying this comment has been ignored etc which was actually more annoying so I removed ignore.
Yes you can wipe OS via recovery but only by formatting system/deleting partition etc. All the "wipe" options do is remove files that have been created by rom like app settings/cache etc.
Your confusion was probably also the reason why you made a big thing in a previous topic about you trying to avoid wiping data, because you thought it wiped rom? :silly:
Wiping data/factory reset in cwm is one of the best ways to get rid of system issues, Its basically like doing a clean install of Windows on a PC. After you have wiped you can simply restore your needed apps from a backup using Titanium Backup. Other things like sms/mms etc can be also backed up easily and contacts will be synced via Google account.
Click to expand...
Click to collapse
hum...okay.
I actually know what Factory Reset does, I mean..."factory"..."reset", kinda......gives it away.
And yes, it made sense to me that you could wipe the ROM you are on before installing a new one, just like the format c:/s days in win98.
You learn something every day, speaking of which, how come no one recommends noobs to root their device with exynos abuse? It's because they're noobs and wouldn't be able to handle/understand the exploit?
I still don't do factory resets because I don't need to, and I avoid needing to perform it.
TheATHEiST said:
Seriously dude? Use some common sense please and give relevant information on what you have. What model/variant do you have, rom are you on, what kernel have you flashed?
How do you expect anybody to be able to help you if you dont give such basic info???
Are you sure the kernel supports the rom/version you have installed?
Click to expand...
Click to collapse
Thanks for the reply Figured if someone was willing to help me I'd give them the information they wanted.
Have Samsung Galaxy S II (GT-I9100) (couldn't tell you what "variant" it is). I was following this guide. It told me to get an insecure kernel from here. The guide said it didn't really matter which kernel I picked so I picked the first one (GT-I9100_BGKF5_insecure) and used Odin to flash it. Got a green pass and the phone began reboot but it's now stuck on the yellow triangle (the warning message that you've flashed an insecure kernel).
I couldn't tell whether there would be compatibility issues as the thread just seems to be one big list of kernels and nothing else. AFAIK the phone was running ICS.
Looking at the replies, I keep seeing factory reset. Is that a liable option to restore my phone back to its original state. I don't care as long the phone works again. If not can someone run through how to fix my predicament I heard if I can access download and recovery mode I should be able to fix it.
ikradex said:
Thanks for the reply Figured if someone was willing to help me I'd give them the information they wanted.
Have Samsung Galaxy S II (GT-I9100) (couldn't tell you what "variant" it is). I was following this guide. It told me to get an insecure kernel from here. The guide said it didn't really matter which kernel I picked so I picked the first one (GT-I9100_BGKF5_insecure) and used Odin to flash it. Got a green pass and the phone began reboot but it's now stuck on the yellow triangle (the warning message that you've flashed an insecure kernel).
I couldn't tell whether there would be compatibility issues as the thread just seems to be one big list of kernels and nothing else. AFAIK the phone was running ICS.
Looking at the replies, I keep seeing factory reset. Is that a liable option to restore my phone back to its original state. I don't care as long the phone works again. If not can someone run through how to fix my predicament I heard if I can access download and recovery mode I should be able to fix it.
Click to expand...
Click to collapse
Of course, you're not bricked yet.
Before trying your back up, why don't you flash a stock ROM via odin and take a long breath?
This is JB leak.
These are ICS, look for 4.0.3 unbranded.
gastonw said:
Of course, you're not bricked yet.
Before trying your back up, why don't you flash a stock ROM via odin and take a long breath?
This is JB leak.
These are ICS, look for 4.0.3 unbranded.
Click to expand...
Click to collapse
I know this is leading onto another thread but my phone now is having trouble connecting to my computer. Keep getting "USB not recognized" error. Installed/Uninstalled kies & drivers then installed drivers again alone and still won't recognize it
Tried another usb port? another pc/laptop? sure kies is not running in background? reinstalled kies?
Don't worry, your pc WILL see your device.
Sent from the little guy
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
pstrulm said:
Wow! I need some help. I've acquired a Samsung Galaxy Note (i717, I believe) that shows all the signs of being healthy (appearance, touch screen, etc.) but persistently slows down at the ATT opening splash screen, begins to load Android, dies and reboots. Whatever variant rooted ROM I received it with (sluggish and unreliable) I have written over and now I can't get any farther than the Android settings screen. Therefore I do not know the exact version nor can I begin to set it up (wifi, etc.).
That's the 'presenting problem', so let me explain what I've done to this point (about 25 hrs. worth!). I have reloaded latest version of CWM (runs great) and then Padawan JB . . . same symptoms. I have loaded the ATT JB and ICS via the latest Odin successfully . . . with same symptoms. I have loaded TWRP (touch screen is snappy and works as it should) and Padawan JB again . . . with same symptoms. I have wiped caches before, after, and in between till I'm blue in the face, each time with the same symptoms. Most recently I have done a hard reset to native/factory settings . . . with no change! I've tried to scour the XDA (and any other sites) trouble shooting articles and seem to have come to a dead end.
Here's a couple things that I'm wondering: because I can't get deep enough into Android to check out the model number, could the phone be something other than an ATT model? At the top of the front face it simply says 'Samsung', not ATT at top and Samsung at bottom like my previous ATT Note. Right after boot I persistently get an ATT splash screen which would lead me to believe that it is ATT. Is there some other way to find model, say in TWRP? Do I need a phone specific version of Android? Second, everything seems to be working fine physically (i.e., no hardware problems). Could this thing have gotten a virus in an earlier life that's preventing the ROM from working right? I've not been able to get far enough to register it with my cell provider (second party, not ATT). Must you be up and running with the cell service to correctly load and use the ROM (wouldn't think so)? And if so, how without Android working? I've been using and playing with computers for 25 years, but I'm fairly new to the Android system (but learning fast!) Any help would sure be appreciated. I'd really like to resurrect this baby. I loved my first Note (till it fell off the car and disappeared).
Click to expand...
Click to collapse
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory reset in between.
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
androidmechanic said:
fbauto1 said:
Well, if you keep flashing an AT&T based rom, then yes, you will get an AT&T boot animation simply because it's part of the rom you are flashing.
You said "you think" you have an I717, did you take the battery off and physically look at the sticker beneath it to see the model?
Try TWRP, go to WIPE, and WIPE everything, which means checking every checkbox. Then flash a stock rom with a fresh phone (no data, nothing at all)
You said you did CWM->Padawan.. these are two totally different roms, so you should always do a factory reset whenever flashing two totally different roms.
You can't just rely on the Android->settings to see the info since roms overwrite these stuff in build.prop so if you flash a wrong rom, wrong info will show up.
Here's my advice:
1. Flash TWRP
2. Wipe in TWRP, check every checkbox
3. Flash a stock i717 rom
4. Reboot
If that doesn't work, either hardware is bad or your phone isn't for the I717 roms.
Edit:
Question, have you ever come to a point that the phone boots successfuly at all? You did mention CM works great. But you can't go from CWM->TW Based rom without factory
I would reflash cwm thru odin after that I would flash the latest TWRP 2.5. Then you can flash whatever. If padawan is givin u problems try something else like AOSP or AOKP. Padawan is TW based. JaimeD builds are pretty sweet.
sent from my GalaxySuperNote running OC Padawan JB
Click to expand...
Click to collapse
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
AT&T Phones have a [logo}AT&T] on the top-center!!
But if you are in doubt, use kies to do a full recovery-restore [WILL ERASE EVERYTHING ON YOUR DEVICE].
See post #4 on this thread.
fbauto1 said:
androidmechanic said:
If you want TWRP, flash TWRP. No need to flash CWM
Click to expand...
Click to collapse
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
androidmechanic said:
If you go thru Odin you would have cwm first. With the problems talked about, I would go back factory stock then re-root with Odin. Then thru cwm, flash twrp or whatever floats your boat.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
fbauto1 said:
Nope. If you want TWRP, then flash TWRP via Odin. No need to go through CWM first. You can flash TWRP via Odin, you know that, right?
Click to expand...
Click to collapse
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
you are both actually correct, however, I am looking at PSTRULM's stats. if he is anything like me when I started, the more simple and less complication involved in the process, the more he may understand.
ANDROIDMECHANIC is stating the most basic and beginner way to do this and understand simply. after doing this a few times as I did, the basic mechanics of the process will become more fluent.
then he can make his own decisions as to methods which might be easier for him, without confusing.
I am sure you both are a huge help to everyone and I thank members such as yourself for your efforts. ME, I prefer baby steps, cause I know I can really EFF things up if I get confused
androidmechanic said:
No I didn't know that. All of the Odin programs that I dealt with flash cwm. Than for the Intel tho. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Just a reminder.. when flashing through Odin, make sure it's an ODIN-flashable tarball, i.e., you can't flash a recovery-type zip through Odin and vice versa.
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?