Related
This morning connected my Galaxy Tab to KIES and it prompted that there is an update !!
it took ages to download its binary files then finally after it got done, it gave me a decryption error !!
I have changed my sales code to gain access to market, could this be the problem or do i redownload the files !!
Isn't there a way to UPGRADE fw via OTA? or placing update.zip in root of sd nd flashing from recovery? (similar to HTC devices)
how do I upgrade to the latest version? help please
Cheers
Jackie
PS: Please find attached the firmware code : current and new !
Are you UK based Jackie? Just guessing as you said cheers! I've seen nothing this morning though have read there was an Android Market update which I had already downloaded and applied, maybe why I'm seeing no update.
no I'm based in UAE !! that's just teh way I speak !!
Ah right, nice to read it all the same, Cheers!
so anyone has any idea?
Jackie,
I don't bother with Kies.... It put my SGS in a right mess and couldn't be used until I sorted it out with another ROM and a different PC software upgrader by the name of Odin.
Your best bet is to go on over to samfirmware.com and check out the latest ROM's available.
I'm sending you also a link which although was written for the SGS and Froyo it's still relevant for ROM files for the Tab and how to use Odin.
See here:- How to use Odin to Upgrade the SGS to Froyo
Beards said:
Jackie,
I don't bother with Kies.... It put my SGS in a right mess and couldn't be used until I sorted it out with another ROM and a different PC software upgrader by the name of Odin.
Your best bet is to go on over to samfirmware.com and check out the latest ROM's available.
I'm sending you also a link which although was written for the SGS and Froyo it's still relevant for ROM files for the Tab and how to use Odin.
See here:- How to use Odin to Upgrade the SGS to Froyo
Click to expand...
Click to collapse
How do I know which is the latest ROM is for my TAB !
I checked out samfirmware, but it has loads of firmwares !
I'll check out what to do with ODIN though !
Thanks a lot
Cheers
jackie_jagger said:
How do I know which is the latest ROM is for my TAB !
I checked out samfirmware, but it has loads of firmwares !
I'll check out what to do with ODIN though !
Thanks a lot
Cheers
Click to expand...
Click to collapse
First, what ROM version do you currently have installed?
Next, look at the list of ROM's available see here.
You need to find out if you are on a European, Asian, Arabic, etc ROM and decide if you want to stay on that list or opt to another nation list.
For European lists JMA is the latest. There's a topic on JMA here.
PDA: P1000JPJJ2
Phone: P1000JXJJ1
CSC: P1000OJPJJ3
is what is being reported on *#1234# and samfirmware says this is the Arabic firmware and the latest for Arabic is P1000JVJL1 December 2010, not that I'm interested in any of the region specific apps - just wondering what has been fixed in these firmwares and also if flashing would delete all my data (I'm guessing it would)
I don't mind flashing a European firmware too, so which would be best?
PS: Tab is currently rooted with OCLF set ! =)
Cheers
Hi may i ask if you do firmware update does the tab have to be sim free not lock to a network as im on t-mobile uk, i dont want to brick my tab
thanks
jackie_jagger said:
PDA: P1000JPJJ2
Phone: P1000JXJJ1
CSC: P1000OJPJJ3
is what is being reported on *#1234# and samfirmware says this is the Arabic firmware and the latest for Arabic is P1000JVJL1 December 2010, not that I'm interested in any of the region specific apps - just wondering what has been fixed in these firmwares and also if flashing would delete all my data (I'm guessing it would)
I don't mind flashing a European firmware too, so which would be best?
PS: Tab is currently rooted with OCLF set ! =)
Cheers
Click to expand...
Click to collapse
It should not delete any data.
The browser and camera have been improved.
The browser now scrolls smoother.
The camera focus's much better.
No idea what other improvements have been made.
It does not really matter which firmware you wish to use BUT bear in mind a number of users who have performed a lagfix have had issues in upgrading the ROM.
You MUST ensure you remove any lagfix applied otherwise you stand a good chance in bricking the phone.
Also, ensure you have access to the Recovery and download mode.
You will need this if you 'brick' the phone.
ownhd2 said:
Hi may i ask if you do firmware update does the tab have to be sim free not lock to a network as im on t-mobile uk, i dont want to brick my tab
thanks
Click to expand...
Click to collapse
You need someone who is on a T-Mobile locked phone to answer this. I have heard of users on carrier networks who have run into issues.
Basically, unless you have a sound knowledge in what you are doing I would not attempt it until you get good solid advice.
seems like a long procedure, I'll hold off until i'm done with my exams....
also should I try KIES again? just in case ?? o.0
jackie_jagger said:
seems like a long procedure, I'll hold off until i'm done with my exams....
also should I try KIES again? just in case ?? o.0
Click to expand...
Click to collapse
You can try but I'd still make sure you have access to recovery and download first, just in case anything goes wrong.
Aight !! thanks a bunch !! will do
Got a similar problem... info says its P1000XXJID, valid euro firmware... Bought the tab in Hungary (Middle of europe), carrier free, and after looking at samfirmware.com's ROM list I was wondering about the updates.
Kies tells me this version can't be updated...
Can anyone help me with this problem?
Many, Many of us here in UK are having problems and are unsuccessful when trying to update/upgrade using Kies.
Hopefully Kies will get fixed properly to allow us all to use it.
ziffos said:
Many, Many of us here in UK are having problems and are unsuccessful when trying to update/upgrade using Kies.
Hopefully Kies will get fixed properly to allow us all to use it.
Click to expand...
Click to collapse
Even ActiveSync was better... at least it didn't offer the SW update...
to trick kies to update u could use kies registry patcher. I have sucsessfully updated via kies from jj3 -> jj7 (when no updates was availible)
read thru this post
http://forum.xda-developers.com/showthread.php?t=863386
Use the info from check fus and paste it in registry patcher, reboot pc - start kies - connect phone - something should happen.
Before anyone flames me down ive used the search multiple times to no avail and the capcha thing made me want to shoot myself.
i bought a galaxy s about a week ago (converted from and iphone) and im moderately happy. ive upgraded it to 2.2 and its 'better' but still lags n freezes and eats my battery in about 5hours but its ok.
now i want to upgrade to 2.2.1 because i hear it may fix some of those issues. i connected the phone to Kies which told me to go away as there was no update?
im really confused and new to the android scene, could someone help a noob out here lol?
it was originally locked to vodafoneuk and i have managed to unlock it.
any help would be greatly appreciated, all i want to do is make my galaxy s the best it can be performance wise.
in Kies my current software is PDA:JP7/PHONEJP5/CSC:JP7 (VOD)
thanks
Update is only if Vodaphone have an update ready .
Other route is the unofficial one and is outside warranty .
That involves flashing your phone via Odin with a stock Samsung firmware for your region . That is not your network customized firmware .
Or installing a customized rom with a faster kernel lagfixed etc .Again its outside warranty .
I would use rom kitchen as an easy method .
http://forum.xda-developers.com/showthread.php?t=817703
http://romkitchen.org/sgs/?s=home
https://spreadsheets.google.com/pub...MWI2LWlSR3IwM0dnYmdLX2kzMEE&hl=en&output=html
The following should give you a fast UK phone from the kitchen .
XXJPY Wipe CSC XEU Kernel Supercurios Modem JPY
the rest you can choose or just pick stock .
Again as a new user this is outside of warranty and may brick your phone though mostly recoverable .
jje
thanks mate greatly appreciated!
Just a caveat. Make sure you can access the recovery mode via the three button startup BEFORE you do anything or you may end up with big problems.
If you have Kies v1.xxxxxxxxx_102 you can use the kies reg hack utility found elsewhere on the forum to force an official 2.2.1 upgrade to your phone. It is also very worth while doing a full factory reset and cache clear before starting.
I upgraded to 2.2.1 about a month ago with my vodafone uk i9000. No mods or reg hacks.
When I first tried it said no udpates available, I let kies update itself fully and once that was done it immediately offered me 2.2.1.
It didn't wipe any phone data or apps, but it did wipe the icons on the touchwiz screens so I had to set them up again dragging from the apps list.
Vodafone didn't give me a branded phone though, I had one from the first batches they got into the country.
after upgrading do make sure it's set to make the wifi sleep if the screen goes off or your battery will suffer
There is a new Firmware I8700XXKC1 XXKB2 available:
samfirmware.com/apps/blog/show/7124400-new-firmwares-omnia-7-and-galaxy-s-ii-
Password: samfirmware.com
No thanks I got Official Nodo
Though would be interested to see if there are any firmware updates.
The screen flickering and slow rotation fixes
thank you but if it's nodo rom nobody is interesting except people who have developer account (chevron don't work on nodo...)
You're right...if you want to unlock your phone (and don't have an official dev account) this ROM cannot be used. I do wonder if there is any difference when you use the I8700XENJK1 ROM and officially update to NoDo...or when you use this ROM directly (radio version? Other differences?). Anyone care to test this ?
Its not that Id be the first one to test it if i had a way to back up all my game saves...Right i dont even have my phone dev unlocked cause that hape of crap chevron wont even work.
Deleted.
Deleted.
Deleted.
Same here. Only phone was updated. PDA and CSC remained the same.
VoltageMX said:
Same here. Only phone was updated. PDA and CSC remained the same.
Click to expand...
Click to collapse
You should feel lucky, you've been able to update the firmeware. Really, changing that CSC and PDA means that you are already at NODO and untill now there is no jailbreak for that. Besides there is a way to do with that CSC its just we don't want it yet, you know what I mean.
So this means firmware and radio is the same and only OS got updated?
evolutionqy7 said:
So this means firmware and radio is the same and only OS got updated?
Click to expand...
Click to collapse
No, its the other way around.
Lol this is just what the Omnia 7 needs... some more unknown firmware.
If your phone actually works i'd steer clear of flashing anything from Samsung... Maybe unfair but i'm smarting from having the dodgy bootloader.
I tried again and use this files:
Signed__Cetus_Europe_KB2_Phone.bin
Signed__Cetus_Europe_KC1_Eboot.eb0
Signed__Cetus_Europe_KC1_PDA.nb0
signed_CSC_Cetus_Europe_I8700DBTJK1.csc
Now PDA, Phone and CSC were updated:
PDA: I8700XXKC1
Phone: I8700XXKB2
CSC: I8700DBTJK1
What do the different parts do?
Eboot ist the bootloader.
What do the other 3 stand for?
If I flash to JK1 firmware, unlock with chevron and then update phone and eboot to KB2/KC1, will I have an unlocked NODO with latest firmware or only parts of the latest firmware?
Has anyone who flashed the new ROM noticed any differences yet?
EDIT:
Just read this on mobiletechworld:
- The capacitive buttons are now disabled if the screen is touched so that you can no longer accidentally exist an app/game while playing (this feature is also present in the latest Samsung Focus firmware).
Click to expand...
Click to collapse
I guess this will be in the PDA part.
Where did you get the last file? There are only three files in the zip. Oh i get it now
i just flashed my omnia :
the OS version after flashing is 7389 (i got 7392 before) , but as i connected it to zune, update notification showed up (post nodo, 7392, i am updating right now)
another difference i notice : different default lock screen picture.... yay ... less appealing tho..it is...a desert
HansHalber2095 said:
What do the different parts do?
Eboot ist the bootloader.
What do the other 3 stand for?
If I flash to JK1 firmware, unlock with chevron and then update phone and eboot to KB2/KC1, will I have an unlocked NODO with latest firmware or only parts of the latest firmware?
Has anyone who flashed the new ROM noticed any differences yet?
Click to expand...
Click to collapse
Yes you will, I tested it with my stock rom, I just flashed the firmware only and not the whole ROM
So anyway to flash this and keep all the data?
josef_68 said:
I tried again and use this files:
Signed__Cetus_Europe_KB2_Phone.bin
Signed__Cetus_Europe_KC1_Eboot.eb0
Signed__Cetus_Europe_KC1_PDA.nb0
signed_CSC_Cetus_Europe_I8700DBTJK1.csc
Now PDA, Phone and CSC were updated:
PDA: I8700XXKC1
Phone: I8700XXKB2
CSC: I8700DBTJK1
Click to expand...
Click to collapse
Does it mean I do have to include the older JK1 CSC in order to flash PDA and Phone ? Will it update Phone only if I dont?
I really hope samsung addressed the reception issues (silence during calls) and stutter during audio playback. It is strange this newer firmware was not included with NODO delivered by MSFT, after all the rollout began two months later.
so if i flash this
Signed__Cetus_Europe_KB2_Phone.bin
Signed__Cetus_Europe_KC1_Eboot.eb0
Signed__Cetus_Europe_KC1_PDA.nb0
signed_CSC_Cetus_Europe_I8700DBTJK1.csc
I keep the OS and jsut update firmware?
evolutionqy7 said:
so if i flash this
Signed__Cetus_Europe_KB2_Phone.bin
Signed__Cetus_Europe_KC1_Eboot.eb0
Signed__Cetus_Europe_KC1_PDA.nb0
signed_CSC_Cetus_Europe_I8700DBTJK1.csc
I keep the OS and jsut update firmware?
Click to expand...
Click to collapse
no, as far as i understand it, the CSC goes hand in hand with the .bin, so leave the csc out and you will only update bootloader/radio and OS will remain unchanged.
made by eqlove196426597 from CHINA
MT15i_4.0.A.2.368_HK_ftf
http://u.115.com/file/aqz1z5i4
MT15i_4.0.A.2.368_HK_rooted_system
http://u.115.com/file/bhzudmfd
thx for eq，
i love u，hahaha
eqlove196426597 said:
made by eqlove196426597 from CHINA
MT15i_4.0.A.2.368_HK_ftf
http://u.115.com/file/aqz1z5i4
MT15i_4.0.A.2.368_HK_rooted_system
http://u.115.com/file/bhzudmfd
Click to expand...
Click to collapse
THANK YOU!!!
I guess you need unlocked bootloader to flashe the rooted system.img?
on http://u.115.com/file/bhzudmfd
If you see this text, below blue sign with 115 on it:
优蛋专用下载链接 then the below are links right next to it.
联通下载 - Unicom download 电信下载 - Telecom Download
or whatever but, these are the links for those like me who can't make much out of chinese text.
flashing went perfect, in this HK version there is also Asfalt 5 HD included, nice!
------------------------
My mirror for the rooted image:
https://rapidshare.com/files/3350520540/MT15i_4.0.A.2.368_HK_rooted_system.7z
MD5: F378E8B79ACBC8903A6B69B0E0711728
----------------------------------------
mirror of the FTF file
https://rapidshare.com/files/3725100388/MT15i_4.0.A.2.368_HK.7z
MD5: B4826194C2B54AACD483ECB0941DABB4
in this ROM you can not turn off the camera sound when taking pictures :| there is no such option, you can choose one of three sounds.
MT15i_4.0.A.2.368_HK_ftf
http://www.multiupload.com/7XOEGED282
I reuploaded to a better site
Been using this for a little over 12 hours and despite the new enhancements and slightly faster running speed, I've had nothing but problems with:
- Touchscreen response is all over the place
- Had to uninstall Swype as touchscreen was making things up as it went
- Connectivity with wifi is patchy, connectivity with mobile data is questionable at best
- Sync issues related to connectivity
- Battery drain is significantly higher.
Is this an official Neo FW or something that's been compiled from the Arc release? If so, might be best to wait until the Neo FW is released properly. The update works beautifully on the Arc, but on the Neo (I have both handsets) I'm flashing back to rooted 2.3.2 and applying 2.3.3 OTA to await the new OTA build.
I recommend flashing via Wotanclient. Then unlock bootloader.
Thanks to Bi4ary, rooting newest Xperia firmware(4.0.A...) is very simple and safe.
First you need RootXperia.zip from http://forum.xda-developers.com/showthread.php?t=1130639 Put it on your SDcard.
Then fastboot recoveryNeo.img from http://forum.xda-developers.com/showthread.php?t=1183465
In recovery install RootXperia.zip
Now if you want to relock bootloader, then get this ftf, made by Blagus from
http://forum.xda-developers.com/showthread.php?t=1134335
Remember to thank our fine developers for such great tools!
(I hope that RootXperia.zip stays maintained by Bi4ary)
Raoa said:
I recommend flashing via Wotanclient. Then unlock bootloader.
Thanks to Bi4ary, rooting newest Xperia firmware(4.0.A...) is very simple and safe.
First you need RootXperia.zip from http://forum.xda-developers.com/showthread.php?t=1130639 Put it on your SDcard.
Then fastboot recoveryNeo.img from http://forum.xda-developers.com/showthread.php?t=1183465
In recovery install RootXperia.zip
Now if you want to relock bootloader, then get this ftf, made by Blagus from
http://forum.xda-developers.com/showthread.php?t=1134335
Remember to thank our fine developers for such great tools!
Click to expand...
Click to collapse
I flash MT15i_4.0.A.2.368_HK_rooted_system.img is OK,just one poccess.
And what about the issues brought out by poster before me?
Been using this for a little over 12 hours and despite the new enhancements and slightly faster running speed, I've had nothing but problems with:
- Touchscreen response is all over the place
- Had to uninstall Swype as touchscreen was making things up as it went
- Connectivity with wifi is patchy, connectivity with mobile data is questionable at best
- Sync issues related to connectivity
- Battery drain is significantly higher.
Is this an official Neo FW or something that's been compiled from the Arc release? If so, might be best to wait until the Neo FW is released properly. The update works beautifully on the Arc, but on the Neo (I have both handsets) I'm flashing back to rooted 2.3.2 and applying 2.3.3 OTA to await the new OTA build.
Click to expand...
Click to collapse
i flashed the stock firmware and had none of the problems mentioned above, to me it seems exactly the same with the benefit of the new features....
Raoa said:
I recommend flashing via Wotanclient. Then unlock bootloader.
Thanks to Bi4ary, rooting newest Xperia firmware(4.0.A...) is very simple and safe.
First you need RootXperia.zip from http://forum.xda-developers.com/showthread.php?t=1130639 Put it on your SDcard.
Then fastboot recoveryNeo.img from http://forum.xda-developers.com/showthread.php?t=1183465
In recovery install RootXperia.zip
Now if you want to relock bootloader, then get this ftf, made by Blagus from
http://forum.xda-developers.com/showthread.php?t=1134335
Remember to thank our fine developers for such great tools!
(I hope that RootXperia.zip stays maintained by Bi4ary)
Click to expand...
Click to collapse
This worked for me 100% as posted in the other thread. No issues here. Just a faster phone,
No issues whatsoever with the hk-firmware. The only thing i've noticed is that the camera sound can not be disabled (not even in third party apps), but I suppose thats only because of the rules and laws in HK that does not allow silent cameraphones. It's however easily fixed when rooted by switching the sound files in the systems media folder.
Hello,
I have a MT15a, would that work on it or is it ONLY for MT15i?
Thanks!
Hi
i'm a new owner of experia neo
i want update to new firmware, but i don't understand a thing
what mean "the touchscreen response is all over the place" ?
i have some problem for the correct translation
wich is the problem, is less responsive? less feeling?
i will update official firmware with Pc companion, not rooted
maRRRco89 said:
Hi
i'm a new owner of experia neo
i want update to new firmware, but i don't understand a thing
what mean "the touchscreen response is all over the place" ?
i have some problem for the correct translation
wich is the problem, is less responsive? less feeling?
i will update official firmware with Pc companion, not rooted
Click to expand...
Click to collapse
It means that person had a problem with their touchscreen. It is not related to the update, it was just an individual error.
You can update without any problems using PC Companion or Sony Ericsson Update Service (recommended).
Ambroos said:
It means that person had a problem with their touchscreen. It is not related to the update, it was just an individual error.
You can update without any problems using PC Companion or Sony Ericsson Update Service (recommended).
Click to expand...
Click to collapse
Thanks, but
the firmware now is not available in europe
the update service say me the firmware 3.0 ... is the last
maRRRco89 said:
Thanks, but
the firmware now is not available in europe
the update service say me the firmware 3.0 ... is the last
Click to expand...
Click to collapse
They're still rolling it out. Generic Nordic has the update.
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!