Has anyone gotten a gsi working with the galaxy A105M/DS? I have tried aosp pie and lineage 16.0 pie arm32_binder64 A/B but both were stuck at the logo screen.
Samsung phones have a weird habbit of staying stuck on bootanimation on some Pie GSI.
Try this:
Delete the following file with TWRP file manager: system/bin/rw_system.sh
Then reboot
Hopefully it works!
ShaDisNX255 said:
Samsung phones have a weird habbit of staying stuck on bootanimation on some Pie GSI.
Try this:
Delete the following file with TWRP file manager: system/bin/rw_system.sh
Then reboot
Hopefully it works!
Click to expand...
Click to collapse
Thank you so much <3 it worked!
I was finally able to successfully boot up lineage os and it works like a charm
parthibratan said:
Has anyone gotten a gsi working with the galaxy A105M/DS? I have tried aosp pie and lineage 16.0 pie arm32_binder64 A/B but both were stuck at the logo screen.
Click to expand...
Click to collapse
Hi parthibratan can you tell me how you successfully flashed twrp on your device?!!
@ShaDisNX255 According to what i have studied in Samsung phones. Their bootanimation format is .qmg unlike .png in other mobiles. This maybe a reason to bootloop too as gsi's are made for all supported devices and changes in the stock bootanimation may cause a bootloop too! I actually need a help. I have the Samsung Galaxy A10 (A105F/DS) which is rooted using magisk and flashed twrp v.3.3.1 and i wanna gsi roms such as lineage os 16 and 17 , aosp , viper os etc., But , am afraid that my phone will get stuck in bootloop as this is my only device in my hand right now. Can i use this : Delete the following file with TWRP file manager: system/bin/rw_system.sh
Then reboot
Can you please guide me ?
Waiting for your reply ?
Infant9099 said:
@ShaDisNX255 According to what i have studied in Samsung phones. Their bootanimation format is .qmg unlike .png in other mobiles. This maybe a reason to bootloop too as gsi's are made for all supported devices and changes in the stock bootanimation may cause a bootloop too! I actually need a help. I have the Samsung Galaxy A10 (A105F/DS) which is rooted using magisk and flashed twrp v.3.3.1 and i wanna gsi roms such as lineage os 16 and 17 , aosp , viper os etc., But , am afraid that my phone will get stuck in bootloop as this is my only device in my hand right now. Can i use this : Delete the following file with TWRP file manager: system/bin/rw_system.sh
Then reboot
Can you please guide me ?
Waiting for your reply ?
Click to expand...
Click to collapse
If you are afraid of a bootloop, why not just do a full backup of your current stock ROM and if it fails, just restore
It's that easy, it doesn't matter if it doesn't boot, you can safely just return to stock
Albert pallam said:
Hi parthibratan can you tell me how you successfully flashed twrp on your device?!!
Click to expand...
Click to collapse
Yes of course
Download the twrp from here https://androidfilehost.com/?w=files&flid=306584
The U1 version of twrp didn't work for me so I used the U2 version
What I did was
1.Firstly download the firmware for my device
2.Extracted it and also extracted the boot.img.lz4 from the AP****.tar using 7zip and copied both AP*****.tar and boot.img.lz4 to my phone
3.Patched AP*****.tar using magisk manager and then patched boot.img.lz4
4.Copied both magisk_patched.tar and magisk_patched.img to my pc from my phones Download folder
5.Extracted only the vbmeta.img from the magisk_patched.tar and renamed the magisk_patched.img to recovery.img
6.Made a tar file of vbmeta.img and recovery.img using 7zip, named it patch then flashed it using odin's ap tab
7.Restarted the phone into stock recovery and factory data resetted and restarted the phone again fully booted up the phone once
8.Then renamed the downloaded twrp-a10-3.3.1-0_afaneh92_U2.img to recovery.img and created a tar of it using 7zip and named it twrp
9.Flashed the twrp.tar using odin's AP tab and voila I got twrp running on my a10
Hope this helps
ShaDisNX255 said:
If you are afraid of a bootloop, why not just do a full backup of your current stock ROM and if it fails, just restore
It's that easy, it doesn't matter if it doesn't boot, you can safely just return to stock
Click to expand...
Click to collapse
Hey it seems like I have a new problem
Turns out flashing the latest multidisabler.zip makes the phone stuck at bootanimation again
But if I don't flash multidisabler I can't copy anything into the phones Android folder it always fails
parthibratan said:
Yes of course
Download the twrp from here https://androidfilehost.com/?w=files&flid=306584
The U1 version of twrp didn't work for me so I used the U2 version
What I did was
1.Firstly download the firmware for my device
2.Extracted it and also extracted the boot.img.lz4 from the AP****.tar using 7zip and copied both AP*****.tar and boot.img.lz4 to my phone
3.Patched AP*****.tar using magisk manager and then patched boot.img.lz4
4.Copied both magisk_patched.tar and magisk_patched.img to my pc from my phones Download folder
5.Extracted only the vbmeta.img from the magisk_patched.tar and renamed the magisk_patched.img to recovery.img
6.Made a tar file of vbmeta.img and recovery.img using 7zip, named it patch then flashed it using odin's ap tab
7.Restarted the phone into stock recovery and factory data resetted and restarted the phone again fully booted up the phone once
8.Then renamed the downloaded twrp-a10-3.3.1-0_afaneh92_U2.img to recovery.img and created a tar of it using 7zip and named it twrp
9.Flashed the twrp.tar using odin's AP tab and voila I got twrp running on my a10
Hope this helps
Click to expand...
Click to collapse
Thank you for your help!!
I have flashed lineage os 17 (android 10).
It is smooth, but no volte is working for me. As a result I can't call or install whatsapp. So I decided to go back to stock ROM!.
Albert pallam said:
Thank you for your help!!
I have flashed lineage os 17 (android 10).
It is smooth, but no volte is working for me. As a result I can't call or install whatsapp. So I decided to go back to stock ROM!.
Click to expand...
Click to collapse
VoLTE will not work on any GSI, it's a Samsung only thing for now
---------- Post added at 07:16 AM ---------- Previous post was at 07:15 AM ----------
parthibratan said:
Hey it seems like I have a new problem
Turns out flashing the latest multidisabler.zip makes the phone stuck at bootanimation again
But if I don't flash multidisabler I can't copy anything into the phones Android folder it always fails
Click to expand...
Click to collapse
I don't know what multidisabler is or what it does
How do we flash gsi on the A10? I tried to flash the linage img in twrp and it says no os installed, I assume twrp for A10 does not support flashing gsi Roms?
Cupcake 1.5 said:
How do we flash gsi on the A10? I tried to flash the linage img in twrp and it says no os installed, I assume twrp for A10 does not support flashing gsi Roms?
Click to expand...
Click to collapse
-> Flash the gsi img as system img
-> Reboot directly to TWRP
-> Then reboot to system
Related
is there a custom rom SM-A107f ?
and how to install TWRP recovery on SM-A107f?
-No
-And does not exist yet from what I can tell.
ShaDisNX255 said:
-No
-And does not exist yet from what I can tell.
Click to expand...
Click to collapse
thats a sad news
Consider this
ddiv1de said:
thats a sad news
Click to expand...
Click to collapse
Have you tried gsi roms? for more information head over to geektoandroid.com i hope this helps
Infant9099 said:
Have you tried gsi roms? for more information head over to geektoandroid.com i hope this helps
Click to expand...
Click to collapse
I've tried a couple, none have booted for me.
GSI Treble rom
ShaDisNX255 said:
I've tried a couple, none have booted for me.
Click to expand...
Click to collapse
I currently have a Samsung galaxy A105F/DS-U3 and it supports treble and seamless update - a/b. I have searched and it has lineageOS , Paranoid android and ViperOS. I'm gonna try LineageOS 17.0 - which gives me Anddroid Q. I'll let you know if i find one for you.
Infant9099 said:
I currently have a Samsung galaxy A105F/DS-U3 and it supports treble and seamless update - a/b. I have searched and it has lineageOS , Paranoid android and ViperOS. I'm gonna try LineageOS 17.0 - which gives me Anddroid Q. I'll let you know if i find one for you.
Click to expand...
Click to collapse
You have the A10, which is a bit different than the A10s so it is most likely that any GSI that boots to your phone will not boot for mine. Besides, A10s does not have TWRP yet and A10 does
Infant9099 said:
I currently have a Samsung galaxy A105F/DS-U3 and it supports treble and seamless update - a/b. I have searched and it has lineageOS , Paranoid android and ViperOS. I'm gonna try LineageOS 17.0 - which gives me Anddroid Q. I'll let you know if i find one for you.
Click to expand...
Click to collapse
any luck pal?
Infant9099 said:
I currently have a Samsung galaxy A105F/DS-U3 and it supports treble and seamless update - a/b. I have searched and it has lineageOS , Paranoid android and ViperOS. I'm gonna try LineageOS 17.0 - which gives me Anddroid Q. I'll let you know if i find one for you.
Click to expand...
Click to collapse
any luck pal?
Can A107F (A10s) be rooted?
Rootthegalaxy said:
Can A107F (A10s) be rooted?
Click to expand...
Click to collapse
Yes.
how to root SM-A107f Samsung Galaxy A10s
ShaDisNX255 said:
Yes.
Click to expand...
Click to collapse
so this is what i did to root my A10s.
1. check what binary your phone is running I already updated mine so my phone is on Android 10 binary 6.
how to check your binary - goto setings-about phone-software info, check Baseband version so on my phone its A107FXXU6BTES the U6 indicates your binary some has U3 binary 3 or U5, S5 binary 5
once you determined your binary.
2. activate DEVELOPER OPTIONS then activate OEM UNLOCK
samfw.com/firmware/SM-A107F/XTC/A107FXXU6BTF
go to this website and download the appropriate firmware.
each will contain a BL, AP, CP, and Home_CSC.
3. once finished downloading unlock your bootloader just boot to download mode then there is an option to press and HOLD VOLUME UP to unlock bootloader then press volume up again. if it didn't reboot instantly press and hold volume up and down again just do it again until when you choose to unlockbootloader it will reboot instatly.
4. after unlocking bootloader just go through the entire process of setting up your phone keep the bootloader unlock, INSTALL Magisk manager, so yeah install magisk choose patch image then from your downloaded firmware remove the "MD5" at the end of the files so it will be AP_A107F.tar then choose the AP to patch hrough magisk
5. after patching copy the patched file to your PC extract it by WINRAR get the boot.img if its boot.img.lz4 it means patch was not sucessful
6. after getting the boot.img copy it to your phone again and patch again make sure to rename it boot.img from inside the generated patch file then compress it as TAR using 7zip
7. flash it through odin on AP section and there your magisk rooted.
sorry for the long post
nyxl said:
how to root SM-A107f Samsung Galaxy A10s
so this is what i did to root my A10s.
1. check what binary your phone is running I already updated mine so my phone is on Android 10 binary 6.
how to check your binary - goto setings-about phone-software info, check Baseband version so on my phone its A107FXXU6BTES the U6 indicates your binary some has U3 binary 3 or U5, S5 binary 5
once you determined your binary.
2. activate DEVELOPER OPTIONS then activate OEM UNLOCK
samfw.com/firmware/SM-A107F/XTC/A107FXXU6BTF
go to this website and download the appropriate firmware.
each will contain a BL, AP, CP, and Home_CSC.
3. once finished downloading unlock your bootloader just boot to download mode then there is an option to press and HOLD VOLUME UP to unlock bootloader then press volume up again. if it didn't reboot instantly press and hold volume up and down again just do it again until when you choose to unlockbootloader it will reboot instatly.
4. after unlocking bootloader just go through the entire process of setting up your phone keep the bootloader unlock, INSTALL Magisk manager, so yeah install magisk choose patch image then from your downloaded firmware remove the "MD5" at the end of the files so it will be AP_A107F.tar then choose the AP to patch hrough magisk
5. after patching copy the patched file to your PC extract it by WINRAR get the boot.img if its boot.img.lz4 it means patch was not sucessful
6. after getting the boot.img copy it to your phone again and patch again make sure to rename it boot.img from inside the generated patch file then compress it as TAR using 7zip
7. flash it through odin on AP section and there your magisk rooted.
sorry for the long post
Click to expand...
Click to collapse
HOW THA?
it worked guy
thank yu guy
I hope that you maybe able to help me as my bootloader will not load
1 The OEM UNLOCK is on
2 Have pressed buttons as instructions but the phone just switches of
guyz that they dont know how to write magisk patch with odin
i had same problem that when i started to writing i got a failed error
if your bootloader is unlocked and yu renamed patched.img to boot.img
but yu got error do this :
change your frimware
if your a10s frimware is
A107FU5ATA9 it dosent support any root . change your frimware to a107fxxs5asl3
now start patching magisk !
Mirloo_HK said:
guyz that they dont know how to write magisk patch with odin
i had same problem that when i started to writing i got a failed error
if your bootloader is unlocked and yu renamed patched.img to boot.img
but yu got error do this :
change your frimware
if your a10s frimware is
A107FU5ATA9 it dosent support any root . change your frimware to a107fxxs5asl3
now start patching magisk !
Click to expand...
Click to collapse
Hi '''Mirloo''''About rooting the (Samsung Galaxy 10s SM-A107f) I have tried most of the rooting akps with no luck (cfautoroot I have not tried yet)'''''''As for using Odin & magisk I am getting so many different instructions from different posts
1 unlock the bootloader This I have done successfully
The next steps using Magisk & Odin Start to get misleading
one site says Copy the AP to your phone and patch it where another site says says change the format of the AP file to tar by deleting .mds then copy it to your phone
I seem to get confused now as what to do next ''''Please could you give me full instructions ....Thank you
I have attempted to patch boot.img around 7 times unsuccessfully, I have the SM-A107F, can someone please send me the correctly patched boot image for my device, will be much appreciated.
i have this device, SM-A107F/DS, still no custom rom? is it possible to install lineage os?
fatdog1 said:
i have this device, SM-A107F/DS, still no custom rom? is it possible to install lineage os?
Click to expand...
Click to collapse
I'm also waiting for this. Tried flashing twrp recovery using odin but I failed. The error says "only official binaries are allowed to be flashed" tried flashing the original firmware but same error. Wondering why.
Before rooting, you'll need an unlocked bootloader. Check my previous guide here: https://forum.xda-developers.com/x3...ck-bootloader-realme-x3-t4136325/post83109505.
After unlocking, we can get started with rooting.
First, you'll want to install Magisk Manager. You can find the latest APK here: https://github.com/topjohnwu/magisk/releases.
Next, you'll need to download the latest OTA OZIP. There's a link at the end of the post for this.
While that's downloading, you'll also need to grab a copy of an OZIP extractor. Follow the link below, download the repository as a ZIP, and unzip it.
For this program to work, you'll need Python 3 installed. On Linux systems, it should already be installed. On Windows 10, you can install Python from the Store.
Open a terminal or CMD window and cd to where you extracted the OZIP extractor files.
Use pip to install the docopt module: "pip3 install docopt".
Once the OZIP has finished downloading, move it to the same folder as the extractor program.
Run the following command: "python3 ozipdecrypt.py NAME_OF_OZIP_FILE". This will take a while!
Once it's done extracting, there will be a ZIP file with the same name as the OZIP. We only need two files from here: boot.img and vbmeta.img.
Extract those two files to the same folder as the extractor program.
Copy the boot.img file to your device.
Open Magisk Manager and choose the "INSTALL" option next to the Magisk status. Tap "INSTALL" in the dialog that appears and then choose "Select and Patch a File."
Browse to where you copied your boot.img to and select it. Magisk will now patch it and create a file named magisk_patched.img in your Download folder. Copy magisk_patched.img back to your computer.
Reboot your phone into fastboot: "adb reboot bootloader". If you don't have ADB or fastboot installed (which you should, since you needed them for the previous guide), you can find the link in the bootloader unlocking guide.
Before you flash the patched boot image, you need to disable image verification, which is where the vbmeta.img comes in.
Run "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (remember, you'll probably need to unplug and replug the device after hitting Enter). This will disable boot verification and allow the patched image to actually work.
Finally, run "fastboot flash boot magisk_patched.img". This will flash the rooted boot image to your device.
Run "fastboot reboot" and let the phone boot back into the system. Check Magisk Manager and you should now be rooted!
Troubleshooting:
If you get an error that the boot image was "destroyed," don't worry. You'll just need to flash the stock boot.img and try again. Unplug your phone from your computer and wait for it to turn off. Once the screen is black, hold down VOL-DWN and PWR to enter fastboot mode. You can then run "fastboot flash boot boot.img" (where boot.img is the stock image) to restore. Reboot, then try the vbmeta and patched image flashing again.
You can get the OTA OZIPs from Realme EU's site: https://www.realme.com/eu/support/software-update.
You can get an OZIP extractor from here: https://github.com/bkerler/oppo_ozip_decrypt. (NOTE: you'll need to install the "docopt" Python module.)
OZIPs contain a boot.img, which you can extract and patch with Magisk for root. If someone else has an idea for patching Magisk into the boot.img, this is where to start.
Here's my patched boot.img for A.32. I don't recommend using this on other versions: https://www.androidfilehost.com/?w=files&flid=315334
Could you share your patched boot.img for the latest OS version? And could you check if the aux magisk module from X2 pro works to activate all aux cameras in Gcam? Thanks
Patched boot image
Thanks Zacharee1....Could someone upload the patched boot image for the latest one? Also do we have a generic version of twrp that can be installed on x3 ?? If yes, then we could try installing havoc gsi...
I've added a link to a patched A.32 boot.img.
also needed pip install pycryptodome win10
Zacharee1 said:
I've added a link to a patched A.32 boot.img.
Click to expand...
Click to collapse
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
cheth20 said:
Thanks a ton Zacharee!!
But it seems like I have A.33 version (https://www.realme.com/in/support/software-update)
I wish we had a video guide or something. Does anyone have a patched A.33 boot.img?
Click to expand...
Click to collapse
It's pretty simple to patch it yourself. Download the OZIP, use the Python tool to unencrypt it, take the boot.img file out of the created ZIP, copy it to your device, and then patch with with Magisk Manager.
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Firmware for RMX2085
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
The firmware is the same for them all.
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
phonedroid said:
Great thread @Zacharee1. I have been waiting for this!
I have one question - is it mandatory to download the OTA package and do the patching? Is it because of the absence of recovery software like TWRP yet, for the X3 Super Zoom?
Click to expand...
Click to collapse
Yes, and that's why. It might be possible to pull the boot image directly from your device, but I'm not sure.
Can someone tell me if I can use realme 6 pro vbmeta.img?
realme x3 super zoom twrp recovery bro give me
Hi Sukhad,
I updated the system to the latest OTA (39), but I do not have the latest magisk patched file. Could you kindly help me with latest version patched boot for x3 superzoom?
sukhad86 said:
https://drive.google.com/file/d/1Od99thSd_a8sCOSpDYb0KyBLOzREiG76/view?usp=sharing
From Software Update - realme (India)
Click to expand...
Click to collapse
Thanks Zacharee1!
Finally did it (15/20 year old windows machines... Win7 was dificult and finally use a win8). Worth big as root gives me a new smartphone
Had all sorts of problems (installing python... But once installed was pretty quick) mainly adb conneting...
Anyway I will share vbmeta.img attached for a38 rom.
Also link to boot img, again a38.
For A38 rom
http://www.mediafire.com/file/i9jvl1al95k40vv/magisk_patched_a38.img/file
bro please could u tell me.. help
cheth20 said:
I have RMX2085 model. So installing RMX2081 would be okay?
Actually I installed GSI ROM after this and now stuck with boot animation loops. Any idea if it would be okay to flash 2081 ROM else where can I get the one for 2085 version?
Click to expand...
Click to collapse
bro please could u tell me.. after unlocking the bootloader of realme X3 superzoom , does it breaks the fingerprint sensor?
ota update after root
Someone have experiencing ota update failed on rooted device with this procedure? I m on RMX2081EU_11.A.40 but ota update to RMX2081EU_11.A.42 fails. how to update now?
Good afternoon. I want to get a root for my X3 super zoom, but I literally do not understand all the manipulations so that your description is attached with an image (screenshots). I think it will be useful for everyone who can't.
Anyone have working patched boot.img for a46?? I'm trying and always boot destroyed. Magisk 21.4
It's really weird on official en site there is a42 soft from September but on pl site there is a46 from December.
VERY IMPORTANT:
Please make sure your boot.img version matches the ROM version . that's mean if you update your device then you have to use patch boot.img from new recovery rom.never use the old one. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
Yes you can root your phone without data loss. You do not need to you type so much command line. You have to patch the stock boot image file with magisk manager. Then you have to download a a blank vbmeta.img file.(link in this post)
Then run this command
fastboot flash vbmeta vbmeta.img
fastboot flash boot patch-boot.img
%%replace patch-boot as your file name...
I guarantee you no data loss.
Remember one thing...
You must patch the correct boot image of your rom... If you to flash a wrong version of bhoot image then you have some problem.
Suppose you update miui global 11.0.5.0 from 11.0.4.0 and you use 11.0.4.0 version patch boot image file....
Then your device boot up but you can not play any music .....i do this dump thing.....but do not worry just flash currect patch boot image and your problem is gone...
Shas45558 said:
Yes you can root your phone without data loss. You do not need to you type so much command line. You have to patch the stock boot image file with magisk manager. Then you have to download a a blank vbmeta.img file.
https://forum.hovatek.com/thread-32719.html
Go to method 3....log in to download vbmeta.img file.
Then run this command
fastboot flash boot patch-boot.img
fastboot flash vbmeta vbmeta.img
%%replace patch-boot as your file name...
I guarantee you no data loss.
Remember one thing...
You must patch the correct boot image of your rom... If you to flash a wrong version of bhoot image then you have some problem.
Suppose you update miui global 11.0.5.0 from 11.0.4.0 and you use 11.0.4.0 version patch boot image file....
Then your device boot up but you can not play any music .....i do this dump thing.....but do not worry just flash currect patch boot image and your problem is gone...
Click to expand...
Click to collapse
Hey @Shas45558, I can't root MIUI V11.0.7.0.Q having tried these steps on a friend's phone yesterday. It worked on my phone on V11.0.50.Q but I also installed that update though my bootloader is still locked as you may know
nielsync said:
Hey @Shas45558, I can't root MIUI V11.0.7.0.Q having tried these steps on a friend's phone yesterday. It worked on my phone on V11.0.50.Q but I also installed that update though my bootloader is still locked as you may know
Click to expand...
Click to collapse
Do u flash vbmeta.img?? (Download from this post)
It workes for me every time...
When any update appires you should download full recovery rom reather then otq update.
Then extract and patch boot which is insiDe the recovery rom...
It will must work...
Shas45558 said:
Do u flash vbmeta.img?? (Download from this post)
It workes for me every time...
When any update appires you should download full recovery rom reather then otq update.
Then extract and patch boot which is insiDe the recovery rom...
It will must work...
Click to expand...
Click to collapse
That's exactly what I did. Downloaded the full recovery rom and extracted it. Patched the boot.img inside images folder with Magisk canary and after copied it to my PC and flashed it via fastboot. I then flashed the vbmeta after. Do you mind sharing with me your patched boot image for V.11.0.7Q? Maybe I'll have luck with that otherwise I did everything right. Its really strange.
nielsync said:
That's exactly what I did. Downloaded the full recovery rom and extracted it. Patched the boot.img inside images folder with Magisk canary and after copied it to my PC and flashed it via fastboot. I then flashed the vbmeta after. Do you mind sharing with me your patched boot image for V.11.0.7Q? Maybe I'll have luck with that otherwise I did everything right. Its really strange.
Click to expand...
Click to collapse
You should use your phone and magisk manager To patch boot image file...
Do not use computer to patch it
I give the boot file in this post which root your redmi 9 based on global v11.0.7.0....
Do not flash it on outher version...
Extract mboot7.tar you get mboot7.img....
Flash it and enjoy root on globalv11.0.7.0....
Do not forget to flash vbmeta.img....
Flash vbmeta file then patch boot file..
Good luck..
Shas45558 said:
You should use your phone and magisk manager To patch boot image file...
Do not use computer to patch it
I give the boot file in this post which root your redmi 9 based on global v11.0.7.0....
Do not flash it on outher version...
Extract mboot7.tar you get mboot7.img....
Flash it and enjoy root on globalv11.0.7.0....
Do not forget to flash vbmeta.img....
Flash vbmeta file then patch boot file..
Good luck..
Click to expand...
Click to collapse
Thanks a lot it worked!!! :good:
I've been patching using Magisk Manager canary version on the phone. What version of Magisk Manager did you use It's really strange
nielsync said:
Thanks a lot it worked!!! :good:
I've been patching using Magisk Manager canary version on the phone. What version of Magisk Manager did you use It's really strange
Click to expand...
Click to collapse
I use this version of magisk manager and it always work
Shas45558 said:
I use this version of magisk manager and it always work
Click to expand...
Click to collapse
Thanks. I've been using Magisk Manager beta/canary and it seems it does not patch the boot image properly. You are the best.
Thanks for the post. It helped me to root my redmi note 9.
nielsync said:
Thanks. I've been using Magisk Manager beta/canary and it seems it does not patch the boot image properly. You are the best.
Click to expand...
Click to collapse
Welcome. Redmi 9 and redmi note 9 are are based on same chipset mt6768....
And so the process help you. I think it is the same to root any device running on Android 10.
And vbmeta.img which I provide upper post, is a universal vbmeta.img. you can use it to flash any Android device which has vbmeta partition because this vbmeta.img is a dummy file or you can call it as a blank file...
Shas45558 said:
Welcome. Redmi 9 and redmi note 9 are are based on same chipset mt6768....
And so the process help you. I think it is the same to root any device running on Android 10.
And vbmeta.img which I provide upper post, is a universal vbmeta.img. you can use it to flash any Android device which has vbmeta partition because this vbmeta.img is a dummy file or you can call it as a blank file...
Click to expand...
Click to collapse
My issues was patching using the canary version of Magisk Manager which isn't stable enough and was probably not patching the boot image properly as opposed to Magisk Manager 7.5.1 which is the stable version. Nice explanation on the vbmeta.img file.
VERY IMPORTANT:
Please make sure your ROM version matches the ROM version of those patched boot image and files. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
For the post author:
Thanks for your effort
I understand you are trying to help and that you put a note at the end of your post. But please make it clear at the BEGINING, that this method is valid for this specific ROM Version "xx.x.xx.x.x"
I guess this still doesn't unlock the bootloader, and what about system updates?
Kiwironic said:
VERY IMPORTANT:
Please make sure your ROM version matches the ROM version of those patched boot image and files. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
For the post author:
Thanks for your effort
I understand you are trying to help and that you put a note at the end of your post. But please make it clear at the BEGINING, that this method is valid for this specific ROM Version "xx.x.xx.x.x"
Click to expand...
Click to collapse
Ok i do ir on top and bottom of the post and thanks for your advice:good::good:
I have an issue. I cannot install any custom recovery on Redmi 9, no matter how much I try (Twrp or PBRP). Every time the phone reboots directly. There is anyone that can help me?
rizelgeorgel said:
I have an issue. I cannot install any custom recovery on Redmi 9, no matter how much I try (Twrp or PBRP). Every time the phone reboots directly. There is anyone that can help me?
Click to expand...
Click to collapse
Download pbrp from official website.then extract it and you will get a .img file.flash it via fastboot mood and the cmd is
fastboot flash recovery pbrp.img
*Change pbrb.img according to your file name.
One big question..did you unlock your bootloader and root your device?
Thank you very much! I succeeded according to your advice!
shas hows pbrp?
regarding flashing?
mhark.moby said:
shas hows pbrp?
regarding flashing?
Click to expand...
Click to collapse
Pbrp is in beta testing....so it has some bug and there's no use to install..
Buenas tardes tengo problemas al cargar el parche de magisk en redmi 9. Cuando cargo el boot.img parchado de magisk el tlfn queda en bootloop estoy en la version 11.0.8 global.
Hi guys so Many users are facing issue while they are rooted and twrp installed on there phone.
They can't able to Flash update through stock settings OR via twrp if they tries to flash it via twrp manually facing no wifi and Bluetooth.
So here is the process to flash any incremental update via twrp just we need update zip, vbmeta image and boot image of old oos version respective to your new update means if. We are upgrading to V11 we need V10 boot img
U can use following commands to extract your current stock boot img after connecting to PC
adb shell
dd if=/dev/block/sdc49 of=/sdcard/boot.img
exit
Note: Remember this process will replace your twrp and removes root to gain root access. We need to repeat twrp installation shown in the following tutorial
TUTORIAL TWRP AND ROOT NORD 2 OXYGEN OS 11 ( Links updated!)
SO finally I successfully rooted with TWRP and root access.thanks to all developers @Eastw1ng @TheMalachite Following are all download links combined in one post Also there are two threads like unlocking boot loader and twrp but there are some...
forum.xda-developers.com
You can gain root acess only by flashing magisk.zip file after step no 7 given under instructions but I didn't tested it yet.
DOWNLOADS:
1)Download update v11 from Telegram :
®D$ in OnePlus Nord 2 Community
t.me
2) DOWNLOAD V13:
®D$ in OnePlus Nord 2 Community
t.me
3) Download V14 update zip:
️ in OnePlus Nord 2 Community
t.me
4) Download A15 update zip:
e9708c8610bae8fa64d76e0f9a55dda444ce981a.zip
drive.google.com
We can also download update in system update process. Just download OTA update and when we boot in twrp just click install and then go to following folder there you will find update.zip
/data/OTA-package/update.zip
5)A17 update zip:
https://t.me/OnePlusNord2GlobalOfficial/81364
Download vbmeta:
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download boot.img:
1) upgrade from v10 to v11(indian)
boot.img
drive.google.com
2) upgrade from v11 to v13(indian)
bootnew.img
drive.google.com
3)Upgrade from v13 to v14:
Rose in OnePlus Nord 2 Community
t.me
4)Upgrade from A14 to A15:
Rose in OnePlus Nord 2 Community
t.me
5)15 Boot img india (update from A15 to AA16)
https://t.me/OnePlusNord2GlobalOfficial/57795
5)A16 boot.img to upgrade to A17:
Rose in OnePlus Nord 2 Community
A16 stock boot image
t.me
6)17 BOOT IMG Upgrade to A18 (boot.img vbmeta zip extract file)
Rose in OnePlus Nord 2 Community
t.me
Boot img for nord 2 EU REGION :
File folder on MEGA
mega.nz
This another thread for all boot img of EU region
Stock Boot & Patched images Oneplus Nord 2 Oxygen 11.3 DN2103_11_A.07/09/10 EEA
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! https://mega.nz/folder/fZx2nBaR#Q33lJstFRMQg6_0j7Z0TJw Special Thanks: @HofaTheRipper @phhusson
forum.xda-developers.com
Instructions :
1) Download all file from the link given under this thread place them at one place on your phone so it can be easily accessible when we boot in TWRP.
2)Now to boot in TWRP use following root acess app called as advance reboot. Open it and click reboot to recovery
Advanced Reboot Tools [ROOT] - Apps on Google Play
Provides lots of options for restarting your device; excellent for tweakers.
play.google.com
Or you can use adb command after connecting phone to pc in USB debugging mode.
adb reboot recovery
3) when phone boot in TWRP click install tab now go to folder where we placed All files.
4) click install image tab at bottom now you we see image files boot. img and vbmeta.img that we downloaded
5)now select boot.img and then select boot partation and slide bottom bar after successful installation
6)click reboot and select recovery phone will boots back to twrp( This step is optional)
7)Now again click Install and find our old folder now select update.zip file and slide bottom bar it will take 2min for complete falshing of zip.
8)now agian click install now click install image and select vbmeta.img
9)Now click reboot system phone will reboots and take 10min.
Now you are successfully updated and have new OOS 11.3 A11 version on your phone without any issues.
Follow the video:
New update v13 update process :
New update A14 update process:
New update A15:
New update A16:
New A18 update:
pankspoo said:
Hi guys so Many users are facing issue while they are rooted and twrp installed on there phone.
They can't able to Flash update via twrp if they tries to flash it via twrp manually facing no wifi and Bluetooth.
So here is the process to flash any incremental update via twrp just we need update zip, vbmeta image and boot image of old oos version respective to your new update means if. We are upgrading to V11 we need V10 boot img.
Follow the video:
Click to expand...
Click to collapse
good Instructions! Reboot after flashing boot.img isnt necessary. OTA Update zip can be downloaded within OTA App in Settings (do not press reboot). After downloading you can reboot to TWRP and the file location is: /data/OTA-package/update.zip.
HofaTheRipper said:
good Instructions! Reboot after flashing boot.img isnt necessary. OTA Update zip can be downloaded within OTA App in Settings (do not press reboot). After downloading you can reboot to TWRP and the file location is: /data/OTA-package/update.zip.
Click to expand...
Click to collapse
Yes but I don't want to go to automatic reboot and flashing process of OTA Update installation after download which may cause some issues for new users.
The old boot.img I image is the stock one not rooted right? How can you extract it from your firmware if you're not rooted? From the Nandroid backup maybe?
Edit, found out: https://forum.xda-developers.com/t/how-to-extract-your-boot-img-from-any-rom-adb.3760210/ Just had to google it
Don't wo
Raygen said:
The old boot.img I image is the stock one not rooted right? How can you extract it from your firmware if you're not rooted? From the Nandroid backup maybe?
Click to expand...
Click to collapse
Donts worry from here every new updates we will provide all stock boot. img
Thread updated for latest update v13 for India region
HI. This is my 1st OnePlus and OxygenOS. I am now on DN2103_11_A.11 and OTA is available. It is DN2103_11_A.12
Basically I can flash it from TWRP and I do not need to save and flash boot.img afterwards bec OS will be the same version. Is that so? Or am I wrong? And I have to follow threads instructions ?
Thank you
jis251 said:
HI. This is my 1st OnePlus and OxygenOS. I am now on DN2103_11_A.11 and OTA is available. It is DN2103_11_A.12
Basically I can flash it from TWRP and I do not need to save and flash boot.img afterwards bec OS will be the same version. Is that so? Or am I wrong? And I have to follow threads instructions ?
Thank you
Click to expand...
Click to collapse
NO u need A11 boot img of only DN 2103 firmware not indian I don't have that now first flash that then flash update zip of v12 then flash Vbmeta now that's done
pankspoo said:
NO u need A11 boot img of only DN 2103 firmware not indian I don't have that now first flash that then flash update zip of v12 then flash Vbmeta now that's done
Click to expand...
Click to collapse
HI. And thx for quick reply. I mange now, thank you.
DN2103 A.11 stock boot img :
HofaTheRipper said:
DN2103 A.11 stock boot img :
Click to expand...
Click to collapse
You got it do it now
HofaTheRipper said:
DN2103 A.11 stock boot img :
Click to expand...
Click to collapse
HI and thx. I have made TWRP backup, boot and vbmeta
So I can first restore boot then flash OTA and then restore vbmeta, yes? (Version 11)
I do not have to flash boot and vbmeta, restore does the same??
jis251 said:
HI and thx. I have made TWRP backup, boot and vbmeta
So I can first restore boot then flash OTA and then restore vbmeta, yes? (Version 11)
I do not have to flash boot and vbmeta, restore does the same??
Click to expand...
Click to collapse
Don't use backup boot image restore process.
Just download above boot image given
https://forum.xda-developers.com/attachments/boot_stock_a11-img.5461307/
and vbmeta image given in. My thread
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
And u r update zip of device of your region not mine
First flash boot img then. Install update zip then. Flash Vbmeta done
pankspoo said:
Don't use backup boot image restore process.
Just download above boot image given
https://forum.xda-developers.com/attachments/boot_stock_a11-img.5461307/
and vbmeta image given in. My thread
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
And u r update zip of device of your region not mine
First flash boot img then. Install update zip then. Flash Vbmeta done
Click to expand...
Click to collapse
Thx. OK I do that.
Magisk is installed (patched) to boot image so after OTA and Vbmeta I flash Magisk to keep root.
jis251 said:
Thx. OK I do that.
Magisk is installed (patched) to boot image so after OTA and Vbmeta I flash Magisk to keep root.
Click to expand...
Click to collapse
Yes
pankspoo said:
Download boot.img:
1) upgrade from v10 to v11(indian)
boot.img
drive.google.com
2) upgrade from v11 to v13(indian)
bootnew.img
drive.google.com
Click to expand...
Click to collapse
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
NetSoerfer said:
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
Click to expand...
Click to collapse
Ok I will upload in thread
NetSoerfer said:
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
Use boot images from stock folder
pankspoo said:
U can use following commands to extract your current stock boot img after connecting to PC
adb shell
dd if=/dev/block/sdc49 of=/sdcard/boot.img
exit
Click to expand...
Click to collapse
Still trying to wrap my head around this (although updating worked fine from A11 to A12 on my EEA variant, thanks @pankspoo!).
Can I actually extract a stock boot.img from a Magisk-rooted phone? Is it stock (in which case why is root removed by the update.zip) or is it modified (in which case, why can I extract it as stock)?
NetSoerfer said:
Still trying to wrap my head around this (although updating worked fine from A11 to A12 on my EEA variant, thanks @pankspoo!).
Can I actually extract a stock boot.img from a Magisk-rooted phone? Is it stock (in which case why is root removed by the update.zip) or is it modified (in which case, why can I extract it as stock)?
Click to expand...
Click to collapse
You can use those adb commands while booted in TWRP, without being rooted. So you'll extract the stock boot image
is it possible to install a GSI rom without TWRP?
It is possible but involves a heck ton of work you basically need to extract an entire GSI and compress each file using lz4 then repack them the way Samsung does and flash using Odin
The work involved in repacking the GSI in Samsung's format when there is no guarantee what issues the GSi will coz with the device makes it not a very suitable option
But yeah you can try for the heck of it, here's a thread that might help you
[GUIDE] [CUSTOM] How to Install Custom ROM using ODIN without TWRP [PHH] [LineageOS]
Hello, This would be a short & sweet guide on how to install a custom ROM on your Samsung using ODIN. I'm going to tailored this guide for the S10e G9700 HK version (is the phone I own) I'm a linux user but Odin only runs on Windows so this...
forum.xda-developers.com
Insomniac05 said:
It is possible but involves a heck ton of work you basically need to extract an entire GSI and compress each file using lz4 then repack them the way Samsung does and flash using Odin
The work involved in repacking the GSI in Samsung's format when there is no guarantee what issues the GSi will coz with the device makes it not a very suitable option
But yeah you can try for the heck of it, here's a thread that might help you
[GUIDE] [CUSTOM] How to Install Custom ROM using ODIN without TWRP [PHH] [LineageOS]
Hello, This would be a short & sweet guide on how to install a custom ROM on your Samsung using ODIN. I'm going to tailored this guide for the S10e G9700 HK version (is the phone I own) I'm a linux user but Odin only runs on Windows so this...
forum.xda-developers.com
Click to expand...
Click to collapse
ok i'll try it thank you!
Insomniac05 said:
It is possible but involves a heck ton of work you basically need to extract an entire GSI and compress each file using lz4 then repack them the way Samsung does and flash using Odin
The work involved in repacking the GSI in Samsung's format when there is no guarantee what issues the GSi will coz with the device makes it not a very suitable option
But yeah you can try for the heck of it, here's a thread that might help you
[GUIDE] [CUSTOM] How to Install Custom ROM using ODIN without TWRP [PHH] [LineageOS]
Hello, This would be a short & sweet guide on how to install a custom ROM on your Samsung using ODIN. I'm going to tailored this guide for the S10e G9700 HK version (is the phone I own) I'm a linux user but Odin only runs on Windows so this...
forum.xda-developers.com
Click to expand...
Click to collapse
I have tried the tutorial but in the tutorial it says I need
boot.img.lz4
dqmdbg.img.ext4.lz4
dtbo.img.lz4
persist.img.ext4.lz4
recovery.img.lz4
system.img.ext4.lz4
userdata.img.ext4.lz4
vbmeta.img.lz4
vendor.img.ext4.lz4
these files but I only have
boot.img.lz4
dtbo.img.lz4
recovery.img.lz4
system.img.ext4.lz4
userdata.img.ext4.lz4
vbmeta.img.lz4
And when I flash it like it says in the tutorial I cannot flash system.img.ext4 and fails
Is there anymore ways to do this? tried it with Lineage OS 19.0
GyuminLeo said:
I have tried the tutorial but in the tutorial it says I need
boot.img.lz4
dqmdbg.img.ext4.lz4
dtbo.img.lz4
persist.img.ext4.lz4
recovery.img.lz4
system.img.ext4.lz4
userdata.img.ext4.lz4
vbmeta.img.lz4
vendor.img.ext4.lz4
these files but I only have
boot.img.lz4
dtbo.img.lz4
recovery.img.lz4
system.img.ext4.lz4
userdata.img.ext4.lz4
vbmeta.img.lz4
And when I flash it like it says in the tutorial I cannot flash system.img.ext4 and fails
Is there anymore ways to do this? tried it with Lineage OS 19.0
Click to expand...
Click to collapse
not really since samsung has no fastboot mode
try renaming system.img.ext4.lz4 as super.img.lz4 as that's the name of the file in stock
Insomniac05 said:
not really since samsung has no fastboot mode
try renaming system.img.ext4.lz4 as super.img.lz4 as that's the name of the file in stock
Click to expand...
Click to collapse
will try it now
Insomniac05 said:
not really since samsung has no fastboot mode
try renaming system.img.ext4.lz4 as super.img.lz4 as that's the name of the file in stock
Click to expand...
Click to collapse
So the flash itself went well without any errors. But the tablet is in a boot loop. When it boots Samsung Galaxy logo appears and reboots. This tablet is running Android 11 so do I need to install Android 11 Lineage OS?
GyuminLeo said:
So the flash itself went well without any errors. But the tablet is in a boot loop. When it boots Samsung Galaxy logo appears and reboots. This tablet is running Android 11 so do I need to install Android 11 Lineage OS?
Click to expand...
Click to collapse
Nope don't think the android version would have anything to do with it is probably the os not working properly
Maybe try some other GSI like pixel experience to see if they work
GyuminLeo said:
So the flash itself went well without any errors. But the tablet is in a boot loop. When it boots Samsung Galaxy logo appears and reboots. This tablet is running Android 11 so do I need to install Android 11 Lineage OS?
Click to expand...
Click to collapse
I think you should try Android 11 Lineage OS
Insomniac05 said:
Nope don't think the android version would have anything to do with it is probably the os not working properly
Maybe try some other GSI like pixel experience to see if they work
Click to expand...
Click to collapse
Same thing happens with AOSP GSI image
thatha said:
I think you should try Android 11 Lineage OS
Click to expand...
Click to collapse
I downloaded the zip file but there is no system.img file. Is there a way to extract the img file?
If I have twrp or any custom recovery can I just install it with the zip file?
GyuminLeo said:
I downloaded the zip file but there is no system.img file. Is there a way to extract the img file?
If I have twrp or any custom recovery can I just install it with the zip file?
Click to expand...
Click to collapse
Yes with a recovery u can straight up flash the zip file
Insomniac05 said:
Yes with a recovery u can straight up flash the zip file
Click to expand...
Click to collapse
But does the A7 Lite have a custom recovery? I have searched alot but no juice
GyuminLeo said:
But does the A7 Lite have a custom recovery? I have searched alot but no juice
Click to expand...
Click to collapse
Nope it does not
Insomniac05 said:
Nope it does not
Click to expand...
Click to collapse
Is there a way to flash this zip file?
GyuminLeo said:
Is there a way to flash this zip file?
Click to expand...
Click to collapse
Well you can extract the contents using something like winrar or 7zip and then try building an Odin flashable md5 like you did for the last one
Insomniac05 said:
Nope it does not
Click to expand...
Click to collapse
Is there a way to port a twrp image for the A7 Lite?
GyuminLeo said:
Is there a way to port a twrp image for the A7 Lite?
Click to expand...
Click to collapse
Samsung's stock recovery is kinda strange so not sure if it could be used with some other device' twrp then mixed and mashed together to port the twrp
Probably needs to be built from the ground up
Insomniac05 said:
Samsung's stock recovery is kinda strange so not sure if it could be used with some other device' twrp then mixed and mashed together to port the twrp
Probably needs to be built from the ground up
Click to expand...
Click to collapse
Oh ok thanks. And I was able to root this device but can I install a custom rom from that state? Tab was rooted with Samsung's default firmware with magisk installed
GyuminLeo said:
Oh ok thanks. And I was able to root this device but can I install a custom rom from that state? Tab was rooted with Samsung's default firmware with magisk installed
Click to expand...
Click to collapse
Nope rooting has no role in flashing custom roms that all is recovery dependent