yashsingh1/xdaforums huggingface dataset:
[Nexus 7 General] dirtyhamster73:
Staples told me the same thing after I declined their insurance. They said google will handle the warranty for the year if I don't go with staples.

It was the same thing with my Gnex.... I bought it from google and they handled things when I had an issue with it, not Samsung.
[Nexus 7 General] riot1031:
I just got off the phone with them. They're sending a replacement for my C60. It has a wierd bubble on the screen. It almost looks like a dead pixel, but much larger. I'm hoping the replacement is a C80!
[Nexus 7 General] randroid123:
Did u purchase through the play store or a different retailer?

---------- Post added at 05:38 PM ---------- Previous post was at 05:36 PM ----------

Also what number did u call to get in touch with them?
[Nexus 7 General] pxlitup:
I first heard about it on here before launch. Then someone posted something contrary so I called Google Support and specifically asked about it.

The rep I spoke with assured me that Google would be handling Play store warranties for the first year.

Here is the followup email I received.
[Nexus 7 General] randroid123:
I'm not a fan of your answer
[Nexus 7 General] pxlitup:
AFAIK, it's not posted anywhere on the website, which is strange since it would be a good selling point.

Call them yourself if my correspondence wasn't thorough enough, but I did ask the rep to send me something concrete in the email and that's all I received.

I'd be interested in further confirmation, so please report back if you choose to do this.
[Nexus 7 General] randroid123:
Not saying I don't believe u... Just saying I don't like it... Haha I'll look into it eventually but my screen lift is barely noticeable so pretty lazy about the whole thing
[Nexus 7 General] rkanwar:
I have just received my n7 ten mins ago. Absolutely pissed off. I receive a box where the side was scuffed. I thought noyhing of it. Pulled off the sleeve, the seals were broken, looked at the device fingerprints galore. Looked in the little box. No charger in it. What the hell! How are devices not floating around? Im pretty sure its not even 16gb however I cant see on the box where it states the capacity.

Update: just phoned google. The lady said shell sort a replacement out. But wait. After all of that the cssn number is not even for my order. So now I have to wait at least six hours to get an email from shipping to see what theyll do.
[Nexus 7 General] navodwickra:
Got my replacement unit yesterday (came with the return package and label :highfive:) So far so good :D
[Nexus 7 General] knight4led:
Was the label from Mountain View? I bet what happened is someone in the shipping department messed up UPS label numbers and wound up giving someone a label that sent their return to your house.
[Nexus 7 General] b34tn1k:
Received a bad replacement on the 20th, screen lift and blown speakers. It was a c70, my next replacement is set to arrive tomorrow. We'll see what I get
[Nexus 7 General] TitaniumBarbell:
My Serial Number begins with C70k. I just bought yesterday with no issues.
[Nexus 7 General] tombud10:
I bought my C70k N7 on the day of launch on the high street in the UK and it's absolutely fine. No screen lift, dead pixels or blown speaker. Bit of rippling on the left side and a minute bit of bleed on a black screen with the lights off but it's not noticeable. I think I've been pretty lucky as I have a good unit and I was probably one of the first people in the UK to have a N7.
[Nexus 7 General] Solange82200:
I went through four devices to get a decent one like I have now, and obviously that didn't happen in 15 days. As long as you bought it from the play store, you're fine.
[Nexus 7 General] randroid123:
Nah that's not what I was referring to... I misunderstood, I thought someone said Google was handling not ASUS. Period. I bought mine at Staples :(
[Nexus 7 General] cmg5461:
Play store handled my claim. I got the tablet on the 30th out something. Ordered the replacement on 20th
[Nexus 7 General] randroid123:
But u bought the original unit from the play store yea?
[Nexus 7 General] tvdang7:
I got a c80 16 gb from game stop yesterday works great.
[Nexus 7 General] jamesst20:
Awesome man! That means once I will receive an email to get replacement, there is no danger to get a broken screen :D
[Nexus 7 General] TheMuffStuff:
Ordered mine a couple days ago, I hope its c80k ;)
[Nexus 7 General] randroid123:
My friend just picked up a c70 that's perfect and had a couple fingerprints on it in the packaging.... Looks like they've been quality checking everything for the past month
[Nexus 7 General] jamesst20:
It is (1) 855-83-NEXUS or well spelled (1) 855 836-3987

