Database Info

[Q] Can't Update Transformer

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.

[Q] what is the new update??

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?

Looking for dir of ota files

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.

I'm rooted, phone is trying to update from 8.0.0.369 to 8.0.0.373 and it just...

It ends up in recovery mode so I just turn it off and boot up again and it says update failed. I realize it will lose root so I'll have to reroot but will it lock the bootloader again also? I'm just tired of seeing it everyday want to update so figured I'd let it do it but it does't seem to work. Is there a manual update file somewhere? I googled but I can't find it. Should I find the complete rom and re-install the newest version?

jeffrimerman said:
It ends up in recovery mode so I just turn it off and boot up again and it says update failed. I realize it will lose root so I'll have to reroot but will it lock the bootloader again also? I'm just tired of seeing it everyday want to update so figured I'd let it do it but it does't seem to work. Is there a manual update file somewhere? I googled but I can't find it. Should I find the complete rom and re-install the newest version?
Click to expand...
Click to collapse
Bootloader will stay unlocked. If it's an OTA it's trying to install it will fail IF it wants to patch ramdisk as you're rooted.
You can restore stock ramdisk and it should update correctly, but I'd use FullOTA instead for best compatibility.
You can install FullOTA either using HWOTA or installing TWRP (by Pretoriano80 as it has decryption support) and use HuRUpdater script to update.

ante0 said:
Bootloader will stay unlocked. If it's an OTA it's trying to install it will fail IF it wants to patch ramdisk as you're rooted.
You can restore stock ramdisk and it should update correctly, but I'd use FullOTA instead for best compatibility.
You can install FullOTA either using HWOTA or installing TWRP (by Pretoriano80 as it has decryption support) and use HuRUpdater script to update.
Click to expand...
Click to collapse
I have TWRP 3.2.1-0 since I installed Oreo. Is the full ota downloaded into my phone somewhere since it seems to download it fine then I can install it with TWRP? Or do I need to find it online somewhere. Since it ends up in TWRP after trying to install if it was someplace I can find then maybe I can just install whie in TWRP. I'll google for HuRpdater script or is it on here somewhere? I just googled but nothing came up.

jeffrimerman said:
I have TWRP 3.2.1-0 since I installed Oreo. Is the full ota downloaded into my phone somewhere since it seems to download it fine then I can install it with TWRP? Or do I need to find it online somewhere. Since it ends up in TWRP after trying to install if it was someplace I can find then maybe I can just install whie in TWRP. I'll google for HuRpdater script or is it on here somewhere? I just googled but nothing came up.
Click to expand...
Click to collapse
Updates go to /data/update/
But you can download it from http://pro-teammt.ru/firmware-database/ (download update.zip, public zip and data zip for your firmware. You can click the File list link after you have searched to find the public and hw data)
And HuRUpdater is found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
TWRP can't install huawei update.zips by default, so you'd have to download firmware then use HuRUpdater to flash it.

ante0 said:
Updates go to /data/update/
But you can download it from http://pro-teammt.ru/firmware-database/ (download update.zip, public zip and data zip for your firmware. You can click the File list link after you have searched to find the public and hw data)
And HuRUpdater is found here: https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
TWRP can't install huawei update.zips by default, so you'd have to download firmware then use HuRUpdater to flash it.
Click to expand...
Click to collapse
I found the files where you said, thanks. update_data_public.zip, update_MHA_L29_hw_usa.zip, and update.zip
When I read the instuction it calls for 3 files 2 of which are already spelled out correctly but looks like I need to rename the MHA file to update_all_hw.zip is this correct?
It also says to put the recovery image in the same folder if I want to keep custom recovery so sounds like it will wipe it if I don't. I'll have to download twrp 3.2.1-0 again
Ok this is interesting, I have 2 files in data with 6 digit names 151465 and 161808 and both have the 3 files but they are of different sizes but the exact same names as I mentioned before. Maybe better to go to the website you mentioned or I'll screw something up with them.
Figured out how to open the file list and can see the 3 files now so I'll get all 3. Update.zip is 2gb is that right? It's gonna take like 5 hours it says.

jeffrimerman said:
I found the files where you said, thanks. update_data_public.zip, update_MHA_L29_hw_usa.zip, and update.zip
When I read the instuction it calls for 3 files 2 of which are already spelled out correctly but looks like I need to rename the MHA file to update_all_hw.zip is this correct?
It also says to put the recovery image in the same folder if I want to keep custom recovery so sounds like it will wipe it if I don't.
Ok this is interesting, I have 2 files in data with 6 digit names 151465 and 161808 and both have the 3 files but they are of different sizes but the exact same names as I mentioned before. Maybe better to go to the website you mentioned or I'll screw something up with them.
When I click on the "update" hyperlink it just opens a new page and doesn't seem to start downloading. Maybe I need to do something else?
Click to expand...
Click to collapse
Rename the zip with HW in its name to update_all_hw.zip and Public to update_data_public.zip.
If recovery.img is present in the same dir as guru it will flash it back to recovery_ramdisk after update is flashed. It's to save a step so you don't have to reboot to fastboot to flash it again.
/data/update includes old/partial downloads too. So if you for example have used eRecovery before to download, but cancelled it, the update is still there. Same goes for system update. I would rather use firmware finder/teammt because you know those are completed zips.
On the site you can click on file list to show links to downloads, the update link rarely works anymore. It just parses data from hicloud but for some reason the update link always points to front page (or to search results if you have searched).
So just copy paste the update, public and Hw l29 links into a new tab to download.
jeffrimerman said:
Figured out how to open the file list and can see the 3 files now so I'll get all 3. Update.zip is 2gb is that right? It's gonna take like 5 hours it says.
Click to expand...
Click to collapse
That's correct.

