I have been getting desperate on an issue which I mention in another thread.
I wrecked my phone and got a replacement, got it back to a state I wanted, so that's all good... However, I need to send the damaged phone back by tomorrow (Thursday) or else TMO is going to slap me with a $850 fee.
The problem is that I need to copy the contents of the SD card. This isn't an unreasonable endeavor because the phone, from all appearances, works fine, other than the fact that about 5 seconds after it gets to the desktop, it goes black...but it continues to sound notifications, etc., so I know it is still functioning, albeit with no screen.
When I plug into my laptop using adb, it acknowledges the device, but says its "offline". From looking around the web reading others experience with this error, it doesn't seem like a "real" error. Solutions suggested are changing USB ports, reinstalling drivers, rebooting phone, etc., and the problem seems to go away for those users. However I have tried these solutions, and yet my device still is considered to be "offline".
I use ADB often enough that I never turn off USB debugging so that isn't an issue. But while I know how to push and pull files , or fastboot flash a recovery, I don't know much else about ADB. Is there any experts or ADB gurus who can suggest some other ideas about how I can get this USB convection working? Or at least run some diagnostic too see if in fact the SD card is damaged?
It is very important I get these files of my SD..they are attorney work product and notes regarding a transaction (and also several pictures from the night the phone was damaged) . I make regular backups to dropbox, but apparently not regular enough as my backup wasn't current when I damaged it.
Please ... I am looking for any suggestions. And further, I can't believe that ifthe sd card was in fact damaged, I should still be able to recover some portion of the files. Can one access the sd card when the phone isn't on? It seems rather counterintuitive to me for HTC to create this obstacle consisting the microSD is non-removable on the first place.
Any thoughts are very much appreciated.
Sent from my HTC VLE_U using xda premium
Can't you just mount usb in recovery and pull the contents that way?
Sent from my HTC One S using xda app
lampel said:
Can't you just mount usb in recovery and pull the contents that way?
Sent from my HTC One S using xda app
Click to expand...
Click to collapse
The screen didn't work.
Sent from my One S using Tapatalk 2
Because he said it worked for five seconds I assumed that to be rom related and thought there might be a possibility that recovery would work. After I posted I saw other posts and realized he's pretty knowledgeable... Not too used to that.
Sent from my HTC One S using xda app
Related
Hi, I am having the problem where my HTC Desire can't mount the sd card, and am using the method whereby you open cmd and use 'fastboot oem enableqxdm 0' to fix it. I had done this before because it has annoyingly already happened... anyway, when it came to entering the line 'fastboot oem enableqxdm 0' it read '<waiting for device>' and stops there; the computer doesn't seem to be reading it at all. Am I missing any drivers? I have reinstalled and wiped windows since the first time I did this, so I will have lost everything I had, including programs, drivers etc. that may have read the device.
Please post any ideas you may have; if you need any more information about the device (I think this is more of a comuter related issue at the moment) please ask.
Thanks!
You're not going to like my answer but I had the same problem on my Incredible. I had even just gotten a new computer and cleared my old one. I tried to d/l my sd card contents onto my new computer but my computer couldn't read it, even though up to that point my phone had recognized it just fine. I tried several methods of reading in my computer and reformatting (after I got desperate) but nothing worked. Then when I tried to put my sd card back in the phone, my phone couldn't read it or write to it!
I must've searched a hundred forums and my answers were basically either no one had any idea, or the only option was to get a new sd card because mine had somehow shorted out. I didn't want to believe that there was nothing I could do so I called a buddy of mine who has been building computers probably since before he could walk or talk and he confirmed that sometimes sd cards have a defect that will just randomly cause them to "short" and become unuseable.
After much frustration I ended up having to get a whole new sd (and lose everything off of my previous one) in the process. The only good thing that came out of it was that Verizon replaced it for free with a bigger one.
Hopefully you can find something that will allow you to access yours but I wasn't so lucky. From what I can tell from your post you may end up having the same fate as me in this situation.
I always recommend backing up to an external drive on the computer now as well. You never know when it might come in handy for something like this. I just wish I would have had one before I had to go through all of that.
Sent from my Incredible using XDA App
Hey guys
I just bought a new Nexus S (the GT-I9023 model) and I really love the phone. BUT, since about two weeks, I have very strange problems with the internal USB storage. When I connect it to a computer (yes, I tried on Windows and Mac OS X), I can mount the drive and copy files to it. But as soon as I try to copy larger files from my Nexus S to my computer, the USB storage disables itself and the file transfer crashes. I constantly have this bug, and I have absolutely no clue why it does this. My Nexus S is 100% stock and not rooted (I'm running 2.3.6). Is this a hardware issue? Should I try to get my phone exchanged? Is that a know bug?
I would be EXTREMELY thankful, if you could help me track down this issue...
Please define "large files".
Sent from my Nexus S using XDA App
guru2468 said:
Hey guys
I just bought a new Nexus S (the GT-I9023 model) and I really love the phone. BUT, since about two weeks, I have very strange problems with the internal USB storage. When I connect it to a computer (yes, I tried on Windows and Mac OS X), I can mount the drive and copy files to it. But as soon as I try to copy larger files from my Nexus S to my computer, the USB storage disables itself and the file transfer crashes. I constantly have this bug, and I have absolutely no clue why it does this. My Nexus S is 100% stock and not rooted (I'm running 2.3.6). Is this a hardware issue? Should I try to get my phone exchanged? Is that a know bug?
I would be EXTREMELY thankful, if you could help me track down this issue...
Click to expand...
Click to collapse
Do you have adequate space in your storage? The next time you hook your phone up to OSX, empty the trash while the phone is connected. Sometimes the phone will show plenty of available storage but in reality all your previously deleted files are hidden somewhere waiting for you to "empty trash" in OSX.
Long shot here, but you might have a bad USB cable that makes intermittent contact, and USB disabling turning off during large file transfers is just a coincidence. My OEM cable degraded over time and I had to buy a new one.
If none of the above works, there could be some corruption in your file system. You could copy all the contents of the phone to your computer, format the storage, and copy everything that you need back.
There is one more option that happened to me, but I don't want to panic you since it doesn't sound like the same symptoms, but if you'd like to know more: http://forum.xda-developers.com/showthread.php?t=993403&highlight=corrupt+storage
OK, all files larger than about 30MB are causing the storage to disable. Also, it's not an issue with the trash (I know what you mean, I know the .trashes folder in OSX). I also have plenty of free space.
By the way, huge thanks for the tip with the cable, it seems to have fixed the problem :O ! I actually didn't even think about an issue as simple as a broken cable... >.< At least, it seems to work fine again. The one thing I still don't get, is WHY it could copy small files from the Nexus to the computer and copy ANY file to the Nexus from the computer, but COULDN'T copy large files from the phone to my Mac....
Anyway, thank you for the simple but INSANELY useful tip!
guru2468 said:
By the way, huge thanks for the tip with the cable, it seems to have fixed the problem :O ! I actually didn't even think about an issue as simple as a broken cable... >.< At least, it seems to work fine again. The one thing I still don't get, is WHY it could copy small files from the Nexus to the computer and copy ANY file to the Nexus from the computer, but COULDN'T copy large files from the phone to my Mac....
Anyway, thank you for the simple but INSANELY useful tip!
Click to expand...
Click to collapse
Yep, glad you got it figured out.
Yeah, thank you! (Also glad it's not my Nexus or my iMac's USB ports )
Sent from my Nexus S using XDA App
I was curious if anyone has had any luck in locating the pin out for the jtag port on the ATT Samsung SGH-i727 "Skyrocket". I'm currently trying to locate and jtag my phone. Its not bricked. But I'd like to start digging and hopefully find an unbrick solution
Sent from my SAMSUNG-SGH-I727 using xda premium
Anybody...?
Sent from my SAMSUNG-SGH-I727 using xda premium
It does work. There are people who offer jtag services . But you will need to track them down and hope the share the pin out with you
Oh I know it works. The MSM8660 also supports UART over USB just like SP5C110 chips did. I've been seeing people with a lot of bricks. So I'd basically like to see if we can do an "unbrickable mod" with this chip set too.
Sent from my SAMSUNG-SGH-I727 using xda premium
Yup, ton of bricks around here! Mostly from user error (flashing roms for other devices), but some mysterious ones as well.
I'd love to see this happen.
Alternately, people have been looking into the possibility of using QPST (Qualcomm Product Support Tool) to re-flash the system image (hex file maybe?). QPST seems to see hard bricked phones when Odin does not.
But I hear QPST can be pretty tricky (and dangerous), so that may not get anywhere.
Yes QPST would fix the brick, I'm very sure of it. Problem is like you said very hard to use unless your experienced with it. And also what would we do about the hex? If there's a way to flash on in QPST maybe there's a way to dump one. However, would we need to "virginize" it as to allow install on phones without loss of device specific information?
Sent from my SAMSUNG-SGH-I727 using xda premium
Thx for alls answers... I gonna see what I do..thx!!
TiTy said:
Thx for alls answers... I gonna see what I do..thx!!
Click to expand...
Click to collapse
Did you find the pinout configuration for i727?
Is there any place that lists the pin out connections for different phone models or do they come with the Riff box?
heres a video with a jtag attached, see if u can see what wire is what, it might help
http://vegaslsx.com/vbulletin/youtube_browser.php?do=show&vidid=AkJQAbwZjRk
atrixboy said:
Yes QPST would fix the brick, I'm very sure of it. Problem is like you said very hard to use unless your experienced with it. And also what would we do about the hex? If there's a way to flash on in QPST maybe there's a way to dump one. However, would we need to "virginize" it as to allow install on phones without loss of device specific information?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I often buy broken phones from a friend and have access to two SGH-I727R phones one is hard bricked due to my not noticing that re-partition was checked on the second attempt to flash clockworkmod recovery with ODIN. The second one boots but has multiple issues like no wifi, no Bluetooth, no SIM connection, random data loss on internal SDCARD, USB doesn't show up on computer but charges, likely due to the couple of resistors that fell off the board with the USB connector. I seem to have lost them from the box I put them in. They were specs of dust, lol. Happened when I was cleaning off the white powdery corrosion from the boards.
The corrosion resembles battery acids and aluminum oxides from the housing degrading. And also other damage from water and the elements and likely all manner of unknown liquids, it was found at the local Garbage dump's battery disposal bin.Plus the phone states that the USB cable is connected when it isn't and I have to use the 300kOHM jig to get it to stop that silliness long enough to start USB debugging mode. And last but not least the battery will only charge when it is in download mode or recovery due to warnings that the battery is "too hot and too cold"???? therefore it won't resume charging until it has sufficiently cooled and warmed up (in reverse I am assuming hahahaha) from it's erm hot cold state. Which it isn't. Oh one more thing when booting to the stock rom it had before it was brutally raped and tortured then left to die in a bucket of decomposing and leaking batteries it shuts down app by app till it causes a reboot then it goes through the same loop. I can only get severely stripped roms to boot before the loop happens but after one successful boot it does stay booted. Normal sized Roms crash before it can successfully optimize it's apps. etc...
Anyway, I thought that I would try to use the bootable board to create a hex to flash to the nonBooting QHSUSB DLOAD bricked one, but alas I cannot seem to (haven't searched on it yet been wasting time playing around with QPST without any idea of how any of the tools work or what most of their capabilities are or what 70%+ of the terminology it uses means in relation to the rest of the limited knowledge and experience I have with erm normal erm flashing thingamy bobs. I could understand just enough of it to likely make things worse had I been able to connect to the booting device. And either way while in QHSUSB DLOAD I can see the phone but it does not seem to want to connect and Windows refuses to open the help files because it doesn't want to support those types of help files anymore. So once I find out how to
***So that's the background I apologize for the length. If anyone knows how I go about connecting the booting phone to QPST so I can create a flashable HEX file to then unbrick the other one please let me know. Or where I can get a hex file that is meant for the SGH-I727R phone. Thanks. Googling Hex file etc... returns useless results that have nothing to do with what I want. I will keep trying to find the information and if and when I do I will post it here for yourselves and anyone else that may need it. Plus I will upload the HEX file to my dropbox or similar cloud storage for anyone to use that needs it.
jtag is the only way, afaik no ones has done a diy jtag on the sr, Mobiletechvideos has been used by sr owners w/good results
Okay I'm not into windows 7 phones but I'm helping out a friend. She said its been a common thing with the HTC surround. It boots to the bootsplash(the HTC logo) and doesnt do anything afterward. She hasnt rooted or whatever they call it here lol but can anyone help me on a solution? Warranty is out of the question. But please and thanks for anyone that can help me
Sent from my Inspire 4G using xda premium
Bump.
Sent from my Inspire 4G using xda premium
Sounds like either bad hardware or bad firmware... if it hasn't been modified in any way, I'm not sure what you expect us to suggest. This isn't a tech support forum.
The only thing I can think of to try is get into the flashing mode and re-flash the stock OS. Alternatively, if it has an old enough bootloader, install HSPL and flash a custom ROM. Neither of those will help if it's a hardware problem, though.
Yeah I know I'm not expecting tech support just seeing if there was something I could flash it with I'm an android user so I don't know the ways around wp7 could you supply some links possibly?
Sent from my Inspire 4G using xda premium
Pull the simcard out, wipe the connectors and put it back in.
Had that happen once before with my surround (that my wife now uses to play games and facebook since i got my titan). Simcard was my issue.
Not really that common of an issue.
If the doesn't do it, it's one of 3 things.
messed up flash on built in sd card. if that's the case you need to reset the phone.
1st try a zune restore - you can try to start the phone while holding the power and camera button until you see an image of the phone requesting to be connected to computer once you connect zune should launch and try to restore the device. This should bring you back to the last backup (if you ever made one) that zune took.
if that doesn't work, straight hard reset...
http://www.addictivetips.com/mobile/how-to-perform-a-hard-reset-on-your-htc-surround-guide/
And finally in emergency- take the phone apart and replace the built in sd card
http://www.youtube.com/watch?v=6BiZzfdWDR4
When your done with above you would have to hard reset it. You will need a fast card and do a little research but it's a nice upgrade if you drop a 32gb card in.
Hello, as some of you might have noticed in my previous posts around xda, my tf101 is royally screwed up. I'm stuck in a permanent recovery bootloop, and I can't be saved by my PC. the only concern i have now, is just trying to get the files I had on its internal sdcard. could I somehow put the motherboard into a TF101 with a working USB port, or can I somehow connect a torn USB cable to certain pins on the motherboard to detect it? (my friend once said something about UART connections). I only want to get the files. doing things with software seems out of the question now. hardware tricks might be the only viable option for me... I would really appreciate any kind of answer. whether it's a "that's impossible" answer or otherwise. either way, I'm probably just going to be leaving xda forever. so like I said, does anyone in the vast, knowledge a filled xda community have any ideas?
Sent from my LG-LG870 using Xparent Blue Tapatalk 2
If you have the twrp recovery you can copy the files via the in-recovery-file manager to an sdcard assuming you are able to access the internal memory.
creed10 said:
Hello, as some of you might have noticed in my previous posts around xda, my tf101 is royally screwed up. I'm stuck in a permanent recovery bootloop, and I can't be saved by my PC. the only concern i have now, is just trying to get the files I had on its internal sdcard. could I somehow put the motherboard into a TF101 with a working USB port, or can I somehow connect a torn USB cable to certain pins on the motherboard to detect it? (my friend once said something about UART connections). I only want to get the files. doing things with software seems out of the question now. hardware tricks might be the only viable option for me... I would really appreciate any kind of answer. whether it's a "that's impossible" answer or otherwise. either way, I'm probably just going to be leaving xda forever. so like I said, does anyone in the vast, knowledge a filled xda community have any ideas?
Sent from my LG-LG870 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
There is a lot of information about bootloop in this forum. So there should be a way to break it.
Mostly you can still use APX mode and you can take a backup with spflashtool:
http://forum.xda-developers.com/showthread.php?t=1982587
http://forum.xda-developers.com/showthread.php?t=1129308
I thought it is possible to unpack that image or mount it in a Linux system. It is a long time ago for me, so I don't know the steps anymore.
Take a look here: http://forum.xda-developers.com/showthread.php?t=1249251
But is better to break the bootloop.