Related
Hi, all. First time posting, long time lurker. I've gotten quite comfortable with flashing/running custom software in the last several months with my i727 Skyrocket. However, I've run into a problem I don't know how to fix. I was trying to go from CM9 to try AOKP M6. I did the following:
Backed up all apps + data in TB
Nandroid backup in CWM
Factory reset, wiped cache/dalvik cache twice each
Flashed UCLF6 modem (thought that might fix it)
Flashed AOKP, followed by gapps, agps fix, and mikey6 v7 offline Google Now.
Rebooted, ran through basic phone setup.
After all that, I've got no mobile data whatsoever - no MMS, no Internet, nothing. I've tried several times to get it working today, but to no avail. I've restored my CM9 backup and had it working just fine. I checked my APN settings and tried using the ones that come default with the phone, including some that use the wap.cingular settings.
At this point, I'm at a complete loss. I really like the feature set in AOKP, but it kinda renders my smartphone worthless if I have no data. So, any thoughts on how to get it going?
Nevermind, fixed it.
I'd tried all kinds of things to get it, but the steps at the bottom of a random blog post fixed it. It was from an unofficial build, no less. I'd post the link just to be helpful, but I see I can't post links given my noob status. Ah, well.
I am unlocked and have the recovery of twrp 2.3.3.0. I'm having problems with about every single rom I flash. I wipe everything as you are suppose to and the flash appears to go well but usually right away after the rom boots up the system becomes unresponsive. I have to hold my finger over a button for a couple seconds for it to acknowledge a touch and things just don"t run right.
Its like either the system is almost locked up or the touchscreen just hardly works.... one of the two. I made a backup of my original asus setup and if I restore it the tablet works just fine. I've tried hydro, cm 10.1, blackbean 7, and one or two I'm forgetting. AOKP RC1 is the only custom rom that gives me no problems at all in this regard, unfortunately its an unfinished rom, no camera and my battery dies like crazy with it...
The 2nd best running rom that I really like from what I have seen is blackbean 7. Runs great for first few minutes but after playing a game for a bit or doing some other things and having it run just great all the sudden the dreaded problem occurs and the only fix is a reboot for it to work for a while longer. So frustrated at this point as I have flashed so many roms and resetup so many things just to find myself doing it again trying to fix this and find a rom that works for me.
Any ideas at all on what could do this? Is the difference in the kernels the reason why AOKP RC1 and Asus original work but none of the others? Or does it have to do with my recovery? Fairly certain I have the correct most recommended one with twrp 2.3.3.0 and the process went fine. Any ideas greatly appreciated. I really just want to be able to run blackbean. And knowing that most all roms will not work for me is rather disturbing in regards to the future. Really wanting to like my new tf300t but its making it hard:silly:
Try to downgrade your recovery.
Use this : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
and take a feedback after, thanks
I really appreciate that you took the time to give me something to try but I'm afraid it didn't work. Process went fine I'm on 2.3.1.0 twrp but same problem. First rom I've tried instant non-responsive. Any other ideas?
I've been using ClockWorkMod Recovery on my TF300T, and it's been great. (Used it to upgrade my ROM to CM 10.1.) No issues at all.
If you need instructions for getting it installed on a TF300T, check out my second-to-last post on thoughtsontechnology.com. (NONE of the work is mine, I just compiled the instructions and links in one spot for easier access. Most of the work came from XDA contributors, they've been really great.)
Most roms need 5 to 10 mins to stabilize after a new install, usually as they are building media storage files, etc. Are you giving them enough time?
Failing that I can only think your microsd has something corrupt on it. Boot with it out.
Well I tried cwm again flashed it no problem installed rom no problem but no fix. So guess we have established it definitely isn't the recovery at this point...
Yes I've given roms several reboots and lots of suffering them working for 10min to only fail again for another reboot... So its not that. Still the only Rom that will work is my backup of the original asus and the AOKP RC1. Trying it without the external sdcard right now.
Well no joy on the removal of the external sdcard
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
sbdags said:
Have you tried a full wipe before installing? You must have some thing on the data partition causing this. I
Click to expand...
Click to collapse
Not sure what a full wipe is? I wipe cache/dalvik system format data and have even tried formatting the sdcard once several roms ago. One thing I have noticed since I am trying so many roms all the time is the sdcard file structure seems odd as I have at the root of the sdcard a 0 directory that continues to be added to. Currently it goes sdcard/0/0/0/0 to actually get to where I have things stored like music, downloads. Is this normal? Its strangely repetitive.
Personally I think you should stop using TWRP if you're having all these issues. Just flash CWM and have fun
touchscreen
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Showme1 said:
This thread is a couple months old, but i am having the same problem. After installing a lot of different roms, both stock based and cm/AOKP. I let the rom stabilize and after a few hours or even minutes the touch screen has a mind of its own. It lags, double touches or fails to respond at all. I m on twrp 2.4.1.0. Was this issue ever resolved? Should I try old version recovery or cwm? I restored rooted stock us10.4.2.20 and the issue is gone. Is it possible that installing a rom changed the touch screen firmware? I am open to suggestions as I have spent alot of time on this with no luck. Thanks!
What version CWM would u suggest as this is probably my next move?
Click to expand...
Click to collapse
Sounds like you have a hardware fault if the issue persists across multiple firmwares.
Also, OP said his SD card directory structure was strange. I'd format both internal and external SD in recovery (in addition to wiping and factory reset) before you flash.
Thanks! Wiping internal has seemed to do the job. Still would like to know what the issue was. I was thinking it was the touch panel firmware, but thought that would be in /system
Sent from my SGH-I747 using xda app-developers app
I installed CarbonROM 1.6.1 on my S3 yesterday, and every time I reboot the phone, it goes to an activation screen that never finishes. Additionally, my phone number displays incorrectly. I can fix this by going in and out of Airplane mode and changing the CDMA subscription. But it just reverts back after a reboot (along with the activation screen).
This has been mentioned several times in the developer forum, but I have not found a solution to make it work. I performed a clean install (factory reset, wipe cache and dalvik cache, etc.) along with another install on top of the same ROM without wiping. Does anyone have any suggestions on how to fix this?
Thanks.
That's pretty much it
Unfortunately that's pretty much it. Your phone information should eventually stick (dunno why, but it does eventually) but if it doesn't then try another clean install. (btw have you made a backup of your imei, that might help a little as well.) I've had this problem many times and these work for me pretty much every time.
I discovered that this isn't an issue only with CarbonRom. I tried LiquidSmooth and ran into the exact same issue. I then proceeded to install CleanROM and no longer experienced the issue. So it seems to be an issue with AOSP ROMS.
I've done numerous clean installs and dirty installs, all with the same result. I've also backed up my IMEI. When you say that my phone info should eventually stick, are we talking about needing to let it run for days/weeks without rebooting?
Thanks.
IamMark70 said:
I discovered that this isn't an issue only with CarbonRom. I tried LiquidSmooth and ran into the exact same issue. I then proceeded to install CleanROM and no longer experienced the issue. So it seems to be an issue with AOSP ROMS.
I've done numerous clean installs and dirty installs, all with the same result. I've also backed up my IMEI. When you say that my phone info should eventually stick, are we talking about needing to let it run for days/weeks without rebooting?
Thanks.
Click to expand...
Click to collapse
ive been having this issue when i tired both roms so i ended up on cleanrom and then went over to beans for now due to it been base off of clean rom and having the asop look and feel of a aosp rom and the features of touchwiz and the stabilizability of it
I tried a couple more things and simply could not get around the activation issue after every reboot. Also always had to go in and change it from nv to rium/sim. I simply don't see how everyone using AOSP ROMS isn't running into this issue on the S3, and I have yet to see one definitive answer on how to resolve it.
I ended up taking your advice and installing Beans. Its a pretty nice ROM and close enough to AOSP.
IamMark70 said:
I tried a couple more things and simply could not get around the activation issue after every reboot. Also always had to go in and change it from nv to rium/sim. I simply don't see how everyone using AOSP ROMS isn't running into this issue on the S3, and I have yet to see one definitive answer on how to resolve it.
I ended up taking your advice and installing Beans. Its a pretty nice ROM and close enough to AOSP.
Click to expand...
Click to collapse
yep its pretty good rom i like it. im kinda having a issue with my picture messages though but probably had a dirty flash when i chose the aosp mms. if you like touchwiz also check out cleanrom its a great stock rom best stable rom and pretty great battery life as well and beans rom i think is based off clean well your welcome hope you enjoy the beans rom aslo i had issues with the sim card to so your not alone
IamMark70 said:
I installed CarbonROM 1.6.1 on my S3 yesterday, and every time I reboot the phone, it goes to an activation screen that never finishes. Additionally, my phone number displays incorrectly. I can fix this by going in and out of Airplane mode and changing the CDMA subscription. But it just reverts back after a reboot (along with the activation screen).
This has been mentioned several times in the developer forum, but I have not found a solution to make it work. I performed a clean install (factory reset, wipe cache and dalvik cache, etc.) along with another install on top of the same ROM without wiping. Does anyone have any suggestions on how to fix this?
Thanks.
Click to expand...
Click to collapse
I downloaded Liquid Smooth 2.4, and it finally addressed the issue of the activation screen popping up after every reboot. So I'm extremely happy and loving the ROM!
Can someone please instruct me how to get GPS up and running again? I am on latest nightly and have tried various past builds. I installed the new modern, I have cleared the cache several times, dalvik and otherwise. I have even factory resetted several times. I use GPS allot because I work for FedEx. Any help would be greatly appreciated.
Sent from my SGH-T699 using xda premium
chuckiev79 said:
Can someone please instruct me how to get GPS up and running again? I am on latest nightly and have tried various past builds. I installed the new modern, I have cleared the cache several times, dalvik and otherwise. I have even factory resetted several times. I use GPS allot because I work for FedEx. Any help would be greatly appreciated.
Sent from my SGH-T699 using xda premium
Click to expand...
Click to collapse
same here.
nardholio asked to pm him if one has this issue. i did some hours ago. when i have an reply i'll pm you. or publish it here (whatever is applicable).
Thanks man !!!!
Sent from my SGH-T699 using xda premium
I hope this will work for you. This worked for me. I don't pretend to understand all the details of what went wrong, but from what I understand there's a non-volatile (ie factory reset, reboot, etc won't fix it) privacy setting on the GPS which, when activated, basically breaks GPS. Samsung must have realized this was stupid too because the latest stock rom/modem doesn't mess with this setting anymore. Unfortunately, if it was set before you upgraded to the newest modem, that means your GPS is stuck in privacy, aka non-working mode (stupid because if you didn't want GPS you should just turn it off).
So what you need to do is backtrack to a combination of software that DOES mess with this setting. Once you are SURE GPS is working again, you can consider flashing the new stuff again (you may have to try more than once because there is absolutely no user control of the privacy setting, another stupidity in the system).
So
1. Flash either an older stock image (newer stock image contains the same privacy bug so you can't use that) or older cyanogenmod and modem. For stock, I recommend the original firmware released with the phone https://dl.dropboxusercontent.com/u/103520801/T699UVALH1_T699TMBALH1_T699UVALH1_HOME.tar.rar
That is what fixed mine
You can try the following version of cyanogenmod + modem
http://goo.im/devs/nardholio/apexqtmo/cm-10.1-20130309-UNOFFICIAL-apexqtmo.zip
https://dl.dropboxusercontent.com/u/103520801/RelayLJ1modem.zip
2. Do a battery pull and wait a minute. Just to clear out anything that might be lingering.
3. Obtain a solid GPS fix. Install GPS Status and stand outside. If GPS doesn't come back at this point try the other route (cyanogenmod or stock)
4. Turn off GPS.
5. Battery pull, do not power off
6. Flash forward to cyanogenmod (build 111 or higher)/newer modem. You can try restoring your nandroid (at this point mine worked with a restored nandroid) but if GPS goes away again try with a fresh install.
7. If you obtained GPS on stock but cannot get GPS going in cyanogenmod try repeating again but replace step 4 with "do battery pull while you have a solid gps fix"
Thanks nardholio! It worked like a charm. Any chance we will ever see photosphere? If not it's no big deal. Just curious.
Sent from my SGH-T699 using xda premium
thanks nardholio
will try that when i get back from work...
Thanks for this tip Nard.
I did this.
1) Created a nandroid of my full wiped build 111 install/setup
2) full wipe install of 20130309 build
Got GPS to lock.
Turned GPS off.
Battery Pull.
3) Without wipe, nandroid restore of 111 build.
Reboot, GPS works.
Thanks again :thumbup:
Sent from my SGH-T699 using xda app-developers app
took the files on the road with me and worked like a charm.. did:
-backup
-format data/system/cache
-install radio and cm provided by nardholio
-boot and installed a gps status.apk off the web since i was too lazy to setup my google account ^^
-INSTANT gps lock. kept it running a lil, then restarted the phone with gps still enabled.
-format data/system/cache
-restored backup
==> works like a charm
thx again
Sent from my SGH-T699 using xda app-developers app
Sweet that fixed it right up. I did these steps, in this order:
1. Nandroid backup from CWM
2. (From CWM) Factroy reset and cleared cache, then flashed this file(rom): http://goo.im/devs/nardholio/apexqtm...L-apexqtmo.zip followed immeditatly by this one (cell radio) https://dl.dropboxusercontent.com/u/...ayLJ1modem.zip
3. Booted into cyanogenmod.
4. Downloaded and installed a recent googlemaps.apk
5. (Switched off wifi) Obtained a solid GPS fix
6. Turn off GPS.
7. Did a battery pull, did not power off just pulled the battery..waited 1 min and put the battery back in.
8. Booted into CWM recovery (by presssing Home, Volume Up and Power) and flashed the nightly build #137, immedetally flashed the MC5 Modem from this thread, and then after that finished immediately restored my nandroid backup.
GPS is working and my phone is still setup like it was an hour ago. PERFECT!
Thanks Nardholio :highfive:
though the reason was me misreading when i applied the fix, but i kept GPS ON. which actually - from a logic pov - is the thing that makes sense to me.
and it worked fine.
all you others switch it off once you've gotten a good gps fix.
and it works fine as well.
but it really raises the question what the real issue behind this problem is..
No "real reason" mr conspiracy theorist. Cycling the setting after getting a GPS fix makes sure its set the right way when you upgrade to the newest rom. Otherwise you don't know what state the chip has been left in
Sent from my SGH-T699 using xda premium
which makes it russian gps roulette
i guess, whatever works...
When you guys are saying GPS is broken - do you mean it doesn't work at all, or just takes a while to get a fix? Mine is slow to lock and the compass is off kilter, but eventually it will lock.
nah, it never locked. he just kept on searching for satelites forever.
The first lock after i went back to the latest build took a little but after that fft was like 5 seconds. and still is.
MIA on all files
Hi,
All of the original firmware files seem to be MIA. Does anyone have an alternative link to the original modem?
Thanks
BRad Barnett said:
Hi,
All of the original firmware files seem to be MIA. Does anyone have an alternative link to the original modem?
Thanks
Click to expand...
Click to collapse
Found it here...
http://forum.xda-developers.com/showpost.php?p=35147531&postcount=691
Nardholio said:
I hope this will work for you. This worked for me. I don't pretend to understand all the details of what went wrong, but from what I understand there's a non-volatile (ie factory reset, reboot, etc won't fix it) privacy setting on the GPS which, when activated, basically breaks GPS. Samsung must have realized this was stupid too because the latest stock rom/modem doesn't mess with this setting anymore. Unfortunately, if it was set before you upgraded to the newest modem, that means your GPS is stuck in privacy, aka non-working mode (stupid because if you didn't want GPS you should just turn it off).
So what you need to do is backtrack to a combination of software that DOES mess with this setting. Once you are SURE GPS is working again, you can consider flashing the new stuff again (you may have to try more than once because there is absolutely no user control of the privacy setting, another stupidity in the system).
So
1. Flash either an older stock image (newer stock image contains the same privacy bug so you can't use that) or older cyanogenmod and modem. For stock, I recommend the original firmware released with the phone https://dl.dropboxusercontent.com/u/103520801/T699UVALH1_T699TMBALH1_T699UVALH1_HOME.tar.rar
That is what fixed mine
You can try the following version of cyanogenmod + modem
http://goo.im/devs/nardholio/apexqtmo/cm-10.1-20130309-UNOFFICIAL-apexqtmo.zip
https://dl.dropboxusercontent.com/u/103520801/RelayLJ1modem.zip
2. Do a battery pull and wait a minute. Just to clear out anything that might be lingering.
3. Obtain a solid GPS fix. Install GPS Status and stand outside. If GPS doesn't come back at this point try the other route (cyanogenmod or stock)
4. Turn off GPS.
5. Battery pull, do not power off
6. Flash forward to cyanogenmod (build 111 or higher)/newer modem. You can try restoring your nandroid (at this point mine worked with a restored nandroid) but if GPS goes away again try with a fresh install.
7. If you obtained GPS on stock but cannot get GPS going in cyanogenmod try repeating again but replace step 4 with "do battery pull while you have a solid gps fix"
Click to expand...
Click to collapse
Worked perfectly.
1. Backup CM11.
2. Wipe all partitions.
3. Flash CM10.1 and Modem.
4 Pull battery.
5 Boot CM and install Google Maps
6. Set GPS to device only and open G Maps
7. GPS WORKS!
8. Reboot to recovery (forgot to disable gps)
9. Wipe partitions and restore CM11 backup
10. GPS WORKS!
I am however on baseband T699UVLJ1 and I believe T699UVBMC5 is the latest one.
All seems to be working so I will leave it like this for a day and then update and test GPS again.
Flashed to the latest baseband again without any problems so far
Nardholio said:
I hope this will work for you. This worked for me. I don't pretend to understand all the details of what went wrong, but from what I understand there's a non-volatile (ie factory reset, reboot, etc won't fix it) privacy setting on the GPS which, when activated, basically breaks GPS. Samsung must have realized this was stupid too because the latest stock rom/modem doesn't mess with this setting anymore. Unfortunately, if it was set before you upgraded to the newest modem, that means your GPS is stuck in privacy, aka non-working mode (stupid because if you didn't want GPS you should just turn it off).
Click to expand...
Click to collapse
After I managed to bollix up my GPS, I went through the steps with CM (the link to the stock rom is 404). I flashed the 10.1 gapps as well, and I used GPS Status instead of Maps, but I did manage to get GPS working again after restoring my backup. Thanks a bunch!
I must say, my Avant has a vastly better GPS than the Relay, but (for now) the Avant is completely stock/unrooted.
Nardholio said:
So what you need to do is backtrack to a combination of software that DOES mess with this setting. Once you are SURE GPS is working again, you can consider flashing the new stuff again (you may have to try more than once because there is absolutely no user control of the privacy setting, another stupidity in the system).
Click to expand...
Click to collapse
And why does it not work with a CM11 image?
I cannot find any CM10.1 image, links are dead! :/
----
Right, going back to CM10.2.1 and after that back to CM11 also worked.
Phone never booted in CM10.2.1 by the way... CM boot circle was going round and round for 15 minutes... Removed battery, tried to boot again, same thing. Went into recovery mode, luckily I still had a CM11 ROM zip on my phone. Installed it and works! Some Trebuchet error message popping up though and Google Play services crashing all the time.. Hmm we will see what can be done about that. Maybe because I used a July nightly.
Need help
I need serious help to fix my GPS. I want to follow the steps, but all the links are dead. So I have no idea how to obtain 10.1 or original stock firmware to fix gps.
Anyone can help with the files?
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.