Related
This doesn't seem like a common problem, but I found a few people who got this issue.
My TF700 have been on 4.0.1 and it does not upgrade to 4.1 JB even though it has been released for a week. I have then used the custom method to force update to 10.4.4.16 - JB. However, I know 4.4.18 just came out and I am afraid it still would not update OTA.
Anyone has a solution for this??
wakkigy said:
This doesn't seem like a common problem, but I found a few people who got this issue.
My TF700 have been on 4.0.1 and it does not upgrade to 4.1 JB even though it has been released for a week. I have then used the custom method to force update to 10.4.4.16 - JB. However, I know 4.4.18 just came out and I am afraid it still would not update OTA.
Anyone has a solution for this??
Click to expand...
Click to collapse
Have to try to go into settings->about tablet-> check for update?? I assumed that your device is locked/rooted with pure stock JB, no modification, no system app freezing?
buhohitr said:
Have to try to go into settings->about tablet-> check for update?? I assumed that your device is locked/rooted with pure stock JB, no modification, no system app freezing?
Click to expand...
Click to collapse
Yup checking for update has nothing
Before I upgraded to 10.4.4.16 the device was totally stock, and it just does not update for the longest time.
Since I had updated to 10.4.4.16, I have then unlocked, rooted. No mod, no system app freeze.
Still no update notice for 10.4.4.18
wakkigy said:
Yup checking for update has nothing
Before I upgraded to 10.4.4.16 the device was totally stock, and it just does not update for the longest time.
Since I had updated to 10.4.4.16, I have then unlocked, rooted. No mod, no system app freeze.
Still no update notice for 10.4.4.18
Click to expand...
Click to collapse
Well there's your problem if you unlocked.
No automatic OTAs for unlocked tabs.
Thats OK said:
Well there's your problem if you unlocked.
No automatic OTAs for unlocked tabs.
Click to expand...
Click to collapse
Thanks - Thats OK :good:
I didn't realized it was that and now I went back to read the All-In-One Guide For Asus Infinity thread detail; I do see that in the note. I am fine with doing manual updates but was just bothered the device doesn't function properly**
I guess now even the tablet will have to be manual updated OR eventually use custom rom :fingers-crossed:
wakkigy said:
Thanks - Thats OK :good:
I didn't realized it was that and now I went back to read the All-In-One Guide For Asus Infinity thread detail; I do see that in the note. I am fine with doing manual updates but was just bothered the device doesn't function properly**
I guess now even the tablet will have to be manual updated OR eventually use custom rom :fingers-crossed:
Click to expand...
Click to collapse
Yup. Assuming you're into the stock experience and have the keyboard (thus appreciating the shortcut keys), CleanROM is eyeing you. Your 700 is behaving normally, so that's one problem out of the way.
When I come back to home, i saw that update is available. But I forgot temporary disabled root (ota root keeper). My device started update, but it stoped in bootloader (deat android with red triangle) My tf started without update, and now I can`t OTA (update is not available for you). Can I redownload update, and update soft one more time? How can I do this?
msmajerczak said:
When I come back to home, i saw that update is available. But I forgot temporary disabled root (ota root keeper). My device started update, but it stoped in bootloader (deat android with red triangle) My tf started without update, and now I can`t OTA (update is not available for you). Can I redownload update, and update soft one more time? How can I do this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1
Would the above link be of any help?
I had something kinda weird happen just now.
I originally unlocked and rooted the moment I got the tablet, and manually installed 10.4.4.16. Everything works great.
I just finished manually updating to 10.4.4.18 and after a reboot, it said I have a system update available, which was 10.4.4.16.....
[/doublerainbowvoice] Does this mean I still got an OTA even though I'm unlocked and rooted?
Jimmah555 said:
I had something kinda weird happen just now.
I originally unlocked and rooted the moment I got the tablet, and manually installed 10.4.4.16. Everything works great.
I just finished manually updating to 10.4.4.18 and after a reboot, it said I have a system update available, which was 10.4.4.16.....
[/doublerainbowvoice] Does this mean I still got an OTA even though I'm unlocked and rooted?
Click to expand...
Click to collapse
Make sure you delete the old zip file in your sd card.
buhohitr said:
Make sure you delete the old zip file in your sd card.
Click to expand...
Click to collapse
Oh I know that. I just think it's funny that it wants me to "update" to an older software version.
Thats OK said:
http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1
Would the above link be of any help?
Click to expand...
Click to collapse
After that i lost root
msmajerczak said:
After that i lost root
Click to expand...
Click to collapse
Sorry man!
Looks you and me are in the same boat.
I just threw up my hands and did another factory reset last evening.
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
go to the root of your external sd card and delete all the zip file(s), you probably left it there when you downgrade. Also delete file from internal sdcard in /cache/recover if any. Once you unlocked you shouldn't receive anymore OTA.
redheadplantguy said:
I finally got the nerve to unlock. I had to downgrade doing it.
Click to expand...
Click to collapse
Strange, many people said the unlock tool works fine on JB.
redheadplantguy said:
Now, I heard after unlocking, an ota will brick tablet.
Click to expand...
Click to collapse
Where?
I don't say it cannot brick your tablet, but I am not aware of any reports that it does.
redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
MartyHulskemper said:
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
Click to expand...
Click to collapse
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
redheadplantguy said:
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
Click to expand...
Click to collapse
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
buhohitr said:
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
Click to expand...
Click to collapse
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
redheadplantguy said:
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
Click to expand...
Click to collapse
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
buhohitr said:
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
Click to expand...
Click to collapse
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
redheadplantguy said:
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
Click to expand...
Click to collapse
That does sound like it actually flashed something (at least partly). I would run that unlock tool another time just to be sure I wouldn't get into trouble down the road (Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on. Flashing over stock, well... minor nuisance, but it would be majorly inconvenient to have to flash root and stuff all the time.)
MartyHulskemper said:
Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on.
Click to expand...
Click to collapse
No, it just doesn't work. The updater-script inside the OTA package compares the checksums of the system apps to be patched, and aborts as soon as one doesn't match the previous stock ROM.
The only potential danger I see is the communication with the bootloader which kernel to boot - the OTA downloader (DMClient) somehow has to instruct the bootloader to load the recovery kernel to install the dlpkgfile from /cache, and if that process is still not understood by custom recovery creators (there were some problems apparently, I don't know if they are solved), you might end up with a device that only boots into the recovery and not into Android.
Thanks. I will.
Sent from my SGH-T679 using Xparent ICS Blue Tapatalk 2
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.
Hello:
I'm trying to root my JB (.25) TF700. Yesterday, I was able to downgrade to ICS, root, temp unroot and then install JB (.25). But - after installing JB, the TempRoot was gone. What's up with that?
Here's my method:
From JB (.25), downloaded ICS (.30), extracted it to MicroSD and downgraded without issue. I tried to do this through factory recovery (Volume Down, release and then Volume Up); however, I'd get the Android+red triangle error. Instead, I just inserted the card on the home screen and the system pushed the downgrade itself.
Once I installed ICS, I rooted without issue. Downloaded RootKeeper, created backup and temp unrooted.
Then, here's were I went wrong probably, used the same method as stated above to install the JB (.25) firmware. I downloaded .25 from ASUS, extracted onto MicroSD and then inserted the card at home screen. The OS prompted the firmware update and JB was installed. I did create a TempRoot (backup) before installing JB.
Like I said above, JB installed but TempRoot was gone. I'm assuming that I used the wrong technique for upgrading to JB. But I always seem to get the Android + red triangle when I go through recovery mode.
Any ideas? Thanks.
-lukin- said:
Hello:
I'm trying to root my JB (.25) TF700. Yesterday, I was able to downgrade to ICS, root, temp unroot and then install JB (.25). But - after installing JB, the TempRoot was gone. What's up with that?
Here's my method:
From JB (.25), downloaded ICS (.30), extracted it to MicroSD and downgraded without issue. I tried to do this through factory recovery (Volume Down, release and then Volume Up); however, I'd get the Android+red triangle error. Instead, I just inserted the card on the home screen and the system pushed the downgrade itself.
Once I installed ICS, I rooted without issue. Downloaded RootKeeper, created backup and temp unrooted.
Then, here's were I went wrong probably, used the same method as stated above to install the JB (.25) firmware. I downloaded .25 from ASUS, extracted onto MicroSD and then inserted the card at home screen. The OS prompted the firmware update and JB was installed. I did create a TempRoot (backup) before installing JB.
Like I said above, JB installed but TempRoot was gone. I'm assuming that I used the wrong technique for upgrading to JB. But I always seem to get the Android + red triangle when I go through recovery mode.
Any ideas? Thanks.
Click to expand...
Click to collapse
OK, what's going on here is you're using the Asus full firmware upgrade which will wipe your root. You need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090
It's a pain since you need to go one upgrade at a time -.30 then .16 then .18 you got the idea!
buhohitr said:
OK, what's going on here is you're using the Asus full firmware upgrade which will wipe your root. You need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090
It's a pain since you need to go one upgrade at a time -.30 then .16 then .18 you got the idea!
Click to expand...
Click to collapse
Thanks. Can't do one firmware upgrade, darn. How many increments are there?
-lukin- said:
Thanks. Can't do one firmware upgrade, darn. How many increments are there?
Click to expand...
Click to collapse
To do it right, .16,.18,.20,.23,.25 ...total of 5, (unless you unlock your device). You may get away with just .16,.18, then .25.(bootloader is the same after .18). Your auto OTA is not working??
buhohitr said:
To do it right, .16,.18,.20,.23,.25 ...total of 5, (unless you unlock your device). You may get away with just .16,.18, then .25.(bootloader is the same after .18). Your auto OTA is not working??
Click to expand...
Click to collapse
Well, at ICS .25, I checked for OTA and there was nothing. Not sure how long I should be waiting. I've had problems with OTA in the past and just assumed I screwed the pooch somehow. Should I be able to OTA at ICS .25?
Thanks.
-lukin- said:
Well, at ICS .25, I checked for OTA and there was nothing. Not sure how long I should be waiting. I've had problems with OTA in the past and just assumed I screwed the pooch somehow. Should I be able to OTA at ICS .25?
Thanks.
Click to expand...
Click to collapse
Well, I suggest at the least you should do .16, .18 then .25, since it's incremental change, one change depended on the previous change so some stuff may not working correctly if you decided to skip.
buhohitr said:
Well, I suggest at the least you should do .16, .18 then .25, since it's incremental change, one change depended on the previous change so some stuff may not working correctly if you decided to skip.
Click to expand...
Click to collapse
Okay - I have found all the firmwares here http://forum.xda-developers.com/showthread.php?t=1946456and here http://support.asus.com/download/options.aspx?SLanguage=en. I will try to do the incremental upgrades - but the step by step process isn't exactly clear from the link provided above. For example, what is the first step with "WW_epad-user-10.4.4.16.zip"? Do I extract the blob and if so so where to? How is "dlpkgfile" involved? Thanks.
-lukin- said:
Okay - I have found all the firmwares here http://forum.xda-developers.com/showthread.php?t=1946456and here http://support.asus.com/download/options.aspx?SLanguage=en. I will try to do the incremental upgrades - but the step by step process isn't exactly clear from the link provided above. For example, what is the first step with "WW_epad-user-10.4.4.16.zip"? Do I extract the blob and if so so where to? How is "dlpkgfile" involved? Thanks.
Click to expand...
Click to collapse
Both links you provide are full stock firmware, not going to work. You need dlpkgfile only, can be found here http://forum.xda-developers.com/showthread.php?t=1926147
Just download them and make sure the final name is dlpkgfile (no extention, exactly like that).
also download command file and the name is command (exactly like that, no extention)
copy them these directories:
command goes to /cache/recovery
dlpkgfile goes to /cache
Make sure the files are named exactly as shown above. No capitals, no file extensions, etc.
Make sure the permissions for both files are changed to RW-RW-R for both.
This is how it should be after copied:
/cache/recovery/command
/cache/dlpkgfile
power off, then boot into recovery and wait a 10sec it should update. Remember if it failed or boot back into the OS, you need to verify if the two files still there, one of them will be erase and you have to recopy then do it again.
buhohitr said:
Both links you provide are full stock firmware, not going to work. You need dlpkgfile only, can be found here http://forum.xda-developers.com/showthread.php?t=1926147
Click to expand...
Click to collapse
Thanks. I'm working on getting these downloaded. But I notice that the dlpkgfile is considerably smaller than full firmware. Is that right?
-lukin- said:
Thanks. I'm working on getting these downloaded. But I notice that the dlpkgfile is considerably smaller than full firmware. Is that right?
Click to expand...
Click to collapse
Yes, depend on how much upgrade, but they are much smaller around 14meg. Full firmware is around 455-485meg.
-lukin- said:
Thanks. I'm working on getting these downloaded. But I notice that the dlpkgfile is considerably smaller than full firmware. Is that right?
Click to expand...
Click to collapse
The dlpkgfile that updates from ICS to JB is almost 200 MB, the others are around 15 MB each.
buhohitr said:
Yes, depend on how much upgrade, but they are much smaller around 14meg. Full firmware is around 455-485meg.
Click to expand...
Click to collapse
We're in business. I've got ICS, rooted and JB .16 - now working on .18
Thanks for taking the time to help today
P.S. Never forget to unroot! That's how I got here in the first place. Cheers.
Not bad, you're a pretty smart guy after all.
Sent from my ASUS Transformer Pad TF700T using xda premium
Hi guys,
Just like other people I have also rooted my Note 3 and flagged/tripped the KNOX counter...
The issue first appeared when I was trying to upgrade from Android OS, v4.3 (Jelly Bean) to v4.4.2 (KitKat). The update notification popped, it took roughly 40 minutes to download the firmware and I was then prompted to install. The device then restarted automatically as usual and I received the "Failure to update" window. I have tried couple of times more in case something went wrong with the download but it didn't help. So I had to install the update manually from SamMobile, using Odin and wiping my phone data. Everything went well and I am now enjoying the KitKat version.
Today it seems a new update appeared around 26 MB and I am facing the same issue. After I download the update and hit install, the device will restart and then show the "Failure to update" window.
Is there any way to fix this? Does it mean I can never install the updates automatically?
Please advise and thanks in advance.
croussou said:
Hi guys,
Just like other people I have also rooted my Note 3 and flagged/tripped the KNOX counter...
The issue first appeared when I was trying to upgrade from Android OS, v4.3 (Jelly Bean) to v4.4.2 (KitKat). The update notification popped, it took roughly 40 minutes to download the firmware and I was then prompted to install. The device then restarted automatically as usual and I received the "Failure to update" window. I have tried couple of times more in case something went wrong with the download but it didn't help. So I had to install the update manually from SamMobile, using Odin and wiping my phone data. Everything went well and I am now enjoying the KitKat version.
Today it seems a new update appeared around 26 MB and I am facing the same issue. After I download the update and hit install, the device will restart and then show the "Failure to update" window.
Is there any way to fix this? Does it mean I can never install the updates automatically?
Please advise and thanks in advance.
Click to expand...
Click to collapse
Have you at any point tried to downgrade back to 4.3?
gee2012 said:
Have you at any point tried to downgrade back to 4.3?
Click to expand...
Click to collapse
Thanks for your prompt reply.
Why should I downgrade?*
*This is not me being an ass, just really wondering
Thanks again!
croussou said:
Thanks for your prompt reply.
Why should I downgrade?*
*This is not me being an ass, just really wondering
Thanks again!
Click to expand...
Click to collapse
I asked because some users tried to downgrade to 4.3 and now some can`t upgrade at all anymore except manualy You are not rooted atm right? How is your system status?
gee2012 said:
I asked because some users tried to downgrade to 4.3 and now some can`t upgrade at all anymore except manualy You are not rooted right?
Click to expand...
Click to collapse
Aha, interesting No I haven't tried to downgrade, but yes, I am rooted, I mentioned that in the original post
croussou said:
Aha, interesting No I haven't tried to downgrade, but yes, I am rooted, I mentioned that in the original post
Click to expand...
Click to collapse
Oke, well you can`t install official updates when you are rooted (modified the system)! I suggest you download Mobile Odin Pro from Play and flash the whole new rom from www.sammobile.com and keep root.
gee2012 said:
Oke, well you can`t install official updates when you are rooted (modified the system)! I suggest you download Mobile Odin Pro from Play and flash the whole new rom and keep root.
Click to expand...
Click to collapse
Right, so I can just receive the updates but not install them! that's convenient
Do I have to wipe everything again or just install the latest update? Because if I have to wipe everything each time there's an update, I may just cancel the whole update thing until there's something like a major update
croussou said:
Right, so I can just receive the updates but not install them! that's convenient
Do I have to wipe everything again or just install the latest update? Because if I have to wipe everything each time there's an update, I may just cancel the whole update thing until there's something like a major update
Click to expand...
Click to collapse
You don`t have to wipe as the updates atm are mostly bugfixes. Only wipe cache and dalvik cache after the flash.
gee2012 said:
You don`t have wipe as the updates atm are mostly bugfixes. Only wipe cache and dalvik cache after the flash.
Click to expand...
Click to collapse
Awesome then! From the description of Mobile ODIN Pro though it says "throw those firmware files on your SD...", where can I get those minor updates in order to download them?
croussou said:
Awesome then! From the description of Mobile ODIN Pro though it says "throw those firmware files on your SD...", where can I get those minor updates in order to download them?
Click to expand...
Click to collapse
Download the whole rom from here http://www.sammobile.com/firmwares/2/ and follow the instructions of mobile odin. You can`t install OTA`s.
gee2012 said:
Download the whole rom from here http://www.sammobile.com/firmwares/2/ and follow the instructions of mobile odin. You can`t install OTA`s.
Click to expand...
Click to collapse
Okay I think I got it, so each time there's an update I must download the whole ROM and flash it on top of the current? Since it's the same, it only updates the files that are needed while keeping the rest of the system intact.
croussou said:
Okay I think I got it, so each time there's an update I must download the whole ROM and flash it on top of the current? Since it's the same, it only updates the files that are needed while keeping the rest of the system intact.
Click to expand...
Click to collapse
Thats correct
gee2012 said:
Thats correct
Click to expand...
Click to collapse
You've been extremely helpful, thank you for taking the time to explain couple of things
Have a great weekend ahead!
croussou said:
You've been extremely helpful, thank you for taking the time to explain couple of things
Have a great weekend ahead!
Click to expand...
Click to collapse
You`re welcome bro