Related
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!
With all the updating going on lately for the YotaPhone I am lost if the Chinese (YD-206) got the update? I mean without the hassle of trying to flash the RU version on it?
If not maybe could you help me find the cheapest YD-201 version? It's be greatly appreciated!
Also another question I had on my mind was how the performance is for simple VR games? I noticed it has Gyroscope and I wanted to use Riftcat and a leap motion to simulate a vive... Maybe use some freetrack with it to get some tracking so i can walk a little too! I don't wanna bore you all with the details but yeah do you guys think it can handle some of the games? I realize that riftcat just streams it from my PC but i'm not sure how intensive that is!
Thanks guys I appreciate it! Also if all works out and I get all that VR stuff going I'll keep you all updated! Again Thank You all so much
adc103 said:
With all the updating going on lately for the YotaPhone I am lost if the Chinese (YD-206) got the update? I mean without the hassle of trying to flash the RU version on it?
)
Click to expand...
Click to collapse
The Chinese version is unfortunately stuck on KitKat. Flashing to the RU firmware is not that hard and if it should fail you can always flash back to the Chinesae version.
Yes, I agree , it's easy , put handset in developer mode so your PC can talk to it, then install yotaflasher on the PC, 1 option to download your chosen firmware zip file then another option to flash your handset. If there is something wrong (normally adb drivers) you have not lost anything.
The problems will only start if it does not flash and you have to tinker.
But yes, I recommend that you try to update to the latest release.
Yes Yotaphone works very well with VR games, gets a little hot and uses battery , but so all handsets.
I think even if you buy the yd201 , you may not have an update selection, but I am not sure of this. They usually have a special modified retailer firmware with more languages and stopping updates. A few weeks ago when I ordered my yd206 there were plenty of international yd201s and even some white Yotaphone, but now there fewer.
Parmo100 said:
Yes, I agree , it's easy , put handset in developer mode so your PC can talk to it, then install yotaflasher on the PC, 1 option to download your chosen firmware zip file then another option to flash your handset. If there is something wrong (normally adb drivers) you have not lost anything.
The problems will only start if it does not flash and you have to tinker.
But yes, I recommend that you try to update to the latest release.
Click to expand...
Click to collapse
I think I am convinced too take my chance with the YD-206 now, I was just a little skeptical since I saw some others on the forum having problems trying to get it too RU. But in one of the threads a saw a solution if I can't get it too work by doing it manually.
I've been working at this non-stop for the past week, and I've finally found a way. I am not able to flash a European ROM on the Chinese Mate 9.
I came very close to bricking my device, so I'm currently making sure of the method. Here is what it looks like:
http://imgur.com/a/1ONOF
(I am long-pressing the home button to show it's fully google-ized, in both pictures, but I took my hand out of the picture for paranoia purposes)
So, how is it done? Through eRecovery. I will release the full method once I have tested it enough for public consumption, because I don't want people bricking their devices.
How does it work? It's... interesting.
The version showing up on the phone is the last Chinese firmware which was installed. It doesn't update to show what version it is. In the imgur picture, for instance, it says B109SP01, but it's actually B115 running on it. The phone still thinks it's a Chinese phone, so if you try to get an OTA, you'll probably be getting a Chinese OTA which will not work correctly. So in that sense, it's a bastardized version, and OTAs/updates will not work normally -- You'll have to flash them through a different method.
The positive side is, Google works. Completely. It comes installed out of the gate with account sync, and so on. Other than being Google-fied, some other differences include the permissions menu, the keyboard (SwiftKey is default), and a few other things here and there. The default theme looks strange, and I think it has to do with the cust partition not matching the actual model. This is something I'm currently looking into before release. I'm also looking into using version B122 (or newer if it becomes available) instead of 115.
I'm sure many of you want to get your hands on the European firmware and the method to install it. If you're interested in testing despite one-day-old pre-beta status, shoot me a PM, and I'll try to get you hooked up. In the future, because this method will require a lot of data transfer, I'm considering charging some money to people who download it, and setting up a proper server.
Anyway, for now, know that it's possible, and if you want to do it right away, get in touch with me and I'll try to help!
Update: I have now verified that it's possible to go back to the Chinese ROM. I should have something for those who contacted me wanting to test tomorrow. Since this is a LOT of work, priority will be given to those willing to make a donation.
Although I don't have a Chinese M9 I appreciate your efforts as this opens up the way to flashing other stock and maybe even custom ROM's. Well done!
blackspp said:
Although I don't have a Chinese M9 I appreciate your efforts as this opens up the way to flashing other stock and maybe even custom ROM's. Well done!
Click to expand...
Click to collapse
Unfortunately, I think that custom ROMs will not work with this method, because they're not signed by Huawei.
Wow, That's great news.
I really appreciate your efforts.
I think that you can get a little bit of money in return for your efforts.
I would like to participate in this plan.
Please notify me when the procedure is completed.
Thanks again!
So, here's where we are at right now:
We can flash the system partition of a European firmware, no problem. There's seemingly no issue there.
Where we get the issue is when we look at the cust partition. Because we can't change the actual region of the phone from all/cn to hw/eu, for example, the cust partition has issues. What I mean by issues is, you don't get any of the default themes, various software might be missing features, and so on. Your phone's model number also appears to change from MHA-AL00 to M300-AL00 if you flash the non-Chinese cust partition. When this happens, things go crazy, and you cannot see a proper version number, build number, or model number.
I am looking into making a 'bastardized' version of something to flash, using a Chinese cust partition with an international system rom. Theoretically, this could fix the issues to an extent. It will, however, probably give you a warning upon boot-up that the system has been tampered with, and so on. I will have more information later tonight, Japan time, when I get a chance to work on it some more.
The programs which go missing on a flash of the European firmware are the following:
AutoInStallAPKFromMcc HPLegacyPlugin HwPhoneService PlayGames
Books HwCloudDrive_Local LatinImeGoogle PlusOne
ChromeHomePage HwID Newsstand PredefinedEapSim
GameBoxGlobal HwOUC OMACP talkback
Appmanager HwBetaClub Instagram_Stub Todoist
Booking HwHealthPlatform_OVE Installer Todoist_ntp
DisableTodoistReceiver HwLogUploadService NewsRepublic Twitter
Facebook_Stub HwOUCBeta ProjectMenuAct WPS
Along with all the included themes, and the auto-installer which mounts via USB when you plug the phone in.
Obviously, some of these files are more important than others. All of the things really vital to being able to use the phone can likely be loaded via a Chinese cust partition, but the versions are probably different from the european versions.
Update:
I've obtained a server and am currently setting things up to bring this to the public. The first stage will be a private test. I'm still willing to take some testers who are willing to put their phones in the line of fire! I don't think the private test will launch today, because a new International B126 ROM just came out, so I'm going to base my work off of that for now.
After all the kinks are worked out, I will develop some kind of system for the general public to use. Eventually, this system will be one where you configure your DNS to my server, log into a website, choose what firmware you want to flash, then use eRecovery and that firmware will flash to your phone. I will have to customize all of the international firmware to work perfectly on Chinese devices, and I've yet to do that, but will be working on it. If there's a need, I can expand this system to other Huawei phones. It's exciting times for Mate 9 owners.
Hi duraraa
I have just received my 128g mate 9 in France. I will be happy tomake a donation and participate to the test. Please let me know.
v.kuo said:
Hi duraraa
I have just received my 128g mate 9 in France. I will be happy tomake a donation and participate to the test. Please let me know.
Click to expand...
Click to collapse
Sure, thank you for your interest. In the meantime, if you are currently on a version like B115 or higher, please downgrade to B106 / B109SP01 so you are familiar with the process.
Update: Now that we can install Google framework on the Chinese latest firmware, I have decided to cancel this project for now. I may keep a server alive to upload to unsupported/beta firmwares, but trying to get the European firmware working well on the Chinese Mate 9 is no longer a priority.
Which version of the firmware Duraraa ?
duraaraa said:
Update: Now that we can install Google framework on the Chinese latest firmware, I have decided to cancel this project for now. I may keep a server alive to upload to unsupported/beta firmwares, but trying to get the European firmware working well on the Chinese Mate 9 is no longer a priority.
Click to expand...
Click to collapse
Hi Duraaraa.
i might have missed something... how to put the framework on? Thanks so much - looking soo much forward to have Google on my AL00 phone.
weiaoli said:
Hi Duraaraa.
i might have missed something... how to put the framework on? Thanks so much - looking soo much forward to have Google on my AL00 phone.
Click to expand...
Click to collapse
Just search for GMS in the HiApp store. Huawei released a google framework installer.
But the app twin functionality in Chinese handset only allows QQ and wechat. Please continue with finding out how we can install European Rom on Chinese handset so we can have twin app functionality for whatsapp.
ewijaya74 said:
But the app twin functionality in Chinese handset only allows QQ and wechat. Please continue with finding out how we can install European Rom on Chinese handset so we can have twin app functionality for whatsapp.
Click to expand...
Click to collapse
If I flash the European rom on the Chinese handset, it's still QQ and wechat. Strange, eh?
Yes very strange....But there must be a way to fix this right?
Mate 9 from Taiwan
Hi everyone, keeping an eye on the market I found a very tempting offer on the 64GB version - HUAWEI Mate 9 64GB 4G Dual Sim SIM FREE/ UNLOCKED .
Now, my knowledge of ROM flashing is "level: what is a ROM?", but I am reading lots on the subject , but a couple of months ago I bought a P9 for my wife, chinese Al00 version, no problems to install Google Play but still many things are in chinese, the language correction for english or other EU languages sucks. That is why I decided not to go for Chinese versions unless there were exaustive guides on how to flash the mobile to an international or better european ROM.
Said all that, I wonder if anyone has found an easy way to solve the above mentioned issues - I assume everyone with a chinese version will have similar problems - and if you solved them otherwise.
Thanks for any information you might provide, and sorry if I missed key info to have this question properly addressed, but I will be happy to add it if asked.
Cheers,
Daniele
Hi, I assume someone much smarter than me will be able to point me to a Sony Xperia standard/stock ROM which I can flash with TWRP.
I had loaded TWRP and manages to accidentally wipe out the system with no backup (it's a new phone anyway). I found some ROMS from European telcos, etc. but would like to install the "standard" Sony Xperia ROM for XC.
Thanks in advance to anyone who can help.
PS. I think it would be easiest for me to able to install it through TWRP.... but obviously, anyway to recover my phone would be great.
PPS. Still can access device with adb and Flashtool, but not from Fastboot or Sony PC Companion.
PPS. I have installed OmniROM in the meantime... but don't want to spend too much time on it if I am going to wipe it out anyway.
PPS. I am in the US.
Update:
I found XperiaFirmware. It's downloading F5321_34.1.A.3.49_CE.ftf. Per the download website, will take about 18 hours on average, but it is progressing better than that.
I also found XperiFirm tool which downloads much faster, but I don't know which version. My understanding is that US customized is for CDA version of the phone. I also ran across the post about enabling the fingerprint reader by downloading the UK customized version... But based on latest attempts to do this, since UK version has been upgraded to Nougat, this approach is not working anymore...? But anyway, I could give it a shot to try a European version which is still on MM,
Update: *Whew*
I used XperiFirm to select a ROM. I didn't know which ROM, but I was intrigued to enable the fingerprint scanner. Due to some recent posts that the original method of using the Customized UK (or as they would say "Customised UK") version no longer works as the posted firmware was for Nougat. As a workaround, some people downloaded CE version, but CE version has also been recently updated to Nougat. I noticed a CE5 version which still seemed to be the MM version.
However, I also wasn't sure what differences I may see in the European version as some posters were complaining about some cosmetic differences, so I downloaded Customized US even though I thought I read somewhere it was for CDMA network. I also decided to download one called "Commercial and Journalists" which was the same MM version.
I decided to install it first as I was anxious about trying to get my phone back. I was able to load OmniROM but since there were some known issues, my preference was to use authentic Sony firmware. In addition, I took some low light pictures with the OmniROM version, and they turned out really bad. Not sure if it was the ROM or what, but it was very disappointing. Also, I couldn't get root access to it. Also, even though OmniROM seemed to support the fingerprint scanner, I couldn't get it to register my fingerprint well.
I downloaded the Commercial and Journalists version from XperiFirm, let it unpack it, and then used FlashTool to create the bundle, not including fwinfo.xml or the .ta files.
It started up Android ok, but I noticed I seemed to have lost my TWRP. Anyway, while starting up Android, guess what? The fingerprint enabled software was there... and it works like a champ!
Since I seemed to have lost TWRP, I started from instructions again from http://www.stupdroid.com/2016/10/root-sony-xperia-x-compact.html and was able to get it back.
Then, I tried to get root, but following the instructions, I got the error ""There is no su binary installed" when opening SuperSU.
I then flashed UPDATE-SuperSU-v2.46.zip from https://download.chainfire.eu/696/supersu/
And now I have root access!
Whew! I don't know what damage I've done overall... and since I don't have a nano SIM card yet, the worst case scenario is that what I have now doesn't work as a phone (but I doubt it). After what I went through (accidentally deleting the system from my Android phone), I now have a rooted Xperia X Compact with the fingerprint sensor enabled. Sometimes it's better to be lucky than good?
And, when I took some low light pics, they turned out better!
Hi Bro,
i need a help can you please give me the web link to download UK customized ftf or CE customized ftf. please its almost a month with xperia x compact but no fingerprint working. im unable to download it with my system its very old configuration. i badly want fingerprint working on my phone. can you please upload somewhere so that i can download and flash it directly, please....
Sorry for my bad english. Thanks in advance..
Nauju said:
i need a help can you please give me the web link to download UK customized ftf or CE customized ftf.
Click to expand...
Click to collapse
http://www.xperiablog.net/forum/resources/categories/xperia-x-compact.108/
Thanks a lot!!
XperienceD said:
http://www.xperiablog.net/forum/resources/categories/xperia-x-compact.108/
Click to expand...
Click to collapse
If i download and flash the CE.ftf will i get a working fingerprint??
Nauju said:
If i download and flash the CE.ftf will i get a working fingerprint??
Click to expand...
Click to collapse
Yep!
Central Europe firmware does enables Fingerprint scanner.
After flashing you will get four ota updates in a row.
A security patch for 6.0 and nougat afterwards.
Help plz..
Ftf file not showing on flashtool..
What will be the possible issues??
Nauju said:
If i download and flash the CE.ftf will i get a working fingerprint??
Click to expand...
Click to collapse
Nauju said:
Ftf file not showing on flashtool..
What will be the possible issues??
Click to expand...
Click to collapse
Update flashtool!
That will fix issues.
Hey all, I was wondering if anyone could provide me with the stock recovery image from N.
The original from MM will fail when trying to system update because the updates are looking for a newer version of the rom than it thinks I am running. I have not been able to find a newer recovery anywhere.
Help me, XDA. You're my only hope.
p.s. if someone could just give me the newest image I'll just try flashing it in fastboot.
I'm having some sort of software issue with my touchscreen only working intermittently. It works fine after waking from screen off but then decides to quit at some point. I wanna totally replace my system image and the OTA packages don't contain a system image.
In this MEGA link you'll find stock recoveries from Shakalaca. In my case, since mine came preloaded with MM, Nougat recoveries won't work for me. Maybe you'll different results from it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
+)KEV1N(+ said:
In this MEGA link you'll find stock recoveries from Shakalaca. In my case, since mine came preloaded with MM, Nougat recoveries won't work for me. Maybe you'll different results from it?
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w
Click to expand...
Click to collapse
I'll just say "thank you," but you can safely assume that it comes with several pages worth of exclamation points that I will omit for brevity.
Seriously, thanks! Hopefully this will work out!