Develop Bugs

[Q] Random Reboots on ZF2 4gb/32gb

Hello,
Anyone facing issues of random reboots on ZenFone 2 4gb/32gb model?
If yes, how to come over this issue?
Mine is a WW version. Bought it from FlipKart. Un-rooted.

Suhas_JS said:
Hello,
Anyone facing issues of random reboots on ZenFone 2 4gb/32gb model?
If yes, how to come over this issue?
Mine is a WW version. Bought it from FlipKart. Un-rooted.
Click to expand...
Click to collapse
You could back up any important information you had, format the phone and then sideload either the stock firmware (available from Asus) or the pre-rooted images available here.

kibmikey1 said:
You could back up any important information you had, format the phone and then sideload either the stock firmware (available from Asus) or the pre-rooted images available here.
Click to expand...
Click to collapse
Just hard reset or complete wiping of cache, dalvik, data, root and then reload the stock/pre-rooted ROM?

It's what I would try.
Download these, if you don't have them:
Intel USB Driver
ADB & Fastboot Tool
and either stock ROM from Asus or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.

Thanks a ton mate
Sent from my ASUS_Z00AD using XDA Free mobile app

i suspect this has alot to do with android 5.0. asus needs to work on getting 5.1 to the device.

Suhas_JS said:
Thanks a ton mate
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
what rom did you install? latest or stock?
did you follow the step one or alternative??
please help me i got the same problem.

kibmikey1 said:
It's what I would try.
Download these, if you don't have them:
stock ROM from Asus[/URL] or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.
Click to expand...
Click to collapse
following the process i have install stock rom... with adn sideloader... this version is not suporrted so download 1.0.32 form other place.. sucessfully install the rom . don't know yet the problem is solved or not.. but i will post update after using .. thanks man.. atlest after viewing lots of form alon with asus whole day.. following urs sucessfully able install the rom with adb sideload. thanks a lot. now hope it will work fine.
---------- Post added at 06:54 PM ---------- Previous post was at 06:48 PM ----------
kowsar684 said:
following the process i have install stock rom... with adn sideloader... this version is not suporrted so download 1.0.32 form other place.. sucessfully install the rom . don't know yet the problem is solved or not.. but i will post update after using .. thanks man.. atlest after viewing lots of form alon with asus whole day.. following urs sucessfully able install the rom with adb sideload. thanks a lot. now hope it will work fine.
Click to expand...
Click to collapse
no problem is still there ...... should i install pre root rom???
---------- Post added at 07:01 PM ---------- Previous post was at 06:54 PM ----------
what is the difference between stock ROM and pre root ROM???

can't install stock rom. how to flass

kibmikey1 said:
It's what I would try.
Download these, if you don't have them:
Intel USB Driver
ADB & Fastboot Tool
and either stock ROM from Asus or
if you prefer, the same latest ROM pre-rooted from here. Make sure you have the ROMS in your platform-tools folder of the adb/fastboot tool you downloaded.
Once you have everything you need:
Restart your phone and hold volume up to enter fastboot/bootloader.
Test the connection from your pc adb/fastboot terminal by typing: fastboot devices. You should see numbers and device listed. If not, double check your driver installation and try again. Once the connection's established,
Enter the following fastboot commands:
fastboot format system
fastboot format cache
fastboot format data
Once completed, you have two methods to install the ROM of your choice. You can unzip the pre-rooted rom and install each partition individually. Note, you need to unzip system.img into the folder with the other img's. Once again, be sure to copy these img's to the platform-tools folder of the adb/fastboot tool. These fastboot commands are:
fastboot flash fastboot droidboot.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Once completed, use the volume selection menu to do a normal boot into Android, and setup from there.
Alternatively you could sideload the Asus ROM from adb in recovery. To do this, use the volume selection menu to do a reboot into recovery mode. In recovery, select install update from ADB. In your adb/fastboot terminal type:
adb devices (to check connection)
adb sideload (either drag and drop the ROM or enter the /path)
Once it loads, reboot into system, and setup from there.
Please do research this and make sure this is what you want to do. I hope this helps.
Edit: I know these instructions can be found elsewhere, but I couldn't in good conscience advise someone to wipe their phone and not help them. I'd never ask someone else to do something I wouldn't do.
Click to expand...
Click to collapse
Thanks a million man.
This saved me instead of sending back the phone rto newegg after a failed cache format.
Repped!!!

I have folowed all step successfuly but reboots are still there, i can't do **** about them, mostly happen installing / updating apps and playing games, sometime it's just random, listening music.

more ideas about why it's happen?

I have recently had a spate of random reboots. Thought it was flip cover causing problem, still the same. Its the 32Gb, 4Gb ram, 1.8mhz model.
Phone is stock, all updates applied and problem happening much more after last update, 22.

sandozer said:
I have recently had a spate of random reboots. Thought it was flip cover causing problem, still the same. Its the 32Gb, 4Gb ram, 1.8mhz model.
Phone is stock, all updates applied and problem happening much more after last update, 22.
Click to expand...
Click to collapse
If you have been using the phone as an ordinary consumer, I would suggest to get a replacement if that's within your entitlement. Just my personal opinion.
Sent from my ASUS_Z00AD

Anyone get a random shutdown with the 2.19.40.20 firmware? Happened to me overnight/this morning, at 98 to 96% charge. First time this has happened with this device.
No last_kmsg to share, so will keep a watch on it for now...
Edit: happened a second time, this afternoon. Maybe I will upgrade to 2.19.40.22, or at least install TWRP to see if I can grab a last_kmsg (if I can find it) to see what's going on..

chooks06 said:
If you have been using the phone as an ordinary consumer, I would suggest to get a replacement if that's within your entitlement. Just my personal opinion.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
Yes, good advice ! Unfortunately I bought it in Hong Kong at the beginning of April. It has had no problems, seems like the last update upset something. Maybe 5.1 will do me a favour . . . .

@sandozer..5.1 will do a lot of good for a lot of people

sandozer said:
Yes, good advice ! Unfortunately I bought it in Hong Kong at the beginning of April. It has had no problems, seems like the last update upset something. Maybe 5.1 will do me a favour . . . .
Click to expand...
Click to collapse
If you have not tried resetting the phone, it may be worth a try, though painful to start setting up all over again. You can try using the stock ASUS back up app to do your back up..
Sent from my ASUS_Z00AD

I am on 22 and have random reboots as well?

I had 2 random reboots on the 2gb/16gb version, but I think it was USB cable related. I'd plug the phone into the car and do something fast and then lock it, POOF! Reboot. It hasn't happened in awhile though and I believe I did an OTA update afterwards.

D855 Stuck at Boot Screen

