Database Develop

[Q] Always cannot read android-info.txt on AT&T HTC One

The phone is used to reboot every 2 mins. Then I looked the articles here and try to fix it. But right now, I cannot flash the rom.zip to the phone.
Following are the steps I did:
1. s-off on the phone
2. installed ClockworkMod Recovery 6.0.5.1.
3. installed minimal_adb_fastboot
4. download superuser.zip and run CWM to install the file
5. downlaod the ElementX-m7-18.0-Sense.zip for Sense 6 Android 4.4.3 and run CWM to install the file
6. download the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2 rom
7. try to flash the rom after rebootRUU but always tell me cannot read android_info.txt
My current phone info:
ClockworkMod Recovery 6.0.5.1,
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -----------------
(bootloader) imei: ----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Other info:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-hoot 2047MB
Sep 10 2013.01:32:23.0
:crying::crying::crying:I don't know where i did wrong. Really need helps on it.:highfive:

Michael Xie said:
The phone is used to reboot every 2 mins. Then I looked the articles here and try to fix it. But right now, I cannot flash the rom.zip to the phone.
Following are the steps I did:
1. s-off on the phone
2. installed ClockworkMod Recovery 6.0.5.1.
3. installed minimal_adb_fastboot
4. download superuser.zip and run CWM to install the file
5. downlaod the ElementX-m7-18.0-Sense.zip for Sense 6 Android 4.4.3 and run CWM to install the file
6. download the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2 rom
7. try to flash the rom after rebootRUU but always tell me cannot read android_info.txt
My current phone info:
ClockworkMod Recovery 6.0.5.1,
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -----------------
(bootloader) imei: ----------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Other info:
***TAMPERED***
***UNLOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-hoot 2047MB
Sep 10 2013.01:32:23.0
:crying::crying::crying:I don't know where i did wrong. Really need helps on it.:highfive:
Click to expand...
Click to collapse
Well according to your getvar and the info shown in your bootloader your device is not s-off. Your still s-on so that ruu won't work for you anyway.
So what ever method you used to s-off apparently didn't work. And you need s-off to use that RUU.
However this RUU should work for you with s-on but you will need to relock your bootloader. And make sure you check the md5 of your download with this tool from www.winmd5.com
Correct md5 for this ruu is
Code:
5f121d72b8fa3f6f1704588467752605
http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Boot your device to the bootloader and connect fastboot usb. In the command window type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Make sure fastboot usb is connected then launch the ruu.exe on your pc.

Thanks a lot, I tried but after I launched the ruu.exe. It always display "htc_fastboot.exe is not working".

Michael Xie said:
Thanks a lot, I tried but after I launched the ruu.exe. It always display "htc_fastboot.exe is not working".
Click to expand...
Click to collapse
This is a visual c++ error I believe. Install this on your pc and try the ruu again http://www.microsoft.com/en-gb/download/details.aspx?id=29
---------- Post added at 06:58 AM ---------- Previous post was at 06:49 AM ----------
Alternatively you could use this RUU.zip
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
The procedure for flashing is a little more complex though.
Download the ruu.zip and put it in your fastboot folder and rename it to ruu.zip.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
you can skip this part if your already locked.
Code:
fastboot oem rebootRUU
--- case sensitive ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the ruu.
Code:
fastboot flash zip ruu.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip ruu.zip
The second flash will take a little longer and this time it will flash the full ruu. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader

I just installed and tried again. but it says some problem cause the application is not working correct. the htc_fastboot.exe is still not working. Do i need to reboot my system after installation?
-----------------------------------------------------------
I am trying the zip file. Thank you so much.

Michael Xie said:
I just installed and tried again. but it says some problem cause the application is not working correct. the htc_fastboot.exe is still not working. Do i need to reboot my system after installation?
Click to expand...
Click to collapse
Rebooting wouldn't hurt :good:

