Database Develop

[Q] Problems Installing - ★AMCHA Rom v5.00

So I've tried installing this half a dozen times, I did a full wipe I'm using the i9305 and installing this using both kernel options for the knox based bootloader, after it completes installation it says complete, reboot the phone and I end up stuck at the Samsung Galaxy s3 black screen and it never boots into the os.
I noticed while installing this it installs some modem not sure what one it is but I thought perhaps that was the issue, to installed went straight into download mode and flashed a optus modem i've been using for my phone rebooted but still same issue.
Would appreciate some help with this, I've tried searching the thread for similar issues no such luck.
Thanks

Demonic Wraith said:
So I've tried installing this half a dozen times, I did a full wipe I'm using the i9305 and installing this using both kernel options for the knox based bootloader, after it completes installation it says complete, reboot the phone and I end up stuck at the Samsung Galaxy s3 black screen and it never boots into the os.
I noticed while installing this it installs some modem not sure what one it is but I thought perhaps that was the issue, to installed went straight into download mode and flashed a optus modem i've been using for my phone rebooted but still same issue.
Would appreciate some help with this, I've tried searching the thread for similar issues no such luck.
Thanks
Click to expand...
Click to collapse
maybe your using a old recovery?

MaHo_66 said:
maybe your using a old recovery?
Click to expand...
Click to collapse
Thanks but it's not that, I wasn't even aware of having to use the newer one for the recovery till recently and have been using the one for the old recovery even tho I have the new one... either way, I tried installing both the new and old recovery's same results.

Demonic Wraith said:
Thanks but it's not that, I wasn't even aware of having to use the newer one for the recovery till recently and have been using the one for the old recovery even tho I have the new one... either way, I tried installing both the new and old recovery's same results.
Click to expand...
Click to collapse
i see, well your 2 posts away from being able to post in development thread, you will get better help in rom thread try a full wipe anyway and install the rom with default aroma settings, maybe the problem lies in some setting you change in aroma installer..

MaHo_66 said:
i see, well your 2 posts away from being able to post in development thread, you will get better help in rom thread try a full wipe anyway and install the rom with default aroma settings, maybe the problem lies in some setting you change in aroma installer..
Click to expand...
Click to collapse
True, that could be it, except i thought of that myself and just hit next next next to the end and hit install to see if it would help matters it didn't. Yeah I tried posting there to begin with, but even if your an advanced person you have to post here first lol fun times
I did think maybe there's a newer version of philz recovery out and mine just buggers it up some how it offers to install 6.41.6 not sure what my version is.. it crossed my mind tho but I wouldn't presume that's the most likely of causes.

Demonic Wraith said:
True, that could be it, except i thought of that myself and just hit next next next to the end and hit install to see if it would help matters it didn't. Yeah I tried posting there to begin with, but even if your an advanced person you have to post here first lol fun times
I did think maybe there's a newer version of philz recovery out and mine just buggers it up some how it offers to install 6.41.6 not sure what my version is.. it crossed my mind tho but I wouldn't presume that's the most likely of causes.
Click to expand...
Click to collapse
hmm.. well philz 6.41.6 is the latest one a.t.m and roms these days need up to date recovery so you can give it a shot if you are not on philz yet. here is the latest one http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
flash it with odin then try again, hopefully this will fix your problem

MaHo_66 said:
hmm.. well philz 6.41.6 is the latest one a.t.m and roms these days need up to date recovery so you can give it a shot if you are not on philz yet. here is the latest one http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
flash it with odin then try again, hopefully this will fix your problem
Click to expand...
Click to collapse
Yeah unfortunately that didn't work either, was worth a shot tho now I can post in the proper place.

Demonic Wraith said:
Yeah unfortunately that didn't work either, was worth a shot tho now I can post in the proper place.
Click to expand...
Click to collapse
haha yeah man

At&t S 5 Active Restore Thread (NE4) (NO MORE SUPPORT)

