-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
android o & open database file #2
Comments
So it seems to be the database file which may have changed places on newer android versions. |
Got the same Problem with my PixelXL on 8.0. |
Same issue here I think. Backup works, then I get the same error message: ************** Ausnahmetext ************** ************** Geladene Assemblys **************
|
It is indeed an Android Oreo problem. Will ditch into this the coming weekend, I think there is only another path of the file. |
I think the exception might be misleading. Might this have something to do with the backup version number changing from 4 to 5 on Oreo? After I was unsuccessful with MiToolkit, I followed this procedure here. The step to extract the backup file from backup.ab failed. Once I changed the version number from 5 to 4 in the backup.ab with a hex editor, the extract succeeded. I'm just speculating that the same failure may be occurring when MiToolkit tries to extract the tar file from backup.ab. |
me,too |
Finally solved it, it was an error relating the android backup extractor. |
works like a charm with oneplus 3t (7.1.1)
After Backuping error message with "unable to open database file."
Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.
************** Ausnahmetext **************
System.Data.SQLite.SQLiteException (0x80004005): unable to open database file
bei System.Data.SQLite.SQLite3.Open(String strFilename, String vfsName, SQLiteConnectionFlags connectionFlags, SQLiteOpenFlagsEnum openFlags, Int32 maxPoolSize, Boolean usePool)
bei System.Data.SQLite.SQLiteConnection.Open()
bei MiToolkit.Start.cmdGetToken_Click(Object sender, EventArgs e)
bei System.Windows.Forms.Control.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnClick(EventArgs e)
bei System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ButtonBase.WndProc(Message& m)
bei System.Windows.Forms.Button.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.2098.0 built by: NET47REL1LAST.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.
MiToolkit
Assembly-Version: 1.4.0.0.
Win32-Version: 1.4.0.0.
CodeBase: file:///C:/Users/Christoph/Downloads/MiToolkit.1.4%20(1)/MiToolkit%201.4/MiToolkit.exe.
Microsoft.VisualBasic
Assembly-Version: 10.0.0.0.
Win32-Version: 14.7.2046.0 built by: NET47REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll.
System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.2094.0 built by: NET47REL1LAST.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.2093.0 built by: NET47REL1LAST.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.
System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.2046.0 built by: NET47REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
System.Configuration
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.2046.0 built by: NET47REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
System.Core
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.2099.0 built by: NET47REL1LAST.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.
System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.2046.0 built by: NET47REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
System.Runtime.Remoting
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.2046.0 built by: NET47REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll.
System.Data.SQLite
Assembly-Version: 1.0.105.2.
Win32-Version: 1.0.105.2.
CodeBase: file:///C:/Users/Christoph/Downloads/MiToolkit.1.4%20(1)/MiToolkit%201.4/System.Data.SQLite.DLL.
System.Data
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.2046.0 built by: NET47REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll.
System.Transactions
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.2046.0 built by: NET47REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll.
System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.2046.0 built by: NET47REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.7.2046.0 built by: NET47REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.
************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.
Zum Beispiel:
Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.
The text was updated successfully, but these errors were encountered: