Develop Bugs

[ROM][C6903][LB&UB]z1slim v0.4[4.3][NO BLOAT][FULL ROOT][XZDR][09/01]

{
"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"
}
Introduction:
This is my first ROM for any device, there will probably be bugs. I am not responsible for anything that happens to YOUR device as a result of flashing this. All releases are tested before posting to minimize the risk but there is always a chance something could go wrong!
My aim with this rom was to clean out all the useless rubbish I never use. This includes all social networking integration as I only see this as bloat, being as most of it is installable from the market.
Maybe someone else would like this too, so I am sharing my work.
Downloads:
z1slim.flashable.v0.4.zip (XDA Direct)
z1slim.flashable.v0.4.zip (XDA Torrent)
MD5: f12ac5a793edd2a25f7d9c3e758fda38
290-stripped.ftf
MD5: d06d6a554ba012d3ca0fb6bcd0f526b3​
If you need something I have removed, download the AROMA installer below. It has all the apps and integration that I have removed from the stock rom in a format you can easily pick and choose what to reinstall. Just install it in recovery and tick any apps you want back! All apps within this installer are also deodexed.
z1slim.re-bloat.v1.zip
MD5: 91416eb62e0ddafd5257da28166fddac​
How to install:
YOU WILL LOSE ALL USERDATA ON INTERNAL SDCARD BY DOING THIS. SO BACKUP FIRST!
1: Flash c6903 stock version 534 from this link: https://mega.co.nz/#!K1QD1bSK!JkgNvz3Tqb6lq4brVUEyZGraOjMQuTuzn8IaEFhQhUI
2: Root using bin4rys tool: http://forum.xda-developers.com/showthread.php?p=31545627
3: Install XZ1 DualRecovery 2.7.73 beta from [NUT]'s website: http://forum.xda-developers.com/showthread.php?t=2261606
4: Copy z1slim.flashable.v0.4.zip to external sdcard
4: Reboot into TWRP
5: Click wipe -> Advanced wipe -> Tick dalvik+cache+system+internal data -> swipe to wipe
6: Format data -> Type yes
7: Install z1slim.flashable.v0.4.zip
8: DO NOT REBOOT! Instead go to reboot menu and click power off
9: Flash 290-stripped.ftf using FlashTool
10: Enjoy the rom!
First boot will take a while if you have done a factory reset.
Alternatively if you do not have an external sdcard you can sideload the zip
this is neccessary because we will format internal storage, so it cannot be there.
If you already have a rooted 4.3 ROM installed with XZDR working properly, you can just download the flashable zip, wipe data etc and install it from recovery. If you are coming from a previous version of this ROM then you only need to install the zip. No wipe required.
Changelog:
Version 0.4
-Removed all themes and wallpapers except default
-Removed chrome and put back stock browser
-Removed almost all social integration again (Didnt break rom this time!)
+Updated DualRecovery to 2.7.73 Beta (thanks again [NUT]!)
+Updated all sony apps that are left
+Updated Google play store
+Added white balance settings and a script to reapply settings at boot (Thanks to RyokoN!)
+Deodexed apps and framework
Version 0.3
-Removed further O2 customization
+Added social network integration again as it broke the ROM
+Adblock hosts file
+Customized the install script
Version 0.2
-Removed the rest of the bloat + apps you can get from market
-Removed social network integration
+Stock bootanimation
+Fixed full root (System now mounts R/W on LB)
+Fixed language selection appearing every boot
Version 0.1
-Based on 14.2.A.0.290_O2-UK
-Removed O2 Branding
-Removed all useless bloatware apps
-Removed anonymous statistics
-Removed My Xperia app
-Removed stock browser as chrome is included
+Rooted (LB & UB) by [NUT]
+DualRecovery 2.7.71 by [NUT]
+SuperSU by Chainfire
Bugs:
None known as of now with the base rom.
When restoring twitter integration there seems to be an issue signing in. Twitter app works fine though. - Thanks to sg1969 for finding this.
Credits:
[NUT] for kitchen + 4.3 Root + XZ1 DualRecovery (damn he's good!) - Click here to donate to [NUT]
Chainfire for SuperSU
zyclops1 for figuring out which rom we had to start from
BSDgeek_Jake - Adblock hosts file
RyokoN - White balance settings port
Myself
If I have missed anyone, give me a slap in a pm.
DONATIONS ARE NOT REQUIRED! But if you want to thank me for my work, I wouldn't say no.
Click here to buy me a beer!
If you want to use this as a base for your own ROM. You are welcome to. Please just give me and the other guys some credit!
XDA:DevDB Information
z1slim, a ROM for the Sony Xperia Z1
Contributors
GavTheStoner
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Stock 14.1.G.1.534 firmware or working 4.3 with recovery and root
Based On: Stock 4.3 version 290
Version Information
Status: Beta
Current Beta Version: 0.4
Beta Release Date: 2014-01-13
Created 2014-01-08
Last Updated 2014-01-18

Reserved.

Good to see more DEVS here and there, let me give you an advice, people will not go back to 534 if they're already in .290 with working recovery, because i didnt go back to 534 since the first semi-rooted 290 i had to always flash the flashable recovery that i had! now if you read the NUT thread you can figure out that if you already have a working recovery or you were on any 290 from iHackers or ROMAUR or even Monx you'll be able to just flash the update zip that is in the NUT to get Full ROOT!
anyways that was only my opinion
Thanks and good luck.

Nice mate.
You are not taking anything more than others who are posting stupid things like - "new album upgrade".
Learn and upgrade your ROM, we need good guys here.
Maybe this isn't heavy development but it's one step up and I'm 100% sure it'll be great ROM one day.
You are creating something new, unlike some others guys who are constantly whining and doesn't contribute this community at all.
BTW what @Simow.b saying is correct, you should add that in OP.
Just write: if you are already on 290 or any ROM with working recovery just flash ROM through recovery, flash recovery, power of, flash ftf and restart.
:thumbup:
Sent from my C6903 using Tapatalk

funky0308 said:
Nice mate.
You are not taking anything more than others who are posting stupid things like - "new album upgrade".
Learn and upgrade your ROM, we need good guys here.
Maybe this isn't heavy development but it's one step up and I'm 100% sure it'll be great ROM one day.
You are creating something new, unlike some others guys who are constantly whining and doesn't contribute this community at all.
BTW what @Simow.b saying is correct, you should add that in OP.
Just write: if you are already on 290 or any ROM with working recovery just flash ROM through recovery, flash recovery, power of, flash ftf and restart.
:thumbup:
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Thank you for the kind words my friend

Simow.b said:
Thank you for the kind words my friend
Click to expand...
Click to collapse
We have to support guys who are willing to take their free time and work for us - free.
Someone will make something smaller, someone will make something big - but that's not important, what's important is that they are trying and learning and that's great.
Sent from my C6903 using Tapatalk

funky0308 said:
We have to support guys who are willing to take their free time and work for us - free.
Someone will make something smaller, someone will make something big - but that's not important, what's important is that they are trying and learning and that's great.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
I agree with that !

Simow.b said:
Good to see more DEVS here and there, let me give you an advice, people will not go back to 534 if they're already in .290 with working recovery, because i didnt go back to 534 since the first semi-rooted 290 i had to always flash the flashable recovery that i had! now if you read the NUT thread you can figure out that if you already have a working recovery or you were on any 290 from iHackers or ROMAUR or even Monx you'll be able to just flash the update zip that is in the NUT to get Full ROOT!
anyways that was only my opinion
Thanks and good luck.
Click to expand...
Click to collapse
So is there way to get recovery back I run ihackers but I don't see any recovery?

adamo86 said:
So is there way to get recovery back I run ihackers but I don't see any recovery?
Click to expand...
Click to collapse
Try to flash the latest windows recovery from NUT and follow the steps:
1- Make sure you have USB debugging turned ON.
2- download XZ/ZL/TabZ/Z1/ZU-lockeddualrecovery[VERSION]-BETA.installer.zip from http://nut.xperia-files.com
Windows:
3- unpack at C: or somewhere you will remember!
4- navigate to the resulting directory and look for install.bat, double click it to run;
let me know if this worked for you

Simow.b said:
Try to flash the latest windows recovery from NUT and follow the steps:
1- Make sure you have USB debugging turned ON.
2- download XZ/ZL/TabZ/Z1/ZU-lockeddualrecovery[VERSION]-BETA.installer.zip from http://nut.xperia-files.com
Windows:
3- unpack at C: or somewhere you will remember!
4- navigate to the resulting directory and look for install.bat, double click it to run;
let me know if this worked for you
Click to expand...
Click to collapse
I can't see the version you mentioned in the link.
I'm on LB so would it work I have partial root though.

adamo86 said:
I can't see the version you mentioned in the link.
I'm on LB so would it work I have partial root though.
Click to expand...
Click to collapse
i'm also on LB here's the windows version
http://nut.xperia-files.com/?dlid=WjEtbG9ja2VkZHVhbHJlY292ZXJ5Mi43LjcxLUJFVEEuaW5zdGFsbGVy
and after that flash this:
http://nut.xperia-files.com/?dlid=WjEtbG9ja2VkZHVhbHJlY292ZXJ5Mi43LjcxLUJFVEEuZmxhc2hhYmxl
you could always try my friend if it doesnt work then you should do the steps again from 534 but this time when installing the recovery install the one that i have posted now.

Simow.b said:
i'm also on LB here's the windows version
http://nut.xperia-files.com/?dlid=WjEtbG9ja2VkZHVhbHJlY292ZXJ5Mi43LjcxLUJFVEEuaW5zdGFsbGVy
and after that flash this:
http://nut.xperia-files.com/?dlid=WjEtbG9ja2VkZHVhbHJlY292ZXJ5Mi43LjcxLUJFVEEuZmxhc2hhYmxl
you could always try my friend if it doesnt work then you should do the steps again from 534 but this time when installing the recovery install the one that i have posted now.
Click to expand...
Click to collapse
I won't fall any boot or brick problems would I.thanks

adamo86 said:
I won't fall any boot or brick problems would I.thanks
Click to expand...
Click to collapse
if everything's goes well then you will get a fully working recovery plus a nice full rooted ROM!
if not then you should just do the steps from NUT thread and you'll be fine

Simow.b said:
if everything's goes well then you will get a fully working recovery plus a nice full rooted ROM!
if not then you should just do the steps from NUT thread and you'll be fine
Click to expand...
Click to collapse
Link please

adamo86 said:
Link please
Click to expand...
Click to collapse
Here you go :
http://forum.xda-developers.com/showthread.php?t=2572988

Simow.b said:
Here you go :
http://forum.xda-developers.com/showthread.php?t=2572988
Click to expand...
Click to collapse
Didn't work the phone reboots back up dosent go into recovery.

Jonster111 - Nobody is forcing you to click on this thread or download this ROM. It is quite apparent what it is from both the thread title and the description in the first post.
Thanks Simow.b and funky0308 for the real support
Who knows, maybe this will one day be a base for a proper modified rom. Until then, I still need to remove the useless rubbish!
----
Ive just noticed that its not really got full root so have to fix that too. Cant mount system R/W but have got latest XZDR... Weird.

adamo06 please follow the guide in [NUT]'s thread properly. You need to download the 534 version from his OP to get the rom to install properly, or at least have a rooted 257 with recovery already. Also, please take discussion about that to the appropriate thread.

adamo86 said:
Didn't work the phone reboots back up dosent go into recovery.
Click to expand...
Click to collapse
Follow my steps then:
1- flash 534 using flashtool
2- root it using bin4ry's tools
3- install NUT recovery (the ones that i have given) install windows version and when you're on the recovery flash the one that is flashable! do not reboot!
4- flash the 290 from any DEV i would recommend iHackers v2.0 do not reboot!
5- flash xposed for lb from Monx and again (do not reboot! )
6- flash the update zip for 290 from NUT thread
7- wipe cache/dalvik
8- power off the phone from recovery
9- flash the kernel for 290
10- boot the phone and wait!
Hope this helps now
---------- Post added at 03:00 PM ---------- Previous post was at 02:58 PM ----------
GavTheStoner said:
Jonster111 - Nobody is forcing you to click on this thread or download this ROM. It is quite apparent what it is from both the thread title and the description in the first post.
Thanks Simow.b and funky0308 for the real support
Who knows, maybe this will one day be a base for a proper modified rom. Until then, I still need to remove the useless rubbish!
----
Ive just noticed that its not really got full root so have to fix that too. Cant mount system R/W but have got latest XZDR... Weird.
Click to expand...
Click to collapse
You're always welcome my friend

Version 0.2 was pulled due to a fatal bug.
Version 0.3
-Removed further O2 customization
+Added social network integration again as it broke the ROM
+Adblock hosts file
+Customized the install script

[STOCK][C69XX][4.3] Update to 14.2.A.1.136 [Root & XZDR][LB/UB][DE-/ODEX]

{
"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"
}
Requirements:
Flashtool 0.9.13 by @Androxyde
XZDualRecovery 2.7.76 BETA or newer.
Current rooted FW version: 14.2.A.0.290 .
Special features:
SuperSU integrated in system, FULL ROOT!
XZDualRecovery 2.7.80 BETA (CWM & PhilZ Touch & TWRP) pre-installed;
init.d support (read how to enable)
For both locked and unlocked bootloaders!
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.
If you are unable to download torrent files directly, have http://zbigz.com/ do it for you!
How to update to 14.2.A.1.136:
Files:
For C6902: Download C6902_14.2.A.1.136.flashable.zip (Bittorrent: 926MB) and C6902_14.2.A.1.136_Stripped.ftf (21MB)
For C6903: Download C6903_14.2.A.1.136.flashable.zip (Bittorrent: 806MB) and C6903_14.2.A.1.136_Stripped.ftf (21MB)
For C6906: Download C6906_14.2.A.1.136.flashable.zip (Bittorrent: 872MB) and C6906_14.2.A.1.136_Stripped.ftf (21MB)
For C6943: Download C6943_14.2.A.1.136.flashable.zip (Bittorrent: 889MB) and C6943_14.2.A.1.136_Stripped.ftf (21MB)
Save them somewhere you remember;
Put 'C69XX_14.2.A.1.136.flashable.zip' on (the external) SDcard1;
Put 'C69XX_14.2.A.1.136_Stripped.ftf' inside the Flashtool/firmwares folder;
Create a backup of your phone in TWRP and don't forget to backup the contents of 'SDCard' (the internal storage!);
Flash 'C69XX_14.2.A.1.136.flashable.zip' in TWRP;
NOTE: do not reboot but go back to the main menu, then go to reboot->power off;
Flash everything in 'C69XX_14.2.A.1.136_Stripped.ftf' using flashtool;
Reboot to system.
The first boot will be slow and after some time at the boot animation you will see Android start optimizing the apps on your phone.
Enjoy! :laugh:
Unlocked bootloader?
To be able to use this ROM without any special tweaking, download C6903_14.2.A.1.136_kernel.img and
Code:
fastboot flash boot C6903_14.2.A.1.136_kernel.img
Or use flashtool to flash it.
It is a kernel repack, with only one change. To confirm you are running this kernel, check if the file '/nuts_repack' exists.
DE-ODEX your ROM!
Make sure you have the flashable ROM installed before you do this.
Download C6903_14.2.A.1.136_deodex.zip (Bittorrent: 412MB), save it somewhere you remember;
Put 'C6903_14.2.A.1.136_deodex.zip' on (the external) SDcard1;
Create a backup of your phone in CWM or TWRP and don't forget to backup the contents of 'SDCard0';
Flash 'C6903_14.2.A.1.136_deodex.zip' in recovery, do not reboot but go back to the main menu;
Clear dalvik-cache ONLY;
Reboot to system.
The first boot after flashing this you will see Android optimizing the apps on your phone, this might take a while... but should be just fine
Known XZDualRecovery Issues:
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 any JB 4.2.2 FTF using any means you are familiar with so you can try again.
Root it using any means you are familiar with.
Install XZDualRecovery;
Update to 14.2.A.0.290;
Then try to update again using TWRP.
If it still fails something from there on: LOGS!!.
NOTE: The important ones can be found in /cache/recovery and in /sdcard1/XZDualRecovery, pack them up and send them to me or attach them to your bug report.
Thank you
XDA:DevDB Information
[STOCK][C69XX][4.3] Update to 14.2.A.1.136 [Root & XZDR][LB/UB][DE-/ODEX], a ROM for the Sony Xperia Z1
Contributors
[NUT]
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 14.2.A.0.290
Based On: STOCK
Version Information
Status: Stable
Stable Release Date: 2014-01-31
Created 2014-01-29
Last Updated 2014-02-01

FAQ & Tips and Tricks
Easy switching between locked and unlocked bootloader states!
NOTE: USE TWRP ONLY for this guide.
NOTE 2: You NEED to have XZDualRecovery 2.7.43 or higher to make this work.
Create a backup, including the Trim Area (TA!)
Unlock your bootloader
Restore backup without TA
Create a new backup of your UNLOCKED TA
Restore the previous TA backup to relock your phone.
Done :good:
Now you can switch between locked and unlocked bootloaders quick and painless: no more system wipes and you can basically do whatever you want
How to enable init.d support:
Open a filemanager app and navigate to the location where the XZDualRecovery folder is located and go in to it. Open XZDR.prop as a text file and set dr.initd.active to true.
NOTE: For this guide ROM it means the init.d script called 99SuperSUDaemon will kick in to action, so it's best to disable (by setting chmod 644) /system/etc/install-recovery.sh for the time being or to clear it's contents.
Done
Downgrading to a 4.2 ROM:
Download C6903_14.1.G.1.534_[NUT].ftf (Bittorrent: 770MB) and flash it using FlashTool. I've also added the FTF to the downloads page on this DevDB tab, this will allow straight downloads as well.
This FTF will allow you to downgrade to .534 without loss of your IMEI :good:
Thanks to @mharckk and @MohammadAG for the workaround which contributed to the creation of this FTF.

ROM STATUS: STABLE
At this moment, running out of time to sleep before work tomorrow, I have to put this online still with a SEMI-ROOT
Fortunately recovery is working well, so I will be able to release a simple patch once I crack this one :good:
No patch required, it was my sleep deprived stupidity which resulted in a stupid mistake!

Hahaaaa nice work mon ami ^_^
Sent from my GT-I9505 using XDA Premium 4 mobile app

I'm not much of a developer, but there is one thing im good at seeding! :good:

@[NUT] it just have SEMI Root???
Another RIC must to crack??

Thank you @[NUT]. You're awesome
Sent from my C6903 using Tapatalk

Is this normal, in this case to have /system without RW ?

binoslaw said:
Is this normal, in this case to have /system without RW ?
Click to expand...
Click to collapse
For this version, yes... Will try to find a solution tonight...
The rom is fine to use and some root tasks can still be performed, using recovery you are able to install just about everything... Provided it is flashable of course

Yes, I know. BTW great work. I need RW because I would like to uninstall some apps.
Anyway. I'm waiting for Your magic.
Sent from my C6903 using XDA Premium 4 mobile app

binoslaw said:
Yes, I know. BTW great work. I need RW because I would like to uninstall some apps.
Anyway. I'm waiting for Your magic.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can use twrp for that too you know
Boot twrp, mount system, go to advanced and then the file manager. Navigate to system/app and tap all files you want to do something with... :highfive:

Will /system remount work on an Unlocked Bootloader?

mynameisjon said:
Will /system remount work on an Unlocked Bootloader?
Click to expand...
Click to collapse
Only with a patched ramdisk on the stock kernel I'm afraid... I can do that though, it's not that hard
If anyone wants a patched ramdisk-kernel for this ROM, let me know. I won't integrate a recovery though, just the RW patch.
BIG NOTE: it is intended for use on an UNLOCKED BOOTLOADER ONLY then ... just FYI
Because of your question @mynameisjon I reallized that with the guide in post #2, it should be fairly easy to switch between locked and unlocked TA+kernel sets

[NUT] said:
Only with a patched ramdisk on the stock kernel I'm afraid... I can do that though, it's not that hard
If anyone wants a patched ramdisk-kernel for this ROM, let me know. I won't integrate a recovery though, just the RW patch.
BIG NOTE: it is intended for use on an UNLOCKED BOOTLOADER ONLY then ... just FYI
Because of your question @mynameisjon I reallized that with the guide in post #2, it should be fairly easy to switch between locked and unlocked TA+kernel sets
Click to expand...
Click to collapse
Would be awesome if you could provide the ramdisk-kernel. I'm assuming that it's a boot.img and that I'd have to install the dual recovery seperately?

[NUT] said:
Only with a patched ramdisk on the stock kernel I'm afraid... I can do that though, it's not that hard
If anyone wants a patched ramdisk-kernel for this ROM, let me know. I won't integrate a recovery though, just the RW patch.
BIG NOTE: it is intended for use on an UNLOCKED BOOTLOADER ONLY then ... just FYI
Because of your question @mynameisjon I reallized that with the guide in post #2, it should be fairly easy to switch between locked and unlocked TA+kernel sets
Click to expand...
Click to collapse
For Locked booloader you can use the same root method of 259?

mynameisjon said:
Would be awesome if you could provide the ramdisk-kernel. I'm assuming that it's a boot.img and that I'd have to install the dual recovery seperately?
Click to expand...
Click to collapse
Correct. But if you use my ROM package, recovery will already have been integrated.

fer2503 said:
For Locked booloader you can use the same root method of 259?
Click to expand...
Click to collapse
I'm assuming you mean .290? Well... that same method has been applied in this ROM... but to no avail unfortunately, it needs some updating unfortunately.

Yes, you are right, i mean 290. I Hope you Can find a solution

[NUT] said:
Correct. But if you use my ROM package, recovery will already have been integrated.
Click to expand...
Click to collapse
Does an unlocked bootloader still require flashing the stripped package?

mynameisjon said:
Does an unlocked bootloader still require flashing the stripped package?
Click to expand...
Click to collapse
Yes sir, it contains all the bits the flashable zip can not flash. I did not check if the kernel itself changed to be honest, so maybe this ROM will work fine on any .290 kernel... but i still need to test that.
Loads of stuff to do tonight

PirateXPERIA Project

{
"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"
}
Hi XDA. I used cyanogenmod ramdisk overclocked by FindYanot.
Thanx FindYanot, awesome work.
Kernel is for Sony Xperia M | C1905 | Nicki
Incudled recoveries:
Team Win Recovery Project
Philz Recovery
ClockworkMod
CyanogenMod Recovery
Click to expand...
Click to collapse
DOWNLOADS
Install instructions:
If updating form older version, is recommended to delete /system/kernel folder.
New files will overwrite old files, but some old files are not needed.
by removing /system/kernel folder before flash you can maybe get some free space.
Via custom recovery:
Code:
1. flash PirateXperiaKernel.zip via custom recovery (CWM/TWRP)
2. flash cm11_addon, cm12_addon or stock_addon (when you flash both, last flashed will be used)
When you dont have any kernel with custom recovery:
Code:
1. extract boot.img form PirateXperiaKernel.zip, and flash it via fastboot.
2. BUT THEN DONT FORGET TO FLASH PirateXperiaKernel.zip VIA TWRP!
3. flash cm11_addon, cm12_addon or stock_addon (when you flash both, last flashed will be used)
Dont forget to flash PirateXperiaKernel.zip again, after system formating!!!
Click to expand...
Click to collapse
What do you need?
Xperia M device (C1505 cnofirmed)
CyanogenMod 12 based ROM (can flash after kernel)
15MB free space in /system partition
Click to expand...
Click to collapse
Why use PirateXPERIA Kernel:
+ Overclocked CPU to 1.6GHz.
+ 4 recoveryes
+ Downloadable backgrounds
Click to expand...
Click to collapse
Preview Wallpapers
Download Wallpapers
Boot Logo:
Boot Animation:
It is one bootanimation. but i cannot make gif, that wil loop from part1.
First is part0, and part1 preview. Second is only part1 (bootanimation loop) preview.
DOWNLOAD: bootanimation.zip in DOWNLOADS / misc
To apply bootanimation, just copy bootanimation.zip into /system/media folder, and "chmod 644 /system/media/bootanimation.zip"
If you like my work, press Thans button, but first press thanks button on FindYanot´s thread .
And sorry for my bad english.
Using:
To boot system only turn on your phone.
To boot recovery menu press vol+/vol- during blue led flashes.
To boot TWRP first boot to recovery menu, then press vol+/vol- during cyan led flashes.
To boot Philz Recovery first boot to recovery menu, then press vol+/vol- during amber led flashes.
To boot CWM first boot to recovery menu, then press vol+/vol- during yellow led flashes.
To boot CM Recovery first boot to recovery menu, then press vol+/vol- during green led flashes.
To boot Recovery from FOTA partition first boot to recovery menu, then wait to white led flashes.
Click to expand...
Click to collapse
XDA:DevDB Information
PirateXPERIA Project, Kernel for the Sony Xperia M
Contributors
gouster3
Kernel Special Features: MultiRecovery OverClock
Version Information
Status: Testing
Created 2015-02-09
Last Updated 2015-03-01

Reserved
Changelog:
- Project paused until i will have time to look up kexex, and it´s use.
//EDIT: Project died with my device. So no more updates.
- Versions uses date, inside of numbers.(from next version)
- Downloads moved to BasketBuild
- Created bootanimation. (bootanimation.zip in downloads)
Version 2.1.1
- Kernel patch copy is recursive, you can add folders to pach.
Version 2.1.0
- Fixed kernel patch function. (thanx thichthat)
- Added support to run user's script before boot. (thanx thichthat)
- Changed CM Recovery Version for touch support (Fixed power-down bug too).
Version 2.0.0:
- Added CM11 Support
- Auto boot into recovery if ramdisk not found
- Load build-in recovery, when recovery not found
- need to flash cm11_addon.zip or cm11_addon.zip to get working
- added stock ROM support (with some extra optimalizations)
Version 1.10.0:
- TWRP Downgraded to 2.8.0.0 for mtp fix
- Fixed boot without config
Version 1.9.0:
- Can define kernel type (IMG/CPIO/FOLDER)
- TWRP recovery moved from /recovery to /sbin
- some bug fixes
Version 1.8.0:
- TWRP Updated to 2.8.4.0
- Changed logo colour
- Automatic patch kernel files from /system/kernel/patch
- Load recovery from FOTA
Version 1.7.0:
- Fixed logo position
- recoveries located in /system/kernel/recovery (TWRP located in kernel too)
- ramdisk located in /system/kernel/boot.cpio
- config file in /system/kernel/cofing
Version 1.6.0:
- Fixed Logo resultion
- Some bug fixes
- cpio images will deleted from ramdisk after one of it unpacked.
Version 1.5.0:
- Changed Logo
- Project renamed from MultiRecovery
to PirateXPERIA Project
Version 1.4.0:
- Added Philz Recovery
Version 1.3.0:
- Added CWM Recovery
- Added CyanogenMod Recovery
- Updated Kernel Version
Version 1.2.0:
- Updated Kernel Version
Version 1.0.0:
- Initial relase
- TWRP Recovery
- BattleField Boot logo
//When you see new version in challengelog, but not in downloads, just wait until i will upload it.
//Newest version can be relased few days after added to changelog. (time to test and compile it.)
Click to expand...
Click to collapse

Reserved
Woking on:
- Incudle MULTIROM by alvinhochun
- Higher freq. for manual overclocking. (use is optional)
- More variants of BootAnimation
- Fix screen shift bug in CWM and Philz Recovery.
- PirateXPERIA ROM
Click to expand...
Click to collapse
Know bugs:
- Screen shift bug in CWM and Philz Recovery.
- Phone will not in turn off when pressed Power off in CM Reovery
Click to expand...
Click to collapse
You can report bug here.
For advanced users, look into /system/kernel folder
config - configuration file. open with notepad++ (you can here change paths)
boot.cpio - ramdisk (overclocked cyanogenmod factory ramdisk)
recovery - folder with recoveryes.
script.sh - execute this file before boot to system/recovery.
patch -
this folder will copyred after ramdisk extract, and before execute ramdisk startup file.
here you can patch files from kernel. Applyed to boot.cpio and recoveries.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

awesome
Ill try this. I cant see the installation progress / logs in the cm recovery included in the cm12 package

Can it work on C1904/C2004?
Hi. Great job with the kernel dev. Have been waiting for an OC kernel for CM12. Problem is, I have a C2004 with C1904 firmware cross-flashed on it, on top of which i have CM-12 based Resurrection Remix ROM running. Will this kernel be able to run on my device, since you have mentioned only C1905 in your post?

manal.21sinha said:
Hi. Great job with the kernel dev. Have been waiting for an OC kernel for CM12. Problem is, I have a C2004 with C1904 firmware cross-flashed on it, on top of which i have CM-12 based Resurrection Remix ROM running. Will this kernel be able to run on my device, since you have mentioned only C1905 in your post?
Click to expand...
Click to collapse
Hi, i think no, just try. When it will no work, just flash your prevous kernel. Hope it works.

Tommienots said:
Ill try this. I cant see the installation progress / logs in the cm recovery included in the cm12 package
Click to expand...
Click to collapse
I will try to fix it.

SystemUI FC on c1904/2004
gouster3 said:
Hi, i think no, just try. When it will no work, just flash your prevous kernel. Hope it works.
Click to expand...
Click to collapse
Hi I flashed your kernel today on my device with configuration mentioned above. SystemUI keeps on FCing. So it doesn't work for now. Really hope it will be workable for c1904/2004 in the near future. Keep up the good work!
---------- Post added at 12:33 PM ---------- Previous post was at 11:58 AM ----------
manal.21sinha said:
Hi I flashed your kernel today on my device with configuration mentioned above. SystemUI keeps on FCing. So it doesn't work for now. Really hope it will be workable for c1904/2004 in the near future. Keep up the good work!
Click to expand...
Click to collapse
Also, Philz recovery doesn't load when I do the necessary steps. Also, the CWM recovery included has a screen shift bug. Please look into this if you can. Thanks!

I Will try this awesome kernel on pa 4.6 beta 6, i will report soon if this kernel works perfectly or not ..
Edit: i get only blank screen after boot logo appear ..
But i'm really confused, OP says support cm11, so this kernel probably work with kitkat rom, but i'm wrong .. :crying:
Sorry for my bad engelish

manal.21sinha said:
Hi I flashed your kernel today on my device with configuration mentioned above. SystemUI keeps on FCing. So it doesn't work for now. Really hope it will be workable for c1904/2004 in the near future. Keep up the good work!
Click to expand...
Click to collapse
Thank you. C2004 Not supported. Maybe later.
manal.21sinha said:
Also, Philz recovery doesn't load when I do the necessary steps. Also, the CWM recovery included has a screen shift bug. Please look into this if you can. Thanks!
Click to expand...
Click to collapse
Yes. I have it in to-do list.

itsnie said:
I Will try this awesome kernel on pa 4.6 beta 6, i will report soon if this kernel works perfectly or not ..
Edit: i get only blank screen after boot logo appear ..
But i'm really confused, OP says support cm11, so this kernel probably work with kitkat rom, but i'm wrong .. :crying:
Sorry for my bad engelish
Click to expand...
Click to collapse
Working just on CM12 (Lollipop) //Edit: now cm11 & stock supported

Can i boot any roms with this multirom?

itsnie said:
Can i boot any roms with this multirom?
Click to expand...
Click to collapse
No. This is not multirom, but MultiRecovery. (you can have TWRP, Philz, CWM and CM Recoveryes in one kernel)
if you mean cm11_addon cm12_addon and stock_addon, you can use only one of this.
i dont want to upload new kernel versions for both, so you must install kernel first. and then one of addons.
if you flash more of addons, it will use last flashed addon.
MultiRom is another project by alvinhochun
but i want implement it in my MultiRecovery kernel in future.
But, when you want, you can extract ramdisk from kernels, replace recovery cpio´s in /system/kernel/recovery
and now you can boot 4 different kernels. but without editing this kernels you can use kenrel only for rom located in /system.
only cm11, cm12 and stock rom are supported.
but if you want boot "unsupported" rom with this kernel, you must unpack ramdisk.cpio from rom kernel, and then move it in /system/boot.cpio.
cm11_addon, cm12_addon and stock_addon flashes only thit boot.cpio. so you can support any ramdisk you want.
but you will not have OC.

I copied my fstab.qcom and init.qcom.rc to /patch folder but it didn't replace the original files
I found this code in your init.sh:
Code:
busybox cp /system/kernel/patch /
And I think it should be changed to
Code:
busybox cp /system/kernel/patch/* /
We should also have an option to run user's script before system boot. I added this line:
Code:
exec /system/kernel/script.sh

Thanx. I have not trayed patch function yet.
I will change this in next version.

gouster3 said:
Thanx. I have not trayed patch function yet.
I will change this in next version.
Click to expand...
Click to collapse
i think using -R is allowed in busybox. or not? cp -r /system/kernel/patch/* /

Help!! Overclock works, but UI force closes and nav buttons, notifications and status bar dissapear.... Help please... thanks

ByronFer said:
Help!! Overclock works, but UI force closes and nav buttons, notifications and status bar dissapear.... Help please... thanks
Click to expand...
Click to collapse
Which rom are you using? i have same problem with Resurrection Remix 5.3.3.
Try cm-12-20150123-UNOFFICIAL-nicki by PecanCM´s CM12
Now i am using Resurrection Remix 5.3.3, with my kernel, but i have copyred ramdisk from rom into /system/kernel/boot.cpio.
it is solution too. but you will have not overclock.

[ROM] Stock 30a/30b/30d/30e/30f-eur/30f-vdf/30h-vdf - flashable zip [20160528] - NEW!

New build from D80230a/D80230b/D80230d/D80230e/D80230f
Still has recovery after flash.
Please Checking MD5 checksum before Flash...
For The guys from EUR zone I made flash able ZIP for a new KDZ please visit this thread as below
[ROM] SRKG2-1-00 (ESA/EUR) [3 In 1 ROM with Thai Food Names] - 20150517
Don't ask about what different between the previous version I don't have any change logs.
Download link
SRK-D80230F-EUR_20160528_droidth (NEW) Please read instruction as below for new build:
https://www.androidfilehost.com/?fid=24562946973630919
SRK-D80230H_20160107_droidth:
https://www.androidfilehost.com/?fid=24352994023707839
SRK-D80230d_EUR_20151124_droidth:
https://www.androidfilehost.com/?fid=24269982087003734
SRK-D80230f_20150926_droidth:
https://www.androidfilehost.com/?fid=24052804347822701
SRK-D80230e_20150417_droidth:
http://bit.ly/1b1BA2H
Download link
SRK-D80230d_20150403_droidth :
http://bit.ly/1ENqBXF
Download link
SRK-D80230b_20150425_droidth:
http://bit.ly/1bELkB0 - google drive mirror1
http://bit.ly/1IWE7qf - google drive mirror2
http://bit.ly/1JEX5BL - google drive mirror3
http://bit.ly/1E4uu7D - mirror MEGA1
http://bit.ly/1Gu9JmR - mirror MEGA2
Bittorrent format
https://www.androidfilehost.com/?fid=96042739161893331
(Unzip SRK-D80230b_20150425_droidth.zip then use bittorrent to Download)
Download link
SRK-D80230a_20150403_droidth:
http://bit.ly/1yIejs7
Download link
SRK-D80230a-SG_201500505_droidth (SEA) :
https://www.androidfilehost.com/?fid=23991606952597843
Mirror torrent file :
- D80230a
- D80230a
- D80230d
- D80230e
If you like my work , you can donate me with my email in paypal
My email : [email protected]
{
"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"
}
Mirror link :
- https://mega.co.nz/#F!Fg9URAbS!EhGVUeuzaQg0-uMX0_puMw (SRK-D80230a_20150403_droidth,SRK-D80230d_20150403_droidth)
From Member of my fackbook Fanpage @radoslaw Rusin @reza Sadeghi
SRK-D80230e_20150417_droidth.zip
https://mega.co.nz/?hc_location=ufi#!0EMDwCRT!07XccJVFYLu0_WcyEEbuTnlgeVWGuZEJgGaSuCC6NtY
http://fs2.filegir.com/gladiators1980/SRK-D80230e_20150417_droidth.zip?hc_location=ufi
Thank, @hockh @fuxmen, @mooncrown_ksk
File: SRK-D80230a_20150403_droidth.zip
MD5 checksum: 0BD1154DC296C73AE1061AED41FE4D53
File: SRK-D80230b_20150425_droidth.zip
MD5 checksum: FA96651705BEC42A23525652EC80DD4A
File: SRK-D80230d_20150403_droidth.zip
MD5 checksum: 95D9E126FA87A1A4F8C2F1CD5A33701E
File: SRK-D80230e_20150417_droidth.zip
MD5 checksum:15243a03c33c57fead73ddce1638b934
File: SRK-D80230f_20150926_droidth.zip
MD5 checksum:db2daa234e6fe50b6cb84f1d1736558d
MOD by @glfsd
http://forum.xda-developers.com/lg-g2/themes-apps/d802-lollipop-theme-original-firmware-t3071485
D802 - Bump Stock LP 30a,30b,30d,30e,30f,30h:
https://www.androidfilehost.com/?w=files&flid=31132
D802 - LP BaseBand 30a,30b,30d,30e,30f,30h:
https://www.androidfilehost.com/?w=files&flid=31134
Change logs:
- Rooted
- Remove all Vodafoneblotware
- Bump kernel 30d/30a
- Fix Battery
- Still have TWRP Recovery Bump 2.8.6.1
- Add SELinux Mode Changer
- Smoothy / Fast / Stable
- Hide Home touch buttons
- Combination key enter to Recovery
- Can flash on Jelly Bean or KitKat ROM
- Lte Support
BACKUP DATA BEFORE INSTALL ROM AND MAKE SURE YOU HAVE THE LASTEST VERSION......
New instructions FOR SRK-D80230F-EUR_20160528_droidth.zip
1. downlaod ROM
2. download 01-CustomPatcherScript_Bump.zip
https://onedrive.live.com/redir?resid=F8CABDE84AF2675E!4276&authkey=!AJCH2nNZUVGRxBI&ithint=file,zip
3. download 02-BETA-SuperSU-v2.67-20160121175247.zip
https://onedrive.live.com/redir?resid=F8CABDE84AF2675E!4275&authkey=!AM1CLoezpWOl9mk&ithint=file,zip
4. reboot to TWRP
5. install ROM (after finished don't reboot system)
6. install 01-CustomPatcherScript_Bump.zip
7. install 02-BETA-SuperSU-v2.67-20160121175247.zip
8. reboot
if you forget install 01-CustomPatcherScript_Bump.zip and 02-BETA-SuperSU-v2.67-20160121175247.zip, then you got bootloop, please go back to TWP and then install both files and reboot again
How to install
1. Copy ROM into SDCARD
2. Reboot to Recovery
3. Wipe (System,cache,dalvik,data)
4. Install ROM
5. Reboot
6. Enjoy
How to Go back to KK (Install ROM or Restore KK image)
- D802_PATCH_RETURN_KK_droidth.zip
http://bit.ly/1LJG52P
1. Reboot to Recovery (Base on TWRP Recovery)
2. Flash D802_PATCH_RETURN_KK_droidth.zip > Home
> Choose Reboot > reboot to Recovery again
3. Depend on situation
3.1 You want to restore KK image
- Restore KK Image (Go to 4.)
3.2 You want to install KK Custom ROM
- Wipe (system\data\dalvik and cache)
- Flash KK Custom ROM
- Flash ASOP KK BaseBand (For ASOP Custom ROM)
4. Reboot
How to Restock LP image (When current ROM is KK)
-D802_PATCH_GO_LP_V1.1_droidth
https://mega.nz/#!YNMmWKoJ!h2siD4om0jKPkrTA4mSpCrdHvMBIY3Bv3aXIQxMDKQo
1. Reboot to Recovery (Base on TWRP Recovery)
2. Flash D802_PATCH_GO_LP_V1.1_droidth.zip > Home
> Choose Reboot > reboot to Recovery again
3. Flash your Custom Recovery that you use backup your ROM before go back to KK
Then choose reboot to recovery again
4. Restore LP image
5. Reboot
How to enter to recovery
1. Turnoff G2
2. Press Power + Vol down button Until LG Logo appear
3. Release 2 button immediately 1-2 sec. then press 2 button again Until appear white screen
4. Choose Yes (Use Vol. Key to choose,Use Power Key to select) 2 times it will be enter to recovery
How to solve problem with Boot stuck on LG Logo
(In case wipe internal storage)
1. Return to Recovery again
2. Choose Wipe > Format > type yes
3. Reboot
FOR Charging bug
Don't worry about this bug.It will be resolve by @dorimanx for comming soon.
It's auto, from 300 to 1500 as kernel decides. Its random..
PLEASE DON'T ASK THIS QUESTION
What's the difference between 30a and 30d?
30a is Italy/international version and 30d is the vodafone version but both are the same except one 30a is just without the Vodafone stuff @Supracer
Thank,
@blastagator Bump TWRP
@topet2k12001 How to add Bump TWRP
For people who can answer the question in my thread please help me answer too,I can't answer or see all question because I have so many question in Thread/inbox xda/Q&A thread/facebook fanpage/inbox facebook fanpage/facebook group and I have so many work in my office.I can't answer for all question.I apologize for it.
Thank you,
ขอบคุณครับ (In Thai language)
[LG2-D802] Step by Step install Official Lollipop firmware via Flash-able Zip
[LG2-D802] Step by Step install Official Lollipop firmware via Flash-able Zip

What about flashing bumped recovery right after flashing this zip to keep the recovery? Is it possible?

Somboons fantastic job! Super Fast! It would be possible to make a flashable zip with the new OPEN V30A of Portugal? Thus avoided blotware Vodafone, we would have a cleaner ROM Thanks

Kael710 said:
What about flashing bumped recovery right after flashing this zip to keep the recovery? Is it possible?
Click to expand...
Click to collapse
Now I have TWRP Recovery.it can use combinationkey. I will be upload tonight.the link can public tomorrow

Can i flash this over cloudyflex 2.7? My phone is 32g d802 with the autorec on it.

flashed this (without flashing TWRP) and got into bootloop had to CSE flash KDZ

Actually im using cyanogenmod 12. Can i flash this ROM with no problems? Thanks
Sent from my SM-N910F using XDA Free mobile app

somboons said:
Now I have TWRP Recovery.it can use combinationkey. I will be upload tonight.the link can public tomorrow
Click to expand...
Click to collapse
We will be waiting. Please use an open rom, not vodafone . Thanks so much.

Rivafe said:
Actually im using cyanogenmod 12. Can i flash this ROM with no problems? Thanks
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
insalled 10 minutes ago over cm12 (wiped data, formated system & cache), booted up without a problem

Can i flash this ROM with TWRP? Thanks
Sent from my LG-D802 using XDA Free mobile app

Rivafe said:
Can i flash this ROM with TWRP? Thanks
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
worked for me

Rivafe said:
Can i flash this ROM with TWRP? Thanks
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
If u can, read first post and answer himself.

legola said:
Can i flash this over cloudyflex 2.7? My phone is 32g d802 with the autorec on it.
Click to expand...
Click to collapse
Yes ,you can .please use TWRP the latest version

TiagoEsteves said:
It would be possible to make a flashable zip with the new OPEN V30A of Portugal? Thus avoided blotware Vodafone, we would have a cleaner ROM Thanks
Click to expand...
Click to collapse
+1 :good:

I ' m working how to install TWRP on lollipop ROM for all varaint.
If I can prove it I will create thread to guide.

So to get this correctly...with latest twrp on D802 you wont lose custom recovery after flashing??

pikachukaki said:
So to get this correctly...with latest twrp on D802 you wont lose custom recovery after flashing??
Click to expand...
Click to collapse
TWRP IS costum recovery. If you don't flash TWRP you'll have STOCK recovery.

klemenSLO said:
TWRP IS costum recovery. If you don't flash TWRP you'll have STOCK recovery.
Click to expand...
Click to collapse
You can't flash this without twrp...im asking if this zip cause the custom recovery to be lost...

pikachukaki said:
You can't flash this without twrp...im asking if this zip cause the custom recovery to be lost...
Click to expand...
Click to collapse
Yep, if you flash this ROM trough custom recovery, you'll we lost your custom recovery, BUT, if you got international version of G2 (D802), you can use this tutorial -> http://forum.xda-developers.com/lg-g2/development/guide-bumpedtwrp-recovery-stock-v30d-t3070365 to get it back (thanks @wolfgart by the way)

vesi said:
+1 :good:
Click to expand...
Click to collapse
I can do it,please check for me it have Thai language.?

[ROM][UNOFFICIAL][ResurrectionRemix-P-v7.0.2][dragon] -> 20190624 (DISCONTINUED)

{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* 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.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
​
Make sure you have a custom recovery installed(TWRP is the preferred recovery)
Download the latest Resurrection Remix Rom & the latest GApps package
Boot into recovery
Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution
Flash ResurrectionRemix Rom
Flash Google Apps package(Optional)
Flash Magisk Root(Optional)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.​
​
Known issues:
- Encryption seems not work - and has not been tested. -> Pls do not encrypt your data partition yet.
- Keymaster -> If you set Pattern, PIN or Password the Screen unlock may not work correctly.
Workaround for Pattern: On fresh boot you will need to wait a bit longer before you enter credentials.
The waiting time is required on fresh boot only, the following unlocks are working normally.
In case of problems pls use Update.ZIP_TWRP_flashable_pattern_pin_remover_V2.zip to remove pattern/pin or password.
XDA:DevDB Information
ResurrectionRemix, ROM for the Google Pixel C
Contributors
followmsi, apascual89, redukt
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 3.18.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: RR-P-v7.0.2-20190423
Stable Release Date: 2017-04-15
Created 2017-04-25
Last Updated 2019-06-24

Ok guys, this rom is ultimative for configuration nerds (like me) - tested it now since release and find no issues. Magisk root and hide is full integrated, OMS too. Did some tests with my new toy (Huawei Watch 2 4g) by playing with watchface tools on bluetooth connection - well... it´s stable!
Connected my B&W P5 wireless headphones and got no hickups!
Running this setup with an accelerator based wallpaper - the GUI is really fluid and smooth.
Some screens;

The blur & transparency options are realyl eyecatcher, check it out

New version arrived ..
RR-N-v5.8.3-20170503-dragon-Unofficial-followmsi.zip
Installation:
1. Boot into TWRP
2. Wipe system, cache, dalvik and data. (Not needed if you upgrade from previous build)
3. Install RR-N-v5.8.3-20170503-dragon-Unofficial-followmsi.zip
4. install open_gapps-arm64-7.1-xxxx-20xxxxxx.zip (optional)
5. install SuperSU-v2.79-201612051815.zip (optional - the RR ROM installer does not include Magisk installation)
6. Reboot into system ..
- If you had gapps installed before you don't need to install gapps again - the installer will take care.
- Due to systemless rooting - if you have installed supersu before you need to install SperSU.zip again !
- Due to supersu installation it will boot twice - no panic, it's normal !
- If you face any strange issues, pls do a factory reset via TWRP first.
- If you have problems with SetupWizard from opengapps - pls install opengapps after first system boot.
- BeansGapps SetupWizard should have no problems at all !
The required (stock) vendor.img is part of the ROM installer now !
You may have a try and do a "dirty" flash too -> do not wipe your data partition.
If you face any problems pls fo a factory reset via TWRP first.
DOWNLOAD:
NEW: https://drive.google.com/drive/folders/0By6p5AdQfavBUTZmNWJoaU1iazg
OLD: https://onedrive.live.com/redir?res...17&authkey=!ACPxBsf1QD-Fr0M&ithint=folder,zip
Enjoy

Guys, it seems that the manually Magisk root installation is recommended. SuperSu give some conflicts and settings force closes. Many thank to @followmsi for his hard work supporting our lovely device with this beast of rom
Btw - if you get in trouble with SuperSU get MagiskManager root privileges and let it download Magisk-v12.0.zip. Reboot your device in TWRP and install Rom / (Kernel) / /MagiskManager/Magisk-v12.0.zip again. Thats´s all Have Fun

redukt said:
Guys, it seems that the manually Magisk root installation is recommended. SuperSu give some conflicts and settings force closes. Many thank to @followmsi for his hard work supporting our lovely device with this beast of rom
Btw - if you get in trouble with SuperSU get MagiskManager root privileges and let it download Magisk-v12.0.zip. Reboot your device in TWRP and install Rom / (Kernel) / /MagiskManager/Magisk-v12.0.zip again. Thats´s all Have Fun
Click to expand...
Click to collapse
Did you install fresh boot.img before you installed Magisk ?
If you want to install both - magisk and supersu - you need to follow the instructions here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
If you're not rooted, or something went wrong and you need a clean start
(Recommended) Restore your boot image back to stock (flash uninstaller if Magisk is previously installed)
Download the latest Magisk zip file
Reboot to a custom recovery
If you choose to use SuperSU (only support Android 6.0+), flash SuperSU in systemless mode now
Flash Magisk zip
Reboot. Update the stub Magisk Manager to the latest from Play Store
I don't have any problems ...
Installed Magisk only - works fine.
Installed SuperSU and Magisk - works fine. (SuperSU is the root tool then - Magisk Manger is used for modules only)
Magisk is quite nice - it does not need to double-boot after installation.
And it's open source too
If you install SuperSU and Magisk it still needs to double-boot because of SuperSu.
Maybe we should switch to Magisk in general .. for all ROMs
I did test this on LineageOS OMS CM14.1 now.
Will test again on RR version .. but it should be the same - the integrated Magisk Manager should not be related.
Cheers

Made a screen shot with LOS OMS version ..

Made same test on latest RR version now ... no problems at all.
Installed Magisk only - working fine.
Installed Magisk and SuperSU .. all is fine.
Same like in LOS OMS version .. root tool is SuperSU.
Magisk Manager has been granted access inside SuperSU tool.
Pls check your install procedure again ..
Removal of SuperSU or Magisk is done by just applying the fresh boot.img.
Magisk only install:
1. fresh boot.img (taken from zipped ROM package)
2. Install Magisk only-
3. Reboot system - no double-boot
or
Magisk and SuperSU install:
1. fresh boot.img (taken from zipped ROM package)
2. Install SuperSU first !!!
3. Install Magisk
4. Reboot system - still have the double-boot
SuperSu only installation has been already validated on last RR version.
I am really starting to like Magisk ... no double-boot anymore and full opensource

Here the same screen shot but inside RR ..
My conclusion .. no issues at all with magisk !
Seems to fully working with chromeos signed boot.img
Works with and without Supersu.
Does not need double-boot .. and is opensource.
Hmmmm .... I think I will switch
But the ROMs will be not changed !
If somebody wants to install SuperSU you don't need install a fresh boot.img before.
After ROM installation you decide what you want .. both tools or just one tool.
Topic magisk is closed now

followmsi said:
Here the same screen shot but inside RR ..
My conclusion .. no issues at all with magisk !
Seems to fully working with chromeos signed boot.img
Works with and without Supersu.
Does not need double-boot .. and is opensource.
Hmmmm .... I think I will switch
But the ROMs will be not changed !
If somebody wants to install SuperSU you don't need install a fresh boot.img before.
After ROM installation you decide what you want .. both tools or just one tool.
Topic magisk is closed now
Click to expand...
Click to collapse
Those screenshots have nicely answered a question for me if the Roms are laid out like stock nav bars or not lol

Made the same package for flo/deb and manta devices .
And now for dragon device too ..
It seems there are still issues with the opengapps SetupWizard on 7.1.2 ROMs.
The SetupWizard (only) package below seems to work fine - except for the "vision settings".
BeansGapps_SetupWizard_7.1.2_Dragon.zip
Installation:
1. As we want to see the SetupWizard we do a clean install .. wipe system, cache, dalvik, data .. everything except internal storage.
2. install the 7.1.2 ROM of your choice.
3. Install official opengapps package you like ..
4. install BeansGapps_SetupWizard_7.1.2_Manta.zip
5. Install Magisk and/or SuperSu.
6. Reboot into system and wait for the SetupWizard.
Cheers

followmsi said:
Made the same package for flo/deb and manta devices .
And now for dragon device too ..
It seems there are still issues with the opengapps SetupWizard on 7.1.2 ROMs.
The SetupWizard (only) package below seems to work fine - except for the "vision settings".
BeansGapps_SetupWizard_7.1.2_Dragon.zip
Installation:
1. As we want to see the SetupWizard we do a clean install .. wipe system, cache, dalvik, data .. everything except internal storage.
2. install the 7.1.2 ROM of your choice.
3. Install official opengapps package you like ..
4. install BeansGapps_SetupWizard_7.1.2_Manta.zip
5. Install Magisk and/or SuperSu.
6. Reboot into system and wait for the SetupWizard.
Cheers
Click to expand...
Click to collapse
Hello followmsi,
Thanks for port RR to our Pixel C I love RR and I use it on both of my OnePlus.
In my OP 3T with a 7.1.2 RR Rom I´m using BeansGAPPS Mini, so I should use the Beans package provided in your OneDrive folder?
Thanks in advance.

Istvan_86 said:
Hello followmsi,
Thanks for port RR to our Pixel C I love RR and I use it on both of my OnePlus.
In my OP 3T with a 7.1.2 RR Rom I´m using BeansGAPPS Mini, so I should use the Beans package provided in your OneDrive folder?
Thanks in advance.
Click to expand...
Click to collapse
If you read above .. it's just a replacement for the setupwizard.
If you install opengapps and the setupwizard is crashing reboot into TWRP again and install this package above - just to fix setupwizard only.
Of course you can install complete beans gapps too.
Cheers

followmsi said:
If you read above .. it's just a replacement for the setupwizard.
If you install opengapps and the setupwizard is crashing reboot into TWRP again and install this package above - just to fix setupwizard only.
Of course you can install complete beans gapps too.
Cheers
Click to expand...
Click to collapse
Ok, let´s give it a try and post results here.
Cheers!!

followmsi said:
If you read above .. it's just a replacement for the setupwizard.
If you install opengapps and the setupwizard is crashing reboot into TWRP again and install this package above - just to fix setupwizard only.
Of course you can install complete beans gapps too.
Cheers
Click to expand...
Click to collapse
Full wipe and ROM installed with latest Beans Gapps without any kind of problems. I love RR and it works like a charm for the moment. I was using the tablet for at least 4 hours I think with all my daily apps installed (arround 40 apps) Substratum and rooted with latest Magisk.
I have a question, the stock kernel can handle usb-otg? And what formats can handle, like NTFS, exFAT, etc? Sorry for dumb question but I forget all my USB at the office....
Really thanks for your work mate!!!

Istvan_86 said:
Full wipe and ROM installed with latest Beans Gapps without any kind of problems. I love RR and it works like a charm for the moment. I was using the tablet for at least 4 hours I think with all my daily apps installed (arround 40 apps) Substratum and rooted with latest Magisk.
I have a question, the stock kernel can handle usb-otg? And what formats can handle, like NTFS, exFAT, etc? Sorry for dumb question but I forget all my USB at the office....
Really thanks for your work mate!!!
Click to expand...
Click to collapse
The kernel supports NTFS and F2FS .. exFAT via fuse only.
Have a try to mount your drive via console.
Maybe tricky ..
To make it short ..
Pls use Paragon drivers or other tools for exFAT and NTFS.
Maybe use "stick mount" too.
These tools offer "real" Android integration .. that what you want !
Cheers
EDIT: Because of TWRP config, the ntfs-3g user space driver is also included in the RR ROM.
https://github.com/followmsi/androi...mmit/01918bd2e07ae491eaae9a37af4175d375c18c86
Type in terminal ..
mount.ntfs /dev/yourdevice
To mount via kernel driver you just type. ..
mount -t ntfs /dev/yourdevice
Have a try ..
But as said above .. to have it "comfortable" use proper Android tools

New version arrived ...
RR-N-v5.8.3-20170511-dragon-Unofficial-followmsi.zip
Changes:
- Latest RR changes
- Latest kernel changes
- Fix for "Wifi direct"
- Enabled Doze (Ambient light)
Enjoy ..

Due to several reasons I have removed the vendor.img from the ROM now !
I have changed the first page accordingly ...
The required (stock) vendor.img is not part of the ROM installer !
You will find a copy inside the download folder.
Installation:
1. Boot into TWRP
2. Wipe system, cache, dalvik and data. (Not required if you upgrade from previous build)
3. Install ROM ...
4. Install current stock vendor.img (flash via TWRP)
5. install opengapps or beansgapps (arm64) (optional)
6. install SuperSU.zip and/or Magisk.zip
7. Reboot into system ..
Thanks for your understanding ..

followmsi said:
Due to several reasons I have removed the vendor.img from the ROM now !
I have changed the first page accordingly ...
The required (stock) vendor.img is not part of the ROM installer !
You will find a copy inside the download folder.
Installation:
1. Boot into TWRP
2. Wipe system, cache, dalvik and data. (Not required if you upgrade from previous build)
3. Install ROM ...
4. Install current stock vendor.img (flash via TWRP)
5. install opengapps or beansgapps (arm64) (optional)
6. install SuperSU.zip and/or Magisk.zip
7. Reboot into system ..
Thanks for your understanding ..
Click to expand...
Click to collapse
Hello and thanks for updating the ROM,
So in order to flash the latest update after install the "vendor_N2G47O_2017-05.img" I must flash the "vendor_N2G47O_2017-05.img" right?
Cheers!!!

Istvan_86 said:
Hello and thanks for updating the ROM,
So in order to flash the latest update after install the "vendor_N2G47O_2017-05.img" I must flash the "vendor_N2G47O_2017-05.img" right?
Cheers!!!
Click to expand...
Click to collapse
No .. this is a copy of current stock vendor.img file.
And if you have current vendor.img now, you don't need to install again.
Sent from my AOSP on Manta using Tapatalk