The T-Mobile Fajita Nightmare (or, why you should NOT get the T-Mobile version of the 6T so far)

AntiDroid

@totalrando said in The T-Mobile Fajita Nightmare (or, why you should NOT get the T-Mobile version of the 6T so far):

If you have or know of Linux based instructions to roll back the 6T to Android 9 I beg of thee to give them to me. Because Windows and I usually don't get along

My instructions are for Linux. I have not had windows since XP. Although I do maintain some virtual machines with Windows.

TotalRando

@antidroid This is good, really good stuff. I will try this after work and let you know the results.

TotalRando

@antidroid I feel stupid now on rereading this, not realizing you had referred to a post here. I saw a blue link and didn't even think it was a new post, but the xda-developers post I've stared at for hundreds of times this week. Shame on me for not paying attention. This is good work, and I am really hopeful I might be able to make this work on my phone soon.

AntiDroid

@totalrando said in The T-Mobile Fajita Nightmare (or, why you should NOT get the T-Mobile version of the 6T so far):

EDIT: I should add, this is a really common problem with the T-Mobile edition, with apparently hundreds of desperatae 6T owners complaining that the T-Mobile fork of OxygenOS is so bad that people with virtually no flashing experience are desperately trying to get the stock ROM. It's an amazing phone. But that's exactly why I refuse to run Android on it and by hook or by crook I will flash this phone to my bidding. insert evil laughter

Please note that flashing the phone with the Global version of the OS will fix the T-mobile issue but currently flashing it with Ubuntu Touch for a daily driver is questionable. I have had to reflash my 6T a few times after instaling things that broke it (not sure which apps i installed that broke it). The symptoms of the bug are well known. The phone will be at full brightness and you can't adjust it and then the screen shuts off and you have to force a reset and in my case reinstall everything again as every time i rebooted it had the same issue. It is still usable but be careful as you may need to reflash and lose stuff.

wgarcia

This post is deleted!

wgarcia

This post is deleted!

TotalRando

@antidroid This assessment brought me to the pit of despair, along with the realization that I needed a different SlimPort than my Nexus 4. Luckily my wife came by and woke me with a good slap, so I got back to work and tried your method. I put the phone in bootloader, assembled the directories and got, well, this. I'm no expert but it seems I can't get it to push anything?

At least it's progress of some kind. alt text

AntiDroid

@totalrando It looks like the phone is still locked. Have you run

fastboot oem unlock

since getting the unlock code? If not just run that command while in fastboot and try again. You have to have the unlock option enabled in Androids developer mode before sending that command via fastboot.

TotalRando

@antidroid Well that changed the equation a little. I realized that I had drivers on the device itself, so I went back to Windows and installed them, and after reading your post, tried again in fastboot mode. NOW my device is finally unlocked. So I began running the script again.

$ ./flash-all-partitions.sh
Do you want to wipe all the data ( recommended )[Y/N]?y
[sudo] password for computer: 
Sorry, try again.
[sudo] password for computer: 
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: Check device console.)
finished. total time: 0.001s
target didn't report max-download-size
sending 'aop_a' (180 KB)...

so I will report back with results as they happen. Not sure why it's taking 5 minutes to do 180KB but hey, I like progress as it comes.

AntiDroid

@totalrando That does seem strange and also not correct. My guess is you will need to try again. Since you now have the bootloader unlocked correctly you could try the way that is recommended rather than mine.

My script is just an automated way of doing the steps provided here plus a second script to flash the critical. You could try following the manual steps to slow it down and not get stuck with the script hanging on failures. (They talk a lot about danger but they are just covering their butts)