So I think I've gone and bricked my LG G3.
After the ROM I was using, cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd) from here, kept freezing 20 seconds after startup, I went to update to cm-13.0-20160325-NIGHTLY-d855 (CM13 March 25th). I booted into recovery (TWRP 2.8.7.0) as usual and went to flash both the ROM's .zip file and an Opengapps .zip file using TWRP's queue feature. However, it appeared to get stuck at a line (unfortunately I don't remember what it said exactly. Something involving patching system, I think), so I pulled the battery. I get the feeling this was a super not good thing to do, as my G3 now sits at the "LG - Life's Good" screen indefinitely. Holding Power+Vol.Down does not boot into Recovery, and neither does holding Vol.Up and plugging into my computer activate Download mode.
I tried to be as thorough as I could with exactly the steps I took, so I'm just hoping someone can give me a few pointers on what I can do.
As I type this I had the phone connected to my computer next to me, and I've suddenly heard the Windows "Device connected" sound and the phone is now showing this in the top right corner, in tiny font:
Code:
[784670] Fastboot mode started
[784820] -- reset --
[784820] -- portchange --
Edit: When this occurred, a device named "Android" appeared under the "Other devices" tab in Windows Device Manager. It's got a yellow warning sign next to the icon, and Properties says that the drivers for the device aren't installed.
Perhaps this is relevant to getting it working again.

First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...

bender_007 said:
First you need the adb drivers for lg g3
Then you need proper partitions, depends what your starting system was, before cm..
then simply reflash them
fastboot flash aboot aboot.img
fastboot flash recovery twrp.img (because you don´t have one)
fastboot flash laf laf.img (this should fix the download mode)
Depending on what the system in original was and what the cm package installed...
Click to expand...
Click to collapse
Many thanks for the reply.
By ADB drivers for the LG G3, do you mean the Lg United Mobile Driver? I have version 3.13.2 of them, if that's what they are.
When I input the commands
Code:
adb devices
or
Code:
fastboot devices
nothing appears, so are there different drivers I should look for?
I'm not too sure how to "fix" partitions, either, but I'm guessing it requires ADB/fastboot.
The file aboot.img and laf.img, will I need to find somewhere to download them from?
Again, I appreciate the response.

In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)

bender_007 said:
In case you have the drivers not installed (the "android" device without drivers in device manager), try with "google adb driver" ->
or pdanet
however the lg one should be fine (if not -> try one of the ones I mentioned)
Click to expand...
Click to collapse
I used PdaNet to install the LG drivers, and inputting the command "fastboot devices" now shows
Code:
? fastboot
Inputting "adb devices" does not show anything, however.
I then attempted to flash a recovery, TWRP version 2.8.7.0 with the command "fastboot flash recovery "recovery.img"". However, the phone's screen showed the following:
Code:
[998960] Error: Command never completed
[998960] Error: Auto CMD12 Error
[998960] Error: Command never completed with errors
[998960] Failed Writing block @ 1
How do I fix the partitions and find the files "aboot.img" and "laf.img"?
Thanks for your help so far, I'm glad that there is progress now.

it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor

bender_007 said:
it has to be fastboot flash recovery recovery.img (where recovery.img is twrp.img, twrp.bin, recovery.img or similiar, without any quotations)
What happens when you try to enter TWRP? Are you doing it right? Hold volume down and power ---- wait for lg logo an release for less than a second and keep holding again.
aboot and laf are downloadable or extractable (from KDZ/TOT) -> use bullghosts kdz/tot extractor
Click to expand...
Click to collapse
I retried the command fastboot flash recovery recovery.img but it resulted in the same output as before.
I followed the exact instructions to enter TWRP but it just stays at the LG logo screen. I've held Power+Vol.Down for about a minute after quickly releasing it+pressing it again at the LG logo, but it just doesn't do anything.
I've found myself a Lollipop KDZ file. The CyanogenMod I was running, however, ran on Android 6.0 Marshmallow. Will I need a Marshmallow KDZ file instead?

check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)

bender_007 said:
check PM - Private Messages
+check out this drivers(I packaged few of them, there is also lg adb, try the ones)
Click to expand...
Click to collapse
I appreciate the offer to use Teamviewer to help me, but I think it would be best if you typed out some instructions in a reply to this thread so that others with the same issue can refer to here.

Solution
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.

HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" from here, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)

bender_007 said:
Glad you got it working
Regarding teamviewer - it was an exploration mission so I would see how your device behaves, maybe wrong drivers, maybe..100reasons (I certainly would write it in here if there was a better idea on my side)
Click to expand...
Click to collapse
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.

HexManiacSpeck said:
That's alright, many thanks for your help. I've just heard bad stories regarding Teamviewer and didn't want to risk anything.
Click to expand...
Click to collapse
No problem, sometimes you have to trust people
There were people who asked for help, installed teamviewer and didn´t gave any control permissions (which is fine). But they were expecting someone is having soo much free time to explain things (which I would if I had time)
cheers, flad you fixed it

Fixed my G3 I was about to send to trash!
HexManiacSpeck said:
I've found a solution to my issue, at least.
Downloading "recovery.img" fromhere, putting it in the same folder as fastboot, and then using the command
Code:
fastboot boot recovery.img
booted my phone properly, into cm-13.0-20160322-NIGHTLY-d855 (CM13 March 22nd).
However this resulted in all data being erased, including internal storage.
After using Flashify to re-flash TWRP (just in case), everything works as it should.
Click to expand...
Click to collapse
Thanks a million for pointing to this recovery file!
I was also in a situation where all my attempts to flash a recovery were failing due to:
Failed Writing block @ 1
Click to expand...
Click to collapse
The rest of my phone was unusable (no working recovery, no download mode, just the LG logo or this fastboot mode)
I tried several TWRP recovery versions & flavors, but so far, I only successfully reboot in recovery using CyanogenMod recovery file (download.cyanogenmod.org/?device=d855). Though I was not able to do much afterwards apart some adb commands that were not working either.
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p20
dd: /dev/block/mmcblk0p20: write error: I/O error
This recovery img did the trick and I'm now back with a CyanogenMod ROM and a wiped phone.

[Guide] Unlock/Root/Update/Relock for BQ Aquaris X2 pro (zangyapro)

