Hi all,
my Tab Z2 (LTE) freezed during operation so I turned it off (Power + Vol Up) and it vibrated 3 times
When turning it on I only see the Sony Logo but that´s it
I´m not able to access TWRP (TWRP is flashed and AICP 14) as it won´t boot that far that the LED starts to blink.
So I tried to flash TWRP via fastboot again - no success
I tried to flash boot.img via fastboot again - no success
Tried different files (to exclude a courrpted file) and tried a second laptop (to exclude driver issues)
The error which I get is the following:
FAILED (remote: flash write failure)
Anyone an idea what is causing this issue and how to solve it?
My assumption is that my Tab Z2 flash is broken!?
Regerads
UserX10
Related
hello,
part 1
I will start by that the LG G3 I got from a neighbor and she did not exactly know what her boys do to the device :angel:
I do not know if the device was in debugging mode and ROOT so I will describe the current situation:
1 If you turn on the device is stuck the logo of LG
2 he can get into a normal recovery, but after I perform Clear / Reset is back to being stuck in the logo.
3- When I try to enter download mode he entered to fastboot mode Started and wait for fastboot Processsing command.
4- My computer installed SRKtool_2.1 droidth and SRKtool_1.0.5_droidth, as well as SDK is updated.
5- I tried to make various adjustments through SRKtool and via fastboot command, the file (*.bin\*.img) send to the device from the PC but faild to write them, and I get messages:
sending laf "okay"
writing laf "failed (remote: flash write failure)
all file have the same masssage.
I try to perform repair to:
A- fastboot mode Started
B- recovery mode
from srktools and I got the same write fail massage !
He's trying to re-write the BIN files taking off from the original rom,
again he can transfer files but does not actually write the on the device,
then the device restarts and then he stuck the logo of TWRP, the expense of battery re-enters the regular recovery mode.
part 2 Updated!
From time to time the device did not enter the FASTBOOT MODE and gets to the firmware update, I install a new ROM, but !!!
the operating system install LGE Android MTP Device driver,
when I flash the rom he stack on 3% and the hardware driver turn to yellow with code 10 (device not work properly).
does LGE Android MTP Device have to be install to do the FLASH ???
the MPT can be damage and that cause the problem ?
the same problem on 2 different PC & OS (xp/7/10) with different drivers for MPT,
after you restart the mobile it returns to FASTBOOT MODE
Hi,
I got my Oneplus X three days back and when booted, the first thing it showed was to update the phone. When I clicked on download, it did download and asked me to install. When I clicked install, it restarted the phone and stayed at "1+" logo for ever without updating or restarting the phone. When I force restarted it (10 seconds power hold), it started, but the update was not applied. I did not have any other option, but to return the phone for a replacement.
Yesterday I received the replacement and to my surprise, it still does not update and stays on the same "1+" icon. To set things right, I thought of installing TWRP and reflash the bootloader, or better install any custom ROM's. While installing TWRP, I unlocked the bootloader and the result was:
Code:
J:\Mobile\Minimal ADB and Fastboot>fastboot oem unlock
...
OKAY [ 0.011s]
finished. total time: 0.012s
Once unlocked, it goes back into its own weird "1+" icon and stays there (exiting from fastboot mode). Then when I try to boot into twrp, it says:
Code:
J:\Mobile\Minimal ADB and Fastboot>fastboot boot twrp-2.8.7.0-onyx.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.498s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.498s
Should I now send this device back assuming that this is also a buggy phone, or is there solution to this? Kindly help.
I too have the same device but never came across this prob. Better you replace asap!
Just flash TWRP Recovery and install full 2.1.3 ROM. Do not try to boot it.
bioan said:
Just flash TWRP Recovery and install full 2.1.3 ROM. Do not try to boot it.
Click to expand...
Click to collapse
Thanks for the response guys. Problem solved!
For those of you who are in any case facing this problem, the issue was with SD Card. I removed the SD card (which was formatted using my previous Galaxy S3) and tried updating it and it worked. Now, I formatted the SD card and tried again and I was able to get into bootloader mode.
Hi
I used my Xiaomi Redmi Note 3, 3GB RAM, 32GB new phone first day yesterday.
When I went to sleep it was 92% charged and when I woke up it was stuck on the Xiaomi loading screen. I let it on that screen for about 3 hours before I restarted it.
It's unable to boot into normal mode, and when I try to get into recovery mode it just shows a screen to connect a cable.
When I connect the cable to the computer it shows that the cable is connected but nothing happens after this.
If I boot the phone in fastboot and use Mi PC Suite to try to flash it, it just tells me to reboot in normal mode and try again.
If I hold all 3 buttons I have managed to get into some test mode, but from there I can't do anything.
How can I reset or get into my phone again? Is this normal behaviour after just one day use?
Johanna12221 said:
Hi
I used my Xiaomi Redmi Note 3, 3GB RAM, 32GB new phone first day yesterday.
When I went to sleep it was 92% charged and when I woke up it was stuck on the Xiaomi loading screen. I let it on that screen for about 3 hours before I restarted it.
It's unable to boot into normal mode, and when I try to get into recovery mode it just shows a screen to connect a cable.
When I connect the cable to the computer it shows that the cable is connected but nothing happens after this.
If I boot the phone in fastboot and use Mi PC Suite to try to flash it, it just tells me to reboot in normal mode and try again.
If I hold all 3 buttons I have managed to get into some test mode, but from there I can't do anything.
How can I reset or get into my phone again? Is this normal behaviour after just one day use?
Click to expand...
Click to collapse
Flash aboot it will ok..
Hi and thanks for your reply!
By running fastboot getvar product I found out that I have the "special edition" model, kate.
I have now downloaded this:
kate_global_images_6.9.8_20160805.0000.29_6.0_global_042c784ac4
After unpacking and trying to flash I get this:
Code:
fastboot flash tz C:\kate\kate\images\tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (637 KB)...
OKAY [ 0.023s]
writing 'tz'...
FAILED [B](remote: Critical partition flashing is not allowed)[/B]
finished. total time: 0.032s
"Flash tz error"
Johanna12221 said:
Hi and thanks for your reply!
By running fastboot getvar product I found out that I have the "special edition" model, kate.
I have now downloaded this:
kate_global_images_6.9.8_20160805.0000.29_6.0_global_042c784ac4
After unpacking and trying to flash I get this:
Code:
fastboot flash tz C:\kate\kate\images\tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (637 KB)...
OKAY [ 0.023s]
writing 'tz'...
FAILED [B](remote: Critical partition flashing is not allowed)[/B]
finished. total time: 0.032s
"Flash tz error"
Click to expand...
Click to collapse
By looks of it, you have a locked bootloader and hence, are unable to flash fastboot files. The only way for you to make your device usable again is to somehow boot into the 'edl' mode and use MiFlash to falsh the fastboot ROM from there.
Hi! Thanks for your reply.
I didn't do anything to the bootloader, so yeah it should be locked.
I will contact the store I bought it from and try to get it returned.
So sad to have made this purchase. I hope I can find another phone, perhaps one that is not as cheap as this.
Hi again!
I have kept trying to solve this issue further. I'm able to get into edl mode using the modified fastboot that I found here on the forums with "fastboot reboot-edl".
I managed to run MiFlash 2016.04.01 (important, newer version didn't work!)
But it still seems to be stuck in just an endless Android loading screen. Anything else I can try?
Johanna12221 said:
Hi again!
I have kept trying to solve this issue further. I'm able to get into edl mode using the modified fastboot that I found here on the forums with "fastboot reboot-edl".
I managed to run MiFlash 2016.04.01 (important, newer version didn't work!)
But it still seems to be stuck in just an endless Android loading screen. Anything else I can try?
Click to expand...
Click to collapse
I can help you. Talk me in PM.
Hi!
Thanks for offering your help, andersonaragao.
I finally got it to work by doing a "Flash all" of the MIUI 8 package.
So the steps so solve was just this easy:
Boot in fastboot (Volume down + power)
Make sure you have kenzo or kate (fastboot getvar product)
Get correct fastboot rom, depending on kenzo/kate: (http://en.miui.com/a-234.html)
Boot in edl (Fastboot_edl-v2: fastboot reboot-edl)
MiFlash 2016.04.01 (Flash all)
Hello, my realme 3 pro is stuck in bootloop, I am able to go into fastboot, but unable to write anything using it.
How it happened:
I was installing magisk using the magisk app. I rebooted my phone from the magisk app and the phone got stuck on android screen.
What I have tried:
I used vol up + power button then volume down + power button to go into fastboot. On my PC using fastboot devices I can see my device but whenever I try to execute any command such as
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
It says sending 'recovery' (32056 KB) but takes about a minute before saying FAILED (Write to device failed (no link)).
Can anyone please help me.
Thank You
im facing the same problm .
I fixed the issue be using adb on an older computer with usb 2.0 you can try the same
tell me the complete process
i ve deleted my realme vender and other data files in twrp now im stuck on bootloop of realme 3 pro...
but twrp recovery is loading..
how to fix that please help me
Sparta9000 said:
Hello, my realme 3 pro is stuck in bootloop, I am able to go into fastboot, but unable to write anything using it.
How it happened:
I was installing magisk using the magisk app. I rebooted my phone from the magisk app and the phone got stuck on android screen.
What I have tried:
I used vol up + power button then volume down + power button to go into fastboot. On my PC using fastboot devices I can see my device but whenever I try to execute any command such as
It says sending 'recovery' (32056 KB) but takes about a minute before saying FAILED (Write to device failed (no link)).
Can anyone please help me.
Thank You
Click to expand...
Click to collapse
You should have to install realme ui recovery and vander 3.5gb file from official. Than try official method for installation of twrp ozip supported recovery. And flash any rom and mjsik that you want. In case you accidently delete your vander?
Or
But may be your recovery file is corrupted ?
So I advise you to install twrp from official website .
That will be approx 60mb.
After flashing TWRP version 3.7.0_9.0-poplar, and waiting for "Your device has been unlocked and can't be trusted." message to disappear it displays "Your device has been unlocked and the boot image is not working".
How have I flashed TWRP:
Code:
# NOTE: I am using Arch Linux as the host, not windows adb installed from official repositories.
adb reboot bootloader
fastboot oem unlock 0x################ (I have blackout unlock code)
# Restarted and seted up device again, OEM unlocked is enabled in settings + USB debugging
adb reboot bootloader
fastboot flash boot twrp-3.7.0_9-0-poplar.img
After flashing finished and phone being restarted I encountered the message above.
So far I have tried to:
Boot into recovery mode. Power button + Volume Down, the same result except now I have SONY logo for around 5 seconds.
Using ADB to boot into recovery. "adb wait-for-device" doesn't work and never sees the device.
Also when plugged into a computer green light appears in left top corner of phone and also it won't react to any buttons like Power and Volume Up/Down. But Power + Volume Up (completely turn off device) is an exception and it still works.
I think TWRP was corrupted when transferring probably because I have two cables and probably grabbed the one which likes to on random stop transferring data
Is there a way to flash original boot or repair this phone?
EDIT: Okay so I managed to enable fastboot mode. But I can't find stock Boot/ROM.
EDIT 2: Finally created ftf image using Flashtool using files downloaded using XperiFirm. Now the issue is when entering flashmode (Volume Down + Power [NOT fastboot]), green light indicator lights up for ~4.5 seconds then for 2 seconds it turns off and cycle repeats for ever until I unplug the cable. Also when just plugging cable without pressing Vol- the result is the same. If flashmode doesn't work is there a workaround to use fastboot to flash ftf file? Also when I enter fastboot mode and try to get unlock ability I get an error:
Code:
$ fastboot flashing get_unlock_ability
FAILED (remote: 'unknown command')
fastboot: error: Command failed
(Seems like Experia XZ is refusing to execute the command, but I can still flash anything I want onto it using "fastboot flash name file")
EDIT 3: Okay so using Sin extractor in flash tool I have extracted contents form kernel_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin and flashed it as boot and... it works!, but also no. Because when I was messing with this phone I also have flashed something to recovery and oem partitions and I don't know what .sin files correspond to those partitions, below I provide list of files download by ExpriFirm for Experia XZ (F8331)
F8331_Orange MCV FR-ES-PL-SK-RO_41.3.A.2.192-R9E:
Code:
Folders:
boot
Sin Files:
adspso_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
amss_fs_1_S1-MODEMSW-LIVE-DE8D-PID1-0007-MMC.sin
amss_fs_2_S1-MODEMSW-LIVE-DE8D-PID1-0007-MMC.sin
amss_fsg_S1-MODEMSW-LIVE-DE8D-PID1-0007-MMC.sin
apps_log_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
cache_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
diag_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
elabel-F8331-row-row_201804120243693.1_41.3.A.2.149_S1-ELABEL-LIVE-DE8D-PID1-0004-MMC.sin
fotakernel_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
kernel_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
modem_S1-MODEMSW-LIVE-DE8D-PID1-0007-MMC.sin
oem_S1-CUST-LIVE-DE8D-PID1-0004-MMC.sin
partition-image_S1-SW-LIVE-DE8D-PID1-0007-MBR.sin
persist_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
Qnovo_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
ramdump_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
ssd_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
system_S1-SW-LIVE-DE8D-PID1-0007-MMC.sin
userdata_S1-CUST-LIVE-DE8D-PID1-0004-MMC.sin
XML Files:
fwinfo.xml
update.xml
TA Files:
auto-boot.ta
cust-reset.ta
fota-reset.ta
master-reset.ta
osv-restriction.ta
reset-kernel-cmd-debug.ta
reset-non-secure-adb.ta
reset-wipe-reason.ta
simlock.ta
F8331_Orange MCV FR-ES-PL-SK-RO_41.3.A.2.192-R9E/boot
Code:
SIN Files:
cmnlib_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0C-APPID01-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
cmnlib_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
cmnlib_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
devcfg_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID05-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
devcfg_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID05-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
devcfg_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID05-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
emmc_appsboot_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID09-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
emmc_appsboot_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
emmc_appsboot_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID09-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
hyp_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID15-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
hyp_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID15-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
hyp_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID15-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
keymaster_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0C-APPID01-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
keymaster_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
keymaster_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
pmic_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID16-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
pmic_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID16-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
pmic_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID16-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
rpm_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0A-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
rpm_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
rpm_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0A-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
s1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-S1-BOOT-TEST-B316-0001-MMC.sin
s1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_S1-BOOT-LIVE-DE8D-0004-ELF_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tzs1attest_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0C-APPID01-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
tzs1attest_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tzs1attest_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tz_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID07-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
tz_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tz_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID07-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tzs1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID0C-APPID01-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
tzs1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
tzs1sbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID0C-APPID01-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
xbl_S1_Boot_MSM8996_LA2_0_O_204_AID_1_TONE-TEST-HWID009470E1-SWID00-OEM0-AID1-DEBUG00_S1-BOOT-TEST-B316-0001-MMC.sin
xbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-COM-LIVE-HWID009470E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
xbl_S1_Boot_MSM8996_LA2_0_O_204_AID_4_PLATFORM-TONE-LIVE-HWID009470E1-SWID00-OEM1-AID4-DEBUG00_S1-BOOT-LIVE-DE8D-0004-MMC.sin
TA Files:
Kagura_S1BootConfig_MiscTA.ta
XML Files:
boot_delivery.xml
EDIT 4: Also I have egzamined the green light further and it looks like it reboots phone, because when I hold Vol- after green light turn off it will enter fastboot mode. I now know that ROM is located in system.sin, but when I extract the data from it I get ext4 partition which I can mount but I have absolutly no idea how to flash it as Experia XZ complains that file is too big (~5.3GB). Oh and I would almost forgot, I still don't know which .sin file is the recovery one.
EDIT 5: BIG NEWS!!! After unbricking boot partition I was able to install TWRP on recovery. I will get microSD ASAP and I will see what if I can flash stock ROM at least for now.
Thanks in advice for any kind of help!