I have converted my padfone x to a padfone s
The basic way I did it was follow the directions for installing cm12 boot cm12 using fastboot boot cwm6.img instead of flashing unlocking the bl using cwm6 ( I was not running a tested version of att software) then flashing the flash the newest ww padfone s firmware from their webpage then doinf a data format then rebooting to stock recovery and flashing the asus firmware a second time then factory reset.. I kept BL unlock and did not flash new recovery because I will unroot when 5.0 is released. second bonus is incall recording. but the minus is the mobile net connection is based on strongest signal not fastest and LTE band 17 needs to be enabled on each boot using anycut But in my opinion the benefits are way better the the lte thing HSPA is really fast enough. IF these instructions dont make any sense to you dont ask for help they are to advanced for you
Update
LTE has worked it self out. this conversion is 100% and my device is still unlocked BL and SIM
Very good. Thank you for posting this. Currently on tmo running CM12 and will be attempting this
magiconthetire said:
Very good. Thank you for posting this. Currently on tmo running CM12 and will be attempting this
Click to expand...
Click to collapse
good luck first boot takes along time
also flash stock recovery then in fastboot boot to cwm6 using fastboot boot cwm6.img and when it loads do a data and system format flash the update from asus padfone s support page. i used the WW one then power off not reboot then reboot into stock recovery (took some time) then flash the update with stock and factory reset
This is the firmware package i used.
http://dlcdnet.asus.com/pub/ASUS/Mobile_Phone/PadFone_S/UL-ASUS_T00N-WW-11.10.7.11-user.zip
After root with this
A new thing I've noticed with this waw firmware it supports incall call recording
an interesting thing. the zip file from asus does not update the modem.
tjsooley said:
I have converted my padfone x to a padfone s
Click to expand...
Click to collapse
Can you please be more specific?
Did you install an original firmware to your AT&T Padfone X?
I am trying to do so with WW original firmware, but I keep getting an error about signature.
atinkrios said:
Can you please be more specific?
Did you install an original firmware to your AT&T Padfone X?
I am trying to do so with WW original firmware, but I keep getting an error about signature.
Click to expand...
Click to collapse
I installed ww firmware follow the directions in this thread
start with this http://forum.xda-developers.com/showpost.php?p=59623876&postcount=167
then copy the ww firmware to your sd then boot into recovery and format system and data not media and install the ww firmware after that reboot recovery a second time and flash the firmware with the stock recovery it took a few reboots to get it to boot but its golden afer
tjsooley said:
I installed ww firmware follow the directions in this thread
start with this http://forum.xda-developers.com/showpost.php?p=59623876&postcount=167
then copy the ww firmware to your sd then boot into recovery and format system and data not media and install the ww firmware after that reboot recovery a second time and flash the firmware with the stock recovery it took a few reboots to get it to boot but its golden afer
Click to expand...
Click to collapse
After bricking my phone, I managed to push the zip file into recovery mode. However, I cannot update my phone to WW version as it states that Padfone X is a T00D instead of T00N!!!
How did you manage to push the files into it?
Or you just installed the CM12?
atinkrios said:
After bricking my phone, I managed to push the zip file into recovery mode. However, I cannot update my phone to WW version as it states that Padfone X is a T00D instead of T00N!!!
How did you manage to push the files into it?
Or you just installed the CM12?
Click to expand...
Click to collapse
I copied the files to sd first and did not factory reset I just formatted data without media
I installed cm12 first and got that booting then formatted my phone and installed the WW you need to use cwm6 to unlock the BL and system MUST be empty when flashing the zip
tjsooley said:
I copied the files to sd first and did not factory reset I just formatted data without media
I installed cm12 first and got that booting then formatted my phone and installed the WW you need to use cwm6 to unlock the BL and system MUST be empty when flashing the zip
Click to expand...
Click to collapse
I managed to get the phone on.
However I have a hard time to install CWM6. It turns black and doesn't answer to any touch.
Did it happen to you too?
I didn't install I did a fast boot boot and booted the image
Sent from my ASUS_T00N using Tapatalk
tjsooley said:
I didn't install I did a fast boot boot and booted the image
Sent from my ASUS_T00N using Tapatalk
Click to expand...
Click to collapse
I was doing the same mistake again. I rebooting with me CABLE ON!!!!
I managed to install the new T00N version from ASUS website.
First boot had some issues. I did a second install and waiting for the result.
Thank you for your support.
atinkrios said:
I was doing the same mistake again. I rebooting with me CABLE ON!!!!
I managed to install the new T00N version from ASUS website.
First boot had some issues. I did a second install and waiting for the result.
Thank you for your support.
Click to expand...
Click to collapse
Welcome. We most likely wont get OTA's even unrooted because the BL is now unlocked and we cannot relock them because of the way the BL is unlocked so we just need to wait till the DL is posted by ASUS
tjsooley said:
Welcome. We most likely wont get OTA's even unrooted because the BL is now unlocked and we cannot relock them because of the way the BL is unlocked so we just need to wait till the DL is posted by ASUS
Click to expand...
Click to collapse
Are you using the new update from the Asus website or the Nightly Cyogen?
I am using the one from Asus and the phone keeps rebooting.
Asus and no reboots do a factory reset them reflash from stock recovery
Sent from my ASUS_T00N using Tapatalk
Did mobile hotspot work okay after moving to Padfone S?
Related
hi
i tried upgrade to hairybeen 2.3 (from an earlier version which is 4.1.1)(its unlocked)
now i get this screen
i tried to flash twrp recovery 2.6 via fastboot
and i get a massage it was flashed ok
is it bricked ?
how can i fix it ?
why the usb icon is missing ?
pre-thank you for helping
EliranB said:
hi
i tried upgrade to hairybeen 2.3 (from an earlier version which is 4.1.1)(its unlocked)
now i get this screen
i tried to flash twrp recovery 2.6 via fastboot
and i get a massage it was flashed ok
is it bricked ?
how can i fix it ?
why the usb icon is missing ?
pre-thank you for helping
Click to expand...
Click to collapse
First of all that message is totally normal in the first screenshot.
The USB icon is missing because in later bootloaders you are instantly in fastboot if you don't select anything.
Now for the problem.... Where did you get that TWRP 2.6 from and what version that you flashed in fastboot...
There are warning all over the Hairybean first post telling you not to flash any other version of twrp on there except what the upgrade puts on because they are not compatible and they will brick you.
If you have flashed a Prime JB TWRP on there you could be in trouble.
Where did you get that TWRP 2.6 from and what version that you flashed in fastboot... from their webpage the 2 in the botom
There are warning all over the Hairybean first post telling you not to flash any other version of twrp on there except what the upgrade puts on because they are not compatible and they will brick you. im sure in 99% it was the jb version
If you have flashed a Prime JB TWRP on there you could be in trouble. so im in trouble now ???
TWRP TF201
EliranB said:
Where did you get that TWRP 2.6 from and what version that you flashed in fastboot... from their webpage the 2 in the botom
There are warning all over the Hairybean first post telling you not to flash any other version of twrp on there except what the upgrade puts on because they are not compatible and they will brick you. im sure in 99% it was the jb version
If you have flashed a Prime JB TWRP on there you could be in trouble.
TWRP TF201
Click to expand...
Click to collapse
You wasn't supposed to use any of them. That is what all the warnings are for.
Can I ask why you flashed it? Compatible 2.6 twrp was included in the bootloader upgrade.
flumpster said:
You wasn't supposed to use any of them. That is what all the warnings are for.
Can I ask why you flashed it? Compatible 2.6 twrp was included in the bootloader upgrade.
Click to expand...
Click to collapse
twrp 2.6 worked for me then i flashed the update of hairybeen & i thought it was stuck after the reboot so i turn it off
then the problem started
so i reflashed the TWRP via fastboot
& now i cant install TWRP or CWM Recovery
its transfering the file successfully but wont load the rck(recovery) mode
so its breaked ? or there is a way to flash something ???
EliranB said:
twrp 2.6 worked for me then i flashed the update of hairybeen & i thought it was stuck after the reboot so i turn it off
then the problem started
so i reflashed the TWRP via fastboot
& now i cant install TWRP or CWM Recovery
its transfering the file successfully but wont load the rck(recovery) mode
so its breaked ? or there is a way to flash something ???
Click to expand...
Click to collapse
Did you restart as the blue line was filling when it was flashing the new partitions ?
flumpster said:
Did you restart as the blue line was filling when it was flashing the new partitions ?
Click to expand...
Click to collapse
the blue line was full
EliranB said:
the blue line was full
Click to expand...
Click to collapse
Yes but you have to wait for it to finish itself and it will restart on its own.
I don't mean to sound nasty but you basically ignored every instruction in the thread.
Your only chance now is to see if the following thread can fix you.. I have a link in it.
http://forum.xda-developers.com/showthread.php?t=2409602
flumpster said:
Yes but you have to wait for it to finish itself and it will restart on its own.
I don't mean to sound nasty but you basically ignored every instruction in the thread.
Your only chance now is to see if the following thread can fix you.. I have a link in it.
http://forum.xda-developers.com/showthread.php?t=2409602
Click to expand...
Click to collapse
i think now i breaked it
i tried the "wipe data" option & now its only in the asus splash screen without fastboot or anything else but asus is unlocked
EliranB said:
i think now i breaked it
i tried the "wipe data" option & now its only in the asus splash screen without fastboot or anything else but asus is unlocked
Click to expand...
Click to collapse
There was nothing in that post I linked you to that says to use that wipe data option mate.
Now I think you are really hard bricked sorry.
i did the mistake
i dont blame you
thank you very much for your help
now i need to replace the motherboard right ??
EliranB said:
i did the mistake
i dont blame you
thank you very much for your help
now i need to replace the motherboard right ??
Click to expand...
Click to collapse
At the moment that is the only option available I am sorry mate unless you made nvflash backups while you was on ICS which I doubt you have.
I just used casual to root and unlock my note 2.i have root and it booted up on twrp but I want to check if I am unlocked bootloader. Is there a way I can check? In my about phone my status says normal
If the bootloader was not unlocked it would overwrite any changes you make to recovery and system files. So as long as you can reboot without losing TWRP or any custom ROM you've installed you're golden.
Unlocked Bootloader?
Jiggabitties said:
If the bootloader was not unlocked it would overwrite any changes you make to recovery and system files. So as long as you can reboot without losing TWRP or any custom ROM you've installed you're golden.
Click to expand...
Click to collapse
It's been a while for me since I rooted my phone, and I don't know if I unlocked my bootloader either... I have never installed a custom ROM, I only rooted so I could tether. But now that the new OTA update keeps trying to install itself, I need to fix this because it's extremely annoying. I read a thread that said I need to flash this: http://forum.xda-developers.com/showthread.php?t=2578458, but it said that I need my bootloader to be unloacked, and therein lies my question...
Am I thinking this through the correct way?
If you just want to stop the update notification fteeze SDM 1.0
James Mac said:
It's been a while for me since I rooted my phone, and I don't know if I unlocked my bootloader either... I have never installed a custom ROM, I only rooted so I could tether. But now that the new OTA update keeps trying to install itself, I need to fix this because it's extremely annoying. I read a thread that said I need to flash this: http://forum.xda-developers.com/showthread.php?t=2578458, but it said that I need my bootloader to be unloacked, and therein lies my question...
Am I thinking this through the correct way?
Click to expand...
Click to collapse
That is the correct thread. Easy way to check is to boot into recovery and see if there is a custom recovery installed. Power down your device, hold down the volume up + verizon button, then power up. Hold volume up + verizon button until you see the galaxy note 2 splash screen. If it boots into TWRP than you're still good. But you will probably want to update to the latest version of TWRP before you go installing any new roms.
Jiggabitties said:
That is the correct thread. Easy way to check is to boot into recovery and see if there is a custom recovery installed. Power down your device, hold down the volume up + verizon button, then power up. Hold volume up + verizon button until you see the galaxy note 2 splash screen. If it boots into TWRP than you're still good. But you will probably want to update to the latest version of TWRP before you go installing any new roms.
Click to expand...
Click to collapse
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
James Mac said:
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
Click to expand...
Click to collapse
The firmware update is done in ODIN and the ROM is done in TWRP.
James Mac said:
Thanks Jiggabitties, I updated TWRP and downloaded official firmware.md5 file and the Mj9 DeOdex file to my pc. Should I transfer those files to the sd card in my phone and install from the TWRP menu? If so, I do the official firmware file first, right? Then the deodex...?
Thanks for all your help man
Click to expand...
Click to collapse
Yes start by transferring the files to your SD card.
The firmware package from that thread is meant to be flashed via ODIN. If you are not comfortable in flashing firmware via ODIN then use this in it's place... https://www.dropbox.com/s/lz29kvrvzfttfpu/MJ9ModemParams.zip This is a TWRP flashable version of the firmware.
Place the MJ9 Deodex and the modemparam.zip I linked to above on your SD card. Flash the ROM file first, then the modemparam.zip. Then clear cache/ dalvik and reboot. That should be all you need to do. If when you boot you don't get service, then you will need to go ahead and flash the firmware vid ODIN. Some users have no issues with the flashable version that I linked above, some users do.
So I realized that there wasn't much support out there for the padfone X. I love my padfone X regardless of its tiny battery, lack of developer support, and unpopularity. So I decided to embrace my love for tech and support the device myself.
So, Asus is still showing love to the padfone S(not X). That being the case it's the international version of the AT&T X; the hardware is almost identical. I decided to turn my X into an S, unlock the bootloader, upgrade to Android 5(I know its not the latest but it's better than 4.4.2), root and enjoy.
Breaking, bricking, whatever... This is all on you, this is what I did to my phone. I'm only sharing my experience. Make sure your phone is fully charged before you begin. Don't say I broke your phone, your taking a risk. I take no credit if this does or doesn't work. This process is time consuming and might not work for you. Don't blame me for wasted time.
This should give you carrier unlock as well.(not tested) and you should be able to use the Padstation with Lollipop. I'll leave download links below.
Steps
#1 back up all your data(titanium etc)
#2 download and run New Kingroot(took 5 tries to work)
#3 download and run superSume Pro
#3a step 3 should have installed SuperSU... Uninstall Kingroot & update SuperSU (use normal method); get a root checker and check root
#4 download a custom recovery(I personally like TWRP, but its buggy on this phone whatever) store the recovery.img on your phone's internal storage(not sd)
#5 install a flash tool(rashr or flashify will do) flash the custom recovery img.
#5a you should have root and custom recovery now, even if the bootloader is locked.
#6 The hard part. Put the S firmware on your internal storage(not sd card)
#7 in recovery mode you need to make another back up(back ups are awesome) do a factory reset in recovery(also wipe cache)
#7a install S firmware(do this in recovery mode) and restart phone. (Initial boot takes about 2 minutes). This might not work the first time(took 5 restores for me to finally get it)
Congratulations!!! You now have a "Padfone S"
#8 preferably using clockwork mod, install crowlock zip file by quarx to unlock bootloader
#9 to upgrade from 4.4.2 to 5.0 you need to go through about 4 updates from the Asus website. Follow this link(only use WW upgrades)
#10 after the upgrades you may have lost root. Just follow steps 2 and 3 again.
Asus "says" they will be releasing Android 6 for the Padphone S... Don't know how true that is, hope so. ENJOY!!!
Downloads and links
Kingroot:
http://www.appsandroidapk.com/tools/kingroot/
S firmware: thank you to tjsnooley!!!
http://forum.xda-developers.com/padfone-x/general/i-have-done-it-t3053207
TWRP/Cwm: thanks quarx!!!
http://quarx2k.ru/asus_padfone_s/recovery/
Crow Lock:
http://quarx2k.ru/asus_padfone_s/
Asus upgrades:
https://www.asus.com/support/Download/29/1/0/10/6vHIzvNAKBCV4v9w/32/
The superSume Pro costs money, you'll have to find it on your own, sorry...
This is a good write up but doesn't work on new units that was recently pushed out...I have tried multiple custom recoveries and none will even write to the phone.I keep getting a response remote device doesn't allow operation.I do have it rooted with the intel tool.Any advice would be great.Thanks in advance.
Surgeman said:
This is a good write up but doesn't work on new units that was recently pushed out...I have tried multiple custom recoveries and none will even write to the phone.I keep getting a response remote device doesn't allow operation.I do have it rooted with the intel tool.Any advice would be great.Thanks in advance.
Click to expand...
Click to collapse
Think it's because 7a and 8 should be switched around. You can't flash the Padfone S firmware on a Padfone X until you unlock the bootloader.
So basically, the steps:
1. Root
2. Install Flashify from the Play Store
3. Use Flashify to flash the Padfone X/S TWRP
4. Boot into TWRP and make a backup.
5. In TWRP, flash the Crowlock bootloader unlocker zip
6. Wipe internal storage except for /sdcard
7. Flash the Padfone S firmware zip
8. Reboot and enjoy
Also, #9 and #10 don't have to be done. The firmware update zips that ASUS publishes are full system images, so you can just flash the newest one and be good to go. (but make sure to flash WW)
This is an other on how to do a conversion in a different way.
There are other guides that are written up that do the exact same thing.
I have also written a guide to do this as well if that helps, its kinda of different but it is comprehensive.
One difference is that to root the padfone x I did towelrootv1 (other versions don't work) because its easier and not worrisome by default. ( I haven't mentioned that because I assumed people have rooted it already and know what they are doing)
Another difference is that you don't need to keep updating the device to the latest, that's just wasting time.
You could just go from the at&t 4.4.2 version, to the absolute latest version of the padfone s firmware.
I just don't want to see any confusion out of this guide in general, but keep in mind that this is a similar but different guide to a conversion.
---------- Post added at 10:04 AM ---------- Previous post was at 10:01 AM ----------
Surgeman said:
This is a good write up but doesn't work on new units that was recently pushed out...I have tried multiple custom recoveries and none will even write to the phone.I keep getting a response remote device doesn't allow operation.I do have it rooted with the intel tool.Any advice would be great.Thanks in advance.
Click to expand...
Click to collapse
Wait what device do you have?
Padfone x mini?
Thanks for the advice xtermmin but something has changed with the newer units.Flashify just crashes and if you fastboot flash the recovery you get this command has been stubbed.Also...towelroot won't even touch it for root now.I did manage to get it rooted with the intel tool with a temp cwm recovery,and flashed the SU zip beta.I have tried flashing the recovery with terminal emulator no go.If you boot with the intel temp cwm recovery and flash the Crowlock zip it errors out.I have followed several threads and so far nothing will tough it...Asus has been watching us....lol...
Oh the device is AT&T Padfone X mini by the way.
Surgeman said:
Thanks for the advice xtermmin but something has changed with the newer units.Flashify just crashes and if you fastboot flash the recovery you get this command has been stubbed.Also...towelroot won't even touch it for root now.I did manage to get it rooted with the intel tool with a temp cwm recovery,and flashed the SU zip beta.I have tried flashing the recovery with terminal emulator no go.If you boot with the intel temp cwm recovery and flash the Crowlock zip it errors out.I have followed several threads and so far nothing will tough it...Asus has been watching us....lol...
Oh the device is AT&T Padfone X mini by the way.
Click to expand...
Click to collapse
The Padfone x mini contains an intel processor so they have a different kind of bootloader than the Padfone x, which has a Snapdragon 800.
Towelroot was patched when newer updates came along, but it still works with the original padfone x since they never got an update from at&t in the last year.
Also the padfone s fw is not compatable with the padfone x mini, since there is a different dock involved. (different screen and resolution).
Overall both devices may look similar but have completely different hardware, so that why it will not work for you.
Thanks for verifying the regular X processor..I seen it said it had the Snapdragon but was curious of the fact.Well I guess I'm on my own,and maybe I need to start a support thread for this thing.lol...Thanks for everyone's help...
How Can I unlock bootloader ATT 11.10.8.16? is posible? help me pls
leo025 said:
How Can I unlock bootloader ATT 11.10.8.16? is posible? help me pls
Click to expand...
Click to collapse
xtermmin said:
Think it's because 7a and 8 should be switched around. You can't flash the Padfone S firmware on a Padfone X until you unlock the bootloader.
So basically, the steps:
1. Root
2. Install Flashify from the Play Store
3. Use Flashify to flash the Padfone X/S TWRP
4. Boot into TWRP and make a backup.
5. In TWRP, flash the Crowlock bootloader unlocker zip
6. Wipe internal storage except for /sdcard
7. Flash the Padfone S firmware zip
8. Reboot and enjoy
Also, #9 and #10 don't have to be done. The firmware update zips that ASUS publishes are full system images, so you can just flash the newest one and be good to go. (but make sure to flash WW)
Click to expand...
Click to collapse
Simple and works!!! LL 5.0 in my Padfone X :highfive:
Easy as pie
xtermmin said:
Think it's because 7a and 8 should be switched around. You can't flash the Padfone S firmware on a Padfone X until you unlock the bootloader.
So basically, the steps:
1. Root
2. Install Flashify from the Play Store
3. Use Flashify to flash the Padfone X/S TWRP
4. Boot into TWRP and make a backup.
5. In TWRP, flash the Crowlock bootloader unlocker zip
6. Wipe internal storage except for /sdcard
7. Flash the Padfone S firmware zip
8. Reboot and enjoy
Also, #9 and #10 don't have to be done. The firmware update zips that ASUS publishes are full system images, so you can just flash the newest one and be good to go. (but make sure to flash WW)
Click to expand...
Click to collapse
Yeah this is exactly what I did, but in case of rooting (for some bizarre reason) the only method that worked for me was using Kingroot and then to purchase the app Super Sume Pro in order to get root access. After that I strictly followed the above procedure and now both devices are functioning flawlessly!!!
Big thanks to all doing the tutorials on the padfone x to s!
For the folks following this thread - any issues with band 17 like described in the other threads? I think the twrp.img link is not the one that allows restoring of EFS (Nexus5repack-A01) so just curious if anyone having issues with LTE or band 17 (if you care )?
I also received a software update from ATT recently - got excited it was finally Lollipop but it turned out to be updated built ATT_11.10.11.1. Anyone else get this, any issues converting / unlocking BL on this build before I plunge L)
Thanks again!
Phone: Padfone X
Build: ATT_11.10.11.1
Mods: TowelRootv1, TWRP (twrp_2.8.7.8_v5.img)
synergysemantics said:
Big thanks to all doing the tutorials on the padfone x to s!
For the folks following this thread - any issues with band 17 like described in the other threads? I think the twrp.img link is not the one that allows restoring of EFS (Nexus5repack-A01) so just curious if anyone having issues with LTE or band 17 (if you care )?
I also received a software update from ATT recently - got excited it was finally Lollipop but it turned out to be updated built ATT_11.10.11.1. Anyone else get this, any issues converting / unlocking BL on this build before I plunge L)
Thanks again!
Phone: Padfone X
Build: ATT_11.10.11.1
Mods: TowelRootv1, TWRP (twrp_2.8.7.8_v5.img)
Click to expand...
Click to collapse
Wow at&t pushed an update to this device, I thought that was the end of the suport due to this thing not selling much at all.
At&t will probably not update the Padfone x to lollipop as there are rumors that the Padfone X2 might be coming out around march.
I flash those different versions of twrp to keep my band 17 and for call settings to actually work.
With out that I cannot make my phone number show up on caller id, and call forwarding to work.
Using PFS Fw, This phone is incredibly stable and all of the features actually work despite doing that conversion.
Probably worried as to what could happen if Marshmallow gets pushed out for the S, would we still be able to use the firmware then? We'll see from there. Its probably better to go to CM13, once everything starts working. (its been improving, but not suitable for being a daily driver as some apps FC and tablet support almost works.)
As always you could check my guide, a bit longer, though its understandable and help you prevent losing Band 17 and call settings
youngson87 said:
So I realized that there wasn't much support out there for the padfone X. I love my padfone X regardless of its tiny battery, lack of developer support, and unpopularity. So I decided to embrace my love for tech and support the device myself.
So, Asus is still showing love to the padfone S(not X). That being the case it's the international version of the AT&T X; the hardware is almost identical. I decided to turn my X into an S, unlock the bootloader, upgrade to Android 5(I know its not the latest but it's better than 4.4.2), root and enjoy.
Breaking, bricking, whatever... This is all on you, this is what I did to my phone. I'm only sharing my experience. Make sure your phone is fully charged before you begin. Don't say I broke your phone, your taking a risk. I take no credit if this does or doesn't work. This process is time consuming and might not work for you. Don't blame me for wasted time.
This should give you carrier unlock as well.(not tested) and you should be able to use the Padstation with Lollipop. I'll leave download links below.
Steps
#1 back up all your data(titanium etc)
#2 download and run New Kingroot(took 5 tries to work)
#3 download and run superSume Pro
#3a step 3 should have installed SuperSU... Uninstall Kingroot & update SuperSU (use normal method); get a root checker and check root
#4 download a custom recovery(I personally like TWRP, but its buggy on this phone whatever) store the recovery.img on your phone's internal storage(not sd)
#5 install a flash tool(rashr or flashify will do) flash the custom recovery img.
#5a you should have root and custom recovery now, even if the bootloader is locked.
#6 The hard part. Put the S firmware on your internal storage(not sd card)
#7 in recovery mode you need to make another back up(back ups are awesome) do a factory reset in recovery(also wipe cache)
#7a install S firmware(do this in recovery mode) and restart phone. (Initial boot takes about 2 minutes). This might not work the first time(took 5 restores for me to finally get it)
Congratulations!!! You now have a "Padfone S"
#8 preferably using clockwork mod, install crowlock zip file by quarx to unlock bootloader
#9 to upgrade from 4.4.2 to 5.0 you need to go through about 4 updates from the Asus website. Follow this link(only use WW upgrades)
#10 after the upgrades you may have lost root. Just follow steps 2 and 3 again.
Asus "says" they will be releasing Android 6 for the Padphone S... Don't know how true that is, hope so. ENJOY!!!
Downloads and links
Kingroot:
http://www.appsandroidapk.com/tools/kingroot/
S firmware: thank you to tjsnooley!!!
http://forum.xda-developers.com/padfone-x/general/i-have-done-it-t3053207
TWRP/Cwm: thanks quarx!!!
http://quarx2k.ru/asus_padfone_s/recovery/
Crow Lock:
http://quarx2k.ru/asus_padfone_s/
Asus upgrades:
https://www.asus.com/support/Download/29/1/0/10/6vHIzvNAKBCV4v9w/32/
The superSume Pro costs money, you'll have to find it on your own, sorry...
Click to expand...
Click to collapse
Hello, thanks for you work, a have a question, the padstation work fine after change padfone x to padfone s firmware?
Regards.
i think i need help, in twrp i cant do wipe data cache dalvik, i try to do data factory reset from options, but after insert code, nothing... doesn't start.. i try to install a rom ww of padfone S, doesn't work.. T___T my internal storage is near to full and my telephone have stock icons and no other applications.. Any suggestions to do ?
colla.paolo said:
i think i need help, in twrp i cant do wipe data cache dalvik, i try to do data factory reset from options, but after insert code, nothing... doesn't start.. i try to install a rom ww of padfone S, doesn't work.. T___T my internal storage is near to full and my telephone have stock icons and no other applications.. Any suggestions to do ?
Click to expand...
Click to collapse
Hmmm Try it with a different recovery such as cwm, thats strange that twrp would not work. After boot into it and factory reset then flash cm12.1 just to make sure that the internal storage not full, then it will be best to install twrp afterwards to flash the padfone s firmware.
unable to mount cache, i cant clean
edit: i do wipe cache and system with cwm, now i have bootloop in cwm,
i try to install romname.zip ... system say, this is ASUS_T00N file, this is t00n.
Failed.
i try with ADB too, at 94% *failed to write data 'protocol fault p' * .
i try with the last firmware *failed to write data
i can't explore cellphone via usb, sd card can't readed.
im totally a noob.
i try to follow all steps, but nothing.
Thanks for brick my cellphone and now it's a totally useless.
thanks regards
colla.paolo said:
unable to mount cache, i cant clean
edit: i do wipe cache and system with cwm, now i have bootloop in cwm,
i try to install romname.zip ... system say, this is ASUS_T00N file, this is t00n.
Failed.
i try with ADB too, at 94% *failed to write data 'protocol fault p' * .
i try with the last firmware *failed to write data
i can't explore cellphone via usb, sd card can't readed.
im totally a noob.
i try to follow all steps, but nothing.
Thanks for brick my cellphone and now it's a totally useless.
thanks regards
Click to expand...
Click to collapse
I have never had luck with CWM on this phone, that is why I use TWRP.
If you still have difficulty mounting: From TWRP, go to wipe, advanced wipe, select the partition you are having difficulty with, tap Repair or Change File System, tap Repair. If that isn't successful, tap Change File System, then choose EXT4.
For the error: ASUS_T00N file, this is t00n
1. open the rom.zip, do not extract, just open.
2. Browse to \META-INF\com\google\android\ then open updater-script. Most people suggest to use a unix based text editor, but wordpad works fine for me.
3. Delete the first line containing: getprop("ro.product.device") == "ASUS_T00N" || abort("This package is for "ASUS_T00N" devices; this is a "" + getprop("ro.product.device") + "".");
4. Save and close. (this is the part where I have trouble with using Note++ or other unix based editor, I can't get it to save within a zip file. That is why I just use wordpad which i have never had issue with.)
5. Transfer to phone and flash.
6. Profit.
If that doesn't work, just use ADB sideload through TWRP.
1. From TWRP go to Advanced, ADB Sideload, tick checkboxes, swipe to Start Sideload. (Note, make sure phone is connected to PC.
2. From PC command prompt, run command ADB Devices to verify device is connected and detected as being in Sideload mode.
3. From PC command prompt, run command ADB Sideload filename.zip
Note: To make using ADB easier, I just drop the rom into the folder where adb.exe is located. From Windows explorer, CTRL+Shift+Right Click Folder containing ADB, click Open Command Window Here This way I don't have to do a bunch of CD commands or provide file path to ROM that I am using.
^ Follow his guide first ^
colla.paolo said:
unable to mount cache, i cant clean
edit: i do wipe cache and system with cwm, now i have bootloop in cwm,
i try to install romname.zip ... system say, this is ASUS_T00N file, this is t00n.
Failed.
i try with ADB too, at 94% *failed to write data 'protocol fault p' * .
i try with the last firmware *failed to write data
i can't explore cellphone via usb, sd card can't readed.
im totally a noob.
i try to follow all steps, but nothing.
Thanks for brick my cellphone and now it's a totally useless.
thanks regards
Click to expand...
Click to collapse
I assume that you did unlock the bootloader prior to that, but if not do that in cwm (if its still installed) since that works well by putting the file into the sd card.
Ok, but you were able to fix cache, I wouldn't say its bricked as you could just boot a different recovery through fastboot, so twrp is what you must use to flash the ww fw to the phone since cwm doesn't like that fw.
So put your phone to fastboot mode which is power and volume up at the same time, the logo should be frozen, which is good. Then put in the usb cable into the computer afterwards, and let the computer recogonize the device. If it does good, and thats when you need to get fastboot running on your computer and hope that the phone gets detected. If it does great.
The next step is putting the twrp recovery in a place that would be able to be activated from the computer, there are many tutorials how to get it to set up perfectly, but as long as the command you are about to put in should give you "cannot" locate file. Heres a nice guide: https://aubykhan.wordpress.com/2013...t-into-twrp-or-cwm-recovery-without-flashing/
The command is fastboot boot (then the file name).img and presto you got a recovery rolling for you to flash a rom on to the phone.
After flashing the fw the bootloader does get locked and the recovery will be replaced with stock so make sure to reflash the bootloader unlock through flashing the zip file and the twrp recovery file under img flash. (there should be an option there)
I've been there and that sucks but as long as you are careful and know what your'e doing I think you could get yourself out of that state where there is no rom installed.
The guy who posted above me does have the other solutions with the other errors if you run into them.
Good Luck
How to turn Padfone x to s
Am new at this How i can my Padfone x to s
King 242 said:
Am new at this How i can my Padfone x to s
Click to expand...
Click to collapse
Read the first page of this thread.
The basic steps:
0. Grab the following and throw them on your microSD card:
Latest Padfone S Worldwide (WW) firmware from ASUS: https://www.asus.com/support/Download/29/1/0/10/6vHIzvNAKBCV4v9w/32/
CrowLock: http://quarx2k.ru/asus_padfone_s/CrowLock_RC3.zip
TWRP Recovery: http://quarx2k.ru/asus_padfone_s/recovery/twrp_3.0.0.img1. Root (via Kingroot, Towelroot v1, whatever)
2. Install Flashify from the Play Store
3. Use Flashify to flash the TWRP recovery on your microSD card
4. Boot into TWRP recovery and make a backup.
5. In TWRP, flash the Crowlock bootloader unlocker zip
6. Wipe internal storage except for /sdcard
7. Flash the Padfone S firmware zip
8. System > Reboot > say yes to rooting the device. Enjoy.
Model:XT1521 Retasia(Indian)
So let's get on with the story
I own a moto e 2 4g variant. I unlocked the bootloader of the device,installed a custom recovery and flashed a custom ROM. Everything went well;I was trying a new ROM almost everyday(5.1.1 and 6.0.1) until one day when I decided to go back to stock ROM.I downloaded the official 6.0 stock ROM,installed it and started the device.The phone booted,went straight to recovery and showed erasing.The problem starts here.It showing eraseing and rebooted after some time and I thought that it's going to boot up into stock 6.0.But I was wrong.The phone booted and again did the same thing and this went on in a loop.So I decided to try it once more.This time I did two more things prior to installing the ROM;
Fastboot erase all
Fastboot erase system - w
Till then in bootloader it showed official in software status.But after those two erase commands it started showing modified.
Even then the result was the same I.e.showing erasing and rebooting.So I thought that I will go back to custom ROM for the time being.all went well,phone booted up but there was no signal.The phone was not accepting any Sims. I went to bootloader and immediately found out the cause.It was showing not found under baseband.So I seperately flashed a modem but to no luck.As of now I have tried all stock rims available(5.0.2,5.1.1,6.0) but the device is not booting up.
Any help will be highly appreciated.
Thanks in advance.
This happened to me with CM13, the same thing happened with the baseband number, and I couldn't even enter in the recovery, so I had to manually flash the Stock ROM via adb. It happened to me again when I tried to root my phone even with the systemless root, the phone just doesn't boot up, I'd recommend you to flash the basebands found in the forums, if that doesn't fix it, you'll have to manually flash the stock rom via adb or you can use the easy tool, it's fairly simple if you follow the steps, I'll leave the links bellow.
Easy tool flasher
Basebands
Filz0r said:
This happened to me with CM13, the same thing happened with the baseband number, and I couldn't even enter in the recovery, so I had to manually flash the Stock ROM via adb. It happened to me again when I tried to root my phone even with the systemless root, the phone just doesn't boot up, I'd recommend you to flash the basebands found in the forums, if that doesn't fix it, you'll have to manually flash the stock rom via adb or you can use the easy tool, it's fairly simple if you follow the steps, I'll leave the links bellow.
Easy tool flasher
Basebands
Click to expand...
Click to collapse
Used the flashing tool.But in every mode of flashing,the bootloader flashing and boot.img flashing is showing some error.But rest all are flashing succesfully.Still in bootloader it is showing baseband not found.And when I boot the device,the bootloader screen comes up,followed by a black screen and the cycle repeats.Any help would be appreciated.
Edit:My moto e 2015 is a LTE RETASIA(Indian) model.In the baseband link you provided,XT1521 RETASIA version's baseband is not available.
Fastboot flash bootloader bootloader. Img
Rename motoboot img
Sent from my MotoG3 using XDA-Developers mobile app
first.act.line said:
Fastboot flash bootloader bootloader. Img
Rename motoboot img
Sent from my MotoG3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks I will try that.
gauthamkithu said:
Model:XT1521 Retasia(Indian)
So let's get on with the story
I own a moto e 2 4g variant. I unlocked the bootloader of the device,installed a custom recovery and flashed a custom ROM. Everything went well;I was trying a new ROM almost everyday(5.1.1 and 6.0.1) until one day when I decided to go back to stock ROM.I downloaded the official 6.0 stock ROM,installed it and started the device.The phone booted,went straight to recovery and showed erasing.The problem starts here.It showing eraseing and rebooted after some time and I thought that it's going to boot up into stock 6.0.But I was wrong.The phone booted and again did the same thing and this went on in a loop.So I decided to try it once more.This time I did two more things prior to installing the ROM;
Fastboot erase all
Fastboot erase system - w
Till then in bootloader it showed official in software status.But after those two erase commands it started showing modified.
Even then the result was the same I.e.showing erasing and rebooting.So I thought that I will go back to custom ROM for the time being.all went well,phone booted up but there was no signal.The phone was not accepting any Sims. I went to bootloader and immediately found out the cause.It was showing not found under baseband.So I seperately flashed a modem but to no luck.As of now I have tried all stock rims available(5.0.2,5.1.1,6.0) but the device is not booting up.
Any help will be highly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
u have to flash a official rom with propper way and remember u cannot flash old bootloader on the new bootloader it will definatly brick ur phone so if ur bootloader working do not replace it with old one for more info u can go in official rom section of this site and bootloader section.....good luck
vishalgupta.vns said:
u have to flash a official rom with propper way and remember u cannot flash old bootloader on the new bootloader it will definatly brick ur phone so if ur bootloader working do not replace it with old one for more info u can go in official rom section of this site and bootloader section.....good luck
Click to expand...
Click to collapse
Thanks buddy but unfortunately I have tried that.:crying:
OK guys, thread cleaned.
No more flame from anyone please, no more garbage.
OP please provide as much details as possible. Everyone else, you can ignore the OP if you want, but do not come in here just to flame.
Thanks.
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Fonku said:
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Click to expand...
Click to collapse
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
zinko_pt said:
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
Click to expand...
Click to collapse
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Fonku said:
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Click to expand...
Click to collapse
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
zinko_pt said:
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
Click to expand...
Click to collapse
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Fonku said:
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
You can use B130 as it is also Lollipop. But all the img from the same rom. You can update to B350 manually after, but first you need a stable rom working.
Let us know man if you fixed your phone. So if not, we can give firther recommendations.
Sent from my Galaxy Tab 3 using XDA Labs