Database Users

magic blue led fix

so after getting my blue led light after i did a bad flash of a mod update zip when i didnt have a rom flashed first...i was told to replace my trackball instead i ...
opened my htc magic and removed my trackball and disconnected the ribon to it let it sit for 30 seconds then put it back together i guess it resets hardware but it worked like a charm

tried ur methode on my bricked magic ... no luck

did u have the blue led with no hboot or recovery ...make sure ur battery is charge some

thatruth132 said:
so after getting my blue led light after i did a bad flash of a mod update zip when i didnt have a rom flashed first...i was told to replace my trackball instead i ...
opened my htc magic and removed my trackball and disconnected the ribon to it let it sit for 30 seconds then put it back together i guess it resets hardware but it worked like a charm
Click to expand...
Click to collapse
I can't understant why doing that the device has unbricked, I probably must do the same.

anyone else tried?
is this really working???

can anyone other than the OP confirm this works? what showed up on the screen when it was bricked? Did it have the 'arrow coming out of the box' symbol, when the phone was switched on?

i did nt get big arrow or anything my phone wouldnt boot period all i kept getting was a blue light no fastboot or adb would work until i did this the only reason i tried it was because someone mentioned to me to replace the track ball i dont know why but it worked

Did you happen to remove the little battery when you did this?

no i only disconnected the cable leading to track ball the if u look where the track ball is you can pry and pop out the track ball i did it just to look around in there ...i am not a tech but i do have a basic understanding of somethings and i think for some reason in my situation it may have reset something i really dont know but my phone was a brick for half a day with me trying to use google as my friend typing away at fastboot and adb commands only to get nothing ..but when one person told me i may need a new track ball i just decided to look inside on how that a bad flash would effect the track ball but i did what i did and i am back using my phone but i did notice one thing today i had put my phone in fastboot and the normally when it loads those command or whatever about loading img. ...its now saying no image

Thanks, I will try this. Unfortunately I gave away my battery and cable... I still have doubts about this helping me, as I flashed the wrong radio. Where as you just flashed a bad update.

did u use a 32b radio

thatruth132 said:
did u use a 32b radio
Click to expand...
Click to collapse
hi,
quick question. my friend rooted the phone and then flashed hardSPL but i think it was the wrong one. the last thing we saw was a box with a arrow on it and the phone has been dead ever since.
was this the same for you ? we would love to be able to unbrick his phone.

brick
hi,
i have a 32b magic, and since yesterday it just doesn't startup anymore.
i just get a black screen, with backlight on. (also no adb/fb/recovery)
if i hold trackball while power on, i get the blue led
i've searched, but haven't found any similar problem, cause i don't get that box with an arrow.
to unbrick this, you just disconnected the trackball?
pls be more specific
HEEEELLPPP!

fakecaker said:
i just get a black screen, with backlight on. (also no adb/fb/recovery)
Click to expand...
Click to collapse
Sounds like you erased or flashed an invalid SPL (usually people brick into boot mode 3 where the radio + SPL works but is forcing the boot of a broken recovery image) Thus the user becomes stuck at the splash screen.
Regardless if blue light mode woks and nothing else will boot [and you are not stuck in blue light mode]:
the only option at this point in time is using JTAG to force an engineering SPL to load.. then use that to fix the rest of the phone.
http://forum.xda-developers.com/showthread.php?t=668246
http://forum.xda-developers.com/showthread.php?p=6100287&highlight=radata#post6100287

The OP likely had a stuck trackball.
Holding the trackball when you power on puts you in the blue-led mode and doesn't let you do anything else. Being in blue-led mode doesn't mean you are bricked, it's just a mode in which the phone can start up. If the op's trackball got "stuck", it would explain his problem. Replacing the faulty trackball likely is what solved his problem.
It would be nice if the OP could update the first entry to reflect as much.
If your phone isn't voluntarily going into blue-led mode on it's own, this "fix" likely won't do anything for you. You still have a brick... like me

