Related
4.0.3 Firmware for Galaxy Note — DXLP9 Hi I just flashed new Ics from thailand apparently with repaired kernel, and I have a little problem it cconsist only asian languages and few versions of english , is there any way to add more european languages i.e.polish?
pavulon77 said:
4.0.3 Firmware for Galaxy Note — DXLP9 Hi I just flashed new Ics from thailand apparently with repaired kernel, and I have a little problem it cconsist only asian languages and few versions of english , is there any way to add more european languages i.e.polish?
Click to expand...
Click to collapse
Repaired Kernel?
How do u know that he Kernel has been repaired?
You have prefix [Q]
then why you creating in general? There is already Q n A section.
4.0.3 Firmware for Galaxy Note — DXLP9 Hi I just flashed new Ics from thailand apparently with repaired kernel,
Click to expand...
Click to collapse
So are confirming it is repaired OR are you asking?
this is merely leaving ppl confuse.
Add it properly.
Appologies
Sorry for the confusion created, as it was my first post i did not strictly follow the rules , but I learn pretty quick.I could not quote the other forum cause it is allowed only once you have published 8 or 10 posts..That was just a rumour about that kernel apparentely being fixed I wanted to confirm with you guys , the pros!
Word of warning!
Word of warning ! for those who try to root thei galaxy note having this ROM what i just did , almost bricked the phone I followed Dr Ketan's guide to get root access when I flashed via 1,85 odin the file that was provided in guide, when the phone rebooted I got the message that google calendar is not accessible and something about google too, then when I try sing up with a google account when I was trying to type letters I was getting "null" word for each leter numbers were not affected,then I gave up and flashed GB with multiple CSC choice and now installing again the german version, no root yet !
If you have the "null" bug, it means your CSC is not set correctly.
If you had done a quick search you would have found plenty threads documenting this.
The easy fix is to use the dialer to access the CSC settings and set the CSC yourself.
http://www.inspiredgeek.com/2012/01...figuration-on-your-samsung-galaxy-sii-s2-tip/
-KJ
Cheers!
Thanx for the reply I think so personally that I had phone with code XEU and Rom was from Thailand and I tried to root it , now I am back on a german one thanx! Maybe I will try again with this one to follow Dr. Ketan's advice! Cheerio!
pavulon77 said:
Word of warning ! for those who try to root thei galaxy note having this ROM what i just did , almost bricked the phone I followed Dr Ketan's guide to get root access when I flashed via 1,85 odin the file that was provided in guide, when the phone rebooted I got the message that google calendar is not accessible and something about google too, then when I try sing up with a google account when I was trying to type letters I was getting "null" word for each leter numbers were not affected,then I gave up and flashed GB with multiple CSC choice and now installing again the german version, no root yet !
Click to expand...
Click to collapse
Please remove warning, this is common issue. It may create unnecessary hype. Your device is not bricked.
If you hav posted it before doing anything it may solved it in just 5min.
If you find null anytime, just flash csc.with odin n use same rom as you used.for pda. Leave all pit,repartition,pda,phone field empty.
This is issue is not related to root.
This is due to wrong csc.
Sent from my GT-N7000 using xda premium
pavulon77 said:
Sorry for the confusion created, as it was my first post i did not strictly follow the rules , but I learn pretty quick.I could not quote the other forum cause it is allowed only once you have published 8 or 10 posts..That was just a rumour about that kernel apparentely being fixed I wanted to confirm with you guys , the pros!
Click to expand...
Click to collapse
Link to the rumour perhaps?
Sent from my GT-N7000 using xda premium
Hey all
I just downloaded the latest stock firmware I9301IXCUANJ4 and after installation my stock camera app wasn't starting and gave me message "Camera server Error" So in reflashed firmware again and after that same problem occured so i contacted samsung and the already had reports of the bug and they are pulling it back for my region (the Netherlands )
So if any1 want the latest firmware go for the italion version that one is solid and has some battery drain improvement
How can i instal him? With kies or odin?
Sent from my GT-I9301I using XDA Free mobile app
Scarfangs said:
How can i instal him? With kies or odin?
Sent from my GT-I9301I using XDA Free mobile app
Click to expand...
Click to collapse
i installed it with odin
Im from italy dont know but i get some update on the phone 15mb size. I just accept and my phone go of and start to load some instalation after instalation someting about 110 application and then done my phone was one. This is the update or i need to instali with odin?
Sorry for my english
Sent from my GT-I9301I using XDA Free mobile app
Caimarcladev said:
i installed it with odin
Click to expand...
Click to collapse
have some problem with this new firmware camera dont work when you install i have also Luxembourg firmware run on my device i have juste downgrade to I9301IXXUANH1_I9301IPHNANG1_I9301IXXUANF2_HOME and now camera are work normaly
Caimarcladev said:
Hey all
I just downloaded the latest stock firmware I9301IXCUANJ4 and after installation my stock camera app wasn't starting and gave me message "Camera server Error" So in reflashed firmware again and after that same problem occured so i contacted samsung and the already had reports of the bug and they are pulling it back for my region (the Netherlands )
So if any1 want the latest firmware go for the italion version that one is solid and has some battery drain improvement
Click to expand...
Click to collapse
Hello, please do not say the latest version, because the last version has the camera bug as well.
The last confirmed working version is I9301IXXUANI1_I9301IITVANJ1_I9301IXXUANI2_HOME
I had just downgraded back from installing I9301IXCUANJ6, from the italian region. Hopefully it will avoid useless data wipes for other people :good:
Caimarcladev said:
Hey all
I just downloaded the latest stock firmware I9301IXCUANJ4 and after installation my stock camera app wasn't starting and gave me message "Camera server Error" So in reflashed firmware again and after that same problem occured so i contacted samsung and the already had reports of the bug and they are pulling it back for my region (the Netherlands )
So if any1 want the latest firmware go for the italion version that one is solid and has some battery drain improvement
Click to expand...
Click to collapse
Wich is the latest version? I9301IXCUANJ6 ?
xCoNDex said:
Wich is the latest version? I9301IXCUANJ6 ?
Click to expand...
Click to collapse
depending region from wher you are
spawk said:
depending region from wher you are
Click to expand...
Click to collapse
I have been testing all roms stock mentioned on xda forums and no one works, my camera is tottaly dead.....
xCoNDex said:
I have been testing all roms stock mentioned on xda forums and no one works, my camera is tottaly dead.....
Click to expand...
Click to collapse
yesterday i have flashed new firmware and got camera not work i have lanched odine and chek nand errase if uncheked and flashed downgrade old firmware and now camera are work but i have loste all my old setting and apps because errase del all your previous phone and install system from 0 test and you see
spawk said:
yesterday i have flashed new firmware and got camera not work i have lanched odine and chek nand errase if uncheked and flashed downgrade old firmware and now camera are work but i have loste all my old setting and apps because errase del all your previous phone and install system from 0 test and you see
Click to expand...
Click to collapse
Flashed with Nand erased disables, is that ok right?
I purchased my phone on spain, but its from ITA, im gonna test the last rom stock for this region, is the last thing left to prove
xCoNDex said:
Flashed with Nand erased disables, is that ok right?
I purchased my phone on spain, but its from ITA, im gonna test the last rom stock for this region, is the last thing left to prove
Click to expand...
Click to collapse
no flash with nand erased enabled
Again Camera Bug ( Server error)
spawk said:
yesterday i have flashed new firmware and got camera not work i have lanched odine and chek nand errase if uncheked and flashed downgrade old firmware and now camera are work but i have loste all my old setting and apps because errase del all your previous phone and install system from 0 test and you see
Click to expand...
Click to collapse
Hi Spark,
as some other users I have my problems with the Camera Bug. I flashed four in this forum recommended ROMs with wiping each time Cache, System and Internal Storage , and activated Nand Erase before flashing with Odin. But each time the error message appears again.
That somehow drives me crazy. Idon't know wht to do else. Any Idea?
Galaxy S3 Neo
Hello people
Great news, to fix S3 Neo camera server error you need to install stock rom I9301IXXUANH1 from Sammobile.
It really works
does any1 knows if the lates version (I9301IXXUANG1 from open Austria ) also has the camera bug?
cause they say this is the best firmware version with the lowest battery usage
New Phone (for mum ) and I thought lets flash new FW for Germany DBT for it... What the f**k! Camera stop working with this well known Server issue!
Its an GT-I9301I for European Region. Bought in Germany.
This one made the camera working again for me!
I9301IXCUANL1 - CYV - 08.12.2014
http://samsung-updates.com/details/40228/Galaxy_S3_Neoplus/GT-I9301I/CYV/I9301IXCUANL1.html
And this one works also
I9301IXCUAOA1 - PHE - 09 Jan 2015
http://www.sammobile.com/firmwares/download/42204/I9301IXCUAOA1_I9301IPHEAOA1_PHE.zip/
Thanks goodness. Thought I bricked the phone right out of the box
Thanks to this thread for kicking me in the right direction!
when you bought the phone had the version XXUAN ... but if flashi firmware XCUAN .... the camera will not work and will fail. If you would like to solve the problem you have to flash the firmware again that had your phone when it was bought
fraross said:
when you bought the phone had the version XXUAN ... but if flashi firmware XCUAN .... the camera will not work and will fail. If you would like to solve the problem you have to flash the firmware again that had your phone when it was bought
Click to expand...
Click to collapse
that's right. we've got 2 versions with 2 cameras. xc camera and xx camera. this is not a bug. people just flash the appropriate rom for each. don't mix.
If it's not a bug, than why does the official ota flash the wrong update?
putti71 said:
If it's not a bug, than why does the official ota flash the wrong update?
Click to expand...
Click to collapse
Maybe because OTA will flash updates for the current installed firmware. For example if you have got a XCUAN firmware OTA will fash the updated version for XCUAN. if you have got a XXUAN firmware OTA will fash the updated version for XXUAN. if the camera won't work after the update you have to install the correct update manually. You can find firmwares on SAMMOBILE
Anyone in the UK got there OTA or Kies Lollipop update yet?
If you have flashed the German DBT & the CSC has changed will it change back to the UK CSC if flashed later with a UK Firmware?
If you have flashed how is it running?
Ta
@home said:
Anyone in the UK got there OTA or Kies Lollipop update yet?
If you have flashed the German DBT & the CSC has changed will it change back to the UK CSC if flashed later with a UK Firmware?
If you have flashed how is it running?
Ta
Click to expand...
Click to collapse
Got a UK version on EE and flashed German rom with odin. Working well and nice and snappy. Had to re root it though and re install CM recovery.
I have a SIM free note 4 bought from Samsung estore, nothing on mine yet.
@home said:
Anyone in the UK got there OTA or Kies Lollipop update yet?
If you have flashed the German DBT & the CSC has changed will it change back to the UK CSC if flashed later with a UK Firmware?
If you have flashed how is it running?
Ta
Click to expand...
Click to collapse
No update for me yet, however I think that Samsung will provide the network provider with the build then the network provider will add there bloatware and so on. I'm not 100% sure on this though.
Based on the CSC changing to a German CSC when I flashed the German DBT I'd have a guess and say flashing a UK ROM via Odin it would again change the CSC. Just a guess..
I have installed the German DBT and so far so good..
markgilmour99 said:
Got a UK version on EE and flashed German rom with odin. Working well and nice and snappy. Had to re root it though and re install CM recovery.
Click to expand...
Click to collapse
Hi mark, just wondering but I have a n910f UK version and I flashed the German lollipop build through Odin yesterday, although after giving it some time to boot it upgraded all of the pre-installed apps, the phone booted but all that showed up was a black screen and an empty notification bar, and kept rebooting over and over. anyone know what the problem could be?
xjw1 said:
Hi mark, just wondering but I have a n910f UK version and I flashed the German lollipop build through Odin yesterday, although after giving it some time to boot it upgraded all of the pre-installed apps, the phone booted but all that showed up was a black screen and an empty notification bar, and kept rebooting over and over. anyone know what the problem could be?
Click to expand...
Click to collapse
Hi xjw1,
Not really knowledgeable enough to help much here. You don't say what you flashed the rom over. I flashed over bobcat rom and had already updated the bootloader too. I also did a full wipe in recovery before using odin. If you ask here you should get a response from an expert. Good luck. http://forum.xda-developers.com/note-4/general/910f-official-lolipop-germany-dbt-t3029508
markgilmour99 said:
Hi xjw1,
Not really knowledgeable enough to help much here. You don't say what you flashed the rom over. I flashed over bobcat rom and had already updated the bootloader too. I also did a full wipe in recovery before using odin. If you ask here you should get a response from an expert. Good luck. http://forum.xda-developers.com/note-4/general/910f-official-lolipop-germany-dbt-t3029508
Click to expand...
Click to collapse
I flashed the official stock Lollipop firmware straight from SamMobile, I forget what the baseband was as SamMobile is down at the moment, but thank you for your reply, I'm going to check out the link you provided now.
Sent from my SM-N910F using XDA Free mobile app
@home said:
Anyone in the UK got there OTA or Kies Lollipop update yet?
If you have flashed the German DBT & the CSC has changed will it change back to the UK CSC if flashed later with a UK Firmware?
If you have flashed how is it running?
Ta
Click to expand...
Click to collapse
Got Kies Lollipop on Friday on my EE.
All running fine
SM-N910K not rooted although I would like to get rid of the remnants of Korean
mklass said:
No update for me yet, however I think that Samsung will provide the network provider with the build then the network provider will add there bloatware and so on. I'm not 100% sure on this though.
Based on the CSC changing to a German CSC when I flashed the German DBT I'd have a guess and say flashing a UK ROM via Odin it would again change the CSC. Just a guess..
I have installed the German DBT and so far so good..
Click to expand...
Click to collapse
Yup you use the German update you get the German CSC, flash to a UK one you'll get a UK CSC. But there is almost no difference.You'd be better off sticking to this German one. Whenever an update is pushed you will get it first. If you flash a UK ROM you'll be back in the same situation you're in now waiting for an upgrade. Sometimes the UK providers are weeks/months behind the German updates.
If you want any new OTA updates as soon as Europe gets them stick with this ROM. That is unless you want the UK bloatware. I'm quite surprised the only German stuff is deletable. I bet the EE/Vodafone stuff won't be.
Edit: Actually I take that back, I just checked my CSC and my phone is showing as Polish OXA strangely enough. Well I'm pretty sure I'll still get the OTAs first. What I said should still count for German/Polish updates as they get them first so ..........(fingers crossed).
Flashed German update still retained my UK CSC
Like Mcshave said am better off with German update than EE bloatwares.
Sent from the future using my SM-N910F Note 7
Did you guys do a factory reset after flashing or just carried on with out the reset?
@home said:
Did you guys do a factory reset after flashing or just carried on with out the reset?
Click to expand...
Click to collapse
Hi Mate,
Flashed over my 4.4.4 no reset before or after and all data is still intact
McShave said:
Yup you use the German update you get the German CSC, flash to a UK one you'll get a UK CSC. But there is almost no difference.You'd be better off sticking to this German one. Whenever an update is pushed you will get it first. If you flash a UK ROM you'll be back in the same situation you're in now waiting for an upgrade. Sometimes the UK providers are weeks/months behind the German updates.
If you want any new OTA updates as soon as Europe gets them stick with this ROM. That is unless you want the UK bloatware. I'm quite surprised the only German stuff is deletable. I bet the EE/Vodafone stuff won't be.
Edit: Actually I take that back, I just checked my CSC and my phone is showing as Polish OXA strangely enough. Well I'm pretty sure I'll still get the OTAs first. What I said should still count for German/Polish updates as they get them first so ..........(fingers crossed).
Click to expand...
Click to collapse
But what does it mean if you are with German csc? Idk what csc means but does it add something that you use a German rom in another country? Still have not flashed it yet
I'm from Holland btw
Sent from my SM-N910F using XDA Free mobile app
Well I've got the German Rom on now, so far all seems well. I haven't done a reset just a dirty flash.
So all you guys who have done the same to your UK N4, will you flash the BTU when it's released or stay on the German Rom?
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!
Hello everyone. I recently bought an Samsung Galaxy S5 (SM-G900F). After I made the "first run set-up" , I went to Google Play to download all the apps I needed.And then Google Play suddenly stopped and an error poped out : "Google Play stopped working"..ok I tried again,after aproximatively 3 minutes the error shows up again and again..I know that Samsung has some problems with Google Play,so I tried some fixes found on the internet. I tried deleting all data,cache,and updates.. It worked.Looks like my phone has some "problems" with the new update (6.0.5) for Google Play Store. With the old one (5.x - sorry I can't remember the version),I have no problems. But,the other problem is that after a few minutes,the app updates itself to the last version. I even tried to make a factory reset,but the error still shows up (I tried to reset the phone from the settings and from the recovery boot). I don't have a problem using the old version of PLay store,but I also can't use an outdated version for too long. Is there any way to fix it? I'm trying all kind of fixes found on the internet for hours and I'm getting angry. Is there any way to fix it,or I can send it to warrany? (I'm afraid to send it to warranty because I know that all they do there is to reset my phone and I lose a lot of time waiting to make a freaking reset that I can make even myself).
I would have posted an image with the error,but this forum doesn't allow me to put links into my threads for "security reasons".
So please,if you can help me It would be awesome. Thank you again and sorry for my bad english.
I forgot to mention,phone model is SM-G900F with Android 5.0 (I can`t make update to 5.1,I dont know why.)
Try reflashing 5.0 stock firmware using Odin
Note: G900F does not have 5.1.1 yet
Daniel Iuga said:
Hello everyone. I recently bought an Samsung Galaxy S5 (SM-G900F). After I made the "first run set-up" , I went to Google Play to download all the apps I needed.And then Google Play suddenly stopped and an error poped out : "Google Play stopped working"..ok I tried again,after aproximatively 3 minutes the error shows up again and again..I know that Samsung has some problems with Google Play,so I tried some fixes found on the internet. I tried deleting all data,cache,and updates.. It worked.Looks like my phone has some "problems" with the new update (6.0.5) for Google Play Store. With the old one (5.x - sorry I can't remember the version),I have no problems. But,the other problem is that after a few minutes,the app updates itself to the last version. I even tried to make a factory reset,but the error still shows up (I tried to reset the phone from the settings and from the recovery boot). I don't have a problem using the old version of PLay store,but I also can't use an outdated version for too long. Is there any way to fix it? I'm trying all kind of fixes found on the internet for hours and I'm getting angry. Is there any way to fix it,or I can send it to warrany? (I'm afraid to send it to warranty because I know that all they do there is to reset my phone and I lose a lot of time waiting to make a freaking reset that I can make even myself).
I would have posted an image with the error,but this forum doesn't allow me to put links into my threads for "security reasons".
So please,if you can help me It would be awesome. Thank you again and sorry for my bad english.
I forgot to mention,phone model is SM-G900F with Android 5.0 (I can`t make update to 5.1,I dont know why.)
Click to expand...
Click to collapse
Well,I'm very dissapointed because I got my phone to some GSM Services,and most of they told me that this is a common issue for Samsung devices and you must be pretty lucky to not get into such errors with an Samsung phone. So yes,I will "maybe" try to flash the original firmware with Odin,but I don't think it will help. So anyway thank you for helping me,I will try to use this phone with this bulls*it error and maybe,maybe (which is quite impossible) Samsung will release an update that would solve this problem.
Whats your firmware build number?
Daniel Iuga said:
Well,I'm very dissapointed because I got my phone to some GSM Services,and most of they told me that this is a common issue for Samsung devices and you must be pretty lucky to not get into such errors with an Samsung phone. So yes,I will "maybe" try to flash the original firmware with Odin,but I don't think it will help. So anyway thank you for helping me,I will try to use this phone with this bulls*it error and maybe,maybe (which is quite impossible) Samsung will release an update that would solve this problem.
Click to expand...
Click to collapse
Just to lighten you up, this problem is not "common" in Samsung devices. My family and relatives uses mostly Samsung phones and tablets and never did we have this problem, even on two Galaxy S5s (G900F and G900FD).
Flashing the stock firmware should help.
Sent from my SM-G900F using XDA Forums
Well,I reflashed the stock rom with Odin3.9 but this problem still occurs. If you are talking about Baseband version than this is it: G900FXXU1BOJ1
EDIT: After 2 months of trying to fix the problem,it still occurs.