Hello All,
I have taken the liberty of re-packaging the adb binary and fastboot binaries so they will work naively on Android into a flashable zip file. With these tools, you can theoretically use your Android device (plus a USB OTG Cable) to connect to another Android Device. If your device has a native USB port (such as the ASUS Transformers), it will work as well.
As not to conflict with the official adb in /system/bin (which does not work the same way), I renamed these to "kadb" and "kfastboot". You just need to supply your own Terminal Emulator (such as connectbot) to use.
Example Uses
1) Unlock a bootloader on a Nexus device (erases all data on the target device)
kfastboot oem unlock
2) Lock a bootloader
kfastboot oem lock
3) Boot a recovery
kfastboot boot /sdcard/path/to/recovery.img
4) Flash a recovery
kfastboot flash recovery /sdcard/path/to/recovery.img
5) Reboot into the bootloader
kadb reboot bootloader
6) Shell
kadb shell
7) Reboot into recovery
kadb reboot recovery
8) logcat
kadb logcat
9) Sideload an APK file
kadb install /sdcard/path/to/APK.APK
10) Push a file
kadb push /sdcard/path/to/file /sdcard/path/to/destination
Please remember that these are taking place on the remote device connected via USB. Most, if not ALL ADB commands are supported. You can even modify most linux based one-click root methods (by changing all "adb" references to "kadb" and "fastboot" with "kfastboot") and run them via shell. Its also perfect for remote debugging of embedded Android Systems. Hell, the uses are endless!
Installation Instructions
Note : You do not need to be rooted, you do however need a custom recovery or temp boot a custom recovery.
1) Flash the attached Zip File via any Recovery such as CWM or TWRP
2) Reboot and install a Terminal Emulator, if using ConnectBot, you should choose the "local" option.
3) Connect a device and test
This should support any ARM based device, so far I have tested it on my ASUS Nexus 7 and ASUS Transformer 700 (Stock/Rooted)
HAVE FUN!!!
KMyers said:
Hello All,
I have taken the liberty of re-packaging the adb binary and fastboot binaries so they will work naively on Android into a flashable zip file. With these tools, you can theoretically use your Android device (plus a USB OTG Cable) to connect to another Android Device. If your device has a native USB port (such as the ASUS Transformers), it will work as well.
As not to conflict with the official adb in /system/bin (which does not work the same way), I renamed these to "kadb" and "kfastboot". You just need to supply your own Terminal Emulator (such as connectbot) to use.
Example Uses
1) Unlock a bootloader on a Nexus device (erases all data on the target device)
kfastboot oem unlock
2) Lock a bootloader
kfastboot oem lock
3) Boot a recovery
kfastboot boot /sdcard/path/to/recovery.img
4) Flash a recovery
kfastboot flash recovery /sdcard/path/to/recovery.img
5) Reboot into the bootloader
kadb reboot bootloader
6) Shell
kadb shell
7) Reboot into recovery
kadb reboot recovery
8) logcat
kadb logcat
9) Sideload an APK file
kadb install /sdcard/path/to/APK.APK
10) Push a file
kadb push /sdcard/path/to/file /sdcard/path/to/destination
Please remember that these are taking place on the remote device connected via USB. Most, if not ALL ADB commands are supported. You can even modify most linux based one-click root methods (by changing all "adb" references to "kadb" and "fastboot" with "kfastboot") and run them via shell. Its also perfect for remote debugging of embedded Android Systems. Hell, the uses are endless!
Installation Instructions
Note : You do not need to be rooted, you do however need a custom recovery or temp boot a custom recovery.
1) Flash the attached Zip File via any Recovery such as CWM or TWRP
2) Reboot and install a Terminal Emulator, if using ConnectBot, you should choose the "local" option.
3) Connect a device and test
This should support any ARM based device, so far I have tested it on my ASUS Nexus 7 and ASUS Transformer 700 (Stock/Rooted)
HAVE FUN!!!
Click to expand...
Click to collapse
Very interesting and nice work, certainly a lot of interesting possibilities for apps that could be written to take advantage of these features.
Awesome Post. Thanks Alot.Need this tool very much .
shimp208 said:
Very interesting and nice work, certainly a lot of interesting possibilities for apps that could be written to take advantage of these features.
Click to expand...
Click to collapse
Yeh... I can picture one of you going to a store and rooting all of the Demo Tablets or Phones with your phones. With a small amount of effort, one can port ZergRush or a few of the "adb backup restore" exploits over to run naively on your Phone or Tablet.
No GameStop, BestBuy, Sprint Store, T-Mobile Store, AT&T Store, CompUSA or WalMart is safe
KMyers said:
Yeh... I can picture one of you going to a store and rooting all of the Demo Tablets or Phones with your phones. With a small amount of effort, one can port ZergRush or a few of the "adb backup restore" exploits over to run naively on your Phone or Tablet.
No GameStop, BestBuy, Sprint Store, T-Mobile Store, AT&T Store, CompUSA or WalMart is safe
Click to expand...
Click to collapse
Or Verizon Store, or any other store that sells smartphones and tablets . You could make a app that has a run button that when pressed automatically run's a root exploit such as Zerg Rush, then permanently flashes a custom recovery, then a custom ROM of your choice all one after the other. Think of it as mix of z4root, EZ-Recovery, and ROM manager all rolled into one. Only problem is not every device supports fastboot so some devices would be left out. Also wondering if you wouldn't mind clarifying if the target device must be running a custom recovery or the host device must be running a custom recovery for this to work?
shimp208 said:
eft out. Also wondering if you wouldn't mind clarifying if the target device must be running a custom recovery or the host device must be running a custom recovery for this to work?
Click to expand...
Click to collapse
Hello,
Just the host device needs a custom recovery only to install the tools (this can be perm flashed or temp flashed (fastboot boot recovery.img). Once the tools are installed, the recovery is no longer used.
The target device only needs USB Debugging enabled.
You are also correct in your statement that not all phones respond to the Fastboot protocol. The other tools such as Odin and NVFlash are not so easy to package. Some devices such as the ASUS Transformer TF700 have a Fastboot mode, assuming you unlock the bootloader. Fastboot is the standard on all HTC, Sony and any phone bearing the sacred "Nexus" moniker. It is also favored among "cheap/knockoff" devices.
There are several root tools that simply use adb to work.
What?!
KMyers said:
Hello All,
I have taken the liberty of re-packaging the adb binary and fastboot binaries so they will work naively on Android into a flashable zip file. With these tools, you can theoretically use your Android device (plus a USB OTG Cable) to connect to another Android Device. If your device has a native USB port (such as the ASUS Transformers), it will work as well.
As not to conflict with the official adb in /system/bin (which does not work the same way), I renamed these to "kadb" and "kfastboot". You just need to supply your own Terminal Emulator (such as connectbot) to use.
.....
HAVE FUN!!!
Click to expand...
Click to collapse
I'm truly stumped as to why you don't have pages of thank you posts here but I wanted to add mine. So often I cannot get to my PC or just want more freedom but need to use Fastboot. Now I'm free! Thank you so much! I
rainabba said:
I'm truly stumped as to why you don't have pages of thank you posts here but I wanted to add mine. So often I cannot get to my PC or just want more freedom but need to use Fastboot. Now I'm free! Thank you so much! I
Click to expand...
Click to collapse
Thanks,
I guess the reason many have not downloaded this is because it was stuck in one of the lesser active sections of XDA-Developers. I assume that most people visit the portal and device specific development threads. Aside from being featured on the portal, not many ways to get people in here.
Just tried this out on my nexus 7 running ubuntu, this is indeed awesome, thanks for compiling it
Hi, just came across this whilst trying to find a solution to flashing a custom recovery on an Nexus 7 that i cannot get to a computer. (its in my car). this would fit my needs perfectly but i just cannot get it to work. wondering if im missing something.
ive tried using another N7, and also my Galaxy Nexus. i plug in using an OTG cable on host device, then a USB cable to the target device. the target device starts to charge, and it shows debugging icon on notification bar.
Then try "kadb devices" but shows no devices. could it be to do with the adb binaries needing updating? (current adb is 1.0.31, this one is 1.0.29).. All devices are running stock rooted 4.2.2 (except the target device, that im trying to root.)
i have a friend interested too, he tried with a 4.2.2 Nexus 7 to a HTC One X and is seeing similar issue.
hope theres an easy fix, or something obvious im doing wrong.
Cheers
Ross.
rmclardy said:
Hi, just came across this whilst trying to find a solution to flashing a custom recovery on an Nexus 7 that i cannot get to a computer. (its in my car). this would fit my needs perfectly but i just cannot get it to work. wondering if im missing something.
ive tried using another N7, and also my Galaxy Nexus. i plug in using an OTG cable on host device, then a USB cable to the target device. the target device starts to charge, and it shows debugging icon on notification bar.
Then try "kadb devices" but shows no devices. could it be to do with the adb binaries needing updating? (current adb is 1.0.31, this one is 1.0.29).. All devices are running stock rooted 4.2.2 (except the target device, that im trying to root.)
i have a friend interested too, he tried with a 4.2.2 Nexus 7 to a HTC One X and is seeing similar issue.
hope theres an easy fix, or something obvious im doing wrong.
Cheers
Ross.
Click to expand...
Click to collapse
Hello Ross,
The new "secure adb" that was introduced in Android 4.2.2 will not work at this time. You may be able to try running "adb devices" at root to see if it works for you. If not, you can manually reboot it into recovery and use kfastboot to flash the new recovery
Hi Keith, thanks for the reply.
sorry for my delayed response, busy few days!. I did have another go at seeing if i could get two devices talking to each other using kfastboot, but again, i dont seem to be picking anything up. "kfastboot devices" just returns me to the prompt with no devices listed. im trying between a galaxy nexus and another nexus 7. my other problem is that the one i have fiited in the car no longer has access to the volume keys, so i cant even manually get into the bootloader. Shame its not possible to turn off the secure adb feature. lol.
it was worth a try tho.
Cheers
Ross.
rmclardy said:
Hi Keith, thanks for the reply.
sorry for my delayed response, busy few days!. I did have another go at seeing if i could get two devices talking to each other using kfastboot, but again, i dont seem to be picking anything up. "kfastboot devices" just returns me to the prompt with no devices listed. im trying between a galaxy nexus and another nexus 7. my other problem is that the one i have fiited in the car no longer has access to the volume keys, so i cant even manually get into the bootloader. Shame its not possible to turn off the secure adb feature. lol.
it was worth a try tho.
Cheers
Ross.
Click to expand...
Click to collapse
Hello Ross,
If your device is currently rooted, you should be able to run an App from the Play Store to reboot it into recovery (https://play.google.com/store/apps/details?id=com.liveov.rebooter ), from there, kfastboot will work
Great tool. Just unlocked, installed recovery and rooted my Google Nexus 4 with my Asus TF300t.
It only took a while before I figured out that the first terminal command must be SU before I could use the kfastboot command.
Thanks for your work.
Harald
Verstuurd van mijn Nexus 4 met Tapatalk
777.300 said:
Great tool. Just unlocked, installed recovery and rooted my Google Nexus 4 with my Asus TF300t.
It only took a while before I figured out that the first terminal command must be SU before I could use the kfastboot command.
Thanks for your work.
Harald
Verstuurd van mijn Nexus 4 met Tapatalk
Click to expand...
Click to collapse
Hello,
You would be correct as Fastboot needs root access to be able to run (it is the same as fastboot on Ubuntu)
KMyers said:
Hello,
You would be correct as Fastboot needs root access to be able to run (it is the same as fastboot on Ubuntu)
Click to expand...
Click to collapse
Yes I know but did not remember it when using your great tool for the first time. Perhaps it is good to mention it in your first post.
You build a great tool, still amazed that I was able to unlock, root and install a recovery on my Nexus 4 thru my Asus tablet while on vacation . (laptop at home)
Just great.
Harald
Verstuurd van mijn ASUS Transformer Pad TF300T met Tapatalk
777.300 said:
Yes I know but did not remember it when using your great tool for the first time. Perhaps it is good to mention it in your first post.
You build a great tool, still amazed that I was able to unlock, root and install a recovery on my Nexus 4 thru my Asus tablet while on vacation . (laptop at home)
Just great.
Harald
Verstuurd van mijn ASUS Transformer Pad TF300T met Tapatalk
Click to expand...
Click to collapse
Yes, I had a similar issue a few weeks ago. I was in Texas for a few days and my HTC EVO 4G LTE had an unfortunate run in with the Drink Cart on the Airplane. I had to go out and purchase a new phone at the Sprint Store in Texas. I had the phone purchased and rooted in about 10 minutes . Thanks to revone, unlocking the bootloader on the HTC one took almost no effort and I had S-Off to boot. All from my ASUS Transformer 700
so this is only for nexus?
Thank you very much!,
Testing on Samsung Galaxy Y
Just what i was looking for
I am yet to test it out, but i surely am very happy to see this thing actually exists. Just googled it out of the the blue and "kaboom!"here it was..
Keep up the good work.
Cheers
Hello XDA community, this is my first thread, i had never needed to post anything cause i always find everything im searching for in this awesome community... until now :crying:
Last week I got a new android device which is made by Polaroid, model: PSPR355, its a pretty low class device but I thought it would be enough for me.... then i realize I needed root permissions, for obvious reasons... easy I thought... i had rooted many devices...how hard can it be...right?... WRONG! :crying: . The first problem I encountered were the drivers..couldnt find em anywhere... fortunatelly i found a tutorial were i could install the drivers in a different way...although I took 2 days to do this...Ive been about 5 days trying to root my phone.... Ive tryied about 10 different programs with their different versions... and any of those rooted my phone, nor Oneclikroot, nor Unlockroot, etc, etc..... I really gave up trying to find something on the web cause i didnt even find the phone on its official site, so I came her defeated asking for any solution, idea, or if you want to help me with commands, a programm or anything else to root my phone, Im not even afraid of trying programming (Im trying to learn how to make roms, kernels, etc for this phone cause theres nothing on the web abou it but this is a theme for another time) if you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
MecaMarck said:
If you wanted to help me i would really appreciate it, im a little desperate so anything would come useful thanks everyone and I hoppe you can help me!!! :fingers-crossed:
Click to expand...
Click to collapse
I would recommend trying the towelroot application. It can be downloaded from here, just click on the orange lambda to download the tr.apk file. Then open towelroot follow the instructions in the application. After the device reboots I would recommend downloading, Root Checker Basic form the Play Store and running that to make sure your device is rooted. Finally install SuperSU, and you should be good to go.
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
MecaMarck said:
First thanks for answering so fast shimp208! And I guess I forgot to tell that I was in Mexico and Im using Telcel's network, I downloaded and installed the apk file but it doesnt starts I click the button pops up a black screen and then closes to the last app I used...any idea about this error...or if its beacuse of the carrier, by the way the device has Android 2.3.7 I dont know if it has something to do with this error
Click to expand...
Click to collapse
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
shimp208 said:
Does it present an error message of any kind before it force closes? Try uninstalling and then re-installing the application, and if that doesn't work go to application manger under settings, find the towelroot application and select the options to clear it's cache and data. The carrier won't have any effect in this case, and with it being Android 2.3.7 your device most definitely has a kernel build date before June 3rd, 2014.
Click to expand...
Click to collapse
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
MecaMarck said:
No it simply closes without showing anything, and without even giving the "Force Close" message, i thought it was because i first installed it on the sd card, or because of not enough space but no, I moved it to the phone and uninstalled some apps I had, I uninstalled and installed towelroot twice and it didnt work, I installed the v1 of it and i got to the [make it ra1n] screen but when I click the button it closes immediately again without any error message
Click to expand...
Click to collapse
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
shimp208 said:
Very interesting, while in theory the app should work for any kernel build date earlier then June 3rd, 2014 the app many not be compatible with devices running an Android version less then 4.x.
Click to expand...
Click to collapse
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
MecaMarck said:
Yes that´s what i thought, do you think that theres no rooting method for this phone? if so, do yo think there´s a way of doing one?
Click to expand...
Click to collapse
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Interesting for me.,.
Sent from my LT26w using xda premium
Same Boat
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
klonic0 said:
I'm in the same boat
I use moto-fastboot (any way it's fastboot)
#:\moto-fastboot devices
? fastboot
don't show any info...
I do a system dump in this way
#:\adb pull / c:\PSPR355
mega,co,nz/#!ThIUQYiS!LLbJ9e1-yVJI4juNlWQuPfa9GFH6HP9lr4X8Gwu1MBY
Change "," please, sorry mod if you want i can delete it! =$
Click to expand...
Click to collapse
Unfortunately if fastboot doesn't show your device without any other flashing utility, even with the system dump there is no way to flash a rooted system image if it was created.
Got to see if this guys do the trick!
http://forum.xda-developers.com/showthread.php?t=2066041
shimp208 said:
Since you have the usb drivers working on your computer, try booting into the bootloader and using fastboot to see if the command fastboot devices returns anything. If the computer see's the device in fastboot that's a good sign. If your device doesn't have a locked bootloader which it likely doesn't, then I can try and create a rooted system image for you to flash in fastboot. Provided fastboot see's your device if it does, if you can provide me an adb dump of your /system folder then I will see what can be done.
Click to expand...
Click to collapse
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
MecaMarck said:
Hello shimp well I connected my device on FastBoot Mode and my computer recognized it and it installed a driver named: ADB Testing Interface I dont know if thats a good sign or what should I do, I tried entering into recovery mode but it shows only an android little guy and exclamation quote... so I think it doesnt have a recovery boot I dont know if thats relevant, Could you help with the adb dump i dont know how to get it. And.... I dont know if besides you help me with the rooted system image you could teach me how I do this.... anyways thanks a lot for helping me! I'll keep doing everything you need so we can root this device!
Click to expand...
Click to collapse
Since your computer recognizes the device and installed the driver and shows the device when in fastboot mode that's a good sign. The Android with the exclamation point is part of normal stock Android system recovery, it just means that the recovery menu has been hidden (You should be able to get the menu to appear by pressing the power and both the volume buttons in recovery mode). To dump /system run the following command:
Code:
adb pull /system
Then please send me a link to the /system dump, from there I will make a rooted system image.
Factory Rooted??
Hey guys I'm new to this so I may be wrong but has anybody thought to check if the Polaroid PSPR355 comes Factory Rooted??? I had a Polaroid Tablet, PID something(I forget the name), which I tried for hours to root resulting in: bootloop, hard reset, root, bootloop, hard reset, root, bootloop, hard reset, about to give up. So I Googled how to root Polaroid PID something (again, I forget the name), and I come to a post somewhere(forgot that too) that tells me my Tablet and similar Polaroid electronic devices(as well as most electronic devices coming from China) are factory rooted due to some Chinese law. So after the last hard reset, I downloaded HowToRoot App to check if my Polaroid Tablet is, in fact, rooted. I press the little lock button(root checker) and I find that, to my surprise, my Polaroid Table is in fact rooted. So all I had to do was download SuperSU from Google Play Store and Update Binary when prompted and I was Super User. Don't know if this helps but it worked for me.
I have a passcode locked LG Rebel 4 - LML212VL and cant get into download mode.. Ideas?
I need to recover a clients data and the only way for me to do this is through LGLAF or with a box that can remove the pattern lock.. However all ive managed to get to is recovery and that is it.. No download mode.. Being a Tracfone i know fastboot is disabled but download mode should not be. Now seeing that it is passcode locked is there a chance a security feature is blocking me from getting to Download mode??
Any help is much appreciated.
@noidodroid
If device is accesable in ADB mode, why don't pull out the data in question?
Code:
adb devices
adb pull <remote data location> <local location>
jwoegerbauer said:
@noidodroid
If device is accesable in ADB mode, why don't pull out the data in question?
Code:
adb devices
adb pull <remote data location> <local location>
Click to expand...
Click to collapse
Yeah if I could enable ADB i would do this. However i'm stuck on passcode screen. Know any ways?
noidodroid said:
I have a passcode locked LG Rebel 4 - LML212VL and cant get into download mode.. Ideas?
I need to recover a clients data and the only way for me to do this is through LGLAF or with a box that can remove the pattern lock.. .
Click to expand...
Click to collapse
The LG tools like LGUP will change the mode when necessary.
They do it by sending an AT command... AT%DLOAD
What next then? The data is still encrypted...
:fingers-crossed:
@noidodroid or whoever might need this.
Here is how to use AT...
First check in Device Manager (devmgmt. msc) what COM port LG is using - under the Modems.
Then use Putty terminal or similar program to give the command(s).
Or "blindly" by using dos prompt. (You don't see the answers. )
First get the port to use and then echo the command.
Code:
[B]reg query HKLM\hardware\devicemap\SERIALCOMM[/B]
\Device\LGANDNET[B]MDM0[/B] REG_SZ [B]COM##[/B] <--use this
\Device\LGANDNETDIAG1 REG_SZ COM$$
[B]echo AT%DLOAD>\\.\COM##[/B]
AT commands taken from my LG's /system/bin/atd , laf probably have some more...
AT#CLS, AT$LGAPP, AT$NSRI, AT$PRL, AT%AATEND, AT%AATFULL, AT%AATINIT, AT%AATORDERSET, AT%AATSET, AT%AATSTART, AT%ACCEL, AT%ACS, AT%ALC, AT%ANTCONF, AT%ANTINFO, AT%BAROMETER, AT%BATL, AT%BATMP, AT%BATT, AT%BATTLEVEL, AT%BATTTEMP, AT%BATTTEMPINFO, AT%BCPE, AT%BCPL, AT%BLEDSTART, AT%BLEDSTOP, AT%BTAD, AT%BTLER, AT%BTLET, AT%BTTM, AT%BUILDDATE, AT%CALCK, AT%CALDT, AT%CAMP, AT%CAMPREQ, AT%CHANGEWTR, AT%CHARGE, AT%CHARGINGMODEOFF, AT%CHCOMP, AT%CHECKFOTAPACKAGE, AT%CHIPSET, AT%CLOCKSTATUSCPU, AT%CLOCKSTATUSGPU, AT%CLOCKSTATUSSETCPU, AT%CMDLOCK, AT%CMPCPUFULL, AT%CODECRC, AT%COMPASS, AT%COVERDETECT, AT%CPUFULL, AT%CPUFULLINFO, AT%CSN, AT%DATST, AT%DBCHK, AT%DBCOPY, AT%DBDUMP, AT%DCTEST, AT%DETACH, AT%DEVICEID, AT%DEVICETEST, AT%DLOAD, AT%DTLOGCAT, AT%EARJACK, AT%ECALL, AT%EFUSECHECK, AT%EFUSEENABLE, AT%EFUSERESULT, AT%EFUSEVERIFICATION, AT%EMMCSIZE, AT%EMMREJECT, AT%EMT, AT%ENCRYPT, AT%ENCRYPTMOUNTDATA, AT%ENCRYPTONBOOT, AT%ETM, AT%FBOOT, AT%FIDOCHECK, AT%FIDOERASE, AT%FIDOWRITE, AT%FILECRC, AT%FKPD, AT%FLIGHT, AT%FMR, AT%FPCKBOARD, AT%FPRICRC, AT%FPRUBSTAMP, AT%FPSPI, AT%FPZONE, AT%FRST, AT%FRSTSTATUS, AT%FSM, AT%FSMDRESULT, AT%FSMMIC, AT%FSMMODE, AT%FSMRESULT, AT%FSMSTART, AT%FSMSTATUS, AT%FSMVERSION, AT%FTM, AT%FTMMAGIC, AT%FUELRST, AT%FUELVAL, AT%FUSE, AT%FUSECHECK, AT%FUSG, AT%GERANCAPDISABLE, AT%GKPD, AT%GNSS, AT%GNSS1, AT%GPIO, AT%GREBOOTSTATUSCLR, AT%GSTATUS, AT%GSTATUSCLR, AT%GWIFI, AT%GWLANSSID, AT%GYRO, AT%HALLIC, AT%HDCP, AT%HDCPERASE, AT%HDCPID, AT%HDCPST, AT%HMEXT, AT%HWVER, AT%IDDE, AT%IMEI, AT%IMEI2, AT%IMEI3, AT%IMPL, AT%IMSTESTMODE, AT%INFO, AT%IRRC, AT%ISSIM, AT%KCAL, AT%KEYLOCK, AT%KPHVERSION, AT%KSANTITHEFTSTATUS, AT%KSCHECKLOCK, AT%KSDOUNLOCK, AT%KSGETEXTRA, AT%KSGETLAFLOCK, AT%KSOSTYPE, AT%KSSERIALNO, AT%KSTYPE, AT%KSUNLOCKSTATUS, AT%KSWITCH, AT%LCATT, AT%LCD, AT%LCDCAPTURE, AT%LCIMSSETCFG, AT%LED, AT%LEDON, AT%LGANDROID, AT%LGATSERVICE, AT%LGPWD, AT%LOGSAVE, AT%LOGSERVICE, AT%LTEAUTHFAIL, AT%LTECALL, AT%LTERFMODE, AT%LTL, AT%LTR, AT%LTRST, AT%MAC, AT%MAINCAMERAID, AT%MAXCPU, AT%MAXCT, AT%MDATE, AT%MDMLOG, AT%MDMPVS, AT%MEID, AT%MIMOANTCHECK, AT%MINIOS, AT%MLT, AT%MMCCONTENTSINTEGRITY, AT%MMCFACTORYFORMAT, AT%MMCFORMAT, AT%MMCISFORMATTED, AT%MMCTOTALSIZE, AT%MMCUSEDSIZE, AT%MOBICORE, AT%MOBICOREERASE, AT%MODELNAME, AT%MODEMCHK, AT%MODEMRESET, AT%MOT, AT%MPDECISION, AT%MPT, AT%MSN, AT%MTSLOG, AT%MTSLOGERS, AT%MTSLOGGET, AT%NCM, AT%NFC, AT%NTCODE, AT%NTCODECHANGE, AT%NTSWAP, AT%ONECMD, AT%OPNAMEREAD, AT%OPRESIZECHECK, AT%OSPPWDINIT, AT%OSVER, AT%PCBREV, AT%PMRST, AT%PNUM, AT%POWEROFF, AT%PRECPUFULL, AT%PROCCAT, AT%PROPTCAT, AT%PROXIMITY, AT%PROXIMITYCAL, AT%PSCAT, AT%PSELFDE, AT%PST, AT%PTNCLR, AT%QEM, AT%QFUSEVERI, AT%RADIATIONRESULT, AT%RAMSIZE, AT%RCT, AT%REATTACH, AT%RESTART, AT%RFDEVCHK, AT%RPMBMANUALPROVISIONING, AT%RPMBSTATUSCHECK, AT%RTC, AT%SAATRESULT, AT%SATPC, AT%SATPC2, AT%SCHK, AT%SDCHECK, AT%SELFDRESULT, AT%SEQCPUFULL, AT%SERIALNO, AT%SETREV, AT%SIMID, AT%SIMIMSI, AT%SIMOFF, AT%SIMPWDINIT, AT%SIMTRAY, AT%SLEN, AT%SLTYPE, AT%SPTCHK, AT%SPTLOCK, AT%SPTUNLOCK, AT%STARTDAYCHECK, AT%STARTFOTAPACKAGE, AT%SUBCAMERAID, AT%SUFFIX, AT%SULC, AT%SURV, AT%SWCV, AT%SWFV, AT%SWOV, AT%SWV, AT%SYSCAT, AT%TESTPATTERN, AT%TETHER, AT%THEME, AT%THERMALENGINE, AT%TOTALCRC, AT%TOUCHFWVER, AT%TOUCHLOG, AT%TSENS, AT%ULCV, AT%ULCW, AT%USB, AT%USBIDADC, AT%USBMODE, AT%USERDATASIZE, AT%VCOIN, AT%VLC, AT%VSLT, AT%VSLT2, AT%VSLT3, AT%VSLT4, AT%VZWAPNE, AT%VZWHM, AT%VZWIOTHM, AT%WALLPAPER, AT%WEBFLAG, AT%WLAN, AT%WLANCH, AT%WLANPING, AT%WLANR, AT%WLANT, AT%WORKFRSTMODEON, AT%XOTEMP, AT+CCLK, AT+CFUN, AT+CGMI, AT+CGMM, AT+CGMR, AT+CNUM, AT+CSDF, AT+CSO, AT+ESLP, AT+ESUO, AT+FUMO, AT+GCI, AT+GMI, AT+GMM, AT+LED, AT+MTC, AT+OMADM, AT+PRL, [email protected], [email protected], [email protected]
CXZa said:
@noidodroid or whoever might need this.
Here is how to use AT...
First check in Device Manager (devmgmt. msc) what COM port LG is using - under the Modems.
Then use Putty terminal or similar program to give the command(s).
Or "blindly" by using dos prompt. (You don't see the answers. )
First get the port to use and then echo the command.
Code:
[B]reg query HKLM\hardware\devicemap\SERIALCOMM[/B]
\Device\LGANDNET[B]MDM0[/B] REG_SZ [B]COM##[/B] <--use this
\Device\LGANDNETDIAG1 REG_SZ COM$$
[B]echo AT%DLOAD>\\.\COM##[/B]
AT commands taken from my LG's /system/bin/atd , laf probably have some more...
AT#CLS, AT$LGAPP, AT$NSRI, AT$PRL, AT%AATEND, AT%AATFULL, AT%AATINIT, AT%AATORDERSET, AT%AATSET, AT%AATSTART, AT%ACCEL, AT%ACS, AT%ALC, AT%ANTCONF, AT%ANTINFO, AT%BAROMETER, AT%BATL, AT%BATMP, AT%BATT, AT%BATTLEVEL, AT%BATTTEMP, AT%BATTTEMPINFO, AT%BCPE, AT%BCPL, AT%BLEDSTART, AT%BLEDSTOP, AT%BTAD, AT%BTLER, AT%BTLET, AT%BTTM, AT%BUILDDATE, AT%CALCK, AT%CALDT, AT%CAMP, AT%CAMPREQ, AT%CHANGEWTR, AT%CHARGE, AT%CHARGINGMODEOFF, AT%CHCOMP, AT%CHECKFOTAPACKAGE, AT%CHIPSET, AT%CLOCKSTATUSCPU, AT%CLOCKSTATUSGPU, AT%CLOCKSTATUSSETCPU, AT%CMDLOCK, AT%CMPCPUFULL, AT%CODECRC, AT%COMPASS, AT%COVERDETECT, AT%CPUFULL, AT%CPUFULLINFO, AT%CSN, AT%DATST, AT%DBCHK, AT%DBCOPY, AT%DBDUMP, AT%DCTEST, AT%DETACH, AT%DEVICEID, AT%DEVICETEST, AT%DLOAD, AT%DTLOGCAT, AT%EARJACK, AT%ECALL, AT%EFUSECHECK, AT%EFUSEENABLE, AT%EFUSERESULT, AT%EFUSEVERIFICATION, AT%EMMCSIZE, AT%EMMREJECT, AT%EMT, AT%ENCRYPT, AT%ENCRYPTMOUNTDATA, AT%ENCRYPTONBOOT, AT%ETM, AT%FBOOT, AT%FIDOCHECK, AT%FIDOERASE, AT%FIDOWRITE, AT%FILECRC, AT%FKPD, AT%FLIGHT, AT%FMR, AT%FPCKBOARD, AT%FPRICRC, AT%FPRUBSTAMP, AT%FPSPI, AT%FPZONE, AT%FRST, AT%FRSTSTATUS, AT%FSM, AT%FSMDRESULT, AT%FSMMIC, AT%FSMMODE, AT%FSMRESULT, AT%FSMSTART, AT%FSMSTATUS, AT%FSMVERSION, AT%FTM, AT%FTMMAGIC, AT%FUELRST, AT%FUELVAL, AT%FUSE, AT%FUSECHECK, AT%FUSG, AT%GERANCAPDISABLE, AT%GKPD, AT%GNSS, AT%GNSS1, AT%GPIO, AT%GREBOOTSTATUSCLR, AT%GSTATUS, AT%GSTATUSCLR, AT%GWIFI, AT%GWLANSSID, AT%GYRO, AT%HALLIC, AT%HDCP, AT%HDCPERASE, AT%HDCPID, AT%HDCPST, AT%HMEXT, AT%HWVER, AT%IDDE, AT%IMEI, AT%IMEI2, AT%IMEI3, AT%IMPL, AT%IMSTESTMODE, AT%INFO, AT%IRRC, AT%ISSIM, AT%KCAL, AT%KEYLOCK, AT%KPHVERSION, AT%KSANTITHEFTSTATUS, AT%KSCHECKLOCK, AT%KSDOUNLOCK, AT%KSGETEXTRA, AT%KSGETLAFLOCK, AT%KSOSTYPE, AT%KSSERIALNO, AT%KSTYPE, AT%KSUNLOCKSTATUS, AT%KSWITCH, AT%LCATT, AT%LCD, AT%LCDCAPTURE, AT%LCIMSSETCFG, AT%LED, AT%LEDON, AT%LGANDROID, AT%LGATSERVICE, AT%LGPWD, AT%LOGSAVE, AT%LOGSERVICE, AT%LTEAUTHFAIL, AT%LTECALL, AT%LTERFMODE, AT%LTL, AT%LTR, AT%LTRST, AT%MAC, AT%MAINCAMERAID, AT%MAXCPU, AT%MAXCT, AT%MDATE, AT%MDMLOG, AT%MDMPVS, AT%MEID, AT%MIMOANTCHECK, AT%MINIOS, AT%MLT, AT%MMCCONTENTSINTEGRITY, AT%MMCFACTORYFORMAT, AT%MMCFORMAT, AT%MMCISFORMATTED, AT%MMCTOTALSIZE, AT%MMCUSEDSIZE, AT%MOBICORE, AT%MOBICOREERASE, AT%MODELNAME, AT%MODEMCHK, AT%MODEMRESET, AT%MOT, AT%MPDECISION, AT%MPT, AT%MSN, AT%MTSLOG, AT%MTSLOGERS, AT%MTSLOGGET, AT%NCM, AT%NFC, AT%NTCODE, AT%NTCODECHANGE, AT%NTSWAP, AT%ONECMD, AT%OPNAMEREAD, AT%OPRESIZECHECK, AT%OSPPWDINIT, AT%OSVER, AT%PCBREV, AT%PMRST, AT%PNUM, AT%POWEROFF, AT%PRECPUFULL, AT%PROCCAT, AT%PROPTCAT, AT%PROXIMITY, AT%PROXIMITYCAL, AT%PSCAT, AT%PSELFDE, AT%PST, AT%PTNCLR, AT%QEM, AT%QFUSEVERI, AT%RADIATIONRESULT, AT%RAMSIZE, AT%RCT, AT%REATTACH, AT%RESTART, AT%RFDEVCHK, AT%RPMBMANUALPROVISIONING, AT%RPMBSTATUSCHECK, AT%RTC, AT%SAATRESULT, AT%SATPC, AT%SATPC2, AT%SCHK, AT%SDCHECK, AT%SELFDRESULT, AT%SEQCPUFULL, AT%SERIALNO, AT%SETREV, AT%SIMID, AT%SIMIMSI, AT%SIMOFF, AT%SIMPWDINIT, AT%SIMTRAY, AT%SLEN, AT%SLTYPE, AT%SPTCHK, AT%SPTLOCK, AT%SPTUNLOCK, AT%STARTDAYCHECK, AT%STARTFOTAPACKAGE, AT%SUBCAMERAID, AT%SUFFIX, AT%SULC, AT%SURV, AT%SWCV, AT%SWFV, AT%SWOV, AT%SWV, AT%SYSCAT, AT%TESTPATTERN, AT%TETHER, AT%THEME, AT%THERMALENGINE, AT%TOTALCRC, AT%TOUCHFWVER, AT%TOUCHLOG, AT%TSENS, AT%ULCV, AT%ULCW, AT%USB, AT%USBIDADC, AT%USBMODE, AT%USERDATASIZE, AT%VCOIN, AT%VLC, AT%VSLT, AT%VSLT2, AT%VSLT3, AT%VSLT4, AT%VZWAPNE, AT%VZWHM, AT%VZWIOTHM, AT%WALLPAPER, AT%WEBFLAG, AT%WLAN, AT%WLANCH, AT%WLANPING, AT%WLANR, AT%WLANT, AT%WORKFRSTMODEON, AT%XOTEMP, AT+CCLK, AT+CFUN, AT+CGMI, AT+CGMM, AT+CGMR, AT+CNUM, AT+CSDF, AT+CSO, AT+ESLP, AT+ESUO, AT+FUMO, AT+GCI, AT+GMI, AT+GMM, AT+LED, AT+MTC, AT+OMADM, AT+PRL, [email protected], [email protected], [email protected]
Click to expand...
Click to collapse
Right on man! These are definitely helpful. I was using some AT tools and a script to run all commands in a database i have to see which were compatible with certain LG phones but I never got to finish the project. Now my only problem with this phone. here is i get no modem / com ports. I think it is possibly a security feature? I could see LG locking out people from download mode when phone is passcode locked unless they goto recovery and wipe it...
I need to find another way to do this or a way using FWUL, MAID etc (once modem recognized) unless someone knows how to get the modem to work.
Thanks for the wonderful information bro i will definitely save it and make use of it. Love toying around with AT commands, always have.
noidodroid said:
Now my only problem with this phone. here is i get no modem / com ports. I think it is possibly a security feature? I could see LG locking out people from download mode when phone is passcode locked unless they goto recovery and wipe it...
I need to find another way to do this or a way using FWUL, MAID etc (once modem recognized) unless someone knows how to get the modem to work.
Click to expand...
Click to collapse
Tried with my LG10 2017 m250n. Even with secure startup the com ports work, adb doesn't though.... Also recovery shows some COM ports. It's shows it as LG device, but there is no driver installed. Maybe reinstalling the driver package would help, IDK..
edit:
Those recovery COM ports show only if you enter recovery from laf download mode and quite shortly too.
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGSIDIAG1 REG_SZ COMxx
\Device\LGSIMDM0 REG_SZ COMyy
Also noticed that both LGANDNETMDM# or LGANDNETDIAG# device will do... goes to DLOAD mode..
CXZa said:
Tried with my LG10 2017 m250n. Even with secure startup the com ports work, adb doesn't though.... Also recovery shows some COM ports. It's shows it as LG device, but there is no driver installed. Maybe reinstalling the driver package would help, IDK..
edit:
Those recovery COM ports show only if you enter recovery from laf download mode and quite shortly too.
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGSIDIAG1 REG_SZ COMxx
\Device\LGSIMDM0 REG_SZ COMyy
Also noticed that both LGANDNETMDM# or LGANDNETDIAG# device will do... goes to DLOAD mode..
Click to expand...
Click to collapse
Yeah I have never had an issue getting those ports until this clients passcode locked tracfone. I think tracfone locks down everything.
I know there are some methods of getting LG's into certain modes on zero % battery but haven't tried this yet.
Unfortunately and i guess fortunately lol this phone went back to the client. They are having to go back through notes to find possible entries. Good luck to them.
Thanks for the help everyone!
CXZa said:
Tried with my LG10 2017 m250n. Even with secure startup the com ports work, adb doesn't though.... Also recovery shows some COM ports. It's shows it as LG device, but there is no driver installed. Maybe reinstalling the driver package would help, IDK..
edit:
Those recovery COM ports show only if you enter recovery from laf download mode and quite shortly too.
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGSIDIAG1 REG_SZ COMxx
\Device\LGSIMDM0 REG_SZ COMyy
Also noticed that both LGANDNETMDM# or LGANDNETDIAG# device will do... goes to DLOAD mode..
Click to expand...
Click to collapse
At what point is recovery showing the com ports? And are you just checking Device Manager or? And how to get into laf download mode to enter recovery from? LAF download is this the normal old download mode? If so i have never been able to switch over to recovery unless it is using some AT command that works (i have tried a handful and none work in download mode so far - LG Phoenix 4)
Also thank you 1000% again for the AT commands. I already found what i need and client is bringing phone back to me so i will give it a whirl and see what happens. Already locking up various LG phones here just to try it out.. IF you have any confirmed working AT commands and such lmk privately if you want and when done i can swap with you what all I have found to work the most. I was reading on security forums about how repairing imei, unlocking and other such actions are taken out using serial port for the most part and can be done in terminal (well it is one way) but not a lick of more information have i found on the topics yet. Just 3 white hat security forums. heh
Right when recovery starts for maybe minute or two. Doing something in recovery which prevents continuing to the normal boot doesn't help. Shows in device manager.
In MTK devices one can run multi_init in laf mode and as it fails it will go to the recovery. In Snapdragons is there such? IDK, but you might be able mount a sdcard formatted as ext4 and try to run it from there. I have run some programs that way - I believe, but cannot really remember much. What I did I tested if I could modify multi_init to boot into bootloader. It run but just normal boot happened. But maybe it could be modified to boot into edl?? Renaming it to something that can be run maybe needed...
Interesting to see what you've found out about AT commands, if you're willing to share.
PM if so, LG is watching me already...
(happened to found the LGUP v1.17 and shared here, it's package was removed next day - plus some others...)
Very cool. I never thought of doing any of that. I especially like the EDL idea. I might run some of that by eliwiggy a previous admin and wiz with Samsung devices to see what he says also.
I had a break through in FRP removal using AT commands recently. I found a way to get out from some locked LG devices using SVC stuff and AT commands. Nobody is doing this AFAIK... As for screen locks no success yet on newer devices. I will get in touch with you and we can chat.
Hmm so you can't get into download mode. Why don't you reset the phone first then connect to the internet when it asks and then find a way to open up a browser. If you can open up the browser you can download and install apk's and what not. That's how I FRP unlocked my Aristo 2.
I have done this already. No way into browser on the device i tried it on. Weird device too.. MS210.. I have been able to bypass this device no problem before until someone updated the firmware i think.. Mindboggling..
Anywho here is how i bypassed it and so far i think this method should work on all similar. I couldn't get security patch level as i had to give device back to the client. :-/
New Way to Bypass LG - Google Factory Reset Protetion on VARIOUS Devices!!
New Way to Bypass LG - Google Factory Reset Protection on VARIOUS Devices! Ignore the poor grammar, typos etc.. Bits and pieces from notes. --needed-- bluetooth (needed) data cable (needed) computer (needed) Factory reset phone, forward...
forum.xda-developers.com
Credits for app goto those Yemen Fellas who have so far been able to bypass anything in front of them LG/Samsung Carrier - Sprint!! Tracfone --> FRP/Unlock
Credits also to @CXZa as if it weren't for him i probably would not have looked deeper into AT commands.
noidodroid said:
I have done this already. No way into browser on the device i tried it on. Weird device too.. MS210.. I have been able to bypass this device no problem before until someone updated the firmware i think.. Mindboggling..
Anywho here is how i bypassed it and so far i think this method should work on all similar. I couldn't get security patch level as i had to give device back to the client. :-/
New Way to Bypass LG - Google Factory Reset Protetion on VARIOUS Devices!!
New Way to Bypass LG - Google Factory Reset Protection on VARIOUS Devices! Ignore the poor grammar, typos etc.. Bits and pieces from notes. --needed-- bluetooth (needed) data cable (needed) computer (needed) Factory reset phone, forward...
forum.xda-developers.com
Credits for app goto those Yemen Fellas who have so far been able to bypass anything in front of them LG/Samsung Carrier - Sprint!! Tracfone --> FRP/Unlock
ALL YOU HAVE TO DO IS FACTORY RESET....THEN DURING SET UP TURN WIFI ON....THEN HOLD NEXT AND WIFI SWITCH AT SAME TIME...AND IT BYPASSES
Click to expand...
Click to collapse
Finish by setting lock pin then skip to start up...then developer options oem unlock and usb debugging...then factory reset from settings menu....$$$$
KtownJeff said:
Finish by setting lock pin then skip to start up...then developer options oem unlock and usb debugging...then factory reset from settings menu....$$$$
Click to expand...
Click to collapse
Bypass FRP LG Velvet Android 10 - Bypass frp Without PC
How to Remove FRP LG Velvet Android, How to bypass google account LG Velvet Android 10, Remove FRP LG Velvet Android ? All process can be done easily from
www.techeligible.com
Nice. I will check it out.
KtownJeff said:
Bypass FRP LG Velvet Android 10 - Bypass frp Without PC
How to Remove FRP LG Velvet Android, How to bypass google account LG Velvet Android 10, Remove FRP LG Velvet Android ? All process can be done easily from
www.techeligible.com
Click to expand...
Click to collapse
I wonder if anyone has found a way to carrier unlock these LG Velvet devices yet.. From what i hear nobody has. But there is always someone or some team.
If you just reset it and once you get to the wifi select screen, just click the button to turn wifi off and the next in bottom right at same time. It will continue setup offline and let you choose pin to get in.
Hey guys I’ve been here once or twice before but it’s been a while. I have some in the ass and I need your help please. I’ve been working at unlocking the boot loader on my Motorola Moto G power 2021 for two months now. The reasoning is for that I have no PC nor desktop rather one of my old android phones (Motorola Moto G7 Optimo) That I have had, Trying to figure out how to unlock my boot loader on my Motorola Moto G power 2021. I managed to unlock the boot loader finally but now I’m having issues with trying to install TWRP. My question is is that is there another custom room that I can install with two androids connected to USB – C double cable? I’ve been waiting for a long time to get my phone routed, please help and thanks
If you have one android rooted with magisk, there is an ADB/Fastboot Magisk module that might work for that, but I've never actually tried it. But I'm pretty sure one would have to be rooted. Another option might be to install linux on your phone. I have manjaro linux installed on mine but, again, it is limited without root because of selinux policy. With root, that can be disabled.
I also just noticed adb and fastboot can be installed in termux without root with
pkg install android-tools
You might try that.
If it workS, then YES, you can root without pc. Just 2 Android phones and a doubLe type c cable.
bryzone25 said:
but now I’m having issues with trying to install TWRP.
Click to expand...
Click to collapse
Don't install the TWRP we have now. Just boot it to use it with adb shell commands or a mouse. If you install it you'll get a bootloop, Dude says. I had to use it to extract my kernel for rooting.
Aaaannd the story thickens…. I ended up unlocking the boot loader with the two android phones and a USB – C type. However when I tried to flash Magisk, it flip my phone into a boot loop. Now, Me being the rookie that I am and trying to progress far too quickly, I Have relocked my boot loader and now I have a message which says no valid operating system can be found, will not boot.
Can someone please put me out of my misery and just go ahead and say that I am screwed?
Try to unlock your bootlloader againDamn I can't even type in here. Fgn xda is throwing up an ad over the typing area every time I make a cursor. Ok it finally stopped as I took a screenshot.
Now why on earth are you people trying to relock your bootloaders? I've rarely heard of such a thing and only to try to claim warranty, but I've been here for 2 days and already found 2 people with relocked (possible) bricks on this phone. And there aren't even many people here yet. What gives?
Don't worry yet. I think you're in better shape than the other guy.
If you still have your unlock email try to unlock it again with the same code. If you don't, or that doesn't work run get_unlock_data again and request another code.
BTW, I've never done this twice. So it might not work. If it doesn't, there is another option. Just come back and tell us how it went.
What carrier is your phone?
arkansawdave74 said:
Try to unlock your bootlloader againDamn I can't even type in here. Fgn xda is throwing up an ad over the typing area every time I make a cursor. Ok it finally stopped as I took a screenshot.
Now why on earth are you people trying to relock your bootloaders? I've rarely heard of such a thing and only to try to claim warranty, but I've been here for 2 days and already found 2 people with relocked (possible) bricks on this phone. And there aren't even many people here yet. What gives?
Don't worry yet. I think you're in better shape than the other guy.
If you still have your unlock email try to unlock it again with the same code. If you don't, or that doesn't work run get_unlock_data again and request another code.
BTW, I've never done this twice. So it might not work. If it doesn't, there is another option. Just come back and tell us how it went.
What carrier is your phone?
Click to expand...
Click to collapse
arkansawdave74 said:
so yeah I tried it again but the boot loader is still locked however I think the partitions are messed up after I was trying to flash magic and it fell right into a boot loop. Somehow it has actually gotten better and not continuously boot looping I can stay in fast boot but it won’t burn into anything else or power off unless it runs out of battery. But I do have the same code but it’s not taking hit it because OEM unlocking on developer mode is still locked.
Click to expand...
Click to collapse
So what other plans do you have I’m very curious to know? Also I am through straight talk on a TracFone. I’m also trying to unlock the boot loader on my Moto G7 optimo and I’ve tried the unlock data through Motorola and it says it can’t be unlocked but I think that’s b******t
Bry2025 said:
I’ve tried the unlock data through Motorola and it says it can’t be unlocked but I think that’s b******t
Click to expand...
Click to collapse
That used to happen to me a lot in the olden days when I used Windows and would manually type the code. I never know if they are Os or zeros. Now that I use linux I just copy/paste the code quick and easy. If you know that phone with that carrier can be unlocked, keep trying. In Android I know you can copy/paste from the terminal. I hear some carriers make you wait so long before unlocking too, although I've never had a phone with that problem. A good friend told me just the other day he had a Boost phone that they made him wait 6 months to unlock.
As far as plans, I got this phone by accident and dropped and broke the screen the 1st day I had it, before the case arrived. When the case arrived, it was a case for the G9 Power, which I thought this phone was when I ordered it. So, next month I will order the G9 Power since I already have a case and screen protector for it. My last phone was the G8 Stylus (sofiap) and this "Power" just doesn't have the same great battery life. I also had the G7 Power (ocean) and it had excellent battery life. I meant to get the G9 Power for the 6000 mAh battery, but with it's higher resolution screen it's probably no better than this Power. I think all "Power"s should have a 720P screen for the better battery life. or at least a switch to select the resolution you want like on my Galaxy S7.
This phone needs some ROMs though, so if I can find the time, I will do my best to give it a couple, if luck is on my side. Maybe a Resurrection Remix and a crDroid or Bliss. But really, it's whatever I can get to build, so maybe none. Lol.
Bry2025 said:
So what other plans do you have I’m very curious to know? Also I am through straight talk on a TracFone. I’m also trying to unlock the boot loader on my Moto G7 optimo and I’ve tried the unlock data through Motorola and it says it can’t be unlocked but I think that’s b******t
Click to expand...
Click to collapse
I think there's still hope for you. I'm trying to figure out which stock firmware version your phone came with. If we can figure that out, I think you can flash and boot it even with a locked bootloader. What splash screen and boot animation does it have? Is it tracphone? I see a US Cellular version. When you boot to the bootloader what does the 1st white line say on the lower left? The BL line?
Also, I assume you got fastboot working phone to phone. I've tried 3 different adb/fastboot installations and can't get it to work (Magisk module, the one from termux pkg install android-tools, and one from github.). Can you tell me how you did it?
arkansawdave74 said:
That used to happen to me a lot in the olden days when I used Windows and would manually type the code. I never know if they are Os or zeros. Now that I use linux I just copy/paste the code quick and easy.
Click to expand...
Click to collapse
I've used copy and paste on windows to unlock several moto devices.
It's the only sane way to do it.
sd_shadow said:
I've used copy and paste on windows to unlock several moto devices.
It's the only sane way to do it.
Click to expand...
Click to collapse
Yeah, I hear there is some trick to do it. Maybe in the new powershell (I've never tried it), but highlighting some text and right clicking to copy doesn't work in a command prompt, or it didn't 6 years ago. Did they add that functionality?
arkansawdave74 said:
Yeah, I hear there is some trick to do it. Maybe in the new powershell (I've never tried it), but highlighting some text and right clicking to copy doesn't work in a command prompt, or it didn't 6 years ago. Did they add that functionality?
Click to expand...
Click to collapse
I think I used copy/paste in cmd.exe since windows 7, but I don't know when it started working.
Well Damn....now I have one less way to insult Windows. Hey @sd_shadow , you would sure know...can you flash and boot the original firmware that came on your phone (same software channel) with a locked bootloader? Seems like you could but I've never tried it.
And @Bry2025 do you have USB Debugging enabled in Developer Options?
arkansawdave74 said:
Well Damn....now I have one less way to insult Windows. Hey @sd_shadow , you would sure know...can you flash and boot the original firmware that came on your phone (same software channel) with a locked bootloader? Seems like you could but I've never tried it.
And @Bry2025 do you have USB Debugging enabled in Developer Options?
Click to expand...
Click to collapse
Moto devices can be finicky.
You should be able to flash stock firmware with fastboot, but on windows rsd lite or the newer lsma work more reliably.
On windows mfastboot sometime works when standard fastboot.exe doesn't.
Linux may work better.
USB debugging doesn't effect fastboot mode, it's an adb function.
Edit:for locked bootloader
Booting stock .img may work for some devices
sd_shadow said:
USB debugging doesn't effect fastboot mode, it's an adb function.
Click to expand...
Click to collapse
Yes, but I was going to have him run
adb shell getprop | grep build.version.base
to figure out the software channel he needs. With the output I could find the exact build he is/was running on lolinet. That's hoping his bootloop is booting far enough for adb to enable though. adb shell wont work from stock recovery and adb shell from the quamp twrp we're using returns guamp device info. Wtf?
sd_shadow said:
On windows mfastboot sometime works when standard fastboot.exe doesn't.
Linux may work better.
Click to expand...
Click to collapse
On Linux fastboot seems to be flawless. I'm surprised to hear that it has trouble on Windows. But I think he's running fastboot from another android., which is so cool. Opens a door for root with no pc.
arkansawdave74 said:
I think there's still hope for you. I'm trying to figure out which stock firmware version your phone came with. If we can figure that out, I think you can flash and boot it even with a locked bootloader. What splash screen and boot animation does it have? Is it tracphone? I see a US Cellular version. When you boot to the bootloader what does the 1st white line say on the lower left? The BL line?
Also, I assume you got fastboot working phone to phone. I've tried 3 different adb/fastboot installations and can't get it to work (Magisk module, the one from termux pkg install android-tools, and one from github.). Can you tell me how you did it?
Click to expand...
Click to collapse
arkansawdave74 said:
I think there's still hope for you. I'm trying to figure out which stock firmware version your phone came with. If we can figure that out, I think you can flash and boot it even with a locked bootloader. What splash screen and boot animation does it have? Is it tracphone? I see a US Cellular version. When you boot to the bootloader what does the 1st white line say on the lower left? The BL line?
Also, I assume you got fastboot working phone to phone. I've tried 3 different adb/fastboot installations and can't get it to work (Magisk module, the one from termux pkg install android-tools, and one from github.). Can you tell me how you did it?
Click to expand...
Click to collapse
My Moto G power of 2021 is the one that I unlocked the boot loader with the code off of the Motorola site and then I tried to mess with Magis and it ended up boot looping so I tried to lock it again thinking that would help somehow and that’s where I’m at on that one. On the Moto G7 optimo I haven’t gotten anywhere with that one yet however I did get I haven't gotten anywhere with that one yet however I did get the Unlock data and put it on Motorola site and it said it can’t be unlocked. Also sorry but I’m new to this so I don’t understand about the splash screen and boot animation so please let me know what I need to do to give you that information.
Now with the phone to phone android to android, are used the Google app BUGJAEGER 3.0-full (164). Are used the command: fastboot oem unlock <unlock code> . And it unlocked right away.
arkansawdave74 said:
Well Damn....now I have one less way to insult Windows. Hey @sd_shadow , you would sure know...can you flash and boot the original firmware that came on your phone (same software channel) with a locked bootloader? Seems like you could but I've never tried it.
And @Bry2025 do you have USB Debugging enabled in Developer Options?
Click to expand...
Click to collapse
I just got a laptop and I’m going to attempt to use the command prompt and copy and paste to see if I can get the unlock code for my G7 optimo but on the Moto G power of 2021, I did have all of it unlocked but now since my dumbass locked the boot loader again I can’t get back on the initial platform and get developer tools. If I can get the OEM unlocking toggled back on I probably can unlock it reflash the firmware and boot my phone again
<EVERYONE>
Just to recap, my Motorola Moto G power 2021 is Bootloader locked after Magisk Installation failure. I have messed around with it and have it stuck in Fastboot Mode after it was stuck in bootloop. Some progress but the boot loader is locked again because of a error of mine and now it will not take my unlock code that I used before. Mind you, I did all of this between two android phones and an app called BUGAEGER That is available on Google play
I have a LG K7 that will boot to system, but no matter how many times I try, it wont boot into either download mode or recovery mode. I've tried the combos of vol down + power and vol up + power and every other combination I can think of. Pulled the battery and it didn't improve.
Anybody ever see something like this? Any suggestions on how to get it to work?
BigZ1 said:
I have a LG K7 that will boot to system, but no matter how many times I try, it wont boot into either download mode or recovery mode. I've tried the combos of vol down + power and vol up + power and every other combination I can think of. Pulled the battery and it didn't improve.
Anybody ever see something like this? Any suggestions on how to get it to work?
Click to expand...
Click to collapse
Tried ADB commands?
adb reboot recovery
adb reboot bootloader
bmwdroid said:
Tried ADB commands?
adb reboot recovery
adb reboot bootloader
Click to expand...
Click to collapse
Yes, and adb devices shows nothing. I'm wondering if the bootloader is locked and maybe that's why I'm having problems.
Also, I'm having problems getting TWRP to load. Do you know what version of TWRP will work with K7?
Do you have to root first before installing TWRP from the playstore?
BigZ1 said:
Yes, and adb devices shows nothing. I'm wondering if the bootloader is locked and maybe that's why I'm having problems.
Click to expand...
Click to collapse
If "adb devices" shows nothing imo it's not recognised so not possible to flash.
Tried other cable/port?
BigZ1 said:
Also, I'm having problems getting TWRP to load. Do you know what version of TWRP will work with K7?
Click to expand...
Click to collapse
No idea as I own a G5.
BigZ1 said:
Do you have to root first before installing TWRP from the playstore?
Click to expand...
Click to collapse
Never did that.
Always flashed directly but I guess so.
bmwdroid said:
If "adb devices" shows nothing imo it's not recognised so not possible to flash.
Tried other cable/port?
No idea as I own a G5.
Never did that.
Always flashed directly but I guess so.
Click to expand...
Click to collapse
tried another cable and different port. Status Quo!
Any other ideas/thoughts?
@BigZ1 sorry, none.
OK, finally can get into firmware mode and also recovery mode. Reason I needed this is to be able to try loading custom roms on this old phone. Now I'm on to the next pothole in the road.
I would like to install twrp. twrp from the playstore wont install unless you are rooted. I am using stock rom android 5 unrooted. I've looked at all the options and from what I see, I have the classic chicken and the egg dilema. Can't flash until my OS is rooted, and cant root without flashing.
The only way out is to use adb to flash the twrp file. Unfortunately I can't get adb devices command to acknowledge any devices. I have usb debugging on, and by connecting to a windows computer, I can view internal storage. So the device is communicating, but not via adb commands.
I tried to use the LGUP tool from LG, but it wont let me select my device, It sees the correct model of phone on Com3, but wont let me select the model. I think it's because LG has turned off their servers and cast us adrift.
If anybody has any ideas, it would be much appreciated.
I think my best bet is to get adb devices to work, or find a way to root my OS. I just cant figure out how to make that work. Help, please!!!!
BTW, in the stock recovry mode, LG has removed everything useful (e.g. install zip, reboot options, wipe cache, etc.) so the only option there is factory data reset. Thanks a lot LG!!!!!
BigZ1 said:
....The only way out is to use adb to flash the twrp file........
Click to expand...
Click to collapse
Sorry to tell you but afaik this won't work.
fastboot flash recovery <filename.img> would be the command but this will only work if it's unlocked.
BigZ1 said:
....Unfortunately I can't get adb devices command to acknowledge any devices. ......
Click to expand...
Click to collapse
I doubt that fastboot will work if adb isn't but it's worth a try.
You are right, a fastboot command would do it. Only reason I mentioned adb devices, is that if adb can't see the devices, fastboot wont either. I'll try it again, but so far no luck.
What I don't understand is why usb debugging lets me look at the internal files, but adb devices doesn't work. Perhaps you are right, the bootloader may be locked. Only thing I could find about that is in developer options I turned on OEM unlock.
Is there any other way to unlock the bootloader?
Sure wish I could get some of the LG tools working. They might enable flashing of twrp recovery or one of the various zip files that would root my OS.
Any more ideas? I'm desperate enough to try most anything....
One more question. When you try to execute adb or fastboot commands, should you be in what LG calls "firmware download" mode? Seems to me that when I did adb or fastboot commands on other vendors phones, I was able to do so while the OS was running.
Grasping for straws....
Well, it looks like you are right. There is a fastboot command
fastboot oem unlock
that would unlock the bootloader. Unfortunately while it's locked, I can't get fastboot to recognize any devices, so I can't unlock it.
Is there any way around this?
BigZ1 said:
Well, it looks like you are right. There is a fastboot command
fastboot oem unlock
that would unlock the bootloader. Unfortunately while it's locked, I can't get fastboot to recognize any devices, so I can't unlock it.
Is there any way around this?
Click to expand...
Click to collapse
Fastboot is afaik only working in download/bootloader mode.
ADB working on any other.
So <adb reboot bootloader > usually gets you there (but adb doesn't work) or switch to it manually.
Idk if you need to flash an unlock.bin by LG.
Got it before 31.12.21 for my G5.
bmwdroid said:
Fastboot is afaik only working in download/bootloader mode.
ADB working on any other.
So <adb reboot bootloader > usually gets you there (but adb doesn't work) or switch to it manually.
Idk if you need to flash an unlock.bin by LG.
Got it before 31.12.21 for my G5.
Click to expand...
Click to collapse
Yeah, I just discovered that LG discontinued support on Dec 31, 2021. So, looks like I'm out of luck for getting anything from them.
My only hope is that someone has that lockbin file and would share it. Sure wish LG hadn't left me high and dry.
Now that LG support is gone, is there any forum that might have some kind of workaround for the bootloader?
anybody got a lockbin file for K7????
BigZ1 said:
Yeah, I just discovered that LG discontinued support on Dec 31, 2021. So, looks like I'm out of luck for getting anything from them.
My only hope is that someone has that lockbin file and would share it. Sure wish LG hadn't left me high and dry.
Now that LG support is gone, is there any forum that might have some kind of workaround for the bootloader?
anybody got a lockbin file for K7????
Click to expand...
Click to collapse
Oh yeah, one more thing. The phone is still of some use to me, if I can find a way to root it. So far all the stuff I tried (kingoroot, supersu, magisk) have failed.
Anybody got any suggestions???
BigZ1 said:
Yeah, I just discovered that LG discontinued support on Dec 31, 2021. So, looks like I'm out of luck for getting anything from them.
My only hope is that someone has that lockbin file and would share it. Sure wish LG hadn't left me high and dry.
Now that LG support is gone, is there any forum that might have some kind of workaround for the bootloader?
anybody got a lockbin file for K7????
Click to expand...
Click to collapse
The file got generated by LG after I entered a long code on their developers site which is afaik different for each device.
So someone elses unlock.bin might even harm your device.
You may be right, but at this point I don't have much to lose.
One thing I would like to do with the K7, is get it rooted. I can move files to the internal storage with usb debugging. I can't install any zip files and that makes it really difficult to find anything that can root it. Thanks again to LG for reducing the recovery menu to "factory reset data" so the phone has almost nothing useful.
If you can figure out a way that I can install zip files, please let me know.
I can't find anything that will let me flash the device without root, and I can;t get to root without some tools in the recovery menu.
Thanks
OK, I have not found a way to root. So I thought I'd take one last look at flashing/upating the firmware. I found a .kdz and a .tot file that I'd like to try. At this point I'm not risking much because the phone isn't worth much to me as is.
So, if you had a .kdz and .tot file to try out, what app would you use to flash it to the K7?
I tried to get LGUP to work and LG flash tool, but cant seem to make them work. If I knew what one to use, it would narrow my search. I'm trying to flash the K7 firmware by running exe files (LG UP, LG flash tool) on Windows 10.
What do you guys use?
BigZ1 said:
OK, I have not found a way to root. So I thought I'd take one last look at flashing/upating the firmware. I found a .kdz and a .tot file that I'd like to try. At this point I'm not risking much because the phone isn't worth much to me as is.
So, if you had a .kdz and .tot file to try out, what app would you use to flash it to the K7?
I tried to get LGUP to work and LG flash tool, but cant seem to make them work. If I knew what one to use, it would narrow my search. I'm trying to flash the K7 firmware by running exe files (LG UP, LG flash tool) on Windows 10.
What do you guys use?
Click to expand...
Click to collapse
So, I managed to find a patched version of LG flash tool (2.0.1.6) on this website (thanks to member ieatacid), that doesn't give me errors immediately after I open it. The first thing I notice is that it doesn't appear to recognize the K7. If I try checking the box for manual mode and adding the file I want to flash, the click start, it tells me to "select model dll file". This is probably a result of flash tool not recognizing the phone. Anyway, where am I supposed to find this .dll file? I've searched everywhere and came up empty handed.
Can anybody give me some enlightenment on what I am doing wrong? Any help at all will be much appreciated.
Is there a tutorial on use of the flash tool? I looked but haven't found it yet. Just some youtube videos that are terse and lacking in detail.
Thanks!
BigZ1 said:
So, I managed to find a patched version of LG flash tool (2.0.1.6) on this website (thanks to member ieatacid), that doesn't give me errors immediately after I open it. The first thing I notice is that it doesn't appear to recognize the K7. If I try checking the box for manual mode and adding the file I want to flash, the click start, it tells me to "select model dll file". This is probably a result of flash tool not recognizing the phone. Anyway, where am I supposed to find this .dll file? I've searched everywhere and came up empty handed.
Can anybody give me some enlightenment on what I am doing wrong? Any help at all will be much appreciated.
Is there a tutorial on use of the flash tool? I looked but haven't found it yet. Just some youtube videos that are terse and lacking in detail.
Thanks!
Click to expand...
Click to collapse
I don't know why I didn't think of this earlier. I own 3 LG phones (LGMS300m1, LM-X210ULMG10r. VS500PP9). I tried all 3 with LGUP tool. The tool recognized 2 of the 3, and failed to ID the LGMS300 (K7). Anybody got any ideas why the tool would recognize some but not others?
I am the only owner of the two phones that LGUP would ID. I guarantee that the bootloader on them was never touched (unlocked or locked, in any way). So that's not the answer.
It would be a big improvement for me, if I could at least get the LGUP tool to work for the K7.
BTW, I tried all 3 phones on the 2016 version of LG Flash Tool. All 3 failed to be identified.
Please, if anybody has a hypothesis for the odd behavior of the LGUP tool, I would love to hear it. Any suggestions are welcome.
BigZ1 said:
I don't know why I didn't think of this earlier. I own 3 LG phones (LGMS300m1, LM-X210ULMG10r. VS500PP9). I tried all 3 with LGUP tool. The tool recognized 2 of the 3, and failed to ID the LGMS300 (K7). Anybody got any ideas why the tool would recognize some but not others?
I am the only owner of the two phones that LGUP would ID. I guarantee that the bootloader on them was never touched (unlocked or locked, in any way). So that's not the answer.
It would be a big improvement for me, if I could at least get the LGUP tool to work for the K7.
BTW, I tried all 3 phones on the 2016 version of LG Flash Tool. All 3 failed to be identified.
Please, if anybody has a hypothesis for the odd behavior of the LGUP tool, I would love to hear it. Any suggestions are welcome.
Click to expand...
Click to collapse
Update on the never ending saga!
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). I was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes i'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Words of wisdom, anyone?