[Q] Bricked T-mobile ZTE 768 concord - General Questions and Answers

Hello all,
I have been searching all day trying to find an answer to this issue but so far have only really found information on the ZTE blade...
Today my ZTE concord (v768) randomly turned off. When i tried to boot it back up, i got stuck at the green android boot screen. I tried taking the battery out and tried to boot with the volume up and power keys, or the volume down and power keys, to try to enter recovery mode with no avail.
I have also tried the guide found here- http://forum.xda-developers.com/showthread.php?t=2426426 and the program wouldnt recognize the device when it was plugged into the computer (stuck at the green android logo).
I also tried installing adb but could not get adb to locate the device.
when i plug the phone in to charge it shows an empty battery container with a circle inscribed in it composed of 6 lines (very similar to this logo, http://www.maclife.com/files/u220903/mac_boot_screen_so_fast_620px.png, but with only 6 lines instead of 12.
Is there anything left to try here? Or is this a hardware issue that no amount of fiddling with software can correct?
Thank you for all of your help, and if you need any more info please let me know!

Related

[Q] xoom not powering on

Hi
After being on numerous custom Roms for the xoom I decided to return to stock and was succesful in return to the 3.01 stock image for the wifi MZ604 model
I was also successful in relocking the xoom.
I then began to receive the offical updates though everytime the were applied I had to go into recovery and wipe the device as otherwise it would bootloop on the dual core screen.
On the last update that it received and that was installed , on rebooting nothing happend and the screen just went blank
No combination of volume up + power would show any sign of doing anything.
After leaving the tablet to the side for awhile I noticed it came up with the following
model mz604 : Revision0 (0x8000) modem none
InitBl Info function failed with codes 299/3
failed to boot 0x0001
starting RSD mode 3
one wire : charger is not connected or battery is not being charged
battery charge level : 56%
I tried fastbooting and adb at this point but no devices are found. However when plugging in the xoom my laptop recognises something is attached.
After some searching I found out about RSd lite and SBF files.
When opening rsdlite v5.6 (running as admin) the tablet is recognised and I have now attempted to use two sbf files
HUBWF_W5.H.6.4-20_SIGNED_UCAHUBLWFRTCOREEU_P010_A010_M004_HWwifi_hubble_AP1FF.sb f
and
HUBWF_W5.H.6.2-24_SIGNED_UCAHUBLWFRTCOREEU_P006_A006_M003_HWwifi_hubble_Service1 FF.sbf
however both fail when it attempts re numeration.
I would greatly appreciate any help that anyone could give on this
Thanks
Try this.
My mom's Xoom had a similar problem. Reboot the tablet by pressing Volume Up and Power.
Then quickly turn on the xoom and press the down button as fast as possible, and continue pressing until you see "Recovery Mode" (or something similar) on the top left of the screen.
Once you see that, press the volume up button. Quickly, when you see the Android guy with the exclamation mark tap the power button and the up button.
This will take you to recovery mode. In there use the up and down volume keys to navigate and the power button to confirm things.
Go down to restore/delete data (may vary) and press power. use the volume down key to scroll to Yes.
This will restore your tablet back to factory settings. If you're trying to backup your data, don't try... No such luck and you won't be able to without the tablet booted.
thanks for the reply but this didnt work. Tried quite a few times. The screen just goes blank and again after a long while the error shown in the op appears. Should add there is no Motorola logo showing.
I have also tried forcing fastboot by the instructions found in other similar threads but again this does not work.
I think my best bet is the SBF files , but need to understand why this is failing on re-numeration

[Q] **SOLVED - Need Help Unbricking - Orange Light Problem

Hello, I am trying to help my friend unbrick his phone.
All I know is that he was trying to use a one click root program and after several reboots the phone would no longer boot. It vibrates three times and flashes an orange light.
If I plug the phone into my computer, clockwork mod recovery with the words "ace hack kit" will show up. I tried wiping data, cachce, etc. and installing Android Revolution HD.
On my computer, if I type "adb devices" then it will show H13142452345 recovery.
If I type adb reboot bootloader the phone will vibrate three times and flash the orange light.
When the phone is plugged into my computer during the blinking orange light, then my computer says "device drivers not found for Qualcomm MSM"
I have also tried booting the phone with the sd card and SIM card removed.
Can anyone help?
Thank you.
**************SOLVED******************
The problem was that my volume buttons were broken. Once I destroyed the ribbon cable connecting the volume buttons to the motherboard, the phone booted up just fine.
azndan2 said:
Hello, I am trying to help my friend unbrick his phone.
All I know is that he was trying to use a one click root program and after several reboots the phone would no longer boot. It vibrates three times and flashes an orange light.
If I plug the phone into my computer, clockwork mod recovery with the words "ace hack kit" will show up. I tried wiping data, cachce, etc. and installing Android Revolution HD.
On my computer, if I type "adb devices" then it will show H13142452345 recovery.
If I type adb reboot bootloader the phone will vibrate three times and flash the orange light.
When the phone is plugged into my computer during the blinking orange light, then my computer says "device drivers not found for Qualcomm MSM"
I have also tried booting the phone with the sd card and SIM card removed.
Can anyone help?
Thank you.
Click to expand...
Click to collapse
First, you shouldn't have used a root program that does not support your device. The only efficient rooting method to the moment is the Hack Kit. Anyway. Try reverting your phone to stock using the hack kit. You shouldn't have wiped data also as you have probably disabled USB debugging. If you can't revert it to stock with the hack kit, then your best choice is to hit the IRC channel and ask for help. The guys there know the business and might be able to help. Hope you.can sort the issue out.
Sent from my Inspire 4G using XDA App
Thanks. I'm not sure what program he was using to try to root the phone, my guess is that he was using the ace hack kit because the recovery on his phone says "ace hack kit" on it. Thanks for the tip on going to the IRC.
You've bricked it, I believe the phone is now in Qualcomm's Diagnostic dload mode.
Confirmed, you're in Qualcomm's Diagnostic mode.
My suggestion is to try and find a PD98IMG file that flashes everything to stock, use a clean FAT32 sd card, put it in the phone, and then try to see if it'll flash it when you press volume-down and power. Apparently that should give you five vibrations, then after 5 minutes, press volume up to let it vibrate once, then spend about another 10 minutes before pressing volume up one more time.
Thanks for the reply Hunter. I've tried a variety of button combinations and methods to try to get it to boot into the five vibration green light mode. Unfortunately, no matter what button combination I press I can only get it into 3 vibration orange light mode.
Did you attempt the Hack kit ?
Help please
Im in a dire situation, what do I do. Could some one give me a step by step explanation??
Thank you that would be a big help
it vibrated 5 times and i have a green light, for a while the battery charging thing came up, what do I do??????
I can not help you now, but as a last resort could find a technician and ask for "medusa box"(search in crome explorer). I have this device and I'm back to life a dozen android devices completely bricked, and the htc inspire 4g is fully supported by medusa box, luck

[Completed] Android boot loop - is my device dead?

Hello All,
This is my first post at this forum.
I've come to a point where I'm on the verge of giving up.
A few days ago my Nexus 5 entered a boot loop without me doing anything special with it - it was just in my pocket.
All see is the google logo for a few seconds , then the screen goes down for a few more, and back to the google logo.
I'm able to go into fastboot by hold down the volume down (only) button when this happens, but the boot loop happens when I choose to boot into recovery mode.
My device has an unlocked bootloader.
I have fast boot access and no ADB (ADB wait-for-device doesn't work).
Went over a tutorial from androidforums.com and flashed a completely new image using fastboot.
The entire process worked, but the phone is still at the same state.
I've read that there is and issue with the power button on these devices - so I tried all methods of knocking it against stuff without success.
I've taken it to a lab nearby and the guy there was sure it was the power button. He said he fixed about 50 of these already - after a few hours he called me up and said he had replaced the power button 3 times and he's giving up.
in short , this is the current situation :
1. Device stuck in bootloop - only google logo is seen
2. can boot into fastboot (and have fastboot access from PC) but can't boot into recovery
3. flushing a stock succeeds but won't help
4. power button seems o.k.
I am about to call this a bricked phone and look for a new one but something inside me tells me that this might still be a software issue and can be fixed.
I would be happy to know if there is a way to know what is failing in the boot sequence. or maybe load a debug application on to the device to check the HW. I've yet to find any help in that direction.
I'm a software eng. working in the cellular comm. field, so I'm up for anything that anyone has in mind.
Thanks,
Ran.
XDA Visitor said:
Hello All,
This is my first post at this forum.
I've come to a point where I'm on the verge of giving up.
A few days ago my Nexus 5 entered a boot loop without me doing anything special with it - it was just in my pocket.
All see is the google logo for a few seconds , then the screen goes down for a few more, and back to the google logo.
I'm able to go into fastboot by hold down the volume down (only) button when this happens, but the boot loop happens when I choose to boot into recovery mode.
My device has an unlocked bootloader.
I have fast boot access and no ADB (ADB wait-for-device doesn't work).
Went over a tutorial from androidforums.com and flashed a completely new image using fastboot.
The entire process worked, but the phone is still at the same state.
I've read that there is and issue with the power button on these devices - so I tried all methods of knocking it against stuff without success.
I've taken it to a lab nearby and the guy there was sure it was the power button. He said he fixed about 50 of these already - after a few hours he called me up and said he had replaced the power button 3 times and he's giving up.
in short , this is the current situation :
1. Device stuck in bootloop - only google logo is seen
2. can boot into fastboot (and have fastboot access from PC) but can't boot into recovery
3. flushing a stock succeeds but won't help
4. power button seems o.k.
I am about to call this a bricked phone and look for a new one but something inside me tells me that this might still be a software issue and can be fixed.
I would be happy to know if there is a way to know what is failing in the boot sequence. or maybe load a debug application on to the device to check the HW. I've yet to find any help in that direction.
I'm a software eng. working in the cellular comm. field, so I'm up for anything that anyone has in mind.
Thanks,
Ran.
Click to expand...
Click to collapse
Hello, and welcome to XDA!
It does sound like a hardware issue and it could be the power button, except for one thing: wouldn't a held down power button in fastboot cause a shutdown as well? Maybe not, but I thought I'd ask that.
At any rate, better to get an opinion from someone who actually has the deivce. Please create an account (so you post in other forums) and then post in this thread (can copy and paste from here):
> Google Nexus 5 > Nexus 5 Q&A, Help & Troubleshooting > [HELP THREAD] Nexus 5
Hope this helps, and good luck!

[Completed] Can't boot into download mode Samsung Galaxy S7

Ok, I bought a galaxy s7 from my friend, because he was getting a new phone, but I discovered that wifi wasn't working at all, so I thought it had to do something with the firmware and I decided to flash the rom with odin, with a newer version of the firmware.
This is where all my problems started, when I restarted my phone for the first time I noticed that the startup/booting animation was some weird ****, not like the usual one (the samsung logo) but was a weird loud animation with the letters of MTK, in that moment what came to my mind was that I just could be a custom rom or just a custom boot animation, so I didn't gave it too much attention, I continued to do what I was gonna do and tried to boot my phone into download mode with the classic normal method , Volum Down+Home+Power, when I tried this apparently It didn't work, I could stay there pressing the buttons for like 5 minutes and nothing would happen, and once I would release them, the phone would turn on and do the weird animation and boot like normal, at this point I was already worried so I proceded to Root my phone with KingRoot and install an app to manually boot my phone into download mode, it didn't worked. After hours of searching for a solution I found about ADB and I did all the steps to boot my phone from there, still nothing, when I typed the "abd reboot download mode" or something like that, the phone would just restart and do the ****ing weird animation again, so I tried booting into recovery mode and when I tried to do it, an android robot would appear laying on the ground with his chest open, and the words "No command". When I would press the home button the phone would react and send me to the recovery mode, normal.
So I'm begging you guys for help, since I don't know what to try now.
It looks like the download mode or maybe the firmware is broken, and I can barely do something without the download mode, pls help.
What I've tried so far:
-Basic 3 buttons method (can't remove battery, it's an s7)
- ADB method
- ADB fastboot method
- Vol Up+Vol Down+Home+Power
- Can't do anything with Odin since I need download mode
- Tried to install twrp recovery mode from ADB but says that It didn't found the file
If someone knows a solution for this please tell me what I can do.
Hello,
Welcome to XDA.
Try posting your question in the forum linked below.
http://forum.xda-developers.com/galaxy-s7/help
The experts there may be able to help.
Register a XDA account in order to post and reply in the forums. Good luck.

[HELP] I'm stuck at a Authorization Error screen on a Kyocera duraforce e6560

I attempted to use the majisk manager to install majisk for an unrelated issue and I'm now stuck in some kind of boot loop. I cant get any of the button combos to work as it shuts off the instant I touch the power button and my pc isn't recognizing it. I would prefer to not lose my data but at this point I'm up for any solution you guys have.
Update
I managed to get it to a screen showing the charge symbol and an orange led staying on solid, however nothing seems to be charging nor is it continuing to fastboot or showing up on the adb device list what can i do from here?

Categories

Resources