I got this used HTC one. I had google edition ROM on it when I got it. Then I flashed AR HD Rom on it. Everything was going fine till I decided to flash the latest firmware since I wanted to go to ARHD 30 and everyone seems to recommend to flash the new firmware.
I was going thru the normal steps and saw that I need to relock my device. I did this:
C:\Program Files\Android\sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.110s
After this I noticed that I had relocked written in fastboot mode even though it said failed. So tried the next step:
C:\Program Files\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.036s]
finished. total time: 0.040s
C:\Program Files\Android\sdk\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (28338 KB)...
OKAY [ 2.566s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.843s
And any step that I try it fails. The most unfortunate thing is I can only boot in fastboot & bootloader mode. I can't go in recovery neither can I boot normally. These are my phone details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(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: 4137mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.057s
I looked up online tried flashing recovery but now any step that I try to do in fastboot fails with following message:
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
I saw in some places people mentioned to use RUU. Not sure what it is but if some one can point me to a correct RUU or let me know any other steps it would be greatly appreciated. My phone is almost bricked now since i can't go past fastboot/bootloader.
awaitforitb said:
(bootloader) version-bootloader: 1.44.0000
Click to expand...
Click to collapse
You have no idea how lucky you are. Before you do anything, get S-OFF using revone. Just go into CWM (or re-flash recovery) so you can use adb. Once you have s-off, follow my guide :
This guide requires S-OFF​Important
*** If there are files you need to keep, you can always use adb pull to get them out before hand (let's say a nandroid backup or something important)
This guide assumes you have knowledge about how adb and fastboot command work and that your HTC drivers are up to date.
I am in NO WAY responsible for any possible damage that may happen to your phone, I am only trying to help
Start your phone in bootloader by typing
Code:
adb reboot bootloader
or by other means.
Select "Fastboot" so that it appears in red instead of HBOOT
On your computer, make sure fastboot sees your device, then type
Code:
fastboot erase cache
Type
Code:
fastboot erase cache
Type
Code:
fastboot erase userdata
Type
Code:
fastboot erase system
Type
Code:
fastboot erase linux
Type
Code:
fastboot erase recovery
Type
Code:
fastboot erase cache
Type
Code:
fastboot reboot-bootloader
Download the new firmware.zip
Type
Code:
fastboot oem rebootRUU
Once it's rebooted on a silver HTC logo, type :
Code:
fastboot flash zip [pathonyourcomputer/firmware.zip]
Wait until it is done on your computer. The green line on the phone will never reach the end.
Type
Code:
fastboot reboot-bootloader
Reflash your recovery (I recommend CWM). Might as well play it safe.
Code:
fastboot flash recovery [pathonyourcomputer/recovery.img]
Reboot into recovery (select the option in fastboot)
Wipe data/factory reset (you will loose everythng)
Select "Wipe Cache partition"
Select "Advanced -> Wipe Dalvik Cache"
Now you have 2 options :
Push (Preferred)
While in recovery, type
Code:
adb push [path/rom.zip] /sdcard/rom.zip
Select "Install zip"
Select "Choose zip from sdcard"
Voila ! You should be good to go !
Sideload (If you can't push for some reason)
Select "Install zip"
Select "Install zip from sideload"
Type
Code:
adb sideload [path/rom.zip]
Voila ! You should be good to go !
attanasi0 said:
You have no idea how lucky you are. Before you do anything, get S-OFF using revone. Just go into CWM (or re-flash recovery) so you can use adb. Once you have s-off, follow my guide :
Click to expand...
Click to collapse
@awaitforitb:
I agree with the S-Off part, just check the date of your bootloader it has to be pre June 2013. Also, in order for revone to work you need a functioning ROM (4.1.2... 4.3 will NOT work). Do you have one functioning device, or are you "stuck in bootloader" as the title says.
You could run the RUU found on androidruu http://www.androidruu.com/?developer=M7, I believe yours would be http://www.androidruu.com/getdownlo....20_10.40.1150.04_release_326691_signed_2.exe
That's an exe you run directly from your PC, and it will walk you through the steps, this will wipe your phone completely! and restore everything back to 100% stock.
After that you should get S-Off, and then proceed to whatever your end goal is.
@attanasi0 just a couple of questions, why do you recommend all the "fastboot erase userdata/linux/system/recovery" ?
Also, please remember that when using "fastboot flash zip <name of firmware>.zip", in most cases, you have to do it twice after each other, the first will push the zip and say "failed, flush image again" (or something along those lines), the second flash will actually start the installation and should report success.
I usually use firmwares from @vomer's guide: http://forum.xda-developers.com/showthread.php?t=2365506 as they have the dzdata files removed, as well as the stock boot.img and recovery.img removed.
nkk71 said:
@attanasi0 just a couple of questions, why do you recommend all the "fastboot erase userdata/linux/system/recovery" ?
Also, please remember that when using "fastboot flash zip <name of firmware>.zip", in most cases, you have to do it twice after each other, the first will push the zip and say "failed, flush image again" (or something along those lines), the second flash will actually start the installation and should report success.
I usually use firmwares from @vomer's guide: http://forum.xda-developers.com/showthread.php?t=2365506 as they have the dzdata files removed, as well as the stock boot.img and recovery.img removed.
Click to expand...
Click to collapse
You're about pushing the zip at first, forgot about that.
I honestly don't know why I recommend that. I guess it's to make sure the phone is a clean slate and no conflict will be created TL;DR : Paranoia
Hi there.
Well, my 802w (M7Cdug) is bricked. First it used to have this cycle of "turn on - work for a couple of minutes - restart - work for a couple of minutes", when I woke up next day after leaving it on cable I got this message of "decrypt storage, to start Android enter your password", of course whatever password I write it ends up with "pasword is correct, but data is corrupt", then it suggests to hard reset the phone. Doing that ends up with opening the Android system recovery with the following info in the log:
Code:
E:failed to mount /data (Invalid argument).. try emmc mount handle_cota_install: Can't mount /data/data/cwtemp/cwpkg.zi, 508056 times
Wiping cache partition (which is completed) and wiping data (which ends up with the same info and information on completion) does nothing.
Getting to the bootloader it says it's locked.
What else have I tried (I'm a real newbie in this topic so I might have done something absolutely stupid which couldn't have worked, but if you have any solution, please tell me):
* Unlocking: using the command "fastboot flash unlocktoken Unlock_code.bin" makes the phone show the "Unlock bootloader?" screen, choosing yes restarts it and makes it go back to the recovery screen, going back to the bootloader it's still locked.
* Moonshine S-OFF: ends up with "ERROR: run distiller again and READ"
* Minimal ADB and Fastboot & TWRP: the device is connected, doing the "fastboot flash recovery" ends up with "(bootloader) signature checking... FAILED (remote: signature verify fail)" and the "fastboot oem unlock" with "Command error".
* Minimal ADB and Fastboot & RUU: running "rebootRUU" ends up with phone again at the decrypt screen, getting it back there and running flash zip RUU.zip ends up with: signature checking / rom parsing start / rom parsing finish / FAILnot allowed / FAIL (remote: not allowed)"
I'm out of ideas - maybe I'm doing something wrong? If you guys have any idea what can help or if you'd like to help eg. via a TeamViewer I would be really thankful - having a $200 brick is not really satysfying, as well as having to use a shabby Xperia J with a broken screen as I can't afford anything new
If you need some info on what files should be used here's some stuff I got from fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: U3.19.3509.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.402.55
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4281mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d0e3b226
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Bump?
Like... seriously? Nothing can be done?
YacoobPL said:
Wiping cache partition (which is completed) and wiping data (which ends up with the same info and information on completion) does nothing.
Click to expand...
Click to collapse
* Unlocking: using the command "fastboot flash unlocktoken Unlock_code.bin" makes the phone show the "Unlock bootloader?" screen, choosing yes restarts it and makes it go back to the recovery screen, going back to the bootloader it's still locked.
Click to expand...
Click to collapse
* Minimal ADB and Fastboot & RUU: running "rebootRUU" ends up with phone again at the decrypt screen
Click to expand...
Click to collapse
These 3 symptoms make it sounds like your Emmc might be faulty
* Minimal ADB and Fastboot & TWRP: the device is connected, doing the "fastboot flash recovery" ends up with "(bootloader) signature checking... FAILED
Click to expand...
Click to collapse
You must have an unlocked bootloader to flash the recovery partition, it can't be unlocked so trying to flash recovery is useless, will not work.
"fastboot oem unlock" with "Command error".
Click to expand...
Click to collapse
fastboot oem unlock isn't a supported command on your model, on the GPE variant can be unlocked this way.
,
* Minimal ADB and Fastboot & RUU: running "rebootRUU" ends up with phone again at the decrypt screen getting it back there and running flash zip RUU.zip ends up with: signature checking / rom parsing start / rom parsing finish / FAILnot allowed / FAIL (remote: not allowed)"
Click to expand...
Click to collapse
Getting it back where? In bootloader? RUU can only be flashed when booted in RUU mode (black screen with silver HTC logo). If you're not booted at this screen, trying to flash RUU is useless, will not work.
If you guys have any idea what can help
Click to expand...
Click to collapse
The dual sim variant can be flashed using the external sd card. Rename the RUU file to "PN071IMG.zip" (watch out for souble file extension when renaming). Move the file at the root of your external sd card (must be formatted using FAT32), reboot in bootloader mode and you should be asked if you want to update. Btw what RUU were you using? With S-On you can only use the same (or newer) RUU than your version-main number (you're already on the newest version so only the 7.17.402.55 should work, hope you already have it cause I cant find this version).
Also the ouput of "fastboot oem dmesg" and "fastboot oem last_dmesg" might help determine any hardware failure.
On the Moto X subreddit you might have seen my post on how it came to this. Cant post it here though, because I'm a new user.
So here is the stuff copy pasted:
I'll start from the beginning to list what I did to the phone: Also, yes I'm new to this, so I did some dumdums along the way.
-Did the Moto unlock stuff(worked fine)(thanks tutorial, you didn't tell me this would wipe all my data till the end, I was already done by then)
-Installed TWRP 2.7something (the latest that the TWRP site recommended for this phone, worked fine)
-Used TWRP to install SuperSU/Root the phone(worked fine)
-tried installing cyanogenmod (failed, doesn't boot normally)
-reflashed everything to stock(worked fine, boot android 4.2.2)
-android loads updates, installs, fails to boot (bricked)
Here I am this is what my bootloader looks like:
AP Fastboot Flash Mode (S)
30.BE(*) (sha- blahblah
eMMC: 16gGB blah blah
...
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode: USB Connected
here comes the menue stuff
...
log looks like this:
downgraded security version
update gpt_main version failed
Failed to hab check for gtp_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Fastboot reason Invalid CID
USB connected
my fastboot recognizes the device I'm using the mfastboot v2 The Moto X is bought in EU (should be Moto X 1052)
I tried flashing it the same way I did for the reset, the way I did it before, but that doesn't work. I'm not exactly at the setup I actually used to do that with, I'll be able to try it that way again in 3 hours or so, but my setup should be about the same, cept that I'm using a USB3 connection right now instead of a USB2 (I read that ADB is having some problems there, but not that this is the case with fastboot) I've googled for a lot of solutions, non of them worked for me. I don't know what to do anymore.
Some things that might be of interest
mfastboot oem get_unlock_data
results in:
(bootloader) could not get unlock data! [Okay] finished...
Trying:
mfastboot flash partition gpt.bin
results in:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.269s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.174s
bootloader:
downgraded security version
update gpt_mail version failed
preflash validation failed for GPT
I usually get things done with trying around and normally(on other phones) I have no problem making a TWRP backup finding it! and pulling it from the phone so I can reset it within something like 15 mins, but I wasn't able to find where TWRP stored it's backups in this case, and I didn't care very much, not much on the phone to loose.
Anyone know what I could try?
E: Okay, just noticed that the codes in barcodes are different now:
IMEI/MEID: 0000000000000000
SKU: 000000000000
Serial Number: 13a869f1 (that's not the one it should be!!! My serial number should start with TA.... and not contain any lower case letters)
DATE: 01-01-1970
Click to expand...
Click to collapse
One more thing I did(because I found it in this forum) was mfastboot getvar all and got this back:
Code:
version-bootloader: 30BE(*)
version: 0.5
cpu: MSM8960 Pro CS
ram: 2048MB Samsung S4 SDRAM DIE=4Gb
emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
product: ghost
revision-hardware: 0x8300
radio: 0x3
secure: yes
mid: 026b
serialno: 13a869f1
qe:
unlocked: Not supported
iswarrantyvoid: Not supported
max-download-size: 805306368
uid: 2EED8B050C000100000000000000
imei: 000000000000000
meid:
sku: 000000000000000
cid: 0xdead
iccid:
date: 01-01-1970
cust_md5:
reason: Invalid CID
ro.build.date:
ro.build.id:
ro.build.tags:
ro.build.type:
ro.build.user:
ro.build.version.codename:
ro.build.version.incremental:
ro.build.version.release:
ro.mot.build.customerid:
ro.product.name:
ro.build.fingerprint:
ro.build.version.full:
kernel.version:
E: And no, I don't have a problem with the serial number showing here, in the getvar all, because as said in the text quoted from reddit, the stuff there is wrong anyway.
I am seeing the same error. Looking forward to any help to OP and me.
Hello,
I have an Amazon BLU R1 HD which I flashed with a standard OEM ROM based on the instructions in this forum, its been working great for months until I stupidly accepted an OTA (this one)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Since the update the device is stuck in a boot loop. I no longer have adb access to it (adb devices shows nothing) and I've tried to unlock the bootloader using SP Flash Tool and method 2 from here https://forum.xda-developers.com/r1-hd/development/r1-hd-amazon-bootloader-unlock-method-t3426104 but I just get a s_brom_download_da_fail error. I've tried on Windows and Linux, same results.
Can anything be done? Does anyone have any thoughts on this?
Thanks!
g00s3m4n said:
Hello,
I have an Amazon BLU R1 HD which I flashed with a standard OEM ROM based on the instructions in this forum, its been working great for months until I stupidly accepted an OTA (this one)
Since the update the device is stuck in a boot loop. I no longer have adb access to it (adb devices shows nothing) and I've tried to unlock the bootloader using SP Flash Tool and method 2 from here https://forum.xda-developers.com/r1-hd/development/r1-hd-amazon-bootloader-unlock-method-t3426104 but I just get a s_brom_download_da_fail error. I've tried on Windows and Linux, same results.
Can anything be done? Does anyone have any thoughts on this?
Thanks!
Click to expand...
Click to collapse
Since you had converted to OEM version. You most likely already had unlocked bootloader. Also when you take an ota with unlocked bootloader you end up with half re-locked bootloader and a boot loop.
We have already seen this in the forum , and have an easy solution.
But to verify the situation before making changes do this:
Hold volume up while phone is boot looping. it should eventually go to the boot menu. Select fastboot. Connect to your pc.
Open cmd window. type this "fastboot devices" you should get almost instant response. " *your serial number* fastboot"
now that you verified you have the connection type this "fastboot getvar all" the response is a list of partitions then near the end there is the bootloader status
"unlocked = yes"
and
"secure = yes"
if this is true then my assumption is correct. It should be "secure = no" for an unlocked phone.
Now type "fastboot oem unlock" followed by volume up button on phone.
follow that with "fastboot format userdata"
obviously this will factory reset your phone.
mrmazak said:
Since you had converted to OEM version. You most likely already had unlocked bootloader. Also when you take an ota with unlocked bootloader you end up with half re-locked bootloader and a boot loop.
We have already seen this in the forum , and have an easy solution.
But to verify the situation before making changes do this:
Hold volume up while phone is boot looping. it should eventually go to the boot menu. Select fastboot. Connect to your pc.
Open cmd window. type this "fastboot devices" you should get almost instant response. " *your serial number* fastboot"
now that you verified you have the connection type this "fastboot getvar all" the response is a list of partitions then near the end there is the bootloader status
"unlocked = yes"
and
"secure = yes"
if this is true then my assumption is correct. It should be "secure = no" for an unlocked phone.
Now type "fastboot oem unlock" followed by volume up button on phone.
follow that with "fastboot format userdata"
obviously this will factory reset your phone.
Click to expand...
Click to collapse
Thank you, your assumption was correct and that has fixed the problem. Obviously my search foo failed me.
I appreciate the quick reply and assistance.
mrmazak said:
Since you had converted to OEM version. You most likely already had unlocked bootloader. Also when you take an ota with unlocked bootloader you end up with half re-locked bootloader and a boot loop.
We have already seen this in the forum , and have an easy solution.
But to verify the situation before making changes do this:
Hold volume up while phone is boot looping. it should eventually go to the boot menu. Select fastboot. Connect to your pc.
Open cmd window. type this "fastboot devices" you should get almost instant response. " *your serial number* fastboot"
now that you verified you have the connection type this "fastboot getvar all" the response is a list of partitions then near the end there is the bootloader status
"unlocked = yes"
and
"secure = yes"
if this is true then my assumption is correct. It should be "secure = no" for an unlocked phone.
Now type "fastboot oem unlock" followed by volume up button on phone.
follow that with "fastboot format userdata"
obviously this will factory reset your phone.
Click to expand...
Click to collapse
confirmed working. one more phone has been saved. Thanks!
OEM version - boot loop
My BLU R1 HD from Amazon, is stuck at reboot. I have not made any changes to the ROM except OTA updates.
I have provided the fastboot getvar all - details below.
Kindly guide me how to unbrick the phone. I am not looking to root the phone. Thanks in advance.
The values are different from what you had mentioned above
(bootloader) unlocked: no
(bootloader) secure: yes
C:\>fastboot devices
4SPFSKDUOVQWMBFE fastboot
C:\>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
I ran the unlock bootloader and it fails as well
C:\>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 90.128s
praxtwin said:
My BLU R1 HD from Amazon, is stuck at reboot. I have not made any changes to the ROM except OTA updates.
I have provided the fastboot getvar all - details below.
Kindly guide me how to unbrick the phone. I am not looking to root the phone. Thanks in advance.
The values are different from what you had mentioned above
(bootloader) unlocked: no
(bootloader) secure: yes
C:\>fastboot devices
4SPFSKDUOVQWMBFE fastboot
C:\>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
I ran the unlock bootloader and it fails as well
C:\>fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 90.128s
Click to expand...
Click to collapse
Don't have any proven information to give you in your situation. All previous boot loops after taking an OTA have been a result of already having bootloader unlocked.
I would normally suggest trying to do a factory reset in a boot loop situation . So if you can get into recovery mode try to do a reset. If you cannot get into recovery you can try to do a "fastboot format userdata" and / or. "fastboot format cache"
mrmazak said:
Don't have any proven information to give you in your situation. All previous boot loops after taking an OTA have been a result of already having bootloader unlocked.
I would normally suggest trying to do a factory reset in a boot loop situation . So if you can get into recovery mode try to do a reset. If you cannot get into recovery you can try to do a "fastboot format userdata" and / or. "fastboot format cache"
Click to expand...
Click to collapse
Thanks for your suggestion. Unfortunately, Recovery mode doesn't seem to work. I did Factory reset , and then reboot, it stays on white BLU screen.
Additional Info: I did a ROOT INTEGRITY CHECK. It fails stating several files modified. I am not sure if that is an indication of any problems.
So I fastboot'ed again and tried format userdata and cache.
Both result in Failure - Not Allowed.
C:\>fastboot format cache
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
target reported max download size of 134217728 bytes
erasing 'cache'...
FAILED (remote: format for partition 'cache' is not allowed
)
finished. total time: 0.005s
Is this because I do not have ROOT access, that I am not able to format?
Do you think there is anything I could do to get the phone working again. Appreciate your help so much.
praxtwin said:
Thanks for your suggestion. Unfortunately, Recovery mode doesn't seem to work. I did Factory reset , and then reboot, it stays on white BLU screen.
Additional Info: I did a ROOT INTEGRITY CHECK. It fails stating several files modified. I am not sure if that is an indication of any problems.
So I fastboot'ed again and tried format userdata and cache.
Both result in Failure - Not Allowed.
C:\>fastboot format cache
Creating filesystem with parameters:
Size: 419430400
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1600
Label:
Blocks: 102400
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/25600 inodes and 3310/102400 blocks
target reported max download size of 134217728 bytes
erasing 'cache'...
FAILED (remote: format for partition 'cache' is not allowed
)
finished. total time: 0.005s
Is this because I do not have ROOT access, that I am not able to format?
Do you think there is anything I could do to get the phone working again. Appreciate your help so much.
Click to expand...
Click to collapse
You are not allowed to format from fastboot because , not bootloader unlocked. So not unlocked, no custom recovery, and integrity check says system files are changed.
It is most likely end of line for that device. Only option I can think of is factory repair. Phone must be less than 1 year old. (released July 2016) They have 12 month warranty I believe.
I have the Amazon R1 HD and I too fell victim to the update install that relocked my phone so its stuck in the reboot format. My problem seems to be when attaching my phone to the computer as instructed previously to another Blu...after typing in "fastboot devices" I receive an error code stating the Android device has no drive. I am almost past exasperated. Help, please!
Please help
I tried the spitting flash tool method to get my phone out of bootloop it won't work because I can't turn it off. It's battery has to die out then when I plug it. It automatically goes to the BLU screen and stays there for a bit then powers off and turns on again. I tried plugging it in to my pc and using fastboot devices but I get this error.
'Fastboot' is not recognized as an internal or external command operable program or batch file
And I can't power it off to begin the flash every time I get a timeout and I have all the mtk drivers install and the MT65xx USB vcom drivers I'm so confused I have a week working on this issue
Ghost0711 said:
I tried the spitting flash tool method to get my phone out of bootloop it won't work because I can't turn it off. It's battery has to die out then when I plug it. It automatically goes to the BLU screen and stays there for a bit then powers off and turns on again. I tried plugging it in to my pc and using fastboot devices but I get this error.
'Fastboot' is not recognized as an internal or external command operable program or batch file
And I can't power it off to begin the flash every time I get a timeout and I have all the mtk drivers install and the MT65xx USB vcom drivers I'm so confused I have a week working on this issue
Click to expand...
Click to collapse
You are throwing a lot of different things together, but sounds like none of the steps are right.
If you have been stuck in a boot loop after an OTA update (like title of thread you are in) , and your phone was bootloader unlocked before taking the OTA update, then the following information should help.
If you are in a boot loop for other reason then this will not help.
While the phone in Turing on / off, hold volume up. Eventually it should come to the boot select screen. Use volume button to scroll to fastboot and power button to select.
Now plug usb into pc and open CMD window. Verify you have the fastboot program on pc, and it sees phone by typing "fastboot devices"
Your statement said you got response that fastboot was not recognized command. I suspect you may not have fastboot on pc, but it no fastboot on pc how did you unlock bootloader?
Moving on., Once you have fastboot recognizing the phone , type "fastboot oem unlock"
Should be message on phone screen asking to confirm by pushing volume up.
Next , if phone has stock recovery you can just reboot and stock recovery will wipe /data and phone should reboot.
If phone has custom recovery (twrp) need to format userdata and cache. Type "fastboot format userdata" then "fastboot format cache"
And again I must state that if phone is boot looping for other reasons then this may not help.
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.