.Net CF Versions? - Upgrading, Modifying and Unlocking

I have some questions on .Net CF.
Currently my O2 XDA Flame is having v1.0.
Many Apps using v2.0 and even v3.5 Beta cannot be used.
I have download them both v2.0 & v3.5 Beta, but not sure which to use,
1. Can I jump from v1.0 to v3.5 Beta and v2.0 Apps will still work with v3.5 Beta?
2. Each version normally comes with PPC & WM Version, which should I use?
3. For O2 XDA Flame, should I use the ARM version or which version?
4. I cannot find the cab of v1.0, I am looking for it in case I want to downgrade. I only found the Sevice Pack 3 for developer version. I know I can also do a uninstall or a hard reset or do a restore from backup to get back v1.0.

You can have multiple versions of the .NET CF installed if you want. When a program runs, it will attempt to load the version it was compiled against. If that version is not available, it will attempt to load the highest version that is available, and hopefully it will be compatible with the app.
For example, if you run an app that was designed for framework version 1.1, and you have 2.0 and 3.5 installed, 3.5 will get loaded.
As for locating and installing the different frameworks, I can't be much help, except to suggest that, if an app you have didn't install the version it wants, you might be able to download the correct version by looking at the microsoft mobile website.

bcbarnes said:
You can have multiple versions of the .NET CF installed if you want. When a program runs, it will attempt to load the version it was compiled against. If that version is not available, it will attempt to load the highest version that is available, and hopefully it will be compatible with the app.
For example, if you run an app that was designed for framework version 1.1, and you have 2.0 and 3.5 installed, 3.5 will get loaded.
As for locating and installing the different frameworks, I can't be much help, except to suggest that, if an app you have didn't install the version it wants, you might be able to download the correct version by looking at the microsoft mobile website.
Click to expand...
Click to collapse
Thank you for answer Q1 & Q4.
Do you have an answer for Q2 & Q3?

Took the courage to install NetCfV3.5Beta WM Version and manage to get downloaded Apps (SimpleOS) to work.

Without installing NetCfV2, direct from Flame's NetCfV1 to NetCfV3.5Beta, download Apps (TouchFlo3D, needed at least NetCfV2) works with NetCfV3.5Beta.

yeah .net is backward compatible
but with beta's it's not always the case
.net2 had issues with some .net1.1 stuff
in it's beta's

Related

YouTube plugin issues

I'm having issues with hte YouTube plugin. I haven't been able to watch anything yet. I believe it's because when you're watching videos, they're actually being downloaded to the temp folder. At least that's how it works in Windows. I keep getting "cannot play this video" error.
Is there a way to set the YouTube plugin to load the temp files into the SD card instead? Or is it missing a codec or something? Thanks
try this one, works for me
Is that supposed to replace the one I have installed which is the HTCYouTubeQVGA-Official 2mb or install on top of it?
Thanks.
markafreeman said:
try this one, works for me
Click to expand...
Click to collapse
chukalov said:
Is that supposed to replace the one I have installed which is the HTCYouTubeQVGA-Official 2mb or install on top of it?
Thanks.
Click to expand...
Click to collapse
I believe those are two separate applications. From what I've gathered, the "cannot play this video" error is based on what ROM you have, and I guess what exactly is cooked into the ROM. The only ROM I've been able to have the youtube application fully working is Shamiax's (sp?) ultimate WM6. The youtubeplay application, on the other hand, seems to work regardless of what ROM you have, but it's not as slick as the youtube application.
I'm using the OS 5.2.20755 (Build 20755.1.4.0 PV DVH) Black(Full) BS V25 rom. I also loaded the Manilla2D and everything looks and works great except YouTube.
in my new manilla rom i'm testing i have not been able to get working also.. i'll let you guys know if i figure it out in more testing tonight
5.2.20755 is the newest build. I believe the YouTube has been working with the older builds but not in the last few releases. BTW I love the new Manilla ROM too but it was a little too "loaded" with apps that I didn't needs so i installed the M2D cabs to get the same look. Maybe in your next release YouTube will be working too and i can put the Lite version

Can't get Copilot working with Villain 3.3

