Related
hi all ... am facing a BIG problem ... was using a tm G1 from Europe (RC7) version which i bought from the local market .. it was probably used by someone in UK but now its here and we could use it with any local sim. ...
i tried to gain root access to the phone by following instructions from the site
http://coolpstuts.blogspot.com/2009/07/how-to-mod-root-jailbreak-your-g1.html
now once the phone restarted after the innitial updation the phone naturally wanted me to sign into my google account (which im assuming is the regular gmail account) but all the access points are from TMobile operators and even if i try to change the access points to the ones of my local carrier it wont connect... as if there is no internet connection.
now the situation is that iam stuck while everytime i restart the phone it asks me to signin to my gmail account and i cant do that since i have a different operator. I need to UnLock the phone to other operators i believe so that it can read my SIM ....
Please HELP !!!
so do you have root access or not? if you do have root access then you can either flash a rom that is ADP based which will allow you to skip the initial setup or, go to this thread and
download file from the second post
remove .zip extension
place file on the root of you sdcard (the upmost folder)
boot into recovery (home and power)
go to the recovery console
press enter
type mount /system
then type mount /sdcard
then type cp /sdcard/apns-conf.xml /system/etc if the cp command will not work substitute it with mv
finally type reboot
if this method doesn't work then just flash an ADP based rom.
if you do not have root then look at this thread.
shoeibyarsheikh said:
now once the phone restarted after the innitial updation the phone naturally wanted me to sign into my google account (which im assuming is the regular gmail account) but all the access points are from TMobile operators and even if i try to change the access points to the ones of my local carrier it wont connect... as if there is no internet connection.
now the situation is that iam stuck while everytime i restart the phone it asks me to signin to my gmail account and i cant do that since i have a different operator. I need to UnLock the phone to other operators i believe so that it can read my SIM ....
Please HELP !!!
Click to expand...
Click to collapse
If you insert a non-T-Mobile SIM into a locked G1, it will present a lock screen before it shows anything else. So I am guessing your G1 is already unlocked? You just need to press menu at the Google sign-in screen and enter a new APN. Remember to open the menu and tap save when you are done entering the APN info.
shoeibyarsheikh said:
now the situation is that iam stuck while everytime i restart the phone it asks me to signin to my gmail account and i cant do that since i have a different operator. I need to UnLock the phone to other operators i believe so that it can read my SIM ....
Please HELP !!!
Click to expand...
Click to collapse
You only have to sign in to Gmail once after the initial flashing of the rom. Now, you phone HAS to be unlocked in order for you to even get to the sign-in screen with non-T-mobile SIM. Sounds like all you need is APN Settings from your provider. Once you have those, hit menu button at the sign in screen and put them in. You should be good to go.
Good luck, let us know how it turns out.
wow guyz it worked.... cant thank you much !! i just threw in the correct settings and it went all good
my current situation is that i added "DREAIMG.NBH" and updated the phone with the file. ..
the second portion of the update was to reboot and than do the telnet thingy which i didnt do as of the moment .... this i was doing to gain ROOT access to the phone ... do you think that i should complete the TELNET portion of the update as well and than continue with anything or is there any way to upgrade to cupcake 1.5 (my ultimate goal) without gaining the root access ?
shoeibyarsheikh said:
wow guyz it worked.... cant thank you much !! i just threw in the correct settings and it went all good
my current situation is that i added "DREAIMG.NBH" and updated the phone with the file. ..
the second portion of the update was to reboot and than do the telnet thingy which i didnt do as of the moment .... this i was doing to gain ROOT access to the phone ... do you think that i should complete the TELNET portion of the update as well and than continue with anything or is there any way to upgrade to cupcake 1.5 (my ultimate goal) without gaining the root access ?
Click to expand...
Click to collapse
If you just want to update to 1.5 without gaining root, find a T-Mo EU update.zip file and run it in the recovery.
although the phone is unlocked (as per the experience) but if (lets say) i do update the phone to 1.5 without the root gain ... will it lock the phone again or something (asking me to enter only T-Mob SIM only) ??
shoeibyarsheikh said:
although the phone is unlocked (as per the experience) but if (lets say) i do update the phone to 1.5 without the root gain ... will it lock the phone again or something (asking me to enter only T-Mob SIM only) ??
Click to expand...
Click to collapse
No, there is probably no way to re-simlock a phone once it has been unlocked. Remember that the state of the simlock is stored internally in the baseband processor and is not affected at all by what you do on the main processor or in the accessible memory spaces.
thanks alot jashsu and others ... will bug u guyz laterz for other stuff ...
Hi All,
Having trouble with my G1 (see my post below). The only remedy I see is to get past the opening tmobile Google sign up and get to the real home screen. From there...
I tried to do it through wifi but I don't have an att data plan or an unlocking code for my ATT SIM. (I did put ATT APN settings)
THoughts appreciated?
Regards, PK
BTW, why are my posts not in bold?
Your posts are not in bold until you have new reply to it.
Why would you need att plan to use your wi-fi? That part I don't get but neverless
You will need to get that unlock code to use your att sim card, there's no way around it, period.
If you want to use your phone on wi-fi with no sim card and you have root access then you can just go to this thread and follow the directions. If you don't have root access then then you need to downgrade to RC29 (using DREAIMG.nbh) and then follow the info in this thread. After it's all said and done you can either wait for OTA of the official 1.6 Donut or you can root and install the rom of your choice.
Good luck
very good, Thanks,
I did a successfully flash (I believe, sorta,... "bla, bla installation succesfull") with R29 DREAIMG.nbh from unlockr" .com" I say I believe because the only way I can tell is I can type in return, reboot,return and it reboots +it's a whole new opening screen with the Google runaround . The iffy part of "sorta...sucsesfull" of the flash is, I no longer have any access to any SD card and no ability to sync with PC.
As to unlocking the SIM card, no doubt, It will have to be done. Of the some 25 odd android websites I've been pouring over, theres no definitive statements as to just when in the process it should be done. I also don't know which of these guys are reputable Given my track record of half bricking this thing with my first flash, I'm going forward with a good dose of timidity. I'll take your comment as a go.
As far as wifi Google registration with out SIM card, I appreciate the link. I'll have to study it more but, I can't link to to my P.C. right now. I futzed with everything & follow instructions & prescriptions from everywhere for everything: adb, loaded new usb drivers, HTC drivers, android SDK-3, HTC sync (with supposedly corrected vista HTC drivers), Droid explorer, etc all day till 2 in the morning and the phone just isn't "taking calls", (or Sd's for that matter). But I'll keep trying.
Anyway thanks again for the straightening me out and the links.
Regards, PK
P.S. You can safely assume I tried everything every-which- way to get it to read SD's, that rebooting PC and the phone reformatting SD's, trying different capacities, buying another virgin card, popping the battery in and out,,, all a zillion times. Same goes for syncing. NADA.
thanks for ur information
I wanted to turn my HTC Dream Dev phone into a Wifi Tether. I followed the Wiki article and did not realize that I had flashed a T-Mobile .nbh file. I want to restore the Dev Phone back to its original state and remove T-Mobile from my Dev Phone. I removed the T-Mobile.nbh setup file from my SD card, but the device is still booting the T-Mobile Android launch.
It is a 2008 European HTC Dream. I have loved this phone for years. Please help me.
I have searched google for hours now, and no tangible help. I am not a computer science expert and perhaps my search was amateur at best.
What you might need to know:
I had no recovery, backup.
I have AT&T gophone SIM in my Dev before I flashed it.
The Link:
Wiki: -.- cannot post
Question: How do return back to the orginal Dev device and remove the TMOBILE .nbh boot
You can try orange.nbh and place it on your sdcard. Boot while holding camera just like your dreaming .nbh
If thisnt isn't good enough you can either
Flash dev rom from fastboot (must have proper spl)
Flash dev rom from recovery (may not work with curent recovery probably need to flash amonra etc)
By the way you can find the official developers rom (presumibly what you had in xda - search in the dev threads) if you can't find it ill post a link next time I'm by a computer)
Not sure why you want to go back to this as there are many other roms far superior to that old dev rom
Sent from my HTC Vision using xda premium
You can try orange.nbh and place it on your sdcard. Boot while holding camera just like your dreaming .nbh
If thisnt isn't good enough you can either
Flash dev rom from fastboot (must have proper spl)
Flash dev rom from recovery (may not work with curent recovery probably need to flash amonra etc)
By the way you can find the official developers rom (presumibly what you had in xda - search in the dev threads) if you can't find it ill post a link next time I'm by a computer)
Not sure why you want to go back to this as there are many other roms far superior to that old dev rom
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I will address the other suggestions tomorrow with proper response.
I do not know anything about programming or modification of cellular technology, however I believe working 10 hours on a problem qualifies me to have a simple understanding.
I tried using the orange.nbh, however the Firmware, Radio and possible other additions did not match the current setup.
I cannot utlize FastBoot on my phone because I do not have proper tutorial information, moreover I tried <enter>something.adb.enable 1<enter> that too failed. I will look for the dev rom first thing in the morning. I have tried to learn how to use fastboot via youtube videos and large forum threads. I hope this will help me tomorrow.
There are better rom(s) out there? Please suggest, I just want to remove a provider restriction from my unlocked Dev phone. I should have never have followed the Wiki. I was happy with no provider and using various gophone SIM cards when plans became cheaper.
I just want this stifling .nph file off my system and back to original dev. If I am feeling bold, I will try to wifi tether my dev phone again.
Thank you for such a quick reply. I am very much in your debt.
Once your phone is sim unlocked (yours was a dev phone so it was) it always will be. The reason changing roms sometimes won't allow you to use other providers is a problem with he apn. Settings and you will have to mannualy change them. Find any rom you like and if your sim won't work then you need to change those apn settings.
Sent from my HTC Vision using xda premium
After Flash, my phone reads as:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
Where do I find and how do I install the proper credentials, so my phone is back to the Orange ROM or the ROM you recommend. Thank you again.
I know my phone is not rooted, I tried just downloading a WiFi tether app weeks ago and nothing happened.
Well it was rooted as a dev phone, by flashing the dreaming.nbh you unrooted your phone and downgraded your firmware, radio, spl, and recovery. You now need to upgrade all of this. Sim is still unlocked though.
Continue following those steps in the wiki, but it looks like you may need to flash dreaming.nbh again for it looks as if you update your radio since the first flash
Sent from my HTC Vision using xda premium
I cannot access any normal user interface. I do not have any access to the phone, is it still possible to install fastboot and update without accessing the basic interface on the phone? i.e Settings.
Step 1: Flash DREAIMG.nbh
Step 2: Flash Firmware
Step 3: Flash Radio
Step 4: Flash SPL
Step 5: Flash Recovery
Please edit my terminology if not correct. I know nothing about computers and I am about to pull my hair out. The guides are for someone who has experience with computer software installation from a terminal. I do not.
Would it be better to just get a T-Mobile SIM card and work from there?
My Windows 7 OS is not recognizing my HTC G1 as a mass storage device. Error in reading device properties, may be corrupt.
Windows isn't recognising phone because you need the proper drivers. If you don't want to use adb and fastboot that's ok you don't have to.
Steps-
Put files needed on root of sd card
All will be found in that cyanogen how to root wiki
Dreaming.nbh, radio, danger spl, and amonra recovery
1 boot phone while holding camera (it will find dreming.nbh and say yes after about 5min it will finish and say done
2 boot into phone normally, sign in, download telnet from market
From home screen hit "enter" twice then type "telnetd"
Then open telnet and hit enter then type "flash_image recovery /sdcard/recovery.img
When done you get ##
3boot into recovery holding home while powering on here you can flash radio hboot and rom
4 flash radio
5 flash spl
6 flash rom (and gapps if needed)
Your done!
Sent from my HTC Vision using xda premium
2 boot into phone normally, sign in, download telnet from market
Click to expand...
Click to collapse
That Wiki is what caused the problem in the first place. I have been going back and forth between this guide, the fastboot guide, and the xda-develop guide.
SDK manager does not recognize G1 as the mass storage device. It does not recognize it at all, I cannot run the bypass WiFi. I do not have a T-Mobile provider account and cannot log in to GMail via AT&T SIM.
I have been doing this song and dance for the last 10 hours. I am really frustrated. Should I just buy a T-Mobile SIM card?
http://forum.xda-developers.com/showthread.php?t=1417962
heres an old post that a couple of us @ xda helped with your same problem
it has all the steps needed within it (including a how to without tmobile sim)
i have some school work to do right now but if i get some more time ill check back
for now read through it and youll be happy - everything is explained throughout - ask me again if you need more help
http://wiki.cyanogenmod.com/wiki/Google_Login_via_a_WiFi_Connection
I was able to follow the help on the thread you previously posted, however on p. 4 there is a slight problem. Both the SDK Manager and FastBoot are installed on my computer. I also installed HTCSync.
Location:
C:\android-sdk-windows
C:\android-tools
However, the computer still does not recognize my HTC G1. I have included in PATH ;C:\android-tools
The terminal does not recognize any location. I have Windows 7 OS.
If you didn't manually point to the drivers windows may have guesses so try plugging the phone in and seeing which driver pops up and then change it to the proper one. Also if you type adb from the cnd make sure it looks good, if it says no such directory you didn't set the patch correctly
Sent from my HTC Vision using xda premium
If you didn't manually point to the drivers windows may have guesses so try plugging the phone in and seeing which driver pops up and then change it to the proper one. Also if you type adb from the cnd make sure it looks good, if it says no such directory you didn't set the patch correctly
Click to expand...
Click to collapse
Run > CMD > ABD
The terminal closes and does not stay open.
Direct file location of abd.exe also force closes.
If this is normal, please let me know.
Not normal, you need to change the enviromental variables. If you can't find the right value then erase what you put in the path. Then go to folder adb is in, hold down shift and right click, then click open cmd here. Type adb
A long list should now pop up - that's good
Sent from my HTC Vision using xda premium
Not normal, you need to change the enviromental variables. If you can't find the right value then erase what you put in the path. Then go to folder adb is in, hold down shift and right click, then click open cmd here. Type adb
A long list should now pop up - that's good
Click to expand...
Click to collapse
1.) PATH addition deleted
2.) Open CMD
I will post if I have additional problems!
C:\android-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Starting: Intent { action=android.intent.action.MAIN comp={com.android.settings/
com.android.settings.Settings} }
$
C:\android-tools>
The HTC G1 has a black background.
No SIM card.
No SIM card in phone.
date/time
Emegency Call.
Should I reflash DREAIMG.nbh and reboot via recovery. I.E Step 1 in this tutorial. http://forum.xda-developers.com/showthread.php?t=1098899
When in cmd and adb is working (it is by the way) type adb devices
If it shows your serial number than your in and can move on if not you need to update drivers
Sent from my HTC Vision using xda premium
C:\android-tools>adb devices
List of devices attached
HT851N003562 device
C:\android-tools>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
$ am start -a android.intent.action.MAIN -n com.android.settings/.Settings
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
Starting: Intent { action=android.intent.action.MAIN comp={com.android.settings/
com.android.settings.Settings} }
$
C:\android-tools>
Click to expand...
Click to collapse
HTC G1 online~
Now that I have successfully updated my phone.
Dream PVT 32b SHIP S-on
HBOOT 1.33.0013d (drea10000)
CPLD-4
RADIO 2.22.28.25
OCT 21,2009,22:33:27
What ROM do you recommend I should get?
I cannot thank you enough for you assistance. I really do appreciate everything you have done for me. I think I passed this crash course.
I have done what was on the HTCDev website, no luck. I have done all I can and haven't been able to succeed. I'm ranging across a plethora of problems, sometimes I can't get the phone to be recognized through fastboot, other times I can't get the authorization to work the chmod 777 command to allow for access, most of the time I just keep getting the "command not found" or things of that sort. I'm getting so furious at this process because this is the ONLY phone i've ever had any problem trying to root and I can't even get past the damn bootloader. Wtf?! Doesn't anyone have a program or something I can use besides have to screw around with Terminal constantly?
Model: opcv1
Software: 1.48.652.2
Android 4.4.2
HTC Sense 6.0
Provider: Boost Mobile
GGwhatYoNameIs said:
I have done what was on the HTCDev website, no luck. I have done all I can and haven't been able to succeed. I'm ranging across a plethora of problems, sometimes I can't get the phone to be recognized through fastboot, other times I can't get the authorization to work the chmod 777 command to allow for access, most of the time I just keep getting the "command not found" or things of that sort. I'm getting so furious at this process because this is the ONLY phone i've ever had any problem trying to root and I can't even get past the damn bootloader. Wtf?! Doesn't anyone have a program or something I can use besides have to screw around with Terminal constantly?
Model: opcv1
Software: 1.48.652.2
Android 4.4.2
HTC Sense 6.0
Provider: Boost Mobile
Click to expand...
Click to collapse
Did you turn the USB debugging mode on in the phones settings? You know you have to enable developer options?
MrMike2182 said:
Did you turn the USB debugging mode on in the phones settings? You know you have to enable developer options?
Click to expand...
Click to collapse
Yeah, i've done that.
if your on linux,you need to do sudo fastboot whatever. post some errors,ill try and help 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.