Related
Here is the deal. Got my wifi only xoom (USA) when it was first released. Rooted shortly thereafter....one click method. Installed the tiamat 2.6.36.3 kernel. This prevented me from updating from android 3.0.1...which I'm still using. I didn't care until recently. My xoom is starting to act weird. Now xoom says I'm not rooted. Long story short. In the most simple terms (not good at this stuff). How can I catch up to the lastest version of android which I believe is 3.2? Thanks in advance.
xhuck1 said:
Here is the deal. Got my wifi only xoom (USA) when it was first released. Rooted shortly thereafter....one click method. Installed the tiamat 2.6.36.3 kernel. This prevented me from updating from android 3.0.1...which I'm still using. I didn't care until recently. My xoom is starting to act weird. Now xoom says I'm not rooted. Long story short. In the most simple terms (not good at this stuff). How can I catch up to the lastest version of android which I believe is 3.2? Thanks in advance.
Click to expand...
Click to collapse
Maybe there's an easier way, but you could go back to stock -- fastboot flash stock wifi images from moto dev (no need to relock, though) and let it OTA update to at least three-point-two. Then you can install a custom CWM recovery and flash a rom or kernel.
http://forum.xda-developers.com/showthread.php?t=1242524
Tried this?
Sorry, but I wouldn't recommend that. People are having trouble with it breaking their wifi.
okantomi said:
Maybe there's an easier way, but you could go back to stock -- fastboot flash stock wifi images from moto dev (no need to relock, though) and let it OTA update to at least three-point-two. Then you can install a custom CWM recovery and flash a rom or kernel.
Click to expand...
Click to collapse
I don't know how to "fastboot flash stock images" how do I do that?
xhuck1 said:
I don't know how to "fastboot flash stock images" how do I do that?
Click to expand...
Click to collapse
Do you have CWM recovery installed and have the use of your sdcard? If so, what version do you have? You actually may be able to flash the Tiamat Moray Rom which is the latest version and should give you the update. But you need the most recent solarnz cwm recovery R4c and you will need to do a wipe data/factory reset in recovery before flashing the rom from your external micro sdcard.
I can get into recovery but after that then to android with red exclamation or usb fastboot screen or fdr screen cold boot. Once I get to red x andy I can go no further. Tried all combo of button pushes and will not go to blue menu for clear cache partition fdr or re start. I am trying to clean cache . It just sits at Andy then after about 5 Min's tab reboots by itself. Have tried about 6 times same thing happens each time, Any idea what is happening or what I am doing wrong or is recovery clean cache partition gone? Thanks
Other wise JB install went smooth no problems and tab is working well . seems smoother . Also kept root with voodoo.
Same here...
I had this same issuethis once, after update with the same intention, was considering either clear cache or to do a full wipe from that level as opposed to doing it through settings. Almost had a stroke u I saw the animated android with the famous (or rather infamous red triangle) Ended up using the one in Backup and Restore in system settings. Think I will try this again, since this concerns me. Anyone else seeing this? If recovery is broken in JB, we have another wait on out hands. Sigh
ditto, starting to see a trend...
Same here, I've had no luck getting past the initial stock recovery screen. Not good.
When you flash OTA update you lose custom recovery.
i have custom recovery installed on JB but it is useless. nothing wants to mount.
ultramegaman963 said:
i have custom recovery installed on JB but it is useless. nothing wants to mount.
Click to expand...
Click to collapse
Same here. Seems as though mount points changed and I can't seem to get adb in twrp...
What is different?
cmdrdredd said:
When you flash OTA update you lose custom recovery.
Click to expand...
Click to collapse
I am using Asus stock recovery. When I got tablet it was on .22 rooted tab everything ok. got ota for .26 kept root all ok still could get into recovery got .30 ota kept root again with voodoo. everything o k got into recovery wiped cache no problem. got JB ota everything ok tried to get into recovery and my above post happened? I am confused as to how jb is now custom recovery versus all other otas. What has turned from stock recovery to custom recovery
Tomv5314 said:
I am using Asus stock recovery. When I got tablet it was on .22 rooted tab everything ok. got ota for .26 kept root all ok still could get into recovery got .30 ota kept root again with voodoo. everything o k got into recovery wiped cache no problem. got JB ota everything ok tried to get into recovery and my above post happened? I am confused as to how jb is now custom recovery versus all other otas. What has turned from stock recovery to custom recovery
Click to expand...
Click to collapse
I kept root with OTA Root Keeper. So I was able to reflash TWRP from Goomanager. But anyway it cannot mount either the internal storage nor the microSD card. There seems to be no working recovery for JB, yet.
FreakyPriest said:
I kept root with OTA Root Keeper. So I was able to reflash TWRP from Goomanager. But anyway it cannot mount either the internal storage nor the microSD card. There seems to be no working recovery for JB, yet.
Click to expand...
Click to collapse
That's not entirely accurate... if you mount /system in twrp, you will see externalSD is mounted instead. Kind of goofy. Messed me up good, since I expected to install supersu through recovery. Now I have no root and no useful recovery! Anyone know the mount point cure?
Sent from my ASUS Transformer Pad TF700T using xda premium
still nothing
xfinrodx said:
That's not entirely accurate... if you mount /system in twrp, you will see externalSD is mounted instead. Kind of goofy. Messed me up good, since I expected to install supersu through recovery. Now I have no root and no useful recovery! Anyone know the mount point cure?
Sent from my ASUS Transformer Pad TF700T using xda premium
Click to expand...
Click to collapse
Has anyone been able to get past red exclamation point andy in recovery mode yet?
http://forum.xda-developers.com/showthread.php?t=1886901
This recovery works with the JB Kernel. Flash it using fastboot.
FineWolf said:
http://forum.xda-developers.com/showthread.php?t=1886901
This recovery works with the JB Kernel. Flash it using fastboot.
Click to expand...
Click to collapse
I like a few others was stuck at the infamous red triangle with no way to get into TWRP. Lost custom recovery. Did the above mentioned in fastboot and was able to flash CWM and then was able to flash Supersu via CWM. Got me out of a jam, unfortunately missed the opportunity to NVFLASH on .26, had already upgaded to .30
merge thread?
amaury48 said:
I like a few others was stuck at the infamous red triangle with no way to get into TWRP. Lost custom recovery. Did the above mentioned in fastboot and was able to flash CWM and then was able to flash Supersu via CWM. Got me out of a jam, unfortunately missed the opportunity to NVFLASH on .26, had already upgaded to .30
Click to expand...
Click to collapse
Could one of the moderators merge this thread with Red triangle in locked stock recovery ? They are both concerning the same thing thanks Tom
Hi guys,
My tablet is rooted (and back to fully stock ROM from Acer's website). I updated OTA just a moment ago, and I was totally shocked to see the message "Booting kernal recovery image - Recovery verified failed..."
I tried rebooting, fastbooting,....they all don't work. How should I move on? What can be done now?
Please do help me. I need the tablet, and never knew such a situation could arise.
Thanks!
Sounds like your device's bootloader is locked again. Just perform a fastboot oem unlock and see whether that fixes your problem. Worked for me.
/edit: Which, of course, assumes you're able to get into fastboot. You should be able to get in using adb... what do you mean by "they all don't work"?
got the same problem. how do you get into fastboot again?
Liquidator said:
Sounds like your device's bootloader is locked again. Just perform a fastboot oem unlock and see whether that fixes your problem. Worked for me.
/edit: Which, of course, assumes you're able to get into fastboot. You should be able to get in using adb... what do you mean by "they all don't work"?
Click to expand...
Click to collapse
I assume yes, it is locked since I went back to a fully Stock ROM (which includes the locked bootloader?). But what has a bootloader got to do with an OTA update?
What I mean by they all don't work is that, even when I try shutting down, rebooting or enter stock recovery using the volume keys + power button, nothing works. Absolutely nothing! The screen just stays there.
I then thought, let the battery run down and maybe I can enter stock recovery and flash the zip for the stock ROM again from my SD card, but this doesn't work. The tablet just boots again to that same screen, with a message saying wiping off update cache and something to do with cdm.
I fear my device is gone. If anyone can lead me to getting back my device up and running, as a small token of appreciation, I will provide you with either $10 via PayPal or a $10 Google Play Gift Card code. This is really important for me, and I can't seem to find any help on this matter on the Internet.
I tried to update to JB, by flashing a stock rom through CWM. But then I try to get into the recovery I get hte same message. For me, if i dont try to get into the recovery it repeats an animation of the Acer logo and it never ends. I believe ill have to give it to the acer support. I also cant get into the stock recovery, so we pretty much have the same problem.
Temporeiches said:
I tried to update to JB, by flashing a stock rom through CWM. But then I try to get into the recovery I get hte same message. For me, if i dont try to get into the recovery it repeats an animation of the Acer logo and it never ends. I believe ill have to give it to the acer support. I also cant get into the stock recovery, so we pretty much have the same problem.
Click to expand...
Click to collapse
No, we don't have a same problem. I don't have CWM on my device, and I am doing an OTA. I can do absolutely NOTHING other than stare at the error message in red ink and the static Acer logo.
Okay sorry. Just want to tell you that I flashed the stock rom and so I lost CWM. If i find a way to fix mine ill tell you and it might help you.
As an update, after letting the tablets battery drain out and then charging it back up, the message I am seeing now is a little longer:
Erasing cache before SD update...
SD Update cmd: recovery
--Update_package=sdcard:update.zip
Booting recovery kernal image
Recovery verified failed...
PS: If anyone can make sense of this message, please tell me.
If I recall correctly, the stock recovery has no user interface whatsoever. All it does is offer to flash a signed update.zip from the external SD card.
I have/had CWM installed, and got the "Recovery verified failed..." message after flashing JB as well. Thing is, it appears Acer is not only flashing the system, but also a new bootloader (which explains the new key-press combos necessary to get into recovery). Why it's not working for you on a stock device I am unable to tell, but something may have gone wrong during your update.
So, suggestion: Place the update.zip from Acer on a microSD and see what happens. With any luck, it'll just flash the system contained within the zip again and it'll work.
Liquidator said:
If I recall correctly, the stock recovery has no user interface whatsoever. All it does is offer to flash a signed update.zip from the external SD card.
I have/had CWM installed, and got the "Recovery verified failed..." message after flashing JB as well. Thing is, it appears Acer is not only flashing the system, but also a new bootloader (which explains the new key-press combos necessary to get into recovery). Why it's not working for you on a stock device I am unable to tell, but something may have gone wrong during your update.
So, suggestion: Place the update.zip from Acer on a microSD and see what happens. With any luck, it'll just flash the system contained within the zip again and it'll work.
Click to expand...
Click to collapse
So how do I get this latest firmware? I can't find on acers website.
himmatsj said:
So how do I get this latest firmware? I can't find on acers website.
Click to expand...
Click to collapse
http://global-download.acer.com/Step5.aspx?Step1=Tablet&Step2=ICONIA%20TAB&Step3=A510&BC=Acer&SC=&LC=en&OS=a09&FS=O02&Category=OS
Change the Language and download the largest file (thats stock ICS) best is the RV28.RC02.WW.GEN1 so later you can retry an update
Temporeiches said:
http://global-download.acer.com/Step5.aspx?Step1=Tablet&Step2=ICONIA%20TAB&Step3=A510&BC=Acer&SC=&LC=en&OS=a09&FS=O02&Category=OS
Change the Language and download the largest file (thats stock ICS) best is the RV28.RC02.WW.GEN1 so later you can retry an update
Click to expand...
Click to collapse
Did the update fail because I already had the previous Acer firmware version as update.zip on my ext sd card? The tab is friggin useless as things stand!!
himmatsj said:
Did the update fail because I already had the previous Acer firmware version as update.zip on my ext sd card? The tab is friggin useless as things stand!!
Click to expand...
Click to collapse
Try this:
Here's how to get into fastboot (bootloader) manually:
Turn off your tablet
Hold the Volume Down (**) button and press the Power button
As soon as the tablet vibrates, let go of only the Power button (keep the Volume Down (**) button pressed) and immediately start switching the Screen Rotation Lock slider back and forth.
If this works continue.Connect your device to PC. Open your device manager look for fastboot under other devices and right click on it and select update driver. Then click browse my computer for driver software and locate the folder i could send by mail, just ask me. Click Next, and it might say it is a threat, but click continue (its safe as I edited it myself) and let it install. Next download http://forum.xda-developers.com/showthread.php?t=1661324 and use it to unlock bootloader. Next follow instructions on http://forum.xda-developers.com/showthread.php?t=1866378 Then place a ROM from NoThrills on an external sdcard, and insert it into the tablet. If the tablet is shut down get into CWM through the key combination for ICS bootloader power and ** sound button and for JB bootloader
* PowerON+Vol-
* At the first vibration release PowerOn, keeping Vol- pressed
* At the second vibration release Vol- and press Vol+
Next flash the rom from external sdcard and reboot. Now things should work.
Guys, can anyone help me understand, why when I do an OTA on a fully stock ROM (no bootloader unlocked, no custom recovery, no custom ROM and no root), do I get the message I mention earlier? (that is: Booting recovery kernel image, Recovery verified failed...)
Mind you, I did go to a custom ROM once, which was No Thrills A700 Fraken ROM for the A510. Could that be an issue here?
Please, just help me understand why I am continuously getting this error when I do an OTA. If you can successfully explain to me, I owe you $10 (PayPal or Google Play Gift Code).
Thanks!
PS: I am not looking for a solution (don't tell me flash this and that, I've done all that). I am merely looking for an explanantion as to why the above happens.
himmatsj said:
Guys, can anyone help me understand, why when I do an OTA on a fully stock ROM (no bootloader unlocked, no custom recovery, no custom ROM and no root), do I get the message I mention earlier? (that is: Booting recovery kernel image, Recovery verified failed...)
Mind you, I did go to a custom ROM once, which was No Thrills A700 Fraken ROM for the A510. Could that be an issue here?
Please, just help me understand why I am continuously getting this error when I do an OTA. If you can successfully explain to me, I owe you $10 (PayPal or Google Play Gift Code).
Thanks!
PS: I am not looking for a solution (don't tell me flash this and that, I've done all that). I am merely looking for an explanantion as to why the above happens.
Click to expand...
Click to collapse
it likely happend due to you rooting and flashing a non stock kernel.
when you apply the update off acers website after having it cwm and a customer rom i don't believe it will replace the recovery properly.
this is becasue the files on acers sites are updates and not full roms.
this is the reason why i did not do it to mine.
don't quote me on it but i had a similar issue with an old phone and ended up stuck on customer roms after that.
malos1984 said:
it likely happend due to you rooting and flashing a non stock kernel.
when you apply the update off acers website after having it cwm and a customer rom i don't believe it will replace the recovery properly.
this is becasue the files on acers sites are updates and not full roms.
this is the reason why i did not do it to mine.
don't quote me on it but i had a similar issue with an old phone and ended up stuck on customer roms after that.
Click to expand...
Click to collapse
You mean when I flashed the A700 Franken ROM by NoThrills, that had a non-stock kernel?
If so, what can I do to get back stock kernel on my tablet? There has to be some way, right?
PS: I flashed the official files from Acer via the update.zip file from their website. From here: http://forum.xda-developers.com/showthread.php?t=1897791
PSS: I checked, and I *think* you are wrong because by flashing the files from Acer's website I am back to the stock kernel. Version number: 2.6.39.4+ (Correct me if I am wrong to assume as such)
himmatsj said:
You mean when I flashed the A700 Franken ROM by NoThrills, that had a non-stock kernel?
If so, what can I do to get back stock kernel on my tablet? There has to be some way, right?
PS: I flashed the official files from Acer via the update.zip file from their website. From here: http://forum.xda-developers.com/showthread.php?t=1897791
PSS: I checked, and I *think* you are wrong because by flashing the files from Acer's website I am back to the stock kernel. Version number: 2.6.39.4+ (Correct me if I am wrong to assume as such)
Click to expand...
Click to collapse
yes but i don't think those update.zip's restore the recovery partitions correctly. They seem to only restore the stock rom and nothing else?
Nothrills may be able to clarify that though. i don't know too much about how these roms work.
malos1984 said:
yes but i don't think those update.zip's restore the recovery partitions correctly. They seem to only restore the stock rom and nothing else?
Nothrills may be able to clarify that though. i don't know too much about how these roms work.
Click to expand...
Click to collapse
Yeah, I hope someone who is directly involved in these things like NoThrills can come and enlighten us.
Thread moved to Q&A
MD
Problem SOLVED!
Hi guys,
For all those having the "recovery verification failed" error while trying to do OTA, I know the fix!
The key is, you need to restore stock recovery manually. There's a zip file of the stock recovery here (at the bottom of the first post). Just restore stock recovery as per usual.
Steps to follow in brief:
1) Install stock recovery manually from HERE
2) If your's isn't the stock Acer ROM, download the correct ICS version for your region from HERE (place it as update.zip and follow steps as per normal to flash)
3) Go to settings>apps>all apps>systemupdater, and then clear data/cache.
4) Reboot tablet and you should get an OTA notification.
5) You're done!
Hi, I unlocked my TF300T sotck ICS 4.0.3 with the Asus app, I flashed CWM and the root_signed thingy without a problem. I then did a data wipe, cache and dalvik wipe and flashed CM10 stable build for TF300T and the Gapps zip. I reboot and it's stuck on ASUS screen. I'm currently doing a restore of the "nandroid". Will this restore my tablet to ICS? What did I do wrong? How do I get either Cm10 to work or return to the ICS? Also, if I need to flash something else, how do I do it? Does the CWM recognize msd cards? Because all I have on the internal memory is the CM10 which currently did not work for me. I'm a little desperate right now. Thanks.
EDIT: DAMN IT, I just got an error restoring data. What the hell do I do? Please!
i tried restoring again and reflashing cm10 and the gapps and still nothing changes. I did wipe again the caches and still nothing. Also I can't download other roms to the tablet because my computer doesn't recognize the tablet because it hasn't booted and the cwm won't recognize micro sd cards. So I think flashing something else isn't an option. Did I break my tablet completely? I'm almost in tears
I tried several things due to some searches on different forums but nohitng works. I tried wiping caches and reflashing Cm10, didn't work. I tried pluggin my tablet to my computer and sending the asus stock rom via ADB and flashing that, but CWM gives me an "installacion aborted" error. I just don't know what to do nor I understand what went wrong. I did everything according to multiple tutorials. Unlocking, flashing CWM and rooting went just fine. But installing CM10 ended up pretty much destroying my tablet. I wanna kill myself.
I think you have a brick??!! :'( cm10 is jellybean and you where on ics and you probably didn't flash the jellybean bootloader did you?
Sent from my ASUS Transformer Pad TF300T
Not a single tutorial said that I had to do that. Every tutorial says "unlock bootloader, flash cwm, flash root_signed, flash cmrom". I did just that. Are you telling me that my tablet is lost forever?
in most cm threads (except cm9) their is stated that you atleast need android 4.1.1 with it's bootloader or 4.2 with it's bootloader, what i suggest you try is to flash a bootloader and upgrade staight to 4.1.1 you can download the firmware from asus the links are on this guide: http://forum.xda-developers.com/showthread.php?p=39272826 FOLLOW THIS GUIDE CORRECTLLY OR YOU MIGHT PERMANENTLY BRICK YOUR TABLET!!!!
EDIT: if you get an error during flash it's probably the drivers or a fastboot flash brick wich is only fixable by replacing the motherboard!!
Sent from my ASUS Transformer Pad TF300T
If what you say is true, then you can't flash CM10 on a stock ICS tablet, and that goes against every freaking tutorial I've read before messing with my tablet.
What exactly is your bootloader version?
Sent from my ASUS Transformer Pad TF300T
I'm not sure what my answer is. The "bootloader" was unlocked by the Asus app from their website. I did that by downloading (I believe it was V7) the apk from their website and installing that and unlocking the tablet. From there on, I just followed did fastboot flashing CWM and rooting. I never read a tutorial that said "you should flash JB bootloader before installing cm10". In fact I thought that just by unlocking the tablet, rooting and flashing the custom recovery one could just install a custom rom regardless of wether it's JB or not. It's funny because I didn't want to upgrade to stock JB because it seemed buggy from a lot of reviewers, and CM10 was the classic option to have JB and a lot of great features and speed. So I google time and time again how to flash CM10 on a ICS stock ASUS. I just followed the tutorials for that.
is my tablet unrecoverably bricked? I also tried fastbooting and "flash system blob" with the blob for the ICS 4.0.3 firmware, after a while of "sending" the file in the command prompt, I got a blue progress bar in the fastboot screen on the tablet and then "FAILED". So I guess that doesn't work either.
Nothing will work?
Try entering fastboot reboot: does your tablet reboot or does it hang?
cm10 is android 4.1 it seems logical that it only runs on a 4.1 bootloader and not on an ics one! most posts must have said that you atleast need jelllybean 4.1.1
I was confused in the beginning aswell because my phone accepts any rom no matter what bootloader version!
Sent from my ASUS Transformer Pad TF300T
If it makes so much sense that CM10 with JB 4.1 only boots with the JB bootloader, then how the hell one can go from ICS to CM10?! Google tutorial flash cm10 on asus tf300t stock ics and you'll find a thousand tutorials not one of which says you need JB bootloader. I mean, I assume one could upgrade to the official JB rom and then unlock bootloader, etc, but I'm telling you, every tutorial that said "stock ics to cm10" did no mention the bootloader version issue. I'm not trying toblame anyone other than myself for "bricking" my tablet, but I read so many tutorials to ensure I wouldn't mess it up that I'm very upset about this.
I can use fastboot and adb commands. But I haven't been able to flash the ICS stock rom so far. First of all, it's not on the Asus website anymore, and the one I got from the web gave me this error on CWM "instaling update.. installation aborted". I also tried flashing the .blob via fastboot and it also failed. It seems nothing works. Any thoughts, anyone?
philos64 posted links to some old ICS ASUS firmwares in this post:
http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Maybe worth a try ? Never been on ICS myself - just thought I'd mention this source...sorry for wasting your time if this is what you already tried.
Yeah, I tried flashing the ICS 9.4.3.30 (my stock rom) and it didn't fly (said installation aborted) and also tried to flash it as a blob and it failed. I guess I deserve this, but I just can't bellieve this isn't fixable.
samus88 said:
Yeah, I tried flashing the ICS 9.4.3.30 (my stock rom) and it didn't fly (said installation aborted) and also tried to flash it as a blob and it failed. I guess I deserve this, but I just can't bellieve this isn't fixable.
Click to expand...
Click to collapse
We would like to know what bootloader you now have. You use the bootloader menu to get to cwm. Tell us how many ICONS you have and what they are. This way we will have more info to consider options if any.
It's ICS. I have the Wipe Data and the Coldboot option. If I'm connecte with the usb cable, there's also the usb icon.
Currently I don't have the tablet, because I send it to a tech support place and they should give me a repair budget (if they deem it repairable, I guess) by tomorrow, but I'm not confident that they'll be able to fix it. So I'm still open to suggestions. Thanks!
samus88 said:
It's ICS. I have the Wipe Data and the Coldboot option. If I'm connecte with the usb cable, there's also the usb icon.
Currently I don't have the tablet, because I send it to a tech support place and they should give me a repair budget (if they deem it repairable, I guess) by tomorrow, but I'm not confident that they'll be able to fix it. So I'm still open to suggestions. Thanks!
Click to expand...
Click to collapse
I reread the thread and I believe I would make a blob with just stock recovery (4.03) to match your bootloader. I know fastboot is failing on a complete blob but may process something as small as recovery. The blob could also be pushed to your tablet with adb and flash with that.
I made these choices as a place to begin since we need to match your bootloader.
Once stock recovery was in place we could use adb to push a once unzipped stock firmware (4.03) and get stock recovery to install it for us.
Thanks a lot man. When I get the tablet back and you make me that blob I'll definitely give it a try. Although I have a question, I already have the once unzipped stock ICS on my tablet (pushed it with ADB), how do I install it with stock recovery should flashing that blob work?
samus88 said:
Thanks a lot man. When I get the tablet back and you make me that blob I'll definitely give it a try. Although I have a question, I already have the once unzipped stock ICS on my tablet (pushed it with ADB), how do I install it with stock recovery should flashing that blob work?
Click to expand...
Click to collapse
With stock recovery in place go into bootloader and pretend you are going into cwm that activates stock recovery now. If android lays down we'll rename the zip to EP201_768_SDUPDATE.zip and try again.
I'll download 4.03 and make the recovery blob tomorrow so we'll be ready.
Sorry about that. I read "I would make" as "I will make", lol. Is there a stock recovery 4.0.3 blob on the internet for download? I'll get some sleep now, but I'll try to prepare everythng for when I get the tablet back, assuming I don't have fixed for me by tech support (although I'd love not to have to pay forit, right)
samus88 said:
Sorry about that. I read "I would make" as "I will make", lol. Is there a stock recovery 4.0.3 blob on the internet for download? I'll get some sleep now, but I'll try to prepare everythng for when I get the tablet back, assuming I don't have fixed for me by tech support (although I'd love not to have to pay forit, right)
Click to expand...
Click to collapse
No, there is the full blob in the factory firmware and that is what I'll use. It only takes a couple of minutes to extract the recovery image file which might flash and then re-blob just the recovery partition.
Downloading takes longer than everything else.
Update:
This zip contains stock 4.03 recovery as a blob and as an image file.
Unzip and try flashing the blob - if it fails try flashing twice more or until success. If it still fails try flashing the image file - three times if it fails.
Note:
These are to be flashed with fastboot or adb, not cwm.
Great, thanks man. Unfortunately, I won't have my tablet until at least wednesday because of the holiday on my country (independence day and such). But I'll give it a try and get back to you.
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!