Can't format, Constant Errors, Strange Issues - Droid Incredible Q&A, Help & Troubleshooting

So on Wednesday, I woke up to find all blank screens on my droid incredible. No apps, no widgets, etc. Thought this was odd. Rebooted, and they all came back. Then, came the error/force close messages. For everything. My contacts would randomly disappear, everything would just crash etc.
Went to clockwork (most recent version, whatever it is) to try to wipe the dalvik cache, regular cache, and fix permissions. Dalvik and permission fix went fine. When I tried to format the cache I got an "error formatting cache" message.
Over the last couple days, I noticed other strange problems. App updates wouldn't install properly, Every time I would reboot my phone, all my text messages from tuesday on would disappear (including any I have sent since a reboot). Apps I tried to uninstall would magically reappear on reboots. It seems that every time I rebooted my phone, it would revert back to this state prior to whatever went wrong with it.
This morning, I got a strange "UID Inconsistencies" message and telling me to wipe the phone data. My Only choice was to select a button that said "I'm Feeling Lucky"
I said screw it, I'll just backup what I need and wipe it.
Tried to do a data wipe via CW and.......when I rebooted it was like I never did. All the apps I had uninstalled were present, same issues (though slightly less prevelent), it was like I never did a factory reset at all.
I am really confused by this. I installed NO new apps prior to this, was not doing anything fancy on my phone. I rooted my phone last fall sometime, and have Touch of Blue 2.0 Rom installed. My only purpose for rooting and flashing this rom was to get rid of the dreaded "memory low" errors that plague the Incredible. I didn't experiment with anything so I am unclear how this problem arose or how to fix it. My phone basically works, but it's like the state of the phone continually reverts back to sometime between Monday and Wednesday of this week every time I reboot, no matter what I do to it, along with a slew of crazy errors that makes it extremely frustrating.
Hoping for some help. Thank you.

w0j07 said:
So on Wednesday, I woke up to find all blank screens on my droid incredible. No apps, no widgets, etc. Thought this was odd. Rebooted, and they all came back. Then, came the error/force close messages. For everything. My contacts would randomly disappear, everything would just crash etc.
Went to clockwork (most recent version, whatever it is) to try to wipe the dalvik cache, regular cache, and fix permissions. Dalvik and permission fix went fine. When I tried to format the cache I got an "error formatting cache" message.
Over the last couple days, I noticed other strange problems. App updates wouldn't install properly, Every time I would reboot my phone, all my text messages from tuesday on would disappear (including any I have sent since a reboot). Apps I tried to uninstall would magically reappear on reboots. It seems that every time I rebooted my phone, it would revert back to this state prior to whatever went wrong with it.
This morning, I got a strange "UID Inconsistencies" message and telling me to wipe the phone data. My Only choice was to select a button that said "I'm Feeling Lucky"
I said screw it, I'll just backup what I need and wipe it.
Tried to do a data wipe via CW and.......when I rebooted it was like I never did. All the apps I had uninstalled were present, same issues (though slightly less prevelent), it was like I never did a factory reset at all.
I am really confused by this. I installed NO new apps prior to this, was not doing anything fancy on my phone. I rooted my phone last fall sometime, and have Touch of Blue 2.0 Rom installed. My only purpose for rooting and flashing this rom was to get rid of the dreaded "memory low" errors that plague the Incredible. I didn't experiment with anything so I am unclear how this problem arose or how to fix it. My phone basically works, but it's like the state of the phone continually reverts back to sometime between Monday and Wednesday of this week every time I reboot, no matter what I do to it, along with a slew of crazy errors that makes it extremely frustrating.
Hoping for some help. Thank you.
Click to expand...
Click to collapse
Are you s-off, bootloader unkocked, or both? Have you tried reflashing recovery?

cmlusco said:
Are you s-off, bootloader unkocked, or both? Have you tried reflashing recovery?
Click to expand...
Click to collapse
s is on, because it seemed like too much effort to downgrade/turn it off than it was worth since my reasons for rooting didn't require it. I'm not sure what you mean by the bootloader being unlocked so probably not, and no I have not tried reflashing recovery. Will try that now.

