471 replies to this topic

[johnlgalt]

Yeah, booted just fine. 

 

I just found out something.

 

Background:  I'm a little ... ornery, if you will ... about file management.  I hate having the same file lying around in multiple places.  But I also hate having to go digging many levels deep for files.  So, I've developed a system that works for me.

 

I have files that are slated for permanent storage in folders that make sense.  For example, one of my 1 TB Seagates (don't start - we've agreed to disagree about them) has folders named Android related, Storage, and several other folders.  In Android related, I have folders for Android Studio, Apps, Devices, Misc, Motorola, ROMs, Root, SamuriHL (yes, you!), SuperSU Installers, and TWRP images.

 

In devices, I have a device name listed (whether it be by user, such as my sister, or it be by device codename, such as Taimen or Shamu) and in these folders I have several other folder,s usually the following:  Drivers & Binaries, Full System, Internal Storage, OTA, ROMs, TWRP, and βeta.  As you can guess, each of those folders stores different files, mostly stuff I get from Google for the images, and such.  Now, since I have these in the device specific folder, there is no need for me to have them again in a higher tree - so that's where I use symbolic links to link these files to the folders more easily accessible (and thus leaving me with much less typing when using CL).

 

So, naturally, in F:\Android related\TWRP IMages\ I have a symbolic link to "F:\Android related\Devices\Taimen\TWRP\twrp-3.2.3-1-taimen.img", as well as other files.

 

Turns out, fastboot has no issue when I used "F:\Android related\TWRP images\twrp-3.2.3-1-taimen.img" as the path for boot TWRP - it booted right up.

 

However, when I tried to use symbolic links for files to push to the device when in recovery using adb push, adb was not happy about it.

 

Not.

 

One.

 

Bit.

 

If I navigate to the actual repository and use the file's full path adb has no issues pushing the file - but it won't work with symbolically linked files.

 

I suppose that I could try a hardlink - but, why? - if I delete one hardlink all of them go, right?  That would be a PITA for storage, because I tend to keep multiple version of files, particularly when dealing with βeta releases of things like root installers and Android versions....

 

Oh well.

 

I think that I am going to let my computer install the latest Windows IP 20H1 build 18860 while I go about setting up my phone on Q DP1 again, and call it a night.  Even with my nap, I'm feeling tired, for some reason.

 

Lights out.

[SamuriHL]

Well that was a good bit of testing and it seems things are working from the house of Google perspective so that's good. Tomorrow I will concentrate on getting the essential support done as I suspect it will probably join the Q betas at some point. Either way I'd like to have that support done and refactor some of the code around the website parsing.

Sent from my Pixel XL using Tapatalk

[johnlgalt]

Woke up to my phone not able to connect to FI and trying to activate it is giving me either a G003 or T120 error.

 

Not f%$king cool.

 

This is not HoG's fault - trust me - I'm betting that it is the fault of either Q or Magisk.  If it is Magisk, I have a report to make.

 

If it is Q...#%^$@%^@$%&$#@^&^$#%& Fi.....

[SamuriHL]

That's not kuel at all. Ugh!!!

Sent from my Pixel XL using Tapatalk

[johnlgalt]

OK, so check this $#!+ out.

 

Google Fi app is not activating, giving me alternating errors of G003 and T120.  But, in the background, Fi is actually working - I can make calls, send SMS and even have a working data connection, and the phone shows me the LTE icon next to the mobile data icon.

 

WT Seriously F is going on?

 

(Answer - Fi app needs an update to work correctly with Q, apparently)

[johnlgalt]

I'm traveling to Atlanta again and had to make sure my data was working for Maps - otherwise I owuldn't be all bent out of shape about this. 

 

It looks like I may have to flash Pie onto the phone, set it up completely, including Fi, and then take the Q DP1 OTA.  And I obviously do not have time to do al that $#!+ right now...

[johnlgalt]

So, I get to test HoG some more this evening / tonight

[SamuriHL]

Good lord that's a pain in the ass.

Sent from my Pixel XL using Tapatalk

[SamuriHL]

Ya know...the essential just really irritates me.  LOL  That's all. 

[SamuriHL]

OMFG Essential you guys ROYALLY SUCKKKKKKKKKKKKKKKKKKKKKKKKKK!!!!!!!!!!!!!!!!!!!  They are REALLY truly pissing me off.  Turns out you can't download the images unless you are signed into your google account.  So, I actually can't simply just download the images from the HoG.  I've spent literally all day getting this stupid code built to find out I can't even download it without authentication.  Hello!  Google doesn't even f***ing do that with their own images!!!!!!!!!!!!!!  The Essential can go F*** itself!

[johnlgalt]

I used my Fi account all day-  and during the entire time I had a notification stating that my Fi account was not set up.

 

I'll have to go back and check, but I think there was a similar mini-fiasco with Pie, now that I think about it.  The app was slow on the uptake with the newly released DPx of Pie last year, and when I decided to clean install it activating my Fi account took a lot of work.  I need to figure out where I was posting all that, if it was here or XDA or elsewhere.  That will help enlighten me.

 

However, I had 0 issues with Fi connectivity while I was on the road in various parts of Atlanta and a few of the suburbs - I mean 0.  Flawless connectivity - just like it should be.

 

Now, if I am correct, I'll have to clean flash Pie, set up my Fi, and then flash the OTA over Pie.  Ugh.

[SamuriHL]

I'm beyond irritated with the essential site at this point.

[johnlgalt]

I'm beyond irritate with Fi at this point.  Second time in a row they've dropped the ball in terms of being ready for an impending release of a DP build.

[SamuriHL]

But it's not like Fi is a Google app so how could they POSSIBLY be prepared for a Google beta?  LMAO

[johnlgalt]

Get outta my head!

 

(But, yeah, exactly what I was trying to figure out myself....)

[SamuriHL]

I'm just glad the HoG works as well as it does so far. I'll probably do some more work on it tomorrow.

Sent from my Pixel XL using Tapatalk

[johnlgalt]

OK.

 

I'm about to flash Pie to both slots and then set up my phone on slot A, and see if it receives the Q DP1 OTA automatically or not.

 

I really need to get Fi working correctly.  Hoping that this Pie flash does the trick.

[johnlgalt]

%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe --skip-secondary update %APPDATA%\HouseOfGoogle\IMAGES\taimen\FACTORY\image-taimen-pq2a.190305.002.zip

In reading the fastboot help section, I see that --skip-secondary means just that:

--skip-secondary           Don't flash secondary slots in flashall/update.

But in layman's terms - does this mean that if you leave that out and do the first parts using

 --slot SLOT                Use SLOT; 'all' for both slots, 'other' for
                            non-current slot (default: current active slot).

where SLOT is replaced by all, will effectively flash both slots all the way through?

 

If so, that would be a great....I'm almost tempted to try it on my phone manually... lol.

[johnlgalt]

So, I am doing this manually through HoG.  I first ran HoG for the latest Pie for Taimen.  Let it do its thing.

