PadFone S - Android 5.0 Lollipop released - Asus Padfone X and S

PadFone S - Android 5.0 Lollipop released
ASUS PadFone S Firmware: V12.2.2.21 Only for WW SKU (Android 5.0)
ASUS said: Some apps been removed some been added
the braver; any luck to upgrade... please share your experience, screenshots, is there any problems or issues?
http://support.asus.com/Download.aspx?SLanguage=en&m=PadFone+S&p=29&s=1

---

At first I was constantly getting an error saying process.android.acore had crashed. I went into settings, apps, and then to the all tab and cleared the data for contacts and contacts storage. Now, the error is gone. Scrolling in Firefox, seems smoother. I like the quick apps you can launch from notifications. So far, I like it.

---

I like it too, it seems like the docking station got louder and smoother.
Camera is smoother too.
4k I went from 12 fps (at&t) to 20-24 fps (PFS)
Chromecasting works natively.
You get better battery life because of two reasons. Lollipop (Project Volta) and Asus autostart manager. This is what other android manufacturers should include in the phones themselves. (it can prevent an app from running it and it does that without root)
Lastly better performance
Edit: I like to also point out that fm radio works. Im surprised. Maybe asus disabled it by default because it didnt work in stock.
The only problem for me is getting additional call settings to work.
It would say error with reading SIM card even though LTE works, calling works etc.
This would bother me maybe not you guys because somehow my "network default" is private calling and a private number tends to not get picked up or not answered. (its been like that on my old phone)
I want it to be set on "show number" but it has to check SIM but it doesn't work.
If anyone else has the same problem of doing that the only work around is to dial *82 and the phone number after that so you will be recognized on caller id.
In other words if you can call and your number shows up like normal then you are likely not going to use the additional call settings.
The second issue if you are on at&t is there is no band 17 support.
2 and 4 work fine. Great for T-Mobile
The only way of getting back 17 is restoring from an EFS backup from twrp
Other than that, nothing is acting weird and unstable compared to the at&t version.

---

Months of waiting and this is fing awful.
Worst design descisions and tonns of bloatware...

---

so far so good!
I didn't revert back to the factory recovery, nor did I do a full wipe.
Flashed dirty TWRP!

---

shigileeni said:
PadFone S - Android 5.0 Lollipop released
ASUS PadFone S Firmware: V12.2.2.21 Only for WW SKU (Android 5.0)
ASUS said: Some apps been removed some been added
the braver; any luck to upgrade... please share your experience, screenshots, is there any problems or issues?
http://support.asus.com/Download.aspx?SLanguage=en&m=PadFone+S&p=29&s=1
Click to expand...
Click to collapse
Dirty flashed with TWRP recovery a few days ago (when the link popped up in the ASUS PadFone S forums). Have been testing it thoroughly. OK so far, nothing that earth shaking.
I use this as a tablet for the most part, update works, no hiccups. Video playback and audio both seem a little bit more crisp in station. WiFi stable. Battery balance good.
Going to do a full TWRP data format, then clean flash with Gapps and SuperSU to see if it gets a performance boost.
XPOSED works just fine on this updated ROM.. Lots of Lollipop whistles and bells work with the activated modules. (You must be rooted of course.)
A tweaked kernel would really help here. They safe zoned the Krait 400 CPU to its lowest point, and I'm sure that it will go much higher, 2.8-3.0Ghz perhaps. The Adreno 330 should be able to go to dance @675.
More later.

---

