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
Android devices can have different designs, so there is no generic command or set of instructions for flashing a GSI to apply to all devices. Specially for Xperias am i writing this Guides for You. So please read carefully...
1. Ensure that You have the following before You start:
Latest Fastboot Version (Or the used fastboot commands may not work)
A Method for disabling Android Verified Boot (Part of the Guide)
An unlocked Bootloader State (Official Instructions HERE)
To Start:
Download the Basic Package from Google: https://developer.android.com/topic/generic-system-image/releases
Download the AOSP Vendor Package from Sony: https://developer.sony.com/develop/open-devices/downloads/software-binaries
Open up the Zip Files and place the 3 included Images on Your fastboot destination
Boot Your Device into Fastboot:
Code:
Turn off Your Device and hold VolumeUP while connecting via USB to a PC or use ADB to reboot to fastboot
Disable the verified booting (AVB) by flashing vbmeta.img:
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Flash the Vendor to the Primary A Slot OEM:
Code:
fastboot flash oem_a nameofthesonyoemimage.img
Repeat to flash to the B Slot OEM
Code:
fastboot flash oem_b nameofthesonyoemimage.img
Flash the GSI to the Primary A Slot System:
Code:
fastboot flash system_a system.img
Repeat to flash to the B Slot System
Code:
fastboot flash system_b system.img
Wipe the user data and clear the data from other necessary partitions (for example, user data and system partitions):
Code:
fastboot -w
Reboot:
Code:
fastboot reboot
Additional:
You can use any Android 9+ GSI out of the XDA Forum here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
To get Magisk/Root; just patch Your actual Kernel with the Magisk Manager App and flash the Boot Image together with the GSI (Example below)
Patched Boot Image for Xperia 5 Users: https://forum.xda-developers.com/xp...isk-v20-3-patched-boot-image-android-t4033547
Hi,
A few things
Why flash all on both slots? Not needed
Why flash OEM? Not needed, android 10 GSI work with stock vendor.
niaboc79 said:
Hi,
A few things
Why flash all on both slots? Not needed
Why flash OEM? Not needed, android 10 GSI work with stock vendor.
Click to expand...
Click to collapse
After testing with Magisk have i faced that A only flashing ends up in softbricked devices since it can't boot into the second Slot. Fastboot will tell You what it does flash over the output. You can also erase one slot without touching the other like that. there are A Only ROMs that can be used like that but in case of A/B ROMs should we flash to both Slots.
Flashing the AOSP Vendor prepares the device for all Kinds of GSIs. In case of people like me who have just a Linux PC to use, will it be helpful to be also able to run AOSP from Scratch. Just My 2 Cents after using different machines and devices ofter the time... The AOSP Vendor does also not have any disadvantages in any view on GSIs and NewFlasher will flash stock fully anyways and reverts that if wanted.
BR
Miustone said:
After testing with Magisk have i faced that A only flashing ends up in softbricked devices since it can't boot into the second Slot. Fastboot will tell You what it does flash over the output. You can also erase one slot without touching the other like that. there are A Only ROMs that can be used like that but in case of A/B ROMs should we flash to both Slots.
Flashing the AOSP Vendor prepares the device for all Kinds of GSIs. In case of people like me who have just a Linux PC to use, will it be helpful to be also able to run AOSP from Scratch. Just My 2 Cents after using different machines and devices ofter the time... The AOSP Vendor does also not have any disadvantages in any view on GSIs and NewFlasher will flash stock fully anyways and reverts that if wanted.
BR
Click to expand...
Click to collapse
Sure but stock vendor give better results with wireless charging and fingerprint.
Thanks for your the explanations ?
niaboc79 said:
Sure but stock vendor give better results with wireless charging and fingerprint.
Thanks for your the explanations
Click to expand...
Click to collapse
Nice to know! Fingerprints are the worst on Xperia 1 and 5. Hope it will be better on the Mark 2...
Just made an Overlay over Night for GSIs, after experimenting around with them again. Finally got some essential Features working like AoD. Still missing is VoLTE and wifi calling which is a common Android 10 GSI bug i think. Double Touch to work does also not work on My Xperia 5 (Dunno why).
Thread; https://forum.xda-developers.com/xp...eriment-mars-vendor-overlay-gsi-roms-t4128449
which AOSP Vendor Package from Sony can be use on xperia 1 ii
I was wondering, is this device Xperia 1ii is able to recieved GSI 13?
I have the previous model Xperia 1 running GSI 13 really well, and was wondering if this device is similar to do the same?
Kind of a dumb question, because I would assume yes?... But would like to know just the same, as I saw a bargain price for a new Xperia 1ii, and hoping it to be similar.
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%
fastbootd flashing of LOS is not working for me. NOTE: *"fastbootd"* process not fastboot. I'm trying an unofficial LOS on an Android10 device (Moto G8 Power) that evidently requires fastbootd. An informed XDA member kindly linked to the official doc on this new stuff ... but I'm too n00b to post Google's doc here.
I _can_ actually boot the phone into fastbootd -- using a command below -- and the splash screen says in BIG red letters "fastbootd", but right after the reboot, my USB connection is lost, and the rest of the fastboot commands return "< waiting for any device>"
This command reboots and displays "fastbootd":
Code:
$ sudo adb reboot fastboot
Everyone suggests downloading latest ADB & flashboot binaries ... OK, I'll bite: what version are you running that works? Below is my version and it is newer that what others have downloaded (I saw v29.x being suggested on XDA).
Code:
$ fastboot --version
fastboot version 30.0.4
Installed as /usr/bin/fastboot
$ adb --version
Android Debug Bridge version 1.0.41
Version 30.0.4
Installed as /usr/bin/adb
What is the sequence folks use for devices needing this new fastbootd process? Perhaps the dev for this unofficial LOS overlooked doc'ing a step that isn't obvious to me.
BTW: if I reboot into the regular bootloader, my adb stays connected to the phone. I learned this hard way while trying to troubleshoot ... while in the regular bootloader, I accidentally started a $ fastboot flash boot boot.img, and it started flashing! Luckily the phone immediately rejected it, rebooted into system recovery, and I got back into Android10.
vap0rtranz said:
fastbootd flashing of LOS is not working for me. NOTE: *"fastbootd"* process not fastboot. I'm trying an unofficial LOS on an Android10 device (Moto G8 Power) that evidently requires fastbootd. An informed XDA member kindly linked to the official doc on this new stuff ... but I'm too n00b to post Google's doc here.
I _can_ actually boot the phone into fastbootd -- using a command below -- and the splash screen says in BIG red letters "fastbootd", but right after the reboot, my USB connection is lost, and the rest of the fastboot commands return "< waiting for any device>"
This command reboots and displays "fastbootd":
Everyone suggests downloading latest ADB & flashboot binaries ... OK, I'll bite: what version are you running that works? Below is my version and it is newer that what others have downloaded (I saw v29.x being suggested on XDA).
What is the sequence folks use for devices needing this new fastbootd process? Perhaps the dev for this unofficial LOS overlooked doc'ing a step that isn't obvious to me.
BTW: if I reboot into the regular bootloader, my adb stays connected to the phone. I learned this hard way while trying to troubleshoot ... while in the regular bootloader, I accidentally started a $ fastboot flash boot boot.img, and it started flashing! Luckily the phone immediately rejected it, rebooted into system recovery, and I got back into Android10.
Click to expand...
Click to collapse
Make sure, this is really your device
https://forum.xda-developers.com/moto-g8/development/rom-lineageos-17-1-t4163021
kurtn said:
Make sure, this is really your device
https://forum.xda-developers.com/moto-g8/development/rom-lineageos-17-1-t4163021
Click to expand...
Click to collapse
No, I'm using the doc that is for the Moto G8 Power (the URL ends with 4163275 not 4163021). I could see how this could be easily confused b/c of Moto's branding and both are from the same Dev.
Both require fastbootd so at this point it should not matter until I get to the actual .img's.
Jp