Can I use the stock recovery OS for Software Upgrade 3.3.0 on the shield 2017? I wan't to use this to keep the HDHomeRun App to still work with DRM Channels.
I've asked the same question on another board and haven't got an answer. I also had a chat with Nvidia and the guy kept asking why I wanted to do that. I just asked is the 3.3 firmware compatible. He didn't give me an answer.
im kinda wondering what would happen if i did it? i have a 2017 shield but i dont feel like bricking it today lol
Did you brick yours? I oem unlocked and mine doesn't boot anymore. I do see it in windows as APX in device manager.
You'll probably brick your device. I say this because I highly doubt the new shield shares the exact same hardware as the old. It may be running X1 just like the old shield but the Bluetooth wifi ram internal storage etc are most likely different.
any1 get adb to work on 2017 model?
adb works fine, make sure you have a male to male usb cable, and enable it under the storage setting menu, should be called usb transfer or something.
My guy at NVidia said, "I wouldn't recommend doing that."
He was interested in more information - so I passed along the OP.
My Nvidia guy asked:
Can you find out what version of HDHomeRun app he is using? Is the app the green or grey version?
Green
i can get adb to work re reboot/push/pull but cant get any shell commands to work, all return errors, is there anything i can do
Related
Hello XDA Members,
first I dont know if im in the right place, but if im not, dont hasitate to move this thread.
Story: I tried to root my Pearl Touchlet XA100 tablet (running Android 4.4.2), but i failed. At this point, it was working. Some time later i wanted to know if it has a fastboot mode were i could boot into, so I typed via adb "adb reboot bootloader", the device rebooted but the device is stuck in the kernel splash image (the image that gets displayed before the bootanimation appears). Its even stuck there when i plug in the charger (it has its own charger port, i dont know i it displayed ever this offline charging animation over usb).
While Im thinking about RMA (with luck they swap/repair it) i cant get it out of my head so i was watching the devices source code, where i found under 0709_4.4/android/hardware/qcom the folders "msm8x74" and "msm8960", the folder msm8960 where in my mind they i looked for it, and its the qualcomm S4 Plus cpu.
Now my Idea/question is that i can compile the source code and flash it... But is there any way for me flashing it if i cant do anything with it? While my PC still detect it as "Samsung Android Phone" i cant use adb, and the device has only a "Back" and a "Power" button on the side, pressing both at the same time to boot into recovery (its the only way i imagine to enter a recovery/bootloader on this device aside from adb...bootloader worked "well").
I dont know much about Android source development, but atleast i know how to flash roms/kernels via recovery and Samsung phones via odin, but maybe with a little help with you it will be enough to revive the tab from the dead.
The device has a 1,5GHz dual CPU, usb 2.0 with OTG support, Android 4.4.2, 2 hardwarebuttons ("Back" and "Power"), a seperate charger port, wifi, a 10.1 zoll touchscreen, 4,5gb internal storage (only /system and /data, no emulated internal sd), the microSD slot supports up to 32gb microSD card. Device at pearl (german cheap-things site: http://www.pearl.de/a-PX8838-1000.shtml Link to the source code of the device: (Sorry, actually i cant upload them on github, its official pearl download) http://www.pearl.de/support/product.jsp?pdid=PX8838&catid=1000&nodocs=1
Call my stupid, frankenstein or so but i cant get it out of my head and i want to repair it, first for fun at the challange and 2nd for saving time waiting on the answer of the support.
Hopefully you understand my personal reasons, the post itself and have the knowhow/right tips to help me
How to root Touchlet XA100?
Hi adi2500,
Unfortunately I do not have the answer for your post, I am new to the Android world.
I would like to know though how you rooted the Touchlet XA100. I have the same tablet and I am a bit lost with all these tools I can find on the internet, none of them seem compatible with Touchlet tablets... Information about tTouchlet tablets is very hard to find...
Which tool did you use? Before you tried the fastboot mode, did you say that your tablet was rooted and working?
Thanks in advance for your answer !
Nothing i tried rooted the device. I actually have 2 superuser apks in /system/app, supersu installed and still i cant install the su binary. Actually i got it running again bx fully discharge the battery, but what makes me wondering is the fact that the battery wasnt connected to the mainboard and the devicr still didnt Boot.
Well, my last Option is building CM11 for it, but i dont know if i can run a modded kernel in it and even if i make it bugless, i dont know how to flash it.
One APP Form bluebox (forgott the Name) tells me, the towelroot bug isnt patched and maybe we have to mod towelroot or write our own APP, but actually im happy without root (better having a non root tab than no tablet). Maybe an Android pro could help us, since im at the end with my knowledge.
Hacker kibs at your service
Never heard of that device, but I can help you
Did u tried the kingo android root
The rooting software is only for supported or unsupported android devices
So I request u to try the kingo android root
This requires a computer to do it
Thanks
HK
Thanks for the advice, I will try Kingo Root
Kingo Root worked
Thanks for the advice KIBS2173 , Kingo Root was able to root my Pearl Touchlet XA100 without any issue I just had to install Universal Android USB Driver on my PC because Windows did not manage to find a driver for it via Windows Update.
I have been reading for many days and there is no way I can get into fastboot , to install new system ,no boot logo, not fastboot.
I have some other way to repair fastboot?
Is it possible to delete the fastboot?
If so, can it be rewritten?
thanks
Pro, or Standard?! I don't know what to tell you about the Standard though.
If it's the Pro we're talking about I would slow down FAST! And, have a look at the SSHD to SSD Migration Threads here first. Namely the bits on cloning it. Which might at first seem to be pointless. But let me explain.
Each Shield TV has a hidden Partition inside the SSHD that contains the valid Widevine L1 Keys. In short you will want these if you have plans to use either Amazon, Netflix or <Insert other heavy handed OTT Service here!>.
While you may have forked the Bootloader to a permabricking state. You could use the Op's Backup Image of his own Shield TV which he was generous enough to make public.
That however would way out your own Keys FOREVER! The practical upshot would be like an XBOX Live Permaban.
So heres the "Idea", you backup what's left of your SSHD Under normal circumstances you should never have need to touch the Security Sectors of the SSHD. Once you have made that Backup... Following the info from that Thread. Go ahead and install Ops backup Image to your Shield.
(Full disclosure) It's to late for me, so I can't tell you exactly which Partition you need or which DD command to enter, in order to flash back your personal Security Sector to your Device. I think I may have inquired about it in that Thread. But not having bothered to make a backup even at that point means I no longer have those Keys, even if I do have a working Shield TV. But as long as you can replace the correct Partition with the One that came with the Shield you should be able to recover.
Now outside of that advice. You really don't need to ask me anything further. Again I never managed to get that far. I was going on what turned out to be false information at the time that only Netflix would be affected, by a broken ESN. What the people in that Thread probably faild to realize was that it was the Widevine Keys that were to blame. So I thought ok fork Netflix! As long as I can use Amazon.
Needless to say: WRONG ANSWER!
But, if I were in your shoes now, the above would be my plan of attack. But, I'm not the One to be asking about how to do all of that. Besides most of the foreseeable questions should already be answered there.
if you cant boot into bootloader or fastboot mode, at least in 16gb, your screwed. Better request for RMA.
Sent from my Tapatalk Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ Full Android for ShieldTV and Nexus Player
Ichijoe said:
Pro, or Standard?! I don't know what to tell you about the Standard though.
If it's the Pro we're talking about I would slow down FAST! And, have a look at the SSHD to SSD Migration Threads here first. Namely the bits on cloning it. Which might at first seem to be pointless. But let me explain.
Each Shield TV has a hidden Partition inside the SSHD that contains the valid Widevine L1 Keys. In short you will want these if you have plans to use either Amazon, Netflix or <Insert other heavy handed OTT Service here!>.
While you may have forked the Bootloader to a permabricking state. You could use the Op's Backup Image of his own Shield TV which he was generous enough to make public.
That however would way out your own Keys FOREVER! The practical upshot would be like an XBOX Live Permaban.
So heres the "Idea", you backup what's left of your SSHD Under normal circumstances you should never have need to touch the Security Sectors of the SSHD. Once you have made that Backup... Following the info from that Thread. Go ahead and install Ops backup Image to your Shield.
(Full disclosure) It's to late for me, so I can't tell you exactly which Partition you need or which DD command to enter, in order to flash back your personal Security Sector to your Device. I think I may have inquired about it in that Thread. But not having bothered to make a backup even at that point means I no longer have those Keys, even if I do have a working Shield TV. But as long as you can replace the correct Partition with the One that came with the Shield you should be able to recover.
Now outside of that advice. You really don't need to ask me anything further. Again I never managed to get that far. I was going on what turned out to be false information at the time that only Netflix would be affected, by a broken ESN. What the people in that Thread probably faild to realize was that it was the Widevine Keys that were to blame. So I thought ok fork Netflix! As long as I can use Amazon.
Needless to say: WRONG ANSWER!
But, if I were in your shoes now, the above would be my plan of attack. But, I'm not the One to be asking about how to do all of that. Besides most of the foreseeable questions should already be answered there.
Click to expand...
Click to collapse
Many thanks for your reply, but I do not have the pro and I do not have a backup.
demondhume said:
Many thanks for your reply, but I do not have the pro and I do not have a backup.
Click to expand...
Click to collapse
If you have a "Standard" (i.e. The 16Gb), then it's pretty much the end of the Road for you. As there is no way outside of a nVIDIA Factory, that I'm aware of that would allow you to recover your Bootloader on an eMMC Chip. Without some very expensive equipment, and some very MAD SKILLZ. Apperently someone here managed to do that by upgrading the Chip to 32Gb's, from the usual 16. But, this is likely beyond the scope of most People.
It kinda sucks to say it, but I think it's time to start looking for a replacement.
demondhume said:
I have been reading for many days and there is no way I can get into fastboot , to install new system ,no boot logo, not fastboot.
I have some other way to repair fastboot?
Is it possible to delete the fastboot?
If so, can it be rewritten?
thanks
Click to expand...
Click to collapse
It is possible to delete the fastboot if you've performed this command
fastboot erase bootloader
If not, I suspect that you just can't deal with the hardware trick to enter the bootloader which it is tricky indeed
- with the TV box disconnect from the power cable
- Connect the hdmi both to TV and TV box
- connect the USB cable to both pc /laptop and TV box
- connect the power cable and on the next split second hold the power button of the TV box for few seconds, it should go to bootloader
From there, use the Nvidia TV box recovery image to flash it, there are instructions on website about how to which consists on a set of fastboot commands
Before starting be sure that the fastboot drivers are correctly installed and functional
Sent from my Darkside of Oneplus 3T
it is clear that OP's device is in that state because he already flashed something (wrongly) and nuked the bootloader.
If he already flashed something, it means he knows how to get into fastboot or bootloader mode, so that is not the issue. The issue is that OP bricked his device by flashing wrong bootloader, and if the bootloader gets corrupted in 16gb model you won't be able to boot into that mode, thus not able to flash anything anymore.
Best advice is to request for RMA.
Sent from my Tapatalk Hub
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee ~ Full Android for ShieldTV and Nexus Player
I fastboot flashed a system update and now the only way i can get into the bootloader is via adb, then once i am in I cannot interact with it on screen.
Any thoughts on this?
2me3 said:
I fastboot flashed a system update and now the only way i can get into the bootloader is via adb, then once i am in I cannot interact with it on screen.
Any thoughts on this?
Click to expand...
Click to collapse
Are you sure that the Controller/Keyboard is plugged into the USB port next to the HDMI port?
!1
ACiDxCHRiST said:
Are you sure that the Controller/Keyboard is plugged into the USB port next to the HDMI port?
Click to expand...
Click to collapse
yes. this was on my first stv which i ended up bricking. I have 4 of the OG shield tablets which are much more durable in terms of software mods.
In my research I found someone on youtube with a process to downgrade the bootloader, in his tutorial he states clearly that you will no longer be able to interact with the bootloader via controller/keyboard and must use ADB to reach it (exactly where I was)
I believe i got there being trigger happy flashing DTB files, from what i've read (also elsewhere on the internet) the DTB file is the most dangerous thing to flash to the STV and in many cases is not necessary (moving between small updates)
It would seem its better to flash an update without the DTB first and have to re do it than flash it as the flashboot script provided by nvidia states.
Regardless I am disappointed there seems to be such little development on this great little machine, especially compared to the shield tablet. We barely even have a custom rom and the thing ships with an unlock-able bootloader!
Wait I to have lost control of bootloader in my Nivida Shield tv 2017 version after the 7.2.2 update I put in the keyboard and i can select anything in the bootloader. Im not sure if the controller works b/c at first it didnt I had to update the controller as well for it to recognize the controller again. Anyone also having usb driver issues. I'm on windows 7 still so that could be the reason I'm having issues finding these new tegra drivers and the ones from 2018 dont work?
As title. I have just purchased a 2017 Shield TV, and it came rooted with Pie 9.0. Now, I don't really care for that at all. I mostly just use Plex with my devices, and that's why I bought this. Save me turning on my Xbox One X just to watch a movie, ha ha. I don't really want an extra "warning" screen when I boot it up, and would prefer it to simply just work from the remote (I may consider selling on the controller as I have multiple xbox / PS4 / Switch / 8bitdo controllers if required).
Anyway, as it has full Android on there, rather than the original Shield OS, do I loose anything with respect to the Plex app (which is my most used app), or Amazon Prime Video? Are there any other media limitations that I may experience from running a rooted system?
I am relatively happy with flashing firmwares and such (I regularly play about with CFW on my Switches and Vitas). So is there a guide anywhere that will show me how to put this shield back to stock? Rooted or otherwise.
if you want to flash the device back to stock go here
https://developer.nvidia.com/gameworksdownload
make sure you read everything about how to do it first and make sure you download the correct rom image for the correct device otherwise you will brick the device.
i have the 2017 16gb model with the developer rom (stock rom with root capability). i rooted mine with magisk but really i don't see any reason to really root it other than adblocking. i use mine mainly for plex and iptv. i do use atv laucher pro. i don't like the stock home screen setup. also i can download just about any app from https://www.apkmirror.com/ put the apk on a usb stick and load it with es file manager or even the stock file manager software.
rchris494 said:
if you want to flash the device back to stock go here
https://developer.nvidia.com/gameworksdownload
make sure you read everything about how to do it first and make sure you download the correct rom image for the correct device otherwise you will brick the device.
i have the 2017 16gb model with the developer rom (stock rom with root capability). i rooted mine with magisk but really i don't see any reason to really root it other than adblocking. i use mine mainly for plex and iptv. i do use atv laucher pro. i don't like the stock home screen setup. also i can download just about any app from https://www.apkmirror.com/ put the apk on a usb stick and load it with es file manager or even the stock file manager software.
Click to expand...
Click to collapse
Thanks for the help. I got there in the end. Had a panic when it refused to boot, and couldn't get into fastboot to try a factory reset, but plugging my keyboard in, rather than the controller, and locking the bootloader helped that.
Now back on stock and got it all set up and running. As expected, Plex is MILES better than on my Xbox One X...
Hello , i have a problem which occured from one day to another.My Shield TV was not booting. I tried to go to recvery and do Wipe and reset and it didn't let me.Then I tried with different recoveries from Nvidia , and still no luck.I went i tried it with this https://nvidia.custhelp.com/app/ans...hen-you-are-unable-to-access-android-settings I only got errors Failed to mount... failed to format I/O Error ... also mke2fs returned 1 .....failed to clear BCB message and so on when i start i see the nvidia logo and after a minute the android logo flashing slowly, but after that nothing more. Is my device storage dead???
Did you ever manage to fix the device? I got EXACTLY the same errors on my 2017 shield pro.
Unfortunately not. I ordered a new SanDisc memory and soldered it, but it didn't work. i Also found this site
Unbricking SHIELD TV (2015) with a Bootrom Exploit
Last year, a friend gave me his SHIELD TV when he moved. He worked at NVIDIA and got it for free and had used it only a handful of times before it traveled from his closet to my own. I had forgotten about it until I had a need for a Raspberry Pi and discovered that they were all still sold out...
yifan.lu
and talked to the guy about my atempt.He told me that the Storage chip is somehow bound, and I should try to dump something from the old chip to the new one. I can solder but dumping was to high for me.
You can check his site and try his method described there. I also asked him about which pin has to be grounded and here is a clearer picture than on his site. Good Luck !
Okay if you see APX that’s good because you can use the recovery tools worst case. However, if you have access to your old emmc still, you can dump it and copy it to the new emmc. Also know that the emmc contains per-device unique identifiers that are required if you use Netflix or any drm. If you flash someone’s else’s backup, they wont work.
If all else fails, you need to use the brom exploit and APX to run the recovery cboot and manually flash a backup that way. Not sure if that’s easier or harder than flashing the emmc externally.
Click to expand...
Click to collapse
Thanks for the reply! As fascinating as the linked article is, this is way beyound me. Also, thinkgs will probebly not be 100% the same as I have the 2017 model.