Database Info

TF101 Rooted, want to update firmware

I rooted my TF101 with the peri for windows. No problems there. Been running sluggish lately, and browser's been crashing a lot, so I wanna do the latest firmware update on it. I don't mind losing the root if keeping it isn't possible to upgrade. When the tablet tries to auto install the new firmware the system reboots, and then goes to a screen that reads the following:
Rouge XM Recovery 1.5.0(CWM-Based Recovery v 5.0.2.8):
Install from zip file ---->
wipe
Nandroid Backup
Mounts and storage --->
Advanced ---->
Reboot
Power off
What would be the best way to go about getting the new firmware on the system?

[GT-i9020T] 4.1 OTA failed and no longer available (rooted, stock recovery)

Hi,
I have a GT-i9020T.
It is rooted, running 4.0.4 stock (unlocked bootloader, IMM76D). Today I got the 4.1 OTA update notification. As far as I know the phone had stock recovery before I tried all of this below, since I never did a permanent install of CWM and have had to re-flash CWM every time I want to use it.
So I did the following:
1) Booted into the bootloader
2) Flashed (via fastboot) the newest CWM recovery (6.0.1.0) that I could find on the CWM site
3) Went into CWM and did a backup
4) Upon asking CWM to reboot after the backup, it asked me if I wanted to permanently install it and I said NO
5) Booted into Android and began the 4.2 install
6) After it rebooted to do the install, it soon came to the icon where the Android is laying down and exposing his guts with a red triangle exclamation mark icon on him
7) A bit later it automatically rebooted back to Android and the OTA update notification is no longer available
So my questions are:
1) Why did this happen and how could I have prevented it? Is it because the phone is rooted (seen some threads saying that)? Is it because I used CWM before the upgrade and that somehow messed up the recovery even though I didn't tell it to make itself permanent? (other threads mention this)
2) How can I get the OTA update to show up as available again? Did it go away because that's what Android does when the OTA update fails, assuming that it will fail if retried, so it makes it unavailable? Will I have to install it manually instead of via the normal OTA notification?
Thanks

Ok. Now after searching some more and trying to manually install the very same zip that was downloaded by the OTA, I see the issue is with the verify/assert/check/md5 for /system/bin/gzip.
And I see the other threads where people discuss the cause and solution for this.
Still interested in how to make the OTA notification come back though

i have the same probleme as you. and don't know how to solve it

scootley said:
Hi,
I have a GT-i9020T.
It is rooted, running 4.0.4 stock (unlocked bootloader, IMM76D). Today I got the 4.1 OTA update notification. As far as I know the phone had stock recovery before I tried all of this below, since I never did a permanent install of CWM and have had to re-flash CWM every time I want to use it.
So I did the following:
1) Booted into the bootloader
2) Flashed (via fastboot) the newest CWM recovery (6.0.1.0) that I could find on the CWM site
3) Went into CWM and did a backup
4) Upon asking CWM to reboot after the backup, it asked me if I wanted to permanently install it and I said NO
5) Booted into Android and began the 4.2 install
6) After it rebooted to do the install, it soon came to the icon where the Android is laying down and exposing his guts with a red triangle exclamation mark icon on him
7) A bit later it automatically rebooted back to Android and the OTA update notification is no longer available
So my questions are:
1) Why did this happen and how could I have prevented it? Is it because the phone is rooted (seen some threads saying that)? Is it because I used CWM before the upgrade and that somehow messed up the recovery even though I didn't tell it to make itself permanent? (other threads mention this)
2) How can I get the OTA update to show up as available again? Did it go away because that's what Android does when the OTA update fails, assuming that it will fail if retried, so it makes it unavailable? Will I have to install it manually instead of via the normal OTA notification?
Thanks
Click to expand...
Click to collapse
I think somehow CWM did stick and so you lost stock.
Use this guide to get back to stock. http://forum.xda-developers.com/showpost.php?p=29073020&postcount=1
The OTA should come. If not try this trick to force it. http://forum.xda-developers.com/showpost.php?p=29067584&postcount=2817
It doesn't say but pull your SIM or go into airplane mode first. Turn on wifi and make sure you have a strong signal. Cheers hope this helps.

For the time being, I:
* Tried to force an install of the previously downloaded 4.1 OTA zip using CWM (it was in /cache)
* Saw it present a checksum error for patching gzip
* Searched the forum for help
* Downloaded the full official 4.0.4 ROM zip for my phone
* Extracted system.img from it
* Converted that image file (not sure what format it is in) into an ext4 image using http://forum.xda-developers.com/showpost.php?p=15333542&postcount=135
* Mounted that ext4 image in linux
* Extracted 3 files from /system/bin in that mount: gzip, ip, ping
* Copied those files to /system/bin on my phone when it was in CWM via adb
* Forced an install of the previously downloaded 4.1 OTA zip using CWM (it was in /cache)
* Did part of the above steps in a loop, because the OTA update only tells you which files are not matching the checksum one by one
This allowed the OTA update to proceed.
I will check on CWM getting somehow stuck and on reverting it.
Thanks for the tips jayjay3333

I should also mention that I have very little interest in wiping my phone. In other words, to me one of the greatest benefits of Android is it's ability to update the OS successfully.
Luckily I got this to work.
Hopefully I can restore the original recovery without wiping the OS too.

