Database Develop

[Rom][ICS 4.0.4][p7500][AOSP] Updated_Fixed

Hello
i present you new rom AOSP 4.0.4 it based on pershoot new source
bugs :
No voice call control ( Fixed )
Download
http://www.mediafire.com/?e7ewf7851n6nnws
gapps
http://goo.im/gapps/gapps-ics-20120429-signed.zip
Installation
1- Copy AOSP_4.0.4_Fixed.zip to sd
2- Reboot to Recovery Mode.
3- Make a Full wipe Data & Cache & Dalvik Cache.
4- AOSP_4.0.4_Fixed.zip
5- Reboot
6- to active voice call please download ( Only ) CWM_I9103XXLQ3_Modem.zip from http://forum.xda-developers.com/showthread.php?t=1875024
*use pershoot recovery 6.0.1.1 to install zip
screenshot attached
Enjoy
credit & thanks :
Pershoot for his great work
cyanogenmod
Android open source project
Faryaab for his great job of porting samsung seprated stream to aosp

mazen912 said:
Hello
i present you new rom AOSP+ 4.0.4 it based on pershoot new source
use CWM_I9103XXLQ3_Modem.zip http://forum.xda-developers.com/showthread.php?t=1875024 thx to almaqdad
Screenshot
coming soon
Bugs :
Keyboard ( you have to turn off use physical keyboard ) it will be fix soon
Download
http://www.mediafire.com/?3yo5hfllixexg3c
Installation
1- Copy AOSP4.0.4.zip to sd
2- Reboot to Recovery Mode.
3- Make a Full wipe Cache & Dalvik Cache.
4- Install AOSP4.0.4.zip
5- Reboot
Enjoy
credit :
Pershoot for his great work
cyanogenmod
Android open source project
Click to expand...
Click to collapse
Awesome to see a new rom ......... but will there be a p7510 version?
Thanks for everything!

may a hint howto enable keyboard ?
or is the bug mentioned, only use a physical keyboard ?

Can't get 3g to work but everything else seem to be working real good
Keep up the good work

Is it compactly with voice enable? Dose both Cameras work?

You should probably ask pershoot if you can upload this. Although everything is a public git & open-source its just a little courtesy since we know pershoot has been working on this a while.
Sent from my HTC Desire HD using xda app-developers app

mazen912 said:
Hello
i present you new rom AOSP+ 4.0.4 it based on pershoot new source
use CWM_I9103XXLQ3_Modem.zip http://forum.xda-developers.com/showthread.php?t=1875024 thx to almaqdad
Screenshot
coming soon
Bugs :
Keyboard ( you have to turn off use physical keyboard ) it will be fix soon
Download
http://www.mediafire.com/?3yo5hfllixexg3c
Installation
1- Copy AOSP4.0.4.zip to sd
2- Reboot to Recovery Mode.
3- Make a Full wipe Cache & Dalvik Cache.
4- Install AOSP4.0.4.zip
5- Reboot
Enjoy
credit :
Pershoot for his great work
cyanogenmod
Android open source project
Click to expand...
Click to collapse
Thanks for the new rom.
More info pls? ??

Nice to see more roms for my galaxy tab 10.1 p7500 but any info on that ROM
i mean like whats the difference between this and toldos ROM ?
i can flash it and try it but im a bit afraid to wipe data because of that eMMc brickbug !

georgesadam said:
Nice to see more roms for my galaxy tab 10.1 p7500 but any info on that ROM
i mean like whats the difference between this and toldos ROM ?
i can flash it and try it but im a bit afraid to wipe data because of that eMMc brickbug !
Click to expand...
Click to collapse
The brick big relies on a bit of code in the kernel. I'm not sure about toldos Rom but if you flash either the yoda kernel or a1 kernel on your Rom first you'll be fine because they've removed the bug in the kernel. It also helps to be on twrp or the recovery posted in the op.
Sent from my HTC Desire HD using xda app-developers app

