Related
Hello friends, i have Sm-n950f device. Yesterday, i tried to root my device. I successfully installed TWRP recovery but afterwards, i got error that only official binary allowed to be installed and i was stuck on samsung logo. Then with odin i install official firmware again and i found oem unlock missing. I tried some methods to get it back by setting up date 8 days back but nothing happen. Now my device have 1 july security pacth and its again showing update for august patch. What should i do??
Thanks
cheemak said:
Hello friends, i have Sm-n950f device. Yesterday, i tried to root my device. I successfully installed TWRP recovery but afterwards, i got error that only official binary allowed to be installed and i was stuck on samsung logo. Then with odin i install official firmware again and i found oem unlock missing. I tried some methods to get it back by setting up date 8 days back but nothing happen. Now my device have 1 july security pacth and its again showing update for august patch. What should i do??
Thanks
Click to expand...
Click to collapse
Maybe try this and see if it works for you
https://forum.xda-developers.com/galaxy-note-8/how-to/oem-unlock-quick-fix-highly-recommend-t3791984
I tried these steps whole day but it did not work for me.,,, any other suggestion please?
thanks for your reply
cheemak said:
Hello friends, i have Sm-n950f device. Yesterday, i tried to root my device. I successfully installed TWRP recovery but afterwards, i got error that only official binary allowed to be installed and i was stuck on samsung logo. Then with odin i install official firmware again and i found oem unlock missing. I tried some methods to get it back by setting up date 8 days back but nothing happen. Now my device have 1 july security pacth and its again showing update for august patch. What should i do??
Thanks
Click to expand...
Click to collapse
If the workaround to bring back the oem unlock toggle isn't working, then you will have to wait the 7 days for it to appear. Then you can toggle it and try installing twrp again. You likely missed a step in the process last time which resulted in 'jail'.
cheemak said:
I tried these steps whole day but it did not work for me.,,, any other suggestion please?
thanks for your reply
Click to expand...
Click to collapse
You could try my method here - https://forum.xda-developers.com/showpost.php?p=76962872&postcount=28
I tried this method as well but without sim card and it didn't work,,, is sim card important to insert? Now my device running time is about 20 hours so I don't want to restart my device if I restarted then it again come back to 0. What should I do not getting??
indercheema14 said:
I tried this method as well but without sim card and it didn't work,,, is sim card important to insert? Now my device running time is about 20 hours so I don't want to restart my device if I restarted then it again come back to 0. What should I do not getting??
Click to expand...
Click to collapse
Reboots don't affect the 7 day timer. Your uptime timer will reset, but the 7 day timer for OEM unlock is server-side.
sefrcoko said:
Reboots don't affect the 7 day timer. Your uptime timer will reset, but the 7 day timer for OEM unlock is server-side.
Click to expand...
Click to collapse
Ok thank you for information,, i am getting OTA update for august security patch,, should i install this update or not? i want to root my device and install custom rom but still waiting for oem button to appear in developer option? what you suggest?
cheemak said:
Ok thank you for information,, i am getting OTA update for august security patch,, should i install this update or not? i want to root my device and install custom rom but still waiting for oem button to appear in developer option? what you suggest?
Click to expand...
Click to collapse
I'm not sure but I think that installing the update could restart the 7-day wait period. If you want to root as fast as possible then it's probably safer to not install the update for now and just wait for the OEM Unlock toggle to appear. There is also a stick thread here with a workaround to skip the 7 day waiting period, but it didn't seem to work for everyone (although it did work for me the one time I tried it).
Any luck///need help too.
Any luck with getting the OEM to show?
I've tried them all waiting 7 to 2 weeks, factory reset change date at setting up insert sim card and no luck. I got my note 8 at soon as it came out so maybe it has something to do with it? I want to root it so bad it cant because of no OEM. Any new information would be great!
dandel0074 said:
Any luck with getting the OEM to show?
I've tried them all waiting 7 to 2 weeks, factory reset change date at setting up insert sim card and no luck. I got my note 8 at soon as it came out so maybe it has something to do with it? I want to root it so bad it cant because of no OEM. Any new information would be great!
Click to expand...
Click to collapse
What model do you have? What's your csc?
sefrcoko said:
What model do you have? What's your csc?
Click to expand...
Click to collapse
Damn, sorry I thought I listed it. I have a t mobile note 8 where the OEM wont show up and a unlocked note 9 N9600 where the OEM is grayed out to which I tried Odin flashing N9600 CPT/TCP version (not to sure right early this moment) and the flash passed but the phone was exactly the same without any changes and still the OEM was grayed out. I tried 3 different methods of changing dates on both phones with no luck. Any kind of new information or version ti they and get this OEM to work for me would be greatly appreciated.
dandel0074 said:
Damn, sorry I thought I listed it. I have a t mobile note 8 where the OEM wont show up and a unlocked note 9 N9600 where the OEM is grayed out to which I tried Odin flashing N9600 CPT/TCP version (not to sure right early this moment) and the flash passed but the phone was exactly the same without any changes and still the OEM was grayed out. I tried 3 different methods of changing dates on both phones with no luck. Any kind of new information or version ti they and get this OEM to work for me would be greatly appreciated.
Click to expand...
Click to collapse
Ok the T-Mobile model has a locked bootloader that can't be unlocked, so OEM unlock won't work.
The N9600's bootloader can be unlocked though. I have tried the date trick in the past on another Note 8 variant and it worked, but I have since read different things such as recent firmware updates stopping the trick, or needing to jump more than 30 days ahead instead of 7 to make it work. Not sure if all that's true or not, but if nothing works then I would probably back things up, flash original firmware through Odin with full wipe and wait 7 days to see if OEM unlock appears.
sefrcoko said:
Ok the T-Mobile model has a locked bootloader that can't be unlocked, so OEM unlock won't work.
The N9600's bootloader can be unlocked though. I have tried the date trick in the past on another Note 8 variant and it worked, but I have since read different things such as recent firmware updates stopping the trick, or needing to jump more than 30 days ahead instead of 7 to make it work. Not sure if all that's true or not, but if nothing works then I would probably back things up, flash original firmware through Odin with full wipe and wait 7 days to see if OEM unlock appears.
Click to expand...
Click to collapse
Yes I know the t mobile bootloader cant be unlocked but still can get be rooted and use some mods with the lost of 20% battery lose but one has to get OEM unlocked under developers options (that option never shows up for me) I've tried 7 to 14 day without reboot but not 30. I've give that a try on the note 8.
As for the note 9 N9600, I thought it came unlocked already but still just need the OEM unlock switched, which for me is grayed out and cant be switched. I'll use factory reset on both and try the 30 days trick instead of 7 and see if itll work.
Thanks for the info.
dandel0074 said:
Yes I know the t mobile bootloader cant be unlocked but still can get be rooted and use some mods with the lost of 20% battery lose but one has to get OEM unlocked under developers options (that option never shows up for me) I've tried 7 to 14 day without reboot but not 30. I've give that a try on the note 8.
As for the note 9 N9600, I thought it came unlocked already but still just need the OEM unlock switched, which for me is grayed out and cant be switched. I'll use factory reset on both and try the 30 days trick instead of 7 and see if itll work.
Thanks for the info.
Click to expand...
Click to collapse
Yeah the samfail method for u.s. snapdragon models was patched by Samsung at one point, but it depends on which version bootloader you currently have installed if I recall correctly. Check through the samfail thread for more info there. I have an exynos, so can't say for sure about n9600 but that's what I would try at this point
sefrcoko said:
Yeah the samfail method for u.s. snapdragon models was patched by Samsung at one point, but it depends on which version bootloader you currently have installed if I recall correctly. Check through the samfail thread for more info there. I have an exynos, so can't say for sure about n9600 but that's what I would try at this point
Click to expand...
Click to collapse
I cant do anything without figuring out how to get OEM unlock to show up on my note and OEM unlock option greyed out removed from my note 9. The only step one found was the tricking the device on changing the date and that didnt work on the note 8 (going to try it for 30 plus days and see if thatll work) as for the note 9,,,,,,, I dont know why it's even grayed out.
dandel0074 said:
I cant do anything without figuring out how to get OEM unlock to show up on my note and OEM unlock option greyed out removed from my note 9. The only step one found was the tricking the device on changing the date and that didnt work on the note 8 (going to try it for 30 plus days and see if thatll work) as for the note 9,,,,,,, I dont know why it's even grayed out.
Click to expand...
Click to collapse
Like I said you won't get it on the T-Mobile model (and iirc it's not needed for samfail, even if you are on the proper bootloader, etc.), but you can always check the 9600 and/or OEM unlock threads for more on that one if the stock flash/wipe and waiting period approach isn't preferred or doesn't work out.
Hi. Today I found a bug in my Nokia 5 allowing me to enable OEM Unlock in the Developer Option Settings. Please note that I am on the new Android Pie with the latest April security patch. So here is what I did:
1. Please enable Developer Option on the Settings menu. If you already did so, skip this.
2. Now, on the Developer Option, you can see the OEM Unlock is greyed out. To toggle the switch on, "you need to disable and re-enable the Developer Option toggle switch at the top of the menu".
3. After then, you can now freely toggle the OEM Unlock switch. You will be prompted then to enter your device password and voila! OEM Unlock is now enable.
4. To switch it off, you just need to do the steps over again.
That's all. I hope this helps. Sorry, I might have posted this in the wrong section cause I am a new member and just wanted to fill my share to you.
Hey there! been lurking xda for ages but your post just made me register! Thanks a lot for sharing mate.
I just downloaded the update and tried this method, worked fine. Btw there's a new security patch as latest update (5/19), didnt bother doing it as they could have patched it probably.
So, i tried flashing twrp and noticed it still wouldn't let me and flashing get_unlock_ability returns 0. Did you manage to get past this?
This actually works. Havent flashed anything yet, as I'm scared of bricking it.
I just love the good old days when I had the Tmobile G2x with the Nvidia chip, flashed the darn thing so many times, even bricked it numerous times, but I was able to go into recovery and reflash it again. That phone was "Flash and Brick Proof"
thanks for sharing, spent countless hours trying to fix with usb driver setups and cmd lines from other tutorials.
question is what's next?
That's a dummy command,
You still need to properly Unlock it, I'm afraid all the options are paid service
Sent from my Xperia 1 using XDA Labs
This thing still works as now it's may 11th 2020.
I'm I ready to unlock bootloader now?
alexben_007 said:
This thing still works as now it's may 11th 2020.
I'm I ready to unlock bootloader now?
Click to expand...
Click to collapse
Try fastboot oem unlock
Mod edit - translated by https://www.deepl.com/translator:
Unlock the bootloader
****************************
Разблокировать загрузчик -358536084114397 -nokia5_nd1
I am N.E.E.T said:
Hi. Today I found a bug in my Nokia 5 allowing me to enable OEM Unlock in the Developer Option Settings. Please note that I am on the new Android Pie with the latest April security patch. So here is what I did:
1. Please enable Developer Option on the Settings menu. If you already did so, skip this.
2. Now, on the Developer Option, you can see the OEM Unlock is greyed out. To toggle the switch on, "you need to disable and re-enable the Developer Option toggle switch at the top of the menu".
3. After then, you can now freely toggle the OEM Unlock switch. You will be prompted then to enter your device password and voila! OEM Unlock is now enable.
4. To switch it off, you just need to do the steps over again.
That's all. I hope this helps. Sorry, I might have posted this in the wrong section cause I am a new member and just wanted to fill my share to you.
Click to expand...
Click to collapse
pretty usefull tip bro, it worked on my nokia 6 TA-1000
Today I got up real pissed with Samsung for being so restrictive around ROM flashing, rooting, flashing custom firmware or even stock firmware, so wanted to create this post to help anybody considering to get a Samsung phone to stay away from it.
This post is not intended to recommend any specific brand or model of android phone, but to recommend the exact opposite, which brand and model NOT TO EVEN THINK of purchasing.
This post relates to Samsung Galaxy S9 G9600 model which is Snapdragon architecture, but since Samsung is coming up with a bunch of "security features" I tend to think this may be the case for other models as well. I browsed all around XDA and other sources for guides on how to root and install custom roms, and it turns out Samsung manages to have limitations for EVERY step of the way.
Getting a few facts straight
Reference post: https://forum.xda-developers.com/ga.../rom-lineageos-17-1-s9-s9-snapdragon-t4093301
Ok, so there is a solid thread about a custom firmware and looks like several users got hands on it, but they might have been able to get passed though all Samsung security crap before it came out or before it got so tightened up. I'll list below every limitation I found:
OEM Unlock
There is a step where we need to tick OEM Unlock from the phone developer settings, it turns out Samsung has put a 7-day timer for this option to even appear listed to enable. If you do factory reset of the phone, the 7-day timer restarts. There are a few posts around on how to get passed this timer, but to me they were all crap, none of them worked. STRIKE ONE!
Bootloader unlock
After 7-days, we get the OEM Unlock option to appear, at this point you may think: Hurray!! .... WRONG! Now next step is to unlock the bootloader using an utility called CROM Services... And as you may have already guessed, did not work! I'm able to install the apk, but on launch it complains about wrong android version. (Tried with Android 8 and 10) STRIKE TWO!
There are some posts and guides claiming to be able to unlock bootloader by using fastboot utility, I can't reach to understand how, since fastboot commands rely on the bootloader to be previously unlocked (?). I least that is my understanding, correct me if wrong. Needless to say fastboot did not work for me. ADB lists my device but fastboot doesn't. There are a few troubleshoot guides around to try selecting proper USB driver from windows device manager, tried all that, tried a couple of ADB installations, fastboot didn't work.
Knox and RMM state
After some lookup in the web, Samsung incorporates some security features trying to prevent device theft and such things. For us power users this is in reality just a whole load of crap preventing us to get all the juice out of our phones.
Reference: https://www.goandroid.co.in/unlock-bootloader-of-galaxy-s9-plus-snapdragon/84688/
TWRP Recovery
Next step would be to flash a custom recovery such as TWRP with Odin or adb/fastboot, but since we are not able to unlock the bootloader in previous step, this is not doable at all. STRIKE THREE! OUT!
Fastboot utility doesn't recognize the device in download mode, so we can't send any commands to the phone.
Odin complains it is only able to flash signed stock roms, so since TWRP is not, we cannot flash it.
Rooting
Needless to say that if we don't have TWRP, we cannot flash the corresponding packages to root. Although this step may not be needed to install custom firmware, rooting has not been possible.
Stock ROM Flashing
Ok, so let's stay out of custom firmware - let's play around with stock firmwares. At this point, since flashing stock firmwares is kind of allowed by Samsung I was able to try out a couple from android 8 to 10 with Odin
Stock ROM Source: https://www.sammobile.com/samsung/galaxy-s9/firmware/#SM-G9600
But watch out! Once you get to install a specific build version, you cannot go back or downgrade to ROMS with previous Android build version. So now that I got Android 10 cannot go back to 8 or 9, this is probably because locked bootloader and unable to unlock. Here, Odin complains with FAIL! (AUTH) message.
STRIKE FOUR! EVEN OUTTER!
SIM Unlock
Ok, let's stay out of Samsung S9 G9600 model, let's crash it to the wall and throw it away to the garbage! Ok no, let's have it carrier unlocked and sell. Unlockbase is a well known and trusted sim unlock provider, I purchased a license to unlock by USB cable, but... GUESS WHAT! G9600 is not supported for unlocking operator network with this software... what a surprise!! I was able to apply for a refund and got my money back, so no worries here.
Note that flashing carrier free ROM does not unlock sim to use with any network operator.
I'll be trying to unlocking by code soon, as this is based on IMEI number, I may think this is independent to the phone model and edition, so I hope I have more luck with this option.
Conclusion
G9600 is a really crappy phone to mess around with. I may have ran low on luck with this specific Samsung Galaxy model since I got it as a gift, which is the latinamerican crappy edition. I wonder if other S9 editions and other Samsung models run with better luck than mine on this scenery... But as a lesson to myself, I will stay away of any Samsung smartphone in the foreseeable future.
OEM Unlock
The 7-day lock prevents stolen phones from being factory reset, leaving the thief with a phone permanently protected by your account. While a minor inconvenience, it's actually effective and not the worst compared to other manufacturers.
Bootloader Unlock
After OEM Unlocking, flashing TWRP through ODIN is effectively unlocking the bootloader. This is possible on both exynos and snap.
Knox and RMM
While this is an inconvenience, from Samsung's point of view, it's worth it. It makes the phone look more secure in the eyes of potential customers. If you really wish for NFC payments, I'm still able to use GPay with Magisk on a custom ROM.
TWRP Recovery
TWRP is flashed through ODIN, not fastboot. Look up an actual guide before complaining.
Root
Yes you can
Stock ROM Flashing
The one thing I could agree on with you is Samsung disabling OTA updates when OEM unlocking. I don't see the point really, but you're free to flash whatever you want through ODIN. Downgrading shouldn't be an issue. Not sure what's up with that.
Before buying a phone, how about you do some research before crying on forums. As a power user coming from the Oneplus One, I don't regret going for Samsung in the least.
Thanks for your reply, I had dropped all hope after several attempts over last few weeks. Found this option and I was able to get past my blocking issue with TWRP and moved on.
https://forum.xda-developers.com/ga...er-development/g9650zhu6dta7-android-t4051751
I have G960F and have to admit I totally disagree with your original post. I've been using custom ROMs on nearly every phone I ever had and don't think S9 (G960F) is bad in terms of unlocking. Just did an OEM unlock, waited a week, flashed TWRP through Odin, booted straight to TWRP and immediately flashed a custom ROM from it (because a boot to the stock ROM would replace TWRP back with the stock recovery IIRC). In the end I got sick of all the problems with Magisk and non-working google pay that I went back to the stock ROM - making S9 the first phone I use with a stock ROM even though it can be flashed. I think it's a great phone for power users.
And as far as SIM unlock goes - Samsung is not to blame, the carrier the phone was made for (and purchased from) is. Phones that Samsung itself sells are unlocked. I wonder why there's still some countries where SIM locking remains legal.
This thread is a prime example of how people end up with bricked devices. So much misinformation in one page LOL
I had the 9650 and most of what I'm doing here is user error. This was one of the best devices I've ever owned. I mention of fast boot and such you obviously just do not know samsung devices. You can't blame samsung on your own ignorance
I've just been wondering if I get just unlock the Verizon bootloader for a Pixel 4a 5g (got the phone at a thrift store for 10 dollars only) - the OEM unlocking button is grayed out and I heard I cannot unlock the bootloader. I'mjust wonderingif I can at least do something funny with a Verizon bootloader at least.
Its not supposed to be possible, yet on the latest Android 13 update, my OEM unlock toggle suddenly became switchable after freezing a bunch of carrier apps. The only thing I didn't freeze was Sim tool kit and work config. I've literally done this over and over again with no results, in fact my phone was never even paid off. Yet for some reason, suddenly I was able to just toggle the switch unlock my bootloader and my device which is pretty much unheard of since the pixel 3
Yeedatoy said:
Its not supposed to be possible, yet on the latest Android 13 update, my OEM unlock toggle suddenly became switchable after freezing a bunch of carrier apps. The only thing I didn't freeze was Sim tool kit and work config. I've literally done this over and over again with no results, in fact my phone was never even paid off. Yet for some reason, suddenly I was able to just toggle the switch unlock my bootloader and my device which is pretty much unheard of since the pixel 3
Click to expand...
Click to collapse
So sorry for the late response.
How are you able to freeze the carrier apps on your Pixel? Do you use some task manager?
I used Shizuku, and froze apps with hail or icebox. Also, there's the universal android debloater for windows which is amazing
webhook said:
So sorry for the late response.
How are you able to freeze the carrier apps on your Pixel? Do you use some task manager?
Click to expand...
Click to collapse
Yeedatoy said:
I used Shizuku, and froze apps with hail or icebox. Also, there's the universal android debloater for windows which is amazing
Click to expand...
Click to collapse
Is there a download link for those apps?
Yeedatoy said:
I used Shizuku, and froze apps with hail or icebox. Also, there's the universal android debloater for windows which is amazing
Click to expand...
Click to collapse
I'm on icebox now, what work mode do I choose?
What system apps should I freeze in icebox?
Hello All, this is my first ever post. I got pixel 4a 5g (2nd hand) and its OEM unlocking option is grayed out. I tried connecting with internet, tried date change trick, tried adb command but nothing seems to work. I am stuck currently. the phone is not career locked as I have been using other networks on the phone. i see so many posts regarding this but could not find any confirmed solution of unlocking OEM. if any one can guide me to the ans? appreciate in advance.
If there are any software to unlock oem? or any other solution based on my problem?
PS: its running on android 13, with May 5, 2023 security update. the IMEI ends with 18292
Diabuirani said:
Hello All, this is my first ever post. I got pixel 4a 5g (2nd hand) and its OEM unlocking option is grayed out. I tried connecting with internet, tried date change trick, tried adb command but nothing seems to work. I am stuck currently. the phone is not career locked as I have been using other networks on the phone. i see so many posts regarding this but could not find any confirmed solution of unlocking OEM. if any one can guide me to the ans? appreciate in advance.
If there are any software to unlock oem? or any other solution based on my problem?
PS: its running on android 13, with May 5, 2023 security update. the IMEI ends with 18292
Click to expand...
Click to collapse
Insert a SIM card in your device and determine if it's locked to a carrier.
If it's a Verizon SIM lock, :/ outta of luck. Found that out the hard way via looking at XDA forums and nearly wasting time on the device. I plan to sell it to get a Google Pixel 6 Pro.
If i flashed a custom rom does it remove the lock and they can't detect me?
If that so how to flash roms without unlocking the bootloader?
Abdelrahman Salah said:
If i flashed a custom rom does it remove the lock and they can't detect me?
If that so how to flash roms without unlocking the bootloader?
Click to expand...
Click to collapse
Simply can't flash roms without unlocking bootloader, need custom recovery to rewrite OS which can't be access because no unlock >:3
Hi,
for my Google Pixel 5 I want /e/os/.
Two instructions how to accomplish this. To flash /e/os onto a Google Pixel 5, the smartphone need to have Android 12.
My Google Pixel 5 has Android 13 (I received a New Old Stock device in a unopened box with Android 13. So no tinkering
beforehand.)
I found this archive of Android 12 images - all for the Google Pixel 5 and all Android 12:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
How can I determine and choose the correct image to flash?
Cheers!
Etymotics
12.1.0 (SQ3A.220705.003.A1, Jul 2022) is going to be the latest android 12 build which should be compatible.
Hi noidea24,
thank you for your post and the information. That helps me a lot - I was confused by the shear amount of images.
Do you know a thread which may have the things I want to achieve as topic ? I tried to search with keywords
like "Google Pixel 5 /e/os" and similiar, but it looks like the search found all threads containing GOOGLE *and* all threads with PIXEL *and* all....and so forth. I would need a second search engine to skim through the results...\
Cheers!
Etymotics
What are you looking for specifically? There's not really much info on e/os on the pixel 5. It works well, but the development is slow. Why e/os over similar projects with updated android versions like Graphene, Calyx, Copperhead?
e/os is not daily drivable, recommend not to install.
e/os was recommended to me by Marcel Bokhorst, the author of XPrivacy.
But as it seems, I had bad luck with the phone I bought:
The "OEM unlock" is greyed out and I know of no way to unlock the bootloader.
It currently runs on Android13 and last update was Dec. '22.
My intention behind all this was to have a de-googled phone because I [CENSORED] this
tracking and spying and "owning" a device, which I cannot control to 100%.
Anything else I can do to achieve this?
PS: My phone may be is one of these [CENSORED] Verizon devices. It was originally packaged
and as it seems never used before...
Where did you buy your phone? Ebay? A retailer?
Is there a keyword "Locked" or "Unlocked" anywhere on the website?
If the product listing didn't mention anything about it being carrier locked, I suggest requesting a refund or a replacement.
The "OEM Unlock" greyed-out is most definitely due to it being a carrier locked device and you're out of luck.
Also, if you truly want a de-googled OS, I recommend Graphene OS. https://grapheneos.org/
Etymotics said:
e/os was recommended to me by Marcel Bokhorst, the author of XPrivacy.
But as it seems, I had bad luck with the phone I bought:
The "OEM unlock" is greyed out and I know of no way to unlock the bootloader.
It currently runs on Android13 and last update was Dec. '22.
My intention behind all this was to have a de-googled phone because I [CENSORED] this
tracking and spying and "owning" a device, which I cannot control to 100%.
Anything else I can do to achieve this?
PS: My phone may be is one of these [CENSORED] Verizon devices. It was originally packaged
and as it seems never used before...
Click to expand...
Click to collapse
Not to give you false hope but did you connect to wifi on your first time through setup? If you don't, OEM unlock will be greyed out, regardless.
Hi Alex,
(NOT meant as any form of criticism or complaint... )
...I am a little confused here.
Other posts (not necessarily on this forum...can't remember) say: "Pull out the simcard, disable Wifi and DON'T contact anything, only skip through the setup..."
At the moment I only have a simcard of the wrong size...but I enabled Wifi but did not update anything in fear of getting an even stronger patch to disable any form of tinkering.
But as I am still having a locked "OEM unlocking" and a locked bootloader I am open for any kind of tinkering to get
this damn thing freed.
Would these steps ok:
Start the phone,
Setup lockscreen, dark theme, etc..
enable Wifi and download all updates, install updates
Ok? Or what would you suggest?
Cheers!
Etymotics
Etymotics said:
Hi Alex,
(NOT meant as any form of criticism or complaint... )
...I am a little confused here.
Other posts (not necessarily on this forum...can't remember) say: "Pull out the simcard, disable Wifi and DON'T contact anything, only skip through the setup..."
At the moment I only have a simcard of the wrong size...but I enabled Wifi but did not update anything in fear of getting an even stronger patch to disable any form of tinkering.
But as I am still having a locked "OEM unlocking" and a locked bootloader I am open for any kind of tinkering to get
this damn thing freed.
Would these steps ok:
Start the phone,
Setup lockscreen, dark theme, etc..
enable Wifi and download all updates, install updates
Ok? Or what would you suggest?
Cheers!
Etymotics
Click to expand...
Click to collapse
If you're not going to lose data or your not afraid of it, I would:
Factory reset without sim card in
When phone reboots, start setup
Don't put sim in but do connect to wifi
Skip through setup if you want and check if oem unlock is available
I'm not sure of the instructions you have, maybe that's what people believe for Verizon phones but you're not sure if you have one, correct?
Here's my experience:
I have several pixels, all unlocked. If I flash back to stock firmware and skip through setup without connecting to wifi, OEM unlock is greyed out. If I connect wifi on the first time through, it's available.
I've also heard this in tech videos. However, it won't work with Verizon phones. But if yours isn't Verizon, this could be the reason you're not able to unlock.
Hi Alex,
thank you for all your help! By the way: Are there any definite proofs for "my smartphone is a Verizon one" ?
I will try what you wrote and will be back with the result.
Two things came into my mind:
- Shall I install updates/upgrades if offered?
- Would downgrading (if even possible) via Chrome and the "Flash" feature on the Google page with all these images help, if I have a Verizon jail?
Cheers!
Etymotics
Etymotics said:
Hi Alex,
thank you for all your help! By the way: Are there any definite proofs for "my smartphone is a Verizon one" ?
I will try what you wrote and will be back with the result.
Two things came into my mind:
- Shall I install updates/upgrades if offered?
- Would downgrading (if even possible) via Chrome and the "Flash" feature on the Google page with all these images help, if I have a Verizon jail?
Cheers!
Etymotics
Click to expand...
Click to collapse
There may be a way but I'm not entirely sure, perhaps Google well help. I do seem to remember something about the IEMI but that may have been older models.
I wouldn't upgrade anything after setup and it shouldn't offer anything during.
As far as I know, downgrading won't help but I don't think you could from the Google page, as it requires an unlocked bootloader
Hi Alex,
I will try, what you wrote without updating anything ... will be back then...
Hi Alex,
no...unfortunately it does not help to connect to wifi...the "OEM unlock" is still grayed out.
Now....I wanted a de-googled phone to keep my privacy...instead I got a phone which is the
exact opposite. Unfortunately the cost of that thing remains the same...
Anything else, I can try?
Cheers!
Etymotics
Last week-end, i was abble to downgrade a Pixel 5 from A13 to A12 following this page
Navigate this article:
Downgrading your Google Pixel smartphone to stable Android version
Method 1: Leave the beta program
Method 2: Manual downgrade
Using Android Flash Tool
Using Fastboot
choose method 2 : fastboot (at the end of the article)
https://www.xda-developers.com/how-...rom-beta-developer-preview-to-stable-android/
and install e-1.10-s-20230412278810-stable-redfin according to the official instructions https://doc.e.foundation/devices/redfin/install
Hi Piero-e
That sounds very interesting. Did you unlock your bootloader before starting the procedure?
Did you change the bootloader of you device to another one?
Cheers!
Etymotics
Yes, i first unlock the bootloader (using the WiFi connection to another phone)
And flash bootloader and modem,
Then unfortunately my computer don't find the flash-all command, so I used the Gogol online tool to flash the others partitions