Database Users

[How To] Downgrade to 4.5.3 so you can root device

Step by step instructional video
Help setting up adb for windows: https://www.youtube.com/watch?v=CyJlmTtLsIg
If you are already running Fire OS 4.5.3 and below, all you need to do is follow this video to root: https://youtu.be/KcQ30qcImJc
Steps:
1. Install the Fire OS 5.0 developer preview. EDIT: Do not do this. If you already have a lollypop ROM installed, use that instead of installing dev preview (You could cause a brick)
2. Enable ADB on your device and set up ADB on your computer
3. Download 4.5.3 firmware: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.3_user_453011120.bin (Mirror coming soon. This download works for the Fire HD7 and HD6)
4. connect device to computer and run "adb reboot recovery"
5. use volume keys and power button to navigate to "Apply update from ADB"
6. from computer type "adb sideload update-kindle-20.4.5.3_user_453011120.bin"
7. from tablet select "wipe data/factory reset"
8. from tablet select "reboot system"
9. Complete setup (do not connect to a wifi network yet)
10. Download KingRoot: http://www.kingroot.net/
11. Download JmzFireHDTool: http://forum.xda-developers.com/fir...ool-jmz-fire-hd-7-tool-gapps-disable-t3113655
12. install both apps. "adb install KingRoot-4.1.0.249-release-nolog-201505211812_105001.apk" and "adb install JmzFireHDTool_v4.apk"
13. Temporarily disable otaverify via adb "adb shell pm block com.amazon.otaverifier" (spelled wrong in video)
14. Connect to wifi so that KingRoot can work
15. Open KingRoot on your device
16. press "try to root"
17. re-enable otaverifier "adb shell pm unblock com.amazon.otaverifier" (spelled wrong in video)
18. Open JMZ Fire Tools and press "Disable OTA's"
Note: If you ever need to upgrade back to lollypop, you should follow these steps so you do not brick device: http://forum.xda-developers.com/fire-hd/general/tools-fire-hd-67-rooting-gapps-t3371242/page4

Awesome find !!! Here is a direct link to the 5.2.0 update file:
http://forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810
After the downgrade, install TWRP, and upgrade to 4.5.4 but this time with root and fully working GAPPS:
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
This way one goes directly to SuperSu, and a clean device with no traces of KingRoot.

bibikalka said:
Awesome find !!! Now, can you install TWRP, and try to upgrade to 4.5.4 while keeping root as per this post:
http://forum.xda-developers.com/showpost.php?p=61329063&postcount=4
This way one goes directly to SuperSu, and a clean device with no traces of KingRoot.
Click to expand...
Click to collapse
ah yes good idea. I'm hoping someone with ROM development knowledge will start a build. We've got just about everything setup so that a custom ROM can run
Sent from my LG-V480 using Tapatalk

powerpoint45 said:
ah yes good idea. I'm hoping someone with ROM development knowledge will start a build. We've got just about everything setup so that a custom ROM can run
Click to expand...
Click to collapse
The tricky part is that the unlocked bootloader still needs a signed kernel. Which is pretty constraining. It'd be interesting to replace the boot preloader, but the risks are high.
Upon boot (if connected to PC), the system flashes MT65xx pre-loader. Which seems to indicate that one could start looking into programs such as "Smart Phone Flash Tool" and "MTK Droid Tools" for MTK chipsets.
Another hope is that the 5.0 version would be sufficiently buggy, such that the bootloader can be made to boot unsigned kernels.

bibikalka said:
The tricky part is that the unlocked bootloader still needs a signed kernel. Which is pretty constraining. It'd be interesting to replace the boot preloader, but the risks are high.
Upon boot (if connected to PC), the system flashes MT65xx pre-loader. Which seems to indicate that one could start looking into programs such as "Smart Phone Flash Tool" and "MTK Droid Tools" for MTK chipsets.
Another hope is that the 5.0 version would be sufficiently buggy, such that the bootloader can be made to boot unsigned kernels.
Click to expand...
Click to collapse
Hashcode has gotten around this issue multiple times with something called a bootstrap but I'm not too sure how it works
Sent from my LG-V480 using Tapatalk

Btw, any chance you could post the direct link to 5.0 preview (for non-developers), since it's probably behind some registration page or something ...

i just signed in with my amazon account, you will need to unroot your fire and reset it as 5.0 is a OTA.

bibikalka said:
Btw, any chance you could post the direct link to 5.0 preview (for non-developers), since it's probably behind some registration page or something ...
Click to expand...
Click to collapse
I wish I could find that bin file link... I looked for it but could not find a link to the actual bin file.. If ota's download to the sdcard then It could still be accessed but I don't know where it downloads to. If it downloads to the data dir of the app it would be inaccesable since you need to be on the latest update in order to download the 5.0 version and on the latest version we have no root which means no access to data dir
Sent from my LG-V480 using Tapatalk

this is a great find. but stupid me only have a macbook pro and i cant set up adb. sucks..

edgar.vrgs said:
this is a great find. but stupid me only have a macbook pro and i cant set up adb. sucks..
Click to expand...
Click to collapse
you can set it up on a mac. Just do a little searching. I know it's plausible
Sent from my LG-V480 using Tapatalk

powerpoint45 said:
you can set it up on a mac. Just do a little searching. I know it's plausible
Sent from my LG-V480 using Tapatalk
Click to expand...
Click to collapse
i have tried but i cant figure it out

It worked perfectly. Thanks

