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
Related
Is anyone experience bootloops on random occasions with android 10 ROMs?
Things work great, played with tons of stuff and when android 10 ROMs appeared I jump to them. With android 9 firmware and android 10 custom ROMs I had no issues except the HEVC issues which were common before they fix this.
So after a while Xiaomi release android 10(miui) and I've put the firmware only and clean flash custom ROMs but after a few weeks I've experience some hard reboots. Random without any reason, bam hard reboot and when it occured it was bootlooping without a stop.
So Xiaomi image(unlocked), rom load and bam again restart, sometimes it booted properly but most of the times the boot loop never stopped UNLESS I force restart faster than the rom logo and enter twrp and shut it off and leave it a few seconds then boot it up ...after that it was working fine until the next boot loop that might occur same day or a few days later
One time it bootloop I enter to twrp fast and it boot looped even in TWRP!!!
This is weird, so let's fastboot the phone and clean everything up. Using Mi flashtool I tried to flash MIUI, after 30+ minutes nothing..it was trying to flash. Oh well. I force restart and enter fastboot and tried again..it finished with error but seemed to flash MIUI properly, clean flash custom ROMs but the issue remains
Anyone have similar experience? After some search some other Xiaomi users have similar issues and use an app called "wakelock" ..I'll see how this goes
P.S. If issue remains I'll fastboot the phone manually(without the mi flashtool), that would be my last resort - Sorry for the long post
P.S.2 usually the bootloop starts when I'm stop using my phone and press the power button to turn off display, it never happened when the phone is on idle
EDIT: Wakelock didn't save anything, got bootloop once again ..tonight I'm gonna try fastboot manual ..hoping for a fix(if it still keeps messing around I'd go back to android 9 where I had no issues at all)
So Xiaomi flash tool failed me if you read my original post, didn't want to risk it again, so I backup up everything and went the old way, it seems the bootloop is fixed, my proximity issues are also fixed(proximity sensor worked on short calls but on long calls the screen remained black - cleaned it as some suggested but the issue was there, now it seems that it's also fixed!!)
So if you have weird behavior just use CMD with fastboot style and write the following(one at a time, or you can create a batch file(bat file) but I strongly recommend that you do it one after another and seek for "success" after each command):
fastboot erase boot
fastboot flash crclist crclist.txt
fastboot flash sparsecrclist sparsecrclist.txt
fastboot flash xbl_ab xbl.img
fastboot flash xbl_config_ab xbl_config.img
fastboot flash abl_ab abl.img
fastboot flash tz_ab tz.img
fastboot flash hyp_ab hyp.img
fastboot flash devcfg_ab devcfg.img
fastboot flash storsec_ab storsec.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib_ab cmnlib.img
fastboot flash cmnlib64_ab cmnlib64.img
fastboot flash modem modem.img
fastboot flash dsp dsp.img
fastboot flash keymaster_ab keymaster.img
fastboot flash logo logo.img
fastboot flash misc misc.img
fastboot flash aop_ab aop.img
fastboot flash qupfw_ab qupfw.img
fastboot flash ImageFv imagefv.elf
fastboot flash vendor vendor.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase sec
fastboot flash cust cust.img
fastboot flash boot boot.img
fastboot reboot
P.S. This WILL ERASE your internal data but won't lock bootloader, so back up your photos and files before
Requirements:
1) ADB Installer v1.4.3 (or any adb installer you prefer)
2) Fastboot MIUI rom, I've use "polaris_global_images_V11.0.4.0.QDGMIXM_20200325.0000.00_10.0_global_82f39e53fd"
Hi, today I experienced unexpected update to Android 10 even I had turned off auto updates and I bricked my phone trying to roll back. So while trying to revive my phone I tested few things and found a way to sort it all out.
Now my phone has TWRP on RAMDISK and no problems with Force Encryption. I didn't tested backup and restore yet so feel free to post results in comments.
1. Install stock ROM, In my case it was 20k, let it fully boot after flash
2. Flash patched boot (for example 20k patched with Magisk 21.1) and boot system to check if you have root:
a. "fastboot flash boot_a magisk_patched.img"
b. "fastboot flash boot_b magisk_patched.img"
3. Boot TWRP G710EM "fastboot boot TWRP_G710EM.img"
4. FORMAT DATA (option where you gonna have to type "YES"), reboot but be careful DO NOT LET SYSTEM BOOT, so keep holding Vol- button while connected to PC and boot TWRP
5. Flash Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip, reboot and once again boot TWRP
6. In Advanced, Flash TWRP to RAMDISK, choose TWRP_G710EM.img and wait until end
7. Reboot. Your phone probably reboots to recovery so in Advanced, Repair Recovery Bootloop
8. Flashing TWRP to RAMDISK can damage Magisk so flash latest zip through TWRP.
9. Done.
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.
Merry Christmas guys,
I have a really unusual situation.
First time that I have tried all tricks I know and I can't get myself out of this difficult situation.
I was trying to update Magisk with a patched boot file and after a reboot I was not being able anymore to access the system but only this black screen with the Crashdump Mode is appearing.
I can access the Fastboot screen, but no way to reboot to the TWRP recovery or to flash another boot.img, even through some pc flashing utilities.
Is there anything to try through another slot or something else?
I also tried:
fastboot flash boot_a boot.img
and I get this error:
FAILED (remote: Flashing is not allowed for Critical Partitions)
But my bootloader is unlocked and other commands like fastboot reboot works normally.
After I flashed through fastboot the images of boot, abl, dtbo, fw I can only access the TWRP recovery where everything is decrypted.
Any other ideas?
Try booting temporary into TWRP by using this command
fastboot boot twrp.img
If you can't use MSMDownloadTool
Installed lineageos19.1 with lineage recovery. Flashed recovery_a with fastboot flash recovery_a twrp-3.5.2_10-kiev.img. All working normally except recovery. Twrp starts but only gets to start screen then shuts down and reboots to lineageos. Also cannot access recover_a to flash anything else. Any ideas on how how to clear and reflash lineageos recovery?
Maybe try:
fastboot boot lineagerecovery.img
once booted (assuming it doesnt reboot as you are experiecing)
abd sideload lineagerecovery.img
reboot