LG K7 MS330 wont boot into download or recovery mode. Any suggestions? - LG K7 Questions & Answers

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?

Related

LG L9 (769 Model) Black Screen Bricked (I've read a lot!)

Hey all,
So I successfully rooted my phone, and then I was going to go into recovery reboot mode to install a downloaded rom. I'm not sure what did it, but on that restart I got LG Security error. I first attempted on three different computers to do LG Mobile Support Tool. It stopped everytime when it was going to begin downloading the files. I'm pretty sure if I still had the Security Error image, I would be fine, because I now know of ways to bypass the LG Support Tool, and edit the host file, and then get it downloading.
Either way, in my research after no success with LG Mobile Support Tool, I came across Fastboot. So I got fastboot, I got the drivers installed, but I'm pretty sure my problem was, on the command prompt screen when Fastboot asks' you questions I said yes on them. I believe this is what caused my phone to have the black screen. It will not go into S/W upgrade mode now. It will not do anything, just black screen. I found a tutorial over on Android Forums, and with using Fastboot, I was able to sucessfully flash "p4_769.img" According to that tutorial, after doing that I should have a dead android guy logo, and then just be able to hard reset... but that didn't change anything. Still have the black screen. Still won't go into S/W Upgrade mode.
Now according to what I've read, the next step would be to flash KDZ Afresh...I've looked for this, whatever it is, specific to my model phone, but I can't find anything. If anyone else has any ideas, I would love to hear. I'm so frustrated at this point. Very much appreciate any help. Thank you.
It sounds like now what I have to do is, using how I flashed that recovery img, I first should flash the x and uboot.bin files to my phone. Then I will be able to get into S/W mode, and then restore from there. I just have to find these bin files. I don't have a friend or anyone nearby with the same phone as mine that can:
adb shell su -c busybox dd if=/dev/block/mmcblk0p2 of=/sdcard/external_sd/p2.bin
with theres.
Hi dlipford370, you could try this http://forum.xda-developers.com/showthread.php?p=51206080
Cheers. Good luck.
Sent from my LG P76020L-EUR-XX unlocked and rooted

[Q] Impossible Rooting Polaroid PSPR355

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.

LG Tribute HD (LS 676) root?

Hi,
Just wondering if anyone was working on root access for the popular Black Friday LG Tribute HD phone? It was $20 dollars and must've sold like hotcakes!
Apparently, it also supports some GSM bands like it's fellow low cost predecessor LG Tribute 5 which can be SIM unlock with a build.prop edit.
Android_JT said:
Hi,
Just wondering if anyone was working on root access for the popular Black Friday LG Tribute HD phone? It was $20 dollars and must've sold like hotcakes!
Apparently, it also supports some GSM bands like it's fellow low cost predecessor LG Tribute 5 which can be SIM unlock with a build.prop edit.
Click to expand...
Click to collapse
I am wondering the same, will there be any development for this type of phone?
How much would it cost for someone to do development work for the phone, I would be willing to donate some.
few peoples wait for root
I did a system dump this morning and I am working on it as we speak =) The hardest problem I am facing is determining which partition recovery is stock. What is the closest phone to this, anybody know?
Sands207 said:
I did a system dump this morning and I am working on it as we speak =) The hardest problem I am facing is determining which partition recovery is stock. What is the closest phone to this, anybody know?
Click to expand...
Click to collapse
How did you do a system dump
Sent from my H1611 using XDA-Developers mobile app
903tex said:
How did you do a system dump
Sent from my H1611 using XDA-Developers mobile app
Click to expand...
Click to collapse
I am using BBQlinux so I have all of my android tools set up all ready, including adb. Anyway once in terminal enter
Code:
adb devices
and then
Code:
adb pull /system systemdump
Just throwing it out there but as anyone tried
Code:
fastboot oem unlock
after enabling it in developer settings and then try the various root exploits? I keep feeling like this is something worth investigating
Sands207 said:
I did a system dump this morning and I am working on it as we speak =) The hardest problem I am facing is determining which partition recovery is stock. What is the closest phone to this, anybody know?
Click to expand...
Click to collapse
lg x style
---------- Post added at 05:50 PM ---------- Previous post was at 05:48 PM ----------
I am also waiting for root. Nice phone but useless without root.
Sands207 said:
Just throwing it out there but as anyone tried after enabling it in developer settings and then try the various root exploits? I keep feeling like this is something worth investigating
Click to expand...
Click to collapse
I've tried 5+ different exploits and nothing seems to work. I wish LG would add this phone as one of the unlockable ones on their developer website
ncs1263 said:
I've tried 5+ different exploits and nothing seems to work. I wish LG would add this phone as one of the unlockable ones on their developer website
Click to expand...
Click to collapse
I do too. Even the xda app detects this phone as LG X style I have the backup from earlier I wish I knew to at least gain temp root long enough to push busybox and extract either recovery.img or boot.img at least then maybe we could bump unlock the recovery for permanent root...Should I upload the system backup so at least we have that? That way people can try what ever they can with the files for future use since LG is silent and we are not very organized yet but I have a dev machine at the ready if we can achieve root pm me if you are interested in the files :good:
Sands207 said:
Just throwing it out there but as anyone tried
Code:
fastboot oem unlock
after enabling it in developer settings and then try the various root exploits? I keep feeling like this is something worth investigating
Click to expand...
Click to collapse
I couldn't even get to fastboot. Playing around I was able to get into LG download mode (Vol up + power), but no fastboot access.
Android Recovery
Ok, so just wanted to update. This morning I decided to take a similar course that we took to unlock the LG Volt... Baby steps Making sure you have adb+fastboot installed (pdaNET does this for you on install) open a folder of your choice (WINDOWS) and right click and select open A command line here and with my phone plugged in booted to normal android and enter
Code:
adb devices
and then hit enter and once your phone is recognized by adb enter
Code:
adb reboot recovery
At that point you will see a dead android on the screen don't worry! Just unplug your phone and then and I mean briefly press volume down and let go quickly and you will be greeted by android recovery. Now that we can see stock recovery we are heading in the right direction!!
Sands207 said:
Ok, so just wanted to update. This morning I decided to take a similar course that we took to unlock the LG Volt... Baby steps Making sure you have adb+fastboot installed (pdaNET does this for you on install) open a folder of your choice (WINDOWS) and right click and select open A command line here and with my phone plugged in booted to normal android and enter
Code:
adb devices
and then hit enter and once your phone is recognized by adb enter
Code:
adb reboot recovery
At that point you will see a dead android on the screen don't worry! Just unplug your phone and then and I mean briefly press volume down and let go quickly and you will be greeted by android recovery. Now that we can see stock recovery we are heading in the right direction!!
Click to expand...
Click to collapse
Thanks for that tip, I got the dead android,l freaked, and the device rebooted.
We appreciate your help!
As far as fastboot goes which we NEED too guys to issue the fastboot unlock command.. the obstacle im seeing is we need a way to zero out the current Laf partition which right now is download mode and if it can be zeroed we can finally access fastboot because download mode is placed there by LG to make this harder for us. Adb is recognized but the fastboot reboot command just spits me back into android. And I need to be root to zero AND finally pull the recovery because I think we might be able to use the twrp build for the Style X.. because it's the dd command being used here even if it's a temp root lol would make all the difference. I haven't had an LG phone in a few years so I'm kind of stumped. Put the word out we might need a root bounty ???
Sent from my LGLS676 using Tapatalk
Sands207 said:
As far as fastboot goes which we NEED too guys to issue the fastboot unlock command.. the obstacle im seeing is we need a way to zero out the current Laf partition which right now is download mode and if it can be zeroed we can finally access fastboot because download mode is placed there by LG to make this harder for us. Adb is recognized but the fastboot reboot command just spits me back into android. And I need to be root to zero AND finally pull the recovery because I think we might be able to use the twrp build for the Style X.. because it's the dd command being used here even if it's a temp root lol would make all the difference. I haven't had an LG phone in a few years so I'm kind of stumped. Put the word out we might need a root bounty ???
Sent from my LGLS676 using Tapatalk
Click to expand...
Click to collapse
LG doesnt typically provide access to fastboot (not without wiping laf that is), even then fastboot oem unlock is not generally supported
jcase said:
LG doesnt typically provide access to fastboot (not without wiping laf that is), even then fastboot oem unlock is not generally supported
Click to expand...
Click to collapse
It was just a thought
Just wanted to say I really appreciate that there are people who are working on this.
I just bought this today for $15, any progress?
Enable OEM unlock is available under developer settings and data profile settings are in opened by ##3282#
demonaxe said:
Enable OEM unlock is available under developer settings and data profile settings are in opened by ##3282#
Click to expand...
Click to collapse
Is there sim unlock?

