Database Develop

Update to marshmallow roms

A year back I installed XZDualRecovery with a Lollipop ROM from xda. Now I want to update to resurrection remix for marshmallow. I wanted to know what is the path to follow?
Flash twrp 3.0+ (can I directly flash it on my current phone using twrp 2.8 on XZDualRecovery?).
and then the kernel?

THeLogiC said:
A year back I installed XZDualRecovery with a Lollipop ROM from xda. Now I want to update to resurrection remix for marshmallow. I wanted to know what is the path to follow?
Flash twrp 3.0+ (can I directly flash it on my current phone using twrp 2.8 on XZDualRecovery?).
and then the kernel?
Click to expand...
Click to collapse
You can flash RR rom using twrp 2.8 and if you want to update twrp then flash the twrp 3.0.2 zip after flashing the rom.You don't need to flash any other custom kernel on RR.It's stable.

Røbin said:
You can flash RR rom using twrp 2.8 and if you want to update twrp then flash the twrp 3.0.2 zip after flashing the rom.You don't need to flash any other custom kernel on RR.It's stable.
Click to expand...
Click to collapse
Thank you for your response. The rom is working perfectly.

[C6903] - cant run new NOUGAT custom roms - bootanimation 2-3 sec and phone turns off

At the beginning, please forgive me the quality of my English.
Me and other friends using c6903 have posted on the forum about trouble with running Nougat ROMs:
- [ROM][7.1.X][27/07/17][STOCK-CAMERA][3.4 KERNEL][TESTING] LineageOS 14.1 - UNOFFICIAL
- [ROM] [7.1.2] [OMS] [OFFICIAL] [Honami] Resurrection Remix Nougat v5.8.3 [01/08/2017]
- [ROM] [7.1.2] [Substratum/OMS] [UNOFFICIAL] [Honami] Android Ice Cold Project 12.1
For example LinageOS 14.1.
I flashed build from 11/07 without any problems.
Everythings worked fine, but when i try to flash newest build I encountered a big problem.
Bootanimation continues 2-3 sec. and phone turn off [check plz video].
Then only the launch button was active.
Everything I do exactly the same as in 11/07 build.
Why rom can't run?
The situation applies to all the above versions.
Resurrection Remix Nougat from 28/06 booted fine too.
Newer versions not...
One of friends - MIcHiJK - suggested that this could be a problem with changing the screen for "fake".
Me and him changed screens probably for counterfeiting.
Maybe someone else did it and have this problem?
....but why build from 11/07 (LinageOS), 26/08 (RR) and 20/06 (ACIP) booted without any problems?? In my case change screen was earlier.
What have I done so far to solve the problem.
- used TWRP 3.0.0 and 3.0.2
- Always full wiped (a few times format internal storage using twrp too)
- flashed roms when using Cyanogenmod 12.1
- flashed roms when using stock .236
- restored software using EMMa and Flashtool, then root (kingroot), flashed twrp by fastboot, full wipe, flash rom - without result
- used others kernels referenced by creators roms (flashed after installation rom).
Nothing worked.
I know I'm not alone. Many guys have problem like me.
Is anyone able to give a solution?
May God bless guy which will solve our problems!
"https://youtu.be/sOBquHNlbzQ"

Hello to all ppl which had this problem.
Since I replace my broken original xperia z1 Display, I wasn´t able to boot any of the new Nougat rom releases.
I solved this problem with a new Kernel.
Super Lamic Posted this Kernel to test the Battery Life but with this Kernel the problem was solved and I was able to run the new Releases on my fake Display.
Kernel Link: https://mega.nz/#!RN1nFYRT!546WMDdM2ToJEeZlleKTjS-TdR54rkYiOGKUDDWQ-t0
Install new LineageOS build on your xperia z1 with TWRP 3.1 (with 3.0 it wasnt able to install the boot.img).
Before you reboot select images, boot and flash the boot.img.
Then the new build should run without problems.
On other roms like Resurrection Remix it endet in invinite boot so I was just able to run normal Lineage.
I hope it helped someone. Im still interested what the devs changed that causes this problem. And I hope there will be improvments in future that this problem wont happen anymore.

same problem for me like OP. Would be interesting whats the reason for this behaviour that some nougat roms don't run on phones with replaced display. for me some still run, but then i have the problem that recovery is not available.

