471 replies to this topic

[johnlgalt]

D:\platform-tools>adb reboot bootloader

D:\platform-tools>fastboot devices
ZY222X6Z3C      fastboot

D:\platform-tools>fastboot --slot b
fastboot: usage: no command

D:\platform-tools>fastboot --set-active b
(bootloader) current-slot: not found
fastboot: usage: unknown command b

D:\platform-tools>fastboot --set-active a
(bootloader) current-slot: not found
fastboot: usage: unknown command a

D:\platform-tools>fastboot --set-active =a
(bootloader) current-slot: not found
fastboot: usage: unknown command =a

D:\platform-tools>fastboot --set-active =b
(bootloader) current-slot: not found
fastboot: usage: unknown command =b

D:\platform-tools>

It just returns that.  I tried both with and without =

[johnlgalt]

I'm also looking at the help and realize that I don't have to swap slots, since when using flash_all I could simply add the argument --slot all to the commands and for actions that involve the use of slots, it flashes both slots - *way* more handy for completely removing everything / paranoid flashing than my method of flash_all, change active slot, and flash_all again.....

[SamuriHL]

D:\platform-tools>adb reboot bootloader

D:\platform-tools>fastboot devices
ZY222X6Z3C      fastboot

D:\platform-tools>fastboot --slot b
fastboot: usage: no command

D:\platform-tools>fastboot --set-active b
(bootloader) current-slot: not found
fastboot: usage: unknown command b

D:\platform-tools>fastboot --set-active a
(bootloader) current-slot: not found
fastboot: usage: unknown command a

D:\platform-tools>fastboot --set-active =a
(bootloader) current-slot: not found
fastboot: usage: unknown command =a

D:\platform-tools>fastboot --set-active =b
(bootloader) current-slot: not found
fastboot: usage: unknown command =b

D:\platform-tools>

It just returns that.  I tried both with and without =

 

 

You got the syntax slightly off.

 

fastboot --set_active=_b

 

notice the _

[SamuriHL]

I'm also looking at the help and realize that I don't have to swap slots, since when using flash_all I could simply add the argument --slot all to the commands and for actions that involve the use of slots, it flashes both slots - *way* more handy for completely removing everything / paranoid flashing than my method of flash_all, change active slot, and flash_all again.....

 

Yes, I intentionally force it to NOT flash both slots at the same time.  I suppose I could change that but I'd still have to flash boot and radio to both slots regardless.

[johnlgalt]

You got the syntax slightly off.

 

fastboot --set_active=_b

 

notice the _

 

uh, no.

 

From my Taimen:

D:\platform-tools>adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
710KPMZ0254299  device


D:\platform-tools>adb reboot bootloader

D:\platform-tools>fastboot devices
710KPMZ0254299  fastboot

D:\platform-tools>fastboot --set-active=b
Setting current slot to 'b'                        OKAY [  0.016s]
Finished. Total time: 0.016s

D:\platform-tools>

Notice - no underscore nor space.

[johnlgalt]

I do see where I had an extra space in both for the Shamu.  I'll give it another whirl without the spaces.

[johnlgalt]

From Shamu, with love:

D:\platform-tools>adb devices
List of devices attached
ZY222X6Z3C      device


D:\platform-tools>adb reboot bootloader

D:\platform-tools>fastboot devices
ZY222X6Z3C      fastboot

D:\platform-tools>fastboot --set-active=b
(bootloader) slot-count: not found
fastboot: error: Device does not support slots

D:\platform-tools>

[johnlgalt]

I forgot to change the active slot back.  Booted and everything started FCing.

 

Booted back to bootloader, changed slot, an now phone thinks I am not set up, although all account info is there.

 

Short story, I'm about to HoGwash this thing with a pristine Q install to both slots.

 

I'll let Google set it all back up overnight.

[johnlgalt]

well f%$kity f%$k f%$k.

 

It DLd the file, then I clicked Magic - and nothing.

[johnlgalt]

So, HoG ain't playin' nice.   Magic button does nothing, when I selected Beta for Taimen.

 

I had to get this flashed so I could get it set up and head to bed.  So, I extracted the .ZIP and used flash_all - but with a twist.

 

For every fastboot flash command, I added the argument --slot all - so all flashing would be to both slots where applicable.

 

Sure enough, it worked like a champ.

Microsoft Windows [Version 10.0.18855.1000]
(c) 2018 Microsoft Corporation. All rights reserved.

