Hello everyone.
I have something fun for you : Someone gave me a phone (apparently bought on amazon to some dodgy reseller), and it appears to be some kind of chinese fake Goophone or something. I was asked to make the phone usable, because right now, no Play Store, Chinese apps, can't change the keyboard layout...
I've made an album with some pics, but I can't post it directly since this is a new xda account, so please go to the imgur website and add "/a/heFVk" to the address to check it out. You can notice the fake Iphone 6 id on the back, or the "32GB Space" in the parameters when actally there is only 1GB. I love it.
So here's my problem : There was no recovery, I tried to flash one (well, a lot actually) but the phone won't boot on it (if I try, it'll stay stuck on the splash screen 4G+ Volte, and I have to remove the battery to make the phone boot again).
If I try to go on the bootloader, I'll get a blackscreen with just a little red text "fastboot mode".
With the fastboot commands, I can detect the device, flash a recovery, reboot, but if I try "fastboot oem device-info" or "fastboot oem unlock", I only get 3 dots ("...") and nothing happens.
I don't have a device name (well, the brand and model are both "4G+", lulz) and I have absolutely no idea if I can / how to flash another rom on it.
Right now, the phone is still working, but is not usable (well, except if you are chinese with low standards I guess?)
If anyone got any ideas how to proceed to get the recovery working, and what kind of rom I could flash on the phone, that would be amazing.
Thanks in advance !
You have fastboot mode! Also, enable usb debugging in settings (check online for guides if you are not sure on how to do that). Check that adb recognizes your device and just sideload the apk. If that doesn't work, hop into fastboot, run fastboot oem unlock to unlock your bootloader and try flashing gapps. Good luck!
Hi all,
I've spent a rather frustrating week or so in the throes of searching Google and XDA to figure out how to get my brand new RS988 upgraded to the 21c software version on Nougat. Here's what I've done so far:
-Check for OTA updates using the OS. No dice...it went from 11a to 11c and will not find any further updates.
-Use LG Bridge to try to update the software. No dice. The software tries to get the current OS version and then says "cannot find operating system version" and won't contact home base to get the new files.
-Reboot into boot loader to install TWRP. No dice...the phone will not reboot into the boot loader for some reason. I've tried using both the ADB method of "adb reboot bootloader" and "adb reboot-bootloader", but both just have it reboot into the full OS. I've also tried powering on the phone while holding the volume down button, to no avail.
-All root and TWRP methods, and even getting the official bootloader unlock require booting into the boot loader
The one thing I *have* been able to get to work was re-flashing a KDZ of the RS98811c software from autoprime's linked repository.
As best as I can tell, I am stuck. Without being able to install TWRP via the boot loader I don't know how to update the software. Please help me figure this out!
Edit: additional device info added
Android version: 6.0.1, 2016-07-01 security patch
Baseband version: MPSS.TH.2.0.c1.4-00010-M8996FAAAANAZM-1.43591.5
Kernel: 3.18.20
Build: MMB29M
Configuration: F15.LGE.RS988.0
Software version: RS98811c
Security software: MDF v2.0 Release 1
Thanks!
Use lg up
It's possible that you have the RS988.BPT version (Brightpoint), which only got updated to 11h, I believe. I sent in a RS988.USA version, and they swapped for a new BPT motherboard. I've since sent it back yet again to get that resolved.
It appears to be a Tracfone Wireless version, according to the box, at least. It was supposed to be new, not refurb, so fingers crossed that's all good as well. Even if it was the Brightpoint version, wouldn't that have been fixed when I flashed the USA stock ROM?
I also don't see how to use LG UP to reboot into boot loader mode. It only shows me the phone, with nothing clickable, and a selection of 4 processes: refurbish, upgrade, phonesetting, and FOTA upgrade. Not wanting to mess up my phone, I am trying to be cautious about just trying either of the latter two options. Especially without a file there. Thoughts?
You did unlock the bootloader am I correct?
Matthew_Jay said:
You did unlock the bootloader am I correct?
Click to expand...
Click to collapse
Nope. I can't get into the bootloader (unless I've totally missed a method to do that). Even the instructions on LG's website pre-suppose that you can enter the bootloader. Step 9 on their bootloader unlock instructions say:
9. Enter your phone’s unique Device ID. You can view the Device ID by connecting your phone to the PC using a USB cable and entering "adb reboot bootloader" in DOS command window of the folder you created in previous step (for example: C:\tools). Your phone will reboot into the fastboot mode. Enter "fastboot oem device-id" in DOS command window.
Click to expand...
Click to collapse
Unfortunately, issuing that command simply reboots the phone without a bootloader in sight. Any commands issued by fastboot after the "adb reboot bootloader" command just sit there saying "waiting for device". I think if I could get this far, the excellent instructions elsewhere on these forums would have me sorted the rest of the way, since then I could use TWRP to flash a more recent OS version. Thus far, it's only LG UP which works, which also requires a .KDZ file, but I can't find one for any version > 11c.
One further edit - I re-read autoprime's instructions and was at least able to get the phone to boot into recovery mode. (I can't tell whether the grey or white highlight is the "active" selection, so I haven't tried selecting one since I'd rather not wipe my device unnecessarily.) But in that mode it won't connect to my Win10 machine for adb or fastboot to do anything. Still can't get it into fastboot mode using "adb reboot bootloader". What am I missing? Feel free to be super-basic, since it's probably something of that sort.
AdamDG said:
One further edit - I re-read autoprime's instructions and was at least able to get the phone to boot into recovery mode. (I can't tell whether the grey or white highlight is the "active" selection, so I haven't tried selecting one since I'd rather not wipe my device unnecessarily.) But in that mode it won't connect to my Win10 machine for adb or fastboot to do anything. Still can't get it into fastboot mode using "adb reboot bootloader". What am I missing? Feel free to be super-basic, since it's probably something of that sort.
Click to expand...
Click to collapse
Simple answer is "You can't". I am in the same boat, stuck on 11c with no OTAs in sight. The ability to boot into the bootloader wasn't added until a later version (11h, I think?) So until/unless LG releases a KDZ of one of the later versions, you (and I) are out of luck.
Further futile time spent with LG revealed one more issue: the phone apparently was originally for Tracfone. (Never mind that I bought something specified as RS988.AUSATN and not as RS988.ATFNTN.) LG claims they have no say in the operating system or updates (even before they determined it was Tracfone) and now Tracfone says LG is solely responsible for the OS.
What is going on with these jokers?
AdamDG said:
Further futile time spent with LG revealed one more issue: the phone apparently was originally for Tracfone. (Never mind that I bought something specified as RS988.AUSATN and not as RS988.ATFNTN.) LG claims they have no say in the operating system or updates (even before they determined it was Tracfone) and now Tracfone says LG is solely responsible for the OS.
What is going on with these jokers?
Click to expand...
Click to collapse
Hey AdamDG, were you able to solve your issue? I am stuck with the same situation and asinine LG folks won't help me out because Total Wireless/Tracfone are supposed to take care of the matter. But the latter are not responsible for software updates because they are MVNOs and don't (need to) care.
Truly jokers, but more importantly, taking customers for a s(laughter) ride!
Basic device info
Model Number : PB1009
Android Version : 7.0
Kernel Version: 4.4.22
Build Number : PB1009_20170912
Hey so i need literally any way to root this tablet, ive been able to unlock the bootloader (easiest bootloader on the planet) but havent been able to find a compatable twrp.
i just need a custom recovery that will work or p much any root ideas, i would consider a full custom firmware as well.
i considered compiling a twrp but i dont know how i would get the source files for it...
Kenvarus said:
Basic device info
Model Number : PB1009
Android Version : 7.0
Kernel Version: 4.4.22
Build Number : PB1009_20170912
Hey so i need literally any way to root this tablet, ive been able to unlock the bootloader (easiest bootloader on the planet) but havent been able to find a compatable twrp.
i just need a custom recovery that will work or p much any root ideas, i would consider a full custom firmware as well.
i considered compiling a twrp but i dont know how i would get the source files for it...
Click to expand...
Click to collapse
how did you unlock bootloader and did you ever figure out how to root it? going through same thing now.
Kind of an old thread and old device now, but I own one myself (branded Packard Bell) and just figured this all out, so here goes:
Root
This one is really easy now thanks to a MediaTek flaw. Just go to https://github.com/JunioJsv/mtk-easy-su, download the latest release, install the APK on the device, and run it by opening the app and pressing the button in the lower-right corner (still works on this since the latest security patch level AFAIK is from 2017). Note that this gives root temporarily, so you will need to run it again after reboot if you want root again.
Bootloader Unlock
When Kenvarus said "easiest bootloader on the planet", I took a guess at the method and it worked:
Back up any important data on your tablet, as this will factory reset it.
Install ADB and Fastboot on your computer if they are not installed, including drivers. For Fastboot (as that can be tricky sometimes), it "just worked" for me and I think Windows used an Amazon driver I had installed for my KF2. YMMV.
If you haven't already, enable Development Settings by going to Settings->About tablet and tapping the build number 7 times.
Go to Settings->Developer options (switch them on if they're off) and enable the "OEM unlocking" toggle.
In the same menu, enable "USB debugging" if it is not enabled already.
Connect the tablet to your computer, confirming the authorization prompt that pops up if it wasn't connected before. Check whether the connection is good with the "adb devices" command if needed.
Run the command "adb reboot bootloader", this gave me a blank screen.
Use the "fastboot devices" command to make sure the Fastboot connection works.
Run the command "fastboot oem unlock".
Press Volume Up when the text-mode confirmation screen pops up on the tablet.
Once the unlock procedure is complete, reset the tablet. You should see text on your bootscreen saying "Orange State" and a factory reset on the first reboot if it worked.
WARNING: I highly recommend charging your battery to be at least 10-20% filled before doing this. I stupidly did this at 1% battery thinking "it's plugged in anyway" and had quite the time rebooting after unlocking the bootloader (I thought it was bricked for a good hour or so, only after walking away for 20 minutes to eat dinner did I see that the battery was now at 20% and I could boot the tablet).
After unlocking the bootloader and temp-rooting it with the above app, I was able to use Magisk to patch the boot image (using dd to shuttle the files to and from /dev/block/mmcblk0p10, use "strings saved_boot_partition_name|head -n1" and check for "ANDROID!" to make sure it's the right partition) and I now have persistent root after all these years (note that Direct Install in Magisk doesn't work here). I'd definitely be interested in a custom recovery and/or ROMs for this device, but I'm not holding my breath (I'd take a crack at it if I knew better how to do it, but I have near-zero experience with ROM development and so far have only recompiled existing ROMs for a few phones).
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