Database Info

Blackview A60 Pro Help With Custom Recovery Please

Hi, so I have a Blackview A60 which I adore for the price, fantastic!
Looking to get custom recovery to get Magisk up and running.
I've flashed a 3.1.1 twrp (apparently for Blackview A60 Pro) which caused a bootloop
I had to stock rom it via fastboot.
It's working, however I've tried a few Twrp version via fastboot boot <img's>
Any help in trying to get one to function? Cheers.
Android 9.0
Edit: I got Magisk working with a back up patched boot.img, didn't think to try flashing it since it was a patch of the boot.img before I updated. I'm a dope.

You need to flash vbmeta with --disable-verity --disable-verification, that fixed my bootloop and my twrp worked.

Hi,
Could you please let me know which recovery and vbmeta files you used?
Thanks in advance.

Hi all,
Quick follow-up to my question, and hopefully some help for others.
I did NOT flash TWRP because I wanted to used an Android 10 GSI roms (and TWRP doesn't support, yet, Android 10). However I did flash a custom Android 10 ROM.
Here is what I did :
* Activate bootloader OEM unlock from boot ;
* Reboot phone to fastboot, then "fastboot flashing unlock" ;
* Get vbmeta file from here : https://developer.android.com/topic/generic-system-image/releases ;
* Flash it : "fastboot --disable-verification flash vbmeta vbmeta.img" ;
* Then erase system : "fastboot erase system" ;
* Flash your desired rom : "fastboot flash system your_desired_iso.img" ;
* Wipe user data : "fastboot -w"
* Reboot : "fastboot reboot" and voilà !
Source, mainly DuckDuckGo searches + https://source.android.com/setup/build/gsi#flashing-gsis

Nesousx said:
Hi all,
Quick follow-up to my question, and hopefully some help for others.
I did NOT flash TWRP because I wanted to used an Android 10 GSI roms (and TWRP doesn't support, yet, Android 10). However I did flash a custom Android 10 ROM.
Here is what I did :
* Activate bootloader OEM unlock from boot ;
* Reboot phone to fastboot, then "fastboot flashing unlock" ;
* Get vbmeta file from here : https://developer.android.com/topic/generic-system-image/releases ;
* Flash it : "fastboot --disable-verification flash vbmeta vbmeta.img" ;
* Then erase system : "fastboot erase system" ;
* Flash your desired rom : "fastboot flash system your_desired_iso.img" ;
* Wipe user data : "fastboot -w"
* Reboot : "fastboot reboot" and voilà !
Source, mainly DuckDuckGo searches + https://source.android.com/setup/build/gsi#flashing-gsis
Click to expand...
Click to collapse
Thank you for the details.
Can you tell me of the Blackview A60 Pro works OK with GSI (phhusson). I am interested in general browsing, whatsapp, basic -camera. (no games).

EtoileLabrie said:
Thank you for the details.
Can you tell me of the Blackview A60 Pro works OK with GSI (phhusson). I am interested in general browsing, whatsapp, basic -camera. (no games).
Click to expand...
Click to collapse
Hi,
I think it does, but don't remember. I tried many roms, but then returned the phone to Amazon. I did not really like it for everyday use.

thank you for the reply. I am wondering to buy but it is very heavy!

How to flash GSIs on devices with dynamic super partition

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 links​to 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

[CLOSED][GUIDE] Avoid Overwriting TWRP by your Stock OEM Recovery [All Devices][R][11]

After a long investigation, i find out that the command " fastboot boot <twrp-xxxx>.img " is no longer working in Android [11] to avoid overwriting TWRP by the Stock OEM Recovery. Because the code to do this wicked job, after every reboot, is now inside the stock "init" binary.
So to finally stop this mess, after flashing your TWRP (better to be in raw.img) with this command :
fastboot flash recovery <twrp-xxxx>.img
type :
fastboot reboot recovery
Then, flash Magisk (rename it to .zip) in TWRP menu ... This will overwrite the original "init" with the Magisk one ... That's All !
This workaround should work for all devices with android 11 oem software pre-installed ! (tested on my POCO X3 NFC and oneplus 8 too)
Cheers

What do you mean by "raw.img"? I attempted to do this from the bootloader on my OnePlus 6 (with Lineage OS 18.1 and latest firmware from OnePlus) and got a '(recovery_a) No such partition' error.

gringo80 said:
After a long investigation, i find out that the command " fastboot boot <twrp-xxxx>.img " is no longer working in Android [11] to avoid overwriting TWRP by the Stock OEM Recovery. Because the code to do this wicked job, after every reboot, is now inside the stock "init" binary.
So to finally stop this mess, after flashing your TWRP (better to be in raw.img) with this command :
fastboot flash recovery <twrp-xxxx>.img
type :
fastboot reboot recovery
Then, flash Magisk (rename it to .zip) in TWRP menu ... This will overwrite the original "init" with the Magisk one ... That's All !
This workaround should work for all devices with android 11 oem software pre-installed ! (tested on my POCO X3 NFC and oneplus 8 too)
Cheers
Click to expand...
Click to collapse
Hello, recently flashed MIUI 12 on POCO X and tried:
Code:
fastboot reboot recovery
But it gives me:
fastboot: usage: unknown reboot target recovery
Its the command correct?

darkvier said:
Hello, recently flashed MIUI 12 on POCO X and tried:
Code:
fastboot reboot recovery
But it gives me:
fastboot: usage: unknown reboot target recovery
Its the command correct?
Click to expand...
Click to collapse
POCO X ??? WOW ... I never heard about that phone !
Check first your bootloader status ! locked or unlocked ???
Update your adb/fastboot binaries ... or use this ones.
If that command doesn't work, use this one :
fastboot boot <your-flashed-twrp-xxx>.img

gringo80 said:
POCO X ??? WOW ... I never heard about that phone !
Check first your bootloader status ! locked or unlocked ???
Update your adb/fastboot binaries ... or use this ones.
If that command doesn't work, use this one :
fastboot boot <your-flashed-twrp-xxx>.img
Click to expand...
Click to collapse
yes, quite a famous xiaomi phone hahaha ...
My bootloader is unlocked, fastboot boot img worked because i flashed lineageos below (i think)
mmm i think my adb and fastboot from 2018 are not up to date hahaha I'm an oldfag

Thread closed at op's request.
strongst
XDA Staff

[CLOSED]Pixel-S-Stable-redfin-AB-12

Gsi for Nokia 6.1 2018 pl2
Flash it on your risk .i am not responsible if you break your mobile
1)Flash lineage 18.1 using any recover like TWRP, lineage recovery or Pixel recovery
2) extract the image
3) now go to bootloader
4) Now flash the GSI using fastboot
Commands for flashing image GSI
Fastboot flash system ( image name and path)
Fastboot-w
Fastboot reboot
6) now wait for GSI to boot
7) enjoy GSI
[Mod Edit] Links removed
updating soon