D:\Users\{userlogin}\AppData\Roaming\HouseOfGoogle\IMAGES\taimen\taimen-qpp1.190205.018.b4>fastboot devices
710KPMZ0254299  fastboot

D:\Users\{userlogin}\AppData\Roaming\HouseOfGoogle\IMAGES\taimen\taimen-qpp1.190205.018.b4>PATH=%PATH%;"%SYSTEMROOT%\System32"

D:\Users\{userlogin}\AppData\Roaming\HouseOfGoogle\IMAGES\taimen\taimen-qpp1.190205.018.b4>fastboot flash bootloader bootloader-taimen-tmz20o.img --slot all
Sending 'bootloader_a' (36356 KB)                  OKAY [  0.255s]
Writing 'bootloader_a'                             OKAY [  0.487s]
Sending 'bootloader_b' (36356 KB)                  OKAY [  0.264s]
Writing 'bootloader_b'                             OKAY [  0.271s]
Finished. Total time: 1.292s

D:\Users\{userlogin}\AppData\Roaming\HouseOfGoogle\IMAGES\taimen\taimen-qpp1.190205.018.b4>fastboot reboot-bootloader
rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s

D:\Users\{userlogin}\AppData\Roaming\HouseOfGoogle\IMAGES\taimen\taimen-qpp1.190205.018.b4>ping -n 5 127.0.0.1 >nul

D:\Users\{userlogin}\AppData\Roaming\HouseOfGoogle\IMAGES\taimen\taimen-qpp1.190205.018.b4>fastboot flash radio radio-taimen-g8998-00008-1901230130.img --slot all
Sending 'radio_a' (60372 KB)                       OKAY [  0.418s]
Writing 'radio_a'                                  OKAY [  1.509s]
Sending 'radio_b' (60372 KB)                       OKAY [  0.418s]
Writing 'radio_b'                                  OKAY [  1.440s]
Finished. Total time: 3.785s

D:\Users\{userlogin}\AppData\Roaming\HouseOfGoogle\IMAGES\taimen\taimen-qpp1.190205.018.b4>fastboot reboot-bootloader
rebooting into bootloader                          OKAY [  0.016s]
Finished. Total time: 0.016s

D:\Users\{userlogin}\AppData\Roaming\HouseOfGoogle\IMAGES\taimen\taimen-qpp1.190205.018.b4>ping -n 5 127.0.0.1 >nul

D:\Users\{userlogin}\AppData\Roaming\HouseOfGoogle\IMAGES\taimen\taimen-qpp1.190205.018.b4>fastboot -w --slot all update image-taimen-qpp1.190205.018.b4.zip
Warning: slot set to 'all'. Secondary slots will not be flashed.
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ20o
Baseband Version.....: g8998-00008-1901230130
Serial Number........: 710KPMZ0254299
--------------------------------------------
Checking product                                   OKAY [  0.000s]
Checking version-bootloader                        OKAY [  0.015s]
Checking version-baseband                          OKAY [  0.000s]
extracting boot.img (40 MB) to disk... took 0.179s
archive does not contain 'boot.sig'
archive does not contain 'boot.sig'
extracting dtbo.img (8 MB) to disk... took 0.022s
archive does not contain 'dtbo.sig'
archive does not contain 'dtbo.sig'
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'
archive does not contain 'recovery.img'
archive does not contain 'super.img'
extracting system.img (2374 MB) to disk... took 12.533s
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
archive does not contain 'vbmeta.sig'
extracting vendor.img (344 MB) to disk... took 2.012s
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 29518843 4k blocks and 7380992 inodes
Filesystem UUID: 8f05d8fe-4ae0-11e9-8361-6183570a530b
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
        4096000, 7962624, 11239424, 20480000, 23887872

Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'boot_a' (40960 KB)                        OKAY [  0.286s]
Writing 'boot_a'                                   OKAY [  0.534s]
Sending 'boot_b' (40960 KB)                        OKAY [  0.286s]
Writing 'boot_b'                                   OKAY [  1.912s]
Sending 'dtbo_a' (8192 KB)                         OKAY [  0.053s]
Writing 'dtbo_a'                                   OKAY [  0.380s]
Sending 'dtbo_b' (8192 KB)                         OKAY [  0.054s]
Writing 'dtbo_b'                                   OKAY [  0.402s]
Sending 'vbmeta_a' (4 KB)                          OKAY [  0.000s]
Writing 'vbmeta_a'                                 OKAY [  0.000s]
Sending 'vbmeta_b' (4 KB)                          OKAY [  0.016s]
Writing 'vbmeta_b'                                 OKAY [  0.000s]
Setting current slot to 'a'                        OKAY [  0.100s]
Erasing 'userdata'                                 OKAY [  6.438s]
Sending 'userdata' (4672 KB)                       OKAY [  0.047s]
Writing 'userdata'                                 OKAY [  0.107s]
Rebooting
Finished. Total time: 25.988s