NO MORE SUPPORT.....GAME OVER
Did you delete your data, system, safestrap is gone, only download mode and stock recovery are available? Do you want to start fresh and out of the box new?
(( FOR s 5 ACTIVE )) NE4​Thanks to @ted77usa & @Intub8 for the help. SAM MOBILE for the Firmware and steps. KNOX was not tripped. Nothing was after this. It worked perfectly.
Just FOLLOW INSTRUCTIONS
Do this at your own risk. If you don't read and mess up your phone, its not my fault . As long as you can get into download mode, this will help out a lot. I am not responsible for what you do to your device.
Odin Back to s5 Active Stock. NE4​
Make sure you have the Samsung drivers installed before starting.
Samsung USB drivers
Make sure USB debugging is checked under settings/developer options. If you don't know how to do that, go to "about device" in settings, and click on "Build Number x5 till you unlock Developer options".
Extract (unzip) the firmware file (NE4) HERE
Download Odin v3.09 HERE
Extract Odin zip-file
Open Odin v3.09
Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait a few minutes
Note : Some users are getting stuck at long At&t screen, once odin finishes and you happen to get stuck, reboot to stock recovery and factory reset your phone.
It should boot up just fine after that. The At&t screen sometimes takes a while.
​
You can do this below if you want. I have done this about 5 or 6 times. #6 and 7 happens sometimes.​
I wanted to be totally fresh and wanted to use "Wipe Data (YES)" in safestrap. Here is what I did and what happened.
My phone has been really good since this and all is smooth.
Things to do to be fresh and start all the way over out of box style:
1. Make sure you have done a back up, and your ready to restore with Odin.
2. Go into Safestrap
3. Go to WIPE tab > Factory reset
4. Advanced wipe, (Wipe > Dalvik Cache, "NOT Micro SDcard"> Data, Cache, System)
5. For really starting over > next to Advanced wipe is "Format Data" do that and type YES
6. This will get rid of safestrap and everything so you will get a black screen once it deletes all.
7. Try to catch it and go into download mode before it boots to the Samsung screen (Which it will stay there FOREVER)
(As soon as your phone does this, try to catch it before the samsung screen and go into download mode. When it turns black, quickly hold Power + Volume down + home button. )
8. While in download mode, flash the restore firmware.
9. Let it do its thing and you will be factory new.
10. After it all settles down and you are back up and running, you can start like I do.
(Root with V3 (Make it Rain), Install and update SU, Reboot 3 times lol, install busybox, install safestrap, install xposed, reboot, install your modules, reboot, power down and boot back but go into safestrap and wipe dalvik cache and regular cache. Reboot. lol- Install all your apps you like or have your backups from titanium on your sd card and restore) Reboot and go into safestrap again and fix permissions and reboot lol...... BAM. (Your phone should be sick and you should throw up on it)
LINKS
NE4 (THE MAIN FILE YOU NEED)
[KITKAT:ND3]
LATEST BETA FILE: Safestrap-KLTEATT-ND3-3.75-B03.apk
XDA Downloads Safestrap
Mirror 1 (Crackflasher) Safestrap
BUSYBOX
SUPERSU

Just make sure the model number matches yours and you should be all set. That file should contain everything you need to get back to stock. Follow the directions listed underneath the firmware.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app

Thanks. All is good and I can confirm this works on the At&t S 5 Active (NE4).
I am fresh to start over.
Edit: All is good. Rooted, Busybox, Froze bloat etc. Safestraped, Backuped, Phone is running great!!

Intub8 said:
Just make sure the model number matches yours and you should be all set. That file should contain everything you need to get back to stock. Follow the directions listed underneath the firmware.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. Its working!!!!! I thought this wasn't out yet. Looks out to me.
I will update OP and get on my XDA app to hit thanks. Thanks for pointing out the simple directions I failed to see on SAM mobile. My phone is back

LuckyColdJohnson said:
Thanks. Its working!!!!! I thought this wasn't out yet. Looks out to me.
I will update OP and get on my XDA app to hit thanks. Thanks for pointing out the simple directions I failed to see on SAM mobile. My phone is back
Click to expand...
Click to collapse
Glad that worked out for u bud.....[emoji41][emoji106]
☆Swyped From SFive SS Edition☆

I wonder if this would work on the regular S5? If someone tries and it does please report back....THanks

LuckyColdJohnson said:
I wonder if this would work on the regular S5? If someone tries and it does please report back....THanks
Click to expand...
Click to collapse
WWWHYY would you even want to know if this will work when you have your own firmware?! Then you try and convince someone else to take the plunge and try instead of you doing it? Just wondering why... cause i'm very baffled right now.

