My realme 5 pro bootloops and never boot to recovery, I've flashed
stock .img files (system, vendor, boot, dbto, vbmeta, recovery) from
ROM(RMX1971EX_11_OTA_1080_all_29hQ1fOMjgyl) (C.08 RUI 1.0) and various custom recoveries(TWRP-OrangeFox) using fastboot mode but nothing.
Also it was booting into fastboot directly nothing else, but after erasing system partitions
(system, boot, vendor, recovery, dbto, cache, userdata)
via fastboot commends then flashing them using C.08 ROM files and disabling verification,
it began to bootloop on "powered by android" screen after it was booting into fastboot only so i think it's good step forward, but i need some help to know what should i do next.
What happended exactly ?
Well, yesterday i had an OTA update for android 11 RUI 2.0, after update done and system boot up, it began flashing the lock screen then a black screen; so i used commend
Code:
fastboot erase userdata
after that i couldn't go recovery mode again.
Related
I wanted to upgrade my LineageOS version, so:
I wiped all the partitions I could wipe (from TWRP)
I rebooted to recovery, but I got a CrashDump error
I tried "fastboot boot" the latest official twrp img, and the bluespark one, but same error.
I also tried this https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but it wasn't of help.
What do I have to do?
Both system and recovery mode leads to a CrashDump mode
Solved! I did this https://www.getdroidtips.com/unbrick-oneplus-6/ and worked!
If you can boot into fastboot, you could just flash fastboot images with flashall.bat script
I have wiped system partition and dalvik cache without flashing recovery and rebooted it, now I'm stuck on fastboot mode, anyway to boot back normally, without losing data? I'm unable to boot into twrp through fastboot, it says that couldnt authenticate boot image
Try switching the recovery partition, then try to boot the recovery img again.
fastboot --set-active=b
fastboot boot path/to/your/recovery.img
I been trying to flash some system images I find on the treble forum and nothing is flashing.
My bootloader is unlocked and I'm rooted with magisk
Whenever I run "fastboot erase system" I get a permission denied error and doing "fastboot format system" I get an error about a raw filesystem
Trying to flash an image without wiping I get an error about resizing the system partition.
Am I doing something wrong? It's been years since I've tinkered with Android so I'm out of the loop on Android's dynamic partitioning etc etc
Edit: Figured it out
https://forum.xda-developers.com/mo...de-how-to-flash-generic-image-moto-g-t4131199
for anyone wondering, i just figured it out, the moto g stylus has 2 fastboot modes? one is the bootloader (adb reboot bootloader) and the other is fastbootd (adb reboot fastboot)
booting into fastbootd solved my flashing and wiping issues
Yes. The Android 10 has a new fastbootd mode.
You can enter it with a command
Code:
adb reboot fastboot
You can try to install the Treble image through it. Because in Android 10 there is a new physical partition super.img, which contains three logical partitions - vendor.img, system.img and product.img.
ilia3367 said:
Yes. The Android 10 has a new fastbootd mode.
You can enter it with a command
You can try to install the Treble image through it. Because in Android 10 there is a new physical partition super.img, which contains three logical partitions - vendor.img, system.img and product.img.
Click to expand...
Click to collapse
Yeah I just figured this out although I'm still having issues flashing any gsi ROM, nothing boots after a factory reset, even if I just flash a boot.img patched by magisk with dm verity and encryption disabled
DMedina559 said:
Yeah I just figured this out although I'm still having issues flashing any gsi ROM, nothing boots after a factory reset, even if I just flash a boot.img patched by magisk with dm verity and encryption disabled
Click to expand...
Click to collapse
Same boat. Bootloop if I try to get it to start unencrypted. Booting at least once into a clean boot, then flashing without formatting first let me patch magisk. Have a suspicion the phone isn't too happy about being unecrypted.
Hi, I am running the latest MIUI on my redmi note 7 pro. I unlocked the bootloader and tried to flash both orange fox and twrp recoveries. The flashing process completes fine but when I try to boot the device to recovery mode or system it says this device has been destroyed. I tried to boot into recovery using fastboot boot recovery_name.img but that doesn't work either. Please help.
check out Technobuzznet's video on Youtube regarding system has been destroyed. I had followed his steps and came out of it victorious.
You should flash stock ROM using Mi flash first then flash a custom recovery you want and afterwards flash vbmeta file.
I would recommend to connect device to fastboot mode first and then flash the vbmeta file using command fastboot flash vbmeta vbmetafile, then try to reboot to recovery, if this doesn't help then you can try the flashing method mentioned above.
Here is how I fixed it.
1. Flashed the vbmeta.img from pixel experience plus rom zip by
fastboot flash vbmeta vbmeta.img
2. Rebooted into fastboot mode again and flashed latest orangefox.img
3. Booted into orangefox deleted system, dalvik, cache,
4. Formatted data partition (cause it was encrypted)
5. Flashed PE plus rom.
I flashed custom rom and Magisk on my realme 5 pro, I did all the procedures right, wipe, flash rom, magisk, clear data, and reboot to the system, but after I reboot to the system I got bootloop. Recovery is not working but the fast boot is working, but when I connect my cable fast boot logo appears and I get stuck in the logo with a press any key to shutdown st the top and then the cable connection disconnects. I'm using a phone and bugjaeger app to install recovery and adb sideload.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.bin