Jump to content


Photo

House of Google 0.0.9.8 [BETA]


  • Please log in to reply
452 replies to this topic

#441 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 36,386 posts
  • Current Device(s):Pixel XL

Posted 24 February 2020 - 09:11 PM

I've learned a lot of programming stuff in the last year so I'll see what crazy stuff I can do to it this week.

Sent from my SM-G975U using Tapatalk


  • johnlgalt likes this

5uWEQs7.jpg

 

Non potest esse nisi unus

 


#442 johnlgalt

johnlgalt

    Antidisestablishmentarianist

  • Superuser
  • 4,759 posts
  • Twitter:https://twitter.com/JohnLGalt
  • Google+:google.com/+JohnLGalt_1
  • Location3rd Rock
  • Current Device(s):Pixel 4 XL 128 GB

Posted 24 February 2020 - 09:14 PM

All good - The best part is that I can really live up to my reputation - and try to break $#!+, without actually breaking anything important.

 

Although, I've replaced my older laptops that were running Sabayon Linux with a newer laptop also running WinX.  So I can now only test WinX.  But I can still test on my ancient platform as well as on the newer lappy (i5 6xxx CPU, 16 GB RAM, M.2 + SATA II SSDs).  And all without fscking my Pixel 4 XL.


  • SamuriHL likes this

#443 johnlgalt

johnlgalt

    Antidisestablishmentarianist

  • Superuser
  • 4,759 posts
  • Twitter:https://twitter.com/JohnLGalt
  • Google+:google.com/+JohnLGalt_1
  • Location3rd Rock
  • Current Device(s):Pixel 4 XL 128 GB

Posted 25 February 2020 - 11:08 AM

OK, so I obviously should not have attempted this so late last night.

 

