471 replies to this topic

[SamuriHL]

I was looking at fastboot -h and saw the different functions there.  I initially got curious when I saw some of the functions you were using.  I saw that erase function and was going to use it myself for my Shamu if I couldn't get the normal flash over Bliss ROM to work, because no matter what anyone says, TWRP is buggy AF.  I never remember having issues before with previous devices, but it has screwed things up more than once with both devices here.

 

Hell, I might still write up my own little batch file for use with wiping my devices anyway.

 

But, yeah, it lets you do a lot more than just fastboot boot and fastboot reboot.  lol.

 

You've only seen the beginning of what I have planned.  The refactoring was necessary to support what I intend to do next to make this thing a LOT more robust and useful.    The device auto selection is just a taste of what's to come.  And yes, I also modified it to auto select the latest android version and latest image, as well.  Remember...I said mind reading. 

[SamuriHL]

Factory (Sep 2017) --> OTA (Oct 2017)

 

log:

Platform tools found.
Found Device: Nexus_6 (shamu)
D:\HouseOfGoogle\IMAGES\shamu\shamu-ota-n6f27m-df27bd83.zip
SHA256 VERIFIED!
Download complete...
Rebooting to recovery...
D:\HouseOfGoogle\TOOLS\adb.exe reboot recovery
Sideload in progress.
D:\HouseOfGoogle\TOOLS\adb.exe sideload D:\HouseOfGoogle\IMAGES\shamu\shamu-ota-n6f27m-df27bd83.zip
Total xfer: 2.00x                                                                     

Suppose I should press reboot now, huh?

 

Yup.  I can't reboot it from recovery.

[johnlgalt]

Want to know the funniest thing?  The single biggest obstacle I've had with the Shamu is its size + the case I have on it (Spigen 2 piece).  Every time I am attaching it to the USB, one of my fingers slip and hit the power button while it is already in fastboot mode.  It's just that wide, and that case makes the buttons virtually indistinguishable from the rest of the case - and the phone proceeds to reboot.

 

Sigh.

 

Anyway, confirmed on device that the OTA took as well.  Build N6F27M.

 

I'd call this an all around success.

[johnlgalt]

You've only seen the beginning of what I have planned.  The refactoring was necessary to support what I intend to do next to make this thing a LOT more robust and useful.    The device auto selection is just a taste of what's to come.  And yes, I also modified it to auto select the latest android version and latest image, as well.  Remember...I said mind reading. 

 

Noticed that as well.  One thing I didn't try was to try to type in the name Shamu the first time that it could not find the device because I was too slow and authorizing.  Let me see if that works....

[SamuriHL]

Kuel.  So the only thing left to do for beta release is to package this thing up properly.  That requires quite a bit of additional work on stuff I've never worked with before.  But I should have an "official" beta by tomorrow.  Using the version you're now testing.

[SamuriHL]

Noticed that as well.  One thing I didn't try was to try to type in the name Shamu the first time that it could not find the device because I was too slow and authorizing.  Let me see if that works....

 

I doubt it.  But you should be able to arrow down on that combo box and select it with the keyboard.  

[johnlgalt]

Lol whoops.  The log field is a standard issue text box.

 

Attempting to flash Factory VZW stock NGI77B on top with a wipe via HoG.  It was in normal boot up mode, I had authorized Android Debug.

 

When asked if I want to let it boot back to bl, I said yes - and it rebooted the phone - back to Android again.

 

HoG log (For Ss & Gs about me typing in the text box):

Platform tools found.
ssasdasdadad
sdfasdf
asdfasd
fasf
asdf
asdfas
dfas
fasdf
asdf
asdfa
sdfas
dfas
dfas
dfas
dfa
sdfa
sd
f
asdf
awsfa
wtg q
eaha
gh s
gj 
fg
ja
dgch a
d
ghv a
g
jha
dfh a
dg
hv 
ad
fh
a dv
ghvad
h
adfha 
df
gh v
ad
h
a
dh
adfgh 
vaeh

