Related
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)
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.
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
mkanet said:
I dont see a lot of posts about this. But, there is a very annoying bug after the update; where if I press the Home Button to wake the screen, it will sometimes launch the task manager about a second later. I've seen sporadic posts about this for Tmobile as well as Sprint for JB 4.1.2 update; but nobody seems to have a solution.
I guess it's possible that some people dont think it's annoying enough to post; or, it's a possiblility it only affects people who have the factory rooted update installed.
I'm hoping someone smarter than me has already figured out a way to circumvent this very annoying behavior. What makes it really bad is that it only sometimes happens.
PS: The only carrier that doesn't seem to have this issue after the 4.1.2 update is ATT. My guess is they caught this bug before pushing it to all their customers.
Click to expand...
Click to collapse
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
dwitherell said:
I'm going to bet that is you disable your lockscreen you'll see this behavior just about every time. I'm fairly certain I tracked down at least one way to circumvent this behavior - check out this post for some info on it. The take home - my approach requires a wee bit of smali hacking, and everything that utilizing such a solution entails...
Click to expand...
Click to collapse
My annoying fix...
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
I forgot to mention that lock screen prevents this bug from happenening. I'm guessing that's why not everyone has complained about the issue.. and why the bug somehow sneaked passed beta testing of 4.1.2. I would think this changed behavior was a new "feature" as horrible as it is, but it looks like it dad unintentional since its not consistent behavior.
I'm hoping that a kind android developer who also can't stand this problem, Kay offer a small script or app for rooted user to patch this problem.
mrtolles said:
I have been plagued by this since the update as well. I have tried factory resets and uninstall programs one by one. Nothing worked. Today I decided to try removing my lock screen pin, just used the swipe to unlock. That did not work. Then it came to me...
I set back up my pin to unlock, and switched the setting "Lock automatically" to Immediately instead of having a delay that I love. That "worked" as in it no longer goes to recent apps. But now I have to chose to have a pin to unlock it every time my screen turns off or remove security or deal with the recent apps issue. Any way you choose it's an extra annoying step to unlock.
I'd like to hear if anyone else has found any other solution.
Edit.... I have tried every lock option and as long as set to lock immediately, it will eliminate the problem. And the same with setting any delay, with any lock option it will result in the recent apps.
Click to expand...
Click to collapse
mkanet said:
Dwitherell, thank you so much for responding. I was even considering on reverting back to 4.1.1 because of this. I don't use any kind password or pattern lock.
Forgive my ignorance, but the post you pointed me to locks like its on a Jedi ROM. I don't even see any specific references to this issue. What is this fix for specifically? If it is for sure going to restore normal behavior, i guess i could try to do this hack.
If this issue is as wide spread as i think it is, is there any chance you could make a tiny root app that fixes the problem or some way of automating a fix for not so technical people? How wide spread is this issue? Thanks a million for your help.
Click to expand...
Click to collapse
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
You did it! Your fix works perfectly! The bug is gone! ...like the bug was never there. My understanding is the fix prevents the phone from stupidly trying to launch the task manager when the screen wakes by the home button. I also donated for you time and effort. Thanks a million.
dwitherell said:
It was posted in a Jedi thread, but only because that is where I noticed it was mentioned. The context outside that single post was someone stating the same observation as you, my responding saying that I was also annoyed by it, with a later edit saying I may have come up with a workaround for it, and their response of "tell me more". As far as automating a fix or creating an app or the like - that is well beyond my paygrade unfortunately. What are you running? If you are interested you could PM me - all I need is your android.policy.jar (or to know what you are currently running) and I can try to get a fix together for you given some other conditions (i.e. have a custom recovery installed so you can flash things). It seems to have fixed it on my end, but I would be very interested in getting some others to test
Click to expand...
Click to collapse
No, thank you for making me learn how to put an odexed mod together and testing it for me!
So this fix will work for anyone running a stock odexed version of 4.1.2 UVBMB4 - you just need to be rooted, and having a custom recovery would be nice so you could flash it but you could also just copy the files over. That being said - would this be worthwhile to post?
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
mkanet said:
I wish i had know i could just copy the files over.. that's actually less convoluted process than depending on a script. I thought the reason you made a patch via flashing is because the system files were locked/open by the system. Anyway, i am extremely thankful for this'll as there is no other way to fix the bug without adding extra steps to wake the screen.
You should definitely share both odexed and deodexed patches with others. I personally don't know how i could tollerate that bug for much longer. I'm sure there are others who don't use the lock screen. Plus, this would give a chance for others to appreciate your work by dontating for your time and effort.
Click to expand...
Click to collapse
The flashable zip is just one method to get the files where they need to go. Literally all it does is overwrite the 2 files in /system/framework by moving the 2 files over from the zip - but there are definitely other ways to do such things. Some are more comfortable with this route, others are more comfortable w/ getting /system to be rw and move the files manually.
I'll likely post this at some point in the next few days
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
Glad to hear
Is it possible that my phone isn't affected? If its a 4.1.2 bug, it should be in all phones with same version right?
This is not happening to my phone. Whether I have lock screen activated or not. I'm rooted but running stock ROM and I have Nova launcher installed if thats even important.
It's not all notes.
Sent from my SGH-T889 using xda premium
kabuk1 said:
I don't mean to revive a dead thread or anything, but this bug has been driving me CRAZY & the smali hacking worked perfectly for me, thank you!!!
FYI, I'm willing to help people out with this as well. If anyone wants this done but doesn't wanna mess with the java stuff, PM me & send me your android.policy.jar and I'll hack it for you
Click to expand...
Click to collapse
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Yes you'll need to be rooted unfortunately - sorry
wesblogger said:
is this offer still good? i'm was experiencing the same problem and it was so annoying that the only solution i found was to revert back to 4.1.1. I'm currently running t889uvall4.
also, my phone is not rooted. will the fix dwitherell came up w/ work? or do i really have to root my phone?
Click to expand...
Click to collapse
Absolutely. just PM me. Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
kabuk1 said:
...Yeah, you have to be rooted but that's easy to do & worth it for this hack & all the other things you can do once you're rooted.
Click to expand...
Click to collapse
^^^ THIS - a thousand times over
Jedi Master 16 or Tweaked 2.4? Why?
Thanks
Please.close
Sent from my SGH-T889 using Tapatalk 4 Beta
janjannsen99 said:
Please.close
Sent from my SGH-T889 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I had to delete the words I want to tell you like 3 times...
What are you talking about? How can you be so disrespectful?
I Have the tweaked 2.1 version now and I'm not satisfied, I want to know before leaving it hearing from others experiences...
Arturofm2 said:
I had to delete the words I want to tell you like 3 times...
What are you talking about? How can you be so disrespectful?
I Have the tweaked 2.1 version now and I'm not satisfied, I want to know before leaving it hearing from others experiences...
Click to expand...
Click to collapse
Just flash it and find out. Someone may sing praises about one rom but your experience may be different. Then there is personal taste. Something only you can attest to. Just give it a whirl. I was never a huge fan of jedi. Great work, just not for me. You might feel different though.
Sent from my SGH-T889 using xda premium
No disrespect to the OP - but threads like these tend to be dangerous and often times lead to work for the moderators when things get out of hand. This doesn't always happen, but if I were a betting man and knew nothing more than the first post my money would be on it being trouble.
The reasons for this are what EVO-lution of Man stated - especially between those two it's a matter of personal taste (in other words both are fully functioning daily-driver type material in terms of the basic phone functionality and what not). When people start stating opinions, those opinions can be challenged, then a felt need for defending those opinions takes over and things get messy - usually anyway. It's all about what works best for you, and the only way to really know is to try and see.
That being said - if there is something in particular you are unsatisfied with in the current setup another option would be contacting those responsible for it (hi ) and see if anything can be done.
dwitherell said:
No disrespect to the OP - but threads like these tend to be dangerous and often times lead to work for the moderators when things get out of hand. This doesn't always happen, but if I were a betting man and knew nothing more than the first post my money would be on it being trouble.
The reasons for this are what EVO-lution of Man stated - especially between those two it's a matter of personal taste (in other words both are fully functioning daily-driver type material in terms of the basic phone functionality and what not). When people start stating opinions, those opinions can be challenged, then a felt need for defending those opinions takes over and things get messy - usually anyway. It's all about what works best for you, and the only way to really know is to try and see.
That being said - if there is something in particular you are unsatisfied with in the current setup another option would be contacting those responsible for it (hi ) and see if anything can be done.
Click to expand...
Click to collapse
I didn't mean unsatisfied, I wrote it because I was mad with that guy at the beginning, anyways.. It is not that, what I was trying to say is that I see that jedi has more features, more new things. At least that's my impression, I might be wrong, any ways... I'm installing the tweaked 2.4 version now because it is the one I've always used.
I want to format my phone and now I have to figure out how to install it with the new system, it would be easier with a simple installer (I'm suggesting ).
By the way, I have an extra camera, how can I delete the new one? I'm good with the old one . (I'm saying the app u use to take pics)
Oh, I forgot, I'm not demanding, this is free! and it's your work, and I'm great full to you for the time invested thanks
All right end of the post, it was a stupid idea.
Arturofm2 said:
I didn't mean unsatisfied, I wrote it because I was mad with that guy at the beginning, anyways.. It is not that, what I was trying to say is that I see that jedi has more features, more new things. At least that's my impression, I might be wrong, any ways... I'm installing the tweaked 2.4 version now because it is the one I've always used.
I want to format my phone and now I have to figure out how to install it with the new system, it would be easier with a simple installer (I'm suggesting ).
By the way, I have an extra camera, how can I delete the new one? I'm good with the old one . (I'm saying the app u use to take pics)
Oh, I forgot, I'm not demanding, this is free! and it's your work, and I'm great full to you for the time invested thanks
All right end of the post, it was a stupid idea.
Click to expand...
Click to collapse
No worries. You very well might be right on the feature bit - Jedi definitely has features included that are not in tweaked (his kernel work, xposed framework, etc.), but there are likely a few the other way as well - as it should be as it would be a bit redundant if they were too similar That's not to say some of the features are exclusive to one or the other (using the above examples, ptmr posts his kernel separately and xposed is also something that can be installed separately) - just prepackaged.
I'm not sure whether either of these roms lack much in personalization, but I'll take the hit on the installer bit. I still like the idea, but it's a little different and that's not for everyone. That being said I redid much of the OP for 2.4 in order to address this, so hopefully the install process is a bit simpler looking now. And thanks to Alexea - there are a few more theme options around. I am in no way a themer, so one weakness on the tweaked side is definitely my reliance on others to take up the task and share their work. This does not seem to be a weakness on the Jedi side.
I take it you installed the aosp camera? That's the only way I could see you having two at least - if you want to get rid of the aosp one you can use the modificatinator. If you want to get rid of the samsung one you'll want to delete/freeze SamsungCamera.apk in /system/app.
Feel free to PM me if you have any other thoughts/questions/etc. - and I still think you should at least try Jedi. Personally I rather enjoy flashing things to try them out and see what they are like - and you very well may like it enough to stick with it. Of those who run stock modified roms, I think most use Jedi so it's definitely worth a look.
Arturofm2 said:
I didn't mean unsatisfied, I wrote it because I was mad with that guy at the beginning, anyways.. It is not that, what I was trying to say is that I see that jedi has more features, more new things. At least that's my impression, I might be wrong, any ways... I'm installing the tweaked 2.4 version now because it is the one I've always used.
I want to format my phone and now I have to figure out how to install it with the new system, it would be easier with a simple installer (I'm suggesting ).
By the way, I have an extra camera, how can I delete the new one? I'm good with the old one . (I'm saying the app u use to take pics)
Oh, I forgot, I'm not demanding, this is free! and it's your work, and I'm great full to you for the time invested thanks
All right end of the post, it was a stupid idea.
Click to expand...
Click to collapse
A little to. Go to settings, tsmparts. Any feature you could possibly imagine is there. Tweaked is close to AOKP with all the options
Sent from my SGH-T889 using xda app-developers app
Well I tried tweaked 2.4 for a day and it was OK but I did not really get into it. Was going away on trip and needed something solid that I have used before. So I loaded Jedi master 16 and had so many issue with memory swap. Lost all. Oh well. Just look at last few pages of each and u can see what if any issues are in the rom. Now I gonna try tweaked but need to get hold of chef as to changing my kernel cause it did not do deep sleep at all. Maybe I missed something but need to try a diff kernel.
BACARDILIMON said:
Well I tried tweaked 2.4 for a day and it was OK but I did not really get into it. Was going away on trip and needed something solid that I have used before. So I loaded Jedi master 16 and had so many issue with memory swap. Lost all. Oh well. Just look at last few pages of each and u can see what if any issues are in the rom. Now I gonna try tweaked but need to get hold of chef as to changing my kernel cause it did not do deep sleep at all. Maybe I missed something but need to try a diff kernel.
Click to expand...
Click to collapse
Not sure if we ever wanted to stay on topic, but since we are diverting...
Sorry to hear tweaked didn't strike your fancy - what kernel did you pick? Safest bet is go with stock - not the sexy choice I know but it won't do you wrong in terms of stability.
dwitherell said:
Not sure if we ever wanted to stay on topic, but since we are diverting...
Sorry to hear tweaked didn't strike your fancy - what kernel did you pick? Safest bet is go with stock - not the sexy choice I know but it won't do you wrong in terms of stability.
Click to expand...
Click to collapse
+1 Im very happy with stock kernel running 2.4 Ive always seem to have very minor issues with the "sexy" choice....
I've been running the jedi roms since I've got my note and just switched to tweaked in the last few days. I really like them both a lot but I'm definitely liking tweaked a little more. The whole star wars thing was getting a little old for my taste but it was still a great rom. It's all gonna come down to personal preferences and that's about all there is to it.
Sent from my SGH-T889 using xda premium
Tweaked is 100x better I tried all the TW roms and Tweaked and the S4 Themed one are the best
Sent from my SGH-T889 using xda app-developers app
dwitherell said:
Not sure if we ever wanted to stay on topic, but since we are diverting...
Sorry to hear tweaked didn't strike your fancy - what kernel did you pick? Safest bet is go with stock - not the sexy choice I know but it won't do you wrong in terms of stability.
Click to expand...
Click to collapse
I believe I did go with stock. I went from a full charge to 20% in about 10 hrs. Just need more battery life.
BACARDILIMON said:
I believe I did go with stock. I went from a full charge to 20% in about 10 hrs. Just need more battery life.
Click to expand...
Click to collapse
Oh wow - well the more telling stat on that one would be the screen on time. That's a pretty harsh drop if you weren't using your phone, but if the screen was on for half that time then it's much less surprising. Assuming it was off more than on, there have been a few google apps (mostly maps I think) that have been reported to cause some wake lock issues which could be at the root of it - this would be much more the case if the phone was not deep sleeping (except if you enabled the zerowakelag bit).
dwitherell said:
Oh wow - well the more telling stat on that one would be the screen on time. That's a pretty harsh drop if you weren't using your phone, but if the screen was on for half that time then it's much less surprising. Assuming it was off more than on, there have been a few google apps (mostly maps I think) that have been reported to cause some wake lock issues which could be at the root of it - this would be much more the case if the phone was not deep sleeping (except if you enabled the zerowakelag bit).
Click to expand...
Click to collapse
I gonna try it again with stock kernel and give it a few days and see from that point.
Tweaked is killing it for me
dwitherell never mind bro... I installed the last version of Tweaked and it's running perfect, oh now that I remember, there is something I'd like you to try to fix if you can. When you hack the volume and you make a call, the other person can hear his voice twice, like an echo. And the volume hack is very important.
Respect to the installer, I did the standard when it first came out on 2.1 I think, and I didn't like it that way (but it was not hard at all... my sister could do it and she has 14), then for the 2.4 I used the simple version of the installer and I liked it. So, forget what I said about the installer. Besides... you can modify everything later.
Oh... this was my question at the beginning, if I delete the AOSP camera, I will delete the gallery as well, and I really like the app for the gallery (I don't use the stock one). Is there any way I can delete only the camera?
So... 2 things:
Camera and volume hack
That's it, and they are not even issues, they work great. Thanks for everything :good:
Arturofm2 said:
dwitherell never mind bro... I installed the last version of Tweaked and it's running perfect, oh now that I remember, there is something I'd like you to try to fix if you can. When you hack the volume and you make a call, the other person can hear his voice twice, like an echo. And the volume hack is very important.
Respect to the installer, I did the standard when it first came out on 2.1 I think, and I didn't like it that way (but it was not hard at all... my sister could do it and she has 14), then for the 2.4 I used the simple version of the installer and I liked it. So, forget what I said about the installer. Besides... you can modify everything later.
Oh... this was my question at the beginning, if I delete the AOSP camera, I will delete the gallery as well, and I really like the app for the gallery (I don't use the stock one). Is there any way I can delete only the camera?
So... 2 things:
Camera and volume hack
That's it, and they are not even issues, they work great. Thanks for everything :good:
Click to expand...
Click to collapse
No worries
I've heard the echo bit regarding the volume hack. I'll have to add that to the list of things to revisit to see if I can chase down what edit in particular is causing the issue. Yay trial and error
Unfortunately w/ the aosp camera/gallery - they are both contained within one single apk. Unless there is a sort of fanciness out there I am not aware of (a real possibility granted) I don't think you can have one without the other. I'm not sure if they come up as separate entities in something like titanium backup - but if they do perhaps you could freeze the camera part and see what happens w/ the gallery end? Just a thought
dwitherell said:
No worries
I've heard the echo bit regarding the volume hack. I'll have to add that to the list of things to revisit to see if I can chase down what edit in particular is causing the issue. Yay trial and error
Unfortunately w/ the aosp camera/gallery - they are both contained within one single apk. Unless there is a sort of fanciness out there I am not aware of (a real possibility granted) I don't think you can have one without the other. I'm not sure if they come up as separate entities in something like titanium backup - but if they do perhaps you could freeze the camera part and see what happens w/ the gallery end? Just a thought
Click to expand...
Click to collapse
I'll try that
This device may be a few years old, but its still great. Support for it has almost disappeared, but there are still people out there like me that are on this device that can't/won't upgrade for one reason or another. Sure, Superstock is a great ROM, but lollipop is outdated, and having the features of custom ROMS but on a newer base would be freaking great. I am right?
I may have missed them, but as far as I could find on XDA, I couldnt find any nougat custom ROMs for this device. I would super excited to petition for one of the awesome developers out there to make a new ROM, even if it might be the last for this phone. Or maybe there is one, and I have just been much to dense to see it. Let this thread be for all posts related to the development of a custom Nougat rom, or sharing of one that already exists. Thanks everyone for reading and participating! :laugh:
EDIT: SM-G928T is the model number, just in case it isn't implied
"petition for one of the awesome developers out there to make a new ROM"
Wow... no need to do that buddy..
I'll save you the headache, hassle and lynching..
Check this out.. https://forum.xda-developers.com/s6-edge-plus
Heads up, read thru the thread carefully, many of these ROMs will require the "T-Mobile audio fix" to get in call audio, that is if you have the T-Mobile variant (G928T). You can search for the fix..
We can run Note 5 ROMs too, check out the TMo N5 or the Int'l forums, like I mentioned, above.
Talysdaddy said:
"petition for one of the awesome developers out there to make a new ROM"
Wow... no need to do that buddy..
I'll save you the headache, hassle and lynching..
Check this out.. https://forum.xda-developers.com/s6-edge-plus
Heads up, read thru the thread carefully, many of these ROMs will require the "T-Mobile audio fix" to get in call audio, that is if you have the T-Mobile variant (G928T). You can search for the fix..
We can run Note 5 ROMs too, check out the TMo N5 or the Int'l forums, like I mentioned, above.
Click to expand...
Click to collapse
Thanks for the response. I had no idea we could run international ROMs on variant devices. I am having the issue you mentioned, though, with the call audio. So far ive tried two roms, flashed the fix, without any change. Ideas as to how i might get that working?
There is a audio fix on the T mobile Galaxy Note 5 page, it worked for me using Dr Ketan's rom
N
LEGONIKES said:
Thanks for the response. I had no idea we could run international ROMs on variant devices. I am having the issue you mentioned, though, with the call audio. So far ive tried two roms, flashed the fix, without any change. Ideas as to how i might get that working?
Click to expand...
Click to collapse
I do know that theres a few different "audio fixes" available. Im thinking they differ bcuz of the Android version? Just a guess, but what I'll do, is, I'll use only Roms that another 928T user already reported their success using it. I dont want to waste my time and effort being the guinea pig and then, for it not to work. Usually, whomever confirmed compatibility, will also list anything thats needed additionally to get it running, like the audio fix, along with link(s) to get it. If it doesn't work, they'll usually state the issues they found. Someone else's issue with it, might not be relevant to another person so they may decide to run it.
The best way to do this is to simply go to the OP of the Rom thread, in the upper right corner, you'll see a "search" option/box, (depending on browser or app, might see 3 dots instead, its a drop down list) click on it and enter our phone model, "928T, 928-T" or "T-Mobile, Tmobile, TMO " I try to cover the different variations, others here use to identify the phone. Seems like the search function, searches only the exact characters, as entered in the box, doubting it can identify and include similar known ones, so rather be thorough and not miss something. It searches your entry only in that particular thread and lists the results.
If you're braver than I, and dont mind going where no other TMO'rs have gone before and found only the in call audio isnt working, then its likely, flashing the audio fix is all thats needed.
The best way to solve this is, again, with a simple search. This time I'd recommend, a broader search using Google's search engine, type "XDA T-Mobile audio fix," bcuz this will search all XDA forums, more importantly, both S6 E+ and N5, carrier and int'l forums all at once. Then just go down the list if results, making sure that youre in either of the 4 forums, above, locating the download. Last I checked there was 3 or so fixes available, this was many months ago though. Anyway, having more isnt a bad thing, less would mean needing to go back and finding the one you missed. Once you have them, flash each one seperately, in recovery, reboot, confirm whether you're issue is fixed or not. If not, then continue these steps till it works. Flashing the audio fix won't mess your phone up. No need to reset, clear cache or anything of the sort, between each audio fix, just flash only the audio fix and rebooting is necessary. If you want to be organized, you can cross reference the dates of each audio fix, with the current firmware available at the time. That way you can flash any Rom you desire and will already have the fix ready.
Wow, my apologies, talk about rambling on about nothing more than finding correct file, flash your device, confirm its fixed, if not then repeat till its fixed. If no fix is found then, Rom isnt compatible...
Sorry, one last thing, Im sure that you'll help many others like yourself, if you had minute to post your experience with whichever Rom(s), you chose.
For example, "Rom works great, needed this (link to audio fix) for in call audio on the TMO variant"
It seems like you're the first 928T to try the Rom you have so,
report your experience, posts are permanent, its there forever, for any curious new comers, you'd be their hero! It'd most def get a "thx" from me.. :good:
Any updates on your experience here?
Zulmonster said:
Any updates on your experience here?
Click to expand...
Click to collapse
Found a few ROMs that work without fixes and run nougat. Khongloi's s8 port works and has some of the best features I've ever had on this phone, but is heavy on the battery. AndroidSword's NFuel XL runs fast and light, but doesn't have edge features. The original NFuel also has full support for 928T, but I haven't tried it yet. I'm also working on my own custom ROM now since every ROM I tried was missing something I wanted.
LEGONIKES said:
Found a few ROMs that work without fixes and run nougat. Khongloi's s8 port works and has some of the best features I've ever had on this phone, but is heavy on the battery. AndroidSword's NFuel XL runs fast and light, but doesn't have edge features. The original NFuel also has full support for 928T, but I haven't tried it yet. I'm also working on my own custom ROM now since every ROM I tried was missing something I wanted.
Click to expand...
Click to collapse
Thanks for the info. My S8 has kicked the bucket, and so I'm back on my S6 for the time being and want to give it a bit of a refresh. I'll look up those NFUEL ROMs.
Zulmonster said:
Thanks for the info. My S8 has kicked the bucket, and so I'm back on my S6 for the time being and want to give it a bit of a refresh. I'll look up those NFUEL ROMs.
Click to expand...
Click to collapse
Nearly lost my phone today and realized find my mobile does not work on NFuel XL. Would not recommend if your one to lose you phone like me.
Zulmonster said:
Thanks for the info. My S8 has kicked the bucket, and so I'm back on my S6 for the time being and want to give it a bit of a refresh. I'll look up those NFUEL ROMs.
Click to expand...
Click to collapse
I've just finished cooking a second version of my custom rom. Haven't had any issues so far. It's Called TrueStockN.
Here's a list of ROMs I was able to get working for the G928T:
Khongloi's s8 Port
Nemesis s7 Port
N-Fuel
TrueStockN
These are just Nougat roms I that worked for me off the bat, no additional audio fix required. Of course, there may be more, but these are the ones I know of and have used extensively.