04-30-2016, 01:55 AM
(This post was last modified: 04-30-2016, 02:31 AM by MrWizerd.
Edit Reason: xpossed framework
)
(04-30-2016, 01:36 AM)rakib-hasan Wrote:(04-30-2016, 12:31 AM)tllim Wrote:(04-30-2016, 12:22 AM)rakib-hasan Wrote: Tried the rooted DD image. Worked great.
Also, tried the phoenix card image. Couldn't get it to boot. Waited for 20 minutes for the initial boot. Didn't get past the initial "android" screen. It didn't even show the Pine64 screen (where I assume it extracts the OS).
Anyone successful with the phoenix card image?
Strange, the DD image read from the boot up microSD card that created by Phoenix card.
Tried 4 times in a row. It worked twice and failed twice. Must be a PhoenixCard issue (although it finished successfully). But at least, I have it working now. Thanks @tllim
(04-30-2016, 12:35 AM)tllim Wrote:(04-29-2016, 11:22 PM)rakib-hasan Wrote: @tllim, Thanks for the build and the next build plan. Do you have any plan to include HDMI-CEC?
Since my sdcard is 32GB, I am going to use the phoenix card method and based on the description, it seems that the phoenix card image is rootable but not rooted. Can anyone suggest a method (preferably an easy one ) to root that image?
Noted on the HDMi-CE request, sorry that this request not in my top priority list but I will check on.
The PhoenixCard image can be root, just execute the superSU app, select "norma;" option, and the app will detected the image can be root and starts the rooted process (need to reboot).
Thanks for the quick response.
I had to format and re-flash on phoenix several times before it took without error. But once it wrote without error it booted up on the first try. It probably took around 15-30 minutes, but I was not timing it. On initial boot I did NOT have any access to the network. I rebooted the unit and after reboot it optimized two applications, and then the network was working. I don't know why it wouldn't initialize the network after the first boot but if anyone is having issues with network after first boot they should try a reboot. I don't know if it keeps a log of what it optimized or were to check to see if it did something on that second boot that fixed the network or not. IF someone is interested in that information and knows were it may be I am willing to retrieve it for you just let me know where it is. SuperSU Binaries are loaded and I am cycling the unit for boot 3 now. Everything seems in order for the root. If anything is amiss I will report back.
Everything still seems to be running well. I have run into compatibility issues for a few things, none of them a huge issue, but both Amazon's main program as well as paypal report they are incompatible with my device. I was going to install a program that makes it super easy to change the device info so I can grab them that way but I forgot it uses the xposed framework. That requires a bootloader like TWRP... SO I will have to figure a way around that... Although that may be a new thread issue... not sure... it is a root issue, but... different software this is more about the actual android root itself... any thoughts on xposed framework and or weather a new thread should be made for it?
(*All that said, I know of other ways around these issues, the easiest may be to just download the apk's elsewhere, doing searches for things like that is faster with a full browser but until my USB hub or second pine64+Wifi/Bluetooth arrives I am stuck with just two ports for my keyboard and mouse)