I have owned my xperia x compact since June 2017, the first thing I did with it when I bought it was flash the UK firmware and root it. The phone has operated with out any real issues since then, but today I woke up to my phone on the charger showing a back lit black screen. It was unresponsive to any inputs so I rebooted it (power button, up volume), and it would just load to the xperia splash screen freeze then reboot ad nauseam. I am tempted to use the xperia companion to attempt a software repair but I am afriad if I do I'll get updated to oreo and not have a working camera. I did back up my keys when I rooted my phone but I did not change to the bootloader from factory.
Any input as to how I should proceed would be greatly apprechiated
Thank you
Do you have twrp? Do you have a twrp backup? If so, just boot to twrp, try factory reset, and if it boots after that, just restore your backup. If you don't have a backup, and you don't want to lose data, it's hard to know what to do, especially since you don't seem to have a clue what caused it. You can try to flash an ftf with Flashtool, excluding everything except 'system', (and making sure to check nothing in 'wipe' box'. Other possibilities, if you have recovery, is to try uninstalling things like Xposed, Magisk, Substratum, etc...
Thanks for the input, as stated I never changed the boot loader so unfortunately I do not have twrp and thus no images to restore.
I would like to preserve my data if possible but biggest concern is losing the camera. From what I gather using the Xperia companion will update my phone to Oreo likely loosing my ability to root but also locking out the camera. I have a back up of my DRM keys but if I am not on the factory marshmallow rom I don't think I'll be able to restore them. So is there a way to restore the phone to original factory marshmallow firmware?
Marshmallow ftf / Flashtool. I'm sure you can find one out there. Also, you can upgrade to O and your camera will be fine. Drm keys just make it a little better. And you can root with Rootkernel, and use your ta backup to mount onto Rootkernel, so camera will be just like stock. See here - https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
Thanks for your help I really appreciate it. If I can have camera and root functionality on Oreo then I might as well upgrade.
Its been awhile since I've messed with this, and I am on a different computer. Hopefully I can get this phone up and running and out of this boot loop.
Also looking at your guide the modded boot images offered are older than the firmware currently offered on xperiafirm, do I need to find the specific firmware offered in your guide instead of the one offered on xperiafirm?
It's pretty easy to do once you're set up, but I'll see if I can post an updated one tonight.
Thanks, I do not recall having much issue getting the device unlocked and rooted with the guides here on XDA. Then again the phone was fully bootable at that time so once plugged in, windows and the xperia companion took care of the drivers. I am in the process of familiarizing myself with all the ancillary bits which may not be explicitly detailed. I suspect I will need to put adb and fastboot on this new PC, was going to use snoop05 15 second installer but all his links are dead.
Related
I just bought a Z3CT(SGP612) and am a bit confused.
The first big question is about DRM key thing. Why do I care about them if I don't have any other Sony devices (Playstation etc.) and probably won't ever. I read in one thread that these keys may be non-recoverable, but in another thread it was said they could be saved and restored. What are the best practices for doing this?
Second, and I'm stuck here until this thread works, or further research surfaces the answer. I just bought this unit, it's brand new out of box. I'm probably the last man on earth to buy one, but....The device is nagging me to update, but I think that may end in tears. I'm afraid Sony official updates may render the device unrootable, or permanently lock the bootloader forcing me to beg Sony to do whatever I want to my own device. I think on 4.4.4 there is a way to unlock the bootloader without begging Sony to do it. The device is presently 4.4.4, build 23.0.1.A.0.167. The nagging update will take me to 23.0.1.A.3.12. I'm assuming there may be further updates beyond that to get to 23.4.xxxx. Should I accept this, and do any other updates, or proceed directly to one of the pre-rooted stock ftf files (sorry, what is ftf and acronym for?). I'd like to get to the latest 5.11 and have the ability to run adaway, make backups, have proper working SD card and USB OTG, and maybe run a few Xposed apps all of which mean I need root. As it's a virgin device I don't care about if I have to wipe the device in the process.
http://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
http://xperiafirmware.com/8-firmware/77-sony-xperia-z3-tablet-compact
as i´m in the same situation as you i will share my experience / research so far:
1. Rooting works on different firmware with different methods, kingroot being one rather easy but with the drawback of sending personal phone data to uncertain chinese servers. Rooting 4.4 seems easier than 5.x.
2. Research showed that the DRM keys / TA partition is something to be backed up, just in case. But for backing up you need root but no unlocked bootloader (unlocking erases the keys).
3. Recoveries can be installed without unlocking the bootloader but need root(?).
This is where im right now with my progress - rooted, TA/DRM keys backed up and on a custom recovery but bootloader still locked and TA intact .. getting root demanded some patience and several tries though.
4. next step will be installing a prerooted 5.1 firmware i guess and everything has to be running fine
I have an Xperia Z5 Compact with German T-Mobile factory ROM, which is not too much use to me coz I don't live in Germany or use T-Mobile. I wanted to flash a stock ROM with no bloatware. Root probably later, I'd like to use the phone a bit first. It isn't simlocked btw, and was OTA updated to Marshmallow before I tried anything.
So I unlocked the bootloader, then flashed the recovery and boot images from the first post here without noticing they are old versions and further down the thread they are updated. Now I can get into TWRP recovery, but when I try to start the phone normally it freezes on the pink T-Mobile splash screen. Recovering from my Nandroid backup doesn't help... coz I only created it from within TWRP after I did this flash.
I can't use Flashtool, it says USB debugging is turned off. I guess what I flashed before has reset that to off. I tried following the Lollipop instructions here to turn it back on using adb, but I can't pull the file mentioned there. Anyone got instructions for doing the same on Marshmallow please?
Not exactly panicking here, but I really wish I practiced on my old HTC Hero before jumping in blind....
moyabrit said:
I have an Xperia Z5 Compact with German T-Mobile factory ROM, which is not too much use to me coz I don't live in Germany or use T-Mobile. I wanted to flash a stock ROM with no bloatware. Root probably later, I'd like to use the phone a bit first. It isn't simlocked btw, and was OTA updated to Marshmallow before I tried anything.
So I unlocked the bootloader, then flashed the recovery and boot images from the first post here without noticing they are old versions and further down the thread they are updated. Now I can get into TWRP recovery, but when I try to start the phone normally it freezes on the pink T-Mobile splash screen. Recovering from my Nandroid backup doesn't help... coz I only created it from within TWRP after I did this flash.
I can't use Flashtool, it says USB debugging is turned off. I guess what I flashed before has reset that to off. I tried following the Lollipop instructions here to turn it back on using adb, but I can't pull the file mentioned there. Anyone got instructions for doing the same on Marshmallow please?
Not exactly panicking here, but I really wish I practiced on my old HTC Hero before jumping in blind....
Click to expand...
Click to collapse
use adb and flash androkernel to fix the incorrect kernel that you installed. you can do that by renaming it boot.img and sending the command fastboot flash boot boot.img
i haven't messed with androplus in a while but if you were on marshmallow i believe v34 will work and if you were on the absolute newest marshmallow i think its v35 off the top of my head.
fyi you dont need usb debugging on to use flashtool, you can get into fastboot mode with no rom at all installed.
I recently managed to snag one of these up at a local walmart recently (well, 2 actually) - So I would share my experience with the software aspects I have dealt with so far.
Upon opening the box, I removed the NanoSIM (before even powering it up) and gave the device a full charge - no setup yet or anything.
I then went through the initial setup, skipping everything - not signing into Wi-Fi, or added my google account. The system was on B130 or B140, I can't recall now. I enabled developer settings, enable usb debug and checked OEM Unlock (for bootloader). I then connected it to my PC (I already had the proper drivers installed, and Minimal ADB and Fastboot) and proceeded to unlock the bootloader via the official code from Huawei. This of course gives you the warning that the phone is not secure, every time you power up the phone from fully off (or restart)
Now that the bootloader was successfully unlocked, I installed TWRP from the thread "[TWRP]Unofficial[5/21/2017]huawei ascend xt" by madvane20 using Fastboot. This was perfectly successful. Upon first load of TWRP I swiped to allow modifications.
Once in TWRP I copied the B180_Full_Update.zip from "[Guide]Huawei Ascend XT - How to update from any version up to B180 after rooting" by clsA - to a 4GB MicroSD Card that I put in the phone. I mounted system and cust, as it instructs in the thread - then proceeded to do a factory reset, format data from within TWRP (I might have done an advanced wipe too, and checked everything but the external SD, but I can't quite recall) and then did a reboot directly back to recovery.
I then proceeded to make sure that system and cust was mounted again, and installed the B180_Full_Update.zip - wiping dalvik/cache after. Then I did a standard reboot system, but the phone failed to boot. It just stopped at the unsecure warning, where you can press power (or wait) to boot anyhow. It would respond to me pressing power, but not go past that part. I was slightly concerned at this point, but lucky for me a long press of the power button and holding volume up - took me back to TWRP. So all was not lost.
I then decided to fully wipe everything again - following the previous steps I mentioned - and this time install the SR2-SuperSU-v2.79-SR2-20170103215521.zip from the thread "AT&T Huawei Ascend XT H1611 Feb27, 2017 update all things Root and TWRP (guide)" By powerserge1 . This was installed immediately after the Rom zip. Then I wiped dalvik/cache and reboot. This time the phone did boot as described (AT&T logo and a few automatic reboots, before actually getting to the setup screen) - I was then on B180 with SuperSU installed. Unfortunately, wifi was not working!
So at that point I decided to flash the boot.img (inside the boot.zip) at the bottom of the first post on the thread "[Rom][11thMay]Ascend XT - Swift&Fast Slim B160/b170/b180 aio" By madvane20. I did this with my PC via Fastboot. At this point the Wi-Fi was fixed. Unfortunately while SuperSU was installed ( and I ended up updating it via Play Store) - Root was not working (tried root checker from the play store), and the SuperSU program was not actually functioning properly. But other than that the phone seemed fully functional, and up to date.
I should state now that I bought this phone just to use it as a cheap tablet (Wi-Fi only), I do not have AT&T Service - and did not try and unlock it. So I cannot speak to how it performs as an actual cellphone - Service quality, service features etc.
Of course, I felt a little uneasy about the phone working fine - but not correctly rooted. I don't really need root for my uses, but it's what got it actually booting in the first place, so I figure I may as well know it is working. So here's my last step...
I just simply reflashed the B180_Full_Update.zip in TWRP. Mounted everything, full wipe of everything and rebooted back to recovery - before flashing of course. I did not reflash SuperSU or mess around with the boot.img etc. Just a davlik/cache wipe before rebooting the system. This time the system booted fine (AT&T logo and a couple resets, like before) and wifi was working right off the bat. I was at B180 still (obviously), and no signs of root or SuperSU. This is fine by me.
SO after all of that, it seems I am on a stock (unrooted, all bloat) B180 version (from B130 or B140, no other versions in between). Updated fully via unlocked bootloader, and various software. I have not tried to root again, because I don't need it. I just do the basic debloating that android natively allows, disabling all the AT&T stuff and various built in apps I wont use.
Hopefully this will be some help to anyone following the same path that I have, or currently in any of the hangups I was in.
Also, for anyone trying to replace the Huawei Home Launcher with something like Nova Launcher (recommended) - be sure to go to Settings/apps/Huawei Home/Open by default then clear defaults. This will allow you to select a new default launcher.
Feel free to ask any questions, and I will help as best as I can!
Good outline! It's not all too hard to get going, most of the hassle is tweaking EMUI.
As far as your problem with supersu... Supersu, and magisk as well, work by patching the boot img - so when you flashed the default boot files, you uninstalled the part of supersu that does the work (though not the management utility that provides its interface). Also take care not to clear cache/dalvik immediately after installing magisk or supersu, as their installers often use it as a workaround to inject their system files. My advice: flas osm0sis's unSu script (forum/google search), reboot, reboot into twrp, reflash default boot img, clear cache/dalvik, flash supersu, and then reboot (can reboot back into twrp to wipe cache/dalvik again if you want, just verify supersu is working first).
Edit: use the most recent flashable version of supersu from its thread - installs aren't device-specific
Thanks for reading, and for the insightful reply - that does shed some light on things for sure.
I'm still not really interested in rooting the device, but if I decide that I need to - that should sort me out. I just have to make sure I reinstall SuperSU from TWRP, if I flash that stock (I'm guessing) boot image..
My main problem was that I wanted to get it the phone up to the latest software version, and I don't have an active AT&T SIM. Well, actually now that I think about it maybe I could have just used the gophone sim that was installed in the phone... hah! I am no stranger to flashing ROMS/Recoveries etc. so I didn't mind having to go manual to get the phone up to date. This phone is blessed in that you are able to unlock the bootloader - just sucks that I had to, just to get it on a later version of official software. I like keeping my devices stock, as much a possible - provided it meets my needs in that form. Obviously if It is what it takes to make a device usable, or bring it up from a software update abandoned state - I will use Custom ROMs, and ROOT features where needed. I try not to even waste my time with devices like that though, unless it is acquired for very cheap or free. There are just so many other choices out there, and the used market is very good to me.
I guess the thing that escaped me while doing research to start on this phone, was how best to get to the latest stock B180 software version - altering as little as possible to get there. The only direct solution that I found assumed (or required) that you were also rooted, and I didn't think about that in the right way. I just assumed that it wouldn't matter that I was not, and that a bigger problem might be that I was jumping a few software versions. I'll admit I kinda skimmed over that part that said "Also some roms may need to have SuperSU flashed after the Rom or the phone may not boot the first time after the upgrade." I just figured I didn't need root, so I didn't have to worry flashing Super SU. It makes sense now, due in no small part to your explanation!
I wonder if (starting at stock bootloader unlocked B140) I could have just flashed that B180 full update zip from TWRP, and then PC fastboot flashed that boot image - forgo flashing superSU in TWRP - and then be good to go (Wi-Fi Working as well)? Assuming I was not interested in being rooted of course. I'm guessing not, and I'm not sure why.
As a follow up... I started working on the other phone I bought - brand new, on B140 Software Version.
Unlocked bootloader > flashed TWRP > full wipe/format everything > flashed B180 zip > and fastboot flashed boot image - presto change-o! Stock B180 with wifi working fine (no root, as desired). Still have the unlocked bootloader message upon power on, but that's unavoidable. This is pretty much the most direct method for manually updating to the latest software version.
I also used DC-Unlocker Successfully on both phones for about $4 USD each.
The Sony Xperia Z2 tablet has got to be the most horrible device in android history to root or install a recovery on it. The process and the complexity of it is just horrible. You daren't ever make the slightest change to a rom or anything in twrp as it just screws everything up on this device. I can't count the amount of roms i've put on it just to totally trash the device and you have to start from scratch. Either you put a new rom on, it wipes the recovery, you have to piss about using flashtool to flash some other ftf on just to get into recovery, then you have to then flash another tft to get root, the list just goes on and on. I don't even know why sony mobile even bother offering the bootloader unlock option in the first place, it's an absolute nightmare. It's basically you can have root with the official stock firmware, if you want a custom rom spend the next 2 weeks trying to get supersu installed on it. The most horrible device I've ever come across.
Then sell it :laugh:
Somehow I cannot share this view. Running Carbon ROM with Magisk without any issues. For a more than 4 years old tablet the Z2 stands its ground, I don't regret having bought it.
Just hoping that we'll get Pie...
BabelHuber said:
Then sell it :laugh:
Somehow I cannot share this view. Running Carbon ROM with Magisk without any issues. For a more than 4 years old tablet the Z2 stands its ground, I don't regret having bought it.
Just hoping that we'll get Pie...
Click to expand...
Click to collapse
I've tried Carbon and would love to use it but it just screws up the tablet after install and recovery gets wiped so you can't even go back to restore a back up. You then have to reflash using Emma then back into flashtool to reflash the tft to get recovery to work again because flashtool ends up reporting back that the current tft is not compatible with the device. It's a finicky device to root. It's got to be the worst out of all android devices. E.g my Samsung s9 had it rooted and flashed with a custom rom in around 5 mins. No matter what firmware is installed. Sony decided that after 23.1.A.575 or whatever rooting was not possible after that. Also every method on here telling you how to do it is different to each other and inconsistant. I tried 23.1.A.575 root for UK and it would not allow for twrp to be booted into. I had to use xperiafirm to download the Taiwanese version so I could get the batch script to allow recovery so holding down power on volume down would allow twrp to load. It's just a painstakingly horrible device to root to get something so simple. But yes your right probably best time to get rid and something different. Sorry for the rant it's just been a frustration for me.
Sorry to say so, but rcstar has a very good step by step description on how to install the ROM. I followed it to the point and have no issues whatsoever.
TWRP, Magisk and Substratum work, like everything else.
It's not a device which is easy to mess with, you are right. But it's doable.
BabelHuber said:
Sorry to say so, but rcstar has a very good step by step description on how to install the ROM. I followed it to the point and have no issues whatsoever.
TWRP, Magisk and Substratum work, like everything else.
It's not a device which is easy to mess with, you are right. But it's doable.
Click to expand...
Click to collapse
I've followed so many without much success. I tried the solution by kulvertti to the letter and the tab was having non of it. I think the problem also is that a lot of the links are dead to the specific tft you need to download so getting the exact version is tricky. The only one that has worked for me is the Taiwanese rom then using the recovery script by danalec to get Marshmallow flashed which is what I'm running now. So I made a back up today and thought OK let me try carbon because I can get all the nice customization options like being able to choose a dark theme for the settings menu instead of piercing white. What is it with manufacturers wanna make every thing bright and painful on the eyes. Anyway downloaded gaps wiped system etc installed rom and once it loaded the system was all unstable and lost root and recovery. So I give up now and have to accept I can only have marshmallow on it.
Danalec has a very simple root method for Marshmallow in the general section. This is one of the best tablets out there by far. Build quality doesn't come close with other brands.
Hey everyone,
So! I bought a Sony Xperia 1 (J8110-2019) phone from someone on Facebook Marketplace at a very solid price of £250 (RRP is still £850 in the UK) due to the seller describing it as 'in retail demo mode' so they lowered the price. I jumped the gun thinking I was getting a solid deal and just stupidly assumed it to be a feature I could just disable with *#*#73556673*#*#- me believing I was some insane developer with mad coding skills where in realityI had once flashed and rooted my Xperia XZ back in 2016. [Insert 'Hackerman' meme]
Yes... I am fully aware I'm a complete idiot for not doing a full assessment on the phone and am now having to learn a very important lesson from this situation!!
It seems to have a Store Front firmware installed and unsure what firmware to download and flash? I've tried some of the official stock ROMs from XperiFirm and it just continues to boot into constant 10-second cycles of demo videos making general functionality like phone calls pretty much impossible. without interruption. I've tried Customized and UK Service Provider Firmware such as EE and O2 but it always goes back into Store mode.
I was hoping if anyone would have or could elaborate on how to make an executable system flash zip for a 2019 Xperia 1? When I extract files from XperiaFirm ROMS (FTF,ZIP,SIN etc), I don't seem to get any META-INF files and thus cant make the proper .zip that TWRP needs to successfully flash a new repacked stock ROM? It always ends in a boot loop."
Here are some key points to hopefully give you some background:
I've installed TWRP successfully and have attempted to use 3 official firmware to flash whilst in recovery but have been unsuccessful each time with 'Invalid .ZIP format'. I've only a few times got booted whilst bundling together FTF files via Flashtool and doing it that way round but only ever seems to solve half the problem
I can't use the SinExtract feature in Flashtools as the SIN file errors as not being supported yet to use different file versions.
I can't use PRFCreator as it errors as the FTF file being unsupported (Due to it being new I assume)
I attempted to create my own META-INF>Updater-script but am unable to identify what partition my phone would use for mounting on "/dev/block". I only ever seem to get MANIFEST.MF from the files and nothing else. On my XZ I think I used something like:
(package_extract_file("boot.img", "/dev/block/mmcblk0");
package_extract_file("system.sin","/dev/block/platform/msm_sdcc.1/by-name/system");
Click to expand...
Click to collapse
I have been able to install Magisk for rooting and verified.
I have used Minimal ADB and Fastboot to install programs like TWRP, SuperSu, Magisk but have never attempted, nor would I even know how to wipe my phone completely and install a clean stock ROM - is this possible?
All drivers, software, and systems are correct and up to date (as far as I am aware)
Would installing the' Service Exchange Firmware' be recommended (if I ever make it that far!) due to it being StoreFront?
I checked the IMEI number to see if it was blacklisted/blocked and it's all good. Not lost or stolen.
Thank you for your time to read and wallow in my woes with me my lovelies! Any help would be GREATLY appreciated you magnificent beasts! x
Bump x
...
the last chance... :good: