Database Info

[Q] uh oh...

Ok.... so, I done gone and did it. I think I managed to brick my gtab. Which is odd, because it was working one minute, then said "shove off" the next.
I was running the VEGAn-Tab Gingerbread Alpha and couldn't stand the lack of hardware acceleration anymore. Choppy video, games, and such. So, I decided to jump back to 5.1. I flashed the .8 recovery again and was able to get it installed zero issue. I was even running 5.1 for a good day or two. I was in the middle of redoing the Angry Birds levels since the backup data from GB wasn't playing nice for just that one app.. I noticed there was no sound after a bit, thought another app might have been holding priority over the audio, so I went to reboot. Shuts down, when it should reboot, the screen just stays black. The screen is definitely on, just blank.
The power button shuts it off after a second or two of holding it, so it's still functioning from some form of data to know to do that... I figured nvflash might work, but I can't figure out how to get it going without my computer picking up on a USB device.
Have I just screwed myself here, somehow? any ideas?

theclassicalgod said:
Ok.... so, I done gone and did it. I think I managed to brick my gtab. Which is odd, because it was working one minute, then said "shove off" the next.
I was running the VEGAn-Tab Gingerbread Alpha and couldn't stand the lack of hardware acceleration anymore. Choppy video, games, and such. So, I decided to jump back to 5.1. I flashed the .8 recovery again and was able to get it installed zero issue. I was even running 5.1 for a good day or two. I was in the middle of redoing the Angry Birds levels since the backup data from GB wasn't playing nice for just that one app.. I noticed there was no sound after a bit, thought another app might have been holding priority over the audio, so I went to reboot. Shuts down, when it should reboot, the screen just stays black. The screen is definitely on, just blank.
The power button shuts it off after a second or two of holding it, so it's still functioning from some form of data to know to do that... I figured nvflash might work, but I can't figure out how to get it going without my computer picking up on a USB device.
Have I just screwed myself here, somehow? any ideas?
Click to expand...
Click to collapse
Sounds like a brick to me, same thing happened to me.
Luckily for you the gtab is virtually unbrickable.
Follow the method from the following thread to get your gtab back to stock.
http://forum.xda-developers.com/showthread.php?t=861950
G'luck

Yep, Semibricked.
Happened to me 2 days ago. See the last post from me, pazzu510 and you´ll see some images from the process. XD It makes it so easy to have ubuntu specially linux mint(i dont know if the "run in terminal" works in other distros and in which).
Good luck and dont get too worried. Not even data get lost(just some apps).

Pazzu510 said:
Yep, Semibricked.
Happened to me 2 days ago. See the last post from me, pazzu510 and you´ll see some images from the process. XD It makes it so easy to have ubuntu specially linux mint(i dont know if the "run in terminal" works in other distros and in which).
Good luck and dont get too worried. Not even data get lost(just some apps).
Click to expand...
Click to collapse
wait... there are actually running versions of Ubuntu on this thing? I've been hoping for that since I decided on this thing over the Adam. lol I've only seen a few posts around for Karmic.
I'll give the methods mentioned a try and report back. I'm glad this is fixable. My only experience with this stuff is with my Droid and old iPod Touch(which I semi-bricked quite a few times with all of my tinkering. lol)
edit: Wait.. sorry.. I just realized you meant on a normal computer. lol My brain kinda jumped the gun there, for a second. lol

Ok... So, I had no choice but to do the nvflash from linux because windows 7 decided it didn't want to play nice with the drivers. I've been meaning to dual-boot Ubuntu anyway, so it pushed me into doing that now instead of procrastinating. lol
I did the nvflash without any issues, got back into android. It reinstalled TnT, but whatever.
Enter issue number two... It works "fine"(about as good as the stock TnT, pre-updates could.. lol). I go to reboot, screen doesn't come on at all. Not even the on but blank. Not even the back light this time. nvflash cures it, but if I ever turn it off, it does the exact same thing. I was hoping to switch back to VEGAn 5.1.1 or at least get the stock TnT updated. I can't reboot for the update or the same thing happens. Which also leaves out hope for getting into recovery to format.
I went from ... lol

Its rebooting into apx mode. Exact same thing Happened to me a month back. You need to make sure you are using the correct nvflash files. Which ones are u using?
Sent from my Evo 4G using Tapatalk Pro

xRepinsSporx said:
Its rebooting into apx mode. Exact same thing Happened to me a month back. You need to make sure you are using the correct nvflash files. Which ones are u using?
Sent from my Evo 4G using Tapatalk Pro
Click to expand...
Click to collapse
I was using the files in the zip with the later date in bekit's dropbox. I figured they were just updated files. I'll give the other one a try and see how that goes.

yup. That was it. I used the other set of files and it's working fine now. Thanks for catching that. I probably would have went a few more days before trying that. lol

Np man in glad you got it.
Sent from my Evo 4G using Tapatalk Pro

[Q] Help! Frozen Phone! Captivate

Hello, everyone.
Ok I'll explain the situation, then explain how it might of happened.
My phone will not turn on. It is stuck at the white at&t screen.
How It Happened:
I went out camping with family. We decided to go boating, No I didn't dunk the phone in lake water. I was listening to music on the boat, I noticed that an error message kept coming up. It said something along the lines of "com.android.phone has stopped unexpectedly, please try again." I would get this message every other second. So I booted the phone into clockwork recovery, hoping to recover an old back up of my system. It didn't work, I got some other error message saying it couldn't recover. Being desperate, I was like, "I'll just flash a different ROM!" I tried flashing cognition. It said it installed correctly. I was stoked! I rebooted my phone. I noticed it still showed the cyanogenmod 7 boot animation, so of course it didn't flash the other ROM. I decided to reboot my phone again. This time instead of turning all the way on, it stopped at the cyanogenmod animation, then restarted. It looks as if, right before it would restart it looked like a "loading screen" in clockwork recovery. It rebooted continually for the next 10 minutes until I took the battery out. I then tried to recover the phone again. Then I rebooted my phone, but then it froze at the at&t white screen. I left it like that for around 20 minutes. As we were coming back to the dock, I decided that I had enough messing with it and turned it off.
Any ideas. Did I do what they call "Bricking" and if so, what can I do to fix it?
And if not what do you think I did?
Thanks for help. I am getting a new phone in 2 days.
Btw, I am running through AT&T, and I own a sumsung captivate.

Well, the phone does sound like it has a pretty solid issue, I would have assumed that the flashing would have fixed it. There are probably other things you can try to get it running, but honestly after everything you've done, I would just Odin the phone. There are plenty of posts in the dev forums about running Odin. You download it on PC, plug the phone into download mode, click the button in Odin and after a bit, bam you are back to stock 2.1 like it's right outta the box. Then the obvious, root/rom. Unless you are desperate to get data off the phone I would just use Odin.
Someone may have a better answer, but weird stuff like that, I don't bother with trial and error. Just make sure if you do go with the Odin route, follow instructions, or you definitely WILL brick the phone. If you need the link because you actually can't find it on the forums (sigh) then I can send it tomorrow, it's bookmarked on another PC. Hope this helps

DanBroChill said:
Well, the phone does sound like it has a pretty solid issue, I would have assumed that the flashing would have fixed it. There are probably other things you can try to get it running, but honestly after everything you've done, I would just Odin the phone. There are plenty of posts in the dev forums about running Odin. You download it on PC, plug the phone into download mode, click the button in Odin and after a bit, bam you are back to stock 2.1 like it's right outta the box. Then the obvious, root/rom. Unless you are desperate to get data off the phone I would just use Odin.
Someone may have a better answer, but weird stuff like that, I don't bother with trial and error. Just make sure if you do go with the Odin route, follow instructions, or you definitely WILL brick the phone. If you need the link because you actually can't find it on the forums (sigh) then I can send it tomorrow, it's bookmarked on another PC. Hope this helps
Click to expand...
Click to collapse
No, I got Odin3. Thanks, I got it back to stock. I got my new Cappy today. I'm sending my old one to AT&T and all that. Thanks anyways.

Let's recap the new update

