Database Users

Anyone bricked from iMilka's AOSP/CM9?

Entropy recently stated that using any leaked build was dangerous.
I have used every single version of AOSP and CM9 from the beginning to current, jumping between and back and forth from GB many times with no issues.
I have also never SEEN a report of anyone bricking (when properly) flashing around with these roms.
Just curious if a case actually exists.

crawlgsx said:
Entropy recently stated that using any leaked build was dangerous.
I have used every single version of AOSP and CM9 from the beginning to current, jumping between and back and forth from GB many times with no issues.
I have also never SEEN a report of anyone bricking (when properly) flashing around with these roms.
Just curious if a case actually exists.
Click to expand...
Click to collapse
No but there is a risk. And the question is : "Do you want to take this risk while CM9 is announce next week with a safe kernel".
I was using Imilka Cm9, and yesterday i flashed back to GB. Maybe you could wait one week and avoid flashing a hazardous repack !

I had no issues with Imikas cm9 roms, I used all 3 of them and have since flashed to a stock gingerbread as the video playback in all the ICS roms is not good enough yet compared to GB roms.
I have tried all the ICS leaks and gone back to GB with no issues, just waiting for a proper stable release of ICS with good video playback performance as I get in GB then I will stick with the Ice Cream

remixtech said:
No but there is a risk. And the question is : "Do you want to take this risk while CM9 is announce next week with a safe kernel".
I was using Imilka Cm9, and yesterday i flashed back to GB. Maybe you could wait one week and avoid flashing a hazardous repack !
Click to expand...
Click to collapse
I wasn't stating that there isn't a risk, or that anyone should chance it. Just simply that I have not heard of a single case of anyone having a problem with iMilka's releases (killing the board). Therefore my none developer point of view is that the risk must be VERY small IF said risk does truly exist with all Kernel Leak builds.
It SEEMS to me that the problem does not lie with the kernel build but the way it is scripted and executed. Hence why no one has ever had the problem with AOSP/CM9, but the problem came up with Angelom's kernel and the last Stunner build. The problems were also immediate in both cases, again where no one has ever had this problem caused by AOSP/CM9. So YES, I am sure AOSP/CM9 could have caused the problem if iMilka made whatever mistake was made by Stunner/Angelom, but I would say to me it is quite obvious he did not, and that the problem IS a mistake in the way the kernel is handled. Speculation and opinion only of course.
I have been running them since the beginning, so I am not saying I personally would have chanced it this close to offical ICS / Official CM9, but i've been running his releases for quite some time.

crawlgsx said:
Entropy recently stated that using any leaked build was dangerous.
I have used every single version of AOSP and CM9 from the beginning to current, jumping between and back and forth from GB many times with no issues.
I have also never SEEN a report of anyone bricking (when properly) flashing around with these roms.
Just curious if a case actually exists.
Click to expand...
Click to collapse
Flashed all imilka Roms from day one, and never had as much as a hiccup on any one of them.

The question is if anyone tried to restore a cwm backup ? The most of the bricks were caused by doing that task..
Sent from my GT-N7000 using xda premium

No issues here either with Midnote or TeamMid ROMS (also tried a couple of Alba versions and Stunner).
I have flashed many times and with LP5 kernel through CWMR or Mobile Odin including full wipes.
I have made nandroid backups but haven't tried to restore any, perhaps this has saved me?

Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium

dimcus said:
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Exactly the same here. Unable to format /system partition after restoring.
Odin managed to fix it tho.

jscurtu said:
The question is if anyone tried to restore a cwm backup ? The most of the bricks were caused by doing that task..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I have multiple times. CWM Backup restore works sometimes for me ICS to ICS, and fine GB to GB. ICS to GB or GB to ICS causes issues but I can easily fix them with a flash/odin/etc and still have complete access to download mode / CWM. ICS to ICS I have run in to problems such as funky root or partition issues, once again still easily fixable and still have plenty of access to the phone/flash abilities, By no means even close to a brick.
That said at this point in the game I wouldn't even consider doing a CWM restore, why even chance it!