Sry - if its not the right section for my question !! Please move if it is so.
Have flashed the new Villain 3.3 ROM thanks - i like it
But one Question - is it possible to get copilot working with it ? Walking through installation without problems. But when I start Copilot it says something like:
The system couldn't load Copilot-Code
What I'm doing wrong - or is Copilot not compatibel with Android 2.1 ? Please help
use Ndrive
I think - I will test another ROM. Thanks for ur advice !
copilot is not compatible with android 2.0
pina_ said:
copilot is not compatible with android 2.0
Click to expand...
Click to collapse
That's not the point as we're talking about 2.1. But anyway, I think you're wrong: my version of CoPilot works flawlessly on my HeroDroid-Rom (which is built on the same Eris leak as Villain).
So, maybe it's a specific problem with Villain, but definitely not with Android 2.1
Thanks for your answere - I will try to get it work - however ... btw which Copilot Version do you use ?
I'm using iGo, which runs great on 3.3 and is a better navigation system in my opinion.
spunkey said:
Thanks for your answere - I will try to get it work - however ... btw which Copilot Version do you use ?
Click to expand...
Click to collapse
CoPilot 8 from the Market (Full EU). Bought it under the old 1.5-Rom version, made a backup with Titanium Backup and restored it under Android 2.1.
It says on their site that they have Nexus support, so it should work in 2.1. You may have to update to the latest version though.
spunkey said:
What I'm doing wrong - or is Copilot not compatibel with Android 2.1 ? Please help
Click to expand...
Click to collapse
I have no problems with Copilot under Villain 3.3. Had it reinstalled from the market after flashing.
iGO just works - I don't know why Copilot wan't do ...
spunkey said:
Sry - if its not the right section for my question !! Please move if it is so.
Have flashed the new Villain 3.3 ROM thanks - i like it
But one Question - is it possible to get copilot working with it ? Walking through installation without problems. But when I start Copilot it says something like:
The system couldn't load Copilot-Code
What I'm doing wrong - or is Copilot not compatibel with Android 2.1 ? Please help
Click to expand...
Click to collapse
Strange, I get the same error!
I think you need version 8.0.0.606
Maybe you should uninstall it and reinstall it from the market instead of using titanium backup, 2.1 is a lot different than 1.5 and it may be that titaniumbackup can not restore the settings from an 1.5 rom to a 2.1 rom properly.
IMHO you should not restore your settings from 1.5 roms to 2.1 ones as many things have changed and you can easily break your system and then you will have to flash it again in order to get it working. I've had that experience, I restored 1.5 settings to 2.1 and all I got were force closes of sense and this and that. Selectively the restore works but I dont recommend it..
pina_ said:
copilot is not compatible with android 2.0
Click to expand...
Click to collapse
Don't know where you got that from, but my Copilot works perfectly with Villain 3.3 (Android 2.1).
Regards,
Dave
xTuX said:
Maybe you should uninstall it and reinstall it from the market instead of using titanium backup, 2.1 is a lot different than 1.5 and it may be that titaniumbackup can not restore the settings from an 1.5 rom to a 2.1 rom properly.
IMHO you should not restore your settings from 1.5 roms to 2.1 ones as many things have changed and you can easily break your system and then you will have to flash it again in order to get it working. I've had that experience, I restored 1.5 settings to 2.1 and all I got were force closes of sense and this and that. Selectively the restore works but I dont recommend it..
Click to expand...
Click to collapse
I used Titanium Backup for all the self-installed software and I had not one single FC (and as mentioned earlier, it also worked flawlessly with CoPilot). But I never restored any system settings from 1.5, I think that it what leads to your crashes.
sorted mine, updated to 8.0.0.507 and its working again!!!
alti4 said:
I used Titanium Backup for all the self-installed software and I had not one single FC (and as mentioned earlier, it also worked flawlessly with CoPilot). But I never restored any system settings from 1.5, I think that it what leads to your crashes.
Click to expand...
Click to collapse
yip, I know, as I said, it works if you select certain things that dont have much to do with the system itself. my problem was also that the apps didnt appear in the market so they dont update as easy - for me its best to do a clean setup, it takes some time but it almost always works safer and better

[Q] Busybox version importance?

