Problems with 3.2 - Xoom Q&A, Help & Troubleshooting

I restored my Xoom to stock 3.0.1 with the device locked, and update to 3.1 OTA. I then unlocked, flashed CWM (latest), and installed the 3.2 rooted. I am now having problems, and I'm not sure if they're from a bad update. I also installed the deodexed update.zip a little later, but it didn't solve the problems.
My keyboard click sound is very quiet. I can't hear it unless the room is completely silent.
My lock settings sould not stick until I rebooted. Tried setting a PIN and disabling visible passwords.
My keyboard doesn't function correctly. Auto caps works, but auto punctuation and auto correction are completely broken.
Input from a USB keyboard is very laggy in the browser.

70 views... is this common or isolated? Need to know if i should go back to 3.1 or just do a reinstall.

I boot looped the first two times I installed 3.2, (yea I erased EVERYTHING first) then on the third try it worked like it should. Try to reload it again, it worked for me.

Related

[Q] hw to unroot asus tf slider ??

Please help me to unroot my asus slider , i want to my tab is back to basic ( official)
What i did was most likely risky but worked nonetheless had kinda a similar problem.
Make sure you have cwm recovery installed and download the "old" update from the asus website. Put the zip on the sd card and install this with cwm recovery.
After its done your back on an older firmware completely stock from what i know this is risky so try on your own risk. It worked for me but when it was booted into honeycomb the launcher keeps crashing what i did was to solve this was keep tabbing away at the bottom right so that menu slides out and quickly tab wifi, if done right you enter settings and launcher stops bugging you about its crashes, then goto OTA update and apply the latest update after this is done slider will work fully no weird launcher crashes and from what i know your back to full stock as it came out the factory.
I rooted mine with this link
http://forum.xda-developers.com/showthread.php?t=1173230&highlight=slider
It was easy!

[A700] Removing Update for _FR Version

Hi, I have rooted mz Device and installed the Version Acer_AV043_A700_RV23RC04_EMEA_FR via the Thread "Update while rooted". So far so good. Update works well. .but since this update,my touchscreen is just a disaster. Writing is nearly impossible. I have to touch up to 3 sec. to mark a letter. I checked the settings and the touch sensitivity is already set to high. I installed the app "touch Screen Tune" but it dont really helps. Corners at the Screen are almost "dead". So anyone an Idea? I think about to remove this update, but dont know how... thanks for any Idea
I posted instructions on how to go back to stock (using all the posts from the dev area.) If you download the right FR ROM, you should be able to take yours to pre-update stock system. After it is back to stock you could re-unlock and re-root. I've done this twice now and it has worked both times.
http://forum.xda-developers.com/showthread.php?t=1829577

Challenge: Figure out why I can't get 100% restore to stock

I have a challenge for the group.....
I have a GT-N8013 that I was running Darkman's N8013 Rooted / Deoxed/ BusyBox ROM. When I applied his latest update, I lost the ability to autoswitch between the handwriting and standard Samsung keyboard based on pen auto detection (it worked fine prior to the last update).
Playing around to try to get it back I installed the Android Revolution HD 7.0 ROM and the pen auto detection worked again.
Now, I'm trying to get back to the latest stock ROM. I installed CWM, wiped all mounts, wiped the internal SD card, wiped Dalvik and cache and checked permissions. I then used Odin 3.07 to install: N8013UEUCMD3_N8013XARCMD3_XAR which appears to be the latest April stock firmware. Went back through setup and still no pen auto detection.
Since it works on the HD 7.0 ROM, it's clearly not a hardware issue. Makes me think there was something in the last Darkman's ROM that glitched on my tablet (no one else seems to have the issue). Not sure why my wipe and install wouldn't have cleared everything out but it appears that is the case.
Open to any and all ideas/suggestions to see if I can get that feature back since it's a critical piece in how I use my tablet.

[Q] Which unlock tool to unlock v4.1.1?