Introduction
I'm writing this thread to summarize useful information about the BQ Aquaris X2 pro such as:
preliminary actions (adb and fastboot configuration)
unlocking the bootloader
flash a factory image
root the device (currently without TWRP)
updating the device without losing root
relocking the bootloader
I own this phone since July 2018. I started writing my notes in August 2018 in the form of a Google document (link here). I shared this document with some telegram groups and some people I know.
Now I that I think it can be more useful to summarize all my notes here on XDA so that all interested people can access it.
DISCLAIMER:
By attempting any of the processes listed in this thread you accept full responsibility for your actions. I have no responsibility about your actions.​
1) Preliminary actions
1.1) Developer options, USB debugging and Unlock OEM
The first thing you need to do is to enable Developer options, USB debugging and Unlock OEM. Hence:
enable “Developer options” by hitting 7 times on the build number (Got to settings --> about phone)
enter the new menu “Developer options” and,
enable “USB debugging”
enable “Unlock OEM”
1.2) Download and configure abd and fastboot
All steps listed in this guide will require the use of Google Platform tools. I suggest the use of the one provided by Google here: https://developer.android.com/studio/releases/platform-tools.
Download the one for your operating system:
View attachment 4655394
Be sure that your terminal can access adb and fastboot from every position by configuring the PATH. I'm use to configure the PATH on the fly when I need it. As I said before, I work on Linux/macOS where you can set the PATH by:
opening a terminal and running:
Code:
export PATH=$PATH:path_to_platform_tools
2) Unlock the bootloader
Unlocking the booloader will wipe your phone. So backup your data first.
The good news here is that this phone can be handled like a Nexus/Pixel phone. Therefore, the procedure to unlock the bootloader is straightforward:
do all stuff at point 1.1 and 1.2
open a terminal
plug your phone to the PC
reboot into the bootloader
Code:
adb reboot bootloader
run the code:
Code:
fastboot flashing unlock
now you have to wait until your phone reboots. It takes a while, don't panic!!! When the phone is on the initial screen turn it off and reboot into the bottloader again by holing 'power + volume down'.
run the code:
Code:
fastboot flashing unlock_critical
it's done. Your bootloader is completely unlocked. Now, you only have to wait again for the reboot.
3) Flash a factory image
As you probably know, BQ releases a factory image at each update at this link factory images. Factory images are very useful to perform a very clean install. Are you experiencing some issues with your phone and none of the trick you tried solved it? If it is a software issue a clean flash with a factory image will likely remove the issue.
Keep in mind that by flashing a factory image you will wipe also the userdata partition. So backup your data first. Now let's see how to flash the factory image:
you need an unlocked bootloader (see previous sections)
download the factory image from this link
unzip the archive
open a terminal at this folder
be sure to have abd and fastboot properly configured (see previous sections)
run the script to flash all (*):
Code:
./sdm660_fastboot_all_images.sh
wait the end of the process. The phone will reboot.
(*) on Windows you have to deal with the file sdm660_fastboot_all_images.bat. I suppose it's similar but I've never done it on Windows.
4) Obtain ROOT privileges
Nowadays, the most common tool to obtain root privileges is Magisk. Many people here know very well what Magisk is and how to install it with TWRP. However, TWRP is not yet ready for BQ Aquaris X2 pro, hence, we must follow the procedure for installing it without the custom recovery.
When I wrote the document in August I find very informative this guide by @nathanchance. It's for the pixel 2XL but, as I told you before, it works perfectly also for the BQ Aquaris X2 pro (zangyapro). So here I summarize what @nathanchance already posted. All credits must go to him.
Here you have the steps:
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Please note that it exists also a specific thread where the author also provides the patched boot.img files for download. Hence, you can start from point 6 without patching the boot.img by yourself. Take care of selecting the right one. Here you have the thread link.
5) Update the ROM without loosing root
To the best of my knowledge, the only way to update keeping root is by using the factory images provided by BQ.
Download the factory image of the latest firmware (link)
Extract the file zip and upload the file boot.img on your phone
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt and then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Place the file patched_boot.img in the folder of the BQ firmware unzipped at point 2
Make a copy of the file sdm660_fastboot_all_images (.sh in Mac/Liux and .bat on Windows).
Rename the file, I called it sdm660_fastboot_upgrade.sh
Change the following lines (this will preserve root privileges on your phone):
Code:
fastboot flash boot_a boot.img # <-- delete this line
fastboot flash boot_a patched_boot.img # <-- add this line
Delete the following line (this will prevent your data to be wiped):
Code:
fastboot flash userdata userdata.img # <-- delete this line
Run from your terminal
Code:
./sdm660_fastboot_upgrade.sh (or bat)
I think that one can also update using the OTA. This will make you lose the root privileges and therefore, you will have to repeat the procedure at section 4. I've never tested this so, if you decide to do it, you are on your own.
6) Relock the Bootloader
By relocking the bootloader you will lose all your data, hence, backup them first.
To relock the bootloader you only need the following commands:
Code:
fastboot flashing lock_critical
fastboot flashing lock
Each command will wipe your data and will reboot the phone. Be patient waiting for the reboot and do not panic.

Reserved.
(work in progress)

