Related
I just spoke with the Android dept at AT&T who where I spoke to a gentleman named Jeremy Everson. After he informed me that I was the 6th caller he had had in the past 3 hours about the failing updates...he called Samsung on a 3-way conversation with me.
Here's what I found out. If you DO NOT HAVE GPS, EMAIL OR MMS PROBLEMS...THEN THE UPDATE MAY BRICK YOUR PHONE. THIS IS ATT AND SAMSUNGS RESPONSIBILITY AND THEY ARE GOING TO FIX IT.
AT&T IS WORKING DILIGENTLY WITH SAMSUNG AND MR. EVERSON INFORMED ME THAT THEY ARE FRUSTRATED AT THE BLURRY COMMUNICATION WITH SAMSUNG OVER THIS UPDATE.
All in all...there are no answers yet as to why this update isnt working...but we know that it is causing problems.
Basically, what that tells me is stop resetting, odin-ing, unrooting, and reflashing...it is a problem on Samsungs end...not your device.
fiendiish said:
I just spoke with the Android dept at AT&T who where I spoke to a gentleman named Jeremy Everson. After he informed me that I was the 6th caller he had had in the past 3 hours about the failing updates...he called Samsung on a 3-way conversation with me.
Here's what I found out. If you DO NOT HAVE GPS, EMAIL OR MMS PROBLEMS...THEN THE UPDATE MAY BRICK YOUR PHONE. THIS IS ATT AND SAMSUNGS RESPONSIBILITY AND THEY ARE GOING TO FIX IT.
AT&T IS WORKING DILIGENTLY WITH SAMSUNG AND MR. EVERSON INFORMED ME THAT THEY ARE FRUSTRATED AT THE BLURRY COMMUNICATION WITH SAMSUNG OVER THIS UPDATE.
All in all...there are no answers yet as to why this update isnt working...but we know that it is causing problems.
Basically, what that tells me is stop resetting, odin-ing, unrooting, and reflashing...it is a problem on Samsungs end...not your device.
Click to expand...
Click to collapse
That doesn't help those of us with completely bricked phones...
qwertyaas said:
That doesn't help those of us with completely bricked phones...
Click to expand...
Click to collapse
Contact Samsung 1800 726 7864. That's the number I was given by AT&T to call. Or, take your phone to an AT&T store. You did nothing to brick your device. This is their issue.
We have the choice to not do the update, right? I think I read that from another thread somewhere, but I just wanted to double check. I haven't received a notification from AT&T yet about the update, but when I do, I don't think I want to go through with it seeing how there are a lot of issues with the update.
"AT&T does not provide technical support for the Samsung Captivate update and makes no warranties, express, implied or statutory, as to the content within this solution; such content is provided "as is" and with all faults, and your use of the content is at your own risk. "
this is a mess
Oh mannnn...after reading your painful story with AT&T & Samsung...all I want to say to those people is "F*** YOU!!".
WTH have you guys been doing for 2 months???
You have spent 2 months to come up with the phone bricker not the problem fixer???
I really want to switch to Android world but it seems starting with Samsung is one hell bad idea of mine. Maybe I should wait for the phones from other makers.
well... at least they're aware that there is an issue
Well.. if you think about it, as soon as we rooted our units.. there goes AT&T's responsibility.
That's the thing I noticed the most about AT&T, they are pros are shifting to blame to anyone but themselves.
If you're under the 30 day return policy return it ASAP, No hesitation, talk to a manager if necessary.
For those over 30 days hope for the best, make AT&T and Samsung aware of your issue.
I just got off the phone with AT&T they are sending me a new phone. Spent about 45 minutes on the phone doing through all of test they do to try and get the update. The tech I talked to is actually overnighting me a new phone. I had to agree to the terms that there is no physical damage or liquid damage. There is none.
I claimed my GPS failes to aquire a viable signal. Network tower triangulation is not acceptable. I waited passed the 30 days for this update that was promised and I can no longer get.
I have used ODIN in the past and believe something with it is causing the problem. Before I ever used odin I had a backup made of my entire phone with just a root.
Tried to use ODIN and restore my previous ROM with no luck still failing at 50%. I have removed all traces of lagfix, root, roms and still can not get the update to take. I even swapped out the SIM card at the store. All of it failed so the tech had them rush me a new phone.
thehavock18 said:
I just got off the phone with AT&T they are sending me a new phone. Spent about 45 minutes on the phone doing through all of test they do to try and get the update. The tech I talked to is actually overnighting me a new phone. I had to agree to the terms that there is no physical damage or liquid damage. There is none.
I claimed my GPS failes to aquire a viable signal. Network tower triangulation is not acceptable. I waited passed the 30 days for this update that was promised and I can no longer get.
I have used ODIN in the past and believe something with it is causing the problem. Before I ever used odin I had a backup made of my entire phone with just a root.
Tried to use ODIN and restore my previous ROM with no luck still failing at 50%. I have removed all traces of lagfix, root, roms and still can not get the update to take. I even swapped out the SIM card at the store. All of it failed so the tech had them rush me a new phone.
Click to expand...
Click to collapse
Wow, so anyone getting this phone should really just wait for the phones that are pre-installed with this update already.
Sounds like Ill have to wait a few months then.
Thanks for the info.
fiendiish said:
Contact Samsung 1800 726 7864. That's the number I was given by AT&T to call. Or, take your phone to an AT&T store. You did nothing to brick your device. This is their issue.
Click to expand...
Click to collapse
I was within my 30 days so they gave me a new Captivate. Sadly, I haven't had a chance to back up my old phone so everything is gone from there.
For some reason, the AT&T employee said this uses my only 'exchange' in terms of warranty. I didn't even bother to argue as that makes no sense - how is replacing a bricked phone (that was bricked on an AT&T update) 'exchanging' the phone [as in being able to exchange to a different phone].
orlandoxpolice said:
"AT&T does not provide technical support for the Samsung Captivate update and makes no warranties, express, implied or statutory, as to the content within this solution; such content is provided "as is" and with all faults, and your use of the content is at your own risk. "
this is a mess
Click to expand...
Click to collapse
I would think that one could argue successfully to get a new phone regardless, because this update is being pushed to the phone and not voluntarily download (by some), I woke up to a message that the device had fail to connect to the server (thank god) for the update. but if they're updating your phone without your approval then they (whomever is pushing the update) can't absolve themselves of responsibility. unless my not reading the EULA leads to it saying something like, we can do what we want when we want and you can suck it!
fiendiish said:
Here's what I found out. If you DO NOT HAVE GPS, EMAIL OR MMS PROBLEMS...THEN THE UPDATE MAY BRICK YOUR PHONE. THIS IS ATT AND SAMSUNGS RESPONSIBILITY AND THEY ARE GOING TO FIX IT.
Click to expand...
Click to collapse
Not sure if that's true. I have GPS issues (Even outside on a clear night it took more than five minutes for me to get a lock). My phone is bricked.
A new one is on the way. Should be here tomorrow.
How will I fix the software/hardware freezing, delay in hanging up the phone, random reboots, etc if I did not root my phone? LG said to send it in but I don't have a warranty since I bought a refurb off Ebay. T-Mobile probably cannot do anything either. I just want my phone to be fixed without costing me too much money. Can ICS be a solution if I can manually update my phone since I get an error message when I try to update my phone normally?
Root it, add a custom ROM. All issues solved.
Will rooting it be easy? I have very little experience with the file extensions on Android. I only worked on unlocking iPhones but I got consistant error messages when I tried to unlock those. I just don't want to brick my phone. I bearly know about some of the terms lol. Can you give me a link to a good root setup?
dwade22 said:
Will rooting it be easy? I have very little experience with the file extensions on Android. I only worked on unlocking iPhones but I got consistant error messages when I tried to unlock those. I just don't want to brick my phone. I bearly know about some of the terms lol. Can you give me a link to a good root setup?
Click to expand...
Click to collapse
I skipped to 2.3 so this is what I used:
http://forum.xda-developers.com/showthread.php?t=1255214
then flashed this rom:
http://forum.xda-developers.com/showthread.php?t=1124522
It wasn't that hard at all for me, just follow the directions and you'll be fine.
dwade22 said:
How will I fix the software/hardware freezing, delay in hanging up the phone, random reboots, etc if I did not root my phone? LG said to send it in but I don't have a warranty since I bought a refurb off Ebay. T-Mobile probably cannot do anything either. I just want my phone to be fixed without costing me too much money. Can ICS be a solution if I can manually update my phone since I get an error message when I try to update my phone normally?
Click to expand...
Click to collapse
Is your phone on 2.2.2 or 2.3.3? Also, LG will do warranty work on a phone 18 months from the date of manufacture if you do not have proof of purchase. They don't have to know you bought it second hand. If you tell them then you have no warranty. But if you don't mention anything, get an RMA and sent it in, most likely they will send you a refurb replacement.
As a preface, I got the ATT one x a few days ago, so far I'm really happy with it, but would like to get rid of a bunch of the bloatware and want to get root.
So this morning I woke up to the update message. Now I read up on it the night before on these forums that I should wait to update if I want to root/etc, so naturally I don't want to update quite yet. But here's the problem. The message popped up so fast that I could barely read the message. My thumb must have been right above the accept button, since the message disappeared almost instantly and the process started up. I exited it as far as possible, and it seemed to work. I used apps on the phone, and everything seemed fine. As soon as I locked the phone again, it decided to reboot, initiating the update, all on its own. Even a forced power-off wouldn't stop the wheels turning. And now I feel like an idiot. So is there any way/what is the best way to downgrade or reverse the update?
TL;DR: I accidentally updated the new update, is there, and or what is the best way to downgrade so I can eventually root?
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
I know that with enough time I could find some of these answers on the forums, but because they are so lively, it's hard to keep track and sift through the forums for information. Thanks for your time and thank you in advance for your help.
In regards to the root on the update there is no way to downgrade or root given your situation at this time but hopefully one of the talented people here on xda wil find a new exploit like they did for the 1.85
As far as warranty goes someone else will.have to let you know.
Sent from my Nocturnalized Beast
same boat
I am in exactly the same boat. I didn't check the MD5 on a download of CR4.5 and it completed wiped my phone (SD Card as well). I was away from my laptop and had to wait days to get it back online. When I finally got it up and running, I was rooting through the one click and in checking the update, it updated to 2.20. So now I'm stuck.
I have my previous unlock token, but I'm not sure if that will do me any good. I don't want to do much until a new RUU becomes available.
misiek93 said:
As a preface, I got the ATT one x a few days ago, so far I'm really happy with it, but would like to get rid of a bunch of the bloatware and want to get root.
So this morning I woke up to the update message. Now I read up on it the night before on these forums that I should wait to update if I want to root/etc, so naturally I don't want to update quite yet. But here's the problem. The message popped up so fast that I could barely read the message. My thumb must have been right above the accept button, since the message disappeared almost instantly and the process started up. I exited it as far as possible, and it seemed to work. I used apps on the phone, and everything seemed fine. As soon as I locked the phone again, it decided to reboot, initiating the update, all on its own. Even a forced power-off wouldn't stop the wheels turning. And now I feel like an idiot. So is there any way/what is the best way to downgrade or reverse the update?
TL;DR: I accidentally updated the new update, is there, and or what is the best way to downgrade so I can eventually root?
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
I know that with enough time I could find some of these answers on the forums, but because they are so lively, it's hard to keep track and sift through the forums for information. Thanks for your time and thank you in advance for your help.
Click to expand...
Click to collapse
BB2DX said:
I am in exactly the same boat. I didn't check the MD5 on a download of CR4.5 and it completed wiped my phone (SD Card as well). I was away from my laptop and had to wait days to get it back online. When I finally got it up and running, I was rooting through the one click and in checking the update, it updated to 2.20. So now I'm stuck.
I have my previous unlock token, but I'm not sure if that will do me any good. I don't want to do much until a new RUU becomes available.
Click to expand...
Click to collapse
The ruu is out for the 2.20 on the HTC dev site
If you already have your unlock token you should be fine just run through the steps to unlock then root. Your still stuck with the new hboot so your previous nandroids will no longer work and you can no longer flash boot images from recovery.
Sent from my Nocturnalized Beast
misiek93 said:
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
Click to expand...
Click to collapse
Consensus seems to be that a warranty return to AT&T, they don't normally check for bootloader unlock at all. Technically, they can check, and void your warranty. But to this point, they don't seem to be. This is probably your safest bet. But that warranty is only one year.
Based on various reports by XDA users HTC seems to be much more strict about enforcing their own warranty terms. I would suggest going through AT&T rather than HTC.
For your AmEx warranty, I think that would be handled by AmEx (not AT&T). You should probably check through them, and see what the warranty terms our (might be handled by a 3rd party?). I think only someone that has had experience with the AmEx process could say for sure what would happen in this case. So maybe somebody will chime in.
redpoint73 said:
Consensus seems to be that a warranty return to AT&T, they don't normally check for bootloader unlock at all. Technically, they can check, and void your warranty. But to this point, they don't seem to be. This is probably your safest bet. But that warranty is only one year.
Based on various reports by XDA users HTC seems to be much more strict about enforcing their own warranty terms. I would suggest going through AT&T rather than HTC.
For your AmEx warranty, I think that would be handled by AmEx (not AT&T). You should probably check through them, and see what the warranty terms our (might be handled by a 3rd party?). I think only someone that has had experience with the AmEx process could say for sure what would happen in this case. So maybe somebody will chime in.
Click to expand...
Click to collapse
Amex is extremely lax. All they want is a copy of the original warranty and require doing the work at an authorized repair shop. Then they reimburse you, no questions asked.
GroovyGeek said:
Amex is extremely lax. All they want is a copy of the original warranty and require doing the work at an authorized repair shop. Then they reimburse you, no questions asked.
Click to expand...
Click to collapse
I kinda figured as much. They aren't in the business of fixing phones, so I guessed they either just farmed it out to a 3rd party company, or just paid up pretty easily. Credit cards (especially AmEx) also often cover things like lost luggage, travel insurance (cancelled flights, etc.) and I don't imagine they go through much hassle confirming that kind of thing either. They must figure that the extra business gained from offering their services (and yearly fees) outweighs the payouts they have to make.
Thanks for clarifying with your personal experience, probably useful to the OP.
I have a P6810 that was imported from Hong Kong by Expansys. My warranty is valid until August 25, 2013. The screen has a problem where it sometimes intermittently flashes dark lines on the screen. Full screen vertical lines. It's really just like those columns of pixels aren't being lite up to the same degree as the others, and not as brightly as they should be.
It doesn't do it all the time, but it has become more frequent, and it appears in all applications as far as I can tell. I have not yet reloaded the firmware because personally it seems like more of hardware problem. Either the LCD or the LCD driver is failing.
The only place that seems to be willing to work on it is Samsung Warranty Repair in Hong Kong, and they do not accept devices that have been shipped to them for repair. All warranty repair work there must be hand delivered. I'm in Hawaii and that is not an option. Expansys is of no use. They just said contact Samsung Hong Kong Warranty Repair.
Is there anybody that works on the P6810 state side? How much does it cost to replace the LCD or the motherboard? Does anybody know? It will cost me at least $60 just to ship the thing back to Hong Kong anyway, so I'm willing to investigate other options, but I don't know what they are for a specialty item like the P6810.
me too on p6800..
i have the same issue here but i am not sure if it is really hardware fail as i am using custom erobot rom v2.3
Thank you for the response
Salamonti said:
me too on p6800..
i have the same issue here but i am not sure if it is really hardware fail as i am using custom erobot rom v2.3
Click to expand...
Click to collapse
Thanks for the response. With only 2 of us responding so far it's hard to know if its just because a Super AMOLED of this size is a new technology, and there were still some bugs not worked out in the processing, or if it is as you say, and as I'm hoping, just a software issue.
My P6810 hasn't done it at all for about 2 weeks now. I'm hoping that when Ice Cream Sandwich is pushed out, that it will solve the problem once and for all.
My findings were that since mine is a p6810, it won't be fixed under warranty, and Samsung won't fix it even if I pay for it, unless I hand deliver it to Hong Kong. If I'm confident that the problem is the hardware (I'm not), then I have to buy a used p6800 on eBay and try to fix it myself. I'm not going to do that.
If yours is a p6800 couldn't it have been fixed under warranty in the U.S.? I wonder if your erobot rom 2.3 is using the same graphics driver code as Jelly Bean? In other words, was erobot rom v2.3 a custom ground up recode of everything, or did they cannibalize Jelly Bean for sections of code?
I love my p6810. I'm in Hawaii and don't have TV. I read on it every morning and watch movies on it almost every night. It's the perfect 7" tablet in my opinion, but that display issue drives me crazy.
I guess one of the morals of the store is to not trust Expansys if they tell you that they have a grey market item that is fully covered under the manufacturers warranty. They told me that, but it was not true.
i am not in US and my tb is not covered by warranty either (as i am in Egypt)
my custom rom is built on JB 4.1.2
but i know nothing about display driver so i cant figure it out
Thanks
Salamonti said:
i am not in US and my tb is not covered by warranty either (as i am in Egypt)
my custom rom is built on JB 4.1.2
but i know nothing about display driver so i cant figure it out
Click to expand...
Click to collapse
Thanks for your response. When Ice Cream Sandwich comes out, I will reply about whether or not it fixes the problem.
Arobase40 said:
Some clues you may investigate on...
On the technical aspects :
- You can try to do a factory reset and see if that solve your display issue.
- Try to flash any official ROM : HC or ICS even though this is a European version.
- If the display issue is still there, then you can consider this as a hardware failure. I don't know how Law works in your country, but you could try to find a non profit organization specialized in juridical procedures which could help you in forcing Expansys to support the warranty procedure... ^^
---------- Post added at 11:38 PM ---------- Previous post was at 11:33 PM ----------
Unless you are a good developer or a very good modder and you like to play dice, don't even try to use the eRobot rom with your P6810...
Click to expand...
Click to collapse
Thanks Arobase40.
I will probably wait until ICS comes out and then factory reset and install/upgrade to ICS immediately.
On Expansys, just as a matter of justice, I wish I could force them to do something, but my warranty expired on 8/22/13. They wouldn't answer their phone and only responded to one of several emails, saying "Contact Samsung". I think the most effective thing I can do is just let other members of xdadevelopers know what happened to me relative to Expansys.
Thanks for your input Arobase40, I appreciate your suggestions.
Arobase40 said:
I don't really understand your position about your GT 7.7 ???
As you were talking about P6810, I assumed you were talking about the International version, right ???
Then, as I said you could flash a European firmware with PC Odin as I don't think Samsung will deliver any further updates/upgrades... ^^
But whatever, and again you could simply do a factory reset to see if that solve your issue...
But if you already used a Cyanogen firmware, then just forget everything about what I said, and forget about your warranty as well... ^^
I don't understand what the members of xdadevelopers could do for you relative to Expansys, except suggesting you to contact your local non profit organization, if there is one (should be existing) ?!?!?!
Which Expansys is it ? A US one or any others ???
You have to write them an official letter as "Registered Letter with Acknowledgement of Delivery" to make things official so the warranty will be extended "indefinitely" until Expansys solve your problem...
But again, get informed yourself about your local rules or laws !!!
I got a similar problem with ASUS, as my TF101 returned 3 times in their repair center and the last time they "lost" it (it was stolen on the way to the Repair Center)... ^^
ASUS accepted to pay me back the price I paid for it but refused to compensate the prejudice as they awaited a very long time (about a month) before they just started to investigate on what happened to my device... ^^
I first wanted to go on trial with ASUS, but I tried first an official transaction with the help of a retired judge (as member of a non profit organization)...
So they finally accepted to compensate an additional 250 € of the initial 540 € price I paid (got a 60 € discount from official price)... So I got 790 € and didn't pay anything for a lawyer or for the Trial procedure...
On the other hand, if we were going to a Trial, ASUS knew they will loose and would have to pay MUCH MUCH more...
YOU are the only one to know if you want to take your chance...
Click to expand...
Click to collapse
Thanks Arobase40,
Yes I am talking about a Hong Kong version. It arrived default in Mandarin(?).
The only ICS 4.2.2 version I could find was P6810XXLPL_CSC_XEU with is the United Kingdom version. I’ve downloaded it. My preference is to use this one so that my P6810 defaults into English. I do plan to use Odin for this (probably this weekend).
My planned strategy is to do a factory reset to positively flush everything out, and then use Odin to update to ICS 4.2.2. My preference is to do everything at once, and only once, because even though I have Titanium Backup installed and running, my experience with my Nook was it still took several hours to get everything setup correctly after a factory reset.
I don’t have Cyanogen firmware installed, as my goal in getting at P6810 was to buy the best, and therefore not have to spend much time mod’ing it. I have rooted though so that I could install fonts with diacritical marks.
In terms of alerting xdadevelopers to Expansys policies, the best way to get Expansys to change their policies is enough people give them feedback during the purchasing process. If I had been able to read a post like this prior to my purchase of my P6810, I would have asked more questions and made a few phone calls, and I would have been better informed and wouldn’t have purchased from Expansys unless that had been able to give me some kind of further assurance that they would stand behind the product if it was required.
Yes it was the Expansys in the U.S. It’s the one you find on the internet when Googling within the U.S..
Thanks for the suggestion on the “Registered Letter with Acknowledgment of Delivery”.
Part of the problem is that for the past month, my P6810 hasn’t displayed the problem. I’m confident that it’s coming back sometime in the future, and probably worse, but intermittent problems are tricky to demand repairs on. If the “Registered Letter with Acknowledgment of Delivery” would get me an indefinitely extended warranty though, it could be worth it. It kind of boils down to a question of how much time would it take me versus other options. I’ll have to think about it. In any case, thanks for your suggestions.
I will try to go ahead and factory reset, then update to ICS 4.2.2 this weekend and see what happens. Actually, interestingly, my P6810 tells me that it has ICS 4.2.1 installed right now, as of early July. That surprised me when I saw it yesterday because I don’t remember that happening. I certainly didn’t do it. But maybe that’s why the screen problem went away?
Arobase40 said:
GOTCHA !!!
Sounds like there are many confusions with your explanations... ^^
1) ICS is Android 4.0.x !!!
2) 4.1.2 or 4.2.2 are Jelly Bean Android versions !!! NONE of them are available for P6810 yet and will probably never be... ^^ Yes I know, I'm very defeatist and somewhat negative in my position, but Sammy will maybe prove I was wrong...
3) If your device tells you have ICS 4.2.1, then there is something wrong somewhere !!! ^^
This is the first thing you'll have to investigate on...
4) NO ONE as P6800 or P6810 owners got a 4.2.2 Android versions, and we will most probably never get such versions... ^^
5) On Expansys policies and responsibilities concerns : have you fully been informed they would send you a H.K version when you bought this device ??? Check at this when you ordered it and what your delivery and invoice mentions/forms...
6) There may be a slight chance, but go on the Samsung US website to find out the Phone number or the mail address by which you can contact them and described your issue (after you're fully sure about the real Android version you have...) and ask them for help/support and/or a RMA to send your device for repair. They will tell you if they accept to take your device under warranty to a US repair center... ^^
In Europe, we are probably better protected against juridical aspects compared to the US, but we obtain less as damages when we win while in the US you can get MUCH MUCH more if you can afford a Trial...
7) But before going that far : backup up all your internal storage (including the Titanium Backup folder) onto your hard disk computer or an external USB HDD...
8) Optionally, use Kies to backup up all your data and apps.
9) Make sure your battery is fully charged.
10) Get into your Settings and in the Backup and Reinit tab option and select "Re establish default param" (I'm unsure about the real words, as I don't have a US/English firmware version, but you should find out...
It shouldn't be that long before it'll reboot and ask you to reconfigure your Tab.
11) Don't reinstall anything and take awhile and your time to check & assure that solve your display issues. Update your default apps with Google Play and see if that's still good...
12) Finally you'll have 2 options : restore everything with Kies or copy back the Titanium Backup folder from your backup place to the internal storage, download TB and restore everything.
If after the restore you encounter the same display issues again, then you'll know you must not do a full restore, but just your apps... ^^
13) Before you try to update/upgrade or flash anything, make sure which firmware version you're downloading and installing !!! LOL
Good luck !
EDIT : when you buy anything anywhere better is to read the terms and conditions of the Online retailers... ^^
http://www.expansys-usa.com/terms/
In the European or French Expansys website, they can't do what they want as European/French rules & laws better protect customers against such illegal restrictions !!! ^^
I guess you should have consumers organizations as the ones I was referring earlier at your place, when needed...
Click to expand...
Click to collapse
Thanks Arobase40,
1) You're right. I've just checked and its 4.0.4 installed. ICS was an update I made shortly after I purchased the unit. Since there will be no JB for the P6800/P6810, there's no point in my waiting for it.
5) There was no indication that an HK version would be sold/shipped. Also it does not indicate that anywhere on the receipt. I knew it would be a non-U.S. version, because Samsung only sells the P6800 within the U.S.
6) I tried asking Samsung's U.S. warranty repair center if they could repair it, but they go by model numbers, and the P6810 is not one that they will touch. Same thing with the U.K. Samsung Warranty Repair Center, they said that the serial # indicated that it wasn't made in the U.K., so they could not work on it. I couldn't even find anyone in the U.S. who sells parts (i.e. LCDs) for it, it's such a speciality item.
7 - 13) Thanks for the detailed steps. Since I realize now that I was completely confused about the version of my firmware, I realize that for sure, I'm going to have to do one or all of the steps you have outlined.
Thanks again!
Long time lurker, not much of a poster here in the S4 forums (former owner of S2 and Motorola Atrix, rooted and had lots of ROM fun with both until they crapped out).
In speaking with Samsung, AT&T, and Best Buy reps I may have found a potential way for all of you wanting to get back from 4.3, 4.4.2 NB1, or NC1 back to 4.2.2.
I expressed my phone's constant operational issues since moving from 4.2.2, and was essentially given the go ahead to visit an AT&T service center (not your standard AT&T store, but one of their direct service facilities that have many more technical resources and serviceable personnel) and they would reflash the phone from scratch with the original 4.2.2 software to attempt to "fix" my phone. If this is the case, the workaround the locked bootloader/Knox/Qcode might just be available wouldn't you all think?
I have an appointment with them tomorrow afternoon and will update as I am able to.
airforcerg said:
Long time lurker, not much of a poster here in the S4 forums (former owner of S2 and Motorola Atrix, rooted and had lots of ROM fun with both until they crapped out).
In speaking with Samsung, AT&T, and Best Buy reps I may have found a potential way for all of you wanting to get back from 4.3, 4.4.2 NB1, or NC1 back to 4.2.2.
I expressed my phone's constant operational issues since moving from 4.2.2, and was essentially given the go ahead to visit an AT&T service center (not your standard AT&T store, but one of their direct service facilities that have many more technical resources and serviceable personnel) and they would reflash the phone from scratch with the original 4.2.2 software to attempt to "fix" my phone. If this is the case, the workaround the locked bootloader/Knox/Qcode might just be available wouldn't you all think?
I have an appointment with them tomorrow afternoon and will update as I am able to.
Click to expand...
Click to collapse
Unless they exchange your phone, I doubt they'll get 4.2.2 on it. The reps are not very educated and probably just said that not knowing. So unless you get an exchange, this probably won't bring anything. Not to mention if all S4's suddenly come in for service that'll be suspicious.
Sent from my SGH-I337 running BlackBox 3.0
@Surge1223 maybe there's something he can possibly find out?
hope this isnt a dream thread. but which 4.2? though mf3 or mdl?
I don't know what you expect @Surge1223 to tell you. He wouldn't know anything about this. I can say though that from what I have read around here, it's impossible for AT&T to downgrade your device. Maybe OP will get lucky, but I bet they were just telling him something to get him to move on, because they couldn't solve his problem. Who knows though, I may be completely wrong. Wouldn't be the first time.
Maybe if they actually do work on his phone in person surge would have a question/s to possible ask whoever is working on his phone, of course unless they give him a refurbished device
Brooklynsour said:
Maybe if they actually do work on his phone in person surge would have a question/s to possible ask whoever is working on his phone, of course unless they give him a refurbished device
Click to expand...
Click to collapse
This. At best he will get a new/refurb device with MF3 on it.
There's no trick any tech can do to allow reversion to MDL, short of replacing the entire motherboard.
jeboo said:
This. At best he will get a new/refurb device with MF3 on it.
There's no trick any tech can do to allow reversion to MDL, short of replacing the entire motherboard.
Click to expand...
Click to collapse
Sadly this appears to be the case. The at&t rep I spoke with earlier this week was clearly incorrect. Within the past 3 months it appears that all device service centers have been recently outfitted with updates to their flashing system that ONLY includes the NB1 software. They tried to explain to me that no downgrade potential even exists, and that neither Samsung nor att (whether they may have the software existent in some form within their databases) "can", but obviously won't perform any downgrade of android software.
They've essentially created just another "failsafe" to prevent any further changes.
my apologies for getting anyone's hopes up.
You're good bro. We all figured that was the case.