Database Develop

Unable to get into Recovery after 4.1.2 upgrade...

Ok, so I ran into a VERY weird issue and was wondering if anyone else has experienced this or has a better solution then what I found.
My Nexus7 was running stock JRO03D. I had it rooted, using the Motley kernel with CWM Recovery - but outside of that, everything else was pretty stock. Anyway, I decided to upgrade to the 4.1.2 image. I pulled the one it downloaded automatically out of /cache and looked at the updater-script to see what it did. I noticed it replaced a lot, including the boot image, so I figured it would be better just to let it do everything and revert my custom stuff later. So I replaced the kernel with the stock JRO03D kernel and, using CWM, flashed the upgrade. Everything seemed to go perfect and it completed the upgrade. Prior to rebooting it, I also flashed the "unofficial" motley 4.1.2 kernel posted on XDA. I rebooted the device, and CWM warned me that 'su' needed to be fixed (how nice!) and made it suid again. It rebooted and after android "updated", everything was up and running. I confirmed in settings that it was on 4.1.2 with the custom kernel. SU was suid root as well. Perfect!
Not quite.
I decided to try rebooting into recovery to make sure CWM was still there, or flash it back if it wasn't. I opened up a terminal emulator, removed the new recovery-recovery image in /system, and did "reboot recovery". The Nexus7 rebooted, but rebooted right back into normal operation. Very weird. So I hooked it up to my computer, figuring CWM was gone, and tried to fastboot flash it back. Fastboot said it did, but I still wasn't able to reboot into recovery. I tried three different versions of CWM and even TWRP, but no dice. Every time I tried rebooting into recovery (using terminal emulator, adb shell or bootloader method) it just went right back into the normal boot process.
I spoke to some people on IRC who recommended reflashing the stock image from Google (without wiping user data). I reflashed the bootloader and then did a fastboot update <stock image>, and it said it replaced boot, recovery, system, etc. It rebooted automatically, and I tried going into stock recovery. That still did NOT work. Instead, I got a very sick looking android guy who was lying down with a red triangle with an exclamation point over him. I was a bit worried and upset at this point. I tried reflashing CWM/TWRP again, but nothing. When I did this, I no longer got the unhappy android image, but it just booted up normally.
I decided to try and doing a more thorough wipe, using fastboot to wipe cache/boot/recovery/system manually. Then I reflashed the bootloader and stock image. Still no recovery (stock or custom).
As you can imagine, I was getting even more concerned now. Especially since I was no without root and no way to get it back (since I couldn't get into recovery to flash the zip for it).
I tried every other thing I could think of to flash recovery back, but nothing worked. It wouldn't load at all.
Finally, I was about to do a complete factory reset and wipe/reflash of everything, but one last thought crossed my mind. I found the older (JRO03D) bootloader and flashed that. Reloaded bootloader and selected "Recovery". Voila, I was in TWRP Recovery Mode! (which was the last one I tried installing). I was able to reinstall my SU.zip and get everything back up and running.
SO, long story short, I'm now on 4.1.2, running the newer unofficial motley kernel and have su back. But I'm also stuck on the older 3.34 bootloader. If I try upgrading it back to 3.41, I won't be able to get into recovery.
Has this happened to anyone else? It doesn't seem like it. Is there a HW issue with my device causing this problem? I can't believe it's software related since I tried two different copies of the 3.41 image. Does anyone have any other suggestions on how I can upgrade the bootloader while keeping the ability to get into recovery mode?
Also, while everything *seems* to be working OK using 3.34, do you think it will cause other problems since I'm using 4.1.2?
Thanks.

*MOD EDIT* please don't quote the entire OP
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!

That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium

MetalWych said:
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
Click to expand...
Click to collapse
No problem. I'm glad to hear that my solution above helped someone else, and also that I'm not the only one experiencing the problem. I assume you mean you only went back to the JRO03D bootloader and not the whole image, right?
What I'm most concerned about is that it seems like my N7 (and possibly yours as well) is defective. I'm not an uber-expert on Android, but I'm fairly knowledgeable. With a stock system, outside of userdata, that I reflashed multiple times from multiple sources, to have any type of recovery (stock or custom) not work is a bit upsetting. Since it works fine on the older bootloader, it definitely seems to be an issue with that. But since most people do not have the same issue, the only variable I can see being the difference is hardware.

Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It looked more like a warning symbol that something went very wrong then a stock recovery screen.
I've gone into stock recovery on other Android devices before, and it looked similar to CWM. There was a menu that allowed you to install "authorized" update.zip files, factory reset the device, etc. There was no menu here, just a very pissed off and sick looking android guy .

I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium

There's a big thread around here somewhere with people having the same problem as the op. Unfortunately, staying with the 3.34 bootloader is the only 'fix' I've read about. I still can't figure out why some people run into this problem and some don't. I used twrp to flash the update when it became available, and twrp continued to work afterwards.

spongers said:
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It took me a long time to find the old full JRO03D update, since Google only has the latest one on their page. I uploaded the bootloader out of it and you can download it here:
http://core.routed.com/bootloader-grouper-3.34.img
Reboot the Nexus7 into bootloader mode and run:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
and then you should be able to flash recovery and get into it.

Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The android with the red triangle does not sound like the stock recovery, it is THE stock recovery.
Under JB 4.1.2 you do not need anymore to connect the N7 to a computer - like it had to be under JB 4.1.1 - to access the bootloader and then the recovery.
Now, pressing volume + power brings the bootloader , the up volume, one press, and then power press put the N7 to recovery. The recovery is the android with the red triangle. To enter in the recovery menu pressing power + volume up brings the menu with the following options:
i) reboot system now,
ii) apply update from ADB,
iii) wipe data/factory reset,
iiii)wipe cache partition.
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.

