{CLOSED} delete - Android Q&A, Help & Troubleshooting

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.

Related

No "Enable OEM unlock" options in developer settings

Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
I had the same issue you don't need to toggle the option on marshmallow. The error looks like you need to do a sudo fastboot if your using linux.
The only other thing to remember is you need to remove the factory reset protection (frp) see here http://forum.xda-developers.com/honor-5x/help/unlock-bootloader-issues-kiw-t3411032
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
Just because that option is not available does not mean your bootloader is locked, plus you can unlock using ADB.
Just enable usb debug only
Sent from my KIW-L24 using XDA-Developers mobile app
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
This option is not there in Marshmallow. not sure if there is still a way to unlock as this option itself is not there...try enabling USB debugging couple of times and see if it prompt you for authorisation. if it does, you can still do the required things.
did u unlocked bootloder???
did u unlocked bootloder???
i m having same problem
princereshim said:
did u unlocked bootloder???
i m having same problem
Click to expand...
Click to collapse
What problem?
no oem unlock option
no oem unlock option
in developer option
princereshim said:
no oem unlock option
in developer option
Click to expand...
Click to collapse
If you are in lollipop it will be there but if u r on marshmallow then it wont be there. Just enable usb debugging and you r good to proceed.
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
How did u get the unlock code on KIW-L22 model because i have tried i dont know how many time but the emui website return me error that either model number is wrong or the verification code
Harsh007agrawal said:
, I always get stuck at
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
How did u get the unlock code on KIW-L22 model because i have tried i dont know how many time but the emui website return me error that either model number is wrong or the verification code
Click to expand...
Click to collapse
Try Chinese site to get same.
And which rom are u sing could you give me link to latest twrp and rooting files needed
Harsh007agrawal said:
And which rom are u sing could you give me link to latest twrp and rooting files needed
Click to expand...
Click to collapse
See the pinned post in the guides tab... It has all the information and links
Sent from my KIW-L21 using Tapatalk
im also getting the same problem. it does not recognize device.. im on stock marshmallow and there is no option of oem unlock
Harris Aamir said:
im also getting the same problem. it does not recognize device.. im on stock marshmallow and there is no option of oem unlock
Click to expand...
Click to collapse
Just enable the usb debugging if you r on stock mm. Try changing the usb port amd see if it work
seams rolling back is the only solution ! .
Romiui said:
seams rolling back is the only solution ! .
Click to expand...
Click to collapse
Why what happened?
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
I cant find mine either, but i have a suspicion that they just removed/edited the files to just have one state of locked and no controls or commands to unlock it.
Find out the file name and path for the "OEM unlock" setting in the developer options.
then search for it using the ADB, if the files aren't there then you might need to put the phone in to download mode and "sideload" the the full files back on to it.. if it's possible.
it might be more complicated than that. that's what i would've done as a Carrier if i wanted to keep modders and phone thieves out.
also on my Carrier phone when i put it into Download mode it seems to run like there own unlock before it does anything else, might need to run that first to unlock the lock so you can unlock it...
this is kind of a BS response, but at least it's an idea to look into. Sorry.
also you could try loading PDANet to see if the device will recognise.
Tamoghna Chowdhury from Android.stackexchange TOO NEW CAN'T POST LINKS said:
To unlock the boot loader you need to have the ADT with all the packages installed and configured.
Later once the configuration is done properly then you can connect your device and enable USB Debugging under the options.
Download Modaco’s Superboot files and save them to your computer.
Once downloaded, extract it by right clicking and extract all.
On your phone, click on Settings > Developer Options > Turn USB Debugging On.
Plug the device in to your computer via USB cable.
Open the superboot folder that we just extracted (until you see the folder with fastboot-windows inside it), then hold the shift key down on your computer and right click any blank area.
Now, select open command window here.
In the command prompt, type the following with hitting enter at the end of each line.
adb-windows reboot bootloader (and wait for the device to reboot)
fastboot-windows oem unlock
(If it gets stuck at waiting for device here, download and install PDANet on your computer, once installed, unplug then plug the device back in and see if that fixes it)
Once it runs the device should display a screen asking you if you are sure. Click yes using the volume buttons. The device will go back to the bootloader screen but say unlocked at the bottom.
Click to expand...
Click to collapse
Leftcatcher said:
I cant find mine either, but i have a suspicion that they just removed/edited the files to just have one state of locked and no controls or commands to unlock it.
Find out the file name and path for the "OEM unlock" setting in the developer options.
then search for it using the ADB, if the files aren't there then you might need to put the phone in to download mode and "sideload" the the full files back on to it.. if it's possible.
it might be more complicated than that. that's what i would've done as a Carrier if i wanted to keep modders and phone thieves out.
also on my Carrier phone when i put it into Download mode it seems to run like there own unlock before it does anything else, might need to run that first to unlock the lock so you can unlock it...
this is kind of a BS response, but at least it's an idea to look into. Sorry.
also you could try loading PDANet to see if the device will recognise.
Click to expand...
Click to collapse
Never mind, I did unlock my bootloader. Thanks for your help though.
Fixed !!!
narangkunal said:
Hey guys, I just tried to unlock my bootloader. I have obtained the unlock code and everything. I try to execute this command
Code:
fastboot oem unlock XXXX
, I always get stuck at
Code:
waiting for devices
1. I have updated my device drivers.
2. For some odd reason, the toggle for "Enable OEM unlock" is not present in the developer options.
3. Now, I have updated my KIW-L22 to B340 version recently. Maybe the toggle is removed in the recent update. Is there not any way to bring back that toggle so that I can unlock my bootloader?
Please guys, I need your help with this, if anyone has ever encountered this before, please tell me how to bring it back.
Click to expand...
Click to collapse
It's Ok,In Adb Write "adb enable oem unlocking"
I Learned That From A Video
Called:
"How To Unlock Bootloader-Huawei GR5 & Honor 5X EMUI 4.0"
From The Channel Called:"NoNDrOiD"