a
h
ad
h
a d
h
va 
dgh
dgha
dh v
adgbyh 
agjh
adh
adh
dh
avdgh 
d
z
gh
dsgh 
vsgh
b sf

s
fghs
rgh
bvsf j
sg
hsfd
gh
bd s

gh 
zd
vhb
sd
hs
yhb s
fns
fgdh
sbg
bh sD:\HouseOfGoogle\IMAGES\shamu\shamu-ngi77b-factory-5cd75e2a.zip
SHA256 VERIFIED!
Download complete...
D:\HouseOfGoogle\TOOLS\adb.exe reboot bootloader
Extract: D:\HouseOfGoogle\IMAGES\shamu\shamu-ngi77b-factory-5cd75e2a.zip
To: D:\HouseOfGoogle\IMAGES\shamu\FACTORY\
extract: radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
extract: image-shamu-ngi77b.zip
extract: bootloader-shamu-moto-apq8084-72.04.img
Extract complete.

[johnlgalt]

I doubt it.  But you should be able to arrow down on that combo box and select it with the keyboard.  

 

Blah.  Arrow keys.  Blah.

[johnlgalt]

Must have been something funky going on - this time it went to BL.

 

Flashing.

[johnlgalt]

Shamu:  N6F27M --> NGI77B Factory with wipe

 

HoG log:

Platform tools found.
D:\HouseOfGoogle\TOOLS\adb.exe reboot bootloader
Extract: D:\HouseOfGoogle\IMAGES\shamu\shamu-ngi77b-factory-5cd75e2a.zip
To: D:\HouseOfGoogle\IMAGES\shamu\FACTORY\
extract: radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
extract: image-shamu-ngi77b.zip
extract: bootloader-shamu-moto-apq8084-72.04.img
Extract complete.
Starting flash...
D:\HouseOfGoogle\TOOLS\fastboot.exe 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.156s]
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.703s]
Finished. Total time: 0.953s
D:\HouseOfGoogle\TOOLS\fastboot.exe reboot-bootloader
rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s
Sleep 5 seconds for reboot...
D:\HouseOfGoogle\TOOLS\fastboot.exe flash radio D:\HouseOfGoogle\IMAGES\shamu\FACTORY\radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
(bootloader) has-slot:radio: not found
Sending 'radio' (115510 KB)                        OKAY [  4.244s]
Writing 'radio'                                    (bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [  1.594s]
Finished. Total time: 5.933s
D:\HouseOfGoogle\TOOLS\fastboot.exe reboot-bootloader
rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s
Sleep 5 seconds for reboot...
D:\HouseOfGoogle\TOOLS\fastboot.exe erase userdata
(bootloader) has-slot:userdata: not found
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata'                                 OKAY [  2.900s]
Finished. Total time: 2.990s
D:\HouseOfGoogle\TOOLS\fastboot.exe --skip-secondary update D:\HouseOfGoogle\IMAGES\shamu\FACTORY\image-shamu-ngi77b.zip
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------       
Bootloader Version...: moto-apq8084-72.04
Baseband Version.....: D4.01-9625-05.51+FSG-9625-02.118
Serial Number........: ZY222X6Z3C
--------------------------------------------       
Checking product                                   OKAY [  0.000s]
Checking version-bootloader                        OKAY [  0.000s]
Checking version-baseband                          OKAY [  0.000s]
extracting boot.img (8 MB) to disk... took 0.031s
(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.031s
(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.219s
(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
Sending 'boot' (8483 KB)                           OKAY [  0.391s]
Writing 'boot'                                     OKAY [  0.156s]
Sending 'recovery' (13873 KB)                      OKAY [  0.500s]
Writing 'recovery'                                 OKAY [  0.203s]
Sending sparse 'system' 1/4 (522524 KB)            OKAY [ 19.719s]
Writing sparse 'system' 1/4                        OKAY [  7.437s]
Sending sparse 'system' 2/4 (517601 KB)            OKAY [ 19.539s]
Writing sparse 'system' 2/4                        OKAY [  6.859s]
Sending sparse 'system' 3/4 (508949 KB)            OKAY [ 19.459s]
Writing sparse 'system' 3/4                        OKAY [  7.062s]
Sending sparse 'system' 4/4 (32756 KB)             OKAY [  1.266s]
Writing sparse 'system' 4/4                        OKAY [  0.406s]
Rebooting                                          
Finished. Total time: 95.389s
D:\HouseOfGoogle\TOOLS\fastboot.exe reboot

I'm at the initial setup screen.

[SamuriHL]

I was going to say, the reboot to bootloader I tested so I know that works.  And yea, ok, I can make the text box not do stupid s***.  I actually am about half way through what I need to package this thing up for users.  So we'll definitely be ready for beta tomorrow.

[SamuriHL]

Beta is incoming.  I'm going to warn you, this MIGHT piss you off royally because I've changed something.  Because I've created an actual installer for this thing, I can't write to the same directory that I exist in (because default will be Program Files\House of Google).  Yes, it can be changed, BUT, I have to assume 99% of my users won't change the default.  I know you like keeping the images and tools all nice and together in your D:\HouseOfGoogle directory, but, for now for this beta, that's not going to happen.  It's going to behave like a good little windows program and put its data in %appdata%\roaming\HouseOfGoogle which I suspect will annoy you.  At some point in the future I may revisit this and allow an alternative location for images.  Right now, given that it's beta, I want it consistent.  Trust me, I get it....it's annoying as all hell but this is what apps are SUPPOSED to do.

[johnlgalt]

Actually, you'd be surprised how much I've come to appreciate the \Users tree in general and the storage of files / settings / cache there.

 

And, hell, I can still point it to install to D:\ (if you don't make it mandatory to install to %ProgramFiles%) anyway.

 

Having the files in \Users is not a bad thing, IMO.

[SamuriHL]

You can install it to D yes.  It just won't put your images and tools there.  Nor will it find them there.  I will eventually add a way to select older images and nuke them from the UI but we are beta now.

[SamuriHL]

The beta is now live.  I hope a few of you brave people will be tempted to try this out tomorrow when the new images are released.  It should be fairly painless.  Just make sure you read the directions....twice...and proceed with some caution.  Especially you unlocked factory image people.  I'm definitely curious to see what people's impressions are and if they encounter any show stopping bugs.  Lots and lots of things to still do, but, we're on our way to a 1.0.0.0 release in the next few weeks.

 

HUGE thanks to johnlgalt for all the amazing testing.  This would have have gotten as far as it has without that support.

[SamuriHL]

Small change and update to 0.0.9.2

 

I changed the order in which things are selected which has some nice impact on the whole thing.  So first time run:

 

o) Check for platform tools

o) Download tools when they aren't found

o) Extract tools

o) Check for connected device

o) Populate Image Type drop down with FACTORY or OTA

 

So, first time run the UI will hang a little bit while it grabs the tools and extracts them.  After that, the UI will come up just fine.  When you select the image type:

 

o) Load the data for the image type from the corresponding google page

o) Load the devices combo box

o) Check the devices combo box for the device we found....if found, select it

o) If device is selected, select the highest version

o) If version is selected, select the latest image

 

Basically this changes the flow so in theory you may only need to select the image type, download, and magic and it'll flash your image.

 

P.S.  john....stop typing in my fields, thanks. 

[SamuriHL]

Ok, so, that didn't go well.  Let's try 0.0.9.3 instead.    Fixed a bug in device selection caused by the rewrite.  Should be all good now.

[SamuriHL]

Man....this is not my day.  The auto device selection code is still broken.  Looking into it now.  

[SamuriHL]

Stupid bug eliminated.  0.0.9.4

 

Let's go, Google, I want some images posted.  LOL

[LDubs]

Will this work on essential phone ? Or just Google devices

Sent from my PH-1 using Tapatalk