488 replies to this topic

[cmh714]

ALL --- hold off d/l'ing 1.3 as Sam already found some issues.....if you didnt see the post in the other thread.

[SamuriHL]

1.4 released

 

-Fixed bug caused by idiot screwing with the wrong code

-Bothered to change the linux/mac code this time (good lord)

-Added a new generated from factory image message at the top of the flashme script so you can see what factory image it was created from

[SamuriHL]

ALL --- hold off d/l'ing 1.3 as Sam already found some issues.....if you didnt see the post in the other thread.

 

They weren't given a choice.  I removed the link.  LOL

[johnlgalt]

Welp.  A lot happened in the last couple of months.

Finally got around to having a birthday, being hired full time (well, that really happened in Dec.), oh, and got a replacement device for the one I bought - they sent me a MB64GBNAGPE.  Decipher that.

 

Sam - VZW still can't figure out how to activcate the f%$king thing.

 

I have a lot of reading and unfortunately not a lot of time to do it in - three f%$knig 5.1 updates?  Bricking when trying to flash down certain components (gee, *that* sounds familiar...)?  ***VZW Telling me that they cannot activate a Google Play Edition device because it is not in their system, and the Engineering team that the very helpful CSR sent the IMEI to to have it added tells her within 10 minutes that it cannot be done because my IMEI has to start with a 99 and not a 35?  (Moron, that was my BIONIC - My other line has an iPhone 6 that also starts with 35, so you're kinda being a stupid jackass....)

 

Sigh.  Now to see how well unlocknig this puppy performs on a Win 10 Pro x64 machine....

 

I need root.  And trying to copy mt TiBu repository so I can reload all the settings and data for my apps is proving... problematic....at best.....

 

And it is Friday.  And the Macon, GA Cherry Blossom Street Party is getting geared up..........

FML.

That is all.


Oh - and never, ever ever EVER develop this condition - it ***SUCKS***.  

Costochondritis

Edited by johnlgalt, 27 March 2015 - 02:22 PM.

[SamuriHL]

Wow, that's uh, yea, not good.  Jeeze man.  If there's anything you need me to help with, let me know.  

[johnlgalt]

I'm not doing badly, all things considered.  A world of difference from 6 months ago when I didn't have the job and was limping along - But so little time!

 

<OT>Company I work for went from being a very small regional to a full on national company, jumping from around 200 or so employees to 8K+ - and absolutely no network infrastructure in place, forget regulatory compliance, forget anything other than going to dell.com for a new PC when someone was hired and needed one....

 

We are *so* building this all up from scratch - I get to break things *on purpose* so they will have less of a penchant need to do so (shaddap Sam - yes, I know, very well, what you've been steadily going through with the House of Series....that is another story - and I did warn you, what, 3, 4 years ago?)....

 

Oh, and that condition is more of an injury / aggravation / inflammation, which means it *can* be healed.  It just takes time.  And pollen and hay fever sure as hell don't help.

 

</OT>

 

 

I'm going to *not* be obtuse and guess that I should say Screw everything and directly flash TWRP 2.8.6.0 and the latest "i" stock and get myself rooted, instead of going through hell and back again over the weekend, eh?

[SamuriHL]

I don't bother flashing TWRP myself, but, it's an option.  I simply boot it in memory and keep stock recovery.  Choice is yours on that one.  Yes, the I build seems to be the latest trend these days.  LMAO.  I'm running it.  Do yourself a favor...after every build you flash, ALWAYS check to make sure the oem option in developer options is enabled....EVEN IF YOU'RE UNLOCKED.  Failure to do so will totally screw you if you ever brick and need to flash a factory image.  And it HAS been reset even on unlocked devices.  Yey, Google.  

[johnlgalt]

That is friggin stupid....  Noted.

Argggh.  Getting hot up in here.  I need a beer.

[johnlgalt]

Crap.  Gotta update my links with the latest RSD and Moto drivers...I am *so* far behind....

[Aldroid33]

Hi Sam. Just visiting the House. Never know what may happen. As my N6 is on VZW, is there any practical reason to upgrade from E to I at this time? My understanding is that E has the latest Modem/radio for VZW. Is that correct?

[SamuriHL]

Hi Sam. Just visiting the House. Never know what may happen. As my N6 is on VZW, is there any practical reason to upgrade from E to I at this time? My understanding is that E has the latest Modem/radio for VZW. Is that correct?

 

Build E was VZW specific, yes.  Build I appears to have some minor fixes for all NX6's.  I don't know whether it includes VZW's radio enhancements or not.  I'm running I but I have a Google Edition.

[johnlgalt]

Sounds like what I need to put on mine then.  Got scared for a moment, forgot about the enforced encryption thing when unlocking....

Looking around the interwebs, seems there is a way to buck that - if I didn't let it encrypt...

 

*sigh*

 

OK, unlocked, then ran HoN.  Now booting.  OK, it's up

[SamuriHL]

Woo hoo.  The HoN in its new home boys and girls!

[kellym]

Woo hoo.  The HoN in its new home boys and girls!

So nice not to play hide and seek, lol!  Soocold is good!  Sam - copying my version of fastboot resolved all issues instantly.  

[SamuriHL]

So nice not to play hide and seek, lol!  Soocold is good!  Sam - copying my version of fastboot resolved all issues instantly.  

 

Kaos did it.    And yea, I figured it would.  Still don't know why.

[johnlgalt]

I had to copy the fastboot (in fact the Mod Tools .ZIP from XDA) in order to get my new (replacement) OEM unlocked as well.

 

Don't know why, but even with having it the tools directory from the Android SDK in the system path, it would not find the device until I 'installed' the Mod Tools.

 

Now to fool VZW once and for all to get my phone working  - as a .phone​.

[SamuriHL]

I suspect I know what that issue is with fastboot.  I think they changed something and it now requires both adb dll's to be in the tools directory.  I'll deal with it later.  I just got home after being gone all week.

[johnlgalt]

Nice.  Let's not make the tools as good as  they can be but focus instead on adding more wanker cyclic redundancy checks so that the tools don't seem any faster than they were before because you're spending 3 minutes just for it to triple verify with it self that it is in fact itself.

[SamuriHL]

LOL.  My tools do almost no error checking.  They either work or they don't.  

[johnthehillbilly]

Nice. Let's not make the tools as good as they can be but focus instead on adding more wanker cyclic redundancy checks so that the tools don't seem any faster than they were before because you're spending 3 minutes just for it to triple verify with it self that it is in fact itself.

You must think this is Microsoft ... Hahaha