Related
i have stock 4.0.3. I try to download the OTA 4.0.4 but I get the red triangle with the green android as it is trying to install. did these steps and it still won't update:
1. go to setting / apps then hit the all button at the top
2. scroll down to google services framework and then press it to open
3. hit the clear data button
4. go to settings / about phone / system updates (you will notice the date will be 1969 or 1970 this is ok )
5. hit the check now button
6. xoom should show you the 4.0.4 update avalaible
7. hit install and enjoy
any suggestions?? seems like I have to send it in to Motorola for them to manually flash this update
a bunch of users in the Official Motorola forum also have this issue: https://forums.motorola.com/posts/0212457c59
vinnyt225 said:
i have stock 4.0.3. I try to download the OTA 4.0.4 but I get the red triangle with the green android as it is trying to install. did these steps and it still won't update:
1. go to setting / apps then hit the all button at the top
2. scroll down to google services framework and then press it to open
3. hit the clear data button
4. go to settings / about phone / system updates (you will notice the date will be 1969 or 1970 this is ok )
5. hit the check now button
6. xoom should show you the 4.0.4 update avalaible
7. hit install and enjoy
any suggestions?? seems like I have to send it in to Motorola for them to manually flash this update
a bunch of users in the Official Motorola forum also have this issue: https://forums.motorola.com/posts/0212457c59
Click to expand...
Click to collapse
It's because you're not using a stock recovery. Go into your /cache folder, pull the file out of there and put it on your internal storage somewhere, then go into whatever recovery you use and flash the zip file.
You can only do the auto OTA installs if you're using stock recovery. Otherwise, you have to flash manually. Just the way it is.
thanks for the reply oldblue910. I don't have any zip files anywhere. Everything i am trying to do is over the internet. But if you could guide me your process maybe i'll try your way.
vinnyt225 said:
thanks for the reply oldblue910. I don't have any zip files anywhere. Everything i am trying to do is over the internet. But if you could guide me your process maybe i'll try your way.
Click to expand...
Click to collapse
OK first off, I assume you're rooted, yes?
i am not rooted...forgot to say that. completely stock. tablet came with 4.0.3 and was new out of the box.
vinnyt225 said:
i am not rooted...forgot to say that. completely stock. tablet came with 4.0.3 and was new out of the box.
Click to expand...
Click to collapse
Interesting...the OTA should apply fine then. OK here's the next thing. Go and flash the OTA as normal. Once it gets to the Android with the red triangle, press and hold the power button, then press volume up (while holding down the power button). Some text will appear on screen. Please post that text here.
oldblue910 said:
Once it gets to the Android with the red triangle, press and hold the power button, then press volume up (while holding down the power button). Some text will appear on screen. Please post that text here.
Click to expand...
Click to collapse
Same exact issue here!!!!
I did that, and it reads in yellow text:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
That means for some reason the downloaded file is corrupt...hmmm....not quite sure on that one...
Sent from my Xoom using Tapatalk 2
From what I can read, the only way to get 4.0.4 is to either root of send it in to Moto. Here is a link that I read that is about the same issue.
*** I tried to post the link but since I am a new member I can't post outside links. It is on the motorola xoom owner's forum
False. If you haven't dicked around with your tablet and wait for the OTA notification like a good boy, it installs fine.
Sent from my Xoom using Tapatalk 2
I'm having the exact same issue, and I'm two for two on brand new Xoom's that will not install the update right out of the box.
---------- Post added at 07:11 PM ---------- Previous post was at 06:21 PM ----------
MikeMBau said:
Same exact issue here!!!!
I did that, and it reads in yellow text:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
I'm getting the same text(obviously), but at the top of the screen, are you guys seeing these 4 options:
reboot system now
apply update from USB drive
wipe data/factory reset
wipe cache partition
?
I'm sure you are. The one I'm interested in is the "apply update from USB drive", because someone at Xoom Forums suggested doing the update from a USB drive, but with a USB host cable, and it was a different method than what I think this option is suggesting, but mu understanding is that using a USB host cable doesn't work with an unrooted Xoom.
This option makes me curious.......and I'm wondering if it would see the update on a USB drive attached to the Xoom, should you have it attached with the stock 4.0.4 zip file on the USB drive, and selected this option.
I'd never do it unless someone said it would work.
All that being said, it also seems that if you installed a recovery, and rooted it, that you could flash the stock 4.0.4, but I'm just assuming that's right.
You know guys, I totally forgot about this...
If you are on 4.0.3 and trying to update manually to 4.0.4 in stock recovery via OTG cable, you will not be able to. There is a bug in the stock recovery that only allows flashing OTAs when using the OTA notification software, and will fail if attempted manually.
This topic was beat to death when the 4.0.4 OTA for the WiFi Xoom came out back in April. The Nexus S had the same problem as well because of the same stock recovery bug. If you want to read up on it, just do some searching here on XDA. There was a ton of chatter about it.
Sent from my Xoom using Tapatalk 2
oldblue910 said:
If you are on 4.0.3 and trying to update manually to 4.0.4 in stock recovery via OTG cable, you will not be able to.
Click to expand...
Click to collapse
Nope, this is all in reference to OTA updates. None of us are attempting to install it manually. It is a known issue with this device.
I don't get why you think I "dicked around" with my tablet... I got it in the mail, saw it was on 4.0.3 and just went to settings>about tablet>system updates. I haven't "dicked around" at all.
Do you have any other ideas in order to get 4.0.4 on my Xoom? Is the USB host cable worth a shot?
This is what someone on the Motorola support forums had to say about this:
I agree with the possibility that the OTA package could be corrupt and there are theories out there that Google's process is causing the issue, but no confirmation. The problem with the storage of Android OTA images is that they reside in a system partition without user accessibility, so if they are corrupt, the system just keeps trying to install it.
Let me share your details with the Motorola Tech I have been working with and see what your upgrade status shows.
I submitted a ticket online to send my Xoom in, but I am uncomfortable doing that. If someone told me that the USB works, then I would rather do that instead.
MikeMBau said:
I submitted a ticket online to send my Xoom in, but I am uncomfortable doing that. If someone told me that the USB works, then I would rather do that instead.
Click to expand...
Click to collapse
Yeah, I haven't pulled the trigger on that decision yet. I have to sleep on it. I told the one guy I talked to, who was "level 2"......Motorola is doing nothing about this. He said "we are doing something........we'll send you a box". Great answer.
On the USB thing.....I feel the same way, but sounds like you have to root it to do that. If I root it, it will be because I want to, and right now I don't. I just bought it. I'm on my second one in 3 days that has the same issue. If I root it, I'm going to cut to the chase and just flash a custom ROM, and I won't have to worry about updates. Right now I just don't want to do that.
On a side note, make sure they're real clear on what the issue is with your Xoom. The reason I say that is that I saw one lady post on the Motorola support forums that she has two Xooms that she bought at the same time, with the same issue you and I have, and they simply put "repair" in the notes. She got them both back, and they still had 4.0.3 on them, and wouldn't update. Read the second post on this page, from "Sharon"
https://forums.motorola.com/posts/0bc09ed02d?commentId=613182#613182
Totally ridiculous.
I was just about to say "screw it" and send it in, and then read that. I'd go through the roof if that happened to me. I still might send it in, but I'm just really uncomfortable doing that with something that has an issue right out of the box, but I don't want to keep sending them back to Amazon, with the hope that the "next one" will update correctly.
Trust me.......any method that would work to resolve this, that didn't involve rooting the damn thing, I'd be all over, just like you.
Just read this post from a guy on the Motorola support forums that has been talking to a Motorola tech he knows:
"The Android OS always downloads an update first (to a system-only partition), does a basic validation (like total size) and then applies the update to your system. What I have heard from other developers is that if the update fails (for any reason), the OS does not download a new copy nor delete the current image, it just keeps trying to reinstall the same image. If that is true, then someone (like the service center) may have to unlock the Xoom and apply a new image to resolve the issue."
MikeMBau said:
I submitted a ticket online to send my Xoom in.
Click to expand...
Click to collapse
So did I.......not crazy about it either.
MikeMBau said:
I submitted a ticket online to send my Xoom in, but I am uncomfortable doing that.
Click to expand...
Click to collapse
Did you end up sending it in after all? I sent mine, they got it the next day, the repair status says closed, and hopefully it will ship back today, and be here tomorrow.
OK, i searched and found some threads on the matter but that was for the Prime. also found some other issues with the unlocker dealing with an un-recognized serial number or no data connection.
anyway, a little about my tablet. purchased it from a friend, brand new, sealed in box. serial numbers match (between box and device) i rooted right away since i was on the .17 firmware, did the OTA root keeper thing. the OTA was pushed to my device that same day, it updated just fine. a couple days later the .30 update was pushed to my device...took that as well just fine. so i was running stock .30 firmware but was rooted. I tried the unlock tool in that state, and got the message below. so i started reading and saw a reset could fix it...so i did that.....no dice.
did a "cold reboot" (volume down and power until the message pops up and just let it time out for the 10 seconds to clear caches and what-not.)
tried again....Nothing.
i have tried it while tethered to my Nexus, and connected to my home wi-fi with no luck.
what is my next step? should i downgrade to .17 and give it another go? is this possible without a computer (at work and would like to do it today)
is this just an ASUS server issue and just "bad timing" to unlock...or does this go deeper than that?
thanks for all your help....pulling out my hair trying to figure this out.
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
EndlessDissent said:
Except, he got an OTA already.
I would recommend downgrading to .17 since some people have had success with that.
Click to expand...
Click to collapse
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
turdbogls said:
that was my thoughts....i though the serial number issues also affected the OTA's being pushed.
can downgrading be one on the tablet alone?
i though i read on the TF prime site that you can download the built, extract the .zip file from the .zip you download from asus, plop it on the root of an sd card (internal storage or external SD? i have both available) then turn off, volume down + power and hit volume down, then volume up and it will install that....is this correct?
or do i need to do it though ADB?
Click to expand...
Click to collapse
Yeah, I think that's how it works. When I downgraded to .17 to root way back when, I used Wolf's method, which used ADB. I think either way will work fine.
OK, can anyone confirm or post a link or something to the exact method of an "on the device" downgrade method.
the only things i am finding online are Wolf method which involves ADB.
can i simply put the .zip or blob (which one?) on the root of internal memory.
turn off tablet
hold volume down +power
hit volume down
then volume up
and it will install the .17 system?
I am working late tonight with no access to my home computer for the next couple of days probably
ok, i actually got of work early and was able to downgrade via ADB. i am on stock .17 firmware right now doing a factory reset and then i will be giving it a go one more time.
edit: Annnnd....it didnt work >)
Damn. The worst part is that Asus refuses to help people in your situation. All I can suggest now (hopefully someone can suggest something better), is to try everyday, at least once. Some people get it to work like that.
I really wish I could help more. The most trouble I had with unlocking was signing into my Google account (I have 2-step authentication). I was on .30 rooted, and it worked perfectly. I know that's not what you want to hear. I just have no idea why it would work fine for some people and not work for others. The serial number issue was bad enough, but now, people with working serials can't use the unlocker? That's preposterous, and Asus needs to fix it.
Well....what can ya do. I am going to call Asus tomorrow and see if they can verify my SN is in the database.
I'd I can unlock...great!
If I cant , well I will still enjoy my rooted tf300 and wait patiently for my JB OTA.
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
EndlessDissent said:
I hope you get it sorted out. Knowing Asus, though, even if they don't help you, the official update should be ready shortly. Possibly before there's a stable CM10 available.
Click to expand...
Click to collapse
I hope you are right....I dont expect it to be before a stable CM10 is released....but i do have high hopes to see it before the end of August.
FWIW, i am back on stock .30 rooted sofware. back at square 1
but i will be trying the unlock tool every day until JB arrives or it works...lol
also contacted ASUS (e-mail) about the issue, they told me to factory reset and see if that worked.....hope they can help me out even more when replying to my reply.
mikaole said:
its a problem with your serial not been in the asus database. Call Asus and tell them that update is not working, don´t tell them that you want to unlock.
They will put your serial in their database. Then try unlock again.
Click to expand...
Click to collapse
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Saintom said:
And don't say your serial is not in the database, cuz the only way to know that is
when trying to unlock!
Click to expand...
Click to collapse
lol
I'll give them some BS about a neighbor having the same issue and having them enter it into thier database fixed it.....that should work.
the announcement of an almost complete (BT and camera dont matter to me) AOKP JB build has me making this call in about an hour. I want this done SOOOO bad now
OK, so i called them with some BS about not getting updates and asked them to put my number in their "system"
the guy said that my SN was in there now.
still no dice on the unlocker app.
how long does it take to become "activated" in their system. should i be waiting a day before expecting results?
still nothing today...anyone else get this message and have it resolved?
i read a thread where a bunch of people are getting the same error (over on the TF Prime forums) it just wasn't working for some reason...then one day, boom, it started working again.
so maybe it is something on ASUS' end and they either shut it down or it just isn't working right now.
anyone successfully unlock their device in the last week?
turdbogls said:
anyone successfully unlock their device in the last week?
Click to expand...
Click to collapse
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
bsaman said:
I had this exact issue and resolved it by doing a 'factory reset' on it, then reinstalling the tool. At the time, I was stuck on FW 17 and wasn't getting updates from Asus, so unlocking and flashing a different ROM was the way to go in order to keep ROOT.
Haven't looked back since (currently on AOKP's JB build and loving it).
Click to expand...
Click to collapse
I hate you for being able to do it so easy...lol
i have unrooted, i have factory reset a couple times, i have downgraded to .17 and factory reset then...nothing
I WAS getting OTA's though. so i guess i am just going to have to wait for official JB...i would love to be running AOKP JB on my 2 main devices.
Did you manage to get this working?
help. After tried update .30 so my transformer cant not boot, it stay at ASUS logo
Im root, but not unlock.
WHat sholuld i do ??
early i remove bulid.pop and replace a build.pop stock. and replace all app on system/app.
HLEP
dose it brick ????:crying::crying:
please !!! help
lethang90b said:
please !!! help
Click to expand...
Click to collapse
See the instructions in this thread for Factory Restore after a Softbrick
http://forum.xda-developers.com/showthread.php?t=1833212
You could substitute the .30 update for the .26 since it appears to be available online again.
okantomi said:
See the instructions in this thread for Factory Restore after a Softbrick
http://forum.xda-developers.com/showthread.php?t=1833212
You could substitute the .30 update for the .26 if it is available online. I think it was taken down, but it may be available in someone's dropbox...perhaps in Development/ZEUS Rom thread.
Click to expand...
Click to collapse
Just an FYI - the .30 firmware is now available on the Asus site again - I downloaded it this morning.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Did you put the full image correctly renamed to EP201_768_SDUPDATE.zip on the SD card and reboot into recovery? (Power + Vol Down then Vol Up when you see the text at the top left?). This is the only way to recover from this situation that I know of, however, you won't lose anything - it upgrades "in place"
See here: http://forum.xda-developers.com/showthread.php?t=1755576
okantomi said:
See the instructions in this thread for Factory Restore after a Softbrick
http://forum.xda-developers.com/showthread.php?t=1833212
You could substitute the .30 update for the .26 since it appears to be available online again.
Click to expand...
Click to collapse
i tried it, but it field like update .30
EDIT: i did it. but can to change .30 US, im at WW .30
About the time JB was released I checked for an update not realising that it would go ahead without confirmation. As I didn't want to update just then I cancelled the download by clearing data in CM & DMclient (seemed to be the only way after turning wifi off).
Recently I just rooted (locked) using the debugfs method, after which checking for updates comes back with a zilch.
I tried clearing DM/CMclient data again and removing the update files :
fw_update_progress & isp_fw_progress
These had java errors in them presumably because I had aborted. After trying again they hold "0" and "100" in text format.
Finally on someone's recommendation I did a full factory reset (which worked for him) but I'm still without OTAs.
I'm hoping someone can shed some light on what may be the problem. AFAIK just rooting doesn't kill OTAs yet something has. Does Asus perhaps keep a database record as to what has been downloaded? I somehow doubt it but with a full factory reset I fail to see what's stopping these updates.
Any help , suggestions appreciated.
I dont know if the OTA is operational again, but a lot of people like myself never received any automatic updates for a brand new stock infinity on the 11th. You might might want to try a manual update. Here is my post on the other threads on what I did to manual update to 4.1.1.
"I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update. "
junrider said:
I dont know if the OTA is operational again, but a lot of people like myself never received any automatic updates for a brand new stock infinity on the 11th. You might might want to try a manual update. Here is my post on the other threads on what I did to manual update to 4.1.1.
"I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update. "
Click to expand...
Click to collapse
Yes I was aware of cases where OTAs never happened from the beginning but they did work for me . I had a pre-JB update and then the JB update itself which I aborted. So I think this is a slightly different case.
louiscar said:
Yes I was aware of cases where OTAs never happened from the beginning but they did work for me . I had a pre-JB update and then the JB update itself which I aborted. So I think this is a slightly different case.
Click to expand...
Click to collapse
I believe after a sucessful download OTA, Asus marked your ID, so you will not able to receive OTA again, the only way now is you have to do it manually.
buhohitr said:
I believe after a sucessful download OTA, Asus marked your ID, so you will not able to receive OTA again, the only way now is you have to do it manually.
Click to expand...
Click to collapse
Right, I've been trying to confirm if this is the case and how Asus do their OTAs. Thing is though, I aborted the download so it should have detected that the OTA was unsuccessful.
louiscar said:
Right, I've been trying to confirm if this is the case and how Asus do their OTAs. Thing is though, I aborted the download so it should have detected that the OTA was unsuccessful.
Click to expand...
Click to collapse
Here is how to update manually when OTA failed to update:
1. Download dlpkgfile.bin (US version)
http://www.mediafire.com/?2ctnjai5b68c7im
2. Rename dlpkgfile.bin to dlpkgfile then copy the dlpkgfile to /cache then set permissions to rw-r-r.
3. Download command file:
http://www.mediafire.com/?yq1bt16mnm7tc8d
4. Unzip and copy the "command" file to /cache/recovery, then set the file's permissions to rw-r-r.
5. Temp-unroot if you want to keep your root with OTA Root Keeper.(skip this if you already done this)
6. Power off.
7. Reboot holding power on and volume down, when you see white text message on the screen release both buttons
8. Press power up to confirm recovery mode.
9. Update will install and upgrade your device.
10. Once done, use OTA root keeper to restore root.
11. If you want to switch to superSU, you can download superSU, launch the app, verify it's working, then you can un install superuser.
buhohitr said:
Here is how to update manually when OTA failed to update:
1. Download dlpkgfile.bin (US version)
http://www.mediafire.com/?2ctnjai5b68c7im
2. Rename dlpkgfile.bin to dlpkgfile then copy the dlpkgfile to /cache then set permissions to rw-r-r.
3. Download command file:
http://www.mediafire.com/?yq1bt16mnm7tc8d
4. Unzip and copy the "command" file to /cache/recovery, then set the file's permissions to rw-r-r.
5. Temp-unroot if you want to keep your root with OTA Root Keeper.(skip this if you already done this)
6. Power off.
7. Reboot holding power on and volume down, when you see white text message on the screen release both buttons
8. Press power up to confirm recovery mode.
9. Update will install and upgrade your device.
10. Once done, use OTA root keeper to restore root.
11. If you want to switch to superSU, you can download superSU, launch the app, verify it's working, then you can un install superuser.
Click to expand...
Click to collapse
Thanks, yes I have already done that. I've also emailed Asus to try to get something sorted for future updates. I'm not sure if updating JB in this way will restore the OTAs. Asus' reply so far has been to tell me to clear DMclient data and I've just replied to tell them I've done that many times already. I'll see what transpires.
louiscar said:
Thanks, yes I have already done that. I've also emailed Asus to try to get something sorted for future updates. I'm not sure if updating JB in this way will restore the OTAs. Asus' reply so far has been to tell me to clear DMclient data and I've just replied to tell them I've done that many times already. I'll see what transpires.
Click to expand...
Click to collapse
Thank you for the update. I believe the issue is with their update servers. I had help people with brand new tf700 without receiving update, so it's not the tablet and it's not software or configuration related.
buhohitr said:
Thank you for the update. I believe the issue is with their update servers. I had help people with brand new tf700 without receiving update, so it's not the tablet and it's not software or configuration related.
Click to expand...
Click to collapse
Ok I will report here if I get anywhere with them. I somehow suspect that their support may not even realise or understand the issue but I will persist and see if I can get some kind of acknowledgment about their servers.
Well my OTA resumed after updating to JB so I think that it's as you state, the datebase on their servers. I don't know what the update was but your post in another thread would probably confirm this was JB .18. I guess once they have pushed an OTA, regardless of whether it was successful or not they don't seem to do it again. Which means I need to collect the dlpkgfile for each JB update given that I need to go back to ICS to do a proper factory reset and retain root.
I recently bought my new Transformer Infinity and like an idiot I updated to jellybean without thinking if I wanted to root first.
I've tried several different ways but I can't get my TF700t to root after updating so that leads me to ask if I must unlock before rooting after jellybean?
I've tried downgrading and that is to say I've put the 9.4.5.30 update in my root of the microsd card and when I go to recovery boot i just get the little guy on his back with a red triangle and black exlamation mark.
I realize unlocking will void my warranty which I am a little hesitant, though I never purchased any warranty with my tf700t but i think i can do so now.
I tried following this post:
Thanks for the reply, but i've been working on this for the past couple of hrs and my issue is solved. i'm currently back at 4.1.1 Jellybean again and Root Checker has verified that root is in place. the su binary is also present and all apps that need root work properly (Busybox, Titanium Backup, etc). i've also rebooted and rechecked several times to be sure, it say rooted every time now, whereas it didnt before. I managed to do all of this without unlocking the bootloader as well, even though what i've read elsewhere says it is necessary to do so.
I would have agreed with you before on your point that OTA updates are irreversible, and they usually are, but my experience today shows otherwise. however, you are right that each OTA will probably make it harder to reroot or stay rooted. you're also right that factory reset only wipes data but not firmware, which i just recently figured out today before you posted. i used the "about tablet" section in settings both before and after my steps below to verify that i had indeed downgraded/upgraded firmware/Android versions from JB to ICS and vice versa.
here are the steps i took, in sequential order, so that maybe anyone else with my issue can benefit. i cant gaurantee it will work for everyone:
1. downgraded from 4.1.1 JB firmware to "Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for US SKU (Android 4.0.3)". This will roll you back from Jellybean to Ice Cream Sandwich. go to support.asus.com, enter TF700T as the model number, and scroll down until you find this, then download it and unzip the zip file to the root of your sdcard (there is a zip file within the downloaded zip, place that at the root, not the downloaded file itself). if you are using a TF700T that is not US-based then download the appropriate file for your region, just make sure that it has .30 in the file name. I read on a forum somewhere that this is the only firmware update for this device that enables downgrading from higher version to 4.0.3, although it's possible that others may work. then power off your device and do a cold boot (hold down left volume and then followed by power button, do this for about 10 seconds. when you get to the desktop/start screen you will see "Safe Mode" in lower left corner, then your device will notify that an update is available. tell it to apply and let it reboot. when it powers back on you should be back at 4.0.3
2. Do a factory reset, this can be done either before or after the step above, but i did it after. i'm not sure if this is necessary , but just to be on the safe side. back-up all important info, apps, etc beforehand
3. I used the method at Simple Guide to Root TF700T Asus Transformer Pad Infinity : Tips For Tab . this guide can also be found at other websites, but the steps are the same and the files/utilities needed are the same as well. just follow the steps. this will not work if you are still at 4.1.1, you will get the error i detailed in my last post.
4. Download Root Checker (to verify root access) and make sure you have the latest Superuser installed from Play (SuperSU may also work but i'm not sure, i'm using the paid version of Superuser Elite). and also get Voodoo OTA RootKeeper (free), this has a function that will allow you to restore root access after upgrading to 4.1.1. Superuser Elite also has a "ota survival" function that does essentially the same, both worked for me (this software isnt free). and get Busybox and a terminal emulator like Better Terminal Emulator or Android Terminal Emulator. i'm not even sure if these last 2/3 are absolutely necessary, but they install essential must-have functions that all root users should have.
5. then use RootKeeper and make a backup of the su binary, or place a checkmark beside the "ota survival" function in Superuser Elite. either will backup the su info so that it can be restored.
6. Next, do a direct OTA upgrade to 4.1.1 JB , either by using the built-in firmware update function, or by manually downloading from the website and updating using the method listed above. Do NOT do a restore to factory backup state after this point (especially after), it will most likely wipe out the backups of su made by RootKeeper/Superuser Elite.
7. after the upgrade is finished you will be back at start screen at at 4.1.1, use Root Checker and it will say you're not rooted. Then use either of the 2 programs ive outlined to restore the su binary from the backup. in SU(E) just uncheck and recheck the OTA Survival box, or in RootKeeper just restore from backup. Then go back to Root Checker after doing either of these, it should say rooted. reboot and recheck to make sure.
8. That's it! just wash, rinse and repeat when the next firmware update is available, hopefully these same steps should work
Also make sure to keep a backup of the su binaries/app from here onwards, otherwise at some point in the future you may lose the ability to simply restore from backup after each OTA Firmware update. you will have to start over from the beginning.
I'm sure someone figured this out already, but i figured i would post anyways.
Click to expand...
Click to collapse
but i couldn't even downgrade
Beret67 said:
I recently bought my new Transformer Infinity and like an idiot I updated to jellybean without thinking if I wanted to root first.
I've tried several different ways but I can't get my TF700t to root after updating so that leads me to ask if I must unlock before rooting after jellybean?
I've tried downgrading and that is to say I've put the 9.4.5.30 update in my root of the microsd card and when I go to recovery boot i just get the little guy on his back with a red triangle and black exlamation mark.
I realize unlocking will void my warranty which I am a little hesitant, though I never purchased any warranty with my tf700t but i think i can do so now.
I tried following this post:
but i couldn't even downgrade
Click to expand...
Click to collapse
Where did you get the old ROM from? ASUS isnt hosting it anymore and it HAS TO BE a factory original Firmware signed properly or it will not take. In fact you should see "Signature Match" (or maybe its matched) in the top left corner in recovery.
I'm not saying that message is a guarantee you have the right ROM but its a good sign.
The default warranty is like a year so I wouldnt want to unlock either.
hx4700 Killer said:
Where did you get the old ROM from? ASUS isnt hosting it anymore and it HAS TO BE a factory original Firmware signed properly or it will not take. In fact you should see "Signature Match" (or maybe its matched) in the top left corner in recovery.
I'm not saying that message is a guarantee you have the right ROM but its a good sign.
The default warranty is like a year so I wouldnt want to unlock either.
Click to expand...
Click to collapse
I got the update that said: Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for US SKU (Android 4.0.3) - 2012.09.21 update
from http://forum.xda-developers.com/showthread.php?t=1946456
And i'm pretty sure it said signature match.
Beret67 said:
I got the update that said: Eee Pad Transformer Pad Infinity TF700T Firmware: V9.4.5.30 Only for US SKU (Android 4.0.3) - 2012.09.21 update
from http://forum.xda-developers.com/showthread.php?t=1946456
And i'm pretty sure it said signature match.
Click to expand...
Click to collapse
Makes me wonder if they have broken downgrade on the 10_4_4_25 firmware then?! The TF201 had that happen on the first JB update. You could no longer downgrade to ICS.
Edit, Adding that I just downloaded the US 9.4.5.30 from that site you linked to and an MD5 check confirmed it matches the one I have used 3 times.
hx4700 Killer said:
Makes me wonder if they have broken downgrade on the 10_4_4_25 firmware then?! The TF201 had that happen on the first JB update. You could no longer downgrade to ICS.
Edit, Adding that I just downloaded the US 9.4.5.30 from that site you linked to and an MD5 check confirmed it matches the one I have used 3 times.
Click to expand...
Click to collapse
The US link?
maybe i just need to redownload it or something and leave it named as is.
So then what can I do?
Beret67 said:
The US link?
maybe i just need to redownload it or something and leave it named as is.
So then what can I do?
Click to expand...
Click to collapse
The link you supplied that has all the firmwares there are several that say 9.4.5.30
The first one is WW, World Wide. You need to make sure you get the correct one for your device. So if you bough retail in the US get the second one that says "US". The firmware will not work if you don't get the correct one.
An easy way to tell what you need is to go to settings and scroll down to "About" on the left. Tap About and on the right half scroll down to "Build Number" My daughters TF201 says JRO03c.US_epad........
So she has the US one and would need the US Firmware.
If you have a US device and tried to apply the WW firmware from what I have read it will fail, won't work.. dead andy. Make sure you have the right firmware for your device.
Please post back your results as I am sure many would be interested if ASUS broke reverting to ICS.
Beret67 said:
The US link?
maybe i just need to redownload it or something and leave it named as is.
So then what can I do?
Click to expand...
Click to collapse
After you download the zip file, first you have to UNZIP the zip file and you're going to see another zip file. Now rename this new zip to EP201_768_SDUPDATE.zip , then copy this to the root of your sdcard, boot into recovery and try again.
Beret67 said:
The US link?
maybe i just need to redownload it or something and leave it named as is.
So then what can I do?
Click to expand...
Click to collapse
I assumed the file rename was in the directions above
The only device I believe you should ever have to root/unlock /jailbreak is the IOS platform. As you probably know, you are extremely limited to any customization with an IOS device. Under the android platform, I find that there are many flavours of customization under the stock setting already. I've ran the TF700T with the latest updates and firmware for the past few months and performance is still optimal ... I also bet that if you had my tablet side by side next to a rooted/unlocked TF700T tablet, you wouldn't be able to tell the difference from a performance perspective. I'm only speaking from a standard user point of view. I can see where a developer may want root access and or someone who wants to learn how to program the OS, create custom ROMS etc., however for the casual user, I'd leave it the way it is.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Rashar said:
The only device I believe you should ever have to root/unlock /jailbreak is the IOS platform. As you probably know, you are extremely limited to any customization with an IOS device. Under the android platform, I find that there are many flavours of customization under the stock setting already. I've ran the TF700T with the latest updates and firmware for the past few months and performance is still optimal ... I also bet that if you had my tablet side by side next to a rooted/unlocked TF700T tablet, you wouldn't be able to tell the difference from a performance perspective. I'm only speaking from a standard user point of view. I can see where a developer may want root access and or someone who wants to learn how to program the OS, create custom ROMS etc., however for the casual user, I'd leave it the way it is.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
I guarantee if you unlocked and installed a custom rom you would be blown away with how slow stock is Seriously, how do you know if you haven't done it? Seems like a strange challenge you have set. BTW I don't know one single person who has unlocked and gone to a custom rom who would go back to locked stock because performance is that different. You just don't know it.
sbdags said:
I guarantee if you unlocked and installed a custom rom you would be blown away with how slow stock is Seriously, how do you know if you haven't done it? Seems like a strange challenge you have set. BTW I don't know one single person who has unlocked and gone to a custom rom who would go back to locked stock because performance is that different. You just don't know it.
Click to expand...
Click to collapse
A significant reason for increased performance on custom ROMS is that the kernel they use allows for overclocking usually to 1.8GHZ. Just FYI in the interest of full disclosure.
It is not the ONLY reason but a big part of why they look/feel so much faster.
hx4700 Killer said:
A significant reason for increased performance on custom ROMS is that the kernel they use allows for overclocking usually to 1.8GHZ. Just FYI in the interest of full disclosure.
It is not the ONLY reason but a big part of why they look/feel so much faster.
Click to expand...
Click to collapse
Yes kernel tweaking brings huge benefits but there are plenty of other tweaks that bring the perks as well outside the kernel
Hello everyone, I just joined XDA and hope to be a successful contributor to this amazing community. This is my first post, hope it will be of help.
I can confirm that 10.4.4.25 did not break the downgrade option. Like others already suggested, make sure you're using the firmware which matches your device (WW/US/etc.) and you should be fine.
I Just got my device tonight from ASUS (RMA due to crashes every 2.5 days on the clock, black lines every few seconds, extremely laggy).
My precious came with 10.4.4.23 and I upgraded it to 10.4.4.25 to check the performance and black lines issue. With 25 it still lags a little but less than 23 and other earlier firmwares. I ran these tests on 23 then on 25:
1. For real life performance (don't care about synthetic benchmarks) I updated all the apps simultaneously. Both firmwares were laggy but 25 was much less than 23.
2. The black line is still there in 25 but much less than 23. I could reproduce it only with the black hole live wallpaper test which is a very good sign as in 23 I reproduced it a couple of times without the black hole live wallpaper.
After these tests I downgraded successfully to 9.4.5.30 (US) in order to root (need that for Avast FW) with no problems at all. Now I will go root it.
Update: Successfully rooted and upgraded back to 10.4.4.25
G0llum said:
After these tests I downgraded successfully to 9.4.5.30 (US) in order to root (need that for Avast FW) with no problems at all. Now I will go root it.
Update: Successfully rooted and upgraded back to 10.4.4.25
Click to expand...
Click to collapse
I downgraded also to clear a few things. After that, I went back in and went to Settings and check updates and nothing show up. How did you upgraded back to the latest version? Can you share your method?
Thank you much.
ils01 said:
I downgraded also to clear a few things. After that, I went back in and went to Settings and check updates and nothing show up. How did you upgraded back to the latest version? Can you share your method?
Thank you much.
Click to expand...
Click to collapse
Are you rooted? If you are you need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090
buhohitr said:
Are you rooted? If you are you need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090
Click to expand...
Click to collapse
I am rooted now (but still locked). Can I jump directly to 10.4.4.25 using dlpkgfile without doing other middle steps?
Edit: Tried going straight to 10.4.4.25 and failed. No OTA either.
ils01 said:
I am rooted now (but still locked). Can I jump directly to 10.4.4.25 using dlpkgfile without doing other middle steps?
Click to expand...
Click to collapse
No you can't, you need to upgrade to JB .16, then .18 then you can jump to .25.
buhohitr said:
No you can't, you need to upgrade to JB .16, then .18 then you can jump to .25.
Click to expand...
Click to collapse
Thank you very much. Will do that.
ils01 said:
I downgraded also to clear a few things. After that, I went back in and went to Settings and check updates and nothing show up. How did you upgraded back to the latest version? Can you share your method?
Thank you much.
Click to expand...
Click to collapse
OTA. Immediately after restart the tablet started downloading the update automatically... I postponed the update installation and then rooted, installed voodoo, created su backup, temp un-rooted and only then applied the OTA.
G0llum said:
OTA. Immediately after restart the tablet started downloading the update automatically... I postponed the update installation and then rooted, installed voodoo, created su backup, temp un-rooted and only then applied the OTA.
Click to expand...
Click to collapse
Thanks for the update.
Mine did not see any update regarless of multiple checkings performed (this was done before any rooting attempted). I am in the process of dowloading dlpkgfiles and slowly doing the hard way.
Update: After I reflashed back to 9.4.5.30 to root, I went on and started updating using dlpkgfile started with .16, .18, .20, .23, and finally .25. All is good now. However, I had a few errors when going from .16 to .18 due to getting incorrect/wrong dlpkgfile.
Thank you for everyone's help.