the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.

smirkis said:
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
Click to expand...
Click to collapse
Smirkis, my initial thought was that something went wrong in the upgrade process, possibly with the kernel like you suggested, so, as I mentioned in the OP, I flashed everything back to stock 4.1.2. I used flashboot to manually erase boot, cache, recovery and system. I then reinstalled the bootloader from Google's update tarball. I then used fastboot to update to image-nakasi-jzo54k.zip. At this point, outside of wiping sdcard, everything was stock 4.1.2.
While I will admit that I didn't realize that the dead-looking android meant stock recovery (and that's good to hear), subsequently flashing a custom recovery (CWM or TWRP) would continually fail to load it. In fact, I couldn't even boot into the recovery manually without flashing it. While using 100% stock, I attempted to flash three different versions of CWM and one version of TWRP. It claimed it updated, but I was not able to get back into recovery - either through bootloader, adb or "reboot recovery".
I know it's easy for people to always jump to the "user error" answer, but I fail to see how that is the case here. Based on your response, I don't think you actually read what I did and just jumped to the wrong conclusion, especially since I already tried your recommendation and much more. I am not running any custom ROM - everything was always stock outside of recovery, root and kernel. If you can explain your reasoning for thinking I did something wrong in all of my numerous attempts to get it working, I would appreciate it since maybe that would provide a solution. While I did attempt to use a custom kernel originally, that obviously isn't the issue if going back to stock didn't fix it.
Additionally, reverting back to the older bootloader magically fixed everything, while all other attempts failed. Subsequently reinstalling the custom kernel didn't break anything either. So if it wasn't the bootloader and something else was broken, I would assume it would be broken in both versions of the bootloader. The fact that this problem is affecting others, granted a small number, and the same solution works for them, leads me to believe that there is either a bug in the bootloader affecting some N7s or some rare HW defect causing a few of us problems.

There is a conversation about the new android update the boot-loader update and A Power management chip on the nexus 7.. It seems this chip is being changed out. The new chip functions the same as they have been using but Its not compatible with the old boot-loader . The above is the reason for the boot-loader change.. Google is aware of the troubles everyone in this thread is having . I would be looking for a new very tiny update in the near days. Just a guess im wondering if the truth is they are gearing up for the 3g version of nexus .maybe the pm chip being changed has a issue with the added radios. They did say ITS NOT A Chip upgrade but will not say why they are making the switch .
sorry i do not have a link . but everyone knows how to get to google groups ..
Happy Reading..

I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.

smirkis said:
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
Click to expand...
Click to collapse
Just to clarify, going from bootloader->recovery never worked for me either. Whenever I needed to get into recovery mode, I just opened up a terminal, su'd to root and then ran "reboot recovery", or occasionally doing it via adb. However, those methods always worked for me until I upgraded to the latest bootloader. Then, no custom recoveries would load via any method.
My Nexus7 was first generation. I actually picked it up in Sams Club the day before they were officially released. So if Google made any HW changes in the different revisions, that might explain the difference in results on 4.1.2. Though I imagine most people on XDA also picked theirs up out of the first batch, so I don't think that could be the case. What seems more likely is that there are minor hardware differences that are causing some people's to fail with the 3.41 bootloader, while most don't have that issue. It will be interesting to see if you experience the same issue on your new one though.

