I have strange touchscreen problem on my sm-n910f. After I flashed custom recovery and one of the custom roms my touchscreen stopped working properly, even if I revert to stock. It looks like touch surface became smaller, right and bottom part of the screen doesn't work any more. Phone seems to use smaller surface for touch, so to press very bottom icon I need to press 1-2cm above it. It behaves the same in any rom and any recovery. See photos, I activated show touches in dev options. I try to look if anyone had the same problem, but I couldn't find anything. Any ideas?
I forgot to add that spen works perfectly fine.
Well I know what I did wrong so just in case someone else has the same problem: I flashed wrong recovery, one for n915f (no idea how I managed to get that file instead of proper one). Funny enough reflashing good one or flashing stock rom doesn't solve my problem. Over the weekend I will go to Samsung shop, hope they can help me.
Ouch maybe they can.. id say touchscreen driver may be corrupt or something. Id try a 3 part odin flash if i were you
Ausboy 2011 said:
Ouch maybe they can.. id say touchscreen driver may be corrupt or something. Id try a 3 part odin flash if i were you
Click to expand...
Click to collapse
I tried to flash original firmware and two custom roms, no change unfortunately. I also believe it is not hardware fault, but I have no idea how to fix it.
I love Samsung warranty policy in the UK, 28 days from purchase date they replace faulty device without asking for a reason, so I got mine replaced. Pure luck.
I still believe it would be know if what I have done is reversible. I understand why flashing wrong recovery is messing with graphic driver, but I would like to know why flashing proper one doesn't solve it.
I would appreciate if someone could share some light on that matter.
torquadon said:
I love Samsung warranty policy in the UK, 28 days from purchase date they replace faulty device without asking for a reason, so I got mine replaced. Pure luck.
I still believe it would be know if what I have done is reversible. I understand why flashing wrong recovery is messing with graphic driver, but I would like to know why flashing proper one doesn't solve it.
I would appreciate if someone could share some light on that matter.
Click to expand...
Click to collapse
Probably has to do something with partition size. When you flashed the wrong recovery, a repartition was done and it messed up your device. Flashing the right one in a messed up partition did not solve the problem. Perhaps if you had tried to flash the appropriate PIT File for your device, the problem would have been solved. But, in the future, the safest option is to be extra careful about which files you flash. Glad you got it sorted out!
Sent from my SM-P600 using Tapatalk
iridaki said:
Probably has to do something with partition size. When you flashed the wrong recovery, a repartition was done and it messed up your device. Flashing the right one in a messed up partition did not solve the problem. Perhaps if you had tried to flash the appropriate PIT File for your device, the problem would have been solved. But, in the future, the safest option is to be extra careful about which files you flash. Glad you got it sorted out!
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
I tried PIT file too, no go As I said my problem is sorted, but fact that I do not know if it could have been resolved without replacement bothers me a little bit
torquadon said:
I tried PIT file too, no go As I said my problem is sorted, but fact that I do not know if it could have been resolved without replacement bothers me a little bit
Click to expand...
Click to collapse
If the PIT file didn't work, then it seems that the replacement was the only way to go.
iR¡[email protected]!* from Galaxy Note 4 via Tapatalk
N910F touch stopped after root
Manufactory: SAMSUNG
Model: SM-N910F
Hardware: QCOM
Mode: normal
Checking environment ...
System Info
Display ID: KTU84P
System Ver: 4.4.4 REL
API Level: 19
Incremental: N910FXXU1ANK4
Model: SM-N910F
Brand: samsung
Device: trlte
Platform: apq8084
Language: en
Rigion: GB
Device Info
SerialNumber: bc98dac2
Hardware: qcom
Model: trlte
PDA Version: N910FXXU1ANK4
Phone Version: N910FXXU1ANK4
Bootloader ver: N910FXXU1ANK4
Ril Hw Version: MP 0.900
Sales Code: PHE
Model ID:
Get Bluetooth info failed
Get WI-FI info failed
Network [1]: GSM IMEI: 35420106xxxxxx
Root Access: ROOTED
sm-n910f it was working good unluckily i did root thats all my bad luck started there,
touch stopped working and its working but very strange if i press 9,8,7 it will become ok but any how
i found the solution but u guys wont believe me but the solution is i changed full lcd thats it i loosed money of full lcd instead of unlocking i loose 150$ and around 6 days to understand so dont. So u guys waiting are who reading this post please go ahead and change lcd, thats all just now i changed have a nice day, dont be dissapoint its part of telecom industry we loose sum but learnt alot :crying: :fingers-crossed: :laugh:
---------- Post added at 03:29 PM ---------- Previous post was at 03:20 PM ----------
Dont waste time for searching different roms or pits doesnt exist problem in software:
i tried to full flash .oct .zip .spt around 35 roms official and unofficial but failed
itried even to disturb or repair efs with readed efs files but same noluck
i tried to reinstall touch and lcd but failed
itried to change battery and everything alots more but solution is touch damaged after root so its doesnt matter its really strange problem not easy to understand when they will face this type of problem
i have the same problem
and me too wrong recovery and now only spen to work
i have more than 28 days purchase so i dont know what samsung are gonna say if i take it there
if its been rooted and knox is tripped your warranty is void.
Have a look here :
http://forum.xda-developers.com/note-4-tmobile/help/touch-screen-issues-root-t2986883
I got my touch screen calibration fixed 
Anybody having similar problems do the following:
dial *#2663# and update the touch FW by pressing "TSP FW update (General)
Not my idea, copied from cm12 thread.
As I mentioned I got my replaced. I didn't test solution above and it is not my idea. Try it at your own risk.
solved... I have fixed the problem
Thanks a lot i have try it and works for me..... thanksss
alagoinhas said:
Thanks a lot i have try it and works for me..... thanksss
Click to expand...
Click to collapse
thanks so much , you saved me from a new purchase:good::good::good:
Thanx Bro...it worked..!!!!!
Great Job my friend......it helped.....!!!! your a life saver...!!!
torquadon said:
I got my touch screen calibration fixed 
Anybody having similar problems do the following:
dial *#2663# and update the touch FW by pressing "TSP FW update (General)
Not my idea, copied from cm12 thread.
Click to expand...
Click to collapse
wow!!!! it worked thank u!!!!!!!!!
note 4 n910f wrong recovery touch problem solution
i had the same problem and examined lots of kernel and rom for my galaxy note 4 n910f .i have examined oddin and repartition and .... but only this code solved my problem :
in your dial pad just type
*#2663#
then press " TSP FW UPDATE (general)"
your touch will be recalibrate
---------- Post added at 08:44 PM ---------- Previous post was at 08:38 PM ----------
torquadon said:
I have strange touchscreen problem on my sm-n910f. After I flashed custom recovery and one of the custom roms my touchscreen stopped working properly, even if I revert to stock. It looks like touch surface became smaller, right and bottom part of the screen doesn't work any more. Phone seems to use smaller surface for touch, so to press very bottom icon I need to press 1-2cm above it. It behaves the same in any rom and any recovery. See photos, I activated show touches in dev options. I try to look if anyone had the same problem, but I couldn't find anything. Any ideas?
I forgot to add that spen works perfectly fine.
Click to expand...
Click to collapse
i had the same problem and examined lots of kernel and rom for my galaxy note 4 n910f . but only this code solved my problem :
*#2663#
then press " TSP FW UPDATE (general)"
my touch screen lacks sensitivity on the left side from upper corner to lower corner.
i already did 2263#.... still less responsive touch screen
Related
Hi! I read every forum/post I could, but I don't know what else to do... I'm not and advance user, but I'm used to flashing ROMs, Stock ROMs, trying recoverys etc. always had an Android phone and I always unlock the bootloader, flash new rom and blah blah... so, here's my problem T^T
A week ago I buy a Samsung S4 GT i9500... not 'casuse I'm a fan of Samsung, but 'cause the price was great (at least in my Country)... The glas was cracked, but the touch was ok, the only thing broken was the front camera, but hey... I'll never used it
So the phone was able to connect to all the 3 carriers in my country (Argentina) Personal - Movistar - Claro. So I started with a Custom Recovery... everything OK
I always used the CyanogenMOD roms, so I downloaded the last one for my phone... but was kinda buggy... so I started to look for another options, I downloaded MIUI (official) but was too chinese for my taste, I mean, no Play Store, half of the phone options was in chinese, so... I moved on... the last one was Thunder Universe V6... was ok, nice skins, fast... stable... but the battery was the problem, almost 1% per minute, with power save activated so... I decided to go back to Stock ROM or Firmware... but I couldn't find one for my country or the links were dead...
So I finally found this one (I don't know if I can post a link to another forum so I will post the specs only):
Model: GT-I9500
Model name: GALAXY S4
Country: Argentina
Version: Android 4.4.2
Changelist: 2735569
Build date: Tue, 09 Sep 2014 11:17:09 +0000
Product Code: ANC
PDA: I9500UBUGNI1
CSC: I9500ANCGNI1
MODEM: I9500UBUGNI1
Flashed with Odin, no errors, everything went ok... but after all the update, all my apps I realize that I have signal bars, but no carrier connection... only "Emergency Calls Only"
I started to read, and try a couple of things, but no luck... if I change the modem/radio/baseband I got the "unknown baseband" "uknown IMEI" thing... I flashed the phone to the previous roms, Cyano and Thunder but the problem remains...
I don't know what else to do :s and send my phone to someone for fixing it is very expensive, more than half the price of a new phone :s so if there is something I could try to fix it myself, will be amazing...
If u need more data, or whatever just ask, and i will do it, and post the result...
thanks in advance and sorry for my crappy eng >.<
VV0LF said:
Hi! I read every forum/post I could, but I don't know what else to do... I'm not and advance user, but I'm used to flashing ROMs, Stock ROMs, trying recoverys etc. always had an Android phone and I always unlock the bootloader, flash new rom and blah blah... so, here's my problem T^T
A week ago I buy a Samsung S4 GT i9500... not 'casuse I'm a fan of Samsung, but 'cause the price was great (at least in my Country)... The glas was cracked, but the touch was ok, the only thing broken was the front camera, but hey... I'll never used it
So the phone was able to connect to all the 3 carriers in my country (Argentina) Personal - Movistar - Claro. So I started with a Custom Recovery... everything OK
I always used the CyanogenMOD roms, so I downloaded the last one for my phone... but was kinda buggy... so I started to look for another options, I downloaded MIUI (official) but was too chinese for my taste, I mean, no Play Store, half of the phone options was in chinese, so... I moved on... the last one was Thunder Universe V6... was ok, nice skins, fast... stable... but the battery was the problem, almost 1% per minute, with power save activated so... I decided to go back to Stock ROM or Firmware... but I couldn't find one for my country or the links were dead...
So I finally found this one (I don't know if I can post a link to another forum so I will post the specs only):
Model: GT-I9500
Model name: GALAXY S4
Country: Argentina
Version: Android 4.4.2
Changelist: 2735569
Build date: Tue, 09 Sep 2014 11:17:09 +0000
Product Code: ANC
PDA: I9500UBUGNI1
CSC: I9500ANCGNI1
MODEM: I9500UBUGNI1
Flashed with Odin, no errors, everything went ok... but after all the update, all my apps I realize that I have signal bars, but no carrier connection... only "Emergency Calls Only"
I started to read, and try a couple of things, but no luck... if I change the modem/radio/baseband I got the "unknown baseband" "uknown IMEI" thing... I flashed the phone to the previous roms, Cyano and Thunder but the problem remains...
I don't know what else to do :s and send my phone to someone for fixing it is very expensive, more than half the price of a new phone :s so if there is something I could try to fix it myself, will be amazing...
If u need more data, or whatever just ask, and i will do it, and post the result...
thanks in advance and sorry for my crappy eng >.<
Click to expand...
Click to collapse
Hi mate ,
Try flashing a stock rom and see if it helps.....but to me it looks like the EFS folder is broken , do you have an EFS folder back up? if not you may have to take the phone to a local service center ( samsung or not) and have the imei fix, you need a box like Z3X or similar to do it.
MAX 404 said:
Hi mate ,
Try flashing a stock rom and see if it helps.....but to me it looks like the EFS folder is broken , do you have an EFS folder back up? if not you may have to take the phone to a local service center ( samsung or not) and have the imei fix, you need a box like Z3X or similar to do it.
Click to expand...
Click to collapse
Hi! thanks for replaying! I can't find a stock rom for my country or the links are dead :s the one I downloaded (I put the specs on my previous post) seems to be an unbranded stock rom... but I don't really know, I don't have an EFS folder back up >.< I know... my bad here :s I read about the z3x box or the octopus one, but I was hoping for another problem more easy to fix :s there is a way to be sure that is the EFS folder? like 100%? there is nothing more I can do or try? :c
Thanx again!
VV0LF said:
Hi! thanks for replaying! I can't find a stock rom for my country or the links are dead :s the one I downloaded (I put the specs on my previous post) seems to be an unbranded stock rom... but I don't really know, I don't have an EFS folder back up >.< I know... my bad here :s I read about the z3x box or the octopus one, but I was hoping for another problem more easy to fix :s there is a way to be sure that is the EFS folder? like 100%? there is nothing more I can do or try? :c
Thanx again!
Click to expand...
Click to collapse
Hi ,
the stock rom you flashed should been fine ( check here for stock rom for your country http://www.sammobile.com/firmwares/database/GT-I9500/PSN/ ) , if that did not help can it only be two things hardware ( like the sim caddy) or the EFS folder....there is no way to know without one of those boxes....
The repair should run around 25 usd........
MAX 404 said:
Hi ,
the stock rom you flashed should been fine ( check here for stock rom for your country http://www.sammobile.com/firmwares/database/GT-I9500/PSN/ ) , if that did not help can it only be two things hardware ( like the sim caddy) or the EFS folder....there is no way to know without one of those boxes....
The repair should run around 25 usd........
Click to expand...
Click to collapse
Thx Max, the firmware I downloaded was from that site, but like I said was an unbrended one, so I will download one from the link u post, and will come back with the results =) thx again for your help!
well... sadly the problem remains... everything works great, but I can't connect to any network carrier... just emergency calls u.u
if there is nothing more to try...
Thx again for your help MAX
VV0LF said:
well... sadly the problem remains... everything works great, but I can't connect to any network carrier... just emergency calls u.u
if there is nothing more to try...
Thx again for your help MAX
Click to expand...
Click to collapse
Sorry to hear that mate ,
if you are skill , open the phone and check the antenna cable , make sure is tight in place...just in case
A friend has an S4 (i9505) from Vodafone Spain (ATL), unlocked and using another operator microSIM (Jazztel). Last week, via OTA, she received the latest update available: http://www.sammobile.com/firmwares/download/59777/I9505XXUHOJ4_I9505VFRHOF3_ATL/
After installing that OTA update, the signal level is very low, even none inside buildings, etc. This was not happening before.
In addition, the 2 soft keys (on both sides of the Home button) are not responding anymore, not even lighting up.
The Home button works, so... I think that it's not a hardware problem. Too much coincidence that the update and that hypothetical hardware problem happened at the same time...
First I did was a total hard reset, to factory settings, etc. No success, both problems (signal and soft keys) were still there.
Second, I flashed ROM manually via Odin. I flashed latest PHE one, so no Vodafone bloatware anymore: http://www.sammobile.com/firmwares/download/59311/I9505XXUHOJ2_I9505YXXHOJ1_PHE/
No success, still the same. I then did again a hard reset to factory setting, with Wipes first... and nothing.
Next thing I will do (when i have the phone in my hands again) is flashing with Odin the previous PHE one, and crossing fingers: http://www.sammobile.com/firmwares/download/48153/I9505XXUHOE3_I9505PHEHOE1_PHE/
Anyone with the same problem? Any solution/suggestion?
Flashed next-to-last Stock ROM for PHE http://www.sammobile.com/firmwares/download/48153/I9505XXUHOE3_I9505PHEHOE1_PHE/ and no success
Then I flashed Base HOH2 (4files+PIT) with Odin and... nothing either.
No idea what to try next. Suggestions?
Same here, after OTA no menu/back buttons (neither backlight or functionality)
Current status:
- seems to affect quite a lot of people, there are more threads like this on various sites
*e.g. here, here, here
- happenning after both OTA or ODIN based update to latest 5.0.1 ROM (for me it was i9505XXUHOJ2)
My findings so far:
- NO rom change seems to fix this
- it seems that touch keys' FW is updated (physically on the chip) along with the update (to version 0x12)
- Touch key FW update in menu *#2663# not applicable as it says that it won't update - versions are the same (you can check the version of driver used by ROM and the actual FW in chip on this page)
NOTE. my girlfriend has the buttons working after successful update and has both in version 0x12
Conclusion:
- It seems that the FW flashing process of the touch keys controllers somehow failed => phone says that it's also ver. 0x12 (same as android driver) but it is probably corrupted
- Re-flashing of the chip could solve the problems, however there are problems with this:
NOTES.
Menu *#2663# won't let us do the flash because of the version check - Can we use ADB to force the update on a rooted phone? Does anybody know how?
There is a slight chance, that it'll be fixed if Samsung will release some newer update which updates also the keys' FW
Samsung could release a fix, that will flash this manually as a lot of people have problem with this
!EDIT:
I've found very similar problem + solution on the Vietnamese forum bellow (don't use the files as it's for different phone!):
- to sum it up - force downgrading the FW, the update again... (any ROM cook that could help?)
see here
regards,
J.
I completely agree with you. I also tried the *#2663# path, the phone also has 0x12 touch keys FW, and it doesn't let me reflash it, either. Don't know what FW was there before the OTA update.
I have been told about the first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/download/44821/I9505XXUHOB7_I9505OXAHOB7_DBT/ and also about the last 4.4.2 one: http://www.sammobile.com/firmwares/download/40046/I9505XXUGNK4_I9505OXAGNK4_DBT/
Maybe one of those... makes something again on the Touch Keys FW?
I couldn't try anymore bcs I gave the phone back to my friend (with accesibility touch keys on-screen)
HI, have you found a solution? My Italian S4 suffered the same bug after the same upgrade. I tried to contact samsung and they said I need to replace the screen because upgrading the firmware put the electronic under stress and they got broken. I don't believe them because too many people have the same problem + my screen is two days old! Please help me!
Same problem for my S4! how we can flash/reflash/downgrade soft touch fw?
Has anyone tried the first first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/d...05OXAHOB7_DBT/ or the last 4.4.2 one: http://www.sammobile.com/firmwares/d...05OXAGNK4_DBT/ ?
A friend of mine (another one) told me that he fixed it with German HOA7 one, and then updated again to latest with no problem: https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I can't try it myself bcs I gave back the S4 to the owner. If anyone tries, please leave here the results!
oiluj said:
Has anyone tried the first first German 5.0.1 stock ROM: http://www.sammobile.com/firmwares/d...05OXAHOB7_DBT/ or the last 4.4.2 one: http://www.sammobile.com/firmwares/d...05OXAGNK4_DBT/ ?
A friend of mine (another one) told me that he fixed it with German HOA7 one, and then updated again to latest with no problem: https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I can't try it myself bcs I gave back the S4 to the owner. If anyone tries, please leave here the results!
Click to expand...
Click to collapse
I've tried a lot of ROMs - 4.4.2, also older 5.0.1 with no result...
I haven't tried UHOA7 I've tried UHOB7 instead, so I'll probably give it the shot, but I can't imagine how it could fix this issue (maybe if it for some reason has the touch-cypress FW update forced...)
- I've seen that on some German forums reverting back helped, but it wasn't my case (+it didn't fix the problem for many others...)
As I've wrote before, they've created modified kernel (with forced touch key FW reflash - bypassed version check) for a little bit different phone on the Vietnamese forum (see the link in my previous post) and it seems that it would be quite easy for somebody who has some knowledge with kernel compilation... (it would just need small modification in the "if" condition of 1 kernel source file) I've tried to do some research, but it takes some time to understand the process of building the kernel and to figure out how to properly pack it again... Also the sources are a little bit different for i9505.
kosmodisk said:
I've tried a lot of ROMs - 4.4.2, also older 5.0.1 with no result...
I haven't tried UHOA7 I've tried UHOB7 instead, so I'll probably give it the shot, but I can't imagine how it could fix this issue (maybe if it for some reason has the touch-cypress FW update forced...)
- I've seen that on some German forums reverting back helped, but it wasn't my case (+it didn't fix the problem for many others...)
As I've wrote before, they've created modified kernel (with forced touch key FW reflash - bypassed version check) for a little bit different phone on the Vietnamese forum (see the link in my previous post) and it seems that it would be quite easy for somebody who has some knowledge with kernel compilation... (it would just need small modification in the "if" condition of 1 kernel source file) I've tried to do some research, but it takes some time to understand the process of building the kernel and to figure out how to properly pack it again... Also the sources are a little bit different for i9505.
Click to expand...
Click to collapse
No idea, another friend of mine (different than the one who gave me her "broken" i9505 for fixing), who had the same problem with his own i9505 told me that with the I9505XXUHOA7_OXAHOA7 he fixed it. And sent me the Mega link, as it's not on SamMobile (or I didn't find it): https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I couldn't try it by myself, because I gave back the "broken" i9505 I was trying to fix to her owner before I was told about HOA7.
U know a lot more about this than me. Maybe you can give a try to that HOA7 Mega link, and see if it really works, or if my friend was extremely extremely lucky, and still doesn't know it (and ofc, doesn't know what the hell fixed his phone, and how).
Anyway, if u decide to give a try to the I9505XXUHOA7_OXAHOA7 one, don't forget to come back to tell us if it worked or... nothing. I keep fingers crossed!!!
Oh, and ofc: THANK YOU!!!
oiluj said:
No idea, another friend of mine (different than the one who gave me her "broken" i9505 for fixing), who had the same problem with his own i9505 told me that with the I9505XXUHOA7_OXAHOA7 he fixed it. And sent me the Mega link, as it's not on SamMobile (or I didn't find it): https://mega.nz/#!VwcgXSQC!uGAhPxEuRrl-luS3sw8JmoPnjP4ybxrlsY4XcfFaWKE
I couldn't try it by myself, because I gave back the "broken" i9505 I was trying to fix to her owner before I was told about HOA7.
U know a lot more about this than me. Maybe you can give a try to that HOA7 Mega link, and see if it really works, or if my friend was extremely extremely lucky, and still doesn't know it (and ofc, doesn't know what the hell fixed his phone, and how).
Anyway, if u decide to give a try to the I9505XXUHOA7_OXAHOA7 one, don't forget to come back to tell us if it worked or... nothing. I keep fingers crossed!!!
Oh, and ofc: THANK YOU!!!
Click to expand...
Click to collapse
I got the problem but only the back button was not working. Did factory reset and it did not help.
Then i flashed I9505XXUHOA7_OXAHOA7 from your link with Odin 3.10 and YES!!! i can confirm it is working again So happy now.
It is my Moms Phone now and she loves it!!. I was unly helping her doing the OTA so she realy hated me and SAM for F****** up her phone.
This tread realy saved my ass
Can confirm this is happening to me as well. All firmwares starting from HOF2 seem to have this problem so if you encounter this, downgrading to a HOE/HOD firmware should correct this bug. The downside is that without a proper fix, you won't be able to update.
BUBA0071 said:
I got the problem but only the back button was not working. Did factory reset and it did not help.
Then i flashed I9505XXUHOA7_OXAHOA7 from your link with Odin 3.10 and YES!!! i can confirm it is working again So happy now.
It is my Moms Phone now and she loves it!!. I was unly helping her doing the OTA so she realy hated me and SAM for F****** up her phone.
This tread realy saved my ass
Click to expand...
Click to collapse
@kosmodisk, did u read that? have u tried I9505XXUHOA7_OXAHOA7 by urself? Ur conclusions?
@BUBA0071:
- Did u look before (and after) flashing HOA7 which FW had (and have now) the touch keys? Remember: *#2663#
- After flashing HOA7, did u update again to latest one? Did the update work well this time, and now u have latest version with touch leys working?
MoLoCEL said:
Can confirm this is happening to me as well. All firmwares starting from HOF2 seem to have this problem so if you encounter this, downgrading to a HOE/HOD firmware should correct this bug. The downside is that without a proper fix, you won't be able to update.
Click to expand...
Click to collapse
I tried with a HOE1 one and... didn't work. Couldn't try one even older, but HOE1 seems to keep the same problem.
the file is corrupted when i try to extract it ? any other files that i can try ? im having the same problem right now with my s4.. have been looking for quiet some times now, and this is my only hope, hope this way will works smoothly...
wild081 said:
the file is corrupted when i try to extract it ? any other files that i can try ? im having the same problem right now with my s4.. have been looking for quiet some times now, and this is my only hope, hope this way will works smoothly...
Click to expand...
Click to collapse
download it again
@oiluj
HOE3 works for me. Problems start from HOF onwards.
I have also tried flashing HOA7 DBT and upgrading. Problem persists. My touchkey firmware is 0x1a and won't update no matter what Firmware package I tried. Up to now i have tried: GNG2, GNI2, GNK4, HOA7, HOB7, HOD7.
I'm pretty sure a rom (custom or early kitkat/lollipop leaks) caused this, altough I never flashed the initial chinese leak.
MoLoCEL said:
[MENTION=3170873]I'm pretty sure a rom (custom or early kitkat/lollipop leaks) caused this, altough I never flashed the initial chinese leak.
Click to expand...
Click to collapse
The phone that that girl gave to me, for fixing... was completely in official status. Always official ROMs, and official OTA updates, from first minute. And the problem was caused by latest official OTA update available: http://www.sammobile.com/firmwares/download/59777/I9505XXUHOJ4_I9505VFRHOF3_ATL/
So the problem was not caused by any custom ROM or a not official one.
oiluj said:
@kosmodisk, did u read that? have u tried I9505XXUHOA7_OXAHOA7 by urself? Ur conclusions?
@BUBA0071:
- Did u look before (and after) flashing HOA7 which FW had (and have now) the touch keys? Remember: *#2663#
- After flashing HOA7, did u update again to latest one? Did the update work well this time, and now u have latest version with touch leys working?
I tried with a HOE1 one and... didn't work. Couldn't try one even older, but HOE1 seems to keep the same problem.
Click to expand...
Click to collapse
Hardware key firmware 0X12 parth 0X1a (when it was not working, dont know if it have changed after german firmware flash). I have not updated again, think my CSC is blocking. It stayed on NEE after update to German firmware.
It was NEE I9505XXUPOJ2 firmware that F***** up my Phone
BUBA0071 said:
Hardware key firmware 0X12 parth 0X1a (when it was not working, dont know if it have changed after german firmware flash). I have not updated again, think my CSC is blocking. It stayed on NEE after update to German firmware.
It was NEE I9505XXUPOJ2 firmware that F***** up my Phone
Click to expand...
Click to collapse
unfortunately I've tried I9505XXUHOA7_OXAHOA7 with no luck (even with repartition when flashing) - the buttons still don't respond
BUBA0071, I'd like to ask which custom ROM have you tried? It seems that your keys have FW of version 0x1a which should be newer than 0x12, so this could lead to some sollution. Was it some cyanogen mod or MIUI?
thx
kosmodisk said:
unfortunately I've tried I9505XXUHOA7_OXAHOA7 with no luck (even with repartition when flashing) - the buttons still don't respond
BUBA0071, I'd like to ask which custom ROM have you tried? It seems that your keys have FW of version 0x1a which should be newer than 0x12, so this could lead to some sollution. Was it some cyanogen mod or MIUI?
thx
Click to expand...
Click to collapse
Wups it have been some time since it was custum, but in any cace it must have been some of the first lollipop roms. I gave to my mom 13 feb 2015 and i did a lot of flashing before that, i think one of the roms i tryed was Project Chaos. but also i tryed all the google editition roms for i9505 and cyanogen.
but when it whent back to stock it i used PDA I9505XXUHOD7 CSC I9505NEEHOD2 NEE firmware
I've got a question. When you flash the HOA7 file from the Mega link, do you use only the AP file, or you use AP,BL,CP, CSC and PIT files?
I'm gonna try to fix my S4 but i'm not sure about the right process I should follow.
Thank you!
My 3A was running perfect when update A310FXXU2APDC came out. After updating I have sometimes problem with touchscreen. Sometimes i must press something twice or more to get it to work. No matter keyboard or icon or else. Do anyone encountered this problem before? Before touchscreen was super responsive. Will hard reset help?
kabuki8888 said:
My 3A was running perfect when update A310FXXU2APDC came out. After updating I have sometimes problem with touchscreen. Sometimes i must press something twice or more to get it to work. No matter keyboard or icon or else. Do anyone encountered this problem before? Before touchscreen was super responsive. Will hard reset help?
Click to expand...
Click to collapse
Same problem here, screen unsensitive and looks "crazy" often after unlock, looks related to the same software update. Hard reset didn't help for me. Any news for you?
Nope. Hard reset didn't help. No option to downgrade through Odin. I think that we must wait for next firmware update. Probably few months. I will write message to Samsung about this problem. Please do the same so they will know that there's an issue with firmware.
Hey guys, I have an A9 and had the same problem. I could barely navigate through the phone as touchscreen was non- responsive. I resolved the issue by upgrading to newer software release. I now have no problem.
You can downgrade to older version that was working via Odin. Get the required file from sammobile. If you are running 5.1 just make sure that OEM Unlock is allowed {developer option in settings}.
A new software update is out, it is called "A310FXXU2APE1".
I can't flash it until this week-end but I hope it is the good one !
Storka said:
A new software update is out, it is called "A310FXXU2APE1".
I can't flash it until this week-end but I hope it is the good one !
Click to expand...
Click to collapse
Please let us know when you falash this ROM if it helped
*#2663# then update all FIXED i hope you phone the best again hehe keep smile broo
harris210793 said:
*#2663# then update all FIXED i hope you phone the best again hehe keep smile broo
Click to expand...
Click to collapse
Thank you very much, this fixes the touchscreen lag
Thx to harris210793...
Thats work properly on my galaxy a3 2016...
Try *#2663#...and all my touch problem has fixed...
I had this problem for a few days, unresponsive touch, i couldnt write a single word without errors... and also my phone wouldnt recognize codes like *#2663* etc.,
I upgraded to a higher number firmware from sammobile/androidfilehost A3 2016 from A310FXXU3 to A310FXXU4( i found firmware for my country and flashed it with Odin 3.10.) and it fixed the touch and i could also enter codes and manage those subprograms with ease.
My galaxy s4 i9500 had kitkat installed and it was updated to lollipop last year. Thereafter in september while installing ota update phone restarted and suddenly back and menu key were gone blank.
Trued every possible trouble shoot available on xda and other sites to no avail.
1. Installed Stock kitkat again.
2. Installed other lollipop firmwares.
3. Installed cyanogenmod 12.1
4. Wiped phone many times using twrp.
5. Change of strip cable also did not work.
6. *#2663# menu shows blank in place of touch key firmware version/update.
Please if somebody could only figure out what has actually turned the phone like this..even if this is not solvable..at least i should know what went wrong..
Thanks.
There is a similar problem with the GT-I9505 models too.
It's probably related to a faulty update or something.
I don't know if there is anything you can do without professional help.
What you have to do is: you have to force the touch key firmware to update somehow.
GDReaper said:
There is a similar problem with the GT-I9505 models too.
It's probably related to a faulty update or something.
I don't know if there is anything you can do without professional help.
What you have to do is: you have to force the touch key firmware to update somehow.
Click to expand...
Click to collapse
Dear I have been looking for everywhere regarding force install touch key firmware but could not find any solution or patch.
Chupshah said:
Dear I have been looking for everywhere regarding force install touch key firmware but could not find any solution or patch.
Click to expand...
Click to collapse
There was a thread around here that might have some things you could try. I can't find it, but you can do a forum search.
It was for the GT-I9505, but some of it can probably be applied to yours.
Otherwise you might need the help of a professional since they have the necessary tools.
GDReaper said:
There was a thread around here that might have some things you could try. I can't find it, but you can do a forum search.
It was for the GT-I9505, but some of it can probably be applied to yours.
Otherwise you might need the help of a professional since they have the necessary tools.
Click to expand...
Click to collapse
I have gone through that thread it is about incompatible Touch Key and Part Key Firmware Version. I have already tried those fixes but no success. Even in that thread issue is not solved yet.
In my case that dialog box for touch key and parts key firmware update doesnot appear in *#2663#. :crying:
Hi all !
I'm here cause i really need your help and to be honest everything i've found on web so far, is telling totally the opposite things so i'm lost.
Let me explain a ltl, i purchased a Samsung Galaxy S7 Edge Duos/Dual Sim black version (SM-G935FD).
Actually i'm from France ( and i was travelling to Serbia for work, and broke my Note 4 )... The problem is i can't do any update from the phone "Registration Failed" when i click on it.
So after few hours on google, looks like the updates simply doesn't work cause i'm moving France - Serbia ... and the phone seems to be imported from Vietnam.
...
first of all, do you think this update problem is realy linked to this ?
second, i was searching on SAMMOBILE for SM-G935FD to try to put a French Firmware with odin (i don't even know if i can do such a thing without ****ing it up ?)... and on this model all i could find are countries from ASIA.
when i type *#1234# in call i get this :
AP : G935FXXU1BPJG
CP : G935FXXU1BPJG
CSC : G935FOXE1BPH1 (i'm not sure if its a O or a 0 ... the letter or the number :-/)
Model : SM-G935FD
in the Software Infos (in settings) i got this :
Android Version : 6.0.1
BaseBand Version : G935FXXU1BPJG
Kernel Version : 3.18.14-9519568
Version Number : MMB29K.G935FXXU1BPJG
...
please guys i spent a lot of money (in hurry) for this phone, and i'm scared that i got ****ed by the vendor...
if anyone here knows something and can help me... would mean a lot...
Thanks in advance for any kind of help guys.
please guys... if someone got any answer... would mean a lot...
as well if u need any information that can help you answer me feel free to ask...
thanks again.
No need to worry INAX93,
Firmware for 935F will work on 935-FD
Please go to the link below (external link)
http://www.sammobile.com/firmwares/download/115870/G935FXXU1BPLB_G935FOXA1BPL2_XEF/
You can download this firmware and flash it using Odin_3.12.3 in the download mode by pressing volume down+home+power key when ur phone is switched off and selecting the correct files (the firmware package contains 4 files, hence you need to select the correct slot) and you should be good to go with latest firmware for France...
Hope this helps...
max9979 said:
No need to worry INAX93,
Firmware for 935F will work on 935-FD
Please go to the link below (external link)
[not allowed link cause new member]
You can download this firmware and flash it using Odin_3.12.3 in the download mode by pressing volume down+home+power key when ur phone is switched off and selecting the correct files (the firmware package contains 4 files, hence you need to select the correct slot) and you should be good to go with latest firmware for France...
Hope this helps...
Click to expand...
Click to collapse
Thank you a million times! And yes it bhelps a lot!
I feel a lot better just with the hope your reply gave me!
So you are sure that i can go with this french firmware and will not get any trouble right? (cause the thing is that i'm not able to even find on Sammobile the firmware i currently have, and looks like its impossible to save from the device without rooting...)
I see a lot of people getring troubles with some functions not working...
And the last thing do you think the "registration failed" that i get when i click on manual update in the phone settings is linked to my location? (not being in Vietnam?)
Thanks a lot again!
Hello, french too, flashed Orange ROM for g935F on my brand new g935FD, everything OK.
Joyeux Noel
valiran said:
Hello, french too, flashed Orange ROM for g935F on my brand new g935FD, everything OK.
Joyeux Noel
Click to expand...
Click to collapse
Oh salut salut ! Thanks a lot! I guess i'll do try to do it today then! Thanks a lot!
Joyeux Noel a toi et aux tiens !
Merry Christmas to all of you guys! And thanks again for your help and kindness!
I use the ZTO 935F firmware on my 935FD with no problems, works without problems.
Dont worry INAX93 this is a confirmed official download of the French firmware. Dont worry it wont trip knox if done correctly and also your phone will be restored to french firmware without any trouble. I have done similar attempts of flashing official G935F firmware on my G935-FD without any problems am able to update and knox warranty also intact. So go ahead and wish you a merry christmas and a happy new year....
---------- Post added at 03:57 AM ---------- Previous post was at 03:56 AM ----------
Registration will also succeed INAX93 so dont you worry...just go ahead and flash the firmware....cheers....
Hi guys !
I just wanted to thank you all one more time ! with your help i did it ! now my phone (SM-G935FD) is with his French XEF firmware !
So thanks a lot to all of you for your help !
Merry Christmas and Happy new year to all of you !
Hi dear experts !
Hope all of you guys are going well, that the new year brought only positive things to you and your family !
I'm back in this thread cause I need your help one more time... everything was well until approx 6 months ago maybe a ltl more... maybe when the 7.0 version went out...
Actually that's when I faced the problem cause i bought a Gear S3 Frontier... I started having troubles with notifications mostly, they were delayed (sometimes for 3-4 hours !)...
While doing a lot of tests in all ways... i found that when i uninstalled all the updates linked to the "Google" app, or disabling it... it solved the problem... Then 6-7 months later i got pissed of cause i wanted to use some of the Google Now features... So i started searching again... after all kind of tests, i finally found that the problem also get solved when my Bluetooth is OFF... When it's set to off i can have the last update for the Google app and everything works fine...
So as i discovered that, i started thinking... maybe the only problem i have actually is a problem with my Bluetooth... as it started 6-7 months ago, 7.0 Version, Gear S3... the point is I started using the Bluetooth before (for my car) and it was always on... but maybe all mixed together... the Google app updates, the 7.0 Version and the Gear S3 king od bluetooth use... is not mixing well... or i don't know...
then i remembered that i flashed my S7 Edge (g935FD) from Vietnam with a firmware from France (g935F)... and maybe i did something incorrect while flashing that led to some Bluetooth troubles that i just discovered... (i had some problems with bluetooth before, like reconnecting randomly to a bluetooth device even if i disconnected it or things like that... )...
So i started searching and find out that there is actually few different way of flashing it, using odin... and i was unable to find a clear explanation of the differencies to be able to understand what i need to do to flash my phone again and in the best conditions.
There is people saying that a bad way of flashing can lead to bluetooth issues (and other things even worse but ok...), so if someone here can explain me, how can i manage to do it the best way... it would mean a lot...
differences between CSC and Home_CSC for example ? then some people are saying "check the re-partition" others say that you must avoid that... how do I know what is the best to do ?
then a lot of them are talking about CSC codes ?
I hope someone will have answers, i want to try to flash it again to try to solve this problem, without bricking it, and also without triggering the knox thing...
thanks in advance for help again...
Ps : the problem i was talking about is :
https://forum.xda-developers.com/s7-edge/help/s7-edge-notification-delay-problems-t3635161
or even :
https://us.community.samsung.com/t5...and-Answers/Delayed-notifications/td-p/114947
no one ? please guys...
still no one to help ?
guys i need just to know if it may solve my problem to flash my phone...
i need to know if i need to check the "re-partition" thing in Odin... somewhere they say "you must check it if you are changing the CSC" and other say "You must avoid checking this unless you have a Pit file" ...
So what is the correct thing to do ?