scootley said:
For the time being, I:
* Tried to force an install of the previously downloaded 4.1 OTA zip using CWM (it was in /cache)
* Saw it present a checksum error for patching gzip
* Searched the forum for help
* Downloaded the full official 4.0.4 ROM zip for my phone
* Extracted system.img from it
* Converted that image file (not sure what format it is in) into an ext4 image using http://forum.xda-developers.com/showpost.php?p=15333542&postcount=135
* Mounted that ext4 image in linux
* Extracted 3 files from /system/bin in that mount: gzip, ip, ping
* Copied those files to /system/bin on my phone when it was in CWM via adb
* Forced an install of the previously downloaded 4.1 OTA zip using CWM (it was in /cache)
* Did part of the above steps in a loop, because the OTA update only tells you which files are not matching the checksum one by one
This allowed the OTA update to proceed.
I will check on CWM getting somehow stuck and on reverting it.
Thanks for the tips jayjay3333
Click to expand...
Click to collapse
No problem. Glad you got it sorted.

scootley said:
Hi,
I have a GT-i9020T.
It is rooted, running 4.0.4 stock (unlocked bootloader, IMM76D). Today I got the 4.1 OTA update notification. As far as I know the phone had stock recovery before I tried all of this below, since I never did a permanent install of CWM and have had to re-flash CWM every time I want to use it.
So I did the following:
1) Booted into the bootloader
2) Flashed (via fastboot) the newest CWM recovery (6.0.1.0) that I could find on the CWM site
3) Went into CWM and did a backup
4) Upon asking CWM to reboot after the backup, it asked me if I wanted to permanently install it and I said NO
5) Booted into Android and began the 4.2 install
6) After it rebooted to do the install, it soon came to the icon where the Android is laying down and exposing his guts with a red triangle exclamation mark icon on him
7) A bit later it automatically rebooted back to Android and the OTA update notification is no longer available
So my questions are:
1) Why did this happen and how could I have prevented it? Is it because the phone is rooted (seen some threads saying that)? Is it because I used CWM before the upgrade and that somehow messed up the recovery even though I didn't tell it to make itself permanent? (other threads mention this)
2) How can I get the OTA update to show up as available again? Did it go away because that's what Android does when the OTA update fails, assuming that it will fail if retried, so it makes it unavailable? Will I have to install it manually instead of via the normal OTA notification?
Thanks
Click to expand...
Click to collapse
u must accept yes for that it should work.

abhidoT38 said:
u must accept yes for that it should work.
Click to expand...
Click to collapse
what?

[Q] Did I root correctly?

So I got my 300T a few nights ago.
It's already got Asus's JB on it.
Wanted to root to use the SwitchMe app for multiple profiles.
I was able to get the system to see fastboot, and ran all of the commands. Was able to boot to CWM and install root-signed. When I was trying to reboot, it said root was possibly lost, asked me to fix it, i said yes.
When I open up the SwitchMe app, it just keeps trying to open a SuperUser window about 7 times, and then does nothing else.
Have I done something wrong?
SuperUser just says No Apps in List.
edit: tried to update SuperUser. It says "gaining root access.....fail!". Guess I'll try to install root-signed again. Not sure how I could've messed it up the first time.
edit 2: wiped cache and dalvik, installed root-signed again, same problem. SwitchMe says I haven't granted superuser permissions. SuperUser shows no apps, is set to auto-allow root access, and fails getting root access when running binary updater.

im pretty sure you have to unlock the bootloader
and go through some crazy process before you can root with JB

My tablet was running JB when I bought it. I unlocked and still could not get my tablet to root using CWM. On top of that, CWM would not make a proper backup. I highly recommend you switching to TWRP. I did, flashed a rooted custom ROM and haven't had anymore issues.
Many people are having issues with CWM. TWRP is definitely the way to go. :good:

1 wrong section
2 root checker app(s)

Well, what I did to root my stock using TWRP was to flash the root-signed in the CWM thread, but as this didn't really got me full root, I flashed the flashable zip from here, downloaded SuperSU from market, there then chose "update binary" and then I had root
I'm pretty sure flashing the root-signed of the CWM thread wasn't needed, but if you do this steps (need to be unlocked to flash a recovery, strangely recommend TWRP 2.3.1 or 2.2.2 for 4.1 ROMs and 2.3.3 for 4.2 ROMs (as 4.2 has this sdcard/0 directions because of Multiusers, 2.3.3 uses this directories too))
So what should work:
1. unlock bootloader
2. flash CWM / TWRP / MobileODIN installable ZIP: CWM-SuperSU-v0.99.zip from here
3. download SuperSU from market and there update binary (don't know how it's called exactly)
4. enjoy!
if you decide to use a Custom ROM, you just need to flash the ROM in TWRP and should get Root too with the ROM (as all of them include Root afaik)

How to update with TWRP

Hi,
Basically I'm trying to update to lollipop via OTA so I dont lose all my data, but whenever I try and install the update, my phone reboots into TWRP, but then it just goes to the main menu and doesn't update anything.
Just wondering how I should update? Do I have to install the stock recovery? Or will that make me lose my data too?
Cheers,
Jack

I don't think it's a very good idea to update ota when your phone is rooted. I don't think it will update either because you don't have the stock recovery.
What I did personally... I backed up my 4.4 ROM and followed the instructions on bixie's stock ROM. I didn't delete my internal storage and everything carried over.
If you don't have the latest twrp. You can either download flashify from the market or you can use adb/fast boot.
Sent from my Nexus 5 using XDA Free mobile app

So I used TWRP to install that rom but lost my root in the process. Any idea's what I screwed up?
I made sure to backup using TWRP before starting.

Root is removed as the OTA removes it, just root again (if you read any of the guide threads on here you'd know this)

[Q]Update to Lollipop AND Stay Rooted

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?