My Transformer notified me this morning of a MobileDock update, but it doesn't successfully install. Gets to about 19% then it tells me 'The hardware keyboard will not work before updating mobiledock firmware successfully. Try Again?' with an 'Ok' and 'Cancel' button. If I hit 'OK' to try again it retries but fails and gives me the same window.
Is it because of CWM/Root that it won't install properly? I've read android ota updates won't install because of CWM and my thinking is MobileDock update may have the same issue.
Is there a way to install it while retaining root and CWM?
Related
Hello. Last night I finally unlocked Infinity. Now, odd things are happening. Gmail quit sending, they just stay stuck in out box, stock browser keeps disappearing, I have to restore with TB, and, Wifi indicator stays grey now instead of blue. Several other odd glitches, too. I did factory reset, I tried re installing nandroid, and cold boot. Doesn't work. Any ideas?
Oh. I forgot strangest thing. An OTA downloaded last night before reset, and this morning it downloaded again. Keeps prompting me to update. Its the newest JB firmware. Didn't think I was supposed to get anymore.
redheadplantguy said:
Hello. Last night I finally unlocked Infinity. Now, odd things are happening. Gmail quit sending, they just stay stuck in out box, stock browser keeps disappearing, I have to restore with TB, and, Wifi indicator stays grey now instead of blue. Several other odd glitches, too. I did factory reset, I tried re installing nandroid, and cold boot. Doesn't work. Any ideas?
Oh. I forgot strangest thing. An OTA downloaded last night before reset, and this morning it downloaded again. Keeps prompting me to update. Its the newest JB firmware. Didn't think I was supposed to get anymore.
Click to expand...
Click to collapse
Probably the best bet now is try to do a factory reset(do it twice) and manually reflash the full stock firmware.
buhohitr said:
Probably the best bet now is try to do a factory reset(do it twice) and manually reflash the full stock firmware.
Click to expand...
Click to collapse
How would I re flash full stock firmware? I was trying to flash clean ROM last night, but kept failing. I don't have the newest firmware, just the original JB update. Using TWRP
I probably start by downloading from Asus, what steps after that? Think I was screwing up last night.
redheadplantguy said:
How would I re flash full stock firmware? I was trying to flash clean ROM last night, but kept failing. I don't have the newest firmware, just the original JB update. Using TWRP
I probably start by downloading from Asus, what steps after that? Think I was screwing up last night.
Click to expand...
Click to collapse
========= Recover /Downgrade from Jelly Bean to ICS/Clean Factory Restore with custom recovery =========
1) Download the latest firmware from Asus site
2) Extract the .zip file somewere on your desktop
3)Rename the file to something like "recover.zip" uploade it to the root of your MicroSD card
4) Insert the MicroSD card in your tablet and use this button combination to Power ON and go to recovery -->
Start the tablet by pressing Volume Down and POWER togheter for 5 seconds ,a message will inform you that you have 5 seconds to enter the recovery,press Volume UP before the 5 seconds expire
5) From the recovery menu press Install and select the "recover.zip" file ...wait until the install process ends and then restart your device.
I'm trying to figure out what I did wrong when upgrading my TF300T, and how to possibly fix it.
I installed an unofficial nightly build of CM10 back in early August (before the official builds of CM10 for the TF300T were out), with CWM recovery. That ran mostly fine - the occasional lock-up and reboot, but not too bad. Recently, though I wanted to upgrade to the most up-to-date stock firmware (10.4.2.17, US version). I downloaded the firmware from ASUS's site directly to the tablet, and after some aborted installs (due to an un-extracted .zip file... derp) I got the new firmware to install.
Now, however, the device only boots to the brushed-metallic ASUS logo and puts up a spinny dot-thing ("working..." indicator) and gets stuck. I even left it plugged in overnight and it didn't budge from that screen. Also, when I do the key combo that used to take me into recovery, it now gives me the boot option menu - RCK, Android, USB device, and wipe data. Trying to boot RCK gives me the clockwork mod android on his back with an error sign above, so obviously that's screwed up. However, the bootloader seems intact. Any pointers on how to fix this?
EDIT: OK, fixed. I just had to wipe data and it booted properly on the next reboot.
I had recently rooted my Google Nexus 5 and I had an update for it (The 5.0.1). My bootloader is also unlocked. I have followed the instructions, downloaded the update where the file size was 13.3MB and my device had restarted and started to install the update where the android icon had appeared with the spinning settings icon. When the bar was a quarter, it asked me to 'Install Untrusted Package" and I selected the "Yes - Install untrusted zip" using the volume key and lock button. It had then popped up with something like this: "Root access possibly lost. Fix?" and I had selected the "Yes - Fix root (system/xbin/su). My phone had then restarted and loaded up like it normally does. I then went into my settings to see if the update was installed through the "About phone" in settings. The Android version was still 5.0 and nothing had changed. What do I do?
Sir,
Please wait until mods will move this thread to the device specific forum.
For reply or more questions please register an account on XDA forums.
Stand by
Good luck
XDA Visitor said:
I had recently rooted my Google Nexus 5 and I had an update for it (The 5.0.1). My bootloader is also unlocked. I have followed the instructions, downloaded the update where the file size was 13.3MB and my device had restarted and started to install the update where the android icon had appeared with the spinning settings icon. When the bar was a quarter, it asked me to 'Install Untrusted Package" and I selected the "Yes - Install untrusted zip" using the volume key and lock button. It had then popped up with something like this: "Root access possibly lost. Fix?" and I had selected the "Yes - Fix root (system/xbin/su). My phone had then restarted and loaded up like it normally does. I then went into my settings to see if the update was installed through the "About phone" in settings. The Android version was still 5.0 and nothing had changed. What do I do?
Click to expand...
Click to collapse
It sounds like you are using a custom recovery. You can't flash an OTA unless you have the stock recovery and are 100% stock - literally NO changes to /system are allowed in Lollipop
Hi guys.
Im hoping someone has a clever fix to my problem.
Version: FLD-L09C432B131, rooted and with TWRP.
Issue:
I took a plunge into the updating sea and installed B360. Never thought it would go through since I didnt unroot first. Well, it actually worked and the phone booted fine. The "About" part listed the new version but I was still on decembers security patch. So I ran Firmware Finder and started with the small file, 230MB or something. Unpacked it and moved to dload via the menu in FF.
Now the problems began. Phone booted and ran the update without any noticable issue....until it was time for a reboot.
It now only boots into Huawei eRecovery with the options to:
"Download latest version and recovery" - Which fails after connecting to wifi and trying to download from huawei.
"Reboot" - Just returns to eRecovery.
"Shutdown" - self-explanatory.
The devices does show up for a few seconds in ADB when it reboots and is connected to my PC. But not for long.
I was hoping to be able to flash TWRP with ADB but its kinda hard when it doesnt stay connected.
Anyone wise out there with some input?
Much obliged.
/nort
Ok update.
I managed to get adb to work finally by timing the seconds the phone was actually visible to the computer. A reset back to B131 and now im on B360. Not sure if i have the latest version with the battery fix but I guess that will be obvious soon enough.
Hi guys,
I have not received the November update, and I always received latest security patches on the day of release, so it was strange to me.
Tapping the "Check for updates" button shows no update.
I've been suspicious so I booted into bootloader and it greeted me with an error: "ERROR: OPERATION DENIED".
However, this only happens when I boot into bootloader the first time from booted phone. Every other time the error is not there. I'm not sure if that's the cause of the update not coming, but my gut feeling tells me that.
Current system I'm running is October 5th and I've flashed that via PC since I've had an unlocked bootloader + root after which I've re-locked it and wiped the phone so it's been completely clean.
I've tried to flash it manually via PC without wiping the phone but cmd throws me an error saying some versions are not compatible.
My questions would be:
- has anybody had this error thrown in the bootloader? Since Google didn't really help me
- could this be the cause of the update not coming?
- is there a solution apart from a wipe?