Maybe this has been answered in the past and in this case I apologise.
I have a few questions, because there are quite a lot of busybox (BB) versions available to install. What I am asking is, does it matter which version you choose in terms of system performance, compatibility and system stability or other factors?
For example: Currently I'm using Redux2 TEST ROM (I have a rooted S-OFF device) which by default uses 1.16.2 BB version. To my knowledge this version is quite old in contrast to the ROM itself, which is GB 2.3.5.
To my confusion also contribute conflicting information about this topic. Some say if everything works, leave it alone, other recommend the latest stable version. To my knowledge there are 2 apps intended solely to the BB installation. So, by advice of the app I moved to the latest stable BB version - 1.18.5, installed successfully, but then my system refused to reboot and I had to perform a NAND restore.
The other app listed the latest BB version as 1.19.1 but according to author of the previous mentioned app this version is unstable, but I do not have any problems with it.
To a degree, I learned to solve such problems by trial and error, but especially in this case I'm left confused and without reliable answers.
Thank you for your help.
For example: Currently I'm using Redux2 TEST ROM (I have a rooted S-OFF device) which by default uses 1.16.2 BB version. To my knowledge this version is quite old in contrast to the ROM itself, which is GB 2.3.5.
Click to expand...
Click to collapse
Well you compare busybox version to android version?? Seems odd considering they have nothing in common what so ever.
Busybox is simply a linux script/tool containing a bunch of mainstream commands allowing for simple commandline actions. Usually those are only accessed by the system and some root apps, so in general i'd recommend to keep the one bundled with your rom since that's the one it's meant to use. Some apps like titanium backup might require a newer one though.
So if it works, keep it if some app require a newer one, try it out but backup first
Helpful info
Thank you for your answer.
After all this comparison without sense turned out to be useful after all
Now I learned something new, and you gave me an excelent example.
But try to in my shoes for a minute. By profession I'm a physician and I have been trained to do my job with competence. If someone does not know something I try to pass on my knowledge. That is all I can do.
In contrast, about Android or Linux I know almost nothing (only so much, what I had to learn alone, to have a phone, which is functional and uses all of its capabilities).
So for the end I can only say thank you for your advice.

Polaroid All in One - Root, Un-Root, Play Store, Should work on other devices