ezterry said:
Sounds like you erased or flashed an invalid SPL (usually people brick into boot mode 3 where the radio + SPL works but is forcing the boot of a broken recovery image) Thus the user becomes stuck at the splash screen.
Regardless if blue light mode woks and nothing else will boot [and you are not stuck in blue light mode]:
the only option at this point in time is using JTAG to force an engineering SPL to load.. then use that to fix the rest of the phone.
http://forum.xda-developers.com/showthread.php?t=668246
http://forum.xda-developers.com/showthread.php?p=6100287&highlight=radata#post6100287
Click to expand...
Click to collapse
hi terry ...
quick question.
the jtag de-bricking that everyone is mentioning is said to work with g1/dream/g2 ... is this also possible with the magic(sapphire) 32A ?
like i said my friend bricked his loading hardSPL and the phone is charging and i can get into the blue led mode no problem.
if it is possible would the pinouts be the same or similar for the magic? i am quite keen to give it a bash if i can be pointed in the right direction.
thanx in advance.

Thank for you response
but i didn't flash any new spl or something else.
i had my phone working fine with spl/radio/rom.
but then i shut down, and after that i couldn't power up

i reboot my working magic with froyo and then is dead.
its keeps rebooting and no fastboot or recovery mode only if i press trackball and on the phone i got blue led, any solutions ???
Regards Sn00py

But what exactly was the problem, when you turned it on it automatically turned the blue led or did that happen when you pressed the trackball+power? im going to try to debrick my magic now but must it be on with the blue led or off?

ale922 said:
But what exactly was the problem, when you turned it on it automatically turned the blue led or did that happen when you pressed the trackball+power? im going to try to debrick my magic now but must it be on with the blue led or off?
Click to expand...
Click to collapse
Who are you asking, the OP? They just had a stuck trackball, so they couldn't boot normally.
It doesn't matter, just continue.

[Q] Black Screen, no reaction, no LED

Hey
At first sorry for my bad english
I tried to root my kindle fire and i think i installed the wrong cyanogenmod recovery/bootloader. Now he will not start, the screen is black and the LED shows no reaction. I serched for someone with the same problem... i tried it with a self made factoy cable with connection from the 1st pin to the 4th, but no reaction... what can i do?
Ever grateful
Tungred

Could your battery be low? Mine does that when it needs to be charged and it does it without any warning. Sometimes when charging it takes a while, maybe 20 minutes for the orange light to come on.

ok i try it tonight but i think there will be no reaction

ok i tried, and i am right there is no reaction
anything else i can do?

sounds like a bricked kindle. I had one after i shorted a couple pads on the mobo by accident. contact amazon, and play dumb. xD

Tungred said:
ok i tried, and i am right there is no reaction
anything else i can do?
Click to expand...
Click to collapse
I think i have the same problem as you. And I just got this kindle. So what happened to your kindle? what did u do?

Omg man, do i will need send to lg warranty center for the 3rd time?

hi guys, this is my 2nd nexus 4 and it already got to lg cervice center less then one month ago.
now i have a problem with the screen.
my phone was on fastboot mode for some time(~45 mins) with usb plugged in, it wasnt hot or warm.
but when i booted into the os i could see some marks of the 2 arrows of the fastboot mode
http://cdn-static.cnet.co.uk/i/c/blg/cat/mobiles/nexus-4-root/fastboot1.jpg (fastbootmode image)
then i restarted in twrp and i still could see(altho it was less, probably because of the buttons not being transparent).
so now the phone is off. do u guys think if i let it off until tomorrow 7am(13hours from now) it will disapear?

Do you mean this?
http://forum.xda-developers.com/showthread.php?t=2331143
[Q] What's wrong with my display?

Krazhil said:
Do you mean this?
http://forum.xda-developers.com/showthread.php?t=2331143
[Q] What's wrong with my display?
Click to expand...
Click to collapse
nope,if you look the bootloader mode, on top left side there are 2 arrows(one poiting up, other down)after some time on bootloader mode when i started, i still could see a "Ghost" of those arrows on every app etc, even in the recovery... . my phone is turned off, i will turn on in some hours, i hope it fixes by itself