dimcus said:
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Just to report, I experienced exactly the same.
Regards!
Sent from my GT-N7000 using xda premium

dimcus said:
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Which kernel were you on?

chill392 said:
Which kernel were you on?
Click to expand...
Click to collapse
The first leaked one - LP1.

jscurtu said:
The question is if anyone tried to restore a cwm backup ? The most of the bricks were caused by doing that task..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I think you are wrong.Bricks caused when trying to format /system
Sent from my GT-N7000 using Tapatalk

Bricks were caused by anything that tried to wipe a partition - and restoring a nandroid will first wipe a partition.
What kernel is imilka's a repack of? Maybe it's an unaffected one. I recall seeing stuff in imilka's thread saying not to use its CWM.
Without source for the leak kernels it's impossible to tell what's changed and declare one kernel "safe" and another "dangerous" - as long as some are proven dangerous they should all be considered dangerous.

afilopou said:
I think you are wrong.Bricks caused when trying to format /system
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
When restoring a backup , you usually format /system ; )...so basically yes that is correct, I only mentioned that it mostly happened while doing that task..
Sent from my GT-N7000 using xda premium

Entropy512 said:
What kernel is imilka's a repack of? Maybe it's an unaffected one. I recall seeing stuff in imilka's thread saying not to use its CWM.
Without source for the leak kernels it's impossible to tell what's changed and declare one kernel "safe" and another "dangerous" - as long as some are proven dangerous they should all be considered dangerous.
Click to expand...
Click to collapse
It was multiple different kernels, up to LP5 and LP6 even.
I understand the logic and respect your words of caution with what is most certainly from someone who has a much better understanding than I, I just feel it is the way the kernel was used/modified/implemented that caused the potential problems (by the devs), not the kernel itself. Based on the logic I provided earlier in the thread. I am not saying the problem still does not exist in the kernel, I have no idea, but it is obviously something that did not come out in many rom implementations, just those 2.

Flashed all roms from maxicet and some repack stock ICS roms. Never got any problems. Tested over 10 ICS roms... And now using maxicet's ROM as daily.

crawlgsx said:
It was multiple different kernels, up to LP5 and LP6 even.
I understand the logic and respect your words of caution with what is most certainly from someone who has a much better understanding than I, I just feel it is the way the kernel was used/modified/implemented that caused the potential problems (by the devs), not the kernel itself. Based on the logic I provided earlier in the thread. I am not saying the problem still does not exist in the kernel, I have no idea, but it is obviously something that did not come out in many rom implementations, just those 2.
Click to expand...
Click to collapse
The thing is, this has happened over multiple devices, with multiple recovery implementations, including recovery implementations that work fine with other kernel bases. The end result is the same - fried eMMC that can't even be recovered with JTAG.

Entropy512 said:
The thing is, this has happened over multiple devices, with multiple recovery implementations, including recovery implementations that work fine with other kernel bases. The end result is the same - fried eMMC that can't even be recovered with JTAG.
Click to expand...
Click to collapse
Agreed, very bad.
All I am saying is that it ONLY happened on those 2 botched kernel implementations. It is obviously SOMETHING the Dev's did with the kernel that caused this, seeing how ALL the other roms/versions clearly have not caused this. Since the result was immediate with both of those and many of us have jumped/cwm'ed/etc from MANY different Leaked kernel builds and NOT had that problem.
I am not trying to put them at blame, running any rom/dev is strictly at your own responsibility and risk, just stating that I don't think it is fair to place every leaked rom build in the same category of danger. Is there a risk, certainly, as the dev's could accidentally make said same mistake (I am not even clear if "we" know what causes it?) in a future version. That said I feel pretty confident that if the "final" versions of iMilka's roms were going to cause that issue, it would've happened by now. That is why I wanted to see if anyone had ever been bricked (fried eMMC) from them, and it seems, no.

