Develop Bugs

Vote to fix haret method.

http://code.google.com/p/vogue-andr... Priority Component Owner Summary#makechanges

things change fast around here. try reading new threads before post useless request to fix an old problem from march

If your going to daddy me at least leave me a toy.
Wow learn to read. The android n00b thread people are still having these issues. Maybe something has changed but I have seen it. I see two categories of haret users those who work (miracles people who usually are using nand and may have some enviromental difference over us regular sdcard-hare ppl)..
If you can fix my issue fix it, but don't tell me its fixed when nothing says that. Albeit a night of going through all the updates on the different builds may produce results no one has done that in that particular thread (2, or 3, which upon someone coming up and saying this easy has ended up giving up) both threads are a bit different. One was supposed to be look how easy it is , with a few nand resistant fools getting every thing but sound. You sir are a troll... !#@@! @!# @#[email protected][email protected]@!
Seriously if you want new people using android put out a haret build that works... Don't make us n00bs flash our customized **** so we can say oh thats broke, i need that...

sorry if my tone was incorrect. let me try again
The link you posted refers to something that is not a problem any more or was due to old hardware, ie the button physically wasnt working.
k_k successfully used haret to test his build when he was working on the gps. that was the beginning of june
are you trying to say that the link is to YOUR problem? i cannot tell from the post of only a link. it looks like reading through this thread that you got past that problem.
if you need help please list your problem with as much detail as possible so i or someone else can help you.
if you are trying to make a case for haret dev, you should post links or quote more recent attempts and problems

Thanks for the news
Cool. I'll search up on that and post to the threads that I've been going to. It's just email never comes across very personable. People who say to read the entire forum get on my nerves or to search when I have is annoying because sometimes they have read it in an area I haven't landed and it like a race run condition due to bad communication. If you see something try to link it, glad I have a user name to search off, but if you can pt a better thread I'll be happy. Either way when I find it, I'll try to boot again maybe in a week or so. I'll be very happy if it does indeed work now, we'll see.. As far as my posting relating to haret, yet you can regain control of your buttons but if you actually read all of the thread you'll see it doesn't get better than that, it then is a sound issue. Either way haret is broken, and my point is that poor user from march is still suffering now, and this time its sound. I suspected that haret became broken due to the development direction towards nand. I.e. whatif system.file is reffed somehow as (NAND0,0):/initrd.gz. I mean droid when from system.img's to partitions so something very generic could lead to both issues esspecially if a user A who can't hear in haret, can hear in a nand install using the same release? See the modules and stuff are going to be the same. I hope your not wasting my time with the k_k bit...

tyler51773 said:
I hope your not wasting my time with the k_k bit...
Click to expand...
Click to collapse
no. he is one exmple of people who have it working. there are others, i just know him off the top of my head.
People who say to read the entire forum get on my nerves or to search when I have is annoying because sometimes they have read it in an area I haven't landed and it like a race run condition due to bad communication.
Click to expand...
Click to collapse
your first post was just as indirect. from that post i had no way of know you have been working on it. the specific link you post was probably not the best choice. with out direction from you i have no reason to go 2 links deep. not until you gave more description did i go into the xda thread where have been trying things.
it then is a sound issue.
Click to expand...
Click to collapse
yes there is still the sound issue. you could have gotten much better response if you had put something in the first post to indicate you specifically want the sound worked on.

sound it is.
its just more like a watch me thread for people who care about haret. i posted a bug on vogue-android.. but the drift it haret is broken. been broken. its bad right now. can we fix it? or is it fixed already. you mentioned K_K do you mean this thread http://forum.xda-developers.com/showthread.php?p=6852911 or do you mean kalt_kafee kernel are they same guy? where you saying dpad was fixed versus just sound. I guess I'm going to try his latest update kernel, unless you've seen a better thread. I've already got to goto bed. Maybe that's why the guy never came back on my own thread cause i sent him to a new kalt kernel hehehe..

sound working
Going through the list now. Thanks for the pointer. I'll will soon venture forward.
I got sound on an old androidinstall of unknown origin. it was freezing and unstable. I did not get sound ironically on VaniljEclair , the second install from the old android I also installed to system.img vs sdcard partition. trying warm
Aqtrans' CM-5.07 - nice and stable
warm eclair rls 1 - fast, worked great for a day then force closes all over
Incubus26Jc's SuperE beta 3 - still slow on kaiser
VaniljEclair 5.0.8 out! (not tested by me)
trying myn's warm donut then will try aqtrans'
you may have beaten the pepsi challenge.

OCLF is not safe, DO NOT TRY IT

DO NOT TRY OCLF, if you can not go to factory reset.
I have read almost all the threads answer etc. on many forums, How many people faced the problem and I think I am latest victim after having OCLF, phone doesn't start anymore, does not go in hard reset..nothing just vibration and 2 lights in bottom nothing else.
It just screwed me, OCLF 2.2, with Z4Root , Android 2.2 froyo on SGS....installed and you are gone. still you want it go ahead, feel free....I am angry on myself not on anybody else but I thought, I better write something to save few people at least, opposed to other people who are also bricked and praised the fix to not to stand alone.
Finally I gave phone back, not sure if I get a new one or get same repaired ( in warranty or I have to pay if they can detect that It was me not the hardware or something else...), will post what happens but for now, its not safe, do not go for it and remember there is very thin line between bravery and foolishness. decide yourself.

There are numerous ways to recover your SGS, all you had to do was have a read on here, don't panic and use the search function.
I'm new to all this and i've been in the same position as you and have thought I had bricked my phone at least 5 or more times. But thanks to others on XDA they have same me and my SGS )

sorry but if you dont know what you are doing, why are you doing it?
and btw there are alot of things you can do to recover your phone, even if its totally bricked.
you saying you read all threads etc? i dont think so cuz then you would know what to do.
and OCLF IS SAFE, if you know what you doing and have to do if its going wrong.
ps: if you need help, pm me i will explain you what to do, but only if you have the phone in front of you.

There should be a big banner in the development section which says "Don't try these if you are a n00b and not willing to read and learn before flashing anything!"

That is a thoughtless, misinformed thread title maligning a good developer's excellent work.
Think hard before you post in future........
doc jpy 7.1, jpx, k12i.

OCLF pertains to the Software Level. I see no reason for the Hardware to be affected. You should always be able to go the Download Mode after removing the battery for sometime.

i just say OMG.. i "bricked" (like you) my device about 7-8 times... no problem! i also BRICKED my device 1 time... no problem! don't panic, sgs is very strong! use search function of forum, the problem is not OCLF itself, is a "dead" sd-card (i don't know exactely, i'm a noob) it's a problem connected with the mount of an internal memory, i personally discovered that it might be also connected with a wrong flash of the csc (personal experience!)
Next time (yes it will be) don't panic there's a solution

