Related
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.
Hi guys,
Is it possible to install TWRP alongside with the official already installed Flyme 6.
I unlocked bootloader, installed TWRP and tried some custom ROMs, I wanted Flyme back so I reinstalled stock recovery and installed Flyme 6. Now I want TWRP back
hi
hi dude, how to instal flyme back? my m2 note already instal twrp, but i dont know how to instal back flyme boot, or rom.. can you help?
renggapahlawan said:
hi dude, how to instal flyme back? my m2 note already instal twrp, but i dont know how to instal back flyme boot, or rom.. can you help?
Click to expand...
Click to collapse
Hi, I reinstalled the stock recovery and then I just flashed the flyme 6.1 update.zip.
I found the stock recovery for my phone here (THE MINI VERSION) (I can't post link, it's in the verdict)
DO NOT USE THAT IF YOU'RE NOT SURE IT'S COMPATIBLE WITH YOUR PHONE. You can brick your phone entirely.
Here's the steps
1- Boot into fastboot
2- On a terminal run "fastboot flash recovery recovery.img"
3- Wait 2-3 minutes and reboot
Now you have your stock recovery back you can download flyme and install it the usual way
well sorry for being late but yes you can flash Flyme over TWRP no problem there but sometime flyme recovery overwrite TWRP so take care of it flash it again via pc
regards~
murtaza1326 said:
well sorry for being late but yes you can flash Flyme over TWRP no problem there but sometime flyme recovery overwrite TWRP so take care of it flash it again via pc
regards~
Click to expand...
Click to collapse
Thanks a lot
ChakibDEV said:
Thanks a lot
Click to expand...
Click to collapse
my pleasure
murtaza1326 said:
well sorry for being late but yes you can flash Flyme over TWRP no problem there but sometime flyme recovery overwrite TWRP so take care of it flash it again via pc
regards~
Click to expand...
Click to collapse
Just to be sure: are you saying that i can flash flyme official roms directly from twrp? i don't mind losing the twrp recovery, i just want to avoid bootloops. Thanks
io00 said:
Just to be sure: are you saying that i can flash flyme official roms directly from twrp? i don't mind losing the twrp recovery, i just want to avoid bootloops. Thanks
Click to expand...
Click to collapse
you can do it you may loose twrp but if you backup and restore it after you flash flyme there will be no problem
flyme can be installed over TWRP very easily
hello.. los 15.1 touch screen issues fixed? and which firmware reccomended?
Hey, I'm using LOS 15.1 for two months now and no issues to be found. But always use the latest MIUI firmware.
ngato35 said:
hello.. los 15.1 touch screen issues fixed? and which firmware reccomended?
Click to expand...
Click to collapse
PlagueCz said:
Hey, I'm using LOS 15.1 for two months now and no issues to be found. But always use the latest MIUI firmware.
Click to expand...
Click to collapse
How to install LOS 15.1? I'm not so advanced user. I have already unlocked bootloader but not able to install TWRP recovery. Currently my Mi 5 32/3 GB is running on Global beta 8.3.29(i.e. latest). I'm facing auto wake up and Google Assistant continuously popping up issue. And how is LOS in day to day use? I want my Mi 5 to last at least another 6 months.
It's simple:
1/ Flashing TWRP:
Download this whole folder (all 6 files) and save it to your PC: https://drive.google.com/open?id=1IXNOlda6yF7dNQEvPH12mILdMkUbf2bt.
Turn your phone to Fastboot mode.
In your PC folder with downloaded files, open "install_TWRP.bat". It will be in Czech language, but all you have to do is to press any key (enter etc. ). It will download TWRP to your phone.
Wait a while (one minute), again press any key and your phone will boot to system.
2/ Boot to system. To your phone, download latest TWRP from here: https://eu.dl.twrp.me/gemini/twrp-3.2.1-1-gemini.img.html
3/ Boot to TWRP. Update TWRP (use that you just downloaded - 3.2.1-1).
4/ Wipe Dalvik Cache, Data, Cache, System. Optional: wipe Internal storage, I always do that.
5/ Connect phone to PC (you are still in TWRP). Download LOS, GApps 8.1 ARM64 (http://opengapps.org/) and root to your phone (optional). Or use USB OTG or ADB.
6/ Flash LOS, GApps and root. Do not reboot between these steps.
7/ Boot to system.
ngato35 said:
hello.. los 15.1 touch screen issues fixed? and which firmware reccomended?
Click to expand...
Click to collapse
8.1.4
So, I tried everything, flashed the ROM based on OREO like 9.6.1.0 ended in bootlooping the device, also custom rom based on OREO doesnt work too, like pixel experience, LINEAGE, ETC
Other than OREO based, ROM based on NOUGAT works well, like MIUI 8.xxx or RR based on NOUGAT
Any idea why this happens?
codearm2 said:
So, I tried everything, flashed the ROM based on OREO like 9.6.1.0 ended in bootlooping the device, also custom rom based on OREO doesnt work too, like pixel experience, LINEAGE, ETC
Other than OREO based, ROM based on NOUGAT works well, like MIUI 8.xxx or RR based on NOUGAT
Any idea why this happens?
Click to expand...
Click to collapse
-Format data
-wipe
-use otg drive since format data delete everything
-flash firmware newest 8.5.10 minimum requirment for oreo
-flash rom
-flash gapps
-reboot
evanlocked said:
-Format data
-wipe
-use otg drive since format data delete everything
-flash firmware newest 8.5.10 minimum requirment for oreo
-flash rom
-flash gapps
-reboot
Click to expand...
Click to collapse
tried it all, still bootloop
codearm2 said:
tried it all, still bootloop
Click to expand...
Click to collapse
flash any miui dev rom beyond 8.5.10 using miflash
reboot once ...
flash twrp ...
push any oreo rom (ie. LOS 15.1) and gapps while in recovery ...
Install that rom and gapps ...
reboot to twrp ...
format data ...
reboot again to twrp ...
reboot to system ...
3Dota said:
flash any miui dev rom beyond 8.5.10 using miflash
reboot once ...
flash twrp ...
push any oreo rom (ie. LOS 15.1) and gapps while in recovery ...
Install that rom and gapps ...
reboot to twrp ...
format data ...
reboot again to twrp ...
reboot to system ...
Click to expand...
Click to collapse
not working
Flashed 8.5.10 rom, ended in bootloop
flashed the LOS 15.1 and GAPPS, still bootloop
so, any one?
codearm2 said:
so, any one?
Click to expand...
Click to collapse
Your custom recovery needs to be an Oreo version compatible, so you can install oreo based roms on it.
Try to update to early version.
Regards.
codearm2 said:
So, I tried everything, flashed the ROM based on OREO like 9.6.1.0 ended in bootlooping the device, also custom rom based on OREO doesnt work too, like pixel experience, LINEAGE, ETC
Other than OREO based, ROM based on NOUGAT works well, like MIUI 8.xxx or RR based on NOUGAT
Any idea why this happens?
Click to expand...
Click to collapse
try updating firmware and twrp and flash lazy flasher zip after rom instalation hope it fix . *Lazy Flasher zip is must
Steffanom said:
Your custom recovery needs to be an Oreo version compatible, so you can install oreo based roms on it.
Try to update to early version.
Regards.
Click to expand...
Click to collapse
already 3.2.3 version which I believe supports oreo rom
Tsuzan said:
try updating firmware and twrp and flash lazy flasher zip after rom instalation hope it fix . *Lazy Flasher zip is must
Click to expand...
Click to collapse
didnt work, still bootloop
codearm2 said:
so, any one?
Click to expand...
Click to collapse
so ... what last rom boot fine in your Mi5?
3Dota said:
so ... what last rom boot fine in your Mi5?
Click to expand...
Click to collapse
any nougat rom works well
tried flashed 8.5.10 rom, still bootloop
codearm2 said:
any nougat rom works well
tried flashed 8.5.10 rom, still bootloop
Click to expand...
Click to collapse
this is quite weird ... since if you install any nougat ... you'll sure receive OTA update to oreo (dev or stable) ...
why dont you take that OTA?
3Dota said:
this is quite weird ... since if you install any nougat ... you'll sure receive OTA update to oreo (dev or stable) ...
why dont you take that OTA?
Click to expand...
Click to collapse
yes, installing the OTA based on OREO update also cause bootloop happens
basically, anything OREO based, whether it's ota or flashing it manually through TWRP, ZCX TWRP, or Mi Flash cause bootloop
Have you wipe your internal partition?
I think we need to wipe all partition after installing firmware when come from nougat to Oreo, because Oreo have new vendor partition.
At least you should use twrp-3.2.1-1-gemini
Sent from my MI 5 using Tapatalk
codearm2 said:
not working
Flashed 8.5.10 rom, ended in bootloop
flashed the LOS 15.1 and GAPPS, still bootloop
Click to expand...
Click to collapse
Try reflashing latest twrp via fastboot (not from within twrp).
After wiping all partitions (also mount and wipe vendor) and formatting data, reboot to recovery before flashing the ROM to access the data partition correctly again.
Then also try to boot (would go with a custom ROM) without any gapps, mods or root first, to further center the problem.
What happens now?
Have the same problem
Try to install latest build via fastboot --> failed
Try to install miui nougat based work, ota update to oreo based -->bootloop
Also try to flash all included internal storage but the problem still occured
Any miui nougat based and aex mod 5.1 work fine in my phone
Install lazy flasher before installing anything like SuperSU...
masruri03 said:
Have you wipe your internal partition?
I think we need to wipe all partition after installing firmware when come from nougat to Oreo, because Oreo have new vendor partition.
At least you should use twrp-3.2.1-1-gemini
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
already wiped, still not working
Phil_Smith said:
Try reflashing latest twrp via fastboot (not from within twrp).
After wiping all partitions (also mount and wipe vendor) and formatting data, reboot to recovery before flashing the ROM to access the data partition correctly again.
Then also try to boot (would go with a custom ROM) without any gapps, mods or root first, to further center the problem.
What happens now?
Click to expand...
Click to collapse
flashed latest twrp via fastboot, also already wiped all partition included mount and wipe vendor, also formated the data and reboot first before flashing the rom, boot without any gapps, still it doesnt work
reysack said:
Have the same problem
Try to install latest build via fastboot --> failed
Try to install miui nougat based work, ota update to oreo based -->bootloop
Also try to flash all included internal storage but the problem still occured
Any miui nougat based and aex mod 5.1 work fine in my phone
Click to expand...
Click to collapse
yeah, practically the same with mine
brhnahmad05 said:
Install lazy flasher before installing anything like SuperSU...
Click to expand...
Click to collapse
tried, doenst work
codearm2 said:
flashed latest twrp via fastboot, also already wiped all partition included mount and wipe vendor, also formated the data and reboot first before flashing the rom, boot without any gapps, still it doesnt work
Click to expand...
Click to collapse
Puh, don't know.
Do you have an old backup of your efs partition lying around?
If so, try restoring that.
If that also doesn't help, I'm through with my math here, I think...
Flash a Lineage OS 14.1 build without GApps but with a firmware that supports Oreo. Then, go to developer settings, turn on ADB and run adb devices on your computer so that the RSA Fingerprint pops up. There, make sure you tap on remember this computer and click ok.
Now, do an update to Lineage 15.1 without wiping anything. As soon as you reboot your phone, connect it to your PC and try to get a logcat. Paste the logcat here and we'll be able to see what's actually going on.
Im trying to install the ressurection remix rom, and i downloaded twrp 3.1.1-1 from the site, but it wont boot. just stuck at the TWRP logo..?
xSpartacusx said:
Im trying to install the ressurection remix rom, and i downloaded twrp 3.1.1-1 from the site, but it wont boot. just stuck at the TWRP logo..?
Click to expand...
Click to collapse
you can boot with the older version. 3.1.1.0
kewlzter said:
you can boot with the older version. 3.1.1.0
Click to expand...
Click to collapse
ye i found that out after the fact. alls good.
I was able to install working twrp on mine. It is a patched version by "Jleeblanch". https://androidfilehost.com/?w=files&flid=294840
I downloaded and installed the zip through fastboot boot of 3.3.3-0 which works fine but even the Sept version of 3.3.3-1 hangs for more than 5 minutes. For the life of me I can't figure out how to flash the img of 3.3.3-0 directly to the phone.