Caliesv said:
WWWHYY would you even want to know if this will work when you have your own firmware?! Then you try and convince someone else to take the plunge and try instead of you doing it? Just wondering why... cause i'm very baffled right now.
Click to expand...
Click to collapse
Uhhhh. I'm sorry you feel that way. I was running s 5 ROMS just fine on my phone. Their basicly the same but with a few different specs.
What plunge are you talking about dude? I have soft bricked my phone (formated data) and used this to start fresh. The more we know the better. I have done it. Its fine. I have ran NCE NE4, you must not know whats going on here. That what this thread is for. Restoring your phone to factory defaults. I have done it for the Active and if someone did it on their regular s 5 than I want to know.

LuckyColdJohnson said:
Uhhhh. I'm sorry you feel that way. I was running s 5 ROMS just fine on my phone. Their basicly the same but with a few different specs.
What plunge are you talking about dude? I have soft bricked my phone (formated data) and used this to start fresh. The more we know the better. I have done it. Its fine. I have ran NC2 NE4, you must not know whats going on here. That what this thread is for. Restoring your phone to factory defaults. I have done it for the Active and if someone did it on their regular s 5 than I want to know. THATS IT. Now go here for being mean > CLICK ME @Caliesv
Click to expand...
Click to collapse
LOL! nice actually made me laugh! lol i hear ya man. i was just wondering why. and you full fulled my wondering. thanks

Caliesv said:
LOL! nice actually made me laugh! lol i hear ya man. i was just wondering why. and you full fulled my wondering. thanks
Click to expand...
Click to collapse
Its all good. I'm glad I made you laugh too. Really. I'm just messing with ya a little....This thread is for Active users. Like I said, if this can work for the regular S 5, then I will update the OP for S5/S5 Actives only. Thats all. I was on NCE (A regular S 5 ROM) when I did this and it worked perfectly.

LuckyColdJohnson said:
Its all good. I'm glad I made you laugh too. Really. I'm just messing with ya a little....This thread is for Active users. Like I said, if this can work for the regular S 5, then I will update the OP for S5/S5 Actives only. Thats all. I was on NCE (A regular S 5 ROM) when I did this and it worked perfectly.
Click to expand...
Click to collapse
No worries man lol. yeah i have an active too. i hope we get our own thread soon. And thanks for the steps, tons of people are going to need it lol

Caliesv said:
No worries man lol. yeah i have an active too. i hope we get our own thread soon. And thanks for the steps, tons of people are going to need it lol
Click to expand...
Click to collapse
10-4.....It really helped me when I screwed up. This worked 100% for me. I have flashed over 5 different ROMS from T-Mobile, International, as well as At&t ROMs we have. Sometimes its better to start all the way over fresh. Sometimes we get into a pickle and need to start over. This will help us.....Thanks !!!!

Continued thanks for being our official S5 Active tester. I'm glad to hear you got it back to running and that you were able to find the firmware for our G870A. This will come in handy when I get my phone past the point of no return, it usually takes me a month or so but I'll get there.
Please keep us informed as your tests, trials and discoveries continue!

thepktrckt said:
Continued thanks for being our official S5 Active tester. I'm glad to hear you got it back to running and that you were able to find the firmware for our G870A. This will come in handy when I get my phone past the point of no return, it usually takes me a month or so but I'll get there.
Please keep us informed as your tests, trials and discoveries continue!
Click to expand...
Click to collapse
No problem. Looking at a GPS issue now. Something has screwed it all up. Probably a module or two (exposed) Almost tempted to restore again and test before each install.
Sent from my SAMSUNG-SM-G870A using XDA Premium 4 mobile app

If you go back to stock and the GPS still doesn't initiate let me know. There was a way to hard reset the GPS that I came across on the gs3 that may work. Every time I flash a rom if it's acting goofy I wipe everything and go back to 100% stock. Sometimes things get stuck and left behind that can muck things up. Think of it like a colon clense for your phone. Glad the Odin worked for you.
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app

