just a quick question, do you have to wipe your phone (alt+w) everytime theres a new rom update? for example if going from JF ADP 1.5 to JF ADP 1.6, do you need to wipe phone before applying the 1.6 update? or is it only necessary to wipe if your going from different roms for example JF to Haykuro..etc..etc
thanks
anyone have an answer to my question?
I'm curious as well. The impression is that you do not as long as you've wiped when you originally rooted.
I'm sure the safe answer is yes, you should wipe but that's a pain in the a**.
You should wipe IMO.
If you don't wipe and run into esoteric issues most likely you will be asked to do so anyways as it is the only useful troubleshooting tool most of these people have because
1.They don't know any better (no ones fault)
2.They don't have time take a look at your debug logs and then instruct you through some most likely intermediate-advanced commands to fix the issue.
Say you moved into an apartment and it's filled with the last occupants stuff. There's a blood stained sofa, stacks of magazine around the WHOLE apartment and a dirty toothbrush. Are you going to be comfortable sitting on that sofa? Would those magazines get annoying? Would you brush your teeth with the dirty toothbrush?
If you have to walk 10 miles, do you wear your own shoes or the last runner's leather shoes that are two sizes too small? If you can even get the shoes on you, you're gonna be in pain and give up within the first mile.
^_^
My answer is: Always wipe. Let the new OS use his own shoes.
ok i understand where you guys are coming from, but what if its only a small update to say JF ADP 1.6, and you are on JF ADP 1.5, it wouldn't make sense to do a wipe just for a small update. am i wrong here. now if ur going from JF to Haykuro then a wipe is definitely necessary. I read somewhere before, that mentioned you didn't have to wipe if you were staying within the same rom. i guess i just need a better understanding on this.
See the quote in my signature
hahaha! ok so I guess I will wipe before applying any new updates. what about the JFupdater app, it says it applys any updates, i dont believe the app wipes your phone before applying it, so is it best not to use the jfupdater when flashing an update?
boricuaace said:
hahaha! ok so I guess I will wipe before applying any new updates. what about the JFupdater app, it says it applys any updates, i dont believe the app wipes your phone before applying it, so is it best not to use the jfupdater when flashing an update?
Click to expand...
Click to collapse
My suggestion is generally this: Try it without a wipe. If it works, then great, you keep all your stuff the way you had it. If you run into issues that seem blaringly obvious(home process crashing, many force closes, boot looping, etc) then go back to the recovery image and do a wipe. There aren't any problems I know of caused by not wiping that can't be solved by going back and doing it after the fact.
[email protected] said:
My suggestion is generally this: Try it without a wipe. If it works, then great, you keep all your stuff the way you had it. If you run into issues that seem blaringly obvious(home process crashing, many force closes, boot looping, etc) then go back to the recovery image and do a wipe. There aren't any problems I know of caused by not wiping that can't be solved by going back and doing it after the fact.
Click to expand...
Click to collapse
thanks! thats exactly what i was thinking but wanted to be sure.
now wiping wouldn't mess up any links to the sd card(apps2sd) correct? wiping basically justs wipes the data from the phone....i guess what i mean is would I have to set up apps2sd again?
i'm with marcus, if you can get away with not wiping great, if not oh well wipe. or you could perform a nandroid bakup and then wipe, then after the update just fastboot flash your data.img
boricuaace said:
now wiping wouldn't mess up any links to the sd card(apps2sd) correct? wiping basically justs wipes the data from the phone....i guess what i mean is would I have to set up apps2sd again?
Click to expand...
Click to collapse
You would only need to restore the symlinks (if that's the method you were using).
Related
Just updated JF1.41. Everything seemed perfect, but I found I couldn't download anything from Market, and couldn't see any clips from your tube either. I am able to see the previews in both...it's odd. If I changed wifi to GPRS, everything went back to good..I really did some modificaitons on IM. But even I copied back the original files, the problem still existed..I don't know if I can flash the official build back to fix this??
for me it works with jf 1.4.1. the only issue I have so far is that snapphoto does not recognize my sd anymore (see my other thread).
Before going crazy and flashing back to RC29, try doing a full wipe and see if that fixes the problem.
nickwinn said:
Before going crazy and flashing back to RC29, try doing a full wipe and see if that fixes the problem.
Click to expand...
Click to collapse
Agreed. flashing the nbh is a bit.. extreme . Additionally, flashing the nbh is riskier than wiping or re-applying the JFv1.41 update. Flashing the nbh could potentially brick your phone, doing a wipe or re-applying the JFv1.41 update doesn't touch the bootloader, so it is much much safer.
I had to reboot my phone before downloading anything from the market but I think it was because of bad reception. I say first reboot it, if it doesn't help -wipe it.
I found that I had to log into Gmail to setup the phone and log into the market via GPRS and download one program before I could download reliably via WiFi.
JesusFreke said:
Agreed. flashing the nbh is a bit.. extreme . Additionally, flashing the nbh is riskier than wiping or re-applying the JFv1.41 update. Flashing the nbh could potentially brick your phone, doing a wipe or re-applying the JFv1.41 update doesn't touch the bootloader, so it is much much safer.
Click to expand...
Click to collapse
Actually, I had done the wipe and re-applied the JFv1.41 update many times, but that didn't work for me. I knew I did something wrong, but I just didn't know how to undo what I had done...What I had done is that I deleted [email protected]@[email protected], and applied another version of this file in order to make my MSN work with others carriers except Tmobile in GRPS mode.
Anyone else with this problem on ADP1.1? I cannot even access the internet with WIFI any longer. I have deleted NOTHING, done a wipe, and prior to installing anything, tested it again. No dice
maybe a silly question, but those help me too, sometimes...
did you re-enter your wifi settings? they are wiped, too.
sputnik99 said:
maybe a silly question, but those help me too, sometimes...
did you re-enter your wifi settings? they are wiped, too.
Click to expand...
Click to collapse
I was about to smack you upside the head (interwebz style) but I have done stupid stuff before like that and realized it would be unjustified. Yes, my settings are all good. I am connecting with WPA-PSK
I don't think it has a lot to do with the 1.41 biuld. I'm still using 1.31 and just recently I've started having this same issue. I have no clue why this is happening, all used to work fine about 1 1/2 weeks ago????
I am relatively new to flashing ROMs & kernels for Android. Currently I'm using MIUI 1.5.6 and would like to upgrade to the newest version of 1.5.13.
My question is, do I have to wipe data if I'm just upgrading to the same ROM or would wiping cahce & Dalvik cache be sufficient?
Before anyone flaming me I have searched the forum prior to posting and surprisingly didn't find anything useful as I thought this would be a frequently asked question.
Thanks in advance!
I never clear if i'm gonna do the same rom and it seems to work perfect. So I'd say dont it takes less time but if your worried do it. clearing that stuff wont really loose anything so its your choice really
I think you ALWAYS should do a backup, just in case something goes wrong.
You have the device at the Computer, you have the cable hooked up.
What would it take... about 5 minutes to do the backup up ??
oddball69 is right. You should always do a wipe.
Just to avoid problems
Most of the Devs will specify for each version if a full wipe is not required. If you can't find anything about it then do a full wipe.
If they directly say a wipe is not required then it's probably just some small fixes.
Thanks for all the responses.
I was going to do a backup for sure I just wanted to avoid having to wipe everything and then reinstalling and re-setting up all my apps which could be quite a pain
Depends on the ROMs used, usually the developers state if this is necessary.
It wont hurt if you try without wiping, if it makes problem just wipe and do it again.
What is there to loose?
Hey all, long term lurker here posting, obviously, for the first time. I'm not sure whether this would be better placed in the general or q&a section, as it seems like a good portion of the general section consists of questions.
Anyways, on to the problem. I recently attempted to flash the mr1 version of CM7 and was greeted by a force close loop, with com.android.phone closing. This was after wiping the dalvik cache and all data before flashing the rom. I was actually getting into a bootloop before that, even thought the md5 of the rom matched up with the one posted. I had redownloaded the rom to try again, and managed to actually boot before running into this fc problem. I have no idea what could be causing this, and it would be great if anyone could offer up some ideas on potential fixes, or at least some insight into what might be going wrong.
What radio are you using?
As far as I know, the stock radio. I don't remember ever flashing anything other than some of the early thunderbolt cm7 builds. Radio version is 1.16.00.0223r.
You have the correct radio (you can use 223r or 402w for MR1 version). Did you wipe /data, /system, /cache, /dalvik-cache?
I believe I wiped all of those. I know for a fact that the dalvik cache got wiped, and I'm pretty sure I wiped /system and /cache
Dark_Rak3r said:
I believe I wiped all of those. I know for a fact that the dalvik cache got wiped, and I'm pretty sure I wiped /system and /cache
Click to expand...
Click to collapse
I'd recommend wiping and flashing back to a Froyo ROM (BAMF is always a good choice, just make sure its not one of the new Froyo mr2 ones), and then attempting to wipe and re-flash CM7. Sometimes these things just happen. If its just a little bug, this will fix it. If theres a deeper issue, we can do more to expose what exactly it is, but lets go in baby steps
MattBeyers said:
I'd recommend wiping and flashing back to a Froyo ROM (BAMF is always a good choice, just make sure its not one of the new Froyo mr2 ones), and then attempting to wipe and re-flash CM7. Sometimes these things just happen. If its just a little bug, this will fix it. If theres a deeper issue, we can do more to expose what exactly it is, but lets go in baby steps
Click to expand...
Click to collapse
I'd agree but me personally I'd just do a wipe of /system, /data, /cache, /dalvik-cache and reload the ROM fresh over a clean system. Once you do that and load up gapps see if you have any issues before reloading apps. It wouldn't hurt to return to a FroYo ROM just to make sure things are good though as well.
Try clearing data on contacts storage, phone, and media storage, for some reason one of those worked for me
Thanks, I'll try your suggestions and see if they get anywhere. @MattBeyers, I'm currently on the stock sense rom (or whatever you end up on after rooting), so would you suggest I flash another froyo rom or should I just go ahead and try a wipe and then reflash cm7?
EDIT: Well something worked. Seems like I'm good to go, although I'm not really sure if anything changed in what I did to try and get cm7 running this time. Thanks for your help guys, and hopefully I won't run into any more problems here.
Ok so I have Vahalla Final flashed through Odin as my first ROM on this phone. Everything has been great for a few days and I flashed the lighting tweak today with no issues. Just a little while ago I made a backup and flashed the Linda voices and the Ki3 modem bc I saw where the KJ6 didn't allow long text messages. When I flashed the modem some blue words popped up really zoomed in on another screen then it was done. The phone was laggy so i tried to delete everything and restore like I had done numerous times on old phone.
I did a factory reset then cache then tried to format system. These are all steps i used to successfully take on other phone. It won't let me format the system though. Says: "format_volume failed to mount "/system" error formatting system!"
Where did I go wrong? Am I supposed to do some more wacky things on this phone for a restore? Everything else on it seems to take 20 more steps
aburn95 said:
Ok so I have Vahalla Final flashed through Odin as my first ROM on this phone. Everything has been great for a few days and I flashed the lighting tweak today with no issues. Just a little while ago I made a backup and flashed the Linda voices and the Ki3 modem bc I saw where the KJ6 didn't allow long text messages. When I flashed the modem some blue words popped up really zoomed in on another screen then it was done. The phone was laggy so i tried to delete everything and restore like I had done numerous times on old phone.
I did a factory reset then cache then tried to format system. These are all steps i used to successfully take on other phone. It won't let me format the system though. Says: "format_volume failed to mount "/system" error formatting system!"
Where did I go wrong? Am I supposed to do some more wacky things on this phone for a restore? Everything else on it seems to take 20 more steps
Click to expand...
Click to collapse
CWM versions prior to those in bhndven's Slightly Modified Stock kernels have a problem with mounting/unmouting the /system partition in GB. I believe you can backup and restore user data, but nothing on the /system partition.
Flashing the KI3 modem shouldn't have had an effect like you're describing, though. I can't say I've had an issue like that at all or heard of people having that issue after flashing the modem.
stephen_w said:
CWM versions prior to those in bhndven's Slightly Modified Stock kernels have a problem with mounting/unmouting the /system partition in GB. I believe you can backup and restore user data, but nothing on the /system partition.
Flashing the KI3 modem shouldn't have had an effect like you're describing, though. I can't say I've had an issue like that at all or heard of people having that issue after flashing the modem.
Click to expand...
Click to collapse
So everything should run fine after trying the actual restore of my backup even though i couldn't format the system? I have a backup but don't want to restore over data that wasn't deleted or whatever. If that's possible.
How the hell do i know which modem to use anyways? There's like 10 to choose from
Uh yeah I forget it tries to format system anyways when restoring... and it couldn't. So what do i do? Re-flash the GB starter pack way through Odin?
aburn95 said:
Uh yeah I forget it tries to format system anyways when restoring... and it couldn't. So what do i do? Re-flash the GB starter pack way through Odin?
Click to expand...
Click to collapse
As for the modem, I'm using KI3 on mine. You already did a factory reset so you should be able to just re-flash Valhalla.
Trying now. Does Vahalla automatically change all the mounts that the other roms require changing before flashing?
aburn95 said:
Trying now. Does Vahalla automatically change all the mounts that the other roms require changing before flashing?
Click to expand...
Click to collapse
I'm not sure about that one. Definitely go check the original Valhalla post to make sure you don't have to set the mounts.
Guess you don't have too. I'm using it now. thanks for the help
aburn95 said:
Guess you don't have too. I'm using it now. thanks for the help
Click to expand...
Click to collapse
No worries. Good luck
Hey I still have an issue. I reflashed Vahalla through CWM and it was fine at first all the way through setting everything up like it was before. Ran smooth. I went to the market this morning and checked for updates and Google Search, Maps and Superuser updated. Phone started acting really laggy again. Scrolls really slow, pulls up GO Launcher menu slowly, etc.
It seems to me that the re flash installed over the existing data that was left on the phone since i couldn't format my system.
My new question is, what's the best way to re do everything including formatting the system if I can't format through CWM? If I flash through Odin does that format everything? Or am I better of just going through the whole GB Starter Pack process again?? Or will that even work now since i've already done it?
aburn95 said:
Hey I still have an issue. I reflashed Vahalla through CWM and it was fine at first all the way through setting everything up like it was before. Ran smooth. I went to the market this morning and checked for updates and Google Search, Maps and Superuser updated. Phone started acting really laggy again. Scrolls really slow, pulls up GO Launcher menu slowly, etc.
It seems to me that the re flash installed over the existing data that was left on the phone since i couldn't format my system.
My new question is, what's the best way to re do everything including formatting the system if I can't format through CWM? If I flash through Odin does that format everything? Or am I better of just going through the whole GB Starter Pack process again?? Or will that even work now since i've already done it?
Click to expand...
Click to collapse
Did you restore your previous apps are do fresh installs?
Restored w titanium..... ugh.. Flashing a new zip doesn't wipe anything right? Just installs over whats already there right?
aburn95 said:
Restored w titanium..... ugh.. Flashing a new zip doesn't wipe anything right? Just installs over whats already there right?
Click to expand...
Click to collapse
If you flashed and "it was fine at first all the way through setting everything up"...
try reflashing as you did before. Do fresh installs on as much as you can ONE AT A TIME. And then restore ONE AT A TIME what you can't do fresh installs on. It sounds like one of your backups is not agreeing with the system. Install/Restore ONE AT A TIME and play with phone between each to see if you can determine which backup your system is not agreeing with.
Did that make sense??
EDIT: And make sure to wipe dalvik cache and cache partition before you reflash as is always recommended.
stephen_w said:
No worries. Good luck
Click to expand...
Click to collapse
lumin30 said:
If you flashed and "it was fine at first all the way through setting everything up"...
try reflashing as you did before. Do fresh installs on as much as you can ONE AT A TIME. And then restore ONE AT A TIME what you can't do fresh installs on. It sounds like one of your backups is not agreeing with the system. Install/Restore ONE AT A TIME and play with phone between each to see if you can determine which on your system is not agreeing with.
Did that make sense??
EDIT: And make sure to wipe dalvik cache and cache partition before you reflash as is always recommended.
Click to expand...
Click to collapse
Yeah it makes sense thanks. I will do this despite how impatient I am (see where that got me). I'm just got spoiled on another phone that was way way easier to work with. Weren't as many options to screw up either.
Any suggestions on how I can get my system to format for future reference?
I feel like it's Go Launcher for some reason. In cased you missed it though, I didn't start having lag issues until I flashed the Ki3 modem and linda voices one after another. I have a good backup but I can't format system to restore it.
aburn95 said:
Yeah it makes sense thanks. I will do this despite how impatient I am (see where that got me). I'm just got spoiled on another phone that was way way easier to work with. Weren't as many options to screw up either.
Any suggestions on how I can get my system to format for future reference?
Click to expand...
Click to collapse
I have never formatted my system nor read anybody wanting/needing to format their system. A factory reset is what people use to clean the gremlins along with wiping dalvik cache and cache partition. Bhundven has recommended flashing the same rom twice in a row I believe to help make sure all installs correctly (I think he was talking about bootloaders when he recommended that).
But a factory reset is what I think you are trying to accomplish with formatting your system.
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
aburn95 said:
I feel like it's Go Launcher for some reason. In cased you missed it though, I didn't start having lag issues until I flashed the Ki3 modem and linda voices one after another. I have a good backup but I can't format system to restore it.
Click to expand...
Click to collapse
I use GoLauncher on Vahalla Black with no problems. I think it has to do with your backup... not the app itself.
I wiped caches, did factory reset, tired to format system again with no luck and accidentally restarted before re-flashing Vahalla. Which, I guess I didn't really need to do anyways if it's an App causing the issue. I guess the factory reset would be enough. Smooth again so i will try some fresh reinstalls now. Thanks for the noob patience
lumin30 said:
I have never formatted my system nor read anybody wanting/needing to format their system. A factory reset is what people use to clean the gremlins along with wiping dalvik cache and cache partition. Bhundven has recommended flashing the same rom twice in a row I believe to help make sure all installs correctly (I think he was talking about bootloaders when he recommended that).
But a factory reset is what I think you are trying to accomplish with formatting your system.
---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------
I use GoLauncher on Vahalla Black with no problems. I think it has to do with your backup... not the app itself.
Click to expand...
Click to collapse
Ok cool. In another phones forum a system wipe is actually suggested a lot. I think... I did it every time on the G2x before installing any new roms or backups. I wasn't doing it at first but started after someone suggested it. But yeah I think the factoy reset is enough. Seems to be enough so far.
aburn95 said:
I wiped caches, did factory reset, tired to format system again with no luck and accidentally restarted before re-flashing Vahalla. Which, I guess I didn't really need to do anyways if it's an App causing the issue. I guess the factory reset would be enough. Smooth again so i will try some fresh reinstalls now. Thanks for the noob patience
Click to expand...
Click to collapse
I am a noob too. No worries. Vahalla Black is solid. Backups are tricky. Fresh installs are the way to go.
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.