can't flash custom roms - Nexus 5X Q&A, Help & Troubleshooting

hey there, i just bought nexus 5x and it was updated to latest official android 8.0, now i want to flash custom roms, steps i made: unlocked bootloader, flashed twrp, disabled forced encryption and dm-verity (found somewhere boot.img on xda which disables that), now i downloaded custom rom(tried crdroid and dirty unicorns both 7.1 android) and , gapps arm64 7.1, and latest supersu. flashed these files whith that order and got stuck at google splash logo. not even boot animation is played. tried without and with supersu, and custom kernels. still no luck. official google system boots fine though. so, hope you help me guys

You can't flash 7.1 ROMs over 8.0 partitions and vice versa.
If you want to flash 8.0 ROMs, flash the stock OPR6 images FIRST. If you want to flash <7.1.2 ROMs, flash the latest N factory images.

For me, it was enough to flash the Vendor Image other than the newest one... (or maybe the newest 2, I tried the July one)

Related

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.

Bootloader loop when installing lineage

Hello,
After mucking with custom roms for the day, i've now found myself only able to boot into bootloader or recovery when using lineage. When turning the phone on, it'll instantly put me at the bootloader.
The stock rom flashes fine, as does crDroid, however despite using lineage for the past few months, I'm now unable to boot into system after re-flashing it. The only thing I can think off that I've done differently is that of trying out lineage's oreo version. Though I'm having this issue trying to flash nougat.
There's no error that I've seen from twrp during flashing, and nothing occurred out of the ordinary.
Presumably trying "oreo" you used 8.0 gapps you need 7.1 gapps for nougat
robin0800 said:
Presumably trying "oreo" you used 8.0 gapps you need 7.1 gapps for nougat
Click to expand...
Click to collapse
When trying out Oreo, I used the official gapps rather than the unofficial open-gapps linked in the thread. This would have been "Arm64 8.0 Micro", however the one provided is 'unofficial'.
I did this as androidfilehost was trying to download at 40kbps at the time.
For flashing nougat I'd have used OpenGapps's Arm64 mini 7.1. I had the same issue with BeansGapps as well.

Moto G5 encryption

I have a G5 Cedric XT1671 DUALSIM that comes by default encrypted and when flashing some custom ROM with Oreo the encryption prevents me from accessing the system. I have searched in xda but the only that I found doesn't work, I formatted the cell phone from scratch, flashed the stock and tried to flash from a custom 7.1.2 to go to 8 and I could not. Does anyone know how I could remove the encryption?
Currently I have Viper OS 7.1.2
Flash stock firmware and then twrp, after that install this via twrp: https://androidfilehost.com/?fid=673368273298927206, then reboot the device and flash your custom rom.
REMEMBER; If you are flashing android 8.1, you must have a 64bit enabled twrp installed rather than the regular one, this does not apply to 8.0.
It happens to me that I think the same thing, flash stock, then installs the recovery, and when you get it you ask for the encryption key, cancel it, then do a full wipe and install the 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?

Can't boot any GSI, always resulting in a bootloop

Hello,
I'd like to use an AOSP ROM on my S9 Exynos (only because of personal preferences), the only problem is that I couldn't boot a single GSI on my device even though it is Treble compatible. I tried multiple versions of Phh-Treble 9.0 and Resurrection Remix 7, flashed them via TWRP over stock ROM and it never went further than the booting screen of the specific ROM. What am I doing wrong?
I would be so glad if someone could help, thanks in advance.
First you have to flash a vendor , like BRK3 then flash the rom and gapps if needed , and sometimes you have to flash a kernel
where to find vendor file?

Categories

Resources