Intub8 said:
If you go back to stock and the GPS still doesn't initiate let me know. There was a way to hard reset the GPS that I came across on the gs3 that may work. Every time I flash a rom if it's acting goofy I wipe everything and go back to 100% stock. Sometimes things get stuck and left behind that can muck things up. Think of it like a colon clense for your phone. Glad the Odin worked for you.
Sent from my SAMSUNG-SM-G900A using XDA Premium HD app
Click to expand...
Click to collapse
Yes, Please share if you don't mind. I broke the GPS lol. I don't believe flashing this official firmware did it though, I think flashing different ROM's did it but who am I......I found a GPS fix I used for my Note 3 (Kit Kat) You have to flash it in recovery. Is that how yours is? Here is the file for you to check out if you want to. I haven't flashed it yet though. >>>> Deleted Link ....That didnt work. Got random reboots.

LuckyColdJohnson said:
Yes, Please share if you don't mind. I broke the GPS lol. I don't believe flashing this official firmware did it though, I think flashing different ROM's did it but who am I......I found a GPS fix I used for my Note 3 (Kit Kat) You have to flash it in recovery. Is that how yours is? Here is the file for you to check out if you want to. I haven't flashed it yet though. >>>> Deleted Link ....That didnt work. Got random reboots.
Click to expand...
Click to collapse
Found it after about an hour of looking , You must Odin back to a stock ROM first.
((((2. Enter into dialer *2767*3855# (Will do a HARD reset, no internal storage will be lost except the usual data)
3. Boot up again and run... )))
keep in mind this was the method to fix the gps on the note 2 and it may or may not still be a good dialer code for your s5.

Intub8 said:
Found it after about an hour of looking , You must Odin back to a stock ROM first.
((((2. Enter into dialer *2767*3855# (Will do a HARD reset, no internal storage will be lost except the usual data)
3. Boot up again and run... )))
keep in mind this was the method to fix the gps on the note 2 and it may or may not still be a good dialer code for your s5.
Click to expand...
Click to collapse
I restored a back up and it's working again. Something I installed did it. I'm trying to figure out what did. It could be anything. Thanks for this.

Caliesv said:
WWWHYY would you even want to know if this will work when you have your own firmware?! Then you try and convince someone else to take the plunge and try instead of you doing it? Just wondering why... cause i'm very baffled right now.
Click to expand...
Click to collapse
And @Caliesv I would ask you Why Not? The whole point of unlocking/rooting/building custom ROMs is because WE CAN, and how better to learn what we can and can't do then by trying? Just because a device has its own firmware has absolutely no bearing on what ROM you flash, granted as the default firmware it likely wont flash do to a signature mismatch but as a custom ROM why not?
I might just build one for the Heck of it.

GPS is a problem still. About to re-flash the restore and see what happens without root. Will report back.

[Q] Why does my rom install in seconds and boot to black screen?

I have a note 3 that I'm trying to get Cyanogenmod 11 on to. I should note that I got this working with my Droid Razr earlier today using the exact same process. I get to the point where I flash the rom and it only takes like 5 seconds then says "successful". When I boot the rom I just get a black screen that I have to hold the power button down to get out of. My note 3 is running 4.4.2 I have root and busybox is installed. I've tried safestrap 3.72 and 3.75. I've even tried the stock slot (and then reverted back when it didn't work). I'm out of things to try and I can't find anyone else who has had a similar issue. Anyone got any ideas?

If its an N900A or N900V, you can only run TW based roms because the bootloader is locked.

andygev35 said:
If its an N900A or N900V, you can only run TW based roms because the bootloader is locked.
Click to expand...
Click to collapse
How are people getting cyanogenmod 11 on their att note 3s if not through safestrap?

I don't know of anyone with an at&t note 3 running CM. It's possible they're using an N900T, or an N9005 Note 3 on at&t.

andygev35 said:
I don't know of anyone with an at&t note 3 running CM. It's possible they're using an international note 3 on at&t.
Click to expand...
Click to collapse
Well that's sad. I'm assuming any of these will work in the meantime? http://forum.xda-developers.com/note-3-att/#romList

They should, just make sure if you're on KK to choose a KK rom.

noob over here needing help
i have the ATT Note 3 with the locked bootloader. i cant rememeber the model name but i think its like I900A. anyway i have had it rooted for about 5 months or so and i have had safestrap and busybox and use Xposed wanam. also using twrp and titanium backup. well i have never flashed anything on it cuz ive always been sketched out with the locked bootloader and not being able to flash kernals and all that. so yesterday i figured i would try one out and see if i could get it. i used the "S5 Experience" rom and i downloaded it from MEGA onto my ext. SD under a new folder i made called "s5 experience". i then went into recovery mode through safestrap and went to "backup" and then made a backup of data, cache, and system. after that i went to "wipe" and did a factory reset/wipe. when that was done i went to "install" and found my "s5 experience" on my ext. SD and installed it. when that was done i rebooted my device and it popped up with the samsung note 3 emblem and under it the little lock underneath it in the unlocked position just like it always has. then went to safestrap with the little red robot and "safestrap: disabled" like always. so i hit continue and from there is when my problem started. the blue LED light on the top left turned on and stayed on but the screen stayed black. this is the problem i am still having right now. if i press the power button it will vibrate or double vibrate and eventualy if i hold it down i can get it to restart. after that i went into recovery again and tried to restore from my backup i had made just earlier. when i try that it goes for a while and then will eventually say that restore has failed. ive mesed with some of the settings and stuff in the twrp recovery interface but not much because im new and not sure what i should and should not be doing. so i started looking here. i didnt find any help on the S5 Experience forum and i havent found and other forums that have this problem except maybe this one. so i am asking for help, if someone would be so kind as to walk me through how to fix my phone and what i did wrong it would be greatly greatly appreciated. if at all possible i would love to keep all of my pics and apps and stuff but if that is not possible then i wont complain if i have to lose it all. i would be happy just to have a working phone again. thanks in advance and sorry if i have posted this in the wrong place.

sethers said:
i have the ATT Note 3 with the locked bootloader. i cant rememeber the model name but i think its like I900A. anyway i have had it rooted for about 5 months or so and i have had safestrap and busybox and use Xposed wanam. also using twrp and titanium backup. well i have never flashed anything on it cuz ive always been sketched out with the locked bootloader and not being able to flash kernals and all that. so yesterday i figured i would try one out and see if i could get it. i used the "S5 Experience" rom and i downloaded it from MEGA onto my ext. SD under a new folder i made called "s5 experience". i then went into recovery mode through safestrap and went to "backup" and then made a backup of data, cache, and system. after that i went to "wipe" and did a factory reset/wipe. when that was done i went to "install" and found my "s5 experience" on my ext. SD and installed it. when that was done i rebooted my device and it popped up with the samsung note 3 emblem and under it the little lock underneath it in the unlocked position just like it always has. then went to safestrap with the little red robot and "safestrap: disabled" like always. so i hit continue and from there is when my problem started. the blue LED light on the top left turned on and stayed on but the screen stayed black. this is the problem i am still having right now. if i press the power button it will vibrate or double vibrate and eventualy if i hold it down i can get it to restart. after that i went into recovery again and tried to restore from my backup i had made just earlier. when i try that it goes for a while and then will eventually say that restore has failed. ive mesed with some of the settings and stuff in the twrp recovery interface but not much because im new and not sure what i should and should not be doing. so i started looking here. i didnt find any help on the S5 Experience forum and i havent found and other forums that have this problem except maybe this one. so i am asking for help, if someone would be so kind as to walk me through how to fix my phone and what i did wrong it would be greatly greatly appreciated. if at all possible i would love to keep all of my pics and apps and stuff but if that is not possible then i wont complain if i have to lose it all. i would be happy just to have a working phone again. thanks in advance and sorry if i have posted this in the wrong place.
Click to expand...
Click to collapse
If you can boot to stock recovery (power+home+volume up) NOT safestrap recovery do a factory reset from there. That'll reflash stock rom and you can reroot + busybox + SS. Make sure to check what build you are on as well - if you are on NC2 kitkat you can only flash kitkat-based roms.

Sethers, please do not hijack and do not double post your questions in multiple threads.

graydiggy said:
Sethers, please do not hijack and do not double post your questions in multiple threads.
Click to expand...
Click to collapse
sorry graydiggy. this seemed like a thread that had something to do with the same black screen i was getting. besides this one i only posted it on the stupid questions thread.
---------- Post added at 01:56 PM ---------- Previous post was at 01:51 PM ----------
brisinger08 said:
If you can boot to stock recovery (power+home+volume up) NOT safestrap recovery do a factory reset from there. That'll reflash stock rom and you can reroot + busybox + SS. Make sure to check what build you are on as well - if you are on NC2 kitkat you can only flash kitkat-based roms.
Click to expand...
Click to collapse
brisinger08, thanks for the input. i was running kit kat. i figured the s5 experience would be based off of kitkat too but i guess i should have checked first. i just tried that. when i got into the recovery boot the little android guy falls over. then i went to factory wipe and let it wipe. after that i went to reboot. when it rebooted it still had the little lock under the Samsung logo and after that screen it went straight to safestrap again. it hasn't seemed to change anything as far as i can tell. any other ideas?

sethers said:
sorry graydiggy. this seemed like a thread that had something to do with the same black screen i was getting. besides this one i only posted it on the stupid questions thread.
---------- Post added at 01:56 PM ---------- Previous post was at 01:51 PM ----------
brisinger08, thanks for the input. i was running kit kat. i figured the s5 experience would be based off of kitkat too but i guess i should have checked first. i just tried that. when i got into the recovery boot the little android guy falls over. then i went to factory wipe and let it wipe. after that i went to reboot. when it rebooted it still had the little lock under the Samsung logo and after that screen it went straight to safestrap again. it hasn't seemed to change anything as far as i can tell. any other ideas?
Click to expand...
Click to collapse
If you're on the A3 bootloader then reflashing NC2 with odin will clear this up, (double-check in download mode) then follow the instructions in this thread. If you're on A2 you can still do this but it will overwrite your bootloader and lock you into NC2 so if that's the case you might want to read through that thread to make sure you're ok with that!

Knock On

I have been doing some searching and seen that several people have had trouble with knock on. I ran into the same problem but have yet to fix it. Got me wondering what causes the problem in the first place. Any thoughts? Additional pointers to fixing it would also be appreciated.
Sent from my VS980 4G using XDA Free mobile app
NOTE: Just noticed that when I dialed *611 to get Verizon, com.lge.doubletap fc'd.

More info is needed like what rom or kernel your on to know or have an idea why it's not working for you. Then you might get some answers that help you out

It's not all that critical to me just more of a brain exercise to me trying to figure it out. Interestingly, I found that immediately after I went back stock, rerooted, etc and turned on the option to use the power key to lock knock on quit working and wouldn't come back on.

I have stock ROM and rooted but after I installed twrp recovery the knock on stopped working. Now when I double tap the phone restarts. I liked using that feature.

Found a solution that worked for me, sensor calibration in settings , gestures.
Unfortunately it worked for a little while, now its not working. Seems like the phone goes into deep sleep and when I double knock the phone restarts.

This morning I did factory reset, its still rooted but I will try it without a custom recovery. Knock on is working for now. I thought factory
reset would get rid of TWRP, its still there and so is the knock problem.

Knock on help
Hello everyone,
This is my first post ever on XDA. I will try to be as brief and detailed as possible.
I have been rooted with custom recoveries using vs98024A through vs98026. After going back to stock(24A) using LG Flash tool 2014 and the kdz method, then factory upgrading to 27A(latest software upgrade from VZW) and re-rooting(stump root) and finally getting twrp re-installed(Auto Rec), I also lost my knock on feature and have a dead strip close to the top of my screen.
I've done the hidden menu touch firmware upgrade and that doesn't work for me. It says it upgraded but it didn't fix the issue. I tried flashing the cloudyfa g3 port last night. The installation was a success. It didn't fix the dead spot but knock code halfway worked. I know knock code is different than knock on. I am looking for a fix to knock on. I've been reading forums for about a week now I've found that the hiddenmenu fix has only helped a handful of people with the vs980. I haven't tried any kernel flashing yet.
I'm running stock rooted 4.4.2 VS98027A build number KOT491.VS98027A Kernel Version 3.4.0-perf [email protected] Baseband version VS98027A-MPSS.DI.2.0.c2-00079-M8974AAAAANAZM-1
I also have TWRP recovery working
Let me know if I left out any pertinent information and I will be more than happy to produce that information.
This dead spot on the screen and no knock on is killing me. Any suggestions would be greatly appreciated.
Thanks in advance =)

