Acore FC Downgrade! - Eee Pad Transformer Q&A, Help & Troubleshooting

Started the process to root (had flashed the 3.1 update). Loaded .9 to uSD and flashed down to 8.2.3.9 all went well. Upon boot started getting all sorts of FC (acore). Noted in About Tablet I was on the right build but Asus Sync and FC spooked me so I relaoded the 3.1 zip and flashed back. All apears well.
Any ideas just what the heck caused all the FC?

skeeterpro said:
Started the process to root (had flashed the 3.1 update). Loaded .9 to uSD and flashed down to 8.2.3.9 all went well. Upon boot started getting all sorts of FC (acore). Noted in About Tablet I was on the right build but Asus Sync and FC spooked me so I relaoded the 3.1 zip and flashed back. All apears well.
Any ideas just what the heck caused all the FC?
Click to expand...
Click to collapse
Corrupted update files? Maybe you needed to do a hard shutdown and start it again. I would've just rooted it right then and there. ASUS sync crashing doesn't affect adb.

Funny you mentioned that because and the 3.1 was installing I thought the same. Hard shutdowns can work miracles at times. I might just grab another copy of .9 somewhere and use that one (presuming I can locate one...I hear Asus has taken old firmware versions down...or at least the ones that can be rooted). dang.
thanks

skeeterpro said:
Started the process to root (had flashed the 3.1 update). Loaded .9 to uSD and flashed down to 8.2.3.9 all went well. Upon boot started getting all sorts of FC (acore). Noted in About Tablet I was on the right build but Asus Sync and FC spooked me so I relaoded the 3.1 zip and flashed back. All apears well.
Any ideas just what the heck caused all the FC?
Click to expand...
Click to collapse
Did you wipe the data (factory reset) after downgrading to .9? I did the same procedure, and got the same FC. Factory reset it and no more FC. I think Asus doesn't wipe the data folder when it upgrades, thus some of the 3.1 apps were still trying to run on 3.0.1.

tom0927 said:
Did you wipe the data (factory reset) after downgrading to .9? I did the same procedure, and got the same FC. Factory reset it and no more FC. I think Asus doesn't wipe the data folder when it upgrades, thus some of the 3.1 apps were still trying to run on 3.0.1.
Click to expand...
Click to collapse
when I downgraded from 3.1 to 3.0.1 I had to factory reset to get rid of the FC's

bbilko said:
when I downgraded from 3.1 to 3.0.1 I had to factory reset to get rid of the FC's
Click to expand...
Click to collapse
Good point. Will keep that in mind. Will search forum to refresh exactly how factory reset is done.....just to be safe!

skeeterpro said:
Good point. Will keep that in mind. Will search forum to refresh exactly how factory reset is done.....just to be safe!
Click to expand...
Click to collapse
Don't have my tablet on hand, but I believe it's Settings -> Privacy -> Factory Reset

Related

New 3.2 update bootlooping?

OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
wingnutta said:
OK, weird one this. Downloaded the update with no issues, it installed ok, it went to android recovery and then rebooted after a few mins into my homescreen. All good! - Then after about 5 seconds it said shutting off.. it then went through the whole updating procedure again. Ok no probs i thought, it needs 2 reboots.. fine.
However it has now done this 5 times!! and counting..I guess thats not right.. so how the hell do i stop it? lol
edit: managed to get quick view of "about tablet" and its still showing as 3.1 so the update is not applying.. i wonder why?
Click to expand...
Click to collapse
Are you rooted? That would be why. It's not advisable to accept an OTA update when your system has been altered. Unlocked is ok, just not rooted/modded.
If you are rooted and have a nandroid backup from before the update, try to restore from there. If not, boot into fastboot and restore to your model's original stock image (from motodev) then let the OTA updates bring you up to 3.1 and then 3.2. Re-install CWM Recovery, and re-root after that with solarnz' Universal Xoom Root and go from there.
If you're not rooted and your system is just continually rebooting, you should still try the fastboot/restore stock images procedure. There may be something easier, but I'll let someone else advise you on that.
Good luck!
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
wingnutta said:
Appreciate the help. No i am not rooted but i certainly dont want to restore a stock image as i will lose everything! Its nothing that cant be restored but why should i go through the hassle after accepting an OTA update if it doesnt work!
Currently now on my 16th reboot! - Getting fed up now...
Any ideas on how to apply this update ok?.. or at least stop it! lol
Click to expand...
Click to collapse
I can't think of any way to resolve this that doesn't involve a wipe of some kind. Have you checked any other Moto/Xoom forums to see if anyone else had the same problem?
My condolences on the irritating situation and the potential loss of your stuff. Actually, a good reason to root is that you can back everything up!
Well i took the plunge and wiped by unlocking. Cured the bootlooping (obviously), and so then thought - why not root aswell
All done and running Tiamat 2.2 and very happy!
Appreciate the help peeps..