gunner1937 said:
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
Click to expand...
Click to collapse
It didn't worked for me. I've tried Rootkeeper apk, but it was useless.
This was driving me crazy until I've found this topic! I've tried resetting it to original settings, using rootkeeper and traditional methods, nothing, zero!
At last, phonic saved my life, and finally I a could root my Nexus 7!

I never responded but my RMA worked as it should. but the issue has been resolved with recovery updates from the developers. the rest of the world who had issues should be good to go. I ended up selling my 16gb unit and got a 32 and it works as it should as well. are we all happy campers now?
Sent from my Nexus 7 using xda premium

I've had similar experiences where the way certain kernels install zips are packaged, the wipe custom recoveries at install. In that situation, I've never wiped anything from system, but rebooted into bootloader and fastboot boot recovery "recovery.img". Then from there install the recovery.zip. The worst is when this happens when you get flash happy away from home and the kernel doesn't work. No way to fix without a comp w/SDK. Glad you're back up and running.
(I cannot be held responsible if the aforementioned damages your device; do the research and own the process.)

I am so glad to have found this thread. This problem was beginning to drive me nuts.

[Q] Vertical lines appeared on my screen today...

Had the phone for about 24 hours. Had no issues last night as I rooted though adb with ioroot and flashed recovery using AutoRec. I then did a full wipe and flashed xdabbeb's ROM, kernel, and alarm fix. I let it run all night and shut it off to install SIM. Installed SIM and when it booted back up the LG screen went white and now I have the the vertical lines in the image attached. The lines are now preset no matter what I do. Do I need to return to stock and return/replace or is this a problem with the methods I used?
Any help would be greatly appreciated!! The phone itself seems stable enough...and I know LG has some quality issues, but damn..
UPDATE with further details:
ioroot v25 to root via adb
vs980 AutoRec to flash 2.7 TWRP
backed up EFS
nandroid backup
full wipe
flashed xdabbeb VS98024A v1.1.1
flashed xdabbeb alarm fix
flashed xdabbeb kernel 1.1.0
panel type is LGD
Let it run all night, took it off the charger this morning and powered it off to put SIM in. Phone rebooted instead and I thought, "that's weird".. Powered it off and it rebooted again, "oh sh!t", I thought.. Then the LG logo came up and sorta went inverse of the colors...white with a dark greenish logo.. Held down the power again and it rebooted again and the normal logo came up but with a parallel white line and the LG logo kinda off center.. Then when the ROM booted up all the way I noticed the horizontal dark lines staggered down then right side of the device. Stays that way in recovery and even after loading stock backup. Guess I gotta get it back to stock and swap it at BB. Pic attached!
Hope this helps people figure out the issue.. Makes me wary of LG phones for sure. Say what you will but my M7 didn't do this [email protected]!

Return it to stock using the guide in the general section, take it back to Verizon and get it replaced under warranty. There's been a rash of issues lately with certain roms/kernels/or other causing damage to the screen.
More about it here - http://forum.xda-developers.com/showthread.php?t=2769770

mjones73 said:
Return it to stock using the guide in the general section, take it back to Verizon and get it replaced under warranty. There's been a rash of issues lately with certain roms/kernels/or other causing damage to the screen.
More about it here - http://forum.xda-developers.com/showthread.php?t=2769770
Click to expand...
Click to collapse
I reported in that post as well with a bit more detail. If I bought this thing at BB I should just be able to take it in and swap it right? I'll return it stock for sure.

F1fan07 said:
I reported in that post as well with a bit more detail. If I bought this thing at BB I should just be able to take it in and swap it right? I'll return it stock for sure.
Click to expand...
Click to collapse
As long as it's still under warranty you should have no problem taking it back to BB.

swapped for a new one at bb today with no issues
going to try Mahdi as I'm not a fan of the modded stock ROMs
also got the other type panel, jdi?