For those wo will flash AICP maybe this solution will work in RR too.
In normal Lineage it worked when i flashed cm12.1 Nouagt Kernel after flashing LOS 14.1.
But for RR or AICP it ended in infinite boot. Here is how I managed to get it work.
1. Download AICP (Latest Version [2017/08/01]) then download AICP (Version 2017/06/20).
2. Delete 'boot.img' from the Latest Version zip and put the 'boot.img' from the older relase into the Latest
3. Boot into TWRP 3.1 or 3.0, Wipe all and flash your Latest AICP zip with the older boot.img.
4. Boot phone. The z1 will show you just the Sony Logo. I waited some Minutes and powered off with power + volume up.
5. Connect phone in fastboot mode on PC and flashed cm12.1 Nougat Kernel.
6. Type 'Fastboot Reboot', the phone Turns on with the newer Boot screen where xperia stands on the bottom. You will finally see AICP Boot Animation and after some time rom boots.
---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------
Aaskereija said:
same problem for me like OP. Would be interesting whats the reason for this behaviour that some nougat roms don't run on phones with replaced display. for me some still run, but then i have the problem that recovery is not available.
Click to expand...
Click to collapse
Just Install Recovery via Fastboot. If you dont know how to do this you need to set up android sdk. You will find many tutorials in the internet.

MIcHiJK said:
Just Install Recovery via Fastboot. If you dont know how to do this you need to set up android sdk. You will find many tutorials in the internet.
Click to expand...
Click to collapse
really funny. sound good, doesn't work

Aaskereija said:
really funny. sound good, doesn't work
Click to expand...
Click to collapse
How did you installed the rom?
From which rom you came and which recovery did you used and how did you installed the recover?

different ways, but mostly with my standard custom-rom Tesla which is on Android 5.1.1. TWRP is on 3.1 which i install via cmd (fastboot flash recovery) cause build in recovery of tesla is broken.
Or i go over latest stock with dualrecovery, flash boot.img of the custom-rom (wich work) and then flash rom. but still recovery is gone after that.

@Aaskereija
I can tell you how I installed. I never lost my recovery. I came from xproject rom and I had nuts dual recovery. I flashed via fastboot advanced kernel, rebooted directly into inbuild TWRP 3.1, wiped all and flashed nougat rom. I had no recover so I flashed via fastboot official TWRP 3.0 and now I have a recovery. Since I installed TWRP one Time i never done it again. Everytime I flash a new rom it's still there. Maybe you try some different ways to install a nougat rom cuz it should work we all have the same device. Another question. Can you give me link to TWRP 3.1 for honami. I can't find TWRP 3.1 for z1 I used it just with advanced kernel. I just can find official TWRP on the internet witch is outdated

Guys, you don't have to create threads for this. I'll have an aftermarket display too, so I'll be forced to fix it anyway. And I have an idea what can be wrong...

MIcHiJK said:
@Aaskereija
I can tell you how I installed. I never lost my recovery. I came from xproject rom and I had nuts dual recovery. I flashed via fastboot advanced kernel, rebooted directly into inbuild TWRP 3.1, wiped all and flashed nougat rom. I had no recover so I flashed via fastboot official TWRP 3.0 and now I have a recovery. Since I installed TWRP one Time i never done it again. Everytime I flash a new rom it's still there. Maybe you try some different ways to install a nougat rom cuz it should work we all have the same device. Another question. Can you give me link to TWRP 3.1 for honami. I can't find TWRP 3.1 for z1 I used it just with advanced kernel. I just can find official TWRP on the internet witch is outdated
Click to expand...
Click to collapse
how do u installed it? fastboot flash recovery or else?
i was mistaken, its 3.0.2 not 3.1 if u still ned it, download

Aaskereija said:
how do u installed it? fastboot flash recovery or else?
i was mistaken, its 3.0.2 not 3.1 if u still ned it, download
Click to expand...
Click to collapse
Android Sdk put twrp.img in platform tools folder then open CMD in this foder, fastboot flash recovery TWRP.img.
I asked about twrp cuz in advanced kernel is TWRP 3.1 inbuild but I can't find just the twrp 3.1 IMG without kernel. Strange.

Not booting Android Oreo

Flashed stock rom, flashed different versions of twrp.
But the same stuck on logo after flashing every Oreo rom.
Want to taste but can't, somebody's got any solution?

May be an issue of recovery. Try with twrp 3.1.1-3 from below link.
https://androidfilehost.com/?fid=889764386195917689

Only 8.1 ROMs are not booting. also tried with this recovery and also with mine ported one. But nothing works

i also had the same problem.we need to patch the boot image after flashing the roms provided by daniel hk sir
preform a clean flash{wipe internal storage}
flash supersu 2.82 after flashing the rom
it will work for sure
i got it working on my phone

Can you give me that patched boot image.

How to patch?

[Question] How to "fastboot boot" a custom kernel with Magisk intact?

