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&A for [ROM][D855][20A][Lollipop] --|||..:: ChupaChups Rom::..|||--
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][D855][20A][Lollipop] --|||..:: ChupaChups Rom::..|||--. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
is miniview in progress?
thxv
hi, somehow I don't see why not finish CyanogenMod first before you start other projects based on stock rom, which many people don't expect
sorry for my bad english
ermm... why not the 80° mod?
just curious, lol...
and no need to wipe or anything?
19h to chupachups
hi guys.
Sorry, new here, quick question, how would one get from 19h to this version?
getting allot of lag and i think its due to upgrading to 19h instead of installing fresh.
Sorry of the question is basic and if its answered somewhere. i had a hint around without luck.
Thanks
can you port this rom to d850?
Google Services Battery Drain
One would think with all the development in both lollipop and kitkat that this problem would have been fixed and implemented into all the new rom releases. Google Services battery drain depletes the battery preventing the phone from deep sleep and accounts for quite allot of drainage. A fix would be nice from the developers, Thanks.
@Skin1980
there are no notifications, but why my led keeps blinking?
Brave Frontier anyone?
anybody here play brave frontier? i wanted to try this rom but i'm hesitant to make the switch because in the stock kitkat rom, the game would constantly crash (even with all effects off).. Currently on AOSP it works well, but I miss the sleek look of the LG UI
new kernel
lagfree governor
http://imgur.com/hhklRZd
http://imgur.com/j6A3DcI
How did you manage to get those stats?
tehosiris said:
lagfree governor
http://imgur.com/hhklRZd
http://imgur.com/j6A3DcI
Click to expand...
Click to collapse
What kernel are you speaking of? What settings are you running (brightness, tweaks etc)? A little context would help many folks smile a little. The pictures are all fine and well, but how did you achieve that?
astrokreep said:
What kernel are you speaking of? What settings are you running (brightness, tweaks etc)? A little context would help many folks smile a little. The pictures are all fine and well, but how did you achieve that?
Click to expand...
Click to collapse
it's the new kernel, since that has the new options, decided to try lagfree first, worked well i guess
auto brigthness, wifi and location enabled all day
I see...
tehosiris said:
it's the new kernel, since that has the new options, decided to try lagfree first, worked well i guess
auto brigthness, wifi and location enabled all day
Click to expand...
Click to collapse
Sorry for all the questions, just trying to clarify for everyone else. You mean this one?
http://forum.xda-developers.com/lg-g3/orig-development/kernel-chupachups-kernel-t2943339
And how are you finding this kernel?
astrokreep said:
Sorry for all the questions, just trying to clarify for everyone else. You mean this one?
http://forum.xda-developers.com/lg-g3/orig-development/kernel-chupachups-kernel-t2943339
And how are you finding this kernel?
Click to expand...
Click to collapse
yes thats the one,
it's just as good as the one before to be honest, haven't really noticed anything spectacular
although i never had issues before, so i can't tell if it fixes anything or not hehe
Hi,
First of all, thank you for your hard work.
Could you please advise, if it's possible to customize this ROM somehow? I would love to:
1) Remove all lg software
2) Remove stock browser
3) Replace stock dialer with something else
4) Replace messaging app with let's say Textra or something similar
5) Have only Core Google Apps (something like PA-Gaps Nano)
Sorry for noob questions.
Thank you very much,
Yuriy
I dirty flashed this and ever since music from Google Play and Soundcloud just refuses to play. I can play music locally in other apps but even local music won't play in Googe Play Music. Has anyone else had this problem?
Banker Z Concern or False Positive?
Avast alerted me as well. Seems like it was able to remove it and everything was working before it was detected and still is after it was removed. Could be a false positive since a lot of people are reporting it now but better to be safe for now and let Avast and them go to work.
Thank you very much @Skin1980 for the great work! I'm having a little bug about notification LED. I'm having blinking white LED like Whatsapp default LED notification even if I haven't got any new message. I flashed the new kernel and using the Lollipop Theme of Kickoff.
Knock code is buggy
I don't know if someone else is having problem with the knock code feature as well. I found that some times the knock code feature doesn't work properly. While the screen is off and after knocking the proper code the screen won't wake up, not even after double tapping on it. Even the LED that turns on when you introduce a wrong code is not turning on, it is like it was disable. I have to press the power button, wake up the screen and then introduce the code.
I have a quick circle case and a smartwatch connected as a trusted device to use the new Smart lock feature that comes with Lollipop. I'm not looking for a solution, just pointing out the bug, I'll flash the LG stock image as soon as it's realeased in my country.
By the way, none of the quick circle apps work. Only the ones that comes with the phone by stock. You might want to check that up.
Thanks for all your work, it is awesome to have a developer community like this one. =)
Anyone having issues on Feedly after moving to this rom or any other Lollipop rom ? When scrolling the sources list everything gets blank, then reappears, like it's some rendering problem.