Hi,
I have unlocked bootlader and am trying to install this rom but Philz recovery shows "status 7" error when I flash the zip.
What is the problem, how can I flash the zip succesfullly?
Thanks in advance.
EDIT: It seems that the phone does not boot anymore. It does not enter into recovery mode either. It shows "Sony" and "Xperia" words on the screen and waits indefinitely.
Anyone?
CarbonRom is an aftermarket firmware based on the CyanogenMod and Android Open Source Project.
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Carbon|CM|AICP|AOKP|Slim|Omni
Version Information
Status: Stable
Created 2015-05-29
Last Updated 2015-05-28
flash boot.img from carbon rom with fastboot, I´m not sure if carbon has cm or twrp recovery, just in case flash multi rom twrp with fastboot (you don't need to use more than one rom if you don't want), now you can reach recovery in usual way(vol +)
sudo fastboot flash boot fota-twrp2.8.5.0-z3c.img
you need xposed alpha for lp 5.1... here:
I flashed stock kitkat with flashtool, then I saw your reply. I flashed TWRP and restored my backup and i am at the start point again. I will try again.
Can you provide flash boot.img and flash recovery commands? I am using linux, I flashed TWRP with command below in fastboot mode (connected usb cable with vol + pressed when the phone is off) but I am not sure about it. But it worked.
Code:sudo fastboot flash boot fota-twrp2.8.5.0-z3c.img
Should I flash boot.img after "status 7" error? And should I run same command above, with filename boot.img?
I flashed stock kitkat with flashtool, then I saw your reply. I flashed TWRP and restored my backup and i am at the start point again. I will try again.
Can you provide flash boot.img and flash recovery commands? I am using linux, I flashed TWRP with command below in fastboot mode (connected usb cable with vol + pressed when the phone is off) but I am not sure about it. But it worked.
Code:sudo fastboot flash boot fota-twrp2.8.5.0-z3c.img
Should I flash boot.img after "status 7" error? And should I run same command above, with filename boot.img?
Correct command for boot.img is fastboot flash boot boot.img
For fota recovery fastboot flash recovery recovery.img
Very nice rom so far thanks.
The only real issue I have is the camera, more specifically the camera button. I want it to work properly. Any solutions?
Thanks
Thanks. I have managed to flash recovery, but in order to solve "status 7" error, I modified "update-script" in the rom. I deleted the assert expression at the beginning of the file. This time zip is flashed succesfully, after boot.img flash, it booted correctly.
Would that be possible? i.e. A bootloader unlocked custom rom with DRM-protected features still in tact? Like many, that's the only thing keeping me from unlocking the bootloader because I want to keep my camera's low light performance. Stock Sony is good enough for me, but the memory leaks are driving me nuts and who knows when they'll roll out 5.1.x?Agreed... I'd quite like to the get the stock (or 20MP Superauto modified version) of the sony camera with DRM on this rom, then it would be heaven too
Would that be possible? i.e. A bootloader unlocked custom rom with DRM-protected features still in tact? Like many, that's the only thing keeping me from unlocking the bootloader because I want to keep my camera's low light performance. Stock Sony is good enough for me, but the memory leaks are driving me nuts and who knows when they'll roll out 5.1.x?
I'm aware that DRM features can be restored after unlocking the bootloader, but as far as I know, one must return to stock (and a relocked bootloader) in order for the features to work again.Im no developer, but you can patch drm back on a custom rom from what ive read.. and and I guess the camera is just an app mostly
Cheers
@Myself5
I have noticed a bug, when I go to reboot the phone or reboot in to recovery the device shuts down and does not restart or go in to reovery.
I have to push the power button again to power up the phone and press vol + if I want to get to recovery.
I am using your M5 kernel in combination with the ROM if that may play any part in this issue.
Would it help to send you a bug report?
Think it's a known cm12.1 bug, meaning you have probably alarm active, disable that and see!
Sent from my D5803 using XDA Free mobile app