Question HARD Bricked Moto G power (2021) XT2117-4 / Blankflash, Flash file, or emmc_prog_firehose request.

Requesting someone's backup of emmc so I can unbrick my XT2117-4 Retail(Retus) Moto G power 2021. Stuck in Qusb-HS Dloader 9008 mode after setting active slot to b with nothing on slot b in fastboot. If I could atleast somehow swap back to slot_a I feel like that would work but I don't think that's really a possibility in edl. Mainly the GPT also would be helpful. Motorola/borneo_retail/borneo:10/QZBS30.Q4-43-35-2/f8e93:user/test-keys is the build I was on at the time. My phone is hard bricked not soft bricked. There is no fastboot mode only edl mode with Qcom HS-USB 9008. I believe It got bricked by me switching to slot_b in fastboot mode with nothing on slot_b not even bootloader. Also my bootloader is unlocked and it was rooted with magisk at the Time of hard brick. I believe fastboot set_active_slot b was the command that bricked it or what ever the correct usage of the set active command was if that's not exactly it. I just need the emmc_prog_firehose for SM_KAMORTA_H or SDM662 or SM6115. Whatever the proper name out of those it would be I guess for this phones type.
Can't use LSMA since it's hard bricked it doesn't even recognize anything is plugged in. I need a blankflash file to use with qboot or the emmc_programmer and then use QFIL or QPST possibly. I use Linux and Windows both if that helps at all somehow.
More info from a reply of mine.
REPLY:
"No it specifically warned that there was nothing on b and it was dangerous but I wasn't paying much attention to it because I was watching family guy so I told it to go ahead and switch. Insta brick after that decision. It does warn you though or it did with me on my phone. Whenever you've done it your slot probably wasn't really "empty" in the sense it didn't have a bootloader on it. You can't boot up a phone that's on a slot without even a bootloader on it otherwise you'll literally have nothing to load your boot image in the first place which means no recovery or fastboot either for A/B devices hence you then have a hard bricked phone in emergency download mode afterwards that either needs reprogrammed or deep flashed (If there's really a difference I don't know). I think you still need a firehose_emmc_programmer or Blank-flash file which has a programmer in it to do that though which is what I need. Some phones might have different emergency protocols for that situation or maybe it's been updated since to where it prevents A/B phones from getting stuck in limbo on an empty slot but the XT2117-4 Moto G Power 2021 doesn't it just warns or atleast when I bricked mine. It's nice to have the option for developer and testing purposes probably or just as a way to get into EDL Mode. I just wasn't paying as much attention as I should have been while tweaking my phone. I'm not a developer or expert though so someone correct me if I'm mistaken somewhere but I have atleast an alright understanding of what's going on I hope from my experience with rooting/rooted phones. A/B partitioning is still kind of a weird newer thing to me since I haven't done much after bricking my G Power and I was used to System As Root before that."
snuffinaround said:
Requesting someone's backup of emmc so I can unbrick my XT2117-4 Retail(Retus) Moto G power 2021. Stuck in Qusb-HS Dloader 9008 mode after setting active slot to b with nothing on slot b in fastboot. If I could atleast somehow swap back to slot_a I feel like that would work but I don't think that's really a possibility in edl. Mainly the GPT also would be helpful. Motorola/borneo_retail/borneo:10/QZBS30.Q4-43-35-2/f8e93:user/test-keys is the build I was on at the time.
Click to expand...
Click to collapse
Did you by any chance track down anything or solve this? Mine is currently soft bricked also.,,bootloader locked and will only boot to fastboot. any help would be great!
HazyBoneX said:
Did you by any chance track down anything or solve this? Mine is currently soft bricked also.,,bootloader locked and will only boot to fastboot. any help would be great!
Click to expand...
Click to collapse
You already tried LMSA?
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
sd_shadow said:
You already tried LMSA?
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
Yes every time it says fastboot flash single partition failed
Hello guys. I have this device and I'll help you. Mine's not rooted yet which is why I came to ask a question and accidentally clicked this thread. Tell me what I need to do to get what you need and I'll do it. i don't know how to use a mouse in TWRP and it sounds like that's what you need. I have a wireless mouse with a usb dongle but no type-c otg at the moment. I just found out from another post in here about using twrp from a terminal. I need to learn more about that too. Dude made a kernel backup with an adb twrp command. I asked him about it but have gotten no response.I also only run linux, but may install a windows 11 virtual machine to use LMSA since every lolinet kernel I've rooted so far results in no touch response.
Have you guys tried fastboot flashing the entire lolinet firmware? I just made a tutorial on it. I've never had a problem that wouldn't fix and I have quite a bit of experience....
Fastboot Flash Firmware Commands (borneo)
I made this list because I needed it and didn't see one around here. If anyone can use it, here it is with a link to the firmware. Taylor made for the XT2117 Moto G Power 2021 (borneo). https://mirrors.lolinet.com/firmware/moto/borneo/...
forum.xda-developers.com
I'd bet that would fix it. It re-writes all partitions.
arkansawdave74 said:
Hello guys. I have this device and I'll help you. Mine's not rooted yet which is why I came to ask a question and accidentally clicked this thread. Tell me what I need to do to get what you need and I'll do it. i don't know how to use a mouse in TWRP and it sounds like that's what you need. I have a wireless mouse with a usb dongle but no type-c otg at the moment. I just found out from another post in here about using twrp from a terminal. I need to learn more about that too. Dude made a kernel backup with an adb twrp command. I asked him about it but have gotten no response.I also only run linux, but may install a windows 11 virtual machine to use LMSA since every lolinet kernel I've rooted so far results in no touch response.
Have you guys tried fastboot flashing the entire lolinet firmware? I just made a tutorial on it. I've never had a problem that wouldn't fix and I have quite a bit of experience....
Fastboot Flash Firmware Commands (borneo)
I made this list because I needed it and didn't see one around here. If anyone can use it, here it is with a link to the firmware. Taylor made for the XT2117 Moto G Power 2021 (borneo). https://mirrors.lolinet.com/firmware/moto/borneo/...
forum.xda-developers.com
Click to expand...
Click to collapse
If you If you could pull a total nandroid backup i think that should be what i need to restore my phone if any one could chime in it would be greatly qpp
Yes I have tried that. Check out command line android backup twrp.
HazyBoneX said:
If you If you could pull a total nandroid backup i think that should be what i need to restore my phone if any one could chime in it would be greatly qpp
Click to expand...
Click to collapse
Ok. I have a question as I've never used a mouse with my phone before. Are you guys using a mouse through OTG to use im TWRP? To help you any time soon I'll have to find info for using TWRP with ADB commands as I don't think I have the hardware to use my mouse.
Edit: I found information faster than I thought I would. I looked it up in the past and could find nothing but it's a new feature.
HazyBoneX said:
If you If you could pull a total nandroid backup i think that should be what i need to restore my phone if any one could chime in it would be greatly qpp
Click to expand...
Click to collapse
Okay, that would require me to factory reset because I won't send a backup of my logged in system. I would do that if I thought it would help, but it won't. I don't thiink amyone has beennable to restore a stock nandroid on these auto-encrypting motos. If I''m wrong, and I may be, show me. I've tried many times and many ways. I have been able to restore custom backups, but never stock.
arkansawdave74 said:
Okay, that would require me to factory reset because I won't send a backup of my logged in system. I would do that if I thought it would help, but it won't. I don't thiink amyone has been able to restore a stock nandroid on these auto-encrypting motos. If I''m wrong, and I may be, show me. I've tried many times and many ways.
Click to expand...
Click to collapse
I I'm not really sure I can't get any files to flash on it I can get TWRP to load I can't get the Motorola restore program to flash anything so I'm literally just stuck in fast food with a locked bootloader and non-rooted and no developer options turned on any help would be appreciated
HazyBoneX said:
I I'm not really sure I can't get any files to flash on it I can get TWRP to load I can't get the Motorola restore program to flash anything so I'm literally just stuck in fast food with a locked bootloader and non-rooted and no developer options turned on any help would be appreciated
Click to expand...
Click to collapse
I feel your pain. You have tried the obvious
fastboot set_active a
of course? I'm not trying to be a smartass. You just may have switched slots with twrp and don't know the fastboot command.
arkansawdave74 said:
I feel your pain. You have tried the obvious
fastboot set_active a
of course? I'm not trying to be a smartass. You just may have switched slots with twrp and don't know the fastboot command.
Click to expand...
Click to collapse
Fastboot set_active a retutns....
Setting current slot to 'a'...
FAILED REMOTE FAILURR
HazyBoneX said:
Fastboot set_active a retutns....
Setting current slot to 'a'...
FAILED REMOTE FAILURR
Click to expand...
Click to collapse
Ok. How was it that you switched slots and got stuck? I want to experiment but I don't want to make the same mistake.
Also, if your bootloader is locked, aren't you still under warranty? Can you make a warranty claim?
If not, you may be able to unlock it in your current state which might make fixing it easier. You could try
fastboot oem get_unlock_data
and if it returns some lines of code you can likely unlock it now.
With a locked bootloader you are very limited and my twrp backup of a RETUS would have had no chance at all of helping you unless you happen to have a factory unlocked US variant.
I had it rooted and the bootloader unlocked...then i tried to follow a flash back to stock and re lock boot loader guide....but now when it boots it says no valid os or i can go into fastboot and thats about it....
HazyBoneX said:
I had it rooted and the bootloader unlocked...then i tried to follow a flash back to stock and re lock boot loader guide....but now when it boots it says no valid os or i can go into fastboot and thats about it....
Click to expand...
Click to collapse
Have you tried to unlock it again with the same code? I have never even tried to relock a bootloader. I may have nightmares. If you still have the unlock email I would try that.
arkansawdave74 said:
Have you tried to unlock it again with the same code? I have never even tried to relock a bootloader. I may have nightmares. If you still have the unlock email I would try that.
Click to expand...
Click to collapse
I have tried that also and developer options are not on so i cant
So sorry. If i think of anything else I'll let you know. I think relocking your bootloader with an altered kernel was a bad idea, but I think relocking your bootloader is a bad idea anytime.
My phone is hard bricked not soft bricked. There is no fastboot mode only edl mode with Qcom HS-USB 9008. honestly a mmcblk0 backup would definitely help if anyone would want to backup and then pm me a link or something. I believe It got bricked by me switching to slot_b in fastboot mode with nothing on slot_b not even bootloader. Also my bootloader is unlocked and it was rooted with magisk at the Time of hard brick
snuffinaround said:
Requesting someone's backup of emmc so I can unbrick my XT2117-4 Retail(Retus) Moto G power 2021. Stuck in Qusb-HS Dloader 9008 mode after setting active slot to b with nothing on slot b in fastboot. If I could atleast somehow swap back to slot_a I feel like that would work but I don't think that's really a possibility in edl. Mainly the GPT also would be helpful. Motorola/borneo_retail/borneo:10/QZBS30.Q4-43-35-2/f8e93:user/test-keys is the build I was on at the time.
Click to expand...
Click to collapse
My phone is hard bricked not soft bricked. There is no fastboot mode only edl mode with Qcom HS-USB 9008. honestly a mmcblk0 backup would definitely help if anyone would want to backup and then pm me a link or something. I believe It got bricked by me switching to slot_b in fastboot mode with nothing on slot_b not even bootloader. Also my bootloader is unlocked and it was rooted with magisk at the Time of hard brick
sd_shadow said:
You already tried LMSA?
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
LSMA won't work because my phone won't turn on its stuck in emergency download mode and so LSMA doesn't even detect device

Question I need help please…

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

Categories

Resources