Database Develop

[Q] Corrupted partitions?

Hello, I have a problem with my razr i xt890 and I can't find out the solution.
I had omar's rom (sept 2013 versions) on my phone (unlocked bootloader) and I tried to flash a new version using twrp but it stops/freezes when I wipe /system or /cache.
Also I can't mount /data.
I've tried with all recovery images from this thread [RECOVERY] New Installer for CWM / TouchCWM / TWRP / STOCK Recovery, but no luck.
I can get into fastboot and in recovery without problems, but I can't wipe the partitions.
Right now I'm trying to wipe /system, /data & /cache using cwm but it can't mount /data and it's stuck on formatting /cache.
Do you have any ideas?
Thank you.
[Details from fastboot]
AP Fastboot flash mode (secure boot)
20.25 (sha - )
IFWI Info: 42.26
eMMC Info: Size 8GB
Barcode: N/A
Battery (Okay): 4.09v
Transfer Mode: USB Connected
ROM-Key: Motorola-key
Modem Status: NA
C:\>fastboot getvar all
(bootloader) version-bootloader: 0x2025
(bootloader) product: smi
(bootloader) secure: yes
(bootloader) rom-key: motorola-key
(bootloader) model-id: 0268
(bootloader) cid: 7
(bootloader) version: 0.5
(bootloader) uid:
(bootloader) max-download-size: 104857600
(bootloader) emmc-size: 8GB
(bootloader) qe: qe 1/1
(bootloader) unlocked: yes
(bootloader) is-warranty-void: yes
(bootloader) ifwi: 42.26
(bootloader) cpu: Intel(R) Atom(TM) CPU Z2480 @ 2.00GHz
(bootloader) kernel: droidboot
(bootloader) battery: capacity: 73, voltage: 4053750, temperature: 290
(bootloader) modem-status: n/a

U could try to wipe the partitions through fastboot

I can't erase partitions from fastboot.
Output from device (fastboot)
read from /dev/block/mmcblk0 failed: I/O error
E:read_intel_version_from_mmc: Failed to read OSIP header from sector0!
E:Failed to read version for bos
read from /dev/block/mmcblk0 failed: I/O error
E:Failed to read partition gpt_main
I tried to flash the original rom from motorola with rsd lite but still no luck.
Can't write to mmc
I have also tried the solution from this thread http://forum.xda-developers.com/showthread.php?t=2184877, but still no luck
Is the internal sd card damaged/broken?

U did use JB versions of ifwi, motoboot and the other file? If so and it won't flash through the xfstk flasher, we can't help u. Sorry.

maybe you have to flash a stock rom with RSD lite, maybe with that, it'll be resolve...

I did flash with xfstk flasher successfully, but when i'm in fastboot the phone can't read or write to internal sd.
I have tried with rsd lite to flash the original but failed since the device can't write to the internal sd.
Any suggestions (or may I have to give up)?

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.

BLU R1 HD Boot Loop after OTA

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.

Can't Get USB Debugging / ADB to work WiN 7 32bit

Hi All not to sure what is going on but i'll try to explain as much as best as i can hopefully someone help i can get my phone to show up with usb debugging enabled windows device manager just shows it as R1 HD with a yellow " ! " forcing it to install as ADB interface does do much it installs but does not show in adb with "adb devices" phone has debugging turned on and ive installed android aio driver pack from androidmtk.com didn't help though im at a loss my computer recognizes the phone in mtp or ptp if i turn off usb debugging but like i said just shows up as R1 HD with an exclamation mark either way in device manager so im guessing its driver related but i can't find the right driver so i really would be grateful to get some help.
phone version : BLU_R0011UU_V17_GENERIC 15-11-2016 14:41
Build Number: MRA58K

Are you running Windows 7 or 10, 32 bits or 64 bits ? running MTK's usb drivers ? using the OEM Blu usb cable ? tried a different usb port ? Is your Settings > Security > Unknown Sources enabled or disabled - toggle it and reconnect, any difference ?
Check for possible usb drivers conflict, uninstall those & reboot and then try a fresh install, on a different port, with a different PS and/or OS, or a Linux machine (gotta loved my old Dell Laptop D410 with new life, as good as a Chromebook.) Look under Device Manager & check for hidden/unknown devices.

