471 replies to this topic

[SamuriHL]

Windows gets touchy about that kind of thing.  File handles are a pain in the ass.  As long as your'e sure you validated the image, the new version won't let you redownload it anyway cause I'm assuming if it was downloaded in my IMAGES\device folder it's valid.  If it's NOT valid, simply delete the file and it'll let you redownload it in the new version.

[johnlgalt]

Rebooted.  Deleted existing image via Windows Explorer.  Ran HoG via Windows Explorer.  Same exception error.

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

************** Exception Text **************
System.IO.IOException: The process cannot access the file 'D:\HouseOfGoogle\IMAGES\shamu\shamu-ngi77b-factory-5cd75e2a.zip' because it is being used by another process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode)
   at HoG.Form1.checkHash()
   at HoG.Form1.downloadButton_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.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/Framework64/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
----------------------------------------

************** 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]

I'm able to repro it.  Will look at it and see what's going on.

[johnlgalt]

I don't think this has anything to do with it, as I've not even tried flashing yet - but it seems that my USB woes with the Shamu are, in fact, device related.  I'll have to go digging in there and see if there may be some lint or something that is preventing a good connection.

 

So, I tried flashing using a .ZIP that I had already DLd for Shamu, and HoG recognized it was there and flashed it. 

Extracting: D:\HouseOfGoogle\IMAGES\shamu\shamu-n6f27m-factory-bf5cce08.zip
 To: D:\HouseOfGoogle\IMAGES\shamu\FACTORY\