Envoyé depuis mon Nexus 7 avec Tapatalk
[Nexus 7 General] randroid123:
Just called... If u purchased from retailer other than play store, u gotta go through ASUS :( but he did confirm that they are well aware of defects and new batch should be all good to go
[Nexus 7 General] demandarin:
Well I might be joining the replacement crowd now. I have slight screen lift on left side and speakers sound all distorted or possibly blown.

What is the exact number everyone is using to call Google for replacement? Also, when you call, and tell them the situation, they automatically send you a new unit with a return label&box for shipping your unit back to them? Do they put any type of holds on bank account or anything? Lastly, how long did it take them to send you a new unit from the time you called and they said they would?

Thanks in advance. I can't let this screen lift thing be ignored anymore. The speakers acting up was the icing on the cake to make me want a replacement now. Good to hear newer units seeming to have lift fixed.

Are they open on Saturday to call? Need that number everyone using ;)

Is it this number I saw posted " It is (1) 855-83-NEXUS or well spelled (1) 855 836-3987" ?

Also did anyone get a replacement and sent their unit back that was rooted and unlocked? Did they giveyou hassel over that or it didn't matter?
[Nexus 7 General] kenhicg:
Thanks. Mine is blown as well and I will need to call support.
[Nexus 7 General] demandarin:
Update: well I just got off the phone with them. They are going to send me a replacement unit. I have to wait for an email with link to kind of order the replacement one. What happens is you click that link and order replacement. Then its sent off with advance 2 day shipping. You will have a temporary hold placed on account for the amount of particular unit you have. Itll never go through. New unit will be shipped to you with return label and everything. Once you get new unit, you have 21 days to send back defective unit. If they don't receive defective unit within that timeframe, then your account will be charged. As soon as they recieve defective unit back, the hold disappears on account.

I asked the girl about serial numbers, latest batches, and how it correlates to screen lift issues. She said THST wasn't true..lol she said there were no bad batches, per se. Mostly just coincidence that those units had lift issue. She said serial number shouldn't really matter. Well I said I still want a latest model one as mines is a C6 batch. I purchased back in June.

Now my only question is, do I need to worry about putting this device to a locked and unrooted state or not. I'm currently unlocked, rooted, running stock rom and motley kernel. Or I DONT have to worry about THST and send off as is? Of course factory reset at least. Anyone send their unit back still unlocked and rooted and had no issue?
[Nexus 7 General] contradude:
I just hit it with the nexus 7 toolkit. My current nexus 7 would be perfect except for the blown speakers. Needless to say, RMA #2 is on the way.
[Nexus 7 General] demandarin:
You mean you used toolkit to lock it back up and return to stock? Which kit emxactly? I have a few installed actually..lol. I also just saw that wug fresh has a new version. That supposedly has all files included to revert back to stock and relock.
[Nexus 7 General] 145ty:
Screen lift isn't fixed on the newer units, probably be hit or miss. I have very minor screen lift on my C8 unit (doesn't bother me, nor does it move when pushed - so I am leaving it be as everything else is working fine). Seen few other people report screen lift with C8 units as well.
[Nexus 7 General] Harry GT-S5830:
The 'screen not responsive' when I'm touching the screen as I turn it on
[Nexus 7 General] demandarin:
If it has slight screen lift, that'll be OK for me. But I just want a new unit with fresh set of speakers. I can't let the distorted/blown sound quality slide.
[Nexus 7 General] xerox89:
Actually nexus 7 have more than a million pixel .

i don think you can esily notice 1 dead pixel .
[Nexus 7 General] dirtyhamster73:
Not even with a dead pixel test?
[Nexus 7 General] randroid123:
I think someone here has already mentioned this, but after examining a few solid more recently manufactured N7s... The issue isn't only the raised left side of the screen but also the recessed right side... All the solid units I've seen have the screen flush with the bezels edge while all the units with raised left sides I've seen also have a recessed right side... I think there is more to it than tinkering with the left side of the device to fix
[Verizon Samsung Galaxy S III] Lembro:
thanky you to anyone ahead of time for reading this post. I really could use some help.

