Related
It looks like Huawei has made available an official method to unlock the bootloader.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=preUnlock
But i haven't tried it yet. Maybe it could lead to something useful.
both way to obtain product ID doesn't work on cm10 rom, maybe I need to use stock rom.
borisxiao said:
both way to obtain product ID doesn't work on cm10 rom, maybe I need to use stock rom.
Click to expand...
Click to collapse
tested on hwmod's c232B005 rom with bart's kernel, doesn't work either.
Rumbi said:
It looks like Huawei has made available an official method to unlock the bootloader.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=preUnlock
But i haven't tried it yet. Maybe it could lead to something useful.
Click to expand...
Click to collapse
The form doesn't work correctly. Poor Huawei, they need to get some help from WEB professionals ...
If I select "Tablet" then "Huawei Mediapad" form the two select boxes then it is impossible to fill the IMEI/MEID field.
However if you press the "SUBMIT" button the system says "The IMEI/MEID can contain numbers and letters only.".
The procedure to find the "Product ID" is wrong, or it is not for the MediaPad tablet and doesn't work.
The string they suggest to type in the phone *#*#1357946#*#* or in the calculator ()()1357946()()
doesn't bring up any "Product ID" on my tablet. Probably this number is for other devices.
I just unlocked my MediaPad device by typing:
Code:
fastboot oem unlock
So I believe this device was not really LOCKED.
hwmod said:
The form doesn't work correctly. Poor Huawei, they need to get some help from WEB professionals ...
If I select "Tablet" then "Huawei Mediapad" form the two select boxes then it is impossible to fill the IMEI/MEID field.
However if you press the "SUBMIT" button the system says "The IMEI/MEID can contain numbers and letters only.".
The procedure to find the "Product ID" is wrong, or it is not for the MediaPad tablet and doesn't work.
The string they suggest to type in the phone *#*#1357946#*#* or in the calculator ()()1357946()()
doesn't bring up any "Product ID" on my tablet. Probably this number is for other devices.
I just unlocked my MediaPad device by typing:
Code:
fastboot oem unlock
So I believe this device was not really LOCKED.
Click to expand...
Click to collapse
wow, that looks easy...
hwmod said:
...
So I believe this device was not really LOCKED.
Click to expand...
Click to collapse
I also don't see in what aspect the device should have been locked, fastboot flashing stuff worked right out of the box. Not even fastboot oem unlock was needed.
mblaster said:
I also don't see in what aspect the device should have been locked, fastboot flashing stuff worked right out of the box. Not even fastboot oem unlock was needed.
Click to expand...
Click to collapse
Correct ...
However I tried "fastboot oem unlock" as soon as I bought back in December.
Now with the following "fastboot" command my device shows:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
OKAY [ 0.004s]
finished. total time: 0.004s
while we have tested that for some others users it is:
Code:
fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
OKAY [ 0.004s]
finished. total time: 0.004s
You can try with your and see what you get.
I had a problem,.
I install Mediapad_2.06.26_OsiMood - Light gets Lighter on my Pad.
Now, I can not test CyanogenMod, because it is not come in "fastboot"
How can I do, thank you
anyone has any alternative to unlock the fastbooot Huawei Mediapad 7 v302u
If you have locked bootloader just flash older fw version. This or something older http://download-c.huawei.com/tcpsdownload/downLoadCenter?category=&flay=software&downloadID=NDYyNDc=
Rumbi said:
It looks like Huawei has made available an official method to unlock the bootloader.
http://www.huaweidevice.com/worldwide/servicePolicy.do?method=preUnlock
But i haven't tried it yet. Maybe it could lead to something useful.
Click to expand...
Click to collapse
This website doesn't work, there is not even a way to select MediaPad as of 7/28/2013
hwmod said:
The string they suggest to type in the phone *#*#1357946#*#* or in the calculator ()()1357946()()
doesn't bring up any "Product ID" on my tablet. Probably this number is for other devices.
I just unlocked my MediaPad device by typing:
Code:
fastboot oem unlock
So I believe this device was not really LOCKED.
Click to expand...
Click to collapse
the correct string in the calculator is ()()1357946()()=
you forgot the '=' sign...
but when I type your code in adb I get " FAILED <remote: please input key>
So then I tried to type*
Code:
fastboot oem unlock <product key I obtained from above mentioned method>
then it says: Unlocking...
OKAY [0.038 sec]
Finished. Total Time..
But the MediaPad reboots and goes into "Failed" wrong key or something of that sort, and still cannot get over the fastboot lock. Can anyone please help?
Corn Flake said:
Everything what was said there about unlocked bootloader for hws73xx. I am not sure if there is fw with unlocked bootloader for lite. Try to send email to [email protected] with your S/N number, IMEI and product id and request for bootloader unlocking code.
Click to expand...
Click to collapse
I sent an email to that address and I got the following reply from HuaWei:
From: [email protected]
Sent: Sunday, July 28, 2013 5:17 PM
Subject: 答复: i need bootloader unlock code for my mediapad
Dear Customer,
Thank you for contacting Huawei device.
Sorry that there have no bootloader unlock code for the MediaPad items.
Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team.
Please someone HELP ME unlock the fastboot, because this is the only firmware <<<HUAWEI MediaPad Firmware(S7-302u, Android 4.0, C235B001, EN, Network Function)>>> that I find perfectly working the way I need it, except I cannot install SU and CWM to root it because of this fastboot lock thing... I REALLY NEED HELP! PLEASE!!!
I have the TMobile Springboard 303u version, still waiting on network unlock code from tmobile... wonder if that code is going to work to unlock the bootloader too?
of only superuser you can try this way. inject su binary & superuser.apk to the official rom with linux command. set permission. then reflash it to your mediapad. but this can't fix the unlocked bootloader problem. this just add a superuser to official rom.
danisukses said:
of only superuser you can try this way. inject su binary & superuser.apk to the official rom with linux command. set permission. then reflash it to your mediapad. but this can't fix the unlocked bootloader problem. this just add a superuser to official rom.
Click to expand...
Click to collapse
i did the unthinkable! (I am so stupid) In the effort to get a working unlocked bootloader, I stubbornly flashed the wrong bootloader by using the attached application [NOTE to everyone - do NOT use this attachment for anything! you will brick your device! i am only attaching it in hopes that somebody will fully understand what i've done & troubleshoot and help/guide me in the process of unbricking my device]
So can somebody please help me unbrick my device? I am a noob and I have Windows 7 Ultimate. I don't even know how to use Linux. The sad part is that I got SU and root right before I did this stupidity. I got root and SU with the software from this website: http://www.unlockroot.com/unlockroot.html
so officially now I am really begging for HELP with step-by-step instructions on how to unbrick my device? (again - I flashed the wrong bootloader from the attached file).
can you enter to bootloader (fastboot) mode?
danisukses said:
can you enter to bootloader (fastboot) mode?
Click to expand...
Click to collapse
No. Dead. Device doesn't even look like it is turning on, which is expected when one flashes the wrong bootloader. this is brick-brick dead. it doesn't get any worse than this...
maybe the JTAG method can fix it. but JTAG method is only for professional who really2 know how to use the tools.
danisukses said:
maybe the JTAG method can fix it. but JTAG method is only for professional who really2 know how to use the tools.
Click to expand...
Click to collapse
what is JTAG method? are their detailed instructions for the T-Mobile Springboard? If there are detailed instructions for this specific device, then I can definitely do it. I've been pretty good so far at following all the instructions here. I've flashed many ROMs here, etc. The only time I get in trouble is when I go off and do stupid things like flashing the wrong bootloader... I'll never do that again! So yeah - any step-by-step instructions for Windows 7 user?
you can find it on google. it use some toolkit to flashing the board directly from PC.
Unlock code recived from Huawei support about 3 hours ago
try to install "twrp recovery for mediapad" - done
try to find people, who can build CM mod
hwmod said:
The form doesn't work correctly. Poor Huawei, they need to get some help from WEB professionals ...
If I select "Tablet" then "Huawei Mediapad" form the two select boxes then it is impossible to fill the IMEI/MEID field.
However if you press the "SUBMIT" button the system says "The IMEI/MEID can contain numbers and letters only.".
The procedure to find the "Product ID" is wrong, or it is not for the MediaPad tablet and doesn't work.
The string they suggest to type in the phone *#*#1357946#*#* or in the calculator ()()1357946()()
doesn't bring up any "Product ID" on my tablet. Probably this number is for other devices.
I just unlocked my MediaPad device by typing:
Code:
fastboot oem unlock
So I believe this device was not really LOCKED.
Click to expand...
Click to collapse
where to write this? and how to get the adb file for media pad 7 youth (S7-701u)
---------- Post added at 03:18 PM ---------- Previous post was at 02:47 PM ----------
danisukses said:
can you enter to bootloader (fastboot) mode?
Click to expand...
Click to collapse
where to get the ADB file?
Hey everyone,
So I've been having a problem with my Z Ultra that I haven't been able to solve for a number of weeks now.
The service menu on my C6833 specifically says that the bootloader is unlockable, as shown here:
(imgur) com/OO9549 (sorry, XDA won't let me post links yet. ><)
However, when I try unlocking using Sony's official instructions (and using FlashTool) - I get the following:
fastboot -i 0x0ffce oem unlock 0x(my key here)
...
FAILED (remote: Command did not succeed)
finished. total time: 0.027s
I've copied/pasted the key, I've typed it out manually, they all get me the same error. I'm running Windows 8.1 (finally managed to get the drivers installed), yet this also happened on a Windows 7 machine. I've been racking my brain, but I can't find ANYTHING that'll help. The last time I tried, I gave up trying to unlock the bootloader and installed the DualRecovery for locked bootloaders, which ended up bricking my phone and I had to flash back to stock.
Help! I just want to be able to install custom roms again! D:
Hmm, that's strange. I've googled a bit and you're not the first xperia owner with this issue. Some say that updating or re-flashing the ROM will fix it. Which version are you running?
LordManhattan said:
Hmm, that's strange. I've googled a bit and you're not the first xperia owner with this issue. Some say that updating or re-flashing the ROM will fix it. Which version are you running?
Click to expand...
Click to collapse
I've re-flashed the ROM a few times on different versions. I'm currently on 4.2.2 - 14.1.B.2.257.
Mandersoon said:
Hey everyone,
So I've been having a problem with my Z Ultra that I haven't been able to solve for a number of weeks now.
The service menu on my C6833 specifically says that the bootloader is unlockable, as shown here:
(imgur) com/OO9549 (sorry, XDA won't let me post links yet. ><)
However, when I try unlocking using Sony's official instructions (and using FlashTool) - I get the following:
fastboot -i 0x0ffce oem unlock 0x(my key here)
...
FAILED (remote: Command did not succeed)
finished. total time: 0.027s
I've copied/pasted the key, I've typed it out manually, they all get me the same error. I'm running Windows 8.1 (finally managed to get the drivers installed), yet this also happened on a Windows 7 machine. I've been racking my brain, but I can't find ANYTHING that'll help. The last time I tried, I gave up trying to unlock the bootloader and installed the DualRecovery for locked bootloaders, which ended up bricking my phone and I had to flash back to stock.
Help! I just want to be able to install custom roms again! D:
Click to expand...
Click to collapse
I had the same problem when I tried to unlock.
Tried 5 times and then was finally successful. Ensure that you have typed out the commands correctly. Don't copy and paste as that wont work.
Are you getting the same error in Flashtool?
Sent from my C6833 using Tapatalk
LordManhattan said:
Are you getting the same error in Flashtool?
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
I can't be sure as it was 3/4 months ago. Kept having issues, and I gave up. Then came back and after many attempts it worked. It was incorrect commands i was typing. 0 or O may have been the problem, or no space where they should be one.
If it says command failed then it sounds like you have the command correct, but the key is incorrect or the format of your input after the command is incorrect.
Also... are you rooted? Root first then try agian
hamdogg said:
I can't be sure as it was 3/4 months ago. Kept having issues, and I gave up. Then came back and after many attempts it worked. It was incorrect commands i was typing. 0 or O may have been the problem, or no space where they should be one.
If it says command failed then it sounds like you have the command correct, but the key is incorrect or the format of your input after the command is incorrect.
Also... are you rooted? Root first then try agian
Click to expand...
Click to collapse
I have copied/pasted, as well as typing out the commands. This has happened with Flashtool as well as in the command prompt.
And the phone is rooted.
EDIT:
I figured out the problem. I ended up using flashtool for the whole process. Windows 8.1's Driver Signature Verification NEEDS to be turned off. I ended up getting a new unlock code from Sony and that worked.
Mandersoon said:
I have copied/pasted, as well as typing out the commands. This has happened with Flashtool as well as in the command prompt.
And the phone is rooted.
EDIT:
I figured out the problem. I ended up using flashtool for the whole process. Windows 8.1's Driver Signature Verification NEEDS to be turned off. I ended up getting a new unlock code from Sony and that worked.
Click to expand...
Click to collapse
Hi Mandersoon,
I am in same problem and do you have any link or email to get new Unlock code from sony?
Thanks.
Encountered this on my first try. Then on the second attempt, it went through.
i had the same problem, it said "FAILED (remote: Incorrect format for unlock data. Should be on the form "0x)" so I did exactly as it said - added "0x" before my code and it worked!
I just removed "0x" from the unlock code given by sony, it worked like a charm. :good:
I dont know why.
BlackCatAlex said:
i had the same problem, it said "FAILED (remote: Incorrect format for unlock data. Should be on the form "0x)" so I did exactly as it said - added "0x" before my code and it worked!
Click to expand...
Click to collapse
can you please share the code i cant understand where to add 0x. i am facing the same issue. reply ASAP
Do not share the code/key. That's your unique key.
@psylbaba: it says "added "0x" before my code", so I assume he means 0x in front of the key when you're unlocking in Flashtool.
I just.....removed 0x and the <> in my code and it worked like a charm. Curious. (XZ1 user here)
Hi, found this thread when I was trying to unlock a Xperia z2, for me worked removing only the <> like this: fastboot oem unlock 0x"CODE"
Right click, administrator mode
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
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11. Many guides online seem to gloss over needing the bootloader unlocked before root. TMALSS; I'm not sure if the non-international version can be bootloader unlocked and/or if I can root without needing this. Long version of what I've tried is below:
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Thus to unlock the bootloader, I am following a guide from TWRPupdate:
It says to perform 'adb reboot bootloader' and then 'fastboot oem device-id':
Code:
C:\adb-platform-tools>fastboot device-id
fastboot: usage: unknown command device-id
My phone only reboots into normal mode whenever running reboot bootloader command within ADB.
I can run fastboot commands when I run 'adb reboot fastmode' but I don't believe this is true fastmode. As I have tried everything mentioned here, such as cables or different computers. Essentially most fastboot commands I've tried do not work except for showing my device as listed / connected.
I have also tried the drivers from LG / Google / ADB separately. And on 2 computers.
Is it possible that I don't have rescue mode or a bootloader still? As I get a black screen when entering recovery mode (but my computer recognizes A device), but adb nor fastboot does. I used to see the recovery screen logo, but I stopped seeing this screen either after updating to Android V11 or reading/backing-up the partitions in QFIL.
In last resort, I have tried rooting via patching the boot image using Magisk v23. I downloaded the firmware for my carrier, converted the KDZ to DZ via Python, and extracted the boot.img_117638 file. Given the file is 0 bytes with nothing in text edit, I still converted it to an img file. But in the kdztools android app, when I select this image file and run, I get:
Code:
!Invalid input file
!Installation failed
I'm guessing the boot.img file should have some data in it. But I'm not sure this method would even work due to the fastboot issues, especially with 'download to device' errors.
-------
I'm just at a standstill on what to even try next. I don't see many people having this much trouble unlocking/rooting their v60. Did the OTA Android v.11 break the root-ability?!
PS: Debugging and OEM unlock are both set in developer options. I can also list drivers used if need.
Thanks for the help in advance!
While digging I also found a post by alexenferman whom managed to use QFIL to root many older ZTE smartphones. They state it may but likely won't work on newer flagship phones. It's a great tutorial I'll have to try soon, but is there a reason it likely won't work here?
kyij said:
Greetings all,
I am having trouble attempting to root or even unlock the bootloader on my V60 (LM-V600TM), Android V11.
When following this guide on xda using KDZ,
I am getting stuck at Section 11.1.2:
Code:
C:\adb-platform-tools>fastboot flash frp frp.img
Sending 'frp' (512 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
Click to expand...
Click to collapse
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
NGOwner said:
Why are you even in section 11.1? You have a v600TM ... a TMobile version. Not a Verizon version. Stop. Just stop. Jump to 11.2.
If you have gotten the engineering bootloader in place, you should be good to go with 11.2.
[NG]Owner
Click to expand...
Click to collapse
Haha, I remember reading that and still continued
I am on Verizon myself using this TM model. I know the phone was unlocked to the point where I could use it with Verizon. I even got 5g using my old 4g sim card.
Anyhow.. I have tried using that command already, and get the same 'command not supported issue'.
Code:
C:\adb-platform-tools>fastboot devices
LMV600TMc40cxxxx fastboot
C:\adb-platform-tools>fastboot oem unlock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Again have tried different computers and cables as I've read fastboot can be pretty picky too.
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
NGOwner said:
Did you select/enable OEM unlock within the Developer Options under Settings/System?
[NG]Owner
Click to expand...
Click to collapse
Yes I do, I have turned it off and back on as well.
Well then at this point, I'm tapped out. Smarter folks than me will need to step in and take up the mantle.
[NG]Owner
I ended up posting a form to reddit where about 10 people insisted I did something wrong, and with little surprise -- I did.
I did not flash the engineering bootloader after saving a copy.
Makes a lot more sense since it seemed like a lot of steps to backup without actually doing anything
Thanks NG for the help too!
are you success to unlock bootloader yet. if no i will show you
adb reboot fastboot> select reboot bootloader on your phone> fastboot oem unlock