extract: radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
extract: image-shamu-n6f27m.zip
extract: bootloader-shamu-moto-apq8084-72.04.img
Extract complete.
Starting flash...
(bootloader) has-slot:bootloader: not found
Sending 'bootloader' (4071 KB)                     OKAY [  0.150s]
Writing 'bootloader'                               (bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [  0.668s]
Finished. Total time: 0.909s
rebooting into bootloader                          OKAY [  0.001s]
Finished. Total time: 0.001s
Sleep 5 seconds for reboot...
(bootloader) has-slot:radio: not found
Sending 'radio' (115507 KB)                        OKAY [  4.146s]
Writing 'radio'                                    (bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [  1.664s]
Finished. Total time: 5.900s
rebooting into bootloader                          OKAY [  0.001s]
Finished. Total time: 0.001s
Sleep 5 seconds for reboot...
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------       
Bootloader Version...: moto-apq8084-72.04
Baseband Version.....: D4.01-9625-05.45+FSG-9625-02.117
Serial Number........: ZY222X6Z3C
--------------------------------------------       
Checking product                                   OKAY [  0.003s]
Checking version-bootloader                        OKAY [  0.002s]
Checking version-baseband                          OKAY [  0.004s]
extracting boot.img (8 MB) to disk... took 0.032s
(bootloader) has-slot:boot: not found
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product-services.img'
extracting recovery.img (13 MB) to disk... took 0.044s
(bootloader) has-slot:recovery: not found
archive does not contain 'recovery.sig'
archive does not contain 'super.img'
extracting system.img (1544 MB) to disk... took 9.113s
(bootloader) has-slot:system: not found
(bootloader) has-slot:system: not found
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
(bootloader) slot-count: not found
Sending 'boot' (8483 KB)                           OKAY [  0.396s]
Writing 'boot'                                     OKAY [  0.149s]
Sending 'recovery' (13873 KB)                      OKAY [  0.494s]
Writing 'recovery'                                 OKAY [  0.228s]
Sending sparse 'system' 1/4 (522524 KB)            OKAY [ 20.035s]
Writing sparse 'system' 1/4                        OKAY [  7.862s]
Sending sparse 'system' 2/4 (517601 KB)            OKAY [ 19.036s]
Writing sparse 'system' 2/4                        OKAY [  7.004s]
Sending sparse 'system' 3/4 (508949 KB)            OKAY [ 18.802s]
Writing sparse 'system' 3/4                        OKAY [  7.055s]
Sending sparse 'system' 4/4 (32756 KB)             OKAY [  1.147s]
Writing sparse 'system' 4/4                        OKAY [  0.408s]
Rebooting                                          
Finished. Total time: 94.864s

Only it rebooted to the dead Andy again.  Had to enter recovery myself and tell it to reboot from there.

 

I honestly think that the Shamu may have some latent issues that I was not aware of, above the charging port issues, but the good news is that the above process did, in fact, flash the system image to the device.  I've now got the standard Google Nougat Curly-cues starting up - let's see if it actually boots.

[SamuriHL]

I found the issue.  It was a stupid bug on my part.  I moved some code around and broke something.

[johnlgalt]

Of course it won't boot - it's not wiping data.  And Flashing stock over a ROM (in this case BlissROM) will only make it bootloop until I wipe data.

 

I've entered stock recovery, and run the command to wipe data /factory reset.  It's doing that now.

 

It should boot after this.

[johnlgalt]

I found the issue.  It was a stupid bug on my part.  I moved some code around and broke something.

 

Cool.  So, ver 0.6 coming with the fix.

 

Meanwhile, ver 0.5 flashed just fine, so that is a step in the right direction.

[SamuriHL]

Yea, just testing it now before I ship it your way.  Some dumbass was trying to check the hash before the file was downloaded.  WOOPSIE.

[SamuriHL]

And yes, it's on my todo list to add a wipe option but I haven't decided how I want to implement it just yet.  Mainly cause I have some other under the covers functionality that's going in next (probably tomorrow) that will be really nice to have.  It will require a few test runs in...different configurations....for factory images.  I'll explain when we get there.

[SamuriHL]

New version is up.  I gotta step away for a few.  I have a hard stop tonight at some point, as well, as I have a friend coming for movie night.  But test the new version and lemme know how it goes.

[johnlgalt]

Yea, just testing it now before I ship it your way.  Some dumbass was trying to check the hash before the file was downloaded.  WOOPSIE.

 

Not gonna call anyone any names, but I honestly thought that was what was happening.

 

And yes, it's on my todo list to add a wipe option but I haven't decided how I want to implement it just yet.  Mainly cause I have some other under the covers functionality that's going in next (probably tomorrow) that will be really nice to have.  It will require a few test runs in...different configurations....for factory images.  I'll explain when we get there.

 

Cool.  I have a feeling more than a couple of the ideas that I have you'll be far ahead of anyway

 

New version is up.  I gotta step away for a few.  I have a hard stop tonight at some point, as well, as I have a friend coming for movie night.  But test the new version and lemme know how it goes.

 

Roger that, about to test after manually installing Bliss again.

[SamuriHL]

Yea, I have LOTS of ideas but I gotta get a release out first that focuses just on the basics.  And there's fundamentals that are left to be done.  At some point a major refactoring of the code has to happen as it's pretty much mostly prototype "can this be done" type of code at the moment.  The option to wipe will make it into a release 1.  Some of my under the covers fundamentals will surprise people with what it allows me to do.  Definitely a fun project and allows me to stretch my legs as a developer.  Getting the processes to run was hell on earth, but, now I can run any fastboot and/or adb command I want.  I'll let that sink in. 

[johnlgalt]

Including slot swapping, booting recovery images, sdb shells, lol - this is gonna be fun I can see.

 

That alone will allow you to integrate setting up Magisk on a device a whole lot more easily.  It will require some user interface, as they have to use the Magisk.apk to patch the boot.img for their device, and that could lead to issues if a user tries to patch the wrong boot.img (not wrong device, though that could happen as well, but wrong *release*...)

[johnlgalt]

Installing Bliss on the Shamu again.  After that, I'll test from start to finish of installing Factory, and I'll use a slightly older install of the factory image so I can then test the OTA to the latest.

 

That should pretty much cover everything that is working so far, right?

[SamuriHL]

Yes yes, slot support is on the short list.  All the other fun stuff comes later.

 

And doesn't my app guarantee already that you're using the version you select?  So that should solve that problem real quick.  But yea, I'll get to all that advanced stuff.  I just want to make sure we got a tool people can use to make it drop dead simple to pick an image and have it flashed.  

[SamuriHL]

Installing Bliss on the Shamu again.  After that, I'll test from start to finish of installing Factory, and I'll use a slightly older install of the factory image so I can then test the OTA to the latest.

 

That should pretty much cover everything that is working so far, right?

 

Yea that should cover it all.  I'll be around for about 2 or so more hours so if anything comes up I'll keep checking the thread.

[SamuriHL]

BTW, one of the neat things they apparently added to adb at some point is that if you're rooted you can reboot recovery directly into sideload-auto-reboot mode.  Push the image over adb and when it finishes it auto-reboots.  That's something I plan to add support for in the advanced options.

[johnlgalt]

Did not know that.  Way cool.

 

BlissROM booted just fine - I've learned that using the function (button) to format /data for my Shamu breaks it and I have to do a wipe / factory reset for it to recreate /data.  Extremely odd, but there you go.

 

So, basically, in order to use this effectively, with a non-stock ROM installed on the Shamu, I need to boot TWRP, wipe the device, reboot to bootloader, and run HoG.  This should be fun.  I'll try not ot do the whole long stepping factory wipe so you don't have to wait an hour for results.

 

If I wasn't expecting an important phone call (and I really need to contact FI customer support to get a backup SIM so I can set it up on another device while I am testing on the Taimen) I'd play around with the Taimen, since it is *soooooooooooooo* much faster at doing everything.

 

I suppose I'll contact them while doing this iteration on Shamu and see if they will oblige me.

[johnlgalt]

Odd, odd, ODD!

 

My Shamu is apparently weird AF.  When in TWRP, if I don't disable the screen timeout, it goes to a blank (black) screen and becomes unresponsive - cannot unlock it, have to manually force the device back into bootloader mode.

 

Furthermore, I just wiped everything in TWRP, and used TWRP to reboot back to BL - and after looking away for some time, getting everything else ready, I look at it - and it is giving me the battery charging icon you see when the device is powered off.

 

Seriously, WTF?

 

Confirmed, neither adb nor fastboot can currently see the device - it is, for all intents and purposes (indents and porpoises?) off.

 

Sigh.

[johnlgalt]

Rebooting Shamu with flash of System Image of 7.1.1 (NGI55D, Sep 2017) - got Curly-cues.  Let's see if it bootloops this time since I wiped before starting.