Related
SOlved:
so I was unaware that the bootloader unlock was going to be a problem before I purchased this phone... I did some research before making the purchase and it seemed all was good.
I spent $17 with DC for an unlock... all I got was some nonsense "temporary unlock" SO once I run the temp unlock the phone says "unlocked" on both the phone and the FRP.
FYI.. I also tried HCU client... and it can find the phone but then when I hit "unlock" it says something about a COM error and cant get the code... I tried this with 2 different PCs as well.
I was able to then push the TWRP recovery to it via fastboot. I then did fastboot reboot and went straight into the recovery... and no luck. it brings me right into the EMUI recovery.
is there anyway that I can at least get into TWRP temporarily since I do have the temporary bootloader unlock? or any other way that I can push supersu via fastboot?
this is very frustrating...
Ok so I CAREFULLY re read the directions for HCU... HCU is to be run while the phone is still on in the OS. not in fastboot which was my mistake all along.
so the key is to go into the dialer and enable manufacure mode... then run HCU while the phone is still on.
another key is to disable the Huawei software ... IM not sure if this is necessary but I think its a good idea because I noticed that the software itself causes the phone to go back to Hisuite mode instead of manufacturer mode. so I went into windows services and disabled hisuite... and closed out of it.
Hope this helps someone else
and do not waste your money on the DC program!!! you have to purchase your credits from DC but dont use the DC client. I am currently working on getting a refund for my first wasted credits. also they charge 15 credits for this unlock which is $18 USD! but thats not so bad considering I got this phone for $499 from newegg brand new
ilmar72 said:
SOlved:
so I was unaware that the bootloader unlock was going to be a problem before I purchased this phone... I did some research before making the purchase and it seemed all was good.
I spent $17 with DC for an unlock... all I got was some nonsense "temporary unlock" SO once I run the temp unlock the phone says "unlocked" on both the phone and the FRP.
FYI.. I also tried HCU client... and it can find the phone but then when I hit "unlock" it says something about a COM error and cant get the code... I tried this with 2 different PCs as well.
I was able to then push the TWRP recovery to it via fastboot. I then did fastboot reboot and went straight into the recovery... and no luck. it brings me right into the EMUI recovery.
is there anyway that I can at least get into TWRP temporarily since I do have the temporary bootloader unlock? or any other way that I can push supersu via fastboot?
this is very frustrating...
Ok so I CAREFULLY re read the directions for HCU... HCU is to be run while the phone is still on in the OS. not in fastboot which was my mistake all along.
so the key is to go into the dialer and enable manufacure mode... then run HCU while the phone is still on.
another key is to disable the Huawei software ... IM not sure if this is necessary but I think its a good idea because I noticed that the software itself causes the phone to go back to Hisuite mode instead of manufacturer mode. so I went into windows services and disabled hisuite... and closed out of it.
Hope this helps someone else
and do not waste your money on the DC program!!! you have to purchase your credits from DC but dont use the DC client. I am currently working on getting a refund for my first wasted credits. also they charge 15 credits for this unlock which is $18 USD! but thats not so bad considering I got this phone for $499 from newegg brand new
Click to expand...
Click to collapse
Temp unlock lets you flash anything (stock images) from fastboot. So essentially you could flash a whole firmware using only images in Fastboot mode.
Twrp don't work as you need to be unlocked to use it, even if you have Twrp it will reboot to sec_recovery when you are locked.
Do you remember wich firmware was in your phone before you unlock your bootloader?
basty95 said:
Do you remember wich firmware was in your phone before you unlock your bootloader?
Click to expand...
Click to collapse
It was c567. The latest one for the bla-a09
how temp unlock for flashing firmware in fastboot not twrp ... i need command thanks in advance
So I got this Sony Xperia X model F5121 from one of my relatives, and I ran into quite a few issues when I tried rooting it. it says Bootloader Unlock Allowed: NO, which would mean that i couldn't get into fastboot mode and unlock my bootloader but here's the very specific and weird part: I can get into fastboot mode, at least I believe so. My phone was carrier locked to Vodafone but I payed a professional to unlock that and now I can use every SIM I want. I looked online and the first XDA page said that unlocking the SIM meant that fastboot mode is unlocked as well. So I tried, I plugged my phone in while holding the volume key, a blue light popped up and it meant I was currently using fastboot mode, but when i try doing anything it says "waiting for devices" and doesnt end up working at all. Am I missing some drivers? Is it just impossible? Could one of you be kind enough to provide the needed files and some instructions for this procedure? i'm asking for a lot, I know but if there's anyone kind enough. I'm running the absolute latest version of Android 8 Sony provides.
EDIT: YEs, used adb shell, I have the ADB drivers, I tried the szuzu install or what the TWRP codename for it is, but everything just stops at "waiting for devices" and I can't do anything.
Since you are not allowed to unlock the bootloader - Bootloader unlock allowed - No, there is no way to unlock it and root it. Sorry.
even if you want to try again, make sure to force install googles drivers
instead of sonys
hello. first of all i don't speak english and i use google translate and i'm sorry for that.
I have an asus-me302kl tablet. I wanted to install twrp but now it's locked. I installed firmware with rawdate but it has no function. I need help unlocking the bootloader. recovery mode does not turn on either. I am wondering if there is a pat file or some other method to unlock the bootloader. Thanks in advance. I hope I was able to explain myself.
please help
civan34 said:
please help
Click to expand...
Click to collapse
This low-end tablet is heavily outdated ( 7 years old ), means you won't find a TWRP suitable to it.
jwoegerbauer said:
This low-end tablet is heavily outdated ( 7 years old ), means you won't find a TWRP suitable to it.
Click to expand...
Click to collapse
First of all, thanks for the answer. this tablet is a customer tablet. and it's my fault that it's locked. For this I need to unlock the bootloader. is there no tool to flash the software? I managed to install the .rawdata firmware. and the device has root permission but I couldn't go further. Now I'm waiting like this.
@civan34
My suggestion:
Re-flash tablet's Stock ROM ( is a ZIP-file ) to bring tablet back to its initial state ( what includes flashing the Stock Recovery ).
When that's done you can start to unlock tablet's bootloader by means of Fastboot, if it's not denied by OEM/Carrier.
If tablet's bootloader got successfully unlocked you can try to flash LineageOS v15 ( Android 8 Oreo ) onto tablet.
jwoegerbauer said:
@civan34
My suggestion:
Re-flash tablet's Stock ROM ( is a ZIP-file ) to bring tablet back to its initial state ( what includes flashing the Stock Recovery ).
When that's done you can start to unlock tablet's bootloader by means of Fastboot, if it's not denied by OEM/Carrier.
If tablet's bootloader got successfully unlocked you can try to flash LineageOS v15 ( Android 8 Oreo ) onto tablet.
Click to expand...
Click to collapse
I can't install the stock firmware. Doesn't allow flashing over fastboot. Doesn't allow flashing via recovery mode. Is there a program to install stock firmware?
@civan34
A Stock ROM gets flashed by means of ADB
Example command sequence:
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ZIP_ON_PC>
adb reboot
jwoegerbauer said:
@civan34
A Stock ROM gets flashed by means of ADB
Example command sequence:
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ZIP_ON_PC>
adb reboot
Click to expand...
Click to collapse
I am a little novice at the command line and do not know how to type the command you typed. Should I type as you wrote, or do I need to change the name of the zip on the computer?
my command
(adb sideload stock.zip) and I get read error for this command.Since I don't speak English, I didn't understand exactly how to write the command. I don't want to overwhelm you, sorry for that
I'm in the same boat.
I picked up 4 of these from an auction. I can't unlock any of them, because the Asus tool, (ME302KL_UnlockTool_Instructions) zip file, no longer works. TWRP is available 3.2, link is below. I have rolled back to the stock ROM on 2 of the machines, no joy. Any suggestions or guidance, would be greatly appreciated. Thanks.
https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Link to Asus Unlock file
https://drive.google.com/file/d/1mzntnfm5OlHbKd1cYkd1YEFs6CYeKqmn/view?usp=sharing
jbone899 said:
I picked up 4 of these from an auction. I can't unlock any of them, because the Asus tool, (ME302KL_UnlockTool_Instructions) zip file, no longer works. TWRP is available 3.2, link is below. I have rolled back to the stock ROM on 2 of the machines, no joy. Any suggestions or guidance, would be greatly appreciated. Thanks.
https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Link to Asus Unlock file
https://drive.google.com/file/d/1mzntnfm5OlHbKd1cYkd1YEFs6CYeKqmn/view?usp=sharing
Click to expand...
Click to collapse
I contacted Asus a few times about this Bootloader issue, but today I took a different approach. It appears they Blacklisted the ME302KL from the servers, because it is EOL. I made it clear to them. that I can't access the Asus Cloud or any other Asus tool loaded on the machine and I can't do OTA updates either. I made it clear that I should be able to at a minimum be able to upgrade to 4.4.4 from 4.2.2 after resetting the device. They agreed and are escalating the issue up the food chain.
My hope is they remove it from the blacklist which will fix the "Network Error" message when trying to use the Unlock Tool for the bootloader. I will circle back around, once I hear back from them....
jbone899 said:
I contacted Asus a few times about this Bootloader issue, but today I took a different approach. It appears they Blacklisted the ME302KL from the servers, because it is EOL. I made it clear to them. that I can't access the Asus Cloud or any other Asus tool loaded on the machine and I can't do OTA updates either. I made it clear that I should be able to at a minimum be able to upgrade to 4.4.4 from 4.2.2 after resetting the device. They agreed and are escalating the issue up the food chain.
My hope is they remove it from the blacklist which will fix the "Network Error" message when trying to use the Unlock Tool for the bootloader. I will circle back around, once I hear back from them....
Click to expand...
Click to collapse
No joy. Asus says they are under contract with AT&T. The ME302KL has been black listed and Asus will not add it back to the unlock tool or provide any support AT ALL!. They keep telling me the unlock tool isn't theirs. But the amount of times Asus's name is used in the EULA, tells me otherwise. I'm waiting to hear back from AT&T on their position on the matter. Stay tuned...
Ok campers, i have a work around for the ME302KL AT&T bootloader issue. I just verified AT&T can unlock the devices, they just verified 3 devices for me. Only catch, you have to have an account with them.
So, If you like people actually being able to hear you on a call, you probably have a different service, like i do. Based on the call, there are really only 2 options. Option 1, Harassment. Someone you know, has them as their provider. A family member, a friend maybe your priest. So, my suggestion is to harass them into they adding the device, under their plan. They only need to do it long enough, for you to get it upgraded. Once AT&T unlocks it, upgrade the OS, add TWRP and create a custom recovery that never goes back to KitKat. then, have them cancel it off their account. At the most, you're looking at $25 for the month, if anything at all.
Option 2 - Go Prepaid for a couple of months. This one is tricky based on the T&C's on their website. You will need to create a new account, $30 for 5 5gb a month. No contract and what you don't use, rolls over to the next month. Make sure to read their T&C's ased on new prepaid accounts with BYOD. I told the agent I wanted to Only use broadband service, no phone for when im working in the field, until i'm still under contract with Verizon. She pitched services, i dodged and evaded. She told me a month to month prepaid plan was doable, to get it unlocked. They would be able to unlock it for free and so i could upgrade the OS. So, it's not too terrible, just annoying to jump through so many hoops. The first option, would be the easiest.
These are just suggestions. I take no responsibility if you brick the device once it's unlocked. It is AT&T and the device may be commiting suicide in lieu of being on their Network. :0)
I sent the message to AT&T with imei of my ME302KL but the answer is been "the manufacturer doesn't have an unlock code for this device".
Help me to unlock my device.
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.
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