Develop Bugs

Problem loading G2 V3 Rom with E980

I have downloaded the G2 V3 update.zip to my phone and have tried installing the zip via CWM. I followed instructions stating factory default first, then flash the update.zip, install the SU add-on 1, then factory default. When I reboot my phone I get the LG boot screen, afterwards my indicator lights both flash on, my phone vibrates and the backlight stays on but I get a blank screen. I left it like this for 20 minutes but it never continues. I have tried rebooting but it does the same thing. I have loaded my previous CM 10.2 Rom since. Tried repeating this process, get same results. Adding to this, when I load the add-on it does say there was a problem with Loki at the end.
Please help.

Are you coming from stock or were you on CM?
I always return to stock before changing roms,, I've heard of people having trouble going from CM to V3....
_________________
Beavers & Ducks!

Always wipe system, cache and dalvik-cache before flashing. I'd also suggest wiping the internal sd card as well. Always gives me the best results. I've jumped from ROM to ROM this way with no problems. :3
Sent from my LG-E988 using XDA Premium 4 mobile app

That has to be what it is, I am going from CM10.2 to this mod. I am going to try to go to stock and then message again my results. Thank you for replying to my message.

tobias87 said:
That has to be what it is, I am going from CM10.2 to this mod. I am going to try to go to stock and then message again my results. Thank you for replying to my message.
Click to expand...
Click to collapse
Yup, that is the issue. Those ROMs do not have stock kernel bundled and hence they do not boot when you come from CM or Carbon or Vanir to V3.
You have to go back to stock and then flash that.
Or there might be another way which might work and will spare you hassles of going back to stock and rerooting. Give it a go.
1. Download this kernel : http://forum.xda-developers.com/showthread.php?t=2363330
This kernel is for stock based ROMs.
2. Install V3 by following the procedure. After second factory reset, before rebooting, flash this kernel. And then reboot.
See if that is successful. It should be. (it will still take 4-5 minutes for first boot )
If not , you can always go back to CM and then go through whole going back to stock thing.

Got The thing to work by flashing the CWM recovery files in three parts. Then updated to V4 and SU. The only thing I can't seem to get working is the wireless reefer devices can connect but the receive no data.
Funkym0nkey said:
Yup, that is the issue. Those ROMs do not have stock kernel bundled and hence they do not boot when you come from CM or Carbon or Vanir to V3.
You have to go back to stock and then flash that.
Or there might be another way which might work and will spare you hassles of going back to stock and rerooting. Give it a go.
1. Download this kernel : http://forum.xda-developers.com/showthread.php?t=2363330
This kernel is for stock based ROMs.
2. Install V3 by following the procedure. After second factory reset, before rebooting, flash this kernel. And then reboot.
See if that is successful. It should be. (it will still take 4-5 minutes for first boot )
If not , you can always go back to CM and then go through whole going back to stock thing.
Click to expand...
Click to collapse

Swype decided to fill in an odd word for what I meant sorry. I meant wireless tether.
tobias87 said:
Got The thing to work by flashing the CWM recovery files in three parts. Then updated to V4 and SU. The only thing I can't seem to get working is the wireless reefer devices can connect but the receive no data.
Click to expand...
Click to collapse

[Q] Phone wont reboot properly after 4.3 update

Ever since I updated to 4.3 I have never been able to properly reboot my phone. When I reboot its stays on the splash screen after the samsung logo and doesnt move. I have to go into TWRP and wipe everything completely restore data , rom ,Gapps. I have to do this every single time I reboot. I never had these problems on 4.2.x roms or anything. Any fixes for this? Anyone experience anything similar :crying:

emili0estavez said:
Ever since I updated to 4.3 I have never been able to properly reboot my phone. When I reboot its stays on the splash screen after the samsung logo and doesnt move. I have to go into TWRP and wipe everything completely restore data , rom ,Gapps. I have to do this every single time I reboot. I never had these problems on 4.2.x roms or anything. Any fixes for this? Anyone experience anything similar :crying:
Click to expand...
Click to collapse
Which 4.3 ROM(S) are you having trouble with?
Please update us also what provider you have along with more info about your phone.
Sent from my SGH-I747 using XDA Premium 4 mobile app

Bruce Lee said:
Which 4.3 ROM(S) are you having trouble with?
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Right now im on the quantum v2.20. This problem happens with any 4.3 rom though Tasks,PA,Liquid smooth they all give me this error. Tried wiping the phone over and over nothing. I even installed clean without restoring data or anything and can never reboot properly. In order to reboot properly I have to go back wipe memory, factory reset, wipe everything else and install Rom again.

emili0estavez said:
Right now im on the quantum v2.20. This problem happens with any 4.3 rom though Tasks,PA,Liquid smooth they all give me this error. Tried wiping the phone over and over nothing. I even installed clean without restoring data or anything and can never reboot properly. In order to reboot properly I have to go back wipe memory, factory reset, wipe everything else and install Rom again.
Click to expand...
Click to collapse
Well, from what it sounds it could be the recovery, so make sure that it is the latest version and also make sure that your bootloader is updated to one from the 4.1.2 OTA update. There's a post on the Quantum thread about how to update your bootloader (something necessary to flash any 4.3 rom). Just please make sure to read a lot BEFORE flashing so you don't end up with a paperweight. I assume your on AT&T, correct? If this is the case and your phone is a SGH-I747, the update should go fine. If this doesn't work, I would try asking super nicely on the official thread and explain everything with as much deatil as possible, and they'll be able to help you, since it's not one of those threads that get furious at asking questions in the dev thread. Hope this helps.

emili0estavez said:
Ever since I updated to 4.3 I have never been able to properly reboot my phone. When I reboot its stays on the splash screen after the samsung logo and doesnt move. I have to go into TWRP and wipe everything completely restore data , rom ,Gapps. I have to do this every single time I reboot. I never had these problems on 4.2.x roms or anything. Any fixes for this? Anyone experience anything similar :crying:
Click to expand...
Click to collapse
or you can go back to 4.1.2 which is mostly stable and works fine with no issues or problems compared to 4.2.2 or 4.3 AOSP/CM Roms

I'm having the same issue, but for me my phone gets soft bricked and I have to reformat internal storage for anything to work. I bought my phone with 4.1.2 already installed, and my recovery is twrp 2.6.30, which is the latest one
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

AOSP roms will NOT run! Driving me crazy...

So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?

I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app

iamdofus said:
I have the same problem, just format your internal and external sd card with just ROM file on your storage then try to install, than please inform me
Sent from my SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.

Do you by chance have a refurbished s2?

The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?

es0tericcha0s said:
The screen has been replaced by a friend of mine and he managed to mess up the soft keys with it, but everything else functions. That's actually why he sent it to me, so I could hook him up with Pie and all that kind of thing so the soft keys aren't an issue. What's your thoughts on the refurb side of it?
Click to expand...
Click to collapse
OK thanks for reply, I have one more solution give me. Some time I will give try that it worked for me.
Sent from my SGH-T989 using XDA Premium 4 mobile app

es0tericcha0s said:
Nope. No luck there (only tried Beanstalk so far, but exact same issue). Thanks for the suggestion though! Only using internal storage, no SD card, though thinking I might try that next...
Edit: Just to be thorough, I formatted internal storage via TWRP and my computer then readded the files and just tried to boot rom only and freezes before I can do anything.
Click to expand...
Click to collapse
ok lets stat it with this
1) download both the scripts of infamous wipe cache and infamous super wipe.
2) format your both SD card with PC (FAT32)
2) put both these wipe files and and your rom file ( i prefer try slimbean rom first)
3) Now in twrp 2.6.0.0- follow the steps
i) format your phone with twrp options
ii) again format your phone with infamous super file. (by going in to INSTALL ZIP file option in TWRP)
iii) than format with infamouse cache file (by going in to INSTALL ZIP file option in TWRP)
iv) install your rom and compatiable GAPPS zip file.
v) after installing or somewhere between procedure if twrp says something about supersu birnaries are not correct than click on DO . NOT FIX
vi) again format infamouse cache wipe.
vii) now FINALLY reboot the rom.
it should work, and it worked for me. if u sucessfully run the rom than you can eailsy run all the AOSP roms in this forum. Again If you try this please do tell me what happend.

Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!