No panic, just another way of adding some more info for OCLF
Well well well, I am not in panic, I have had galaxy for 5 days only and of-course a new comer for Android, I didn't hesitate for the fix, tried to figure out pros and cons (unfortunately didn't see complains for the problem I had after reboot, until I became the victim) and to be clear not trying to blacken the founder of OCLF with due respect.
Thanks for the fellows offering help, I don't have phone with me as I was not willing to play around with other fixes as I can get it fixed by service center but it would be great if you can blog about it or mention steps here for a problem of a phone stuck on Galaxy screen and can't go in recovery mode and does not connect with odin. what you get is black screen, 2 lightning button in the bottom and vibration when you press any key in bottom or screen.
I was already expecting the several responses and staring eyes but if its safe then why you have so many thread complaining a frozen phone. If this fix is safe then why its removed from Market? (arrg Google norms..but for a good thing and open source system, don''t understand, make it an enhancement, put it already in ROM)
and why OCLF app does not warn, if you have a temp root or permanent root? before making the fix. if its not possible in this context then place info window as it will fail with temp root.
ODIN thing will only work with rooted phone what if its temp rooted and do you want any user to open their phone's mother board for making some soldering to re flash.
Please somebody make a detailed instruction page, if its safe and get proper steps and don'ts list, I won't mind doing it again once I get phone back and keeping fingers crossed that they won't charge me for this out of warranty. Not sure I'll get replacement or repaired one.
Again its not safe until and unless in any case you are ready for using other fixes (which may or may not be applicable for your situation)to fix the phone.There are chances that you loose important data(if not backup). Go for it, if you have enough time and nothing else to do, if it works, good for you, if not don't panic..............
and don;t forget its not your development machine, open in front of you, for free by company, which has corrupted passwd file or something and not booting up....it's your costly new smart phone.
yeah criticize me but its doesn't feel nice when your brick your new phone.
in the end some more things to remember based on my exp for prevention:
1. Back up data
2. make sure you have hard reset option available
3. Root permanent
Please add more if you know. anyways thanks for all the responses.

Tried once to have a bricked phone, my first try actually..
Formated the system by mistake, to high i guess.. LOL..
Non the less, had black-screen ofc, System format, in more than 5 hours, till I tried odin with the org firmware, and brick gone
Sure, thought Sh!!!!!t at first, but then started reading, that was what I've spent the 5 hours on, and 7mins later up and running.. No worries for brick no more
So, think you could have made it your self, instead of returning it, sry
Or maybe you couldn't go into DL mode? I could with formated system?
Just like dhiru1602 wrote, DL mode should be in place, it was on mine like I said

SandeepSharma said:
Well well well, I am not in panic, I have had galaxy for 5 days only and of-course a new comer for Android, I didn't hesitate for the fix, tried to figure out pros and cons (unfortunately didn't see complains for the problem I had after reboot, until I became the victim) and to be clear not trying to blacken the founder of OCLF with due respect.
Thanks for the fellows offering help, I don't have phone with me as I was not willing to play around with other fixes as I can get it fixed by service center but it would be great if you can blog about it or mention steps here for a problem of a phone stuck on Galaxy screen and can't go in recovery mode and does not connect with odin. what you get is black screen, 2 lightning button in the bottom and vibration when you press any key in bottom or screen.
I was already expecting the several responses and staring eyes but if its safe then why you have so many thread complaining a frozen phone. If this fix is safe then why its removed from Market? (arrg Google norms..but for a good thing and open source system, don''t understand, make it an enhancement, put it already in ROM)
and why OCLF app does not warn, if you have a temp root or permanent root? before making the fix. if its not possible in this context then place info window as it will fail with temp root.
ODIN thing will only work with rooted phone what if its temp rooted and do you want any user to open their phone's mother board for making some soldering to re flash.
Please somebody make a detailed instruction page, if its safe and get proper steps and don'ts list, I won't mind doing it again once I get phone back and keeping fingers crossed that they won't charge me for this out of warranty. Not sure I'll get replacement or repaired one.
Again its not safe until and unless in any case you are ready for using other fixes (which may or may not be applicable for your situation)to fix the phone.There are chances that you loose important data(if not backup). Go for it, if you have enough time and nothing else to do, if it works, good for you, if not don't panic..............
and don;t forget its not your development machine, open in front of you, for free by company, which has corrupted passwd file or something and not booting up....it's your costly new smart phone.
yeah criticize me but its doesn't feel nice when your brick your new phone.
in the end some more things to remember based on my exp for prevention:
1. Back up data
2. make sure you have hard reset option available
3. Root permanent
Please add more if you know. anyways thanks for all the responses.
Click to expand...
Click to collapse
Did u read the info screen that pops up when u first started oclf? I guess u didnt coz there are very clear instructions on what u have to do to apply the lagfix sucessfully...
Edit: btw ockf is on market again he just had to remove the abillity to root...
Sent from my GT-I9000 using Tapatalk

SandeepSharma said:
Well well well, I am not in panic, I have had galaxy for 5 days only and of-course a new comer for Android, I didn't hesitate for the fix, tried to figure out pros and cons (unfortunately didn't see complains for the problem I had after reboot, until I became the victim) and to be clear not trying to blacken the founder of OCLF with due respect.
Thanks for the fellows offering help, I don't have phone with me as I was not willing to play around with other fixes as I can get it fixed by service center but it would be great if you can blog about it or mention steps here for a problem of a phone stuck on Galaxy screen and can't go in recovery mode and does not connect with odin. what you get is black screen, 2 lightning button in the bottom and vibration when you press any key in bottom or screen.
I was already expecting the several responses and staring eyes but if its safe then why you have so many thread complaining a frozen phone. If this fix is safe then why its removed from Market? (arrg Google norms..but for a good thing and open source system, don''t understand, make it an enhancement, put it already in ROM)
and why OCLF app does not warn, if you have a temp root or permanent root? before making the fix. if its not possible in this context then place info window as it will fail with temp root.
ODIN thing will only work with rooted phone what if its temp rooted and do you want any user to open their phone's mother board for making some soldering to re flash.
Please somebody make a detailed instruction page, if its safe and get proper steps and don'ts list, I won't mind doing it again once I get phone back and keeping fingers crossed that they won't charge me for this out of warranty. Not sure I'll get replacement or repaired one.
Again its not safe until and unless in any case you are ready for using other fixes (which may or may not be applicable for your situation)to fix the phone.There are chances that you loose important data(if not backup). Go for it, if you have enough time and nothing else to do, if it works, good for you, if not don't panic..............
and don;t forget its not your development machine, open in front of you, for free by company, which has corrupted passwd file or something and not booting up....it's your costly new smart phone.
yeah criticize me but its doesn't feel nice when your brick your new phone.
in the end some more things to remember based on my exp for prevention:
1. Back up data
2. make sure you have hard reset option available
3. Root permanent
Please add more if you know. anyways thanks for all the responses.
Click to expand...
Click to collapse
READ!!!!!!!!!!!!!!!!! SEARCH!!!!!!!!!!!!!!!!!!!!!!!!!!!! READ!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! SEARCH!!!!!!!!!!!!!!!!!!!!!!!!! BREATH IN!!!!!!!!!!!!!!!!!!!!!!! BREATH OUT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
1. You didn't read instructions clearly
2. You created a misleading thread title
3. You are now asking for step by step instructions when there is already numerous guides and answers on how to get your phone going again
4. You now look like a lazy, ignorant and upset kid that broke his new toy because he was too rough with it and now expects to be spoon fed instead of actually learning from his mistake.
5. I am not usually this hard on anybody but I am annoyed by this thread

