Related
Device cannot boot to recovery or to system but it can boot erecovery and fastboot mode. It has an unlocked bootloader.
I was trying to change my root from SuperSU to Magisk and failed and now leading to this. Please help.
themagicalmage22 said:
Device cannot boot to recovery or to system but it can boot erecovery and fastboot mode. It has an unlocked bootloader.
I was trying to change my root from SuperSU to Magisk and failed and now leading to this. Please help.
Click to expand...
Click to collapse
You need to download your full-ota here http://pro-teammt.ru/firmware-database/?firmware_model=RNE-L22C636&firmware_page=0
and you can update your rom via this link its easy just follow the instruction here https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
flamedrops said:
You need to download your full-ota here http://pro-teammt.ru/firmware-database/?firmware_model=RNE-L22C636&firmware_page=0
and you can update your rom via this link its easy just follow the instruction here https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
I can't access TWRP or regular recovery. All I can access is eRecovery and Fastboot mode.
themagicalmage22 said:
I can't access TWRP or regular recovery. All I can access is eRecovery and Fastboot mode.
Click to expand...
Click to collapse
Did you try this method from another post in this forum ?
Quote:
Originally Posted by mLgz0rn
Don't flash the update.zip through twrp.
You need unzip update.app
Open it with Huawei extractor.
For getting it back to stock
Extract ramdisk.img, kernel.img, system.img, recovery_ramdisk.img.
The in fastboot do.
fastboot flash ramdisk ramdisk.img
fastboot flash recovery_ramdisk recovery_ramdisk.img
fastboot flash kernel kernel.img
fastboot flash system system.img
This will put your phone back to stock, but you will need to install everything from scratch
themagicalmage22 said:
I can't access TWRP or regular recovery. All I can access is eRecovery and Fastboot mode.
Click to expand...
Click to collapse
here you can flash twrp.
fastboot flash recovery_ramdisk TWRP Morfuz.img
download the twrp morfuz below.
Disclaimer :
Code:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Your warranty will be void if you tamper with any part of your device / software.
Download :
RMX2081PU_A33_fastboot [IN]
Fastboot Commands :
Code:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img
Latest Fastboot :
Download
Fastboot Images For Other Realme Devices :
Github
Guide to extract Fastboot images from ozip :
Credits :
jamflux
Regards,
acervenky
FAQs
I'm getting the "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it." Error, what should I do now?
Flash the vbmeta using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I'm getting the "Invalid sparse file format at header magic" Error, does that mean that the images are corrupt?
No! Just ignore the error, if you get the "Finished" message it means that the image has been flashed without any issues.
Can I cross-flash images?(CN -> IN & vice versa)
Some users have reported that the images can't be flashed due to different partition sizes, proceed at your own risk!
Regards,
acervenky
Stuck in boot animation window
Hi Acervenky,
Thanks for posting the fastboot flashable zip. I was able to flash all the partitions as per your post, but when I try to start the device, it keeps boot looping every 10 seconds.
1 - Tried re-enabling verity as I was going back to STOCK, by - "fastboot oem enable_dm_verity", but it said ---- FAILED (remote: 'Unable to open fastboot HAL')
2 - Tried flashing magisk patched boot.img (33 version) posted by another user. Now it does not boot loop but just keeps showing the boot screen for hours.
3 - Please help me revive the device. I am stuck!!!
4 - I cant even push any firmware file to the device for recovery firmware update option as I dont have TWRP installed
I thought I should try reenabling the
acervenky said:
I'm getting the "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it." Error, what should I do now?
Flash the vbmeta using this command :
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I'm getting the "Invalid sparse file format at header magic" Error, does that mean that the images are corrupt?
No! Just ignore the error, if you get the "Finished" message it means that the image has been flashed without any issues.
Can I cross-flash images?(CN -> IN & vice versa)
Some users have reported that the images can't be flashed due to different partition sizes, proceed at your own risk!
Regards,
acervenky
Click to expand...
Click to collapse
cheth20 said:
Hi Acervenky,
Thanks for posting the fastboot flashable zip. I was able to flash all the partitions as per your post, but when I try to start the device, it keeps boot looping every 10 seconds.
1 - Tried re-enabling verity as I was going back to STOCK, by - "fastboot oem enable_dm_verity", but it said ---- FAILED (remote: 'Unable to open fastboot HAL')
2 - Tried flashing magisk patched boot.img (33 version) posted by another user. Now it does not boot loop but just keeps showing the boot screen for hours.
3 - Please help me revive the device. I am stuck!!!
4 - I cant even push any firmware file to the device for recovery firmware update option as I dont have TWRP installed
I thought I should try reenabling the
Click to expand...
Click to collapse
Don't flash patched boot.img, flash the stock one, disable verity and use fastboot erase.
This should fix your issues!
Regards,
acervenky
Hi Venky,
I tried as suggested by you. But it keeps boot looping every 5 seconds. I tried it in the below order -
In fastboot screen
------------------------
fastboot -w
fastboot flash vbmeta vbmeta_patched.img --disable-verity --disable-verification
in Fastbootd screen (fastboot reboot fastboot)
-------------------------
fastboot -w
fastboot erase system
fastboot flash vbmeta vbmeta_patched.img --disable-verity --disable-verification
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot -w
fastboot flash vbmeta vbmeta_patched.img --disable-verity --disable-verification
fastboot reboot
Could it be that I am using the wrong model ROM?
Mine is RMX2085 256gb
Realme X3 Superzoom
model number :RBS0X324IN
acervenky said:
Don't flash patched boot.img, flash the stock one, disable verity and use fastboot erase.
This should fix your issues!
Regards,
acervenky
Click to expand...
Click to collapse
cheth20 said:
Hi Venky,
I tried as suggested by you. But it keeps boot looping every 5 seconds. I tried it in the below order -
In fastboot screen
------------------------
fastboot -w
fastboot flash vbmeta vbmeta_patched.img --disable-verity --disable-verification
in Fastbootd screen (fastboot reboot fastboot)
-------------------------
fastboot -w
fastboot erase system
fastboot flash vbmeta vbmeta_patched.img --disable-verity --disable-verification
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot -w
fastboot flash vbmeta vbmeta_patched.img --disable-verity --disable-verification
fastboot reboot
Could it be that I am using the wrong model ROM?
Mine is RMX2085 256gb
Realme X3 Superzoom
model number :RBS0X324IN
Click to expand...
Click to collapse
Which rom were you on before flashing the GSI?
Regards,
acervenky
Thanks I was able to restore the mobile after flashing the fastboot files.
I am going to try the stereo mod for my phone. Is it possible to add a mod to increase the mic volume and ear piece volume during calls?? This has been an issue since ages and the manual mod is not easy for normal users like us. Please assist!!
acervenky said:
Which rom were you on before flashing the GSI?
Regards,
acervenky
Click to expand...
Click to collapse
I want to flash recovery image
Where I can get recovery.img RMX2081 because I don't get recovery.img in the ozip file
cheth20 said:
Thanks I was able to restore the mobile after flashing the fastboot files.
I am going to try the stereo mod for my phone. Is it possible to add a mod to increase the mic volume and ear piece volume during calls?? This has been an issue since ages and the manual mod is not easy for normal users like us. Please assist!!
Click to expand...
Click to collapse
Yes it is possible to increase the mic & earpiece gains.
Regards,
acervenky
Could you please tell me what values have to be changed to increase the mic and ear piece volume for better sound levels during calls?
acervenky said:
Yes it is possible to increase the mic & earpiece gains.
Regards,
acervenky
Click to expand...
Click to collapse
Hi Acervenky,
My mobile auto updated to version 39. I was trying to install a GSI but it failed to boot.
Now, I am unable to flash the OLD fastboot files successfully.
Coincidentally I had my old ozip file (version 33) in my phone storage. But when I try to install that from the standard recovery, it says that - I am trying to install an old version firmware and then it fails the update process after that message.
I tried extracting the fastboot files for the "new 39 version" OZIP, but when I flash them it does not boot. It keeps going back to boot-loader. Does it mean that my fastboot files are not good? (I tried following your process, but not sure what went wrong)
Can you PLEASE help me with the fastboot files for the latest version 39?
Also as you are an expert, I have the following questions -
1 - HAVOC GSI Rom had installed succesfully, but it had a bug where if I place my phone in DND then it would forever mute my ringtones. So I thought I would flash back to stock and then install the GSI again. Cleared user data and cache using the following commands, full formatted using stock recovery. But somehow even after all this the GSI DND bug was retained in new installs.
Stock sound works fine, but no matter what GSI I install, it all had that bug. Is there any way I can clear all the contents using fastboot as there is no TWRP for this device. Wish we had TWRP but we dont.
fastboot erase cache
fastboot erase userdata
fastboot gsi wipe - did not work. it said I had no GSI install.
2 - Other device users were able to root thier GSI using magisk patch method. But mine never worked except in stock rom and with the magisk patched boot file that was uploaded by Sukhad (https://forum.xda-developers.com/showpost.php?p=83117333&postcount=8). Not sure if the boot file(version 39) that I used for patch was not extracted properly.
3 - One of the installs went wrong and now my phone is bricked. Your previous version helped me unbrick my phone. Could you kindly help me with the latest version fastboot files? (version 39, india)
Device is Realme X3 Superzoom (India )
https://www.realme.com/in/support/software-update
Version 39
acervenky said:
Don't flash patched boot.img, flash the stock one, disable verity and use fastboot erase.
This should fix your issues!
Regards,
acervenky
Click to expand...
Click to collapse
cheth20 said:
Hi Acervenky,
My mobile auto updated to version 39. I was trying to install a GSI but it failed to boot.
Now, I am unable to flash the OLD fastboot files successfully.
Coincidentally I had my old ozip file (version 33) in my phone storage. But when I try to install that from the standard recovery, it says that - I am trying to install an old version firmware and then it fails the update process after that message.
I tried extracting the fastboot files for the "new 39 version" OZIP, but when I flash them it does not boot. It keeps going back to boot-loader. Does it mean that my fastboot files are not good? (I tried following your process, but not sure what went wrong)
Can you PLEASE help me with the fastboot files for the latest version 39?
Also as you are an expert, I have the following questions -
1 - HAVOC GSI Rom had installed succesfully, but it had a bug where if I place my phone in DND then it would forever mute my ringtones. So I thought I would flash back to stock and then install the GSI again. Cleared user data and cache using the following commands, full formatted using stock recovery. But somehow even after all this the GSI DND bug was retained in new installs.
Stock sound works fine, but no matter what GSI I install, it all had that bug. Is there any way I can clear all the contents using fastboot as there is no TWRP for this device. Wish we had TWRP but we dont.
fastboot erase cache
fastboot erase userdata
fastboot gsi wipe - did not work. it said I had no GSI install.
2 - Other device users were able to root thier GSI using magisk patch method. But mine never worked except in stock rom and with the magisk patched boot file that was uploaded by Sukhad (https://forum.xda-developers.com/showpost.php?p=83117333&postcount=8). Not sure if the boot file(version 39) that I used for patch was not extracted properly.
3 - One of the installs went wrong and now my phone is bricked. Your previous version helped me unbrick my phone. Could you kindly help me with the latest version fastboot files? (version 39, india)
Device is Realme X3 Superzoom (India )
https://www.realme.com/in/support/software-update
Version 39
Click to expand...
Click to collapse
One of the users from X50 Pro thread mentioned the use of Realme Flash utility to restore his device to complete factory state, can you check if it is available for your device?
And about your GSI issue, some files stick even if you factory reset; the issues are different according to devices and can carry on to other roms depending on the file in question.
Regards,
acervenky
Unfortunately it did not work when I tried. But your fastboot files helped me unbrick my phone.
Right now, it says that it cannot update and it fails (as I am trying to flash 33 but my system was recently updated to 39).
I am hoping that your fastboot files (version 39) will be able to unbrick as it did earlier...
acervenky said:
One of the users from X50 Pro thread mentioned the use of Realme Flash utility to restore his device to complete factory state, can you check if it is available for your device?
And about your GSI issue, some files stick even if you factory reset; the issues are different according to devices and can carry on to other roms depending on the file in question.
Regards,
acervenky
Click to expand...
Click to collapse
This so called stock ruined my wifi, and I couldn't flash to any stock after that. my solution was gsmmafia, he helped me for only the sum of $23.
I bricked my devise and trying to restore it using fastboot mode, but I am not able to restore System and Vendor Partitions, Plz help me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[email protected] said:
I bricked my devise and trying to restore it using fastboot mode, but I am not able to restore System and Vendor Partitions, Plz help me.
View attachment 5485619
Click to expand...
Click to collapse
I finally flashed stock rom after a hectic working, found an app to convert OFP file to fastboot image files conversion (latest stock rom) and then flashed using fastboot commands. But there is no system & vendor images, instead of these there are userdata and other files, I flashed the same and it's worked for me.
Before unlocking the boot loader or unlocking the phone I was running android 11 with latest FEB 2021 security patch. I successfully unlocked the phone and boot loader using :
fastboot flashing unlock
fastboot flashing unlock_critical
but when trying to temporary boot TWRP image twrp-3.4.0-0-laurel_sprout.img using :
fastboot boot twrp-3.4.0-0-laurel_sprout.img
I get the error FAILED(unkonwn command). Making things worse I ended up ruining the boot partition so if someone can give a guide on how to solve this problem and install TWRP or other recovery or give a the suitable stock or rooted boot image for this particular build so I can revert back my changes without bricking phone due to anti rollback.
koko2010psp said:
but when trying to temporary boot TWRP image twrp-3.4.0-0-laurel_sprout.img using :
fastboot boot twrp-3.4.0-0-laurel_sprout.img
I get the error FAILED(unkonwn command).
Click to expand...
Click to collapse
I have that too on my Xiaomi Mi A2. Sometimes it won't accept bootloader commands. What helped so far is to boot into system or recovery for a minute, or just shuting down the device for a minute and try again.
User699 said:
I have that too on my Xiaomi Mi A2. Sometimes it won't accept bootloader commands. What helped so far is to boot into system or recovery for a minute, or just shuting down the device for a minute and try again.
Click to expand...
Click to collapse
This doesnt seem to help it still displays FAILED (remote: unknown command). I really need some help to get TWRP running if thats hard or will take some time if you can point me to where I can Download latest stock or rooted boot image with FEB 2021 patch so I can install it as I all I can find online are old android 10 and 9 boot images
koko2010psp said:
This doesnt seem to help it still displays FAILED (remote: unknown command). I really need some help to get TWRP running if thats hard or will take some time if you can point me to where I can Download latest stock or rooted boot image with FEB 2021 patch so I can install it as I all I can find online are old android 10 and 9 boot images
Click to expand...
Click to collapse
I don't know where to download these... Maybe you can find some here on xda?
But if booting twrp doesn't work, those images aren't helpfull... (At least on my device it won't accept any input, not even from fastboot flash boot).
Could you check if
Bash:
fastboot getvar all
works?
User699 said:
I don't know where to download these... Maybe you can find some here on xda?
But if booting twrp doesn't work, those images aren't helpfull... (At least on my device it won't accept any input, not even from fastboot flash boot).
Could you check if
Bash:
fastboot getvar all
works?
Click to expand...
Click to collapse
fastboot getvar all does work I installed some image found on XDA and it works except WIFI and phone calls are not working (worthless). anyway getvar all does return that anti=0 and current-slot=b which have installed this boot image. so any ideas what to do.
Okay, since
Code:
fastboot getvar all
works, I actually don't understand why
Code:
fastboot boot twrp
didn't work. Maybe Xiaomis bootloader is buggy.
Since WIFI and phone calls aren't working, you could actually try to install another os to check if it works. If it doesn't, you should look at logcat right after that error happend. Maybe we can find out whats wrong then.
To get the logcat, you can do this in a terminal:
Bash:
adb logcat
and to redirect the logcat into a file you can do
Code:
adb logcat > myLogcatOutput.txt
Hey there,
Gone through every other thread in XDA and most other blogs already. I'm pretty used to rooting and modding android devices, still i somehow find rooting this dirty device harder than I expected.
It's been 2 days now and I could really use some 1-1 help for my case. So, my stock is MIUI Global 11.0.8 Stable 11.0.8.0 PCQINXM, I already unlocked the bootloader and flashed the latest PBRP. On attempting to flash Magisk, I don't find any success regardless of error/ no error messages.
1. I extracted my boot.img with
i) adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
ii) from my ROM via xiaomifirmwareupdater.com repo
2. Used recovery.img that came with olivewood's PBRP.
Patched both of them via Magisk Manager with Recovery Mode checked on.
3. Used vbmeta.img that came with stock ROM.
4. Flashed using fastboot flash boot c:\boot.img
fastboot flash recovery c:\recovery.img
fastboot flash vbmeta c:\vbmeta.img
Still can't seem to complete the root successfully.
What am i doing wrong?
P.S.: I found that flashing a recovery patched this way leads to issues, that I'm stuck in fastboot even if I try to boot to system or PBRP recovery. Flashing the original recovery.img from PBRP repo gets back the recovery menu.
prashanth_ said:
Hey there,
Gone through every other thread in XDA and most other blogs already. I'm pretty used to rooting and modding android devices, still i somehow find rooting this dirty device harder than I expected.
It's been 2 days now and I could really use some 1-1 help for my case. So, my stock is MIUI Global 11.0.8 Stable 11.0.8.0 PCQINXM, I already unlocked the bootloader and flashed the latest PBRP. On attempting to flash Magisk, I don't find any success regardless of error/ no error messages.
1. I extracted my boot.img with
i) adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
ii) from my ROM via xiaomifirmwareupdater.com repo
2. Used recovery.img that came with olivewood's PBRP.
Patched both of them via Magisk Manager with Recovery Mode checked on.
3. Used vbmeta.img that came with stock ROM.
4. Flashed using fastboot flash boot c:\boot.img
fastboot flash recovery c:\recovery.img
fastboot flash vbmeta c:\vbmeta.img
Still can't seem to complete the root successfully.
What am i doing wrong?
P.S.: I found that flashing a recovery patched this way leads to issues, that I'm stuck in fastboot even if I try to boot to system or PBRP recovery. Flashing the original recovery.img from PBRP repo gets back the recovery menu.
Click to expand...
Click to collapse
I have miui 12 how to root?
Ameer9963 said:
I have miui 12 how to root?
Click to expand...
Click to collapse
Which guide have you followed?
prashanth_ said:
Which guide have you followed?
Click to expand...
Click to collapse
I have followed miui 11 guide
But i have miui 12
Ameer9963 said:
I have followed miui 11 guide
But i have miui 12
Click to expand...
Click to collapse
Plz post how to patch boot image
Magist patched boot image not working to root
root: for A.87 stock rom
Unlock bootloader and place the mentioned two files to Platform tools folder on your pc.
Download "vbmeta.img" and "Magisk_patched.img"
• adb devices
• adb reboot bootloader
•fastboot devices
• fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
• fastboot flash boot magisk_patched.img
• fastboot reboot
+++±+++++++
Guide to flash Recovery
- Connect your phone to PC, Allow USB Debugging. Now Type These Commands.
adb reboot bootloader
fastboot devices
fastboot reboot bootloader
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase recovery
fastboot flash recovery recoveryname.img
fastboot reboot recovery
To keep custom recovery flash twrpkeep.zip when's booted to recovery :
Bro my device is a.89 ..is this vbmeta working...?
qeb said:
Bro my device is a.89 ..is this vbmeta working...?
Click to expand...
Click to collapse
Yes it work on all a10 update
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
misiek998 said:
@albatron34000
Please change "fastboot flash bootj magisk_patched.img" for "fastboot flash boot magisk_patched.img" thank you
ALSO
>fastboot erase recovery
>fastboot reboot recovery (?)
Click to expand...
Click to collapse
oh, thank's men. edited.
Hello, Can I use the VBMeta on android 11 or no? thanks!
Ryeeeeel said:
Hello, Can I use the VBMeta on android 11 or no? thanks!
Click to expand...
Click to collapse
Can't root rui 2.0 (Android 11), and can't install custom recovery except "los recovery" but can't do any thing with it just wiping cache and data partition.
do not try to flash custom recovery on realme ui 2.0 , it will brick your device
I need to ask, this guide will work with A88/A89 update?
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
adamuadamu said:
sorry for noob question - I'm not familiar with mediatek devices and rooting/flashing stuff. Currently I'm running crdroid. What steps are neccessary to get rooted stock? is it:
- flash original firmware (how? SPTool?)
- issue all the commands from OP?
Or do I need anything else?
Click to expand...
Click to collapse
Yes. Just flash the original firmware using SP Flash-Tools. However, youmust make sure it is the full 7-8 GB ROM, and not an OTA file. Also, ensure that you are flashing the correct ROM for your model. If your model is an RMX2155, you'll need to follow this guide steps 1-through-to-10 (inclusive):
[GUIDE] REALME 7 RMX2155 GLOBAL BOOTLOADER UNLOCK
WELCOME, ALL. After a very tiring process of swapping between ROMs and changing regions, APKs, et cetera, we have finally been able to perfect the method for unlocking the bootloader of the RMX2155! This is a detailed guide aimed to give you an...
forum.xda-developers.com
If it is any other model, just do what is said to work. Unfortunately, I don't know much about the other versions.
thanks the explanation.
I've found a 2155 ROM or at least a file that's said to be - ie. I've found a file 'RMX2155export_11_C.09_2021070809260000', extracted that, there was a huge file 'RMX2155export_11_C.09_2021070809260000.ofp' inside; using oppo-decrypt from github I've got bunch of files with names that seem to be SPFlashTool ROM.
Assuming it's a proper ROM: if I have already unlocked the bootloader, do I have to flash the rom and do the 10 steps from the tutorial or could I replace recovery.img and magisk-patched boot.img and flash rooted rom immediately? Sorry if it sound noobish, but I don't want to brick the phone.
I'm curious to try to go back to stock ROM for a while, because of call quality (I believe changing it to Vietnam needed for unlock made the call quality worse) and to check the camera and it's libraries - I'm running crdroid, photo quality is disappointing no matter what GCam/settings/tweaks I use and there are only imx682/imx471 libs on the phone there are samsung libs, but diagnose apps like aida show the main sensor is imx682, but the EU version of realme 7 is said to have different back camera sensor (GM1). Not sure if RMX2151 ROMs would include proper GM1 libs if that's true about sensor differences between RMX2151 and 2155.