Recover the Y01 battery SHIELD Tablet (old) after booting the B01 battery one (new)
- Thread starter Victorcangil 16
- Start date
You can see it here, in my Twitter
https://twitter.com/victorcangil16/status/642389331768942592
https://twitter.com/victorcangil16/status/642389331768942592
I used Windows 10 with the NVIDIA Family USB Drivers. I made the process I described in the first post
Ok,
Thx for your reply Victorcangil 16.
But how did your device was recognized by windows before done this process ? APX or something else
It was reconized as normal device by Windows, like if I plug my phone to the PC. And the drivers I had to configure them manually, if not, It gives me error when doing FastBoot
It stay on :"<waiting for device>"
And my tablet is not reconized as normal device but as "APX"
Last edited:
Change the ADB drivers interface using the next process:
Search in Windows: Device Manager
If the ADB interface has a Yellow alert, Right Click, Update Drivers, Select from Computer, Use Disk, Use all, and then select the file in the NVIDIA Drivers folder (in my case, Downloads). Accept,
Search in Windows: Device Manager
If the ADB interface has a Yellow alert, Right Click, Update Drivers, Select from Computer, Use Disk, Use all, and then select the file in the NVIDIA Drivers folder (in my case, Downloads). Accept,
I don't known. My tablet appears like that in the peripherics manager ...
Yes i have skype.
But i think i got the problem : my tablet wasn't rooted and the bootloader was locked...
I think you saved your shield because it was rooted...
I thinks is that. If is has not unlocked bootloader, you can't change nothing. But to unlock it, just type in Fastboot: "fastboot oem unlock" (tablet will Factory Reset)
Similar threads
- Locked
- Sticky
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
1033IMEI (International Mobile station Equipment Identity) is a unique code each mobile device has, similar to the MAC address of a network card. Changing this is most of the time not possible, being a hardware specific number. That would not help in this case, since nVidia identifies our Shield Tablets by serial number.
In bootloader mode, there is no concept of "being rooted". You can only be rooted while running an OS (Like Android, Windows, Linux, etc) and means having access to the master Administration account. The bootloader is similar to a computer BIOS. Since Nvidia messed that up with the killswitch, having root or unlocked bootloader has no point.
The only action is, with the only access remaining, APX mode, to rewrite the nvflash with a valid bootloader and other first boot stuff (similar to rewriting the BIOS on a computer.... You mess that one up, computer is a paperweight). Trick is that only nVidia has the necessary packets to fix the nvflash.
So, Victor, you did not get your tablet killed by nVidia. Was something else that happened to your tablet. Having access to the bootloader means is still there.
I hope one day someone will find a way to fix this tablets (hack the APX access, leaked packages from nVidia) because is a big waste of perfect hardware.2You can see it here, in my Twitter
https://twitter.com/victorcangil16/status/6423893317689425922Indeed, 100% accurate!
Once the killer roms upgrade has been applied, the tablet is dead period. Unless an nvflash package surface this recall is indeed a waste of hardware! Nvflash is fairly common with older nvidia chipset but it's been less and less common with the recent SOC they released. The best is to remove the OTA before your tablet get killed.
The only question I still have about the recall process is the fact that the made us enter a code inside the recalled tablet, I suspect we unlocked something inside the recalled tablet so that the kill switch can kill the recalled tablet, I would not be surprised that the kill switch would not work on a regular tablet as you would need to enter the code to allow the kill to happen, however I am not yet ready to do a proof of concept test on this theory yet on my hardware
I would find strange that any tablet can be killed by urgent OTA, to me that would be opening a HUGE security hole ..
I had the same question, but the reason is simple (thanks to Bogdacutu again): the code that we had to enter is proof that we own the recalled tablet. Imagine we could enter someone else serial, from a friend, leaked on forums, etc. and get for free a new tablet, while those would be left hanging. Regarding to the killswitch, you are partially right: from the entered serial at the recall they pair the old and new tablets so when the new tablet connects for the first time to the OTA server, the old one will be sent that broken rom. Thing is, all receive the same 3.1 firmware... all have the urgent OTA option. If the new tablet received the killswitch, would run it in the same way. In the end is a firmware update like any other, only that is broken intentionally
I removed TegraOTA from my new tablet the moment I first powered it on. It did not have time to connect to the OTA server. I did the same on the old tablet as well. Thing is that 27 days have passed since I have both tablets on and according to Bogdacutu OTA check, no killswitch is waiting for my old tablet. So, is exactly as they said: activating the new tablet (more exactly, appearing on Nvidia OTA server) will kill the old one. If is not connecting, it is not killed (at least for now... maybe they will put all the list on death row one day).
Edit: It crossed my mind now.... If someone would check the new tablet serial also on Bogdacutu page, that might as well mark it active and release the killswitch for the old. Auci !
Sent from my SHIELD Tablet using XDA Free mobile app
New posts
-
-
Amazon Fire TV Stick 4K (E9L29Y) TWRP Unlock Issues/Help
- Latest: cityhunter_1919_xyz