D:\Users\{userlogin}\AppData\Roaming\HouseOfGoogle\IMAGES\taimen\taimen-qpp1.190205.018.b4>

Any sort of log stored somewhere that I can send you to figure out why it just hung on magic?

[SamuriHL]

No but I'll figure it out later today.

Sent from my Pixel XL using Tapatalk

[SamuriHL]

I want to get back into this because I'm not seeing the same issue as you.  Are you sure you had the phone connected in either ADB or fasbtoot mode when you tried clicking the magic button???  Cause it will give you an error in the status text if you don't and it'll seem like "it's doing nothing".

[johnlgalt]

It was connected and verified in the app - I get it to fastboot mode *before* starting HoG.

 

I forgot to get the 'log' from the text box.  I'll give it another shot tonight.

[SamuriHL]

Yea, something's not right and I can't really test it since I'm not unlocked.  But for me it seems to work as well as it can for me.  Meaning it's calling the code and all that.  And if the magic button is enabled, it found your image.  So, it's not that.  Very strange.

[johnlgalt]

Yeah - everything was fine up to the point of Magic.  But pressing the Magic button did nothing at all.

 

I know it was not a fastboot issue as I still had the cmd window that I used to put the phone in bootloader from adb, and I used the same window without reseating he cable in the phone to use flash_all to flash the system files.  And as I said, it had downloaded the file and I even deleted that download and let it download it again to see if that made a difference.

 

Since I am unlocked, and since I have not fully set up my phone, I might try again.  The biggest issue I am having right now is that with a full system image flash, TWRP latest for Taimen refuses to decrypt the data.  That is critical, as I cannot make a backup of the data partitions to keep playing around - which means that I have to either let Google restore my data, or use a round-about method like TiBu and skip those that are already stored elsewhere, like a game account in Play Games.

 

Not happy about that at all.

 

I do have one trick to try and see if it (decrypting) works - but I suspect it will not.  If it works, I will be back in business and able to test HoG a lot more- if not, well, then HoG testing will have to be relegated to nighttime testing only, as I need my phone set up and working during the day.

[johnlgalt]

Interesting.

 

I thought only factory system images were available for Q for Pixels - turns out the OTAs are also there.

 

Factory images;  https://developer.an...review/download

 

OTAs:  https://developer.an...ew/download-ota

 

Now I'm all convoluted.  lol.

[SamuriHL]

That was added after the damn factory images then.  Grrrrrrrr.  LOL  I'll add support for them here in a bit.  I still don't know what's going on with your issue.  I'll trace the code and see if I see a glaring bug that I've introduced.

[johnlgalt]

I'm off for now.  I'll set up a testbench for my Taimen later this evening and see if I can figure out what is going on - I just realized that I did not reboot between the 2 attempts, though that *should* not have affected it, particularly when flash_all worked.

 

In looking in my Profile folder, I see that the download was there - but no attempt was made to extract.  Only 2 folders, Images and Tools.

[SamuriHL]

That's an interesting clue then.  I'll see what's going on.

[SamuriHL]

LMAO um, yup, that was stupid on my part.  Found your bug and accidentally fixed it when I added OTA support for betas.  LOL!  So this upcoming version which I'll upload in a minute will be a little bit different.  What's going to happen is that it'll work like before.  Select factory or ota, then your device.  Now, here's the difference....I DO NOT want to auto-select the BETA images for a device, so, I added code to ensure that it will select the last release build for the device.  That being said, if you look in the version drop down, you will see BETA as the last entry if there is a beta for your device.  Selecting that will auto select the beta image in the list box.  So now that I put it back to factory and ota instead of factory, ota, and beta, the code that activates when you press magic will actually have a f***ing clue what it's supposed to do.  LOL  (Hint....I didn't have a handler for the BETA type....WOOPS).