I have a Verizon galaxy s3 which I rooted 3 weeks ago when i got it. I know it was rooted as i had super user permissions, and deleted many bloatware apps. I waited until cm10 came out to flash a new rom and after doing so last night my phone now boots up with this message "System software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."

So I tried to boot it in to recovery mode but when I did, the same message came up, only this time it said "recovery booting" in small blue writing in the top left corner.

I followed the directions to a T from a page entitled "Jelly Bean for Verizon Galaxy S3: Unofficial CyanogenMod 10 (CM10) Nightlies Available for Flashing!

From what I understand, the bootloader was somehow never unlocked by kexec. because I cant get in to recovery mode, I was wondering if there was a way to disable the bootlock by installing kexec via odin.

Also, whether it was a good idea or not, I re flashed the stock rom via oden last, which was successful but, nothing has changed still the same response all boot ups. Download boot obviously works though as I have been able to mess with it in odin.

any insight on this would be graciously appreciated.
[Verizon Samsung Galaxy S III] Watanuki-Kun:
Okay, first, If you did follow the directions for that thread, i'm sure it would of worked, I'm pretty sure you are missing something here and i'm pretty sure from reading your post that I think you didn't unlock your bootloader. kexec was a workaround for the locked bootloader, it doesn't unlock it. I would follow droidstyle's guide to unlocking the bootloader, http://xdaforums.com/showpost.php?p=28530409&postcount=2 after you unlocked it, i'm pretty sure you forgot that step. But the issue when flashing back to stock via odin and still showing up its a custom rom, I don't know why that would happen but I suggest reading section 2 of droidstyle's guide on flashing back to stock. http://xdaforums.com/showpost.php?p=28530394&postcount=1

So first, I suggest to return to stock, then root, then unlock bootloader, and then install the rom of your choice, preferably without kexec, if you don't want the triple reboot.
[Verizon Samsung Galaxy S III] droidstyle:
Agreed! Op, do more reading and less flashing before you end up with a 600.00 paperweight!
[Verizon Samsung Galaxy S III] arrogantS3:
Like he says above you have not unlocked your bootloader . Restore nandroid or recover to stock. Then unlock your bootloader and try again
[Verizon Samsung Galaxy S III] MDMoore313:
Get rid of the Verizon screen of death

I got the same error msg after flashing a nightly of d2hacker's unofficial cm10, after I had flashed a few nightly's before of the same ROM w/ no problems. I had to

1. Flash a stock bloated unrooted ROM via odin (lemme know if you need a link to one)

2.boot into droid recovery and do a factory reset, and wipe the cache partition also.

If you don't do step 2 you end up w/ a permanent verizon 4G LTE rainbow boot screen :silly:

I haven't re-rooted yet but I'll be trying the official cm10 now that it's up.
[Verizon Samsung Galaxy S III] droidstyle:
Refer to my last post :p
[Verizon Samsung Galaxy S III] MDMoore313:
Note that even when I flashed back to stock, my initial boot screen still had the unlocked lock, w/ "Custom" under it, suggesting my bootloader is unlocked:cool:
[Verizon Samsung Galaxy S III] Zalithian:
Incorrect. It actually means the opposite. The only way to tell if your bootloader is unlocked is to flash a custom rom/kernel and boot up. Please people, do some reading before you turn your phone into a paperweight. That unlocked lock/custom means you're running or were running custom software and it's been detected as such. One possible culprit is your "custom" recovery. If your bootloader is unlocked, you will not have that problem.
[Verizon Samsung Galaxy S III] droidstyle:
refer to post #3 and read this link :p

http://xdaforums.com/showpost.php?p=30479625&postcount=13
[Verizon Samsung Galaxy S III] MDMoore313:
Thanks for clearing that up, Where did you find this info? I'm coming from a Droid incredible, so I never had to worry about such things....

EDIT: I just saw Droidstyle's post @ http://xdaforums.com/showpost.php?p=30479625&postcount=13, makes a little sense, but why all of a sudden Verizon's screen of death is odd, if it was already detecting custom s/w to begin with. I used kexec also as a workaround, but this was back when there was no way to unlock the gs3 bootloader.