Hi,
I am getting into kernel development with a Google Pixel phone. I noticed that I need root permission in order to access syslog. My phone is on stock ROM with Magisk installed.
However, since Magisk only patched the original boot image, and since I am testing my kernel by temporarily booting it using "fastboot boot", I don't have access to root when using my own kernel. (I know this is sarcastic...)
I wonder how other kernel devs handle this situation. Do I need to compile the entire AOSP into a ROM with root builtin? Or is there another way around this using Magisk?
Thank you!

You don't fastboot boot a kernel, do you?
Anyway, if you use Anykernel you can flash your kernel over the Magisk patched boot image and Magisk should stay intact.
DISCLAIMER: I know absolutely nothing, zip, and null about kernel development.

Eventually I found out that, there was no way for my kernel to coexist with Magisk, because Magisk also modifies the kernel and I wouldn't want to merge its changes.
I think I'll just have to compile an engineering variant of AOSP from scratch... Are there any precompiled "official" images?

Didgeridoohan said:
You don't fastboot boot a kernel, do you?
Anyway, if you use Anykernel you can flash your kernel over the Magisk patched boot image and Magisk should stay intact.
DISCLAIMER: I know absolutely nothing, zip, and null about kernel development.
Click to expand...
Click to collapse
Thanks for the suggestion. But I couldn't get it to work. I think I'll just build an entirely new system.img from AOSP.
I'd also recommend building the entire AOSP for any other people facing this question. It takes more time but is officially supported by Google.

Magisk Not Working On Pie ROMs

It's been awhile but the last time this was brought up was in this thread:
https://forum.xda-developers.com/xiaomi-redmi-4x/help/magisk-doesnt-pie-roms-t3848025
Eversince interacting with the people in the thread I've been stuck on Oreo Non-treble for almost a year now, I've been dying to upgrade to 9.0, but the thing is the problem I had almost a year ago STILL persists to this day. I've tried installing Latest Magisk 19.0/19.1 on Latest AEX, Havoc and, PE.
I don't want to be stuck on Oreo forever, please to those who got root (Magisk) working on their Pie ROMS please help me. Thanks in advance for taking the time to read and help me!

Dont flash while you flash the rom let the rom setup then install the magisk apk and then flash the 18.1 magisk I do this mine always work on every rom

V1ncent9 said:
Dont flash while you flash the rom let the rom setup then install the magisk apk and then flash the 18.1 magisk I do this mine always work on every rom
Click to expand...
Click to collapse
I did what you said before posting this thread but flashed 19.0 and 19.1. I'll do it again with 18.1 later, i'm currently back on oreo.

Sygnomi said:
I did what you said before posting this thread but flashed 19.0 and 19.1. I'll do it again with 18.1 later, i'm currently back on oreo.
Click to expand...
Click to collapse
So, what,s the problem, magisk apk shows you: not installed?

zkoz said:
So, what,s the problem, magisk apk shows you: not installed?
Click to expand...
Click to collapse
Pretty much, yes.

Sygnomi said:
Pretty much, yes.
Click to expand...
Click to collapse
So, I have had a problem for several months. With magisk. Always shows me not installed on stock kernel. Then I install gabriel kernel and magisk root my phone.
Try!
I do not have to worry about switching the phone off or restarting. Magisk just works.

Hi
Same problem, same solution : flash a custom kernel ! Jaguar kernel works, Gabriel kernel seems to work too !

newbie_or_not_newbie said:
Hi
Same problem, same solution : flash a custom kernel ! Jaguar kernel works, Gabriel kernel seems to work too !
Click to expand...
Click to collapse
zkoz said:
So, I have had a problem for several months. With magisk. Always shows me not installed on stock kernel. Then I install gabriel kernel and magisk root my phone.
Try!
I do not have to worry about switching the phone off or restarting. Magisk just works.
Click to expand...
Click to collapse
What's the order of the flashing? Do I flash the Kernel right after the GAPPS or do I flash it after the initial setup (allowing the phone to boot and finish the setup)

Sygnomi said:
What's the order of the flashing? Do I flash the Kernel right after the GAPPS or do I flash it after the initial setup (allowing the phone to boot and finish the setup)
Click to expand...
Click to collapse
I do:
Clean partitions,
Flash rom,
Flash kernel
Flash magisk,
Reboot to system.
I dont know how it with gapps because i use microg
I think you ncan flash gapps after rom, then reboot nto system, then reboot to recovery and flash the other things.

And? Did you run magisk on pie?

zkoz said:
And? Did you run magisk on pie?
Click to expand...
Click to collapse
I actually managed to run Magisk (with working root) on pie, after flashing Latest Rockstar Kernel. Thanks for helping!

Sygnomi said:
I actually managed to run Magisk (with working root) on pie, after flashing Latest Rockstar Kernel. Thanks for helping!
Click to expand...
Click to collapse
Yeah, it looks like magisk also works with rockstar :]