After about one day of this GB update, what can we tell? Still any issues? Some people bricked their phones, so is there any idea why? Can we recap on what has been achieved this far? Are there any flashable ROMs with all good stuff?

The phone is still buggy. I have been having issue with BT and the phone locked up on a call once.
Basically, sometimes when I turn my BT headset off, it will still say it is connected on the phone. I will need to turn the BT off and then back on to get it to work correctly again.
As for the phone locking up. I was on BT and switched over to the speaker phone and the phone just died. I had to do a battery pull to get it to turn back on.
So it really just sounds like they need to work on BT more because I never had these issues on Froyo.

aowendoff said:
The phone is still buggy. I have been having issue with BT and the phone locked up on a call once.
Basically, sometimes when I turn my BT headset off, it will still say it is connected on the phone. I will need to turn the BT off and then back on to get it to work correctly again.
As for the phone locking up. I was on BT and switched over to the speaker phone and the phone just died. I had to do a battery pull to get it to turn back on.
So it really just sounds like they need to work on BT more because I never had these issues on Froyo.
Click to expand...
Click to collapse
Did you update the baseband?

I'm curious about this too! I was about to start a tread, but this one shall do.
Questions -
1. (People having reboots before update)
*Did it fix the reboot issue?
2. (People with signal problems before update)
*Did the new baseband fix this/ do you get better signal now??
3. Another problem I have is that wifi and 4G constantly battle each other to see which one gets the signal. So I have to turn wifi on and off until 2G/4G go away.
(For people that have this)
*Did this get solved?
4. * Does GPS lock faster/work better?
I've had three different phones and I've had same issues with all three and even trying different roms. A different rom might fix one issue, but not the others for me.
My main concern is the reboot and signal issues!
These are questions for people that have same or similar issues.
NOT for people with no issues before update.
So please NO "There is nothing wrong with my phone!" People.
Thanks!!
....

For those who are still having problems after the update it might be wise just to do a factory reset because froyo and gbread is very different...

* GPS locks much faster now, often instantly, and indoors.
* Switching between 2G/4G seems to be smoother; doesn't lose the connection for a few seconds like it used to

htc2364 said:
I'm curious about this too! I was about to start a tread, but this one shall do.
Questions -
1. (People having reboots before update)
*Did it fix the reboot issue?
2. (People with signal problems before update)
*Did the new baseband fix this/ do you get better signal now??
3. Another problem I have is that wifi and 4G constantly battle each other to see which one gets the signal. So I have to turn wifi on and off until 2G/4G go away.
(For people that have this)
*Did this get solved?
4. * Does GPS lock faster/work better?
I've had three different phones and I've had same issues with all three and even trying different roms. A different rom might fix one issue, but not the others for me.
My main concern is the reboot and signal issues!
These are questions for people that have same or similar issues.
NOT for people with no issues before update.
So please NO "There is nothing wrong with my phone!" People.
Thanks!!
....
Click to expand...
Click to collapse
I had reboot issues before and so far haven't had any, but to make a proper conclusion I'll have to wait, as even before the update sometimes I would make it days between reboots/shut offs and sometimes only hours.
GPS appears to be very good now, as for wifi/4g/2g I always turn off 2g and use only wcdma setting, and haven't had any issues with it, I leave my wifi and BT on at all times too even when not connected and don't have too bad battery strain.
some things I noticed, in the gallery now when I hit share I don't see the gmail option, the camera reverted back to stock, which is a shame because I loved the things the LG cam app had, but there are a lot of camera apps (I love vignette) so that's not a huge issue, if anyone has the lg app I would love it back though.
I did have some sluggishness especially this morning, I downloaded some widgets though so it might be more of what I added than the update itself.
one surprise was that I thought it was supposed to wipe all data etc. from the phone, but everything was set up the same as I had it before with launcher pro, so I was happy I didn't have to start from scratch. Also I have been getting occasional force closes with launcher pro that I didn't have before.
as far as quadrant scores go I'm getting consistant 2600+ so that is good, I had Faux's kernal and OC to 1300 w/ pimpmycpu and was getting 2800-3000 so without OC I'm more than happy with 2600. Now if only netflix will make it's way to this phone as is, and hopefully we can root soon as i really want ROM Manager, pimpmycpu and a few other root only apps to work again! Love this community, everyone is so helpful and creative, keep up the good work.