dakattak said:
Hello everyone,
This is my first post ever on XDA. I will try to be as brief and detailed as possible.
I have been rooted with custom recoveries using vs98024A through vs98026. After going back to stock(24A) using LG Flash tool 2014 and the kdz method, then factory upgrading to 27A(latest software upgrade from VZW) and re-rooting(stump root) and finally getting twrp re-installed(Auto Rec), I also lost my knock on feature and have a dead strip close to the top of my screen.
I've done the hidden menu touch firmware upgrade and that doesn't work for me. It says it upgraded but it didn't fix the issue. I tried flashing the cloudyfa g3 port last night. The installation was a success. It didn't fix the dead spot but knock code halfway worked. I know knock code is different than knock on. I am looking for a fix to knock on. I've been reading forums for about a week now I've found that the hiddenmenu fix has only helped a handful of people with the vs980. I haven't tried any kernel flashing yet.
I'm running stock rooted 4.4.2 VS98027A build number KOT491.VS98027A Kernel Version 3.4.0-perf [email protected] Baseband version VS98027A-MPSS.DI.2.0.c2-00079-M8974AAAAANAZM-1
I also have TWRP recovery working
Let me know if I left out any pertinent information and I will be more than happy to produce that information.
This dead spot on the screen and no knock on is killing me. Any suggestions would be greatly appreciated.
Thanks in advance =)
Click to expand...
Click to collapse
I don't know about fixing the dead spot/black band on your screen (you probably need a new screen now), but I suggest you .kdz your way back to stock 27A, use stump root again, but, this time, do not use AutoRec. Using AutoRec on 27A causes all kinds of issues.
You have to flash a bumped recovery using adb commands...I think I read somewhere that there is a tool, or something that automates the adb commands for you, and flashes a bumped recovery for you, but I can't remember where I read it...use blastagator's bumped recovery to flash to your phone; just take out the recovery image from his zip, and flash it using adb commands.
Blastagator recovery: http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705