you're funny. maybe you can discuss why it's so bad with RyanZA himself?
herpderp.

If you hadn't have badmouthed his work, you'd have found Ryan extremely helpful, in fact, he's such a good bloke, he'd probably still help you if it was necessary.
doc jpy 7.1, jpx, k12i.

@OP: Please change the thread's title to something more respectful for RyanZA's hard work.
A good title like : "too lazy to read before doing something potentially dangerous to my expensive smartphone, I've bricked it (in fact probably not...) while trying OCLF..."
___________________________________
Sent from my GT-I9000 ××× DocRambone®'s XXJPY_Kitchen, Hardcore®'s SpeedMod K12I, ext4-all ××× using Tapatalk Pro®

its ok now guys, he is new to android and galaxy. Close this thread pls.
pm me if you got your phone back and i still will help you and explain everything.

Just plug it into the computer and use adb reboot recovery. Should work, it did for me.
Sent from my GT-I9000 using XDA App

madfix said:
@OP: Please change the thread's title to something more respectful for RyanZA's hard work.
A good title like : "too lazy to read before doing something potentially dangerous to my expensive smartphone, I've bricked it (in fact probably not...) while trying OCLF..."
___________________________________
Sent from my GT-I9000 ××× DocRambone®'s XXJPY_Kitchen, Hardcore®'s SpeedMod K12I, ext4-all ××× using Tapatalk Pro®
Click to expand...
Click to collapse
@OP (original poster) please change the title or delete the thread.
I installed OCLF about 2 weeks ago on my new Froyo install (!!>after reading<!!) and had no problems at all. I used version 1.1 on Eclair and version 2 on Froyo. Ryanza has made a brilliant tool and does not at all deserve to be tainted like this

A ignorant noob like u dont even deserve the help! Uve read? Where?? In every instruction its writte try this at ur own risk.. I had the same problem..Didnt u read abt the 3 button combo?? Z4root and OCLF dont always work well together! AH m very annoyed cuz i really respect Ryan's work!! READ ----- READ----- then again READ--

no point flaming him too much. just report his post

all i can say is LOL

[Q] ICS soft-brick hopeless? Sum up of all attempts tried...

