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..)
Got my gTab yesterday. [VERY EXCITED!]
Plugged in wall outlet, waited 4 hours to charge.
Connected to WiFi.
Updated TapnTap, as instructed.
My Vist Ultimate computer didn't see the gTab when I plugged it in, at least not so I could get to the root directory.
So I went to an old XP and tried that. It worked.
Wanted to Root it, so I installed (sorry if that's not the correct word) ClockworkMod v08.
So far so good.
Then rooted TnT Lite v 4.2
Still good.
Then rooted TnT Lite suppl 4.25
STILL okay.
Then went to gMail. Added my gMail account. (An account I use for business.) It took a LONG time to do whatever it was doing. So I went to do something else, thinking it would continue doing it's thing in the background. I was wrong. It messed up, and I kept getting error messages.
Next thing I know, I'm somehow in that infinite boot loop.
It was about 2 am, and I was tired, and... panicked!
Next thing you know I'm freaking out and went hog-wild (while following directions to the letter), to get my brand new toy to work.
I did nvflash windows, still infinite boot loop. I tried putting the vanilla recovery 3588 on there. Still infinite boot loop.
Kept at things, trying everything I read, and STILL... infinite boot loop.
Then I figured it was time to try to get my Vista computer working so I wouldn't have to keep transferring stuff from the Vista to the XP to the miscroSD card to the gTab, and followed directions about APX mode.
I was delirious, exhausted and scared, and kind of went postal (in a frenzied OCD sort-of way), trying everything and anything to get rid of the infinite boot loop.
Now it won't even power up. (AT ALL!) I think I gave it a heart attack, or possibly a stroke. And that's with not even owning it for 24 hours!
I've tried the long 45 second power hold, then the short one. [Did that about 37 times.] I've tried power and Vol+. Nope. Then did a few power and Vol-, just to really freak the poor sick, dead thing out. [Like kicking the proverbial dead horse, I guess. Trying to see if there was any life left in it.] I even read to turn off the lights to see if there was a faint glow. But nope. No glow.
I will now follow the directions from another post, and will let it just sit for 24 hours (if I can survive the wait) to let the battery discharge and then see if it will boot. [After this nightmare, there is no WAY I will take off the back and hit the reset button--thereby definitely voiding my warranty.] But I hope I'm not like the woman from the forum thread: http://forum.xda-developers.com/showthread.php?t=968177
If I am, and can't get this thing to power up, do you think WOOT will let me return it???? I'm so upset that I broke my new toy so quickly. If anyone has any suggestions about getting this thing to boot up, I'd appreciate it. [at this point, I'd be happy to have it boot up in the infinite boot loop!]
Oh, and one last question, how does having it turned off (because I can't turn it on) and sitting there drain the battery to the point that it needs to start fresh after a mere 24 hours with no activity? Is that typical for tablets?
THANK YOU to anyone who can offer advice on what to try next or how to remedy this problem. Please keep in mind that I am good with PCs and laptops/netbooks, but am VERY new to this whole android and tablet things, so if you send instructions, please give implicit directions (as though you are instructing a 3-year-old), without feeling as if you are insulting me. [Please believe it's what I need, and will appreciate. As will the other wooters who just turned their gTabs into brinks] And know that you will be helping Roebeet by answering my questions, because the poor guy must be exhausted from all of us lay-peoples' foibles and mess-ups. [The man seems to be a God at this site!]
Did you do what is mentioned right after step 10 in this thread?
http://forum.xda-developers.com/showthread.php?t=865245
"If your tablet bootloops…Also may be required to get market running correctly on some ROMs...
Press and hold the power button to shut the device down. Boot back into Clockwork. Select the advanced option at the bottom, then go to “partition SD card”, for the first option select 2048, and for the second option select 0. Then, redo steps 7-10. This erases all data on your tablet, including backups."
But first... switch to decaf and get some rest... ;-)
Panic doesn't help.
It might actually be powering up but staying in APX mode. I've seen one do that. If that's the case you can still nvflash it back to normal. Let it charge for 15-20 minutes and leave it on the charger. Try to start it up and see if your pc can see it.
You maybe got the bootloop because your tab had sleep death while syncing. Was the error you got by chance something like process.acore? If so that is a classic error that happens after syncing contacts, sometimes there are empty contacts with no data that make the tab go nuts. Simply deleting the bad contacts solves the problem.
A simple wipe data/cash/davlic would have been the first place to start. Breathing helps when stuff goes wonky.
If you can get it to recovery a repartition is totally necessary. Deffinetly... and maybe some whiskey ....
Good luck.
good luck with woot return, dont even think they do it.
I wouldn't worry about the warranty. You already voided it when you rooted the device.
I'm so sorry, guys, I didn't check off the subscribe notification, so I didn't know that anyone had written.
cdavisccs28, I didn't do that while the tablet was boot looping, but somehow it went from bootlooping to complete death.
K J Rad, it wasn't charging, and wouldn't boot. [And you can probably guess, I tried numerous times.]
Mantara, the death in the middle of syncing certainly didn't help it, and, as you suggested, might have been the last nail in the coffin. The whiskey suggestion was funny! Actually I, personally don't drink, but as you might have deduced, I'm a carrier. [AKA: I've been told that I drive people to drink.]
spike378 & filterking: Yup, I think you are both correct. How I managed to spike from "excited as a schoolgirl" to "completely tanking" in less than 24 hours amazes even ME! [And I know me, and am used to me! I think that was a personal record!] [If I don't laugh about it, I'll cry!]
THANK YOU ALL for replying! Your time and concern meant a lot to me, but I think this baby is totally bricked! Elvis has DEFINITELY left the building! If I do get another one (I'll have to start saving again), I might be too afraid to play with it. I really am good with PCs and notebooks, so I might just keep staying with what I know. YOU GUYS ROCK, for trying to help me, and I really appreciate it!
Same problem. I booted the device up, and connected it to WiFi. Then it gave a popup where it asked to update to the newest version. I said okay, and let it do its thing. Then it restarted into a bootloop. So, I turned the device off, and tried to turn it back on, except -- nothing. With the USB plugged in, it's not recognized by the computer at any time after I press the power button. I've been trying to get it to boot for an hour now and it's still just sitting there with a black screen. Not even a backlight is showing. Anyone know of any solution? Or is it time to ask for an RMA from Woot!?
h.nocturna, WOW, you didn't even get to the part where you started doing everything and anything (in a frenzy) to get it to work properly! That might be a good thing, h.nocturna, because you haven't voided your warranty! You might need to send it to Viewsonic to be fixed (since it messed up while you were doing their update), but at least you can do THAT! I mailed my brand new brick to my son up in college and gave him this site, and told him to have a blast, and do whatever he wanted with it. [He's known me his whole life, and said even HE "can't fathom my destroying something so completely in less than 10 hours."] I wish you luck!
Oh, one more question that will help the masses, I'm sure. So how do you get your computer to recognize the device as a hard drive, when it is plugged in to a Windows PC (without voiding the warrenty, of course)? [Vista Ultimate does not recognize it, and neither did Windows 7.] Please give step-by-step instructions for the lay-person. [By answering this question, at least we will solve THAT problem for folks!]
badtypist,
I wrote you a fix last night and when I went to save it the Forums had been shut down and do it didn't save to post --
and I had been on the road and was exhausted and just couldn't stay up long enough to redo it if and when they came back up. Sorry.
You simply needed to find one solution and then let us get down the procedure to follow to fix it.
Several people in the past have gotten to the point where you were. I read two fixes.
One was some people were able to get the tab to start again by playing with the
power switch -- hold it for long, long times and then press a short startup, etc. Somehow they got that to reset and start.
Somewhere else in the forums -- and I have never done this with either of my tablets --
there are a few threads where someone in this kind of situation opened up
the tablet card and simply unplugged the battery for 10- or more seconds. There also
is a reset button inside the case as shown in an old thread where someone opened a
G-Tab up and took pictures.
If any of those three choices get to where you can either use power / volume - to get
into NVFlash more ---- or to where we can load CWM -- then you are in fair shape.
LOTS AND LOTS OF BOOT LOOPS ARE ASSOCIATED WITH PARTITIONING. Simply
getting into CWM and re-partitioning to 2048 and 0 and then using CWM to "Fix
Permissions" will get it working. CWM also will let you wipe the cache and wipe the
factory data, which sometimes will allow and NVFlash to come on up and work right.
You see, we were not dead by any stretch.
You might pass this on to the recipient of the tablet.
Also, so many people are trying to do so much that is over their heads -- and so many
people are borking their tablets -- that this site and the folks that can help -- just can't communicate. Sad day.
I wish you luck. Hope this helps.
Rev
EDIT: Well, I guess we missed the boat completely. Evidently she mailed of the G-Tab and checked
out for good!!!
Hi Rev! Sorry I didn't get back to you sooner. I TRIED to get back to you sooner, but I think this site was down, because it kept timing out and wouldn't let me get to the site OR the conversation thread! I tried a few times, then tried later, and now just tried again!
I think you guys are getting BLASTED with desperate lay-people from the over 10,000 tablets sold on Woot who have "borked" their tablets. (That's a funny word, Rev! I hope I'm using it properly! And please note, although the WORD is funny, the actual situation is NOT funny!)
Yes, I mailed the offending frustration-linked object to my son, and can't "take it back," but perhaps I will beg for and borrow enough money to try again, sometime soon! If I do, I will come back here again sine I feel I have bonded with the wonderful, sharing folks on this site. (I'm a she, by the way, not a "he.") I admire (okay, worship) the folks who help us lay-people out so we don't sit alone crying and trying to power/Vol+ in solitude!
I've read your other posts previously, Rev, and you are so wonderful to help us n00bs! So please remember "badtypist" (hopefully with good thoughts) and when you hear my name again, let's hope it's to say... THIS TIME I ROOTED IT CORRECTLY!!!!
Thanks again, for your time, Rev AND the rest of you, which wasn't wasted, because I sent my son this link and he will (in his spare time) read through it to fix HIS new tablet. [I think he kind of liked that his mom messed up! He got a VERY expensive new toy, if he can fix it.]
Perhaps I'll talk with you soon...
badtypist (and bad ROOTER. Or is it ROOTERIST? Or maybe ROOTIST? Whatever the proper term, I think we can all agree that I AM bad at it!)
Gtab Update Problems
So, I would agree with some of the posts above. I would also point out that you have two options (or some combination of the two):
1. Try to return the tablet, or put in a warranty claim (the warranty specifically does not cover modification\rooting)
2. Try to fix it yourself
I tend to choose #2 f I think the chances are better than 50/50 in my favor. Also, if the hardware is okay, you can have it fixed in 20 minutes.
The experience that the OP went through is EXACTLY why I discourage newer g-tablet owners from rushing in and flashing alternate firmware to their tablet. I am often chided for this recommendation, but I believe that it is unwise to modify a brand new tablet.
If you still want to mod it, you should have a backup plan. I save my update file to an external USB drive. You should then be able to re-install the stock update by placing it on a microSD card. You need to rename it to update.zip, and add a file that tells it to look at the microSD card for an update. I am a but fuzzy on the specifics, but that file is named "command", and I found it somewhere here in the forums.
As I plan on modding my newer woot tablet (or maybe my older Sears one). I will first set this up, and will work out the details.
Hi buzzzard, thanks for the great info! VERY helpful. I did see that video while researching the gTab, but didn't bookmark it, so I appreciate your adding it here! My son will see all your posts and will use all of your suggestions to try to raise my brand new gTab from the dead! [It wasn't even in zombie mode when I shipped it to my son, so we'll see what happens! I'll keep ya'll informed.]
wasserkapf, you are probably right about not jumping in with both feet for us n00bs. And I most certainly don't mean to be disrespectful in ANY way, but I have a (serious) question... if I'd kept the tap-n-tap and played with it for a while, how would that have changed things for me if I eventually decided to root it to a faster, better OS? [I'm not meaning this sarcastically, I really want to know what I'd have to learn in order to change the results I had, in case I ever do this whole process again, or in case others out there are (hopefully) learning by my mistakes.] What would you suggest lay-people should be learning about the gTab BEFORE attempting to root it? [The answer to this question wil help a LOT of folks!]
buzzzard,
I have always understood -- and I don't want to know bad enough to spend the time
researching it -- that the warranty is void when you load non-standard software.
And even if it were not, I have real questions about messing up a computer and then
taking it back to the seller as if it were faulty. Seems to me there is a dishonesty
component in that equation.
I think modders SHOULD accept the risk that they can trash their tablets -- and that
if they do then the loss is theirs.
Rev
P. S. -- I've tried to say this much without starting a flame war -- if you do I won't
answer you and will ask the moderator to close and hide the thread.
badtypist said:
wasserkapf, you are probably right about not jumping in with both feet for us n00bs. And I most certainly don't mean to be disrespectful in ANY way, but I have a (serious) question... if I'd kept the tap-n-tap and played with it for a while, how would that have changed things for me if I eventually decided to root it to a faster, better OS?
Click to expand...
Click to collapse
For one, this will give you time to read up and learn more. I can tell that you are confused by all of this. You don't "root it to a faster OS". Rooting is a method to gain root privileges on the tablet. To you windows users, root is the equivalent of Administrator. There also is only one OS available for this tablet, and that is Android. Some have made modified/customized versions of Android, but it is still Android.
[I'm not meaning this sarcastically, I really want to know what I'd have to learn in order to change the results I had, in case I ever do this whole process again, or in case others out there are (hopefully) learning by my mistakes.] What would you suggest lay-people should be learning about the gTab BEFORE attempting to root it? [The answer to this question wil help a LOT of folks!]
Click to expand...
Click to collapse
There seems to be the misperception that you have to install a custom firmware to get root privileges or Android Market access. This can be done on the stock firmware, and then makes the tablet much more useful.
butchconner, I know you weren't talking to me, but I am taking full responsibility, and am hoping my son can resurrect my gTab, and I DO hope there will be no flaming, as well. ["There's no need for flaming. It's unsportsmanlike, kind-of rude and unproductive," said the mom to all reading this thread. So please don't flame so this won't get deleted for other poor people who "bork" their gTabs.]
badtypist,
wasserkapf was around when I got my first G-Tablet -- when we were all getting started last November.
You have no idea how bad the software was back then and the things we had to do to make things work.
It wasn't a question of 10 different ROMS and whether it was fast or not -- it was a question of making it work.
But I agree with wasserkapf (and I don't mean this comment particularly at you ) that
people are trying to do too much to fast. In addition to being a minister, I also was
an exec in the IT field for 30 years. I learned to read the docs, to move slow, to make sure each step was
successfully completed before moving on, to test things that
I'm not sure of -- and a whole host of other things that IT people use to operate their
company's systems without crashing it and losing data.
I helped a guy along the way who said he was inexperienced and that his tablet was in
the same kind of situation yours ways. He had gotten his G-Tab, charged it up, and had loaded EVERYTHING he could find on it.
Three or four different ROMS including an
experimental ROM he had been warned was risky. Yet he was having to ask what
recovery was and where to look for files and other basic questions.
I think everybody should get their tablet, upgrade to the latest version of stock, install z4root and
Titanium Backup and learn to use them, then install the latest version of Angry Birds and whatever useful software they need -- and then enjoy
that for a while while they learn the ins and outs of modding.
I help people because of the kind of person I am and because I am retired and have
some time to devote. But I also will be honest and tell you this -- I don't suffer
obnoxious, foolish people well -- and there are folks I just don't help because someone gave them good advice
and they didn't listen........I help folks who need and deserve to be helped.
The alternate ROMs are nice. And it's neat to add market and other useful stuff to
your tablet. But none of those kinds of things are so important that they are worth
what some folks do.
Nuff said. I don't respond to flames. And when you have been helping people as long
as I have, then you can have your opinion.
Peace,
Rev
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.
I just want to start off by saying that I don't know too much about rooting or much of Android/Amazon OS in general. I have had my (Apollo) Fire HDX 8.9" since March 2, 2013. I have side-loaded apps and I am just a typical user. I know how to modify applications and such, so I know a bit but probably not as much as I should. I'm up-to-date with a lot of tech, but not all the rooting stuff. Anyway... Last night (November 25, 2015) I decided that I wanted to root. I started by finding some important info, specifically from this forum. (http://forum.xda-developers.com/kindle-fire-hdx/general/rollback-13-3-2-8-rollback-ota-captured-t3046204) So being as lazy as I am I did as much as I could without my computer and got 14.3.2.8 up and running over night. When I woke up I started the setup and enabled the wifi just quick enough to get ES File Manager. I got it installed successfully with no problems and turned off the wifi. After that I didn't really understand the OTA thing and TBH I still don't. I am assuming that is what updates my Kindle automatically. Anyway I just ignored that and moved on to my next step, installing 14.4.5.2. (Which I did on my computer.) After realizing my internet was really slow I decided to go reset the modem. Doing this messed up the modem and it kept going into "Limited mode". I had an idea that it could just be my Ethernet cable so to check that I turned my Kindle's wifi to see if I could connect through wireless. It still didn't work so I just decided to get ready for the day. This was around 11 AM (MST)(Thanksgiving 2015). When I am all done getting ready I go check my computer to see if my wifi is working, and it was finally working. So I go grab my Kindle, but now it wont turn on at all. I am assuming that this is a hard brick. I am still on 14.3.2.8 (I'm guessing that there is still stuff on my Kindle) and have no root and never did turn on developer options. When I connect it to my computer it takes a second and then say that it is unrecognizable. I am aware of "Restore2Stock", but I want to know if there are any other options. I don't want to spend $20 on a service that I don't necessarily trust. Anyone able to help???
My original post was a reply on a different thread. (http://forum.xda-developers.com/kindle-fire-hdx/help/help-thread-question-noob-friendly-t3206752/page11#post64025036)
DiaperBandit said:
I just want to start off by saying that I don't know too much about rooting or much of Android/Amazon OS in general. I have had my (Apollo) Fire HDX 8.9" since March 2, 2013. I have side-loaded apps and I am just a typical user. I know how to modify applications and such, so I know a bit but probably not as much as I should. I'm up-to-date with a lot of tech, but not all the rooting stuff. Anyway... Last night (November 25, 2015) I decided that I wanted to root. I started by finding some important info, specifically from this forum. (http://forum.xda-developers.com/kin...lback-13-3-2-8-rollback-ota-captured-t3046204) So being as lazy as I am I did as much as I could without my computer and got 14.3.2.8 up and running over night. When I woke up I started the setup and enabled the wifi just quick enough to get ES File Manager. I got it installed successfully with no problems and turned off the wifi. After that I didn't really understand the OTA thing and TBH I still don't. I am assuming that is what updates my Kindle automatically. Anyway I just ignored that and moved on to my next step, installing 14.4.5.2. (Which I did on my computer.) After realizing my internet was really slow I decided to go reset the modem. Doing this messed up the modem and it kept going into "Limited mode". I had an idea that it could just be my Ethernet cable so to check that I turned my Kindle's wifi to see if I could connect through wireless. It still didn't work so I just decided to get ready for the day. This was around 11 AM (MST)(Thanksgiving 2015). When I am all done getting ready I go check my computer to see if my wifi is working, and it was finally working. So I go grab my Kindle, but now it wont turn on at all. I am assuming that this is a hard brick. I am still on 14.3.2.8 (I'm guessing that there is still stuff on my Kindle) and have no root and never did turn on developer options. When I connect it to my computer it takes a second and then say that it is unrecognizable. I am aware of "Restore2Stock", but I want to know if there are any other options. I don't want to spend $20 on a service that I don't necessarily trust. Anyone able to help???
My original post was a reply on a different thread. (http://forum.xda-developers.com/kin...on-noob-friendly-t3206752/page11#post64025036)
Click to expand...
Click to collapse
As you probably realize your device is toast. Leaving WiFi enabled resulted in receiving an incompatible OTA (over the air) update from Amazon. There is no recovery.
Davey126 said:
As you probably realize your device is toast. Leaving WiFi enabled resulted in receiving an incompatible OTA (over the air) update from Amazon. There is no recovery.
Click to expand...
Click to collapse
So is there anything that I can do with my $300 tablet now called a brick? Can I call support and see of they can do something? I'm sad and I realize that it is my fault but I'm pretty over the top that my tablet now has a worth of a dime. I would expect there to be some sort of company that would buy my "brick". Like a junkyard for disfunctional devices. My guess it that there is not a single thing in the entire world that can fix this.
DiaperBandit said:
So is there anything that I can do with my $300 tablet now called a brick? Can I call support and see of they can do something? I'm sad and I realize that it is my fault but I'm pretty over the top that my tablet now has a worth of a dime. I would expect there to be some sort of company that would buy my "brick". Like a junkyard for disfunctional devices. My guess it that there is not a single thing in the entire world that can fix this.
Click to expand...
Click to collapse
Check eBay or similar auction sites to get an idea what your device is worth (very little) in its current state. To my knowledge there is no company that refurbishes bricked Kindles (at least HDX models) and no one on XDA has figured out how to resurrect crippled devices. Sorry for your loss.
Davey126 said:
Check eBay or similar auction sites to get an idea what your device is worth (very little) in its current state. To my knowledge there is no company that refurbishes bricked Kindles (at least HDX models) and no one on XDA has figured out how to resurrect crippled devices. Sorry for your loss.
Click to expand...
Click to collapse
Thanks for the help. I'll see how much I can get.
I'm in a position equal to his own , I have nuna 3rd kindle fire and think that just left on the wifi was going to be the tablet is useless crap ..
Friend anything that might serve to regain our fire I notice , just hope you do the same , never give that friend to relive our Kindle
I just replaced the motherboard in mine. The 16gb board I bought was $36
I just ordered a daughter board also. I must have damaged it also when I was messing with it.
I took the daughterboard out of my wife's to test just to make sure.
Daughterboard was $14
Bought both from ifixit but they are out of motherboards.
Google them and you should be able to find one.
Be patient removing the display from the back frame.
Just posted a thread with a link for motherboards.
Sent from my SM-N920T using Tapatalk
donharden2002 said:
I just replaced the motherboard in mine. The 16gb board I bought was $36
I just ordered a daughter board also. I must have damaged it also when I was messing with it.
I took the daughterboard out of my wife's to test just to make sure.
Daughterboard was $14
Bought both from ifixit but they are out of motherboards.
Google them and you should be able to find one.
Be patient removing the display from the back frame.
Just posted a thread with a link for motherboards.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Good stuff! Offers some hope for those with bricked devices (especially pricey Apollo/Saturns) and moderate skills in electronics disassembly/repair. At present there are few viable alternatives to the outstanding display and unique form factor of the HDX line. Thanks for sharing.
for some reason I am unable to use the laptop on this website so I am left stuck talking to my phone because it's too small to talk on anyways a quick briefing if you can follow my text.
I flashed my j33v 7 from my unknown source using Odin and it is a brand new spanking phone from Verizon and it is really screwed up with the wrong build number and the phone don't even look like a phone it has some kind of weird funny screen with a bunch of strange looking buttons it makes no sense to me and I cannot get it to go back in download mode I read somewhere I could use a 300,000 ohm resistors between pin 4 and 5 of the HDMI mini port to get it to boot back into download and I have yet to try it because I have not had time but anyways I have no backup of the image that come from the phone I'm not even sure how to create one or if anyone out there even has one can someone please help me figure this out I understand I could just purchase and be done with it a lot cheaper but apparently the build number to the software that was flashed on there it's the wrong one and I think I actually put a hacker flash on their stupid me haha very smart on my part huh but I had no help and I have not been on any forums this is my first post I accidentally ended up joining odinbrotherhood don't know what I was thinking. That turned out to be a really fun trip for me.
please guys is there anyone out there that can help me understand if you have to shake really I am made whatever I have to do just please let me know I am in deep urgent help I really want the phone back it's the only phone that actually mirrored my high definition TV screen all my other phones are old and I cannot watch YouTube on my phone anymore.
I was going to show a photo of what the front of the phone look like but I can't get the website to work on my laptop I am able to login on my telephone but not my laptop I don't know what the deal is with all these electronics these day I can't seem to get anything to work anyways thanks in advance Atlantis.
Sorry I have 4 kids and I havent had the time to read any stikys at all! very sorry for that..
I will make this easy, if anyone here can answer just one question.
HOW DO YOU BACKUP A FACTORY IMAGE FROM ONE PHONE AND APPLY IT TO ANOTHER?
Is there anyone here that could please point me to how to do that? sorry guys I have a ten month old baby in my lap crawling aroud and I can hardly type at all.