Screen burn. Not sure if that's covered by warranty, you might want to look. If it's not too bad it usually fades over time.

Screenburn is normal on N4.

turned on phone and it was gone.lol i thoght that this didnt happen on lcd screens, on all of my phones the n4 is the 1st to do this...

Locked out of EDL, ROM, and recovery

I have an A2017U. Earlier I EDL flashed @jcadduono's B19. But now, when I use VolUp+Power, it goes to stock recovery and reboots. So I can't factory reset the phone. And I don't have TWRP either. I also can't boot into the stock ROM by just holding power, stock recovery appears for a second and then the phone turns off. When I hold VolUp+VolDown+Power I get a black screen and a solid red light, which is supposed to be EDL. But MiFlash doesn't detect the phone.
What the hell am I supposed to do to recover, when I'm locked out of all the modes I can use to get out of this mess?!
Thanks!

Always replace recovery with twrp when flashing. If you can get to test mode - vol down + power - you can adb reboot edl.

@lafester: Do you mean the FTM screen? Is that test mode? I've seen it before but I've always thought it was 100% useless. I've never heard of anyone flashing from that screen. What about DFU? When I press VolDown+Power the stock recovery screen just flashes for a second and the phone shuts off. Same thing when I press VolUp+Power. I simply don't see how flashing a stock EDL can brick the phone, MiFlash reported it was successful. No errors at all. But now, I can't get back into EDL. Just a solid red light and a black screen. MiFlash wont read it, neither will Axon7Tool. I think the issue is that my data and cache partitions are F2FS, stock recovery can't read them, so it just shuts down. I had this issue before, but eventually the ROM booted and told me to factory reset. So I did and all was dandy. No luck this time around.

Another thing I've noticed, is that when I reboot to EDL, I get a black screen and a solid red light. I was previously running AEX Oreo, I have heard that the Oreo bootstacks can screw with EDL. Before Oreo I got a black screen and a red light that blinked once and turned off, then I was able to EDL flash. I have read that if I let the phone fully discharge (by allowing the red light to drain the battery completely), then maybe I can try something else in a few hours once that is done. But what? really need some help here.
Thanks!

AnonVendetta said:
Another thing I've noticed, is that when I reboot to EDL, I get a black screen and a solid red light. I was previously running AEX Oreo, I have heard that the Oreo bootstacks can screw with EDL. Before Oreo I got a black screen and a red light that blinked once and turned off, then I was able to EDL flash. I have read that if I let the phone fully discharge (by allowing the red light to drain the battery completely), then maybe I can try something else in a few hours once that is done. But what? really need some help here.
Thanks!
Click to expand...
Click to collapse
I run Oreo bootstacks and EDL works fine.
If you cant enter recovery or EDL mode, you will have to try with a deep flash cable (very low chances of it working) or follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152

So did you try it? Yes, ftm screen is test mode. You also need to tell us what device manager is saying when you are in edl mode.

lafester said:
So did you try it? Yes, ftm screen is test mode. You also need to tell us what device manager is saying when you are in edl mode.
Click to expand...
Click to collapse
he has a black screen with a red light, that's DFU
EDL only blinks a red light once
thats a 4th category brick

AnonVendetta said:
Another thing I've noticed, is that when I reboot to EDL, I get a black screen and a solid red light. I was previously running AEX Oreo, I have heard that the Oreo bootstacks can screw with EDL. Before Oreo I got a black screen and a red light that blinked once and turned off, then I was able to EDL flash. I have read that if I let the phone fully discharge (by allowing the red light to drain the battery completely), then maybe I can try something else in a few hours once that is done. But what? really need some help here.
Thanks!
Click to expand...
Click to collapse
Have fun using my guide! ?

He has a u version. Most likely not bricked.

lafester said:
He has a u version. Most likely not bricked.
Click to expand...
Click to collapse
crap, i overlooked that. Maybe @kitcostantino knows more? Honestly I never understood what was his problem or what he did to fix it, but it was on an U and it looked exactly like DFU...

Only time I ever had a dfu issue was with the very first Chinese beta. I was able to get into test mode and then boot into edl.