blambo said:
Dirty flashed with TWRP recovery a few days ago (when the link popped up in the ASUS PadFone S forums). Have been testing it thoroughly. OK so far, nothing that earth shaking.
I use this as a tablet for the most part, update works, no hiccups. Video playback and audio both seem a little bit more crisp in station. WiFi stable. Battery balance good.
Going to do a full TWRP data format, then clean flash with Gapps and SuperSU to see if it gets a performance boost.
XPOSED works just fine on this updated ROM.. Lots of Lollipop whistles and bells work with the activated modules. (You must be rooted of course.)
A tweaked kernel would really help here. They safe zoned the Krait 400 CPU to its lowest point, and I'm sure that it will go much higher, 2.8-3.0Ghz perhaps. The Adreno 330 should be able to go to dance @675.
More later.
Click to expand...
Click to collapse
I was thinking about tweaking CPU performance but unlike the stock AT&T rom, this one is relatively stable and doesn't make my Padfone X heat up like a furnace. I've had this on all night and into this morning. I've been really happy with the results and maybe AT&T should take notice since whatever they did to this ROM (or whatever ASUS did with it) is why this unit didn't sell. Reminds me of the Pantech Element. Decent device but it was locked down heavily and crashed constantly under Honeycomb. Once ICS came out a few years ago, it acts normally and works better than it ever did before.
I actually just went into TWRP and installed this ZIP without GAPPS and used the WW one. At first it didn't work but the second time, I did a full wipe which removed data and cache partitions. Since then, it booted and has since. Instead of using ADB, I just copied it to a micro SD card and installed it from there.
No real issues except for one minor one where I turned off an option and the tablet piece stopped working until I rebooted it. But no random resets and no extremely hot phone this time. I remember with the old ROM that it got so hot that I had to put it on the air conditioning vent and then the refrigerator because I thought it was going to burn through the plastic.
Plus, now it's unlocked (I'm using T-Mobile now and have LTE coverage) and the dock works.
---------- Post added at 02:43 PM ---------- Previous post was at 02:39 PM ----------
nameless517 said:
Months of waiting and this is fing awful.
Worst design descisions and tonns of bloatware...
Click to expand...
Click to collapse
This is how the older ROM was also for the Padfone S when I installed it. If you root it, can't you just remove these apps?
Either way, it's stable, unlocked, and the dock works so I can live with bloatware. Maybe it's because I'm from the USA and all of our phones have this but unlike Windows Phone, I can uninstall them (This is one advantage Windows Phone has. You can actually remove all of the bloatware from the machine easily without much effort).
Here's hoping this keeps up.
Lauren

---

alissa914 said:
I was thinking about tweaking CPU performance but unlike the stock AT&T rom, this one is relatively stable and doesn't make my Padfone X heat up like a furnace. I've had this on all night and into this morning. I've been really happy with the results and maybe AT&T should take notice since whatever they did to this ROM (or whatever ASUS did with it) is why this unit didn't sell. Reminds me of the Pantech Element. Decent device but it was locked down heavily and crashed constantly under Honeycomb. Once ICS came out a few years ago, it acts normally and works better than it ever did before.
I actually just went into TWRP and installed this ZIP without GAPPS and used the WW one. At first it didn't work but the second time, I did a full wipe which removed data and cache partitions. Since then, it booted and has since. Instead of using ADB, I just copied it to a micro SD card and installed it from there.
No real issues except for one minor one where I turned off an option and the tablet piece stopped working until I rebooted it. But no random resets and no extremely hot phone this time. I remember with the old ROM that it got so hot that I had to put it on the air conditioning vent and then the refrigerator because I thought it was going to burn through the plastic.
Plus, now it's unlocked (I'm using T-Mobile now and have LTE coverage) and the dock works.
---------- Post added at 02:43 PM ---------- Previous post was at 02:39 PM ----------
This is how the older ROM was also for the Padfone S when I installed it. If you root it, can't you just remove these apps?
Either way, it's stable, unlocked, and the dock works so I can live with bloatware. Maybe it's because I'm from the USA and all of our phones have this but unlike Windows Phone, I can uninstall them (This is one advantage Windows Phone has. You can actually remove all of the bloatware from the machine easily without much effort).
Here's hoping this keeps up.
Lauren
Click to expand...
Click to collapse
Well, I guess I just got used to CM12.1, clean and fast. Official 5.0 looks too much cluttered and IMHO ugly, and everything felt weird. Got back to CM.

---

any lollipop BSOD guys? my padfone s was getting BSOD after 1 week smooth operation. black screen with only notif and navigaton bar visible. always need to restart after that and becoming more often even after i did factory reset and reinstalling the firmware.
is it really lollipop bugs or what? cause it happened almost no clear reasons. first i guess it was caused by my smart cover apps that automatically lock unlock screen if i closed my flip cover but even in a couple of minutes after fresh and clear reinstalling firmware without installing any apps it happened again and again. i also read about this bug up to 5.1 release in nexus 5 if i am not mistaken.