I am curious about something with the whole black line issue. I think I may have another idea. Please input for this will help confirm. What if it has something to do with downgrading the bootloader with autorec? Can anyone confirm keeping JB and installing xdabbebs 24a bootstack did this also?
Could it possible have something to do with autorec? Like I state before I am not pointing blame, but I read alot of post where people stated this has happened to them where they used autorec for kitkat and then installed? Maybe there is something where kitkat isnt working well with autorec downgrading the bootloader. If you downgrade any software with a newer upgrade wouldnt that cause instability within the kitkat itself?
What I am thinking is maybe the downgrade of the bootloader is causing over heating since it wasnt made for kitkat? Maybe it sounds stupid but what if? I remember having the black lines happen once before on a gnex I had and if i recall at one time you had to downgrade part of the software to gain custom recovery. My phone in fact got the black lines. What if we find a way to reupgrade the back to kitkats original bootloader and see if that fixes the black lines.
I know there was one case where someone claimed they got it after the OTA for kitkat, but could there be a possiblity that autorec was used in this case also?

simple_fear85 said:
I am curious about something with the whole black line issue. I think I may have another idea. Please input for this will help confirm. What if it has something to do with downgrading the bootloader with autorec? Can anyone confirm keeping JB and installing xdabbebs 24a bootstack did this also?
Could it possible have something to do with autorec? Like I state before I am not pointing blame, but I read alot of post where people stated this has happened to them where they used autorec for kitkat and then installed? Maybe there is something where kitkat isnt working well with autorec downgrading the bootloader. If you downgrade any software with a newer upgrade wouldnt that cause instability within the kitkat itself?
What I am thinking is maybe the downgrade of the bootloader is causing over heating since it wasnt made for kitkat? Maybe it sounds stupid but what if? I remember having the black lines happen once before on a gnex I had and if i recall at one time you had to downgrade part of the software to gain custom recovery. My phone in fact got the black lines. What if we find a way to reupgrade the back to kitkats original bootloader and see if that fixes the black lines.
I know there was one case where someone claimed they got it after the OTA for kitkat, but could there be a possiblity that autorec was used in this case also?
Click to expand...
Click to collapse
I think it's safe to say most people flashing roms that had this happen had already been running a downgraded aboot so they could flash TWRP way before it happen.

Otro mas
Otro mas con este problema...

Got same problem mine is not showing anything but only vertical and horizontal lines all over the screen. please help

[Q] soft bricked at&t note 3

I rooted through towelroot. Then I installed safestrap and alliance rom. This all occurred around 6:00 am this morning. Everything installed and was working. I woke up around 9:30 and started cleaning up my instal i.e. settings in Nova, hiding unnecessary apps the like and then i realized that my phone would not connect to wifi. I tried all of the pedestrian stuff like remove battery, toggle wifi on and off and toggle the airplane mode on and off. Still no wifi. Then I went back into Safestrap and the goal was to reflash the rom. But I think that i wiped the wrong partition or something because i have been stuck at the note 3 splash screen with the custom lock symbol. I went to Best Buy to see if they could flash the factory image, Nope. Then i came how and tried kies, it would not recognize my phone. I am trying to flash back to factory preferably without root. I youtubed and found an old video with an old file at Sammobile. and i am currently downloading it and odin 3. Am I on the right track or am i screwed? I have not rooted a phone since my Droid Razr Maxx. Please Help This is the only thing that i have to communicate with my family. And yes, I am an idiot

7 views no suggestions
tyroniousdex said:
I rooted through towelroot. Then I installed safestrap and alliance rom. This all occurred around 6:00 am this morning. Everything installed and was working. I woke up around 9:30 and started cleaning up my instal i.e. settings in Nova, hiding unnecessary apps the like and then i realized that my phone would not connect to wifi. I tried all of the pedestrian stuff like remove battery, toggle wifi on and off and toggle the airplane mode on and off. Still no wifi. Then I went back into Safestrap and the goal was to reflash the rom. But I think that i wiped the wrong partition or something because i have been stuck at the note 3 splash screen with the custom lock symbol. I went to Best Buy to see if they could flash the factory image, Nope. Then i came how and tried kies, it would not recognize my phone. I am trying to flash back to factory preferably without root. I youtubed and found an old video with an old file at Sammobile. and i am currently downloading it and odin 3. Am I on the right track or am i screwed? I have not rooted a phone since my Droid Razr Maxx. Please Help This is the only thing that i have to communicate with my family. And yes, I am an idiot
Click to expand...
Click to collapse
i must be screwed several views and no replies. Please help. I have learned my lesson. I knew how to root, I just was not that familiar with the recovery.

Go here do this http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my SM-N900A using Tapatalk

thanks
jerrycoffman45 said:
Go here do this http://forum.xda-developers.com/showthread.php?t=2703006
Sent from my SM-N900A using Tapatalk
Click to expand...
Click to collapse
Thank You Jefferey coffman 45. I PM'ed Walter White 2 hours ago and he turned me on. This was the longest i ever went without a solution. I was a little puckered.

