Hi, I recently flashed an official CyanogenMod 14.1 Nightly. Shortly after that, TWRP Recovery was wiped from my phone (I would boot into recovery mode, the OnePlus logo would be visible for a while and the the screen would go black). I re-flashed TWRP again and then the stock Oxygen Recovery but the same kept happening. I eventually got into a bootloop trying to root my phone so I could use flashfire, so I tried flashing CyanogenMod Recovery. This one booted up perfectly, so I wiped system, data and ADB sideloaded Oxygen OS. I got an error, so I flashed an unofficial nightly via ADB sideload and booted to the system. I tried flashing TWRP again but the same keeps happening. Apparently CyanogenMod doesn't want you using anything other than Cyanogenmod.
Please Help!
UPDATE: I was able to ADB sideload Resurrection Remix (Nougat), but still can't flash TWRP (or any other recovery, or Oxygen OS)
I'm having issues with LineageOS based roms. Basically, ever since 4.1.0 was released, I haven't been able to boot anything other than OxygenOS.
The first time I flashed the 4.1.0 firmware, my OnePlus 3 bricked. I then used the unbrick tool to fix it. I then tried again, by flashing the 4.1.0 firmware, then flashing the latest LineageOS "lineage-14.1-20170316-nightly-oneplus3-signed.zip". Upon reboot, the phone stays stuck at the lineageos boot animation. I can't get any logcats (adb logcat doesn't seem to work).
Things I've tried so far:
- Using TWRP 3.0.4-1
- Using TWRP 3.1.0-0
- Dirty flash
- Clean flash
- Data as both f2fs and ext4, neither works
- Tried using TWRP's "Fix Contents"
- Tried using TWRP's filesystem repair, no problems with the filesystem
I'm at a loss, no idea what to do. I really want to get back to LineageOS, but ever since that original brick, the phone hasn't been able to boot anything other than the stock ROM.
do you try download again that rom?
i had some problems with AICP, flashing last firmware+modem was solved
you can try using other base, like 4.02, or freedomOS OB12
just ideas, I don't know what's the problem :/
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
vasu1312 said:
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
Click to expand...
Click to collapse
I don't think I screwed up anything. I had flashed multiple roms before. (LineageOS, ResurrectionRemix, AICP, FreedomOS...)
All of them worked, up until recently. When the 4.1.0 update came out, LineageOS Roms stopped booting. OxygenOS ROMS still work fine though. Flashing the OB12 firmware doesn't help.
This is the first time this has happened, I have no idea why its happening.
Do you flash SuperSU, without SuperSU mine boots fine. Without i m stuck in boot
Tried flashing SuperSU, but nothing has changed. Android still won't boot up if it is a LineageOS based ROM
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
indroider said:
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
Click to expand...
Click to collapse
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Now, not even Android 6.0 ROMS will boot. I think some partitions are corrupted, but I'm unable to wipe them in fastboot mode.
Edit: So, finally, after 3 days, I was able to get in contact with OnePlus. OnePlus fixed the problem with the Qualcomm Tools, not entirely sure what they did, but it fixed the problem. I'm finally able to boot LineageOS!!!!
AquaBytez said:
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Click to expand...
Click to collapse
how much time do you wait because first boot does take 5 or more minutes
indroider said:
how much time do you wait because first boot does take 5 or more minutes
Click to expand...
Click to collapse
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
AquaBytez said:
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
Click to expand...
Click to collapse
perfect... that is what i was trying ro instruct you reflasing the stock but somehow ,,, it was not able to be done throught stock oxygen recovery... from ur end
nevertheless happy ur device is working fine now
hi i bought op5t few days ago.
and now i have serious problem.
i flashed the5tos. and custom kernel
but my phone booted on recovery.
can't boot 5tos rom.
only can boot official oos rom.
and after rom flashing twrp always has problem
'failed to mount cache (no such file or directory)
and i flashed noverity op5.zip and no_verity_op5_v2.zip too
it can't boot. boot on recovery mode again
can you solve this critical problem?
and i use official twrp 3.2.1-2
I have been having the same problem. I have tried lineageos 16, los17, pixel experience 9 and 10 and they all softbrick. Only oos boots fine.
Hey everyone. Tried to flash a custom ROM for the first (and maybe last time) on the Mi5s from China Stable V10.2 to Lineage OS16. I think i did everything correctly at first
Unlocked the bootloader with Mi Unlock, put the SDK tools into ADB folder, flashed TWRP with command prompt, made a backup, wiped data, disabled force encryption, MAGISK root, flashed Mi5s firmware (although I could only find Oreo), LOS16 (Pie), and OpenGApps
I did all of that and got stuck on the LOS boot animation. Then I wiped data + cache partitions and tried again (didn't work). I quit trying with LOS but instead tried to flash the MIUI Global Stable recovery ROM with TWRP, also only made it to the boot animation. I then did a factory wipe on TWRP and tried to restore my backup but now it would only boot to the fastboot (not even trying to load the ROM)....... I can still access TWRP so maybe I'm not so screwed but what do I do? I just want a functioning device and don't mind if I go back to China Stable although advice on trying to flash a custom ROM would be appreciated. Thanks!
After flashing MIUI 11 beta I decided to go back to crDroid. Restored backup via twrp but it wouldn't boot, just booted into recovery, but twrp wouldn't decrypt data. I've seen this before and solved it by adb sideload crdroid rom (maybe because it includes vendor?). I tried this and now it just boots straight into fastboot. I tried fastboot boot twrp.img and that says "failed to load/authenticate boot image". What should I do?
Edit: After using miflash I can get back to stock, and then use fastboot to flash twrp. Twrp still doesn't ask for password to decrypt data. Every time I try to adb sideload crdroid.zip i end up stuck with fastboot again and have to miflash!?
Full wipe in TWRP and format data partition
reboot in recovery
flash crdroid and flash magisk
flash vmbeta after rom
I tried full wipes including data and flashing crdroid. I've also tried flashing vbmeta at multiple points.
Even after flashing back to stock miui with miflash android wouldn't boot, instead it just loaded miassistant (miui recovery). I'd have to flash twrp again, try flashing a new system and it would always reboot to fastboot.
The only solution has been to flash back to miui 11 beta (android 10) which boots fine. I'm still not sure whats going on but I'm ok with miui for now.
Deleted due to double post
briandarrel said:
I tried full wipes including data and flashing crdroid. I've also tried flashing vbmeta at multiple points.
Even after flashing back to stock miui with miflash android wouldn't boot, instead it just loaded miassistant (miui recovery). I'd have to flash twrp again, try flashing a new system and it would always reboot to fastboot.
The only solution has been to flash back to miui 11 beta (android 10) which boots fine. I'm still not sure whats going on but I'm ok with miui for now.
Click to expand...
Click to collapse
Solution mil kya bhai