Database Info

[Q] Unable to text unless my battery is in the red after the offical update

Long time lurker, but i dont think i have posted before...so sorry if this is on the wrong place/already been answered, if that is the case i would love be be redirected to where i should go.
Anyways, after updating this morning, everything worked fine other that some occasion lag. But when i opened up handcent, it was just a black screen. so i reinstalled it, and still no dice. the default messaging app had the same problem. If someone texted me i wouldnt get it, and there was no way for me to send out a text. then, when my battery went down to red, all of a sudden it worked like normal. i was able to charge it and even when the battery was full it still worked. However, when i reset my phone, it stopped working again, and resumed working when my battery got to red. Im pretty sure those are the only symptoms i noticed...Any ideas on what is going on/what i can do to remedy it?
And fyi, i was rooted before the upgrade and have rooted since. I had oclf, but disabled it before i upgraded.

Shameless bump, I really need help

Only thing I can think of is a bad install of the update. I would suggest going back to 2.1 using odin and then reinstalling the froyo update
Sent from my SAMSUNG-SGH-I897 using XDA App

So step one of http://forum.xda-developers.com/showthread.php?t=884364
Then follow the installation of 2.2 as samsungs website outlines? Would that require me to restore all of my apps and settings from tibu again?
Thanks

ahurley said:
So step one of http://forum.xda-developers.com/showthread.php?t=884364
Then follow the installation of 2.2 as samsungs website outlines? Would that require me to restore all of my apps and settings from tibu again?
Thanks
Click to expand...
Click to collapse
Yea if you are going to flash back to odin you will need to back up all user apps using titanium backup. Make sure you do not restore any system apps though as that can cause problems. Also you will lose your texts so I would recommend backing them up. I use sms backup+
Sent from my SAMSUNG-SGH-I897 using XDA App

My friend had the same problem and had to go back to 2.1 and re-install the update and then it worked. Seems like the update didn't install correctly on a handful of Captivates.

okay so i still haven't done this because of how long restoring everything with tibu takes, but if I am gonna have to go through this process again, should i just make my first venture into flashing a custom rom? Am i correct in thinking that flashing wont be messed up because of the current glitch i have because it all reverts back to stock as the first step anyways?

[Q] [SOLVED]home button not working

Okay so.. I have an answer to my problem.. this is a problem that i had encountered many times in forums while i was looking for my answer.. big thanks to diablo2224 for his help and a thanks goes out to Cranvis for actually replying at all..
Okay so the home button wasn't working at all and it would flash and basically do zero (im sure this fix would help any buttons if this was the case). In the end i didnt have much to lose the home button not working was giving me the 'sheets' so i just tried to flash most things for wifi xoom as i was hoping it would crack a difference but it didnt... i ended up seeing a post from stachre for an update and in it was there he had pointed to stock motorola files.. i grabbed these and preformed all wipes (user data, cache, delvik - i doubt it would do much but i did it anyway).. using fastboot i then flashed the boot.img, the system.img, the userdata.img and finally the recovery.img (can always flash over the CWM anway so not a big deal) and booted it back up... suprise suprise the home button was perfectly functional again (every other update/flash of software would seeming 'update' and not actually flash to that portion of the device thereby leaving my problem and the stock images must have actually hit these sectors) i know my answer is long but just trying to be helpful to anyone else with this type of problem (stock Xoom WiFi MZ604 HWI69 images from Motorola)
as a side note : this was followed by flashing the CWM again and booting into CWM and flashing the 2.1 hammer and then wiping user data and booting into the freshly updated rom stoked!
okay it seems the home button is not working at present. i have wiped all data and cache and dalvik cache a thousand times and tried reflashing, etc still to no avail. does anyone have any more ideas? its painful to push the back button a million times to get anywhere lol

