I succeeded in doing the following:
1) downgrade my tablet to a rootable fw version
2) rooted with doomlord tool
Now I need to unlock my bootloader: I had requested the key a while ago, but never got around to using it.
I followed all the instructions and succeeded in connecting the tablet in fastboot mode to my pc (drivers installed fine and I receive a reply when issuing the trial command getvar version, meaning, I presume that the device is connected and able to receive commands and reply to them).
However when I issue the command in the instructions on http://unlockbootloader.sonymobile.com/instructions and replace the final "KEY" with the key provided by Sony via email I receive a reply "FAILED (remote: Command did not succeed)": what could I be doing wrong? I also copied and pasted the command in order to make sure that the syntax was correct and checked the code I input many times to make sure I did not miss or messed up something, but it all seems OK. I issued the command from within the same directory where the getvar command was issued, i.e. within Android SDk/Tools folder (the procedure on the website doesn't suggest to change folder, so I didn't!) , but no success at all!
Can anyone suggest some way out?
Thanks
Luca
astrovale said:
I succeeded in doing the following:
1) downgrade my tablet to a rootable fw version
2) rooted with doomlord tool
Now I need to unlock my bootloader: I had requested the key a while ago, but never got around to using it.
I followed all the instructions and succeeded in connecting the tablet in fastboot mode to my pc (drivers installed fine and I receive a reply when issuing the trial command getvar version, meaning, I presume that the device is connected and able to receive commands and reply to them).
However when I issue the command in the instructions on http://unlockbootloader.sonymobile.com/instructions and replace the final "KEY" with the key provided by Sony via email I receive a reply "FAILED (remote: Command did not succeed)": what could I be doing wrong? I also copied and pasted the command in order to make sure that the syntax was correct and checked the code I input many times to make sure I did not miss or messed up something, but it all seems OK. I issued the command from within the same directory where the getvar command was issued, i.e. within Android SDk/Tools folder (the procedure on the website doesn't suggest to change folder, so I didn't!) , but no success at all!
Can anyone suggest some way out?
Thanks
Luca
Click to expand...
Click to collapse
Sorry if this is a dumb question, but is bootloader unlocking allowed on your tablet ?
Some service providers have blocked bootloader unlocking.
GretaLewd said:
Sorry if this is a dumb question, but is bootloader unlocking allowed on your tablet ?
Some service providers have blocked bootloader unlocking.
Click to expand...
Click to collapse
I followed the procedure on the Sony website to check that and the answer is yes, it can be unlocked.
I tried some other tutorials and no results. It seems that it might be connected to the doomlord exploit (which I used to gain root access), but all the instructions on how to get around that have failed to allow me the unlocking!!!!
astrovale said:
I followed the procedure on the Sony website to check that and the answer is yes, it can be unlocked.
I tried some other tutorials and no results. It seems that it might be connected to the doomlord exploit (which I used to gain root access), but all the instructions on how to get around that have failed to allow me the unlocking!!!![/QUOTE
SOLVED
Click to expand...
Click to collapse
I read other threads with the same issue, before post this , but i cant solve it yet
Rooted HDX 4.5.5.3 -Check
Set developer mode on the Kindle -Check
Allow USB Depuration before proceed -Check
Downloaded ADB Composite Drivers / Unlock Bat's / ADB Interface- Check
I run as admin both files without problems, abut the error appears when kindle reboots "Unlock Failed- Unlock code is not correct"
(The files are placed on the correct site,by the way)
I tried
Download again ADB + Fastboot
Reinstall ADB Composite Drivers
Reboot Kindle
Download again Unlock files from original thread
Erase mutiple times unlock.code
No sucess at this point
Any suggestion its apreciated, serial number seems ok
I dont try downgrade yet , because someone post recently he bricks his device using this procedure, so i prefer stay away if is possible.
Yousucks2 said:
I read other threads with the same issue, before post this , but i cant solve it yet
Rooted HDX 4.5.5.3 -Check
Set developer mode on the Kindle -Check
Allow USB Depuration before proceed -Check
Downloaded ADB Composite Drivers / Unlock Bat's / ADB Interface- Check
I run as admin both files without problems, abut the error appears when kindle reboots "Unlock Failed- Unlock code is not correct"
(The files are placed on the correct site,by the way)
I tried
Download again ADB + Fastboot
Reinstall ADB Composite Drivers
Reboot Kindle
Download again Unlock files from original thread
Erase mutiple times unlock.code
No sucess at this point
Any suggestion its apreciated, serial number seems ok
I dont try downgrade yet , because someone post recently he bricks his device using this procedure, so i prefer stay away if is possible.
Click to expand...
Click to collapse
You need to install a vulnerable bootloader before unlocking. See step #2 in OP of linked thread. Scroll to the end of that thread to secure the referenced files as links in the OP are dead. Proceed with caution; a simple mistake can yield a world of hurt and potentially an unrecoverable device.
If your device is rooted you do NOT need to downgrade.
Yeah im following the steps correctly, i try again on my desktop tonight with Windows Vista , i think its some issue with W10 FCU on the laptop, when i tried unlock bootloader on my Blu Life One X2 on w10 , the system show excatly the same issues with unlocking tools, i repply the results
Yousucks2 said:
Yeah im following the steps correctly, i try again on my desktop tonight with Windows Vista , i think its some issue with W10 FCU on the laptop, when i tried unlock bootloader on my Blu Life One X2 on w10 , the system show excatly the same issues with unlocking tools, i repply the results
Click to expand...
Click to collapse
Can you boot into TWRP after completing step #2 of the unlock procedure? If not it is likely the vulnerable bootloader (ABOOT) was not properly installed.
Step #2 can be performed independent of steps #1 and #3. IMO it should be the first step taken after rooting. There is no need to generate an unlock code (step #1) prior to installing and testing the vulnerable bootloader and TWRP (step #2).
Davey126 said:
Can you boot into TWRP after completing step #2 of the unlock procedure? If not it is likely the vulnerable bootloader (ABOOT) was not properly installed.
Step #2 can be performed independent of steps #1 and #3. IMO it should be the first step taken after rooting. There is no need to generate an unlock code (step #1) prior to installing and testing the vulnerable bootloader and TWRP (step #2).
Click to expand...
Click to collapse
Sucess on my desktop PC , i have fully working TWRP and unlock code at the first try, dont know why fails on my laptop every time i tried, on the Blu Life X2 the bootloader and TWRP needs be patched to work on W10 , probably some issue with drivers or something weird, if someone have this issue try on other computer with old OS, thanks for the assistance
what should I do when vulnerable bootloader (ABOOT) was not properly installed
Davey126 said:
Can you boot into TWRP after completing step #2 of the unlock procedure? If not it is likely the vulnerable bootloader (ABOOT) was not properly installed.
Step #2 can be performed independent of steps #1 and #3. IMO it should be the first step taken after rooting. There is no need to generate an unlock code (step #1) prior to installing and testing the vulnerable bootloader and TWRP (step #2).
Click to expand...
Click to collapse
I can't boot into TWRP after installing aboot_vuln.mbn. What should I do now? My tablet can only get into fastboot.
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
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