Related
First one was hacked almost immediately. Ended up perma-roaming with an IMEI of 0.
They replaced that with a new one. Of course they wanted to re-up my contract and steal my unlimited data. I looked the guy dead in the eye and said "No, that's unacceptable." He said "but unlimited data isn't in the system." I said "There's no 'system' to it. I take my old SIM, put in in a new phone, and walk out." Then he wanted to tell me that wouldn't work, until I grabbed my old phone, SIM, and threw it in the new phone. Then the manager walked up and said I could go.
That phone lasted until yesterday. Capacitive touchscreen starts acting up. Reboot, nothing. Turn it off for a while (CM10 was running hot), and it started working for just a couple of minutes. Restored to stock and it stopped working all together.
Took that to the store, and they were nice once they figured out that this one didn't come from online, but another store. Then they realized it was out of 14 days so it had to be a refurb. Wanted to ship it with free 5 day, but I paid $15 for it to get here by 10am this morning. Not a bad deal, over all.
Refurb arrives this morning, pull the SIM, battery, etc from the old one, and boot it up. Capacitive layer works properly, so that's good. Skip all the My Verizon and Google stuff, because I want to get everything tested. Open a few apps, good. Press physical home button....
NOTHING. Press it again. Nothing. Third time (really pressing hard this time), it pauses for a few seconds then slowly crawls back to the homescreen.
Freaking refurb. I call up verizon and they were super nice. Explained this was my 3rd phone, and they are overnighting another GS3 for free. Let's hope this lasts a little longer.
Edit: just realized this was my first actual post! I've been a member here since I got my first smart phone: an HTC Touch with WM 6!
I'll bet those VZW reps are loving to see you come through the door :laugh:
It's amazing how easy it is to get into the refurb vortex and not be able to get out. As you've seen, device after device has some inconspicuous issue that requires a return. These forums are loaded with these stories.
Hopefully the next one will be the one that keeps you happy, out of the VZW stores, and out of that vortex.
A QPST backup would have kept you out of this loop lol. So sorry to hear the struggle!
con247 said:
A QPST backup would have kept you out of this loop lol. So sorry to hear the struggle!
Click to expand...
Click to collapse
Yeah, I was in IRC while switching to CM10. invisibleK tried to help me out, but this was before the EFS or QPST fixes.
I too got the IMEI of 0 prior to QPST backups (ironically I got it from a TW rom, never flashed a AOSP rom. I think it was the lean Kernal.) I tried restoring my efs.sbn but I am stuck in roaming. If I Odin back to stock and take my phone back to a VZW will they give me a new one?
I got Verizon to do an even swap form a GNEX to a GS3 because of the connectivity issues it has had...free upgrade
no wonder verizon doesnt like people rooting their phones. op's fault
First two refurbs were your fault, hopefully with this 4th one it'll act right, and you won't mess it up.
luke1333 said:
no wonder verizon doesnt like people rooting their phones. op's fault
Click to expand...
Click to collapse
Yeah, I'd like to say it's vzw's fault for locking things down, but it happens on other networks as well. Looks like a Samsung issue.
Jothen2002 said:
I got Verizon to do an even swap form a GNEX to a GS3 because of the connectivity issues it has had...free upgrade
Click to expand...
Click to collapse
Hah, I tried to switch to a gnex and they talked me out of it.
tgom222 said:
I too got the IMEI of 0 prior to QPST backups (ironically I got it from a TW rom, never flashed a AOSP rom. I think it was the lean Kernal.) I tried restoring my efs.sbn but I am stuck in roaming. If I Odin back to stock and take my phone back to a VZW will they give me a new one?
Click to expand...
Click to collapse
Yeah, they should replace it, just play dumb and make sure you're on stock. But you'll end up with a return if it's been more than 14 days, and you really don't want that. Instead, just use QPST to write your IMEI to your phone. You don't need a backup, just the number on the back of the phone.
Neverendingxsin said:
First two refurbs were your fault, hopefully with this 4th one it'll act right, and you won't mess it up.
Click to expand...
Click to collapse
How is a faulty capacitive layer on a touchscreen my fault? A ROM doesn't make a touchscreen go bad.
So today(5-15) I saw online that T-Mobile USA released the 5.1.1 OTA for there branded Galaxy S6/S6 Edge, so any info on when the Verizon branded version is coming out? I'm having multiply major bugs(wifi, memory, and lagging) across 3 different S6 devices(original device and 2 replacements) since launch day. Also, the Verizon Branded OTA that just came out brought me new bugs like with Google voice to text giving me 2 new bugs and making it unusable. Also, apps are freezing like crazy and ends up freezing the whole phone and when I try to lock the phone with the power button when an app is freezing it opens up the camera instead of locking the phone and most of the time I have to restart the phone when this happens and it happens quite often, but only started after the Verizon OTA. Also, from launch day(across all 3 devices) I been having memory issues with the phone, it tells me it has between 1GB-1.2GB of total memory on the phone and I only have 748MB total available with only very few apps on the phone at the moment, everything closed and all the bloatware gone off the phone. I herd that the Verizon OTA we just got was suppose to fix the memory issue, but apparently for me it did nothing at all with the memory on my phone. and lastly I'm having the major wifi bug a lot of us are having witch for me started on the 6th day after launch and never worked again even after I had 3 different devices and still the same thing is still ongoing, and in fact the Verizon OTA we just got made the wifi bug even worst then before.
So the 5.1.1 OTA is really needed for me to fix these ongoing and new bugs I'm having and after 2 months I'm getting sick and tired of waiting for patches to come out!
You probably should go into your system recovery and clear cache. That will probably help a majority of your bugs.
charlesvw9 said:
You probably should go into your system recovery and clear cache. That will probably help a majority of your bugs.
Click to expand...
Click to collapse
I already did that and nothing changed at all, and like I said I had 3 different devices and nothing changed at all. In fact the 3rd device I got which I still have was giving me problems from very first time I turned it on and during the initial setup as soon as I turned it on from the FedEx box and the keyboard was slow and not putting the letters I clicked in the box and to click next/skip, restart or power off I had to use my pointer finger and press multiple times and fast like a woodpecker would on a tree in order for those functions to respond, and before I can even finish the initial setup I had to already do a factory reset on the phone. Even typing right now in this box responding to you the phone is lagging just typing now.
Don't think Verizon has announced anything yet. The current G920VVRU1A0E2 works fine for me.
To help with keyboard lag - go into settings and make sure the proper language is intalled and updated. Have you tried different keyboards? Swiftkey?
krelvinaz said:
Don't think Verizon has announced anything yet. The current G920VVRU1A0E2 works fine for me.
Click to expand...
Click to collapse
Same here and I'm in no hurry to lose root.
krelvinaz said:
Don't think Verizon has announced anything yet. The current G920VVRU1A0E2 works fine for me.
Click to expand...
Click to collapse
Well 3 different phones since launch day have been giving me all different kinds of problems and never had a device with out a major problem in it and the new Verizon OTA that just came out in June made the phone even worst then before. The Build for the update is G920VVRU1A0E2, and in fact I even had problems getting the update on my phone because from launch day of the OTA-4days after it came out the OTA would not fully download and give me error code 503 and it wasn't until the 5th day that it worked and then when I finally got it installed on my phone it just brought more bugs to the phone like I talked about in the OP
bigj0110 said:
Well 3 different phones since launch day have been giving me all different kinds of problems and never had a device with out a major problem in it and the new Verizon OTA that just came out in June made the phone even worst then before. The Build for the update is G920VVRU1A0E2, and in fact I even had problems getting the update on my phone because from launch day of the OTA-4days after it came out the OTA would not fully download and give me error code 503 and it wasn't until the 5th day that it worked and then when I finally got it installed on my phone it just brought more bugs to the phone like I talked about in the OP
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock with the full tar file instead of the update? If not go here and give it a shot. If you use the OE2 one you will have to factory data reset to wipe your phone clean either after or before you flash.
charlesvw9 said:
To help with keyboard lag - go into settings and make sure the proper language is intalled and updated. Have you tried different keyboards? Swiftkey?
Click to expand...
Click to collapse
yea I tired that, but this started as soon as I turned on my phone for the very 1st time trying to do the initial set up, plus like I said even pressing next/skip, power off or reset in the initial setup was a hassle. I had to take my pointer finger and point it down and press fast and many times like a woodpecker in order for the buttons functions to work and I could not even finish the initial setup and had to already do a factory reset before the initial setup was even finished on the 3rd device I have now. The phone is so bad that even clicking the home button some of the apps, Google search and weather is not on screen right away and takes second or 2 to show up, its lagging to show up.
Misterxtc said:
Have you tried using Odin to flash back to stock with the full tar file instead of the update? If not go here and give it a shot. If you use the OE2 one you will have to factory data reset to wipe your phone clean either after or before you flash.
Click to expand...
Click to collapse
Thanks, but I already did that last night and still the same thing nothing different at all changed for me, it was a complete waste of time!
bigj0110 said:
Thanks, but I already did that last night and still the same thing nothing different at all changed for me, it was a complete waste of time!
Click to expand...
Click to collapse
That stinks, hopefully the next update will fix things for you. Mine has been running fine for the most part.
Misterxtc said:
That stinks, hopefully the next update will fix things for you. Mine has been running fine for the most part.
Click to expand...
Click to collapse
3 different devices and still the same exact major things plus new things on each device are going on with the phone. Switching out the device should fix it all, but I guess this is not the case here. Plus about the wifi issues I'm in a XDA forum 13 pages long about the phones wifi not working(I know it says edge, but it's the same problems with the S6 and S6 edge so no difference)
http://forum.xda-developers.com/galaxy-s6-edge/help/wifi-dropping-t3079504
I would not be surprised to see that the new upgrade to lollipop was to foil or prevent root. Kind of like the s4. screwed up everything now I have no root.
THANKS SAMSUNG !!!!!!
traco1 said:
I would not be surprised to see that the new upgrade to lollipop was to foil or prevent root. Kind of like the s4. screwed up everything now I have no root.
THANKS SAMSUNG !!!!!!
Click to expand...
Click to collapse
They already said that the new update(5.1.1) is taking away root
My 1st phone which arrived on Sat came with G920VVRU1A0E2 out of the box.
Other than normal setups, and uninstalling Google Play Services and Google Play it has not had any problems.
Perhaps you should go into a store and show them how it is not working?
traco1 said:
I would not be surprised to see that the new upgrade to lollipop was to foil or prevent root. Kind of like the s4. screwed up everything now I have no root.
THANKS SAMSUNG !!!!!!
Click to expand...
Click to collapse
Ya you're thanking the wrong company here. You need to thank Verizon...
krelvinaz said:
My 1st phone which arrived on Sat came with G920VVRU1A0E2 out of the box.
Other than normal setups, and uninstalling Google Play Services and Google Play it has not had any problems.
Perhaps you should go into a store and show them how it is not working?
Click to expand...
Click to collapse
I did on launch day, I went back to the same corporate store a few hours later and got into a fight with the sales rep who sold me the phone a few hours earlier and the store GM because they were Ignorant because my phone was hot as fuc k at 90F and hotter and they said nothing was wrong. On top of that they even lied to me about having the edge devices in stock on launch day and even pulled out the normal S6 trying to trick me and it was not until I said something did he say oh this is not an edge and then said there was no edge's in stock, but while I was waiting in line I asked him and 2 other reps and they all said they had the white 64GB edge in stock. They rather lie to there customers to make a sale then tell the truth(at least this corporate store location), and then when you have problems with the phone they don't care to help you at all. Even 611 said this was very wrong and made a complaint on mine and 611's behalf on the corporate store and the sales rep.
Misterxtc said:
Have you tried using Odin to flash back to stock with the full tar file instead of the update? If not go here and give it a shot. If you use the OE2 one you will have to factory data reset to wipe your phone clean either after or before you flash.
Click to expand...
Click to collapse
Here is an update, as of recently my phone is getting really really hot and temperatures of 120F+ and even Verizon technical support saw that through their diagnostic system as it was actually on those temperatures at that very moment when they were looking. Also, from me just being tech savvy and Verizon technical support confirming it as well this phone is also supposed to have a safeguard in the phone and if it gets too hot the device is upposed to power off on its own, but apparently the safeguard is not working because when the phone gets very hot the battery starts flashing and in the middle of the screen it tells me the phone is very hot and it only lets me click OK. If I'm charging the phone the battery flashes and say the same thing but just adds unable to charge, & I can unplug the charger and immediately plug it back in to the phone and it will start charging again and then a few minutes later it will give me the same message. When it's doing that its not supposed to tell me anything it's supposed to just shut off and its not doing so.
So there overheating policy states that I have to bring my phone too a corporate store and they're going to replace the device right on spot. So Sunday I went to the corporate store to do that, but for some reason their system wouldn't allow them to process this because it didn't have an option to do it and the general manager and the store representative we're booth trying together for at least 45 minutes. They ultimately ended up just sending me a replacement device via Fedex to my house and when the phone arrives today(7-2) I have to bring the overheating device that I currently have to the store so they can do what they need to do to send it back because by law I'm not allowed to send an overheating device back. Verizon corporate store processed my order on Sunday and I was supposed to get the device on Tuesday but I'm getting it today due to inclement weather at the FedEx Memphis Tennessee hub and so Fedex at the Memphis Tennessee hub was at a complete standstill and my package was part of it.
Once I get my 4th replacement device and start using it for a while I will let you know how it's working
So I'll try to keep this as short as I can. Basically, this is my gf's phone that she gave to me. Ever since it updated to 6.0.1, she's had nothing but problems with it. Constant freezing, lagging, restarts, SMS trouble, poor battery life, you name it. Recently AT&T rolled out an update and her phone upgraded automatically. After that it pretty much bricked. The update failed for some reason and the phone got stuck in Download Mode. And then it didn't turn on for almost a week. Since her phone is a couple months out of warranty, she was forced to upgrade to an S8, and she gave me this Note Edge.
Yesterday I spent a few hours trying to fix it. I finally managed to get it to power back on and flash a PIT file to it, then flashed a fresh install of 6.0.1 to it. It worked okay for maybe 10 minutes, but then it would reboot every time you tried to lock or unlock the screen, and was still super laggy. So I decided to to give it another try and I managed to downgrade it to 5.1.1. It seems to be working great at the moment (fingers crossed).
So after reading here in the forums, it seems that you can't root AT&T Note Edge's. Bummer. I was hoping I'd be able to disable updates on this phone, unlock it, and use it on a new carrier (I think Verizon is trying to kill my Note 4 now).
So my question is, is there any way that I can keep this phone on 5.1.1? I know this sounds stupid, but I'm not sure how AT&T updates work, if they're forced or you just get annoying pop-ups. Right now I'm reluctant to connect the phone to WiFi, and there's no SIM card in it. Either way I'd just like to disable updates.
I haven't messed with rooting since my S4, which was about 3.5 years ago, but if there's something I can do to keep this phone on 5.1.1, I want to try it. Thanks.
camismacho said:
So I'll try to keep this as short as I can. Basically, this is my gf's phone that she gave to me. Ever since it updated to 6.0.1, she's had nothing but problems with it. Constant freezing, lagging, restarts, SMS trouble, poor battery life, you name it. Recently AT&T rolled out an update and her phone upgraded automatically. After that it pretty much bricked. The update failed for some reason and the phone got stuck in Download Mode. And then it didn't turn on for almost a week. Since her phone is a couple months out of warranty, she was forced to upgrade to an S8, and she gave me this Note Edge.
Yesterday I spent a few hours trying to fix it. I finally managed to get it to power back on and flash a PIT file to it, then flashed a fresh install of 6.0.1 to it. It worked okay for maybe 10 minutes, but then it would reboot every time you tried to lock or unlock the screen, and was still super laggy. So I decided to to give it another try and I managed to downgrade it to 5.1.1. It seems to be working great at the moment (fingers crossed).
So after reading here in the forums, it seems that you can't root AT&T Note Edge's. Bummer. I was hoping I'd be able to disable updates on this phone, unlock it, and use it on a new carrier (I think Verizon is trying to kill my Note 4 now).
So my question is, is there any way that I can keep this phone on 5.1.1? I know this sounds stupid, but I'm not sure how AT&T updates work, if they're forced or you just get annoying pop-ups. Right now I'm reluctant to connect the phone to WiFi, and there's no SIM card in it. Either way I'd just like to disable updates.
I haven't messed with rooting since my S4, which was about 3.5 years ago, but if there's something I can do to keep this phone on 5.1.1, I want to try it. Thanks.
Click to expand...
Click to collapse
You should be able to turn off auto updates in the about phone area of the settings menu.
You might want to turn off the picture sync'ing in the settings area of gallery....three dots,top right corner.
Wondering if this is isolated to my phone or if its systemic. I have never modified my phone, its stock from Google directly. Twice now, the phone starts running slow/acting strange, then will reboot and say that the system is corrupted and will not load. I tried to sideload the latest OTA to recover, but doesnt take. I literally have to do a full hard reset to get the phone back. The phone has done this to me twice now randomly. I have never had a phone, especially not modified at all, just randomly corrupt itself let alone do it twice. Has this happened to anyone else?
Wondering if I should have Google send me another phone.
iceman4357 said:
Wondering if this is isolated to my phone or if its systemic. I have never modified my phone, its stock from Google directly. Twice now, the phone starts running slow/acting strange, then will reboot and say that the system is corrupted and will not load. I tried to sideload the latest OTA to recover, but doesnt take. I literally have to do a full hard reset to get the phone back. The phone has done this to me twice now randomly. I have never had a phone, especially not modified at all, just randomly corrupt itself let alone do it twice. Has this happened to anyone else?
Wondering if I should have Google send me another phone.
Click to expand...
Click to collapse
For me this sounds like a hardware failure and I'd try to get the phone replaced.
Probably the NEW in house TITAN chip.
There must be something on your device. Factory reset it. Should be yohr best bet.
dirtyreturn said:
Probably the NEW in house TITAN chip.
There must be something on your device. Factory reset it. Should be yohr best bet.
Click to expand...
Click to collapse
I agree and think it could be hardware. I have Factory reset the phone twice already.
The firmware flash may have become corrupted therefore factory resets are useless.
Flash data has a limited lifespan usually this doesn't become an issue but it can.
Reflash and see if it holds. Otherwise it's likely a memory chipset or mobo failure.
This happened to me. Was running one of the developer previews and chalked it off to that. lost everything I didn't back up the night before (out of habit from messing with my phones I do daily backups of the important folders and phone data). The only thing that worked for me was re-flashing factory image and start fresh. Hasn't happened again for me.,
I had a similar experience about a month or two ago. Same situation, stock firmware on an unlocked device direct from Google. I had thankfully backed up about a week prior.
EvilRubberDuck said:
I had a similar experience about a month or two ago. Same situation, stock firmware on an unlocked device direct from Google. I had thankfully backed up about a week prior.
Click to expand...
Click to collapse
For the system to go corrupt by itself is rare unless there's a hardware fault.
More than likely it was 3rd party software that caused it. Launchers, power management apps are prime suspects.
Androids are typically a very stable platform.
**Solved posting update in thread.
Purchased S21+ from Samsung online for Verizon Network, every OTA update since purchase results in it failing to the downloading screen with "
partition super Reason SUPER: Build-id does not match with the reference" I have been able to resurrect it successfully by entering the recovery mode and performing a factory reset. But each OTA update push results in the same issue.
Samsung wants me to either send them the phone or take to a repair location for a software refresh as they called it. Problem is nearest repair center is 3+ hours away from me or 5-7 day turn around on the mailed device with no backup phone.
Has anyone else encountered this and does anyone here have a solution to fix this myself? I am comfortable using Odin and flashing roms but not sure if this will fix it.
have you talked to verizon?
Post Nine said:
have you talked to verizon?
Click to expand...
Click to collapse
Yes, Spoke with their Tier 2 support. Tier 2 discussed the issue and implied a change of information for the phone would fix it. They transferred me to Samsung due to the phone being purchased direct from Samsung.
Ok so the problem seems to have been resolved. Here's what I did to fix it.
Downloaded the current firmware I had before the update from Sammobile.com. Using Odin I installed the firmware I was currently on. I had done this before on the last update that failed. But this time I gave it the user data info and did use the Home CSC in an effort to reset everything.
Phone came back online functioning normally with everything wiped. I connected to WiFi and let the first of 2 updates download then run. Success . First OTA that's been successful on the phone. Then went for update #2. Failed, but rebooted this time and gave me an Error 402. Tried again a little later, same WiFi. It redownloaded the update and success again.
So it seems it needs a very very stable internet connection and the full wipe fixed the build id mismatch.
Also before attempting updates highly recommend having all your 2FA accounts either backed up, a second authenticator on another device or turned off. Its a real PITA to get back into all your accounts when your authenticator app gets wiped unexpectedly.
Hope this helps someone else!
CBH60 said:
Hope this helps someone else
Click to expand...
Click to collapse
Thank you!!! I was stuck on this screen all day!
I had restored my S22 Ultra, as a last resort to troubleshoot the shut down/reboot issue I, like many others, have been experiencing. When my phone then updated itself afterward, the install failed and I was stuck. I just happened to find this post of yours, while I was researching some info someone at the Geek Squad gave me, and told me to try it when I got home. The print out he gave me was a word for word copy of your solution! It totally worked, and I am back in. Now to see if the shut down/reboot issue recurs..... I suspect it will, I'm thinking it has something to do with my battery, which I can't remove.
Ardera_Sempre said:
Thank you!!! I was stuck on this screen all day!
I had restored my S22 Ultra, as a last resort to troubleshoot the shut down/reboot issue I, like many others, have been experiencing. When my phone then updated itself afterward, the install failed and I was stuck. I just happened to find this post of yours, while I was researching some info someone at the Geek Squad gave me, and told me to try it when I got home. The print out he gave me was a word for word copy of your solution! It totally worked, and I am back in. Now to see if the shut down/reboot issue recurs..... I suspect it will, I'm thinking it has something to do with my battery, which I can't remove.
Click to expand...
Click to collapse
Hey did you ever get this screen again? And were OTA updates normal after you flashed?
OTA updates keep failing for me on my S22+, either at 25% causing it to go back to the old firmware with an error message, or getting bricked showing that screen. I've tried to reflash and then update and so far only solution is flashing the update through Odin every time. I have had only 2 successful OTA updates since I got this phone in April
AliRAS said:
Hey did you ever get this screen again? And were OTA updates normal after you flashed?
OTA updates keep failing for me on my S22+, either at 25% causing it to go back to the old firmware with an error message, or getting bricked showing that screen. I've tried to reflash and then update and so far only solution is flashing the update through Odin every time. I have had only 2 successful OTA updates since I got this phone in April
Click to expand...
Click to collapse
I did not have any further issues with updates failing, and getting this screen again. I DID have to send my phone back to Samsung twice though for repair, because of the constant rebooting issue. They could NOT repair that issue, so I ended up getting a refund for the phone. Due to their p**s poor customer service (more than a month later I'm still trying to get them to return the charger for the phone, that they said I HAD to send back with the phone for testing), I will (very unhappy) be purchasing an iPhone. Never buying Samsung again.
Ardera_Sempre said:
I did not have any further issues with updates failing, and getting this screen again. I DID have to send my phone back to Samsung twice though for repair, because of the constant rebooting issue. They could NOT repair that issue, so I ended up getting a refund for the phone. Due to their p**s poor customer service (more than a month later I'm still trying to get them to return the charger for the phone, that they said I HAD to send back with the phone for testing), I will (very unhappy) be purchasing an iPhone. Never buying Samsung again.
Click to expand...
Click to collapse
Damn that sucks never heard of them needing the charger as well for tests, that is a bit odd. The reflash seems to have fixed the rebooting issue I had when I first got my S22+ not sure if I should gamble with trying to update again after the last one failed. Might just wait for One UI 5 and do a dirty flash through Odin and if it doesn't give any problems I'll just flash the security updates every so often I guess. Saves me the stress haha.