Shield Kill Switch

Search This thread

smiter

Senior Member
Jul 16, 2008
91
0
Dublin
just got mine replacement, with letter - Please dispose of your old device following local e-waste guidelines. so they dont want it back... its rooted and working fine!

pic:

 

Lachsmeister

New member
Aug 24, 2015
1
0
45
Eisinghausen
I did the same like Paul describes...according to the website the "kill switch command" has been triggered already but with this guide and the latest blisspop everything still looks fine...
the replacement unit asks for the OTA 3.1 update but as far as i understood this guide..not doing that rom update will prevent the shield from being able to recive the "kill switch command"

Many thanks for writing this guide
 

Frankenscript

Senior Member
May 29, 2014
932
165
Indianapolis Metro
Chill, folks. Just because they set our expectations for "2-4 weeks" doesn't mean that the world is ending if it's 4.5 weeks and you haven't received your tablet. Sure, they should ship within their stated timeframe, but it's not unusual for programs like this to take longer than expected.
It's not a good thing that it's going slowly, but for gosh sakes give them some slack and don't get so frustrated. They probably got more RMA applications than expected. Eventually they will catch up. IT's not worth a coronary over.

Pretty much everyone who reported getting their RMAed tablet is from the first day or two of the recall. I didn't fill mine out until almost midnight on Aug 3rd, and I haven't yet seen anyone post that they filled it out so "late" and already received their tablet (U.S.A., LTE version). So, I'm just chilling out and waiting patiently. If it gets to six weeks, that's when I'll complain to Nvidia.

Keep Calm
and
Carry a Fire Extinguisher

Marc
 

ady702

Senior Member
Aug 23, 2012
143
8
I got this email today.. (UK)


Dear NVIDIA tablet owner,

We apologize for the delay in sending your replacement SHIELD Tablet.

We are fulfilling claims as quickly as we can, in the order in which they were received. In some cases, we are running behind our target delivery of 2-4 weeks. We’re doing everything we can to accelerate the schedule.

We’ll notify you when your unit ships. In the meantime, should you have any questions, please contact us at [email protected].

Thanks for your patience.

NVIDIA

So could we end of September/ start of October!
 

MikaelSparks

New member
Aug 2, 2015
2
0
38
Same email in Canada. Was starting to get annoyed but at least they sent that update, so I know my rma isn't lost in the process. I'd say the email was a good call on nvidias part. Just as an FYI, gmail had stuck it in the promo folder. Didn't find it until I searched after reading others had gotten one.
 
got the email then a tracking the next day, Canada LTE unit. Not delivered yet as it's stuck at the fedex location awaiting for me...

Still haven't gotten the tracking email for mine. I'm in the USA. Hopefully they send it out soon. Can't wait to get it so I can flash KitKat AOSP on my old one and play the Chaos Rings games again. Never did finish the first one since it doesn't work on LP.
 

Frankenscript

Senior Member
May 29, 2014
932
165
Indianapolis Metro
If the tablet wasn't previously bootloader unlocked before it was killed, I believe it is completely impossible to recover it without Nvidia-prorietary tools. I believe there is some hope for folks that had bootloader-unlocked their devices prior to being killed. There are a few posts of people being able to interact with their tablets but only if the bootloader was unlocked.
 
  • Like
Reactions: GuyInDogSuit
If the tablet wasn't previously bootloader unlocked before it was killed, I believe it is completely impossible to recover it without Nvidia-prorietary tools. I believe there is some hope for folks that had bootloader-unlocked their devices prior to being killed. There are a few posts of people being able to interact with their tablets but only if the bootloader was unlocked.

Yeah, that seems to be the key. Otherwise you can't even use most fastboot/bootloader commands.
 

garrettcorn

Member
Dec 4, 2010
44
19
Some Small Town
Yeah, that seems to be the key. Otherwise you can't even use most fastboot/bootloader commands.

I can't seem to find that thread anymore.. Do you have a link to it? I'm not sure if I got the kill switch or what but my tablet internal memory is coming up as 0mb, but I can get into fastboot and recovery. This was on a stock, bootloader unlocked, custom recover, nomoreota.zip flashed tablet.

I was using the tablet as normal when it froze up, when I hard shut it down and restarted it internal memory was 0mb, so I'm looking for some kind of fix.


UPDATE: seems that everything is ok now.. Must have had something to do with encrypting my tablet recently (why the internal memory is showing up as 0mb). I flashed the boot.img from the 3.1 full ota and was able to boot into android.
 
Last edited:
I can't seem to find that thread anymore.. Do you have a link to it? I'm not sure if I got the kill switch or what but my tablet internal memory is coming up as 0mb, but I can get into fastboot and recovery. This was on a stock, bootloader unlocked, custom recover, nomoreota.zip flashed tablet.

I was using the tablet as normal when it froze up, when I hard shut it down and restarted it internal memory was 0mb, so I'm looking for some kind of fix.


UPDATE: seems that everything is ok now.. Must have had something to do with encrypting my tablet recently (why the internal memory is showing up as 0mb). I flashed the boot.img from the 3.1 full ota and was able to boot into android.
How'd you figure that out, flashing the boot.img?

Sent from my Nexus 6 using Tapatalk
 

garrettcorn

Member
Dec 4, 2010
44
19
Some Small Town
How'd you figure that out, flashing the boot.img?

Sent from my Nexus 6 using Tapatalk

Well I read here "boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted." which seemed to be my issue. I was stuck on the nvidia screen at boot,so it seemed to me that my tablet was having trouble mounting the filesystem.
 
Well I read here "boot.img contains the kernel and ramdisk, critical files necessary to load the device before the filesystem can be mounted." which seemed to be my issue. I was stuck on the nvidia screen at boot,so it seemed to me that my tablet was having trouble mounting the filesystem.

Good job. I think I would have been stuck for a lot longer, lol.
 

Top Liked Posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone