[Q] Semi-Brick? - myTouch 4G Q&A, Help & Troubleshooting

Okay, today I was about to flash a new rom so I attempted to wipe, but I got an error that the phone could not mount the cache (and later couldn't mount data). It says "E:Can't mount CACHE:recovery/command" on the next line "E:Can't mount CACHE:recovery/log" and the next "E:Can't open CACHE:recovery/log". So I have tried reflashing recovery to fix it and it did not work. I cannot flash any rom without an error or restore my nandroid backups. I am in the process of trying to restore the nandroid backups throught fastboot. Can anyone give me any help on this?
SOLUTION: blancoisgod recommends formatting the cache partition to fix this problem

Did you pull the battery and retry?

Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow

toby4059 said:
Yep. Actually, the phone wont even turn on anymore. I will just have to return it to tmobile tomorrow
Click to expand...
Click to collapse
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!

No man dont turn it into tmobile. Now everyone is gonna ride you because you broke it and your going to return it because of what you have done,not the manufacturer.
Go ahead and turn it in, but please read around a bit before you do this again.

CBConsultation said:
This is exactly why manufacturers don't want people rooting and messing with their phones.
So because of your stupidity and lack of foresight you're now going to return your phone?! That's laughable.
Now T-Mobile and HTC have to pick up the bill for someone else's ignorance.
Note to self....remember your name and never help you!
Click to expand...
Click to collapse
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.

toby4059 said:
Your right it is my fault; although, I am not sure what I did wrong. I am not a complete idiot and have been doing this stuff for a while. I did everything by the instructions and this happened. I actually saw this happen to someone in the G2 forum but no one found a solution. I see how returning the phone would be wrong but what are my options? I am only 15, no income, so what could I do. If I had income of course I would just pay for a new phone. I hope I am not coming off as a dumb juvenile crook, I apologize.
Click to expand...
Click to collapse
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?

CBConsultation said:
Did you make a backup image? If so you could just flash your recovery image and be golden. If not, then your options are very limited.
I was not trying to hurt or insult your feelings but we constantly see people who 'think' they know what they're doing with these same issues all day every day.
My advice is limited as well at this point because I'm not sure exactly what you've done or precautions you had in place for this.
Can you even boot into the OS at all? Do a factory reset?
Click to expand...
Click to collapse
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.

toby4059 said:
I cannot turn the phone on what so ever. I was flashing my backup through fastboot then tried to reboot and now it will no longer turn on. I fastboot erased recovery, system, userdata, and boot and restored them from the nandroid backup I had taken prior to the error. The day prior I had rooted successfully and flashed the desire z port. I decided I wanted to try the HD port so I wiped and flashed the rom. When I rebooted it got to the lockscreen and it showed some graphical corruption then began to boot loop. I turned it off and went to recovery and thats when the CACHE errors started. Was I supposed to wipe the dav cache because I am pretty sure I did. I just want to find out what I did wrong so it won't happen to me or anyone else.
Click to expand...
Click to collapse
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.

CBConsultation said:
Between ROM's, you said you wiped. What did you wipe? Cache? Dalvik? Partition?
You said you're not too sure so I am going to assume you either didn't wipe something you should have or you did wipe something you shouldn't have.
Try this. Remove the battery for 10 minutes. When the battery is removed, hold the power button for about 2 minutes. This will drain any residual current left on the board. After the 10 minutes are up, try reinserting the battery, hold the volume- button and try to power on. We'll see if you can manage to boot into recovery at this point.
Click to expand...
Click to collapse
Okay I will give that a try thanks.

I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.

blancoisgod said:
I had the same error just right now man
What you want to do is format the cache partition when you get the thing booted.
Click to expand...
Click to collapse
Did you do that and did it fix? I did that through adb and thats when it stopped booting, although I think the boot issue is unrelated to my current problem.

i did it via clockwork

Alright, I will try this if I can ever get my phone started again.

Related

phone not going to desktop

How long after reboot does it take for everything to loadup, because right now my phone keeps going back and forth between htc and sprint splash screens. Did I do something wrong, or am I being impatiant.
how long has it been so far?
Have you used A2sd before?
**EDIT**
What ROM are you flashing?
Did you nandroid backup?
I can further assist you with these questions answered.
I'd say about 30 mins and a I used the flashrec process.
yes i did do a nand and flashed damage 2.08
rbarr001 said:
I'd say about 30 mins and a I used the flashrec process.
Click to expand...
Click to collapse
Okay nothing to flash takes 30 minutes. You are stuck in a boot loop.
Steps to take:
Remove battery
go to recovery (down volume + end call button at same time and hold them,
when you get word come up hit home)
Now that you are in recovery go to wipe
click "Restore Default" (it will say something like that)
Reflash the ROM
Let me know it this works.
**STEPS TO TAKE IF THIS STILL DOESN'T WORK**
Re download Damage Control
then place back on SD Card.
Flash that one..
Note: you are in no way bricked so don't worry.
Every thing can be fixed with the right assistance.
Restore Default" (it will say something like that)
wipe data/factory reset is that what you ment for wipe?
rbarr001 said:
Restore Default" (it will say something like that)
wipe data/factory reset is that what you ment for wipe?
Click to expand...
Click to collapse
Yes and if you have ever used Apps 2 SD then you need to wipe "SD:ext partition" And considering DC uses that you need to wipe it.
then reflash it
EDIT: I dont want to confuse you so here it is in a more professional manner.
Wipe: data/factory reset
Wipe: SD:ext partition
reflash DC, then reboot phone.
----------------------------------------------------
If all fails Download DC again here
http://dl.damagedroms.com/2.0/DamageControlv2.08.1.zip
Then you should know the steps from there
So how long should it take to load that flash?
10 Minutes at most.
but hold off a couple minutes after that just in case. Also it should do HTC the HTC with the green brilliant then back to HTC if it goes back and forth like before you are in a boot loop.
Also you can tell if its in a boot loop because the Htc will kinda flash.. That means that it is reloading the boot which in turn tells you the phone wont boot up.
Never mind it just came up thank you very much the info you gave me was very appreciated. I knew i didn't brick my phone because it was doing something Ijust didn't know how to fix that issue. So again THANK YOU VERY MUCH!!!!!!!!!!!!!!!
rbarr001 said:
Never mind it just came up thank you very much the info you gave me was very appreciated. I knew i didn't brick my phone because it was doing something Ijust didn't know how to fix that issue. So again THANK YOU VERY MUCH!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
No problem! I live for helping people with there problems! I'm just happy you put it in the right selection.
Thanks, Devin

[Q] Stuck on the X logo, pls help...

Guys, its my first time to try to do some modding on Android and unfortunately Im stuck with a problem.
I did a good install with drivers, unlocked it successfully then installed TWRP 2.5 mako. after installing TWRP, I locked my phone again. Then I went to TWRP recovery then made a backup. After backup was complete, I was to reboot but was prompted something like "my device seemed not to be rooted. Do you like to install SU?" But I choose "dot not install" instead. Then it rebooted. Then the Google logo showed up longer than usual, then the X logo and was stuck on it from there. I waited till morning thinkin the phone might be configuring itself for the first time after all the things I have done but to my surprise, when I got up this morning, still on the X logo! I then tried to reset by pressing the power button for some seconds. It rebooted but same thing happens, google logo showed up for a longer time than usual then stuck again on the X logo. Then I tried fastboot, it did went to fastboot. Tried to reset bootloader, tried using TWRP reset system and reboot but still no success.
What do you think happenede and what did I do wrong? What should I do now to fix this.
Im really nervous now thinking I might have bricked my phone. Im a newbie so I really have no idea..
Hope you guys could help. Thanks!
Try clearing cache in twrp if that doesn't work flash the stock recovery and clear cache from there.
Sent from my Xoom using Tapatalk 4 Beta
El Daddy said:
Try clearing cache in twrp if that doesn't work flash the stock recovery and clear cache from there.
Sent from my Xoom using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks for the reply. You mean using "Wipe" in twrp right? After choosing wipe, i was prompted with 2 button options and a swipe option. 1 button was "advance wipe", the other was "format data" and the swipe option was "swipe to factory reset" what should I use? It says "factory reset wipes data, cache and dalvik (not including internal storage). Most of the time this is the only wipe that you need." You mentioned to try to clear cache, do you mean to say the data and dalvic as well? If so then should I choose the swip option which is "factory reset"?
Thanks again..
Nope just the cache. This phone sometimes has issues when wiping data/cache from the bootloader. (Which is what happens when you unlock the bootloader) The way to fix the bootloop problem is to wipe cache using the stock recovery.
Sent from my Nexus 4 using Tapatalk 4 Beta
vinz_bangiz said:
thanks for the reply. You mean using "Wipe" in twrp right? After choosing wipe, i was prompted with 2 button options and a swipe option. 1 button was "advance wipe", the other was "format data" and the swipe option was "swipe to factory reset" what should I use? It says "factory reset wipes data, cache and dalvik (not including internal storage). Most of the time this is the only wipe that you need." You mentioned to try to clear cache, do you mean to say the data and dalvic as well? If so then should I choose the swip option which is "factory reset"?
Thanks again..
Click to expand...
Click to collapse
Try factory reset first if that doesn't work you may have to sideload a ROM onto it. The same thing happened to me a couple of times. Sometimes a factory reset worked but most of the time I ended up sideloading.
El Daddy said:
Nope just the cache. This phone sometimes has issues when wiping data/cache from the bootloader. (Which is what happens when you unlock the bootloader) The way to fix the bootloop problem is to wipe cache using the stock recovery.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
so just to clear, i would not try anymore to clear cache via twrp or should i try it first before flashing stock recovery and clearing it from there? To be honest, im quite careful now in every move ill make coz Im afraid i might make matters worst.
Pls advice. thanks for your patience.
by the way, in case I would really need to flash stock rom, how to do it and where to get right stock recovery?
Thanks again!
All the info to flash recovery and resources are here: http://forum.xda-developers.com/showthread.php?t=2010312
Basically, download the stock image. Extract the folder down til you see the recovery.img.
Then using fastboot type the command:
fastboot flash recovery recovery.img
Then boot into recovery and clear cache.
Sent from my Nexus 4 using Tapatalk 4 Beta
El Daddy said:
All the info to flash recovery and resources are here: http://forum.xda-developers.com/showthread.php?t=2010312
Basically, download the stock image. Extract the folder down til you see the recovery.img.
Then using fastboot type the command:
fastboot flash recovery recovery.img
Then boot into recovery and clear cache.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
oh ok. I understand now. Sorry, its my first time so im not that familiar yet on how things go. I did a lot of reading and browsing as well but xda sure is very overwhelming in information..
P41ll37 is suggesting sideload which I also am not yet familiar with. i tried to search it but most of it led to using a toolkit. I mentioned in another post that I made that I wanted to learn instead of jsut being able to fix my problems. Could you advice me as well or lead me to the right link to know how to do this.
Thanks!
Guys! before trying anything else, I tried to clear cache using TWRP and choosing advance then marked the delvic cache and cache then restarted system, was asked if I wanted to installed SU, this time I choose yes, it rebooted by itself, but still nothing happened. same stuck on X logo problem.
But then, I tried wipe again in TWRP this time choosing factory reset, then restarted system again, google logo did stay a longer but not as long as before, then X logo appeared and stayed there like forever but after a minute or so.. FINALLY! it went to the Welcome screen asking for what language I should use.
So i guess this means it is fixed already?
Also, since I choose to install SU a while ago, does this mean my phone is already rooted as well? How would I know? Well, maybe installing a root app like titanium backup should tell right?
If so, then looks like I have advanced already on my step by step learning to mod my phone. I was only in the unlocking and custom recovery part last night. Tonight was supposed to be rooting and putting custom rom but I was still trying to learn thru our forum guides.
I wana thank you guys for your time, kind help and suggestions. This was my first experience in modding and right away I was faced with a problem to be solved. This is good anyway as a learning experience.
One last thing, could you guys tell what really happend, how I went into this kind of problem or what caused it? As I mentioned, I was noping not only to mod or fix my phone but rather really learn on how to do or fix things. Like a difference between a toolkit and manually doing it. Right?
Thanks again guys!
vinz_bangiz said:
Guys! before trying anything else, I tried to clear cache using TWRP and choosing advance then marked the delvic cache and cache then restarted system, was asked if I wanted to installed SU, this time I choose yes, it rebooted by itself, but still nothing happened. same stuck on X logo problem.
But then, I tried wipe again in TWRP this time choosing factory reset, then restarted system again, google logo did stay a longer but not as long as before, then X logo appeared and stayed there like forever but after a minute or so.. FINALLY! it went to the Welcome screen asking for what language I should use.
So i guess this means it is fixed already?
Also, since I choose to install SU a while ago, does this mean my phone is already rooted as well? How would I know? Well, maybe installing a root app like titanium backup should tell right?
If so, then looks like I have advanced already on my step by step learning to mod my phone. I was only in the unlocking and custom recovery part last night. Tonight was supposed to be rooting and putting custom rom but I was still trying to learn thru our forum guides.
I wana thank you guys for your time, kind help and suggestions. This was my first experience in modding and right away I was faced with a problem to be solved. This is good anyway as a learning experience.
One last thing, could you guys tell what really happend, how I went into this kind of problem or what caused it? As I mentioned, I was noping not only to mod or fix my phone but rather really learn on how to do or fix things. Like a difference between a toolkit and manually doing it. Right?
Thanks again guys!
Click to expand...
Click to collapse
basically whenever you flash a factory image (and perhaps even some custom ROMS) you have to do a factory reset for really two reasons. The first reason is to get it out of bootloop. For some reason whenever the phone is flashed it will go on endless loop until you boot into recovery and factory reset. Also, you will need to check your storage after you flash. The phone has a tendency to lose half its memory after a flash. Check storage and if at half memory do another factory wipe and you should be good to go.
The easiest way I do it is to simply reboot the phone after flashing the files, I then allow the phone to reboot and get stuck on the bootloop. I then hard shut the phone off by holding down power. Once shut down boot into fastboot and then fastboot boot TWRP recovery where I then wipe the phone. After it reboots it will stick on the X logo for a few minutes and get to the welcome screen. From there log in and get it set up again.
Also, this is where you should check storage. I notice that more often than not mine still is only half storage (despite my TWRP wipe), so I use the phone to factory reset and then when it reboots the phone has full storage again.
Im sure there is probably someone out there with a better system but that is how I do it.
thos25 said:
basically whenever you flash a factory image (and perhaps even some custom ROMS) you have to do a factory reset for really two reasons. The first reason is to get it out of bootloop. For some reason whenever the phone is flashed it will go on endless loop until you boot into recovery and factory reset. Also, you will need to check your storage after you flash. The phone has a tendency to lose half its memory after a flash. Check storage and if at half memory do another factory wipe and you should be good to go.
The easiest way I do it is to simply reboot the phone after flashing the files, I then allow the phone to reboot and get stuck on the bootloop. I then hard shut the phone off by holding down power. Once shut down boot into fastboot and then fastboot boot TWRP recovery where I then wipe the phone. After it reboots it will stick on the X logo for a few minutes and get to the welcome screen. From there log in and get it set up again.
Also, this is where you should check storage. I notice that more often than not mine still is only half storage (despite my TWRP wipe), so I use the phone to factory reset and then when it reboots the phone has full storage again.
Im sure there is probably someone out there with a better system but that is how I do it.
Click to expand...
Click to collapse
Thanks for the reply. really very informative!
The easiest way I do it is to simply reboot the phone after flashing the files, I then allow the phone to reboot and get stuck on the bootloop. I then hard shut the phone off by holding down power. Once shut down boot into fastboot and then fastboot boot TWRP recovery where I then wipe the phone. After it reboots it will stick on the X logo for a few minutes and get to the welcome screen. From there log in and get it set up again.
Click to expand...
Click to collapse
Actually, this is exactly what I did and the one that solved my problem.
Also, this is where you should check storage. I notice that more often than not mine still is only half storage (despite my TWRP wipe), so I use the phone to factory reset and then when it reboots the phone has full storage again.
Click to expand...
Click to collapse
About this, are you referring to the remaining free storage or that actual usable storage of the phone. To my knowledge, a new 16gb nex4 would actually give you about 12+gb of free usuable space. Do you mean I should observe if this has dropped to about 6gb? or are you reffering to for example I have 5gb remaining free space before flashing and rebooting then after this I should observe if the "remaining free" space is now only around 2.5gb after rebooting it?
Looking forward to your clarification.. thanks again!

[Q] Help! Spontaneously Bricked My Stock Nexus 4

Ok my battery was draining at a faster rate than normal so i figured I'd reboot my phone. Once I shut down my phone and hit the power button it boot into fastboot mode. I am literally the most basic Nexus 4 user meaning, I've never rooted, unlocked, flashed or done anything to my phone. I simply just don't know how to do any of this stuff so it's not like I was tinkering with anything.
I searched online and I went into recovery mode and tried to reset the phone and wipe the partition and it just reboots to the fastboot mode. I honestly have no clue what went wrong. Again, I know nothing about root and stuff but there must be a solution right or am I the first person to ever brick their completely stock phone by trying to restart it? I figure some of the awesome people on here what know what to do or to simplify some steps to fixing this. Thanks in advance.
Sounds like your volume down key might be stuck (as holding that when you power on is how you get to fastboot).
If it's not that then maybe you should try downloading the factory image from here: https://developers.google.com/android/nexus/images and letting that install.
I don't think the button is stuck.
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
After restoring a factory image, it is recommended that you lock the bootloader, for security reasons.
Click to expand...
Click to collapse
Rusty! said:
Sounds like your volume down key might be stuck (as holding that when you power on is how you get to fastboot).
If it's not that then maybe you should try downloading the factory image from here: https://developers.google.com/android/nexus/images and letting that install.
Click to expand...
Click to collapse
Definitely not the volume down key. I'm able to navigate with volume rocker in fastboot.
Alex_Dreyk said:
I don't think the button is stuck.
Click to expand...
Click to collapse
are u able to get to the bootloader and recovery
One3OneKing said:
Definitely not the volume down key. I'm able to navigate with volume rocker in fastboot.
Click to expand...
Click to collapse
I picked an instrucktion form the link below.
As you have already wiped it do as in instruction
faddyie said:
are u able to get to the bootloader and recovery
Click to expand...
Click to collapse
yes, I can get to recovery. can i get to the bootloader?how would i get there, no clue. lol
Bootloader = fastboot
Try the factory image flash.
Rusty! said:
Bootloader = fastboot
Try the factory image flash.
Click to expand...
Click to collapse
I kind of have an idea of how to do that but a link to a set of instructions would be great. I've looked but most people have rooted and installed computer programs so I didnt know what exactly I would need to do in my completely stock scenario.
One3OneKing said:
I kind of have an idea of how to do that but a link to a set of instructions would be great. I've looked but most people have rooted and installed computer programs so I didnt know what exactly I would need to do in my completely stock scenario.
Click to expand...
Click to collapse
Dear if you have not rooted it. your stock rom has not gone any where...
Goto recovery and then press volume up key and power button. keep holding for like 10 secs and u will be get into the system. However, check that your volume down key is not pressed
faddyie said:
Dear if you have not rooted it. your stock rom has not gone any where...
Goto recovery and then press volume up key and power button. keep holding for like 10 secs and u will be get into the system. However, check that your volume down key is not pressed
Click to expand...
Click to collapse
No luck. This is crazy, I literally don't know what happened...:crying:
Have u downloaded the sender image file as described in previous posts
Sent from my Nexus 4
One3OneKing said:
Ok my battery was draining at a faster rate than normal so i figured I'd reboot my phone. Once I shut down my phone and hit the power button it boot into fastboot mode. I am literally the most basic Nexus 4 user meaning, I've never rooted, unlocked, flashed or done anything to my phone. I simply just don't know how to do any of this stuff so it's not like I was tinkering with anything.
I searched online and I went into recovery mode and tried to reset the phone and wipe the partition and it just reboots to the fastboot mode. I honestly have no clue what went wrong. Again, I know nothing about root and stuff but there must be a solution right or am I the first person to ever brick their completely stock phone by trying to restart it? I figure some of the awesome people on here what know what to do or to simplify some steps to fixing this. Thanks in advance.
Click to expand...
Click to collapse
Being that you haven't unlocked or rooted the phone its most likely a hardware problem. If you bought it from Google RMA
From my BLACKED OUT N4
Before RMA'ing try the factory image. You don't need instructions, you just run a .bat file while in fastboot. What have you git to lose?
if you wiped your partitions, then you dont have a rom on your phone. flashing the factory img via fastboot would fix that.
simms22 said:
if you wiped your partitions, then you dont have a rom on your phone. flashing the factory img via fastboot would fix that.
Click to expand...
Click to collapse
You can't wipe /system from stock recovery, so he didn't do that.
EvoXOhio said:
You can't wipe /system from stock recovery, so he didn't do that.
Click to expand...
Click to collapse
i havent seen the stock recovery in a loooooooooong time, just going by what he wrote in his post :angel:
heres his quote, and thats what happens exactly when you dont have a rom stalled on the device..
I searched online and I went into recovery mode and tried to reset the phone and wipe the partition and it just reboots to the fastboot mode
Click to expand...
Click to collapse
simms22 said:
i havent seen the stock recovery in a loooooooooong time, just going by what he wrote in his post :angel:
heres his quote, and thats what happens exactly when you dont have a rom stalled on the device..
Click to expand...
Click to collapse
I'm guessing he wiped data and/or cache. If he truly is stock like he says then he didn't wipe his /system partition.
My phone got messed up once and I couldn't make or restore nandroids nor boot past the CM boot image, and it ended up being because my /data partition got corrupted. No idea how. I had to flash stock Google images to get it to boot. it happened during normal use of the phone.
EvoXOhio said:
I'm guessing he wiped data and/or cache. If he truly is stock like he says then he didn't wipe his /system partition.
My phone got messed up once and I couldn't make or restore nandroids nor boot past the CM boot image, and it ended up being because my /data partition got corrupted. No idea how. I had to flash stock Google images to get it to boot. it happened during normal use of the phone.
Click to expand...
Click to collapse
yea, if had my data partition get corrupted too, wouldnt finish booting. flashing the stock img fixed it quick. but it was my own fault.. bennchmarking at 1890mhz with fsync turned off
I ended up just taking advantage of my warranty and I'll get a new one. Thanks to everyone for the suggestions and tips. I'm still trying to figure out why simply turning off the phone to restart it caused this to happen. It makes no sense.

[Q] Freezing, rebooting, and can't flash stock rom (reverts to previous state)

Okay, so I feel like I've looked everywhere and tried everything for this problem with my Nexus 7. The closest thing I found was this:
(Google: Nexus 7 2012 rebooting reverts back to previous state)(I can't post outside links as I am a new member)
and there was no followup reply, and the thread was closed.
Here's my problem (I want to be very detailed in case I missed something):
I've had Cyanogenmod 11 on my Nexus 7 for a long time (I think I started with M1 release). I recently installed the M7 release after previous nightly and it was working so smooth that I had finally decided there was no need to install nighties anymore. Everything was going fine until the night after when I noticed it kept rebooting, so I reverted it back to the nightly I had before (June 11th?) because I assumed it was probably something bad with the update. Except it did the same thing, rebooting after a couple minutes, which is weird because it never did that with this nightly. There was never enough time to download the nightlies before it reboots so I tried downloading them on my laptop and then just transferring them to my nexus via usb. I put it in the cmupdate folder so that I could quickly go to settings and press install (as it can see the update from there). It rebooted to install, but it went into cwm with what appears that nothing happened, and I usually never see cwm when updating this way. So I figured, while I'm here, I could just "install zip" and find that zip I just transferred and install, right? Nope. The zip mysteriously vanished, yet the other two updates were still there (M7 and the previous nightly). So I just rebooted just to try the process again, maybe the file transfer didn't work. Same thing happened. So I went to cwm and tried wiping cache, nothing. Wiped dalvik cache, nothing. So I went and did it, wiped data/factory reset, that did NOTHING, as in I rebooted and everything was still there.
So I got to the point where I just wanted to see if I could just revert back to stock so I have a place to start from, maybe contemplate on just staying there for a while where there shouldn't be problems. So I got that all set up with fastboot, got the latest 4.4.3 image, unarchived until I could get to the flashall.bat I ran that and it was successful. Okay now I can just boot into that, right? Suddenly I see the cyanogenmod boot graphic. What happened? Even all of my apps are still there. Still freezing and rebooting.
I tried reverting to stock manually by erasing then formating everything that I can, flashed bootloader (grouper 4.23), flashed zip, locked bootloader, unlocked bootloader (trying to erase as much as I can). This did nothing, still cyanogenmod. I tried a third time while rebooting to bootloader with each step. Nothing. I tried doing a factory reset within cyanogenmod, but when I press the "erase everything" button it doesn't lead anywhere, so I could never get that to start the process. I also tried doing the erasing and formatting from cwm (which isn't being overwritten, as it seems, by all the attempts at flashing stock?), nothing.
I was curious. I uninstalled Netflix because it was right there in my dock. Then I rebooted myself. When it came back up, Netflix was still there. I tried various things, also going back to locking the bootloader and rebooting the bootloader, it still said it was unlocked. So I came to the conclusion that literally nothing was being written or committed to the sdcard no matter what I do.
I did some more research and found that article up top. So I tried uninstalling some apps because it said it may have something to do with a third-party app misbehaving (seems a bit extreme, I'll do it anyways), but there's never enough time to erase everything before it reboots. It also said to try to get it into safemode. I think I might have gotten there once but it still rebooted (which makes me think that it didn't get to safemode), the rest of the times it wouldn't even get to the lockscreen.
What I'm currently attempting is to see if I can get it into safemode, or I'm trying to uninstall or stop/clear data for every single app with an intentional reboot each time.
Anyone got any idea what's going on? Is it maybe a bad sector, or worse, bad sdcard?
Gonna bump this. Still no luck on my part.
Anyone have any idea?
Perhaps somehow something got triggered to prevent anything being written to the sdcard? (Kinda like the lock switch on actual sdcards?) Is everything I've been doing going straight to memory since everything reverts back after a reboot? That's the only explanation I can think of.
Perhaps there's more I could try. I'm only moderately knowledgeable with things like fastboot and roms, so maybe someone with more experience might have more insight. Please, chime in.
Thanks in advance,
JM
Same problem here....
Flash factory image
USBhost said:
Flash factory image
Click to expand...
Click to collapse
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Amd64bits said:
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Click to expand...
Click to collapse
O ok
Amd64bits said:
Same problem here....
Click to expand...
Click to collapse
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
violoncellemuse said:
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
Click to expand...
Click to collapse
Boot twrp temporary from the bootloader
USBhost said:
Boot twrp temporary from the bootloader
Click to expand...
Click to collapse
I'm unfamiliar with this, how do I boot temporarily?
violoncellemuse said:
I'm unfamiliar with this, how do I boot temporarily?
Click to expand...
Click to collapse
1 set getting on computer
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
violoncellemuse said:
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
Click to expand...
Click to collapse
then you did boot twrp temporary
USBhost said:
then you did boot twrp temporary
Click to expand...
Click to collapse
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
USBhost said:
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
Click to expand...
Click to collapse
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
violoncellemuse said:
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
Click to expand...
Click to collapse
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
USBhost said:
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
Click to expand...
Click to collapse
I do thank you for trying to help me out.
I found a thread with someone with the same problem I'd like to direct people towards: http://forum.xda-developers.com/showthread.php?t=2800064
violoncellemuse said:
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Click to expand...
Click to collapse
Well, I have Paranaoid Android 4.4.4, not Cyanogen, and everything seemed ok until I installed Cloudmagic (and maybe Busybox?) that poped up a Play Store error (I don't remember which one), and suddenly all the problems began. It started to reboots, rebooted so many times that I decided to flash another ROM... but this wasn't possible.
My recovery is TWRP, so we can discard Cyanogen, ParanoidAndroid, CMW and TWRP as guilty, I think.
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
Tried that, nothing happened, still with Paranoid Android.
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
Same here.

Thought I bricked my N6

Hey guys,
Just for informational purpose I want to share my awful experience over the weekend. This is my first Nexus that I've decided to keep the boot loader locked with everything stock. Basically I sideloaded the 5.1.1 OTA on my N6 and that went smooth. After side loading it, I decided to wipe my cache from recovery. The formatting cache message kept going for over 20 minutes so I thought it hung and I forced boot my phone. Now I got stuck in a boot loop and when accessing the recovery screen I started getting "could not mount /cache" error messages. So now I decided to factory reset from recovery and lo and behold... Formatting /data went on for over 20 minutes so I forced boot my phone again...now i had a corrupted /data and /cache partition so I thought my phone was 100% bricked since I had a locked boot loader. I searched google and found some N5 threads about people complaining about the same issue but found a post saying the formatting can take over 20 minutes. As my last chance I went to recovery and factory reset it again. I got tons of messages about the cache partition failing to mount but I let the factory reset continue. After 30 minutes the data and cache partition format finished and my phone was able to boot again. So moral of the story... Be patient..lol
Moral of the story; unlock your bootloader and don't live in fear.
bwheelies said:
Moral of the story; unlock your bootloader and don't live in fear.
Click to expand...
Click to collapse
+1 , i used my thanks
Yup I did unlock it right away after fixing this issue. Man I'm lucky forced booting during cache or data wipe didn't mess with the other partitions.
rasengan82 said:
Yup I did unlock it right away after fixing this issue. Man I'm lucky forced booting during cache or data wipe didn't mess with the other partitions.
Click to expand...
Click to collapse
+1 Well done, if something ever goes wrong you have a way out
Flasholic since Nexus one and I thought the n6 would be the first nexus I would not unlock the bootloader lol. What are the implications of this with encryption and the enhance device protection in 5.1?
rasengan82 said:
Flasholic since Nexus one and I thought the n6 would be the first nexus I would not unlock the bootloader lol. What are the implications of this with encryption and the enhance device protection in 5.1?
Click to expand...
Click to collapse
Some users decrypt to get faster reading and writing speed, its advantages are theoretical though imo. In real life it doesn`t make much difference in performance so the gain is marginal. Not worth the hassle for me.
Its feel nice when those little beads of sweat start popping out of your forehead and your thinking oh **** what happened. Keeps you on your toes.
bill3508 said:
Its feel nice when those little beads of sweat start popping out of your forehead and your thinking oh **** what happened. Keeps you on your toes.
Click to expand...
Click to collapse
If your anxious when you flash you need to read up bro, if you have the skills you have nothing to worry about and you just do your thing and follow the procedures
gee2012 said:
Some users decrypt to get faster reading and writing speed, its advantages are theoretical though imo. In real life it doesn`t make much difference in performance so the gain is marginal. Not worth the hassle for me.
Click to expand...
Click to collapse
There is nothing theoretical about it. The gains are VERY easily measured and astronomical.
And while it may not have a massive moment to moment advantage for **YOUR USE**, it does, in fact, have a great advantage to a lot of people who have frequent and large reads and writes. It is important for you to recognize that not everyone uses their phone in the same way.
---------- Post added at 01:57 PM ---------- Previous post was at 01:53 PM ----------
rasengan82 said:
Hey guys,
Just for informational purpose I want to share my awful experience over the weekend. This is my first Nexus that I've decided to keep the boot loader locked with everything stock. Basically I sideloaded the 5.1.1 OTA on my N6 and that went smooth. After side loading it, I decided to wipe my cache from recovery. The formatting cache message kept going for over 20 minutes so I thought it hung and I forced boot my phone. Now I got stuck in a boot loop and when accessing the recovery screen I started getting "could not mount /cache" error messages. So now I decided to factory reset from recovery and lo and behold... Formatting /data went on for over 20 minutes so I forced boot my phone again...now i had a corrupted /data and /cache partition so I thought my phone was 100% bricked since I had a locked boot loader. I searched google and found some N5 threads about people complaining about the same issue but found a post saying the formatting can take over 20 minutes. As my last chance I went to recovery and factory reset it again. I got tons of messages about the cache partition failing to mount but I let the factory reset continue. After 30 minutes the data and cache partition format finished and my phone was able to boot again. So moral of the story... Be patient..lol
Click to expand...
Click to collapse
Hahahaha, I remember the days of using more primitive electronics, where any operation on the storage device could REALLY brick it if you didn't let it complete. Usually, "community" instructions for hacking on those types of things came with big honking warnings about pulling the plug prematurely and the dire consequences of doing so.
I've bricked a few bioses over the years... have you ever hot swapped a bios on a live mainboard so you could reflash the thing? Fun stuff I tell you....
Haha nice prolly the storage chip on the phones don't brick because it doesn't have mechanical parts like regular HD. I'm sure you can still damage a regular HD if you shutdown during a format.
rasengan82 said:
Haha nice prolly the storage chip on the phones don't brick because it doesn't have mechanical parts like regular HD. I'm sure you can still damage a regular HD if you shutdown during a format.
Click to expand...
Click to collapse
Hell yeah, you can break everything if you realy mean too

Categories

Resources