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.

[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.

[Q] NEED HELP, stock nexus apps menu not coming up in landscape mode

i was using it quite normally, just got it 2 weeks back and suddenly now i noticed the apps menu coming only in landscape mode, when i open a browser or an app, it can change its orientation but not the menu , also the clock in lockscreen is only in portrait mode suddenly. wat should i do , do i have to do facotry reset etc or wat may be causing it,
i checked and my auto rotate option in settings in checked plz help guys,,

You didn't provide any information to help you with.

063_XOBX said:
You didn't provide any information to help you with.
Click to expand...
Click to collapse
ok , its 4.2 stock android. it cant auto rotate my apps menu anymore as well as the clock in the lockscreen , however if i open an app or browser , i am able to rotate it , i wasnot doing anything fishy , just downloaded some apps from google play , normal apps, and never rooted or tried anything on it. it was working fine from last week when i got it.. please tell me about any other thing you may need to know
also tried checking/unchecking the autorotate option , rebooted several times.

I'm bone stock, and neither my app drawer, nor lock screen have ever had rotation, to my knowledge

Cmoore0965 said:
I've never known the app drawer (which I assume you're talking about) to have a landscape mode. In fairness, I never really cared or looked for it, so that could be my own oversight. The clock app, does, however rotate, so I guess you've got an issue. If you flashed, reflash with a clean install. If you're ota, then you're options branch out depending on if you're rooted, and/or your access to custom recovery. Anyone here is going to need more information, though, to help you. Might start with your current firmware, and method of installing it.
Click to expand...
Click to collapse
ok actually its pure stock , nothing tweaked , iwas planning to but now after this problem ,i dont know

Lol I'm not used to such quick responders on threads, I apologize for my edits and timing. You're first response posted while I was typing. Like I amended my post to say, I've never known this phone to have that function on stock, and mine definitely don't since I've checked just now. We're they rotating before you updated to 4.2?

Cmoore0965 said:
Lol I'm not used to such quick responders on threads, I apologize for my edits and timing. You're first response posted while I was typing. Like I amended my post to say, I've never known this phone to have that function on stock, and mine definitely don't since I've checked just now. We're they rotating before you updated to 4.2?
Click to expand...
Click to collapse
oh ok, i just figured it out , it was basically almost new for me, not much data on it , so i did a factory reset and now the lock screen clock working fine, i guess u rite about app drawer. could wait lol
could you please tell me th best method to root and unlock, as their are so many methods, and then wha are the next possibilities.

Best method to root is a mildly interesting debate around here lol depends on your comfort level with simple adb commands, and a little footwork to find the drivers to do it manually, or your comfort in little understanding of one stop shop toolkits. The toolkits are pretty reliable, and the only discouragement I've heard against them is the fact that you don't have to learn what going on to achieve your goal. The manual method isn't difficult either, you'll have to set up the proper drivers,and sdk on your computer, and use an extremely simple series of commands utilizing fast boot. Either path to root can be found in the stickies around here, and I've only given a very fast a loose overview of the processes lol but keep an open mind, follow the instructions to the letter, and they're both easily attainable
As for further possibilities passed unlock and root, there's always the hunt for your favorite rom, there's extremely useful scripts you can run to modify particular necessities for your experience or shortcomings you may find, there's even guides on compiling your own stuff if you're particularly taken by this wide world of amazing android user control lol you can do whatever you want, buddy. If you've got the time, the selfless dev, mod, and member community here has almost certainly posted how to get it done

Cmoore0965 said:
Best method to root is a mildly interesting debate around here lol depends on your comfort level with simple adb commands, and a little footwork to find the drivers to do it manually, or your comfort in little understanding of one stop shop toolkits. The toolkits are pretty reliable, and the only discouragement I've heard against them is the fact that you don't have to learn what going on to achieve your goal. The manual method isn't difficult either, you'll have to set up the proper drivers,and sdk on your computer, and use an extremely simple series of commands utilizing fast boot. Either path to root can be found in the stickies around here, and I've only given a very fast a loose overview of the processes lol but keep an open mind, follow the instructions to the letter, and they're both easily attainable
As for further possibilities passed unlock and root, there's always the hunt for your favorite rom, there's extremely useful scripts you can run to modify particular necessities for your experience or shortcomings you may find, there's even guides on compiling your own stuff if you're particularly taken by this wide world of amazing android user control lol you can do whatever you want, buddy. If you've got the time, the selfless dev, mod, and member community here has almost certainly posted how to get it done
Click to expand...
Click to collapse
thanx dude, that was encouraging as well as enlightening, and yup i am going to start working on this already dont like some things like i cant customize the lockscreen ,, you were the ist one to ans my post . thanx for a great start..:good:

