Hi all! I just picked up a Shield Tablet from Amazon about a week ago. I'm loving this Android probably more than my Note 3 (which, of course, is rooted. Stock rooted, but I like it that way!) My Shield tablet is rooted with Towelroot, but I'm on Kit Kat 4.4.2. I have root because of AdAway & Titaninum Backup. I have those in my Note 3 & I won't live without them on any Android device I have.
Now, onto the issue here...
I want to update to Lollipop to get the OS up to date. Also, I have these two annoying "reminders" in the taskbar that a ROM update (version 5.0.1) & a Tegra OTA update, each time at bootup & as time progresses they come back as notifications, even after I clear them.
Where can I find the process of upgrading to rooted Lollipop from rooted Kit Kat 4.4.2? It doesn't matter if I have to wipe the device in the process because there's just not much in there presently. Nothing more than XBMC Gotham edition & my apps from Google Play that came from my Google account when I logged into there from my tablet for the first time. I have a micro SD card in my tablet, so I don't want to lose what's on there...but...I can always remove it in the process to keep the data.
I have TWRP on my Note 3, but I've read that there's problems with that on the Shield tablet, so CWM wouldn't be so bad.
I've got a good laptop here (a Sony Vaio) so updating & rooting the Shield tablet won't be an issue.
Point me in the right direction please? From one Android lover to another?
What you could do (read everything):
1- Download and Flash a TWRP found here. with Flashify.
2- Factory reset, wipe everything, data, cache, system.
3- Then with TWRP flash a full OTA of the latest update (2.2.1)
4- Flash SuperSu.zip
5- Switch to .img and reflash TWRP recovery in recovery partition.
From 2 to 5 are easily done without leaving recovery to reboot.
I recommend having the supersu.zip, the full ota zip and the twrp 2.8.5.0 recovery img in the same folder.
I did something alike to move from 442 rooted to 501 rooted with locked bootloader. Except I did it with a Philz rec instead of TWRP. But I think is the same thing. Dont know the implications of unlocked bl.
PS1: Make a nandroid backup just in case.
PS2: You'll have to do almost this exact way everytime you want to update to the latest update. Except you won't have to factory reset, just wipe dalvik & cache in between. But you'll have to reflash recovery and supersu, just in case.
PS3: You won't lose anything on your external microsd card.
Things about TWRP, specifically 2.8.5.0 (haven't used 2.8.2.0):
1- Wiping cache & dalvik takes a loooong time with that TWRP (about 5 minutes). Reboot to system as well (1 minute). I make that comment so you don't think the tablet got stuck or hanged.
2- The only thing you have to avoid doing with this TWRP is Fix Permissions. Check here.
Hope you understand everything. Good luck.
NaminatoR1254jaime.sier said:
What you could do (read everything):
1- Download and Flash a TWRP found here. with Flashify.
2- Factory reset, wipe everything, data, cache, system.
3- Then with TWRP flash a full OTA of the latest update (2.2.1)
4- Flash SuperSu.zip
5- Switch to .img and reflash TWRP recovery in recovery partition.
From 2 to 5 are easily done without leaving recovery to reboot.
I recommend having the supersu.zip, the full ota zip and the twrp 2.8.5.0 recovery img in the same folder.
I did something alike to move from 442 rooted to 501 rooted with locked bootloader. Except I did it with a Philz rec instead of TWRP. But I think is the same thing. Dont know the implications of unlocked bl.
PS1: Make a nandroid backup just in case.
PS2: You'll have to do almost this exact way everytime you want to update to the latest update. Except you won't have to factory reset, just wipe dalvik & cache in between. But you'll have to reflash recovery and supersu, just in case.
PS3: You won't lose anything on your external microsd card.
Things about TWRP, specifically 2.8.5.0 (haven't used 2.8.2.0):
1- Wiping cache & dalvik takes a loooong time with that TWRP (about 5 minutes). Reboot to system as well (1 minute). I make that comment so you don't think the tablet got stuck or hanged.
2- The only thing you have to avoid doing with this TWRP is Fix Permissions. Check here.
Hope you understand everything. Good luck.
Click to expand...
Click to collapse
Where did you get the latest OTA update file?
Could you give me a link to the Nvidia site, and I'm assuming all the newest OTA zip's (flashable through TWRP) will be there when available as well?
FoxyDrew said:
Where did you get the latest OTA update file?
Could you give me a link to the Nvidia site, and I'm assuming all the newest OTA zip's (flashable through TWRP) will be there when available as well?
Click to expand...
Click to collapse
I dont know how they get them, but they're not available to the public. People usually get the links from other people that post them.
Here there are full ota under OTAs --> Download Full OTA's
If some mod see this post, pleeeeaseeee, pin that topic, it's really useful.
PS: Didn't give you an Nvidia link since they only host available to the public, the image files. And you need to register to get them. That xda link is much more useful.
NaminatoR1254jaime.sier said:
I dont know how they get them, but they're not available to the public. People usually get the links from other people that post them.
Here there are full ota under OTAs --> Download Full OTA's
If some mod see this post, pleeeeaseeee, pin that topic, it's really useful.
PS: Didn't give you an Nvidia link since they only host available to the public, the image files. And you need to register to get them. That xda link is much more useful.
Click to expand...
Click to collapse
The link that you posted was http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29979_515.3274.zip
That's "ota.nvidia.com" so it must be an official file from Nvidia's website no?
FoxyDrew said:
The link that you posted was http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29979_515.3274.zip
That's "ota.nvidia.com" so it must be an official file from Nvidia's website no?
Click to expand...
Click to collapse
Yes. But if you try to enter ota.nvidia.com you get a 403 Forbidden. And in Nvidia.com only the image files are available to the public. And you need to sign up (and someone to authorize you) in order for you to download them.
That's what I know at least.
No Dice...
NaminatoR1254jaime.sier... I did everything you suggested, & it did not work. When it came time to reboot, I saw Andy lying on his side with a red exclamation point in his open chest & the words "no command" under him. It did nothing else. I even had to buy Flashify because of it telling me that only three flashes can be done with the free version while doing your steps. It's okay, I needed to spend the Google Play money I got as a gift last Christmas.
I held the power button down for about 10 seconds, it shut off. I then held the power button & it rebooted into Kit Kat & everything seems normal. I'm back to square one.
Suggestions?
***Edit*** The more I try the steps above, I see that flashing TWRP is causing the error I mentioned. That's where it hangs.
If it makes any difference, I have the Wi-Fi version & the bootloader hasn't been touched. I see those were not mentioned in the original post.
***Okay...double-edit!***
I now have Lollipop AND root! 5.0.1. I had to go in different order than you suggested, but all is good. Flashify to install TWRP, reboot, did NOT wipe dalvic/cache, side loaded the latest SuperSU THEN installed Lollipop ROM through TWRP, & a final reboot. Took about 10 minutes for all apps to finalize at bootup.
I've been at this all evening & all of my data/apps are there. At least Gold Rush was on TV tonight to keep me company!
I thank you for pointing me in the right direction, even though it started out badly. It's a new device, but it's still an Android. How hard could it be since I've rooted all my other Androids? :good:
Great news!! Well done!!
Take note that to flash new updates, you'll have to do the same, with full OTAs of new updates.
Good luck!
NaminatoR1254jaime.sier said:
Great news!! Well done!!
Take note that to flash new updates, you'll have to do the same, with full OTAs of new updates.
Good luck!
Click to expand...
Click to collapse
Understood! I suppose it's the price to pay to be rooted until an even better solution comes out. One click/tap, maybe?
Related
So finally took the plunge and flashed Cromi-X 5,2,2. Current set up is bootloader 10.8, TWRP 2.5.0 unlocked and rooted. I was running fine for a couple of days and decided to try cromi control to turn of a couple of notifications.I didnt reboot from cromi control as I read there was a bug. I powered off using the power button and when powering back on I was stuck on boot animation. Options I chose on the original flash was _thatv4 10.8 with defaults. No ET / OV / OC / No tweaks. So i decided to dirty flash 5.2.2 again without formating data I got to upgrading apps and when it rebooted, back stuck on animation. I am going to try flashing my original stock asus nandroid.prior to 5.2.2 just to get it working for the evening.
Doing a search of the thread now... See this has been covered on 5.2.1. I may have to wipe / format data IDK
Any suggestions?
Thanks
Update
Restored my nandroid and back up and running.. Guess I have some reading to do.
Would updating to 8.10 and latest TWRP help any? Maybe try that and use _thatv7 next go around.
GPWILL said:
Restored my nandroid and back up and running.. Guess I have some reading to do.
Would updating to 8.10 and latest TWRP help any? Maybe try that and use _thatv7 next go around.
Click to expand...
Click to collapse
It is always good to have the latest bootloader and TWRP. What is your firmware or bootloader now? What do you want to achieve or usage on your device? _that v7 on Cromi X is a nice combo with speed and stability...
GPWILL said:
Restored my nandroid and back up and running.. Guess I have some reading to do.
Would updating to 8.10 and latest TWRP help any? Maybe try that and use _thatv7 next go around.
Click to expand...
Click to collapse
Glad you got it working again. It's strange - what happened is typical for rebooting from the Cromi app, but you didn't.....
Did you do a factory wipe in TWRP before installing CROMi-X?
Also, it certainly wouldn't hurt to update your recovery. Just flash the bootloader/TWRP package in the CROMi-X OP and reboot to system.
My current working is 10.6.1.14.8 from ASUS and TWRP 2.5.0. I did a factory wipe in TWRP before flashing Cromi 5.2.2. Everything went smooth. I let google restore my apps when running thru the setup wizard. A little painful but only took 30 minor so. I didnt restore any apps or data from my TB. So I let it run for a couple of days with no issues. I ran into trouble with the chromi control. Wanted to get rid of that annoying external card notification. Powered off using the power button and boom. Things went south. I am not a overclock / tweak poweruser. Just wanted a little tweak since it looks like ASUS is not going to update anymore. My tab is a little over a year old and my only complaints have been browser lag and the painful lag of using the tablet when apps updates. My intent is to get 5.2.2. Run thru set up / installer a couple of times so I could get use the installer and then at some point venture into rom2sd or data2sd. Next go around I will get 5.2.2 working and nandroid that. I had tried B2R and it works ok. But with 5.2.2 it seems to give the tab a big 'push'. The browser worked way faster. I tried both stock and Chrome with 5.2.2 and was nice and smooth..
Thanks for the responses. If you think of anything else I appreciate it. Been on this forum for awhile and you guys are great!
GPWILL said:
My current working is 10.6.1.14.8 from ASUS and TWRP 2.5.0. I did a factory wipe in TWRP before flashing Cromi 5.2.2. Everything went smooth. I let google restore my apps when running thru the setup wizard. A little painful but only took 30 minor so. I didnt restore any apps or data from my TB. So I let it run for a couple of days with no issues. I ran into trouble with the chromi control. Wanted to get rid of that annoying external card notification. Powered off using the power button and boom. Things went south. I am not a overclock / tweak poweruser. Just wanted a little tweak since it looks like ASUS is not going to update anymore. My tab is a little over a year old and my only complaints have been browser lag and the painful lag of using the tablet when apps updates. My intent is to get 5.2.2. Run thru set up / installer a couple of times so I could get use the installer and then at some point venture into rom2sd or data2sd. Next go around I will get 5.2.2 working and nandroid that. I had tried B2R and it works ok. But with 5.2.2 it seems to give the tab a big 'push'. The browser worked way faster. I tried both stock and Chrome with 5.2.2 and was nice and smooth..
Thanks for the responses. If you think of anything else I appreciate it. Been on this forum for awhile and you guys are great!
Click to expand...
Click to collapse
With your current firmware, 10.6.1.14.8, you should have the latest bootloader but you still need to update your TWRP to a later version, 2.6.1.0 or 2.6.3.0.. You need to pick one. I am still using 2.6.1.0 and it works fine at the moment and no plan to update to 2.6.3.0. I am very sure that you know how to update your custom recovery, TWRP,
If I am not mistaken, you have the old backup but not the 5.2.2 backup before it crashed... It is always a good idea to backup your good working current setup so you can go back or restore if something is going wrong.. One more thing about backup, it would be nice if you can keep your backup and personal stuff on your External SD, Not the internal SD...
Rom and kernel selections: Cromi v5.2.2 is the latest and the fastest in my opinion so it is your first choice unless you something else in mind.. You only have a few selections on kernel and they are all good and serve with a different purposes. sbdags is very closed to stock with a minimal modifications. _that v7 is the latest and more modifications comparing to sbdags. However, it is faster and more stable or most stable of all according to testers and users... Hund's kernel is the fastest of all with even more modifications and options for users to change settings. Testers and users report back with a little less stable comparing to _that but I don't have a single problem with this kernel... However, it is running a little warmer than sbdags and _that because it is running with higher frequency...Max kernel is another option but it seems like there is no supports at the moment. No one knows where he is, haha... Hopefully, we can hear back from him again...
Installation: Totally clean installing because you are already having issue...
1. Backup anything that you want to save including your personal data and files
2. Copy cromi and kernel that you want to install to your External SD because you want to format your data partition
3. Format your data partition and I mean Format, not wipe.
4. Wipe everything on your device including your system but not your external SD..
5. Install cromi and kernel of your choices
6. Reboot and let it sits for a few minutes, then you can do your setup from the setup wizard
7. Go back to your TWRP and do a nandroid backup to your External SD, just in case so you restore it
8. Install your apps or whatever you want from the google store, not from your TB so you can have a good and stable backup
9. After you are done with all the apps and games installation, you may want to do another backup in the TWRP
10. Now you can do whatever you want from this point and if you have more settings to do, you may want to do another backup as a Final backup and a good working one... You can delete the other backup from the previous if you have the final and working backup. You just need one good working backup..That is it..
You can always go back to TWRP to restore just your data or just a system or a whole backup. Those are the options that you can restore and good luck...:fingers-crossed:
LetMeKnow said:
With your current firmware, 10.6.1.14.8, you should have the latest bootloader but you still need to update your TWRP to a later version, 2.6.1.0 or 2.6.3.0.. You need to pick one. I am still using 2.6.1.0 and it works fine at the moment and no plan to update to 2.6.3.0. I am very sure that you know how to update your custom recovery, TWRP,
If I am not mistaken, you have the old backup but not the 5.2.2 backup before it crashed... It is always a good idea to backup your good working current setup so you can go back or restore if something is going wrong.. One more thing about backup, it would be nice if you can keep your backup and personal stuff on your External SD, Not the internal SD...
Rom and kernel selections: Cromi v5.2.2 is the latest and the fastest in my opinion so it is your first choice unless you something else in mind.. You only have a few selections on kernel and they are all good and serve with a different purposes. sbdags is very closed to stock with a minimal modifications. _that v7 is the latest and more modifications comparing to sbdags. However, it is faster and more stable or most stable of all according to testers and users... Hund's kernel is the fastest of all with even more modifications and options for users to change settings. Testers and users report back with a little less stable comparing to _that but I don't have a single problem with this kernel... However, it is running a little warmer than sbdags and _that because it is running with higher frequency...Max kernel is another option but it seems like there is no supports at the moment. No one knows where he is, haha... Hopefully, we can hear back from him again...
Installation: Totally clean installing because you are already having issue...
1. Backup anything that you want to save including your personal data and files
2. Copy cromi and kernel that you want to install to your External SD because you want to format your data partition
3. Format your data partition and I mean Format, not wipe.
4. Wipe everything on your device including your system but not your external SD..
5. Install cromi and kernel of your choices
6. Reboot and let it sits for a few minutes, then you can do your setup from the setup wizard
7. Go back to your TWRP and do a nandroid backup to your External SD, just in case so you restore it
8. Install your apps or whatever you want from the google store, not from your TB so you can have a good and stable backup
9. After you are done with all the apps and games installation, you may want to do another backup in the TWRP
10. Now you can do whatever you want from this point and if you have more settings to do, you may want to do another backup as a Final backup and a good working one... You can delete the other backup from the previous if you have the final and working backup. You just need one good working backup..That is it..
You can always go back to TWRP to restore just your data or just a system or a whole backup. Those are the options that you can restore and good luck...:fingers-crossed:
Click to expand...
Click to collapse
Been awhile since I played with fastboot. Can I just flash the bootloader and twrp zip from the 5.2.2 Cromi thread and be ok? I know to flash this first and reboot into rom before flashing 5.2.2 again. Otherwise I will get fastboot going again.
"10.6.1.14.10 US Bootloader and TWRP 2.6.1.0 DOWNLOAD 1" This is in scenario 2 which doesnt really apply because I dont have a custom rom installed yet at this point.
I am saving these notes for future reference. Thanks for the time in writing these up.
GPWILL said:
Been awhile since I played with fastboot. Can I just flash the bootloader and twrp zip from the 5.2.2 Cromi thread and be ok? I know to flash this first and reboot into rom before flashing 5.2.2 again. Otherwise I will get fastboot going again.
"10.6.1.14.10 US Bootloader and TWRP 2.6.1.0 DOWNLOAD 1" This is in scenario 2 which doesnt really apply because I dont have a custom rom installed yet at this point.
I am saving these notes for future reference. Thanks for the time in writing these up.
Click to expand...
Click to collapse
I think that it would fine since you are running TWRP 2.5. Please be careful when you install custom recovery and bootloader. If you make a mistake, it could brick your device, just my two cents.. Please ask a lot of questions to be sure...
Note: From your TWRP 2.5, install 10.6.1.14.10 first and reboot so the blob can update your bootloader. When it boots into the system, then you need to reboot it back into your TWRP 2.5 and install the TWRP 2.6.1.0. When it is done, then you need to shut it down and use your power button and volume down to boot back into your new TWRP...Good luck..:fingers-crossed:
Always check your download "MD5 Sum" to verify that you have a good download....
You have my attention now and I will take your offer to ask questions. So if I understand correctly the bootloader and twrp zip from above will allow to flash them individually? In twrp point to the zip and it gives you options to flash the bootloader without twrp? I would do this:
1. boot into twrp and choose install.
2. choose zip from above
3. choose bootloader only?
4. reboot into rom. let it sit for a few.
5 reboot into twrp
6 choose new twrp?
7 reboot into rom.
Just trying to be clear so no brick...
I would upgrade in goomanager. Thats how I got twrp to begin with. But I have read it doesnt work anymore?
GPWILL said:
You have my attention now and I will take your offer to ask questions. So if I understand correctly the bootloader and twrp zip from above will allow to flash them individually? In twrp point to the zip and it gives you options to flash the bootloader without twrp? I would do this:
1. boot into twrp and choose install.
2. choose zip from above
3. choose bootloader only?
4. reboot into rom. let it sit for a few.
5 reboot into twrp
6 choose new twrp?
7 reboot into rom.
Just trying to be clear so no brick...
I would upgrade in goomanager. Thats how I got twrp to begin with. But I have read it doesnt work anymore?
Click to expand...
Click to collapse
I never use the method from cromi thread but I trust sbdags as a great developer and so many users used this method without a problem...
If you are still running stock firmware version 10.6.1.14.8, then you still can use goomanager to update your TWRP... If you prefer it that way, then goo still works for you...If you are on stock version 10.6.1.14.8, you are already on the latest bootloader unless you want the latest stock firmware V14.10 which you will update it with Cromi any way...
1. Use goo to update the correct TWRP, 2.6.3.0 or 2.6.1.0
2. Boot into your new TWRP and install the Cromi and follow the instructions that I wrote earlier
Good luck..:fingers-crossed:
GPWILL said:
You have my attention now and I will take your offer to ask questions. So if I understand correctly the bootloader and twrp zip from above will allow to flash them individually? In twrp point to the zip and it gives you options to flash the bootloader without twrp? I would do this:
1. boot into twrp and choose install.
2. choose zip from above
3. choose bootloader only?
4. reboot into rom. let it sit for a few.
5 reboot into twrp
6 choose new twrp?
7 reboot into rom.
Just trying to be clear so no brick...
I would upgrade in goomanager. Thats how I got twrp to begin with. But I have read it doesnt work anymore?
Click to expand...
Click to collapse
Not quite.
You cannot flash BL or TWRP separately from that package. It's either both or none.
But flashing the package would be the easiest and safest method to get you on a current recovery in my opinion.
GooManager: For a few weeks now Goo did not support flashing recoveries anymore. I've read it often enough that I consider that information confirmed - although I have not tested it myself.
Now - just yesterday I read a post where a user reported that Goo got an update and he flashed TWRP successfully. That's one report I know of - if you want to give it a try, go for it. It can't hurt.
The thing is, to use GooManager you have to root the stock rom you are running.
I don't know if the stock rom you are running is rooted, but why bother if you can just flash sbdags package??
Sounds like choosing _thatv7 from the 5.2.2 also upgrades the bootloader also to 10? I assumed you needed the correct bootloader already installed.
I will give goo a go and see what happens.
GPWILL said:
Sounds like choosing _thatv7 from the 5.2.2 also upgrades the bootloader also to 10? I assumed you needed the correct bootloader already installed.
I will give goo a go and see what happens.
Click to expand...
Click to collapse
Well goomanager didnt work for me. Just sits on "downloading" forever. only option was to upgrade to 2.6.3.1
Off to get fastboot working..
GPWILL said:
Sounds like choosing _thatv7 from the 5.2.2 also upgrades the bootloader also to 10? I assumed you needed the correct bootloader already installed.
I will give goo a go and see what happens.
Click to expand...
Click to collapse
_thatv7 is one of the kernel choices - changing a kernel does not do anything to the bootloader.
Look at these elements of the system as parts of an engine: If the bootloader is the starter motor, the kernel may be the distributor.....
Thanks for trying Goo, the score is 1:1
Anyway, to get fastboot working is worth the effort. It's great for troubleshooting or pulling logs and such. It's very helpful to have a working fastboot connection BEFORE you run into some trouble and really need it to work
I guess my question is if I choose _thatv7 will bootloader .8 work? The 10 after the kernel choice is what has put me down this road.
fastboot and adb working. So getting there albeit slowly.
This thread really helped a lot in my learning process..
http://forum.xda-developers.com/showthread.php?t=2546420&highlight=flash+10+6+1+14+10+fastboot
Thanks again for all the info and help.
GPWILL said:
I guess my question is if I choose _thatv7 will bootloader .8 work? The 10 after the kernel choice is what has put me down this road.
fastboot and adb working. So getting there albeit slowly.
This thread really helped a lot in my learning process..
http://forum.xda-developers.com/showthread.php?t=2546420&highlight=flash+10+6+1+14+10+fastboot
Thanks again for all the info and help.
Click to expand...
Click to collapse
There's hardly anything different between the. 8 and . 10 bootloader. V7 works fine with either.
Sent from my DROID4 using Tapatalk
berndblb said:
There's hardly anything different between the. 8 and . 10 bootloader. V7 works fine with either.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Update:
Updated TWRP to 2.6.1
fastboot and adb working
Flashed 5.2.2 Cromi-X _thatv7 this time around. (used the advice from above)
Set up apps
I will def nandroid this working config..
All good now.
Thanks to everyone!
FYI I updated goomanager and tried it again on my old setup and it still did not work updating twrp. Stuck on downloading app...
GPWILL said:
Update:
Updated TWRP to 2.6.1
fastboot and adb working
Flashed 5.2.2 Cromi-X _thatv7 this time around. (used the advice from above)
Set up apps
I will def nandroid this working config..
All good now.
Thanks to everyone!
FYI I updated goomanager and tried it again on my old setup and it still did not work updating twrp. Stuck on downloading app...
Click to expand...
Click to collapse
Fastboot is a prefer method to use...:good: I always use fastboot for this stuff. It is fast and easy without any hassle...
How is it running? It should be running very reasonable speed and smoothness...
LetMeKnow said:
Fastboot is a prefer method to use...:good: I always use fastboot for this stuff. It is fast and easy without any hassle...
How is it running? It should be running very reasonable speed and smoothness...
Click to expand...
Click to collapse
It is running pretty nice. Stock browser and Chrome are a little faster than my stock setup with B2R. I have had a few " laucher has stopped" errors. This happened before I installed any apps with thatV7. Didnt get a single laucher error before on thatv4. Stock laucher. Nice and smooth on apps and such. Both stock browser and chrome are faster but not anything like "WOW". Just a little better. Nice to have it built in. I am going to give this a few more days and see if the laucher errors settle down. If it stablizes I will get another nandroid of it and try the ROM2SD to see if I can get the wow factor going.
Hey there, guys. I've been around XDA a while & have messed around with different ROMS. I had found one that I liked (decent battery life is the most important for me) & stuck with ParanoidAndroid 3.60 (4.2 based ROM) for Android 4.1 (I believe the firmware version is 10.4.2.20). TWRP is 2.5.0.0. This was around 1-2 years ago, and I finally decided it was time to upgrade it.
Can anyone point me the direction on where to start? I would like to update to the latest (or most stable) android version, if possible. I have a basic knowledge of fastboot & how it works.:fingers-crossed:
First, you will have to upgrade your bootloader to the latest version to run the latest recovery. I don't know if there's an easier way of doing this, but I'd suggest installing a stock ROM and then unlocking/rooting/installing recovery again.
You can download the latest official firmware from here (assuming you have a TF300T model): http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Make sure to select the one with the correct SKU.
Then, follow this guide: http://forum.xda-developers.com/showthread.php?t=1757077
This will wipe all your data so make sure to backup all the files you need.
The bootloader will most likely remain unlocked, so what you need now is root and recovery. There are plenty of guides for those, so find the right one for you. You can download the latest TWRP from here: http://teamw.in/project/twrp2/97
An installation guide is on the same page, but make sure to download the one ending with 4.2 since you will be on the latest firmware version (here's the name of the file you'll probably need if you have a TF300T model: openrecovery-twrp-2.6.3.0-tf300t-4.2.blob).
Hope this will help
Duchman said:
First, you will have to upgrade your bootloader to the latest version to run the latest recovery. I don't know if there's an easier way of doing this, but I'd suggest installing a stock ROM and then unlocking/rooting/installing recovery again.
You can download the latest official firmware from here (assuming you have a TF300T model): http://www.asus.com/Tablets_Mobile/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/
Make sure to select the one with the correct SKU.
Then, follow this guide: http://forum.xda-developers.com/showthread.php?t=1757077
This will wipe all your data so make sure to backup all the files you need.
The bootloader will most likely remain unlocked, so what you need now is root and recovery. There are plenty of guides for those, so find the right one for you. You can download the latest TWRP from here: http://teamw.in/project/twrp2/97
An installation guide is on the same page, but make sure to download the one ending with 4.2 since you will be on the latest firmware version (here's the name of the file you'll probably need if you have a TF300T model: openrecovery-twrp-2.6.3.0-tf300t-4.2.blob).
Hope this will help
Click to expand...
Click to collapse
Thanks for replying! I got it to boot, but it stays stuck on the Asus logo with the loading circle. I installed the correct TWRP recovery. I tried rebooting, but it says no OS installed. Furthermore, it does not mount the External storage. I can browse the files through the file Manager in TWRP.
EDIT: It rebooted & I have everything back. It just took forever to reboot. Thanks for your help!!
boxer3310 said:
Thanks for replying! I got it to boot, but it stays stuck on the Asus logo with the loading circle. I installed the correct TWRP recovery. I tried rebooting, but it says no OS installed. Furthermore, it does not mount the External storage. I can browse the files through the file Manager in TWRP.
EDIT: It rebooted & I have everything back. It just took forever to reboot. Thanks for your help!!
Click to expand...
Click to collapse
I'm glad I was able to help. Could you tell me the order of your actions and what happened after what? I'm a bit confused as to why it'd get stuck like this.
Also, you might need a newer recovery for more recent ROMs. There are both 2.7.0.1 and 2.7.1.0 versions available in the development section.
Duchman said:
I'm glad I was able to help. Could you tell me the order of your actions and what happened after what? I'm a bit confused as to why it'd get stuck like this.
Also, you might need a newer recovery for more recent ROMs. There are both 2.7.0.1 and 2.7.1.0 versions available in the development section.
Click to expand...
Click to collapse
I did everything as you posted:
1. Downloaded the most current firmware for the TF300T from the Asus site.
2. Pushed it to my device using fastboot
3. Installed custom recovery for my version of Android
4. Rebooted.
The Installation bar completed after I pushed the firmware & recovery. It just took long to reboot. I read that you have to let the ROM "stabilize," so I suspect it might have been the cause of the hang. Everything went pretty smooth after the reboot, though. I installed TWRP 2.7.1.0 (as you posted above) and installed a new ROM. Thank you very much for taking the time to reply. I love this update! :victory:
Ok so.. here's a quick guide to flashing 5.0.1 on the Nvidia Shield Tablet. I have the 16GB Wifi version so if you have a different version (LTE or non-US tablet) this guide may or may not apply to you. I also essentially dirty flashed this in CWM recovery. If you're using TWRP WIP, no idea if it will blow up or not. Standard disclaimer applies if your Tablet blows up or anything, i'm not responsible. You do these steps at your own risk. I'm going on the premise that you have the Shield drivers already installed and have some flashing knowledge.
This is an upgrade from 5.0 to 5.0.1
This guide DOES NOT utilize the OTA zip that your tablet downloaded.
1. Download http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29082_493.9700.zip (AGAIN, US 16gb WIFI only, there's another thread here somewhere with other full download links) I copied it to external SDCard rather than tablet storage.
2. adb reboot recovery to get into CWM or shut down and use the hardware keys to reboot to recovery
3. In CWM, install zip from external sd card and flash it like a normal rom. CWM reports this sucessful and reboot to 5.0.1 and let it settle. It updates binaries and blah blah. Oh also root and recovery are now gone. You should still have fastboot.
4. reboot into fastboot, hardware keys again or using adb reboot bootloader.
5. Now you follow the excellent post by sandrodjay for restoring CWM and root. (If you didn't wipe, most of the preliminaries in sandrodjay's post should already be done. Debug mode and whatnot) http://forum.xda-developers.com/shi...t-lollipop-t2972316/post57719881#post57719881
After the dust settled for me, i was on 5.0.1 and had CWM and root back. YMMV.
terrigan said:
Ok so.. here's a quick guide to flashing 5.0.1 on the Nvidia Shield Tablet. I have the 16GB Wifi version so if you have a different version (LTE or non-US tablet) this guide may or may not apply to you. I also essentially dirty flashed this in CWM recovery. If you're using TWRP WIP, no idea if it will blow up or not. Standard disclaimer applies if your Tablet blows up or anything, i'm not responsible. You do these steps at your own risk. I'm going on the premise that you have the Shield drivers already installed and have some flashing knowledge.
1. Download http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29082_493.9700.zip (AGAIN, US 16gb WIFI only, there's another thread here somewhere with other full download links) I copied it to external SDCard rather than tablet storage.
2. adb reboot recovery to get into CWM or shut down and use the hardware keys to reboot to recovery
3. In CWM, install zip from external sd card and flash it like a normal rom. CWM reports this sucessful and reboot to 5.0.1 and let it settle. It updates binaries and blah blah. Oh also root and recovery are now gone. You should still have fastboot.
4. reboot into fastboot, hardware keys again or using adb reboot bootloader.
5. Now you follow the excellent post by sandrodjay for restoring CWM and root. (If you didn't wipe, most of the preliminaries in sandrodjay's post should already be done. Debug mode and whatnot) http://forum.xda-developers.com/shi...t-lollipop-t2972316/post57719881#post57719881
After the dust settled for me, i was on 5.0.1 and had CWM and root back. YMMV.
Click to expand...
Click to collapse
What CWM version are you using? My CWM is reporting a failure to update because it thinks I'm still running Android 4.4.2.
dibblebill said:
What CWM version are you using? My CWM is reporting a failure to update because it thinks I'm still running Android 4.4.2.
Click to expand...
Click to collapse
Did you for download full ota zip 700mb or did you try flashing partial which you would get through system update
Full ZIP not OTA. The 700mb download. Also i'm using the flashed recovery.img from sandrojay's post which is CWM 6.0.5.0. Are you guys on 5.0 or 4.4.4? I suppose i should mention this is an upgrade from 5.0 to 5.0.1
terrigan said:
Full ZIP not OTA. The 700mb download. Also i'm using the flashed recovery.img from sandrojay's post which is CWM 6.0.5.0. Are you guys on 5.0 or 4.4.4? I suppose i should mention this is an upgrade from 5.0 to 5.0.1
Click to expand...
Click to collapse
I'm running the stock lollipop build. I tried removing the checks from the updater script but it still won't install.
dibblebill said:
I'm running the stock lollipop build. I tried removing the checks from the updater script but it still won't install.
Click to expand...
Click to collapse
Are you running the same CWM?
dibblebill said:
I'm running the stock lollipop build. I tried removing the checks from the updater script but it still won't install.
Click to expand...
Click to collapse
It sounds like you are trying to install the partial ota can you confirm
Yeah this guide isn't meant to utilize the OTA zip. My first instruction is to download the whole 700mb update.
mcord11758 said:
It sounds like you are trying to install the partial ota can you confirm
Click to expand...
Click to collapse
terrigan said:
Yeah this guide isn't meant to utilize the OTA zip. My first instruction is to download the whole 700mb update.
Click to expand...
Click to collapse
I see that now. Downloading the full OTA. Modified your link to the "do" version.
It worked this time though I oddly didn't need to reflash CWM
Sent from my Sony Xperia Z3
Thanks for the topic. Anyone has a link for full 5.0.1 for EU WIFI version ?
Aanze said:
Thanks for the topic. Anyone has a link for full 5.0.1 for EU WIFI version ?
Click to expand...
Click to collapse
I flashed the NA one as someone mentioned that they seems to be the same - worked fine on my system.
Thanks for the feedback, trying it right now
terrigan said:
Ok so.. here's a quick guide to flashing 5.0.1 on the Nvidia Shield Tablet. I have the 16GB Wifi version so if you have a different version (LTE or non-US tablet) this guide may or may not apply to you. I also essentially dirty flashed this in CWM recovery. If you're using TWRP WIP, no idea if it will blow up or not. Standard disclaimer applies if your Tablet blows up or anything, i'm not responsible. You do these steps at your own risk. I'm going on the premise that you have the Shield drivers already installed and have some flashing knowledge.
This is an upgrade from 5.0 to 5.0.1
This guide DOES NOT utilize the OTA zip that your tablet downloaded.
1. Download http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29082_493.9700.zip (AGAIN, US 16gb WIFI only, there's another thread here somewhere with other full download links) I copied it to external SDCard rather than tablet storage.
2. adb reboot recovery to get into CWM or shut down and use the hardware keys to reboot to recovery
3. In CWM, install zip from external sd card and flash it like a normal rom. CWM reports this sucessful and reboot to 5.0.1 and let it settle. It updates binaries and blah blah. Oh also root and recovery are now gone. You should still have fastboot.
4. reboot into fastboot, hardware keys again or using adb reboot bootloader.
5. Now you follow the excellent post by sandrodjay for restoring CWM and root. (If you didn't wipe, most of the preliminaries in sandrodjay's post should already be done. Debug mode and whatnot) http://forum.xda-developers.com/shi...t-lollipop-t2972316/post57719881#post57719881
After the dust settled for me, i was on 5.0.1 and had CWM and root back. YMMV.
Click to expand...
Click to collapse
Does this upgrade method loose all data (like factory reset) or not loosing anything other than CWM and root? Thanks.
If you don't wipe, no. Everything stays.
layanto said:
Does this upgrade method loose all data (like factory reset) or not loosing anything other than CWM and root? Thanks.
Click to expand...
Click to collapse
I've got good news... Your data and apps remain untouched, only litle problem depending on number of apps is time to "optimize apps" on first boot after update
Thank you for this!
Aanze said:
Thanks for the feedback, trying it right now
Click to expand...
Click to collapse
Did it work?
Just to make it clear for all, I've flashed the wifi version....
Tried with all (really all) the recovery in XDA ending with error.
The only recovery that worked is the 6.0.5.0!!
Updated dirty flashed but ended with lag for me, so clean install, and now all is good.
(was unlocked bootloader)
Lost recovery and lost root of course, but with adb takes 2 minutes to put them back.
ciribaski said:
Just to make it clear for all, I've flashed the wifi version....
Tried with all (really all) the recovery in XDA ending with error.
The only recovery that worked is the 6.0.5.0!!
Updated dirty flashed but ended with lag for me, so clean install, and now all is good.
(was unlocked bootloader)
Lost recovery and lost root of course, but with adb takes 2 minutes to put them back.
Click to expand...
Click to collapse
+1 as I've also just flashed the full wifi update to 5.0.1 using CWM v6.0.5.0, without wiping data, and everything came back up nicely. Still giving the tablet a chance to settle in after re-rooting with SuperSU v2.40, but hoping that the extreme lag doesn't return. If it does, I suppose I'll have to try a full wipe.
One thing I noticed is that after the very first reboot (without rooting, immediately after flashing the update), the system was very busy, and this could have been due to FolderMount trying to mount folders on boot using root when the tablet was NOT rooted. I'd recommend disabling FolderMount from auto-mounting on boot if you have it configured that way.
Thanks for providing this full 5.0.1 update package OP!
Hello community,
I was given the device last year and had been fairly satisfied with the performance of it. However, it has gotten laggy over the past couple weeks and a friend suggested to root and flash a rom on it. So, without any prior knowledge, I have been doing some research and browsing through the threads on this forum. I can see that there are guides but was very unsure if the methods would still work because I have noticed that most of them were last updated/edit a while ago. I know I shouldn't use the word 'latest' for doing this to a tablet that is fairly old in the market. However, it would be very helpful if someone can point me to some 'proven to work' or 'trust-worthy' guides of rooting, flashing recovery, and rom.
Also, just out of curiosity, please recommend which recovery and rom a first-timer should use if possible
try these roms.
rocketfans14 said:
Hello community,
I was given the device last year and had been fairly satisfied with the performance of it. However, it has gotten laggy over the past couple weeks and a friend suggested to root and flash a rom on it. So, without any prior knowledge, I have been doing some research and browsing through the threads on this forum. I can see that there are guides but was very unsure if the methods would still work because I have noticed that most of them were last updated/edit a while ago. I know I shouldn't use the word 'latest' for doing this to a tablet that is fairly old in the market. However, it would be very helpful if someone can point me to some 'proven to work' or 'trust-worthy' guides of rooting, flashing recovery, and rom.
Also, just out of curiosity, please recommend which recovery and rom a first-timer should use if possible
Click to expand...
Click to collapse
hello ,
these are the things you need to do before flashing a ROM.
note: -the following things may void your warranty.
-do this on your own risk.
1. HOW TO ROOT
-First install kingo root on your windows PC. Then check USB debugging .
( settings. < about device < touch build number 7times < go back and select developer options < check USB debugging.)
-Open kingo root on the PC and connect your device and connect your device to the PC. Start root and do not remove the USB cable until it says finish.
-Now you have successfully rooted your device.
2.HOW TO INSTALL A CUSTOM RECOVERY
- Go to the following link and download CLOCK WORK MOD(CWM)
LINK: https://www.clockworkmod.com/rommanager
Select your device and install the recovery.
go into the app and install recovery .
3.BACK UP
download rom manager from playstore and do a backup( do a backup using this ap only if you are using CWM recovery.
link for ROM manager: https://play.google.com/store/apps/d...mmanager&hl=en
Now the first thing you need to do is download this rom.
https://www.androidfilehost.com/?fid=95916177934533333
(note: you can flash the rom of p5110 for p5113)
now to flash the rom follow the following steps.
1. Go to recovery mode
2. (have the rom in your sd card)flash it there .
use this link to know how to flash a rom.
https://www.youtube.com/watch?v=tJfPwWjnWGY
now you can reboot after flashing.
to get inbuilt google apps and play store you need to install something called GAPPS (Google apps) download from this link.
http://opengapps.org/?api=5.1&variant=nano
now you flash this zip the same way you flashed the rom.
any problems plz notoce me.
Zte blade l said:
hello ,
these are the things you need to do before flashing a ROM.
note: -the following things may void your warranty.
-do this on your own risk.
1. HOW TO ROOT
-First install kingo root on your windows PC. Then check USB debugging .
( settings. < about device < touch build number 7times < go back and select developer options < check USB debugging.)
-Open kingo root on the PC and connect your device and connect your device to the PC. Start root and do not remove the USB cable until it says finish.
-Now you have successfully rooted your device.
2.HOW TO INSTALL A CUSTOM RECOVERY
- Go to the following link and download CLOCK WORK MOD(CWM)
LINK: https://www.clockworkmod.com/rommanager
Select your device and install the recovery.
go into the app and install recovery .
3.BACK UP
download rom manager from playstore and do a backup( do a backup using this ap only if you are using CWM recovery.
link for ROM manager: https://play.google.com/store/apps/d...mmanager&hl=en
Now the first thing you need to do is download this rom.
https://www.androidfilehost.com/?fid=95916177934533333
(note: you can flash the rom of p5110 for p5113)
now to flash the rom follow the following steps.
1. Go to recovery mode
2. (have the rom in your sd card)flash it there .
use this link to know how to flash a rom.
https://www.youtube.com/watch?v=tJfPwWjnWGY
now you can reboot after flashing.
to get inbuilt google apps and play store you need to install something called GAPPS (Google apps) download from this link.
http://opengapps.org/?api=5.1&variant=nano
now you flash this zip the same way you flashed the rom.
any problems plz notoce me.
Click to expand...
Click to collapse
I was looking in the forum and someone said that I would also need to unlock the bootloader? If so, how do I do that?
Also, is there a difference between kingroot and towelroot? I saw a post in the forum here saying towelroot is fast and easy to root the tablet.
Not much difference.
Actually there is not much difference between kings root and towel root....towel root doesn't need a PC...but I have never used it so I can't assure you that it is safe.
And coming to the boot loader I don't know much about it but I didn't do anything like that before flashing a rom or rooting my tab2....
If you want further assistance about the boot loader I can help you with that..
rocketfans14 said:
I was looking in the forum and someone said that I would also need to unlock the bootloader? If so, how do I do that?
Also, is there a difference between kingroot and towelroot? I saw a post in the forum here saying towelroot is fast and easy to root the tablet.
Click to expand...
Click to collapse
it is not necessary to unloack bootloader for tab 2 as it comes with a unlocked bootloader from stock.
Zte blade l said:
Actually there is not much difference between kings root and towel root....towel root doesn't need a PC...but I have never used it so I can't assure you that it is safe.
And coming to the boot loader I don't know much about it but I didn't do anything like that before flashing a rom or rooting my tab2....
If you want further assistance about the boot loader I can help you with that..
Click to expand...
Click to collapse
Hey, it's been a while. Honestly speaking, when I first posted this thread, I didn't really have enough time to do the things so now I am finally back and trying to do it. So far, I know what recovery and rom I'm going to use with all the files downloaded and ready. Though, currently, I am still at the pre-root stage. I have read up things about kingoroot and not sure if I wanted to use it. So I looked around on the forum and wonder if Odin is still a working solution. Reading on the steps and guides, I was wondering if I need to have Kies installed?
rocketfans14 said:
Hey, it's been a while. Honestly speaking, when I first posted this thread, I didn't really have enough time to do the things so now I am finally back and trying to do it. So far, I know what recovery and rom I'm going to use with all the files downloaded and ready. Though, currently, I am still at the pre-root stage. I have read up things about kingoroot and not sure if I wanted to use it. So I looked around on the forum and wonder if Odin is still a working solution. Reading on the steps and guides, I was wondering if I need to have Kies installed?
Click to expand...
Click to collapse
Kies is not needed as it never helped.
You can depend on odin it is your only saviour when you are in trouble.
I think rooting with kingroot is easy as it is just connecting to your PC and cick the start button.
So just notice me when your ready.
And there is also one good news...?
Tab 2 has got marshmallow.
Zte blade l said:
Kies is not needed as it never helped.
You can depend on odin it is your only saviour when you are in trouble.
I think rooting with kingroot is easy as it is just connecting to your PC and cick the start button.
So just notice me when your ready.
And there is also one good news...��
Tab 2 has got marshmallow.
Click to expand...
Click to collapse
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
rocketfans14 said:
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
Click to expand...
Click to collapse
You first must update your tab to jelly bean bootloader, before trying out newer roms.
Or perhaps flash stock jb firmware with odin
Whatever you choose, both is ok.
http://forum.xda-developers.com/showthread.php?t=2642005
Read here
The first thing you do, is take a nandroid backup, it's very important at every step, unless you are really ready to risk. It's better to have it.
Next Read through the rom threads, clear your mind and your tab too. You must format data.
Stay on twrp 2.8.7.2. Don't go to the latest one yet.
Flash rom, wait, it will boot up.
Every tab behave differently with every rom, sure you are going to face soft reboots, on some roms it will be a lot, on some it will be less. I would suggest you try both LP and kk first.
Remember, it's better to keep this tab updated than to stay on stock. This tab 2 series has a emmc bug and staying on stock or jumping back is a risk too. I have been on kk and lp. They both have kept this tab running great and away from that bug.
billysam said:
You first must update your tab to jelly bean bootloader, before trying out newer roms.
Or perhaps flash stock jb firmware with odin
Whatever you choose, both is ok.
http://forum.xda-developers.com/showthread.php?t=2642005
Read here
The first thing you do, is take a nandroid backup, it's very important at every step, unless you are really ready to risk. It's better to have it.
Next Read through the rom threads, clear your mind and your tab too. You must format data.
Stay on twrp 2.8.7.2. Don't go to the latest one yet.
Flash rom, wait, it will boot up.
Every tab behave differently with every rom, sure you are going to face soft reboots, on some roms it will be a lot, on some it will be less. I would suggest you try both LP and kk first.
Remember, it's better to keep this tab updated than to stay on stock. This tab 2 series has a emmc bug and staying on stock or jumping back is a risk too. I have been on kk and lp. They both have kept this tab running great and away from that bug.
Click to expand...
Click to collapse
Do I have to unroot first? Do you have a link to making a nandroid backup?
Edit: Oh, I looked at the link you included and it said that if I am on stock jb (4.2.2), I can skip the update bootloader part..
When you flashed the new rom, did you do a factory reset (wipe data)?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
rocketfans14 said:
Do I have to unroot first? Do you have a link to making a nandroid backup?
Edit: Oh, I looked at the link you included and it said that if I am on stock jb (4.2.2), I can skip the update bootloader part..
Click to expand...
Click to collapse
Yes, that's what I meant too, if you're on jb already, you are fine. You don't have to unroot. For making a nandroid backup, use twrp recovery, there is an option for backup, select and backup all from there, if you get into bootloop or any other problem, as long as you can get back to recovery, you can restore from there. Most rom comes pre rooted.
rocketfans14 said:
I have rooted the tablet. I did it with odin and twrp with flashing the updatedSuperSU zip folder.
I have tried flashing the CM12.1 rom yesterday but resulted in a boot loop. So for now, I'm just rooted and on stock rom until I or someone can find out what was the problem. I have read about the discussion with marshmallow but it seems to me that the project isn't really stable yet. From what I have researched lately, can I assume there's issue with the p51xx line of tablets? Because I saw many people having problems with p51xx and most people with the other tablets aren't having any.
Click to expand...
Click to collapse
Did you clear dalvik cache in recovery before flashing rom?
Zte blade l said:
Did you clear dalvik cache in recovery before flashing rom?
Click to expand...
Click to collapse
Yes, I cleared the top four options in recovery, and formatted data before flashing.
billysam said:
Yes, that's what I meant too, if you're on jb already, you are fine. You don't have to unroot. For making a nandroid backup, use twrp recovery, there is an option for backup, select and backup all from there, if you get into bootloop or any other problem, as long as you can get back to recovery, you can restore from there. Most rom comes pre rooted.
Click to expand...
Click to collapse
That's what I did. Let me just briefly summarize what I have done:
used odin with twrp
booted into recovery and made back up
cleared dalvik, cache, system, and data, formatted data
flashed update supersu, booted into system and checked root with root checker
rebooted into recovery, cleared dalvik, cache, system, and data, formatted data again
flashed cm12.1 and gapps, rebooted but ran into bootloop at splash screen
rebooted into recovery and restored back up
So I'm rooted and on stock 4.2.2 currently.
champ1919 said:
When you flashed the new rom, did you do a factory reset (wipe data)?
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
Click to expand...
Click to collapse
I did.
Try flashing blisspop or slimLP.
I have a Shield Tablet (post battery fire exchange) and I would like to update it to the newest firmware/os... It is currently rooted, running BitO-Kernel, and stock nvidia rom. I did all the rooting and flashing on this tablet originally, but I never kept it up to date with newer updates. I heard on this forum awhile back that it's not just as simple as flashing a new rom, something about having to flash some other system stuff first or some partition or something. Basically I'm looking for a guide on how to update a Shield Tablet from rooted 5.1.1 to the newest OS version avalible. I tried sreaching the forum, but I couldn't find what I was looking for (maybe I'm not using the right search keyworks).
Agreed, that it is typically best to keep devices updated with the whole OTA update, which include firmware, modems, and whatever other partitions (not always flashed with custom ROMs). Although I'm not sure if there is much changed in those partitions between 5.1.s and 5.2.
That is the original Shield tablet (not the K1) right?
If so, I think you can just download the full OTA zip, and flash in TWRP: https://forum.xda-developers.com/showpost.php?p=72501806&postcount=35
Then root (flash Magisk or SuperSU) right away before rebooting, if you want to keep TWRP. If you don't root, the update will cause TWRP to be replaced with stock recovery.
Another option, if you made a backup of the stock ROM before installing custom ROM (I suggest always doing that) you can restore it, and should get the OTA notification. Then you should be able to just download and update that way. Again, root before rebooting, if you want to retain TWRP.
If all the above fail, you can download the recovery OS, and flash all the components using fastboot, as described in the supplied instructions:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20Tablet%20wifi&tx=$additional,shield
redpoint73 said:
Agreed, that it is typically best to keep devices updated with the whole OTA update, which include firmware, modems, and whatever other partitions (not always flashed with custom ROMs). Although I'm not sure if there is much changed in those partitions between 5.1.s and 5.2.
That is the original Shield tablet (not the K1) right?
If so, I think you can just download the full OTA zip, and flash in TWRP: https://forum.xda-developers.com/showpost.php?p=72501806&postcount=35
Then root (flash Magisk or SuperSU) right away before rebooting, if you want to keep TWRP. If you don't root, the update will cause TWRP to be replaced with stock recovery.
Another option, if you made a backup of the stock ROM before installing custom ROM (I suggest always doing that) you can restore it, and should get the OTA notification. Then you should be able to just download and update that way. Again, root before rebooting, if you want to retain TWRP.
If all the above fail, you can download the recovery OS, and flash all the components using fastboot, as described in the supplied instructions:
https://developer.nvidia.com/gameworksdownload#?search=SHIELD Tablet wifi&tx=$additional,shield
Click to expand...
Click to collapse
Thanks I appreciate the help! Yes it's an original tablet (not the k1). It's currently rooted with the Bit-O kernel running over the stock Nvidia 5.1.1 os (also has twrp on it as well). I'd like to keep root. I'll have to do some more search to see if I can find the old thread where I was told it's more difficult the a simple flash, I remember it was explained fairly clearly, I just can remember exactly what that was lol.
EDIT: found the original post where I was asking about this from last year, the issue revolves around the Staging Blob which I've never worked with before and know nothing about it (usually just ROMs and kernel flashes and occasionally radio images).
https://forum.xda-developers.com/shield-tablet/help/how-update-rooted-shield-tablet-to-t3355436
bluegizmo83 said:
It's currently rooted with the Bit-O kernel running over the stock Nvidia 5.1.1 os (also has twrp on it as well). I'd like to keep root.
Click to expand...
Click to collapse
You won't be able to update the OS and keep root. Which is pretty typical when updating most Android devices (root will be lost). But for the 1st and 2nd options I gave (flashing the OTA zips in TWRP), it's easy to just root the device again. Just have your preferred root zip (Magisk or SuperSU) on the phone when you update. Then after the update (before rebooting to OS) while still in TWRP, just flash the root zip. Then you will be rooted, and TWRP will not be wiped (replaced by stock recovery).
3rd option (flash Recoveyr OS in fastboot), getting root again is a few more steps, but still not that hard. After flashing all the components, reboot and verify everything is working. Then go to fastboot again, flash TWRP. Then boot into TWRP, and flash the root file (Magisk or SuperSU).
For any of the options 1-3, if you want to then flash your custom kernel again after rooting, you are free to do so. I'd probably verify the stock OS is working. Then boot to TWRP, make a backup of the stock kernel & ROM, then flash your desired kernel.
bluegizmo83 said:
I'll have to do some more search to see if I can find the old thread where I was told it's more difficult the a simple flash, I remember it was explained fairly clearly, I just can remember exactly what that was lol.
EDIT: found the original post where I was asking about this from last year, the issue revolves around the Staging Blob which I've never worked with before and know nothing about it (usually just ROMs and kernel flashes and occasionally radio images).
Click to expand...
Click to collapse
On the 3rd option (flash Recovery OS in fastboot), if you go to the link then click the desired version 5.2, it will expand, and you will see Downloads for the Windows or Linux files, and instructions below that. Click on "instructions" and you will see there are steps to extraxt various components, than flash each one individually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
If you do the other methods (flash OTA zip with TWRP) I believe all these components are included, and just flash automatically.
redpoint73 said:
You won't be able to update the OS and keep root. Which is pretty typical when updating most Android devices (root will be lost). But for the 1st and 2nd options I gave (flashing the OTA zips in TWRP), it's easy to just root the device again. Just have your preferred root zip (Magisk or SuperSU) on the phone when you update. Then after the update (before rebooting to OS) while still in TWRP, just flash the root zip. Then you will be rooted, and TWRP will not be wiped (replaced by stock recovery).
3rd option (flash Recoveyr OS in fastboot), getting root again is a few more steps, but still not that hard. After flashing all the components, reboot and verify everything is working. Then go to fastboot again, flash TWRP. Then boot into TWRP, and flash the root file (Magisk or SuperSU).
For any of the options 1-3, if you want to then flash your custom kernel again after rooting, you are free to do so. I'd probably verify the stock OS is working. Then boot to TWRP, make a backup of the stock kernel & ROM, then flash your desired kernel.
On the 3rd option (flash Recovery OS in fastboot), if you go to the link then click the desired version 5.2, it will expand, and you will see Downloads for the Windows or Linux files, and instructions below that. Click on "instructions" and you will see there are steps to extraxt various components, than flash each one individually using fastboot:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash staging blob
If you do the other methods (flash OTA zip with TWRP) I believe all these components are included, and just flash automatically.
Click to expand...
Click to collapse
Oh ok thanks! I'll definitely try to flash that 5.2 OTA zip from twrp and see if that works. After that, I should be able to flash any current update (like 6.0) also, correct? And I assume I need to flash 5.2 first before flashing 6.0 (or whatever the most current shield tablet OTA is), correct?
bluegizmo83 said:
Oh ok thanks! I'll definitely try to flash that 5.2 OTA zip from twrp and see if that works.
Click to expand...
Click to collapse
Pretty sure it's how I updated to 5.2 (then rooted), and probably the easiest of the options. It's been a busy last couple months, so it's all a little blurry!
bluegizmo83 said:
After that, I should be able to flash any current update (like 6.0) also, correct?
Click to expand...
Click to collapse
Correct.
bluegizmo83 said:
And I assume I need to flash 5.2 first before flashing 6.0 (or whatever the most current shield tablet OTA is), correct?
Click to expand...
Click to collapse
Not 100% sure. It's a full OTA zip, not an incremental update. So in those cases (full OTA) it may not need the preceding update installed. But again, I'm not sure.
redpoint73 said:
Pretty sure it's how I updated to 5.2 (then rooted), and probably the easiest of the options. It's been a busy last couple months, so it's all a little blurry!.
Click to expand...
Click to collapse
Ok thanks again, I appreciate all the help! One last question I promise lol. Do I need to wipe anything in twrp before I flash an OTA zip? In the past I've been told wipes are not required for incremental updates (like 5.0 to 5.1 to 5.2) but they are usually recommended for larger os revisions like 5.0 to 6.0, does that still hold true?
bluegizmo83 said:
One last question I promise lol. Do I need to wipe anything in twrp before I flash an OTA zip? In the past I've been told wipes are not required for incremental updates (like 5.0 to 5.1 to 5.2) but they are usually recommended for larger os revisions like 5.0 to 6.0, does that still hold true?
Click to expand...
Click to collapse
I would say that is still true. Don't think you need to wipe anything (except cache and Dalvik - which I usually wipe when flashing anything), and I don't think I did either. Make a TWRP backup, in case anything goes wrong, as well as any other backups of apps, data, etc. (such as Titanium)..
Ask all the questions you like. It's fun to help, although I may not necessarily always know the answer!
redpoint73 said:
I would say that is still true. Don't think you need to wipe anything (except cache and Dalvik - which I usually wipe when flashing anything), and I don't think I did either. Make a TWRP backup, in case anything goes wrong, as well as any other backups of apps, data, etc. (such as Titanium)..
Ask all the questions you like. It's fun to help, although I may not necessarily always know the answer!
Click to expand...
Click to collapse
Ok thanks. I did just think of one more question, its not 100% related to flashing though... On my shield tablet, I have a 128gb SDcard in it, and I use Folder Mount to move all my large apps and games to the SDcard. Do these backup through TWRP if I check every box (I don't think it does cause there isn't a check box to backup the sdcard)? Would titanium backup work better to backup and restore these large apps & games that were moved with Folder Mount?
bluegizmo83 said:
Ok thanks. I did just think of one more question, its not 100% related to flashing though... On my shield tablet, I have a 128gb SDcard in it, and I use Folder Mount to move all my large apps and games to the SDcard. Do these backup through TWRP if I check every box (I don't think it does cause there isn't a check box to backup the sdcard)? Would titanium backup work better to backup and restore these large apps & games that were moved with Folder Mount?
Click to expand...
Click to collapse
You can't backup internal storage or SD card in TWRP.
I don't personally use anything like Folder Mount. I would think as long as the folders are where they are supposed to be, and the data for Folder Mount is preserved/migrated properly, then it will all still work as it did before the update. If you are really paranoid, you can make a copy of the folders on your SD card to your computer as a "backup".
redpoint73 said:
You can't backup internal storage or SD card in TWRP.
I don't personally use anything like Folder Mount. I would think as long as the folders are where they are supposed to be, and the data for Folder Mount is preserved/migrated properly, then it will all still work as it did before the update. If you are really paranoid, you can make a copy of the folders on your SD card to your computer as a "backup".
Click to expand...
Click to collapse
I just noticed on that download link you posted earlier, that Nvidia lists the newest update as 5.2.0, but that is actually Android os version 7.0. Earlier when I said on was on 5.1.1 I meant Android os 5.1.1 (as in Lollipop), not shield os version 5.1 (which is Nougat). Sorry if that wasn't clear in the beginning. Does that effect any of your original advise? Just thought I should double-check that.
bluegizmo83 said:
I just noticed on that download link you posted earlier, that Nvidia lists the newest update as 5.2.0, but that is actually Android os version 7.0. Earlier when I said on was on 5.1.1 I meant Android os 5.1.1 (as in Lollipop), not shield os version 5.1 (which is Nougat). Sorry if that wasn't clear in the beginning. Does that effect any of your original advise? Just thought I should double-check that.
Click to expand...
Click to collapse
I'm not sure if it matters with the OTA. My feeling is, that it won't matter, and it will still install.
My guess is that in the worst case, the OTA fails, and you have to resort to flashing the recovery OS version.