Sorry my poor english, guys.
No response from the phone. No vol - home power, nor any other combination. No logo, no charging led, no vib... Black screen.
When plugged without battery, the PC detects the Omap4, so I can enter flasboot, but every writting attemp results in a "FAILED (remote: partition does not exist)". Here's an example:
sending 'x-loader' (384 KB)...
OKAY [ 0.203s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
Any advise about this? Is it really dead?
Thanks.
Related
My phone is fine until I'm on travelling severl days ago, I recharge the phone with power bank that I usual use when I cand find any electricity port.
For several minute my phone become warm, and more warmer and close to hot. I try to switch off my phone, then remove battery (its more warm or hot than I expect) after its become colder I try to install battery and swich on power, tara.... There is nothink happen.. Try to charge with charger no response on its screen, still blank. Try to connect on my laptops, its same nothink happens. No hardware detection or etc...
First I think the battery is dead, I try to charge the battery directly with universal charger until the battery full charge, but the result is same my phone still on its "freeze".
Than I try to use fastboot but on 2nd stage give response like i mention below, its FAILED to writing X and U (remote : partition does not exist)
anyone has solution for this?
Code:
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.201s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.217s
sending 'u-boot' (1024 KB)...
OKAY [ 0.527s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.534s
Done
Press any key to continue . . .
adim6001 said:
My phone is fine until I'm on travelling severl days ago, I recharge the phone with power bank that I usual use when I cand find any electricity port.
For several minute my phone become warm, and more warmer and close to hot. I try to switch off my phone, then remove battery (its more warm or hot than I expect) after its become colder I try to install battery and swich on power, tara.... There is nothink happen.. Try to charge with charger no response on its screen, still blank. Try to connect on my laptops, its same nothink happens. No hardware detection or etc...
First I think the battery is dead, I try to charge the battery directly with universal charger until the battery full charge, but the result is same my phone still on its "freeze".
Than I try to use fastboot but on 2nd stage give response like i mention below, its FAILED to writing X and U (remote : partition does not exist)
anyone has solution for this?
Code:
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.201s]
writing 'x-loader'...
FAILED (remote: partition does not exist)
finished. total time: 0.217s
sending 'u-boot' (1024 KB)...
OKAY [ 0.527s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
finished. total time: 0.534s
Done
Press any key to continue . . .
Click to expand...
Click to collapse
You my friend (I think) have a hardware issue and no one on this site can really help you with that. Contact LG
Hey guys am new to this forum even though I have been using your advice for some years now This time I finally encounter my self in really really big trouble with my brand new dell venue 7840 , what happens is that i got the freaking updated for lollipop out of the box, next to that i followed all steps to root lollipop it took some time but everything went 'right'. But 3 days later my tab started to drastically drain Battery, to the point were i cant actually see it going from 100% to 0% in just a minute or two, i hope making some kind of a downgrade to 4.4.4 could fix this issue , but im afraid that when I try to get in to tethered cmw it just show this :
================================================== =====================
DEVICE STATUS: FASTBOOT-ONLINE
DEVICE INFORMATION: 56900EFA01 fastboot
================================================== =====================
copy needed files to our device
target reported max download size of 536870912 bytes
sending '/tmp/recovery.zip' (3477 KB)...
OKAY [ 0.384s]
writing '/tmp/recovery.zip'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.655s
target reported max download size of 536870912 bytes
sending '/tmp/recovery.launcher' (400 KB)...
OKAY [ 0.276s]
writing '/tmp/recovery.launcher'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.545s
we need to stop logcat before replacing it
...
FAILED (remote: command not allowed in this device state)
finished. total time: 0.376s
target reported max download size of 536870912 bytes
sending '/system/bin/logcat' (178 KB)...
OKAY [ 0.269s]
writing '/system/bin/logcat'...
FAILED (remote: Bootloader must not be locked)
finished. total time: 0.537s
issue fastboot oem "stop_partitioning" command to start cwm recovery:
...
FAILED (remote: command not allowed in this device state)
finished. total time: 0.367s
even though the bootloader is not locked , and if i try to unlocked it again in order to enter cmw it says this:
.................................................. .................................................. .................................................. .................................................. .................................................. .............................
C:\Users\Hugo Sanchez\Desktop\IntelAndroid-FBRL-05-16-2015-PTR\resources\platfor
m-tools_aosp>fastboot devices
56900EFA01 fastboot
C:\Users\Hugo Sanchez\Desktop\IntelAndroid-FBRL-05-16-2015-PTR\resources\platfor
m-tools_aosp>fastboot oem unlock
...
(bootloader) Checking unlock authorization.
FAILED (remote: couldn't change state)
finished. total time: 0.309s
I hope some one can help me to fix this
Just a thought but of it drains in a few minutes, something is wrong with the battery or the charger. One possibility is the battery stats are messed up, easy fix is to delete them, but I haven't tried that on lollipop. Otherwise sounds like a return to me... One question, when it drains, does it get smoking hot? If not, battery problem for sure.
dbh369 said:
Just a thought but of it drains in a few minutes, something is wrong with the battery or the charger. One possibility is the battery stats are messed up, easy fix is to delete them, but I haven't tried that on lollipop. Otherwise sounds like a return to me... One question, when it drains, does it get smoking hot? If not, battery problem for sure.
Click to expand...
Click to collapse
Actually it does not get hot when it drains, I believe there is a couple of treads were people are having the same problem after the lollipop update. Don't you think there might be a work around for this ?
I have same problem but cannot find any help ...
I did a wipe with twrp and there was nothing left on my phone...
Then i searched on the web and flashed the boot.img recovery.img and some other things but it says:
target reported max download size of 471859200 bytes
sending 'recovery' (32096 KB)...
OKAY [ 0.715s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.724s
Phone is unlocked..
When i try the update.app and boot into the installer it goes to twrp
Please some1 help me
p.s. My english is bad
EDIT: I followed this thread > https://forum.xda-developers.com/xperia-z2/help/guide-idiots-guide-to-root-twrp-t3534647
And it worked perfectly. This thread is solved
So I got a hold of a z2 running MM and I'm trying to install twrp using linux shell.
So first I got this apparently installed right.
Code:
fastboot flash recovery twrp-3.0.1-0.img
sending 'recovery' (11558 KB)...
OKAY [ 0.365s]
writing 'recovery'...
OKAY [ 0.774s]
finished. total time: 1.139s
But then when I try to get to the recovery, this happens...
Code:
fastboot boot twrp-3.0.1-0.img
downloading 'boot.img'...
OKAY [ 0.365s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.417s
Does anyone know what the fix is for this? It's probably something simple that I'm just unaware of.
Thanks for your replies.
The cruel irony about it all, is that right after I got everything set to switch it over to being my main phone, as I inserted the sim card, the sim card slot broke inside
Hey all,
basically I ****ed up. I installed 9.0.0.161 through TWRP, forgot to clean everything so naturally while I had Pie running, everything was strange and slow working. When I went to TWRP and format everything (the option where you have to type 'yes'), it couldn't boot.
Now the only thing I can do is flash stuff over fastboot, and I tried flashing the system.img and kernel.img from the BLA-L09C432B157 (8.0.0.157) firmware. It didn't work, and I can't even access eRecovery or anything else than fastboot.
What should I do? I realize this has been my fault for trying stuff out without thinking twice. >.<
EDIT: I should say it's a European Mate 10 Pro (BLA-L09C432)
bump
Flash recovery
E recovery C185 Pİe
Shutdown phone use vol- and usb cable to enter fastboot
Press ENTER key to continue...
Wait FASTBOOT connection....
Replace kernel...
target reported max download size of 471859200 bytes
sending 'kernel' (12882 KB)...
OKAY [ 0.411s]
writing 'kernel'...
OKAY [ 0.063s]
finished. total time: 0.489s
Replace recovery...
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (25632 KB)...
OKAY [ 0.804s]
writing 'recovery_ramdisk'...
OKAY [ 0.167s]
finished. total time: 0.992s
Unplug usb cable, use vol+ and power key to enter recovery.
Press ENTER key to continue...
I'm removing the Usb Cable for OK After. Audio Turn On And Power Off Directly into eRECOVERY. Normal does not enter Recovery!
emprazol said:
Flash recovery
Click to expand...
Click to collapse
Did that, still didn't work until now
yunusdemir said:
Shutdown phone use vol- and usb cable to enter fastboot
Press ENTER key to continue...
Wait FASTBOOT connection....
Replace kernel...
target reported max download size of 471859200 bytes
sending 'kernel' (12882 KB)...
OKAY [ 0.411s]
writing 'kernel'...
OKAY [ 0.063s]
finished. total time: 0.489s
Replace recovery...
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (25632 KB)...
OKAY [ 0.804s]
writing 'recovery_ramdisk'...
OKAY [ 0.167s]
finished. total time: 0.992s
Unplug usb cable, use vol+ and power key to enter recovery.
Press ENTER key to continue...
I'm removing the Usb Cable for OK After. Audio Turn On And Power Off Directly into eRECOVERY. Normal does not enter Recovery!
Click to expand...
Click to collapse
Well, now I'm in eRecovery, thanks for that. However, when I try to download latest version and recovery, it just tells me "Getting package info failed".. how should I proceed?