Related
I think my phone is bricked
When I start up my phone it just stops when it says "ZTE"
Tried to reboot but wont work, its fully charged...
Please help
Are you rooted? Do you have ClockworkMod installed? What rom were you running?
NO
matt4321 said:
Are you rooted? Do you have ClockworkMod installed? What rom were you running?
Click to expand...
Click to collapse
No. No. and none.
I weren't running any roms or anything, but i have tried to root it with z4root and gingerbreak (etc..) a million times...
Your best bet mate is to get into fastboot (should be doable since you're getting to the splash screen), flash a custom recovery and then a custom rom, although this does void your warranty, I think its worth it though. What android version was your phone on before the problems started?
Sent from my Xoom using Tapatalk 2
if he installs stock rom and unroots then it should be fine and he will keep his warranty
Sent from my Blade using xda premium
Ehhh..
matt4321 said:
Your best bet mate is to get into fastboot (should be doable since you're getting to the splash screen), flash a custom recovery and then a custom rom, although this does void your warranty, I think its worth it though. What android version was your phone on before the problems started?
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
I dont quiet know how to do that
I was on 2.3.5 have 2gen stock rom
how do i get into fastboot then?
To get clockworkmod on, so you can flash your stock rom, which can be found here http://forum.xda-developers.com/showthread.php?t=1353526
Download fastboot and adb files, grab them either from the android website but through the sdk, or just Google adb and fastboot files and you'll be fine.
Then boot into fastboot by turning your phone on with the volume up button held down. It'll stay at the splash screen, connect to the PC and it should install drivers automatically.
Download the recovery image by googling clockworkmod zte blade. You want 5.0.2.0, it's the latest.
In the command prompt change directory to where your adb and fastboot files are. Then type 'fastboot flash recovery *nameofrecovery*.img'. Then 'fastboot reboot'. Power off the device after and boot into recovery by powering on with the volume down button held. Then flash your stock rom.
Hope this helps, i know it could be better but I'm at a BBQ so on my phone and can't link stuff easily, if you need more help, i can do it tonight. Others I'm sure will help too
Sent from my ZTE-BLADE using Tapatalk 2
matt4321 said:
To get clockworkmod on, so you can flash your stock rom, which can be found here http://forum.xda-developers.com/showthread.php?t=1353526
Download fastboot and adb files, grab them either from the android website but through the sdk, or just Google adb and fastboot files and you'll be fine.
Then boot into fastboot by turning your phone on with the volume up button held down. It'll stay at the splash screen, connect to the PC and it should install drivers automatically.
Download the recovery image by googling clockworkmod zte blade. You want 5.0.2.0, it's the latest.
In the command prompt change directory to where your adb and fastboot files are. Then type 'fastboot flash recovery *nameofrecovery*.img'. Then 'fastboot reboot'. Power off the device after and boot into recovery by powering on with the volume down button held. Then flash your stock rom.
Hope this helps, i know it could be better but I'm at a BBQ so on my phone and can't link stuff easily, if you need more help, i can do it tonight. Others I'm sure will help too
Sent from my ZTE-BLADE using Tapatalk 2
Click to expand...
Click to collapse
Still looks way to complicated for me :/
Do u know any videos that can show me how to do it?
hi is it bricked or what?
hi all xda members, im new on this forum and i really don know were to post or something like that, sorry, and i have searched on every singel page in google and on a lots of forums, and i dont find anything that can help me with my problem..:crying:
So now to my poroblem, i have a zte blade II 2.3.6 gen3 un-rooted, i tryed but no luck... and now i think its really bricked...because i cant boot it at all, not in FTM, not in bootloader mode, not in recovery, the only thing i can boot it in is DFU but i cant flash from there, it is bricked or can this be fixed easily? Thanx in advanced guys!
ZTE Blade does not respond at all
My ZTE Blade does not respond at all.
I have tried to install the official update from android 2.1 - 2.2 using this official application from ZTE
( ztedevices official site -> downloads -> Greece -> smartphone ->Blade)
It stopped in the middle of the process and after that I cannot use neither Power&volume(+) nor Power+volume(-) nor Power.
It looks completely dead.
Battery is fully charged,
When connected to charger, back button does not get red.
When connected to computer does not show android logo.
I have copied gen1 to gen 2 image folder to sd... nothing
gen2 to gen 1 the same.
I have also tried the AIO-BLADE application no respond to any action.
I have been searching this forum and the internet for 2 days now. No one answers cases whith hardbricked phones.
I think the phone is out of warranty.
PLZ it is my only smartphone and there is no money for a replacement, I am unemployed.
:crying:
*** Returned my N7 (2012) as faulty and swapped with a 2013. Thread Ended. ***
I've been having trouble with my N7 (2012) for a while now.. Ever since the 4.3 update.. Slow response, hangs, and so on.
The latest 4.3 update would not install. Just a lying down droid with '!'.
My tablet was rooted using Wugfresh toolkit and was perfect before 4.3.
So i thought i'd go back to the start and use the toolkit to go back to root and flash stock+unroot.
Went through all instructions, it got to the part where it says ' You tablet will now reboot a few times. Please wait.'
Waited for 30 mins and nothing..
Now got a tablet with the google name and the unlock symbol. Options available are start, bootloader, recovery, off
All bring back to same screen.. Bootloader option displays -
Fastboot mode
PRODUCT NAME - tilapia
VARIANT = tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.18.0_0409
SERIAL NUMBER - 015d88ffa8540a1c
SIGNING - not defined yet
LOCK STATE - UNLOCKED
During the flash boot to stock it wiped all directories etc so I now have an empty tablet..
Any ideas what I can do now? I would prefer to go back to stock 4.2 if possible... but if not, any help would be nice...
filking said:
I've been having trouble with my N7 (2012) for a while now.. Ever since the 4.3 update.. Slow response, hangs, and so on.
The latest 4.3 update would not install. Just a lying down droid with '!'.
My tablet was rooted using Wugfresh toolkit and was perfect before 4.3.
So i thought i'd go back to the start and use the toolkit to go back to root and flash stock+unroot.
Went through all instructions, it got to the part where it says ' You tablet will now reboot a few times. Please wait.'
Waited for 30 mins and nothing..
Now got a tablet with the google name and the unlock symbol. Options available are start, bootloader, recovery, off
All bring back to same screen.. Bootloader option displays -
Fastboot mode
PRODUCT NAME - tilapia
VARIANT = tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.18.0_0409
SERIAL NUMBER - 015d88ffa8540a1c
SIGNING - not defined yet
LOCK STATE - UNLOCKED
During the flash boot to stock it wiped all directories etc so I now have an empty tablet..
Any ideas what I can do now? I would prefer to go back to stock 4.2 if possible... but if not, any help would be nice...
Click to expand...
Click to collapse
Hi, filking...
I have no experience with toolkits, so I can only advise you to download the Factory Image for your 'tilapia'/'nakasig' Nexus 7, and fastboot flash it.
Using fastboot isn't that difficult, and I'm at a loss to understand why toolkits have become so popular, when fastboot is so easy to use. Maybe people don't like command line interfaces...??
Anyway, there's a thread here which explains it all in detail.
Good luck.
Rgrds,
Ged.
Hi, thanks for the reply.
I think, in the world it is now, everyone is used to menus/mouse clicks to perform functions.
Anyway, I have read that thread already and my problem is when I get to the commands. All 'adb' commands don't work.
'adb devices' shows nothing.
I've tried in bootloader mode and recovery mode... All show a droid lying down. Fastboot mode shows the above message. Rest show, 'boot failed'
Help.....
filking said:
Hi, thanks for the reply.
I think, in the world it is now, everyone is used to menus/mouse clicks to perform functions.
Anyway, I have read that thread already and my problem is when I get to the commands. All 'adb' commands don't work.
'adb devices' shows nothing.
I've tried in bootloader mode and recovery mode... All show a droid lying down. Fastboot mode shows the above message. Rest show, 'boot failed'
Help.....
Click to expand...
Click to collapse
You don't need ADB to flash a stock image. ADB only works with a fully booted Android tablet. Indeed, if you have no bootable OS on your tablet, ADB is redundant and will not work.
You need to use fastboot...
What do you see when you type fastboot devices? (whilst the N7 is booted into the bootloader).
Rgrds,
Ged.
An update....
I went through wugs full driver setup part and deleted existing drivers. Installed the drivers again...
The device is detected on my PC.. But, seeing as it is stuck on the bootloader screen and I can't get into the system to turn on debugging, no adb commands work.
Device is listed as an 'unknown' android device when plugged in..
Seen a few other posts similar, but a lot say, 'it's ok, i've fixed it' without saying how.
anyone?
sorry, our posts must've been at same time..
Fastboot devices shows
015d88ffa8540a0c fastboot
*EDIT* Looks like i've misread the instructions in the post linked to above...
It got to the part where is said 'type in adb devices'... I read that, it didn't work, and I stopped.
BUT, I was already in bootloader mode, so didn't need that bit..
My error. (it's been a hot day!!! is that a good enough excuse.)
Continuing with the fastboot commands now... I'll update how it goes..
Thanks for replies.....
Update. All resolved.
I tried with the 4.3 img, but for some reason, it went through all the steps correctly. fastboot reboot resulted in the bootloader screen again.
Weird I thought, so I downloaded the 4.2.2 img and tried that and it worked perfectly..
Many thanks all who did, and it's a reminder to all. Re-read instructions..
:highfive::good:
Hi guys,
I had posted a brief thread a couple weeks ago stating that my Nexus 4 restarted by itself, and got stuck in the bootloader animation loop. I couldn't remember whether I had enabled USB debugging in my phone prior to it killing itself (not rooted, completely stock, did the OTA 4.4.3 update just a few days before my phone died, and phone's been out of warranty for quite a while now ).
So I installed the SDK developer tooklit, and followed instructions to set up ADB.
However, everytime I boot my nexus 4 into recovery mode/"safe" mode, I get the following screen ("Screenshot 1" below).
From there, when I boot into recovery mode, I get the following screen ("Screenshot 2").
Every time I connected my phone to my laptop (keep in mind that I cannot start it .. I always plug it in when I'm in "Screenshot 1" mode) and try to used "adb devices", I get the following cmd screen ("CMD ADB Devices" picture below). I've repeated this process and tried plugging the nexus in during various points in different "safe mode" options. Same result: nothing is detected.
So I got frustrated at trying to backup any data from my phone, and just chose the "wipe data/factory reset" option from the nexus recovery mode, and I got this screen ("Screenshot 3"). I've tried this several times, and I keep getting this screen.
So my nexus committed suicide, and I'm totally not sure what to do. I've been trying to learn how to use ADB etc for the past couple of days by scouring through the xda nexus 4 forums, but I'm still very much a n00b. Do you guys have any advice as to what I can do to get my nexus 4 back to a usable state again?
Things I've already tried (in order):
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
I also tried to ADB sideload a stock Nexus 4.4.3 factory image, but it is useless since my device won't even show up in CMD when i enter ADB devices.
However, the problem is that my nexus is never detected in CMD no matter what combination of things I tried, so I can't even do half of the things both of those thread instructions state.
I would greatly appreciate ANY ways to factory reset or flash working firmware on my phone! :highfive:
Edit: I reinstalled Android SDK, and connected my nexus to my laptop after entering fastboot ("safe" mode; volume down + power from phone off state), and I was able to get a slightly better looking CMD window when running ADB Devices command (See "CMD ADB Devices 2" picture). However, same problem as before, where my phone isn't even registering via ADB.
So again, your input would be tremendously appreciated.
If you boot in the bootloader (Volume- and Power) it's normal that you can't use adb. You have to use fastboot in the bootloader.
What is the output of fastboot devices?
Code:
fastboot devices
Have you already tried to flash the factory image or did this fail, too? You have to download the factory image from google, extract it and connect the phone in the bootloader/fastboot mode. Run the flash-all.bat then and it will reflash the stock rom. This will wipe your data, but I guess this shouldn't be a problem for you anymore because you already tried to do a factory reset!
If this worked, boot your phone and if it works fine, I would recommend to relock the bootloader (because it gets unlocked automatically if you flash the factory image and if you don't want to root/modify your phone in any way, your bootloader is usually locked):
Code:
fastboot oem lock
Try it and if there are any other problems or if it doesn't work, just ask again
Hello everyone. Recently, I used this tutorial: http://forum.xda-developers.com/showthread.php?t=2392762 to obtain Cm11. What happened was when I tried to unlock the bootloader, and used adb commands to execute the files on my root. After I did reboot, the phone wouldn't turn on. No signs of life, can't boot into recovery mode. I've done the tutorial before on this phone, and I reverted back to stock. Now that I'm doing it again it won't work. I think it may be hardbricked. When I plug it into my PC, I can go to device manager and the PC will recognize it as a Qualcomm driver. I really want to fix this problem without needing to call LG or get repair for it. I looked at some tutorials and found this one: http://forum.cyanogenmod.org/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/ I'm not sure if this'll work for me. Can someone please provide me with some help with this situation.
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Same problem
Same thing happened to me. Same day as you. I can get fastboot but not adb but since the device is locked I can't flash. I've only had the phone about 6 months so I contacted customer support and they offered to replace the phone.
It might be a known issue because they didn't even try to address the fact that I could get fastboot connected but not adb. They just offered to replace.
Thanks for the info! I am -at least in this case- unfortunately an early adopter. I bought two essentials at the beginning of the pre-release.
Essential support checked my serial number and said the phone was out of warranty.
Has anyone been able to force the Essential into EDL mode to recover that way? It looks like you have to latch one of the USB pins to ground, or 5V, but I haven't found any detailed instructions on how to make this work on the essential...
Thanks again
Justin
I'm sure things have changed and I'm wrong, but if you can get into the fastboot menu can't you just cycle through the options until you get to recovery and then flash an official release from Essential?
I may be thinking of LG or something but this should be possible as long as it's newer than the current software installed because it will see it as an official update and allow the flash.
Thanks but unfortunately, when I try and do that, the phone just does the same thing, it hangs forever on the initial boot screen white Android text with the circle/square logo...
That's why I've been looking into the more direct hardware version of forcing the phone into EDL mode, which is supposed to be possible with all Qualcomm based phones.
I've just not found the time yet to find a USB-C cable I'd be happy to cut in half and short the pins on! Which is why I was hoping someone might have tried this with an essential before to know if it was successful before I start trashing good cables
Thanks again for your reply!
JB
justinbaird said:
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Click to expand...
Click to collapse
I have the exact same problem,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cannot flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you