488 replies to this topic

[SamuriHL]

I only unlocked my Pixel XL so I could flash factory images.  Yet that "broke" android pay which is absolute bs.  In any case, if you're unlocked you can flash factory and/or ota images with the HoN.  Just make sure to grab the latest platform tools especially if you're on a Pixel 2.

[johnlgalt]

Yeah, Kaos warned me of that as well. But I tend to keep platform tools (and other SDK components as well) updated via the SDK manager anyway, so it's already ready.

I rarely every need the full system files, and I do occasionally use Pay, but I think I may change my mind soon and unlock it so I don't get trapped into a situation where I later cannot unlock it to flash a full system image after I break something. Which, knowing me, shouldn't be an issue, but making that assumption is not one I want to bank on.

Sent from my Pixel 2 XL using Tapatalk

[johnlgalt]

Giving this a shot, but my system is being stupid.  In writing the scripts in the HouseOfNexus folder on D:\, for an OTA it is supposed to spit out scripts in a newly created \NEXUS folder - which for whatever odd reason is not getting created.

 

I swear something went stupid in this latest clean install - gonna keep fighting it - should eventually get it working.  Needless to say, though, making a full backup of the phone first....

[SamuriHL]

That seems....odd.

[SamuriHL]

Looks like you found a nifty bug in the HoN that no one's caught.  If the NEXUS dir doesn't already exist, it doesn't create it when creating the script for the OTA.  Lovely.  I'll fix it when I get a chance.  Work around is to create the NEXUS dir before running the HoN.

[johnlgalt]

OK, so it wasn't my system (which, at this point, I was getting ready to flash, and then start another clean install process).  I guess that most ppl just opted to Flash the full system files, opting to keep data when doing so, rather then even try to flash the OTA.  And the few that opted to flash OTA probably just manually sideloaded it.  And yeah, upon creating the folder manually, it created all 3 scripts, which is (part of) what clued me in in the first place - when it was failing it was saying it created a single file and then saying it was completed....

 

Cool.  My work here is done - until a new version is released and I can test again

[SamuriHL]

Yea, maybe later tonight when I get a minute to look at it. Simple fix.  Just need to package it and all that fun stuff.

[johnlgalt]

No worries.

 

But this will make you laugh.

 

 

E:\update package is older than the current build, expected a build newer than timestamp 1510775026 but package has timestamp 1510540413 and downgrade not allowed.

Installation aborted.

 

Looks like I have to wait for the OTA since I am on the ßeta Preview build 2.....

[johnlgalt]

I actually saw that in the name of the files, and decided to try anyway, so I was at least partially expecting this to happen.

 

Filename of the ßeta Preview 2:  taimen-opp6.171019.012-factory-2e1202ea

Filename of the 8.1 Full system:  taimen-opm1.171019.011-factory-2df1c1cb

 

I saw the .11 and wondered if it would make a difference.  And now we know.

[SamuriHL]

No worries.

 

But this will make you laugh.

 

 

Looks like I have to wait for the OTA since I am on the ßeta Preview build 2.....

 

Ok, that's bad.  That's what Kaos saw when he tried to sideload an OTA.  This tells me they've done something very very bad to the Pixel 2.

[SamuriHL]

I actually saw that in the name of the files, and decided to try anyway, so I was at least partially expecting this to happen.

 

Filename of the ßeta Preview 2:  taimen-opp6.171019.012-factory-2e1202ea

Filename of the 8.1 Full system:  taimen-opm1.171019.011-factory-2df1c1cb

 

I saw the .11 and wondered if it would make a difference.  And now we know.

 

Not necessarily....

[SamuriHL]

2.9 RELEASED

 

• Fixed bug in OTA writing script where it fails if the NEXUS directory doesn't already exist

[johnlgalt]

He told me it's not the same error message

Sent from my Pixel 2 XL using Tapatalk

[SamuriHL]

Ok, that's probably good then.  But as I said, until I see a successful OTA sideload on a locked Pixel 2.....

[johnlgalt]

Indeed.  And it looks like I have to wait until they release the OTA for the upgrade from the ßeta Preview before I can do much of any kind of testing.

 

Sigh

[SamuriHL]

That'll only be pushed OTA...

[spainter]

interesting Last night I couldn't get HON 2.9 to set up the Nexus directory for flashing the Factory image files. It created the Directory and would get about 3/4 of the way through then just hang. Wouldn't lock up but hang like it was lost. Cleared everything out re booted the computer pulled a fresh download twice with different browsers. Finally I put the OTA in and turned it loose and everything went well through the setup and it created the flashme.bat file. The batch file ran through and installed the OTA right to the end. The phone said update complete but just before the Thanks for using House of Nexus message adb threw an error about not being able to read the last command. The phone booted and seems fine. I had Play Services throw a FC once since the upgrade but that is all.

 

When I used HON to flashed my Nexus 6 during the unzipping and creating the files in the Nexus directory it always unzipped the system.img file etc from the zipfile contained in the factory image file. I noticed it doesn't do that with the Pixel 2 images but looking at the flashme.batch file it didn't seem like it was suppose to.

 

@echo off

::Generated script from the House of Nexus 2.9.
::Generated script from the Factory Image: taimen-opm1.171019.011-factory-2df1c1cb.zip.

set PATH=I:\HouseOfNexus\TOOLS;%PATH%

set FASTBOOT_CMD=fastboot

%FASTBOOT_CMD% flash bootloader bootloader-taimen-tmz12a.img
%FASTBOOT_CMD% reboot-bootloader
ping -n 5 127.0.0.1 >nul

%FASTBOOT_CMD% flash radio radio-taimen-g8998-00164-1710262031.img
%FASTBOOT_CMD% reboot-bootloader
ping -n 5 127.0.0.1 >nul

:ask_wipe
    set choice=
    set /p choice=Wipe data? [y/n]:
    if "%choice%"=="y" goto wipe_data
    if "%choice%"=="Y" goto wipe_data
    if "%choice%"=="n" goto no_wipe_data
    if "%choice%"=="N" goto no_wipe_data
goto ask_wipe

:wipe_data
    %FASTBOOT_CMD% --skip-secondary -w update image-taimen-opm1.171019.011.zip
:end_wipe_data
    goto end

_wipe_data
    %FASTBOOT_CMD% --skip-secondary update image-taimen-opm1.171019.011.zip
:end_no_wipe_data
    goto end

:end
   echo Thanks for using the House of Nexus.
   pause
 

[SamuriHL]

That was changed a while ago.  LOL  So I'm guessing you didn't have 2.8 installed.  I made the change to flash in the same way that the factory image stock script flashes to make it easier when they change partitions and stuff.  I just verified that it worked for my Pixel XL factory image with no hanging or any other weird issues.  Wasn't sure if I introduced a regression because I moved where I delete/create the NEXUS directory.  Doesn't look like that's the case.

[spainter]

I don't delete the nexus directory just clean it out as a practice, but it worked fine. i hadn't flashed anything to the Nexus 6 since the first of October since there hasn't been anything to flash.  That's why I got so excited about the new Pixel, going into withdrawls

[SamuriHL]

You don't need to do anything with the NEXUS dir at all.  I delete and recreate it if it exists.  Otherwise it gets created.