Despite really wanting root and the possibility of using my already paid for apps from the Play store, I really like the lollipop version of fire os. I do think it's a bit ridiculous they haven't retained the old kindle skin because it's exactly how every real android tablet looks but at this point they should be forced by law to let people use the Play store as they wish. Sort of like how Verizon was once forced to allow tethering without a subscription.

devicer said:
It worked perfectly. Thanks
Click to expand...
Click to collapse
great to hear it!
Sent from my LG-V480 using Tapatalk

bpeery84 said:
Despite really wanting root and the possibility of using my already paid for apps from the Play store, I really like the lollipop version of fire os. I do think it's a bit ridiculous they haven't retained the old kindle skin because it's exactly how every real android tablet looks but at this point they should be forced by law to let people use the Play store as they wish. Sort of like how Verizon was once forced to allow tethering without a subscription.
Click to expand...
Click to collapse
I hear ya
Sent from my LG-V480 using Tapatalk

so i finally got adb on my mac to work, but now when i am on the last command to install 4.5.3 terminal says it can't read update-kindle-20.4.5.3_user_453011120.bin
has anybody done this on a mac and would like to guide me on what i am doing wrong?

edgar.vrgs said:
so i finally got adb on my mac to work, but now when i am on the last command to install 4.5.3 terminal says it can't read update-kindle-20.4.5.3_user_453011120.bin
has anybody done this on a mac and would like to guide me on what i am doing wrong?
Click to expand...
Click to collapse
does adb devices list your device. Maybe try re-downloading the update in case of corruption
Sent from my LG-V480 using Tapatalk

Perfect timing! Lost root last week and hoped for a way to get back. You the man

I wonder if there is a way to stop the update once it's downloaded, in order to grab the 5.0 update bin from /cache.
This would help to re-pack the update in a way that does not re-write key partitions, then one can have TWRP and root on 5.0
It does sound like 5.0 is a nice update, since it provides stock Android. That's what custom ROMs are usually for, but Amazon will give it away !

bibikalka said:
I wonder if there is a way to stop the update once it's downloaded, in order to grab the 5.0 update bin from /cache.
Click to expand...
Click to collapse
I was wondering the same. Seems like you could rename the otaverifier apk back to (plain) .apk and get the download but by keeping com...otaverifier blocked it wouldn't install. I'm just not sure these developer updates are handled like any other.

Can't sideload the OTA

Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it

Vref said:
Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it
Click to expand...
Click to collapse
Have you tried switching ports?

Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands

I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...

DJBhardwaj said:
Have you tried switching ports?
Click to expand...
Click to collapse
Nope...didn't think that would be an issue but I can always try.
brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
mgrass said:
I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...
Click to expand...
Click to collapse
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site

brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
You're talking about flashing the factory images with fastboot, he's talking about sideloading the full OTA.

Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.

Heisenberg said:
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.
Click to expand...
Click to collapse
Roger that. Thanks Heisenberg... I'll give it another go tonight.

Vref said:
Roger that. Thanks Heisenberg... I'll give it another go tonight.
Click to expand...
Click to collapse
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!

Vref said:
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!
Click to expand...
Click to collapse
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Dunno how or why it finally took but this isn't the first time I've had to switch from port to port (like a drunken sailor) to get it to see the phone but I've always attributed that to Android File Transfer being a little b!tch. I can tell you when I restored from Pure Nexus and relocked the bootloader two weeks ago it worked 4.0....not a clue as to why it got all fussy today.

Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.

billamin said:
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.
Click to expand...
Click to collapse
Cool. Glad you got it working.

Unlocking bootloader and rooting your Honor 8 [Easist methods]

Check this link and follow the instruction for unlocking the bootloader- http://www.modaco.com/forums/topic/...your-honor-8-official-and-unofficial-methods/
For rooting your phone, download the latest version from the link provided, boot your phone into recovery mode (make sure you have TWRP installed) and flash the zip. Enjoy! https://download.chainfire.eu/696/supersu/

this phone is so new that there's barely anyone talking about it here on xda, so since there's no responses i'm mostly wondering how many people actually tried this and if anyone experienced any issues.
either way, thnx a lot for your work meraj99. i'm actually backing up my phone to unlock the bootloader and then root it as i'm writing this, so i'm pretty excited to finally get root

JimZiii said:
this phone is so new that there's barely anyone talking about it here on xda, so since there's no responses i'm mostly wondering how many people actually tried this and if anyone experienced any issues.
either way, thnx a lot for your work meraj99. i'm actually backing up my phone to unlock the bootloader and then root it as i'm writing this, so i'm pretty excited to finally get root
Click to expand...
Click to collapse
Don't download that version of SuperSU I had issues with it, my device boot looped, you need a forced systemless version
https://www.androidfilehost.com/?fid=24591000424939898
And also if you can please upload a backup of your system please I had to use an outdated rom from modaco to restore my device

JEANRIVERA said:
Don't download that version of SuperSU I had issues with it, my device boot looped, you need a forced systemless version
https://www.androidfilehost.com/?fid=24591000424939898
And also if you can please upload a backup of your system please I had to use an outdated rom from modaco to restore my device
Click to expand...
Click to collapse
I used this guide on my L09 and it worked without problems.
http://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946/page1
Sent from my HUAWEI VIE-L29 using XDA Labs

You can get an account with 4 credits for free via DC-Unlocks facebook page, you need 20 friends though. If you don't have facebook then you can get it for 1 usd from their android app.
The purchase is In-app and uses googles payment system so you can use the spare change from opinion rewards too.