cpope-11 said:
Can't get 3g to work but everything else seem to be working real good
Keep up the good work
Click to expand...
Click to collapse
Same by me.
prasoeu168 said:
Is it compactly with voice enable? Dose both Cameras work?
Click to expand...
Click to collapse
Yes both camera are working.
@OP
Maybe some more Infos would be nice. No Link to Gapps, or which recommend. And 3G not working. If i try to edit it manuell in settings, i got a fc. And Homebutton still not working.

Good to see a new ROM for our great (and usually forgotten) P7500 !! :laugh:
... and AOSP (for those who don't know, it's the pure android, not customized by Samsung and not customized by CyanogenMod).
Thank you and good luck to your work !

thanks guys for feedback
i will try to fix bugs soon
thx

Any screenshot guys...?

wtgserpant said:
Awesome to see a new rom ......... but will there be a p7510 version?
Thanks for everything!
Click to expand...
Click to collapse
Just edit the first 2 line of the update script from p4 to p4wifi & your done!
Edit
Here are my first impressions.
1 to get the keyboard to work tap somewhere the keyboard would turn up then tap the little keyboard icon in the status bar and uncheck
ue physical keyboard.
2 the home button isn't working.
3 sometimes there is a down arrow instead if a back one
4 everything works great although there is a little signal icon who cares!
All round great job I would prefer a more aosp look. Ie no touvhwoz icons in the settings menu!
As for the guy that wanted screenshots, its AOSP!
Edit 2
After a quick gapps flash and reboot bugs 2 and 3 are gone! That just leaves the TW icons then
Sent from my GT-P7510 using XDA Premium HD app

uploading new aosp

Error...status 7

iTalisman said:
Error...status 7
Click to expand...
Click to collapse
Me too. While installation progress. it's unable to signed Please fix that

Works great, also 3G. Thx a lot.:good:
Update your recoveries. 5.5.0.4 ist not 5.5.0.4.

iTalisman said:
Error...status 7
Click to expand...
Click to collapse
hm_dreamware said:
Me too. While installation progress. it's unable to signed Please fix that
Click to expand...
Click to collapse
use pershoot recovery 6.0.1.1 to install the rom
http://droidbasement.com/galaxy/roms/cm10/p4/recovery.tar.md5
or as hanspampel said above

Thanks...got it

CM10 pre-alpha

All credit goes to @HashCode
@dhacker29
Just posting this for all of us at xda
Safe strap latest 3.05.19 and cm10 pre alpha ROM can be found :
http://goo.im/devs/Hashcode/scorpion_mini
Install new safe strap first, then flash cm10 after creating and activating rom-slot-1
Note : ROM may be a bit laggy at first
Known issues : camera broken
WiFi / Bluetooth broken
Headphones / speaker broken
Calls are a bit funky
Video / some 3d games broken
Other then that happy flashing / enjoy
4.1-4.2 *upgrade*
Credit goes to safariking
http://www.mediafire.com/?aldqml4r8jyzm87
Download zip and flash over cm10 for new 4.2 gapps
Inverted gapps :
Credit goes to xlory
http://d-h.st/0b1
Same as above just download zip and flash over cm10
*these are the stock cm10 gapps just inverted not the 4.2 gapps
Then of course , stock jellybean-cm10 gapps :
http://goo.im/gapps/gapps-jb-20121011-signed.zip
At first boot go to settings>performance
Set min cpufreq @ 1ghz and max @ 1.5ghz leave gov on interactive
Enable 16-bit transparency
Disable "surface improvement" dithering
Allow purging of assets
Set zram comp to 26%
Reboot, wait 10 min and reboot again
Also switch launcher or install 4.2 gapps as that launcher seems snappy