So, no access to FTM, otherwise my issue would be solved and I wouldn't be posting. I let the battery drain all day by letting the red light burn through it, I had figured that letting the battery drain would be the equivalent of short circuiting the pin that @Choose an username... speaks of. No power in the circuits=reset. I got it to where the red light either does blink, or stays on for a moment and turns off. But EDL and other tools doesnt recognize the phone either way. I read some of the 4th category brick guide, it says you need to disassemble the phone. But I am no good with hardware, if I take it apart then it will very likely not go back together in one piece. So I would like to avoid that. I also don't have the money to pay a technician, I prefer to fix my own problems. I bought my A7 new from NewEgg, it came with SquareTrade insurance. Maybe I should call ZTE and try to get a warranty repair? I can just tell them I was repairing via EDL from a bootloop, when it all went bad. Don't need (and probably shouldn't) mention TWRP, etc.
I have 3 QUSB__BULK entries under "Universal Serial Bus Devices" in Device Management. Normally, it would show up in "Ports" category, if EDL was working properly.

Just dropped a private message to @kitcostantino to see if here can post in the thread.....

Volume + and - plug USB cable at the same time may work......

@stinka318: Already tried that before you posted. Same as before.

If you still have your warranty, then I'd send it back to ZTE if you can't get it to come back to life.

@try5890: I still have the standard warranty, as well as SquareTrade insurance. But if there is a way out of this that doesnt involve hardware disassembly (which might make things worse), then I'd rather go that route instead. It's Sunday anyway, so I'll have to wait til tomorrow to call either ZTE or SquareTrade. If there is a chance of resolving it before then.....

AnonVendetta said:
So, no access to FTM, otherwise my issue would be solved and I wouldn't be posting. I let the battery drain all day by letting the red light burn through it, I had figured that letting the battery drain would be the equivalent of short circuiting the pin that @Choose an username... speaks of. No power in the circuits=reset. I got it to where the red light either does blink, or stays on for a moment and turns off. But EDL and other tools doesnt recognize the phone either way. I read some of the 4th category brick guide, it says you need to disassemble the phone. But I am no good with hardware, if I take it apart then it will very likely not go back together in one piece. So I would like to avoid that. I also don't have the money to pay a technician, I prefer to fix my own problems. I bought my A7 new from NewEgg, it came with SquareTrade insurance. Maybe I should call ZTE and try to get a warranty repair? I can just tell them I was repairing via EDL from a bootloop, when it all went bad. Don't need (and probably shouldn't) mention TWRP, etc.
I have 3 QUSB__BULK entries under "Universal Serial Bus Devices" in Device Management. Normally, it would show up in "Ports" category, if EDL was working properly.
Click to expand...
Click to collapse
You have another problem there. Right click on the QUSB_BULK and Uninstall device. If you were on DFU it would show up as ZTE Handset Diagnostic Interface.
If you ever used Zadig then that's your problem. If not, it's worth trying anyways

