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.
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
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)
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
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?
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