Related
Hello again everyone, im here with another new problem. Out of the blue.
This is what happens.
-Phone is on
Hold down power
Shut off
-Phone shuts off screen goes blank
5 seconds pass
-Phone boots up... never touch a thing....
WTF?
It will not stay off, no matter the rom, I pulled the batter,SD,SIM nothing will shut it off unless i pull the battery.
I've downgraded the phone with the ace hack kit, ive re-rooted. nothing. I've searched, nothing. Anyone out there got a clue? Cus I dont.
FYI:when the phone rebooted after it flashed the downgrade during re-rooting, the alarm was going off and had the snooze button and everything, no matter what it wouldnt go off. but I just went on with the root process and now its gone, but the phone still wont stay off, something just screwed up!
That's hilarious, and I don't mean that literally. I am laughing though, kind of. Why? Because the same thing just happened to me last night. I know I said the exact same thing you said, possibly more. I have been on the same rom for a week and the only thing I have done was update a couple of apps from the market last night. Nothing else was done. Suddenly I can not power off the phone, it simply shuts off for five seconds and then reboots. I have wiped, restored, and tried flashing and the issue still persists. I am heavily researching and experimenting on what could be the cause for this issue. If I figure it out I will be sure to let you know.
Wolf_2 said:
That's hilarious, and I don't mean that literally. I am laughing though, kind of. Why? Because the same thing just happened to me last night. I know I said the exact same thing you said, possibly more. I have been on the same rom for a week and the only thing I have done was update a couple of apps from the market last night. Nothing else was done. Suddenly I can not power off the phone, it simply shuts off for five seconds and then reboots. I have wiped, restored, and tried flashing and the issue still persists. I am heavily researching and experimenting on what could be the cause for this issue. If I figure it out I will be sure to let you know.
Click to expand...
Click to collapse
Lol that is funny, what apps did you update?
I also have a problem with charging the phone and not sleeping, i was starting to think that it was just finaly getting worst
The only apps that were updated were Battery Monitor widget, Elixir, Xfinity TV, and one more which I can't remember right now. If you do get your phone to shut off, which I have been able to do twice, it may not wish to power back up, which is what mine does now also. (Laughing hysterically now.) Just pull the battery out and put it back in and it will power up. My feelings are that this may have been caused by some kind of update. Possibly from the market or from ATT. I have tried three different roms and it is still doing the same thing. I am about to wipe and restore the phone back to stock and see if it does it still. I will keep you appraised.
Wolf_2 said:
The only apps that were updated were Battery Monitor widget, Elixir, Xfinity TV, and one more which I can't remember right now. If you do get your phone to shut off, which I have been able to do twice, it may not wish to power back up, which is what mine does now also. (Laughing hysterically now.) Just pull the battery out and put it back in and it will power up. My feelings are that this may have been caused by some kind of update. Possibly from the market or from ATT. I have tried three different roms and it is still doing the same thing. I am about to wipe and restore the phone back to stock and see if it does it still. I will keep you appraised.
Click to expand...
Click to collapse
I dunno, I already did that and it did nothing, but I guess its worth a shot for you...
And I dont have any of those apps
If I find something I'll post here
/me shrugs
I am very confused by this, but I will have to try a restore to stock to see what happens. I do find it strange that two different people had this happen to their phones at about the same time and day. I will let you know how things progress later.
Edit: What version of Clock Work Mod recovery do you have installed and which rom were you running? Trying to go through the variables with this issue.
Wolf_2 said:
I am very confused by this, but I will have to try a restore to stock to see what happens. I do find it strange that two different people had this happen to their phones at about the same time and day. I will let you know how things progress later.
Click to expand...
Click to collapse
Yeah it is odd, could be coincidence, could be related, dunno, I dont see how it could be an ATT update when nearly all the roms here have that function disabled. Then again maybe you know something I don't
What did you do to get it to turn off finally? I dunno if I wanna try now that you said it wouldn't turn back on.
Also, what rom where you on when it started, I was on CM nightly #121 or maybe #120 I forget
I just happened to come across this in the general section
http://forum.xda-developers.com/showthread.php?t=1145495
no fix though
I am restoring an old rom and I will try changing the date as someone suggested to see what that does. If it does not work then I will have to wait until later tonight to return the phone to stock and go step by step from there.
Wolf_2 said:
I am restoring an old rom and I will try changing the date as someone suggested to see what that does. If it does not work then I will have to wait until later tonight to return the phone to stock and go step by step from there.
Click to expand...
Click to collapse
Could this have something to do with partitioning the SD card? I think i remember reading that clockwork bricked some phones, is that true?
I believe CWM did have some problems partitioning before. Not sure if it still does. It seems like I have found a fix for myself. I turned off automatic system time and date and reset the date to January 2012. The phone seems to be working like it did before this occured. I will wait until tomorrow and change the date back to automatic and see if the power issue shows back up, but for now it seems ok.
Edit: I changed the time and date back to automatic and it is working like it should again. Did you get yours working again or is it still having problems?
Wolf_2 said:
I believe CWM did have some problems partitioning before. Not sure if it still does. It seems like I have found a fix for myself. I turned off automatic system time and date and reset the date to January 2012. The phone seems to be working like it did before this occured. I will wait until tomorrow and change the date back to automatic and see if the power issue shows back up, but for now it seems ok.
Edit: Did you get yours working again or is it still having problems?
Click to expand...
Click to collapse
This worked for me also.
im still having this phone wont shut off issue as well. i have set it to the same date as u and turned off auto and it still just reboots when trying to turn it off
Try leaving automatic off for a whole day. Then see if it is still having this problem. Also replied to pm but try this first to see if it gets past it and works..
willdo thanks a bunch
BAleR said:
Hello again everyone, im here with another new problem. Out of the blue.
This is what happens.
-Phone is on
Hold down power
Shut off
-Phone shuts off screen goes blank
5 seconds pass
-Phone boots up... never touch a thing....
WTF?
It will not stay off, no matter the rom, I pulled the batter,SD,SIM nothing will shut it off unless i pull the battery.
I've downgraded the phone with the ace hack kit, ive re-rooted. nothing. I've searched, nothing. Anyone out there got a clue? Cus I dont.
FYI:when the phone rebooted after it flashed the downgrade during re-rooting, the alarm was going off and had the snooze button and everything, no matter what it wouldnt go off. but I just went on with the root process and now its gone, but the phone still wont stay off, something just screwed up!
Click to expand...
Click to collapse
I had that problem, but it was the car app. I had to disable it in the settings.
seems this keeps happening more and more to people. i still have yet to solve my issue
well i retried setting the date on the phone but this time i chose 1/1/2011 and now the phone stays off when i turn it off which is nice but now i have to deal with having the wrong date
background info:
I am (or was) running MHX superlite 3.0 rom with romracers stockish 0.3 kernel.
UCLA3 modem and radio.
So today my phone decides to restart itself and never will load past the "first two"
samsung screens.
Once these "two" samsung logos pass by, the screen turns blank (not on)
and starts to vibrate with 1 second intervals.
The only way for it to stop is if I pull the battery.
Heres the weird part.
I tried to ODIN back to stock...once I put my phone into DOWNLOAD MODE.
The little android guy that says DOWNLOADING "dont turn off" will show for a millisecond and then the screen will shut off and start the vibrations. ODIN will not recognize the device either
So what I have is a phone that wont load past the samsung logos if the power button is pressed
AND
Download mode works, but the screen will turn blank and vibrations start buzzing.
My phone is having seizures. The only way to stop the vibrations is by pulling the battery.
I have accepted the fact that the phone may be done for.
It was a great 4 months together. tear*
Well, if you can't get it sorted out there's always this! Unless the hardware is busted, but maybe he can fix that too??
http://www.youtube.com/watch?v=AkJQAbwZjRk
Did you try booting into recovery mode instead of odin?
Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.
silver03wrx said:
Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.
Click to expand...
Click to collapse
No, its not. Can't OC or UV. It can only UC.
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3
if u can boot into cwm flash darkside
OP... what rom/kernel/modem were you running before MHX-SuperLite? and what wipe process did you use prior to MHX flash?
Can you get into recovery and restore a backup?
If you don't have a backup and can get into recovery, try wiping data/cache, then go into mounts/storage and format system, data, and cache, then go to advanced and wipe Dalvic cache. Then power down and try to Odin back to stock again.
If this doesn't work, try another data cable or usb port on your machine (or another pc if this doesn't work). Maybe communication is getting lost due to bad usb connection...
EDIT: Are you saying you tried to Odin even though Odin wasn't recognizing your phone? That could be part of the problem. Try re-installing the Samsung drivers and see if Odin sees it then.
If you can get into download mode you aren't hard bricked yet...
I think he is saying that Odin recognizes his phone but his phone goes black before he can't start the reflash right?
Sent from my SAMSUNG-SGH-I727
Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.
Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts
DoctorQMM said:
Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.
Click to expand...
Click to collapse
MHX is great. The rom has nothing to do with it i believe
Jooosty said:
Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts
Click to expand...
Click to collapse
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!
skrambled said:
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!
Click to expand...
Click to collapse
He already said Odin/connection isn't the problem. His phone won't stay on long enough for the communication to be made. According to what he said, it has nothing to do with machine/drivers/cable. He needs a way of keep the phone on long enough to make the connection, or somehow communicate with it another way. Unfortunately, I have no ideas. Although, I really hope someone does. That RussianBear guy seems to be onto something with communicating with the emmc without the phone being on... or something like that.
heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/
Jooosty said:
heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/
Click to expand...
Click to collapse
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.
plwalsh88 said:
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.
Click to expand...
Click to collapse
Or even a external battery charger maybe there is just enough juice to turn on and then dies
Sent from my SAMSUNG-SGH-I727
The battery is fine. Wouldnt keep rebooting if otherwise. O well.
Just bought a captivate to feed my android in me
Sent from my SAMSUNG-SGH-I897 using XDA
DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litmus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....
xtechx said:
DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litinus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....
Click to expand...
Click to collapse
What ROM were you on man?
Sent from SKYROCKET
NexusMod 4.0
Faux 010m
Let me try to explain as comprehensively as possible what happened before I couldn't start my Nexus S again.
Until yesterday, I was running an older CM9 Nightly, together with the Matrix CFS kernel (18.0) and an older reloadedICS mod. Everything was running fine. Well, except for the fact that every time I rebooted, it took 2 or 3 times before it actually started. So 2 or 3 times, while rebooting, my Nexus S rebooted again, or just crashed so that I'd have to pull out the battery. But when my Nexus S finally started, it worked fine. I still had the occasional crash, but everything worked.
Yesterday, I decided it was time for a new nightly. So I downloaded the CM9 nightly from 7 april, the latest gapps, the newest matrix CFS kernel (18.5), and the Reloaded ICS 1.9b2 mod. Before I flashed everything, I wiped cache/dalvik cache, as always. I did flash everything at the same time though.
I didn't like the new icons in the statusbar from the latest Reloaded ICS mod, so I downloaded a different version of the Reloaded ICS 1.9b2 mod that someone had uploaded, with the different icons. That also worked fine. Every icon changed, except for the battery icon.
I used my Nexus S for the day. I listened music, browsed the web, whatsapped with some people... It worked fine. Then I went and watched some TV. After that I went to bed, and I noticed the battery of my Nexus S was empty. Since I wanted to check my mail/facebook before I went to sleep, I put my Nexus S in the charger. I started it, that worked fine. It said the battery had 0% on the statusbar, and because of the new battery icon from the Reloaded ICS mod, you can't see anymore if your Nexus S is charging. But it started, so I guess that's what counts.
So I started facebook (in the browser). Halfway loading, my Nexus S crashed. I experienced crashes before, certainly with CM9 nightlies, so I wasn't really surprised. I pulled out the battery, because the power button wasn't working (again, wasn't surprised, that's normal with that kind of crash).
And that's when things went wrong. My Nexus S wouldn't start again. I tried starting it in fastboot mode. Didn't work.... I put it in the charger for the night, but the charge icon (the white battery icon) didn't show up on the screen. And the next day (today), it still didn't start. I know someone who also has a Nexus S, so I tried his battery. Didn't work. I tried his charger. Didn't work. But when he tried MY battery and charger in HIS Nexus S, it DID work! Well, except for the fact that his Nexus S is still trying to boot up, after half an hour...
So that's two Nexus S's dead. One that won't even charge anymore. The other at least shows signs of life. I have no idea how this is possible. Clearly it has something to do with pulling out batteries, since his Nexus S wouldn't start anymore after he pulled out the battery when it was still turned on, and my Nexus S wouldn't start anymore after I pulled out the battery when it crashed.
By the way, my friend's Nexus S is not rooted. He is using stock ICS.
Thanks a lot in advance!
Edit; i also noticed that my battery was going down exceptionally quick after the 7 april nightly. I don't know if this is relevant.
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Harbb said:
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Click to expand...
Click to collapse
Thanks for your help! I'm going to try that.
Yes, his phone can enter bootloader.
I've found some other people on the internet with the same problem as me. First there were problems with rebooting (it would only start after the second or third try). Then the battery drained exceptionally quick. And then, no signs of life at all... http://groups.google.com/a/googlepr...gory-topic/mobile/android-devices/06zm2LENFpc
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Harbb said:
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Click to expand...
Click to collapse
My friend can't get into recovery anymore... It shows the green android icon for a flash of a second, and then it shuts down... But at least he can get into bootloader mode... I guess that's something.
I guess it has something to do with my battery, since that is what killed my friends Nexus S. I don't think my problem will ever be fixed though. That ubuntu app is worth a shot, but for that I need a computer that can run ubuntu and windows, and I don't think I have that.
I've also found this: http://mobiletechvideos.mybigcommerce.com/nexus-s-jtag-brick-repair/. Is that worth a shot? I'm willing to pay that kind of money for it. I do a lot of things myself without having too much knowledge, but this goes a little too far...
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Harbb said:
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Click to expand...
Click to collapse
That tip with the bright lamp really worked! Thanks for that! But the first time he didn't do the factory reset yet, and now he can't even see the recovery menu (not even with a bright lamp), just the exclamation mark...
He needs to press Power + Vol. Up while he can see the exclamation mark. This will exit the splash screen and enter the actual recovery menu.
Thanks! But the factory reset didn't work, unfortunately... He is still stuck in boot...
As a matter of fact, oldblue has written up good instructions to get the phone to factory-stock state and fastboot flashable images. These should overwrite everything that should be overwrited on the phone and throw stock google stuff on there. Definitely something to try out, i would be doing this beyond anything else.
Note that it requires unlocking (and relocking later) the bootloader, and this will also erase all data on the phone and internal sdcard.
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Happy to help and best of luck. Definitely use AdamOutler's app to the best of it's ability, it can do damn near anything. There is one more thing to try on top of this too if nothing goes to plan but it could be a potential sacrifice (minor hardware mod). Let's just hope this works.
The fastboot images would be, theoretically, a more perfect way to return to stock, so if this is possible to fix by software alone you'd be hard at work trying to find a better alternative. Maybe your phone is recoverable after all.
Androyed said:
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Click to expand...
Click to collapse
No dont try the ubuntu tool unless it doesnt turn on, you cant boot into bootloader or you cant turn it on, and you see nothing on the screen.
---
die tool is voor echte gebrickte nexussen.. gebruik die aleen als je dus niks meer ermee kan, zoals dat hij nieteens in de bootloader kan booten. (dat was met demijne gebeurd).
succes , als je vragen hebt PM me maar.
Same Problem?
Hey guys, i have a Nexus S (never rooted or anything). I received the update notice for ICS so i duly updated. Right after, my phone was bricked. Doesn't turn on / respond to anything.
I ran the UnbrickableRessurector by Adam and I can get Fastboot Mode to show up this way. I was really hoping that i don't have to unlock it or anything as i don't want to void warranty.
Any thoughts? I tried selecting 'recovery' after which the screen goes dark. Shining a bright light on the display doesn't help - really can't make out anything. Do i have a different problem?
Thanks!
So my tablet got unplugged during the NVFLASH process shortly after formatting the partitions. It is now stuck in NVFLASH. Is there anyway I can reboot it or do I need to wait for the battery to drain and for it to die.
I have been having problems with my power button not responding when pressed so I filed for an RMA. They said to send it back but I wanted to flash back to stock before sending it. Could I send it to them like this ans say that it just stopped working or do I need to reflash to stock. Its a B50 so I know it can be fixed I just dont want to waste time waiting.
If you still have service on your tf they will repair your power button , i don't know if they flash new software files because of your button. What i do know they have to test your button and then they will see that it won't boot.
So with a bit of luck they will flash new files bcause of the whole startup problem with the power button.
Good luck
Let the battery drain, and NVFlash to stock. It will seriously help if you don't want to deal with any crap if they see you were rooted.
You don't have to let the battery drain.
When I bricked mine, my battery was low when I started the nvflash process, then the process failed b/c I forgot to put the files where they were needed, so I unplugged my transformer, let it charge for a little bit more so the battery wouldn't die while I found the files needed, then I plugged it back into my laptop and did a reboot into nvflash and let it do it's thing.
So I am having a weird issue with nvflash; it randomly quits mid-process. Sometimes nvflash stops when initializing the boot loader while other times it starts formatting the partitions and then stops. A few times it has even kicked my tablet out of apx mode.
Has this ever happened to anyone?
Is your cable bad? That's all I could think of, try several different USB ports as well.
Thing O Doom said:
Is your cable bad? That's all I could think of, try several different USB ports as well.
Click to expand...
Click to collapse
I tried multiple usb ports on two different computers. My macbook running ubuntu and a windows pc both have the same issue. I will try using another cable but dont know if that will help.
If I send the tablet back in this condition (no OS and NVFLASH not working), will they say its user error?
So I was never able to get the tablet to boot up. I am not sure what the issue was but I believe that the battery was almost dead but not quite. This left the tablet in nvflash mode, unable to charge. When I tried to transmit data however, it created too much of a load on the tablet and it would fail. I sent the tablet to asus as is and I just got a notification that they fixed everything and are sending it back to me. In case somebody is in the same situation as me it seems they did not care that all the partitions were formatted blank, just that there was no custom rom installed.
Good that it was resolve, and that they didn't give you any trouble.
I went to use my 300 today after not touching it for a couple weeks (been busy with my new evo 4g lte) and it was stuck on the asus boot screen. Tried rebooting a number of times with various button combos, long pressing the power button and all and it will not pass this screen.
I had the latest firmware installed prior to this issue.
Anyone have any suggestions?
Did you try cold booting? To do this, power off your tf. While holding the vol down button, then press and hold the power button. You will see white text at the top. Let go of the buttons and it should boot to a screenasking if u want to wipe data. Dont presss anything and let it timeout and reboot.
cavsoldier19d said:
Did you try cold booting? To do this, power off your tf. While holding the vol down button, then press and hold the power button. You will see white text at the top. Let go of the buttons and it should boot to a screenasking if u want to wipe data. Dont presss anything and let it timeout and reboot.
Click to expand...
Click to collapse
I did indeed try that, still did nothing
Right now I have it sitting unplugged waiting for it to run out of power.
Well thats not good. You could download and play a movie on it to help expedite the battery discharge. If after that and it still doesn't work, consider doing a wipe/factory reset as a last ditch effort. After that, you are looking at a store return or warranty repair. If this was the 101, you would have utilities to fix that but we dont have such things for the 300 yet. Good luck my friend.
cavsoldier19d said:
Well thats not good. You could download and play a movie on it to help expedite the battery discharge. If after that and it still doesn't work, consider doing a wipe/factory reset as a last ditch effort. After that, you are looking at a store return or warranty repair. If this was the 101, you would have utilities to fix that but we dont have such things for the 300 yet. Good luck my friend.
Click to expand...
Click to collapse
If I could play a movie I wouldn't be in this situation
It's weird because The only people I've seen with issues like this were rooted or trying to flash roms.
Lol yea you are right on that. Ive seen this happen with unrooted 101s before. For whatever ryme or reason something in the system gets borked and prevents it from booting properly.
Try to do a factory reset, it should solve the problem
nooktablet said:
Try to do a factory reset, it should solve the problem
Click to expand...
Click to collapse
As in wipe data from the cold boot menu?
Was hoping against that as this wasn't really something I brought on myself through flashing and tinkering.
If this happens again I'll be doing an rma I'd say. Either way I have plenty of time for other suggestions, just hoping someone has some!
Tried wiping data and still stuck, just tried resetting with a paper clip and still no go as well. I'm assuming it's bricked at this point.
Brandito said:
Tried wiping data and still stuck, just tried resetting with a paper clip and still no go as well. I'm assuming it's bricked at this point.
Click to expand...
Click to collapse
Yeah, I'd return it. Without root or unlock, it would be impossible to modify anything even if we knew exactly what was wrong with it.