---

highbud said:
any lollipop BSOD guys? my padfone s was getting BSOD after 1 week smooth operation. black screen with only notif and navigaton bar visible. always need to restart after that and becoming more often even after i did factory reset and reinstalling the firmware.
is it really lollipop bugs or what? cause it happened almost no clear reasons. first i guess it was caused by my smart cover apps that automatically lock unlock screen if i closed my flip cover but even in a couple of minutes after fresh and clear reinstalling firmware without installing any apps it happened again and again. i also read about this bug up to 5.1 release in nexus 5 if i am not mistaken.
Click to expand...
Click to collapse
Im still fine after 10 days of operation. Keep in mind im really using a padfone x that is converted.
What ever it is you should do the downgrade then upgrade again. It shouldn't hurt anything. Just follow the instructions from asus.
Doing that should definitely clear what is causing the problem.

---

Justatechie said:
Im still fine after 10 days of operation. Keep in mind im really using a padfone x that is converted.
What ever it is you should do the downgrade then upgrade again. It shouldn't hurt anything. Just follow the instructions from asus.
Doing that should definitely clear what is causing the problem.
Click to expand...
Click to collapse
i do exactly what asus said. i started from kitkat .17, factory reset, upgrade it to kitkat .18, factory reset, upgrade to lollipop, factory reset again, installing all apps i needed. working fine for a week before it gave me BSOD. so i tried to reinstall the lollipop again after i did factory reset. but it was getting worse, i got BSOD even before installing any apps.
now i am back to .18 kitkat. maybe i ll just wait for next lollipop. thanks.

---

highbud said:
i do exactly what asus said. i started from kitkat .17, factory reset, upgrade it to kitkat .18, factory reset, upgrade to lollipop, factory reset again, installing all apps i needed. working fine for a week before it gave me BSOD. so i tried to reinstall the lollipop again after i did factory reset. but it was getting worse, i got BSOD even before installing any apps.
now i am back to .18 kitkat. maybe i ll just wait for next lollipop. thanks.
Click to expand...
Click to collapse
Do you have a link for this old ROM in case I need it also later down the line?
Not that I want to go back to whatever happened with the old Padfone X rom from AT&T (or Padfone S one), but I somehow think that having Root is what caused me to have problems to begin with. I haven't done root on this one yet so if I'm not having problems (and have full SD card access with Lollipop), then I'm probably not going to... :/
Lauren

---

alissa914 said:
Do you have a link for this old ROM in case I need it also later down the line?
Not that I want to go back to whatever happened with the old Padfone X rom from AT&T (or Padfone S one), but I somehow think that having Root is what caused me to have problems to begin with. I haven't done root on this one yet so if I'm not having problems (and have full SD card access with Lollipop), then I'm probably not going to... :/
Lauren
Click to expand...
Click to collapse
mine is padfone s, just look for ww .18 for manual downgrade (manually through stock recovery) or ww .99 in case for automatic downgrade. it's basically the same kitkat.
http://support.asus.com/Download.aspx?SLanguage=en&m=PadFone+S&p=29&s=1
if you want to downgrade automatically you must use .99 because the phone can only detect new firmware only when the version number is bigger then current one i think.

---

blambo said:
XPOSED works just fine on this updated ROM.. Lots of Lollipop whistles and bells work with the activated modules. (You must be rooted of course.)
Click to expand...
Click to collapse
Which XPOSED installer did you use for Lollipop on Asus Padfone S? I just tried one for Lollipop and I got stuck at the boot logo (not a bootloop, just hung).

---

TigerC10 said:
Which XPOSED installer did you use for Lollipop on Asus Padfone S? I just tried one for Lollipop and I got stuck at the boot logo (not a bootloop, just hung).
Click to expand...
Click to collapse
I had the same issue as well with both XPOSED and SuperSU. Kingroot worked fine though for rooting for me.

---

I've just tried flashing this both by rebooting with the file in the root of the internal sdcard and with CWM and both are failing. The error I'm getting in cwm is "This package is for "ASUS_T00N" devices; this is a "t00n".
Does anyone know what I might need to edit in order to be able to flash this? I've got a Padfone S Plus.
Thanks in advance

---