First: Thanks for this really nice and comprehensive thread!
I have an important addition to point:
3. Open Magisk Manager and click the Install button.
Click to expand...
Click to collapse
Install Button will only appear if the phone has internet connection (Wifi or Mobile Data)
with this I can patch the boot image successfully
But unfortunately I can not run the "sdm660_fastboot_upgrade.sh.bat" it does not recognize my device.
When checking the commands in the batch I found that my device is acting really strange, sometimes giving different errors for the same command like:
Code:
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
error: Device does not support slots.
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
Setting current slot to 'a'...
FAILED (remote: Invalid Slot)
finished. total time: 0.004s
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot set_active _a
error: Device does not support slots.
also strange:
Code:
C:\Android\X2proRoot\1.7.1_WithRoot>fastboot flash boot patched_boot.img
target didn't report max-download-size
sending 'boot' (50749 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Probably some windows crap not working or an incompatibility of the installed platform tools / drivers and the ones from BQ...

raudidroid said:
First: Thanks for this really nice and comprehensive thread!
I have an important addition to point:
Install Button will only appear if the phone has internet connection (Wifi or Mobile Data)
Click to expand...
Click to collapse
Thanks. I was not aware of this. And now I can't check this on my device because I started using GPay and I prefer to stay with no root and locked bootloader.
Maybe I will play again with the bootloader when TWRP for this device will be released. If it will

got it running!
raudidroid said:
Probably some windows crap not working or an incompatibility of the installed platform tools / drivers and the ones from BQ...
Click to expand...
Click to collapse
Probably it was just that. I Installed Ubuntu 16.04 LTS in a Vmware machine and followed the tutorial (important note here: do everything in a Terminal running under root).
Short moments of panic due to boot-loop included (I flashed a defective boot image [vmware drag and drop files obviously did not copy the whole file] )
for everybody who ends in a bootloop: just keep calm, switch off phone (>10s press power button) an very quickly when it is of press power and volume down to get into flashmode again (I had to try several times)

Hey @raudidroid, when I answered to you the first time I did not read all the message or you edited it later. Only now I'm reading the issues you faced.
On Windows, what shell did you use? PowerShell?
I'm not sure about this because I banned Windows from my personal and working life several years ago, however, recently I read some posts of people having issues with PowerShell. If this is also your case next time try to use classic cmd.
Probably it was just that. I Installed Ubuntu 16.04 LTS in a Vmware machine and followed the tutorial (important note here: do everything in a Terminal running under root).
Click to expand...
Click to collapse
Regarding this the above quote, I'm quite sure that you do not need to be super user to apply any of the procedure listed in the guide.
for everybody who ends in a bootloop: just keep calm, switch off phone (>10s press power button) an very quickly when it is of press power and volume down to get into flashmode again (I had to try several times)
Click to expand...
Click to collapse
Since your are suggesting "... very quickly when it is of press power and volume down ... " I can imagine that you did this procedure while your phone was connected to the laptop/PC with the USB cable. In this condition, when you force the shutdown by pressing power for 10s, the phone reboots automatically. So my suggestion is to unplug it first, in this way the phone turn off without rebooting and you can comfortably enter in the bootloader with no hurry.

luk.giak said:
On Windows, what shell did you use? PowerShell?
I'm not sure about this because I banned Windows from my personal and working life several years ago, however, recently I read some posts of people having issues with PowerShell. If this is also your case next time try to use classic cmd.
Click to expand...
Click to collapse
I was using CMD / Command Prompt on win10, but maybe I have to many ADBs/Drivers/... installed. got a really weird behavior...
Regarding this the above quote, I'm quite sure that you do not need to be super user to apply any of the procedure listed in the guide.
Click to expand...
Click to collapse
without root it wouldn't work, i got "no permissions (user in plugdev group; are your udev rules wrong?)"
with root everything ran smoothly
Since your are suggesting "... very quickly when it is of press power and volume down ... " I can imagine that you did this procedure while your phone was connected to the laptop/PC with the USB cable. In this condition, when you force the shutdown by pressing power for 10s, the phone reboots automatically. So my suggestion is to unplug it first, in this way the phone turn off without rebooting and you can comfortably enter in the bootloader with no hurry.
Click to expand...
Click to collapse
Oh! Yep, that sounds like it would have been the better way to do it
Thanks for your post and your answers.
BTW: half-OT do you know any way to get netflix running after the rooting?

For your information.
I follow part 5 and updated my firmware to version 1.7.3 successfully. Thanks for this guide.

AndroidenKalle said:
For your information.
I follow part 5 and updated my firmware to version 1.7.3 successfully. Thanks for this guide.
Click to expand...
Click to collapse
Your welcome!

For your information.
I follow part 5 and updated my firmware to version 2.0.0 (Android Pie 9) successfully.

AndroidenKalle said:
For your information.
I follow part 5 and updated my firmware to version 2.0.0 (Android Pie 9) successfully.
Click to expand...
Click to collapse
Thanks for sharing.
I'm on PIE as well. Today I flashed the factory image to make a clean install.

Hello, maybe someone can be of help to my situation.
I had my phone rooted in the last firmware version (1.7.3), and I was getting notifications to update to Android 9 pie for some time, however I was waiting to have some time to spare and first backup my files and do a factory update to pie and then root.
However, last nigh without warning my phone just rebooted and updated to pie, (firmware ver 2.0.2) and I lost root obviously. However, all my files, apps, etc were intact.
So today I decided to root my phone again. I download the firmware zip from BQ's site and then used Magisk (ver. 19.2) to patch the boot.img.
I rebooted to fastboot and did "sudo fastboot flash magisk_patched.img", and rebooted but the phone got stuck in the logo screen.
Then I used method 5 of this tutorial and ran ./sdm660_fastboot_upgrade.sh (with the mentioned modifications), however it bootlooped again. Then I flashed the original boot img and my phone booted just fine again, I tried to patch the img again, did again step 4 and it bootlooped again.
Any clues on how to successfully root ? Never had any problems updating and rooting from firmware 1.4.0 to 1.7.3.
Thank you for your time

GSIs that work on the E6

Here's what I've learned far about the E6:
Mostly from Treble Info app from Hackintosh Five
VNDK-28
Arm32 BINDER64
It's actually AB, according to it having System As Root.
No Seamless upgrade.
Binder64-AB/A64-AB GSIs work on this device.
Quack GSI should be the first we focus on.
TO INSTALL:
Code:
fastboot -w flash system <gsiname.img>
BOOTS
Quack GSI (AOSP 10, bb)!
Will list others as I come across them.

This is awesome.
I got LOS 16 bvn to boot.
The ril must be off or something, it had no connection.
I've got stock rom with encryption disabled and verity disabled, full magisk root living inside the boot.img..
And got twrp with touch adb and mtp working...
But it looks a lil funny cause the port has slightly smaller image so it doesn't fully fill screen.
But everything seems to work, including flashing zips..
Should that be a thread by its self?

LgPWN'd said:
This is awesome.
I got LOS 16 bvn to boot.
The ril must be off or something, it had no connection.
I've got stock rom with encryption disabled and verity disabled, full magisk root living inside the boot.img..
And got twrp with touch adb and mtp working...
But it looks a lil funny cause the port has slightly smaller image so it doesn't fully fill screen.
But everything seems to work, including flashing zips..
Should that be a thread by its self?
Click to expand...
Click to collapse
Yes, please! it's very nice that u did that, I'll link it in the main post when u do

For a working recovery see this
https://forum.xda-developers.com/moto-e6/development/development-team-looking-testors-t4120171

tried:
>fastboot flash system <image.img>
for all the 3 Quack GSI: system-quack-arm32_binder64-ab-gapps.img.xz, system-quack-arm32_binder64-ab-go.img.xz and system-quack-arm32_binder64-ab-vanilla.img.xz
The system just keeps looping the andriod logo...
Anyone knows of a twrp version that works with this moto e6?

soulmaker2207 Did you do the -w in fastboot after you installed the gsi? If you didn't it is definitely worth a try Beware it will erase all data including the internal sd

soulmaker2207 said:
tried:
>fastboot flash system <image.img>
for all the 3 Quack GSI: system-quack-arm32_binder64-ab-gapps.img.xz, system-quack-arm32_binder64-ab-go.img.xz and system-quack-arm32_binder64-ab-vanilla.img.xz
The system just keeps looping the andriod logo...
Anyone knows of a twrp version that works with this moto e6?
Click to expand...
Click to collapse
Alongside the fastboot -w advice, try renaming every img you download to "system.img." I have had way more success doing that than using long img names.
Also, I noticed that for a lot of GSIs, USB Tethering does not work.

Just installed latest phusson aosp android 11 gsi, over latest stock pie, using fastboot -w option, of course. Boots great, working VoLTE, sms, etc. Super fast performance. Usb tethering greyed out. That's the only problem I sound so far.

scottyrick2 said:
Just installed latest phusson aosp android 11 gsi, over latest stock pie, using fastboot -w option, of course. Boots great, working VoLTE, sms, etc. Super fast performance. Usb tethering greyed out. That's the only problem I sound so far.
Click to expand...
Click to collapse
Yeah USB Tethering doesn't seem to work for ANY GSI ROMs.

I am running Android 11 AOSP now using phhusson gsi rom V300.l. For your phone calling and sms to work properly, you need to follow this guide every time you reboot or power off/on. I mean every time.
[Razer Phone 2/as of v300.l/non-Verizon] IMS still needs some manual intervention to re-enable after reboot. · Issue #1681 · phhusson/treble_experimentations · GitHub
I have done this often enough now that I can do it in under 30 seconds. Hopefully, this issue will be fixed soon, but it is not that difficult to fix yourself.

scottyrick2 said:
I am running Android 11 AOSP now using phhusson gsi rom V300.l. For your phone calling and sms to work properly, you need to follow this guide every time you reboot or power off/on. I mean every time.
[Razer Phone 2/as of v300.l/non-Verizon] IMS still needs some manual intervention to re-enable after reboot. · Issue #1681 · phhusson/treble_experimentations · GitHub
I have done this often enough now that I can do it in under 30 seconds. Hopefully, this issue will be fixed soon, but it is not that difficult to fix yourself.
Click to expand...
Click to collapse
How odd. I can't get any Android 11 GSI to work on my E6

Are you trying to update from Android 10? I don't think you can.

scottyrick2 said:
Are you trying to update from Android 10? I don't think you can.
Click to expand...
Click to collapse
Yes I was trying to update from Android 10

I am running phhusson aosp 11 v300.l gsi rom right now. Super fast. Amazing, really.
If you are on the T-Mobile system, you need to do 3 things in order to make VoLTE and sms work properly. Hopefully, this will not be needed in future updates, but it might be.
1. using a root file explorer (I use 3C) to locate and move the org.codeaurora.ims folder from /data/app to /system/app
2. reboot
3. using *#*#4636*#*# on the dialer to open "phone information menu", change the band to GMS/WCDMA/LTE, and close the menu.
That's it. I hope this helps you to consider moving up to gsi roms. They are truly amazing.

Greetings people and like minded friends of the internet (and fellow trashman) I come bearing great gifts of flashing goodness. For the XT2005-5, I needed a nice de-Googled imaged phone for usage. As most of you probably have found in searching, finding TWRP and getting it to work has been a tedious journey. Never fear, there is a way to drop images on this phone. I will give you my experience and steps I took, in hopes it may help you save a bit of time.
1.) Download the factory image for the device found here
https://mirrors.lolinet.com/firmware/motorola/surfna/official/RETUS/ I used this one https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-XT2005-5-SKU6_CFC.xml.zip Use a program like 7-Zip to extract it to a folder of your liking and you will use this folder later in the process. Of course, you're welcome to stop here and just flash the factory image and be done. But after all, why would you be reading this post if you wanted to just stop here, right?!
2.) Now find a GSI system image of your liking for flashing to the phone. I used the following system image from PHH (KUDOS FOR THE MAN WHO ROCKS GREAT ANDROID SKILLS) https://github.com/phhusson/treble_experimentations/releases For this phone you can you ARM32/Binder64/AB and I decided to go with
system-roar-arm32_binder64-ab-vndklite-vanilla.img.xz as I wanted no GAPPS. You will need to use 7-Zip again to extract the image from the archive file you've download. You can extract this file anywhere for the time being.
3.) Rename the extracted image from step 2 to system.img (just for simplicity) and put the file in the same directory you've created from step1.
4.) Now create a flashfile2.bat with the following and put this .bat file in the same directory as Step1
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
5.) You will notice that I modified the .bat to flash the system.img that was downloaded in Step 2. Keep in mind, this method will re-write your system and you will LOSE ALL OF YOUR DATA so ensure you have YOUR DATA BACKED UP.
Run the flashfile2.bat file after you've connected your USB cable and you're at the bootloader screen
You already unlocked the bootloader, right? Hopefully, you're at least to BL screen, right after you've researched a bit about your phone .