GPS locks Faster
Google Music Beta offline feature does NOT work, won't download.
Android Market did not restore my previous apps.
Touch screen is still dodgy, sometimes requiring multiple touches.
Email, specifically @Live.com mail will not display junk mail. Other folders, yes, but not junk.
More frequent messages about Cannot connect to Server

Has anyone figured out why some people have bricks trying to update? To be honest I still hesitate to do the update because I still don't know why this happens

MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.

mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
I think it's worth waiting for a rooted flashable version a day or two and to avoid any risks.

mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
<nods head and ducks>

mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
this ^^
even so, i had latest cwm running and i didnt brick **** lol people get so damn worried when the updating bar doesnt move consistently so they start fiddling with **** and boom! brick!

dmartin1976 said:
GPS appears to be very good now...
Click to expand...
Click to collapse
I wish that were true for me. As I've mentioned in other threads, I'm still getting 90-180 second TTFFs, which is about where I was with stock Froyo. I hope someone will reply to my question in the other thread about the system settings they have that give them such good results. I've fiddled with all of the ones in the hidden menu GPS Test section and haven't found a good combination (and I don't know what the factory settings are supposed to be any more); it's hard because of having to wait a few hours between tests to let the ephemeris data expire in the receiver so I won't just be getting a carryover hot fix.
dmartin1976 said:
some things I noticed, in the gallery now when I hit share I don't see the gmail option, the camera reverted back to stock, which is a shame because I loved the things the LG cam app had...
Click to expand...
Click to collapse
Hmm, that's strange; I still have Gmail in the list of options for "Share" in the gallery.
As for the camera, I think I actually like this one better. At least, it seems to do a better job of taking close-ups with the flash. With the original LG camera, close-up flash photos were always blown-out and overexposed. I took a couple of test shots in a dark room with the flash, and they look great, about as good as you can get with an LED flash, I think.

JHaste said:
this ^^
even so, i had latest cwm running and i didnt brick **** lol people get so damn worried when the updating bar doesnt move consistently so they start fiddling with **** and boom! brick!
Click to expand...
Click to collapse
If I recall, once you reach the % range....the install range, it tells you, do NOT disconnect. Some of the pictures people were showing were in the Analyze area, before the actual download and install. I think if you get past the analyze phase you can install. I don't believe you can get past it with CWR installed.
Even still, the anticipated failure rate of an update like this (Bricked), is like 8 digits to the right of the decimal point. Even with the problems MS had with the NODO update on the Samsungs, the total # of failures was like 8 World wide. (or just over half their sales. )
So the process is pretty well tested and known.

alodar1 said:
If I recall, once you reach the % range....the install range, it tells you, do NOT disconnect. Some of the pictures people were showing were in the Analyze area, before the actual download and install. I think if you get past the analyze phase you can install. I don't believe you can get past it with CWR installed.
Even still, the anticipated failure rate of an update like this (Bricked), is like 8 digits to the right of the decimal point. Even with the problems MS had with the NODO update on the Samsungs, the total # of failures was like 8 World wide. (or just over half their sales. )
So the process is pretty well tested and known.
Click to expand...
Click to collapse
I promise you that I did it with CWM installed... I literally restored my stock nandroid, booted into that and then ran the update tool... I only had one hiccup where after i got to the S/W screen (after I had already downloaded but before the update) it said that I did not have the phone connected so i unplugged and plugged back in and that didnt work... so I unplugged, pulled the battery, put it back in, plugged in and everything went smoothly

JHaste said:
I promise you that I did it with CWM installed... I literally restored my stock nandroid, booted into that and then ran the update tool... I only had one hiccup where after i got to the S/W screen (after I had already downloaded but before the update) it said that I did not have the phone connected so i unplugged and plugged back in and that didnt work... so I unplugged, pulled the battery, put it back in, plugged in and everything went smoothly
Click to expand...
Click to collapse
So it seems some folks just had bad luck

krekabl said:
So it seems some folks just had bad luck
Click to expand...
Click to collapse
or the file they downloaded was corrupt? its not like we had an md5 to match...

JHaste said:
or the file they downloaded was corrupt? its not like we had an md5 to match...
Click to expand...
Click to collapse
well everybody updated the same source didn't they?

GPS locks on a lot faster...but still loses accuracy in middle of route.

Thunderbolt autoupdated!!

I don't know how this happened but I look over and see my thunderbolt rebooted (happens maybe once every one or two weeks). Not thinking much of it I look away and then look back a moment later to see the update screen! I would have ripped the battery out but I didn't want to risk bricking it.
I have been hitting reject to the update since it was first released and it's never updated on its own! This is a warning to anyone else that has been hitting reject all this time, it seems it somehow is starting the update process on its own now.

Italianguy said:
I don't know how this happened but I look over and see my thunderbolt rebooted (happens maybe once every one or two weeks). Not thinking much of it I look away and then look back a moment later to see the update screen! I would have ripped the battery out but I didn't want to risk bricking it.
I have been hitting reject to the update since it was first released and it's never updated on its own! This is a warning to anyone else that has been hitting reject all this time, it seems it somehow is starting the update process on its own now.
Click to expand...
Click to collapse
The phone doesn't auto-update.

g00s3y said:
The phone doesn't auto-update.
Click to expand...
Click to collapse
Well apparently it can because it has been sitting at my desk at work all day and I haven't touched it. It vibrated and I look over and see the HTC splash screen and then it went to the update logo. If it was just sitting there how else can you explain it?
It rebooted several times and now the data icon is different, mobile hotspot doesn't work, and there is a new Verizon data widget. It updated on its own.

Resistance is futile.

mine updated itself too last night. I plan to reject the update since i still had a working hotspot up too last night. I looked at my phone and the update was already in progress and halfway done.
No i am concidering root but wanted to stay stock. Someone just posted that they were rooted and stock and this automatic update caused their phone to brick.

what update? we haven't had a OTA since early july.

fixxxer2008 said:
what update? we haven't had a OTA since early july.
Click to expand...
Click to collapse
The same one. I never received the 7/8 update until last night. They are still pushing out the mr2 update which should give you an idea of how close GB is...not very

microdot said:
The same one. I never received the 7/8 update until last night. They are still pushing out the mr2 update which should give you an idea of how close GB is...not very
Click to expand...
Click to collapse
gb is closer than you think. i always said a fall release anyways.

microdot said:
They are still pushing out the mr2 update which should give you an idea of how close GB is...not very
Click to expand...
Click to collapse
Huh? It's coming Q2, and this is only June 86th.

I can confirm that the phone did "auto-update". I had been hitting reject on every notification for the update (so i could keep using the mobile hotspot). When i woke up this morning (or yesterday morning, i cant remember) - my phone had the new verizon icons, new version number, and mobile hotspot didnt work anymore (prompt to buy $30/month feature).
I'll guess i'll finally have to root and install some ROM.

mike.s said:
Huh? It's coming Q2, and this is only June 86th.
Click to expand...
Click to collapse
LOL!!!
That's why summer won't end. I don't have my GB update yet!

I can confirm my phone auto-updated last night too, it failed the updated and keeps rebooting.

g00s3y said:
The phone doesn't auto-update.
Click to expand...
Click to collapse
Yes it does. In fact, I suspect what happens is when the screen/menu pops up with 'accept, reject, or the 3rd option (??)', if you don't respond within a certain time, it defaults to 'accept'.

I think is too much coincidence that more than one person had the same issue the same night. Verizon you !#$% failz!

Same here. Updated this morning right when my alarm was supposed to go off. Luckily the flashing lights woke me, but it was too late as it was already on the update screen and couldn't risk pulling the battery.
Sent from my ADR6400L using Tapatalk

http://www.thunderboltforums.com/fo...-get-rid-ota-forced-reboots-rooted-phone.html
I got this from another thread, solution #1 seems to have done it for me...

i got the same problem as everyone else
===
So I plugged in my phone last night and rebooted it, only to find ClockWorkRecovery giving me a warning message saying that some update has failed (details below), and if I tell it to reboot, it will properly enter Android and load all my stuff, but within seconds of loading up properly, the phone FORCE shuts down.
Power Off - Shutting Down, and there is nothing I can do to stop it.
I have the latest CWM 4.0.1.5, i just flashed it. I did a backup just in case, as I don't know what steps to take.
While booting up..the phone will look like its installing something, but then fails.
Press the menu key, CWM opens up and I see the following.
===============
ClockworkMod Recovery 4.0.1.5
Finding update package...
Opening update package...
Verifying update package...
E: failed to verify whole-file signature
E: Signature verification failed
Installation aborted
================
I know Verizon has been bugging me with that firmware update, but I've been denying it every time. There is no way it would have downloaded already, would it? I didn't accept any software updates.
I've tried rebooting phone from cold shutdown, taking memeory card out. I have't restored to previous ROM, or dont any wipes/factory resets. I dont wanna attempt those unless I know what it's going to do.
At this rate, my HTC Thunderbolt is pretty much a brick.
========
UPDATE:
I followed the method 1 steps from the link bastukee posted and its been working so far so good.
i am currently rooted with the old software, is there anyway to update the software but still stay rooted? I dont want to keep seeing these annoying updates.

@blenderben
Mine did EXACTLY the same thing and solution #1 fixed it, the option to clear the cache. I'm going to actually use a non-stock ROM from now on.

yeah i wanna swap to CM7, but isn't it still in alpha?

Verizon auto push update to phone.
How can we stop it?

Freezing - Not sure if random

So since about 2 days ago the phone just start freezing. Sometimes it just restarted randomly, but mainly freezing at least every 5 minutes. The power button alone wouldn't turn it off no matter how long I held it. Always have to use Pwr+Vol Down to reboot.
I put up with it because I've been busy, but finally tried wiping cache - no profit. Tried safe mode - no profit. Factory reset- negative profit. After the reset it just seems to restart a bit more often but in general it freezes less, making the timing seem even more random.
This happened when I first got it (used). It was restarting due to the fresh 7.0 update. So a factory reset fixed it and it was smooth sailing for like 3 months or something. I know there was a minor system update a few days ago but those dont usually call for a factory reset. I tried it anyway and it just didnt work. I had actually even tried uninstalling all the app updates from the night before it started happening. but safe mode couldn't even fix the problem so I guess that was moot.
Software version: G920VVRS4DQE1
Stock everything - I dont hack my daily drivers at all
Android 7.0
Mainly I'd like to know if Im alone. A fix would be great but I'm hoping it's not specific to my device. If it's a hardware issue I'm gonna give it a swift toss down the stairs and maybe deliver a nasty curb stomp to it right afterward.
Any advice?

I'm running into the same exact issue. Same build, and am running out of ideas.

Lathorus said:
I'm running into the same exact issue. Same build, and am running out of ideas.
Click to expand...
Click to collapse
Good to know its not just me. Did it start after a recent update for you also? That would give me hope that its not faulty hardware. Maybe just a bad update.

sawyerbenjamin said:
Good to know its not just me. Did it start after a recent update for you also? That would give me hope that its not faulty hardware. Maybe just a bad update.
Click to expand...
Click to collapse
Yes, it started right after I got a small update. I'm hoping a fix will come. (I'm on verizon).

Lathorus said:
Yes, it started right after I got a small update. I'm hoping a fix will come. (I'm on verizon).
Click to expand...
Click to collapse
Same for Verizon. I guess I'll just hold out, using a backup phone, until a new update hopefully fixes it.

Lathorus said:
Yes, it started right after I got a small update. I'm hoping a fix will come. (I'm on verizon).
Click to expand...
Click to collapse
Gonna go ahead and revive this. It seems to work fine when the sim card is out. I recommend you see if it's the same with you. I've charged it up before work multiple times before work days and come home from to see that it never restarted. I was able to test this using the fingerprint feature; it isn't asking me to use pattern like it does after boot.
No one else is chiming in but, since we're both on Verizon, I'm having a feeling that it's directly related to the SIM/carrier.