Polaroid All in One is a C++ application that will easily and quickly Root, Un-Root, and Install / Remove Google Applications and Google Services Framework. This software is designed for the PTAB8000, and PMID800. However, should work for similar tablets running Ice Cream Sandwich and Jelly Bean (Google Apps only supported on Android 4.0.x). If you use this software with any other device please post your results in the this forum.
Requirements
Microsoft Windows (Tested on Windows 7 and Windows XP)
ADB Drivers Installed
Android Device Running 4.0 or 4.1 (Google Apps only supported on 4.0.x)
Recommended Method
Use version 1.6b to root your device, then use version 2.1b to install Google Framework.
UPDATE 8/11/14 -- Why doesn't this work with my device?
I just wanted to clear a few things up. I have had a few inquires about PAIO (Polaroid AIO) not installing Google Framework on their devices. The framework included in the latest releases is only compatible with Android 4.0.x. While PAIO v1.6b should be able to root 4.0, and 4.1 devices, the application will refuse to load the framework on a non-compatible version of android. If your tablet is not running a variant of Ice Cream Sandwich, it's simply not going to work. If we continue development we can support newer versions of Android. But, for now you would have to install the framework manually. If you would like to pursue a manual install I recommend you check out this page: http://wiki.rootzwiki.com/Google_Apps Make sure you know what you are doing, and install the version that is correct for your device. I'm waiting to get more feedback on the poll before I decide to continue this project.
Have a great week everyone,
Wayne
UPDATE 8/10/14 -- [Quick Survey] Should we continue development?
As I am sure some of you have noticed by now, this project has not been under active development for over a year now. We had an event that resulted in a loss of the source code for the project. As a result, the project was put on the back burner as it worked "OK"-ish. Between the 1.6b and 2.1b releases it did meet the requirements at the time, which was to root and install a full play store on the PTAB8000, and PMID800 devices. While these devices may not be as popular at this time (they had a fairly high failure rate). There are other Generic devices that people have used this program on, with mixed results. I did have a PTAB8000 with a cracked screen donated a while back. As long as we have people to test/debug, and support the project however they can. I am willing to start the project from scratch (again).
All I ask is for a few minutes of your time to take a quick survey to help me understand the interest we have in this project.
Click here to take the survey.
UPDATE 1/21/13 -- Polaroid AIO v2.1b [Beta Release]
After a nightmare's worth of coding Polaroid All in One v2.1b is finally here. This update aims to provide the best possible user experience. While utilizing the latest patches discovered by the team. I would like to give a special shout out to Android Pizza for taking the initiative to get a fully stocked Play Store on the PTAB8000. Special thanks to the guys over at FreakTab for providing the permission files needed for the patch on the PTAB8000. Last but not least I would like to thank all of you for testing every release. You're feedback is critical to this product. Every post has helped with PAIO's development process.
PTAB8000 users please make sure you are running a stock firmware. If you have tried earlier versions of PAIO, or have used any other files to patch your tablet, you must re-flash your tablet. Please see the section below on flashing your PTAB8000.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UPDATE 12/30/12 -- Polaroid AIO v1.6b [Old, Stable Release]
I am leaving this version posted as it seems to have been the most stable version. This will work with Android Pizza's tutorial on the PTAB8000, and works perfectly on the PMID800. It is recommended this version be used to root, and 2.1b used to install the framework (if supported on your device).
Downloads
ADB Drivers
Polaroid AIO v1.6b
Polaroid AIO v2.1b
PTAB8000 Flashing Tutorial
PTAB8000 v2 Firmware (v1 is no longer hosted by Southern Telecom)
Keep up the good work, and if you need anyone to test it, let me know.
Polaroid AIO
Was able to add google play to the PMID800 Polaroid Tablet. There was all ready some framework, so I removed google then re-added.
uncuthkid said:
Was able to add google play to the PMID800 Polaroid Tablet. There was all ready some framework, so I removed google then re-added.
Click to expand...
Click to collapse
Great to hear, does everything work correctly?
Well unfortunately it seems my ptab8000's screen stopped working... I am going to try and get the device exchanged, Khols may be out of stock on this item now... :-/
This set of instructions worked for installing Google Play on my PMID10C.
http://forum.xda-developers.com/showthread.php?t=1749707
Just updated this thread see the original post for the Polaroid All in One 1.3b beta release. I need people to test this update and let me know if it fixes the issues with the Google Services Framework, and the Google Play Store crashing. Make sure you choose Remove Google Applications and Framework first be fore you install the updated gapps.
Good luck please post back to this thread with your results.
-Wayne
Minor Bug Fix
Fixed minor bug when displaying information about connected device. updated post, please download 1.3.1b
TeODH4 said:
Fixed minor bug when displaying information about connected device. updated post, please download 1.3.1b
Click to expand...
Click to collapse
I'm trying to give it a go but I cannot get Windows 8 to recognise the device when I plug it in. I managed to get the ADB drivers installed eventually as you need a work around for the "The third-party INF does not contain digital signature information" but that didnt help Windows 8 see the device. Then I installed the Google USB Drivers from the Android SDK Manager, but that hasn't helped.
I have everything checked correctly in the Settings --> Developer's section too....... Anyone else managed to get this device to work with Windows 8?
Pihrana said:
I'm trying to give it a go but I cannot get Windows 8 to recognise the device when I plug it in. I managed to get the ADB drivers installed eventually as you need a work around for the "The third-party INF does not contain digital signature information" but that didnt help Windows 8 see the device. Then I installed the Google USB Drivers from the Android SDK Manager, but that hasn't helped.
I have everything checked correctly in the Settings --> Developer's section too....... Anyone else managed to get this device to work with Windows 8?
Click to expand...
Click to collapse
What device do you have? Did you follow these steps here? http://forum.xda-developers.com/showthread.php?t=1982718 Can you run an adb command to interface with the device? I do not currently have a Windows 8 install to debug on. Give me a couple hours and I'll setup a VM for some debuging... You may also want to try using compatibility mode. http://www.online-tech-tips.com/windows-8/run-a-program-in-compatibility-mode-in-windows-8/
OK. I ended up using a crappy Netbook running Win7 and your v1.3b can see the device perfectly. Unfortunately I don't have any Google apps, but I do have root. Not sure why framework and Google apps didn't work but I even tried resetting the tablet to stock to try again. I've tried all options numerous times, and no beans on this device I'm afraid.
Like I said. It rooted perfectly and I love how slick everything is. Seriously impressive work my friend. Hopefully you can take a look into the issues I'm having? Anyone else had this problem?
I do have one more PTAB8000 I can try this one once I'm given the tablet that is... (Doing this for my Lads girlfriend and sister)
Thanks TeOHD4 !!
Pihrana said:
OK. I ended up using a crappy Netbook running Win7 and your v1.3b can see the device perfectly. Unfortunately I don't have any Google apps, but I do have root. Not sure why framework and Google apps didn't work but I even tried resetting the tablet to stock to try again. I've tried all options numerous times, and no beans on this device I'm afraid.
Like I said. It rooted perfectly and I love how slick everything is. Seriously impressive work my friend. Hopefully you can take a look into the issues I'm having? Anyone else had this problem?
I do have one more PTAB8000 I can try this one once I'm given the tablet that is... (Doing this for my Lads girlfriend and sister)
Thanks TeOHD4 !!
Click to expand...
Click to collapse
Is the device that will not give you google apps a PTAB8000? No errors given?
Also have you tried 1.2? The Framework is a little buggy but will be helpful in debugging why this is not working with your device.
Thank you for the support. Glad you where able to at least get root, and we will work on getting google apps installed for you. Give 1.2 a go and let me know what happens.
TeODH4 said:
Is the device that will not give you google apps a PTAB8000? No errors given?
Also have you tried 1.2? The Framework is a little buggy but will be helpful in debugging why this is not working with your device.
Thank you for the support. Glad you where able to at least get root, and we will work on getting google apps installed for you. Give 1.2 a go and let me know what happens.
Click to expand...
Click to collapse
Both are PTAB8000's. The one I have at the moment just worked with v1.2 on the 1st attempt when trying to add the framework and gApps.. I didn't try any other option since v1.3b rooted it first..
v1.3b didnt give any error messages... My observations between v1.2 and v1.3b is that they both show that they are doing the same thing, but v1.3b does it at such a speed that it's hard to imagine that the device had enough time to receive the files that were being pushed. On v1.2 is was a lot slower and more in tune with the fact that data is being pushed to the device.
Then on the reboot, you get the Android is updating logo before hitting the desktop for version 1.2, whereas I didn't get that with v1.3b....
I can't test any of the apps just yet as I need my Son's, Girlfriends gmail account details but so far so good.
Seriously GREAT work TeODH4
Pihrana said:
Both are PTAB8000's. The one I have at the moment just worked with v1.2 on the 1st attempt when trying to add the framework and gApps.. I didn't try any other option since v1.3b rooted it first..
v1.3b didnt give any error messages... My observations between v1.2 and v1.3b is that they both show that they are doing the same thing, but v1.3b does it at such a speed that it's hard to imagine that the device had enough time to receive the files that were being pushed. On v1.2 is was a lot slower and more in tune with the fact that data is being pushed to the device.
Then on the reboot, you get the Android is updating logo before hitting the desktop for version 1.2, whereas I didn't get that with v1.3b....
I can't test any of the apps just yet as I need my Son's, Girlfriends gmail account details but so far so good.
Seriously GREAT work TeODH4
Click to expand...
Click to collapse
Ok thanks for your feedback. 1.2 should work for you However you will experience some bugs such as com.google.gapps randomly crashing which i tried to fix. in 1.3b. I will take a look at the 1.3 code and see if i can figure out what the issue is. Maybe add some better error checking.
Pihrana said:
Both are PTAB8000's. The one I have at the moment just worked with v1.2 on the 1st attempt when trying to add the framework and gApps.. I didn't try any other option since v1.3b rooted it first..
v1.3b didnt give any error messages... My observations between v1.2 and v1.3b is that they both show that they are doing the same thing, but v1.3b does it at such a speed that it's hard to imagine that the device had enough time to receive the files that were being pushed. On v1.2 is was a lot slower and more in tune with the fact that data is being pushed to the device.
Then on the reboot, you get the Android is updating logo before hitting the desktop for version 1.2, whereas I didn't get that with v1.3b....
I can't test any of the apps just yet as I need my Son's, Girlfriends gmail account details but so far so good.
Seriously GREAT work TeODH4
Click to expand...
Click to collapse
Found the issue with 1.3. just a simple typo when trying to change directory to Resources/gapps. If you don't mind give 1.4b a shot,
Be sure to Remove Google Apps first, then install. It worked just fine with my simulation. But without having a tablet to debug on at the moment its hard to be sure...
Thanks,
Wayne
PolaroidAIO stuck waiting for the devide to be ready
Hi,
I tried AIO 1.3-1.4 on a PTAB8000 and it it just waits forever for the tablet to be ready. The ADB drivers appear properly installed (I see an Android Phone/ADB interface in the device manager on XP SP2). Any suggestions?
Thanks,
Nick
dutanico said:
Hi,
I tried AIO 1.3-1.4 on a PTAB8000 and it it just waits forever for the tablet to be ready. The ADB drivers appear properly installed (I see an Android Phone/ADB interface in the device manager on XP SP2). Any suggestions?
Thanks,
Nick
Click to expand...
Click to collapse
can you upload a screenshot? what device do you have?
Here it is attached. The device is PTAB8000
dutanico said:
Here it is attached. The device is PTAB8000
Click to expand...
Click to collapse
ok it may be an issue with the code, I'm installing windows xp now to debug give me like an hour to figure things out.
TeODH4 said:
Found the issue with 1.3. just a simple typo when trying to change directory to Resources/gapps. If you don't mind give 1.4b a shot,
Be sure to Remove Google Apps first, then install. It worked just fine with my simulation. But without having a tablet to debug on at the moment its hard to be sure...
Thanks,
Wayne
Click to expand...
Click to collapse
Hey Wayne, My sons GF has took her tablet after finishing work. Until she brings her sisters tablet over I'm without a device to help try things out

