Related
Watching the Sony Ericsson PC Application on a repair today I noticed that it was downloading and installing an update engine.
Maybe I'm day dreaming but I believe this will hold the key to the bootloader issues. This engine should be what's controlling the bootloader while loading to OS image to the Qualcomm chip.
So my hypothesis is that if we can pull this update engine out of the application by removing the rest of the application we can use the tools and UI from any of the DEV or HTC ROM loader applications to control said engine. Basically what we'd be doing is taking their tool and wrapping a new shell around it to control what we need and are legally entitled to make our devices do.
Thoughts?
--------------------------------------------------------------------------------------------------
============================================================================
--------------------------------------------------------------------------------------------------
FOLLOWING TWO PAGES OF YOUR RESPONSES:
Okay guys. The secret to the bootloader is actually inside of the PC Companion application with SEUS. We need to figure out how to wrap a different Windows UI around this. Basically take all the critical guts and use the RUU loader found on device sites like Rhodium, HD2, etc... and only use it's UI. So to get this is there a way to watch in real time what files PC Companion and SEUS are downloading while in the repair stages of operation?
If this is not possible we need to remember that SE develops a lot more Symbian than Android. Some of the chip security could be the same found in those devices. I've included a link that may help guide us. I haven't wrapped my head 100% around this concept but at least I have a strong grasp on solutions!
http:// developer. symbian. org/wiki/index.php/What_are_the_product_development_kits%3F
This product development kit is geared towards hardware and if you scroll down some will see details on accessing the Kernel Taster Kit which is a subset of the PDK which enables the creation of new baseports and device drivers. Because SE is probably using a BIOS designed for Symbian this could likely help us with our quest. Or ultimately give us a big FU to Sony and give us Symbian 3^ on our Xperia... so basically one hell of a sweet as Vivaz. The Mini Pro could replicate the Vivaz Pro.
Hey, the idea is nice. But Basically thats what was done with X10flash. X10flash is based on SEUS, it takes all update functions out of SEUS and lets us flash what we want to.
The Problem is that there is no function for flashing the Bootloader.
We have the loader.sin which controls the flashing on phone itself. What is needed is a loader.sin which unlocks Bootloader or or or
So the idea is not bad but was there before And X10flash is the result
Regards
Bin4ry
Why X10flash need the DeviceID, and SEUS not ?
I try to find a way to flash without DeviceID... is it a dream too?
Thol said:
Why X10flash need the DeviceID, and SEUS not ?
I try to find a way to flash without DeviceID... is it a dream too?
Click to expand...
Click to collapse
Flashing with a DeviceID would be tricky since you need to know what hardware the program should speak with. SEUS probably finds out the ID automatically while we have to find it manually.
then who had work about this problem ?
i want to help him... i want to know what ways are already searched... to don't loose my time in theses bad way ...
So now I have a question...
If we need to change the bootloader in order to get new roms, then why do Sony not need that?
An other thing, how is the bootloader locked, is it a des-key or what?
I am just trying to understand the problems here...
Sent from my X10i using XDA App
Thol said:
Why X10flash need the DeviceID, and SEUS not ?
I try to find a way to flash without DeviceID... is it a dream too?
Click to expand...
Click to collapse
SEUS has an automatic detection, but is is tricky to find, because we can only decompile the java JAR's which are located in plugins folder. If you decompile them you get only function names like a b c d e f g etc. And because of this its very hard to follow these.
So DeviceID is the minior Problem we have, so we don't spent time in automatic detection as we have a method with decon, grep and cut. (I think this is totally okay for now) If we have finally a way around BL we can spent more time in making the flashin Process with X10flash more cute.
pshdo said:
If we need to change the bootloader in order to get new roms, then why do Sony not need that?
Click to expand...
Click to collapse
Because the firmware is signed
The problem is less the flashing. Even if we can flash what we want the Bootloader checks the signature on every boot, so we are running the wrong way to think about altering the flash process. We must look in other areas.
Regards
Bin4ry
had you try to switch the X10 BL with an another device with same specs ?
Bin4ry said:
Because the firmware is signed
The problem is less the flashing. Even if we can flash what we want the Bootloader checks the signature on every boot, so we are running the wrong way to think about altering the flash process. We must look in other areas.
Regards
Bin4ry
Click to expand...
Click to collapse
Any luck on disassembling the BL? If we're insanely lucky then all that sets the retail loader apart from the dev loader is a debug flag or something. It would seem counterintuitive to write a complete separate bootloader just for development when the standard qualcomm should work just fine.
Even if we don't have access to the unsigned loader from SE we could perhaps compare the X10 bootloader with the stock one from Qualcomm's SDK and if those look similar. If the SE one is a modified version of the reference BL we might be able to figure out what bits to flip in order to enable debug-mode.
Bin4ry said:
Because the firmware is signed
The problem is less the flashing. Even if we can flash what we want the Bootloader checks the signature on every boot, so we are running the wrong way to think about altering the flash process. We must look in other areas.
Regards
Bin4ry
Click to expand...
Click to collapse
So if I understand correct (I probably don't), then the more updates Sony put out, the more likely it is that we can figure out how the lock works ?
All the updates from Sony should pass that lock in order to work, right?
Sent from my X10i using XDA App
Thol said:
had you try to switch the X10 BL with an another device with same specs ?
Click to expand...
Click to collapse
Tryed and failed (Was one of the first thing we tryed )
ddewbofh said:
Any luck on disassembling the BL? If we're insanely lucky then all that sets the retail loader apart from the dev loader is a debug flag or something. It would seem counterintuitive to write a complete separate bootloader just for development when the standard qualcomm should work just fine.
Even if we don't have access to the unsigned loader from SE we could perhaps compare the X10 bootloader with the stock one from Qualcomm's SDK and if those look similar. If the SE one is a modified version of the reference BL we might be able to figure out what bits to flip in order to enable debug-mode.
Click to expand...
Click to collapse
Yep thats what i'm trying. The original Qualcomm does not load, but we must have some value which can be set on S1Loader because if you take a look with a simple hexeditor then you see some normal strings which are about Debug etc.
So feel free to help me pushing the Loader through IDA or smth. to find a way to do smth.
I think if we can manage to find the DBG value we could be lucky and get the S1Loader switch our normal BL to DEV or DBG mode.
Worth a try
pshdo said:
So if I understand correct (I probably don't), then the more updates Sony put out, the more likely it is that we can figure out how the lock works ?
All the updates from Sony should pass that lock in order to work, right?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
No sorry. There is no way to crack the key. Its to hard encoded, with actual power of Computers you will calculate the key for approx 10^27 years
Even if you have 1000 updates :/
Regards
Bin4ry
Bin4ry we believe in your mathematic scientic powers!
Go go go ! You will have pscychological support from us !!!
Everybody.. support our team !
GO GO crack the boot you can do it ! The people believe in you !!!! I believe in you ! My wife believe in you
We love you man !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Bin4ry said:
No sorry. There is no way to crack the key. Its to hard encoded, with actual power of Computers you will calculate the key for approx 10^27 years
Even if you have 1000 updates :/
Regards
Bin4ry
Click to expand...
Click to collapse
Thank you for the answer...
Someone have cracked lots of other stuff in the past, eg satellite and a lot other things, so if someone can setup a search engine, perhaps we can all help... it COULD be hard, but no one know for sure...
But that offcource means that we need to know exactly what we are looking for...
Is it kind of a management key or?
Not that I know anything about searching offcource...
Sent from my X10i using XDA App
Hello Binary,
When you try to flash a new boot loader does it check that you're flashing a valid loader or will it let you flash anything you want? And if you were to flash anything you want (even just a whole load of 0s) would that mean that your phone would be destroyed or is there a recovery method? Can you simply write back over it with a good loader?
Also, has anyone read out the SE loader? And if so can it be disassembled? And if that has been done, roughly how many lines of assembly code is it?
Sorry about all the questions but I'm interested in this stuff but it's awkward to find a good starting point.
Sent from my X10i using XDA App
This is the official FunkyHuawei support thread.
FunkyHuawei is a (mostly) paid service which allows you to do the following:
1. Install the latest system software, even before it's released by OTA.
2. Install beta/prerelease system software, without needing to be a beta tester.
3. Recover a bricked phone.
4. Rebranding / Change the region of your phone (China -> Europe, for example, to get Google and so on.)
5. Root your EMUI 8 phone, even with stock recovery (This feature is free)
Except for rooting, all of these features are supported even if you cannot unlock your phone's bootloader.
To find FunkyHuawei, please Google it. Or you can find a link to the service within the following XDA Portal article.
https://www.xda-developers.com/android-oreo-emui-6-huawei-mate-9/
We are pleased to announce FHUnbrickFlashTool -- You can now repair any recent Huawei phone via fastboot, even if you cannot access eRecovery or boot the phone! Even if it doesn't show the Huawei logo, as long as you can get a fastboot connection to your computer, you can recover the phone! Google FHUnbrickFlashTool or check FunkyHuawei's reddit for details.
In cooperation with XDA, FunkyHuawei is offering a free credit to Recognized Developers and Recognized Contributers on XDA.
Please PM me for more details.
We will continue posting in this thread with updates regarding new software versions and releases regarding this device.
We will also be monitoring it so we can help anyone who has issues.
For device-specific information, please see the next post.
P10 Device-Specific Information
The P10 now has a relatively mature community with many methods to do many things.
However, there are still some things only possible with FunkyHuawei, so it would be most useful for:
1. Installing updates on bootloader-locked devices, even if the update is not approved by Huawei for your device.
2. Rebranding bootloader-locked devices, or rebranding to obscure carrier brandings.
3. Restoring bricked devices.
Note that even though the Mate 10 Root tool is designed for the Mate 10, it works perfectly on the P10 running Android O betas.
This tool is FREE, and might be easier than installing TWRP and rooting that way.
Frequently Asked Questions
Q: How much does FunkyHuawei cost?
A: You need to buy credits on the FunkyHuawei website. The price per credit varies depending on the number of credits you buy. Different operations cost different amounts of credits. However, the Root feature of the Mate 10 tool is free, and as mentioned above, Recognized Developers/Contributors of XDA can ask for a free credit.
Q: My phone is bootloader locked, and FRP locked. My bootloader unlock code dosen't work. It won't boot. eRecovery doesn't work. Can you help?
A: Yes. With the Mate 10 this is now a common situation. Contact FunkyHuawei for help in this situation. We'll need to access your computer remotely and the procedure is a little bit complicated, but the phone can be unbricked.
Q: I can't get my bootloader unlock code/don't want to unlock my bootloader, but I want to change my phone to something other than Chinese. Can you help?
A: Yes. Our new FunkyHuawei Rebrand Tool works on ALL recent Huawei phones, to rebrand them to another region even when the bootloader is locked.
Q: I'm not seeing the latest version listed on FunkyHuawei or elsewhere as an OTA. Why not?
A: Huawei has a very odd and unpredictable way of rolling out OTA updates. You can use FunkyHuawei to install the new version immediately, or can wait for the update to be rolled out. It might be a month or more after release until the update reaches your device from Huawei directly. We have no idea why.
Q: Why isn't FunkyHuawei free?
A: Because many of FunkyHuawei's features cost FunkyHuawei money to provide. Features that don't cost FunkyHuawei money to provide, like rooting the Mate 10 or our TWRP build for Mate 9/Oreo, for example, are generally made available for free. There are also bills to pay, kids to put through school, and so on.
Q: I noticed FunkyHuawei in an XDA Portal article!
A: FunkyHuawei loves XDA, and is cooperating with them as much as possible. Recognized Developers and Contributors on the XDA forums are welcome to claim a free credit from FunkyHuawei as well.
Q: I have a different question.
A: This is what this thread is for! Post away!
duraaraa said:
P10 Device-Specific Information
The P10 now has a relatively mature community with many methods to do many things.
However, there are still some things only possible with FunkyHuawei, so it would be most useful for:
1. Installing updates on bootloader-locked devices, even if the update is not approved by Huawei for your device.
2. Rebranding bootloader-locked devices, or rebranding to obscure carrier brandings.
3. Restoring bricked devices..
Click to expand...
Click to collapse
Luckilly the P10 community here is mature enough that there is no longer a need for Funky's services. However effective Funky may be, we can save ourselves the 30bucks and do it ourselves
We are pleased to announce FHUnbrickFlashTool -- You can now repair any recent Huawei phone via fastboot, even if you cannot access eRecovery or boot the phone! Even if it doesn't show the Huawei logo, as long as you can get a fastboot connection to your computer, you can recover the phone! Google FHUnbrickFlashTool or check FunkyHuawei's reddit for details.
We have added a brand new Android O build for the Chinese P10.
You will need to rebrand your phone to VTR-AL00 (all/cn) to install it.
Best to use HiSuite to install it -- check out Mate 10 rebranding information to find the correct version of HiSuite and instructions.
We now have Android O for International P10 and P10 Plus.
Check FunkyHuawei reddit for install instructions, or google for "Android O Builds for International P10 and P10 Plus now available! Instructions inside"
This is great news!!
If I only got some $:crying: but nice news
Does this include Treble?
tiktok1 said:
Does this include Treble?
Click to expand...
Click to collapse
Yes, of course.
Hey all, I'm having a problems to which i've been pulling my hair out and not sure what to do. Essentially, I had my phone rooted, although later decided I wanted to unroot. To unroot I used an app called "simply unroot" however it did not fully unroot my device, just made it worse, my phone does not pass the safety net, however "root checker apps" suggest my phone is not rooted, although some apps recognise my phone as being rooted. My phone bootloader is unlocked, but the OEM toggle in the developer options is not set as enabled, and is NOW greyed out so i cant click it, meaning i do not have access to any fastboot commands and thus cannot flash a recovery.img. Although, believe after having trying to unroot it had automatically disable OEM. I have tried to lock the bootloader in the hopes that OEM toggle would no longer be greyed out, but cannot do this as i dont have access to fastboot commands. Even with TWRP i cannot flash anything just promps me with Error 9. I have tried storing the UPDATE.app within the dload folder, but that doesnt work either. I have no idea how i can recover this device. Fell like i've tried everything. Please help.
rustymole said:
Hey all, I'm having a problems to which i've been pulling my hair out and not sure what to do. Essentially, I had my phone rooted, although later decided I wanted to unroot. To unroot I used an app called "simply unroot" however it did not fully unroot my device, just made it worse, my phone does not pass the safety net, however "root checker apps" suggest my phone is not rooted, although some apps recognise my phone as being rooted. My phone bootloader is unlocked, but the OEM toggle in the developer options is not set as enabled, and is NOW greyed out so i cant click it, meaning i do not have access to any fastboot commands and thus cannot flash a recovery.img. Although, believe after having trying to unroot it had automatically disable OEM. I have tried to lock the bootloader in the hopes that OEM toggle would no longer be greyed out, but cannot do this as i dont have access to fastboot commands. Even with TWRP i cannot flash anything just promps me with Error 9. I have tried storing the UPDATE.app within the dload folder, but that doesnt work either. I have no idea how i can recover this device. Fell like i've tried everything. Please help.
Click to expand...
Click to collapse
Why you pose this question in the "official funkyhuawei support" thread is beyond me....
Only thing that comes to mind is: do you have USB debugging enabled in the developers options? It should be enabled if you want to use ADB or Fastboot.
rustymole said:
Hey all, I'm having a problems to which i've been pulling my hair out and not sure what to do. Essentially, I had my phone rooted, although later decided I wanted to unroot. To unroot I used an app called "simply unroot" however it did not fully unroot my device, just made it worse, my phone does not pass the safety net, however "root checker apps" suggest my phone is not rooted, although some apps recognise my phone as being rooted. My phone bootloader is unlocked, but the OEM toggle in the developer options is not set as enabled, and is NOW greyed out so i cant click it, meaning i do not have access to any fastboot commands and thus cannot flash a recovery.img. Although, believe after having trying to unroot it had automatically disable OEM. I have tried to lock the bootloader in the hopes that OEM toggle would no longer be greyed out, but cannot do this as i dont have access to fastboot commands. Even with TWRP i cannot flash anything just promps me with Error 9. I have tried storing the UPDATE.app within the dload folder, but that doesnt work either. I have no idea how i can recover this device. Fell like i've tried everything. Please help.
Click to expand...
Click to collapse
You can use FunkyHuawei eRecovery method to return it to stock.
I recently updated my P10 VTR L29 C432 from nougat to Oreo B360 via oreoupgrade script method as posted in forum but after update my bootloader seems to be locked again i wanted to root my phone via installing TWRP but it's not allowed by fastboot
Any solution or any solution to unlock bootloader or root the phone without losing data !? I have too much files and apps on phone that i won't lose
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
Question in title, so far I cannot found anything to solve this problem, not to mention Nokia does not offer official bootloader unlocking
Perhaps @hikari_calyx knows
mingkee said:
Perhaps @hikari_calyx knows
Click to expand...
Click to collapse
are you actually sure? like, Nokia just doesn't let you unlock their phones' bootloader, plus he doesn''t have my device, so how is he able to develop a tool to unlock it?
AltFantasy said:
are you actually sure? like, Nokia just doesn't let you unlock their phones' bootloader, and I actually asked someone on Discord if there's another way, and they said I need to use the EDL tool with a flash file that contains an unlock key, but both I (and they) do not know how to make the file
Click to expand...
Click to collapse
The poster found a patch of bootloader and I used it to unlock 8.3 bootloader and eventually rooted it.
mingkee said:
The poster found a patch of bootloader and I used it to unlock 8.3 bootloader and eventually rooted it.
Click to expand...
Click to collapse
cool, but there's no support for the Nokia X10, it's just released last June, and the poster might not support my phone
mingkee said:
The poster found a patch of bootloader and I used it to unlock 8.3 bootloader and eventually rooted it.
Click to expand...
Click to collapse
Well, apparently they do not support my model (which is the X10). Their tool can only detect the phone, not unlock its bootloader
Well, Nokia/HMD wants to have their phones and tablets deadlocked, and 8.3 is my only and final Nokia Android phone.
No more.
Good Morning,
I have arrived at this thread looking for how to unlock the bootloader of my Nokia X10/X20 for later rooting it.
It seems that there is no way to do it.
To do Root I have found this link (is in Spanish): https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/
The option «Enable OEM unlocking», comes in gray and is not accessible, with which I have not been able to apply this solution.
I have found this other article: How to Unlock Bootloader on Any Nokia Smartphone.
Someone has tried?
If the answer is affirmative, does it work?
If nobody has tried it, do you think it can work?
All the best
gonzo1963 said:
Good Morning,
I have arrived at this thread looking for how to unlock the bootloader of my Nokia X10/X20 for later rooting it.
It seems that there is no way to do it.
To do Root I have found this link (is in Spanish): https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/#comment-41075
The option «Enable OEM unlocking», comes in gray and is not accessible, with which I have not been able to apply this solution.
I have found this other article: How to Unlock Bootloader on Any Nokia Smartphone.
Someone has tried?
If the answer is affirmative, does it work?
If nobody has tried it, do you think it can work?
All the best
Click to expand...
Click to collapse
Nope, the "buying unlock bootloader keys" (I meant the thing in the "How to Unlock Bootloader on Any Nokia Smartphone" article, the official way also does not work anymore, due to the site is dead) way does not work on the Nokia X10/20 (the creators of those keys confirmed with me that it's literally impossible to unlock those phones and potentially any future Nokia phones).
The "Enable OEM unlocking" should not be not accessible, my Nokia X10 does not have that option greyed out.
About the tool used in the Spanish site? I'm not so sure about whether it will work or not. The tutorial video shows a different phone, but it seems so legit. Try it at your own risk, I guess.
AltFantasy said:
Nope, the "buying unlock bootloader keys" (I meant the thing in the "How to Unlock Bootloader on Any Nokia Smartphone" article, the official way also does not work anymore, due to the site is dead) way does not work on the Nokia X10/20 (the creators of those keys confirmed with me that it's literally impossible to unlock those phones and potentially any future Nokia phones).
The "Enable OEM unlocking" should not be not accessible, my Nokia X10 does not have that option greyed out.
About the tool used in the Spanish site? I'm not so sure about whether it will work or not. The tutorial video shows a different phone, but it seems so legit. Try it at your own risk, I guess.
Click to expand...
Click to collapse
Good morning,
Thank you very much for the answer, but I inform you:
My phone is new, just arrived from the provider (Nokia directly).
-Modelo: TA1332.
-Compilation 00WW_1_070.
-Android 11.
-Actualization May 5, 2021
I have not modified anything, and I assure you that the «Enable OEM Unlocking» option, is gray and is not accessible.
A rectification, I think.
The link in Spanish: https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/#comment-41075
In the article, not in the video; It refers to a Qualcomm chip, but requires that the "Enable OEM Unlocking" option is unlocked.
Three questions apart:
1.- Is there any way to root this smartphone?
2.- Is this option valid to make a backup of the ROM?: [Tutorial] How to use Miracle Box to backup Qualcomm Android firmware
3.- And is it to restore the ROM?: [Tutorial] How to use Miracle Box / Thunder to flash firmware to Qualcomm devices
All the best
gonzo1963 said:
Good morning,
Thank you very much for the answer, but I inform you:
My phone is new, just arrived from the provider (Nokia directly).
-Modelo: TA1332.
-Compilation 00WW_1_070.
-Android 11.
-Actualization May 5, 2021
I have not modified anything, and I assure you that the «Enable OEM Unlocking» option, is gray and is not accessible.
A rectification, I think.
The link in Spanish: https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/#comment-41075
In the article, not in the video; It refers to a Qualcomm chip, but requires that the "Enable OEM Unlocking" option is unlocked.
Three questions apart:
1.- Is there any way to root this smartphone?
2.- Is this option valid to make a backup of the ROM?: [Tutorial] How to use Miracle Box to backup Qualcomm Android firmware
3.- And is it to restore the ROM?: [Tutorial] How to use Miracle Box / Thunder to flash firmware to Qualcomm devices
All the best
Click to expand...
Click to collapse
Apparently, the creators of the site that sells bootloader unlocking keys for Nokia phones said that you should ignore sites like the Spanish link, because those websites write similar content for every device that exists and just replace the device name and publish it again, then again for another device. But I guess you can try using it and see, I guess?
For the first question, I don't think you can root the phone with Magisk? You need some files inside the ROM file, but there's no ROM files for Nokia X10/20.
For the second and third question, I do not know if the tool even works. I do ask the creators of that site (again), and I quote:
I don't think they will work. The only way to trigger EDL on the device would be to disassemble and then short the testpoint to trigger EDL. But what next? What do you aim to do while in EDL mode?
We do not know which bytes are written on the chip that remembers the unlocked status. So, even in EDL mode, there isn't much that we can tinker and re-write to the device. I am also unsure if the user firmware that hmd ships to the Nokia Care includes EDL programmer, they never did for the Nokia 7.2 (the last Nokia device I really tried to play around with). Without the programmer, none of the EDL flash tools will work and we can't load just any programmer. It has to be signed by the OEM. A wrong/invalid/modified firehose programmer can put the device into a non-recoverable state.
HMD hasn't done much magic into making the phones more appealing to the buyers. But they have money and time to make more mess behind the scenes to make their devices more secure (which they think is better).
Sorry for the rant, but there's no meaningful ways to unlock the Nokia X10/20 and possibly any forthcoming phone.
Click to expand...
Click to collapse
In conclusion: It's impossible, but you can try? (Try it at your own risk of course, you could brick the whole thing, and nothing will fix it.) I do not even know if it's possible or not, so... eh?
gonzo1963 said:
Good morning,
Thank you very much for the answer, but I inform you:
My phone is new, just arrived from the provider (Nokia directly).
-Modelo: TA1332.
-Compilation 00WW_1_070.
-Android 11.
-Actualization May 5, 2021
I have not modified anything, and I assure you that the «Enable OEM Unlocking» option, is gray and is not accessible.
A rectification, I think.
The link in Spanish: https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/#comment-41075
In the article, not in the video; It refers to a Qualcomm chip, but requires that the "Enable OEM Unlocking" option is unlocked.
Three questions apart:
1.- Is there any way to root this smartphone?
2.- Is this option valid to make a backup of the ROM?: [Tutorial] How to use Miracle Box to backup Qualcomm Android firmware
3.- And is it to restore the ROM?: [Tutorial] How to use Miracle Box / Thunder to flash firmware to Qualcomm devices
All the best
Click to expand...
Click to collapse
Also, next time you buy a phone, just go buy a Samsung/Xiaomi or whatever brand that do support unlocking their phones' bootloader and pray that the phone you bought in the future got tons of custom ROMs ported to it or something, Nokia thinks that locking their phones' bootloader will make those phones more secure, which is purely bull****. If you ABSOLUTELY have to buy a Nokia phone however, go buy an older one, cause the site with unlock keys only support those old phones, and it might be impossible to even unlock new phones coming from Nokia in the future.
AltFantasy said:
Also, next time you buy a phone, just go buy a Samsung/Xiaomi or whatever brand that do support unlocking their phones' bootloader and pray that the phone you bought in the future got tons of custom ROMs ported to it or something, Nokia thinks that locking their phones' bootloader will make those phones more secure, which is purely bull****. If you ABSOLUTELY have to buy a Nokia phone however, go buy an older one, cause the site with unlock keys only support those old phones, and it might be impossible to even unlock new phones coming from Nokia in the future.
Click to expand...
Click to collapse
Good afternoon,
Thank you very much for all the information you have given me.
It has no solution, I bought an X10 and an X20, because they have Android One and will have updates for 3 years.
I thought I could unlock it and do root, and I see that it is impossible or it is very difficult.
All the best
gonzo1963 said:
Good afternoon,
Thank you very much for all the information you have given me.
It has no solution, I bought an X10 and an X20, because they have Android One and will have updates for 3 years.
I thought I could unlock it and do root, and I see that it is impossible or it is very difficult.
All the best
Click to expand...
Click to collapse
Wait, you bought both? Well, if you're trying to root them, then too bad, it's literally impossible. But if you're just using both phones normally, I would say: They're actually pretty good! The specs are great for medium gaming, the build quality is really nice, the cameras are not bad honestly. They're slightly overpriced, but they felt nice enough to use daily. Too bad Nokia ruined these phones with the bootloader unlocking problem though, and I swear I'll never buy a Nokia again, cause of this problem, even though they might be one of the best phones I've ever used.
Good evening,
I have tried to do what they explain in the article in Spanish: https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/ and it has been impossible to do anything.
I have found the following problems:
1.- The option "Enable OEM unlocking", comes in gray and is not accessible on the smartphone.
2.- You can not extract the "boot.img" file, because at the link that explains how to do it: https://www.ayudaroot.com/actualizar/alternativa-para-conseguir-la-rom-de-un-telefono-movil/ do not explain how to do it for this smartphone, which is "Qualcomm", not "MTK"; with which it is impossible to extract it.
3.- The "Qualcomm" and «ADB» drivers that are installed with the application are not worth connecting the Nokia X10 to the computer, I had to uninstall them so that the computer itself detects the smartphone.
4.- You can not unlock the bootloader in the way they explain it, so nothing can be done.
5.- The video of the end still confuses more, it is not for this smartphone or a similar one.
Therefore, the item is not useful.
Better forget it and not waste time.
Greetings
gonzo1963 said:
Good evening,
I have tried to do what they explain in the article in Spanish: https://www.ayudaroot.com/root/nokia/como-hacer-root-al-nokia-x10/ and it has been impossible to do anything.
I have found the following problems:
1.- The option "Enable OEM unlocking", comes in gray and is not accessible on the smartphone.
2.- You can not extract the "boot.img" file, because at the link that explains how to do it: https://www.ayudaroot.com/actualizar/alternativa-para-conseguir-la-rom-de-un-telefono-movil/ do not explain how to do it for this smartphone, which is "Qualcomm", not "MTK"; with which it is impossible to extract it.
3.- The "Qualcomm" and «ADB» drivers that are installed with the application are not worth connecting the Nokia X10 to the computer, I had to uninstall them so that the computer itself detects the smartphone.
4.- You can not unlock the bootloader in the way they explain it, so nothing can be done.
5.- The video of the end still confuses more, it is not for this smartphone or a similar one.
Therefore, the item is not useful.
Better forget it and not waste time.
Greetings
Click to expand...
Click to collapse
Weird, my OEM unlocking is not greyed out.
jukyO said:
Weird, my OEM unlocking is not greyed out.
Click to expand...
Click to collapse
mine too, but then it's a useless feature anyway, cause Nokia does not let anyone to unlock its phones' bootloaders
jukyO said:
Weird, my OEM unlocking is not greyed out.
Click to expand...
Click to collapse
AltFantasy said:
mine too, but then it's a useless feature anyway, cause Nokia does not let anyone to unlock its phones' bootloaders
Click to expand...
Click to collapse
Good Morning,
After installing all security updates, it has also been made accessible.
It is no longer gray, but it does not work for nothing, since there is no way to unlock it.
Regards
gonzo1963 said:
Good Morning,
After installing all security updates, it has also been made accessible.
It is no longer gray, but it does not work for nothing, since there is no way to unlock it.
Regards
Click to expand...
Click to collapse
also, I think you should try contacting their customer service, and hope that they'll accept or something. If not, keep on annoying them with the "Can you unlock my phones' bootloaders?" question, and see if they will answer or not.
Hey brothers , am a random guy looking forward to get my brand new Nokia x10 soon. And according to all paragraphs I read above it seems the main thing I need from this device apart from daily usage is inaccessible which it ""unlocking the bootloader"* But am not totally sure if it's still impossible because it's almost a year since you're conversing and it seemed to be impossible according to what I've looked at in your Conversations. Back to the topic- I got a Nokia service-center in my area here so I need your advise if I'll be able to take there the Nokia x10 and they unlock the bootloader "Incase I buy it" on their end because there have access to everything I assume whereas they're working for Nokia but it looks risky for me to get a device before am sure if it'll go up with what I need from it.......In conclusion if any of you knows a method to unlock the bootloader currently "because it's almost a year when it was impossible". You may advise me before making the mistake I'll regret. Goodnight
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
TLDR; I am wondering if all U.S. phones with Snapdragon cannot be normally rooted by just enabling OEM unlock/unlocking bootloader and must be rooted in an expert/costly method. Or if accounts from people saying they enabled OEM unlock on their Moto G Powers I read were not just fictional or with non-U.S. phones.
Click to expand...
Click to collapse
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked. I found this to be the case with the (unlocked, not carrier-specific) U.S. Moto G Power 2021 phone I just bought. I cannot tick OEM Unlocking in Developer settings, it's greyed out. I found users here and on other forums saying that it's possible to conventionally root Moto G Power 2021 phones, which I thought up till recently because I easily got an ID from the Motorola website, but obviously couldn't proceed with fastboot because OEM Unlocking is disabled and I can't change that. (in CMD fastboot said exactly this: OEM must be unlocked to proceed.)
Oddly, some users said that the option stopped being greyed out after a few days or a week. I contacted Motorola to see if this is a design thing but they were of no help, just telling me not to root as if I was unaware it voids warranty. Notably, just as many users said that the option would always be disabled, which began to make sense given what I learned next.
It was soon after I found people saying that all U.S. Android phones with Snapdragon consciously lock bootloader. All carrier-specific and unlocked varieties. (Consequently, there are services that do it for you, but this costs money and I'm interested in a phone I can root myself for free.) I was surprised it took me as long as I did to hear of this, and afterwards I searched for this specifically to get more clarity but didn't find any articles or documentation. It explains everything, of course, except for why I read some people (including here) were able to enable OEM Unlocking on their Moto G Power 2021 devices. (perhaps they were not U.S. phones but this was not mentioned.)
At this point if there's no way to enable OEM unlock I'm simply going to return the phone as I want a phone that I can root.
Snapdragon Androids disabling OEM unlock/bootloader unlocking is simply because of U.S. company decisions, because non-U.S. Android phones with Snapdragon do allow it. Because of this, I'm looking at international/European GSM Androids with Snapdragon, (such as the Xiaomi Mi A3) which the majority of anywhere-near-recent Androids clearly have, that would allow me to do this. I'm going to be as sure as I can it will be compatible in the U.S. (I use AT&T) and that it will be feasible to root for free.
Thanks for reading, especially if you got this far.
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
jwoegerbauer said:
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
Click to expand...
Click to collapse
Motorola system partition is write-protected, the bootloader must be unlocked for permanent root.
KindleMatchLight said:
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked...
Click to expand...
Click to collapse
See the CID and OEM unlock posts
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
If you get the bootloader unlocked
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
sd_shadow said:
Motorola system partition is write-protected, the bootloader must be unlocked for permanent root.
Click to expand...
Click to collapse
Absolute nonsense.
KindleMatchLight said:
Hi, I have no doubt this is a common question, but I'm here because after researching all day on this website and others, I have heard conflicting narratives and want to see if I can get some clarity with someone who has knowledge on this.
I live in the U.S. What I understand is that all U.S. Android phones with the Snapdragon chipset are impossible to easily root because they cannot have their bootloaders unlocked. I found this to be the case with the (unlocked, not carrier-specific) U.S. Moto G Power 2021 phone I just bought. I cannot tick OEM Unlocking in Developer settings, it's greyed out. I found users here and on other forums saying that it's possible to conventionally root Moto G Power 2021 phones, which I thought up till recently because I easily got an ID from the Motorola website, but obviously couldn't proceed with fastboot because OEM Unlocking is disabled and I can't change that. (in CMD fastboot said exactly this: OEM must be unlocked to proceed.)
Oddly, some users said that the option stopped being greyed out after a few days or a week. I contacted Motorola to see if this is a design thing but they were of no help, just telling me not to root as if I was unaware it voids warranty. Notably, just as many users said that the option would always be disabled, which began to make sense given what I learned next.
It was soon after I found people saying that all U.S. Android phones with Snapdragon consciously lock bootloader. All carrier-specific and unlocked varieties. (Consequently, this there are services that do it for you, but this costs money and I'm interested in a phone I can root myself for free.) I was surprised it took me as long as I did to hear of this, and afterwards I searched for this specifically to get more clarity but didn't find any articles or documentation. It explains everything, of course, except for why I read some people (including here) were able to enable OEM Unlocking on their Moto G Power 2021 devices. (perhaps they were not U.S. phones but this was not mentioned.)
At this point if there's no way to enable OEM unlock I'm simply going to return the phone as I want a phone that I can root.
Snapdragon Androids disabling OEM unlock/bootloader unlocking is simply because of U.S. company decisions, because non-U.S. Android phones with Snapdragon do allow it. Because of this, I'm looking at international/European GSM Androids with Snapdragon, (such as the Xiaomi Mi A3) which the majority of anywhere-near-recent Androids clearly have, that would allow me to do this. I'm going to be as sure as I can it will be compatible in the U.S. (I use AT&T) and that it will be feasible to root for free.
Thanks for reading, especially if you got this far.
Click to expand...
Click to collapse
You must wait, I believe it was several days of the device being online (wifi at least) to get it to permit unlocking the bootloader. I know with mine (US Xfinity Wireless), out of the box, it was gray, but 2 or 3 days later it was able to be toggled and I unlocked and got Magisk installed easily, using the patch stock boot.img method, and flashing it via fastboot beyond that. So you can do it, just can't do it before you activate the thing properly I think is the main block there you're describing. So perhaps those outside the US (with US models they can't toggle) can connect to a VPN'd wifi network and have it look like it's in the US, maybe.
There's a lot that can be done on these with just tinkering to get it there is all. But make sure you have your stock firmware is all, so you can quickly get it back into bootloader and just a flash away to fix anything really.
jwoegerbauer said:
Absolute nonsense.
Click to expand...
Click to collapse
Okay. Legit question here... How does one go about injecting SU binary to the system on the moto g 2021 series with secured boot?
Why should SU binary get housed in /system/... ? It's irrelevant where it's located, the main thing is that it's available and executable. Even Magisk doesn't store it in /system/.. but in /data/..
Because folder /data/local/tmp by default is mounted as RW my recommendation is to store it there. Using this storage place isn't conflicting with SELinux and/or AVB.
Code:
adb devices
adb push <FULL-PATH-OF-SU-BINARY-ON-PC-HERE> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/su"
When you have to run a shell command what requires elevated rights, then you run
Code:
adb devices
adb shell "/data/local/tmp/su -c '<SHELL-COMMAND-HERE>'"
Deleted member 1890170 said:
To root a phone's Android it isn't needed to unlock phone's bootloader. Android is rooted as soon as SU binary is present in Android's file system.
Click to expand...
Click to collapse
it needs to be unlock