Hi Sir. I have the EXACTLY the same problem you had. First, my wifi stopped working so I wiped cache. After Wiping the phone is stucking at splash screen with the custom symbol. Have you figured out a way to fix your phone? If you do, would you mind share the process with me please? Thanks a million in advance.

s205702 said:
Hi Sir. I have the EXACTLY the same problem you had. First, my wifi stopped working so I wiped cache. After Wiping the phone is stucking at splash screen with the custom symbol. Have you figured out a way to fix your phone? If you do, would you mind share the process with me please? Thanks a million in advance.
Click to expand...
Click to collapse
Guys, just flash MLG on with Odin. Install the NC2 Kernel w/ Odin and root w/ Toweroot and Safestrap. Then you can reflash a new rom.
Edit: Here is a good guide: http://forum.xda-developers.com/showthread.php?t=2703006
Note: Must have NC2 bootloader which im sure you do since you used towelroot.

Touch Screen issues after root

So I was going through the process of rooting my phone, and after I rooted my phone with CF auto root my touch screen calibration is all off for my touch screen with the diparity getting greater the further to the right and the further down you go on the screen, but my s-pen works at is should. Is this a known issue, or is there a way to fix this?
I have tried flashing different roms, and un rooting as well as a different recovery, but even in the recoveries the screen is not calibrated properly.
Did I just suffer bad luck and lose my touch digitizer at the same time?

I really haven't heard of anything like this. Don't wait to long to return if you still can
BAD ASS NOTE 4

Recalibrate

Karakoram2 said:
Recalibrate
Click to expand...
Click to collapse
How do you go about doing that? I don't have the problem, only with a certain rim. Wanted to see if that worked
Sent from my SM-N910T using XDA Free mobile app

Karakoram2 said:
Recalibrate
Click to expand...
Click to collapse
Do you know of an app to do it or the code.
BAD ASS NOTE 4

Karakoram2 said:
Recalibrate
Click to expand...
Click to collapse
I tried the *#0*#, but I cant even get that to work since its so inaccurate,

Looking into it:
http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/

Looks like they are making it harder.
We are flashing so hard we didn't notice.
Honestly flash firekat and use it as a base.
But, we'll have a better answer soon.

I'm having the same exact problem here.
I have illustrated the problem in the attached photo, just to make it clear.
My phone is Note 4 Sprint
I have flashed custom and stock firmware but ends up with no luck
Hope to find the solution here :good:

Finally found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/showthread.php?t=2144166

Exact same issue here as well. After rooting my phone and installing CM 12 on it all of a sudden my touchscreen calibration is waaaay off. Its more pronounced the further down the screen you go (ie I click in the 2/3 section top to bottom to click on the actual bottom) but with the s-pen everything is fine. I tried the code dial *#2663# but then I receive the prompt "connection problem or invalid mmi code". I am connected to the mobile network (Rogers in Canada) and mobile data is working without issue. I've tried completely wiping the phone again, all partitions and reformatting system, reflashing CM12 + gapps and still the issue persists. Google-fu isn't turning up with much either, please help!

Did you do it with Odin.

