Related
#Prerequisites:
Stock Rom: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
TWRP: https://dl.twrp.me/ali/twrp-3.3.0-0-ali.img
Dejello TWRP: https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn (Unofficial) //Only for custom roms, when you need to install GApps.
Magisk: https://github.com/topjohnwu/Magisk/releases/download/v19.0/Magisk-v19.0.zip
Magisk Manager: https://github.com/topjohnwu/Magisk/releases/download/manager-v7.1.1/MagiskManager-v7.1.1.apk
DM Verity Disabler: https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_04.03.19.zip
Unlocked Bootloader: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Minimal ADB/Fastboot (Windows only): https://androidfilehost.com/?fid=962187416754459552
Moto USB Drivers (drivers only, no manager): https://motorolausbdriver.com/wp-content/uploads/Motorola_Mobile_Drivers_v6.4.0.zip
Windows hint:
For all what you want to do with your Motorola phone, you need the above provided Minimal ADB/Fastboot environment.
Download and extract it,
Move the files you want to flash into the folder
Open CMD (Windows Key and R - then type cmd) and navigate into the extracted folder.
//It's easier when you type cd into the cmd and drag the folder from your adb/fastboot environment into the cmd window and hit enter.
And that's it. The patched boot image is no longer needed.
Rooting the Moto G6
1. Boot into fastboot mode (Vol - and Power simultaneously) and connect it to your computer
2. Open Terminal (Linux)/CMD (Windows) and go into the folder where your recovery image lies.
3. Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
4. If it asks for a password hit cancel, go to wipe, data wipe and confirm it with yes. Then reboot again into recovery.
5. Repeat the wiping and reboot another time into recovery.
6. Connect your phone to your Computer while in recovery and copy magisk and dm-verity disabler to your phone.
7. Go to Install and flash dm-verity disabler first, then magisk.
Thats it. You're rooted.
Update/Go back to Stock.
//Download the stock rom you want to use and extract it to your Desktop.
//Latest ROM (Android 9) is ALI_RETAIL_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1. Go into recovery mode (twrp), choose wipe - wipe data and confirm with yes.
2. Back to the wipe main screen, advanced wipe and hit everything.
3. Wipe it two times.
4. Boot into download mode and connect your phone to your computer.
5. Open Terminal or CMD in the folder of your stock firmware and hit the following commands (hint: it's easier to use a bash/batch file):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Wait until it finished, disconnect your phone, wait and set it up.
That's it.
Simple and easy.
So... When do you tell people about installing ADB and fastboot? Moto drivers? Ya skipped some stuff dude.
madbat99 said:
So... When do you tell people about installing ADB and fastboot? Moto drivers? Ya skipped some stuff dude.
Click to expand...
Click to collapse
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
And for root not need boot.img file?
cecogor said:
And for root not need boot.img file?
Click to expand...
Click to collapse
No, Magisk is patching the stock boot.img, which is already on your device.
The patched images are not needed anymore for Magisk.
ThisIsRussia said:
No, Magisk is patching the stock boot.img, which is already on your device.
The patched images are not needed anymore for Magisk.
Click to expand...
Click to collapse
Ok, I see.
I remark one more thing - "Disable_Dm-Verity_ForceEncrypt_02.04.2019" i much more biger then "Force_Encryption_Disabler_For_ALI_Oreo_v2" - 4MB vs 100kB. What is different here?
cecogor said:
Ok, I see.
I remark one more thing - "Disable_Dm-Verity_ForceEncrypt_02.04.2019" i much more biger then "Force_Encryption_Disabler_For_ALI_Oreo_v2" - 4MB vs 100kB. What is different here?
Click to expand...
Click to collapse
Due to OS changes and it's a feature bundle.
It edits DM-Verity, ForceEncrypt and Disk Quota.
Can't get root
The install by the instructions went perfectly but I can't get root. I did one thing differently than on the root instructions and I think I did it correctly, where you have;
Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
I did "fastboot flash recovery twrp-3.2.3-0-ali.img" which I thought you meant because stock recovery would already be installed or am I missing something here. I followed all the rest of the instructions perfectly and everything seemed to wipe reboot and install fine but when I boot back into android I don't have root. In fact I tried it four times and never got root. Do you have any ideas what could be wrong? Thanks for any help but I do have Android 9 running just fine. I'd like to get this rooted rather than go back to 8 because it seems to run so much better.
mward7221 said:
The install by the instructions went perfectly but I can't get root. I did one thing differently than on the root instructions and I think I did it correctly, where you have;
Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
I did "fastboot flash recovery twrp-3.2.3-0-ali.img" which I thought you meant because stock recovery would already be installed or am I missing something here. I followed all the rest of the instructions perfectly and everything seemed to wipe reboot and install fine but when I boot back into android I don't have root. In fact I tried it four times and never got root. Do you have any ideas what could be wrong? Thanks for any help but I do have Android 9 running just fine. I'd like to get this rooted rather than go back to 8 because it seems to run so much better.
Click to expand...
Click to collapse
You Need install magisk Manager wich is linked above and restart device.
Then open magisk Manager from Menu.
ThisIsRussia said:
You Need install magisk Manager wich is linked above and restart device.
Then open magisk Manager from Menu.
Click to expand...
Click to collapse
I tried all that and couldn't get it to work, I downloaded everything from your links above but no go. Someone posted a no-verity boot image in another thread. post 598 I believe and I flashed that file, flashed Magisk 18.1 in twrp and now I have root so I'm set, Thanks for your reply
ThisIsRussia said:
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
Click to expand...
Click to collapse
Of course on Linux no drivers are needed. But most running Linux don't need instructions. It's usually windows users needing such instructions.
That's the only reason I chimed in.
Carry on.
Nice guide.
ThisIsRussia said:
Update/Go back to Stock.
//Download the stock rom you want to use and extract it to your Desktop.
//Latest ROM (Android 9) is ALI_RETAIL_9.0_PPS29.55-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
1. Go into recovery mode (twrp), choose wipe - wipe data and confirm with yes.
2. Back to the wipe main screen, advanced wipe and hit everything.
3. Wipe it two times.
4. Boot into download mode and connect your phone to your computer.
5. Open Terminal or CMD in the folder of your stock firmware and hit the following commands (hint: it's easier to use a bash/batch file):
Click to expand...
Click to collapse
When updating a rooted phone from Android 8 to Android 9 do you have to wipe (in TWRP) and use the following?
Code:
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
kmssd said:
When updating a rooted phone from Android 8 to Android 9 do you have to wipe (in TWRP) and use the following?
Click to expand...
Click to collapse
If you Change major OS Version, you always need a clean Flash and rerooting.
ThisIsRussia said:
For my own experience it worked without moto drivers. On Windows 7 and Windows 10 testing systems.
Personally I use Arch, which natively supports adb and fastboot, provided by the android-tools package.
But thank you for your hint, I added it.
Click to expand...
Click to collapse
I would change official TWRP to Dejello's unofficial TWRP as official one won't install Gapps
https://drive.google.com/open?id=1QWYIcti-wJPPMAc8Ol5pnoO3b8CqtKFn
Hi ppl, sorry for that questions, I make a lot of roots, on mine Samsung S3, Sony ZQ, and many other, But in last times I dont make it with magisk.... so someone can explain some things for me?
First work on XT1925-3? 4/64gb variant?
TWRP is need or only ADB? I just want to make only by adb...
If its okay now:
1. Boot into fastboot mode (Vol - and Power simultaneously) and connect it to your computer
Click to expand...
Click to collapse
>> Here is ok,
2. Open Terminal (Linux)/CMD (Windows) and go into the folder where your recovery image lies.
Click to expand...
Click to collapse
>> Here is ok too
3. Type "fastboot flash recovery recovery.img" and use the volume keys on your phone to select "recovery mode", when finished.
Click to expand...
Click to collapse
>> Here is ok too, similar to flash my Sony
4. If it asks for a password hit cancel, go to wipe, data wipe and confirm it with yes. Then reboot again into recovery.
Click to expand...
Click to collapse
>> I belive if I have pass on phone? if I remove the phone only need a reboot in recovery?
5. Repeat the wiping and reboot another time into recovery.
Click to expand...
Click to collapse
>> The phone will be need a wipe two wipes? or only one?
6. Connect your phone to your Computer while in recovery and copy magisk and dm-verity disabler to your phone.
Click to expand...
Click to collapse
>> Here is mine question, the phone wont wakeup for now, but in recovery mode will be open folder to that? I remeber on my S3 in twrp I mount the storage to acess, in ADB method is same?
7. Go to Install and flash dm-verity disabler first, then magisk.
Click to expand...
Click to collapse
>> Okay, install DM, after that, wakeup phone, and after that flash magisk? Magisk maneger is same thing? So, is Flash DM > reboot into recovery or wakeup? after, flash magisk, reboot again? install magisk maneger?
So, sorry for that all questions, and if I trade some words, I have dyslexia and I'm backing to root world after a long time.
brunogroa said:
Hi ppl, sorry for that questions, I make a lot of roots, on mine Samsung S3, Sony ZQ, and many other, But in last times I dont make it with magisk.... so someone can explain some things for me?
First work on XT1925-3? 4/64gb variant?
TWRP is need or only ADB? I just want to make only by adb...
If its okay now:
>> Here is ok,
>> Here is ok too
>> Here is ok too, similar to flash my Sony
>> I belive if I have pass on phone? if I remove the phone only need a reboot in recovery?
>> The phone will be need a wipe two wipes? or only one?
>> Here is mine question, the phone wont wakeup for now, but in recovery mode will be open folder to that? I remeber on my S3 in twrp I mount the storage to acess, in ADB method is same?
>> Okay, install DM, after that, wakeup phone, and after that flash magisk? Magisk maneger is same thing? So, is Flash DM > reboot into recovery or wakeup? after, flash magisk, reboot again? install magisk maneger?
So, sorry for that all questions, and if I trade some words, I have dyslexia and I'm backing to root world after a long time.
Click to expand...
Click to collapse
Here are the steps I use to flash/root my wifes Moto G6 xt1925-6 (pie)
1. Make sure dev options are on and usb debugging is on.
2. adb reboot bootloader
3. Extract the image file directly into the same directory as adb and fastboot.
4. Launch cmd as admin, CD to the directory where adb and fastboot is.
5. via CMD launch flash_all.bat which will run through and do all the flashing of the necessary parts.
6. I actually did the first time setup, making sure usb debugging is on again and also making sure I dont have any pw or security enabled.
7. adb reboot bootloader.
8. fastboot flash recovery recovery.img
9. fastboot flash boot no-verity_boot.img
10. boot into twrp and then format, I did a Format data, then a factory data reset.
11. back in twrp copy magisk over to phone, and install via twrp
12. reboot system and it should boot up again.
13. make sure to do first time setup and enable usb debugging and make sure magisk manager is installed, updated, and configured how you want it.
14. I usually do core only mode, magisk hide, and also hide the magisk manager package via the settings. under general settings.
Stuck on Booting screen
Unlocked bootloader on Moto G6 xt1925-6 RETUS. Loaded TWRP fine. Did factory reset twice to remove data encryption. Installed Disable_Dm-Verity_ForceEncrypt_03.28.19.zip followed by Magisk 18.1.zip. Boots back to recovery fine but stays at boot screen when booting to system.
Any suggestions.
Stephen
theseeker2654 said:
Here are the steps I use to flash/root my wifes Moto G6 xt1925-6 (pie)
1. Make sure dev options are on and usb debugging is on.
2. adb reboot bootloader
3. Extract the image file directly into the same directory as adb and fastboot.
4. Launch cmd as admin, CD to the directory where adb and fastboot is.
5. via CMD launch flash_all.bat which will run through and do all the flashing of the necessary parts.
6. I actually did the first time setup, making sure usb debugging is on again and also making sure I dont have any pw or security enabled.
7. adb reboot bootloader.
8. fastboot flash recovery recovery.img
9. fastboot flash boot no-verity_boot.img
10. boot into twrp and then format, I did a Format data, then a factory data reset.
11. back in twrp copy magisk over to phone, and install via twrp
12. reboot system and it should boot up again.
13. make sure to do first time setup and enable usb debugging and make sure magisk manager is installed, updated, and configured how you want it.
14. I usually do core only mode, magisk hide, and also hide the magisk manager package via the settings. under general settings.
Click to expand...
Click to collapse
Ohh sure... So need twrp to do, I Will trie this, thx a lots, here is the same with pie
Tom Swift said:
Unlocked bootloader on Moto G6 xt1925-6 RETUS. Loaded TWRP fine. Did factory reset twice to remove data encryption. Installed Disable_Dm-Verity_ForceEncrypt_03.28.19.zip followed by Magisk 18.1.zip. Boots back to recovery fine but stays at boot screen when booting to system.
Any suggestions.
Stephen
Click to expand...
Click to collapse
On top of using the disabler download and flash the no verity boot.img from the link below. Works great on my xt1925-6 with pie.
Also, use Magisk 19.0
https://drive.google.com/file/d/1JLMVRBCsMnr7RYxdRFjFLOwVSy8r8hSQ/view
The DM Verity Disabler link not working:
https://zackptg5.com/downloads/Disab...02.04.2019.zip
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
I own a Doogee s88 pro. I have installed twrp as a recovery using an unofficial method. I have also rooted the device using OEM key.
However, I am having an issue flashing a gsi to it. Through twrp it states that the "image is larger than the target device"
I have used the universal tool for making my system / super files rewritable as I initially couldn't mount them in twrp.
If I use fastboot I have to remove twrp because fastboot flash system system.img requires to be loaded into fastbootd via fastboot reboot fastboot.
However when I do that it does not work. How do I go about flashing a gsi now that I've gotten this far?
Steps taken:
1. Stock firmware Via sp tool
2. Flash magisk patched img (obtain root)
3. Flash twrp to recovery
4. Use the universal tool to change super partitions to rewritable
5. Mount system, attempt gsi install via twrp (fails)
Just want to get rid of the damn stock ROM and it's spyware.
Hi. You can write what you trwp flash to doggee?
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
now they have a proper 12S Ultra section!
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to "Advanced" and "flash this twrp."
edit: the recovery image file is too large to be flashed directly via fastboot, so you need to boot first then flash using twrp!
edit2: backup and restore function may not be working properly on this version of twrp! I get boot loops everytime I do a full system backup and full restore after bricking the device, especially on the data partition. Clean installing rom then restoring data only still get boot loops. so use it with caution.
I suggest you to use 3rd party backup apps to do backups on apps and data, and stick to the flashing and other functions only for twrp.
original source unofficialtwrp.com
Nabicook said:
12S Ultra unofficial TWRP - link MEGA
Credit - UnofficialTWRP
They released TWRP under 12S Pro, but the code name is Thor which stands for 12S Ultra, and after flashing, I do confirm this is for 12S Ultra.
Download the image and rename as recovery.img for simplicity.
fastboot boot recovery.img (or full file name)
in TWRP, go to Advanced and flash this twrp.
original source unofficialtwrp.com
Click to expand...
Click to collapse
Awesome thanks. But why not Fastboot flash recovery recovery.img?
No. You must type fastboot flash boot recovey. img
dungnghien said:
No. You must type fastboot flash boot recovey. img
Click to expand...
Click to collapse
No I'm pretty sure it's:
fastboot flash recovery twrp.img
However my question was why the method outlined by @Nabicook vs this method. Is it because of the dual partition?
GodKingKnight said:
Awesome thanks. But why not Fastboot flash recovery recovery.img?
Click to expand...
Click to collapse
Because not only it is the method unofficialtwrp suggested, but also the size of the recovery img file is too large to be flashed via fastboot.
I already tried
fastboot flash recovery recovery.img
fastboot flash recovery_a recovery.img
and so on, but all failed.
only way to properly install this version of twrp is to boot first then let twrp to install itself to both a/b partitions.
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
joiliko said:
Hi!
I'm following your guide...and after uploading recovery nothing happens
rebooting into recovery through ADB or just using buttons...still sends me into fastboot mode
What can I do?
Click to expand...
Click to collapse
are you sure you did
fastboot boot (your recovery file name).img
it should automatically boot into twrp without touching anything from fastboot mode.
then install twrp through the advanced option in twrp
Nabicook said:
are you sure you did
fastboot boot (your recovery file name).img
Click to expand...
Click to collapse
Great many thanks! I was actually doing flash boot
Nabicook said:
then install twrp through the advanced option in twrp
Click to expand...
Click to collapse
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
yeah you can try flashing stock boot img, and if that doesnt work, you can download fastboot rom and flash stock rom using flash all without wiping data(there is .bat file that says something like install without formatting).
That will fix any kind of brick issues of xiaomi device, and you just redo the twrp part.
joiliko said:
Still having issues:
After flashing twrp + magisk, reboot sends me into fastboot mode ..
As I get it, previously I've messed up with boot image, flashing recovery into that partition
So question is:
Do I need to reflash stock boot.img (need help with getting it, stock recovery rom is packed into .bin and I'm unable to extract boot image
Or can I simply reflash stock ROM (in recovery or fastboot mode?)
*my phone is unlocked already
Click to expand...
Click to collapse
How to Extract payload.bin and get stock boot image file
To extract the payload.bin file from Android stock firmware and get stock boot image file, you should refer to the instructions given in here.
www.droidwin.com
My idea worked!
I used the method above to extract boot.img & flashed it successfully
Can someone tell me why wipe data and settings dosent work on my 12s ultra every time reboots the twrp after i press the icon... Im try at 7.5 version the same and on 7.2
Hi,
sorry to take your time
I'm french so also sorry for my english
I have installed TWRP 3.51 on my poco x3 pro using ADB
fastboot flash recovery twrp.img
sending
writing
finish
fastboot boot twrp.img
After install phone boot in twrp.
I then use the option booting system and the phone boot again in TWRP
Then i used a boot.img from a rom stock
fastboot flash boot boot.img
I also tried fastboot flash vbmeta vbmeta.img
without success
Each time the phone boot in TWRP
regards
alain
Ps I'm not an expert to please explain as much as you can
Dude what?
Fastboot Flash recovery recovery.img
That's it!
Hold Volume Up+ Power to boot the device to boot into Recovery.
Go to install and select customRomFileOfYourChoice.zip to install it.
Maybe needs a format Data to wipe failed encryption.
Reboot to system.
Done
Haldi4803 said:
Dude what?
Fastboot Flash recovery recovery.img
That's it!
Hold Volume Up+ Power to boot the device to boot into Recovery.
Go to install and select customRomFileOfYourChoice.zip to install it.
Maybe needs a format Data to wipe failed encryption.
Reboot to system.
Done
Click to expand...
Click to collapse
thank you
a stock rom or a custom rom ?
custom ROM.
Stock rom has to be flashed differently.
alix264 said:
Hi,
sorry to take your time
I'm french so also sorry for my english
I have installed TWRP 3.51 on my poco x3 pro using ADB
fastboot flash recovery twrp.img
sending
writing
finish
fastboot boot twrp.img
After install phone boot in twrp.
I then use the option booting system and the phone boot again in TWRP
Then i used a boot.img from a rom stock
fastboot flash boot boot.img
I also tried fastboot flash vbmeta vbmeta.img
without success
Each time the phone boot in TWRP
regards
alain
Ps I'm not an expert to please explain as much as you can
Click to expand...
Click to collapse
You need to install a custom ROM and format the data. If you are using an Android 12 or 13 ROM the data partition is encrypted that's why you're phone is boot looping
its working... I had to format data
thank you very much
All is working now. magisk installed (with trwp), lsposed install
But If i'm going in trwrp backup option, I don't see "system"
?
you have to mount the system partition first and set it via terminal to read/write i think.
But i am also not professional mhh..
Try mount it and when u cant Backup it ask again for help