• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Ways to flash update.zip

Previously, I downloaded a update.zip from asus offical website. But the file size is too big that can't fit in with cache partition.
So I came up with some possible solution below,
1. Re-partition
Since I wanna extend cache,the effected partitions will be APD,ADF,System,Data, I'll backup them by dd command (dd if=/dev/block/mmcblk0p*7~10* of=/storage/emulated/0/*APD.img,etc.) And export them to my pc. Then I'll remake those partition by parted command and mkfs command, and use fastboot flash or dd to recover them all except /data.
The only issue of this method is that I can't find a custom rom for this. I might do it while normal boot
2. Resize update.zip
Since I know how to sign a update.zip file by signapk, I'll use this to split the file to a few packs.
In practice,I'll only leave META-INF and a tiny part of /system folder and pack them.the command will only be'mount('ext4','EMMC',(the patch),'/system');package_extract_dir('system','/system');', repeat for 6 time for copying files only .The 7th update.zip will include the rest of the files and official update-script.
I'll use fastboot flash update 7 times without rebooting to make it work.

Please help me analysis if these methods are correct and working, thanks:3.

Btw the reason of 'why I don't just let my tablet do a ota update and everything will be done?' is...
Well... The Update Manager just wanna leave me alone....(it is not function properly at all)

Sdk emulator not working : VCRUNTIME140.dll not found

So I installed Android Studio not long ago. I installed everything right, I installed in the sdk tools :
  • Android Emulator
  • Android SDK platform tools
  • Intel (x86) Emulator accelerator (HAXM)
I installed the API-Level 30 (x86 too)
I tried enabling/disabling launching in a tool window
I uninstalled and reinstalled everything several time

Next, I tried launching the emulator with command line
I first created an AVD: Pixel_XL_API_30 and used the command
emulator.exe -avd Pixel_XL_API_30 in the right folder with admin and non-admin privileges
I get a VCRUNTIME140.dll not found

So I tried fixing the dll following mainly (https://softwarekeep.com/help-center/how-to-fix-the-vcruntime140dll-is-missing-error-on-windows-10)
I ran scannow, I tried repair tools in all Visual studio version I could find in apps and functionalities
Then I tried unrergistering and registering back the dll and I get the following :

Module VCRUNTIME140.dll was loaded but entry point dllRegisterServer not found (more or less) Same for dllUnregisterServer.

And here I am stuck and desperately in need of your help. Thanks

recomendation for an android tablet; projector; good lens

GooDee 2020 Upgrade HD Video Projector, A couple of weeks back, my basketball teammate, a buddy came to me for a suggestion on best budget 1080p projector, as he was excited to celebrate his team’s winning moments on a widescreen (sadly, his team lost the game!!). Undoubtedly, I told him to go for GooDee 2020 Upgrade HD Video Projector. With excellent brightness, contrast ratio, and broader view, I must say it is one of the best 1080p projectors under 500.

bash: build.env/: No such file or directory error trying to Build/Run Cuttlefish on PC/ARM64

Hello.

I'm trying to Build/Run Cuttlefish on PC/ARM64. This is the tutorial that Im following :

https://sites.google.com/junsun.net/how-to-run-cuttlefish/home

Im stuck here :

root@ziomario-Z390-AORUS-PRO:/media/ziomario/Elements/android-cuttlefish# repo init -u platform/manifest - Git at Google -b pie-gsi

Downloading Repo source from git-repo - Git at Google
remote: Counting objects: 8, done
remote: Finding sources: 100% (150/150)
remote: Total 150 (delta 70), reused 150 (delta 70)
Receiving objects: 100% (150/150), 139.35 KiB | 1.74 MiB/s, done.
Resolving deltas: 100% (70/70), completed with 14 local objects.
Downloading manifest from platform/manifest - Git at Google
remote: Sending approximately 105.06 MiB …
remote: Counting objects: 1145, done
remote: Finding sources: 100% (3/3)
remote: Total 87072 (delta 26102), reused 87072 (delta 26102)
Receiving objects: 100% (87072/87072), 105.06 MiB | 7.15 MiB/s, done.
Resolving deltas: 100% (26102/26102), done.

repo has been initialized in /media/ziomario/Elements/android-cuttlefish

root@ziomario-Z390-AORUS-PRO:/media/ziomario/Elements/android-cuttlefish# source build.env/
bash: build.env/: No such file or directory

someone can give me some suggestions to fix that eror and goes further with the tutorial ? thanks.

Apps What will be impact of Google Contact API deprecation?

I think it probably means that the API won't be included in a new SDK version introduced then, which means apps using the old API will stop working as devices are updated to that. So the minimum impact would be that an app using the Contacts API won't work on Android 12, which I guess won't bother you at all.

It is much worst than this. Contact API will not work on all Android devices, not only on new devices because this is server side change. Server/Endpoint responsible for Contact API will be shut down and any attempt to access it will be responded with "404 not found". The same as with old SyncML service.

It means many apps on old phones will stop working because either developer will not update these apps with new API (abandoned apps) or updates will not be pushed to old phones for multiple reasons (not built for old Android versions, hardware or software limitations).

Main question here: Will built in Contact app (whatever it is called on different phones) continue to work after the change?

Regarding deprecation of old software (Android Market, for example): it is understandable and not an issue in this case. First, this change is server side change and not related to Android (any platform can use Google APIs). Second, I do not really expect devices on Android 2.x-Android 4.0 to be something more than dumbphone anyway. They can not connect to Google (well, 2.x can not, I did not check 4.0) and, actually, can not be used as smartphones. But this change may affect newer devices - at least 4.1-5.0.

Filter

Back
Top Bottom