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.
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.
I'm at wit's end here...
I had to get a replacement TF300, and it came with .26. I downgraded to .17, rooted, OTA Rootkeeper'ed SU, then accepted the OTA update.
The update FAILED (green robot with red ! above). I powered down, rebooted.
Since then, I cannot get my device to find any OTA updates. I tried manually installing .29 - then no update. I installed .30 manually .. no update to JB.
I've force stopped DMClient and CMClient - cleared data/cache and cold booted as directed from some other posts.
Still no OTA.
While I realize I can do manual updates from this point forward, I'd like JB back - and so far, no manual installer of that.
I appreciate any help - this is making me nuts.
darkuni said:
I'm at wit's end here...
I had to get a replacement TF300, and it came with .26. I downgraded to .17, rooted, OTA Rootkeeper'ed SU, then accepted the OTA update.
The update FAILED (green robot with red ! above). I powered down, rebooted.
Since then, I cannot get my device to find any OTA updates. I tried manually installing .29 - then no update. I installed .30 manually .. no update to JB.
I've force stopped DMClient and CMClient - cleared data/cache and cold booted as directed from some other posts.
Still no OTA.
While I realize I can do manual updates from this point forward, I'd like JB back - and so far, no manual installer of that.
I appreciate any help - this is making me nuts.
Click to expand...
Click to collapse
im in the same boat as you i would also like help
joeyman08 said:
im in the same boat as you i would also like help
Click to expand...
Click to collapse
I am also in the same boat as I have an unlocked bootloader and will no longer receive OTA's from ASUS. We just have to be patient for another day or 2 and ASUS will post the JB Firmware on their site here:
http://support.asus.com/download.as...er Pad TF300T&os=32&hashedid=8BmzkQ4yoz5WzBrW
---------- Post added at 10:17 AM ---------- Previous post was at 10:11 AM ----------
But who wants to be patient. THere is always the option of updating manually. Thank krabappel2548 for this one!
http://forum.xda-developers.com/showthread.php?t=1845377
I will give the manual update a go. Thanks!
The manual process requires unlocking the bootloader. Not sure I'm ready to do that.
I'm open to other options.
darkuni said:
The manual process requires unlocking the bootloader. Not sure I'm ready to do that.
I'm open to other options.
Click to expand...
Click to collapse
Don't do all that crap. Do this. I did. Others as well.
Reference: http://forum.xda-developers.com/showthread.php?t=1840540
1) Found the correct OTA file. Someone posted it here for my US MODEL. If your WW or JP or something else, you'll need a different file.
http://forum.xda-developers.com/show...840397&page=11
2) I downloaded that file, named it dlpkgfile and put it in /cache/ (I also kept a copy in /sdcard so I can simply recopy it if/when it failed to update because of some missing app or something again)
3) I created a file called 'command' and put it in /cache/recovery with the contents of that file being as follows(without quotes): "--update_package=/cache/dlpkgfile". (I also kept a copy in /sdcard so I can simply recopy it if/when it failed to update because of some missing app or something again)
4) Now just run the update. To do this, make sure you do all your prep work (Voodoo OTA root keeper, supersu binary installed and run at least once, all original system apps in place. yada yada yada. To run the update shut down your tf300. and then start it holding the POWER and VOLUME DOWN. Keep holding it until you see writing appear. when the writing appears release and press VOLUME UP within 5 seconds of those words appearing.
5) you'll see the normal asus upgrade spin up.... and either complete or fail. If it fails, check your log file in /cache/recovery and see WHY it failed. Fix why it failed, and restart from step 1.
We have a winner! I had the command and dlpkg file ... what I didn't have was the boot process to enact it.
WONDERFUL! I'm safe for one more update
Hi people. thinking of unlocking, but afraid of brick. my tablet is funny.
every update that came through, never auto installed. Had to do it manually.
ALSO, voodoo never worked.
stock Rom, locked, jelly bean.
thinking of unlocking to regain root.
i miss it!
Thanks
redheadplantguy said:
Hi people. thinking of unlocking, but afraid of brick. my tablet is funny.
every update that came through, never auto installed. Had to do it manually.
ALSO, voodoo never worked.
stock Rom, locked, jelly bean.
thinking of unlocking to regain root.
i miss it!
Thanks
Click to expand...
Click to collapse
You don't need to unlock to get root back. Since your OS is iffy, I suggest to should do a clean flash and put everything back to normal.
Yes. i heard only way to root was to unlock JB was downgrade, then reroot. but, i don't know if voodoo would work after update. it's failed 3 times
redheadplantguy said:
Yes. i heard only way to root was to unlock JB was downgrade, then reroot. but, i don't know if voodoo would work after update. it's failed 3 times
Click to expand...
Click to collapse
I will make it work for you. Downgrade back to .30, re root, now here is the trick part, after you root, you should have superuser on your device, open up superuser(keep it open), then download rootcheck from the market to verify that you have root, now download superSU from the market, open it up, it will do the update.Now download Voodoo OTA root keeper, open it up and verify that all the boxes does have check mark to it except one, when you click save button the last box will be checked and now you have the option to "temp" unroot, click on this to save root. Go back to your notification, then click update to JB. Your device will shutdown and do the upgrade. Once it's done, open up OTA root keeper and click restore, bam you have root back.
Cool. how do i downgrade without unlocking
redheadplantguy said:
Cool. how do i downgrade without unlocking
Click to expand...
Click to collapse
Very simple:
Download .30 from Asus website, unzip it, now you have a zip file called EP201_768_SDUPDATE
Copy this to the root of your external sdcard, put it back to your device.
Turn off your tab. Hold down volumedown+powerbutton to get to stock recovery and once you see the white text displayed,let go both buttons, it automatic downgrade for you.
If you copy the file to the root of your internal sdcard then you just reboot and it will install for you.
thank you. gonna try this right now. I'll let you know in a bit.
buhohitr said:
Very simple:
Download .30 from Asus website, unzip it, now you have a zip file called EP201_768_SDUPDATE
Copy this to the root of your external sdcard, put it back to your device.
Turn off your tab. Hold down volumedown+powerbutton to get to stock recovery and once you see the white text displayed,let go both buttons, it automatic downgrade for you.
If you copy the file to the root of your internal sdcard then you just reboot and it will install for you.
Click to expand...
Click to collapse
Didn't work. Unzipped file was named something else, I renamed it to what you said. White letters came up, I let go, and there was 4 tiles on screen. One said rck, one Android, one USB, one wipe data.
Tried again with original filename. Downgrading now.
(hopeful)
redheadplantguy said:
Didn't work. Unzipped file was named something else, I renamed it to what you said. White letters came up, I let go, and there was 4 tiles on screen. One said rck, one Android, one USB, one wipe data.
Tried again with original filename. Downgrading now.
(hopeful)
Click to expand...
Click to collapse
Wait, when you download the zip from Asus web site the file name should be US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip right? and when you unziped it should be this EP201_768_SDUPDATE.zip? So what is the file name when you unziped?
buhohitr said:
Wait, when you download the zip from Asus web site the file name should be US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip right? and when you unziped it should be this EP201_768_SDUPDATE.zip? So what is the file name when you unziped?
Click to expand...
Click to collapse
Us_epad-user-.9.4.5.30
It downgraded wiped all data too. Rooted and getting ready to try your advice about updating. I never heard i had to temp unroot first. Good luck to me. I'll let you know
buhohitr said:
Wait, when you download the zip from Asus web site the file name should be US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip right? and when you unziped it should be this EP201_768_SDUPDATE.zip? So what is the file name when you unziped?
Click to expand...
Click to collapse
Crap. Lost root when updated back to jelly bean. Tried twice. Voodoo has no checkmark by protected copy available. Might take it to best buy. I have 2 year plan on it.
Tried a 3 rd time cause I thought manually updating many have been a problem, but "check for update" still shows none. Anytime firmware came through, never auto updated. They always failed.
Thinking of just returning it and have them get me another
redheadplantguy said:
Crap. Lost root when updated back to jelly bean. Tried twice. Voodoo has no checkmark by protected copy available. Might take it to best buy. I have 2 year plan on it.
Tried a 3 rd time cause I thought manually updating many have been a problem, but "check for update" still shows none. Anytime firmware came through, never auto updated. They always failed.
Thinking of just returning it and have them get me another
Click to expand...
Click to collapse
You only can do manual downgrade to .30, but you must do OTA update from .30 to JB to preserve root. If you manually upgraded, it will wipe everything before upgrade. After you finished manual upgrad with .30 and when the os came up, and you connect it to the internet it should automatically download JB to your device and prompt you to upgrade, this is not happening??
buhohitr said:
You only can do manual downgrade to .30, but you must do OTA update from .30 to JB to preserve root. If you manually upgraded, it will wipe everything before upgrade. After you finished manual upgrad with .30 and when the os came up, and you connect it to the internet it should automatically download JB to your device and prompt you to upgrade, this is not happening??
Click to expand...
Click to collapse
No. Every firmware, .26 .30 and JB, would download but fail installation. Now, I'm clicking " check for update" but it says none available
Rooted and back to ICS, but really miss JB too.
buhohitr said:
I will make it work for you. Downgrade back to .30, re root, now here is the trick part, after you root, you should have superuser on your device, open up superuser(keep it open), then download rootcheck from the market to verify that you have root, now download superSU from the market, open it up, it will do the update.Now download Voodoo OTA root keeper, open it up and verify that all the boxes does have check mark to it except one, when you click save button the last box will be checked and now you have the option to "temp" unroot, click on this to save root. Go back to your notification, then click update to JB. Your device will shutdown and do the upgrade. Once it's done, open up OTA root keeper and click restore, bam you have root back.
Click to expand...
Click to collapse
I wanted to thank you. The first tablet overheated and suffered a meltdown. This worked on the replacement.
Thanks a bunch. I have rooted JB now
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
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