[Q] SuperSU on TW4.3

SuperSU on TW ROMs running 4.3 (regardless of version, source of version and how you got it) is frustrating. Apps that need root do sometimes able to get root access, and most often than not wont' be able to.
YES !!! I have done more of my share of reading. And please do NOT treat users with less than 10 posts like idiots.
*** The only solution is to change between Default Access modes. Going from grant, to prompt. Doing so for some strange reasons wakes up SuperSU***
The following solutions DO NOT WORK (meaning the problem resists)
1. Flash Antenna (regardless of which, even with the one provided by OP on their threads)
2. Flash insecure kernel zip
3. Download the version form Play and Update
Hope this help any of you that are experiencing some crazy frustrations like me.
*** Not to offend anyone, but the rule of 10 post or less = No reply/post on dev. forum is beyond me ***
*** I have tried to report my experience with certain ROMs, but Nooooooooooo.... <10 amigo ***
--- One more, since I think I am going be booted because of offending Seniors Party Members. ---
Can anyone tell me the logic of formatting a partition 3 times ??? I found this ridiculously offending being an engineer myself.
I do appreciate every single one of the developers who spends countless hours to make the word "FREE" as free as possible.

@mrbackdoor
Whoa Cool down Bro. Take a deep breath. Now tell me what precise are your problems ? I got the part with SuperSU making you go Ape. But what's with Roms and 10 Wipes ? I have no Idea what you are getting at.
So about SuperSU. If that app is making you go nuts, why don't you try SuperUser by @ChainsDD ? There's also a great Superuser app from CM team. But without knowing your Rom, I won't recommend it.
Do Kindly note, some Root apps are not compatible with 4.3. So you may get weird errors. Others like Nandroid Manager have their own limitations on Root access.
P.S. - Your Current Post Count is 1. I did respond right ?

LOL... thanks man. I am positively NOT HOT
what's with Roms
>>> TW 4.3 ATT leak on Tmobile LTElessS3
>>> I was just venting the fact that a member CAN NOT post on Development Forums because he/she has less than 10 posts.
>>> That's like filling 10 forms before you are able to download a file. Similar to registration process that just drive you nut.
>>> One engineering note is wiping a partition 3 times. The wipe process before installing a new ROM.
>>> I just don't get it... Why 3 ??? "insanity according to Albert Einstein"
Superuser..But without knowing your Rom, I won't recommend it.
>>>Superuser - NOT an option, not even working
Do Kindly note, some Root apps are not compatible with 4.3. So you may get weird errors. Others like Nandroid Manager have their own limitations on Root access.
>>> YES sir. Fully understood
P.S. - Your Current Post Count is 1. I did respond right ?
>>> call me up when you want a beer... or couple shots of the good sh****

@mrbackdoor
I don't have the ATT S3 Let alone the leaked Rom so can't comment. I hate TouchWiz anyway. I don't want to comment on the rules. They are there for a reason. Yes they may be an irritant but they keep Noobs away. You my dear friend is a Newb. There's a difference.
Whoever asked you to wipe the same partition 3 times needs to get their head examined. But then I am jumping ahead without knowing full circumstances. So if you don't mind, show me the thread link.
Are you trying to get the Leaked ATT Rom with a working Root ?
Now you too sir, have been guilty as well. I need to have full problem statement, which I am sorry I have not got as yet. So can you kindly explain what precisely are you trying to do and where does SuperSU come into play ?

