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
Related
I hope this is useful information. It took me a bit to figure it out due to a lot of conflicting information, since the procedure has changed, perhaps several times, since the first version of Android. Also, I'll probably forget myself.
Please note that I've performed these steps on Linux (Specifically Arch Linux). Others have pointed out that if you have issues executing step 7 from Windows, you may need to follow this post.
1. Install Android Studio, or otherwise obtain the latest versions of the adb and fastboot programs. I think Windows users also need to install a USB driver, but I run Linux, so I am not sure about that procedure.
2. Gain access to the developer options on the tablet. Go to the settings, and find the "about tablet" section. Scroll down to the "Software version" section and tap on that several times until it says that you are now a developer. Feel special.
3. Go to the new "Developer options" setting. Select "OEM unlocking." Also, I selected "USB debugging" as a straightforward way to reboot into the boot loader.
4. Connect to the computer on which you've installed adb and fastboot.
5. Type 'adb devices' to see your device listed. The tablet will ask you if you're sure you want to allow the computer access to it. Answer in the affirmative, and save that option.
6. Type 'adb reboot-bootloader' to do just that.
7. After you see the innards of your 'droid, type 'fastboot flashing unlock' . On Linux, you may need root permissions to do this. The tablet will ask you to confirm (select with up/down volume, and accept with the power button), and will then erase all of your data! I didn't worry about this as I'm all on Google services, and so they can be restored easily enough.
Huhu
and where is that for? What can I do after the bootloader is unlocked? Is there any alternative bootloader that I can use then?
Huhu
and where is that for? What can I do after the bootloader is unlocked? Is there any alternative bootloader that I can use then?
Click to expand...
Click to collapse
you are then able to flash another (custom) recovery, which would let you install unsigned zip-files, e.g. in order to get root.
Unfortunately, there is no recovery port by now.
I don't know if one could use the source code on Lenovo's website to port one, if not we would probably need an image dump directly from the device (if I'm not mistaken you need root to dump the recovery image).
I really would like to have root, but it still seems far away unless there's an experienced developer somewhere who owns the device.
I've already thought of starting a bounty thread...maybe enough people are willing to contribute so that developers might feel attracted.
Hello,
Do you think it would be possible to install Windows 10 on our android yoga book?
Thanks,
I faced with one question , when I typed the 'fastboot flashing unlock ', there was nothing occurred except the innards of driod :crying,and I also selected the oem unlocking
(All right, I solved it )
AndyVerne said:
I faced with one question , when I typed the 'fastboot flashing unlock ', there was nothing occurred except the innards of driod :crying,and I also selected the oem unlocking
(All right, I solved it )
Click to expand...
Click to collapse
can you tell me how to deal with it? I met the same problem.
Vsplorer said:
can you tell me how to deal with it? I met the same problem.
Click to expand...
Click to collapse
I used one exe for adb and fastboot which is written by others, and every thing went perfectly.
AndyVerne said:
I used one exe for adb and fastboot which is written by others, and every thing went perfectly.
Click to expand...
Click to collapse
can you tell me where to download the exe？ thanks a lot！
Vsplorer said:
can you tell me where to download the exe？ thanks a lot！
Click to expand...
Click to collapse
Here is the link of the exe, hope it will be helpful
https://forum.xda-developers.com/showthread.php?t=2588979
AndyVerne said:
Here is the link of the exe, hope it will be helpful
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
thanks！
Missing Something?
I tried to follow the instructions above, but I might be missing something. After typing in 'adb reboot-bootloader' the Yoga Book reboots into a screen that says 'FASTBOOT MODE.' But when I type 'fastboot flashing unlock' it just says '< waiting for device >' and nothing ends up happening. What am I doing wrong?
jasonccheng said:
I tried to follow the instructions above, but I might be missing something. After typing in 'adb reboot-bootloader' the Yoga Book reboots into a screen that says 'FASTBOOT MODE.' But when I type 'fastboot flashing unlock' it just says '< waiting for device >' and nothing ends up happening. What am I doing wrong?
Click to expand...
Click to collapse
See this post:
https://forum.xda-developers.com/yoga-book/help/missing-usb-driver-cherry-trail-tablet-t3537008
Same here with Linux... The adb devices command shows the device but the flash command ends in 'waiting for device' and thats it. Damn
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
carepack said:
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
Click to expand...
Click to collapse
It's the price you pay for unlocking the bootloader. Affects many lower end devices, presumably using Intel chips. There is a solution for several devices - check around XDA - but I have not been able to get it to work with the YB.
For what it's worth, I would suggest those tempted to unlock the device and root it to check that you will be able to do what you want to do. Even rooted, I have found it impossible to get rid of the junk apps, so the whole exercise for me has been a waste of time. I'm waiting now to see if Lenovo will release the stock firmware. Until then, the YB is back in its box and I am a bit older and a bit wiser. Lenovo is junk.
carepack said:
I relocked the bootloader, sinct then I got following message at the boot screen: bootloader error 01, please contact support.
After that the device is booting android properly. Anybody else experienced this and know how to get rid of the message?
Thx.
Click to expand...
Click to collapse
i believe, this is due to android's security feature 'verified boot'. it warns that the system was somehow altered and can't be trusted - in other words that it is not an oem stock rom any more.
you might be able to get rid of it by flashing a complete stock rom, but i'm not sure.
zamzenos said:
It's the price you pay for unlocking the bootloader. Affects many lower end devices, presumably using Intel chips. There is a solution for several devices - check around XDA - but I have not been able to get it to work with the YB.
For what it's worth, I would suggest those tempted to unlock the device and root it to check that you will be able to do what you want to do. Even rooted, I have found it impossible to get rid of the junk apps, so the whole exercise for me has been a waste of time. I'm waiting now to see if Lenovo will release the stock firmware. Until then, the YB is back in its box and I am a bit older and a bit wiser. Lenovo is junk.
Click to expand...
Click to collapse
firstly, it has nothing to do with intel or lenovo or low end devices, because secure boot or verified boot is part of android - it is nothing more than a security feature to show whether system integrity (as provided by the vendor) is still valid.
secondly, why is Lenovo junk just because you are not able to get things done? i don't get it. i've already told you that it is possible to get rid of system apps, just use the right tools... e.g. 'Sytstem App Entferner' which definitely works. also i helped you to get your twrp backup working and i was also able to use the newest magisk root (v10.2) immediately, which you said was not possible. so i guess you shouldn't blame others for your shortcomings. the yb might surely have it flaws, bur no more or less than devices of other manufacturers.
danjac said:
i believe, this is due to android's security feature 'verified boot'. it warns that the system was somehow altered and can't be trusted - in other words that it is not an oem stock rom any more.
you might be able to get rid of it by flashing a complete stock rom, but i'm not sure.
firstly, it has nothing to do with intel or lenovo or low end devices, because secure boot or verified boot is part of android - it is nothing more than a security feature to show whether system integrity (as provided by the vendor) is still valid.
secondly, why is Lenovo junk just because you are not able to get things done? i don't get it. i've already told you that it is possible to get rid of system apps, just use the right tools... e.g. 'Sytstem App Entferner' which definitely works. also i helped you to get your twrp backup working and i was also able to use the newest magisk root (v10.2) immediately, which you said was not possible. so i guess you shouldn't blame others for your shortcomings. the yb might surely have it flaws, bur no more or less than devices of other manufacturers.
Click to expand...
Click to collapse
Let me start at the top:
1. My comments on Lenovo are no reflection on the useful tools you have provided us here, for which I have thanked you more than once. So no need to be defensive on that score.
2. If the unlock warning had its source in Android itself, we could expect the warning to bear its logo. I assume it bears the Intel logo because Intel is the author of it. In itself, this is of no importance. What is profoundly irritating is the fact that the security warning is followed by a completely unjustfied 5 second suspension. This is a penalty. Perhaps many do not mind this interference with their use of their devices, but I do. I'm not used to that kind of treatment and I don't take kindly to it.
3. My opinion of Lenovo has always been low, especially since their attempts some years ago to spike their devices with spyware. I regard Lenovo as an exploitative bottom feeder, supplying workaday gear and screwing their customers every way they can for an extra buck or two. I offered the YB to several of my friends. All turned their noses up at the mention of the manufacturer. Don't blame them.
4. If you do want to be of further assistance here, perhaps you can use your obvious technical skills and knowhow to work out how we can replace the Intel penalty with something more benign. I have tried, but can't find where the Intel warning is hidden.
I have downloaded and extracted the apk of the system app remover you mentioned. But until I can get rid of the Intel warning I won't bother to re-root the YB and test if it will clear the junk.
#carepack: at the moment, you must buy the stock firmware (and won't it be expensive!). All part of lenny's screw.
thx to all for youre response. my hope is that with next update the problem will solve by itself. We'll see. I were doin this ooi and was aware of things like that. So no drama for me.
@zamzenos
Buying the stock firmware? Could you provide more info about this?
carepack said:
thx to all for youre response. my hope is that with next update the problem will solve by itself. We'll see. I were doin this ooi and was aware of things like that. So no drama for me.
@zamzenos
Buying the stock firmware? Could you provide more info about this?
Click to expand...
Click to collapse
Yes, that could well do it. But will there be an update? There's a new 12" YB on offer. Could be our 10" version is history already. But we could then hope that they will release the stock.
Re buying the stock: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Yoga-Book-Firmware/td-p/3511903
zamzenos said:
Yes, that could well do it. But will there be an update? There's a new 12" YB on offer. Could be our 10" version is history already. But we could then hope that they will release the stock.
Re buying the stock: https://forums.lenovo.com/t5/Android-Yoga-Series-Tablets/Lenovo-Yoga-Book-Firmware/td-p/3511903
Click to expand...
Click to collapse
According to this:
http://www.androidpolice.com/2016/1...views-cite-software-issues-incredible-design/
We'll receive the nougat Update.
Greetings
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?
I'm might be in wrong place but im Looking for any info on g8 power lite variant of g8 power. UK unlocked regards retail. Looking like It is a oddball as I cannot find anything. I don't think there will be much support but if anybody knows if this similar enough to any other variant ?? Android pie out the box no update. Not even Moto app to enable one button navbar. Any help thanks
Hello
I just got the LATAM version of that same phone, and i can tell you that it's gonna take some time to get information, but it will appear in some time.
Indeed, this is the right place, but it seems to be that similar models have variants around the globe, and the Moto G8 Power Lite it's not a priority right now.
I'm waiting the same for my version (XT2055-2), but it's just a matter of patience.
Keep looking on the forum and eventually it will appear some information
Kiffo said:
Hello
I just got the LATAM version of that same phone, and i can tell you that it's gonna take some time to get information, but it will appear in some time.
Indeed, this is the right place, but it seems to be that similar models have variants around the globe, and the Moto G8 Power Lite it's not a priority right now.
I'm waiting the same for my version (XT2055-2), but it's just a matter of patience.
Keep looking on the forum and eventually it will appear some information
Click to expand...
Click to collapse
Yea I thought as much, motorola seems to be putting out lots of versions of every device. This is by far the worst device I have had in recent memory, seems be missing quite a bit of the usual options available on other recent moto devices. I would have a go at bits myself but it also seems my version of this device has a Chinese bootloader installed, I don't think I will still have this device by the time any work is done I need to change phones quite often for work. Good luck.
bukata said:
Yea I thought as much, motorola seems to be putting out lots of versions of every device. This is by far the worst device I have had in recent memory, seems be missing quite a bit of the usual options available on other recent moto devices. I would have a go at bits myself but it also seems my version of this device has a Chinese bootloader installed, I don't think I will still have this device by the time any work is done I need to change phones quite often for work. Good luck.
Click to expand...
Click to collapse
The chinese bootloader is something common on Motorola, even i have the same thing. But i guess they gonna come up with something. As per today, the Brazil version of this smartphone started getting Android 10 (with some bugs tho) so i guess Motorola gonna start moving things in the coming weeks
Hi, I've got g8 power lite and would like some modding but how can I recon which version have I got?
islandman75 said:
Hi, I've got g8 power lite and would like some modding but how can I recon which version have I got?
Click to expand...
Click to collapse
Go to Settings > About Phone > Model & hardware
and it will show you the Model, Serial number and Model(SKU) of the device. Ithing what you are after is the SKU.
Tip: Under the title "Model & Hardware" you should see "Model: moto g8 power lite" in a gray(er) font.
{This may vary between models and versions}
Hope this helps.
lennonhorrocks said:
Go to Settings > About Phone > Model & hardware
and it will show you the Model, Serial number and Model(SKU) of the device. Ithing what you are after is the SKU.
Tip: Under the title "Model & Hardware" you should see "Model: moto g8 power lite" in a gray(er) font.
{This may vary between models and versions}
Hope this helps.
Click to expand...
Click to collapse
found it, thank you. I've got XT2055-1
It's not possible to unlock the bootloader on the G8 power lite, only the G8/G8 power.
It cannot be done using fastboot but it is certainly possible using the Realtek VCOM USB protocol
Rooting Moto G8 Power Lite
Does anyone know where I can find a decent guide to rooting the G8 Power Lite (if one exists - I know it's only been out a few months)? I've had a Google around and looked on this forum and on reddit but I can't find anything. I haven't done...
forum.xda-developers.com
This video sums it up well
Essentially you need to:
1. download MTKCLIENT from github, works best on Linux IMHO but Windows works too - on Windows you need additional USB drivers and MTK Drivers, which i attached. Use PIP to install the requirements by going into the MTKCLIENT directory and typing into CMD/Terminal: python3 pip install -r requirements.txt
2. Copy the G8 power Lite specific script to the root folder of the MTKCLIENT
3. Open up the phone, remove the plastic covering the cameras and motherboard. Unplug the battery. Short these two pins either by soldering them together or just using something metal - this is only necessary during the flash and then should be removed.
View attachment 5889467
4. Plug in usb cable to the phone but dont connect it to the pc yet. Start the program either by CD-ing to the MTKCLIENT directory and running it via CLI (on Linux: python3 mtk w proinfo,seccfg proinfo.bin,seccfg.bin, If it wont unlock using the custom G8 script, just run this generic command: python mtk da seccfg unlock) or doubleclicking the desbloq_bootloader.bat on Windows. Then short the two pins, keep them shorted and connect the USB cable to the PC. You should see a bunch of code scroling, it will automatically close/end.
5. Unplug USB, remove short circuit from two pins, plug in battery, turn on phone, you should see lines of text during the boot like this:
View attachment 5889471
Bootloader unlocked. Now the only use is ROOT, no custom ROMs or Recoveries available as its vastly different from normal G8 power, which has a Snapdragon CPU and totally different screen. You'll also get a big "CARRIER INVALID" message on the home screen, so after you ROOT make sure to relock the bootloader using the same method but the command is python3 mtk da seccfg lock
I'm almost sure that what I got it's a - Moto g8 Power lite - XT2055-1
So I got the phone long ago and it's been mostly at home and used as a backup by some of my friends.. I can't even remember which person had it last time.
Thing is that I completely forgot about the Motorola protection and after factory reset it keeps on asking for the last used google account which I got no clue which one would be. To make things worst I have no way to find out the IMEI's so that I can use Motorola RSA.
It looks like to me that I can't enter BootRom mode and I can only access preloader mode even tho, I got access to recovery mode and meta mode. I have tried all the key combos I can imagine by now.
I have also tried sp flash tools but I'm getting an error when the process is starting.
I'll drop some more details soon.. thank you.
BadChoices said:
I'm almost sure that what I got it's a - Moto g8 Power lite - XT2055-2
So I got the phone long ago and it's been mostly at home and used as a backup by some of my friends.. I can't even remember which person had it last time.
Thing is that I completely forgot about the Motorola protection and after factory reset it keeps on asking for the last used google account which I got no clue which one would be. To make things worst I have no way to find out the IMEI's so that I can use Motorola RSA.
It looks like to me that I can't enter Boot mode and I can only access Preload mode even tho, I got access to recovery mode. I have tried all the key combos I can imagine.
I have also tried sp flash tools but I'm getting an error when the process is starting.
I'll drop some more details soon.. thank you.
Click to expand...
Click to collapse
have you tried using mtkclient? unlock the bootloader and then remove frp
aryanhington said:
have you tried using mtkclient? unlock the bootloader and then remove frp
Click to expand...
Click to collapse
I did before as far as I recall but I gave up on it I think 'cus I ran into some issues as well.. I'm a bit rusty when it comes to this kind of stuff.. now that I'm reading all again about the tools etc I'm gonna give mtkclient a go and keep you all posted. Thank you again.
First off some questions please.. and I'm running win 11 pro.
What am I suppose to see on the screen when on Brom mode ? or how do I know that I'm on that mode.. obviously that if I'm not the operations just fail.
cant run mtk_gui atm for some reason trying to clear that out.. 'C:\Users\Q\AppData\Local\Programs\Python\Python311\Lib\site-packages\shiboken6\libshiboken does not exist'
Also tried bypass_utility_v1.4.2 using dif. key combos always returns 'device in preloader mode, trying to crash..'
mtkclient handshake returns failed 'Preloader - [LIB]: status: handshake failed, retrying..'
I'll keep on trying to understand all this just need my time.. all help appreciated.
BadChoices said:
First off some questions please.. and I'm running win 11 pro.
What am I suppose to see on the screen when on Brom mode ? or how do I know that I'm on that mode.. obviously that if I'm not the operations just fail.
cant run mtk_gui atm for some reason trying to clear that out.. 'C:\Users\Q\AppData\Local\Programs\Python\Python311\Lib\site-packages\shiboken6\libshiboken does not exist'
Also tried bypass_utility_v1.4.2 using dif. key combos always returns 'device in preloader mode, trying to crash..'
mtkclient handshake returns failed 'Preloader - [LIB]: status: handshake failed, retrying..'
I'll keep on trying to understand all this just need my time.. all help appreciated.
Click to expand...
Click to collapse
for brom/preloader mode you will need to use the shorting method shown in the previously mentioned youtube video, not sure why you're trying mtk_gui and bypass_utility_v1.4.2 , what are you trying to achieve by using them?
Well reading from github where you get the mtkclient I thought that I could unlock the bootloader using the bypass_utility_v1.4.2 just like that.. guess ain't that easy and tbh after reading your previous words also thought that I could try using the mtkclient regardless being via the gui or the terminal.
I have seen some posts about the Brasilian fella and more shorting method but thought that by now wouldn't be needed anymore.. I did have my phone open before 'cause of that.. guess I'll have to have a look again.. my bad.
Thanks again.
BadChoices said:
Well reading from github where you get the mtkclient I thought that I could unlock the bootloader using the bypass_utility_v1.4.2 just like that.. guess ain't that easy and tbh after reading your previous words also thought that I could try using the mtkclient regardless being via the gui or the terminal.
I have seen some posts about the Brasilian fella and more shorting method but thought that by now wouldn't be needed anymore.. I did have my phone open before 'cause of that.. guess I'll have to have a look again.. my bad.
Thanks again.
Click to expand...
Click to collapse
you might be able to get into brom/preloader mode by holding volume down button while it is booting but shorting also brings the same result
aryanhington said:
you might be able to get into brom/preloader mode by holding volume down button while it is booting but shorting also brings the same result
Click to expand...
Click to collapse
I still can't believe what is that I ran into.. so was about to disassemble the motherboard/cameras cover that doesn't look that straight forward but went on checking again some bits on the vid.. meanwhile made a search for moto g8 power lite disassembling when got the suggestion moto g8 power lite frp bypass.. the first vid solved my issue.. I just died 'cus I have been wondering about an hack like this for ages now.
I'll come back for some further assistance on some other devices when I get the... brains.
Thanks for the support @aryanhington
BadChoices said:
I still can't believe what is that I ran into.. so was about to disassemble the motherboard/cameras cover that doesn't look that straight forward but went on checking again some bits on the vid.. meanwhile made a search for moto g8 power lite disassembling when got the suggestion moto g8 power lite frp bypass.. the first vid solved my issue.. I just died 'cus I have been wondering about an hack like this for ages now.
I'll come back for some further assistance on some other devices when I get the... brains.
Thanks for the support @aryanhington
Click to expand...
Click to collapse
care to share what you did so we can know?
I do care.. I also care the way some people talk to others behind screens.
Now if you read what I have just said on my previous post and the first post so to get what you/I'm dealing with you will realize that I was stuck on welcome screen, after soft reset, 'cus of FRP, once the last google account used was still active and I had no clue. Just use the search string on youtube that I have mentioned and on the first vid follow the 20k steps to be able to bypass google/android FRP.
Farewell.
Would someone please point me out their fav XT2055-1 roms ?
Thank you.
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?
Here was a Guide. Someone said people don't care about Me or My Work so...
This doesnt work on US model of Xperia 5 IV ( XQ-CQ62) because Sony isnt allowing bootloader unlock in USA.
Meaning you cannot get unlock codes for your phone thru sony website ,thats a crucial step in this guide.
hello, i've tried flashing the patched file onto my device but it just seems to bootloop, i'm currently running 64.1.a.0.857
viper. said:
This doesnt work on US model of Xperia 5 IV ( XQ-CQ62) because Sony isnt allowing bootloader unlock in USA.
Meaning you cannot get unlock codes for your phone thru sony website ,thats a crucial step in this guide.
Click to expand...
Click to collapse
Wow......glad I got the JP version of a new phone for once! Otherwise it's still blowing my mind that Sony itself isn't scrutinizing root like damn-near every other manufacturer as of late.
It's been more than 7 years since I rooted my last phone. Now is everything very different. Thanks for the thread, I know what I will do this weekend.
Just got my 5IV (UK) and exactly the guide I was looking for but just a simple question
My last personal Sony was the Z3C and unlocking bootloader/rooting that had drm issues with the official camera etc
Does unlocking bootloader with 5IV have any app issues, do the camera apps all work exactly as before and any other imporant Sony apps?
Will I be able to use Sony OTA updates?
If all good, I'll be unlocking and rooting this weekend, cant wait.
Thanks
rawdealer said:
It's been more than 7 years since I rooted my last phone. Now is everything very different. Thanks for the thread, I know what I will do this weekend.
Click to expand...
Click to collapse
Bruh! You and me both!! I finally rooted my Asus Zenphone 6 this past October. A bunch of reading and forums lol. Also back 7-8 years ago there were plenty of Youtube videos. Now not so much! My Zenphone 6 just died today and I am 90% sure I'll be getting the Xperia 5IV which I was eyeing since announced. I was hoping my Zenphone would have given me one more year, but alas. I'm visiting here to get the scoop on rooting this in the event I want to. I feel your pain!
smudgy636 said:
hello, i've tried flashing the patched file onto my device but it just seems to bootloop, i'm currently running 64.1.a.0.857
Click to expand...
Click to collapse
HI, not sure if you solved it, had the same issue. So, as it gave an option to do full user reset (or something like that) I chose it. It then rebooted and I was back into the phone with the initial setup again.
I then re-installed the latest magisk app and it showed that magisk/root is installed.
As a test, I then installed f-droid and installed Adaway. I chose to configure in root mode,
the 'grant access' dialogue popped up and boom, root access provided.
Btw, if you do want to install Adaway too, enable systemless host in magisk preferences.
Trying it now... It's a bit of a hassle, but that's on Sony.
Edit: yep, works an absolute treat. One little remark: Wiping after installing Magisk isn't neccesary, afaict. Perhaps make it optional "in case of weird problems".
thany2 said:
Trying it now... It's a bit of a hassle, but that's on Sony.
Edit: yep, works an absolute treat. One little remark: Wiping after installing Magisk isn't neccesary, afaict. Perhaps make it optional "in case of weird problems".
Click to expand...
Click to collapse
So, no need to wipe all user data or?
how to hide root from GooglePay?
So I'm getting stuck on the OEM unlock bit. After entering the command I get this:
...
FAILED (remote: Command not supported in default implementation)
finished. total time: 0.004s
Click to expand...
Click to collapse
Any Ideas?
hasztagL said:
how to hide root from GooglePay?
Click to expand...
Click to collapse
Why would you need to? Play works perfectly fine with non-hidden root.
Either way, try enabling Zygisk in the Magisk manager. You might also have to check to enforce the DenyList, and check the Play app on the DenyList.
But really it's not neccesary in my experience. The only app that refuses to work properly is my banking app. In their infinite stupidity they demote rooted users to a PIN code instead of fingerprint, even though on a rooted device, the fingerprint is still more secure. But I digress, sorry.
Skv012a said:
So, no need to wipe all user data or?
Click to expand...
Click to collapse
I guess it was a catchall. Maybe if you've already been tinkering a lot, it might be a good idea to "start over", since Magisk can completely fluff up you phone if it's being interfered with. However, my phone was completely stock, other than being bootloader-unlocked, so in my case the answer is no, not needed.
No promises though. Just give it a go. Do have a backup ready.
thany2 said:
Why would you need to? Play works perfectly fine with non-hidden root.
Either way, try enabling Zygisk in the Magisk manager. You might also have to check to enforce the DenyList, and check the Play app on the DenyList.
But really it's not neccesary in my experience. The only app that refuses to work properly is my banking app. In their infinite stupidity they demote rooted users to a PIN code instead of fingerprint, even though on a rooted device, the fingerprint is still more secure. But I digress, sorry.
Click to expand...
Click to collapse
Google Wallet not work with root. With DenyList still not work.
Matrixclonk said:
So I'm getting stuck on the OEM unlock bit. After entering the command I get this:
Any Ideas?
Click to expand...
Click to collapse
It looks like you started fastboot mode. You should enter bootloader mode for the fastboot command for some reason
Also I had a problem in bootloader mode and had to manually update the driver in Windows for the phone.
When I was in bootloader, the adb devices and fastboot devices commands did not return anything, meaning the phone wasn't found.
So if someone else's phone isn't recognized in fastboot/bootloader mode you could try installing the driver manually like so:
Open the Device Manager in Windows and under under Other devices (probably), there will be a device named Android with a question mark (meaning no driver or problem with it.)
Then right click on it -> Update driver -> Browse my computer for drivers -> Let me pick from a list of available drivers... (you should have installed the drivers from windows (in file explorer, right click, install on the .inf file))
Then there under Android, from Google I had the ADB Interface driver which I selected and Installed it forcefully.
And after that fastboot comand worked normally.
alexdo said:
It looks like you started fastboot mode. You should enter bootloader mode for the fastboot command for some reason
Also I had a problem in bootloader mode and had to manually update the driver in Windows for the phone.
When I was in bootloader, the adb devices and fastboot devices commands did not return anything, meaning the phone wasn't found.
So if someone else's phone isn't recognized in fastboot/bootloader mode you could try installing the driver manually like so:
Open the Device Manager in Windows and under under Other devices (probably), there will be a device named Android with a question mark (meaning no driver or problem with it.)
Then right click on it -> Update driver -> Browse my computer for drivers -> Let me pick from a list of available drivers... (you should have installed the drivers from windows (in file explorer, right click, install on the .inf file))
Then there under Android, from Google I had the ADB Interface driver which I selected and Installed it forcefully.
And after that fastboot comand worked normally.
Click to expand...
Click to collapse
Thanks man, I was in fastboot because when I went to bootloader I always got the message waiting for device. Also weird I had to reinstall the driver each time i went into bootloader :S
@Miustone Hey. I rooted my phone following your guide and I have a question.
Sony have released an update was wodnering if I flash the latest update, will my settings/data be intact? Apparaently the update is only small, just wish I could flash that...not the whole 3.3GB
Thanks
After getting said from some Stock Tree ROM Cookers that People wont miss Me around Xperias (and that i havent developed that much), i just decided to take My Work offline and to remove also My Guides. Sorry for everyone who apprecciated My Contributions but You will get Stock FW based ROMs instead (one Day)! It wont have the quality or safeness of a good old SODP based ROM (since they refuse to work with it on a disrespectful way) but hope You will be fine with it somehow!
All the Best for the future,
Miu
Miustone said:
After getting said from some Stock Tree ROM Cookers that People wont miss Me around Xperias (and that i havent developed that much), i just decided to take My Work offline and to remove also My Guides. Sorry for everyone who apprecciated My Contributions but You will get Stock FW based ROMs instead (one Day)! It wont have the quality or safeness of a good old SODP based ROM (since they refuse to work with it on a disrespectful way) but hope You will be fine with it somehow!
All the Best for the future,
Miu
Click to expand...
Click to collapse
sad. i love your work.