Develop Bugs

Problem with dirty flash older version of a custom rom

Hello, a friend of mine installed a custom rom at my lg g3 android phone. The rom is ressurrection remix. I accidently dirty flashed an older version of the same rom, I had 5.1.1 r6 and I flashed 5.0.3, and now neither adb works nor download mode due to killswitch. The only thing it does is show the old rr boot image. It's on a bootloop and since it doesn't open I don't know how to fix it. Can someone tell me what should I do?

Can you use the button combo to boot into TWRP? If you can get into TWRP then just flash the ROM you want and be sure to follow the rom threads instructions before flashing of course.

Can't boot any N 7.1 Rom [Stuck at the rom boot logo]

I can't get my GT-N7100 to boot any Android 7.1 custom rom.
I used to install lots of roms earlier like Android 5,6 custom roms, then I went back to rooted stock again a few months ago.
Recently I tried to install Android 7.1 with the traditional steps: wiping everything (system/data/cache/dalvik/internal storage) then I install the rom and gapps, but I couldn't get any rom to boot. They all stuck on the rom boot logo playing without proceeding to the rom itself. Yet, when I restore my twrp backup of the stock rom it works fine.
I even tried to install android 6 yet it didn't boot as it used to do before, the same logo stuck thing happens without any progress.
Any idea how to fix that ? what could be the reason behind that ?
Should I reinstall a stock rom and re-root it again?
I can't find a good reason for what I have regarding that problem.
I have: GT-N7100 with the following:
OS: wesam.othman ROM 4.4.2 stock rooted rom.
Recovery: twrp 3.0.2
Kernel: AGNi pureSTOCK N7100
Boot loader version: N7100XXUEMJ5
SD Card: 32 GB
I'm using a script that swaps storage so I have nothing on my device internal storage.
Thanks in advance.

Fixed by doing the following:
Installing an original 4.1.2 stock unrooted rom.
re-rooting again using cf auto root.
installing custom recovery
installing a 4.4.2 modem
then finally installing the 7.1 rom

[HELP] Get stuck in bootanimation &then only boot to TWRP after upgrade Magisk & TWRP

[HELP] Get stuck in bootanimation &then only boot to TWRP after upgrade Magisk & TWRP
I have sucessfully rooted my phone but yesterday when i upgraded Magisk from 16.4 to 17.1 and then flashed lasted TWRP, my phone some how corrupted .
After that I tried to flash Factory Image and boot TWRP portable -> Flash ElementalX 2.05 -> Magisk 17.1 -> VerifiedBootSigner-v8 -> Reboot but my phone get stuck in bootanimation about 5 min and then reboot to recovery. Then it will always boot back to recovery when I reboot.
I have searched here but couldn't find any solution.
I tried to flash ElementalX and TWRP only and my phone booting normally. But anytime I flash Magisk it can't.
Please help me, I don't know what to do next, Thank you and sorry for my bad English. :crying:

I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.

Cozmikk said:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Click to expand...
Click to collapse
What version of TWRP did you use?

bricked xiaomi mi a2 lite

installed twrp then tried to install a custom rom crdroid 5.3 I belive encountered error, then tried to install official firmware again got stuck in bootloop with horizontal beam.managed to install twrp again so now how do I install a custom rom or get back to official firmware. I have pcwith adb tools and have twrp installed on my device. think I wiped everything first time installing rom.
how to get my device with a working os and no bootloop?

xdadaizzz said:
installed twrp then tried to install a custom rom crdroid 5.3 I belive encountered error, then tried to install official firmware again got stuck in bootloop with horizontal beam.managed to install twrp again so now how do I install a custom rom or get back to official firmware. I have pcwith adb tools and have twrp installed on my device. think I wiped everything first time installing rom.
how to get my device with a working os and no bootloop?
Click to expand...
Click to collapse
You need stock recovery and bootloader unlock for original rom image flashing, for all other roms, you must follow the instructions without any hickups.

galaxy a70 bootloop after installing custom rom

hi guys
so I tried installing Dot OS V5.1 on my a70q, I flashed vbmeta and then twrp using a guide on XDA and I can boot twrp and install the rom with no errors but after rebooting my phone boots into download mode and the only way I can fix it is by flashing the stock rom using odin
I also tried lineage 18.1 but it has the same problem
(bootloader is unlocked, flashed gapps arm64 android 11 pico version with both roms, I can root my device using twrp and stock rom by flashing magisk with no problems it happens only when I try to install a custom rom)
any help is appreciated