[Q&A] [ROM + KERNEL] Tari's ASUS PadFone 2 (r150301) - Android Q&A, Help & Troubleshooting

Q&A for [ROM + KERNEL] Tari's ASUS PadFone 2 (r150301)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM + KERNEL] Tari's ASUS PadFone 2 (r150301). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

---

Hello Tari! I have Running your awesome ROM on my Padfone2, and i find it a very smooth and cool ROM! Thank You, for your Work in it!
I have a Question, - There is a Custom Lollipop ROM on XDA for Padfone S/X! Do you think that work on Padfone2? And the Nexus4 is almost the same hardware as Padfone2, is it possible that a Nexus4 Custom Lollipop ROM works on Padfone2?
Many, Thanks to you for your Work, Time and Engagement!

---

roselanguste said:
Hello Tari! I have Running your awesome ROM on my Padfone2, and i find it a very smooth and cool ROM! Thank You, for your Work in it!
I have a Question, - There is a Custom Lollipop ROM on XDA for Padfone S/X! Do you think that work on Padfone2? And the Nexus4 is almost the same hardware as Padfone2, is it possible that a Nexus4 Custom Lollipop ROM works on Padfone2?
Many, Thanks to you for your Work, Time and Engagement!
Click to expand...
Click to collapse
Thanks for the kind words roselanguste, I am glad you are satisfied with the ROM.
As for the Lollipop, porting it onto the Padfone2 would be lot of work. There are too many ASUS-specific details that would have to be changed, plus for the kernel to work we would need updated hardware modules and firmware. As far as I am concerned, KitKat is the last stop for our device.

---

can you give me step by step how to flash cwm after unlocking the phone (using ansarijavid method for unlock)?
kinda new for this stuff
running 8.1 64 bit
does this rom fix weird colour contrast after put the phone into sleep?

---

azurisu said:
can you give me step by step how to flash cwm after unlocking the phone (using ansarijavid method for unlock)?
Click to expand...
Click to collapse
Create a folder, download the needed files into it and open a terminal from there
Make sure the tools are present: sudo apt-get install android-tools-adb android-tools-fastboot
Enable USB Debugging on the phone
Boot into fastboot mode (Power, Volume up)
Install the CWM recovery: sudo fastboot -i 0x0b05 flash recovery cwm.img
Note: The above is for Linux - no extras are needed, you just plug in your phone and go. Windows users should probably need some drivers, enable ADB, and change the "sudo + COMMAND" parts.
azurisu said:
does this rom fix weird colour contrast after put the phone into sleep?
Click to expand...
Click to collapse
I have not had any contrast troubles, so I really can't tell. The kernel is the latest PF2 can handle, and the firmware is also up-to-date. There should be no issues.

---

tari01 said:
Create a folder, download the needed files into it and open a terminal from there
Make sure the tools are present: sudo apt-get install android-tools-adb android-tools-fastboot
Enable USB Debugging on the phone
Boot into fastboot mode (Power, Volume up)
Install the CWM recovery: sudo fastboot -i 0x0b05 flash recovery cwm.img
Note: The above is for Linux - no extras are needed, you just plug in your phone and go. Windows users should probably need some drivers, enable ADB, and change the "sudo + COMMAND" parts.
I have not had any contrast troubles, so I really can't tell. The kernel is the latest PF2 can handle, and the firmware is also up-to-date. There should be no issues.
Click to expand...
Click to collapse
weird,, i've been experiencing some weird colour issue since kitkat for PF2 released, and still happened on newest fw (11.4.8.23)
locking then unlocking the screen always trigger this, need to restart my device to get it back to normal
something like this..
padfoneclub.com/pl/forum/forum_viewtopic.php?15485
so i thought using custom rom will solve my issue haha
--------

---

reversiblity
tari01 said:
Create a folder, download the needed files into it and open a terminal from there
Make sure the tools are present: sudo apt-get install android-tools-adb android-tools-fastboot
Enable USB Debugging on the phone
Boot into fastboot mode (Power, Volume up)
Install the CWM recovery: sudo fastboot -i 0x0b05 flash recovery cwm.img
Note: The above is for Linux - no extras are needed, you just plug in your phone and go. Windows users should probably need some drivers, enable ADB, and change the "sudo + COMMAND" parts.
I have not had any contrast troubles, so I really can't tell. The kernel is the latest PF2 can handle, and the firmware is also up-to-date. There should be no issues.
Click to expand...
Click to collapse
i'm a completely noob about linux so my only question is : is the procedure reversible? my only fear is about this " sudo fastboot -i 0x0b05 flash recovery cwm.img" , if i type wrong a value what's going to happen? Brick or simply a failrure in the procedure?
Thanks in advance

---

Zollolo19 said:
i'm a completely noob about linux so my only question is : is the procedure reversible? my only fear is about this " sudo fastboot -i 0x0b05 flash recovery cwm.img" , if i type wrong a value what's going to happen? Brick or simply a failrure in the procedure?
Thanks in advance
Click to expand...
Click to collapse
This command is fairly safe. It simply means: "use fastboot to write the cwm.img image to an ASUS device (0x0b05 is your PadFone)". If you feel paranoid you can search for a Stock Recovery image. You can always flash that file instead of cwm.img to get your device back to factory state. Bricking is harder than you think. The bottom line: always read the instructions carefully, make sure you have EXACTLY what is required, and go slowly step-by-step. If you are unsure, or there is an error, do not try to fix it by yourself - go to the forums and tell the people about it, someone will surely help you out.