b00ster23 said:
Greetings people and like minded friends of the internet (and fellow trashman) I come bearing great gifts of flashing goodness. For the XT2005-5, I needed a nice de-Googled imaged phone for usage. As most of you probably have found in searching, finding TWRP and getting it to work has been a tedious journey. Never fear, there is a way to drop images on this phone. I will give you my experience and steps I took, in hopes it may help you save a bit of time.
1.) Download the factory image for the device found here
https://mirrors.lolinet.com/firmware/motorola/surfna/official/RETUS/ I used this one https://mirrors.lolinet.com/firmwar...-DEFAULT_regulatory-XT2005-5-SKU6_CFC.xml.zip Use a program like 7-Zip to extract it to a folder of your liking and you will use this folder later in the process. Of course, you're welcome to stop here and just flash the factory image and be done. But after all, why would you be reading this post if you wanted to just stop here, right?!
2.) Now find a GSI system image of your liking for flashing to the phone. I used the following system image from PHH (KUDOS FOR THE MAN WHO ROCKS GREAT ANDROID SKILLS) https://github.com/phhusson/treble_experimentations/releases For this phone you can you ARM32/Binder64/AB and I decided to go with
system-roar-arm32_binder64-ab-vndklite-vanilla.img.xz as I wanted no GAPPS. You will need to use 7-Zip again to extract the image from the archive file you've download. You can extract this file anywhere for the time being.
3.) Rename the extracted image from step 2 to system.img (just for simplicity) and put the file in the same directory you've created from step1.
4.) Now create a flashfile.bat with the following and put this file in the same directory as Step1
echo off
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot erase modemst1
fastboot erase modemst2
fastboot erase userdata
fastboot erase cache
fastboot erase DDR
fastboot flash fsg fsg.mbn
fastboot oem fb_mode_clear
echo -------------------------------------------------------------------------
echo please scroll up and check your flash for any errors
echo -------------------------------------------------------------------------
pause
fastboot reboot
exit
5.) You will notice that I modified the .bat to flash the system.img that was downloaded in Step 2. Keep in mind, this method will re-write your system and you will LOSE ALL OF YOUR DATA so ensure you have YOUR DATA BACKED UP.
Run the .bat file after you've connected your USB cable and you're at the bootloader screen
You already unlocked the bootloader, right? Hopefully, you're at least to BL screen, right after you've researched a bit about your phone .
Click to expand...
Click to collapse
ARM32/Binder64/AB = a64 a/b OR potentially a64bvN/a64bvS
Something to make it easier on others.
There was a link for TWRP on this post but had to remove it because the link is dead. I'll explore other options before re-updating this post

koyo said:
Some things to add to this post to make it easier
1) ARM32/Binder64/AB = a64 a/b OR potentially a64bvN/a64bvS
2) I prefer doing it via this method rather than flashing stock files: - E6 AIO ToolKit Mod Release- | XDA Developers Forums (xda-developers.com)
This has a TWRP for E6 which allows you to flash things like magisk, universal encryption disabler, gapps, et cetera. Things that might not be built into the native ROM.
Click to expand...
Click to collapse
The links are all broken, and I see no TWRP available.

b00ster23 said:
The links are all broken, and I see no TWRP available.
Click to expand...
Click to collapse
Ugh oops. This is the result of going off of memory from months ago rather than checking to see if everything's up to date.
The developers that made that TWRP have an OrangeFox recovery to download on their telegram
Telegram: Contact @android_general_chat
t.me

koyo said:
Ugh oops. This is the result of going off of memory from months ago rather than checking to see if everything's up to date.
The developers that made that TWRP have an OrangeFox recovery to download on their telegram
Telegram: Contact @android_general_chat
t.me
Click to expand...
Click to collapse
Yeah, I don't see any links to the OrangeFox recovery img... Keep in mind this is for the XT2005-5 variant (SURFNA) unless OrangeFox is universal

b00ster23 said:
Yeah, I don't see any links to the OrangeFox recovery img... Keep in mind this is for the XT2005-5 variant (SURFNA) unless OrangeFox is universal
Click to expand...
Click to collapse
Telegram: Contact @Android_General_Chat
t.me

Moto G Power flashing guide