w0j07 said:
s is on, because it seemed like too much effort to downgrade/turn it off than it was worth since my reasons for rooting didn't require it. I'm not sure what you mean by the bootloader being unlocked so probably not, and no I have not tried reflashing recovery. Will try that now.
Click to expand...
Click to collapse
Well if you have a custom recovery and have flashed a rom, then you have to be unlocked. Use fastboot and type without quotes "fastboot erase recovery " and then " fastboot flash recovery recovery.img ".

Related

[Q] Root66 T999UVDM5 ROM

I have been on all the Root66 versions, and have had no problems ever...... till this UVDM5
I made a CWM backup (2 just to be sure) and proceeded to flash this new version that I have been waiting for so anxiously!
After it booted up, my desktop was the same, and all the apps showed, but talkback was already turned on, and I could no way get to the settings to turn that #$%%$ thing off. Heck, I could not even get to anything at all. It kept talking and reciting numbers everytime I tried to do anything. It was "Frozen" on the main homescreen, and could not do anything. I sometimes could get to the app drawer and that, too, would not scroll or do anything. I Re-flashed the thing after doing another download with the usual cache, dalvic blow out, and it acted the same way...
I decided to revert to the backup and tried to get to recovery (CWM).... That, too was gone! Stock recovery. I flashed the only version I had of CWM and it booted, and declared both of my backups were "corrupt" after it was almost done restoring?????? WTF!!!
I then reloaded UVDMD5 again, got the same results so did a factory restore and got to install my ROM manager, and re-flashed CWM to the version it uses, and tried the restore.....
It worked, and now after some pressure packed moments, I'm back to the UVLJA. I have to go on a trip tomorrow, (in a few hours) and need the phone working. PHEW! if anyone knows why the hiccup that I had occurred, please chime in and let me know. I still want the new OS and after my return, I plan to do the update again.... Hopefully....... Just gotta ccalm m my nnnneerves a bit before I attempt it again!
bobolinko said:
I have been on all the Root66 versions, and have had no problems ever...... till this UVDM5
I made a CWM backup (2 just to be sure) and proceeded to flash this new version that I have been waiting for so anxiously!
After it booted up, my desktop was the same, and all the apps showed, but talkback was already turned on, and I could no way get to the settings to turn that #$%%$ thing off. Heck, I could not even get to anything at all. It kept talking and reciting numbers everytime I tried to do anything. It was "Frozen" on the main homescreen, and could not do anything. I sometimes could get to the app drawer and that, too, would not scroll or do anything. I Re-flashed the thing after doing another download with the usual cache, dalvic blow out, and it acted the same way...
I decided to revert to the backup and tried to get to recovery (CWM).... That, too was gone! Stock recovery. I flashed the only version I had of CWM and it booted, and declared both of my backups were "corrupt" after it was almost done restoring?????? WTF!!!
I then reloaded UVDMD5 again, got the same results so did a factory restore and got to install my ROM manager, and re-flashed CWM to the version it uses, and tried the restore.....
It worked, and now after some pressure packed moments, I'm back to the UVLJA. I have to go on a trip tomorrow, (in a few hours) and need the phone working. PHEW! if anyone knows why the hiccup that I had occurred, please chime in and let me know. I still want the new OS and after my return, I plan to do the update again.... Hopefully....... Just gotta ccalm m my nnnneerves a bit before I attempt it again!
Click to expand...
Click to collapse
It seems to be an issue with the latest version of TalkBack on most roms. I had the issue already and from what I read in the forums, many other people have to. My advice, as soon as you flash a rom, uninstall or freeze talkback and DO NOT let it update to the latest version. Im not too sure what the issue is but hope Google fixes that soon.
I think also that I had a problem before when I installed the stock 4.1.2, it seemed to take my sdcard and renamed it to 0 on the sdcard. Took me a few hours to figure that out. I then copied everything that was in the folder 0 over everything in the root of the sdcard and it was back to normal.
Thanks! (Clicked it already)
I did notice a LOT of stuff was on the external card after the final recovery to the older version and had to clean up the external SD card.
You were right! I had no means to freeze the TalkBack, or do anything at all while within the OS itself, so no alternative was available to me at that time except a Factory Restore. The re-installation of my software was just going to take too long, so I did a recovery using the same version of CWM and was back where I was before the fiasco. Good thing I got it going.... Ida been really screwed! LOL. I'll try again maybe later, when I get home.
When I do try again, I'll remove the SD Card and then do the install using a spare one.
Have a great day!

