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!
Related
I have the Total Wireless variant of the RS988 running Android 6.0.1 (11c).
Trying to boot to the bootloader simply reboots the phone normally (power + vol up as well as adb reboot bootloader)
When I try to check for OTA updates, it tells me I have the newest software for my phone. When I connect my phone to LG Bridge, it tells me it cannot check the software version number.
Googling and searching XDA has yielded pretty few results considering the possibility of getting 11d or later is pretty much up to the carrier. Trying to unlock my bootloader through LG's developer website leaves me with a log in screen that doesn't go anywhere (with a confirmed LG account and the right password).
What are my options for getting this phone rooted?
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
I'm with same problem here!
Suckmymfdick17 said:
Hello friends of XDA, I have a big problem between hands, I have a MOTO Z and I had it in android 7.0 since last year the update to andorid 7.1.1 did not arrive and I felt that with android 7 the battery was consumed very quickly, so I tried to find the update to flash it and just about 3 days ago I found it, I proceeded to download it and flash it in fastboot and adb.
The thing is that a few months ago, browsing through my phone (I had already rotated it, and unlocked the bottloader, I decided to re-block the bootloader, and remove the root, which never worked at 100) I got into the developer options, and I saw an option that until then I didn't know about its "OEM Unlock"function, as it was turned on and deactivated because I thought it didn't work.
Returning to the update flashing I proceeded as usual, with the commands, I proceed to restart the device and show the image of the boot of motrola but then it shows me a message in red letters.
"Startup Failed"
"failed to pass validation, backup to fastboot.
I thought it was a compatibility problem with the downloaded version of 7.1.1 so again I decided to flash the stock rom 7.0 but when I finished and restart the same message appeared.
I started to investigate and it seems that the OEM blockade is responsible for not being able to install any Stock Rom, or anything, and now I have a nice brick with Moto mods and I can't use it.
I wanted to unlock OEM in fastboot but nothing. sends message from "ALLOW OEM UNLOCK IN SETTINGS"
There is way to unlock the OEM from pc or fastboot without needing to be unlocked from the android settings, as in my case it is impossible for me,
I'd be very grateful for your help friends, I know it's a bit tedious to read but it's the only phone I have and I feel weird without it on the street.:bueno::bueno::llorando:
Click to expand...
Click to collapse
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
knjigo said:
Try to boot in Fastboot flash twrp and flash ressurection remix rom. It's great rom. Forget about locking. I had the same problem like you as I was trying to flash stock ROM and lock bootloader.
I gave up on this.
Click to expand...
Click to collapse
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Suckmymfdick17 said:
Well, when the root didn't work properly, I flashed the phone again and blocked the bootloader. Will I still be able to install TWPR or should I lose my phone?
Click to expand...
Click to collapse
What do you mean with "I blocked my bootloader"?
Twrp is easy to flash. Root is integrated in ressurection remix rom. And this rom is great. Just try to flash twrp in Fastboot and than ressurection remix with twrp.
Can you boot in Fastboot?
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
tjgibri said:
I'm with same problem here!
Click to expand...
Click to collapse
I solved it, I finally flashed the stock rom to my phone and it works.
Apparently my pc was not flashing the stock rom in adb, and the phone turned off when loading the software. I did it 3 times until I load correctly and start well.
if you have the same problem apparently then OEM Blocking is not responsible. You have to flash the most current rom or the one that you had by default when the brick happened to you, you flash it in a normal way with commands of adb and ready, I would have to come back to life.
download from firmware center MotoZ Griffin the most current rom stock at 7.1.1
echo92 said:
Do you remember what build of 7.1.1 you had on your device before downgrading to 7.0?
If so, I would suggest finding that firmware (the full stock firmware, not OTA updates) or newer if you can, and try to flash that. Since your bootloader is still likely from the 7.1.1 build, a locked bootloader will only permit files matching the same patch level (i.e. from the exact same stock ROM as that bootloader patch) to boot.
If not, then unfortunately there's not a lot we can do. You could wait for a newer firmware to get leaked, but as your device is unable to boot (due to failing the bootloader checks) and you cannot toggle OEM unlocking because you cannot boot, it's a nasty vicious circle that is difficult to get out of. You may have to consider sending your device for service and pay for an expensive motherboard replacement otherwise, since Motorola have a record of your device being unlocked. Your service centre experience may vary.
Only lock a bootloader after ensuring you've flashed all the stock firmware and it is all the same patch level as your bootloader. Hopefully you'll find newer firmware that you can repair with.
Click to expand...
Click to collapse
Thanks for your help friend, I finally flashed it with a recent android 7.1.1 update. Apparently the OEM lockout was not the culprit, but it was an interrupted flash of android 7.1.1 at some point when loading the software to the phone, it would shut down on its own and not complete the installation, which showed me the mentioned message. I didn't realize that and thought it was the OEM blockade.
I finally did it on another pc and it worked. the phone came back to life.
I have one Moto Z2 Force (XT1789-05), bought from coolicool.com, I didn't know device came Unlocked Bootloader, Device rom had problem with many apps, I googled and found one topic in XDA developer to Install Stock Rom, I downloaded and Installed India Rom, it's worked somehow fine, but still had problem, I downloaded Verizon Rom, Android 8, after Installed Android 8 Verizon Rom, Locked device bootloader immediately, now device stuck at Welcome Wizard in Android 8, after select language I got this message: (Please wait, this may take a few minutes) this is proof video (http://ahmn.co/Upload/IMG_0161.MOV), after this issue, device already locked, I can't unlock, because need to go to the Developer Option in Setting, I stucked in Welcome Wizard, there isn't any bypass, So, I start to search in Google, XDA-Forum, Android Central and more, I created many threads, many requests, no one can't help me, I tried to reach google developer support to the tell to me how can I bypass Android 8 Welcome Wizard, there is must be a way, but I can't find it, now I can access to Android Recovery and Bootloader
1. if you help me to FORCE UNLOCK device without need Developer Option in setting my problem will solve
2. If you help me to Bypass Android Welcome Wizard, access setting and enable OEM Unlock
3. If you help me to update the device from Android 8 to Android 9 Verizon ROM via ADB Sideload or Update from SD card in Recovery mode
4. If you have any idea to how can I fix it
Extra Information: I bought Belkin and Uni USB-C to Ethernet Adaptor to help me bypass Android 8 Welcome Wizard, I bought WSKY WIFI Adaptor because device Wifi can't find any network (I found QR setup by tap several times in Language Selection), after this section need to download google device policy apk, my device can't find any Wifi Network and my Ethernet Adaptor can't help me either, So, I just remained with my phone, and I can't do anything,
Please, someone, help me
My Device SKU: XT1789-05
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
Hi,
I've searched for instructions but can't find my situation.
I'd like to unroot, go back to LG stock, and lock bootloader so I can sell my LGv30 US998.
I have the actual US998 from B&H (not one that's been converted from something else).
Current build is: US99820a with March 1, 2018 Security.
Can someone let me know the procedure? I believe I'd like to go to the latest Oreo version "h" I think.
PS. I've tried to install LGUP tool, LG Flash Tool and none of them seem to detect my phone on Windows 10 from https://lgflash.com/download/ There are so many versions of all of these programs I don't know which one is correct. I've also installed the LGMobileDriver_WHQL_Ver_4.5.0.exe
So, some links to LGUP that actually works would be great.
Thanks
glhelinski said:
Hi,
I've searched for instructions but can't find my situation.
I'd like to unroot, go back to LG stock, and lock bootloader so I can sell my LGv30 US998.
I have the actual US998 from B&H (not one that's been converted from something else).
Current build is: US99820a with March 1, 2018 Security.
Can someone let me know the procedure? I believe I'd like to go to the latest Oreo version "h" I think.
PS. I've tried to install LGUP tool, LG Flash Tool and none of them seem to detect my phone on Windows 10 from https://lgflash.com/download/ There are so many versions of all of these programs I don't know which one is correct. I've also installed the LGMobileDriver_WHQL_Ver_4.5.0.exe
So, some links to LGUP that actually works would be great.
Thanks
Click to expand...
Click to collapse
follow instructions from ChazzMatt's thread, they have LG UP dual linked and the instructions to flash kdz
Thanks. He has lots of threads. Do you have a link?
I believe it's the one/main thread he maintains on how to root/unlock the phone. You'll have to do some thinking on how to go "backwards" from there, but the software and steps are all in there.
Generally speaking, it's NOT recommended to relock the BL because if the phone isn't 100% stock ROM, I believe you could end up bricking or bootlooping. I think you can leave the BL unlocked and just KDZ flash US998 and leave it unrooted (no Magisk, etc). This should look "stock" to anyone who cares to have a stock-specific phone anyway.
I'm concerned a buyer wouldn't like the opening "corruption. lock the bootloader" screen. My assumption is locking the bootloader would get rid of that... Does anyone know if that's true?
glhelinski said:
I'm concerned a buyer wouldn't like the opening "corruption. lock the bootloader" screen. My assumption is locking the bootloader would get rid of that... Does anyone know if that's true?
Click to expand...
Click to collapse
Yes, re-locking the bootloader will get rid of the warning screen. Just make sure you are 100% complete stock (all partitions) before you re-lock it. Otherwise the phone may brick itself.
Also, make sure you remove your Google account in the OS before you wipe/re-flash the phone. Otherwise it will trigger FRP and require the new user to enter the previous username and password.
I might be in the same boat here, would love to know how to just return to stock and relock bootloader (for someone who didn't make an initial backup)
How about these steps:
1) Make sure you have working ADB on your computer, including latest LG USB drivers.
2) Boot into the OS and remove your account using Settings -> General -> Accounts -> (select Google account) -> Remove account. This prevents Android's Factory reset Protection from kicking in, which otherwise would require the previous account to be re-entered after wiping the phone.
3) Go to ChazzMatt's US998 Pie KDZ thread and download and install LGUP exactly as described under How to Install Dev Patched LGUP towards the bottom of post #2. Remember to thank Chazz.
4) Download the KDZ for your current OS version (Oreo or Pie) either from the relevant KDZ ROM thread in the V30 ROM sub-forum or from LG-firmwares.com. Verify its MD5.
5) Enter Download mode: With the phone off, hold Vol Up, and plug in the USB cable that is connected to your PC.
6) Assuming you manage to get into Download mode, launch LGUP and make sure it detects the phone.
7) Flash the KDZ you downloaded using LGUP Refurbish mode. If you're on a custom ROM and/or if you want to do a particularly thorough job, you may consider FIRST flashing Nougat using LGUP Partition DL mode, THEN flashing back up to Oreo or Pie, again using Partition DL Mode.
8) After LGUP (hopefully) completes flashing the KDZ unplug the cable and let phone reboot.
9) Once (hopefully) you're booted into the OS, tap Settings -> General -> About phone -> Software info- > Build number until Developer Options are enabled.
10) Enable Settings -> General -> Developer Options -> Enable OEM unlock.
11) Turn phone off and unplug the cable.
12) With phone off, enter fastboot mode by holding Vol Down and plug in the USB cable that is connected to your PC.
13) In ADB window on computer, enter fastboot devices to verify ADB is working.
14) In ADB window, enter fastboot oem lock to re-lock the bootloader.
15) Use fastboot keys to reboot phone into OS. See that it works.
16). Run Settings -> General -> Reset -> Factory data reset. Do NOT use Master Reset (button dance) or the new user might trigger FRP/kill switch (although shouldn't happen if you removed the account previously and didn't enter it again).
17) Done. Hand off the phone to its new user.
These steps were written off the top of my head. If anybody sees glaring mistakes or omissions, then please let me know.
Note: Some carrier models cannot readily get into fastboot mode. For those you will need to convert back to stock US998 to re-lock the bootloader (using Frankenstein like when you first rooted) and THEN convert back to the carrier firmware (again using Frankenstein).
Thank you
TheDannemand said:
How about these steps:
1) Make sure you have working ADB on your computer, including latest LG USB drivers.
2) Boot into the OS and remove your account using Settings -> General -> Accounts -> (select Google account) -> Remove account. This prevents Android's Factory reset Protection from kicking in, which otherwise would require the previous account to be re-entered after wiping the phone.
3) Go to ChazzMatt's US998 Pie KDZ thread and download and install LGUP exactly as described under How to Install Dev Patched LGUP towards the bottom of post #2. Remember to thank Chazz.
4) Download the KDZ for your current OS version (Oreo or Pie) either from the relevant KDZ ROM thread in the V30 ROM sub-forum or from LG-firmwares.com. Verify its MD5.
5) Enter Download mode: With the phone off, hold Vol Up, and plug in the USB cable that is connected to your PC.
6) Assuming you manage to get into Download mode, launch LGUP and make sure it detects the phone.
7) Flash the KDZ you downloaded using LGUP Refurbish mode. If you're on a custom ROM and/or if you want to do a particularly thorough job, you may consider FIRST flashing Nougat using LGUP Partition DL mode, THEN flashing back up to Oreo or Pie, again using Partition DL Mode.
8) After LGUP (hopefully) completes flashing the KDZ unplug the cable and let phone reboot.
9) Once (hopefully) you're booted into the OS, tap Settings -> General -> About phone -> Software info- > Build number until Developer Options are enabled.
10) Enable Settings -> General -> Developer Options -> Enable OEM unlock.
11) Turn phone off and unplug the cable.
12) With phone off, enter fastboot mode by holding Vol Down and plug in the USB cable that is connected to your PC.
13) In ADB window on computer, enter fastboot devices to verify ADB is working.
14) In ADB window, enter fastboot oem lock to re-lock the bootloader.
15) Use fastboot keys to reboot phone into OS. See that it works.
16). Run Settings -> General -> Reset -> Factory data reset. Do NOT use Master Reset (button dance) or the new user might trigger FRP/kill switch (although shouldn't happen if you removed the account previously and didn't enter it again).
17) Done. Hand off the phone to its new user.
These steps were written off the top of my head. If anybody sees glaring mistakes or omissions, then please let me know.
Note: Some carrier models cannot readily get into fastboot mode. For those you will need to convert back to stock US998 to re-lock the bootloader (using Frankenstein like when you first rooted) and THEN convert back to the carrier firmware (again using Frankenstein).
Click to expand...
Click to collapse
not sure if you can help. i asked chaz as well but haven't received a resolution. i've done this but the phone at aroud >10 says that it needs to enable oem unlock to move forward with fastboot commands. except that this option is greyed out in the dev options. says phone is bootloader is already unlocked and doesn;t give option to enable it?? sigh i have tried 4 versions nougat and oreo ... none worked... any ideas??
johnp357 said:
not sure if you can help. i asked chaz as well but haven't received a resolution. i've done this but the phone at aroud >10 says that it needs to enable oem unlock to move forward with fastboot commands. except that this option is greyed out in the dev options. says phone is bootloader is already unlocked and doesn;t give option to enable it?? sigh i have tried 4 versions nougat and oreo ... none worked... any ideas??
Click to expand...
Click to collapse
I've heard of this before, where OEM Unlock was greyed out in the Developer Settings menu. I believe the answer was you have to wait a few days and it will change. But that's very frustrating when you're trying to get this phone back to stock.
Just to make sure I understood you correctly: You have tried booting into fastboot and run "fastboot oem lock" even with OEM Unlock greyed out, right? Otherwise definitely try that.
I am afraid I don't have any other suggestions.
@ChazzMatt: I remember you posting about this one time. Do you have more to add?
TheDannemand said:
I've heard of this before, where OEM Unlock was greyed out in the Developer Settings menu. I believe the answer was you have to wait a few days and it will change. But that's very frustrating when you're trying to get this phone back to stock.
Just to make sure I understood you correctly: You have tried booting into fastboot and run "fastboot oem lock" even with OEM Unlock greyed out, right? Otherwise definitely try that.
I am afraid I don't have any other suggestions.
@ChazzMatt: I remember you posting about this one time. Do you have more to add?
Click to expand...
Click to collapse
yes. i have tried it anyway but the pc says waiting for devices. it does not recognize it since oem unlock isn't triggered.. doesn't work....sigh
johnp357 said:
yes. i have tried it anyway but the pc says waiting for devices. it does not recognize it since oem unlock isn't triggered.. doesn't work....sigh
Click to expand...
Click to collapse
Understood. Question: Did you flash KDZ with Refurbish or Partition DL? Maybe one of them will clear this state and the other won't. But DON'T go experimenting with other LGUP modes!
Also, you could try a Factory reset and/or Master Reset (button dance) and see if that clears it.
If none of that works, you may have to just wait it out.
Edit: I googled around a bit. It seems Factory reset, then letting the OS connect to the internet (enable WiFi) can make the difference. Try googling as there are many references to this.
TheDannemand said:
Understood. Question: Did you flash KDZ with Refurbish or Partition DL? Maybe one of them will clear this state and the other won't. But DON'T go experimenting with other LGUP modes!
Also, you could try a Factory reset and/or Master Reset (button dance) and see if that clears it.
If none of that works, you may have to just wait it out.
Edit: I googled around a bit. It seems Factory reset, then letting the OS connect to the internet (enable WiFi) can make the difference. Try googling as there are many references to this.
Click to expand...
Click to collapse
i tried both refurbished and partition dl.. i may start tinkering with the others but people have warned against some so i'm hesitant of trying it... this really sucks.. need to return it to VZ on a trade in and running out of time
johnp357 said:
i tried both refurbished and partition dl.. i may start tinkering with the others but people have warned against some so i'm hesitant of trying it... this really sucks.. need to return it to VZ on a trade in and running out of time
Click to expand...
Click to collapse
Why can't you wipe it and return it to VZ like that? They don't care if it's rooted, bl unlocked, etc. They're going to wipe it when they get it and try to resell it regardless, why do their job for them?
ldeveraux said:
Why can't you wipe it and return it to VZ like that? They don't care if it's rooted, bl unlocked, etc. They're going to wipe it when they get it and try to resell it regardless, why do their job for them?
Click to expand...
Click to collapse
i read somewhere that rooting a phone violates their terms and makes it invalid as a trade in...
johnp357 said:
i read somewhere that rooting a phone violates their terms and makes it invalid as a trade in...
Click to expand...
Click to collapse
It voids whatever warranty existed between you, Verizon, and LG, but I haven't seen anything about trade ins. Where'd you read that?
johnp357 said:
i tried both refurbished and partition dl.. i may start tinkering with the others but people have warned against some so i'm hesitant of trying it... this really sucks.. need to return it to VZ on a trade in and running out of time
Click to expand...
Click to collapse
Did you try a Factory reset from the menu, then setup phone again with WiFi enabled? Heck, possibly even entering you Google account during setup and let it sync, if that's what it takes. As long as you perform a Factory reset from the menu to remove your account before trading it in.
@ldeveraux is probably right that Verizon won't care. But I am cautious person too when it comes to these things, and would prefer to trade in the phone in a clean state. Just in case the person you end up dealing with is a nitpick.
TheDannemand said:
Did you try a Factory reset from the menu, then setup phone again with WiFi enabled? Heck, possibly even entering you Google account during setup and let it sync, if that's what it takes. As long as you perform a Factory reset from the menu to remove your account before trading it in.
@ldeveraux is probably right that Verizon won't care. But I am cautious person too when it comes to these things, and would prefer to trade in the phone in a clean state. Just in case the person you end up dealing with is a nitpick.
Click to expand...
Click to collapse
i did try the factory reset. both from within and the buttons. and connected with wifi. didn't work... sadly. removing my account is not an issue. every time I install 1 of 4 diff nougat or oreo kdz in lgup, I put skip in the login so it doesn't have my info anymore... resetting doesn't really do it. messing with the date like others have suggested didn't either.
johnp357 said:
i did try the factory reset. both from within and the buttons. and connected with wifi. didn't work... sadly. removing my account is not an issue. every time I install 1 of 4 diff nougat or oreo kdz in lgup, I put skip in the login so it doesn't have my info anymore... resetting doesn't really do it. messing with the date like others have suggested didn't either.
Click to expand...
Click to collapse
That is indeed puzzling. I did this twice on my old H932 before sending it in for warranty, and never saw that problem.
I am sorry I don't have more suggestions to offer