Choose an username... said:
crap, i overlooked that. Maybe @kitcostantino knows more? Honestly I never understood what was his problem or what he did to fix it, but it was on an U and it looked exactly like DFU...
Click to expand...
Click to collapse
just to clarify, what i have had success with,is letting the phone completely die, then charging with my laptop (which is lower power than a QC or standard plug) until i get the 'connect charger' message. at that point i charge using my Quick Charge oem brick and cable. after that, for whatever reason, EDL works for me again. Prior to that, point, DFU mode was all i could get. no recovery, no fastboot, no EDL. Just solid red light after holding the EDL mode key combo (vol +, vol -, power). but no Qualcomm 9008 whatever it is, ive done this a couple of times. its always trying to go stock, but something had failed.
while it makes no sense to me, id say its worth a shot. boot into what you have at that point, which is only DFU mode, and simply let the phone die. if it powers off, power back on, and let it die completely. then plug up to a computer usb port, let it charge until you get that message, and after you charge above 30-40% min, EDL to something else. i must also say somewhere in my mis-adventures, i killed the imei on not one but two a2017u boards, so something does not like going back to MM. at that point, i had a bad download of b15 that was breaking touch functionality, so i flashed back to MM. The board flashed fine, but serial and imei went bye bye.
[posted for the greater good...this was a pm. ]
AnonVendetta said:
@try5890: I still have the standard warranty, as well as SquareTrade insurance. But if there is a way out of this that doesnt involve hardware disassembly (which might make things worse), then I'd rather go that route instead. It's Sunday anyway, so I'll have to wait til tomorrow to call either ZTE or SquareTrade. If there is a chance of resolving it before then.....
Click to expand...
Click to collapse
Dude, it may seem daunting, but this is one of the easiest phones to disassemble i have owned. grab some guitar pics, a magnet (for screws), and something like the top to the axon 7 box, and a relatively high quality phillips precision screw driver. the trickiest parts are the speaker grills, the fingerprint cable, and separating the back. the screws beneath the tape/speaker screen material i just didnt put back in my axon phone that has been taken apart. if ya have warranty, ya may as well send it in. i presently have not one but two boards that are without an IMEI. i keep my second axon in an easy to disassemble state as i didnt put the screws that are under the adhesive and speaker grills. i can board swap it in about two minutes now as ive done it like 20 times. it really isnt bad man. watch jerryrigeverything's video and its a piece of cake.
however, if you want to use warranty and not have to pay ($79) to ZTE to use Passport warranty, dont take it apart. if ya take it apart and fail, worst case scenario, ZTE will charge ya $80.
Square Warranty i know nothing about.
critical step on drain/trickle charge/edl is to just let it charge by itself on the oem usb cable to the computer until you get the 'plug in....' screen. just going over it in my mind trying to be certain i mentioned everything i did. in both instances, i was on stock.

AnonVendetta said:
@try5890: I still have the standard warranty, as well as SquareTrade insurance. But if there is a way out of this that doesnt involve hardware disassembly (which might make things worse), then I'd rather go that route instead. It's Sunday anyway, so I'll have to wait til tomorrow to call either ZTE or SquareTrade. If there is a chance of resolving it before then.....
Click to expand...
Click to collapse
No need to open your device, just follow this guide.

Recovering pictures from Crashdump blocked phone?

Hey guys,
I was on my honeymoon until yesterday, celebrating in Cancún (Mexico), taking some great and important pictures for us with my OP8P, and in one of the places the phone got a bit of water inside it but it kept working fine for the next two days (even charging up after dried it). Then, next day we tried to take a picture, camera app looked like it were inside water and front camera had condensation on it. When restarted the phone, it got stuck into "Qualcomm CrashDump", and forever there. It reacts to pushing vol + vol - and power going into fastboot menu, but recovery mode doesn't work.
I understand that my phone got softbricked (as hard means no reaction at all, right?) and that I need to restore it to have it working back; thing is, I really want to save my honeymoon pictures before wiping everything away with MSM (never used it but saw that's the way to flash and revive the phone), but can't find a way so far to get my pictures back... Could you guys help me please?
My phone is a IN2023 version, original stock rom and unlocked developer mode from menu, but never rooted nor touched anything else.
Thanks in advance!!
EDIT: As another piece of info, when I plug the phone into windows I hear the "plug and play" sound, but don't see no new unit in the "my computer" area.

Should be able to just hold power and volume up for about 10 seconds to force it to reboot to android

jamescable said:
Should be able to just hold power and volume up for about 10 seconds to force it to reboot to android
Click to expand...
Click to collapse
Nope, it doesn't. If I do that, it goes back to the 1+ screen, then goes black, and then instead of loading OxygenOS, goes to Qualcomm Crashdump...

Alohran said:
Nope, it doesn't. If I do that, it goes back to the 1+ screen, then goes black, and then instead of loading OxygenOS, goes to Qualcomm Crashdump...
Click to expand...
Click to collapse
Then yeah, your only option is msm. Even if you sent it to one plus, that's the tool they use. You could always factory reset in recovery but once again, that will delete your stuff. Either way, you lose it all