[Q] In desperate need of help. GT-N7100 'soft brick' ?

I'm in need of help guys and girls.
The other night I decided to "increase my battery life" by "disabling" a few (probably system) apps, through the "Apps Manager / All Apps" tab in Settings.
Everything was ok for another 10mins, went to bed.
Woke up to the "Samsung" logo stuck on the screen.
I tried rebooting and rebooting after removing the battery (15-20 times),
this gave me the same result; self rebooting non-stop after freezing on the "Samsung" screen.
I cleared the Dalvik Cache.
This got me past the "Samsung" screen and went to "Updating Apps".
It initially completed the 192/192 (Number of apps on my phone),
but then rebooted, and continued to reboot every time it got to the "Android is updating apps" screen.
Will 'flashing' a (most likely stock, but suggestions are very much welcome) Kernel fix this problem?
I was stupid in not backing anything up on Titanium Back Up, and not setting up a regular backing up schedule, (since everything was running smoothly for 1 year)
I really have no back up of the data on the phone.
Please.
Please, some one out there, help me just get back into my phone with out losing all my data, and I promise I won't play around with system files any more.
Extra info.
I remember rooting the phone the day I got it, but can't remember what I did exactly. Probably a pre-rooted ROM.
It was a fire and forget thing, and I haven't played with Android software much since then. So now processes need to be explained to me like I'm 5. :good:
>TLDR; Think I disabled system apps. Can't get past "Samsung" / "Android is updating apps" screen. Constant self rebooting at these screens. No back up of any phone data. Will 'flashing' (stock?) Kernel fix this? (and not delete all my data) Please help, ****ting bricks here.
Reflashing the Stock ROM should fix this, yes.
Clear the cache again once you've flashed it.
Mate,
For what you are saying, you have a recovery (Phil'z, Clockwork or TWRP). If so, try and Format data and cache. Doing that wont erase your internal memory, dont worry. I guess it should be enough to get your phone working again.
After that, BACK UP!
Leogp said:
Mate,
For what you are saying, you have a recovery (Phil'z, Clockwork or TWRP). If so, try and Format data and cache. Doing that wont erase your internal memory, dont worry. I guess it should be enough to get your phone working again.
After that, BACK UP!
Click to expand...
Click to collapse
I'm at a recovery(?) screen. "CWM-based Recovery v6.0.1.4"
You mean to "wipe data/factory reset" AND "wipe cache partition" ?
Will I lose contacts, sms messages, S notes, emails, installed apps, photos, videos, the lot?
I'm still in semi panic mode and am afraid to do anything that might delete any of the above. :silly:
Through this "CWM-based Recovery v6.0.1.4", I have made a ".dup" back up to my external SD.
Is this enough before I do anything else?
I have other users saying I should, "Then flash a stock rooted rom and restore your data backup."
If so, should I flash JUST the stock ROM (which I don't even know where to get),
or should I flash the newer 4.3 Jelly Bean ROM since I'll be "flashing a ROM" anyways?

Strange Boot Loop With NO CWM Recovery

I've got a T-Mobile Note 3 that I picked it up on launch day last Thursday at a T-mobile store. I proceeded to root the phone with Odin, then restore via Titanium Backup and then fix the backup with "restorecon -R -v /data". Life has been great until last night. Initially I got a circle with a line through it instead of the mobile signal and my cellular link would not connect, but my wifi was fine. When the problem was sill occurring this morning I figured it was an odd cellular problem and rebooted the phone this morning when it persisted. Now the phone is rebooting a few minutes after it completes booting.
It will boot normally, then I'll unlock the phone and get my window manager (Holo)...then I'll get the error "Process system isn't responding. Do you want to close it?". Then I get the error "Unfortunately, Favorite Apps has stopped." Regardless whether I interact with those error messages the phone then reboots a minute later. I have *not* done a restore from CWM ever and the phone doesn't seem to have suffered any physical damage.
The things I've tried include:
*) power down, remove sdcard, then reboot
*) power down, remove sim card, then reboot
*) power down, remove sim card, remove sdcard, then reboot
*) clear cache, then reboot
*) clear dalvik-cache, then reboot
*) clear dalvik-cache and cache, then reboot
*) clear dalvik-cache, clean cache, then wipe to factory, then reboot
In all the above scenarios nothing has changed. The phone reboots after it completes booting.
In the past, I've rooted and flashed on a G1, a G2, and an S3. I've bricked my S3 that had to be repaired via JTAG. This reboot problem with my Note 3 is completely unlike any of the things I've seen with previous phones.
I've read through some of the other threads about reboot loops, but all the threads I've read were caused by a CWM restore and have no solution yet.
Does anyone know the cause of this and what could fix it?
digitalfiend said:
I've got a T-Mobile Note 3 that I picked it up on launch day last Thursday at a T-mobile store. I proceeded to root the phone with Odin, then restore via Titanium Backup and then fix the backup with "restorecon -R -v /data". Life has been great until last night. Initially I got a circle with a line through it instead of the mobile signal and my cellular link would not connect, but my wifi was fine. When the problem was sill occurring this morning I figured it was an odd cellular problem and rebooted the phone this morning when it persisted. Now the phone is rebooting a few minutes after it completes booting.
It will boot normally, then I'll unlock the phone and get my window manager (Holo)...then I'll get the error "Process system isn't responding. Do you want to close it?". Then I get the error "Unfortunately, Favorite Apps has stopped." Regardless whether I interact with those error messages the phone then reboots a minute later. I have *not* done a restore from CWM ever and the phone doesn't seem to have suffered any physical damage.
The things I've tried include:
*) power down, remove sdcard, then reboot
*) power down, remove sim card, then reboot
*) power down, remove sim card, remove sdcard, then reboot
*) clear cache, then reboot
*) clear dalvik-cache, then reboot
*) clear dalvik-cache and cache, then reboot
*) clear dalvik-cache, clean cache, then wipe to factory, then reboot
In all the above scenarios nothing has changed. The phone reboots after it completes booting.
In the past, I've rooted and flashed on a G1, a G2, and an S3. I've bricked my S3 that had to be repaired via JTAG. This reboot problem with my Note 3 is completely unlike any of the things I've seen with previous phones.
I've read through some of the other threads about reboot loops, but all the threads I've read were caused by a CWM restore and have no solution yet.
Does anyone know the cause of this and what could fix it?
Click to expand...
Click to collapse
I would just Odin to stock and restart. I'm guessing some app your restored form another phone did it.
YellowGTO said:
I would just Odin to stock and restart. I'm guessing some app your restored form another phone did it.
Click to expand...
Click to collapse
I don't believe it was an app that was restored because the restore had run perfectly for 5 full days. I completed the restore last Thursday...that's what makes this so unusual.
Do you know where to get the stock zips to use with Odin?
digitalfiend said:
I don't believe it was an app that was restored because the restore had run perfectly for 5 full days. I completed the restore last Thursday...that's what makes this so unusual.
Do you know where to get the stock zips to use with Odin?
Click to expand...
Click to collapse
There's some stock Odin tar files in the Android development forum. Download and flash using Odin. Once it reboots, remove battery and manually boot into stock recovery and do a factory reset/wipe. Reboot and it should work.
Sent from my SGH-T889
jmerlos said:
There's some stock Odin tar files in the Android development forum. Download and flash using Odin. Once it reboots, remove battery and manually boot into stock recovery and do a factory reset/wipe. Reboot and it should work.
Sent from my SGH-T889
Click to expand...
Click to collapse
It looks as if the stock tar in zip format (N900TUVUBMI7_N900TTMBBMI7_TMB.zip) can be downloaded from either of these links:
http://forum.xda-developers.com/showthread.php?t=2465764 (faster download link)
http://forum.xda-developers.com/showthread.php?t=2468275 (slow download link)
I just finished downloading from the first link and after extracting the zip file I have these files:
N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5
SS_DL.dll
This seems like an obvious thing, but want to ask because of how odd this problem is: Do I simply flash the "N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5" file the same way that I flashed the CWM through Odin?
Yes, but IIRC, just uncheck reboot, reboot manually into recovery, then wipe, factory reset, etc. Pull your battery, reboot. Check the TWRP thread, it has exact directions.
sgh-TWEAKED-889©
Warrior1975 said:
Yes, but IIRC, just uncheck reboot, reboot manually into recovery, then wipe, factory reset, etc. Pull your battery, reboot. Check the TWRP thread, it has exact directions.
sgh-TWEAKED-889©
Click to expand...
Click to collapse
Got it, thank you! Here's what I'm referencing for the Odin options:
http://forum.xda-developers.com/showpost.php?p=46110842&postcount=2
I'll flash this and update the thread.
Good luck bro!!
sgh-TWEAKED-889©
Ok, I flashed with Odin then once it completed I got the "PASS!" status in Odin. I shut down Odin, pulled the battery from the Note 3, then allowed the phone to boot. There was a "booting recovery" message in blue at the top of the screen before the phone booted, then it booted to the "samsung logo", then the animated circular logo, then the white screen with the "T-Mobile 4G LTE" logo, then rebooted. The second boot, it did the same thing but stayed on the "T-Mobile 4G LTE" screen for many minutes...then it seemed as if it was completing it's reboot because I got the notification bar with the time and the circle with the line through it for the cell signal strength. I got the same error when the phone seemed to have completed booting, then a reboot. Now it's back to the same place it started in it's rebooting cycle.
This makes absolutely no sense at all. If I'd have done a CWM restore then I could understand that...but there's no reason for this that I can see. The phone acts as if it was knocked off of the T-Mobile network and now it finishes it's booting cycle long enough to be rebooted.
So now I have a useless Note 3. I'm game for taking the phone back to the T-Mobile store and requesting that they replace the phone, which they probably would, but I have no guarantee that this wouldn't happen again. I'm open to suggestions as long as they don't cause me to brick my phone completely.
I finished installing TWRP and darthrom successfully. However, after the darthrom finishes booting I have the exact same problem with the phone rebooting that the stock ROM had.
I'm back to square one.
I'm open to suggestions.
There are a lot of people having boot loop problems even without root though they are spread out among various sub forums. Try this thread for example:
http://forum.xda-developers.com/show....php?t=2467005[Q] Reboot cycle after restart help
Sent from my SAMSUNG-SGH-I317
Dumbo53 said:
There are a lot of people having boot loop problems even without root though they are spread out among various sub forums. Try this thread for example:
http://forum.xda-developers.com/show....php?t=2467005[Q] Reboot cycle after restart help
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
I saw a couple threads last night when I was searching around on the web about other models of phones with SIM socket and SIM card issues. I'm beginning to think that my issue is hardware-related, and not software. I did another wipe last night based on this thread's post: http://forum.xda-developers.com/showpost.php?p=46157872&postcount=6&nocache=1&z=7848000959493220
Instead of simply wiping, I formatted /data/, then wiped, then I flashed on the stock ROM, then flashed on the darth rom. I got slightly different results once the phone was done with it's firstboot - it kept giving me the error that a new SIM card had been installed and the phone needed to be rebooted. This causes me to suspect the physical hardware of my Note 3 or the SIM card. I have ruled out the SIM card because I've been using it in my old G2 since this started, via an adapter for the G2's SIM socket, and it's been fine. I'm planning on taking the phone to T-Mobile today and seeing what they can sort out with either a SIM exchange or phone exchange.
The note 3 misbehaved the same way while in the T-Mobile store. They swapped the phone out under warranty after asking only the basic questions and trying a factory reset. The same SIM card in the new note 3 works fine.
I'm on the same boat. Got my Note 3 this morning, rooted an hour ago with CMW, made backup and flashed Stock ROM from Jovy. Result: bootloop. Restore backup and still on bootloop. DLing the Odin stock .tar to see if it helps. Any more suggestions?
Edit: After flashing with Odin the stock tar from Sammy all it's good...at least for now.
Wally72 said:
I'm on the same boat. Got my Note 3 this morning, rooted an hour ago with CMW, made backup and flashed Stock ROM from Jovy. Result: bootloop. Restore backup and still on bootloop. DLing the Odin stock .tar to see if it helps. Any more suggestions?
Edit: After flashing with Odin the stock tar from Sammy all it's good...at least for now.
Click to expand...
Click to collapse
How far into the booting process would you get before the phone rebooted?
digitalfiend said:
How far into the booting process would you get before the phone rebooted?
Click to expand...
Click to collapse
Never passed Samsung! In my case, flashing the .tar with Odin from Samfirmware fixed my issue. I think imma wait for a more stable recovery.
Sent from my SM-N900T using Tapatalk now Free
Wally72 said:
Never passed Samsung! In my case, flashing the .tar with Odin from Samfirmware fixed my issue.
Click to expand...
Click to collapse
Interesting...it sounds like you had the boot loop that many others have had...it's cool to hear that you got it fixed. I think my problem was hardware-based since the phone completed it's boot process and *then* had issues. Luckily T-Mobile was there for me and helped out.
Wally72 said:
I think imma wait for a more stable recovery.
Click to expand...
Click to collapse
I know what you mean as far as waiting for a stable recovery. If it's any help, I've decided to stay far away from the recovery restore and simply use Titanium backup to do restores. It's more work than a nandroid recovery, but it reliably does it's job well for me.
digitalfiend said:
Interesting...it sounds like you had the boot loop that many others have had...it's cool to hear that you got it fixed. I think my problem was hardware-based since the phone completed it's boot process and *then* had issues. Luckily T-Mobile was there for me and helped out.
I know what you mean as far as waiting for a stable recovery. If it's any help, I've decided to stay far away from the recovery restore and simply use Titanium backup to do restores. It's more work than a nandroid recovery, but it reliably does it's job well for me.
Click to expand...
Click to collapse
Well...I'm doing a lot of reading. I can't stand this "stock look" and me, every time I root a phone, I always do my own modifications within the ROM I choose to flash. SystemUI and apk's. I only change the .png's, therefore, getting the visual look I want/like. Always done it with certain ROMs/Themes. I downloaded Jovy's stock ROM and made the visual changes I wanted. I flashed and got into that bootloop scenario. Restore backup with CWM provided by Zedomax and made it worse. I think the problem is recovery (at least from what I've read). In this case, CWM been less unstable than TWRP. I f you read a bit around, must ppl if not all, had the "dead bootloop" issue with TWRP. I haven't read from anybody yet having the "dead bootloop" with CWM. Ppl with CWM that flashed their backup and got that bootloop, fixed it flashing back to stock, where ppl that had TWRP have tried to flash back to stock and their phones never boot completely
Again...imma wait a little more for good reports as far as recovery goes!
Bigbiff has a file he uploaded, it may be a fix for the bootlooping issue. You'd be the first to try at this point. It's linked below, but the entire thread is in the OG development of tmobile.
http://forum.xda-developers.com/showthread.php?p=46379854
sgh-TWEAKED-889©
I've never seen so many issues with a brand new flagship phone before. Makes me think it wasn't tested fully before release. I mean all these problems!
Even though I returned my N3 after I tried restoring and getting bootloop of death, I feel this model is really flawed. Hearing new things everyday.

