So I just got this XA2 and it had sailfish operation system, that's why I bought it. Today I decided to install android to the phone, because I didn't have money to buy the full version of sailfish.
So my bootloader is unlocked and I have tried to save the phone with newflasher but even when it flashes something, the phone still says that it's corrupt. And I cannot download stockrom from xperifirm, because the download always timesout.
And I'm using arch, if that matters.
Any help?
Related
Hello, I have Moto Z play with chinese firmware (64gb model) and tried to flash european version of firmware so I can use google services. flashing succeeded until i got to the part where firmware flashing starts (fastboot flash system system.img_sparsechunk.0) and thats where it started to fail. So I assumed it cannot be flashed as phone model differes as well as some hardware potentially, my model is XT1635-03 when non chinese are XT1635-02 with 32gb max memory. I completed flashing all parts from european firmware and as system imgs failed - chinese version remained. Later I found another way of having google services on my phone, I flashed TWRP recovery with SuperSU and then installed Xposed framwork to allow install other frameworks like google play services framework. So everything went well and I managed to enable google services on chinese phone, but I couldn't upgrade software version as it fails verification when it finds european boot, recovery, logo and modem ( I assumed). My solution was to reinstall stock chinese firmware and flash everything again to use google services. Afther reinstalling firmware I was allowed to upgrade it, next step was to flash TWRP recovery and the rest, but that's where it started to go wrong. It will not let me flash anything anymore.
Fastboot devices will find my phone, adb devices works when phone is switched on, but not when in bootloader mode, adb reboot bootloader will not work - no devices found. When I try to flash something it just gets stuck in cmd window and phone bootloader (volume buttons will not navigate, but power button will switch off). Also I noticed when I switch USB debugging on, go to bootloader mode and out or restart phone it will switch by itself off. Tried to reinstall every driver and program, nothing worked... maybe firmware update triggered something, even when version didn't change, only build number when I thought it will upgrade to android 7.
Please someone help me, my brains hurt so much and I don't know what to do. Thank you in advanced
Long story short, my phone came from China and did not have Google Apps installed. I tried to root it with some youtube method and the boot.img file got changed, not knowing what to do next I gave it to repair shop.
They somehow managed to restore the stock rom and gave me the stock rom.zip file as well but the IMEI was removed, so after trying a few methods I realized my phone doesn't get detected in META Mode but somehow gets detected if it's turned off and connected directly. I thought should install the stock firmware again by myself.
I first tried it with Download mode only, it loaded a few files but gave some error like IMGHDR_TYPE_MISMATCHED. After that it got stuck on boot screen.
So instead of the download option in SP tool I chose Format All + Download.
The thing is my phone does not get detected in META Mode so I thought it wouldn't change anything but now the phone doesn't turn on. The screen is blank, nothing happens with phone is connected to charger.
If I connect the phone to PC, it detects a Preloader Port Android (COM 7) on device manager for a few seconds then goes off, then keeps going on and off like it's trying to boot but doesn't boot.
Please help. This phone can't be sent back to china because the warranty is possibly void as this phone has been used about 6 months and also been tried for rooting.
It still gets connected via SP Tool but gives the same error after loading a few files. Image Attached.
https://preview.ibb.co/kyJvZn/xt1662bricked.png
Any help in this regard would be much appreciated.
Thank you.
I had the same initial issue, so I did the "Format All + Download" on the SP Tool with a ROM I downloaded and it flashed successfully and everything works fine now, it even auto updated to the Android 7.0 and the latest security patches (05/08/18).
I cannot remember from where I got the ROM I used but I can upload it for you, if you want/need it.
The only issue is that I lost my IMEI. When I find a way to fix it I will let you know.
https://www.youtube.com/watch?v=jgTSbGBk1bI
I followed that and I successfully restored my lost IMEI, everything works fine now.
Hope it helps.
Tiki Thorsen said:
I had the same initial issue, so I did the "Format All + Download" on the SP Tool with a ROM I downloaded and it flashed successfully and everything works fine now, it even auto updated to the Android 7.0 and the latest security patches (05/08/18).
I cannot remember from where I got the ROM I used but I can upload it for you, if you want/need it.
The only issue is that I lost my IMEI. When I find a way to fix it I will let you know.
Click to expand...
Click to collapse
when i m trying this i m getting error of
verified boot is enabled please download signed image (md1img-verified.img) or disable verified boot
earthworm82 said:
when i m trying this i m getting error of
verified boot is enabled please download signed image (md1img-verified.img) or disable verified boot
Click to expand...
Click to collapse
Sadly I cannot help you since I no longer have that phone available, sorry.
Hey guys,
I would have liked to get the OREO update, because it said every time is up-to-date, and I wasn't patient. because all of these already get it, and the battery life was terrible with, and I have just 30 days to cancel the phone if I'm unsatisfied with it, so it was urgent for me to update and try it.
But I didn't know enough from the newest devices, so that I need unlocked bootloader to flash STOCK ROM or ROOT or for flash RECOVERY
Mine is XT1789-06, I tried to flash first this ROM:
https://androidfilehost.com/?fid=962187416754456314
It didn't tell this is TMO. :/
This changed my baseband to TMO and my boot image to T-mobile, after I didn't have signal and the fingerprint sensor didn't work.
I wanted fix it with RETAIL ROM flashing.
I tried to flash this: https://androidfilehost.com/?w=files&flid=241773
After that my phone didn't boot, says your device is corrupt.
Cause this I tried to flash back the previous version so this: NASH_RETAIL_7.1.1_NPXS26.122-68-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
from here https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/
But no result. The baseband stucked on TMO, the phone is not start up. Fall back to fast boot mode.
After and mean while these things I tried many things.
The Motorola Device Manager isn't working at all.
The Software Upgrade Assistant what the phone want when show boot up failed message isn't working just say processing device information and isn't going further. I don't understand why the phone ask it, because that is for verizon phones.
The RSD lite says the model name is Fastboot nash S and isn't start to flash anything, when I press the start it says the phone failed to switch to fastboot mode, but it's in that.
I tried already flash more different ROMs, but didn't work one of them .
Recovery is unable, the phone isn't rooted, the bootloader is locked, however sometimes it showed ""Your device software cannot be checked for corruption. Please lock the bootloader", but I checked in the powershell and in fastboot mode I looked what phone says, so it's locked.
I was thinking maybe if I unlock it will solve the problem, but I can't turn it on, so the developer options are unavailable and I don't know maybe it won't help, if I can do it somehow.
Now if I want turn on the phone it's going to fastboot mode right away or say your device is corrupt... and after.
I can't try flash it through Qualcomm 9008 because the PC recognise the device for fastboot device.
In the device manager the computer shows Motorola ADB interface.
I try to unbrick for 3 days, please help me.
Thanks a lot in advance.
Same here, if you find anything out DM me
I already contacted with the phone, I will bring back to Repait it.
I couldn't find out nothing, I tried everything what was possible.
i think i found a solution i just dont know how it works exactly, something to do with a batch file and a full flash of the phone
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 im going to try this and let you know
Hello,
yesterday Iv benn tryin to get LineageOS on my XA2, but I missed the point about root phone straigh after unlockin bootloader.
So I unlocked bootloader then I flashed boot.img and I get TWRP. Forgot about root... TWRP is tellin me, there's no OS in my phone,
I can't install LineageOS from SD, can't install even Magisk because of same error, "Updater process ended with ERROR: 1.".
My phone stucked on Sony logo and advise about unlocked bootloader, can go just into TWRP. ADB and Fasboot is detected by PC, ADB by TWRP Sideload, fastboot just by phone. I downloaded Flashtool to put brand rom, but I gettin error after phone connected about "Unable to read TA unit 10021, error=-22 ( Hex unit value 00002725 )".
I'm not a geek, I'm just normal user who been enjoyin in CW's few years ago last time, this time it's bigger than me...
What Can I do, how do I can solve my problem? How I cant go back to stock room or anything?
Arnoldii said:
Hello,
yesterday Iv benn tryin to get LineageOS on my XA2, but I missed the point about root phone straigh after unlockin bootloader.
So I unlocked bootloader then I flashed boot.img and I get TWRP. Forgot about root... TWRP is tellin me, there's no OS in my phone,
I can't install LineageOS from SD, can't install even Magisk because of same error, "Updater process ended with ERROR: 1.".
My phone stucked on Sony logo and advise about unlocked bootloader, can go just into TWRP. ADB and Fasboot is detected by PC, ADB by TWRP Sideload, fastboot just by phone. I downloaded Flashtool to put brand rom, but I gettin error after phone connected about "Unable to read TA unit 10021, error=-22 ( Hex unit value 00002725 )".
I'm not a geek, I'm just normal user who been enjoyin in CW's few years ago last time, this time it's bigger than me...
What Can I do, how do I can solve my problem? How I cant go back to stock room or anything?
Click to expand...
Click to collapse
You should try to go back to stock rom with the Emma Tool from Sony.
Hi!
I have a problem with my new Sony Xperia XA2. When I got my new phone I decided to flash LineageOS 16.0 (the unofficial build from LuK1337), however the Lineage-build is not the problem. I got the problem when I tried to flash TWRP and Magisk, and I've realised that I did it too quick.
Here's what I did:
0. Unlocked bootloader
1. Booted TWRP
2. Flashed LineageOS
3. Flashed GAPPS.
4. Flashed Magisk.
So far, so good. This worked.
5. Decided to flash TWRP to get rid of the standard recovery.
6. Now both the standard recovery and TWRP seems to be gone.
Is there a way to revert to the standard recovery? I've tried to download FlashTool and XperiFirm, and I've downloaded the correct stock image for my Xperia XA2 Dual (H4113), but I cannot get it to only flash the bootloader.
My understanding is that the recovery and bootloader resides on the same partition. Is this correct?
When I try to flash the bootloader with FlashTool, I get an error stating that the device is identifying as H3113, which is the single-sim-version.
Thank you for the help!
I managed to get my phone working again by using Emma, as I had managed to soft-brick my phone. The bootloader said that the phone was corrupt, and turned off after 5 seconds. Using Emma and the bundled USB-C-USB-A-cable did the trick for me.
Now I'm going to install TWRP once more, and hopefully I'll manage it correctly this time.
My understanding is that we cannot install TWRP as a replacement recovery on this device because there is no true recovery partition. It's part of the boot partition. Hopefully someone will come along and correct me if I'm wrong.
You can install twrp on a/b devices. However, it installs to /boot. Thus every upgrade kills it. Which really sucks as lineage recovery sucks bad.
hjahre said:
Hi!
I have a problem with my new Sony Xperia XA2. When I got my new phone I decided to flash LineageOS 16.0 (the unofficial build from LuK1337), however the Lineage-build is not the problem. I got the problem when I tried to flash TWRP and Magisk, and I've realised that I did it too quick.
Thank you for the help!
Click to expand...
Click to collapse
Hello,
sorry for the delay.
You can use EMMA to flash back the stock firmware, however if you don't want your data lost, use flashtool ( http://flashtool.net ) and make sure your userdata is Wipe Excluded
what is the trick of USB-C-USB-A
Hello friend, what is the trick of USB-C-USB-A, can you explain it, because I can not get flashtools to work on my sony xa2, explain me the trick please
cristianrb said:
Hello friend, what is the trick of USB-C-USB-A, can you explain it, because I can not get flashtools to work on my sony xa2, explain me the trick please
Click to expand...
Click to collapse
There's really no trick to it. Just plug the cable bundled with the phone and plug it into your PC.
My problem was that I've got a Macbook Pro that only have USB-C ports. When I tried a cable with USB-C connectors in both ends, my phone would not let me flash from my computer. When I used the bundled cable and a USB-hub it worked as it should