es0tericcha0s said:
So, first off, just wanna say that I have a RIDICULOUS amount of experience with flashing roms. Literally over 100 different devices and 1000s of different flashes of my own devices on top of it. Quite familiar with this S2 as well and have customized them to all sorts of extents, but this one has me baffled. This phone refuses to run 4.2.2/4.3/4.4.x roms. Using the most up to date radio and the suggested TWRP (2.6.1.0) as well as CWM 6.0.44 and the newer TWRP: 2.6.3.0. Every time the phone will get to the set up screen, refreeze and boot. No issues running stock or stock based 4.1.2 roms. I've tried changing recoveries, wiping everything (/system, /data, /caches) repeatedly, Odin back to stock and redoing everything, switching kernels, wiping caches before rebooting and leaving it be, changing batteries, etc but nothing has worked. So far I've tried BlackLiquid 2.92 (4.2.2 stable), Awesome Audio rom (4.3), official CM11 (whatever the last build up was last night), and BeanStalk 4.4.2 (12/16) and all behave exactly the same - freeze on start up and reboot. This doesn't seem to be much of a widespread issue obviously, so just baffled and getting a bit frustrated as this should have been a 20 minute process that has turned into a few hours already. Since USB Debugging isn't on by default on newer roms, how would I even do a logcat to see if there is anything meaningful there? Any ideas?
Update: I have another S2. Performed same steps, same TWRP, same radio and rom, on same external SD card and that one booted right up like normal confirming that it is the phone itself, but what causes that?? Corrupted partitions?
Click to expand...
Click to collapse
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?

UltimaniumX said:
Interesting, so you're saying it's phone specific?
That begs to ask other questions now:
1. Where did this phone come from? is it a Tmobile version (SGH-T989) or AT&T (i-1900)?
2. You mentioned you got it from a friend; did it come rooted? unlocked? Or did you have to do that process yourself?
Click to expand...
Click to collapse
Yep, very much phone specific. Used same recovery, same rom zip and gapps off the same external SD card, to be certain. That one updated just like every other S2 I've done. And it's the Tmo version. The At&t models are i777 S2 or i727 S2 Skyrocket. The i9100 is international and has a physical home button. But the phone was not modified at all. No root, custom recovery, etc. I was only able to resolve it by first starting with an AOSP 4.1.2 rom and working my way up to 4.4. One of the weirder issues I've come across.

es0tericcha0s said:
Followed to a "T" and still in the same boat - freezes after bootup. I used those same steps before with another darkside wipe script (maybe older?) but yea, have already been down that road. I did downgrade to 2.6.0.0 and used Slim 4.3 because 4.4 is supposed to use the newer TWRP, just to be certain, but GRRR. I guess we're just gonna have to settle for a 4.1.2 rom and call it a day. :/
So here are the log output from the wipes:
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.SUPER.WIPE_recovery.log
https://dl.dropboxusercontent.com/u/9903887/INFAMOUS.CACHE.WIPE_recovery.log
I see some stuff at the bottom of those that might indicate something weird, but I am not adept at interpreting these, so just wondering if someone could point me to the right direction about the repair checks and what not listed on these. Thanks!
Edit 2: I did get a AOSP based 4.1.2 rom to boot with no problems! wtf... LoL
Last Edit:
Problem solved! I used basically the same steps I had been doing but once the AOSP 4.1.2 rom booted then now everything works like it should again. Have loaded a 4.3 and 4.4 rom successfully. Thanks for the help!
Click to expand...
Click to collapse
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?

