Hello!, does anyone have a stock recovery.img file for rmx2103 i flash the wrong recovery and now it's not booting anymore.
Soe1652000(MM) said:
Hello!, does anyone have a stock recovery.img file for rmx2103 i flash the wrong recovery and now it's not booting anymore.
Click to expand...
Click to collapse
Did you got it?
Related
I wanted to go back to stock recovery from TWRP.
Now the confusion is i dont have the latest recovery.img file to flash.
I have 32bit version.
I have downloaded fastboot CM12.1 YOG4PAS3JM zip file and I have recovery.img file in it.
Can I use it flash to get back on stock recovery?
Is it the latest stock recovery file?
Hi all, i have problem to boot my ze553kl, can someone post here stock recovery.img and boot.img newest oreo firmware WW-80.30.76.10?
Many thanks
Ciao
Here you go
https://drive.google.com/open?id=1vz_OG7QICx9qemF-5MjbcroXhD5cYD4z
boot.img already have recovery so no need to flash recovery.img separately.
Thanks!
Ciao
How do I extract the recovery.img from a downloaded asus firmware file?
I downloaded the WW-15.0200.1808.418 firmware for my Asus Zenfone 3 Max ZC553KL and I don't know what to do.
If possible, maybe someone can share me the recovery.img for that phone (ZC553KL) version WW-15.0200.1808.418, it would be greatly appreciated.
I was in your position.
What i did was
I followed this steps to install TWRP
Download TWRP Tutorial Guide Step By Step
After that i flash the boot & recovery files from 418 firmware
WW-15.0200.1808.418 Stock Boot & Recovery IMG
Boot to TWRP
Install
Select Image
Boot select the boot.img
Recovery select the recovery.img
Click to expand...
Click to collapse
In TWRP reboot to recovery u will now enter stock Recovery
Flash your 418 firmware.
Or you can Flash using Fastboot commands
fastboot flash boot boot.img
Click to expand...
Click to collapse
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I place the 418 Firmware in my Sd card
Apply update from SD card.
Just in case you need 418 firmware for ZC533KL
It's WW-15.0200.1808.418
When all is done. I reinstall the TWRP
Flash latest Magisk 1.8.0
Happy me.
every time I do the procedure to install the gcam with temporary root, when uninstalling the magisk, my mi a1 gets stuck in the "no command" screen, I saw in several sites that this happens when the magisk does not make a backup correct boot.img, has anyone gone through this?
die.henrique said:
every time I do the procedure to install the gcam with temporary root, when uninstalling the magisk, my mi a1 gets stuck in the "no command" screen, I saw in several sites that this happens when the magisk does not make a backup correct boot.img, has anyone gone through this?
Click to expand...
Click to collapse
Mine too, had to flash the original rom with mi flash. Get the og boot.img then when you're in fastboot mode type : "fastboot boot boot.img" the boot.img needs to be the stock unpatched boot image
emiljano539 said:
Mine too, had to flash the original rom with mi flash. Get the og boot.img then when you're in fastboot mode type : "fastboot boot boot.img" the boot.img needs to be the stock unpatched boot image
Click to expand...
Click to collapse
but will not this reset the device? can I flash the stock boot.img without erasing the data?
die.henrique said:
but will not this reset the device? can I flash the stock boot.img without erasing the data?
Click to expand...
Click to collapse
Yes, but you can keep the data by selecting to flash only the system.
And you can also flash only the stock boot.img with command "fastboot flash boot boot.img"
emiljano539 said:
Yes, but you can keep the data by selecting to flash only the system.
And you can also flash only the stock boot.img with command "fastboot flash boot boot.img"
Click to expand...
Click to collapse
Omg, thanks for the answers, just one more thing, the boot.img do I have to download from the internet or do a backup of my current device?
die.henrique said:
Omg, thanks for the answers, just one more thing, the boot.img do I have to download from the internet or do a backup of my current device?
Click to expand...
Click to collapse
You should download the boot.img for mi a1 which corresponds with your update. For ex. boot.img of january rom.
device not found in adb fasboot after uninstall magisk
emiljano539 said:
Mine too, had to flash the original rom with mi flash. Get the og boot.img then when you're in fastboot mode type : "fastboot boot boot.img" the boot.img needs to be the stock unpatched boot image
Click to expand...
Click to collapse
[HELP] after uninstalling magisk, my mi a2 stuck at no command and does not found in adb (device not listed in fastboot). what should i do? i want to flashboot.
caan90 said:
[HELP] after uninstalling magisk, my mi a2 stuck at no command and does not found in adb (device not listed in fastboot). what should i do? i want to flashboot.
Click to expand...
Click to collapse
Because you have lost the stock boot.img. find the stock boot img of your patch then flash it via fastboot directly
emiljano539 said:
Because you have lost the stock boot.img. find the stock boot img of your patch then flash it via fastboot directly
Click to expand...
Click to collapse
Thank you so much... it work.. my mi a2 just come back to life..
caan90 said:
Thank you so much... it work.. my mi a2 just come back to life..
Click to expand...
Click to collapse
I'm glad it worked. Make sure you leave a like in my comment if it was useful . Peace
my mi a2 is not detect in adb and in fastboot too what can i do
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
LinhBT said:
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
Click to expand...
Click to collapse
Can you share your file?
Rootk1t said:
Can you share your file?
Click to expand...
Click to collapse
Sure man, find attachment
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
houstontaxi said:
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
Click to expand...
Click to collapse
unpack your firmware, extract stock recovery.img and flash it.
But for flashing do I need to unlock bootloader or it can be done without unlocking?
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Rootk1t said:
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Click to expand...
Click to collapse
If it needs to flash recovery the same way as we do for custom roms like fastboot flash recovery in platform tools then i tried that doesn't work to make it work bootloader needs to be unlocked I did that(unlocked the boot loader) then flashed stock recovery and it worked but after locking the boot loader with fastboot oem lock same issue happened again couldn't boot into recovery.
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
LinhBT said:
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
Click to expand...
Click to collapse
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
houstontaxi said:
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
Click to expand...
Click to collapse
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
I'm gonna try that thanks for the help and I hope it resolves my issue with OOS A12 recovery as I don't face this kind of issue on OOS11
1
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
lenox30 said:
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
Click to expand...
Click to collapse
This is simply Stock Recovery with ADB enabled bro. It only can help u in some tasks which need to access adb via Recovery, it won't help to decrypt ur device and/or have any functions as other custom recovery