Database Develop

[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]

[STOCK][C6602&C6603][4.2.2] Update to 10.3.A.0.423 [Rooted & XZDualRecovery][LB/UB]
Requirements:
Flashtool by @Androxyde
XZDualRecovery 2.5 BETA
Current FW version: 10.1.A.1.350, 10.1.A.1.434, 10.1.1.A.1.253 or 10.1.1.A.1.307 all can be updated!
Special features:
Superuser integrated in system, FULL root, no reboots when remounting /system RW!
XZDualRecovery 2.5 BETA (CWM 6.0.3.2 & TWRP 2.5.0.0) pre-installed;
Tailored FTF to minimize the chance of accidental system wiping!
No need to clear caches!
@shem2409 created a nice youtube video guide to assist you in your work, be sure to check this post for it! Thanks m8!
In the following guide I suggest you use an external SDCard but that's just good practice, you can use your internal storage or even an USB OTG storage device in TWRP if you like to install, that's no problem!... If you are modding and the likes, best is to have an external sdcard, just for safeties sake.
C6602: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6602: Download C6602.flashable.423.zip (Bittorrent: 686MB) and C6602_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6602.flashable.423.zip' on (the external) SDcard1;
Put 'C6602_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6602.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6602_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
C6603: How to update to 10.3.A.0.423:
NOTE: STICK TO THIS ORDER AND STEPS!!
For C6603: Download C6603.flashable.423.zip (Bittorrent: 719MB) and C6603_10.3.A.0.423-stripped.ftf (15MB), save it somewhere you remember;
Put 'C6603.flashable.423.zip' on (the external) SDcard1;
Put 'C6603_10.3.A.0.423-stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6603.flashable.423.zip' in TWRP, do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C6603_10.3.A.0.423-stripped.ftf';
Reboot to system without clearing (dalvik-/)cache.
The first boot will be considerably slower and after a long wait at the boot animation you will see Android optimizing the apps on your phone.
After updating your NFC firmware and some update information has been displayed, all is done!
I have done this myself, using my own method and I have not found any problem yet, again! :fingers-crossed:
Enjoy! :victory:
Known XZDualRecovery Issues:
TWRP Usage warning: It seems TWRP 2.5.0.0 has issues with the internal storage, which seem related to the changes made to support encrypted storage volumes... This means the internal storage sometimes shows up almost empty (just folders) and no files. Try to use CWM when that happens.
Busybox Updater/Installer: If you have XZDualRecovery installed, un-install any Busybox updating app/tool as most if not all of them will install a version of busybox which does not support the lzma compression applets XZDualRecovery depends on. The version installed together with XZDualRecovery is very stable and I have yet to hear anyone complain about it's stability.
How to report errors:
Please, before shouting out "It doesn't work!!1!" or "I lost root!" or even "My phone reboots when remounting /system RW!!" try the following:
Restore a /system ONLY using any means you are familiar with so you can try again.
Root it using [Z][ROOT] DooMLoRD Easy Rooting Toolkit.
Install XZDualRecovery and then try to update again using TWRP. This time you can skip the FTF as it has already done it's job.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /tmp/XZDualRecovery, pack them up and send them to me.
Thank you
Flashable ROM Mutator:
Download AROMA ROM Mutator 0.14
This (former patch package) uses AROMA to create a user friendly menu to choose between updates to be installed.
If you want to switch from SuperSU (default in this ROM) to SuperUser (Be careful, SuperUser is incompatible with 4.2.2!) you can use this to make the change.
If you have the reboot problem when trying to remount /system writable, you can reinstall the superuser app of your preference, it's installation includes the latest patch.
If you are missing /system/bin/chargemon.stock and you want to be able to charge your phone while it's turned off.
Flash using one of the recoveries!
Version 0.13 and upwards is using AROMA 2.70B1 or better, the below warning can be ignored for now. Let me know how it performs!
AROMA Warning: AROMA currently works best in TWRP but even there it has some issues on the Z/ZL. It sometimes does not start up correctly or it has a 'sticky button' issue. It makes it a little less easy to use but this will be fixed in time. It is a combination problem caused by the new hardware and incompatibility with it and the fact the recoveries both have been updated considerably to work on the latest phones, causing issues with some functionality of AROMA.
If it hangs when trying to start, reboot your phone and try again.
If it has the sticky buttons, press the button again to activate.
You can avoid the sticky buttons by pressing them for about half a second (that means not too short and not too long). It will work, it's just showing a bug associated with the latest recoveries.
The Samsung S4, HTC One and One X and the Nexus 4 & 7 show the same issues. For them AROMA sometimes crashes, this is an issue i have not yet observed on the Z/ZL.
Thanks go to @Androxyde for the FTF creation, cheers m8!

nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.

After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.

Ya, I need manual install dual boot to access back to CWM/TWRP then just can install but the preinstall superuser root is not working at all.
Root working back by installing DooMLoRD Easy Rooting Toolkit (v15) - http://forum.xda-developers.com/showthread.php?t=2327472

Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?

Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.

Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.

Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.

zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
I got into the same problem, and cannot get out. Anyone has any advice?

please fix dead links

dopeee said:
nice! so does that mean we dont need to factory wipe before upgrading? I thought if we go across versions (4.1.2 > 4.2.2) you gotta wipe all your stuff first.
Click to expand...
Click to collapse
I found out with the leak by doomlord that it would be possible to update, no need to wipe, the official update works even better
lysp said:
Is there any reason why the dalvik cache are not wiped in this release process?
Is it simply a speed/optimisation thing, or will it cause issues if it happens?
Click to expand...
Click to collapse
It's meant as an update process and not wiping anything will make the ROM treat your phone as one that just got updated
Faelz said:
Comming from PAC... Do i need to install other Stock rom before update or just use the instructions above? thanks.
Click to expand...
Click to collapse
Yes, you need a stock ROM before you can flash this, I would not recommend updating your phone from PAC...
bungknees said:
Ok, so this is what ive done to get this to boot, on existing rom with recovery installed I flashed the .432.zip, obviously it bootlooped, but then flashed the ftf file which got the rom to boot. Then rooted and installed recovery as Andrewtst has linked to above.
Cheers.
Click to expand...
Click to collapse
&
zanndoth said:
After flashing the stripped ftf, the phone doesn't go into recovery. It shows green light, Sony logo and nothing else. Then it just reboot again. Already tried downloaing the file and flashing again. still the same problem.
Click to expand...
Click to collapse
&
chuazy said:
I got into the same problem, and cannot get out. Anyone has any advice?
Click to expand...
Click to collapse
I have modified the guide a bit as i should have done before i posted it...
Restore the kernel to anything other then the 4.2.2 one and then try to flash the update package, after flashing the update, re-flash the kernel.
I made one error in my guide: If someone is not using the correct version of XZDualRecovery (2.5 BETA) then you lose recovery when on the 4.2.2 kernel. The correct steps order to prevent this from happening are now in the OP.

please fix dead links

calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
+1

After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?

calvinleeabc said:
please fix dead links
Click to expand...
Click to collapse
buciupetru said:
Can't download the zip and ftf file, doesnt work, anyone can confirm that? can you reuploading or verify if is everything ok, thx for the work you done.
Click to expand...
Click to collapse
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now

lethalfriend said:
After flashing this Rom, my data is still at Data/media but not on the default path, what should i do in this case? should i move the data from data/media to new location manually?
Click to expand...
Click to collapse
No need: /data/media IS the 'new' location.

[NUT] said:
Sorry guys, the server is under a heavy load at the moment... the webserver lost a few workers that ate up much of the cpu time. I've killed them all and restarted the webserver.
IF the problem was caused by that, it's solved now
Click to expand...
Click to collapse
thanks:good:efficient

[NUT] said:
No need: /data/media IS the 'new' location.
Click to expand...
Click to collapse
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location

lethalfriend said:
But strangely, my phone isn't detecting the media from the above path, its just showing the pictures form newly created DCIM folder which is on a different location
Click to expand...
Click to collapse
Ooh... i now see what you mean... you are correct. I'll patch up the flashable package to do it automatically.
For you, use a file explorer to move the contents (skipping the 0 folder) of /data/media to /data/media/0/. Sorry man, i missed that completely on my phone

server stilll unreachable.

[Q] Help Needed! Two strange isseus after iHakers 1.1 install!