This guide also applies on other Moto phones shipping with Android 10 (not compatible with phone updated from Android 9)
Requirements:
* Adb must be up to date. You will use new fastbootd interface. You can toggle between bootloader and fastbootd.
* LMSA. You can get full ROM matched with your phone build number as well as required drivers
Working USB cable. Except you want to backup, restore, or rescue, close LMSA after ROM downloaded
* ADB debug is on and your host computer is trusted
* Your phone should be at least 60% battery. Manual flashing can take time
Are you ready?
1. Your phone should be in bootloader mode. Turn your phone off. Press and hold volume down and turn it on. You should see bootloader screen. Connect your phone to host computer.
2. Open LMSA and enter rescue in order to get full ROM. Go to the downloaded folder and go to ROM file. Watch the progress if you want to grab zip files. Copy it to somewhere you know. The zip file will be removed after unpacked by LMSA. However, all files you need are in the unzipped folder
3. Open command window and go to adb folder
4. Flash the following in bootloader
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash radio radio.img
fastboot flash logo logo.bin
5. Now toggle to fastbootd
Code:
fastboot reboot fastboot
6. Flash the following
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash super super.img.sparsechunk.x
All sparsechunk must be flashed by numeric order from zero
7. Toggle back to bootloader. Do the following:
Code:
fastboot reboot bootloader
fastboot erase carrier
fastboot erase ddr
(Optional except you want to wipe) fastboot erase userdata
8. Flash patched boot to root
Code:
adb reboot fastboot
fastboot flash boot patched_boot.img
fastboot reboot
That's it. Make sure you check Magisk Manager to check for hide as well as systemless host

i cant seem to toggle to fastbootd. when i put in the code i get the really long list of codes. And if i go into recovery and use power+vol up to get to fastbootd that way, if i try to flash anything, it fails and says no file or directory found

ok so my first root. took awhile, didnt know where to get the patched boot.img. figured it out though. thanks, it was simple

babyj3sus said:
ok so my first root. took awhile, didnt know where to get the patched boot.img. figured it out though. thanks, it was simple
Click to expand...
Click to collapse
Where? Or it becomes clear as-you-go ?

mingkee said:
This guide also applies on other Moto phones shipping with Android 10 (not compatible with phone updated from Android 9)
Requirements:
* Adb must be up to date. You will use new fastbootd interface. You can toggle between bootloader and fastbootd.
* LMSA. You can get full ROM matched with your phone build number as well as required drivers
Working USB cable. Except you want to backup, restore, or rescue, close LMSA after ROM downloaded
* ADB debug is on and your host computer is trusted
* Your phone should be at least 60% battery. Manual flashing can take time
Are you ready?
1. Your phone should be in bootloader mode. Turn your phone off. Press and hold volume down and turn it on. You should see bootloader screen. Connect your phone to host computer.
2. Open LMSA and enter rescue in order to get full ROM. Go to the downloaded folder and go to ROM file. Watch the progress if you want to grab zip files. Copy it to somewhere you know. The zip file will be removed after unpacked by LMSA. However, all files you need are in the unzipped folder
3. Open command window and go to adb folder
4. Flash the following in bootloader
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash radio radio.img
fastboot flash logo logo.bin
5. Now toggle to fastbootd
Code:
fastboot reboot fastboot
6. Flash the following
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash super super.img.sparsechunk.x
All sparsechunk must be flashed by numeric order from zero
7. Toggle back to bootloader. Do the following:
Code:
fastboot reboot bootloader
fastboot erase carrier
fastboot erase ddr
(Optional except you want to wipe) fastboot erase userdata
8. Flash patched boot to root
Code:
adb reboot fastboot
fastboot flash boot patched_boot.img
fastboot reboot
That's it. Make sure you check Magisk Manager to check for hide as well as systemless host
Click to expand...
Click to collapse
is there an way without using LMSA, i cant download it cus i have linux

When flashing patched_boot.img I get this
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 1.420s]
writing 'boot'...
FAILED (remote: No such file or directory)
finished. total time: 1.428s​
I'm not new to rooting i'm familiar with rooting Motorola phones... I just can not figure out what I'm doing wrong. Please any help would be amazing.

NEVERMIND i figured it out lol

In which location does the patched_boot.img get created? Also you mention Magisk. Is there more to the process than what you posted? It's been at least 7 or 8 years since I've rooted a phone. I followed the directions, but still feel like part of the process is missing, for those of us who don't do this on a regular basis.

In which location does the patched_boot.img get created? Also you mention Magisk. Is there more to the process than what you posted? It's been at least 7 or 8 years since I've rooted a phone. I followed the directions, but still feel like part of the process is missing, for those of us who don't do this on a regular basis.
abgrady said:
In which location does the patched_boot.img get created? Also you mention Magisk. Is there more to the process than what you posted? It's been at least 7 or 8 years since I've rooted a phone. I followed the directions, but still feel like part of the process is missing, for those of us who don't do this on a regular basis.
Click to expand...
Click to collapse
Yes, same here. What's the point to post incomplete guide? It just creates more problems for those, who don't know what he's doing.
I've rooted various phones in the past, each model is a different process, so complete and exact guide is a must. I guess this guide is missing Magisk part, which could be found somewhere. But isn't it to hard to put everything in one place?

