Related
So i was odin-ing back to stock when for some reason Odin stopped. I start freaking out cause what else am i gonna do. My wife hates that i play with my phone.
Back in the early days of vibrant i effed up a voodoo lagfix (was able to fix it), but it cost me $50 buck when i had to send the replacment phone back after fixing mine.
So (like a noob) i unplug my phone and leave it in download mode. Nothings working.
I turn the phone off (again LIKE A NOOB), and it give me this angry picture of a cell connected to a PC...
Lost my Sh*t!!!!
However, was able to get into download mode, retore stock, and avoid a sexless month.
So, who has a good OMGZ-BRICKED-MY-PONE-OH-WAIT-NO-I-DIDNT moment...
I'd be willing to bet 99% of people on this forum have had this go down and freaked out the first time. It's one of those things that's inevitable when messing with this stuff.
i feel ya bro. I once spent 3.5 hours trying to odin before it went thru. I was sick to my stomach. Thought my phone was done!!
I once used a broken USB cable that I broke earlier (but forgot). It made very VERY poor contact with the phone so it disconnected if the phone was touched.
I used that cable with ODIN. Needless to say, it disconnected MANY times and I kept thinking I'm done. Finally I remembered the cable is broken and then I TOOK IT AND HELD IT AS TIGHT AS POSSIBLE with the USB contact.
Scarriest hour of my life.
I pulled the USB early, just before Odin says completed, on a bootloader flash. Holy **** what a scary moment. It booted up fine though.
Sent from my GT-I9000 using XDA Premium App
I know a sexless month is terrifying but its okay bro.
Sent from my Nexus S using XDA App
dunkerya said:
I know a sexless month is terrifying but its okay bro.
No its not. Try dating for only 2 yrs and having them often.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA Premium App
Lol, i tried flashing the gb bootloader, then my phone didnt boot up cuz odin failed and then it magicaly went to the computer phone screen, and i just flashed back the stock froyo bootloader.. o thought i was done for lol
Try being married for 20 yrs.....you get them often :-/
Project-V 6/11/11
Been there atleast 6 times, just kept trying and I get there
Sent from my SGH-T959 using XDA App
Jose Quervo and Android don't blend well LOL
Sent from my SGH-T959 using XDA App
Dan_Brutal said:
I pulled the USB early, just before Odin says completed, on a bootloader flash. Holy **** what a scary moment. It booted up fine though.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Haha I did this too outdated odin and bootloaders dont mix. I had to flash it at least 5 times to get it to take. Odin wouldnt recognize on the com after every bad flash unless I reboted. The last time I couldnt get back to download so I flashed it in the phone!pc screen with a different odin and it worked like a charm. Stomach was churning like it was trying to make butter lol.
Sent from my SGH-T959 using XDA App
First time I used ODIN my roomate accidentally unplugged my phone (cable was crazy loose)... wound up on the phone---!---PC screen and that was scary as crap. Took a little while, but I figured it out
Basically, unless you're in the realm of bootloaders, this phone is difficult enough to brick (which I'm very thankful for!)
grose65 said:
Been there atleast 6 times, just kept trying and I get there
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The burning question in my mind is, do you mean the failed upload attempts?
...or the month your kick-banned from hanky panky... because of course you keep trying, and eventually you get there. waka waka waka
Tried to flash my phone while driving, I hit a road bump and next thing, I know ODIN stopped working and my phone had a bunch of garbage display on the screen.
C*0000000*** something like that.
used Jig back to download mode. But the remaining 30 minutes drive back to my desk was horrifying.
Been there, done that
You tried to flash your phone while driving??
I used Clockwork mod to flash back to a Rom I liked better with a nandroid backup and it just got into a bootloop. I kept trying, but the only thing I could get to work was to Odin back to a stable Eclair build I had on hand.
BUT it gave me a red FAIL and just stopped mid-way through. However, when I unplugged and started my phone it came up just fine. PHEW!
Hours of fiddling and my wife was also all like "What the heck are you doing??? Can't you leave well enough alone???"
No. Of course not.
First time I got a soft brick I was scared as **** but then I learned about Odin I was so happy
Sent from my T959 using XDA Premium App
Dan_Brutal said:
I pulled the USB early, just before Odin says completed, on a bootloader flash. Holy **** what a scary moment. It booted up fine though.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
I never pull out early.... it's better if you let it finish.
Yea same problem lol
Sent from my SGH-T959 using XDA Premium App
lotherius said:
I never pull out early.... it's better if you let it finish.
Click to expand...
Click to collapse
But if you finish your have a higher chance of your phone producing more phones.
So... I cannot turn on my Asus tf101 unless I plug it in to a power source, once the screen lights up I can unplug it immediately and it functions normally when turned on. I bought this device refurbished from best buy a few months back, I dealt with the issue but now am looking to sell it. Any ideas on how to fix this? I have never rooted the device, however I have tried factory resets and cold boots.
mled203 said:
So... I cannot turn on my Asus tf101 unless I plug it in to a power source, once the screen lights up I can unplug it immediately and it functions normally when turned on. I bought this device refurbished from best buy a few months back, I dealt with the issue but now am looking to sell it. Any ideas on how to fix this? I have never rooted the device, however I have tried factory resets and cold boots.
Click to expand...
Click to collapse
Are you holding the pwr button long enough. If so,it sounds like the switch is bad.
I hold the power button for 12 seconds and try it with different variation holding volume keys. It functions fine when the device is powered on.
Sent from my Galaxy Nexus using xda app-developers app
It could be a bad battery or your charger is only giving enough to power the device on. I would try a new charger first.
Sent from my Transformer TF101 using xda premium
But once powered on, it functions flawlessly. The only issue is turning it on.
Sent from my Galaxy Nexus using xda app-developers app
I'v got the same problem. So +1. Any ideas?
I have the same problem, i am actually talking with the Asus Support Centre
I emailed them. All I can do.
Sent from my Galaxy Nexus using xda app-developers app
mled203 said:
I emailed them. All I can do.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Do you have the keyboard docking station for it?
Are you on custom ROM or OEM?
What "app killers" are you running?
Some custom ROM's have had similar issues a long while back. maybe yours is getting that issue IF your running custom.
Keyboard dock, if you have it, does it do the same thing for powering on, where it needs to be plugged in to start the screen?
I only ask about the app killers because I had experienced a similar issue about a year ago due to an app killer I had installed. Removed it, and the phone worked fine. Put it back on and it reverted back to having to be plugged in to start the screen.
Have you tried a clean wipe of everything on the tablet? And I do mean CLEAN, no dirty flashes here (keep your pants on bud).
Lastly have you given the charge port a good ole blow out lately? Long bursts aren't really going to do any damage, but I would stick to short quick bursts of compressed gas, again NO VACUUM CLEANERS. They create static and the charge port is quite susceptible to static discharge.
I know your pretty intelligent, but let me put it out there again. DON'T be a fool and use alcohol on your tool.
This post made me laugh. I do not have the keyboard docking station. I have never installed any task killers as I do not believe in them. The tablet has been running the stock ROM the whole time and has never been tampered with.
Sent from my Galaxy Nexus using xda app-developers app
And yes I have done a factory reset twice with no success.
Sent from my Galaxy Nexus using xda app-developers app
mled203 said:
And yes I have done a factory reset twice with no success.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
But you never said if you gave the ole girl a good ole cleaning in the slot.
I would venture to say that you need to send it in to Asus or take it back to Best Buy (if your able to). It sounds like there may be a voltage issue with the digitizer or the inverter.
And NEVER EVER EVER Invert your digits while cleaning out the slot.
You also didn't say if you went deep up in the ole girl and gave her a good rootin.
I'm working with Asus right now and of course there's something wrong with my serial number. Nerve been rooted. Blew it out and that did nothing.
Sent from my Galaxy Nexus using xda app-developers app
mled203 said:
I'm working with Asus right now and of course there's something wrong with my serial number. Nerve been rooted. Blew it out and that did nothing.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Please keep us posted as I am curious to know how ASUS customer service is to deal with.
Well, I am trying to send my TF to Asus to fix the problem and they are a bit annoying. I have just dealt with HTC before and that was wonderful, but here they have send me 4 emails asking me to wipe, to update and to do everything that I have already done, and after that they have sent me to another web to fill another questionary. With HTC I just had to told them the IMEI and in 4 days I had my phone back
I had similar issue with mine. It was one of the reason I took back to best buy and used the buy back.
I then picked up the Nexus 7.
Sent from my Nexus 7 using Tapatalk 2
I had a similar issue, do you use your device often ?
I figured out after a couple of months that each time it showed this behaviour the battery was in fact empty and it was in fact the root of the problem.
My transformer take much longer time to boot when plugged even with a full battery, and when it's empty it doesn't boot at all.
I must plug it, wait for it to be enough charged to boot unplugged, and do so. Then plug it back when started.
Considering that the transformer on stock cannot shut off when plugged to its keyboard (or even to USB ? Or is it just mine ? When I shut it off plugged to the keyboard then close it, it boot on again) When the tablet is left for several days unused the battery will be empty.
Sent from my Transformer using xda app-developers app
Yes I do. But even if the device is fully charged it will still not power on unless plugged in and I don't have the dock.
Sent from my Galaxy Nexus using xda app-developers app
Ok, sounds to be a totally different issue then, sorry
Sent from my Transformer using xda app-developers app
mled203 said:
Yes I do. But even if the device is fully charged it will still not power on unless plugged in and I don't have the dock.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Do the power and volume buttons work normally once fully booted? I have had similar issues, one was improperly seated power button, the other was a loose ribbon cable way down in the guts of this beast. Also, was this happening the whole time you've had it , or after a firmware update?
Right now I'm dealing with one that the screen won't stay on once I get into ics unless I'm plugged in. I went in and noticed that if the auto brightness wasn't set, it works. So I tweaked the settings in display time off when unplugged and uninstalled some screensaver app, and now it's working fine. It was probably the first thing, even though was already set to one minute. Anyway, just letting people know sometimes it isn't hardware. But the op probably is since he's done factory reset.
So I bricked my one to the point that it cannot mount, adb, side load and is stuck at the boot screen. Talked to Bell, and they said that they would give me a new one when they have more in stock by Friday. After using the one for a week, its getting really hard for me to use another device. Missing the feel, of it in the hands, the sexy build, amazing speaker sound, the gorgeous display, Zoe and blink feed. It feels weird using my nexus 4 now.
Sent from my Nexus 10 using Tapatalk HD
EnIXmA said:
So I bricked my one to the point that it cannot mount, adb, side load and is stuck at the boot screen. Talked to Bell, and they said that they would give me a new one when they have more in stock by Friday. After using the one for a week, its getting really hard for me to use another device. Missing the feel, of it in the hands, the sexy build, amazing speaker sound, the gorgeous display, Zoe and blink feed. It feels weird using my nexus 4 now.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
i sold my n4 to get the one and u r right..the n4 got nothing on this..the only thing i will miss is getting early updates
Not trying to be a ****, but you getting a new phone because you bricked yours is stealing. The warranty does not cover you flashing unsupported software, so by getting a replacement for a non-defective device, you're stealing from HTC.
Just so you know.
sassafras
Not stealing from HTC, but from Bell. And bell can suck a big one.
Well, they don't know the state of the phone yet, so they can say no on Friday. I haven't stolen it yet.
Sent from my Nexus 10 using XDA Premium HD app
EnIXmA said:
So I bricked my one to the point that it cannot mount, adb, side load and is stuck at the boot screen. Talked to Bell, and they said that they would give me a new one when they have more in stock by Friday. After using the one for a week, its getting really hard for me to use another device. Missing the feel, of it in the hands, the sexy build, amazing speaker sound, the gorgeous display, Zoe and blink feed. It feels weird using my nexus 4 now.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
So you can't get it into hboot and flash from there?
Sent from my HTC One using xda premium
gusto5 said:
So you can't get it into hboot and flash from there?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I can, but even after flashing a ROM, or the stock ROM, it ends up in in a stuck HTC boot screen after rebooting
Sent from my Nexus 10 using Tapatalk HD
gusto5 said:
So you can't get it into hboot and flash from there?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Second that, hardly believable that you couldn't boot into hboot and enable fastboot and do some work from there AKA if your device is rooted, find the command for installing a recovery and boom.
Sent from my HTC One using xda premium
beforedenied said:
Second that, hardly believable that you couldn't boot into hboot and enable fastboot and do some work from there AKA if your device is rooted, find the command for installing a recovery and boom.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Does it boot cycle? I did that to mine when i got it and it kept on rebooting i fixed it though. Let me know.
MAXIUM TROLLING
I really hate people that do that. If you break your device man up and try to fix it, which I'm sure it could have been fixed with a little effort. People like you is why insurance is so high and with crazy deductibles.
Sent from my HTC One using xda premium
EnIXmA said:
I can, but even after flashing a ROM, or the stock ROM, it ends up in in a stuck HTC boot screen after rebooting
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Fastboot flash the boot.img of whatever rom you're flashing. Odds are, you didn't brick it. Wipe everything first. Flash the rom. Flash the boot.img via Fastboot.
Sent from my HTC One using Tapatalk 2
Can't you just use the RUU and go back to stock?
Completely lazy noob! That's all there is to this story....
It's not bricked it could be fixed in 5 minutes guaranteed.
No ...lets just tell HTC a fib and get a second one to softbrick next week :what:
Sent from my HTC One using xda app-developers app
---------- Post added at 01:02 PM ---------- Previous post was at 12:58 PM ----------
EnIXmA said:
I can, but even after flashing a ROM, or the stock ROM, it ends up in in a stuck HTC boot screen after rebooting
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
For the record this Device tends to have a lengthy boot up time on HTC screen ....especially on backups and fresh Rom installs ...a lot of people have been getting this mistaken for bricking ... When it's not it's just time ...I'd almost laugh if he isnt letting it sit long enuff to boot up.
Sent from my HTC One using xda app-developers app
K. I have managed to sideload 3 different roms, fast boot, a db push etc. Still doesn't get past the HTC screen. Mounted my USB through otg and did a nandroid restore of Bell's nandroid backup posted by some one. Bell has not released the ruu yet, other carrier's ruu doesn't work. o yeah, flashed stock ROM too. Left the phone on the HTC boot screen for hours, and it doesn't go past boot screen.
Any other suggestions?
BTW, I own 3 other nexus devices that are all rooted, and have been soft bricked numerous times and were easily brought back to stock. My first HTC device with no carrier ruu.
Sent from my Nexus 4 using XDA Premium HD app
EnIXmA said:
they said that they would give me a new one when they have more in stock by Friday.
Click to expand...
Click to collapse
Right...well, mine is gone since 04/13...and I still didn't receive my new phone.
The phone company will decide whether they want to replace it and I've never had any problems with warranty replacements due to custom software. The phone isn't broke and HTC will simply use the parts or re flash it.
All the hysteria over rooting and custom roms breaking warranty is complete nonsesnse
If you burn out your processor over clicking it that's different of course but he hasn't.
Sheesh give the guy a break.
A phone that soft bricks or boot loops as easily as the one should never of been rootable in the first place.
Hi all does anybody have the problem of putting the 300 on sleep and picking it up a little while later only to find its all the way off?
Sent from my XT907 using Tapatalk 2
i have had this a few times but not sure whats causing it so im gonna try a few things to see whats up, what setup do you have, im on CROMi-X with hunds kernel v10
Yeah, I get this if I don't flash a rom for a few weeks. In other words, cleaning out the cache can help.
CM10.1
Sent from my TF300T using xda app-developers app
robgee789 said:
i have had this a few times but not sure whats causing it so im gonna try a few things to see whats up, what setup do you have, im on CROMi-X with hunds kernel v10
Click to expand...
Click to collapse
Ihave the stock tom but its rooted
Sent from my XT907 using Tapatalk 2
im on warp now mate and ive not had a single random reboot or crash at all
Bad SD Card or corrupt files
applesaregoodforeating said:
Hi all does anybody have the problem of putting the 300 on sleep and picking it up a little while later only to find its all the way off?
Sent from my XT907 using Tapatalk 2
Click to expand...
Click to collapse
I had this problem on my tf300t. I am running kitkat omnirom and cm11. I can run either.
The sleep of death was 100% caused by a faulty sd card. Not sure if it was file(s) or the card. Fixed the problem in both Omni and CM.
Backup your card to your computer.
Erase/Format it using the system you are on.
Verify that the SOD problem is gone.
That has happened several times to me too. Completely stock. Formatted about 3 weeks ago. Has not done it until just now. went to check it and it won't come on. Have to wait til I get home and put it on the charger. I just charged it last night. Maybe I didn't connect it right. Well update when I know for sure.
Sent from my SM-N900T using xda app-developers app
Well bad news for me. Tablet won't come on at all. No lights nothing. I don't know where to go from here. Anyone?
Sent from my SM-N900T using xda app-developers app
billwinkle said:
Well bad news for me. Tablet won't come on at all. No lights nothing. I don't know where to go from here. Anyone?
Click to expand...
Click to collapse
Did you try to hold the power button down for more than 10 secs, then release it? But time it, seems awfully long...
So far that always fixed it for me.
Sent from my TF300T using Tapatalk
I tried bit no luck. Talked to Asus set up rma. $92 to fix it. Sending out today.
Sent from my SM-N900T using xda app-developers app
billwinkle said:
I tried bit no luck. Talked to Asus set up rma. $92 to fix it. Sending out today.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Ouch. $92 that's abit expensive. Perhaps you should had consider to topup abit more to get a new Memo FHD 16GB. It is about $250 at amazon.
I just got an email from Asus. I wil not pay $200 to repair an out of warranty tablet, when I can buy the exact same model from Frys for the same amount. They said the motherboard needs to be replaced. It took them one full week and 3 phone calls to get this quote in the first place. They told me that it was diagnosed on Feb 14.
I seriously doubt I will buy anything from Asus again. I was told that it would cost $92 to fix it. I will not spend that kind of money on an item that could break the minute I get it back as they do not even warranty their own repairs. This tablet was nice while I had it, but it was not the greatest either.
Basically, my N7's screen is frequently unresponsive. I was trying to start something in my launcher, and tried pressing it at least 6 times, but nothing happened. Then I tried swiping between launcher pages, and that worked just fine the first time.
This just started happening on an almost constant basis within the last 30-60 minutes, and I was wondering if anyone else has experienced this, or heard of anyone else experiencing it. I'm running the latest Minimus with Jassy's latest kernel (I just flashed them this morning, but it was probably 4-5 hours ago at least), with the DPI set to 290 (I just raised it from 280 to see if that would help anything). I also cleared the cache and dalvik.
Any ideas?
My girlfriends tablet has done that too, then it just randomly goes back to just fine
Sent from my Nexus 7 using Tapatalk 4 Beta
Why don't you try stock and see if you have an issue. This would allow you to rule things out at least.
Sent from my Nexus 7 using xda app-developers app
Same issue here...both stock and CleanROM
me as well. And this is my second tablet after returning the first one for dead pixels
My tablet is stock rooted and I have just experienced this. I had to reboot in order to fix it. Hopefully this doesn't happen again.
Sent from my Nexus 7 using xda premium
lyall29 said:
My tablet is stock rooted and I have just experienced this. I had to reboot in order to fix it. Hopefully this doesn't happen again.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Same here this has happened to me on stock, but a reboot fixed it.
I've only experienced this using Chrome. it got so bad that I'm using the molasses-in-the-winter-going-up-hill Firefox browser just to be able to web surf.
Same here stock, and clean ROM.. Haven't noticed anything on kanged cm nor pa yet. Can't get otg to work worth a crap either I bought chainfires app to help with otg worked with stock based ROMs but not cm based ROMs .. I'm pissed I bought the 16 GB model..
Sent from my Nexus 7 using Tapatalk 4
dincdoes.me said:
Same here stock, and clean ROM.. Haven't noticed anything on kanged cm nor pa yet. Can't get otg to work worth a crap either I bought chainfires app to help with otg worked with stock based ROMs but not cm based ROMs .. I'm pissed I bought the 16 GB model..
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
It happened to me as well (complete stock). Mostly (if not all) instances were with Chrome. I don't remember it happening again since I switched to Chrome beta. (Fingers crossed).
I just took mine back to Best Buy and exchanged it for the 32gb model. The guy at the store asked if anything was wrong with the tablet and I told him that it would freeze up and I would have to reboot in order to fix it. He told me that all tablets and phones freeze like that and that I should reboot the device at least once a day to prevent the freezing of the screen. I thanked him and told him that I would do that. These salesmen must think that everyone is as dumb as they are.
I hope my new tablet doesn't have the same problem, because if it does I might give up on the new nexus 7.
Sent from my Nexus 7 using xda premium