[ROM]CleanSTOCK-MM.209-v3.4[Z00X/ZX551ML]-16 March

CleanSTOCK​
-->Features<--
based last asus stock firmware Z00X-4.209
Last Busybox
Last Magisk V11.1
Last SuperSU v2.79-SR3
Last Systemless Xposed V87.0
ZenUi 3.0 SystemUi from ZenFone 3
Dark Theme Status Bar (All Credits to @japh1997)
Blur Effect on the Status Bar/Recents Screen (All Credits to @BORETS24)
New Bootanimation (Google)
Notifications Android Nougat Style
Removed Notification of Headset Connected
61 Apps Removed
Added Google Keyboard (replaces the keyboard ASUS)
Removed "Cd rom install.iso"
Added Kernel Adiutor MOD
Added SystemUi Sounds, ringtones and Notifications from Google Pixel/Xperia/LG
New Wallpaper
Kernel STOCK
and more...
*BUGs: None ^^
List of Apps Removed
->Installation<-
->Full Tutorial (Portuguese Video)
->CleanSTOCK Official Site (PT/EN)
->Telegram Group (PT/EN)
->Bootloader Update Files
->Update to MMbootloader (Ifwi Version -> 096.0123)
->Install TWRP 3.0.2-m1 (Z00A)
->Full Wipe (System/Data/Cache/Dalvik)
->Install ROM and Reboot
->Downloads<-
->Z00X/ZX551ML [V3.4!]
->Add-on ASUS Themes App (Optional/Remove Dark Theme)
->VIPER4Arise + 10 Profiles (Optional)
***Credits/Thanks***
@IODroids for tests in ROM
@topjohnwu for Magisk and Xposed SystemLess
@Paget96 for L Speed BETA
@BORETS24 for SystemUi
@japh1997 for Dark Theme Status Bar
AsusTeam
Google
PayPal: [email protected]
I am not responsible for damage to the device, do so at your own risk!
XDA:DevDB Information
CleanSTOCK-MM, ROM for the Asus ZenFone Zoom
Contributors
GuilhermeXtreme
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: V3.4
Stable Release Date: 2017-03-17
Created 2017-03-16
Last Updated 2017-03-16
Reserved for screenshots..
Reserved for some more additional information.. (if required)
If you are dialer/contacts is crashing after the installation, patch this Contacts.zip from TWRP or a suitable custom recovery.
Check attachment:
Can you add a link to the version of twrp you say to use in the open? Looks very nice.
famewolf said:
Can you add a link to the version of twrp you say to use in the open? Looks very nice.
Click to expand...
Click to collapse
Download in "Bootloader Update Files", Inside of "MM Bootloader" folder.
Need Help
Hi, The rom looks Beautiful. I really want to try it out but i cant get the bootloader unlocked in the first place. Can You please help me? (P.S, I have an asus zenfone zoom 64gb)
hrithik12373 said:
Hi, The rom looks Beautiful. I really want to try it out but i cant get the bootloader unlocked in the first place. Can You please help me? (P.S, I have an asus zenfone zoom 64gb)
Click to expand...
Click to collapse
Need download unlock tool, download in ASUS site Support (Firmware pag.)
GuilhermeXtreme said:
Need download unlock tool, download in ASUS site Support (Firmware pag.)
Click to expand...
Click to collapse
I did, but whenever it starts unlocking, it fails and I never get the inverted screen.
I believe the problem is with the drivers on my laptop as i believe that i didnt install them properly, mostly because i cant figure out how to
hrithik12373 said:
I did, but whenever it starts unlocking, it fails and I never get the inverted screen.
I believe the problem is with the drivers on my laptop as i believe that i didnt install them properly, mostly because i cant figure out how to
Click to expand...
Click to collapse
Try using a different PC, fresh windows 7 or windows 10.
I have personally tested the ROM on 2 devices over 50+ times.. Worked and Without unlocker tool from Asus..
Upgrade
Can I use this rom to upgrade to Marshmallow? Iam currently using lollipop OS. Will this delete all existing photos and videos in phone memory? I have a rooted ZX551ML 128gb variant. Thanks.
IODroids said:
Try using a different PC, fresh windows 7 or windows 10.
I have personally tested the ROM on 2 devices over 50+ times.. Worked and Without unlocker tool from Asus..
Click to expand...
Click to collapse
Are you saying there is no need to use the Asus unlocker tool?
Saw a bunch of warning on their site saying I have sign away the first born if I ever use it.
Also does the various memory make any difference? Since there are 32/64 and 128gb versions.
@GuilhermeXtreme can you kindly shred some light on this posts.
IODroids said:
Try using a different PC, fresh windows 7 or windows 10.
I have personally tested the ROM on 2 devices over 50+ times.. Worked and Without unlocker tool from Asus..
Click to expand...
Click to collapse
I just finished trying on at least 4 different desktops and laptops. Still no luck.
(PS-The screenshots attached are the same errors I got on every single computer)
->Install TWRP 3.0.2-m1 (Z00A)
It works the same on Z00X?
I see IODroids got it working so I assume it works fine.
AlienTeck said:
Are you saying there is no need to use the Asus unlocker tool?
Saw a bunch of warning on their site saying I have sign away the first born if I ever use it.
Also does the various memory make any difference? Since there are 32/64 and 128gb versions.
Click to expand...
Click to collapse
I am on 128 GB variant, check screenshots and works fabulous.
IODroids said:
I am on 128 GB variant, check screenshots and works fabulous.
Click to expand...
Click to collapse
Did you find d out what's different between the 2 version s z00x and z00a?
I saw a comparability listing showing it as a zenfone 2 model and not zoom. Although both seem to run same programs including camera app. Google camera can't access some specialised camera processing on these phones and pics come out looking bad in anything but sun light. I think so will all other camera apps.
AlienTeck said:
Did you find d out what's different between the 2 version s z00x and z00a?
I saw a comparability listing showing it as a zenfone 2 model and not zoom. Although both seem to run same programs including camera app. Google camera can't access some specialised camera processing on these phones and pics come out looking bad in anything but sun light. I think so will all other camera apps.
Click to expand...
Click to collapse
You are absolutely correct, the major difference is camera.
I tried CleanStock MM which was based on Z00A base, everything worked except 2 important things (camera and mobile network, it was way too smooth comparatively).
Finally the OP of this thread @GuilhermeXtreme did the dirty work of porting the z00x base with his custom modifications, removing bloatware/rooting/magisk and other enormous stuff.
z00 or z00d varies because of hardware differences like 16, 32, 64, GB variants, different processors too.
Check wikipedia for more detailed information about this.
One thing I got to mention is, this phone uses Intel cisc CPU, installing Android apps not optimized for it draws more than twice the battery consumption. Not only does the CPU itself draw more power but the display does too. If all 3 are not synced the battery drains very fast. Even though Asus says install Google apps, I am not sure they are all optimized for Intel. Emulating is slower and also a power hog.
Just things I noticed while using it. During use the battery drain is huge. It will last 2 or 3 days with only phone use but not for apps. Using unoptimized apps drains battetyuch faster than on arm CPU. I went back to many Asus apps now which are huge in size but uses less power.
how to install xposed?
Nice work! Any chance of taking a peak at Lineage OS for this device?

Categories

Resources