Thanks for your response. I guess using auto rec on 27a was the culprit like you say. I seem to remember it happening shortly after the update.
As for the dead spot. It doesn't affect my screen other than not responding to touch in the affected region. The entire screen display works visually.
I'll give this a shot tonight and see how it goes.
Again, thank you for your response!
Cheers
Sent from my VS980 4G using XDA Free mobile app

I had a similar issue and it was the dead spot in the screen causing problems. It sounds like it died in the same location too. I restored to stock without it fixing the problem and ended up getting a replacement from Verizon. Hopefully you're still under warranty, I had a month left in mine.

ATgiant said:
I had a similar issue and it was the dead spot in the screen causing problems. It sounds like it died in the same location too. I restored to stock without it fixing the problem and ended up getting a replacement from Verizon. Hopefully you're still under warranty, I had a month left in mine.
Click to expand...
Click to collapse
After a lengthy power outage in my building, I was finally give blastagator's bumped recovery a try. I flashed back to stock 27A and rooted with stump like you suggested. Couldn't get it to flash manually with adb or terminal. I ended up using flashify to flash blastagator's bumped recovery image. It installed fine and I was able to boot into the custom recovery, unfortunately the dead spot is still there.
So annoying. It looks like I'll be contacting Verizon about a replacement.
Thanks again for your help

