Hi everyone,
I'm on custom recovery TWRP and everytime i download the OTA 1.2 and try to flash the tablet goes on the custom recovery but doen't flash the update.
Probably because of the custom recovery.
Is there any way to manually flash the 1.2 update?
Thanks
You can flash the stock recovery, ensure all the apps you've frozen are unfrozen (this mattered when the 1.1 incremental was released - checksum matches require all apps present in the previous build to be "visible"), and then apply the update.
Someone else may have a work-around.
There are no fully working custom recoveries for the Nvidia Shield Tablet so far. I would suggest staying on the Stock recovery until they are working correctly, just my opinion.
Related
My device:
- TF300
- Android 4.2.2. / CM10.1 (10.1-20130621-nightly-tf300t)
- WW_epad-10.4.2.9-20120809 (= 4.1 bootloader version)
- TWRP 2.6 recovery (for bootloader v4.1)
My aim is to update to CM10.2, therefore I need a bootloader version 4.2. I downloaded the latest firmware from the asus-website (TF300T-WW_epad-10_6_1_27_5-UpdateLauncher.zip) and put it on /sdcard.
But I'm in doubt:
- Is the asus firmwire described above the best way to upgrade my bootloader? And can I use TWRP to install this zip?
- If so, do I need to change the TWRP version to 2.6 ready for -4.2 (teamw.in/project/twrp2/97) not at all, before or after I installed the new bootloader?
I know bootloader/recovery issues can easily brick a TF300, so to be sure I ask. Thanks in advance!
Found this thread:
Quote:
Originally Posted by Nschneider7 View Post
Nope missed that and was just reading about it. Can I just flash the "TF300T-US_epad-10_6_1_27_1-UpdateLauncher" zip in TWRP? Then from there flash the new TWRP and then install CM? Or do I have to go back and let it upgrade to that point?
I flashed the blob via fastboot. Then flashed recovery via fast boot. Then cm10.2 from recovery. I was on old June build of 10.1 and 4.1 bootloader same as you. Be safe fastboot flash follow guide in q and a section
Sent from inside my mkv.
Same question, but not exactly answered: can you do this without a cable connection with your pc?
X10i/3011 said:
Found this thread:
Quote:
Originally Posted by Nschneider7 View Post
Nope missed that and was just reading about it. Can I just flash the "TF300T-US_epad-10_6_1_27_1-UpdateLauncher" zip in TWRP? Then from there flash the new TWRP and then install CM? Or do I have to go back and let it upgrade to that point?
I flashed the blob via fastboot. Then flashed recovery via fast boot. Then cm10.2 from recovery. I was on old June build of 10.1 and 4.1 bootloader same as you. Be safe fastboot flash follow guide in q and a section
Sent from inside my mkv.
Same question, but not exactly answered: can you do this without a cable connection with your pc?
Click to expand...
Click to collapse
Honestly, I'd rather be safe than sorry when upgrading bootloaders. So I would always suggest using the cable connection because it is less likely to fail. You probably could get away without using it to flash stock, but you wouldn't be able to flash TWRP without fastboot, and then couldn't flash a custom ROM. But everything feels safer once you have Nvflash backups.
X10i/3011 said:
My device:
- TF300
- Android 4.2.2. / CM10.1 (10.1-20130621-nightly-tf300t)
- WW_epad-10.4.2.9-20120809 (= 4.1 bootloader version)
- TWRP 2.6 recovery (for bootloader v4.1)
My aim is to update to CM10.2, therefore I need a bootloader version 4.2. I downloaded the latest firmware from the asus-website (TF300T-WW_epad-10_6_1_27_5-UpdateLauncher.zip) and put it on /sdcard.
But I'm in doubt:
- Is the asus firmwire described above the best way to upgrade my bootloader? And can I use TWRP to install this zip?
- If so, do I need to change the TWRP version to 2.6 ready for -4.2 (teamw.in/project/twrp2/97) not at all, before or after I installed the new bootloader?
I know bootloader/recovery issues can easily brick a TF300, so to be sure I ask. Thanks in advance!
Click to expand...
Click to collapse
I was in the same situation as you not so long ago. Was on 4.1.1 with TWRP 2.6.3.0 JB installed. Asked myself these questions repeatedly. I updated via fastboot to the staging partition using the blob within the latested ASUS firmware zip file. The blob file contains, bootloader, recovery, system and boot. This means your are essentially returning to stock everything upon flashing. This was a huge sigh of relief as I didn't want to brick my device because of the same concerns you have. So I flashed via fastboot to 10.6.2.10 then flashed to TWRP 2.5.0 4.2 as 2.6.3.0 didn't work for me for some reason. I heard a number of people say that 2.6.3.0 4.2 is buggy and suggested to stay with 2.5.0 in which I would recommend from experience. Then flash your custom firmware.
Pretty lost by now. I am still (sick of it) on an unlocked Asus stock 4.2.1 with TWRP 2.5. My intention is to change the ROM but was considering CM 11 which I understand does require TWRP 2.6.X at least. I was hoping for a fix for installing navflash on post JB but I believe does not possible so anything that means touching the bootloader makes me very concern.
I was wondering:
- Can I flash TWRP 2.6 (4.2 img file i beleive) directly from my already installes TWRP 2.5 bootloader and then install CM 11? or do I need fastboot process again?
- Is CM 11 worth on the TF300? I just need some stability and reasonable speed after having so many problems with the stock rom.
Thanks.
luison said:
Pretty lost by now. I am still (sick of it) on an unlocked Asus stock 4.2.1 with TWRP 2.5. My intention is to change the ROM but was considering CM 11 which I understand does require TWRP 2.6.X at least. I was hoping for a fix for installing navflash on post JB but I believe does not possible so anything that means touching the bootloader makes me very concern.
I was wondering:
- Can I flash TWRP 2.6 (4.2 img file i beleive) directly from my already installes TWRP 2.5 bootloader and then install CM 11? or do I need fastboot process again?
- Is CM 11 worth on the TF300? I just need some stability and reasonable speed after having so many problems with the stock rom.
Thanks.
Click to expand...
Click to collapse
Yes, CM11 requires TWRP 2.6.3.1.
You can install NvFlash on a JellyBean Bootloader, link and guide is in my signature.
If you bootloader is above 10.6.1.8, you can just flash the TWRP 2.6.3.1 and then reboot and then flash CM11 + gapps.
I think it is super smooth with the OC Kernel.
I have been trying to get my phone to update following the directions for the past year almost and have had no luck.
EDIT*: I am trying to do the OTA update that i am being prompted to do (9.16.6)
I am on:
Android Version 4.1.1
System Verison 9.1.41XT926
Bootloader: unlocked
Safestrap
I am trying to get to Android 4.3 but when I go to voodoo OTA rootkeeper and temp unroot then download and try and install the update my phone reboots like its starting the install but then shows the android the with the ! coming out of him then it restarts and upon restart it tells me that the update failed.
What am I doing wrong and how can I get these updates to work!
Thanks,
Tyler Hegamyer
There isn't an official 4.3. And if your trying to flash a custom 4.3 you need to be unlocked running a custom recovery.
Sent from my PACMAN MATRIX HD MAXX
deeje00 said:
There isn't an official 4.3. And if your trying to flash a custom 4.3 you need to be unlocked running a custom recovery.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
I currently have my bootloader unlocked and am running SafeStrap. What do i need to do from there, do i simpily just flash a new rom on a new rom slot in SS and ill be at 4.3?
TylerHegamyer said:
I currently have my bootloader unlocked and am running SafeStrap. What do i need to do from there, do i simpily just flash a new rom on a new rom slot in SS and ill be at 4.3?
Click to expand...
Click to collapse
i would suggest abandoning ss unless the rom you want is only supported through ss (rare but possible).
i would:
-disable ss
-use the 1.33 utility in the dev forum to update and return to the latest stock
-use the same utility to root
-use the same utility to flash a custom recovery
--boot into recovery and witpe data/cache/"data-media(cwm recovery specific)" to be sure everything is gone
-choose the rom of your chice from the dev forum and flash in recovery as directed by the rom's dev.
Don't use safe strap. Delete the partion and uninstall it. Use cwm or twrp. And might want to change the title then your not accepting a ota your flashing a custom rom.
Sent from my PACMAN MATRIX HD MAXX
I'm also having some troubles. Trying to apply the new update (rooted with stock 4.1.2) keeps resulting in "signature verification failed" in CWM. I have to then wipe the cache so it doesn't keep trying to reboot and apply the update. I've also tried unfreezing all the bloat in TitaniumBackup but got the same results.
Does anyone know a solution for this?
EDIT: I've also tried running OTA rootkeeper app and it still failed.
gf1723 said:
I'm also having some troubles. Trying to apply the new update (rooted with stock 4.1.2) keeps resulting in "signature verification failed" in CWM. I have to then wipe the cache so it doesn't keep trying to reboot and apply the update. I've also tried unfreezing all the bloat in TitaniumBackup but got the same results.
Does anyone know a solution for this?
EDIT: I've also tried running OTA rootkeeper app and it still failed.
Click to expand...
Click to collapse
the ota will not work through a custom recovery such as cwm, you need to put the stock recovery back on.
I was on a custom build of android 6 and had twrp and then I got an update and installed it. Now I have lost TWRP... Is that even possible? Also when in recovery it says can't mount sdcard!
Was it a custom ROM based on stock 6.0? If it is, it's possible that the update was pushed to the phone because Google sees the phone as running a stock ROM and only a stock recovery can install a stock recovery.
What I don't get is how and why users running custom roms receive and accept stock OTA notification updates.
If you had twrp installed, then the OTA would not install - it would fail.
So I've been trying to update my Shield LTE ROW since this Friday from the stock based rom LL (version 3.1.1) to the MM-based rom (version 4.2) and spend a dozen of hours failing to update :crying:
When I install a MM-based rom the shield boots and the nvidia logo shows a few seconds and then the screen goes black. When the tablet is attached to my pc I noticed that the tablet is not turned off but booted in APX-mode.
These are the things I've tried:
Installing the recovery image 4.2 (fails)
Installing the recovery image 4.1 (fails)
Installing the recovery image 4.0.1 (fails)
Installing the recovery image 3.1.1 (works)
Installing several full and incremental OTA updates to 4.x (fails)
Installing CM 13.0 (fails)
Installing carbon 5.1.1 (works)
Followed the guides mentioned in topics: http://forum.xda-developers.com/shield-tablet/help/unable-to-update-to-marshmallow-rom-t3444124 and http://forum.xda-developers.com/shield-tablet/general/unofficial-update-original-shield-t3281541 (fails)
I've tried a lot of things, but now I'm out of ideas.
Has anyone a explanation why MM-based roms don't want to boot on my tablet? And has the knowledge to fix this?
All feedback is welcome and appreciated.
You are currently able to flash and boot with 3.1.1 or stuck in apx mode?
I'm able to flash and boot with 3.1.1. Only MM-based roms are stuck in apx mode when booting.
You are probably on the Lollipop boatloader still. With that bootloader MM based roms don't work. Flash the latest stock from here, root it with cf-autoroot, flash twrp and MM based roms should work.
Thanks for your advice, I'll try it this weekend.
Just a quick question, why do I need to root and flash twrp? Shouldn't it work if I only flash the latest stock?
My tablet currently has TWRP (latest version from the StockOTA tutorial on the forums) installed as well as a custom rom (CyanogenMod) installed on to the tablet. I'm looking to restore Stock or an optimized Stock rom onto the kill switch wifi K1 tablet, but the problem is I can't find the latest available OTA download? Is it the Recovery OS on NVIDIA's site?
Are these the right steps to have me running the proper setup?
Boot TWRP Recovery
Flash NVIDIA SHIELD Tablet K1 Recovery OS Image (5.1.0)
Flash TWRP Custom Recovery (Supposedly this gets erased in the process from what I've read on the forums)
Flash 'nomoreota.zip'
Flash 'SuperSU' from the stockOTA thread
Delete some sort of (Nvidia or Stock)OTA.apk file in the system partition
If anyone has any suggestions or tips, please help if you don't mind. I've read through a couple threads here, and honestly, I'm pretty lost...I just think that my current rom is lacking in performance, but I don't want the device to brick.