tpag02 said:
What did you exactly do? I flashed a 4.1.2 and then flashed a 4.3 based ROM and it didn't work. What recovery version did you use to flash the 4.3 ROM?
Click to expand...
Click to collapse
Sorry, I don't pay attention to the notifications on XDA very often. I don't usually browse the S2 forums unless needed because I have an N5, but anyway... The 4.1.2 rom you used, was it TW or AOSP type? I used 2.6.0 to wipe everything, then used cache and superwipe zips then 4.1.2 AOSP type rom then cache wipe zip again then after that booted, I was able to go back to 2.6.1 and flash a 4.3 via wiping, wipe zips, installing rom then cache wipe again. After that, repeated with a KK rom and now it loads roms just like it should. If you want more precise help, feel free to hit me up on Hangouts with my username: es0tericcha0s. Good luck! I know how frustrating it can be when it gets a little out of whack like this...

I'm in the same boat
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.

DennyTek said:
Same here. I just bought a galaxy s2 from my friend (tmobile version) and I too get stuck in a bootloop no matter what rom I use. It boots up freezes then reboots 7 keeps doing that endelessly. I've even wiped using twrp & darkside then reflashed the stock rom in odin, but no luck. strangely it only happens on the cellular network, otherwise it works fine on wifi. But when I turn off the wifi and go to the cellular network I can't even turn on the wifi anymore and still stuck in this boot loop It's wierd and frustrating.
Click to expand...
Click to collapse
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?

TMO 4.1.2
es0tericcha0s said:
Hmm. That's interesting... This is happening on the stock rom - where you turn on cellular data and it reboots? Definitely a different issue than the one I was having. Which stock rom were you flashing via Odin? Have you tried other versions of the stock rom and had the same problem?
Click to expand...
Click to collapse
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/

Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk

yep
wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ya, well at least I am anyways

wikitiki said:
Are you guys flashing gapps if the ROM you're installing doesn't have it?
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I had tried with and without and did not make any difference.

DennyTek said:
This was happening on any rom I used (Cm 10.2 stable, Cm 11 nightly, AOKP & Super Nexus 3.0 which is Android 4.3) I can't really speak for the stock rom (tmo 4.1.2) since I've never used it for more that 5 minutes, sigh but I'll try it and see if it gives me the same problem :/
Click to expand...
Click to collapse
I just started working on a VZW S3 on T-Mobile service that has this issue. Happens on stock VZW 4.1.2, stock T-Mobile 4.1.2 rom, custom 4.1.2 T-Mobile rom, and stable CM 10.2. Weirdest thing... full wipes including /system inbetween each flash. Changed the modem too. Nothing helps. Pretty sure it's a bad board at this stage.

Cool beans, 0! Having this exact problem, will try your method for my s2, btw which aosp 4.1.2 did u use? Can I get a link? Thanks been having the problem for a few months now and just gave up haha, been super thirsty for that beanstalk kk build
One last thing can u also provide a link to the 4.3 that u used? I really want it to work and want to follow what u did to the , megabyte

LG Optimus G LS970 Data connection problem (4G LTE)

Relatively inexperienced with flashing ROMs and what not, but since switching to the LG Optimus G, flashing has been really simple. I have been running into a few problems though. No matter which ROM I choose, I can't seem to get my data connection to work. I've tried flashing various zips that claim to fix it, but so far no luck.
Currently running CM11 with TWRP
Any help would be appreciated.

