Related
Hello,
I have bricked my P10 and I need some files for Oreo:
I have the system.img and the cust.img
I am missing:
boot.img , recovery and userdata.img
I have got the 2 I have extracting the update.zip but the other 3 are not available in the update.app from huawei inside the zip.
Can anyone upload the files for me or upload a TWRP backup as I have TWRP Oreo up and running in the P10 but I formatted everything and forgot to backup first.
Thank you very much.
PS: Resume I please need a TWRP backup of the OREO rom or the 3 missing files above, thank you very much.
there is no longer a boot.img and recovery.img for oreo. If I am not mistaken you are trying to use the multi_tool right?
You can use the ramdisk kernel and recovry_ramdisk files as replacement.
Userdata is not necessary from what I recon.
If you have a running TWRP I would strongly urge you to try to find a fix using that way. Such as by running HWOTA if you can.
martindoublem said:
there is no longer a boot.img and recovery.img for oreo. If I am not mistaken you are trying to use the multi_tool right?
You can use the ramdisk kernel and recovry_ramdisk files as replacement.
Userdata is not necessary from what I recon.
If you have a running TWRP I would strongly urge you to try to find a fix using that way. Such as by running HWOTA if you can.
Click to expand...
Click to collapse
Thank you but I can´t because HWOTA doesn´t recognise the TWRP. I am trying to use the multi_tool 8 but without success. I don´t know how to fix it at the moment, maybe SAT time?
martindoublem said:
there is no longer a boot.img and recovery.img for oreo. If I am not mistaken you are trying to use the multi_tool right?
You can use the ramdisk kernel and recovry_ramdisk files as replacement.
Userdata is not necessary from what I recon.
If you have a running TWRP I would strongly urge you to try to find a fix using that way. Such as by running HWOTA if you can.
Click to expand...
Click to collapse
I will try to not flash the recovery because I think TWRP is a better option at the moment?
The problem is that I can´t find any Oreo ROM that I can flash with TWRP and it would be awesome if someone share one although if it is very unstable just to be able to recover an OS.
martindoublem said:
there is no longer a boot.img and recovery.img for oreo. If I am not mistaken you are trying to use the multi_tool right?
You can use the ramdisk kernel and recovry_ramdisk files as replacement.
Userdata is not necessary from what I recon.
If you have a running TWRP I would strongly urge you to try to find a fix using that way. Such as by running HWOTA if you can.
Click to expand...
Click to collapse
Ramdisk kernel would be boot.img and recovery_ramdisk the recovery?
I have tried and it doesn´t recognise it so I think they are not the corresponding files it seems....
just download all 3 update packages of oreo from firmware finder. unpack them with huawei extract tool and you will have all partitions images. Or if you have erecovery pay 10 bucks to funky huawei and they will help you.
DallasCZ said:
just download all 3 update packages of oreo from firmware finder. unpack them with huawei extract tool and you will have all partitions images. Or if you have erecovery pay 10 bucks to funky huawei and they will help you.
Click to expand...
Click to collapse
I have a SAT near home, if they don´t help I will do the funky option...
If anyone needs, can use my DC-Phoenix account, I don`t need it anymore.
Your username is: cesedy
Your password is: dnL4eHEm
I need help getting my phone unbricked, because its my only phone, it bricked and it boots into black screen and i can't boot into recovery mode and fast boot mode, is there anyone who can help me, it bricked when i flashed TWRP because my phone was updated into MIUI 12.5
Edited: it shows the logo and it turns on but it will back screen when it reaches the boot animation and does nothing.
I've searched my way into every pieces on the internet to find answers on my phone, and i got some information about how to restore redmi note 9 into stock, by using EDL mode in the phone, you can reset the phone into stock firmware, but the problem is i don't know anything about the redmi note 9 main board and i don't know which specific jumper i should touch, i might destroy the board if i shorted any jumpers, i hope get answers on what jumper i should touch to enter EDL mode in Redmi note 9
PM me... i'll guide u
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop after flashed misc partition, you need to erase misc partition.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Click to expand...
Click to collapse
Thank you so much for the help bro, i unbricked my device but i still need help about downgrading MIUI, you have any guide to that? from preloader to every img?
VD171 said:
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop after flashed misc partition, you need to erase misc partition.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Click to expand...
Click to collapse
btw, i totaled my phone and it doesn't boot no more it just black screens and in computer, it shows mediatek comport, i installed the wrong vbmeta because i was planning to downgrade the phone, is there any fix on it?
briangwapo81 said:
Thank you so much for the help bro, i unbricked my device but i still need help about downgrading MIUI, you have any guide to that? from preloader to every img?
Click to expand...
Click to collapse
Choose your firmware and flash it as any other xiaomi. You can google about it.
briangwapo81 said:
btw, i totaled my phone and it doesn't boot no more it just black screens and in computer, it shows mediatek comport, i installed the wrong vbmeta because i was planning to downgrade the phone, is there any fix on it?
Click to expand...
Click to collapse
Read my post again: https://forum.xda-developers.com/t/my-phone-got-bricked.4224163/post-84373765
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
Choose your firmware and flash it as any other xiaomi. You can google about it.
Read my post again: https://forum.xda-developers.com/t/my-phone-got-bricked.4224163/post-84373765
Click to expand...
Click to collapse
no bro, i meant that the phone does not boot anymore and just shows this, your fix worked but, i really totaled my phone because it didn't flash, it errored
briangwapo81 said:
no bro, i meant that the phone does not boot anymore and just shows this, your fix worked but, i really totaled my phone because it didn't flash, it errored
Click to expand...
Click to collapse
What caused this ?
Did you try to flash the patched vbmeta or original stock vbmeta ?
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
What caused this ?
Did you try to flash the patched vbmeta or original stock vbmeta ?
Click to expand...
Click to collapse
i flashed the wrong VBmeta version and the wrong recovery version
briangwapo81 said:
i flashed the wrong VBmeta version and the wrong recovery version
Click to expand...
Click to collapse
Did you flash the patched vbmeta or original stock vbmeta ?
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
Did you flash the patched vbmeta or original stock vbmeta ?
Click to expand...
Click to collapse
the original one, but the thing is i installed the wrong version because my phone's miui is 12.5 but i installed vbmeta 11.5 original version
u want solution??
briangwapo81 said:
the original one, but the thing is i installed the wrong version because my phone's miui is 12.5 but i installed vbmeta 11.5 original version
Click to expand...
Click to collapse
Recovery partition is verified by vbmeta.
You need to disable verification in vbmeta.
Doesn't matter what version is, if vbmeta is disabled, it will not verify any partition.
If you flash any custom partition without disable verification on vbmeta (or change vbmeta version without disabled verification), it will keeps bricked until you flash original stock rom firmware.
If you are flashing anything, you are changing stock rom.
You can only change stock rom with unlocked bootloader.
If your bootloader is locked, it will keeps bricked until you flash stock rom and unlock bootloader.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Butterfly_Bites said:
u want solution??
Click to expand...
Click to collapse
Yes. Please, tell us your solution
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Butterfly_Bites said:
u want solution??
Click to expand...
Click to collapse
Will you please tell us?
briangwapo81 said:
Will you please tell us?
Click to expand...
Click to collapse
Obviously, he will try to sell you something.
Please, taken care.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
Recovery partition is verified by vbmeta.
You need to disable verification in vbmeta.
Doesn't matter what version is, if vbmeta is disabled, it will not verify any partition.
If you flash any custom partition without disable verification on vbmeta (or change vbmeta version without disabled verification), it will keeps bricked until you flash original stock rom firmware.
If you are flashing anything, you are changing stock rom.
You can only change stock rom with unlocked bootloader.
If your bootloader is locked, it will keeps bricked until you flash stock rom and unlock bootloader.
Click to expand...
Click to collapse
yeah, i used the disable verification command on vbmeta, the bootloader is unlocked, but the issue is that i installed the wrong version of the vbmeta, and other things are that my device won't sow in mi flash or SP flash tool, but it shows up in platform tools when the phone was in fastboot mode
VD171 said:
Obviously, he will try to sell you something.
Please, taken care.
Click to expand...
Click to collapse
that's what i doubt too.
briangwapo81 said:
yeah, i used the disable verification command on vbmeta, the bootloader is unlocked, but the issue is that i installed the wrong version of the vbmeta, and other things are that my device won't sow in mi flash or SP flash tool, but it shows up in platform tools when the phone was in fastboot mode
Click to expand...
Click to collapse
Can you record your bootloop?
Please, read careful this FAQ and reply with your bootloop record in this thread: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
I made the mistake of reading that the firmware is the same for all three 10S models, and accidentally flashed the wrong magisk-patched boot.img.
Now, to fix my phone i Need to flash the original boot.img, but I can't find online the ROM for the Maltose variant.
Anyone can help?
I was able to find a dump of the file from here. And though that fixed my boot issue (note: the dump says it's for MIUI V12.5.14.0, whereas my phone has version V12.5.13), I still can't get root because when I patch that file with Magisk, and flash it via fastboot, it doesn't boot, and goes to FastBoot until I reflash the original.
So, the question now is, where can I find a patched boot.img for [Maltose]?
Since there's nearly no threads regarding Maltose, it might be best to leave this thread here for future reference of other users.
armaldon said:
I was able to find a dump of the file from here. And though that fixed my boot issue (note: the dump says it's for MIUI V12.5.14.0, whereas my phone has version V12.5.13), I still can't get root because when I patch that file with Magisk, and flash it via fastboot, it doesn't boot, and goes to FastBoot until I reflash the original.
So, the question now is, where can I find a patched boot.img for [Maltose]?
Since there's nearly no threads regarding Maltose, it might be best to leave this thread here for future reference of other users.
Click to expand...
Click to collapse
maltose is rosemary
Okay, that seems correct. I downloaded the RoseMary IMG version 12.5.13.0 and extracted the boot.img file, after flashing it on my device's boot A & B partitions, it does boot correctly.
I am still having issues rooting my phone, but I guess that's a different issue and requires it's own topic.
Hello! I would like to root my Realme c25s [RMX3195_11_A.19] phone. I can not find the necessary files to install twrp. Named Vbmeta.img and Recovery.img (Recovery is the TWRP firmware itself, but I couldn’t find the Vbmeta.img file ANYWHERE on the Internet that matches my firmware version). As far as I understand, both files must be of the same version (A.19 in my case), otherwise it is possible to turn the phone into a brick. If you have experience flashing this device of the same assembly as mine, or if you know how to do it, please attach ALL the files that you used to flash. Thank you!
Metro1919 said:
Hello! I would like to root my Realme c25s [RMX3195_11_A.19] phone. I can not find the necessary files to install twrp. Named Vbmeta.img and Recovery.img (Recovery is the TWRP firmware itself, but I couldn’t find the Vbmeta.img file ANYWHERE on the Internet that matches my firmware version). As far as I understand, both files must be of the same version (A.19 in my case), otherwise it is possible to turn the phone into a brick. If you have experience flashing this device of the same assembly as mine, or if you know how to do it, please attach ALL the files that you used to flash. Thank you!
Click to expand...
Click to collapse
your vbmeta can be found in the firmware file (ofp)
I would like to know if someone has managed to root with magisk from CMD without twrp?
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
or965 said:
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
Click to expand...
Click to collapse
ive use your method but my phone still gone to bootloop. im using eu rom currently.
martin132014 said:
ive use your method but my phone still gone to bootloop. im using eu rom currently.
Click to expand...
Click to collapse
What did you do? I wrote several options.
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
System23 said:
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
Click to expand...
Click to collapse
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
or965 said:
What did you do? I wrote several options.
Click to expand...
Click to collapse
I use the method for eu that you posted. First i install magisk 25.2 and then i patch the rom boot.img. I boot to fastboot and flash the patch boot.img using the command. It flash successful then i reboot. But it still bootloop.
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
martin132014 said:
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
Click to expand...
Click to collapse
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
martin132014 said:
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
Click to expand...
Click to collapse
and what your experience with that!!! Tell me why you like this!!!
System23 said:
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
Click to expand...
Click to collapse
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
ok a Tip to you!!! when you only Backup Data Partition you can restore it and all Contacts,SMS,Accounts,Apps are availibile again on new ROM!!!
Why you dont use the Magisk.zip and flash it via TWRP after Flash ROM!!! you can rename Magisk.apk to Magisk.zip and flash it!! than you dont need other steps to Root!!! when it dosnt work use the recovery.img to Patch it and try this Method for Rooting, but dont forgett when ya do so you need to try the Buttons-Combo to start in Recovery to boot the System in Root and you have no Recovery-Mode at this Method!!! Also to use Recovery again you must Flash it again via Fastboot!!
And in TWRP use the WIPE Option to make a Factory Reset or WIPE a Single Partition, after some Flashing CROMS its needed to be WIPE the Data Partition!!!
martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
you can ask me what you would i share my Informations with ya!!! when iam not knowing iam googleing it out to find a solution!! the talk we have start are hope helpfully!! when ya have intresst we can stay in kontakt and make what we can, even its public 4 all or PM!!! PS i must not hide my Knowledge, but PM its OK too!!!