After I seen two threads regarding QPST/CDMA Workshop, I decided to give it a try too.
However, I had the problem with drivers, which I luckily solved.
Drivers source: http://catalog.update.microsoft.com...updateid=14df499c-c71f-4152-a63b-1c1e40cfc14c
So, here's the solution for everyone:
1. Unzip the attached archive.
2. adb shell, su, echo 1 > /sys/devices/virtual/usb_composite/modem/enable
3. Open Device Manager. Under unknown devices you'll find two "SEMC HSUSB" devices.
4. For both, install drivers from the folder.
You'll get unsigned driver warning, ignore and continue with installation.
5. Reboot phone.
6. adb shell, su, echo 1 > /sys/devices/virtual/usb_composite/diag/enable
7. QPST/CDMA workshop should detect the phone now.
I won't link QPST (I don't know if there are any copyright barriers), but you can find it extremely easy on Google. You want QPST 2.7 build 355.
If you're asked for SPC code, it's default 000000.
Now, I need testers: anyone with locked bootloader, or bootloader unlocked with Omnius/SEtool, please open EFS Explorer and tell me if there's anything inside cert, client-cert and client-key folders. Alternatively, try to find any SE/SEMC certificates in EFS.
Best regards
64 bit vista won't let me install. any chances you can make this.
trent6gol said:
64 bit vista won't let me install. any chances you can make this.
Click to expand...
Click to collapse
Strange. What error are you getting?
Thanks no error messages at all!
Good. Is your bootloader locked?
No new hardware are detected, even with modem enable set to 1
Im in Xperia arc unlocked by setool
Alejandrissimo said:
No new hardware are detected, even with modem enable set to 1
Im in Xperia arc unlocked by setool
Click to expand...
Click to collapse
Just turn on modem mode and install provided drivers for both HSUSB devices in Device Manager.
Blagus said:
Just turn on modem mode and install provided drivers for both HSUSB devices in Device Manager.
Click to expand...
Click to collapse
When I set the modem to 1 the adb stop working and the sa102 dissapear from the device manager but there is now new hardware detected.
Yes, that's what should happen - you should have two or three HSUSB devices under unknown ones. Install drivers for them.
Blagus said:
Yes, that's what should happen - you should have two or three HSUSB devices under unknown ones. Install drivers for them.
Click to expand...
Click to collapse
Nop. There is no unknown devices at all :S
Im runing a custom kernel, maybe need to run stock?
link up my video also and claim its yours atleast give credit
also guys if your on stock rom verizon to enter DIAG mode you enter ##3424
edokassiah said:
link up my video also and claim its yours atleast give credit
also guys if your on stock rom verizon to enter DIAG mode you enter ##3424
Click to expand...
Click to collapse
Which video?
Fyi for those using cdma workshop, You dont need to do the adb commands, phone wont "read" the info for general stuff, just goto security, send the spc code, it will unlock, then continue to upload your PRL stuff and change nam settings. Worked fine. =)
what is this exactly? and what is DIAG/QPST/CDMA workshop?
For cdma phones to change out which carrier its on, you need diag mode (which is the programming mode thats seperate from rom flashing as it tells the phone which tower to connect to) qpst and cdma workshop, are tools we use to program this stuff easier. Cdma workshop costs 100$ for a license tho.
x64 Drivers that WORK!!!!!!!!!!!
i dunno if this even matters anymore but i just made these x64 drivers and they have been tested and work just fine htey are not signed but they will install on win 7 x64
Will this driver let us who use custom rom to using DIAG mode?
since most of custom ROM kill the DIAG ability, so nothing will happen when u press #3424
no they wont unforutnatly
Related
Dear XDA community,
everyday i'm reading new questions from users, how they have to unlock their Lumia 800 and how they can flash custom roms onto it...
So i decided to make this how-to-thread.
I'll keep this post updated as an overview:
post 2: Bootloader unlock DLOAD Lumia 800 to Qualcomm
post 3: Backup and flash your L800 with Ubuntu, flash in Windows using dewe's Lumia Downloader 0.5
post 4: How-To use USB-Video-Out
So please, guys, read this thread, and if you don't understand, feel free to ask. :good:
Bootloader unlock DLOAD Lumia 800 to Qualcomm
If you want to flash a custom rom, you need to have a Lumia 800 with qualcomm bootloader.
But it's a difficult way to make your DLOAD Lumia 800 to Qualcomm:
You need two main things:
1. You need ATF flasher box
2. You need good soldering skills or the special atf cables from gpg industries
Here's a tutorial to SIM-Unlock a Lumia 800: How-To SIM-Unlock your Lumia 800 - gsmhosting.com
This is almost the same procedure for "bootloader-unlocking" your Lumia 800.
You just do not need to click SP-Unlock, you need to click "boot repair" (and select qualcomm, of course).
Here's the thread of the special cables: No more soldering for lumia 610,710,800,900 easiest osbl swap ever
These cables do not require you to solder your device. You only need to open up your phone and connect it to the cable and your ATF Box.
So, if you don't want, or can't buy such a box, check for a local phone repair shop in your town/city. If they have ATF, i'm sure they can do this for you for a small amount.
Hope this helps.
Flash your custom rom using dewe's Lumia Downloader 0.5
Dewe's Nokia Lumia Downloader 0.5
I attached the Nokia Lumia Downloader 0.5 for flashing your Lumia 800 easily in Windows.
Thx to dewe for his great work!
This requires your Lumia 800 to have the qualcomm bootloader!!
First: make a backup of ALL 9 partitions of the phone!
This might really save your ass Id did save mine more than once :good:
1. Install Ubuntu to your computer, or use Ubuntu-Live-CD
2. put phone into "Qualcomm Mode" by pressing VOL UP + POWER and connect it to your pc
3. check with
Code:
sudo fdisk -l
how your phone appears in ubuntu
4. backup your partitions using this:
Code:
sudo dd if=/dev/sd[B]X[/B]1 of=/media/Data/backup1.bin
sudo dd if=/dev/sd[B]X[/B]2 of=/media/Data/backup2.bin
sudo dd if=/dev/sd[B]X[/B]3 of=/media/Data/backup3.bin
up to
sudo dd if=/dev/sd[B]X[/B]9 of=/media/Data/backup9.bin
where the X is your special letter, mostly it's b, c, or d.
if = your input file
of = your output file
And this might take up to 2 hours.
Restoring your backups is the exact opposit.
second: you can now flash your Lumia 800.
because you're already in Ubuntu, you can flash it using:
Code:
sudo dd if=/path/to/your/os-new.nb of=/dev/sd[B]X[/B]9
You MUST flash the os-new.nb file to partition 9!!!
Or you can use attached Nokia Lumia Downloader on Windows.
1. Connect your phone in "qualcomm mode"
2. open the Tool with admin rights in Windows
3. Klick "download" and select os-new.nb file
NOTICE: when you connect the phone in "qualcomm mode" in windows, you'll get a message of formatting the drive. DO NOT DO THAT!!!! CLICK CANCEL! If you format, your phone's broken.
How-To use USB-Video-Out
How to use USB Video Out:
As it seems to be a little "difficult" to use the usb video out package, here's what you have to do (this is a copy out of the readme file of the package):
You can download the needed files here:
USB-Video-Out.rar
Mirror @4shared
Enabling USB video out on the phone (ON THE PHONE)
- From Start Menu swipe over to the application list and run "USB Video Out"
- Answer Yes to enable USB Video out. This is a toggle.
- When the phone boots up it is in Zune Mode which enables it to sync data with Zune Client software on the PC. You will need to toggle this to Video mode using the above steps to get video out.
- Note: Toggling between Zune mode and Video mode requires the phone to reboot each time.
Setting up driver on the desktop (one time)
- Make sure Zune is not running.
- Your Phone must be flashed with a ROM that has video out bits on it, they must be enabled, and the phone must be on and plugged into your PC to continue. When the phone boots up the default setting is OFF for the video output.
- Start -> Right click on Computer, select Manage
- In "Computer Management" click on the Device Manager
- Under "Other Devices"
- Within the list of drivers Right Click on WM7VIDSTREAM driver, select "Update Driver Software..."
- Choose Browse and point Windows to appropriate driver folder.
- Approve the Unsigned Driver installation.
Starting application
- Launch VidStream.exe.
- This application does support disconnect & reconnecting of the phone's USB cable.
- If a previous instance of VidStream.exe was running with the device connected, you will need to simply unplug and replug the phone's USB cable.
- Press ESC to exit the PC Client application.
Re-enabling MTPz USB sync (Zune Mode)
- Open "USB Video Out"
- Answer Yes to enable MTPz
- The device will reboot to make the changes effective.
Click to expand...
Click to collapse
Oh, I was about to write that I'm flashing my phone on Windows but then I saw this method below the Ubuntu.
Isn't it better to put the windows method above the ubuntu? I think more ppl use Windows and possibly won't se the windows method as me
Paviano said:
Oh, I was about to write that I'm flashing my phone on Windows but then I saw this method below the Ubuntu.
Isn't it better to put the windows method above the ubuntu? I think more ppl use Windows and possibly won't se the windows method as me
Click to expand...
Click to collapse
Hi, thx for reply, i wrote it this way, because i wanted to point out, that it is really recommended to make a backup.
If i put the windows flashing above, most people will stop reading, and don't make a backup
I think this way, more people read the backup story, so it's their choice if they don't make one
Zune
Hey thanks for this tutorial. I just had one quick question.
After I do this can I still sync with Zune? Because I would like my data such as songs and apps back. Is this still possible?
if i got for it, it will cost me about 12000 Pakistani rupee for ATF, and about 4000 Pakistani rupee for cable............total 16000, and i can buys with this + sale price of my cell = samsung s#........my GOD....where i am
Good bye to lumia 800....wanna get rid off
bowi1612 said:
Hey thanks for this tutorial. I just had one quick question.
After I do this can I still sync with Zune? Because I would like my data such as songs and apps back. Is this still possible?
Click to expand...
Click to collapse
Hi there,
sorry for late reply.
I you mean with "doing this" unlocking your bootloader, syncing data does not really have anything to do with your bootloader.
Generally, if you make your DLOAD to Qualcomm, your personal files are still on your phone, as bootloader changing does not overwrite any personal files (partition 9 of the phone).
It matters more, which rom you install, if syncing content with zune is still possible or not.
If you flash a custom rom, your data is whiped, as you overwrite your OS partition with the custom rom. But after that, with my roms for example, you can sync your songs etc. back to your Lumia.
I don't think this might work with apps, you have to install them again via marketplace.
Is it possible to use your ROMs on N9?
Is it possible to use your ROMs on Nokia N9? If yes how?
with regards
hrbani said:
Is it possible to use your ROMs on Nokia N9? If yes how?
with regards
Click to expand...
Click to collapse
Is this a serious question??
mate... N9 is a totally different phone, this will NOT work!
Thanks. I'm amateur and know noting about ROM port and others, I asked that question because I want win phone on my N9 .
with regards
Bootloader unlock DLOAD to Qualcomm L800
If I do Bootloader unlock DLOAD to Qualcomm L800 using ATF NITRO ...
do this make any changes on my ROM..?
will this make my phone data wiped...?
and do i need any kind of flash files for this
saddam.khan999 said:
If I do Bootloader unlock DLOAD to Qualcomm L800 using ATF NITRO ...
do this make any changes on my ROM..?
will this make my phone data wiped...?
and do i need any kind of flash files for this
Click to expand...
Click to collapse
Hi there,
no, this only overwrites your bootloader, which is on a different partition as the phone operating system.
so this will not wipe your phone data.
just flashing a custom rom will wipe your data.
Remove Funkyrom
I am just wondering. If I ever want to go back to the Original Windows Phone OS, can I just restore to factory settings on my windows phone? Or do I need to do some other stuff, I can't find an answer anywhere.
bowi1612 said:
I am just wondering. If I ever want to go back to the Original Windows Phone OS, can I just restore to factory settings on my windows phone? Or do I need to do some other stuff, I can't find an answer anywhere.
Click to expand...
Click to collapse
Hi there,
if you've made a backup, you can restore this and reset your phone afterwards.
That's the best solution in my opinion, because you're back on the original rom, but you're still on the qualcomm bootloader, so you can reflash a custom rom whenever you want
Of course you can restore DLOAD and flash the original ROM with ATF, too. But then you have to do the soldering stuff again, if you want to use a custom rom in the future.
thanks for your support
What about the method from cyclone box?
Do you think there will be a method soon for changing bootloader without opening the phone and buying a box? The problem is I don't want to pay for cyclone box.
Celteek said:
What about the method from cyclone box?
Do you think there will be a method soon for changing bootloader without opening the phone and buying a box? The problem is I don't want to pay for cyclone box.
Click to expand...
Click to collapse
No. I think there'll never be an option.
Afaik, this is only possible with ATF, not with cyclone.
lordmaxey said:
No. I think there'll never be an option.
Afaik, this is only possible with ATF, not with cyclone.
Click to expand...
Click to collapse
It is said on their website that it is possible to patch bootloader without opening the phone. (sorry I can't post links yet, but it is easy to find on google by typing "cyclone box lumia 800 no tp" ). Unfortunately we need a cyclone box . My question is : will there be a method with which we don't need a cyclone box?
Hi, all...
After hours of searching, I finally decided to patch the diag drivers to include the HTC Zara (Desire 601). Any of you with the CDMA version may want to play with radio settings, etc.
To use this, unzip the file. Then, in an adb shell, type:
Code:
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
This got me into diag mode, and I could read the phone on the full version of CDMA workshop. I was trying to flash the phone to another carrier, but my settings for NV_ONLY wouldn't seem to stick.
It looks like a lot of settings are locked down now, so either a CDMA WS update will fix it, or someone with far more knowledge than me will have to actually patch the radio.
Credit to XDA User twistedumbrella for the adb shell command.
Enjoy....
Stovepipe said:
Hi, all...
After hours of searching, I finally decided to patch the diag drivers to include the HTC Zara (Desire 601). Any of you with the CDMA version may want to play with radio settings, etc.
To use this, unzip the file. Then, in an adb shell, type:
Code:
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
This got me into diag mode, and I could read the phone on the full version of CDMA workshop. I was trying to flash the phone to another carrier, but my settings for NV_ONLY wouldn't seem to stick.
It looks like a lot of settings are locked down now, so either a CDMA WS update will fix it, or someone with far more knowledge than me will have to actually patch the radio.
Credit to XDA User twistedumbrella for the adb shell command.
Enjoy....
Click to expand...
Click to collapse
Is that command for getting into diag mode without the MSL or something? I had no problems using QPST or CDMA WS with the device as-is, didn't even have to install the diag drivers like with older devices. I think HTC sync installs them now, so you can just install sync for the drivers and then uninstall just the sync app.
Also, are those drivers 32-bit or 64-bit?
If you need your MSL, MSL Reader gets it quick and easy on this device and ##3424# opens diag mode.
These are 32 Bit drivers.
I guess my original post was redundant.. the back story is that I was working on a nTelos Desire 601, which didn't have the ##3424# option. Having just acquired a VM Model, you're correct, 3424 does work.
Windoze still installed the diag driver I'd patched, so they still may be useful to some people.
I'm gonna put this phone on PagePlus.
U have a Zaru_ul and would like to know if anybody has been able to unlock the AWS band on this phone, and if so what was the procedure? Thanks
Expired
Access to doc-00-2k-docs.googleusercontent.com was denied
I cant access the page.
sorry ,, the for the useless google drive broken links ,, i will update the links now
I updated all,,links now u see
This is fantastic. I'm using the t-mobile version. It's excellent, but I'm having a problem with wifi. Does anyone have any recommendations?
change ur wifi region in router webpage to north america and see
i tested this,, this both zips 5 to 6 times ,,but there is no problem for me ,,
go to ur router webpage ,,,and change ur wifi region to north america ,,and then ur phone will start detecting ur region
even i use to change my wifi region in router page to north america,,the my wifi started working
u follow this link here for ur problem :- https://youtu.be/IJ6Vj9_S4QE
So, i was working on an lg k7 and was told to remove the factory reset protection. Which that is apart of the set up wizard for lg so I removed that. Yes it was rooted. But, when I rebooted the device It said security error, authentication error #9 (modification). Ok, so I researched and it is fixable, but the lg download tool will not find the device. The download driver screen goes to 100% and I left it there for a couple hours and theres nothing. and the same exit button remains. I have tried the kdz download and that didnt work either. tried odin or twrp, which twrp is already on the device, but I cannot access anything. Any help with this? been working on it for weeks and its nothing but a head ache.
one thing u did completely wrong process,, setup wizard is a part of LG OS ,,IF U REMOVE IT WILL BREAK UR OS
THE MAIN REASON WHY YOU ARE NOT ABLE TO BOOT INTO RECOVERY IS THIS ONE :- [KERNEL/RECOVERY IS NOT SEANDROID ENFORCING] ON BOOT ,, IF U REMOVE IT FROM BOOT IMG ,THEN IT WILL MAKE U TO BOOT INTO RECOVERY,, AS IT WILL PROTECT U TO BOOT INTO CUSTOM TWRP RECOVERY ,,SO ULTIMATELY U NEED ONE [KERNEL/RECOVERY IS NOT SEANDROID ENFORCING] ON BOOT ,,REMOVED BOOT IMG
So, how do I obtain that one kernal/recovery and flash it on that phone?
Thank you for the quick and detailed reply.
My router is set up correctly.
I also have two identical LG K7 devices. The only difference is that one has your rom and the other is rooted stock.
The one without your rom can connect to Wifi with no issue.
The other one cannot. I enable Wifi and it hangs, as does Bluetooth. The Wifi Icon flashes consistently. Bluetooth just gives an error and goes off.
I believe that another member is having a similar issue, as posted here.
First of all ,,u unlock it boot loader ,,,boot up it android
Go to settings
,,after that go to software info
,,then after go to about phone,and,, Tap the build number until u see you are a developer message
Get into developer options now
Then enable USB debbuging and OEM unlock
Then download Android SDK platform tools
After that open a command windows ,,on the directory where u extracted adb ,,now type adb devices ,,,u will get one pop up like allow RSA key in it phone,,u just allow it,,
Now type command :- adb reboot bootloader
After that it will reboot bootloader,,note bootloader unlock commands are present on the display of the mobile
Note if it device does not support bootloader unlock ,,then it will not allow ur phone into bootloader
After that root ur phone with kingroot or kingroot
Then use flashify to flah twrp
RahulMantha said:
Expired
Click to expand...
Click to collapse
Oh no!
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
This is what I had to do to fix the Unknown caller ID issue with 4G Calling enabled in the respective SIM settings:
Installed QPST Tool on my computer.
With USB debugging enabled in Developer Settings and Magisk for root access, enabled DIAG mode using adb:
Code:
$ adb shell
surya:/ $ su
surya:/ # setprop sys.usb.config diag,serial_cdev,rmnet,adb
In QPST >> PDC activated the respective profile for Sub0 and Sub1 and removed the originally automatically chosen profile (otherwise it kept reversing the desired setting on reboot).
Checked status with *#*#INFO#*#*.
Can this be done without root, I'm having the same issue on a Meizu device without root access & don't have a option to disable VoLTE
TheInfiniteAndroid said:
Can this be done without root, I'm having the same issue on a Meizu device without root access & don't have a option to disable VoLTE
Click to expand...
Click to collapse
If on an original ROM, there should be a way to access a service menu where you can switch on the diag mode that's necessary to be able to use PDC by using the phone dialer.
You may want to search for how to enable diag mode for your device (on my previous OnePlus with OxygenOS firmware it was somthing like *#*#801#*#* or *#*#808#*#*).
Master One said:
If on an original ROM, there should be a way to access a service menu where you can switch on the diag mode that's necessary to be able to use PDC by using the phone dialer.
You may want to search for how to enable diag mode for your device (on my previous OnePlus with OxygenOS firmware it was somthing like *#*#801#*#* or *#*#808#*#*).
Click to expand...
Click to collapse
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
TheInfiniteAndroid said:
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
Click to expand...
Click to collapse
Do you happen to know if there's a way to find it through Activity Manager, finding it hard to navigate
@TheInfiniteAndroid, sorry, can't help with this, don't know Activity Manager.
Hi, I have switched my profiles on my Mi 8 to DT_Greece to activate VoWiFi and deleted the original ROW_Commercial profile.
Whenever a call is getting through VoWiFi or VoLTE i still get unknown caller ID.
Do you perhaps have any other idea to fix that?
razenxd said:
Hi, I have switched my profiles on my Mi 8 to DT_Greece to activate VoWiFi and deleted the original ROW_Commercial profile.
Whenever a call is getting through VoWiFi or VoLTE i still get unknown caller ID.
Do you perhaps have any other idea to fix that?
Click to expand...
Click to collapse
You may want to try another profile in that case, as there is no other way to solve this.
Master One said:
You may want to try another profile in that case, as there is no other way to solve this.
Click to expand...
Click to collapse
Aah really? That sux
Ι've tried more than the half configs listed and only DT_greece seems to enabling VoWiFi for Vodafone Greece carrier
razenxd said:
Aah really? That sux Ι've tried more than the half configs listed and only DT_greece seems to enabling VoWiFi for Vodafone Greece carrier
Click to expand...
Click to collapse
Indeed, sucks if not working, but I have no other idea. Try the second half of configs as well, maybe there is one that just works with your carrier.
Master One said:
Indeed, sucks if not working, but I have no other idea. Try the second half of configs as well, maybe there is one that just works with your carrier.
Click to expand...
Click to collapse
That's what i'm doing at the moment.
No luck so far
On RN10 Pro my carrier works just fine, I already have extracted the .mbns from RN10 Pro's firmware but now i need to find which one is actually is using and a way to insert it to my device!
Master One said:
This is what I had to do to fix the Unknown caller ID issue with 4G Calling enabled in the respective SIM settings:
Installed QPST Tool on my computer.
With USB debugging enabled in Developer Settings and Magisk for root access, enabled DIAG mode using adb:
Code:
$ adb shell
surya:/ $ su
surya:/ # setprop sys.usb.config diag,serial_cdev,rmnet,adb
In QPST >> PDC activated the respective profile for Sub0 and Sub1 and removed the originally automatically chosen profile (otherwise it kept reversing the desired setting on reboot).
Checked status with *#*#INFO#*#*.
Click to expand...
Click to collapse
Thanks for posting on this, but what do you mean by qpst>>pdc? When I run qpst I see no active devices, pdc doesn't either. So no clue how to proceed.
treebaard said:
Thanks for posting on this, but what do you mean by qpst>>pdc? When I run qpst I see no active devices, pdc doesn't either. So no clue how to proceed.
Click to expand...
Click to collapse
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after connecting?
Master One said:
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after
Master One said:
Did you follow the other steps with enabling USB debugging and DIAG mode?
Qualcomm USB driver installed and phone properly recognized after connecting?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yes, up to the step of my phone being recognized, as it isn't automatically recognized at all by qpst config. And since there is no faq of any kind on what to do if the phone isn't recognized by QPST, I'm stuck.
I presume the issue is that I don't see any ports listed in the ports view. But I installed the Qualcomm usb driver already, so not sure how to fix that
per https://forum.xda-developers.com/t/rom-11-lineageos-official-surya-karna.4202533/post-85746887 , did you fix this in LOS 17.1, or 18?
treebaard said:
per https://forum.xda-developers.com/t/rom-11-lineageos-official-surya-karna.4202533/post-85746887 , did you fix this in LOS 17.1, or 18?
Click to expand...
Click to collapse
I'm not a developer and I can't really help as I'm not currently using LOS. You may want to find out if DIAG mode is supported and working in LOS.
TheInfiniteAndroid said:
Thanks for your reply, downloaded activity manager & managed to switch off VoLTE through there, couldn't find the PDC thing unfortunately, hopefully a OTA fixes the issue in the future otherwise I'm stuck with VoLTE
Click to expand...
Click to collapse
PDC you will find it in the folder with the installed program QPST.
I did it. Sorry for my English.
Master One said:
I'm not a developer and I can't really help as I'm not currently using LOS. You may want to find out if DIAG mode is supported and working in LOS.
Click to expand...
Click to collapse
Another user said this procedure worked with LOS 17.1, but not 18.1 which we now run. I don't see a new device added in windows task manager, so I guess something's changed, and the QPST folks need to look into it.
treebaard said:
Another user said this procedure worked with LOS 17.1, but not 18.1 which we now run. I don't see a new device added in windows task manager, so I guess something's changed, and the QPST folks need to look into it.
Click to expand...
Click to collapse
The QPST folks have nothing to do with this, maybe (I mean hopefully) @gardiol can comment on DIAG mode support in the current version of LOS.
Can this have anything to do with the MUIU vs. OSS vendor?
I'm still running an older version of ArrowOS with the MIUI vendor, but possibly the DIAG mode problem came up with the move to OSS vendor?