Related
First off, I want to thank the wonderful amount of knowledge and help here at XDA! Not to be impolite to anyone else, but through all my searching, I have yet to find anything like this forum (and I come from a number of forums); but none have had quite the caliber of kind, knowledgeable, and often humorous: people. So thank you all. Also, another disclaimer is that I've only been on Android for about a month and half, so please bear with me as I might (and probably) misuse vernacular and/or might not completely understand some of the technical lingo' (at least the first time through, but I have spent much time here reading through help guides and threads).
Alright, here's the problem: I cannot get a computer to recognize the Vibrant. Installed all the drivers I have found thus far, followed a number of guides from here at xda, and have tried a number of different computers (two Win7 machines, a Vista, and even two XP machines); all of which recognize my personal Vibrant without a hick-up. Here is perhaps the biggest, and main, problem: the computers/odin won't even recognize it in Download Mode. That is what is stumping me..
If you do not care to know about how I got to where I am, please jump to the 'Question:' part.
Here is the back-story:
I bought a used Samsung Vibrant that came with the JI6 build. This was the second vibrant I had purchased as it was for my sister; and for the most part (other than it being horribly slow on the 'stock' build) it was running, and perfectly functioning.
However, I did notice that it was not able to connect it to a computer; usb debugging, mounting sd, and all the guides I found for troubleshooting just didn't seem to do the trick. Still no connection to the pc. I eventually educated myself on Download and Recovery mode, both of which I could execute without really any problems.
But since I wanted to run a faster OS (And I had already successfully flashed my personal Vibrant to Froyo (Build 21VE) (Here)) I decided to flash my sister's vibrant as well. And since I was unable to connect via usb to use odin to flash to the JFD build (per highly suggested here on xda), I used a nandroid image to flash the stock JFD build from Samsung (I can't find the link at the moment, but it was here from the xda forum). All went well, I was on JFD. I then used the above link to flash the Froyo21VE build via clockwordMod; again, it went smoothly. Only one problem persisted at this point: the wifi would not work.
My brother had experienced a similar issue with his Vibrant's wifi a few weeks previous, but had resolved it by flashing a different Froyo build. Naturally I thought I might do the same. This is where things went South.. Perhaps I was multi-tasking too much at the time, or possibly I just wasn't paying attention, but after a quick google search I found this Froyo build here on xda: [ROM] Froyo (RS)JP5 - "K9" [25/11/2010]. Moved it onto the internal sd card; flashed via clockworkMod; and then it froze on its boot-up after installation. Not cool..
Unfortunately, I was not aware that the build was for the Galaxy S i9000 rather than a Vibrant branded Galaxy; once realized though, my gut sank.. As now I am wondering if I completely tanked this Vibrant; or perhaps it had a problem from the bigging in that the usb wasn't connecting?
Question:
First and foremost, is there an 'advanced' way of connecting via usb from a computer, or some other way of doing it? I have tried numerous usb cables (as I've read a couple different people were having success with that) on several different computers (all of which, though, seem to be working perfectly on my personal vibrant, just not this one). Or is there a special driver that allows for just the 'Download Mode' on the Vibrant to communicate to the pc? But from my understanding, it seems as though the 'download mode' is pretty much as basic as you can get, am I correct in that assumption? Additionally, would using the android sdk help at all? (Or again, doesn't it have to be able to be recognized from the computer first?)
And lastly, just in case I thought it wasn't complex, when I had a functioning OS on the Vibrant: when I plugged in the usb, the Vibrant would show that it recognizes the pc; I even could 'mount the sd', but the computer still wouldn't recognize it apart from a few times that it would show it as 'unknown device' and would not seem to load any drivers; and I was having difficulty locating the device in Device Manager. (But that only seemed to work when I had a functioning OS, now that it only can go into ClockworkMod or Download Mode, I have yet for the computer to acknowledge its presence)
Alright, there it is. Please let me know if I missed something, or if more information would be helpful. Again, I want to thank anyone who would be able to help me out, or give suggestions. I really am at a loss for ideas; and the past week of analyzation is hardly showing any signs of improvement.
Thanks for taking the time to read.
EDIT: it occurred to me that I didn't mention that I am unable to load any *.zip files while in ClockworkMod (thus being able to flash a different build). It continually gives a 'No File Found' or Error/Wrong command. I believe that was caused by the i9000 firmware messing up the file system on the Internal_sd, does that seem logical?
Have you installed kies from samsung? I tried installing just the drivers on my win 7 pc and they wouldn't take either. I then downloaded kies and installed and it seemed to properly install the needed drivers.
Sent from my Axura injected voodoo possessed Vibrant.
I believe I have installed it twice now, but I will try again. Thanks for the suggestion, I'm pretty much all ears at this point.
EDIT: Well I installed the Samsung Kies mini Apllication and it did its update thing and now I have v1.0.0.10104_1. Doesn't appear to have helped the drivers out..
Question: would anyone think that this particular Vibrant has a defective usb port? I realize that's a long-shot, as well as I would definitely not like hearing that.. but any thoughts?
shalom24 said:
I believe I have installed it twice now, but I will try again. Thanks for the suggestion, I'm pretty much all ears at this point.
EDIT: Well I installed the Samsung Kies mini Apllication and it did its update thing and now I have v1.0.0.10104_1. Doesn't appear to have helped the drivers out..
Question: would anyone think that this particular Vibrant has a defective usb port? I realize that's a long-shot, as well as I would definitely not like hearing that.. but any thoughts?
Click to expand...
Click to collapse
It appears that you have a defective USB port on the phone.
Do you have an access to a Linux box? If a current linux distro cannot see your phone via USB it will confirm the DOA USB port on the Vibrant.
Thanks for the reply lqaddict, although it's somewhat sad to hear.. Forgive my ignorance, but by 'Linux Box' you are referring to a Linux machine, correct? If so, then I do not have access to one. Again, forgive me for not knowing, but would running linux (possibly via a bootable Linux cd) on a computer be equivalent?
Since I purchased it used (through Craigslist about three weeks ago (which he said he had purchased two weeks previous)) do you think I might be able to retrieve the receipt from the original owner and perhaps Samsung would be able to help with some sort of warranty?
Thanks again for your response.
EDIT: Well I am running Live CD of Ubuntu 10.10 on another one of my pc's, however, I'm not quite sure I know how to 'check' to see if usb port is properly functioning (sorry I'm not very familiar with Linux, but I imagine I will become increasingly more accustomed to it in the near future). Any ideas for trying out connectivity on Linux?
shalom24 said:
Thanks for the reply lqaddict, although it's somewhat sad to hear.. Forgive my ignorance, but by 'Linux Box' you are referring to a Linux machine, correct? If so, then I do not have access to one. Again, forgive me for not knowing, but would running linux (possibly via a bootable Linux cd) on a computer be equivalent?
Since I purchased it used (through Craigslist about three weeks ago (which he said he had purchased two weeks previous)) do you think I might be able to retrieve the receipt from the original owner and perhaps Samsung would be able to help with some sort of warranty?
Thanks again for your response.
EDIT: Well I am running Live CD of Ubuntu 10.10 on another one of my pc's, however, I'm not quite sure I know how to 'check' to see if usb port is properly functioning (sorry I'm not very familiar with Linux, but I imagine I will become increasingly more accustomed to it in the near future). Any ideas for trying out connectivity on Linux?
Click to expand...
Click to collapse
When you connect your phone via USB, does a USB connected symbol show up on your phone? Does the battery start charging?
You can issue the following command in the terminal window - should be in Applications->Accessories on Ubuntu (it resembles MS-DOS window under Windows OS)
Code:
lsusb
If the Samsung device shows up the USB port on your phone should be working, if however it is not showing up you might have a bigger problem with your phone
Thanks again lqaddict, I'll give it a try..
EDIT: Alright, to answer your first question: yes when I plugged it in while off, it does give the battery charging icon, as well as it does give juice to the battery.
Additionally, I ran the suggested "lsusb" in the Linux Terminal while the Vibrant was in Download Mode, and I didn't seem to get too much in the way of interest of the Vibrant except this line:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Click to expand...
Click to collapse
Would that possibly be the Vibrant? Does "Linux Foundation" refer to a Linux device? Then again, I just ran it another time without the Vibrant plugged in, and it yielded the same results.. So, most likely.. dead usb port?? Or perhaps is this just a weird phenomena? Thanks again, for all the suggestions and comments; hopefully I'll be able to one day return the favours to others here on xda.
Sorry, looks like you have a faulty usb port on your phone
Sent from my Nero powered Vibrant
Thanks for helping troubleshoot that, however unfortunate it was to hear... Perhaps one last question though, as I would like to make sure I 'cover my basis', so to speak, would anyone have suggestions as to what to do when I talk to Samsung? Or would anyone know what the procedure is like; I have dealt with a faulty iPone 3gs before and basically all I did was wait for the replacement in the mail, and ship the faulty one in the same packaging. I realize I will need to contact them, but would anyone know what information they might need from me? (as in would it be a problem that I might not have an original receipt? (I contacted the seller about that, and have yet to hear back))
Simply put, while I have had Samsung products in the past (and have been for the most part very satisfied with said products); I would, however, like to make sure I don't mess something up within the warranty process for the Vibrant (at least in consideration that I wasn't the first purchaser; then again, I would hope that they would cover the 'basic' quality issues of their products for at least the normal 90 days.. but what do I know..).
Whatever the case my be, I greatly appreciate the help I've received here; if for nothing else, perhaps it will be useful in someone else's mishaps in their Android journey. Thanks again, and I will be exceedingly grateful for any further suggestions on the matter.
shalom24 said:
Thanks for helping troubleshoot that, however unfortunate it was to hear... Perhaps one last question though, as I would like to make sure I 'cover my basis', so to speak, would anyone have suggestions as to what to do when I talk to Samsung? Or would anyone know what the procedure is like; I have dealt with a faulty iPone 3gs before and basically all I did was wait for the replacement in the mail, and ship the faulty one in the same packaging. I realize I will need to contact them, but would anyone know what information they might need from me? (as in would it be a problem that I might not have an original receipt? (I contacted the seller about that, and have yet to hear back))
Simply put, while I have had Samsung products in the past (and have been for the most part very satisfied with said products); I would, however, like to make sure I don't mess something up within the warranty process for the Vibrant (at least in consideration that I wasn't the first purchaser; then again, I would hope that they would cover the 'basic' quality issues of their products for at least the normal 90 days.. but what do I know..).
Whatever the case my be, I greatly appreciate the help I've received here; if for nothing else, perhaps it will be useful in someone else's mishaps in their Android journey. Thanks again, and I will be exceedingly grateful for any further suggestions on the matter.
Click to expand...
Click to collapse
Contact Samsung what have you got to lose? The phone comes with 1 year manufacturer warranty, and it has been on the market since mid July 2010, so it is not even 6 month old.
Yea, I don't mean to be too non-committal, I just don't want to mess up a warranty; if that makes any sense. And hopefully the ~210 people who have viewed this thread thus far will find a conclusion of the situation somewhat helpful. I'll update this thread once some of the dust settles.. I'm most definitely a fan of xda! Thanks for all the help everyone!
EDIT: Contacted Samsung, and after listening to the 'did you check this list' for about five minutes, I received a free shipping label and they said it was covered by the 'repair warranty'. I'm optimistic that something good will come of it...
EDIT_2:
Well, what do you know, just got the package/phone a little under an hour ago. First of all, compliments to Samsung! Fantastic communication and customer service! I really thought that the Vibrant was unrecoverable and that I would most likely have to pay for a new one; but I was wrong! Opened the sealed package with the original Vibrant (I knew it was mine since I had already but a BestSkinsEver skin on it) and plugged it into the computer at, Wohla!, Odin recognized, Windows/drivers recognized, and I'm up and rolling!
Thank you once again everyone for the comments and helpful input! And know that Samsung rocks! (I won't be going back with apple products anytime soon..)
Dammit Dammit Dammit! lol I have had the Dev preview on another SSD since the day it launched, and guess what happens? My Win7 Ultimate SSD crashed, so I feel all high and mighty I start diving into Win8 for real instead of just playing around and BAM Moto Drivers don't work with Win8 yet because they "Don't recognize the OS". My computer basically told me to get ****ed and that I can't root my brothers phone. I refuse to go back to Win7, guess I will go play on someone else computer!
Just thought I would give you guys a heads up, in case you wanted to migrate onto the Dev Preview or an Alpha/Beta. This is where it stands right now.
Windows 8 Dev Preview has Windows 7 compatibility mode... Right click the installer and set them to install that way. Let us know if that works....
Nope, I had tried that already.
Damn.... That's a pretty crappy bro... I tried it out on a spare HDD I had for a few days and the whole Metro interface being designed for a touch screen device just got cumbersome and I only tried installing some basic stuff like office, chrome, skype, and other things like that....
Most software works(even processor intensive CAD/Revit, Adobe CS5 products), and I rarely even see the Metro UI, I don't use it for anything. I just have my desktop extended across both screens.
True... I have an old dell lappy I might throw it on there and play with it some more.... Maybe that will make it heat up less....
I had to revert back to Windows 7 (no big deal) because I had trouble SBFing in Windows 8.
Meticode said:
I had to revert back to Windows 7 (no big deal) because I had trouble SBFing in Windows 8.
Click to expand...
Click to collapse
Yea, for the same reason, lol. I am not too worried though. I am upgrading to the ReZound on Monday. But, I thought I would post this. I am sure there is someone smart enough to adapt the drivers, or knows another way we are not thinking of.
Could probably always partion the drive and have 7 or xp on another partition...
Hopefully this will be fixed when they decide to release Windows 8.
motcher41 said:
Could probably always partion the drive and have 7 or xp on another partition...
Click to expand...
Click to collapse
I have 4 500GB HDD's 1 1TB HDD and 2 256GB SSD's. I have plenty of space for Win7, but after being on Windows 8 there is no going back. Not to mention I don't want to set up an entire system just to root a phone I will only have for 3 more days
I was thinking about trying that other root method because it doesn't say anything about drivers, although, that might just be an obvious given. We will see, and I will let you guys know probably tomorrow. I am a Veteran, got things to do today that don't involve sitting in front of a computer lol.
BTW, Happy Veteran's Day to my fellow Brothers-in-Arms and Veterans alike! RLTW!
No Bueno...
I found elsewhere on the net a solution to windows 8 problem...
Extract the usb drivers from the motorola's driver MSI using Uniextract to a easy to find folder, then go into device manager and find the 'unknown usb device' and manually update drivers by pointing to the drivers you just extracted. Hope all that makes sense....
I should note that while this method has gotten me farther than I had previously, and allowed RSDlite to work SBF'ing my phone back to stock, but it seems ADB doesn't want to play nicely with windows 8. I've tried windows compatability mode, run as admin. no luck so far.
I don't have much of a clue of what I'm talking about but maybe its worth a shot...what if you ran a virtual of 7 inside of 8? Would you be able to use the drivers that way?
Sorry if I woke an older thread. Just curious..
We condemn you to xda hell
Sent from my MB870 using xda app-developers app
I recently picked up a Samsung Admire. It has Gingerbread 2.3.4, and my computer's running Vista 64. When I first got, it showed up on My Computer, but then it randomly stopped. I've tried everything I can think of to no avail. I've swapped USB ports, tried uninstalling and reinstalling the drivers, tried getting drivers directly from Samsung's website, tried debugging mode, tried going into Device Manager to find it there (where it does show up under Disk Drives and says it's working properly, but I can't do anything with it from there), etc, and still nothing. I've looked a several posts on here about it, too (which is where I got the uninstall/reinstall idea), but no luck (I'll admit I didn't understand some of what was said, as well...I'm not a phone guy, really). It's a brand new cord, too, in case someone mentions that.
It would be nice to be able to put stuff on it, so if anyone has any ideas, I'd certainly appreciate it.
Are you pulling down the status bar (at the top of the phone), and selecting 'Enable USB Storage'? Most android phones can connect to the computer and be seen by the device manager, but until the phone is told "OK, communicate with the computer", it will not actually let the computer access the file system.
ambiate said:
Are you pulling down the status bar (at the top of the phone), and selecting 'Enable USB Storage'? Most android phones can connect to the computer and be seen by the device manager, but until the phone is told "OK, communicate with the computer", it will not actually let the computer access the file system.
Click to expand...
Click to collapse
Oh yah, I forgot to mention it doesn't show up either way, whether that's enabled or not.
I guess I'll take it into the MetroPCS store and see if they have any ideas on what's up. I need to take it there anyway to find out why my reception is so constantly horrid. Worst reception of any phone company I've ever been with, and I've been with a few.
salihe66 said:
I recently picked up a Samsung Admire. It has Gingerbread 2.3.4, and my computer's running Vista 64. When I first got, it showed up on My Computer, but then it randomly stopped. I've tried everything I can think of to no avail. I've swapped USB ports, tried uninstalling and reinstalling the drivers, tried getting drivers directly from Samsung's website, tried debugging mode, tried going into Device Manager to find it there (where it does show up under Disk Drives and says it's working properly, but I can't do anything with it from there), etc, and still nothing. I've looked a several posts on here about it, too (which is where I got the uninstall/reinstall idea), but no luck (I'll admit I didn't understand some of what was said, as well...I'm not a phone guy, really). It's a brand new cord, too, in case someone mentions that.
It would be nice to be able to put stuff on it, so if anyone has any ideas, I'd certainly appreciate it.
Click to expand...
Click to collapse
Hi, i had the same problem with my admire but i have just recently found newly released drivers for the samsung from their website and now i have no issues with it anymore, you have to download the drivers for the samsung indulge YES THE INDULGE and it will operate perfectly..
Here's my problem XDA Gods:
I've recently made a huge mistake, I was %&$#ing around with roms for the HDX and with Hashcode's Safestrap and had my phone fully rooted with the ADB drivers installed on my pc. I was using the default rom slot to operate(Yes it's stupid, but I have problems working with under 8gb of space and it was working fine.). Through an accidental factory reset I managed to delete my safestrap backup and screw up the current Rom. So I went into safestrap and tried to flash a new rom which suddenly wouldn't flash correctly. So I did advanced wipe and cleared everything and rebooted the device whilst still set to bootup from the default rom slot. My Proceeded to then bootloop the grey kindle logo. In a panic trying to fix it, I did the factory reset by holding the volume and power buttons (Another stupid move in my game of life.). Now when I plug it into a PC it reads the device as MTP USB Device and proceeds to fail installing Drivers that I've already installed. Adb wont recognize the device and I'm currently attempting to reinstall all my drivers.
To Sum It Up:
* My Device Can't Boot Into Safestrap
* My Device Can't Boot Past The Kindle Gray Logo
* My Computers wont recognize the kindle and calls it an MTP USB Device and fails driver installation.
*ADB also rejects my love.
Dear XDA Gods, I pray to thee for divine help and request the speedy help of thy talents. Many goats I will sacrifice for any that will help. I have scoured the Internet looking for a holy answer and have stumbled only upon ADB fixes to which I cannot. Please look upon my request and help me fly through this terrible storm.
From what I understand...
...this is a brick situation. Not to be a debby downer but I found myself in the same situation. I spent countless hours in the XDA forums and beyond, read every Android Cowboy post (who knows his way around this issue), tried a fastboot cable (didn't work), and even looked for a way to JTAG the internal memory - all to no avail. My advice - if you can't get ADB to wreckonize, accept your fate and flaunt your expensive taste in paperweights because, indeed, the stakes of being a tinkerer are high.
zomblitous said:
Here's my problem XDA Gods:
I've recently made a huge mistake, I was %&$#ing around with roms for the HDX and with Hashcode's Safestrap and had my phone fully rooted with the ADB drivers installed on my pc. I was using the default rom slot to operate(Yes it's stupid, but I have problems working with under 8gb of space and it was working fine.). Through an accidental factory reset I managed to delete my safestrap backup and screw up the current Rom. So I went into safestrap and tried to flash a new rom which suddenly wouldn't flash correctly. So I did advanced wipe and cleared everything and rebooted the device whilst still set to bootup from the default rom slot. My Proceeded to then bootloop the grey kindle logo. In a panic trying to fix it, I did the factory reset by holding the volume and power buttons (Another stupid move in my game of life.). Now when I plug it into a PC it reads the device as MTP USB Device and proceeds to fail installing Drivers that I've already installed. Adb wont recognize the device and I'm currently attempting to reinstall all my drivers.
To Sum It Up:
* My Device Can't Boot Into Safestrap
* My Device Can't Boot Past The Kindle Gray Logo
* My Computers wont recognize the kindle and calls it an MTP USB Device and fails driver installation.
*ADB also rejects my love.
Dear XDA Gods, I pray to thee for divine help and request the speedy help of thy talents. Many goats I will sacrifice for any that will help. I have scoured the Internet looking for a holy answer and have stumbled only upon ADB fixes to which I cannot. Please look upon my request and help me fly through this terrible storm.
Click to expand...
Click to collapse
---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------
Google "Setting Up Your Kindle Fire Tablet for Testing" there is an article that might help to get ADB up.
This may be helpful to try to get ADB working. Also, a fastboot cable might be worth a try, though I don't think it will work if you don't get ADB working. Did you modify build.prop? Delete any system files?
I am sure that there is a way to restore through QPST:
http://forum.xda-developers.com/showthread.php?p=49862146
but I lack the skills to complete this process
Thanks
Thanks for the speedey responses guys, I'll try the QTSP method when I have time, but still thanks. Any other help is good to.
Same happened to me also , and i contacted with Amazon Customer Service. I explained whole situation ( that i tried the install gapps and bricked it like you - same way - ) they offered me a replacement. Then they sent me a new Kindle.
If you cant do anything just contact with them and explain everything. They will help im sure about that.
They are the most amazing Customer Service i've ever seen in my life. Just 2 days , i got my new Kindle and sent bricked one back.
Also they sent me a email for return shipping expenses. I used it at UPS and did not paid any money for return shipping.
Aren't they amazing?
Really!?!?
squee9 said:
Same happened to me also , and i contacted with Amazon Customer Service. I explained whole situation ( that i tried the install gapps and bricked it like you - same way - ) they offered me a replacement. Then they sent me a new Kindle.
If you cant do anything just contact with them and explain everything. They will help im sure about that.
They are the most amazing Customer Service i've ever seen in my life. Just 2 days , i got my new Kindle and sent bricked one back.
Also they sent me a email for return shipping expenses. I used it at UPS and did not paid any money for return shipping.
Aren't they amazing?
Click to expand...
Click to collapse
So even after ""breaking the system"" I'll get my money back. I dont have a warranty by the way, and I got it in December. Will that effect anything.
zomblitous said:
So even after ""breaking the system"" I'll get my money back. I dont have a warranty by the way, and I got it in December. Will that effect anything.
Click to expand...
Click to collapse
I have to admit I went through something very similar to you with my first HDX. I wiped the system without fully understanding it and afterwards it was bricked with my computer being unable to recognize it.
I also spent quite a bit of time looking for a solution but ultimately it was far easier talking to Amazon about this and having them send a replacement. Now with my second HDX I didn't make the same mistake twice.
I didn't tell the truth though. I just said that after I powered it on one day it would get stuck on the boot screen and after a troubleshoot run through Amazon offered a replacement.
Good luck.
Fastboot & the system
lawnnewm said:
...this is a brick situation. Not to be a debby downer but I found myself in the same situation. I spent countless hours in the XDA forums and beyond, read every Android Cowboy post (who knows his way around this issue), tried a fastboot cable (didn't work), and even looked for a way to JTAG the internal memory - all to no avail. My advice - if you can't get ADB to wreckonize, accept your fate and flaunt your expensive taste in paperweights because, indeed, the stakes of being a tinkerer are high.
---------- Post added at 12:18 PM ---------- Previous post was at 12:04 PM ----------
Google "Setting Up Your Kindle Fire Tablet for Testing" there is an article that might help to get ADB up.
This may be helpful to try to get ADB working. Also, a fastboot cable might be worth a try, though I don't think it will work if you don't get ADB working. Did you modify build.prop? Delete any system files?
Click to expand...
Click to collapse
Well I did the advanced system wipe, I think I may have just wiped off all traces of a rom by formatting the system, I havent touched the build.prop or any file like that, only format. Also I'll grab a fastboot cable off ebay and give tinkering a try,
Thanks
zXiC said:
I have to admit I went through something very similar to you with my first HDX. I wiped the system without fully understanding it and afterwards it was bricked with my computer being unable to recognize it.
I also spent quite a bit of time looking for a solution but ultimately it was far easier talking to Amazon about this and having them send a replacement. Now with my second HDX I didn't make the same mistake twice.
I didn't tell the truth though. I just said that after I powered it on one day it would get stuck on the boot screen and after a troubleshoot run through Amazon offered a replacement.
Good luck.
Click to expand...
Click to collapse
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
zomblitous said:
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
Click to expand...
Click to collapse
Rubbish. A bad kindle is a temporary thing. Bad karma lasts a lifetime & even if you can work it off, it's on a sliding scale approximately 1000:1.
The worst thing you can do is panic. 99.999% of devices can be recovered. However, you greatly increase your chances of being in that screwed .001% statistically by panicking & doing things like factory resetting or rebooting.
Personally, after sitting down to think about it, I can say I have actually borked my device 23 times. Nearly every three times, it was a different issue, since I was recreating issues to find solutions for others. To this day, I still have my FIRST HDX. I even got the update, the one that nobody can reverse. Guess what? I'm rooted, have SafeStrap & GAPPS still, because I didn't panic.
When you screw something up, you have to walk away. 3 out of 4 times, if you react to an issue without planning & reasoning, you will only make things worse, particularly if you really have no idea what you are doing & how Linux, Android Bootloaders & firmware in general work together. You don't need to know every detail, but a basic understanding at the very least. Listen, I am by no means a developer. I am a butcher hack of a coder, but I am a mechanical engineer & so I approach everything methodically, especially when dealing with something I do not know. Knowing your limits can be the most important thing to know at times & when you have stepped outside of your knowledge base, reacting with a guess rarely goes good. Just ask all the folks leaving Las Vegas casinos without their money. The bottom line is that bad things happen when you panic & let fear take hold. Bad things happen when you think you know more than you do.
What also helps me, is that this is my NEWEST username (you used to be able to have multiple, for different devices, etc), which is from 2006. I am pretty sure my first login was from 2002, maybe early 2003. When I joined I didn't do anything other than lurk, read, ask questions & follow things that interested me in IRC for a year & a half. I never even posted for the first 9 months I was around. I used PM & IRC, then it was only to ask questions to things I could find answers too reading through the earlier posts. Again, there are brand new members that understand & have abilities in technology that far outstrip anything I'll ever comprehend. Just like there were over a decade ago. Find those people & become friends. Follow one of the tutorials on building a basic app or building a rom like CM or AOSP or any of the other open roms from scratch. You'll learn something new, I garuntee it & it will come in handy some day, even if it's just a hobby. Of course things are different at XDA these days. It used to be that EVERY member was here to learn how to do these things for themselves & to share the experience & what was learned. Now, you still have some of those types, but predominantly, you have members that are here just because they want someone else to make a theme, or mod, or fix for them & they have no desire to contribute.
At any rate, I don't have the time to keep up with all the bootloops & bricks these days. Right now, work is crazy busy & that is what pays the bills, so it takes precedence over everything else. I'll start answering PM's & taking a look at borked devices again when things slow down again, however, I think I could probably recover 8 out of 10 if I had it in my hands & so could you. For those of you unwilling to give up, I suggest you read around other forums, check out some of the qualcomm developer forums & find some of the very talented developers that participate in those communities too. Most of them WILL take the time, not necessarily to fix your problem, but to answer questions & even to teach you a thing or two, if you are sincere about wanting to learn & not just looking for the first sucker to fix whatever problem you have.
GSLEON3 said:
Rubbish. A bad kindle is a temporary thing. Bad karma lasts a lifetime & even if you can work it off, it's on a sliding scale approximately 1000:1.
The worst thing you can do is panic. 99.999% of devices can be recovered. However, you greatly increase your chances of being in that screwed .001% statistically by panicking & doing things like factory resetting or rebooting.
Personally, after sitting down to think about it, I can say I have actually borked my device 23 times. Nearly every three times, it was a different issue, since I was recreating issues to find solutions for others. To this day, I still have my FIRST HDX. I even got the update, the one that nobody can reverse. Guess what? I'm rooted, have SafeStrap & GAPPS still, because I didn't panic.
When you screw something up, you have to walk away. 3 out of 4 times, if you react to an issue without planning & reasoning, you will only make things worse, particularly if you really have no idea what you are doing & how Linux, Android Bootloaders & firmware in general work together. You don't need to know every detail, but a basic understanding at the very least. Listen, I am by no means a developer. I am a butcher hack of a coder, but I am a mechanical engineer & so I approach everything methodically, especially when dealing with something I do not know. Knowing your limits can be the most important thing to know at times & when you have stepped outside of your knowledge base, reacting with a guess rarely goes good. Just ask all the folks leaving Las Vegas casinos without their money. The bottom line is that bad things happen when you panic & let fear take hold. Bad things happen when you think you know more than you do.
What also helps me, is that this is my NEWEST username (you used to be able to have multiple, for different devices, etc), which is from 2006. I am pretty sure my first login was from 2002, maybe early 2003. When I joined I didn't do anything other than lurk, read, ask questions & follow things that interested me in IRC for a year & a half. I never even posted for the first 9 months I was around. I used PM & IRC, then it was only to ask questions to things I could find answers too reading through the earlier posts. Again, there are brand new members that understand & have abilities in technology that far outstrip anything I'll ever comprehend. Just like there were over a decade ago. Find those people & become friends. Follow one of the tutorials on building a basic app or building a rom like CM or AOSP or any of the other open roms from scratch. You'll learn something new, I garuntee it & it will come in handy some day, even if it's just a hobby. Of course things are different at XDA these days. It used to be that EVERY member was here to learn how to do these things for themselves & to share the experience & what was learned. Now, you still have some of those types, but predominantly, you have members that are here just because they want someone else to make a theme, or mod, or fix for them & they have no desire to contribute.
At any rate, I don't have the time to keep up with all the bootloops & bricks these days. Right now, work is crazy busy & that is what pays the bills, so it takes precedence over everything else. I'll start answering PM's & taking a look at borked devices again when things slow down again, however, I think I could probably recover 8 out of 10 if I had it in my hands & so could you. For those of you unwilling to give up, I suggest you read around other forums, check out some of the qualcomm developer forums & find some of the very talented developers that participate in those communities too. Most of them WILL take the time, not necessarily to fix your problem, but to answer questions & even to teach you a thing or two, if you are sincere about wanting to learn & not just looking for the first sucker to fix whatever problem you have.
Click to expand...
Click to collapse
Thanks for the pep-talk, I haven't even thought about giving up, and I don't really want to just get out the easy lying way. But sadly my problem is one of few and will take time even with the help of power techies. I really only have one option at the moment and that is to continue troubleshooting and ignore everyone who just says that i have acquired a taste in paperweights. And Thanks anyway, means alot when a member takes time just to cheer ya on.
zomblitous said:
Well, best to have a working kindle and bad karma than an expensive paperweight, i'll give a fastboot cable a try first and use this as a last attempt. Thanks, also, when did you get the replacement and did you have a warranty?
Click to expand...
Click to collapse
Replacement was expediated by Amazon so in two days.
You have a limited warranty for a year. You just have to convince Amazon that your problem falls under that.
Edit: It's admirable to try and fix it yourself but in my opinion it's far too time consuming.
1 year then...
zXiC said:
Replacement was expediated by Amazon so in two days.
You have a limited warranty for a year. You just have to convince Amazon that your problem falls under that.
Edit: It's admirable to try and fix it yourself but in my opinion it's far too time consuming.
Click to expand...
Click to collapse
Well I have about a year then.
Sorry if this is in the wrong subforum, and I'm sorry to cause trouble if you have to move it. I've been a google-searching lurker for years now, but I made an account just to ask this question so again, I'm sorry if I placed it wrong.
Yes, I have a good old Pantech Pocket P9060, good ol' 2.3. I love the little thing but like always, I want to get this thing rooted. I've rooted before, but it definitely wasn't as difficult as this thing.
Every website I've been to, and my google searches are all purple links now I've been at this for hours, make it look so fracking easy (it's such an older model, after all), but for some reason mine just won't budge.
I downloaded and installed JDK, I've got the ADT bundle, I've downloaded the packs, I've got the drivers, I've got SuperOneClick, I've unmounted the SD card, I have it in USB debugging mode, I've followed all these webpages to the letter and for some reason it just won't work for me. I've done literally everything, but obviously there's gotta be something I'm not doing hidden in the void that is the steps to get this thing rooted.
I've tried having the SD mounted, I've toggled a few options, I've reset the phone while it was plugged in, I've manually updated the drivers...nothing.
There was even one page that said to dial some #*#* number but it wouldn't let me type in the whole thing, it was one * character too long. I just can't do it.
S1C keeps freezing at "starting adb server" which I see is a common problem, except they usually end up getting it resolved by doing something that, in the end, doesn't work for me. I'm past the point of pulling my hair out. What is this things problem? What am I missing?
Again, sorry if this is out of place.