[Q] Getting new TF700T - best way to get JB optimized?

I'll likely be purchasing a new TF700T and Dock today, probably at Best Buy (they've indicated they'll match Amazon and such). I doubt it will have JB onboard, so will need to do the update.
Since I'm starting completely fresh with this device, I imagine the update is the first thing I'll do, so will have no data or other files, settings, etc. for me to worry about. But I've read here that some have needed to do a cold boot or a factory reset to get things working right with JB.
So - what is the optimal way for me to get my new Tablet working best with JB? Just do the update and get started, or a cold boot and/or factory reset after the update is done? Any particular steps or actions that need to be taken?
Thanks for the help.
I just did the update without having to factory reset and/or cold boot.
rndmnss said:
I just did the update without having to factory reset and/or cold boot.
Click to expand...
Click to collapse
Thanks. I was also researching this at transformerforums.com and they have a protocol recommended to minimize the potential for problems, which includes a cold boot before and after updating the OS, as well as a Factory Reset as the final step. It sounds like possible overkill (although not harmful), and was just wondering if there were any consensus about an optimal way to do this for a brand new device.
Thought I'd get a "second opinion" here.
I did the update and then did a cold boot. No factory reset.
*shrugs*
On windows you reboot your pc after an install. (Usually. I never do...)
On Android you do a cold boot. It's the same process, except a regular restart on Android doesn't empty the memorycache.
DLCPhoto said:
Thanks. I was also researching this at transformerforums.com and they have a protocol recommended to minimize the potential for problems, which includes a cold boot before and after updating the OS, as well as a Factory Reset as the final step. It sounds like possible overkill (although not harmful), and was just wondering if there were any consensus about an optimal way to do this for a brand new device.
Thought I'd get a "second opinion" here.
Click to expand...
Click to collapse
Out of curiosity, what build number for your tablet??
buhohitr said:
Out of curiosity, what build number for your tablet??
Click to expand...
Click to collapse
Just bought it a couple of hours ago. Not sure exactly which numbers you're asking for, but here's what it says:
Build # JRO03C.US_epad-10.4.4.16-20120927
Plugged the Tablet in, it booted up and very quickly advised of a Firmware Update. I allowed this to proceed, but this wasn't the JellyBean update. The only setup I did was allow it to connect to my WiFi network.
I then checked Settings, System Update, and that's when it downloaded and did the JB update. Everything went smoothly. No problems.
So far I haven't done any cold boot or anything out of the ordinary. Guess it wouldn't hurt to cold boot now before I start testing it out.
DLCPhoto said:
Just bought it a couple of hours ago. Not sure exactly which numbers you're asking for, but here's what it says:
Build # JRO03C.US_epad-10.4.4.16-20120927
Plugged the Tablet in, it booted up and very quickly advised of a Firmware Update. I allowed this to proceed, but this wasn't the JellyBean update. The only setup I did was allow it to connect to my WiFi network.
I then checked Settings, System Update, and that's when it downloaded and did the JB update. Everything went smoothly. No problems.
So far I haven't done any cold boot or anything out of the ordinary. Guess it wouldn't hurt to cold boot now before I start testing it out.
Click to expand...
Click to collapse
OK, you already on JB. I thought you maybe lucky and still on .26, then I would recommend to save your bootloader with NVflash. Back to cold boot, if you have issue then you could try cold boot or worst case factory reset, but if you don't, it's not needed. This had happened to me after upgrade to JB, I did a cold boot and my table started to have randomly rebooted and blank screen issue.
buhohitr said:
OK, you already on JB. I thought you maybe lucky and still on .26, then I would recommend to save your bootloader with NVflash. Back to cold boot, if you have issue then you could try cold boot or worst case factory reset, but if you don't, it's not needed. This had happened to me after upgrade to JB, I did a cold boot and my table started to have randomly rebooted and blank screen issue.
Click to expand...
Click to collapse
So far so good. Just plugged in my Seagate 7200 RPM Expansion Portable HD, and it was recognized without problem. That's a big thing for this to work for me as hoped!

[Q] ASUS TF101 reboots, bootloops, tried reflashing