PattyCakez said:
Relatively inexperienced with flashing ROMs and what not, but since switching to the LG Optimus G, flashing has been really simple. I have been running into a few problems though. No matter which ROM I choose, I can't seem to get my data connection to work. I've tried flashing various zips that claim to fix it, but so far no luck.
Currently running CM11 with TWRP
Any help would be appreciated.
Click to expand...
Click to collapse
Make a back up of your rom via recovery
Flash stock ZVC ROM, update PRL & Profile, Wipe data/system/cache/dalvik and restore 4.4.4
data should be restored.

RG3 said:
Make a back up of your rom via recovery
Flash stock ZVC ROM, update PRL & Profile, Wipe data/system/cache/dalvik and restore 4.4.4
data should be restored.
Click to expand...
Click to collapse
Ok, I downloaded the ZVC Stock ROM .zip file from here
http://forum.xda-developers.com/showthread.php?t=2536636
I tried flashing and it gets stuck at the LG screen. Are there any gapps that i'm supposed to flash with it?

PattyCakez said:
Ok, I downloaded the ZVC Stock ROM .zip file from here
http://forum.xda-developers.com/showthread.php?t=2536636
I tried flashing and it gets stuck at the LG screen. Are there any gapps that i'm supposed to flash with it?
Click to expand...
Click to collapse
No. The ROM itself is all you need. I'm not sure why it's stuck at boot. Try wiping cache, dalvik, and data. It should just boot. How long did you wait? It might take awhile. Possibly 5ish but no more than 10 minutes to boot.

dopy25 said:
No. The ROM itself is all you need. I'm not sure why it's stuck at boot. Try wiping cache, dalvik, and data. It should just boot. How long did you wait? It might take awhile. Possibly 5ish but no more than 10 minutes to boot.
Click to expand...
Click to collapse
I waited at least 15-20 minutes. I'll try it again.

Ok, so I got it back to the stock ROM, working on trying to update the PRL.

PattyCakez said:
Ok, so I got it back to the stock ROM, working on trying to update the PRL.
Click to expand...
Click to collapse
What changed that caused it to work? I am glad you got it, I am just curious how the process came together.

I'm thinking forgot to wipe /system.

Not sure what I did different to make it boot into stock, but I made a back up, (Boot, System, Data, and Cache), flashed stock, booted, updated profile and PRL, wiped (Dalvik System, Data, and Cache) reinstalled back up and still no 4G, am I missing something or doing something wrong?

Almost Working
So I almost fixed it, I did the whole flashing back to stock thing with no luck. I did a clean flash of the latest cm11 Nightly, then also flashed the file found here
https://help.ting.com/entries/23423026-Flashable-Zip-Fixed-LTE-eHRPD-for-CyanogenMod
I figured maybe the problem was due to me being on Ting. So far I can get it to say I am on LTE, but any data connection I am receiving is painfully slow to the point where it is completely useless.
Any suggestions?

PattyCakez said:
So I almost fixed it, I did the whole flashing back to stock thing with no luck. I did a clean flash of the latest cm11 Nightly, then also flashed the file found here
https://help.ting.com/entries/23423026-Flashable-Zip-Fixed-LTE-eHRPD-for-CyanogenMod
I figured maybe the problem was due to me being on Ting. So far I can get it to say I am on LTE, but any data connection I am receiving is painfully slow to the point where it is completely useless.
Any suggestions?
Click to expand...
Click to collapse
I am also on ting, and the only way I have been able to get my LTE to be consistent it to manually enter in the APN settings. I have tried to flash that same file, but I don't get LTE.
Sent from my LG-LS970 using XDA Free mobile app

cmf04 said:
I am also on ting, and the only way I have been able to get my LTE to be consistent it to manually enter in the APN settings. I have tried to flash that same file, but I don't get LTE.
Sent from my LG-LS970 using XDA Free mobile app
Click to expand...
Click to collapse
How would I go about manually putting in the APN settings? Is there a tutorial somewhere?
Also, is the unreliable LTE causeing my mms to not work? Or is that a separate problem all together?