m4ds3n said:
You can get an account with 4 credits for free via DC-Unlocks facebook page, you need 20 friends though. If you don't have facebook then you can get it for 1 usd from their android app.
The purchase is In-app and uses googles payment system so you can use the spare change from opinion rewards too.
Click to expand...
Click to collapse
What are you talking about? lol

Tikerz said:
What are you talking about? lol
Click to expand...
Click to collapse
To unlock your phone via DC-unlocker, you need four credits. I just mentioned how you could get them for cheaper than buying them via their program.

m4ds3n said:
To unlock your phone via DC-unlocker, you need four credits. I just mentioned how you could get them for cheaper than buying them via their program.
Click to expand...
Click to collapse
But are you mentioning this as someone who had "verified" success in this method? Sorry but pyramid schemed non dev focused sources are a bit schetchy, especially given the lack of dev due to the new phone and the other decampment issues going on currently

*mj13* said:
But are you mentioning this as someone who had "verified" success in this method? Sorry but pyramid schemed non dev focused sources are a bit schetchy, especially given the lack of dev due to the new phone and the other decampment issues going on currently
Click to expand...
Click to collapse
I understand your concern, both of the facebook page and the app is run by dc-unlocker themselves. If you look at their webpage you'll find links to both of them.

Personnaly the unofficial methode worked good for me because de Huawei club's website was broken for the captcha. I payed 0.99€ and got the Bootloader unlock code !

