471 replies to this topic

[SamuriHL]

Ok.  I'm getting ready to release a new version anyway.  I took your suggestion and handled the file crap.  And did some other nifty stuff to it to prevent people from doing stupid s***.  Like redownloading a perfectly good image.  How do I know it's good?  I check the hash...and if it doesn't match, then I redownload it.   But I wanna take a stab at the OTA stuff before I upload a new version.  And yes, I added a txt file to the archive to let you know what's changed just so you and I can keep track til I add real versioning.

[johnlgalt]

Sweet!

 

Interestingly enough, this time, after wiping with TWRP, I used ver 1 and it was still giving me a couple of the FAILED (Write to device failed (Too many links)) error.

 

But then when I went to look for another cable, just in case, the phone rebooted, and is now attempting to boot - got the curly-cues.

 

But, the HoG utility is locked up tighter than a straight man's arsehole.  I just clicked on it and it has gone into that 'faded' mode, where everything looks like you're looking at it through a fog.

 

Just the HoG - everything else on my system is running normally.

[johnlgalt]

Boom!  Initial setup screen confirmed.

 

So, I just realized - all that means is that my data wipe in TWRP worked.  Doesn't mean this thing actually flashed everything, although I'm rather positive that it did.

 

I should have used a different version, that would have proven it installed /system

[johnlgalt]

Of course, now that I know everything works the way it should, I could, theoretically, make a TWRP backup of the existing setup on my Taimen, restore it to the other partition, boot, make sure it works, then flip back, wipe and install BlissROM, and then set that up, wipe, and use HoG to install stock and see how that goes....

 

Plus, the Taimen has 75% battery and doesn't take nearly as long to boot, even after flashing.

[SamuriHL]

Give me a few minutes before you do that.  I want to give you the new version first.

[johnlgalt]

Well, I've started the backup in TWRP at any rate.

 

And I had to restart because the screen timed out - and nothing I would do would make it come back on.  So I had to use adb (which recognizes devices in recovery) to reboot to BL, fastboot boot to TWRP again, delete teh existing backup, disable the screen timeout, and then start the backup again.

 

Holy crap this thing is blazingly fast when backing up.....

[SamuriHL]

I'm almost ready to present a new version.  In fact I can do my testing while you do yours so it's incoming.

[SamuriHL]

Ok, new version is up.  Um, big changes for you in this new one.  If you have images you want to use that you've downloaded already, create an IMAGES directory and under that create a "device" directory.  E.G. IMAGES\taimen and stick your images in there.

[johnlgalt]

Right on.

 

Guess I'll delete the folder and extract fresh.

 

I'm restoring the TWRP backup from partition B to partition A and will boot to see if it actually boots.  If so, then I'll go back TWRP and install BlissROM, and then after getting that nominally set up, I'll make a backup of it and then fire up the latest HoG and let it do its thing.

[johnlgalt]

Uh, yeah.  It said that it doesn't backup things in /data like Pictures, Downloads, etc.

 

Uh, it didn't backup anything *but* Downloads.  Even everything under /Android is gone.  Apparently it missed a USB Debug authorization, so  it was 'protecting' me from myself.  But the next line still does apply....

 

However, since this is a multi-partition set up, my original install is safe on partition B.  Gonna go back into TWRP and verify that all is still well there, and then I'll flash BlissROM.

[SamuriHL]

Yikes that doesn't sound pleasant.  OTA flashing is not working and I quite frankly don't know why yet.  It reboots to recovery just fine so I know calls to adb are working.  Will need to debug this one and I'm pretty tired at this point.  I'm curious how you make out though.  The factory side should be ok.

[johnlgalt]

New Windows Insider Preview Skip Ahead build is out lol.

 

BlissROM installed successfully.  Now to test my theory about flipping partitions and booting back into the old.

 

After that, I'm running with HoG.

[johnlgalt]

Ha!

 

Wiping one partition and installing a ROM on it rendered the other partition unable to boot.  Which makes sense, because only the /system partition is duplicated, right?

 

At any rate, time to install via HoG, and then get back to the Shamu, since its battery is almost fully charged now.

[johnlgalt]

