Related
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
cubano2031 said:
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
Click to expand...
Click to collapse
Sent from my LGE LM-X410.FGN using XDA Labs
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Rebel_X said:
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Click to expand...
Click to collapse
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
Thanks a lot!! And it was as simple as that. It works fine. :good:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
MAREK10747 said:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
Click to expand...
Click to collapse
Hi,me devie is I4293
I have unrar the rom , so i get the boot_X-FLASH-ALL-8F02.sin
would you mind to make the kernel for me?
the file is here :
https://drive.google.com/file/d/1sywqfBtELSTgRXtTBEvlI454K_1ul-1h/view?usp=sharing
my gmail is [email protected]
you can send it to me.
thank you.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
yishisanren said:
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
Click to expand...
Click to collapse
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Zaben said:
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Click to expand...
Click to collapse
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
yishisanren said:
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
Click to expand...
Click to collapse
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
wang4632 said:
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
Click to expand...
Click to collapse
older version can not patch boot.img, because when you click "install the zip",it will let you update the new verison.
Any news on the boot loop situation? I also encounterd this problem and back to running original boot.img. having an unlocked bootloader is useless without root ?
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Did you lose any feature like super vivid mode and camera focusing after unlocking the bootloader?
can't find the driver, the model is l421dual sim, can't rooting, have i already patched the boot img?
My I4293 stuck in bootloop~~help ~!
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
This phone cannot be rooted at this time due to the lack of the img.patch and no driever.
Zack_U said:
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
Click to expand...
Click to collapse
Are you still stuck? For all of the latest Sony phones try NewFlasher instead.
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
Flashtool doesn't support our phones. Magisk 19.1+ currently doesn't work with our phones. Hopefully 19.4 will fix that.
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 everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
T4gB0t said:
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
Click to expand...
Click to collapse
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Hw4ng3r said:
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Click to expand...
Click to collapse
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
T4gB0t said:
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
Click to expand...
Click to collapse
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Hw4ng3r said:
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Click to expand...
Click to collapse
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
T4gB0t said:
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
Click to expand...
Click to collapse
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Hw4ng3r said:
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Click to expand...
Click to collapse
I downloaded the software from the official website and used payload dumper to extract the boot image. To be sure that I understood everything... you suggested to use "fastboot boot patched.img" instead of "fastboot flash boot patched.img", and once the phone restarted to go to magisk manager and click direct install.
Do I need Magisk Manager canary or the normal version for this to work and do I have to mantain the canary version or can I install the normal version once it is rooted?
Either 22.1 or Canary works for A11
Hw4ng3r said:
Either 22.1 or Canary works for A11
Click to expand...
Click to collapse
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
T4gB0t said:
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
Click to expand...
Click to collapse
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
T4gB0t said:
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
Click to expand...
Click to collapse
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Hw4ng3r said:
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Click to expand...
Click to collapse
So not Magisk v.23 but Magisk canary?
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Hw4ng3r said:
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Click to expand...
Click to collapse
Okay thanks, I'll try with v.23 first and If that does not work than I'll try with the canary one. Thank you very much!!!
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Wacko1805 said:
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay thank you, I'll try if the other method does not work
T4gB0t said:
Okay thank you, I'll try if the other method does not work
Click to expand...
Click to collapse
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Hw4ng3r said:
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Click to expand...
Click to collapse
I'm sorry to bother you again, but I tried with "fastboot boot patched.img" and it still did not work. It got stuck while booting again with "unable to parse kernel log" as error message. Do you have any other suggestions?
P.S. I got a full backup with "adb backup -apk -all -shared -f /path/to/location" today and thought about just doing a factory reset, trying to root the phone, restore the backup. Do you think that might actually work? Thank you for your help!
How exactly did you patched your boot.img?
FSadino said:
How exactly did you patched your boot.img?
Click to expand...
Click to collapse
I tried doing it with magisk (both v.23 and canary)
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process!
Downloads:
The Fastboot restoration file can be downloaded in here:
DN2103_11_A.07
DN2103_11_A.10 *deleted
DN2103_11_A.11 *deleted
please use ota files to upgrade
File folder on MEGA
mega.nz
include Flash Root & TWRPinstaller
tool for Windows (.bat)
Special Thanks: @HofaTheRipper @phhusson
Caution! Please check your version on your mobile phone before flashing. these files may only be used for V07!If you want to upgrade, use the ota files here.
Oneplus Nord 2 Oxygen 11.3 DN2103_11_A.10 EEA ROM
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! Downloads: The Fastboot restoration file can be downloaded in here: https://mega.nz/folder/bMwxRCKb#E_ZX3TfA9hhbuODHMquxDA include...
forum.xda-developers.com
before flashing
Backup your nvcfg.img, nvdata.img, nvram.img, persist.img, proinfo.img, protect1.img and protect2.img with Partition Backup from Playstore
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
Interesting! Could I ask what ROM this is?
Eastw1ng said:
Interesting! Could I ask what ROM this is?
Click to expand...
Click to collapse
Hi, this is Oxygen OS .. I forget it in the Title Thanks
11.3.A07 EEA and11.3.A10 EEA
After doing this, will the updates come from oneplus as usual?
xirosiman said:
After doing this, will the updates come from oneplus as usual?
Click to expand...
Click to collapse
Yes, but i not test to Upgrade
sakarya1980 said:
Hi, this is Oxygen OS .. I forget it in the Title Thanks
11.0.3.A07 EEA
Click to expand...
Click to collapse
Hey thanks for the reply, my question was mostly if this is the stock rom for the oneplus nord 2, or is this a different rom made compatible?
Eastw1ng said:
Hey thanks for the reply, my question was mostly if this is the stock rom for the oneplus nord 2, or is this a different rom made compatible?
Click to expand...
Click to collapse
Stock, not custom
sakarya1980 said:
Yes, but i not test to Upgrade
Click to expand...
Click to collapse
I tested. You must flash without root, then can you upgrade @xirosiman
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process!
OTA files here (put this files to your OTG)
File folder on MEGA
mega.nz
Click to expand...
Click to collapse
Stock boot.img https://mega.nz/folder/fZx2nBaR#Q33lJstFRMQg6_0j7Z0TJw
Click to expand...
Click to collapse
Please use this commands
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta2.img
Fastboot flash boot nord2_stock_boot_A07.img
ok i managed to make it run.
when all is done, it can not boot.
i managed to flash the boot.img from the other thread in order to make it run.
xirosiman said:
ok i managed to make it run.
when all is done, it can not boot.
i managed to flash the boot.img from the other thread in order to make it run.
Click to expand...
Click to collapse
You must flash vbmeta2 then boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta2.img
Do you try v10? You can not flash from v7 to v10 and please check your driver
ok i have done it. Somehow the wifi toggle wasnt working but after flashing vbmeta and boot its ok.
i managed to go to A7 stock and now is updating to A10.
One thing i noticed, the combination of volume down and start button has changed only to fastboot.
And the only way to go to recovery is from command
also it can not recognise the sim cards
and the updade through ota is failed. it can not verify says
xirosiman said:
ok i have done it. Somehow the wifi toggle wasnt working but after flashing vbmeta and boot its ok.
i managed to go to A7 stock and now is updating to A10.
One thing i noticed, the combination of volume down and start button has changed only to fastboot.
And the only way to go to recovery is from command
also it can not recognise the sim cards
and the updade through ota is failed. it can not verify says
Click to expand...
Click to collapse
You can't update from 7 to 10. You must flash ota file with v9, then Upgrade to 10.
Wlan and Bluetooth works, after flash v7 again
Here ota files
https://mega.nz/folder/rQhhHQpA#nNHvPlmzBXwPjmaFpuDa2Q
Please put both file to your otg storage and flash it, with stock recovery. Every time after flash vbmeta2
You can start recovery with fastboot reboot recovery
Downgrading from 10 to 7 was not successful. Even if the rom works it can not recognise the sim cards.
Now i am flasing 10 to see if it works
during flashing its says "Invalid sparse file format at header magic" do this has something to do with drivers?
xirosiman said:
Downgrading from 10 to 7 was not successful. Even if the rom works it can not recognise the sim cards.
Now i am flasing 10 to see if it works
during flashing its says "Invalid sparse file format at header magic" do this has something to do with drivers?
Click to expand...
Click to collapse
dont abort this. Invalid sparse file format at header magic" is normal, but you must wait ...
sakarya1980 said:
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process!
Please use this commands
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta2.img
Fastboot flash boot nord2_stock_boot_A07.img
Click to expand...
Click to collapse
Did a full upgrade from stock 07 to 09 then 10, went perfectly.
Thanks Sakarya!
Eastw1ng said:
Did a full upgrade from stock 07 to 09 then 10, went perfectly.
Thanks Sakarya!
Click to expand...
Click to collapse
Hi, good ota flash 07 to 09?
Yeah OTA flash from 07 to 09, then a flash from 09 to 10 and followed up with the rooted boot image to make sure everything was as you described. Works flawlessly!
Is there any way to flash the ROM without fastboot? I bricked the phone and I'm unable to get to fastboot.
Update tonOxygen 11.3 DN2103_11_A.10 EEAinclude Flash Root & TWRPinstaller
tool for Windows (.bat)
[RECOVERY][UNOFFICIAL] TWRP 3.5.2_11-0 for OnePlus Nord 2 5G [denniz]
https://forum.xda-developers.com/t/...-2_11-0-for-oneplus-nord-2-5g-denniz.4335021/
I have a Samsung A52 5g and there is a new software update from android 11 to 12. Do I have to go through the first time setup for magisk or can i just patch it as an update like normal?
sygmstr said:
I have a Samsung A52 5g and there is a new software update from android 11 to 12. Do I have to go through the first time setup for magisk or can i just patch it as an update like normal?
Click to expand...
Click to collapse
If the previous method was patching the boot image, you can repeat the process with the new one that comes with the update.
SubwayChamp said:
If the previous method was patching the boot image, you can repeat the process with the new one that comes with the update.
Click to expand...
Click to collapse
well I just tried updating and I lost root so if you update to a newer version of android you have to do a clean install of magisk
sygmstr said:
well I just tried updating and I lost root so if you update to a newer version of android you have to do a clean install of magisk
Click to expand...
Click to collapse
Sure, you lost root as an update includes most likely a newer boot image that will replace the magisk-patched boot image, as I said you, you should patch the new boot image included in the update and install it normally, not a clean update, so you wouldn't need to uninstall it previously.
SubwayChamp said:
Sure, you lost root as an update includes most likely a newer boot image that will replace the magisk-patched boot image, as I said you, you should patch the new boot image included in the update and install it normally, not a clean update, so you wouldn't need to uninstall it previously.
Click to expand...
Click to collapse
I tried patching magisk to my samsung using the method in their instructions twice now and I havent been able to get it to work. Can you help me?
sygmstr said:
I tried patching magisk to my samsung using the method in their instructions twice now and I havent been able to get it to work. Can you help me?
Click to expand...
Click to collapse
And what was the method you used the first time? In some devices you need to patch the boot image, if this is the case you have to extract the boot image from the stock ROM (the same you're currently on), unpack it from the lz4 format, also depends on if your device has ramdisk, and most of them support patching the whole AP file and then converting it in tar format to flash it through Odin. You should follow this https://topjohnwu.github.io/Magisk/install.html
I just did this upgrade and successfully kept magisk, did you get this working?