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
.
Related
Hi
I'm trying to flash the factory image recently posted but getting the following error:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814213396 bytes
error: update package missing system.img
Looks like the Nexus 9 doesn't have enough allocated space to take the 820+MB zip file that contains the system images. I've updated to the latest version of SDK tools and have the newest Fastboot EXE, and device state is saying UNLOCKED on the HTC Fastboot screen.
Anyone have any ideas?
Regards
Phil
PhilipL said:
Hi
I'm trying to flash the factory image recently posted but getting the following error:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814213396 bytes
error: update package missing system.img
Looks like the Nexus 9 doesn't have enough allocated space to take the 820+MB zip file that contains the system images. I've updated to the latest version of SDK tools and have the newest Fastboot EXE, and device state is saying UNLOCKED on the HTC Fastboot screen.
Anyone have any ideas?
Regards
Phil
Click to expand...
Click to collapse
I would trying to flash each image in factory image individually (Flash bootloader, flash boot, flash recovery, etc.), flashing them in the order the flash-all script would flash them (If your not sure which order it would flash them in just open the flash-all.bat or flash-all.sh as a text file and look at the order they are flashed in).
PhilipL said:
Hi
I'm trying to flash the factory image recently posted but getting the following error:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814213396 bytes
error: update package missing system.img
Looks like the Nexus 9 doesn't have enough allocated space to take the 820+MB zip file that contains the system images. I've updated to the latest version of SDK tools and have the newest Fastboot EXE, and device state is saying UNLOCKED on the HTC Fastboot screen.
Anyone have any ideas?
Regards
Phil
Click to expand...
Click to collapse
The missing.sig errors are normal. The missing system.img is not. Try downloading the factory image again.
Sent from my Nexus 5 using XDA Free mobile app
Same here, get the same error when trying to flash factory image. I did flash the files individually, but wasn't sure how to flash the vendor.img?
any update on this?
what do we do with vendor.img?
mingiunate said:
any update on this?
what do we do with vendor.img?
Click to expand...
Click to collapse
Just an update - based on the size of vendor.img, I assumed it was the same as userdata.
here are the steps i took to manually flash:
unzip image-volantis-lrx21l.zip
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash userdata vendor.img
from tablet - select hboot
select factory reset
Done!
Hm, I successfully flashed vendor.img using
Code:
fastboot flash vendor vendor.img
But I'm not sure whether that was the correct way to go about things.
Hi
Thanks everyone for the replies/responses.
I will try and flash each image separately, however this shouldn't be necessary and means the image (or some setting on the Nexus 9) is wrong or broken. The whole point of the factory image is that it flashes with ease to get us back to a clean slate (well tablet), so a bit worrying they've not seemingly tested it too well.
Note I've flashed factory images dozens of times to Nexus 4, 5, 7 (both years) and never had this problem.
Perhaps Google will post a fix soon.
Best Regards
Phil
I think you need to run these two commands before you flash the rest of the .img files?
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
ilatimer1 said:
I think you need to run these two commands before you flash the rest of the .img files?
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
here are the steps i took to manually flash:
run the flash-all.bat up until the point where it fails
unzip image-volantis-lrx21l.zip
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash userdata vendor.img - looks like userdata should be vendor? - mine worked with userdata regardless
from tablet - select hboot
select factory reset
Done!
Hi
ilatimer1 said:
I think you need to run these two commands before you flash the rest of the .img files?
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
I did this as the first step as that is what is in the batch file with all/most Nexus factory images, didn't make a difference though. Something is definitely broken somewhere. However installing the images separately seems to work.
Best Regards
Phil
When was the last time you updated your SDK? Try downloading the latest SDK and run the flash-all
Hi
cundiffr said:
When was the last time you updated your SDK? Try downloading the latest SDK and run the flash-all
Click to expand...
Click to collapse
As I mentioned in the first post, after the first failure I updated my SDK to the very latest version, the result was the same. The image doesn't flash unless you separate out the individual parts and do it separately. Either the Nexus 9 isn't configured to allow enough space to accept the entire image (which clearly Google think it should as that is how they instruct it to be installed), or the image is broken in some way.
I'm sure it will get fixed at some point.
Regards
Phil
The same thing happened to my while I tried to flashed the newly released lollipop image to my nexus 5. I only had to restart my laptop and it worked.
mingiunate said:
[*]fastboot flash userdata vendor.img - looks like userdata should be vendor? - mine worked with userdata regardless
Click to expand...
Click to collapse
Yep, vendor should be flashed to the "vendor" partition.
userdata is emptied during factory reset.
Are you sure the prollem is with the tablet? When running a full ruu on other HTC devices, the failure to allocate space prollem arises from not having enough ram on the pc. Could be why flashing the images separately is working.
scotty1223 said:
Are you sure the prollem is with the tablet? When running a full ruu on other HTC devices, the failure to allocate space prollem arises from not having enough ram on the pc. Could be why flashing the images separately is working.
Click to expand...
Click to collapse
It's the image or tablet that's at fault. I ran the flashing process on a high-end machine equipped with 32 GB of RAM.
Restart your computer!
I sat here forever trying to figure why the hell i couldn't get 5.0 to flash to my nexus 5. I looked everywhere and didn't find anything that helped at all. I restarted my computer and tried again and it worked instantly. The first thing i said to myself was are you ****ing kidding me.... my computer was the issue. Dont tell yourself bull**** about how your computer is the bees knees. Mine may only have 16 gb of ram but restarting it worked perfectly.
Do i make a fullwipe, befor i flash the Image Files, if yes how i do this.
format system
format data
format cache
????????
fastboot flash userdata vender.img actually worked for me
Problem already solved. Thanks!
Hi everyone, this is Sarry. I got my new huawei mate 9 pro on Wednesday this week, the version is LON-L29C636, I was trying to flash a custom ROM into the phone, but unfortunately I was too careless, flashed a different version ROM into it and cause immediate start up loop. As I finally boot into fastboot and twrp rec mode, I noticed that the computer won't recognize the USB portal of the device. So I went in eRecovery mode and tried to download an updated version but it failed to find any useful version.
Since mate 9 pro doesn't support SD card, I brought a USB-OTG cable and also usb type-c microSD adapter, when I connected the sd card to the phone, twrp reads the information, but when I tried to flash the update.zip file, it failed. I tried to copy the dload folder with update.app by twrp into phone storage, even if I got successful, the file just disappeared when i refresh the page. So now I don't have any idea on how to unbrick the phone, felt really bad.
Feel free to ask me any question or information needed, I really hope to unbrick the phone, I've been using huawei cellphone for more then 2 years and love it very much. Thanks for the help!!
Hello,
well the situation isn't that hard actually, you may just get the stock image and flash it from fastboot then start the custom rom installation from scratch.
what is the error number or statement?
EDIT: you will need huawei update extractor to pull out the img files and flash them through fastboot
Another Edit:
in the file path choose the update.app
you will need the following partitions:
Boot
System
Recovery
^select these then right click and press `extract selected` and flash them using the following commands:
1- fastboot devices > to check the device
2- fastboot flash boot boot.img
3- fastboot flash recovery recovery.img
4- fastboot flash system system.img
hope this helps you
good luck!
TheShadowMC said:
Hello,
well the situation isn't that hard actually, you may just get the stock image and flash it from fastboot then start the custom rom installation from scratch.
what is the error number or statement?
EDIT: you will need huawei update extractor to pull out the img files and flash them through fastboot
Another Edit:
in the file path choose the update.app
you will need the following partitions:
Boot
System
Recovery
^select these then right click and press `extract selected` and flash them using the following commands:
1- fastboot devices > to check the device
2- fastboot flash boot boot.img
3- fastboot flash recovery recovery.img
4- fastboot flash system system.img
hope this helps you
good luck!
Click to expand...
Click to collapse
Thank you so much for the help! The fastboot script isn't really working because when I tried to run it in cmd, it shows 'error can't find device', so I tried to flash the img files with twrp, the boot.img and recovery.img works well, but the system.img cannot be flashed, and the error message shows 'E:\cannot flash system.img'. I also tried to download the full version firmware and created dload folder in my SD card, copied UPDATE.APP into the folder, tried the 3 button force update, still nothing worked. Now the seller send me an Email said I can return the product, they are going to charge me for some ROM re installation fee.
However what error does it give during flashing system.IMG I would like to know, also as well as twrp custom ROM flashing?
Aquarius_2333 said:
Thank you so much for the help! The fastboot script isn't really working because when I tried to run it in cmd, it shows 'error can't find device', so I tried to flash the img files with twrp, the boot.img and recovery.img works well, but the system.img cannot be flashed, and the error message shows 'E:\cannot flash system.img'. I also tried to download the full version firmware and created dload folder in my SD card, copied UPDATE.APP into the folder, tried the 3 button force update, still nothing worked. Now the seller send me an Email said I can return the product, they are going to charge me for some ROM re installation fee.
Click to expand...
Click to collapse
well brother about the driver issue, sorry about being late, you must have downloaded the fastboot drivers and installed them.
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...
I'm searching for the P20 Lite ANE-LX1-C432 Stock Firmware update.app or the stock/matching system.img file.
I cannot find it on google maybe huawei did not release it yet so i wonder if one of you guys did dump it
Thank you.
EDIT:
I found a full firmware here for ANE-LX1 :
Stock Firmware C185 (Middle East) [url]https://www.allrom.ir/2018/04/01/رام-فارسی-اندروید-8-0-هوآوی-پی-20-لایت-ane-l21-l01/[/URL]
I extracted the stock system.img ANE-LX1 from the update.app
I just flashed it everything works. system.img :
https://drive.google.com/open?id=1cbfdA9GaOQAKMWM0sFBPZh28q-Klmyvc
Without root we can't dump anything, still working on it. For now, there's nothing
RogerXIII said:
Without root we can't dump anything, still working on it. For now, there's nothing
Click to expand...
Click to collapse
Yes i tried to dump files with adb or fastboot but was not successful and now my device is too modified to try again.
Gonna wait for Huawei to post the firmware...
EDIT:
Look at the first post for links ! thx.
I found a full firmware here:
https://www.allrom.ir/2018/04/01/رام-فارسی-اندروید-8-0-هوآوی-پی-20-لایت-ane-l21-l01/
This one is C185 (Middle East)
Edit: Now i need to create a P20 Lite Profile for the Huawei Extractor. :crying:
Edit 2: i was able to extract the system.img from the update.app, now trying it.
Edit 3: I now have a Stock system.img ANE-LX1
I just flashed it everything works.
I will post it if you need it like me after trying some treble roms :angel:
Thanks, got system.img from this with no problem, but it looks like there's no boot.img in here, so still no chance for root
RogerXIII said:
Thanks, got system.img from this with no problem, but it looks like there's no boot.img in here, so still no chance for root
Click to expand...
Click to collapse
In the OREO boot & recovery partitions got a different names.
RECOVERY is now split in several partitions:
RECOVERY_RAMDISK
RECOVERY_VENDOR
RECOVERY_VBMETA
In the Oreo the command to flash a TWRP (that is not available yet) in the fastboot mode is:
fastboot flash recovery_ramdisk twrp.img
___
BOOT is now split in two partitions:
KERNEL
RAMDISK
In the Oreo the command to flash "KERNEL" in the fastboot mode is:
fastboot flash kernel kernel.img
kilroystyx said:
In the OREO boot & recovery partitions got a different names.
RECOVERY is now split in several partitions:
RECOVERY_KERNEL
RECOVERY_RAMDISK
RECOVERY_VENDOR
RECOVERY_VBMETA
In the Oreo the command to flash a TWRP (that is not available yet) in the fastboot mode is:
fastboot flash recovery_ramdisk twrp.img
___
BOOT is now split in two partitions:
KERNEL
RAMDISK
In the Oreo the command to flash "KERNEL" in the fastboot mode is:
fastboot flash kernel kernel.img
Click to expand...
Click to collapse
Thanks for this information! Patching boot.img to get root that way is not possible then I assume?
By flashing the Mate 10 Pro recovery, you can dump your boot.img with adb in recovery using dd command. I just tried dumping some partitions of my P20 Lite, everything works fine, but I already flashed a wrong boot partition so I cant provide the stock boot.img file.
EDIT : the recovery doesn't work at all, please do nothing else except dumping partitions, or you may brick your phone
Never mind! I managed to root by patching the ramdisk.img
RogerXIII said:
Never mind! I managed to root by patching the ramdisk.img
Click to expand...
Click to collapse
Can you pleeease give me a dump of your boot partition? I failed flashing the partition and without any boot.img file I'm totally lost :')
Jb-kun said:
Can you pleeease give me a dump of your boot partition? I failed flashing the partition and without any boot.img file I'm totally lost :')
Click to expand...
Click to collapse
I made a thread here, you can root or go back to stock there
Boas kilroystyx comprei um ANE-LX1 P20 Lite da vdf. Isto está com apenas single SIM. Sabes se mudar a ROM liberta a segunda SLOT? ainda não há firmware para isto pois não?
Obrigado,
MC
GV
kilroystyx said:
In the OREO boot & recovery partitions got a different names.
RECOVERY is now split in several partitions:
RECOVERY_KERNEL
RECOVERY_RAMDISK
RECOVERY_VENDOR
RECOVERY_VBMETA
In the Oreo the command to flash a TWRP (that is not available yet) in the fastboot mode is:
fastboot flash recovery_ramdisk twrp.img
___
BOOT is now split in two partitions:
KERNEL
RAMDISK
In the Oreo the command to flash "KERNEL" in the fastboot mode is:
fastboot flash kernel kernel.img
Click to expand...
Click to collapse
@ggviegas, xda is an international forum, so please write in English, or PM me.
RogerXIII said:
Thanks, got system.img from this with no problem, but it looks like there's no boot.img in here, so still no chance for root
Click to expand...
Click to collapse
I was too lazy to dump the other partitions because had to create a huawei extractor profile for the device, and there is a lot of partitions on the P20 Lite.
I am a complete noob. Brought the Chinese version with HiApp and all - don't know how to get it to the Middle East version. Can someone share the instruction that a 3-year-old can understand???
Thanks
I flashed system in fastboot. My device is Huawei Nova 3e (P20 Lite in china) everything works kinda nicely but notch settings in the display settings are disappeared. Notch is not working properly. Other than that, everything is alright. I need help to fix that notch settings. Can somebody help me?
Is the Android Auto working properly on this version? I see its the 105 and not the 108.
thelonelyman said:
I flashed system in fastboot. My device is Huawei Nova 3e (P20 Lite in china) everything works kinda nicely but notch settings in the display settings are disappeared. Notch is not working properly. Other than that, everything is alright. I need help to fix that notch settings. Can somebody help me?
Click to expand...
Click to collapse
Try to update the software as the notch options were added recently.
Hi there. I downloaded the Firmware and flashed the system.img but still my phone shows the 112 version. How is this possible?
When i flashed all img (all recovery, ramdisk, kernel, system) i got into a bootloop.
So i replaced them with the old ones. But still the system img was from the downloaded package.
What am i doing wrong? i can flash every system.img file but my version wont change.
I did a Full wipe aswell.
kilroystyx said:
In the OREO boot & recovery partitions got a different names.
RECOVERY is now split in several partitions:
RECOVERY_RAMDISK
RECOVERY_VENDOR
RECOVERY_VBMETA
In the Oreo the command to flash a TWRP (that is not available yet) in the fastboot mode is:
fastboot flash recovery_ramdisk twrp.img
___
Click to expand...
Click to collapse
so, using fastboot flash recovery_ramdisk recovery_ramdisk.img would be the proper way to go back to stock recovery?
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