Related
The problem: After installing AOSP 1.6, I noticed protected apps weren't showing in Market, including some I had bought in 1.5. I restored my 1.5 backup and found the same thing. Instructions on this thread (http://forum.xda-developers.com/showthread.php?t=605028) were able to get my apps back in 1.5, but upon reflashing 1.6 I was back to square one.
Update:
----------
I started fresh to test things out, trying both AOSP 1.6 and gbhil's modded AOSP 1.6. I wiped, then flashed and booted, then flashed gbits and booted, then setup my google creds, then rebooted and flashed superuser, then installed busybox then rebooted.
That's my baseline. From that point, I observed:
- Market showed a limited amount of apps. One time My Downloads had all my apps, but upon trying to install one I got a "Download unsuccessful" error. I'm assuming when the download was initiated my fingerprint was sent out, and then Market filtered My Downloads to reflect that unofficial fingerprint. Meaning, most apps were missing again.
- I updated build.prop with the fingerprint from stock 1.5 (see below for instructions). I downloaded a random app (Twidroid Free) so it'd send out my "new" fingerprint, and thus remove the filter limiting my apps. Soon after all apps were appearing again. Be patient here, sometimes it doesn't update instantly. One gave a download error, but trying to install it again solved it.
- Just to test, I edited my build.prop back to whatever was default with the 1.6 rom I was using, then rebooted. My Downloads still showed everything, but as soon as I installed any random app, that unofficial fingerprint was sent out and my apps were limited again.
I don't know enough about Market to know the repercussions of what I did - does it think I have 1.5, so will it be showing me only 1.5 compatible apps? Either way, I'd rather have access to all 1.5 apps than only some 1.6 apps. And aren't most (not all, but most) 1.5 apps backwards compatible with 1.6 anyway? So the only real downside is 1.6+ apps will be hidden. If someone has the fingerprint for an "official" 1.6 device, they could change their fingerprint to that and conceivably have the best of both worlds (protected apps AND 1.6+ apps).
How To Change Your Build Fingerprint:
--------------------------------------------
1. Connect your phone.
2. Pull /system/build.prop | For Mac users: ./adb pull /system/build.prop ./
3. Using your favorite editor, find the line that starts with ro.build.fingerprint and put a # in front of it.
4. On a new line, put: ro.build.fingerprint=sprint/htc_heroc/heroc/heroc:1.5/CUPCAKE/85027:user/release-keys
5. Save the file.
6. Remount the filesystem as read/write | For Mac users: ./adb remount
7. Log into the phone | For Mac users: ./adb shell
8. Exit the shell by typing: exit
9. Now push the file back. | For Mac users: ./adb push ./build.prop /system/build.prop
10. Reboot | For Mac users: ./adb reboot
11. Go to Market, and install something to send out the new fingerprint.
12. Within a few minutes you should see all apps. If not, try rebooting. If still not, try clearing Market's cache (Settings->Applications->Market->Clear Cache)
--------------------------------------------
Hope this helps someone.
-TM
This affects the MoDaCo rom I installed, and the AOSP 1.6 rom I was playing around with. Things like WeatherBug Elite, and tons of other stuff are hidden from the Market. In the case of MoDaCo, which I installed overtop my existing 1.5 stock (after backing up of course) the apps ran fine since they were grandfathered in from the stock rom, but still weren't listed in the marketplace. I'd really appreciate any help, as these speedy roms are useless if I can't run any of my apps on them.
search is king
this should help you
Link here
This reply isn't valid anymore and may be deleted.
Can you please post the code for this. I'm having a hard time getting this to work. Thanks
dathryl said:
Can you please post the code for this. I'm having a hard time getting this to work. Thanks
Click to expand...
Click to collapse
Code for what? What problems are you having?
Newbie question, how do you "pull" the file. I'm on shell but don't know what to input in order to edit the file.
PRGUY85 said:
Newbie question, how do you "pull" the file. I'm on shell but don't know what to input in order to edit the file.
Click to expand...
Click to collapse
You need to have ADB installed (which you do if you've rooted your phone, as ADB is required to do so). So you'd need to go into a command prompt (Windows) or Terminal (Mac), navigate to your adb/tools directory (that has adb.exe in it) and type "adb pull fileonyourphone fileonyourcomputer". Obviously replace fileonyourcomputer with the actual paths and filenames of what you're pushing/pulling. When you push the file back to the Hero, you swap the syntax, so it'd be "adb push fileonyourcomputer fileonyourphone".
OK, sorry again for noobness...
He says adb remount as read write, how do I do that?
He says log in to the phone...how do I do that on the shell?
So just to be sure, this fix will allow me to download the apps that I just can't find on the market that my friends with stock Heros can, right?
Someone recommended a new twitter client (twicca) but I couldn't open it on the market and I'm assuming it's because I'm running AOSP 1.6.
Thanks.
I just did this, and it seemed to work, but when Weatherbug Elite was downloading the phone went into the "Android" boot screen and just looped it over and over. After a battery pull it still won't boot up, and it keeps getting stuck at the boot screen. Is there anyway to fix this?
sure is nice to have sufbs back.
thanks for this.
Thanks, worked like a charm.
Release notes:
Software Update for the DROID Pro by Motorola
Introduction
We are pleased to announce the new software update for DROID 2 Pro by Motorola. The software update by Motorola (Version.2.26.60.XT610.Verizon.en.US) includes numerous enhancements. Upgrade today for peak performance.
For more information on Motorola updates and product support, visit us at DROID PRO - Motorola, Inc. USA.
Who Can Use This Release
ALL Motorola DROID Pro users.
After downloading and installing the software release, you will notice:
Enhancements:
*
o Improved audio on voice calls.
o Improved stability and performance.
o User interface display now refreshes when user switches from GSM/UMTS communication to Global Mode.
o Device now prepends 011 to Country Code to send SMS messages.
o Global Mode no longer resets when connecting to a USB charger.
o Visual Voice Mail now detects airplane mode while Wi-Fi is active.
o Prompt return to full screen brightness after wake-up.
o Upgraded Bluetooth firmware.
o Improved interoperability with Microsoft Internet Application Gateway (IAG) configurations.
o Device string format for Exchange changed to include device name and version number.
o Upgrade to Google applications Release 7.
Other Improvements:
*
o Improved audio during voice calls.
o Reduced user interface lock-ups.
Will I need to unroot (or at least unfreeze stock apps) before applying the update?
kcowling said:
Will I need to unroot (or at least unfreeze stock apps) before applying the update?
Click to expand...
Click to collapse
Some users have reported that they were able to do the update without un-rooting, others couldn't. You'll have to go ahead and try it.
Hey, any feedback on this update yet?
Thanks .
I have 2 Droid Pros in my household, both rooted, both running Droid 2 boostrapper for clockworkmod recovery. One updated perfectly; the other not. Still can't update. Not sure if it's the CWM recovery that's causing the issue.
My phone was rooted with the app Z4 and I was also unable to update. I have now unrooted and I will do a 2nd attempt in a minute .
Edit: No luck
The update was successful on my rooted, unlocked droid pro.
Does anyone know if this fixes the choppy music?
I am seeing a much more responsive unlock screen. No more do I have to drag multiple times to get it unlocked. That's the first thing I noticed
Sent from my DROID PRO using Tapatalk
having issues as well.
First try: forgot to unroot, update failed.
Second try: unrooted, update failed.
Third try: unrooted, update failed
I'm considering resetting the phone then trying again, but someone over on droid forums mentioned that the update failed even after a reset.
FWIW, after rooting I've only deleted a few of the apk's that I didn't use (amazon mp3, city id, social networking, a few others).
Thoughts?
This update did NOT fix this skipping / choppy / stuttering music issue.
Music playback still skips, chops or stutters during playback. Better luck next time Verizon
jonkranked said:
having issues as well.
FWIW, after rooting I've only deleted a few of the apk's that I didn't use (amazon mp3, city id, social networking, a few others).
Thoughts?
Click to expand...
Click to collapse
The deleted apps may be causing the problem. Try doing a factory reset, app update, then system update.
cool thanks for the input. i'll give it a shot.
ok so just a factory reset didn't work. it didn't restore the bloatware apks that I removed. I found them in another thread (another user was kind enough to post a zip file containing ALL the stock factory apks from the app folder).
when i get home from work tonight i'll reinstall them then try updating again. (don't have admin privs on my work PC, so can't copy things onto my phone from it)
jonkranked said:
ok so just a factory reset didn't work. it didn't restore the bloatware apks that I removed. I found them in another thread (another user was kind enough to post a zip file containing ALL the stock factory apks from the app folder).
when i get home from work tonight i'll reinstall them then try updating again. (don't have admin privs on my work PC, so can't copy things onto my phone from it)
Click to expand...
Click to collapse
Can you post a link for us? I thought Titanium backup, actually backed up the apps but I guess not. TIA.
David F.
newevery2 said:
Can you post a link for us? I thought Titanium backup, actually backed up the apps but I guess not. TIA.
David F.
Click to expand...
Click to collapse
Post #20, user: jwgraves
www.droidforums.net/forum/droid-pro-discussions/108310-update-invite-motorola-2.html
edit: couldn't make it an actual link, the forum software prevents users with <8 posts from posting links
jonkranked said:
Post #20, user: jwgraves
www.droidforums.net/forum/droid-pro-discussions/108310-update-invite-motorola-2.html
edit: couldn't make it an actual link, the forum software prevents users with <8 posts from posting links
Click to expand...
Click to collapse
I made it a link for you
theimpaler747 said:
I made it a link for you
Click to expand...
Click to collapse
thanks.
one thing i guess i should point out, the user who posted those files hadn't deleted/uninstalled the apps... he just renamed them from .apk to .bak and reverted them back to .apk to get the update to work.
another user who had actually deleted the apps and then copied them back in to the sys/apps folder can't get his device to reboot now.
i actually deleted the files, so I'm a little nervous now. Proceed with caution?
I'm still a noob to all this, would i benefit from installing something like bootstrap in the event my phone won't boot after i replace the apps?
Well I'm also having problems updating. I have all the system apps installed and running, I've tried updating rooted and unrooted, and just no luck. It's quite aggravating, I'm hoping someone or me figures out what the deal is with the Failed attempts
Solution for those unable to update!
So I've figured out a solution for those of you unable to do the update directly. I've posted a walk through in my original post for the Pro. It only updates the System.img - I've been running my Pro all day with it installed in this fashion with no issues what-so-ever. To quote my post in the other forum:
For those of you unable to get the new Droid Pro OTA working I have found a solution! You will need:
1)Root
2)Clockwork Recovery
3)System.img from update
4)Current Nandroid backup of your phone
5)ADB drivers and ASDK
So lets begin.
1)Boot into Clockwork recovery and create a backup of your phone.
2)Once complete, mount the phone as USB storage and pull the system.img file from the nandroid backup folder, as well as the nandroid.md5 (KEEP THESE FILES SAFE!!!!!)
3)Obtain the system.img file from here (Compliments of whoopsiedaisy).
4)Replace the system.img file in the Nandroid backup folder on your PHONE.
5)ADB into your phone (preferably still in recovery) and do the following:
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-xx-xx.xx.xx.xx
# rm nandroid.md5
# md5sum *img > nandroid.md5
6)If all goes will it should create a new MD5 checksum file utilizing the new system.img
7)Go to the 'backup and restore' menu in Clockwork, and select 'Advanced Restore'
8)Select the correct nandroid backup folder where the new system.img file is located, and then select 'Restore System'
9)Assuming all goes well, go to Settings, About and check your new system version!
Excellent. Wish I would've seen this before I went home from work, no ADB on the home computer, (and it's too late to mess with it). It will have to wait until after Christmas now, but at least there's a fix now....
Is anyone else able to install the latest update to Google Keyboard from the Market? I am unable to. I think I broke my Razr at some point, sadly. I manually updated to the new keyboard before they put it in the market (way back when). I have been able to get it to update in the past, but now, something is wrong, and it won't update...it keeps either telling me my certificate isn't correct, or it is already installed.
Things I have tried:
Making sure the following were the stock versions, and then removing all of them:
in /system/app:
Latin.apk, LatinIME.apk, LatinImeDictionaryPack.apk
in /system/lib:
libjni_latin.so, libjni_latinime.so
in /data/data:
com.google.android.inputmethod.latin
com.google.android.inputmethod.latin.dictionarypack
com.motorola.android.inputmethod.latin
I have tried wiping davlik-cache and cache, tried rebooting. Tried installing from market, and downloaded apk, using adb and pm install. It seems to either, if all the files are present, tell me that it can't install, as it is a different version of the certificate OR if I delete them all, it tries to install and reports the app is already installed.
Any suggestions?
Just to help anyone else find this post, some of the error messages I encountered that would help them find this in searching:
From the pm install, errors: INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES and INSTALL_FAILED_ALREADY_EXISTS
and from the dialogs in Android, when trying to do it from the market:
Application already exists, and Package file was not signed correctly.
Are you rooted? If so, have you tried uninstalling the keyboard with titanium backup, rebooting, then installing the new one from the play store?
Yep, I'm rooted, I should have mentioned that. I tried uninstalling with Titanium Backup, no luck. There must be some other thing that is colliding with the keyboard, something that I need to delete or clear, no idea. I am sure it is an odd problem to me, cause I got the keyboard manually before it came to market, but darned if I can figure this out. It really stinks, cause now I have only one choice, Swype. I really like and miss the Google Keyboard.
Only other thing that I can think of is if you are running a custom rom, do a dirty flash and then flash gapps. Otherwise you might have to do a complete wipe and start over.
RoboCuz said:
Is anyone else able to install the latest update to Google Keyboard from the Market? I am unable to. I think I broke my Razr at some point, sadly. I manually updated to the new keyboard before they put it in the market (way back when). I have been able to get it to update in the past, but now, something is wrong, and it won't update...it keeps either telling me my certificate isn't correct, or it is already installed.
Things I have tried:
Making sure the following were the stock versions, and then removing all of them:
in /system/app:
Latin.apk, LatinIME.apk, LatinImeDictionaryPack.apk
in /system/lib:
libjni_latin.so, libjni_latinime.so
in /data/data:
com.google.android.inputmethod.latin
com.google.android.inputmethod.latin.dictionarypack
com.motorola.android.inputmethod.latin
I have tried wiping davlik-cache and cache, tried rebooting. Tried installing from market, and downloaded apk, using adb and pm install. It seems to either, if all the files are present, tell me that it can't install, as it is a different version of the certificate OR if I delete them all, it tries to install and reports the app is already installed.
Any suggestions?
Just to help anyone else find this post, some of the error messages I encountered that would help them find this in searching:
From the pm install, errors: INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES and INSTALL_FAILED_ALREADY_EXISTS
and from the dialogs in Android, when trying to do it from the market:
Application already exists, and Package file was not signed correctly.
Click to expand...
Click to collapse
If your problem is in somewhere in data then a factory data reset is an option. But before you try that my restore thread allows you to try 3 different systems (stock, stock deodexed-debloat & if your are unlocked: a Telstra deodexed-debloat) and keep your data. They all need to be done is a series to keep data.
aviwdoowks said:
If your problem is in somewhere in data then a factory data reset is an option. But before you try that my restore thread allows you to try 3 different systems (stock, stock deodexed-debloat & if your are unlocked: a Telstra deodexed-debloat) and keep your data. They all need to be done is a series to keep data.
Click to expand...
Click to collapse
I managed to get this installed...I'm not sure exactly what I did to get it to work, and I still think I am somewhat broken, unfortunately. I removed the data directory, left all the .so and .apk files from stock, EXCEPT I took the Google Keyboard apk and manually stuck it into /system/app. I THEN did a pm install -r googlekeyboard.apk and it managed to install on top. I think I also (although not sure it helped) removed a rename line in /data/system/packages.xml about the package.
I don't have it linked in the market (in spite of trying with TB) and I don't have the Google Keyboard Settings app showing in my app tray, but the keyboard is there, selectable and seems to be working.
Cheers
RoboCuz
I am unable to install any version of google keyboard in my rooted Micromax A177.
This is a guide to debloat the KIW-AL10 and make stock Chinese usable.
First download Minimal adb and fastboot from here and install it.
Download HISuite and use that to install huawei drivers
Next Make sure developer options by hitting build number 7 times then open developer options and make sure usb debugging is activated in the developer options.
Plug phone into computer and install drivers, any unknown device will be adb so right click and select choose driver from list then select android devices then adb interface, always choose the older driver version for this phone.
One you have that installed you need to unlock your bootloader a great guide is here
Once you have unlocked the bootloader download install twrp using minimal adb and fastboot
First reboot into fastboot..
First check the device is present. using the command :adb devices
then boot into bootloader using the command : adb reboot-bootloader
if that doesn't work turn off device then switching on quickly hold down the volume down button while inserting the cable into the device
The device should then have a white screen with a robot and say unlocked in green writing
find the recovery image you downloaded and if its a different name rename it twrp.img so you know which one it is, files everywhere can get quite messy !
Now right click on the minimal adb link on the desktop and click open file location..
Now put the twrp.img file into the folder with the minimal adb files and close the window.
now flash the recovery using the command: fastboot flash recovery twrp.img
Voila if everything is sucessful your phone now has twrp recovery !
Next use the following command: adb reboot recovery, if that doesnt work force a shutdown by holding the power button then let the phone boot while holding down the volume up button, it should boot into recovery.
Next MAKE A BACKUP THIS IS VERY IMPORTANT AND WHEN ITS DONE COPY IT TO A SAFE DRIVE DO NOT KEEP IT JUST ON YOU SD CARD IN CASE YOUR CARD DIES ! BECAUSE OF THE NATURE OF THIS PHONE AND THE FACT THAT YOU CANT FLASH NON VOLTE ROMS ON THIS PHONE THIS IS YOUR ONLY WAY OF RESTORING THE PHONE SO GUARD IT LIKE YOUR LIFE DEPENDS ON IT !
Now get a cup of coffee and have a break its not good to rush things
Now to root your phone..
Finish your coffee.
Download supersu from here
Put the zip onto your phones sd card and boot into recovery, select install and select the supersu zip and let it install, once done reboot the phone, it may reboot a few times thats normal dont panic, once the phone has finished booting check you have the su app installed, if so now we can do the rest of the stuff.
Next download google play store from here and install it
After opening the play store and signing in you will probably be told to update google services, let it do it then reboot the phone
Next using the play store download root explorer
Next stage is to make the dialer English. and remove yellow pages.
Using root explorer navigate to /cust/alltelecom/cn/prop
hard press on the file local.prop and select open in text editor using the 3 dots on the top right
Look for the following lines of code ro.product.locale.region=CN or similar
Change this to ro.product.locale.region=GB (or whatever your location is such make sure the country code is in CAPS )
Save the file
Now navigate to /system and open build.prop in text editor and change the following lines of code so they end in County matching code not cn
Example
ro.product.locale.region=GB (or whatever your location is such )
ro.product.locale.language=en (or whatever your location is such )
ro.product.locale.region=GB
Go slow there is lots of lines there but you will see them if you take your time
select save and exit from root explorer then reboot.. viola the chinese and yellow pages is gone !
After reboot you may get a baidu warning about location tracking, dont panic we will kill that bugger next !
Next install system app safe remover from the play store https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_GB I always use this as its simple and keeps a backup of the removed app (just in case of problems)
Use that to remove all the chinse apps from the system including hivoice or it will interfere with google assistant, they are self explanatory
as they are all in chinese !
Next remove hi app
hi care
huawei id
network location (this is the one causing the nag screen dont worry work it will still work.
then reboot phone, there should be no more warnings about baidu location.
Now to get services google working.
You my have notice that despite installing a google account you contacts havent synced. we will fix that now..
To get google contacts to sync you need to install google contacts sync adaptor 6.0.1 from here
After you have installed it open up system apps and check it permision contacts is allowed, also open the battery setting and check it runs at boot and while screen is off, if there are no options for that ignore that bit and exit.
while you are there check google play services permission are all on especially contacts then reboot
Now install the google app from the app store
next install google assistant from the play store
now install google photos from the play store
Next install google chrome from play store
next install google calendar from the play store
next install google plus from the play store
next install google maps from the play store
next install youtube from the play store
Next install gboard from the play store
Then when all is done reboot the phone
After reboot check all the permissions of the apps and make sure all the google apps run at boot and keep running after screen off or they wont sync etc then reboot again.
Change horrible huawei keyboard to gboard in language settings
Open the google app and setup google and check your contacts have synced. set up the rest of your settings
Get a decent launcher as the huawei one sucks I use nova launcher prime its worth every penny but the free one is still good
Open settings app and click advanced, here you can change default launcher and select default app setting then select assistance and voice input, selectassist app as google select use text from screen and select use screenshot
I think that pretty much it, the rest you should be able to do yourself, have fun and good luck, any questions just ask.
I wrote this guide as there is very little info on the AL10,
Happy modding !
Very useful
Very useful post, my first venture into phone modding, enabled me to use my KIW-AL10 with Google functionality and to avoid the worst excesses of the stock Chinese software. Thanks!
Ed_shred said:
Very useful post, my first venture into phone modding, enabled me to use my KIW-AL10 with Google functionality and to avoid the worst excesses of the stock Chinese software. Thanks!
Click to expand...
Click to collapse
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
swukjay said:
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
Click to expand...
Click to collapse
So, the phone worked ok for a month, but then started restarting itself all the time. I deleted loads of apps, but it didn't solve the problem. Now, I decided to try to solve the problem by installing a custom ROM, so first step was to wipe the phone with TWRP. After wiping, I no longer had root access, and now installing SuperSU doesn't work, I can install the .zip through TWRP recovery, but I still don't have root access afterwards, according to Root Checker. Any ideas? Thanks!
Ed_shred said:
So, the phone worked ok for a month, but then started restarting itself all the time. I deleted loads of apps, but it didn't solve the problem. Now, I decided to try to solve the problem by installing a custom ROM, so first step was to wipe the phone with TWRP. After wiping, I no longer had root access, and now installing SuperSU doesn't work, I can install the .zip through TWRP recovery, but I still don't have root access afterwards, according to Root Checker. Any ideas? Thanks!
Click to expand...
Click to collapse
Repeated the process, ticked a few boxes in SuperSU, seems to be solved for now, thanks...
swukjay said:
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
Click to expand...
Click to collapse
OK, so I have tried quite a few times to install Lineage OS 14.1 and Viper, with both they get stuck in a bootloop. Trying to install Lineage with this guide https://wiki.lineageos.org/devices/kiwi/install, the 'format data' stage is not successful. I get a message saying ' E:Unable to wipe '/data' - unknown file system 'auto Unable to format to remove encryption '.
I'm not totally committed to a custom ROM, but I'd like this phone to work. Any ideas, either how to troubleshoot the ROM flashing issue, or to get the phone stable with the stock de-Chinesed stock ROM? Thanks!
I'm using Xiaomi.eu (latest 12.20.20) but problem began a month ago with 20.4.28 and IMO, must be something generic about MIUI and its Updater app - Settings / My device / Updater)
Does anybody know where the Updater stores (unsuccessful) downloads and/or anything about the available updates (excepts on root of Internal memory and the Updater's folder in /data/data aka /data/user/0)
I have Magisk/root (and MiXplorer) and TWRP, hence I could delete wherever I would need..
Problem:
- Opening System or System, My Device, they note me that some update is available (screenshots 1,2).
- However, I have the latest Xiaomi.eu 12.5.20 hence there is no (and there will be no) update until 21.5.27 Thursday next week.
- And indeed, once I enter Updater and I Check for update, it reports that I'm up-to-date, i e., that there is no update for me (screenshot 3).
When I ran Security app, it reported me that (a month old) 21.4.28 is available - I'm not sure but maybe a month ago I really tried downloading 21.4.28 (when it was brand new) from Updater and it failed but then I deleted the broken zip file and the accompanying mdf5 file from the root on Internal memory.
But maybe, something/somewhere remained on the phone making it to think that an update is still available.
I already did/tried but no avail:
- Clear Cache and All data for the Updater app from Settings, Apps
- Wiped Dalwik and Cache from TWRP
- Wiped /data/system/package_cache
- Manually deleted /data/data/com.android.updater (data folder for the Updater app).
- Also, I have inspected Internal memory (files and folders on root and also /Android/data folder) and /data partition (by browsing with MiXplorer as much as it made sense) but I could nowhere find anything to look like related to updates.
- I also opened Downloads app and deleted everything it showed me for (the old) downloads.
- My /data/ota folder is empty.
- I did deep cleaning from Security app, no avail - it still notes me in Settings and My Device about some not-available (Xiaomi.eu) update.
It makes me crazy because downloading Xiaomi eu update by Updater app was a way faster than manually downloading Xiaomi.eu zip ROM by browser (even ADM) from AFH or from SFN servers.
Plus, Updater downloads both the zip and md5 files.
It's also more convenient (when it works properly), it should show when update is really available, just like for OTA, hence I would not need to check every hour on Xiaomi.eu forum or Telegram when update becomes available, to take the AFH or SFN links there to manually download...
Last Thursday when I was on 21.5.12 and Xiaomi.eu 21.5.20 really became available, Settings and My device were showing that Update was available (as they constantly do) but the Updater was answering that I was up-to-date / that there was no update for me - hence all the same as now upon I nanually updated to the latest Xiaomi.eu - and thus I was unable to use the Updater to really know when update was available and to download it
I can live with that problem (and manually update the new Xiaomi.eu next Thursday, and so on) but I would really like to solve the problem.
I want to know what exactly to delete to get rid of -however, I will absolutely NOT GO into Wiping (or even Formatting) Internal memory or Data (like Factory reset) since everything else works perfect (and the phone is my daily driver)
Problem resolved - an interesting solution was given on Xiaomi.eu forum
Although I was on 21.5.20, the following command was returning 21.4.28:
adb shell settings get global miui_new_version
Hence I had to use:
adb shell settings put global miui_new_version 21.5.20
to let it properly know it is already on 21.5.20 and to get rid of that ghost Update note in Settings and My device
Now, they are in sync with Updater (and ro fingerprint props who all already 'knew' that system was updated to 21.5.20)
Btw, I didn't breally use PC and adb shell, but terminal app on the phone and cmd commands -hence (must start with su to obtain root access):
su
cmd settings get global miui_new_version
cmd settings put global miui_new_version 21.5.20
PS:
Tested, this put settings properly survive reboot (hence ghost Update did not return upon reboot)
Admin, please lock this thread, problem was resolved (and solution explained) - thanks
zgfg said:
Admin, please lock this thread, problem was resolved (and solution explained) - thanks
Click to expand...
Click to collapse
Thread closed on request of OP @zgfg