Related
UPDATE:
OK I'M BACK INTO RECOVERY.
Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?
When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?
I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
so I received a new Nexus 6 device from T-Mobile for my girlfriend.
In our area unfortunately Wi-Fi calling is a must, so she went ahead and did both of the OTA updates. After doing the second update the phone was stuck optimizing apps, and then the screen wouldn't work...
So I then hooked the phone up to the PC and through ADB did the following commands
fastboot erase userdata
fastboot erase cache
That was supposedly the commands I had found on the internet to go ahead and factory reset the phone.
Now the phone is stuck at the balls swirling and it won't stop. Try and hold the power button down and the phone just restarts itself, won't shut down so I can't even get back into the recovery.
I tried to first load up a factory image before doing something silly like that but when I tried to run the command "fasboot oem unlock" it says I need to enable developer options in Android... which I couldn't get to anyways...
Can someone please help with this issue. Her old phone got stolen and now she has this one which is completely messed up.
Thank you for anyone who can help me!
none
You have to hold power and down on the bottom button, or since you have adb, you can do "adb reboot recovery". Push volume down first then power. After that you can enable MTP and toss a rom on the phone. Do a complete wipe with the exception of the internal storage ( I did storage one time accidentally, yuk) flash a ROM and you should be good
I can't even turn off the device at this point.... It is just stuck at the balls spinning and won't go any further.
When trying to shut the phone off the power button just restarts the phone, doesn't shut it down. Not sure what is going on.....
jwleonhart said:
I can't even turn off the device at this point.... It is just stuck at the balls spinning and won't go any further.
When trying to shut the phone off the power button just restarts the phone, doesn't shut it down. Not sure what is going on.....
Click to expand...
Click to collapse
It should shut down if hold the power button long enough. Takes like 20 seconds or so.
OK I'M BACK INTO RECOVERY.
Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?
When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?
I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.
jwleonhart said:
OK I'M BACK INTO RECOVERY.
Now can I erase the bootloader and everything and reload all of it without having the phone unlocked?
When I try and do "fastboot oem unlock" it comes back with an error and says "I Must have OEM Unlocked in Developer Options. That's great, but I can't get the phone to boot into android so what should I do at this point?
I don't want to try and erase everything and reload it just to find out i've seriously messed it up at this point, even though the silly thing doesn't load anyways.
Click to expand...
Click to collapse
As far as I know with stock recovery about all you can do is try to format cache and try to factory reset again. Otherwise will have to take back to T-Mobile and RMA. Make them update it. Lot of OTA updates have been failing.
I'm just curious to know if there is someway. Maybe I can force TWRP recovery or something like that on the phone by at least getting in the bootloader... There is a fix for bricking if it is like that.
Why the bootloader just doesn't come unlocked I will not understand. It would prevent motorola from having a heap of useless devices, as i'm sure probably even motorola themselves cannot fix the device.
Seems like a whole pile of sh*t if you ask me.
Anyone have any ideas? Worst part is T-Mobile won't ship a phone over the weekend either, so thats just 3 more days without a phone which is just wonderful.
jwleonhart said:
I'm just curious to know if there is someway. Maybe I can force TWRP recovery or something like that on the phone by at least getting in the bootloader... There is a fix for bricking if it is like that.
Why the bootloader just doesn't come unlocked I will not understand. It would prevent motorola from having a heap of useless devices, as i'm sure probably even motorola themselves cannot fix the device.
Seems like a whole pile of sh*t if you ask me.
Anyone have any ideas? Worst part is T-Mobile won't ship a phone over the weekend either, so thats just 3 more days without a phone which is just wonderful.
Click to expand...
Click to collapse
There is no way to flash a recovery without the bootloader unlocked. On these devices it is best to unlock bootloader first thing before trying to update so have some control if things go bad. Moto has the ability to reflash them like J-Tag. TMobile store may replace it.
Messed up part about T-Mobile is the fact this was an exchange for a stolen phone. They actually waived the insurance fee of $175 and the tax on the phone... which was extremely nice of them since I still owed about $350 on the LG G3 my girlfriend had.
So since the exchange was done over the phone or I should say since the new handset would bought over the phone the store won't replace it... it's weird they operate that way because the store should be able to replace anything that is sold via phone or internet and vice versa.
jwleonhart said:
Messed up part about T-Mobile is the fact this was an exchange for a stolen phone. They actually waived the insurance fee of $175 and the tax on the phone... which was extremely nice of them since I still owed about $350 on the LG G3 my girlfriend had.
So since the exchange was done over the phone or I should say since the new handset would bought over the phone the store won't replace it... it's weird they operate that way because the store should be able to replace anything that is sold via phone or internet and vice versa.
Click to expand...
Click to collapse
Yea. It a bad situation. We have seen a lot of them choke on the OTA flash. Best to unlock upfront and fastboot the updated factory image. You are always safe once it is unlocked.
Still begs the question as to why they don't just unlock the bootloader from the factory to avoid all this crap. I mean imagine how much money and time they would save if they just did it? I completely forgot about unlocking the bootloader even because I figured hey just OTA it and be done.... remember it's my girlfriend so I wasn't going to put some ROM on there that might have something broken or whatever... can't believe this **** though.
jwleonhart said:
Still begs the question as to why they don't just unlock the bootloader from the factory to avoid all this crap. I mean imagine how much money and time they would save if they just did it? I completely forgot about unlocking the bootloader even because I figured hey just OTA it and be done.... remember it's my girlfriend so I wasn't going to put some ROM on there that might have something broken or whatever... can't believe this **** though.
Click to expand...
Click to collapse
I understand. They look at unlocked bootloader as a security problem. It even tells you it disabled security when you flip the unlock switch. From the many OTAs we have seen brick it is best to just unlock even if running stock. Once it is up and running can always relock. Do not relock if have custom recovery or kernel tho. It will more than likely bootloop. I tried it for grins but made sure the unlock option was enabled and was able to unlock and reflash. Many have flashed new software and relocked before first boot to find out it bootloops and can't unlock again. Best to have TWRP so that if is locked have a adb/MTP option. We pretty much discourage OTA. I haven't tried but have seen a post that says must be locked to OTA. If that is the case you always have the chance of a bad OTA flash and end up same place you are now. With TWRP there are also OTA files that have been converted to flashable zip and can be flashed in recovery.
I had to get a new Nexus because I lost my previous one. Now I'm trying to root this one but I can't seem to get the OEM Unlock setting to work. I've rebooted it, factory reset it, enabled/disabled the option countless times, enabled/disabled USB debugging... nothing. Google doesn't seem to have an answer either. Anyone has any idea what's going on? Or if there's another way to unlock this setting?
Thanks for your time!
Just to clarify, are you actually attemping to unlock it? You have to first enable that option in developer settings, but you still have to put the phone in bootloader mode and run the command "fastboot oem unlock", then use the buttons on the phone to confirm it. I think all your data wipes first time you unlock your bootloader too so just be careful.
SilverSix said:
I had to get a new Nexus because I lost my previous one. Now I'm trying to root this one but I can't seem to get the OEM Unlock setting to work. I've rebooted it, factory reset it, enabled/disabled the option countless times, enabled/disabled USB debugging... nothing. Google doesn't seem to have an answer either. Anyone has any idea what's going on? Or if there's another way to unlock this setting?
Thanks for your time!
Click to expand...
Click to collapse
Depending the Android build installed, sometimes the option has been greyed out. Don't know why...
You said you tried to get the "OEM unlock" slider working... But did you try issuing the unlock command in bootloader?
Good luck...
Yeah, I'm aware it wipes your device. Also, don't burn me but I was using a Toolkit to start the process but I just gave up and did it the old fashioned way. After restarting into bootloader and sending the fastboot command it prompted the question to unlock it, so everything went smoothly.
Somewhere I had read that Android purposely locks OEM unlocking after n reboots, and I thought I was completely out of luck, but everything went smoothly. Thanks for your time!
Hello XDA, I hope that you could help me troubleshoot my Note 8 (N950F).
So it's been 7 days and oem unlock toggle has finally appeared.. The only issue is it is greyed out and unselectable.
When I got this device I wasn't able to see developer options by pressing build number (though I got the notification that it was enabled), I was only able to access the setting by downloading an app short cut for it via the play store and on initial launch it said developer options are disabled. But then second launch it worked. Idk if this is significant but maybe the country this is meant for disabled it? Regardless of the sim card being in/out the phone, it is still greyed out. Also, I was able to factory reset the phone through the settings after downloading an OTA (I did this in hopes of developer options being enabled about a week ago.)
I tried to boot into download mode but it seems I can't boot into it (following the steps only lead to a normal reboot, and when I select that option from the stock recovery or through adb, it only boots the phone up normally. I purchased the phone off of swappa, in brand new/like new condition. Any ideas? Thank you for your help.
Edit: added screenshots.
SM-N950F / DS here running Taiwan software BRI and I have the option maybe if you flash this firmware you'll get it.
Eddygraphic said:
SM-N950F / DS here running Taiwan software BRI and I have the option maybe if you flash this firmware you'll get it.
Click to expand...
Click to collapse
Thanks for the answer! However, I don't think I can flash firmware because I can not go into download mode, which is needed for odin to flash firmware
Negroid said:
Thanks for the answer! However, I don't think I can flash firmware because I can not go into download mode, which is needed for odin to flash firmware
Click to expand...
Click to collapse
That's weird I've never seen a Galaxy that can't enter download mode.
Eddygraphic said:
That's weird I've never seen a Galaxy that can't enter download mode.
Click to expand...
Click to collapse
Exactly. That's why I'm so concerned.
Have you logout your Samsung Account and Google account？sorry for my poor English.:crying:
Do you use any of the KNOX stuff? Did you do any factory reset?
Can you "clear data" on "settings" app? this would make the "developer option" menu hidden again. Then re-show it by tapping build number numerous time again. Hoping that OEM is now editable.
Hi, could you solve this problem? My Note 8 has the same problem and I have not found any solution :llorando:.
I would appreciate it if you can help me.
Hey,
I purchased a Samsung Note 8 (SM-N950F) a couple of years from Amazon.de. The phone was unlocked, since then new OS releases were really slow so I decided to download the Pie update from Sammobile and updated my phone via Odin. The phone is using official firmware and has never been rooted yet when I try to activate Google Pay I receive the following error; "Couldn't finish setup to pay in shop. This phone can't be used to pay in shops. This may be because it is rooted or altered in some other way."
I spoke to Samsung and told me to check a few things and they confirmed the phone is not rooted, I spoke to Google and they told me I should ask Samsung how to unlock the bootloader but Samsung said doing this would void my warranty. I'm a bit confused as to what to do, is there a stock pie rom I can use without voiding my warranty?
Thanks a lot, appreciate any help
Regards
p4rma
The only thig i can think of is that, the phone you've got has a CSC code of a region where Google Pay is not supported, or maybe you are living in a country that do not support Google Pay.
If you think I'm wrong, flash stock pie firmware.
Flashing stock offiicial binaries doesn't need your bootloader to be unlocked.
Thanks for the quick reply I will try this. Would Samsung have their own stock pie rom? Kinda wish I just waited for the pie update rather than flashing. Its annoying I can't use Netflix either as it says my device is not compatible.
I just checked and my bootloader is N950FXXU7DSJ1
Hey there,
I also faced the same issue when using GPay. I recommend trying these steps, might workout for you (it did for me):
Before doing this I recommend Backing your phone up, sometimes phone might erase user data but I didn't lose data.
1. Goto Settings > About Phone > Software Information > Build Number (Tap this thing 7 times). It should display a toast saying Developer options has been enabled.
2. Go back to Settings > Developer Options.
3. Turn on USB Debugging first, just in case.
4. See if OEM Unlock is turn on, if it is then turn it off.
5. Try turning it back on if it is turned off, you phone will reboot if you do so. Once rebooted, go back and turn it back off.
You shall be able to use Google Pay.
Note: These are the exact same steps that I did and it started to work for me.
As for changing CSC its a little complicated (by rooting its way easier but then you will lose Samsung Pay & some other Knox features). You will need to do a couple of steps and it also leads to erasing of user data.
If you don't wanna risk anything, why not try SPay. It might be supported in your country.
Unix_Dominator said:
Hey there,
I also faced the same issue when using GPay. I recommend trying these steps, might workout for you (it did for me):
Before doing this I recommend Backing your phone up, sometimes phone might erase user data but I didn't lose data.
1. Goto Settings > About Phone > Software Information > Build Number (Tap this thing 7 times). It should display a toast saying Developer options has been enabled.
2. Go back to Settings > Developer Options.
3. Turn on USB Debugging first, just in case.
4. See if OEM Unlock is turn on, if it is then turn it off.
5. Try turning it back on if it is turned off, you phone will reboot if you do so. Once rebooted, go back and turn it back off.
You shall be able to use Google Pay.
Note: These are the exact same steps that I did and it started to work for me.
As for changing CSC its a little complicated (by rooting its way easier but then you will lose Samsung Pay & some other Knox features). You will need to do a couple of steps and it also leads to erasing of user data.
If you don't wanna risk anything, why not try SPay. It might be supported in your country.
Click to expand...
Click to collapse
Thank you Unix_Dominator!!!!!!!!! This worked, I can now use Google Pay & Netflix
p4rma said:
Thank you Unix_Dominator!!!!!!!!! This worked, I can now use Google Pay & Netflix
Click to expand...
Click to collapse
I'm glad it worked out for you too!!!
Unix_Dominator said:
I'm glad it worked out for you too!!!
Click to expand...
Click to collapse
I noticed it has stopped working again but I'll try your method again. Did you have the issue or is yours pemanently fixed?
Thanks
p4rma said:
I noticed it has stopped working again but I'll try your method again. Did you have the issue or is yours pemanently fixed?
Thanks
Click to expand...
Click to collapse
It has been permanently fixed for me, I never faced any issue with GPay after that method (I don't use Netflix though). Could you also see if you phone is updated to the latest version, if so also check if your phone has a fix for Stagefright.
To check if you are vulnerable to that exploit download this app it will tell you Click Here . If it fails, try OEM unlock as off and see, might fix it.
I really hope this issue doesn't come back for you.
Hello all!
Recently I bought a Pixel 4 XL on ebay. Loving the phone, however it turned out to be from AT&T. When it arrived I had a lot of issues, the SIM I use on Spain wouldn't work, and the 2x camera didn't work as well. After a bit of research I find a way to fix those 2 problems, but now I want to flash magisk to improve motion sense gestures, however I can't unlock the Bootloader. I think if I can find where that information about the Bootloader is stored I could try to modify it through the computer. It must be somewhere on the phone, so if I find the file I can unlock it. If anyone has any idea, please let me know.
Thanks in advance
@mcl Enable oem unlocking. It's greyed out in your screenshot you posted. Try enabling developer options and USB debugging on phone, disable any lock screen you have set up, set lock screen to NONE in security settings on phone aaaannd change default USB configuration from "charging" to "transfer files" then plug it up to you computer with latest ADB and Fastboot installed and attempt to unlock your bootloader by typing in terminal: sudo adb reboot bootloader (enter) watch your phone close and if a small box pops up when you do this or when you first connect to PC pc
Checkmark it rreally quickly on your phone screen. That allows PC to communicate with your device, send commands, etc...If all has gone well up to now you should now be in "Fastboot mode" aka: bootloader mode on your phone screen. A black screen with "Fastboot mode" in red letters and the word "START" kinda in center of your screen on phone. Now just go back to terminal and type: sudo fastboot flashing unlock (enter) return to device use volume keys to go up or down and confirm unlocking bootloader by pressing power once on the "yes unlock bootloader" thingy. Soon as you push power to confirm bootloader unlock you will reboot automatically and you will bootloader unlocked. Keep in mind unlocking and locking your bootloader can and will factory reset your device. No pics or anything will be on phone, all will be wiped and there's no way to prevent that. Cheers.
If by some crazy situation something I've mentioned above does NOT work like I've said let me know and I'll help best I can. I use Linux Ubuntu on my laptop 18.04.5 LTS. I stopped using Windows MAAAANNNYYY years ago so I'm inexperienced when it comes to setting up adb and fastboot tools on Windows. I do know that the USB driver's used to always be a real pain in the ass to get right for me. I'd have to reboot by computer a few times and update them in device manager to get it working which I don't have to do anything using Ubuntu my PC just automatically sees my phones. Yay!!!
I hope this helps. Feel free to hmu any time. Remember im on central time in the USA.
To get your enable oem unlocking to become not stuck where it's greyed out like yours is you may have to factory reset your device before you do what I've mentioned above. Just factory reset in settings on your device but afterwards make sure you enable developer options and USB debugging and make sure you flip on the "enable oem unlocking" switch towards the top of developer options on your device
flash713 said:
@mcl Enable oem unlocking. It's greyed out in your screenshot you posted. Try enabling developer options and USB debugging on phone, disable any lock screen you have set up, set lock screen to NONE in security settings on phone aaaannd change default USB configuration from "charging" to "transfer files" then plug it up to you computer with latest ADB and Fastboot installed and attempt to unlock your bootloader by typing in terminal: sudo adb reboot bootloader (enter) watch your phone close and if a small box pops up when you do this or when you first connect to PC pc
Checkmark it rreally quickly on your phone screen. That allows PC to communicate with your device, send commands, etc...If all has gone well up to now you should now be in "Fastboot mode" aka: bootloader mode on your phone screen. A black screen with "Fastboot mode" in red letters and the word "START" kinda in center of your screen on phone. Now just go back to terminal and type: sudo fastboot flashing unlock (enter) return to device use volume keys to go up or down and confirm unlocking bootloader by pressing power once on the "yes unlock bootloader" thingy. Soon as you push power to confirm bootloader unlock you will reboot automatically and you will bootloader unlocked. Keep in mind unlocking and locking your bootloader can and will factory reset your device. No pics or anything will be on phone, all will be wiped and there's no way to prevent that. Cheers.
If by some crazy situation something I've mentioned above does NOT work like I've said let me know and I'll help best I can. I use Linux Ubuntu on my laptop 18.04.5 LTS. I stopped using Windows MAAAANNNYYY years ago so I'm inexperienced when it comes to setting up adb and fastboot tools on Windows. I do know that the USB driver's used to always be a real pain in the ass to get right for me. I'd have to reboot by computer a few times and update them in device manager to get it working which I don't have to do anything using Ubuntu my PC just automatically sees my phones. Yay!!!
I hope this helps. Feel free to hmu any time. Remember im on central time in the USA.
To get your enable oem unlocking to become not stuck where it's greyed out like yours is you may have to factory reset your device before you do what I've mentioned above. Just factory reset in settings on your device but afterwards make sure you enable developer options and USB debugging and make sure you flip on the "enable oem unlocking" switch towards the top of developer options on your device
Click to expand...
Click to collapse
Hey thanks for the very detailed guide, however I run into a few problems. First I factory reset(also, after that it wouldn't allow me to enable OEM unlock) the device and disable any lock screen, as you told me and set the usb configuration to data transfer. Later I enable USB Debugging and checked the box to allow my computer to connect to the phone. Finally I run the command to reboot into the boot loader, which worked but the 2 command, to unlock the bootloader show an error(see screenshot). Any idea what could have happened?
I tried this on my MacbookPro 13" Late 2013 with Catalina and the latest version of ADB from google. The phone is running android 11, with the July security Patch.
#mcl said:
Hey thanks for the very detailed guide, however I run into a few problems. First I factory reset(also, after that it wouldn't allow me to enable OEM unlock) the device and disable any lock screen, as you told me and set the usb configuration to data transfer. Later I enable USB Debugging and checked the box to allow my computer to connect to the phone. Finally I run the command to reboot into the boot loader, which worked but the 2 command, to unlock the bootloader show an error(see screenshot). Any idea what could have happened?
I tried this on my MacbookPro 13" Late 2013 with Catalina and the latest version of ADB from google. The phone is running android 11, with the July security Patch.
Click to expand...
Click to collapse
Honestly I have no idea. What I know is Linux and what's worked for me. My first assumption is that adb and fastboot need to be updated to the latest release if they are not at this time. That error you are showing in terminal sounds like something is wrong either maybe in your USB cable connecting to your PC or it needs to be updated ooorrr it's some sort of USB driver issue. Unless we are both crazy and somehow your device was already rooted and has an unlocked bootloader and that's how it was when you purchased it used online.. Download a root checker app and see what it says maybe. Also try booting stock recovery and factory reset front it and then reboot and see if anything changes...I know absolutely NOTHING about MacOS or OSX or anything otter than Linux because that's what I've used for eight or nine years now. I'm attaching a picture of my current updated adb and fastboot tools to show what latest release is. Maybe try different ports and USB cables just to see if anything changes. You are running the bootloader unlock command as root correct?
Adb and fastboot latest version: 31.0.3-7562133
I updated mine yesterday to that version from here: https://developer.android.com/studio/command-line/sdkmanager
You are doing everything exactly how it shows here:: https://www.xda-developers.com/google-pixel-4-root-magisk/ ?
and using the latest adb and fastboot on PC? Does Mac have to have any extra USB driver's like Windows needs to allow fastboot and adb to work or.no? I guess you would know that just type : sudo adb devices (enter)with phone plugged in and on. Maybe reboot bootloader/fastboot mode and run: fastboot devices (enter) and see if your terminal replies with your phones serial number in your terminal? If it does not than something isn't correctly setup because this should work. Did you use homebrew to setup platform tools on your Mac or no? Usually when I can't figure something ike this out it's the most random basic thing like a reboot or something and BOOM it works. Try running the commands again from your PC and see if anything happens. If you can type ./adb devices then hit enter while you are plugged in and slap a pic up of what it tells you like you did before. This is all stuff I would do if I were in the situation that you're in. I'm going to read up more on Mac now. You said you factory reset your device in settings on phone and the greyed out "enable oem unlocking" didn't change to where you can tap the switch and choose to either enable it or not? If it did not change after factory reset and maybe trying factory reset in stock recovery then it sounds like something else could be wrong with your device. I believe you will figure it out. When you did the while process did you ever checkmark a pop up box on phone screen whole you were plugged in to your PC??
Hey!
Ok so first I downloaded the latest ADB for Mac, but I am unsure of the version I have of Fastboot. Do I need to update it on the phone or download something else? What I did was download the latest version of the SDK from Google to my Mac as you show me on the screenshot, and on their webpage they say I don't need to do anything else, like installing USB drivers on windows. Also if I run Fastboot devices command I can see my phone on the terminal. The cable is working I think, but I may try to change it just in case and also change the port I am using. Also I downloaded and app to check if the device is rooted, and unfortunately it isn't. I will boot into recovery and try to do a factory reset from there, but I don't believe it will work as I believe I already try that before.
The commands I run correct, just copy and paste what you wrote before and the computer asked me my user password. However I didn't use homebrew at any moment, directly downloaded the SDK from google and got a zip file, then extracted it to my desktop and open a terminal window, then use cd to get to that folder directory as I used to do in my Windows PC and start using the commands. Until now it worked great because in order to get my SIM working I needed to use ADB to uninstall an app that came with phone, otherwise my SIM wouldn't work, as theoretically the phone should only accept only AT&T SIM, but I am currently using a Vodafone SIM. Also I am leaving a screenshot of what you asked me.
Yeah after factory reset I doesn't allow me to enable OEM Unlock, still grey out.
Finally yes, when I plugged my phone into the computer I got a window asking to allow the computer to connect to phone to debug, and I allow it.
Sooo here is what I think is happening. This phone was bought by someone at an AT&T store. Then the guy sold the phone and I ended up buying it. The problem, according to my findings, are that carriers usually lock down the bootloader and for you to get it unlocked you need to talk with them. Obviously I can't do that, as I would have to do an international call, and I don't even know if the buyer end the payment of the phone. I already got into AT&T webpage and try to get the phone unlock but get always and error. So researching more I found a command that you can use on Fastboot mode, "Fastboot flashing get_unlock_ability"(enter) and the result I got was 0. According to this page, if you get 0 means you need to go on settings and enable OEM unlocking, which changes the value from 0 to 1. So what I need to do is to find where this info is stored, which I suppose is on the bootloader partition, as on Fastboot mode it was able to tell me the value. Once I find it I just need to change it to 1, and then I would be able to unlock the bootloader.
Also thanks for all the help until now, I really appreciate it
I may try this on other OS just in case. Do you know if I can do this on Kali Linux? I already have it download ed but never try it.
#mcl said:
I may try this on other OS just in case. Do you know if I can do this on Kali Linux? I already have it download ed but never try it.
Click to expand...
Click to collapse
Pretty sure you can. I've never used Kali , yet but I've used ARC, Morrodoca, Ubuntu, Mint and Fabian and tried a few of the super private distros as well. Pretty cool! Linux rules and is made for this.
I almost said something about carriers encryption bootloader's on devices when we started this but idk I assumed it was a factory unlocked unit. I've had to repeat commands more than once before and things have ended up working. Worth a shot.
I say if you can't get it sell it online and grab a factory unlocked model. If the carrier encrypted the bootloader I don't believe it's possible to get it out of that without their code ever used to do it. Then again I do recall another Pixel model that Google was actually sending users refurnished units that had encrypted bootloader's. That would have really pissed me off. I believe Pixel 2/2XL was that way. But the Pixel 2XL/2 that Verizon sold , Verizon locked the bootloaders and for a long time there was no possible way to get around it. I recall reading many posts all over about people buying them and being told they were unlocked Pixels only to discover later they had encrypted bootloader's and Verizon did it. Shortly after this someone on XDA found a way to bypass it and unlock bootloader and root rge Verizon encrypted models but the phones had to be on a specific older firmware and if they'd been updated past it it didn't work. I'll go find this thread and link you. May have some good info but unless you come up with a back to get around it if bootloader has been locked bt carrier I believe it's a no go. Also careful because messing with encrypted things can cause your device ti bootloop and seeing how your NOT bootloader unlocked that wouldn't be good if that happened. I'll go find this link to what I'm referring to. Brb.
Here was the work round for Verizon for a while on Pixel 2 that had been carrier bootloader locked: https://www.xda-developers.com/how-to-unlock-bootloader-verizon-google-pixel-xl-running-android-10/
Actually this is Pixel 2XL, was P2 work around for this: https://forum.xda-developers.com/t/...-google-ver-refurb-devices-look-here.3763443/
Pixel 2XL some users report they had to be connected to the net to toggle their allow oem unlocking switch in dev options. On 4XL one of the "How to Root, unlock .." threads says if it's greyed out that factory resetting is mandatory to allow the ability to enable oem unlocking switch.. A couple people claimed once they reset they could flip it. Also I have also read where people used different bootloop unlocking terminal commands and they worked. On 4xl and older Pixies. How long have you had fastboot already installed to your MacBook? Only reason I ask is they must be manually updated or sometimes will not work right. I've had that happy once. Linux has a very similar adb and fastboot tools install as Mac does. I did this process I'm about to mention yesterday to get my adb and fastboot updated because I saw it was on a previous version. I just grab the adb and fastboot from my screenshot from like I posted back some posts ago here then go to where I have adb and fastboot installed already open terminal where I've downloaded and extracted fastboot and adb on PC and reinstalled adb and fastboot using these commands:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin (Enter)
sudo mkdir -p /usr/local/lib64 (enter)
sudo install lib64/libc++.so /usr/local/lib64 (enter)
Then make sure it did it's thing and updated property. sudo adb --version (enter)
sudo fastboot --version (enter)
And it showed newer version of both so done. I use Nathanchnace's Pixel 2xl guide to learn this at first from here in his op:
[GUIDE] Unlock/Flash/Root for the Pixel 2 XL (taimen)
Introduction Hello everyone, this is a guide to assist you with customizing your Pixel 2 XL! I will be going over installing fastboot and adb, unlocking your bootloader, how to flash the factory images for clean flashes and upgrades, and how to...
forum.xda-developers.com
flash713 said:
Pretty sure you can. I've never used Kali , yet but I've used ARC, Morrodoca, Ubuntu, Mint and Fabian and tried a few of the super private distros as well. Pretty cool! Linux rules and is made for this.
I almost said something about carriers encryption bootloader's on devices when we started this but idk I assumed it was a factory unlocked unit. I've had to repeat commands more than once before and things have ended up working. Worth a shot.
I say if you can't get it sell it online and grab a factory unlocked model. If the carrier encrypted the bootloader I don't believe it's possible to get it out of that without their code ever used to do it. Then again I do recall another Pixel model that Google was actually sending users refurnished units that had encrypted bootloader's. That would have really pissed me off. I believe Pixel 2/2XL was that way. But the Pixel 2XL/2 that Verizon sold , Verizon locked the bootloaders and for a long time there was no possible way to get around it. I recall reading many posts all over about people buying them and being told they were unlocked Pixels only to discover later they had encrypted bootloader's and Verizon did it. Shortly after this someone on XDA found a way to bypass it and unlock bootloader and root rge Verizon encrypted models but the phones had to be on a specific older firmware and if they'd been updated past it it didn't work. I'll go find this thread and link you. May have some good info but unless you come up with a back to get around it if bootloader has been locked bt carrier I believe it's a no go. Also careful because messing with encrypted things can cause your device ti bootloop and seeing how your NOT bootloader unlocked that wouldn't be good if that happened. I'll go find this link to what I'm referring to. Brb.
Here was the work round for Verizon for a while on Pixel 2 that had been carrier bootloader locked: https://www.xda-developers.com/how-to-unlock-bootloader-verizon-google-pixel-xl-running-android-10/
Actually this is Pixel 2XL, was P2 work around for this: https://forum.xda-developers.com/t/...-google-ver-refurb-devices-look-here.3763443/
Click to expand...
Click to collapse
OK thanks! Yeah I saw a few things only about the Pixel 2 Verizon case, but I am going to have a deep look into it. I can't sell this phone and buy an unlocked version, I bought this one because it was over 100 euros cheaper than what I could found here on Europe, so that's not an option.
Also, If I manage to use a Vodafone SIM on this AT&T phone without unlocking I am confident I will manage to find a way to fix the locked bootloader. It may take time and effort, but I will keep trying.
Right now I found there are ways to get root without unlocking the bootloader, its safer but posible. And if I get root access I am confident I would be able to unlock the bootloader. Anyway thanks for all!!!
flash713 said:
Pixel 2XL some users report they had to be connected to the net to toggle their allow oem unlocking switch in dev options. On 4XL one of the "How to Root, unlock .." threads says if it's greyed out that factory resetting is mandatory to allow the ability to enable oem unlocking switch.. A couple people claimed once they reset they could flip it. Also I have also read where people used different bootloop unlocking terminal commands and they worked. On 4xl and older Pixies. How long have you had fastboot already installed to your MacBook? Only reason I ask is they must be manually updated or sometimes will not work right. I've had that happy once. Linux has a very similar adb and fastboot tools install as Mac does. I did this process I'm about to mention yesterday to get my adb and fastboot updated because I saw it was on a previous version. I just grab the adb and fastboot from my screenshot from like I posted back some posts ago here then go to where I have adb and fastboot installed already open terminal where I've downloaded and extracted fastboot and adb on PC and reinstalled adb and fastboot using these commands:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin (Enter)
sudo mkdir -p /usr/local/lib64 (enter)
sudo install lib64/libc++.so /usr/local/lib64 (enter)
Then make sure it did it's thing and updated property. sudo adb --version (enter)
sudo fastboot --version (enter)
And it showed newer version of both so done. I use Nathanchnace's Pixel 2xl guide to learn this at first from here in his op:
[GUIDE] Unlock/Flash/Root for the Pixel 2 XL (taimen)
Introduction Hello everyone, this is a guide to assist you with customizing your Pixel 2 XL! I will be going over installing fastboot and adb, unlocking your bootloader, how to flash the factory images for clean flashes and upgrades, and how to...
forum.xda-developers.com
Click to expand...
Click to collapse
The SDK I downloaded this week, Monday I think, so it should be up to date, but I will make sure to check if this is the case. If you get any idea on how to unlock the bootloader, please let me know
Also if anyone was able to unlock a Pixel 4/Pixel 4 XL from any carrier, let me know how you did, maybe I can replicate the process and unlock my bootloader too!
#mcl said:
Also if anyone was able to unlock a Pixel 4/Pixel 4 XL from any carrier, let me know how you did, maybe I can replicate the process and unlock my bootloader too!
Click to expand...
Click to collapse
@#mcl
Not gonna happen. Sorry to hear you got a carrier locked AND bootloader locked phone. Unfortunately there is nothing you can do. There are some shady online unlockers that claim to be able to do this remotely (remote unlock) but you will probably be ripped off.