joshndroid said:
okay it seems the home button is not working at present. i have wiped all data and cache and dalvik cache a thousand times and tried reflashing, etc still to no avail. does anyone have any more ideas? its painful to push the back button a million times to get anywhere lol
Click to expand...
Click to collapse
ok, so a few questions.
I am guessing it is rooted so my questions are:
What ROM are you using?
Have you tried other ROMs?
Have you been experiencing this problem since you installed the rom?
have you downloaded anything (APP, Live Wall Paper, a random APK File) before this happened?
Are you using a screen protector on the Xoom?
~If yes to the last question, is there any air bubbles or dirt in that area of the button?
~If no to last question, are you aware of any dirt or scratches in that area?
Have you tried the Home tab in Landscape as well as Portrait mode?
Have you just recently updated to a OTA that was pushed out by either Motorola/Verizon/etc?
There could be many possible reasons as to why this is happening... and I would like to help you (and who ever posts afterwords) to fix this situation. I or someone else on this board will respond as soon as possible to your problem and I hope this post helps to solve the problem

Cranvis said:
ok, so a few questions.
I am guessing it is rooted so my questions are:
What ROM are you using?
Have you tried other ROMs?
Have you been experiencing this problem since you installed the rom?
have you downloaded anything (APP, Live Wall Paper, a random APK File) before this happened?
Are you using a screen protector on the Xoom?
~If yes to the last question, is there any air bubbles or dirt in that area of the button?
~If no to last question, are you aware of any dirt or scratches in that area?
Have you tried the Home tab in Landscape as well as Portrait mode?
Have you just recently updated to a OTA that was pushed out by either Motorola/Verizon/etc?
There could be many possible reasons as to why this is happening... and I would like to help you (and who ever posts afterwords) to fix this situation. I or someone else on this board will respond as soon as possible to your problem and I hope this post helps to solve the problem
Click to expand...
Click to collapse
Okay mate ill answer each question firstly i was on the manta ray with update rom.. Everything was fine i was able to use it perfect as normal no updated apks no new apks.. I was fine i cam home from work seen the update so downloaded check the md5 and did all wipes as instructed in the tiamat 2.1 rom.. I had previously installed the kernal for that the day prior and was running great.. I tried reinstalling the previous rom again after a few reflashes of the 2.1 hammer and wiped that see if the button would come back to no avail..
I have a screen protector but it is fine i was using it for days prior wirh not 1 hiccup so that is definately elimated.. No pushed updates.. I went through all otas already before i flashed the manta ray stuff and as i said that was fine all the other buttond beside it work like tje back menu and switcher just the home does nothing
Cheers
Josh
Sent from my HTC Sensation Z710e using XDA Premium App

joshndroid said:
Okay mate ill answer each question firstly i was on the manta ray with update rom.. Everything was fine i was able to use it perfect as normal no updated apks no new apks.. I was fine i cam home from work seen the update so downloaded check the md5 and did all wipes as instructed in the tiamat 2.1 rom.. I had previously installed the kernal for that the day prior and was running great.. I tried reinstalling the previous rom again after a few reflashes of the 2.1 hammer and wiped that see if the button would come back to no avail..
I have a screen protector but it is fine i was using it for days prior wirh not 1 hiccup so that is definately elimated.. No pushed updates.. I went through all otas already before i flashed the manta ray stuff and as i said that was fine all the other buttond beside it work like tje back menu and switcher just the home does nothing
Cheers
Josh
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
Thank you for the speedy reply to my questions. And I am sorry to say, this is one that is over my head. I would suggest that you go to Tiamat's (Or current ROM's) maker and inquire for their help. I am new to some of this but I thought I should at least ask you the basics and make sure on everything. (Woo A+ Tech Training haha!) But unfortunately, I cannot help you with this problem because I do not know what could be doing this other then maybe a line of code didn't get placed into memory when the device was flashed, or maybe there is a small error in the code itself and only certain devices have this problem (different model number = slightly different change to the chip-sets and code of the device.) There are many things that could be the trouble, and like i said, unfortunately, they are out of my understanding of the device.
I do hope that you are able to get an answer soon to your question and I hope it is a simple answer.
Sorry I could not help any more but I hope others can!
Good Luck