Do you have any problem caused by the [LPY] ICS ROM?

If YES, please state how did get into the Official [LPY] ICS ROM and the problem you are experiencing.
If NO, then just please tell us your success story.
The reason why this thread exists is to, once and for all, trace the HARDBRICK that plague (?) some (?) ITCHY SGN fanatics and to pacify the fear of some of the other kids.
Don't need your opinions on why blah blah, just the scenario, OK?
Thanks

no problems now, except maybe battery but that might because we are all using it more to test it out
gonna test the battery today when i go to work, if it drops 20% in my pocket then theres a problem but last night it only dropped 5%

Does anyone know anybody that bricked te note with LPY?
I have no problems at all. All working excellent. From miui, flashed back to gingerbread then update to LPY all with mobile odin. No Cwm only everRoot.
Sent from my GT-N7000 using xda premium

No problem coming from official LC1 GB with CF-Root kernel using Mobile Odin Pro with Everoot and injections. Had no problems before factory reset in CWM nor after. I let the system rest both after the initial flash, and after the factory reset/wipe cache/wipe dalvik for about 20 minutes without touching the device.
This is my best experience on the note yet.

Alejandrissimo said:
Does anyone know anybody that bricked te note with LPY?
I have no problems at all. All working excellent. From miui, flashed back to gingerbread then update to LPY all with mobile odin. No Cwm only everRoot.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
One person has, but it is VERY questionable as to the cause of the brick. Time will tell.

No problem occurred thusfar.
I kept my Note stock, didn't want to root to give Sammy a chance...especially with the premium suite and S apps.
So used Odin v1.85..downloaded the 600mb+ file from samfirmware.com..extracted, loaded .tar file In PDA..flash and succes so far.
Good battery life..using Apex launcher but graphics seem improved, Tweakers.net did some benchmarks and conforms my feeling about this.
No trouble downloading large files, playing them and deleting.
So far nothing but good feelings about this..got bit scared by the posible brick stories but keeping it all stock seems to do the trick.
Sent from my GT-N7000 using xda premium

All good here as well . I returned to my stock rooted GB nandroid when the problems with the leaked kernels started (from Stunner, using the Abyss method without any problems). Stayed on it and then upgraded today with mobile odin and everoot (with full wipe). With that I kept root and restored my apps & data with TB. As I read a lot about bricking even with stock ICS I hesitated a bit to also flash the CF kernel. In the end I even flashed that (also using mobile odin). Went into CWM an wiped cashes to flash lidroid's 15 toggle mod. That is working fine now as well. Been using it since some hours now and no problems whatsoever! The only thing I didn't do as yet is a nandroid backup of it.
Sent from my GT-N7000 using xda premium

I am having issues with screen sensitivity.
Battery life isn't very good...
Runs a little warm...
Otherwise, I'm very happy with ICS

zkyevolved said:
I am having issues with screen sensitivity.
Battery life isn't very good...
Runs a little warm...
Otherwise, I'm very happy with ICS
Click to expand...
Click to collapse
I noticed some wonky screen sensitivity issues too. Scrolling through lists on Tapatalk 2 is a pain in the arse. Going to try touch screen booster app
I froze a lot of apps in Titanium Backup, and my battery life/heat issue went away

Itchy SGN fanatics and other kids? Calling an opinion bla bla?
Here's my bla bla: don't patronize people if you want them to contribute to your cause.
Here's my success story: flashed LPY with PC Odin, hated it, reverted back to CM9, happy again.

smooth so far 2 days now and working great battery drains a bit faster but np.

No problems here. Flashed rom and CF-Kernel using Mobile Odin Pro. Have got now a rooted ICS which works very well.
Sent from my rooted Galaxy Note using XDA Premium App

