Related
So I plugged my Vibrant into Odin to revert to stock. Apparently everything went wrong, and now my phone is stuck at the Phone---!---computer screen. It seems that my phone won't respond to hardware methods of entering download mode, so am I screwed?
Keep reading on here. This has happened to many people. Keep trying things and hopefully you will get it.
1. Remove SD and SIM card
2. Remove battery
3. plugged the phone into USB (connected to PC)
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
I've tried that, and many other methods, multiple times already. It seems that none of the volume/power methods do anything for my phone. I'm certain that if hardware-locks do exist for certain vibrants, mine just so happens to be one of them (Date on box is August 13). I just want to know if anyone with a similarly dated phone has ever been able to access download mode without adb.
If anyone knows of more methods, please post them. If all else fails, I'll go complain in my local T-Mobile store that my phone died. I have no idea if that'll get me anywhere, but it's worth a shot.
Does anyone who has had a problem similar to mine know of any fix? By that I mean, has someone who has had a presumably hardware-locked phone ever been able to boot it into download mode without adb? I'd really like to know if I can salvage this thing, or if I have to try my luck with T-Mobile.
Try holding volume down and holding power button and plug in USB while this is happening.
Sadly, I've tried that method as well, thank you though for responding. I will continue trying since it seems not to be a 100% thing for some people. Anyway, for the Volume keys + Power method, can anyone provide a more precise time of releasing power than "When it goes black". I'm hoping my inability to enter download mode is human-error, so I'd like as much input on this as possible. Thanks in advance.
Generic112 said:
Sadly, I've tried that method as well, thank you though for responding. I will continue trying since it seems not to be a 100% thing for some people. Anyway, for the Volume keys + Power method, can anyone provide a more precise time of releasing power than "When it goes black". I'm hoping my inability to enter download mode is human-error, so I'd like as much input on this as possible. Thanks in advance.
Click to expand...
Click to collapse
When you see the " !---> (pc)" symbol, plug your USB in. Hold down volume +, volume -, and power. As soon as the screen turns black release the power button only. Continue holding Vol + and Vol -. You'll enter Download mode.
I've tried that multiple times, but I will continue to try it. It seems as though my phone won't register that buttons are being pressed. All that happens is the phone reboots to the Phone--!--Computer screen every time the power is held and released (As it should). No combination of buttons seems to have any affect on this. Oh well, I'll continue trying and hopefully someone will post a working method.
I have the same problem and the hardware button method isn't working and I am stuck at the Phone ! Computer screen, and I read around the forums and they say that some Vibrant's have the hardware method locked, so you can't boot into Download mode from using the buttons. Since adb cannot find the phone when its stuck at this screen it seems we are both screwed. I have found no other solution other than returning it Tmo, not sure if they will exchange since it might be a violation of warranty.
I'm just going to play dumb when I go to T-Mobile. I'll say it just booted into that screen, and I can't get out of it. The hardware lock appears to be a defect, since it's not present on most Vibrants, so that should be able to warrant the replacement phone. I've been with T-Mobile awhile, and they're usually pretty good with replacements. Besides, the phone would be easily fixed if it wasn't broken in the first place.
But before I go to T-Mobile, I'm going to try and talk to Customer Service. If it's a common problem, then I'm sure it can be covered under warranty (Even though MOST ways of getting it require voiding warranty). Again, on the basis that this wouldn't be a big deal if my phone worked like a normal Vibrant. Besides, I'm sure T-Mobile can flash it without requiring the hardware method, so even if they only charge me some sort of service fee, I won't really mind.
As final moral reassurance for myself, I only tried to flash it because apps started FC on me and the phone constantly acted weird. The only thing I've done is root it, so it's not like I really set it up to fail.
Let me know how it goes with Customer Service. I would to get this problem resolved as well with the least amount of trouble. I don't want to have a brick and have to pay like $500 for a new phone. And I think the hardware buttons thing might actually be a defect. I tried doing the hardware buttons thing to get to recovery mode once before and it worked. I did this to install an update.zip to root the phone. It only worked that one time and now the buttons don't boot into recovery mode or download mode. It if works once then not again, there has to be something wrong.
I'll be trying them tomorrow (It's 10PM where I am). If all goes well, I'll try and contact you. I'm pretty sure I'll be safe so long as I don't mention rooting it. The firmware flash they'll have to do should help me on that front, so unless they catch on, I should be safe. Anyway, hopefully tomorrow I'll be good news, otherwise expect some post from me on Monday or Tuesday, depending on whether I have the time to deal with them or not.
Hey Generic112, I got with T-Mobile customer service. I told them about the screen I was seeing but did not mention rooting or attempting to flash the phone. They said they will replace my phone by shipping me a new Vibrant, but I have to return the one I have. I am not sure if they will do a check to verify if the Vibrant was rooted or not after they receive it, but I will have my new Vibrant before they receive the one I have. I won't know what will happen for awhile because its going to take a week for the new phone to arrive and when it does then I will be returning the one with the phone ! computer problem, unless someone thinks it is a better idea to tell them what happened and have them repair it?
I am also struck with the same problem
Hi,
I am also struck with the same problem. Please let me know if you guys got any method to resolve the problem or T-Mobile was able to help.
the3dman said:
Keep reading on here. This has happened to many people. Keep trying things and hopefully you will get it.
1. Remove SD and SIM card
2. Remove battery
3. plugged the phone into USB (connected to PC)
4. held down vol-up and vol-down
5. popped the battery back in while holding vol buttons
Click to expand...
Click to collapse
This method actually worked for me. I was beginning to think I'd have to build the USB jig, but tried this as a last ditch. Thanks!
The above method has worked for me numerous times with the same problem, my old bricked one, and my new one. Try holding down power button as well once or twice, never know. You have to keep the volume buttons pressed the whole time for it to work.
Sent from my SGH-T959 using XDA App
ViralCipher said:
Hey Generic112, I got with T-Mobile customer service. I told them about the screen I was seeing but did not mention rooting or attempting to flash the phone. They said they will replace my phone by shipping me a new Vibrant, but I have to return the one I have. I am not sure if they will do a check to verify if the Vibrant was rooted or not after they receive it, but I will have my new Vibrant before they receive the one I have. I won't know what will happen for awhile because its going to take a week for the new phone to arrive and when it does then I will be returning the one with the phone ! computer problem, unless someone thinks it is a better idea to tell them what happened and have them repair it?
Click to expand...
Click to collapse
In some cases that I've read they say, TMo charged them 600$ for the Replacement after finding out that it was bricked due to hacking. Before replacing try to get it repaired by them.
I would also like people whose phones were replaced to confirm what I've said above.
ech419 said:
In some cases that I've read they say, TMo charged them 600$ for the Replacement after finding out that it was bricked due to hacking. Before replacing try to get it repaired by them.
I would also like people whose phones were replaced to confirm what I've said above.
Click to expand...
Click to collapse
He should be able to get the phone woking again, what happened is not a big deal. If he sends it in the way it's sitting right now, t'Mo's techs won't have a problem getting it working again. (IMO) Especially if they find out the phone's rooted, I wouldn't be surprised if he gets charged.
I bricked my phone so bad, it was beyond recovery. I erased the bootloader, therefore it was completelly dead. No life. I got a replacement under warranty for free, never got charged for it.
My advice would be to try and get to work again before sending it in.
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 started high jacking threads to get some help and I don't want to be that person.
So let me start from the beginning, I decided to install the ICS update after my husband's and my mom's phone automatically updated on my completely stock Razr MAXX. I installed let it go and it restarted and got stuck on the DROID splash screen. Tried restarting, same thing. Tried reinstalling the update from the cache, same thing, stuck on the DROID screen. Asked Motorola, they told me to do a hard reset, no results. I've tried to go back to GB using the 1.6 utility which got it stuck to the dual core splash screen. Somebody told me to use the 1.81 utility, used option 1, back to the DROID splash screen.
Currently I'm wondering if I'm just being impatient, so I've let it sit after the last load for about 2 hours now, I've let it sit at the spot for up to 4 hours previously hoping it would start up.
I have some tech skills as long as I understand what I'm doing, right now there are a lot of jargon that I have no idea what it means being thrown around. If anyone has help for me I would greatly appreciate it. I don't want to go through the refurbished phone nightmare (last time I went through 3 phones before I got one that worked). I would be eternally grateful to anyone who has some help for me especially if I could understand it :silly:
Thanks in advance to anyone who can help!
Of you are stock then send it back for a warranty repair.
Sent from my DROID RAZR using Tapatalk 2
snobunny said:
I started high jacking threads to get some help and I don't want to be that person.
So let me start from the beginning, I decided to install the ICS update after my husband's and my mom's phone automatically updated on my completely stock Razr MAXX. I installed let it go and it restarted and got stuck on the DROID splash screen. Tried restarting, same thing. Tried reinstalling the update from the cache, same thing, stuck on the DROID screen. Asked Motorola, they told me to do a hard reset, no results. I've tried to go back to GB using the 1.6 utility which got it stuck to the dual core splash screen. Somebody told me to use the 1.81 utility, used option 1, back to the DROID splash screen.
Currently I'm wondering if I'm just being impatient, so I've let it sit after the last load for about 2 hours now, I've let it sit at the spot for up to 4 hours previously hoping it would start up.
I have some tech skills as long as I understand what I'm doing, right now there are a lot of jargon that I have no idea what it means being thrown around. If anyone has help for me I would greatly appreciate it. I don't want to go through the refurbished phone nightmare (last time I went through 3 phones before I got one that worked). I would be eternally grateful to anyone who has some help for me especially if I could understand it :silly:
Thanks in advance to anyone who can help!
Click to expand...
Click to collapse
You can try option 1 follow these instructions
Getting back to .211:
This is a fairly simple process, but not as simple as getting back to .211 from .214.
If you are new to this, please fully read all the directions before starting this process. Remember, check how much battery you have.
1) Download Matt's Droid Razr Utility 1.81 from the link above.
2) Extract the files from the .zip (Creates DroidRazrUtility1.81 folder)
3) Go into the DroidRazrUtility folder and start the DroidRazrUtility batch file
4) At the Batman logo, press any key to continue.
5) At the next menu, select option "1" (Fastboot Restore 6.16.211 (ICS 4.0.4 Official OTA Software)) by typing 1 and pressing enter.
** DO NOT PRESS ANYTHING AT THE NEXT SCREEN UNTIL STEP 10**
6) Attach your phone to your PC with a USB cable.
7) Power down your phone
8) While phone is off, hold down both volume keys (up+down) and the power key.
9) Use the Volume Down key to select "AP Fastboot" and then use the Volume Up key to select it.
10) On the DroidRazrUtility, press any key to continue.
11) Keep an eye on your phone, it will turn off and on again.
12) Follow the on screen instructions and press any key why your phone's display turns on.
13) Repeat Steps 11-12 one more time
** .211 install should take around 5-10 minutes **
14) When the screen asks if you want to wipe data, hit any key to continue OR exit the program to KEEP DATA.
15) Tap the power key to bring you out of AP Fastboot, then it should power down.
16) Turn on your phone to see a screen of an Android with his chest open. Wait.
dave5777 said:
Here's a Dropbox link to the 1.81 Utility You can try option 1 follow these instructions
Getting back to .211:
This is a fairly simple process, but not as simple as getting back to .211 from .214.
If you are new to this, please fully read all the directions before starting this process. Remember, check how much battery you have.
1) Download Matt's Droid Razr Utility 1.81 from the link above.
2) Extract the files from the .zip (Creates DroidRazrUtility1.81 folder)
3) Go into the DroidRazrUtility folder and start the DroidRazrUtility batch file
4) At the Batman logo, press any key to continue.
5) At the next menu, select option "1" (Fastboot Restore 6.16.211 (ICS 4.0.4 Official OTA Software)) by typing 1 and pressing enter.
** DO NOT PRESS ANYTHING AT THE NEXT SCREEN UNTIL STEP 10**
6) Attach your phone to your PC with a USB cable.
7) Power down your phone
8) While phone is off, hold down both volume keys (up+down) and the power key.
9) Use the Volume Down key to select "AP Fastboot" and then use the Volume Up key to select it.
10) On the DroidRazrUtility, press any key to continue.
11) Keep an eye on your phone, it will turn off and on again.
12) Follow the on screen instructions and press any key why your phone's display turns on.
13) Repeat Steps 11-12 one more time
** .211 install should take around 5-10 minutes **
14) When the screen asks if you want to wipe data, hit any key to continue OR exit the program to KEEP DATA.
15) Tap the power key to bring you out of AP Fastboot, then it should power down.
16) Turn on your phone to see a screen of an Android with his chest open. Wait.
Click to expand...
Click to collapse
Thanks, very clear directions, but I've already tried that....twice and I'm stuck at the DROID splash screen. I let it sit there all night hoping and praying it was slow and eventually boot up, but that is wishful thinking.
I'm going to find out if I can send it in for warranty repair now. In the past they've only been willing to replace and not repair...and always with a crappy refurb.
Wish me luck!
snobunny said:
Thanks, very clear directions, but I've already tried that....twice and I'm stuck at the DROID splash screen. I let it sit there all night hoping and praying it was slow and eventually boot up, but that is wishful thinking.
I'm going to find out if I can send it in for warranty repair now. In the past they've only been willing to replace and not repair...and always with a crappy refurb.
Wish me luck!
Click to expand...
Click to collapse
Well thanks a whole bunch Motorola for your lovely use of the ridiculous "water damage indicator" While my phone has never seen water, my guess is "excessive humidity" which I'm sure it encountered while I was on my honey moon in Mexico tripped the indicator. So even though my phone worked perfectly fine until it decided to update and I can't see how the failure to boot could even be conceivably be related to their supposed water damage, they sent the phone back to me without even attempting to fix it (two weeks to send it back unrepaired and warranty voided) stating that the problem was in fact the water damage........AAGGGGGGGGG F#$%^%$%#$#$$^^^&&%&$%$^#$%#@!!&*(&*(%^$
They didn't even bother to call me and say "hey, you have water damage, so your warranty is voided. But it says here that it quit working after you updated your OS, so maybe we can fix it anyway because that probably has nothing to do with the so called water damage" But that would actually require them to know why I sent my phone in the first place. Something you would think that they might have on file, but NOOOOO. So now I can try to warranty through Verizon, which if I try I will most likely get a too bad now give us $600 for your phone that wasn't under warranty. Or I beg Motorola to wipe it and reinstall the OS, but I'm sure they will tell me that is something that isn't possible. Or I "lose" my phone and pay the deductible on insurance. F)*&%$#@$^&*))*&$$#^*(*.
Thanks Motorola for being *&^$heads. :crying:
snobunny said:
Well thanks a whole bunch Motorola for your lovely use of the ridiculous "water damage indicator" While my phone has never seen water, my guess is "excessive humidity" which I'm sure it encountered while I was on my honey moon in Mexico tripped the indicator. So even though my phone worked perfectly fine until it decided to update and I can't see how the failure to boot could even be conceivably be related to their supposed water damage, they sent the phone back to me without even attempting to fix it (two weeks to send it back unrepaired and warranty voided) stating that the problem was in fact the water damage........AAGGGGGGGGG F#$%^%$%#$#$$^^^&&%&$%$^#$%#@!!&*(&*(%^$
They didn't even bother to call me and say "hey, you have water damage, so your warranty is voided. But it says here that it quit working after you updated your OS, so maybe we can fix it anyway because that probably has nothing to do with the so called water damage" But that would actually require them to know why I sent my phone in the first place. Something you would think that they might have on file, but NOOOOO. So now I can try to warranty through Verizon, which if I try I will most likely get a too bad now give us $600 for your phone that wasn't under warranty. Or I beg Motorola to wipe it and reinstall the OS, but I'm sure they will tell me that is something that isn't possible. Or I "lose" my phone and pay the deductible on insurance. F)*&%$#@$^&*))*&$$#^*(*.
Thanks Motorola for being *&^$heads. :crying:
Click to expand...
Click to collapse
I know it sucks, but to be honest, talk to any phone manufacturer and they would do the same thing (well, maybe they would email/call you to let you know, but you get what I'm saying).
Is there any reason why you can't simply Root and install a custom ROM or even try doing some sort of Fastboot stock restore? It sounds to me like you aren't completely bricked and that it's likely not the hardware if you are certain there is no water damage.
EDIT: Here's what I am talking about using RSD Lite and Fasbooting back to stock: http://forum.xda-developers.com/showthread.php?p=23453478
WorldOfJohnboy said:
I know it sucks, but to be honest, talk to any phone manufacturer and they would do the same thing (well, maybe they would email/call you to let you know, but you get what I'm saying).
Is there any reason why you can't simply Root and install a custom ROM or even try doing some sort of Fastboot stock restore? It sounds to me like you aren't completely bricked and that it's likely not the hardware if you are certain there is no water damage.
EDIT: Here's what I am talking about using RSD Lite and Fasbooting back to stock: http://forum.xda-developers.com/showthread.php?p=23453478
Click to expand...
Click to collapse
Thanks, I haven't tried RSD yet. What I think that I'm running into, and I can't be sure because I have very little knowledge about the boot files, but I think that there is a something wrong in those files and I'm not sure that the files contained when flashing back to stock are what it needs for that deficiency.
Deductive reasoning says that water damage has absolutely nothing to do with why it is actually failing to boot since the phone was working just fine before the OTA update.
It really comes down to is all phone manufacturers are trying to decrease the bottom line and cover their own butts. Interestingly someone brought a lawsuit against apple for this very issue and apple has since relaxed it's warranty in regards to water damage, for example if a piece of hardware fails that has nothing to do with water damage they will fix it under warranty....I hate to think this way, but maybe I should switch teams
Well, what I have found out today is that Motorola's customer service and warranty center is worse than their ability to program an OTA update that will load correctly on my phone.....
I call them on Wed to find out if they will/can wipe the phone and reload everything. Guy tells me that he will have someone call me back in 24 hours. They don't call, so I called them....they are closed. Yay. Call them today..."we see you have a case started, let me transfer you to a rep..."......ring...ring...."welcome to the viva-la-mailbox system, please enter the mailbox number of the person you would like to talk to..." WHAT THE $%^&??????......0..."invalid response"....000000000000000000000....."invalid response".....::::....hang up try again. Same thing. Call with hubby's phone. Enter my phone number....."we see you have a case started, let me transfer you two a rep..."......ring...ring...."welcome to the viva-la-mailbox system, please enter the mailbox number of the person you would like to talk to..." :::::fuming:::::
Finally beat the system and get to talk to a real human being....at least I think so.... has no idea why I'm calling even though she has the notes right in front of her....ok....transfers me to the "Claim Escalation Dept." I ask if there is a number I can call someone directly so I don't have to go through massive automated phone system glitch irritation again. Nope, this is the only number. Can I get a mailbox? Nope. Name? Nope. $%^&.
They tell me I have damage to my phone. I ask what kind of damage, they say water damage. I tell them that my receipt says the "damage" was the water damage indicator. Nope, they are saying damage to the mother-board....
Side bar- Last time I had the motherboard go on a computer I couldn't get it to boot past the blue screen of death. How is it that the motherboard is damaged but the phone worked FLAWLESSLY until I did the OTA update.
Now they have pictures...pictures they sent to me via email on 8/22....***goes to check email and all spam folders**** Nothing. He says he will resend it to me. I've been stalking my email for the last two hours for the email that he swears he was going to send as soon as he finished the notes and I have yet to see it. I will be finding a torque bit small enough to open this pile of crap up tonight and looking for this magical damage.
Ask him if it is even possible for them to wipe the phone completely and reload the entire system fresh. He tells me that the techs can only do the same that I can from my phone, do a master reset. So the techs are glorified brick and mortar sales guys that get a screw driver too? Seems unfair to them.
I would LOVE for someone who really knows the ins and outs of the hardware and programming of these phones to explain it to me in excruciating detail. Is there a way that a damaged mother board could brick a phone only when an update is installed? Like a time bomb or something.....brick bomb.
So even if the supposedly damaged mother board has nothing to do with Motorola and the Google consortium bricking my phone, there is nothing they can do for my poor dead phone. Fine. F-off.
Call Verizon, they are sending me a new phone, made sure that insurance would cover it even if they decide the warranty is void. Sheniqa, my new sista, says that it doesn't sound like a hardware issue (see, even the lady who deals with people calling with busted phones everyday sees my point). Of course I played dumb, but I'm sure they will void my warranty.
Sooooooo.......I know I'm really just talking to myself at this point and ranting, but can anyone shed light on how damage to a motherboard would cause a phone to brick during an OTA update? I'm not even being facetious, I have half a mind to sue them over this phone and pain and suffering.... Does anyone want to explain the nuts and bolts of how Droid systems boot up? and last who wants to hold my hand through this RSD thing and see if I can make one last attempt to bring it back from the dead.
I really think that I will give up the ability to customize and all the cool features of DROID for *gag* an iPhone next time.....:crying:
Forget the iphone. Go for the SGS II or III as samsung made there phones to bring back from the dead.
I am sure you can get this phone up and running again if you are willing to spend lots of time researching all needed info on razr not that you havent but if it doesnt work then you havent tried every thing as i have tried the endless boot a few times with razr my self.
Sent from my XT910 using xda premium
Well I decided to go with the warranty replacement route and I'm waiting for the next denial...
I thought I should share my treatment by Motorola. As I said, thy told me the phone has water damage. I still have yet to get a pic and I discovered that the indicator strips are in their original condition, which is white with red x's. I would love to see their picture now. Additionally, I discovered another customer receivedthe same treatment, and after much hassle did get her phone replaced. I'm hoping that Verizon will prevent this from happening, but I may have a battle ahead.
Interestingly the customer with the similar issue was eventually sent a picture of the back of "her" phone with a completely red indicator, but no identifying marks on the battery or elsewhere. Motorola is intentionally defrauding its customers. In fact even with its implicit warranty, there is an implied warranty in their advertising. I will be trudging along again with the old crap phone for a few days until I can get another phone. Hopefully Motorola won't give me any hassle as I am going through Verizon, however if they hassle me it will get ugly. Just for giggles I would love to do some testing on these indicators as well.
I received a Nook Tablet 8GB from a friend that has it messed up pretty badly.
I have tried option 1 on the thread below and was able to boot into CWR and install the partition zip, then i used MiniTool Partition wizard to setup microsd as described, then place the update zip onto microsd.
http://forum.xda-developers.com/showthread.php?p=36492731
Once i put back into nook and boot up it goes to call customer service.
I also tried the following method here
http://forum.xda-developers.com/show....php?t=1663836
I get the green check mark and after reboot i get call customer service.
Again, im not sure what was done to this device before. Just trying to fix it for a friend. Is there anything else i can do?
Should i be using this method?
http://forum.xda-developers.com/show....php?t=1570022
So im assuming there is no hope since there is no response? I see many threads of bricked NT's so im assuming this sort of this is quite common and thats the reason for the lack of response to this thread.
I have worked with android for 2 years now and never bricked a device. I just find it hard to believe this nook tablet cannot be repaired. But again, i have no idea what was done to it.
"Bricked" is a very loose term: without knowing more what's wrong and/or what was done with a tablet it's hard to suggest how to really fix it. Applying a wrong fix often makes the problem worse rather than better.
But it's not necessarily a total loss: until you can figure how to fix it you might try to run CM10 off an SDcard: see http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/, or http://forum.xda-developers.com/showthread.php?t=2061536.
Not sure how i missed that thread but that worked great!
i was about to throw in the towel and you blessed me with that great info. Thank you so much!
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Try holding the "n" button when you power up. Press power and at that very first flicker after a few seconds, press and hold n.
bignadad said:
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Click to expand...
Click to collapse
Try what Asa suggested above, if it doesn't work then your friend's NT is like mine and many others' -- they only boot into SD with a cold boot and using a powered USB cable. Some people deem this "USB-tethered boot" behavior a manufacturing defect, but it might very well be by design by B&N to discourage people from venturing outside their content wall-garden with easy-to-use 3rd-party ROMs.
Hello I have ran into a issue(s) with a couple of phones, both really the same phone but different model numbers. BUT exact problem for each, I do repairs for several pawn shops, and one in particular has an absent minded employee that had repeatedly not followed proper procedure when purchasing used devices, most the time this is job security good me but there's this exception. Both of these Kyocera Hydro phones are locked with pins and the owners can't remember them, I've tried to Hard Reset but most I get is.SAFE MID, or Android is Optimizing xxx of xxx apps, before coming to home screen, one I've been able to disassemble and remove battery. Holding power for 2 mins trying to drain reserve if any replace battery, and.... Nothing changes. The hydro shore (c6745a) I can't even figure out how to disassemble to get to battery without damaging (what am I missing) I can't download apps, or get you recover mode. Is there any one that could enlighten me? How can I hard reset these phones, wiping all back to factory so they can be resold? I actually wanted to purchase for myself but this has beaten me at every turn. Thank you in advance for your time, and help. I sincerely am very appreciative XDA and it's community have yet to disappoint or let me down, I'm ready to see you shine in this matter!
I'm having the same problem... My daughter set a pin and then forgot it and it won't hard reset either because she can't remember her old email... Anyway have you had any luck in resetting yours? Would definitely appreciate the help to fix this
melowed said:
I'm having the same problem... My daughter set a pin and then forgot it and it won't hard reset either because she can't remember her old email... Anyway have you had any luck in resetting yours? Would definitely appreciate the help to fix this
Click to expand...
Click to collapse
Send it in under warranty, they will reflash it and it'll be just like new.
solution for hydro view coming soon
I have reset solution for c6742 (view)
I will publish the solution links soon.
Haora I can not share links here.
I need more post to share link
It works 100% search in youtube: Bypass Kyocera c6742 Android 5.1.1 (Video part 2)
HYDRO SHORE Recovery Menu
uid_C6742A:/> $ adb reboot recovery.img the .img makes all the difference Still looking for way to use/enter fastboot. no perm root, cause no custom recovery. no custom recovery, cause no fastboot. no fastboot cause no root..... wt-actual-fukk lol