So I'm curious- when flashing OEM images from Google, which version is the "Verizon" version? The reason I ask is that I've had a Pixel that I purchased from Google direct and have been running it on VZW.
Recently, due to some odd malfunctioning, I tried and tried to re-flash the phone with the standard image (not Europe and not Verizon because I bought the phone directly from Google), but since it still didn't correct the problem, Google has now sent me a new, replacement phone.
So upon receiving the new Pixel, it was way out of date - running 7.1.1 and a February build, so I updated the os only to find that it has installed the May - Verizon build (aka NHG47L). That blew me away because I always assumed the "Verizon" images were for when you bought the phone from Verizon...NO?
Thanks for clearing the air here-
Questions go in the Q&A section. Report your post to a moderator by clicking the exclamation point in the triangle /!\ in the lower left corner of your post and ask them to move the thread to Q&A.
When you're running stock on the Pixel no matter where you got the Pixel, after you put a Verizon SIM in it, the phone will download and install the Verizon version of the stock Pixel ROM.
The site https://developers.google.com/android/images says which versions are Verizon specific.
Understand.
If you are re-flashing a Pixel to stock though, and that Pixel came from Google but has a VZW sim card installed, is it advised to flash the Verizon stock image or the non-designated image or does it matter? I had assumed it was best to flash the non-VZW image due to the added issues involved with unlocking a VZW phone, but after I had done that, I was having some phone app malfunction issues and so I'm wondering if the fact that I had not flashed the VZW image was causing my issues or not.
Thanks
pstgh said:
Understand.
If you are re-flashing a Pixel to stock though, and that Pixel came from Google but has a VZW sim card installed, is it advised to flash the Verizon stock image or the non-designated image or does it matter? I had assumed it was best to flash the non-VZW image due to the added issues involved with unlocking a VZW phone, but after I had done that, I was having some phone app malfunction issues and so I'm wondering if the fact that I had not flashed the VZW image was causing my issues or not.
Thanks
Click to expand...
Click to collapse
If Verizon is your carrier, then you should flash the Verizon build which is at this time NHG47L. If your Pixel came from the Google Store, then you don't have to worry about the bootloader, you will be able to unlock, and lock it at will.
jmartin72 said:
If Verizon is your carrier, then you should flash the Verizon build which is at this time NHG47L. If your Pixel came from the Google Store, then you don't have to worry about the bootloader, you will be able to unlock, and lock it at will.
Click to expand...
Click to collapse
Would it affect rooting?
Tulsadiver said:
Would it affect rooting?
Click to expand...
Click to collapse
Again, as long as it's a pixel direct from Google, then no I've rooted mine before, but I usually stay stock
Tulsadiver said:
Would it affect rooting?
Click to expand...
Click to collapse
no. definitely not...
if it was purchased from the google store then you can flash anything..
reyscott said:
no. definitely not...
if it was purchased from the google store then you can flash anything..
Click to expand...
Click to collapse
Thanks, I like their reception but nothing else. I'll never buy another phone from them. I've been using Google version with no problems. Could the difference be just bloat ware?
Tulsadiver said:
Thanks, I like their reception but nothing else. I'll never buy another phone from them. I've been using Google version with no problems. Could the difference be just bloat ware?
Click to expand...
Click to collapse
havent used any carrier specific devices. so cant really tell
Tulsadiver said:
Thanks, I like their reception but nothing else. I'll never buy another phone from them. I've been using Google version with no problems. Could the difference be just bloat ware?
Click to expand...
Click to collapse
no. It apparently has improvements in it for their network. It doesn't include extra applications.
Related
I read in a thread that someone lost their imei and it was suggested for them to use *2767*3855# to restore everything back to factory and reactivate the sim. I know this won't update oyur baseband to the newer editions, but it made me think about if someone bought a new phone that has the updated firmware, or somehow got their baseband/radios/kernel updated to the new version (whether through OTA or through getting a new phone), would it be possible to downgrade baseband/radio/firmware back to the previous edition since the VRLF2 version is also signed and authentic?
If it is possible to downgrade, does anyone have the dump files needed from an "older" version to do this? How would it be done, through odin or recovery, or terminal/adb (like backing up and restoring /efs partition)?
Thanks
newuser134 said:
If it is possible to downgrade, does anyone have the dump files needed from an "older" version to do this? How would it be done, through odin or recovery, or terminal/adb (like backing up and restoring /efs partition)?
Click to expand...
Click to collapse
Yep, see http://forum.xda-developers.com/showthread.php?t=1788313 for details.
The forum post has links to both the old and new modem, and full flashing instructions.
yes and I would only use the VLRF2 since it does not have the dumbed down search...the update is a downgrade!! If you like you can upgrade to the VRLG1 radio/modem and stay on the VRLF2 software.
droidstyle said:
yes and I would only use the VLRF2 since it does not have the dumbed down search...the update is a downgrade!! If you like you can upgrade to the VRLG1 radio/modem and stay on the VRLF2 software.
Click to expand...
Click to collapse
True, although you can just get the full featured googlequicksearchbox APK and replace the new one with it.
pjamv5 said:
True, although you can just get the full featured googlequicksearchbox APK and replace the new one with it.
Click to expand...
Click to collapse
indeed...more than one way to skin a cat.
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
I guess the only way to be sure is to try it out
Desterly said:
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
Click to expand...
Click to collapse
I used the Phone Info app to shut off 4g, and made a number of before/after test of the 3g signal.
It seems to be consistantly 2 or 3 db better with the new modem.
For example, sitting at my desk, I would show -82 dBm with the old modem, and -79 dBm with the new modem.
Can't say if there is any difference in 4g performance, it's nice and fast both before and after.
One change that I noticed, with the new modem, when switching from 3g to 4g, it changes over almost instantly. Before the modem upgrade, it would take maybe 30 seconds or so to pick up the 4g signal.
I535VRLG1 update
I also wondered this. Is there a reason except for the search function to go back to the first radio?
Also on a side note, I never accepted an OTA update! Was this pushed without the user's consent?
excelsisba said:
I also wondered this. Is there a reason except for the search function to go back to the first radio?
Click to expand...
Click to collapse
Updating the radio has nothing to do with the search function. If you currently have the VRLF2 build, you can update the radio (also the kernel) to the newer version without changing the build version.
If you purchased an updated phone, or take an OTA update, then you will have the downgraded google search. As pointed out by pjamv5, that's easy enough to fix if you want the old google search.
I've updated the kernel and radio, here's the end result:
Desterly said:
Is there a general concensus yet on the newer modem? seems the posts go both ways... a lot of people saying it's better, others saying it's not.
I guess the only way to be sure is to try it out
Click to expand...
Click to collapse
I first flashed the G1 radio firmware and kept the F2 ROM. I didn't notice much of a difference. Went ahead and flashed BeanTown R2 ROM which is based on the G1 rom but customized. It all works well for me.
Bought my GS4 yesturday, this morning around 10am i got an OTA that was about 28mb. Not sure what that OTA did because i cant find any change log anywhere or anybody else talking about it...does anybody know anything?
Build Number is JDQ39.I337MVLUAMDL
On Rogers in Canada
You should probably have put down Rogers on the thread title. I didn't receive anything but I am no AT&T. But one more thing, I was talking in this other thread with the Canadian carrier guys. Is your Contacts and phone app white or black / blue?
Even though I'm on AT&T, I am happy for Rogers customers. Can anyone elaborate on what this update does? Hopefully it addresses the lag?
On US AT&T and no OTA. I wouldn't download any OTA's though just in-case they address the hacked bootloader.
@geoldr: The OTA was launched by Samsung globally.
Good to see you again P-Pat! I got the notification, but rooted before installing in case there was patch to stop root. After I tried to install and it said my phone has been modified and updates are not available. I am now searching to figure out how to install this....
For news on the update, see here: http://gadgets.ndtv.com/mobiles/news/samsung-galaxy-s4-receives-first-software-update-362298
David Dee said:
@geoldr: The OTA was launched by Samsung globally.
Good to see you again P-Pat! I got the notification, but rooted before installing in case there was patch to stop root. After I tried to install and it said my phone has been modified and updates are not available. I am now searching to figure out how to install this....
For news on the update, see here: http://gadgets.ndtv.com/mobiles/news/samsung-galaxy-s4-receives-first-software-update-362298
Click to expand...
Click to collapse
I'm a bit confused at this. Even if Samsung releases an update, we won't get it instantly because the carriers have to test it out and everything right? Hasn't this always been the case or am I missing something?
geoldr said:
I'm a bit confused at this. Even if Samsung releases an update, we won't get it instantly because the carriers have to test it out and everything right? Hasn't this always been the case or am I missing something?
Click to expand...
Click to collapse
From what I have read, so far it has been launched on Sprint, Rogers and the international version. I am sure AT&T will come soon. Samsung launches the updates, but the carriers distribute them...that is why Android version updates have different timing for different carriers.
David Dee said:
From what I have read, so far it has been launched on Sprint, Rogers and the international version. I am sure AT&T will come soon. Samsung launches the updates, but the carriers distribute them...that is why Android version updates have different timing for different carriers.
Click to expand...
Click to collapse
I see. Now just to find out what this update does.
For now I will be staying away from it. I don't want anything locking up the chance of unlocking the bootloader.
geoldr said:
I see. Now just to find out what this update does.
For now I will be staying away from it. I don't want anything locking up the chance of unlocking the bootloader.
Click to expand...
Click to collapse
This! I just rooted my phone this morning finally and froze the AT&T Software Update and FWUpdater. Should protect me from the OTA when it comes over to AT&T correct?
Thermalwolf said:
This! I just rooted my phone this morning finally and froze the AT&T Software Update and FWUpdater. Should protect me from the OTA when it comes over to AT&T correct?
Click to expand...
Click to collapse
Yeah. I dont think the firmware installs without the user accepting it anyways.
geoldr said:
Yeah. I dont think the firmware installs without the user accepting it anyways.
Click to expand...
Click to collapse
Somewhere I read they can force push security updates onto the phone without you even having to accept it. This is something I think they would do over the bootloader to prevent people from stopping the patch.
Thermalwolf said:
This! I just rooted my phone this morning finally and froze the AT&T Software Update and FWUpdater. Should protect me from the OTA when it comes over to AT&T correct?
Click to expand...
Click to collapse
It will save you from an annoying notification, but you have to click to initiate the install. Also, if you are are rooted, the ota won't work. You are safe.
Thermalwolf said:
Somewhere I read they can force push security updates onto the phone without you even having to accept it. This is something I think they would do over the bootloader to prevent people from stopping the patch.
Click to expand...
Click to collapse
Really? Well in that case I need to root and block those services. I've been waiting for an unlock and then was gonna root it.
David Dee said:
It will save you from an annoying notification, but you have to click to initiate the install. Also, if you are are rooted, the ota won't work. You are safe.
Click to expand...
Click to collapse
I figured with this method of root it wouldn't effect the update since we weren't messing with the firmware.
Thermalwolf said:
I figured with this method of root it wouldn't effect the update since we weren't messing with the firmware.
Click to expand...
Click to collapse
This is Sammy's doing, seems like they are taking a harder line this time around. I used the exact same method on my TF300 and OTAs work like a charm.
geoldr said:
You should probably have put down Rogers on the thread title. I didn't receive anything but I am no AT&T. But one more thing, I was talking in this other thread with the Canadian carrier guys. Is your Contacts and phone app white or black / blue?
Click to expand...
Click to collapse
its black blue
David Dee said:
@geoldr: The OTA was launched by Samsung globally.
Good to see you again P-Pat! I got the notification, but rooted before installing in case there was patch to stop root. After I tried to install and it said my phone has been modified and updates are not available. I am now searching to figure out how to install this....
For news on the update, see here: http://gadgets.ndtv.com/mobiles/news/samsung-galaxy-s4-receives-first-software-update-362298
Click to expand...
Click to collapse
Thanks Bud!! Nice to see you too. On the screenshot you posted, it doesnt match up to mine. It was 28mb and it didnt have any mention of ''improved stability''. Im really wondering what that was, maybe the canadien version of that european release. Also the build number doesnt match up
geoldr said:
I'm a bit confused at this. Even if Samsung releases an update, we won't get it instantly because the carriers have to test it out and everything right? Hasn't this always been the case or am I missing something?
Click to expand...
Click to collapse
not always, i received 2 updates on the GS3 that were released from sammy and did not go through carrier testing, unless they did it so uniformly that it didnt seem like it, but then again, telus and bell got it the same day rogers did, but those updates were stability and securtiy related, they didnt bring any features, so i guess it really depends on what the updates changes
This link confirms what David Dee was saying, it also matches my build number and size of update
http://www.androidpolice.com/2013/0...iving-its-first-ota-update-build-l720vpuamdl/
I wouldnt worry too much about OTAs anymore since AdamOutler has an Odin flashable current firmware up in the dev forums.
polish_pat said:
its black blue
Click to expand...
Click to collapse
Now see thats weird. AT&T version everything is white. Messaging app is white dialer is white contacts are white.
I wonder why...
David Dee said:
This is Sammy's doing, seems like they are taking a harder line this time around. I used the exact same method on my TF300 and OTAs work like a charm.
Click to expand...
Click to collapse
So what you're saying is I can still install OTA's if I rooted with motochopper? But as long as I have the ota update files frozen I shouldn't have to worry?
Thermalwolf said:
So what you're saying is I can still install OTA's if I rooted with motochopper? But as long as I have the ota update files frozen I shouldn't have to worry?
Click to expand...
Click to collapse
No, once rooted the otas will not work because it detects device modification.
I installed the Nuseven stock 6.0 ROM on my htc one m8 and now I get no service. Can somebody please help me I have entered in the apn stuff and have tried all combination of settings in the 4g switcher app but nothing works.
Werzal123 said:
I installed the Nuseven stock 6.0 ROM on my htc one m8 and now I get no service. Can somebody please help me I have entered in the apn stuff and have tried all combination of settings in the 4g switcher app but nothing works.
Click to expand...
Click to collapse
What is your carrier?
If Verizon, just flash and that's it, no need to mess with any settings.
andybones said:
What is your carrier?
If Verizon, just flash and that's it, no need to mess with any settings.
Click to expand...
Click to collapse
My carrier is 2degrees in New Zealand. It's almost as if installing new roms disabled "unlocked to any network" thing
I payed for s-off so I could install a debloated ROM but i got no service. So i decided to install Viper but still got no service.
Now all I want is for service to work i don't even care about the bloatware since getting rid of it seems to be so fricken difficult.\
Could you please help me in installing the stock rom for my phone and getting service to work?
Werzal123 said:
My carrier is 2degrees in New Zealand. It's almost as if installing new roms disabled "unlocked to any network" thing
I payed for s-off so I could install a debloated ROM but i got no service. So i decided to install Viper but still got no service.
Now all I want is for service to work i don't even care about the bloatware since getting rid of it seems to be so fricken difficult.\
Could you please help me in installing the stock rom for my phone and getting service to work?
Click to expand...
Click to collapse
I'm sorry I'm not familiar or even heard of 2degrees, wish I could help my friend.
Same issue but I'm with page plus which uses the verizon network. I'm on ROM wolla gpe 6.1 MM
I flashed the same ROM, and I''m having the same issue. I have the Verizon HTC One M8. I flashed the RUU hoping it would solve the problem but, I still have zero service. I can't find any fix for this. I have searched far and wide for any solution and I am now at a stand still...
taymo said:
I flashed the same ROM, and I''m having the same issue. I have the Verizon HTC One M8. I flashed the RUU hoping it would solve the problem but, I still have zero service. I can't find any fix for this. I have searched far and wide for any solution and I am now at a stand still...
Click to expand...
Click to collapse
A factory reset from the stock recovery is usually the answer for this. Has to be the stock recovery, not TWRP. They do different things.
I tried that already.
robocuff said:
A factory reset from the stock recovery is usually the answer for this. Has to be the stock recovery, not TWRP. They do different things.
Click to expand...
Click to collapse
When I flashed RUU it took me back to stock recovery. No TWRP or SuperSU. I failed to mention I am Verizon to Straight Talk conversion. Idk if maybe it has something to do with them or not. I just have zero signal whether the phone is activated or unactive.
I have been working on my m8 for the past 7 hours. It was working but I messed it up the same way as you and now I am without service as well. No idea what to do
taymo said:
When I flashed RUU it took me back to stock recovery. No TWRP or SuperSU. I failed to mention I am Verizon to Straight Talk conversion. Idk if maybe it has something to do with them or not. I just have zero signal whether the phone is activated or unactive.
Click to expand...
Click to collapse
Please tell me you found a solution for this mess... It's been a whole day and I'm without service on my phone
Alpha-Retard said:
Please tell me you found a solution for this mess... It's been a whole day and I'm without service on my phone
Click to expand...
Click to collapse
I've been searching man. The be at conclusion I can come up with is finding the correct RUU for you service provider and area. I flashed on for Europe and idk if maybe that has something to do with my poor service. Our phone receives very minimal support due to age.
taymo said:
I've been searching man. The be at conclusion I can come up with is finding the correct RUU for you service provider and area. I flashed on for Europe and idk if maybe that has something to do with my poor service. Our phone receives very minimal support due to age.
Click to expand...
Click to collapse
Finally got service to work by flashing a Verizon RUU even though I'm in Pakistan. It works but I am back on square one, i.e absolutely horrendous signals. The phone is basically useless at this point because it's always on a single bar. I think it's a hardware issue so there's nothing really I can do :/
Hi guys,
i have a pixel and i want to enrrol to the beta program, i just done the process but it seams that update is not arriving, its posible that verizon pixels can't enroll to beta program?
http://www.droid-life.com/2017/01/30/android-7-1-2-beta-download-update-nexus-pixel/
Regards
You can download the full image here
I dont have oem unlocked. I can sideloade it?
Yea even i didn't get it. I guess it not for the verizon phones.
Can anyone who has upgraded to 7.1.2 let us know if it appears stable enough for a daily driver and have they noticed any differences ? Thank you.....
Another locked bootloader VZW customer here who enrolled and is waiting for OTA. I think we'll get it, just have to wait for OTA's to start. Google let us enroll, and we seem to have gotten updates from Google and not VZW so far. I think it'll just take a day or 2 to start rolling.
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
I am a non VZW pixel user (Koodo - Canada) and have not received the OTA after signing up yesterday. They note that it may take 24 hours and looks like it's going to for me.
k.s.deviate said:
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
Click to expand...
Click to collapse
I know that the bootloader is what loads the Android filesystem to the boot image, I wonder if it can somehow be manipulated to unlock and root since you mention that the boot image is different? Does anyone know? Thanks
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
farfromovin said:
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
Click to expand...
Click to collapse
Signed up yesterday for both my Pixel (VZW sim) and Pixel XL (Project Fi sim) both bought direct from Google. Pixel XL rec'd update almost immediately not yet on Pixel so far.
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Sent from my Pixel using Tapatalk
joshw0000 said:
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Click to expand...
Click to collapse
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Nope it's exactly that. Just remove -w so it doesn't wipe the device. It's how I update my Pixel and 5X since I'm impatient waiting for OTAs.
murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Sent from my Pixel using Tapatalk
joshw0000 said:
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Click to expand...
Click to collapse
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
OTA hasn't rolled for the pixel yet, likely "soon", my guess is today or tomorrow at the latest since XL has gone out. I am on project FI and got the pixel through the play store fyi
murryrulz said:
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
Click to expand...
Click to collapse
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
I am also in the waiting for the OTA camp and use an unlocked Verizon Pixel and PIxel XL. I have had better luck using the TWRP sideload method and it installing to the other slot with each subsequent sideload appears to me a more consistent way to keep everything updated in the same way that the system OTA works.
joshw0000 said:
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Get rid of windows, use Linux, no messing around with anything, it just works ?
-------- runs -----_ducks_---- runs ----
Sent from my Pixel using XDA-Developers Legacy app
So I was away from my computer when the January Security update came out so Im on the December update.
I would like to know can I just jump straight to the Feb update when its available or do I need to do Jan first then Feb?
im unlocked, rooted, ex kernel, google store phone. thanks.
You can just jump.
my phone is on the latest 8.1 april ota.
after the update the phone freezes when placing and recieving phone calls
is it possible to "downgrade" to the previous ota the one from march to test the phone app or will it break the phone
i googled the hell out of this but only found people flashing later releases and not previous ones
thanks
kidhudi said:
my phone is on the latest 8.1 april ota.
after the update the phone freezes when placing and recieving phone calls
is it possible to "downgrade" to the previous ota the one from march to test the phone app or will it break the phone
i googled the hell out of this but only found people flashing later releases and not previous ones
thanks
Click to expand...
Click to collapse
I think downgrading via OTA it's quite impossible.
You have to wipe and flash the full factory image.
damn it thats what i was afraid of.
thanks
kidhudi said:
damn it thats what i was afraid of.
thanks
Click to expand...
Click to collapse
You should've have to wipe. Just flash the full image but remove the -w from the flash all bat file. That saves data and settings. But backup to be sure.
TonikJDK said:
You should've have to wipe. Just flash the full image but remove the -w from the flash all bat file. That saves data and settings. But backup to be sure.
Click to expand...
Click to collapse
i got the verizon varient. it seems i cant oem unlock the device.
i searched all day and cant find a technique that works so flashing the stock image is a no go apparently.
life was so much easier with my nexus 6.
damn verizon.
kidhudi said:
i got the verizon varient. it seems i cant oem unlock the device.
i searched all day and cant find a technique that works so flashing the stock image is a no go apparently.
life was so much easier with my nexus 6.
damn verizon.
Click to expand...
Click to collapse
Time to start clearing data on the dialer related apps, or reset the phone. I am hopeful that will help you. If it was soley update related the forum would be blowing up with complaints.
Now did something go wrong with your update... I'll buy that.
i just assumed it was the april security update it started acting up around the same time. i thought maybe a crappy download
i already did a few factory resets. tried third party dialers. everything i could think of.
what really sucks is i am 3 months out of the 1 year google warranty. so i am pretty much screwed.
thanks for your help bro
i will try to sideload the latest ota.. if it is still jacked up then it is probably hardware related
what sucks is i am still paying it off and it is virtually unusable lol.. at least i can text