Heya. Since I haven't updated phone for quite some time now (I'm still at 2.0.49), so is it safe to upload to latest version, via SE PC Companion, to still have root access, for xrecovery, flashing etc.. That's question number one.
Question number two would be - if phone, x10i keeps random restarting, mostly while browsing websites via stock browser (usually, screen just "freezes" for few seconds (6-8 at most), and phone just reboots, showing that SE boot logo). If it's software related - would update, that I mentioned above fix that, if not... Phone is still under warranty (at least I hope ).
Yes, Update definitely. That should fix your software related problems.
And I'll still be able to root it, and flash ?
yes you will still be able to root, just download latest flasher, plug your phone and root it, optimize, install xrec and many more
Related
I am facing a very annoying problem: my x10 mini(unrooted) automatically gets restarts.
Some of the days it works fine. But once it gets restarts then it restarts atleast 3-4 times a day. I have tried to reinstall the android firmware but still the problem prevails. I keep the phone memory at 21-22MB level, is the problem because of this( But I want to tell you 1 thing that I bought the phone in november and in feb end my phone was not switching on ,then I went to SE service centre they reinstalled the firmware and the problem was solved. Since then I am facing the problem of rebooting, before that it worked fine. I used to keep the phone memory around 2mb in the initial days of purchasing and it worked fine even in 2mb so I guess low phone memory is not a problem. I rooted my phone in november but when service centre employee reinstalled the firmware then I lost rooting.i.e. Now my phone is unrooted). Can the problem be because of SIM card or SD Card(corrupt files which I am aware of) or it is because of some other reason?
I dont want to go to the service centre because I feel that they will just reinstall the firmware which I already have done. It would be great if you could tell me any solution. If not the solution then a user friendly and so technical language using app which show the log of my phone so that I can figure out what happens in the system. But I really want a solution. Please guys help! Hope you guys would bring all your experience into play and help me.
Sent from my E10i using XDA App
Well ..people will need some more specific info ..like are you on the latest SE update ? what programs did u install (seems u did install quite a few as ur phone memory is ~22 MB ). Anything you noticed when it reboots ? Like while doing some operation or running something in particular when this reboot happens ?
Why dont you do a fresh flashing of the latest update through SEUS (not PC companion) and then just stick to the stock ROM (without installing anything else) for 7-10 days and see how it behaves ?
You can always take a backup of ur essentials like SMS and contacts (if you are not syncing ur contacts with google ) before you flash using SEUS.
There are ways to check the logs (using logcat ) but not sure how much effective it might be as u might not be in a position to check logs everytime when your phone reboots.
Hope this helps. Really there was very less inputs available for giving any solution.
I am having the latest android firmware. I updated the android firmware by downloading a firmware file avaible on the sony's website, I don't know what it is called but I surely didn't used pc companion for updating. There is no specific app which I am using when it restarts.
I will give any necessary info which will help you to suggest a solution.
Sent from my E10i using XDA App
you cannot just download a firmware from SE site ..it can be done only by two ways one via PC companion and the other by SE Update service. (SEUS)
And yes , it would be better to reflash through SEUS . It does seem that you have installed lots of things ..better forget them now and just use the stock ROM from SE.
i have just got an xperia s, and unlocked the bootloader through sony's site today. i then flashed the pre-rooted firmware, the correct one for my model, and am stuck in a bootloop. I have had android phones before, and always been able to get out of messes like this, but sony's system seems to be somewhat different from my previous Moto. can anyone tell me how to possibly fix this? many thanks
Flash another firmware with flashtools.
Sent from my LT26i using Tapatalk 2
thanks, currently downloading the 73 version to test. I have an issue with flashtools though, and fastboot in general on my PC, the drivers do not seem to have installed, as when i try fastboot i get blue led for aprox. 5 seconds, then reboot into the bootloop. fastboot works fine on my mac though
Must install them manually. You open the device manager, right clicking on the S1boot, update drivers. Then shows you which folder is the drivers. and voila.
thanks, ive got it to boot again, and tried various roms, but keep having the same wierd issues. first, everytime i boot i have to go through the xperia setup completely from scratch again, as if the phone is brand new.
secondly, im using doomkernel v4a, and have installed the wifi modules as specified, but turning on wifi causes an instant crash and then reboot, sometimes immediately, sometimes after a short freeze
thirdly, somehow 'phone memory' is completely full, whatever i do. Internal memory, when the phone is completely empty, only shows as 25gb, but phone memory is totaly full, regardless of weather i clear app data/cache etc
any help would be greatly appreciated XD
hello,
you must flash doomkernel v1 or v1a , then after modules wifi for v1, before flashing v4a ,
(sorry for my bad english)
Hello,
recently I downloaded a Glamour S4 and installed it. Also I downloaded, what is propably obvious, CWM. I used it for some time, but didn't like bacause of many bugs and limitations. I tried to download other rom, Project Chaos, but what is driving me crazy I couldn't download it from mega.co.nz becauze it freezes all the time on 66 or 90%. So after two days of trying to download and having this issue I decided to go back to original. I did everything as in this thread http://forum.xda-developers.com/showthread.php?t=2323847 but after finishing I realized that the software is branded by one of operators here in Poland, and it was freezing too long (about 30 minutes and samsung logo stayed still).
Fortunetly I had my backup from CWM. So what I did then was:
Installed CWM
backed up software
Installed original recovery
Set binary counter to default
Then I figured that root is still on my phone, so I choosed option in SU to fully unroot
Voila! Soft is smooth and as it was orginally. Status is original. Everything as it was before I changed any software, except one thing - I cannot check if there is a new update. I have internet connection, can access websites through wifi or mobile data etc., but when I check if there is new software, phone only shows "checking if there is new software" and progress bar, and it stays for 5, 10, 30... 60 minutes even, and nothing is happening...
It is annoying cause I wanted to back to fully original and wait for the official update, but right now something is wrong... Do anyone know, why?
Cheers!
Adam.st said:
Hello,
recently I downloaded a Glamour S4 and installed it. Also I downloaded, what is propably obvious, CWM. I used it for some time, but didn't like bacause of many bugs and limitations. I tried to download other rom, Project Chaos, but what is driving me crazy I couldn't download it from mega.co.nz becauze it freezes all the time on 66 or 90%. So after two days of trying to download and having this issue I decided to go back to original. I did everything as in this thread http://forum.xda-developers.com/showthread.php?t=2323847 but after finishing I realized that the software is branded by one of operators here in Poland, and it was freezing too long (about 30 minutes and samsung logo stayed still).
Fortunetly I had my backup from CWM. So what I did then was:
Installed CWM
backed up software
Installed original recovery
Set binary counter to default
Then I figured that root is still on my phone, so I choosed option in SU to fully unroot
Voila! Soft is smooth and as it was orginally. Status is original. Everything as it was before I changed any software, except one thing - I cannot check if there is a new update. I have internet connection, can access websites through wifi or mobile data etc., but when I check if there is new software, phone only shows "checking if there is new software" and progress bar, and it stays for 5, 10, 30... 60 minutes even, and nothing is happening...
It is annoying cause I wanted to back to fully original and wait for the official update, but right now something is wrong... Do anyone know, why?
Cheers!
Click to expand...
Click to collapse
You will need to flash a stock ROM with odin use: SAMSUNG GALAXY S3 UNIFIED TOOLKIT
Dear Experts,
Months ago my 2y old XZU on 4.4.4 (6833, towel rooted, locked, CWM recovery) started to fail on init of LCD, when coming out of standby. LCD init not only fails when device gets waked up by "power" button, but also when power is applied (Dock connector or USB). So I guess in fact it is a firmware issue (not a defective power button or the like).
It gets worse and worse; when device is warm it sometimes needs 30 or more off/on cycles.
When LCD init fails, the screen either stays black (only backlight) or colored lines show up shortly and fade away. But in fact the device is running - only LCD is not working.
But when init is successful, the XZU can run nicely for hours (as navi).
I hope that a android FW update might help!?
Unfortunately OTA doesn't seem to work on routed devices even with still locked boot loader.
Is there a way to update directly to 5.1.1 available now? Is it possible to update in two steps?
I would not mind to loose root, but loosing the possibility to write to external SDCARD!
Any help/ideas? THANKS A LOT!
Thomas
Sounds like SOD, or Sleep Of Death. The Ultra had some issues with it back on Jelly Bean, but I hardly read about it being an issue on KitKat, but yeah, it's probably a software issue, so an update to 5.1.1 might just cure it. You have a couple of options here:
1. Update the official way by installing Sony's PC Companion app on your computer and updating it that way
2. Update it in a little less official way by updating it manually yourself with Flashtool on your computer
3. Update by flashing a customized version through a recovery system on your device (like CWM or TWRP)
I would personally update it through PC Companion if I were you, since I guess you're not that technical when it comes to flashing and troubleshooting things. PC Companion should notify you about the update as soon as you plug your Ultra to your computer. If it notifies you about the 5.0.2 update, then I guess you'll have to update to 5.0.2 first, and then you'll be able to update to 5.1.
Flashtool allows you to manually download a FTF, or the ROM file from XDA and then flash it yourself. It's a lot quicker than PC Companion, but also a lot more complicated for people who haven't used it before.
Flashing through a recovery is mainly for people who already are used to flashing and stuff like that, and know what they're (mostly) doing.
Any other questions?
Thanks for your very valuable hints!!!
I'm really curious if it will work with PC comp (vs. OTA) and if I will loose write access to SDRAM (introduced in Android 4.4 and regained by root and SDFix).
Currently the download is running..
Will post results
zamzon said:
Thanks for your very valuable hints!!!
I'm really curious if it will work with PC comp (vs. OTA) and if I will loose write access to SDRAM (introduced in Android 4.4 and regained by root and SDFix).
Currently the download is running..
Will post results
Click to expand...
Click to collapse
The OTA will only tell you to connect to the computer to update. And regarding SD-card, that won't be an issue. Android will ask you to grant permission to the SD-card in some cases, but I haven't had any issues with it. Most if not all file explorers works just fine, and you won't experience any issues with the SD-card.
The update worked (no error on PC), but device seemed dead afterwads
After a reset and numerous power off/on cycles, the LCD init worked and I could see the result. :laugh:
Root was gone, of course. Recovery system and write access to SDCARD, too. Therefore Sygic app (navi), which had been moved to ext. SDCard. could not run anymore and moved itself to .android again.
But worst of all: the init of LCD now works even more seldom!
It does not even work when device has been shut down before, cooled down and is then switched on.
As far as I read, the SOD is different, cause my device in fact is "awake". It runs fine - only LCD is not working and not displaying anything.
I have no idea how to fix this. I can not imagine any hardware defect, causing such behavior (and I designed embeded systems with gfx controllers, myself).
Thomas
zamzon said:
The update worked (no error on PC), but device seemed dead afterwads
After a reset and numerous power off/on cycles, the LCD init worked and I could see the result. :laugh:
Root was gone, of course. Recovery system and write access to SDCARD, too. Therefore Sygic app (navi), which had been moved to ext. SDCard. could not run anymore and moved itself to .android again.
But worst of all: the init of LCD now works even more seldom!
It does not even work when device has been shut down before, cooled down and is then switched on.
As far as I read, the SOD is different, cause my device in fact is "awake". It runs fine - only LCD is not working and not displaying anything.
I have no idea how to fix this. I can not imagine any hardware defect, causing such behavior (and I designed embeded systems with gfx controllers, myself).
Thomas
Click to expand...
Click to collapse
But that does sound like a hardware issue. The final thing you can do, before you'll have to send it in for repairs, or get a new device, is to do a full factory resetting and see if that finally helps. You just updated now, but there's still a lot of crap left over from the previous version, that might screw things up.
So my advice would be to do a wipe, check if it help, and if not either send it in for repairs or get a new device. It's not a software issue if the issue travels over several OS versions with you. It may be a faulty display connector.
Hi!
I received J8110 from Sony as a service exchange unit (they could not repair my other model). It came originally with Android 9 1317-9334_55.0.A.2.205 GLOBAL-A1. I have not unlocked it.
It never got any OTA update for this over 2 years old firmware, so I decided to flash it myself using flashtool. As I could not find exactly matching 1317-9334 on XperiCheck, I used 1318-3803 Android 10 "Internal Service Exchange Unit 55.1.A.9.127-R1B" firmware. It did flash correctly, and almost everything works - except both Netflix and HBO Max reboot the phone whenever I try to play any video. Moreover, the phone reboots itself randomly once a few hours, and I must say it is really irritating issue.
The last entries in Android logcat just before reboot look like this:
Code:
03-07 10:18:41.251 886 17948 D WVCdm : [license.cpp(355):PrepareKeyRequest] PrepareKeyRequest: nonce=3174971344
03-07 10:18:41.313 886 6842 I WVCdm : [cdm_engine.cpp(191):CloseSession] CdmEngine::CloseSession: sid10
I suspect it might be somehow related to Widevine keys. But the DRM info app shows everything is OK and L1 support is enabled (as in the attached screenshot).
I tried to flash also other firmware images - everything available for J8110 in XperiCheck (including 55.2.A.4.332), but the phone won't boot - "Your device is corrupt. It can't be trusted and will not boot.". I even tried flashing J8170, but that eneded up even worse, in recovery: "cannot load Android system". This 55.1.A.9.127-R1B (that reboots my phone on Netflix) is the only firmware I was able to boot.
My first question: is there any way to downgrade to this original, obsolete but working Android 9 1317-9334_55.0.A.2.205 GLOBAL-A1? I can't find it in XperiFirm.
And, of course - if you could point me on how to install the more recent Android versions that work I would be very grateful. I would prefer to leave the phone locked as I suspect some DRM issues with unlocking, but if that is the only way and it is confirmed working I can try it as well.
Service menu *#*#7378423#*#* "software info" of original and updated firmware attached.
Thanks for any help!
I forgot to mention that of course I tried clearing data and cache for Netflix app, as well as uninstalling and re-installing updates (can't fully uninstall the app as it was included in the firmware). I could fully reinstall HBO though, but fresh install did not help with the issue at all.
Did you tried the Firmware with version 205 on XperiFirm?
There is one called SA or ZA.
Get things into your PC and use newflasher by @munjeni. It will work if there is nothing wrong with hardware.
Thanks for the response.
I have tried the newflasher as well, but the results are exactly the same as for flashtool - "Your device is corrupt..." (or recovery error, depending on firmware). I don't think this is an issue with flashing itself, I did not notice any error in logs.
Yes, I have tried this 205 "Customized ZA" also - it does not boot, stops in recovery "Can't load Android system". I did not try to factory reset the data yet, as I really would prefer to keep my user data intact.
I have tried every single firmware available in XperiCheck for J8110, and only this 1318-3803 boots for me - but reboots my phone every hour or so and this is really annoying.
I have also asked XperiCheck maintainer to add my 1317-9334, but no response so far.
Plz provide the frimware that is working in your mobile i am facing the same problem my device stuck on sony logo i will be thankful to you brother