---

tari01 said:
This command is fairly safe. It simply means: "use fastboot to write the cwm.img image to an ASUS device (0x0b05 is your PadFone)". If you feel paranoid you can search for a Stock Recovery image. You can always flash that file instead of cwm.img to get your device back to factory state. Bricking is harder than you think. The bottom line: always read the instructions carefully, make sure you have EXACTLY what is required, and go slowly step-by-step. If you are unsure, or there is an error, do not try to fix it by yourself - go to the forums and tell the people about it, someone will surely help you out.
Click to expand...
Click to collapse
Thank you for the professional and specially quick answer I'm going to try the procedure tomorrow

---

i have to leave "A68_signed_030415_031241.zip" zipped?
Thanks

---

Zollolo19 said:
i have to leave "A68_signed_030415_031241.zip" zipped?
Thanks
Click to expand...
Click to collapse
Yes. ROMs are always packaged in a ZIP - you just send it to your CWM (sideload seems to be the fastest).

---

it's going automatically in recovery mode? Because i don't know how to enter in it and there're tons of procedure throughout the web.
i'm referring to this point : 3. Boot into recovery mode.
I thought that power + bottom up volume was for the recovery mode, indeed is for the fastboot mode.
Thanks for your courtesy
ULTRA LOL: i forgot to try power + volume down when i wrote this post, sorry xD

---

Zollolo19 said:
it's going automatically in recovery mode? Because i don't know how to enter in it and there're tons of procedure throughout the web.
i'm referring to this point : 3. Boot into recovery mode.
I thought that power + bottom up volume was for the recovery mode, indeed is for the fastboot mode.
Thanks for your courtesy
ULTRA LOL: i forgot to try power + volume down when i wrote this post, sorry xD
Click to expand...
Click to collapse
So it seems you have got it right, but just for future reference:
Power + Volume Up = fastboot/csc
Power + Volume Down = recovery
It goes for most Android devices, ASUS especially.

---

i'm blocked at point 9... it says "cannot read sideload".. i've tried solutions found online like rename folder, or use adb push but in this it says "acces: blocked"..
help please :crying:
news: when i tried the normal boot of the padfone it returned to original conditions, it's like new eek: . factory mode returned like new, too
Now how i can use the other procedure (without sideload) ? i have to put simply the file in the root?

---

Zollolo19 said:
i'm blocked at point 9... it says "cannot read sideload".. i've tried solutions found online like rename folder, or use adb push but in this it says "acces: blocked"..
help please :crying:
news: when i tried the normal boot of the padfone it returned to original conditions, it's like new eek: . factory mode returned like new, too
Now how i can use the other procedure (without sideload) ? i have to put simply the file in the root?
Click to expand...
Click to collapse
I see no reason why sideload or push shouldn't work. When you enter CWM recovery you select the sideload option and then send your ROM from the PC. On Debian and derivatives (Ubuntu, Mint, etc.) adb/fastboot tools are in system locations, so you need to run the commands with "sudo" to elevate your privileges.
Here are the detailed steps:
Boot into fastboot mode (Power, Volume up)
Install the CWM recovery: sudo fastboot -i 0x0b05 flash recovery cwm.img
Boot into recovery mode (Power, Volume down)
Select "wipe data/factory reset"
Select "install zip from sideload"
Send the ROM to the phone: sudo adb sideload ROMNAME.zip
Wait until it says it's done, then select "reboot"
When CWM asks "ROM may flash stock rocovery on boot. Fix?" Choose "No"
When CWM asks "ROM access possibly lost. Fix?" Choose "No"
Alternatively, you could simply plug in your phone, copy the ROM to the root folder (/sdcard) using nautilus/nemo or any other file manager you're using, then go to CWM and select "Install zip from SD card", then browse for it.
As for your phone looking like a fresh one, it's because you still have the stock ROM and it has been reset to factory settings. This should not bother you at all.

---

I tried everything with ubuntu but nothing... so i put the rom in the root and flashed by sd card. Everything seems to be ok now DDD I'm trying your rom like now.
Thanks a lot

---

Hey im happy to see a nice Rom for my womens padfone 2! The only Problem is the i have a Invalidit kernel.. And no boot for me) = i can only boot with Superboot trick. I need help to repair this phone.. please help me.

---

locce said:
Hey im happy to see a nice Rom for my womens padfone 2! The only Problem is the i have a Invalidit kernel.. And no boot for me) = i can only boot with Superboot trick. I need help to repair this phone.. please help me.
Click to expand...
Click to collapse
I think we need to know a little bit more about your problem to see if there is help:
- How did you get an invalid kernel?
- Is the device unlocked/do you have custom recovery on it?

---

Im New in the asus sector...okay I have root with towelroot and forget to unlock the bootloader!!! The not normal booting and Invalid kernel Problem is coming from twrp flash.

---

locce said:
Im New in the asus sector...okay I have root with towelroot and forget to unlock the bootloader!!! The not normal booting and Invalid kernel Problem is coming from twrp flash.
Click to expand...
Click to collapse
Unlocking the bootloader is always the first step. You can fix things, though. First, remove towelroot, and any other rooting mechanisms you may have - you do not need them, custom roms are pre-rooted.
If you are running a 4.1 or 4.2 ROM follow the points from this post
If you have KitKat, it is a bit more complicated, see this post
WARNING: If your device has been serviced (specifically the motherboard replaced), you will not be able to unlock it!