Related
Hello XDA!
I've ran into some hardware related issues with my Z1 compact (the earphone jack is glitchy) and i want to send my phone in for repairs.
The thing is i have a modded cyanogenmod firmware on it as i preferred it over the stock rom. I also have that clockword mod thing.
As you can tell i'm not very accostumed to doing these things and i was wondering if anyone would guide me on how to restore the phone to its original stock setting?
The phone is a swedish device so i would need the scandinavian versions i'm guessing, any ideas out there?
Thanks.
jeriksson said:
Hello XDA!
I've ran into some hardware related issues with my Z1 compact (the earphone jack is glitchy) and i want to send my phone in for repairs.
The thing is i have a modded cyanogenmod firmware on it as i preferred it over the stock rom. I also have that clockword mod thing.
As you can tell i'm not very accostumed to doing these things and i was wondering if anyone would guide me on how to restore the phone to its original stock setting?
The phone is a swedish device so i would need the scandinavian versions i'm guessing, any ideas out there?
Thanks.
Click to expand...
Click to collapse
You just need to find the right firmware for your region / provider.
I would recommend IaguCool's thread on Xperia Firmware Downloader & Checker, if you have flashtool installed you can make your own ftf that is exactly right for your phone. All the instructions are in the thread.
Hopefully you made a copy of your TA partition before you unlocked it and put CM on your phone? it may not matter if you have not, as long as it looks stock.
Didgesteve said:
You just need to find the right firmware for your region / provider.
I would recommend IaguCool's thread on Xperia Firmware Downloader & Checker, if you have flashtool installed you can make your own ftf that is exactly right for your phone. All the instructions are in the thread.
Hopefully you made a copy of your TA partition before you unlocked it and put CM on your phone? it may not matter if you have not, as long as it looks stock.
Click to expand...
Click to collapse
Hey digesteve,
Thanks, i'll check that tool out. I don't know if i made any backups of my TA partition, but probably no because i don't know about it.
Is there a way to see if i made a backup of the TA partition, could it be stored somewhere on the phone after installing clockwork mod?
Thanks for the help!
jeriksson said:
Hey digesteve,
Thanks, i'll check that tool out. I don't know if i made any backups of my TA partition, but probably no because i don't know about it.
Is there a way to see if i made a backup of the TA partition, could it be stored somewhere on the phone after installing clockwork mod?
Thanks for the help!
Click to expand...
Click to collapse
If you didn't do it, then it won't be saved anywhere on the phone. You have to physically copy it to the hard drive of your pc for safekeeping.
It doesn't matter, it won't stop you from restoring the stock rom and I don't think not having it voids the warranty. Maybe somebody could correct me on that?
Didgesteve said:
If you didn't do it, then it won't be saved anywhere on the phone. You have to physically copy it to the hard drive of your pc for safekeeping.
It doesn't matter, it won't stop you from restoring the stock rom and I don't think not having it voids the warranty. Maybe somebody could correct me on that?
Click to expand...
Click to collapse
Definitely didn't do it then. Hopefully they won't give me any trouble for rooting it, it's worth a shot anyway.
I've downloaded the firmware but it doesn't come in the same sort of package as cyanogenmod, are there any guides you can recommend on how to apply this firmware to the phone?
and don´t forget to relock the bootloader with flashtool!
jeriksson said:
are there any guides you can recommend on how to apply this firmware to the phone?
Click to expand...
Click to collapse
You'll need a copy of flashtool and the adb drivers.
Flashtool will turn the downloaded files into a tft file, but all the instructions are in the thread.
If you get lost then XperienceD's AIO thread will guide you in the right direction
I downloaded flashtool from sonys website and it actually listed stock firmwares in a list which i could apply to my phone so i did.
Now the phone boots into what seems to the be stock firmware, however i was going to go into recovery just to check that was restored too and not the clockworkmod i had previously installed but it seems i cannot boot to recovery anymore, what can i do? Where can i find the "stock recovery" that these phones comes with? I want the phone to seem as it was never rooted/changed on the software level
jeriksson said:
I downloaded flashtool from sonys website and it actually listed stock firmwares in a list which i could apply to my phone so i did.
Now the phone boots into what seems to the be stock firmware, however i was going to go into recovery just to check that was restored too and not the clockworkmod i had previously installed but it seems i cannot boot to recovery anymore, what can i do? Where can i find the "stock recovery" that these phones comes with? I want the phone to seem as it was never rooted/changed on the software level
Click to expand...
Click to collapse
You have flashed the Sony rom, so now it is stock, with no root or recovery. There isn't a stock recovery. Your work is done.
Isn't there a menu you can boot to that gives you the option to wipe cache partition and do some various other stuff? Perhaps this is only for samsung devices, sorry for the confusion and thanks for the help!
Hopefully the service goes as planned!
Is still the way to do it or is there any new ways ?? I have bought a Z1 Compact for my son who is 8 and he wants it back to stock. It has CyanogenMod now.....cant recall what version though since i dont have the phone with me.
Im thinking of buying a Z5P and while i have searched a lot, i just cant seem to find the answer to a question i have maybe someone here can help. On Sonys developer website there is instructions on how to unlock the bootloader and the last line of the instructions are as follows, note the part in blue text.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.[/B]
My question is how/where do i buy a Z5P that will definitely be Bootloader unlock allowed yes, surely its not just a case of random devices are unlockable is it? I was going to buy this from carphone its sim free so im expecting to be allowed to unlock the bootloader but dont want to buy it only to find i cant.
http://www.carphonewarehouse.com/phones/sony-xperia-z5-premium/handset?colourCode=BLACK
If the phone has no SIM lock, it's bootloader should be unlockable. I say "should" since I am not aware of other factors that keep the bootloader locked, but there might as well be.
On another note, unless you are a fairly advanced user and are set on flashing your device with a custom kernel, I would not recommend a bootloader unlock before root or an option to back up of TA becomes available.
It contains your device's DRM which gets irreversibly lost which makes your camera perform worse(BIONZ stops working), among other things.
CPW is the place to go for unlockable fones. I got my Z5P from there.
Sent from my SGP311 using XDA Free mobile app
As mentioned elsewhere, IN GENERAL (rare exceptions) - if it's SIM-unlocked it'll be bootloader-unlockable. If it's SIM-locked, the bootloader is almost guaranteed to be perma-locked.
While SIM locks and bootloader locks are technolgically independent, in the case of Sony devices (This rule of thumb can NOT be applied to any other manufacturer), SIMlocked devices have a permanent bootloader lock, devices sold without a SIM lock can have bootloader unlocked. Note that in the case of phones sold with a SIM lock that are later unlocked with a PIN - the bootloader lock is still disallowed.
Cheese for the replys everyone I got the phone from the carphone and its boot loader unlock allowed yes
I got the regular z5 instead though.
Hey, Dunno if I have an option or not, but my phone says Bootloader Unlock Allowed: No.
I imagine that it's a no, but is there any way to unlock the BL? If not I may consider swapping the Z5P out for something else, dunno if I can live without root
NJ72 said:
Hey, Dunno if I have an option or not, but my phone says Bootloader Unlock Allowed: No.
I imagine that it's a no, but is there any way to unlock the BL? If not I may consider swapping the Z5P out for something else, dunno if I can live without root
Click to expand...
Click to collapse
Try flashing another firmware through flashtool that is allowed.
KbaB.BroS said:
Try flashing another firmware through flashtool that is allowed.
Click to expand...
Click to collapse
Worth a punt, didn't think about that. The only concern is that Flashtool isn't supported for the Z5p according to Sony's site.
NJ72 said:
Worth a punt, didn't think about that. The only concern is that Flashtool isn't supported for the Z5p according to Sony's site.
Click to expand...
Click to collapse
As long as you use flashmode there is no need to be supported, because the program doesn't know which phone it is in that state. I flashed my Z5P once using flashtool about a week ago.
KbaB.BroS said:
As long as you use flashmode there is no need to be supported, because the program doesn't know which phone it is in that state. I flashed my Z5P once using flashtool about a week ago.
Click to expand...
Click to collapse
OK, cool, thanks.
Where do I get the firmware from for Flashtool? Can I flash something like AurRom using Flashtool?
Sorry for the idiot questions, but I haven't used Flashtool very much at all. Much more familiar with ODIN, ADB and flashing through recovery...
NJ72 said:
OK, cool, thanks.
Where do I get the firmware from for Flashtool? Can I flash something like AurRom using Flashtool?
Sorry for the idiot questions, but I haven't used Flashtool very much at all. Much more familiar with ODIN, ADB and flashing through recovery...
Click to expand...
Click to collapse
Install flashtool from "flashtool.net"
It comes bundled with Xperifirm where you can download ftf files for every Xperia device. You access Xperifirm through the Flashtool program.
You cannot flash AurROM through flashtool because it's not a ftf file. Flash a stock rom and try unlocking the Bootloader afterwards.
And don't worry about asking "stupid questions". This thread is made for every kind of questions, as long as it's about the device.
KbaB.BroS said:
Install flashtool from "flashtool.net"
It comes bundled with Xperifirm where you can download ftf files for every Xperia device. You access Xperifirm through the Flashtool program.
You cannot flash AurROM through flashtool because it's not a ftf file. Flash a stock rom and try unlocking the Bootloader afterwards.
And don't worry about asking "stupid questions". This thread is made for every kind of questions, as long as it's about the device.
Click to expand...
Click to collapse
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
NJ72 said:
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
Click to expand...
Click to collapse
You can try this guide:
http://m.youtube.com/watch?v=F0bSsGxFdks
NJ72 said:
Thanks very much.
One final question, in the UK I have EE WiFi calling currently - if I install non-carrier specific firmware I will most likely lose this. Is there any way I can backup the existing software so I can revert whether the flashtool flash works or not?
Click to expand...
Click to collapse
What you want to do is follow sonys instructions on how to check if your phone is able to unlock bootloader here: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
If you can unlock your bootloader, which you will know after performing the simple steps provided by sony, then you need to install android studio along with required drivers etc, before you can actually unlock the bootloader.
Android studio can be found here: http://developer.android.com/sdk/installing/index.html?pkg=studio
Read everything throughly, it is important to get all the details regarding usage and installation.
After installing Android studio, you should download all the required SDK's found inside android studio->Configure->SDK Manager.
On the left side you will see several options in the navigation menu.
First go to Appearance & Behavior->System settings->Android SDK. Then in the "window" you have, make sure the first tab is selected (SDK Platforms).
Here you need to check all the android versions your phone(s) run.
Then go to the second tab (SDK Tools) and download:
Android SDK Build Tools
Android SDK Tools 24.4.1
Android SDK Platform-Tools 23.1
Google USB Driver
Android NDK
I am not sure if you really need the NDK one, but the rest I think is required. You can do as I did and choose all if you want.
On the last tab (SDK Update Sites) I have checked everything.
When you have done all of this, you should install Flashtool and go to the install directory and open the Driver folder, where you will find a .exe file. Run this and click next untill you can choose a few items from a list, in this list you should check Fastboot drivers, and USB drivers, and any other options that are relevant to your use, then finish the installation. (The entire installation of Flashtool should be done with 100% admin rights on the user).
After this is done, connect your phone to your pc and go to device management on your pc and you will likely find something similar to this:
If you have this yellow exclamation mark triangle thingy, then you will need to manually install your USB drivers.
Download your driver here: http://developer.sonymobile.com/downloads/drivers/
Then right click the yellow exclamation mark triangle thingy device in device management, and select update driver, then select "Browse my computer for driver software".
On the next window, select "Let me pick from a list of device drivers on my computer".
In the list that appears, select "Show All Devices" and click next.
Click the "Have Disk" button, then navigate to the driver you downloaded, and you will get 3 options in the window on you screen, select "Android ADB Interface" and click next.
Confirm by pressing "Yes" Then press "Install".
If completed without problems you should see "Windows has successfully updated your driver software".
*NOTE* On the above steps, you can also navigate to the folder where you installed android studio, which should be something similar to this: C:\Program Files(x86)\Android\android-sdk\extras\google\usb_driver OR it can be found your USER folder.
and here you can install the usb_driver aswell, which should make most phones support USB debugging and ADB on via your pc.*NOTE*
now reconnect your phone and the exclamation mark triangle thingy should be gone, good!
Next thing you can do is navigate to the installation folder of Android studio, and go to the Platform-Tools folder.
Inside the folder, hold down shift, while right clicking any white empty space inside the folder, and click open terminal here.
In the terminal, type: "adb devices" /Without the " marks. then it should say something about daemon not running etc, when its done, do the same command again, and you should se you device listed. Good, at this point you are ready to unlock bootloader!
If you have succeeded in every step so far, then go ahead and unlock bootloader following sonys instructions!
When you are done, you can simply follow the guides provided in the custom Rom thread itself most of the time.
If not, then a simple way to do it is:
Get all the files you need for the rom flash. That means Kernel, rom img, and a custom recovery like TWRP and SuperSU.
It is REALLY important that all files are for your device specifically!
Put the SuperSU.zip and the custom Rom.zip on your sd card and put it in the phone.
To avoid any trouble, do as I did and save all those files in the Platform-Tools folder, because you need to open the terminal as shown earlier in the post, by holding shift and right clicking in the same folder as the files, this is a must.
Open the terminal from the same folder as the rom, kernel and recovery.
type:
Code:
fastboot flash boot NAMEOFYOUR_KERNEL.img (This is usually boot.img)
fastboot flash recovery NAMEOFYOUR_RECOVERY.img (Usually contains TWRP in name)
fastboot reboot
You should now press volume up key when a led lights up while you see the sony logo, a orange light, not the red one, this will bring you into recovery, from here choose install, then navigate to your SuperSU.zip and install it.
Reboot your phone and you are now rooted, if you also have a custom rom, then place it on your sd card like the SuperSU.zip, but make sure the custom rom is a ZIP file!
Boot into recovery and install the custom rom, wipe cache and dalvick cache.
Congratulations on your custom rom!
Hope this helps a bit, sorry for any errors, but this is exactly how I did it, as far as I can remember!
Btw, this can seem like alot of work, especially when and if you encounter any problems while installing. I know I did encounter ALOT of them, but hopefully with my simple guide you can avoid them!
Luckily, this is just something you have to do once if you do it 100% right!
xirt0n said:
What you want to do is follow sonys instructions on how to check if your phone is able to unlock bootloader here: http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
If you can unlock your bootloader, which you will know after performing the simple steps provided by sony, then you need to install android studio along with required drivers etc, before you can actually unlock the bootloader.
Click to expand...
Click to collapse
The problem he has is that his stock ROM (or the phone itself) doesn't allow bootloader unlocking, probably because of SIM and carrier lock. Therefore he first needs to find a way to make the phone unlockable.
KbaB.BroS said:
The problem he has is that his stock ROM (or the phone itself) doesn't allow bootloader unlocking, probably because of SIM and carrier lock. Therefore he first needs to find a way to make the phone unlockable.
Click to expand...
Click to collapse
I am no expert on this, but doesnt the carrier decide if its locked or not?
I've seen people solve it by flashing different and unbranded firmware, but not for this particular phone tho, but I dont think it's officially possible.
xirt0n said:
I am no expert on this, but doesnt the carrier decide if its locked or not?
I've seen people solve it by flashing different and unbranded firmware, but not for this particular phone tho, but I dont think it's officially possible.
Click to expand...
Click to collapse
At this point he could at least try, he's got nothing to lose. I have never had this problem, because I buy my phones unlocked no carrier involved, so these are only suggestions.
KbaB.BroS said:
At this point he could at least try, he's got nothing to lose. I have never had this problem, because I buy my phones unlocked no carrier involved, so these are only suggestions.
Click to expand...
Click to collapse
Yeah, what I would try is first just try to do a full restore of your phone via PC Companion, and if that doesnt work then id try downloading an unbranded firmware from XperiFirm (If I am not mistaken, those named CUSTOM or something are unbranded) and then flash that via flashtool and see if that works, if not then your last hope is to get it replaced by warranty, which I'd say is fraud if the device isnt actually malfunctioning.
xirt0n said:
Yeah, what I would try is first just try to do a full restore of your phone via PC Companion, and if that doesnt work then id try downloading an unbranded firmware from XperiFirm (If I am not mistaken, those named CUSTOM or something are unbranded) and then flash that via flashtool and see if that works, if not then your last hope is to get it replaced by warranty, which I'd say is fraud if the device isnt actually malfunctioning.
Click to expand...
Click to collapse
I don't think PC Companion works at all, because the only thing it does is downloading identical firmware like the one on the phone. So Flashtool only choice.
I replaced mine with one from flashtool that has a lot less bloatware it originally came with.
KbaB.BroS said:
I don't think PC Companion works at all, because the only thing it does is downloading identical firmware like the one on the phone. So Flashtool only choice.
I replaced mine with one from flashtool that has a lot less bloatware it originally came with.
Click to expand...
Click to collapse
Ok, I never personally used PC companion so I didnt know what it does, I just saw people suggest it around
Pls
Pls
Plsssss custom recovery
custom recovery m5 dual
yes please some developer please help us obtain recovery for our xperia m5's if i could have done it i already would have but im a noob at building recoveries ..........................sighh:crying::crying:
I've been using flash fire but takes too long please developers make a custom recovery
Yes please, I just got this from a great Vodafone deal, but would LOVE to have this set up like my Xperia T, with a locked bootloader, but custom recovery and debloated clean android
It's not that easy. As you may already know, Xperia devices doesn't have a dedicated recovery partition and thus you need to pack recovery together with the stock kernel and put a selector at boot (like "press up to go to recovery"). Besides that, the main issue I see right now is the lack of support from Flashtool, basically you need to unlock the bootloader in order to flash new boot images, by unlocking the bootloader, Xperia Companion/Sony Update Service refuses to repair the device if something goes wrong, and since Flashtool also doesn't work, your device may end soft-bricked until you go to a Service Center, and that's what just happened to me =/
I was looking into the possibility of getting TWRP working with our device, but at least until Flashtool becomes compatible with our Xperia M5 I won't mess with the boot partition anymore. At my first try I got a non working boot partition but managed to get back to a working state, but then I tried a more "hacky" approach by getting the TWRP RAM Disk of a similar device, making the required changes (fstab, etc) and then repacking with our stock kernel but things didn't go well, I got my device soft-bricked again but this time it would go only into flash mode (no fastboot) and since Xperia Companion/Sony Update service refused to repair my phone because of the unlocked bootloader condition at the time of the failure and the lack of Flashtool support my only choice was sending it to the Service Center, now I'm currently without my phone *sigh*
@mbc07 good luck getting your phone back quickly, let's us know how it goes.
Yes, I have already posted on the flashtool thread to encourage them to support this phone. I hope the fact it is not on snapdragon does not put them off too much.
I may be wrong but it's not a matter of having a MediaTek/Qualcomm SoC, it looks like late-2015 Xperia devices uses a slight different S1 protocol that's not handled by current versions of Flashtool (especially the TA stuff). I saw some Z5 Premium owners having incompatibilities too and to reforce my assumption, Xperia C/C4/E4 are MediaTek-based devices but they work fine with Flashtool...
Since the Sony introduced drm-verity or what ever it is root on locked Bootloader with working recovery maybe nigh on impossible. Yes I know there's kingroot, flashtool is just a waiting game pretty sure it'll be included at some point
At least i know people are trying to get this for us. This thread has reassured me, thanks guys
Yep, I think things are moving in the right direction for those with big brains to make a big breakthrough for us!
News?
Has anyone tried it? :/ https://www.google.co.id/url?sa=t&s...gg9MAg&usg=AFQjCNHT7mAg7aMNhUEo3lpJYpzkL9KFRQ
Is flashtool still not compatible?
Bennybtc said:
Has anyone tried it? :/ https://www.google.co.id/url?sa=t&s...gg9MAg&usg=AFQjCNHT7mAg7aMNhUEo3lpJYpzkL9KFRQ
Click to expand...
Click to collapse
It's fake!
Sent from my E5603 using Tapatalk
someone has an easy way to root this M5 MM?
casaynoonhack said:
someone has an easy way to root this M5 MM?
Click to expand...
Click to collapse
Yes, but you need an unlockable bootloader and a TA Backup (optional, but highly recommended). You just need to use this kernel...
my team ported xperia m5 twrp e5603
---------- Post added at 03:44 PM ---------- Previous post was at 03:44 PM ----------
http://forum.xda-developers.com/xperia-m5/general/recovery-3-0-2-1-t3461396 look at this
Well let me explain this question, i bought this device in aliexpress cause i live in mexico, so, my device version is the chinese (this for the network compatibility).
when the new software version roll out i downloaded in the realme web i tried to install it. But i was not able to, so i unlocked the bootloader to try some custom roms, i install the recovery TWRP , and then i downloaded the pixwel experience, before installing i checked and the realme ui update was released, so i tried to install it, but i couldn't cause i had the bootloader unlocked and the custom recovery.
Next thing i did was install the stock recovery, and then i locked again the bootloader, but now the cellphone dont start, it only shows the screen of "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it" .
The problem here is, the recovery dont start and the fastboot its locked and i can't bypass that.
I'm looking for a solution, but i want to know if anyone have solve this before or have any idea to do it. Thanks guys!
well it happened to me same the only way is to take it to realme service center or finde some one who have the oppo realme server to flash it like i did ifound a guy who have an official server the flash my device am from algeria
Update
Irvinukis said:
Well let me explain this question, i bought this device in aliexpress cause i live in mexico, so, my device version is the chinese (this for the network compatibility).
when the new software version roll out i downloaded in the realme web i tried to install it. But i was not able to, so i unlocked the bootloader to try some custom roms, i install the recovery TWRP , and then i downloaded the pixwel experience, before installing i checked and the realme ui update was released, so i tried to install it, but i couldn't cause i had the bootloader unlocked and the custom recovery.
Next thing i did was install the stock recovery, and then i locked again the bootloader, but now the cellphone dont start, it only shows the screen of "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it" .
The problem here is, the recovery dont start and the fastboot its locked and i can't bypass that.
I'm looking for a solution, but i want to know if anyone have solve this before or have any idea to do it. Thanks guys!
Click to expand...
Click to collapse
i´ve been "searching" (not too much to be honest) a way to flash my device, or even easier, to unlock the bootloader, once that is done, i will be able to do the next thing.
There are ways to "force" flashing modifying the hardware (i really don't want to that), other places suggest flashing a vbmeta.img, but i get back to the same, i need the bootloader
im actualy downloading UFI android tool, any update i will post it
Irvinukis said:
i´ve been "searching" (not too much to be honest) a way to flash my device, or even easier, to unlock the bootloader, once that is done, i will be able to do the next thing.
There are ways to "force" flashing modifying the hardware (i really don't want to that), other places suggest flashing a vbmeta.img, but i get back to the same, i need the bootloader
im actualy downloading UFI android tool, any update i will post it
Click to expand...
Click to collapse
well, my research and asking lead me to teh JIG usb to force the download mode, but i need to build it, does anyone have experience with this?
Firstly u need to flash twrp with adb and then use twrp to flash the rom. Then wipe and clean cache and you are done
eni_pog said:
Firstly u need to flash twrp with adb and then use twrp to flash the rom. Then wipe and clean cache and you are done
Click to expand...
Click to collapse
How can i do that with the bootloader blocked?
Can u explain me please?
The solution may be QFI and EMMC download tool, if unbrick the device i'll post a guide
i made a EDL cable that i'm gonna use to try, i don't even know if the device have that mode, i'm actually searching a micro usb to type c usb to try
Irvinukis said:
Well let me explain this question, i bought this device in aliexpress cause i live in mexico, so, my device version is the chinese (this for the network compatibility).
when the new software version roll out i downloaded in the realme web i tried to install it. But i was not able to, so i unlocked the bootloader to try some custom roms, i install the recovery TWRP , and then i downloaded the pixwel experience, before installing i checked and the realme ui update was released, so i tried to install it, but i couldn't cause i had the bootloader unlocked and the custom recovery.
Next thing i did was install the stock recovery, and then i locked again the bootloader, but now the cellphone dont start, it only shows the screen of "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it" .
The problem here is, the recovery dont start and the fastboot its locked and i can't bypass that.
I'm looking for a solution, but i want to know if anyone have solve this before or have any idea to do it. Thanks guys!
Click to expand...
Click to collapse
I think EDL mode flashing stock ROM is a good way, but is there compatible download tool or image? I have ever used Miflash to downgrade my bootloader locked Xiaomi 4c for unlocking bootloader in EDL mode (maybe "fasboot oem edl" ,"fastboot reboot-edl", or "fastboot reboot edl" command).
Unlocking the Mi4c Bootloader: https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
Miflash guide: https://xiaomi.eu/community/threads/miui-10-developer-rom-8-9-13-with-miflash.47542/
Did you get the solution same problem
Well let me explain this question, i bought this device in aliexpress cause i live in mexico, so, my device version is the chinese (this for the network compatibility).
when the new software version roll out i downloaded in the realme web i tried to install it. But i was not able to, so i unlocked the bootloader to try some custom roms, i install the recovery TWRP , and then i downloaded the pixwel experience, before installing i checked and the realme ui update was released, so i tried to install it, but i couldn't cause i had the bootloader unlocked and the custom recovery.
Next thing i did was install the stock recovery, and then i locked again the bootloader, but now the cellphone dont start, it only shows the screen of "The current image (boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer service to fix it" .
The problem here is, the recovery dont start and the fastboot its locked and i can't bypass that.
I'm looking for a solution, but i want to know if anyone have solve this before or have any idea to do it. Thanks guys!
did u get the solution bro
Not yet, i have some steps to do it, but now im facing the last step, the file don´t get recognized by the tool, this tool ask for a scatter file, and the one with QFIL, i need a xml firehose fle, and i havent found it
did u get the solution bro[/QUOTE]
What i got is this:
Emergency download: press vol + and vol - then connect it to the pc, the pc will recognize it as port 9008 com in the device manager of your pc, if yor phone reboots u have to disconnect the battery cause the battery forces the reboot of the EDL mode, maybe if you put the phone on EDL mode an then quickly flash would work with out tearing appart the device
Files: you need to install qualcomm drivers (https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/), download the .ofp file of your device (i get if from here https://oppostockrom.com/oppo-realme-x-rmx1901 ), then you need to download the tool you will use
here is where things are gonna get a bit harder
MSMDownload: this is the official tool, it came withe ofp file from the link i put before, the proble is you need a user and password, i haven't found where to get one official, its from oppo workers i guess
There is a cracked version, but don't recognizes the file
QFIL: its for qualcom devices (found it here https://androidmtk.com/download-qualcomm-flash-image-loader-qfil), this will let you flash every qualcomm device (or thats what they tell you), it shows the port, but ask for a xml file and a programer path (thing that i haven't found it yet)
Cracked MSMDownload: i found this https://www.techoxygen.com/msm-download-tool/ , https://romprovider.com/2020/02/flash-qualcomm-devices-using-msm-download-tools/, or this https://www.youtube.com/watch?v=0CKsEOfGGaQ
now, in my case the file its not recognized, it says incorrect scatter file, from here you can start diggin around, if you solve this please let me know
What i got is this:
Emergency download: press vol + and vol - then connect it to the pc said:
https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/),[/url] download the .ofp file of your device (i get if from here https://oppostockrom.com/oppo-realme-x-rmx1901 ), then you need to download the tool you will use
here is where things are gonna get a bit harder
MSMDownload: this is the official tool, it came withe ofp file from the link i put before, the proble is you need a user and password, i haven't found where to get one official, its from oppo workers i guess
There is a cracked version, but don't recognizes the file
QFIL: its for qualcom devices (found it here https://androidmtk.com/download-qualcomm-flash-image-loader-qfil), this will let you flash every qualcomm device (or thats what they tell you), it shows the port, but ask for a xml file and a programer path (thing that i haven't found it yet)
Cracked MSMDownload: i found this https://www.techoxygen.com/msm-download-tool/ , https://romprovider.com/2020/02/flash-qualcomm-devices-using-msm-download-tools/, or this
now, in my case the file its not recognized, it says incorrect scatter file, from here you can start diggin around, if you solve this please let me know
Click to expand...
Click to collapse
Hi man , did you try this method?
devilkar said:
Hi man , did you try this method?
Click to expand...
Click to collapse
yeah, i tried, but my bootloader its blocked
zaki789 said:
well it happened to me same the only way is to take it to realme service center or finde some one who have the oppo realme server to flash it like i did ifound a guy who have an official server the flash my device am from algeria
Click to expand...
Click to collapse
Hi bro i from algeria too can you tell where you flashed your phone, please adresse phone number any help, thank you
Question:
Is there any way to install a different firmware on my XZ2 Compact (SO-05K)? Preferably the one for H8314 as they are both single SIM.
Story:
Recently, I got my (used) XZ2 Compact and what I immediately tried to do was to unlock the bootloader so I could install LineageOS. What I didn't know was that the device was the Japanese model (SO-05K) so I nearly gave up on unlocking its bootloader and just live with it as it is. At least it was SIM unlocked so it wasn't totally useless.
Not until I found this post. So I followed that post and to my surprise, the bootloader indeed got unlocked.
Now, my problem is that I can't successfully install LineageOS 17.1 because the stock firmware is different from what was required in order to flash it. So I tried changing the firmware (flashtool and newflasher) but never had luck. Hence, the question.
Thank you!
Did you get any luck in installing h8314 on do-05k? When I tried using newflasher, I got "Error, didn't got signature OKAY reply! Got reply: FAILFailed to verify cms"
Not sure about Android images. But, I was able to flash Sailfish OS, a Linux based OS (https://forum.xda-developers.com/t/gnu-linux-sailfish-os-for-xperia-tama-devices.4008699/) on my unlocked SO-05K. It uses the firmware files for H8314 from Sony's Open Devices website. I guess both the devices (H8314 nad SO-05K) are the same, but with different model numbers hardcoded.
Could be that the flasher checks for a connected H8314, but finds no such device and fails. I experienced similar problem initially that the fastboot flasher script was looking for H8314, but was finding SO-05K and hence was failing. Modifying the script to look for SO-05K allowed me to use the script. In any case, I believe one could manually flash each file to the right partition using fastboot only. That said, I am no expert.
I've got a SO-05K with unlocked bootloader and I'd love to flash LineageOS or any other custom andriod rom but I'm not sure if its compatible and I'd hate to brick my device.
Does anyone have an idea if its possible?
Is there a program that will allow scan a rom and tell me to if it supports SO-05K?
I have same problem
Hi,
My device: Sony Xperia XZ2 Compact, version SO-05K, NTT DoCoMo, Android 10 > working well.
.
I tried to install LineageOS 17.1 on the Xperia XZ2c.
I followed the page https://wiki.lineageos.org/devices/xz2c/install
- Performed the basic requirements.
- The latest recovery file 'lineage-17.1-20210514-recovery-xz2c.img' has been installed.
Recovery installed in 'Active slot: a'.
- 'Factory reset', then 'Format data / factory reset' was done.
- Sideload package using: 'adb sideload copy-partitions-20210323_1922.zip'
Everything went well, but when installing the update 'lineage-17.1-20210514-nightly-xz2c-signed.zip' an error occurred and does not allow to proceed:
.
"Installing update ..."
"Step 1/2"
"Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)"
.
EDIT:
70%
[0127/031946.016998:ERROR:cached_file_descriptor.cc (89)] Failed to flush cached data: no space left on devive (28)
[0127/031946.017290:ERROR:extend_writer.cc(53)] utils:WriteA11(fd_, c_bytes + bytes_written,bytes_to_write) failed.
Leaving there, I tried official firmware SO-05K, FlashTool, Newflasher, but they all went wrong.
I also tried the Unofficial TWRP, and it gave an error: 'error: cannot load 'boot_a': No such file or directory´.
The error may be in the access to Slot-a, is it?
Right now I only have 'Lineage Recovery 17.1' in slot-a. The device locks on the Sony Logo, obviously.
That said, I am not an expert.
Someone can help me?
Sorry for the bad English.
anjomale said:
Hi,
My device: Sony Xperia XZ2 Compact, version SO-05K, NTT DoCoMo, Android 10 > working well.
.
I tried to install LineageOS 17.1 on the Xperia XZ2c.
I followed the page https://wiki.lineageos.org/devices/xz2c/install
- Performed the basic requirements.
- The latest recovery file 'lineage-17.1-20210514-recovery-xz2c.img' has been installed.
Recovery installed in 'Active slot: a'.
- 'Factory reset', then 'Format data / factory reset' was done.
- Sideload package using: 'adb sideload copy-partitions-20210323_1922.zip'
Everything went well, but when installing the update 'lineage-17.1-20210514-nightly-xz2c-signed.zip' an error occurred and does not allow to proceed:
.
"Installing update ..."
"Step 1/2"
"Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)"
.
EDIT:
70%
[0127/031946.016998:ERROR:cached_file_descriptor.cc (89)] Failed to flush cached data: no space left on devive (28)
[0127/031946.017290:ERROR:extend_writer.cc(53)] utils:WriteA11(fd_, c_bytes + bytes_written,bytes_to_write) failed.
Leaving there, I tried official firmware SO-05K, FlashTool, Newflasher, but they all went wrong.
I also tried the Unofficial TWRP, and it gave an error: 'error: cannot load 'boot_a': No such file or directory´.
The error may be in the access to Slot-a, is it?
Right now I only have 'Lineage Recovery 17.1' in slot-a. The device locks on the Sony Logo, obviously.
That said, I am not an expert.
Someone can help me?
Sorry for the bad English.
Click to expand...
Click to collapse
I'm no expert, but I had a similar issue with the Z3 D6683 Hong Kong variant to work with LineageOS for D6633.
I remember having to first install a stock D6633 firmware but I needed to remove fwinfo.xml so that FlashTool would allow flashing the firmware.
Perhaps a similar trick could work for the So-05K XZ2 Compact?
The link is to the D6683 story: https://forum.xda-developers.com/t/sony-xperia-z3-dual-d6683-flash-to-d6633-marshmallow.3404448/
lal883 said:
Not sure about Android images. But, I was able to flash Sailfish OS, a Linux based OS (https://forum.xda-developers.com/t/gnu-linux-sailfish-os-for-xperia-tama-devices.4008699/) on my unlocked SO-05K. [...]
Click to expand...
Click to collapse
wait... you installed sailfish on an xz2c? I thought these aren't supported?
I would almost prefer that over lineage os tbh... haven't checked your link yet, but I hope it contains proper instructions on how to do it -_-
anjomale said:
[...]
"Installing update ..."
"Step 1/2"
"Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)"
.
EDIT:
70%
[0127/031946.016998:ERROR:cached_file_descriptor.cc (89)] Failed to flush cached data: no space left on devive (28)
[0127/031946.017290:ERROR:extend_writer.cc(53)] utils:WriteA11(fd_, c_bytes + bytes_written,bytes_to_write) failed.
Leaving there, I tried official firmware SO-05K, FlashTool, Newflasher, but they all went wrong.
I also tried the Unofficial TWRP, and it gave an error: 'error: cannot load 'boot_a': No such file or directory´.
The error may be in the access to Slot-a, is it?
Right now I only have 'Lineage Recovery 17.1' in slot-a. The device locks on the Sony Logo, obviously.
[...]
Click to expand...
Click to collapse
I am having exactly the same issues atm! did you ever solve them? how did you make it to 70%? I never managed to get past the error 28..
I was also able to flash Sailfish, see https://forum.xda-developers.com/t/...ish-os-for-xperia-tama-devices.4008681/page-5
Sadly Sailfish doesn't quite support one essential app and also no japanese text so I went back again.
Still so using the wrong firmware on the device is definitely possible, question is now how to get it onto it...
Z0rnica said:
I was also able to flash Sailfish, see https://forum.xda-developers.com/t/...ish-os-for-xperia-tama-devices.4008681/page-5
Sadly Sailfish doesn't quite support one essential app and also no japanese text so I went back again.
Still so using the wrong firmware on the device is definitely possible, question is now how to get it onto it...
Click to expand...
Click to collapse
Sounds like it's worth downloading the H8314 firmware fileset from Sony with the Xperifirm client then delete the fwinfo.xml file before starting up the FlashTool client and building an .ftf package to flash to the device. Then your device will pretend it's an H8314 model assuming it boots up. From there you can follow the instructions on the LineageOS official guide.
yes, currently downloading flashtool to try to create the ftf package - simply flashing the firmware (as is) with new flasher did not work... the other thread also said, that flashing the ftf with flashtool wont work (https://forum.xda-developers.com/t/need-help-flashing-xz2-ftf-flash-fails.3873024/), so I am hoping that flashing the ftf with newflasher will work...
I am not quite sure which H8314 firmware to pick though, most seem to be branded. there is one designated "internal" and "storefront", I assume that is for over the shelf phones without contracts? there is also one called internal "commercial and journalists", I assume that contains the nsa spyware?
lal883 said:
Not sure about Android images. But, I was able to flash Sailfish OS, a Linux based OS (https://forum.xda-developers.com/t/gnu-linux-sailfish-os-for-xperia-tama-devices.4008699/) on my unlocked SO-05K. It uses the firmware files for H8314 from Sony's Open Devices website. I guess both the devices (H8314 nad SO-05K) are the same, but with different model numbers hardcoded.
Could be that the flasher checks for a connected H8314, but finds no such device and fails. I experienced similar problem initially that the fastboot flasher script was looking for H8314, but was finding SO-05K and hence was failing. Modifying the script to look for SO-05K allowed me to use the script. In any case, I believe one could manually flash each file to the right partition using fastboot only. That said, I am no expert.
Click to expand...
Click to collapse
Do you know if your H8314-sailfish flashed SO-O5K supports the same LTE bands as a "real" H8314? I'm having trouble getting trustworthy info on what bands the SO-O5K supports but some sources e.g. kimovil imply the Docomo version has fewer bands.
chaphal3 said:
Do you know if your H8314-sailfish flashed SO-O5K supports the same LTE bands as a "real" H8314? I'm having trouble getting trustworthy info on what bands the SO-O5K supports but some sources e.g. kimovil imply the Docomo version has fewer bands.
Click to expand...
Click to collapse
I cannot be certain about that. All I could confirm is that I havn't had trouble so far connecting to 4G network of my operator (not Docomo).
Does anyone know if you can downgrade on the SO-05K running Android 10 to the presumably Docomo Android 9 firmware on xperifirm, without breaking anything?4
I've flashed H8314 from 10 back to 9 before with newsflasher, I just need to know if I can do the same thing with Docomo firmware on SO-05K...
Hi guys, I'm planning to buy a so-05k to make a comparison with the old so-02k (xz1c) but I'm wondering if I can put the "global" firmware or not and if there is a working guide to unlock the LTE bands
Thanks for the clarification.
I've kept trying to flash global firmware to no avail, even modifying the source code of newflasher to stop it from returning after facing any error just results in another error:
Code:
Error, didn't got flash OKAY reply! Got reply: FAILCommand not authenticated
This error isn't actually part of newflasher and I'm assuming is from the phone itself.
I've also tried mix-matching the files from the Japanese and the Global roms, because at this point I don't really care if the phone bricks itself lol. But yeah, still no luck, either it just flashes as the regular Japanese firmware with no noticeable changes, or it just straight up fails.
Very disappointing!
The closest thing I have achieved is installing a treble ROM on the device, however the camera is non-functioning which is a dealbreaker for me.
drychemical said:
I've kept trying to flash global firmware to no avail, even modifying the source code of newflasher to stop it from returning after facing any error just results in another error:
Code:
Error, didn't got flash OKAY reply! Got reply: FAILCommand not authenticated
This error isn't actually part of newflasher and I'm assuming is from the phone itself.
I've also tried mix-matching the files from the Japanese and the Global roms, because at this point I don't really care if the phone bricks itself lol. But yeah, still no luck, either it just flashes as the regular Japanese firmware with no noticeable changes, or it just straight up fails.
Very disappointing!
The closest thing I have achieved is installing a treble ROM on the device, however the camera is non-functioning which is a dealbreaker for me.
Click to expand...
Click to collapse
Hi, what do you mean with a treble rom ?
bob1791 said:
Hi, what do you mean with a treble rom ?
Click to expand...
Click to collapse
Treble ROMs are ROMs that can work on any device shipped with Android 8.0 or later, to keep the explanation simple.
You can see them all here: https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
drychemical said:
Treble ROMs are ROMs that can work on any device shipped with Android 8.0 or later, to keep the explanation simple.
You can see them all here: https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Click to expand...
Click to collapse
Oh right... So you put and android rom on SO-05K and it worked well ?
bob1791 said:
Oh right... So you put and android rom on SO-05K and it worked well ?
Click to expand...
Click to collapse
Yep, apart from the camera, from my brief test everything worked as it should.