users who have ROOT and problem with touchscreen, try test this fix whether it works or not.
go to system\usr\idc, delete clearpad_pen.idc
in clearpad.idc, delete all the code on # Touch Filter
save and reboot.
This method fixed the problem in your phone?
somehow it reduce it.
Then is not a completely fix. Did you tried the .136 FW?
eclyptos said:
Then is not a completely fix. Did you tried the .136 FW?
Click to expand...
Click to collapse
i m already on .136 firmware
chunlianghere said:
i m already on .136 firmware
Click to expand...
Click to collapse
..and you still have touch screen problems? Bad news. I will go for a replacement via warranty.
eclyptos said:
..and you still have touch screen problems? Bad news. I will go for a replacement via warranty.
Click to expand...
Click to collapse
no point i guess. since alot of people around the world send for repair, yet problem still there
Related
[deleted]
I followed exact to your instructions, still the update did not work.
Update failed to install.
I made sure I was on .352
Rooted with Vroot and then installed Dualrecovery (https://mega.co.nz/#!zNBjCLgK!RloqhT1DzO4mYQgmbDXsZycDjHlFjTL-eSonTz4VBX4)
Flashed (in Recovery) pre-rooted 257 fw (http://forum.xda-developers.com/showthread.php?t=2440408) + BusyBox/SU (http://d-h.st/M10)
Flashed (in Flashtool) kernel/baseband from 257 stock tft (http://forum.xda-developers.com/showthread.php?t=2469191)
Restarted phone and everything have been working flawlessly since. Reinstalled recovery.
:good::good:
killkyo said:
I followed exact to your instructions, still the update did not work.
Update failed to install.
Click to expand...
Click to collapse
Sorry for wasting you time man. I know it is very frustrating not to get your device rooted. But it worked for me. I'll just try to do this again and let you know. Hope I'll not loose my root (fingers crossed).
SweFox said:
I made sure I was on .352
Rooted with Vroot and then installed Dualrecovery (https://mega.co.nz/#!zNBjCLgK!RloqhT1DzO4mYQgmbDXsZycDjHlFjTL-eSonTz4VBX4)
Flashed (in Recovery) pre-rooted 257 fw (http://forum.xda-developers.com/showthread.php?t=2440408) + BusyBox/SU (http://d-h.st/M10)
Flashed (in Flashtool) kernel/baseband from 257 stock tft (http://forum.xda-developers.com/showthread.php?t=2469191)
Restarted phone and everything have been working flawlessly since. Reinstalled recovery.
:good::good:
Click to expand...
Click to collapse
Yeah it works great, I have tried it too but it comes with a cost of loosing some stock apps, installed apps and data. Wouldn't it be great if we can just do the OTA update without having to loose anything and also keep root?
Thanks for trying again, I'm starting to think that it's my phone or region's problem. I tried a lot of different methods but none worked.
Sad case for me...
mpmaheshbabu said:
Yeah it works great, I have tried it too but it comes with a cost of loosing some stock apps, installed apps and data. Wouldn't it be great if we can just do the OTA update without having to loose anything and also keep root?
Click to expand...
Click to collapse
I unticked the wipe boxes and didn't lose anything .
killkyo said:
Thanks for trying again, I'm starting to think that it's my phone or region's problem. I tried a lot of different methods but none worked.
Sad case for me...
Click to expand...
Click to collapse
Well, what happens?
SweFox said:
I unticked the wipe boxes and didn't lose anything .
Well, what happens?
Click to expand...
Click to collapse
Hmm, it turns out to be like this.
Once you are on 14.1.G.1.534,
1. Root it with VROOT, Install Super Su Pro, update binaries and enable survival mode*.
2. Reboot and unroot using VROOT and reroot then update Super Su binaries.
3. Repeat Step 2 twice.
4. Now try to do the OTA update.
Let please let me know if this didn't work. Thanks and good luck.
Save this attachment in your sd card in a folder with name romsu.
killkyo said:
Thanks for trying again, I'm starting to think that it's my phone or region's problem. I tried a lot of different methods but none worked.
Sad case for me...
Click to expand...
Click to collapse
Hey if you really think that wrong place is the reason for sure, then try to connect to net via hotspot sheild vpn or some vpn you prefer and then download the OTA update, I know I'm just being stupid but just give it a try. To me it makes sense to some extent.
Are you telling me or killyo ?
SweFox said:
Are you telling me or killyo ?
Click to expand...
Click to collapse
he he sorry it was for ??? im nt sure either
@mpmaheshbabu
Mate...
Really... Why don't you read and check XDA first.
First you opened a thread with bunch of questions that are already answered all over the Z1 threads.
And now you open thread for something we wrote days ago?!
HERE IT IS
It's cool to help guys but you shouldn't double threads.
Sent from my Z1
funky0308 said:
@mpmaheshbabu
Mate...
Really... Why don't you read and check XDA first.
First you opened a thread with bunch of questions that are already answered all over the Z1 threads.
And now you open thread for something we wrote days ago?!
HERE IT IS
It's cool to help guys but you shouldn't double threads.
Sent from my Z1
Click to expand...
Click to collapse
Sorry
mpmaheshbabu said:
Sorry
Click to expand...
Click to collapse
Hehe...
You are the nice guy
I'm not saying you have to say sorry to me but I just wondering why double post...
But O.K - it's a bit different
Sent from my Z1
@mpmaheshbabu
You shouldn't delete OP mate.
I feel terrible now, that wasn't my intention...
I just said we already have that...
I have no right to tell you to delete it and I really didn't think you'll delete it...
Sent from my Z1
funky0308 said:
@mpmaheshbabu
You shouldn't delete OP mate.
I feel terrible now, that wasn't my intention...
I just said we already have that...
I have no right to tell you to delete it and I really didn't think you'll delete it...
Sent from my Z1
Click to expand...
Click to collapse
YO! I'm back. It's ok. Someone mentioned it didn't work so I'll just double check and post things again.
Hi everybody,
just updated to Android 4.3 on my Z1 and realised that the Sony click sounds seems to have changed?
Has anyone experienced the same problem?
I really liked the "Sony" click sound any idea how to get it back?
Thanks in advance for your replies
Yes, the click on 4.3 is different and many do not like it. The only one way to get that click back is to root your phone and replace with the old one from 4.2. The problem is you did not saved the wave file from 4.2 so somebody should post it for you and then you should replace it on your phone or you downgrade, root your phone, backup all what you need and update again. Anyway if you want root your .290 the only way is to downgrade with NUT method so you will do 2 things in 1.
eclyptos said:
Yes, the click on 4.3 is different and many do not like it. The only one way to get that click back is to root your phone and replace with the old one from 4.2. The problem is you did not saved the wave file from 4.2 so somebody should post it for you and then you should replace it on your phone or you downgrade, root your phone, backup all what you need and update again. Anyway if you want root your .290 the only way is to downgrade with NUT method so you will do 2 things in 1.
Click to expand...
Click to collapse
Damn, had that thought - but i didn't want to believe
Well i'll wait for the next update, maybe the'll bring it back?!
Thanks!
minifamilie said:
Well i'll wait for the next update, maybe the'll bring it back?!
Click to expand...
Click to collapse
Maybe they make it better.
Hi all,
i got a problem with my bluetooth phonebook sync. My phone connects via blutooth to the car, but the phone book does not sync. The request for the transfer of the phone book does not appear at all.
I have this Problem with following ROMs:
Sony Stock 4.3 (14.2.A.0.290)
IHackers 2.1 (JellyBean 4.3)
SlimKat 4.4
However, no problems with these ROMs,
Sony Stock 4.2.2 (14.1.G.2.257)
FreeXperia CM11 (fxp / kali)
What can cause this and how can I solve this problem for the other roms?
Thank you
Sony xperia Z1 C6903
Opel UHP car kit
You can flash the "Baseband" only from 14.1.G.2.257 on 14.2.A.0.290 or Update to .136. If .136 will not solve this problem then flash Baseband here too from .257.
I have the same problems with 290 and 136.. Does this mean that I can flash the 136 generic BALL ftf and then just flash the baseband from 257? It won't screw the phone up will it?
Regards,
Alan
nalab1 said:
It won't screw the phone up will it?
Click to expand...
Click to collapse
I can't guarantee that but this was confirmed by users who did that to improve the signals on they phone. They flashed baseband from 4.2.2 FW .257 on 4.3 FW .290 and it worked. Flashing anything its a risk so be careful, BTW, if this will not work you can flash the baseband from 4.3 FW .136 back, in the same way. If I am not wrong, if so someone correct me please, the baseband contain all package of frequency for the phone to work properly.
eclyptos said:
I can't guarantee that but this was confirmed by users who did that to improve the signals on they phone. They flashed baseband from 4.2.2 FW .257 on 4.3 FW .290 and it worked. Flashing anything its a risk so be careful, BTW, if this will not work you can flash the baseband from 4.3 FW .136 back, in the same way. If I am not wrong, if so someone correct me please, the baseband contain all package of frequency for the phone to work properly.
Click to expand...
Click to collapse
Hi eclyptos,
Thank you for your reply.. So, does the baseband contain all of the wireless stuff like wifi, bluetooth etc?
To get the sequence right I -
1) Completely flash .136 - reboot to check if ok
2) Flash the baseband ONLY from .257 - reboot to check if ok
If, the phone were to get stuck in say, a bootloop is there any way to completely power it off and then reflash?
Regards,
Alan
nalab1 said:
Hi eclyptos,
Thank you for your reply.. So, does the baseband contain all of the wireless stuff like wifi, bluetooth etc?
Click to expand...
Click to collapse
It should.
nalab1 said:
To get the sequence right I -
1) Completely flash .136 - reboot to check if ok
2) Flash the baseband ONLY from .257 - reboot to check if ok
Click to expand...
Click to collapse
Yes.
nalab1 said:
If, the phone were to get stuck in say, a bootloop is there any way to completely power it off and then reflash?
Regards,
Alan
Click to expand...
Click to collapse
Of curse but it will not stuck.
@chunlianghere already did this HERE and will report leater.
eclyptos said:
It should.
Yes.
Of curse but it will not stuck.
@chunlianghere already did this HERE and will report leater.
Click to expand...
Click to collapse
Hi eclyptos,
Thank you. For my information (sorry for the noobness!) if it were stuck in a bootloop how do I actually power the phone off?
Regards,
Alan
nalab1 said:
Thank you. For my information (sorry for the noobness!) if it were stuck in a bootloop how do I actually power the phone off?
Click to expand...
Click to collapse
Power + Volume Up. BTW, Flash with fully charged battery.
eclyptos said:
Power + Volume Up. BTW, Flash with fully charged battery.
Click to expand...
Click to collapse
Hi eclyptos,
Thank you for your replies and help. I am going to try this at the weekend as during the week, I work away from home and dont have access to my pc. I will let you know how it goes.
Regards,
Alan
eclyptos said:
You can flash the "Baseband" only from 14.1.G.2.257 on 14.2.A.0.290 or Update to .136. If .136 will not solve this problem then flash Baseband here too from .257.
Click to expand...
Click to collapse
I have tried this, but i did not work.
Any other advise?
Yocto69 said:
I have tried this, but i did not work.
Any other advise?
Click to expand...
Click to collapse
Are you saying that after flashing baseband from .257 on .136 you still have problems? Try downgrade the entire system and check if the problem persist. Sometime is not the phone but the other devices so really we can try looking forever.
eclyptos said:
Are you saying that after flashing baseband from .257 on .136 you still have problems? Try downgrade the entire system and check if the problem persist. Sometime is not the phone but the other devices so really we can try looking forever.
Click to expand...
Click to collapse
Look in the op. I have tried several Firmwares and Roms.
If i downgrade to. 257 It works perfect!
The other Device is not the problem.
Thx
Yocto69 said:
Look in the op. I have tried several Firmwares and Roms.
If i downgrade to. 257 It works perfect!
The other Device is not the problem.
Thx
Click to expand...
Click to collapse
Other than that can be a kernel.
eclyptos said:
Other than that can be a kernel.
Click to expand...
Click to collapse
Is it maybe possible to take a blutooth.apk from .257 and use it on .290?
Yocto69 said:
I have tried this, but i did not work.
Any other advise?
Click to expand...
Click to collapse
it works fine when listening music.
but during voice call, its not ok.
Yocto69 said:
Is it maybe possible to take a blutooth.apk from .257 and use it on .290?
Click to expand...
Click to collapse
Is not that easy. Bluetooth is not an application which you can download or install. It's implemented in the system and baseband. The main reason for bad quality like WiFi, Mobile Signal or Bluetooth is the Radio which is the Baseband in Z1. On HTC for example to improve the reception for all of them I am able to flash just the Radio.
eclyptos said:
Is not that easy. Bluetooth is not an application which you can download or install. It's implemented in the system and baseband. The main reason for bad quality like WiFi, Mobile Signal or Bluetooth is the Radio which is the Baseband in Z1. On HTC for example to improve the reception for all of them I am able to flash just the Radio.
Click to expand...
Click to collapse
Ok, i have tried severall kernel.
ihackers advanced kernel, stock kernel and doomlords kernel. All on 4.3 roms. => No change.
What else could I try?
Yocto69 said:
Ok, i have tried severall kernel.
ihackers advanced kernel, stock kernel and doomlords kernel. All on 4.3 roms. => No change.
What else could I try?
Click to expand...
Click to collapse
I losing ideas, I don't want to say but at last it may be a hardware issue but not sure. I don't know if you want to do this but you should go back to Stock and Flash a Stock FTF to check if the problem persist even there, is it does it's the phone.
I do not know why, but the flash on my camera no longer works for both photos as flashlight. does not turn on at all, someone would know why, since I put stock 4.1.2, 4.3 and 4.4.4 omini then, and nothing
Might be a hardware issue. You still have warranty on your phone?
WhiteNeo said:
Might be a hardware issue. You still have warranty on your phone?
Click to expand...
Click to collapse
I have no more
Hello guys.. just want to know the possible reason why my note3 sensors no longer working.. i do not even know when it starts.. i remember that i upgraded from jb to kitkat and after a weeks i noticed the problem.. is it because of the upgrade..?
Up
Do you have XPrivacy installed and are blocking the sensors? If not I guess if they are failing the test you could flash NC2 over and that might get them working.
Namelesswonder said:
Do you have XPrivacy installed and are blocking the sensors? If not I guess if they are failing the test you could flash NC2 over and that might get them working.
Click to expand...
Click to collapse
I tried flashing stock nc2 but same issue.. im not sure if its a hardware problem or a software.
Why are they failing all at the same time..?
Up. .
clarksterkent said:
I tried flashing stock nc2 but same issue.. im not sure if its a hardware problem or a software.
Why are they failing all at the same time..?
Click to expand...
Click to collapse
Do they not work at all or do they work sometimes and then fail at the same time? Also have you tried any 3rd party sensor apps besides the built-in tests?
brisinger08 said:
Do they not work at all or do they work sometimes and then fail at the same time? Also have you tried any 3rd party sensor apps besides the built-in tests?
Click to expand...
Click to collapse
I already tried third party apps but the issue still exists.. what is the possible problem..?
Sounds like hardware is the next place to check. Feel comfortable taking your phone apart?
I had to to get my proximity sensor working as a bunch of crud (mostly pocket lint) made its way into the sensor pocket. There are many tear down videos for this device.
Good luck!
Did it pass the Sensor Hub Test? *#0*# test near the end of the page.
aj_vogtman said:
Did it pass the Sensor Hub Test? *#0*# test near the end of the page.
Click to expand...
Click to collapse
No.. it FAILS.. what am going to do now..? Is this really a hardware problem..? Im not going to a technician yet, still trying to solve issue..
clarksterkent said:
No.. it FAILS.. what am going to do now..? Is this really a hardware problem..? Im not going to a technician yet, still trying to solve issue..
Click to expand...
Click to collapse
This happen to me yesterday. Try a reboot and see if that helps. Mine was cause by a crash app.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
xfaega said:
This happen to me yesterday. Try a reboot and see if that helps. Mine was cause by a crash app.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
Reboot didnt solve the issue.. sad..
clarksterkent said:
Reboot didnt solve the issue.. sad..
Click to expand...
Click to collapse
I know you said you reflashed stock, but you might want to try reflashing with the PIT file as well. That will repartition your phone and is probably the most you can do software-wise at this point...if you still have problems you may be better off sending it in for repair unless you're comfortable taking your phone apart yourself.
Download the 4 Odin files in this thread http://forum.xda-developers.com/showthread.php?t=2703006 (ignore the home file) and the PIT file. In this case you do want repartition checked in Odin...it will check it automatically when you load the PIT file just make sure to leave it checked.
This will wipe everything so backup what you want to save first.
Hope this works for you bro and it's not a hardware issue