Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
HOW TO FLASH
This version is only for not branded devices
Download the zip;
Unpack the zip in a folder;
Reboot the OnePlus 7 in fastboot mode (Power and volume + and volume-);
Connect the OnePlus 7 to PC;
Run flash-all.bat flasher you need;
Wait until the process end;
The phone will automatically reboot.
FLASHER ADVANCED GUIDE
flash-all-partitions-fastboot.bat : this .bat will flash all possible partitions through fastboot (Except persist) , there are some criticals partitions that can't be flashed through fastboot;
flash-only-persist.bat : this .bat will flash only persist partition in fastboot mode (This is good for people that have problems with sensor);
flash-all-partitions-recovery-criticals.bat : this .bat will boot the twrp and will flash criticals partitions, use this carefully;
flash-system-boot-vendor.bat : this .bat is the same of older flash-all.bat and so it will flash only vendor, system and boot;
flash-all-partitions.bat : this .bat will run flash-all-partitions-fastboot.bat , then flash-only-persist.bat and then flash-all-partitions-recovery-criticals.bat .
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
DOWNLOAD
All roms on AFH: https://www.androidfilehost.com/?w=files&flid=295200
All roms on Sourceforge: https://sourceforge.net/projects/fastbootroms/files/OnePlus 7
BRANDED PHONE
For now branded device are not supported
MANUAL FLASH: Windows - OSX - Linux
If you want to manual flash these roms these are the commands (you need to extract images.zip before proceed)
Fastboot Partitions:
Code:
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash oem_stanvbk oem_stanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash storsec_a storsec.img
fastboot flash storsec_b storsec.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash LOGO_a LOGO.img
fastboot flash LOGO_b LOGO.img
If you need also persist partition, this is the command:
Code:
fastboot flash persist persist.img
Criticals Partitions, for these you need to boot the TWRP:
Code:
fastboot boot TWRP.img
When you are in TWRP you need to run these commands to push and flash all criticals partitions:
Code:
adb push abl.img /sdcard/abl.img
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_a
adb shell dd if=/sdcard/abl.img of=/dev/block/bootdevice/by-name/abl_b
adb push cmnlib.img /sdcard/cmnlib.img
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_a
adb shell dd if=/sdcard/cmnlib.img of=/dev/block/bootdevice/by-name/cmnlib_b
adb push cmnlib64.img /sdcard/cmnlib64.img
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_a
adb shell dd if=/sdcard/cmnlib64.img of=/dev/block/bootdevice/by-name/cmnlib64_b
adb push devcfg.img /sdcard/devcfg.img
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_a
adb shell dd if=/sdcard/devcfg.img of=/dev/block/bootdevice/by-name/devcfg_b
adb push hyp.img /sdcard/hyp.img
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_a
adb shell dd if=/sdcard/hyp.img of=/dev/block/bootdevice/by-name/hyp_b
adb push keymaster.img /sdcard/keymaster.img
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_a
adb shell dd if=/sdcard/keymaster.img of=/dev/block/bootdevice/by-name/keymaster_b
adb push xbl.img /sdcard/xbl.img
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_a
adb shell dd if=/sdcard/xbl.img of=/dev/block/bootdevice/by-name/xbl_b
adb push xbl_config.img /sdcard/xbl_config.img
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_a
adb shell dd if=/sdcard/xbl_config.img of=/dev/block/bootdevice/by-name/xbl_config_b
adb push odm.img /sdcard/odm.img
adb shell dd if=/sdcard/odm.img of=/dev/block/bootdevice/by-name/odm_a
adb shell dd if=/sdcard/odm_config.img of=/dev/block/bootdevice/by-name/odm_b
adb push tz.img /sdcard/tz.img
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_a
adb shell dd if=/sdcard/tz.img of=/dev/block/bootdevice/by-name/tz_b
REMEMBER
"Invalid sparce file format at header magic" is not an error, you need to wait a bit when you see that string, just wait.
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.
If you want to rebrand your phone from HydrogenOS to OxygenOS you can follow this guide: Rebrand Guide
If you want you can use also my tool to flash Factory Images, unlock bootloader, flash twrp or to understand if the device is recognized: https://toolaio.tk/
Thanks to @SaiBork for first time tested
If you got some problems like write error or no partition, check this: https://forum.xda-developers.com/showpost.php?p=76658555&postcount=34
DONATE LINK
If you want to support this and others my projects please consider making a donation, thanks.
What does branded devices mean?
What about locking the bootloader. I noticed recovery image is not included
Recovery is a part of the boot image for A/B devices such as Oneplus 7.
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
arvindgr said:
What does branded devices mean?
Click to expand...
Click to collapse
Branded device means it is customized by mobile service provider, such as T Mobile.
any way to flash this without erasing data
Dragonlord07 said:
any way to flash this without erasing data
Click to expand...
Click to collapse
There were multiple scripts included in the zip
Just Be sure to flash the script that does not include -w fastboot parameter
Also, @mauronofrio My phone was originally GM57AA, but since stock image is of GM57BA my phone become GM57BA. Any ideas on how to go back to GM57AA...?
Dragonlord07 said:
any way to flash this without erasing data
Click to expand...
Click to collapse
Just remove -w from the script
arvindgr said:
There were multiple scripts included in the zip
Just Be sure to flash the script that does not include -w fastboot parameter
Also, @mauronofrio My phone was originally GM57AA, but since stock image is of GM57BA my phone become GM57BA. Any ideas on how to go back to GM57AA...?
Click to expand...
Click to collapse
Just flash the GM57AA rom, there are boths in the link you can find in the first post
Ismael034 said:
What about locking the bootloader. I noticed recovery image is not included
Click to expand...
Click to collapse
Hello, I have sent you a message regarding this message. a greeting.
Stuck at boot animation. Is there a way to make it do it's thing on both slots?
fusk said:
Stuck at boot animation. Is there a way to make it do it's thing on both slots?
Click to expand...
Click to collapse
Go in stock recovery, go to wipe data, check also internal storage and wipe it, then it should work.
mauronofrio said:
Go in stock recovery, go to wipe data, check also internal storage and wipe it, then it should work.
Click to expand...
Click to collapse
There is 3 options. Reset system settings, wipe cache & erase everything. There does not appear to be an option to "wipe data" like it would say in twrp or check internal storage. I erased everything and restarted the process, hope that was what you meant.
---------- Post added at 19:23 ---------- Previous post was at 19:15 ----------
That worked, now my question is. The reason i was doing this was because slot B was unable to mount storage, slot A worked fine and phone worked fine. Would this process fix the issue i had with slot B?
fusk said:
There is 3 options. Reset system settings, wipe cache & erase everything. There does not appear to be an option to "wipe data" like it would say in twrp or check internal storage. I erased everything and restarted the process, hope that was what you meant.
---------- Post added at 19:23 ---------- Previous post was at 19:15 ----------
That worked, now my question is. The reason i was doing this was because slot B was unable to mount storage, slot A worked fine and phone worked fine. Would this process fix the issue i had with slot B?
Click to expand...
Click to collapse
if in the slots you have different roms with different security patches only the recent slot will be able to boot. In the .bat there is a command to wipe data, but i don't know why it doesn't work on the oneplus 7 pro
mauronofrio said:
if in the slots you have different roms with different security patches only the recent slot will be able to boot. In the .bat there is a command to wipe data, but i don't know why it doesn't work on the oneplus 7 pro
Click to expand...
Click to collapse
I don't have a 1+7p, so i wouldn't know anything about that. Phone was 9.5.5 when i got it, updated to 9.5.6 with some problems. Wanted to update to 9.5.7 which was unsuccessful. When loading slot B in twrp it could not mount storage or sdcard. Looking at cmd while running your tool, it looks like it's only working with slot A and not touching slot B at any point.
---------- Post added at 19:48 ---------- Previous post was at 19:28 ----------
Appears it worked, can now boot both slots and mount storage and sdcard on both. Thanks for the assist.
fusk said:
I don't have a 1+7p, so i wouldn't know anything about that. Phone was 9.5.5 when i got it, updated to 9.5.6 with some problems. Wanted to update to 9.5.7 which was unsuccessful. When loading slot B in twrp it could not mount storage or sdcard. Looking at cmd while running your tool, it looks like it's only working with slot A and not touching slot B at any point.
---------- Post added at 19:48 ---------- Previous post was at 19:28 ----------
Appears it worked, can now boot both slots and mount storage and sdcard on both. Thanks for the assist.
Click to expand...
Click to collapse
Hello friend, can you say how you did it in the end so that the two slots (A and B) will work? Thank you. Was it because you had encrypted memory and did not let mount slot B? What did you do? Thanks greetings.
mauronofrio said:
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock or twrp) because is no more needed. The updates will be done on the slot not used for example if you are using slot a the update will be installed on slot b and the slot b will be set as default. If you brick and you are in bootloop how you can restore the rom? You can't with Stock ROM you have, because the zip can be only installed via Update Engine, so what can you do? Flash a stock rom via fastboot. I have extracted all images from the stock zip and i have made a new zip with the Fastboot ROM with a flash-all.bat included. This will work only if your bootloader is unlocked. This will erase all your data and will wipe your internal storage.
Click to expand...
Click to collapse
@mauronofrio Hello friend, thanks for your work, I want to ask you if these files to put a rom by fastboot are valid for my version of OnePlus 7 (not pro) Chinese version Gm1900?
Another question I have is, my oneplus 7 gm1900 came with the AA version and I manually added the BA version locally for local improvement. If this fastboot method works, could I put the BA or do I have to put the AA files first?
Thank you.
tURkOsANsE said:
Hello friend, can you say how you did it in the end so that the two slots (A and B) will work? Thank you. Was it because you had encrypted memory and did not let mount slot B? What did you do? Thanks greetings.
Click to expand...
Click to collapse
I did as mentioned. When the .bat failed, i entered "Go in stock recovery" and choose "erase everything" and then ran the .bat again and it worked. I had encryption on both, so that was not the issue. It's fixed now.
fusk said:
I did as mentioned. When the .bat failed, i entered "Go in stock recovery" and choose "erase everything" and then ran the .bat again and it worked. I had encryption on both, so that was not the issue. It's fixed now.
Click to expand...
Click to collapse
Thank you for answering friend, what version do you have of OnePlus 7? Do you have the Chinese version Gm1900 ?.
Before putting the rom by fastboot did you have Twrp installed?
mauronofrio said:
if in the slots you have different roms with different security patches only the recent slot will be able to boot. In the .bat there is a command to wipe data, but i don't know why it doesn't work on the oneplus 7 pro
Click to expand...
Click to collapse
Hello friend, thanks for your work, I want to ask you if these files to put a rom by fastboot are valid for my version of OnePlus 7 (not pro) Chinese version Gm1900?
Another question I have is, my oneplus 7 gm1900 came with the AA version and I manually added the BA version locally for local improvement. If this fastboot method works, could I put the BA or do I have to put the AA files first?
Thank you.
tURkOsANsE said:
Hello friend, thanks for your work, I want to ask you if these files to put a rom by fastboot are valid for my version of OnePlus 7 (not pro) Chinese version Gm1900?
Another question I have is, my oneplus 7 gm1900 came with the AA version and I manually added the BA version locally for local improvement. If this fastboot method works, could I put the BA or do I have to put the AA files first?
Thank you.
Click to expand...
Click to collapse
Yes it will work on the oneplus 7, there are 2 different thread for the fastboot roms this one is for oneplus 7 only. AA or BA there are not a lot of.differences, just use the one you prefer.
I accidentally made a mistake, flash custom kernel when my phone has custom kernel installed. Now every time i'm trying to boot up, my phone is only able to boot on fastboot mode, no recovery and i unable to install recovery too (stock/custom).
I wonder, is this method can save my phone?
Thank you.
cakriez92 said:
I accidentally made a mistake, flash custom kernel when my phone has custom kernel installed. Now every time i'm trying to boot up, my phone is only able to boot on fastboot mode, no recovery and i unable to install recovery too (stock/custom).
I wonder, is this method can save my phone?
Thank you.
Click to expand...
Click to collapse
Yes
Related
If you are not able to boot a patched boot image or a twrp image on Android 10, here is a workadound.
Machi007 said:
Boot TWRP and images is possible also on Android 10, but it needs some workaround...
1) Turn phone into Download Mode
2) Use command fastboot flash recovery twrp.img where twrp.img is your TWRP image you want to boot up
It shows this error (it is OKAY):
Code:
FAILED (remote: '(recovery_a) No such partition') //This is because an A/B Device does not have a recovery partition. It's located in the boot partition itself.
3) Now you can boot your TWRP recovery image, for example: fastboot boot twrp.img
Click to expand...
Click to collapse
Hay Guys!
One of the most important things on Android is to make backups. Every time you want to root or flash something, make backups!
I saw many people struggling with OTA because they didn't make backups to restore there images.
=========================================================================
If you DONT have any backup, but you want to restore stock, I'll upload all my stock backups as well as all patched boot images in this mega:
https://mega.nz/#F!52B0HCID!A1k8PiGn9OQbiEa_IJ3_EQ
This is just in case something went wrong with you backup. You should still make your own backups!!!
=========================================================================
In this post I will show you how to create a backup and how to restore it.
There are 2 ways to backup your Phone images.
TWRP:
Reboot ur phone into bootloader
You can do this via adb
Code:
adb reboot bootloader
You can do this by holding volume down + power button while your phone is connected to USB.
Boot into TWRP. you can use the TWRP image from my mega. DO NOT FLASH IT!!!
Code:
fastboot boot twrp.img
Hit the Backup button and backup boot image, system image and vendor image.
If you want to restore this images, you can restore them with TWRP. Just hit the restore button.
This may not work for all Devices. But you can flash the images via fastboot too.
The fastboot files looks like boot.emmc.win. Dont worry, this is img file. So you can rename it to boot.img or something.
ADB:
1Reboot ur phone into bootloader
You can do this via adb
Code:
adb reboot bootloader
You can do this by holding volume down + power button while your phone is connected to USB.
Find out your current slot
Code:
fastboot getvar current-slot
Boot into a patched boot image.
Code:
fastboot boot patched.img
Your phone shoud boot up. If it does,
then open ADB.
In ADB type there commands to dump the images.
Get root access by typing the "su"
Dump your boot, system and vendor from your current slot you found out on step 2
(The commands for dumping an image are below)
If you want to restore this images, you can restore them via fastboot.
Code:
fastboot flash [boot_{current-slot}/system_{current-slot}/vendor_{current-slot}] <image file>
Replace the {current-slot} with your current slot.
Example:
Current slot is a and you want to restore the boot image.
Code:
fastboot flash boot_a boot_a.img
If you still have Questions or need help, feel free to pm me.
Also you can leave a comment under this post.
Commands for dumping images:
#Backup A boot:
Code:
dd if=/dev/block/mmcblk0p52 of=/sdcard/boot_a.img
#Backup B boot:
Code:
dd if=/dev/block/mmcblk0p53 of=/sdcard/boot_b.img
#Backup A vendor:
Code:
dd if=/dev/block/mmcblk0p83 of=/sdcard/vendor_a.img
#Backup B vendor:
Code:
dd if=/dev/block/mmcblk0p84 of=/sdcard/vendor_b.img
#Backup A system:
Code:
dd if=/dev/block/mmcblk0p81 of=/sdcard/system_a.img
#Backup B system:
Code:
dd if=/dev/block/mmcblk0p82 of=/sdcard/system_b.img
Great tutorial and much appreciated. On the first sentence... There is a typo on the word "thinks".. it should be "things".
Danny1976 said:
Great tutorial and much appreciated. On the first sentence... There is a typo on the word "thinks".. it should be "things".
Click to expand...
Click to collapse
Thanks. fixed it :good:
Hail brother! Tnx!
might have shot the capability of OTA on experimenting with TWRP and it's possibilites of taking backups.
thought, I was careful, but wasn't enough.
so THANKS a lot for providing all the information and (of course) : the sp1 images.
January stock and patched images is now uploaded.
Hi! I have a Problem with the wifi not working after flashing back stock boot.img on slot a & b....if anyone could help I'll be grateful.
emicloud91 said:
Hi! I have a Problem with the wifi not working after flashing back stock boot.img on slot a & b....if anyone could help I'll be grateful.
Click to expand...
Click to collapse
Did you flash your own backups?
Do you have global 6.1?
Also, why did you flash A AND B?
¥sBielefeld said:
Hay Guys!
One of the most important things on Android is to make backups. Every time you want to root or flash something, make backups!
I saw many people struggling with OTA because they didn't make backups to restore there images.
=========================================================================
If you DONT have any backup, but you want to restore stock, I'll upload all my stock backups as well as all patched boot images in this mega:
https://mega.nz/#F!52B0HCID!A1k8PiGn9OQbiEa_IJ3_EQ
This is just in case something went wrong with you backup. You should still make your own backups!!!
=========================================================================
In this post I will show you how to create a backup and how to restore it.
There are 2 ways to backup your Phone images.
TWRP:
Reboot ur phone into bootloader
You can do this via adb
Code:
adb reboot bootloader
You can do this by holding volume down + power button while your phone is connected to USB.
Boot into TWRP. you can use the TWRP image from my mega. DO NOT FLASH IT!!!
Code:
fastboot boot twrp.img
Hit the Backup button and backup boot image, system image and vendor image.
If you want to restore this images, you can restore them with TWRP. Just hit the restore button.
This may not work for all Devices. But you can flash the images via fastboot too.
The fastboot files looks like boot.emmc.win. Dont worry, this is img file. So you can rename it to boot.img or something.
ADB:
1Reboot ur phone into bootloader
You can do this via adb
Code:
adb reboot bootloader
You can do this by holding volume down + power button while your phone is connected to USB.
Find out your current slot
Code:
fastboot getvar current-slot
Boot into a patched boot image.
Code:
fastboot boot patched.img
Your phone shoud boot up. If it does,
then open ADB.
In ADB type there commands to dump the images.
Get root access by typing the "su"
Dump your boot, system and vendor from your current slot you found out on step 2
(The commands for dumping an image are below)
If you want to restore this images, you can restore them via fastboot.
Code:
fastboot flash [boot_{current-slot}/system_{current-slot}/vendor_{current-slot}] <image file>
Replace the {current-slot} with your current slot.
Example:
Current slot is a and you want to restore the boot image.
Code:
fastboot flash boot_a boot_a.img
If you still have Questions or need help, feel free to pm me.
Also you can leave a comment under this post.
Commands for dumping images:
#Backup A boot:
Code:
dd if=/dev/block/mmcblk0p52 of=/sdcard/boot_a.img
#Backup B boot:
Code:
dd if=/dev/block/mmcblk0p53 of=/sdcard/boot_b.img
#Backup A vendor:
Code:
dd if=/dev/block/mmcblk0p83 of=/sdcard/vendor_a.img
#Backup B vendor:
Code:
dd if=/dev/block/mmcblk0p84 of=/sdcard/vendor_b.img
#Backup A system:
Code:
dd if=/dev/block/mmcblk0p81 of=/sdcard/system_a.img
#Backup B system:
Code:
dd if=/dev/block/mmcblk0p82 of=/sdcard/system_b.img
Click to expand...
Click to collapse
Can these images be used for downgrade to oreo? I am on pie (ta1068), unrooted and loocked bootloader.
Windoors said:
Can these images be used for downgrade to oreo? I am on pie (ta1068), unrooted and loocked bootloader.
Click to expand...
Click to collapse
No i don't think so. I never tested it.
Anyway.. You are locked, so you need to downgrade to unlock bootloader. You can use NTool or visit this
¥sBielefeld said:
No i don't think so. I never tested it.
Anyway.. You are locked, so you need to downgrade to unlock bootloader. You can use NTool or visit this
Click to expand...
Click to collapse
How to do it with NTool?
JurreTas said:
How to do it with NTool?
Click to expand...
Click to collapse
You need to buy Ntool credits. Just google it
¥sBielefeld said:
No i don't think so. I never tested it.
Anyway.. You are locked, so you need to downgrade to unlock bootloader. You can use NTool or visit this
Click to expand...
Click to collapse
I heard in nokia 6.1 u don't need to downgrade to unlock bootloader (just change slot a to b).
Anyways, if I have already unlocked my bootloader can i downgrade to oreo without ntool? Thanks
Windoors said:
I heard in nokia 6.1 u don't need to downgrade to unlock bootloader (just change slot a to b).
Click to expand...
Click to collapse
Nokia changed the Bootloader unlock algorithm with the August patch. So you need to be pre August patch.
A B slots work work like this:
Start: A(June)B(June) Currentslot A -> OTA UPDATE -> A(June)B(July) Currentslot B -> OTA -> A(August)B(July) current slot A and so forth.
So. If you are on Slot A and you have Januar installed, you B slot is on December. This means, switching the Slot does not help you with the bootloader unlock.
You have to downgrade.
Windoors said:
Anyways, if I have already unlocked my bootloader can i downgrade to oreo without ntool? Thanks
Click to expand...
Click to collapse
Yes you can use OST LA for downgrade if you are unlocked. Make sure you are critical unlocked too.
Thanks for clarifying. I unfortunately updated to January patch.
March update just released (V3.51F) with 530 MegaByte...
This is not just a security update but a complete software update.
Waiting for your files @MEGA.
Do we have to flash more than boot, system and vendor?
Last time (with pie october patch) radio and some other files were updated!
Updated to march security patch.
klauer said:
March update just released (V3.51F) with 530 MegaByte...
This is not just a security update but a complete software update.
Waiting for your files @MEGA.
Do we have to flash more than boot, system and vendor?
Last time (with pie october patch) radio and some other files were updated!
Click to expand...
Click to collapse
Why do you want to flash more?`If you are rooted, flash stock boot image. If ur modified ur system, flash stock system.
If you are complete stock, install OTA
Btw. Stock images for march are online
Are your images from Global version ? I had issues updating to March OTA (said that some partitions were modified) so I flashed your boot.img and system.img, but I still cannot update.
Solannae said:
Are your images from Global version ? I had issues updating to March OTA (said that some partitions were modified) so I flashed your boot.img and system.img, but I still cannot update.
Click to expand...
Click to collapse
Yes, they are global. I hade this issue a few weeks ago too. I had to reflash my phone for some reason...
Tried All in One Tool a while ago, but after booting up after flash, and the flashing again it still flashed to partition b.
I forgot. I have done it. Flash with Tool All in One, flash TWRP, change partition in TWRP, reboot to fastboot and flash stock again with Tool All in One, and flash TWRP again.
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
andacro said:
I forgot. I have done it. Flash with All in One Tool, flash TWRP, change partition in TWRP, reboot and flash stock again with All in One Tool.
Click to expand...
Click to collapse
In future you can also run this command to change slot in fastboot, fastboot --set-active=a or fastboot --set-active=b depending which slot you need.
liam_davenport said:
In future you can also run this command to change slot in fastboot, fastboot --set-active=a or fastboot --set-active=b depending which slot you need.
Click to expand...
Click to collapse
Great! Thanks a lot
Hi guys. If you can't install ROMs, this is your place to ask. Please be detailed, mention: ROM, build, your variant and firmware version. And tell us your specific issue.
Here's a guide on how to do it, and I'll link you to the files needed for the procedure:
1. If you're using a Google account, remove it in Settings > Accounts and factory reset. Else, skip this step.
2. Unlock your bootloader following Motorola's instructions. Google it, it'll be easy to find and follow.
3. Download:
. Fastboot tools/Minimal ADB & Fastboot or your prefered fastboot program for PC.
. A firmware image for your variant
. ROM you want to install
. GApps (optional): http://opengapps.org/
. Magisk (optional): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And the next files:
TWRP (img) & TWRP installer (zip): https://androidfilehost.com/?w=files&flid=299042
copypartitions.zip: https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
You'll need an SD card to store the files needed for installing the ROM, since internal storage won't be usable temporarily.
4. Hold power + volume down until you reach bootloader (fastboot mode).
In your extracted firmware folder open a terminal and flash your firmware files with these commands:
----------------------------------------------------------------------
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 5
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.2
fastboot flash vendor_b vendor.img_sparsechunk.0
fastboot flash vendor_b vendor.img_sparsechunk.1
fastboot flash vendor_b vendor.img_sparsechunk.2
fastboot flash oem_a oem.img
fastboot flash oem_b oem.img
fastboot oem fb_mode_clear
fastboot reboot-bootloader
--------------------------------------------------------------------
Don't worry if any error message appears.
5. Place TWRP .img file into your fastboot folder, and do "fastboot boot TWRP.img" - replace TWRP with file's real name, but it should be the IMG file's name, not the zip file's name. With TWRP booted, now check if the screen actually responds. If it doesn't, just turn your phone off, get into fastboot mode again, and boot TWRP until it works.
6. With that solved, now just copy copypartitions.zip to your sdcard (called external_sd in your phone) and install it. Also copy to your external_sd, just to save time, your ROM and TWRP's installer. And Magisk or GApps if you'll need them.
7. Reboot to bootloader, and do "fastboot -w".
8. "fastboot boot" TWRP again, flash ROM, and flash TWRP's installer (zip file). Boot system.
9. Reboot to bootloader, select recovery mode and flash Magisk/GApps if you need them.
10. Reboot to system, and enjoy
Any questions, feel free to ask 'em in the comments. Hope it works!
P.S.: OmniROM has its own recovery (TWRP is a recovery). So, keep that in mind and don't flash TWRP's zip in Omni if you want it to boot.
Also, if you want, you can try OrangeFOX. It's a cute TWRP replacement that has some interesting features. Worth checking out.
TL;DR:
1. Remove your Google account
2. Flash firmware with the set of commands attached.
3. "Fastboot boot" TWRP and flash copypartitions.zip.
4. Go to bootloader mode and do "fastboot -w".
5. Boot TWRP, flash ROM and TWRP's installer
5.1. Boot system
(optional) 6. Open recovery mode and flash Magisk/GApps.
-----------------------------------------------------------------------------------
Download:
. Fastboot tools/Minimal ADB & Fastboot or your prefered fastboot program for PC.
. A firmware image for your variant
. ROM you want to install
. GApps (optional): http://opengapps.org/
. Magisk (optional): https://forum.xda-developers.com/app...mless-t3473445
. TWRP (img) & TWRP installer (zip): https://androidfilehost.com/?w=files&flid=299042
. copypartitions.zip: https://drive.google.com/file/d/1oir...t2eSGKt0F/view
You'll need an SD card to store the files needed for installing the ROM, since internal storage won't be usable temporarily.
All ROMs posted in XDA are actually working in this device.
Thank you for creating this thread. People need to get used to this A/B partition format. This is the proper forum to discuss these issues, not in the development section.
Using these instructions:
crDroid -> bootloop
bootleggers rom -> bootloop
lineageos -> bootloop
ressurection remix -> bootloop
Twrp is screaming at me "Failed to mount /data partition "invalid argument"
I noticed your instructions fail to mention you need to run through the setup process of android, then run fastboot -w, then run twrp format data as fastboot -w will (using retus and amz stock rom) create a "raw" partition table and so on. None of the current roms can handle this and will bootloop.
These incomplete instructions will waste people's time and cause problems.
Please reconsider the purpose of this thread. It is the developers responsibility to add a filesystem check during rom flash and write working instructions. Currently only bootleggers instructions will work to any capacity due to their inbuilt sanity checks.
derek12213 said:
Using these instructions:
crDroid -> bootloop
bootleggers rom -> bootloop
lineageos -> bootloop
ressurection remix -> bootloop
[...]
Click to expand...
Click to collapse
Hey. like I said at the beggining of the thread, it's not possible to help you without giving specifics. Give that info and I'll help you.
I made this thread because this steps worked to dozens of users, and I'm not joking. Literally. They are not incomplete since they worked for everyone. Search for our group in Telegram if you think it's not true. We might be able to help you there too.
TWRP screams "Failed to mount /data partition", that's why internal storage won't work temporarily until you flash a ROM. Could that be better? Of course. But still the procedure works.
"I noticed your instructions fail to mention you need to run through the setup process of..." Nope. There's no need for that. That's why I didn't mentioned it, because I've tried lots of ROMs and never needed to do that.
Also, do you have latest fastboot? Some users had issues because of using older versions of that program.
But yeah, I'm not some friend who can go to your house and see what you've got. So, we need information. I won't be able to help you further if you don't do your part. Tell me what you've got please.
Flash to stock -> fine
follow your instructions for any rom -> bootloop
from stock flashed metropcs rom per crDroid developers recomendation (I am amz fw)
flash all that commands using metropcs firmware (crDroid said to use this one, I am AMZ fw, tried AMZ fw and RETUS fw and it doesnt matter, same result)
fastboot boot twrp
twrp flash copy partitions
reboot bootloader
fastboot -w
boot twrp
flash rom flash twrp
reboot system
bootloop
output of twrp and fastboot during the process :
Erasing 'userdata' OKAY [ 0.117s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
install rom zip and twrp zip (downloaded your versions)
could not mount /data and unnable to find crypto footer
failed to mount /data invalid argument
unable to recreate /data/media folder
updating partition details...
failed to mount /data invalid argument
...done
unable to mount storage
failed to mount /data invalid arugment
Full selinux support is present
unable to mount /data/media/TWRP/.twrp
after flashing twrp says
Failed to mount /data invalid argument
...done
Your guide says " Boot system."
I am interpreting this as reboot system
Bootloop
All roms.
I dont install gapps because I dont need spyware. I would use stock if I wanted to be spyed on 24/7.365
I dont install magisk outside of booting a magisk patched boot img to modify hosts for less CONSTANT TRACKING
Hey, did you read my last reply, as well as the first line of this thread? Where I require specifically to give me some info first to be able to help you. I'm like trying to help a question mark... try to follow a simple rule.
In step 9, you're doing "fastboot boot" to TWRP, or you're actually going to recovery mode? We need to know if TWRP install actually works. Even if you won't use any Magisk or GApps, check if it is actually installed AND working.
I've also heard of users that had issues booting of the first time a ROM with TWRP installed. Maybe just do the procedure until you have to flash a ROM, and boot the system instead of installing TWRP. And flash TWRP after the ROM already booted and it's running.
Also, how much time should pass for you to consider for a ROM to be bootlooping?
Well, both fastboot -w and TWRP mount /data errors are the same thing. Fastboot isn't able to format it properly, so data is not mounted by TWRP. Like I said before, it's a temporal thing that's fixed when flashing the ROM. Don't worry about that.
But please, I don't know if you do this on purpose, you're not following even a simple request stated at the beggining of the thread. Please answer that to keep the conversation going, I won't reply you any further if you don't do your part.
derek12213 said:
Flash to stock -> fine
follow your instructions for any rom -> bootloop
from stock flashed metropcs rom per crDroid developers recomendation (I am amz fw)
flash all that commands using metropcs firmware (crDroid said to use this one, I am AMZ fw, tried AMZ fw and RETUS fw and it doesnt matter, same result)
fastboot boot twrp
twrp flash copy partitions
reboot bootloader
fastboot -w
boot twrp
flash rom flash twrp
reboot system
bootloop
output of twrp and fastboot during the process :
Erasing 'userdata' OKAY [ 0.117s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
install rom zip and twrp zip (downloaded your versions)
could not mount /data and unnable to find crypto footer
failed to mount /data invalid argument
unable to recreate /data/media folder
updating partition details...
failed to mount /data invalid argument
...done
unable to mount storage
failed to mount /data invalid arugment
Full selinux support is present
unable to mount /data/media/TWRP/.twrp
after flashing twrp says
Failed to mount /data invalid argument
...done
Your guide says " Boot system."
I am interpreting this as reboot system
Bootloop
All roms.
I dont install gapps because I dont need spyware. I would use stock if I wanted to be spyed on 24/7.365
I dont install magisk outside of booting a magisk patched boot img to modify hosts for less CONSTANT TRACKING
Click to expand...
Click to collapse
Dude, I had the same issue as you, couldn't load any roms, no matter what guide I followed, it always bootlooped. Turned out to be my microSD was causing it. I followed Life_goes_on's solution on this thread (post #74):
https://forum.xda-developers.com/g7-power/development/rom-resurrection-remix-t3994687/page8
Substituted 'fastboot erase userdata' for 'fastboot -w' and took out my microSD before booting it up and it worked.
I'm using the MetroPCS version on RETUS firmware.
BETA215 said:
Hey, did you read my last reply, as well as the first line of this thread? Where I require specifically to give me some info first to be able to help you. I'm like trying to help a question mark... try to follow a simple rule.
In step 9, you're doing "fastboot boot" to TWRP, or you're actually going to recovery mode? We need to know if TWRP install actually works. Even if you won't use any Magisk or GApps, check if it is actually installed AND working.
I've also heard of users that had issues booting of the first time a ROM with TWRP installed. Maybe just do the procedure until you have to flash a ROM, and boot the system instead of installing TWRP. And flash TWRP after the ROM already booted and it's running.
Also, how much time should pass for you to consider for a ROM to be bootlooping?
Well, both fastboot -w and TWRP mount /data errors are the same thing. Fastboot isn't able to format it properly, so data is not mounted by TWRP. Like I said before, it's a temporal thing that's fixed when flashing the ROM. Don't worry about that.
But please, I don't know if you do this on purpose, you're not following even a simple request stated at the beggining of the thread. Please answer that to keep the conversation going, I won't reply you any further if you don't do your part.
Click to expand...
Click to collapse
After i flash rom and twrp I can go to twrp by holding volume down and pwr then selecting recovery at that point or can boot it via fastboot. I think that it changes parition (from a to b) during this process so I always use twrp to reboot to recovery even if I am not flashing gapps or magisk to rule out problems.
---------- Post added at 12:38 AM ---------- Previous post was at 12:11 AM ----------
framila said:
Dude, I had the same issue as you, couldn't load any roms, no matter what guide I followed, it always bootlooped. Turned out to be my microSD was causing it. I followed Life_goes_on's solution on this thread (post #74):
https://forum.xda-developers.com/g7-power/development/rom-resurrection-remix-t3994687/page8
Substituted 'fastboot erase userdata' for 'fastboot -w' and took out my microSD before booting it up and it worked.
I'm using the MetroPCS version on RETUS firmware.
Click to expand...
Click to collapse
bootloop
Alright I figured it out. It was my sdcard. I did everything using the Dave Chappelle method and it fixed it.
Dave Chappelle method:
1- remove sd card. In fact just remove the whole tray.
2- go back to stock, boot it, do whatever you gotta do. There is a thread on how to go back to stock, follow those instructions, its beyond the scope of the Dave Chappelle method.
3- go to bootloader with vol+pwr held
get your copypartitions.zip, your rom.zip, and twrp.img and twrp.zip in a folder. I like sybers twrp mod but whatever use official doesnt matter.
fastboot boot twrp
wait 3 seconds
adb push copypartitions.zip /tmp/
go to twrp install and go up a level, click copypartitions.zip, and install it. /tmp/ is memory, our phone has enough ram to do this.
adb shell
cd /tmp/
rm copypartitions.zip
# you dont have to do above, but we dont want too much stuff in memory, rebooting SHOULD clear memory, but I havent used android extensively they may have windows hibernate thing or whatever.
exit
adb reboot bootloader
fastboot boot twrp.img
adb push rom.zip /tmp/
go to twrp install and go up a level, click rom.zip, and install it. /tmp/ is memory, our phone has enough ram to do this.
adb shell
cd /tmp/
rm rom.zip
exit
adb push twrp.zip /tmp/
go to twrp install and go up a level, click twrp.zip, and install it. /tmp/ is memory, our phone has enough ram to do this.
adb shell
cd /tmp/
rm twrp.zip
exit
twrp select reboot bootloader
wait a tic
fastboot erase userdata
select recovery and boot
alright so at this point I am good because I dont want gapps or magisk I am done. I would boot a modified boot partition once a month and install adaware hosts modifications, then reboot. I dont want to be walking around with root or google proprietary code. I would then select reboot, make sure slotb is selected, and reboot system.
If you want gapps, then you flash your gapps at this point. I discourage you from doing so and encourage microg for google maps or whatever google service you actually need. I also discourage the idea of walking around with "hot" root. Where you can grant an application root at any time. It is trivial to write an application that modifies what the screen is displaying to trick you into accidentally granting root permissions.
Great guide! We really needed one. Btw you don't necessarily need a SD card to install zips, you can install them directly from your computer by sideloading them with adb on twrp. You can do that by going into twrp, then to Advanced and press on ADB Sideload, now on adb type in: "adb sideload thezipyouwanttoinstall.zip" and twrp will start installing that zip.
BETA215 said:
Hi guys. If you can't install ROMs, this is your place to ask. Please be detailed, mention: ROM, build, your variant and firmware version. And tell us your specific issue.
Here's a guide on how to do it, and I'll link you to the files needed for the procedure:
1. If you're using a Google account, remove it in Settings > Accounts and factory reset. Else, skip this step.
2. Unlock your bootloader following Motorola's instructions. Google it, it'll be easy to find and follow.
3. Download:
. Fastboot tools/Minimal ADB & Fastboot or your prefered fastboot program for PC.
. A firmware image for your variant
. ROM you want to install
. GApps (optional): http://opengapps.org/
. Magisk (optional): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And the next files:
TWRP (img) & TWRP installer (zip): https://androidfilehost.com/?w=files&flid=299042
copypartitions.zip: https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view
You'll need an SD card to store the files needed for installing the ROM, since internal storage won't be usable temporarily.
4. Hold power + volume down until you reach bootloader (fastboot mode).
In your extracted firmware folder open a terminal and flash your firmware files with these commands:
----------------------------------------------------------------------
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot set_active a
fastboot reboot-bootloader
sleep 5
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
sleep 5
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.2
fastboot flash vendor_b vendor.img_sparsechunk.0
fastboot flash vendor_b vendor.img_sparsechunk.1
fastboot flash vendor_b vendor.img_sparsechunk.2
fastboot flash oem_a oem.img
fastboot flash oem_b oem.img
fastboot oem fb_mode_clear
fastboot reboot-bootloader
--------------------------------------------------------------------
Don't worry if any error message appears.
5. Place TWRP .img file into your fastboot folder, and do "fastboot boot TWRP.img" - replace TWRP with file's real name, but it should be the IMG file's name, not the zip file's name. With TWRP booted, now check if the screen actually responds. If it doesn't, just turn your phone off, get into fastboot mode again, and boot TWRP until it works.
6. With that solved, now just copy copypartitions.zip to your sdcard (called external_sd in your phone) and install it. Also copy to your external_sd, just to save time, your ROM and TWRP's installer. And Magisk or GApps if you'll need them.
7. Reboot to bootloader, and do "fastboot -w".
8. "fastboot boot" TWRP again, flash ROM, and flash TWRP's installer (zip file). Boot system.
9. Reboot to bootloader, select recovery mode and flash Magisk/GApps if you need them.
10. Reboot to system, and enjoy
Any questions, feel free to ask 'em in the comments. Hope it works!
P.S.: OmniROM has its own recovery (TWRP is a recovery). So, keep that in mind and don't flash TWRP's zip in Omni if you want it to boot.
Also, if you want, you can try OrangeFOX. It's a cute TWRP replacement that has some interesting features. Worth checking out.
Click to expand...
Click to collapse
Is there an orange Fox recovery for Moto G7 power?
Ljw4884 said:
Is there an orange Fox recovery for Moto G7 power?
Click to expand...
Click to collapse
Yes and it's absolutely amazing!
You can find it here
@BETA215, I see some folks mentioning bootloops. I personally had many many bootloops before I found out that TWRP/ ROM flashing on this device does not play nice with exFAT filesystem. maybe a note about that in the OP? formatting my SDcard to VFAT resolved all my issues, when it was ExFAT I couldn't get anything past the boot logo
I've just spent the past 10 days trying to root my phone and use a custom ROM working (and detecting SIM card and most important functions). But it's always problem after problem after problem and at this point, I'm ready to give up. I feel broken. I'm at the point where I'd literally pay someone to take control and do it for me. I just can't do it no matter how much I learn, always a new problem and now I'm stuck at this one and I just can't take it anymore. Swear to god, I will pay .
Deleted
SIM Card issue and no gapps?
Hi,
I installed Havoc OS on my moto g7 power XT1955-5, using these steps:
1) Switched off device
2) Volume down+Power to go in bootloader
3) CMD: fastboot erase userdata (maybe useless)
4) CMD: fastboot boot "C:\...\twrp.img" (or orangefox.img)
5) On Slot B mount "system" then wipe and format (maybe useless)
6) On Slot A mount "system" then wipe and format
7) Flash copy-partition-AB.zip
8) Flash Havoc ROM
9) Reboot -> Recovery
10) Flash GApps
11) Reboot -> Bootloader
13) CMD: fastboot erase userdata
14) CMD: fastboot reboot
(from time to time the message: failed to mount /data (invalid argument) popped up, and I don't know why)
However, havoc installed. I don't think Gapps installed though, because all I see in the os that is google related is a searchbar for apps only, gallery go, and the file manager. I used the "arm, 9.0, nano" options from the Gapps website, but when I flashed it, it said no changes were made. Did Gapps flash properly? If it didn't, how do you flash it properly? (I would expect the google play store to be in there somewhere, perhaps I need to get a heavier Gapps than nano?)
More importantly though, the OS says there is no sim card. I am on T-mobile, and calling and texting worked when I used lineage OS.
Does anyone have any advice of how to fix any of these issues? Again, my end goal is to have havoc os with the play store, and have the sim card working to make calls and texts.
Thank you one million to who ever can answer this.
Octodad said:
I've just spent the past 10 days trying to root my phone and use a custom ROM working (and detecting SIM card and most important functions). But it's always problem after problem after problem and at this point, I'm ready to give up. I feel broken. I'm at the point where I'd literally pay someone to take control and do it for me. I just can't do it no matter how much I learn, always a new problem and now I'm stuck at this one and I just can't take it anymore. Swear to god, I will pay .
Click to expand...
Click to collapse
Hey I literally am feeling the same way!! I know it's been a few months, but if you are still working on it, would you like to share knowledge and see if we can help each other?
timba123 said:
MetroPCS Moto G Power .I can't flash anything. And it oem locked. Is there any way to flash a stock partition ? Like Samsung's pit file
Click to expand...
Click to collapse
Try rsd light check into it might b what u looking for
UPDATE: I kept finding bugs in josh1x's rom, so i installed the LOS17 GSI instead. Guide for that outline in reply #11
Figured this out and thought i'd write a simple tutorial that covers stock (i was at 20e) to lineage. You'll need the LG USB Drivers and adb/fastboot. There are a couple other things to download through out the tutorial and the unlock tutorial in step 1.
LG USB Drivers 4.2.0
ADB/Fastboot
LGUP with partition DL
Note: I was able to reach download mode and fastboot at any point in this process and even when it went wrong (kernel crashes, boot loops etc) while figuring out this tutorial. I found that i could just hold vol down or up in a bootloop with the usb connected to get to the mode i wanted.
Typical combos:
-Download mode: power off phone with usb disconnected. hold vol up and plug in cable
--NOTE: after wiping laf_a and boot_b, you must switch to slot b to access download mode (run command: fastboot -ab)
-fastboot: power off phone with usb disconnected, hold vol down and plug in cable. or adb reboot bootloader
--NOTE: after wiping laf_a and boot_b, you can only access fastboot from slot a by holding vol up on boot (for 20e/21d, on 11g vol down still works).
-Recovery: power off. hold power and vol down, when you see the white LG G7 logo temporarily release just the power button. Continue to hold power and vol down till you get to the option menu. Select Yes three times.
Guide:
1. Follow the universal unlock method here.
1.5. You need to zero out laf_a and boot_b before flashing 21d/20e to maintain fastboot access. Use adb to run the following commands
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
dd if=/dev/zero of=/dev/block/bootdevice/by-name/boot_b
1.75. Enable usb debugging (should already be done). Open LGUP and connect to your phone. dont close it. If you open it after booting to DL mode it wont recognize it
2. 21d ULM firmware (here) must be flashed to use the latest twrp (20e works as well). The 11g twrp cannot install lineageos. I would imagine the EU firmware could be flashed as well, but I used ULM.
Code:
Boot into fastboot
fastboot -ab
Boot into download mode
Use the lg up linked in this post to flash 20e/21d without laf_a and boot_b with partition dl mode
3. Format userdata to decrpyt your file system so TWRP can access it. Then flash TWRP; boot_twrp-june.img can be found here. It's from Josh1x's post here. Note: this TWRP is non persistant.
Code:
Boot to bootloader
fastboot format userdata
fastboot flash boot_a boot_twrp-june.img
fastboot flash boot_b boot_twrp-june.img
Select restart in fastboot
Boot to recovery
4. Obtain the latest lineage build here. This is from Josh1x's post here. I attempted to flash gapps at this point and it failed, see the next steps.
Code:
Wipe everything
Transfer lineageos to your phone and install it
Restart normally
5. Gapps
Code:
Reboot to bootloader
fastboot flash boot_a boot_twrp-june.img
fastboot flash boot_b boot_twrp-june.img
Reboot to recovery
Transfer opengapps 9.0 to your phone and install.
Reboot to bootloader
6. We need to flash the stock lineage boot image (here) again now that we are done. The file was obtained with this method
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Restart normally
if you have magisk, it would be magisk_patched_boot.img (here). this one was made from the above image with magisk on my phone.
Code:
fastboot flash boot_a magisk_patched_boot.img
fastboot flash boot_b magisk_patched_boot.img
Restart normally
Any time you want to flash something via twrp you will have to flash twrp via fastboot again (hence the non persistance), do your stuff in twrp, and then reflash the boot img (it will not boot if you dont do this or use josh1x's boot file). Just like steps 5-6 for gapps.
I am so glad to be off of stock, enjoy guys and girls!
Bugs (from my ULM phone)
-flash doesnt work in the camera. also probably why gcam crashes (gcam works on an EM phone somehow)
-brightness slider is calibrated incorrectly compared to stock. way too bright when set to 0%
NOTE: using ULM vendor fixed the flash and brightness, but gcam still doesnt work. This would make it the most functional rom for this phone at this point (vibrate does work).
Being that since day1 of g710pm/ulm could be boot unlocked, all ypu had to do is flash the eu firmware and go to lineage frlm there due to twrp incompatibility.
I have not tested it, but does being on lineage based off EU blobs, do you still get full LTE and/or volte.
If sprint users have switched to eu/lineage do you have full lte/ril compatibility.
Ah crap I didn't know that. I tried unlocking through LG when I got it a couple months ago and that didn't work of course. At that time the phone was working well (not going on a background apps killing spree), so I didn't bother. I couldn't find anything on here at the time for unlocking, but I obviously missed that.
LTE and wifi are working fine. Maybe that has something to do with me never flashing the EU rom to install lineage? Anyways, I couldn't find a volte toggle, but I'd assume it is working. I'm on Verizon and I believe they are killing their cdma network, so I'll find out.
Would this work on sprint phones? There is a warning at the end of the unlocking guide about sprint phones loosing fastboot when upgrading to ulm pie.
does it work for EM too ? because i dont have any boot for linage to make it boot after i flash gapps also magisk bootloops too
Emanel000000 said:
does it work for EM too ? because i dont have any boot for linage to make it boot after i flash gapps also magisk bootloops too
Click to expand...
Click to collapse
If it boots on the lineage bootimg before flashing twrp again for Gapps, then yes, if you get that bootimg and flash it again after using twrp it will boot again.
Though I'm not sure why josh1x's boot img wouldn't work for your phone. That's what he used on his EM model after all.
Have you tried the other twrps?
sirbow2 said:
If it boots on the lineage bootimg before flashing twrp again for Gapps, then yes, if you get that bootimg and flash it again after using twrp it will boot again.
Though I'm not sure why josh1x's boot img wouldn't work for your phone. That's what he used on his EM model after all.
Click to expand...
Click to collapse
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk) ... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Emanel000000 said:
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk)
Click to expand...
Click to collapse
oh yea. i see, yes, they might as they are from the lineage rom.
Emanel000000 said:
... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Click to expand...
Click to collapse
It wont let me install that camera2 module. Says incompatible device. I tried the gcam patch and that didnt work either.
Also, flash does not work properly on the included camera. It flashes for the focus, but then doesnt for actually taking the picture.
sirbow2 said:
oh yea. i see, yes, they might as they are from the lineage rom.
It wont let me install that camera2 module. Says incompatible device. I tried the gcam patch and that didnt work either.
Also, flash does not work properly on the included camera. It flashes for the focus, but then doesnt for actually taking the picture.
Click to expand...
Click to collapse
i installed everything and now gcam somehow works its perfect thank you so much i couldn't do it without your guide
Emanel000000 said:
nonono i meant like magisk from the stock rom it was bootlooping so that means those images works for EM model too ? (bootimg and magisk) ... also i saw a guy saying gcam works on the lineage and i installed it and didnt work it was crashing if i would install camera2 api module from magisk will it work or ?
Click to expand...
Click to collapse
Emanel000000 said:
i installed everything and now gcam somehow works its perfect thank you so much i couldn't do it without your guide
Click to expand...
Click to collapse
Sweet man, so just to clarify, you have a 710EM and what firmware did you flash before lineage? 21dulm or 21d EM?
I think im going to try Andy's lineage GSI.
Edit: Update 2: dont use the vendor in this post. I patched the ULM vendor, but vibrate and gcam are still an issue with a GSI. links here: https://forum.xda-developers.com/showpost.php?p=81563763&postcount=41 Also, using the ulm vendor on Josh1x's rom fixed everything but gcam.
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.
sirbow2 said:
Sweet man, so just to clarify, you have a 710EM and what firmware did you flash before lineage? 21dulm or 21d EM?
I think im going to try Andy's lineage GSI.
Click to expand...
Click to collapse
i just had 20c for em it doesnt matter the version
sirbow2 said:
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.
Click to expand...
Click to collapse
Thanks. You're process got my audio working on GSI. Not sure what incorrect image I was installing or what the issue was.
Just need to disable the LED notification and get vibration working.
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
loonycgb2 said:
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
Click to expand...
Click to collapse
thats what i was kind of thinking the issue was. thats over my head though.
sirbow2 said:
thats what i was kind of thinking the issue was. thats over my head though.
Click to expand...
Click to collapse
Ask someone from the thread of flashing ulm 20d to backup their vendor if they havent flashed to EM firmware or lineage yet
loonycgb2 said:
EM devices vendor partition differ slightly compared to ULM devices, so camera issues and such will happen since you are using a slightly different blob.
There was a post of someone getting ULM to work with twrp so if someone can flash ULM and modify the vendor to load without encryption check and dmverity disabled then backup the vendor img.
Use that new vendor img will fix minor issues for ULM based devices on new gsi's.
Click to expand...
Click to collapse
loonycgb2 said:
Ask someone from the thread of flashing ulm 20d to backup their vendor if they havent flashed to EM firmware or lineage yet
Click to expand...
Click to collapse
Oh, so all we have to do is get it to boot through twrp (or just a boot with root?) and then dd it? I could probably just flash the 21d ULM kdz again and do that?
sirbow2 said:
Oh, so all we have to do is get it to boot through twrp (or just a boot with root?) and then dd it? I could probably just flash the 21d ULM kdz again and do that?
Click to expand...
Click to collapse
Once you got twrp running with stock then do the normal thing of format userdat to decrypt it then flash the no dmverity zip mentioned in the thread or magisk then backup vendor via twrp or dd...
That will give you a usable vendor for lineage and such.
All josh1x or whoever did to the EM vendor was modify fstab to remove the force encrypt so that way decrypted roms would work.
sirbow2 said:
I ended up moving to the GSI. I tried Deepflex's lineage 16 GSI but it was buggy and not working correctly. AndyYan's lineage 17 rom is working much better. Camera flash even works and the brightness slider is correct. List of all GSIs
If starting from stock, follow this new guide after doing the fastboot format userdata command in step 3 of the original guide in post #1
1. Flash vendor_gsi image (sourced from aosp trebble g7 EM this thread)
Code:
fastboot flash vendor_a vendor_gsi.img
fastboot flash vendor_b vendor_gsi.img
The above is the only file used from the source i linked above. I had to use a different twrp (the one from the existing thread wouldnt go past the lock screen after first reboot) so i tried the one below which worked, but only with the vbmeta img from josh1x's lineage 16 rom.
2. Flash vbmeta from josh1x's LOS16 rom (as mentioned before). File attached.
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
3. Flash latest twrp 3.3.1 (sourced from this thread). If you have magisk, here's the version i patched.
Code:
fastboot flash boot_a twrp_20b.img
fastboot flash boot_b twrp_20b.img
4. Flash GSI of whatever flavor you want. needs to be amd64 and for the A/B (bvN) partition type. I used this one
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
5. Reboot while wiping data (shouldnt wipe internal "sdcard", didnt for me). Should boot into lineage now.
Code:
fastboot -w reboot
6. For gapps, just reboot into recovery (none of that non persistant boot stuff), and flash the beta android 10 gapps from here
Note: I had to resize the system partition for the LOS17 rom for this as it didnt fill the entire filesystem when it was flashed. Go to the TWRP terminal and run mount to find the device path for /system and then run resize2fs /device/block/whatever.
Click to expand...
Click to collapse
Nevermind
I tried using the vendor from ULM 20e and it doesnt work, i even tried flashing dm verity right after. How would one modify the vendor partition anyways?
Android 11 gsi images are out and the OP7Pro is a compatible device. Just wondering if anyone has tried flashing the image yet?
https://developer.android.com/preview/gsi-release-notes
Was going to try it out on my OP7Pro 5G Sprint in a little while.
Electricboy207 said:
Was going to try it out on my OP7Pro 5G Sprint in a little while.
Click to expand...
Click to collapse
Great. Let me know. I'm anxious to try it myself but a little nervous I might screw it up.
You can flash the image in twrp.
I'm a little nervous too since this is my first A/B device, along with my first treble device. I've already made a backup.
Gordietm said:
Android 11 gsi images are out and the OP7Pro is a compatible device. Just wondering if anyone has tried flashing the image yet?
https://developer.android.com/preview/gsi-release-notes
Click to expand...
Click to collapse
Tried to flash doesn't boot just hangs on bootanim.
liam_davenport said:
Tried to flash doesn't boot just hangs on bootanim.
Click to expand...
Click to collapse
What exactly did you do to flash it? I was going to try to flash some other GSIs, too.
just wipe system, data,cache dont wipe vendor.
austinpinto said:
just wipe system, data,cache dont wipe vendor.
Click to expand...
Click to collapse
I think you might have to format data first.
Better flash using Fastboot method .
1- Format Userdata (Formats data partition with raw . Follow next step)
1.1 fastboot -w ( Gives format to data partition)
2- Disable Vbmeta
3- Flash system_a system_b
4- Reboot and it should work
ZoiraP said:
Better flash using Fastboot method .
1- Format Userdata (Formats data partition with raw . Follow next step)
1.1 fastboot -w ( Gives format to data partition)
2- Disable Vbmeta
3- Flash system_a system_b
4- Reboot and it should work
Click to expand...
Click to collapse
Didn't work for me, I get
qualcomm crash dump:
attempted to kill init exitcode=0x00000000b
Whoareyou said:
Didn't work for me, I get
qualcomm crash dump:
attempted to kill init exitcode=0x00000000b
Click to expand...
Click to collapse
I'm Finishing my last University-Class , As soon as I arrive home I'll try and report back here the results.
If someone gets it running please test out Desktop OS. You might have to unlock it in developer settings like one Android 10. Interested in seeing if it was optimized and updated some more. Would be good sign to see it being actively worked on!!
Has anyone gotten it booted on here yet? It should work from what I've read.
Waiting to hear what @ZoiraP comes up with ?
Deleted
ZoiraP said:
Better flash using Fastboot method .
1- Format Userdata (Formats data partition with raw . Follow next step)
1.1 fastboot -w ( Gives format to data partition)
2- Disable Vbmeta
3- Flash system_a system_b
4- Reboot and it should work
Click to expand...
Click to collapse
did you do this while in fastboot mode and what are the fastboot commands? Example: fastboot flash system_a ?????? Zip is invalid whenever trying to flash with twrp...
mjb337 said:
did you do this while in fastboot mode and what are the fastboot commands? Example: fastboot flash system_a ?????? Zip is invalid whenever trying to flash with twrp...
Click to expand...
Click to collapse
I do know that you need to change the file ext from .zip to .img and flash it as a system image in twrp.
anyone got R bootup
Is there R platform tools you have to use also? There is new ask build tools
I actually managed to flash on TWRP. But I had to extract the zip file and use the System img file inside the zip. However I forgot to flash the TWRP installer ... Instead I reboot system and It went to bootloader and I lost my recovery...so had to flash the msm to unbrick. No idea what to do again.
---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------
ZoiraP said:
Better flash using Fastboot method .
1- Format Userdata (Formats data partition with raw . Follow next step)
1.1 fastboot -w ( Gives format to data partition)
2- Disable Vbmeta
3- Flash system_a system_b
4- Reboot and it should work
Click to expand...
Click to collapse
Did this work for you?