I'm at wit's end here. My TF101 will not stop rebooting. it doesn't matter what firmware I have on it (stock rooted, stock UNrooted, CM9, Frozn). it just reboots. the majority of the time it goes into a boot loop, or, if I'm lucky, I'll actually get to the homescreen for about five seconds, then it reboots. I just tried flashing the stock rom again. can't even get to the welcome screen now. I Never had this problem until I downloaded a firmware update (for stock ROM)
Using Rogue XM Recovery 1.5.0 (cwm doesn't want to work, for some reason)
S/n: C10KAS158799
When you flash between firmware, are you wiping cache, Davlik and doing a factory reset?
Go back to stock using easyflasher. It'll wipe your device clean, so make sure to back up important data. Then start over. I suggest Fred's guide over at transformeforums, it's the most complete one out there.
frederuco said:
When you flash between firmware, are you wiping cache, Davlik and doing a factory reset?
Click to expand...
Click to collapse
Tried that. Still boot-looping. nothing I do seems to help. so far, I've had the most luck with Frozn. CM9 nor the Stock asus firmware seem to work at all anymore. apparently the recovery is borked too. anytime i try to wipe something, It freezes.
am I just SOL?
(edit) alright, so I tried it again. instead of boot-looping, now it just sits at the Eee pad screen forever
I would try using TWRP instead of Rogue. Never had an issue with Rogue myself, but TWRP is better IMO.
You can use EasyFlasher to push it in APX mode, or use ADB shell and push it using the dd command (see the terminal method here: http://www.teamw.in/project/twrp2/109)
frederuco said:
I would try using TWRP instead of Rogue. Never had an issue with Rogue myself, but TWRP is better IMO.
You can use EasyFlasher to push it in APX mode, or use ADB shell and push it using the dd command)
Click to expand...
Click to collapse
Treid TWRP. wiped everything (Dalvik, System, factory reset, Cache) and flashed stock rom. still rebooting.
Des0late Law said:
Treid TWRP. wiped everything (Dalvik, System, factory reset, Cache) and flashed stock rom. still rebooting.
Click to expand...
Click to collapse
Did flashing the stock ROM replace TWRP? It should have...
frederuco said:
Did flashing the stock ROM replace TWRP? It should have...
Click to expand...
Click to collapse
It did. Now I can actually get into the OS for awhile, but it still reboots randomly (and bootloops, although not as often). I've been doing some googling. apparently the reboot/bootloop problem Is ICS based (or so some think) and, to be honest, I didn't have any problems with it before I updated from Honeycomb. that being said, someone wouldn't happen to have a spare honeycomb ROM lying around, would they? google (oddly enough) turned up nothing, and Android Revolution just leads to dead links...
Edit: never mind, someone fixed the links. will try 3.2 after I get home from work.
IMO if you are getting RR and SOD on a fresh stock install with nothing installed, it is probably a hardware issue with a failing chip on one of the boards. If it is still under warranty you may want to try to return it for repair.
Well, I haven't had the SoD issue, just reboots. I was able to use it most of the day yesterday, before I shut it off myself. It turned on fine this morning, too (rebooted once).
Sent from my LGL75C using xda app-developers app
frederuco said:
IMO if you are getting RR and SOD on a fresh stock install with nothing installed, it is probably a hardware issue with a failing chip on one of the boards. If it is still under warranty you may want to try to return it for repair.
Click to expand...
Click to collapse
Alright. So, I flashed it back to Honeycomb. Haven't had a reset or reboot all weekend. I guess the problem WAS ICS-based. Can't figure why, though.
only downside to that is, can't use some apps on the market. oh well, I'll live!

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] Forgot to factory reset before CROMi-X 5.2a

Hi
Recently installed CROMi-X 5.2a on my TF300T. Stupid as I was I missed to do a factory reset first. The installation went fine and the system is up and running with CROMi-X. But am I missing out on something now that I did not factory reset first? All my applications working as before as far as I have seen was a little stunned at first seeing all my apps being left untouched.
Should I do a factory reset and do the installation again to get the benifits from CROMi-X or does it not matter as long as it is working without problem?
Any input is welcome
Grettings from Sweden
Boddington1900 said:
Hi
Recently installed CROMi-X 5.2a on my TF300T. Stupid as I was I missed to do a factory reset first. The installation went fine and the system is up and running with CROMi-X. But am I missing out on something now that I did not factory reset first? All my applications working as before as far as I have seen was a little stunned at first seeing all my apps being left untouched.
Should I do a factory reset and do the installation again to get the benifits from CROMi-X or does it not matter as long as it is working without problem?
Any input is welcome
Grettings from Sweden
Click to expand...
Click to collapse
If you run into app permission problems or random force closes, then it is advisable to factory reset. If everything works fine, then I see no need to.
cmendonc2 said:
If you run into app permission problems or random force closes, then it is advisable to factory reset. If everything works fine, then I see no need to.
Click to expand...
Click to collapse
Thank you cmendonc2
Yeah dirty flashing is fine usually :good:

Categories

Resources