I got this message three times during the flash:
target reported max download size of 1526722560 bytes
sending 'zip' (1158208 KB)...
OKAY [ 37.747s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 161.040s
Have to go sleep. Thanks

Michael Xie said:
I got this message three times during the flash:
target reported max download size of 1526722560 bytes
sending 'zip' (1158208 KB)...
OKAY [ 37.747s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 161.040s
Have to go sleep. Thanks
Click to expand...
Click to collapse
use the .exe ruu that danny linked above (post #2), you can't use the decrypted ruu.zip (from post #4) with s-on.
Decrypted ruu = not signed by htc private key
s-on = must check htc signature before flashing
s-on + decrypted ruu = signature verification fail.
so with s-on you can only use signed ruu same or higher version
s-off: you can use signed and decrypted ruu, same, higher or lower version.

Michael Xie said:
Thanks a lot, I tried but after I launched the ruu.exe. It always display "htc_fastboot.exe is not working".
Click to expand...
Click to collapse
What version of Windows are you running on your pc?
Do you have HTC sync installed?
Is your SDK adb/fastboot up to date?
You can also try this ruu.exe http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/ , I'm not sure it will help with the fastboot error since I think that problem is pc side. But try it maybe the older installer will work with the c++ you installed previously. :good:

Michael Xie said:
Thanks a lot, I tried but after I launched the ruu.exe. It always display "htc_fastboot.exe is not working".
Click to expand...
Click to collapse
if you have htc sync installed, uninstall it (but don't uninstall the drivers)

The one Danny201281 gives to me works!!!!!
However, the phone goes back to keep rebooting after I installed the rom.
Need big help here.

Michael Xie said:
The one Danny201281 gives to me works!!!!!
However, the phone goes back to keep rebooting after I installed the rom.
Need big help here.
Click to expand...
Click to collapse
do a factory reset from stock recovery
when you get in recovery from the bootloader push volume up and tap power to see the menu

After I entered the "recovery", I saw following:
Android system recovery <3e>
Volume up/down to move highlight:
Enter button to select:
reboot system now
apply from sd card
apply from phone storage
apply from cache
wipe data/factory reset
wipe cache partition
I didn't see the mean you give to me....
HTC One 32 GB AT&T
Rolled Back to Android 4.3 Sense 5.5 / ARHD 53
Is there anyway for me to install brand everything if I unlock with s-on? Or is there anyway for me to change from s-on to s-off? I used the htcdev to unlock but it doesn't change the "s-on" to "s-off"..

I did "adb devices", it shows:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
This is correct or not?

Michael Xie said:
Just tried, still don't work. the phone is rebooting during the green "htc" screen.
Is there anyway for me to install brand everything if I unlock with s-on? Or is there anyway for me to change from s-on to s-off? I used the htcdev to unlock but it doesn't change the "s-on" to "s-off"..
Click to expand...
Click to collapse
You need the phone to boot to a Rom to gain s-off.
If these reboots continue after flashing the ruu was successful there's a good chance your problem is hardware related.
Best option now it to unlock the bootloader and flash a Custom Recovery and Rom. I would also recommend doing a data format before flashing the new Rom to ensure your partitions are free from corruption.

So I just wipe cache partition or wipe data/factory reset?

Michael Xie said:
I did "adb devices", it shows:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
This is correct or not?
Click to expand...
Click to collapse
You should see your phone serial number here. But this will only work if booted into a custom recovery like TWRP.
Michael Xie said:
So I just wipe cache partition or wipe data/factory reset?
Click to expand...
Click to collapse
If you have Stock recovery it would be best to factory reset with that first if you haven't already. Other wise just flash a Custom recovery

I did "fastboot -w" and got following message:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
Creating filesystem with parameters:
Size: 27917287424
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6815744
Block groups: 208
Reserved block group size: 1024
Created filesystem with 11/1703936 inodes and 150980/6815744 blocks
target reported max download size of 1526722560 bytes
Creating filesystem with parameters:
Size: 671084544
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2559
Label:
Blocks: 163839
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/40960 inodes and 5255/163839 blocks
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.003s
Is there something wrong here...

Phone write protected? Or freezed?

So in a preview attepmt to fix my phone , i discovered that dont mater what rom i flash, ether its via fastboot, or regular recovery or TWRP, phone always comes to the same state, even if i use the erase comands on fastboot, or try to format partitions on twrp, once i reboot the phone, it comes back to the original state, even pictures or music, stay there intact after delete them....
Wich leads me here to ask for some help again
My phone its an xt1063 ,the latest build, runing Blur_Version.21.11.23.titan_retug wich stops me from flashing another rom via stock recovery as there are no builds for 21.11.23. Its there something i can check to see if my phone its write protected or freezed? Thanks for your time and help .
Code:
C:\mfastboot-v2>fastboot getvar all > command.txt
(bootloader) version: 0.5
(bootloader) version-bootloader: 4807(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D3239LM
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: D59CBB060F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: Why its emei so important?
(bootloader) meid:
(bootloader) date: 10-23-2014
(bootloader) sku: XT1063
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Dec 2 3:44:40 UTC 2014"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retuglb/titan_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.85-23/21:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.23.titan_retug
(bootloader) ro.build.version.full[1]: lb.retuglb.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g668a77b ([email protected]
(bootloader) kernel.version[1]: ilclbld53) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Aug 26 20:21:50 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V48.07-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.07-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V48.07-0-g71b1aae-dirty
(bootloader) tz.git: git=MBM-NG-V48.07-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V48.07-0-ge875a20
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D3239LM
(bootloader) sutinfo:
all: listed above
finished. total time: 0.088s

so, am i doing it wrong? its there something i can do for someone to help me? are there anyone whos interested in such a weird problem? i know it dosnt happen often and at the same time, cant find nothing here or in google, thats why i dare to ask for help in here.
Thanks for your attention, but can anyone explain to me why im not getting any help? so i can fix it,thanks again.

Sorry man,I have no clue what is happening with your phone. Maybe it´s got something to do with writeprotection. Replying just to push your thread for some of the cracks around here can check this out?
All the best to you!

Wolfcity said:
Sorry man,I have no clue what is happening with your phone. Maybe it´s got something to do with writeprotection. Replying just to push your thread for some of the cracks around here can check this out?
All the best to you!
Click to expand...
Click to collapse
Glad is a problem thats not easy to fix than thinking im just being ignored im still trying things to see if i can fix it.
edit: i might be out of luck, i have the exact same problem as this guy http://forum.xda-developers.com/showthread.php?t=1967620 he did not found a solution, probably a hardware problem, but ill keep looking.

Same here

what have you tried?

I tried wiping everything through recovery, fixing permissions, formating partitions, wiping through bootloader, flashing stock kk with no result. When I first saw the problem I was like nah not big deal but no one has managed to solve it

Did you try?
adb shell
getprop ro.boot.write_protect
What is returned from this command 0 or 1?

Tonal4Nagual said:
Did you try?
adb shell
getprop ro.boot.write_protect
What is returned from this command 0 or 1?
Click to expand...
Click to collapse
i get
0

Then your system partition is not write protected.
Sent from my XT1068 using XDA Free mobile app

so for me, the only thing i was not being able to try, is to flash an original rom , even better, but i think it dosnt exists, flash the rom that the phone is asking for
Code:
phone has (motorola/titan_retuglb/titan_umts:4.4.4/KXB23)
i really have no idea wich original phone rom comes after that one. I tried to modify an original 5.0.2 rom
Code:
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US
modify the updater-script script to acept the current rom i have or even erase the part that checks it, but neither work, i get installation aborted. So if someone knows how to modify original roms ,pack them back again , and be able to flash via original recovery, that would be awsome so i can try one more thing.

You propably can't flash anything not original through stock recovery.
Sent from my XT1068 using XDA Free mobile app

i tried to unpack , found the string that checks for the version installed on the phone, modifed that in 3 files , metadata.gpb,metadata , and updater-script, repacked, and when i try to install, i get installation aborted.....

ried to format partitions as per instructed here http://android-revolution-hd.blogspot.mx/2013/10/fix-data-htc-one.html no luck...

so today i tried to install RETLA_XT1063_4.4.4_KXB21.85-24_cid12_CFC_SVC.xml via fastboot, and no go, i couldnt fin an origial rom for the same so i could try to install via original recovery, i also tried the philz recovery and tried to format partitions with it, and instal varius roms, with no luck. im running out of ideas at this point, but tomorrow maight get more, its just frustating that its been 5 days trying to resurect this phone.... any help or feedback from other members with the same problem would be apreciated,

looks like im along on this boat.....i tried a couple of more roms, no good outcome ...will keep looking...

abispac said:
looks like im along on this boat.....i tried a couple of more roms, no good outcome ...will keep looking...
Click to expand...
Click to collapse
do you have a twrp of original rom (even if it doesnt flash) i can figure out original rom from it and then find full firmware and TRY to make a easy installer for you - but i'm thinking this may fail too as im thinking corrupted partiton thats gonna need linux to fix

reefuge said:
do you have a twrp of original rom (even if it doesnt flash) i can figure out original rom from it and then find full firmware and TRY to make a easy installer for you - but i'm thinking this may fail too as im thinking corrupted partiton thats gonna need linux to fix
Click to expand...
Click to collapse
Do you have any suggestion for the storage? When I thry to format using fastboot I get tha raw format is not supported

xGiorgos said:
Do you have any suggestion for the storage? When I thry to format using fastboot I get tha raw format is not supported
Click to expand...
Click to collapse
what are you trying to format /system /cache /userdata ?

reefuge said:
what are you trying to format /system /cache /userdata ?
Click to expand...
Click to collapse
all of them

flashed wrong partition (gpt.bin) and other images

Problem: As after having the notification of latest update regarding stagefright exploit on my XT1052 RetailAsia version of moto x (2013), I downloaded a file named "ghost_retail_51_lpa2312-15_cid9_cfc.xml.zip", and tried flashing.
At first I started my flash-all.bat file which has all the command starting from "fastboot oem fb_mode_set" to "fastboot oem fb_mode_clear" which include commands for partition, system, boot, logo, recovery, modem, fsg, in between .(not in the order the same order as mentioned)
after all the commands done, i start checking the results from the first command, the first one i.e. fastboot oem fb_mode_set was quiet successfully done but starting from second command i.e., from fastboot flash partiton gpt.bin, all command shows same error i.e.
Code:
C:\Ajay\GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml>mfastboot flash partition gpt.
bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.265s]
writing 'partition'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.562s
my devices info got from fastboot getvar all
Code:
C:\Ajay\GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml>fastboot getvar all
INFOversion-bootloader: 30BE
INFOversion: 0.5
INFOcpu: MSM8960 Pro CS
INFOram: 2048MB Samsung S4 SDRAM DIE=4Gb
INFOemmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
INFOproduct: ghost
INFOrevision-hardware: 0x8300
INFOradio: 0x3
INFOsecure: yes
INFOmid: 026b
INFOserialno: TA6---30[COLOR="black"]X4[/COLOR]
INFOqe: qe 1/1
INFOunlocked: yes
INFOiswarrantyvoid: yes
INFOmax-download-size: 805306368
INFOuid: 4EABB2050C000100000000000000
INFOimei: 3532---5[COLOR="black"]13--9[/COLOR]9-
INFOmeid:
INFOsku: 000000000000000
INFOcid: 0x07
INFOiccid:
INFOdate: 04-27-2014
INFOcust_md5:
INFOreason: Key pressed
INFOro.build.date: Fri May 8 07:37:44 CDT 2015
INFOro.build.id: LPA23.12-15
INFOro.build.tags: release-keys
INFOro.build.type: user
INFOro.build.user: hudsoncm
INFOro.build.version.codename: REL
INFOro.build.version.incremental: 19
INFOro.build.version.release: 5.1
INFOro.mot.build.customerid: RETASIA
INFOro.product.name: ghost_retasia
INFOro.build.fingerprint[0]: motorola/ghost_retasia/ghost:5.1
INFOro.build.fingerprint[1]: /LPA23.12-15/19:user/release-key
INFOro.build.fingerprint[2]: s
INFOro.build.version.full[0]: Blur_Version.222.21.15.ghost_row
INFOro.build.version.full[1]: .AsiaRetail.en.03
INFOkernel.version[0]: Linux version 3.4.42-g030aaa2 (h
INFOkernel.version[1]: [email protected]) (gcc version
INFOkernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Fri M
INFOkernel.version[3]: ay 8 07:51:10 CDT 2015
now the phone doesn't booting up nor it is going into recovery|
A "No Command" photo with an Android image into it.
i got that file from Here ,
Please tell me what to do!
in my view i thought the file i got is not AsiaRetail version or possibly the file name indicates its a CID9 version and when i checked on my phone using "fastboot getvar cid" it shows mine is 0x07. i.e,
Code:
C:\Ajay\GHOST_RETAIL_5.1_LPA23.12-15_cid9_CFC.xml>fastboot getvar cid
cid: 0x07
finished. total time: 0.109s
While flashing partition gpt.bin it shows following message on bootloader screen
Downgrading security version
Update gpt_main version fail
Preflash validation failed for GPT

nexus 6 stuck in fastboot, unable to flash factory image IMEI set to zero's

Device is stuck in fastboot mode
screen shows
Device is LOCKED: Status code: 0
IMEI : 00000000000
SKU: 00000
Serial number shows values
Date being shown as 01-01-1970
Bootloader logs shows
fastboot reason: failed to initialize partition table
any advise on how to recover from this?

Fastboot erase userdata plus cache
Sent from my Nexus 6 using XDA-Developers mobile app

get error on erase
MacBook-Pro:~ user$ fastboot devices -l
994f3b10 fastboot usb:337641472X
MacBook-Pro:~ user$ fastboot erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.067s
MacBook-Pro:~ user$ fastboot erase userdata
erasing 'userdata'...
(bootloader) Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.066s
MacBook-Pro:~ user$

fastboot flash bootloader. Are you trying to flash N Preview?

reagan1998 said:
fastboot flash bootloader. Are you trying to flash N Preview?
Click to expand...
Click to collapse
my device was running fine with 5.1 and not sure what caused to get into this stuck where its stuck in fastboot boot
i am just trying to flash factory images from https://developers.google.com/android/nexus/images#shamu

Given the suddenness of your problem as well as the symptoms, I believe the internal memory has failed, meaning a service call. However, I hope I'm wrong.
Regardless, flashing factory images won't work because your bootloader is locked. Assuming this is a software issue you may be able to restore the system by sideloading the Android N OTA through recovery. If you can successfully do that, head to Developer Options in the N preview and enable OEM unlock. From there, unlock the bootloader, so you can flash factory images.

Strephon Alkhalikoi said:
Given the suddenness of your problem as well as the symptoms, I believe the internal memory has failed, meaning a service call. However, I hope I'm wrong.
Regardless, flashing factory images won't work because your bootloader is locked. Assuming this is a software issue you may be able to restore the system by sideloading the Android N OTA through recovery. If you can successfully do that, head to Developer Options in the N preview and enable OEM unlock. From there, unlock the bootloader, so you can flash factory images.
Click to expand...
Click to collapse
- I read some threads on sideload, they need device booted with adb access, since mine is stuck in fastboot, i don't have access to device via adb, would side load still work?
- still looking for zip for side load for nexus 6, if you have pointer for it, please let me know

To sideload the Android N OTA, which is the only thing that will help you here, you need to be able to get into recovery and set the recovery to adb sideload mode. If you cannot get into recovery, you definitely have a hardware problem and will need to get the internal storage chip replaced. As for the Android N OTA zip, check in the General subforum. Of course you could also simply do a quick Google search for "Android N OTA Brick" and get to Google's page of OTA zips that way.

Strephon Alkhalikoi said:
To sideload the Android N OTA, which is the only thing that will help you here, you need to be able to get into recovery and set the recovery to adb sideload mode. If you cannot get into recovery, you definitely have a hardware problem and will need to get the internal storage chip replaced. As for the Android N OTA zip, check in the General subforum. Of course you could also simply do a quick Google search for "Android N OTA Brick" and get to Google's page of OTA zips that way.
Click to expand...
Click to collapse
Android N has a new bootloader, so sideloading it will probably make the device not boot into Android.
---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------
Have you tried flashing a TWRP recovery and maybe flashing a custom ROM to see if it is a storage issue? This phone is not even two years old, it should not be having internal storage issues.

The Android N OTA I'm talking about includes the bootloader, as it is a full system image. Flashing TWRP will not work as the device has a locked bootloader. But since the device apparently has no partitions at all, the exercise I believe is moot. This is a hardware issue.

Run 'fastboot format cache' and 'fastboot format userdata', then run the most holy words in android 'fastboot oem unlock'. Check this: http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783 it really helped me out of a deep hole.

The only way that will work is if the OP enabled OEM Unlocking in Developer Options prior to the device forgetting its partitions. I hope he did, as having the option enabled doesn't affect the ability to get OTAs from Google. If however his device's EMMC chip failed as I believe, it won't help him resolve this issue.

reagan1998 said:
Run 'fastboot format cache' and 'fastboot format userdata', then run the most holy words in android 'fastboot oem unlock'. Check this: http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783 it really helped me out of a deep hole.
Click to expand...
Click to collapse
apologies for delayed response, i didn't realize there was second page in replies and you guys are still trying to help
here is outout
sh-3.2# fastboot devices
994f3b10 fastboot
sh-3.2# fastboot format cache
Formatting is not supported for filesystem with type ''.
sh-3.2# fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
sh-3.2# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-71.08(*)
(bootloader) product: shamu
(bootloader) board: shamu
(bootloader) secure: yes
(bootloader) hwrev: 0x83A0
(bootloader) radio: 0x6
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 3072MB Elpida S8 SDRAM DIE=6Gb
(bootloader) cpu: APQ8084 ES1.1
(bootloader) serialno: 994f3b10
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: 7858B30111000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git: sdi.git
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) aboot.git: git=MBM-NG-V71.08-0-g32b8854
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.040s
sh-3.2#

If it's failing to initialize the partition table, there's nothing you can do here. It needs to go to Motorola for warranty service.
EDIT: How I can tell? The date was set to 1/1/70. That's the beginning date of the Unix clock, which means something got screwed up internally. That plus the lost IMEI and the failure of the device to find its partitions means a bad device.
Sorry to be the bearer of bad news here, but this isn't something software can fix.

Strephon Alkhalikoi said:
If it's failing to initialize the partition table, there's nothing you can do here. It needs to go to Motorola for warranty service.
EDIT: How I can tell? The date was set to 1/1/70. That's the beginning date of the Unix clock, which means something got screwed up internally. That plus the lost IMEI and the failure of the device to find its partitions means a bad device.
Sorry to be the bearer of bad news here, but this isn't something software can fix.
Click to expand...
Click to collapse
Thanks for looking in, warranty must be void since i had open the back cover .

EDIT: Bad advice given.

Strephon Alkhalikoi said:
I would try anyway. The worst that will happen is they will want to charge you.
Click to expand...
Click to collapse
Which is considered fraud and not condoned by xda.

@zelendel: Echh. I'm not looking to get myself or XDA in trouble. I'll edit my post appropriately. Thank you for the reminder.

Strephon Alkhalikoi said:
@zelendel: Echh. I'm not looking to get myself or XDA in trouble. I'll edit my post appropriately. Thank you for the reminder.
Click to expand...
Click to collapse
Not a worry. I know a lot of people advise it but we don't condone it. This is why the disclosure in the OP of every rom thread. We accept what we do might mean killing our device and having to buy a new one. It's a risk of the hobby.

issues with fastboot

Just got a used xz1 compact. I've been rooting and flashing android phones for years, so I'm not a total noob. Nevertheless, I find myself a bit stuck on an issue I've never experienced before.
So, first step to me was to unlock the bootloader so that i can flash twrp and the unofficial lineage 16 from modpunk. So I do the usual thing of getting the code from the sony website, opening the dev-settings in the stock android and clicking "allow unlock", rebooting to fastboot mode and then:
Code:
$ fastboot oem unlock 0xCODEHERE
Well, so I didn't get what I expected. Instead of a success message, I got a message that said "command failed". But then, on a subsequent try, I got the message "already unlocked". Then, I tried a reboot, and I see a warning screen saying "device cannot be checked for for corruption, please lock bootloader". Then it enters the Xperia splash screen and never progresses. Well, that's not too big of an issue since I don't really want the stock ROM anyway. So I go ahead and try to flash twrp (modpunk's version for xz1 compact) and I get:
Code:
$ fastboot flash -v recovery twrp-3.3.1-0-lilac-pie-5.img
fastboot: verbose: target didn't report max-download-size
Sending 'recovery' (34548 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
So that's a bit discouraging. I also tried to see what I could find with "fastboot getvar all", and I was surprised that I couldn't even get any debugging info. The `devices` command seems normal, tho:
Code:
$ fastboot devices
XXXXXXXXX fastboot
$ fastboot getvar all
getvar:all FAILED (remote: 'GetVar Variable Not found')
Finished. Total time: 0.002s
Also related, I tried the sony flashtool, which I'm already familiar with because my old phone is a Z3 Compact (see, not my first rodeo). When I try to connect in fastboot mode with flashtool, the flashtool menu says "device connected in fastboot mode" followed immediately by "device disconnected". I notice that in the stderr from flashtool there's a message from libusb which is associated:
Code:
libusb_get_string_descriptor_ascii : I/O Errors
So, that's not encouraging. So, I wonder if the unlocking command ended up failing in a partially done way, leaving things broken. Let me know if you have ideas on what I might try next. One other note, I'm using the same laptop and usb ports that have worked in the past for flashing my z3 compact. The cable is a bit of an unknown though. I'm using the usb->usbc cable that came with the phone. But I've also just tried some of other usb cables I have around the house with an adapter for usbc.
A heads up, I'm on linux with no Windows machine available. I'm technically competent and I'd prefer detailed hypotheses to "try x". But I'm all ears. Anyone have ideas?
-----
Update:
I realized that there was a chance at least some of my issue was due to usb-c support in my kernel. So I built a 5.0 kernel and rebooted. The nice thing is that now `fastboot getvar all` is working. That's very encouraging. Here are the details:
Code:
(bootloader) hw-revision:20001
(bootloader) unlocked:yes
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4269
(bootloader) version-baseband:1308-8921_47.2.A.10.107
(bootloader) version-bootloader:1306-5035_X_Boot_MSM8998_LA2.0_P_114
(bootloader) erase-block-size: 0x1000
(bootloader) logical-block-size: 0x1000
(bootloader) variant:MSM UFS
(bootloader) partition-type:xblbak:raw
(bootloader) partition-size:xblbak: 0x3F5000
(bootloader) partition-type:xbl:raw
(bootloader) partition-size:xbl: 0x3F5000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x587D76000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x138800000
(bootloader) partition-type:vendor:raw
(bootloader) partition-size:vendor: 0x60000000
(bootloader) partition-type:oem:raw
(bootloader) partition-size:oem: 0x19000000
(bootloader) partition-type:rdimage:raw
(bootloader) partition-size:rdimage: 0x2000000
(bootloader) partition-type:fsmetadata:raw
(bootloader) partition-size:fsmetadata: 0x101000
(bootloader) partition-type:Qnovo:raw
(bootloader) partition-size:Qnovo: 0x1800000
(bootloader) partition-type:diag:raw
(bootloader) partition-size:diag: 0x2000000
(bootloader) partition-type:appslog:raw
(bootloader) partition-size:appslog: 0x1000000
(bootloader) partition-type:vbmeta:raw
(bootloader) partition-size:vbmeta: 0x10000
(bootloader) partition-type:frp:raw
(bootloader) partition-size:frp: 0x80000
(bootloader) partition-type:keystore:raw
(bootloader) partition-size:keystore: 0x80000
(bootloader) partition-type:misc:raw
(bootloader) partition-size:misc: 0x100000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x17C00000
(bootloader) partition-type:ssd:raw
(bootloader) partition-size:ssd: 0x2000
(bootloader) partition-type:fsc:raw
(bootloader) partition-size:fsc: 0x1000
(bootloader) partition-type:modemst2:raw
(bootloader) partition-size:modemst2: 0x200000
(bootloader) partition-type:modemst1:raw
(bootloader) partition-size:modemst1: 0x200000
(bootloader) partition-type:ddr:raw
(bootloader) partition-size:ddr: 0x100000
(bootloader) partition-type:FOTAKernel:raw
(bootloader) partition-size:FOTAKernel: 0x4000000
(bootloader) partition-type:logfs:raw
(bootloader) partition-size:logfs: 0x800000
(bootloader) partition-type:toolsfv:raw
(bootloader) partition-size:toolsfv: 0x100000
(bootloader) partition-type:limits:raw
(bootloader) partition-size:limits: 0x1000
(bootloader) partition-type:splash:raw
(bootloader) partition-size:splash: 0x20A4000
(bootloader) partition-type:dpo:raw
(bootloader) partition-size:dpo: 0x1000
(bootloader) partition-type:msadp:raw
(bootloader) partition-size:msadp: 0x40000
(bootloader) partition-type:apdp:raw
(bootloader) partition-size:apdp: 0x40000
(bootloader) partition-type:bluetooth:raw
(bootloader) partition-size:bluetooth: 0x100000
(bootloader) partition-type:boot:raw
(bootloader) partition-size:boot: 0x4000000
(bootloader) partition-type:dsp:raw
(bootloader) partition-size:dsp: 0x1000000
(bootloader) partition-type:modem:raw
(bootloader) partition-size:modem: 0x6E00000
(bootloader) partition-type:sec:raw
(bootloader) partition-size:sec: 0x4000
(bootloader) partition-type:fsg:raw
(bootloader) partition-size:fsg: 0x180000
(bootloader) partition-type:persist:raw
(bootloader) partition-size:persist: 0x2000000
(bootloader) partition-type:xflkeystorebak:raw
(bootloader) partition-size:xflkeystorebak: 0x20000
(bootloader) partition-type:xflkeystore:raw
(bootloader) partition-size:xflkeystore: 0x20000
(bootloader) partition-type:tzxflbak:raw
(bootloader) partition-size:tzxflbak: 0x80000
(bootloader) partition-type:tzxfl:raw
(bootloader) partition-size:tzxfl: 0x80000
(bootloader) partition-type:tzxflattestbak:raw
(bootloader) partition-size:tzxflattestbak: 0x80000
(bootloader) partition-type:tzxflattest:raw
(bootloader) partition-size:tzxflattest: 0x80000
(bootloader) partition-type:xflbak:raw
(bootloader) partition-size:xflbak: 0x1E00000
(bootloader) partition-type:xfl:raw
(bootloader) partition-size:xfl: 0x1E00000
(bootloader) partition-type:storsecbak:raw
(bootloader) partition-size:storsecbak: 0x20000
(bootloader) partition-type:storsec:raw
(bootloader) partition-size:storsec: 0x20000
(bootloader) partition-type:devcfgbak:raw
(bootloader) partition-size:devcfgbak: 0x20000
(bootloader) partition-type:devcfg:raw
(bootloader) partition-size:devcfg: 0x20000
(bootloader) partition-type:sti:raw
(bootloader) partition-size:sti: 0x200000
(bootloader) partition-type:cmnlib64bak:raw
(bootloader) partition-size:cmnlib64bak: 0x80000
(bootloader) partition-type:cmnlib64:raw
(bootloader) partition-size:cmnlib64: 0x80000
(bootloader) partition-type:cmnlibbak:raw
(bootloader) partition-size:cmnlibbak: 0x80000
(bootloader) partition-type:cmnlib:raw
(bootloader) partition-size:cmnlib: 0x80000
(bootloader) partition-type:keymasterbak:raw
(bootloader) partition-size:keymasterbak: 0x80000
(bootloader) partition-type:keymaster:raw
(bootloader) partition-size:keymaster: 0x80000
(bootloader) partition-type:devinfo:raw
(bootloader) partition-size:devinfo: 0x1000
(bootloader) partition-type:ablbak:raw
(bootloader) partition-size:ablbak: 0x180000
(bootloader) partition-type:abl:raw
(bootloader) partition-size:abl: 0x180000
(bootloader) partition-type:pmicbak:raw
(bootloader) partition-size:pmicbak: 0x80000
(bootloader) partition-type:pmic:raw
(bootloader) partition-size:pmic: 0x80000
(bootloader) partition-type:hypbak:raw
(bootloader) partition-size:hypbak: 0x80000
(bootloader) partition-type:hyp:raw
(bootloader) partition-size:hyp: 0x80000
(bootloader) partition-type:tzbak:raw
(bootloader) partition-size:tzbak: 0x200000
(bootloader) partition-type:tz:raw
(bootloader) partition-size:tz: 0x200000
(bootloader) partition-type:rpmbak:raw
(bootloader) partition-size:rpmbak: 0x80000
(bootloader) partition-type:rpm:raw
(bootloader) partition-size:rpm: 0x80000
(bootloader) partition-type:LTALabel:raw
(bootloader) partition-size:LTALabel: 0x1000000
(bootloader) partition-type:TA:raw
(bootloader) partition-size:TA: 0x200000
(bootloader) secure:no
(bootloader) serialno:XXXXXXXX
(bootloader) serial:1a322f75
(bootloader) product:G8441
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
So that seems like I did succeed at the unlocking. Now, I still can't seem to flash twrp:
Code:
$ fastboot -v flash recovery twrp-3.3.1-0-lilac-pie-5.img
fastboot: verbose: target reported max download size of 536870912 bytes
Sending 'recovery' (34548 KB) FAILED (Status read failed (No such device))
fastboot: error: Command failed
But things look normalish otherwise (max download size actually reported). And I still get libusb I/O error messages from flashtool when I tried to connect the device in fastboot mode while running flashtool. So, now my question has really morphed into help with this specific error. Why would it say "no such device"?
---
One more note: tailing /var/log/kern.log while doing the above (trying to flash recovery with fastboot), I can see that the device does reconnect. So I'm assuming that the "no such device" message is due to the disconnection. It's not clear to me if my troubles are due to kernel version, libusb version, cables/cable-types or something else. Looking forward to any advice.

Update (a second state acheived)
I managed to get the phone into some other mode (I guess what was called "flash mode" in other xperia devices). The indicator here is that the led is green instead of blue (fastboot). Well, it still seems to be some sort of fastboot mode, although quite a bit is different. For one thing, the device doesn't send its serial. In /var/log/kern.log I see:
Code:
Sep 22 21:53:11 kernel: [25251.575770] usb 1-1: Product: Android
Sep 22 21:53:11 kernel: [25251.575772] usb 1-1: Manufacturer: Sony
Sep 22 21:56:50 kernel: [25470.553359] usb 1-1: USB disconnect, device number 40
Sep 22 21:56:57kernel: [25477.008071] usb 1-1: new high-speed USB device number 41 using xhci_hcd
Sep 22 21:56:57 kernel: [25477.158020] usb 1-1: New USB device found, idVendor=0fce, idProduct=b00b, bcdDevice= 4.04
Sep 22 21:56:57 kernel: [25477.158025] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Then, fastboot itself says that the serial is a bunch of question marks:
Code:
$ fastboot devices
???????????? fastboot
Most interesting, now I get farther along the 'flash' command, instead of failing on 'Sending' with no such device, I see that the sending is "OKAY", but then the command to write fails as "unauthenticated".
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (34548 KB) OKAY [ 1.314s]
Writing 'recovery' FAILED (remote: 'Command not authenticated')
fastboot: error: Command failed
Also, now `getvar all` has different info:
Code:
fastboot getvar all
(bootloader) version:0.4-SONY-0.31
(bootloader) max-download-size:104857600
(bootloader) Version-sony:0.31
(bootloader) Loader-version:XFL-MSM8998-N-47
(bootloader) serialno:YYYYYYYY
(bootloader) version-bootloader:1306-5035_X_Boot_MSM8998_LA2.0_P_114
(bootloader) version-baseband:1308-8921_47.2.A.10.107
(bootloader) product:G8441
(bootloader) Phone-id:0000:XXXXXXXX
(bootloader) Rooting-status:ROOTED
(bootloader) Device-id:EDF6B4C3
(bootloader) Platform-id:2005E0E1
(bootloader) Frp-partition:frp
(bootloader) secure:no
(bootloader) Sector-size:4096
(bootloader) Ufs-info:SKhynix,H28U62301AMR,D003
(bootloader) Keystore-counter:1
(bootloader) Sake-root:D159
(bootloader) Default-security:eek:N
(bootloader) S1-root:S1_Root_e69c
(bootloader) Security-state:162509AE6B4B54D487F2496DDC4D4B6C6747A73B
(bootloader) USB-version:0x0200
(bootloader) slot-count:0
(bootloader) slot-suffixes:<empty>
(bootloader) current-slot:<empty>
all:
Finished. Total time: 0.107s
Also, in this mode, instead of just hanging if I retry the `oem unlock` command, it promptly replies that it's already unlocked.
Code:
$ fastboot oem unlock 0xBADHEAD
FAILED (remote: 'Bootloader already unlocked')
fastboot: error: Command failed
These seem like important clues. I'm looking for any tips parsing them

Rooting is not worth it anymore.
With any flashing there is the risk to damage the memory chips (because, you know, manufacturing defects, wearing out, etc). With old device the risk is even higher - and you won't have warranty anymore.
What I am saying is that you may have a (now) defective device.

bookworth said:
Rooting is not worth it anymore.
With any flashing there is the risk to damage the memory chips (because, you know, manufacturing defects, wearing out, etc). With old device the risk is even higher - and you won't have warranty anymore.
What I am saying is that you may have a (now) defective device.
Click to expand...
Click to collapse
Sure. It's possible that the device is defective. The purpose of this thread is to determine that. Do you have any experience which is relevant?
This is not about "rooting" in the traditional sense of owning uid 0 in Android. This is about installing a system which I'm comfortable using.

apexofservice said:
Sure. It's possible that the device is defective. The purpose of this thread is to determine that. Do you have any experience which is relevant?
This is not about "rooting" in the traditional sense of owning uid 0 in Android. This is about installing a system which I'm comfortable using.
Click to expand...
Click to collapse
I think you can obviously see that the device is old and both the offial and unofficial support has faded. It is just like flashing a Nokia E6 from 2011 today - noone cares. I know because I just did the Nokia thing.

@apexofservice, for flashing twrp image you need fastboot mode - blue led light (vol+ held while connecting to usb).
The other mode - green led light - is flash mode (Sony Service Mode) - there you can flash only sony signed stock firmware (like with newflasher all those .sin files).
I guess you troubles are most likely caused by some old version of 'fastboot' utility in your linux distro - are you using the version you've installed for modding your previous sony phone?
Or did you follow the sony unlocking guide and really installed the recommended fastboot utility version (as part of some android devel pack)?
To rule out flash error, you may try to just boot twrp without flashing it:
Code:
fastboot reboot bootloader
fastboot boot twrp.img
I wonder why so many people just unlock the phone without reading first?
You might have noticed, there is a drm keys backup method and do that first before unlocking...

j4nn said:
@apexofservice, for flashing twrp image you need fastboot mode - blue led light (vol+ held while connecting to usb).
The other mode - green led light - is flash mode (Sony Service Mode) - there you can flash only sony signed stock firmware (like with newflasher all those .sin files).
I guess you troubles are most likely caused by some old version of 'fastboot' utility in your linux distro - are you using the version you've installed for modding your previous sony phone?
Or did you follow the sony unlocking guide and really installed the recommended fastboot utility version (as part of some android devel pack)?
To rule out flash error, you may try to just boot twrp without flashing it:
Code:
fastboot reboot bootloader
fastboot boot twrp.img
I wonder why so many people just unlock the phone without reading first?
You might have noticed, there is a drm keys backup method and do that first before unlocking...
Click to expand...
Click to collapse
@j4nn: thanks so much for picking up the conversation. I realized what you said about green vs blue led and fastboot vs Sony Service mode sometime after my last post. But I didn't want to keep updating and just talking to myself so I held off. Still it's interesting that sony service mode is clearly based at least partially on the fastboot protocol.
In terms of which fastboot binary, I started by using the one I had installed from previous work with my z3c, that one is:
Code:
fastboot version 28.0.1-4986621
It was new enough not to have the -i $vendor_id option which is quoted in a bunch of guides for xperia stuff, and that's one of the things which lead me to try upgrading fastboot. Nowadays, it turns out, you can get the platform-tools without downloading the Sdk. So that download was quite convenient and I downloaded this version:
Code:
$ ./platform-tools/fastboot --version
fastboot version 29.0.4-5871666
I believe that's the latest fastboot, but let me know if it's not and if I should try to find something more recent. Actually, regarding fastboot, I ended up turning up the source code repo and found the README quite fascinating. I actually started using pyUSB to make a python version of fastboot, but that's a bit of an aside. In any case, I guess I could just compile fastboot from source. However, I suspect that the fastboot version isn't actually my issue.
Regarding booting from twrp using fastboot: Alas, that fails too. And, interestingly (perhaps), it fails in a similar way to the flash command. The phone seems to restart during or after the data send part:
Code:
./fastboot boot twrp-3.3.1-0-lilac-pie-5.img
Sending 'boot.img' (34548 KB) FAILED (Write to device failed (Cannot send after transport endpoint shutdown))
fastboot: error: Command failed
So then, given that the Green LED is Sony Mode, I thought maybe I should try to use FlashTool to try to reflash a working ROM/boot/kernel. So, I downloaded a stock ROM (same major version, Android 9 in my case), and then used the bundle command to prepare an FTF package.
Unfortunately, the version of FlashTool that I have doesnt' seem to be able to recognize the "flash mode" (green LED) that this phone provides. After preparing the firmware for flashing, it just says "phone connected with usb debugging disabled" when I connect it with Green LED. So, I figured that I needed to upgrade FlashTool. I found the lastest FlashTool and then tried to run it. But the jvm that comes with it seems to have been linked dynamically against a newer GLIBC than the one I have on this distro, so I started compiling a newer GLIBC into /opt but haven't gotten any farther before it was time to go work and set this aside for a while.
In terms of why I went straight to bootloader unlock instead of doing the firmware exploit to backup the TA keys, the main reason is as follows. The first is that I went through that exercise twice with my Z3C (I had two Z3Cs over the last 4 years), and it never ended up being useful. I never wanted to go back to stock, I never ended up caring about the DRM keys on the TA partition. So, I didn't really want to go through a bunch of hoops just to backup some keys that at this point it's clear that I'm not going to be using---I just wanted to get to the business of getting lineage up.
Please do post any further ideas or suggestions. I'd love any advice. Thanks in advance!

@apexofservice, instead of flashtool, just use newflasher to try to flash stock fw.
In linux you can ignore the pre-built binaries and just compile from source.
You may ignore even the prepared makefile and just use
gcc -o newflasher newflasher.c -lz -lexpat -ggdb
in order to use your system libs instead of those bundled.
Just do not use -O2 as that seams to cause flashtool segfault if compiled with -O2 with some recent gcc versions (there is probably a bug somewhere), -O0 resolves the segfault if it happens.

@apexofservice, xz1c sony flash mode init script contains this
Code:
# Increase min_free_kbytes to reduce risk of getting out of memory when doing USB read.
# The value 56766 was created by adding 12*4096 to the default value of 7614. I.e. we
# add 12 4MB buffers and this seems to be big enough for our use case.
write /proc/sys/vm/min_free_kbytes 56766
Maybe it is related also to your linux setup?
Could you test
Code:
echo 56766 > /proc/sys/vm/min_free_kbytes
before testing fastboot or newflasher?

Last update for now. I upgraded glibc and got to try out the lastest FlashTool. It's very cool that they've got XperiFirm integrated now. However, my situation is unchanged. When I go ServiceMode (Green LED), FlashTool says "Device connected with usb debugging disabled". When I connect with fastboot mode (Blue LED), i see a libusb error in stderr which says "libusb_get_string_descriptor_ascii : I/O Errors".
So, I guess I've tried all the tools now, and the device really is responding surprisingly to commands, it seems. I think I'm down to USB ports/cables. Unless people have other ideas.

Just saw your posts. Thanks for the quick reply.
j4nn said:
@apexofservice, xz1c sony flash mode init script contains this
Code:
# Increase min_free_kbytes to reduce risk of getting out of memory when doing USB read.
# The value 56766 was created by adding 12*4096 to the default value of 7614. I.e. we
# add 12 4MB buffers and this seems to be big enough for our use case.
write /proc/sys/vm/min_free_kbytes 56766
Maybe it is related also to your linux setup?
Could you test
Code:
echo 56766 > /proc/sys/vm/min_free_kbytes
before testing fastboot or newflasher?
Click to expand...
Click to collapse
FWIW, my system currently has 67584, so technically 56766 is a *decrease*. In any case, I tried it. Unfortunately, same output as previous:
Code:
./platform-tools/fastboot flash recovery twrp-3.3.1-0-lilac-pie-5.img
Sending 'recovery' (34548 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
Btw, where are you reading the source of that sony init script from?

j4nn said:
@apexofservice, instead of flashtool, just use newflasher to try to flash stock fw.
In linux you can ignore the pre-built binaries and just compile from source.
You may ignore even the prepared makefile and just use
gcc -o newflasher newflasher.c -lz -lexpat -ggdb
in order to use your system libs instead of those bundled.
Just do not use -O2 as that seams to cause flashtool segfault if compiled with -O2 with some recent gcc versions (there is probably a bug somewhere), -O0 resolves the segfault if it happens.
Click to expand...
Click to collapse
Cool, I actually did try newflasher already. I had compiled it from source (I had to change the source minimally because it has a hard-coded device id). After I changed that (to 0x0dde), I built it with `make`. I recompiled using your suggested `gcc` invocation and alas, same error as what I saw last time I tried it.
Code:
$ ./newflasher
--------------------------------------------------------
newflasher v18 by Munjeni @ 2017/2019
--------------------------------------------------------
Determining available free space:
Available space to caller = 114642 MB
Total space on current drive = 471964 MB
Free space on drive = 138685 MB
found device with vid:0x0fce pid:0x0dde.
Optional step! Type 'y' and press ENTER if you want dump trim area, or type 'n' and press ENTER to skip.
Do in mind this doesn't dump drm key since sake authentifiction is need for that!
n
- Error, no DATA reply!
End. You can disconnect your device when you close newflasher
I read in the fastboot README that that DATA reply is what's supposed to happen when the device reports that it's ready to read after and OKAY.
In fact, it was pretty easy to add the line `printf("%s\n", tmp_reply);" to the source code right after the line which is printing
"no DATA reply" and then I recompile and see:
Code:
- Error, no DATA reply!
FAILunknown command
So that's the same "unknown command" message that I'm seeing from the fastboot tool too. Shucks.

@apexofservice, your change of "hardcoded" device id does not make sense. The original device id in newflasher is all right.
Changing it to 0x0dde means you are trying to use newflasher in fastboot mode (i.e. idVendor=0fce, idProduct=0dde) which is indicated by blue led light. That will not work.
You need to use flash mode (green led light: idVendor=0fce, idProduct=b00b) with newflasher - no change in source needed.

apexofservice said:
In terms of why I went straight to bootloader unlock instead of doing the firmware exploit to backup the TA keys, the main reason is as follows. The first is that I went through that exercise twice with my Z3C (I had two Z3Cs over the last 4 years), and it never ended up being useful. I never wanted to go back to stock, I never ended up caring about the DRM keys on the TA partition. So, I didn't really want to go through a bunch of hoops just to backup some keys that at this point it's clear that I'm not going to be using---I just wanted to get to the business of getting lineage up.
Click to expand...
Click to collapse
You should know that even LOS16 is depending on stock heavily - my (a bit outdated) source build tree contains 467MB of stock fw proprietary binary blobs. Those blobs might still contain functions that depend on drm, like for example stock camera.
Another discussion about this topic with interesting links is in this thread:
j4nn said:
@Didgesteve, that "no one else seems to have noticed" - a rather big assumption of yours. There are many users complaining about xzp/xz1/xz1c camera quality in general.
But just with regard to oreo vs pie, read the xzp thread from here: post#27, particularly post#30 contains very interesting internal stuff.
I would like to believe sony stopped conditioning camera with keeping bootloader locked with pie but somehow I am not sure about that at all considering all the circumstances and my linked camera quality comparison test.
Thanks for your advice, luckily I do not need janjan's kernels as I've implemented the TA backup exploit, so both my phones can have drm keys restored (in fact one of them is still locked on purpose).
I (and anybody who saved TA-unlocked.img together with TA-locked.img) can switch easily between "drm keys restored" and "drm keys lost" states for testing/comparisons.
Click to expand...
Click to collapse

j4nn said:
@apexofservice, for flashing twrp image you need fastboot mode - blue led light (vol+ held while connecting to usb).
The other mode - green led light - is flash mode (Sony Service Mode) - there you can flash only sony signed stock firmware (like with newflasher all those .sin files).
I guess you troubles are most likely caused by some old version of 'fastboot' utility in your linux distro - are you using the version you've installed for modding your previous sony phone?
Or did you follow the sony unlocking guide and really installed the recommended fastboot utility version (as part of some android devel pack)?
To rule out flash error, you may try to just boot twrp without flashing it:
Code:
fastboot reboot bootloader
fastboot boot twrp.img
I wonder why so many people just unlock the phone without reading first?
You might have noticed, there is a drm keys backup method and do that first before unlocking...
Click to expand...
Click to collapse
Good news here is that I managed to finally properly use newflasher to flash a stock ROM (android 9) and boot into it. Hooray. Bad news is that I still get the same behavior as reported above when I try to flash twrp. As above, I can't even boot into it with `fastboot boot twrp.img`. Since I'm really not interested in using the stock ROM, I'd love advice on what I may need to try next in order to get a custom recovery working (and eventually, obviously, a custom ROM).

Had very similar issues - could only get to fastboot devices. Nothing else worked. Then I read that connecting through USB hub could work. Now fastboot getvar all works as well, managed to unlock the bootloader and flash TWRP...

bookworth said:
Rooting is not worth it anymore.
With any flashing there is the risk to damage the memory chips (because, you know, manufacturing defects, wearing out, etc). With old device the risk is even higher - and you won't have warranty anymore.
What I am saying is that you may have a (now) defective device.
Click to expand...
Click to collapse
Go take this garbage elsewhere, rooting and custom roms are very much worth it unless you like a crappy bloated stock rom. The devices are not defective nor is there any risk really as long as you're able to read. Way to waste the OP's time too and mine.
apexofservice said:
Good news here is that I managed to finally properly use newflasher to flash a stock ROM (android 9) and boot into it. Hooray. Bad news is that I still get the same behavior as reported above when I try to flash twrp. As above, I can't even boot into it with `fastboot boot twrp.img`. Since I'm really not interested in using the stock ROM, I'd love advice on what I may need to try next in order to get a custom recovery working (and eventually, obviously, a custom ROM).
Click to expand...
Click to collapse
Still having issues or did you figure it out?

Same for me after flashing the firmware. Issue solved.
I got the latest TWRP here: https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
Then I activated flash mode. (Phone off, volume down, then connect USB. The green LED is lit, otherwise black screen.)
Code:
fastboot reboot-bootloader
fastboot boot twrp-3.xxx.img
I Copied the TWRP image to the phone, then I used TWRP to install the TWRP image. (There is an option to install ZIP, which is default, or image.)

R3xXDA said:
Had very similar issues - could only get to fastboot devices. Nothing else worked. Then I read that connecting through USB hub could work. Now fastboot getvar all works as well, managed to unlock the bootloader and flash TWRP...
Click to expand...
Click to collapse
Using a USB hub was also the fix for me on an Xperia XA2 when flashing AOSP 9.0.