I have downloaded the firmware update from ASUS, but I have absolutely no idea how to install it. Anyone know?
place it on the root of the /sdcard or on the microsd card if you have one, it should automatically pick it up and ask you to update.
the method is in the manual (iirc) and also on the support section of asus' website.
Now that I'm looking at more threads- is this update worth doing? Seems some people are having serious problems with it. Anyone find it to be very useful?
Before I upgraded, I was experiencing times where I'd have to double tap letters on the keyboard for them to properly register. After the update it hasn't happened since.
I also had some weird hangs and crashes when scrolling through my apps and homescreens, that also hasn't happened since.
Hey if you can't auto-update, check to see if you have a serial number. settings/about/status I believe. I don't have mine in front of me. If you do not have a serial search serial number in the general section and read that thread. Ultimately it just says that the TFP is missing a couple scripts in the kernel and other portions of the system. It's best to return it for a new one. Mine had no serial # and a few other issues, so I returned mine and will be getting a new one tomorrow night.
Related
I've seen a lot of cross-posting between threads from people who are experiencing one of the various problems with the ICS update for the Prime, so I thought I'd provide a quick reference for people to find their particular malady more easily.
This isn't intended to be a list of any ol' thread discussing lag, strange app behavior, or "slightly better/worse" wifi/GPS/BT performance after update, etc; but actual, show-stopping, deal-breaking, tablet-bricking problems that we are either waiting on a solution from Asus, or have a workaround ourselves.
1. "Unknown" Serial number - these people have an otherwise working tablet with a valid serial number sticker, but the About screen shows "unknown," so they aren't able to get the OTA push.
Thread: http://forum.xda-developers.com/showthread.php?t=1426881
2. Ugly, ugly lines appearing on the screen after ICS update; some worse than others.
Thread: http://forum.xda-developers.com/showthread.php?t=1437280
3. People getting an "Update failed" message after downloading and applying the ICS OTA update, regardless of whether they had rooted their device in Honeycomb beforehand. (Good news, it looks like there's a work-around for this!)
Thread: http://forum.xda-developers.com/showthread.php?t=1437285
4. People (like me) who downloaded and installed the ICS OTA "successfully" except for the fact that it boot-loops, freezes on boot, or boots successfully only to freeze and reboot after a brief period of usage.
Thread: http://forum.xda-developers.com/showthread.php?t=1437392
The fact of the matter is that the vast majority of folks are having a great experience with their Prime; a very small percentage of people are experiencing the issues above, but they are no less valid. We are trying to get an idea of the scope of each problem, so it's helpful if people are posting in consistent threads for each.
If there are any other major issues I'm missing/forgetting, let me know and I'll update the OP with a description and a link to the thread.
Unable to wifi tether
I was able to update and use the tablet without any issues at all. I had a few lock ups but usually only happens opening an app once (ie. gallery, movie etc) after it recovers then it does not lock up again.
Biggest gripe: Lost wifi tethering.
Losing wifi tether is no trivial thing, I agree - though at least you can use your tablet. =) Still, that is a hot issue and the thread is rather large.
Thread: http://forum.xda-developers.com/showthread.php?t=1438297
I guess I'm still the "one-off". I want to put it here in case someone else sees it and has the same problem.
For the most part, everything seems fine if I'm not docked. But I have big lags going in and out of some apps (especially Google+ when I want to view people's pictures the screen is just sorta blank, no spinning wheel or anything) and also going in and out of the app drawer.
Biggest problem - if I am docked, at some point the screen goes black. And it will not power on at all unless I remove the tablet from the dock and do the volume+power trick to turn it on. This didn't happen until the ICS update.
When it is working right, it is fantastic! Thankfully that is most of the time.
Hi all,
I have a serious problem with my Asus Transformer Prime. Yesterday a new update came and I installed it. Since then I can't get passed a security screen to slide and unlock. I have really no idea how to solve this and I am getting really desperate right now, since all my notes from work are in there!
My tablet is rooted and I am using SwitchMe so both my gf and I can use it. Now I am stuck in my gf profile and a can't do anything. No matter how many times I retry slide and unlock. Nothing happens.
I made a video so I can explain the problem a bit better.
youtu.be/iFIpojRJZDI
Try a post in the developer's thread http://forum.xda-developers.com/showthread.php?t=1478326 ?
good idea... I will do that, although I am not sure if Switchme is the problem.
Finally, my problem is solved!
The issue was indeed SwitchME. I unistalled SwitchMe with ADB. Then everything worked back as a charm. After that I regained my root with rootkeeper and reinstalled SwitchMe. No profile data was lost, so one happy Asus Transformer Prime user here.
If you have any serious problems like this you really should just email us, its a considerably better idea than posting in forums.
You can find developer contact details on any app page in the Play Store.
I had the similar problem after upgrading my CyanogenMod on HP Touchpad yesterday.
Here is how to fix it:
- Connect via ADB
- Kill the switchme process.
Immediately after that, I was asked to give superuser permission for Switchme. After I confirmed this, the problem was solved.
So I guess that SwitchMe somehow looses the sudo permission during ROM upgrades...
(I posted the same information also to the main SwitchMe thread at http://forum.xda-developers.com/showthread.php?t=1465661)
I'm currently on the "old GB" firmware, and s-offed. But I want to know what exactly is in the "firmware"? Just the radio files? I would like to upgrade to the "OTA" firmware, but I'm not sure if I can just do it like we used to do with the Tbolt, or if I still have to go though the pimg98(sic) renaming and flash that way.
1454 said:
I'm not sure if bootloops is the correct term, as it never actually reboots, it just goes straight to the boot splash gif, and stays there. It happens every time I open nav now. I did "flash" gnow, and that is the only big thing I have changed since the issue started occurring. Is anyone else having an issue with this, or is it just me? I searched bootloops for the rezound and *didn't* see any other thread started on the issue. But I could have missed, I apologize if this is a duplicate.
Click to expand...
Click to collapse
This will get you what you need to know: http://forum.xda-developers.com/showthread.php?t=1837316
Quick and dirty, uninstall updates. Go to Settings - Apps - Maps and select "Uninstall Updates" then jump over the Play Store and find Maps and make sure Automatic Updating is turned off, this will set you back to the ROM's default Map version. If your ROM is custom and doesn't have Maps preinstalled, just Google for Maps 6.9.2 and download the APK and side load it in, it should work fine.
EDIT: Oops, looks like you changed this post up since I saw it, sorry if this isn't relevant anymore.
Yeah, I didn't see the thread/s in the gen section, I just searched then posted. So, I thought I would ask another question since I couldn't delete it. Of which I have now found the answer to. Thanks though.
I have searched on phone issues and even messagebank... There was a post that seemed similar but not the same.
Unfortunately I can't say just where this issue came in; I only noticed it yesterday and, as mentioned in another thread, I have been trying out ROM flashing. My GUESS would be it has to do with flashing 'modem_CWM_I9300XXDLH7' but that is purely a guess because it is call related.
I have flashed a stock ROM, GT-I9300_XSA_1_20120710170916_9xjds9h0pm to install an Aussie ROM (phone from Kogan and was German model) and more recently flashed 'Kernel_CM10_20120820_Official_CWM' in preparation for trying a JB ROM. (I am planning on using 'I9300XXBLH4_Jelly_Bean_4.1.1_Clean_Stock_Rom_Nandroid_Backup' for a first try)
SO, phone seems to be working well; I managed to crash it (stuck on Samsung screen) but have backups that brought me back up to where I was without too many issues.
But, I noticed yesterday I got a Telstra Messagebank notification for a missed call/voice message. It says it came from +101 but when I click the notification it takes me to a Telstra recording saying the number is not connected. This used to work. Dialling 101 works just fine and I have looked to try to locate where the phone has decided MB is now +101 but can't find it.
It's not a biggie, and I figure maybe I need to call Telstra to get their info resent or something, but it is a little annoying to have to dial each time instead of just press the notification.
Any ideas of what to try? I'm about to flash the JB ROM so if that fixes it I will be back (hopefully without dramas ) soon. Thanks in advance for any suggestions.
XXBLH4 is a really old JB leak, flash XXDLH8 instead (DLH9 is newer but has a keyboard bug)
As for your problem, I don't know what to tell you but your carrier won't be able to help you as you have unofficial firmware on your phone and that may be the reason and they will only be able to assist you in regards to the official Telstra fw.
Is it really that big of a deal to dial 101?
Sent from my GT-I9300 using xda premium
Journyman16 said:
It says it came from +101 but when I click the notification it takes me to a Telstra recording saying the number is not connected. This used to work. Dialling 101 works just fine and I have looked to try to locate where the phone has decided MB is now +101 but can't find it.
Click to expand...
Click to collapse
that is a strange one. It seems as though it's trying to dial 101 as an international call (with that plus in front of it making it a call to USA number 01), when it should have picked it up as +61 101.
Out of curiosity, what does it come up with when you tap and hold on the SMS and go to "View Message Details"?
@nodstuff - The reason for I9300XXBLH4_Jelly_Bean was because, a. I found it and the file date was something like 25/8/12, and because the description said it has been cleaned up and all bloatware removed. I don't recall seeing XXDLH8 for download but I am new here... I was thinking along the lines of getting something known and stable for my first JB flash.
@Dinty - I don't get a 'View Message' option on a long tap, I get a menu with, Call +101, Send Msg, Edit numbr, Add to Contacts, Send Nmbr, Add to Reject list, Delete.
Further info just noticed - older call from MB (30/8 - prior to new Modem flash) came in as Int'l M'Bank with #101# so somewhere the MB number has altered.
I doubt Telstra will have an issue with the FW etc. It isn't their phone. I bought outright and would be speaking to a rep - IIRC when I got my Moto Defy from the dealer a couple of years back they had to send me a txt which I saved and it set up the Telstra info on the phone. Might be mistaken in memory of that though...
@nodstuff - do you have a recommendation for a XXDLH8 ROM to flash? I'm looking for stable with some optimisation and as clean of standard apps as possible. I've got an Apps backup in Titanium Pro that I figure I can use to put my new apps back.
Also, is the Keybd issue with LH9 itself or just with some ROM's?
thanks for the help...
Journyman16 said:
@nodstuff - The reason for I9300XXBLH4_Jelly_Bean was because, a. I found it and the file date was something like 25/8/12, and because the description said it has been cleaned up and all bloatware removed. I don't recall seeing XXDLH8 for download but I am new here... I was thinking along the lines of getting something known and stable for my first JB flash...
Click to expand...
Click to collapse
Well don't flash XXBLH4 so, its very buggy and not stable.
XXDLH8 is very stable and pretty bug free.
There are a few downloads for it (cwm flashable, Odin or an ota package. I suggest cwm or Odin method as the ota method is quite tricky.)
Sent from my GT-I9300 using xda premium
Journyman16 said:
IIRC when I got my Moto Defy from the dealer a couple of years back they had to send me a txt which I saved and it set up the Telstra info on the phone. Might be mistaken in memory of that though...
Click to expand...
Click to collapse
I believe you're talking about the automatic set-up service. I think this is what you mean:
http://www.configure.telstra.com.au/telstra/index.jsp
Not sure it will have any effect on that messagebank issue, but I suppose it doesn't hurt to try!
Dinty said:
I believe you're talking about the automatic set-up service. I think this is what you mean:
http://www.configure.telstra.com.au/telstra/index.jsp
Not sure it will have any effect on that messagebank issue, but I suppose it doesn't hurt to try!
Click to expand...
Click to collapse
Thanks for the link - that looks what I originally had to do over the phone, but then I didn't have a Telstra account set up at that point.Didn't work unfortunately. le sigh!
So, I am now the owner of a JellyBean phone, all working nicely and with my apps installed again. All went smoothly and I just chose my purchased and download apps from my titanium backup and Voila!!!
I took the advice and installed GT-I9300_WanamLite.XXDLH8.V3.0.RC4.NO-WIPE - I thought about the DLH9 version of it but saw a note in the thread about keybd issues, so, taking the advice above I DL'd the DLH8 version.
Only thing I have noticed so far is it seems a bit slow on the USB charging. Once it's at 100% I will disconnect and see if maybe power is draining too fast, then look at ways to improve battery.
Just did some trials of the MB issue and noticed something odd - if I try to create a Contact I am unable to enter numbers in the name field. I also tried to set up my mobile banking and using the app provided by the bank I cannot use numbers for my ID, even though it is an 8 number ID. The Keybd simply will not change to numbers until I go to the PW line - is this the keybd error you mentioned as being present in DLH9, nodstuff??
Hm... so I took a chance and flashed Wanamlite's keybd fix; the thread says it is for DLH9 but I figured what the heck, if it fails the phone I can easily reflash the ROM.
Seems to have worked. Gonna leave a comment over there about it because I seem to have noticed something not mentioned by others.
How's it going, everyone? I just want to apologize ahead of time if this is in the incorrect forum. There's so many to choose from and I didn't see one dedicated to this particular tablet.
I recently acquired a Verizon Ellipsis 8 and the first thing I wanted to do with the device was root it. After trying what must have been 10-15 different methods, I was finally successful at getting the device rooted using a (What I assume to be) Chinese root method called Kingroot. They had support for the tablet and actually got me root access, so I went with it. Shortly after, I installed all my necessary root apks and got the device working in what I would describe as acceptable order. I then began hunting for custom ROMS for the thing, but if there was one thing harder to find for this tablet than root access, it was a custom ROM.
Anyways, I've been living quite happily on rooted stock. I removed all the unnecessary bloatware from the device and everything has been going smoothly, until a few days ago. Verizon pushed out an OTA update and now I am receiving daily prompts from Verizon to update to the latest firmware. Now, this isn't my first rodeo when it comes to dealing with OTA updates, so I began digging around inside my system files to find the update.zip and disable it, as well as remove the different processes that would possibly be spamming this update notification. After several different files given the .bak extension and several different reboots, I felt comfortable that I had taken care of the issue. Hell, I even went so far as to take the same steps on my wife's tablet (She has the same one, rooted in the same fashion), and HER tablet has stopped sending her updates. HOWEVER, even though I have taken all the necessary steps, I still get the same prompt on my tablet at least once a day.
Now, I know for a fact the update files have been disabled, because last night I decided to test the update to see if it would actually go through, but it always results in the same error and the update doesn't apply. But no matter what, the prompt still shows up for me the next morning.
The prompt itself is quite annoying. It takes up the entirety of the screen, disables all other functionality of the tablet and doesn't let me choose other processes, and makes me select one of two options: Either I choose to apply the update, which immediately fails, or I can choose to delay the update to a different time during the day. If I could grab a screenshot, I'd show you guys what it looks like. But, I literally can't do anything on my tablet until after I make that selection, which immediately closes the process. That means I can't freeze the process using TitaniumBackup or something like that. I am helpless to suffer these update prompts every morning.
Now don't get me wrong. I'm not ever going to actually run the update, but the reminder is just such an inconvenience. So, I thought I'd make a post and see if there's anything you guys can think of that might be able to help me find whatever is causing these prompts and get rid of it. I've disabled the update.zip, I've disabled notifications from the Google Play Services, and I've rid myself of all the unnecessary bloatware on my device. I left a few Verizon processes on the tablet that I wasn't 100% sure if they were safe to remove or not, and I've even installed the FOTAKill.apk to see if that would help. The update doesn't work, but the prompt still shows up every morning.
I'd be forever in your guys' debt if you could help me on this one. Thanks for the read, and thanks ahead of time for any help! =D
metalslug53 said:
How's it going, everyone? I just want to apologize ahead of time if this is in the incorrect forum. There's so many to choose from and I didn't see one dedicated to this particular tablet.
I recently acquired a Verizon Ellipsis 8 and the first thing I wanted to do with the device was root it. After trying what must have been 10-15 different methods, I was finally successful at getting the device rooted using a (What I assume to be) Chinese root method called Kingroot. They had support for the tablet and actually got me root access, so I went with it. Shortly after, I installed all my necessary root apks and got the device working in what I would describe as acceptable order. I then began hunting for custom ROMS for the thing, but if there was one thing harder to find for this tablet than root access, it was a custom ROM.
Anyways, I've been living quite happily on rooted stock. I removed all the unnecessary bloatware from the device and everything has been going smoothly, until a few days ago. Verizon pushed out an OTA update and now I am receiving daily prompts from Verizon to update to the latest firmware. Now, this isn't my first rodeo when it comes to dealing with OTA updates, so I began digging around inside my system files to find the update.zip and disable it, as well as remove the different processes that would possibly be spamming this update notification. After several different files given the .bak extension and several different reboots, I felt comfortable that I had taken care of the issue. Hell, I even went so far as to take the same steps on my wife's tablet (She has the same one, rooted in the same fashion), and HER tablet has stopped sending her updates. HOWEVER, even though I have taken all the necessary steps, I still get the same prompt on my tablet at least once a day.
Now, I know for a fact the update files have been disabled, because last night I decided to test the update to see if it would actually go through, but it always results in the same error and the update doesn't apply. But no matter what, the prompt still shows up for me the next morning.
The prompt itself is quite annoying. It takes up the entirety of the screen, disables all other functionality of the tablet and doesn't let me choose other processes, and makes me select one of two options: Either I choose to apply the update, which immediately fails, or I can choose to delay the update to a different time during the day. If I could grab a screenshot, I'd show you guys what it looks like. But, I literally can't do anything on my tablet until after I make that selection, which immediately closes the process. That means I can't freeze the process using TitaniumBackup or something like that. I am helpless to suffer these update prompts every morning.
Now don't get me wrong. I'm not ever going to actually run the update, but the reminder is just such an inconvenience. So, I thought I'd make a post and see if there's anything you guys can think of that might be able to help me find whatever is causing these prompts and get rid of it. I've disabled the update.zip, I've disabled notifications from the Google Play Services, and I've rid myself of all the unnecessary bloatware on my device. I left a few Verizon processes on the tablet that I wasn't 100% sure if they were safe to remove or not, and I've even installed the FOTAKill.apk to see if that would help. The update doesn't work, but the prompt still shows up every morning.
I'd be forever in your guys' debt if you could help me on this one. Thanks for the read, and thanks ahead of time for any help! =D
Click to expand...
Click to collapse
You will need to modify your build.conf to prevent the update screen from prompting you.
Change the build number to something else....
/system/build.prop
Change the build to something like: ro.build.display.id=AKOT49HA
and do the same to the rest of them in the file.