Due to an error in the kernels we've been flashing to our devices, a lot of users have been experiencing a FULL BRICK. Full brick meaning you may as well play golf with your phone, it's dead.
I've been told there is a fix, BUT YOU MUST NOT FLASH ANYTHING FROM CWM. The bug is originating from flashing a corrupt kernel from CWM or mobile ODIN.
Here's a cut from the article:
Thanks to XDA Elite Recognized Developer Entropy512, we have learned that most devices that are receiving leaks are at a very high risk of never waking up after a flash. It turns out that there is a major bug in the leaked ICS kernel that affects the /data partition in the eMMC chip, which apparently gets corrupted during certain operations such as wiping and flashing. This was originally believed to be affecting only operations performed in custom recoveries such as CWM. However, there have been reports of hard bricks being produced from the flashing from stock recoveries as well. The affected devices are:
All Epic 4G Touch (SPH-D710) ICS leaks
All Galaxy Note (GT-N7000) ICS leaks
The AT&T Galaxy S II (SGH-I777) UCLD3 leak – and probably all others
Korean SHW-M250S/K/L official releases and any kernel built from their source
Entropy and other devs have posted several warnings scattered throughout the site, in which they explain in detail what is happening. Our suggestion is that users should stay away from flashing ICS from leaks until the bug in the kernel has been completely fixed—unless of course, you are looking to hard brick your device. Remember, this is not something that can be resurrected via Unbrickable Mod or even via JTAG, as this is a firmware error in the eMMC.
Click to expand...
Click to collapse
Just like you, I don't wish to brick my E4GT. xST4T1K has posted a comprehensive guide to find your options on removing the affected ICS kernels from your device, and hopefully resulting in you not bricking the crap out of your phone. Go check this page: http://forum.xda-developers.com/showthread.php?t=1525495
I DO NOT take credit for finding this bug, credit goes to Entropy512 and XDA TV's EGZTHUNDER1 for alerting me of this bug. I have safely removed the affected ICS kernel from my phone and custom builds, now it's your turn.
The only reason I'm requesting a sticky in the wrong forum (Yes, I know I posted in the development branch) is because most users won't know about these affected kernels before trying their newly rooted E4GT into some ICS bling.. Next thing you know, you've got a two day old brick with a shiny screen.
Please, once again, GO TO THIS PAGE and explore the options of returning your phone back to dry land.
As a reminder, DO NOT FLASH ANYTHING FROM CWM OR MOBILE ODIN.
While I have heard that flashing a non-ICS kernel from ODIN has fixed these issues, we're looking more into that now.. I have alerted xST4T1K of this, and we'll get back to you with confirmed results.
Safe flashing, XDA members.
Maybe this sticky from the general forum should just be moved over to here.
http://forum.xda-developers.com/showthread.php?p=23149990
Sent from my SPH-D710 using Tapatalk 2
Weve kinda known this for a while now since the February leaks... js. Still, safe flashing everyone lol.
first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
If you do what is said above, you won't brick your device.
Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?
NOW again....
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
Quite Easy.
In the end, it's called following directions.
Edit: just to clarify... Wiping cache/dalvik cache from stock or cwm repacked recoveries is safe.
The issue is Wiping Data (Don't use the option)
bigpeng said:
first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
If you do what is said above, you won't brick your device.
Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?
NOW again....
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
Quite Easy.
In the end, it's called following directions.
Click to expand...
Click to collapse
So my question is... What about flashing mod's that require only wiping cache and dalvik??? I guess I've been lucky with wiping cache and dalvik from cwm recoveries but does this mean no more mod's until source is released???
Sent from my SPH-D710 using Tapatalk 2
bigpeng said:
first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
If you do what is said above, you won't brick your device.
Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?
NOW again....
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
Quite Easy.
In the end, it's called following directions.
Click to expand...
Click to collapse
In a world where users flash before they research, common sense doesn't have a stronghold.
DjKurt said:
So my question is... What about flashing mod's that require only wiping cache and dalvik??? I guess I've been lucky with wiping cache and dalvik from cwm recoveries but does this mean no more mod's until source is released???
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
The issue is from Wiping Data from stock and cwm recoveries, you can wipe cache and dalvik with no worries. Those don't mess with partitions.
Sent from my SPH-D710 using xda premium
You may be able to flash wipe mods and such but imsince I bricked mine doing just that. I will not flash anything in an ics recovery. I will Odin modems and will flash roms and kernels in one session and that is always coming from stock GB. Take for what its worth. Not saying the above mentioned ways aren't worth noting. But flashing the format script in blue cwm while on ICS is what bricked me.
scarmon25 said:
You may be able to flash wipe mods and such but imsince I bricked mine doing just that. I will not flash anything in an ics recovery. I will Odin modems and will flash roms and kernels in one session and that is always coming from stock GB. Take for what its worth. Not saying the above mentioned ways aren't worth noting. But flashing the format script in blue cwm while on ICS is what bricked me.
Click to expand...
Click to collapse
That sucks, sorry to hear that...
I was one of the first to test cwm repacked recoveries for agat63 since FE10 and have flashed 37 times to and from different roms and done backups and restores countless times and I've been fine.
I haven't been fearful of any bricks since I tested these repacked kernels.
Hope it does get figured out once source hits though.
Edit: btw what kernel (with or without cwm repack?) did you brick in?
Sent from my SPH-D710 using xda premium
It was back when CM9 first was released. I was using the el26 cwm kernel to flash. I was on one of the ice builds I can't remember. I odined the kernel cwm combo el26 and then ran a format all and flashed cm9 and ggot the blue light special haha
Its all good though. I have read alot of info in this including the one mentioned. One thing that was mentioned in one of them is that the bug had been triggered be deleteing a large file off the internal memory. That worried me. So I've been weary of ICS builds since. The fact that the issue seems to be that info getting wrote to a certain block of the emmc has me worried that it could be triggered by more then wiping of flashing. I have ran agats ROMs and I have to say he seems to be doing something right. Whether it is because he is staying TouchWiz or what for some reason his users seem tto not have many issues. But just keep in mind that it may not just be kernel/recovery related.
Safe flashing is key and I never want to see someone brick. Just be careful in whatever you do.
Sorry, I haven't had much of a chance to update my thread lately but I will soon. With all the leaks that were consistently being released, it wasn't feasible to update it every other day. The thread already has everything you need to know about bricking so I figured if you couldn't figure out how to prevent a brick with the information given, then you should probably buy an IPhone and never attempt flashing in the first place.
xST4T1K said:
Sorry, I haven't had much of a chance to update my thread lately but I will soon. With all the leaks that were consistently being released, it wasn't feasible to update it every other day. The thread already has everything you need to know about bricking so I figured if you couldn't figure out how to prevent a brick with the information given, then you should probably buy an IPhone and never attempt flashing in the first place.
Click to expand...
Click to collapse
I couldn't have said it any better, my friend!
As far as those who've bricked their phones, it is truly unfortunate.. Google themselves has been brought into light on this situation, and are working to correct this issue in the kernels that they've been adding in with their firmware.
As far as your useless phones go.. Try filing for an insurance claim, I guess! NOT my professionally recommended advice.. But IF someone were to have stolen that useless phone of yours and you were to never see it again.. Well, who am I to say that's not a reason to get a replacement from asurion! Lol!
By the way, xST4T1K.. Bumped you thanks count up a little more.
Thank goodness I ran into these threads before I decided to flash anything else.. Been running a solid ICS rom for a few weeks, now. But I'd rather get back to safe land on GingerBread Island and use Apex Launcher. Wouldn't care for the huge difference in the settings menu. Would miss the lockscreen, though.. Not aiming my finger at an unlock tab has gotten habitual!
crazy.. not sure i agree with this thread.. its scaring people away from trying awesome roms.. if you search in any ics rom or aosp ics rom you hear little about people bricking there phones.. there are clear instructions to install and if you dont know what your doing and cant follow instructions dont do it or you will have a brick. ive been on ics since the first leak and have had to odin many times after a "soft brick" from me not following instructions but its simple.. dont format data on any ics kernel/cwm and you'll be fine..
Sent from my SPH-D710 using XDA
elliwigy said:
crazy.. not sure i agree with this thread.. its scaring people away from trying awesome roms.. if you search in any ics rom or aosp ics rom you hear little about people bricking there phones.. there are clear instructions to install and if you dont know what your doing and cant follow instructions dont do it or you will have a brick. ive been on ics since the first leak and have had to odin many times after a "soft brick" from me not following instructions but its simple.. dont format data on any ics kernel/cwm and you'll be fine..
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I would never want to scare anyone away from trying these great builds on XDA. What I do want though is to make people aware that no matter how many tines you flash something. Always treat the flash your about to do as if it was your first. Sometimes we get to comfortable in what we're doing. We have to remember that this is a pretty expensive device and if something happens you may be buying a new one outright. Not everyone has insurance or can throw out that kind of cash. Do safe flashing practices and make sure you read the OP. When flashing leaked software make sure to flash from stock or the most current OEM released build such as EL29 in this case. Verify the right files are in the right slots of Odin. Make sure you're flashing files in the right sequence when in a custom recovery. Thing like that. I believe in the openness of android and never want to see anyone say they aren't going to flash something because they are scared. With the right ammount of reading and precautions. There is no reason to be scared.
Just for example. And this is not an exaggeration. Between this phone,my wife's phone, my last phone, my wife's last phone, and numerous friends phones. I have well over 200+ flashes. I have only had one actual brick. And that brick was because I got too comfortable in what I was doing. So, odds are if you take tthe time to do it right. You will succeed. Also.
i cant figure out why this is not locked yet....
i agree scarmon.. you said it better than i could.. if i wasnt tech savvy and i read the op i would have been scared away.. it says in all caps not to flash in cwm and says many have experienced bricks.. it can be worded differently but its freedom of speech.. when the initial leak came out and we had rogue ics kernels and the LOSt kernel we werent sure why people were having bricks until we figured out what was causing it.. we've known this for a while and since then hard bricks have dropped drastically.. and every single developer insisted not flashing from ics kernels and every rom has a disclaimer in the op for this reason.. only bricks ive read have been user error for a while ie. unplugging device during odin flash or battery dieing during mobile odin flash etc.. plus this is in the dev thread.. right now most people come here for ics roms since thats what devs are working on.. and many have gone safely back to gingerbread many times.. the ics roms have hundreds of thousands if not millions of hits and how many posts about hard bricks?
Sent from my SPH-D710 using XDA
I've been flashing ICS roms since FB17 and haven't had any bricks. I've been making sure to only flash things from EL26 and it's been smooth sailing.
Now I'm running the most recent AOKP and it's running very well.
Your credit is pretty thin too. Entropy is a big name in this issue but him and some random dude that apparently notified you very very late about this issue doesn't even cover half of it.
The front page news on the issue was pretty late as well. Just lets the general population know about it.
ijoshv2 said:
While I have heard that flashing a non-ICS kernel from ODIN has fixed these issues, we're looking more into that now.. I have alerted xST4T1K of this, and we'll get back to you with confirmed results.
Click to expand...
Click to collapse
Its things like this "While I have heard" that is the problem with your post. That and begging for a sticky, talk to a moderator if you feel its important.
Flashing a non-ics kernel through ODIN does not fix any issue. Flashing from a safe Kernel avoids the issue, If your on ICS flashing the GB Kernel from ODIN would be the safe method. Gingerbread as far as we have known and hundreds of flashes per person per hundreds of phones later. No one has been known to trigger the eMMC firmware bug though gingerbread. So yes flashing from a Gingerbread kernel as we have since the phone came out is the safest known way. You don't need anyone to tell you that.
You come in and say "Do not flash anything from CWM". This is inaccurate it suggests one can not flash from EG30+ CWM which has never been a known danger. Obviously EK02 would be more popular due to supporting full modems rather than patch. EL26 was the last to have true CWM which is why EL29 Rogue is less often suggested.
ijoshv2 said:
The only reason I'm requesting a sticky in the wrong forum (Yes, I know I posted in the development branch) is because most users won't know about these affected kernels before trying their newly rooted E4GT into some ICS bling.. Next thing you know, you've got a two day old brick with a shiny screen.
Click to expand...
Click to collapse
The danger is not in flashing ICS. The unknowing user is going to be flashing ICS from EL29 which is safe. The danger is after they are there, and they try a factory reset, or install a CWM or Unlocked Recovery Kernel and flash something, or flash an update.zip through stock recovery. Yes they need to know, the information should be accurate however.
If anyone wants details of this emmc firmware bug, there's some really knowledgeable people in this thread.
http://forum.xda-developers.com/showthread.php?t=1644364
The info is very detailed, but these are the individuals to watch. OP if your serious about helping our community with this emmc bug, I hope you join in that conversation instead of asking to sticky this thread.
Sent from my SPH-D710
Related
Can any of the devs give a technical explanation on why this is necessary?
I am coming from the Sprint Hero phone and it seems like that phone went through a similar phase early on.
Originally, wiping and flashing a ROM seemed to be somewhat hit or miss and sometimes wiping mulitiple times and then flashing twice before starting the ROM the first time seemed to get it through a rough spot.
Now with the Epic, when switching one ROM family to another, the devs are typically saying that an ODIN is needed to get on that ROM family, then normal wiping and flashing from CWM works as expected as long as you stay within that ROM family.
SOOOO.. my question is... Why is that? Is CWM still too green on this phone to properly clear everything that is needed? Does a flash not write to every memory address that is needed?
No griping on my part, just honest curiosity both for why it happens, what if anything is being done, and how it is even diagnosed.
<Bump> Please? I'm not asking to be smart. I'm asking to get smart. Educate me and hopefully others on the issues you are encountering. It would be interesting to hear.
Odin is only necessary to flash Modems when switching roms with different android versions (EC05 for Froyo, EF02 for Gingerbread etc.).
The reason for this is differences in how Samsung handles their Modem files vs other devices.
Wiping cache and dalvik is important because, when flashing a rom over another rom that's installed. The data from the previous installation tends to linger, which could cause some major issues. May even brick your device. Think of it as a bad kidney transplant. Incompatibility could brick your life. You figga dill me?
Sent from my SPH-D700 using XDA Premium App
And the reason for the 3X wipe was because the ported Clockwork Mod was not perfect and did not clean everything the first time. I believe that has been fixed in the newer version so that once is sufficient.
Sent from my SPH-D700 using XDA App
Alright, I'm no noob and I've successfully rooted and flashed several phones over the past couple of years, I get what we're doing - above a basic knowledge, well below an "expert". But it seems somewhere around FC05 I started seeing warnings about using the Rogue Repack to both flash ROMS and restore. I fully understand people were have major issues with touch recovery/ROM Manager, but this is different. This is what I've been able to pick from filtering through threads, it's a little tough to put it together because it's a few dozen post in many places. Please, in detail if you can, fill in the blanks.
1. Obviously, DON'T use an ICS recovery to restore a GB setup or the other way round. That seemed a no brainer.
2. Steady is advising people to NOT flash any ROMS using the FC kernals. I've waited and used the sfhub's one-click ODINs since EL26, but I found this interesting he's advising to not use it to go from FC06 to FC07, for example.
3. Some say don't flash an ICS ROM zip from ICS recovery, some say it's no problem.
I've slimmed down quite a bit during the ICS transition because, I knew I'd be doing a lot of flashing. So doing a manual restore is not too big of a deal. But is there, in an experts opinion, any perceived issue restoring an ICS nandorid in a FC recovery?
Data is formated differently in ICS, so it is best to just leave it alone. They say not to wipe data in ICS recoveries because of the format difference. Your best bet is to play it safe and use gingerbread EL26 kernel with CWM.
Thanks, and I get the difference between ICS and GB formatting, but are these warnings only for those trying to go back to GB? Or are you saying NO MATTER WHAT play it safe and if you must restore use EL26 (ie One-click back to stock/rooted), since the new ICS kernal would get flashed over it anyhow?
Forgive me for asking for a complete breakdown, but I'd rather play Devil's Advocate and get the info posted.
I would recommend ALWAYS going back to the EL26 CWM kernel. I attempted to wipe data from FC07's CWM and bricked my phone.
luckychef28 said:
Thanks, and I get the difference between ICS and GB formatting, but are these warnings only for those trying to go back to GB? Or are you saying NO MATTER WHAT play it safe and if you must restore use EL26 (ie One-click back to stock/rooted), since the new ICS kernal would get flashed over it anyhow?
Forgive me for asking for a complete breakdown, but I'd rather play Devil's Advocate and get the info posted.
Click to expand...
Click to collapse
Please consider changing further conversation on this to the following thread:
http://forum.xda-developers.com/showthread.php?t=1525495
This has been regularly updated with advice and links as the OP is trying to get it stickied. It also helps those of us keeping a close eye on the topic to consolidate what we're looking at versus going through many threads.
As for flashing ICS ROMs there is a good link in that first post that should give you the requested breakdown. Hope this helps!
I am currently running Agat63's tFD26_v0.1.0 Rooted Odexed along with FD26 kernel w/ rogue cwm that was taken from Calkulin's_E4GT_2_ROM_v1.5 and I want to do a nandroid backup. Is it safe to do the backup from this kernel or do I need to go back to EL26+cwm?
Also, what would be the safest way to restore said backup if I am on another ICS rom? I don't think I will be playing with AOKP or CM9 for some time so those are not in question.
Reflash the El26 CWM kernel, nandroid, then reflash the FD26 kernel so that your Rom will boot again.
That's all ya gotta do. If you have to restore from that nandroid, you will have to restore, then reflash the FD26 kernel for it to work.
Honestly the answer to this and many questions can be easily found in here or using Google. As instructed above basically flashing an EL26 kernel will get you started. I don't mean to be an ass but this a question you honestly should of figured out prior to flashing.
Knowing what to do before you get yourself into trouble is always a good idea. I just don't want to see you start a I bricked my phone thread that's all. Be careful and know your options in the future....
Good luck
playya said:
Honestly the answer to this and many questions can be easily found in here or using Google. As instructed above basically flashing an EL26 kernel will get you started. I don't mean to be an ass but this a question you honestly should of figured out prior to flashing.
Knowing what to do before you get yourself into trouble is always a good idea. I just don't want to see you start a I bricked my phone thread that's all. Be careful and know your options in the future....
Good luck
Click to expand...
Click to collapse
Nobody is in trouble here, and quite frankly I am not sure how many times someone has answered a question about a kernel that is from a rom that was released a couple days ago. But maybe my question SHOULD have been is this newest kernel safe to back up with.
CyberpodS2 said:
Nobody is in trouble here, and quite frankly I am not sure how many times someone has answered a question about a kernel that is from a rom that was released a couple days ago. But maybe my question SHOULD have been is this newest kernel safe to back up with.
Click to expand...
Click to collapse
A day ago a week ago a month ago the process is still the same my friend I see you got a little upset my bad but your question is no different than the process noted all over xda epic touch forum.
I am basically saying that asking the question can open up multiple answers and may only confuse you more. Follow the developers wishes and those who know better than us and things should go great for you. Again my bad if you dont get what I am trying to say.... Happy Flashing
quite simply use the GB EL26 CWM and make sure you have a copy of the ICS kernel...
Once again good luck
playya said:
A day ago a week ago a month ago the process is still the same my friend I see you got a little upset my bad but your question is no different than the process noted all over xda epic touch forum.
Click to expand...
Click to collapse
I am not upset, just wanted to nail down what is what in regards to my setup. There is conflicting (or at least concurrent) information regarding what is and is not safe to flash with repacked kernels vs. the EL26+CWM.
I did a lot of searching and reading before asking my question. I have read that nothing should be flashed with the rogue repacks. That modems and kernels are safe but not roms. That any zips that do not format are safe. Etc... I truly do understand your frustration with what seems to be similar questions being asked daily. Maybe I did not read enough different posts, but just 5 minutes after reading your reply I read this post: http://forum.xda-developers.com/showpost.php?p=25850359&postcount=165
You might understand why I thought to ask about my specific rom/kernel install. I do appreciate the time you took to reply twice and no I don't think your being an ass.
From what I have read and through my own experience, the AOSP type ROMS are really the only ones that you need to backup using the EL26 kernel. I have switched between agat/calk/venum/stock rooted using the rogue fd02 kernel with no issues at all. The brick seems to happen because the AOSP kernels/ROMS are written different than the stock based ROMS and it corrupts the partition when trying to go back and forth.
T.C.P. is almost done with his AOSP Cwm kernel so it might just pay to be patient for it.
Of course, flash at your own risk always.
Sent from my SPH-D710 using XDA
dante32278 said:
I have switched between agat/calk/venum/stock rooted using the rogue fd02 kernel with no issues at all.
Of course, flash at your own risk always.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Question for you since you have been through those roms. Did you have a favorite? I came from Blazer 4.1 to tFD26_v0.1.0 and so far am happy with it. That being said I was wondering if any of the others had a shiny spot worth looking at...
Calks is super fast....the new one from reactive disorder has been very smooth and is my current daily...agat roms are nice and run smooth....personally I like the rubix from reactive disorder. No issues with the rom and he is all over the message board for it.
Sent from my SPH-D710 using XDA
dante32278 said:
Calks is super fast....the new one from reactive disorder has been very smooth and is my current daily...agat roms are nice and run smooth....personally I like the rubix from reactive disorder. No issues with the rom and he is all over the message board for it.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Sweet... Thanks!
CyberpodS2 said:
I am not upset, just wanted to nail down what is what in regards to my setup. There is conflicting (or at least concurrent) information regarding what is and is not safe to flash with repacked kernels vs. the EL26+CWM.
I did a lot of searching and reading before asking my question. I have read that nothing should be flashed with the rogue repacks. That modems and kernels are safe but not roms. That any zips that do not format are safe. Etc... I truly do understand your frustration with what seems to be similar questions being asked daily. Maybe I did not read enough different posts, but just 5 minutes after reading your reply I read this post: http://forum.xda-developers.com/showpost.php?p=25850359&postcount=165
You might understand why I thought to ask about my specific rom/kernel install. I do appreciate the time you took to reply twice and no I don't think your being an ass.
Click to expand...
Click to collapse
Believe me I understand your frustration but it seems what may work for one does not always work for another and I would prefer you to be cautious and like you said SAFE way to backup as opposed to a way that someone on here may have had luck with... But it seems you got it under control so again enjoy!
playya said:
Believe me I understand your frustration but it seems what may work for one does not always work for another and I would prefer you to be cautious and like you said SAFE way to backup as opposed to a way that someone on here may have had luck with... But it seems you got it under control so again enjoy!
Click to expand...
Click to collapse
Thanks man!
Hey Guyz am new here ,
coming from S1 i500, i have noticed its not as easy flashing and rooting this phone as was with i500.
So decided to make a small query bunch for you knowledgeable guyz. Hope I will be helped as i was helped and properly tutored there at i500 Fassy forums.
1.. what is this ODIN count , every one talks about , how it happens and ways to reset or avoid it ( lol for the first time i laughed at this but meh, its there )
2.. what is this yellow triangle thingy , over at fascinate forums , yellow triangle meant Download mode and thats it , but here it seems its something EVIL
3.. Why there is such a BIG BRICK BUG in E4GT , which comes into play while factory rest or data wipe ? and especially in ICS,
4.. Currently i am on FI03 stock rooted , want to flash a CWM recovery thru which i can freely change ICS ROMS , how can i do that
and whats the exact procedure to flash newer roms ,
what i know is just wipe all three and flash
5.. whats the safest way to go from ICS to GB ( stock rooted ) - are those One click files by the ULTIMATE ACE sfhub can be flashed on any setup irrespective of ICS or GB or even JB ??
6.. which are the safest possible recoveries available for
GB
ICS
JB
and how to flash them on respective setups
7.. for a great user experience and battery backup
which custom ROMS are suggested for
GB
ICS
JB ( i know )
and whats the best way to install aka flash them.
I know its kinna too much , and might turn a lot of you off , but would appreciate the help coz really me having enough know how about fassy , feel out of sorts with E4GT , then what was going thru the minds of total newbies.
Thankies
lord dredd said:
Hey Guyz am new here ,
coming from S1 i500, i have noticed its not as easy flashing and rooting this phone as was with i500.
So decided to make a small query bunch for you knowledgeable guyz. Hope I will be helped as i was helped and properly tutored there at i500 Fassy forums.
1.. what is this ODIN count , every one talks about , how it happens and ways to reset or avoid it ( lol for the first time i laughed at this but meh, its there )
2.. what is this yellow triangle thingy , over at fascinate forums , yellow triangle meant Download mode and thats it , but here it seems its something EVIL
3.. Why there is such a BIG BRICK BUG in E4GT , which comes into play while factory rest or data wipe ? and especially in ICS,
4.. Currently i am on FI03 stock rooted , want to flash a CWM recovery thru which i can freely change ICS ROMS , how can i do that
and whats the exact procedure to flash newer roms ,
what i know is just wipe all three and flash
5.. whats the safest way to go from ICS to GB ( stock rooted ) - are those One click files by the ULTIMATE ACE sfhub can be flashed on any setup irrespective of ICS or GB or even JB ??
6.. which are the safest possible recoveries available for
GB
ICS
JB
and how to flash them on respective setups
7.. for a great user experience and battery backup
which custom ROMS are suggested for
GB
ICS
JB ( i know )
and whats the best way to install aka flash them.
I know its kinna too much , and might turn a lot of you off , but would appreciate the help coz really me having enough know how about fassy , feel out of sorts with E4GT , then what was going thru the minds of total newbies.
Thankies
Click to expand...
Click to collapse
I might be able to answer them all, as I'm not as knowledgeable in this area as other, but I've learned from the best here so ill answer what I can to help and pass on the knowledge I have!
1: it occurs when a non-Samsung kernel is flashed through Odin. You can avoid it by using Mobile Odin or the autoroot package to flash a recovery, or use one of the Odin Ome-clicks.
2: i cant remember exactly, but i believe the yellow triangle appears when the odin count goes up. Again, avoidable through Mobile Odin and Odin One-clicks.
3: I believe the brick bug is kernel related. That's avoidable by using a safe recovery. You can find out of its safe by either asking around if it's not posted that it is, or by reading the OP.
4: I can't help you with a custom recovery for that build. I never went to it. The last build I was on was the leaked version of FF18. But yes, standard procedure is wipe all three then flash rom and gapps if needed. But always check the OP first.
5: sfhubs Odin One-clicks are the best thing you could ever use. Ever. Yes, they can be flashed regardless of what version you're on. In fact I believe that's standard procedure for downgrading.
6: for GB and ICS recoveries, use the autoroot package that's should be stickied in one of these sub forums. For JB, it's automatically packaged in the JB rom you flash. It's CWM6.
7: this changes with every person you ask. Here's my favorite on each of the three:
GB: definitely sfhubs Tweaked stock roms. They're smooth and fast. Run without problems unless you cause one.
ICS: I would say either AOKP or CM9. AOKP no longer has a device for our device though. He dropped it to do an AOSP ICS rom.
JB: definitely CM10. I've hardly had any issues with it. Although I have high hopes for AOKP JB that's in development right now. Once it's major bugs get worked out, since it's brand new right now, that will be my daily driver.
And to anyone more knowledgeable on this than me, if I'm wrong on any of these please correct me.
Sent from my SPH-D710 using xda app-developers app
All of these questions are answered in sticky posts. You need to do a lot more reading before you potentially brick your phone.
Thanks a lot EggosEvo
now all i need is someone directing me to a safe recovery and its flashing method so that i can try out either Calk's ICS ROM or some other stable yet awesome ROM.
One important thing that i have noticed
I may be doing something wrong , but in comparasion why di i feel that Fascinate's camera is way way better as compared to E4GT
the INDOOR pictures with E4GT are darker and with some darker hues on colors too whereas with my 1.5 yrs old fascinate the INDOOR snaps are pretty well lit and clear with good natural colors
and a BUMP
lord dredd said:
Thanks a lot EggosEvo
now all i need is someone directing me to a safe recovery and its flashing method so that i can try out either Calk's ICS ROM or some other stable yet awesome ROM.
One important thing that i have noticed
I may be doing something wrong , but in comparasion why di i feel that Fascinate's camera is way way better as compared to E4GT
the INDOOR pictures with E4GT are darker and with some darker hues on colors too whereas with my 1.5 yrs old fascinate the INDOOR snaps are pretty well lit and clear with good natural colors
Click to expand...
Click to collapse
What I would do is Odin One Click to FF18, then use the Autoroot package(should be stickied in the dev section) to flash Agat's source-built recovery. That's just the easiest way I know how to do, as I don't know how if there are any custom recoveries for FI03. Plus its a safe way to go. You could always search the forums for an FI03 based recovery if you don't want to go to a build that was released quite a bit ago.
Thanks a bunch mate.
Actually just five minutes before you replied, I took the plunge and used mobile odin to flash agat's latest fi03 kernel and clock work mod.
So now I have a custom recovery as well.
Also I am sure now there us no issue wiping data via recovery to flash other roms
Regards
GWizzing on beautifully and freakin loving it.
Ravaged Pheonix said:
All of these questions are answered in sticky posts. You need to do a lot more reading before you potentially brick your phone.
Click to expand...
Click to collapse
lord dredd said:
Thanks a bunch mate.
Actually just five minutes before you replied, I took the plunge and used mobile odin to flash agat's latest fi03 kernel and clock work mod.
So now I have a custom recovery as well.
Also I am sure now there us no issue wiping data via recovery to flash other roms
Regards
GWizzing on beautifully and freakin loving it.
Click to expand...
Click to collapse
Although you may not of liked Ravaged Pheonix's answer it was a damn good one, he deserves some thanks as well. All these questions are answered for you in stickys. That is where you should start so there is no confusion. Hate to see you start a "I Think I Bricked My Phone" thread.... Jus Sayin'
well mate , i have been there and read quite a lot
from where do you think i got all the info i have mentioned in the first post.
Everyone who doesnt flame deserves a Thank, i should have thanked him as well, correcting it now
The reason for starting a new thread was i didnt want to go on posting spearate queries in separate threads , so made one in Q and A ,
this might as well help other newbies who keep searching pages after pages on various threads for some smallish thing.
Regards
I bought two new SG3's yesterday for my sons, and immediately commenced to root one of them via the "Easy Root" method in a how-to here (ODIN recovery, flash root.zip, rooted). I encountered all kinds of issues where no recovery (CWM, TWRP, or even a stock recovery image) would mount anything. I finally read here on XDA where the stock root that comes with the Toolkit works, so I tried that and now I'm back to stock recovery but, of course, an non-rooted phone. I didn't try to do any of this on the second phone after encountering so many issues. I assumed that something may have changed with this latest update and that this root method may not work anymore.
Anyway....
When I boot the phone that I attempted to root to stock recovery, the little Android is dead on his back with an exclamation point in a triangle. Everything seems to work though -- I can wipe cache, browse around the SD card and cache, etc. I assumed it was because of my dinking around with root and that the phone was now cranky because the flash count was at like 5 or 6 by now. However, I then booted the phone that I didn't dink around with to stock recovery and noticed that the Android was dead for it, too! I've done nothing to this second phone that a 75-year-old first-time smartphone user wouldn't do.
So my question: Is this normal? Is this something that happens when you force it into stock recovery or is there something wrong with these two phones, above and beyond the apparent inability to be rooted (at least at the moment)?
internetpilot said:
I bought two new SG3's yesterday for my sons, and immediately commenced to root one of them via the "Easy Root" method in a how-to here (ODIN recovery, flash root.zip, rooted). I encountered all kinds of issues where no recovery (CWM, TWRP, or even a stock recovery image) would mount anything. I finally read here on XDA where the stock root that comes with the Toolkit works, so I tried that and now I'm back to stock recovery but, of course, an non-rooted phone. I didn't try to do any of this on the second phone after encountering so many issues. I assumed that something may have changed with this latest update and that this root method may not work anymore.
Anyway....
When I boot the phone that I attempted to root to stock recovery, the little Android is dead on his back with an exclamation point in a triangle. Everything seems to work though -- I can wipe cache, browse around the SD card and cache, etc. I assumed it was because of my dinking around with root and that the phone was now cranky because the flash count was at like 5 or 6 by now. However, I then booted the phone that I didn't dink around with to stock recovery and noticed that the Android was dead for it, too! I've done nothing to this second phone that a 75-year-old first-time smartphone user wouldn't do.
So my question: Is this normal? Is this something that happens when you force it into stock recovery or is there something wrong with these two phones, above and beyond the apparent inability to be rooted (at least at the moment)?
Click to expand...
Click to collapse
It's been a long time since I've dealt with custom recoveries, but I believe that's just the normal background for it. It's like you're tinkering with the inner working of an Android (wiping cache, etc), so you've opened up the green robot.
That's what I recall from when I still had stock about 9 months ago...
If it shows up like that, that means you have the stock recovery...use GooManager or Rom Manager to install a custom recovery while booted up.
Sent from my buttered S3
Hmmm...any other time I've been in a stock recovery, I remember the Android being standing with that spinning wireframe in front of him. that's what displays when I successfully wipe the cache. Maybe I'm just remembering wrong and I'm being paranoid since I'm still deep in issues with being able to install a working custom recovery.
Hey, I'd love to install a custom recovery via GooManager or ROM Manager, but none of the custom recoveries are working on my SG3's. Nothing will mount so I'm stuck with stock recovery until someone more knowledgeable than me figures outwhat Sprint and/or Samsung did with the latest SG3's.
internetpilot said:
Hmmm...any other time I've been in a stock recovery, I remember the Android being standing with that spinning wireframe in front of him. that's what displays when I successfully wipe the cache. Maybe I'm just remembering wrong and I'm being paranoid since I'm still deep in issues with being able to install a working custom recovery.
Hey, I'd love to install a custom recovery via GooManager or ROM Manager, but none of the custom recoveries are working on my SG3's. Nothing will mount so I'm stuck with stock recovery until someone more knowledgeable than me figures outwhat Sprint and/or Samsung did with the latest SG3's.
Click to expand...
Click to collapse
I don't know why you're having these problems but the newest update (md4) roots exactly like any other software on the s3... I and many have done it plenty of times, it roots exactly the same way... Not sure why your recovery won't mount anything but somebody else also had this problem just today... You could always try to Odin in an earlier build (lj7 maybe) and try to root from there
“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power."” ― David Brin
flastnoles11 said:
I don't know why you're having these problems but the newest update (md4) roots exactly like any other software on the s3... I and many have done it plenty of times, it roots exactly the same way... Not sure why your recovery won't mount anything but somebody else also had this problem just today... You could always try to Odin in an earlier build (lj7 maybe) and try to root from there.
Click to expand...
Click to collapse
I think something changed on the newest batch of S3's. I'm sure the OTA S3's are still rootable with this method but for some reason the brand new ones aren't. I've found at least a dozen other people complaining about the same thing only with brand new S3's.
Unfortunately I had a limited window of time to root these two phones and get them set up before going on vacation, so the phones are in use now and there's no way to backup and restore the existing configuration, data, etc.without like a day of downtime and basically starting over. And even then it's not a sure thing that reverting to an older stock ROM will work. I'll just wait for someone to figure it out and then root the phones later.
But there's definitely something new going on here. Its happening to too many people now. At least my sanity is confirmed!
internetpilot said:
I think something changed on the newest batch of S3's. I'm sure the OTA S3's are still rootable with this method but for some reason the brand new ones aren't. I've found at least a dozen other people complaining about the same thing only with brand new S3's.
Unfortunately I had a limited window of time to root these two phones and get them set up before going on vacation, so the phones are in use now and there's no way to backup and restore the existing configuration, data, etc.without like a day of downtime and basically starting over. And even then it's not a sure thing that reverting to an older stock ROM will work. I'll just wait for someone to figure it out and then root the phones later.
But there's definitely something new going on here. Its happening to too many people now. At least my sanity is confirmed!
Click to expand...
Click to collapse
When you decide to root again here is a prerooted Odin build for mc3, after successfully flashing via Odin you will be rooted and can flash up to md4 from there... There is a prerooted that wipes everything and one that wipes and restores, make sure you read carefully and flash the one you need http://www.sxtpdevelopers.com/showthread.php?t=207
“It is said that power corrupts, but actually it's more true that power attracts the corruptible. The sane are usually attracted by other things than power."” ― David Brin
flastnoles11 said:
When you decide to root again here is a prerooted Odin build for mc3, after successfully flashing via Odin you will be rooted and can flash up to md4 from there... There is a prerooted that wipes everything and one that wipes and restores, make sure you read carefully and flash the one you need http://www.sxtpdevelopers.com/showthread.php?t=207
Click to expand...
Click to collapse
Thanks for this. I'm not going to attempt root again until I can get a working custom recovery going.
internetpilot said:
Thanks for this. I'm not going to attempt root again until I can get a working custom recovery going.
Click to expand...
Click to collapse
That build will do it all.. It is prerooted, includes the custom recovery... Just like flashing a custom rom with recovery except you do it with Odin
flastnoles11 said:
That build will do it all.. It is prerooted, includes the custom recovery... Just like flashing a custom rom with recovery except you do it with Odin
Click to expand...
Click to collapse
Hmmm...but I wonder if that will end up with a working recovery or if I'll be in the same boat I am now, but with an older stock ROM?
I'm just really hesitant to try anything until someone figures out what Sprint/Samsung did with this latest batch of S3's. It's probably something relatively simple to overcome, but I'm not mobile tech enough to even guess what that is. I can't really end up with sons' new phones bricked (even soft bricked).
internetpilot said:
Hmmm...but I wonder if that will end up with a working recovery or if I'll be in the same boat I am now, but with an older stock ROM?
I'm just really hesitant to try anything until someone figures out what Sprint/Samsung did with this latest batch of S3's. It's probably something relatively simple to overcome, but I'm not mobile tech enough to even guess what that is. I can't really end up with sons' new phones bricked (even soft bricked).
Click to expand...
Click to collapse
You may be waiting a long time then since most devs either already have the phone or have already moved to other phones... Unless a Dev happens to pick one up with the same problems you're probably S.o.l... And I'm 95%sure they didn't change anything, some phones just have issues on certain builds, there have been plenty of people the last month and even the last week reporting successfully rooting with the same method you used...
You really have nothing to lose, if it doesnt work you can just Odin full stock and be in the exact same place you are now
flastnoles11 said:
You may be waiting a long time then since most devs either already have the phone or have already moved to other phones... Unless a Dev happens to pick one up with the same problems you're probably S.o.l... And I'm 95%sure they didn't change anything, some phones just have issues on certain builds, there have been plenty of people the last month and even the last week reporting successfully rooting with the same method you used...
You really have nothing to lose, if it doesnt work you can just Odin full stock and be in the exact same place you are now
Click to expand...
Click to collapse
True. I always forget the Odin option for when recovery fails. But I'd be without the data and current configuration (basically starting from scratch).
In the last two days I've seen posts from over a dozen people now who are encountering this issue with brand new Sprint S3's. I'm kinda hoping more and more people encounter this problem increasing the chances of it being resolved... Haha
It doesn't matter once your rooted and booted all you do us download either rom Manager or goo manager and install the custom recovery of your choice from the running phone. Doesn't get any easier.
Sent from the future via Tapatalk 4
Until the custom recovery can't mount anything, which is the problem I'm having now. I've tried numerous versions of CWM and TWRP and none of them can mount anything on these phones so they're useless. I'm not sure how reverting back to an older stock ROM will change that...?
internetpilot said:
Until the custom recovery can't mount anything, which is the problem I'm having now. I've tried numerous versions of CWM and TWRP and none of them can mount anything on these phones so they're useless. I'm not sure how reverting back to an older stock ROM will change that...?
Click to expand...
Click to collapse
Because you yourself feel the bootloader is the issue. If you Odin the stock tar of a previous version then that loads a previous bootloader. Pretty simple huh? I rooted 2 S3 last week brand new and did not have a single issue both where on the latest md4 right out of the box. I don't understand how you and that other person both ran into the same issue on the same day. It's really weird and like everyone else said and I just experienced just a week ago thousands of people have rooted on the latest version on brand new devices. Unless you guys are getting refurbs which by accident the bootloader has been locked.
Sent from the future via Tapatalk 4
edfunkycold said:
Because you yourself feel the bootloader is the issue. If you Odin the stock tar of a previous version then that loads a previous bootloader. Pretty simple huh? I rooted 2 S3 last week brand new and did not have a single issue both where on the latest md4 right out of the box. I don't understand how you and that other person both ran into the same issue on the same day. It's really weird and like everyone else said and I just experienced just a week ago thousands of people have rooted on the latest version on brand new devices. Unless you guys are getting refurbs which by accident the bootloader has been locked.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Flashing back to an older stock rom doesn't work either. I flashed to a 4.1.1 stock rom and followed the method for CF-Root and The Easiest Way to Root and neither of them allowed a custom recovery to mount anything.
deutscher3891 said:
Flashing back to an older stock rom doesn't work either. I flashed to a 4.1.1 stock rom and followed the method for CF-Root and The Easiest Way to Root and neither of them allowed a custom recovery to mount anything.
Click to expand...
Click to collapse
Thank you for trying that as I couldn't because I'm on vacation with the two phones in use. Well that sucks that it didn't work. I'm a retired career network engineer, so I'm not a non-tech, but I'm also not the most tech person with regard to mobile phones. Even so, I can't figure this one out so it's probably not something obvious. Also, on XDA and other forums I'm up to about 18 different people who have now encountered this on very new Sprint S3's.
internetpilot said:
Thank you for trying that as I couldn't because I'm on vacation with the two phones in use. Well that sucks that it didn't work. I'm a retired career network engineer, so I'm not a non-tech, but I'm also not the most tech person with regard to mobile phones. Even so, I can't figure this one out so it's probably not something obvious. Also, on XDA and other forums I'm up to about 18 different people who have now encountered this on very new Sprint S3's.
Click to expand...
Click to collapse
Did you purchase your phones from Sprint directly? I purchased mine through Wirefly. Thinking I may send it back for exchange and pray like heck I get one that works. I am definitely a Vanilla Android person. Touchwiz is not my cup o tea.
Enjoy your vacation, as much as you can. Us tech nerds can never get it off the mind when something isn't working. Lol
Sent from my SPH-L710 using Tapatalk 4 Beta
I purchased two s3 phones from Amazon about a month ago and haven't had any issues. Both are rooted too. The root process is pretty simple. Have you tried the unified toolkit also? Another easy method.
deutscher3891 said:
Did you purchase your phones from Sprint directly? I purchased mine through Wirefly. Thinking I may send it back for exchange and pray like heck I get one that works. I am definitely a Vanilla Android person. Touchwiz is not my cup o tea.
Enjoy your vacation, as much as you can. Us tech nerds can never get it off the mind when something isn't working. Lol
Sent from my SPH-L710 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Both directly from Sprint.
lvpre said:
I purchased two s3 phones from Amazon about a month ago and haven't had any issues. Both are rooted too. The root process is pretty simple. Have you tried the unified toolkit also? Another easy method.
Click to expand...
Click to collapse
The problem isn't really root. Depending on the method, we can get root. It's the custom recovery that's the problem -- it can't mount anything so you can't flash anything, backup, wipe, etc via recovery.