Related
I present to you
Project POC - Phoenix OS Custom
I spend countless nights developing roms, awesome mods, and scripts, if you wish to support my work and future developments you can donate to me via the link here!
Features:
1.Pre-rooted with SuperSU 2.76
2.Busybox
3.CM File Manager (root access to files)
4.Deodexed
5.Adaway
Changelog for Project POC
V1.1.0
First Build
Added SuperSU 2.76
Added Busybox
Added CM File Manager
Added Deodex
Added Adaway
Install Instructions:
1. Extract Project POC
2. Run Phoenix OS Installation Tool
3. Select desired install location: Hard Disk or USB
4. Select target drive and partition
5. Press next and choose data partition size and continue to allow the installer to finish
6. Copy system.img from the POC zip you extracted to the install location (eg. C:\PhoenixOS\)
Downloads:
Google Drive
32-bit only:
V1.1.0 https://drive.google.com/open?id=0B-mpriMWe2WUcjhhbnZXNzdYUHM
Credits:
PhoenixOS for providing us with an awesome OS
@Chainfire for SuperSU
@Stericson for Busybox
@mrRobinson for Adaway
Android (Google) for Android
CyanogenMod Team for the apps
I spend countless nights developing roms, awesome mods, and scripts, if you wish to support my work and future developments you can donate to me via the link here!
I am trying to install on ASUS T100, no windows. I get usb stick made and it just boots to GNU GRUB grub> command line. Any ideas?
Thanks in advance,
Gary
I'm guessing this breaks OTA of official phoenix OS, but do let me know if my assumption is incorrect
meanhacker said:
I'm guessing this breaks OTA of official phoenix OS, but do let me know if my assumption is incorrect
Click to expand...
Click to collapse
I'm not entirely sure of this, but it could possibly have broken the ability to update via OTA.
It would make sense that OTA Updates won't work due to foreign files (SU, CM APPS) in the system partition.
Does it replace win bootloader with grub?
Hey guys, today I downloaded the updated Phoenix OS and decided to root it. I'm kindly sharing my image for anyone who would like to download it:
Instructions:
Install Phoenix OS v2.0.6 and do not restart your computer
Download the correct system rooted.7z file provided in the Download section and extract it
Go to C:\Phoenix OS (or wherever your Phoenix OS installation is) and replace the system.img file that's already there with the one you just downloaded
Reboot your computer now and boot into Phoenix OS. Complete the setup wizard
Install the latest version of SuperSU. Since Phoenix OS v2.0.6 comes with Play Store already, sign in with your Google account and update SuperSU that way. If you for some reason cannot use the Play Store, you can find SuperSU on the official thread. Download the flashable zip, extract Superuser.apk from the common folder, and install it in Phoenix OS by opening the .apk file with the default file manager that comes with the OS.
Update the binary by choosing Normal and your Phoenix OS should now be fully rooted
Download:
Phoenix OS x86 v2.0.6 (26 May) Rooted Image + grub.cfg + original system.img + PhoenixOSInstaller-v2.0.6.145.32bit.exe
https://drive.google.com/open?id=0B_UTWXKFnZoNZGhVNTFpSHRtUnc
Phoenix OS x64 v2.0.6 (26 May) Rooted Image + grub.cfg + original system.img + PhoenixOSInstaller-v2.0.6.144.64bit.exe
https://drive.google.com/open?id=0B_UTWXKFnZoNdVBMOGtDY3RSdEk
Download Phoenix OS v2.0.6 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6010
History:
Uploaded original Phoenix OS system.img (for backup)
Uploaded Phoenix OS executable installers (for backup mirroring purposes)
Added x86 version of the rooted image
Compressed the system.img file so that it's faster for you to download!
[Request][Root] Phoenix OS x86 v2.0.6
Hey first of all finally i found the way to root Phoenix OS but there is a problem i have x86 bit version of Phoenix OS so i was hoping you could help out so could you kindly provide a rooted Phoenix OS x86 bit system.img please or tell me the method to root it i would appreciate the help.
And by the way i have a question i have a 64-bit operating system but when i installed Phoenix OS it said it is recommended to install the x86 bit version so i installed the x86 bit version so should i use the 64 or 86 bit version ????
Well the x86 bit version works fine but some glitches can be seen and it gets stuck if i leave it inactive for some time.
farazmajid56 said:
Hey first of all finally i found the way to root Phoenix OS but there is a problem i have x86 bit version of Phoenix OS so i was hoping you could help out so could you kindly provide a rooted Phoenix OS x86 bit system.img please or tell me the method to root it i would appreciate the help.
And by the way i have a question i have a 64-bit operating system but when i installed Phoenix OS it said it is recommended to install the x86 bit version so i installed the x86 bit version so should i use the 64 or 86 bit version ????
Well the x86 bit version works fine but some glitches can be seen and it gets stuck if i leave it inactive for some time.
Click to expand...
Click to collapse
Hey, I can work on getting the x86 version of the rooted image for you The method which I used could be found here.
Also, that suggestion sounds incorrect. What OS exactly are you running? Tell me more about your computer specs (CPU, Windows version, and especially how much RAM you have). If you have 4GB of RAM or more, I would go for the x64 version of Phoenix OS. Try it out and let us know if it works better for you, though there might not be much difference in performance. If I remember correctly, my Phoenix OS also causes my screen to go black after it's been sitting inactively for a while. I think it's a common issue with Phoenix OS.
meanhacker said:
Hey, I can work on getting the x86 version of the rooted image for you The method which I used could be found here.
Also, that suggestion sounds incorrect. What OS exactly are you running? Tell me more about your computer specs (CPU, Windows version, and especially how much RAM you have). If you have 4GB of RAM or more, I would go for the x64 version of Phoenix OS. Try it out and let us know if it works better for you, though there might not be much difference in performance. If I remember correctly, my Phoenix OS also causes my screen to go black after it's been sitting inactive for a while. I think it's a common issue with Phoenix OS.
Click to expand...
Click to collapse
The specs of my PC are
CPU: Core 2 Duo 2.4 Ghz (64-bit Architecture)
RAM: 6 GB
GPU: NVIDIA GeForce 8400 GS with 1 GB VRAM
Operating System: Windows 7 Ultimate 64-bit
I forgot to tell you i am dual booting Windows 7 Ultimate (64-bit) with Phoenix OS (86-bit)
Check these for more info
https://ibb.co/m7AFVv
https://ibb.co/h9khAv
https://ibb.co/kkgB3F
https://ibb.co/eVsJiF
https://ibb.co/hqJDHa
The inactive black screen bug of Phoenix OS has to do something with the lock screen in android which auto locks screen if inactive for some time.
Thanks for the extensive info. It looks like your computer should be able to run the 64-bit version of Phoenix OS just fine. Why don't you give it a try? Also, I posted the x86 version of the rooted image if you still need it.
farazmajid56 said:
The inactive black screen bug of Phoenix OS has to do something with the lock screen in android which auto locks screen if inactive for some time.
Click to expand...
Click to collapse
Good point, I will try to fix it. I'm assuming this issue can be eliminated by disabling the screen lock timeout timer.
meanhacker said:
Thanks for the extensive info. It looks like your computer should be able to run the 64-bit version of Phoenix OS just fine. Why don't you give it a try? Also, I posted the x86 version of the rooted image if you still need it.
Good point, I will try to fix it. I'm assuming this issue can be eliminated by disabling the screen lock timeout timer.
Click to expand...
Click to collapse
Precisely and by the way Thanks
farazmajid56 said:
Precisely and by the way Thanks
Click to expand...
Click to collapse
You got it! Let me know if you need anything else :good:
Root is working fine, but the one app that won't install successfully for me is Google Plus. It claims my "device isn't compatible with this version" which is weird, given that it worked in previous versions of Phoenix OS. Any thoughts on this? Chinese localization or something maybe?
Edit: I can't even install it if I download it from APKMirror btw.
The Wrath of Kahn said:
Root is working fine, but the one app that won't install successfully for me is Google Plus. It claims my "device isn't compatible with this version" which is weird, given that it worked in previous versions of Phoenix OS. Any thoughts on this? Chinese localization or something maybe?
Edit: I can't even install it if I download it from APKMirror btw.
Click to expand...
Click to collapse
Hmm thanks for bringing it up. I haven't tried the app on Phoenix OS. Does it work on the original non-rooted version of Phoenix? Give it a try and let us know.
I've noticed that there are several apps that don't work for some reason. Some of the apps I use often give me an Error 501 when trying to install from anywhere. I've tried everything and still haven't gotten them to work. Hopefully more compatibility is coming soon.
meanhacker said:
Hmm thanks for bringing it up. I haven't tried the app on Phoenix OS. Does it work on the original non-rooted version of Phoenix? Give it a try and let us know.
Click to expand...
Click to collapse
Yea, it doesn't work in the non-rooted version either. Probably a build.prop issue with whatever the device is being identified as. I tried to modify it several ways, but couldn't get it working. It worked in previous versions, so I'm hoping they'll correct it soon. I'll report it in the official forums too.
Hi
After installing the PhoenixOS, the Windows Boot Manager(the blue screen one) did not appear when booting,it will boot into the windows 10 directly and I cant select to boot into the Phoenix OS.So I need to press the F12 button everytime i power on my laptop to choose whether i want to boot into windows or phoenix OS via the bios boot manager.Is there any solution to make my Phoenix detectable by Windows Boot Manager?
kirito990701 said:
Hi
After installing the PhoenixOS, the Windows Boot Manager(the blue screen one) did not appear when booting,it will boot into the windows 10 directly and I cant select to boot into the Phoenix OS.So I need to press the F12 button everytime i power on my laptop to choose whether i want to boot into windows or phoenix OS via the bios boot manager.Is there any solution to make my Phoenix detectable by Windows Boot Manager?
Click to expand...
Click to collapse
Chances are, Windows Boot Manager got moved up in the boot sequence. Using EasyUEFI, you can move the Phoenix OS entry back up so it starts booting:
Download and install EasyUEFI.
Open it, click OK, click Manage EFI Boot Option and post what you see here. This is your boot order. If Windows Boot Manager is above Phoenix OS, that means that Windows is being loaded using its default boot loader. What you're trying to do is use the Phoenix OS GRUB loader.
Click on Phoenix OS and click the green up arrow until the Phoenix OS entry is at the very top.
Restart the computer and see if it boots to the GRUB loader.
If it doesn't work, let's investigate what's inside your EFI partition.
First, open command prompt as admin (press start, type in cmd, press Ctrl+Shift+Enter, then press yes). Type in:
Code:
mountvol X: /s
Then type in:
Code:
cd X:\EFI\Boot
And then type in
Code:
dir
and press enter. It should list all the files in that boot directory. Post here on the forum what you see. You can use the command
Code:
dir >>C:\xda-efi-output.txt
to output to a text file and then it would make it easier for you to post it here. The file is located on the root of the C:\ drive. Open it and copy-paste what's inside on the forum, preferably inside code or hide tags to keep it neat. Assuming it's there, you can type in
Code:
grub.cfg
which will open the file with your default text editor. Feel free to post what's inside your grub file.
meanhacker said:
Hey guys, today I downloaded the updated Phoenix OS and decided to root it. I'm kindly sharing my image for anyone who would like to download it:
Instructions:
Install Phoenix OS v2.0.6 and do not restart your computer
Download the correct system rooted.7z file provided in the Download section and extract it
Go to C:\Phoenix OS (or wherever your Phoenix OS installation is) and replace the system.img file that's already there with the one you just downloaded
Reboot your computer now and boot into Phoenix OS. Complete the setup wizard
Install the latest version of SuperSU. Since Phoenix OS v2.0.6 comes with Play Store already, sign in with your Google account and update SuperSU that way. If you for some reason cannot use the Play Store, you can find SuperSU on the official thread. Download the flashable zip, extract Superuser.apk from the common folder, and install it in Phoenix OS by opening the .apk file with the default file manager that comes with the OS.
Update the binary by choosing Normal and your Phoenix OS should now be fully rooted
Download:
Phoenix OS x86 v2.0.6 (26 May) Rooted Image + grub.cfg + original system.img + PhoenixOSInstaller-v2.0.6.145.32bit.exe
https://drive.google.com/open?id=0B_UTWXKFnZoNZGhVNTFpSHRtUnc
Phoenix OS x64 v2.0.6 (26 May) Rooted Image + grub.cfg + original system.img + PhoenixOSInstaller-v2.0.6.144.64bit.exe
https://drive.google.com/open?id=0B_UTWXKFnZoNdVBMOGtDY3RSdEk
Download Phoenix OS v2.0.6 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6010
History:
Uploaded original Phoenix OS system.img (for backup)
Uploaded Phoenix OS executable installers (for backup mirroring purposes)
Added x86 version of the rooted image
Compressed the system.img file so that it's faster for you to download!
Click to expand...
Click to collapse
Hi Successfully Installed Phoenix os with rooted Image, updated superSu app using Playstore, but I am unable to access to root i.e unable to check log using Log cat apk,
nanianji99 said:
Hi Successfully Installed Phoenix os with rooted Image, updated superSu app using Playstore, but I am unable to access to root i.e unable to check log using Log cat apk,
Click to expand...
Click to collapse
Hey, I don't know what the problem could be. Do other root apps work? Maybe try using another logcat app
meanhacker said:
Chances are, Windows Boot Manager got moved up in the boot sequence. Using EasyUEFI, you can move the Phoenix OS entry back up so it starts booting:
Download and install EasyUEFI.
Open it, click OK, click Manage EFI Boot Option and post what you see here. This is your boot order. If Windows Boot Manager is above Phoenix OS, that means that Windows is being loaded using its default boot loader. What you're trying to do is use the Phoenix OS GRUB loader.
Click on Phoenix OS and click the green up arrow until the Phoenix OS entry is at the very top.
Restart the computer and see if it boots to the GRUB loader.
If it doesn't work, let's investigate what's inside your EFI partition.
First, open command prompt as admin (press start, type in cmd, press Ctrl+Shift+Enter, then press yes). Type in:
Code:
mountvol X: /s
Then type in:
Code:
cd X:\EFI\Boot
And then type in
Code:
dir
and press enter. It should list all the files in that boot directory. Post here on the forum what you see. You can use the command
Code:
dir >>C:\xda-efi-output.txt
to output to a text file and then it would make it easier for you to post it here. The file is located on the root of the C:\ drive. Open it and copy-paste what's inside on the forum, preferably inside code or hide tags to keep it neat. Assuming it's there, you can type in
Code:
grub.cfg
which will open the file with your default text editor. Feel free to post what's inside your grub file.
Click to expand...
Click to collapse
Sorry but i cant find the PhoenixOS from the EasyUEFI entries list...
Here is the text file
Phoenix OS x86/x64 v2.0.7
hi .... good new ... new release is out today as:
Phoenix OS x86/x64 v2.0.7
kirito990701 said:
Sorry but i cant find the PhoenixOS from the EasyUEFI entries list...
Here is the text file
Click to expand...
Click to collapse
The solution is to add it yourself.
When in EasyUEFI:
1. click the add button.
2. From type list select Linux/Other.
3. Add a Description (this is what it will be called in the UEFI menu).
4. Select your efi partition (the FAT32 one with the light dot).
5. Click Browse
6. Select \EFI\PhoenixOS\bootx64.efi and click OK.
7. Click OK
8. Use arrows to reorder list to your needs.
And that text file you put up seems to be nothing to do with your EFI. It's a list of your windows directory.
TNTPro said:
The solution is to add it yourself.
When in EasyUEFI:
1. click the add button.
2. From type list select Linux/Other.
3. Add a Description (this is what it will be called in the UEFI menu).
4. Select your efi partition (the FAT32 one with the light dot).
5. Click Browse
6. Select \EFI\PhoenixOS\bootx64.efi and click OK.
7. Click OK
8. Use arrows to reorder list to your needs.
And that text file you put up seems to be nothing to do with your EFI. It's a list of your windows directory.
Click to expand...
Click to collapse
Thank you so much to reply this. And again...after the phoenix os is added into the list and moved to the uppest side...I tried to restart my laptop but it still boots into windows without the system selection screen. After that I checked the list in EastUEFI and the phoenix os was missing again from the list :silly:
kirito990701 said:
Thank you so much to reply this. And again...after the phoenix os is added into the list and moved to the uppest side...I tried to restart my laptop but it still boots into windows without the system selection screen. After that I checked the list in EastUEFI and the phoenix os was missing again from the list :silly:
Click to expand...
Click to collapse
What kind of laptop do you have? It sounds like your bootloader is locker. Try going into BIOS and disabling "Secure Boot" or whatever is available from your motherboard. Also, since you couldn't find the Phoenix OS entry, maybe you should try reinstalling Phoenix OS.
Hi all,
I'm trying to install magisk on Phoenix Os. Without a recovery I tried to install it via the magisk manager but I can't see the boot partition to patch via the app... So I tried to patch the ramdisk manually but ./magiskboot and . /magisk (from x64) seems not to work... Don't know how to patch it... Does anyone have any idea how to do it?
Thanks.
Ps
No custom recovery are installable (and it is not useful because if Magisk manager can't detect boot partition also the zip can't); Phoenix Os is for common PC, in fact I have in triple boot with windows and ubuntu
Bump
P.S. custom recovery for Phoenix OS running off USB?
Bump
This would be very nice, but I am equally useless at making this sort of thing work.
I was able to install Magisk V12.0 on Android x86 7.1.2 rc2, using this tools to create a "fake" boot.img using kernel and ramdisk.img files:
https://forum.xda-developers.com/showthread.php?t=2319018
But I had to make small modifications in the install scripts and magic_mask.sh to bypass some errors and correctly mount system to the magisk folder. Newer versions don't have magic_mask.sh anymore but a binary, so unless you modify the source and compile it yourself I think it won't work. Probably because v12.0 is somewhat old I can't install modules automatically using Magisk Manager tho...
Yesterday, I installed PhoenixOS v2.5.9.375 on an old laptop, and I must say that I really like the Android experience on a laptop that I thought was too old to be good for anything. One problem that I am having though is that I cannot update Google Play Services which is preventing some of the GApps that I want to use from working. I tried using the instructions in this thread to fix the problem, but sadly they do not work with this version of the OS, and I get an error message saying "App not installed" when I try to fix it this way. I also so this, which looked promising until I learned that it requires a dual boot into Windows, and I am using PhoenixOS exclusively on my laptop, meaning that this is ruled out as an option.
Does anyone have any suggestions?
I am having the same issue with my Google Play Services, but the one I provided in the thread works with Google Play Games at least. I wonder why Phoenix OS comes with version number beginning with 070... This version is for x86 and for Android 4.0+ nodpi (according to apkmirror). Shouldn't Phoenix OS come with 270 or 480 since Phoenix OS 64-bit runs on Android 7.1.1 (32-bit runs on 5.1)? If so, my instinct is telling me that we have to forcefully install the updated Google Play Services (probably along with Google Play Store and Google Services Framework) to get it working correctly. This cold probably be done with root, so at least we know we can fully root the OS and work our way from there.
I have that problem also before... I downloaded the updated Google Play service in apkmirror, tried to manually installed it but still it wont install... But what I did in order to fix it is first to disable the Play Service on the App Settings and then I use Root Explorer to locate the location of the Gplayservice which is /system/priv-app/GmsCore. so what I did i rename the GPlayService that I downloaded into GmsCore.apk and then replace the app on /system/priv-app/GmsCore and change permission to "rw-r-r". and re-enabling back the GPlayService on that App Settings and reboot.... at Viola its fix... now I dont have an error on it anymore...
killerBEE07 said:
I have that problem also before... I downloaded the updated Google Play service in apkmirror, tried to manually installed it but still it wont install... But what I did in order to fix it is first to disable the Play Service on the App Settings and then I use Root Explorer to locate the location of the Gplayservice which is /system/priv-app/GmsCore. so what I did i rename the GPlayService that I downloaded into GmsCore.apk and then replace the app on /system/priv-app/GmsCore and change permission to "rw-r-r". and re-enabling back the GPlayService on that App Settings and reboot.... at Viola its fix... now I dont have an error on it anymore...
Click to expand...
Click to collapse
If this really works, then I will update my thread. What variant and version did you download? Can you provide a bit more information?
Thank you for the info, this looks very promising, please could you let us know which version you downloaded
Hi all,
This is how I got it working, several ways actually:
Using the toolkit http://bbs.phoenixstudio.org/en/showthread.php?tid=9661
Extract the system.img from the downloaded installation EXE or copy the system.img from your install directory
Make sure you download the GAPPS7.1 in the above post and put it in the \tools directory of the toolkit
Follow the toolkit to unpack/update GAPPS/repack
Copy the system.img back to your installed directory (C:\PhoenixOS)
Hacking it yourself
Download the latest GAPPS 7.1 PICO
Replace the APK in the GAPPS package over the ones installed on your PhoenixOS
Does this method require you to have a dual boot setup? Because I don't.
Android PC tool works!!
Used the PC tool and it worked flawlessly. On another note i have been trying to tinker with the OS and found out that the system cannot be mounted as r/w. Tried the command
Code:
su mount -o rw,remount /system
which gives me /dev/loop0 is write-protected mounting read-only. Is there any way fix to this.
meanhacker said:
If this really works, then I will update my thread. What variant and version did you download? Can you provide a bit more information?
Click to expand...
Click to collapse
Im using Phoenix 1.5.0 android 5.1.1... I tried it also in the Nougat version and it also works...
killerBEE07 said:
Im using Phoenix 1.5.0 android 5.1.1... I tried it also in the Nougat version and it also works...
Click to expand...
Click to collapse
Which version of GPlayService did you download and which variant? Post the apkmirror link
meanhacker said:
Which version of GPlayService did you download and which variant? Post the apkmirror link
Click to expand...
Click to collapse
sorry I took so long to reply... here's the link... https://www.apkmirror.com/apk/googl...2-6-73-020700-194189626-android-apk-download/
I hope this will be useful...
killerBEE07 said:
I have that problem also before... I downloaded the updated Google Play service in apkmirror, tried to manually installed it but still it wont install... But what I did in order to fix it is first to disable the Play Service on the App Settings and then I use Root Explorer to locate the location of the Gplayservice which is /system/priv-app/GmsCore. so what I did i rename the GPlayService that I downloaded into GmsCore.apk and then replace the app on /system/priv-app/GmsCore and change permission to "rw-r-r". and re-enabling back the GPlayService on that App Settings and reboot.... at Viola its fix... now I dont have an error on it anymore...
Click to expand...
Click to collapse
dude thanks a lot it did work now its updated to last version
andyle2k said:
Hi all,
This is how I got it working, several ways actually:
Using the toolkit http://bbs.phoenixstudio.org/en/showthread.php?tid=9661
Extract the system.img from the downloaded installation EXE or copy the system.img from your install directory
Make sure you download the GAPPS7.1 in the above post and put it in the \tools directory of the toolkit
Follow the toolkit to unpack/update GAPPS/repack
Copy the system.img back to your installed directory (C:\PhoenixOS)
Hacking it yourself
Download the latest GAPPS 7.1 PICO
Replace the APK in the GAPPS package over the ones installed on your PhoenixOS
Click to expand...
Click to collapse
Hi, I put the gapps in the tools directory, but I don't understand what you mean by follow the toolkit to unpack/update GAPPS/ repack. Am I supposed to make those folders? When I go to the unpack folder, just my system image is in there.
I'd like to share my experiences about bringing a good old TF101G back to life in 03/2021. My report is heavily based on the instructions of javidben (05/2020).
IngredientsRequired:
A microSD card, SD card or USB drive
TWRP 2.8.1.1 by Team Win Recovery Project, @sidneyk, @josteink, @timduru
Katkiss 6.0.3.4 by @timduru
Super User 2.52 Beta by @Chainfire
Xposed Module by @rovo89 (03/2021: v3.1.5)
Xposed Framework SDK23 by @rovo89 (03/2021: v89)
MicroG Services Core by the microG Team, @MaR-V-iN (03/2021: v0.2.17.204714)
MicroG Services Framework Proxy by the microG Team, @MaR-V-iN (03/2021: v0.1.0)
NanoDroid-microG by @Setialpha (03/2021: v23.1.2.20210117)
F-Droid by Team F-Droid (03/2021: v1.11)
MiXplorer by @HootanParsa (03/2021: v6.53.7)
PeaZip by PeaZip SRL (03/2021: v7.8.0) or any other tool to extract a ZST compressed file
Optional and recommended:
fsync_on.zip by @timduru to avoid random reboots caused by corrupted data
Katkiss V2.2.0 by @timduru
Wakelock v3 by @Dark3n to avoid reboots in deep sleep (TF101G only)
InstructionsOn your PC
Download all files and save everything except PeaZip on the SD card.
Open NanoDroid-microG-???.zip and extract the file system/priv-app/PhoneSky/PhoneSky.apk.zst.
Use PeaZip to decompress PhoneSky.apk.zst to PhoneSky.apk.
Rename PhoneSky.apk to com.android.vending.apk and save it on the SD card.
On the tablet
Boot into TWRP 2.8.1.1 Recovery (Hold Vol Down and Power Button).
Wipe/Format Data.
Flash (in order):
Katkiss 6.0.34
SuperUser 2.52 Beta
optional: fsync_on
optional: KatKiss V2.2.0
Xposed SDK 23
Reboot into Android. Do not enable Wi-Fi yet.
Once in Android, select the SD card notification and setup the SD card as external memory.
Touch the notification again to see a simple file explorer showing the files on the SD card.
Copy the following files to the Downloadsdirectory in internal memory:
F-Droid
MiXplorer
MicroG Services Core
MicroG Services Framework Proxy
Xposed Module
Go to the app drawer, open app Downloads and install in order:
F-Droid
MiXplorer
MicroG Services Core (com.google.android.gms-???.apk)
MicroG Services Framework (com.google.android.gsf-???.apk)
Xposed Module
Go to the app drawer, open F-Droidand
Go to settings, enable Expert Mode and Unstable updates
Turn on Wi-Fi and refresh F-Droid Repository
Search & Install Apple UnifiedNlp Backend
Search & Install NominatimNlpBackend
Go to the app drawer, open MicroG Settings and
Go to Self Check, grant all permissions and enable Battery optimizations ignored
Go to Google device registration and enable it
Go to Google Cloud Messaging and enable it
Go to Location modules and enable Apple Wi-Fi; if possible, enable Nominatim.
Go to the app drawer, open Xposedand
Go to Download, search FakeGApps and install FakeGApps 2.0
Go to Modules tab and activate FakeGApps
Reboot the device.
Go to the app drawer, open MicroG Settings and select Self-Check.
Now you should have everything but Play Store checklisted.
Go to the app drawer, open MiXPlorerand
Copy file com.android.vending.apk to Root/system/priv-app
Select the file com.android.vending.apk, press Info (top right), select Permissions and set to 755 (executable).
Go to Root/data/app and create empty files
com.android.vending
com.android.vending-1
com.android.vending-2
Select the empty files, press Info (top right), select Permissions and set to 755 (executable).
Go to the app drawer, open MicroG Settings and select Self-Check.
Now you should have everything checked.
Reboot your device.
Go to the app drawer, open MicroG Settings, select Account and login into your Google account.
For TF101G only (to prevent reboots in deep sleep):
Install Wakelock
Enable Wakelock Processor
Go to Settings and enable Autostart on boot
App compatibilityAlthough the TF101G runs Marshmallow, a lot of Marshmallow-compatible apps do not work on the device. The reason is that the CPU does not support the NEON instruction set. Nowadays, most apps expect a NEON-compatible CPU. Google dropped support of non-neon phones and tablets with Android 4.2 in 2013. My observation is that apps compiled for Android <4.2 have a good chance to work without problems on the device. So, if you're looking for a certain app in of the apk portals, filter by target platform Android <4.2 (Jelly Bean).
These specific versions do work on the TF101G:
Chromium 76 for Tegra2 by @decatf
Fennec 59 for Tegra2 by schmaller
Firefox 52.0.2
VLC 3.0.13
Kodi 17.6 without NEON instructions by tetramarreta
RemarksFlashing NanoDroid no longer possible from v22In the previous tutorials, the ZIP files NanoDroid-FDroid and NanoDroid-Patcher have been recommended instead of installing the APKs. I found out these ZIPs are not usable anymore because the zstd binary within them is not compatible with the TF101. Trying to flash these files results in an error message
Code:
failed to decompress /system/app/FDroid/FDroid.apk.zst
I found out that the binary zstd.arm that is part of the ZIP crashes with a Illegal instruction on the device. The same file works on a Raspberry Pi (also armv7), so I guess it's compiled against the NEON instruction set. Maybe an older version (v21.0) from the NanoDroid Archive works, but I didn't try. NanoDroid #197 addresses this issue.
Backup feature broken in TWRP 2.8.1.1It seems that the Backup feature does not work in TWRP 2.8.1.1. When starting a backup, the screen turns off (feels like a little crash); when turned on again, TWRP is still on the same page but no backup was created and no process is running. Using an older version (e.g. twrp-2.6.3.0-7_tf101g.zip) works. So as a workaraound, you can flash the old TWRP, do the backup and finally flash 2.8.1.1 again.
CreditsThanks to @timduru for the great KatKiss ROM. Thanks to the community for all the infos and details in >1.500 posts allowing a 10-year old device to do a good job in 2021.
All I did was reading, executing and documenting the steps described in the
Tutorial of @javidben (05/2020)
Tutorial of @alexchandra (12/2018)
Tutorial of @EpicCentr (11/2018)
-christian- said:
I'd like to share my experiences about bringing a good old TF101G back to life in 03/2021. My report is heavily based on the instructions of javidben (05/2020).
IngredientsRequired:
A microSD card, SD card or USB drive
TWRP 2.8.1.1 by Team Win Recovery Project, @sidneyk, @josteink, @timduru
Katkiss 6.0.3.4 by @timduru
Super User 2.52 Beta by @Chainfire
Xposed Module by @rovo89 (03/2021: v3.1.5)
Xposed Framework SDK23 by @rovo89 (03/2021: v89)
MicroG Services Core by the microG Team, @MaR-V-iN (03/2021: v0.2.17.204714)
MicroG Services Framework Proxy by the microG Team, @MaR-V-iN (03/2021: v0.1.0)
NanoDroid-microG by @Setialpha (03/2021: v23.1.2.20210117)
F-Droid by Team F-Droid (03/2021: v1.11)
MiXplorer by @HootanParsa (03/2021: v6.53.7)
PeaZip by PeaZip SRL (03/2021: v7.8.0) or any other tool to extract a ZST compressed file
Optional and recommended:
fsync_on.zip by @timduru to avoid random reboots caused by corrupted data
Katkiss V2.2.0 by @timduru
Wakelock v3 by @Dark3n to avoid reboots in deep sleep (TF101G only)
InstructionsOn your PC
Download all files and save everything except PeaZip on the SD card.
Open NanoDroid-microG-???.zip and extract the file system/priv-app/PhoneSky/PhoneSky.apk.zst.
Use PeaZip to decompress PhoneSky.apk.zst to PhoneSky.apk.
Rename PhoneSky.apk to com.android.vending.apk and save it on the SD card.
On the tablet
Boot into TWRP 2.8.1.1 Recovery (Hold Vol Down and Power Button).
Wipe/Format Data.
Flash (in order):
Katkiss 6.0.34
SuperUser 2.52 Beta
optional: fsync_on
optional: KatKiss V2.2.0
Xposed SDK 23
Reboot into Android. Do not enable Wi-Fi yet.
Once in Android, select the SD card notification and setup the SD card as external memory.
Touch the notification again to see a simple file explorer showing the files on the SD card.
Copy the following files to the Downloadsdirectory in internal memory:
F-Droid
MiXplorer
MicroG Services Core
MicroG Services Framework Proxy
Xposed Module
Go to the app drawer, open app Downloads and install in order:
F-Droid
MiXplorer
MicroG Services Core (com.google.android.gms-???.apk)
MicroG Services Framework (com.google.android.gsf-???.apk)
Xposed Module
Go to the app drawer, open F-Droidand
Go to settings, enable Expert Mode and Unstable updates
Turn on Wi-Fi and refresh F-Droid Repository
Search & Install Apple UnifiedNlp Backend
Search & Install NominatimNlpBackend
Go to the app drawer, open MicroG Settings and
Go to Self Check, grant all permissions and enable Battery optimizations ignored
Go to Google device registration and enable it
Go to Google Cloud Messaging and enable it
Go to Location modules and enable Apple Wi-Fi; if possible, enable Nominatim.
Go to the app drawer, open Xposedand
Go to Download, search FakeGApps and install FakeGApps 2.0
Go to Modules tab and activate FakeGApps
Reboot the device.
Go to the app drawer, open MicroG Settings and select Self-Check.
Now you should have everything but Play Store checklisted.
Go to the app drawer, open MiXPlorerand
Copy file com.android.vending.apk to Root/system/priv-app
Select the file com.android.vending.apk, press Info (top right), select Permissions and set to 755 (executable).
Go to Root/data/app and create empty files
com.android.vending
com.android.vending-1
com.android.vending-2
Select the empty files, press Info (top right), select Permissions and set to 755 (executable).
Go to the app drawer, open MicroG Settings and select Self-Check.
Now you should have everything checked.
Reboot your device.
Go to the app drawer, open MicroG Settings, select Account and login into your Google account.
For TF101G only (to prevent reboots in deep sleep):
Install Wakelock
Enable Wakelock Processor
Go to Settings and enable Autostart on boot
App compatibilityAlthough the TF101G runs Marshmallow, a lot of Marshmallow-compatible apps do not work on the device. The reason is that the CPU does not support the NEON instruction set. Nowadays, most apps expect a NEON-compatible CPU. Google dropped support of non-neon phones and tablets with Android 4.2 in 2013. My observation is that apps compiled for Android <4.2 have a good chance to work without problems on the device. So, if you're looking for a certain app in of the apk portals, filter by target platform Android <4.2 (Jelly Bean).
These specific versions do work on the TF101G:
Chromium 76 for Tegra2 by @decatf
Fennec 59 for Tegra2 by schmaller
Firefox 52.0.2
VLC 3.0.13
Kodi 17.6 without NEON instructions by tetramarreta
RemarksFlashing NanoDroid no longer possible from v22In the previous tutorials, the ZIP files NanoDroid-FDroid and NanoDroid-Patcher have been recommended instead of installing the APKs. I found out these ZIPs are not usable anymore because the zstd binary within them is not compatible with the TF101. Trying to flash these files results in an error message
Code:
failed to decompress /system/app/FDroid/FDroid.apk.zst
I found out that the binary zstd.arm that is part of the ZIP crashes with a Illegal instruction on the device. The same file works on a Raspberry Pi (also armv7), so I guess it's compiled against the NEON instruction set. Maybe an older version (v21.0) from the NanoDroid Archive works, but I didn't try. NanoDroid #197 addresses this issue.
Backup feature broken in TWRP 2.8.1.1It seems that the Backup feature does not work in TWRP 2.8.1.1. When starting a backup, the screen turns off (feels like a little crash); when turned on again, TWRP is still on the same page but no backup was created and no process is running. Using an older version (e.g. twrp-2.6.3.0-7_tf101g.zip) works. So as a workaraound, you can flash the old TWRP, do the backup and finally flash 2.8.1.1 again.
CreditsThanks to @timduru for the great KatKiss ROM. Thanks to the community for all the infos and details in >1.500 posts allowing a 10-year old device to do a good job in 2021.
All I did was reading, executing and documenting the steps described in the
Tutorial of @javidben (05/2020)
Tutorial of @alexchandra (12/2018)
Tutorial of @EpicCentr (11/2018)
Click to expand...
Click to collapse
I can also confirm that Spotify 8.4.30.688, Elementum 0.1.74 (installed from zip manually), MX Player 1.10.50, BubbleUPnP 3.2.3, and Netflix 4.16.4 are working perfectly under @timduru's ROM.
Can you add an Tutorial how to root tf101G i cant find anything.
I don't have usb option in recovery mode only boot android and wipe cache/data.
Got it: https://forum.xda-developers.com/t/...bricks-all-devices-27-d.1681155/post-77935324
-christian- said:
I'd like to share my experiences about bringing a good old TF101G back to life in 03/2021. My report is heavily based on the instructions of javidben (05/2020).
IngredientsRequired:
A microSD card, SD card or USB drive
TWRP 2.8.1.1 by Team Win Recovery Project, @sidneyk, @josteink, @timduru
Katkiss 6.0.3.4 by @timduru
Super User 2.52 Beta by @Chainfire
Xposed Module by @rovo89 (03/2021: v3.1.5)
Xposed Framework SDK23 by @rovo89 (03/2021: v89)
MicroG Services Core by the microG Team, @MaR-V-iN (03/2021: v0.2.17.204714)
MicroG Services Framework Proxy by the microG Team, @MaR-V-iN (03/2021: v0.1.0)
NanoDroid-microG by @Setialpha (03/2021: v23.1.2.20210117)
F-Droid by Team F-Droid (03/2021: v1.11)
MiXplorer by @HootanParsa (03/2021: v6.53.7)
PeaZip by PeaZip SRL (03/2021: v7.8.0) or any other tool to extract a ZST compressed file
Optional and recommended:
fsync_on.zip by @timduru to avoid random reboots caused by corrupted data
Katkiss V2.2.0 by @timduru
Wakelock v3 by @Dark3n to avoid reboots in deep sleep (TF101G only)
InstructionsOn your PC
Download all files and save everything except PeaZip on the SD card.
Open NanoDroid-microG-???.zip and extract the file system/priv-app/PhoneSky/PhoneSky.apk.zst.
Use PeaZip to decompress PhoneSky.apk.zst to PhoneSky.apk.
Rename PhoneSky.apk to com.android.vending.apk and save it on the SD card.
On the tablet
Boot into TWRP 2.8.1.1 Recovery (Hold Vol Down and Power Button).
Wipe/Format Data.
Flash (in order):
Katkiss 6.0.34
SuperUser 2.52 Beta
optional: fsync_on
optional: KatKiss V2.2.0
Xposed SDK 23
Reboot into Android. Do not enable Wi-Fi yet.
Once in Android, select the SD card notification and setup the SD card as external memory.
Touch the notification again to see a simple file explorer showing the files on the SD card.
Copy the following files to the Downloadsdirectory in internal memory:
F-Droid
MiXplorer
MicroG Services Core
MicroG Services Framework Proxy
Xposed Module
Go to the app drawer, open app Downloads and install in order:
F-Droid
MiXplorer
MicroG Services Core (com.google.android.gms-???.apk)
MicroG Services Framework (com.google.android.gsf-???.apk)
Xposed Module
Go to the app drawer, open F-Droidand
Go to settings, enable Expert Mode and Unstable updates
Turn on Wi-Fi and refresh F-Droid Repository
Search & Install Apple UnifiedNlp Backend
Search & Install NominatimNlpBackend
Go to the app drawer, open MicroG Settings and
Go to Self Check, grant all permissions and enable Battery optimizations ignored
Go to Google device registration and enable it
Go to Google Cloud Messaging and enable it
Go to Location modules and enable Apple Wi-Fi; if possible, enable Nominatim.
Go to the app drawer, open Xposedand
Go to Download, search FakeGApps and install FakeGApps 2.0
Go to Modules tab and activate FakeGApps
Reboot the device.
Go to the app drawer, open MicroG Settings and select Self-Check.
Now you should have everything but Play Store checklisted.
Go to the app drawer, open MiXPlorerand
Copy file com.android.vending.apk to Root/system/priv-app
Select the file com.android.vending.apk, press Info (top right), select Permissions and set to 755 (executable).
Go to Root/data/app and create empty files
com.android.vending
com.android.vending-1
com.android.vending-2
Select the empty files, press Info (top right), select Permissions and set to 755 (executable).
Go to the app drawer, open MicroG Settings and select Self-Check.
Now you should have everything checked.
Reboot your device.
Go to the app drawer, open MicroG Settings, select Account and login into your Google account.
For TF101G only (to prevent reboots in deep sleep):
Install Wakelock
Enable Wakelock Processor
Go to Settings and enable Autostart on boot
App compatibilityAlthough the TF101G runs Marshmallow, a lot of Marshmallow-compatible apps do not work on the device. The reason is that the CPU does not support the NEON instruction set. Nowadays, most apps expect a NEON-compatible CPU. Google dropped support of non-neon phones and tablets with Android 4.2 in 2013. My observation is that apps compiled for Android <4.2 have a good chance to work without problems on the device. So, if you're looking for a certain app in of the apk portals, filter by target platform Android <4.2 (Jelly Bean).
These specific versions do work on the TF101G:
Chromium 76 for Tegra2 by @decatf
Fennec 59 for Tegra2 by schmaller
Firefox 52.0.2
VLC 3.0.13
Kodi 17.6 without NEON instructions by tetramarreta
RemarksFlashing NanoDroid no longer possible from v22In the previous tutorials, the ZIP files NanoDroid-FDroid and NanoDroid-Patcher have been recommended instead of installing the APKs. I found out these ZIPs are not usable anymore because the zstd binary within them is not compatible with the TF101. Trying to flash these files results in an error message
Code:
failed to decompress /system/app/FDroid/FDroid.apk.zst
I found out that the binary zstd.arm that is part of the ZIP crashes with a Illegal instruction on the device. The same file works on a Raspberry Pi (also armv7), so I guess it's compiled against the NEON instruction set. Maybe an older version (v21.0) from the NanoDroid Archive works, but I didn't try. NanoDroid #197 addresses this issue.
Backup feature broken in TWRP 2.8.1.1It seems that the Backup feature does not work in TWRP 2.8.1.1. When starting a backup, the screen turns off (feels like a little crash); when turned on again, TWRP is still on the same page but no backup was created and no process is running. Using an older version (e.g. twrp-2.6.3.0-7_tf101g.zip) works. So as a workaraound, you can flash the old TWRP, do the backup and finally flash 2.8.1.1 again.
CreditsThanks to @timduru for the great KatKiss ROM. Thanks to the community for all the infos and details in >1.500 posts allowing a 10-year old device to do a good job in 2021.
All I did was reading, executing and documenting the steps described in the
Tutorial of @javidben (05/2020)
Tutorial of @alexchandra (12/2018)
Tutorial of @EpicCentr (11/2018)
Click to expand...
Click to collapse
Does this still work? I will try it. Thank you if you can reply.
roguedes said:
Does this still work?
Click to expand...
Click to collapse
At least it did in 03/2021 - I'd like to encourage you to try it and share your experiences here.
Could you please tell me if there is any Tegra 2 compatible video conference app left?
Hi Christian, thanks a lot for this tutorial.
I've done it two times, with Always the same problem : my paid apps are not recognized as paid...
Could you please help me on that point ? Thanks for answer.
Edit : when trying to manage my account on Google play store, this app crash.
zgildasz said:
Hi Christian, thanks a lot for this tutorial.
I've done it two times, with Always the same problem : my paid apps are not recognized as paid...
Could you please help me on that point ? Thanks for answer.
Edit : when trying to manage my account on Google play store, this app crash.
Click to expand...
Click to collapse
Sorry, I can't help with that problem, maybe someone else has an idea.
Ok. Anyway thanks again for what you did. Wonder if I can buy again a cheap app just to check if this is possible and stable.
I would like to know also. ASUS should at least consider android Go as an option, despite the terminal has been released on the market 10 years ago.