[Success]
Flashed from CM9 build#7 via Mobile Odin with everroot, inject su, inject Mobile Odin and Wipe data and cache options. Worked fine for me.
Flashed CF's CWM injected LPY kernel via Mobile Odin and that worked too.
After the whole brick panic I reverted to the original Samsung LPY kernel via Mobile Odin, no problem.
I didn't use CWM at all though given the suggestions that there may be some imcompatibility between it and the lpy kernel.

bioweb said:
Itchy SGN fanatics and other kids? Calling an opinion bla bla?
Here's my bla bla: don't patronize people if you want them to contribute to your cause.
Here's my success story: flashed LPY with PC Odin, hated it, reverted back to CM9, happy again.
Click to expand...
Click to collapse
Nobody cares... Thread asks if you had problems, not if you hated it. So we will assume it was working just fine for you.

Ok. Here's the real deal. I upgraded through Kies. No root here. DONT UPGRADE NOW:
Problems:
1. Its just as jerky as Gingerbread. Its actually even worse at times in slowness. It has a fast homescreen scroll at first and then has random pauses (almost the same). What worst is in apps when scrolling up and down on text it randomly pauses sometimes for several seconds. Also, every once in a while it does this on and off screen flashing then (not very seldom though). When it does it sucks.
2. The "fast reboot" app now crashes apps if you use them within the first 5-10 seconds after doing a reboot.
3. I'm noticing lots of compatibility issues with apps that aren't fully ics ready.
4. Samsung's version of Ics is dumbed down to almost look like gingerbread. So it runs worse and almost looks the same. I'm historically the one that notices all of the bugs because of how frequently I use multiple apps and because of the amount of apps I have on my phone. Thats why I constantly help by emailing devs pointing out bugs that 98% dont see for some reason.
5. Please dont get mad at me because I'm not a follower to give all praises to samsung and google (I am the same way towards apple too, even know I prefer android).
6. I suspect one of the problems is that Ics takes a little more juice and that the 1.4 exynos is once again underpowered. I think the other problem is samsung tried to rush this update out to the people and that the current touchwiz overlay is buggy. I expect an updgrade on touchwiz shortly (if they are a ethical company).
7. A primary example of the problems: While I'm typing this post I get a phone call. After I reject the phone call it goes back to taptalk with a less lighter screen. It is totally unresponsive. I then have to hit the back key to get back to composing. I then try to move up and down. It won't let me. After 15 to 30 seconds in able to once again continue this post.
8. I am sorry also that I upgraded because it might be glitchy for whom ever buys my phone eventually when I sell it (sell my phone every 6 months) and they may think there is something wrong with the phone, even though I baby my phones for future resell.
9. Bottom line: If its not broke dont fix it. We all want ice cream sandwich. Unfortunately, samsung's touchwiz version of ics at least doesn't appear to be ready for prime time. If you like beta testing and dont mind even worst glitches, then go for it. I definitely wont be upgrading to another phone with ics unless it has the new tegra 3 or the latest exynos processor.
AC
Sent from my GT-N7000 using Tapatalk 2

Well said my man, if it is slower and chews my battery faster wtf is the point of upgrading. We don't gain any mind blowing feature. Fyi who gives a flying F^k about angry birds space or whatever they come out with next
Sent from my GT-N7000

I went from gb, to german release ics, worked fine no issues from pc odin, then chainfire produced rooted kernel for it flashed with pc odin. all worked fine, but now i had triangle and 1 on the counter, ahhh, ok so triangle away dont work, flashed chinese repack did triangle away worked, using mobile odin, then i flashed the repack of the release with chainfire kernel, had nothing but problems, so went back to mobile odin flashed stock ics, then lost root, ahhh so flashed chainfire kernel with pc odin all well but still have triangle and 1 on the counter, i did full factory reset each time. I find ics a bit laggy more than latest gingerbread, i am leaving mine as is for the moment.