Yes I rooted it with Odin using CF-Root as with all my past Samsung devices (specifically this link: download.chainfire.eu/563/CF-Root/CF-Auto-Root/CF-Auto-Root-trltecan-trltecan-smn910w8.zip). TWRP recovery was flashed with version 2.8.1.0 (don't have the original link at hand but filename is: openrecovery-twrp-2.8.1.0-trltecan.img), following with CM 12. I've tried reflashing the root as well and it did not help. Screen calibration is off even in TWRP but as mentioned before s-pen works fine.

Update on this, I flashed back to a stock (but flashable) ROM. Ran the *#2663# screen firmware fix, which resolved the inconsistency. Booted back into recovery, re-flashed the AOSP ROM (Beanstalk in my case, I was trying it as I thought CM was my issue initially (which I know was wrong)) and everything is good.
Very frustrating but at least now it works. Replying to SMS messages with the s-pen made me feel like my father typing....

Well you can root only in android 2.2 or below because if you root in a lastest version on android it would not work it will crash your phone it will delete system files which you cannot restore, it critical job to do and very dangerous, I notice that some ones phone got rooted and does not work by someone rooting it to cyangemod,which delete the whole system files, well if you rooted your phone there will be lots of problem that you may not like, the rooting can do anything in your phone.

HDL4E said:
Finally found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/showthread.php?t=2144166
Click to expand...
Click to collapse
Thanks for finding this thought i had a busted note

you saved my note 4!
HDL4E said:
Finally found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/showthread.php?t=2144166
Click to expand...
Click to collapse
thank you for this info!! you saved my note 4 . i was having some touch screen issues!

HDL4E said:
Finally found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/showthread.php?t=2144166
Click to expand...
Click to collapse
Oh, Thank You! This restored my Note 4 after I had accidentally flashed the wrong recovery image (which screwed up my touch screen calibration, but luckily nothing else). Kudos!!!
---------- Post added at 08:40 AM ---------- Previous post was at 08:35 AM ----------
HDL4E said:
Finally found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/showthread.php?t=2144166
Click to expand...
Click to collapse
Oh, Thank You! This restored my Note 4 after I had accidentally flashed the wrong recovery image (which screwed up my touch screen calibration, but luckily nothing else). Kudos!!!

HDL4E said:
Finally found a solution
dial *#2663# and update the touch FW by pressing "TSP FW update (General)".
All credit goes to charlieb620 on this post:
http://forum.xda-developers.com/showthread.php?t=2144166
Click to expand...
Click to collapse
Thank you so much this was the exact fix my phone needed. I've spent so much time with @Flashvetrin trying to figure it out
Thank you thank you Thank you

re: screen calibration issue
Dockadocka said:
So I was going through the process of rooting my phone, and after I rooted my phone with CF auto root my touch screen calibration is all off for my touch screen with the diparity getting greater the further to the right and the further down you go on the screen, but my s-pen works at is should. Is this a known issue, or is there a way to fix this?
I have tried flashing different roms, and un rooting as well as a different recovery, but even in the recoveries the screen is not calibrated properly.
Did I just suffer bad luck and lose my touch digitizer at the same time?
Click to expand...
Click to collapse
Don't worry, here is the fix for it.
I had the exact same problem a few weeks ago.
Go to the dialer screen and click in:
*#2663# screen fix works perfect, it will display a menu, select re-calibrate
or update or something to that effect, ( I forgot the exact wording)
But when you see that menu screen you will know which one to click.
You might have odin flashed the wrong twrp for the phone, but either
way this will fix it.
I would suggest that before you do this, odin flash the n910t
stock samsung firmware, that way twrp will get over-written.
Good luck,
Have a great day!

[Q&A] VS980 Resources - Bootstacks/Modems/Unofficial FW/Manual OTA/etc

Q&A for VS980 Resources - Bootstacks/Modems/Unofficial FW/Manual OTA/etc
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 VS980 Resources - Bootstacks/Modems/Unofficial FW/Manual OTA/etc. 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!

MicroMod777 said:
Sweet. Did you post you tried the bumped twrp on the 39a and it didn't work. Last time I remember they had to rebuild twrp based on 26a. It might need to be rebuild on 39a sources.
Click to expand...
Click to collapse
xdabbeb said:
Nope. No idea what the point of that is.
Click to expand...
Click to collapse
Following the links, it looks like there's a new root exploit using download mode for a number of LG devices - http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772

Help
With these zip files. Are we able to use twrp and jump back and forth between boot loader versions or once you go past a certain boot loader you have to revert back to stock or use a special process to down grade.

protfire said:
With these zip files. Are we able to use twrp and jump back and forth between boot loader versions or once you go past a certain boot loader you have to revert back to stock or use a special process to down grade.
Click to expand...
Click to collapse
You can, but when switching between different based roms you'll often need to flash stock to get your sensors working again.
Sent from my LG-VS980 using XDA Free mobile app

Looking for some guidance
Having some issues with getting setup to flash VS982.5
Had a replacement phone sent from Verizon because of a dead digitizer. The phone shipped with 27A. I was able to get it rooted and got recovery installed, but then started running into issues. From there, I used the 11A tot. Got rooted, used Autorec for recovery and then tried flashing 28A, but am now getting a secure boot error.
Anyone have any advice?
@xdabbeb ???

noob question
Ok been flashing for a while nexus 7 - nexus 7 2013 and nexus 10 but this lg is a diiferent animal so im on broadbase 26a and can flash all cloudys roms but cant get lollipop roms to flash tried flashing the 39a and it rebooted but no data so went back to 26a broadbaseand all worked again so my question is can i flash 39a with the 26a modem and make flashing lollipop Possibly. Im on the verizon vs 980 model. Thanks in advance

Help please!
Sorry - I've not had to ask for help much, but I may have flashed the bootstack incorrectly.
I was on xdabbeb's VS980 v2.3.0 (26A), and I wanted to update to his VS982.5 1.2.0. I thought I could just go into my TWRP and flashed the new bootstack.
Ooops - now I'm getting that secure booting error. Anyone know how to fix this?
---------- Post added at 04:37 AM ---------- Previous post was at 04:27 AM ----------
Sorry - I've not had to ask for help much, but I may have flashed the bootstack incorrectly.
I was on xdabbeb's VS980 v2.3.0 (26A), and I wanted to update to his VS982.5 1.2.0. I thought I could just go into my TWRP and flashed the new bootstack.
Ooops - now I'm getting that secure booting error. Anyone know how to fix this?

kongo101 said:
Sorry - I've not had to ask for help much, but I may have flashed the bootstack incorrectly.
I was on xdabbeb's VS980 v2.3.0 (26A), and I wanted to update to his VS982.5 1.2.0. I thought I could just go into my TWRP and flashed the new bootstack.
Ooops - now I'm getting that secure booting error. Anyone know how to fix this?
Click to expand...
Click to collapse
So, after 3 hours of fiddling around, I figured it out.
1. I was in the process of using the unbrick method where you hop onto Linux and dd those 5 files to fix the error and unbrick your phone from the loop. However, I realized that method is for folks who actually still have a ROM installed. I had just wiped to install the XDABBEB's 482.5 FW and there was no other FW installed. Stupid.
However, I still had my internal SD card stuff (photos, Titanium backups, etc) that were on the phone somewhere.
2. Somewhere along the line of frustration, I thought that the only way was to get a replacement (insurance) phone, which would mean losing all my data anyways. During that time, I somehow got into fastboot mode. Then I tried flashing the stock 11A FW. Somehow, it worked! (I lost all my internal SD data though, sadly).
3. I took all the OTA updates to 28A. Then I rooted with IOroot, installed TWRP with AutoRec. Then I flashed XDABBEB's 28A bootstack and on the restart, I got that same stupid secure boot error and black screen. I was VERY upset at that point.
4. I did the Vol Down + Power button hold to get into recovery, and when it asked me if I wanted to factory reset, I simply said yes, and it brought me back to TWRP. I flashed XDABBEB's ROM and on the reboot, everything was fine
I'm sure most of this stuff just sounds dumb. I probably could have just got into recovery from the very beginning (step 4) and just flashed XDA's Rom and all of this would have been unnecessary. However, as soon as I saw the "secure boot error" I freaked out and started browsing XDA and jumped the gun. Lesson learned.
Thanks still, for the XDA resources so that I could eventually figure this out on my own, even the long way.
Thanks,
David.

kongo101 said:
So, after 3 hours of fiddling around, I figured it out.
1. I was in the process of using the unbrick method where you hop onto Linux and dd those 5 files to fix the error and unbrick your phone from the loop. However, I realized that method is for folks who actually still have a ROM installed. I had just wiped to install the XDABBEB's 482.5 FW and there was no other FW installed. Stupid.
However, I still had my internal SD card stuff (photos, Titanium backups, etc) that were on the phone somewhere.
2. Somewhere along the line of frustration, I thought that the only way was to get a replacement (insurance) phone, which would mean losing all my data anyways. During that time, I somehow got into fastboot mode. Then I tried flashing the stock 11A FW. Somehow, it worked! (I lost all my internal SD data though, sadly).
3. I took all the OTA updates to 28A. Then I rooted with IOroot, installed TWRP with AutoRec. Then I flashed XDABBEB's 28A bootstack and on the restart, I got that same stupid secure boot error and black screen. I was VERY upset at that point.
4. I did the Vol Down + Power button hold to get into recovery, and when it asked me if I wanted to factory reset, I simply said yes, and it brought me back to TWRP. I flashed XDABBEB's ROM and on the reboot, everything was fine
I'm sure most of this stuff just sounds dumb. I probably could have just got into recovery from the very beginning (step 4) and just flashed XDA's Rom and all of this would have been unnecessary. However, as soon as I saw the "secure boot error" I freaked out and started browsing XDA and jumped the gun. Lesson learned.
Thanks still, for the XDA resources so that I could eventually figure this out on my own, even the long way.
Thanks,
David.
Click to expand...
Click to collapse
The answer was to simply rebooting into recovery after flashing the bootstack, rather that rebooting the system. That would have prevented the secure boot error. Lesson learned the hard way.

Hey, tryna get my head to stop spinning after the loads of info I just memorized trying to figure all this stuff out. I'm trying to flash a CM12 official nightly on stock 5.02 and TWRP 2.8.5.1. I just used bouchigo's little guide to get the 28A aboot and bumped boot and recovery to see if that would let me flash CM12/the updated TWRP 2.8.6.0 and neither worked (I'm assuming because it's not 12b still). So now I'm about to try to use the 39A zip in here and then flash the 12b bootloader, but I'm not sure exactly how to do it. Do I just flash both in TWRP and then do the reboot to recovery? I tried to flash the new TWRP (2.8.6.0) in TWRP and it gave me the same loki error as CM12 did so not sure it will work that way with this? Also will it mess anything up with the bouchigo images I have installed/should i flash my stock backup before I flash the 39A? And once I install the boot stack can I just flash 12b boot loader and be good to go to install CM12?
Also is there anything major to be concerned about while messing with this boot stack stuff or will it mostly be recoverable problems where you can just flash your backup? Sorry for the general question. You don't have to go into too much detail or anything, just tryna make sure there's not something you would be more likely to do (like rebooting to system instead of recovery) trying to configure the boot stack to work for your needs. Thought it may be helpful for others also as I haven't seen too many (more specific and/or general) caution tips in the threads I've visited in the last few days, especially in the OP's. No offense to any of you developers or anything, just something I thought might be helpful in future posts (especially for semi-casual's and noob's like me lol). With that said I'm very grateful for all the information on this site and the devs for their time. Keep up the amazing work. And thank you in advance for the knowledge!

I'm confused with an issue I'm facing with my Vs980 on Tmobile, so might as well ask this here before I mess up the phone any further.
After flashing 39a kdz I was able to get LTE connectivity, but battery lifetime was kinda poor. A few posts reported improvements with a factory reset ... so I did just that. Battery lifetime was even worse ... so why not another factory reset? I did just that and LTE wouldn't come back on. The phone starts, shows full network, and 4G for a second ... then network connectivity becomes glitchy going on/off constantly. The only way to get a stable network connection was to go into the settings and change the network connectivity to UMTS/HSPA instead of the LTE/3GPP .
I tried flashing 27a kdz, but the same issue keeps on happening. Now I'm debating whether I should be flashing just the 39a modem from this post after a clean 39a kdz flash ... but I can't make much sense out of this thought.
Any ideas on what could be done to resolve this problem?

It works perfectly. Congrats!!!!

I have a question.. I'm on stock rooted 39a..do I need to flash bootstacks or can I just flash roms?
Sent from my VS980 4G using Tapatalk

Kilroy245 said:
I have a question.. I'm on stock rooted 39a..do I need to flash bootstacks or can I just flash roms?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I flashed the rom without bootstacks but in twrp, if it goes into sleep, i get a dead screen with lines which I need to reset with adb command
adb reboot
On 39A rooted and twrp

vs980 39a Bootstack lollipop no cell signal or service
i have this lg g2 vs980, i was running an old xdabbeb 24a bootstack with a KK lg g2 rom on cricket service everything worked good besides bluetooth. (rooted&twrp recovery)
since then i have flashed twrp 2.8.6.3 bump-blastgator. i followed xdabbeb instructions for flashing 39a bootstack and xdabbeb_vs980_312.zip but i have no cell signal. i also tried LP-TMO-Extreme rom with a t-mobile simcard and apn and it didn’t work either. i was wondering if someone here can help, i tried flashing this rom and bootstack in every combination i could imagine, and still no signal.
i also flashed the 24a bootstack back and KK rom back and now still no signal. can someone please help me, I’m out of ideas.
thanks in advance!

Error loki-ifying
Hello, following your directions at http://forum.xda-developers.com/verizon-g2/development/vs98039a-stock-fw-t3051560, I was trying to flash the 39a bootstack zip from CWM on a VS980 10B. After the extractions, I got this message:
Code:
Finished!
script succeeded: result was [Finished]Checki
ng if loki-fying is needed/dev/block/platform/
msm_sdcc.1/by-name/boot needs lokifying.
[-] Failed to find function to patch.
Error loki-ifying the boot image.
I'm confused because it both says the script succeeded and that there was an error.
When I rebooted, I went into a bootloop. I got back into recovery. My recovery is now TWRP. I went ahead and flashed the 38A firmware, and everything seems to have worked out just fine.
Do I need to worry about the error I got flashing the bootstack?