Hi!
Just flashed iHackers V1.1-CR last night by following 100% the tutorial:
CR-Link: http://forum.xda-developers.com/showthread.php?t=2539008
HowTo:
Install Oficial FTF for Firmware 14.1.G.1.534.
Root Your Phone Using VRoot or KingoApp Root.
Backup TA Partition.
Copy the ROM to External SDCard.
Install Dual Recovery for LB.
Reboot into Recovery.
Make Sure to do a Wipe Data/Factory Reset before Installing the ROM.
Start the Installation. (Install Zip >> Choose Zip for External SDCard).
Switch Off Your Phone (Do Not Reboot). Select No to Disable Flash Recovery Confirmation.
Install Kernel.ftf .257 C6903 or Kernel.ftf .257 C6902 with Flashtool
Reboot and Enjoy.
I did as following:
- installed ADB-drivers
- installed Kingo-Root
- installed Flashtool-drivers
- installed Flashtool
- unpacked Dual-CWM-files
- unpacked TA-Backup
- unbox Z1
- boot
- check firmware (was something about 51x or so)
- downloaded firmware 534
- started Z1 within Flashmode
- connected Z1 with USB-cable to PC
- pressed 'volume -* + green LED blinked
- started installed 'Flashtool'
- pressed the 'Flash'
- picked 'Flashmode'
- picket 534-firmwarefile
- flashed
- unplugged cable
- reboot
- set up google-account
- DID not made OTA-Update
- stopped Auto-App-restore from Google Play
- went to XPERIA-conectivity-options
- PC-Compagnion-install disabled
- picked correct USB-connection-modus
- ticket allow unknown source-install
- ticket USB-debugging within developer-menu
- started Kingo
- plugged Z1 with USB-cable
- waited till driver/stuff was synched
- 'Root'-option was able to be clicked
- clicked
- 'Root succeeded' appears
- did an TA-Backup and ticked SuperSu-request while backing up
- put iHackers V1.1 onto external SD-card
- went to 'Dual-CWM'-folder and double-clicked 'Run.bat'
- CWM-window appeared
- clicked 1 (= SuperSU)
- once done, Z1 rebooted into recovery
- rebooted into recovery once again
- did complete Nandroid-backup
- did Wipe Data, factory Reset + Davlik
- installed ROM by using my options I would have to be installed
- installed 257-Kernel with Flashtool -> Flashmode -> pickde Kernelfile -> flashed
- Reboot
- installed ALL needed apps
- did ALL settings I would like to use
ISSUES:
1) Dual-CWM:
- has gone -> tried to re-install -> failed -> 'Waiting for Device' for a long time without any progress
2) Camera:
- while ticking 'camera' it shows message: 'Sorry but camera was shut down' -> OK
HOW TO GET DUAL-CWM BACK?
HOW TO GET CAMERA BACK TO NORMAL?
Once those two issues are solved, HOW TO GET NEW iHACKERS V1.2 INSTALLED WITHOUT GETTING THOSE TWO ISSUES AGAIN?
Thanks a lot,
DES75

Did you unlock your bootloader? that can explain the camera issue. btw you should post of the IHackers Thread not create your own thread in general section

1) downgrade and try again, this time flash the .zip for dual recovery AFTER flashing the rom and BEFORE rebooting (EDIT before trying that, make sure you have granted ADB shell root access in superuser app)
2) Clear data in settings/app/camera common

Morlock O said:
Did you unlock your bootloader? that can explain the camera issue. btw you should post of the IHackers Thread not create your own thread in general section
Click to expand...
Click to collapse
Hi!
I did all written stuff! I didn't unlock BL at all! Within all those stuff, nothing appeared to open BL!
OR
Is there an option within FLASHTOOL which will open BL while flashing Firmware and/or 257-Kernel?
BTW:
I'm not allowed to post within iHackers-thread!
Thx + BR,
DES75

DESASTER75 said:
Is there an option within FLASHTOOL which will open BL while flashing Firmware and/or 257-Kernel?
Click to expand...
Click to collapse
If you do not know the answer to that I would you suggest you stay away from unlocking the bootloader until you have learned a few basics

gregbradley said:
If you do not know the answer to that I would you suggest you stay away from unlocking the bootloader until you have learned a few basics
Click to expand...
Click to collapse
Hi!
How to do downgrade!
thx

DESASTER75 said:
Hi!
How to do downgrade!
thx
Click to expand...
Click to collapse
Flash a 534 FW in flashtool, you did it before on your list

gregbradley said:
Flash a 534 FW in flashtool, you did it before on your list
Click to expand...
Click to collapse
534 flah
something to umcheck within flashtool
after flash, how to proceed to het Ihackers installed

DESASTER75 said:
534 flah
something to umcheck within flashtool
after flash, how to proceed to het Ihackers installed
Click to expand...
Click to collapse
Like this
DESASTER75 said:
Hi!
- started Z1 within Flashmode
- connected Z1 with USB-cable to PC
- pressed 'volume -* + green LED blinked
- started installed 'Flashtool'
- pressed the 'Flash'
- picked 'Flashmode'
- picket 534-firmwarefile
- flashed
- unplugged cable
- reboot
- set up google-account
- DID not made OTA-Update
- stopped Auto-App-restore from Google Play
- went to XPERIA-conectivity-options
- PC-Compagnion-install disabled
- picked correct USB-connection-modus
- ticket allow unknown source-install
- ticket USB-debugging within developer-menu
- started Kingo
- plugged Z1 with USB-cable
- waited till driver/stuff was synched
- 'Root'-option was able to be clicked
- clicked
- 'Root succeeded' appears
- did an TA-Backup and ticked SuperSu-request while backing up
- put iHackers V1.1 onto external SD-card
- went to 'Dual-CWM'-folder and double-clicked 'Run.bat'
- CWM-window appeared
- clicked 1 (= SuperSU)
- once done, Z1 rebooted into recovery
- rebooted into recovery once again
- did complete Nandroid-backup
- did Wipe Data, factory Reset + Davlik
- installed ROM by using my options I would have to be installed
Before rebooting and after flashing the rom flash this Z1-lockeddualrecovery2.7.43-BETA.zip (7.58MB) from here
- installed 257-Kernel with Flashtool -> Flashmode -> pickde Kernelfile -> flashed
- Reboot
- installed ALL needed apps
Click to expand...
Click to collapse

gregbradley said:
Like this
Click to expand...
Click to collapse
Hi!
So just do the whole procedure (beginning from first line) once again? It's not the prob, just want to be 100% safe!
And after that, you think that ...
- Dual-CWM will be installed
- Camera-issue will have been gone
- iHackers V1.2 will be installed
Thx

DESASTER75 said:
Hi!
So just do the whole procedure (beginning from first line) once again? It's not the prob, just want to be 100% safe!
And after that, you think that ...
- Dual-CWM will be installed
- Camera-issue will have been gone
- iHackers V1.2 will be installed
Thx
Click to expand...
Click to collapse
There is no need to do it all again, but the issue will be gone if you flash that file when I say and if you clear data in settings/app/camera common

gregbradley said:
There is no need to do it all again, but the issue will be gone if you flash that file when I say and if you clear data in settings/app/camera common
Click to expand...
Click to collapse
Hi!
1) So I should use Flashtool to get this *.zip flashed onto Z1 NOW or should it be flashed onto Z1?
2) Already cleaded data from 'camera common' but still same camera-prob
Thanks for your great support

1) Use flashtool to flash 534
2) Root it
3) Let it update OTA
4) Install DualRecovery from here
5) Enter Recovery, factory reset, clear cache, clear dalvik.
6) Follow the installation guide to install the rom of your choice. The only thing to do differently is AFTER flashing the rom.zip and BEFORE rebooting flash the .zip file I mentioned in the earlier post.
6) Reboot
7) Done

gregbradley said:
1) Use flashtool to flash 534
2) Root it
3) Let it update OTA
4) Install DualRecovery from here
5) Enter Recovery, factory reset, clear cache, clear dalvik.
6) Follow the installation guide to install the rom of your choice. The only thing to do differently is AFTER flashing the rom.zip and BEFORE rebooting flash the .zip file I mentioned in the earlier post.
6) Reboot
7) Done
Click to expand...
Click to collapse
Hi!
Sorry, I'm really a bit nooby and just want to be 100% safe!
1) Use flashtool to flash 534 (connect Z1 with PC, start flashtool, flash, Flashmode, pick 534-firmware, flash)
1-2) reboot
2) Root it (Kindo)
2-1) reboot
3) Let it update OTA (just download OTA + install)
4) Install DualRecovery (file name: ZU-lockeddualrecovery2.7.42-BETA.windows.zip) - (unpack on PC, double-click *.bat, install by using 'supersu')
4-1) reboot and hold 'Volume +'
5) Enter Recovery, factory reset, clear cache, clear dalvik.
5-1) iHacker 1.2 on external card
5-2) install zip from ... + follow instructions
6) Follow the installation guide to install the rom of your choice.
6-1) NO REBOOT
6-2) stay in recovery and install zip from external card and flash the 'Z1-lockeddualrecovery2.7.42-BETA.zip''
6) Reboot
7) Done
That's it?
Please finally confirm,
DES75

yes

gregbradley said:
yes
Click to expand...
Click to collapse
you are probably the most patient person on a forum I ever met.

