471 replies to this topic

[SamuriHL]

Rebooting to recovery...
adb reboot recovery
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb reboot recovery complete...
Sideload in progress.
adb sideload D:\dev\projects\HoG\HoG\bin\x64\Release\IMAGES\marlin\marlin-ota-pq2a.190205.003-471a4610.zip
Total xfer: 2.00x                                                                                                       
adb sideload D:\dev\projects\HoG\HoG\bin\x64\Release\IMAGES\marlin\marlin-ota-pq2a.190205.003-471a4610.zip complete...

[SamuriHL]

Um, it lost all the rest of what I posted.  Lovely.  I was attempting to say that I didn't break anything.  I'm going to add a piece of functionality for you to make re-testing worthwhile, then I'm going to upload a new version.

[SamuriHL]

New version is up and ready for testing.  It'll need a factory and ota test to ensure nothing's broken.  It should all just work the same.  I hope.

[johnlgalt]

Gah - you were online building last night.  I was taking it easy because allergies hit me like a two-ton, heavy thing,

 

So, I'll flash Bliss onto the Shamu, then use the utility to flash the Sept 2017 factory image and finally use it again to flash the Oct 2017 OTA.

 

Anything else?

[SamuriHL]

That'll suffice for now.  I'm currently in the middle of arguing with visual studio about adding an extension I need to complete turning this into a beta.  Let's just say it's pissing me off.

[johnlgalt]

Lol. 

 

OK, so I installed Bliss, but upon boot even after a full wipe before install, it asked for a 'decryption pw' - which I entered my PIN (which the previous stock install did NOT have a PIN or anything else).  That, of course, failed, so now it is performing a factory reset, which, as we all know and love on the Shamu, takes half a lifetime.

 

So, it will be a while before I actually get around to the testing part.

 

In keeping with the testing mechanism, I'm also going to let the app download the required Factory image and OTA, instead of using the ones I have DLd.

 

That should give me about as full a testing procedure with what you have coded thus far, on 0.7

[SamuriHL]

Yea, that'll be good.  I take it you're not reading my release notes cause you haven't yet commented about the new version. 

[johnlgalt]

You take it right - I haven't extracted it yet, much less read anything.  Although I have read the previous ones (but only so I could assign the correct version number to the .ZIP - I've got all 8 of them thus far lol).

[johnlgalt]

Only someone?

[johnlgalt]

Holy $#!+, I'm getting more feedback, too.  Nice.

[johnlgalt]

Flash from Bliss --> Stock Sept 2017 image, using HoG to DL:

 

log:

D:\HouseOfGoogle\IMAGES\shamu\shamu-ngi55d-factory-1132151d.zip
SHA256 VERIFIED!
Download complete...
Extract: D:\HouseOfGoogle\IMAGES\shamu\shamu-ngi55d-factory-1132151d.zip
To: D:\HouseOfGoogle\IMAGES\shamu\FACTORY\
extract: image-shamu-ngi55d.zip
extract: radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
extract: bootloader-shamu-moto-apq8084-72.04.img
Extract complete.
Starting flash...
fastboot flash bootloader D:\HouseOfGoogle\IMAGES\shamu\FACTORY\bootloader-shamu-moto-apq8084-72.04.img
(bootloader) has-slot:bootloader: not found
Sending 'bootloader' (4071 KB)                     OKAY [  0.154s]
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.700s]
Finished. Total time: 0.955s
fastboot flash bootloader D:\HouseOfGoogle\IMAGES\shamu\FACTORY\bootloader-shamu-moto-apq8084-72.04.img complete...
fastboot reboot-bootloader
rebooting into bootloader                          OKAY [  0.016s]
Finished. Total time: 0.016s
fastboot reboot-bootloader complete...
Sleep 5 seconds for reboot...
fastboot flash radio D:\HouseOfGoogle\IMAGES\shamu\FACTORY\radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
(bootloader) has-slot:radio: not found
Sending 'radio' (115507 KB)                        OKAY [  4.221s]
Writing 'radio'                                    (bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [  1.596s]
Finished. Total time: 5.912s
fastboot flash radio D:\HouseOfGoogle\IMAGES\shamu\FACTORY\radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img complete...
fastboot reboot-bootloader
rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s
fastboot reboot-bootloader complete...
Sleep 5 seconds for reboot...
fastboot --skip-secondary -w update D:\HouseOfGoogle\IMAGES\shamu\FACTORY\image-shamu-ngi55d.zip
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 14585824 4k blocks and 3646496 inodes
Filesystem UUID: f5d93fac-3dd0-11e9-bbdf-dffb6a6f1972
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 
	4096000, 7962624, 11239424
Allocating group tables:   0/446       done                            
Writing inode tables:   0/446       done                            
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information:   0/446       done
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 65536 4k blocks and 65536 inodes
Filesystem UUID: f60c5ca2-3dd0-11e9-96aa-d17d98a1bc81
Superblock backups stored on blocks: 
	32768
Allocating group tables: 0/2   done                            
Writing inode tables: 0/2   done                            
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: 0/2   done
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.005s]
Checking version-bootloader                        OKAY [  0.000s]
Checking version-baseband                          OKAY [  0.005s]
extracting boot.img (8 MB) to disk... took 0.030s
(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.040s
(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.146s
(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
(bootloader) erase-block-size: not found
(bootloader) logical-block-size: not found
(bootloader) erase-block-size: not found
(bootloader) logical-block-size: not found
Erase successful, but not automatically formatting.
File system type raw not supported.
Sending 'boot' (8497 KB)                           OKAY [  0.313s]
Writing 'boot'                                     OKAY [  0.146s]
Sending 'recovery' (13887 KB)                      OKAY [  0.508s]
Writing 'recovery'                                 OKAY [  0.206s]
Sending sparse 'system' 1/4 (522524 KB)            OKAY [ 19.998s]
Writing sparse 'system' 1/4                        OKAY [  7.762s]
Sending sparse 'system' 2/4 (517601 KB)            OKAY [ 19.608s]
Writing sparse 'system' 2/4                        OKAY [  7.088s]
Sending sparse 'system' 3/4 (508949 KB)            OKAY [ 19.481s]
Writing sparse 'system' 3/4                        OKAY [  7.000s]
Sending sparse 'system' 4/4 (32756 KB)             OKAY [  1.235s]
Writing sparse 'system' 4/4                        OKAY [  0.407s]
Erasing 'userdata'                                 OKAY [  2.046s]
Sending 'userdata' (4396 KB)                       OKAY [  0.162s]
Writing 'userdata'                                 OKAY [  1.780s]
Erasing 'cache'                                    OKAY [  0.035s]
Sending 'cache' (120 KB)                           OKAY [  0.016s]
Writing 'cache'                                    OKAY [  0.031s]
Erasing 'metadata'                                 (bootloader) Permission denied
FAILED (remote: '')
Finished. Total time: 100.941s
fastboot --skip-secondary -w update D:\HouseOfGoogle\IMAGES\shamu\FACTORY\image-shamu-ngi55d.zip complete...
fastboot reboot
Rebooting                                          
Finished. Total time: 0.000s
fastboot reboot complete...
Flash complete.  Thank you for using the House of Google!

[johnlgalt]

 

Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')

 

Hmmm.  Let's see if this is significant.  I suspect it is not, but I've never actually seen anything like that before.

[johnlgalt]

It wasn't - I'm at the setup screen.

[SamuriHL]

Hmmm.  Let's see if this is significant.  I suspect it is not, but I've never actually seen anything like that before.

 

No it's fine.  That's using the -w command that google inherently uses in their stupid bat file to erase data.  So that's normal.  You like that option? 

[SamuriHL]

I'm neck deep in code right now trying to figure out how to refactor the download code cause I need to use it to grab some platform tools which is coming in the next update.  I also did something I KNOW you'll appreciate cause it was driving me nuts.  Now you'll be able to maximize the stupid thing and have the status window scale.  You're welcome.    Once I get the platform tools code done I'll release a final "pre-beta candidate" to test again.  Then the real fun begins as I prep this thing for a beta release.

[johnlgalt]

Oh, yeah, that was driving me mad, bro.  Seriously.

 

OK, so, as it works now, does the Factory image flash code take the phone from normal boot and reboot to bootloader automatically now?

 

I'm still manually putting it in the BL since that is what I did with ver 0.0.....

[johnlgalt]

HoG OTA Flash to Oct 2017 log:

D:\HouseOfGoogle\IMAGES\shamu\shamu-ota-n6f27m-df27bd83.zip
SHA256 VERIFIED!
Download complete...
Rebooting to recovery...
adb reboot recovery
error: no devices/emulators found
adb reboot recovery complete...
OTA Flash cancelled.
Reboot to recovery cancelled.
Rebooting to recovery...
adb reboot recovery
error: no devices/emulators found
adb reboot recovery complete...
Sideload in progress.
adb sideload D:\HouseOfGoogle\IMAGES\shamu\shamu-ota-n6f27m-df27bd83.zip
Total xfer: 2.00x                                                                     
adb sideload D:\HouseOfGoogle\IMAGES\shamu\shamu-ota-n6f27m-df27bd83.zip complete...

[johnlgalt]

Something went wrong somewhere.  It's starting boot to the Google logo and nothing.  I think it was actually from the first flash, as it did the same thing when it attempted to boot to recovery, which is why it shows that error: no devices/emulators found.

 

Gonna start again with the whole process, see where I went wrong at.

[SamuriHL]

Oh, yeah, that was driving me mad, bro.  Seriously.

 

OK, so, as it works now, does the Factory image flash code take the phone from normal boot and reboot to bootloader automatically now?

 

I'm still manually putting it in the BL since that is what I did with ver 0.0.....

 

Not yet.  It's on the list.  However, it'll be....better than that when I get to that part of the code.  Not sure it'll make it for a beta or not.  If I don't get to the code I have in mind, I'll prompt and ask if you need to reboot the thing or not.  It's going to be smarter than the average bear when I get done.

[johnlgalt]

Lol - this is interesting.

 

On installing Bliss again, after wiping, formatting data and wiping again, I have a bunch of E:recv error on uevent error messages in TWRP.

 

Sigh.  Time to figure out what my Shamu is trying (or not trying) to do.

 

May be a while before I get a full test log with working results, depending upon what happens here.