Hello I am still dealing with a weird problem that I posted on this forum over a year ago that was never resolved. Basically my tablet is stuck running Android version 4.1.1 (Build JRO03C.US_epad-10.4.4.25-20121228) because if I upgrade to any new versions (whether I do it as OTA or via micro USB) my wifi card stops functioning (it does not see any networks). Anyways I even went so far as to RMA it and Asus said they fixed it, shipped it back to me, but in reality all they did was roll me back to 4.1.1, saw the wifi was working and shipped it back to me saying they "fixed" it. Well of course the second I got it back I installed the OTA and wifi broke again... So I just rolled back to 4.1.1 and said screw it, I just won't update it anymore. Well this week I figured I'd try installing the latest OTA and hoped that this version would not kill my wifi, unfortunately the same exact issue has occurred and thus I have once again rolled back to v4.1.1 and my wifi works perfectly...
TLDR; Anyways apologize for the rant/story but basically I am stuck with using version 4.1.1 of Android and am considering flashing a custom rom to try and resolve some issues I am having with the stock rom's wifi, however the official bootloader unlock tools only say they work on version 4.0 (ICS) or version 4.2 (JB). I'm stuck on v4.1.1 so which tool should I use (or am I out of luck)? Thanks
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
berndblb said:
v7 worked your JB version, but I think v8 will work as well. Just try them both - it's just an app. Either it works or not....
But that is the weirdest thing I've heard in a while (reg. WiFi).
What have you done on your router side? I cannot believe this is a problem with the tablet's wifi card.
Is this 'wifi not working' consistent on any router, any network?
Did you reset the router, change the channel?
Do you have possible interference: microwave, bluetooth speakers, bluetooth enabled or any other device that uses radio waves anywhere in the vicinity of the tablet?
Click to expand...
Click to collapse
Thanks appreciate the reply - I just wasn't sure if using the wrong unlocker could brick my device... I'll give 8 a try first then 7 if necessary. The ironic part is that it requires a network connection to complete the unlock operation (I guess so Asus can cross your S/N forever off of their list of devices under warranty).
I agree that this is a strange problem as I have not seen anyone else report it. Basically I tried resolving this about 13 months ago with the help of this board and as mentioned I finally had to RMA it, but ASUS just rolled the version back instead of fixing anything and at that point I just wanted to enjoy using my tablet more than I wanted to fight with ASUS's customer service reps who effed up the first RMA job (the language barrier was also apparent in my interactions with them)...
Since over a year has gone by since the last time I tried an OTA, I hoped that the latest update would not have the same issues but alas, I'm not that fortunate.
As far as what I've tried - I have tried connecting to different networks and changing router channels and checking for interference, but the thing is, I'm quite certain the problem is with the tablet. When I first had the problem I lived in an apt building where I could 'see' 10+ wifi networks at any given time on all different channels with different routers/security settings etc. As soon as I applied the OTA the tablet could no longer 'see' any of them (even as I sat with my laptop/phone connected to wifi right next to it). I now live in a house (and have a different ISP, and a different router) and tablet works perfectly when on version 4.1.1. I don't have as many wifi networks visible from my house, but can still see a few of my neighbor's wifi networks both on the tablet (v4.1.1) and on other devices. But the second that I upgrade, all of them disappear from the tablet's view (but continue to be visible/work on other devices). I have turned wifi on/off, turned airplane mode on/off, tried connecting via wifi direct, rebooted, cold booted, booted into recovery, factory reset all data, etc. but nothing works because the tablet cannot see any wifi networks. And the second that I rollback to version 4.1.1 the wifi works perfectly... I have upgraded and rolled back probably at least 6 times and it is always the same result.
I do also get another weird side affect when I upgrade - the tablet refuses to turn off when I'm on any version higher than 4.1.1. So if I press "Shut Down", the tablet displays "shutting down" and the screen goes black and becomes non-responsive (as do the buttons, just as you would expect when turning off), but it does NOT actually shut down because if I come back 30 mins, an hour, 2 hours later I can feel it running very hot. The only way to truly shut it down is to let the battery drain...
So maybe a better question on my part would have been, do you think installing a custom ROM will even help resolve this issue? Or should I continue using 4.1.1 and not risk making the situation worse with custom ROMS?
WiFi problems are often kernel related..... Did you always take the update OTA?
Did you ever try to flash the latest firmware version manually? OTA updates do go wrong sometimes....
Although repeatedly???? It's weird. Maybe the server your tablet pulled the OTA from hosts a bad copy????
If you do not want to unlock, manually flashing the firmware would be one thing to try. OTA's patch the existing system, replace old files with new ones where necessary. Manually flashing the firmware replaces everything - a totally new installation of everything: bootloader, recovery, kernel, system and data.
But you cannot make it worse by flashing a custom rom. You unlock, flash a custom recovery (which does not change anything else on your system), then you make a nandroid (backup) of your current 4.1.1 system before you flash a rom. So you would always be able to go back to where you are now. On a custom rom you could even try out different kernels, which often are the root cause of wifi problems..
The thing is: If you want to flash a current custom rom like CROMi-X, based on Asus JB 4.2.2, or CROMBi-KK/CM11 which are KK roms, you always have to update your bootloader first. Your .25 bootloader is too old for any current rom.
You can easily do it once you have a custom recovery installed, but even easier would be to update to the latest Asus firmware 10.6.1.14.10 (after unlocking), then flash the custom recovery (TWRP 2.8.1.0), then flash a rom of your choosing.
Downside of this route would be you wouldn't have that 4.1.1 nandroid I mentioned earlier.....
Nahhh - thinking about it, I would recommend you go this route:
Unlock,
flash an older version of TWRP compatible with your current bootloader (TWRP 2.6.1.0 is ok)
make a nandroid of your current system
do a full wipe of cache, Dalvik and data in recovery
flash the 10.6.1.14.10 bootloader in recovery (I can talk you through it)
flash TWRP 2.8.1.0
flash a rom of your choice
Check out my guide, link in my signature, and let me know if you have questions
Thanks - I was able to successfully unlock my device with v7 of the unlock tool (v8 wouldn't even install). Thanks too for the advice on how to flash a custom rom safely. I've never flashed a custom rom before (have rooted a different android device before tho), so I appreciate any help.
I downloaded the blob file for TWRP 2.6.1.0 from here (techerrata.com/browse/twrp2/tf700t), but not sure how to proceed next, (also I don't see a link in your signature to your guide, but I am running a bunch of script blocking addins so maybe that's why) seems like all the guides I am finding say I need to get a copy of a fastboot program (but don't provide links), where can I find that? Again, I appreciate the help.
Sorry, my bad, I don't have a signature on XDA - wrong forum. LOL
My thread is here: http://forum.xda-developers.com/showthread.php?t=2688891
Ask any questions you may have in that thread, but it should cover your questions - I hope

Note 4 Dreadful unusable performance!

Hi Guys,
Hopefully this is in the right section
I have a Note 4 SM-N910G and its just turned absolutely useless since I factory flashed it. I have rooted it before and bricked it and un bricked it before so have some experience with it. I recently wiped my phone and did a firmware restore using Samsung Kies and since I did the phone is absolutely useless. It started out fine for an hour or two and now it lags by like a minute with any action, even trying to bring up the keyboard when typing. It will reset itself, lock itself, crash, just un useable. I've tried reflashing it again stock a couple times and still the same everytime. It went from perfectly fine to dreadful with the original mentioned restore. I did just recently get an error code of "sbl1 partition doesn't exist" in Boot recovery mode.
Does anyone know if this is fixable and not a hardware issue?
Should I try and just root it again and flash a non-oem rom? (I havent had the time to do it recently)
many thanks,
Tekkado
Hi Guys,
Also I should add that when I was rooted the phone was fine but when i went to unroot through super user the phone was still functioning as though rooted and I couldnt download software updates because my device was "modified".
So thats when i just flashed stock firmware and again now flashing through odin aswell it proceeds fine then the device will say installing updates and then give a no command error or seandroid not enforced. Everytime is basically a different message.
How can I just wipe everything and get back to stock?
Thanks
So to add to this is there any relationship between the firmware running and the bootloader? I just realised that before i tried to flash stock firmware i was rooted and didnt un root via superuser because in the past that did jack all.
I flashed dr. ketan rom this morning and the phone was operating as normal very snappy but as soon as i downloaded a new app from the play store (reddit and chrome) again it turned to absolute crap.
Is there a disconnect here that i missing that can be fixed?
Thanks

Categories

Resources