Ok, first, please don't assume we are all jerks who are going to belittle you or treat you horribly and then ban you from OUR playground. I personally felt it a little insulting that your first post, coming to us for help, was so defensive and presumptuous.
Yes, we want you to do as much on your own as you can. No, most of us do not consider a low post count an indicator of idiocy. We might, however, judge how much we want to help depending on the quality of your post, or any other OP by anyone. If you do your best to find your own answers, and post clearly and respectfully, it'll show.
And there absolutely are reasons for all the rules here, and no one wants to hear anyone complain about them. (And if you haven't actually read them, please do so). The 10 post rule is to prevent spammers and bots from being able to post in the most important sections. And it's just 10 posts...see you're already on your way!
So if you'd care to try starting over on a better note, here are my points regarding your issues.
There is no real benefit to formatting something more than once. This is something that apparently began with some old device where the recovery wouldn't always format correctly. So people got in the habit of wiping several times rather than the king after each time. They then spread out across xda and push this practice like gospel sometimes, even though it gives no benefit and imo shortens the life of the device. I have tried to point out to folks this is not necessary, but gave up long ago! To each his own.
Enewman found a bit of a workaround for the su issues. It's not perfect but does seem to help a little.
Find these files
/etc/install-recovery.sh
/etc/init.d/dameonsu (or similar named script)
Find this line
/system/xbin/daemonsu --auto-daemon &
Delete --auto
Reboot
Hopefully that helps. And fyi, I'm going by memory, but am pretty sure I've been fairly accurate.
But also keep in mind that it's a combo of things, you do also need the insecure kernel. And Knox is still gonna screw with it if it's not been removed.
Also, try to remember, all of this stuff is brand new to all of us. Do not expect miracles, it takes time to relearn everything for everyone. But if it's really that bad, then consider going back to an older Rom for now.
These are after all leaked builds and should not be expected to be fully functional and bug free.
Sent from my SGH-T999 using Tapatalk

Dr. and Perseus
To you both, thank you, thank you and thank you. It would have been more appropriate on the General thread. Anyhow:
Perseus
If needed, I can point you to the threads. You are kind. I do appreciate that.
Dr.
I think you know exactly what I was talking about. So to you I do apology if my post is offended. In fact, to anyone who do feel the same. My bad.
please don't assume we are all jerks who are going to belittle you or treat you horribly and then ban you from OUR playground. I personally felt it a little insulting that your first post, coming to us for help, was so defensive and presumptuous.
>>>No Sir, no way in any shapes or forms I do assume people are jerks. Like I stated before, I was just venting on the fact that the rule cripples members ability to contribute and alienates them as well.
And there absolutely are reasons for all the rules here, and no one wants to hear anyone complain about them. (And if you haven't actually read them, please do so). The 10 post rule is to prevent spammers and bots from being able to post in the most important sections. And it's just 10 posts...see you're already on your way!
>>> Understood. Complain is absolutely not my thing. If there is a way to monitor users' footprints, you will find out that I have been here for a while, and it just not my style to complain or ask unless I have read just about anything posted.
So if you'd care to try starting over on a better note, here are my points regarding your issues.
>>> Of course.
There is no real benefit to formatting something more than once.
>>> Got it. Now's that is at the core. That's exactly what I was looking for. Instead banging my head trying to understand how partitions are being formatted and the file system that is basically associated to the NIX for a long time . Basically what I posted is the workaround that I use for now.
Hopefully that helps. And fyi, I'm going by memory, but am pretty sure I've been fairly accurate.
>>> Correct.
But also keep in mind that it's a combo of things, you do also need the insecure kernel.
>>> Appreciate your time Dr.
Statement below is my initial love your developers. That has not changed. Just "kang" members that I do find .... well.... you got my drift.
"I do appreciate every single one of the developers who spends countless hours to make the word "FREE" as free as possible."
Whenever you two do find your way to America Finest City... ring me up. A few rounds on me, if not all.
Again, thanks.

mrbackdoor said:
you will find out that I have been here for a while, and it just not my style to complain or ask unless I have read just about anything posted.
Whenever you two do find your way to America Finest City... ring me up. A few rounds on me, if not all.
Click to expand...
Click to collapse
Actually your join date of May '11 is the first thing I noticed. Pretty big time Reading on your part if you didn't ask before.
I am afraid we are still missing the problem you posted for aren't we ? Or what steps Doc suggested about the leak solved your problem ?

I'm on the app most of the time, so I can't readily see post counts, join dates, junior/senior member status, etc. But anyway, thanks for the reply op. I lurked around the forums for about a year before my first post, reading and learning all I could, so I can appreciate that you seem to have done so as well!
I was slightly off earlier, when you find those files, change this:
/system/xbin/daemonsu --auto-daemon &
To this:
/system/xbin/daemonsu --daemon &
Had to go look it up again. Sorry bout that!
@Perseus71
I'm pretty sure his main issue was that root wouldn't always work. After a little while sometimes root apps will lose their root access, which can be annoying, obviously! Some have just resorted to opening and closing the app a bunch of times till it regained root.
If I'm not mistaken it's due to seLinux blocking root. And by removing auto from the script, it forces the daemon to run persistently, as opposed to just when it's called, thereby helping to retain root access.
Another workaround I read somewhere was to tell SuperSU to ignore the apps permissions, or something like that. Not positive on what they meant right now, I'll have to try and find it again to be sure.
The other part of this is the insecure kernel. This will set seLinux status from enforcing to permissive. You may have to reboot or even reflash the kernel if it doesn't change from what I hear. I've not seen this myself though.
And then there's Knox. If it's not removed it can also cause problems with root access.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
@Perseus71
I'm pretty sure his main issue was that root wouldn't always work. After a little while sometimes root apps will lose their root access, which can be annoying, obviously! Some have just resorted to opening and closing the app a bunch of times till it regained root.
If I'm not mistaken it's due to seLinux blocking root. And by removing auto from the script, it forces the daemon to run persistently, as opposed to just when it's called, thereby helping to retain root access.
Another workaround I read somewhere was to tell SuperSU to ignore the apps permissions, or something like that. Not positive on what they meant right now, I'll have to try and find it again to be sure.
The other part of this is the insecure kernel. This will set seLinux status from enforcing to permissive. You may have to reboot or even reflash the kernel if it doesn't change from what I hear. I've not seen this myself though.
And then there's Knox. If it's not removed it can also cause problems with root access.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Oh I see. Honestly on my 4.3.1 rom that I had, I never experienced this problem. Possible its related to the leaked Rom's implementation of SELINUX?

I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers. The developers do they developing, and we do modifications to make things how we want them and hopefully others enjoy it too, that's all.
To OP, we're aware this SuperSU problem was annoying, we were one of the first few dealing with non-stop before bringing the leak from AT&T and debloating it over here.
enewman17 and his infinite knowledge did some poking around in the files and found a way to make root more persistent, albeit this is a leak, and we have Samsung KNOXing at our door. Things are bound to be broken, and especially because myself and others working on the leak are not professional Android developers nor do we ever claim to be, more like hobbyists who try to learn on their own by reading, or their own personal knowledge of NIX' and shell scripting.
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder.

All
Dr. has it right about the issue (I'm pretty sure his main issue was that root wouldn't always work.). I can work around it. No biggie. Will try the recommended method.
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers.
>>> Sir, I am not angry. I did explained couple times on previous posts. I just find certain rules and their enforcers hinder members' contributions. Whether that is just saying thanks or report something back. .The process in my opinion alienates the excitement of new members who are willing to do what it takes in hope to return something back. And so I did vent about it, Probably on the wrong forum. And I did apologize. If you want we can table this offline to show you what I meant.
nor do we ever claim to be
>>> Nor did I
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder
>>> I wouldn't doubt you. I've seen your work.
>>> The point is not about developers, contributors, members. Just rules and the re-reinforcement. I personally believe any voice is constructive and beneficial. I am not a NIX person, but I do find the creation of the linux kernel and its distributions since then fascinating. Awesome technologies have been built due to the collaboration of community sharing and giving back. I am almost certain xda was also created on the same principle.

mrbackdoor said:
All
Dr. has it right about the issue (I'm pretty sure his main issue was that root wouldn't always work.). I can work around it. No biggie. Will try the recommended method.
I have got no idea at all what you are so angry about, if it's kangers like myself well we never claimed to be true developers.
>>> Sir, I am not angry. I did explained couple times on previous posts. I just find certain rules and their enforcers hinder members' contributions. Whether that is just saying thanks or report something back. .The process in my opinion alienates the excitement of new members who are willing to do what it takes in hope to return something back. And so I did vent about it, Probably on the wrong forum. And I did apologize. If you want we can table this offline to show you what I meant.
nor do we ever claim to be
>>> Nor did I
Rest assured, we're all doing what we can to find workarounds, and make the transition from 4.1.2 to 4.3 as painless as possible because believe me, it is painful. The SDcard structure lining up with the AOSP file structure change from 4.2+, KNOX, SELinux, things just got a bit harder
>>> I wouldn't doubt you. I've seen your work.
>>> The point is not about developers, contributors, members. Just rules and the re-reinforcement. I personally believe any voice is constructive and beneficial. I am not a NIX person, but I do find the creation of the linux kernel and its distributions since then fascinating. Awesome technologies have been built due to the collaboration of community sharing and giving back. I am almost certain xda was also created on the same principle.
Click to expand...
Click to collapse
Glad to know we could be of assistance. Glad to clear that up with you. Feel free to post more, don't be such a lurker!