Not sure what the cause is. The screen remains black on bootup. There's no sign of damage and I don't think I've done anything out of the ordinary/ I've tried connecting it to USB but it comes up with something called APX. Any help would be greatly appreciated.
So it doesn't boot?
hmm did you replace the bootanimation.zip?
Related
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.
Nexus 7 was working fine and then I pulled it out and notices a gray screen. Restarted it and I get a slight blue shadow to the Google and Padlock boot screen. Then it begins to change crazy colors and ends up fading to a gray screen. Can't boot into recovery from fastboot. Help?
Here are some pictures in order of boot.
cbcampos said:
Nexus 7 was working fine and then I pulled it out and notices a gray screen. Restarted it and I get a slight blue shadow to the Google and Padlock boot screen. Then it begins to change crazy colors and ends up fading to a gray screen. Can't boot into recovery from fastboot. Help?
Here are some pictures in order of boot.
Click to expand...
Click to collapse
Wow, I haven't seen or heard of any defect like that in the N7 yet. I would exchange/RMA the device if I were you. It seems like an easily demonstrable problem, there shouldn't be any reason Google/a retailer wouldn't exchange it.
Sent from my Paranoid Nexus 7
RockNrolling said:
Wow, I haven't seen or heard of any defect like that in the N7 yet. I would exchange/RMA the device if I were you. It seems like an easily demonstrable problem, there shouldn't be any reason Google/a retailer wouldn't exchange it.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
Even with the bootloader unlocked? Or do I need to somehow lock it?
update
cbcampos said:
Nexus 7 was working fine and then I pulled it out and notices a gray screen. Restarted it and I get a slight blue shadow to the Google and Padlock boot screen. Then it begins to change crazy colors and ends up fading to a gray screen. Can't boot into recovery from fastboot. Help?
Here are some pictures in order of boot.
Click to expand...
Click to collapse
It actually seems as if it is partially just a screen issue. I heard a notification of an email on the N7. I believe it has actually booted up, but the display is stuck. If I tap where the notification bar would be, I heard audio feedback.
UPDATE: I suspected something was loose in display connection because of the type of problem. I knocked pretty hard on the device, and the display kicked back in. Doesn't solve the problem of being unable to boot into recovery, but it seems like it could be a display problem. Suggestion still to just get a replacement? and relock bootloader?
cbcampos said:
Even with the bootloader unlocked? Or do I need to somehow lock it?
Click to expand...
Click to collapse
My bad, I skimmed your post and didn't realize you could get into fastboot mode. Try turning off the N7, connecting it to a computer , and getting back to fastboot mode. You should be able to use adb to relock the boot loader. In fact, you should be able to boot into recovery from fastboot since the N7 is connected to a computer.
Good job trouble shooting the display connection! I would still personally recommend exchanging/RMA. You never know when the problem might reappear even if you "fix" it.
Sent from my Paranoid Nexus 7
Take the back cover off and check the display ribbon cable,and all other connections are tight. They won't be able to tell that the back was removed, unless you ding it up. Might find a loose connection. May just save you the trouble of going through RMA.
Sorry, i am very poor at english.
My G2 is Hard Bricked (No recovery, no download mode, even no LG logo!).
My computer says my G2 is 'Unknown Device'
I tried to fix it, but anything works.
And almost every solutions I've read are needed QHSUSB_DLOAD or similar things, so i can't get any help:crying:
Please help me........
I don't want to go to the support center:crying:
When you attempt to boot the phone is it just a black screen? As in you can see the backlight on, but the screen is black?
EricCamino121 said:
When you attempt to boot the phone is it just a black screen? As in you can see the backlight on, but the screen is black?
Click to expand...
Click to collapse
Nope.:crying:
My phone is not answering while(after) pressing my power button.
No backlight.
My phone do completely nothing without computer.
EricCamino121 said:
When you attempt to boot the phone is it just a black screen? As in you can see the backlight on, but the screen is black?
Click to expand...
Click to collapse
But i can controll the power.
When the phone turns off, computer can't cognize my phone.
Try plugging your phone into the computer when the screen is black, and if it comes up with a bunch of different partitions, then you're going to need to manually flash the bootstack with a linux machine.
My s4 is stuck in boot screen. Recovery doesn't work and i dunno why. Download mode works but I don't wanna format my phone(got some important apps in there). And it really heats up to the point there's moist on the camera lens(?)
What did you do?
I haven't really done anything. Just while charging I'd turned it off. Then turn it on to find out the it is stuck on boot screen. I will try flashing a stock firmware
I did now flash a stock firmware.. but still not working. at first boot some green dots covered up the screen. then it became white then i was forced to remove the battery. I think it has something to do with the heat that made the screen green-white
ryanperez said:
I did now flash a stock firmware.. but still not working. at first boot some green dots covered up the screen. then it became white then i was forced to remove the battery. I think it has something to do with the heat that made the screen green-white
Click to expand...
Click to collapse
Seems a hardware problem.
Yeah. :/ i want to really know what causes the problem
Hey, I broke my op2 screen so I bought one from ebay, teared it apart all correctly (i'm a computer technician), installed the new screen, all fine but a weird symptom appears:
- It boots and shows the Oneplus logo then screen all black. I know it booted cuz the touch buttons work and i can ear the sound of unlocking etc. Also if i plug into the pc I can easily access its memory.
- If I try to enter recovery I know it enters too but the screen is all black, the only mode I can see the screen is fastboot mode and it stays and acts normally.
- I did a full reset on the phone back to stock via adb, thinking it was software, its all stock now, still the same occurs
Im out of ideas so I just think the screen is faulty from ebay, did this happened to anyone?
Thanks in advance