Was on several Leaks, to CM9 Official, to Official ICS. 0 problems!
People panic to easily in this forum. 1 guy bricks his phone and the damn section blows up and a public service announcement is made. Really?
Follow the directions.. EXACTLY, don't do anything erroneous, and you will be perfectly fine! Just like the rest of us.

Nope, not yet. Flashed with Mobile Odin Pro with Everroot and not the CF kernel.

Folowed dr ketan method from the lc1 cf root kernel. No problem so far

Help please

So I was trying to help a friend flash stock using Odin because his phone app was being a piece of crap, he was on a CM 11 nightly and, well, long story short I almost bricked his phone not knowing there is a limit on how many times you can flash a Samsung device using Odin because of the yellow triangle. I can't use triangle away because it's the CM ROM on a CM kernel, I was able to get rid of the softbrick by using a older CM ROM on his SD card, this wouldn't be a problem if his phone app was still working, his WiFi was working and if his sound was working, but it's not. So to recap and for the question, Samsung is stupid, and can anyone help?
Thanks in advanced
Sent from my awesome LG-E980

lonlyhornet said:
So I was trying to help a friend flash stock using Odin because his phone app was being a piece of crap, he was on a CM 11 nightly and, well, long story short I almost bricked his phone not knowing there is a limit on how many times you can flash a Samsung device using Odin because of the yellow triangle. I can't use triangle away because it's the CM ROM on a CM kernel, I was able to get rid of the softbrick by using a older CM ROM on his SD card, this wouldn't be a problem if his phone app was still working, his WiFi was working and if his sound was working, but it's not. So to recap and for the question, Samsung is stupid, and can anyone help?
Thanks in advanced
Sent from my awesome LG-E980
Click to expand...
Click to collapse
First thing you have to do for anyone to help you is,provide which build you were on and which stock rom you were trying to flash. There are tons of people here with great knowledge if you can be real specific.
Sent from my Nexus 5 using Tapatalk

So you wanna go to complete stock on a sprint s4?
Sent from my SPH-L720 using XDA Premium 4 mobile app

Fairly sure there is no limit to the amount of times you can flash using Odin. There is a counter but no limit
Sent from my SPH-L720 using xda app-developers app

Sorry, Samsung isn't stupid or they wouldn't just magically be a $250+billion dollar company that has been around for 76 years.
Because you jumped in and were unsuccessful with what you were doing doesn't constitute failure on their part.
How about taking that phone - S4 back to bone stock. ALL the answers on how to do that are here. In fact in the last couple days I've personally given instructions on how to do that for a number of people here in the help section. Do some searching and reading and you'll find your answers.
It always helps to come to a manufacture's section and say how sh**y they are. Makes those of us who choose to use and support them feel ever so helpful.

