[ROM][LB][UB] eXistenZ v2.0.0 | Black Edition | 4.3 | 10.4.B.0.569 | 23/01/14

niaboc79

Recognized Developer / Themer
Sep 8, 2007
12,440
68,159
263
Enghien
www.nirvana-records.be
Additional bug is when i want to reboot, it just hang at the niaboc79 screen splash and do nothing, so have to push yellow button at the back to restart. My solution to this issue is turn ON advance power menu in the gravity box.
That bug is on all my JB 4.3 roms but I have finally found the solution :)

This will be fixed in first OTA update.
 
  • Like
Reactions: demonicangell™

Sirence

Senior Member
Jun 17, 2012
689
135
0
That bug is on all my JB 4.3 roms but I have finally found the solution :)

This will be fixed in first OTA update.
So the updates for this Rom will be only via ota? I kind of wanted to skip this version because of the reboot issue and only install it once fixed, is that possible?

Gesendet von meinem Xperia ZL
 

butatx

Senior Member
Sep 22, 2009
517
157
0
Perak
Deleted.

My bad, bug reported regarding the usb otg is not a bug actually, it's my pendrive which has problem.


Update : After checking my pen drive, it actually formatted as exfat not fat32. If i connect with note 2 it can be mounted, but ZL with this ROM won't. Maybe Sony rom did not support it yet. Anyone can try with stock rom.

Update 2 : actually kernel is the culprit, doom v20r2 has problem detecting exfat pendrive, revert back to stock rom and it detect with no problem.



Sent from my C6506 using Tapatalk
 
Last edited:
  • Like
Reactions: niaboc79

marksee

Senior Member
Jul 30, 2011
123
14
0
los angeles
Thank you for making a black version of your rom. It is literally, the sexiest rom i have seen! In today's world, all of us are constantly looking at our phone, and it strains our eye alot, your black theme definitely eases this strain and makes it so much bearable, specially at night time. I wish you success in your endeavors and request that you keep development on this version alive.
 
  • Like
Reactions: niaboc79

NamenIos

Senior Member
Nov 26, 2010
473
243
63
When I start the OTA Updater I get the message "Invalid ROM (xzlexistenzblack) & device (c6506) combo!" and below Available Updates it says "Error fetching update info: Invalid ROM (xzlexistenzblack) & device (c6506) combo!". I guess that is the case because there is no update yet and it is no reason to worry?

I there any downside in renaming the device to the values of my local ftf (ro.product.name, ro.product.device etc.) in build.prop?

[…]recovery ( http://nut.xperia-files.com/?dlid=Wk...EuZmxhc2hhYmxl )"
when i click the link for recovery, it said file not found.
Use either the 2.81-BETA or the latest stable. I can't find a flashable zip of the latest stable for recovery on http://nut.xperia-files.com/ , but the beta works fine and has the proper device name.
 

marksee

Senior Member
Jul 30, 2011
123
14
0
los angeles
Same here, OTA says Invalid ROM (xzlexistenzblack) & device (c6506) combo!" and below Available Updates it says "Error fetching update info: Invalid ROM (xzlexistenzblack) & device (c6506) combo!".

Maybe we need to add C6506 to approved devices to receive the update over the air list ?

Also i did install the latest beta 2.83 from nut.

When I start the OTA Updater I get the message "Invalid ROM (xzlexistenzblack) & device (c6506) combo!" and below Available Updates it says "Error fetching update info: Invalid ROM (xzlexistenzblack) & device (c6506) combo!". I guess that is the case because there is no update yet and it is no reason to worry?

I there any downside in renaming the device to the values of my local ftf (ro.product.name, ro.product.device etc.) in build.prop?


Use either the 2.81-BETA or the latest stable. I can't find a flashable zip of the latest stable for recovery on http://nut.xperia-files.com/ , but the beta works fine and has the proper device name.
 

demonicangell™

Senior Member
Aug 5, 2011
2,201
572
0
Bombay
When I start the OTA Updater I get the message "Invalid ROM (xzlexistenzblack) & device (c6506) combo!" and below Available Updates it says "Error fetching update info: Invalid ROM (xzlexistenzblack) & device (c6506) combo!". I guess that is the case because there is no update yet and it is no reason to worry?

I there any downside in renaming the device to the values of my local ftf (ro.product.name, ro.product.device etc.) in build.prop?


Use either the 2.81-BETA or the latest stable. I can't find a flashable zip of the latest stable for recovery on http://nut.xperia-files.com/ , but the beta works fine and has the proper device name.
Same here, OTA says Invalid ROM (xzlexistenzblack) & device (c6506) combo!" and below Available Updates it says "Error fetching update info: Invalid ROM (xzlexistenzblack) & device (c6506) combo!".

Maybe we need to add C6506 to approved devices to receive the update over the air list ?

Also i did install the latest beta 2.83 from nut.
there is no ota available so that is normal .. after the first ota it will show correctly .
please search before u post
 

ej_424

Senior Member
Apr 17, 2009
566
63
0
Minneapolis, MN
Coming from CM11

Isn't there a easier way to get on this rom coming from CM11 with root and unlocked bootloader? Do I really have to flash back to stock and then go through the root process again?

Why can't I just flash a new compatible kernel with a customer recovery, boot back into the new recovery and flash this rom via CWM?
 

NamenIos

Senior Member
Nov 26, 2010
473
243
63
there is no ota available so that is normal .. after the first ota it will show correctly .
please search before u post
There is no mention of that in this thread. Apparently this information is in the non black edition thread, but that's kind of a stretch.


I edited 11 lines of the build.prop to match the one of the C6503 of my local ftf (of course kept everything below "# eXistenZ") and flashed also the baseband of the ftf. So far I did not encounter any problems and my phone is again showing up as C6503 and not C6506.

For extracting the build.prop out of the ftf I used flashtool to extract the system.ext4 and ext2explore to extract the build.prop.

edit: Also I changed to the open source Superuser app (flashed in the recovery) and had not encountered any problems with this (Titanium Backup warns but works flawlessly).
 
Last edited:

adibayer_

Senior Member
Oct 3, 2010
592
73
0
28
Melbourne
reporting, the calculator app is white version, not the black one.
also the on off tools widget is in white version, not the black.

maybe you can fix this. thanks is advance