UPDATE: This phone is money down the drain unless I can unlock and root it. If you can help me do that successfully, I'll pay you $20. Just to end this frustration.
UPDATE: Cash offer rescinded. I fixed the problem by buying a different phone and giving up on this one.
Question: How do I fix the OEM Unlocking option not appearing on a Samsung A01 (SM-S111DL)?
Answer: By giving up on it and buying a different phone.
Maybe this is a better forum to post this. I have a Samsung A01, SM-S111DL. I want to root. I want Magisk on there.
I have been searching, and searching, and searching for any useful tutorials on how to root this specific device. In addition to searching, I have also been searching. And besides that, completely apart from that, I have been searching. So nobody better tell me I haven't tried figuring this one out for myself.
So far, I can't find anything that works. I just can't. Partly because tutorials keep telling me I need to turn on the OEM Unlocking option, and it ain't there. I know where it's supposed to be, between Bluetooth HCI and Running Services, and it's not there. And I tried the Date & Time trick, and it didn't help.
So, if I can't turn that option on, what can I do? I was thinking about trying Heimdall. It was unable to print the PIT, but I managed to download a PIT that supposedly corresponds exactly to my device. It's labeled A01Q_USA_TFN.pit. I also downloaded the full firmware with Frija, and extracted stuff. I took the boot.img from the downloaded firmware and patched it with Magisk. I was thinking of installing it, but then I said, no, I better wait until some experts weigh in on this. Best case, the flash would go just fine. But then there are two bad cases. One, Heimdall won't even be able to flash, and that will mean more anger and frustration. Two, it'll brick the device. And I'm not even sure which is worse anymore.
This point, I don't even know what the hell to do. Please, someone help.
Also, I'd like to have TWRP on this device. But I don't know whether there's a version out yet. Sure, there's one for some other model of A01, but would it work with mine? I just don't know, and I'm feeling too discouraged to try.
Please, someone help.
Did you search before posting? I see many, many threads regarding rooting the Galaxy A01, including one you posted 7 days ago on the same topic.
V0latyle said:
Did you search before posting? I see many, many threads regarding rooting the Galaxy A01.
Click to expand...
Click to collapse
Did you read before replying? I told you many, many times that I searched.
FailSafeNow said:
Did you read before replying? I told you many, many times that I searched.
Click to expand...
Click to collapse
My point is, creating a new post isn't always the best course of action when there's already discussions on the topic. Secondly, do not create multiple threads on the same topic.
If OEM Unlock is not available, you won't be able to unlock the bootloader, which will prevent you from flashing custom images (such as the patched boot image). You could try using Odin to flash an older firmware version and see if OEM Unlock becomes available.
Here's a couple things you can try. First, remove your SIM and turn off WiFi. Then, disable Automatic Date & Time, and set the time ahead by at least 1 week. If the OEM Unlock toggle does not appear, just wait a while.
Apparently, this has something to do with Knox.
If you want to check whether unlocking the bootloader will be possible at all, you can use ADB:
Code:
adb shell getprop ro.oem_unlock_supported
If this returns 0, unlocking the bootloader is not possible at all.
If this returns 1, then you just need to be able to access the OEM Unlock toggle, which will set get_unlock_ability to 1 and permit unlocking the bootloader, at which point you should be able to flash a patched boot image.
See this article for more information.
V0latyle said:
My point is, creating a new post isn't always the best course of action when there's already discussions on the topic. Secondly, do not create multiple threads on the same topic.
If OEM Unlock is not available, you won't be able to unlock the bootloader, which will prevent you from flashing custom images (such as the patched boot image). You could try using Odin to flash an older firmware version and see if OEM Unlock becomes available.
Here's a couple things you can try. First, remove your SIM and turn off WiFi. Then, disable Automatic Date & Time, and set the time ahead by at least 1 week. If the OEM Unlock toggle does not appear, just wait a while.
Apparently, this has something to do with Knox.
If you want to check whether unlocking the bootloader will be possible at all, you can use ADB:
Code:
adb shell getprop ro.oem_unlock_supported
If this returns 0, unlocking the bootloader is not possible at all.
If this returns 1, then you just need to be able to access the OEM Unlock toggle, which will set get_unlock_ability to 1 and permit unlocking the bootloader, at which point you should be able to flash a patched boot image.
See this article for more information.
Click to expand...
Click to collapse
Thank you. I've tried various tricks with the date, to no avail so far. But I will try the trick the way you said it, and try waiting. Incidentally, I have no sim. Just got this phone off eBay. Never planned on putting a sim in it. Just wanted it for usage as a wifi device.
So far, no OEM Unlocking option has appeared. But I'll wait on it, like you said. And yeah, I've read that these devices are made to have some kind of waiting period.
I also read that you had to be on Android 11 before you could get the unlocking option. So that's what I'm on. As for Odin, it gets stuck on the analyzing phase and never actually writes anything. Heimdall gives me an error of -12 when I try to use it. I've tried installing drivers on my computer with Zadig, but it hasn't changed anything so far. And it has a lot of options for drivers and stuff, so I don't know which are even the right ones. (I'm on Windows 10 Pro.)
I tried the ADB code about a week ago, having found that direction in one of the threads. And yes, it gave me a 1, so good news.
Is there no other way to set unlock ability to 1? I mean, if Samsung had this phone in its lab, would they be able to force it to do things, or would they have to manually remove the MMC and put it on a special reader?
Also, the reason I created my own thread was that I thought piggybacking on other people's threads was frowned upon.
Edit: I also checked the article. I've seen it before, because when I want something, I keep searching for it until I either find it or destroy my nervous system trying. I tried putting together the combination firmware. But two problems. First, it lies about which files I'm going to find when I extract the various archives. boot.img.lz4: fine. system.img.lz4: no such file exists. sboot.bin.lz4: no such file exists. I'm guessing they would want me to use aboot.img.lz4 instead of sboot.img.lz4, and super.img.lz4 instead of system.img.lz4, but since the guide was made for phones that call their images different things, I don't honestly know. Second problem: Odin can't flash crap. Neither can Heimdall. The experts say, "Use one of these patched versions of Odin." So I try. No dice. And I try Heimdall, but that's no good either. Like I said, Error -12. What do I do about this? "Install stuff with Zadig." So I try that. I install every damn thing that Zadig has an option to install. Nothing changes. Nothing gets better. The tutorials have failed me.
Next time I buy a phone, painless rooting and unlocking is going to be my first criterion.
The option to unlock still has not appeared. I need more help.
I'm just about ready to give up on this phone completely. Can nobody save this situation?
are there any variants to this device? how would you match firmwares? or substitute the firmware to be able to flash, so that other options such as oem unlock become available? have we checked if any of the android 10 firmwares for a01 sm-s111dl have the oem option available?
FailSafeNow said:
UPDATE: This phone is money down the drain unless I can unlock and root it. If you can help me do that successfully, I'll pay you $20. Just to end this frustration.
UPDATE: Cash offer rescinded. I fixed the problem by buying a different phone and giving up on this one.
Question: How do I fix the OEM Unlocking option not appearing on a Samsung A01 (SM-S111DL)?
Answer: By giving up on it and buying a different phone.
Maybe this is a better forum to post this. I have a Samsung A01, SM-S111DL. I want to root. I want Magisk on there.
I have been searching, and searching, and searching for any useful tutorials on how to root this specific device. In addition to searching, I have also been searching. And besides that, completely apart from that, I have been searching. So nobody better tell me I haven't tried figuring this one out for myself.
So far, I can't find anything that works. I just can't. Partly because tutorials keep telling me I need to turn on the OEM Unlocking option, and it ain't there. I know where it's supposed to be, between Bluetooth HCI and Running Services, and it's not there. And I tried the Date & Time trick, and it didn't help.
So, if I can't turn that option on, what can I do? I was thinking about trying Heimdall. It was unable to print the PIT, but I managed to download a PIT that supposedly corresponds exactly to my device. It's labeled A01Q_USA_TFN.pit. I also downloaded the full firmware with Frija, and extracted stuff. I took the boot.img from the downloaded firmware and patched it with Magisk. I was thinking of installing it, but then I said, no, I better wait until some experts weigh in on this. Best case, the flash would go just fine. But then there are two bad cases. One, Heimdall won't even be able to flash, and that will mean more anger and frustration. Two, it'll brick the device. And I'm not even sure which is worse anymore.
This point, I don't even know what the hell to do. Please, someone help.
Also, I'd like to have TWRP on this device. But I don't know whether there's a version out yet. Sure, there's one for some other model of A01, but would it work with mine? I just don't know, and I'm feeling too discouraged to try.
Please, someone help.
Click to expand...
Click to collapse
ADB Fastboot OEM unlock? https://www.getdroidtips.com/how-to...-on-Samsung-Galaxy-Phones-via-PC-ADB-Fastboot
so i found out how to do this if anyone still needs this information for this phone. You go to software status and click the kernel version several times to activate developer mode and once thats activated there will be a developer options under "about phone" on the main settings menu and instead of being between bt hci and services it was down at the bottom under the debugging sub menu. There is USB debugging and wireless debugging(over wifi) simply toggle usb debugging and/or wireless debugging and continue from there on youre pc of choice with process of choice! Hope this has helped anyone. I have the exact same phone as OP, same model number.
Related
I got this phone from a friend who also got it from a friend and its FRP locked. I have ODIN and I have not been able to find any firmware for this device. I seen some paid for but it looks risky. Any details on that? I would take it to stores but they will do nothing except a select few that I'm not trying to venture to. Obviously this is newer OS and stuff so I think it may require a bit more than just firmware, I keep hearing about some bootfile that looks different than the .md5 file or whatever it was... any help? Ive been able to get a quick settings app on it and i can get into settings but not developer options, I can't seem to disable google play services to bypass it, no successful root apps, running android marshmallow ?????
Xae.andi said:
I got this phone from a friend who also got it from a friend and its FRP locked. I have ODIN and I have not been able to find any firmware for this device. I seen some paid for but it looks risky. Any details on that? I would take it to stores but they will do nothing except a select few that I'm not trying to venture to. Obviously this is newer OS and stuff so I think it may require a bit more than just firmware, I keep hearing about some bootfile that looks different than the .md5 file or whatever it was... any help? Ive been able to get a quick settings app on it and i can get into settings but not developer options, I can't seem to disable google play services to bypass it, no successful root apps, running android marshmallow
Click to expand...
Click to collapse
Hi bro.
Sorry to hear about the problem. I know the hassles of getting phones from someone else. You're not to clear on your problem. I assume you cant get into settings and therefor you had to download a 3rd party quick settings app. If possible go to settings and then "About". Look for "Software Info". There tap on the build number until you see a notification stating you are now a developer. Go back to main settings screen and developer options should be listed at the bottom. In developer options there should be an option for "OEM Unlock", turn it on and tr flashing again. If this is not possible try searching the settings for "Re-Activation Lock" and turn it off. Insert your password when promted and try again. If all this is not possible or fails then try Samsung Tool Pro. I cant post the link but just google D3X Samsung Tool Pro with loader. This tool is helpful for unlocking and bypassing FRP as well as flashing firmware, recovery's etc.
Feel free to ask for help
I used Nova for a forced launched homescreen and got into the settings that isn't the hard part. The hard part is the OEM Unlock. Been trying that build number a million times hoping something would do different and no sucess. I already have ODIN and Pro Tools but even they don't have the SM-S327VL firmware to fix this. I was thinking about re-partitioning it with odin... I know it's risky but if I brick it I would have to wait for the firmware anyway?. I cant flash a thing without any firmware. So far I haven't been able to find it on the samsung website or any others. I seen some that wanted money for them but I don't trust it. Can anyone confirm any? HhEeLlPp???
Finally disabled all google apps but I can't get rid of Knox
Frp bypass
I unlocked my phone on my own. I used an app called Test DCP and it became a device owner and then I restarted my phone and it was done. Good app????
Xae.andi said:
I unlocked my phone on my own. I used an app called Test DCP and it became a device owner and then I restarted my phone and it was done. Good app
Click to expand...
Click to collapse
great works fine with that app
Hi!
New here, hope I am in the right place...I have limited tech skills (born pre cell phones and computers) I did manage to install a custom ROM on an old HTC years ago, and thought I could do it again!
I have a Samsung A10e (SM-A102U) locked to sprint.
I can get the developer options but can't get the OEM unlock option. I also can't wait 7 days. Have tried a few things with the date and turning off updates etc, nothing worked. Here is what I am trying to do in order (please correct me if it is the wrong order) Ultimately I want my phone unlocked for use with any sim, and install a custom rom, to remove some bloatware. Could I wipe the phone totally take it to a piece of memory with no ROM and then re-load it, or use ADB to do it? Please excuse my ignorance - if I sound clueless I kinda am!
1. Unlock the bootloader
2. Install TWRP
3. Install custom ROM
It has taken me days of searching but to no avail, literally pulling my hair out. Happy to buy a beer for anyone that helps!
Wow,thanks...
Response has been overwhelming...
SandsCayman said:
Hi!
New here, hope I am in the right place...I have limited tech skills (born pre cell phones and computers) I did manage to install a custom ROM on an old HTC years ago, and thought I could do it again!
I have a Samsung A10e (SM-A102U) locked to sprint.
I can get the developer options but can't get the OEM unlock option. I also can't wait 7 days. Have tried a few things with the date and turning off updates etc, nothing worked. Here is what I am trying to do in order (please correct me if it is the wrong order) Ultimately I want my phone unlocked for use with any sim, and install a custom rom, to remove some bloatware. Could I wipe the phone totally take it to a piece of memory with no ROM and then re-load it, or use ADB to do it? Please excuse my ignorance - if I sound clueless I kinda am!
1. Unlock the bootloader
2. Install TWRP
3. Install custom ROM
It has taken me days of searching but to no avail, literally pulling my hair out. Happy to buy a beer for anyone that helps!
Click to expand...
Click to collapse
I have the exact same question.
it will not happen alot of us based carriers will lock down the phone via bootloader our best option is to find combination firmware and hopefully find root that way assuming that method still works.
Same situation here with Verizon. And sorry to tell you but I don't think anything will happen for you after seven days either, at least nothing did for me. I've spent a long time trying to get past this with no success, trying every trick I've found (the changing the date manually trick, factory resetting and trying on WiFi, etc.).
Also, using the app "Settings Database Editor," I've found the config/property where OEM bootloader unlock has been disabled:
"sys.oem_unlock_allowed" "0"
Screenshot here.
I'm hoping maybe we can edit that property via ADB or something. I'm not really holding out any hope here though. :-/
One other random discovery (not really helpful or relevant for our OEM bootloader unlock goal, but something I discovered while trying to obtain unlock): I believe I discovered a firmware error (at least on the Verizon build). When you hold volume up + power together for about 30 seconds, the phone shows the recovery menu for a split second but then instantly/immediately wipes all data and factory resets, without ever allowing the user to choose their own recovery menu selection and without giving any reset confirmation prompt before instantly wiping all user data. It's not supposed to work that way, according to the phone's user manual/Samsung technical support instruction. It's actually really pissed me off because I've triggered this instant reset twice now by accident just by having the phone in my back pocket and sitting down. I go to pick up my phone from my pocket and notice the screen is on and then discover everything was wiped. Very annoying! I called Samsung customer support twice to try to explain that I believe there to be a firmware error present (at least on Verizon models) but they didn't seem to care/their support script told them to have me take the device to some local authorized third-party screen repair place. One good outcome I've discovered from factory resetting the phone is that you can at least avoid enrolling the phone in part of the Knox security crap, the "kme" protection. I originally couldn't use remote apps like TeamViewer or AnyDesk without some stupid "Protected by Knox" notification popping up and then my remote app instantly exiting. Made me so angry. But now I'm able to use those apps without any issue. Though, the phone does try to have me agree to enroll in kme protection or whatever about once a day and I have to manually close the enrollment agreement form that pops up.
allenjthomsen said:
it will not happen alot of us based carriers will lock down the phone via bootloader our best option is to find combination firmware and hopefully finwww reset that way assuming that method still works.
Click to expand...
Click to collapse
I've had the same issue with entire A series. All OEM's are disabled regardless of carrier. It seems to be part of Samsung's firmware. After nothing but dead ends and contacting samsung directly i was left scratching my head. Came here searching for some insights I may have overlooked.
-Enable developer options
-Enable wifi
-Join a network
-Change date to 10 days forward
-Reboot phone
-OEM unlock will be available
Thank me later
moe7863 said:
-Enable developer options
-Enable wifi
-Join a network
-Change date to 10 days forward
-Reboot phone
-OEM unlock will be available
Thank me later
Click to expand...
Click to collapse
Nothing happens/doesn't work for Verizon. :-/
I mentioned having tried this technique already in my previous post above.
---------- Post added at 07:42 PM ---------- Previous post was at 07:38 PM ----------
For what it's worth, here's a sister thread I started on this topic with a few responses/potential bootloader unlock ideas shared by other members but no real solid progress made at this point:
https://forum.xda-developers.com/galaxy-a10/help/samsung-galaxy-a10e-to-t3990817/page4
the bl is not unlockable
Bump
I know this is possible I've seen it done before. I think it had to do with a modified ota update.
SHAD0WUSER said:
Bump
I know this is possible I've seen it done before. I think it had to do with a modified ota update.
Click to expand...
Click to collapse
Do you have proof of this being done?
Because as far as I'm aware, it's been impossible to unlock bootloader for years
I actually purchased this phone from Metro last week after searching for it on XDA and seeing that is was BL unlockable. I didn't realize any the time that this was only the international variants. Good luck to all devs whose skillset is better than my own.
ShaDisNX255 said:
Do you have proof of this being done?
Because as far as I'm aware, it's been impossible to unlock bootloader for years
Click to expand...
Click to collapse
it is not possible.. also u cant flash a modified ota cuz it will fail sig check
nateberhardt81 said:
I actually purchased this phone from Metro last week after searching for it on XDA and seeing that is was BL unlockable. I didn't realize any the time that this was only the international variants. Good luck to all devs whose skillset is better than my own.
Click to expand...
Click to collapse
if u looked u would have seen the model numbers are different
elliwigy said:
if u looked u would have seen the model numbers are different
Click to expand...
Click to collapse
Yeah... I I knew better than to just look at a10e and assume they were all the same. I went through the same struggle with a J7 not too long ago... Should have learned my lesson then.
nateberhardt81 said:
Yeah... I I knew better than to just look at a10e and assume they were all the same. I went through the same struggle with a J7 not too long ago... Should have learned my lesson then.
Click to expand...
Click to collapse
no biggie.. at least those r super cheap.. i got a a50 just to brick it to try an exploit that didnt work lol.. o well
I have an A10e as well but the model number is SM-S102DL, I am a complete novice when it comes t phones but will I be able to root this without unlocking the bootloader?
xSpookyx said:
I have an A10e as well but the model number is SM-S102DL, I am a complete novice when it comes t phones but will I be able to root this without unlocking the bootloader?
Click to expand...
Click to collapse
no.. are u sure u have a a10e?
you cant root without exploits that dknt exist without unlocking the bootloader
No matter about root. but I converted many of Samsung A10e to international variant to remove any boost metropcs or any other networks bloatware application.
you can also do it without any issue. Simply flash A102U1 Firmware. I m not sure that it will work on Network Locked/Sim locked devices. I flash and convert it after using a remote unlocking service which already changed the CSC version of EFS to XAA from the BST csc...
XAA is for US Unlocked Without carrier locked phones and BST for Boost mobile carrier only which came with lots of boost bloatwares but maybe that A10e boost remote unlock service saved me.
check the screenshot attached.
Shabby The Dev said:
No matter about root. but I converted many of Samsung A10e to international variant to remove any boost metropcs or any other networks bloatware application.
you can also do it without any issue. Simply flash A102U1 Firmware. I m not sure that it will work on Network Locked/Sim locked devices. I flash and convert it after using a remote unlocking service which already changed the CSC version of EFS to XAA from the BST csc...
XAA is for US Unlocked Without carrier locked phones and BST for Boost mobile carrier only which came with lots of boost bloatwares but maybe that A10e boost remote unlock service saved me.
check the screenshot attached.
Click to expand...
Click to collapse
Careful, don't post your IMEI on the internet as some bad people can do stuff with it
Hi,
I am pretty new on how to install custom-roms on Android, although I have a good experience on Linux distro installs on pc.
My question is how can you unlock OEM on a SM-A025G/DSN? I was reading this article: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a02s-snapdragon.4294377/ from afaneh92, and I saw that my device is compatible with OEM unlocking so I wasn't hesitated to actually search for this function but it seems that on Android 11 this option is not available?
I saw a few articles (like this: https://www.getdroidtips.com/unlock-bootloader-galaxy-a02s/) where they can eventually find the OEM unlocking option but I was not lucky to see that. My phone is developer mod, so I think I ran out of options.
Any help on this?
Thanks for the responses!
I've ran across the issue of not finding OEM unlock on my Samsung phones. All it requires (for me, anyway) to show up is to connect to a WiFi network... that's it. Try it, maybe you can get it to pop up.
ShaDisNX255 said:
I've ran across the issue of not finding OEM unlock on my Samsung phones. All it requires (for me, anyway) to show up is to connect to a WiFi network... that's it. Try it, maybe you can get it to pop up.
Click to expand...
Click to collapse
Didnt work for me.. but I have the SM-A025AZ (cricket variant) and I'm starting to think its impossible...
Hello group I interested in rooting my Oneplus n 10. Now I've been doing research for the past week and a half but it's very confusing. First off my oem is greyed out in developers my mode, and second I don't own a computer. I did DL LADB app but for some reason I can't find the code to do so. Can someone give me a guide or a easy way to do so? Thanks I appreciate it.
Hoosier-daddy? said:
Hello group I interested in rooting my Oneplus n 10. Now I've been doing research for the past week and a half but it's very confusing. First off my oem is greyed out in developers my mode, and second I don't own a computer. I did DL LADB app but for some reason I can't find the code to do so. Can someone give me a guide or a easy way to do so? Thanks I appreciate it.
Click to expand...
Click to collapse
Need PC
What @VovaHouse said... I know of no way without a PC.
If you have the global model (e.g. carrier indifferent) the phone still needs to connect to the Google Spyware server once before the OEM switch is ungreyed out. There is another thread where it is claimed this can be bypassed, but it was never worth it for me to do.
If you have a carrier model, you need to get it unlocked, which, like the rooting, requires a PC AFAIK. Maybe buy a cheap used one or something? Once you are freed, it is no longer required.
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
AndyYan said:
Just a quick heads-up.
unlock token - OnePlus (United States)
www.oneplus.com
By the way, to root without readily available stock firmware, first unlock bootloader, then boot a pre-rooted GSI with DSU Sideloader, pull stock boot partition from there, and finally patch/flash it. This applies to the Open variant as well.
Click to expand...
Click to collapse
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
PsYk0n4uT said:
Tried to unlock but apparentpy my device only has 7 digits in the serial number which keeps me from being able to use the website to request the unlock code.
I used the debloat script I found on n200 threads to get oem unlock on option. T-Mobile variant
Click to expand...
Click to collapse
Try prepending 0s?
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
PsYk0n4uT said:
Well. I was thinking that doing that would make the unlock token they give me different from what the phone would be expecting
Click to expand...
Click to collapse
Tried adding zero on front and back of serial it just tells me invalid serial
PsYk0n4uT said:
Tried adding zero on front and back of serial it just tells me invalid serial
Click to expand...
Click to collapse
Chatting with OnePlus hasn't yielded anything so far
Just a tip, because in my infinite forgetfulness I wasted an hour last night trying to figure out why I was getting the error, fastboot could not open target HAL.
Remember that you must request the unlock code from fastboot, not fastbootd. Which is what you will boot into if you issue adb reboot fastboot.
So here's a quick step by step.
1.Enable usb debugging. 2. Connect your device and allow access for the computer. My device asks if I want it to charge or transfer files. Select transfer files/Android auto and then use adb start-server. May have to unplug the USB cable and reconnect. Select "always allow this device/PC".
3. Issue "adb devices" to make sure your connected.it should list your device by it's serial number. If not then try unplugging the device and revoke adb authorizations in dev options and toggle USB debugging off and back on, may even need to reboot the device to get it to connect after doing this.
4. If your device is listed under devices go ahead and issue "adb reboot fastboot"
5. Once rebooted issue "fastboot devices" and make sure the device is listed again.(If not listed make sure you have your driver's installed correctly and fastboot is installed correctly, may need to install Android SDK into same folder as fastboot)
6.You can select English or whatever language if you want but it doesn't seem necessary.You are in fastbootd mode you will see if you DO select a language.
So from here issue"fastboot reboot bootloader" device will reboot and you will have scrollable option at the top beginning with a big green START at the top. This is regular fastboot And where you wanna be to get your unlock code for submitting to Oppo for your unlock token.
7. Issue "fastboot oem get_unlock_code"
8. It should return the info you need, you will also need your IMEI number when submitting so be sure to copy that down.
you can copy and paste the unlock code into notepad or Word and delete out the extra stuff so your left with just the two lines of your unlock code as one single contiguous string of numbers.
8. Go to the link listed by OP and submit the required info. And wait for what seems like forever.
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
PsYk0n4uT said:
ADB/Fastboot commands-quick recap.
1. adb reboot fastboot
2. fastboot reboot bootloader
3. fastboot oem get_unlock_code
Click to expand...
Click to collapse
Simply "adb reboot bootloader". You won't need fastbootd until GSIs (which I already did ofc).
Thanks, definitely a quicker way to get to fastboot. I guess I wasn't sure if you could reboot directly. Seems maybe I was confusing an older device where you had to reboot to fastboot then "fastboot reboot fastboot" to get to fastbootd for a whole different reason.
This one goes directly to fastbootd when you "adb reboot fastboot"
Nice catch.
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
I'm not really sure to be honest, this is my first OnePlus device and just trying to contribute anything I can to get the N20 section up and going as I make progress with the device.
Just a quick search though turns up this and maybe it could be of use if you can still access the bootloader.
the current image(boot/recovery) have been destroyed
I updated my oneplus 8t to KB2005_11.C.11 (OOS 12 ) by first booting to twrp-3.6.1_11-0-kebab.img and then flashed the KB2005_11_C_OTA_1100_all_362b9b_10100001.zip. After the upgrade I had no mobile data on t-mobile and had Volte instead of 5g...
forum.xda-developers.com
Someone mentions extracting the boot.img from stock image and flashing it. I would imagine it should work for you if the stock firmware can be found and circumstances are similar. Maybe at least a start. Wish I could be of more help, maybe someone else can chime in that knows more.
Try Linux, maybe a live dist. if your on a windows machine that won't recognize it just to get it into a state that you can work with it again.
Just an idea, I don't want to steer you wrong as i still have a lot to learn
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsettinghav
Click to expand...
Click to collapse
DrScrad said:
with this particular model in scope, what do either of you guys suggest I do if I have gottne the age old bricked message "destroyed boot/recovery image"".. I've tried the MSMTool route and cna't get it to register under Device Manager with the Qualcomm drivers.. It's highly upsetting..
Click to expand...
Click to collapse
I want to try and help but I'm so new it's sketchy I don't want to say something and get bashed
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Fyi according to a recently made friend who also had the 7 digit serial issue, they were told by OnePlus their dev team is working on an OTA update that will resolve the serial number issues. I'm not sure how that's going to work but I saw the email between them and Oppo support
I guess this must be a widespread issue that they feel is cheaper to invest the amount of money it takes for r&d to come up with a fix than it was to replace a few devices or attempt to do remote repairs.
But this also makes me wonder what avenue they will take to correct the issue.
Also I wonder if someone with the right skillset could gather enough bootloader unlock codes along with the unlock tokens, serial, IMEI, pcba etc.. maybe the algorithm their using to generate the codes could be broken. I'm no crypto expert or math genius either, but if we have the variables to the equation minus one but have the answer, isn't this pretty simple almost pre-algebra?
I mean I guess their not worried about enough people being brave enough to give out sensitive info like that. But maybe Im just ignorant of the complexity of these algorithms.
64 digit key on one end
T-Mobile bought sprint and they have T-Mobile sims no. But I understand that sprint is still a somewhat seperate company (tried to buy a T-Mobile phone and it would not activate on my sprint account. So I bought this from the sprint side of the T-Mobile site so I knew it would work but I assume this is a sprint phone and not a T-Mobile phone so this method would not work.
Can anyone confirm this?
PsYk0n4uT said:
Please feel free to comment. Don't worry about the trolls. We would love to have you to be part of this conversation. If you have suggestions just post them, and if your unsure about anything just mention that you are. It's a great way to learn. Don't worry about negative feedback, take it as constructive criticism. You may find that the feedback can clear up many questions and/or misconceptions. You never know how your dialogue with other members could help someone else in the future. These forums are here to document all of it just for that purpose. We are all here to learn or help others who want to learn. Though this account is only a year old I have been around these forums on and off for many years and I learn something each and every time I come in search of wisdom. I'm by no means an expert but I find that others benefit from my questions and answer just as much as I have over the years.
Click to expand...
Click to collapse
okay peep theres a way i put my oneplus into efu mode, hold both vol up and down then put usb c in continue to hold u should hear PC recognize it
So, before i do it, would deleting the modemst1/modemst2 partitions still let me bypass the t-mobile sim lock and let me unlock the phone like it did on the old oneplus phones?
Flashed a patched boot.img and lost modems. Anyone willing to post the modems? Are they device specific like a device partition?
Sim locked and trying to recover. No radios are working