I recently upgraded my Shield tablet to 5.1. Was running 5.0.1 (pretty sure). Rooted & no problems before the upgrade.
I downloaded the update from Nvidia (through another member's link in another discussion) & also got the newer SuperSU (from the same thread) & flashed those through TWRP. Rebooted & enjoyed the new OS & still had root. Easy-Peasy! But...here's the issue...
Each time I power down the tablet (say for the night) then power it on later, it boots fine for about 15 seconds, THEN...shows me that Android is upgrading & is optimizing the apps. This takes around 5 minutes for it to optimize then final boot to the home screen. Each-and-every-time I power down & start back up, it does this. It doesn't do it with a reboot, only a power down then a power up..either immediately or over night. doesn't matter how long it's powered off.
I could've sworn I unlocked the bootloader when I first upgraded & rooted, but I could be wrong. Could this be the issue, a still-locked bootloader even though I was rooted with another OS, then upgraded again to another OS & still have root? I did not wipe the Cache after I flashed the OS & the SuperSU, just rebooted through TWRP. Follow me there?
I'll leave this here for your ideas to tell me where I went wrong & how to fix this. It's frustrating to wait for 5 minutes until I can use my tablet, even though it works just fine (& a noticeably overall speed improvement too!) after it finishes optimizing the apps (again & again each time.
Ctrl_Alt_Del said:
I recently upgraded my Shield tablet to 5.1. Was running 5.0.1 (pretty sure). Rooted & no problems before the upgrade.
I downloaded the update from Nvidia (through another member's link in another discussion) & also got the newer SuperSU (from the same thread) & flashed those through TWRP. Rebooted & enjoyed the new OS & still had root. Easy-Peasy! But...here's the issue...
Each time I power down the tablet (say for the night) then power it on later, it boots fine for about 15 seconds, THEN...shows me that Android is upgrading & is optimizing the apps. This takes around 5 minutes for it to optimize then final boot to the home screen. Each-and-every-time I power down & start back up, it does this. It doesn't do it with a reboot, only a power down then a power up..either immediately or over night. doesn't matter how long it's powered off.
I could've sworn I unlocked the bootloader when I first upgraded & rooted, but I could be wrong. Could this be the issue, a still-locked bootloader even though I was rooted with another OS, then upgraded again to another OS & still have root? I did not wipe the Cache after I flashed the OS & the SuperSU, just rebooted through TWRP. Follow me there?
I'll leave this here for your ideas to tell me where I went wrong & how to fix this. It's frustrating to wait for 5 minutes until I can use my tablet, even though it works just fine (& a noticeably overall speed improvement too!) after it finishes optimizing the apps (again & again each time.
Click to expand...
Click to collapse
Read other topics. Its an issue on Update 3.0 (Android 5.1). Supposedly it goes away by going to settings --> about --> system update --> clear update data (3 dot menu) but I haven't tested it.
Other issue some people are having usb otg not working.
NaminatoR1254jaime.sier said:
Read other topics. Its an issue on Update 3.0 (Android 5.1). Supposedly it goes away by going to settings --> about --> system update --> clear update data (3 dot menu) but I haven't tested it.
Other issue some people are having usb otg not working.
Click to expand...
Click to collapse
Yeah, clearing the update data didn't work. It immediately went to "Android is starting" & optimizing the apps again. After a manual power off & on again, it did the same thing. And yes, I knew about the OTG not working. I saw those on other posts, which I can confirm that it no longer works. The OTG works beautifully on my Note 3 but when I plug it into the tablet...nothing. Doesn't even recognize it.
I suppose it's back to the previous version I have backed up in TWRP. I really need OTG to work when I'm using my tablet on my HDTV for typing on a Logitech K400 because trying to type with the controller just plain sux.
Ctrl_Alt_Del said:
Yeah, clearing the update data didn't work. It immediately went to "Android is starting" & optimizing the apps again. After a manual power off & on again, it did the same thing. And yes, I knew about the OTG not working. I saw those on other posts, which I can confirm that it no longer works. The OTG works beautifully on my Note 3 but when I plug it into the tablet...nothing. Doesn't even recognize it.
I suppose it's back to the previous version I have backed up in TWRP. I really need OTG to work when I'm using my tablet on my HDTV for typing on a Logitech K400 because trying to type with the controller just plain sux.
Click to expand...
Click to collapse
Unfortunately I'm in the same boat. I never rooted my shield tablet so the lack of otg support and always having the optimizing app on reboot sucks.
I hope nvidia puts a pach out soon
OTG should work if you power on the tablet with the OTG plugged in...pain in the butt...but better then nothing until they fix it.
Related
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...
I really don't know what I'm doing here.
I've been using CM11 for probably 6 months now, when I originally installed it I followed cynagenmod's wiki and used recovery-clockwork-6.0.4.4-xt926. Since then I'd updated several times using the phone menu. That quit working on the past couple versions I tried, something like "Unfortunately, CMUpdater has stopped".
I've been having some problems for about a week connecting to google+ (and my location is no longer sharing which annoys my wife), probably unlreated, but I decided I better figure out how to update my phone to the latest CM11, which looks to have stopped a month ago, but still newer than what I was running. I vaguely recalled something about pushing a volume button and power (when powered off) to load recovery bootloader or something... I figured I'd try that and see if there what was on those menus then go from there (hoping to install the CMupdate from there).
I couldn't remember if it was volume up or down or both or what, so I just tried volume up + boot. I figured I'd get a menu options, nothing would happen by itself. I was wrong. It showed a screen with an android with open belly for a while, then rebooted, said something about updating android then updating apps 1-62 or something... went on for a while... then finishing booting.
All seems normal. I was a little worried it was doing some type of reset or wipe or I dunno what. But not only does it appear normal, it updated to latest CM version. All by itself. I'm happy with results actually, but I have no idea what happened.
I would recommend using the latest TWRP.
The absolute latest compiled for our device can be found here.
The latest official TWRP is 2.7.1.2, which is also fine - but I believe it will not flash CM12 properly. At least it won't take advantage of the new F2FS file system.
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!
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
Starting on the first week of 2019, I have experienced problems with my Tab3 7 Essentials tablet that I bought 7-8 months after its initial release. I enjoyed it until that following day.
The problem first started after I am updating some apps from Google Play Store. I tried to update it, but got an error of -504 after 5-10 minutes of trying to install (not downloading from WiFi). One reviewer even said that the same thing happened on his device which runs Android 5.0.
I tried numerous apps to install/update, but the same problem, even for the apps that are not installed yet. I restarted my tablet.
The tablet went to the manufacturer bootlogo (right after the initial bootscreen with "Powered by Android" text) and instead of taking the regular time (about 15-40 seconds), it went up to about 7 minutes of the bootlogo to just start up.
I then tried to install/update my apps again, but this time, Play Store gave me an error of 910 (again install). Even Play Store is unable to update itself, but it either gives up and makes me unable to open Play Store until I restarted my tablet, or the tablet automatically restarts which took about another 7 minutes. What's weird is if the tablet has automatically restarted (soft reboot) because Android crashed, the logo doesn't show up but it boots up normally.
Also, my apps are soon going to be dependent on Lollipop and above, by making them incompatible with Jellybean, or my apps that I'm going to install isn't compatible with Jellybean.
I scanned my device for suspected malware by Malwarebytes, but nothing is found except one of the system apps (related to system update) that has Adups. None of the ads show up yet.
My firmware is updated to its latest version, if it helps. It originally came with the S00025 firmware and I'm running S000028. Each upgrade took around 30-35 minutes to optimize all apps with the black screen.
I knew that Lollipop should run correctly, because I have another tablet, which runs Jellybean, that works correctly except the ghost touch issue. Is there any solution to get out of this problem where I can't install some apps and the tablet taking around 7 minutes to boot up?
Sent from my Lenovo TB3-710F using Tapatalk
Bump.
Sent from my Lenovo TB3-710F using Tapatalk
slow boot Tab3 7
tried volume UP + power and reseted cache -> no changes
EoflaOE said:
Bump.
Sent from my Lenovo TB3-710F using Tapatalk
Click to expand...
Click to collapse
finally reset to factory solved issue - booting 35 sec
nEON7T said:
tried volume UP + power and reseted cache -> no changes
Click to expand...
Click to collapse