jontr said:
you are probably the most patient person on a forum I ever met.
Click to expand...
Click to collapse
I have my moments
Sent from my C6903 using XDA Premium 4 mobile app

Hello!
I did like following but got problem (marked in red)! Do someone know how to get that fixed?
1) Use flashtool to flash 534 (connect Z1 with PC, start flashtool, flash, Flashmode, pick 534-firmware, flash)
1-2) reboot
2) Root it (Kindo)
2-1) reboot
3) Let it update OTA (just download OTA + install)
4) Install DualRecovery (file name: ZU-lockeddualrecovery2.7.42-BETA.windows.zip) - (unpack on PC, double-click *.bat, install by using 'supersu')
4-1) reboot and hold 'Volume +'
5) Enter Recovery, factory reset, clear cache, clear dalvik.
RECOVERY IS NOT ABLE TO LOCATE/GET FILE FROM EXTERNAL SD!!! ALL FILES ARE ON EXTERNAL SD BUT RECOVERY SHOWS EXTERNAL SD WITH 0BYTES!!! SO HOW TO GET MY EXTERNAL SD WORKING WELL???
BTW (before someone is asking):
The external SD already checked on PC and on PC, on an EEEPC and on an other smartphone, that SD is working well!
would like to proceed the following steps, too:
5-1) iHacker 1.2 on external card
5-2) install zip from ... + follow instructions
6) Follow the installation guide to install the rom of your choice.
6-1) NO REBOOT
6-2) stay in recovery and install zip from external card and flash the 'Z1-lockeddualrecovery2.7.42-BETA.zip''
6) Reboot
7) Done
Thanks a lot for your kind support and have a nice weekend,
DES75

Just put the required file on the internal sdcard...

gregbradley said:
Just put the required file on the internal sdcard...
Click to expand...
Click to collapse
Hi!
That's not working, too!
Anyone an other idea?
Thx,
DES75

[Rom] [TCL S960/Alcatel - Idol x+] - Miui 8 Port - Unofficial (Updated 30/Jul/2016)

Hi All,
***MIUI 8 is now operational on our TCL_S960!
I managed to get it running on TCL S960 (IDOL X+),
Here's my work... (I am not a developer but I followed some instructions online and was able to make it at least for me...)
Probably there will be bugs - so let me know
I'll try to fix what I know...
If you want to use my work elsewhere, you must request in advance and make sure that credits goes to the correct people....
Supported Languages:
All languages that are supported by Xiaomi.EU roms.
Credits:
Xiaomi.eu - for the translations and guides.
Latest version Download links:
Android File Host: (WIP)...
30/Jul/2016 -
Older Versions (Miui8)
24/Jul/2016 (fixes to 14/7/2016) - https://www.androidfilehost.com/?fid=24651429356503158
14/Jul/2016 - https://www.androidfilehost.com/?fid=24591000424947416
7/7/2016 - https://www.androidfilehost.com/?fid=24591020540823614
30/6/2016 - https://www.androidfilehost.com/?fid=24591020540823614
Older Versions (MIUI7):
26/5/2016 - https://www.androidfilehost.com/?fid=24566454284190288
19/5/2016 - https://www.androidfilehost.com/?fid=24533103863143479
12/05/2016 - https://www.androidfilehost.com/?fid=24533103863139453
05/05/2016 - https://www.androidfilehost.com/?fid=24533103863137243
28/4/2016 - https://www.androidfilehost.com/?fid=4996500813288309006
14/4/2016 - https://www.androidfilehost.com/?fid=24499762636000772
7/4/2016 - https://www.androidfilehost.com/?fid=24459283995317117
31/3/2016 - https://www.androidfilehost.com/?fid=24459283995310311
17/3/2016 - https://www.androidfilehost.com/?fid=24459283995303903
XdaDevDB:
Installations:
Important:
Prior to any install make sure to backup your existing ROM. (TWRP backup?) if you wish to backup your SMS/Contacts there are a bunch of apps that can do it... (MobilePro is an example)
Backup your IMEI just in case... (Use MobileUncle or similar)
If you chose to install - your warranty is void.
I am not responsible for any damage that may be caused by this ROM.​
Did you make a backup? - Save your backup on a PC...
First time transition to MIUI8 requires re-partition of the phone to increase system size.
you will need a different recovery to finalise the process.
1. Copy the Repartition zip file to phone.
2. Copy the Philz recovery to your phone.
3. Install Philz recovery.
4. Reboot into recovery
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
8. Restore your backup.
9. Boot the phone.
10. Copy the MIUI8 install file to phone.
11. Click on the 3 dots
12. Chose select update file --> select your copied file.
13. Phone will Reboot and install.
If the above version does not work, you will need to use SP-Flash tools to install the EBR1, EBR2 files in the zip.
Then continue from step 6 (Format partitions)
if coming from another rom/ Fresh install
as ususal... - I recomend a total wipe, but it is not a must....
Wipe Cache, Dalvik, Data, System, custpack.
Install Rom from internal memory
reboot.​
Wait patiently - it will take 3-4 minutes on the 1st boot.
To update (existing Miui Rom):
Copy rom to SD Card
Open updater app.
Click on the 3 dots
Chose select update file --> select your copied file.
Reboot​
*** Make sure to disable Automated OTA... as it is based on Redmi Note 3G MTK, and I can't promise to keep this forever...
Recovery:
I used TWRP 2.8.7.0 for TCL S960
Other recoveries:
CWM - Link
TWRP 2.6.3 - Link
If you like my work feel free to buy me beer Donation link
Known Issues:
Default theme - some icons are missing - Use another theme icon set...
When making full wipe - unable to login to MiAccount - Install 6.1.28 version --> login, then update to latest.
TouchAssistant APK exceeds the space of System partition - I removed it, you can install it manually after the rom installs. - Link solved after repartition.
31/3/16 - Additional settings FC - Fixed.
12/05/2016 - Fixed wallpaper carousel FC when unlocking device
Some screenshots:
Miui8:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Miui7:
XDA:DevDB Information
TCL S960/Alcatel (IdolX+), ROM for the Android General
Contributors
hellfreezover, Xiaomi.eu
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: MIUI
Version Information
Status: Beta
Current Beta Version: 26-05-2016
Beta Release Date: 2016-07-15
Created 2016-01-22
Last Updated 2016-07-30