tadgerloks said:
All credit goes to @HashCode
@dhacker29
Just posting this for all of us at xda
Safe strap latest 3.05.19 and cm10 pre alpha ROM can be found :
http://goo.im/devs/Hashcode/scorpion_mini
Install new safe strap first, then flash cm10 after creating and activating rom-slot-1
Note : ROM may be a bit laggy at first
Known issues : camera broken
WiFi / Bluetooth broken
Headphones / speaker broken
Calls are a bit funky
Other then that happy flashing / enjoy
4.1-4.2 *upgrade*
Credit goes to safariking
http://www.mediafire.com/?aldqml4r8jyzm87
Download zip and flash over cm10 for new 4.2 gapps
Inverted gapps :
Credit goes to xlory
http://d-h.st/0b1
Same as above just download zip and flash over cm10
*these are the stock cm10 gapps just inverted not the 4.2 gapps
At first boot go to settings>performance
Set min cpufreq @ 1ghz and max @ 1.5ghz leave gov on interactive
Enable 16-bit transparency
Disable "surface improvement" dithering
Allow purging of assets
Set zram comp to 26%
Reboot, wait 10 min and reboot again
Also switch launcher or install 4.2 gapps as that launcher seems snappy
Click to expand...
Click to collapse
I'm very thankful and optimistic for this. Thanks so much.
But unfortunately i need features like Wi-Fi so i must wait until its more stable.
Looking forward to this though!
Sent from my XT907 using xda app-developers app

Is this a fully stable build of safestrap?
Sent from my XT907 using xda premium

jarzy00 said:
Is this a fully stable build of safestrap?
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
safestrap is stable. cm10, on the other hand is not, per the bugs in the OP

antp121 said:
safestrap is stable. cm10, on the other hand is not, per the bugs in the OP
Click to expand...
Click to collapse
I understand the idea of safestrap, but I was wondering if you could gimme a quick lowdown on how to use it. I come from a droid 3 and yes safe strap came out for that but I mainly worked with CWM so I'm a lot more familiar with that. Few questions. Do I install recovery once downloaded? And I forgot what safe system is/when it should be used etc. And how to access safe strap to start flashing. All I can think of is bp tools when I think of custom recoveries lol. Thanks in advance!
Sent from my XT907 using xda premium

jarzy00 said:
I understand the idea of safestrap, but I was wondering if you could gimme a quick lowdown on how to use it. I come from a droid 3 and yes safe strap came out for that but I mainly worked with CWM so I'm a lot more familiar with that. Few questions. Do I install recovery once downloaded? And I forgot what safe system is/when it should be used etc. And how to access safe strap to start flashing. All I can think of is bp tools when I think of custom recoveries lol. Thanks in advance!
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
Ok, so in the new safestrap, make sure you're rooted, go into the app, install, and reboot. Upon booting, you will see a boot up screen with safe system disabled on it. Go into the recovery option by hitting the recovery button on that screen. You'll go into twrp with safestrap settings. Click the rom slots option in the top left. Then choose the first rom slot. Next, choose the partition size. Depending on your sd card size, pick accordingly. It'll take a little while to make the slot but it will. It should switch to that rom slot upon creation, but if not, just click on the rom slot and hit activate. You'll be able to tell because it'll say rom slot one on the top of the screen. Next, you'll have to install the rom by hitting the install button, navigating to the downloads folder, or wherever you have the rom and swiping to install. Next install the gapps and reboot. The safestrap splash screen should look a lot different and say enabled now. If you've done all this, you're golden
Sent from my XT907 using Tapatalk 2

antp121 said:
Ok, so in the new safestrap, make sure you're rooted, go into the app, install, and reboot. Upon booting, you will see a boot up screen with safe system disabled on it. Go into the recovery option by hitting the recovery button on that screen. You'll go into twrp with safestrap settings. Click the rom slots option in the top left. Then choose the first rom slot. Next, choose the partition size. Depending on your sd card size, pick accordingly. It'll take a little while to make the slot but it will. It should switch to that rom slot upon creation, but if not, just click on the rom slot and hit activate. You'll be able to tell because it'll say rom slot one on the top of the screen. Next, you'll have to install the rom by hitting the install button, navigating to the downloads folder, or wherever you have the rom and swiping to install. Next install the gapps and reboot. The safestrap splash screen should look a lot different and say enabled now. If you've done all this, you're golden
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
I thank you again for your response. I just played around with it a bunch and did a full backup which is always good oh and one more quick question. It should say "safestrap disabled" now because I haven't flashed anything yet right?
Sent from my XT907 using xda premium

jarzy00 said:
I thank you again for your response. I just played around with it a bunch and did a full backup which is always good oh and one more quick question. It should say "safestrap disabled" now because I haven't flashed anything yet right?
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
yup. if you wait a bit, im making a guide :3
---------- Post added at 11:06 PM ---------- Previous post was at 10:18 PM ----------
Heres the guide! http://forum.xda-developers.com/showthread.php?p=34248144#post34248144 hope it helps with any problems!

love the devs for this, only thing missing from this amazing phone was cm10

anyone tried this (full ROM version not safestrap) on Aussie Razr M (unlocked bootloader)?
Heck anyone tried safestrap on locked Aussie Razr M?

wintermute000 said:
anyone tried this (full ROM version not safestrap) on Aussie Razr M (unlocked bootloader)?
Heck anyone tried safestrap on locked Aussie Razr M?
Click to expand...
Click to collapse
Tried it on Aussie unlocked boot loader. Works fine, but it's slow as treacle. Needs optimizing to work on RAZR M properly.
Sent from my Nexus 7 using Tapatalk 2

[Nexus 4][MOD] Improve Touch Screen Sensitivity

Hey guys,
The Android 4.3 update for the Nexus 4, in my opinion, has majorly improved the touch screen sensitivity of the Nexus 4, therefore I believe this mod is irrelevant. For those who still want to use it, its still here.
Hey guys,
First of all, I would like to say thanks to trter10 who made the original thread for this. Unfortunately, that thread has been abandoned by the OP and forgotten about. Therefore, I have decided to make this thread. In fact, the mod that I made, in my opinion, is much better than the one in that thread.
As many of us, Nexus 4 users, have come to realize, the device's touch screen sensitivity is way below par when it comes to today's day and age. It has been pointed out that this is due to some changes in the latest touch screen driver from Synaptics, E027. An earlier driver, E015, had much better sensitivity and therefore downgrading to it improves touch screen sensitivity significantly.
There are two ways to downgrade the driver. The first way is the easiest but it doesn't work for everybody, such as people (like me) who use custom kernels like Franco Kernel. I don't know why it doesn't work, but that's the way it is.
First Method:
What You Need:
Root - If you don't have it, go to this thread: http://forum.xda-developers.com/showthread.php?t=2010312
A custom recovery - If you don't have it, go to this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Busybox - If you don't have it, get it here: https://play.google.com/store/apps/details?id=stericson.busybox
init.d support - If you don't have, go to this thread: http://forum.xda-developers.com/showthread.php?t=1933849
What This Does:
Puts an init.d script in the init.d folder. This script will install the E015 driver on boot.
Places the driver in /system for the script to use.
Instructions:
Extract Method 1.zip.
Boot in to your custom recovery.
Install E015-TouchDriver-Mako.zip
Reboot.
Instructions to Revert:
Boot in to your custom recovery.
Install E015-TouchDriver-Mako-Revert.zip
Reboot.
Notes:
After boot, your touchscreen will be unresponsive for around 30 seconds.
After flashing a ROM, you will need to install this zip again.
I am not responsible for any damage this modification may cause.
Second Method:
What You Need:
Root - If you don't have it, go to this thread: http://forum.xda-developers.com/showthread.php?t=2010312
Busybox - If you don't have it, get it here: https://play.google.com/store/apps/details?id=stericson.busybox
Script Manager - SManager - If you don't have it, get it here: https://play.google.com/store/apps/details?id=os.tools.scriptmanager
Instructions:
Extract Method 2.zip.
Using any android file explorer, place SynaImage.E015.bin in /sdcard.
Using any android file explorer, place the E015TouchDriverDowngrade script in any location you want on your internal SD card (I placed it in /sdcard/Scripts).
Go into Smanager, navigate to the E015TouchDriverDowngrade script and press on it.
Select the following options: Fav, Su.
Press Run.
The touch screen will be disabled for the next 15-30 seconds.
From now on, on every reboot you need to perform the following steps in order to downgrade the touchscreen driver:
Go into Smanager, click on options -> Scripts -> E015TouchDriverDowngrade -> Run.
Enjoy!
Notes:
After a reboot, your touchscreen will be unresponsive for around 20 seconds because the kernel is reflashing the new touch screen driver (E027).
After selecting Run your touch screen won't work for 15-30 seconds if it does work, the old touch driver is not being flashed.
I am not responsible for any damage this modification may cause.
Enjoy!
Click to expand...
Click to collapse

Known Issues
Known Issues

FAQ - Frequently Asked Questions
FAQ - Frequently Asked Questions

Like a known issue you could say the ~30 sec delay on boot and on recovery (I know its already in notes)

Re: [MOD] Improve Touch Screen Sensitivity
@OP what is different about your zip than the original one in the thread below. Does yours work with 4.2.2 and the original does not? Is that the main difference? If so please state that in your OP. Thanks
http://forum.xda-developers.com/showthread.php?p=34987520

Monk4Life said:
@OP what is different about your zip than the original one in the thread below. Does yours work with 4.2.2 and the original does not? Is that the main difference? If so please state that in your OP. Thanks
http://forum.xda-developers.com/showthread.php?p=34987520
Click to expand...
Click to collapse
There is a difference, I'm not home right now, I'll update the OP later.

Thanks!! Does this work with other custom roms? such as http://forum.xda-developers.com/showthread.php?t=2009561

tomho529 said:
Thanks!! Does this work with other custom roms? such as http://forum.xda-developers.com/showthread.php?t=2009561
Click to expand...
Click to collapse
Yes, it should.

Re: [MOD] Improve Touch Screen Sensitivity
I noticed this after a few hours with my n4 I actually have a replacement device shipping out to me soon. Ive only have the phone for 2 days. I guess this will be fixed in Android update?
Sent from my Nexus 4 using xda app-developers app

Sv: [MOD] Improve Touch Screen Sensitivity
Confirmed working om latest cm nightly with Franco kernel
Sendt fra min Nexus 4 med Tapatalk2

bxsteve31 said:
I noticed this after a few hours with my n4 I actually have a replacement device shipping out to me soon. Ive only have the phone for 2 days. I guess this will be fixed in Android update?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Well, from 4.2.1 to 4.2.2 they didn't fix it, so probably not.

Works fantastically, thank you!
on aokp build 3 for anyone who's curious.

Will not look back!!
Works as advertised on PA 3.0 (24FEB) I can finally type a message in portrait without it making me feel like I have no clue how to type. I would consistently hit letters and they would not register, just did a test and tapped a whole paragraph with not one error. Thank you very much.

Re: [MOD] Improve Touch Screen Sensitivity
Thanks for this! Going to install this now and try if the delay is shorter. The previous one was annoying that I disabled.
Beamed from my very paranoid and harsh Nexus⁴

Got rid of the 30 second delay being a known issue since it's part of the mod and is mentioned in notes.
I will be away for a week so I won't be able to support the thread for that time, happy flashing!

Re: [MOD] Improve Touch Screen Sensitivity
Works great thanks!
Sent from my Nexus 4 using xda premium

Now how can I flash things in the recovery since it's all touch..

rockneo said:
Now how can I flash things in the recovery since it's all touch..
Click to expand...
Click to collapse
When you boot into recovery just wait a minute for the touch screen to start responding then carry on as normal.
Whats happening is the touch driver is being reflahed back to 027 one.

meangreenie said:
When you boot into recovery just wait a minute for the touch screen to start responding then carry on as normal.
Whats happening is the touch driver is being reflahed back to 027 one.
Click to expand...
Click to collapse
Thank you.

Re: [MOD] Improve Touch Screen Sensitivity
Wow this really works. None of the placebo stuff here. Really responsive now. Thanks +1
Sent from my Nexus 4 using xda premium

[yuga][CWM Advanced Edition] PhilZ Touch

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?

[mint][CWM Advanced Edition] PhilZ Touch

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.