joshndroid said:
okay it seems the home button is not working at present. i have wiped all data and cache and dalvik cache a thousand times and tried reflashing, etc still to no avail. does anyone have any more ideas? its painful to push the back button a million times to get anywhere lol
Click to expand...
Click to collapse
I reported this issue once before when I was using Xoom Zone a month or so ago. I hadn't wiped data, and it was like the home button was there just to look pretty. You could click it, it would highlight, but it was broken. If anything, I can be of service as I have had this issue once before.
I will need more info though. Do you restore data and try to hit the home button, or do you try the home button after a fresh data wipe without restoring data? It's hard for me to explain what I want you to explain, but...

diablo2224 said:
I reported this issue once before when I was using Xoom Zone a month or so ago. I hadn't wiped data, and it was like the home button was there just to look pretty. You could click it, it would highlight, but it was broken. If anything, I can be of service as I have had this issue once before.
I will need more info though. Do you restore data and try to hit the home button, or do you try the home button after a fresh data wipe without restoring data? It's hard for me to explain what I want you to explain, but...
Click to expand...
Click to collapse
A fresh data wipe mate exactly as the hammer rom thread instructed to do. No restore of data as i wanted to start fresh as i find less problems arise when u try to recover too much data and as the thread specifically called for a wipe i was more than obliging lol
Sent from my HTC Sensation Z710e using XDA Premium App

joshndroid said:
A fresh data wipe mate exactly as the hammer rom thread instructed to do. No restore of data as i wanted to start fresh as i find less problems arise when u try to recover too much data and as the thread specifically called for a wipe i was more than obliging lol
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
I see. I've never heard of this version of the problem. My problem occurred when updating from the 3.1 Rom to the 3.2 Rom. I only had this problem because I didn't wipe data the first time because after it booted up I thought all was well... until I discovered the home button was broken... lol.
Anyways, even I'm at a loss here for how we can solve your problem. A simple data wipe resolved mine in a heartbeat... but it seems your problem is still persistent even after a clean data wipe install... interesting... can't say that I've ever seen a problem stay in the memory even after a complete data wipe...
The only thing I can suggest is to maybe drop back to a stock Rom, maybe 3.1, then installing Tiamat from that fresh stock Rom with another clean data wipe before and after. That's all I can think of since after a data wipe it's still there. Good luck!

I dropped back to manta still with the issue.. Would a nandroid recovery possibly help fix as it takes precedence over an update cuz thwn someone maybe be able to help
Sent from my HTC Sensation Z710e using XDA Premium App

joshndroid said:
I dropped back to manta still with the issue.. Would a nandroid recovery possibly help fix as it takes precedence over an update cuz thwn someone maybe be able to help
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
That might help. I can help as much as I can, but...
Try to go full stock first before anything. Do not use Tiamat for right now. Install a completely stock, but rooted 3.1 Rom is what I suggest for you to do so that you can see if it's still giving you troubles on a stock Rom.

I tried that from the other thread and gained a bootloop.. Maybe stock 3.1 recovery and not just an update more to the point where would i find such? I only used otas as i was just speeding process to get to 3.2 to start flashing customs
Sent from my HTC Sensation Z710e using XDA Premium App

joshndroid said:
I tried that from the other thread and gained a bootloop.. Maybe stock 3.1 recovery and not just an update more to the point where would i find such? I only used otas as i was just speeding process to get to 3.2 to start flashing customs
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
I dunno man, I'm usually one who has great helpful answers, but... uh, this one stumps me. Like I said, I've never seen a problem that still persisted after a data wipe. It's almost as if it is much deeper than a data wipe, but more like something has locked itself into your Xoom's memory and won't leave without forcing it out manually... something must be messing with your system files or something like that. Possibly something left over from the OTA updates of some sort maybe. Very strange...
I would pass this by Team Tiamat. Sorry I can't help this time. Good luck!

I need a nandroid i think from someone
Sent from my HTC Sensation Z710e using XDA Premium App

joshndroid said:
I need a nandroid i think from someone
Sent from my HTC Sensation Z710e using XDA Premium App
Click to expand...
Click to collapse
So you want someone to have a completely data wiped nandroid backup of the latest Tiamat Rom so that you can use that? That should work, especially if the backup has everything working perfectly. By having the ability to use nandroid backups you have nothing to lose since it can be restored very easily.

im not picky i would like a nandroid of any rom really mate... as long as the home button was working... so basically from a wifi US xoom (if compatibility was an issue) and the rest was okay yeh that would be great... i dont know anyone else with one here in AUS so someone here would have to help me out
p.s i have already tried the one from the dev thread of the stock 3.2 but that is bogus and doesnt really work for anyone and it didnt for me

joshndroid said:
im not picky i would like a nandroid of any rom really mate... as long as the home button was working... so basically from a wifi US xoom (if compatibility was an issue) and the rest was okay yeh that would be great... i dont know anyone else with one here in AUS so someone here would have to help me out
p.s i have already tried the one from the dev thread of the stock 3.2 but that is bogus and doesnt really work for anyone and it didnt for me
Click to expand...
Click to collapse
I have a 3G Xoom, but I can make a data wiped clean nandroid backup for the latest Tiamat Rom, which I am running since Tiamat supports 3G and Wifi models alike. I can do that after work tomorrow if you would like me to...
Or you could find someone who has the Wifi model and do that.

diablo2224 said:
I have a 3G Xoom, but I can make a data wiped clean nandroid backup for the latest Tiamat Rom, which I am running since Tiamat supports 3G and Wifi models alike. I can do that after work tomorrow if you would like me to...
Or you could find someone who has the Wifi model and do that.
Click to expand...
Click to collapse
thanks for ya help... i solved my problem and edited my first post

joshndroid said:
thanks for ya help... i solved my problem and edited my first post
Click to expand...
Click to collapse
Cool! I knew it was something with the system files. Case closed.

[Q] Droid is in trouble, have tried everything I know of.

Alright folks, my phone appears to have gone off the deep end.
A few weeks back, I was changing over to the new Eclipse ROM, and at first everything was going fine and dandy. However, I soon began experiencing a few force closes. I restarted the phone, and then everything went to hell. So many force closes I couldn't operate the phone, inability to make calls, unable to open apps, unable to install apps, basically all I can do is text, receive calls, and browse the web (although after enough time the phone crashes anyway). I have tried everything I know of to fix it: new ROMs via recovery, new ROMs via Odin, deleting caches, deleting personal data, using the .pit file and factory stock in Odin, the works. I even found the Samsung PST and used that, but for naught. The weird thing is that even after using the .pit file (which is supposed to delete EVERYTHING), my phone "remembers" old applications that were installed on it. In fact, it seems like there is some sort of ghost image on my phone, and whenever I restart it the phone returns to that state (any applications I tried to uninstall are back, all contact data is deleted, etc.). This ghost image hangs around no matter what I do.
Any suggestions?

Sounds to me that you obviously are not getting a true "PASS" with pit file. If you had you would have no files saved on phone. But if you followed the instructions to a "t" like you allude to...
Sent from my SCH-I510 using xda premium

I have followed the instructions fully (and multiple times to boot), and I have always gotten a PASS.