[Thread Closed] Due to violations of our Forum Rules, potential harmful intent and lack of constructive feedback.

ROOT RMX2117 Realme Narzo 30 Pro

GSI flashing guide for mediatek uplaoded- checkout
Rooting Realme Narzo 30 Pro:
New Method (Android 10 and above)
Go to this link
Also checkout how to flash stock rom if you face any problems such as bootloop:
link
Old Method (Android 11 and below)
Prerequisite :
Unlocked Bootloader
How to unlock bootloader: Phone will be formatted
Backup your data.
Install deeptesting.apk
Open the app and click start applying
Wait for application to be summited and processed
Minimize the app and head over to developer settings and turn on OEM Unlock and USB Debugging
Open deeptesting again and click on start in-depth test, the phone will reboot to bootloader
Connect phone to PC. Open platform-tools folder and type cmd in address bar
Type fastboot flashing unlock
Use volume and power button to select unlock the bootloader
Phone will format and reboot.
Realme Narzo 30 Pro (C.12) :
How to root ? Can cause bootloop or even brick your device
Download boot.img and vbmeta.img
Patch only the boot.img using this version of Magisk
Connect your phone to PC via USB Cable open cmd in platform-tools folder type adb command : adb reboot bootloader
Now your device is in fastboot mode
Firstly flash vbmeta.img file
Command for flashing vbmeta.img : fastboot --disable-verity --disable-verification flash vbmeta drag and drop vbmeta file
Now flash patched boot.image file
Command for flashing boot.img : fastboot flash boot drag and drop patched boot image file
Reboot your device with command : fastboot reboot
Your device is rooted now ╰(*°▽°*)╯
You can uninstall this version of magisk after rebooting and install the latest version
Other Files (C.12) :
Recovery.img
For rooting older versions :
Follow the same procedure, using the files, boot.img and vbmeta.img for specific version.
Extras:
Scatter file :
MT6853 Scatter.txt