LMFAO!

 

Hard coding the path broke something somewhere, because I am using Xplorer² as my default file manager, it tried to load the image from the location where Xplorer² runs from:

 

 

C:\Program Files\zabkat\xplorer2_ult\IMAGES\taimen\taimen-pq2a.190205.002-factory-5bf777e4.zip does not exist!

 

Gonna try running it via a cmd prompt opened in HoG folder.

 

[EDIT] It accepted that path just fine when it was run from cmd.

 

Log:

Extracting: D:\HouseOfGoogle\IMAGES\taimen\taimen-pq2a.190205.002-factory-5bf777e4.zip
 To: D:\HouseOfGoogle\IMAGES\taimen\NEXUS\
extract: image-taimen-pq2a.190205.002.zip
extract: bootloader-taimen-tmz20o.img
extract: radio-taimen-g8998-00253-1811291732.img
Extract complete.

However, it also threw up an unhandled exception:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\HouseOfGoogle\IMAGES\taimen\FACTORY'.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileSystemEnumerableIterator`1.CommonInit()
   at System.IO.FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler, Boolean checkHost)
   at System.IO.Directory.GetFiles(String path)
   at HoG.Form1.processFACTORY()
   at HoG.Form1.magicButton_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3745.0 built by: NET48REL1
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
HouseOfGoogle
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///D:/HouseOfGoogle/HouseOfGoogle.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3745.0 built by: NET48REL1
    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.8.3745.0 built by: NET48REL1
    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.8.3745.0 built by: NET48REL1
    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.8.3745.0 built by: NET48REL1
    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.8.3745.0 built by: NET48REL1
    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.8.3745.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
HtmlAgilityPack
    Assembly Version: 1.9.0.0
    Win32 Version: 1.9.0
    CodeBase: file:///D:/HouseOfGoogle/HtmlAgilityPack.DLL
----------------------------------------
System.IO.Compression.FileSystem
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3745.0
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.IO.Compression.FileSystem/v4.0_4.0.0.0__b77a5c561934e089/System.IO.Compression.FileSystem.dll
----------------------------------------
System.IO.Compression
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3745.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.IO.Compression/v4.0_4.0.0.0__b77a5c561934e089/System.IO.Compression.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

[SamuriHL]

It's getting the path from the exe so apparently your nice little file explorer isn't playing nice with the code I used. There are other methods I can use. We may have to test that tomorrow.

Sent from my Pixel XL using Tapatalk

[SamuriHL]

Shit. I know what that error is. Just create a factory directory in your device directory and run it again. More bugs to fix.

Sent from my Pixel XL using Tapatalk

[johnlgalt]

I have everything set up correctly.  Taimen for Pixel 2 XL / FACTORY / 9.0.0 and the files there are correct - the current Feb OTA and FACTORY image.

 

I select the image, hit magic, and this happens - because it created a folder inside /Taimen called /NEXUS?

[SamuriHL]

Oh hell that won't fix it either. Ffs I really screwed that up. It's trying to extract to the old Nexus directory but use the factory directory that doesn't exist to parse the image files. Brilliant. Wtf. Yeah I'll fix all this in the morning.

Sent from my Pixel XL using Tapatalk

[SamuriHL]

I have everything set up correctly. Taimen for Pixel 2 XL / FACTORY / 9.0.0 and the files there are correct - the current Feb OTA and FACTORY image.

I select the image, hit magic, and this happens - because it created a folder inside /Taimen called /NEXUS?

Yeah for the reason I just explained.

Sent from my Pixel XL using Tapatalk

[johnlgalt]

Uh huh - it asked if I was ready to flash, then when I clicked yes, it told me that it is complete.

Extracting: D:\HouseOfGoogle\IMAGES\taimen\taimen-pq2a.190205.002-factory-5bf777e4.zip
 To: D:\HouseOfGoogle\IMAGES\taimen\NEXUS\
extract: image-taimen-pq2a.190205.002.zip
extract: bootloader-taimen-tmz20o.img
extract: radio-taimen-g8998-00253-1811291732.img
Extract complete.
Starting flash...
Flash complete.  Thank you for using the House of Google!