Been waiting all day for the battery to completely die so G Tab could lose info in temporary memory, as Viewsonic tech support suggested, to see if I can bring my damaged device back up after a bad firmware flash.
It has been 10 hrs, had it on all day. First it was just stuck on the bird screen with lights on non-stop then it went to powering down occasionally. A proceeded on to, after about 8 hrs, to where I would have to push the power button to give it juice to stay on for about 30 secs at a time. That gradually went down to about a second. After 9 1/2 hours went down to waiting 10 minutes pushing the power button and the G Tab still would pop on. In any event it is still stuck on the bird screen and not fully booting. I sure hope this helps with the process of bringing her back up. She never booted the firmware flash.
Fyi nvflash could have had you up and running in minutes (assuming you could get the drivers working right away) there are multiple posts in the dev forum on how to set it up.
This has already been mentioned, but hopefully this points you in the right direction.
Follow this link to download the stock update.zip.
hxtp://forum.xda-developers.com/showthread.php?t=842000
To use nvflash follow the following instructions listed at.
hxtp://forum.xda-developers.com/showthread.php?t=861950
Don't forget to replace x in hxtp links i sent you with t.
Roadzero said:
Fyi nvflash could have had you up and running in minutes (assuming you could get the drivers working right away) there are multiple posts in the dev forum on how to set it up.
Click to expand...
Click to collapse
Took me over 4 hours last night to get the correct drivers.
Once I got past that took about 15 minutes to get my G Tab running TnT Lite 5.0
Roadzero said:
Fyi nvflash could have had you up and running in minutes (assuming you could get the drivers working right away) there are multiple posts in the dev forum on how to set it up.
Click to expand...
Click to collapse
Been trying since last night over 24 hours ago. Read most of the articles. My tab is not recognizing inputs. I'm on Win 7, 64 bit with nvidia drivers on my system from my graphics card and such. Not showing any of the usb drivers I loaded to nvflash. Tried every method posted on this site and then some. For some it is easier than others depends on what equipment you are working with. That was my first resort.
My G Tab after more than 12 hours, still powers on an amazing device.
Cannibul said:
Took me over 4 hours last night to get the correct drivers.
Once I got past that took about 15 minutes to get my G Tab running TnT Lite 5.0
Click to expand...
Click to collapse
God bless you to the poster who posted the useable Win 7, 64 bit nvidia usb file. Finally she came back up!
Related
I bought my wife a Galaxy note 10.1 for xmas. Her choice as she loves her note phone and the stylus. Anyway the thing I noticed over anything is after she had all her apps installed and email setup her tab starts way faster than my infinity. Like she is up and running in 30 sec and I take about 2 1/2 minutes to get to the same point.
Can some of you share what you are getting for startup times from pushing the button to everything ready to go. I am looking at mine to see what is wrong as I can't believe that it should take that long to get started. I guess I just didn't notice as it must have been getting worse since I got it last summer and never noticed until I played with my wife's note.
Thanks
frozenbutt said:
I bought my wife a Galaxy note 10.1 for xmas. Her choice as she loves her note phone and the stylus. Anyway the thing I noticed over anything is after she had all her apps installed and email setup her tab starts way faster than my infinity. Like she is up and running in 30 sec and I take about 2 1/2 minutes to get to the same point.
Can some of you share what you are getting for startup times from pushing the button to everything ready to go. I am looking at mine to see what is wrong as I can't believe that it should take that long to get started. I guess I just didn't notice as it must have been getting worse since I got it last summer and never noticed until I played with my wife's note.
Thanks
Click to expand...
Click to collapse
The infinity definitely takes a little while to boot up, however, mine definitely does not take more than 45 sec, usually is just over 30 sec. When i first got it it was around 45s to 1min, after deleting crapware, unlocking, rooting, and installing clean ROM im fully booted in about 30s.
Best of luck
Was going to post here earlier...
From cold the TF700T that I have lights up in about 50-70 seconds.
Oh, mine does indeed take quite a while. (It takes longer to boot than my XP laptop...) About 2 minutes, almost.
The more stuff you have on it, the longer it takes to boot. Simple as that. Mine is utterly loaded. (I have about 500mb free of the 64gb, as well as two full 32GB microSD's. Last update put it on updating 433 apps. I don't have that many, but I suppose it also counts Android's parts as well)
So I simply don't turn it off if I don't have to. It eats 1% battery in 24 hours, turning it off completely would only decrease my battery, as it takes 3-5% to boot.
Hi folks! Long time XDA lurker (Nexus 7, 10, and Samsung Galaxy Tab 2 7 forums), first time poster.
I picked up a XOOM off of EBay last week. The device ran well once I got it charged, it did software updates and was running on 4.0.3 with no issues until last night. I went to pop in a micro SD card, and when I pressed the power button to get it out of sleep mode, the screen began flashing colors, cycling between all colors, a checkerboard test pattern at one point, gradients from light to dark, etc. I did a bunch of Google searching last night and found one link where someone had the same issue, but no solution was mentioned. I have also looked here, but no luck. The one link I found last night seems to indicate it's some files from ICS getting corrupted during the update to 4.x, but it wasn't really clear whether that was the case or not.
I have tried the power+vol up button trick; that turns the screen off after a second or two, then the light show begins again. I can't find a way to shut off to be able to get it into recovery mode, and I have tried installing the Lord AIO tool but on running it, it seems to be stuck at the 'list of devices attached' section. Any ideas, other than letting the battery run down to nothing, then maybe it being able to get put into recovery mode? The place I bought it from on EBay does have a 14 day return policy, so I have a few days still to figure this out, but not sure how long it'll take to run the battery down. The light show on the screen does time out after about a minute or two, but I obviously can't keep hitting the power button every two minutes until it does finally drain the battery.
I really like the XOOM, it feels like you're actually holding something real & solid, compared to other tablets, and want to get this back up & running again. Any ideas what I can do next?
Received my Nexus 5 today after much waiting due to Google/courier making a mess of my delivery details over the last 9 days...another story altogether.
Straight out of the box, and after putting in my SIM, I stuck the phone on charge for a bit and booted her up, though it seemed like there was a bit of charge in it (40-50%) so felt happy unplugging it during some of the set-up...syncing accounts, connecting to wifi, sending a couple of test SMS and inputting my carriers voicemail number.
Then it crashed as I was reading a text, and wouldn't turn on again.
I put it down to teething problems and left it alone and on charge for a bit, and after 10 mins tried again and everything was fine. Booted up (and super fast at that). Spent another 20 mins or so messing around with wallpapers and adding a couple of apps that I use daily.
Stick it in my pocket to run a quick 10 minute errand (including trying to pair it with the Bluetooth in my car, unsuccessfully), and when I get back to the office I find the phone had shut down in my pocket, and it has now been unresponsive for the last 2+ hours.
I've tried leaving it on charge. Tried every combination of holding down buttons to elicit any kid of response, but absolutely nothing. Not so much as a screen flicker.
Would anyone have any advice on things I could try before I contact Google and pack it back off to them? I'm out of ideas. I can't get it to respond in any way to anything!
robotsonic said:
Received my Nexus 5 today after much waiting due to Google/courier making a mess of my delivery details over the last 9 days...another story altogether.
Straight out of the box, and after putting in my SIM, I stuck the phone on charge for a bit and booted her up, though it seemed like there was a bit of charge in it (40-50%) so felt happy unplugging it during some of the set-up...syncing accounts, connecting to wifi, sending a couple of test SMS and inputting my carriers voicemail number.
Then it crashed as I was reading a text, and wouldn't turn on again.
I put it down to teething problems and left it alone and on charge for a bit, and after 10 mins tried again and everything was fine. Booted up (and super fast at that). Spent another 20 mins or so messing around with wallpapers and adding a couple of apps that I use daily.
Stick it in my pocket to run a quick 10 minute errand (including trying to pair it with the Bluetooth in my car, unsuccessfully), and when I get back to the office I find the phone had shut down in my pocket, and it has now been unresponsive for the last 2+ hours.
I've tried leaving it on charge. Tried every combination of holding down buttons to elicit any kid of response, but absolutely nothing. Not so much as a screen flicker.
Would anyone have any advice on things I could try before I contact Google and pack it back off to them? I'm out of ideas. I can't get it to respond in any way to anything!
Click to expand...
Click to collapse
Try pressing and holding the Power and both Volume Buttons for about 15 seconds. Then try to boot.
abaaaabbbb63 said:
Try pressing and holding the Power and both Volume Buttons for about 15 seconds. Then try to boot.
Click to expand...
Click to collapse
Tried this (which I'd tried to no avail previously), and no joy. Wouldn't boot afterwards.
Left it on charge (which it had been for the 20mins previous to trying this) for another 10 mins. Came back to it, pressed power and it just came on. No boot. It was just already on.
Veeery confused now after trying intermittently to get it to boot for what is hours now.
Should I do a factory reset?
I'll log with Google that this has happened so there's less come-back if it dies again and I need to return it. Haven't tried it with a SIM in yet (need a working phone!), but will report back after that.
robotsonic said:
Tried this (which I'd tried to no avail previously), and no joy. Wouldn't boot afterwards.
Left it on charge (which it had been for the 20mins previous to trying this) for another 10 mins. Came back to it, pressed power and it just came on. No boot. It was just already on.
Veeery confused now after trying intermittently to get it to boot for what is hours now.
Should I do a factory reset?
I'll log with Google that this has happened so there's less come-back if it dies again and I need to return it. Haven't tried it with a SIM in yet (need a working phone!), but will report back after that.
Click to expand...
Click to collapse
I'd fully charge it before doing anything else.
jd1639 said:
I'd fully charge it before doing anything else.
Click to expand...
Click to collapse
Have done now. It's charged and I'm about to retry the SIM.
Possibly of note, after I checked it and saw that it had restarted, I checked the battery log and it showed that it had been running for 29m 25s on battery...yet was on charge. I'd attach the screenshot but I haven't posted here enough times for the forum to let me
It was unresponsive no more than 10 mins previously. 10 minutes would be generous.
Anything I can learn from that?
So the phone lasted all night with some light use. Left my Nexus 4 on with no SIM for alarms so I knew I could wake up this morning, but instead, to my joy, I had two phones alarming at me together!
So it was to my dismay that after I'd read some mails, checked some sites, and left the phone to go and get ready for work for 10mins...I came back to it dead again.
I heard some notifications come through (and I was in the middle of a conversation on WhatsApp, so that was normal). I saw the notification light flashing too, so the messages coming through, or at least the first one, didn't crash it.
It did however start up again, with no SIM, after some cajoling.
Is there some way I can see an error log, or a crash log? Or anything I can install to log this for the next inevitable time? Or is this sounding like a permanent hardware issue and I'll need to return the unit?
There's a thread somewhere you can find it, it will show you how to install stock firmware again.
Do that and if it occurs again, call Google to get a RMA
Sent from my Nexus 5 using XDA Premium 4 mobile app
Re-installing the firmware won't jeopardise my position in sending it back to Google, no?
Just went back to it to put the SIM back in it and it's unresponsive again. FFS.
robotsonic said:
Re-installing the firmware won't jeopardise my position in sending it back to Google, no?
Just went back to it to put the SIM back in it and it's unresponsive again. FFS.
Click to expand...
Click to collapse
No, but you have to unlock the bootloader first before you can flash a factory image and install adb (platform-tools) on your pc, and afterwards relock the bootloader again before sending it to Google.
Hi everyone,
I've been on one heck of a journey with this oneplus one that my wife cracked the screen on. I got that replaced and had it up and running except that it was not able to connect to a network. After doing some searching it seemed like maybe corrupt OS or other software so I started trying to bring it back to stock using the Oneplus toolkit. I got it in fastboot mood but then when I tried to exit that and reboot to recovery the screen went black. The only response I can get out of it now is vibrating if I hold the power button for 10-15 seconds. The same thing happens if I do that plus vol up or vol down. The computer does not recognize the phone. I've tried on a win 8.1 and win 7 machine and I did put the comp into test mode for uploading drivers. I've tried the power+volume trick for getting it to show up and still nothing. The last time it had booted it said something like 70 some percent of battery (I know that can be wrong though).
I'm wondering if this situation is one that seems it needs 12 hours of not being touched, 6 hours of charging, unplug and replug or if this thing is beyond repair. I didn't have too high of hope for it with the no service issue but it would be nice to get at least back to where I was for further troubleshooting. Can anyone point me in the direction of getting a computer to recognize this or tell me what I'm doing wrong? Every other thread I've found people say "Oh it just recognized it suddenly" and I'm not getting that lucky. Thanks for any assistance you can provide!
Ben
Try this: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Keep trying solutions from our forums...they do work eventually
ryanmat said:
Try this: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
Yeah I had seen that one too. I do have an old xp laptop. Maybe i'll give that a shot tonight. If that doesn't work should I assume the battery is low and do that procedure before continuing with the ColorOS restore option?
Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.
thomasanderson said:
Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Plug it into your computer (you'll notice that there will be a longer black screen in-between the bootloops) and hold down the power button for at least 10 seconds or more, then release it after the next vibration and the white BLU screen shows up. It might take a couple of tries.
If you manage to boot into at least recovery but can't boot into the system, then try clearing your cache/dalvik cache and try rebooting into system again.
If all of the above doesn't work for you, then your boot.img/system has gone bad, and you'll have to flash the stock images with SP Flash Tool (both of which can be found on other posts on this forum).
follow the instructions on the SP flash tool thread... sounds like what happened to me after bad flash... theres a lot of information in that thread that will set you up...
Thanks for the quick replies guys. The PC trick didnt work at all. I just called BLU and asked for a replacement(havent heard back from them ironically). I put the phone in the basement so I wouldnt have to deal with that incessant buzzing every 15 seconds. Eventually the battery died. Since I had it powered off finally, I plugged it in for about 10 minutes to give it enough of a charge to power on but not stay on to buzz for another 2 hours. This time I powered it on using the master reset button combo and was finally able to wipe the cache and restart the phone. Took a good 4 or 5 minutes to boot after that, but everything has been fine since. Really dont know what initially caused the issue, never happened before. Good thing too, cause BLU told me that they would send me a RMA within the hour and I still havent heard from them. Think this will be my last BLU phone. Thanks for the assist.
My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app
bolanoboyboom said:
My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app
Click to expand...
Click to collapse
??????
My phone is basically out of the box and I'm getting boot loop problems when I first boot. This happens like once a month
Sent from my PURE XL using XDA-Developers mobile app
This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.
Update
num1greeter said:
This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.
Click to expand...
Click to collapse
I tried to flash the phone, but the bootloop apparently wouldn't allow that. I had 0.0% progress after 3 hours. I then tried to go back into the menu you get from {Power}{Vol UP}: still no go. So, I started to take the phone apart again to get ready for shipping. The battery was still low so it didn't take long for it to die after I unplugged it from the computer. Out of curiosity, I tried to repeat finding the menu like I did earlier that day (conditions were that the phone had no charge when I connected it to the computer, and my SD card was removed.) No go. But, then I hit {Power}{Vol Up}{Vol Down} just to see what happened, and boom. My phone loaded up. No loop... Figured somehow the files had copied and the status bar was wrong. Turned the phone off, put my SD card back in and turned the phone on. Loop reappears ...I waited for the phone to die again, took out the SD, attempted to turn it on and the loop was there. Connected it to the computer and hit all 3 buttons, and the phone loads up. So, now I'm confused. Is there any way that the problem is some crappy connection to the SD?