I have camera issues. After ubl unlocked and rooted. When i record in my camera, my phone reboot on itself. So i think the problem is my patched boot.img and vbmeta.img Please reply me asap
inigueal said:
I have camera issues. After ubl unlocked and rooted. When i record in my camera, my phone reboot on itself. So i think the problem is my patched boot.img and vbmeta.img Please reply me asap
Click to expand...
Click to collapse
Same with me after UBL from B.53. Record camera doesn't work. Rebooting....
Doddy_Doda said:
Same with me after UBL from B.53. Record camera doesn't work. Rebooting....
Click to expand...
Click to collapse
do you fixed the problem or still fixing?
Still fixing on custom rom PE11. I have tried various cameras but they still can't record video. Always freezes while recording, and the result is an error.
The previous thing I did UBL during the B.53 stockrom. I disable verification flash vbmeta according to the instructions and flash PBRP then flash this rom. Then I returned it to B.53 stock rom when recording video is normally only stock rom B.53 can do it.
Doddy_Doda said:
Still fixing on custom rom PE11. I have tried various cameras but they still can't record video. Always freezes while recording, and the result is an error.
The previous thing I did UBL during the B.53 stockrom. I disable verification flash vbmeta according to the instructions and flash PBRP then flash this rom. Then I returned it to B.53 stock rom when recording video is normally only stock rom B.53 can do it.
Click to expand...
Click to collapse
oh i just realized that my magisk patched boot.img was b.49 but my rmx2001 is in b.53. so just need to reflash stock/original b.53 boot.img and vbmeta.img
inigueal said:
oh i just realized that my magisk patched boot.img was b.49 but my rmx2001 is in b.53. so just need to reflash stock/original b.53 boot.img and vbmeta.img
Click to expand...
Click to collapse
i got that magisk patched boot.img from another post, from someone with username veez or idk
inigueal said:
oh i just realized that my magisk patched boot.img was b.49 but my rmx2001 is in b.53. so just need to reflash stock/original b.53 boot.img and vbmeta.img
Click to expand...
Click to collapse
Heya, i don't had this sort of problems
Can you give me patched vbmeta + boot for B53?
(also, tried to update my phone from b49 to b53 but got recovery loop, and i must go to authorized service center to fix my phone cuz i can't install custom recover, some sort of fixes for this?)
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.
I have just bought oneplus 7 t pro and want to root it. How do I extract boot.img from the firmware so I can patch it using magisk ? Any help in rooting this device would be greatly appreciated. Thanks
you should wait the stock rom or you can try to boot the oneplus 7t twrp and backup the boot.img
Thanks
Will try and report back
boots into the twrp 7t recovery but boot.img is not being backed up . It fails to mount any partition . adb pull command not working .
I have boot image
are you able to patch it with magisk ?
ask77 said:
are you able to patch it with magisk ?
Click to expand...
Click to collapse
unfortunately not
I have now extracted boot.img and patched it with magisk but the output image is of 36.44 MB while the original image is of 96 MB so I am a bit wary in flashing this image as I do not want to go into a boot loop also I have a boot.img and a recovery.img both are identical in size and are identified by magisk as stock boot.img . i am uploading the install log . I will research a bit more before flashing the patched boot img to achieve root
ask77 said:
I have now extracted boot.img and patched it with magisk but the output image is of 36.44 MB while the original image is of 96 MB so I am a bit wary in flashing this image as I do not want to go into a boot loop also I have a boot.img and a recovery.img both are identical in size and are identified by magisk as stock boot.img . i am uploading the install log . I will research a bit more before flashing the patched boot img to achieve root
Click to expand...
Click to collapse
try just doing fastboot boot patchedbootimghere.img
if it bootloops you can just restart the phone and it will be back to normal since its not flashed
HolyChickenGuy said:
try just doing fastboot boot patchedbootimghere.img
if it bootloops you can just restart the phone and it will be back to normal since its not flashed
Click to expand...
Click to collapse
Thanks will do that.
sorry no go . It either goes to crashdump or is stuck with the fastboot screen
ask77 said:
sorry no go . It either goes to crashdump or is stuck with the fastboot screen
Click to expand...
Click to collapse
I'm having the same results
Sent from my OnePlus 7T Pro
same there no luck. just the crash dump screen
digitalashley said:
same there no luck. just the crash dump screen
Click to expand...
Click to collapse
Make sure to check Preserve AVB 2.0/dm-verify in advance settings before patching boot.img, then use command
fastboot boot imagenamehere.img, after boot, perform direct install to preserve root.
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.
Hey,
Has someone figured out how to root the phone after bootloader unlock? I saw some attempts in the GSI thread but it wolud be nice if somebody who done it publish a guide. [here or in the new thread]
This way it will be easier to find for future people to follow.
hi, i couldn't find a stock boot.img so far. seems we will have to wait some more time to be able to download latest firmware as full rom to get the boot.img, which we can then patch with magisk.
eagerly waiting for it, as i cannot hide my unlocked bootloader so far and some apps refuse to work now (also safetynet check fails)
juergenh99 said:
hi, i couldn't find a stock boot.img so far. seems we will have to wait some more time to be able to download latest firmware as full rom to get the boot.img, which we can then patch with magisk.
eagerly waiting for it, as i cannot hide my unlocked bootloader so far and some apps refuse to work now (also safetynet check fails)
Click to expand...
Click to collapse
You can use the Oxygen Updater app on google play to download the latest full rom. then use https://github.com/vm03/payload_dumper
to get the boot.img.
Manugamé said:
You can use the Oxygen Updater app on google play to download the latest full rom. then use https://github.com/vm03/payload_dumper
to get the boot.img.
Click to expand...
Click to collapse
Oxygen Updater says the Oneplus Nord 2 is not supported, and i couldn't find a Download of latest FullRom.
If you are already unlocked, download the boot image, patch with magisk etc Do you have to factory reset again?
moisthat said:
If you are already unlocked, download the boot image, patch with magisk etc Do you have to factory reset again?
Click to expand...
Click to collapse
That's the point....where and how to download the latest boot.img??
Bootloader is unlocked already.
That's why I want the latest full rom to extract it from that.
juergenh99 said:
That's the point....where and how to download the latest boot.img??
Bootloader is unlocked already.
That's why I want the latest full rom to extract it from that.
Click to expand...
Click to collapse
My reply was confusing, and I wasn't actually replying to you. Sorry about that. I don't know how or where to download the boot.img.
I am trying to ask the community if we need to factory reset again when we flash the patched boot.img. Or if the reset we did during unlock is the only reset needed.
moisthat said:
My reply was confusing, and I wasn't actually replying to you. Sorry about that. I don't know how or where to download the boot.img.
I am trying to ask the community if we need to factory reset again when we flash the patched boot.img. Or if the reset we did during unlock is the only reset needed.
Click to expand...
Click to collapse
unlocking the bootloader means to do a reset. flashing the boot.img does not cause a reset.
you just have root and working magisk after flashing and reboot
juergenh99 said:
unlocking the bootloader means to do a reset. flashing the boot.img does not cause a reset.
you just have root and working magisk after flashing and reboot
Click to expand...
Click to collapse
Well then, now I have joined you in the hunt for this bloody boot.img
HofaTheRipper said:
I am not respondible if you brick your device as there is no full rom download to revert all this.
i have done this:
- installed magisk on the phone and transfered the attached boot.img to the phone.
- patched it with magisk and transfered it to pc
Flashing:
- Unlock bootloader
- Reboot into bootloader
- Download https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
- `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img`
- `fastboot flash boot magisk_patched_boot.img`
rebootet and root worked but wifi/bt was broken due some version conflict
Fix for wifi/bt for me was:
- unpack vendor.xz
- reboot to bootloader
- `fastboot reboot fastboot`
- `fastboot flash vendor vendor`
- reboot
My Build Version is DN2103_11_A.08.
Thanks to @phhusson for his help and for his files!
Click to expand...
Click to collapse
Found in this thread. Hope it will work for further updates.
I flashed Hongkong firmware which is Android 13 just now and I patched boot.img with magisk and I flashed it, boot to system successfully, but after a while it turned off and rebooted to recovery, said that system may not in stock and may need to erase user data. I reboot it but same. So how to root in Android 13?
I patched my boot.img and after reboot to fastboot flashed patched img and reboot
raven213 said:
I patched my boot.img and after reboot to fastboot flashed patched img and reboot
Click to expand...
Click to collapse
This is what I've done however there is another thread which states to flash vbmeta also, is this required?
Also if possible could you give me information about how to setup newsflasher? As last I've used this it was on an Xperia x10i lmao now I see there's no .exe to it
Mijan94 said:
This is what I've done however there is another thread which states to flash vbmeta also, is this required?
Also if possible could you give me information about how to setup newsflasher? As last I've used this it was on an Xperia x10i lmao now I see there's no .exe to it
Click to expand...
Click to collapse
I didn't flashed vbmeta and for newsflasher just download the firmware and after copy all the files from newsflasher to the firmware folder.
raven213 said:
I patched my boot.img and after reboot to fastboot flashed patched img and reboot
Click to expand...
Click to collapse
I do the same when it's Android 12 and works well but today I flashed new firmware of Android 13, it failed.
wednesyao said:
I do the same when it's Android 12 and works well but today I flashed new firmware of Android 13, it failed.
Click to expand...
Click to collapse
What error do you get? I did a fresh installation of A13 maybe that's why?
raven213 said:
What error do you get? I did a fresh installation of A13 maybe that's why?
Click to expand...
Click to collapse
Emm sort of. It's because of my thermal remove module of scene5, once I disable it my phone's back.