It's going to erase everything isn't it? Rename the TWRP to "recovery" right? Since it's already a .img file I imagine I don't need to add ".img" right?

jeffrimerman said:
It's going to erase everything isn't it? Rename the TWRP to "recovery" right? Since it's already a .img file I imagine I don't need to add ".img" right?
Click to expand...
Click to collapse
Updating doesn't wipe. And HuRUpdater will tell you if it should wipe, it will also tell you if it will lock bootloader.
Yes, if you don't have "show extentions" turned on in Windows just rename it to recovery.

ante0 said:
Updating doesn't wipe. And HuRUpdater will tell you if it should wipe, it will also tell you if it will lock bootloader.
Yes, if you don't have "show extentions" turned on in Windows just rename it to recovery.
Click to expand...
Click to collapse
It didn't erase anything woooo hoooo. Thank you. I did loose root which will be easy to put back on. At the end if installing everything automatically there were 2 buttons on the bottom. One was erase cache/dalvik I think and the other was reboot so I just rebooted to be safe. Figured if it was buggy I could always go back and erase the cache/delvik but looks fine. Just checked and my TWRP is there so all is good

[FIX][PERSIST] Fingerprint not enrolling/Persist storage fix

Hey,
Tired of seeing this message when trying to enroll a fingerprint?
I have seen many people asking for fix and there has also been a file around here for the fix zip. But it was always hard to find that file so here it is.
Steps for fixing fingerprint:
Code:
1. Reboot to recovery
2. In the file manager, go to /persist/data/
3. Delete all the files named finger_0_x and finger_0_x.bak (finger_0_1, finger_0_1.bak,...)
4. Reboot and try again.
If it still doesn't work, flash the attachment zip in recovery.
This works wonders!!!
EDIT: Please notice that I am not the owner of the file!

Your zip file just killed my phone
not working

KamiMK said:
Hey,
Tired of seeing this message when trying to enroll a fingerprint?
I have seen many people asking for fix and there has also been a file around here for the fix zip. But it was always hard to find that file so here it is.
Steps for fixing fingerprint:
Code:
1. Reboot to recovery
2. In the file manager, go to /persist/data/
3. Delete all the files named finger_0_x and finger_0_x.bak (finger_0_1, finger_0_1.bak,...)
4. Reboot and try again.
If it still doesn't work, flash the attachment zip in recovery.
This works wonders!!!
EDIT: Please notice that I am not the owner of the file!
Click to expand...
Click to collapse
sorry for reviving this old thread, but I have been digging around for solution for quite some time and can't really get to the bottom of this.
I am facing the exact same problem - after upgrade, did factory reset on stock 10 but did not remove fingerprints prior, and now enrolment simply fails each time. Files you listed above are not present inside /persist/data (using twrp file manager).
if I flash persist.img I am afraid that could kill my device since some are suggesting that there are device specific information on that partition...
any suggestions?

KamiMK said:
Hey,
Tired of seeing this message when trying to enroll a fingerprint?
I have seen many people asking for fix and there has also been a file around here for the fix zip. But it was always hard to find that file so here it is.
Steps for fixing fingerprint:
Code:
1. Reboot to recovery
2. In the file manager, go to /persist/data/
3. Delete all the files named finger_0_x and finger_0_x.bak (finger_0_1, finger_0_1.bak,...)
4. Reboot and try again.
If it still doesn't work, flash the attachment zip in recovery.
This works wonders!!!
EDIT: Please notice that I am not the owner of the file!
Click to expand...
Click to collapse
I've tried this method in the past when downgrading from GSI or Android 10 to Android 9 and it doesn't work (the above mentioned files are not present). What I do is flash Oreo OEM rom via EDL in MiFlash, then reboot to bootloader and flash the Oreo "persist.img". Then I flash Android 9 OEM rom via EDL in MiFlash (without flashing the Android 9 "persist.img"). This method always works for me.

go to file manager in twrp.
navigate to /data/system
1. delete the file locksettings.db
navigate to /data/system/user/0
1. delete everything inside the folder fpdata
2. delete settings_fingerprint.xml
now you can install persist fix zip.
This will remove any pattern lock/pin lock/password/fingerprint. leaving a slide lock when you boot.

did ANYONE actually manage to install persist fix from the first post in this thread WITHOUT losing data or having to have to factory reset?! thanks