i have a moto g that and im trying to flash twrp buy using the fastboot method
fastboot flash recovery TWRP..........................................
but when i finish flashing it says mismatched partition (recovery)
plzz help me
i have the moto g xt1039 model if any one has the correct .imgfile for twrp for my model can u give me a direct link please
thank you in advance
JaCoB 0o7 said:
i have a moto g that and im trying to flash twrp buy using the fastboot method
fastboot flash recovery TWRP..........................................
but when i finish flashing it says mismatched partition (recovery)
plzz help me
i have the moto g xt1039 model if any one has the correct .imgfile for twrp for my model can u give me a direct link please
thank you in advance
Click to expand...
Click to collapse
I think your device is codename peregrine
If so this is what you need
https://eu.dl.twrp.me/peregrine/twrp-3.1.1-0-peregrine.img.html
download
put phone into bootloader mode and connect to pc via usb
open a command/terminal prompt at your fastboot location where you have also placed the recovery image
type the following where name_of_recovery.img is the name of the recovery img you downloaded
Code:
fastboot flash recovery name_of_recovery.img
Hi everyone, can anyone help me, I have a g4 plus bike that I was on android XT1640_ATHENE_7.0_NPJ25.93-14 he has the bootloader unlocked and asked for an update when I was installing it it went out, I installed the branckflash more when I give the commands : fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
He always fails someone there to help me.
How to Install GApps onto Xiaomi Black Shark
IF YOU ARE UNLOCKING YOUR BOOTLOADER FOR THE FIRST TIME, THEN THIS WILL WIPE USER DATA. You are also assuming the risk of bricking your device! Please read directions carefully!
REQUIREMENTS:
Unlocked Bootloader!
TWRP from mauronofrio found here
1. Unlock Bootloader (if you haven't yet):
FOR CHINESE VERSION (SKR-A0):
Code:
fastboot oem unlock
FOR GLOBAL VERSION (SKR-H0)[SIZE]
Code:
fastboot flashing unlock
2. Get GApps:
Go to http://www.opengapps.org and download NANO SIZE OR BELOW.
Download .gapps-config file if you want to KEEP the STOCK PACKAGE INSTALLER
3. Factory wipe data in recovery mode:
This will erase all of your data! Make sure you have a backup you can use that's not on your phone. This helped make sure active boot a got the correct files flashed to it and it not disappearing.
4. Check that Active Boot Partition as A!:
The default active boot is a. For some reason the system_b and vendor_b partitions doesn't have enough space for flashing gapps...
5. Boot into TWRP and flash!:
Code:
fastboot boot twrpimg.img
move gapps & optional config file to phone internal storage
flash gapps
reboot!
5. All Done!:
Go through both set up processes(if data was wiped)
What Has Been Checked:
All GApps on Stock and Nano Packages
Credits:
OpenGApps for GApps
@Invisan for Unlock Bootloader Method for Global Variant
@ioriz for Unlock Bootloader Method for Chinese Variant
@mauronofrio for TWRP
thanks mate. a must have after rooting. i'll share your good work.
by the way, when flashing, it gives error 70.
kanded said:
by the way, when flashing, it gives error 70.
Click to expand...
Click to collapse
Which GApps version did you use? Error 70 is caused from the system not having enough storage, so nano or pico packages are the only available options that should work.
@kanded I've updated the steps for flashing. For some reason system_b doesn't have a big enough partition size for the GApps to work correctly. Flashing from system_a after setting A as your active partition should work. I just tested it (even with a borked system_a partition like mine!)
JengaMasterG said:
Which GApps version did you use? Error 70 is caused from the system not having enough storage, so nano or pico packages are the only available options that should work.
@kanded I've updated the steps for flashing. For some reason system_b doesn't have a big enough partition size for the GApps to work correctly. Flashing from system_a after setting A as your active partition should work. I just tested it (even with a borked system_a partition like mine!)
Click to expand...
Click to collapse
i think im gonna find a way to reduce the size of the image. thanks a lot mate.
hi, can you share with me stock boot image(i install magisk and i dont have stock boot) and stock recovery backup for bs 1 china ?
By unlocking the bootloader, will I lose the OTA firmawares updates?
cavs171 said:
By unlocking the bootloader, will I lose the OTA firmawares updates?
Click to expand...
Click to collapse
Not by unlocking, but after flashing anything. Including flashing twrp, or magisk, or rooting, or decrypting. You can always backup after unlocking and before flashing anything, allowing you to return to stock anytime. And by backup, i mean manually copying all the phone partitions to your computer, not the twrp backup thingy.
i need help with my black shark 2 global version
i cant unlock the bootloader i dont know why....
any help????
JengaMasterG said:
Which GApps version did you use? Error 70 is caused from the system not having enough storage, so nano or pico packages are the only available options that should work.
@kanded I've updated the steps for flashing. For some reason system_b doesn't have a big enough partition size for the GApps to work correctly. Flashing from system_a after setting A as your active partition should work. I just tested it (even with a borked system_a partition like mine!)
Click to expand...
Click to collapse
Hye, what's the difference between installing GApps via TWRP compare to installing using the google installer from app store that came with the phone?
I'm using SKR-A0 version.
Another question is, can I relock the bootloader without wiping the data? so that I can get the new official OTA again.
Thanks again
Hello there, I have unlocked the bootloader and rooted my phone with magisk but I could not flash gapps stock or mini, I have the same code 70 (Insufficient storage), I have tried to switch to partition A using .\fastboot.exe --set-active=a and it said "current-slot: a" when I tried .\fastboot.exe getvar current-slot.
The reboot menu in TWRP doesn't have the A/B slot option for version 3.3.1 blackshark, the old version has it but no longer works and giving me black screen but the screen is on after I update to android p via System Update.
Is there an additional step to switch partitions or did I messed up?
Code:
* Disclaimer
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* before flashing GSI! YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! goes the dynamite
- make sure you have your stock rom by hand, and in case youre also using a new mediatek device make sure you also have mtk-bypass utility and sp flash tool by hand just in case or any other way of restoring your stock rom
you cant have magisk patched boot image installed unless you have also flashed a different product img
- under developer options enable oem unlocking
- adb reboot bootloader
- fastboot flashing unlock
- fastboot flashing unlock_critical
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
- fastboot reboot fastboot
- fastboot delete-logical-partition product (DONT DO THIS IF YOU WANT TO FLASH MAGISK. IF YOU DO THEN FOLLOW THIS GUIDE REGARDING MAGISK AND PRODUCT PARTITION https://forum.xda-developers.com/t/tutorial-magisk-on-gsi-on-devices-with-dynamic-partition.4311045/)
- fastboot flash system system.img (must be arm64 A/B)
- fastboot reboot recovery
- format in TWRP (https://forum.xda-developers.com/t/unofficial-twrp-3-5-2-for-infinix-zero-8-x687.4303243/)
enjoy your GSI experience
note that im not responsible for any bricked devices
do this at your own risk
tested on infinix zero 8 X687
Your device MUST have an unlockable bootloader.
Your device MUST be Project Treble compatible. That means your device meets one of the following criteria:
Your device LAUNCHED with Android 8.0 Oreo or a newer version (eg. Android 8.1 Oreo) AND is Google Play certified. (If you rooted your device/flashed another custom ROM and somehow ended up with your device being listed as uncertified in Google Play, then don’t worry. We’re only concerned about the status of the device as it was shipped.)
Your device UPGRADED to Android 8.0 Oreo or a newer version AND was made Project Treble compatible by the manufacturer. See this article for a list of such devices.
Your device does not meet either of the above criteria but DOES have access to an unofficial way to be made Treble compatible. Again, refer to this article for a list of such devices.
Your device is free of any heavy modifications such as the Xposed Framework, SuperSU, or Magisk. You can re-install these afterward, but please be sure you are using the stock boot/ramdisk before proceeding.
Sarticle said:
Your device MUST have an unlockable bootloader.
Your device MUST be Project Treble compatible. That means your device meets one of the following criteria:
Your device LAUNCHED with Android 8.0 Oreo or a newer version (eg. Android 8.1 Oreo) AND is Google Play certified. (If you rooted your device/flashed another custom ROM and somehow ended up with your device being listed as uncertified in Google Play, then don’t worry. We’re only concerned about the status of the device as it was shipped.)
Your device UPGRADED to Android 8.0 Oreo or a newer version AND was made Project Treble compatible by the manufacturer. See this article for a list of such devices.
Your device does not meet either of the above criteria but DOES have access to an unofficial way to be made Treble compatible. Again, refer to this article for a list of such devices.
Your device is free of any heavy modifications such as the Xposed Framework, SuperSU, or Magisk. You can re-install these afterward, but please be sure you are using the stock boot/ramdisk before proceeding.
Click to expand...
Click to collapse
thats complete bs
your device must be launched with android 10 or newer to be able to have dynamic partitions.
google play certification has nothing to do with it.
and if you flash product partition you might get away without reinstalling magisk or xposed
can anyone shed light on whether or the super partition is shared between the slots? in other words, if I flash a boot image to super partition in twrp, will it flash only to that slot's super (slot B in my case is messed up) or will it flash to both slots? I am only trying to flash to slot B super partition in hopes of restoring /system_ext, /product, and /odm. any help is greatly appreciated
thirtythr33 said:
can anyone shed light on whether or the super partition is shared between the slots? in other words, if I flash a boot image to super partition in twrp, will it flash only to that slot's super (slot B in my case is messed up) or will it flash to both slots? I am only trying to flash to slot B super partition in hopes of restoring /system_ext, /product, and /odm. any help is greatly appreciated
Click to expand...
Click to collapse
super partiton only has system, vendor and product a/b partitions
boot isnt on super partition
kusti420 said:
super partiton only has system, vendor and product a/b partitions
boot isnt on super partition
Click to expand...
Click to collapse
ok the reason I ask is I am given the option to flash my backup boot image to super in twrp flash image screen, that's why I asked, and since twrp is reporting that I'm missing system_ext, product, and odm, that flashing to super would fix that, a long shot but I'm desperate.
so to be clear is it shared between slots or does each slot have it's own super? (or the partitions found in it)
kusti420 said:
- make sure you have your stock rom by hand, and in case youre also using a new mediatek device make sure you also have mtk-bypass utility and sp flash tool by hand just in case or any other way of restoring your stock rom
also stock recovery must be installed
and you cant have magisk patched boot image installed
- under developer options enable oem unlocking
- fastboot flashing unlock and then fastboot flashing unlock_critical
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
- fastboot reboot fastboot
- fastboot delete-logical-partition product
- fastboot flash system system.img (must be arm64 A/B)
- fastboot reboot
- format in TWRP (https://forum.xda-developers.com/t/unofficial-twrp-3-5-2-for-infinix-zero-8-x687.4303243/)
or if you dont have a custom recovery then you can just factory reset in stock recovery
enjoy your GSI experience
note that im not responsible for any bricked devices
do this at your own risk
tested on infinix zero 8 X687
Click to expand...
Click to collapse
this is all done on pc right? is everything in order?
JordanPahlevi said:
this is all done on pc right? is everything in order?
Click to expand...
Click to collapse
yes its done on pc and everything is indeed in order
Flash gsi with twrp can't ?
Blacxx said:
Flash gsi with twrp can't ?
Click to expand...
Click to collapse
you can only do it in twrp if you rebuild the whole super partition with the gsi of your choice and flash that
Android prevents apps or pretty much anything from mounting the system.
Stephanie_Sy said:
Android prevents apps or pretty much anything from mounting the system.
Click to expand...
Click to collapse
mounting isnt the problem, it mounts just fine, but its read only, thats the problem
How did you port twrp for infinix zero 8? I need one for infinix note 10
My phone is Techno kd7.
My phone Dynamic Partition Android, I have installed TWRP Recovery but can't flash gsi img because the system is IMG partition 1700 MB and gsi img 1800 up. Please give me a solution sir
Parvej789 said:
My phone is Techno kd7.
My phone Dynamic Partition Android, I have installed TWRP Recovery but can't flash gsi img because the system is IMG partition 1700 MB and gsi img 1800 up. Please give me a solution sir
Click to expand...
Click to collapse
follow the tutorial and flash product partition
this may be of interest or help to Samsung users in particular.
getting fastboot via TWRP to work on windows 7 to 10. it worked for me on windows 10 pro and enabled me to flash GSIs successfully.
Latest ADB Fastboot and USB Drivers installer tool for windows
All praise and All Thanks to God ADB Fastboot and USB Driver installer tool for Windows, which will always install the latest version. To update the adb fastboot and usb drivers again, just rerun the tool. OS Requirements: Windows 7 and above Steps: 1. Connect the phone in USB Debugging mode...
eu.community.samsung.com
it's not just for Samsung users though, it'll install the latest ADB and Fastboot drivers and download Microsoft dependencies. but now us Samsung users can have Fastboot and do
Code:
fastboot flash system system.img
... so yay !!
kusti420 said:
super partiton only has system, vendor and product a/b partitions
boot isnt on super partition
Click to expand...
Click to collapse
i flashed using these commands on my v60 tmobile
--AB devices--
fastboot devices
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_insertslothere
Example
fastboot delete-logical-partition product_a
fastboot delete-logical-partition productb
fastboot flash system system.img
fastboot reboot recovery
i flashed 3 gsi A10s, los 17.1 didnt boot, pixel experiance and RR Remix booted but never entered android. and when i tried to flash my kdz it flashes all parititons except for super.img it fails everytime on different modes of LG up. I flashed super.img via Qfil but phon wont boot.
i even tried using ChonDoe_Flasher via twrp in a folder it flashes but it still wont boot at all. at this point i cant use LGup because i get stuck in download mode. any help would be greatly appreciated
blaze2051 said:
Try :
Click to expand...
Click to collapse
Commands used to Install gsi Rom using Fastboot Mode
1. First Go into Fastboot mode by typing this command
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
2.Type these commands 1 by 1
fastboot reboot fastboot
fastboot delete-logical-partition product_a
fastboot delete-logical-partition system_ext_a
fastboot erase system
fastboot flash system system.img(dynamic gsi ROM flash)
fastbo -w
fastboot reboot
Note(stock recovery to try)
Parvej789 said:
Commands used to Install gsi Rom using Fastboot Mode
1. First Go into Fastboot mode by typing this command
adb reboot bootloader
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
2.Type these commands 1 by 1
fastboot reboot fastboot
fastboot delete-logical-partition product_a
fastboot delete-logical-partition system_ext_a
fastboot erase system
fastboot flash system system.img(dynamic gsi ROM flash)
fastbo -w
fastboot reboot
Note(stock recovery to try)
Click to expand...
Click to collapse
i finally got a working rom install since i cant go back to oem stock, it wasnt the commands it was the roms, they just dont boot at all. except one 1 rom did boot. all others LOS 16-18 RR Remix and Pixel experiamce all failed to boot except for E foundation rom
/http://doc.e.foundation/how-tos/understand-and-use-gsi 7
/http://doc.e.foundation/how-tos/install-GSI 7
New linksto download the latest official
dev /e/ G.S.I. android.10 Q
Once you know which system image you need
Arm A 2 (system-arm-a.img.xz)
Arm A/B 3 (system-arm-ab.img.xz)
Arm64 A 11 (system-arm64-a.img.xz)
Arm64 A/B 31 (system-arm64-ab.img.xz)
Binder 64 A 1 (system-a64-a.img.xz)
Binder 64 A/B 4 (system-a64-ab.img.xz)
I no know.
Dynamic
gsi ROM
GsI Rom Link : Tested rom
Tecno kd7 work
*Official Android 11 :
1. AOSP 11.0 v313_system-roar-arusson
Download link AOSP 11.0 v313
*Unofficial QAndroid 11 :
1. Pixel Experience Plus 11.0 v313
Thanks for ponces
Download link PixelExperience_Plus_arm64-ab-11.0-20211011-UNOFFICIAL.img.xz
*Unofficial Android 12 :
1.Pixel Experience 12.0 v400.e
Thanks for ponces
Full googel rom. my used 5 day . 1 bug : bootanimation not vew full size
Download link :PixelExperience_arm64-ab-12.0-20211226-UNOFFICIAL.img.xz
Hi guys, I'm sorry to bother with this question that seems ridiculous but unfortunately around you will not find many decent guides
I own a moto g 5g (Kiev) I would like to install custom rom but I know that the device has dual boot
Since there has been dual boot/partitions technology for years, I have not yet understood the correct installation of a custom rom in such devices
I've always been used to installing custom roms in devices with only one partition (which despite this I had difficulty anyway)
Is there anyone willing to write the steps and steps of installing recovery with custom rom for dual partition A/B devices?
It's also fine if you have material like: videos, links to guides and more
I apologize for my English from google translate
In bootloader
fastboot flash recovery_a <recoveryname.img>
fastboot flash recovery_b <recoveryname.img>
Or flash installer.zip in recovery
fastboot boot <recoveryname.img>
Sideload / select recovery zip
Typically the work flow follows as such:
1) Install permanent recovery via twrp ui or fastboot in bootloader
2) Flash rom.zip
3) Reboot recovery
Flash gapps
4) Format data (recovery ui)
format data (bootloader) / fastboot -w
5) Reboot system/start
Belli99 said:
I own a moto g (Kiev)
Click to expand...
Click to collapse
What is the exact model of your Moto G 5G?
Old_Mil said:
Qual è il modello esatto del tuo Moto G 5G?
Click to expand...
Click to collapse
Moto g 5g - Kiev - XT2113-3
SyberHexen said:
In bootloader
fastboot flash recovery_a <recoveryname.img>
fastboot flash recovery_b <recoveryname.img>
Or flash installer.zip in recovery
fastboot boot <recoveryname.img>
Sideload / select recovery zip
Typically the work flow follows as such:
1) Install permanent recovery via twrp ui or fastboot in bootloader
2) Flash rom.zip
3) Reboot recovery
Flash gapps
4) Format data (recovery ui)
format data (bootloader) / fastboot -w
5) Reboot system/start
Click to expand...
Click to collapse
Fastboot flash recovery must be specified and installed for both partitions. To install the custom ROM and Gapps you just need to flash, right? I noticed that some developers allow you to flash "copy_partition.zip" what would that be?
This may be a naive mistake but I was trying to install the pixel plus 13 rom on my redmi 6 pro (Sakura)
For the first time it showed me a signature failure, I skipped it in the second attempt and it installed. Now the pixel plus os doesn't run, restarting the device brings me back to recovery options. The device gets detected in adb under recovery but not on fast boot mode.
Also I can't install any other images after this.
There was a prompt to modify or keep the partition read only. I selected modify, since then the twrp is stuck at its loading screen.
Any help?