This is sounding regrettably similar to the issues reported in this thread - try looking at post numbers in the mid 300s - I think they are centered around late September/early October (there are more than this, but I'm pretty sure that timeframe has the highest density of discussion on this). If it's what it sounds like, the /data partition is no longer in a state that can be written over (the "ghost image" you were referring to) - and truth be told I don't know if anyone has come up with a "free" solution to the problem.

dwitherell said:
This is sounding regrettably similar to the issues reported in this thread - try looking at post numbers in the mid 300s - I think they are centered around late September/early October (there are more than this, but I'm pretty sure that timeframe has the highest density of discussion on this). If it's what it sounds like, the /data partition is no longer in a state that can be written over (the "ghost image" you were referring to) - and truth be told I don't know if anyone has come up with a "free" solution to the problem.
Click to expand...
Click to collapse
I had read through those posts before, and was not very happy to see the conclusion. As those posts were from a few months ago, I was hoping that perhaps someone had some new ideas. Oh well, I guess I'll be trying my luck with Verizon. Thanks for trying, folks!

jderig said:
I had read through those posts before, and was not very happy to see the conclusion. As those posts were from a few months ago, I was hoping that perhaps someone had some new ideas. Oh well, I guess I'll be trying my luck with Verizon. Thanks for trying, folks!
Click to expand...
Click to collapse
Thinking... What recovery does your phone have on it now- stock or clockwork? Are you on rfs file system- did you revert back or can you flash a diff kernel using cwr?
These are just some thoughts that came to mind. If dwith can't help you I can't do much more. Good luck with Verizon offering any help
Sent from my SCH-I510 using xda premium

Corrupted NAND, but still returns a pass.
I had this once, I spammed with the PIT and it somehow worked
Sent from my SCH-I510 using xda premium

Hindle1225 said:
Thinking... What recovery does your phone have on it now- stock or clockwork? Are you on rfs file system- did you revert back or can you flash a diff kernel using cwr?
These are just some thoughts that came to mind. If dwith can't help you I can't do much more. Good luck with Verizon offering any help
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
I currently have Clockwork. I am unable to tell at this moment what my file system is, as I can't install Voodoo, and the method of adding/deleting folders on my SD card doesn't work. However, I do recall during one of my many attempts at using different kernels/radios/roms I did get the creepy female Voodoo bootup voice, but even though that said it was a success I was never able to tell whether it actually worked.
As of right now I am capable of ODIN and Clockworking any Rom/kernel/etc., but they all bring along the Ghost Image.
kvswim said:
Corrupted NAND, but still returns a pass.
I had this once, I spammed with the PIT and it somehow worked
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
What is NAND, if you don't mind me asking? Also, I suspect by now I've run ODIN with the PIT 10+ times with no success

jderig said:
What is NAND, if you don't mind me asking? Also, I suspect by now I've run ODIN with the PIT 10+ times with no success
Click to expand...
Click to collapse
NAND is just a type of flash memory. If you recognize the word nand then you should have an idea. If not, it's not really important.

jderig said:
Alright folks, my phone appears to have gone off the deep end.
A few weeks back, I was changing over to the new Eclipse ROM, and at first everything was going fine and dandy. However, I soon began experiencing a few force closes. I restarted the phone, and then everything went to hell. So many force closes I couldn't operate the phone, inability to make calls, unable to open apps, unable to install apps, basically all I can do is text, receive calls, and browse the web (although after enough time the phone crashes anyway). I have tried everything I know of to fix it: new ROMs via recovery, new ROMs via Odin, deleting caches, deleting personal data, using the .pit file and factory stock in Odin, the works. I even found the Samsung PST and used that, but for naught. The weird thing is that even after using the .pit file (which is supposed to delete EVERYTHING), my phone "remembers" old applications that were installed on it. In fact, it seems like there is some sort of ghost image on my phone, and whenever I restart it the phone returns to that state (any applications I tried to uninstall are back, all contact data is deleted, etc.). This ghost image hangs around no matter what I do.
Any suggestions?
Click to expand...
Click to collapse
just covering bases by asking, did you go ALL the way back to ed1 with that pit file or a more recent version (gb or something along those lines)

From what I understand, the phone is still working, but is very unstable. The PBJ kernel does NOT support Voodoo Lagfix (but still supports EXT4). Can you try flashing imoseyon's kernel (which supports it) and enabling/disabling Voodoo? It can be found at RootzWiki. Also, when you get into CWM, it says the version at the top.
Sent from my SCH-I510 using xda premium

Here you go....i have been here.
Get into clockwork(CWM) - mount everything via usb and backup what you need to backup.
Perform a quick format of your sdcard so that when you see your phone on the pc, its blank.
Go back to stock odin and boot up, report any issues.
Sent from my SCH-I510 using XDA

What happened next
I tried what you said because I'm in the same boat. I still get the FCs and it tries to walk me through the setup. It gets stuck at the Checking Account step in the setup wizard. I let it sit there for about an hour while I went to lunch to no avail.

tf700 Major, strange problem after update!

Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013

bobstone said:
Just froze a couple.
Click to expand...
Click to collapse
There's your problem...
Sorry mate, but I can't help myself - attention everyone, here comes a rant:
I cannot believe how many people do not backup the data on their tablets! This is the second time in as many days that I read: "Something unexpected went wrong and I cannot loose my data".
If you did not back it up the question is not if you loose it, the question is WHEN!
This is a portable device! Pre-destined to be lost, stolen, dropped, submerged, spilled upon, run over by trucks - and those are everyday scenarios which are LIKELY. Don't even want to get into freak accidents... It's so easy to protect your data now-a-days! There's Dropbox in conjunction with Dropsync, there's Google Drive and a host of other solutions. There is no excuse for having only one copy of important data...... End of rant
To your problem. Before you apply a stock update you have to replace/unfreeze all stock apps. Usually the update just fails if you have frozen system apps - I do not know what went wrong in your case.
How did you update? OTA or manually?
It sounds as if your data partition is corrupted since the stock apps (installed in /system) work, but your user apps (installed in /data) do not. But that your system apps work is the good news! At least you didn't brick your tablet.
One of the stock apps is the file browser. See if you can copy your precious data to a microSD. And I'm only talking about data like pictures, files, video, projects. Don't worry about your apps.
If the file browser cannot see your data you're gonna have to get into the area of data recovery tools - lots of research ahead of you there.....
Another possibility may be - if you can access your tablet from your PC through USB - to ADB pull files off your tablet, check if your computer recognizes your tablet.
Once you have your data safe (or given up on it) you can perform a factory reset and possibly have to reflash the firmware.
BTW, if you did not protect root with Voodoo Rootkeeper before the update or if you flashed the full firmware (as opposed to doing an OTA update) you also lost root. And Asus plugged the hole Motochopper used in the latest firmware version. At this point 10.6.1.14.10 is not rootable without unlocking.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

bobstone said:
Everyone help! I just updated my tf700 to the newest update which was supposed to be minor. Everything went smooth but upon boot up everything went wrong. Every single app force closes upon unlocking the lock screen. I get a pop up for just about every single app that's trying to start saying sorry the app has closed. Oddly, any app that was originally on the device works OK. I did a normal reboot and then again I saw the upgrading message and another message saying optimizing apps and it counts through the apps its optimizing. Then again when I reboot fully it does the same thing. I did a cold reboot and it seemed a little smoother but then again I had the same force closes and error messages. And still only the stock apps will function, anything and everything else force closes upon opening.
I've never even heard of errors or problems such as this. I have no idea what to do and I have lots of data on the device I don't want to lose and can't lose. By the way I am rooted and I did not uninstall any stock apps. Just froze a couple. Build # now 10.6.1.14.10-20130801
Please any and all suggestions!
Ps - under kernel version it says (concerned about name cancer):
3.1.10-gba9af5
[email protected] #1
Thu Aug 1 17:00:24 cst 2013
Click to expand...
Click to collapse
I would just wipe and start over, even if you get it functional again you could end up with problems.

Hmmm - I too think you are going to lose your data here as I can't see how you can recover without wiping if everything is force closing now.
BTW don't worry about the kernel version being cancer that is Asus naming convention. They have been using planets and have now run out so they are now using astrology instead of astronomy which is rather odd but there you go.
Previously we had mercury, venus, jupiter, uranus etc now we have aquarius and cancer......

What don't make sense and I can't accept, I've updated this device 4 times now total and never had a problem like this. Also, I've updated a few devices with frozen apps and had no problems. Are frozen apps really the cause? I can't see it.
And if I do have to wipe, and I really don't want to, will I still be rooted after wiping and is there a way to back up things since I can't use 3rd party apps? (Also, I used voodoo)
It just seems like something went wrong with the update, say something initializing or cache problem, and im sure there's an easy fix.
Please, keep the ideas coming...

I guess, I just need to clerify , stock bootloader, stock ROM, but rooted??
Sent from my [email protected]
Sorry all was reading it on the app wow that really is not good lol

Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.

Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4

bobstone said:
Any responses guys? Would really appreciate any help.
Thanks,
Sent from my rooted Galaxy S4
Click to expand...
Click to collapse
I think you will have to wipe mate as said. Painful but can't see any other way around it.

bobstone said:
Correct, stock rom rooted. No interest in custom roms. I know there's gotta be something simple, maybe even a chkdsk in linux or something. I just hate to wipe n start over. My files seem to be intact and non stock apps start to open for a split second then they force close.
Click to expand...
Click to collapse
Yea, wipe, and no you won't keep root on a stock rom wipe. As I said previously even if you managed to "fix" the problem you would be creating potential for lockups/forced reboots. Your also not the first to have issues when upgrading with sys apps frozen, look around the forum, its been discussed before. Sucks, but there it is.

I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/

vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
boy, i can't believe how close i was to actually going forward with this OTA when it "pooped" up in the notification area. good thing i had just been reading xda forums and i saw a couple posts bout ppl losing root and whatnot with said update.
now i am a happy camper on Cromi-x =D
best bet as a few already said is to try to extract your data from the thingy, and wipe it out, if you wanna take a n00b advice, if you're close to the end of your warranty period, go ahead and unlock it then proceed to cromi-x it. i was of the same position as you back when i bought it, not interested in custom roms and whatnot, just root...... but since my warranty was expiring next month anyways, and it had grown considerably sloppy and laggy, i figured out, why not? and i gotta tell you, it was the right thing to do.
hands down
anyways, good luck on your recovery.

I wiped and downgraded to .8 and will happily stay there for now. Maybe until I unlock the bootloader in the future.

vatvedt said:
I have the same issue, and I can't remember freezing any apps. I don't have any critical data that I can't loose though. Still it sucks to have to wipe if there's another way.
Stock, locked bootloader, rooted. Temp unrooted using OTA Rootkeeper and did the OTA. Then upon the next reboot, all apps FC. All earlier updates has worked flawless. :/
Click to expand...
Click to collapse
If you don't have it download Titanium Backup, hit Menu and wipe Dalvic cache. Reboot. The reboot will take a while because the Dalvic has to be rebuild - so don't panic
If that doesn't do it, I'm fresh out of ideas.

I tried to wipe via the stock recovery, but all the FC's was still there, and what's worse was that because of the FC's I couldn't finish (or quit) the "Set up your tablet" thingie. I always crashed on setting up a gmail account. Didn't matter if I was connected to the internet or not, or if I declined setting it up. So I had to do everything from the stock recovery.
Downloaded the .8 firwmare, unpacked the first .zip file, renamed the second .zip (to EP201_768_SDUPDATE.zip) and put it on an empty micro SD, made sure the SD-card was FAT32, booted to recovery (Power Vol down for 5 sec) and installed it via RCK, Android stock recovery.
Thanks for the tip, though. It might have worked. I don't know.

[Q] Need Help after rooting implosion

UPDATE: 07-04-14 5:25pm EST:
I was able to get all my data off using a mac. I re-flashed Purity ROM after doing a full wipe. I have now re-installed all most of my apps and have begun normal use. For now this is resolved hopefully I have no further issues. Thanks for the response @Kreateablaze Much appreciated.
So here is a brief history about what I did and what I am experiencing. I am pretty much a newb here so please be gentle and excuse my ignorance.
Just in case you don't want to read my book below:
TLDR: rooted phone, Installed TWRP, installed Purity Rom, system failed hardcore, cant get data off my phone because explorer crashes. I just want to get my data off so I can re-install a ROM or just flash back to stock and re-lock the bootloader.....
-Unlocked bootloader, rooted, and installed TWRP using "Wug's Nexus Root Toolkit"
(just want to give props to any one involved in that tool, it is an amazing tool and worked flawlessly!)
-After running the toolkit, I was successfully rooted and running TWRP.
-I ran a back up using TWRP. Is that what is referred to as a "Nandroid" back up?
-After running this back up I installed "Purity ROM"
-For the first 24 hours everything was fine.
-I had to reboot my N5 due to an app that was acting up and a reboot usually cleared up the issue if force stopping didn't. (an app I used before rooting and I knew how to fix the issue I was having, I don't think this is related to my issue.)
-After rebooting the phone, I was faced with a pop up stating something along the lines of android UI has stopped working. I clicked okay, unlocked the phone it flashed black with my home screen icons and everything went back to normal. I rebooted the phone again just to make sure that was a one time fluke. This time The phone was in an endless crash cycle. Every process I could think of was crashing non stop the phone was unusable. I did some research and found something that said to go into TWRP and run a permissions repair.
-After running permissions repair my phone booted back up and was working relatively okay.
-After the repair rebooting my N5 results in that same UI crash I got the first time. BUT the phone is usable, and that process never crashes again unless I reboot.
-After running that permissions repair some of my apps disappeared. Trying to re-install them results in a -24 error. I got a few of them to re-install by clearing related data in data/data folder. A few of my apps refuse to re-install even though there is no trace of the data in the data/data folder.
-Another issue I am having after all of this is that I can NOT pull any data off of the phone. I plug it in, Windows recognizes the phone but it takes about 10-15 minutes to load the folder structure. I am then unable to copy any of the data off of the phone. Explorer crashes and I cant get the data off. UPDATE: I was able to get the data of the phone by using a friends Mac. I will post an update with some more info.
-I need to get my data off the phone before I can continue but am unable to. Any help would here would be greatly appreciated.
-Also if any one knows a more stable ROM with a similar feature set to Purity that is fast, has good battery life and isn't packed to the gills with features tht may one day cause more issues that they are worth. Please let me know.
Thanks in advance for any help you guys may be able to offer me.

Well I'm not too sure what your issue could be, but purity is one of the most stable roms on here... Have you looked in the purity thread for posts saying the same thing happened? I highly doubt it is the rom.
Sent from my Nexus 5 using xda app-developers app

Kreateablaze said:
Well I'm not too sure what your issue could be, but purity is one of the most stable roms on here... Have you looked in the purity thread for posts saying the same thing happened? I highly doubt it is the rom.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I would definitely agree that something went wrong rather than the ROM being unstable..... Any idea about how to get my data off the phone. at this point that is my main concern so I can re-flash purity....

basik17 said:
I would definitely agree that something went wrong rather than the ROM being unstable..... Any idea about how to get my data off the phone. at this point that is my main concern so I can re-flash purity....
Click to expand...
Click to collapse
I'm not too sure, I never had to get the data off my phone using a computer, always just used titanium backup. Maybe try reflashing purity, just wipe cache not any data.
Sent from my Nexus 5 using xda app-developers app

Kreateablaze said:
I'm not too sure, I never had to get the data off my phone using a computer, always just used titanium backup. Maybe try reflashing purity, just wipe cache not any data.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response. I was able to get my data off using a friends Mac... I am going to reflash Purity and see how things go. If they dont go well I may go back to stock. I never seem to have good luck with these things...