"The System has been Destroyed" after re-lock the bootloader

Dear all,
I bought Mi Pad 4 and it was running well, and I want to update the ROM. The device is comes with Locked bootloader.
I unlocked my Mi Pad 4 using MI Unlock. And when I try to relock it using "fastboot oem lock" command, it become suddenly comes with black screen with written: "The system has been destroyed. Press power button to shutdown".
So I entered the fastboot mode and try some command/solutions:
- My device status is locked:
E:\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
finished. total time: 0.006s
- I can't unlock it using Mi Unlock:
- Flashing using MiFlashalso not allowed since it is still locked:
- I tried to unlock using fastboot, also failed:
E:\adb>fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.003s
- The faastboot screen in my mi pad is only for around 10 Second. After that it goes to "The System has been Destroyed" stage...
Any help is appreciated, because I cant use it anymore...
Why did you even want to close the BL again?!? I dont understand anyone who does that.
And AFAIK you can flash an original Image from Xiaomi even with locked BL. But I have never done it and the guide shows a working phone..
http://en.miui.com/thread-835254-1-1.html
You need the Mi-Flash Tool. And these damn Indian people with their fake titles on youtube.. The title is english and the freaking video is hindi or whatever.. SO ANNOYING!!!
Hi, the tutorial you gave is for 'normal' xiaomi phone, where it boot normally (even its BL is locked).
In my case, I cant load the BL (It said: Destroyed). The only thing I can do is restart to fastboot state, and after 20 seconds it goes again to Destroyed state.
Ok, so I have read some other threads and what seems the "only" solution is to unlock the bootloader again.. But the other people had no problem running "oem unlock".. And you get an error, what is kinda strange.
What happens in MiUnlock? Error?
Hi, I think the main problem is current status is "The System has been Destroyed", therefore it cannot load the BL.
Meanwhile, the BL is in Locked status. So it need to be un-locked first, so I can load the new ROM.
MIUnlock is error, it said: "Current account is not bound to this device", which is strange, because previously I unlocked using it before.
I assume MIUnlock said this because the status of "System destroyed"...
Never lock if there is not 100% Xiaomi official rom inside, and better use MiFlash with "clean all and lock" option for locking.
Thanks for your suggestion. Will do that after I fix this problem..
I think you have a bricked device.. Some devices have this "test-pins", where you can enable some debug-bridge and there you could flash it (mi5 or redmi5 was that in that thread). I dont know if the Pad4 has such Pins and you would have to open the whole device.. (its not something you can access from the outside).
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Noted on that, but too risky for me to open the case..
Any other solution would be really appreciated.
thE_29 said:
But I dont know if the Pad has these test-pins, just because another Xiaomi device had it..
Click to expand...
Click to collapse
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
P.Kosunen said:
On some devices you have to login your Mi Account with MiFlash when flashing in EDL mode and account needs special permissions.
Click to expand...
Click to collapse
Yup, and I cant do that since cannot load the BL, because it's "Destroyed" right now..
Up.
Does anyone have the solution on this?
Thanks.
Seemed "bricked" to me, welcome to the bricked world dude, I have had 2 beautiful paper holder on my desk.
mac_erot said:
Up.
Does anyone have the solution on this?
Thanks.
Click to expand...
Click to collapse
The only solution was already posted several times -> open device, find test-pins, use them and flash ROM. And yet, you still ignore it everytime. THERE is no other solution for bricked devices.
And: NEVER close the bootloader again on NON official ROMs.
2 ways to try out...
1st run
"fastboot flashing unlock"
2nd
"fastboot oem reboot EDL"
Or this link if the command doesn't work
https://www.google.com/amp/s/forum....e-how-to-reboot-to-edl-fastboot-t3394292/amp/
go to service centre they will be able to restore the device using edl i hope
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Looks like it is straightforward to remove the back cover. Perhaps you can find the EDL test points on the motherboard?
https://www.youtube.com/watch?v=RZpj0k9HKTQ
Is there no possibility to enable USB Debugging without entering the miui surface?
maluc said:
I tried also all solutions, but nothing helped. EDL, fastboot, etc.
If there is a way to unlock the BL again I can go on. Otherwise there will be no chance for me to get it running.
Has anyone got a solution how I can unlock the BL again? Or flash with locked BL?
Thanks!
Click to expand...
Click to collapse
Edl with test points should work, try some different ones, maybe the ones you are trying are wrong
---------- Post added at 06:47 AM ---------- Previous post was at 06:47 AM ----------
Also, try to run fastboot erase vbmeta

