471 replies to this topic

[SamuriHL]

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.

 

Odd.  The flash was successful of the OTA so it wasn't part of the process that failed.  OTA's are super safe to sideload cause the device controls the whole process including error handling.  It'd fail if something went wrong.

[SamuriHL]

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.

 

Oh lovely.    No worries.  I'm beating on the download and platform tool handlers right now.  That code is going to need major refactoring once I have time.  Right now I'm sort of brute forcing it to work cause there's a lot of difference between downloading platform tools vs downloading an OTA or factory image.  So for now I'm "hardcoding" how they're managed but that'll change eventually.  Short version of what I'm saying is there won't be a new test version til I pick up the pieces off the floor.  Could be a bit.

[johnlgalt]

Lol - no  worries at all.

[SamuriHL]

Platform tools is proving to be a pain in the ass.  It's not working the way I'd have hoped.

[johnlgalt]

That's odd, since there is a dedicated link to it and all you have to do is extract.

[johnlgalt]

OK, new Bliss install, followed by full charge, followed by HoG Factory image NGI55D (Sept 2017) install.  About to reboot.  Log follows:

D:\platform-tools\IMAGES\shamu\shamu-ngi55d-factory-1132151d.zip
SHA256 VERIFIED!
Download complete...
Extract: D:\platform-tools\IMAGES\shamu\shamu-ngi55d-factory-1132151d.zip
To: D:\platform-tools\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:\platform-tools\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.689s]
Finished. Total time: 0.928s
fastboot flash bootloader D:\platform-tools\IMAGES\shamu\FACTORY\bootloader-shamu-moto-apq8084-72.04.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 flash radio D:\platform-tools\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.239s]
Writing 'radio'                                    (bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [  1.625s]
Finished. Total time: 5.955s
fastboot flash radio D:\platform-tools\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:\platform-tools\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: 0a1f0c2a-3de6-11e9-966b-6b56cf8414ac
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: 0a4d2b14-3de6-11e9-80ca-cb0075bacd08
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.025s
(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.307s
(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.317s]
Writing 'boot'                                     OKAY [  0.154s]
Sending 'recovery' (13887 KB)                      OKAY [  0.503s]
Writing 'recovery'                                 OKAY [  0.248s]
Sending sparse 'system' 1/4 (522524 KB)            OKAY [ 19.695s]
Writing sparse 'system' 1/4                        OKAY [  7.522s]
Sending sparse 'system' 2/4 (517601 KB)            OKAY [ 19.497s]
Writing sparse 'system' 2/4                        OKAY [  7.031s]
Sending sparse 'system' 3/4 (508949 KB)            OKAY [ 19.211s]
Writing sparse 'system' 3/4                        OKAY [  6.963s]
Sending sparse 'system' 4/4 (32756 KB)             OKAY [  1.249s]
Writing sparse 'system' 4/4                        OKAY [  0.399s]
Erasing 'userdata'                                 OKAY [  2.227s]
Sending 'userdata' (4396 KB)                       OKAY [  0.153s]
Writing 'userdata'                                 OKAY [  1.779s]
Erasing 'cache'                                    OKAY [  0.047s]
Sending 'cache' (120 KB)                           OKAY [  0.000s]
Writing 'cache'                                    OKAY [  0.038s]
Erasing 'metadata'                                 (bootloader) Permission denied
FAILED (remote: '')
Finished. Total time: 100.112s
fastboot --skip-secondary -w update D:\platform-tools\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]

HoG OTA Flash to N6F27M (Oct 2017) over previous.  Log:

D:\platform-tools\IMAGES\shamu\shamu-ota-n6f27m-df27bd83.zip
SHA256 VERIFIED!
Download complete...
Rebooting to recovery...
adb reboot recovery
adb reboot recovery complete...
Sideload in progress.
adb sideload D:\platform-tools\IMAGES\shamu\shamu-ota-n6f27m-df27bd83.zip
Total xfer: 2.00x                                                                      
adb sideload D:\platform-tools\IMAGES\shamu\shamu-ota-n6f27m-df27bd83.zip complete...

Image:

 

 IMG_20190303_141128_resized.jpg   38.46KB   4 downloads

[johnlgalt]

And the Shamu is sitting at the Google logo again.

 

WT Bloody Fing He||!

[johnlgalt]

So, I loaded up TWRP, performed the default wipe, and then did the format /data and rebooted and it started coming up.

 

Something is not happy here.  And I have a feeling it is on my end not in the software.

 

Gonna make sure I am not expecting any phone calls, then will attempt this $#!+ on my Taimen

[johnlgalt]

I may have to test with Shamu further - maybe manually installing that Sept 2017 factory image, and then using HoG to flash the latest OTA and see if it still gives me the same issue or not.

 

Right now, I cannot be sure if it is something in the BlissROM that is not getting wiped correctly (which makes 0 sense as when I flash the Factory image with HoG it comes up to the initial setup screen, and I set up the device sans Google account and sans any PIN / pw.  So, if I manually flash the factory image and then use HoG to flash the OTA, and the issue still occurs, then I know it is with the OTA part.  If it doesn't, then I'll use HoG to flash the Sept 2017 factory image and manually flash the OTA and see if it happens.

 

If it doesn't happen either time, then it *has* to be with the ROM and the initial flash after ROM install, perhaps something in the wiping procedure in TWRP.  But that makes little to no sense.

 

Meanwhile, I'm making a TiBu of my current system on the Taimen, and then will make a TWRP backup of that so I can start playing around on it as well - shouldn't be getting any phone calls any time soon.  And They can leave me a msg if someone does call lol.

 

Then I can try doing some of the same things on the Taimen and see if it also breaks or not.

[SamuriHL]

That's odd, since there is a dedicated link to it and all you have to do is extract.

 

hahahahaha, that's goddamn hilarious.  Anyway I'm well beyond that now.  This next iteration is going to be insane.  I'll probably throw a new version up here for you shortly.

[SamuriHL]

I may have to test with Shamu further - maybe manually installing that Sept 2017 factory image, and then using HoG to flash the latest OTA and see if it still gives me the same issue or not.

 

Right now, I cannot be sure if it is something in the BlissROM that is not getting wiped correctly (which makes 0 sense as when I flash the Factory image with HoG it comes up to the initial setup screen, and I set up the device sans Google account and sans any PIN / pw.  So, if I manually flash the factory image and then use HoG to flash the OTA, and the issue still occurs, then I know it is with the OTA part.  If it doesn't, then I'll use HoG to flash the Sept 2017 factory image and manually flash the OTA and see if it happens.

 

If it doesn't happen either time, then it *has* to be with the ROM and the initial flash after ROM install, perhaps something in the wiping procedure in TWRP.  But that makes little to no sense.

 

Meanwhile, I'm making a TiBu of my current system on the Taimen, and then will make a TWRP backup of that so I can start playing around on it as well - shouldn't be getting any phone calls any time soon.  And They can leave me a msg if someone does call lol.

 

Then I can try doing some of the same things on the Taimen and see if it also breaks or not.

 

Just give me a few minutes before you go crack flashing again.  I've made a HELL OF A lot of internal changes to this thing and I've no idea if it's all going to work.  The flashing should be fine.  But all the stuff around it is going to be....interesting.

[johnlgalt]

Making backups on the Taimen, and the Shamu is almost ready to have Bliss installed again.

 

Meanwhile making backups of my two laptops with WinX on them - one is going back to Sabayon Linux (Gentoo-based) an the other gets to be a test bed for Bliss-X86 - Android on a laptop.

 

You've got plenty of time - you'll probably be ready before I am lol.

[johnlgalt]

Oh, and what was the laughing for?  I'm still lost on why the coding for platform tools wasn't working....

[SamuriHL]

Oh, and what was the laughing for?  I'm still lost on why the coding for platform tools wasn't working....

 

Because things that SEEM simple most DEFINITELY aren't.  Think about the chain of events that has to happen when you start this thing up.  First I have to load data from 2 web pages.  Then I have to check and see if platform tools do in fact exist where I want them.  If they don't, I need to download those before I can let the user do stuff.  And I don't want it downloaded to a file that I have to read in and extract....I wanted it downloaded to memory and only extracting the files I need.  Which is very different from how an OTA or factory image gets downloaded. So i had to write a custom download piece of code just to handle platform tools.

 

So yea, I find it hilarious that "you just download it from the known link."  LMAO  UH HUH

 

Anyway, new version incoming shortly.  I've lost track of the amount of changes in this one so the release notes aren't going to be super complete.  When you see what I've done, you'll understand why this was so complicated.  I laid the groundwork for that internal functionality I told you about.  It's a start.

[SamuriHL]

New version is up.  This will be the last alpha version unless bugs are found.  It's completely untested in terms of flashing but that stuff SHOULDN'T have changed.  Given all the other changes around it, however, it should be tested.  A word of warning...the UI may seem to "hang" on startup.  There's not a WHOLE lot I can do about it as it's doing a whole bunch of stuff under the covers before the thing is fully drawn.  Like....more stuff than before as you'll see.  My advice is to make sure your device is plugged in when you load it.  I'm going to attempt to work on getting it ready for a public beta release but I genuinely don't know how much work that'll entail.  Happy testing. 

[johnlgalt]

Because things that SEEM simple most DEFINITELY aren't.  Think about the chain of events that has to happen when you start this thing up.  First I have to load data from 2 web pages.  Then I have to check and see if platform tools do in fact exist where I want them.  If they don't, I need to download those before I can let the user do stuff.  And I don't want it downloaded to a file that I have to read in and extract....I wanted it downloaded to memory and only extracting the files I need.  Which is very different from how an OTA or factory image gets downloaded. So i had to write a custom download piece of code just to handle platform tools.

 

So yea, I find it hilarious that "you just download it from the known link."  LMAO  UH HUH

 

Anyway, new version incoming shortly.  I've lost track of the amount of changes in this one so the release notes aren't going to be super complete.  When you see what I've done, you'll understand why this was so complicated.  I laid the groundwork for that internal

functionality I told you about.  It's a start.

 

See, you're just going to make it complicated, aren't you?  lmfao!

 

I do like the functionality that you're going for with this, though.  (If it were me, I'd probably wuss out and just DL and extract the whole thing and be done with it, simply because of the simplicity of doing it that way.  *shrug*)

 

New version is up.  This will be the last alpha version unless bugs are found.  It's completely untested in terms of flashing but that stuff SHOULDN'T have changed.  Given all the other changes around it, however, it should be tested.  A word of warning...the UI may seem to "hang" on startup.  There's not a WHOLE lot I can do about it as it's doing a whole bunch of stuff under the covers before the thing is fully drawn.  Like....more stuff than before as you'll see.  My advice is to make sure your device is plugged in when you load it.  I'm going to attempt to work on getting it ready for a public beta release but I genuinely don't know how much work that'll entail.  Happy testing. 

 

Right on - still copying files from the Taimen to the local machine so I can have a full wipe of the Taimen, with Bliss installed, and see how it goes.  I'll be testing both devices, using the same testing methods as above.

[johnlgalt]

Grrr. 

 

 

-A little UI cleanup to lock the comboboxes to dropdown lists instead of text entry

 

That was how I was doing it so quickly, I'd type 'sh' them hit the down arrow key for Shamu, hit tab, type 'F' or 'O', hit down arrow key, hit tab, type '7', hit the [END] key, then hit tab and down arrow to the desired file.

 

I *really* hate using a mouse with dropdowns....

[SamuriHL]

Grrr. 

 

 

That was how I was doing it so quickly, I'd type 'sh' them hit the down arrow key for Shamu, hit tab, type 'F' or 'O', hit down arrow key, hit tab, type '7', hit the [END] key, then hit tab and down arrow to the desired file.

 

I *really* hate using a mouse with dropdowns....

 

Relax....I know what you REALLY want.  TRY IT before complaining.  Do what I said...start it with the whale connected. 

[SamuriHL]

P.S. It's even more intuitive in the beta release I'm working on.  LMAO   I read minds...or attempt to.  It won't get it exactly right, but, it'll put you in the ballpark.