Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Sony Xperia T (mint)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
For stock rom:
http://forum.xda-developers.com/showthread.php?t=2657190
Click to expand...
Click to collapse
XDA:DevDB Information
[mint][CWM Advanced Edition] PhilZ Touch, a Tool/Utility for the Sony Xperia T
Contributors
Phil3759, DooMLoRD, [NUT]
Version Information
Status: Stable
Created 2014-03-29
Last Updated 2014-03-29
Phil3759 said:
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Click to expand...
Click to collapse
This rules that this has been ported, as I use the PhilzTouch on my Galaxy Tab2. I even donated a few $$ to him!
One question, with the shared kernel "feature" of the T, how did you avoid having it revert back to stock CWMrecovery anytime one flashes a new ROM?
Regardless, I'll try this out tonight.
Hey i always wanted this to get ported! Im using the leaked 4.3 rom and it does work but it only boots into the recovery everytime. Is this a bug or is there a way to fix this?
hhamzah49 said:
Hey i always wanted this to get ported! Im using the leaked 4.3 rom and it does work but it only boots into the recovery everytime. Is this a bug or is there a way to fix this?
Click to expand...
Click to collapse
It will be repacked into other kernels later...
Sent from my C6902 using xda app-developers app
So how do I go about installing this?
Is it as simple as boot the "T" into flashboot mode and running
fastboot -i 0xfce flash boot philz_touch_6.09.3-mint.img
But I'd rather not blow away my phone if this is wrong.
Can I use this for the xperia V, too ?
alex m. said:
Can I use this for the xperia V, too ?
Click to expand...
Click to collapse
No
Sent from my LT30p using Tapatalk
Is there a trick to using PhilzTouch on the T to avoid the shared kernel?
I installed it via "flashboot boot philz.img" and at first glance, it seems to work the same as on my Galaxy Tab 2.
But then it turns out that its not really useable.
a) I was unable to boot back into my normal ROM. Rebooting always brought it back to PhilzTouch.
b) Even if I could have found a way to boot my phone, it turns out that PhilzTouch recovery was overwritten by the stock recovery as soon as I installed a newer CM nightly which I tend to do nightly.
hi all
can i use for TX ? do i need UL or not ? thanks
How to install this recovery?
fastboot flash boot boot.img gives me each time a reboot in recovery
fastboot flash recovery boot.img gives me an error.
Anyone got this working?
Sent from my Xperia T using xda app-developers app
Thanks alot! Used it to get root on the new 4.3 update:good::good:
silasje1 said:
Thanks alot! Used it to get root on the new 4.3 update:good::good:
Click to expand...
Click to collapse
Would you please share how you did it? A how-to would be great including which ROM you came from and all the steps in clear chronological order.
zilboris said:
Would you please share how you did it? A how-to would be great including which ROM you came from and all the steps in clear chronological order.
Click to expand...
Click to collapse
You need Unlocked Boatloader at first!
1. install the 4.3 rom (any you like). Flashing the FTF with everything included
2. Flash this CWM recovery and install SU zip
3. flash FTF and exclude all except KERNEL.
Done! (limited time to write so made it short)
@Phil3759
@steveboss is reporting an extremely sensitive touch interface, is there any way you can confirm it is working out of the ordinary?
[NUT] said:
@Phil3759
@steveboss is reporting an extremely sensitive touch interface, is there any way you can confirm it is working out of the ordinary?
Click to expand...
Click to collapse
I need video of this "extremely..."
Phil3759 said:
I need video of this "extremely..."
Click to expand...
Click to collapse
Hello, I send you video tomorrow
@steveboss where's the video?
@Phil3759
I'm having trouble to get philz to recognize the internal sdcard partition (its a real partition, not part of userdata)... what ever I try, it just keeps failing...
Do you have a possibility to build philz based on the CM10.1 or the freexperia 'jellybean' repo for this device?
I'm starting to suspect the CM10.2 repo might contain some issues as it was put together with pure CM in mind, which might make it incompatible with the stock sony JB4.3 kernel...
The Xperia T made a jump from JB4.1.2 to JB4.3 in one step up, receiving it only a month or so ago, while the CM10.2 repo has been around for far longer...
The 'original' locked bootloader package has made the same jump up recently and CWM started causing problems for it's users too.
[NUT] said:
@steveboss where's the video?
Click to expand...
Click to collapse
I`am sorry, I don`t have any camera now, maybe at weekend
[NUT] said:
@steveboss where's the video?
@Phil3759
I'm having trouble to get philz to recognize the internal sdcard partition (its a real partition, not part of userdata)... what ever I try, it just keeps failing...
Do you have a possibility to build philz based on the CM10.1 or the freexperia 'jellybean' repo for this device?
I'm starting to suspect the CM10.2 repo might contain some issues as it was put together with pure CM in mind, which might make it incompatible with the stock sony JB4.3 kernel...
The Xperia T made a jump from JB4.1.2 to JB4.3 in one step up, receiving it only a month or so ago, while the CM10.2 repo has been around for far longer...
The 'original' locked bootloader package has made the same jump up recently and CWM started causing problems for it's users too.
Click to expand...
Click to collapse
Look at the fireball device repo (fstab file) to use vold with real sdcard partition
Else use compatibility recoveryonly option in fstab with real blk device path
Phil3759 said:
Look at the fireball device repo (fstab file) to use vold with real sdcard partition
Else use compatibility recoveryonly option in fstab with real blk device path
Click to expand...
Click to collapse
ooh, that could be the trick :cyclops:
Thanks for the hint :good:
I'll update you once I know if it works or not.
Related
I have successfully ported ClockworkMod for Galaxy Ace.
Almost everything is working, including flashing boot and recovery images and full backup and restore.
TO-DO List:
Build flashable zip for Froyo.
Fix power-off (as it does a full power off, until you keep pressed power button, then it gets back to recovery).
Try to make a unified version for Froyo and Gingerbread basebands.
Get official support (already notified Koush).
Changelog:
Alpha
Initial release
Beta
Custom kernel with ext4 support (for Froyo and Gingerbread versions).
USB Mass Storage Mode fixed (need's testing on Gingerbread).
All Ace versions should work (using proper build).
Gamma
Fixed reboot out of recovery.
Reverted to 3.x version of CWM, as 4.x is being actively developed (breaking things).
Flashing method:
Flashable zips (currently only for Gingerbread):
Flash attached ClockworkMod-ginger-gamma-signed.zip from any recovery (stock or CWM).
ODIN (alternative method, currently only method for Froyo):
Flash attached recovery_gamma_[your version].tar from ODIN. Put Cooper.ods in proper field, and recovery in PDA field. Leave other fields blank and ignore both errors.
Please port it to the latest 2.3.4 and the european froyo version.
Thanks
Sent from my GT-S5830 using XDA App
manju991 said:
Please port it to the latest 2.3.4 and the european froyo version.
Click to expand...
Click to collapse
Already in my TO-DO list.
Cool... Thanks mate..
Sent from my GT-S5830 using XDA App
you have to fixing framebuffer issue?
Sent from my ViewPad7 using XDA App
digkong said:
Dude why don't u work with the other two developer working on CWM...the work will be lot faster and lot more stable..
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
+1.... Instead of working separately and trying to port CWM, if you, dee000000 and PabloPL collaborate then the work would complete faster and due to the combined effort i am sure that it would be better and also save time and effort of all 3 of you.
ilarrain said:
I have successfully ported ClockworkMod for the american version of Galaxy Ace, running Froyo build of Samsung stock firmware.
Almost everything is working, including flashing boot and recovery images and full backup and restore.
Functions not working:
Formatting partitions.
Reboot recovery (you'll probably end in a boot loop, booting recovery everytime, until you flash an stock recovery in ODIN).
Enabling USB-Mass-Storage mode
Changes pending:
Build for GT-S5830 (european Ace).
Add EXT4 support (custom kernel or module loading).
Build flashable zip.
Code cleanup.
Publish full sources.
Fix boot loop (should send recovery-done to the bootloader).
Tomorrow I will continue development.
Recovery image (for GT-S5830L) attached in a tar (you can flash in ODIN if you like).
Please consider buying me a beer with the donate button on the left side, under my name.
Click to expand...
Click to collapse
Hi, great work. Could you share fix for graphics bug? How did you tested nandroid backup of boot/recovery? (could you test it on my CMW?).
If you want, i can send you what changes i've made, so then we would have fully working recovery for Ace.
Strange, USB Mass Storage mode is working for me (in my recovery). Didn't had to do any changes to make it working.
Edit 1:
I've fixed reboot problem.
PabloPL said:
Hi, great work. Could you share fix for graphics bug? How did you tested nandroid backup of boot/recovery? (could you test it on my CMW?).
If you want, i can send you what changes i've made, so then we would have fully working recovery for Ace.
Strange, USB Mass Storage mode is working for me (in my recovery). Didn't had to do any changes to make it working.
Click to expand...
Click to collapse
also strange on framebuffer. my changes on graphics.c is working good for galaxy mini.
i see in the first post the clockworkmod background is not shown in ace.
Sent from my ViewPad7 using XDA App
tj_style said:
also strange on framebuffer. my changes on graphics.c is working good for galaxy mini.
i see in the first post the clockworkmod background is not shown in ace.
Sent from my ViewPad7 using XDA App
Click to expand...
Click to collapse
THE background is working OK. I've used your fix, but I had to force 24bpp mode.
I will share my sources when I arrive home later today.
PabloPL: great! As soon as I share my sources, we can collaborate to get it working for all ace version ASAP.
ilarrain said:
THE background is working OK. I've used your fix, but I had to force 24bpp mode.
I will share my sources when I arrive home later today.
PabloPL: great! As soon as I share my sources, we can collaborate to get it working for all ace version ASAP.
Click to expand...
Click to collapse
using my fix on github?
will be more progress if you collaborating too on porting recovery for our device.
backup & restore seems okay, but i've bricked my galaxy mini when flashing rom via update.zip. i think it's because write_raw_image("/tmp/boot.img", "boot"), command in update script.
are you have to testing flash update.zip on your recovery?
tj_style said:
using my fix on github?
will be more progress if you collaborating too on porting recovery for our device.
backup & restore seems okay, but i've bricked my galaxy mini when flashing rom via update.zip. i think it's because write_raw_image("/tmp/boot.img", "boot"), command in update script.
are you have to testing flash update.zip on your recovery?
Click to expand...
Click to collapse
I've tested backup+restore. I've also tested "flash_image recovery recovery.img". Doing it from a zip shouldn't be so different.
Sharing my sources is on my original todo list since the beginning, I've just didn't have enough time.
Sources will be in http://github.com/ilarrain.
I think the fix for ace's bml flashing is already there.
Sent from my GT-S5830L using XDA App
ilarrain said:
I've tested backup+restore. I've also tested "flash_image recovery recovery.img". Doing it from a zip shouldn't be so different.
Sharing my sources is on my original todo list since the beginning, I've just didn't have enough time.
Sources will be in http://github.com/ilarrain.
I think the fix for ace's bml flashing is already there.
Sent from my GT-S5830L using XDA App
Click to expand...
Click to collapse
okay, great..
we will discusing again tomorrow, I must sleep now.
btw, maybe better to converting rfs to ext4, for module, we can use from i9000 source.
also, better to merge your changes and PabloPL changes with ifdef, it will more easy when updating from cyanogenmod source.
you want to collaborate in my repo? i will add you and other collaborator to the project.
ilarrain said:
I've tested backup+restore. I've also tested "flash_image recovery recovery.img". Doing it from a zip shouldn't be so different.
Sharing my sources is on my original todo list since the beginning, I've just didn't have enough time.
Sources will be in http://github.com/ilarrain.
I think the fix for ace's bml flashing is already there.
Sent from my GT-S5830L using XDA App
Click to expand...
Click to collapse
Looked at your changes and they looks like the same as mine, so nandroid backup for boot/recovery should also work in my sources.
Now the only think is to fix reboot loop (i thought that i've fixed it - tested with fakeflash recovery, but after flashing it wouldn't worked:/). Will look at it tomorrow.
looks cool o tried it on my froyo with europe firm work great..
but like u just said once u go in recovery you will never go out
nice work.
10x
Full sources published, look first page.
izador said:
looks cool o tried it on my froyo with europe firm work great..
but like u just said once u go in recovery you will never go out
nice work.
10x
Click to expand...
Click to collapse
Great!!! So we need less versions to mantain: froyo and gingerbread, no matter the ace version.
i also create a backup for recovery.img using yours tar for froyo, if some one needs it
after he tried to flash the recovery and have bootloop.
http://17cb3171.yyv.co
*its only for froyo
izador said:
i also create a backup for recovery.img using yours tar for froyo, if some one needs it
after he tried to flash the recovery and have bootloop.
http://17cb3171.yyv.co
*its only for froyo
Click to expand...
Click to collapse
If you have bootlop in recovery, just reboot (while in adb shell)
Code:
reboot recovery_done
excited for this..
good work guys..
After extracting CF-Root's zImage, I have found inside killrecovery.sh:
Code:
..
rm /cache/recovery/command
rm /cache/update.zip
touch /tmp/.ignorebootmessage
..
I hope this information useful for developer.
Sent from my GT-S5830 using XDA App
if i create backup with yours CW can i use it ?
it will work ?
did some one try it ?
partition us working good.
i tried to crate partition with CW, work good.
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
To take a screen shot, just slide left
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Xperia Z - CM kernel (yuga)
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
Xperia Z stock kernels
http://forum.xda-developers.com/showthread.php?p=46613286
Click to expand...
Click to collapse
XDA:DevDB Information
[yuga][CWM Advanced Edition] PhilZ Touch, Tool/Utility for the Sony Xperia Z
Contributors
Phil3759, shoey63, [NUT], DooMLoRD
Version Information
Status: Stable
Created 2014-03-29
Last Updated 2014-10-11
Cwm touch recovery sounds awesome. I'm not brave enough to try it yet though , until someone else has
Sent from my C6603 using XDA Premium 4 mobile app
So just flash with fastboot?
Sent from my C6602 using xda app-developers app
shoey63 said:
So just flash with fastboot?
Sent from my C6602 using xda app-developers app
Click to expand...
Click to collapse
It is the recovery.img outputted by cm-10.1 build
So, if you have a shared boot/recovery kernel, it will work only on cm-10.1 ROMs until someone repacks it for stock ROMs
If you have a dedicated recovery partition, you can flash without much trouble, in theory...
But, I am not responsible of any damage. This is mainly for devs or advanced users knowing what I am talking about
Consider it as really early preview until it is better tested.
@[NUT] compiled open source version and all was working he said. So, I do not expect big issues
Phil3759 said:
It is the recovery.img outputted by cm-10.1 build
So, if you have a shared boot/recovery kernel, it will work only on cm-10.1 ROMs until someone repacks it for stock ROMs
If you have a dedicated recovery partition, you can flash without much trouble, in theory...
But, I am not responsible of any damage. This is mainly for devs or advanced users knowing what I am talking about
Consider it as really early preview until it is better tested.
@[NUT] compiled open source version and all was working he said. So, I do not expect big issues
Click to expand...
Click to collapse
I can repack it into my kernel. I'll test it and let you know.
Thank you!
Don't worry Phil, I know how to get myself out of trouble
Looking forward to @alnikki25k's repack:thumbup:
Sent from my C6602 using xda app-developers app
shoey63 said:
Don't worry Phil, I know how to get myself out of trouble
Sent from my C6602 using xda app-developers app
Click to expand...
Click to collapse
Happy to see you back @shoey63
You did a huge debugging and contributed a lot to make this project last, when it started timidly a year ago
What you can do is:
fastboot flash it or in cwm if possible
Boot into recovery. Give me a feedback and then flash back your kernel for your daily ROM
But don't kill me if your XperiaZ dies
All good Phil:thumbup: Just need touch working
Sent from my C6602 using xda app-developers app
Yay!
I'll get a locked bootloader version out as soon as I get home.
Thanks!
Sent from my C6603 using xda app-developers app
Re-packed As reported, touch does not work.
I'll see what else is not working.
Also, the Aroma File Manager needs an additional zip no?
EDIT: Looks like the touch is registered. I get a haptic feedback when I tap anywhere on the screen. But just can't use it.
alnikki25k said:
Re-packed As reported, touch does not work.
I'll see what else is not working.
Also, the Aroma File Manager needs an additional zip no?
EDIT: Looks like the touch is registered. I get a haptic feedback when I tap anywhere on the screen. But just can't use it.
Click to expand...
Click to collapse
Great it boots and works
Maybe touch needs extra kernel enablers or echo to some /sys/.../touch path
Unless the device has flipped x/y axis. In that case, touch events should register but not considered most of the time
If screen reacts to touch under some parts/scrolls, it is second case, else first
Phil3759 said:
Great it boots and works
Maybe touch needs extra kernel enablers or echo to some /sys/.../touch path
Unless the device has flipped x/y axis. In that case, touch events should register but not considered most of the time
If screen reacts to touch under some parts/scrolls, it is second case, else first
Click to expand...
Click to collapse
Seems like the first case. It does not react except for the haptic feedback. However, when I open the log in the advanced menu and it prompts to press any key to continue, touching the screen registers as a key press and it returns to the previous menu.
EDIT: I could upload TWRP recovery which has touch working if that would help.
alnikki25k said:
Seems like the first case. It does not react except for the haptic feedback. However, when I open the log in the advanced menu and it prompts to press any key to continue, touching the screen registers as a key press and it returns to the previous menu.
EDIT: I could upload TWRP recovery which has touch working if that would help.
Click to expand...
Click to collapse
Humm
Seems like touch is working then, else you won't get any feedback
I will look at TWRP to see if device has flipped or inversed axis
Else, I will release a touch debug version to see what's going
If you need the TWRP release for this phone
https://mega.co.nz/#!IkI2XZCS!QeEcmBUWlbD7rBER8502Sx-cJ6lX_aIJq9aVcuGyNgo
Click to expand...
Click to collapse
@Phil3759
http://nut.xperia-files.com/
XZDualRecovery 2.7.10 BETA contains your PhilZ Touch Recovery. It (not very surprisingly) has the touch screen bug described as above by others. This version is now working fine on locked bootloader devices, except the bugs of course
[NUT] said:
@Phil3759
http://nut.xperia-files.com/
XZDualRecovery 2.7.10 BETA contains your PhilZ Touch Recovery. It (not very surprisingly) has the touch screen bug described as above by others. This version is now working fine on locked bootloader devices, except the bugs of course
Click to expand...
Click to collapse
Thank you a lot (out of my :good: today)
I will look at touch later
Le me know about any other bugs
Meanwhile, can someone repack with twrp recovery kernel and ramdisk files (init, *.rc and files in root) to see if it fixes touch
That's to be sure it is not a kernel issue not having touch enabled
Phil3759 said:
Thank you a lot (out of my :good: today)
I will look at touch later
Le me know about any other bugs
Meanwhile, can someone repack with twrp recovery kernel and ramdisk files (init, *.rc and files in root) to see if it fixes touch
That's to be sure it is not a kernel issue not having touch enabled
Click to expand...
Click to collapse
Will work on that now.
alnikki25k said:
Will work on that now.
Click to expand...
Click to collapse
Great
That would make my life easier to debug it
Phil3759 said:
Great
That would make my life easier to debug it
Click to expand...
Click to collapse
Ok, I replaced the init, *.rc files and same problem. No touch response. Anything else I need to replace from TWRP?
alnikki25k said:
Ok, I replaced the init, *.rc files and same problem. No touch response. Anything else I need to replace from TWRP?
Click to expand...
Click to collapse
you replaced the kernel too? and all files in root?
FEEL FREE TO DONATE US FOR ALL WE'RE DOING FOR YOU!
For general discussions, bug reports and FAQ, write HERE!
Credits:
MoltenMotherBoard team!
Downloads:
CWM Recovery | Code.Google
Full sources:
MoltenMotherBoard sources: MoltenMotherBoard | Github
CyanogenMod sources: CyanogenMod | Github
Kernel: lge-kernel-p880 | Github
Changelog:
20131126
Associated to Power Button the action SELECT_ITEM
From 6.0.4.4 to 6.0.4.5
Code updates from CyanogenMod, Google
20131120
First release
Issues:
Do you want to report an issue? Do it here!
In order to do it, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue.
Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different
kernel, mod, plugins and dependencies we didn't tell to use).
General Questions: MoltenMotherBoard Projects | General Questions and Info
Official Mantainer(s): Mackief, ItachiSama, p4c0
Installation guide:
[Method 1° ~ fastboot]
Code:
$ adb reboot oem-unlock
$ fastboot flash recovery /PATH-TO-THE-IMG-FOLDER-ON-YOUR-COMPUTER/cwm.img
$ fastboot reboot
[Method 2° ~ adb] (put the recovery.img in your sdcard)
Code:
$ adb shell
$ su
# cat /sdcard/cwm.img > /dev/block/mmcblk0p1
# sync
# exit
$ exit
With CyanDelta work?
negativman said:
With CyanDelta work?
Click to expand...
Click to collapse
Obviously it does. In fact, CyanDelta only make a flashable package, that you have to install manually from recovery. Then, yep.
BTW, now want also to make for you a Touch version of this CWM.
mackief said:
Obviously it does. In fact, CyanDelta only make a flashable package, that you have to install manually from recovery. Then, yep.
BTW, now want also to make for you a Touch version of this CWM.
Click to expand...
Click to collapse
cyandelta installs the zip automatically too, if the recovery supports openrecovery script. TWPR does, and so does the CWM based recovery in CM sources. the original CWM from rom manager does not work properly AFAIK
gandhar said:
cyandelta installs the zip automatically too, if the recovery supports openrecovery script. TWPR does, and so does the CWM based recovery in CM sources. the original CWM from rom manager does not work properly AFAIK
Click to expand...
Click to collapse
It could be that CWM from Rom-Manager is out-to-date.
The only way it could not work, is because thi updated CWM still need some merging and commits by the team. Just try and let us know!
mackief said:
It could be that CWM from Rom-Manager is out-to-date.
The only way it could not work, is because thi updated CWM still need some merging and commits by the team. Just try and let us know!
Click to expand...
Click to collapse
i had last tried a long time back, don't know and don't care about the current condition
i like TWRP much more.
just saw your post on g+ about a ubuntu touch port, any progress on that? i am very interested in that.
mackief said:
Obviously it does. In fact, CyanDelta only make a flashable package, that you have to install manually from recovery. Then, yep.
BTW, now want also to make for you a Touch version of this CWM.
Click to expand...
Click to collapse
Will another Nightly today or tomorrow, check whether a set CyanDelta!
Oh yes, the touch recovery - it would be very great. TWRP I personally do not like it. And the one that I have now for our smartphone is locked Rom Manager!
gandhar said:
i had last tried a long time back, don't know and don't care about the current condition
i like TWRP much more.
just saw your post on g+ about a ubuntu touch port, any progress on that? i am very interested in that.
Click to expand...
Click to collapse
About Ubuntu, it's not that simple.
It seems 4X kernel from CM team does not load into the system.
Unfortunately, I cannot debug which is the problem surely: but I'm sure I'll return on it in a week at least. I've some thoughts about how to make it loading and booting next to the kernel!
negativman said:
Will another Nightly today or tomorrow, check whether a set CyanDelta!
Oh yes, the touch recovery - it would be very great. TWRP I personally do not like it. And the one that I have now for our smartphone is locked Rom Manager!
Click to expand...
Click to collapse
As I understood CWM Touch is buildable only through clockworkmod-builder, and I'll do it. The only problem is that in that site, the sources are out-to-date, linked to 4.3 branches.
So, we have to wait, till CWM will update the sources linked in the site to build a 6.0.4.4 touch recovery.
mackief said:
As I understood CWM Touch is buildable only through clockworkmod-builder, and I'll do it. The only problem is that in that site, the sources are out-to-date, linked to 4.3 branches.
So, we have to wait, till CWM will update the sources linked in the site to build a 6.0.4.4 touch recovery.
Click to expand...
Click to collapse
Do not quite understand! Surely there's a new CWM 6.0.4.4. You can unlock it from Rom Manager? http://forum.xda-developers.com/showthread.php?t=2523732
Hey.
Just built a new build of CWM, now coded 6.0.4.5.
In this new release, CM team has apported an important fix - as also TWRP team has done - that avoid any issue while flashing some of KitKat based roms.
BTW, made a test build of CM11, gonna test it
mackief said:
Hey.
Just built a new build of CWM, now coded 6.0.4.5.
In this new release, CM team has apported an important fix - as also TWRP team has done - that avoid any issue while flashing some of KitKat based roms.
BTW, made a test build of CM11, gonna test it
Click to expand...
Click to collapse
Feel free to take us alpha testers
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
[email protected] said:
Feel free to take us alpha testers
Sent from my Optimus 4X HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Just pulled a log, as it does not boot.
Having some issues related to gralloc. Need to debug!
mackief said:
[...]
So, we have to wait, till CWM will update the sources linked in the site to build a 6.0.4.4 touch recovery.
Click to expand...
Click to collapse
Just take a look at my sig we already have 6.0.4.4 touch
laufersteppenwolf said:
Just take a look at my sig we already have 6.0.4.4 touch
Click to expand...
Click to collapse
Oh, marvolous!
But how can I build it? Is it buildable from source?
If you don't want me to build it, just update your port to 6.0.4.5. Ty, dude!
laufersteppenwolf said:
Just take a look at my sig we already have 6.0.4.4 touch
Click to expand...
Click to collapse
When he unlocked from Rom Manager?
mackief said:
Oh, marvolous!
But how can I build it? Is it buildable from source?
If you don't want me to build it, just update your port to 6.0.4.5. Ty, dude!
Click to expand...
Click to collapse
I will update it ASAP
negativman said:
When he unlocked from Rom Manager?
Click to expand...
Click to collapse
Not at all, as only official device maintainers can. And as I am not a maintainer, I can't
Just released new build of CWM.
Changelog:
Associated to Power Button the action SELECT_ITEM
From 6.0.4.4 to 6.0.4.5
Code updates from CyanogenMod, Google
Follow us on Google+, Facebook & Twitter!
Cheers.
We recently changed our Issue Tracker URL.
If you want to report a bug, please, follow the new instructions:
· Issue Tracker URL: Issues | Github
· Important notes: go to the linked URL, create a new issue, choosing correct labels corrisponding to: Device/OS which you're using, ROM/project you're on, kind of issue. Also, please, be sure you're running the ROM/project in the exact way we've provided it to you (do not create issues if you're using different kernel, mod, plugins and dependencies we didn't tell to use).
Development for this project has been totally and officially stopped, as no more needed.
Greetings,
MoltenMotherBoard team.
Actual:
I use CyanogenMod and Mokee teams sources and add some changes to device config.
Latest CM12 builds
СМ12.1 build 24.07.2015
normal- https://yadi.sk/d/l0sQrKeXi4rpT
experimental - https://yadi.sk/d/Sus83ATLi4rjv (aptx bt, mako gps)
news: - kernel, config updates . SoundControl removed, revert to deodex.
revert cm12.1 BT - https://yadi.sk/d/DHjDF-fAi4sQE
СМ 12.1 build 21/07/2015
normal - https://yadi.sk/d/EwsQB88Qhz7RD
experimental - https://yadi.sk/d/X07SjR3Fhz7Rm (GPS from nexus4, APTX BT)
+fixed updater-script - added ifelse(is_mounted("/system"), unmount("/system"));
СМ12.1 build 13.07.2015 - https://yadi.sk/d/CtPkfkpchq2Yb
СМ12.1 build 13.07.2015 w aptx support(experimental) - https://yadi.sk/d/LRV6F7N2hq2bS
fixed: wifi, BT, boot light, recovery, offline charging
Cm 12.1 03.07.2015 build - https://yadi.sk/d/GG3gFTtYhe3dQ
Changes in kernel, libs, binaries, configs
Tested - worked/
CM12.1 11.06.2015 build - https://yadi.sk/d/VyIKm27xhCdhE
CM12.1 20.05.2015 build - https://yadi.sk/d/WnR7d73mgkzcX
CM12.1 28.04.2015 build - https://yadi.sk/d/bn_IsRx1gJaRs
kernel w soundcontrol v3, many kernel and ril updates from см team
CM12.1 20.04.2015 build - https://yadi.sk/d/xiKPp0EBg7Kyo
kernel w soundcontrol v3, updates from см team
gps libs from мако(nexus 4) (possible gps work better) for recovery - https://yadi.sk/d/JU39SUbPg7Kmu
PAC 5 20.04.2015 build from neosuslik - https://drive.google.com/uc?id=0B6kPZoGYA4tfaFhOdjIxenNYbnM&export=download
Mokee 5.1 12.04.2015 build from neosuslik - https://docs.google.com/uc?id=0B6kPZoGYA4tfSGdlNldodnhuVTQ&export=download
CM12.1 build(06.04.2015) tested - https://yadi.sk/d/bzBHxTDmfoyck
move apps to sd fix added, dual recovery
kernel w SoundControl v3 for cm12.1 - https://yadi.sk/d/xPWTpM4ufpgnA - you need faux sound control or other app to tweak sound levels.
CM12 build (01.04.2015), ODEXed, fix for move apps to sdcard - https://yadi.sk/d/93AA69qtffk7Q
CM12 build (12.03.2015), ODEXed - https://yadi.sk/d/dTadZHj_fCZKN
CM12 build (04/03/2015), ODEXed - https://yadi.sk/d/K20AhXQ4f2ha9
CM12 build (28/02/2015) - https://yadi.sk/d/GGDHoe76ewFe4
CM12 build (20/02/2015) - https://yadi.sk/d/mmi7ic1Eeo5Eh
news:
new cm12 updates, bugfixes and bugs
Mokee5 build (25/02/2015) - https://yadi.sk/d/yI-cBxQheskpk
How to install:
a)
1. flash boot.img from archive
2. boot to recovery and flash firmware archive
b) reboot to recovery and flash firmware archive
Old(not actual now):
Big thanks to thomas1991_12 and pabx. This Rom based on their work.
English screenshots - http://forum.xda-developers.com/showpost.php?p=56982062&postcount=77
More Russian screenshots - http://4pda.ru/forum/index.php?showtopic=475149&st=9040&view=findpost&p=35853307
Whats worked: see original theme - http://forum.xda-developers.com/xperia-z/orig-development/exp-lollipop-xperia-z-t2929369
Latest CM12 port(qsnc 09.02.2015 build based) - https://yadi.sk/d/QcxE0x0WedRUd
Updated boot.img w philz recovery and vibro for 09.02.2015 - https://yadi.sk/d/anPzmPL0eeiCg
CM12 for ZR, cm-12-20150112-INFECTED-yuga based:
CM12 for ZR: cm-12-20150112-INFECTED-yuga.zip port - https://yadi.sk/d/L_eIwqujdz6sb
30.12.2014 Update, pabx 5.0.8 build based:
boot - https://yadi.sk/d/BMTyrqVpdnfDQ
system - https://yadi.sk/d/uK10pxZSdnfDa
fix - https://yadi.sk/d/4CBtWW7wdnfDJ
20.12.2014 Update
system.img from 20.12.2014 - https://yadi.sk/d/LObcDGPOdXW4B
boot.img - https://yadi.sk/d/ynTfhBdHdXW3v
fix(Xperia ZR specified files (zr camera libs, sensors.conf etc, you need install it via twrp recovery before boot system)) - https://yadi.sk/d/GU_LI9S2dYwya
04.12.2014 Update:
system.img from 4.12.2014 - https://yadi.sk/d/yeqUq35rdAgGG
boot.img - https://yadi.sk/d/jXkoWjC4dAgFZ
fix(Xperia ZR specified files (zr camera libs, sensors.conf etc, you need install it via twrp recovery before boot system)) - https://yadi.sk/d/8fWVGGj5dAgHM
GAPPS - https://yadi.sk/d/wxoFZUWidAgJr
Worked SuperSu - http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
***************************************************
Installing:
flash via fastboot or flashtool (in fastboot mode) boot and system images
Fastboot:
fastboot flash boot boot.img
fastboot flash system system.img
flash fix(recommended before first boot), supersu, gapps ...etc via recovery
if no internal sdcard found try this(in adb or terminal console):
su
restorecon -FR /data/media/0
***************************************************
Google Apps installation
After booting your phone for the first time, download the gapps package and push it to /sdcard using adb (or MTP):
adb push gapps_50_yuga_004-00cb.tgz /sdcard/
adb reboot
Your phone will now reboot and automatically install gapps during the boot process. (note that your phone will reboot twice - this is normal).
recommend to keep the gapps package in /sdcard/ after the installation finished: Upgrading to a new release will erase your existing gapps installation - but if the package is still present in /sdcard/, it will be automatically installed during the first boot.
*************************************************
Thank you for your effort Looking forward to testing this ROM upon upload. And i know it sounds silly, but an english version will be uploaded right???
I've been checking XDA like 10 times a day for the past two weeks hoping for this, and now it's finally here!!! You sir, deserve a medal.
I have a question, and I'm not sure if it's supposed to go here or the Q&A thread, since it's not specifically related to this ROM, per se. I just want to know how you built this; where did you get the device tree/binaries (not really sure what I'm talking about here, I've only read the building tutorials, don't really understand them fully)? AFAIK, Sony hasn't released them for the ZR, so how'd you do it? Is there some way to port them from other devices or something? Even a reference point to start searching would be great.
Thank you for your work!
P.S. Also, does this question belong in the Q&A thread or not?
Even i was wondering, but i thought perhaps it's only right to give the dev some time to upload the full details
kash296 said:
Even i was wondering, but i thought perhaps it's only right to give the dev some time to upload the full details
Click to expand...
Click to collapse
Of course, no pressure at all on the dev; I just wanted to say kudos, and thought I might as well ask. [emoji12]
xenius9 said:
Coming soon... Now kernel worked, ROM started, need little fixes.
Big thanks to thomas1991_12 and pabx. This Rom based on their work.
Bad news:
I have no time to develop, rom not work on all ZR-s - need additional kernel developing?(on many ZR models this rom work(on 2 phones work normal now), on other not (on my zr not work properly - mixed image on screen))
Now i have:
Kernel w twrp recovery - https://yadi.sk/d/WJw4gqmqcnLWd
SystemImage (from sony z, need add camera libs in vendor folder and some in etc/firmware and fix sensors.conf - from .283 stock firmware) - https://yadi.sk/d/S0Bh4H8gcmqRv
Xperia ZR specified files - https://yadi.sk/d/VZ8whMhccoCnt - zr camera libs, sensors.conf etc, you can install it via twrp recovery
Installing:
flash via fastboot or flashtool (in fastboot mode) boot and system images
test
Root - flash latest supersu via twrp recovery http://download.chainfire.eu/593/SuperSU/BETA-SuperSU-v2.19.zip
Click to expand...
Click to collapse
Um. So that means right now, it's a list of separate files??? Anyway awesome work.
P.S Sorry abt quoting the whole post, i hate that. But my comment wouldn't make any sense then
Awsome
Everything working fine. Just like stable daily driver rom. Can't say about battery right now.
The only thing missing is root because SuperSU 2.23 dosen't seem to work. I think some kernel modifications will be needed for proper execution of SU binary
BTW Thanks alot .
sshivampp said:
Everything working fine. Just like stable daily driver rom. Can't say about battery right now.
The only thing missing is root because SuperSU 2.23 dosen't seem to work. I think some kernel modifications will be needed for proper execution of SU binary
BTW Thanks alot .
Click to expand...
Click to collapse
RIL works ????? ( Are you able to make calls and receive calls and send messages etc ?)
If you are using this as daily driver then try testing bluetooth, wifi, RIL, mobile internet (2g+3g), camera etc......
I would definitely do all this on weekend....
@Xenius :- HATS OFF MAN.......... Even if it just boots, I would say that it's sheer genius..........
nikhilkaushik said:
RIL works ????? ( Are you able to make calls and receive calls and send messages etc ?)
If you are using this as daily driver then try testing bluetooth, wifi, RIL, mobile internet (2g+3g), camera etc......
I would definitely do all this on weekend....
@Xenius :- HATS OFF MAN.......... Even if it just boots, I would say that it's sheer genius..........
Click to expand...
Click to collapse
I have exaaams You guys are tempting me And what do we do abt Gapps?? Jus download one of the lollipop gapps???
nikhilkaushik said:
RIL works ????? ( Are you able to make calls and receive calls and send messages etc ?)
If you are using this as daily driver then try testing bluetooth, wifi, RIL, mobile internet (2g+3g), camera etc......
I would definitely do all this on weekend....
@Xenius :- HATS OFF MAN.......... Even if it just boots, I would say that it's sheer genius..........
Click to expand...
Click to collapse
Bluetooth is fine except I cannot accept or share file with apk extension
WiFi also seems to be fine till now and yes I can make calls, messages, and can connect to data network.
Camera quality is accepteble (photo preview is kind of buggy )
Till now what I cannot test its GPS as I don't use it. but can provide logcat if anyone wants
Edit: At latest lollipop release for xperia Z (18 November), RIL is broken, atleast in ZR with this kernel, don't know about Z
maybe kernel update will fix this
---------- Post added at 10:49 PM ---------- Previous post was at 10:40 PM ----------
kash296 said:
I have exaaams You guys are tempting me And what do we do abt Gapps?? Jus download one of the lollipop gapps???
Click to expand...
Click to collapse
I suggest exam first
BTW you can download gapps from here
or direct link of one I downloaded here (I don't remember the source page but it was from XDA)
Thanks for the gapps link. Holidays inbetween so it aint a prob for the exams. Downloading the image right now, will try out the bluetooth and see if i too get the same issue
Xenius you are genius. Booted and running smoothly without any FCs.
Sent from my Lollipop for ZR using XDA Free mobile app
.
Man
big tnxfor your awsome work:cyclops:
And can you upload your kernel source? May be developers like @Alx31TLse can build more lollipop roms:fingers-crossed:
Yes i can, now i build new kernel w new ramdisk(w working root).
18.11.2014 firmware working... new kernel too... root working
Files...soon.
All updates added. See 1st post.
xenius9 said:
All updates added. See 1st post.
Click to expand...
Click to collapse
I am having trouble downloading from playstore after flashing gapps.. As there isn't a file manager preinstalled, I'm trying to download one, so that i can get back my old apps which are backed up in the SD card. Anyone else has the same issue abt the play store?
P.S I found out the problem. My Gmail wasn't synced so my account wasn't fully functional. Never mind
kash296 said:
I am having trouble downloading from playstore after flashing gapps.. As there isn't a file manager preinstalled, I'm trying to download one, so that i can get back my old apps which are backed up in the SD card. Anyone else has the same issue abt the play store?
Click to expand...
Click to collapse
I Use adb for apps installation and total commander+adb plugin for any dev deals
you can made small installation zip for recovery w needed apps
xenius9 said:
I Use adb for apps installation and total commander+adb plugin for any dev deals
you can made small installation zip for recovery w needed apps
Click to expand...
Click to collapse
Not so familiar with the adb codes, i've never felt the need to use them. Is the kernel fully permissive? I'd like to know if i can run Viper4android on it.
kash296 said:
Not so familiar with the adb codes, i've never felt the need to use them. Is the kernel fully permissive? I'd like to know if i can run Viper4android on it.
Click to expand...
Click to collapse
Install it and test)))
xenius9 said:
Install it and test)))
Click to expand...
Click to collapse
I'm definitely going to. But why i asked is, cause they were mentioning about permissive kernels. So i thought i'd ask you about that.
And i forgot to ask. The exclamatory symbol on the signal icon ? Why is it coming?? Is it indicating any issue???
Hello,
finally I'm creating this thread where you can discuss about Tangerine, ask questions, post your problems... Without filling the development thread.
You don't know where to post something? This schema will help you.
Questions about the kernel (Does it have ****?) > here
Problems you faced, and/or their solutions > here
Things I should read/know > the development thread
Questions that can be answered by any user (not only by me) > here
Miscellaneous posts > here
In a nutshell, if you have to post something that I have to read, post it in the development thread, otherwise use this thread.
I will not read this thread at all. Or maybe I'll check it every now and then
Development thread: http://forum.xda-developers.com/xperia-sp/orig-development/kernel-tangerine-kernel-v1-t3073297
I've flashed 7.1 on ArchXperiaLP and got bootloop...then have tryed 6.6 a1 and gets bootloop...finally I reflashed ArchXperiaLP from scratch and left tangerine away...can I flash that update safely now? I've used twrp flashed keenel and wipes cache/dalvik previous tries...
Where I'm wrong?
Edit: I'm on c5303 ita
Inviato dal mio Xperia SP utilizzando Tapatalk
Tomoms said:
Settings > Developer Options > Disable HW Overlay
EDIT: now there is a Q&A thread. Please check it to learn where to post what: http://forum.xda-developers.com/xperia-sp/help/qa-tangerine-kernel-t3178801
Click to expand...
Click to collapse
@Tomoms, is there any downside to disabling HW Overlay!? I don't really know what that settings does.
Tuxedo75 said:
I've flashed 7.1 on ArchXperiaLP and got bootloop...then have tryed 6.6 a1 and gets bootloop...finally I reflashed ArchXperiaLP from scratch and left tangerine away...can I flash that update safely now? I've used twrp flashed keenel and wipes cache/dalvik previous tries...
Where I'm wrong?
Edit: I'm on c5303 ita
Inviato dal mio Xperia SP utilizzando Tapatalk
Click to expand...
Click to collapse
Flash updated version 7.2 added support for ArchXperia
Sent from my Xperia SP using Tapatalk
Sorry for being a bit offtopic, but there is any other custom kernel for AICP 10, except Tangerine?
While I love the features of Tangerine and I praise the work of its author, unfortunately the kernel is pretty much useless for me due to its screen/device freezing bug.
Thank you.
varioventus said:
Sorry for being a bit offtopic, but there is any other custom kernel for AICP 10, except Tangerine?
While I love the features of Tangerine and I praise the work of its author, unfortunately the kernel is pretty much useless for me due to its screen/device freezing bug.
Thank you.
Click to expand...
Click to collapse
Sorry to say but there is no kernel atm. Use stock kernel (for me it gives better battery life)
I dunno what's wrong but cant install anything than 6.6 (non a1) and in that way I lost root...
ALL other versions wont works for me, gives me boot the system till temasek(I'm on ArchXperiaLP latest version) app opt and than reboot always(not on same app opt)after some app optinised like latest 7.2_a2 or gives me bootloops...
Any way to fix at least root with some package to flash from twrp?
PS I've flashed the kernel from cm recovery and also from twrp after flashing tangerine(recovery works well) and than flushed cache/dalvik....
Phoenix854 said:
Sorry to say but there is no kernel atm. Use stock kernel (for me it gives better battery life)
Click to expand...
Click to collapse
You're right, stock kernel it's just fine, the only issue is that I can't install FauxSound. I need FauxSound for increasing calls volume, I have a friend I'm talking everyday and I can't hear a thing he's talking on the phone. I'm using Tangerine especially for FauxSound.
Please add version with double tap to wake.
enesas said:
Please add version with double tap to wake.
Click to expand...
Click to collapse
This is a long debated topic where most of us have reached the conclusion where double tap to wake should not be added. This is because the hardware on this phone doesn't support the feature and may cause severe battery drain or other major problems.
Interactive governor is gone on 8.0? D:
@Tomoms
i think screen freezing have come with the updated sources (.207) ..isn't it goes like this (the screen goes yellowish then black then it get normal again ? )
About the screen flickering problem on latest cm12.1 unofficials with t-kernel, @Tomoms said
Settings > Developer Options > Disable HW Overlay
Click to expand...
Click to collapse
I did that but that configuration resets itself to default (HW enabled) everytime I reboot. Anyone else experiencing this?
---------- Post added at 11:49 PM ---------- Previous post was at 11:22 PM ----------
flash- said:
it have alot features that's all ...it have very good governors and some core control stuff along with faux sound feature ...etc ...etc )
these are not presented in stock kernel that comes with the custom ROM
Click to expand...
Click to collapse
@flash- or anyone else that might be able to help with this: what if someone flash Tangerine Kernel and leave it untouched, without tinkering with any of its options. Would it still be an improvement over the Stock Kernel?
These questions (and answers) could be in the first post of the original thread, if I might humbly suggest. It would save people a lot of trouble.
To install v8 can I flash AICP ROM + T Kernel at the same time or need to flash only the rom then reboot and flash T Kernel with Rashr?
Sent from my Xperia SP using Tapatalk
Erik FX8 said:
To install v8 can I flash AICP ROM + T Kernel at the same time or need to flash only the rom then reboot and flash T Kernel with Rashr?
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Yes you can do it at the same time with twrp. I've done it that way and everything works correctly
Sent from my Xperia SP using Tapatalk
flash- said:
@Tomoms
i think screen freezing have come with the updated sources (.207) ..isn't it goes like this (the screen goes yellowish then black then it get normal again ? )
Click to expand...
Click to collapse
I've never had a screen freeze, so it's hard for me to tell.
pilger said:
About the screen flickering problem on latest cm12.1 unofficials with t-kernel, @Tomoms said
I did that but that configuration resets itself to default (HW enabled) everytime I reboot. Anyone else experiencing this?
---------- Post added at 11:49 PM ---------- Previous post was at 11:22 PM ----------
@flash- or anyone else that might be able to help with this: what if someone flash Tangerine Kernel and leave it untouched, without tinkering with any of its options. Would it still be an improvement over the Stock Kernel?
These questions (and answers) could be in the first post of the original thread, if I might humbly suggest. It would save people a lot of trouble.
Click to expand...
Click to collapse
At the moment, Tangerine hasn't got any improved default setting. So flashing it and leaving it untouched doesn't improve the performance. However I'm working on a script that will set the best settings at boot!
It's normal that ater every reboot Disable HW overlay gets disabled. It's not a persistent setting.
Krawzer said:
Interactive governor is gone on 8.0? D:
Click to expand...
Click to collapse
Yes, it's a mistake. I'll readd it in v8.1 but you'll have to wait, beacuse I can't do development until next Monday.
I just flash the update of xenonhd... Wanted to try t8.0 so I installed rashr to install recovery... Downloaded Phil touch recovery reboot,but cm recovery is appearing... Tried up and down keys... And I can't install other zip files except gapps and ROM itself..
Note: I don't have pc to use...
Sent from my Xperia SP using XDA Free mobile app
audiedevera27 said:
I just flash the update of xenonhd... Wanted to try t8.0 so I installed rashr to install recovery... Downloaded Phil touch recovery reboot,but cm recovery is appearing... Tried up and down keys... And I can't install other zip files except gapps and ROM itself..
Note: I don't have pc to use...
Sent from my Xperia SP using XDA Free mobile app
Click to expand...
Click to collapse
Rashr is giving problems. Place your Philz img file in /sdcard, rename it to recovery.img, open a terminal on your phone and type:
su -c "dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel"
Then press enter and grant su access.
Or, use an old version of Rashr.
It work using rashr 2.3 version... Thanks so much.... :salute:
Sent from my Xperia SP using XDA Free mobile app
it keeps not working
Hey guys!
So, to me it seems a big issue, but I hope my thing would be easy to you, I don't know that much. Here's what's happening:
I used CrystalPA before, then I decided to go for OwnROM 5.1. I performed a clean install thru CWM, but I flashed old gapps, so it bugged. Then I flashed the right gapps (delta gapps, 5.1). Still didn't worked, the home wasn't opening, so I flash the stock ROM so I could use my phone for a while. On wednesday, I rooted the stock, then flashed the ROM again, this time with outdated tangerines (they seemed to have less bugs to me - reports that on v5.0 the wifi was working, and that's pretty much all I need). This time the ROM booted and I could play with it, but the wifi switch still doesn't turn on. I flashed every tangerine I could find, from 6 to 7.2, with twrp and cwm. Nothing. Than this guy told me today to flash it all over again, this time rebooting between ROM and gapps. I did. Clean - install ROM - reboot - install gapps - reboot - flash stock kernel - reboot (soft brick, bootloop) - flash t8 - reboot. Everything works beautifully and smoth, but with no wifi it's useless to me. Any ideas??? Do I need to flash another kernel, or another ROM?
And I already flashed the tangerine again with twrp, still nothing.