Related
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
I have a verizon wireless htc rezound. I was trying to use my at&t sim card in it attempting to unlock it( first time dealing with android). and figured out i got service but was not able to send sms. after searching i realized it wasnt just me. I have heard of the custom rom venasaur that fixed the sms problem. I am completely new to this and would really appreciate help installing this rom or fixing this problem? I dont know if i need to root it if i need an sd card i am pretty clueless at this point ?
How is this urgent?
Only put urgent in the title if you think you have bricked or something like that.
Start here and read the entire thread, take notes:
http://forum.xda-developers.com/showthread.php?t=
If Venasaur ROM will fix your issue, then yes, you need root to flash it. You should really read about all of this for at least a week before doing anything to your phone or else you can easily cause irreparable harm or at least end up needing a lot of help to get it running again.
Take a bunch of notes about what commands do what, what order you do things in, etc... while you read so you can look that stuff up easily in one place. There's a lot to digest and absorb and you should have a decent understanding of things before you get started.
After scouring for two days I am just giving up and asking for help. Here is what happened. I have a At&t Galaxy Note. It was rooted but very glitchy. Kept shutting off, weird lines going through the screen, my camera didnt work. I know for that process I did TWRP and cyanogenmod. I went back to att stock from a forum found here. After I did that I had no google apps anywhere. SO my brother found some gapps.zip thing. He put it on my phone after I had restored back to a previous version that did have them. Now my phone wont stay on for longer than a minute. I cant get it to recognize on my computer. So I cant even try to get into it to see if I can fix anything. Everytime I conntect it, a message pops up that says that it cannot install MTP... Even if I restore again, as I have tried. It is still not letting me use it. Then my brother decided to re root it I guess. And that is all well and fine but i still cant use my phone. I saw something about a .zip that removes gapps but I havent been able to use that as my phone just wont install it in recovery mode. Can someone please please help me!!!!
luvpudds said:
After scouring for two days I am just giving up and asking for help. Here is what happened. I have a At&t Galaxy Note. It was rooted but very glitchy. Kept shutting off, weird lines going through the screen, my camera didnt work. I know for that process I did TWRP and cyanogenmod. I went back to att stock from a forum found here. After I did that I had no google apps anywhere. SO my brother found some gapps.zip thing. He put it on my phone after I had restored back to a previous version that did have them. Now my phone wont stay on for longer than a minute. I cant get it to recognize on my computer. So I cant even try to get into it to see if I can fix anything. Everytime I conntect it, a message pops up that says that it cannot install MTP... Even if I restore again, as I have tried. It is still not letting me use it. Then my brother decided to re root it I guess. And that is all well and fine but i still cant use my phone. I saw something about a .zip that removes gapps but I havent been able to use that as my phone just wont install it in recovery mode. Can someone please please help me!!!!
Click to expand...
Click to collapse
wow. the first few sentences were making sense, then you just lost it grammar wise and lost me. it would have helped knowing what ROM was on your phone. from symptoms it sounds as if t was a 4.2 ROM with no GAPPS and some serious OC/UV issues.
but you lost me with your English and the "TWRP and CYANOGENMOD thingy" i know what they are obviously, but what you did with them is a HUGE guessing game. one person not knowing what they are doing is bad enough, but two of you.......... cant do that man. kind of like masturbating with someone elses hand man. who cleans up the mess.
absolute clean slate is going to be you best option in my opinion. the "Super Everything Thread" is going to be your new best friend.
read it, live it, learn it......................understand it. put yourself in position to help yourself first.
tutorals on YOUTUBE can help too.
can you get DOWNLOAD MODE?
do you have ODIN?
do you have PDA/ TAR files you need?
you may need to re-install the DRIVERS for phone on computer
there is a glossary in Super thread, that is why i capped these words. key points and things you need to do. its a marathon not a sprint.
go slow, one step at time, understand what you are doing. even rehearse it, i did. be confident in what you are doing. make sure you have files for I717.
read the OP's for ROM's
some need GAPPS (4.2) and some don't (4.1.2) or Touchwiz
the new 4.3 will also need GAPPS and there are 4.2 and 4.3 GAPPS. again make sure you have right files. all the more reason to take your time.
and uh, don't just let someone flash whatever on your phone, that's how you get a BRICK.
good luck and let us know.
if i have stated anything wrong, someone else will be buy to correct.
nothing wrong with how i am telling, others just may have shortcuts.
what you do with it is up to you, i just like to understand what i am doing, cause i will have to fix it.
but keep us posted
captemo said:
wow. the first few sentences were making sense, then you just lost it grammar wise and lost me. it would have helped knowing what ROM was on your phone. from symptoms it sounds as if t was a 4.2 ROM with no GAPPS and some serious OC/UV issues.
but you lost me with your English and the "TWRP and CYANOGENMOD thingy" i know what they are obviously, but what you did with them is a HUGE guessing game. one person not knowing what they are doing is bad enough, but two of you.......... cant do that man. kind of like masturbating with someone elses hand man. who cleans up the mess.
absolute clean slate is going to be you best option in my opinion. the "Super Everything Thread" is going to be your new best friend.
read it, live it, learn it......................understand it. put yourself in position to help yourself first.
tutorals on YOUTUBE can help too.
can you get DOWNLOAD MODE?
do you have ODIN?
do you have PDA/ TAR files you need?
you may need to re-install the DRIVERS for phone on computer
there is a glossary in Super thread, that is why i capped these words. key points and things you need to do. its a marathon not a sprint.
go slow, one step at time, understand what you are doing. even rehearse it, i did. be confident in what you are doing. make sure you have files for I717.
read the OP's for ROM's
some need GAPPS (4.2) and some don't (4.1.2) or Touchwiz
the new 4.3 will also need GAPPS and there are 4.2 and 4.3 GAPPS. again make sure you have right files. all the more reason to take your time.
and uh, don't just let someone flash whatever on your phone, that's how you get a BRICK.
good luck and let us know.
if i have stated anything wrong, someone else will be buy to correct.
nothing wrong with how i am telling, others just may have shortcuts.
what you do with it is up to you, i just like to understand what i am doing, cause i will have to fix it.
but keep us posted
Click to expand...
Click to collapse
Im sorry, Im just really frustrated. My phone was working fine yesterday and now its a very expensive paperweight. And not only that but Im having problems with my laptop. Apparently the hard drive just went clonkers for no reason and now I have to put in a new one. Yes I can get into download mode. Yes I have Odin. Yes I have the PDA/TAR files. I made sure everything was for the sgh i717. I read each process ten times before I did it. I installed my drivers from the Samsung website. I think my problem is that the internal sd card isnt being recognized. When I go into recovery mode, which is CMW btw, it gives me an eemc 07 error message and says it cant mount. When I can get my phone to stay on long enough for thecpu to recognize it it doesnt say sd card just phone memory. I will be sure to read the super everything thread. As for a ROM there isnt one on here. If I try to put one one it wont install and keeps saying that eemc 07 error message. Thanks for responding. Im spiraling in self-pity right now but im determined to get my phone back.
If you get it back to stock, do a complete erase/format, and your still having all these glitches, there's a good chance there's hardware issues. Especially if your not able to see the external SD card etc.
If your the original owner (I.E. you got it from a dealer with a plan), and you can get your counter reset to 0 on stock with these issues still showing up, it might be easiest to take it in and get a replacement. That is, if you have a warranty option available.
Ragnarkov said:
If you get it back to stock, do a complete erase/format, and your still having all these glitches, there's a good chance there's hardware issues. Especially if your not able to see the external SD card etc.
If your the original owner (I.E. you got it from a dealer with a plan), and you can get your counter reset to 0 on stock with these issues still showing up, it might be easiest to take it in and get a replacement. That is, if you have a warranty option available.
Click to expand...
Click to collapse
Its not the external sd but the internal one. Its just gone... I know that this is the problem at this point. But I have no idea how to resolve that issue. I have no idea where it is or how to get it back. I have been on xda and droidforums for an extreme amount of time trying to find a solution but nothing going. The only way I have seen to reset my counter is to use triangle away. As I cannot even use my phone due to freezing and restarting I cannot even install that app. I am hoping that one person in the wide world has had this problem and fixed it and will read this and tell me how to fix it.
Status 7 means you need to update you recovery
Sent from my SGH-I717 using xda app-developers app
Thanks for all the help. Took it it AT&T. Now my phone is working properly if a slight bit laggy. But at least its working.
luvpudds said:
Thanks for all the help. Took it it AT&T. Now my phone is working properly if a slight bit laggy. But at least its working.
Click to expand...
Click to collapse
so where are you at then?
what does your phone show as running?
settings/about phone
are you just going to leave it or are you still going to pursue customizing?
captemo said:
so where are you at then?
what does your phone show as running?
settings/about phone
are you just going to leave it or are you still going to pursue customizing?
Click to expand...
Click to collapse
I'm running 4.1.2 now. I will not be customizing like that for some time. I might think about it later but I'm so glad to have it back I'm just going to enjoy it for awhile.
luvpudds said:
I'm running 4.1.2 now. I will not be customizing like that for some time. I might think about it later but I'm so glad to have it back I'm just going to enjoy it for awhile.
Click to expand...
Click to collapse
you know, something going wrong with mine was my biggest worry. when I decide to screw something up, I can really screw something up. so I was very hesitant. it probably took me 2-3 months to get the courage to flash. but that was most likely a good thing. it made me be very thorough in the process.
all I am saying is don't let it completely discourage you. you have time.
glad you got phone back, I know it can be a bit of a scary thing. I have come across an issue or two myself and actually surprised myself by fixing myself. actually a pretty good feeling.
anyway, stick around, there are some pretty amazing folks here.
captemo said:
one person not knowing what they are doing is bad enough, but two of you.......... cant do that man. kind of like masturbating with someone elses hand man. who cleans up the mess.
Click to expand...
Click to collapse
:laugh::laugh::laugh:
Rofl. Now I have a completely different vision when I see captemo advise a full wipe to someone.
Sent from my SGH-I717 using Tapatalk 4
Bubbajoe40356 said:
Rofl. Now I have a completely different vision when I see captemo advise a full wipe to someone.
Sent from my SGH-I717 using Tapatalk 4
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=h5HJGuyBfx8
Well I think we just lost our "FamilyFriendly" label.
rangercaptain said:
Well I think we just lost our "FamilyFriendly" label.
Click to expand...
Click to collapse
Well at least our PG-13 rating anyway. Tell me it wasn't pretty funny though
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
rangercaptain said:
Well I think we just lost our "FamilyFriendly" label.
Click to expand...
Click to collapse
I don't know ... They looked like they were pretty friendly.....for family
Sent from my SGH-I717 using Tapatalk 4
Hello everyone!
It is obvious I did something REALLY wrong when experimenting with my Atrix 4g, and I would like to know if anyone here is willing to offer some guidance.
I must confess I am not VERY knowledgeable regarding Android phones (I have done it in the past with HTC’s running windows, so it’s been quite a while since then, but definitely similar to androids), BUT I learn VERY quickly and I know how to follow instructions (98% of the time)
So I think I might’ve soft brick it, and perhaps deleted files I should not. Anyway, also I would like to point that if I am NOT in the right thread, inform me where is the right place… in order to keep on going with my posts.
Once senior members/moderators consider this is the right spot for me, I will describe with further details what I have done.
I just can tell you, everything started without upgrades nor flashing the handset or anything alike… suddenly wifi and bluethooth stopped working. And since I could not pair it with my computer even after trying to use the USB cable, (I don’t allow my google account to handle my contacts) I decided to indulge myself and buy a new phone… and I bought a Moto RAZR but I like my Atrix and I want it working again
If you think you can help, or you are willing to help, feel free to ask what I have done, the steps I have followed and the threads I have revised. I have a little log of the things I have worked with and I know I have missed, surely, few important steps.
Thank you in advance for reading
Wow... This is got to be the longest list of disclaimers and precursors to an actual post EVER, lol.
You're asking a question. This is the Q&A section. You're good. Proceed at will.
For future reference, this kind of lenghty introduction and waiting for approval is hardly necessary. Just asj the question, the mods will move it if necessary, and you will only get lashed out at if the question is really trivial (so the solution can easily be googled) or has been answered enough times already (so the solution can easily be found by using the XDA forum search). Your question does kinda sorta fall into the second category, but since you're new here (and such a scardycat), let's let this one pass.
Based on your (very minimal) info, it kinda seems you have that dreaded problem where the wifi/bluetooth chip just dies all of a sudden... Unfortunately if that's the case, there is no known solution as that is most likely a hardware failure.
Yoy might want to go check some other threads (I'm on the phone so can't look for them now), some people have had limited success in dealing with this by applying pressure at certain points in the phone, usually by sliding a piece of thin plastic strip such as an old credit card.
You might however also want to describe your problem further, because it might not actually be this...
description of issues
ravilov said:
Wow... This is got to be the longest list of disclaimers and precursors to an actual post EVER, lol.
You're asking a question. This is the Q&A section. You're good. Proceed at will.
For future reference, this kind of lenghty introduction and waiting for approval is hardly necessary. Just asj the question, the mods will move it if necessary, and you will only get lashed out at if the question is really trivial (so the solution can easily be googled) or has been answered enough times already (so the solution can easily be found by using the XDA forum search). Your question does kinda sorta fall into the second category, but since you're new here (and such a scardycat), let's let this one pass.
Based on your (very minimal) info, it kinda seems you have that dreaded problem where the wifi/bluetooth chip just dies all of a sudden... Unfortunately if that's the case, there is no known solution as that is most likely a hardware failure.
Yoy might want to go check some other threads (I'm on the phone so can't look for them now), some people have had limited success in dealing with this by applying pressure at certain points in the phone, usually by sliding a piece of thin plastic strip such as an old credit card.
You might however also want to describe your problem further, because it might not actually be this...
Click to expand...
Click to collapse
Im sorry, if my disclaimer was a little too lengthy, but I detest to intrude in areas where I am not supposed to be and, even worst I dislike to be told "you are not in the right area" makes me feel moron... but thanks for the support... following you will find a detailed description of what I have done and my results
Motorola Atrix 4G MB860 from AT&T unlocked for other markets
handset suddenly stop working wifi/bluetooth
actions taken and results:
1: hard reset
wiped out all information contained in the handset but it DID NOT made the wifi/BT antenna work
2: apparatus left for aprox 8 hours without battery, then wifi/BT antenna seemed to be operative, at least for 8 hours, tuned it off and on...displayed error message.
3: after consulting several threads posted in this very same website and in this area... no information helpful was found, other than flashing a newer ROM.
4: second hard reset using, tried the HR found in settings... unsuccessfully, handset rebooted with everything in it as if I didn't hard reset it
5: third hard reset: using power button and volume button (for one strange reason I have to press not only the volume down button, but both, in order to start the RSD protocol) but it does not move beyond that point, so after some research.. I found out it has been softbricked, handset operative, but the aforementioned issues still going on.
6: after some research, here
http://forum.xda-developers.com/showthread.php?t=2277112
http://forum.xda-developers.com/showthread.php?t=2141817
http://forum.xda-developers.com/showthread.php?p=42407269
http://www.xda-developers.com/tag/fastboot/
http://forum.xda-developers.com/showthread.php?t=2262869
I found I could flash a newer ROM, specific for my equipment, downloaded it and followed the instructions provided in the threads
http://forum.xda-developers.com/showthread.php?t=1975893
followed the instructions, et cetera, deleted cache and ran the command fastboot erase system -w and, tried to flash the .zip file, handset recognised it, however displayed an error saying "no android info.txt" there were 3 messages total, all of them displaying the same file extension .TXT
I guess thats where I messed up big time... so whensoever you have a chance to reply let me know what could have been wrong..and pelase, let other geniuses out there in the forum whats going on and if they are willing to help me in this.
I will try to keep a concise log of the do's and dont's and what to do in case someone else share the same problem
thank you in advance to the XDA delopers team
So if I got it right, your phone is SIM unlocked but not bootloader-unlocked? Does it have "Unlocked" in the top left of the screen when booting?
If it does, I'd recommend installing MROM (not MROM-ICS as you suggested because that is a testing ROM). If the bt/wifi error happens there as well, then it is most likely a hardware failure and no software will help. In that case, I'd suggest trying a hardware method as described here.
If it doesn't, then I guess I'd try flashing a full SBF. Be warned however that flashing SBFs is potentially very dangerous, so be sure to read all the guides and select a SBF that is appropriate for your device (based on the OS version it had installed previously).
ravilov said:
So if I got it right, your phone is SIM unlocked but not bootloader-unlocked? Does it have "Unlocked" in the top left of the screen when booting?
If it does, I'd recommend installing MROM (not MROM-ICS as you suggested because that is a testing ROM). If the bt/wifi error happens there as well, then it is most likely a hardware failure and no software will help. In that case, I'd suggest trying a hardware method as described here.
If it doesn't, then I guess I'd try flashing a full SBF. Be warned however that flashing SBFs is potentially very dangerous, so be sure to read all the guides and select a SBF that is appropriate for your device (based on the OS version it had installed previously).
Click to expand...
Click to collapse
heheheh thats the one I downloaded and tried to flash.. unless i have picked the wrong file.. please let me know which is the one I have to download and I will try to install it... there are few options.. I just want to make sure I pick the right one
thank you!
There aren't actually many options. Just download the latest ROM package (not the update) and the gapps package. Flash ROM then gapps. That is all.
Thanx
I havent had a chance to follow up my work with the phone...
but anyway I have to thank you for all the attention and help
I will resume my work on it this coming days
and I will keep you posted on whats going on
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.