Related
Hi people. I was trying to install a new ROM on my TF701, 'cause I was very sad to keep that stock 4.4.2.
Of course, I did a mess.
1st thing, I tried to unlock the boot with the Asus apk, but I was struck (it asked for google permission, I tried to give my correct password, but it rejected it. I saw - only too late - that maybe, if I had fully removed my google account before to use that tool, all should have been go right...).
Then, I used an utility to gain root (KingRoot4.1-release-20150703-for-xda.apk). It did the trick, but now I understand that maybe gaining the root rights it's different from "unlocking the boot". Sigh.
Then I used an utility (Flashify if my memory serves me right), to put a clockworkmod in my TF701.
I got the clockworkmod from a droidbasament link (db-blog/?p=3568).
I selected "boot" when the utility asked me what kind of img I was trying to flash... maybe I chose the wrong type again... However, it flashed the img. But now when I boot the device, I get a Signature Mismatch. Booting failed. Unrecoverable bootloader error (0x00000008), with the ASUS logo.
If I reboot with Power + Vol Down, I can get the fastboot USB download protocol, with the 3 icons in the middle of the screen.
I installed the Android SDK. I tried to take the clockworkmod recovery.img and move it in the tablet with:
fastboot boot recovery.img
but I get:
downloading 'boot.img'...
OKAY [ 0.932s]
booting...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.982s
So... the Bootloader is still locked, I imagine. Can I try to return to a full stock ROM, maybe using the microSD?
I tried to download TF701T_11.4.1.30_WW_Boot_TWRP_2870_signed.zip , put on the microSD, and launched RCK. It starts to install, but after a while I get the error broken droid picture.
I tried to rename the file to T4_SDUPDATE.zip, but I get the same results.
Am I screwed? Any help is welcome. Also, if I can fix the problem, I'll offer you a big beer! (paypal?)
Motorola Moto X2 USB does not define all that in the loader in the system, TWRP gone, instead there was an inscription:
Invalid boot image size!
failed to validate recovery image
Fastboot Reason: Fall-through from recovery boot mode.
It was established Lineage OS, correctly and properly, Ruth rights absent
I look for the cause in the expanses of the Internet - really nothing.
Who can faced with similar?
bump
have same problem here
and can't install last nightly, says "cant install on top of incompatible data"
drico_649 said:
bump
have same problem here
and can't install last nightly, says "cant install on top of incompatible data"
Click to expand...
Click to collapse
I have a suspicion that the system itself can not enable debugging on USB, but it is impossible to return to the factory settings - no TWRP. ROOT not set there for a new opportunity - a vicious circle..
the root is separated from the rom itself, it's a zip that u flash on top of ROM. but the update doesn't install on top of the same system is weird, since it's the same code.
I had to wipe data, update and then, re-setup my phone. this is boring, since I have almost 200 apps...
One thing i noticed is, on recently versions of Lineage for xt1097 (br variant of xt1095), there is an option under development settings called "update recovery when update system". On cyanogenmod, this installed a recovery made by CM itself, in lineage it does nothing. and since I turned on this option, when I try to go to recovery gave me this same error of yours. when I turn option off, recovery works again.
I think that this option enables some sort of check of recovery partition to update system and/or recovery itself, but since there isn't any recovery in OS package, it can't be installed, neither the recovery nor the rom itself (choosing to install update through system just boots up twrp, and nothing happens, I had to find zip package myself and install, then find the "error 7".)
Continued: set up your smartphone no drivers to devices. Today died system interface - just a black screen, there are sounds, the phone works, but there is no image. Tried other cable, assorted devices to get in close connection - the connection is OK. The problem with the loader has not been solved, everything develops in a poor way.
And so, I have - Smartphone. without bootloader without Root rights, the operating system crashes. The smartphone can be considered a brick! While the solution to the problems found.
Invalid boot image size!
Bush_Jr said:
Motorola Moto X2 USB does not define all that in the loader in the system, TWRP gone, instead there was an inscription:
Invalid boot image size!
failed to validate recovery image
Fastboot Reason: Fall-through from recovery boot mode.
It was established Lineage OS, correctly and properly, Ruth rights absent
I look for the cause in the expanses of the Internet - really nothing.
Who can faced with similar?
Click to expand...
Click to collapse
I also have the same problem but TWRP 3.0.0.0 condor image is only working for my moto e runninig with lineage 14.1.
has anyone solved this problem by unlocking the bootloader? with error: Failed: Command did not succeed
I tried the following bulds:
52.0.A.3.202
52.0.A.8.14
52.0.A.8.25
52.0.A.8.50
Thanks
Bibi
small update:
after updating to 52.0.A.8.50, I made "factory settings" to reset it to the old version.
But when I restart without wifi, I find build 52.0.A.8.50 again
And now the OEM unlock option, which was usable before, has turned gray !! Mystery for me.
Obviously he wants me to update to 52.0.A.8.85 !!!
SOLVED INFORMATION:
I was wrong in writing IMEI of my device, and I put a wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
bibibabi said:
has anyone solved this problem by unlocking the bootloader? with error: Failed: Command did not succeed
I tried the following bulds:
52.0.A.3.202
52.0.A.8.14
52.0.A.8.25
52.0.A.8.50
Thanks
Bibi
Click to expand...
Click to collapse
Try .131 vor wait for September
For wait for Q, maybe Sony will remove more DRM TA protection like it did with P
if it was for 2 or 3 days it is not a problem.
but I can't wait until late September.
Let's say that I bought it to be root .. and if I can't do it .. maybe I'll send it back.
Sorry, but are you telling me that they haven't solved even after almost a year?
nobody rooted?
The 3.131 where I can find it and flash arla.
if I find it on XFIRM, what program do I use to put it in my phone?
among other things to set it to factory settings he left me at 52.0.A.8.50, even without wifi.
And nice surprise .. OEM unlock is now deactivated !!!!
it leaves me very mulble
bibibabi said:
if it was for 2 or 3 days it is not a problem.
but I can't wait until late September.
Let's say that I bought it to be root .. and if I can't do it .. maybe I'll send it back.
Sorry, but are you telling me that they haven't solved even after almost a year?
nobody rooted?
The 3.131 where I can find it and flash arla.
if I find it on XFIRM, what program do I use to put it in my phone?
among other things to set it to factory settings he left me at 52.0.A.8.50, even without wifi.
And nice surprise .. OEM unlock is now deactivated !!!!
it leaves me very mulble
Click to expand...
Click to collapse
OEM unlock needs internet via a simcard and a phone restart
There ate many unlocked users using magisk and twrp.
I would recommend to follow the Sony unlocking instructions
MartinX3 said:
OEM unlock needs internet via a simcard and a phone restart
There ate many unlocked users using magisk and twrp.
I would recommend to follow the Sony unlocking instructions
Click to expand...
Click to collapse
Then:
if I do a factory reboot and I don't put the wifi in the first cellphone settings, the OEM unlock option remains gray.
If I do it and I put the wifi in the meantime that is imposed then OEM unlock is usable and therefore can be activated. Correct?
(not that it makes much sense)
However I am installing updates one after the other, and for every update I try the command. (what's also coming to 52.0.A.8.131 which has been expanding in August 2019 (practically these days) and text as MartinX3 advised.
bibibabi said:
Then:
if I do a factory reboot and I don't put the wifi in the first cellphone settings, the OEM unlock option remains gray.
If I do it and I put the wifi in the meantime that is imposed then OEM unlock is usable and therefore can be activated. Correct?
(not that it makes much sense)
However I am installing updates one after the other, and for every update I try the command. (what's also coming to 52.0.A.8.131 which has been expanding in August 2019 (practically these days) and text as MartinX3 advised.
Click to expand...
Click to collapse
It's forced by the mobile providers to check if the simcard allows unlocking
Sony isn't alone here
Unlocking factory resets the phone, too
I did check the unlock box and followed only the Sony instructions and used my generated IMEI code.
MartinX3 said:
It's forced by the mobile providers to check if the simcard allows unlocking
Sony isn't alone here
Unlocking factory resets the phone, too
I did check the unlock box and followed only the Sony instructions and used my generated IMEI code.
Click to expand...
Click to collapse
wait MartinX3,
aren't you saying that you need a simcard inserted in the cell to unlock it right? just the wifi I hope to activate the option.
Look, I followed Sony's directions (which are basically 4 things on the cross)
But it gives me that error: FAILED (remote: 'Command did not succeed')
LIST OF WHAT I DID:
-I do All the appropriate procedures:
-I received the unlock code from the official Sony site
- Platform-tool download and driver
-on the phone sets it basic, active developer commands
- USB DEBUG and UNLOCK OEM tip on the mobile phone menu
- I turn off the phone
-Attack the mobile in fastboot mode (blue light)
-then in the devices and printers, which appears in new one when I plug in the cel in fastboot mode, I update the driver of the device appeared, android studio).
-I do the ADB command -> fastboot devices
**and ai read the model serial
- Then enter the code to unlock the phone: fastboot oem unlock 0xCODESEIAL
**and I get this: FAILED (remote: 'Command did not succeed')
----------------------------------------------------------------------------
(I tried the .107, now I try with .131 as you recommended me)
UPDATE:
badly wrong, even with the 52.0.A.8.131 DOES NOT, same identical error.
Sony in his guide makes it so easy, but neither does he make the possible mistakes.
And that I can't find an explanation for this specific error.
bibibabi said:
wait MartinX3,
aren't you saying that you need a simcard inserted in the cell to unlock it right? just the wifi I hope to activate the option.
Look, I followed Sony's directions (which are basically 4 things on the cross)
But it gives me that error: FAILED (remote: 'Command did not succeed')
LIST OF WHAT I DID:
-I do All the appropriate procedures:
-I received the unlock code from the official Sony site
- Platform-tool download and driver
-on the phone sets it basic, active developer commands
- USB DEBUG and UNLOCK OEM tip on the mobile phone menu
- I turn off the phone
-Attack the mobile in fastboot mode (blue light)
-then in the devices and printers, which appears in new one when I plug in the cel in fastboot mode, I update the driver of the device appeared, android studio).
-I do the ADB command -> fastboot devices
**and ai read the model serial
- Then enter the code to unlock the phone: fastboot oem unlock 0xCODESEIAL
**and I get this: FAILED (remote: 'Command did not succeed')
----------------------------------------------------------------------------
(I tried the .107, now I try with .131 as you recommended me)
UPDATE:
badly wrong, even with the 52.0.A.8.131 DOES NOT, same identical error.
Sony in his guide makes it so easy, but neither does he make the possible mistakes.
And that I can't find an explanation for this specific error.
Click to expand...
Click to collapse
Sadly I'm out of ideas
Hoping here or at https://talk.sonymobile.com/t5/Xper...er-Failed-Command-did-not-succeed/m-p/1387453 someone will answer you
MartinX3 said:
Sadly I'm out of ideas
Hoping here or at https://talk.sonymobile.com/t5/Xper...er-Failed-Command-did-not-succeed/m-p/1387453 someone will answer you
Click to expand...
Click to collapse
I found out!
then:
turn and turn, and check IMEI of the cell I used.
I was wrong in writing IMEI, and I put the wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
well OTHER PROBLEM!
it doesn't flash me twrp
with this error:
Sending 'recovery' (34192 KB) OKAY [0.737s]
Writing 'recovery' FAILED (remote: 'No such partition.')
I'm looking at guides.
bibibabi said:
I found out!
then:
turn and turn, and check IMEI of the cell I used.
I was wrong in writing IMEI, and I put the wrong IMEI in SONY's selector, on its official page, which happens to have given its unlock code all quiet.
then the problem FAILED (remote: 'Command did not succeed')
can be translated as "I don't have the exact unlock code for your phone"
I did this to version 52.0.A.8.131 that I had installed before.
well OTHER PROBLEM!
it doesn't flash me twrp
with this error:
Sending 'recovery' (34192 KB) OKAY [0.737s]
Writing 'recovery' FAILED (remote: 'No such partition.')
I'm looking at guides.
Click to expand...
Click to collapse
Nice that it worked
Oh, the error is easy
It indicates "you didn't read the instructions' [emoji14]
MartinX3 said:
Nice that it worked
Oh, the error is easy
It indicates "you didn't read the instructions' [emoji14]
Click to expand...
Click to collapse
No means I'm blind as a mole, for a number
But now, following the instructions of the root of the zx3 H8416, they don't work
bibibabi said:
No means I'm blind as a mole, for a number
But now, following the instructions of the root of the zx3 H8416, they don't work
Click to expand...
Click to collapse
"Fastboot flash recovery twrp.IMG" aren't definitely the instructions dear blind mole
MartinX3 said:
"Fastboot flash recovery twrp.IMG" aren't definitely the instructions dear blind mole
Click to expand...
Click to collapse
Leave me pending? this is the command they say they use.
HTML:
fastboot flash recovery twrp.img
I know you can flash even with androxyed flash, but when you do ... it doesn't start anymore (the white sony script remained) ...
and I went a bit panicked !!!!
doing the Flash of the original firware it has been restored, but returned to the point of before. Install twrp.twp or superSU in short, activate the ROOT
the writing that says that the bootloader is corrupt, at start each time the cell terrifies me every time I see it. BRRRR
bibibabi said:
Leave me pending? this is the command they say they use.
HTML:
fastboot flash recovery twrp.img
I know you can flash even with androxyed flash, but when you do ... it doesn't start anymore (the white sony script remained) ...
and I went a bit panicked !!!!
doing the Flash of the original firware it has been restored, but returned to the point of before. Install twrp.twp or superSU in short, activate the ROOT
the writing that says that the bootloader is corrupt, at start each time the cell terrifies me every time I see it. BRRRR
Click to expand...
Click to collapse
If you corrupted the firmware, please use xperifirm & newflasher from XDA to reflash the firmware
Instructions are in the ROM section of the xz3 on XDA
MartinX3 said:
If you corrupted the firmware, please use xperifirm & newflasher from XDA to reflash the firmware
Instructions are in the ROM section of the xz3 on XDA
Click to expand...
Click to collapse
yes yes, I know that with the flash mode they can reinstall the official system.
there is also the official sony flastool called EMMA. which I have to say is not bad.
Now the system is ok, official.
I'm looking for ways to install root or twrp from a phone
bibibabi said:
yes yes, I know that with the flash mode they can reinstall the official system.
there is also the official sony flastool called EMMA. which I have to say is not bad.
Now the system is ok, official.
I'm looking for ways to install root or twrp from a phone
Click to expand...
Click to collapse
Should be impossible without a computer for initial installation
MartinX3 said:
Should be impossible without a computer for initial installation
Click to expand...
Click to collapse
yes, it's like you say.
Looking at the guides, I think the right solution for me is an official firmware kernel that has both twrp and magikic inside.
I found a guide of 2017, but the official firmware files have changed, I do not find myself in the guide.
Can't you recommend something to me, or the keywords to look for on this theme?
I wanted to learn to change the firmware for future root myself.
bibibabi said:
yes, it's like you say.
Looking at the guides, I think the right solution for me is an official firmware kernel that has both twrp and magikic inside.
I found a guide of 2017, but the official firmware files have changed, I do not find myself in the guide.
Can't you recommend something to me, or the keywords to look for on this theme?
I wanted to learn to change the firmware for future root myself.
Click to expand...
Click to collapse
I have sadly no time to do it and can only recommend the ROM section for the XZ3 in XDA (twrp)
MartinX3 said:
I have sadly no time to do it and can only recommend the ROM section for the XZ3 in XDA (twrp)
Click to expand...
Click to collapse
Each has its own spaces. do not worry. Meanwhile, I've made progress !!!
You know that after unblock I had problems installing TWRP.Practically the command gave error.
I found the solution around.
The guides say:
HTML:
fastboot flash recovery twrp.img
but I have this error:
HTML:
FAILED (remote: 'No such partition.')
basically in the version of android 9 they created 2 partitions and practically the recovery was divided into recovery ramdisck, recovery ...
They explain it HERE
In practice some new systems (I did not understand if the kelner or just the boot), do not have the active recovery partition and then flash the recovery, it is like doing it on a folder that does not exist.
So they recommend starting the mini twrp operating system via adb.
And through this active twrp (but not installed), install twrp itself, and then the apps for the root.
So, I use the new command that starts twrp without installing it:
HTML:
fastboot boot twrp.img
then it takes 3 minutes with the word sony and then I see twrp
I make a twrp backup for security
then from there I install .img used for the command and moved to the phone while twrp is active and I do install, install img and select partition recovery ramdisck.
I tried to install also in the boot partition, which shows in the list.
and apparently the cell works correctly anyway.
In the guides they never say in which partition to put.
Meanwhile there are install magisk 18.1 (and a zip called permissive; I don't know what it is but from the name it seems useful).
Well, everything is smooth and without errors.
Restart, I use the twrp access commands (which in the case of xz3 are volume DOWN + prower simultaneously while the phone is still off).
And the recovery is there, but it has the usual tuoch problem that doesn't work.
I see the twrp main screen, which seems to work correctly, but the touch ...
I then checked the root, via the app downloadable on the cell from the magisk manager repository and marks the correct root.
Obviously I don't update anything about 19.3, which you wrote in other places that is corrupt.
: Sciocco: NOW! I just have to fix twrp and my epic quest will be over.
(although I'm worried about flashing a hypothetical Q that's coming out)
can you give me some inspiration for the touch that doesn't work twrp?
bibibabi said:
Each has its own spaces. do not worry. Meanwhile, I've made progress !!!
You know that after unblock I had problems installing TWRP.Practically the command gave error.
I found the solution around.
The guides say:
HTML:
fastboot flash recovery twrp.img
but I have this error:
HTML:
FAILED (remote: 'No such partition.')
basically in the version of android 9 they created 2 partitions and practically the recovery was divided into recovery ramdisck, recovery ...
They explain it HERE
In practice some new systems (I did not understand if the kelner or just the boot), do not have the active recovery partition and then flash the recovery, it is like doing it on a folder that does not exist.
So they recommend starting the mini twrp operating system via adb.
And through this active twrp (but not installed), install twrp itself, and then the apps for the root.
So, I use the new command that starts twrp without installing it:
HTML:
fastboot boot twrp.img
then it takes 3 minutes with the word sony and then I see twrp
I make a twrp backup for security
then from there I install .img used for the command and moved to the phone while twrp is active and I do install, install img and select partition recovery ramdisck.
I tried to install also in the boot partition, which shows in the list.
and apparently the cell works correctly anyway.
In the guides they never say in which partition to put.
Meanwhile there are install magisk 18.1 (and a zip called permissive; I don't know what it is but from the name it seems useful).
Well, everything is smooth and without errors.
Restart, I use the twrp access commands (which in the case of xz3 are volume DOWN + prower simultaneously while the phone is still off).
And the recovery is there, but it has the usual tuoch problem that doesn't work.
I see the twrp main screen, which seems to work correctly, but the touch ...
I then checked the root, via the app downloadable on the cell from the magisk manager repository and marks the correct root.
Obviously I don't update anything about 19.3, which you wrote in other places that is corrupt.
: Sciocco: NOW! I just have to fix twrp and my epic quest will be over.
(although I'm worried about flashing a hypothetical Q that's coming out)
can you give me some inspiration for the touch that doesn't work twrp?
Click to expand...
Click to collapse
Please use the August .131 firmware and my matching stock twrp
Hi all,
It looks like questions about bricking tend not to get replies...
hard brick
So I tried to relock my BL and restore it to the stock so I could send my phone to the lab for a broken screen replacement. I flashed stock OS, it worked great, messed around with locking the BL with the flashtool, and all I left was restoring my...
forum.xda-developers.com
Hard bricked z3c?
Hi All, I think i have hard bricked my sony xperia z3 compact (d5803). My z3c had unlocked bootloader, was rooted and run on [ROM][5.1.1|STOCK][D5803|D5833] 23.4.A.1.264 SLiM 4.4, with twrp 2.8.7.0 as bootloader. Was doing a factory reset when...
forum.xda-developers.com
... but hey, it's just a post.
I copied the internal memory contents from one of my Z3Cs to another one and now the one that was overwritten does seems bricked.
The copy was done with basically:
Code:
new # dd if=/dev/block/mmcblk0 of=/external_sd/mmcblk0_new.dd
# backup
old # dd if=/dev/block/mmcblk0 of=/external_sd/mmcblk0_old.dd
# copy new:/external_sd/mmcblk0_new.dd to old:/external_sd/mmcblk0_new.dd
# overwrite
old # dd if=/external_sd/mmcblk0_new.dd of=/dev/block/mmcblk0
Power, Power + volume up or down, and camera buttons do nothing. If the phone is plugged in to charge off USB, the notification light slowly blinks red (it is in a pre-boot loop). If I hold the power button while it's plugged in, the notification light is solid red. Holding down other buttons doesn't change the behavior. I tried unplugging the battery and plugging it back in, but it made no difference. Plugging the phone into a PC doesn't show a USB device.
Why didn't it work? And, I guess, is it totally unrecoverable?
Download an older version of flashtool (0.9.18.6) because I couldn't get the newer versions to work and I flashed a stock kitkat rom: http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706 (Specifically the "23.0.A.2.93 - Unbranded - USA (1289-7524)" version - make sure you get the right version for your model). With this process, you don't need to turn your phone on. Just make sure you know how to use flashtool correctly.
Kenora_I said:
Download an older version of flashtool (0.9.18.6) because I couldn't get the newer versions to work and I flashed a stock kitkat rom: http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706 (Specifically the "23.0.A.2.93 - Unbranded - USA (1289-7524)" version - make sure you get the right version for your model). With this process, you don't need to turn your phone on. Just make sure you know how to use flashtool correctly.
Click to expand...
Click to collapse
Thanks, but flashtool requires a functioning USB interface on the phone, right?
Is there maybe some trick I haven't tried yet with the buttons that would make the phone present a USB interface to the host PC?
I'm on Linux using dmesg --follow so I'm certain that the host is not seeing a USB device appear. Nothing happens even if I hold the power button to get the solid red light behavior, but maybe I'm doing something out of order.
Have you installed the drivers for the phone?
you can't flash TA from one phone to another, if you saved it. might explain why
@ascendant512 Yes, what you did was foolish, and is totally unrecoverable (at least as far as anyone outside of Sony knows). The main flash chip itself that you entirely cloned bit-for-bit from one phone to another contains a bunch of data on it that is specific to that particular phone itself (not specific to just that model of phone, but specific to that unique, individual unit).
We don't 100% know exactly how it works, but that data is ciphered and is somehow tied to a serial# or IMEI# or something else that exists outside of the contents of main flash (probably somehow being used as the encryption key, or at least part of the key). If the two don't match up (the ciphered data stored on main flash and whatever it is being checked against outside of main flash), that data is indecipherable, the phone will not boot, and you are left with a brick. (The bootloader chain-of-trust is broken and it won't even kick over to a recovery mode.)
If you had instead cloned individual partitions (e.g., boot/kernel, system, userdata, etc.) rather than the entire flash chip, this could have been avoided. The specific partition that you cloned which ended up killing your target phone was the 'TA' partition. This is the one that has all of the critical, phone-specific data in it. If you overwrite/scramble/trash the contents of that partition (which would include taking a copy of TA from one phone and writing that copy to another phone of the same model), your phone is done for. We lack the knowledge or tools to re-generate the contents of that partition, and even if we didn't, you would likely need to de-solder the flash chip from the mainboard to write the corrected TA partition contents back to it.
@nira
I don't think it was that foolish since Google suggested that it does work for many Android phones, but thanks for the info about TA. It's much more helpful and informative than responding to "no dmesg" with "USB drivers"
I was trying to do this because the GPS doesn't work on one of the phones. I tried to clean the contacts of the antennae, but it made no difference, only ever picks up 0-3 satellites. Looks like I'm stuck buying a third Z3C to have working GPS.
ascendant512 said:
I don't think it was that foolish since Google suggested that it does work for many Android phones, but thanks for the info about TA. It's much more helpful and informative than responding to "no dmesg" with "USB drivers"
I was trying to do this because the GPS doesn't work on one of the phones. I tried to clean the contacts of the antennae, but it made no difference, only ever picks up 0-3 satellites. Looks like I'm stuck buying a third Z3C to have working GPS.
Click to expand...
Click to collapse
TA is a Sony "innovation" that you won't really find on other Android handsets (at least by that particular name).
Given how diverse the Android manufacturing ecosystem is, it's very tricky to extrapolate to a bunch of models (or even vendors) what might be true for a few, and thus, I would by nature be very hesitant to ever do a full-clone of seemingly-identical devices until I had first read up on and understood all of the intricacies of the *specific* model I was working with, because you never know what is easily undo-able and what isn't.
If you compare partition tables between different models of handsets, about the only commonalities when it comes to Android fixed-storage partition structure is 'boot', 'system', 'cache', and '[user]data'. There are typically tons of other various vendor-specific partitions storing who-knows-what data often with who-knows-what filesystems that (as your unfortunate particular story bears out) can be vital to the operation of the device as a whole. (It does seem foolhardy to me that manufacturers would choose to store those bits on the same storage medium as the rest of the system and user data, rather than in a separate ROM chip, but this is aggravatingly common in the world of embedded systems, probably as a cost-cutting measure...)
I *am* sorry for your loss, though...
So I've gone on adventure trying to prepare a new Z3C with working GPS and the adventure seems to have ended in failure.
I can describe some of the journey, and maybe there is advice on what bricked the phone or possibly a way to unbrick it as it is not in as poor condition as the previous one.
The phone arrived new in box with the Sony holographic stickers; I immediately followed the bootloader unlock procedure without any hiccups (to the best of my memory, it arrived with firmware 23.5.A.1.291).
The first failure was getting the phone to boot TWRP. For my previous z3c, this was the TWRP I used.
However, booting it with fastboot boot twrp-3.3.1-0.4-z3c.img
returns the error:
Code:
Booting FAILED (remote: 'dtb not found')
fastboot: error: Command failed
The device forums are sparse on this error, what it means, or how to fix it, but I'm used to TWRP being incredibly flaky. I did find that there is a combination of requirements from a kernel somewhere on the device which boots recovery requiring LZMA support, as it is the compression method for newer TWRPs.
The TWRP 3.2 from that post, as well as older TWRPs such as 3.1.1 were usable to boot, and led to the new phone's very brief peak operating state, in which I was able to flash and boot an old CarbonROM 5.1/Android 7 zip. However, TWRP 3.2 predates the phone's renaming from aries to z3c, and that version of TWRP would not flash the latest CarbonROM and Android 10.
From here, things only went downhill. Retrieving images from my Z3C which currently runs current CarbonROM, I overwrite the boot, FOTAKernel and userdata partitions from the old phone using a process like this:
Bash:
losetup --find --partscan --verbose backup.dd
dd if=/dev/loop0p14 of=backup_boot_14.dd
dd if=backup_boot_14.dd of=/dev/block/mmcblk0p14
Where backup.dd is a copy of mmcblk0 on the working phone and partition 14 is the one labeled "boot" in the GPT (16 is FOTAKernel and userdata is 25). The phone has never successfully booted into anything since, and these are some of the things I've tried to do to fix it:
Using Xperifirm 5.6.1 I downloaded firmware 3.5.A.1.291-R5D for US
Using flashtool 0.9.33.0 I assembled a ftf using the components "fotakernel.sin, kernel.sin and system.sin"
After flashing this group to the phone, it would boot loop the stock firmware (boot animation, freeze, reboot, do "optimizing apps", repeat). The stock firmware would also recognize my encrypted userdata and prompt to decrypt it until I used fastboot to clear the userdata partition.
That's the last time that flashtool worked, though. I later learned that there are preassembled ftfs that can be found, and got the one from this post:
[List][FTF] Stock Firmwares + Concept (18/10/2016)
Please, don't be lazy! If you've never flashed a "z3 compact" before, please read carefully all the warnings and the instructions for beginners. Before any question, read all the FAQs. Any suggestion is welcome! :) WARNINGS This process will...
forum.xda-developers.com
Whenever flashing anything to anywhere using flashtool, it spits out these errors:
flashsystem.X10FlashException: ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="80080021";
I haven't found anything anywhere that explains what these mean, or how to solve them.
I've tried checking and unchecking the various boxes in flashtool's flash mode that cause it to skip steps in the flashing process like so:
Flash the D5803_23.5.A.1.291_Customised_Nordic with default settings
When the first step fails out, restart the flash process
Uncheck the box for that step and let it start. It errors out on the next step
Repeat until only system is left that failed.
However, this does not seem to have accomplished anything productive. I also tried
fastboot flash:raw boot backup_boot_14.dd
and
fastboot flash boot boot.img (from CarbonROM's zip)
As well as the above with recovery and FOTAKernel from various TWRPs.
The phone isn't hard bricked, it boots into fastboot mode with vol+ and flash recovery mode with vol-. fastboot boot twrp.img has a few different behaviors depending on the TWRP version:
Nailyk's twrp_z3c_2019-03-13 from
https://www.reddit.com/r/LineageOS/comments/edwnzf
will boot to a black screen. No adb available.
The previously successful TWRP 3.2.3-0 without LZMA compression from NeoArian boots to a SONY logo notably without the Xperia logo on the bottom.
Newer versions of TWRP (3.3+) or lineage-18.1-20210914-recovery-z3c continue to fail with the "dtb not found" error.
It seems almost certain that the path to a working phone will be through flashing it back to stock using flashtool, but I don't see a way to make flashtool work or what is causing the errors.
Hi,
today I tried to flash TWRP on my XZ1 Compact to later install LineageOS on it, as the provider-supplied Android version is stuck at version 9.
I managed to unlock the bootloader and I followed this guide on TWRP.me to install TWRP.
All steps were successful, except the actual flashing of the recovery.
Meaning, that I could successfully list my device with `adb devices`, successfully boot into the bootloader with `adb reboot bootloader` (blue LED indicator, black screen), as well as successfully list the device with `fastboot devices` afterwards.
The final step though fails as follows:
Code:
sudo ./fastboot flash recovery twrp-3.6.1_9-0-lilac.img
Sending 'recovery' (33816 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed
After the above command failed, the phone seems to end the bootloader mode and returns to just charging via USB.
I tried this several times, but nothing changed.
I'd appreciate any help to get TWRP installed to be hopefully able to install LineageOS.
If there's any further information/details missing, please let me know.
EDIT:
I tried the above steps with ADB/Fastboot versions 33.0.1-8253317 and 33.0.2-855794 on a Linux machine with the same outcome.
Thanks a lot in advance!
SOLVED: For some reason switching to another laptop (with the exact same adb/fastboot files and TWRP) solved the problem.
Had the same f--ing thing. Google brought me to this post where a user solved it by trying out different laptops and USB ports. Thought it was nonsense, but tried it out on another laptop and it worked. BTW, adb's fastboot never worked on Windows for me due to some driver issue which apparently only concerns Xperias and I tried two different Linux distros before finally having success booting up EndeavourOS from a USB.
I have a Redmi 7 and for some reason this is the top result for my search of this exact problem for the redmi, so I'm going to post this here in hops it can help keep someone from banging their head against the wall like I have. And hopefully this method helps us out with Sony as well.
I tried 4 different PCs and I couldn't get mine to work.
However I did get it to work by manually rebooting into recovery after flashing twrp by holding the power + volume up buttons right at the fastboot screen and releasing the buttons after seeing the Redmi name.
To clarify:
Run fastboot flash recovery twrpname.img
Do not run "fastboot boot twrpname.img"
From the fastboot screen on your phone hold the power & volume up buttons until you see the Redmi name display
You will be in TWRP