Yeah absolutely I follow the steps here http://xdaforums.com/showpost.php?p=28530394&postcount=1
[Verizon Samsung Galaxy S III] Zalithian:
I think it has to do with the "degree" of customization. IE a custom ROM or Kernel will get you the verizon screen of death for sure if you're not unlocked. The custom/unlock icon seems more for minor things like a custom recovery, possibly different firmware or tweaking specific settings.
[Verizon Samsung Galaxy S III] MDMoore313:
That makes more sense, as the nightlys progress and more modifications are being made, overnight the "switch is flipped" so to speak, and if you're not running a custom rom, :eek:
[Verizon Samsung Galaxy S III] strung:
Could he Odin back to stock through download mode though? Or will the locked bootloader block download mode and recovery mode too when it detects tampering?
[Verizon Samsung Galaxy S III] droidstyle:
The secure aboot.img only checks 3 of the 5 system images on boot. Since we can flash a custom recovery to the recovery partition, the secure aboot img lets it ride, but knows it there....hence why you see the custom lock screen, but device still boots. Kexec allowed the bootloader aka secure aboot.img to see the stock kernel(boot.img) and pass signature checks, then side loads the custom kernel. Thats why there was 3 reboots...now that the bootloader is unlocked, we ditch kexec because unsecure aboot is unlocked and not checking signatures.

However, if you flash a kernel thats non kexec and the bootloader is locked, you will get the verizon screen of death since the secure aboot.img is checking signatures. So never lock the bootloader unless your on stock rom/kernel or using kexec.
[Verizon Samsung Galaxy S III] JScott65:
Deleted
[Verizon Samsung Galaxy S III] thekendog:
Jesus. All of these people who don't read up on things before they flash something astounds me.
[Verizon Samsung Galaxy S III] EvoSideHustlAZ:
Lol, the exact same thing happen to me as Op, I was unlock (ezrecovery app) and rooted(casual-revision131) but when I flash unofficial CM10 KANG I was lock out by Verizon message.Thanks to DroidStyle awesome GUIDE i just Odin back to stock along with kernel.Thank you to all the cool people here at xda who help and evolve Android:thumbup:

Ezrecovery app must not have work properly even tho it said unlock, so I use Adam casual R131 flash Unsecure Aboot too.
[Verizon Samsung Galaxy S III] Zalithian:
ezrecovery to unlock? What?
[Verizon Samsung Galaxy S III] tdperry:
No, that just means that it normally has detected some changed files. If you WERE unlocked you would never see that icon.

TAPPED in on my (now unlocked bootloader) Verizon S3
[Verizon Samsung Galaxy S III] MDMoore313:
Well, step 1 is going Odin back to stock, but if a cache wipe and factory reset aren't done (like in Droidstyle's guide), then it will never completely boot, at least that's what I experienced after my phone sat at that screen for 10+ minutes. It doesn't run the user setup again.
[Verizon Samsung Galaxy S III] MDMoore313:
Also good info for noobs http://xdaforums.com/showpost.php?p=30484397&postcount=4
[Verizon Samsung Galaxy S III] rocktonic:
link

having the same trouble... i could use a link actually, if you don't mind.
[Verizon Samsung Galaxy S III] droidstyle:
Link in sig has all the links you need.
[Verizon Samsung Galaxy S III] MDMoore313:
http://bit.ly/Pp1Kdb
[Verizon Samsung Galaxy S III] tu3218:
This makes me wonder, they say the only way you know if ezunlock app works is if your able to flash a custom kernel. Well you had to find out the hard way it didn't work. Are they any new ways to determine if it truly unlocked the bootloader?
[Verizon Samsung Galaxy S III] droidstyle:
People here keep referring to my guide...well read it and your question will be answered.

Quote from my guide: "*How to tell if your bootloader is unlocked- The boot sequence should be as follows: Samung logo, Galaxy S III logo, Boot animation...If you get a "Custom Unlock" screen inbetween Samsung & Galaxy SIII screen, then your bootloader is NOT unlocked!"
[Verizon Samsung Galaxy S III] rocktonic:
odin hanging when installing kernel

first of all, awesome guide. thanks from me and everyone else that i'm sure has found it useful.

buuuut, after i flash the rom, which seems to work fine, and i start to flash the kernel, ODIN hangs at "SetupConnection". i've been waiting for it to proceed for about ten minutes now, this being my second try. any thoughts?

UPDATE: after another minute of patience, it says:

Complete(write) operation failed

All thread completed. (succeed 0 / failed 1)

not the result i was hoping for...

decided to proceed with the rest of the guide, hoping a rewrite of the kernel wasn't necessary to fix my problem. appears it wasn't, phone is starting normally and the stock android recovery is back on!

thanks again for the help, much appreciated!
[Verizon Samsung Galaxy S III] lazarus2405:
What do you mean, "seems to work fine"? Did the flash complete, and did you reboot? If you just flashed the stock image through ODIN, and you can boot fine, move on and don't worry about flashing a stock kernel through ODIN.

Use ODIN to root if you're using the root66 method.

Use recovery to make backups, install roms, install custom kernels, and restore backups you previously made.

Use ODIN to flash modems.

Use ODIN to return to stock if you can't fix your problem through recovery.

ODIN should be viewed as a last resort, and recovery as the go-to troubleshooting tool. Make a backup before you do anything risky, restore it if something goes wrong. Always make a ****ing backup.
[Verizon Samsung Galaxy S III] tu3218:
My bootloader is NOT unlocked, just rooted w/ CWM and I don't have any custom unlock screen. So that would exemplify a unlocked bootloader based on my sequece, but I've never done it.
[Verizon Samsung Galaxy S III] rocktonic:
yeah i'm usually pretty good about making backups, this was the first time i've ever not been able to just boot into recovery and scratch everything i did though. i just flashed CM10 nightly and am waiting for it to boot. it's been on the boot animation for some time now. pretty cool and all but i've seen enough! hopefully it works

and yes the flash completed, it said 'reset' at the top of odin. then i loaded the kernel into odin, which failed to push to the phone. pulled the battery, rebooted, and it booted to the factory rom, interestingly with all my mods/apps still loaded (i thought they would go with the new rom i was pushing over). i then used your guide to re-root, unlock bootloader, flash CWM recovery, now working on CM10.
[Verizon Samsung Galaxy S III] lazarus2405:
Not my guide, it's droidstyle's guide. There's more than one person helping you. :highfive:
[Verizon Samsung Galaxy S III] Knox76544:
What if I cant get ODIN to send the factory unrooted rom. I have tried a bunch of different ones. All for verizon but it fails every time.. Please help!!!
[Verizon Samsung Galaxy S III] fr8cture:
The only option is to get into download mode and flash the stock rom otherwise i say your gonna need a replacment.
[Verizon Samsung Galaxy S III] Knox76544:
I'm in download mode but ODIN wont send the file. It will start feeding info then get stuck on setting up connection and fail.
[Verizon Samsung Galaxy S III] daveyp225:
use a rear usb port (srs)
[Verizon Samsung Galaxy S III] MDMoore313:
Are you getting an error message? Post it here if so.
[Verizon Samsung Galaxy S III] elight7286:
galaxy S III locked by verizon

PLEASE HELP?

I can only enter download mode. BOOT wont work, besides download mode the only thing I can see is the infamous verizon message.
[Galaxy S II Q&A, Help & Troubleshooting] Hxcftw:
I have an interesting problem that hopefully someone can help with. For the majority of my music the songs will be displayed in alphabetical order as opposed to the embedded tag data. I've used Mptag software to check and resave the tags but that didn't work. I've noticed that .m4a files are displayed correctly but not Mp3 files.

I've tried clearing the app data/cache and I've even installed the SGS3 music over the top to test but that did the same. Music app downloaded from the app store however do display everything correctly. While I was on older firmwares the stock app was fine also.

I really like the stock music player so I don't really want to use a different one.

Any suggestions would be greatly appreciated!

I'm on rooted stock firmware DXLP9.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] fini13:
can anyone make a tutorial about how to install cwm with SE Extreme Tweak Installer v1.8

it says su:perimission denied
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
On which firmware are you? 4.0.2.A.0.62?

Is your device rooted? Because permission denied meens, that you have no root.

If you want to install clockworkmod on lww, check this out. It will automaticly install cwm, but I don't know if it works on locked bootloader...

For SE Tweak installer you could check this out. It's a tutorial :)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] fini13:
how to root it then?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
On which firmware version are you? 4.0.2.A.0.62?

Check out this here :)

But go to settings -> about phone -> build number and tell which version please!