Related
Just got a notification for OTA to 5.0.1. Anyone know if this will break root? And if it will install with CWM custom recovery?
Hello, I tried to install in my WiFi model and rooted and I got and error during the installation, so I'm waiting for the opinion of other users. ?
Sent from my SHIELD Tablet using XDA Free mobile app
I kiddy got it too, I'll wait for the zip file lol.
Ya think it is really better to install from the zip file?
Sent from my SHIELD Tablet using XDA Free mobile app
I'll be the guinea pig
I downloaded the OTA but can't find where is the ota file. Any idea where is it?
Sent from my SHIELD Tablet using XDA Free mobile app
Get an error in cwm . shucks
Does someone can post change log please?
Gilbot said:
Get an error in cwm . shucks
Click to expand...
Click to collapse
Same. My bootloader is locked and tried flashing via cwm and got error. Pls teach me how to update?
Sent from my SHIELD Tablet using XDA Free mobile app
Judge584 said:
Does someone can post change log please?
Click to expand...
Click to collapse
Android Central has the log change. It's bug fixes really.
Also, in this thread a user states that apparently only with the full 5.0.1 can you install it with CWM.
http://forum.xda-developers.com/shi...p-nvidia-shield-tablet-ota-android-5-t2982677
You will lose root and CWM after the reboot but those took about 3 minutes to get back .. easy peasy. I'm now at 5.0.1 on my shield with root and CWM.
Cheers.
Hello aegern,
deletes the full update all the data? can you give me the recovery and root attach files?
Thanks
Gilbot said:
Get an error in cwm . shucks
Click to expand...
Click to collapse
This should help. Let me know if it works:
http://forum.xda-developers.com/shield-tablet/general/5-0-1-ota-rooted-shield-tablets-dl-t2983104
d4m45cuz said:
This should help. Let me know if it works:
http://forum.xda-developers.com/shield-tablet/general/5-0-1-ota-rooted-shield-tablets-dl-t2983104
Click to expand...
Click to collapse
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
GMrMadrigal said:
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
Click to expand...
Click to collapse
So here's what I did:
Download the full OTA then reboot to CWM (assuming your rooted + recovery) and unmount system partition ( I believe all others were unmounted) and then delete system, data, cache partitions respectively. Then flash the OTA zip followed by latest supersu.
Just tested this method and I have a rooted 5.01 32GB LTE US model working flawlessly. Even managed to take out the top spot in Hwbot Prime for the Shield (woops to newb for links I see lol)
l0ud_sil3nc3 said:
So here's what I did:
Download the full OTA then reboot to CWM (assuming your rooted + recovery) and unmount system partition ( I believe all others were unmounted) and then delete system, data, cache partitions respectively. Then flash the OTA zip followed by latest supersu.
Just tested this method and I have a rooted 5.01 32GB LTE US model working flawlessly. Even managed to take out the top spot in Hwbot Prime for the Shield (woops to newb for links I see lol)
Click to expand...
Click to collapse
I really appreciate your advice but I get the same error
-- Installing: /storage/sdacrd1/lte-full-5.0.1.zip
Finding update package...
Opening update package...
Installing update...
This package is for "shieldtablet" device; this is a "ardbeg".
E:Error in /storage/sdacrd1/lte-full-5.0.1.zip
(Status 7)
Installation aborted.
I've tried with a few zip updates through in xda but nothing. I guess is because the CWM recovery image but Im not an expert on this and cant be sure if flashing the stock recovery will let me make the OTA successfully. But neither i have found the stock recovery image
GMrMadrigal said:
:crying: Does not work for me. I tried locking it again, unrooting my tablet and neither with OTA or CWM flash. Any light?
Click to expand...
Click to collapse
GMrMadrigal said:
I really appreciate your advice but I get the same error
-- Installing: /storage/sdacrd1/lte-full-5.0.1.zip
Finding update package...
Opening update package...
Installing update...
This package is for "shieldtablet" device; this is a "ardbeg".
E:Error in /storage/sdacrd1/lte-full-5.0.1.zip
(Status 7)
Installation aborted.
I've tried with a few zip updates through in xda but nothing. I guess is because the CWM recovery image but Im not an expert on this and cant be sure if flashing the stock recovery will let me make the OTA successfully. But neither i have found the stock recovery image
Click to expand...
Click to collapse
Look in this thread: [.zip] Nvidia Shield Tablet OTA Android 5.0.1, first page posted by user SeVIIn.
Use that zip file, no issues with it.
l0ud_sil3nc3 said:
Look in this thread: [.zip] Nvidia Shield Tablet OTA Android 5.0.1, first page posted by user SeVIIn.
Use that zip file, no issues with it.
Click to expand...
Click to collapse
Nice, I'm going to download it, and I'll tell if it work! :fingers-crossed:
GMrMadrigal said:
Nice, I'm going to download it, and I'll tell if it work! :fingers-crossed:
Click to expand...
Click to collapse
So, did it work for you? I've tried the file in both this link and the official update and get the same thing with both. I'm still on KK and I can't install either the 5.0 or the 5.01 updates. I get the same "this is an ardbeg" error with any update I try to flash, and I'm flashing the full files, not the incremental updates. In fact, I have two tablets (both lte) and I updated the first one to 5.0 a week ago, no problem, but the new one I just bought, I can't even though I'm using the same files (cwm and update). I'm stumped.
Bah. nm. I went back and reinstalled the recovery from here again, http://forum.xda-developers.com/shi.../recovery-cwm-recovery-nvidia-shield-t2848064. Flashed 5.01 just fine. Not sure where I got the other recovery.
dgjenkins said:
So, did it work for you? I've tried the file in both this link and the official update and get the same thing with both. I'm still on KK and I can't install either the 5.0 or the 5.01 updates. I get the same "this is an ardbeg" error with any update I try to flash, and I'm flashing the full files, not the incremental updates. In fact, I have two tablets (both lte) and I updated the first one to 5.0 a week ago, no problem, but the new one I just bought, I can't even though I'm using the same files (cwm and update). I'm stumped.
Bah. nm. I went back and reinstalled the recovery from here again, http://forum.xda-developers.com/shi.../recovery-cwm-recovery-nvidia-shield-t2848064. Flashed 5.01 just fine. Not sure where I got the other recovery.
Click to expand...
Click to collapse
Hi dgjenkins, sorry answer so late. So, answering you first, not, it did not work for me. I actually did give up, the bad was that I tried so many ways to do it that I freezed the tablet and did not start again. Well, looking out there, I found this amazing video who saved my tablet of bust it again the wall and start from the original firmware.
https://www.youtube.com/watch?v=GsMo1tPlIFU
I did intal the Minimal ADB and Fastboot
Copy the image files in to the Minimal ADB and Fasboot directory c:\Programs Files (x86)\Minimal ADB and Fastboot
Ope Minimal ADB and Fastboot
-Type: fastboot flash recovery recovery.img
-Type: fastboot flash boot boot.img
-Type: fastboot flash system system.img
-Type: fastboot flash userdata userdata.img
-Type: fastboot flash staging blob
-Type: fastboot flash dtb tegra124-tn8-p1761-1270-a04-e-battery.dtb
And done . I can now install the updates from the stock firmware. Maybe I will root it again once a stable way to root the shield tablet appear out there. :cyclops:
Happy Holidays and Thanks for the interest! :good:
Nvidia updates definitely trump Android ones. These days, Google is in the habit of pretending that a nexus 5 camera bug is worthy of a new Android version (that was KitKat) or that an update is a great place to break functionality (App Ops, also with KitKat). Anything that's not a minor version with updates you know you want... Avoid on a non Nexus unless you have a great reason for it.
Manufacturers besides Google, see, they do this thing I like to call quality control. They generally release an OS that is ready for the hardware and software*. Crazy, right?
* unless that hardware is, say, the pen
So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff
viper2ko said:
So I recieved the notification that the 5.0.2 update was ready to install on my tablet. My tablet is ROOTED but that is all, still stock, I only root to use ad away. I get an error trying to install it OTA. How can I install the update, without having to wipe all my data? Sorry, I am very new to this stuff
Click to expand...
Click to collapse
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.
So if I get this right, OTA breaks also when recovery is stock, but supersu installed, modified hosts and gps.conf file
jshamlet said:
No go on root. Your system partition has to be pristine. (Technically you can add files, but the ones that came with it have to be unchanged) Just undo any changes you have made and unroot and the OTA should work.
Click to expand...
Click to collapse
Only changed I have made are installing ad away
viper2ko said:
Only changed I have made are installing ad away
Click to expand...
Click to collapse
The HOSTS file came with the stock image. It counts, unfortunately. (I'm also an Adaway user)
Modify /system, you don't OTA. Period.
Just download the Nexus image and flash just system.img, not the batch file.
Can I flash the system.img in TWRP or do I need to flash the stock recovery?
And will this upgrade me from 5.0.1 to 5.0.2 without losing anything except for root?
Thanks!
^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.
yosmokinman said:
^You flash the system image with fastboot. Run: fastboot flash system system.img
You'll keep data just have to reflash the su zip in twrp.
Click to expand...
Click to collapse
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.
flyinion said:
Thanks for the info. Just had this problem myself and was trying to figure out what to do. This must be a 5.x problem? I've never had this problem on 4.x as long as I had the stock recovery installed. Just had to re-root after. Guess I'm off to download the factory images since it won't even show an update available after erroring out. It definitely still shows 5.01 as being the version I'm on.
Click to expand...
Click to collapse
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.
magnumlove said:
Just download Scrosler's Factory Stock Rooted Rom 5.0.2 in the Android Development section and install via TWRP over the top of 5.0.1. No need for a fresh install.
Click to expand...
Click to collapse
Oh I wasn't going to do a fresh install (i.e. wiping everything), just flash that system.img or modify the batch file to remove the "-w" flag and just run that. I'm wary of running 3rd party ROMs now after I couldn't play movies through Play Movies that were downloaded to the device instead of streamed. Something to do with copy protection I guess
It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.
Telyx said:
It isn't a "3rd party ROM," just a flashable version of 5.0.2. If you flash using TWRP, just don't have it wipe anything. I flashed his 5.0.1 flashable ROM over 4.4.4 (after updating my bootloader) and didn't lose anything.
Click to expand...
Click to collapse
Assuming this was in reply to me? I'm not worried about losing anything. I've done the whole back it up and wipe between ROMs a ton on my OG Droid and Galaxy Nexus. In this case it's a worry that Play Movies for instance will detect that it is not a stock ROM/image and will disallow playing downloaded versions of movies in the app. I.e. you can download vs. stream for offline playback. I nearly found out the hard way (night before leaving on a vacation) that I couldn't play downloaded versions (it will download but not play them) when I for instance installed AOKP to my Nexus 7. As best I could tell from a bunch of Googling, it's something to do with copy protection.
It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.
Telyx said:
It was, but I didn't know your experience level. I guess what I wanted to say is that scrosler's stock rooted ROM is exactly that; once it's on the tablet it isn't any different from rooting the OTA or factory image. It's just flashable via recovery instead of having to use fastboot or flash-all.bat.
Click to expand...
Click to collapse
Ah ok. Well, I ended up using fastboot to flash the system.img last night and looks like I'm good to go. I tried unrooting (SuperSU remove root function) and changing betterbatterystats to a non-system app first but the OTA still failed. Yeah I learned how to use the basic adb/fastboot stuff when I got my Galaxy Nexus and again with the N7. I figured that way if I totally broke something I'd know how to fix it, and all the fancy tools weren't around when the GNex first came out (at least I don't think they were).
I dirty flashed scrosler's 5.0.1 ROM when I got the 5.0.1 OTA notification, but when the 5.0.2 factory image was posted I fastboot flashed the system.img from that and rerooted. Naturally, less than half a day or so later, scrosler posted his 5.0.2.
So for someone that's not really too experience with fastboot, could someone post a step by step?
Where would I get the system.img?
Check the sticky threads for guides. Read and reread then get started on setting up the Android SDK. Once complete, type in the commands letter for letter.
This update is known as 6.0.1 (MMB29S): https://dl.google.com/dl/android/aosp/shamu-mmb29s-factory-fc7b590e.tgz
Anyone want to confirm that we can still use systemless root for this update?
Xplicit84 said:
Anyone want to confirm that we can still use systemless root for this update?
Click to expand...
Click to collapse
why, whats the point? why wouldnt you be able to use systemless root with it?
simms22 said:
why, whats the point? why wouldnt you be able to use systemless root with it?
Click to expand...
Click to collapse
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.
Xplicit84 said:
Because when I updated to 6.0.1 last month, the method changed 3 times before things got worked out. Just want to make sure it is still good to go or if the method changed again in the past 3 weeks.
Click to expand...
Click to collapse
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out
Everything's fine for me.
FYI, the radio.img and bootloader.img are the same as MMB29K, so they don't need to be flashed. Boot.img and cache.img are the same size, but I'll flash them anyway. System.img is a different size, so it definitely needs to be flashed.
Looks like the kernel is the same.
Sent from my Nexus 6 using Tapatalk
anyone having trouble downloading the new system image from the site?
simms22 said:
thats because it was a brand new method for 6.0, it was just developed and bugs were being worked out
Click to expand...
Click to collapse
While this is true. These security updates are meant to target thing like the root exploits. So while things may still work don't be surprised if it does start needing updates each time Google pushes a security patch. It's a cat and mouse game that will be played until Google manages to lock it down to the point that it is not worth it to root.
maddoggin said:
anyone having trouble downloading the new system image from the site?
Click to expand...
Click to collapse
The factory image download was very slow. Timed out the first time. Second time it worked OK, but still took about 30 minutes.
Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk
tsongwh said:
Can anyone provide a zip image so that we can flash it in twrp?
来自我的 Nexus 6 上的 Tapatalk
Click to expand...
Click to collapse
I second this too. Thank you in advance
i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.
daimonmustdie said:
i am stock rooted. what are the steps to flash this via adb fastboot? do i have to unroot etc? im getting annoyed by the android update notification.
Click to expand...
Click to collapse
Stock w/ systemless root and Elite kernel.
To applying the update I downloaded the factory image from https://developers.google.com/android/nexus/images untar and unzip image-shamu-mmb29s.zip to get at the system.img file. Then did fastboot flash system system.img, just finished booting and and 'upgrading' my apps. It looks like something in boot.img changed too, but everything seems to be running perfectly fine without flashing it; note that I do have a custom kernel installed, so that might have something to do with it.
If you also fastboot flash boot boot.img then you will likely need to go through the root process again to modify the boot.img to allow root to work properly.
Code:
$diff shamu-mmb29k shamu-mmb29s
Binary files shamu-mmb29k/boot.img and shamu-mmb29s/boot.img differ
...
Binary files shamu-mmb29k/recovery.img and shamu-mmb29s/recovery.img differ
Binary files shamu-mmb29k/system.img and shamu-mmb29s/system.img differ
Stock ROM, TWRP
I have followed the instructions and flashed only the system.img..Nexus 6 - Unlocked, Rooted, Stock ROM, TWRP. It appears everything is running well and the Update notification hasn't appeared..this update was constantly appearing in the notification window and was reported as 5.8mb downloaded patch.
Thanks for your help.
The latest April 2018 OTA update Google pushes to my Nexus 6P is only 38.7mb.
Since my phone is rooted, it won't work and I have to download the full factory image, while OTA image being 899mb and smaller than the full image, then TWRP sideload, then re-flash twrp and re-root with Magisk.
My question is, is there any way to download the 38.7mb (assuming it works) and sideload that instead?
Further, is there any way to do the adb and fastboot stuff without a PC (my PC is slow, even in Linux with all the latest update), maybe with another phone or tablet?
Another problem just came up, TWRP can't verify the 899mb OTA image and failed.
I downloaded and flashed the 899mb OTA file twice, both failed.
Anyone has the same problem?
Guess I have to download the full image and extract files and flash.
mm6ff8 said:
Another problem just came up, TWRP can't verify the 899mb OTA image and failed.
I downloaded and flashed the 899mb OTA file twice, both failed.
Anyone has the same problem?
Guess I have to download the full image and extract files and flash.
Click to expand...
Click to collapse
You can't OTA when your using custom recovery. However I've heard if people using flashfire but have never tried. With Google backup doing such a great back up now just clean wipe and start from scratch. We use too just use superXe was completely stock based and updated frequently but the developer is really busy .
While I've never tried this, and you could cause problems with your device (Make a full nandroid!), you could try flashing stock recovery from the full image, then flashing normally from within the OS.
After flash is successful, flash back to TWRP..
Exodusche said:
You can't OTA when your using custom recovery. However I've heard if people using flashfire but have never tried. With Google backup doing such a great back up now just clean wipe and start from scratch. We use too just use superXe was completely stock based and updated frequently but the developer is really busy .
Click to expand...
Click to collapse
I have successfully done TRWP's "adb sideload" March 2018 OTA image .
But this April 2018 OTA just didn't work.
Wiltron said:
While I've never tried this, and you could cause problems with your device (Make a full nandroid!), you could try flashing stock recovery from the full image, then flashing normally from within the OS.
After flash is successful, flash back to TWRP..
Click to expand...
Click to collapse
Most, if not all, rooted Nexus manual update tutorials tell us to flash recovery stock recovery image, then flash custom recovery.
But I don't see why, and I've almost always skip this step without any problem, since Nexus 4.
But you're definitely right about making a full nandroid part.
mm6ff8 said:
I have successfully done TRWP's "adb sideload" March 2018 OTA image .
But this April 2018 OTA just didn't work.
Click to expand...
Click to collapse
That's great glad you got it sorted. And even better news SuperXe was updated for April! ?
I have UB and rooted with magisk 20.1. I rooted the October build by patching the boot image using magisk. I try to flash the new November stock image and it fails. It says
Writing boot
Failed (failed to write to partition Not found)
I think it may be connected to booting into slot a or b. Maybe?
Can anybody help?
You already took the November OTA or are you still on October?
ctfrommn said:
You already took the November OTA or are you still on October?
Click to expand...
Click to collapse
I'm on October trying to flash November
Pretty sure you cant flash the boot image alone. I always flash the stock boot for the build Im currently on then take the OTA. I think there is a new bootloader for November. Not 100% on that though.
I'm just trying to flash the full factory November stock image. I downloaded it, unzip it, plug in the phone in fastboot and double click the run me bat file.
This has always been fine before but I am new to pixel 3a and have only done this once before, on October build. But I came from an original pixel so I've spent 2 years updating that in this way.
I can't work out why the flash is failing.
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
I've tried flashing October factory image and get the exact same result. Not sure what else to try.
ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Sorry just reread your post. Will try and reflash boot IMG. I do that with fastboot flash boot.img?
Thanks
Yes.... fastboot flash boot boot.img
ctfrommn said:
Yes.... fastboot flash boot boot.img
Click to expand...
Click to collapse
Have tried reflashing boot.img and still won't update ota and same result trying to flash factory image. Any other ideas? And thanks very much for your help
ctfrommn said:
Try flashing the stock October boot.img then try updating. Ive never been successful flashing an OTA or factory image over a patched boot.
Click to expand...
Click to collapse
Do I need to flash boot.img to both slots a and b? If so how do I do that?
I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.
ctfrommn said:
I only ever flash the one in use.
Just fastboot flash boot boot.img is all you need.
Your can also always just clean flash the OTA. Just download it, factory reset, adb sideload the OTA in recovery.
I've done that a few times now.
Click to expand...
Click to collapse
Thanks. Will try things tomorrow. It's late here in London. But I can't get a twrp.img to work. It doesn't seem to mount the system and I can't flash anything. Have you got twrp to work? I'll come back to you in about 18hrs if that's ok?
TWRP doesn't work with Q. Just use stock recovery to sideload.
ctfrommn said:
TWRP doesn't work with Q. Just use stock recovery to sideload.
Click to expand...
Click to collapse
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
Yes, OTA and factory images are essentially the same thing just packaged differently.
And the easiest way to reroot is to just download and repatch the new stock image, or flash a custom pre patched kernel.
Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
The OTA zip is packaged differently and does not include a boot.img file that we can use. (I'm sure it must be in there somewhere, but not in a usable form). Therefore you must download the "Factory Image" from Google. Unzip it, open it where you will find another zip file inside. Open that second zip file and you will find the boot.img file there. Move that boot.img file to your phone so that Magisk can access it and to modify it.
https://developers.google.com/android/images
Horgar said:
Ok, will try when I get home from work. Does the OTA update contain a boot.img? Is that what I need to patch to root again?
Thanks very much
Click to expand...
Click to collapse
FYI here are the steps I took to update my rooted 3a this morning:
1. in Magisk Manager select Uninstall and select restore images (I did this because I kept getting a 'installation error' on the OTA page)
2. Like an idiot I rebooted my phone, do not reboot! So I had to reinstall magisk
2a. copy the boot.img of Oct to my phone to have it patched by magisk
2b. fastboot flash boot boot_patched.img
3. the OTA downloaded while I was on the stock boot.img so I just followed the magisk instructions to install the OTA in the other partition
Next month I'll just jump from step 1 to 3 and carry on being rooted.
The simplest way to update when youre rooted is to......
Reflash the stock boot from the current build youre on
Take the OTA directly on the phone
Download stock image from new build and move it to phone
Patch with Magisk and move to your PC
Fastboot flash boot boot.img
Ive done this for the last 3 updates and it works perfectly every time......I obviously substitute my kernel for the patched boot but the process is the same. I find this far simpler than messing with Magisk
Thanks for all the suggestions but I still cannot update.
I have tried restoring boot.img
data reset from recovery
relocking bl - ota fails
Unlocking bl again - won't flash using ADB
There is no problem with the phone being recognised on ADB, the flash Just fails as the screen shot in my opening post. I'm thinking it may be connected to needing to flash to the inactive slot.
Anyone got any ideas?