[Q] Gnex restarts constantly, can't do factory reset, can't reflash

Hello, there.
Get prepared for a lot of bad bad stuff..
So, my Galaxy Nexus was running on a CM-11 Snapshot build, with AOSP kernel. Yesterday, out of the blue, the phone started to get terribly slow and not responsive at all. After a few minutes, it restarted, only to do the same. A couple of minutes maybe, booting up, then get slow and reboot - it did this constantly, and it still does.
I have tried to go into clockworkmod recovery - wiped cache, wiped dalvik cache, wipe user data (factory reset). The phone booted up again, but my apps, etc. were still there! Nothing had happened. I did it a couple of times, but nothing at all.
Then, I have found a .zip file that was still on my memory, with the latest snapshot I had installed. I tried installing it with the install from sd card option, but when it loaded up again, I was still seeing the same apps, background etc.! Nothing had happened and no error message.
Decided to leave the "custom" days behind, I downloaded the stock image for my Gnex. However, since it is a yakjuxw build, I had to flash the yakju option - so not the ideal "stock" package. Using the google installer, I was unable to proceed, since the bootloader number was different than the one that the installer expected, so it exited.
I have found online the amazing Nexus Root Toolkit from WugFresh. I tried to flash it from there, enabling the "force flash" option.
It started out ok.. But when it went to the "system" portion, it took 25 minutes (!) to complete and then in the "user data" portion, it said "write failure".
Still, rebooted and I was still seeing my apps etc. What on earth is happening?
Honestly, I would expect that it would be bricked by now, with all these rom flashes and factory resets. I even tried flashing the stable CM version for it, but still nothing had changed.
Any help would be greeeeatly appreciated.
Yeah im pretty sure your emmc is fried. So you have two options: buy a new phone or a new motherboard. You van check by locking the bootloader if its still unlocked upon reboot your emmc is fried..
Sent from my Galaxy Nexus using XDA Free mobile app
I runned "fastboot oem lock' from my command line, and I got the status "OK".
Then I pressed "restart bootloader" on my phone, but it still says "lock state - unlocked".
So I suppose, I should let it rest in piece, or change the motherboard?
I think a motherboard is more expensive than a new phone. If it is just let it die. If it isnt you can buy a new motherboard and swap it. But I dont think that is a smart move now. The moto g for example is a awesome phone for (i think) almost the price of a new mobo.
Sent from my Galaxy Nexus using XDA Free mobile app
same problem here
It makes me wonder, I'm having the exact same issue just a couple of days later. Is this the planned obsolescence thing?
withend said:
Hello, there.
Get prepared for a lot of bad bad stuff..
So, my Galaxy Nexus was running on a CM-11 Snapshot build, with AOSP kernel. Yesterday, out of the blue, the phone started to get terribly slow and not responsive at all. After a few minutes, it restarted, only to do the same. A couple of minutes maybe, booting up, then get slow and reboot - it did this constantly, and it still does.
I have tried to go into clockworkmod recovery - wiped cache, wiped dalvik cache, wipe user data (factory reset). The phone booted up again, but my apps, etc. were still there! Nothing had happened. I did it a couple of times, but nothing at all.
Then, I have found a .zip file that was still on my memory, with the latest snapshot I had installed. I tried installing it with the install from sd card option, but when it loaded up again, I was still seeing the same apps, background etc.! Nothing had happened and no error message.
Decided to leave the "custom" days behind, I downloaded the stock image for my Gnex. However, since it is a yakjuxw build, I had to flash the yakju option - so not the ideal "stock" package. Using the google installer, I was unable to proceed, since the bootloader number was different than the one that the installer expected, so it exited.
I have found online the amazing Nexus Root Toolkit from WugFresh. I tried to flash it from there, enabling the "force flash" option.
It started out ok.. But when it went to the "system" portion, it took 25 minutes (!) to complete and then in the "user data" portion, it said "write failure".
Still, rebooted and I was still seeing my apps etc. What on earth is happening?
Honestly, I would expect that it would be bricked by now, with all these rom flashes and factory resets. I even tried flashing the stable CM version for it, but still nothing had changed.
Any help would be greeeeatly appreciated.
Click to expand...
Click to collapse
Google's secret weapon to make us buy the new Nexus 6.
I don't know why that happens though - dual core processor, with this amount of RAM. Tech-specs-wise, GNex has nothing to be jealous about than mid-range smartphones right now.. Unless, the CPU architecture from 2012 is so bad that it can't run properly today's apps.
Hey guys, I have these problems too. Just bought the Galaxy Nexus from a friend for €15 (cracked screen) and from the moment I turn it on, (sometimes at Nexus logo, sometimes on lockscreen.. ) it reebot itself. Again and again.
Unlocked the bootloader by toolkit or manually by fastboot but after the reboot it's locked again, as you said. I've tried Odin too with same results. The strange thing it's that it took time to do things but after the reboot, it's like I haven't done anything. I mean, even if I delete an app, or wipe data from recovery (not custom), when it turns on, it's always the same.
It's like a challenge to me. Anyone can help? I can't just give up >.<
Inviato dal mio Nexus 4
What the hell, just finished answering another thread with same issue (forum.xda-developers.com/galaxy-nexus/help/wipe-flash-restarting-help-t2908788). Happened to me last week, very same, never touched the phone, always stock.
What the hell is going on here???
Is there any way to get any log files to determine what the hell is going on?
Mine opens up for a few minutes, maybe 3-4 and it seems to be working well.. It gradually gets unresponsive and ultimately restarts.. So, if there is anything to do during these 3-4 minutes, I would be glad to know..
If you have backed up your sdcard data to your computer, and are prepared to start from scratch (i.e. flashing bootloader and recovery via fastboot, etc.), you can do a full erasure with "fastboot -w" in fastboot mode. This has worked for me in the past to fix data corruption, of which it sounds like you may be a victim. See if that works, but make sure you've backed up your sdcard backups and other data you want to keep first!!!!!!!!
7175 said:
If you have backed up your sdcard data to your computer, and are prepared to start from scratch (i.e. flashing bootloader and recovery via fastboot, etc.), you can do a full erasure with "fastboot -w" in fastboot mode. This has worked for me in the past to fix data corruption, of which it sounds like you may be a victim. See if that works, but make sure you've backed up your sdcard backups and other data you want to keep first!!!!!!!!
Click to expand...
Click to collapse
Already tried, uneffective. Everything, no matter how low level (e.g. Odin) has no effect, like the memory is write-protected. I've read elsewhere this means the eMMC is fried, but if you go backwards in this forum you see many ppl had the very same problem in the past few days/weeks. Very strange indeed.
I'm having exactly the same issue, was running CM11 mod too. Could it be a cyanogen fail?
Atreb92 said:
I'm having exactly the same issue, was running CM11 mod too. Could it be a cyanogen fail?
Click to expand...
Click to collapse
No. I've always been on stock.
fabrice79 said:
No. I've always been on stock.
Click to expand...
Click to collapse
But could it really be a hardware fail? It's pretty strange tho that multiple device have the same hardware issue in such a short time difference
Atreb92 said:
But could it really be a hardware fail? It's pretty strange tho that multiple device have the same hardware issue in such a short time difference
Click to expand...
Click to collapse
That's what I say, but just go backwards and have a look at older post. I subscribed to ~10 posts until 15 Oct then I got tired of browsing backwards...
I'm allready looking at older posts thats why i'm saying it's pretty strange that there is a massive hardware fail for this many devices. If it's a software fail there must be a solution somehow.
Same problem by 31th December...
Yeah, i have the same problem since august 2014. This thread confirmes for me, that my Gnex is really dead. It is sad, it served my very well and i wanted to use it as secondary phone and as mobile hotspot.
Same for me at the beginning of december
This problem I've faced one time and that meant that EMMC is fried, as fellow members said earlier.
If you overwrite the storage and reboot then everything's the same means that you can't write (somehow) thus emmc is dead. Write failure also means that EMMC is dead.
It's really sad, but that's it