Platform tools found.
Found Device: Pixel 2 XL (taimen)
Extract: %APPDATA%\HouseOfGoogle\IMAGES\taimen\taimen-pq2a.190305.002-factory-8f42be1a.zip
To: %APPDATA%\HouseOfGoogle\IMAGES\taimen\FACTORY\
extract: bootloader-taimen-tmz20o.img
extract: image-taimen-pq2a.190305.002.zip
extract: radio-taimen-g8998-00253-1811291732.img
Extract complete.
%APPDATA%\HouseOfGoogle\TOOLS\adb.exe reboot bootloader
Starting flash...
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe flash bootloader %APPDATA%\HouseOfGoogle\IMAGES\taimen\FACTORY\bootloader-taimen-tmz20o.img
Sending 'bootloader_a' (36356 KB)                  OKAY [  0.250s]
Writing 'bootloader_a'                             OKAY [  0.906s]
Finished. Total time: 1.234s
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe reboot-bootloader
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s
Sleep 5 seconds for reboot...
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe flash radio %APPDATA%\HouseOfGoogle\IMAGES\taimen\FACTORY\radio-taimen-g8998-00253-1811291732.img
Sending 'radio_a' (60388 KB)                       OKAY [  0.422s]
Writing 'radio_a'                                  OKAY [  0.797s]
Finished. Total time: 1.359s
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe reboot-bootloader
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s
Sleep 5 seconds for reboot...
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe erase userdata
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata'                                 OKAY [  2.796s]
Finished. Total time: 2.796s
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe --skip-secondary update %APPDATA%\HouseOfGoogle\IMAGES\taimen\FACTORY\image-taimen-pq2a.190305.002.zip
--------------------------------------------
Bootloader Version...: TMZ20o
Baseband Version.....: g8998-00253-1811291732
Serial Number........: 710KPMZ0254299
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product'                                 OKAY [  0.000s]
Checking 'version-bootloader'                      OKAY [  0.000s]
Checking 'version-baseband'                        OKAY [  0.000s]
Setting current slot to 'a'                        OKAY [  0.016s]
extracting boot.img (40 MB) to disk... took 0.188s
archive does not contain 'boot.sig'
Sending 'boot_a' (40960 KB)                        OKAY [  0.281s]
Writing 'boot_a'                                   OKAY [  0.531s]
extracting dtbo.img (8 MB) to disk... took 0.031s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB)                         OKAY [  0.062s]
Writing 'dtbo_a'                                   OKAY [  0.094s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_a' (4 KB)                          OKAY [  0.000s]
Writing 'vbmeta_a'                                 OKAY [  0.000s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product_services.img'
extracting system.img (2221 MB) to disk... took 12.406s
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/5 (524284 KB)          OKAY [  4.265s]
Writing 'system_a'                                 OKAY [  2.219s]
Sending sparse 'system_a' 2/5 (524284 KB)          OKAY [  4.235s]
Writing 'system_a'                                 OKAY [  2.203s]
Sending sparse 'system_a' 3/5 (524284 KB)          OKAY [  4.273s]
Writing 'system_a'                                 OKAY [  2.196s]
Sending sparse 'system_a' 4/5 (521180 KB)          OKAY [  4.285s]
Writing 'system_a'                                 OKAY [  2.203s]
Sending sparse 'system_a' 5/5 (181280 KB)          OKAY [  1.515s]
Writing 'system_a'                                 OKAY [  0.750s]
extracting vendor.img (351 MB) to disk... took 2.297s
archive does not contain 'vendor.sig'
Sending 'vendor_a' (359960 KB)                     OKAY [  2.500s]
Writing 'vendor_a'                                 OKAY [  1.500s]
Rebooting                                          OKAY [  0.016s]
Finished. Total time: 55.005s
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe reboot
< waiting for any device >
Rebooting                                          OKAY [  0.000s]
Finished. Total time: 0.000s
Flash complete.  Thank you for using the House of Google!

I then skipped all set up, enabled DevOps, enabled USB Debugging, so I could then boot to fastboot, then boot TWRP.  Using TWRP, I verified the current active slot (A), then swapped to the other slot (.  I then rebooted, started HoG again, and reflashed Pie (which is now slot ( ):

Platform tools found.
Found Device: Pixel 2 XL (taimen)
Extract: %APPDATA%\HouseOfGoogle\IMAGES\taimen\taimen-pq2a.190305.002-factory-8f42be1a.zip
To: %APPDATA%\HouseOfGoogle\IMAGES\taimen\FACTORY\
extract: bootloader-taimen-tmz20o.img
extract: image-taimen-pq2a.190305.002.zip
extract: radio-taimen-g8998-00253-1811291732.img
Extract complete.
%APPDATA%\HouseOfGoogle\TOOLS\adb.exe reboot bootloader
Starting flash...
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe flash bootloader %APPDATA%\HouseOfGoogle\IMAGES\taimen\FACTORY\bootloader-taimen-tmz20o.img
Sending 'bootloader_b' (36356 KB)                  OKAY [  0.266s]
Writing 'bootloader_b'                             OKAY [  0.563s]
Finished. Total time: 0.891s
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe reboot-bootloader
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s
Sleep 5 seconds for reboot...
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe flash radio %APPDATA%\HouseOfGoogle\IMAGES\taimen\FACTORY\radio-taimen-g8998-00253-1811291732.img
Sending 'radio_b' (60388 KB)                       OKAY [  0.422s]
Writing 'radio_b'                                  OKAY [  0.813s]
Finished. Total time: 1.344s
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe reboot-bootloader
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s
Sleep 5 seconds for reboot...
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe erase userdata
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata'                                 OKAY [  0.969s]
Finished. Total time: 0.969s
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe --skip-secondary update %APPDATA%\HouseOfGoogle\IMAGES\taimen\FACTORY\image-taimen-pq2a.190305.002.zip
--------------------------------------------
Bootloader Version...: TMZ20o
Baseband Version.....: g8998-00253-1811291732
Serial Number........: 710KPMZ0254299
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product'                                 OKAY [  0.000s]
Checking 'version-bootloader'                      OKAY [  0.000s]
Checking 'version-baseband'                        OKAY [  0.000s]
Setting current slot to 'b'                        OKAY [  0.016s]
extracting boot.img (40 MB) to disk... took 0.203s
archive does not contain 'boot.sig'
Sending 'boot_b' (40960 KB)                        OKAY [  0.297s]
Writing 'boot_b'                                   OKAY [  0.531s]
extracting dtbo.img (8 MB) to disk... took 0.016s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB)                         OKAY [  0.062s]
Writing 'dtbo_b'                                   OKAY [  0.094s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB)                          OKAY [  0.000s]
Writing 'vbmeta_b'                                 OKAY [  0.016s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product_services.img'
extracting system.img (2221 MB) to disk... took 12.516s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/5 (524284 KB)          OKAY [  4.234s]
Writing 'system_b'                                 OKAY [  2.219s]
Sending sparse 'system_b' 2/5 (524284 KB)          OKAY [  4.250s]
Writing 'system_b'                                 OKAY [  2.203s]
Sending sparse 'system_b' 3/5 (524284 KB)          OKAY [  4.234s]
Writing 'system_b'                                 OKAY [  2.203s]
Sending sparse 'system_b' 4/5 (521180 KB)          OKAY [  4.203s]
Writing 'system_b'                                 OKAY [  2.188s]
Sending sparse 'system_b' 5/5 (181280 KB)          OKAY [  1.453s]
Writing 'system_b'                                 OKAY [  0.750s]
extracting vendor.img (351 MB) to disk... took 2.094s
archive does not contain 'vendor.sig'
Sending 'vendor_b' (359960 KB)                     OKAY [  2.484s]
Writing 'vendor_b'                                 OKAY [  1.500s]
Rebooting                                          OKAY [  0.016s]
Finished. Total time: 54.578s
%APPDATA%\HouseOfGoogle\TOOLS\fastboot.exe reboot

First off, notice the end of each flash - the second time it never gave me the "Thank you statement."

 

Second off, I see where the slot name was associated with each action.  I know for a fact (because I already did this once) that you can use --slot all for the manual flash sequences, but it does not work with the update sequence - but I see how you added the --skip-secondary - so I'm betting if I alter flash_all non-update (flash) command by adding the argument --slot all and then make sure that the update does not have the --skip-secondary command, it will effectively be the same as flashing both slots independently, right?

[johnlgalt]

Ha!

 

I got it to work.  Command structure:

fastboot.exe flash bootloader bootloader-taimen-tmz20o.img --slot all
fastboot.exe reboot-bootloader
fastboot.exe flash radio radio-taimen-g8998-00253-1811291732.img --slot all
fastboot.exe reboot-bootloader
fastboot.exe erase userdata
fastboot.exe update image-taimen-pq2a.190205.002.zip
fastboot.exe reboot

Output:

F:\Android related\Devices\Taimen\Full System\taimen-pq2a.190205.002>adb devices
List of devices attached
710KPMZ0254299  device

F:\Android related\Devices\Taimen\Full System\taimen-pq2a.190205.002>adb reboot bootloader

F:\Android related\Devices\Taimen\Full System\taimen-pq2a.190205.002>fastboot devices
710KPMZ0254299  fastboot

F:\Android related\Devices\Taimen\Full System\taimen-pq2a.190205.002>fastboot.exe flash bootloader bootloader-taimen-tmz20o.img --slot all
Sending 'bootloader_a' (36356 KB)                  OKAY [  0.250s]
Writing 'bootloader_a'                             OKAY [  0.484s]
Sending 'bootloader_b' (36356 KB)                  OKAY [  0.250s]
Writing 'bootloader_b'                             OKAY [  0.266s]
Finished. Total time: 1.375s

F:\Android related\Devices\Taimen\Full System\taimen-pq2a.190205.002>fastboot.exe reboot-bootloader
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.016s

F:\Android related\Devices\Taimen\Full System\taimen-pq2a.190205.002>fastboot.exe flash radio radio-taimen-g8998-00253-1811291732.img --slot all
Sending 'radio_a' (60388 KB)                       OKAY [  0.422s]
Writing 'radio_a'                                  OKAY [  2.000s]
Sending 'radio_b' (60388 KB)                       OKAY [  0.406s]
Writing 'radio_b'                                  OKAY [  0.781s]
Finished. Total time: 3.813s

F:\Android related\Devices\Taimen\Full System\taimen-pq2a.190205.002>fastboot.exe reboot-bootloader
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s

F:\Android related\Devices\Taimen\Full System\taimen-pq2a.190205.002>fastboot.exe erase userdata
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata'                                 OKAY [  1.141s]
Finished. Total time: 1.141s

F:\Android related\Devices\Taimen\Full System\taimen-pq2a.190205.002>fastboot.exe update image-taimen-pq2a.190305.002.zip
W/ziparchive(12712): Unable to open 'image-taimen-pq2a.190305.002.zip': No such file or directory
fastboot: error: failed to open zip file 'image-taimen-pq2a.190305.002.zip': I/O error

F:\Android related\Devices\Taimen\Full System\taimen-pq2a.190205.002>fastboot update image-taimen-pq2a.190205.002.zip
--------------------------------------------
Bootloader Version...: TMZ20o
Baseband Version.....: g8998-00253-1811291732
Serial Number........: 710KPMZ0254299
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product'                                 OKAY [  0.016s]
Checking 'version-bootloader'                      OKAY [  0.000s]
Checking 'version-baseband'                        OKAY [  0.000s]
Setting current slot to 'b'                        OKAY [  0.000s]
extracting boot.img (40 MB) to disk... took 0.188s
archive does not contain 'boot.sig'
Sending 'boot_b' (40960 KB)                        OKAY [  0.281s]
Writing 'boot_b'                                   OKAY [  0.531s]
extracting dtbo.img (8 MB) to disk... took 0.016s
archive does not contain 'dtbo.sig'
Sending 'dtbo_b' (8192 KB)                         OKAY [  0.047s]
Writing 'dtbo_b'                                   OKAY [  0.094s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta_b' (4 KB)                          OKAY [  0.000s]
Writing 'vbmeta_b'                                 OKAY [  0.000s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
archive does not contain 'product_services.img'
extracting system.img (2221 MB) to disk... took 12.125s
archive does not contain 'system.sig'
Sending sparse 'system_b' 1/5 (524284 KB)          OKAY [  4.203s]
Writing 'system_b'                                 OKAY [  2.188s]
Sending sparse 'system_b' 2/5 (524284 KB)          OKAY [  4.235s]
Writing 'system_b'                                 OKAY [  2.203s]
Sending sparse 'system_b' 3/5 (524284 KB)          OKAY [  4.235s]
Writing 'system_b'                                 OKAY [  2.203s]
Sending sparse 'system_b' 4/5 (521180 KB)          OKAY [  4.188s]
Writing 'system_b'                                 OKAY [  2.187s]
Sending sparse 'system_b' 5/5 (180808 KB)          OKAY [  1.453s]
Writing 'system_b'                                 OKAY [  0.750s]
extracting system_other.img (320 MB) to disk... took 1.969s
archive does not contain 'system.sig'
Sending 'system_a' (328696 KB)                     OKAY [  2.297s]
Writing 'system_a'                                 OKAY [  1.391s]
extracting vendor.img (351 MB) to disk... took 2.250s
archive does not contain 'vendor.sig'
Sending 'vendor_b' (359936 KB)                     OKAY [  2.563s]
Writing 'vendor_b'                                 OKAY [  1.531s]
archive does not contain 'vendor_other.img'
Rebooting                                          OKAY [  0.000s]
Finished. Total time: 60.813s

F:\Android related\Devices\Taimen\Full System\taimen-pq2a.190205.002>

Or ... it seemingly worked?

 

It didn't flash a full system to (A) - but in looking at the structure,it seems that is normal - it flashes enough for the system to process an OTA flash to the inactive slot, right?

 

Yes, I know, this is for the paranoid only - but you can also look at it as this is for those who have some fracked their devices and get that stupid "Your data is corrupted" message.  I got that more than once when I only flashed to one slot after flashing a custom ROM, and also when I used HoG the yesterday when I ran those tests - something b0rked hard so I had to do the Pie --> Q OTA flash in the first place.

 

But I'm happy this works the way it is intended.