I tried installing fastboot images extracted from ozip files but vendor and system images gave partision not found error and I didn't have a windows device I had ubuntu
I installed .ofp by this way
I had bootloader unlocked, please report if it works without bootloader unlocked
1.Download .ofp file of your device
https://c.realme.com/in/post-details/1271381271037083648 this is link for Indian version from realme's website
2.extract .ofp file, I did it using https://github.com/bkerler/oppo_decrypt (This took awfully long time for me)
3.Go to fastboot and flash all the files through fastboot commands
( 1. fastboot flash boot boot.img 2.fastboot flash super super.img 3.fastboot flash vbmeta vbmeta.img 4. fastboot flash vbmeta_system vbmeta_system.img 5.fastboot flash vbmeta_vendor vbmeta_vendor.img 6.fastboot flash userdata userdata.img)
in this order
4.go to stock recovery and format and wipe data
5.Now you should be able to boot
(If anyone wants stock recovery tell me I'll give link)
thank you very much this have save me a lot of times.
my windows computer have problem with fastboot driver. i installed realme adb-fastboot driver again and again but it doesnt work, device manager still have ''question mark'' android driver, maybe windows need to be reinstall or something... i use the same pc to unlock bootloader before,
i unpack the ozip on raspbian (using raspberry pi 3 with microsd) , fastboot flash realme x 3 that i messed up before and now it work.
Shreeram02 said:
I tried installing fastboot images extracted from ozip files but vendor and system images gave partision not found error and I didn't have a windows device I had ubuntu
I installed .ofp by this way
I had bootloader unlocked, please report if it works without bootloader unlocked
1.Download .ofp file of your device
https://c.realme.com/in/post-details/1271381271037083648 this is link for Indian version from realme's website
2.extract .ofp file, I did it using https://github.com/bkerler/oppo_decrypt (This took awfully long time for me)
3.Go to fastboot and flash all the files through fastboot commands
( 1. fastboot flash boot boot.img 2.fastboot flash super super.img 3.fastboot flash vbmeta vbmeta.img 4. fastboot flash vbmeta_system vbmeta_system.img 5.fastboot flash vbmeta_vendor vbmeta_vendor.img 6.fastboot flash userdata userdata.img)
in this order
4.go to stock recovery and format and wipe data
5.Now you should be able to boot
(If anyone wants stock recovery tell me I'll give link)
Click to expand...
Click to collapse
I followed the same steps, but no luck. later i checked in twrp and it says no os installed.
ash1337x said:
I followed the same steps, but no luck. later i checked in twrp and it says no os installed.
Click to expand...
Click to collapse
ignore twrp thing and u didn't follow everything as u have twrp u should install stock recovery
everything is cool but i have multiple super imgs what do i do?
Shreeram02 said:
I tried installing fastboot images extracted from ozip files but vendor and system images gave partision not found error and I didn't have a windows device I had ubuntu
I installed .ofp by this way
I had bootloader unlocked, please report if it works without bootloader unlocked
1.Download .ofp file of your device
https://c.realme.com/in/post-details/1271381271037083648 this is link for Indian version from realme's website
2.extract .ofp file, I did it using https://github.com/bkerler/oppo_decrypt (This took awfully long time for me)
3.Go to fastboot and flash all the files through fastboot commands
( 1. fastboot flash boot boot.img 2.fastboot flash super super.img 3.fastboot flash vbmeta vbmeta.img 4. fastboot flash vbmeta_system vbmeta_system.img 5.fastboot flash vbmeta_vendor vbmeta_vendor.img 6.fastboot flash userdata userdata.img)
in this order
4.go to stock recovery and format and wipe data
5.Now you should be able to boot
(If anyone wants stock recovery tell me I'll give link)
Click to expand...
Click to collapse
Send me stock recovery please
prabal_2004 said:
everything is cool but i have multiple super imgs what do i do?
Click to expand...
Click to collapse
Yes, 4 or 5 super img files how to flash
4 or more super img files, with defrent name
Sajeevkaif said:
4 or more super img files, with defrent name
Click to expand...
Click to collapse
If all of them have the same size, then they're duplicated, rename one of them to super.img, and delete the others.
SubwayChamp said:
If all of them have the same size, then they're duplicated, rename one of them to super.img, and delete the others.
Click to expand...
Click to collapse
for me, i have 1 super.0 file with 2.86gb
1 super.1 file 1.95gb
and 12 super.2 files ranging 800mb to 1.8gb
what should i get for the super.img?
i opened the super_map.csv and saw this(the picture below)
the super0 and super1 for all country is the same, and in the super2 is different
should i get my super.img from the super2 with my country?
CloudChase said:
i opened the super_map.csv and saw this(the picture below)
the super0 and super1 for all country is the same, and in the super2 is different
should i get my super.img from the super2 with my country?
Click to expand...
Click to collapse
Sometimes the tool split the super images, and sometimes it unpacks it in a one single file, but I guess the size can't be less than 5 or even 6 GB.
SubwayChamp said:
Sometimes the tool split the super images, and sometimes it unpacks it in a one single file, but I guess the size can't be less than 5 or even 6 GB.
Click to expand...
Click to collapse
the overall size of the ofp file for the global version of realme c25s is 21gb, do you need authorization when using the Realme Flash Tool?
SubwayChamp said:
Sometimes the tool split the super images, and sometimes it unpacks it in a one single file, but I guess the size can't be less than 5 or even 6 GB.
Click to expand...
Click to collapse
what should i do? i need to fix my phone
CloudChase said:
the overall size of the ofp file for the global version of realme c25s is 21gb, do you need authorization when using the Realme Flash Tool?
Click to expand...
Click to collapse
CloudChase said:
what should i do? i need to fix my phone
Click to expand...
Click to collapse
I referred to the super image size, it's unlikely that the image has just this size, anyway it doesn't hurt to try it, flash some of them and see, you can try using fastboot too.
SubwayChamp said:
If all of them have the same size, then they're duplicated, rename one of them to super.img, and delete the others.
Click to expand...
Click to collapse
No, all of threm have Difrent name and size (more than a gb file)
Sajeevkaif said:
No, all of threm have Difrent name and size (more than a gb file)
Click to expand...
Click to collapse
Did you try flashing one of them?
SubwayChamp said:
Did you try flashing one of them?
Click to expand...
Click to collapse
No,
There is a tool to merge Super Image if they are split into multiple files.
Follow this tutorial to merge it. Find the exact tool from Google search and ensure it has the orange logo as seen in the video.
my bad I didn't open xda for a long time as this device doesn't have much support on xda
yea only a10 has 1 super img other ones have multiple super imgs
if ur in still in stock u can use partition backup app(needs root) from playstore to backup required img files
I'll try to upload separate img files from a11 and a12 backed up here soon
Related
Hi!
I have unlocked bootloader, then rooted and added twrp recovery, successfully without issues.
then i tried flashing viper4android for oreo, and now it wont boot.
ive tried the viper4android uninnstaler provided in the same thred and still dosent boot.
i tried installing another dolby atmos with viper and a uninstaller, dont work either.
should factory reset fix it? it dosent in that case..
any ideas?
https://forum.xda-developers.com/android/software/sound-mod-viper4android-oreo-t3734107
and it seems i cant take backup of the system to internal storage due to twrp bug,
ive tried backinguppon a 16gb usb3.0 device thru otg adapter with fat32 it stops at 3999 and backupp fails.
i tried otg to usb with 16gb microsdcard, also stopped at 3999 and failed.
i tried usb with ntfs but the it wont backupp at all.
what can i wipe?
installing stock a solution? how? flash update.app?(in zip).
custom rom?
is there any reason to lock the bootloader again?
Maximum file size of FAT32 is only 4GB per file. Use Huawei update extractor to get img files from update.app file. Flash those to your phone using fastboot. You can relock bootloader once you are in stock EMUI. Just run fastboot oem relock *your unlock code*.
EngrVan said:
Maximum file size of FAT32 is only 4GB per file. Use Huawei update extractor to get img files from update.app file. Flash those to your phone using fastboot. You can relock bootloader once you are in stock EMUI. Just run fastboot oem relock *your unlock code*.
Click to expand...
Click to collapse
ok thx^^ what files from the update.app? dont find any boot.img.
and recovery or recovery ramdisk.. dont really know what to write in that case
Extract system.img and ramdisk.img.
In fastboot, write:
fastboot flash system system.img
fastboot flash ramdisk ramdisk.img
Just rename you img files or use whatever name you like.
EngrVan said:
Extract system.img and ramdisk.img.
In fastboot, write:
fastboot flash system system.img
fastboot flash ramdisk ramdisk.img
Just rename you img files or use whatever name you like.
Click to expand...
Click to collapse
ok thx will try ^^
EngrVan said:
Extract system.img and ramdisk.img.
In fastboot, write:
fastboot flash system system.img
fastboot flash ramdisk ramdisk.img
Just rename you img files or use whatever name you like.
Click to expand...
Click to collapse
flashed both, but still the same, bootloop..
flash other files??
Fixed after many hours trying to flash stock
using this!
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
614Emil said:
Fixed after many hours trying to flash stock
using this!
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
what did you use and how to start... to fix it... please share the steps...
Hello!
Posting here because the model doesn't have its forum.
My phone is currently unlocked with phh-trebmble android 9 and the rom has rather crucial problems - apps crashing, no auto brightness, unable to connect to networks with hidden SSID and some more.
Unfortunately I cannot find a guide showing a working method [atleast for my case] to flash the stock rom.
I got the stock rom from firmwarex .net and tried flashing it with QFIL. At first the program couldn't locate a usable file for the "programmer path". After seeing multiple guides for the program I saw that everyone is using the same file "prog_emmc_firehose_8936.mbn" so I got the file, placed it in the rom folder and selected it from the QFIL. When i start the download proccess it returns Sahara error so I am unable to complite the recovery.
As it is somewhat scuffed method with spare parts from here and there could anyone point me to somthing that I am missing or doing wrong.
P.S. Phone is in download mode when I'm trying to flash trough QFIL, QFIL is seeng the phone on the port.
Flash stock rom lenovo k5
try turning off your internet connection and flash sorry for my inglis I'm using google translate
Nox.BG said:
Hello!
Posting here because the model doesn't have its forum.
My phone is currently unlocked with phh-trebmble android 9 and the rom has rather crucial problems - apps crashing, no auto brightness, unable to connect to networks with hidden SSID and some more.
Unfortunately I cannot find a guide showing a working method [atleast for my case] to flash the stock rom.
I got the stock rom from firmwarex .net and tried flashing it with QFIL. At first the program couldn't locate a usable file for the "programmer path". After seeing multiple guides for the program I saw that everyone is using the same file "prog_emmc_firehose_8936.mbn" so I got the file, placed it in the rom folder and selected it from the QFIL. When i start the download proccess it returns Sahara error so I am unable to complite the recovery.
As it is somewhat scuffed method with spare parts from here and there could anyone point me to somthing that I am missing or doing wrong.
P.S. Phone is in download mode when I'm trying to flash trough QFIL, QFIL is seeng the phone on the port.
Click to expand...
Click to collapse
I'm stuck on the "fire hose" file. QFIL seems to not detected the phone.
Did you managed to solve the problem?
Lenovo K5 Pro ROM
After flashing IMG file (using TWRP 3.3.1) the phone (Lenovo k5 pro) always starts in bootloader mode. Everyone can help?
ShmuelCohen said:
After flashing IMG file (using TWRP 3.3.1) the phone (Lenovo k5 pro) always starts in bootloader mode. Everyone can help?
Click to expand...
Click to collapse
Did you get any solution, I have the same problem.
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
Thank you so much for this post.
After many many many attempts to repair my device through qfil without success, I tried what you wrote in the post and thank God I finally succeeded so thank you very much.
However for some reason I can not update the system version because he thinks I have root, no matter what I did I could not fix it.
Any ideas?
I also wanted to ask, for what should a userdata partition be flashed? It is always built on its own. I'm wrong?
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
Resuscitated my K5 Pro, thank you very much your comment saved me!:victory::victory:
help me what is the correct file to download to flash android 10 on lenovo k5 pro. Gapps and custom rom please help. Im stock the google pixel logo boot screen for almost an hour.
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
.
shisho585 said:
Thank you so much for this post.
After many many many attempts to repair my device through qfil without success, I tried what you wrote in the post and thank God I finally succeeded so thank you very much.
However for some reason I can not update the system version because he thinks I have root, no matter what I did I could not fix it.
Any ideas?
I also wanted to ask, for what should a userdata partition be flashed? It is always built on its own. I'm wrong?
Click to expand...
Click to collapse
.
iugleafar said:
Resuscitated my K5 Pro, thank you very much your comment saved me!:victory::victory:
Click to expand...
Click to collapse
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
.
I installed EMUI 9 on my p20 lite and didn't like it, so I tried one of the openkirin 9.0 beta roms. There was some features that didn't work so I decided I wanted to go back. I followed the guide on openkirin's website about going back to stock by flashing system.img, ramdisk.img, kernel.img and recovery_ramdisk.img however trying to flash ramdisk.img gives "partition length get error". Now, the phone only is able to boot into fastboot and eRecovery mode. In eRecovery the options to backup and to factory reset are grayed out however, and the "update to latest version" doesn't work. When I plug the charger in from being turned off it shows the white error screen with error 10 (boot image) and error 2 (load failed). I have a suspicion that flashing kernel.img is what causing the problem, but I don't really know enough to be sure and I don't want to do anything to make it worse since it seems like this should be fixable.
This is the only phone I have which properly worked so any help is greatly appreciated.
Hi there
Don't worry, it's fixable
There's way bigger mess than that, so the best solution for you and the easiest one is to flash a signed dload package, which you can find for your model and build number in this website:
https://androidhost.ru/search.html
Search in this format "ANE-LX1C66".
Then extract it and copy the "dload" folder to the root of your sd card.
Then power off your device if it isn't and then press POWER + Volume Plus + Volume Minus at the same time until a circle with EMUI appears.
That will erase all data and lock your bootloader.
Cheers!
AS
ars_chelsea said:
Hi there
Don't worry, it's fixable
There's way bigger mess than that, so the best solution for you and the easiest one is to flash a signed dload package, which you can find for your model and build number in this website:
https://androidhost.ru/search.html
Search in this format "ANE-LX1C66".
Then extract it and copy the "dload" folder to the root of your sd card.
Then power off your device if it isn't and then press POWER + Volume Plus + Volume Minus at the same time until a circle with EMUI appears.
That will erase all data and lock your bootloader.
Cheers!
AS
Click to expand...
Click to collapse
Ah, yeah, forgot to mention I already tried that. Unfortunately it doesn't work. It just says "software install failed". I'm genuinely about to throw this f***ing thing into orbit
Thanks for your help though.
Afifus said:
Ah, yeah, forgot to mention I already tried that. Unfortunately it doesn't work. It just says "software install failed". I'm genuinely about to throw this f***ing thing into orbit
Thanks for your help though.
Click to expand...
Click to collapse
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
ars_chelsea said:
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
Click to expand...
Click to collapse
Tried Oreo build 150 for ane-lx1c432 and ane-lx1c782 since those are the only models my phone could be.
Although, when I do the get-build-number command in fastboot it still says I'm on a Pie build. I'm gonna try doing a Pie build and I'll get back to you.
ars_chelsea said:
That's weird, are you sure you are installing the right package for your device? It's rare to fail with a correct package.
What's your build number and model ?
Click to expand...
Click to collapse
Yeah, pie didn't work either.
Afifus said:
Yeah, pie didn't work either.
Click to expand...
Click to collapse
But there is no signed package for those models yet, what dload files did you use?
Cheers,
AS
ars_chelsea said:
But there is no signed package for those models yet, what dload files did you use?
Cheers,
AS
Click to expand...
Click to collapse
I got it off of firmware finder. Are those not signed?
Afifus said:
I got it off of firmware finder. Are those not signed?
Click to expand...
Click to collapse
No, those are not signed, you need the dload files from Androidhost.ru since it's the only place you can get them for free, here's a link for both the versions you showed:
Single SIM ANE-LX1C432: https://androidhost.ru/Utm
Dual SIM ANE-LX1C432: https://androidhost.ru/Utn
Single SIM ANE-LX1C782: https://androidhost.ru/29Zn
Dual SIM ANE-LX1C782: https://androidhost.ru/1jzD
Choose the right one, and follow the procedure I sent you in a reply above.
ars_chelsea said:
No, those are not signed, you need the dload files from Androidhost.ru since it's the only place you can get them for free, here's a link for both the versions you showed:
Single SIM ANE-LX1C432: https://androidhost.ru/Utm
Dual SIM ANE-LX1C432: https://androidhost.ru/Utn
Single SIM ANE-LX1C782: https://androidhost.ru/29Zn
Dual SIM ANE-LX1C782: https://androidhost.ru/1jzD
Choose the right one, and follow the procedure I sent you in a reply above.
Click to expand...
Click to collapse
Cheers, but unfortunately neither of those worked. I'm at a loss on what else I could try.
Afifus said:
Cheers, but unfortunately neither of those worked. I'm at a loss on what else I could try.
Click to expand...
Click to collapse
at less you back to emui 9.1 only to save your phone
first download the firmware from tm team database search the right firmware for your phone
after that unzip the two files then use huawei extractor to extract files from update.app
and follow this instructions
Copy to the following partitions to the adb fastboot folder:
recovery_ramdisk
recovery_vbmeta
recovery_vendor
cust
kernel
system
userdata
product
vendor
Then boot your device in fastboot mode.
note if you dont found recovery ramdisk then rename recovery ramdis to previous name
The commands for fastboot:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash system system.img
aftet that make a wipe / factory reset
what happen to you happen to me the same thing if this work after that then be patience until we get official emui, the last news that i read that huawei postpone release until july
Thanks to kilroystyx
Try this and tell me
yassine2217 said:
at less you back to emui 9.1 only to save your phone
first download the firmware from tm team database search the right firmware for your phone
after that unzip the two files then use huawei extractor to extract files from update.app
and follow this instructions
Copy to the following partitions to the adb fastboot folder:
recovery_ramdisk
recovery_vbmeta
recovery_vendor
cust
kernel
system
userdata
product
vendor
Then boot your device in fastboot mode.
note if you dont found recovery ramdisk then rename recovery ramdis to previous name
The commands for fastboot:
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash recovery_vbmeta recovery_vbmeta.img
fastboot flash recovery_vendor recovery_vendor.img
fastboot flash cust cust.img
fastboot flash kernel kernel.img
fastboot flash system system.img
aftet that make a wipe / factory reset
what happen to you happen to me the same thing if this work after that then be patience until we get official emui, the last news that i read that huawei postpone release until july
Thanks to kilroystyx
Try this and tell me
Click to expand...
Click to collapse
Holy f*** thank you. That seems to have worked. It also seems to have fixed the sms problem I had with 9.1.
Afifus said:
Holy f*** thank you. That seems to have worked. It also seems to have fixed the sms problem I had with 9.1.
Click to expand...
Click to collapse
great happy for you
Hi!
I cant enter the MSM Download Tool app provided in ROMs folder. Does anyone know hoy to solve it?
I need to unbrick my phone
Sorry to say that you will have to pay an Indian to recover your phone, the MSM downloader requires an authorized id
I have a similar problem: accidentally i format the system partition and now i can only enter in recovery e fastboot mode but i can't install anything roms. Is there a way to restore stock rom or force a custom rom? Thanks.
I fixed it using part of this guide ->https://forum.xda-developers.com/t/unbrick-realme-7-pro-ui-1-0-android10.4347457/:
- Flash a custom recovery (i use twrp) and start the phone in recovery.
- Download the official rom ozip for realme 7 pro (i use the eu version).
- Start the phone in recovery and connect the phone to a pc and copy the ozip in it (i created a folder named "roms").
- Download a OFP Rom (the only i find are indian version).
- Download "MCT ofp extract tool" (for prevent virus warning it is possible use a vm machine...i used a second pc) and extract the OFP Rom.
- Download "minimal adb portable" and extract in the OFP Rom folder (where are the files of ofp rom extracted).
- Via fastboot flash the follow img:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
- Now start the phone in recovery (will be the stock recovery).
- Wipe and after that flash the ozip file.
- After that format the memory phone (always via stock recovery).
- Reboot and that's all the phone start via with stock rom.
After configuration there are some update with the last ota dated 28/10/2021.
I hope, someone, will find it usefull.
alien762 said:
I fixed it using part of this guide ->https://forum.xda-developers.com/t/unbrick-realme-7-pro-ui-1-0-android10.4347457/:
- Flash a custom recovery (i use twrp) and start the phone in recovery.
- Download the official rom ozip for realme 7 pro (i use the eu version).
- Start the phone in recovery and connect the phone to a pc and copy the ozip in it (i created a folder named "roms").
- Download a OFP Rom (the only i find are indian version).
- Download "MCT ofp extract tool" (for prevent virus warning it is possible use a vm machine...i used a second pc) and extract the OFP Rom.
- Download "minimal adb portable" and extract in the OFP Rom folder (where are the files of ofp rom extracted).
- Via fastboot flash the follow img:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
- Now start the phone in recovery (will be the stock recovery).
- Wipe and after that flash the ozip file.
- After that format the memory phone (always via stock recovery).
- Reboot and that's all the phone start via with stock rom.
After configuration there are some update with the last ota dated 28/10/2021.
I hope, someone, will find it usefull.
Click to expand...
Click to collapse
bro i did everything and i unbricked my phone successfully (thanks to you and that thread https://forum.xda-developers.com/t/unbrick-realme-7-pro-ui-1-0-android10.4347457/ )
but i still have a problem that my fingerprint doesn't work and i did not backup persist.
please help me bro - Thanks in advance.
alien762 said:
I fixed it using part of this guide ->https://forum.xda-developers.com/t/unbrick-realme-7-pro-ui-1-0-android10.4347457/:
- Flash a custom recovery (i use twrp) and start the phone in recovery.
- Download the official rom ozip for realme 7 pro (i use the eu version).
- Start the phone in recovery and connect the phone to a pc and copy the ozip in it (i created a folder named "roms").
- Download a OFP Rom (the only i find are indian version).
- Download "MCT ofp extract tool" (for prevent virus warning it is possible use a vm machine...i used a second pc) and extract the OFP Rom.
- Download "minimal adb portable" and extract in the OFP Rom folder (where are the files of ofp rom extracted).
- Via fastboot flash the follow img:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
- Now start the phone in recovery (will be the stock recovery).
- Wipe and after that flash the ozip file.
- After that format the memory phone (always via stock recovery).
- Reboot and that's all the phone start via with stock rom.
After configuration there are some update with the last ota dated 28/10/2021.
I hope, someone, will find it usefull.
Click to expand...
Click to collapse
Hi, man.
I really need help with this one. I have a bricked device.
So, can you provide me with the twrp? I tried to install one but can't find the right one. Also, I'm stuck with this "boot destroyed" thing. Have tried to fix it--and it seems there's step in your solution above that I've tried as well (aka. flashing boot, vbmeta, super, etc.) but still can't get it work. Do you have any idea?
Cause it seems that I have to fix the boot destroyed thing first.
TIA
pls bro help me...Wipe and after that flash the ozip file?OZIP THATS mean stock rom or?
alien762 said:
I fixed it using part of this guide ->https://forum.xda-developers.com/t/unbrick-realme-7-pro-ui-1-0-android10.4347457/:
- Flash a custom recovery (i use twrp) and start the phone in recovery.
- Download the official rom ozip for realme 7 pro (i use the eu version).
- Start the phone in recovery and connect the phone to a pc and copy the ozip in it (i created a folder named "roms").
- Download a OFP Rom (the only i find are indian version).
- Download "MCT ofp extract tool" (for prevent virus warning it is possible use a vm machine...i used a second pc) and extract the OFP Rom.
- Download "minimal adb portable" and extract in the OFP Rom folder (where are the files of ofp rom extracted).
- Via fastboot flash the follow img:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash persist persist.img
fastboot flash recovery recovery.img
- Now start the phone in recovery (will be the stock recovery).
- Wipe and after that flash the ozip file.
- After that format the memory phone (always via stock recovery).
- Reboot and that's all the phone start via with stock rom.
After configuration there are some update with the last ota dated 28/10/2021.
I hope, someone, will find it usefull.
Click to expand...
Click to collapse
help plis ???
I would be grateful if someone could upload the new A18 boot.img global , from the latest update patched with magic or original.
where is the firmware? you can extract the boot.img and patch it yourself. It is easy.
I know it can be done easily, but I don't have the firmware. The phone downloaded the update and I didn't think about it and restarted the phone.
I think that after the update the phone deletes the file that was used for the update.
By the way, it's the boot image, not the bootloader.
Thank you.
Rapper_skull said:
By the way, it's the boot image, not the bootloader.
Rapper_skull said:
By the way, it's the boot image, not the bootloader.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Rapper_skull said:
If I were not Italian: I flashed your modified boot, now the phone is in bootloop, I don't know how to recover it since I can't find the link to download the firmware anywhere. Could you please pass me the original boot? help me please
Click to expand...
Click to collapse
Rapper_skull said:
Ciao sei italiano? ho visto la località di napoli! Io ho flashato la boot, ora ho bootloop!! Puoi passarmi la boot originale? per favore sono disperato non so come recuperarlo
non riesco a trovare da nessuna parte il firmware.zip da scaricare per prelevare la boot. In caso hai telegram? su telegram mi trovi x91xmarcox91x
Click to expand...
Click to collapse
marco.chinagliaxx91 said:
If I were not Italian: I flashed your modified boot, now the phone is in bootloop, I don't know how to recover it since I can't find the link to download the firmware anywhere. Could you please pass me the original boot? help me please
Click to expand...
Click to collapse
EU or global, the boot.img is the same. You probably bootlooped because you have to do
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Attached you can find the original boot.img
Rapper_skull said:
EU or global, the boot.img is the same. You probably bootlooped because you have to do
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Attached you can find the original boot.img
Click to expand...
Click to collapse
this comand
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
first or later the flash boot?
marco.chinagliaxx91 said:
this comand
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
first or later the flash boot?
Click to expand...
Click to collapse
After the flash, but of course you have to get the vbmeta.img file.
Rapper_skull said:
EU or global, the boot.img is the same. You probably bootlooped because you have to do
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Attached you can find the original boot.img
Click to expand...
Click to collapse
it doesn't work, I thought it was the same eu or global as in the oneplus. How can I do now?
Rapper_skull said:
After the flash, but of course you have to get the vbmeta.img file.
Click to expand...
Click to collapse
i can't find the entire firmware online.
marco.chinagliaxx91 said:
i can't find the entire firmware online.
Click to expand...
Click to collapse
I am writing a post with all the firmware links right now. Please wait.
Rapper_skull said:
I am writing a post with all the firmware links right now. Please wait.
Click to expand...
Click to collapse
tnk
Rapper_skull said:
I am writing a post with all the firmware links right now. Please wait.
Click to expand...
Click to collapse
let me know here then when you finished the post, thanks man
marco.chinagliaxx91 said:
let me know here then when you finished the post, thanks man
Click to expand...
Click to collapse
[Global/EU] Collection of firmware files
Since a lot of people is asking for firmware files, OTAs, boot.img, I decided to collect all the resources here, so that it would be easier to get what you need. First of all, you have to identify your ROM version. It is not the scope of this...
forum.xda-developers.com
What procedure did you use to flash.
I recommend this one:
Quake94 said:
EDIT: Uploaded A.16 Global ROM.
Ok so for anyone struggling, here is what I did to flash 3300 to 3301 Global & root w/safety net. I hope myogui can update original post because many of us are puzzling pieces of information from different sources. Credits to @myogui, @hacls and Shato from 4pda.to forum
Myogui Google Drive has A.10 version. As of now, the newest official version is A.17.
EDIT1: A.16 Global ROM with A.16 patched boot.img is available here.
super.img is a compressed 7zip archive, extract to the same directory as other files.
https://drive.google.com/drive/folders/1Y5mZtZchLytYqDqs0sOYTqCmaZeURrJ5?usp=sharing
EDIT2: Magisk A.17 patched boot.img added to Google drive credit @themagicalImage22
https://drive.google.com/file/d/1k6-K8vRlEnZJXPH6z_t5QHy5Kiud2sGX/view?usp=sharing
If you unlock bootloader the Widevine will be L3. Netflix will not stream in HD.
As of now, there is no official method to restore L1
Locking bootloader does not fix it. Root or stock does not fix it.
OTA update does not fix it.
To check Widevine level, you can use app DRMInfo
1. Download platform-tools for fastboot:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2. Download the Global ROM files (*.img) and put them in the same folder as the platform-tools where your fastboot is. Sometimes the super.img gets renamed to super-001.img, so change name back to super.img
3. Connect phone in fastboot. If drivers are not installed or working, fix it via Windows Update -> Check Updates -> Optional Updates -> Drivers -> Google + FTDI
4. Run the deep testing apk, and after it's approved let it go into bootloader mode.
5. Connect phone to PC. If fastboot shows "waiting for devices", exit, go into Windows Update and check for updates. Then go to Optional Updates and select & install Android Google driver. (Windows 10-11)
6. Complete the unlocking of bootloader with fastboot flashing unlock
7. Follow flashing like below credit @hacls
NOTE 1: You can also run fastboot getvar current-slot to check which partition is active before running fastboot --set-active=a
NOTE 2: You can flash stock nonroot boot.img first and root later with 1 command. Otherwise, flash a patched boot.img that matches the ROM version.
NOTE 3: When flashing super.img, error message will display "Invalid sparse file format in header", it will look frozen but this is OK, leave it running.
Locking bootloader:
If you don't care about root and don't plan to root in future, follow @sanya_rnd guide:
NOTE: CAREFUL - High risk of hard brick if the data was not wiped in step 4. All partitions must be stock, no root.
For unlocked bootloader:
Rooting with Magisk:
The newest Global version as of now is A.17.
NOTE: Patched boot.img has to match the version of the ROM.
7. After flashing global rom check what is most up to date version available via the software update.
You will have to disable automatic system updates to keep the root if Realme releases newer ROM.
7a. Reboot back to bootloader (if you have ADB debugging enabled in Developer Options, run adb reboot bootloader, otherwise you can do the Power + volume down method)
Download appropriate patched boot.img
bootA10magisk.img for A.10
https://drive.google.com/file/d/1hBxqFe7XzO7hub-jgZjsFfAHo4XIdjlm/view?usp=sharing
bootA16magisk.img for A.16
https://drive.google.com/file/d/1pyz7VFkiPjnkzizWfSJjOe836yinQR1w/view?usp=sharing
bootA17magisk.img for A.17
https://drive.google.com/file/d/1k6-K8vRlEnZJXPH6z_t5QHy5Kiud2sGX/view?usp=sharing
7b. Run fastboot getvar current-slot .
Replace the "bootXXXmagisk" with a correct filename for patched magisk file
- If it shows boot B partition, run fastboot flash boot_b bootXXXmagisk.img
- If it shows boot A partition, run fastboot flash boot_a bootXXXmagisk.img
7.c Reboot device with fastboot reboot
7.d Complete Magisk app install
Install Magisk modules (you have to copy .zip files):
SafetyNetFix : https://github.com/kdrag0n/safetynet-fix/releases
Shamiko : https://github.com/LSPosed/LSPosed.github.io/releases
7.e Activate Zygisk in Magisk
7.f Go to configure DenyList and add in any apps you want to hide Magisk from like banking apps.
However - Don't enable the "Activate DenyList" option! This is required by Shamiko hide Magisk module
Just adjust the DenyList.
7.g Restart phone and enjoy root
Safety Net passes with BASIC evaluation type
Additional notes:
Magisk updates can be installed with "Direct Install (recommended)"
Manual extracting of boot.img and other files from original ROM OFP file:
Flash files can be extracted using Oppo Decrypt from:
https://github.com/bkerler/oppo_decrypt
I advise against using MCT OFP Extractor Tool as it contains a ransomware Trojan:Win32/Trickbot!ml
Untested OTA-update preserving root method (proceed at your own risk!)
- Copy current ROM version stock boot.img to storage
- Open Magisk and select install -> Patch file -> Select the stock boot.img
- Restart phone.
This will generate Magisk "backup image" folder
- Go to Magisk -> Restore Images
- Go to OTA update and select to download update. Once it finishes the "Extracting" process, do not click "Install" in the updater!
- Go back to Magisk app and select Install -> Install to Inactive Slot (After OTA)
- After Magisk is done, select reboot
The above method is untested, so make sure you have stock and patched boot.img files for the newest ROM version. Theoretically in the worst case scenario if something goes wrong, all that needs to be done is reflash boot.img via fastboot.
A.17 ROM .ofp file:
RMX3301export_11_A.17_2022062222270183: https://rms01.realme.net/SW/realme service/realme GT2 Pro/216AC/RMX3301export_11_A.17_2022062222270183.7z
Click to expand...
Click to collapse
The most important part is
7b. Run fastboot getvar current-slot .
Replace the "bootXXXmagisk" with a correct filename for patched magisk file
- If it shows boot B partition, run fastboot flash boot_b bootXXXmagisk.img
- If it shows boot A partition, run fastboot flash boot_a bootXXXmagisk.img
Rapper_skull said:
By the way, it's the boot image, not the bootloader.
Click to expand...
Click to collapse
Are you sure this is the real boot.img? All the previous ones were about 190 MB and this one is only 50 MB?
dejop said:
Are you sure this is the real boot.img? All the previous ones were about 190 MB and this one is only 50 MB?
Click to expand...
Click to collapse
The boot partition is not filled to the max of course, so the boot.img extracted from the firmware files is smaller than the partition size (192 MB). In the OTA firmware, the partitions are not filled with empty space like in full firmware files. That's why Full OTA packages are only 5 GB.