Related
I have no explanation of what has happened to my n7. It shut off by itself and just bootloops when I try to turn back on. I can get into recovery and I have a nandroid backup of a stock rom. Everytime I restore it restores system and then fails?? I flashed 3 different roms and all r flashed successfully but I get the same bootloops . I was using latest twrp and was get error I/o data / speedtest. Something else but I flashed cwm touch b4 I could jot down the errors . I figured it was twrp bug and didnt realize I wouldnt b able to flash back to twrp do to using gooim to write the image in the first place. I am desperate to find out what happened and I wont b near a pc for a few days. I have an unlocked rooted grouper version . I have read and searched b4 posting
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
it could be a hardware failure, maybe the mounted drive (emulated sd card) is corrupted and broken? the boot partition seems to be working
It sux cuz I wont have access to a pc for a few days
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
have you tried clearing the whole of /system /data /cache... everything except /sdcard then flash a new rom? maybe that'll clear some things up
Billchen0014 said:
have you tried clearing the whole of /system /data /cache... everything except /sdcard then flash a new rom? maybe that'll clear some things up
Click to expand...
Click to collapse
Yes I wiped system /cache/dalvik/ and factory reset I did them all like 5 times each and flashed a brand new rom. Its so weird
Nothing works. I am always prepared for atuff like this with multiple nandroids cwm/twrp but they both fail to restore
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
Back in a few months ago I'm faced with that problem once, tried everything like factory reset, format system/data/cache/sd, install new ROM and also tried to restore by nandroid backup (that used to work fine before that problem occur) but non of these solutions work.
Finally I've to use fastboot to flash it to 4.1.2 (to format and re-partition the device) and flash it back to 4.2.2 and then it work fine again even with many custom rom and kernel installed to my N7 very frequent and today it still work just fine.
why always me said:
Back in a few months ago I'm faced with that problem once, tried everything like factory reset, format system/data/cache/sd, install new ROM and also tried to restore by nandroid backup (that used to work fine before that problem occur) but non of these solutions work.
Finally I've to use fastboot to flash it to 4.1.2 (to format and re-partition the device) and flash it back to 4.2.2 and then it work fine again even with many custom rom and kernel installed to my N7 very frequent and today it still work just fine.
Click to expand...
Click to collapse
Thanks that is what im gonna have to do
Sent from my SGH-M919 using Xparent Skyblue Tapatalk 2
Thanks for the advice i got my pc back today and used wugs toolkit to flash factory image and it booted up thank god .
Sent from my Nexus 7 using Tapatalk 4 Beta
bbobarino said:
Thanks for the advice i got my pc back today and used wugs toolkit to flash factory image and it booted up thank god .
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
In the future, I'd refrain from flashing if you didn't have a computer on hand.
Sent from my Nexus 7 using XDA Premium HD app
peneoark said:
In the future, I'd refrain from flashing if you didn't have a computer on hand.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I couldnt agree more but thats the weird thing I didnt even flash anything for like a week b4 this happened thats why it was so bizzare to me. Still cant explain why it did that
Sent from my SGH-M919 using Tapatalk 4 Beta
bbobarino said:
I couldnt agree more but thats the weird thing I didnt even flash anything for like a week b4 this happened thats why it was so bizzare to me. Still cant explain why it did that
Sent from my SGH-M919 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Electronics can be wacky sometimes
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
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
Yesterday, I changed my shattered screen and I followed Le55on's tutorial. It worked for the rest of the day, and today, after class, I took it out and tried to unlock it, but it wouldn't respond. I rebooted it and tried everything, but it didn't work. Then I tried three fingers, and my input was recognized. But then I gave up and decided to wait until I got home. Then, when I took my phone out from my pocket at home, it worked perfectly. So far, the screen is still responsive. Could this just be a little problem that righted itself, or will I need to open it up? Thank you!
You could try apps from the play store that help calibration of the touch screen and touches as in amount of touches and see if that helps. Hopefully its just the new screen bedding in and should be OK.
Sent from my Nexus 4 using XDA Premium 4 mobile app
androidlosernoob said:
Yesterday, I changed my shattered screen and I followed Le55on's tutorial. It worked for the rest of the day, and today, after class, I took it out and tried to unlock it, but it wouldn't respond. I rebooted it and tried everything, but it didn't work. Then I tried three fingers, and my input was recognized. But then I gave up and decided to wait until I got home. Then, when I took my phone out from my pocket at home, it worked perfectly. So far, the screen is still responsive. Could this just be a little problem that righted itself, or will I need to open it up? Thank you!
Click to expand...
Click to collapse
bladebuddy said:
You could try apps from the play store that help calibration of the touch screen and touches as in amount of touches and see if that helps. Hopefully its just the new screen bedding in and should be OK.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=ru.tpyxa.android.multitouch
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
https://play.google.com/store/apps/details?id=ru.tpyxa.android.multitouch
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
bladebuddy said:
You could try apps from the play store that help calibration of the touch screen and touches as in amount of touches and see if that helps. Hopefully its just the new screen bedding in and should be OK.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did a calibration test, and it worked. Everything was fine. Just now, it stopped working again. I rebooted it twice and then it worked perfectly. Is this a software issue? What should I do?
androidlosernoob said:
I did a calibration test, and it worked. Everything was fine. Just now, it stopped working again. I rebooted it twice and then it worked perfectly. Is this a software issue? What should I do?
Click to expand...
Click to collapse
My guess would be to flash another rom and that might give you your answer. It might be as simple as the screen and digitizer separating from each other.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
My guess would be to flash another rom and that might give you your answer. It might be as simple as the screen and digitizer separating from each other.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Okay! So, just to go over the process again because I'm a complete amateur, Nandroid backup, Wipe, Flash new rom, flash new kernel, done.
You can flash the kernel afterwards, but you have the correct order.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
You can flash the kernel afterwards, but you have the correct order.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Okay, I'll make sure to report back!
Berrydroidcafe said:
You can flash the kernel afterwards, but you have the correct order.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Well, here I am being a stupid person. After 2 hours of painstakingly configurations of drivers, I can't flash PA. I wiped system, dalvik, factory reset, everything. Then when I flash PA 4.0 Beta, it fails. I don't know why this happens...
androidlosernoob said:
Well, here I am being a stupid person. After 2 hours of painstakingly configurations of drivers, I can't flash PA. I wiped system, dalvik, factory reset, everything. Then when I flash PA 4.0 Beta, it fails. I don't know why this happens...
Click to expand...
Click to collapse
What recovery are you using? How are you flashing it? (adb/toolkit)
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
What recovery are you using? How are you flashing it? (adb/toolkit)
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
So I ended up finding out that you have to upgrade the OS 4.2.2> 4.3>4.4>4.4.2 and now I have that done, and I've flashed CM 11 and it's working flawlessly. There's been no screen unresponsiveness so far and everything seems fine. Except now, I've flashed Matr1x 12.5 GPUOC and my color is getting distorted. Did I get the wrong file?
androidlosernoob said:
So I ended up finding out that you have to upgrade the OS 4.2.2> 4.3>4.4>4.4.2 and now I have that done, and I've flashed CM 11 and it's working flawlessly. There's been no screen unresponsiveness so far and everything seems fine. Except now, I've flashed Matr1x 12.5 GPUOC and my color is getting distorted. Did I get the wrong file?
Click to expand...
Click to collapse
I'm trying to figure out why you went through all of that when you could have flashed CM11 and been done with it.
I would say that the kernel is the problem. I would wipe everything, meaning a factory reset via the recovery and just flash CM11.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
I'm trying to figure out why you went through all of that when you could have flashed CM11 and been done with it.
I would say that the kernel is the problem. I would wipe everything, meaning a factory reset via the recovery and just flash CM11.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Wait what?! You don't have to?! I was on 4.2.2 originally, and I wiped CM10.2 before I flashed PA. It kept on failing, and I tried everything I could, but it wouldn't work. So I ended up updating the device step by step in order to get PA4. It ended up flashing correctly but my backup was gone, and now I need to start up from scratch. So Wipe>Flash CM11>Flash GAPPS> then Flash Matr1x?
androidlosernoob said:
Wait what?! You don't have to?! I was on 4.2.2 originally, and I wiped CM10.2 before I flashed PA. It kept on failing, and I tried everything I could, but it wouldn't work. So I ended up updating the device step by step in order to get PA4. It ended up flashing correctly but my backup was gone, and now I need to start up from scratch. So Wipe>Flash CM11>Flash GAPPS> then Flash Matr1x?
Click to expand...
Click to collapse
Yes, but don't flash the kernel until you get CM11 flashed.
1. Wipe
2. Flash CM11
3. Boot phone to make sure everything is good.
4. Flash gapps
5. Boot phone again and check things out.
6. Flash kernel.
If there are problems, it would be the kernel.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Yes, but don't flash the kernel until you get CM11 flashed.
1. Wipe
2. Flash CM11
3. Boot phone to make sure everything is good.
4. Flash gapps
5. Boot phone again and check things out.
6. Flash kernel.
If there are problems, it would be the kernel.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
I've done exactly that, but it's still the same problem.
androidlosernoob said:
I've done exactly that, but it's still the same problem.
Click to expand...
Click to collapse
The only other suggestion would be to try another rom and the problem is still there, it might be a hardware issue.
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
The only other suggestion would be to try another rom and the problem is still there, it might be a hardware issue.
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
So I've tried out Hells Core and everything is working well so far! Thank you so much for all your help!
androidlosernoob said:
So I've tried out Hells Core and everything is working well so far! Thank you so much for all your help!
Click to expand...
Click to collapse
No problem. Hope everything works for you from now on.
Sent from my Nexus 7 2013 using Tapatalk
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.