Finger touch area to small?

So I tried to update TWRP and it said unsuccessful because I probably had the latest version. (Using TWRP manager) Then a box popped up asking if I wanted to boot into recovery, I hit ok because I had to install something.
When it loaded it was stretched out and I ha had to touch above the buttons to use them. Figuring it was just TWRP being silly I rebooted and now the whole phone is doing it. It's like the area it registers touch was shrunk. The pen works fine, and that's how I'm typing this now.
Any ideas on what happened/how to fix it? I've tried rebooting a few times, and changing the dpi.
Sent from my SM-N910T3

If you can, try taking a backup using TWRP and then ODIN to stock to see if that changes anything.

Does anyone have the stock firmware for the T3? I can't find them

collinstheclown said:
Does anyone have the stock firmware for the T3? I can't find them
Click to expand...
Click to collapse
http://forum.xda-developers.com/not...t/dofc-n910t-t3-tekxxxx-n4-urv0-8-11-t3176500
It never fails, search and search and find nothing. Post about it and find it in 2 seconds..
Will update when I'm done

Finally back to stock, still having the issue. Is there a guide to removing TWRP, looks like it'll have to go in for repair

collinstheclown said:
Finally back to stock, still having the issue. Is there a guide to removing TWRP, looks like it'll have to go in for repair
Click to expand...
Click to collapse
Odin the base and it'll be removed

I don't have the files to Odin.
I just got my replacement, can anyone tell me how to pull the files I need from it to flash to the old phone?