Related
Whenever I try to update, it will restart. Then an android with an orange progress bar will come up but in the middle, it will stop and the Android with the triangle with exclamation point inside would appear??
any solutions?
My version is in 3.2
What are you trying to update and how?
tweak89 said:
What are you trying to update and how?
Click to expand...
Click to collapse
I think I'm updating the tablet? I'm doing it OTA when I clicked check updates on the About Tablet area?
Are you running a stock system? Rooted? Any mods, kernels, custom recovery, buttons, languages, layouts, etc?
The update checks a lot of pieces before it will update the files, and if anything is different, it will fail.
sent from my cyanogen(mod) vision
gee one said:
Are you running a stock system? Rooted? Any mods, kernels, custom recovery, buttons, languages, layouts, etc?
The update checks a lot of pieces before it will update the files, and if anything is different, it will fail.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I'm running stock but I do have it rooted. Other than that, nothing else. I haven't even flashed recovery.
How did you root? Which method? Homebrew?
The stock recovery might spit out a log file that will show you what is failing the update.
It's in /cache/recovery/log or maybe last_log.
You can use adb to pull it or copy it to your sdcard with a file explorer.
sent from my cyanogen(mod) vision
gee one said:
How did you root? Which method? Homebrew?
The stock recovery might spit out a log file that will show you what is failing the update.
It's in /cache/recovery/log or maybe last_log.
You can use adb to pull it or copy it to your sdcard with a file explorer.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I used the root toolkit v7 that can be foundon the development section. I'm thinking that if I unroot the transformer, the update could work?
Or maybe if I just downloathe firmware from the asus website, will it work better? Though I don't know how to install it.
You have a few options:
1) find the recovery log and figure out what is causing the flash to fail. Replace the deviant file using your superuser powers.
Or
2) download the 8.6.5.9 stock firmware from ASUS and flash that, then perhaps the OTA will work.
Or
3) get freaky with the command line and cook up some insecure blobs or images to flash
I think option 2 would be easiest, although I don't know if it will wipe your data. The download is a zip file, which you unzip and copy your external sdcard. I think is should be a folder named ASUS/Update/some other zip. The whole folder structure gets copied to the external sdcard so that the ASUS folder is at the root of the ext sdcard. When you insert it into the slot, your TF will recogize it and ask you if you want to flash it.
At some point ASUS will probably release the full stock rom on their website and you can flash that to update to the latest and greatest.
sent from my cyanogen(mod) vision
gee one said:
You have a few options:
1) find the recovery log and figure out what is causing the flash to fail. Replace the deviant file using your superuser powers.
Or
2) download the 8.6.5.9 stock firmware from ASUS and flash that, then perhaps the OTA will work.
Or
3) get freaky with the command line and cook up some insecure blobs or images to flash
I think option 2 would be easiest, although I don't know if it will wipe your data. The download is a zip file, which you unzip and copy your external sdcard. I think is should be a folder named ASUS/Update/some other zip. The whole folder structure gets copied to the external sdcard so that the ASUS folder is at the root of the ext sdcard. When you insert it into the slot, your TF will recogize it and ask you if you want to flash it.
At some point ASUS will probably release the full stock rom on their website and you can flash that to update to the latest and greatest.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
Owww. so 8659 is not the latest but the one on OTA? Will I lose root if flash that? and does root work on the newest update?
Yes, you will lose root and any custom recovery if you flash the stock image from the ASUS website. I think the tools in the dev section will still root as long as you have SBK v1 I.e., nvflash works on your tf. You rooted once, so it should be fine.
sorry for posting new thread but I don't know where to ask...can anybody please tell me tge new update 4.5.269 and someting3..is it the new version of gingerbread,is it safe to update..please tell me...
The new update is 4.5.629. It goes from Gingerbread 2.3.3 to Gingerbread 2.3.4, so a slight update. There are a few bug fixes, but it has a number of undesirable things.
1) 4.5.629 is currently not rootable
2) You cannot simply return to an earlier version via SBF.
You can overcome the first by using Voodoo Rootkeeper or similar to root on your current version, back up root with Rootkeeper and then update.
Recently, a method was found for this release to unbrick phones damaged by attempts to SBF or from bad ROMs: http://rootzwiki.com/topic/23207-how-to-sbf-unbricking-root-d2g-629 This also allows users who did upgrade to 4.5.629 to return to the previous version, root there and then upgrade again.
So it is sort of safe, but not ideal. The changelog is here, decide if the bug fixes are important enough for the added inconvenience
http://support.verizonwireless.com/pdf/system_update/droid_2_global.pdf
ok...thank u very much +1..I prefer not to update for now,and by mistake ,i select yes button in the update prompt,and its in the pull down bar,stucked and is ready to start downloading as soon as I connect to wi-fi,how will I cancel the download
You can block the update by renaming these files (e.g., append ".bak" to each filename):
/system/app/BlurUpdater_VZW.apk
/system/app/BlurUpdater_VZW.odex
Since these are in /system, renaming them requires root privileges and a root-enabled file manager (such as Root Browser Lite, available in the Google Play store).
ok..thanks,will do that,but after doing that,will I be able ro manually update it,or all the updates have been blocked???
Renaming those files will disable the OTA update client completely. You can still manually install an update by rebooting into recovery, but you will first have to download the update file from another source, rename it to "update.zip", and place it in the root level of your SD card.
Of course, you can also change those files back to their original names to re-enable OTA updates at any time.
jabberwockish said:
Renaming those files will disable the OTA update client completely. You can still manually install an update by rebooting into recovery, but you will first have to download the update file from another source, rename it to "update.zip", and place it in the root level of your SD card.
Of course, you can also change those files back to their original names to re-enable OTA updates at any time.
Click to expand...
Click to collapse
okok..thanks man +1
edit : i got this 'failed to rename file' error ..what should I do??
What app did you use to try to rename the files?
Did you root your phone before attempting the rename? (See http://www.psouza4.com/droid3/ for instructions.)
jabberwockish said:
What app did you use to try to rename the files?
Did you root your phone before attempting the rename? (See http://www.psouza4.com/droid3/ for instructions.)
Click to expand...
Click to collapse
the app that u suggested me,root browser lite and my phone was rooted and also have been granted superuser's permissions..
You didn't remount /system in Read/Write mode.
Gasai Yuno said:
You didn't remount /system in Read/Write mode.
Click to expand...
Click to collapse
please tell me how to do that
Root Explorer has a button for that.
“adb remount” when connected to a PC with USB debugging enabled will do that as well.
It's also possible to do from the terminal emulator, however I don't remember the exact command.
i can't find that button,by long pressing the file/folder or what?
It looks like this app defaults to RW once it gets superuser permission (GY was referring to Root Explorer, a different app). How about copying a system file, does that work?
I just got the OTA for the .30 firmware so I put back the stock build.props and the two client apk and odex files, but when trying to update I got an image of a fallen over android with a red exclamation.
What is wrong?
Sent from my ASUS Transformer Pad TF700T
Same for me
Isn't that the stock recovery screen?
see the install logs in /cache/recovery/ for details, there you should find a reason why it failed
the file size is 4.5kb. The text viewer shows an empty file.
usern ameisval idandnot said:
the file size is 4.5kb. The text viewer shows an empty file.
Click to expand...
Click to collapse
The actual file size of the .30 update is over 200 MB. I'm guessing file didn't download right.
My tablet wouldn't auto update .26 OR .30
Had to install from micro SD. Not sure why. I'm rooted, but still locked and running stock.
usern ameisval idandnot said:
the file size is 4.5kb. The text viewer shows an empty file.
Click to expand...
Click to collapse
Same, I can't open the logs either.
hshah said:
Same, I can't open the logs either.
Click to expand...
Click to collapse
I had the same and the reason was that I had a modified version of file build.prop (modified to have a different dpi value). And the OTA is checking wether or not you have a stock version of build.prop (and also of another file but don't remember which one) and if it founds that your tablet is not stock anymore at 100% then it will fail with the android/red triangle.
To resolve there are 2 ways :
- restore back the stock version of build.prop (and other file)
or
- do manual update (by downloading the .30 firmware from Asus support web site and putting on /sdcard and rebooting)
ps : that issue has already been discussed several times and you could find more detailed "how to" in other threads
Ghorin said:
I had the same and the reason was that I had a modified version of file build.prop (modified to have a different dpi value). And the OTA is checking wether or not you have a stock version of build.prop (and also of another file but don't remember which one) and if it founds that your tablet is not stock anymore at 100% then it will fail with the android/red triangle.
To resolve there are 2 ways :
- restore back the stock version of build.prop (and other file)
or
- do manual update (by downloading the .30 firmware from Asus support web site and putting on /sdcard and rebooting)
ps : that issue has already been discussed several times and you could find more detailed "how to" in other threads
Click to expand...
Click to collapse
PS. If you read my post, I have already restored the stock versions of the necessary files so this issue should not occur.
How to's didnt help because I have a 100% Original stock device.
If anyone still have trouble updating.
As d14b0ll0s said, use a root file browser and see bottom of the /cache/recovery/last_log file right after reset from failed update. If you have trouble opening up that file (empty) copy it to some folder on sdcard (Documents, etc.) and open that.
In my case, i forgot to rename CMClient back to .apk
I dunno if this will help but I have a stock 700. I wanted to reflash the 30 update as I was having problems with the OTA I got. I d/l from Asus the correct US version and unzipped it and copied the zip file I got from that to my root on the sdcard. All this was done on the PC. I got the same error as you all wheb I tried to perform the flash. Then I changed the name of that zip file to EP201_768_SDUPDAT.zip while it was on the PC and copied that to the sdcard again. Followed the alternative firmware update method (found here http://forum.xda-developers.com/showthread.php?t=1755576) and it worked. It helped as most of the weird crap has stopped happening and now I have the normal crap happening like everyone else.
My Solution was to kill the Pad. Now I updated to JB. Works perferctly.
.26 & .30 always did the same, and i had to manually update from SD card. NOW, same thing with JB. Voodoo has also never worked. I have a locked, rooted, stock device. I think I'm gonna take it back to best buy since i have protection plan.
Does anyone have a dump of their system folder? I deleted loads of apps which is stopping me upgrading to JB
Sent from my GT-I9300
My device complains about a file called Vibe_CN.apk.
Does anyone have this file on WW .30 firmware and is able to upload it somewhere?
I'm pretty sure I haven't fiddled with this file, but according to the log below, it doesn't match the expected hash...
Verifying current system...
file "/system/app/Vibe_CN.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/Vibe_CN.apk", "c36a7d96df630bfa6ab4e6a9484ac71f88d7c677", "297e177c2fd02d277792fe9b23b57c31ab67642c")
assert failed: apply_patch_check("/system/app/Vibe_CN.apk", "c36a7d96df630bfa6ab4e6a9484ac71f88d7c677", "297e177c2fd02d277792fe9b23b57c31ab67642c")
E:Error in /cache/dlpkgfile
Does anyone know what dir the ota files are downloaded too? I would like to capture the ota and see whats in there.
TheJokah said:
Does anyone know what dir the ota files are downloaded too? I would like to capture the ota and see whats in there.
Click to expand...
Click to collapse
I did it earlier, have to be rooted to see the file that's downloaded. If you're using a root explorer search for "dlpkgfile" that's the name of the newest OTA at least, I made a copy on my SD card so I could keep putting it in the right dir and avoid downloading it all over again. Since I tried all my options i'm back to unrooted, still can't upgrade from g to o.
I don't remember the exact directory, somewhere in /etc/ if I recall.
ajent said:
I did it earlier, have to be rooted to see the file that's downloaded. If you're using a root explorer search for "dlpkgfile" that's the name of the newest OTA at least, I made a copy on my SD card so I could keep putting it in the right dir and avoid downloading it all over again. Since I tried all my options i'm back to unrooted, still can't upgrade from g to o.
I don't remember the exact directory, somewhere in /etc/ if I recall.
Click to expand...
Click to collapse
I'm having the same issue with upgrading 10G. maybe there is a way in the ota Package
EDIT:
I found this link http://forum.xda-developers.com/showthread.php?t=2699123 to force an update using the dlpkgfile from ota. I wonder if it could work for G4 also??
@TheJokah @ajent. Don't need to be rooted. Root Browser will be able to view the directory without root permissions. (I use it all the time to browse system partitions and files on unrooted devices). You can do a lot with Root Browser without root. You just can't make changes.
When the fota is available you will find it in /cache/fota
I have captured several OTAs for various devices this way...
EDIT: Make sure to copy the file after it downloads and before restart, otherwise the file will be deleted before you get it.
That is good info, thanks.
I'm pretty convinced flashfire installing the xposed zip does something that isn't reverted when flashing the unrooted system image. I used my limited knowledge to look at that xposed zip and it seems like only modifications are made to /system so it should be removed when flashing back unrooted image. I really don't know, but hope somebody can figure it out lol.
after i rooted my phone i still get ota update.
it will brick my phone if i installed it ? or it is safe to install it ?
plz help
Can't say whether it'll brick you phone, only way to know is to try.
Nothing will happen, the update will load, then you press install, after reboot the system update error will appear, it will not crash the system and root will not delete it. Rooting the OTA will not install the update, only through Odin.
dnsvoronkov said:
Nothing will happen, the update will load, then you press install, after reboot the system update error will appear, it will not crash the system and root will not delete it. Rooting the OTA will not install the update, only through Odin.
Click to expand...
Click to collapse
Yes. You are correct. It will not install the OTA update.
If I want to install the new update as rooted user ,what's the procedure? Will it erase all the my apps and data. Thanks
llranga said:
Yes. You are correct. It will not install the OTA update.
If I want to install the new update as rooted user ,what's the procedure? Will it erase all the my apps and data. Thanks
Click to expand...
Click to collapse
Just for anyone one like me who are in doubt on upgrading magisk tooted stock rom
i was in android 12.XX and wanted to upgrade to android 13.
1. download firmware
2. extract downloaded folder using 7zip
3. Copy AP file to your phone using ADB push (copy and paste may corrupt large files)
4. Open Magisk app in your phone and patch the AP file
5. copy patched AP file from phone to PC using ADB pull (copy and paste may corrupt large files)
6. Flash patched AP, BL, CP and HOME_CSC instead of CSC_ODM using Odin (must not flash CSC_ODM)
7. You are ready to go with upgraded firmware.