488 replies to this topic

[SamuriHL]

Yes those are normal. They won't impact the flashing of the partitions in any way.

Sent from my Pixel XL using Tapatalk

[Sabres032]

Yes those are normal. They won't impact the flashing of the partitions in any way.

Sent from my Pixel XL using Tapatalk

House of Nexus flashed it no issues. I've never seen those "errors" before and was initially concerned. Still not seeing much of an improvement in signal quality but at least I'm not dropping calls like before.

[SamuriHL]

Those errors would show up with a regular flash using the built in script as well. They're not really errors. They're like checks but they don't seem to include them in the images. No idea why. Not too worry though the flash is fine.

Sent from my Pixel XL using Tapatalk

[johnlgalt]

I'll be using HoN to clean flash the latest N6 build so I can get Assistant on my phone without having it rooted and such.  Time to have some fun

[johnlgalt]

Ran into an odd issue.  If I double click on the batch file it would not run.  Only by opening a cmd prompt and navigating to HoN/Nexus folder and running the batch file from there would it work.

This has to be an issue on my end, but this is a clean install from last week.  I'm mind boggled at what is causing this.  It may be xplorer2 that is causing the issue, but it never has in the past.

Odd, odd, odd.

I'll try it from a normal explorer window next and see if it does the same thing or works, and that will help me narrow it down.

 

[SamuriHL]

Do I need to go back a few pages and find where it "never did in the past?"  LMAO  You've had that issue before.

[johnlgalt]

Old age. Will look at it tomorrow.

From Nexus with Nougat

[johnlgalt]

OK, found the stuff where it happened last year.  Same supposition on my part, that it is the file manager Xplorer² causing the issue.

 

I might try editing the batch file so nothing but the bootloader is flashed (since it is the same nothing should be affected by it) and see if it is the file manager or something else.

 

Will post back.

[SamuriHL]

Yea, I remembered your theory last year and I agreed that it was likely.  I REALLY wish MS would implement USB devices in bash and make bash a standard on Windows for cmd line.  I'd switch us over to bash in a heart beat.  I really do not like the MS batch files anymore.  It's beyond outdated with far too many limitations.

[johnlgalt]

OK, verified.  It is only when I use Xplorer² that the issue occurs.  If I use a regular Windows explorer window and run the test .BAT file it pushed the bootloader files to my phone without a problem.

 

I'll start up a topic with at the Xplorer² forums and see where it gets me.

[johnlgalt]

Yea, I remembered your theory last year and I agreed that it was likely.  I REALLY wish MS would implement USB devices in bash and make bash a standard on Windows for cmd line.  I'd switch us over to bash in a heart beat.  I really do not like the MS batch files anymore.  It's beyond outdated with far too many limitations.

 

So, no love for Powershell? 

 

j/k - Out of curiosity, though, is the lack of USB support for BASH 4 Win mean that the adb / fastboot command simply do not work?

[johnlgalt]

Lo, and behold!  It is a simple setting in the file manager that was causing it - and someone just posted about it last week:

 

http://netez.com/bbs...hp?f=18&t=11403

 

@%^$%$%&$^&$^&$^&$!@%^&!$@%&@$^&%^#@&*@$^*!!!!!!!

[SamuriHL]

So, no love for Powershell? 

 

j/k - Out of curiosity, though, is the lack of USB support for BASH 4 Win mean that the adb / fastboot command simply do not work?

 

I've thought about powershell.  I don't know, maybe.  I'm not well versed in it and it'd be a pretty big rewrite.  We'll see.

 

But yes, the lack of USB support means that adb and fastboot aren't able to connect to the device.  I've requested way back when that they add USB device support and it seems they took my issue and combined it with someone else's that requested USB storage support.  I suspect they'll add USB storage and not USB device which is useless for us.  I keep trying every once in a while.  I also updated my BASH to suse.  

[SamuriHL]

Lo, and behold!  It is a simple setting in the file manager that was causing it - and someone just posted about it last week:

 

http://netez.com/bbs...hp?f=18&t=11403

 

@%^$%$%&$^&$^&$^&$!@%^&!$@%&@$^&%^#@&*@$^*!!!!!!!

 

LMAO!  Yea, isn't that always the way.  

[johnlgalt]

Indeed!  Pissed me off to no end.  Now, I have to worry about hte folder being locked in the file manager when other apps are trying ot use them.  Sheesh.

[SamuriHL]

Is there an extensive reason you use that particular file manager?

Sent from my Pixel XL using Tapatalk

[johnlgalt]

Multiple reasons.

 

• 2-pane file manager, with intelligent, robust copy / move functions from pane / location to pane / location
• Multiple tabbed interface on both panes
• Easy File date / time stamp manipulation of single / multiple files
• Built-in duplicate file finder
• Built in robust search, including searching inside documents
• Better explorer column handling
• Better attributes handling, including those not shown in Explorer but that still exist in Windows
• Ability to save folder properties for individual folders

 

And many, many more reasons.

[spainter]

Sam,

I don't know if you have already seen this over on XDA, but I thought about you and the others that like the Linux environment for working on android. I know you can make anything easier for those of us that has very little experience with other platforms. I thought this may be a good place for me to start with Linux as well.

https://forum.xda-de...issues-t3526755

[SamuriHL]

I haven't.  It's not that I like Linux for working on Android, as I do all my development in Windows, it's that bash scripting makes things a lot easier vs Windows cmd/bat files.  Because Android is built upon a Linux kernel, it's far easier for some things like getting the device detected without a whole bunch of driver BS.  We've toyed with the idea of creating a self contained Linux environment before so that a user could download a VM and either live boot it off a USB stick or stick it in a VM, but, the complexity for the end user isn't worth it.  This is why I was hoping against all hope that adb/fastboot would work in Windows 10 bash scripting as I would have moved everything to bash and given the users multiple options of getting there.  Unfortunately MS dashed the bash hope.  LOL

[spainter]

It kind of caught my eye. I downloaded it but haven't burned it to a flash drive yet. I really want to get into Linux a bit but just haven't wanted to dedicate a hard drive to it as of yet.  This may be the way to do it with out doing a permanent install and not having it run in a VM under windows.