Related
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
Hello,
How can i boot up custom ROM Android (LineageOS) ?
Do i need to have change something inside boot.img / or something command?
Note:
Phone (Umidigi Power)
Android 9
Unlocked bootloader,
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
What i want is:
1. I want a Custom OS like (LineageOS)
2. Install another ROM or fix the stock ROM
What i found out.
1. After flash a system i got bootloop, see umdiigi power boot logo and reboot
2. Stock ROM / deos not work anymore before i get black screen
3. use alot of commands and nothing working
4. try to install system from TWRP but bootloop
Questions is (I think):
How i can fix it or install custom OS
Can you help me?
Thanks for your time
007fred62 said:
Hello,
How can i boot up custom ROM Android ?
Do i need to have change something inside boot.img?
Note:
Phone (Umidigi Power)
Android 9
Unlocked bootloader,
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.im
Can you help me?
Thanks for your time
Click to expand...
Click to collapse
look up for Project Treble this are custom rom that only require you to flash system.img
The Fastboot command mentioned only prepares phone to allow modifications of Android system, e.g. for installing a Custom ROM. A Custom ROM gets flashed via a Custom Recovery you flashed before.
ineedroot69 said:
look up for Project Treble this are custom rom that only require you to flash system.img
Click to expand...
Click to collapse
there to download it?
jwoegerbauer said:
The Fastboot command mentioned only prepares phone to allow modifications of Android system, e.g. for installing a Custom ROM. A Custom ROM gets flashed via a Custom Recovery you flashed before.
Click to expand...
Click to collapse
I have try this command:
fastboot --disable-verity --disable-verification flash system system.img
still not boot up after this command
007fred62 said:
I have try this command:
fastboot --disable-verity --disable-verification flash system system.img
still not boot up after this command
Click to expand...
Click to collapse
As I can see you didn't get it.
what? you want custom recovery like TWRP or custom rom like LineageOS?
also we can barely understand you.. please write in full sentence don't type fragment phrases
ineedroot69 said:
what?you want custom recovery like TWRP or custom rom like LineageOS?
Click to expand...
Click to collapse
Sorry for my Questions. updated post 1.
i trying to find another custom OS or fix the system.
Yes like LineageOS
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
Thought to share with you guys, as many of people like me face problem while disabling the verification while flashing VBMETA.img.
Most of the time the below command does not work and causes bootloop, when Installing Custom recovery.
So i searched a lot and found the perfect solution which is working 100% and tested personally.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
The errors we receive while flashing this command is due to SDK platform tools version
30.0.5 version is working fine and i have attached it along with this post so nobody else will go through the searching i have went.
This is the whole sole purpose of this thread.
Can you tell me how to do it with Heimdall on Linux? Using this file attached below, but i also ask you, is this file i posted only special for my device? The guy who told me to flash this told me to use odin and place the file on ap slot, just like how i previously flashed the custom recovery.
hi ,may i ask which first, do i need to flash the vbmeta before custom rom?. thanks much appreciated
Luffy83 said:
hi ,may i ask which first, do i need to flash the vbmeta before custom rom?. thanks much appreciated
Click to expand...
Click to collapse
Recovery, VBMETA (if required), Rom, (Microg if you want, i never recommend), and magisk root if you wanna root.
SignatureBoy said:
Thought to share with you guys, as many of people like me face problem while disabling the verification while flashing VBMETA.img.
Most of the time the below command does not work and causes bootloop, when Installing Custom recovery.
So i searched a lot and found the perfect solution which is working 100% and tested personally.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
The errors we receive while flashing this command is due to SDK platform tools version
30.0.5 version is working fine and i have attached it along with this post so nobody else will go through the searching i have went.
This is the whole sole purpose of this thread.
Click to expand...
Click to collapse
can also be wrote this way : fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
This is a very important post.
I am currently having poco m2, and previously I tried flashing costom recovery but everytime got stucked into boot loop, so what should I do, regarding vbmeta, anyone can help - which step should I follow to flash costom rom and vemeta + for fixing bootloop issue in Xiaomi phone , do we have to flash vbmeta
Vedant2 said:
I am currently having poco m2, and previously I tried flashing costom recovery but everytime got stucked into boot loop, so what should I do, regarding vbmeta, anyone can help - which step should I follow to flash costom rom and vemeta + for fixing bootloop issue in Xiaomi phone , do we have to flash vbmeta
Click to expand...
Click to collapse
Are you sure your custom recovery works for your phone? You need to flash vbmeta to get rid of the AVB verification steps, otherwise you end up with a non-booting system because of the differences in keys built in to the hardware, the system partition and the boot partition.
Can anyone tell me, i am having poco m2 Xiaomi , what's the use of vbmeta and is it compulsory to flash vbmeta while flashing custom rom or recovery.
Just used the latest adb tools on cmd admin. Fixed
Download Platform Tools for Android SDK Manager
Download Android SDK Platform-tools 29.0.0 , 29.0.0 , 30.0.0 , 30.0.0 , 31.0.0 , 31.0.0 , 31.0.0 , 33.0.0 , 33.0.0 , 33.0.0 , 34.0.0 ,
androidsdkmanager.azurewebsites.net
You Want Video turorial ?
Cheack This Out;- https://forum.xda-developers.com/t/...stom-rom-installation-video-tutorial.4583503/
Tutorial Install Custom rom Selene
Requirements :
- Unlocked Bootloader
- PC / Laptop with working adb fastboot, SP Flash Tools
- recovery and fastboot MIUI Stock ROM ( ID, EEA, Global, CN, Taiwan / pick one that work, or your currently ROM Version )
- put your recovery miui ROM & custom rom to Microsd / OTG
How To : (If you never update OTA then go STEP 1, else go STEP 2)
- BACKUP YOUR IMEI FIRST (on twrp and backup it to another storage or cloud)
STEP 1
- boot to fastboot mode
- flash twrp / ofox command type on minimal adb fastboot "fastboot flash boot nametwrpfile.img" (make sure the twrp file on same folder at the minimal adb fastboot folder)
- press vol + & power
- Format Data
- Yes
- install / flash MIUI Recovery rom, check reflash TWRP / OFOX
- reboot to "BOOTLOADER"
After reboot to bootloader,Device will be in fastboot.
- flash vbmeta " fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img " (make sure the twrp file on same folder at the minimal adb fastboot folder)
- reboot "fastboot reboot " ( if success booting up to system go to STEP 2, if not success, read again from start )
STEP 2
- no need to setup anything, you can skip all that MIUI Setup
- reboot to twrp recovery, press vol + & power
- Format Data
-Yes
- install / flash Custom rom with check automatically reflash TWRP after flashing a ROM checked
- reboot ( If you skipped STEP 1 and not booting, back to fastboot or TWRP, then Go to STEP 1 first, if can't boot to either TWRP / Fastboot, Then you need MTK Bypass + SP Flash Tool)
- ( If you DONE STEP 1 but still no luck check SPECIAL CASE )
- DONE
SPECIAL CASE
if your phone bootloop on mi logo, then do:
- reboot to twrp/recovery, press vol + & power (wait it, be patient)
-If not boot on TWRP, Go to Fastboot
-Reflash TWRP [fastboot flash boot twrp.img]
-Now Boot in to TWRP
- install image boot.img on boot partition from miui rom you have used on first step (see above)
- reflash twrp, install image twrp.img on recovery ramdisk
- [Even if you go to TWRP Without Reflashing again,you still need to flash boot.img on boot and twrp on ramdisk]
- reboot system
- setup phone with ur mobile internet data (if the custom rom have gapps), cause ur wifi bluetooth hotspot are died
- go to twrp again, install custom kernel to fix bug wifi hotspot bluetooth (but u can't instal yukina starlight, it will make bootloop, use another I Will Recomend Yukina Stamine)
- done u can reboot system
N.B. - If You are in MIUI 13,Then it will won't Work,First Downgrade to MIUI 12.5.xx
N.B. - Just Do Normal Format,Dont Wipe like Delvik,cache,System,Vendor etc.
N.B. - Try To Take All Files(Twrp.img,boot.img,miui recovery.zip,Custom rom zip, custom kernel.zip) In your Memory card and Avoid Use OTG
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
not working in my device
fastboot flash boot twrp.img
my device went in bootloop
i have also tried
Fastboot boot twrp.img
this is throwing " status read failed (too many links)
(also tried with downgrading to MIUI-12 but no success)
Then i tried to boot into fastbootD mode.
with command "Fastboot reboot fastboot"
Now my device is in the infinite boot loop.
Please help
Is that Redmi 10 Selene ?
And Which twrp you used ?
Neelthegamer007 said:
Is that Redmi 10 Selene ?
And Which twrp you used ?
Click to expand...
Click to collapse
is its redmi 10 selene
and i have used twrp you placed here
NOOBOHOLIC said:
is its redmi 10 selene
and i have used twrp you placed here
Click to expand...
Click to collapse
Install miui 12.5.** with fastboot rom,and then unlock bootloader or if its unlocked then disable security by flashing vbmeta.img , comand on post.
Then flash TWRP
fastboot flash boot [space] drag and drop twrp.img file,after flashing reboot your device by holding power button.
Neelthegamer007 said:
Install miui 12.5.** with fastboot rom,and then unlock bootloader or if its unlocked then disable security by flashing vbmeta.img , comand on post.
Then flash TWRP
fastboot flash boot [space] drag and drop twrp.img file,after flashing reboot your device by holding power button.
Click to expand...
Click to collapse
But nothing is working now its just stucked in the bootloop
not booting into recovery
not booting into fastboot
how i do it further
You need SP flash tool, and mtk auth bypass just download it, bypass mtk auth and go to sp flash tool, on auth file section select mtk scatter file from miui fastboot rom/images folder, and on sp flash tool un select every file except boot or boot.img
And click the download button [ must be sure that you need to only download the boot.img file,no other file.]
After download,you can go fastboot
If you can't understand
Get help from YouTube.
I only want root. Is it better to install magisk from this twrp(After downgrading). Or staying in miui 13 & flashing patched boot image?
Tawsif999 said:
I only want root. Is it better to install magisk from this twrp(After downgrading). Or staying in miui 13 & flashing patched boot image?
Click to expand...
Click to collapse
If you only root,then take miui 13 rom's fastboot file and extract boot.img, patch with magisk anf flash vbmeta 1st and then patched boot.img eith adb, enough
Tawsif999 said:
I only want root. Is it better to install magisk from this twrp(After downgrading). Or staying in miui 13 & flashing patched boot image?
Click to expand...
Click to collapse
Downgrade is not nessesery with only root
Neelthegamer007 said:
If you only root,then take miui 13 rom's fastboot file and extract boot.img, patch with magisk anf flash vbmeta 1st and then patched boot.img eith adb, enough
Click to expand...
Click to collapse
Are you sure I need the fastboot rom only. Because I'm already downloading a recovery rom.
And after downloading I have to flash the vbmeta.img before flashing patched boot image? But why? vbmeta is already included in the rom. Can you please explain this.
Tawsif999 said:
Are you sure I need the fastboot rom only. Because I'm already downloading a recovery rom.
And after downloading I have to flash the vbmeta.img before flashing patched boot image? But why? vbmeta is already included in the rom. Can you please explain this.
Click to expand...
Click to collapse
You need to flash vbmeta for disabled verified boot, otherwise patched boot.img is not verified,so flashing patched boot.img will be fail or will be cause of a bootloop
And as i know on recovery rom you won't get the boot.img file,but i,m not sure if you got on recovery rom then it's also file,i will work,and i,m 100 % sure, and vbmeta is inside the rom for enable verified boot,but you need to disable it to flash patched boot img file,its necessary for most of the devices,but in some device, its not necessary,but why would you take risk of a unwanted bootloop?
Disable vbmeta command
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Any other query's ?, just reply....
Neelthegamer007 said:
You need to flash vbmeta for disabled verified boot, otherwise patched boot.img is not verified,so flashing patched boot.img will be fail or will be cause of a bootloop
And as i know on recovery rom you won't get the boot.img file,but i,m not sure if you got on recovery rom then it's also file,i will work,and i,m 100 % sure, and vbmeta is inside the rom for enable verified boot,but you need to disable it to flash patched boot img file,its necessary for most of the devices,but in some device, its not necessary,but why would you take risk of a unwanted bootloop?
Disable vbmeta command
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Any other query's ?, just reply....
Click to expand...
Click to collapse
Thank you very much. I thought I have to flash using fastboot flash vbmeta vbmeta.img. But now I can understand, the command is not for flashing. It's for disabling verification.
Tawsif999 said:
You are most welcome
Click to expand...
Click to collapse
can you tell me more for install custom rom i try 5days and 50time bootloop please help
Teaykhuad said:
can you tell me more for install custom rom i try 5days and 50time bootloop please help
Click to expand...
Click to collapse
Sure,are you active right now ? Reply again,i eill give you my telegram..
yes i trying to booting now i dm you
Teaykhuad said:
yes i trying to booting now i dm you
Click to expand...
Click to collapse
How's your experience?
Neelthegamer007 said:
How's your experience?
Click to expand...
Click to collapse
Good bro You teach me to flash custom rom and pixel expirence is not bad but im go to miui and install https://forum.xda-developers.com/t/ultra-rooted-miui-package.4487967/ this for speed and fast animation
Neelthegamer007 said:
Tutorial Install Custom rom Selene
Requirements :
- Unlocked Bootloader
- PC / Laptop with working adb fastboot, SP Flash Tools
- recovery and fastboot MIUI Stock ROM ( ID, EEA, Global, CN, Taiwan / pick one that work, or your currently ROM Version )
- put your recovery miui ROM & custom rom to Microsd / OTG
How To : (If you never update OTA then go STEP 1, else go STEP 2)
- BACKUP YOUR IMEI FIRST (on twrp and backup it to another storage or cloud)
STEP 1
- boot to fastboot mode
- flash twrp / ofox command type on minimal adb fastboot "fastboot flash boot nametwrpfile.img" (make sure the twrp file on same folder at the minimal adb fastboot folder)
- press vol + & power
- Format Data
- Yes
- install / flash MIUI Recovery rom, check reflash TWRP / OFOX
- reboot to "BOOTLOADER"
After reboot to bootloader,Device will be in fastboot.
- flash vbmeta " fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img " (make sure the twrp file on same folder at the minimal adb fastboot folder)
- reboot "fastboot reboot " ( if success booting up to system go to STEP 2, if not success, read again from start )
STEP 2
- no need to setup anything, you can skip all that MIUI Setup
- reboot to twrp recovery, press vol + & power
- Format Data
-Yes
- install / flash Custom rom with check automatically reflash TWRP after flashing a ROM checked
- reboot ( If you skipped STEP 1 and not booting, back to fastboot or TWRP, then Go to STEP 1 first, if can't boot to either TWRP / Fastboot, Then you need MTK Bypass + SP Flash Tool)
- ( If you DONE STEP 1 but still no luck check SPECIAL CASE )
- DONE
SPECIAL CASE
if your phone bootloop on mi logo, then do:
- reboot to twrp/recovery, press vol + & power (wait it, be patient)
-If not boot on TWRP, Go to Fastboot
-Reflash TWRP [fastboot flash boot twrp.img]
-Now Boot in to TWRP
- install image boot.img on boot partition from miui rom you have used on first step (see above)
- reflash twrp, install image twrp.img on recovery ramdisk
- [Even if you go to TWRP Without Reflashing again,you still need to flash boot.img on boot and twrp on ramdisk]
- reboot system
- setup phone with ur mobile internet data (if the custom rom have gapps), cause ur wifi bluetooth hotspot are died
- go to twrp again, install custom kernel to fix bug wifi hotspot bluetooth (but u can't instal yukina starlight, it will make bootloop, use another I Will Recomend Yukina Stamine)
- done u can reboot system
N.B. - If You are in MIUI 13,Then it will won't Work,First Downgrade to MIUI 12.5.xx
N.B. - Just Do Normal Format,Dont Wipe like Delvik,cache,System,Vendor etc.
N.B. - Try To Take All Files(Twrp.img,boot.img,miui recovery.zip,Custom rom zip, custom kernel.zip) In your Memory card and Avoid Use OTG
View attachment 5793645
Click to expand...
Click to collapse
How do I restore WiFi and Bluetooth after flashing