I bought a g power a month after you wrote this guide - and I used this guide one time, thanks for that. I do it a little differently.
Flashing this phone is pretty easy, like walking in a straight line easy. Rooting is just as easy. Your vendor doesn't want you to do any of this. All vendors are different. They have their tricks and whatnot and in the game, those tricks must be found and gotten around. Thanks to those digging around....making things possible.
Why are yo flashing your phone? It's already got an OS, firmware. It's already doing what it does and it's what you bought. Aren't you happy? For fuk's sakes, Karen, you bought it!
There are reasons to flash your device. You might think - I'm just buying the hardware, and, that's cool. I get it, I do it...
Go get the firmware - lolinet. Find it - know what you are looking for. Don't brick your phone. Nobody is twisting your arm to do this.... Seriously, look in your settings - about phone - know what you are doing. Now, go get your firmware. Have you enabled developer mode? Debugging....
This guide is for Linux people.
Fire-up a terminal
sudo apt-get install android-tools-adb android-tools-fastboot
Reboot your phone to bootloader and plug your phone into your computer.
IN your terminal cd into the extracted firmware directory, run:
Code:
fastboot devices
You see a number returned? Good, proceed.
Let's put a copy of the boot.img into an archive right now because magisk will need it later (to spit a file out that you won't be able to find....baaaa ha ha haaaaa).
Code:
tar -cvf bootimg.tar boot.img
Flash it....run each line, or, make a script:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0 && fastboot flash super super.img_sparsechunk.1 && fastboot flash super super.img_sparsechunk.2 && fastboot flash super super.img_sparsechunk.3 && fastboot flash super super.img_sparsechunk.4 && fastboot flash super super.img_sparsechunk.5 && fastboot flash super super.img_sparsechunk.6 && fastboot flash super super.img_sparsechunk.7 && fastboot flash super super.img_sparsechunk.8 && fastboot flash super super.img_sparsechunk.9 && fastboot flash super super.img_sparsechunk.10 && fastboot flash super super.img_sparsechunk.11 && fastboot flash super super.img_sparsechunk.12 && fastboot flash super super.img_sparsechunk.13 && fastboot flash super super.img_sparsechunk.14 && fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Your phone will reboot into initial setup. Set it up. Cool, have fun with your phone, I guess. If you want root, read on. Don't take the 11 update. Sheesh! EDIT: I flashed my g power, stock 10, took the update, it's on 11 now. I rooted it, no sweat, lolinet has the firmware. Once you go root, there's no more taking updates - be cool with that, or, find a way.
Stop.
Do you really want root? Why are you rooting? For viper? Pffft. Rooting has trade-offs and you don't get to ***** about it later, fool; ain't nobody twisting your arm. You really want to root, 'cause you're ready.
Root is a sexy-fine chunk of plump lovin', awwwww, man. Just back it up one time, oh yeah, that's right.....but, **** comes out of it! Big smile, high-five. Welcome to the show.
That's right. THat's root. There's risk. You want root? Because the phone isn't yours until you have it. In fact it's actively working against you until you do. Let's go ahead and get root. You can handle a little ****, right? I mean, potentially.
Copy that bootimg.tar archive you made earlier onto your phone. Go get the magisk apk and install it.
Go enable developer mode on your phone. Enable usb debugging.
In magisk -
top section, top choice - touch the word: install. Touch it! Choose: select and patch file. Obviously.
Now is when you need that archive - you just copied it onto your phone, show magisk where it is.
Magisk will output a new boot image so you can root. Wicked. Go find it on your phone - it's not hiding. Where do apps put data on your phone? Copy that file to your computer.
Now - in orter to flash this new boot image file to your phone you must be in fastbootd. Take a breath. Reboot your phone into the stock recovery - just hold down power and voldwn for about 11 seconds - you should be at 'start'. Go into recovery.
Stock recovery is a barren wasteland of nothing - right on, let's go into fastbootd.
hold down the power button for 3 seconds, one onethousand, two one thousand....after 3 one thousand press the volup key as well - keep holding the power button down. after 5 one thousand, release the buttons. You should see a new menu. IF you don't, repeat the process until you do. THis is how, get it to work.
In the menu, voldwn to enter fastboot. It does not say fastbootd, but, it is. Choose it, and voila - you are now in fastbootd and in this screen it tells you as much.
ON your computer flash the new boot image:
Code:
fastboot flash boot NEWIMAGE.IMG
After, type:
Code:
fastboot reboot
When your phone boots up, it may loop for a few minutes or loop at the next reboot - go finish setting up magisk.
You are rooted.
Lemme ask you something - why are you rooting stock? If you want root then you want control - if you want control you know you aren't going to get it from stock - there's a ton of stuff going on there. Why not install a custom rom? Just food for thought. I root stock on my g power and run lineage on my edge, also rooted. I don't normally use my g power, though.
I hope my biting cynicism and step-by-step account of flashing firmware and rooting your shiny new g power is helpful. I'm not your dad - I could care less if you brick your phone. Don't cry to me if it doesn't work, because this does. It's a flick of the wrist, but, it's not for everybody. It's especially not for people, maybe like you, that hear a new thing and wanna jump right on it. Nobody in the world cares at all if you break your phone. Nobody is forcing you to do this, nobody forced you to buy this phone, to step left instead of right, to like red better than blue - it's all you. Own that because it's beautiful.

bronkish said:
I bought a g power a month after you wrote this guide - and I used this guide one time, thanks for that. I do it a little differently.
Flashing this phone is pretty easy, like walking in a straight line easy. Rooting is just as easy. Your vendor doesn't want you to do any of this. All vendors are different. They have their tricks and whatnot and in the game, those tricks must be found and gotten around. Thanks to those digging around....making things possible.
Why are yo flashing your phone? It's already got an OS, firmware. It's already doing what it does and it's what you bought. Aren't you happy? For fuk's sakes, Karen, you bought it!
There are reasons to flash your device. You might think - I'm just buying the hardware, and, that's cool. I get it, I do it...
Go get the firmware - lolinet. Find it - know what you are looking for. Don't brick your phone. Nobody is twisting your arm to do this.... Seriously, look in your settings - about phone - know what you are doing. Now, go get your firmware. Have you enabled developer mode? Debugging....
This guide is for Linux people.
Fire-up a terminal
sudo apt-get install android-tools-adb android-tools-fastboot
Reboot your phone to bootloader and plug your phone into your computer.
IN your terminal cd into the extracted firmware directory, run:
Code:
fastboot devices
You see a number returned? Good, proceed.
Let's put a copy of the boot.img into an archive right now because magisk will need it later (to spit a file out that you won't be able to find....baaaa ha ha haaaaa).
Code:
tar -cvf bootimg.tar boot.img
Flash it....run each line, or, make a script:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0 && fastboot flash super super.img_sparsechunk.1 && fastboot flash super super.img_sparsechunk.2 && fastboot flash super super.img_sparsechunk.3 && fastboot flash super super.img_sparsechunk.4 && fastboot flash super super.img_sparsechunk.5 && fastboot flash super super.img_sparsechunk.6 && fastboot flash super super.img_sparsechunk.7 && fastboot flash super super.img_sparsechunk.8 && fastboot flash super super.img_sparsechunk.9 && fastboot flash super super.img_sparsechunk.10 && fastboot flash super super.img_sparsechunk.11 && fastboot flash super super.img_sparsechunk.12 && fastboot flash super super.img_sparsechunk.13 && fastboot flash super super.img_sparsechunk.14 && fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Your phone will reboot into initial setup. Set it up. Cool, have fun with your phone, I guess. If you want root, read on. Don't take the 11 update. Sheesh!
Stop.
Do you really want root? Why are you rooting? For viper? Pffft. Rooting has trade-offs and you don't get to ***** about it later, fool; ain't nobody twisting your arm. You really want to root, 'cause you're ready.
Root is a sexy-fine chunk of plump lovin', awwwww, man. Just back it up one time, oh yeah, that's right.....but, **** comes out of it! Big smile, high-five. Welcome to the show.
That's right. THat's root. There's risk. You want root? Because the phone isn't yours until you have it. In fact it's actively working against you until you do. Let's go ahead and get root. You can handle a little ****, right? I mean, potentially.
Copy that bootimg.tar archive you made earlier onto your phone. Go get the magisk apk and install it.
Go enable developer mode on your phone. Enable usb debugging.
In magisk -
top section, top choice - touch the word: install. Touch it! Choose: select and patch file. Obviously.
Now is when you need that archive - you just copied it onto your phone, show magisk where it is.
Magisk will output a new boot image so you can root. Wicked. Go find it on your phone - it's not hiding. Where do apps put data on your phone? Copy that file to your computer.
Now - in orter to flash this new boot image file to your phone you must be in fastbootd. Take a breath. Reboot your phone into the stock recovery - just hold down power and voldwn for about 11 seconds - you should be at 'start'. Go into recovery.
Stock recovery is a barren wasteland of nothing - right on, let's go into fastbootd.
hold down the power button for 3 seconds, one onethousand, two one thousand....after 3 one thousand press the volup key as well - keep holding the power button down. after 5 one thousand, release the buttons. You should see a new menu. IF you don't, repeat the process until you do. THis is how, get it to work.
In the menu, voldwn to enter fastboot. It does not say fastbootd, but, it is. Choose it, and voila - you are now in fastbootd and in this screen it tells you as much.
ON your computer flash the new boot image:
Code:
fastboot flash boot NEWIMAGE.IMG
After, type:
Code:
fastboot reboot
When your phone boots up, it may loop for a few minutes or loop at the next reboot - go finish setting up magisk.
You are rooted.
Lemme ask you something - why are you rooting stock? If you want root then you want control - if you want control you know you aren't going to get it from stock - there's a ton of stuff going on there. Why not install a custom rom? Just food for thought. I root stock on my g power and run lineage on my edge, also rooted. I don't normally use my g power, though.
I hope my biting cynicism and step-by-step account of flashing firmware and rooting your shiny new g power is helpful. I'm not your dad - I could care less if you brick your phone. Don't cry to me if it doesn't work, because this does. It's a flick of the wrist, but, it's not for everybody. It's especially not for people, maybe like you, that hear a new thing and wanna jump right on it. Nobody in the world cares at all if you break your phone. Nobody is forcing you to do this, nobody forced you to buy this phone, to step left instead of right, to like red better than blue - it's all you. Own that because it's beautiful.
Click to expand...
Click to collapse
How about flashing it upgraded to Android 11?