fmflex said:
I've just tried flashing this both by rebooting with the file in the root of the internal sdcard and with CWM and both are failing. The error I'm getting in cwm is "This package is for "ASUS_T00N" devices; this is a "t00n".
Does anyone know what I might need to edit in order to be able to flash this? I've got a Padfone S Plus.
Thanks in advance
Click to expand...
Click to collapse
Open the zip file, don't extract then go to META_INF/com/google/android then open updater-script with a text editor, most people suggest using a unix based text editor such as Notepad++, but I have found that wordpad works fine, delete the entire first line. Save, then retry install. If that doesn't work, use adb sideload.
Delete line in bold text in example below:
Code:
[B]getprop("ro.product.device") == "ASUS_T00N" || abort("This package is for \"ASUS_T00N\" devices; this is a \"" + getprop("ro.product.device") + "\".");[/B]
show_progress(0.750000, 0);
block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
ui_print("installing rpm");
package_extract_s_file("firmware-update/rpm.mbn", "/dev/block/platform/msm_sdcc.1/by-name/rpm");
ui_print("installing sbl1");
package_extract_s_file("firmware-update/sbl1.mbn", "/dev/block/platform/msm_sdcc.1/by-name/sbl1");
ui_print("installing aboot");
package_extract_s_file("firmware-update/emmc_appsboot.mbn", "/dev/block/platform/msm_sdcc.1/by-name/aboot");
ui_print("installing tz");
package_extract_s_file("firmware-update/tz.mbn", "/dev/block/platform/msm_sdcc.1/by-name/tz");
), "");
ifelse(msm.boot_update("backup"), (
ui_print("installing rpmbak");
package_extract_s_file("firmware-update/rpm.mbn", "/dev/block/platform/msm_sdcc.1/by-name/rpmbak");
ui_print("installing sbl1bak");
package_extract_s_file("firmware-update/sbl1.mbn", "/dev/block/platform/msm_sdcc.1/by-name/sbl1bak");
ui_print("installing abootbak");
package_extract_s_file("firmware-update/emmc_appsboot.mbn", "/dev/block/platform/msm_sdcc.1/by-name/abootbak");
ui_print("installing tzbak");
package_extract_s_file("firmware-update/tz.mbn", "/dev/block/platform/msm_sdcc.1/by-name/tzbak");
),"no backup partition");
msm.boot_update("finalize");
ui_print("installing DDR");
package_extract_file("firmware-update/DDR.img", "/dev/block/platform/msm_sdcc.1/by-name/DDR");
ui_print("installing modem");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem");
ui_print("installing asusfw");
package_extract_file("firmware-update/asusfw.img", "/dev/block/platform/msm_sdcc.1/by-name/asusfw");

---

Thanks a heap Daggorlad, that worked a treat.
Would you know how I can load either twrp or cmw back on using terminal emulator? It throws me a "Unknown username or uid" error though it worked under kitkat.
su -c 'dd if=/sdcard/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
Shoot me over some pp details and I'll buy you a beer.

---

fmflex said:
Thanks a heap Daggorlad, that worked a treat.
Would you know how I can load either twrp or cmw back on using terminal emulator? It throws me a "Unknown username or uid" error though it worked under kitkat.
su -c 'dd if=/sdcard/cwm.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery' bs=4096; sync; reboot recovery;
Shoot me over some pp details and I'll buy you a beer.
Click to expand...
Click to collapse
I'm sorry, but I haven't installed using terminal emulator, I have only ever used fastboot to install recovery on this device.
1. Drop the recovery.img in the same directory as fastboot.exe on your PC..
2. Open CMD and navigate to directory where fastboot.exe and recovery image are located. (can also CTRL+Shift+left click on the folder in which they are located and select Open command window here)
3. Reboot phone into fastboot mode by powering off and holding volume up while powering on or using adb reboot bootloader
4. Run:
Code:
fastboot install recovery [I]recoveryname[/I].img
fastboot reboot
I hope this helps and no need for a beer, just helping others like I have been helped here :good:

---

Thanks Daggorlad, my command prompt just sits at " < waiting for device > "
I powered up the phone holding down the Vol up and it sits on the ASUS screen. Is there anything else I need to get fastboot to work?