Reserved
Changelog: (Latest Version)
24/7/2016 - still based on 6.7.14
Fixed Settings menus.
Enabled "Button mode"
Enabled additional settings to split the menu bar.
Fixed MIUI version to 8...
System seems to be running faster...
Older versions:
14/7/2016
System
Fix - Fingerprint issues (07-12)
Fix - Fingerprint scanner made the device freeze and reboot (07-12)
Lockscreen, Status Bar, Notification Bar
Optimization - Clickable arrow for Wi-Fi (07-12)
Optimization - A prompt about entering password and activating fingerprint after rebooting the device (07-13)
Fix - Customized carrier name isn't shown in Second space (07-12)
Home screen
Optimization - Landscape mode for Task manager (07-08)
Optimization - Task Manager stability (07-13)
Fix - Issues with wallpaper when switching to Second space (07-13)
Delete - Home screen Music widget (07-13)
Gallery
New - Delete directly from the screenshot preview page (07-12)
Optimization - Adjusted size for the button which creates new albums (07-12)
Optimization - "Show original" option appears only on cloud or optimized items (07-12)
Optimization - Double tap to zoom in, swipe up without entering sharing mode (07-12)
Optimization - When auto-rotate is off in Gallery, it won't influence the rest of the system (07-13)
Fix - Scrolling screenshot issues in Notes and Mail (07-12)
Fix - Couldn't go back to the original photo after making a screenshot or finishing editing/sharing it (07-12)
Fix - Couldn't pick up calls while making Scrolling screenshots (07-13)
Fix - Enter system app while editing a scrolling screenshot in the OOB flow (07-13)
Delete - Removed Edit option for GIF images (07-12)
Weather
Fix - Issues with curves in forecasts (07-13)
Optimization - Set C/F in settings (07-13)
7/7/2016
Highlights
New - Saved and available Wi-Fi networks appear first in the list (07-05)
New - After a permission is restricted, a clickable notification is sent to the user which can restore permissions (07-05)
Lock Screen, Status Bar, Notification Bar
New - Animation of WiFi connection (07-07)
Optimization - separate "Ringtone and Vibration" permission in Notification （07-07）
Fix - Switching notification bar style in landscape view issues (07-07)
Fix - In Second Space, enter Mi Home in lock Screen issue (07-07)
Desktop
Optimization - Restore app uninstallation sound effect (07-07)
Fix - Recent app tray, long press to enter wrong app info page issue (07-07)
Fix - Recent app tray, switching view mode issues (07-07)
Settings
New - Saved and available Wi-Fi networks appear first in the list (07-05)
Clock / Calculator
Optimization - "Shutdown alarm", "Set default alarm sound" moved up In Clock settings. (07-01).
30/6/2016 - Miui 8.
26/5/2016 -
Gallery
New - Deleting synced photos from internal storage without deleting from Mi Cloud (05-25)
Cleaner
Optimization - Accessibility support (05-24)
Fix - FC issues (05-24)
19/05/2016 -
System
Optimization - Background CPU processes caused performance issues (05-16)
Optimization - Delayed response for charger's notifications (05-19)
Fix - Wireless display caused reboots (05-19)
Fix - Read mode appeared more red than it should be (05-19)
Fix - Draining battery while using GPS in some cases (05-19)
Fix - Bluetooth turned on automatically with the device (05-19)
Settings
New - Introducing Shortcut menu. Check out the new MIUI 8 feature early. You can turn it on in Additional settings. (05-17)
TouchAssistant must be installed post rom.
Mi Cloud
New - Added "Back up now" feature for fast backups (05-19)
12/05/2016 -
System
Optimization - System storage UI (05-05)
Optimization - Background processes kept CPU busy and lead to performance issues (05-09)
Fix - Issues with adding fingerprint (05-05)
Fix - Problems with sound when listening to some songs using earphones (05-05)
Fix - Issues with video chats in some cases (05-05)
Fix - Sound disappeared in long phone conversations (05-05)
Fix - Fingerprint unlock didn't respond in some cases (05-05)
Backup
New - Optimizing transferring rate in File Transfer (05-09)
05/05/2016 -
System
Optimization - System storage UI (05-05)
Fix - Issues with adding fingerprint (05-05)
Fix - Problems with sound when listening to some songs using earphones (05-05)
Fix - Issues with video chats in some cases (05-05)
Fix - Sound disappeared in long phone conversations (05-05)
Fix - Fingerprint unlock didn't respond in some cases (05-05)
Security
New - Added on/off switch for App lock (05-03)
New - Customized settings for App lock (05-03)
28/4/2016 -
System
Optimisation - Improved speed and performance for devices which have been used for a long time (04-27)
Weather
New - New white design (04-27)
Cleaner
New - New design for Cleaner (04-27)
Gallery
New - Progress list for syncing with Mi Cloud (04-27)
Optimization - Added a prompt notifying about Mi Cloud trash bin when deleting photos for the first time (04-27)
Optimization - Improved sharpness for big photos (04-27)
Security
New - Fingerprint support for App lock in Redmi 3 Pro (04-27)
14/4/2016 -
System
Optimization - Improved algorithms for Silent and DND modes to be used at the same time. (04-13)
Fix - Storage leaks lead to performance problems (04-08)
Fix - Security Center FC in Hebrew Language
7/4/2016 -
Lockscreen, Status Bar, Notification Bar
Optimization - Improved order of switches in notification shade (04-06)
Fix - Music lock screen appeared when a game was running in the background (04-06)
Settings
Optimization - Improved algorithms for international roaming (04-06)
Mi Account
New - Added more items to personal info (04-06)
Cleaner
Optimization - Press and hold to add items to exceptions (04-06)
Optimization - Fixed problems with performance after clean-ups (04-06)
Mi Cloud
Fix - Couldn't find device or sign in to Mi Account due to wrong system time (04-06)
Fix - Fixed issues with incorrect time in backup lists (04-06)
Bug fixes by Xiaomi.
Fixed Additional settings FC.
31/3/2016 general bug fixes by Xiaomi.
24/3/2016
System
Optimization - Apps open faster, system animations work smoother (03-17)
Optimization - Increased image processing speed for image decryption database (03-22)
Fix - Problems with performance after switching from mobile data to Wi-Fi (03-18)
Backup
In some cases Mi Mover stopped working after the connection was established (03-18)
Clock / Calculator
New - Option for deleting an alarm automatically after it was used if it had been set to go off only once (03-23)

thank you
thank you for this awesome Rom. but the sound setting under audio force closes im on viper4android

Did you try sound settings without viper?
For me it works... but I did had to do a clean install...
Sent from my ASUS_Z00XS using XDA Free mobile app

Hi i just tried your rom bt i am stuck at mi login.. It says checking find device status and stays there only.... What to do now...?

santhosh5639 said:
Hi i just tried your rom bt i am stuck at mi login.. It says checking find device status and stays there only.... What to do now...?
Click to expand...
Click to collapse
Try using an older version like 6.1.28, then log in to miui, then update without full wipe.
I have reported this to miui, it is under discussion...
Sent from my ASUS_Z00XS using XDA Free mobile app

Updated OP with the link to 6.1.28 version
Sent from my ASUS_Z00XS using XDA Free mobile app

Updated OP with MIUI 8 for TCL.
Sent from my ASUS_Z00XS using XDA Free mobile app

Bricking my phone
Dear Hellfreezover,
I tried to install your ROM, but I bricked my phone.
(I installed ROM before several times, I never made mistake, but now I did it.)
When I used SP flashtool I selected "Firmware upgrade" option instead of "Download only" option (I never did it before) and I started to install TWRP recovery but I got error message.
Now I can not use my phone, but I know that I can be repairable just I need important files....
...these all files or just some of them:
- PRELOADER
-MBC
-EBR1
-UBOOT
-BOOTIMG
-RECOVERY
-SEC-RO
-LOGO
-EBR2
-CUSTPACK
-MOBILE_INFO
-ANDROID
-CACHE
-USRDATA
Now I get this error message when I try to update the recovery.
Could u send me these files? Or could you link me URL where I can find these files?
Sorry for disturbing, I shame on me, I did ROM install before without mistake, but now I screwed up...
Regards,
Peter (Hungary)

I am not at home now,
I have the files...
You can get searching TCL multi language rom 70 languages and download it through SP flash tools, then, repartition and finally the rest....
Sent from my ASUS_Z00XS using XDA Free mobile app

Olympos.81 said:
Dear Hellfreezover,
I tried to install your ROM, but I bricked my phone.
(I installed ROM before several times, I never made mistake, but now I did it.)
When I used SP flashtool I selected "Firmware upgrade" option instead of "Download only" option (I never did it before) and I started to install TWRP recovery but I got error message.
Now I can not use my phone, but I know that I can be repairable just I need important files....
...these all files or just some of them:
- PRELOADER
-MBC
-EBR1
-UBOOT
-BOOTIMG
-RECOVERY
-SEC-RO
-LOGO
-EBR2
-CUSTPACK
-MOBILE_INFO
-ANDROID
-CACHE
-USRDATA
Now I get this error message when I try to update the recovery.
Could u send me these files? Or could you link me URL where I can find these files?
Sorry for disturbing, I shame on me, I did ROM install before without mistake, but now I screwed up...
Regards,
Peter (Hungary)
Click to expand...
Click to collapse
Check your PM - I sent you a link with all files needed...

Updating problem
hellfreezover said:
Check your PM - I sent you a link with all files needed...
Click to expand...
Click to collapse
Thank you very much, I could unbrick my mobile! :good: :fingers-crossed: :highfive:
I tried to upgrade my ROM according to your instructions, but I could not do it.
What I did:
1. Unbrick my mobile with your files.
2. I copied your MIUI8 ROM, Repartition and Philz zip files to my mobile.
3. In SP Flash I downloaded Philz.zip what contains recovery.
4. I rebooted my mobile in recovery mode.
5. I installed the Repartition zip. (...but I think it was unnecessary, because I did it when I unbricked my mobile.)
6. I tried to reboot my mobile into reocvery mode, but it was not available (after repartition.)
7. I had to download your TWRP 2.8.7.0 recovery to my mobile via SP-Flash tool.
8. I tried to reboot, but same situation: this recovery also was not available.
9. I had to download other 2.6.3 or 2.7.0 TWRP recovery to my mobile.
10. I could reach recovery from that point.
11. I installed your MIUI 8 rom, and it was successful according to message.
12. In spite fo this the ROM can not start: "Idol X+" is appearing and go away and black screen is flashing without logo or sound.
What do I do in wrong way?
Otherway, before I unbricked my mobile and after also I tried to upgrade my ROM to your MIUI 8 version in different way.
Then I had different problem: when I did the uploading of your ROM into my exist differnet rom (like offical ROM, LeWa ROM or modded MIUI 5 rom) in recovery mode the installation was finally failed, unsuccessful: "/data" directory can not reachable/readable/writeable or somehting else.
(I have screenshot, I will share.)
Regards,
Peter

