Before installing Lineageos I can install any rom and they work pretty good but one day when I flashed Lineageos and install it I worked but it have some glitches so I decided to go back to my previous rom but when I flashed it and reboot my device it wast booting and then I tried some other roms and they also didn't work. It happed after I install Lineageos. Is there any solution for this problem (I am using orange fox recovery and my device is rmx1821),
Related
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
Hello, people of XDA!
Not too long ago I bought the OP5T, and after using OxygenOS(5.0.3) for a while I thought it was time for a custom ROM, and decided to install Dirty Unicorns(v12), which was a disaster (the installation, not the ROM). After giving up on that idea, I settled on Resurrection Remix(v6.0.0) which by itself works wonderfully.
The problem is that when I flash Magisk(v16) and reboot, it takes me straight to recovery. I've tried using the official TWRP, blu_spark TWRP, and Codeworkx TWRP.
EDIT: I'm new to XDA, so I'm sorry if this is not the right place to post this question. If it isn't, please let me know so that I can remedy that problem.
This works:
wipe data/system/dalvik/cache -> flash Resurrection Remix(v6.0.0)
This does not:
wipe data/system/dalvik/cache -> flash Resurrection Remix(v6.0.0) -> flash Magisk(v16)
I've also tried to flash open_gapps (arm64, android 8.1.0, AROMA) but the apps just keep on stopping.
Any help would be appreciated.
Signed, Cidy02
I just installed Resurrection Remix with Magisk v16.
Flashed ROM with firmware. Did you flash the firmware?
Let the device start up.
Then rebooted to recovery and flashed.
Booted without issue. Then installed Magisk manager apk.
Only saying as I tried first flashing Magisk with the ROM and it did the same thing, went back to recovery.
So I'd try that first, leave flashing Magisk until you've confirmed it boots up.
I still haven't worked out which ROM I'll stick with. Thinking RR, LineageOS or Android Ice Cold Project.
davoidd said:
I just installed Resurrection Remix with Magisk v16.
Flashed ROM with firmware. Did you flash the firmware?
Let the device start up.
Then rebooted to recovery and flashed.
Booted without issue. Then installed Magisk manager apk.
Only saying as I tried first flashing Magisk with the ROM and it did the same thing, went back to recovery.
So I'd try that first, leave flashing Magisk until you've confirmed it boots up.
I still haven't worked out which ROM I'll stick with. Thinking RR, LineageOS or Android Ice Cold Project.
Click to expand...
Click to collapse
Firmware, you say? I saw no such thing on the Resurrection Remix website. Could you kindly point me in the right direction?
Thanks.
cidy02 said:
Firmware, you say? I saw no such thing on the Resurrection Remix website. Could you kindly point me in the right direction?
Thanks.
Click to expand...
Click to collapse
Hi, if you don't find solution, flash Ressurection Remix-->flash gapps-->boot your phone and after setup completed resrart to recovery a new now flash magisk
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.
So here's the biggest hair pulling dilemma:
The problem started after installing xiaomi.eu rom version 10.3.
I was using crDroid v5.4 (Android 9) Rom in peace. Then after trying the above mentioned rom,
my Orangefox recovery R8.3 was not showing. It was showing red lines. Then i installed various recoveries, everything is exactly like that.
Except TWRP Oreo By FenFern.
Now i'm stuck at MIUI 10 (8.1 Oreo) with the above mentioned (only) working recovery.
N.B: Installing Pie roms with oreo twrp results into distorted lines in the OS after installation.
How do i install the latest TWRP (or OrangeFox) recovery and Android Pie roms?
solidfoxhound said:
So here's the biggest hair pulling dilemma:
The problem started after installing xiaomi.eu rom version 10.3.
I was using crDroid v5.4 (Android 9) Rom in peace. Then after trying the above mentioned rom,
my Orangefox recovery R8.3 was not showing. It was showing red lines. Then i installed various recoveries, everything is exactly like that.
Except TWRP Oreo By FenFern.
Now i'm stuck at MIUI 10 (8.1 Oreo) with the above mentioned (only) working recovery.
N.B: Installing Pie roms with oreo twrp results into distorted lines in the OS after installation.
How do i install the latest TWRP (or OrangeFox) recovery and Android Pie roms?
Click to expand...
Click to collapse
Noob:silly::laugh:
Hey there,
You need to flash the latest stock miui rom using MIflash tool. i'm guessing the phone is encrypted in which case you wont be able to flash any other custom roms in the recovery too. (Unless you have a SD Card).
Alternatively, if you do have a SD card, then flash Batik recovery.I've it on my xiaomi.eu 10.4 rom and i can confirm that it works.
Let me know if it works for you.
cheers.
https://forum.xda-developers.com/xiaomi-redmi-5a/how-to/rollback-downgrade-to-miui-nougat-t3938904
Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"
shim80 said:
Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"
Click to expand...
Click to collapse
Try to flash V12.5.3.0.QFLCNXM with Twrp/O.f (TWRP is newer than this OF.)
then
reboot Twrp/O.F
Wipe/format data type yes
reboot Twrp/O.F
Flash rom
Sometimes the flashing of the recovery ROM does not work with the Twrp/O.F in this case use Miflash with a fastboot rom.
If you're still trying to figure this one out, I think I know how to solve your issue installing LOS.
You most likely used TWRP v3.70, am I right?
You should use TWRP v3.61 coz that was the last stable version that worked, the only thing is that you might need to find another custom recovery other than the official TWRP after installing an Android 12 custom ROM like LOS 19.1.
Lineage OS has their own recovery so you'd probably need to use that if you want to update it.
Same issue with me. yesterday. Though mine is fixed.
My workaround was: I installed the official 12.5.3 MIUI using OrangeFox. After boot, I tried installing PixelExperience using Pixel recovery. There I got successfully installed a custom ROM. Alhough I am not sure if the mounting/encryption of Internal SD is the cause.