The file I downloaded from the Android dev page was the full system image, not the OTA.  I subsequently found the links to both full system images and OTAs on XDA (after sideloading would not work - gee, ya think?), and it was the actual correctly named file (with the correct SHA-256 hash) as what HoG attempted to DL, so I'm not sure why HoG got a different hash for the file.  The Hash that HoG produced didn't seem to match anything there, but I did not DL all of the files, I can do so this weekend to see if it was simply pulling the wrong file (though that is probably not the case (at least from HoG's PoV, as it has the absolute correct name of the file needed).

 

Meanwhile, I sideloaded the Dev preview onto the Taimen and all is well.

 

No rush on anything for HoG for right now, but since I do have the Taimen available (and have successfully re-locked the BL, and since it is not a daily use device anymore, I'm here for when you do need testing again.



#444 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 36,386 posts
  • Current Device(s):Pixel XL

Posted 25 February 2020 - 03:22 PM

I had a long day but I do intend to take a look in a bit and see what's going on.  I saw some crazy s*** the last time I ran it for myself where it enumerated the entire world into one list.  I was like WTF is this?  LMAO  But I've not gotten around to playing with it.  I've learned a LOT more about web technologies in the past year in my current job so I plan on taking a look at how I'm doing all of the parsing.  I think it was fairly decent and solid when I wrote it but if Google makes significant changes to the web page layout, then it'll break.  So I may see if I can make it more robust.


  • johnlgalt likes this

5uWEQs7.jpg

 

Non potest esse nisi unus

 


#445 tomv5314

tomv5314

    Member

  • Members
  • PipPip
  • 237 posts
  • LocationMass.
  • Current Device(s):Pixel 2 XL- 128GB - Nexus 6P- 128GB - LG G3- LG-G2 -Razor Maxx HD unlocked- Bionic- Samsung Galaxy Tab S3--SM-T820

Posted 04 March 2020 - 01:30 AM

I had a long day but I do intend to take a look in a bit and see what's going on.  I saw some crazy s*** the last time I ran it for myself where it enumerated the entire world into one list.  I was like WTF is this?  LMAO  But I've not gotten around to playing with it.  I've learned a LOT more about web technologies in the past year in my current job so I plan on taking a look at how I'm doing all of the parsing.  I think it was fairly decent and solid when I wrote it but if Google makes significant changes to the web page layout, then it'll break.  So I may see if I can make it more robust.

Hi Sam .. I am having a new problem with the march update with H.O.G.It opens , Says Platform tools found then under found device Pixel 2XL(Taimen) on the bottom. Its seeing device fine. As soon as i click  Image Type Factory or OTA  I get Unhandled Exception  has occured in your application.  Length cannot be less than zero. Parametername:length click and app will ignore this error and attempt to continue,  but HOG will go no further. No drop down or version numbers  etc.   I just did the OTA on my backup 2XL that is unlocked and unrooted. But My main 2 XL I  use HOG on is unlocked rooted with Viper working etc and I can do  the factory Image save everything and put on recovery and re root in about 10 min.  and set up as I like so I love being able to save everything  Hoping if you have the time you could help me  if you get a chance.. Sorry for the long winded post. Below is the Exception text.    Thanks Sam.  Hope all is well with you.  

 

System.ArgumentOutOfRangeException: Length cannot be less than zero.
Parameter name: length
   at System.String.Substring(Int32 startIndex, Int32 length)
   at HoG.Image..ctor(String device, String name)
   at HoG.Devices.AddImage(String device, String name, String imageType)
   at HoG.FlashHandler.LoadData(String url, String type, Devices myDevices, Boolean isBeta)
   at HoG.HouseOfGoogle.ImageCombo_SelectedIndexChanged(Object sender, EventArgs e)
   at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
   at System.Windows.Forms.ComboBox.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.4150.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
HouseOfGoogle
    Assembly Version: 0.0.9.8
    Win32 Version: 0.0.9.8
    CodeBase: file:///C:/Program%20Files%20(x86)/House%20of%20Google/HouseOfGoogle.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
 
************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
HouseOfGoogle
    Assembly Version: 0.0.9.8
    Win32 Version: 0.0.9.8
    CodeBase: file:///C:/Program%20Files%20(x86)/House%20of%20Google/HouseOfGoogle.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C
    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.4001.0 built by: NET48REL1LAST_C
    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.3752.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.3752.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.4121.0 built by: NET48REL1LAST_C
    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.3752.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
----------------------------------------
System.Net.Http
    Assembly Version: 4.0.0.0
    Win32 Version: 4.8.3752.0 built by: NET48REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Net.Http/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Net.Http.dll
----------------------------------------
HtmlAgilityPack
    Assembly Version: 1.9.0.0
    Win32 Version: 1.9.0
    CodeBase: file:///C:/Program%20Files%20(x86)/House%20of%20Google/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.
 
 
----------------------------------------

Pixel 2 XL - 128 GB


#446 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 36,386 posts
  • Current Device(s):Pixel XL

Posted 04 March 2020 - 04:25 AM

I'll have to look at it when I get a chance. It's not likely to be until this weekend at the earliest. I'm hoping to make some changes to how it loads the device info.

Sent from my SM-G975U using Tapatalk


  • johnlgalt and tomv5314 like this

5uWEQs7.jpg

 

Non potest esse nisi unus

 


#447 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 36,386 posts
  • Current Device(s):Pixel XL

Posted 13 March 2020 - 02:28 PM

I'm not ignoring this.  I've just been really really busy with family stuff the past couple weeks.  But I'm hoping this weekend I can finally get to this.


  • johnlgalt likes this

5uWEQs7.jpg

 

Non potest esse nisi unus

 


#448 johnlgalt

johnlgalt

    Antidisestablishmentarianist

  • Superuser
  • 4,759 posts
  • Twitter:https://twitter.com/JohnLGalt
  • Google+:google.com/+JohnLGalt_1
  • Location3rd Rock
  • Current Device(s):Pixel 4 XL 128 GB

Posted 23 March 2020 - 02:11 PM

Out of curiosity - I wonder how the new Android Flash tool compares with this....

 

Basic versus super-God level I would assume B)



#449 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 36,386 posts
  • Current Device(s):Pixel XL

Posted 23 March 2020 - 02:14 PM

Not sure.  Haven't had time to screw with anything lately.  I really do want to spend some time working on this soon.


  • johnlgalt likes this

5uWEQs7.jpg

 

Non potest esse nisi unus

 


#450 johnlgalt

johnlgalt

    Antidisestablishmentarianist

  • Superuser
  • 4,759 posts
  • Twitter:https://twitter.com/JohnLGalt
  • Google+:google.com/+JohnLGalt_1
  • Location3rd Rock
  • Current Device(s):Pixel 4 XL 128 GB

Posted 23 March 2020 - 02:18 PM

Android Flash tool - making use of WebUSB protocol:

 

https://source.andro...ontribute/flash

 

I haven't tried it yet, but I *do* have the Android 11 DevPrev2 (started with 1) on my Taimen.  Keeping the Coral free and clear of pre-├četa products, for now.  I may change, though, some really interesting features there.



#451 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 36,386 posts
  • Current Device(s):Pixel XL

Posted 23 March 2020 - 03:15 PM

To quote Luke in A New Hope....what a piece of junk!

 

Enable OEM Unlocking in the Developer options menu. If your bootloader is already unlocked, this option is grayed out with Bootloader is already unlocked.

 

Pfffffftttttt.  I never understood the concept here on this one.  If you're flashing signed images, why the F*** do I need to unlock?  This is why the HoG with OTA images is better.


5uWEQs7.jpg

 

Non potest esse nisi unus

 


#452 johnlgalt

johnlgalt

    Antidisestablishmentarianist

  • Superuser
  • 4,759 posts
  • Twitter:https://twitter.com/JohnLGalt
  • Google+:google.com/+JohnLGalt_1
  • Location3rd Rock
  • Current Device(s):Pixel 4 XL 128 GB

Posted 24 March 2020 - 08:35 AM

I have 2 theories.

 

  1. The Dev Preview are not actually signed.  As of yet.  Doesn't make a lot of sense, but that could be the case.
     
  2. The dev images that are provided on the page are the full system images only.  Although XDA links to the OTAs as well as the FSIs, if you actually go to the Google page, only the FSIs are listed - and the links to the Flash Tool images to be used are probably also to the FSIs as well, which, as we know, can 'only be flashed on unlocked devices'.  :p

IOW - stupidity.  Just like you said.



#453 SamuriHL

SamuriHL

    Android Warrior

  • Smod
  • 36,386 posts
  • Current Device(s):Pixel XL

Posted 24 March 2020 - 09:56 AM

Morons.  That's just carelessness.


  • johnlgalt likes this

5uWEQs7.jpg

 

Non potest esse nisi unus

 





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users