As the title says my nexus 4 just started rebooting out of no where, while one the phone, in an app, doesnt really seem to have a pateren.. I believe it started when she got the 4.4 update and now has 4.4.2. anyone els experience this issue? I think im going to try a factory reset to see if that helps. any input would be appreciated.
Ajxx16 said:
As the title says my nexus 4 just started rebooting out of no where, while one the phone, in an app, doesnt really seem to have a pateren.. I believe it started when she got the 4.4 update and now has 4.4.2. anyone els experience this issue? I think im going to try a factory reset to see if that helps. any input would be appreciated.
Click to expand...
Click to collapse
Are you rooted? If so and you have a custom recovery, I would do the factory reset via the recovery, that way you should still have your apps. If not, then you will lose everything and have to start from scratch.
Could be due to one of two things or a combination of things. One is a hardware issue, which I hope isn't the case. I would check the apps first before resetting, then do the reset. If it continues, try re-flashing the stock image. If after that and you're still having problems, going to 4.4, or 4.3 since it started with 4.4.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Are you rooted? If so and you have a custom recovery, I would do the factory reset via the recovery, that way you should still have your apps. If not, then you will lose everything and have to start from scratch.
Could be due to one of two things or a combination of things. One is a hardware issue, which I hope isn't the case. I would check the apps first before resetting, then do the reset. If it continues, try re-flashing the stock image. If after that and you're still having problems, going to 4.4, or 4.3 since it started with 4.4.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Its bone stock, ill have to take a look at her apps just to check whats up there but i doubt thats a culprit. I may be wrong but if I flash stock ota update it wont delete the user data and storage correct?
Ajxx16 said:
Its bone stock, ill have to take a look at her apps just to check whats up there but i doubt thats a culprit. I may be wrong but if I flash stock ota update it wont delete the user data and storage correct?
Click to expand...
Click to collapse
If you flash stock, it WILL wipe out everything unfortunately. If you at the least had an unlocked bootloader, you could have flashed the ota.zip and kept everything intact.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
If you flash stock, it WILL wipe out everything unfortunately. If you at the least had an unlocked bootloader, you could have flashed the ota.zip and kept everything intact.
Sent from my Nexus 7 (2013)[/QUOTE
And unlocking the BL wipes it as well correct?
Click to expand...
Click to collapse
Ajxx16 said:
Berrydroidcafe said:
If you flash stock, it WILL wipe out everything unfortunately. If you at the least had an unlocked bootloader, you could have flashed the ota.zip and kept everything intact.
Sent from my Nexus 7 (2013)[/QUOTE
And unlocking the BL wipes it as well correct?
Click to expand...
Click to collapse
Yep!
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Related
So I've been looking and I haven't found an answer to this problem
I have a 16 gig nexus 7 and I like to tinker with it. I rooted it quite quickly just after getting it, and I have loaded custom roms, ect. The problem arose when I saw Ubuntu for the Nexus 7! I just HAD to try it out! So I did, and it wasn't so great :/ I went back to Android and a couple days later I realized that somehow my Nexus 7 thinks it's 6 gigs instead of 16. I was wondering if it was something that went wrong with the partitions when I installed Ubuntu on it, and if there was any way I could possibly fix it.
Thanks for all the help
Have you tried flashing a stock image back on the device?
Sent from my SGH-I747 using Tapatalk 2
peneoark said:
Have you tried flashing a stock image back on the device?
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I believe I have. A little unsure though. I downloaded the stock 4.2 and flashed that onto it. Was that right or do I have to find the stock image that came with it out of the box (so 4.1.2 or close)?
Factory reset will fix the issue without installing the ROM I believe.
Sent from my Nexus 7 using Tapatalk HD
dottat said:
Factory reset will fix the issue without installing the ROM I believe.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Well I've tried it before... No harm in trying it again after I do a backup. Will update how this goes.
EDIT I just did a factory reset and no dice. It still believes it is 6 gigs.
RimSide said:
Well I've tried it before... No harm in trying it again after I do a backup. Will update how this goes.
EDIT I just did a factory reset and no dice. It still believes it is 6 gigs.
Click to expand...
Click to collapse
What i believe has happened is that your partition module has become corrupted.
So, you tried flashing stock, and tried factory reset?
Does it show up on your computer as 6 GB when you connect it?
I had the same thing happen. I just used wugs toolkit to flash back to stock, then rerooted from there. That is the easiest way I know of to fix. Becides download times it only takes like 15 minutes to flash to stock, then unlock and root and you are back on your way.
Shesh...the device been out for over a week now, im shock to see theres still not a official firmware image
immunityx said:
Shesh...the device been out for over a week now, im shock to see theres still not a official firmware image
Click to expand...
Click to collapse
I agree. I wanted the stock images to test if my device got a bad flash from the factory causing all of the multi touch and freezing issues. I ended up just exchanging at BB and have yet to upgrade to JSS15 in case that is the culprit.
Rod3 said:
I agree. I wanted the stock images to test if my device got a bad flash from the factory causing all of the multi touch and freezing issues. I ended up just exchanging at BB and have yet to upgrade to JSS15 in case that is the culprit.
Click to expand...
Click to collapse
There is no official one but there is an unofficial one, when the TWRP bug got me, it saved my system. It would still be soft-bricked waiting on Google otherwise.
I know right we need that incase something goes wrong and we can restore right to that i know we have ones on here but i want official
Sent from my Nexus 7 using Tapatalk 4
Hmmm nexus4 all over again
>^.^< Sent from meow HTC One which is like catnip to me atm
here's a flashable OTA image, is that not the same thing?
http://droidbasement.com/db-blog/?p=3120
Midnight_Rider said:
here's a flashable OTA image, is that not the same thing?
http://droidbasement.com/db-blog/?p=3120
Click to expand...
Click to collapse
they want a factory google released image
Midnight_Rider said:
here's a flashable OTA image, is that not the same thing?
http://droidbasement.com/db-blog/?p=3120
Click to expand...
Click to collapse
Nope. A factory image contains all the partitions, not just an update zip. Its used mainly to help devices that are completely broken (won't turn on), or people who want to unroot and go back to complete stock.
If it was there, it would be here: https://developers.google.com/android/nexus/images
That's what's keeping me from unlocking and rooting mine.
A
I want/need that as a backup..... just in case....
gotcha, i understand the diff
danvee said:
That's what's keeping me from unlocking and rooting mine.
A
I want/need that as a backup..... just in case....
Click to expand...
Click to collapse
It is extremely rare to have anything go wrong just unlocking the phone. You might as well go ahead and do it because eventually you will and it'll force a wipe data. Might as well do it now before you install too much stuff.
You can leave root and custom recovery until the images show up if you are concerned about borking your system.
sfhub said:
It is extremely rare to have anything go wrong just unlocking the phone. You might as well go ahead and do it because eventually you will and it'll force a wipe data. Might as well do it now before you install too much stuff.
You can leave root and custom recovery until the images show up if you are concerned about borking your system.
Click to expand...
Click to collapse
Not the unlocking. The rooting...
danvee said:
That's what's keeping me from unlocking and rooting mine.
A
I want/need that as a backup..... just in case....
Click to expand...
Click to collapse
danvee said:
Not the unlocking. The rooting...
Click to expand...
Click to collapse
this is what i did, after unlocking and rooting and installing TWRP go into recovery and make a nandroid backup and keep it safe off the device, keep it on the device, so if you need it you can restore it
That's what I'd be do once rooted, but it's the risk of the process failing without the factory image as a backup....
For example, rooting fails, no custom recovery flashed, OS hosed.....
I like having that safety net....
danvee said:
That's what I'd be do once rooted, but it's the risk of the process failing without the factory image as a backup....
For example, rooting fails, no custom recovery flashed, OS hosed.....
I like having that safety net....
Click to expand...
Click to collapse
oh i gotcha, but you have your steps out of order. first you unlock the bootloader which doesn't flash anything to your device. then you push the recovery image to your device from your PC using adb. yes this step could go horribly wrong, but if you have everything in place you should be ok. this step is very easy as well, not much to screw up and doesnt take any time at all, none of this does.
then once the recovery is installed, reboot your phone so you know everything comes up fine. then reboot into the recovery and flash SuperSU and voila! you have a rooted phone. boot back into the OS and run an app that requires root (Root Checker is a good one to use as a test) to make sure all is well
i understand your concern, but of all the android devices i have owned, the new nexus has been by far the easiest one of all to root and it is meant to be that way so developers can play with it and customize it and learn from it
plus there's this too
http://forum.xda-developers.com/showthread.php?t=2381582
Midnight_Rider said:
oh i gotcha, but you have your steps out of order. first you unlock the bootloader which doesn't flash anything to your device. then you push the recovery image to your device from your PC using adb. yes this step could go horribly wrong, but if you have everything in place you should be ok. this step is very easy as well, not much to screw up and doesnt take any time at all, none of this does.
then once the recovery is installed, reboot your phone so you know everything comes up fine. then reboot into the recovery and flash SuperSU and voila! you have a rooted phone. boot back into the OS and run an app that requires root (Root Checker is a good one to use as a test) to make sure all is well
i understand your concern, but of all the android devices i have owned, the new nexus has been by far the easiest one of all to root and it is meant to be that way so developers can play with it and customize it and learn from it
plus there's this too
http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
these are all wonderful points, but it doesn't change the fact that google should have released the image already
indianajonze said:
these are all wonderful points, but it doesn't change the fact that google should have released the image already
Click to expand...
Click to collapse
agreed, but im sure they are waiting to make sure there are no major bugs reported so they can fix it first, then release it. it will be out
That would mean yet another update, then.
Midnight_Rider said:
agreed, but im sure they are waiting to make sure there are no major bugs reported so they can fix it first, then release it. it will be out
Click to expand...
Click to collapse
Google has never waited before. The only thing that generally holds up posting factory images are licensing issues. They posted the 4.3 images for the Nexus 4, Nexus 7 (2012), and various Galaxy Nexus devices. There is no reason they didn't post the Nexus 7 images unless it is licensing related.
bozzykid said:
Google has never waited before. The only thing that generally holds up posting factory images are licensing issues. They posted the 4.3 images for the Nexus 4, Nexus 7 (2012), and various Galaxy Nexus devices. There is no reason they didn't post the Nexus 7 images unless it is licensing related.
Click to expand...
Click to collapse
good point
Hey guys,
I followed the OTA thread and used fastboot to install KRT16S. Everything works just fine, but, my device thinks it is the 8GB model and says only 6GB are available to me. Only my device is the 16GB model. any advice I can follow?
ramsayeg said:
Hey guys,
I followed the OTA thread and used fastboot to install KRT16S. Everything works just fine, but, my device thinks it is the 8GB model and says only 6GB are available to me. Only my device is the 16GB model. any advice I can follow?
Click to expand...
Click to collapse
probably from so many updates, maybe your phone is keeping a backup of all of them. T'would explain all this usage..
ramsayeg said:
Hey guys,
I followed the OTA thread and used fastboot to install KRT16S. Everything works just fine, but, my device thinks it is the 8GB model and says only 6GB are available to me. Only my device is the 16GB model. any advice I can follow?
Click to expand...
Click to collapse
On the Nexus Root Toolkit site, it says:
Perform a factory reset.
Settings > Backup & reset > Factory data reset.
This will make it display correctly again.
Click to expand...
Click to collapse
madcat1990 said:
probably from so many updates, maybe your phone is keeping a backup of all of them. T'would explain all this usage..
Click to expand...
Click to collapse
Well, I deleted the contents of the /sdcard during the updates, so that wouldn't be possible. Plus, it says my total available storage is 6GB, and not 13GB like it has before the update. The phone thinks it is the 8GB model!
CSX321 said:
On the Nexus Root Toolkit site, it says:
Click to expand...
Click to collapse
Oh man, having to install everything again. Thanks for the tip, will try.
Where did you download the factory image for the Nexus 4? I got one form Google and it seems that the files are name incorrectly. I get a message saying the bootloader is incorrect makoz20i (should be makoz30d). Just need a reliable factory image to flash my N4.
no need to wipe all data, just wipe cache on stock recovery.
I also have same problems. My Nexus 4 16Gb, after installing kitkat KRT16S via fastboot with the factory image download from google then become nexus 4 8Gb??? I don't know what happens ?
I also have this problem - 16gb N4 now showing as only 8gb. Any fixes out there (that don't involve wiping/factory reset)? Thanks
Try wiping cache first. If that doesn't work, factory reset is your only choice.
I just noticed mine is doing the same thing...says 5.67 for total space. I had issues when I tried to flash the update, so I ended up going back completely to stock. Then about 15 minutes later, I received the notification to update to 4.4 which I did. So I didn't even flash my update. It was the normal Nexus 4 update procedure.
Update: I did a factory reset and now my phone says it has 19.92 total space. So, the factory reset fixes it. Hopefully there will be a less drastic solution to this issue at some point.
I am having a similar problem after downloading 4.4 custom rom. Tried resetting n flashing other Roms and it stays the same. Missing a lot of space here, please help?
Sent from my Nexus 4 using XDA Premium 4 mobile app
calypso888 said:
I am having a similar problem after downloading 4.4 custom rom. Tried resetting n flashing other Roms and it stays the same. Missing a lot of space here, please help?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Have you seen this? http://forum.xda-developers.com/showthread.php?t=2033692
Sent from my Nexus 4
Factory reset worked for me on N4 and N7
Sent from my Nexus 7 using Tapatalk 4
I recently fixed an infamous bootloop i had by letting the battery die 100% (yeah I know it is bad), and then it booted. Well i went to flash a new rom and it never rebooted. I then went to flash stock from google. Still a bootloop. tried like 3 roms, still a loop. I then tried the killing my battery thing. Still a loop. Please, i know the phone isn't hard bricked, is there anything else i can do to boot it other than just flashing stock and factory resetting. Thanks.
Another thing, when i try to flash 4.2.2 the phone doesn't go to the boot logo.
Anybody? I need to fix this phone soon.
Wrong thread sorry
YFBanana said:
Anybody? I need to fix this phone soon.
Click to expand...
Click to collapse
Fastboot flash the factory image. Then boot into the stock recovery and do a factory reset.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Fastboot flash the factory image. Then boot into the stock recovery and do a factory reset.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
unfortunately that doesn't work, i have tried it many times.
YFBanana said:
unfortunately that doesn't work, i have tried it many times.
Click to expand...
Click to collapse
Then you have an issue with your device. What happens if you lock the bootloader and then reboot? Does it stay locked or is it still unlocked?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Then you have an issue with your device. What happens if you lock the bootloader and then reboot? Does it stay locked or is it still unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It stays locked. I am guessing thats a good thing?
YFBanana said:
It stays locked. I am guessing thats a good thing?
Click to expand...
Click to collapse
Yep, if it didn't your emmc flash memory would be bad. I'd try re-downloading the factory image and trying again. Are you using the flash-all.bat to flash? You might try flashing all the components separately and see if any of them fail.
Sent from my Nexus 5 using XDA Free mobile app
You flashed stock firmware and it didn't work? What did it do when you flashed it?
Sent from my Moto G running Carbon ROM 4.4.4
jd1639 said:
Yep, if it didn't your emmc flash memory would be bad. I'd try re-downloading the factory image and trying again. Are you using the flash-all.bat to flash? You might try flashing all the components separately and see if any of them fail.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
None of the flashes failed. I have tried redownloading and i have also checked the md5's, so i dont think that would be it. I have also tried reformatting through twrp, and then flashing stock. Still nothing.
flashing 4.4.4 separately got me on the starting apps step, but that seems to be the place where it gets stuck.
I need to decide if i wanna take another month trying to fix the nexus 4 or just get the nexus 5. Nothing is working and i think i should just leave it now. But at the same time, i just wanna fix it so i don't have to spend money on a new phone. I have run out of things to try and revive the phone so i don't know what to do anymore.
YFBanana said:
I need to decide if i wanna take another month trying to fix the nexus 4 or just get the nexus 5. Nothing is working and i think i should just leave it now. But at the same time, i just wanna fix it so i don't have to spend money on a new phone. I have run out of things to try and revive the phone so i don't know what to do anymore.
Click to expand...
Click to collapse
so now you can boot to 4.4.4 ROM but your phone stuck at the "Starting apps" box rite?
groovepeppy said:
so now you can boot to the ROM? but never pass the "Starting apps"?
Click to expand...
Click to collapse
I think it was just the order i flashed the img files that made it go to that point, but i am pretty sure starting apps is where it gets stuck every time.
YFBanana said:
I think it was just the order i flashed the img files that made it go to that point, but i am pretty sure starting apps is where it gets stuck every time.
Click to expand...
Click to collapse
You can fastboot your phone i believe, you should try [HOW-TO] How to flash a factory image / return to stock / unlock / root #
Start from point C
I hope you haven't tried it yet
groovepeppy said:
You can fastboot your phone i believe, you should try [HOW-TO] How to flash a factory image / return to stock / unlock / root #
Start from point C
I hope you haven't tried it yet
Click to expand...
Click to collapse
I have tried it. Still no boot.
YFBanana said:
I have tried it. Still no boot.
Click to expand...
Click to collapse
there's must be a way cause you can boot on 4.4.4 but unfortunately i'm not that good in these kind of problems
but i hope you can find the cure soon
You can obviously get into flashboot, have you tried booting the latest twrp, wiping /system /data /cache and sideloading something different, like Paranoid Android?
Bootloop fix
First thing is that you have use Wug's Tool and flash the 4.3 stock image. In the Wug's tool select the option 'SOFT BRICK or BOOTLOOP' option and then flash the stock image in the fastboot mode. Definitely, I hope the phone will launch without any problem. The same problem I had faced with my nexus 4 and I flash the 4.3 stock image with the help of Wug's tool. Try it I hope it will fix the problem.
I've noticed my 6P has started to randomly reboot every day or so since the latest update from Verizon (last week). Anyone else experiencing this?
Sent from my Nexus 6P using Tapatalk
jpcalhoun said:
I've noticed my 6P has started to randomly reboot every day or so since the latest update from Verizon (last week). Anyone else experiencing this?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Factory reset will most likely resolve your problem.
therock3181 said:
Factory reset will most likely resolve your problem.
Click to expand...
Click to collapse
Thanks.
Sent from my Nexus 6P using Tapatalk
jpcalhoun said:
I've noticed my 6P has started to randomly reboot every day or so since the latest update from Verizon (last week). Anyone else experiencing this?
Click to expand...
Click to collapse
No reboots at all, but I would try wiping the cache partition from recovery first before resetting. If you have TWRP installed wipe the dalvik cache too. This will often clear up minor glitches and problems. The first boot will take longer than normal while it rebuilds. If that doesn't work, a factory reset may be in order, but I would strongly recommend unlocking your bootloader at the same time. If you haven't done so already, it will factory reset the device upon unlocking. You can get more information and a how-to in the tutorial..
If you're rooted, you could look in /proc/last_kmsg to get some context on the fault.
v12xke said:
No reboots at all, but I would try wiping the cache partition from recovery first before resetting. If you have TWRP installed wipe the dalvik cache too. This will often clear up minor glitches and problems. The first boot will take longer than normal while it rebuilds. If that doesn't work, a factory reset may be in order, but I would strongly recommend unlocking your bootloader at the same time. If you haven't done so already, it will factory reset the device upon unlocking. You can get more information and a how-to in the tutorial..
Click to expand...
Click to collapse
Thanks, I'm unlocked, just not rooted. I'll try wiping cache.
Sent from my Nexus 6P using Tapatalk
rchtk said:
If you're rooted, you could look in /proc/last_kmsg to get some context on the fault.
Click to expand...
Click to collapse
Not rooted but thanks for the help.
Sent from my Nexus 6P using Tapatalk
That's where root helps. To have a chance to know what's going on. The log is there, you just don't have the permission to open it.
rchtk said:
That's where root helps. To have a chance to know what's going on. The log is there, you just don't have the permission to open it.
Click to expand...
Click to collapse
I've had developer edition phones for the past 10 years... bootloader unlocked, rooted, custom Roman etc. I decide to go pure Android, no root and see if the Android experience is the same. I do like taking updates over the air w/o the hassle of having to go back to stock though. Thanks for the help.
Sent from my Nexus 6P using Tapatalk
jpcalhoun said:
I've had developer edition phones for the past 10 years... bootloader unlocked, rooted, custom Roman etc. I decide to go pure Android, no root and see if the Android experience is the same. I do like taking updates over the air w/o the hassle of having to go back to stock though. Thanks for the help.
Click to expand...
Click to collapse
Yeah same here. Been doing the same for too long. Now on Nexus I'm happy with stock. There's just root that I keep exactly for this reason. But yeah I do have to take the laptop to do updates (FlashFire has failed a few times).
Understood. Hope you solve your issue with factory reset or maybe flashing a previous radio.
BTW today I reverted from 7.1.2b to 7.1.1 and began having radio problems (which I didn't have before on 7.1.1) and strangely factory reset did solve the problem.
rchtk said:
Yeah same here. Been doing the same for too long. Now on Nexus I'm happy with stock. There's just root that I keep exactly for this reason. But yeah I do have to take the laptop to do updates (FlashFire has failed a few times).
Understood. Hope you solve your issue with factory reset or maybe flashing a previous radio.
BTW today I reverted from 7.1.2b to 7.1.1 and began having radio problems (which I didn't have before on 7.1.1) and strangely factory reset did solve the problem.
Click to expand...
Click to collapse
I guess I'll do a factory reset ?
Sent from my Nexus 6P using Tapatalk