As in the title, I have an, Alcatel Tcl Lx A502dl, Android phone, originally purchased from Walmart with a Trackfone Sim card (Now there is no sim card insterted).
I have spent all day, up until now, figuring out how to link abd and fastboot to the phone using USB debugging, and I have been successful this far. I had downloaded latest "platform-tools_r29.0.1-windows" from here on XDA, and I downloaded latest "fatsboot" from "HighonAndroid.com", for a quicker experience, without wasting time and effort on Java downloads. In addition to all this, I let the computer search the network for updating driver software, for my Alcatel phone. I also downloaded "UniversalAdbDriverSetup", from the former link, @highonandroid.com.
I linked both file pathways for corresponding "Fastboot", and "platform-tools", into the environment variables, under the term: "Path", yes, using a ";" with no spaces to add the new pathways.
I had success linking my phone onto the "abd" program, the phone is listed under "abd devices" command. I could not seem to get a listing of my phone serial number, under the "fastboot devices" command?
I have tried to get "platform-tools" to put the phone into "fastboot/bootloader" mode, but the phone simply reboots, back to the lockscreen. I have also tried on "Fastboot", to "fastboot reboot bootloader", and my Alcatel again reboots to the lockscreen. All the while, I activated the OEM unlocking switch/setting in the "developer options" of my phone, from the beginning, before I ever gave any commands?
Why won't my Alcatel phone reboot into the "fastboot/bootloader" screen, where I could command "fastboot oem unlock"? Why does my phone respond to both programs, yet still she loads the lockscreen?
I am new to all this, not really a tech savvy individual, just wanted a liberated operating system for my line of work...
I need bootloader unlocked in order to root my device via computer, correct?
I can not check to see if my bootloader is unlocked, not by abd tools, or by numerical code in my "dialer app". The app crashes, and any time I attempt the "fastboot oem device-info" command, no device is listed, only a <looking for a device> prompt of sorts appears. I have been told this may be because, the drivers were not installed properly, or the device was not properly connected under some other issue, and I can try to fix this error by reinstalling drivers... what would the issue be?
I need help, and I would appreciate some guidance on rooting my Android, as there are not any threads in the forum, on this model of Alcatel, that I am aware of?
I am doing all of this on a Windows 7 computer, in a Library, just so you all know. I ask for administrative approval for most things.
Thank you.
tcl trackfone
Hello i was wondering if you ever got your phone rooted?
me to i have that problem on my tcl lx
to
Temporary mtk- root. Use init.d for always root
Sonjouten said:
Temporary mtk- root. Use init.d for always root
Click to expand...
Click to collapse
I can't possibly express how much I would love for you to elaborate on the 'use init.d for always root' part. Anyone else who knows, please jump in. Start by pretending I am an idiot. Then stop pretending and explain it to me as if I were an adult who needs a full-time minder. First one to help me achieve "always root" on this terrible, wretched, little excuse for an electronic device gets my undying gratitude and um, maybe some Google Play money? I am open to ideas here on that score. To reiterate, need help rooting my Tracfone TCL LX A502DL that has a castrated recovery (seriously, you can't flash anything from adb, the option is flat-out missing) and apparently no fastboot access AT ALL. I could do another seriously in parentheses, but you need to take my word for it w/o a bunch of examples. The bright spot is the vulnerability the device has to the mtk-su exploit. Get a # in like no time at all. Time elapsed from executing the file to getting the prompt is too short for my flesh computer to register (unless you -v, then about 1.5 seconds.) So how do I turn a root prompt into full root?
I can't possibly express how much I would love for you to elaborate....
Click to expand...
Click to collapse
WHAT HE SAID
+1
X2
etc
Thank you, H
Did he get that?
So did he earn that Google Play Store money or was he just full of it?
Just bumping this thread in case anyone has ideas for me. Seems like Alcatel has bootloader mode hidden on some phones. Here's my story: https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
BTW - I am using mtk-su and have root and Magisk via init.d scripts, but still can't touch /system or flash recovery because of
Code:
/dev/block/dm-0' is read-only
which won't change unti bl unlocked...
I never did get her to root. Alas she is a broken phone now RIP. Sorry for the disappointments. But I move on more hopeful. ?
As posted by Viva La Android in another thread about the tcl a501dl:
The TCL A1 (A501DL) cannot be bootloader unlocked. Although the OEM Unlocking option can be enabled in the Developer Options menu, fastboot mode has been made inaccessible by TCL. Because the bootloader cannot be unlocked, it simply is not possible to flash a custom recovery or a patched boot image for systemless root support. System-wide root is not possible due to TCL's secure boot chain configuration and dm-verity. Until an exploit is found to bootloader unlock this device, rooting is not possible.
Click to expand...
Click to collapse
levone1 said:
Just bumping this thread in case anyone has ideas for me. Seems like Alcatel has bootloader mode hidden on some phones. Here's my story: https://forum.xda-developers.com/showthread.php?p=81780645#post81780645
BTW - I am using mtk-su and have root and Magisk via init.d scripts, but still can't touch /system or flash recovery because of
Code:
/dev/block/dm-0' is read-only
which won't change unti bl unlocked...
Click to expand...
Click to collapse
I have tried everything, and can't even get temporary root on my A502DL. How did you do this, if you don't mind? Thanks!
fliproc said:
I have tried everything, and can't even get temporary root on my A502DL. How did you do this, if you don't mind? Thanks!
Click to expand...
Click to collapse
Sorry, I honestly don't remember now - I just happened to have tje phone for a short time at that moment, so I was messing around with it... I remember there was nothimg special about it. I jist followed the instructions from the mtk-root thread and it worked.
Amazing Temp Root for MediaTek ARMv8 [2020-08-24] | XDA ...
Braadleyah said:
As in the title, I have an, Alcatel Tcl Lx A502dl, Android phone, originally purchased from Walmart with a Trackfone Sim card (Now there is no sim card insterted).
I have spent all day, up until now, figuring out how to link abd and fastboot to the phone using USB debugging, and I have been successful this far. I had downloaded latest "platform-tools_r29.0.1-windows" from here on XDA, and I downloaded latest "fatsboot" from "HighonAndroid.com", for a quicker experience, without wasting time and effort on Java downloads. In addition to all this, I let the computer search the network for updating driver software, for my Alcatel phone. I also downloaded "UniversalAdbDriverSetup", from the former link, @highonandroid.com.
I linked both file pathways for corresponding "Fastboot", and "platform-tools", into the environment variables, under the term: "Path", yes, using a ";" with no spaces to add the new pathways.
I had success linking my phone onto the "abd" program, the phone is listed under "abd devices" command. I could not seem to get a listing of my phone serial number, under the "fastboot devices" command?
I have tried to get "platform-tools" to put the phone into "fastboot/bootloader" mode, but the phone simply reboots, back to the lockscreen. I have also tried on "Fastboot", to "fastboot reboot bootloader", and my Alcatel again reboots to the lockscreen. All the while, I activated the OEM unlocking switch/setting in the "developer options" of my phone, from the beginning, before I ever gave any commands?
Why won't my Alcatel phone reboot into the "fastboot/bootloader" screen, where I could command "fastboot oem unlock"? Why does my phone respond to both programs, yet still she loads the lockscreen?
I am new to all this, not really a tech savvy individual, just wanted a liberated operating system for my line of work...
I need bootloader unlocked in order to root my device via computer, correct?
I can not check to see if my bootloader is unlocked, not by abd tools, or by numerical code in my "dialer app". The app crashes, and any time I attempt the "fastboot oem device-info" command, no device is listed, only a <looking for a device> prompt of sorts appears. I have been told this may be because, the drivers were not installed properly, or the device was not properly connected under some other issue, and I can try to fix this error by reinstalling drivers... what would the issue be?
I need help, and I would appreciate some guidance on rooting my Android, as there are not any threads in the forum, on this model of Alcatel, that I am aware of?
I am doing all of this on a Windows 7 computer, in a Library, just so you all know. I ask for administrative approval for most things.
Thank you.
Click to expand...
Click to collapse
I have heard elsewhere that it's not possible to unlock the bootloader of a Tracfone. Sorry. But at least we know why Tracfones are sold for so cheap lol
$cronos_ said:
I have heard elsewhere that it's not possible to unlock the bootloader of a Tracfone. Sorry. But at least we know why Tracfones are sold for so cheap lol
Click to expand...
Click to collapse
unlock bootloader and root with https://github.com/bkerler/mtkclient
This device cannot be rooted. To date, there has not been a single validated claim of a rooted TCL A509DL. The bootloader cannot be unlocked, preventing root, custom ROM installs,etc.
UPDATE: After hearing from some members regarding the Hydra Tool, and doing a little bit of research on the method, it appears that I was completely wrong on my.statement. Members here on XDA as well as Hovatek have confirmed that the A509DL bootloader can indeed be exploited with the Hydra Tool method, opening the door to systemless root with Magisk. Thanks guys for the info and guidance. I have one of these devices and look forward to unlocking & rooting soon. Thanks @PrivyetCyka for the info.
Yes it can .. it was extremely easy to do so also..i have a rooted one in my hand as we speak the only issue is I was stupid and tried to flash the magisk zip in twrp and it set off secureboot so in working on fixing that .. but .. if you just use MTKClient you can pull the entire firmware , magisk patch then reflash the boot.img using the same tool and you can even install twrp I have the entire firmware , twrp, and magisk patched boot imgs for the device saved ,. If someone knows how to disable secureboot I would really appreciate it
Viva La Android said:
This device cannot be rooted. To date, there has not been a single validated claim of a rooted TCL A509DL. The bootloader cannot be unlocked, preventing root, custom ROM installs,etc.
Click to expand...
Click to collapse
I sure would like to give it a whirl, but I haven't had that phone in over a year
Anyway, I decided to stop buying devices made deliberately less functional by their manufacturers.
PrivyetCyka said:
Yes it can .. it was extremely easy to do so also..i have a rooted one in my hand as we speak the only issue is I was stupid and tried to flash the magisk zip in twrp and it set off secureboot so in working on fixing that .. but .. if you just use MTKClient you can pull the entire firmware , magisk patch then reflash the boot.img using the same tool and you can even install twrp I have the entire firmware , twrp, and magisk patched boot imgs for the device saved ,. If someone knows how to disable secureboot I would really appreciate it
Click to expand...
Click to collapse
I stand corrected on my statement. I was incorrect. Out of curiosity, does the Hydra tool require the dongle in order to unlock the bootloader?
@PrivyetCyka send me the Magisk packed boot image and I will unpack it and disable secure boot. I can then pack it back up and link it to you. Are you referring to only secure boot or also AVB 2.0/dm-verity?
I didn't use hydra tool I used MTKClient from GitHub and did an entire system read back to have a backup then just renamed boot.bin to boot.img used magisk to patch it and then used the same MTKClient tool to reflash it... I have a twrp I made for it also but I don't know how functional it is as far as flashing things and backups , the only thing I tried to flash was the magisk zip just to see what would happen and that tripped the secureboot , I used the mediatek secureboot tool and it says it's disabled but it's still not booting past the secureboot fail screen.. when I get home I'll get the files and upload them tonight
Related
Basic device info
Model Number : PB1009
Android Version : 7.0
Kernel Version: 4.4.22
Build Number : PB1009_20170912
Hey so i need literally any way to root this tablet, ive been able to unlock the bootloader (easiest bootloader on the planet) but havent been able to find a compatable twrp.
i just need a custom recovery that will work or p much any root ideas, i would consider a full custom firmware as well.
i considered compiling a twrp but i dont know how i would get the source files for it...
Kenvarus said:
Basic device info
Model Number : PB1009
Android Version : 7.0
Kernel Version: 4.4.22
Build Number : PB1009_20170912
Hey so i need literally any way to root this tablet, ive been able to unlock the bootloader (easiest bootloader on the planet) but havent been able to find a compatable twrp.
i just need a custom recovery that will work or p much any root ideas, i would consider a full custom firmware as well.
i considered compiling a twrp but i dont know how i would get the source files for it...
Click to expand...
Click to collapse
how did you unlock bootloader and did you ever figure out how to root it? going through same thing now.
Kind of an old thread and old device now, but I own one myself (branded Packard Bell) and just figured this all out, so here goes:
Root
This one is really easy now thanks to a MediaTek flaw. Just go to https://github.com/JunioJsv/mtk-easy-su, download the latest release, install the APK on the device, and run it by opening the app and pressing the button in the lower-right corner (still works on this since the latest security patch level AFAIK is from 2017). Note that this gives root temporarily, so you will need to run it again after reboot if you want root again.
Bootloader Unlock
When Kenvarus said "easiest bootloader on the planet", I took a guess at the method and it worked:
Back up any important data on your tablet, as this will factory reset it.
Install ADB and Fastboot on your computer if they are not installed, including drivers. For Fastboot (as that can be tricky sometimes), it "just worked" for me and I think Windows used an Amazon driver I had installed for my KF2. YMMV.
If you haven't already, enable Development Settings by going to Settings->About tablet and tapping the build number 7 times.
Go to Settings->Developer options (switch them on if they're off) and enable the "OEM unlocking" toggle.
In the same menu, enable "USB debugging" if it is not enabled already.
Connect the tablet to your computer, confirming the authorization prompt that pops up if it wasn't connected before. Check whether the connection is good with the "adb devices" command if needed.
Run the command "adb reboot bootloader", this gave me a blank screen.
Use the "fastboot devices" command to make sure the Fastboot connection works.
Run the command "fastboot oem unlock".
Press Volume Up when the text-mode confirmation screen pops up on the tablet.
Once the unlock procedure is complete, reset the tablet. You should see text on your bootscreen saying "Orange State" and a factory reset on the first reboot if it worked.
WARNING: I highly recommend charging your battery to be at least 10-20% filled before doing this. I stupidly did this at 1% battery thinking "it's plugged in anyway" and had quite the time rebooting after unlocking the bootloader (I thought it was bricked for a good hour or so, only after walking away for 20 minutes to eat dinner did I see that the battery was now at 20% and I could boot the tablet).
After unlocking the bootloader and temp-rooting it with the above app, I was able to use Magisk to patch the boot image (using dd to shuttle the files to and from /dev/block/mmcblk0p10, use "strings saved_boot_partition_name|head -n1" and check for "ANDROID!" to make sure it's the right partition) and I now have persistent root after all these years (note that Direct Install in Magisk doesn't work here). I'd definitely be interested in a custom recovery and/or ROMs for this device, but I'm not holding my breath (I'd take a crack at it if I knew better how to do it, but I have near-zero experience with ROM development and so far have only recompiled existing ROMs for a few phones).
Having trouble rooting my LG K40. I have the same problem as this person when trying to boot into fastmode: https:// youtu.be/yQ99lQv0rQk?t=26
You can find his post here explaining the process more in detail: https:// lgk20.com/root-lg-k40-lm-x420-bootloader-unlock-twrp/
MODEL #: LM-X420MM
Any help is appreciated,
Thanks in advance.
im having the same problem. i must have a proclivity towards phones with what seems impossible rooting methods. the first was the samsung j7 prime and now the lg k40 lmx420mm. ive gotten as for as adb reboot-bootloader, just restarts device, fastboot commands are either not recognized or i receive "waiting on device". Ive updated drivers, followed a diff. method found on reddit posted by jamesrascal (i cant post url here because of my newb status). Phone just stays stuck in firmware update. i feel as if ive exhausted all resources, any direction or help would be appreciated, im not educated on rooting ive been successful a few times on other phones and jailbroken some iphones, im mostly doing this to learn and teach myself so it isnt urgent but i need help to continue any further. thank you
Same problem for me. Because the device has good value for the money it would be nice someone can help us here.
Further this device seems to be full android treble conform I like to know how benefit from this circomstance.
I have LG K40 LM-X420EMW with dualsim.
Thanks for every hint!
@blanksus
IIRC an Android user can not unlock the bootloader without first OEM unlocking, because without this process the device will not accept the bootloader unlocking command.
jwoegerbauer said:
@blanksus
IIRC an Android user can not unlock the bootloader without first OEM unlocking, because without this process the device will not accept the bootloader unlocking command.
Click to expand...
Click to collapse
OK, but it is not possible to get into fastboot mode to enable the OEM unlocking. I marked the slider in developer option butz still there is no chance to get in fastboot mode.
After command "adb reboot bootloader" the device always reboots in normal system mode.
@baerenbisch
Once you enabled the OEM unlock on your Android, the “unlock ability” flag is set to 1, which allows you to use the
Code:
fastboot flashing unlock
command what unlocks device's bootloader.
BTW: Once you have enabled OEM unlock, it stays on. Even if you do a factory reset, it stays unlocked until the setting is manually altered again by going into the Developer options section.
jwoegerbauer said:
@baerenbisch
Once you enabled the OEM unlock on your Android, the “unlock ability” flag is set to 1, which allows you to use the
Code:
fastboot flashing unlock
command what unlocks device's bootloader.
BTW: Once you have enabled OEM unlock, it stays on. Even if you do a factory reset, it stays unlocked until the setting is manually altered again by going into the Developer options section.
Click to expand...
Click to collapse
Hm,
may be it is "allowed" to unlock but in the "LG K40 (LM-X420EMW) real world" it is not possible.
You dont reach fastboot mode which could enable using the order you proposed.
Device reboots into standard mode instead of wanted fastboot mode after sending "adb reboot bootloader"
I think thats the problem.
Code:
[email protected]:/# adb devices
List of devices attached
LMX4205P4TU4S4HEOJ device
[email protected]:/# adb reboot bootloader
[email protected]:/# fastboot flashing unlock
< waiting for any device >
^C
[email protected]:/#
OK, good news. One can get root with this method:
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Works for LG K40 (LM-X420EMW) Android 9 Kernel 4.9.117 Patch Level January 1, 2020 Build Nr. PKQ1.190522.001 Software-Vers. V20d-EEA-XX
baerenbisch said:
OK, good news. One can get root with this method:
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Works for LG K40 (LM-X420EMW) Android 9 Kernel 4.9.117 Patch Level January 1, 2020 Build Nr. PKQ1.190522.001 Software-Vers. V20d-EEA-XX
Click to expand...
Click to collapse
Temp root does sound nice, but what can you actually do with it. Can you change the OEM unlock key?
roycrt said:
Temp root does sound nice, but what can you actually do with it. Can you change the OEM unlock key?
Click to expand...
Click to collapse
Device can be bootloader unlocked now. MtkClient on github. I have the Harmony 3 bl unlocked and twrp for it
Can confirm, I was just able to unlock the bootloader with mtkclient and root with Magisk from there.
BenTheTechGuy said:
Can confirm, I was just able to unlock the bootloader with mtkclient and root with Magisk from there.
Click to expand...
Click to collapse
Please elaborate steps taken to unlock bootloader using mtkclient. Thanks
I wrote a guide as part of my porting of postmarketOS to my K40.
LG K40 (lg-mmh4x) - postmarketOS
wiki.postmarketos.org
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.
ahsvanz
try
C:\ADB >fastboot devices
C:\ADB >fastboot OEM device-info
etc
replacing
C:\ADB with where ever you fastboot file is located
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
have you tried the code above ??
cant you just download the official original firmware and flash that ? im not familiar with the oneplus flashing techniques, ive always had samsungs except for the htc evo 3d back in the day
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
slimmynine said:
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
Click to expand...
Click to collapse
how does the one plus flash firmware ? for samsung we use a tool called odin, do you not have a similar tool for your device ?
I don't recall having any toolkit like that, but in order for the toolkit to work.. do you need to have an unlocked bootloader?
Cause the main issue is that I can't unlock it.
i dont think so, if your flashing an official firmware, but for your device i cant be sure of that
?
did you try running your commands as an su , is your device rooted ? you could try sideloading an update.zip maybe
what does it say when you flash this command ? true, true false ?
C:\ADB>fastboot OEM device-info
maybe this will help https://forum.xda-developers.com/t/...us-2-back-to-stock-100.3269543/#post-64279667
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
yeah i think some phone makers lock down the bootloader, like its unlocked but when i try to flash a gsi it says device locked state
jamsandpeabug said:
alcatel has a program to download and install firmware but the device is not listed, cannot find fw on the net
Click to expand...
Click to collapse
OK try
c:\adb
Adb fastboot oem device-info
Replacing
C:\adb
With where ever your fastboot is located
Just to check if your device is showing is oem locked or unlocked, it will display with a true or false option. I can't really advise to much as I don't have experience with that device
You could also try
fastboot oem unlock_critical
Not sure if that will work for your device though
Idk what else to recommend, are you stuck at boot ? Can u boot into recovery mode ? Do u have an ext sd card slot
OT-6025D | GSMSERVERPRO
gsmserverpro.com
Is that your firmware
Alcatel 1s Flash File Download [Stock ROM or Firmware
You can Download latest flash file and flash tools for Alcatel 1s phone here. Original stock ROM or Firmware available for free.
mobilereset99.com
Have youlooked at that
if you can confirm your phone has a mtk chipset use mtkclient to bootloader unlock it https://github.com/bkerler/mtkclient
otherwise youre out of luck
But
jamsandpeabug said:
im not stuck at boot, i want to flash gsi but it says device is in locked state even with oem unlocked in dev options, adb debugging enabled etc , and just wont let me flash.. its starts flashing and then fails due to locked state
Click to expand...
Click to collapse
If the flashing starts, and fails, the os would be overwritten and you wouldn't be able to boot. So what you mean is the process trys to start but fails, right yh then I don't know what else I can say to try and help, let's hope mtkclient is an avenue you can pursue
MOD ACTION:
Thread closed since OP has no content.
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