I've read through a number of other threads but can't sem to get a definitive answer to my particular problem.
Some weeks ago my daughter dropped my Streak and caused the LCD to leak. I ordered a replacement screen from eBay, it arrived earlier this week and I fitted it and it worked. On a side note I have now upgraded to a Galaxy Note but am keeping my Streak as its such a great phone. This means however that it doesn't currently have a SIM card or an SD Card.
Once i'd fitted the new screen i decided to do a fresh install and booted into fastboot, however I then realised that I didn't have an SD card in, so whilst it was still plugged in, I took the battery out. The screen flashed in a strange way, went blank, but remained backlit until I removed the data cable.
Since then the screen has just backlit but nothing else. I have used Streakflash, QDL tool, both successfully, but to no avail.
I have checked and double checked the connections from the new screen to the motherboard. Unfortunately i disposed of my old screen before this happened so cannot test it on my broken screen.
When I remove insert a blank, freshly formatted SD Card, a 'LOST.DIR' folder and occasionally an 'ANDROID' folder appear if I leave it to run for a while after powering on.
My question is this: Do you think it might just be the screen that is malfunctioning, or might the phone be kaput?
Any help would be appreciated.
No i don't think it is bricked,
since the folders are automatically created (lostdata and .android), i think your phone is still running. If your phone is a factory unlocked i suggest you to flash ROM using fastboot.
You can find lots of thread on how to flash, just search the forum and hope you will have your streak back
Hope it helps.
PS:"From my experience i would like to warn you not to use "fastboot -w" option in fastboot mode never ever(coz that can really brick your phone)"
Related
I posted this over at SD, but not sure that gets the traffic that XDA does so I'm double posting...
*** Original post ***
I was upgrading from an old version of VeganTab to Brillant Corners. I NVFlashed to 1.1 3588 and made sure things worked. I then nvflashed to 1.2 4349 and let things boot up. Everything seemed to work. I then put the BC update.zip on the sdcard and rebooted to recovery which installed BC. I also installed the supplement. Everything worked although I noticed some instability in BC, I gave it a few days but it just didn't seem right so I nvflashed back to 4349.
I was going to reinstall BC but after I nvflashed 4349 I had some issues... I ended up getting a magic number mismatch and when I shut off the tablet and tried to start it again I no longer got any birds or any gtablet screen. It didn't seem like anything was happening. I panicked a little and started reading the recovery options over at the dummies site. I talked myself into cracking open the tab and trying the unplug the battery method of getting back into APX mode. After turning on and off the device a few times, I believe I also ended up hitting the reset button inside the case, I finally noticed that when I was powering on the tab it was going straight to APX mode without showing the birds.
I then nvflashed back to 4349 and booted up. I put the tab back together and when I got booted back up I noticed that I now had no touch screen. My buttons work (home, back, etc...). I could plug in a mouse and click around. But the screen didn't register any touches. I started reading about the touch screen and trying things. I flashed back to 1.1 different roms, flashed back to 1.2. Nothing fixed the screen. I ran the fix screen calibration from the 1.2 recovery and also by putting the file on the sdcard and external sdcard.
I also let the battery drain all the way dead and tried reflashing and recharging and still had no luck.
I also cracked the tab back open to check all the connections. I can't find any reference as to what cord is the connection for the touch screen. Everything internal looks plugged in and ok. I'm always careful with electronics, I have a desk for working on them and have been playing with them since modding PS1's back in the late 90's.
Does anybody have any ideas, anybody head of this. Did some hardware get ruined and do I have a broken tab. I have one of the original tabs, bought when they first appeared at Staples last fall.
*** Somebody suggested running the Code Detox from the dummies site ***
Well I did the detox, after wiping and using the format nvflash I ended up with a magic value mismatch. I used the internal reset button to get the device to connect in APX mode and successfully flashed back to 1.1 3588. Booted up normally but the touch screen is still not responsive. I'm not sure what else to try. I might have just borked the device. I may try completely disassembling the table and reassembling it to make sure nothing got disconnected. I'll also inspect the connections to make sure no wires look damaged.
Anybody else have any other ideas?
bmasephol said:
I posted this over at SD, but not sure that gets the traffic that XDA does so I'm double posting...
*** Original post ***
I was upgrading from an old version of VeganTab to Brillant Corners. I NVFlashed to 1.1 3588 and made sure things worked. I then nvflashed to 1.2 4349 and let things boot up. Everything seemed to work. I then put the BC update.zip on the sdcard and rebooted to recovery which installed BC. I also installed the supplement. Everything worked although I noticed some instability in BC, I gave it a few days but it just didn't seem right so I nvflashed back to 4349.
I was going to reinstall BC but after I nvflashed 4349 I had some issues... I ended up getting a magic number mismatch and when I shut off the tablet and tried to start it again I no longer got any birds or any gtablet screen. It didn't seem like anything was happening. I panicked a little and started reading the recovery options over at the dummies site. I talked myself into cracking open the tab and trying the unplug the battery method of getting back into APX mode. After turning on and off the device a few times, I believe I also ended up hitting the reset button inside the case, I finally noticed that when I was powering on the tab it was going straight to APX mode without showing the birds.
I then nvflashed back to 4349 and booted up. I put the tab back together and when I got booted back up I noticed that I now had no touch screen. My buttons work (home, back, etc...). I could plug in a mouse and click around. But the screen didn't register any touches. I started reading about the touch screen and trying things. I flashed back to 1.1 different roms, flashed back to 1.2. Nothing fixed the screen. I ran the fix screen calibration from the 1.2 recovery and also by putting the file on the sdcard and external sdcard.
I also let the battery drain all the way dead and tried reflashing and recharging and still had no luck.
I also cracked the tab back open to check all the connections. I can't find any reference as to what cord is the connection for the touch screen. Everything internal looks plugged in and ok. I'm always careful with electronics, I have a desk for working on them and have been playing with them since modding PS1's back in the late 90's.
Does anybody have any ideas, anybody head of this. Did some hardware get ruined and do I have a broken tab. I have one of the original tabs, bought when they first appeared at Staples last fall.
*** Somebody suggested running the Code Detox from the dummies site ***
Well I did the detox, after wiping and using the format nvflash I ended up with a magic value mismatch. I used the internal reset button to get the device to connect in APX mode and successfully flashed back to 1.1 3588. Booted up normally but the touch screen is still not responsive. I'm not sure what else to try. I might have just borked the device. I may try completely disassembling the table and reassembling it to make sure nothing got disconnected. I'll also inspect the connections to make sure no wires look damaged.
Anybody else have any other ideas?
Click to expand...
Click to collapse
Hey
Im also suffering from a similar problem. Everything works and my gtab boots up fine, but the touchscreen is unresponsive. Ive pulled the device apart and looked for any damaged connections especially the ribbon connection to the outer touch screen layer. Everything looked fine. After putting back together, i started and it booted up fine, but touchscreen still unresponsive.
Has anyone else been able to recover from this? What did you do?
Cheers
I ended up calling the support number and the device was under waranty so I got a RMA and sent it in. 2 weeks later I had it back working, same case but I think the guts were swapped. Only cost me the shipping. Pretty good deal. Just make sure you flash back to stock.
bmasephol said:
I ended up calling the support number and the device was under waranty so I got a RMA and sent it in. 2 weeks later I had it back working, same case but I think the guts were swapped. Only cost me the shipping. Pretty good deal. Just make sure you flash back to stock.
Click to expand...
Click to collapse
That sounds like what im going to have to try and do, although im in australia, so i dont know how kind they will be about replacing it.
I have another problem now after trying to flash back to original stock rom in this thread
Im not having a good couple of days lol.
Cheers.
Last night I bought a brand new Streak 5 from a local guy. Box was sealed, no mention of refurb, inner contents were sealed.
I didn't have time to test it and the guy I bought it from said he had gotten it a while back from a work raffle and that it had been sitting in a drawer in his house - I have no reason not to trust that he was lying to me.
When I actually got time to unbox it, I popped the battery in and tried to turn it on. The menu buttons lit up briefly and then when out. The screen never came on. Since then, it has been completely unresponsive.
I've tried to charge it with the wall charger, as well as my PC. Neither seem to be doing anything and my PC doesn't recognize it - even with Dell's software installed.
I've tried to take out the battery and hook it up to the wall charger and my PC to get it to turn on.
I've removed the Micro SD.
There is no SIM card in it currently.
I ordered another battery and an external battery charger. They should be here in a few days. I have the current battery rigged up and charging with a spliced USB cord.
What else can I do? I feel like I've done everything "simple" thus far and I'm a little nervous when it comes to utilities like Streakflash.
I'm coming over from the iPhone world and my Android use has been limited at best. Any help is appreciated.
What happens on the device itself after having had a chance to charge?
Does it light up when you press the power button, or nothing at all?
Thanks for the response.
There is no indication that it's charging. The screen doesn't come on, or even flash. The buttons do not light up. However, I don't believe it's the cable or the connector since my PC responds with an unrecognized device -- "Qualcomm CDMA Technologies MSM" prompt. I also managed to get my PC to tell me that the device "wasn't plugged in."
I've tried to get some response out of it in every possible combination regarding the buttons, battery, back cover, microSD, and where it's plugged in. It just sits there. No lit screen, no lit menu buttons, nothing.
If it helps, I'm running Windows 7 64 bit. I've installed every possible thing I could find regarding the Dell drivers and my OS.
It sounds like your device somehow got shipped without having all the software installed onto it.
Can you provide more information about the device itself, such as it's manufacture date or any other info on the box/device labels? Devices getting shipped half baked like that isnt exactly common.
This sounds like a legitamate time to use QDL tool to reflash it, but I cant provide any help with that as I've never used it.
Can you use QDLTool if your computer doesn't even recognize it?
The date on the label is 10/12/2010.
If it's displaying as "Qualcomm CDMA Technologies MSM" that's a sign that it should be able to get into upload mode as that's what the driver qdl tool uses I believe.
It's likely out of warrentee already, so you prob have to fix it on your own if at all.
I can't get it to respond to anything I do. It's very disheartening. I really, really wanted this phone, too.
I'm downloading the latest version of Ubuntu. I'm going to see if I can make any headway through Linux.
I can't get QDLTool to pick-up the device, either. I get an error message when I try to use it and scanning for it does nothing.
Did you install the driver bundled with it properly?
If it still doesnt detect it after that it's likely a dud
use qdltool, you can download it from here
http://www.box.com/s/rj9xd5tl7v5amimbm3youll need to make sure you have all drivers installed though, info is on this forum somewhere,
once installed run the software on pc you should see a big box with "run" on it, click run then connect phone by holding volume up and connecting usb then qdltool will do rest from there
when i got my both my dell streak it was the same deal. first one came exactly as how you described it. I put in the battery, made SURE THAT THE CONNECTORS ARE lined up on the back case, and then tried to power it on. NOTHING.
It seems even if the battery was fully charged, the only real way to turn it on was to connect the streak to the power adapter and then press hold down the on button. WHen the device finally gave me the dell logo, it would just sit there stuck. So i took out the battery, and redid it. Then went into fastboot mode (hold camera and power) and it wouldnt detect the touch screen. It seems that the touch scree was faulty and hence it would remain stuck on the dell logo. I tried to calibrate the touch screen a few times, all failed. Then finally for one time it worked, and the touch screen came back to life. Shortly after though upon booting into the old stage 1.6, it restarted and the touch screen failed again.
So i sent it back to rogers and they gave me a replacement phone. Same deal, when you first put in the battery and the case it wouldnt start no matter what. Only upon plugging it into the power adapter then it starts up. However this new one had a functional touch screen.
1) check out the touch screen by using the fastboot, or stock recovery. If you get error messages, it means your screen is toast most likely and then you might have to open her up and see if all the connections are lined up
2) if it doesnt boot at all, try connecting it to the power adapter first and then after about 30 seconds power it on. You should be able to see the dell logo unless as the guys stated before the software is hosed.
3) if the software is totally hosed, tried to get it into fastboot mode or recovery and see if you can reflash the device.
something like that...
Thanks for the comments, guys.
As of now, it's still in the same position it was in. It doesn't respond to any combinations of buttons, battery in/or, or plugged into the wall/pc.
I'm assuming that the situation it's in currently is what's preventing any sort of legitimate connection between the phone and my PC.
My last shot is a battery and external charger that should be here next week.
My phone was working perfectly fine until yesterday, when I went to the pool and carelessly left my mobile phone near some humid/wet clothes. When I got my hands on it, it was /working/ or so it seemed yet I couldn't put the SIM code to unlock it. It then restarted and got stuck in a bootloop.
I removed the battery, checked the Water Damage stickies and everything seemed fine, but still wasn't working. Today I got home and dropped my phone in rice (I heard it's good in order to absord water and such) and after a while I removed it, put the baterry in but now it just gets stuck on the boot screen.
I tried going into recovery, was able to, but can't surf through the menu because volume keys don't seem to work.
Any ideas what is wrong with my device? Any suggestion for a new phone if my phone doesn't come back from the dead?
Technical data?:
Unlocked with HTCDev Unlocker, rooted, and flashed CM7.1 with no problems before.
Two year old device.
Bump and extra info about my problem.
I left my phone discharging it's battery and seeing if anything worked okay. This morning it was off and wouldn't turn on, so I put it to charge.
After some hours, I got it's LED green so I tried and turned it on. It did, but still didn't pass the Cyanogenmod bootscreen, so I tried going into Recovery, and it worked! Now I'll try to tinker it, and see if I can get it fixed.
So, if anyone out there has the same problem I have, they should try killing their battery and charging it to 100%. It seems the battery malfunctioned or is almost dead, but a man can wish and see if he can repair his gadgets.
Glad to hear it's fixed! I'm sure many others would feel the same way about your recommended remedy!
Sent from my Nexus 7 on the XDA app. GO CANADA GO
Thanks!
When I had access to the Recovery I backed up my phone and wiped dalvik and cache, then re-installed Cyanogenmod (now upgraded from 7.1 to 7.2) but I'm currently considering switching to another ROM, like an ICS'
Everything works fine, except the SIM, but I believe that's a problem on my own end (network not working)
A week or two ago, my phone was lagging, so I pulled the battery out to restart it, as it wasn't restarting from the OS. It turned on to the HTC logo, then the screen went black. The rest of the phone works, including the digitizer and volume buttons. I purchased a replacement screen and installed it. The issue remains. I'm able to boot to Recovery and use a Java program called Android Screen Cast to see the display. Unfortunately, the display signal is corrupt, so I'm unable to test if a ROM reinstallation would work. I doubt it would in the first place, though, as Recovery, Fastboot and Hboot don't show anything as well, so it's most likely a hardware program. What could this be? I'm stumped on this one, and I'd like to have a phone to use until I have enough money to buy a replacement.
Just purchased a brand new Mann Zug 3 rugged phone.
It might be rugged outside buy it's pretty darn fragile when you try to actually use it.
When I first powered it, it booted fine. No problems.
Then I inserted the sim card and a used sd card from my old phone.
Ever since then my phone won't boot. and it's in a loop.
I even got it into fastboot mode but then my windows7 pc couldn't recognize it even though I believe I've installed proper drivers.
Now I can't remember which combination of keys gets me into fastboot once more and the only thing I can get it to do is either
a) bootloop
b) get it to inform me in red lettering that it can't load a specific file
c) get a neon green Chinese word on the screen. It looks a bit like the neon green used for the word fastboot but who knows
d) get it to go into some weird mode that's a blank black screen with a white dot. And ever time I reboot into the same mode, the dot moves to a different location on the screen and just sits there
I'm guessing my new phone might have tried to flash the image in the sd and since that came from another phone it caused trouble but that just my gut feeling.
So does anyone have any sort of suggestion as to what might be happening and how to resolve it?
Even if you know the different key combination for the Mann Zug 3 that could be helpful.