meraj99 said:
Check this link and follow the instruction for unlocking the bootloader- http://www.modaco.com/forums/topic/...your-honor-8-official-and-unofficial-methods/
For rooting your phone, download the latest version from the link provided, boot your phone into recovery mode (make sure you have TWRP installed) and flash the zip. Enjoy! https://download.chainfire.eu/696/supersu/
Click to expand...
Click to collapse
I run DriverSetup.exe (Huawei driver pack from https://files.dc-unlocker.com/share.html?v=share/88D4A98C154D4E19AF9D4A1EF09BA620), but nothing happens, and DC Unlocker doesnt find Honor 8.
What could be the problem?

Shyciii said:
I run DriverSetup.exe (Huawei driver pack from https://files.dc-unlocker.com/share.html?v=share/88D4A98C154D4E19AF9D4A1EF09BA620), but nothing happens, and DC Unlocker doesnt find Honor 8.
What could be the problem?
Click to expand...
Click to collapse
Did u do this?
On your phone, enter Manufacturer Mode - open the dialer and enter?**#*#2846579#*#*. In the app that then opens,?*select Project Menu -> Background settings -> USB ports settings -> Manufacturer Mode.
Sent from my HUAWEI VIE-L29 using XDA Labs

Mostar088 said:
Did u do this?
On your phone, enter Manufacturer Mode - open the dialer and enter?**#*#2846579#*#*. In the app that then opens,?*select Project Menu -> Background settings -> USB ports settings -> Manufacturer Mode.
Sent from my HUAWEI VIE-L29 using XDA Labs
Click to expand...
Click to collapse
Yes, sure, but cannot find my phone.

Shyciii said:
Yes, sure, but cannot find my phone.
Click to expand...
Click to collapse
I finally successfully unlocked, TWRP'd, and rooted this morning.
I believe I had to also swipe down the notification shade and tap Files where it says USB Charging.

guitardedhero said:
I finally successfully unlocked, TWRP'd, and rooted this morning.
I believe I had to also swipe down the notification shade and tap Files where it says USB Charging.
Click to expand...
Click to collapse
I try other usb port, other computer, but DC-Unlocker show doesnt found phone
Show Android Device in Other Device in the device manager.

Shyciii said:
I try other usb port, other computer, but DC-Unlocker show doesnt found phone
Show Android Device in Other Device in the device manager.
Click to expand...
Click to collapse
Did you check your USB notification to ensure that it was not used for charging only? Before and after the Manufacture Mode, tap Files in the USB notification, and then select in DC-Unlocker:
Huawei Phones and Auto Select
Also, I had made both $0.99 purchases within the DC-Unlocker Android app which gave me a User and Password in an email that I was able to input into the Server section of the Windows DC-Unlocker app under Unlock which may have helped.
Once the device is found in the lower left, choose Read Bootloader Code and DO NOT select Unlock in the upper right. Paste the Bootloader Code at the end of your "fastboot oem unlock xxxxxxxxxxxxxxx"

guitardedhero said:
Did you check your USB notification to ensure that it was not used for charging only? Before and after the Manufacture Mode, tap Files in the USB notification, and then select in DC-Unlocker:
Huawei Phones and Auto Select
Also, I had made both $0.99 purchases within the DC-Unlocker Android app which gave me a User and Password in an email that I was able to input into the Server section of the Windows DC-Unlocker app under Unlock which may have helped.
Once the device is found in the lower left, choose Read Bootloader Code and DO NOT select Unlock in the upper right. Paste the Bootloader Code at the end of your "fastboot oem unlock xxxxxxxxxxxxxxx"
Click to expand...
Click to collapse
Problem solved. I installed Huawei driver pack, then its not enough. I installed HiSuite (android device manager+driver), then the DC-Unlocker working fine, found my phone, and get code. Thx for your help.

Is there a root method for that L04 version?

jkbane said:
Is there a root method for that L04 version?
Click to expand...
Click to collapse
No one tested it yet.

jkbane said:
Is there a root method for that L04 version?
Click to expand...
Click to collapse
PalakMi said:
No one tested it yet.
Click to expand...
Click to collapse
You can use the twrp for L09 and flash SuperSU 2.76 after unlocking bootloader. It works. I just had issues trying to backup a ROM.

[Root && Unlock] Droid Turbo 6.0.1 mcg24.251-5-5

@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
fastboot oem config fsg-id " "
Click to expand...
Click to collapse
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.

jcase said:
@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.
Click to expand...
Click to collapse
@jcase, please clarify...
Do you mean mcg24.251-5 or mcg24.251-5-5 (with extra -5 at the end?) The one with the extra -5 at the end (mcg24.251-5-5) is the most current Verizon Droid Turbo firmware (released March 2017) which did NOT work with Sunshine. Whereas mcg24.251-5 (with only one -5) already does work with Sunshine.

ChazzMatt said:
@jcase, please clarify...
Do you mean mcg24.251-5 or mcg24.251-5-5 (with extra -5 at the end?) The one with the extra -5 at the end (mcg24.251-5-5) is the most current Verizon Droid Turbo firmware (released March 2017) which did NOT work with Sunshine. Whereas mcg24.251-5 (with only one -5) already does work with Sunshine.
Click to expand...
Click to collapse
mcg24.251-5-5

Fantastic. Yeah, I figured that had to be typo.
Will make a lot of people happy.

I will try now

KARIM9377 said:
I will try now
Click to expand...
Click to collapse
Yes, great news, right?

jcase said:
@autoprime got the initroot working with internet for Droid Turbo - https://forum.xda-developers.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316/
This provides a temp root until reboot, after rebooting you have to go into the bootloader and run
To clear out the ramdisk address.
While temprooted, SunShine will work to unlock the device again.
Click to expand...
Click to collapse
So just to be clear, the correct method would be to install sunshine, install temproot per the instructions that you linked to, sunshine it up, and uninstall the temproot by performing fastboot oem config fsg-id "" ?

TheSt33v said:
So just to be clear, the correct method would be to install sunshine, install temproot per the instructions that you linked to, sunshine it up, and uninstall the temproot by performing fastboot oem config fsg-id "" ?
Click to expand...
Click to collapse
i would assume you could install sunshine apk before or after temproot. does not matter which.
boot using temproot.
sunshine it up.
fastboot oem config fsg-id ""
if you dont run fastboot oem config fsg-id "" afterwards the phone will boot loop.
for those not planning on using sunshine and just want root there are alternative methods in post #2 of the temproot thread for avoiding the boot loop without needing to be near a computer.

Oh My Lord. @jcase and @autoprime do it again! Even though mine is unlocked my replacement 32gb isnt and this may make me buy a new screen for it to use! Looks like i know what im doing on my day off tomorrow. Transplanting this screen back onto its orginal donor and unlocking that sucker

autoprime said:
i would assume you could install sunshine apk before or after temproot. does not matter which.
boot using temproot.
sunshine it up.
fastboot oem config fsg-id ""
if you dont run fastboot oem config fsg-id "" afterwards the phone will boot loop.
for those not planning on using sunshine and just want root there are alternative methods in post #2 of the temproot thread for avoiding the boot loop without needing to be near a computer.
Click to expand...
Click to collapse
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?

TheSt33v said:
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?
Click to expand...
Click to collapse
no, pressing volume down or vol dwn + pwr should not interfere with sunshine.
whichever method people find easier.. i'd assume not everyone will be able to catch it on the initial reboot after sunshine completes.
i'd just avoid pressing buttons while sunshine is still running.. but once the screen shuts off have at it.
also, not sure how it is with the turbo but on my g4 play i do not have to force a 'power down' while phone is in bootloop. i just wait for bootloop cycle to turn screen off and then quickly press the button combo to go into fastboot (volume down + power for g4 play).

Great was to slow and now I have a bootloop. Restarted to fastboot but ADB can not find the device. Can anybody help me with the next steps. Bootloader is unlocked so all that is left now is getting the device to boot.
Figured it out myself!
Once you have a bootloop restart into fastboot and open up the the fastboot folder in "auto-initroot_xt1254_quark_vzw_mcg24.251-5-5".
Then open up a command promp and issue the => fastboot.exe oem config fsg-id "" command. That's all!
Thanks a lot to JCase and his team for developing this hack!
BRB installing lots of ****

FYI @TheSt33v...
Haven't read your updated instructions, but this may be something worth mentioning if you haven't already.
killer520 said:
Great was to slow and now I have a bootloop. Restarted to fastboot but ADB can not find the device. Can anybody help me with the next steps. Bootloader is unlocked so all that is left now is getting the device to boot.
Figured it out myself!
Once you have a bootloop restart into fastboot and open up the the fastboot folder in "auto-initroot_xt1254_quark_vzw_mcg24.251-5-5".
Then open up a command promp and issue the => fastboot.exe oem config fsg-id "" command. That's all!
Thanks a lot to JCase and his team for developing this hack!
BRB installing lots of ****
Click to expand...
Click to collapse

ChazzMatt said:
FYI @TheSt33v...
Haven't read your updated instructions, but this may be something worth mentioning if you haven't already.
Click to expand...
Click to collapse
Those instructions were in autoprime's OP, so they did make it into my guide.

need more help
TheSt33v said:
Thanks. If I remember correctly, Sunshine reboots the phone automatically after doing its thing. Will holding down volume down to boot directly into bootloader after Sunshine completes interfere with Sunshine in any way? Because that's what I would need to do in order to issue that fastboot command without going into a bootloop. Or should I just tell people to go into bootloop, force power down, get into bootloader and issue the uninstall command?
Click to expand...
Click to collapse
what to do step by step to get my droid xt1254 unlock with sunshine
if i put the sunshine code and the unlock fail is the code still working for the next try or i have to buy another one

KARIM9377 said:
what to do step by step to get my droid xt1254 unlock with sunshine
if i put the sunshine code and the unlock fail is the code still working for the next try or i have to buy another one
Click to expand...
Click to collapse
See updated guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
As for the code not working after a failure, I don't think you'll need another code if yours fails, but that would be a better question for Sunshine customer support if you want to be sure before trying it.

TheSt33v said:
See updated guide: https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
As for the code not working after a failure, I don't think you'll need another code if yours fails, but that would be a better question for Sunshine customer support if you want to be sure before trying it.
Click to expand...
Click to collapse
thanks for your help
can you please update the TWRP

KARIM9377 said:
thanks for your help
can you please update the TWRP
Click to expand...
Click to collapse
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.

KARIM9377 said:
thanks for your help
can you please update the TWRP
Click to expand...
Click to collapse
TheSt33v said:
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.
Click to expand...
Click to collapse
What @TheSt33v said.
This link is to the most recent TWRP with @bhb27 mods for our Quark phones. @bhb27 is our official TWRP maintainer. He's why our TWRP has official status. But he also builds personalized versions which include some features/mods for our phones that other TWRP versions do not have, mods specifically for our Quarks. His modded versions are always better than the versions on the TWRP website (which again are only there due to his efforts).
On that page below you want the modded TWRP with the most recent date -- will always be the one listed at the bottom.
https://www.androidfilehost.com/?w=files&flid=39562

need help
TheSt33v said:
You mean update the link? The provided link is the most recent version of TWRP for our device (except for the one I made myself using only open source and was told not to give to anyone, but that's a story that doesn't need to be opened up again).
Well, technically that's not true. If you want the true latest official version from TWRP's website, here it is: https://dl.twrp.me/quark/twrp-3.1.1-0-quark.img.html
However, that version does not have all the improvements and special features that BHB implemented. For the purposes of unlocking your bootloader and basic flashing/backups, either version will work just fine.
Click to expand...
Click to collapse
i need stack firmware to flash it with my locked droid turbo xt1254 MCG24.251-5-5 with tool to falsh it

[Guide] How to root the Pixel 3a with or without twrp & take OTA updates once rooted

[Guide] How to root the Pixel 3a with or without twrp & take OTA updates once rooted
THIS IS A DRAMA FREE THREAD, I'M NOT GOING TO BASH OTHERS THREADS, NOR AM I GOING TO GO AROUND TO THOSE THREADS AND BASH THEM IN IT BECAUSE I SOMEHOW FEEL SUPERIOR TO THEM.
Standard you do this at your own risk and I'm not responsible for anything warning.
There are a few ways you can go about rooting. You can either use twrp, manually patch the stock boot image and flash it, or just flash a pre-patched boot image. I'll be going over all three, but keep in mind i have depreciated the pre-patched method now that we have twrp. twrp is dead on 10
Do these first if you haven't already:
Update your fastboot and adb
I just toss these 4 highlighted files into the windows folder, but you may have a different set up(I put them in the windows folder so I don't have to add them to PATH.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Googles USB driver if you need it
right click the start menu icon, click device manager, then locate your phone(should have a yellow symbol on it, right click it, then click update driver, then click browse my computer, click the browse button and then navigate to where you extracted the drivers, click the main folder(usb_driver) and then click ok, then click next and ok through any prompts.
CMD = Command Prompt
Unlocking your bootloader:
This wipes your phone
Run through the initial setup if you haven't already, if you haven't don't bother logging into your google account.
Enable dev options(settings>about phone>build number>tap it 7 times).
Go into settings>system>advanced>dev options>oem unlocking, click the toggle.
While still in dev options scroll down a little and enable usb debugging.
Plug your phone into your pc.
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Open up command prompt(powershell works to but i always use command prompt) type into the cmd window
Code:
adb reboot bootloader
The phone will reboot into fastboot mode.
Now type into the cmd window
Code:
fastboot devices
See if it lists a device, if not you need to install the drivers I linked to. If you had to install the drivers try the fastboot devices command again after installing them, it should list the device now.
type in
Code:
fastboot flashing unlock
You will then have to use the phone to select yes to the unlock. you use the volume keys to select and the power button to confirm.
Your bootloader is now unlocked and you follow one of the below root methods.
Onto the root methods:
these are for stock phones, not ones using a custom kernel
IF ON Q YOU MUST USE MAGISK 19.4+
Grab your boot.img from here
it's inside the zip that is inside the folder in the main zip you download
patching and flashing the stock boot.img:
This is the only way to root on android 10+ as twrp doesnt work
Reboot your phone.
Run through the initial setup again, this time you can log into your google account and set the phone up how you want. Re-enable dev options, enable adb, and turn off auto updates.
Grab the stock boot.img for your matching build(from the link above).
Put the boot.img on your phone, location doesn't really matter, as long as you know where you put it.
Download and install Magisk Manager.
Open up magisk manager and click install, then select the "Select and Patch a File" option, let it do its thing.
Move the patched image from your phone to your pc(magisk stores the patched image in your downloads folder).
Open up a cmd window and type in
Code:
adb reboot bootloader
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Once you are in the bootloader(fastboot) type in
Code:
fastboot getvar current-slot
This will tell you the currently active slot of your phone, remember it.
Now to flash your patched boot.img.
- If the cmd window location does not match the location of the boot.img you will have to enter that too.
- If you're on windows 10(this only works on English as far as i know) you can use my Tools Menu it will give you some handy options in your right click context menu. It makes things a lot easier as you can just right click in the location of the boot.img and open a cmd window there.
- If your cmd window is opened in the same location as the boot image you can just do(don't include the ")
Code:
fastboot flash boot_"slot "whatever the boot.img is named"
- If your cmd window was not opened in the same location as the boot image you will need to do one of these.
Code:
cd C:\Users\pbanj\Desktop\android
the cd command changes the current directory to where you tell it. then you can just do
Code:
fastboot flash boot_"slot" "whatever the boot.img is named"
- Or you can type out the location to the boot.img or just drag the boot.img file onto the cmd window. example:
Code:
fastboot flash boot_"slot" C:\Users\pbanj\Desktop\boot.img
Once that's done flashing just type in
Code:
fastboot reboot
MAKE SURE YOU GO INTO DEV OPTIONS AND TURN OFF AUTO UPDATES.
You should use the twrp method over this next one. I'll no longer be adding updated pre-patched boot images as they're completely pointless now that we have twrp.
Do NOT use this method, it's here just for history sake
Method 3 booting a prepatched boot.img and direct installing Magisk:
This gets you rooted a bit faster. thanks to @Uzephi for reminding me about this.
Grab the boot.img that matches your build number in about phone. These were made using the newest canary build of magisk at the time of adding them to the post. If I update them I'll mark them as updated. I used the canary builds for these as it's what I personally use
- PD2A.190115.029
- PD2A.190115.032 Updated to newest canary build as of May-28-2019
- PQ3B.190605.006 This is the June update Updated to the 19.4-c1602d25(19301) canary build
- PQ3B.190705.003 this is the July update
Save it somewhere and rename it if you want.
If not already in fastboot mode open up a command prompt window and type in
Code:
adb reboot bootloader
if/when the phone asks you to trust the computer make sure to check the "always allow this computer" check box.
Once you are in the bootloader(fastboot) type in
Code:
fastboot boot "whatever the boot.img is named".img
- If the cmd window location does not match the location of the boot.img you will have to enter that too.
- If you're on windows 10(this only works on English as far as i know) you can use my Tools Menu it will give you some handy options in your right click context menu. It makes things a lot easier as you can just right click in the location of the boot.img and open a cmd window there.
- If your cmd window is opened in the same location as the boot img you can just do(don't include the ")
Code:
fastboot boot "whatever the boot.img is named".img
- If your cmd window was not opened in the same location as the boot image you will need to do one of these.
Code:
cd C:\Users\pbanj\Desktop\android
the cd command changes the current directory to where you tell it. then you can just do
Code:
fastboot boot "whatever the boot.img is named".img
- Or you can type out the location to the boot.img or just drag the boot.img file onto the cmd window. example:
Code:
fastboot boot C:\Users\pbanj\Desktop\android\boot.img
Once booted run through the initial setup again(if you haven't already after unlocking the bootloader), this time you can log into your google account and set the phone up how you want.
MAKE SURE YOU GO INTO DEV OPTIONS AND TURN OFF AUTO UPDATES.
After you've run through the initial setup(if you had to) open up Magisk Manager(it will most likely say the manager needs to be installed as it is currently only a stub) and then click on the top install option, then click install in the popup that comes up, then click the direct install option.
After it finishes click reboot and you're good to go
UPDATING
There are a couple methods of updating.
Uninstall the edge sense plus mod before you update or you won't be able to root again/you'll end up in a bootloop and will have to enter safemode to disable it.
WHEN UPDATING TO ANDROID 11 DISABLE ALL MAGISK MODS AND REBOOT ONCE BEFORE UPDATING.
If you're using any custom kernel you'll have to flash the stock boot.img first before updating for the sideload method. The magisk method it might not matter but I'm not 100% sure on that. I'd think it'd be fine if you had magisk backup the stock image before you flashed the custom kernel, I don't use one so I cant be 100% sure though.
magisk has removed the ota method for pixel devices so these are the ways to update now.
My personal favorite way to update is to use the full system image as it's fastest. Disable any custom themes or modules that are known to cause bootloops when updating. Then:
grab the system image from here, unzip the folder and inside of it you will find another zip. open that up and pull the boot.img out.
Use magisk manager on your phone to patch that and then take the patched image and rename it to boot.img and put it back in the zip you pulled the stock one from.
Open the "flash-all.bat or .sh if on linux" and remove the -w from the end(this is important as it stops your device from being wiped) save the bat file.
put your phone into fastboot mode and run the flash-all script. should take about 5 min and then your phone will reboot and you are good to go.
I made a telegram group where I'll be posting the system images ready to flash. I typically make them within a few days of the update coming out. https://t.me/joinchat/EC3ivRhc2-t4y1J4REtuqg
Alternative Update method
Grab the OTA update from here.
Reboot the phone into recovery, you can just use
Code:
adb reboot recovery
Once in recovery press power and up and you should see the options.
Go down to apply update from adb(use the volume keys to change options and the power button to select).
Open a cmd window if you haven't already and type in
Code:
adb sideload "ota update file"
Location matters just like it did during the initial flashing, if you didn't open the cmd window in the same location as the update file andyou don't remember what to do, just take a look at one of the root methods as they tell you how to go about fixing that. Or just type in "adb sideload" and then drag the update file onto the cmd window.
After the ota is done select the "reboot to bootloader option".
Once in the bootloader(fastboot) just flash the pre-patched boot.img like you did before. remember the slot changes with each update so make sure you get the current slot, or if you remember what slot it was using before the update just switch input the other one. so if it was on slot a you would flash the patched image to b and vise versa.
BOOT IMAGES:
This is a google drive folder, it will have both stock and patched images. I also provide the newest Magisk manager These are zip files, you must unzip them to use them.
- https://drive.google.com/drive/folders/1wH7pvsHYznbDJ_vTsb_dWBNJBDcx2wHx?usp=sharing
Pass Safetynet
Open Magisk & go into its settings
Scroll down to the "Magisk" category and turn "Zygisk (beta)" on, & "Enforce DenyList" on.
Tap on "Configure DenyList"
Then tap the 3 dot menu and check "show system apps"
Add "google play services", google play store", "google pay", and any of your banking apps or apps that ***** about root.
Reboot
Install Universal Safetynet Fix and reboot
Install Yasnac from the Play Store
Open Yasnac and tap "run SafetyNet attestation" you should get pass on both basic and CTS.
How to use Netflix
Grab the newest apk from here.
Install the apk.
Add the apk to your Magisk DenyList.
if you need help you can ask here in the thread or in the Telegram group

pbanj said:
So I figured I would make a single thread out of the posts I've made. I made prepatched boot.img files to save everyone time.
I assume everyone here knows you need an unlocked bootloader and how to flash them.
Standard you do this at your own risk and I'm not responsible for anything warning.
Update your fastboot and adb
Googles USB driver if you need it
Grab the boot.img that matches your build number in about phone. These were made using the newest canary build of magisk at the time of this thread.
pd2a.190115.029
pd2a.190115.032
Save them somewhere and rename it if you want. then flash
To get google pay to work you may have to do some tinkering(I had to). To get it working go into magisk hide, enable show system apps then make google play services, the play store and pay look like this
Now comes the fun part.
- Plug your phone into your pc
- Grab your root app of choice that allows you to freeze apps
- Freeze google play services this will make your phone pissed and you will get a bunch of notifications, ignore them for now
- Open your favorite command line utility and do
Code:
adb shell
then
Code:
su
grant it root on your phone.
- Then while still in adb shell enter
Code:
rm -rf /data/data/com.google.android.gms
- Go into settings, then apps
- Clear the data of pay, and the play store
- Click disable on the playstore and then yes to restoring the factory version, reenable it
- Reboot your phone. It will ***** about lack of play services again, still ignore it.
- Reenable google play services
- Wait a min so it can do its thing
- Now you can add your cards to pay.
Click to expand...
Click to collapse
Dang, mine worked after I hid Google pay with magisk! That's an intensive process. I clicked hide them rebooted and added my amex without issue. Had to **** system apps to hide play store so I could download Netflix too.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:57 PM ----------
jmtjr278 said:
Dang, mine worked after I hid Google pay with magisk! That's an intensive process. I clicked hide them rebooted and added my amex without issue. Had to click system apps to hide play store so I could download Netflix too.
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
Almost forgot to mention, thanks for the patched image. Saved me some time
Sent from my Pixel 3a using Tapatalk

jmtjr278 said:
Dang, mine worked after I hid Google pay with magisk! That's an intensive process. I clicked hide them rebooted and added my amex without issue. Had to **** system apps to hide play store so I could download Netflix too.
Sent from my Pixel 3a using Tapatalk
---------- Post added at 04:58 PM ---------- Previous post was at 04:57 PM ----------
Almost forgot to mention, thanks for the patched image. Saved me some time
Sent from my Pixel 3a using Tapatalk
Click to expand...
Click to collapse
Ya I had them hid and it wouldn't let me add my cards. so I went oh it must have triggered before I hid them. So I did the old "clear all their data" trick and it still wouldn't let me do it. I was talking in my discord server and was told about how the play services remembers. They told me to do all the stuff I posted and then run that command from twrp. Well we dont have twrp yet so I was like **** am I screwed until then. then another one was like if you freeze the play services and then try the command it might work. So I did and it worked. wasted about an hour of my time lol.

pbanj said:
Ya I had them hid and it wouldn't let me add my cards. so I went oh it must have triggered before I hid them. So I did the old "clear all their data" trick and it still wouldn't let me do it. I was talking in my discord server and was told about how the play services remembers. They told me to do all the stuff I posted and then run that command from twrp. Well we dont have twrp yet so I was like **** am I screwed until then. then another one was like if you freeze the play services and then try the command it might work. So I did and it worked. wasted about an hour of my time lol.
Click to expand...
Click to collapse
The things we do to have fun! That's what I love though, seeing a problem and figuring out the solution. Android is the best. Teaches me things every day
Sent from my Pixel 3a using Tapatalk

Does this work with US carrier Pixel 3a's? (TMobile, Version, AT&T, etc.)

lovelockdown said:
Does this work with US carrier Pixel 3a's? (TMobile, Version, AT&T, etc.)
Click to expand...
Click to collapse
If they will allow you to unlock the bootloader yes. Otherwise no

pbanj said:
If they will allow you to unlock the bootloader yes. Otherwise no
Click to expand...
Click to collapse
I was surprised to find the oem unlock greyed out on T-Mobile.
It does come with the Unlock app for unlocking carrier restrictions but if i remember that didn't effect the bootloader.
Work around will hopefully be found. I will say that i found a audio mod and ad block without root have been good so far

razrlover said:
I was surprised to find the oem unlock greyed out on T-Mobile.
It does come with the Unlock app for unlocking carrier restrictions but if i remember that didn't effect the bootloader.
Work around will hopefully be found. I will say that i found a audio mod and ad block without root have been good so far
Click to expand...
Click to collapse
man that sucks. i would just return it and buy it from google. or hell even bestbuy will give you an unlocked one and let you add it to your tmobile account.

pbanj said:
man that sucks. i would just return it and buy it from google. or hell even bestbuy will give you an unlocked one and let you add it to your tmobile account.
Click to expand...
Click to collapse
Yeah i had already downloaded your boot.imgs. thanks for doing that for everyone.
I've been on a S9 for a while so I'm used to finding work arounds for no root. I will try to make it work for a while and see.

razrlover said:
I was surprised to find the oem unlock greyed out on T-Mobile.
It does come with the Unlock app for unlocking carrier restrictions but if i remember that didn't effect the bootloader.
Work around will hopefully be found. I will say that i found a audio mod and ad block without root have been good so far
Click to expand...
Click to collapse
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.

havens1515 said:
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
Click to expand...
Click to collapse
That's awesome!
A work around indeed! Appreciate it

havens1515 said:
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
Click to expand...
Click to collapse
I will give it a try right now and report back. Thanks.

havens1515 said:
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
Click to expand...
Click to collapse
still grayed out for me after factory reset with no sim
ill try it with a new phone as well
edit: also grayed out on my fresh out of the box phone as well
both from tmobile

havens1515 said:
I powered it on without a SIM card inserted (out of the box) and connected it to wifi and was able to enable OEM unlock.
If you do a factory reset and do the same (set it up without the SIM inserted) you should be able to as well.
Click to expand...
Click to collapse
Did you actually unlock the bootloader?
Thanks

I thought that oem unlock was greyed until you inserted a sim and connected to a network. Seems like this is the way it's always been on pixels.

gtuansdiamm said:
still grayed out for me after factory reset with no sim
ill try it with a new phone as well
edit: also grayed out on my fresh out of the box phone as well
both from tmobile
Click to expand...
Click to collapse
Did you connect to wifi? It was still grelayed out for me until I connected to wifi. Then went back one menu, and returned to developer options and it wasn't grayed out anymore
---------- Post added at 03:40 PM ---------- Previous post was at 03:39 PM ----------
alphahere said:
Did you actually unlock the bootloader?
Thanks
Click to expand...
Click to collapse
Yes, I did. You need to connect to wifi first before it will allow you to enable OEM unlock.
---------- Post added at 03:43 PM ---------- Previous post was at 03:40 PM ----------
Chronzy said:
I thought that oem unlock was greyed until you inserted a sim and connected to a network. Seems like this is the way it's always been on pixels.
Click to expand...
Click to collapse
Yes, it's grayed out until you connect to a network, but that network doesn't have to come from a SIM card (at least not in my case) it can come from wifi

Didn't work for me, factory reset for nothing. Now time to reinstall everything. ugh.

razrlover said:
I was surprised to find the oem unlock greyed out on T-Mobile.
It does come with the Unlock app for unlocking carrier restrictions but if i remember that didn't effect the bootloader.
Work around will hopefully be found. I will say that i found a audio mod and ad block without root have been good so far
Click to expand...
Click to collapse
When the device is paid off and unlocked (permanently, not a travel unlock) through the Unlock app, the OEM unlock option will no longer be grayed out. I can confirm it first hand and I'll add that this is how foreign carriers operate as well with regards to the Pixel.
The way that OEM unlocking works on *all* Pixels is through IMEI whitelisting. Factory Unlocked Pixels sold through Best Buy, Google Fi, Google Store and a few other retailers are whitelisted as being eligible for OEM unlocking. The option will be grayed out until the phone is connected to the internet so as to receive the eligibility state from Google.
Devices branded for T-Mobile are marked as ineligible, but T-Mobile (like virtually all carriers that sell the Pixel except for Verizon and NTT Docomo) updates the OEM Unlock eligibility flag at the same time they deem the device SIM unlock eligible. The device will check in with Google, receive the new eligibility state and unrestrict the OEM Unlock option.
The final bit of weirdness with the T-Mobile variant is how T-Mobile uses the Device Unlock app. Google has a custom SIM unlock solution for carriers that does not involve a carrier app or traditional unlock codes. It is similar to what the iPhone does & how OEM Unlock eligibility works - the carrier sends a request to Google for a phone associated with said carrier to be unlocked. Google processes the request, the phone checks in with Google and displays a notification stating that the SIM unlock was complete. For non Verizon/NTT Docomo carriers, that notification also means that you can now OEM Unlock.
T-Mobile doesn't use that functionality, for whatever reason, if there is even a reason. Maybe on account of Google not supporting temporary unlocks.
T-Mobile has long tied bootloader unlock eligibility to SIM unlock eligibility. You can buy a Moto whatever from T-Mobile, get denied a bootloader unlock code from Motorola's website, pay the device off and, boom, Moto changes their tune. The same is true with the OnePlus 6T and all current T-Mobile devices that have a sanctioned bootloader unlock mechanism.

Beware: My T-Mobile Pixel 3a Came With a SIM Card =(
My new-in-box T-Mobile Pixel 3a had a SIM card installed already. I booted it up, connected to wifi, and now I can't root it. =( Factory reset did not help.

darkmeridian said:
My new-in-box T-Mobile Pixel 3a had a SIM card installed already. I booted it up, connected to wifi, and now I can't root it. =( Factory reset did not help.
Click to expand...
Click to collapse
See above comment for a great explanation of why you can't unlock your TMobile carrier device.
Sent from my Pixel 3a using Tapatalk