Question Problem with OS Updates - Sony Xperia 5 III

I have an Xperia 5 III (XQ-BQ52).
I sent it to Sony for service after the fingerprint scanner stopped working.
I got the phone back with a new mainboard and now the phone just doesn't update. It's stuck in the old Android 11 build and it gets no OS updates or security updates.
The Xperia Companion also throws an error when I try to do the repair. The error is "UEGetPhoneInfoMissingInfo"
I tried am again in touch with Sony Support but its been a week and I still no solution. According to the latest phone call they are going to come back to me in 2 working days...
I really got fed up with this situation. Its been a month that I am not having a properly working phone.
There is no way I am sending the phone back to service. I hope they send me a new phone and get done with this.
Is there anything else I could try myself? Of course the obvious answer is flashing it with a firmware but that would void the guarantee. So I guess only thing I can do is wait?

Flashing the latest update for XQ-BQ52 with new flasher would work. It is the same as if you update via the xperia companion. Have you tried using sony Emma aplication instead? It might do a better job.

Yeah, I have downloaded Emma but it seems I have to open the bootloader in order to flash it. Wouldn't that void the warranty?
I am really pissed with Sony, they really have me in the dark with this. Its been almost two weeks and they don't tell me what to do. I tried to contact them and every time the answer is that they will have a feedback in 48hrs. Now I understand why they do so poorly in sales compared to the competition. For a business phone, that is a no go.

aggelosf said:
Yeah, I have downloaded Emma but it seems I have to open the bootloader in order to flash it. Wouldn't that void the warranty?
I am really pissed with Sony, they really have me in the dark with this. Its been almost two weeks and they don't tell me what to do. I tried to contact them and every time the answer is that they will have a feedback in 48hrs. Now I understand why they do so poorly in sales compared to the competition. For a business phone, that is a no go.
Click to expand...
Click to collapse
You can flash with newflasher without having to unlock bootloader. I thought that Emma still worked with locked bootloader...

@aggelosf
My 2 Cents: I'd also recommend to stay away from that hassle and use XperiFirm to download the latest firmware for your device and use newflasher to simply flash it. The whole process should take you an hour or so.

Sure, it would have been nice if I could stay away from the hassle but the fingerprint scanner has failed again. The phone is sent to service again.
I can understand the reason for the level of success of Apple now. It's not just the marketing. It's the after sales service too.

Related

Downgrading after new update? Also warranty and root/unlock questions