Good evening,
As you can see, I'm a noob on XDA, but I have done my due diligence on searching, and researching, and at an impass which an answer to, would be greatly appreciated.
In addition to explaining my specific issues and what I've done to fix it, it would be great if this post could help contribute a sum of all issues/attempts at fixing, for this huge problem, because I've found bits and pieces of the symptoms and fixes scattered in many different posts.
Ok...so I know now that issues with an ICS kernel source, possibly some problems with CWM (especially Touch), ROM manager, and nandroid backups/restores back and forth from GB to ICS, etc., caused this problem, which apparently a lot of people are having, and it doesn't seem to be a solely stupid-noob mistake. I just wasn't aware of the problems of going back and forth between GB and ICS. I always wiped data before installs, did nandroid backups, basic due diligence, and "thought" I was safe. Obviously mistaken.
So...my mistake was- I flashed Calkulin's stock F22, kernel, modem (instead of Odin) Worked great, looked great- Backed up in ROM Manager (instead of recovery) Then went back into recovery later to do a restore, but not back to GB, but rather my freshly installed ICS. And that's where it occured.
I've got all the symptoms many others have explained in several other different post:
It hung on data, wouldn't restore. Tried to reboot- boot animation loop all the way.
Tried Odin, all attempts hung at data, I knew at that point- my data was likely corrupted, partition messed up, etc.
Emmc won't mount, data won't mount, can't wipe, etc.
What I've tried:
Numerous attempts with Odin (1.85, the one-clicks), Roms, recovery-only files, stock rom, .tars, kernels
Tried Pit on and off to help with partitioning (remember I'm a noob)
When I could get into different CWM recoveries off and on, I tried to flash everything under the sun: Stock unrooted, EL29 rooted, EL29 w/o data (really hoped that would work), zedomax kernel, retried to flash stock fc22 kernel and fc22 de'odexed rom, maybe in some f'd up way, get back into ICS.
I tried repartitioning, mounting, clearing cache, disabling signature verification, wiping, restoring, advanced restoring, applying updates, etc.
Emailed Josh who said JTAG couldn't help me.
Tried Heimdall one-click, looking at trying Heimdall full.
Probably at least one or 2 others, I'm missing. But long story short- is I've tried pretty much everything.
I'm still holding out hope I'm just soft-bricked, and can somehow get back from this, but I simply can't find a way to fix the data.img.
I've read the posts on "how not to brick your E4GT"- one guy wrote:
_______
Everytime i try a OC odin, it hangs at data.img forever, i can't restore any rom, tried reflashing the rom that 'broke' my phone, not sure where else to head.
You didn't read what me and stonesaber were talking about did you? your phone is not bricked, however, to get it back is extremely complicated and may not even be worth attempting. They're is another thread somewhere in which they fix this issue with a very in-depth procedure, keep looking and you will find it
_______
I searched for this "very in-depth procedure" but can't seem to find it, if there is one. I was to a point, where I couldn't install or get anything to load. I have fought my way back a bit, and hope I'm making progress.
Where I'm at now:
I can get into download mode
I can boot into recovery
I was even able flash a copy of Cyanogenmod RC 7.2 that I just happened to thankfully have on my internal SD. At first it had nothing on it, and couldn't get data/wifi. It would freeze up. But I was able to go back into recovery...advance restore, and restore boot, system, cache, sd-ext., everything but data. As a result, I could then get wifi/data signal. I tried to install titanium, but it said I had no more memory (obviously). It has developer tools, terminal emulator. But when I reboot of course, I lose everything I just restored, and would have to re-restore.
I don't know if any of that would help- I haven't been able to get my phone to do squat for 3 days, but now I can actually load a "half" working ROM again.
There have got to be outs from here, right??
What else is there left to try?

Had a similar problem. I had to flash el26 kernel with cwm recovery. From there I wiped everything like 10 times. I then flashed el29 deodex and let it settle for like an hour. From within that rom. I cleared internal storage and wiped my sd card. I odined el29 stock rooted. Used the one-click to install recovery and have since been ok.

You made another post and just like the other thread you are bricked and there is no fix.....your reading comprehension must be horrible because this is the same as 15 other threads....thanks
Sent from my SPH-D710 using xda premium

Epix4G said:
You made another post and just like the other thread you are bricked and there is no fix.....your reading comprehension must be horrible because this is the same as 15 other threads....thanks
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
He can type like a mofo though

Epix4G said:
You made another post and just like the other thread you are bricked and there is no fix.....your reading comprehension must be horrible because this is the same as 15 other threads....thanks
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Wow...what an attitude right out the gate. I read profanity isn't allowed; can I use the word.....d*ck? I hope your posts and actions aren't representative of other senior members...
First off...this was literally the first post I've ever posted here, after registering just this evening...hence why you see today's date for my join-date and the words "good evening". So no...I haven't ever posted anything here.
And...as I said in my post, many other's have mentioned similar symptoms, and similar fixes, but one or two at a time scattered in many different posts, yet all the same issues and fixes for the same main root cause, whereas here is a summation of all.
I know you probably feel a bit god-like on this site senior member....but let the noob...who's not really a noob in that whole reading and writing English thing, give you the memo that the "horrible reading comprehension" is all yours bro...on pretty much literally everything you said in your post.
It's pretty sad, because I would certainly expect some harmless noob flac and/or joking, but not a typical ****-post (especially from a senior member) I sometimes see on XDA from time to time, that- instead of advancing a solution to the issue, creates a back-and-forth reply-session for pages at a time, simply junking up a post, wasting peoples time.
That being said, if you'd like to re-read my post, notice that I've tried pretty much everything you remarked about in all those other posts, and offer a positive contribution to the discussion, it would be appreciated. If not, another smart-alec reply would be expected. To be honest, I'd rather have the surprise of a quality answer. It's always cool in life when you think bad of someone, and they surprise you.
If there is another experienced senior member that has some input, that would be appreciated too.
Thanks

tkemack said:
He can type like a mofo though
Click to expand...
Click to collapse
Thanks for the compliment man. I taught English for a while, so I would hope I had that whole writing thing down. But I've heard from some that my reading comprehension is actually quite crappy...lol

Honestly I think you're pretty much screwed. I think the post you're looking for is titled something like "help! Stuck in data.img"
Edit: http://forum.xda-developers.com/showthread.php?t=1504808

tkemack said:
Honestly I think you're pretty much screwed. I think the post you're looking for is titled something like "help! Stuck in data.img"
Edit: http://forum.xda-developers.com/showthread.php?t=1504808
Click to expand...
Click to collapse
Thanks for link sir! Unfortunately, did read that blow-by-blow as sfhub tried to help dude. I did Odin that original tar file sfhub mentioned, but it's just straight Rogue recovery. I mean, it helped, because it was a workable recovery that let me finally flash Cyanogenmod 7, and get to a bootable rom.
I did Odin EL29, and like that post, it skipped over data. When I Odin'ed stock unrooted md5, it did the same thing.
The unfortunate part, is that I am fully capable of booting into a working rom, but because my data or data partition is damaged, I am crippled. Since getting my Evo over 3 years ago, and reading about the amazing programmer feats in Android on this site and others, it's unfortunate there is no program or ability to reformat or repartition from here.
One area that I have NOT seen on XDA regarding this issue- a readme doc for Heimdall regarding this issue (it says earlier in the page that it works for all Samsung firmware) says:
Flashing Firmware from Command Prompt:
1. Fully charge your phone (use the wall charger as it's faster).
2. Download a decrypted Samsung Galaxy S ROM and extract it to a directory.
3. If the ROM is provided as one of more archives (nested or otherwise),
extract them all to the same location.
NOTE: If you want to use the CSC then extract it last.
4. Put your Galaxy S device into download mode and plug it in..
5. Open command prompt and navigate to the directory where you extracted the
ROM files.
6. Type the following to list all the functionality Heimdall supports:
heimdall help
7. Use the instructions to manually enter a command with all the files you
want to flash.
Here is an example that does a full flash and repartition:
heimdall flash --repartition --pit s1_odin_20100512.pit --factoryfs factoryfs.rfs --cache cache.rfs --dbdata dbdata.rfs --primary-boot boot.bin --secondary-boot Sbl.bin --param param.lfs --kernel zImage --modem modem.bin
8. Done
I don't know if this avenue is worth a try. What does someone else think?

AddamsonFlint said:
Wow...what an attitude right out the gate. I read profanity isn't allowed; can I use the word.....d*ck? I hope your posts and actions aren't representative of other senior members...
First off...this was literally the first post I've ever posted here, after registering just this evening...hence why you see today's date for my join-date and the words "good evening". So no...I haven't ever posted anything here.
And...as I said in my post, many other's have mentioned similar symptoms, and similar fixes, but one or two at a time scattered in many different posts, yet all the same issues and fixes for the same main root cause, whereas here is a summation of all.
I know you probably feel a bit god-like on this site senior member....but let the noob...who's not really a noob in that whole reading and writing English thing, give you the memo that the "horrible reading comprehension" is all yours bro...on pretty much literally everything you said in your post.
It's pretty sad, because I would certainly expect some harmless noob flac and/or joking, but not a typical ****-post (especially from a senior member) I sometimes see on XDA from time to time, that- instead of advancing a solution to the issue, creates a back-and-forth reply-session for pages at a time, simply junking up a post, wasting peoples time.
That being said, if you'd like to re-read my post, notice that I've tried pretty much everything you remarked about in all those other posts, and offer a positive contribution to the discussion, it would be appreciated. If not, another smart-alec reply would be expected. To be honest, I'd rather have the surprise of a quality answer. It's always cool in life when you think bad of someone, and they surprise you.
If there is another experienced senior member that has some input, that would be appreciated too.
Thanks
Click to expand...
Click to collapse
I would like to thank you...I now see what is wrong with this country when you have people who can't read and understand that are teaching our children no wonder this country is going down the tubes.. There are only 10 + threads on here with this in them but you still think your special and your problem is so different from the others. Your data partition is screwed and you should be mad at yourself for not reading and understanding this phone before flashing . There is no fix when it hosed your partition is permanent but you don't listen to the numerous people telling you this that is why he told you jtag won't work that is the lowest level of chip programming there is no fixing it with heimdal or Odin . Sleep well tonight and take it to Sprint and cry to them They may replace it for you otherwise craigslist has them for like 300
And don't use ROM manager how many times does it have to be said... Ooh that's right you probably won't read this anyways
Sent from my SPH-D710 using xda premium

These folks arent being jerks. If you spent half of the time reading before the fact as you did typing after the fact then you would have a functioning device...
Buy insurance, run over your phone, and pay the 100 bucks. Then remain stock.
There are tons of threads that explain everything. Your initial post makes it very clear that you went in blind and borked your phone.
Good luck.
Sent from my SPH-D710 using Tapatalk

Start reading here
http://lmgtfy.com/?q=epic+touch+bricked
Sent from my SPH-D710 using xda premium

Epix4G said:
I would like to thank you...I now see what is wrong with this country when you have people who can't read and understand that are teaching our children no wonder this country is going down the tubes.. There are only 10 + threads on here with this in them but you still think your special and your problem is so different from the others. Your data partition is screwed and you should be mad at yourself for not reading and understanding this phone before flashing . There is no fix when it hosed your partition is permanent but you don't listen to the numerous people telling you this that is why he told you jtag won't work that is the lowest level of chip programming there is no fixing it with heimdal or Odin . Sleep well tonight and take it to Sprint and cry to them They may replace it for you otherwise craigslist has them for like 300
And don't use ROM manager how many times does it have to be said... Ooh that's right you probably won't read this anyways
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Why are you wasting your time on this thread? "Ya screwed Bra'h" that's your solution? Firstly, everyone of those "10+ threads" you mention have knowledgeable people giving quality positive suggestions on issues, stark contrast to your style there senior one.
Secondly, I didn't look up rom on google one day and start downloading. I've had several phones I've been rooting and using custom roms for years. I didn't know CWM Touch was sketchy. I didn't know doing a nandroid restore with FC22 with an issue with a kernel could f'up my data. Do you know why I didn't know these things? Because I don't spend every freakin day on forums buddy.
And for the third time- I wrote what I did at the top of my post because of exactly what you are talking about. I looked at those 10+ threads. I looked at more threads than that...for the last 3 freakin days, and better part of a good weekend. I would look at one post and find a solution, only to read 5 pages down, that it didn't work. So let me pose a pretty stupid question: why the 'f would I "want" to do that? Why would I want to spend all that time digging?
But ya know what, after doing all that digging, what I realized is that many if not most people were having issues that mostly stemmed from the same larger root cause. And they were all trying all these things (with little success), randomly strewn among "10+" 20, maybe 30-page threads- who wants to have to make sense all that?
Instead, I put up a post that simply explained root cause, the many symptoms, and the laundry list of fix it methods and their success. I did this for 2 reasons Mr. Epix. One, to obviously find help for my situation, but just as important, to contribute (as positively, ie. to "add" something) in addressing the issue.
I mean, is it that hard? I wrote it, because it would have been a hell of a lot better had I myself stumbled across one or two core posts that listed everything and anything, so I didn't have to spend days digging through dozens of posts and hundreds of pages- it is still somewhat suprising how you don't get it, when you are making my point for me.

AddamsonFlint said:
Good evening,
As you can see, I'm a noob on XDA, but I have done my due diligence on searching, and researching, and at an impass which an answer to, would be greatly appreciated.
In addition to explaining my specific issues and what I've done to fix it, it would be great if this post could help contribute a sum of all issues/attempts at fixing, for this huge problem, because I've found bits and pieces of the symptoms and fixes scattered in many different posts.
Ok...so I know now that issues with an ICS kernel source, possibly some problems with CWM (especially Touch), ROM manager, and nandroid backups/restores back and forth from GB to ICS, etc., caused this problem, which apparently a lot of people are having, and it doesn't seem to be a solely stupid-noob mistake. I just wasn't aware of the problems of going back and forth between GB and ICS. I always wiped data before installs, did nandroid backups, basic due diligence, and "thought" I was safe. Obviously mistaken.
So...my mistake was- I flashed Calkulin's stock F22, kernel, modem (instead of Odin) Worked great, looked great- Backed up in ROM Manager (instead of recovery) Then went back into recovery later to do a restore, but not back to GB, but rather my freshly installed ICS. And that's where it occured.
I've got all the symptoms many others have explained in several other different post:
It hung on data, wouldn't restore. Tried to reboot- boot animation loop all the way.
Tried Odin, all attempts hung at data, I knew at that point- my data was likely corrupted, partition messed up, etc.
Emmc won't mount, data won't mount, can't wipe, etc.
What I've tried:
Numerous attempts with Odin (1.85, the one-clicks), Roms, recovery-only files, stock rom, .tars, kernels
Tried Pit on and off to help with partitioning (remember I'm a noob)
When I could get into different CWM recoveries off and on, I tried to flash everything under the sun: Stock unrooted, EL29 rooted, EL29 w/o data (really hoped that would work), zedomax kernel, retried to flash stock fc22 kernel and fc22 de'odexed rom, maybe in some f'd up way, get back into ICS.
I tried repartitioning, mounting, clearing cache, disabling signature verification, wiping, restoring, advanced restoring, applying updates, etc.
Emailed Josh who said JTAG couldn't help me.
Tried Heimdall one-click, looking at trying Heimdall full.
Probably at least one or 2 others, I'm missing. But long story short- is I've tried pretty much everything.
I'm still holding out hope I'm just soft-bricked, and can somehow get back from this, but I simply can't find a way to fix the data.img.
I've read the posts on "how not to brick your E4GT"- one guy wrote:
_______
Everytime i try a OC odin, it hangs at data.img forever, i can't restore any rom, tried reflashing the rom that 'broke' my phone, not sure where else to head.
You didn't read what me and stonesaber were talking about did you? your phone is not bricked, however, to get it back is extremely complicated and may not even be worth attempting. They're is another thread somewhere in which they fix this issue with a very in-depth procedure, keep looking and you will find it
_______
I searched for this "very in-depth procedure" but can't seem to find it, if there is one. I was to a point, where I couldn't install or get anything to load. I have fought my way back a bit, and hope I'm making progress.
Where I'm at now:
I can get into download mode
I can boot into recovery
I was even able flash a copy of Cyanogenmod RC 7.2 that I just happened to thankfully have on my internal SD. At first it had nothing on it, and couldn't get data/wifi. It would freeze up. But I was able to go back into recovery...advance restore, and restore boot, system, cache, sd-ext., everything but data. As a result, I could then get wifi/data signal. I tried to install titanium, but it said I had no more memory (obviously). It has developer tools, terminal emulator. But when I reboot of course, I lose everything I just restored, and would have to re-restore.
I don't know if any of that would help- I haven't been able to get my phone to do squat for 3 days, but now I can actually load a "half" working ROM again.
There have got to be outs from here, right??
What else is there left to try?
Click to expand...
Click to collapse
Unfortunately it doesn't look good. At least you posted here and not in development. I clearly see acknowledgments of these other threads in the OP so that would mean you at least did your searching before posting, so meh.
Sadly there seems to be an issue with injecting recoveries into these ics kernels and doing work with them which result in possible non friendly outcomes. I don't have a fix, unfortunately, and its general knowledge that there isn't one atm (nothing implied just stating fact)
I can give advice for the future. Make sure to do your reading before attempting such things. See what others are reporting. And imo stay away from cwm. It can't do anything you're not capable of doing on your own
Edit: the "in depth" fix that you mention I believe involves repartitioning the device. I haven't encountered this issue myself so havent attempted such but I do remember talk about repartitioning the device based on stock config to fix the borked data partition. I wish I had a link but I don't. You might br able to dig it up on xda.
If I come across it ill share.

enfurno said:
These folks arent being jerks. If you spent half of the time reading before the fact as you did typing after the fact then you would have a functioning device...
Buy insurance, run over your phone, and pay the 100 bucks. Then remain stock.
There are tons of threads that explain everything. Your initial post makes it very clear that you went in blind and borked your phone.
Good luck.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Maybe it's the whole "sent from my sph-d710" thing, that your not getting the full context and content on a 4.3" screen.
I made it fully...fuullly clear, that as a part of posting responsibly here, that I researched the hell out of this issue. The list of almost a dozen things I tried to fix it, that I found among more than a dozen threads I looked at...if you know anything about this issue at all- should be pretty obvious that I looked at that content and tried those fixes.
This was the very first thing I noted in my post and made it retardedly clear. So if you missed it the first time, now you know- so why are you offering input here, when you have nothing to add?
It's a shame why some feel this thread needs junked up with talking smack.
Are there any quality knowledgeable members that have some positive suggestions on other avenues in this set of circumstances?

barnacles10 said:
Unfortunately it doesn't look good. At least you posted here and not in development. I clearly see acknowledgments of these other threads in the OP so that would mean you at least did your searching before posting, so meh.
Sadly there seems to be an issue with injecting recoveries into these ics kernels and doing work with them which result in possible non friendly outcomes. I don't have a fix, unfortunately, and its general knowledge that there isn't one atm (nothing implied just stating fact)
I can give advice for the future. Make sure to do your reading before attempting such things. See what others are reporting. And imo stay away from cwm. It can't do anything you're not capable of doing on your own
Edit: the "in depth" fix that you mention I believe involves repartitioning the device. I haven't encountered this issue myself so havent attempted such but I do remember talk about repartitioning the device based on stock config to fix the borked data partition. I wish I had a link but I don't. You might br able to dig it up on xda.
Click to expand...
Click to collapse
Thanks for the info- it has been a learning experience to say the least. I guess I didn't look, because I wasn't looking for that in particular. My friend let me know there was real progress on a good stock ICS for our phones- so I looked it up- and easily found all the files and versions, and page after page of people posting how bomb it was. Of course, I read all the "I'm not responsible for bricking your phone" quotes, but that's been on every page for years.
But from now on, I will definitely do some research on the dirty side of any new big changes on configs. So, I fully understand, stay away from all cwm? or just touch? what should I use place?
and general knowledge of one atm?- (acronym?)
Thanks again for the info

The reason people are grumpy and give attitude on this subject, is because we have to read this subject about every other day, and it's all the exact same thing.
No, there is no fix because flashing through CWM/touch ICS recoveries will BRICK YOU PHONE. No fix, no pass go, no 200 dollars, YOU ARE BRICKED.
I say you are bricked even though there is one solution (that's untested I believe) that involves a deep DEEP level partition of your internal drive to not include the /data/ partition that is now physically f'd up because of wiping through an ICS recovery. No one I believe has tried it, and as far as I know, no one really wants to take the time to try it or even has the ability to do it. Basically, it's not an option.
We are tired of seeing this issue every other day. Yes we know you want to be able to fix it, but we know of no one that can, and we do not like having to state multiple times in the same thread that you are bricked, and have it be refuted by the one asking for help.

Um, wow interesting thread. I see several people actually trying to help however.
Have you tried a different cable btw? The OEM cable is pretty horrible. I didn't see it mentioned throughout the troubleshooting process.

tdunham said:
Um, wow interesting thread. I see several people actually trying to help however.
Have you tried a different cable btw? The OEM cable is pretty horrible. I didn't see it mentioned throughout the troubleshooting process.
Click to expand...
Click to collapse
Yes sir, I did try that as well. And I do appreciate the people trying to help, in spite of the odds.

borkan said:
The reason people are grumpy and give attitude on this subject, is because we have to read this subject about every other day, and it's all the exact same thing.
No, there is no fix because flashing through CWM/touch ICS recoveries will BRICK YOU PHONE. No fix, no pass go, no 200 dollars, YOU ARE BRICKED.
I say you are bricked even though there is one solution (that's untested I believe) that involves a deep DEEP level partition of your internal drive to not include the /data/ partition that is now physically f'd up because of wiping through an ICS recovery. No one I believe has tried it, and as far as I know, no one really wants to take the time to try it or even has the ability to do it. Basically, it's not an option.
We are tired of seeing this issue every other day. Yes we know you want to be able to fix it, but we know of no one that can, and we do not like having to state multiple times in the same thread that you are bricked, and have it be refuted by the one asking for help.
Click to expand...
Click to collapse
Borkan, I totally understand what you're saying- I get why it could get frustrating. I've read a lot of similar posts too that mention the same or similar things over and over. Often times however, what I find in some of these post is-
- someone asking for help for one particular symptom that has rendered their phone inoperable, but aren't aware it's part of a larger issue, and all the discussion around it.
- then, several people...trying to help, chime in "well, did you do this? What about this" for post after post.
So, like I mentioned in an earlier reply- instead of making a post like those other 10 like posts, I tried to give a respectable effort at differentiating my post- because I get the frustration of seeing the same stupid questions.
Instead of asking noob-like, "Hey, I flashed ICS and now I'm hosed, what do I do?" I said, "ok...I know what's wrong, what happened, how I did it. Here's everything I tried from 100's of pages of threads, but still stuck- any new ideas?"
I mean...I've read some pretty dumb posts, poorly explained, stupid questions, that would make someone want to pull their hair out, because the person isn't making it any easier to help them. I wrote what I thought was a decently thorough post, to make it as easy as I could for someone to help me- and I would have hoped such respectable efforts would at least earn a few quality contributions- and surprised to get the same haterade as if I wrote a really poor/stupid post that wasn't quality in anyway.
Had I not been able to get anything to load, I would thought I was pretty much out of options- but getting into one workable rom (albeit w/o data) I was hoping I had outs.
If this is as huge a problem as it sounds- I'd be curious to know why it isn't better identified at the source. I don't know where most people have been going but I went right to:
http://forum.xda-developers.com/showthread.php?t=1494847
I scrolled down a few pags to see if any flags came up- but instead there were just a ton of replies about how awesome it was. It would be good if there was possibly a section in or close to the original post about the issue with this.
And just to close off a criticism before it starts, I'm not talking about the blanket "I'm not responsible for you bricking your phone." That's pasted everywhere and really isn't going to help anyone's cause.
But possibly a convergence of the "how not to brick your E4GT" thread with the main ICS thread, would help fix this issue at the source and before the fact- and keep in mind- I'm not suggesting this for people who are on here posting and contributing every day. It would definitely help noobs who've just bought their phone and never flashed anything before.
But it would also help "intermediates" like myself, to be cautioned about it. I mean...I flashed back and forth from Froyo to GB, different roms, used cwm, for years without issue- this was somewhat of a curve ball for me.
Anyways, that's my thoughts. I understand now that, short of ridiculously complicated work way above my skill set, I am pretty much out of options.
Thanks to all that tried to help.

I'm glad you went about it that way, was the most informed thread for this type of bricking I've seen by far.
I really wish we had a fix but I don't think that'll happen until we have a better ICS kernel. The only one we have to work with right now is just the Stock ICS kernel, we don't have any customized ones yet because they have yet to release the source for it, so we haven't been able to use any others besides the stock, or a GB kernel for it. That's where the problem comes in because those are not meant to wipe data or factory reset when on an ICS bootloader. (At least this is what I've gathered from everything, I've luckily only read about it, not had to experience it myself)

[Q] Root issue

I installed eclipse 4.1.1, it has superuser in it. Tibu works, but when I try to use trickster mod, it says I don't have root access. I used root checker, and sure enough it says I don't have root access on my phone. What's going on with that? What can I do?

I'm not sure of the technicalities causing your issues.
But I can recommend flashing SuperSU in ClockworkMod after installing TricksterMod. Also make a backup beforehand.
Sent from my Galaxy Nexus using Tapatalk 2

Just tried that, didn't work. I don't understand how I don't have root access but one app that required it works and another doesn't.

tried to re-root the phone using the nexus toolkit, no go either. tibu still works but not trickster.

dont use a toolkit. srsly, since you dont know what the hell you're doing.
Sent from my i9250

Thanks, that was real helpful.

Try updating the su binaries from super su app... That's worked for me before. If that doesn't work try flashing an updated rom since they all have su built in.
Sent from my Galaxy Nexus using Tapatalk 2

Tried that too.ended up going to baked black bean ROM.thanks for the input.

bk201doesntexist said:
dont use a toolkit. srsly, since you dont know what the hell you're doing.
Sent from my i9250
Click to expand...
Click to collapse
There's no need to be rude to him. We've all been new at this at some point.
Sent from my Galaxy Nexus using Tapatalk 2

Thank warner. I don't know why some people think if you own a certain phone you should know right away how to do everything the "right" way. If you shouldn't use the toolkit, then take it off the forum. Otherwise people are going to use it like me.

t1.8matt said:
Thank warner. I don't know why some people think if you own a certain phone you should know right away how to do everything the "right" way. If you shouldn't use the toolkit, then take it off the forum. Otherwise people are going to use it like me.
Click to expand...
Click to collapse
just because you find a tool on the table doesn't mean you should take an engine apart without any knowledge before hand.
Some things to search before rooting:
1. What does "root" mean and what does it change?
2. Why do I 'need' root?
3. Differences between soft and hard bricks and how to recover from them.
4. What is and how to use ADB.
5. an extra but, if you were to make this phone unrecoverable or unusable for a degree of time, is this a possibility you can accept? (i ask this because ive worked with those that brick their phone they use for work and then they rush through trying to fix it and make it worse).
We aren't trying to be mean or chase away new users, it's always a great thing when people learn to use their phones. The only thing that can cause bitterness is when users buy a phone and come home and root it because they heard thats what you do with android phones and how to get cool stuff or free apps. Im not saying that is you, likely it isn't from what i've read.
Bottom line, read and learn as much as you can because there is no such thing as too much knowledge. There is nothing more satisfying than figuring out the problem yourself and fixing it instead of 'calling tech support for help' on xda.

I do understand what you're saying. I'm not trying to come off as cocky or I know it all but I have been doing these things with android for a while and do understand how some things work and how to do them. This whole unlocked phone is new to me, and I've never been completely comfortable or able to use fast boot methods which I know is the right way to do most things. I try to learn things about these phones on a daily basis which is why I ask questions and try new things all the time. I appreciate what you have said and am trying to learn how to do things properly, this is just new to me and I appreciate people who have patience to help people like me out.

Darunion said:
just because you find a tool on the table doesn't mean you should take an engine apart without any knowledge before hand.
Some things to search before rooting:
1. What does "root" mean and what does it change?
2. Why do I 'need' root?
3. Differences between soft and hard bricks and how to recover from them.
4. What is and how to use ADB.
5. an extra but, if you were to make this phone unrecoverable or unusable for a degree of time, is this a possibility you can accept? (i ask this because ive worked with those that brick their phone they use for work and then they rush through trying to fix it and make it worse).
We aren't trying to be mean or chase away new users, it's always a great thing when people learn to use their phones. The only thing that can cause bitterness is when users buy a phone and come home and root it because they heard thats what you do with android phones and how to get cool stuff or free apps. Im not saying that is you, likely it isn't from what i've read.
Bottom line, read and learn as much as you can because there is no such thing as too much knowledge. There is nothing more satisfying than figuring out the problem yourself and fixing it instead of 'calling tech support for help' on xda.
Click to expand...
Click to collapse
I do agree that learning as much as we can and being able to fix a problem ourselves without asking for help is extremely satisfying. At the same time though this is the q&a forum and he did try to fix the problem himself through the use of a toolkit, which I agree cuts out a lot of the learning that can be achieved through using fastboot and adb. I think in this forum especially it is better to try to help and make constructive comments than to be rude and post a reply that doesn't help and could possibly chase off a newcomer to modding their device. I appreciate your comment though trying to explain the benefits of learning yourself in a respectful way.
Sent from my Galaxy Nexus using Tapatalk 2

Exactly. I'm not asking anyone to come to my house and fix my phone. But it helps when someone explains what I'm doing wrong and how I can fix my errors in what I'm doing. Thanks for your help everyone who did but I'm going to move on and learn from this experience.

Yes it's a Q&A, but this is a question that asked a lot.
A little bit of reading tell you how to use the forum properly, and you probably find the answer already solved.
Toolkits have there place & for newbies i guess it's the fastest way to get it done, but if you read through the Q's you will find most rooting issues are related to the use of toolkits. Great if they work, but as soon as there is an issue, users are left in the situation you are in now.
efrant & jubakuba have guides in the Q&A section on unlocking, rooting and installing roms with the use of fastboot/adb, all the commands are given.
Good luck

If root is not working as it should, just re-flash the superuser package again. See here.
It's likely an issue with out-dated files or with permissions.

if you use a toolkit, you're on your own - since neither you or us know what happened. it's your fault, for rushing things.
google won't help you either. that's why we say things like that.

Ok, got it. Thanks. Bye.

t1.8matt said:
Ok, got it. Thanks. Bye.
Click to expand...
Click to collapse
Hey I'm a seasoned user here and I'm having the exact same problem with Trickster Mod... you fanboys need to kick it back a notch and try to help someone once in awhile.

Thanks for the info. For now I moved on to Epic V5, maybe when Nitro comes out with the 16 update I'll try it again, cause I really do like that dark eclipse Rom.

GC01 Bugs and Glitches

I've noticed a large amount of glitches and bugs in GC01. If you find any please list them here.
some of the bugs ive noticed:
*Volume slider and slider animation
*Random Reboots
*Missing Features
*Unstable in general

eisawi99 said:
I've noticed a large amount of glitches and bugs in GC01. If you find any please list them here.
some of the bugs ive noticed:
*Volume slider and slider animation
*Random Reboots
*Missing Features
*Unstable in general
Click to expand...
Click to collapse
Just a suggestion, but you may want to consider expanding on the issues so those that may feel like investigating have more to go on. For example..:
*Volume slider and slider animation - Can you provide a screenshot for reference of the issue?
*Missing Features - A list of what you find missing would be helpful. For example; Sprint removed Maps and YouTube since they can be downloaded from the Play Store...
*Unstable in general - How so? What are you seeing that makes you say it's unstable..? FC's, freezing, etc?
There again, only a suggestion but you may get more participation or helpful thoughts on remedies..

More Updates?
I was half expecting gb27 to be the end of the line for this phone.

MrLint said:
I was half expecting gb27 to be the end of the line for this phone.
Click to expand...
Click to collapse
GC01 is Boost's Official JB release.

Post removed. Wrong thread.
Now stop the bickering please.

Post edited.

People please... keep this thread on topic. There are a large amount of boost mobile users that are debating on whether to update or not. Thank you.

Wow... A newbie throwing out rules... Granted threads should stay on topic, but you should understand who is posting in your thread, OP. Garwynn is one of the biggest contributors for the E4GT as well as MoHoGalore. I don't think you have any room to make those kinds of demands when a RC has given you advice on this thread and you completely ignore it. So really, this thread has no real topic of discussion because it says absolutely nothing because of the lack of information provided, therefore people can post whatever they want because this thread is just cluttering up the forum.
Sent from my SPH-D710 using xda premium

graydiggy said:
Wow... A newbie throwing out rules... Granted threads should stay on topic, but you should understand who is posting in your thread, OP. Garwynn is one of the biggest contributors for the E4GT as well as MoHoGalore. I don't think you have any room to make those kinds of demands when a RC has given you advice on this thread and you completely ignore it. So really, this thread has no real topic of discussion because it says absolutely nothing because of the lack of information provided, therefore people can post whatever they want because this thread is just cluttering up the forum.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Whether they're senior members or not, they should follow rules. They could be the owners of XDA and I'd still tell them to stay on topic. There are threads for general conversations, this is not one of them. Rules are rules, and they are meant to be followed. Now please stay on topic people, people really need these kinds of things. And also, he gave me a suggestion. I did not follow his advice because I did not feel the need to do so. My thread, my topic, my list. Whoever wants to add to the list can. Bugs need to be reported to samsung so that hopefully we will have a better future release.

eisawi99 said:
Whether they're senior members or not, they should follow rules. They could be the owners of XDA and I'd still tell them to stay on topic. There are threads for general conversations, this is not one of them. Rules are rules, and they are meant to be followed. Now please stay on topic people, people really need these kinds of things. And also, he gave me a suggestion. I did not follow his advice because I did not feel the need to do so. My thread, my topic, my list. Whoever wants to add to the list can. Bugs need to be reported to samsung so that hopefully we will have a better future release.
Click to expand...
Click to collapse
Well if his advice is not important, then I am going to ask a mod to close this thread because it provides nothing. Also, that will be the last update from Samsung, so with that said, this thread is useless. I also am curious about who is reporting said "bugs" to Samsung? Do you think they will come here to find it? Nope. For the record, they nor I are just Senior Members. All of us that have posted and offered advice are Recognized Contributors. One would do well to take the advice of an RC to help better a thread, instead of blatantly ignoring them. We have been around for quite some time and in that time have learned how things work.
Sent from my SPH-D710 using xda premium

as soon as i gather more bugs i will report to samsung over and over until they release another update, and it was never stated that this would be the last update for the boost model. and if this thread does get closed ill start a fresh new thread where theres no un-needed conversation.

Accidental extra post

eisawi99 said:
as soon as i gather more bugs i will report to samsung over and over until they release another update, and it was never stated that this would be the last update for the boost model. and if this thread does get closed ill start a fresh new thread where theres no un-needed conversation.
Click to expand...
Click to collapse
The Boost model is the same as the E4GT. The 4.1.2 JB Update has been reported as the final from the Samsung sources. I highly doubt they will pay attention to one person reporting little bugs, especially when you don't describe them at all. They have more important things to worry about.

i have a question. does it make you feel better to put people down over the internet? does it make you feel as if your in control of everybody? im not going to be the only one reporting. others that want a bug free GC01 will also report. now please stop further cluttering my thread and go troll someone else.

eisawi99 said:
i have a question. does it make you feel better to put people down over the internet? does it make you feel as if your in control of everybody? im not going to be the only one reporting. others that want a bug free GC01 will also report. now please stop further cluttering my thread and go troll someone else.
Click to expand...
Click to collapse
How am I putting you down? I am agreeing with another RC about your thread not having any descriptions to your so called "bugs". I am not trying to control anything. I am offering the same advice. You can do whatever you like, but I can bet that this thread will either die as is, or it will get closed. You can either let one of the 2 happen by not doing anything to fix it, or do something productive and make it a worthwhile thread. Also, take note. I have not seen very many other people complain about it. Seems like you are the only one or one of a very few people.
Protip: Putting full, well thought out descriptions of your issues will help us help you possibly fix them. If you don't think descriptions are important, you will get nothing.
Example: When testing Shadow_God's Jellyverse 2.0 ROM before he posted it. I ran into a few crashes. I didn't just say "Oh, it crashed". I went into details. "Downloaded via Wi-Fi and installed through Agats GB27 RePack. ROM booted fine, but shortly after getting into the setup process the Android.phone process started force closing. My baseband seems to have been wiped and the launcher seems to be nonexistent."
I then took steps to fix it myself. I was able to fix it with little to no effort, and SG was able to post the ROM without any issues.
So with all that said, if you want to ignore very experienced veterans on XDA, that is your choice. You are free to do so. But don't expect me or anyone else to take you seriously when we make an honest effort to gain viable and needed information to potentially resolve the issues, then have you ignore the efforts.
Consider the following, if we don't take you seriously because of your lack of information and willingness to help us help you, do you honestly think Samsung will give even the slightest crap? They won't... Like I said before, they have better and more important things to do.

From the moderator
To all in the thread...........
Post respectfully......... FOLLOW THE RULES OF XDA OR I CLOSE THE THREAD......
......Thx, oka1

oka1 said:
To all in the thread...........
Post respectfully......... FOLLOW THE RULES OF XDA OR I CLOSE THE THREAD......
......Thx, oka1
Click to expand...
Click to collapse
I vote for option two.
The lack of description on these so called bugs is not informative to the readers, it makes me want to try flashing GC01 to my E4GT just so that I can try to experience whatever issues are being mentioned.
Sent from my SPH-D710 using xda premium

Removed my first post on this thread. I was wrong to post here and op was right to call out.
Op... how you updated to gc01 makes a difference. I still recommend a factory reset or full restore one click. This will resolve most issues as noted in past.
As for whether to update or not that's your call. Most around here believe it is FAR better than ICS and even though this is expected to be the final s/w release feel free to complain to Samsung and/or Boost if not happy. That's your right.
But please avoid using generalizations and then assuming the build is bad based on one individual's experience. That too does other folks a disservice. If you can please provide more specific details it helps the community note confirmed issues and possibly address them on our own.
Thanks.
Sent from my SPH-L900 using Tapatalk 2

I never stated that the build was bad, but like every build it has bugs. the reason i didnt further explain is beacause there really is no way for a screenshot... but i believe i found a fix to anyone experiencing these bugs. so heres what i did to fix my problem.
1. download superuser.zip from rwilco's repo
2. download the gb27 repack from rwilco's repo
3. download the stock gc01 stock kernel
4. place superuser.zip on your sd card
5. Odin the GB27 repack
6. enter recovery and flash superuser.zip
7. delete dalvik cache
8. odin stock gc01 kernel
9. reboot twice

Mattix724 said:
I vote for option two.
The lack of description on these so called bugs is not informative to the readers, it makes me want to try flashing GC01 to my E4GT just so that I can try to experience whatever issues are being mentioned.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
go ahead. the more help the better. it is not some bug that will make you loose all your data... it is minor bugs that annoy the (insert profanity here) out of me. keep in mind there are two installation methods to installing GC01 provided by samsung, local and kies. i chose local because kies wouldnt update for somereason and would randomly crash