Ok sorry should've been more specific, I'm not new to these forums I was just in a hurry, also seriously guys I'm just frustrated I know Samsung is not stupid you don't have to post their history, they're awesome it's just dumb that they have a limit, and yes if you install the latest stock Sprint update (the one I did before I rooted and rom'd his phone) there wouldn't be a thing such as triangle away. Anyway on Odin it says it passed when flashing stock (the firmware that comes with the phone) but it does it in 4 seconds, and when his phone boots up and it just restores CM, so far everything we've tried either softbricks it or restores CM. Is there anything that completely and I mean completely restores this phone
Sent from my awesome LG-E980

lonlyhornet said:
Ok sorry should've been more specific, I'm not new to these forums I was just in a hurry, also seriously guys I'm just frustrated I know Samsung is not stupid you don't have to post their history, they're awesome it's just dumb that they have a limit, and yes if you install the latest stock Sprint update (the one I did before I rooted and rom'd his phone) there wouldn't be a thing such as triangle away. Anyway on Odin it says it passed when flashing stock (the firmware that comes with the phone) but it does it in 4 seconds, and when his phone boots up and it just restores CM, so far everything we've tried either softbricks it or restores CM. Is there anything that completely and I mean completely restores this phone
Sent from my awesome LG-E980
Click to expand...
Click to collapse
Where are you getting this idea there is a limit on Odin flashes?
Sent from my SPH-L720 using xda app-developers app

There is no limit, as mentioned already, with Odin.
I've used it probably a hundred times since I got my S4. I know others have used it more.
Take some time, look through the Q&A/help forum and you'll see some posts I've helped others with, in the last 24hours alone, on how to get back to stock.
Edit:
Okay read this post. It'll get you to stock. Just read the instuctions on how to do it.

Ok I'll try it thanks for tolerating me I can be hard to understand when panicking
Sent from my awsome LG-E980

leaderbuilder said:
There is no limit, as mentioned already, with Odin.
I've used it probably a hundred times since I got my S4. I know others have used it more.
Take some time, look through the Q&A/help forum and you'll see some posts I've helped others with, in the last 24hours alone, on how to get back to stock.
Edit:
Okay read this post. It'll get you to stock. Just read the instuctions on how to do it.
Click to expand...
Click to collapse
Did it and it worked thanks man! sorry for being rude I was just worried that I may have ruined my friends phone.

lonlyhornet said:
Did it and it worked thanks man! sorry for being rude I was just worried that I may have ruined my friends phone.
Click to expand...
Click to collapse
Glad you got it working and THANK YOU for posting back - that is what helps the community.
I understand the panic too. Especially when things are f'd up.
But if there is one valuable lesson I've learned in my half century of life; if you can just pause, relax and step back, many problems are easily resolved. And better yet more avoided by haste.
Good luck with the new phone setup.

OK one more quick thing, we flashed it successfully but now it won't boot its been over an hour after we flashed and its stuck on the Sprint logo

lonlyhornet said:
OK one more quick thing, we flashed it successfully but now it won't boot its been over an hour after we flashed and its stuck on the Sprint logo
Click to expand...
Click to collapse
You can first boot to stock recovery (power on + volume up) and choose a 'factory reset'. That often clears stuff up pretty well
Or
Try and PC Oding a stock MK2 kernel. Then battery pull and restart after. Saw this on a few phones
I'll have to search to find it but it's here somewhere.

leaderbuilder said:
You can first boot to stock recovery (power on + volume up) and choose a 'factory reset'. That often clears stuff up pretty well
Or
Try and PC Oding a stock MK2 kernel. Then battery pull and restart after. Saw this on a few phones
I'll have to search to find it but it's here somewhere.
Click to expand...
Click to collapse
Thanks! Factory resetting worked his phone is back on stock and ready for 4.4.2 thanks for the help LeaderBuilder!

lonlyhornet said:
Thanks! Factory resetting worked his phone is back on stock and ready for 4.4.2 thanks for the help LeaderBuilder!
Click to expand...
Click to collapse
Great!
Sent from my SPH-L720 using XDA Premium 4 mobile app

Huge problem need help

I flashed the Lollipop firmware on my note 4 (910G) and badly wanted to root. In the process of rooting i may have used the wrong CWM file. But i checked it doesnt seems so but i assume. Im not sure. Im not a noob (but not an expert) as i tinkered many phones so many times. But today things went wrong for the 1st time.
The issue is the calibration of the digitizer on my Note 4, its completely off, in some areas it doesnt work at all when using my fingers, but with the S-Pen it seems fine. Its impossible to use the phone, the gap is huge.
I re-installed the stock firmware it doesnt seems to install the stock recovery (Assuming its the recovery i flashed which caused this) hence didnt rectify.
I flashed the philz and twrp recoveries (Correct files) thinking having a working recovery would solve and that too did not help.
I flashed CM based ROM assuming it would make a difference, still no.
Please guys help fix this, and i really really hope its not hardware or triggered any chips to malfunction due to incorrect file flash. Pls help and advice what needs to be done to reverse this.
Thank you...

Flashing official stock firmware should revert your recovery back to standard. It did for me when I was using Cwm and reflashed 5.0.1 firmware.
try your device in safe mode to see if that changes anything. If not I'd recommend doing a complete wipe then reflashing the stock firmware.

BNerd89 said:
Flashing official stock firmware should revert your recovery back to standard. It did for me when I was using Cwm and reflashed 5.0.1 firmware.
try your device in safe mode to see if that changes anything. If not I'd recommend doing a complete wipe then reflashing the stock firmware.
Click to expand...
Click to collapse
No mate tried all that, makes no difference. Even in safe mode its still behaves the same. And installed stock firmware many times, also without battery too. No improvement. Even the stock recovery isn't installed, thats the biggest question i have in that process.

malakalofung said:
I flashed the Lollipop firmware on my note 4 (910G) and badly wanted to root. In the process of rooting i may have used the wrong CWM file. But i checked it doesnt seems so but i assume. Im not sure. Im not a noob (but not an expert) as i tinkered many phones so many times. But today things went wrong for the 1st time.
The issue is the calibration of the digitizer on my Note 4, its completely off, in some areas it doesnt work at all when using my fingers, but with the S-Pen it seems fine. Its impossible to use the phone, the gap is huge.
I re-installed the stock firmware it doesnt seems to install the stock recovery (Assuming its the recovery i flashed which caused this) hence didnt rectify.
I flashed the philz and twrp recoveries (Correct files) thinking having a working recovery would solve and that too did not help.
I flashed CM based ROM assuming it would make a difference, still no.
Please guys help fix this, and i really really hope its not hardware or triggered any chips to malfunction due to incorrect file flash. Pls help and advice what needs to be done to reverse this.
Thank you...
Click to expand...
Click to collapse
Have you tried to update the firmware of the touchscreen? Enter *#2663# into the dialer with your S pen and then click TSP FW Update.

Oh my God. Bro u saved my life. Thank you so much for replying and suggesting this. U r post was the 1st thing I read and did and it worked. Thanks man. Thanks so very much. U don't know how delighted I am now. Thank you again.....
Sent from my SM-N910G using XDA Free mobile app

Hmm.. Wonder why this issue occurred in the first place... I doubt it's due to rooting, though..
Sent from my SM-N910G using Tapatalk

coolfire said:
Hmm.. Wonder why this issue occurred in the first place... I doubt it's due to rooting, though..
Sent from my SM-N910G using Tapatalk
Click to expand...
Click to collapse
Well im sure i followed the process right but now i doubt it used an incorrect file (CWM) to flash on odin, which caused this. Anyhow thank God its fine now lol. I Was literally in tears man. Ha ha

I can totally understand how you felt. Glad all is great now!
Sent from my SM-N910G using Tapatalk

This problem has nothing to do with rooting or installing a custom recovery. Only when upgrading or downgrading firmwares the touchscreen firmware can sometimes bypass the update.

Good one... Hackberrybold

Trying to restore/update PA but unfamiliar with the process

Hi Everyone,
Im using an att LG G2 with Paranoid Android installed; I bought the phone at release I am pretty sure and through att. I believe it to be PA version 3.4 and Android version 4.3.1 from looking af the about phone settings. Basically Ive had this phone on loan to someone for about a year and it is just bogged down with shovelware. Netflix wont even load. I was comfortable playing around with ROMs before but ive been in the Ios scene lately and am out of practice. I have some recoveries but I'm concerned with having not played around on the phone's root for several years now so I'd rather not use something that may be incomplete.
My main concern is having the phone back to its speed from before, getting rid of all of the apps, and starting fresh. Id like to keep PA, hopefully upgrade to the latest version, but if i can just factory reset that works too. I'm pretty sure i could reinstall PA starting from scratch with a clean phone. I've been through the forums different times and I really do find that the info is all consolidated well. I hope I don't come accross as lazy or unwilling to search, I just had a bad experience flashing my Galaxy S2 so whenever I'm not certain on the process I try to consult with people more involved.
Thank you all for your time,
Andrew Rapp

Forgive me but I've had this phone on the shelf for a bit and am seeing now that paranoid Android is relatively dead. That'd be unfortunate since I really dug the interface! But if it really is no longer being supported would anyone have a suggestion on a ROM upgrade? Thanks again!

Cm13 or 12.1 both available with a few variants based on them just give them a whirl.
Sent from my LG-D802 using Tapatalk

Treboeth said:
Cm13 or 12.1 both available with a few variants based on them just give them a whirl.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I had CM back on my s2! I could get down with checking it out again. Going through their website is a lot of helpful information, however, most of it seems to be garnered at first time users. I'm using this guide here:
https://wiki.cyanogenmod.org/w/Install_CM_for_d800
and I'm curious if I can skip the first half (installing a custom recovery); because I'm pretty sure I have one installed already from when I flashed PA. How would I go about checking?

Just reboot into recovery to check the version.
But it would be best to update to TWRP 2.8.73 (latest version).
Sent from my LG-D802 using Tapatalk

So once I've updated TWRP (which I do have installed) I can skip that first half and just do the second part? Thanks for the help btw; really trying to bring the phone back to life since I love the screen and size

If you have flashed Roms before you know the rule, read the first post then read it again then read it a third time
Make sure you have the correct bootstack, I suggest the official CM ROM to start with by Drastic then you can always try the others AICP,Bliss,ResurrectionRemix and Crdroid.
I like AICP for the customisations been on it for a couple of days to try out.
Sent from my LG-D802 using Tapatalk

I know, being cautious to a fault here >_< I just ended up using flashify to update twrp; that was easy enough. I'll use the app to make a back up I believe and then try following instructions on the website! Thanks for all your help, hopefully I won't need to return XD but still keeping the topic open just in case!

Nope! I get an error when trying to install the CM zip file. In red it says:
E: Error executing updater binary in zip '/sdcard/cm-12.1-20151117-SNAPSHOT-YOG7DAO1KI-d800.zip'
I was able to get in what appears to be a broken CM installation, which fortunately includes file system exploration and messaging. Accessing the phone from the computer is no problem either. Any idea what the issue here may be?

Bump!

Not sure to be honest,if you have followed the steps in the OP post up in the thread by @drastic and I am sure the more knowledgeable will help you solve the problem.
Sent from my LG-D802 using Tapatalk

I'm sorry, which thread is that?

Totalrapture said:
I'm sorry, which thread is that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3264508 Cm13 [emoji6]
Sent from my LG-D802 using Tapatalk

Ahhh thanks! Yeah I'd been doing the 12.1 downloads from the CM site but yeah that process seems to be the same. Could it be possible that my something weird had been done with the person I loaned the phone too? He liked to tinker and I wouldn't put it passed him to have done something funny with it, or even I before having loaned it. Coud the bootstack be an incorrect? Is there a way I could check?

Can you get the phone back to stock Lollipop,if you think he has played around this may be the best option.
Sent from my LG-D802 using Tapatalk

Treboeth said:
Can you get the phone back to stock Lollipop,if you think he has played around this may be the best option.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I was thinking that'd be the best option; just to start everything over. Would that process be extensive? I'm on a work computer so I can use recovery and get the files on my phone but anything too complex or needing me to use installers I'll probably have to wait until tomorrow

http://forum.xda-developers.com/showthread.php?t=2432476
Should give you all you need, it could take an hour or two but will give you a fresh start.
Sent from my LG-D802 using Tapatalk

Treboeth said:
http://forum.xda-developers.com/showthread.php?t=2432476
Should give you all you need, it could take an hour or two but will give you a fresh start.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Thanks! I'll probably wait until my next day off and then try to run through it all