In a weird position. How do I root my phone?

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

(Trackfone) Alcatel Tcl Lx [A502dl] : Help unlock bootloader & rooting

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

A3 bricked after trying to flash stock and relock

I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
marceloariel said:
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
Click to expand...
Click to collapse
Thanks for the reply. I actually tried this as well but it did not work. MiFlash just appears to be running the flash_all_lock.bat script on Windows and it failed because the bootloader was not already unlocked according to its debug logs when I ran it. I should have mentioned that above.
Not sure if it will help but did you try a factory reset?
Press and hold the Power+Volume Down buttons untill you see the android with the no command. Press and hold the Power button. Press and release the Volume Up button once then release the Power button. Then you should see some recovery options.
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
sensig said:
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
Click to expand...
Click to collapse
The issue is caused by fastboot rom containing dummy system_b image and flashing script "forgetting" to force partition A as active. If a phone has B as an active partition and someone uses flash_all_lock.bat script, the phone's screwed. No idea what brought Xiaomi to this "brilliant" idea, not only there is a higher chance to brick the phone, but the zip file is also unnecessarily larger.
With locked bootloader it isn't possible to switch active partition anymore, so the phone is a (semi)brick. EDL mode is usually used to reflash locked bootloaders.
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
There are two commands for setting active partition, depending on the fastboot version. It's either old
fastboot set_active a
or newer
fastboot --set-active=a
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
if you open flashing script file (.bat or .sh) in a text editor, you will see that fastboot is flashing system.img to system_a partition and system_other.img to system_b partition. That system_other.img is a dummy image and is not bootable. You either:
Option 1: Set active partition to A before running any stock flashing script.
Option 2: Replace system_other.img to system.img in the script.
Option 3: Force partition A after flashing userdata.img and before any lock or reboot command.
dephekt said:
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
Click to expand...
Click to collapse
I am in the same exact position with my Mi A3... did you ever resolve this and if so how?
mewcatchew said:
I am in the same exact position with my Mi A3...
Click to expand...
Click to collapse
What causes led to this behavior ?
htn711 said:
What causes led to this behavior ?
Click to expand...
Click to collapse
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
Click to expand...
Click to collapse
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting).
Click to expand...
Click to collapse
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
garylawwd said:
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
Click to expand...
Click to collapse
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
---------- Post added at 02:40 PM ---------- Previous post was at 02:30 PM ----------
htn711 said:
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
Click to expand...
Click to collapse
Did you read my posts? I get "locked state error" with fastboot commands. I can reboot bootlader in fastboot, and it tjust reboots into fastboot - thats just about all i can do. It wont let me change anything, can only get info and reboot...
mewcatchew said:
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
Click to expand...
Click to collapse
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
garylawwd said:
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
Click to expand...
Click to collapse
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
Ya I wouldn't go trusting some random Russian site either. I don't think there is anything you can do without either
A) going into edl and using a verified mi account
B) bringing it to a service centre (which nobody wants to do)
In fastboot you can't get any commands to work now right? Your device is fully locked again?
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
That Russian site is run by the XDA guy from what I understood. There are other paid services which have Xiaomi service accounts, I only pointed you to the cheapest "verified" eshop. Just Google another one if you don't trust Russians. All of them will need to connect to your PC over Teamviewer and do the flashing, you will just follow the instructions (connect the phone, reboot it etc.).

Categories

Resources