Recover the Y01 battery SHIELD Tablet (old) after booting the B01 battery one (new)
- Thread starter Victorcangil 16
- Start date
Helo and i would like to suggest, whether we can wake this sleeping beauty by replacing with equivalent batteries..? will it work for good..?
no, nVidia has a killswitch that they use to brick the old tablets by trashing the bootloader. there is a fairly large discussion about it but it comes down to if you use them and accept the OTAs then at some point after using the new tablet the old one gets bricked. that being said even if you do manage to get one working or kept it working I would replace the battery ASAP. as there is a reason why they are sending out replacement tablets....
Last edited:
thanks for ur reply...but still i came thro google ..tat initially they tried to replace the batteries befor the kill switch was implementec...but if we can wake the tab stil we can find some othr solution !!!???
Sent from my SHIELD Tablet using xda premium
Sent from my SHIELD Tablet using xda premium
Its any way how to flash bootloader on device when see only APX as devices
? or acess to partition memory and flash it like on http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 ? lg g2?
Code:
vid_0955&pid_7f40
Sess
Senior Member
someone please explain to me what root has to do with booting into the bootloader? We're pre kernel here, this whole thread sounds like a bad joke in poor taste.
So what this guy did was changed the registered IMEI so that it fools Nvidia and it won't send the KILL SWITCH and the tablet doesn't deactivates. Now my question here is; someone who never got KILL-SWITCH or got deactivated and switched to CUSTOM before it, has tried to do the process so that finally THE TABLET WILL RUN STOCK WILL ALSO RECEIVES OTAs AND Won't get deactivated. Anyone ?
That is not going to work. IMEI is a modem ID. What if I have the WiFi version ? That one has no IMEI.
The killswitch is sent by tablets Serial Number, and that one is not changeable. Even if it were, I would still remove TegraOTA.apk .
Sent from my old SHIELD Tablet.
MiFlash
I can confirm that (after disabling signature verification) one can install APX driver and MiFlash recognizes the tablet. You'll find the driver in \Xiaomi\Miphone\Nvidia\Driver after installing MiFlash
Which leads to a n00b question, is there such a thing as bootloader.img for Nvidia shield tablet ?
I can confirm that (after disabling signature verification) one can install APX driver and MiFlash recognizes the tablet. You'll find the driver in \Xiaomi\Miphone\Nvidia\Driver after installing MiFlash
Which leads to a n00b question, is there such a thing as bootloader.img for Nvidia shield tablet ?
hi frnd..tats a great try..i think the boot loader. img must be there within the recovery image provided on the nvidia developers web...i am also planning to do the same..;
Sent from my SHIELD Tablet using xda premium
Sent from my SHIELD Tablet using xda premium
s..so possibly if u can send me the link for Mi pad Image ..i wil try to download and retrive some bootloader files for testing
Fyi, the below readme txt is from nvidia Dev's Web, show's the existance of the Bootloader and blob file in the recovery image.
http://developer.download.nvidia.com/mobile/shield/ROM/ST8/3_1_1/HowTo-Flash-Recovery-Image.txt
> Have you already downloaded the factory image (2.1gb). If so can you check by unpacking the image ..?
Meahwhile I will also google for some possible extraction's from the existing shield.
Sent from my SM-N920G using xda premium
Fyi, the below readme txt is from nvidia Dev's Web, show's the existance of the Bootloader and blob file in the recovery image.
http://developer.download.nvidia.com/mobile/shield/ROM/ST8/3_1_1/HowTo-Flash-Recovery-Image.txt
> Have you already downloaded the factory image (2.1gb). If so can you check by unpacking the image ..?
Meahwhile I will also google for some possible extraction's from the existing shield.
Sent from my SM-N920G using xda premium
Last edited:
http://bigota.d.miui.com/V7.1.1.0.K...ICK_20151209.0000.6_4.4_global_f80229b3ed.tgz
It contains boot.img, not bootloader
An xposed module called *serial number changer*, just surfaced, it says it masks it from even the manufacturer, those who are gonna try it, proceed with caution cause you never know
http://forum.xda-developers.com/xposed/serial-changer-qa-t3345596
That's the forum link to it
http://forum.xda-developers.com/xposed/serial-changer-qa-t3345596
That's the forum link to it
hey my old shield was not deactivated because i does not conected it since i have my new one but i cant Change the imei...
how can i set up my old tablet so that it does not deactivated?
"oem writeimei" does not work... it Shows me Unknown command!
can i Flash an alternative Rom to stop the deactivated process?
(i have unlock it)
how can i set up my old tablet so that it does not deactivated?
"oem writeimei" does not work... it Shows me Unknown command!
can i Flash an alternative Rom to stop the deactivated process?
(i have unlock it)
Last edited:
Flash custom ROM or delete TegraOTA and use stock.
IMEI is not the ID for deactivation. Tablet's serial number is.
Sent from my old SHIELD Tablet.
Thats all?
my old tablet works definitely online without kill?
great^^ thanks
Can i use the new marshmallow Recovery Rom?
and how do i delete the TegraOTA.apk?
or do you know a good custom Rom instead?
Check this thread for more info: http://forum.xda-developers.com/showthread.php?p=62345155
And here you can find the MM updates: http://forum.xda-developers.com/showthread.php?p=65096689
I am just now typing from my old tablet without any problems, using official MM.
I never used a custom ROM before, so I don't know what's best.
Sent from my old SHIELD Tablet.
Last edited:
TO all the Pro out there, whose device is already in APX or dead already, I found this NVFlash but it's for Tegra Note 7, but commands are the same, see if Y'all and get hand dirty and share it with the community, Don't try to use this on working unless you know what it is, because I myself Have no idea, Proceed With caution
http://rootjunkysdl.com/files/?dir=Tegra Note 7
http://rootjunkysdl.com/files/?dir=Tegra Note 7
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