As a preface, I got the ATT one x a few days ago, so far I'm really happy with it, but would like to get rid of a bunch of the bloatware and want to get root.
So this morning I woke up to the update message. Now I read up on it the night before on these forums that I should wait to update if I want to root/etc, so naturally I don't want to update quite yet. But here's the problem. The message popped up so fast that I could barely read the message. My thumb must have been right above the accept button, since the message disappeared almost instantly and the process started up. I exited it as far as possible, and it seemed to work. I used apps on the phone, and everything seemed fine. As soon as I locked the phone again, it decided to reboot, initiating the update, all on its own. Even a forced power-off wouldn't stop the wheels turning. And now I feel like an idiot. So is there any way/what is the best way to downgrade or reverse the update?
TL;DR: I accidentally updated the new update, is there, and or what is the best way to downgrade so I can eventually root?
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
I know that with enough time I could find some of these answers on the forums, but because they are so lively, it's hard to keep track and sift through the forums for information. Thanks for your time and thank you in advance for your help.
In regards to the root on the update there is no way to downgrade or root given your situation at this time but hopefully one of the talented people here on xda wil find a new exploit like they did for the 1.85
As far as warranty goes someone else will.have to let you know.
Sent from my Nocturnalized Beast
same boat
I am in exactly the same boat. I didn't check the MD5 on a download of CR4.5 and it completed wiped my phone (SD Card as well). I was away from my laptop and had to wait days to get it back online. When I finally got it up and running, I was rooting through the one click and in checking the update, it updated to 2.20. So now I'm stuck.
I have my previous unlock token, but I'm not sure if that will do me any good. I don't want to do much until a new RUU becomes available.
misiek93 said:
As a preface, I got the ATT one x a few days ago, so far I'm really happy with it, but would like to get rid of a bunch of the bloatware and want to get root.
So this morning I woke up to the update message. Now I read up on it the night before on these forums that I should wait to update if I want to root/etc, so naturally I don't want to update quite yet. But here's the problem. The message popped up so fast that I could barely read the message. My thumb must have been right above the accept button, since the message disappeared almost instantly and the process started up. I exited it as far as possible, and it seemed to work. I used apps on the phone, and everything seemed fine. As soon as I locked the phone again, it decided to reboot, initiating the update, all on its own. Even a forced power-off wouldn't stop the wheels turning. And now I feel like an idiot. So is there any way/what is the best way to downgrade or reverse the update?
TL;DR: I accidentally updated the new update, is there, and or what is the best way to downgrade so I can eventually root?
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
I know that with enough time I could find some of these answers on the forums, but because they are so lively, it's hard to keep track and sift through the forums for information. Thanks for your time and thank you in advance for your help.
Click to expand...
Click to collapse
BB2DX said:
I am in exactly the same boat. I didn't check the MD5 on a download of CR4.5 and it completed wiped my phone (SD Card as well). I was away from my laptop and had to wait days to get it back online. When I finally got it up and running, I was rooting through the one click and in checking the update, it updated to 2.20. So now I'm stuck.
I have my previous unlock token, but I'm not sure if that will do me any good. I don't want to do much until a new RUU becomes available.
Click to expand...
Click to collapse
The ruu is out for the 2.20 on the HTC dev site
If you already have your unlock token you should be fine just run through the steps to unlock then root. Your still stuck with the new hboot so your previous nandroids will no longer work and you can no longer flash boot images from recovery.
Sent from my Nocturnalized Beast
misiek93 said:
As for my second question, obviously the warranty will be in question if I root/unlock. I've read that HTC will honor the warranty even if it's an unlock, but not a rom flash (even after a return to stock?) If I root/unlock, run into a problem, and return to stock will by warranty be effected? I've never done a warranty return, so would there be a difference if I tried to go through HTC, ATT, or Costco (purchase location)? The reason I ask is because my last phone's (Original Atrix, love it so much) wifi died before the 2 year period, and we had an upgrade on the family account, and this time the One x was purchased with American Express, so I now effectively have a 2 year warranty to cover such problems I might have.
Click to expand...
Click to collapse
Consensus seems to be that a warranty return to AT&T, they don't normally check for bootloader unlock at all. Technically, they can check, and void your warranty. But to this point, they don't seem to be. This is probably your safest bet. But that warranty is only one year.
Based on various reports by XDA users HTC seems to be much more strict about enforcing their own warranty terms. I would suggest going through AT&T rather than HTC.
For your AmEx warranty, I think that would be handled by AmEx (not AT&T). You should probably check through them, and see what the warranty terms our (might be handled by a 3rd party?). I think only someone that has had experience with the AmEx process could say for sure what would happen in this case. So maybe somebody will chime in.
redpoint73 said:
Consensus seems to be that a warranty return to AT&T, they don't normally check for bootloader unlock at all. Technically, they can check, and void your warranty. But to this point, they don't seem to be. This is probably your safest bet. But that warranty is only one year.
Based on various reports by XDA users HTC seems to be much more strict about enforcing their own warranty terms. I would suggest going through AT&T rather than HTC.
For your AmEx warranty, I think that would be handled by AmEx (not AT&T). You should probably check through them, and see what the warranty terms our (might be handled by a 3rd party?). I think only someone that has had experience with the AmEx process could say for sure what would happen in this case. So maybe somebody will chime in.
Click to expand...
Click to collapse
Amex is extremely lax. All they want is a copy of the original warranty and require doing the work at an authorized repair shop. Then they reimburse you, no questions asked.
GroovyGeek said:
Amex is extremely lax. All they want is a copy of the original warranty and require doing the work at an authorized repair shop. Then they reimburse you, no questions asked.
Click to expand...
Click to collapse
I kinda figured as much. They aren't in the business of fixing phones, so I guessed they either just farmed it out to a 3rd party company, or just paid up pretty easily. Credit cards (especially AmEx) also often cover things like lost luggage, travel insurance (cancelled flights, etc.) and I don't imagine they go through much hassle confirming that kind of thing either. They must figure that the extra business gained from offering their services (and yearly fees) outweighs the payouts they have to make.
Thanks for clarifying with your personal experience, probably useful to the OP.

DO NOT download the 4.4.4 update in the UK

:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked so apparently it's all my responsibility, not their's at all for pushing a corrupted file...
Basically stick to 4.4.2 as long as you can. If anything, 4.4.4 is a downgrade, at best a side-grade. Much like 4.4.x all together really - really wish i'd stayed on 4.3
So I there anything i can do to unbrick it? I'm buying a new one anyway, but might use the "bricked" one for testing ROMs or something but if I can't get to fastboot there's nothing much I can do.
Moto G will not power up
Plug it into the charger
Hold the VOL DOWN key
While still holding the VOL DOWN key, press and hold the POWER key
Hold both keys down for over 120 seconds. This is more than two minutes and will seem like a long time. You might want to time yourself to make sure you hold it longer than two minutes.
After holding the keys down for more than two minutes, release them.
The Flash Boot screen will display, and the Normal Reboot option will be highlighted
Press the VOL UP key and the device will start a normal reboot.
If you have tried the above and it didn't work, try this:
Plug in the phone for 15 minutes.
Proceed to Step 2 above.
Source: https://forums.motorola.com/posts/3d5eadc25d
Broken_motoG said:
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked
Click to expand...
Click to collapse
If the bootloader has mysteriously become unlocked, then clearly you did modify the phone and they are entitled to decline a refund. This is made perfectly clear when the procedure to unlock is executed.
That's why you should be careful of anything you do with the phone once the bootloader is unlocked.
Broken_motoG said:
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked so apparently it's all my responsibility, not their's at all for pushing a corrupted file...
Basically stick to 4.4.2 as long as you can. If anything, 4.4.4 is a downgrade, at best a side-grade. Much like 4.4.x all together really - really wish i'd stayed on 4.3
So I there anything i can do to unbrick it? I'm buying a new one anyway, but might use the "bricked" one for testing ROMs or something but if I can't get to fastboot there's nothing much I can do.
Click to expand...
Click to collapse
Hi, DO NOT take that from Motorola, because you live in the UK which is in Europe (Thats important) Motorola are legally obliged to help you as unlocking the bootloader/loading custom ROMs on to your device is seen as a legitimate practice and not a voiding act of your statuary warranty.
As long as you don't alter hardware they are NOT entitled to decline a refund/replacement under the circumstances, however they can refer you to the retailer you purchased it from but the rules still stand that they have to help you get a new/refurbished phone or a refund
Use this to prove it to them and make them pay up: http://fsfe.org/freesoftware/legal/flashingdevices.en.html
Hope this could be of assistance to you and I'm sorry if its off-topic but it needs to be made clear to all EU Motorola owners
TechMinerUK said:
Hi, DO NOT take that from Motorola, because you live in the UK which is in Europe (Thats important) Motorola are legally obliged to help you as unlocking the bootloader/loading custom ROMs on to your device is seen as a legitimate practice and not a voiding act of your statuary warranty.
As long as you don't alter hardware they are NOT entitled to decline a refund/replacement under the circumstances, however they can refer you to the retailer you purchased it from but the rules still stand that they have to help you get a new/refurbished phone or a refund
Use this to prove it to them and make them pay up: ht tp:// f sfe.org/f reesoftw are/legal/flash ingdev ices.en.html
Hope this could be of assistance to you and I'm sorry if its off-topic but it needs to be made clear to all EU Motorola owners
Click to expand...
Click to collapse
Thanks for that - didn't realise that law existed, but that will be really helpful :laugh::laugh::laugh::laugh:
Broken_motoG said:
Thanks for that - didn't realise that law existed, but that will be really helpful :laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
No problem, I checked on it before I installed CM on my Moto G last week
Hope I could help and good luck with the phone
Good luck with unbricking your phone, but oh no, I've already downloaded the 4.4.4 update!
Oh wait, my phone works just fine...
And if it immediately bricked your phone, how do you know that "If anything, 4.4.4 is a downgrade, at best a side-grade."?
startersorders said:
Good luck with unbricking your phone, but oh no, I've already downloaded the 4.4.4 update!
Oh wait, my phone works just fine...
And if it immediately bricked your phone, how do you know that "If anything, 4.4.4 is a downgrade, at best a side-grade."?
Click to expand...
Click to collapse
I don't want to get off-topic but if an update bricked your phone its a pretty BIG downgrade as it went from a phone with many uses to a paperweight (allbeit a pretty paper weight) as it has lost functionality and its the softwares fault.
Its personal opinion
OP needs to establish if he has simply not encountered the ''Moto G won't turn on' issue. I included instructions above. It could all be just bad timing.
Broken_motoG said:
:crying:
Basically the 4.4.4 update hard bricked my phone, won't even boot into bootloader. I made no modifications at all, not even root, only unlocking the bootloader. I was on the phone to motorola for half an hour trying to get a replacement, but they wouldn't hear a word of it because the boot loader is unlocked so apparently it's all my responsibility, not their's at all for pushing a corrupted file...
Basically stick to 4.4.2 as long as you can. If anything, 4.4.4 is a downgrade, at best a side-grade. Much like 4.4.x all together really - really wish i'd stayed on 4.3
So I there anything i can do to unbrick it? I'm buying a new one anyway, but might use the "bricked" one for testing ROMs or something but if I can't get to fastboot there's nothing much I can do.
Click to expand...
Click to collapse
I don't think this is anything to do with the update. If it was we would have heard about it from more that just you.
After all mine works perfectly fine after the update and I'm UK Tesco.
dethrat said:
I don't think this is anything to do with the update. If it was we would have heard about it from more that just you.
After all mine works perfectly fine after the update and I'm UK Tesco.
Click to expand...
Click to collapse
Same here and plenty of subtle improvements (get rid of the Carrier name woo-hoo) and bug fixes in 4.4.4 - (several features of my Automation app - MacroDroid suddenly work when they didn't before), not to mention one or two security patches. Slightly better battery life and noticeably smoother animations are a nice bonus too. New Dialler is a big improvement - the old one was ugly.
neu - smurph said:
Same here and plenty of subtle improvements (get rid of the Carrier name woo-hoo) and bug fixes in 4.4.4 - (several features of my Automation app - MacroDroid suddenly work when they didn't before), not to mention one or two security patches. Slightly better battery life and noticeably smoother animations are a nice bonus too. New Dialler is a big improvement - the old one was ugly.
Click to expand...
Click to collapse
It depends, my friend who has a Moto G update to 4.4.4 lost all functionality of his apps and his clock stopped working. It just depends as his phone wasn't rooted with no bootloader unlock
TechMinerUK said:
I don't want to get off-topic but if an update bricked your phone its a pretty BIG downgrade as it went from a phone with many uses to a paperweight (allbeit a pretty paper weight) as it has lost functionality and its the softwares fault.
Its personal opinion
Click to expand...
Click to collapse
Of course a bricked phone is useless, but something obviously went wrong with the OP's phone, and its probably a coincidence that it happened while updating. It's the absurdity of the comments "DO NOT download the 4.4.4 update" and "4.4.4 is a downgrade" that got me to post, because its pretty clear that many people have updated without any issue.
Not besmirching the OP's problem, and like I said, I wish him well in getting his phone working.
Also, depending how old the phone is and where you bought it from, isn't it an option just to return it to the seller for an exchange. Just tell them it stopped working and you want a replacement phone?

Noob root now slightly bricked G Flex 2

Hi all. My new phone was going greatish. It was a little laggy, so thought I would root it and remove some of the preinstalled junk. All went fine no problem.
I removed some of the vodafone (UK) stuff, and all was well. Some time later though, I get a message:
"Unfortunately, the process com.android.phone has stopped"
And now my phone won't find the network and message pops up every couple of seconds. I tried a factory reset, but I suspect this made it worse as I have now lost my backups from Titanium app. The phone is basically unusable as it is due to constant error message and no network.
I have tried to access the recovery menu, but i get an empty robot with "no command".
I have seen some mention of CIDs on other forums but haven't got a clue how to go about fixing it or even where to start.
Any help would be greatly appreciated as obviously the phone is absolutely brand new, and I'm very very upset about the whole thing! Not to mention the fact that I feel like an idiot!
Anyway, thanks in advance.
You deleted something that was not suppose to be deleted. Don't the stock tot file on this forum and follow the steps to Flash back to factory
http://forum.xda-developers.com/g-flex2/general/guide-lg-g-flex-2-stock-firmware-to-t3037593 follow the video and you should be up in running in no time . make sure this link support your version not sure which g flex2 Version you have.
Still no tot files available for the LG G Flex 2 (any variant). Sorry got to wait for some to become available.
Thanks for the input. I figured it would be something like that. Any idea when the files might be available? I don't mind being a guinea pig at this stage. My phone is LG H955 on Vodafone UK.
I am going to try and play dumb in Vodafone shop today and see if they'll replace it there and then (doubtful).
I suppose my other alternative is to return it to LG for Firmware Flash. Anyone know if this is possible and potential cost?
Strangely, I'm not so bothered about (temporarily) destroying my brand new phone too much, it's my sudden lack of connectivity that hurts the most.
Thanks guys
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
djjag1 said:
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
Click to expand...
Click to collapse
Stay positive. Hopefully those tot files come soon. I on the other hand what to experiment with my phone but need a tot file just in case I mess anything up.
If it's just your dialer that's acting up, have you tried a third party dialer to make phone calls?
djjag1 said:
Further update; I have spoken to LG tech support / repair department, and I told them the phone had been rooted etc. (I didn't leave any identifying details!) They informed me that as the phone was now out of warranty, I should speak to their service partner SBE.
After calling SBE, they informed me that LG or their partner have no obligation to fix rooted phones, so apparently they just won't do it, even though I'm certain they could, which kind of sucks, as I was obviously willing to pay.
So it looks like I'm waiting for the TOT files. I hope they come along soon!
Lesson well and truly learned!
Click to expand...
Click to collapse
Lets see if we can work on this.
Is it working ok, just not picking up the network?
How long exactly have you had it?
If you put what you all deleted meaning what folders they were in i could make a copy of that folder or apps you deleted and upload them on dropbox for you that might help get you going worth a shot
Be better if someone had the same variant as you i have the Sprint model.
Thanks again for input. I have hopefully managed to sort this with my provider. I was just within the 14 day cancellation period, so I have arranged for a brand new handset. I know its a little bit naughty but if the phone wasnt so laggy to begin with, I would never have rooted it.
I'm guessing it makes no difference to them as the phone will go back to lg for wipe and reflash as a matter of course once returned.
Thanks folks, I will remain on this forum and hopefully not do anything quite so stupid again!
Unfortunately this is my last day with this device . Great phone but i was wrong the 810 processor is dangerously hot to the point it felt like my pockets were on fire. This my second g flex2 and I'm moving on to something more reliable. Love this phone but this heat issue i can't risk. After 14 days i would be stuck with this phone and i can't take the risk of hoping of getting a device that function fine bye everyone.
:victory::victory::victory:
Today, I've gotten myself in a similar pickle after applying noob root.. Data OK but no phonecalls and no txts. When I tried to make a call, the thing said the phone is not activated. Sprint tech supp was of course no help, so after some digging I found this: ##72786#
Factory reset, keep the data (and all apps).
That solved it.
I guess I'm old enough to know that being lazy doesn't pay.
Stank0 said:
Today, I've gotten myself in a similar pickle after applying noob root.. Data OK but no phonecalls and no txts. When I tried to make a call, the thing said the phone is not activated. Sprint tech supp was of course no help, so after some digging I found this: ##72786#
Factory reset, keep the data (and all apps).
That solved it.
I guess I'm old enough to know that being lazy doesn't pay.
Click to expand...
Click to collapse
so you had root, and while doing this factory reset you were able to go back to full stock unrooted rom? if so, were you able to install updates? i too have a sprint version and i was rooted and tried installing an update but failed, i then unrooted my phone tried the update again and still got an error. im just wondering if this method would actually help people who have the same problem as i do.
gothikzoul said:
so you had root, and while doing this factory reset you were able to go back to full stock unrooted rom? if so, were you able to install updates? i too have a sprint version and i was rooted and tried installing an update but failed, i then unrooted my phone tried the update again and still got an error. im just wondering if this method would actually help people who have the same problem as i do.
Click to expand...
Click to collapse
Unfortunately, that wasn't the case.
I tried every possible way to install this damn update. Rooted, unrooted, factory reset 4 times, tried to install from the system update in settings, from recovery (which is, at least for me, very tricky to get into) all efforts errored out.
I posted a link to the update.zip in other thread.
So then I gave up and used this noob root which killed voice calls and text.
This code I posted says it does a factory reset but is resetting something else than other factory resets because almost all my settings, passwords and all apps remained intact.. Then I used the original root method and everything works like it's supposed to.
I guess we'll have to wait until someone finally starts developing for our phone.
So after a few days I just received a notification for the update for the third time. Any suggestions as to how I should proceed? I've tried it while being rooted and failed, also tried it the second time after unrooting and failed too. Also, what is the default location where the update is downloaded to, so I can back it up.
So far nothing has worked. The update should be in the cache folder. There is also a link to download the update that someone posted in another thread here about the update.
FYI - I forced the update through recovery over root and bricked my phone. Like all the way bricked. I can get to recovery and download mode, but no fastboot even. Luckily I was within my 14 days and there is no way to tell it is rooted... because it doesn't even get that far, so I got a replacement. My sincere advice would be to wait to root until we have custom recovery and stock firmware available, and if you have root now, wait to update until a dev can release a "root safe" version.
I'm not an expert but I'm not new either. I got the original Evo on launch day and have done all kinds of dumb stuff to every phone since. This is the first time I haven't been able to recover it.
austontatious said:
FYI - I forced the update through recovery over root and bricked my phone. Like all the way bricked. I can get to recovery and download mode, but no fastboot even. Luckily I was within my 14 days and there is no way to tell it is rooted... because it doesn't even get that far, so I got a replacement. My sincere advice would be to wait to root until we have custom recovery and stock firmware available, and if you have root now, wait to update until a dev can release a "root safe" version.
I'm not an expert but I'm not new either. I got the original Evo on launch day and have done all kinds of dumb stuff to every phone since. This is the first time I haven't been able to recover it.
Click to expand...
Click to collapse
=( *hug. That sucks man, thankfully you were able to get it replaced. *pfew I dodged a bullet there. I was actually thinking about doing the same thing getting home from work. Yeah its best we don't mess with the phone any longer those that have root at the moment. Until custom recovery and stock rom is out like he says.
Wow. How did you manage to "force" the update through recovery? I tried it through recovery but it would error out. (Error 7)
I will tell you, as a cautionary tale.
The error when you flash from recovery references a specific file that is incompatible with the update. I used root explorer to investigate further and found that the root script had overwritten a system file. The original was saved as "original" so I deleted the file causing the error and renamed the original one. After that, the update went through and I thought I was golden... Only now nothing else works.

phone locked after corrup flash

So tried to downgrade to 7.1.1 some thing went wrong got boot loop so tried to flash to pie it was working for a few days then after I turn off to charge it went to setup on restart and will not let me go past wifi and PC companion says my phone is locked what happened? On xz1 forum they say this happen some time and to reset phone but how do I do this.
So since no one could help me here and have warranty still I sent phone to sony and they said memory is corrupted due to update and will be sending me a new phone. My warranty finish in June so good this happened before that.
I'm glad knowing your problem is over, anyway if one counts with the warranty the best thing to do is not to touch or interfere the device in any way, it could precisely provoque the warranty to be void
Zur75 said:
I'm glad knowing your problem is over, anyway if one counts with the warranty the best thing to do is not to touch or interfere the device in any way, it could precisely provoque the warranty to be void
Click to expand...
Click to collapse
Yes this is why I post this to show this is a software problem not physical problem. I love the xzp and will buy another for now I'm using my z5p.

Question Fingerprint Scanner gone

Out of the blue yesterday my fingerprint scanner just stopped working. I dint pay much attention to it because i was busy and thought it was a dirty sensor. But today after cleaning it it's still not working. It seems the entire setting is missing, I can't find the fingerprint manager in Settings -> Security!
What gives!? I think this the last Sony smartphone for me. Too many silly issues .
Anyone had this issue with a 5III? and has a fix? I saw in the xperia 1 forums some ppl had the issue but no definite fix, neither rebooting nor reflashing the OS has worked.
Yeap. If you read my recently opened thread I got exactly the same problem. I sent the phone for service and not only have they created new problems (disabling updates somehow) but the fingerprint sensor failed again within a day!
Sony did almost two weeks to react to my new complaints and even though I was trying to convince them to just give me a new device and get done with it they tell me to send it again for service. A month is past overall.
P.S. I bet it is some cabling issue because I also reflashed the software when the problem appeared using the Xperia companion and no luck. Sony service changed the chipset and the button (but I assume not the cable?) And as I said it failed again. And after I got the phone back updates don't work and Xperia companion does not work. Don't they even test it??? Saying that I am pissed is an understatement.
Ahh seeing your post here, it seems more of hardware issue than software. Checking in with Sony (if it's still under Warranty) should be the best bet for both. Please do try to share your experience here on how the whole process goes. Understandable it's a pain at the moment.
Unfortunately no warranty. Got an unlocked device on amazon as its not available in my country.

Categories

Resources