When the 11 firmware becomes available I'll do the exact same thing. Wouldn't you?

What I meant is: how is flashing LineageOS 17 on Moto G8 Power which was upgraded to Android 11. The guide states it works for Android 10. If downgrade from 11 to 10 is a must, in order to successfully flashing LO17 then what's the best way of doing it? LMSA only downloads the latest version of Android.

alpheus said:
What I meant is: how is flashing LineageOS 17 on Moto G8 Power which was upgraded to Android 11. The guide states it works for Android 10. If downgrade from 11 to 10 is a must, in order to successfully flashing LO17 then what's the best way of doing it? LMSA only downloads the latest version of Android.
Click to expand...
Click to collapse
OK, so, this is my 5th or so edit. Heh. You took the update to 11 and now you want lineageos? Right on, Lineage lets you breathe a little easier, sho' nuff. This phone is probably not popular enough for 18.1 to ever see it, which is built on android 11. Back when android 7 came out, on my phone then, it was a new modem and that changed all the things. It was a pain in the ass to go back to 6 and 7 with custom roms was a matter of either having your cake or eating it, too. And right now you're at 11 wanting that sweet sweet Lineage....I get it.
I might just root 11 and see what I could do with it afore I flashed 10 back onto it. That's me, I like to tinker, and can be ok with a decision, because old and no fuks...You might be in a hurry, I dunno...root it. get with sd maid and appmanager, a firewall, do your thing...fx for a file manager is mui bueno - you can do a lot with root to the stock rom motorola gives you - still, there's a ton of google all over it, even after shutting things down, removing, blocking, et al...
Flash 10 - go ahead. Do it. DO it now. Flash 10 and then do the lineage thing, I hear you. Go get and do it. It won't take long and you'll be happy. Rock on. Sure, I would do it. Why the hell not?

nevermind

bronkish said:
OK, so, this is my 5th or so edit. Heh. You took the update to 11 and now you want lineageos? Right on, Lineage lets you breathe a little easier, sho' nuff. This phone is probably not popular enough for 18.1 to ever see it, which is built on android 11. Back when android 7 came out, on my phone then, it was a new modem and that changed all the things. It was a pain in the ass to go back to 6 and 7 with custom roms was a matter of either having your cake or eating it, too. And right now you're at 11 wanting that sweet sweet Lineage....I get it.
I might just root 11 and see what I could do with it afore I flashed 10 back onto it. That's me, I like to tinker, and can be ok with a decision, because old and no fuks...You might be in a hurry, I dunno...root it. get with sd maid and appmanager, a firewall, do your thing...fx for a file manager is mui bueno - you can do a lot with root to the stock rom motorola gives you - still, there's a ton of google all over it, even after shutting things down, removing, blocking, et al...
Flash 10 - go ahead. Do it. DO it now. Flash 10 and then do the lineage thing, I hear you. Go get and do it. It won't take long and you'll be happy. Rock on. Sure, I would do it. Why the hell not?
Click to expand...
Click to collapse
Hey, thanks for the reply. Yes, rooting G Power is not my interest, Id rather flash LineageOS without any Gapps and fu....g shmuggle. Would you please point out the best way to flash previous Stock 10 on G Power with current 11 installed? The phone was upgraded to 11 when I got it.

See post #10. Just flash 10 ☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠, and then flash lineage 17.1. DOn't forget to flash copy-partitions before lineage. You gotta do it the 1st time you flash a custom rom over stock.
☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠
Lineage is not official for this phone.
☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠
☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠
☠☠☠☠ **DOOM AND GLOOM** **WARNING** **DOOM AND GLOOM** ☠☠☠☠

Hello guys does anyone know how I can get back to stock??? It seems whenever I reboot I keep getting bootloader with the dead android. I tried connecting my device to my laptop and using LMSA. I get a message saying the firmware doesn't match even though I input the right IMEI. Even after putting in the correct model of the phone. Any solution? I would really love to go back to stock. Thanks guys

Mkami said:
Hello guys does anyone know how I can get back to stock??? It seems whenever I reboot I keep getting bootloader with the dead android. I tried connecting my device to my laptop and using LMSA. I get a message saying the firmware doesn't match even though I input the right IMEI. Even after putting in the correct model of the phone. Any solution? I would really love to go back to stock. Thanks guys
Click to expand...
Click to collapse
Is your bootloader unlocked?
You can download the stock firmware from: https://mirrors.lolinet.com/firmware/moto/
Once you've downloaded the files you need just install them using ADB Platform Tools on Windows: https://developer.android.com/studio/releases/platform-tools
Also, if you can't even get it to boot to unlock the bootloader then I would download the firmware from the above lolinet site and then transfer the folder into LMSA on Windows under this path:
C:\ProgramData\LMSA\Download\RomFiles
You'll need to enable hidden items under the view tab in File explorer
Once you've moved the correct firmware into the RomFiles folder then go back to LMSA and have it check for the firmware and it will recognize the firmware you moved into RomFiles.

shylonite said:
Is your bootloader unlocked?
You can download the stock firmware from: https://mirrors.lolinet.com/firmware/moto/
Once you've downloaded the files you need just install them using ADB Platform Tools on Windows: https://developer.android.com/studio/releases/platform-tools
Also, if you can't even get it to boot to unlock the bootloader then I would download the firmware from the above lolinet site and then transfer the folder into LMSA on Windows under this path:
C:\ProgramData\LMSA\Download\RomFiles
You'll need to enable hidden items under the view tab in File explorer
Once you've moved the correct firmware into the RomFiles folder then go back to LMSA and have it check for the firmware and it will recognize the firmware you moved into RomFiles.
Click to expand...
Click to collapse
Thanks so much for your information! My phone is back to its originally stock and working 100%