Olympos.81 said:
Thank you very much, I could unbrick my mobile! :good: :fingers-crossed: :highfive:
I tried to upgrade my ROM according to your instructions, but I could not do it.
What I did:
1. Unbrick my mobile with your files.
2. I copied your MIUI8 ROM, Repartition and Philz zip files to my mobile.
3. In SP Flash I downloaded Philz.zip what contains recovery.
4. I rebooted my mobile in recovery mode.
5. I installed the Repartition zip. (...but I think it was unnecessary, because I did it when I unbricked my mobile.)
6. I tried to reboot my mobile into reocvery mode, but it was not available (after repartition.)
7. I had to download your TWRP 2.8.7.0 recovery to my mobile via SP-Flash tool.
8. I tried to reboot, but same situation: this recovery also was not available.
9. I had to download other 2.6.3 or 2.7.0 TWRP recovery to my mobile.
10. I could reach recovery from that point.
11. I installed your MIUI 8 rom, and it was successful according to message.
12. In spite fo this the ROM can not start: "Idol X+" is appearing and go away and black screen is flashing without logo or sound.
What do I do in wrong way?
Otherway, before I unbricked my mobile and after also I tried to upgrade my ROM to your MIUI 8 version in different way.
Then I had different problem: when I did the uploading of your ROM into my exist differnet rom (like offical ROM, LeWa ROM or modded MIUI 5 rom) in recovery mode the installation was finally failed, unsuccessful: "/data" directory can not reachable/readable/writeable or somehting else.
(I have screenshot, I will share.)
Regards,
Peter
Click to expand...
Click to collapse
Hi,
I think what you missed is the format of system, data, cache - after the installation of re partition, in Philz recovery.
also - you need to verify that your SD-Data is mounted correctly (sometimes in Philz it adds a 0, and then you will not find files there...
You need to change the mount location before you reboot recovery.
Sorry I have no pictures for this, but it is in the menu...
if the above does not work
Try extracting EBR1, EBR2 from repartition file, install them with Philz recovery through SP-Flash tool.
reboot into recovery --> format data, system, cache - check again where SD is mounted...
Reboot recovery
Install rom - if works great if not:
Install TWRP 2.8.7
Place new ROM and install
let me know if this works for you.
The 1st install will take a few minutes until you will see something on the phone...

hellfreezover said:
Hi,
I think what you missed is the format of system, data, cache - after the installation of re partition, in Philz recovery.
also - you need to verify that your SD-Data is mounted correctly (sometimes in Philz it adds a 0, and then you will not find files there...
You need to change the mount location before you reboot recovery.
Sorry I have no pictures for this, but it is in the menu...
if the above does not work
Try extracting EBR1, EBR2 from repartition file, install them with Philz recovery through SP-Flash tool.
reboot into recovery --> format data, system, cache - check again where SD is mounted...
Reboot recovery
Install rom - if works great if not:
Install TWRP 2.8.7
Place new ROM and install
let me know if this works for you.
The 1st install will take a few minutes until you will see something on the phone...
Click to expand...
Click to collapse
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
---------- Post added at 05:49 PM ---------- Previous post was at 05:02 PM ----------
Olympos.81 said:
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
Click to expand...
Click to collapse
My problem is now:
/E: Unable to mount '/system'
/E: Unable to mount '/protect_s'
/E: Unable to mount '/protect_f'

Olympos.81 said:
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
---------- Post added at 05:49 PM ---------- Previous post was at 05:02 PM ----------
My problem is now:
/E: Unable to mount '/system'
/E: Unable to mount '/protect_s'
/E: Unable to mount '/protect_f'
Click to expand...
Click to collapse
you can change the mount location in Philz recovery...
6.a. - check to see where the SDCARD data directory is mounted(\data or \data\0), if it is the \data\0 - change it back to \data in the philz recovery, otherwise - upgrades will not work in TWRP.

I followed your instruction, please see my notes and check my pictures:
1. Copy the Repartition zip file to phone.
OK!
2. Copy the Philz recovery to your phone.
OK!
Please see it, I copied everything to my phone from Window 10, so these files copied into /data directory:
http://kepfeltoltes.hu/160717/factory_directory_www.kepfeltoltes.hu_.jpg
3. Install Philz recovery.
I did it from factory recovery:
http://kepfeltoltes.hu/160717/IMG_1596_www.kepfeltoltes.hu_.jpg
(You can not see the "Philz*.zip" file because of bad quality of picture, but belive me, it is.
4. Reboot into recovery
OK!
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
I did it:
http://kepfeltoltes.hu/160717/IMG_1597_www.kepfeltoltes.hu_.jpg
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
I did not need the format, because your Repartition.zip was installed successfully, and format was done by Repartition.zip as you requested:
Begin:
http://kepfeltoltes.hu/160717/IMG_1598_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1599_www.kepfeltoltes.hu_.jpg
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
Because of your Repartition procedure all files were deleted from /data directory so I had to upload TWRP 2.8.7.0 recovery from SP-Flash tool to mobile:
http://kepfeltoltes.hu/160717/Recovery_www.kepfeltoltes.hu_.jpg
8. Restore your backup.
(I do not know what is it...maybe I make a mistake here. I skiped this step.)
9. Boot the phone.
OK.
10. Copy the MIUI8 install file to phone.
Negative. There is no operation system, because Repartition.zip formatted /data and /system directory.
Furthermore, Internal storage is 0 from the Repartition.zip is completed.
http://kepfeltoltes.hu/160717/IMG_1603_www.kepfeltoltes.hu_.jpg
11. Click on the 3 dots
Negative.
12. Chose select update file --> select your copied file.
I had to use OTG-USB cable and chose the MIUI 8 rom in TWRP 2.8.7.0
But from now due to unavailable /data, /cache / etc - internalt storage is 0 - the installation however started, but failed.
Begin:
http://kepfeltoltes.hu/160717/IMG_1604_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1605_www.kepfeltoltes.hu_.jpg
13. Phone will Reboot and install.
Negative.
Where do I make mistake?

Olympos.81 said:
I followed your instruction, please see my notes and check my pictures:
1. Copy the Repartition zip file to phone.
OK!
2. Copy the Philz recovery to your phone.
OK!
Please see it, I copied everything to my phone from Window 10, so these files copied into /data directory:
http://kepfeltoltes.hu/160717/factory_directory_www.kepfeltoltes.hu_.jpg
3. Install Philz recovery.
I did it from factory recovery:
http://kepfeltoltes.hu/160717/IMG_1596_www.kepfeltoltes.hu_.jpg
(You can not see the "Philz*.zip" file because of bad quality of picture, but belive me, it is.
4. Reboot into recovery
OK!
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
I did it:
http://kepfeltoltes.hu/160717/IMG_1597_www.kepfeltoltes.hu_.jpg
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
I did not need the format, because your Repartition.zip was installed successfully, and format was done by Repartition.zip as you requested:
Begin:
http://kepfeltoltes.hu/160717/IMG_1598_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1599_www.kepfeltoltes.hu_.jpg
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
Because of your Repartition procedure all files were deleted from /data directory so I had to upload TWRP 2.8.7.0 recovery from SP-Flash tool to mobile:
http://kepfeltoltes.hu/160717/Recovery_www.kepfeltoltes.hu_.jpg
8. Restore your backup.
(I do not know what is it...maybe I make a mistake here. I skiped this step.)
9. Boot the phone.
OK.
10. Copy the MIUI8 install file to phone.
Negative. There is no operation system, because Repartition.zip formatted /data and /system directory.
Furthermore, Internal storage is 0 from the Repartition.zip is completed.
http://kepfeltoltes.hu/160717/IMG_1603_www.kepfeltoltes.hu_.jpg
11. Click on the 3 dots
Negative.
12. Chose select update file --> select your copied file.
I had to use OTG-USB cable and chose the MIUI 8 rom in TWRP 2.8.7.0
But from now due to unavailable /data, /cache / etc - internalt storage is 0 - the installation however started, but failed.
Begin:
http://kepfeltoltes.hu/160717/IMG_1604_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1605_www.kepfeltoltes.hu_.jpg
13. Phone will Reboot and install.
Negative.
Where do I make mistake?
Click to expand...
Click to collapse
First you missed your previous MIUI backup...
but that is not the issue...
I would recommend formatting the /system, /data, /cache partitions - even though that it shoes success...
Then reboot recovery (to PHILZ)
Make sure your SDCARD mount is without the "0"...
Try to flash ROM using ADB sideload, in PHILZ touch...
if it doesn't work, try installing with TWRP 2.6.3 recovery.
I shared what I did on my phone and it worked...
If all the above fails - try installing EBR1, EBR2 from SP-Flash tool, then Recovery (Philz), Format cache, system, data, then install rom through PHILZ or TWRP...

Somebody could install this rom as Hellfreezover described?
---------- Post added at 09:23 PM ---------- Previous post was at 09:05 PM ----------
hellfreezover said:
First you missed your previous MIUI backup...
but that is not the issue...
I would recommend formatting the /system, /data, /cache partitions - even though that it shoes success...
Then reboot recovery (to PHILZ)
Make sure your SDCARD mount is without the "0"...
Try to flash ROM using ADB sideload, in PHILZ touch...
if it doesn't work, try installing with TWRP 2.6.3 recovery.
I shared what I did on my phone and it worked...
If all the above fails - try installing EBR1, EBR2 from SP-Flash tool, then Recovery (Philz), Format cache, system, data, then install rom through PHILZ or TWRP...
Click to expand...
Click to collapse
Dear Hellfreezover!
I am sure, that you are advanced or professional developer and you have more experience about mobiles and ROMS, but now, I think what you have written in instructions is different as you have done it in real life.
...or someting is wrong with ROMs.
So...
I tried to follow your instruction several times and when I have reached that point that there were no error message at the beginning of installation of ROM, finally, it was also unsucessfull:
- begining: http://kepfeltoltes.hu/160717/IMG_1592_www.kepfeltoltes.hu_.jpg
- ending: http://kepfeltoltes.hu/160717/IMG_1593_www.kepfeltoltes.hu_.jpg
(See, there is no error message as before like "unmount /data" or somthing else...)

I am hardly a professional....
I used philz, and my files the way I described...
There may be some issues, I had miui Rom installed before...
And there is another guy that did the repartition process... using SP flash tools...
You can try maybe replacing the EBR1, EBR2 in the original Rom and choose firmware update....
Then install the twrp recovery and the Rom...

hellfreezover said:
I am hardly a professional....
I used philz, and my files the way I described...
There may be some issues, I had miui Rom installed before...
And there is another guy that did the repartition process... using SP flash tools...
You can try maybe replacing the EBR1, EBR2 in the original Rom and choose firmware update....
Then install the twrp recovery and the Rom...
Click to expand...
Click to collapse
Now I tried again and again, I followed again your every intsructions and I tried the following ROMs with TWRP 2.6.3.0:
- xiaomi.eu_multi_TCL_S960_6.7.14_v8-4.4 (latest) - Failed
- xiaomi.eu_multi_TCL_S960_6.6.30_v8-4.4 (previous) - Failed
- xiaomi.eu_multi_TCL_S960_6.3.10_v7-4.4 - Success!
Now, the MIUI 7 is running.
I am trying to upgrade to latest MIUI 7 and after to MIUI 8....
...but I am afraid: this will be again failed.

Xperia X Performance root 7.1.1 + PS4 remote play/android pay OK+ Safetynet OK +DRM

I have done the update to 7.1.1 with Magisk v13beta https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 . The steps below still more or less works on Android 7.1.1
--------------
After playing with the Xperia XP for 2 days over weekend, I finally managed to root it with PS4 remote play and Safetynet working. (If Safetynet is working, games like Pokemon and app like Android pay should work with rooted phone as well)
Before you do anything, backup the TA partition first. You have to downgrade back to version 6.0.1 to backup the TA partition. Flash your phone back to 6.0.1 first. (If you don't know how to flash a firmware, https://forum.xda-developers.com/xperia-xz/how-to/how-to-flash-firmware-using-flashtool-t3523946)
Download 6.0.1 firmware here. By backing up the TA partition, in case if you want to roll back to stock rom with valid DRM key , you can install the original DRM key back into your phone. You need this if you want your warranty in case you need to fix your phone.
Download and install backupTA_v2
https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Backup TA partition
1) Ensure you have adb access (e.g. drivers installed, install flashtool)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you encounter issue on installing drivers, follow this to disable driver signature first.
https://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
2) Run backupTA.sh (linux) or backupTA.cmd (windows) in the root directory.
3) TA will be saved as TA-ModelNumber-Serial-Timestamp.img in
the backupTA.sh directory.
4. Send this image file to your gmail or something so that your email will permanently keep a copy of this backup TA partition image.
DO NOT GO BEYOND THE LINE BELOW IF YOU CAN'T BACKUP YOUR TA PARTITION.
-----------------
Now, you have done all pre-requisite. We can now start the rooting.
1. unlock phone https://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Get into fastboot mode first by holding down volume up button and plug in USB cable to computer, click BLU
You should type in unlock code which you got it from the above Sony link.
2. flash/upgrade to stock firmware 7.0 if phone is not having stock rom, check all erase on flash. Flash it so that it will have both stock firmware and stock boot image. (don't restart phone after flash).
3. flash the TWRP. fastboot flash recovery f:\path_to_downlaod\TWRP-3.0.2-4-dora.img (Download TWRP here)
Also download XP_AndroPlusKernel_v22.zip . Get the newest version for both app if available.
4. go into twrp install UPDATE-SuperSU-v2.79-20161211114519.zip, reboot (Download https://download.chainfire.eu/696/supersu/ or see attachment)
5. start the phone the first time and get into phone, should find out the phone still not rooted. Check Setting > Display , the Bravia engine should have no effect on your display.
7. go into twrp install Magisk-v12.0.zip, reboot (download https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 or see attachment)
8. start magisk, it will open google play to update magisk. reboot
9. go into twrp , install phh’s SuperUser superuser-r310-beta.zip, reboot (download https://superuser.phh.me/ or see attachment)
10. go into phone, open google play, search and install phh’s SuperUser app
11. run SuperUser app, upper right choose setting, choose Superuser access and then choose Apps and ADB
12. run magisk, 2nd checkbox should be check by now. Should show Properly rooted)
13. run magisk, 1st checkbox click and install Magisk v12 , reboot
14. run magisk, upper left menu click, then choose Downloads,install Sony Framework v1, reboot
15. On reboot, the phone should hang during boot up, on boot loop, hold the volume up button , plug the usb cable to computer, until you see the blue light turn on on the top of the phone, and screen stays black
16. flash the XP_AndroPlusKernel_v22.zip boot image. fastboot.exe flash boot f:\path_to_downlaod\boot.img
17. go back into phone once again, run magisk, choose menu upper left, choose modules, find the file Magisk_RemotePlayEnabler_v1.zip, press and hold on that file to select, and install, reboot (download https://forum.xda-developers.com/apps/magisk/module-ps-remote-play-enabler-t3575876 or see attachment)
18. Enable Magisk Hide in Setting of Magisk...can put the remote play in Magisk hide if remote play doesn't work.
18. go back to phone again, run magisk, all 3 checkbox should be all checked and OK. PS4 remote play should work fine as well with root running on phone.
In case if you need to roll back to stock rom with original TA partition, here is the instruction.
1. Backup all the data as your device will reset and formatted after this process.
2. Rename your backed up TA partition and rename it TAbackup.img
3. Boot into TWRP.
4. Plug your device in your pc via USB and check the connection by the command adb devices in command prompt in your fastboot directory.
5. Now run the command adb push TAbackup.img /data/local/tmp/TAbackup.img
6. Then run adb shell dd if=/data/local/tmp/TAbackup.img of=/dev/block/bootdevice/by-name/TA
7. Now flash Stock ROM via FlashTool and your device will have original DRM and stock ROM and Ta partition.

great work! followed your instructions, worked almost perfectly for me (but I am using marshmallow and didn't need to do the remote play or anything but I'm rooted for now)
for those that might do what I did, if you do appear to be unrooted after flashing the kernel, you'll need to flash MagiskSU back again.
Also you'll need to flash a compatible kernel version for your build.
I wasn't able to get remote play working and didn't need it but I guess if I'd like to use Android pay I'll spend more time figuring that one out. But for most I think this guide is a dummy's guide ( I did it ) and it covers everything clearly

Thank you for the guide, sdugoten! I followed your process to a t and indeed, it helped me achieve the intended result. I appreciate the time you spent writing up this guide.
However, I did have to find a lot of extra information by searching XDA to achieve each step. For example, I found that after step 2 (flashing the new firmware), all that really needs to be done is to flash both the AndroPlus Kernel (by downloading the flashable zip, unzipping it, and flashing the boot.img via "fastboot flash boot boot.img) and TWRP via fastboot. I found that by NOT doing this, my phone would not boot (due to the stock ROM not accepting a custom recovery w/o a custom kernel). From there, reboot into recovery to flash Magisk v12, reboot the device, go through first-time setup, update Magisk Manager, and enable Magisk Hide. At this point, all three checkmarks in Magisk Manager should show up as green, indicating a successful install. This eliminates flashing both SU beta zips. Installing the Sony Framework and RemotePlayEnabler should be OK in the same step as well. I hope this helps! If anyone wants me to write out a detailed guide as to how I went about this, just let me know!

I have done similar steps and able to get XP Performance running on Android v7.1.1 with Magisk v13 beta and Safetynet working

@sdugoten Your DRM fix isn't complete. It's missing the Device Key (DK). Here are instructions how to make one. Important: Once you have created your DK.ftf, you need to use Flashtool 0.9.22.3. Other Flashtool versions don't install it.

Hi, i'm trying to do this tutorial... Everytime i flash something, a write a "diary" of what i'm doing, just in case of problems. and this is that case.....
i have unlocked bootloader, and done root many months ago, never backup TA partition, so i know what it mean, and so, i've skip step 1 and start from 2.
installed flashtool 0.9.23.1
installed adb and fastboot drivers
enabled in developer debug usb and unknow sources and when connected phone to pc, allowed debug to pc, and allowed supersu to adb.
start flashtool
volume up and plug cable, blu led appear, flashtool says me to install driver from driver folder, installed only fastboot and flashtool drivers (i disabled verify of firma driver)
flashtool says device connected in fastboot. i think is not right, then unplug, volume down and plug, flashtool ays device connected in flash mode
click on flash, selected flashmode, selected right folder of .tft, and selected all the checkboes in wipe tab, and then click in flash.
02/009/2017 22:09:11 - INFO - Device connected in flash mode
02/009/2017 22:09:28 - INFO - Selected Bundle for Sony Xperia X Performance(F8131). FW release : 41.2.A.2.199_R2D. Customization : Switzerland Generic_1302-9924
02/009/2017 22:09:28 - INFO - Preparing files for flashing
02/009/2017 22:09:54 - INFO - Please connect your device into flashmode.
02/009/2017 22:09:54 - INFO - Opening device for R/W
02/009/2017 22:09:54 - INFO - Reading device information
02/009/2017 22:09:54 - INFO - Phone ready for flashmode operations.
02/009/2017 22:09:54 - INFO - Opening TA partition 2
02/009/2017 22:09:54 - INFO - Current device : F8131 - CB512AJSMZ - 1302-9940_R3C - 1300-5321_39.2.A.0.417 - GENERIC_39.2.A.0.417
02/009/2017 22:09:54 - INFO - Closing TA partition
02/009/2017 22:09:54 - INFO - Start Flashing
02/009/2017 22:09:54 - INFO - No loader in the bundle. Searching for one
02/009/2017 22:09:55 - INFO - No matching loader found
02/009/2017 22:09:55 - WARN - No loader found or set manually. Skipping loader
02/009/2017 22:09:55 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Bootloader status : ROOTED
02/009/2017 22:09:55 - INFO - Max packet size set to 4M
02/009/2017 22:09:55 - INFO - USB buffer size set to 512K
02/009/2017 22:09:58 - INFO - Parsing boot delivery
02/009/2017 22:09:58 - INFO - No flash script found.
02/009/2017 22:09:58 - INFO - Flash script is mandatory. Closing session
02/009/2017 22:09:58 - INFO - Ending flash session
02/009/2017 22:09:58 - INFO - Flashing finished.
02/009/2017 22:09:58 - INFO - Please unplug and start your phone
02/009/2017 22:09:58 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
02/009/2017 22:09:58 - INFO - Device connected in flash mode.
Tried this 3 times and still not working, So, i've downloaded the stock firmware directly from flashtool, took me 14mins, then retry to flash... i can't flash because the file downloaded is not a tft, and flashtool has extract it in a lot of files..... how can i flash stock rom?!?! i'm wrong?

25agosto said:
installed flashtool 0.9.23.1
Click to expand...
Click to collapse
As I posted one post above you, you need to use Flashtool version 0.9.22.3. Other versions such as 0.9.23.1 won't work.

Hi
8. start magisk, it will open google play to update magisk. reboot
Doesnt work. Google play says App Not Found. Cant update then.
How to proceed ?!
I downloaded the newest magisk manager apk and installed it manually.
Also i try to use magisk v13.3 but Im stuck again here
12. run magisk, 2nd checkbox should be check by now. Should show Properly rooted) -> doesnt show root / how should it be shown? safety net test passed?
13. run magisk, 1st checkbox click and install Magisk v12 , reboot -> wants to install v13.3 when i click checkbock
14. run magisk, upper left menu click, then choose Downloads,install Sony Framework v1, reboot -> framework install keeps crashing magisk manager app. sometimes immediately / sometimes flashes and says magisk not installed + crash
--------------------
Update
I deinstalled SU and magisk app and run magiskuninstaller.
started to do every step again. this time i stay on v12.0 and when install SU app and give permission ADB/APP Magisk Manager first time crashes.
Then i run magisk manager, grant SU rights. Nothing is rooted. Screen looks totally different then your picture....
When i try to install magisk v13.3 via manager following error occurs: boot image patched by other programms / please restore stock boot image
framework install keeps crashing magisk manager app. probably cuz of missing root
now i when i try to run magsikuninstaller.zip via twrp it drops me
!Boot image patched with other programms
cannot uninstall with this uninstaller
----------------------
SEE LATEST POST for updates!
----------------------
please help!
Thank so much !

sdugoten said:
I have done similar steps and able to get XP Performance running on Android v7.1.1 with Magisk v13 beta and Safetynet working
Click to expand...
Click to collapse
see next post

i just found out why all this is happening
i was on newest FW which was wrong
i followed every step an took correct firmware for v22 kernel
magisk manager is no longer on google
then you go install newest version viia APK download but after 5.0 its not more compatible with v12.
so i installed old version of magisk manager 4.3.3 manually
then i get the root thing done BUT NOW im stuck on step 13. cuz when you click install. it wants to download v13.3. and you cant force to install from sd card.
v13.3 wont work with 4.3.3 manager
-------------
update
you can probably mark this thread as outdated cuz the instructions leading nowhere.
i flashed 7.0 clean install. did twrp. did the su flash from step 4
then on step 7 ( i saw you forgot step 6, lol)
i want to install v13.3 instead of v12
to proceed with latest magisk manager.
but its unable to repack boot.img on flashing Error1
also happens with v13.2 and v13.1
so only v12 is working correctly on flashing in twrp - (even I thought the newer v13.3 should be downwards compatible?).
but then you get stuck as described in my very first post with missing manager in play store
how to fix it see following update post
----
update
so when doing the flash from v13.3 with the newest manager installed BEFORE (right after v12 twrp flash step)
THEN it succeed. MEANS
install v12 via twrp. install latest manager. install v13.3 via TWRP (now works)
then i flash the superuser. download phh app via playstore. grant SU access. reboot. like in OP described.
now i got both first field green. so ready to install framework
BUT when installing it. magisk manager (latest version) crashes and installing fails......
it says _> magisk not activated in flashing process
also no success with the zip in twrp
tried to proceed with kernel fastboot flash after this framework v1 fail.
but NOW it says magisk is not installed
then i twrp flashed v13.3 again. reboot. okay both checkboxes green again!
then you need to flash remoteplayenabler v1 via twrp.
then you have all 3 things green.
SUCCESS. :fingers-crossed::victory:
---------------------
UPDATE:
After all 3 field green i needed to install the latest Superuser form chainfire v82 R3.
Now Magisk wants me to install 13.3 again when i start the device. Also the Safety Check both fails and is red.
Installation fails via APP and TWRP! How can i try to fix it?
Do I need to start from Step 4 again?
How to keep everything Up 2 Date : Like FirmWare and SuperUser?
Thanks for your help!

guys i need help i tried twice and keep ending up with ERROR - Processing of system.sin finished with errors.
yes develop and usb debug is on, what am i doing wrong i want to dowgrade from 7.1.1 to 6.0.1 and root after backed up that key

guys i need help i tried twice and keep ending up with ERROR - Processing of system.sin finished with errors.
yes develop and usb debug is on, what am i doing wrong i want to dowgrade from 7.1.1 to 6.0.1 and root after backed up that key

[ROM] [8.0.0] [yuga] LineageOS 15.0 for Xperia Z (Unofficial)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
About ROM:
This is Experiemental Build of Android 8.0 Oreo for Sony Xperia Z (C6602, C6603), Based on LineageOS.
Thanks To:
Mardon
What's working:
* ROM is experiemental and is not recommended for daily usage *
* Now we have working Audio *
I have not tested whole rom but everything works fine except:
- Flashlight and Camera
- Adaptive Brightness
Please report any bugs in the comments below!
(Special) Install Instructions for Newbies:
Warning: If you flash ROM first time do it at your own risk, You may brick device.
Before resuming remember these things:
- You can't restore TA codes on a custom ROM, TA codes only work on Stock ROMs, So if you ever reflash Stock ROM you can restore them.
- If you're Windows 8/8.1 or 10 User this Tutorial may not work for you as long as you've done This Tutorial
- Read everything Carefully, I wish you Good Luck
1.0 - Backing up TA Codes
- First you need an unlocked bootloader, But before unlocking it you have to backup DRM keys (Optional)
- Download KingoRoot, Root your device with One-Click-Root and then Download Backup-TA Program from Here
1.1 - Unlock Bootloader
- After you've done that, Unlock your bootloader from Here
1.2 - Preparing Drivers
- After you unlock your bootloader Install Sony Flashtool from Here
- Go to Flashtool Folder then go Drivers folder and select Flashtool-drivers.exe
Check the Fastboot and Flashmode drivers then Scrool down and find Xperia Z SO-02E drivers, Check it and Install them.
1.3 - Installing ADB
- Now it's time to download ADB 15 Seconds Installer from Here
Follow the instructions in the program and Install ADB/Fastboot drivers, then locate "C:/adb" folder and open it.
- Download Latest TWRP 3.1.1 from Here and move into adb folder located in "C:/adb"
- Rename TWRP 3.1.1 file to twrp (If your file extensions are shown twrp.img)
- As long as you can't flash TWRP directly as Recovery you must flash it as boot, Your ROM won't start again so back up everything before restarting to ADB!
- After you back up everything just enable USB debugging in your phone (go Settings/About and press Build Number couple times)
- Press Back button and go to Developer Settings and find USB Debugging, Enable it.
- Now go to "C:/adb" and press and hold SHIFT, Then press RMB (Right Mouse Button) and press open command window here.
- Congratulations! Now you're in adb.
1.4 - Flashing TWRP
- Write next ADB Commands:
adb devices (so you will check your device is detected by ADB or not, If adb shows any number row and then DEVICE its okay, If it doesn't then just write):
adb reboot bootloader (Look at your phone and give permissions of USB Debugging to PC, If phone reboots it means you've done everything correctly, If it doesn't then you did something wrong!)
- Well if the phone rebooted you will see blue led in the top of your phone, That means you're in a bootloader!
Write next commands:
fastboot devices (And check your device is detected by fastboot or not, same thing it will show number row and then FASTBOOT, So you did everything correctly, If it doesn't check your installed drivers, You may have little update from Device Manager so comment down below, If drivers are installed wrong and you don't see device number and FASTBOOT just restart phone and wait for the answer in the comments)
- If you see your device number and FASTBOOT enter next commands:
fastboot flash boot twrp.img
- After you've done that and you see that it has flashed without any Errors write next command:
fastboot reboot
- Now you're in TWRP recovery, Congratulations !!
1.5 - CleanFlashing ROM
- If you backed up everything just see if your computer detects your phone's MTP (media file transfer)
Go to My Computer/Xperia Z and see is there Internal Storage or not
- If There is any Storage that's good so make a Fully Clean Install
- Go back in the main menu of TWRP press Wipe, Advanced Wipe and check: Data, Cache, Dalvik Cache, System and Internal Storage, Then swipe to wipe.
- After you wiped your phone go back to the main menu of TWRP, Enter your internal storage folder from your PC and move ROM, Gapps and Rootkit in there.
- After that Press Install, You'll see lineageos, gapps and rootkit in the TWRP so press lineageos file and swipe to flash.
- Then go back (Don't Reboot) and press gapps file, flash it as you flashed lineageos.
- Go back again and flash Rootkit but when it's finished just press wipe dalvik cache and swipe to wipe it!
- After you've done that press Reboot phone.
- Congratulations!! Wait for 10 minute to boot and enjoy your new Android 8.0.0 Oreo!
1.0-2 - Troubleshooting
- If you want to install any other Custom ROMs just resume this tutorial from ADB (adb reboot bootloader) And do the same.
- If ROM doesn't boot up that means you did something incorrectly, So you have to do next steps:
Long Press Power Button and Volume UP, After it vibrates it will vibrate three more times and then release so your phone will shut down.
Get your USB Cable which's connected to PC and hold Volume UP, then connect USB Cable into phone
- You're in a fastboot, resume tutorial from (fastboot flash boot twrp.img)
- If you flashed ROM again and still doesn't work change your gapps version and download gApps-Pico
- Then it will work 100%, Or you can flash LineageOS14.1 and wait for Stable Oreo build.
- Thank you for attention, do it at your own risk and good luck
Downloads:
MOD EDIT: Download link removed.
Download the gApps (ARM, 8.0, Pico)
Download Rootkit if you want (I've tested Magisk and works fine)
- Links updated & No more error7 in TWRP
Short Install Instructions:
Move the ROM/GAPPS/ROOTKIT on your SDCARD
Flash latest TWRP (If you have old version already reflash it using flash image)
Wipe Cache, Data, Dalvik cache and System
Flash ROM
Flash gApps
Flash Rootkit
Wipe dalvik cache
Reboot!
- First boot may take some time for optimizing apps, bootanimation may have a little lag, be patient and wait.
ROM Information:
ROM Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information:
Status: Experiemental
If you like the ROM please hit that Thanks button and give some support

Again hard work on design of topic, i hope you enjoy highlights and green (LOS color) design
So hit that THANKS button <3

#iLiKo said:
Again hard work on design of topic, i hope you enjoy highlights and green (LOS color) design
So hit that THANKS button <3
Click to expand...
Click to collapse
omg I can't believe this @@
thank you so much for your awesome work ^^

with 3.0.2- version of TWRP gave me error 7 and not install me the ROM so it is possible with 3.1.1 version ?

404 not found
Can't find it!
If you are seeing this error page then the file in question has been deleted from the site and servers. Please contact the developer/uploader for a new link to the file.

cyparisss1 said:
with 3.0.2- version of TWRP gave me error 7 and not install me the ROM so it is possible with 3.1.1 version ?
Click to expand...
Click to collapse
Not TWRP problem at all, don't delete rom because mby link got broken, ill help you to fix tommorow, update-script must be changed

Mardon deleted both international testbuilds of lineage15yuga from his account, idk why.
Link of old version:
MOD EDIT: Removed download link

not happen
with version 3.1.1
installing zip file /sdcard/Android 8/lineage-15.*****
checking for digest file....
skipping digest check : no Digest file found
Warning: no file_contexts
E3004: This package is for device: C6602, C6603, C6606, yuga;this device is .
Updater process ended with ERROR: 7
Error installing zip file lineage-15*******
Updating partition details...
....done
my device is 6603 I am sure in that - how to check and set it, may be from the custom roms this information is lost in the phone ?

cyparisss1 said:
with version 3.1.1
installing zip file /sdcard/Android 8/lineage-15.*****
checking for digest file....
skipping digest check : no Digest file found
Warning: no file_contexts
E3004: This package is for device: C6602, C6603, C6606, yuga;this device is .
Updater process ended with ERROR: 7
Error installing zip file lineage-15*******
Updating partition details...
....done
my device is 6603 I am sure in that - how to check and set it, may be from the custom roms this information is lost in the phone ?
Click to expand...
Click to collapse
dude its bugged at update-script so tommorow when i get PC please upload that new ROM somewhere, ill fix it and you and other people can download back, i fixed the link, but its old version without audio..

#iLiKo said:
Mardon deleted both international testbuilds of lineage15yuga from his account, idk why.
Click to expand...
Click to collapse
I can tell you why. Because you posted it without even asking. This happened a month ago too. Please stop that. It is annoying and delays LOS15 for fusion3 because people have to deal with this sh**.

I am using custom rom and my device model is Xperia Z , it is possible to not verify my phone like c6603 and then the installation fails. See on the screen shots

#iLiKo said:
dude its bugged at update-script so tommorow when i get PC please upload that new ROM somewhere, ill fix it and you and other people can download back, i fixed the link, but its old version without audio..
Click to expand...
Click to collapse
welcome my friend, MOD EDIT: Removed download link

NamenIos said:
I can tell you why. Because you posted it without even asking. This happened a month ago too. Please stop that. It is annoying and delays LOS15 for fusion3 because people have to deal with this sh**.
Click to expand...
Click to collapse
ill explain u smth this rom is shared and doesnt require any rights to post on websites, also people must have single oreo rom for this phone to try how its like, plus i made whole tutorial of newbies now i think they wont get in problems, also everyone knowns that this is experimental testbuild, but LOSTEAM still want to share only stable.. i think differently, i think people can see how oreo really is, whats the differences and etc.. by themselves. stop it, im not gonna delete rom again.

cyparisss1 said:
welcome my friend, MOD EDIT: Removed download link
Click to expand...
Click to collapse
new link: MOD EDIT: Removed download link

Bug
Camera not working
Lag ui (recent app)
Error 7 script delete assert line

mohammadnadimi48 said:
Camera not working
Lag ui (recent app)
Error 7 script delete assert line
Click to expand...
Click to collapse
Error 7 has been fixed i think so.
Use new link

Thread closed.
#iLiKo said:
ill explain u smth this rom is shared
Click to expand...
Click to collapse
Yes, you are right here - LineageOS can be built from source.
#iLiKo said:
doesnt require any rights to post on websites
Click to expand...
Click to collapse
Not quite correct - you still need to stick to the XDA rules (see rule 12).
You need to accept the fact that the developers of the ROM don't want to release half-baked builds or unfinished work (even if it's open source). Don't we all want a stable daily driver after all?
Thread closed.