New [8.10.11/12] No google backup restore in case of full wipe and first startup with signing into account


cluster_edge

Members
Aug 17, 2012
32
30
Steps to reproduce:
0. MI8 with unlocked bootloader (MI8 6128 in my case)
1. Flash fastboot file with latest global beta from xiaomi (8.10.12 in my case)
2. Start it, check needed info and maybe some tests including signing into accounts, camera, sound (google restore from backup is working)
3. Flash custom recovery and wipe everything excluding persist
4. Flash 8.10.12\8.10.11 (in both case same error )
5. Boot into system, initial setup for accounts

Expected result - while signing into google accounts its propose restore from backup

Actual result - No proposing and don't have option to start it manually from setting or any other way
Status in google backups section on phone indicates that updates still waiting for backup excluding contacts\photo (i suppose that because they have dedicated apps - contacts and google photos)

Note - After first startup there is notification pop-up in the center of the screen with something like : You disabled in previous version ability to sage location history bla bla bla from google subsystem and design of that popup is kinda like 4.]x android design not a material one. In case with xiaomi global beta all design and pop ups have a new design from 8.x\9.x version. Maybe rootcause for this issue is outdated google libraries? (Sorry, but i dont know about you internal build process)
 
  • Like
Reactions: JoSch68
After some research i"ve, with help of another forum member, discover that manually run bmgr run solve problem with Waiting for backup status in backup section but even manually run bmgr restore leads to fail

Bash:
bmgr run
dipper:/ $ bmgr list sets                                                     
  31c97409cc86b0fb : MI 8
  329da99cc86bd561 : MI 6
  bmgr restore 31c97409cc86b0fb                                       
Scheduling restore: MI 8
restoreStarting: 123 packages
restoreFinished: -1000
done
dipper:/ $ %

I assumed that waiting for backup issue root cause in the absent bmgr run somewhare in app settings config or blocked by something but main problem with restore backup still presents(
 
Bash:
10-19 15:21:01.550  8403  8403 D AndroidRuntime: >>>>>> START com.android.internal.os.RuntimeInit uid 2000 <<<<<<
10-19 15:21:01.635  8403  8403 W main    : type=1400 audit(0.0:7118): avc: denied { read } for name="u:object_r:vendor_mpctl_prop:s0" dev="tmpfs" ino=23685 scontext=u:r:shell:s0 tcontext=u:object_r:vendor_mpctl_prop:s0 tclass=file permissive=0
10-19 15:21:01.646  8403  8403 E libc    : Access denied finding property "ro.vendor.at_library"
10-19 15:21:01.649  8403  8403 D AndroidRuntime: Calling main entry com.android.commands.bmgr.Bmgr
10-19 15:21:01.654  1859  3679 V BackupManagerService: beginRestoreSession: pkg=null transport=null
10-19 15:21:01.655  1859  3679 V BackupAgentTimeout: getRestoreAgentTimeoutMillis(): 60000
10-19 15:21:01.660  1859  3610 I chatty  : uid=1000(system) backup expire 33 lines
10-19 15:21:01.678  1859  1859 I TransportClient: BackupTransportService#3: Notifying [BH/MSG_RUN_GET_RESTORE_SETS] transport = IBackupTransport
10-19 15:21:01.688  1859  3679 D BackupTransportManager: Transport com.google.android.gms/.backup.BackupTransportService updated its attributes
10-19 15:21:01.711  3391  3391 W ChimeraUtils: Non Chimera context
10-19 15:21:01.711  3391  3391 W ChimeraUtils: Non Chimera context
10-19 15:21:01.764   606   632 E Parcel  : Reading a NULL string not supported here.
10-19 15:21:01.765   606   632 E Parcel  : Reading a NULL string not supported here.
10-19 15:21:02.037  3427  5104 W Conscrypt: Could not set socket write timeout: java.net.SocketException: Socket closed
10-19 15:21:02.038  3427  5104 W Conscrypt:     at com.google.android.gms.org.conscrypt.Platform.setSocketWriteTimeout(:com.google.android.gms@14367037@14.3.67 (100400-216465562):2)
10-19 15:21:02.038  3427  5104 W Conscrypt:     at com.google.android.gms.org.conscrypt.ConscryptFileDescriptorSocket.setSoWriteTimeout(:com.google.android.gms@14367037@14.3.67 (100400-216465562):2)
10-19 15:21:02.162  3427  5104 W Conscrypt: Could not set socket write timeout: java.net.SocketException: Socket closed
10-19 15:21:02.163  3427  5104 W Conscrypt:     at com.google.android.gms.org.conscrypt.Platform.setSocketWriteTimeout(:com.google.android.gms@14367037@14.3.67 (100400-216465562):2)
10-19 15:21:02.163  3427  5104 W Conscrypt:     at com.google.android.gms.org.conscrypt.ConscryptFileDescriptorSocket.setSoWriteTimeout(:com.google.android.gms@14367037@14.3.67 (100400-216465562):2)
10-19 15:21:03.134  3427  5104 I Backup  : [BackupHttpRequestUtil] Http Response Code: 200
10-19 15:21:03.164  1859  3610 V BackupAgentTimeout: getRestoreAgentTimeoutMillis(): 60000
10-19 15:21:03.167  1859  3679 D RestoreSession: endRestoreSession
10-19 15:21:03.168  8403  8403 D AndroidRuntime: Shutting down VM
10-19 15:21:03.169  1859  3610 V BackupManagerService: Clearing restore session and halting timeout
10-19 15:21:04.429  1859  1920 I PowerManagerService: Going to sleep due to screen timeout (uid 1000)...

Added logcat. Seems like the problem is in the gms transport. But on MI 6 all works fine. And very strange error 10-19 15:21:01.646 8403 8403 E libc : Access denied finding property "ro.vendor.at_library"