Crosshatch Issue With ROMs & TWRP. Strange Occurrences

Ok, So Here's The Deal.. The Thing.. The WTF
So I had an older version of the Scorpion ROM installed and working fine for a while and wanted to change it up. I downloaded the newest TWRP. Both image and installer.zip, newest Magisk and RR 7.
I flashed the latest stock and you know, followed all the proper steps and after I flashed RR 7, it wouldn't boot up. (Not the issue) as others have had the same issue with RR 7. I left a post about that on the RR 7 thread and went about reflashing stock and proceeded to find a different ROM to check out.
No matter what I try to flash: Lineage, Scorpion, RR 7, dotOS the same thing happens... Everything flashes like it should, but then it won't boot, AND THEN every time I boot back to TWRP to try something else the haptic feedback vibration thing on the pixel 3 xl goes banana sandwich crazy and won't shut off until I reboot to fastboot to flashall to start over. LOL
And not only that but when I jump back to TWRP to try to flash something else stored on the phone, it says the storage is empty and there are nothing available in the menu. And I couldn't get a screenshot but there were some errors that have popped up in twrp as well...
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc.
I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Slo-mo Designs said:
Ok, So Here's The Deal.. The Thing.. The WTF
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc. I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Click to expand...
Click to collapse
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Always late to the party.
v12xke said:
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Click to expand...
Click to collapse
So yeah... I just now logged back on and saw your response [I have had notification issues on everything from Reddit to FB since I have had the 3XL]
About the response, I have had the issue with it showing the corrupt software screen a bunch when flashing new stuff. The reason I perform the Factory Slap is because it allows me to enter the menu where I have the option to "Boot from ADB" or whatever it says, sideloading seems to be the only way I can make progress when it starts giving the corrupt error.. The reason I didn't perform the full wipe but I can't remember exactly why now since that was over a month ago.
But I finally got it fixed, and I was going to repost because I had found a way to prevent the vibration thing from happening in TWRP but by the time I got around to posting, the new update had fixed it. Lol

Categories

Resources