Related
UPDATE: it works. see my link below. If anyone knows how to root I'd appreciate if you reply.
Hi
I own a Linx 7 windows tablet. Android x86 builds have not been great due to lack of sound and other driver issues.
I want to flash the bios - the dual boot one - from the cube iwork7 tablet.
In a youtube video by "Mr Borshchuk" - i cant post links, the cube is shown here running the LINX bios, the same version as my tablet. Can I do the reverse and flash the cube dual boot bios on my Linx?
Do you think this would work?
They seem to have the same spec etc and I'm guessing the same board- the cube just has a silver back. All ports are in the same place.
UPDATE: After looking more on 4pda, the iwork seems to come in 1/16GB variants and 2/32GB variants. My linx has 1GB of ram but 32gb of storage. Would this be an issue? My search also confirmed they are hardware clones.
So, that's the BIOS flash method. My other thought is is there a way to boot the android rom from the cube tablet from the stock linx bios? I have tried using the androidx86 bootloader combined with parts of the cube image and parts of androidx86 but, as expected, it didn't work.
So: I'm currently downloading the dual-boot bios from 4pda. Should I flash to my Linx?
Thanks. I've always loved XDA.
androidonlinx said:
Hi
I own a Linx 7 windows tablet. Android x86 builds have not been great due to lack of sound and other driver issues.
I want to flash the bios - the dual boot one - from the cube iwork7 tablet.
In a youtube video by "Mr Borshchuk" - i cant post links, the cube is shown here running the LINX bios, the same version as my tablet. Can I do the reverse and flash the cube dual boot bios on my Linx?
Do you think this would work?
They seem to have the same spec etc and I'm guessing the same board- the cube just has a silver back. All ports are in the same place.
UPDATE: After looking more on 4pda, the iwork seems to come in 1/16GB variants and 2/32GB variants. My linx has 1GB of ram but 32gb of storage. Would this be an issue? My search also confirmed they are hardware clones.
So, that's the BIOS flash method. My other thought is is there a way to boot the android rom from the cube tablet from the stock linx bios? I have tried using the androidx86 bootloader combined with parts of the cube image and parts of androidx86 but, as expected, it didn't work.
So: I'm currently downloading the dual-boot bios from 4pda. Should I flash to my Linx?
Thanks. I've always loved XDA.
Click to expand...
Click to collapse
I just thought what's the worst that could happen and flashed the bios. it worked. installing android and windows now.
EDIT: Android works. If anyone wants to know how I did this, please reply
EDIT: Windows works. I have achieved a dual boot setup .
androidonlinx said:
I just thought what's the worst that could happen and flashed the bios. it worked. installing android and windows now.
EDIT: Android works. If anyone wants to know how I did this, please reply
Click to expand...
Click to collapse
Windows works. .linxtablet.co.uk/viewtopic.php?f=49&t=1462&p=8748#p8748 is a guide. I am that user.
Can you just flash the android with this? I've no need for windows but if you could please share some info on the procedure.
Thanks
redeyes_ni said:
Can you just flash the android with this? I've no need for windows but if you could please share some info on the procedure.
Thanks
Click to expand...
Click to collapse
Check my 'link' to LinxTablet forums. You have to flash both but you can just ignore Windows and have a 16GB android partition.
androidonlinx said:
Check my 'link' to LinxTablet forums. You have to flash both but you can just ignore Windows and have a 16GB android partition.
Click to expand...
Click to collapse
Done all that which was handy enough so thanks but the android partition is only showing up as:
Internal Storage
Total Space: 4.36GB
I've loaded some apps which leaves me 2 GB free.
The only other partition is the external SD. Is there something I need to do to get the rest of the 16GB? Seems to me that it hasn't mounted or partitioned the internal memory correctly. The tablet is 32GB and I'm not concerned at just using the 16GB for android but with 2 GB left it's going to be a bit tight for apps.
Thanks again, any help would be appreciated.
I'm not sure. I'll check mine tonight but I remember having more storage than that. Are you sure your tablet is a 32gb version
Try using Minitool or Easus on the Windows side to resize the android partition if you can, or even just view the layout.
KitKat lacks support for apps to extsd. Root would mean we can fix this. The device does not support USB as port is otg and charge only so root has to be done with APK on tablet or on offline android fs from Windows. Anyone know how to root?
EDIT: checked. I have 3.43 GB free. Sorry, should have checked earlier. Android system takes up 2GB not shown, storage is only 28GB after bootloader, BIOS partition huge due to touch support in menus plus unnecessary drivers, plus I imagine the EFI partition was wrongly sized. This is fine for me, but will look into when I am working on Android again.
Currently not working on Android any more (fruity-based desktop OS port instead) but will come back to it. Hoping to also create an Androidx86 build to avoid BIOS flashing, but the BIOS flash does mean you have 64bit EFI on the Android side so can boot Win7, Darwin (you know what I mean ) and Ubuntu without modification.
Still looking to root. Anyone?
androidonlinx said:
I'm not sure. I'll check mine tonight but I remember having more storage than that. Are you sure your tablet is a 32gb version
Try using Minitool or Easus on the Windows side to resize the android partition if you can, or even just view the layout.
KitKat lacks support for apps to extsd. Root would mean we can fix this. The device does not support USB as port is otg and charge only so root has to be done with APK on tablet or on offline android fs from Windows. Anyone know how to root?
EDIT: checked. I have 3.43 GB free. Sorry, should have checked earlier. Android system takes up 2GB not shown, storage is only 28GB after bootloader, BIOS partition huge due to touch support in menus plus unnecessary drivers, plus I imagine the EFI partition was wrongly sized. This is fine for me, but will look into when I am working on Android again.
Currently not working on Android any more (fruity-based desktop OS port instead) but will come back to it. Hoping to also create an Androidx86 build to avoid BIOS flashing, but the BIOS flash does mean you have 64bit EFI on the Android side so can boot Win7, Darwin (you know what I mean ) and Ubuntu without modification.
Still looking to root. Anyone?
Click to expand...
Click to collapse
Thanks man. I'll try to resize the partition if/when I need it. Great work, well appreciated.
androidonlinx said:
Currently not working on Android any more (fruity-based desktop OS port instead) but will come back to it. Hoping to also create an Androidx86 build to avoid BIOS flashing, but the BIOS flash does mean you have 64bit EFI on the Android side so can boot Win7, Darwin (you know what I mean ) and Ubuntu without modification.
Still looking to root. Anyone?
Click to expand...
Click to collapse
Any bugs to note with the *toshing?
Rooting wise I can see two options. 1. mount the android system in windows with ext2 viewer or something and root it manually using a SuperSU.zip or better yet with linux (to avoid permissions issues). 2. Is there any other stage in the android boot process that you can halt it at? Dnx mode or droidboot (I'm assuming similar setup to chuwi vi10), where perhaps the usb will work in slave mode and it is identified as a fastboot device, allowing you to flash a custom recovery/root.
HypoTurtle said:
Any bugs to note with the *toshing?
Rooting wise I can see two options. 1. mount the android system in windows with ext2 viewer or something and root it manually using a SuperSU.zip or better yet with linux (to avoid permissions issues). 2. Is there any other stage in the android boot process that you can halt it at? Dnx mode or droidboot (I'm assuming similar setup to chuwi vi10), where perhaps the usb will work in slave mode and it is identified as a fastboot device, allowing you to flash a custom recovery/root.
Click to expand...
Click to collapse
Good idea. The flash is done using droidboot but I cannot get back into recovery again
androidonlinx said:
Good idea. The flash is done using droidboot but I cannot get back into recovery again
Click to expand...
Click to collapse
If its anything like the vi10 then Dnx mode is volume up and power from device off. Volume down and power is Windows/Android switcher. Volume down once the android logo appears will boot into droidboot.
Then there is the question of if you have a working custom recovery to flash, I think any of the baytrail recoveries from Dell/Chuwi etc. devices would work - will a kernel change if needed, and if the buttons work to enter recovery.
HypoTurtle said:
If its anything like the vi10 then Dnx mode is volume up and power from device off. Volume down and power is Windows/Android switcher. Volume down once the android logo appears will boot into droidboot.
Then there is the question of if you have a working custom recovery to flash, I think any of the baytrail recoveries from Dell/Chuwi etc. devices would work - will a kernel change if needed, and if the buttons work to enter recovery.
Click to expand...
Click to collapse
Will try this when I next have some spare time and my Linx to hand.
Knowing the reputation if Cube it wouldn't suprise me if the stock recovery allowed custom zips but otherwise I will try and flash another recovery from a similar tablet.
I'll take another look on 4pda to see if they have achieved root there too
Thanks again
I have root if anyone is interested email me on [email protected]
HypoTurtle said:
If its anything like the vi10 then Dnx mode is volume up and power from device off. Volume down and power is Windows/Android switcher. Volume down once the android logo appears will boot into droidboot.
Then there is the question of if you have a working custom recovery to flash, I think any of the baytrail recoveries from Dell/Chuwi etc. devices would work - will a kernel change if needed, and if the buttons work to enter recovery.
Click to expand...
Click to collapse
I got root working on my linx7 with the icube dual boot email me and I will tell you how
Hi mate, I found you late but really wants to know how to install Android in Linx 7, I don't wan windows at all, please reply
Thanks
U
onlinejobwork said:
Hi mate, I found you late but really wants to know how to install Android in Linx 7, I don't wan windows at all, please reply
Thanks
U
Click to expand...
Click to collapse
Go to linxtablet.co.uk I put my work on there it does mean flashing the bios so backup your product key also the Android partition is only 4gig so you can dual boot and have both I did find a way of making it 8gig but it was messy and buggy
[email protected] said:
Go to linxtablet.co.uk I put my work on there it does mean flashing the bios so backup your product key also the Android partition is only 4gig so you can dual boot and have both I did find a way of making it 8gig but it was messy and buggy
Click to expand...
Click to collapse
any direct link please ?
onlinejobwork said:
any direct link please ?
Click to expand...
Click to collapse
http://linxtablet.co.uk/viewtopic.php?f=4&t=2096
OVERVIEW
some people may have already seen some of the stuff i make like apps, tools, roms, mods and exploitation.
yesterday i got my first ever MTK device, and in all honesty i think the range of tools are crap other then MTK droid tools but that unfortunately isnt open source
THIS IS A COMMUNITY PROJECT AND THAT MEANS FREE AND OPENSOURCE AND OPENMINDED TO IDEAS
DOWNLOADS, DOCUMENTATION AND SOURCE
DOWNLOAD(VERY EARLY STAGES)
SOURCE CODE
NOTES
hopefully the community jumps in and gives me a hand and suggests features
XDA:DevDB Information
MTK open source AIO tool, Tool/Utility for all devices (see above for details)
Contributors
Ricky Divjakovski
Source Code: https://github.com/Ricky310711/OpenSource-MTK-Tool
Version Information
Status: Testing
Created 2016-01-14
Last Updated 2016-01-21
those are Teclast T98 MT8752
first stock
second modified for resizing purpose (system userdata)
hocuspocus69 said:
those are Teclast T98 MT8752
first stock
second modified for resizing purpose (system userdata)
Click to expand...
Click to collapse
i have made the scatter file parser made, ill be making a new repo and pushing to git later tonight
Great idea since MTK Droid Tools doesn't have support. :good:
My MT6572 scatter file with custpack partition (Alcatel Pop C2).
MT6575 scatter file with custpack partition (Alcatel S'Pop).
MT6571 scatter file (Blu Dash Jr K)
MT6577 scatter file with custpack partition (Alcatel Idol 6030X)
Mt6572 ( other china phone)
Here is the scatter for the Wiko Fever: http://forum.xda-developers.com/showpost.php?p=63755203&postcount=4
scatter file for Coolpad Note 3
scatter file for Coolpad Note 3
keemi said:
MT6577 scatter file with custpack partition (Alcatel Idol 6030X)
Mt6572 ( other china phone)
Click to expand...
Click to collapse
kirito9 said:
Great idea since MTK Droid Tools doesn't have support. :good:
My MT6572 scatter file with custpack partition (Alcatel Pop C2).
MT6575 scatter file with custpack partition (Alcatel S'Pop).
MT6571 scatter file (Blu Dash Jr K)
Click to expand...
Click to collapse
well normal scatter conversion is done, but may i ask what is an emmc scatter?
and couldnt we refer to a normal scatter file rather then the eMMC scatter, it doesnt seem to contain much info other then the partition label and size?
Ricky Divjakovski said:
well normal scatter conversion is done, but may i ask what is an emmc scatter?
and couldnt we refer to a normal scatter file rather then the eMMC scatter, it doesnt seem to contain much info other then the partition label and size?
Click to expand...
Click to collapse
It's basically the same as a normal scatter but some smart phones produce that scatter type(emmc) instead of the normal scatter. Same goes for some MTK Droid Tool versions like it happened with me. I got both normal scatter and an emmc scatter for the same phone.
I don't know why that is though. By both scatter files work with SP Flash Tool.
kirito9 said:
It's basically the same as a normal scatter but some smart phones produce that scatter type(emmc) instead of the normal scatter. Same goes for some MTK Droid Tool versions like it happened with me. I got both normal scatter and an emmc scatter for the same phone.
I don't know why that is though. By both scatter files work with SP Flash Tool.
Click to expand...
Click to collapse
ok, well ive made the scatter conversion, added the project donate feature and the abillity to see the tool and utillity versions, the source is in the main post
mt6572 jb scatter
TurkishBoy1 said:
mt6572 jb scatter
Click to expand...
Click to collapse
scatter files arent needed anymore, thanks anyway ill keep it for refferrence
Ricky Divjakovski said:
ok, well ive made the scatter conversion, added the project donate feature and the abillity to see the tool and utillity versions, the source is in the main post
Click to expand...
Click to collapse
Great I will check it out.
kirito9 said:
Great I will check it out.
Click to expand...
Click to collapse
any features you would like to suggest use the suggest features tab
Ricky Divjakovski said:
any features you would like to suggest use the suggest features tab
Click to expand...
Click to collapse
I recently go into mtk myself and have used your kitchen, Thank you! I don't have much experience in making roms but I have hard bricked my mt6572 K8 watch and my Cubot X-15 by getting carried away with with flashing but while doing so I've managed to bring them both back to life and have aquired 10 gigs of all kinds of different MTK tools. I'm mpre then willing to share my collection, now why would any one need 10 gigs of tools? well I learned the hard way that SP flash tools can be a pain in the ass when trying to bring your phone back from the dead hitting you with mad BROM errors so I found out that if you need a no bull**** save me flash tool, go with Infinix Flash. Any ways I'm more then down to be a part of this and will try to comtribute whatever I can
m0nt3s said:
I recently go into mtk myself and have used your kitchen, Thank you! I don't have much experience in making roms but I have hard bricked my mt6572 K8 watch and my Cubot X-15 by getting carried away with with flashing but while doing so I've managed to bring them both back to life and have aquired 10 gigs of all kinds of different MTK tools. I'm mpre then willing to share my collection, now why would any one need 10 gigs of tools? well I learned the hard way that SP flash tools can be a pain in the ass when trying to bring your phone back from the dead hitting you with mad BROM errors so I found out that if you need a no bull**** save me flash tool, go with Infinix Flash. Any ways I'm more then down to be a part of this and will try to comtribute whatever I can
Click to expand...
Click to collapse
SP flash tool is a great tool, abit complicated fpr norrmal users to use but gets the job done, if it were upto me personally id make a menu from the scatter file presented and have a list of partitions to flash based on the scatter
MediaTek 6571 which wont address hard drive properly
Ricky Divjakovski said:
SP flash tool is a great tool, abit complicated fpr norrmal users to use but gets the job done, if it were upto me personally id make a menu from the scatter file presented and have a list of partitions to flash based on the scatter
Click to expand...
Click to collapse
Not sure where to start, trying to get my MediaTek MT6571 working properly but before I try to flash, is there any utility which can read the hard drive, either in Windows, Mac or Linux please? I and numerous others report that we have severe partitioning problems and would like either to see if there is unallocated space on my hard drive OR if there is some endemic problem with my Hexing71_et_lca ROM which is stopping it addressing its drive properly.
I feel I am caught in a Windows 98 time warp with some sort of LBA problem where I can't address anything more than a tiny percentage of the hard drive!
The 6571 seems to have a 16 gig hard drive but if it does, most of it is unallocated and only 899 meg shows as usable. When I try to install anything much larger than a few meg on it, I get OUT OF SPACE error messages.
So I figured that I need to install an SD card in the device and installed a 32 gig one, - obviously for all the apps. Aparted managed to get the card working but now after I did manage to install AIda on the phone, I am getting the same 32 gig installed, 899 meg available (none actually usable and) OUT OF SPACE error messages in Disk Storage & when I try to use the SD card as well!
Is there any GUI out there which can show what is actually going on with this device please? It wont show up in OSX, even in Disk Utility, but I do seem to be able to read (only) the hard drive's empty photos storage partition in XP and Linux. The only thing I know about the device from recovery mode is that it might be a sw version alps.jb7.mp.v1.14
custom build vern 1443066946, whatever that means!
licensedtoquill said:
Not sure where to start, trying to get my MediaTek MT6571 working properly but before I try to flash, is there any utility which can read the hard drive, either in Windows, Mac or Linux please? I and numerous others report that we have severe partitioning problems and would like either to see if there is unallocated space on my hard drive OR if there is some endemic problem with my Hexing71_et_lca ROM which is stopping it addressing its drive properly.
I feel I am caught in a Windows 98 time warp with some sort of LBA problem where I can't address anything more than a tiny percentage of the hard drive!
The 6571 seems to have a 16 gig hard drive but if it does, most of it is unallocated and only 899 meg shows as usable. When I try to install anything much larger than a few meg on it, I get OUT OF SPACE error messages.
So I figured that I need to install an SD card in the device and installed a 32 gig one, - obviously for all the apps. Aparted managed to get the card working but now after I did manage to install AIda on the phone, I am getting the same 32 gig installed, 899 meg available (none actually usable and) OUT OF SPACE error messages in Disk Storage & when I try to use the SD card as well!
Is there any GUI out there which can show what is actually going on with this device please? It wont show up in OSX, even in Disk Utility, but I do seem to be able to read (only) the hard drive's empty photos storage partition in XP and Linux. The only thing I know about the device from recovery mode is that it might be a sw version alps.jb7.mp.v1.14
custom build vern 1443066946, whatever that means!
Click to expand...
Click to collapse
The best way to really see how much space each partition has is using MTK Droid Tool and choose the option block information.There you will see your partition sizes and names.
licensedtoquill said:
Not sure where to start, trying to get my MediaTek MT6571 working properly but before I try to flash, is there any utility which can read the hard drive, either in Windows, Mac or Linux please? I and numerous others report that we have severe partitioning problems and would like either to see if there is unallocated space on my hard drive OR if there is some endemic problem with my Hexing71_et_lca ROM which is stopping it addressing its drive properly.
I feel I am caught in a Windows 98 time warp with some sort of LBA problem where I can't address anything more than a tiny percentage of the hard drive!
The 6571 seems to have a 16 gig hard drive but if it does, most of it is unallocated and only 899 meg shows as usable. When I try to install anything much larger than a few meg on it, I get OUT OF SPACE error messages.
So I figured that I need to install an SD card in the device and installed a 32 gig one, - obviously for all the apps. Aparted managed to get the card working but now after I did manage to install AIda on the phone, I am getting the same 32 gig installed, 899 meg available (none actually usable and) OUT OF SPACE error messages in Disk Storage & when I try to use the SD card as well!
Is there any GUI out there which can show what is actually going on with this device please? It wont show up in OSX, even in Disk Utility, but I do seem to be able to read (only) the hard drive's empty photos storage partition in XP and Linux. The only thing I know about the device from recovery mode is that it might be a sw version alps.jb7.mp.v1.14
custom build vern 1443066946, whatever that means!
Click to expand...
Click to collapse
what do you mean read the hard drive?
if your reffering to the phones storage i think you mean eMMC?
and that is devised into seperate partitions and filesystem formats, you need software to read it not to mention split it, a good start would be SP flashtool and MTK droid tools, also i suggest you format the sdcard(take it out of the device) as FAT32 with minitool partition wizard, also might be a good idea to check for damaged blocks and if you have the time zero all sectors out
EDIT: also if your modifying andd flashing .img files make sure you save it as the exact same size as the partition
Thnx
According to this post along with @LastStandingDroid & @HackerOO7, the Nougat Honor 8 kernel doesn't support loop mounts. Evidently the Marshmallow kernel does, as I'm using Magisk* with no issue.
On a stock unrooted Nougat FRD-L04, the command 'cat /proc/devices" returns (less relevant data snipped):
Code:
127|HWFRD:/ $ cat /proc/devices
Block devices:
1 ramdisk
259 blkext
[B] [U]7 loop[/U][/B]
8 sd
31 mtdblock
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
253 device-mapper
254 zram
It would appear that the FRD Nougat is still somewhat loop aware, in that there are references that still exist, but just evidently not the kernel driver. In light of the fact that there is no Nougat kernel source, and even if there was it would be a Huawei mess, it's unlikely we're ever going to be able to build in loop support from scratch on a stock-base ROM.
In light of that, has anyone attempted building a loadable kernel module for the N kernel (4.1.18 I believe) and installing it via 'insmod'? What are some angles we can try and take to get loop support, and thus Magisk support, back into N.
* (If you're unfamiliar with what Magisk is and does, it allows you to, among other things, get root and modify the system without modifying the system, thus allowing you to continue to use applications (Pokemon Go, Android Pay, banking applications) that otherwise would not allow you to use them with root or a modified system))
Telperion said:
According to this post along with @LastStandingDroid & @HackerOO7, the Nougat Honor 8 kernel doesn't support loop mounts. Evidently the Marshmallow kernel does, as I'm using Magisk* with no issue.
On a stock unrooted Nougat FRD-L04, the command 'cat /proc/devices" returns (less relevant data snipped):
Code:
127|HWFRD:/ $ cat /proc/devices
Block devices:
1 ramdisk
259 blkext
[B] [U]7 loop[/U][/B]
8 sd
31 mtdblock
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
253 device-mapper
254 zram
It would appear that the FRD Nougat is still somewhat loop aware, in that there are references that still exist, but just evidently not the kernel driver. In light of the fact that there is no Nougat kernel source, and even if there was it would be a Huawei mess, it's unlikely we're ever going to be able to build in loop support from scratch on a stock-base ROM.
In light of that, has anyone attempted building a loadable kernel module for the N kernel (4.1.18 I believe) and installing it via 'insmod'? What are some angles we can try and take to get loop support, and thus Magisk support, back into N.
* (If you're unfamiliar with what Magisk is and does, it allows you to, among other things, get root and modify the system without modifying the system, thus allowing you to continue to use applications (Pokemon Go, Android Pay, banking applications) that otherwise would not allow you to use them with root or a modified system))
Click to expand...
Click to collapse
You're right that stock nougat (b360 anyway) doesn't have kernel support for "mount -o loop" or loop device for some reason. Until at least now, I've not seen any Huawei stock kernel source for that kernel. If we had it, then it'd not be a big issue. I noticed this development today: https://github.com/OpenKirin/android_kernel_huawei_frd/tree/7.x
From @surdu_petru , who today uploaded a real version of TWRP for Nougat Honor 8, more specifically from his github where there appears to be a 7.x.x Honor 8 kernel at the link above. I'm guessing that if you pull that source, and the "android-recommended.cfg" .config file, you'll see that CONFIG_BLK_DEV_LOOP=y. So if that's buildable source, then it looks ready to go for your uses.
It's too bad that /proc/config.gz (current honor 8 kernel config) isn't kept in /proc like nearly all other androids, but it's not. Without that, it's hard to rebuild the exact configuration and only add the loop device. (or build the module).
Anyway: I was kind of excited to notice what surdu_petru had done and you can possibly figure out how to do your loop module addition if he used that kernel code at the first pointer above. -- cheers.
That's an encouraging development, I'll check it out. As much as I prefer the Nougat interface, especially the recents, notifications, and quick settings, I prefer Magisk to those things so I'll hang out on MM for now.
Looks like still no kernel source for Nougat so not much we can do on that angle yet.
One possibility may be to fork Magisk's source and modify it to use a ramdisk instead of a loop device. It's pretty far out of my expertise though.
@wraithewok
I see that Source code for Mate 9 is released on this page http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
I know that it is based on Kirin 960. Can't we use it as a base for our Honor 8?
Telperion said:
Looks like still no kernel source for Nougat so not much we can do on that angle yet.
One possibility may be to fork Magisk's source and modify it to use a ramdisk instead of a loop device. It's pretty far out of my expertise though.
@wraithewok
Click to expand...
Click to collapse
Almost everytime I deal with ramdisks, they're implemented via loop devices. I'll have to read around and see if people do ramdisks another way.
---------- Post added at 07:00 AM ---------- Previous post was at 06:32 AM ----------
morpheus302 said:
I see that Source code for Mate 9 is released on this page http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
I know that it is based on Kirin 960. Can't we use it as a base for our Honor 8?
Click to expand...
Click to collapse
From what I've read about 960 (cortex-a73) vx. 950 (a720), there are architectural differences to prevent throttling, etc. It's not just a case of binning (where the "faster" chips are binned as 960's, rather than 950's). I'd like to see a "hammer Honor" campaign nagging them to release their Honor 8 Nougat source like for mate 9. I've put a post on their forum, but they have a record of nearly zero response to anyone that isn't just praising them.
*my post on Honor forum* https://club-us.hihonor.com/honor8.32/where-can-we-get-kernel-source-for-honor-8-nougat.1835
From my googling, it appears to be possible, but you're right that it's not common. Most of what I've found is from old Linux tutorials, not Android specific. It should be doable though.
hachamacha said:
Almost everytime I deal with ramdisks, they're implemented via loop devices. I'll have to read around and see if people do ramdisks another way.
Click to expand...
Click to collapse
hachamacha said:
Almost everytime I deal with ramdisks, they're implemented via loop devices. I'll have to read around and see if people do ramdisks another way.
Click to expand...
Click to collapse
Here's one article I ran across:
http://surfer.nmr.mgh.harvard.edu/partition/ramdisk.html said:
Create a ramdisk device if one does not already exist in /dev:
/home/tony# mknod -m 660 /dev/ram b 1 1
/home/tony# chown root.disk /dev/ram
Zero out the space you need on the ramdisk device:
/home/tony# dd if=/dev/zero of=/dev/ram bs=1k count=4k
4096+0 records in
4096+0 records out
Make a file system on the ram disk, specifying the size:
/home/tony# /sbin/mkfs -t ext2 -m 0 /dev/ram 4096
mke2fs 1.18, 11-Nov-1999 for EXT2 FS 0.5b, 95/08/09
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
1024 inodes, 4096 blocks
204 blocks (4.98%) reserved for the super user
First data block=1
1 block group
8192 blocks per group, 8192 fragments per group
1024 inodes per group
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
Mount the ram disk as you would a regular device:
/home/tony# mount -t ext2 /dev/ram /mnt/disk
Click to expand...
Click to collapse
Telperion said:
Here's one article I ran across:
Click to expand...
Click to collapse
I'm not 100% but this looks like a way to create a ramdisk once you're already logged on or sudo'd to root user. I don't think you'll have access to the full realm of busybox type commands, /sbin,/usr/sbin cmds, without being root. Is that a showstopper since the idea here is to use the ramdisk to get root?
Another thing I don't quite get is what keeps the zeroed out ram from being overwritten by any actions on the phone since no one is bothering to do an malloc(*).?
However: If you could achieve some temporary root, then it looks fine (but catch 22 , blah blah)::
Oh! I guess I wasn't quite thinking of this right.. If you have the latest TWRP installed, and you can boot into it, and use adb shell to reach it, then it must have /xbin/su built in so that it can do anything at all. I guess you can execute everything from TWRP. Then the only question is can you mount the ext2 ramdisk without problem and actually get magisk (sp?) to use it.
Anyway, it does look worth a shot. Thanks for the link.
hachamacha said:
Anyway, it does look worth a shot. Thanks for the link.
Click to expand...
Click to collapse
As far as I understand the way Magisk works, it's essentially loop mounting a symlinked fileystem over top of /system/ and the actual files are located in an .IMG elsewhere. So in light of that, shouldn't it be possible to just change the method of mounting while keeping the functionality the same? Instead of using a loop block device, we'd be using a ram block device.
This is beyond my expertise, but I was able to mount a ramdisk as a block device on Ubuntu so conceptually I think it should be possible.
Have there been any updates?
Latest beta of Magisk works great.
morpheus302 said:
Latest beta of Magisk works great.
Click to expand...
Click to collapse
Are you on stock ROM?!
yes, b389
jonny190 said:
Have there been any updates?
Click to expand...
Click to collapse
It's been working since B381 I believe it was. So yeah. Before that loop was broken or just disabled
Sent from my FRD-L09 using Tapatalk
morpheus302 said:
yes, b389
Click to expand...
Click to collapse
Thanks
LastStandingDroid said:
It's been working since B381 I believe it was. So yeah. Before that loop was broken or just disabled
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
HI there, I was wondering if xposed works on B381 and onwards? Thanks!
Neeosx said:
HI there, I was wondering if xposed works on B381 and onwards? Thanks!
Click to expand...
Click to collapse
Yes it works I've tried it on b381 so I can confirm it works
Sent from my NATASHA using Tapatalk
So magisk is working and you can use magisk hide to use android pay? If its fully working then i'll consider unlocking bootloader again.
colliflower1107 said:
So magisk is working and you can use magisk hide to use android pay? If its fully working then i'll consider unlocking bootloader again.
Click to expand...
Click to collapse
Yes it is working use the universal safety net module in magisk.
Hey guys, a new version of Phoenix OS (v2.0.7) is out and I have created rooted images for you guys to use.
Instructions:
Download the correct system rooted.7z file provided in the Download section and extract it
Install Phoenix OS and restart your computer.
Boot into Phoenix OS and finish the system initialization wizard. Restart the computer and boot into your main OS.
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.
Install the latest version of SuperSU. Sign in to Play Store using 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.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.151.32bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNVGpBZmxQS0dhRjg
Phoenix OS x64 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.150.64bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNclN5SGdFUGlTRGs
Download Phoenix OS v2.0.7 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6186
History:
Uploaded v2.0.7 system images
Oooh... now I can test this to see if it fixes my G+ compatibility issue
The Wrath of Kahn said:
Oooh... now I can test this to see if it fixes my G+ compatibility issue
Click to expand...
Click to collapse
Sure! Let us know if it works out well for you
meanhacker said:
Sure! Let us know if it works out well for you
Click to expand...
Click to collapse
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
The Wrath of Kahn said:
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
Click to expand...
Click to collapse
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
meanhacker said:
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
Click to expand...
Click to collapse
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
The Wrath of Kahn said:
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
Click to expand...
Click to collapse
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
If anyone get's "grub minimal bash like line editing issue" when trying to boot
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
meanhacker said:
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
Click to expand...
Click to collapse
I tried editing the build.prop before with no luck, but I'm not experienced in doing it so I may have missed the fields that I needed.
irex102 said:
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
Click to expand...
Click to collapse
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
irex102 said:
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
Click to expand...
Click to collapse
Hey I found some readied kernels that fixes all the issues on baytrail tablets for android x86 7.1: https://drive.google.com/drive/folders/0B1HDhURlGNctY045UWFhalo5MW8 All that's left is to patch a rom for these devices. More info found here: https://github.com/burzumishi/linux-baytrail-flexx10/issues/12#issuecomment-309275211
#Quest
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Nicojoy said:
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Click to expand...
Click to collapse
What version of Phoenix OS do you have installed? If you have v2.0.7, you're in the right thread, so go ahead and download either a 32 or 64-bit version of the rooted image and replace it with your current system.img.
This will work on a Nexus 9 or it only works in pc's?
when i update su binary like you say it says to me installation failed
edit: ifound soulition its to update super su to the latest version with play store or aptoide or arc market or app vn and the install the binary data its soooo easyyyyyyy
Waiting for rooted system.img for Phoenix OS 2.1.0
SU Binary busy?
So I followed the instructions (although the step 6 is kind of confusing, English is not my native language so...) booted with the rooted sys image, installed superSU from the Play Store and when I open it it says "SU binary busy" and send me to a FAQ where it says that
"The SU files are already occupied by other software, such as Kingroot."
So I need to install the binary somehow? or something went wrong?
Oh BTW, used Root checker and it says it's not propely installed
Thanks for the image, buddy
MrSlenderman said:
"The SU files are already occupied by other software, such as Kingroot."
Click to expand...
Click to collapse
I also ran into this problem using the newest version from the play store, I could avoid this though by installing version 2.79 through an apk.
But now it won't let me update the binary, since everytime I select "Normal" the installation fails after a minute or so.
Any ideas?
Guys, when to expect a rooted image for V 2.1.0 x86
thank you, but i bit confused about when i update the os,
so when i update the os, the rooted image will gone ? and i need to wait for another rooted image ?
Phoenix os for x86 v2.1.0released. In this version we enhance the hardware compatibility, including: sound card, network adapter, etc. And we add smart casting for Strike of Kings.
Update Details
- Keyboard mapping updates to version 2.5 with smart casting for Strike of Kings.
- The bug that window size won't be saved after restart has been fixed.
- Enhance the hardware compatibility, including: sound card, network adapter, etc.
- "Start Phoenix system" shortcut supports legacy boot now.
- Optimize the Phoenix OS downloader.
Link: http://bbs.phoenixstudio.org/en/showthread.php?tid=6511
Download:
EXE
http://files.phoenixos.com/os/PhoenixOSInstaller_v2.1.0.179.32bit.exe
http://files.phoenixos.com/os/PhoenixOSInstaller_v2.1.0.175.64bit.exe
https://mega.nz/#!MH4ijZRK!NiRZaFlM54tsNrufmtEhel6oKnWbd_QjNOYauCrRtcM
https://mega.nz/#!JOxVyZrL!c2gL9s9TrTYEMUvJQoCbpXQ_x49GcSsaPY74w6DQa2w
ISO
http://files.phoenixos.com/os/PhoenixOSInstaller_v2.1.0.179.32bit.iso
http://files.phoenixos.com/os/PhoenixOSInstaller_v2.1.0.175.64bit.iso
https://mega.nz/#!ADQjgRhZ!tC19m6UKuiG1waOHBuypepqkXz3qnMNnF-DF2EMPNKg
https://mega.nz/#!9SIEnboR!GTn3nnW1KlhtZ7XkI98T7Tsaljin8OmZGBqMhhAcm-4
What is the minimum hardware to run Phoenix OS 2.1?
I have an EEE PC 1201ha, does it work?
Specification
Intel® Atom ™ CPU Z520 - 1.33 GHz, 1 core, Hyper-Threading, SSE2, SSE3, SSSE3
Intel® Poulsbo US15W Chipset
RAM DDR2 SO-DIMM 2GB
SSD GOLDENFIR, model T650-60GB
@arielbw install to USB stick and test.
Currently there is no compatibility database, nor no one is working on one.
EEE PC are usually the most well supported Android-x86 devices, so everything should work fine.
EDIT:
Your hardware is enough to make Phoenix OS run.
On 32-bit version, Google Play doesn't work properly. Trying to update Google Play Services, it says that it can't be installed (Error code: -501). Haven't tested the 64-bit version yet, but I can guess it will be the same
@meanhacker are you manually trying to update GMS or it's automatic pop-up?
If manual, why even update?
Vioner said:
@meanhacker are you manually trying to update GMS or it's automatic pop-up?
If manual, why even update?
Click to expand...
Click to collapse
I'm trying to play Bombsquad which requires Google Play Services to be up to date. When I open up Bombsquad, it tell me that Google Play Services needs to be updated. I click OK, and then it takes me to the Google Play Store. Then, I click Update. It's not manual, but it prevents me from doing certain things.
I'm having the same problem.
Just installed the x64 version and I cant even open chrome because it needs google play services updated.
Even tried downloading the apk, but it wont install...
Maheidem said:
I'm having the same problem.
Just installed the x64 version and I cant even open chrome because it needs google play services updated.
Even tried downloading the apk, but it wont install...
Click to expand...
Click to collapse
Yeah I had the same issue until I solved it. Have a look here
Problem on the screen - eee pc 1201ha
Vioner said:
@arielbw install to USB stick and test.
Currently there is no compatibility database, nor no one is working on one.
EEE PC are usually the most well supported Android-x86 devices, so everything should work fine.
EDIT:
Your hardware is enough to make Phoenix OS run.
Click to expand...
Click to collapse
Phoenix OS v2.1.1.190_x86 installed.
Now I have a problem on the screen, an image is duplicated and a bit distorted.
Can someone help me?
Image in the link below
imgur.com/a/DLety
I also installed android-x86-4.0-r1-eeepc.iso. It worked without presenting problems on the screen.
arielbw said:
Phoenix OS v2.1.1.190_x86 installed.
Now I have a problem on the screen, an image is duplicated and a bit distorted.
Can someone help me?
Image in the link below
imgur.com/a/DLety
I also installed android-x86-4.0-r1-eeepc.iso. It worked without presenting problems on the screen.
Click to expand...
Click to collapse
Your integrated graphics might be the issue. I looked up the specs of your laptop:
https://www.asus.com/Laptops/Eee_PC_1201HA_Seashell/specifications/
http://ark.intel.com/products/35444/Intel-SCH-US15W
I actually had something similar to this on my OSMC splash screen (Kodi build on the raspberry pi). I found a post about it here. Have a look and I think you will probably need to let Phoenix OS know your native screen resolution. I think that's why it's distorting like that.
Well, it worked! Thanks!
Meu processador intel® celerom M 430 1.73 ghz roda qual versao do phoenix os ?