26 replies to this topic

[andynolan]

I believe he means the

Please Login or Register to see this Hidden Content

the gpt.bin is the partition table.  I suspect it sets the partitions for everything else that gets flashed.  If someone else can give a good explanation for what it is, what it does and why it can't be downfgraded I'd love to hear it.

 

I've also read elsewhere that some people have gotten around the error by flashing just the gpt.bin in fastboot. Don't see why that would work though.

 

If gpt.bin is a partition table and it doesn't match up with all of the files 100% then an error would be generated, correct?  Is this why you are saying it is unlikely that swapping out this file would work?

[BladeRunner]

If gpt.bin is a partition table and it doesn't match up with all of the files 100% then an error would be generated, correct?  Is this why you are saying it is unlikely that swapping out this file would work?

Well that is the thing with the gpt.bin, you can't "swap it out" once it gets upgraded you can't downgrade it on a locked bootloader (and maybe not even on an unlocked one either)  What I think has happened is that the update they pushed to you upgraded the gpt.bin, then found something it didn't like and failed to install the rest of the update.  I'm not sure what is happening when you try to RSD the latest firmware but I suspect that the firmware expects to see something other than the gpt.bin you have and fails right there.  I really think you should try manually flashing all the files EXCEPT the gpt.bin for the latest update (you can try an earlier firmware if you feel adventurous)  also skip the "fastboot erase userdata" If you're not comfortable using fastboot you modify the RSD xml and flash that way.. OR try House of Moto.

[SamuriHL]

Skip the tz partition too.  IOW, the universal option in my tools.  However, I will say that the scenario you outline is impossible.  Assertions are done before the phone is ever changed....not after.  So the GPT partition would not have been updated unless all the assertions passed.

[KFTheTruth]

Interestingly enough I received a push as well. I lost root access and and am unable to get it back. Device Status is still 3. From my understanding once the fuse goes there was no killswitch or failsafe built in? In addition I was already on the KDA 20-2-15.1 so I'm not sure what prompted all this.

If I RSD my Sim becomes carrier locked and factory reset ends up on the red eye. I'm using HOM with Sam's scripts, should I revert back to motochopper?

[BladeRunner]

Interestingly enough I received a push as well. I lost root access and and am unable to get it back. Device Status is still 3. From my understanding once the fuse goes there was no killswitch or failsafe built in? In addition I was already on the KDA 20-2-15.1 so I'm not sure what prompted all this.

If I RSD my Sim becomes carrier locked and factory reset ends up on the red eye. I'm using HOM with Sam's scripts, should I revert back to motochopper?

How are you trying to get root access? If you are unlocked you should just be able to flash TWRP and get root that way or flash the latest supersu zip

[livinginkaos]

Not exactly sure how you are trying to root. If you are unlocked, you just flash the SuperSU.zip file in custom recovery. If you are not unlocked and/or are trying to use an exploit for root, you are out of luck.

sent from my N6

[soundman99]

My wife's XT907 did this on New Years Day.  I've tried clearing the cache, factory reset, etc, still stuck on the red eye.  For a while, the sound would cut out half-way through the start-up process, now it lasts a little longer, but still cuts out somewhere along the way.  I've tried pushing updates/recoveries to it through RDS Lite and Fastboot: no luck.  I've got 4 more months left on the contract, so no warrentees.  I'm wondering if I shouldn't just try to activate my old Bionic and get something new when my renewal time comes.  Thoughts, opinions or statements welcome...