Please Share Boot.img Of C.09

Files required for C.09 have been uploaded please check

I think the end command is : fastboot reboot

Ignacius57294 said:
I think the end command is : fastboot reboot
Click to expand...
Click to collapse
Yup

NinjaChunks said:
Yup
Click to expand...
Click to collapse
Ohh nice man you corrected it...

NinjaChunks said:
Files required for C.09 have been uploaded please check
Click to expand...
Click to collapse
Please share files boot.img of c11

please share boot.img of c.11

KIRANKEJITON said:
please share boot.img of c.11
Click to expand...
Click to collapse
It will be posted soon

NinjaChunks said:
Realme Narzo 30 pro (C.011) :
How to unlock bootloader Phone will be formatted :
Backup your data.
Install deeptesting.apk.
Open the app and click start applying.
Wait for application to be summited and processed.
Minimize the app and head over to developer settings and turn on OEM Unlock and USB Debugging.
Open deeptesting again and click on start in-depth test, the phone will reboot to bootloader.
Connect phone to PC. Open platform-tools folder and type cmd in address bar.
Type fastboot flashing unlock.
Use volume and power button to select unlock the bootloader.
Phone will format and reboot.
How to root Can cause bootloop or even hardbrick your device :
Download boot.img and vbmeta.img.( Credit : ashkir05)
Patch only the boot.img using this version of Magisk other versions of Magisk doesn't seem to be working.
Connect your phone to PC via USB Cable open cmd in platform-tools folder type adb command : adb reboot bootloader
Now your device is in fastboot mode
Firstly flash vbmeta.img file.
Command for flashing vbmeta.img : fastboot --disable-verity --disable-verification flash vbmeta drag and drop vbmeta file.
Now flash patched boot.image file.
Command for flashing boot.img : fastboot flash boot drag and drop patched boot image file.
Reboot command: fastboot reboot.
Your device is rooted now ╰(*°▽°*)╯
You can uninstall this version of magisk after rebooting and install the latest version
Other Files (C.011) :
MT6853 Scatter.txt
Recovery.img
For rooting older versions :
Follow the same procedure, just use the files provided for specific version.
Realme Narzo 30 pro (C.09) :
Download boot.img and vbmeta.img.
Other Files (C.09) :
MT6853 Scatter.txt
Recovery.img
Realme Narzo 30 pro (C.08) :
Download boot.img and vbmeta.img.
Other Files (C.08) :
MT6853 Scatter.txt
Recovery.img
Click to expand...
Click to collapse
after flashing boot.img , phone is not booting but it is getting looped into bootloader.
Please help

rizwanp880 said:
after flashing boot.img , phone is not booting but it is getting looped into bootloader.
Please help
Click to expand...
Click to collapse
Go to bootloader and flash stock boot.img
You would used other version of Magisk maybe

Bro how about realme 8 5g?

Please share img files for UI 3.0

It worked very well for c12 and I was also able to flash twrp/pwrp. But UI3.0 ota was not installing thus forced me to revert to stock.

TOPDOG3518 said:
It worked very well for c12 and I was also able to flash twrp/pwrp. But UI3.0 ota was not installing thus forced me to revert to stock
Click to expand...
Click to collapse
Stock boot.img is required for ota. Flash stock boot image then update.
To root again, get the boot.img for the software version your phone is running on and patch with magisk. Flash the patched boot.img and voila you have rooted.

Glad that you did. Any idea about custom rom on Narzo 30 Pro? as Realme excluded this device in her Android 14 update.

I am using Realme 3.0. Any good way to root and unlock bootloader without getting bricked?

Oops! We broke the matrix. Someone call Neo!
getting this error while try to download any file