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:
Related
Hello,
As the title suggests, I'm looking for a way to completely backup my stock device without root.
This would include firmware and stock recoveries, basically system files - as I'm not really too terribly worried with saving personal data.
I've searched through various threads but I think I'm in one of those "in-over-my-head" situations, so let me explain why I haven't just flashed a custom recovery and made a nandroid backup.
My device is the C-Spire Note 5, SM-N920R7, running 5.1.1 - recognized by Smart Switch with no updates available.
I received this device in the mail today - because I somehow managed to brick my old device with the "custom binary blocked" FRP.
There is no stock firmware available for download to flash in Odin, and it was impossible to boot the device in regular or recovery mode, leaving me with Download mode.
In order to root my old device, I had to unlock the OEM in Developer Settings and flash the "Beastmode" kernel via Odin:
http://forum.xda-developers.com/spr...rnel-beastmode-modified-stock-1-0-sm-t3196174
Then, I flashed a TWRP recovery and used it to install SuperSU - and voila! I had rooted my device.
Fast forward a few months... My battery died one day and it somehow triggered the FRP lock - with only Download mode available and no C-Spire stock firmware to flash.
Naturally, I want to root my device again, but first I want to create a complete backup of my device that would be flashable in Odin even with the FRP lock on.
So ladies and gentlemen, any help or advice would be appreciated.
I would of course, upload my firmware publicly so that anyone else using this device doesn't brick their phone like I did.
Did you ever get an answer to this? I'm in the same boat and want to do the same thing.
theophile2 said:
Did you ever get an answer to this? I'm in the same boat and want to do the same thing.
Click to expand...
Click to collapse
The only way I've seen involves capturing temporary files during an update through Kies or Smart Switch.
Being on C-Spire, that probably will not ever happen.
Maybe C-Spire will get it together and push out 6.0.1 OTA like the rest of the world - as well as actually providing an alternate (non-OTA) download method.
Apparently some guy on the C-Spire Dev forums paid for a ROM on a Chinese site that works with our phones - which would serve as a nice backup if he would ever upload it.
I asked him to - and apparently he contacted the admins asking for a way to upload the file to the forums.
After they responded to him, he must have never uploaded the file.
My Xperia Neo had Android 4.0.4 (kernel 4.1.B.0.587), has a locked bootloader and is rumored to be rooted. With the Xperia Flashtool I had the Kernel MT11i_4.1.A.0.562_Kernel.ftf (4.651 kB) flashed (then also MT15I_4.1.A.0.562_Kernel.ftf), Logs s. Appendix !! (There must be something wrong here, although no error is shown!), Then to routed with DooMLoRD and start the script runme.bat.
Several things do not run as described:
1.) After the flashing and start-up are now missing lots of app icons on the desktop. (I did not give any Wipe !!)
2.) The phone app and contacts now plunge consistently. Mobile phone currently not usable.
3.) Although the Flash seemed to succeed, changed under Telefoninfos nothing: same Android and Kernel version, as well as build number. Why not? (The attackable Kernel 4.0.3 is nevertheless still on it?)
4.) I start runme.bat, has changed purely GARNICHTS. Just as before, no write access is allowed and, among other things, Reported: "can not open for write: read-only file system". What a crap !!
5.) Under Settings is missing now menu point 'Xperia' !! For example, No longer change between MTP and MSC !! ...
After 6 hours of trial I give it up now frustrated and turn to you. On the net I find NOTHING about my case.
Who can tell me what I am doing wrong here?
Who would be able to look at the attached Flashtool-Log?
Many many thanks.
PS: After flashing again the previous kernel is at least everything again okay, just how do I roote now only? ...
Hello again,
Hmmh, many is now obviously too late and the mobile phone too 'outdated', to report here yet !? No more interested !?
I would however be very grateful, especially since the Neo and the Ray, in addition to the unfortunately unfortunately (not cheaply) available, for Japan-made SX model of Sony the only, really small mobile phones with good display resolution AND a lot of good camera.
I hold little of the in my opinion now much too big mobile phones! Does not anyone have good eyes here or do not surf on the road all the time? ...
And with CM11 (up to CM13 if necessary) you have a much up-to-date and fast Custom Rome, which also takes the small memory into account. So it's worth it! ...
Although I've got a little bit of help now, thanks to the Chinese root program Eroot, but I've reached a partial rooting after all the methods you've described (Xperia-Flashtool, Tweak-Installer, Eroot, ...) With this tool with me not possible, among other things In the system directory.
Please, why is there such a big discrepancy between what you write here in XDev and what works with me?
It has changed in the 4 years here but not at all!? ...
Now, e.g. Link2SD and I now have a CWM recovery on it, but I can still flash a custom rom, because for example. When playing the LX kernel ( 'fastboot flash boot boot.img') I still get the write permission denied.
Please, please help me!
This can not be that everyone thinks, that is very simplistic and here is simply nothing of it!? ...
I am currently not really aware of any error.
Thank you very much.
Yes, unfortunately, no one helped me.
Nevertheless, I have now solved the problem after much testing and time investment.
Here is the solution(s) for subsequent fans of the few small non-beginners smartphones:
There really should be a lot of people who had the same problem because these were the (many) reasons for my problems...
1.) An incomplete DooMLoRD file called 'DooMLoRD_v1_Xperia-2011-ICS-ROOT-emu-busybox-su.zip' was published in XDA, missing the crucial file 'zergRush'!
2.) It is simply a rumor that, as almost everywhere described, only one (older) kernel has to be replaced / replaced for rooting. It must be flashed the complete firmware!
3.) It is simply FALSE that the (older) Android version 4.1.A.0.562 (4.0.3) already contains the vulnerable kernel for rooting and is therefore sufficient to, in particular, the system access rights from RO to R / W to change. Instead, it may not be newer than v2.3.4 (older than kernel version 4.0.2.A.0.62)!
4.) The tool 'Extrem Tweak-Installer' does not suffice if the root is present, in order to unlock the bootloader (enough). While the CWM recovery is installed as expected, e.g. You can not flash a boot image (irritating error message, that root is not available!) Instead you get an official unlocking via the Sony site (specification of the IMEI) by fastboot command with unlock code!
5.) To flash many ftf images you need the older version 9.14.0 of the Xperia Flashtool. The current v9.22.3 expected very accurate ftf device specifications, which are often not fulfilled and therefore the ftf file is not recognized / indicated by the tool.
6.) The chinese tool ERoot does not seem to be sufficient to allow a complete root access, even if su and busybox are installed. E.g. Tweak-Installer still did not get write access
Only with root and unlocked boot loader can up-to-date Custom Roms like LegacyXperia or AOKP be flashed...
By the way, if someone knows how I can get the great Xperia SX smartphone from Sony, please let me know!
This has a 2-core processor and much more memory with the same size, camera and display resolution! ...
Thank you very much.
First off, hello everyone!
I've been reading the Forums for the past couple 3 days amounting to something around 9 hours total and finally signed up to ask some stuff!
I am, not a big surprise, completely new to everything related flashing, rooting and so on but thanks to this place I learned in 3 hours probably more than in a whole week back then in comp-sci classes at my university, thanks for that!
I have an old Xperia Z2 (D6503) to play with which, if bricked, wouldn't be a huge loss so I used it as my play and test ground... well what do you know, after about 3 hours of playing around I finally managed to (at least I think) kill the bootloader...
After another couple hours I fixed various problems (like actually fixing the bootloader and other errors like "failed do mount /system" ) on my own (thanks to guides), however I am now kinda "stuck".
The thing is, at current state, after a full wipe, my phone has, obviously, no OS, so I am trying to flash an original Firmware on it.
At first I googled a couple different .ftf's and tried them, only to be greeted with the "could not find META-INF/com/google/android/update-binary", a quick search told me that those are "update" .ftf which don't contain a complete ROM.
Alright, I keep searching for more .ftf files but no matter what, not a single one of them has said folder inside the META-INF when I check the contents of the zip, so I decide to use the Flashtool to download the newest available Firmware for my device, surely that will net me a fully working ROM.
For that I am using Flashtool 0.9.23.1, I successfully downloaded the newest official Firmware through XperiFirm but as soon as I select all files (except the handfull .ta files) and hit "create", the entire thing just freezes on me, leaving me without a .ftf file to flash on my phone so it has a proper OS again.
While the reason for the freeze might as well go as deep as a ****ty AMD VGA driver, is there a different way to create/obtain a FULL ROM? While it is fun and all experimenting, I am kind of losing hope and motivation after 3 days of no success...
Hope someone can help me out and thanks in advance!
EDIT: WELL, what do you know, I finally found an actual ROM (albeit a prerooted one) and was able to flash it properly, problem solved! I will maybe enhance this post as a kind of "guide" for future idiots like me who need a special case of handholding to not destroy their own device... but as always, learning by doing
Gibgub said:
First off, hello everyone!
I've been reading the Forums for the past couple 3 days amounting to something around 9 hours total and finally signed up to ask some stuff!
I am, not a big surprise, completely new to everything related flashing, rooting and so on but thanks to this place I learned in 3 hours probably more than in a whole week back then in comp-sci classes at my university, thanks for that!
I have an old Xperia Z2 (D6503) to play with which, if bricked, wouldn't be a huge loss so I used it as my play and test ground... well what do you know, after about 3 hours of playing around I finally managed to (at least I think) kill the bootloader...
After another couple hours I fixed various problems (like actually fixing the bootloader and other errors like "failed do mount /system" ) on my own (thanks to guides), however I am now kinda "stuck".
The thing is, at current state, after a full wipe, my phone has, obviously, no OS, so I am trying to flash an original Firmware on it.
At first I googled a couple different .ftf's and tried them, only to be greeted with the "could not find META-INF/com/google/android/update-binary", a quick search told me that those are "update" .ftf which don't contain a complete ROM.
Alright, I keep searching for more .ftf files but no matter what, not a single one of them has said folder inside the META-INF when I check the contents of the zip, so I decide to use the Flashtool to download the newest available Firmware for my device, surely that will net me a fully working ROM.
For that I am using Flashtool 0.9.23.1, I successfully downloaded the newest official Firmware through XperiFirm but as soon as I select all files (except the handfull .ta files) and hit "create", the entire thing just freezes on me, leaving me without a .ftf file to flash on my phone so it has a proper OS again.
While the reason for the freeze might as well go as deep as a ****ty AMD VGA driver, is there a different way to create/obtain a FULL ROM? While it is fun and all experimenting, I am kind of losing hope and motivation after 3 days of no success...
Hope someone can help me out and thanks in advance!
Click to expand...
Click to collapse
There is no need to create an ftf file your self just download an ftf file and flash it using flashtools
Thats it now you have working phone again
And another thing is that you cannot flash ftf files using recovery
raminta said:
There is no need to create an ftf file your self just download an ftf file and flash it using flashtools
Thats it now you have working phone again
Click to expand...
Click to collapse
I know, the thing is, that I couldn't find a simple ftf file that was a COMPLETE ROM and not just an update but as I wrote in my first post after editing it, I finally found one (after about 2 hours of spamming google)
raminta said:
And another thing is that you cannot flash ftf files using recovery
Click to expand...
Click to collapse
Obviously, I was trying with zips the entire time, which didn't contain the needed META-INF stuff
Hey everyone,
I hope i'm not being a pain in the toot for asking this, but I have the above issue. I've been trying for the past several weeks to resolve it but no luck.
I've unlocked my boot loader (worst decision ever) and installed a custom recovery; TWRP in that case. After some time I decided to go back to the official firmware. I already knew about Sony's flash tool which I tried but for some weird reason the flash tool (emma) doesn't recognise the f5122 model just the single sim variant f5121.
I've also tried to download the firmware manually using xperifirm which for some idiotic reason never worked (connection keeps getting messed up and the download fails)
I've managed to get my hands on the .tft file for nougat firmware and once I started the flash tool (developed independently by some awesome guy) it would also fail. Something about needing to enable debugging over usb (which is duh enabled) and enabling Unknown Sources (also duh enabled)
Any idea if there's something else that I didn't try/paid attention to?
P.S i'm currently running the Poison rom (found it here on xda) which works well but I've read that I won't receive any OTA updates.
Thanking you all in advance :fingers-crossed:
-=-=- first, Did you backup DRM before unlock bootloader ?
second, You can flash any x firmware with flashtool on flashmode ( search to find how to turn it on).
third, xperia firm can download well on day time, i think so because i live in vietnam and it only work between 8am to 4pm after that the connection lost.
1. No i didn't backup this thing (didn't know why I needed to)
2. I tried flash tool on windows and mac but without success, maybe I need to load a firmware downloaded with xperifirm in order to make it work
3. I'll keep trying with the xperifirm thingy
Any ideas if there's something that I missed?
1. Sometime Sony release some new Firmware and you need that backup to restore DRM key for full function of sony like xreal...
2. you miss flash scipt ( I guest) so to make it more clearly please give me the image when you flash stock rom
See that there is not ftfs fo X or X Dual on XDA. Strange.
If You cannot download it through XperiFirm, try my upload for my polish forum:
http://www.xperiasite.pl/forum/341-xperia-x/
I'm trying to add every firmware - one unbranded (usually one of the firsts which get) and for all polish carriers - for every Sony device.
There are GDrive and MEGA links, so choose which suits You better.
Excellent news people (at least for me )
I've managed to get stock firmware from xperifirm
Flashed the bastard and locked the bootloader!
Thank you all for your kind support )
Hello everyone.
This is my first post here - in hope to get help with my Sony Z5 Compact.
So a week ago I have updated to Nougat,by mistake tbh.
Unfortunately Im really not happy with the device. The volume is OK unless youd like to watch some videos on a website - you won't hear much.
Then, playing a matroska file is impossible - stutters, pauses, gives you 5 fps ( I'm not joking) - it was flawless on MM (305).
So my plan is to go back to MM and I believe I've read every step by step tutorial existing on the Internet but I still have some questions.
1. How do I backup firmware? Every tutorial says about a folder with firmware files that you can import to flashtool to make an ftf backup of your stock firmware. The folder does not exist on my PC.
I've tried "repairing" etc, still, it does not exist.
2. Why do I need a backup firmware ftf for warranty?
3. Where can I find an ftf file?
Xperifirm doesn't give me anything, there are lots of fake websites, xperiablog doesn't send me an approval email for my account.
4. Is there anyone in Lodz, Poland that could help me?
I'd love to downgrade.. The phone is unusable for my work and I can't afford a new one.
Thanks in advance.
Kindest regards.
Michelangelo
Suggest you download Customized SG firmware, the lastest marshmellow is still available for download. Grab it now.
Hello, welcome to xda.
First, please do not open 2 different threads for the same problem - it's against forum rules.
About your problem: which fw you are on? you could try newest nougat firmware .33 first because the problems you described should've been fixed in this. Also you could dirty flash it and won't lose anything.
However if you want to go back to MM anyway, i would recommend 5.11 fw because it's .305 with newer security patch.
Be aware, that if you go back to MM, you will have to make a clean flash.
You can find all 3 firmwares on xperifirm from different regions(also .305). For most regions there are two different available, so click through all firmwares and look on the right side which you can choose.
What do you mean xperifirm gave you nothing?
How to download via xperifirm, create a ftf and flash viaflashtool: https://forum.xda-developers.com/z5...-33-pushed-t3581352/post71662820#post71662820
yup every update sony become worse
the best one was the last 5.1.1 i think (or one b4)
the last 6MM was meh
the last nougat (.33) is far worse from all of them
probably i won't buy sony's anymore
( i was happy with my WT19 sony ericsson arc like(Legacy Xperia) the one of the reasons i bought this sony(also easy roms flash,you just need use flash tool for stock roms you dont even need root or BTunlocked)
anyway i'm usually replace my phone every 5 years in average (when the phone stop run smooth mid-low range .like waze, temple run 2,subway surfer. apps (z5 still mid-high)
so the phones got about 4 more years, at least how i see it.
As Gewiz suggested, if you're on .376 or .378 version of the Nougat firmware, then updating to 2.33 might just fix the problems you're describing.
This is the highly recommended solution, since you won't lose any of your data or settings, and you don't really have to do anything, just wait for the update to become available for your region via OTA or Xperia Companion.
If you insist on downgrading back to MM, then you must perform a clean flash using unofficial (non-Sony) tools, which means you will lose all of your data and settings. Therefore you should backup all your data before doing so.
Being on anything but the latest version means you will forever have a non-dismissible notification nagging you about upgrading to the newest version.
If you're fine with that, then download a MM ROM from XperiFirm, create a FTF from the bundle, then flash it to your phone using Flashtool.
I think you're confused by the numerous tutorials you've read about "backups" and "warranty". You've likely read guides teaching you how to root your phone, which involves making a backup of the TA partition of your phone to preserve the DRM keys that resides within. Rooting the Z5C requires unlocking the bootloader, a process that wipes the DRM keys and voids your warranty. So, guides are there to help people make a backup of the DRM keys, so that they will have the ability to restore the keys to the phone and return the phone to warranty-eligible state when they need warranty service or resell their phone.
Since you have made no mention of rooting your phone, I assume none of this matters to you, don't worry about it.
Thank you all for the replies.
I updated from 376 to 2.33 and the phone is even more pathetic. It's slow and sluggish even with stamina mode off and data transfer/WiFi off. The battery drain is even bigger, now the alarm volume is terrible ( although video volume in chrome browser is now better). Mind you, I always do a reset after updating the phone, so everything that could be done was done.
I'm after 305 since the 5.11 introduced heating an worse performance ( I don't believe it was just a security patch).
I've managed to download 305 firmware with Xperifirm but I've hit one obstacle - I cannot create an FTF file with flashtool as the Xperifirm download unpacks the " FILE" files to many separate files and folders after download.
Could anyone please tell me how should I go about it? I'm really desperate to downgrade this phone as it was perfect until the cursed update and I can afford a new one.
Thanks in advance, and again thanks for all the replies.
MichelangeloJan said:
Thank you all for the replies.
I cannot create an FTF file with flashtool as the Xperifirm download unpacks the " FILE" files to many separate files and folders after download.
Click to expand...
Click to collapse
First: for nougat (7.0) you need flashtool in version v0.9.23.2
version 0.9.23.1 _cannot_ create ftfs out of what you downloaded with xperifirm
Second: here's a tutorial for FTFs:
http://www.xperiablog.net/2014/08/1...re-files-using-xperifirm-and-flashtool-guide/
Please note: in flashtool, you just have to click "Bundles\Create" (you don't need to decrypt, as this is done by xperifirm already)
Ok, guys I have one last question regarding this topic. Im sorry this took me so long but I don't have the Internet connection at home.
The "how to create an FTF file" tutorial says " exclude . Ta files" although the screen from it show only 2 files being excluded.
Some other tutorials either say the same or don't mention the .ta files.
So should I exclude all of them? Or should I leave "simlock. Ta" and "booter" in there?
Thanks again.
Michelangelo
Reflash firmware or make a factory reset. I am on .33 Nougat and rooted. Don't have any issues. Only have Greenify and battery life is good, performance is very good.
I also have flashed Zach's kernel, it makes a difference. However, these issues you have are not from this. Some people have reported such issues when upgrading from MM. If you don't want to unlock bootloader and root, make a factory reset or flash a whole .33 FTF in Flashtool. Also no, I haven't had these issues on .376 either.
I hope one of my tips helps you
---------- Post added at 01:15 AM ---------- Previous post was at 01:12 AM ----------
MichelangeloJan said:
Ok, guys I have one last question regarding this topic. Im sorry this took me so long but I don't have the Internet connection at home.
The "how to create an FTF file" tutorial says " exclude . Ta files" although the screen from it show only 2 files being excluded.
Some other tutorials either say the same or don't mention the .ta files.
So should I exclude all of them? Or should I leave "simlock. Ta" and "booter" in there?
Thanks again.
Michelangelo
Click to expand...
Click to collapse
Don't exclude anything, leave it as is
If you ask me, make a backup of all the stuff of your Internal Storage and wipe Userdata as well (unlocking the bootloader also does this, if you decide to do so).