I am using a Docomo SO-04J (Sony XZ Premium) as my primary device. Not rooted. Locked Bootloader. I didn't do anything. But suddenly it started to bootloop. (Sony Logo cames, then Restarts)
First I flashed the firmware using flashtool. Tried two versions.
But even after the flash, still phone bootloops.
Then tried newflasher method. Same. Then tried to repair the phone using Xperia Companion. I completes without an error. But Same! Keeps bootlooping.
Any idea, why is that happening? I used correct firmware. No any errors during the flashing process. Can it be related to hardware fault?
This can occur if the battery is deteriorating.
Related
Hi !
I just got my new phone : Xperia ARC !
And you know what ? I Bootlooped it by mistake
The problem is I don't really know I did wrong and why every solution I found doesn't fix my problem.
Okay, now I tell you my story :
I received my phone and use it few hours.
I rooted it with GingerBreak and start to really use it, installing apps...
I removed some useless apps (I think I removed something important ) but everything was good.
And later I rebooted my phone. And tadaaam ! "Sony Ericsson" logo forever, bootlooped !
I tried :
- FastBoot technique, but my phone was blocked by my operator, impossible to use the menu button when I plug my phone.
- FlashTools with 2 different firmwares, the flashing works (no error in logs) but I'm still in the loop !! I used LT15i_3.0.A.2.181 Global Customized and the UK 184.
- Tried again on Win7 and WinXP 64 et 32 bits...
- I prayed all the night.
Nothing fixed my phone...
I don't know what to anymore... I need you !
Thanks.
EDIT : BTW I didn't tell you but I tried with SE Tools to fix it, and nothing change
I tried se tools to fix my arc but I left my phone for a hour after the flash wouldnt work and flashed the firmware again cause that is why my phone would work the first time so anyway tried it after an hour and I left it a good 20 mins and Sony Ericsson logo came on then took another 20 mins for it to load up properly try my way and see if it works for u
Sent from my LT15i using XDA Premium App
You will may need to flash the correct firmware for your phone/ operator..
Where is the phone from? which operator did you buy it from?
I bought it in France, operator : VirginMobile.
I had the same and just recovered the firmware by SEUS (Sony Ericcson Update Service). This program can be downloaded from the internet. Just follow instructions and you have a fresh phone again. Really fresh as you have to setup everything from the beginning but at least your phone works again.
I already tried using SEUS without success, nothing changed
How many Firmware exists ?
How do I know which one was mine ?
How many Firmware exists ?
How do I know which one was mine ?
just try the uk generic one..
Sent from The Arc!
I just did it again. The bootloop is still there.
Hi all!
I am writing some instructions for newbies like me that wish to root their Xperia Tablet Z. I spent a lot of hours trying to understand how things work and I try to fill this gap with this post. If anybody knows, I would like to have an answer on the DRM, and model type questions that I have colored red in the text.
I was a "proud" owner of Sony Xperia Tablet Z WIFI 32GB (SGP312) that I bought from northern Europe last September. It was my first Android device and I consider myself super newbie on this "sport". Since my last official Sony system upgrade ~1-2 months ago I had sound problems with skype. I could not make a call without a handset and also my sony speakers refused to reproduce any youtube video. Nonetheless, the alarm was working fine! I was disappointed and after a factory reset the sound problems persisted. Thus, I decided to delve into the rooting world.
So long story short, we can install whichever stock/original firmware we want if it is designed for our devices consulting the precious links in xda-developers.com forums. Then we can either stay with this or install custom "ROMs" having our tablet "rooted".
My first goal is to fix the sound problem so I tried following the stock firmware route.
I flashed the firmware(s) with the quite intuitive Flashtool. Beware that I had already installed the required Google's Android SDK/ADT kit in my windows machine, although I performed every task in my linux machine in order to have working fastboot and adb commands with the minimal fuss installation-wise. To flash the stock firmwares, or the so called FTF files, I was entering the flash mode holding/pressing down the Volume Down key while connecting the device with the USB to my PC. I note that holding down the Volume Up key, instead, connects the tablet in the fast boot mode
After/Before every firmware flashing I was trying not to forget to:
Enable the USB Debugging mode
Trust installation from unknown sources (this probably is redundant) and
Use massive storage instead of MTP in my USB connection options.
Then, I tried to unlock my bootloader (for experimenting purposes) following the official SONY instructions. I successfully did (fastboot was saying OK!), without keeping any DRM keys, since I guess I do not need them, right? However with some FTF stock firmwares my screen was freezing while booting and showing the "flying colors" and then it was eternally rebooting again and freezing again and so on. I tried this and verified it with a couple of FTF stock firmwares. The one was for sure the SGP312 Global Xperia Tablet Z WiFi 32 GB - 10.4.1.B.0.109, I do not remember the others. This 10.4.1.B.0.109 was working fine but not with the bootloader unlocked. I found out that I could break the boot/freeze loop by entering flash mode (Volume Down while connecting the USB) just after it was turned off after the "flying color" freeze.
So I tried with this stock firmware: SGP312 10.4.B.0.577 (UK version 32GB WIFI Unbranded) and after using my tablet for ~30mins I can say that I did not encounter any problems.
But I wanted to view the rooting world, so to do this I found out that installing a Recovery Software would help.
So I installed XZDualRecovery. I followed the instructions and downloaded TabZ-lockeddualrecovery2.7.123-BETA.installer.zip and also the *flashable.zip from the same site.
Before starting to implement the instructions, the same XZDualRecovery post was mentioning I should install a 10.3.1.C.0.136 firmware and so I did, getting the SGP312 10.3.1.C.0.136 VMo EU4 firmware. This 10.3.1.C.0.136 was also working quite well, and after unlocking the bootloader (I do not know if I have to do unlock the bootloader everytime I flash a stock FTF) it was botting properly and my speakers were working fine.
I runned the install.sh for linux (install.bat for windows). I noticed that the third option was "3/ Attempt installation on unrooted device" which I tried and was successful, since then, the "Root Checker" app was saying that my tablet was rooted. That was really cool!
I wanted to enter the recovery mode so I turned on my tablet and when the "SONY" letters appeared (or a bit earlier) I started pressing multiple times the Volume Up key and a nice purple screen (like this) with the recovery appeared. There, I chose Wipe Data/Factory Reset (it was quite fast) and then Install multiple Zip files from the SD card.
The Zips I had in my card were the Cyanogen Mod, the Google Apps and the XZDualRecovery:
I downloaded Cyanogen Mod, pollux_windy for our devices, from here. I chose the latest stable version, cm-10.2.1-pollux_windy.zip 2014-02-01 01:07:05, but I hope another one will see the light soon.
I also installed the latest google apps that for today are these and the latest versions can be found here.
The TabZ-lockeddualrecovery2.7.123-BETA.flashable.zip metnioned above. I am not sure if this is really needed but I think I read somewhere that I should included or else I would not be able to Reboot to Recovery after flashing.
The problem with the pollux_windy zip was that I panicked since the recovery zip installation stopped with the error: assert failed [...] status 7 and I was pretty sure I had an SGP312 device!!! So I deleted the first line in the cyanogen zip file:
Code:
/META-INF/com/google/android/updater-script
like it appears here or here. This forum post says I should not extract the zip, but I did and it worked.
After all the above steps I booted my tablet and everything seems almost ok so far. I say almost because:
I notice that my device, according to the settings is now the "SGP311" and not the SGP312 (how could I change that?), but in my free space I still see 25+GB (although I am still using only ~3GB).
Also, some times while I am scrolling e.g. in Play Store I see infinitesimal freezes in the movement of the webpage (AnTuTu benchmark returns a rating of ~19800-20118).
Moreover, I have installed ~30 apps, but the installing procedure seems somehow slow, and the last ~10 apps I tried to install have not been installed "due to an error 495". The above was "fixed" after a reboot, but I must say I never encountered this problem with my stock firmware.
To the first question in red: DRM keys are needed for Playstation Mobile, Video and Music Unlimited, I think something regarding Screen Mirroring and, until Android 4.3, no Bravia Engine 2. With 4.4, it works again.
About the 311 and 312 thing, it is because you flashed a firmware that wasn't specifically for your device. You can go into build.prop file, and change every SGP311 you find to SGP312.
Nevertheless, awesome guide
Sent from my LT26i using Tapatalk
Thanks for the time to share
Hi all,
I have the SGP312 but it's not the "global" version (I noticed one of the stock firmware used was the UK one). I have the US/Canadian/North American version.
Would I brick my device if I flashed with the UK firmware? I haven't for the life of me found any guides/threads for my device.
I know it's the "pollux windy" (wifi 32gb) but I'm...afraid.
Thanks!
UberBaumer said:
Would I brick my device if I flashed with the UK firmware? I haven't for the life of me found any guides/threads for my device.
Click to expand...
Click to collapse
no.
Hey,
I tried to flash a stock rom to my Sony Xperia Z Tablet (32GB) - SPG312. The bootloader is unlocked and LineageOS was running on it.
After flashing the following file SGP312_10.7.A.0.228_1273-3719_R2E.ftf that was created by XperiFirm the Tablet does not boot anymore.
When I start the Tablet I see the Sony screen and the display becomes black. Connected to a windows system it is detected as Ericsson Mobile SPG312.
In flashmode it is detected as Ericsson Mobile S1 Service.
How can I get my Xperia Z Tablet working back to stock?
Thank you for your help!
Same Problem here with SGP311
But no solution yet?
No, very strange!
I often roll backk to stock or flashed customs without Problems.
Only these days Stock 5.1.1. Firmware only blank screen after Logo Init.
Have locked bootloader too, but nothing. Whats Wrong. Using flashtool.
Sony's Xperia Companion only reports error when start repair Mode.
It's a well known issue https://forum.xda-developers.com/xperia-tablet-z/help/flash-stock-rom-t3564623.
Rootk1t said:
It's a well known issue https://forum.xda-developers.com/xperia-tablet-z/help/flash-stock-rom-t3564623.
Click to expand...
Click to collapse
Thanks a lot. The Thread helped me to solve my problem!
Hello, recently I tried to flash my phone in flashtool and always stuck at "reading device information", even xperia companion can't detect it !
I re-installed all drivers, tried old versions of flashtool and firmware but always the same problem.
My phone is rooted but I don't know about bootloader. Any help? suggestions?
Thanks
You should probably ask moderators to deleted this since it's already under help section as well.
Edit: I worked out my issues, I'll leave this here in case others have similar trouble:
I needed to manually add in the RAW F53XX files from the github (https://github.com/Androxyde/devices/tree/master/F53XX), this allowed Flashtool to correctly detect the type of phone and apply the fsc. I was then able to flash my desired firmware, I chose the 6.0.1 release for Journalists to begin with as a test. This confirmed my suspicion that it was a software update issue causing the proximity sensor to malfunction (stuck on) and also fixed up the FACTORY STARTUP SERVICE-POWER OFF bug and the Warrantytimeservice permanent notification. I can now look at updating to later versions of Android and find the latest version before I have issues again.
---
tl;dr - I need a guide that actually works on downgrading the F5321 to a specific stock Android version with a locked bootloader.
I recently received a new, old stock version of the X Compact (F5321) that appears to be a HK variant as it started up with the Chinese language selected.
It was initially stock Android 6.0.1 with no apparent problems. After OTA updating all the way through to 7.1.x and onward to the latest 8.0, I now receive the "FACTORY STARTUP SERVICE" problem. Even if I'm quick enough to disable the service for the service flag, the proximity sensor does not work as well after updating, making phone calls impossible. I believe the issue is all related to software, not hardware. I want to downgrade to 6.x and go from there before I have to send it back for another replacement.
I'm having trouble with getting Flashtool to correctly detect and identify the firmware files that I want to flash. I want a completely stock version of Android, so keeping the bootloader locked is fine for me.
After downloading the firmware that I want to try, XperiFirm will close and Flashtool will successfully build the FTF. After clicking the lightning bolt > flashmode > the firmware list is blank.
I'm using Flashtool 0.9.26 (I have tried older versions as well with the same problems) with driver signature enforcement disabled and correct drivers installed to detect the phone.
The last time I used Flashtool was to flash my older Z5 Compact, I didn't have any issues then and it was all done within 10 minutes. I've already spent more than 5 hours on this phone and would appreciate any help.
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
pseudonym58 said:
I seem to have the exact same problem with a Hong Kong-sourced X Compact. I am familiar with Flashtool, and have used it for basic flashing of firmware. This time, however, I am experiencing the dreaded "FACTORY STARTUP SERVICE" problem. Was wondering if Flashtool could be used to circumvent the problem. I simply want the USA Android 8.0 firmware on the phone. I am not familiar with the various options that Flashtool offers. I note that you mention a specific script(?) that can be installed. Do you have any advice? Thanks
Click to expand...
Click to collapse
The "FACTORY STARTUP SERVICE" and to a lesser extent, "Warrantytimeservice" problems surface only in the later version of Android. The only way I could remove them was by staying on 6.0.x only. Anything higher, and the problems show up again. It seems to be a byproduct of upgrading the HK variant that wasn't designed to actually be software upgraded - you won't be able to have the US 8.x firmware on the phone.
Sorry to say, but you'll be stuck on 6.0.x if you want a usable phone. I should mention that I was never able to maintain a newer firmware on that particular phone.
I've since sent the Compact X back (it was meant to be a gift) and replaced it with a Samsung A20.
h
I'm using SO-O2J and a sim card not docomo. Use the "Repair" in Xperia Companion and it auto flash Android 7.0
..
PioneerSeeker said:
Try different region's roms on www.xperiablog.net and I hope you'll be successful to find nougat or oreo at last for your phone.
Remember xperia devices do not need to unlock bootloader for downgrade...
Click to expand...
Click to collapse
Thanks; I was able to obtain an X Compact originally for the UK market, and was able to successfully flash the US Oreo firmware. All seems to be in order.