Letitride said:
Are you running Windows 7 or 10, 32 bits or 64 bits ? running MTK's usb drivers ? using the OEM Blu usb cable ? tried a different usb port ? Is your Settings > Security > Unknown Sources enabled or disabled - toggle it and reconnect, any difference ?
Check for possible usb drivers conflict, uninstall those & reboot and then try a fresh install, on a different port, with a different PS and/or OS, or a Linux machine (gotta loved my old Dell Laptop D410 with new life, as good as a Chromebook.) Look under Device Manager & check for hidden/unknown devices.
Click to expand...
Click to collapse
windows 7 32bit. mtk drivers and unknown sources are already enabled also for some reason oem unlock is not in the developer options it should be i thought on my current firm version..

darkensx said:
windows 7 32bit. mtk drivers and unknown sources are already enabled also for some reason oem unlock is not in the developer options it should be i thought on my current firm version..
Click to expand...
Click to collapse
Hmmm, is your bootloader locked or somehow got relocked after an OTA update/flash ?? How long have you owned this - rooted or not, rolled back the firmware ??
Do a manual reboot into bootloader (without using ADB) and post what those values are - especially about firmware, bootloader & unlock status ? pre-loader version ?
Backup any settings & important files on your R1 HD first, pull out any storage mSD card, do a factory reset - and - if you are sure that it is not bootloader LOCKED - download & run one of the dirty-cow-batch file (don't use the newest one as it didn't work on my other R1 HD now on the modified non-Prime version, was getting an error message when I tried to unlock & root it - one of the older one with the Linux option is what I used)
I then installed TWRP, flashed the modified factory rom, ran the debloat batch file also and flashed the latest SuperUser for good measure along with Busybox.

Letitride said:
Hmmm, is your bootloader locked or somehow got relocked after an OTA update/flash ?? How long have you owned this - rooted or not, rolled back the firmware ??
Do a manual reboot into bootloader (without using ADB) and post what those values are - especially about firmware, bootloader & unlock status ? pre-loader version ?
Backup any settings & important files on your R1 HD first, pull out any storage mSD card, do a factory reset - and - if you are sure that it is not bootloader LOCKED - download & run one of the dirty-cow-batch file (don't use the newest one as it didn't work on my other R1 HD now on the modified non-Prime version, was getting an error message when I tried to unlock & root it - one of the older one with the Linux option is what I used)
I then installed TWRP, flashed the modified factory rom, ran the debloat batch file also and flashed the latest SuperUser for good measure along with Busybox.
Click to expand...
Click to collapse
this phone i got second hand guy only had it 4 days i got it yesterday it was factory reset and afaik the phone was not ever modded, unlocked, rooted etc. is reconized in adb on my win 10 64 bit pc
as far as bootloader status these are the values produced from " 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!!
finished. total time: 0.202s

darkensx said:
this phone i got second hand guy only had it 4 days i got it yesterday it was factory reset and afaik the phone was not ever modded, unlocked, rooted etc. is reconized in adb on my win 10 64 bit pc
as far as bootloader status these are the values produced from " fastboot getvar all " :
(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!!
finished. total time: 0.202s
Click to expand...
Click to collapse
OK, from the last few lines - it indicated your device has an unlockable preloader/bootloader (yet to be done) and once it is, you can root it and install TWRP, and flash the "modified" stock ROM, i.e V2.85
See this thread/post - read the first page & last few pages about some of the discussion, use V10 of the tool - it worked on mine, and if it doesn't - try V8 also.
Make sure you installed & have working ADB and the MTK usb drivers (uninstall & reinstall)
https://forum.xda-developers.com/r1-hd/how-to/unlock-tool-t3561333
See this about running the batch file.
https://forum.xda-developers.com/r1-hd/how-to/blu-r1-hd-v6-6-dirtycowed-f-amazon-root-t3490882
Make a note of any error messages on screen. Have fun.

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.