The new update does not work on my phone tryed reflahing from start and nothing.
2.3.3 software radio works but sim locked.
apply patch nothing happens
How did you update? If you had an unlocked bootloader and updated through Sony you've bricked your phone.
i flashed play from the x10 flash tool...now i get only a grey screen...what to do now...
Related
Hi XDA,
i'm experiencing a not very cool no-update
I just go to the check OS update screen on my G2 and I can see a "Android Update 1.5" (4.2Mb)
I push the download button, it DL well and ... I can't install it ! The Download button is here again with the "Android Update 1.5" (Reboot required but the reboot actually does nothing)
I root my G2, but don't know if it's the reason of this
The very not cool part is that my version is CRB17 ... So the update isn't done !
Please help me, Donut is coming !
Is this a new update released today?
No it's an old one ...
No one had this problem before ?
Hard reset doesn't resolve the problem, stills stuck on displaying "Android Update 1.5" 4.2Mb, the phone doesn't ask me to install after I download it
Update Problem
I have this exact same problem on my rooted UK Voda Magic. No solution but one question. How do you know the update has not been applied you referred to the CRB17 number, my build number is exactly the same but the firmware version reads as 1.5. What is the latest build number????
The FW is firmed with releasekeys and if you flashed a custom recovery it won't accept it.
Cant Update
Any way around this particular problem? Does this also mean when donut is released we will be unable to update through the "update feature" on the phone?
So nobody has any suggestions, is there another recovery version which we could flash that would allow updates? Or maybe un root update and re root? I am assuming this problem will prevent me from updating to 1.6 when it is released.
After spending the last two evenings and most of Saturday trying to flash and root my phone I somehow managed to get it caught in a loop that I couldn't get to stop. Over and over it was flashing the green SE logo and a purplish space looking design.
In flash mood I updated the phone through the SEUS and when I rebooted it I ended up with version 2.1 update1 and build #2.0A.0.504.
I'm in the U.S. with an AT&T x10a. While it still shows X10a as the model number all the AT&T branding and bloatware is gone.
Any thoughts on exactly what I did would be appreciated. Thanks.
Are you able to boot up and use the device or is it still stuck in the boot screen loop?
If it is, open SEUS on your PC and try to update the phone. It will most likely state you have the latest software. Next choose install anyway and this will download and re-install the firmware and your device should be repaired.
No, the phone is working perfectly. Curious as to why it would let me do that with an AT&T branded phone?? It wiped all the AT&T stuff off.
Hi guys, First of all HAPPY CANADA DAY!
I have a rogers branded Sony Ericsson phone with original firmware. But I have removed some bloatwares from Rogers and Golf game.
My phone have been noticing me about 2.3.3 firmware update. The phone itself also downloads, installs it. But after that process, the phone starts like normal and says "Couldn't update" message.
I tried resetting phone and tried many methods. Now the phone also doesn't display "Connect to Phone memory" in Notification area (it charges, but apparently doesn't connect to PC) :/
What's wrong?
You probably modified some of the system files in a way. Anything like removing bloatware with Titanium Backup will cause the update to fail. If you want to root your phone, you'll need to re-flash the Rogers 2.3.2 ROM back, root it with GingerBreak, and then perform the update to 2.3.3.
If you don't want to root, just use FlashTool to flash the Rogers 2.3.3 ROM.
Yeah, that's what I thought. Where can I find 2.3.2 Rogers ROM and how can I re-flash the platform? (the phone doesn't show connected to PC as well).
Do a search. There's a thread in the android development forum with the rogers 2.3.2 rom. I just flashed that one back yesterday to update to 2.3.3
Hello,
I have a problem with my phone.
I rooted it so I could flash a ROM with Marshmallow on it.
I now have ALE--L21C432B574 on it with TWRP. (my phone is single SIM hardware but I installed the double SIM firmware, so far it worked well)
With the recent "****" announced by Niantic, i didn't know if I had to stop playing Pokemon Go, or if I should unroot. After some reflexion, I determined that I don't use root that much, so I decided to unroot directly from SuperSU to uninstall the root.
Except the phone is still detected as rooted, It doesn't pass SafetyNet API so I can't play Pokemon Go.
I did a factory reset but from the beginning of configuration it told me my phone was rooted. I don't understand what to do. Do I have to flash the stock recovery of the C432B574 update and lock the bootloader so it stops detecting root on my phone ?
Or do I have to get it back to the original state with my branded rom (which I can't find...) ?
How can I completely remove root so the game would work ?
Thanks in advance for any helpful response I can get.
Hello! I have just upgraded to Android M and I have two quick questions: 1 is , is it a problem if my system did not have any problems updating , even though I am S-OFF and my boot-loader is unlocked, this system being installed from a zip? 2 is, I do not have the brightness bar in the notification area, and that is a feature I used to use a lot, yet it isn't there, and I can't find it anywhere in settings. Please help on the second one and tell me if this is supposed to happen or not, also BTW in the boot loader it says System status: official, but it is S-OFF and the boot loader is unlocked.
1-Did you unlock the bootloader or it was unlocked when you got the phone? maybe you have the developer edition phone.
2-I think this option is not available for the M9+ you need to use an app like Brightness slider control or any other app from google play
Reply
About your first question: I was the one who unlocked the boot loader because I had the clean slate ROM installed and just reverted to stock, yet the stock ROM was a very old version and because it was S-OFF and the boot loader was unlocked I feared that I might not get the marshmallow update, yet I decided to try and install the update anyways, and to my surprise it worked flawlessly. Is this normal lol