Hello I bought an Nvidia Shield LTE and had Bliss Rom in it, I restored to the original (factory image) and everything seemed to go ok. after reboot I set the wifi and said that there was an update, it rebooted but after flashing the android bot with the progress bar everything went black. I have not been able to power it on or get into recovery mode, if I plug it to the pc it make a different plug in sound. but I have not been able to figure it out, please help.
Hi,
did you buy a "pyrotab" (a recalled tablet because of a Y01 battery) knowing what it was? Did the seller mentioned this?
Yours had Blissrom on it, the tablet could not download and execute the TegraOTA.zip executable that kills the tablet as soon as the replacement is activated. But since you restored the tablet using the official Nvidia Shield rom and did not flash the nomoreota zip file in TRWP *BEFORE* rebooting, the tablet downloaded the ST - YY kill update and your tablet is now a paper weight. And no there's no way to restore it, search the forums for confirmation.
I know this because I bought myself a pyrotab knowing what it was and read many times the instructions on how to prevent it to be killed. It had a crappy rom on it so I flashed the official one but made sure to run the nomoreota.zip and supersu in TRWP before rebooting to make sure it did not have the dreaded files and my tablet is still working perfect so far. (Gotta check that battery though!!)
Sorry for your loss!
Related
After months of Samsung not fixing the known issue, I got mine working again today. Here is what I did, hope any with same problem have similar results. I am not an expert or anything, just finally found a way to get my tablet working again.
I downloaded the Kies program from Samsung website to my pc. I went ahead and used the "Lite" version. Once it recognized my tablet, I had it check for updates. I went ahead and installed the update and the progress screen stalled again and then the tablet rebooted again and still had the same problem not powering off.
So here is what I did different this time after the failed update attempt and it worked!!!!!
I went ahead and force closed the Kies program which was still trying to run with ctrl alt del. I then unplugged the tablet from the computer usb and then plugged it back in.
I restarted Kies Lite and it told me the last attempt failed and if I wanted to use recovery method, so I clicked yes.
It then gave some steps to do to get the process started but they were WRONG! Instead , I disconnected the usb cord, then pressed both the power button and the volume up key for about 15 seconds until the tablet rebooted itself into recovery mode. This booted into a recovery screen which gave a warning about loading custom ROM or something but I went ahead and proceeded anyhow by following the on screen instruction.
I then reconnected the usb cord and then the button to get started was highlighted and able to be clicked, so I clicked start.
And to my surprise it actually finally started updating instead of just sitting there hung up.
I let it continue installing and when the tablet rebooted, I disconnected the usb cord and the tablet was on its way to finish updating and installing the 4.2.2 working update with a power button that finally worked again.
This was my experience I wanted to share with others that are as frustrated as I was, just dont blame me if it doesnt work haha.
Update: I was able to successfully fix my inlaws tablet as well this evening with absolutely no issue. He has read about it and also tried various methods posted everywhere but mine was the only way that worked.
Only download you need is the Samsung Kies program, no need looking for outdated links, unzipping, Odin recovery options, etc. This is to get it back to stock Samsung ROM which currently is the 4.2.2.
Please post up your results if you try it and have a minute, Im curious how many others this works for after spending so much time reading, searching and testing diferent methods.
I have the shield tablet LTE version and after connecting to WIFI it immediately installed all OTAs upto the hotfix also. So here I am sitting with lollipop in my tablet and I decide to go for rooting and CWM installation.. After rooting using adb/fastboot and installing CWM image, I decide to disable ATTall access because I read that it stops the portable hotspot from working. So, did that and then process after process started crashing. First it started with background data not being enabled (playstore wouldn't open) , NVidia hub crashing, google text to speech crashing, etc.
So, I went to cwm and did factory reset. At the initial stages itself where it asks for language setup, the google text to speexh crashes and I cannot click next or proceed forward.
I flash the Lollipop OTA once again thinking it would overwrite the system but it didn't.. and the same issue keeps happening..
Now what do I do?
Regards
Alden
An update to the mess i was in...
I tried recovery mode at the fastloader boot menu and I got the robot lying down with a red exclamation mark sign. I pressed vol + key and it opened the original recovery I think. I wiped user data from this menu and rebooted. and now it has come to the original screen setup and so far no process crashes...
What could have caused this entire mess?
I am not sure what would cause your issues but i believe your best bet is to download the full rom image for your tablet and flash it via fastboot. That should get you back up and running. (Be warned doing this will erase everything on your tablet!! SD card will be untouched)
By fullmrom u mean the one from the nvidia developer website right?
Yes that is the one! I am currently at work so I cant post a link to it but if you need it ill try to post it once im off, in about 30-ish minutes. Good luck! (p.s. last resort is RMA)
Is your shield up and running once again? Just wanted to get an update. =]
Thanks javydawg, I didnt use the one on nvidias developer website as i simply did not have enough data left in my Internet plan .. its 2.3 gb in size... after recoVery i was left with lollipop so i flashed a 750 mb file tht i gt from these forums and updated it to the latest version.. i still haven't pinpointed the reason for my earlier trouble but will shout out if it happens again... have to be careful cos not sure if RMA is possible for me in India...
One day, I got tired of the lame and boring Kindle interface, so I decided to use CyanogenMod to fix that problem. The Kindle Model I had was the 2012 HD Kindle "Soho" model, the one they had a warning on not to mod. So I previously rooted my tablet, and after unknowingly installing the wrong TWRP version, I got Recovery Reboot from the Google Play .apk I got. The first time I used the app, it gave me a red triangle saying I should reset to factory default or reboot. Each time I rebooted got the same triangle, but factory resetting fixed that problem. I logged my Amazon account back in and got all my apps back, then re-rooted and got the Google Play .apk from before. I saw the warning about the Soho models after going back to the CyanogenMod wiki to see what I did wrong, and I gave up and stayed with the boring interface. BUT, my Kindle ran out of battery, and it automatically shut down, and when I charged it, it rebooted into the familiar red triangle. I rebooted again a couple times, didn't work, factory reset didn't work either, and leaving it on for a few hours to completely drain the battery didn't work. I think the TWRP files were still hidden in the system files after I reset it the first time, and rebooting with charging the tablet activated the reboot into recovery, which triggered the TWRP files into action, but it was the wrong version, leading to this brick. How do you fix this? Do I need a fast boot cable?
Hi! So, my father's old Samsung Galaxy Tab 2 10.1 P5110 (bought 5 years ago) has gotten into a bootloop. It's an odd case. Basically, it's like the device is completely read-only.
To describe the symptoms:
It boots into the OS, but after 30 seconds or so it suddenly restarts. The device cannot be turned off (it just reboots and reboots and reboots...), so it empties the battery if left unplugged.
I can enter download mode and recovery mode, where the device is stable.
The device is not rooted.
I tried to flash it with TWRP recovery (it worked on my mother's tablet; exact same model, but no problem like this), but the recovery mode is always unchanged. I've flashed with Odin 1.8*, Odin 3.0*, and latest Heimdall; it always completes, but nothing changes. I've learned about having to boot to recovery after flashing due to a script replacing custom recovery, but even when I go directly to recovery mode, it's the same old stock recovery.
I decided to try another approach, by uninstalling apps during those short 30 second intervals of functioning OS; I got to uninstall one app (AVG anti-virus software), but after the reboot, the app was installed again.
I tried to go into recovery mode to do "wipe data/factory reset" and "wipe cache partition", but even that did nothing! Everything is where it was.
I can use ADB in recovery mode, so I tried to see if I could do some damage there, but the tablet is unrooted, and no rooting works either. (Tried rooting with Odin and "apply update from external storage" in stock recovery.) Couldn't find a writable directory to upload a su executable into either.
Just now I finished a 90 minute flashing of some Chilean stock firmware -- although I'm Swedish -- to see if that made things "rewritable", but guess what? All the old apps and files and settings were still there, in Swedish.
At this point I'm starting to suspect that I could hit it with a sledgehammer and it would just return to normal after a minute.
My father is not poor (just a bit cheap!), so buying a new tablet isn't a big deal, but I'm ostensibly a computer engineer...ing student, so it feels like a surrender to leave it unsolved. What might be the problem? Can memory in these devices become read-only due to some hardware fault?
Risky suggestions are welcome. If it's bricked, that's no problem.
EDIT: Whoops! My father ordered a new tablet; I was still going to experiment on the old one, maybe get it working again, but it seems that he went and tried the sledgehammer mode on it. But what happened is still an open question.
When I got my replacement tablet for the recall, I followed the instructions to kill the kill switch on my old tablet (a 16gb Wifi only version). I deleted the TegraOTA folder, and used the zip file as well. I then installed BlissPop and have left it that way since.
A few days ago, I decided to switch from the now-defunct BlissPop over to LineageOS. For some reason, I couldn't get the tablet to boot into recovery (I installed the TWRP app, wouldn't boot into TWRP; I flashed TWRP using fastboot, wouldn't boot into TWRP; I flashed Nvidia's stock recovery, still wouldn't boot into recovery).
So I decided to flash stock, but new everything (I think the 5.2 or 5.3 version). Booted into OS setup (without connecting to network) so I could enable debugging/connect with ADB. This worked, so I rebooted into bootloader and finally got into TWRP. But, because of shared storage, I couldn't get into system folder to see if TegraOTA was back. So I decided to go back to original stock so I could access internal storage. Performed a factory reset, flashed the very original stock system/recovery/boot from these forums.
Restarted tablet and... nothing. Black screen. When its plugged in, the light shows it has charging, but no amount of time or effort pressing the power button will get it to do anything.
Did I brick it somehow? I've flashed various upgrades, OTAs, custom ROMs on both Shield Tablets I've had and am 99.99% sure that I didn't do anything wrong this time. Did I unknowingly flash something that would allow the kill switch to be thrown even if the tablet was never connected to my network? Is there any way to test? Basically I want to be certain its 100% done for before I toss it and buy a new tablet (I sold my replacement earlier this week, which is why I decided to upgrade the old one in the first place). Thanks in advance for any help!
If you installed latest stock and system detected tablet with bad battery it probably killed itself even if you did not connected it to internet