Hello,
I am unable to install any Marshmallow rom (tried various downloaded from xda: uber, RR).
My phone is configured as follow:
Xperia Z1 6903 with unlocked bootloader
Latest CM 12.1 nightly
TWRP recovery 3,0,0,0.
If I flash the MM rom with the recommended procedure => bootloop on Sony logo.
The only way to get out of bootloop is to reflash boot.img from cm12.1 using flashtool.
This way i can get access to TWRP and reflash CM12.1
If I flash another boot.img from a MM image (last one I tried is Dirty Unicorn) and then flash the MM image => bootloop again.
What can I do to get MM working ?
I think that the installed kernel in incompatible with MM , giving me the bootloop
Thanks for your help.
Gerald
You need to flash the latest .236 firmware (FTF via flashtool) first before you try out any MM ROM.
Also note that the MM ROMs are in really early alpha stages and "might not" be suitable for daily use, unless you're really itching to try them out
Related
Hello, I tried to create a prerooted FW with PRFcreator on latest stock Lollipop FW, but dual recovery doesn't work. Are there any recovery roms compatible with lollipop that I can flash in the meantime?
STR33TPIR8 said:
Hello, I tried to create a prerooted FW with PRFcreator on latest stock Lollipop FW, but dual recovery doesn't work. Are there any recovery roms compatible with lollipop that I can flash in the meantime?
Click to expand...
Click to collapse
- if you are on unlocked bootloader: http://dl.androplus.org/Xperia Z3 Compact D5803_D5833/Z3C_ADV_stock_LP_v2.zip -stock LP kernel with TWRP
- if on locked: wait
Can I install this after Ive had lolipop rooted installed? I.r. will it let me keep my current set up but add a recovery? If so, how do I flash it? Sorry for being a newb
I have managed to root, install a custom recovery and unlock the bootloader.
I'm currently trying to install cyanogenmod 13.0 6.0.1 but whenever I flash the boot.img I extracted from the rom I get a bootloop?
What are the procedure from updating from KK to MM?
It's been a while since I owned a Sony Xperia help a brother out :good:
Don't flash boot img.Just Do wipes and flash the rom.
4.3 is jellybean(jb)
If you're using stock firmware 4.3 jellybean.. Then you need first to unlock your bootloader then root your phone using towel root or any other root app. after that you can fastboot boot.img or twrp.img to boot to recovery and flash cm13.
Sent from my Xperia SP using Tapatalk
You should flash TWRP 3.0.2 with Flashtool (via Fastboot option on Flashtool).
After flashing, power up your phone and boot to twrp.(if the flash was successfull, it boots to the twrp automatically).
Then Wipe system+data+dalvik cache+cache from TWRP.
Flash the CM13, flash Gapps.
Enjoy!
Hi everybody! I wanted a better battery life for my Z1 (1 screen hour at 75% :crying: ) so i flashed the CM11 latest snapshot, (as we all know, the LP builds has a very horrible battery management) and it worked, but when i switched from MX ROM to CM11 i lost my recovery (dual recovery) and it were replaced with CWM, i tried to install TWRP with some apps like Rashr, Flashify, ROM manager, Multirom manager and many others but it wasnt successful, and now im trying to flash a stock build of LP but flashtool gives to me this error:
- root this bundle is not valid -
I tried with a KK build but it was the same result. So I am stuck in CM, i dont know what more can i do... Can anyone help me?
The Bankshooter said:
Hi everybody! I wanted a better battery life for my Z1 (1 screen hour at 75% :crying: ) so i flashed the CM11 latest snapshot, (as we all know, the LP builds has a very horrible battery management) and it worked, but when i switched from MX ROM to CM11 i lost my recovery (dual recovery) and it were replaced with CWM, i tried to install TWRP with some apps like Rashr, Flashify, ROM manager, Multirom manager and many others but it wasnt successful, and now im trying to flash a stock build of LP but flashtool gives to me this error:
- root this bundle is not valid -
I tried with a KK build but it was the same result. So I am stuck in CM, i dont know what more can i do... Can anyone help me?
Click to expand...
Click to collapse
KK custom roms have recovery inside kernel. You have recovery in your FOTA or Recovery partition. The in-kernel recovery won't let you start Fota recovery, no matter what you try to install. Latest LP roms, as well as MM don't have recovery in kernel. So, you want to fastboot an LP kernel that has no recovery: fastboot flash boot boot.img. Then fastboot TWRP: fastboot flash recovery recovery.img. After that, you can boot into TWRP recovery and install whatever you want...
optimumpro said:
KK custom roms have recovery inside kernel. You have recovery in your FOTA or Recovery partition. The in-kernel recovery won't let you start Fota recovery, no matter what you try to install. Latest LP roms, as well as MM don't have recovery in kernel. So, you want to fastboot an LP kernel that has no recovery: fastboot flash boot boot.img. Then fastboot TWRP: fastboot flash recovery recovery.img. After that, you can boot into TWRP recovery and install whatever you want...
Click to expand...
Click to collapse
Thanks a lot! Ill try it
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.
Long time ago, I switched to CM12.1, and I figured I would give a try to CarbonROM (Lineage = CM's successor and I used CM and didn't like it much, omnirom = too new and probably buggy, carbonrom = still maintained and "older").
Here's what I did so far:
- downgraded to 23.0.A.2.93 (4.4.4) (flashed ftf with flashtool)
- rooted it using giefroot 3.1
- installed twrp using another tool with an installer (http://nut.xperia-files.com/)
- then upgraded to pre-rooted version of .291 D5803_23.5.A.1.291_1289-7524_R5D_PreRooted_RecRoot_v4_SuperSU_276.zip, which comes with TWRP 3.0.2.0 (did that using twrp I had just installed)
Then my plan was to upgrade directly to CarbonRom by flashing from TWRP, but it gives me the error 7, so I figured I'd just upgrade TWRP but:
- tried upgrading TWRP (followed instructions here:https://forum.xda-developers.com/z3-compact/general/d5803-z3c-aries-twrp3-0-t3543113), using lineage or omni recovery: will flash "successfully" with fastboot, but when I actually go into recovery mode it's the same old twrp version
- tried flashing the img directly from old twrp version, both recoveries, and same results: when I reboot to recovery, it's the same old version.
I'm therefore stuck right now and can't figure out what I'm doing wrong, nor how I could work around this issue.
Installed twrp 3.1.1 from zip, which allowed me to install Carbon.
Still trying to figure out why flashing didn't work, and why the zip did. Anybody can tell me?
Edit: phone is a D5803. unlocked bootloader, TA partition backed up (just in case), i have latest flashtool, drivers are installed, I know how to go into fastboot, I know how to flash a zip...
Try to flash FOTAKernel instead of recovery
Example:
Code:
fastboot.exe flash FOTAKernel "recovery-Lineage 14.1.img"