I use this program to change my APN
https://play.google.com/store/apps/details?id=it.appando.app.changeApn
This is what my APN is
Name=Sprint
APN=n.t8.ispsn
MMSC=http://mms.plspictures.com
MMS proxy=68.28.31.7
MMS port=80
MCC=310
MNC=120
APN type=default,mms
APN protocol=IPv4
APN roaming protocol=IPv4
You might to try and run a stock ROM and update your prl and profile.
Sent from my LG-LS970 using XDA Free mobile app

[Q] Fingerprint scanner gone and keyboard lag so bad its painful (Developer Edition)

So I took all precautions and still ended up with an unresponsive fingerprint scanner do to I'm assuming a ROM flash. Damn. Wiped everything and restored stock backup to no avail. Losing the scanner stinks but what's worse is now I'm experiencing huge lag on stock keyboard and even Google keyboard along with occasional lag throughout the system. Anyone know how to remedy this?

dirtyjersey856 said:
So I took all precautions and still ended up with an unresponsive fingerprint scanner do to I'm assuming a ROM flash. Damn. Wiped everything and restored stock backup to no avail. Losing the scanner stinks but what's worse is now I'm experiencing huge lag on stock keyboard and even Google keyboard along with occasional lag throughout the system. Anyone know how to remedy this?
Click to expand...
Click to collapse
Out of curiosity what ROM did you flash?
Here is a recommendations: Power off the phone, enter TWRP, wipe cache, wipe data, wipe delvik, do a factory reset and flash your backup. Power off the phone, pull battery and let it sit for about 30 seconds. Put the battery back in and boot. See if that works.

jpcalhoun said:
Out of curiosity what ROM did you flash?
Here is a recommendations: Power off the phone, enter TWRP, wipe cache, wipe data, wipe delvik, do a factory reset and flash your backup. Power off the phone, pull battery and let it sit for about 30 seconds. Put the battery back in and boot. See if that works.
Click to expand...
Click to collapse
I initially flashed Definitive 1.1 since I'm still on old stuff but that was fine..then I tried flashing an unofficial CM12 that I got to boot up but no data even with Verizon Rils. But I think what killed it was Infamous for n910t. After that it was unresponsive with error dialogue box pop-up. I'll try the exact method you mentioned and respond back. I have completely wiped and restored stock through twrp but no Odin yet since my friends WiFi connection is ridiculous at like 150kbps.

No luck. Tried it 3 times.

dirtyjersey856 said:
No luck. Tried it 3 times.
Click to expand...
Click to collapse
If I remember correctly CM has its own kernel. Try flashing the stock Note 4 kernel. You can find the stock kernel in the firmware thread under Android Development.
Sent from my SM-N910V using Tapatalk

jpcalhoun said:
If I remember correctly CM has its own kernel. Try flashing the stock Note 4 kernel. You can find the stock kernel in the firmware thread under Android Development.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
I'm on stock kernel as we speak.

If all else fails, you can flash stock system, modem and kernel found in the Android Development section. That gives you a clean start. Then ODIN TWRP and flash SuperSU. If you do that just make sure you use the files designated for the Developer Edition.
Sent from my SM-N910V using Tapatalk

jpcalhoun said:
If all else fails, you can flash stock system, modem and kernel found in the Android Development section. That gives you a clean start. Then ODIN TWRP and flash SuperSU. If you do that just make sure you use the files designated for the Developer Edition.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
You think that would help? From what I've found so far the only thing that could potentially help would be a complete fresh stock Odin flash INCLUDING a bootloader but we don't have a flashable bootloader for DE.

I don't think you have a bootloader problem, I think you have a system issue or a kernel issue. If you're backup doesn't make things better then the only answer I have is to flash a stock (clean) system firmware and kernel which is available. Then re flash recovery and root. By the way, I wouldn't flash anything that had not been tested and passed for the Note 4, the Verizon Note 4. Just a recommendation.
Sent from my SM-N910V using Tapatalk